WEBVTT Kind: captions Language: en 00:00:03.770 --> 00:00:17.189 align:start position:0% [Music] 00:00:17.189 --> 00:00:17.199 align:start position:0% 00:00:17.199 --> 00:00:22.710 align:start position:0% all<00:00:17.680> right<00:00:18.680> GM<00:00:19.320> welcome<00:00:20.119> back<00:00:21.119> so<00:00:21.720> uh 00:00:22.710 --> 00:00:22.720 align:start position:0% all right GM welcome back so uh 00:00:22.720 --> 00:00:24.630 align:start position:0% all right GM welcome back so uh hopefully<00:00:23.080> all<00:00:23.199> of<00:00:23.320> us<00:00:23.439> are<00:00:23.640> here<00:00:24.000> for<00:00:24.480> the 00:00:24.630 --> 00:00:24.640 align:start position:0% hopefully all of us are here for the 00:00:24.640 --> 00:00:25.790 align:start position:0% hopefully all of us are here for the workshop<00:00:25.119> this 00:00:25.790 --> 00:00:25.800 align:start position:0% workshop this 00:00:25.800 --> 00:00:28.470 align:start position:0% workshop this morning<00:00:26.800> this<00:00:26.960> is<00:00:27.439> going<00:00:27.560> to<00:00:27.760> be<00:00:28.039> about 00:00:28.470 --> 00:00:28.480 align:start position:0% morning this is going to be about 00:00:28.480 --> 00:00:30.550 align:start position:0% morning this is going to be about finding<00:00:29.000> bugs 00:00:30.550 --> 00:00:30.560 align:start position:0% finding bugs 00:00:30.560 --> 00:00:32.549 align:start position:0% finding bugs which<00:00:30.720> is<00:00:30.920> really<00:00:31.199> what<00:00:31.800> security<00:00:32.239> is<00:00:32.360> all 00:00:32.549 --> 00:00:32.559 align:start position:0% which is really what security is all 00:00:32.559 --> 00:00:35.790 align:start position:0% which is really what security is all about<00:00:33.120> finding<00:00:33.559> and<00:00:33.800> fixing<00:00:34.200> bugs 00:00:35.790 --> 00:00:35.800 align:start position:0% about finding and fixing bugs 00:00:35.800 --> 00:00:38.030 align:start position:0% about finding and fixing bugs hopefully<00:00:36.800> and<00:00:37.160> uh<00:00:37.280> this<00:00:37.399> is<00:00:37.480> an<00:00:37.600> interesting 00:00:38.030 --> 00:00:38.040 align:start position:0% hopefully and uh this is an interesting 00:00:38.040 --> 00:00:40.190 align:start position:0% hopefully and uh this is an interesting format<00:00:38.320> for<00:00:38.399> a<00:00:38.559> workshop<00:00:38.920> we<00:00:39.120> trying<00:00:39.399> this<00:00:39.559> out 00:00:40.190 --> 00:00:40.200 align:start position:0% format for a workshop we trying this out 00:00:40.200 --> 00:00:43.910 align:start position:0% format for a workshop we trying this out um<00:00:40.559> recently<00:00:41.559> so<00:00:41.800> this<00:00:41.960> is<00:00:42.440> going<00:00:42.600> to<00:00:42.879> have<00:00:43.280> 42 00:00:43.910 --> 00:00:43.920 align:start position:0% um recently so this is going to have 42 00:00:43.920 --> 00:00:46.790 align:start position:0% um recently so this is going to have 42 tips<00:00:44.840> from<00:00:45.480> the<00:00:45.600> four<00:00:45.960> security<00:00:46.320> researchers 00:00:46.790 --> 00:00:46.800 align:start position:0% tips from the four security researchers 00:00:46.800 --> 00:00:48.069 align:start position:0% tips from the four security researchers that<00:00:46.920> you<00:00:47.039> see 00:00:48.069 --> 00:00:48.079 align:start position:0% that you see 00:00:48.079 --> 00:00:52.950 align:start position:0% that you see here<00:00:49.079> 42<00:00:49.800> why<00:00:50.000> 42<00:00:50.559> 42<00:00:51.039> is<00:00:51.160> supposedly<00:00:51.960> the 00:00:52.950 --> 00:00:52.960 align:start position:0% here 42 why 42 42 is supposedly the 00:00:52.960 --> 00:00:54.709 align:start position:0% here 42 why 42 42 is supposedly the ultimate<00:00:53.440> answer<00:00:53.680> to<00:00:53.960> all<00:00:54.120> questions<00:00:54.440> in<00:00:54.559> the 00:00:54.709 --> 00:00:54.719 align:start position:0% ultimate answer to all questions in the 00:00:54.719 --> 00:00:58.549 align:start position:0% ultimate answer to all questions in the Galaxy<00:00:55.480> so<00:00:55.800> why<00:00:55.920> not<00:00:56.079> finding<00:00:56.399> bugs<00:00:56.719> as 00:00:58.549 --> 00:00:58.559 align:start position:0% Galaxy so why not finding bugs as 00:00:58.559 --> 00:01:01.029 align:start position:0% Galaxy so why not finding bugs as well<00:00:59.559> and<00:00:59.680> the<00:01:00.000> for<00:01:00.160> security<00:01:00.480> researchers 00:01:01.029 --> 00:01:01.039 align:start position:0% well and the for security researchers 00:01:01.039 --> 00:01:03.509 align:start position:0% well and the for security researchers here<00:01:01.800> I'll<00:01:01.960> let<00:01:02.239> my<00:01:02.519> smarter<00:01:03.000> colleagues 00:01:03.509 --> 00:01:03.519 align:start position:0% here I'll let my smarter colleagues 00:01:03.519 --> 00:01:06.710 align:start position:0% here I'll let my smarter colleagues introduce<00:01:04.080> themselves<00:01:04.400> first<00:01:05.239> with 00:01:06.710 --> 00:01:06.720 align:start position:0% introduce themselves first with 00:01:06.720 --> 00:01:10.710 align:start position:0% introduce themselves first with uran<00:01:07.720> thank<00:01:07.920> you<00:01:08.640> um<00:01:09.439> I<00:01:09.520> am<00:01:09.880> a<00:01:10.240> security 00:01:10.710 --> 00:01:10.720 align:start position:0% uran thank you um I am a security 00:01:10.720 --> 00:01:13.910 align:start position:0% uran thank you um I am a security researcher<00:01:11.320> at<00:01:11.560> consensus<00:01:12.240> diligence<00:01:13.240> where 00:01:13.910 --> 00:01:13.920 align:start position:0% researcher at consensus diligence where 00:01:13.920 --> 00:01:17.710 align:start position:0% researcher at consensus diligence where I<00:01:14.920> work<00:01:15.240> mostly<00:01:15.600> on<00:01:15.960> tooling<00:01:16.360> and<00:01:16.720> automation 00:01:17.710 --> 00:01:17.720 align:start position:0% I work mostly on tooling and automation 00:01:17.720 --> 00:01:19.429 align:start position:0% I work mostly on tooling and automation so<00:01:17.960> you<00:01:18.240> might<00:01:18.400> have<00:01:18.520> used<00:01:18.840> a<00:01:19.000> couple<00:01:19.200> of<00:01:19.320> my 00:01:19.429 --> 00:01:19.439 align:start position:0% so you might have used a couple of my 00:01:19.439 --> 00:01:23.550 align:start position:0% so you might have used a couple of my tools<00:01:20.400> uh<00:01:20.680> but<00:01:21.159> I<00:01:21.479> am<00:01:21.840> also<00:01:22.439> a<00:01:23.000> buck<00:01:23.240> Bounty 00:01:23.550 --> 00:01:23.560 align:start position:0% tools uh but I am also a buck Bounty 00:01:23.560 --> 00:01:26.429 align:start position:0% tools uh but I am also a buck Bounty Hunter<00:01:24.240> so<00:01:24.479> most<00:01:24.640> of<00:01:24.799> my<00:01:24.960> tips<00:01:25.240> today<00:01:25.600> will<00:01:26.119> uh 00:01:26.429 --> 00:01:26.439 align:start position:0% Hunter so most of my tips today will uh 00:01:26.439 --> 00:01:32.350 align:start position:0% Hunter so most of my tips today will uh go<00:01:26.680> into<00:01:27.240> that<00:01:27.439> part<00:01:27.640> of<00:01:27.799> security<00:01:28.280> research 00:01:32.350 --> 00:01:32.360 align:start position:0% 00:01:32.360 --> 00:01:35.030 align:start position:0% hi<00:01:32.560> everyone<00:01:33.040> I'm<00:01:33.240> dcho<00:01:34.200> um<00:01:34.439> I<00:01:34.560> work<00:01:34.799> for<00:01:34.920> the 00:01:35.030 --> 00:01:35.040 align:start position:0% hi everyone I'm dcho um I work for the 00:01:35.040 --> 00:01:37.270 align:start position:0% hi everyone I'm dcho um I work for the red<00:01:35.280> y<00:01:35.520> I'm<00:01:35.600> a<00:01:35.720> co-founder<00:01:36.560> we<00:01:36.720> do<00:01:36.960> security 00:01:37.270 --> 00:01:37.280 align:start position:0% red y I'm a co-founder we do security 00:01:37.280 --> 00:01:39.270 align:start position:0% red y I'm a co-founder we do security for<00:01:37.479> the<00:01:37.600> public<00:01:37.920> benefit<00:01:38.280> of<00:01:38.439> ethereum 00:01:39.270 --> 00:01:39.280 align:start position:0% for the public benefit of ethereum 00:01:39.280 --> 00:01:41.670 align:start position:0% for the public benefit of ethereum ecosystem<00:01:40.280> um<00:01:40.799> and<00:01:40.920> in<00:01:41.040> the<00:01:41.200> past<00:01:41.360> I<00:01:41.439> used<00:01:41.600> to 00:01:41.670 --> 00:01:41.680 align:start position:0% ecosystem um and in the past I used to 00:01:41.680 --> 00:01:44.749 align:start position:0% ecosystem um and in the past I used to be<00:01:41.759> a<00:01:41.880> l<00:01:42.079> aitor<00:01:42.520> open<00:01:42.720> sing<00:01:43.240> for<00:01:44.000> many<00:01:44.280> years 00:01:44.749 --> 00:01:44.759 align:start position:0% be a l aitor open sing for many years 00:01:44.759 --> 00:01:47.149 align:start position:0% be a l aitor open sing for many years and<00:01:45.079> before<00:01:45.360> that<00:01:45.520> I<00:01:45.640> was<00:01:45.759> a<00:01:46.479> web<00:01:46.719> developer 00:01:47.149 --> 00:01:47.159 align:start position:0% and before that I was a web developer 00:01:47.159 --> 00:01:48.870 align:start position:0% and before that I was a web developer and 00:01:48.870 --> 00:01:48.880 align:start position:0% and 00:01:48.880 --> 00:01:52.030 align:start position:0% and pester<00:01:49.880> hey<00:01:50.079> everyone<00:01:50.600> I'm<00:01:50.799> Nat<00:01:51.399> I'm<00:01:51.759> an 00:01:52.030 --> 00:01:52.040 align:start position:0% pester hey everyone I'm Nat I'm an 00:01:52.040 --> 00:01:54.510 align:start position:0% pester hey everyone I'm Nat I'm an independent<00:01:52.640> security<00:01:53.200> researcher<00:01:54.200> um<00:01:54.360> I 00:01:54.510 --> 00:01:54.520 align:start position:0% independent security researcher um I 00:01:54.520 --> 00:01:56.550 align:start position:0% independent security researcher um I spent<00:01:54.799> four<00:01:55.079> years<00:01:55.320> at<00:01:55.439> Cher<00:01:55.799> La<00:01:55.960> bits<00:01:56.439> uh 00:01:56.550 --> 00:01:56.560 align:start position:0% spent four years at Cher La bits uh 00:01:56.560 --> 00:01:58.670 align:start position:0% spent four years at Cher La bits uh where<00:01:56.680> I<00:01:56.799> did<00:01:56.960> mainly<00:01:57.399> Security<00:01:57.840> reviews<00:01:58.479> and 00:01:58.670 --> 00:01:58.680 align:start position:0% where I did mainly Security reviews and 00:01:58.680 --> 00:02:01.630 align:start position:0% where I did mainly Security reviews and before<00:01:59.000> that<00:01:59.399> was<00:02:00.159> blockchain<00:02:00.560> developer<00:02:01.159> for 00:02:01.630 --> 00:02:01.640 align:start position:0% before that was blockchain developer for 00:02:01.640 --> 00:02:04.749 align:start position:0% before that was blockchain developer for three<00:02:02.000> years<00:02:03.000> so<00:02:03.520> yeah<00:02:03.840> today<00:02:04.159> my<00:02:04.320> tips<00:02:04.560> are 00:02:04.749 --> 00:02:04.759 align:start position:0% three years so yeah today my tips are 00:02:04.759 --> 00:02:06.630 align:start position:0% three years so yeah today my tips are kind<00:02:04.880> of<00:02:05.159> going<00:02:05.280> to<00:02:05.439> be<00:02:05.880> blockchain<00:02:06.360> Dev 00:02:06.630 --> 00:02:06.640 align:start position:0% kind of going to be blockchain Dev 00:02:06.640 --> 00:02:10.029 align:start position:0% kind of going to be blockchain Dev related<00:02:07.079> and<00:02:07.360> security<00:02:07.719> researcher 00:02:10.029 --> 00:02:10.039 align:start position:0% related and security researcher 00:02:10.039 --> 00:02:13.350 align:start position:0% related and security researcher related<00:02:11.039> fantastic<00:02:11.520> and<00:02:11.680> I'm<00:02:12.040> uh<00:02:12.200> Rajiv<00:02:13.160> so 00:02:13.350 --> 00:02:13.360 align:start position:0% related fantastic and I'm uh Rajiv so 00:02:13.360 --> 00:02:15.270 align:start position:0% related fantastic and I'm uh Rajiv so I've<00:02:13.520> been<00:02:13.640> a<00:02:13.800> security<00:02:14.200> researcher<00:02:15.120> pretty 00:02:15.270 --> 00:02:15.280 align:start position:0% I've been a security researcher pretty 00:02:15.280 --> 00:02:18.070 align:start position:0% I've been a security researcher pretty much<00:02:15.480> my<00:02:15.599> whole<00:02:15.879> life<00:02:16.680> started<00:02:17.239> with<00:02:17.599> ethereum 00:02:18.070 --> 00:02:18.080 align:start position:0% much my whole life started with ethereum 00:02:18.080 --> 00:02:21.830 align:start position:0% much my whole life started with ethereum security<00:02:18.599> roughly<00:02:19.040> about<00:02:19.680> U<00:02:19.920> 6<00:02:20.160> to8<00:02:20.519> years<00:02:20.840> ago 00:02:21.830 --> 00:02:21.840 align:start position:0% security roughly about U 6 to8 years ago 00:02:21.840 --> 00:02:24.350 align:start position:0% security roughly about U 6 to8 years ago um<00:02:22.120> early<00:02:22.720> participant<00:02:23.400> in<00:02:24.000> some<00:02:24.160> of<00:02:24.280> the 00:02:24.350 --> 00:02:24.360 align:start position:0% um early participant in some of the 00:02:24.360 --> 00:02:26.630 align:start position:0% um early participant in some of the leading<00:02:24.840> on<00:02:25.120> audit<00:02:25.440> contest 00:02:26.630 --> 00:02:26.640 align:start position:0% leading on audit contest 00:02:26.640 --> 00:02:29.509 align:start position:0% leading on audit contest platforms<00:02:27.640> um<00:02:28.120> and<00:02:28.319> then<00:02:28.920> uh<00:02:29.000> for<00:02:29.200> the<00:02:29.319> last 00:02:29.509 --> 00:02:29.519 align:start position:0% platforms um and then uh for the last 00:02:29.519 --> 00:02:30.990 align:start position:0% platforms um and then uh for the last couple<00:02:29.720> of<00:02:30.040> years<00:02:30.360> I've<00:02:30.519> been<00:02:30.640> a<00:02:30.760> lead 00:02:30.990 --> 00:02:31.000 align:start position:0% couple of years I've been a lead 00:02:31.000 --> 00:02:34.150 align:start position:0% couple of years I've been a lead security<00:02:31.360> researcher<00:02:31.920> with<00:02:32.239> speit<00:02:33.160> Cantina 00:02:34.150 --> 00:02:34.160 align:start position:0% security researcher with speit Cantina 00:02:34.160 --> 00:02:37.869 align:start position:0% security researcher with speit Cantina um<00:02:34.920> and<00:02:35.120> in<00:02:35.319> this<00:02:35.560> context<00:02:36.280> um<00:02:36.560> started<00:02:36.959> secum 00:02:37.869 --> 00:02:37.879 align:start position:0% um and in this context um started secum 00:02:37.879 --> 00:02:42.390 align:start position:0% um and in this context um started secum about<00:02:38.400> three<00:02:38.720> years<00:02:38.959> ago<00:02:39.280> so<00:02:40.040> secum<00:02:41.040> was<00:02:41.599> um 00:02:42.390 --> 00:02:42.400 align:start position:0% about three years ago so secum was um 00:02:42.400 --> 00:02:44.990 align:start position:0% about three years ago so secum was um was<00:02:42.760> was<00:02:42.920> funded<00:02:43.400> by<00:02:43.599> an<00:02:44.040> ethereum<00:02:44.519> Foundation 00:02:44.990 --> 00:02:45.000 align:start position:0% was was funded by an ethereum Foundation 00:02:45.000 --> 00:02:46.750 align:start position:0% was was funded by an ethereum Foundation Grant<00:02:45.519> and<00:02:45.720> collaborating<00:02:46.280> with<00:02:46.440> some<00:02:46.560> of<00:02:46.680> the 00:02:46.750 --> 00:02:46.760 align:start position:0% Grant and collaborating with some of the 00:02:46.760 --> 00:02:48.869 align:start position:0% Grant and collaborating with some of the leading<00:02:47.159> projects<00:02:47.480> in<00:02:47.599> the<00:02:47.800> space<00:02:48.519> the<00:02:48.640> goal 00:02:48.869 --> 00:02:48.879 align:start position:0% leading projects in the space the goal 00:02:48.879 --> 00:02:51.710 align:start position:0% leading projects in the space the goal was<00:02:49.080> really<00:02:49.360> to<00:02:49.920> scale<00:02:50.360> ethereum<00:02:50.879> security 00:02:51.710 --> 00:02:51.720 align:start position:0% was really to scale ethereum security 00:02:51.720 --> 00:02:54.229 align:start position:0% was really to scale ethereum security right<00:02:51.959> and<00:02:52.120> by<00:02:52.319> that<00:02:52.480> we<00:02:52.599> mean<00:02:53.159> onboarding<00:02:54.000> the 00:02:54.229 --> 00:02:54.239 align:start position:0% right and by that we mean onboarding the 00:02:54.239 --> 00:02:56.750 align:start position:0% right and by that we mean onboarding the next<00:02:54.760> hundreds<00:02:55.239> and<00:02:55.480> thousands<00:02:55.879> of<00:02:56.080> security 00:02:56.750 --> 00:02:56.760 align:start position:0% next hundreds and thousands of security 00:02:56.760 --> 00:03:00.110 align:start position:0% next hundreds and thousands of security Auditors<00:02:57.760> U<00:02:57.920> to<00:02:58.239> make<00:02:58.480> ethereum<00:02:59.080> safer<00:02:59.920> so 00:03:00.110 --> 00:03:00.120 align:start position:0% Auditors U to make ethereum safer so 00:03:00.120 --> 00:03:03.270 align:start position:0% Auditors U to make ethereum safer so secum<00:03:00.959> is<00:03:01.560> um<00:03:02.239> is<00:03:02.400> really<00:03:02.599> an<00:03:02.760> online 00:03:03.270 --> 00:03:03.280 align:start position:0% secum is um is really an online 00:03:03.280 --> 00:03:05.710 align:start position:0% secum is um is really an online community<00:03:04.280> known<00:03:04.560> for<00:03:04.720> its<00:03:04.920> boot<00:03:05.239> camp<00:03:05.519> check 00:03:05.710 --> 00:03:05.720 align:start position:0% community known for its boot camp check 00:03:05.720 --> 00:03:08.670 align:start position:0% community known for its boot camp check it<00:03:05.840> out<00:03:06.239> online<00:03:07.239> has<00:03:07.440> monthly<00:03:07.920> quizzes 00:03:08.670 --> 00:03:08.680 align:start position:0% it out online has monthly quizzes 00:03:08.680 --> 00:03:12.309 align:start position:0% it out online has monthly quizzes designed<00:03:09.280> by<00:03:10.200> uh<00:03:10.680> many<00:03:10.920> of<00:03:11.120> the<00:03:11.640> well<00:03:11.879> all<00:03:12.159> all 00:03:12.309 --> 00:03:12.319 align:start position:0% designed by uh many of the well all all 00:03:12.319 --> 00:03:14.630 align:start position:0% designed by uh many of the well all all the<00:03:12.480> people<00:03:13.000> standing<00:03:13.480> here<00:03:13.760> and<00:03:14.000> many<00:03:14.400> many 00:03:14.630 --> 00:03:14.640 align:start position:0% the people standing here and many many 00:03:14.640 --> 00:03:17.030 align:start position:0% the people standing here and many many others<00:03:15.000> in<00:03:15.120> the<00:03:15.239> room<00:03:15.519> as<00:03:15.640> well<00:03:16.480> uh<00:03:16.599> check<00:03:16.840> that 00:03:17.030 --> 00:03:17.040 align:start position:0% others in the room as well uh check that 00:03:17.040 --> 00:03:20.949 align:start position:0% others in the room as well uh check that out<00:03:17.799> and<00:03:18.280> U<00:03:18.440> secum<00:03:19.040> also<00:03:19.400> hosts<00:03:20.080> trustex<00:03:20.799> which 00:03:20.949 --> 00:03:20.959 align:start position:0% out and U secum also hosts trustex which 00:03:20.959 --> 00:03:23.309 align:start position:0% out and U secum also hosts trustex which is<00:03:21.400> uh<00:03:21.519> one<00:03:21.599> of<00:03:21.720> the<00:03:21.799> leading<00:03:22.599> ethereum 00:03:23.309 --> 00:03:23.319 align:start position:0% is uh one of the leading ethereum 00:03:23.319 --> 00:03:26.430 align:start position:0% is uh one of the leading ethereum security<00:03:23.799> focused<00:03:24.239> events<00:03:25.239> so<00:03:25.480> with<00:03:25.680> that<00:03:26.239> we 00:03:26.430 --> 00:03:26.440 align:start position:0% security focused events so with that we 00:03:26.440 --> 00:03:28.350 align:start position:0% security focused events so with that we will<00:03:26.799> kick<00:03:27.000> it<00:03:27.200> off<00:03:27.720> right<00:03:27.920> the<00:03:28.040> first 00:03:28.350 --> 00:03:28.360 align:start position:0% will kick it off right the first 00:03:28.360 --> 00:03:31.149 align:start position:0% will kick it off right the first question<00:03:29.159> we<00:03:29.319> really<00:03:29.560> need<00:03:29.799> need<00:03:29.920> to<00:03:30.159> ask<00:03:30.599> is 00:03:31.149 --> 00:03:31.159 align:start position:0% question we really need need to ask is 00:03:31.159 --> 00:03:33.789 align:start position:0% question we really need need to ask is why<00:03:31.920> right<00:03:32.280> why<00:03:32.840> why<00:03:32.959> are<00:03:33.080> we<00:03:33.200> doing<00:03:33.519> this 00:03:33.789 --> 00:03:33.799 align:start position:0% why right why why are we doing this 00:03:33.799 --> 00:03:36.910 align:start position:0% why right why why are we doing this Workshop<00:03:34.799> why<00:03:34.920> are<00:03:35.040> we<00:03:35.159> trying<00:03:35.360> to<00:03:35.519> find<00:03:35.920> bugs 00:03:36.910 --> 00:03:36.920 align:start position:0% Workshop why are we trying to find bugs 00:03:36.920 --> 00:03:40.309 align:start position:0% Workshop why are we trying to find bugs and<00:03:37.239> as<00:03:37.319> you<00:03:37.439> can<00:03:37.599> see<00:03:38.599> the<00:03:38.920> whole<00:03:39.920> not<00:03:40.159> not 00:03:40.309 --> 00:03:40.319 align:start position:0% and as you can see the whole not not 00:03:40.319 --> 00:03:42.470 align:start position:0% and as you can see the whole not not just<00:03:40.519> smart<00:03:40.840> contracts<00:03:41.319> or<00:03:41.599> opsc<00:03:42.080> and<00:03:42.239> other 00:03:42.470 --> 00:03:42.480 align:start position:0% just smart contracts or opsc and other 00:03:42.480 --> 00:03:44.750 align:start position:0% just smart contracts or opsc and other things<00:03:42.760> right<00:03:43.040> the<00:03:43.159> whole<00:03:44.000> domain<00:03:44.400> of 00:03:44.750 --> 00:03:44.760 align:start position:0% things right the whole domain of 00:03:44.760 --> 00:03:47.750 align:start position:0% things right the whole domain of blockchains<00:03:45.760> right<00:03:45.959> is<00:03:46.159> really<00:03:46.400> about<00:03:46.760> trust 00:03:47.750 --> 00:03:47.760 align:start position:0% blockchains right is really about trust 00:03:47.760 --> 00:03:49.070 align:start position:0% blockchains right is really about trust and<00:03:47.920> in<00:03:48.159> this 00:03:49.070 --> 00:03:49.080 align:start position:0% and in this 00:03:49.080 --> 00:03:52.830 align:start position:0% and in this case<00:03:50.080> finding<00:03:50.519> and<00:03:50.680> fixing<00:03:51.120> bugs<00:03:52.120> is<00:03:52.519> really 00:03:52.830 --> 00:03:52.840 align:start position:0% case finding and fixing bugs is really 00:03:52.840 --> 00:03:55.270 align:start position:0% case finding and fixing bugs is really one<00:03:52.959> of<00:03:53.079> the<00:03:53.239> biggest<00:03:54.079> um<00:03:54.599> you<00:03:54.720> know<00:03:54.920> technical 00:03:55.270 --> 00:03:55.280 align:start position:0% one of the biggest um you know technical 00:03:55.280 --> 00:03:58.149 align:start position:0% one of the biggest um you know technical risks<00:03:56.239> not<00:03:56.519> just<00:03:57.000> in<00:03:57.200> the<00:03:57.360> base<00:03:57.599> layer<00:03:57.920> in<00:03:58.040> the 00:03:58.149 --> 00:03:58.159 align:start position:0% risks not just in the base layer in the 00:03:58.159 --> 00:04:00.550 align:start position:0% risks not just in the base layer in the layer<00:03:58.400> ones<00:03:58.680> and<00:03:58.840> the<00:03:58.920> layer<00:03:59.200> twos<00:04:00.200> in<00:04:00.400> the 00:04:00.550 --> 00:04:00.560 align:start position:0% layer ones and the layer twos in the 00:04:00.560 --> 00:04:03.550 align:start position:0% layer ones and the layer twos in the bridges<00:04:01.239> and<00:04:01.519> anything<00:04:01.879> else<00:04:02.159> in<00:04:02.360> between<00:04:03.280> but 00:04:03.550 --> 00:04:03.560 align:start position:0% bridges and anything else in between but 00:04:03.560 --> 00:04:07.750 align:start position:0% bridges and anything else in between but also<00:04:04.120> in<00:04:04.640> all<00:04:05.000> the<00:04:05.599> daps<00:04:06.439> right<00:04:06.680> all<00:04:06.879> the<00:04:07.280> smart 00:04:07.750 --> 00:04:07.760 align:start position:0% also in all the daps right all the smart 00:04:07.760 --> 00:04:10.550 align:start position:0% also in all the daps right all the smart contracts<00:04:08.319> that<00:04:08.519> really<00:04:09.280> uh<00:04:09.519> and<00:04:09.799> and<00:04:10.280> all<00:04:10.439> the 00:04:10.550 --> 00:04:10.560 align:start position:0% contracts that really uh and and all the 00:04:10.560 --> 00:04:11.949 align:start position:0% contracts that really uh and and all the glue<00:04:10.840> that<00:04:10.959> holds<00:04:11.200> them<00:04:11.480> together<00:04:11.760> right<00:04:11.879> we 00:04:11.949 --> 00:04:11.959 align:start position:0% glue that holds them together right we 00:04:11.959 --> 00:04:14.149 align:start position:0% glue that holds them together right we need<00:04:12.079> to<00:04:12.159> be<00:04:12.280> finding<00:04:12.560> and<00:04:12.680> fixing 00:04:14.149 --> 00:04:14.159 align:start position:0% need to be finding and fixing 00:04:14.159 --> 00:04:16.749 align:start position:0% need to be finding and fixing bugs<00:04:15.159> why<00:04:15.439> so<00:04:15.680> why<00:04:15.840> is<00:04:15.959> that<00:04:16.120> important<00:04:16.560> I<00:04:16.639> mean 00:04:16.749 --> 00:04:16.759 align:start position:0% bugs why so why is that important I mean 00:04:16.759 --> 00:04:19.110 align:start position:0% bugs why so why is that important I mean it<00:04:16.880> should<00:04:17.560> be<00:04:17.799> very<00:04:18.079> obvious<00:04:18.479> to<00:04:18.720> many<00:04:18.919> of<00:04:19.040> the 00:04:19.110 --> 00:04:19.120 align:start position:0% it should be very obvious to many of the 00:04:19.120 --> 00:04:20.749 align:start position:0% it should be very obvious to many of the folks<00:04:19.479> many<00:04:19.639> of<00:04:19.759> the<00:04:19.840> security<00:04:20.199> researchers 00:04:20.749 --> 00:04:20.759 align:start position:0% folks many of the security researchers 00:04:20.759 --> 00:04:24.110 align:start position:0% folks many of the security researchers here<00:04:21.120> but<00:04:21.280> just<00:04:21.440> to<00:04:21.720> sort<00:04:21.919> of<00:04:22.440> put<00:04:22.600> it<00:04:22.840> once 00:04:24.110 --> 00:04:24.120 align:start position:0% here but just to sort of put it once 00:04:24.120 --> 00:04:28.350 align:start position:0% here but just to sort of put it once more<00:04:25.120> if<00:04:25.280> we<00:04:25.479> would<00:04:25.800> like<00:04:26.800> ethereum<00:04:27.759> to<00:04:27.960> be<00:04:28.240> the 00:04:28.350 --> 00:04:28.360 align:start position:0% more if we would like ethereum to be the 00:04:28.360 --> 00:04:32.070 align:start position:0% more if we would like ethereum to be the world<00:04:28.720> computer<00:04:30.039> if<00:04:30.199> we<00:04:30.520> want<00:04:30.720> to<00:04:30.960> really 00:04:32.070 --> 00:04:32.080 align:start position:0% world computer if we want to really 00:04:32.080 --> 00:04:34.710 align:start position:0% world computer if we want to really onboard<00:04:33.080> millions<00:04:33.520> and<00:04:33.720> billions<00:04:34.080> of<00:04:34.280> people 00:04:34.710 --> 00:04:34.720 align:start position:0% onboard millions and billions of people 00:04:34.720 --> 00:04:37.189 align:start position:0% onboard millions and billions of people onto<00:04:35.000> the<00:04:35.120> onchain<00:04:35.840> economy<00:04:36.840> and<00:04:36.960> if<00:04:37.080> you 00:04:37.189 --> 00:04:37.199 align:start position:0% onto the onchain economy and if you 00:04:37.199 --> 00:04:40.629 align:start position:0% onto the onchain economy and if you really<00:04:37.400> want<00:04:37.800> eth<00:04:38.360> to<00:04:38.560> be<00:04:39.360> ultrasound<00:04:40.000> money 00:04:40.629 --> 00:04:40.639 align:start position:0% really want eth to be ultrasound money 00:04:40.639 --> 00:04:43.070 align:start position:0% really want eth to be ultrasound money we<00:04:40.759> need<00:04:40.919> to<00:04:41.039> make<00:04:41.160> it<00:04:41.280> Ultra<00:04:41.639> safe<00:04:42.639> right<00:04:42.800> so 00:04:43.070 --> 00:04:43.080 align:start position:0% we need to make it Ultra safe right so 00:04:43.080 --> 00:04:45.950 align:start position:0% we need to make it Ultra safe right so that's<00:04:43.280> really<00:04:43.520> the<00:04:43.680> goal<00:04:44.000> here<00:04:44.800> so<00:04:45.039> with<00:04:45.240> that 00:04:45.950 --> 00:04:45.960 align:start position:0% that's really the goal here so with that 00:04:45.960 --> 00:04:48.350 align:start position:0% that's really the goal here so with that um<00:04:46.280> context<00:04:46.919> will'll<00:04:47.199> kick<00:04:47.400> it 00:04:48.350 --> 00:04:48.360 align:start position:0% um context will'll kick it 00:04:48.360 --> 00:04:51.390 align:start position:0% um context will'll kick it off<00:04:49.360> and<00:04:49.639> and<00:04:49.880> this<00:04:50.160> this<00:04:50.320> really<00:04:50.600> sort<00:04:50.840> of 00:04:51.390 --> 00:04:51.400 align:start position:0% off and and this this really sort of 00:04:51.400 --> 00:04:53.390 align:start position:0% off and and this this really sort of hopefully<00:04:52.080> justifies<00:04:52.680> it<00:04:52.919> right<00:04:53.039> I<00:04:53.120> mean<00:04:53.280> this 00:04:53.390 --> 00:04:53.400 align:start position:0% hopefully justifies it right I mean this 00:04:53.400 --> 00:04:57.110 align:start position:0% hopefully justifies it right I mean this is<00:04:53.880> from<00:04:54.320> defi<00:04:54.759> Lama<00:04:55.080> as<00:04:55.160> you<00:04:55.280> can<00:04:55.440> see<00:04:56.400> and<00:04:57.039> I 00:04:57.110 --> 00:04:57.120 align:start position:0% is from defi Lama as you can see and I 00:04:57.120 --> 00:04:58.230 align:start position:0% is from defi Lama as you can see and I don't<00:04:57.440> I<00:04:57.520> mean<00:04:57.680> this<00:04:57.759> is<00:04:57.919> probably 00:04:58.230 --> 00:04:58.240 align:start position:0% don't I mean this is probably 00:04:58.240 --> 00:04:59.749 align:start position:0% don't I mean this is probably representative<00:04:58.880> it<00:04:59.039> really<00:04:59.240> does<00:04:59.400> not 00:04:59.749 --> 00:04:59.759 align:start position:0% representative it really does not 00:04:59.759 --> 00:05:02.909 align:start position:0% representative it really does not capture<00:05:00.600> all<00:05:00.840> the<00:05:01.080> other<00:05:02.080> uh<00:05:02.280> fishing<00:05:02.759> and 00:05:02.909 --> 00:05:02.919 align:start position:0% capture all the other uh fishing and 00:05:02.919 --> 00:05:04.670 align:start position:0% capture all the other uh fishing and many<00:05:03.120> of<00:05:03.240> the<00:05:03.400> other<00:05:03.600> things<00:05:04.000> that<00:05:04.400> uh<00:05:04.520> are 00:05:04.670 --> 00:05:04.680 align:start position:0% many of the other things that uh are 00:05:04.680 --> 00:05:07.150 align:start position:0% many of the other things that uh are draining<00:05:05.160> millions<00:05:05.520> and<00:05:05.680> billions<00:05:06.639> so<00:05:07.000> this 00:05:07.150 --> 00:05:07.160 align:start position:0% draining millions and billions so this 00:05:07.160 --> 00:05:09.629 align:start position:0% draining millions and billions so this is<00:05:07.720> getting<00:05:08.039> better<00:05:08.400> I<00:05:08.479> mean<00:05:08.680> this<00:05:09.039> graph<00:05:09.440> sort 00:05:09.629 --> 00:05:09.639 align:start position:0% is getting better I mean this graph sort 00:05:09.639 --> 00:05:12.189 align:start position:0% is getting better I mean this graph sort of<00:05:10.400> gives<00:05:10.639> us<00:05:10.800> a<00:05:10.960> warm<00:05:11.240> fuzzy<00:05:11.600> feeling<00:05:12.000> that 00:05:12.189 --> 00:05:12.199 align:start position:0% of gives us a warm fuzzy feeling that 00:05:12.199 --> 00:05:14.390 align:start position:0% of gives us a warm fuzzy feeling that hey<00:05:12.600> we<00:05:12.720> may<00:05:12.880> be<00:05:13.000> getting<00:05:13.280> better<00:05:13.600> but<00:05:13.759> I<00:05:13.880> think 00:05:14.390 --> 00:05:14.400 align:start position:0% hey we may be getting better but I think 00:05:14.400 --> 00:05:17.510 align:start position:0% hey we may be getting better but I think we<00:05:14.600> really<00:05:14.840> have<00:05:15.000> a<00:05:15.440> you<00:05:15.560> know<00:05:16.320> long<00:05:16.840> long<00:05:17.160> path 00:05:17.510 --> 00:05:17.520 align:start position:0% we really have a you know long long path 00:05:17.520 --> 00:05:21.430 align:start position:0% we really have a you know long long path ahead<00:05:18.520> so<00:05:19.360> with<00:05:19.560> that<00:05:19.759> we'll<00:05:20.000> start<00:05:20.319> with<00:05:20.680> the 00:05:21.430 --> 00:05:21.440 align:start position:0% ahead so with that we'll start with the 00:05:21.440 --> 00:05:24.710 align:start position:0% ahead so with that we'll start with the tips<00:05:22.440> thank<00:05:23.080> you 00:05:24.710 --> 00:05:24.720 align:start position:0% tips thank you 00:05:24.720 --> 00:05:28.189 align:start position:0% tips thank you clicker<00:05:25.720> awesome<00:05:26.560> so<00:05:27.280> all<00:05:27.440> of<00:05:27.600> you<00:05:27.880> are 00:05:28.189 --> 00:05:28.199 align:start position:0% clicker awesome so all of you are 00:05:28.199 --> 00:05:30.550 align:start position:0% clicker awesome so all of you are probably<00:05:28.600> on<00:05:28.840> Twitter<00:05:29.479> uh<00:05:29.960> if<00:05:30.039> you're<00:05:30.240> not 00:05:30.550 --> 00:05:30.560 align:start position:0% probably on Twitter uh if you're not 00:05:30.560 --> 00:05:33.430 align:start position:0% probably on Twitter uh if you're not you're<00:05:31.400> quite<00:05:31.639> unique<00:05:32.600> and<00:05:32.840> if<00:05:33.000> you've<00:05:33.240> been 00:05:33.430 --> 00:05:33.440 align:start position:0% you're quite unique and if you've been 00:05:33.440 --> 00:05:36.469 align:start position:0% you're quite unique and if you've been on<00:05:33.680> Twitter<00:05:34.440> and<00:05:35.360> read<00:05:35.639> any<00:05:35.840> of<00:05:36.000> the<00:05:36.120> posts 00:05:36.469 --> 00:05:36.479 align:start position:0% on Twitter and read any of the posts 00:05:36.479 --> 00:05:39.430 align:start position:0% on Twitter and read any of the posts around<00:05:36.840> bounty<00:05:37.199> hunting<00:05:37.720> security<00:05:38.440> research 00:05:39.430 --> 00:05:39.440 align:start position:0% around bounty hunting security research 00:05:39.440 --> 00:05:43.309 align:start position:0% around bounty hunting security research uh<00:05:39.560> you<00:05:39.680> see<00:05:39.880> a<00:05:40.000> lot<00:05:40.160> of<00:05:40.840> grind<00:05:41.479> set<00:05:41.720> Focus<00:05:42.319> post 00:05:43.309 --> 00:05:43.319 align:start position:0% uh you see a lot of grind set Focus post 00:05:43.319 --> 00:05:46.469 align:start position:0% uh you see a lot of grind set Focus post and<00:05:44.319> um<00:05:45.120> I'm<00:05:45.240> not<00:05:45.479> saying<00:05:45.880> hard<00:05:46.120> work<00:05:46.319> and 00:05:46.469 --> 00:05:46.479 align:start position:0% and um I'm not saying hard work and 00:05:46.479 --> 00:05:48.510 align:start position:0% and um I'm not saying hard work and dedication<00:05:47.080> isn't<00:05:47.440> what's<00:05:47.800> going<00:05:48.240> like 00:05:48.510 --> 00:05:48.520 align:start position:0% dedication isn't what's going like 00:05:48.520 --> 00:05:50.150 align:start position:0% dedication isn't what's going like required<00:05:49.000> to<00:05:49.120> be<00:05:49.280> a<00:05:49.400> good<00:05:49.680> security 00:05:50.150 --> 00:05:50.160 align:start position:0% required to be a good security 00:05:50.160 --> 00:05:53.110 align:start position:0% required to be a good security researcher<00:05:51.039> but<00:05:51.199> I<00:05:51.360> honestly<00:05:51.880> believe<00:05:52.479> that 00:05:53.110 --> 00:05:53.120 align:start position:0% researcher but I honestly believe that 00:05:53.120 --> 00:05:55.230 align:start position:0% researcher but I honestly believe that going<00:05:53.400> into<00:05:53.840> security<00:05:54.319> research<00:05:54.919> with<00:05:55.080> the 00:05:55.230 --> 00:05:55.240 align:start position:0% going into security research with the 00:05:55.240 --> 00:05:57.670 align:start position:0% going into security research with the mindset<00:05:55.680> of<00:05:55.960> ah<00:05:56.120> I<00:05:56.199> need<00:05:56.360> to<00:05:56.520> grind<00:05:56.880> so<00:05:57.120> hard 00:05:57.670 --> 00:05:57.680 align:start position:0% mindset of ah I need to grind so hard 00:05:57.680 --> 00:06:00.590 align:start position:0% mindset of ah I need to grind so hard work<00:05:58.160> 16<00:05:58.600> hours<00:05:58.880> a<00:05:59.080> day<00:05:59.759> is<00:06:00.080> the<00:06:00.240> worst 00:06:00.590 --> 00:06:00.600 align:start position:0% work 16 hours a day is the worst 00:06:00.600 --> 00:06:03.350 align:start position:0% work 16 hours a day is the worst possible<00:06:01.080> approach<00:06:02.080> um<00:06:02.360> if<00:06:02.479> you<00:06:02.639> look<00:06:02.880> at 00:06:03.350 --> 00:06:03.360 align:start position:0% possible approach um if you look at 00:06:03.360 --> 00:06:06.670 align:start position:0% possible approach um if you look at other<00:06:03.600> Industries<00:06:04.360> like<00:06:04.880> doctors<00:06:05.880> um<00:06:06.360> that 00:06:06.670 --> 00:06:06.680 align:start position:0% other Industries like doctors um that 00:06:06.680 --> 00:06:08.430 align:start position:0% other Industries like doctors um that have<00:06:06.840> a<00:06:07.080> similar<00:06:07.440> kind<00:06:07.639> of<00:06:07.840> mindset<00:06:08.319> where 00:06:08.430 --> 00:06:08.440 align:start position:0% have a similar kind of mindset where 00:06:08.440 --> 00:06:09.909 align:start position:0% have a similar kind of mindset where it's<00:06:08.639> like<00:06:08.880> oh<00:06:09.039> I'm<00:06:09.120> going<00:06:09.240> to<00:06:09.360> work<00:06:09.560> so<00:06:09.720> many 00:06:09.909 --> 00:06:09.919 align:start position:0% it's like oh I'm going to work so many 00:06:09.919 --> 00:06:13.070 align:start position:0% it's like oh I'm going to work so many shifts<00:06:10.800> uh<00:06:11.120> I<00:06:11.280> work<00:06:11.520> so<00:06:11.759> hard<00:06:12.400> if<00:06:12.520> you<00:06:12.680> look<00:06:12.919> at 00:06:13.070 --> 00:06:13.080 align:start position:0% shifts uh I work so hard if you look at 00:06:13.080 --> 00:06:16.270 align:start position:0% shifts uh I work so hard if you look at the<00:06:13.240> amount<00:06:13.479> of<00:06:14.080> incidents<00:06:15.080> that<00:06:15.360> are<00:06:15.680> caused 00:06:16.270 --> 00:06:16.280 align:start position:0% the amount of incidents that are caused 00:06:16.280 --> 00:06:19.430 align:start position:0% the amount of incidents that are caused by<00:06:16.599> people<00:06:16.960> working<00:06:17.479> multiple<00:06:18.199> shifts<00:06:19.199> it's 00:06:19.430 --> 00:06:19.440 align:start position:0% by people working multiple shifts it's 00:06:19.440 --> 00:06:22.469 align:start position:0% by people working multiple shifts it's insane<00:06:20.400> uh<00:06:20.560> and<00:06:20.680> the<00:06:20.880> same<00:06:21.120> thing<00:06:21.360> happens<00:06:21.840> for 00:06:22.469 --> 00:06:22.479 align:start position:0% insane uh and the same thing happens for 00:06:22.479 --> 00:06:25.950 align:start position:0% insane uh and the same thing happens for security<00:06:23.000> research<00:06:23.880> like<00:06:24.400> I'll<00:06:25.400> be<00:06:25.560> stuck<00:06:25.840> on 00:06:25.950 --> 00:06:25.960 align:start position:0% security research like I'll be stuck on 00:06:25.960 --> 00:06:27.629 align:start position:0% security research like I'll be stuck on a<00:06:26.160> problem<00:06:26.400> for<00:06:26.599> four<00:06:26.840> hours<00:06:27.160> at<00:06:27.280> the<00:06:27.400> end<00:06:27.520> of 00:06:27.629 --> 00:06:27.639 align:start position:0% a problem for four hours at the end of 00:06:27.639 --> 00:06:30.350 align:start position:0% a problem for four hours at the end of the<00:06:27.840> day<00:06:28.639> and<00:06:29.160> the<00:06:29.319> next<00:06:29.680> morning<00:06:29.960> I'll<00:06:30.120> solve 00:06:30.350 --> 00:06:30.360 align:start position:0% the day and the next morning I'll solve 00:06:30.360 --> 00:06:33.230 align:start position:0% the day and the next morning I'll solve it<00:06:30.520> in<00:06:30.720> 5<00:06:30.919> minutes<00:06:31.639> like<00:06:32.240> staying<00:06:32.560> stuck<00:06:32.840> on<00:06:32.960> a 00:06:33.230 --> 00:06:33.240 align:start position:0% it in 5 minutes like staying stuck on a 00:06:33.240 --> 00:06:35.790 align:start position:0% it in 5 minutes like staying stuck on a problem<00:06:33.960> just<00:06:34.280> because<00:06:35.039> you<00:06:35.280> feel<00:06:35.560> like<00:06:35.680> you 00:06:35.790 --> 00:06:35.800 align:start position:0% problem just because you feel like you 00:06:35.800 --> 00:06:38.670 align:start position:0% problem just because you feel like you need<00:06:35.960> to<00:06:36.120> work<00:06:36.400> hard<00:06:37.120> not<00:06:37.280> a<00:06:37.400> good 00:06:38.670 --> 00:06:38.680 align:start position:0% need to work hard not a good 00:06:38.680 --> 00:06:41.990 align:start position:0% need to work hard not a good approach<00:06:39.680> okay<00:06:40.319> tip<00:06:40.560> two<00:06:41.319> scoping<00:06:41.759> out 00:06:41.990 --> 00:06:42.000 align:start position:0% approach okay tip two scoping out 00:06:42.000 --> 00:06:44.670 align:start position:0% approach okay tip two scoping out targets<00:06:43.000> and<00:06:43.280> not<00:06:43.560> just<00:06:43.800> picking<00:06:44.160> anyone<00:06:44.479> at 00:06:44.670 --> 00:06:44.680 align:start position:0% targets and not just picking anyone at 00:06:44.680 --> 00:06:47.589 align:start position:0% targets and not just picking anyone at random<00:06:45.400> is<00:06:45.639> a<00:06:45.800> pretty<00:06:46.080> good<00:06:46.319> idea<00:06:46.960> when<00:06:47.280> you're 00:06:47.589 --> 00:06:47.599 align:start position:0% random is a pretty good idea when you're 00:06:47.599 --> 00:06:49.749 align:start position:0% random is a pretty good idea when you're doing<00:06:47.880> bounty<00:06:48.240> hunting<00:06:48.840> there's<00:06:49.199> so<00:06:49.440> many 00:06:49.749 --> 00:06:49.759 align:start position:0% doing bounty hunting there's so many 00:06:49.759 --> 00:06:52.390 align:start position:0% doing bounty hunting there's so many programs<00:06:50.599> and<00:06:51.000> if<00:06:51.080> you<00:06:51.360> just<00:06:51.800> pick<00:06:52.039> one<00:06:52.199> at 00:06:52.390 --> 00:06:52.400 align:start position:0% programs and if you just pick one at 00:06:52.400 --> 00:06:54.550 align:start position:0% programs and if you just pick one at random<00:06:53.240> well<00:06:53.360> it<00:06:53.479> can<00:06:53.639> be<00:06:53.759> a<00:06:53.840> fun<00:06:54.080> approach<00:06:54.440> but 00:06:54.550 --> 00:06:54.560 align:start position:0% random well it can be a fun approach but 00:06:54.560 --> 00:06:57.710 align:start position:0% random well it can be a fun approach but it's<00:06:54.840> probably<00:06:55.160> not<00:06:55.400> that<00:06:55.919> efficient<00:06:56.919> so 00:06:57.710 --> 00:06:57.720 align:start position:0% it's probably not that efficient so 00:06:57.720 --> 00:06:59.270 align:start position:0% it's probably not that efficient so probably<00:06:58.120> the<00:06:58.360> primary<00:06:58.800> thing<00:06:59.000> you<00:06:59.080> should 00:06:59.270 --> 00:06:59.280 align:start position:0% probably the primary thing you should 00:06:59.280 --> 00:07:01.110 align:start position:0% probably the primary thing you should FOC<00:06:59.599> focus<00:06:59.879> on<00:07:00.080> is<00:07:00.199> the<00:07:00.360> amount<00:07:00.560> of<00:07:00.720> time<00:07:01.000> that 00:07:01.110 --> 00:07:01.120 align:start position:0% FOC focus on is the amount of time that 00:07:01.120 --> 00:07:03.990 align:start position:0% FOC focus on is the amount of time that you<00:07:01.280> have<00:07:01.520> available<00:07:02.520> closer<00:07:03.120> okay<00:07:03.800> uh 00:07:03.990 --> 00:07:04.000 align:start position:0% you have available closer okay uh 00:07:04.000 --> 00:07:05.550 align:start position:0% you have available closer okay uh probably<00:07:04.400> what<00:07:04.479> you<00:07:04.599> need<00:07:04.720> to<00:07:04.879> focus<00:07:05.160> on<00:07:05.440> is 00:07:05.550 --> 00:07:05.560 align:start position:0% probably what you need to focus on is 00:07:05.560 --> 00:07:06.790 align:start position:0% probably what you need to focus on is the<00:07:05.720> amount<00:07:05.919> of<00:07:06.080> time<00:07:06.360> that<00:07:06.440> you<00:07:06.599> have 00:07:06.790 --> 00:07:06.800 align:start position:0% the amount of time that you have 00:07:06.800 --> 00:07:10.230 align:start position:0% the amount of time that you have available<00:07:07.280> on<00:07:07.639> these<00:07:07.879> targets<00:07:08.840> so<00:07:09.759> uh<00:07:09.960> maybe 00:07:10.230 --> 00:07:10.240 align:start position:0% available on these targets so uh maybe 00:07:10.240 --> 00:07:12.070 align:start position:0% available on these targets so uh maybe don't<00:07:10.520> go<00:07:10.720> for<00:07:11.000> like<00:07:11.160> a<00:07:11.319> bridge 00:07:12.070 --> 00:07:12.080 align:start position:0% don't go for like a bridge 00:07:12.080 --> 00:07:16.990 align:start position:0% don't go for like a bridge implementation<00:07:13.120> or<00:07:14.120> uh<00:07:14.720> like<00:07:15.000> a<00:07:15.280> an<00:07:15.720> L2<00:07:16.720> if<00:07:16.840> you 00:07:16.990 --> 00:07:17.000 align:start position:0% implementation or uh like a an L2 if you 00:07:17.000 --> 00:07:19.869 align:start position:0% implementation or uh like a an L2 if you just<00:07:17.199> have<00:07:17.360> a<00:07:17.599> weekend<00:07:18.599> um<00:07:19.039> and<00:07:19.199> of<00:07:19.400> course 00:07:19.869 --> 00:07:19.879 align:start position:0% just have a weekend um and of course 00:07:19.879 --> 00:07:21.990 align:start position:0% just have a weekend um and of course like<00:07:20.280> if<00:07:20.400> you're<00:07:20.680> looking<00:07:21.039> to<00:07:21.440> make<00:07:21.599> a<00:07:21.720> living 00:07:21.990 --> 00:07:22.000 align:start position:0% like if you're looking to make a living 00:07:22.000 --> 00:07:24.629 align:start position:0% like if you're looking to make a living out<00:07:22.199> of<00:07:22.400> this<00:07:22.639> or<00:07:23.440> a<00:07:23.599> significant<00:07:24.280> amount<00:07:24.520> of 00:07:24.629 --> 00:07:24.639 align:start position:0% out of this or a significant amount of 00:07:24.639 --> 00:07:27.990 align:start position:0% out of this or a significant amount of money<00:07:25.160> then<00:07:25.960> don't<00:07:26.280> go<00:07:26.560> for<00:07:26.879> projects<00:07:27.599> that 00:07:27.990 --> 00:07:28.000 align:start position:0% money then don't go for projects that 00:07:28.000 --> 00:07:30.550 align:start position:0% money then don't go for projects that offer<00:07:28.440> low<00:07:28.759> bounties<00:07:29.639> one<00:07:29.800> thing<00:07:30.080> I<00:07:30.280> actually 00:07:30.550 --> 00:07:30.560 align:start position:0% offer low bounties one thing I actually 00:07:30.560 --> 00:07:32.909 align:start position:0% offer low bounties one thing I actually look<00:07:30.800> at<00:07:31.000> a<00:07:31.160> lot<00:07:31.720> is<00:07:31.919> not<00:07:32.199> necessarily<00:07:32.759> the 00:07:32.909 --> 00:07:32.919 align:start position:0% look at a lot is not necessarily the 00:07:32.919 --> 00:07:35.510 align:start position:0% look at a lot is not necessarily the height<00:07:33.400> of<00:07:33.520> the<00:07:33.680> main<00:07:34.000> Bounty<00:07:34.479> which<00:07:34.599> is<00:07:34.919> like 00:07:35.510 --> 00:07:35.520 align:start position:0% height of the main Bounty which is like 00:07:35.520 --> 00:07:37.830 align:start position:0% height of the main Bounty which is like 10<00:07:35.840> million<00:07:36.240> or<00:07:36.400> one<00:07:36.639> million<00:07:37.160> it's<00:07:37.319> usually 00:07:37.830 --> 00:07:37.840 align:start position:0% 10 million or one million it's usually 00:07:37.840 --> 00:07:41.150 align:start position:0% 10 million or one million it's usually very<00:07:38.120> high<00:07:38.680> I<00:07:38.840> look<00:07:39.000> at<00:07:39.280> the<00:07:39.879> the<00:07:40.400> the<00:07:40.599> Bounty 00:07:41.150 --> 00:07:41.160 align:start position:0% very high I look at the the the Bounty 00:07:41.160 --> 00:07:42.749 align:start position:0% very high I look at the the the Bounty that's<00:07:41.400> offered<00:07:41.800> for<00:07:42.000> the<00:07:42.199> high 00:07:42.749 --> 00:07:42.759 align:start position:0% that's offered for the high 00:07:42.759 --> 00:07:45.110 align:start position:0% that's offered for the high vulnerability<00:07:43.759> because<00:07:44.000> that's<00:07:44.319> usually<00:07:44.759> a 00:07:45.110 --> 00:07:45.120 align:start position:0% vulnerability because that's usually a 00:07:45.120 --> 00:07:47.510 align:start position:0% vulnerability because that's usually a really<00:07:45.479> good<00:07:45.639> signal<00:07:46.280> about<00:07:46.879> how<00:07:47.080> much<00:07:47.280> a 00:07:47.510 --> 00:07:47.520 align:start position:0% really good signal about how much a 00:07:47.520 --> 00:07:50.029 align:start position:0% really good signal about how much a project<00:07:48.000> actually<00:07:48.360> cares<00:07:48.680> about<00:07:48.960> security<00:07:49.879> if 00:07:50.029 --> 00:07:50.039 align:start position:0% project actually cares about security if 00:07:50.039 --> 00:07:52.469 align:start position:0% project actually cares about security if they<00:07:50.159> won't<00:07:50.440> offer<00:07:50.759> anything<00:07:51.120> for<00:07:51.400> highs<00:07:52.240> or 00:07:52.469 --> 00:07:52.479 align:start position:0% they won't offer anything for highs or 00:07:52.479 --> 00:07:55.950 align:start position:0% they won't offer anything for highs or if<00:07:52.680> their<00:07:52.960> high<00:07:53.199> is<00:07:53.479> like<00:07:54.039> 10K<00:07:54.960> and<00:07:55.159> their<00:07:55.440> crit 00:07:55.950 --> 00:07:55.960 align:start position:0% if their high is like 10K and their crit 00:07:55.960 --> 00:07:59.589 align:start position:0% if their high is like 10K and their crit is<00:07:56.159> 10<00:07:56.599> million<00:07:57.599> um<00:07:58.000> this<00:07:58.120> is<00:07:58.360> just<00:07:58.759> like 00:07:59.589 --> 00:07:59.599 align:start position:0% is 10 million um this is just like 00:07:59.599 --> 00:08:01.189 align:start position:0% is 10 million um this is just like random 00:08:01.189 --> 00:08:01.199 align:start position:0% random 00:08:01.199 --> 00:08:03.909 align:start position:0% random um<00:08:02.199> that's<00:08:02.800> not<00:08:02.960> a<00:08:03.120> good<00:08:03.280> sign<00:08:03.560> that<00:08:03.720> they 00:08:03.909 --> 00:08:03.919 align:start position:0% um that's not a good sign that they 00:08:03.919 --> 00:08:05.869 align:start position:0% um that's not a good sign that they actually<00:08:04.199> care<00:08:04.440> about<00:08:04.720> security<00:08:05.599> uh<00:08:05.720> they 00:08:05.869 --> 00:08:05.879 align:start position:0% actually care about security uh they 00:08:05.879 --> 00:08:09.950 align:start position:0% actually care about security uh they just<00:08:06.080> wna<00:08:06.919> yeah<00:08:07.199> prevent<00:08:07.720> the<00:08:07.919> main 00:08:09.950 --> 00:08:09.960 align:start position:0% just wna yeah prevent the main 00:08:09.960 --> 00:08:13.830 align:start position:0% just wna yeah prevent the main things<00:08:10.960> okay<00:08:11.800> tip<00:08:12.080> three<00:08:12.479> try<00:08:12.800> to<00:08:12.960> sleep<00:08:13.440> sort 00:08:13.830 --> 00:08:13.840 align:start position:0% things okay tip three try to sleep sort 00:08:13.840 --> 00:08:16.950 align:start position:0% things okay tip three try to sleep sort up<00:08:14.599> okay<00:08:15.199> so<00:08:15.479> this<00:08:15.639> one<00:08:16.120> actually<00:08:16.479> happened<00:08:16.800> to 00:08:16.950 --> 00:08:16.960 align:start position:0% up okay so this one actually happened to 00:08:16.960 --> 00:08:21.869 align:start position:0% up okay so this one actually happened to me<00:08:17.879> uh<00:08:18.080> I<00:08:18.159> was<00:08:18.280> trying<00:08:18.599> to<00:08:18.840> sleep<00:08:19.840> uh<00:08:20.159> and<00:08:20.520> then 00:08:21.869 --> 00:08:21.879 align:start position:0% me uh I was trying to sleep uh and then 00:08:21.879 --> 00:08:25.270 align:start position:0% me uh I was trying to sleep uh and then well<00:08:22.879> as<00:08:23.360> as<00:08:23.520> it<00:08:23.680> happens<00:08:24.039> my<00:08:24.159> brain<00:08:24.400> is<00:08:24.599> like 00:08:25.270 --> 00:08:25.280 align:start position:0% well as as it happens my brain is like 00:08:25.280 --> 00:08:27.390 align:start position:0% well as as it happens my brain is like oh<00:08:25.599> you<00:08:25.720> were<00:08:25.960> working<00:08:26.280> on<00:08:26.520> this<00:08:26.840> problem 00:08:27.390 --> 00:08:27.400 align:start position:0% oh you were working on this problem 00:08:27.400 --> 00:08:29.790 align:start position:0% oh you were working on this problem here's<00:08:27.639> the<00:08:27.840> solution<00:08:28.800> and<00:08:28.919> so<00:08:29.159> there<00:08:29.560> was 00:08:29.790 --> 00:08:29.800 align:start position:0% here's the solution and so there was 00:08:29.800 --> 00:08:31.390 align:start position:0% here's the solution and so there was like<00:08:29.960> in<00:08:30.039> the<00:08:30.120> middle<00:08:30.360> of<00:08:30.440> the<00:08:30.599> night<00:08:31.039> typing 00:08:31.390 --> 00:08:31.400 align:start position:0% like in the middle of the night typing 00:08:31.400 --> 00:08:34.389 align:start position:0% like in the middle of the night typing up<00:08:31.560> a<00:08:31.680> bug<00:08:32.200> report 00:08:34.389 --> 00:08:34.399 align:start position:0% up a bug report 00:08:34.399 --> 00:08:37.310 align:start position:0% up a bug report um<00:08:35.399> the<00:08:35.560> idea<00:08:35.919> here<00:08:36.120> is<00:08:36.279> not<00:08:36.519> to<00:08:36.719> try<00:08:36.919> to<00:08:37.039> work 00:08:37.310 --> 00:08:37.320 align:start position:0% um the idea here is not to try to work 00:08:37.320 --> 00:08:40.149 align:start position:0% um the idea here is not to try to work well<00:08:37.560> you're<00:08:37.719> trying<00:08:38.000> to<00:08:38.159> sleep<00:08:38.760> it's<00:08:38.959> more<00:08:39.240> so 00:08:40.149 --> 00:08:40.159 align:start position:0% well you're trying to sleep it's more so 00:08:40.159 --> 00:08:43.230 align:start position:0% well you're trying to sleep it's more so um<00:08:40.519> exploiting<00:08:41.120> the<00:08:41.320> idea<00:08:42.039> that<00:08:42.399> you<00:08:42.680> have 00:08:43.230 --> 00:08:43.240 align:start position:0% um exploiting the idea that you have 00:08:43.240 --> 00:08:44.670 align:start position:0% um exploiting the idea that you have like<00:08:43.399> your<00:08:43.519> brain<00:08:43.800> is<00:08:43.919> doing<00:08:44.240> passive 00:08:44.670 --> 00:08:44.680 align:start position:0% like your brain is doing passive 00:08:44.680 --> 00:08:47.710 align:start position:0% like your brain is doing passive processing<00:08:45.680> on<00:08:46.200> in<00:08:47.040> while<00:08:47.160> you're<00:08:47.320> doing 00:08:47.710 --> 00:08:47.720 align:start position:0% processing on in while you're doing 00:08:47.720 --> 00:08:49.470 align:start position:0% processing on in while you're doing random<00:08:48.120> things<00:08:48.399> like<00:08:48.519> trying<00:08:48.800> to<00:08:48.959> sleep<00:08:49.279> or 00:08:49.470 --> 00:08:49.480 align:start position:0% random things like trying to sleep or 00:08:49.480 --> 00:08:53.750 align:start position:0% random things like trying to sleep or doing<00:08:49.680> the<00:08:50.360> dishes<00:08:51.600> um<00:08:52.600> and<00:08:53.120> to<00:08:53.519> really 00:08:53.750 --> 00:08:53.760 align:start position:0% doing the dishes um and to really 00:08:53.760 --> 00:08:55.910 align:start position:0% doing the dishes um and to really leverage<00:08:54.279> that<00:08:54.519> it's<00:08:54.720> important<00:08:55.160> to<00:08:55.440> not<00:08:55.720> try 00:08:55.910 --> 00:08:55.920 align:start position:0% leverage that it's important to not try 00:08:55.920 --> 00:08:58.389 align:start position:0% leverage that it's important to not try to<00:08:56.080> do<00:08:56.320> too<00:08:56.519> many<00:08:56.800> things<00:08:57.040> at<00:08:57.200> the<00:08:57.320> same<00:08:57.600> time 00:08:58.389 --> 00:08:58.399 align:start position:0% to do too many things at the same time 00:08:58.399 --> 00:09:01.150 align:start position:0% to do too many things at the same time because<00:08:58.800> so<00:08:59.519> for<00:08:59.760> example<00:09:00.480> if<00:09:00.600> you're<00:09:00.760> bounty 00:09:01.150 --> 00:09:01.160 align:start position:0% because so for example if you're bounty 00:09:01.160 --> 00:09:03.470 align:start position:0% because so for example if you're bounty hunting<00:09:01.440> on<00:09:01.560> a<00:09:01.800> project<00:09:02.519> don't<00:09:02.800> switch<00:09:03.120> to<00:09:03.320> a 00:09:03.470 --> 00:09:03.480 align:start position:0% hunting on a project don't switch to a 00:09:03.480 --> 00:09:06.509 align:start position:0% hunting on a project don't switch to a different<00:09:03.880> project<00:09:04.839> just<00:09:05.839> keep<00:09:06.040> doing<00:09:06.360> this 00:09:06.509 --> 00:09:06.519 align:start position:0% different project just keep doing this 00:09:06.519 --> 00:09:10.110 align:start position:0% different project just keep doing this one<00:09:06.920> go<00:09:07.120> for<00:09:07.360> a<00:09:07.560> walk<00:09:08.120> let<00:09:08.320> it<00:09:08.959> process<00:09:09.959> and 00:09:10.110 --> 00:09:10.120 align:start position:0% one go for a walk let it process and 00:09:10.120 --> 00:09:14.150 align:start position:0% one go for a walk let it process and find<00:09:10.360> some<00:09:10.560> bugs<00:09:11.560> um<00:09:12.480> and<00:09:12.920> don't<00:09:13.279> go<00:09:13.680> like 00:09:14.150 --> 00:09:14.160 align:start position:0% find some bugs um and don't go like 00:09:14.160 --> 00:09:16.150 align:start position:0% find some bugs um and don't go like watch<00:09:14.440> Netflix<00:09:14.959> and<00:09:15.120> fill<00:09:15.440> your<00:09:15.640> head<00:09:15.880> with 00:09:16.150 --> 00:09:16.160 align:start position:0% watch Netflix and fill your head with 00:09:16.160 --> 00:09:18.550 align:start position:0% watch Netflix and fill your head with different<00:09:16.480> things<00:09:17.200> because<00:09:17.519> then<00:09:17.720> you<00:09:17.920> can't 00:09:18.550 --> 00:09:18.560 align:start position:0% different things because then you can't 00:09:18.560 --> 00:09:19.350 align:start position:0% different things because then you can't like 00:09:19.350 --> 00:09:19.360 align:start position:0% like 00:09:19.360 --> 00:09:22.150 align:start position:0% like Leverage<00:09:20.360> this<00:09:20.640> ability<00:09:21.000> of<00:09:21.120> your<00:09:21.279> brain<00:09:21.800> like 00:09:22.150 --> 00:09:22.160 align:start position:0% Leverage this ability of your brain like 00:09:22.160 --> 00:09:24.829 align:start position:0% Leverage this ability of your brain like um<00:09:22.600> I<00:09:22.680> have<00:09:22.800> a<00:09:23.120> cool<00:09:23.440> example<00:09:24.040> from<00:09:24.480> when<00:09:24.600> I<00:09:24.720> was 00:09:24.829 --> 00:09:24.839 align:start position:0% um I have a cool example from when I was 00:09:24.839 --> 00:09:28.069 align:start position:0% um I have a cool example from when I was in<00:09:25.240> university<00:09:26.240> um<00:09:26.880> was<00:09:27.120> working<00:09:27.600> really<00:09:27.880> hard 00:09:28.069 --> 00:09:28.079 align:start position:0% in university um was working really hard 00:09:28.079 --> 00:09:31.630 align:start position:0% in university um was working really hard on<00:09:28.200> a<00:09:28.480> problem<00:09:29.240> uh<00:09:29.720> like<00:09:30.519> the<00:09:31.040> we<00:09:31.200> had<00:09:31.440> these 00:09:31.630 --> 00:09:31.640 align:start position:0% on a problem uh like the we had these 00:09:31.640 --> 00:09:33.389 align:start position:0% on a problem uh like the we had these days<00:09:31.920> where<00:09:32.079> you<00:09:32.200> had<00:09:32.320> to<00:09:32.480> solve<00:09:32.839> a<00:09:33.200> a 00:09:33.389 --> 00:09:33.399 align:start position:0% days where you had to solve a a 00:09:33.399 --> 00:09:36.670 align:start position:0% days where you had to solve a a challenge<00:09:33.760> in<00:09:33.880> a<00:09:34.079> day<00:09:34.880> uh<00:09:35.240> kind<00:09:35.360> of<00:09:35.680> hackathon 00:09:36.670 --> 00:09:36.680 align:start position:0% challenge in a day uh kind of hackathon 00:09:36.680 --> 00:09:38.910 align:start position:0% challenge in a day uh kind of hackathon um<00:09:36.959> and<00:09:37.079> it<00:09:37.160> was<00:09:37.519> like<00:09:37.680> super<00:09:37.959> stuck<00:09:38.360> for<00:09:38.800> like 00:09:38.910 --> 00:09:38.920 align:start position:0% um and it was like super stuck for like 00:09:38.920 --> 00:09:41.389 align:start position:0% um and it was like super stuck for like the<00:09:39.040> first<00:09:39.240> four<00:09:39.480> hours<00:09:39.720> of<00:09:39.920> the<00:09:40.160> day<00:09:40.959> um<00:09:41.200> took 00:09:41.389 --> 00:09:41.399 align:start position:0% the first four hours of the day um took 00:09:41.399 --> 00:09:44.230 align:start position:0% the first four hours of the day um took a<00:09:41.600> walk<00:09:41.880> to<00:09:42.040> get<00:09:42.279> lunch<00:09:43.279> passive<00:09:43.720> processing 00:09:44.230 --> 00:09:44.240 align:start position:0% a walk to get lunch passive processing 00:09:44.240 --> 00:09:46.790 align:start position:0% a walk to get lunch passive processing happened<00:09:44.880> solved<00:09:45.240> the<00:09:45.440> issue<00:09:45.959> like<00:09:46.600> right 00:09:46.790 --> 00:09:46.800 align:start position:0% happened solved the issue like right 00:09:46.800 --> 00:09:50.430 align:start position:0% happened solved the issue like right after<00:09:47.240> lunch<00:09:48.240> so<00:09:48.720> yeah<00:09:48.959> till<00:09:49.320> the<00:09:49.480> year<00:09:50.200> take 00:09:50.430 --> 00:09:50.440 align:start position:0% after lunch so yeah till the year take 00:09:50.440 --> 00:09:55.150 align:start position:0% after lunch so yeah till the year take some<00:09:50.640> breaks<00:09:51.640> uh<00:09:52.440> and<00:09:52.640> leverage<00:09:53.120> this<00:09:53.360> passive 00:09:55.150 --> 00:09:55.160 align:start position:0% some breaks uh and leverage this passive 00:09:55.160 --> 00:09:58.430 align:start position:0% some breaks uh and leverage this passive processing<00:09:56.160> okay<00:09:56.880> now<00:09:57.279> some<00:09:57.560> tips<00:09:57.920> about<00:09:58.279> how 00:09:58.430 --> 00:09:58.440 align:start position:0% processing okay now some tips about how 00:09:58.440 --> 00:10:01.069 align:start position:0% processing okay now some tips about how to<00:09:58.640> approach<00:09:59.360> bug<00:09:59.519> Bounty 00:10:01.069 --> 00:10:01.079 align:start position:0% to approach bug Bounty 00:10:01.079 --> 00:10:02.829 align:start position:0% to approach bug Bounty discussions<00:10:02.079> if<00:10:02.200> you're<00:10:02.360> doing<00:10:02.600> Buck 00:10:02.829 --> 00:10:02.839 align:start position:0% discussions if you're doing Buck 00:10:02.839 --> 00:10:04.870 align:start position:0% discussions if you're doing Buck bounties<00:10:03.720> eventually<00:10:04.320> you'll<00:10:04.600> have<00:10:04.720> a 00:10:04.870 --> 00:10:04.880 align:start position:0% bounties eventually you'll have a 00:10:04.880 --> 00:10:07.910 align:start position:0% bounties eventually you'll have a discussion<00:10:05.320> with<00:10:05.480> someone<00:10:06.320> because<00:10:06.959> projects 00:10:07.910 --> 00:10:07.920 align:start position:0% discussion with someone because projects 00:10:07.920 --> 00:10:10.870 align:start position:0% discussion with someone because projects don't<00:10:08.240> always<00:10:08.600> agree<00:10:09.480> with<00:10:09.800> the<00:10:10.000> impact<00:10:10.600> or 00:10:10.870 --> 00:10:10.880 align:start position:0% don't always agree with the impact or 00:10:10.880 --> 00:10:14.350 align:start position:0% don't always agree with the impact or what<00:10:11.000> you<00:10:11.640> found<00:10:12.640> um<00:10:13.240> Everybody<00:10:13.800> responds 00:10:14.350 --> 00:10:14.360 align:start position:0% what you found um Everybody responds 00:10:14.360 --> 00:10:16.590 align:start position:0% what you found um Everybody responds differently<00:10:15.360> uh<00:10:15.519> there<00:10:15.640> can<00:10:15.800> be<00:10:16.200> some 00:10:16.590 --> 00:10:16.600 align:start position:0% differently uh there can be some 00:10:16.600 --> 00:10:18.590 align:start position:0% differently uh there can be some emotions<00:10:17.160> involved<00:10:17.560> when<00:10:17.720> you<00:10:17.839> tell<00:10:18.120> someone 00:10:18.590 --> 00:10:18.600 align:start position:0% emotions involved when you tell someone 00:10:18.600 --> 00:10:21.990 align:start position:0% emotions involved when you tell someone their<00:10:18.800> code<00:10:19.000> is<00:10:19.519> broken<00:10:20.519> um<00:10:21.200> so<00:10:21.560> one<00:10:21.680> of<00:10:21.880> the 00:10:21.990 --> 00:10:22.000 align:start position:0% their code is broken um so one of the 00:10:22.000 --> 00:10:24.030 align:start position:0% their code is broken um so one of the things<00:10:22.240> that's<00:10:22.480> really<00:10:22.720> useful<00:10:23.360> is<00:10:23.560> basically 00:10:24.030 --> 00:10:24.040 align:start position:0% things that's really useful is basically 00:10:24.040 --> 00:10:26.269 align:start position:0% things that's really useful is basically learning<00:10:24.399> a<00:10:24.519> little<00:10:24.720> bit<00:10:24.880> of<00:10:25.160> rhetorics<00:10:26.000> and 00:10:26.269 --> 00:10:26.279 align:start position:0% learning a little bit of rhetorics and 00:10:26.279 --> 00:10:29.870 align:start position:0% learning a little bit of rhetorics and preparing<00:10:26.680> for<00:10:27.240> fallacies<00:10:28.320> um<00:10:29.399> people<00:10:29.640> will 00:10:29.870 --> 00:10:29.880 align:start position:0% preparing for fallacies um people will 00:10:29.880 --> 00:10:31.990 align:start position:0% preparing for fallacies um people will come<00:10:30.040> up<00:10:30.240> with<00:10:30.399> arguments<00:10:30.839> that<00:10:31.000> don't<00:10:31.240> work 00:10:31.990 --> 00:10:32.000 align:start position:0% come up with arguments that don't work 00:10:32.000 --> 00:10:35.030 align:start position:0% come up with arguments that don't work addressing<00:10:32.560> them<00:10:32.800> or<00:10:33.640> strategies<00:10:34.480> that 00:10:35.030 --> 00:10:35.040 align:start position:0% addressing them or strategies that 00:10:35.040 --> 00:10:37.509 align:start position:0% addressing them or strategies that basically<00:10:35.480> derail<00:10:35.920> a<00:10:36.279> discussion<00:10:37.279> being 00:10:37.509 --> 00:10:37.519 align:start position:0% basically derail a discussion being 00:10:37.519 --> 00:10:39.590 align:start position:0% basically derail a discussion being prepared<00:10:37.880> for<00:10:38.079> them<00:10:38.279> will<00:10:38.560> just<00:10:39.240> make<00:10:39.399> your 00:10:39.590 --> 00:10:39.600 align:start position:0% prepared for them will just make your 00:10:39.600 --> 00:10:41.829 align:start position:0% prepared for them will just make your life<00:10:39.839> easier<00:10:40.200> in<00:10:40.320> the 00:10:41.829 --> 00:10:41.839 align:start position:0% life easier in the 00:10:41.839 --> 00:10:44.389 align:start position:0% life easier in the end<00:10:42.839> another<00:10:43.279> tip<00:10:43.560> on<00:10:43.760> Buck<00:10:44.000> Bounty 00:10:44.389 --> 00:10:44.399 align:start position:0% end another tip on Buck Bounty 00:10:44.399 --> 00:10:46.310 align:start position:0% end another tip on Buck Bounty discussions<00:10:45.040> is<00:10:45.639> kind<00:10:45.760> of<00:10:45.920> taking<00:10:46.160> the 00:10:46.310 --> 00:10:46.320 align:start position:0% discussions is kind of taking the 00:10:46.320 --> 00:10:48.509 align:start position:0% discussions is kind of taking the mindset<00:10:46.720> of<00:10:46.920> working<00:10:47.560> with<00:10:47.760> this<00:10:48.040> project<00:10:48.399> as 00:10:48.509 --> 00:10:48.519 align:start position:0% mindset of working with this project as 00:10:48.519 --> 00:10:50.230 align:start position:0% mindset of working with this project as a<00:10:48.680> business<00:10:49.040> partner<00:10:49.639> that<00:10:49.760> you<00:10:49.920> might<00:10:50.079> want 00:10:50.230 --> 00:10:50.240 align:start position:0% a business partner that you might want 00:10:50.240 --> 00:10:54.629 align:start position:0% a business partner that you might want to<00:10:50.360> do<00:10:50.519> an<00:10:50.639> audit<00:10:51.279> with<00:10:52.279> uh<00:10:52.800> later<00:10:53.800> um<00:10:54.160> this 00:10:54.629 --> 00:10:54.639 align:start position:0% to do an audit with uh later um this 00:10:54.639 --> 00:10:56.949 align:start position:0% to do an audit with uh later um this greatest<00:10:55.079> s<00:10:55.440> communication<00:10:56.079> that's<00:10:56.680> that's 00:10:56.949 --> 00:10:56.959 align:start position:0% greatest s communication that's that's 00:10:56.959 --> 00:10:59.430 align:start position:0% greatest s communication that's that's much<00:10:57.200> more<00:10:57.480> productive<00:10:58.360> and<00:10:58.680> much<00:10:58.959> less 00:10:59.430 --> 00:10:59.440 align:start position:0% much more productive and much less 00:10:59.440 --> 00:11:01.310 align:start position:0% much more productive and much less likely<00:10:59.800> to<00:11:00.000> result<00:11:00.360> in<00:11:00.480> a<00:11:00.680> situation<00:11:01.160> where 00:11:01.310 --> 00:11:01.320 align:start position:0% likely to result in a situation where 00:11:01.320 --> 00:11:03.629 align:start position:0% likely to result in a situation where you're<00:11:01.760> just<00:11:01.959> name<00:11:02.399> calling<00:11:02.800> like<00:11:03.160> no<00:11:03.399> your 00:11:03.629 --> 00:11:03.639 align:start position:0% you're just name calling like no your 00:11:03.639 --> 00:11:05.750 align:start position:0% you're just name calling like no your code<00:11:03.880> is<00:11:04.480> and<00:11:04.600> then<00:11:04.760> they're<00:11:04.920> saying<00:11:05.360> no 00:11:05.750 --> 00:11:05.760 align:start position:0% code is and then they're saying no 00:11:05.760 --> 00:11:08.590 align:start position:0% code is and then they're saying no you<00:11:05.920> can't<00:11:06.320> find<00:11:06.600> bugs<00:11:07.000> and<00:11:07.279> everything<00:11:07.680> sucks 00:11:08.590 --> 00:11:08.600 align:start position:0% you can't find bugs and everything sucks 00:11:08.600 --> 00:11:11.509 align:start position:0% you can't find bugs and everything sucks um<00:11:08.760> so<00:11:09.000> this<00:11:09.320> really<00:11:10.320> uh<00:11:10.720> helps<00:11:11.000> things<00:11:11.240> out 00:11:11.509 --> 00:11:11.519 align:start position:0% um so this really uh helps things out 00:11:11.519 --> 00:11:14.389 align:start position:0% um so this really uh helps things out there<00:11:12.120> and<00:11:12.959> as<00:11:13.120> an<00:11:13.320> at<00:11:13.519> a<00:11:13.680> benefit<00:11:14.120> if<00:11:14.240> you 00:11:14.389 --> 00:11:14.399 align:start position:0% there and as an at a benefit if you 00:11:14.399 --> 00:11:15.829 align:start position:0% there and as an at a benefit if you actually<00:11:14.680> do<00:11:14.880> end<00:11:15.040> up<00:11:15.320> buiness<00:11:15.600> being 00:11:15.829 --> 00:11:15.839 align:start position:0% actually do end up buiness being 00:11:15.839 --> 00:11:18.629 align:start position:0% actually do end up buiness being business<00:11:16.240> marter<00:11:16.600> laser<00:11:17.560> uh<00:11:17.720> you<00:11:17.920> have<00:11:18.079> a<00:11:18.320> much 00:11:18.629 --> 00:11:18.639 align:start position:0% business marter laser uh you have a much 00:11:18.639 --> 00:11:20.310 align:start position:0% business marter laser uh you have a much much<00:11:18.880> better 00:11:20.310 --> 00:11:20.320 align:start position:0% much better 00:11:20.320 --> 00:11:24.230 align:start position:0% much better relationship<00:11:21.399> okay<00:11:22.399> then<00:11:23.399> um<00:11:23.839> it's<00:11:23.959> going<00:11:24.079> to 00:11:24.230 --> 00:11:24.240 align:start position:0% relationship okay then um it's going to 00:11:24.240 --> 00:11:27.269 align:start position:0% relationship okay then um it's going to be<00:11:24.440> super<00:11:24.760> useful<00:11:25.480> if<00:11:25.920> you<00:11:26.399> diversify<00:11:27.000> your 00:11:27.269 --> 00:11:27.279 align:start position:0% be super useful if you diversify your 00:11:27.279 --> 00:11:30.670 align:start position:0% be super useful if you diversify your skill<00:11:27.920> your<00:11:28.240> skills<00:11:29.320> so<00:11:29.600> with<00:11:29.800> defi<00:11:30.399> there's 00:11:30.670 --> 00:11:30.680 align:start position:0% skill your skills so with defi there's 00:11:30.680 --> 00:11:34.710 align:start position:0% skill your skills so with defi there's all<00:11:30.920> these<00:11:31.240> super<00:11:31.639> useful<00:11:32.639> uh<00:11:33.279> resources<00:11:34.279> like 00:11:34.710 --> 00:11:34.720 align:start position:0% all these super useful uh resources like 00:11:34.720 --> 00:11:39.430 align:start position:0% all these super useful uh resources like secur<00:11:35.720> uh<00:11:36.399> um<00:11:36.760> that<00:11:37.560> can<00:11:37.760> help<00:11:37.959> you<00:11:38.440> become 00:11:39.430 --> 00:11:39.440 align:start position:0% secur uh um that can help you become 00:11:39.440 --> 00:11:42.509 align:start position:0% secur uh um that can help you become like<00:11:39.600> a<00:11:39.800> security<00:11:41.000> researcher<00:11:42.000> uh<00:11:42.160> but<00:11:42.279> it's 00:11:42.509 --> 00:11:42.519 align:start position:0% like a security researcher uh but it's 00:11:42.519 --> 00:11:44.990 align:start position:0% like a security researcher uh but it's often<00:11:43.440> easy<00:11:43.760> to<00:11:43.959> overlook<00:11:44.480> the<00:11:44.639> fact<00:11:44.880> that 00:11:44.990 --> 00:11:45.000 align:start position:0% often easy to overlook the fact that 00:11:45.000 --> 00:11:47.430 align:start position:0% often easy to overlook the fact that learning<00:11:45.480> other<00:11:45.800> things<00:11:46.360> that<00:11:47.000> aren't 00:11:47.430 --> 00:11:47.440 align:start position:0% learning other things that aren't 00:11:47.440 --> 00:11:51.670 align:start position:0% learning other things that aren't necessarily<00:11:48.079> directly<00:11:48.880> related<00:11:49.399> to<00:11:50.200> um<00:11:50.880> defi 00:11:51.670 --> 00:11:51.680 align:start position:0% necessarily directly related to um defi 00:11:51.680 --> 00:11:54.110 align:start position:0% necessarily directly related to um defi or<00:11:52.200> smart<00:11:52.560> contract<00:11:52.959> security<00:11:53.720> is<00:11:53.839> going<00:11:53.959> to 00:11:54.110 --> 00:11:54.120 align:start position:0% or smart contract security is going to 00:11:54.120 --> 00:11:56.710 align:start position:0% or smart contract security is going to be<00:11:54.320> incredibly<00:11:54.920> useful<00:11:55.800> like<00:11:56.079> learning 00:11:56.710 --> 00:11:56.720 align:start position:0% be incredibly useful like learning 00:11:56.720 --> 00:12:00.150 align:start position:0% be incredibly useful like learning quantitative<00:11:58.000> Finance<00:11:59.000> is 00:12:00.150 --> 00:12:00.160 align:start position:0% quantitative Finance is 00:12:00.160 --> 00:12:01.990 align:start position:0% quantitative Finance is has<00:12:00.320> been<00:12:00.560> super<00:12:00.839> helpful<00:12:01.240> for<00:12:01.399> me<00:12:01.720> like 00:12:01.990 --> 00:12:02.000 align:start position:0% has been super helpful for me like 00:12:02.000 --> 00:12:05.150 align:start position:0% has been super helpful for me like there's<00:12:02.200> a<00:12:02.360> couple<00:12:02.680> topics<00:12:03.160> here<00:12:04.079> uh<00:12:04.720> like<00:12:04.959> for 00:12:05.150 --> 00:12:05.160 align:start position:0% there's a couple topics here uh like for 00:12:05.160 --> 00:12:07.269 align:start position:0% there's a couple topics here uh like for example<00:12:05.600> learning<00:12:05.959> how<00:12:06.160> compilers<00:12:06.680> work<00:12:07.079> I 00:12:07.269 --> 00:12:07.279 align:start position:0% example learning how compilers work I 00:12:07.279 --> 00:12:09.870 align:start position:0% example learning how compilers work I think<00:12:07.519> is<00:12:07.680> an<00:12:08.079> insane<00:12:08.720> thing<00:12:09.200> like<00:12:09.399> insanely 00:12:09.870 --> 00:12:09.880 align:start position:0% think is an insane thing like insanely 00:12:09.880 --> 00:12:12.350 align:start position:0% think is an insane thing like insanely useful<00:12:10.279> thing<00:12:10.440> to<00:12:10.600> know<00:12:10.880> because<00:12:11.040> you'll<00:12:11.680> be 00:12:12.350 --> 00:12:12.360 align:start position:0% useful thing to know because you'll be 00:12:12.360 --> 00:12:14.310 align:start position:0% useful thing to know because you'll be so<00:12:12.600> much<00:12:12.800> more<00:12:13.079> familiar<00:12:13.639> with<00:12:13.920> how 00:12:14.310 --> 00:12:14.320 align:start position:0% so much more familiar with how 00:12:14.320 --> 00:12:16.670 align:start position:0% so much more familiar with how programming<00:12:14.800> languages<00:12:15.360> work<00:12:15.959> how<00:12:16.120> solidity 00:12:16.670 --> 00:12:16.680 align:start position:0% programming languages work how solidity 00:12:16.680 --> 00:12:19.230 align:start position:0% programming languages work how solidity Works<00:12:16.920> under<00:12:17.160> the<00:12:17.320> hood<00:12:17.600> you<00:12:17.800> just<00:12:18.800> get<00:12:19.000> an 00:12:19.230 --> 00:12:19.240 align:start position:0% Works under the hood you just get an 00:12:19.240 --> 00:12:22.910 align:start position:0% Works under the hood you just get an intuitive<00:12:19.959> sense<00:12:20.440> of<00:12:21.160> how<00:12:21.800> these<00:12:22.000> things<00:12:22.320> work 00:12:22.910 --> 00:12:22.920 align:start position:0% intuitive sense of how these things work 00:12:22.920 --> 00:12:24.870 align:start position:0% intuitive sense of how these things work and<00:12:23.120> that<00:12:23.320> in<00:12:23.440> the<00:12:23.600> end<00:12:23.920> will<00:12:24.120> help<00:12:24.360> you 00:12:24.870 --> 00:12:24.880 align:start position:0% and that in the end will help you 00:12:24.880 --> 00:12:27.030 align:start position:0% and that in the end will help you understand<00:12:25.079> code<00:12:25.440> better<00:12:26.360> find<00:12:26.639> and<00:12:26.800> find 00:12:27.030 --> 00:12:27.040 align:start position:0% understand code better find and find 00:12:27.040 --> 00:12:31.310 align:start position:0% understand code better find and find more<00:12:27.320> bugs<00:12:28.320> um<00:12:28.639> it's<00:12:28.839> also 00:12:31.310 --> 00:12:31.320 align:start position:0% 00:12:31.320 --> 00:12:33.389 align:start position:0% just<00:12:32.320> something<00:12:32.680> that<00:12:32.839> keeps<00:12:33.120> things 00:12:33.389 --> 00:12:33.399 align:start position:0% just something that keeps things 00:12:33.399 --> 00:12:36.310 align:start position:0% just something that keeps things interesting<00:12:33.920> you<00:12:34.040> know<00:12:34.639> like<00:12:35.600> after<00:12:35.839> a<00:12:36.000> while 00:12:36.310 --> 00:12:36.320 align:start position:0% interesting you know like after a while 00:12:36.320 --> 00:12:38.350 align:start position:0% interesting you know like after a while maybe<00:12:36.519> defi<00:12:36.959> gets<00:12:37.160> a<00:12:37.240> little<00:12:37.399> bit<00:12:37.560> boring<00:12:38.040> this 00:12:38.350 --> 00:12:38.360 align:start position:0% maybe defi gets a little bit boring this 00:12:38.360 --> 00:12:41.189 align:start position:0% maybe defi gets a little bit boring this kind<00:12:38.480> of<00:12:38.600> switches<00:12:39.000> it<00:12:39.199> up<00:12:40.000> uh<00:12:40.360> so<00:12:40.639> it's<00:12:41.000> it's 00:12:41.189 --> 00:12:41.199 align:start position:0% kind of switches it up uh so it's it's 00:12:41.199 --> 00:12:46.790 align:start position:0% kind of switches it up uh so it's it's also<00:12:41.600> just<00:12:41.760> something<00:12:42.560> uh<00:12:42.680> to<00:12:42.880> have<00:12:43.000> some 00:12:46.790 --> 00:12:46.800 align:start position:0% 00:12:46.800 --> 00:12:49.350 align:start position:0% fun 00:12:49.350 --> 00:12:49.360 align:start position:0% fun 00:12:49.360 --> 00:12:52.310 align:start position:0% fun okay<00:12:50.360> now<00:12:50.920> some<00:12:51.279> strategies<00:12:51.880> that<00:12:52.000> you<00:12:52.120> can 00:12:52.310 --> 00:12:52.320 align:start position:0% okay now some strategies that you can 00:12:52.320 --> 00:12:53.430 align:start position:0% okay now some strategies that you can actually 00:12:53.430 --> 00:12:53.440 align:start position:0% actually 00:12:53.440 --> 00:12:57.829 align:start position:0% actually apply<00:12:54.440> uh<00:12:54.959> in<00:12:55.720> uh<00:12:55.839> your<00:12:56.120> buck<00:12:56.440> hunting 00:12:57.829 --> 00:12:57.839 align:start position:0% apply uh in uh your buck hunting 00:12:57.839 --> 00:12:59.910 align:start position:0% apply uh in uh your buck hunting process<00:12:58.839> I<00:12:58.959> think<00:12:59.160> I<00:12:59.240> think<00:12:59.519> one<00:12:59.639> of<00:12:59.800> the 00:12:59.910 --> 00:12:59.920 align:start position:0% process I think I think one of the 00:12:59.920 --> 00:13:02.629 align:start position:0% process I think I think one of the things<00:13:00.120> that<00:13:00.279> works<00:13:00.600> really<00:13:00.839> well<00:13:01.720> is<00:13:02.440> uh 00:13:02.629 --> 00:13:02.639 align:start position:0% things that works really well is uh 00:13:02.639 --> 00:13:04.710 align:start position:0% things that works really well is uh finding<00:13:02.959> a<00:13:03.160> paradigm<00:13:03.720> and<00:13:03.920> specializing<00:13:04.560> in 00:13:04.710 --> 00:13:04.720 align:start position:0% finding a paradigm and specializing in 00:13:04.720 --> 00:13:09.430 align:start position:0% finding a paradigm and specializing in it<00:13:05.760> so<00:13:06.760> for<00:13:06.959> example<00:13:07.639> in<00:13:07.839> defi<00:13:08.839> uh<00:13:09.000> you<00:13:09.199> have 00:13:09.430 --> 00:13:09.440 align:start position:0% it so for example in defi uh you have 00:13:09.440 --> 00:13:11.990 align:start position:0% it so for example in defi uh you have systems<00:13:09.880> that<00:13:10.120> provide<00:13:10.480> leverage<00:13:11.320> so<00:13:11.880> what 00:13:11.990 --> 00:13:12.000 align:start position:0% systems that provide leverage so what 00:13:12.000 --> 00:13:14.350 align:start position:0% systems that provide leverage so what you<00:13:12.120> can<00:13:12.320> do<00:13:12.560> is<00:13:12.760> become<00:13:13.160> super<00:13:13.519> familiar<00:13:14.199> with 00:13:14.350 --> 00:13:14.360 align:start position:0% you can do is become super familiar with 00:13:14.360 --> 00:13:17.470 align:start position:0% you can do is become super familiar with all<00:13:14.519> the<00:13:14.720> things<00:13:15.440> that<00:13:16.320> you<00:13:16.519> need<00:13:16.720> to<00:13:16.920> do<00:13:17.240> to 00:13:17.470 --> 00:13:17.480 align:start position:0% all the things that you need to do to 00:13:17.480 --> 00:13:20.189 align:start position:0% all the things that you need to do to implement<00:13:18.079> leverage<00:13:18.560> systems<00:13:19.440> and<00:13:19.839> what<00:13:20.000> can 00:13:20.189 --> 00:13:20.199 align:start position:0% implement leverage systems and what can 00:13:20.199 --> 00:13:22.790 align:start position:0% implement leverage systems and what can go<00:13:20.440> wrong<00:13:21.360> once<00:13:21.560> you<00:13:21.680> know<00:13:21.920> all<00:13:22.160> these<00:13:22.360> things 00:13:22.790 --> 00:13:22.800 align:start position:0% go wrong once you know all these things 00:13:22.800 --> 00:13:25.269 align:start position:0% go wrong once you know all these things you<00:13:22.920> can<00:13:23.160> just<00:13:23.399> quickly<00:13:23.720> go<00:13:23.920> into<00:13:24.279> all<00:13:24.519> the 00:13:25.269 --> 00:13:25.279 align:start position:0% you can just quickly go into all the 00:13:25.279 --> 00:13:28.310 align:start position:0% you can just quickly go into all the programs<00:13:26.279> that<00:13:26.800> have<00:13:27.040> some<00:13:27.320> type<00:13:27.519> of<00:13:27.680> Leverage 00:13:28.310 --> 00:13:28.320 align:start position:0% programs that have some type of Leverage 00:13:28.320 --> 00:13:29.550 align:start position:0% programs that have some type of Leverage see<00:13:28.480> if<00:13:28.600> they<00:13:28.720> do<00:13:28.880> everything<00:13:29.120> everything 00:13:29.550 --> 00:13:29.560 align:start position:0% see if they do everything everything 00:13:29.560 --> 00:13:32.189 align:start position:0% see if they do everything everything right<00:13:30.360> and<00:13:30.560> if<00:13:30.720> they<00:13:30.880> do<00:13:31.240> you<00:13:31.399> just<00:13:31.560> move<00:13:31.800> on<00:13:32.000> to 00:13:32.189 --> 00:13:32.199 align:start position:0% right and if they do you just move on to 00:13:32.199 --> 00:13:34.590 align:start position:0% right and if they do you just move on to the<00:13:32.399> next<00:13:32.680> project<00:13:33.399> so<00:13:33.639> this<00:13:33.760> is<00:13:34.000> kind<00:13:34.160> of<00:13:34.360> like 00:13:34.590 --> 00:13:34.600 align:start position:0% the next project so this is kind of like 00:13:34.600 --> 00:13:37.550 align:start position:0% the next project so this is kind of like a<00:13:34.839> an<00:13:35.040> approach<00:13:35.440> where<00:13:35.600> you<00:13:35.760> go<00:13:36.000> super<00:13:36.560> broad 00:13:37.550 --> 00:13:37.560 align:start position:0% a an approach where you go super broad 00:13:37.560 --> 00:13:40.189 align:start position:0% a an approach where you go super broad um<00:13:37.760> and<00:13:37.880> it<00:13:38.000> can<00:13:38.160> be<00:13:38.360> super<00:13:38.959> efficient<00:13:39.959> what's 00:13:40.189 --> 00:13:40.199 align:start position:0% um and it can be super efficient what's 00:13:40.199 --> 00:13:43.389 align:start position:0% um and it can be super efficient what's important<00:13:40.720> here<00:13:41.000> is<00:13:41.120> to<00:13:41.480> get<00:13:41.680> pick<00:13:41.880> a<00:13:42.399> paradigm 00:13:43.389 --> 00:13:43.399 align:start position:0% important here is to get pick a paradigm 00:13:43.399 --> 00:13:46.990 align:start position:0% important here is to get pick a paradigm that<00:13:43.839> is<00:13:44.680> relatively<00:13:45.560> unknown<00:13:46.279> or<00:13:46.600> that<00:13:46.760> you 00:13:46.990 --> 00:13:47.000 align:start position:0% that is relatively unknown or that you 00:13:47.000 --> 00:13:49.509 align:start position:0% that is relatively unknown or that you think<00:13:47.680> nobody<00:13:48.079> else<00:13:48.279> is<00:13:48.440> specializing<00:13:49.040> in 00:13:49.509 --> 00:13:49.519 align:start position:0% think nobody else is specializing in 00:13:49.519 --> 00:13:50.590 align:start position:0% think nobody else is specializing in because<00:13:49.720> that<00:13:49.880> way<00:13:50.079> you<00:13:50.199> have<00:13:50.320> some 00:13:50.590 --> 00:13:50.600 align:start position:0% because that way you have some 00:13:50.600 --> 00:13:55.670 align:start position:0% because that way you have some competitive<00:13:51.440> Advantage<00:13:52.800> um<00:13:53.800> I<00:13:54.040> um<00:13:54.600> so<00:13:55.360> uh<00:13:55.600> I 00:13:55.670 --> 00:13:55.680 align:start position:0% competitive Advantage um I um so uh I 00:13:55.680 --> 00:13:57.069 align:start position:0% competitive Advantage um I um so uh I guess<00:13:55.880> leverage<00:13:56.240> and<00:13:56.480> concentrated 00:13:57.069 --> 00:13:57.079 align:start position:0% guess leverage and concentrated 00:13:57.079 --> 00:14:00.189 align:start position:0% guess leverage and concentrated liquidity<00:13:57.639> are<00:13:58.320> a<00:13:58.440> little<00:13:58.600> bit<00:13:58.759> old<00:13:59.199> now<00:13:59.959> uh 00:14:00.189 --> 00:14:00.199 align:start position:0% liquidity are a little bit old now uh 00:14:00.199 --> 00:14:03.670 align:start position:0% liquidity are a little bit old now uh but<00:14:00.680> I<00:14:00.800> guess<00:14:01.279> like<00:14:01.560> various<00:14:01.920> CK<00:14:02.560> topics<00:14:03.519> uh 00:14:03.670 --> 00:14:03.680 align:start position:0% but I guess like various CK topics uh 00:14:03.680 --> 00:14:05.710 align:start position:0% but I guess like various CK topics uh can<00:14:03.800> be<00:14:04.000> something<00:14:04.519> right<00:14:04.680> now<00:14:05.120> that<00:14:05.399> there's 00:14:05.710 --> 00:14:05.720 align:start position:0% can be something right now that there's 00:14:05.720 --> 00:14:08.150 align:start position:0% can be something right now that there's not<00:14:05.959> that<00:14:06.160> many<00:14:06.440> security<00:14:06.920> researchers<00:14:07.920> that 00:14:08.150 --> 00:14:08.160 align:start position:0% not that many security researchers that 00:14:08.160 --> 00:14:10.710 align:start position:0% not that many security researchers that specialize<00:14:08.680> in<00:14:08.880> these<00:14:09.519> where<00:14:10.160> uh<00:14:10.320> there<00:14:10.519> might 00:14:10.710 --> 00:14:10.720 align:start position:0% specialize in these where uh there might 00:14:10.720 --> 00:14:14.350 align:start position:0% specialize in these where uh there might be<00:14:11.079> uh<00:14:11.279> some<00:14:11.600> some<00:14:11.839> good<00:14:12.399> opportunities<00:14:13.399> um 00:14:14.350 --> 00:14:14.360 align:start position:0% be uh some some good opportunities um 00:14:14.360 --> 00:14:16.350 align:start position:0% be uh some some good opportunities um and<00:14:14.839> I<00:14:15.079> just<00:14:15.199> pick<00:14:15.440> something<00:14:15.800> that<00:14:15.920> you<00:14:16.040> find 00:14:16.350 --> 00:14:16.360 align:start position:0% and I just pick something that you find 00:14:16.360 --> 00:14:18.230 align:start position:0% and I just pick something that you find interesting<00:14:16.880> to<00:14:17.040> be<00:14:17.199> honest<00:14:17.880> uh<00:14:18.040> because 00:14:18.230 --> 00:14:18.240 align:start position:0% interesting to be honest uh because 00:14:18.240 --> 00:14:20.990 align:start position:0% interesting to be honest uh because that's<00:14:18.399> the<00:14:18.560> best<00:14:18.800> way<00:14:19.560> uh<00:14:19.759> to<00:14:20.199> to<00:14:20.360> learn<00:14:20.720> and 00:14:20.990 --> 00:14:21.000 align:start position:0% that's the best way uh to to learn and 00:14:21.000 --> 00:14:23.189 align:start position:0% that's the best way uh to to learn and go<00:14:21.240> about<00:14:21.480> this 00:14:23.189 --> 00:14:23.199 align:start position:0% go about this 00:14:23.199 --> 00:14:26.389 align:start position:0% go about this all<00:14:24.199> that<00:14:24.360> was<00:14:24.519> the<00:14:24.720> go<00:14:24.959> broad<00:14:25.440> strategy<00:14:26.199> now 00:14:26.389 --> 00:14:26.399 align:start position:0% all that was the go broad strategy now 00:14:26.399 --> 00:14:30.509 align:start position:0% all that was the go broad strategy now for<00:14:26.639> the<00:14:26.880> go<00:14:27.199> deep<00:14:27.800> strategy<00:14:28.800> um 00:14:30.509 --> 00:14:30.519 align:start position:0% for the go deep strategy um 00:14:30.519 --> 00:14:33.629 align:start position:0% for the go deep strategy um instead<00:14:30.880> of<00:14:31.120> just<00:14:31.880> going<00:14:32.480> for<00:14:32.880> a<00:14:33.120> bunch<00:14:33.360> of 00:14:33.629 --> 00:14:33.639 align:start position:0% instead of just going for a bunch of 00:14:33.639 --> 00:14:36.509 align:start position:0% instead of just going for a bunch of projects<00:14:34.120> for<00:14:34.360> one<00:14:34.680> topic<00:14:35.160> you<00:14:35.279> can<00:14:35.519> pick<00:14:35.880> one 00:14:36.509 --> 00:14:36.519 align:start position:0% projects for one topic you can pick one 00:14:36.519 --> 00:14:40.150 align:start position:0% projects for one topic you can pick one project<00:14:37.199> and<00:14:37.320> then<00:14:37.519> go<00:14:37.759> deep<00:14:38.120> on<00:14:38.399> that<00:14:38.560> one 00:14:40.150 --> 00:14:40.160 align:start position:0% project and then go deep on that one 00:14:40.160 --> 00:14:43.030 align:start position:0% project and then go deep on that one um<00:14:41.160> this<00:14:41.279> is<00:14:41.440> an<00:14:41.680> approach<00:14:42.120> I<00:14:42.279> usually<00:14:42.680> take 00:14:43.030 --> 00:14:43.040 align:start position:0% um this is an approach I usually take 00:14:43.040 --> 00:14:44.829 align:start position:0% um this is an approach I usually take because<00:14:43.279> I<00:14:43.519> have<00:14:43.880> like<00:14:44.040> I'm<00:14:44.240> very<00:14:44.560> time 00:14:44.829 --> 00:14:44.839 align:start position:0% because I have like I'm very time 00:14:44.839 --> 00:14:47.990 align:start position:0% because I have like I'm very time constrained<00:14:45.839> I<00:14:46.320> do<00:14:46.600> like<00:14:46.839> weekends<00:14:47.839> like 00:14:47.990 --> 00:14:48.000 align:start position:0% constrained I do like weekends like 00:14:48.000 --> 00:14:51.749 align:start position:0% constrained I do like weekends like short<00:14:48.480> weeks<00:14:49.480> um<00:14:50.240> and<00:14:50.800> the<00:14:51.240> approach<00:14:51.600> I 00:14:51.749 --> 00:14:51.759 align:start position:0% short weeks um and the approach I 00:14:51.759 --> 00:14:55.949 align:start position:0% short weeks um and the approach I basically<00:14:52.160> take<00:14:52.399> is<00:14:52.639> I<00:14:53.160> I<00:14:54.160> pick<00:14:54.399> a<00:14:54.720> project<00:14:55.720> and 00:14:55.949 --> 00:14:55.959 align:start position:0% basically take is I I pick a project and 00:14:55.959 --> 00:14:58.470 align:start position:0% basically take is I I pick a project and then<00:14:56.519> I<00:14:56.680> take<00:14:56.839> some<00:14:57.079> time<00:14:57.279> to<00:14:57.519> explore<00:14:57.920> it<00:14:58.240> and 00:14:58.470 --> 00:14:58.480 align:start position:0% then I take some time to explore it and 00:14:58.480 --> 00:15:01.590 align:start position:0% then I take some time to explore it and identify<00:14:59.079> by<00:14:59.399> all<00:14:59.800> the<00:15:00.800> like<00:15:00.959> the<00:15:01.079> interesting 00:15:01.590 --> 00:15:01.600 align:start position:0% identify by all the like the interesting 00:15:01.600 --> 00:15:04.470 align:start position:0% identify by all the like the interesting bits<00:15:02.279> the<00:15:02.440> risky<00:15:02.839> bits<00:15:03.600> uh<00:15:03.800> the<00:15:03.920> parts<00:15:04.199> that<00:15:04.360> I 00:15:04.470 --> 00:15:04.480 align:start position:0% bits the risky bits uh the parts that I 00:15:04.480 --> 00:15:06.189 align:start position:0% bits the risky bits uh the parts that I think<00:15:04.680> are<00:15:04.839> going<00:15:04.920> to<00:15:05.079> be<00:15:05.360> super<00:15:05.920> difficult<00:15:06.040> to 00:15:06.189 --> 00:15:06.199 align:start position:0% think are going to be super difficult to 00:15:06.199 --> 00:15:08.509 align:start position:0% think are going to be super difficult to implement<00:15:06.680> right<00:15:07.399> if<00:15:07.600> I<00:15:07.720> were<00:15:07.920> to<00:15:08.079> implement 00:15:08.509 --> 00:15:08.519 align:start position:0% implement right if I were to implement 00:15:08.519 --> 00:15:11.550 align:start position:0% implement right if I were to implement them<00:15:08.839> that<00:15:09.120> myself<00:15:10.040> and<00:15:10.279> then<00:15:10.839> I<00:15:11.000> basically 00:15:11.550 --> 00:15:11.560 align:start position:0% them that myself and then I basically 00:15:11.560 --> 00:15:14.430 align:start position:0% them that myself and then I basically just<00:15:11.720> go<00:15:12.000> have<00:15:12.120> a<00:15:12.240> look<00:15:12.399> at<00:15:12.639> those<00:15:13.600> um<00:15:14.040> and<00:15:14.199> see 00:15:14.430 --> 00:15:14.440 align:start position:0% just go have a look at those um and see 00:15:14.440 --> 00:15:17.150 align:start position:0% just go have a look at those um and see if<00:15:15.160> they<00:15:16.160> if<00:15:16.320> they<00:15:16.560> actually<00:15:16.759> made<00:15:17.000> the 00:15:17.150 --> 00:15:17.160 align:start position:0% if they if they actually made the 00:15:17.160 --> 00:15:20.430 align:start position:0% if they if they actually made the mistakes<00:15:17.560> that<00:15:17.759> I<00:15:17.959> think<00:15:18.800> uh<00:15:19.199> they<00:15:19.360> would<00:15:19.519> have 00:15:20.430 --> 00:15:20.440 align:start position:0% mistakes that I think uh they would have 00:15:20.440 --> 00:15:23.350 align:start position:0% mistakes that I think uh they would have um<00:15:20.920> and<00:15:21.079> that's<00:15:21.360> actually<00:15:21.880> like<00:15:22.000> a<00:15:22.160> super<00:15:22.759> time 00:15:23.350 --> 00:15:23.360 align:start position:0% um and that's actually like a super time 00:15:23.360 --> 00:15:25.829 align:start position:0% um and that's actually like a super time efficient<00:15:24.360> uh<00:15:24.600> approach<00:15:25.079> when<00:15:25.240> you<00:15:25.560> when<00:15:25.680> you 00:15:25.829 --> 00:15:25.839 align:start position:0% efficient uh approach when you when you 00:15:25.839 --> 00:15:28.150 align:start position:0% efficient uh approach when you when you think<00:15:26.079> about<00:15:26.320> it<00:15:27.199> uh<00:15:27.360> and<00:15:27.519> this<00:15:27.759> kind<00:15:27.920> of 00:15:28.150 --> 00:15:28.160 align:start position:0% think about it uh and this kind of 00:15:28.160 --> 00:15:30.350 align:start position:0% think about it uh and this kind of exploits<00:15:28.680> the<00:15:28.800> fact<00:15:29.319> that<00:15:29.800> as<00:15:29.880> a<00:15:30.040> bounty 00:15:30.350 --> 00:15:30.360 align:start position:0% exploits the fact that as a bounty 00:15:30.360 --> 00:15:33.230 align:start position:0% exploits the fact that as a bounty hunter<00:15:30.839> you're<00:15:31.040> not<00:15:31.240> an<00:15:31.720> auditor<00:15:32.720> as<00:15:32.800> a<00:15:32.959> bounty 00:15:33.230 --> 00:15:33.240 align:start position:0% hunter you're not an auditor as a bounty 00:15:33.240 --> 00:15:35.030 align:start position:0% hunter you're not an auditor as a bounty hunter<00:15:33.639> you<00:15:33.759> don't<00:15:34.000> care<00:15:34.240> about<00:15:34.440> finding<00:15:34.839> all 00:15:35.030 --> 00:15:35.040 align:start position:0% hunter you don't care about finding all 00:15:35.040 --> 00:15:36.550 align:start position:0% hunter you don't care about finding all the<00:15:35.160> bugs<00:15:35.600> it<00:15:35.720> doesn't<00:15:36.000> matter<00:15:36.360> like<00:15:36.480> it 00:15:36.550 --> 00:15:36.560 align:start position:0% the bugs it doesn't matter like it 00:15:36.560 --> 00:15:38.069 align:start position:0% the bugs it doesn't matter like it doesn't<00:15:36.800> matter<00:15:37.079> if<00:15:37.199> something<00:15:37.519> is<00:15:37.800> left 00:15:38.069 --> 00:15:38.079 align:start position:0% doesn't matter if something is left 00:15:38.079 --> 00:15:41.389 align:start position:0% doesn't matter if something is left after<00:15:38.440> you<00:15:39.000> go<00:15:39.279> by<00:15:39.720> as<00:15:39.800> an<00:15:40.000> aitor<00:15:40.680> that<00:15:40.880> kind<00:15:41.000> of 00:15:41.389 --> 00:15:41.399 align:start position:0% after you go by as an aitor that kind of 00:15:41.399 --> 00:15:43.590 align:start position:0% after you go by as an aitor that kind of sucks<00:15:41.759> if<00:15:41.920> that<00:15:42.120> happens<00:15:42.759> but<00:15:43.040> as<00:15:43.160> a<00:15:43.279> bounty 00:15:43.590 --> 00:15:43.600 align:start position:0% sucks if that happens but as a bounty 00:15:43.600 --> 00:15:46.110 align:start position:0% sucks if that happens but as a bounty hunter<00:15:44.000> we<00:15:44.199> just<00:15:44.600> want<00:15:44.759> to<00:15:45.040> find<00:15:45.480> a<00:15:45.680> bug<00:15:46.000> as 00:15:46.110 --> 00:15:46.120 align:start position:0% hunter we just want to find a bug as 00:15:46.120 --> 00:15:48.629 align:start position:0% hunter we just want to find a bug as soon<00:15:46.319> as<00:15:46.600> possible<00:15:47.440> and<00:15:47.639> this<00:15:48.079> approach<00:15:48.440> will 00:15:48.629 --> 00:15:48.639 align:start position:0% soon as possible and this approach will 00:15:48.639 --> 00:15:50.629 align:start position:0% soon as possible and this approach will allow<00:15:48.880> us<00:15:49.000> to<00:15:49.160> do<00:15:49.399> that<00:15:49.839> we<00:15:50.040> we'll<00:15:50.279> just<00:15:50.519> have 00:15:50.629 --> 00:15:50.639 align:start position:0% allow us to do that we we'll just have 00:15:50.639 --> 00:15:53.189 align:start position:0% allow us to do that we we'll just have to<00:15:50.800> look<00:15:50.959> at<00:15:51.160> like<00:15:51.560> the<00:15:51.720> critical<00:15:52.279> code<00:15:53.040> the 00:15:53.189 --> 00:15:53.199 align:start position:0% to look at like the critical code the 00:15:53.199 --> 00:15:55.590 align:start position:0% to look at like the critical code the code<00:15:53.480> that<00:15:53.600> does<00:15:54.160> liquidations<00:15:55.160> uh<00:15:55.279> we<00:15:55.399> don't 00:15:55.590 --> 00:15:55.600 align:start position:0% code that does liquidations uh we don't 00:15:55.600 --> 00:15:58.309 align:start position:0% code that does liquidations uh we don't have<00:15:55.720> to<00:15:55.880> look<00:15:56.000> at<00:15:56.199> all<00:15:56.440> the<00:15:56.720> like<00:15:57.000> boring<00:15:57.360> bits 00:15:58.309 --> 00:15:58.319 align:start position:0% have to look at all the like boring bits 00:15:58.319 --> 00:16:00.309 align:start position:0% have to look at all the like boring bits like<00:15:59.000> usually<00:15:59.279> you<00:15:59.399> don't<00:15:59.639> look<00:15:59.800> at<00:16:00.079> like<00:16:00.199> the 00:16:00.309 --> 00:16:00.319 align:start position:0% like usually you don't look at like the 00:16:00.319 --> 00:16:02.749 align:start position:0% like usually you don't look at like the erc20<00:16:01.120> contracts<00:16:01.600> where<00:16:02.160> they<00:16:02.279> do<00:16:02.480> all<00:16:02.639> the 00:16:02.749 --> 00:16:02.759 align:start position:0% erc20 contracts where they do all the 00:16:02.759 --> 00:16:04.990 align:start position:0% erc20 contracts where they do all the interfacing<00:16:03.600> right<00:16:04.000> I<00:16:04.079> mean<00:16:04.240> you<00:16:04.399> could<00:16:04.800> but 00:16:04.990 --> 00:16:05.000 align:start position:0% interfacing right I mean you could but 00:16:05.000 --> 00:16:08.389 align:start position:0% interfacing right I mean you could but that's<00:16:05.199> not<00:16:05.600> the<00:16:06.079> the<00:16:06.240> go<00:16:06.480> deep 00:16:08.389 --> 00:16:08.399 align:start position:0% that's not the the go deep 00:16:08.399 --> 00:16:12.470 align:start position:0% that's not the the go deep approach<00:16:09.399> tip<00:16:09.680> nine<00:16:10.600> read<00:16:10.839> the<00:16:11.480> documentation 00:16:12.470 --> 00:16:12.480 align:start position:0% approach tip nine read the documentation 00:16:12.480 --> 00:16:15.670 align:start position:0% approach tip nine read the documentation okay<00:16:12.959> so<00:16:13.959> design<00:16:14.360> mistakes<00:16:14.759> can<00:16:14.959> be<00:16:15.079> critical 00:16:15.670 --> 00:16:15.680 align:start position:0% okay so design mistakes can be critical 00:16:15.680 --> 00:16:17.670 align:start position:0% okay so design mistakes can be critical people<00:16:15.920> come<00:16:16.120> up<00:16:16.399> with<00:16:16.600> interesting<00:16:17.160> ideas 00:16:17.670 --> 00:16:17.680 align:start position:0% people come up with interesting ideas 00:16:17.680 --> 00:16:20.389 align:start position:0% people come up with interesting ideas that<00:16:18.120> fundamentally<00:16:19.120> don't<00:16:19.440> work<00:16:19.920> or<00:16:20.199> are 00:16:20.389 --> 00:16:20.399 align:start position:0% that fundamentally don't work or are 00:16:20.399 --> 00:16:23.829 align:start position:0% that fundamentally don't work or are super<00:16:20.720> hard<00:16:20.880> to<00:16:21.040> do<00:16:21.360> right<00:16:22.199> and<00:16:22.680> from<00:16:23.440> reading 00:16:23.829 --> 00:16:23.839 align:start position:0% super hard to do right and from reading 00:16:23.839 --> 00:16:26.309 align:start position:0% super hard to do right and from reading the<00:16:24.480> documentation<00:16:25.480> uh<00:16:25.639> this<00:16:25.800> has<00:16:26.040> happened 00:16:26.309 --> 00:16:26.319 align:start position:0% the documentation uh this has happened 00:16:26.319 --> 00:16:28.790 align:start position:0% the documentation uh this has happened to<00:16:26.480> me<00:16:26.839> this<00:16:26.959> has<00:16:27.199> happened<00:16:27.480> to<00:16:27.680> other<00:16:27.959> people 00:16:28.790 --> 00:16:28.800 align:start position:0% to me this has happened to other people 00:16:28.800 --> 00:16:32.069 align:start position:0% to me this has happened to other people uh<00:16:29.199> you<00:16:29.319> can<00:16:29.560> already<00:16:30.160> notice<00:16:30.920> some<00:16:31.279> bugs<00:16:31.959> and 00:16:32.069 --> 00:16:32.079 align:start position:0% uh you can already notice some bugs and 00:16:32.079 --> 00:16:34.110 align:start position:0% uh you can already notice some bugs and then<00:16:32.199> you<00:16:32.360> just<00:16:32.560> have<00:16:32.680> to<00:16:32.800> go<00:16:32.959> into<00:16:33.240> code<00:16:33.839> into 00:16:34.110 --> 00:16:34.120 align:start position:0% then you just have to go into code into 00:16:34.120 --> 00:16:35.350 align:start position:0% then you just have to go into code into the<00:16:34.279> code<00:16:34.560> to 00:16:35.350 --> 00:16:35.360 align:start position:0% the code to 00:16:35.360 --> 00:16:38.509 align:start position:0% the code to see<00:16:36.399> whether<00:16:37.399> like<00:16:37.560> the<00:16:37.680> bug<00:16:37.959> you<00:16:38.079> think<00:16:38.279> is 00:16:38.509 --> 00:16:38.519 align:start position:0% see whether like the bug you think is 00:16:38.519 --> 00:16:41.110 align:start position:0% see whether like the bug you think is there<00:16:38.880> is<00:16:39.040> going<00:16:39.160> to<00:16:39.319> be<00:16:39.519> actually<00:16:40.120> there 00:16:41.110 --> 00:16:41.120 align:start position:0% there is going to be actually there 00:16:41.120 --> 00:16:43.550 align:start position:0% there is going to be actually there quick<00:16:41.319> side<00:16:41.680> note<00:16:42.040> there<00:16:42.560> documentation 00:16:43.550 --> 00:16:43.560 align:start position:0% quick side note there documentation 00:16:43.560 --> 00:16:45.949 align:start position:0% quick side note there documentation usually<00:16:43.959> out<00:16:44.120> of<00:16:44.360> date 00:16:45.949 --> 00:16:45.959 align:start position:0% usually out of date 00:16:45.959 --> 00:16:49.430 align:start position:0% usually out of date uh<00:16:46.959> fortunately<00:16:48.000> unfortunately<00:16:49.000> depends<00:16:49.279> on 00:16:49.430 --> 00:16:49.440 align:start position:0% uh fortunately unfortunately depends on 00:16:49.440 --> 00:16:53.150 align:start position:0% uh fortunately unfortunately depends on how<00:16:49.600> you<00:16:49.720> look<00:16:49.880> at<00:16:50.040> it<00:16:50.800> um<00:16:51.360> and<00:16:52.000> uh<00:16:52.160> there<00:16:52.399> just 00:16:53.150 --> 00:16:53.160 align:start position:0% how you look at it um and uh there just 00:16:53.160 --> 00:16:54.829 align:start position:0% how you look at it um and uh there just like<00:16:53.319> there's<00:16:53.519> going<00:16:53.639> to<00:16:53.800> be<00:16:54.000> cases<00:16:54.399> where<00:16:54.680> you 00:16:54.829 --> 00:16:54.839 align:start position:0% like there's going to be cases where you 00:16:54.839 --> 00:16:57.309 align:start position:0% like there's going to be cases where you find<00:16:55.040> a<00:16:55.199> bug<00:16:55.600> in<00:16:55.759> the<00:16:55.959> design<00:16:56.639> a<00:16:56.839> bug<00:16:57.079> that's 00:16:57.309 --> 00:16:57.319 align:start position:0% find a bug in the design a bug that's 00:16:57.319 --> 00:16:59.670 align:start position:0% find a bug in the design a bug that's been<00:16:57.560> there<00:16:57.759> but<00:16:57.920> they<00:16:58.120> already<00:16:58.560> like<00:16:59.199> came<00:16:59.480> up 00:16:59.670 --> 00:16:59.680 align:start position:0% been there but they already like came up 00:16:59.680 --> 00:17:02.030 align:start position:0% been there but they already like came up with<00:16:59.880> something<00:17:00.600> that<00:17:00.839> prevented<00:17:01.360> it<00:17:01.839> and 00:17:02.030 --> 00:17:02.040 align:start position:0% with something that prevented it and 00:17:02.040 --> 00:17:05.069 align:start position:0% with something that prevented it and just<00:17:02.199> didn't<00:17:02.839> document<00:17:03.839> it<00:17:04.000> at 00:17:05.069 --> 00:17:05.079 align:start position:0% just didn't document it at 00:17:05.079 --> 00:17:07.789 align:start position:0% just didn't document it at all<00:17:06.079> even<00:17:06.319> if<00:17:06.439> you<00:17:06.559> don't<00:17:06.880> find<00:17:07.199> anything 00:17:07.789 --> 00:17:07.799 align:start position:0% all even if you don't find anything 00:17:07.799 --> 00:17:09.470 align:start position:0% all even if you don't find anything reading<00:17:08.160> the<00:17:08.400> documentation<00:17:09.000> will<00:17:09.160> set<00:17:09.360> you 00:17:09.470 --> 00:17:09.480 align:start position:0% reading the documentation will set you 00:17:09.480 --> 00:17:11.549 align:start position:0% reading the documentation will set you up<00:17:09.600> for<00:17:09.720> a<00:17:09.880> success<00:17:10.439> because<00:17:10.600> you'll<00:17:10.919> have<00:17:11.199> a 00:17:11.549 --> 00:17:11.559 align:start position:0% up for a success because you'll have a 00:17:11.559 --> 00:17:13.470 align:start position:0% up for a success because you'll have a good<00:17:11.839> General<00:17:12.520> understanding<00:17:13.120> of<00:17:13.240> what<00:17:13.360> the 00:17:13.470 --> 00:17:13.480 align:start position:0% good General understanding of what the 00:17:13.480 --> 00:17:17.270 align:start position:0% good General understanding of what the code<00:17:13.760> is<00:17:14.160> doing<00:17:15.160> um<00:17:16.079> which<00:17:16.280> is<00:17:16.720> like<00:17:16.919> the<00:17:17.079> best 00:17:17.270 --> 00:17:17.280 align:start position:0% code is doing um which is like the best 00:17:17.280 --> 00:17:20.630 align:start position:0% code is doing um which is like the best foundation<00:17:18.280> to<00:17:18.760> actually<00:17:19.120> get<00:17:19.319> started<00:17:20.199> so<00:17:20.520> if 00:17:20.630 --> 00:17:20.640 align:start position:0% foundation to actually get started so if 00:17:20.640 --> 00:17:23.510 align:start position:0% foundation to actually get started so if you<00:17:21.120> like<00:17:21.559> when<00:17:21.760> I<00:17:21.919> do 00:17:23.510 --> 00:17:23.520 align:start position:0% you like when I do 00:17:23.520 --> 00:17:26.549 align:start position:0% you like when I do the<00:17:24.520> go<00:17:24.799> deep<00:17:25.079> approach<00:17:25.799> actually<00:17:26.400> the 00:17:26.549 --> 00:17:26.559 align:start position:0% the go deep approach actually the 00:17:26.559 --> 00:17:29.630 align:start position:0% the go deep approach actually the explore<00:17:27.079> phase<00:17:27.720> for<00:17:27.959> me<00:17:28.559> is<00:17:29.039> reading<00:17:29.440> the 00:17:29.630 --> 00:17:29.640 align:start position:0% explore phase for me is reading the 00:17:29.640 --> 00:17:33.230 align:start position:0% explore phase for me is reading the documentation<00:17:30.400> first<00:17:31.400> um<00:17:32.200> because<00:17:32.760> with<00:17:32.960> this 00:17:33.230 --> 00:17:33.240 align:start position:0% documentation first um because with this 00:17:33.240 --> 00:17:35.390 align:start position:0% documentation first um because with this documentation<00:17:33.880> in<00:17:34.039> mind<00:17:34.679> like<00:17:34.960> actually 00:17:35.390 --> 00:17:35.400 align:start position:0% documentation in mind like actually 00:17:35.400 --> 00:17:37.510 align:start position:0% documentation in mind like actually starting<00:17:35.760> to<00:17:35.919> read<00:17:36.120> the<00:17:36.280> code<00:17:36.919> is<00:17:37.080> going<00:17:37.200> to<00:17:37.320> be 00:17:37.510 --> 00:17:37.520 align:start position:0% starting to read the code is going to be 00:17:37.520 --> 00:17:39.510 align:start position:0% starting to read the code is going to be super<00:17:38.400> it's<00:17:38.679> more<00:17:38.880> going<00:17:39.000> to<00:17:39.120> be<00:17:39.280> more 00:17:39.510 --> 00:17:39.520 align:start position:0% super it's more going to be more 00:17:39.520 --> 00:17:41.310 align:start position:0% super it's more going to be more productive<00:17:40.000> because<00:17:40.160> you<00:17:40.280> have<00:17:40.480> some<00:17:41.039> some 00:17:41.310 --> 00:17:41.320 align:start position:0% productive because you have some some 00:17:41.320 --> 00:17:43.830 align:start position:0% productive because you have some some contextual<00:17:41.919> awareness<00:17:42.480> of<00:17:42.840> where<00:17:43.200> everything 00:17:43.830 --> 00:17:43.840 align:start position:0% contextual awareness of where everything 00:17:43.840 --> 00:17:47.870 align:start position:0% contextual awareness of where everything fits<00:17:44.160> in<00:17:44.360> the<00:17:44.960> in<00:17:45.080> the<00:17:45.200> big 00:17:47.870 --> 00:17:47.880 align:start position:0% 00:17:47.880 --> 00:17:49.909 align:start position:0% picture 00:17:49.909 --> 00:17:49.919 align:start position:0% picture 00:17:49.919 --> 00:17:53.630 align:start position:0% picture then<00:17:50.919> for<00:17:51.160> my<00:17:51.400> final<00:17:51.760> tip<00:17:52.760> uh<00:17:52.919> this<00:17:53.039> is<00:17:53.280> kind<00:17:53.400> of 00:17:53.630 --> 00:17:53.640 align:start position:0% then for my final tip uh this is kind of 00:17:53.640 --> 00:17:57.029 align:start position:0% then for my final tip uh this is kind of a<00:17:53.880> mental<00:17:54.280> model<00:17:54.880> I<00:17:55.000> started<00:17:55.400> applying<00:17:56.039> myself 00:17:57.029 --> 00:17:57.039 align:start position:0% a mental model I started applying myself 00:17:57.039 --> 00:17:59.510 align:start position:0% a mental model I started applying myself is<00:17:57.720> when<00:17:57.960> you<00:17:58.120> are<00:17:58.320> reading<00:17:58.960> through<00:17:59.120> a<00:17:59.280> code 00:17:59.510 --> 00:17:59.520 align:start position:0% is when you are reading through a code 00:17:59.520 --> 00:18:03.190 align:start position:0% is when you are reading through a code base<00:18:00.080> you<00:18:00.640> usually<00:18:01.159> notice<00:18:02.120> like<00:18:02.360> a<00:18:02.880> these 00:18:03.190 --> 00:18:03.200 align:start position:0% base you usually notice like a these 00:18:03.200 --> 00:18:07.430 align:start position:0% base you usually notice like a these tricks<00:18:03.679> or<00:18:04.480> gadgets<00:18:05.760> where 00:18:07.430 --> 00:18:07.440 align:start position:0% tricks or gadgets where 00:18:07.440 --> 00:18:10.310 align:start position:0% tricks or gadgets where um<00:18:08.440> it's<00:18:08.679> not<00:18:08.960> really<00:18:09.240> a<00:18:09.400> vulnerability<00:18:10.159> per 00:18:10.310 --> 00:18:10.320 align:start position:0% um it's not really a vulnerability per 00:18:10.320 --> 00:18:12.230 align:start position:0% um it's not really a vulnerability per se<00:18:10.640> like<00:18:10.799> even<00:18:11.039> if<00:18:11.159> you<00:18:11.280> would<00:18:11.480> submit<00:18:11.840> it<00:18:12.039> it 00:18:12.230 --> 00:18:12.240 align:start position:0% se like even if you would submit it it 00:18:12.240 --> 00:18:14.990 align:start position:0% se like even if you would submit it it might<00:18:12.440> be<00:18:12.559> an<00:18:12.679> information<00:18:13.679> or<00:18:13.880> LW<00:18:14.640> but<00:18:14.840> it's 00:18:14.990 --> 00:18:15.000 align:start position:0% might be an information or LW but it's 00:18:15.000 --> 00:18:17.630 align:start position:0% might be an information or LW but it's these<00:18:15.360> tricks<00:18:16.200> that<00:18:16.440> allow<00:18:16.760> you<00:18:16.880> to<00:18:17.080> do<00:18:17.400> things 00:18:17.630 --> 00:18:17.640 align:start position:0% these tricks that allow you to do things 00:18:17.640 --> 00:18:21.710 align:start position:0% these tricks that allow you to do things in<00:18:17.760> a<00:18:18.159> system<00:18:19.159> that<00:18:19.520> are<00:18:19.919> odd<00:18:20.400> or<00:18:21.000> usually<00:18:21.440> not 00:18:21.710 --> 00:18:21.720 align:start position:0% in a system that are odd or usually not 00:18:21.720 --> 00:18:25.029 align:start position:0% in a system that are odd or usually not supposed<00:18:22.080> to<00:18:22.520> happen<00:18:23.520> and<00:18:24.400> even<00:18:24.640> though<00:18:24.840> these 00:18:25.029 --> 00:18:25.039 align:start position:0% supposed to happen and even though these 00:18:25.039 --> 00:18:28.149 align:start position:0% supposed to happen and even though these tricks<00:18:25.360> are<00:18:25.640> kind<00:18:25.760> of<00:18:25.960> useless<00:18:26.400> on<00:18:26.559> their<00:18:27.159> own 00:18:28.149 --> 00:18:28.159 align:start position:0% tricks are kind of useless on their own 00:18:28.159 --> 00:18:32.590 align:start position:0% tricks are kind of useless on their own they<00:18:28.320> are<00:18:28.520> used<00:18:28.799> usually<00:18:29.280> involved<00:18:30.720> in<00:18:31.720> um 00:18:32.590 --> 00:18:32.600 align:start position:0% they are used usually involved in um 00:18:32.600 --> 00:18:34.909 align:start position:0% they are used usually involved in um what<00:18:32.760> you<00:18:32.919> would<00:18:33.159> call<00:18:33.440> a<00:18:33.679> killchain<00:18:34.679> so 00:18:34.909 --> 00:18:34.919 align:start position:0% what you would call a killchain so 00:18:34.919 --> 00:18:36.789 align:start position:0% what you would call a killchain so critical<00:18:35.320> vulnerabilities<00:18:36.320> generally 00:18:36.789 --> 00:18:36.799 align:start position:0% critical vulnerabilities generally 00:18:36.799 --> 00:18:39.110 align:start position:0% critical vulnerabilities generally aren't<00:18:37.200> critical<00:18:37.799> vulnerabilities<00:18:38.799> not 00:18:39.110 --> 00:18:39.120 align:start position:0% aren't critical vulnerabilities not 00:18:39.120 --> 00:18:42.630 align:start position:0% aren't critical vulnerabilities not single<00:18:39.559> bugs<00:18:40.440> but<00:18:40.640> they<00:18:40.760> are<00:18:41.400> kill<00:18:41.679> chains<00:18:42.480> and 00:18:42.630 --> 00:18:42.640 align:start position:0% single bugs but they are kill chains and 00:18:42.640 --> 00:18:44.510 align:start position:0% single bugs but they are kill chains and kill<00:18:42.880> chains<00:18:43.240> are<00:18:43.480> basically<00:18:43.840> a<00:18:44.000> sequence<00:18:44.360> of 00:18:44.510 --> 00:18:44.520 align:start position:0% kill chains are basically a sequence of 00:18:44.520 --> 00:18:46.549 align:start position:0% kill chains are basically a sequence of stabs<00:18:45.000> or<00:18:45.320> sequence<00:18:45.720> of<00:18:45.919> bugs<00:18:46.280> that<00:18:46.400> you 00:18:46.549 --> 00:18:46.559 align:start position:0% stabs or sequence of bugs that you 00:18:46.559 --> 00:18:49.350 align:start position:0% stabs or sequence of bugs that you string<00:18:47.120> together<00:18:47.720> to<00:18:47.960> achieve<00:18:48.320> a<00:18:48.520> critical 00:18:49.350 --> 00:18:49.360 align:start position:0% string together to achieve a critical 00:18:49.360 --> 00:18:52.149 align:start position:0% string together to achieve a critical impact<00:18:50.360> and 00:18:52.149 --> 00:18:52.159 align:start position:0% impact and 00:18:52.159 --> 00:18:55.110 align:start position:0% impact and by<00:18:53.159> keeping<00:18:53.480> track<00:18:53.880> of<00:18:54.120> these<00:18:54.520> little<00:18:54.799> tricks 00:18:55.110 --> 00:18:55.120 align:start position:0% by keeping track of these little tricks 00:18:55.120 --> 00:18:57.430 align:start position:0% by keeping track of these little tricks you<00:18:55.280> find<00:18:55.559> while<00:18:55.760> reading<00:18:56.080> the<00:18:56.240> code<00:18:56.520> base<00:18:57.240> you 00:18:57.430 --> 00:18:57.440 align:start position:0% you find while reading the code base you 00:18:57.440 --> 00:18:59.230 align:start position:0% you find while reading the code base you set<00:18:57.679> yourself<00:18:58.039> up<00:18:58.200> for<00:18:58.400> success<00:18:58.840> say<00:18:59.000> when<00:18:59.120> you 00:18:59.230 --> 00:18:59.240 align:start position:0% set yourself up for success say when you 00:18:59.240 --> 00:19:02.190 align:start position:0% set yourself up for success say when you find<00:18:59.480> an<00:18:59.679> actual<00:19:00.039> bug<00:19:00.880> that's<00:19:01.200> maybe<00:19:01.600> not 00:19:02.190 --> 00:19:02.200 align:start position:0% find an actual bug that's maybe not 00:19:02.200 --> 00:19:04.630 align:start position:0% find an actual bug that's maybe not exploitable<00:19:03.120> or<00:19:03.400> easily<00:19:03.840> exploitable 00:19:04.630 --> 00:19:04.640 align:start position:0% exploitable or easily exploitable 00:19:04.640 --> 00:19:08.230 align:start position:0% exploitable or easily exploitable directly<00:19:05.640> but<00:19:06.440> when<00:19:06.600> you<00:19:06.840> apply<00:19:07.120> your<00:19:07.320> tricks 00:19:08.230 --> 00:19:08.240 align:start position:0% directly but when you apply your tricks 00:19:08.240 --> 00:19:10.270 align:start position:0% directly but when you apply your tricks it<00:19:08.360> suddenly<00:19:08.840> becomes<00:19:09.360> like<00:19:09.480> a<00:19:09.679> super<00:19:09.960> easy 00:19:10.270 --> 00:19:10.280 align:start position:0% it suddenly becomes like a super easy 00:19:10.280 --> 00:19:14.149 align:start position:0% it suddenly becomes like a super easy crit<00:19:11.440> um<00:19:12.440> and<00:19:13.000> just<00:19:13.240> making<00:19:13.559> a<00:19:13.720> list<00:19:13.960> or 00:19:14.149 --> 00:19:14.159 align:start position:0% crit um and just making a list or 00:19:14.159 --> 00:19:16.630 align:start position:0% crit um and just making a list or keeping<00:19:14.400> a<00:19:14.559> list<00:19:15.000> on<00:19:15.159> a<00:19:15.320> piece<00:19:15.520> of<00:19:15.720> paper<00:19:16.320> or 00:19:16.630 --> 00:19:16.640 align:start position:0% keeping a list on a piece of paper or 00:19:16.640 --> 00:19:19.110 align:start position:0% keeping a list on a piece of paper or whatever<00:19:16.919> note<00:19:17.200> taking<00:19:17.520> app<00:19:17.840> you<00:19:18.159> prefer 00:19:19.110 --> 00:19:19.120 align:start position:0% whatever note taking app you prefer 00:19:19.120 --> 00:19:21.590 align:start position:0% whatever note taking app you prefer Apple<00:19:19.440> notes<00:19:20.039> could<00:19:20.200> be<00:19:20.440> whatever<00:19:21.320> uh<00:19:21.440> just 00:19:21.590 --> 00:19:21.600 align:start position:0% Apple notes could be whatever uh just 00:19:21.600 --> 00:19:23.950 align:start position:0% Apple notes could be whatever uh just keeping<00:19:21.960> like<00:19:22.080> a<00:19:22.200> bullet<00:19:22.600> pointed<00:19:23.000> list<00:19:23.520> hey<00:19:23.799> I 00:19:23.950 --> 00:19:23.960 align:start position:0% keeping like a bullet pointed list hey I 00:19:23.960 --> 00:19:27.590 align:start position:0% keeping like a bullet pointed list hey I can<00:19:24.960> trick<00:19:25.280> the<00:19:25.440> system<00:19:25.760> into<00:19:26.039> doing<00:19:26.400> this<00:19:27.320> uh 00:19:27.590 --> 00:19:27.600 align:start position:0% can trick the system into doing this uh 00:19:27.600 --> 00:19:30.909 align:start position:0% can trick the system into doing this uh it's<00:19:28.159> not<00:19:28.360> a<00:19:28.720> security<00:19:29.200> risk<00:19:29.640> but<00:19:29.760> it<00:19:29.960> might<00:19:30.120> be 00:19:30.909 --> 00:19:30.919 align:start position:0% it's not a security risk but it might be 00:19:30.919 --> 00:19:33.149 align:start position:0% it's not a security risk but it might be helpful<00:19:31.919> that's<00:19:32.120> going<00:19:32.240> to<00:19:32.360> set<00:19:32.559> you<00:19:32.720> up<00:19:32.880> for 00:19:33.149 --> 00:19:33.159 align:start position:0% helpful that's going to set you up for 00:19:33.159 --> 00:19:35.070 align:start position:0% helpful that's going to set you up for success<00:19:33.559> in<00:19:33.760> building<00:19:34.120> these<00:19:34.320> skill<00:19:34.600> chains 00:19:35.070 --> 00:19:35.080 align:start position:0% success in building these skill chains 00:19:35.080 --> 00:19:38.230 align:start position:0% success in building these skill chains and<00:19:35.840> basically<00:19:36.280> escalating<00:19:37.200> a<00:19:37.480> vulnerability 00:19:38.230 --> 00:19:38.240 align:start position:0% and basically escalating a vulnerability 00:19:38.240 --> 00:19:41.110 align:start position:0% and basically escalating a vulnerability from<00:19:38.640> maybe<00:19:38.880> medium<00:19:39.240> or<00:19:39.480> high<00:19:39.799> to<00:19:39.960> a<00:19:40.159> critical 00:19:41.110 --> 00:19:41.120 align:start position:0% from maybe medium or high to a critical 00:19:41.120 --> 00:19:44.510 align:start position:0% from maybe medium or high to a critical with<00:19:41.400> a<00:19:41.520> lot<00:19:41.679> of<00:19:42.080> impact<00:19:43.080> all<00:19:43.280> right<00:19:43.919> with<00:19:44.120> that 00:19:44.510 --> 00:19:44.520 align:start position:0% with a lot of impact all right with that 00:19:44.520 --> 00:19:47.230 align:start position:0% with a lot of impact all right with that I'll<00:19:44.760> give<00:19:44.919> it<00:19:45.080> over 00:19:47.230 --> 00:19:47.240 align:start position:0% I'll give it over 00:19:47.240 --> 00:19:50.510 align:start position:0% I'll give it over to 00:19:50.510 --> 00:19:50.520 align:start position:0% 00:19:50.520 --> 00:19:55.510 align:start position:0% [Applause] 00:19:55.510 --> 00:19:55.520 align:start position:0% 00:19:55.520 --> 00:19:58.270 align:start position:0% mat<00:19:56.520> all<00:19:56.679> right<00:19:56.960> just<00:19:57.159> a<00:19:57.360> raise<00:19:57.559> of<00:19:57.760> hands<00:19:58.120> how 00:19:58.270 --> 00:19:58.280 align:start position:0% mat all right just a raise of hands how 00:19:58.280 --> 00:20:02.630 align:start position:0% mat all right just a raise of hands how many<00:19:58.480> of<00:19:58.799> you<00:19:59.000> here<00:19:59.240> are 00:20:02.630 --> 00:20:02.640 align:start position:0% 00:20:02.640 --> 00:20:05.590 align:start position:0% developers<00:20:03.640> okay<00:20:03.799> a<00:20:03.960> good<00:20:04.240> chunk<00:20:05.240> um<00:20:05.480> all 00:20:05.590 --> 00:20:05.600 align:start position:0% developers okay a good chunk um all 00:20:05.600 --> 00:20:07.630 align:start position:0% developers okay a good chunk um all right<00:20:05.760> so<00:20:05.919> my<00:20:06.080> next<00:20:06.280> few<00:20:06.520> tips<00:20:07.240> um<00:20:07.400> as<00:20:07.520> I 00:20:07.630 --> 00:20:07.640 align:start position:0% right so my next few tips um as I 00:20:07.640 --> 00:20:09.230 align:start position:0% right so my next few tips um as I mentioned<00:20:08.039> before<00:20:08.320> I'm<00:20:08.480> going<00:20:08.679> to<00:20:08.880> kind<00:20:09.000> of 00:20:09.230 --> 00:20:09.240 align:start position:0% mentioned before I'm going to kind of 00:20:09.240 --> 00:20:13.350 align:start position:0% mentioned before I'm going to kind of split<00:20:10.000> between<00:20:11.000> um<00:20:11.559> developer<00:20:12.559> based<00:20:13.120> and 00:20:13.350 --> 00:20:13.360 align:start position:0% split between um developer based and 00:20:13.360 --> 00:20:16.590 align:start position:0% split between um developer based and security<00:20:13.799> researcher<00:20:14.360> based<00:20:15.240> just<00:20:15.600> because 00:20:16.590 --> 00:20:16.600 align:start position:0% security researcher based just because 00:20:16.600 --> 00:20:19.549 align:start position:0% security researcher based just because um<00:20:17.480> I<00:20:17.640> guess<00:20:17.880> I've<00:20:18.200> been<00:20:18.440> a<00:20:18.640> developer<00:20:19.120> for 00:20:19.549 --> 00:20:19.559 align:start position:0% um I guess I've been a developer for 00:20:19.559 --> 00:20:21.830 align:start position:0% um I guess I've been a developer for almost<00:20:19.919> as<00:20:20.039> long<00:20:20.240> as<00:20:20.400> I<00:20:20.520> was<00:20:20.720> a<00:20:21.280> as<00:20:21.400> I<00:20:21.520> am<00:20:21.679> a 00:20:21.830 --> 00:20:21.840 align:start position:0% almost as long as I was a as I am a 00:20:21.840 --> 00:20:24.870 align:start position:0% almost as long as I was a as I am a security<00:20:22.679> researcher<00:20:23.679> um<00:20:24.120> and<00:20:24.440> it<00:20:24.600> kind<00:20:24.720> of 00:20:24.870 --> 00:20:24.880 align:start position:0% security researcher um and it kind of 00:20:24.880 --> 00:20:30.230 align:start position:0% security researcher um and it kind of ties<00:20:25.200> into<00:20:25.799> even<00:20:26.080> my<00:20:26.240> current<00:20:26.559> roles 00:20:30.230 --> 00:20:30.240 align:start position:0% 00:20:30.240 --> 00:20:34.029 align:start position:0% all<00:20:30.400> right<00:20:30.679> so<00:20:31.240> tip<00:20:31.960> one<00:20:32.559> is<00:20:33.200> um<00:20:33.400> architect 00:20:34.029 --> 00:20:34.039 align:start position:0% all right so tip one is um architect 00:20:34.039 --> 00:20:37.190 align:start position:0% all right so tip one is um architect first<00:20:34.640> code<00:20:34.919> later<00:20:35.840> um<00:20:36.240> there's<00:20:36.799> nothing 00:20:37.190 --> 00:20:37.200 align:start position:0% first code later um there's nothing 00:20:37.200 --> 00:20:40.630 align:start position:0% first code later um there's nothing worse<00:20:38.120> than<00:20:38.799> a<00:20:39.000> as<00:20:39.120> a<00:20:39.280> security<00:20:39.679> researcher<00:20:40.440> or 00:20:40.630 --> 00:20:40.640 align:start position:0% worse than a as a security researcher or 00:20:40.640 --> 00:20:43.310 align:start position:0% worse than a as a security researcher or a<00:20:40.799> developer<00:20:41.760> than<00:20:41.960> trying<00:20:42.200> to<00:20:42.360> fix<00:20:42.600> your<00:20:42.760> bugs 00:20:43.310 --> 00:20:43.320 align:start position:0% a developer than trying to fix your bugs 00:20:43.320 --> 00:20:47.070 align:start position:0% a developer than trying to fix your bugs and<00:20:43.480> then<00:20:43.640> realizing<00:20:44.240> that<00:20:44.919> one<00:20:45.720> bug<00:20:46.080> fix 00:20:47.070 --> 00:20:47.080 align:start position:0% and then realizing that one bug fix 00:20:47.080 --> 00:20:48.950 align:start position:0% and then realizing that one bug fix results<00:20:47.480> in<00:20:47.679> something<00:20:47.919> else<00:20:48.240> happening 00:20:48.950 --> 00:20:48.960 align:start position:0% results in something else happening 00:20:48.960 --> 00:20:51.110 align:start position:0% results in something else happening which<00:20:49.080> means<00:20:49.320> you<00:20:49.480> can't<00:20:49.720> fix<00:20:49.919> it<00:20:50.120> anymore<00:20:51.000> and 00:20:51.110 --> 00:20:51.120 align:start position:0% which means you can't fix it anymore and 00:20:51.120 --> 00:20:53.630 align:start position:0% which means you can't fix it anymore and you<00:20:51.280> have<00:20:51.400> to<00:20:51.880> Band-Aid<00:20:52.400> patch<00:20:52.720> another<00:20:53.039> thing 00:20:53.630 --> 00:20:53.640 align:start position:0% you have to Band-Aid patch another thing 00:20:53.640 --> 00:20:55.029 align:start position:0% you have to Band-Aid patch another thing and<00:20:53.760> then<00:20:53.960> that<00:20:54.200> thing<00:20:54.360> can't<00:20:54.559> be<00:20:54.679> fixed 00:20:55.029 --> 00:20:55.039 align:start position:0% and then that thing can't be fixed 00:20:55.039 --> 00:20:55.990 align:start position:0% and then that thing can't be fixed because<00:20:55.159> you<00:20:55.240> have<00:20:55.320> to<00:20:55.400> Band-Aid<00:20:55.760> patch 00:20:55.990 --> 00:20:56.000 align:start position:0% because you have to Band-Aid patch 00:20:56.000 --> 00:20:58.590 align:start position:0% because you have to Band-Aid patch another<00:20:56.400> thing<00:20:57.400> um<00:20:57.679> as<00:20:57.799> a<00:20:57.960> security<00:20:58.320> res 00:20:58.590 --> 00:20:58.600 align:start position:0% another thing um as a security res 00:20:58.600 --> 00:21:00.190 align:start position:0% another thing um as a security res researcher<00:20:59.360> that<00:20:59.559> nothing<00:20:59.840> is<00:21:00.000> more 00:21:00.190 --> 00:21:00.200 align:start position:0% researcher that nothing is more 00:21:00.200 --> 00:21:02.390 align:start position:0% researcher that nothing is more dangerous<00:21:00.720> than<00:21:00.960> this<00:21:01.679> but<00:21:01.880> also<00:21:02.120> as<00:21:02.240> a 00:21:02.390 --> 00:21:02.400 align:start position:0% dangerous than this but also as a 00:21:02.400 --> 00:21:05.149 align:start position:0% dangerous than this but also as a developer<00:21:03.120> it<00:21:03.360> becomes<00:21:03.840> really<00:21:04.159> hard<00:21:04.559> to 00:21:05.149 --> 00:21:05.159 align:start position:0% developer it becomes really hard to 00:21:05.159 --> 00:21:08.149 align:start position:0% developer it becomes really hard to manipulate<00:21:05.679> your<00:21:05.880> code<00:21:06.240> to<00:21:06.440> add<00:21:06.679> new<00:21:07.159> features 00:21:08.149 --> 00:21:08.159 align:start position:0% manipulate your code to add new features 00:21:08.159 --> 00:21:11.950 align:start position:0% manipulate your code to add new features um<00:21:08.320> to<00:21:08.640> add<00:21:09.520> behavior<00:21:10.520> um<00:21:10.720> when<00:21:10.919> you<00:21:11.159> have<00:21:11.640> new 00:21:11.950 --> 00:21:11.960 align:start position:0% um to add behavior um when you have new 00:21:11.960 --> 00:21:14.750 align:start position:0% um to add behavior um when you have new code<00:21:12.240> that<00:21:12.360> you<00:21:12.440> want<00:21:12.559> to<00:21:12.799> add<00:21:13.760> um<00:21:14.159> and<00:21:14.559> at<00:21:14.679> the 00:21:14.750 --> 00:21:14.760 align:start position:0% code that you want to add um and at the 00:21:14.760 --> 00:21:16.390 align:start position:0% code that you want to add um and at the end<00:21:14.919> of<00:21:15.000> the<00:21:15.120> day<00:21:15.279> it<00:21:15.400> makes<00:21:15.600> your<00:21:15.840> code<00:21:16.200> much 00:21:16.390 --> 00:21:16.400 align:start position:0% end of the day it makes your code much 00:21:16.400 --> 00:21:18.590 align:start position:0% end of the day it makes your code much harder<00:21:16.679> to<00:21:16.840> read<00:21:17.840> um<00:21:18.000> that<00:21:18.120> means<00:21:18.360> when<00:21:18.480> you 00:21:18.590 --> 00:21:18.600 align:start position:0% harder to read um that means when you 00:21:18.600 --> 00:21:21.269 align:start position:0% harder to read um that means when you bring<00:21:18.799> new<00:21:19.039> developers<00:21:19.559> on<00:21:19.880> board<00:21:20.880> um<00:21:21.080> that's 00:21:21.269 --> 00:21:21.279 align:start position:0% bring new developers on board um that's 00:21:21.279 --> 00:21:23.870 align:start position:0% bring new developers on board um that's more<00:21:21.600> time<00:21:21.799> it<00:21:21.960> takes<00:21:22.240> for<00:21:22.760> a<00:21:22.919> developer<00:21:23.360> to 00:21:23.870 --> 00:21:23.880 align:start position:0% more time it takes for a developer to 00:21:23.880 --> 00:21:26.909 align:start position:0% more time it takes for a developer to understand<00:21:24.039> your<00:21:24.400> system<00:21:25.400> um<00:21:26.000> and<00:21:26.400> more<00:21:26.679> time 00:21:26.909 --> 00:21:26.919 align:start position:0% understand your system um and more time 00:21:26.919 --> 00:21:30.669 align:start position:0% understand your system um and more time for<00:21:27.240> security<00:21:27.679> researchers<00:21:28.640> in<00:21:29.200> a<00:21:29.400> review<00:21:30.039> or 00:21:30.669 --> 00:21:30.679 align:start position:0% for security researchers in a review or 00:21:30.679 --> 00:21:32.269 align:start position:0% for security researchers in a review or in<00:21:30.799> a<00:21:30.919> bug<00:21:31.120> bount<00:21:31.400> teach<00:21:31.559> to<00:21:31.960> understand<00:21:32.159> what 00:21:32.269 --> 00:21:32.279 align:start position:0% in a bug bount teach to understand what 00:21:32.279 --> 00:21:36.430 align:start position:0% in a bug bount teach to understand what you're<00:21:32.400> trying<00:21:32.600> to<00:21:33.000> do<00:21:34.000> um<00:21:34.520> I<00:21:34.640> think<00:21:35.039> this<00:21:35.279> is 00:21:36.430 --> 00:21:36.440 align:start position:0% you're trying to do um I think this is 00:21:36.440 --> 00:21:39.470 align:start position:0% you're trying to do um I think this is probably<00:21:37.440> um<00:21:37.679> one<00:21:37.799> of<00:21:38.120> the<00:21:38.400> most<00:21:39.240> uh 00:21:39.470 --> 00:21:39.480 align:start position:0% probably um one of the most uh 00:21:39.480 --> 00:21:42.110 align:start position:0% probably um one of the most uh underrated<00:21:40.480> techniques<00:21:41.279> is<00:21:41.520> just<00:21:41.679> to<00:21:41.880> really 00:21:42.110 --> 00:21:42.120 align:start position:0% underrated techniques is just to really 00:21:42.120 --> 00:21:44.870 align:start position:0% underrated techniques is just to really think<00:21:42.360> about<00:21:42.600> your<00:21:42.799> code<00:21:43.679> um<00:21:43.880> figure<00:21:44.159> out<00:21:44.720> how 00:21:44.870 --> 00:21:44.880 align:start position:0% think about your code um figure out how 00:21:44.880 --> 00:21:47.029 align:start position:0% think about your code um figure out how do<00:21:45.039> you<00:21:45.480> what<00:21:45.720> what<00:21:45.840> do<00:21:45.960> you<00:21:46.120> want<00:21:46.440> your<00:21:46.720> system 00:21:47.029 --> 00:21:47.039 align:start position:0% do you what what do you want your system 00:21:47.039 --> 00:21:50.789 align:start position:0% do you what what do you want your system to<00:21:47.240> do<00:21:48.080> um<00:21:48.279> how<00:21:48.400> do<00:21:48.480> you<00:21:48.600> want<00:21:48.679> to<00:21:48.880> build<00:21:49.159> it<00:21:50.000> um 00:21:50.789 --> 00:21:50.799 align:start position:0% to do um how do you want to build it um 00:21:50.799 --> 00:21:52.789 align:start position:0% to do um how do you want to build it um identify<00:21:51.559> you<00:21:51.640> know<00:21:51.799> the<00:21:51.960> architecture<00:21:52.679> of 00:21:52.789 --> 00:21:52.799 align:start position:0% identify you know the architecture of 00:21:52.799 --> 00:21:55.870 align:start position:0% identify you know the architecture of your<00:21:53.000> contracts<00:21:53.720> of<00:21:54.000> of<00:21:54.200> whatever<00:21:54.640> your<00:21:55.559> um 00:21:55.870 --> 00:21:55.880 align:start position:0% your contracts of of whatever your um 00:21:55.880 --> 00:21:58.590 align:start position:0% your contracts of of whatever your um system<00:21:56.240> is<00:21:56.400> supposed<00:21:56.720> to<00:21:56.880> do<00:21:57.720> um<00:21:57.960> and<00:21:58.120> code<00:21:58.320> it 00:21:58.590 --> 00:21:58.600 align:start position:0% system is supposed to do um and code it 00:21:58.600 --> 00:22:00.630 align:start position:0% system is supposed to do um and code it later<00:21:59.039> and<00:21:59.159> I<00:21:59.279> know<00:21:59.520> that's<00:21:59.760> hard<00:22:00.200> because 00:22:00.630 --> 00:22:00.640 align:start position:0% later and I know that's hard because 00:22:00.640 --> 00:22:03.149 align:start position:0% later and I know that's hard because even<00:22:01.080> I<00:22:01.720> tend<00:22:01.960> to<00:22:02.240> sit<00:22:02.440> at<00:22:02.520> a<00:22:02.640> computer<00:22:03.000> and 00:22:03.149 --> 00:22:03.159 align:start position:0% even I tend to sit at a computer and 00:22:03.159 --> 00:22:06.310 align:start position:0% even I tend to sit at a computer and just<00:22:03.320> write<00:22:03.559> code<00:22:04.440> um<00:22:04.919> but<00:22:05.080> I<00:22:05.159> will<00:22:05.400> say<00:22:05.720> for<00:22:06.080> a 00:22:06.310 --> 00:22:06.320 align:start position:0% just write code um but I will say for a 00:22:06.320 --> 00:22:09.310 align:start position:0% just write code um but I will say for a project<00:22:06.880> that<00:22:07.799> go<00:22:08.039> under<00:22:08.360> goes<00:22:08.760> continuous 00:22:09.310 --> 00:22:09.320 align:start position:0% project that go under goes continuous 00:22:09.320 --> 00:22:12.190 align:start position:0% project that go under goes continuous development<00:22:09.919> and<00:22:10.159> continuous<00:22:10.960> features<00:22:11.960> um 00:22:12.190 --> 00:22:12.200 align:start position:0% development and continuous features um 00:22:12.200 --> 00:22:14.669 align:start position:0% development and continuous features um following<00:22:12.720> this<00:22:12.880> kind<00:22:13.000> of<00:22:13.200> practice<00:22:13.600> makes<00:22:14.440> um 00:22:14.669 --> 00:22:14.679 align:start position:0% following this kind of practice makes um 00:22:14.679 --> 00:22:20.070 align:start position:0% following this kind of practice makes um just<00:22:15.039> reading<00:22:15.440> that<00:22:15.640> code<00:22:16.200> much 00:22:20.070 --> 00:22:20.080 align:start position:0% 00:22:20.080 --> 00:22:22.789 align:start position:0% easier<00:22:21.080> this<00:22:21.240> is<00:22:21.520> kind<00:22:21.720> of<00:22:21.919> related<00:22:22.279> to<00:22:22.559> maybe 00:22:22.789 --> 00:22:22.799 align:start position:0% easier this is kind of related to maybe 00:22:22.799 --> 00:22:25.830 align:start position:0% easier this is kind of related to maybe one<00:22:22.919> of<00:22:23.039> the<00:22:23.200> previous<00:22:23.679> tips<00:22:24.679> um<00:22:25.120> document 00:22:25.830 --> 00:22:25.840 align:start position:0% one of the previous tips um document 00:22:25.840 --> 00:22:29.430 align:start position:0% one of the previous tips um document everything<00:22:26.840> I<00:22:26.960> think<00:22:27.640> from<00:22:28.080> a<00:22:28.520> security 00:22:29.430 --> 00:22:29.440 align:start position:0% everything I think from a security 00:22:29.440 --> 00:22:31.870 align:start position:0% everything I think from a security researcher<00:22:30.080> point<00:22:30.240> of<00:22:30.400> view<00:22:31.080> there's<00:22:31.320> so<00:22:31.520> many 00:22:31.870 --> 00:22:31.880 align:start position:0% researcher point of view there's so many 00:22:31.880 --> 00:22:35.110 align:start position:0% researcher point of view there's so many issues<00:22:32.400> that<00:22:32.559> we<00:22:32.799> try<00:22:33.240> to<00:22:34.240> uh<00:22:34.360> find<00:22:34.640> in<00:22:34.880> code 00:22:35.110 --> 00:22:35.120 align:start position:0% issues that we try to uh find in code 00:22:35.120 --> 00:22:37.190 align:start position:0% issues that we try to uh find in code bases<00:22:35.559> and<00:22:35.760> they're<00:22:36.000> because<00:22:36.480> they're<00:22:36.919> either 00:22:37.190 --> 00:22:37.200 align:start position:0% bases and they're because they're either 00:22:37.200 --> 00:22:40.430 align:start position:0% bases and they're because they're either wrong<00:22:37.520> assumptions<00:22:38.440> or<00:22:39.120> invariants<00:22:40.080> that 00:22:40.430 --> 00:22:40.440 align:start position:0% wrong assumptions or invariants that 00:22:40.440 --> 00:22:43.750 align:start position:0% wrong assumptions or invariants that maybe<00:22:40.720> aren't<00:22:41.400> correct<00:22:42.400> um<00:22:43.039> yeah<00:22:43.240> sure<00:22:43.559> the 00:22:43.750 --> 00:22:43.760 align:start position:0% maybe aren't correct um yeah sure the 00:22:43.760 --> 00:22:45.950 align:start position:0% maybe aren't correct um yeah sure the documentation<00:22:44.600> might<00:22:44.840> not<00:22:45.400> accurately 00:22:45.950 --> 00:22:45.960 align:start position:0% documentation might not accurately 00:22:45.960 --> 00:22:48.350 align:start position:0% documentation might not accurately reflect<00:22:46.679> what<00:22:46.840> the<00:22:47.000> contract<00:22:47.520> or<00:22:47.720> the<00:22:47.880> co<00:22:48.120> code 00:22:48.350 --> 00:22:48.360 align:start position:0% reflect what the contract or the co code 00:22:48.360 --> 00:22:51.870 align:start position:0% reflect what the contract or the co code is<00:22:48.520> supposed<00:22:48.840> to<00:22:49.039> do<00:22:50.039> um<00:22:50.720> but<00:22:51.039> as<00:22:51.159> a<00:22:51.320> developer 00:22:51.870 --> 00:22:51.880 align:start position:0% is supposed to do um but as a developer 00:22:51.880 --> 00:22:56.510 align:start position:0% is supposed to do um but as a developer putting<00:22:52.240> the<00:22:53.039> actual<00:22:54.039> um<00:22:54.440> effort<00:22:55.360> into<00:22:56.360> uh 00:22:56.510 --> 00:22:56.520 align:start position:0% putting the actual um effort into uh 00:22:56.520 --> 00:22:58.510 align:start position:0% putting the actual um effort into uh like<00:22:56.840> documenting<00:22:57.760> what<00:22:57.919> you<00:22:58.039> want<00:22:58.159> your 00:22:58.510 --> 00:22:58.520 align:start position:0% like documenting what you want your 00:22:58.520 --> 00:23:00.990 align:start position:0% like documenting what you want your system<00:22:58.799> to<00:22:58.960> do<00:22:59.720> um<00:22:59.919> how<00:23:00.240> certain<00:23:00.559> functions 00:23:00.990 --> 00:23:01.000 align:start position:0% system to do um how certain functions 00:23:01.000 --> 00:23:03.350 align:start position:0% system to do um how certain functions work<00:23:01.279> what<00:23:01.400> the<00:23:01.600> expectations<00:23:02.240> are<00:23:03.000> um<00:23:03.240> that 00:23:03.350 --> 00:23:03.360 align:start position:0% work what the expectations are um that 00:23:03.360 --> 00:23:06.830 align:start position:0% work what the expectations are um that can<00:23:03.480> do<00:23:03.679> a<00:23:03.840> lot<00:23:04.240> to<00:23:05.159> actually<00:23:05.520> helping<00:23:06.440> um 00:23:06.830 --> 00:23:06.840 align:start position:0% can do a lot to actually helping um 00:23:06.840 --> 00:23:09.070 align:start position:0% can do a lot to actually helping um other<00:23:07.039> people<00:23:07.679> understand<00:23:07.840> your<00:23:08.039> code<00:23:09.000> I 00:23:09.070 --> 00:23:09.080 align:start position:0% other people understand your code I 00:23:09.080 --> 00:23:11.549 align:start position:0% other people understand your code I think<00:23:09.279> there's<00:23:09.679> also<00:23:10.320> been<00:23:10.760> a<00:23:10.880> lot<00:23:11.039> of<00:23:11.240> times 00:23:11.549 --> 00:23:11.559 align:start position:0% think there's also been a lot of times 00:23:11.559 --> 00:23:13.990 align:start position:0% think there's also been a lot of times looking<00:23:11.799> at<00:23:12.000> certain<00:23:12.559> functions<00:23:13.559> um<00:23:13.720> certain 00:23:13.990 --> 00:23:14.000 align:start position:0% looking at certain functions um certain 00:23:14.000 --> 00:23:16.390 align:start position:0% looking at certain functions um certain code<00:23:14.279> bases<00:23:14.840> and<00:23:14.960> then<00:23:15.159> realizing<00:23:15.840> that 00:23:16.390 --> 00:23:16.400 align:start position:0% code bases and then realizing that 00:23:16.400 --> 00:23:18.789 align:start position:0% code bases and then realizing that everything<00:23:17.120> all<00:23:17.279> the<00:23:17.480> documentation<00:23:18.400> doesn't 00:23:18.789 --> 00:23:18.799 align:start position:0% everything all the documentation doesn't 00:23:18.799 --> 00:23:21.110 align:start position:0% everything all the documentation doesn't actually<00:23:19.080> match<00:23:19.400> the<00:23:19.960> implementation<00:23:20.960> and 00:23:21.110 --> 00:23:21.120 align:start position:0% actually match the implementation and 00:23:21.120 --> 00:23:23.590 align:start position:0% actually match the implementation and then<00:23:21.600> for<00:23:22.000> security<00:23:22.480> research<00:23:22.960> is<00:23:23.200> we<00:23:23.360> have<00:23:23.480> to 00:23:23.590 --> 00:23:23.600 align:start position:0% then for security research is we have to 00:23:23.600 --> 00:23:25.510 align:start position:0% then for security research is we have to spend<00:23:23.880> a<00:23:24.039> lot<00:23:24.159> of<00:23:24.400> time<00:23:24.600> trying<00:23:24.840> to<00:23:25.000> figure<00:23:25.240> out 00:23:25.510 --> 00:23:25.520 align:start position:0% spend a lot of time trying to figure out 00:23:25.520 --> 00:23:27.830 align:start position:0% spend a lot of time trying to figure out all<00:23:25.679> right<00:23:25.919> if<00:23:26.120> that<00:23:26.559> documentation<00:23:27.559> or<00:23:27.679> if 00:23:27.830 --> 00:23:27.840 align:start position:0% all right if that documentation or if 00:23:27.840 --> 00:23:29.789 align:start position:0% all right if that documentation or if that<00:23:27.960> line<00:23:28.240> is<00:23:28.559> n<00:23:28.799> correct<00:23:29.279> what<00:23:29.440> is<00:23:29.559> it 00:23:29.789 --> 00:23:29.799 align:start position:0% that line is n correct what is it 00:23:29.799 --> 00:23:32.390 align:start position:0% that line is n correct what is it actually<00:23:30.159> doing<00:23:31.159> um<00:23:31.360> it<00:23:31.480> can<00:23:31.640> help<00:23:31.919> save<00:23:32.120> a<00:23:32.279> lot 00:23:32.390 --> 00:23:32.400 align:start position:0% actually doing um it can help save a lot 00:23:32.400 --> 00:23:35.029 align:start position:0% actually doing um it can help save a lot of<00:23:32.640> time<00:23:33.400> um<00:23:33.799> in<00:23:33.960> order<00:23:34.200> to<00:23:34.360> bring<00:23:34.600> people<00:23:34.880> on 00:23:35.029 --> 00:23:35.039 align:start position:0% of time um in order to bring people on 00:23:35.039 --> 00:23:37.350 align:start position:0% of time um in order to bring people on board<00:23:35.360> as 00:23:37.350 --> 00:23:37.360 align:start position:0% board as 00:23:37.360 --> 00:23:40.590 align:start position:0% board as well<00:23:38.360> all<00:23:38.480> right<00:23:38.760> this<00:23:38.919> one<00:23:39.679> I'm<00:23:40.039> I'm<00:23:40.200> sorry 00:23:40.590 --> 00:23:40.600 align:start position:0% well all right this one I'm I'm sorry 00:23:40.600 --> 00:23:42.909 align:start position:0% well all right this one I'm I'm sorry for<00:23:40.840> all<00:23:41.039> your<00:23:41.240> develop<00:23:41.640> you<00:23:41.880> developers<00:23:42.600> but 00:23:42.909 --> 00:23:42.919 align:start position:0% for all your develop you developers but 00:23:42.919 --> 00:23:46.350 align:start position:0% for all your develop you developers but simultaneously<00:23:43.799> test<00:23:44.080> and<00:23:44.400> code<00:23:45.400> um<00:23:46.039> yeah<00:23:46.279> I 00:23:46.350 --> 00:23:46.360 align:start position:0% simultaneously test and code um yeah I 00:23:46.360 --> 00:23:48.909 align:start position:0% simultaneously test and code um yeah I know<00:23:46.720> tests<00:23:47.159> aren't<00:23:47.720> that<00:23:47.880> fun<00:23:48.120> to<00:23:48.320> write<00:23:48.760> and 00:23:48.909 --> 00:23:48.919 align:start position:0% know tests aren't that fun to write and 00:23:48.919 --> 00:23:50.549 align:start position:0% know tests aren't that fun to write and I've<00:23:49.080> been<00:23:49.240> in<00:23:49.440> that<00:23:49.640> space<00:23:50.080> I've<00:23:50.200> been<00:23:50.400> in 00:23:50.549 --> 00:23:50.559 align:start position:0% I've been in that space I've been in 00:23:50.559 --> 00:23:54.789 align:start position:0% I've been in that space I've been in that<00:23:50.919> mindset<00:23:51.919> um<00:23:52.240> but<00:23:52.400> I<00:23:52.600> will<00:23:52.960> say<00:23:53.960> that<00:23:54.640> it 00:23:54.789 --> 00:23:54.799 align:start position:0% that mindset um but I will say that it 00:23:54.799 --> 00:23:56.269 align:start position:0% that mindset um but I will say that it does<00:23:55.080> help<00:23:55.320> you<00:23:55.640> think<00:23:55.919> about<00:23:56.080> your 00:23:56.269 --> 00:23:56.279 align:start position:0% does help you think about your 00:23:56.279 --> 00:23:58.870 align:start position:0% does help you think about your invariance<00:23:57.080> it<00:23:57.200> does<00:23:57.559> think<00:23:57.760> help<00:23:58.000> you<00:23:58.679> or 00:23:58.870 --> 00:23:58.880 align:start position:0% invariance it does think help you or 00:23:58.880 --> 00:24:01.669 align:start position:0% invariance it does think help you or forces<00:23:59.360> you<00:24:00.039> to<00:24:00.400> think<00:24:00.720> about<00:24:01.120> how<00:24:01.320> you<00:24:01.480> want 00:24:01.669 --> 00:24:01.679 align:start position:0% forces you to think about how you want 00:24:01.679 --> 00:24:04.149 align:start position:0% forces you to think about how you want your<00:24:01.880> system<00:24:02.240> to<00:24:02.440> work<00:24:03.320> um<00:24:03.440> and<00:24:03.559> it<00:24:03.640> forces<00:24:04.000> you 00:24:04.149 --> 00:24:04.159 align:start position:0% your system to work um and it forces you 00:24:04.159 --> 00:24:06.789 align:start position:0% your system to work um and it forces you to<00:24:04.679> like<00:24:05.000> actually<00:24:05.600> test<00:24:06.000> the<00:24:06.120> outputs<00:24:06.640> of 00:24:06.789 --> 00:24:06.799 align:start position:0% to like actually test the outputs of 00:24:06.799 --> 00:24:09.029 align:start position:0% to like actually test the outputs of your<00:24:07.000> function<00:24:08.000> which<00:24:08.159> you<00:24:08.279> wouldn't<00:24:08.840> be 00:24:09.029 --> 00:24:09.039 align:start position:0% your function which you wouldn't be 00:24:09.039 --> 00:24:10.510 align:start position:0% your function which you wouldn't be doing<00:24:09.480> if<00:24:09.600> you<00:24:09.720> were<00:24:09.880> just<00:24:10.039> writing<00:24:10.360> the 00:24:10.510 --> 00:24:10.520 align:start position:0% doing if you were just writing the 00:24:10.520 --> 00:24:12.830 align:start position:0% doing if you were just writing the function<00:24:11.520> um<00:24:11.640> you<00:24:11.760> wouldn't<00:24:12.080> necessarily<00:24:12.640> be 00:24:12.830 --> 00:24:12.840 align:start position:0% function um you wouldn't necessarily be 00:24:12.840 --> 00:24:15.230 align:start position:0% function um you wouldn't necessarily be thinking<00:24:13.279> about<00:24:14.240> um<00:24:14.480> how<00:24:14.640> a<00:24:14.760> function<00:24:15.080> is 00:24:15.230 --> 00:24:15.240 align:start position:0% thinking about um how a function is 00:24:15.240 --> 00:24:17.669 align:start position:0% thinking about um how a function is supposed<00:24:15.559> to<00:24:15.840> behave<00:24:16.840> um<00:24:17.120> if<00:24:17.240> you<00:24:17.320> weren't 00:24:17.669 --> 00:24:17.679 align:start position:0% supposed to behave um if you weren't 00:24:17.679 --> 00:24:20.190 align:start position:0% supposed to behave um if you weren't actually<00:24:17.919> writing<00:24:18.279> the<00:24:18.440> test<00:24:18.840> with<00:24:19.039> it<00:24:20.039> this 00:24:20.190 --> 00:24:20.200 align:start position:0% actually writing the test with it this 00:24:20.200 --> 00:24:22.549 align:start position:0% actually writing the test with it this can<00:24:20.480> help<00:24:20.880> with<00:24:21.360> at<00:24:21.559> the<00:24:21.720> very<00:24:22.000> least 00:24:22.549 --> 00:24:22.559 align:start position:0% can help with at the very least 00:24:22.559 --> 00:24:24.430 align:start position:0% can help with at the very least extending<00:24:22.960> your<00:24:23.159> unit<00:24:23.440> tests<00:24:23.840> extending<00:24:24.240> your 00:24:24.430 --> 00:24:24.440 align:start position:0% extending your unit tests extending your 00:24:24.440 --> 00:24:28.430 align:start position:0% extending your unit tests extending your test<00:24:25.000> cases<00:24:26.000> um<00:24:26.320> such<00:24:26.640> that<00:24:27.520> sure<00:24:27.799> maybe<00:24:28.080> your 00:24:28.430 --> 00:24:28.440 align:start position:0% test cases um such that sure maybe your 00:24:28.440 --> 00:24:31.750 align:start position:0% test cases um such that sure maybe your test<00:24:28.840> your<00:24:29.039> test<00:24:29.640> coverage<00:24:30.120> may<00:24:30.279> not<00:24:30.440> be<00:24:30.760> 100% 00:24:31.750 --> 00:24:31.760 align:start position:0% test your test coverage may not be 100% 00:24:31.760 --> 00:24:33.789 align:start position:0% test your test coverage may not be 100% but<00:24:31.919> it<00:24:32.000> will<00:24:32.200> be<00:24:32.480> higher<00:24:33.159> than<00:24:33.320> if<00:24:33.440> you<00:24:33.559> were 00:24:33.789 --> 00:24:33.799 align:start position:0% but it will be higher than if you were 00:24:33.799 --> 00:24:36.230 align:start position:0% but it will be higher than if you were coding<00:24:34.159> and<00:24:34.320> then<00:24:34.480> testing 00:24:36.230 --> 00:24:36.240 align:start position:0% coding and then testing 00:24:36.240 --> 00:24:39.149 align:start position:0% coding and then testing afterwards<00:24:37.240> it<00:24:37.440> also<00:24:37.720> helps<00:24:38.039> to<00:24:38.520> use<00:24:38.919> this 00:24:39.149 --> 00:24:39.159 align:start position:0% afterwards it also helps to use this 00:24:39.159 --> 00:24:42.909 align:start position:0% afterwards it also helps to use this method<00:24:39.480> to<00:24:39.640> test<00:24:39.880> for<00:24:40.080> edge<00:24:40.720> cases<00:24:41.720> um<00:24:42.240> because 00:24:42.909 --> 00:24:42.919 align:start position:0% method to test for edge cases um because 00:24:42.919 --> 00:24:45.470 align:start position:0% method to test for edge cases um because if<00:24:43.039> you're<00:24:43.279> forcing<00:24:43.760> yourself<00:24:44.120> to<00:24:44.360> say<00:24:44.960> like 00:24:45.470 --> 00:24:45.480 align:start position:0% if you're forcing yourself to say like 00:24:45.480 --> 00:24:47.190 align:start position:0% if you're forcing yourself to say like there's<00:24:45.840> like<00:24:46.000> a<00:24:46.320> function<00:24:46.720> with<00:24:46.840> an<00:24:46.960> if 00:24:47.190 --> 00:24:47.200 align:start position:0% there's like a function with an if 00:24:47.200 --> 00:24:48.470 align:start position:0% there's like a function with an if statement<00:24:47.559> that<00:24:47.720> covers<00:24:48.080> like<00:24:48.200> different 00:24:48.470 --> 00:24:48.480 align:start position:0% statement that covers like different 00:24:48.480 --> 00:24:49.470 align:start position:0% statement that covers like different Corner 00:24:49.470 --> 00:24:49.480 align:start position:0% Corner 00:24:49.480 --> 00:24:52.549 align:start position:0% Corner cases<00:24:50.480> having<00:24:50.760> a<00:24:50.960> test<00:24:51.279> for<00:24:51.600> that<00:24:51.840> means<00:24:52.279> that 00:24:52.549 --> 00:24:52.559 align:start position:0% cases having a test for that means that 00:24:52.559 --> 00:24:54.710 align:start position:0% cases having a test for that means that you're<00:24:52.919> also<00:24:53.240> increasing<00:24:53.720> your<00:24:53.880> coverage 00:24:54.710 --> 00:24:54.720 align:start position:0% you're also increasing your coverage 00:24:54.720 --> 00:24:58.549 align:start position:0% you're also increasing your coverage there<00:24:55.720> and<00:24:56.039> I<00:24:56.159> think<00:24:56.399> there's<00:24:57.120> kind<00:24:57.240> of<00:24:57.559> a<00:24:58.120> a 00:24:58.549 --> 00:24:58.559 align:start position:0% there and I think there's kind of a a 00:24:58.559 --> 00:25:00.510 align:start position:0% there and I think there's kind of a a really<00:24:58.919> useful<00:24:59.360> use<00:24:59.720> case<00:24:59.919> for<00:25:00.080> these<00:25:00.240> unit 00:25:00.510 --> 00:25:00.520 align:start position:0% really useful use case for these unit 00:25:00.520 --> 00:25:03.269 align:start position:0% really useful use case for these unit tests<00:25:00.880> is<00:25:01.360> essentially<00:25:01.840> finding<00:25:02.279> bugs<00:25:02.679> before 00:25:03.269 --> 00:25:03.279 align:start position:0% tests is essentially finding bugs before 00:25:03.279 --> 00:25:05.870 align:start position:0% tests is essentially finding bugs before your<00:25:03.520> Security<00:25:04.000> review<00:25:04.799> or<00:25:05.000> finding<00:25:05.480> bugs 00:25:05.870 --> 00:25:05.880 align:start position:0% your Security review or finding bugs 00:25:05.880 --> 00:25:08.870 align:start position:0% your Security review or finding bugs before<00:25:06.399> your<00:25:06.600> bug 00:25:08.870 --> 00:25:08.880 align:start position:0% 00:25:08.880 --> 00:25:13.350 align:start position:0% Bounty<00:25:09.880> all<00:25:10.080> right<00:25:10.640> um<00:25:11.080> this<00:25:11.240> one<00:25:12.000> is<00:25:12.960> uh<00:25:13.240> kind 00:25:13.350 --> 00:25:13.360 align:start position:0% Bounty all right um this one is uh kind 00:25:13.360 --> 00:25:16.149 align:start position:0% Bounty all right um this one is uh kind of<00:25:13.520> related<00:25:13.840> to<00:25:14.080> what<00:25:14.200> I'm<00:25:14.360> saying<00:25:14.679> before<00:25:15.399> is 00:25:16.149 --> 00:25:16.159 align:start position:0% of related to what I'm saying before is 00:25:16.159 --> 00:25:19.269 align:start position:0% of related to what I'm saying before is trying<00:25:16.520> to<00:25:16.760> automate<00:25:17.399> as<00:25:17.559> much<00:25:17.760> as<00:25:17.880> you<00:25:18.080> can<00:25:19.000> um 00:25:19.269 --> 00:25:19.279 align:start position:0% trying to automate as much as you can um 00:25:19.279 --> 00:25:21.389 align:start position:0% trying to automate as much as you can um there's<00:25:19.559> going<00:25:19.760> to<00:25:19.919> be<00:25:20.440> a<00:25:20.559> lot<00:25:20.720> of<00:25:20.840> bugs<00:25:21.279> when 00:25:21.389 --> 00:25:21.399 align:start position:0% there's going to be a lot of bugs when 00:25:21.399 --> 00:25:23.070 align:start position:0% there's going to be a lot of bugs when you<00:25:21.520> write<00:25:21.720> your<00:25:21.880> code<00:25:22.240> that<00:25:22.559> that's<00:25:22.760> already 00:25:23.070 --> 00:25:23.080 align:start position:0% you write your code that that's already 00:25:23.080 --> 00:25:27.430 align:start position:0% you write your code that that's already a<00:25:23.240> known<00:25:24.080> Factor<00:25:25.080> um<00:25:25.559> the<00:25:25.720> more<00:25:26.720> time<00:25:27.120> that<00:25:27.240> you 00:25:27.430 --> 00:25:27.440 align:start position:0% a known Factor um the more time that you 00:25:27.440 --> 00:25:31.110 align:start position:0% a known Factor um the more time that you put<00:25:28.000> in<00:25:28.360> your<00:25:28.520> development<00:25:29.120> process<00:25:29.720> to<00:25:30.720> um 00:25:31.110 --> 00:25:31.120 align:start position:0% put in your development process to um 00:25:31.120 --> 00:25:34.909 align:start position:0% put in your development process to um documenting<00:25:32.080> to<00:25:32.840> testing<00:25:33.840> um<00:25:34.200> the<00:25:34.360> more<00:25:34.600> bugs 00:25:34.909 --> 00:25:34.919 align:start position:0% documenting to testing um the more bugs 00:25:34.919 --> 00:25:37.750 align:start position:0% documenting to testing um the more bugs you'll<00:25:35.200> find<00:25:35.960> when<00:25:36.679> like<00:25:36.880> your<00:25:37.080> code<00:25:37.320> is<00:25:37.559> going 00:25:37.750 --> 00:25:37.760 align:start position:0% you'll find when like your code is going 00:25:37.760 --> 00:25:40.070 align:start position:0% you'll find when like your code is going undergoing<00:25:38.480> development<00:25:39.480> and<00:25:39.640> also<00:25:39.919> the 00:25:40.070 --> 00:25:40.080 align:start position:0% undergoing development and also the 00:25:40.080 --> 00:25:42.389 align:start position:0% undergoing development and also the easier<00:25:40.520> it<00:25:40.679> is<00:25:41.080> generally<00:25:41.559> to<00:25:41.760> actually<00:25:42.039> fix 00:25:42.389 --> 00:25:42.399 align:start position:0% easier it is generally to actually fix 00:25:42.399 --> 00:25:45.909 align:start position:0% easier it is generally to actually fix those<00:25:43.120> issues<00:25:44.120> such<00:25:44.520> that<00:25:45.080> hopefully<00:25:45.720> when 00:25:45.909 --> 00:25:45.919 align:start position:0% those issues such that hopefully when 00:25:45.919 --> 00:25:48.950 align:start position:0% those issues such that hopefully when you<00:25:46.080> get<00:25:46.279> to<00:25:46.520> your<00:25:46.760> Security<00:25:47.200> review<00:25:48.000> or<00:25:48.480> your 00:25:48.950 --> 00:25:48.960 align:start position:0% you get to your Security review or your 00:25:48.960 --> 00:25:52.909 align:start position:0% you get to your Security review or your future<00:25:49.640> security<00:25:50.559> practices<00:25:51.559> um<00:25:52.559> hopefully 00:25:52.909 --> 00:25:52.919 align:start position:0% future security practices um hopefully 00:25:52.919 --> 00:25:54.990 align:start position:0% future security practices um hopefully there's<00:25:53.200> less<00:25:53.600> loow<00:25:53.919> hanging<00:25:54.200> fruit<00:25:54.600> so<00:25:54.799> that 00:25:54.990 --> 00:25:55.000 align:start position:0% there's less loow hanging fruit so that 00:25:55.000 --> 00:25:56.870 align:start position:0% there's less loow hanging fruit so that the<00:25:55.320> security<00:25:55.720> researchers<00:25:56.320> can<00:25:56.559> actually 00:25:56.870 --> 00:25:56.880 align:start position:0% the security researchers can actually 00:25:56.880 --> 00:25:58.950 align:start position:0% the security researchers can actually focus<00:25:57.200> on<00:25:57.360> the<00:25:57.520> really<00:25:57.720> fun 00:25:58.950 --> 00:25:58.960 align:start position:0% focus on the really fun 00:25:58.960 --> 00:26:01.750 align:start position:0% focus on the really fun technical<00:25:59.960> um<00:26:00.240> architectural<00:26:01.240> maybe<00:26:01.480> even 00:26:01.750 --> 00:26:01.760 align:start position:0% technical um architectural maybe even 00:26:01.760 --> 00:26:05.549 align:start position:0% technical um architectural maybe even like<00:26:01.960> protocol<00:26:02.600> level<00:26:03.600> um<00:26:04.240> design<00:26:04.679> concerns 00:26:05.549 --> 00:26:05.559 align:start position:0% like protocol level um design concerns 00:26:05.559 --> 00:26:07.909 align:start position:0% like protocol level um design concerns rather<00:26:05.880> than<00:26:06.679> we<00:26:06.840> found<00:26:07.120> another<00:26:07.399> re-entrancy 00:26:07.909 --> 00:26:07.919 align:start position:0% rather than we found another re-entrancy 00:26:07.919 --> 00:26:11.510 align:start position:0% rather than we found another re-entrancy here<00:26:08.840> um<00:26:09.120> explodable<00:26:09.840> here<00:26:10.240> with<00:26:10.399> this<00:26:10.600> token 00:26:11.510 --> 00:26:11.520 align:start position:0% here um explodable here with this token 00:26:11.520 --> 00:26:13.110 align:start position:0% here um explodable here with this token because<00:26:11.880> that's<00:26:12.080> something<00:26:12.399> you<00:26:12.520> could<00:26:12.840> find 00:26:13.110 --> 00:26:13.120 align:start position:0% because that's something you could find 00:26:13.120 --> 00:26:15.510 align:start position:0% because that's something you could find with<00:26:13.240> a<00:26:13.399> tool<00:26:14.080> and<00:26:14.279> it<00:26:14.360> would<00:26:14.480> save<00:26:14.760> you<00:26:15.399> it 00:26:15.510 --> 00:26:15.520 align:start position:0% with a tool and it would save you it 00:26:15.520 --> 00:26:18.230 align:start position:0% with a tool and it would save you it would<00:26:15.880> maximize<00:26:16.600> how<00:26:16.760> you<00:26:16.960> use<00:26:17.240> your<00:26:17.480> Security 00:26:18.230 --> 00:26:18.240 align:start position:0% would maximize how you use your Security 00:26:18.240 --> 00:26:25.310 align:start position:0% would maximize how you use your Security reviews<00:26:19.240> um<00:26:19.919> in<00:26:20.159> in<00:26:20.240> a<00:26:20.399> better 00:26:25.310 --> 00:26:25.320 align:start position:0% 00:26:25.320 --> 00:26:29.110 align:start position:0% way<00:26:26.320> this<00:26:26.559> last<00:26:26.840> tip<00:26:27.240> for<00:26:27.760> develop 00:26:29.110 --> 00:26:29.120 align:start position:0% way this last tip for develop 00:26:29.120 --> 00:26:32.549 align:start position:0% way this last tip for develop is<00:26:30.279> um<00:26:31.279> kind<00:26:31.440> of<00:26:31.640> higher<00:26:31.919> level<00:26:32.320> not 00:26:32.549 --> 00:26:32.559 align:start position:0% is um kind of higher level not 00:26:32.559 --> 00:26:35.830 align:start position:0% is um kind of higher level not necessarily<00:26:33.120> in<00:26:33.320> the<00:26:33.919> weeds<00:26:34.919> um<00:26:35.480> is 00:26:35.830 --> 00:26:35.840 align:start position:0% necessarily in the weeds um is 00:26:35.840 --> 00:26:37.990 align:start position:0% necessarily in the weeds um is proactively<00:26:36.520> trying<00:26:36.720> to<00:26:36.880> figure<00:26:37.159> out<00:26:37.559> how<00:26:37.799> can 00:26:37.990 --> 00:26:38.000 align:start position:0% proactively trying to figure out how can 00:26:38.000 --> 00:26:40.789 align:start position:0% proactively trying to figure out how can you<00:26:38.240> increase<00:26:38.760> security<00:26:39.320> within<00:26:39.640> your<00:26:40.520> life 00:26:40.789 --> 00:26:40.799 align:start position:0% you increase security within your life 00:26:40.799 --> 00:26:43.070 align:start position:0% you increase security within your life cycle<00:26:41.240> how<00:26:41.399> do<00:26:41.559> you<00:26:41.880> what<00:26:41.960> are<00:26:42.240> processes<00:26:42.960> that 00:26:43.070 --> 00:26:43.080 align:start position:0% cycle how do you what are processes that 00:26:43.080 --> 00:26:46.230 align:start position:0% cycle how do you what are processes that you<00:26:43.200> can<00:26:43.559> use<00:26:44.559> um<00:26:44.799> in<00:26:44.960> order<00:26:45.240> to<00:26:45.440> find<00:26:45.799> bugs 00:26:46.230 --> 00:26:46.240 align:start position:0% you can use um in order to find bugs 00:26:46.240 --> 00:26:49.029 align:start position:0% you can use um in order to find bugs during<00:26:46.960> development<00:26:47.960> um<00:26:48.240> such<00:26:48.559> that<00:26:48.799> your 00:26:49.029 --> 00:26:49.039 align:start position:0% during development um such that your 00:26:49.039 --> 00:26:52.269 align:start position:0% during development um such that your bugs<00:26:49.799> that<00:26:49.960> found<00:26:50.320> that<00:26:50.440> are<00:26:50.600> found<00:26:50.960> future<00:26:51.960> um 00:26:52.269 --> 00:26:52.279 align:start position:0% bugs that found that are found future um 00:26:52.279 --> 00:26:56.190 align:start position:0% bugs that found that are found future um in<00:26:52.679> kind<00:26:52.840> of<00:26:53.080> the<00:26:53.559> auditing<00:26:54.159> side<00:26:54.600> or<00:26:55.600> um<00:26:55.919> the 00:26:56.190 --> 00:26:56.200 align:start position:0% in kind of the auditing side or um the 00:26:56.200 --> 00:26:59.029 align:start position:0% in kind of the auditing side or um the kind<00:26:56.320> of<00:26:56.440> further<00:26:56.880> security<00:26:57.480> side<00:26:58.399> um<00:26:58.640> are<00:26:58.840> are 00:26:59.029 --> 00:26:59.039 align:start position:0% kind of further security side um are are 00:26:59.039 --> 00:27:01.510 align:start position:0% kind of further security side um are are the<00:26:59.360> the<00:26:59.480> big<00:26:59.919> ones 00:27:01.510 --> 00:27:01.520 align:start position:0% the the big ones 00:27:01.520 --> 00:27:04.830 align:start position:0% the the big ones um<00:27:02.520> generally<00:27:03.000> the<00:27:03.120> smaller<00:27:03.520> the<00:27:03.679> code<00:27:04.200> the<00:27:04.799> I 00:27:04.830 --> 00:27:04.840 align:start position:0% um generally the smaller the code the I 00:27:04.840 --> 00:27:07.990 align:start position:0% um generally the smaller the code the I mean<00:27:05.320> the<00:27:05.679> the<00:27:06.200> bugs<00:27:06.799> have<00:27:07.200> less<00:27:07.559> impact 00:27:07.990 --> 00:27:08.000 align:start position:0% mean the the bugs have less impact 00:27:08.000 --> 00:27:10.870 align:start position:0% mean the the bugs have less impact within<00:27:08.240> the<00:27:08.399> system<00:27:08.720> to<00:27:09.039> fix<00:27:10.039> um<00:27:10.399> and<00:27:10.520> so<00:27:10.760> the 00:27:10.870 --> 00:27:10.880 align:start position:0% within the system to fix um and so the 00:27:10.880 --> 00:27:12.590 align:start position:0% within the system to fix um and so the more<00:27:11.080> bugs<00:27:11.360> that<00:27:11.480> you<00:27:11.640> find<00:27:12.279> while<00:27:12.440> you're 00:27:12.590 --> 00:27:12.600 align:start position:0% more bugs that you find while you're 00:27:12.600 --> 00:27:20.269 align:start position:0% more bugs that you find while you're writing<00:27:12.919> your<00:27:13.080> code<00:27:13.720> the<00:27:13.880> better<00:27:14.279> for<00:27:14.520> your 00:27:20.269 --> 00:27:20.279 align:start position:0% 00:27:20.279 --> 00:27:23.669 align:start position:0% code<00:27:21.279> all<00:27:21.480> right<00:27:22.320> this<00:27:22.440> is<00:27:22.679> kind<00:27:22.840> of<00:27:23.559> um 00:27:23.669 --> 00:27:23.679 align:start position:0% code all right this is kind of um 00:27:23.679 --> 00:27:26.990 align:start position:0% code all right this is kind of um flip-flopping<00:27:24.360> tracks<00:27:24.919> because<00:27:25.559> I<00:27:25.919> am<00:27:26.159> also 00:27:26.990 --> 00:27:27.000 align:start position:0% flip-flopping tracks because I am also 00:27:27.000 --> 00:27:31.110 align:start position:0% flip-flopping tracks because I am also um<00:27:27.360> or<00:27:27.679> mainly<00:27:28.279> security<00:27:28.640> researcher<00:27:29.279> now<00:27:30.279> um 00:27:31.110 --> 00:27:31.120 align:start position:0% um or mainly security researcher now um 00:27:31.120 --> 00:27:32.950 align:start position:0% um or mainly security researcher now um so<00:27:31.360> I<00:27:31.480> guess<00:27:31.679> raise<00:27:31.919> of<00:27:32.159> hands<00:27:32.480> how<00:27:32.640> many<00:27:32.840> of 00:27:32.950 --> 00:27:32.960 align:start position:0% so I guess raise of hands how many of 00:27:32.960 --> 00:27:35.190 align:start position:0% so I guess raise of hands how many of you<00:27:33.240> are<00:27:33.760> security<00:27:34.200> researchers<00:27:34.840> or 00:27:35.190 --> 00:27:35.200 align:start position:0% you are security researchers or 00:27:35.200 --> 00:27:38.950 align:start position:0% you are security researchers or interested<00:27:36.080> in<00:27:36.320> heading<00:27:36.640> that 00:27:38.950 --> 00:27:38.960 align:start position:0% 00:27:38.960 --> 00:27:41.549 align:start position:0% direction<00:27:39.960> okay 00:27:41.549 --> 00:27:41.559 align:start position:0% direction okay 00:27:41.559 --> 00:27:46.029 align:start position:0% direction okay um<00:27:42.559> then<00:27:42.799> let's<00:27:43.000> get<00:27:43.320> started<00:27:44.559> um<00:27:45.559> this<00:27:45.760> next 00:27:46.029 --> 00:27:46.039 align:start position:0% um then let's get started um this next 00:27:46.039 --> 00:27:48.789 align:start position:0% um then let's get started um this next tip<00:27:46.440> is<00:27:46.760> preemptively<00:27:47.480> ask<00:27:47.799> questions<00:27:48.559> and 00:27:48.789 --> 00:27:48.799 align:start position:0% tip is preemptively ask questions and 00:27:48.799 --> 00:27:50.590 align:start position:0% tip is preemptively ask questions and preemptively<00:27:49.519> identify<00:27:50.120> all<00:27:50.279> of<00:27:50.440> the 00:27:50.590 --> 00:27:50.600 align:start position:0% preemptively identify all of the 00:27:50.600 --> 00:27:53.470 align:start position:0% preemptively identify all of the assumptions<00:27:51.600> that<00:27:51.799> developers<00:27:52.320> are<00:27:52.480> making 00:27:53.470 --> 00:27:53.480 align:start position:0% assumptions that developers are making 00:27:53.480 --> 00:27:56.350 align:start position:0% assumptions that developers are making and<00:27:53.679> this<00:27:54.240> ties<00:27:55.000> kind<00:27:55.200> of<00:27:55.399> into<00:27:55.720> the<00:27:55.919> previous 00:27:56.350 --> 00:27:56.360 align:start position:0% and this ties kind of into the previous 00:27:56.360 --> 00:27:58.470 align:start position:0% and this ties kind of into the previous recommendation<00:27:57.039> for<00:27:57.320> Developers<00:27:58.200> about 00:27:58.470 --> 00:27:58.480 align:start position:0% recommendation for Developers about 00:27:58.480 --> 00:28:00.870 align:start position:0% recommendation for Developers about documenting<00:27:59.000> your<00:27:59.360> system<00:28:00.360> nothing<00:28:00.679> is 00:28:00.870 --> 00:28:00.880 align:start position:0% documenting your system nothing is 00:28:00.880 --> 00:28:02.830 align:start position:0% documenting your system nothing is harder<00:28:01.279> than<00:28:01.480> trying<00:28:01.720> to<00:28:01.919> identify<00:28:02.519> what<00:28:02.679> did 00:28:02.830 --> 00:28:02.840 align:start position:0% harder than trying to identify what did 00:28:02.840 --> 00:28:05.789 align:start position:0% harder than trying to identify what did you<00:28:03.200> actually<00:28:04.000> try<00:28:04.279> to<00:28:04.519> build<00:28:05.039> in<00:28:05.159> the<00:28:05.320> first 00:28:05.789 --> 00:28:05.799 align:start position:0% you actually try to build in the first 00:28:05.799 --> 00:28:09.149 align:start position:0% you actually try to build in the first place<00:28:06.840> um<00:28:07.840> a<00:28:07.960> lot<00:28:08.080> of<00:28:08.240> the<00:28:08.440> time<00:28:08.720> I'll<00:28:08.919> look<00:28:09.039> at 00:28:09.149 --> 00:28:09.159 align:start position:0% place um a lot of the time I'll look at 00:28:09.159 --> 00:28:12.350 align:start position:0% place um a lot of the time I'll look at a<00:28:09.320> code<00:28:09.640> base<00:28:10.320> and<00:28:10.440> then<00:28:10.640> realize<00:28:11.440> yeah<00:28:11.760> that<00:28:12.279> I 00:28:12.350 --> 00:28:12.360 align:start position:0% a code base and then realize yeah that I 00:28:12.360 --> 00:28:14.230 align:start position:0% a code base and then realize yeah that I think<00:28:12.640> that's<00:28:12.880> what<00:28:13.039> was<00:28:13.240> intended<00:28:13.799> I'm<00:28:13.919> not 00:28:14.230 --> 00:28:14.240 align:start position:0% think that's what was intended I'm not 00:28:14.240 --> 00:28:17.310 align:start position:0% think that's what was intended I'm not entirely<00:28:14.679> sure<00:28:15.600> um<00:28:15.880> here's<00:28:16.640> me<00:28:16.919> looking<00:28:17.159> at 00:28:17.310 --> 00:28:17.320 align:start position:0% entirely sure um here's me looking at 00:28:17.320 --> 00:28:19.350 align:start position:0% entirely sure um here's me looking at the<00:28:17.440> code<00:28:17.720> base<00:28:18.039> here's<00:28:18.320> what<00:28:18.559> I<00:28:18.840> think<00:28:19.120> it's 00:28:19.350 --> 00:28:19.360 align:start position:0% the code base here's what I think it's 00:28:19.360 --> 00:28:22.750 align:start position:0% the code base here's what I think it's supposed<00:28:19.720> to<00:28:19.880> do<00:28:20.360> but<00:28:21.200> um<00:28:21.679> it's<00:28:21.880> really<00:28:22.320> hard 00:28:22.750 --> 00:28:22.760 align:start position:0% supposed to do but um it's really hard 00:28:22.760 --> 00:28:26.110 align:start position:0% supposed to do but um it's really hard to<00:28:23.679> have<00:28:23.919> that<00:28:24.440> clarification<00:28:25.440> and<00:28:25.600> if<00:28:25.760> you 00:28:26.110 --> 00:28:26.120 align:start position:0% to have that clarification and if you 00:28:26.120 --> 00:28:28.269 align:start position:0% to have that clarification and if you make<00:28:26.600> a<00:28:26.799> wrong<00:28:27.080> assumption<00:28:27.480> during<00:28:27.760> your<00:28:27.880> code 00:28:28.269 --> 00:28:28.279 align:start position:0% make a wrong assumption during your code 00:28:28.279 --> 00:28:31.190 align:start position:0% make a wrong assumption during your code review<00:28:29.080> I<00:28:29.159> mean<00:28:29.440> you're<00:28:30.399> you're<00:28:30.679> you<00:28:30.799> could<00:28:30.960> be 00:28:31.190 --> 00:28:31.200 align:start position:0% review I mean you're you're you could be 00:28:31.200 --> 00:28:34.669 align:start position:0% review I mean you're you're you could be missing<00:28:32.200> a<00:28:32.399> bunch<00:28:32.640> of<00:28:32.880> bugs<00:28:33.799> um<00:28:34.120> and<00:28:34.320> and 00:28:34.669 --> 00:28:34.679 align:start position:0% missing a bunch of bugs um and and 00:28:34.679 --> 00:28:37.070 align:start position:0% missing a bunch of bugs um and and issues<00:28:35.200> within<00:28:35.480> the<00:28:35.679> actual<00:28:36.320> code<00:28:36.840> because 00:28:37.070 --> 00:28:37.080 align:start position:0% issues within the actual code because 00:28:37.080 --> 00:28:38.870 align:start position:0% issues within the actual code because you<00:28:37.279> misunderstood<00:28:38.000> how<00:28:38.159> it<00:28:38.279> was<00:28:38.440> supposed<00:28:38.760> to 00:28:38.870 --> 00:28:38.880 align:start position:0% you misunderstood how it was supposed to 00:28:38.880 --> 00:28:42.310 align:start position:0% you misunderstood how it was supposed to be<00:28:39.240> used<00:28:40.240> so<00:28:40.640> for<00:28:40.960> that<00:28:41.399> I<00:28:41.559> would 00:28:42.310 --> 00:28:42.320 align:start position:0% be used so for that I would 00:28:42.320 --> 00:28:44.350 align:start position:0% be used so for that I would recommend<00:28:43.320> collaborating<00:28:43.960> with<00:28:44.159> your 00:28:44.350 --> 00:28:44.360 align:start position:0% recommend collaborating with your 00:28:44.360 --> 00:28:46.710 align:start position:0% recommend collaborating with your security<00:28:44.799> team<00:28:45.240> collaborating<00:28:45.960> with<00:28:46.159> the 00:28:46.710 --> 00:28:46.720 align:start position:0% security team collaborating with the 00:28:46.720 --> 00:28:49.590 align:start position:0% security team collaborating with the developers<00:28:47.720> um<00:28:48.600> make<00:28:48.840> sure<00:28:49.080> that<00:28:49.200> you<00:28:49.360> take 00:28:49.590 --> 00:28:49.600 align:start position:0% developers um make sure that you take 00:28:49.600 --> 00:28:52.630 align:start position:0% developers um make sure that you take the<00:28:49.760> time<00:28:50.000> and<00:28:50.159> the<00:28:50.320> effort<00:28:51.080> to<00:28:51.840> identify<00:28:52.480> all 00:28:52.630 --> 00:28:52.640 align:start position:0% the time and the effort to identify all 00:28:52.640 --> 00:28:54.549 align:start position:0% the time and the effort to identify all the<00:28:52.760> assumptions<00:28:53.279> that<00:28:53.399> you're<00:28:53.720> making<00:28:54.399> in 00:28:54.549 --> 00:28:54.559 align:start position:0% the assumptions that you're making in 00:28:54.559 --> 00:28:57.149 align:start position:0% the assumptions that you're making in your<00:28:54.840> Security<00:28:55.360> review<00:28:56.360> um<00:28:56.559> and<00:28:56.679> make<00:28:56.880> sure 00:28:57.149 --> 00:28:57.159 align:start position:0% your Security review um and make sure 00:28:57.159 --> 00:28:59.230 align:start position:0% your Security review um and make sure that<00:28:57.480> that's<00:28:57.720> a<00:28:57.840> lot<00:28:58.480> with<00:28:58.679> what<00:28:59.000> how 00:28:59.230 --> 00:28:59.240 align:start position:0% that that's a lot with what how 00:28:59.240 --> 00:29:01.710 align:start position:0% that that's a lot with what how developers<00:28:59.840> intended<00:29:00.320> to<00:29:00.960> users<00:29:01.360> to<00:29:01.519> use 00:29:01.710 --> 00:29:01.720 align:start position:0% developers intended to users to use 00:29:01.720 --> 00:29:03.669 align:start position:0% developers intended to users to use their 00:29:03.669 --> 00:29:03.679 align:start position:0% their 00:29:03.679 --> 00:29:06.430 align:start position:0% their system<00:29:04.679> all<00:29:04.840> right<00:29:05.080> this<00:29:05.200> one<00:29:05.640> is<00:29:05.919> a<00:29:06.080> bit<00:29:06.200> of<00:29:06.320> an 00:29:06.430 --> 00:29:06.440 align:start position:0% system all right this one is a bit of an 00:29:06.440 --> 00:29:09.830 align:start position:0% system all right this one is a bit of an overlap<00:29:06.960> as<00:29:07.120> well<00:29:08.039> um<00:29:08.399> but<00:29:08.600> essentially<00:29:09.039> to<00:29:09.720> as 00:29:09.830 --> 00:29:09.840 align:start position:0% overlap as well um but essentially to as 00:29:09.840 --> 00:29:12.310 align:start position:0% overlap as well um but essentially to as a<00:29:10.039> security<00:29:10.600> re<00:29:10.960> researcher<00:29:11.640> building<00:29:12.159> a 00:29:12.310 --> 00:29:12.320 align:start position:0% a security re researcher building a 00:29:12.320 --> 00:29:15.029 align:start position:0% a security re researcher building a mental<00:29:12.679> model<00:29:12.960> of<00:29:13.080> the<00:29:13.200> code<00:29:13.519> base<00:29:14.480> um<00:29:14.840> is 00:29:15.029 --> 00:29:15.039 align:start position:0% mental model of the code base um is 00:29:15.039 --> 00:29:18.190 align:start position:0% mental model of the code base um is incredibly<00:29:15.640> important<00:29:16.640> because<00:29:17.519> um<00:29:17.799> and<00:29:18.000> and 00:29:18.190 --> 00:29:18.200 align:start position:0% incredibly important because um and and 00:29:18.200 --> 00:29:22.230 align:start position:0% incredibly important because um and and this<00:29:18.840> um<00:29:19.080> graphic<00:29:19.559> is<00:29:20.039> from<00:29:21.039> uh<00:29:21.559> the<00:29:21.679> most<00:29:22.120> I 00:29:22.230 --> 00:29:22.240 align:start position:0% this um graphic is from uh the most I 00:29:22.240 --> 00:29:24.269 align:start position:0% this um graphic is from uh the most I guess<00:29:22.440> Sherlock<00:29:22.880> Holmes<00:29:23.279> where<00:29:23.399> he<00:29:23.559> kind<00:29:23.679> of 00:29:24.269 --> 00:29:24.279 align:start position:0% guess Sherlock Holmes where he kind of 00:29:24.279 --> 00:29:27.470 align:start position:0% guess Sherlock Holmes where he kind of references<00:29:25.279> um<00:29:25.880> thinking<00:29:26.360> about<00:29:27.000> like 00:29:27.470 --> 00:29:27.480 align:start position:0% references um thinking about like 00:29:27.480 --> 00:29:29.029 align:start position:0% references um thinking about like different<00:29:27.760> con<00:29:28.080> Concepts<00:29:28.440> in<00:29:28.519> terms<00:29:28.799> of<00:29:28.919> a 00:29:29.029 --> 00:29:29.039 align:start position:0% different con Concepts in terms of a 00:29:29.039 --> 00:29:34.029 align:start position:0% different con Concepts in terms of a mine<00:29:29.360> castle<00:29:30.120> and<00:29:30.279> where<00:29:30.480> he<00:29:30.640> can<00:29:31.360> um<00:29:32.200> kind 00:29:34.029 --> 00:29:34.039 align:start position:0% mine castle and where he can um kind 00:29:34.039 --> 00:29:39.070 align:start position:0% mine castle and where he can um kind of<00:29:35.039> figure<00:29:35.399> out<00:29:35.880> how<00:29:36.600> to<00:29:37.600> um<00:29:38.399> categorize 00:29:39.070 --> 00:29:39.080 align:start position:0% of figure out how to um categorize 00:29:39.080 --> 00:29:42.029 align:start position:0% of figure out how to um categorize information<00:29:39.679> into<00:29:40.120> this<00:29:41.000> um<00:29:41.360> kind<00:29:41.519> of 00:29:42.029 --> 00:29:42.039 align:start position:0% information into this um kind of 00:29:42.039 --> 00:29:44.789 align:start position:0% information into this um kind of strategic<00:29:43.039> uh<00:29:43.200> model<00:29:43.679> that<00:29:43.799> he<00:29:43.960> can<00:29:44.360> kind<00:29:44.480> of 00:29:44.789 --> 00:29:44.799 align:start position:0% strategic uh model that he can kind of 00:29:44.799 --> 00:29:47.350 align:start position:0% strategic uh model that he can kind of be<00:29:44.960> able<00:29:45.159> to<00:29:45.519> parse<00:29:45.880> through<00:29:46.240> information<00:29:47.240> um 00:29:47.350 --> 00:29:47.360 align:start position:0% be able to parse through information um 00:29:47.360 --> 00:29:48.990 align:start position:0% be able to parse through information um be<00:29:47.480> able<00:29:47.640> to<00:29:48.080> understand<00:29:48.360> things<00:29:48.640> and<00:29:48.760> then<00:29:48.880> be 00:29:48.990 --> 00:29:49.000 align:start position:0% be able to understand things and then be 00:29:49.000 --> 00:29:50.389 align:start position:0% be able to understand things and then be able<00:29:49.159> to<00:29:49.320> bounce 00:29:50.389 --> 00:29:50.399 align:start position:0% able to bounce 00:29:50.399 --> 00:29:53.149 align:start position:0% able to bounce ideas<00:29:51.399> as<00:29:51.519> a<00:29:51.720> security<00:29:52.159> researcher<00:29:52.799> this<00:29:52.919> is 00:29:53.149 --> 00:29:53.159 align:start position:0% ideas as a security researcher this is 00:29:53.159 --> 00:29:56.470 align:start position:0% ideas as a security researcher this is super<00:29:53.559> important<00:29:54.559> just<00:29:54.840> because<00:29:55.840> um<00:29:56.039> once<00:29:56.279> you 00:29:56.470 --> 00:29:56.480 align:start position:0% super important just because um once you 00:29:56.480 --> 00:29:58.710 align:start position:0% super important just because um once you have<00:29:56.720> this<00:29:56.880> mental<00:29:57.240> model<00:29:57.720> of<00:29:58.159> whatever<00:29:58.480> code 00:29:58.710 --> 00:29:58.720 align:start position:0% have this mental model of whatever code 00:29:58.720 --> 00:30:01.310 align:start position:0% have this mental model of whatever code base<00:29:58.960> you're<00:29:59.120> looking<00:29:59.440> at<00:30:00.399> now<00:30:00.640> you<00:30:00.799> can<00:30:01.039> start 00:30:01.310 --> 00:30:01.320 align:start position:0% base you're looking at now you can start 00:30:01.320 --> 00:30:04.549 align:start position:0% base you're looking at now you can start to<00:30:01.880> understand<00:30:02.240> okay<00:30:02.480> this<00:30:02.600> is<00:30:02.880> how<00:30:03.880> um<00:30:04.440> you 00:30:04.549 --> 00:30:04.559 align:start position:0% to understand okay this is how um you 00:30:04.559 --> 00:30:08.310 align:start position:0% to understand okay this is how um you know<00:30:04.840> this<00:30:05.200> particular<00:30:05.720> flow<00:30:06.200> Works<00:30:07.200> um<00:30:08.159> this 00:30:08.310 --> 00:30:08.320 align:start position:0% know this particular flow Works um this 00:30:08.320 --> 00:30:11.710 align:start position:0% know this particular flow Works um this is<00:30:08.559> how<00:30:09.480> developers<00:30:10.360> intended<00:30:11.360> um<00:30:11.559> this 00:30:11.710 --> 00:30:11.720 align:start position:0% is how developers intended um this 00:30:11.720 --> 00:30:15.029 align:start position:0% is how developers intended um this certain<00:30:12.039> flow<00:30:12.559> to<00:30:13.440> progress<00:30:14.440> um<00:30:14.720> and<00:30:14.840> then<00:30:14.960> you 00:30:15.029 --> 00:30:15.039 align:start position:0% certain flow to progress um and then you 00:30:15.039 --> 00:30:17.110 align:start position:0% certain flow to progress um and then you can<00:30:15.200> look<00:30:15.360> for<00:30:15.600> deviations<00:30:16.320> and<00:30:16.559> assumptions 00:30:17.110 --> 00:30:17.120 align:start position:0% can look for deviations and assumptions 00:30:17.120 --> 00:30:19.549 align:start position:0% can look for deviations and assumptions where<00:30:17.320> they<00:30:17.480> can<00:30:17.840> might<00:30:18.039> they<00:30:18.159> might<00:30:18.360> go<00:30:18.559> wrong 00:30:19.549 --> 00:30:19.559 align:start position:0% where they can might they might go wrong 00:30:19.559 --> 00:30:23.630 align:start position:0% where they can might they might go wrong um<00:30:19.880> a<00:30:20.000> lot<00:30:20.159> of<00:30:20.279> the<00:30:20.679> times<00:30:21.679> this<00:30:22.000> helps<00:30:22.440> with<00:30:23.159> um 00:30:23.630 --> 00:30:23.640 align:start position:0% um a lot of the times this helps with um 00:30:23.640 --> 00:30:26.909 align:start position:0% um a lot of the times this helps with um kind<00:30:23.799> of<00:30:24.200> taking<00:30:24.480> a<00:30:24.679> break<00:30:25.320> and<00:30:25.519> then<00:30:25.919> you<00:30:26.080> can 00:30:26.909 --> 00:30:26.919 align:start position:0% kind of taking a break and then you can 00:30:26.919 --> 00:30:28.990 align:start position:0% kind of taking a break and then you can be<00:30:27.080> able<00:30:27.320> to<00:30:27.640> really<00:30:28.399> understand<00:30:28.720> like 00:30:28.990 --> 00:30:29.000 align:start position:0% be able to really understand like 00:30:29.000 --> 00:30:32.350 align:start position:0% be able to really understand like different<00:30:29.600> impacts<00:30:30.600> um<00:30:30.919> of<00:30:31.240> like<00:30:32.000> different 00:30:32.350 --> 00:30:32.360 align:start position:0% different impacts um of like different 00:30:32.360 --> 00:30:34.230 align:start position:0% different impacts um of like different issues<00:30:32.799> and<00:30:33.000> and<00:30:33.159> especially<00:30:33.720> a<00:30:33.880> kind<00:30:34.000> of 00:30:34.230 --> 00:30:34.240 align:start position:0% issues and and especially a kind of 00:30:34.240 --> 00:30:37.470 align:start position:0% issues and and especially a kind of higher<00:30:35.000> higher<00:30:35.240> level<00:30:35.600> view<00:30:36.080> of<00:30:36.240> the<00:30:36.480> system 00:30:37.470 --> 00:30:37.480 align:start position:0% higher higher level view of the system 00:30:37.480 --> 00:30:39.909 align:start position:0% higher higher level view of the system um<00:30:38.399> understanding<00:30:39.000> just<00:30:39.360> like<00:30:39.600> how<00:30:39.760> the 00:30:39.909 --> 00:30:39.919 align:start position:0% um understanding just like how the 00:30:39.919 --> 00:30:42.310 align:start position:0% um understanding just like how the codebase<00:30:40.440> was<00:30:40.600> built<00:30:40.880> and<00:30:41.120> how<00:30:41.279> it<00:30:41.440> works<00:30:42.120> goes 00:30:42.310 --> 00:30:42.320 align:start position:0% codebase was built and how it works goes 00:30:42.320 --> 00:30:45.310 align:start position:0% codebase was built and how it works goes a<00:30:42.480> long 00:30:45.310 --> 00:30:45.320 align:start position:0% 00:30:45.320 --> 00:30:48.149 align:start position:0% way<00:30:46.320> all<00:30:46.480> right<00:30:46.720> this<00:30:46.960> next<00:30:47.240> tip<00:30:47.559> is<00:30:47.679> to<00:30:47.840> learn 00:30:48.149 --> 00:30:48.159 align:start position:0% way all right this next tip is to learn 00:30:48.159 --> 00:30:51.029 align:start position:0% way all right this next tip is to learn your<00:30:48.440> tools<00:30:49.320> as<00:30:49.440> a<00:30:49.600> security<00:30:50.039> researcher 00:30:51.029 --> 00:30:51.039 align:start position:0% your tools as a security researcher 00:30:51.039 --> 00:30:53.549 align:start position:0% your tools as a security researcher there's<00:30:52.039> endless<00:30:52.480> number<00:30:52.679> of<00:30:52.880> tools<00:30:53.279> that<00:30:53.399> you 00:30:53.549 --> 00:30:53.559 align:start position:0% there's endless number of tools that you 00:30:53.559 --> 00:30:57.470 align:start position:0% there's endless number of tools that you can<00:30:53.880> use<00:30:54.880> um<00:30:55.360> to<00:30:55.960> verify<00:30:56.639> whether<00:30:56.960> developers 00:30:57.470 --> 00:30:57.480 align:start position:0% can use um to verify whether developers 00:30:57.480 --> 00:31:01.190 align:start position:0% can use um to verify whether developers do<00:30:58.039> are<00:30:58.200> doing<00:30:58.559> things<00:30:59.120> correctly<00:31:00.120> um<00:31:00.679> endless 00:31:01.190 --> 00:31:01.200 align:start position:0% do are doing things correctly um endless 00:31:01.200 --> 00:31:04.430 align:start position:0% do are doing things correctly um endless number<00:31:01.559> of<00:31:02.320> um<00:31:03.159> different<00:31:03.679> like<00:31:03.960> fuzzing 00:31:04.430 --> 00:31:04.440 align:start position:0% number of um different like fuzzing 00:31:04.440 --> 00:31:07.350 align:start position:0% number of um different like fuzzing Integrations<00:31:05.360> verification<00:31:06.360> Integrations 00:31:07.350 --> 00:31:07.360 align:start position:0% Integrations verification Integrations 00:31:07.360 --> 00:31:09.509 align:start position:0% Integrations verification Integrations that<00:31:07.519> you<00:31:07.639> can<00:31:07.799> check<00:31:08.159> things<00:31:09.039> and<00:31:09.200> I<00:31:09.320> think 00:31:09.509 --> 00:31:09.519 align:start position:0% that you can check things and I think 00:31:09.519 --> 00:31:12.110 align:start position:0% that you can check things and I think there's<00:31:09.960> far<00:31:10.320> too<00:31:10.720> much<00:31:11.120> conversation<00:31:11.799> about 00:31:12.110 --> 00:31:12.120 align:start position:0% there's far too much conversation about 00:31:12.120 --> 00:31:14.350 align:start position:0% there's far too much conversation about which<00:31:12.279> is<00:31:12.519> better<00:31:13.480> I<00:31:13.559> don't<00:31:13.760> think<00:31:14.039> that's<00:31:14.159> a 00:31:14.350 --> 00:31:14.360 align:start position:0% which is better I don't think that's a 00:31:14.360 --> 00:31:17.549 align:start position:0% which is better I don't think that's a productive<00:31:15.279> discussion<00:31:16.279> um<00:31:16.840> instead<00:31:17.320> I<00:31:17.399> think 00:31:17.549 --> 00:31:17.559 align:start position:0% productive discussion um instead I think 00:31:17.559 --> 00:31:20.669 align:start position:0% productive discussion um instead I think it's<00:31:17.760> more<00:31:18.000> important<00:31:18.799> for<00:31:19.799> um<00:31:20.240> security 00:31:20.669 --> 00:31:20.679 align:start position:0% it's more important for um security 00:31:20.679 --> 00:31:23.269 align:start position:0% it's more important for um security researchers<00:31:21.200> to<00:31:21.399> really<00:31:21.639> sit<00:31:22.039> down<00:31:22.760> play<00:31:23.080> with 00:31:23.269 --> 00:31:23.279 align:start position:0% researchers to really sit down play with 00:31:23.279 --> 00:31:26.710 align:start position:0% researchers to really sit down play with each<00:31:23.480> of<00:31:23.679> these<00:31:24.120> tools<00:31:25.120> figure<00:31:25.480> out<00:31:25.919> when<00:31:26.200> does 00:31:26.710 --> 00:31:26.720 align:start position:0% each of these tools figure out when does 00:31:26.720 --> 00:31:28.669 align:start position:0% each of these tools figure out when does when<00:31:26.880> do<00:31:27.039> they<00:31:27.200> come<00:31:27.360> in<00:31:27.559> handy<00:31:28.080> when<00:31:28.240> are<00:31:28.440> they 00:31:28.669 --> 00:31:28.679 align:start position:0% when do they come in handy when are they 00:31:28.679 --> 00:31:32.230 align:start position:0% when do they come in handy when are they most<00:31:29.360> powerful<00:31:30.360> um<00:31:30.720> and<00:31:30.960> really<00:31:31.240> learn<00:31:31.760> how<00:31:32.000> to 00:31:32.230 --> 00:31:32.240 align:start position:0% most powerful um and really learn how to 00:31:32.240 --> 00:31:36.669 align:start position:0% most powerful um and really learn how to use<00:31:32.559> them<00:31:33.519> um<00:31:34.399> I<00:31:34.480> think<00:31:34.799> there's<00:31:35.440> also<00:31:36.159> endless 00:31:36.669 --> 00:31:36.679 align:start position:0% use them um I think there's also endless 00:31:36.679 --> 00:31:41.149 align:start position:0% use them um I think there's also endless resources<00:31:37.480> on<00:31:37.960> how<00:31:38.159> to<00:31:38.399> use<00:31:38.760> these<00:31:39.760> um<00:31:40.399> and<00:31:41.039> at 00:31:41.149 --> 00:31:41.159 align:start position:0% resources on how to use these um and at 00:31:41.159 --> 00:31:44.070 align:start position:0% resources on how to use these um and at least<00:31:41.360> for<00:31:41.559> me<00:31:42.159> as<00:31:42.519> a<00:31:43.000> developer<00:31:43.559> I<00:31:43.679> just<00:31:43.919> have 00:31:44.070 --> 00:31:44.080 align:start position:0% least for me as a developer I just have 00:31:44.080 --> 00:31:46.870 align:start position:0% least for me as a developer I just have so<00:31:44.240> much<00:31:44.440> fun<00:31:44.720> playing<00:31:45.000> around<00:31:45.279> with<00:31:45.720> these<00:31:46.720> I 00:31:46.870 --> 00:31:46.880 align:start position:0% so much fun playing around with these I 00:31:46.880 --> 00:31:48.310 align:start position:0% so much fun playing around with these I think 00:31:48.310 --> 00:31:48.320 align:start position:0% think 00:31:48.320 --> 00:31:50.750 align:start position:0% think um<00:31:49.320> the<00:31:49.480> more<00:31:49.799> you<00:31:50.000> play<00:31:50.279> around<00:31:50.559> with 00:31:50.750 --> 00:31:50.760 align:start position:0% um the more you play around with 00:31:50.760 --> 00:31:52.750 align:start position:0% um the more you play around with different<00:31:51.039> tooling<00:31:51.919> and<00:31:52.080> the<00:31:52.159> more<00:31:52.360> you<00:31:52.559> play 00:31:52.750 --> 00:31:52.760 align:start position:0% different tooling and the more you play 00:31:52.760 --> 00:31:56.909 align:start position:0% different tooling and the more you play around<00:31:53.200> with<00:31:54.399> um<00:31:55.440> comparisons<00:31:56.440> between<00:31:56.760> like 00:31:56.909 --> 00:31:56.919 align:start position:0% around with um comparisons between like 00:31:56.919 --> 00:31:59.710 align:start position:0% around with um comparisons between like use<00:31:57.240> for<00:31:57.399> example<00:31:58.039> like<00:31:58.679> um<00:31:58.840> fuzzing<00:31:59.279> a<00:31:59.440> code 00:31:59.710 --> 00:31:59.720 align:start position:0% use for example like um fuzzing a code 00:31:59.720 --> 00:32:03.909 align:start position:0% use for example like um fuzzing a code base<00:32:00.679> um<00:32:01.240> or<00:32:01.799> like<00:32:02.799> uh<00:32:02.919> writing<00:32:03.240> unit<00:32:03.559> tests<00:32:03.840> on 00:32:03.909 --> 00:32:03.919 align:start position:0% base um or like uh writing unit tests on 00:32:03.919 --> 00:32:06.350 align:start position:0% base um or like uh writing unit tests on a<00:32:04.080> code<00:32:04.320> base<00:32:05.120> I<00:32:05.200> think<00:32:05.360> the<00:32:05.480> easier<00:32:05.960> it<00:32:06.120> will 00:32:06.350 --> 00:32:06.360 align:start position:0% a code base I think the easier it will 00:32:06.360 --> 00:32:09.509 align:start position:0% a code base I think the easier it will be<00:32:06.639> to<00:32:07.360> test<00:32:07.760> the<00:32:07.919> code<00:32:08.840> um<00:32:09.000> and<00:32:09.159> playing 00:32:09.509 --> 00:32:09.519 align:start position:0% be to test the code um and playing 00:32:09.519 --> 00:32:12.310 align:start position:0% be to test the code um and playing around<00:32:10.039> with<00:32:10.679> um<00:32:10.799> the<00:32:10.919> code<00:32:11.200> base<00:32:11.639> with<00:32:11.880> these 00:32:12.310 --> 00:32:12.320 align:start position:0% around with um the code base with these 00:32:12.320 --> 00:32:16.310 align:start position:0% around with um the code base with these tools<00:32:13.320> that<00:32:13.480> helps<00:32:13.799> you<00:32:14.720> in<00:32:15.480> a<00:32:15.679> different<00:32:16.039> way 00:32:16.310 --> 00:32:16.320 align:start position:0% tools that helps you in a different way 00:32:16.320 --> 00:32:18.789 align:start position:0% tools that helps you in a different way because<00:32:16.639> with<00:32:16.919> code<00:32:17.399> then<00:32:17.600> you<00:32:17.720> can<00:32:18.159> test<00:32:18.600> with 00:32:18.789 --> 00:32:18.799 align:start position:0% because with code then you can test with 00:32:18.799 --> 00:32:21.230 align:start position:0% because with code then you can test with test<00:32:19.080> the<00:32:19.200> code<00:32:19.440> base<00:32:20.120> you<00:32:20.240> can<00:32:20.440> kind<00:32:20.559> of<00:32:20.720> see 00:32:21.230 --> 00:32:21.240 align:start position:0% test the code base you can kind of see 00:32:21.240 --> 00:32:22.830 align:start position:0% test the code base you can kind of see okay<00:32:21.480> what<00:32:21.559> are<00:32:21.760> the<00:32:21.960> different<00:32:22.279> branches 00:32:22.830 --> 00:32:22.840 align:start position:0% okay what are the different branches 00:32:22.840 --> 00:32:25.470 align:start position:0% okay what are the different branches within<00:32:23.080> your<00:32:23.320> function<00:32:24.320> how<00:32:24.440> do<00:32:24.559> you<00:32:24.760> invoke 00:32:25.470 --> 00:32:25.480 align:start position:0% within your function how do you invoke 00:32:25.480 --> 00:32:30.029 align:start position:0% within your function how do you invoke certain<00:32:26.480> um<00:32:27.159> like<00:32:27.440> if<00:32:28.080> M<00:32:28.880> um<00:32:29.120> how<00:32:29.240> do<00:32:29.399> you<00:32:29.919> you 00:32:30.029 --> 00:32:30.039 align:start position:0% certain um like if M um how do you you 00:32:30.039 --> 00:32:31.990 align:start position:0% certain um like if M um how do you you know<00:32:30.240> Trigger<00:32:30.600> or<00:32:30.840> revert<00:32:31.480> and<00:32:31.600> it<00:32:31.760> really 00:32:31.990 --> 00:32:32.000 align:start position:0% know Trigger or revert and it really 00:32:32.000 --> 00:32:34.669 align:start position:0% know Trigger or revert and it really gives<00:32:32.159> you<00:32:32.360> a<00:32:32.519> good<00:32:32.720> idea<00:32:33.080> of<00:32:33.440> how<00:32:33.679> the<00:32:33.840> system 00:32:34.669 --> 00:32:34.679 align:start position:0% gives you a good idea of how the system 00:32:34.679 --> 00:32:38.549 align:start position:0% gives you a good idea of how the system works<00:32:35.679> so<00:32:36.559> I<00:32:36.720> guess<00:32:36.840> the<00:32:36.960> T<00:32:37.360> tldr<00:32:38.039> of<00:32:38.200> this<00:32:38.360> is 00:32:38.549 --> 00:32:38.559 align:start position:0% works so I guess the T tldr of this is 00:32:38.559 --> 00:32:40.149 align:start position:0% works so I guess the T tldr of this is really<00:32:38.799> just<00:32:39.039> play<00:32:39.279> around<00:32:39.600> with<00:32:39.799> as<00:32:39.919> many 00:32:40.149 --> 00:32:40.159 align:start position:0% really just play around with as many 00:32:40.159 --> 00:32:43.149 align:start position:0% really just play around with as many tools<00:32:40.519> as<00:32:40.639> you<00:32:40.880> can<00:32:41.880> um<00:32:42.080> and<00:32:42.240> see<00:32:42.559> where<00:32:43.000> they 00:32:43.149 --> 00:32:43.159 align:start position:0% tools as you can um and see where they 00:32:43.159 --> 00:32:47.950 align:start position:0% tools as you can um and see where they help<00:32:43.399> you<00:32:43.559> the 00:32:47.950 --> 00:32:47.960 align:start position:0% 00:32:47.960 --> 00:32:51.110 align:start position:0% most<00:32:48.960> as<00:32:49.080> a<00:32:49.279> security<00:32:49.720> researcher<00:32:50.639> I've 00:32:51.110 --> 00:32:51.120 align:start position:0% most as a security researcher I've 00:32:51.120 --> 00:32:55.669 align:start position:0% most as a security researcher I've realized<00:32:52.120> that<00:32:53.039> um<00:32:53.880> how<00:32:54.279> developers<00:32:55.080> intended 00:32:55.669 --> 00:32:55.679 align:start position:0% realized that um how developers intended 00:32:55.679 --> 00:32:58.629 align:start position:0% realized that um how developers intended users<00:32:56.120> to<00:32:56.279> use<00:32:56.480> their<00:32:56.840> system<00:32:57.880> never<00:32:58.320> really 00:32:58.629 --> 00:32:58.639 align:start position:0% users to use their system never really 00:32:58.639 --> 00:33:02.350 align:start position:0% users to use their system never really matches<00:32:59.039> to<00:32:59.279> how<00:32:59.519> users<00:33:00.360> intend<00:33:00.760> to<00:33:00.919> use<00:33:01.240> it<00:33:02.240> I 00:33:02.350 --> 00:33:02.360 align:start position:0% matches to how users intend to use it I 00:33:02.360 --> 00:33:05.310 align:start position:0% matches to how users intend to use it I think<00:33:02.600> that's<00:33:02.880> just<00:33:03.240> because<00:33:04.240> um<00:33:04.720> developers 00:33:05.310 --> 00:33:05.320 align:start position:0% think that's just because um developers 00:33:05.320 --> 00:33:07.269 align:start position:0% think that's just because um developers have<00:33:05.480> an<00:33:05.679> assumption<00:33:06.200> of<00:33:06.639> you<00:33:06.760> know<00:33:07.000> this<00:33:07.120> is 00:33:07.269 --> 00:33:07.279 align:start position:0% have an assumption of you know this is 00:33:07.279 --> 00:33:09.269 align:start position:0% have an assumption of you know this is the<00:33:07.399> one<00:33:07.639> flow<00:33:08.039> that<00:33:08.159> users<00:33:08.440> are<00:33:08.600> going<00:33:08.799> to<00:33:08.960> use 00:33:09.269 --> 00:33:09.279 align:start position:0% the one flow that users are going to use 00:33:09.279 --> 00:33:12.350 align:start position:0% the one flow that users are going to use and<00:33:09.480> it's<00:33:09.720> just<00:33:10.000> this<00:33:10.120> is<00:33:10.480> this<00:33:10.600> is<00:33:10.760> it<00:33:11.720> um<00:33:12.200> and 00:33:12.350 --> 00:33:12.360 align:start position:0% and it's just this is this is it um and 00:33:12.360 --> 00:33:15.230 align:start position:0% and it's just this is this is it um and users<00:33:12.720> are<00:33:13.279> always<00:33:13.799> creative<00:33:14.360> in<00:33:14.519> terms<00:33:14.919> of 00:33:15.230 --> 00:33:15.240 align:start position:0% users are always creative in terms of 00:33:15.240 --> 00:33:17.230 align:start position:0% users are always creative in terms of arguments<00:33:15.960> or<00:33:16.279> just<00:33:16.519> like<00:33:16.679> the<00:33:16.840> ways<00:33:17.080> that 00:33:17.230 --> 00:33:17.240 align:start position:0% arguments or just like the ways that 00:33:17.240 --> 00:33:21.549 align:start position:0% arguments or just like the ways that they<00:33:17.399> call<00:33:17.639> Smart<00:33:18.320> contracts<00:33:19.320> um<00:33:20.120> any<00:33:20.399> kind<00:33:20.600> of 00:33:21.549 --> 00:33:21.559 align:start position:0% they call Smart contracts um any kind of 00:33:21.559 --> 00:33:23.870 align:start position:0% they call Smart contracts um any kind of any<00:33:22.120> potential<00:33:22.600> deviation<00:33:23.200> in<00:33:23.440> these<00:33:23.600> two 00:33:23.870 --> 00:33:23.880 align:start position:0% any potential deviation in these two 00:33:23.880 --> 00:33:28.029 align:start position:0% any potential deviation in these two things<00:33:24.320> can<00:33:24.600> be<00:33:25.519> um<00:33:25.760> a<00:33:25.919> fairly<00:33:26.320> big<00:33:26.639> bug<00:33:27.480> um<00:33:27.880> and 00:33:28.029 --> 00:33:28.039 align:start position:0% things can be um a fairly big bug um and 00:33:28.039 --> 00:33:30.509 align:start position:0% things can be um a fairly big bug um and can<00:33:28.279> result<00:33:28.679> in<00:33:29.440> like<00:33:29.600> an<00:33:29.799> impact<00:33:30.159> in<00:33:30.320> the 00:33:30.509 --> 00:33:30.519 align:start position:0% can result in like an impact in the 00:33:30.519 --> 00:33:36.350 align:start position:0% can result in like an impact in the system<00:33:31.240> um<00:33:31.399> so<00:33:31.559> it<00:33:31.679> is<00:33:31.880> one<00:33:32.519> area<00:33:33.080> to<00:33:33.279> look 00:33:36.350 --> 00:33:36.360 align:start position:0% 00:33:36.360 --> 00:33:39.590 align:start position:0% at<00:33:37.360> my<00:33:37.600> last<00:33:37.840> tip<00:33:38.360> is<00:33:38.600> to<00:33:38.919> lean<00:33:39.240> on<00:33:39.440> each 00:33:39.590 --> 00:33:39.600 align:start position:0% at my last tip is to lean on each 00:33:39.600 --> 00:33:43.830 align:start position:0% at my last tip is to lean on each other's<00:33:40.200> strengths<00:33:41.200> I<00:33:41.320> think<00:33:42.120> um<00:33:42.840> from<00:33:43.519> a 00:33:43.830 --> 00:33:43.840 align:start position:0% other's strengths I think um from a 00:33:43.840 --> 00:33:47.350 align:start position:0% other's strengths I think um from a security<00:33:44.320> researcher<00:33:45.120> side<00:33:46.080> um<00:33:46.480> I<00:33:46.559> mean<00:33:46.880> I<00:33:47.080> I<00:33:47.240> I 00:33:47.350 --> 00:33:47.360 align:start position:0% security researcher side um I mean I I I 00:33:47.360 --> 00:33:49.509 align:start position:0% security researcher side um I mean I I I was<00:33:47.760> kind<00:33:47.880> of<00:33:48.000> sitting<00:33:48.399> in<00:33:48.519> in<00:33:48.720> both<00:33:49.000> sides 00:33:49.509 --> 00:33:49.519 align:start position:0% was kind of sitting in in both sides 00:33:49.519 --> 00:33:53.870 align:start position:0% was kind of sitting in in both sides before<00:33:50.519> um<00:33:51.279> but<00:33:52.279> as<00:33:52.399> a<00:33:52.600> security<00:33:53.039> researcher 00:33:53.870 --> 00:33:53.880 align:start position:0% before um but as a security researcher 00:33:53.880 --> 00:33:56.629 align:start position:0% before um but as a security researcher they<00:33:54.039> bring<00:33:54.679> kind<00:33:54.799> of<00:33:55.399> understanding<00:33:56.000> of<00:33:56.519> you 00:33:56.629 --> 00:33:56.639 align:start position:0% they bring kind of understanding of you 00:33:56.639 --> 00:33:58.789 align:start position:0% they bring kind of understanding of you know<00:33:56.799> the<00:33:56.919> security<00:33:57.320> implication<00:33:58.159> of<00:33:58.360> in<00:33:58.519> the 00:33:58.789 --> 00:33:58.799 align:start position:0% know the security implication of in the 00:33:58.799 --> 00:34:03.389 align:start position:0% know the security implication of in the system<00:33:59.799> um<00:34:00.760> security<00:34:01.679> kind<00:34:01.840> of<00:34:02.279> um<00:34:02.840> tooling 00:34:03.389 --> 00:34:03.399 align:start position:0% system um security kind of um tooling 00:34:03.399 --> 00:34:06.149 align:start position:0% system um security kind of um tooling and<00:34:03.639> and<00:34:04.240> knowledge<00:34:04.880> there<00:34:05.399> developers 00:34:06.149 --> 00:34:06.159 align:start position:0% and and knowledge there developers 00:34:06.159 --> 00:34:08.069 align:start position:0% and and knowledge there developers usually<00:34:06.919> understand<00:34:07.240> how<00:34:07.519> they<00:34:07.639> want<00:34:07.840> their 00:34:08.069 --> 00:34:08.079 align:start position:0% usually understand how they want their 00:34:08.079 --> 00:34:11.470 align:start position:0% usually understand how they want their system<00:34:08.399> to<00:34:08.520> be<00:34:08.720> used<00:34:09.480> kind<00:34:09.599> of<00:34:09.800> the<00:34:09.960> more<00:34:10.839> um 00:34:11.470 --> 00:34:11.480 align:start position:0% system to be used kind of the more um 00:34:11.480 --> 00:34:14.750 align:start position:0% system to be used kind of the more um strategic<00:34:12.240> side<00:34:12.919> and<00:34:13.040> I<00:34:13.159> think<00:34:13.560> for<00:34:14.560> a 00:34:14.750 --> 00:34:14.760 align:start position:0% strategic side and I think for a 00:34:14.760 --> 00:34:16.669 align:start position:0% strategic side and I think for a security<00:34:15.240> review<00:34:15.879> you<00:34:16.000> can<00:34:16.200> really<00:34:16.399> take 00:34:16.669 --> 00:34:16.679 align:start position:0% security review you can really take 00:34:16.679 --> 00:34:19.270 align:start position:0% security review you can really take advantage<00:34:17.119> of<00:34:17.359> those<00:34:17.520> two<00:34:17.839> things<00:34:18.839> um<00:34:19.079> and 00:34:19.270 --> 00:34:19.280 align:start position:0% advantage of those two things um and 00:34:19.280 --> 00:34:20.869 align:start position:0% advantage of those two things um and really<00:34:19.599> collaborate<00:34:20.200> with<00:34:20.359> each<00:34:20.520> other<00:34:20.760> and 00:34:20.869 --> 00:34:20.879 align:start position:0% really collaborate with each other and 00:34:20.879 --> 00:34:22.349 align:start position:0% really collaborate with each other and lean<00:34:21.119> on<00:34:21.280> each<00:34:21.399> other's<00:34:21.760> strength<00:34:22.079> to 00:34:22.349 --> 00:34:22.359 align:start position:0% lean on each other's strength to 00:34:22.359 --> 00:34:25.550 align:start position:0% lean on each other's strength to maximize<00:34:23.359> or<00:34:23.639> rather<00:34:23.919> to<00:34:24.240> shorten<00:34:25.240> um<00:34:25.399> the 00:34:25.550 --> 00:34:25.560 align:start position:0% maximize or rather to shorten um the 00:34:25.560 --> 00:34:27.710 align:start position:0% maximize or rather to shorten um the amount<00:34:25.919> of<00:34:26.159> time<00:34:26.399> it<00:34:26.560> takes<00:34:27.000> both<00:34:27.240> parties<00:34:27.560> to 00:34:27.710 --> 00:34:27.720 align:start position:0% amount of time it takes both parties to 00:34:27.720 --> 00:34:29.669 align:start position:0% amount of time it takes both parties to to<00:34:28.079> understand<00:34:28.200> a<00:34:28.359> code<00:34:28.599> base<00:34:29.200> and<00:34:29.320> then<00:34:29.440> to 00:34:29.669 --> 00:34:29.679 align:start position:0% to understand a code base and then to 00:34:29.679 --> 00:34:31.349 align:start position:0% to understand a code base and then to maximize<00:34:30.200> the<00:34:30.320> number<00:34:30.560> of<00:34:30.720> bugs<00:34:31.000> you<00:34:31.119> find 00:34:31.349 --> 00:34:31.359 align:start position:0% maximize the number of bugs you find 00:34:31.359 --> 00:34:32.790 align:start position:0% maximize the number of bugs you find during<00:34:31.639> your 00:34:32.790 --> 00:34:32.800 align:start position:0% during your 00:34:32.800 --> 00:34:35.030 align:start position:0% during your review<00:34:33.800> all<00:34:33.919> right<00:34:34.200> with<00:34:34.359> that<00:34:34.480> I'll<00:34:34.720> pass<00:34:34.879> it 00:34:35.030 --> 00:34:35.040 align:start position:0% review all right with that I'll pass it 00:34:35.040 --> 00:34:37.590 align:start position:0% review all right with that I'll pass it off<00:34:35.399> to 00:34:37.590 --> 00:34:37.600 align:start position:0% off to 00:34:37.600 --> 00:34:39.790 align:start position:0% off to [Applause] 00:34:39.790 --> 00:34:39.800 align:start position:0% [Applause] 00:34:39.800 --> 00:34:43.669 align:start position:0% [Applause] Tino<00:34:40.800> hello<00:34:41.119> hello<00:34:41.399> hello<00:34:42.079> hi<00:34:42.399> everyone<00:34:43.399> let's 00:34:43.669 --> 00:34:43.679 align:start position:0% Tino hello hello hello hi everyone let's 00:34:43.679 --> 00:34:46.109 align:start position:0% Tino hello hello hello hi everyone let's put<00:34:43.800> the 00:34:46.109 --> 00:34:46.119 align:start position:0% 00:34:46.119 --> 00:34:49.310 align:start position:0% stopwatch<00:34:47.119> thank<00:34:47.280> you<00:34:48.280> hi<00:34:48.480> everyone<00:34:49.040> nice<00:34:49.200> to 00:34:49.310 --> 00:34:49.320 align:start position:0% stopwatch thank you hi everyone nice to 00:34:49.320 --> 00:34:50.829 align:start position:0% stopwatch thank you hi everyone nice to see<00:34:49.480> you<00:34:49.639> all<00:34:49.879> here<00:34:50.280> and<00:34:50.440> thank<00:34:50.599> you<00:34:50.679> for 00:34:50.829 --> 00:34:50.839 align:start position:0% see you all here and thank you for 00:34:50.839 --> 00:34:52.510 align:start position:0% see you all here and thank you for coming<00:34:51.159> I<00:34:51.240> know<00:34:51.359> it's<00:34:51.520> early<00:34:52.079> some<00:34:52.240> of<00:34:52.399> you 00:34:52.510 --> 00:34:52.520 align:start position:0% coming I know it's early some of you 00:34:52.520 --> 00:34:56.030 align:start position:0% coming I know it's early some of you went<00:34:52.720> partying<00:34:53.119> last<00:34:53.280> night<00:34:54.000> probably<00:34:55.040> um 00:34:56.030 --> 00:34:56.040 align:start position:0% went partying last night probably um 00:34:56.040 --> 00:34:59.390 align:start position:0% went partying last night probably um hopefully<00:34:56.399> not<00:34:56.520> too<00:34:56.720> hard<00:34:58.119> um<00:34:58.800> yeah<00:34:59.000> so<00:34:59.280> the 00:34:59.390 --> 00:34:59.400 align:start position:0% hopefully not too hard um yeah so the 00:34:59.400 --> 00:35:01.870 align:start position:0% hopefully not too hard um yeah so the idea<00:34:59.720> is<00:35:00.079> continuing<00:35:00.599> talking<00:35:00.920> about<00:35:01.680> these 00:35:01.870 --> 00:35:01.880 align:start position:0% idea is continuing talking about these 00:35:01.880 --> 00:35:05.109 align:start position:0% idea is continuing talking about these tips<00:35:02.760> uh<00:35:02.920> for<00:35:03.160> security<00:35:03.560> researchers<00:35:04.079> for 00:35:05.109 --> 00:35:05.119 align:start position:0% tips uh for security researchers for 00:35:05.119 --> 00:35:07.030 align:start position:0% tips uh for security researchers for developers<00:35:06.119> um<00:35:06.359> nice<00:35:06.520> to<00:35:06.640> see<00:35:06.839> many 00:35:07.030 --> 00:35:07.040 align:start position:0% developers um nice to see many 00:35:07.040 --> 00:35:09.069 align:start position:0% developers um nice to see many developers<00:35:07.480> in<00:35:07.560> the<00:35:07.720> room<00:35:08.440> next<00:35:08.640> time<00:35:08.800> perhaps 00:35:09.069 --> 00:35:09.079 align:start position:0% developers in the room next time perhaps 00:35:09.079 --> 00:35:10.589 align:start position:0% developers in the room next time perhaps you<00:35:09.200> can<00:35:09.320> put<00:35:09.480> like<00:35:09.640> security<00:35:10.000> researchers<00:35:10.440> on 00:35:10.589 --> 00:35:10.599 align:start position:0% you can put like security researchers on 00:35:10.599 --> 00:35:12.069 align:start position:0% you can put like security researchers on one<00:35:10.720> side<00:35:10.960> developers<00:35:11.400> on<00:35:11.520> the<00:35:11.640> other<00:35:11.800> and 00:35:12.069 --> 00:35:12.079 align:start position:0% one side developers on the other and 00:35:12.079 --> 00:35:14.109 align:start position:0% one side developers on the other and like<00:35:12.640> with<00:35:12.920> throw<00:35:13.119> each<00:35:13.240> other<00:35:13.599> stuff<00:35:13.960> or 00:35:14.109 --> 00:35:14.119 align:start position:0% like with throw each other stuff or 00:35:14.119 --> 00:35:15.790 align:start position:0% like with throw each other stuff or something<00:35:14.440> like<00:35:14.599> that<00:35:14.760> just<00:35:14.920> to<00:35:15.160> get<00:35:15.280> it 00:35:15.790 --> 00:35:15.800 align:start position:0% something like that just to get it 00:35:15.800 --> 00:35:19.750 align:start position:0% something like that just to get it started<00:35:16.800> uh<00:35:16.960> but<00:35:17.119> anyway<00:35:17.720> yeah 00:35:19.750 --> 00:35:19.760 align:start position:0% started uh but anyway yeah 00:35:19.760 --> 00:35:25.030 align:start position:0% started uh but anyway yeah let's<00:35:20.760> let's<00:35:21.000> be<00:35:21.160> honest<00:35:22.359> okay<00:35:23.359> I<00:35:23.440> don't<00:35:24.040> think 00:35:25.030 --> 00:35:25.040 align:start position:0% let's let's be honest okay I don't think 00:35:25.040 --> 00:35:27.910 align:start position:0% let's let's be honest okay I don't think many<00:35:25.320> of<00:35:25.480> us<00:35:25.680> here<00:35:25.920> I<00:35:26.040> include<00:35:26.400> myself<00:35:27.400> we<00:35:27.800> not 00:35:27.910 --> 00:35:27.920 align:start position:0% many of us here I include myself we not 00:35:27.920 --> 00:35:31.109 align:start position:0% many of us here I include myself we not going<00:35:28.000> to<00:35:28.160> invent<00:35:28.520> the<00:35:28.760> next<00:35:29.359> new<00:35:29.760> big<00:35:30.119> thing 00:35:31.109 --> 00:35:31.119 align:start position:0% going to invent the next new big thing 00:35:31.119 --> 00:35:33.430 align:start position:0% going to invent the next new big thing right<00:35:32.119> uh<00:35:32.280> it's<00:35:32.480> probably<00:35:32.800> the<00:35:32.960> case<00:35:33.160> that<00:35:33.320> we 00:35:33.430 --> 00:35:33.440 align:start position:0% right uh it's probably the case that we 00:35:33.440 --> 00:35:36.589 align:start position:0% right uh it's probably the case that we are<00:35:34.440> iterating<00:35:35.240> on<00:35:35.480> something<00:35:36.000> that<00:35:36.200> somebody 00:35:36.589 --> 00:35:36.599 align:start position:0% are iterating on something that somebody 00:35:36.599 --> 00:35:39.270 align:start position:0% are iterating on something that somebody else<00:35:36.800> in<00:35:36.920> the<00:35:37.079> past<00:35:37.520> built<00:35:38.520> or<00:35:38.680> that<00:35:38.880> somebody 00:35:39.270 --> 00:35:39.280 align:start position:0% else in the past built or that somebody 00:35:39.280 --> 00:35:40.670 align:start position:0% else in the past built or that somebody else<00:35:39.480> in<00:35:39.560> the<00:35:39.720> past 00:35:40.670 --> 00:35:40.680 align:start position:0% else in the past 00:35:40.680 --> 00:35:43.470 align:start position:0% else in the past found<00:35:41.680> so<00:35:41.880> it<00:35:42.040> might<00:35:42.280> make<00:35:42.520> sense<00:35:42.960> to<00:35:43.119> learn 00:35:43.470 --> 00:35:43.480 align:start position:0% found so it might make sense to learn 00:35:43.480 --> 00:35:46.109 align:start position:0% found so it might make sense to learn from<00:35:43.839> history<00:35:44.760> and<00:35:44.880> to<00:35:45.040> learn<00:35:45.400> from<00:35:45.680> what 00:35:46.109 --> 00:35:46.119 align:start position:0% from history and to learn from what 00:35:46.119 --> 00:35:48.069 align:start position:0% from history and to learn from what somebody<00:35:46.560> else<00:35:46.800> found<00:35:47.240> or<00:35:47.599> what<00:35:47.760> somebody 00:35:48.069 --> 00:35:48.079 align:start position:0% somebody else found or what somebody 00:35:48.079 --> 00:35:51.710 align:start position:0% somebody else found or what somebody else<00:35:48.880> built<00:35:49.880> uh<00:35:50.520> to<00:35:50.680> try<00:35:50.880> to<00:35:51.040> secure<00:35:51.359> the<00:35:51.480> thing 00:35:51.710 --> 00:35:51.720 align:start position:0% else built uh to try to secure the thing 00:35:51.720 --> 00:35:54.750 align:start position:0% else built uh to try to secure the thing that<00:35:51.839> we<00:35:51.920> are<00:35:52.079> doing<00:35:53.079> that<00:35:53.200> we<00:35:53.280> are<00:35:53.760> reviewing 00:35:54.750 --> 00:35:54.760 align:start position:0% that we are doing that we are reviewing 00:35:54.760 --> 00:35:57.630 align:start position:0% that we are doing that we are reviewing so<00:35:54.920> for<00:35:55.119> example<00:35:56.000> you<00:35:56.119> will<00:35:56.400> find<00:35:57.200> uh 00:35:57.630 --> 00:35:57.640 align:start position:0% so for example you will find uh 00:35:57.640 --> 00:35:59.069 align:start position:0% so for example you will find uh particularly<00:35:57.960> in<00:35:58.079> crypto<00:35:58.520> that<00:35:58.640> we<00:35:58.760> are<00:35:58.920> very 00:35:59.069 --> 00:35:59.079 align:start position:0% particularly in crypto that we are very 00:35:59.079 --> 00:36:02.430 align:start position:0% particularly in crypto that we are very good<00:35:59.240> at<00:36:00.040> publishing<00:36:00.560> things<00:36:01.480> is<00:36:01.599> not<00:36:01.880> usual 00:36:02.430 --> 00:36:02.440 align:start position:0% good at publishing things is not usual 00:36:02.440 --> 00:36:05.069 align:start position:0% good at publishing things is not usual in<00:36:02.839> the<00:36:03.000> rest<00:36:03.160> of<00:36:03.319> the<00:36:03.520> security<00:36:04.000> industry<00:36:05.000> uh 00:36:05.069 --> 00:36:05.079 align:start position:0% in the rest of the security industry uh 00:36:05.079 --> 00:36:06.990 align:start position:0% in the rest of the security industry uh to<00:36:05.280> public<00:36:05.640> audit<00:36:06.000> reports<00:36:06.480> you<00:36:06.560> should<00:36:06.800> take 00:36:06.990 --> 00:36:07.000 align:start position:0% to public audit reports you should take 00:36:07.000 --> 00:36:09.309 align:start position:0% to public audit reports you should take advantage<00:36:07.359> of<00:36:07.560> that<00:36:08.480> this<00:36:08.599> is<00:36:08.839> just<00:36:09.079> one 00:36:09.309 --> 00:36:09.319 align:start position:0% advantage of that this is just one 00:36:09.319 --> 00:36:12.470 align:start position:0% advantage of that this is just one example<00:36:09.839> of<00:36:10.000> Cypher<00:36:10.520> Sol<00:36:11.040> AIT<00:36:12.040> where<00:36:12.200> you<00:36:12.280> will 00:36:12.470 --> 00:36:12.480 align:start position:0% example of Cypher Sol AIT where you will 00:36:12.480 --> 00:36:15.230 align:start position:0% example of Cypher Sol AIT where you will find<00:36:12.760> a<00:36:13.160> basically<00:36:13.680> a<00:36:13.839> database<00:36:14.480> of<00:36:14.760> issues 00:36:15.230 --> 00:36:15.240 align:start position:0% find a basically a database of issues 00:36:15.240 --> 00:36:17.109 align:start position:0% find a basically a database of issues that<00:36:15.440> has<00:36:15.760> been<00:36:16.160> that<00:36:16.319> have<00:36:16.440> been<00:36:16.640> reported<00:36:17.000> in 00:36:17.109 --> 00:36:17.119 align:start position:0% that has been that have been reported in 00:36:17.119 --> 00:36:20.230 align:start position:0% that has been that have been reported in the<00:36:17.280> past<00:36:17.920> by<00:36:18.079> many<00:36:18.400> security<00:36:19.040> researchers<00:36:20.040> uh 00:36:20.230 --> 00:36:20.240 align:start position:0% the past by many security researchers uh 00:36:20.240 --> 00:36:22.150 align:start position:0% the past by many security researchers uh across<00:36:20.720> multiple<00:36:21.200> platforms<00:36:21.720> auditing 00:36:22.150 --> 00:36:22.160 align:start position:0% across multiple platforms auditing 00:36:22.160 --> 00:36:23.670 align:start position:0% across multiple platforms auditing companies<00:36:22.640> if<00:36:22.760> you<00:36:22.839> don't<00:36:23.000> want<00:36:23.160> to<00:36:23.280> use<00:36:23.520> this 00:36:23.670 --> 00:36:23.680 align:start position:0% companies if you don't want to use this 00:36:23.680 --> 00:36:25.230 align:start position:0% companies if you don't want to use this you<00:36:23.800> can<00:36:23.960> go<00:36:24.280> know<00:36:24.440> trailer<00:36:24.760> bits<00:36:25.000> I<00:36:25.079> think 00:36:25.230 --> 00:36:25.240 align:start position:0% you can go know trailer bits I think 00:36:25.240 --> 00:36:27.270 align:start position:0% you can go know trailer bits I think publishes<00:36:25.680> reports<00:36:26.040> open<00:36:26.280> sing<00:36:26.839> publishes 00:36:27.270 --> 00:36:27.280 align:start position:0% publishes reports open sing publishes 00:36:27.280 --> 00:36:29.630 align:start position:0% publishes reports open sing publishes con<00:36:27.720> intelligence<00:36:28.200> publes<00:36:28.839> Sigma<00:36:29.240> Prime<00:36:29.480> does 00:36:29.630 --> 00:36:29.640 align:start position:0% con intelligence publes Sigma Prime does 00:36:29.640 --> 00:36:31.990 align:start position:0% con intelligence publes Sigma Prime does the<00:36:29.760> same<00:36:30.240> and<00:36:30.359> I<00:36:30.520> could<00:36:30.720> go<00:36:30.920> on<00:36:31.079> and<00:36:31.200> on<00:36:31.359> and<00:36:31.520> on 00:36:31.990 --> 00:36:32.000 align:start position:0% the same and I could go on and on and on 00:36:32.000 --> 00:36:33.950 align:start position:0% the same and I could go on and on and on so<00:36:32.480> I'm<00:36:32.640> not<00:36:32.839> saying<00:36:33.160> that<00:36:33.319> you<00:36:33.440> should<00:36:33.720> read 00:36:33.950 --> 00:36:33.960 align:start position:0% so I'm not saying that you should read 00:36:33.960 --> 00:36:36.870 align:start position:0% so I'm not saying that you should read other<00:36:34.240> reports<00:36:34.800> like<00:36:34.920> you<00:36:35.000> read<00:36:35.200> a<00:36:35.440> novel<00:36:36.440> but 00:36:36.870 --> 00:36:36.880 align:start position:0% other reports like you read a novel but 00:36:36.880 --> 00:36:38.349 align:start position:0% other reports like you read a novel but probably<00:36:37.280> you<00:36:37.359> should<00:36:37.599> at<00:36:37.720> least<00:36:38.000> scheme 00:36:38.349 --> 00:36:38.359 align:start position:0% probably you should at least scheme 00:36:38.359 --> 00:36:41.349 align:start position:0% probably you should at least scheme through<00:36:38.599> them<00:36:39.079> if<00:36:39.240> you<00:36:39.359> are<00:36:40.200> building<00:36:40.640> a<00:36:40.800> new 00:36:41.349 --> 00:36:41.359 align:start position:0% through them if you are building a new 00:36:41.359 --> 00:36:43.829 align:start position:0% through them if you are building a new protocol<00:36:42.359> H<00:36:42.560> that<00:36:42.880> I<00:36:42.960> don't<00:36:43.040> know<00:36:43.200> it's<00:36:43.280> a<00:36:43.480> defi 00:36:43.829 --> 00:36:43.839 align:start position:0% protocol H that I don't know it's a defi 00:36:43.839 --> 00:36:46.109 align:start position:0% protocol H that I don't know it's a defi laring<00:36:44.280> stuff<00:36:44.640> or<00:36:44.839> some<00:36:45.200> deck<00:36:45.640> or<00:36:45.839> some 00:36:46.109 --> 00:36:46.119 align:start position:0% laring stuff or some deck or some 00:36:46.119 --> 00:36:48.990 align:start position:0% laring stuff or some deck or some whatever<00:36:46.480> that<00:36:46.599> you're<00:36:46.760> building<00:36:47.240> next<00:36:48.240> uh<00:36:48.480> go 00:36:48.990 --> 00:36:49.000 align:start position:0% whatever that you're building next uh go 00:36:49.000 --> 00:36:51.270 align:start position:0% whatever that you're building next uh go see<00:36:49.280> if<00:36:49.520> there's<00:36:49.960> some<00:36:50.280> similar<00:36:50.720> project<00:36:51.079> out 00:36:51.270 --> 00:36:51.280 align:start position:0% see if there's some similar project out 00:36:51.280 --> 00:36:53.430 align:start position:0% see if there's some similar project out there<00:36:52.040> that<00:36:52.240> has<00:36:52.400> done<00:36:52.680> similar<00:36:53.079> things<00:36:53.280> to 00:36:53.430 --> 00:36:53.440 align:start position:0% there that has done similar things to 00:36:53.440 --> 00:36:55.390 align:start position:0% there that has done similar things to you<00:36:53.720> that<00:36:53.960> probably<00:36:54.280> the<00:36:54.400> answer<00:36:54.640> is 00:36:55.390 --> 00:36:55.400 align:start position:0% you that probably the answer is 00:36:55.400 --> 00:36:58.030 align:start position:0% you that probably the answer is yes<00:36:56.400> and<00:36:56.599> go<00:36:56.760> read<00:36:56.960> the<00:36:57.079> issues<00:36:57.599> and<00:36:57.760> probably 00:36:58.030 --> 00:36:58.040 align:start position:0% yes and go read the issues and probably 00:36:58.040 --> 00:37:00.589 align:start position:0% yes and go read the issues and probably you<00:36:58.160> will<00:36:58.319> find<00:36:58.560> good<00:36:58.880> stuff<00:36:59.880> um<00:37:00.160> just<00:37:00.400> to 00:37:00.589 --> 00:37:00.599 align:start position:0% you will find good stuff um just to 00:37:00.599 --> 00:37:01.990 align:start position:0% you will find good stuff um just to double<00:37:00.880> check<00:37:01.160> if<00:37:01.240> you're<00:37:01.440> not<00:37:01.560> missing<00:37:01.839> out 00:37:01.990 --> 00:37:02.000 align:start position:0% double check if you're not missing out 00:37:02.000 --> 00:37:05.550 align:start position:0% double check if you're not missing out on<00:37:02.160> something<00:37:02.880> it's<00:37:03.119> sad<00:37:03.480> when<00:37:04.040> we<00:37:04.200> see<00:37:04.520> in<00:37:04.800> the 00:37:05.550 --> 00:37:05.560 align:start position:0% on something it's sad when we see in the 00:37:05.560 --> 00:37:07.430 align:start position:0% on something it's sad when we see in the out<00:37:05.760> there<00:37:05.839> in<00:37:05.960> the<00:37:06.119> community<00:37:06.760> the<00:37:06.960> same<00:37:07.200> and 00:37:07.430 --> 00:37:07.440 align:start position:0% out there in the community the same and 00:37:07.440 --> 00:37:09.109 align:start position:0% out there in the community the same and same<00:37:07.640> and<00:37:07.760> same<00:37:07.960> issues<00:37:08.400> being<00:37:08.640> repeated 00:37:09.109 --> 00:37:09.119 align:start position:0% same and same issues being repeated 00:37:09.119 --> 00:37:11.870 align:start position:0% same and same issues being repeated again<00:37:09.960> so<00:37:10.240> please<00:37:10.920> I<00:37:11.000> don't<00:37:11.119> know<00:37:11.440> take<00:37:11.599> a<00:37:11.760> look 00:37:11.870 --> 00:37:11.880 align:start position:0% again so please I don't know take a look 00:37:11.880 --> 00:37:15.109 align:start position:0% again so please I don't know take a look at<00:37:12.040> this<00:37:12.200> or<00:37:12.440> many<00:37:12.720> other<00:37:12.960> resources<00:37:13.400> out 00:37:15.109 --> 00:37:15.119 align:start position:0% at this or many other resources out 00:37:15.119 --> 00:37:17.950 align:start position:0% at this or many other resources out there<00:37:16.119> we<00:37:16.280> already<00:37:16.520> talked<00:37:16.800> about<00:37:17.079> this<00:37:17.760> uh 00:37:17.950 --> 00:37:17.960 align:start position:0% there we already talked about this uh 00:37:17.960 --> 00:37:20.829 align:start position:0% there we already talked about this uh but<00:37:18.160> I<00:37:18.280> just<00:37:18.440> want<00:37:18.599> to<00:37:18.720> reinforce<00:37:19.160> the<00:37:19.480> idea<00:37:20.480> um 00:37:20.829 --> 00:37:20.839 align:start position:0% but I just want to reinforce the idea um 00:37:20.839 --> 00:37:22.230 align:start position:0% but I just want to reinforce the idea um particularly<00:37:21.280> for<00:37:21.560> for<00:37:21.800> people<00:37:22.000> doing 00:37:22.230 --> 00:37:22.240 align:start position:0% particularly for for people doing 00:37:22.240 --> 00:37:25.150 align:start position:0% particularly for for people doing security<00:37:22.640> research<00:37:23.000> out<00:37:23.599> here<00:37:24.599> it's<00:37:24.800> very 00:37:25.150 --> 00:37:25.160 align:start position:0% security research out here it's very 00:37:25.160 --> 00:37:26.470 align:start position:0% security research out here it's very difficult<00:37:25.280> to<00:37:25.640> understand<00:37:25.920> to<00:37:26.079> what<00:37:26.240> extent 00:37:26.470 --> 00:37:26.480 align:start position:0% difficult to understand to what extent 00:37:26.480 --> 00:37:27.790 align:start position:0% difficult to understand to what extent you<00:37:26.560> should<00:37:26.760> go<00:37:26.920> deep<00:37:27.200> to<00:37:27.319> what<00:37:27.520> first<00:37:27.680> time 00:37:27.790 --> 00:37:27.800 align:start position:0% you should go deep to what first time 00:37:27.800 --> 00:37:30.230 align:start position:0% you should go deep to what first time you<00:37:27.880> should<00:37:28.079> go<00:37:28.319> white<00:37:29.200> uh<00:37:29.400> there's<00:37:29.640> no<00:37:29.920> clear 00:37:30.230 --> 00:37:30.240 align:start position:0% you should go white uh there's no clear 00:37:30.240 --> 00:37:33.030 align:start position:0% you should go white uh there's no clear answer<00:37:30.680> there's<00:37:30.920> never<00:37:31.200> a<00:37:31.359> clear<00:37:31.839> answer<00:37:32.839> uh 00:37:33.030 --> 00:37:33.040 align:start position:0% answer there's never a clear answer uh 00:37:33.040 --> 00:37:36.510 align:start position:0% answer there's never a clear answer uh my<00:37:33.200> only<00:37:33.599> tip<00:37:33.920> here<00:37:34.160> is<00:37:35.119> uh<00:37:35.319> whenever<00:37:35.720> you<00:37:35.839> are 00:37:36.510 --> 00:37:36.520 align:start position:0% my only tip here is uh whenever you are 00:37:36.520 --> 00:37:40.150 align:start position:0% my only tip here is uh whenever you are very<00:37:37.520> mat<00:37:37.800> in<00:37:38.079> depths<00:37:38.720> of<00:37:38.839> a<00:37:39.000> code<00:37:39.240> base<00:37:39.960> be 00:37:40.150 --> 00:37:40.160 align:start position:0% very mat in depths of a code base be 00:37:40.160 --> 00:37:43.349 align:start position:0% very mat in depths of a code base be careful<00:37:41.040> okay<00:37:42.040> um<00:37:42.240> it's<00:37:42.440> very<00:37:42.640> easy<00:37:42.839> to<00:37:43.000> get<00:37:43.160> in 00:37:43.349 --> 00:37:43.359 align:start position:0% careful okay um it's very easy to get in 00:37:43.359 --> 00:37:47.230 align:start position:0% careful okay um it's very easy to get in tangle<00:37:43.800> in<00:37:44.079> I<00:37:44.200> know<00:37:44.480> line<00:37:45.200> 250<00:37:46.200> of<00:37:46.440> that<00:37:47.040> a 00:37:47.230 --> 00:37:47.240 align:start position:0% tangle in I know line 250 of that a 00:37:47.240 --> 00:37:49.270 align:start position:0% tangle in I know line 250 of that a th000<00:37:47.680> line<00:37:48.160> assembly<00:37:48.680> code<00:37:48.920> that<00:37:49.079> you're 00:37:49.270 --> 00:37:49.280 align:start position:0% th000 line assembly code that you're 00:37:49.280 --> 00:37:51.030 align:start position:0% th000 line assembly code that you're reviewing<00:37:50.119> and<00:37:50.200> you<00:37:50.319> end<00:37:50.480> up<00:37:50.640> finding 00:37:51.030 --> 00:37:51.040 align:start position:0% reviewing and you end up finding 00:37:51.040 --> 00:37:53.390 align:start position:0% reviewing and you end up finding something<00:37:51.520> very<00:37:51.760> cool<00:37:52.160> that<00:37:52.319> I<00:37:52.480> know<00:37:53.079> you<00:37:53.240> can 00:37:53.390 --> 00:37:53.400 align:start position:0% something very cool that I know you can 00:37:53.400 --> 00:37:55.829 align:start position:0% something very cool that I know you can do<00:37:53.599> something<00:37:53.920> very<00:37:54.119> unexpected<00:37:54.720> in<00:37:54.880> that 00:37:55.829 --> 00:37:55.839 align:start position:0% do something very unexpected in that 00:37:55.839 --> 00:37:58.109 align:start position:0% do something very unexpected in that function<00:37:56.839> but<00:37:57.079> there<00:37:57.319> is<00:37:57.480> it's<00:37:57.640> very<00:37:57.800> hard<00:37:57.960> to 00:37:58.109 --> 00:37:58.119 align:start position:0% function but there is it's very hard to 00:37:58.119 --> 00:38:00.109 align:start position:0% function but there is it's very hard to sum<00:37:58.359> out<00:37:59.040> uh<00:37:59.200> because<00:37:59.400> you<00:37:59.480> need<00:37:59.640> to<00:37:59.760> find<00:37:59.960> the 00:38:00.109 --> 00:38:00.119 align:start position:0% sum out uh because you need to find the 00:38:00.119 --> 00:38:01.550 align:start position:0% sum out uh because you need to find the actual<00:38:00.359> attack<00:38:00.680> Vector<00:38:00.960> you<00:38:01.040> need<00:38:01.200> to 00:38:01.550 --> 00:38:01.560 align:start position:0% actual attack Vector you need to 00:38:01.560 --> 00:38:03.990 align:start position:0% actual attack Vector you need to understand<00:38:01.880> impact<00:38:02.359> in<00:38:02.480> the<00:38:02.680> project<00:38:03.520> and<00:38:03.640> to 00:38:03.990 --> 00:38:04.000 align:start position:0% understand impact in the project and to 00:38:04.000 --> 00:38:05.190 align:start position:0% understand impact in the project and to understand<00:38:04.200> impact<00:38:04.520> you<00:38:04.599> should<00:38:04.839> have 00:38:05.190 --> 00:38:05.200 align:start position:0% understand impact you should have 00:38:05.200 --> 00:38:07.470 align:start position:0% understand impact you should have context<00:38:06.200> how<00:38:06.359> many<00:38:06.599> times<00:38:06.920> have<00:38:07.040> you<00:38:07.200> found 00:38:07.470 --> 00:38:07.480 align:start position:0% context how many times have you found 00:38:07.480 --> 00:38:09.550 align:start position:0% context how many times have you found something<00:38:07.839> to<00:38:08.000> then<00:38:08.200> realize<00:38:08.560> that<00:38:08.800> well<00:38:09.400> yeah 00:38:09.550 --> 00:38:09.560 align:start position:0% something to then realize that well yeah 00:38:09.560 --> 00:38:12.390 align:start position:0% something to then realize that well yeah but<00:38:09.720> nobody<00:38:10.040> can<00:38:10.200> exploit<00:38:10.760> this<00:38:11.760> um<00:38:12.200> if<00:38:12.280> you 00:38:12.390 --> 00:38:12.400 align:start position:0% but nobody can exploit this um if you 00:38:12.400 --> 00:38:14.430 align:start position:0% but nobody can exploit this um if you are<00:38:12.560> a<00:38:12.680> little<00:38:12.839> bit<00:38:13.040> evil<00:38:13.319> you<00:38:13.480> might<00:38:13.640> end<00:38:13.760> up 00:38:14.430 --> 00:38:14.440 align:start position:0% are a little bit evil you might end up 00:38:14.440 --> 00:38:16.230 align:start position:0% are a little bit evil you might end up reporting<00:38:14.920> that<00:38:15.200> still<00:38:15.400> to<00:38:15.520> the<00:38:15.640> developers 00:38:16.230 --> 00:38:16.240 align:start position:0% reporting that still to the developers 00:38:16.240 --> 00:38:17.630 align:start position:0% reporting that still to the developers just<00:38:16.440> to<00:38:16.560> fight<00:38:16.839> with<00:38:17.000> them<00:38:17.240> and<00:38:17.359> they<00:38:17.480> will 00:38:17.630 --> 00:38:17.640 align:start position:0% just to fight with them and they will 00:38:17.640 --> 00:38:20.270 align:start position:0% just to fight with them and they will end<00:38:17.800> up<00:38:17.920> telling<00:38:18.160> you<00:38:18.319> that<00:38:18.560> well<00:38:19.359> uh<00:38:19.760> it's<00:38:19.880> not 00:38:20.270 --> 00:38:20.280 align:start position:0% end up telling you that well uh it's not 00:38:20.280 --> 00:38:23.230 align:start position:0% end up telling you that well uh it's not exploitable<00:38:21.280> so<00:38:21.560> zo<00:38:21.839> out<00:38:22.240> have<00:38:22.480> context 00:38:23.230 --> 00:38:23.240 align:start position:0% exploitable so zo out have context 00:38:23.240 --> 00:38:24.750 align:start position:0% exploitable so zo out have context understand<00:38:23.440> where<00:38:23.640> you<00:38:23.760> are<00:38:23.960> standing 00:38:24.750 --> 00:38:24.760 align:start position:0% understand where you are standing 00:38:24.760 --> 00:38:27.710 align:start position:0% understand where you are standing understand<00:38:25.280> the<00:38:25.440> expected<00:38:25.839> use<00:38:26.160> cases<00:38:27.000> uh<00:38:27.560> an 00:38:27.710 --> 00:38:27.720 align:start position:0% understand the expected use cases uh an 00:38:27.720 --> 00:38:29.910 align:start position:0% understand the expected use cases uh an issue<00:38:28.079> could<00:38:28.280> be<00:38:28.400> an<00:38:28.520> issue<00:38:28.760> for<00:38:28.960> you<00:38:29.280> but<00:38:29.800> if 00:38:29.910 --> 00:38:29.920 align:start position:0% issue could be an issue for you but if 00:38:29.920 --> 00:38:31.589 align:start position:0% issue could be an issue for you but if the<00:38:30.079> system<00:38:30.359> is<00:38:30.560> not<00:38:30.839> actually<00:38:31.160> expected<00:38:31.520> to 00:38:31.589 --> 00:38:31.599 align:start position:0% the system is not actually expected to 00:38:31.599 --> 00:38:32.870 align:start position:0% the system is not actually expected to be<00:38:31.720> used<00:38:31.960> that<00:38:32.119> way<00:38:32.280> I<00:38:32.319> don't<00:38:32.440> know<00:38:32.599> if<00:38:32.680> it's 00:38:32.870 --> 00:38:32.880 align:start position:0% be used that way I don't know if it's 00:38:32.880 --> 00:38:34.550 align:start position:0% be used that way I don't know if it's not<00:38:33.119> expected<00:38:33.440> to<00:38:33.560> integrate<00:38:34.040> with<00:38:34.240> that 00:38:34.550 --> 00:38:34.560 align:start position:0% not expected to integrate with that 00:38:34.560 --> 00:38:35.870 align:start position:0% not expected to integrate with that other<00:38:34.800> protocol<00:38:35.200> that<00:38:35.319> you're<00:38:35.560> thinking 00:38:35.870 --> 00:38:35.880 align:start position:0% other protocol that you're thinking 00:38:35.880 --> 00:38:37.829 align:start position:0% other protocol that you're thinking about<00:38:36.400> or<00:38:36.560> it's<00:38:36.680> not<00:38:36.960> respective<00:38:37.359> to<00:38:37.440> use<00:38:37.640> that 00:38:37.829 --> 00:38:37.839 align:start position:0% about or it's not respective to use that 00:38:37.839 --> 00:38:40.069 align:start position:0% about or it's not respective to use that token<00:38:38.160> that<00:38:38.240> you're<00:38:38.480> thinking<00:38:38.800> about<00:38:39.599> your<00:38:39.800> is 00:38:40.069 --> 00:38:40.079 align:start position:0% token that you're thinking about your is 00:38:40.079 --> 00:38:43.990 align:start position:0% token that you're thinking about your is won't<00:38:40.319> make<00:38:40.839> sense<00:38:41.839> so<00:38:42.560> uh<00:38:43.480> have<00:38:43.640> in<00:38:43.760> mind 00:38:43.990 --> 00:38:44.000 align:start position:0% won't make sense so uh have in mind 00:38:44.000 --> 00:38:45.790 align:start position:0% won't make sense so uh have in mind these<00:38:44.160> kind<00:38:44.280> of 00:38:45.790 --> 00:38:45.800 align:start position:0% these kind of 00:38:45.800 --> 00:38:50.150 align:start position:0% these kind of things<00:38:46.800> di<00:38:47.000> Mission<00:38:47.560> returns<00:38:48.560> uh<00:38:48.839> are<00:38:49.119> a<00:38:49.960> I 00:38:50.150 --> 00:38:50.160 align:start position:0% things di Mission returns uh are a I 00:38:50.160 --> 00:38:52.470 align:start position:0% things di Mission returns uh are a I know<00:38:50.480> something<00:38:50.760> that<00:38:50.880> I<00:38:51.000> struggle<00:38:51.480> with<00:38:52.280> and 00:38:52.470 --> 00:38:52.480 align:start position:0% know something that I struggle with and 00:38:52.480 --> 00:38:53.870 align:start position:0% know something that I struggle with and actually<00:38:52.760> I<00:38:52.880> have<00:38:53.079> questions<00:38:53.400> I<00:38:53.520> don't<00:38:53.680> have 00:38:53.870 --> 00:38:53.880 align:start position:0% actually I have questions I don't have 00:38:53.880 --> 00:38:56.030 align:start position:0% actually I have questions I don't have tips<00:38:54.440> uh<00:38:54.599> I<00:38:54.680> will<00:38:54.880> borrow<00:38:55.280> tips<00:38:55.560> from<00:38:55.760> you<00:38:55.920> if 00:38:56.030 --> 00:38:56.040 align:start position:0% tips uh I will borrow tips from you if 00:38:56.040 --> 00:38:58.910 align:start position:0% tips uh I will borrow tips from you if you<00:38:56.280> have<00:38:56.480> some<00:38:56.880> similar<00:38:57.440> bullets<00:38:57.760> to<00:38:57.880> solve 00:38:58.910 --> 00:38:58.920 align:start position:0% you have some similar bullets to solve 00:38:58.920 --> 00:39:01.589 align:start position:0% you have some similar bullets to solve this<00:38:59.920> um<00:39:00.200> I<00:39:00.319> usually<00:39:00.640> don't<00:39:00.839> know<00:39:01.240> to<00:39:01.400> what 00:39:01.589 --> 00:39:01.599 align:start position:0% this um I usually don't know to what 00:39:01.599 --> 00:39:03.309 align:start position:0% this um I usually don't know to what extent<00:39:01.960> I<00:39:02.079> should<00:39:02.240> be<00:39:02.359> chasing<00:39:02.720> down<00:39:02.880> bus<00:39:03.280> I 00:39:03.309 --> 00:39:03.319 align:start position:0% extent I should be chasing down bus I 00:39:03.319 --> 00:39:04.470 align:start position:0% extent I should be chasing down bus I mean<00:39:03.480> it<00:39:03.560> will<00:39:03.720> depend<00:39:03.960> on<00:39:04.079> the<00:39:04.200> kind<00:39:04.319> of 00:39:04.470 --> 00:39:04.480 align:start position:0% mean it will depend on the kind of 00:39:04.480 --> 00:39:06.710 align:start position:0% mean it will depend on the kind of Engagement<00:39:04.880> that<00:39:04.960> you're<00:39:05.119> doing<00:39:05.480> right<00:39:05.680> so<00:39:06.640> I 00:39:06.710 --> 00:39:06.720 align:start position:0% Engagement that you're doing right so I 00:39:06.720 --> 00:39:08.349 align:start position:0% Engagement that you're doing right so I will<00:39:06.880> talk<00:39:07.079> about<00:39:07.280> this<00:39:07.440> later<00:39:07.680> but<00:39:07.839> auditing 00:39:08.349 --> 00:39:08.359 align:start position:0% will talk about this later but auditing 00:39:08.359 --> 00:39:10.109 align:start position:0% will talk about this later but auditing is<00:39:08.520> not<00:39:08.720> back<00:39:09.000> hunting<00:39:09.359> and<00:39:09.520> it's<00:39:09.640> not<00:39:09.839> doing 00:39:10.109 --> 00:39:10.119 align:start position:0% is not back hunting and it's not doing 00:39:10.119 --> 00:39:12.510 align:start position:0% is not back hunting and it's not doing contest<00:39:10.520> for<00:39:10.760> example<00:39:11.760> so<00:39:11.920> to<00:39:12.119> what<00:39:12.240> extent 00:39:12.510 --> 00:39:12.520 align:start position:0% contest for example so to what extent 00:39:12.520 --> 00:39:15.030 align:start position:0% contest for example so to what extent you<00:39:12.599> should<00:39:12.720> be<00:39:12.839> chasing<00:39:13.160> that<00:39:13.400> bags<00:39:14.359> um<00:39:14.839> to 00:39:15.030 --> 00:39:15.040 align:start position:0% you should be chasing that bags um to 00:39:15.040 --> 00:39:16.510 align:start position:0% you should be chasing that bags um to what<00:39:15.200> extent<00:39:15.480> you<00:39:15.560> should<00:39:15.760> be<00:39:16.040> going<00:39:16.319> into 00:39:16.510 --> 00:39:16.520 align:start position:0% what extent you should be going into 00:39:16.520 --> 00:39:18.069 align:start position:0% what extent you should be going into that<00:39:16.680> rabit<00:39:16.960> hole<00:39:17.240> when<00:39:17.400> should<00:39:17.760> should<00:39:17.960> you 00:39:18.069 --> 00:39:18.079 align:start position:0% that rabit hole when should should you 00:39:18.079 --> 00:39:20.470 align:start position:0% that rabit hole when should should you stop<00:39:18.800> probably<00:39:19.200> experience<00:39:19.920> will<00:39:20.119> tell<00:39:20.319> you 00:39:20.470 --> 00:39:20.480 align:start position:0% stop probably experience will tell you 00:39:20.480 --> 00:39:21.589 align:start position:0% stop probably experience will tell you something<00:39:20.800> about 00:39:21.589 --> 00:39:21.599 align:start position:0% something about 00:39:21.599 --> 00:39:23.910 align:start position:0% something about it<00:39:22.599> uh<00:39:22.720> you<00:39:22.839> will<00:39:23.119> start<00:39:23.319> growing<00:39:23.640> some 00:39:23.910 --> 00:39:23.920 align:start position:0% it uh you will start growing some 00:39:23.920 --> 00:39:26.349 align:start position:0% it uh you will start growing some intuitions<00:39:24.920> little<00:39:25.200> by<00:39:25.400> little<00:39:25.800> on<00:39:26.000> to<00:39:26.160> what 00:39:26.349 --> 00:39:26.359 align:start position:0% intuitions little by little on to what 00:39:26.359 --> 00:39:28.349 align:start position:0% intuitions little by little on to what extent<00:39:26.599> you<00:39:26.720> should<00:39:26.920> be<00:39:27.480> yeah<00:39:27.680> going<00:39:28.040> down 00:39:28.349 --> 00:39:28.359 align:start position:0% extent you should be yeah going down 00:39:28.359 --> 00:39:31.510 align:start position:0% extent you should be yeah going down certain<00:39:28.800> paths<00:39:29.359> and<00:39:29.520> not<00:39:29.640> choosing<00:39:30.520> others 00:39:31.510 --> 00:39:31.520 align:start position:0% certain paths and not choosing others 00:39:31.520 --> 00:39:33.030 align:start position:0% certain paths and not choosing others then<00:39:31.680> when<00:39:31.800> it<00:39:31.880> comes<00:39:32.040> to<00:39:32.200> reporting<00:39:32.760> doing 00:39:33.030 --> 00:39:33.040 align:start position:0% then when it comes to reporting doing 00:39:33.040 --> 00:39:35.990 align:start position:0% then when it comes to reporting doing Prof<00:39:33.440> Concepts<00:39:33.880> is<00:39:34.079> also<00:39:34.800> a<00:39:34.960> place<00:39:35.200> where<00:39:35.480> we 00:39:35.990 --> 00:39:36.000 align:start position:0% Prof Concepts is also a place where we 00:39:36.000 --> 00:39:38.910 align:start position:0% Prof Concepts is also a place where we lose<00:39:36.400> ourselves<00:39:37.200> as<00:39:37.680> security 00:39:38.910 --> 00:39:38.920 align:start position:0% lose ourselves as security 00:39:38.920 --> 00:39:42.790 align:start position:0% lose ourselves as security people<00:39:39.920> um<00:39:40.800> how<00:39:41.040> much<00:39:41.599> detail<00:39:42.240> should<00:39:42.440> you<00:39:42.640> put 00:39:42.790 --> 00:39:42.800 align:start position:0% people um how much detail should you put 00:39:42.800 --> 00:39:44.630 align:start position:0% people um how much detail should you put in<00:39:43.000> that<00:39:43.839> how 00:39:44.630 --> 00:39:44.640 align:start position:0% in that how 00:39:44.640 --> 00:39:46.990 align:start position:0% in that how many<00:39:45.640> I<00:39:45.800> know<00:39:46.000> how<00:39:46.119> much<00:39:46.319> infrastructure 00:39:46.990 --> 00:39:47.000 align:start position:0% many I know how much infrastructure 00:39:47.000 --> 00:39:49.030 align:start position:0% many I know how much infrastructure should<00:39:47.319> you<00:39:47.680> be<00:39:47.839> setting<00:39:48.160> up<00:39:48.359> to<00:39:48.520> test<00:39:48.839> that 00:39:49.030 --> 00:39:49.040 align:start position:0% should you be setting up to test that 00:39:49.040 --> 00:39:51.109 align:start position:0% should you be setting up to test that bag<00:39:49.359> you<00:39:49.520> found<00:39:49.800> in<00:39:49.960> that<00:39:50.119> bridge<00:39:50.560> with<00:39:50.920> that 00:39:51.109 --> 00:39:51.119 align:start position:0% bag you found in that bridge with that 00:39:51.119 --> 00:39:53.510 align:start position:0% bag you found in that bridge with that connect<00:39:51.839> a<00:39:52.040> thousand<00:39:52.560> layer<00:39:53.040> threes<00:39:53.359> and 00:39:53.510 --> 00:39:53.520 align:start position:0% connect a thousand layer threes and 00:39:53.520 --> 00:39:55.790 align:start position:0% connect a thousand layer threes and fours<00:39:53.800> and<00:39:54.119> whatever<00:39:55.119> uh<00:39:55.400> sometimes<00:39:55.560> it's 00:39:55.790 --> 00:39:55.800 align:start position:0% fours and whatever uh sometimes it's 00:39:55.800 --> 00:39:57.390 align:start position:0% fours and whatever uh sometimes it's very<00:39:56.000> complicated<00:39:56.520> and<00:39:56.640> you<00:39:56.800> might<00:39:56.960> end<00:39:57.119> up 00:39:57.390 --> 00:39:57.400 align:start position:0% very complicated and you might end up 00:39:57.400 --> 00:40:00.750 align:start position:0% very complicated and you might end up losing<00:39:57.800> too<00:39:58.000> much<00:39:58.280> time<00:39:58.480> on<00:39:58.680> that<00:39:59.560> I've 00:40:00.750 --> 00:40:00.760 align:start position:0% losing too much time on that I've 00:40:00.760 --> 00:40:03.230 align:start position:0% losing too much time on that I've been<00:40:01.760> sometimes<00:40:02.079> like<00:40:02.240> a<00:40:02.359> week<00:40:02.680> trying<00:40:02.920> to<00:40:03.040> set 00:40:03.230 --> 00:40:03.240 align:start position:0% been sometimes like a week trying to set 00:40:03.240 --> 00:40:05.990 align:start position:0% been sometimes like a week trying to set up<00:40:03.400> a<00:40:03.560> whole<00:40:04.359> test<00:40:04.680> n<00:40:04.920> environment<00:40:05.480> to<00:40:05.640> try<00:40:05.839> out 00:40:05.990 --> 00:40:06.000 align:start position:0% up a whole test n environment to try out 00:40:06.000 --> 00:40:09.270 align:start position:0% up a whole test n environment to try out an<00:40:06.319> exploit<00:40:07.319> uh<00:40:07.520> just<00:40:07.720> to<00:40:07.920> realize<00:40:08.359> that<00:40:08.599> then 00:40:09.270 --> 00:40:09.280 align:start position:0% an exploit uh just to realize that then 00:40:09.280 --> 00:40:11.270 align:start position:0% an exploit uh just to realize that then when<00:40:09.400> I<00:40:09.560> reported<00:40:10.040> perhaps<00:40:10.520> it<00:40:10.680> wasn't<00:40:11.119> the 00:40:11.270 --> 00:40:11.280 align:start position:0% when I reported perhaps it wasn't the 00:40:11.280 --> 00:40:14.390 align:start position:0% when I reported perhaps it wasn't the case<00:40:11.920> or<00:40:12.160> the<00:40:12.280> proof<00:40:12.480> of<00:40:12.640> concept<00:40:13.640> it's<00:40:14.000> too 00:40:14.390 --> 00:40:14.400 align:start position:0% case or the proof of concept it's too 00:40:14.400 --> 00:40:17.829 align:start position:0% case or the proof of concept it's too complicated<00:40:14.880> to<00:40:15.040> run<00:40:15.680> or<00:40:15.960> I<00:40:16.079> end<00:40:16.280> up<00:40:16.960> debugging 00:40:17.829 --> 00:40:17.839 align:start position:0% complicated to run or I end up debugging 00:40:17.839 --> 00:40:20.630 align:start position:0% complicated to run or I end up debugging the<00:40:18.599> my<00:40:18.800> own<00:40:19.480> proof<00:40:19.880> concept<00:40:20.240> instead<00:40:20.480> of 00:40:20.630 --> 00:40:20.640 align:start position:0% the my own proof concept instead of 00:40:20.640 --> 00:40:22.030 align:start position:0% the my own proof concept instead of debugging<00:40:21.079> the<00:40:21.160> actual<00:40:21.440> code<00:40:21.640> that<00:40:21.720> I<00:40:21.800> need<00:40:21.920> to 00:40:22.030 --> 00:40:22.040 align:start position:0% debugging the actual code that I need to 00:40:22.040 --> 00:40:25.990 align:start position:0% debugging the actual code that I need to review<00:40:23.000> so<00:40:23.400> again<00:40:24.160> just<00:40:24.800> uh<00:40:25.319> questions<00:40:25.760> to 00:40:25.990 --> 00:40:26.000 align:start position:0% review so again just uh questions to 00:40:26.000 --> 00:40:28.630 align:start position:0% review so again just uh questions to think<00:40:26.280> about<00:40:26.640> things<00:40:26.839> to<00:40:27.000> consider<00:40:27.640> either 00:40:28.630 --> 00:40:28.640 align:start position:0% think about things to consider either 00:40:28.640 --> 00:40:30.510 align:start position:0% think about things to consider either and<00:40:28.760> then<00:40:28.920> the<00:40:29.040> last<00:40:29.240> one<00:40:29.480> I'm<00:40:29.599> not<00:40:29.760> a<00:40:29.920> very<00:40:30.319> big 00:40:30.510 --> 00:40:30.520 align:start position:0% and then the last one I'm not a very big 00:40:30.520 --> 00:40:33.510 align:start position:0% and then the last one I'm not a very big fan<00:40:30.760> of<00:40:31.359> uh<00:40:31.839> this<00:40:32.000> new<00:40:32.319> security<00:40:32.800> contest<00:40:33.359> but 00:40:33.510 --> 00:40:33.520 align:start position:0% fan of uh this new security contest but 00:40:33.520 --> 00:40:36.190 align:start position:0% fan of uh this new security contest but some<00:40:33.680> people<00:40:34.000> in<00:40:34.119> the<00:40:34.240> room<00:40:34.520> might<00:40:34.839> be<00:40:35.839> um<00:40:36.119> you 00:40:36.190 --> 00:40:36.200 align:start position:0% some people in the room might be um you 00:40:36.200 --> 00:40:38.630 align:start position:0% some people in the room might be um you will<00:40:36.400> find<00:40:36.599> this<00:40:36.880> escalation<00:40:37.800> Wars<00:40:38.400> if<00:40:38.480> you're 00:40:38.630 --> 00:40:38.640 align:start position:0% will find this escalation Wars if you're 00:40:38.640 --> 00:40:40.829 align:start position:0% will find this escalation Wars if you're not<00:40:38.800> familiar<00:40:39.119> with<00:40:39.280> it<00:40:39.520> essentially<00:40:40.520> uh<00:40:40.680> in 00:40:40.829 --> 00:40:40.839 align:start position:0% not familiar with it essentially uh in 00:40:40.839 --> 00:40:42.230 align:start position:0% not familiar with it essentially uh in contest<00:40:41.240> you<00:40:41.319> will<00:40:41.480> find<00:40:41.760> people<00:40:42.000> like 00:40:42.230 --> 00:40:42.240 align:start position:0% contest you will find people like 00:40:42.240 --> 00:40:44.550 align:start position:0% contest you will find people like competing<00:40:42.760> to<00:40:42.960> submit<00:40:43.400> bags<00:40:44.040> at<00:40:44.160> some<00:40:44.359> point 00:40:44.550 --> 00:40:44.560 align:start position:0% competing to submit bags at some point 00:40:44.560 --> 00:40:46.670 align:start position:0% competing to submit bags at some point in<00:40:44.720> time<00:40:45.319> there<00:40:45.640> I<00:40:45.760> think<00:40:46.000> this<00:40:46.200> is<00:40:46.359> true<00:40:46.560> in 00:40:46.670 --> 00:40:46.680 align:start position:0% in time there I think this is true in 00:40:46.680 --> 00:40:48.750 align:start position:0% in time there I think this is true in all<00:40:47.040> in<00:40:47.160> many<00:40:47.400> platforms<00:40:47.880> but<00:40:48.040> they<00:40:48.160> all<00:40:48.480> do 00:40:48.750 --> 00:40:48.760 align:start position:0% all in many platforms but they all do 00:40:48.760 --> 00:40:50.630 align:start position:0% all in many platforms but they all do the<00:40:49.319> similar<00:40:49.680> things<00:40:49.920> but<00:40:50.040> not<00:40:50.240> exactly<00:40:50.520> the 00:40:50.630 --> 00:40:50.640 align:start position:0% the similar things but not exactly the 00:40:50.640 --> 00:40:52.829 align:start position:0% the similar things but not exactly the same<00:40:51.480> uh<00:40:51.640> people<00:40:51.880> will<00:40:52.119> start<00:40:52.319> fighting<00:40:52.720> each 00:40:52.829 --> 00:40:52.839 align:start position:0% same uh people will start fighting each 00:40:52.839 --> 00:40:56.270 align:start position:0% same uh people will start fighting each other<00:40:53.200> just<00:40:53.400> to<00:40:54.280> um<00:40:55.119> escalate<00:40:55.720> their<00:40:55.920> issues 00:40:56.270 --> 00:40:56.280 align:start position:0% other just to um escalate their issues 00:40:56.280 --> 00:40:58.150 align:start position:0% other just to um escalate their issues and<00:40:56.400> try<00:40:56.599> to<00:40:56.680> make<00:40:56.839> them<00:40:56.960> more<00:40:57.680> or<00:40:57.800> to<00:40:57.920> fight 00:40:58.150 --> 00:40:58.160 align:start position:0% and try to make them more or to fight 00:40:58.160 --> 00:41:00.190 align:start position:0% and try to make them more or to fight back<00:40:58.359> the<00:40:58.480> judges<00:40:58.880> or<00:40:59.040> whatever<00:40:59.800> and<00:40:59.920> you<00:41:00.040> will 00:41:00.190 --> 00:41:00.200 align:start position:0% back the judges or whatever and you will 00:41:00.200 --> 00:41:03.309 align:start position:0% back the judges or whatever and you will see<00:41:00.480> like<00:41:01.400> endless<00:41:02.000> threats<00:41:02.480> of<00:41:02.680> people 00:41:03.309 --> 00:41:03.319 align:start position:0% see like endless threats of people 00:41:03.319 --> 00:41:05.910 align:start position:0% see like endless threats of people throwing<00:41:03.920> at<00:41:04.040> each<00:41:04.200> other<00:41:05.079> um<00:41:05.640> and 00:41:05.910 --> 00:41:05.920 align:start position:0% throwing at each other um and 00:41:05.920 --> 00:41:07.910 align:start position:0% throwing at each other um and spending<00:41:06.400> precious<00:41:06.839> time<00:41:07.040> on<00:41:07.280> that<00:41:07.720> while 00:41:07.910 --> 00:41:07.920 align:start position:0% spending precious time on that while 00:41:07.920 --> 00:41:09.109 align:start position:0% spending precious time on that while they<00:41:08.079> could<00:41:08.240> be<00:41:08.400> doing<00:41:08.680> something<00:41:08.960> more 00:41:09.109 --> 00:41:09.119 align:start position:0% they could be doing something more 00:41:09.119 --> 00:41:12.589 align:start position:0% they could be doing something more valuable<00:41:09.480> for<00:41:09.599> the<00:41:10.040> ecosystem<00:41:11.040> um<00:41:11.839> but<00:41:12.079> again 00:41:12.589 --> 00:41:12.599 align:start position:0% valuable for the ecosystem um but again 00:41:12.599 --> 00:41:15.230 align:start position:0% valuable for the ecosystem um but again I've<00:41:12.760> been<00:41:13.200> in<00:41:13.560> some<00:41:13.800> cases<00:41:14.240> there<00:41:14.720> and<00:41:14.839> I<00:41:14.960> know 00:41:15.230 --> 00:41:15.240 align:start position:0% I've been in some cases there and I know 00:41:15.240 --> 00:41:17.829 align:start position:0% I've been in some cases there and I know the<00:41:15.319> feeling<00:41:15.720> and<00:41:15.839> it's<00:41:16.119> very<00:41:16.359> hard<00:41:16.560> to<00:41:17.400> to 00:41:17.829 --> 00:41:17.839 align:start position:0% the feeling and it's very hard to to 00:41:17.839 --> 00:41:19.750 align:start position:0% the feeling and it's very hard to to understand<00:41:17.960> to<00:41:18.119> what<00:41:18.280> extent<00:41:18.720> we<00:41:18.800> should<00:41:19.040> be 00:41:19.750 --> 00:41:19.760 align:start position:0% understand to what extent we should be 00:41:19.760 --> 00:41:23.870 align:start position:0% understand to what extent we should be doing<00:41:20.079> it<00:41:20.520> uh<00:41:20.640> but<00:41:20.800> anyway<00:41:21.119> dimin 00:41:23.870 --> 00:41:23.880 align:start position:0% 00:41:23.880 --> 00:41:25.550 align:start position:0% returns 00:41:25.550 --> 00:41:25.560 align:start position:0% returns 00:41:25.560 --> 00:41:28.750 align:start position:0% returns uh<00:41:26.560> okay<00:41:26.760> diagrams<00:41:27.400> yes<00:41:27.560> I<00:41:27.760> love<00:41:27.960> this 00:41:28.750 --> 00:41:28.760 align:start position:0% uh okay diagrams yes I love this 00:41:28.760 --> 00:41:32.069 align:start position:0% uh okay diagrams yes I love this part<00:41:29.760> as<00:41:29.920> a<00:41:30.160> security<00:41:30.560> researcher<00:41:31.240> I'm 00:41:32.069 --> 00:41:32.079 align:start position:0% part as a security researcher I'm 00:41:32.079 --> 00:41:36.430 align:start position:0% part as a security researcher I'm a<00:41:33.079> visual<00:41:33.560> thinker<00:41:34.560> so<00:41:34.720> that<00:41:34.880> means<00:41:35.119> that<00:41:35.440> I 00:41:36.430 --> 00:41:36.440 align:start position:0% a visual thinker so that means that I 00:41:36.440 --> 00:41:38.309 align:start position:0% a visual thinker so that means that I often<00:41:36.720> times<00:41:36.960> find<00:41:37.240> myself<00:41:37.680> like<00:41:37.800> drawing 00:41:38.309 --> 00:41:38.319 align:start position:0% often times find myself like drawing 00:41:38.319 --> 00:41:39.950 align:start position:0% often times find myself like drawing stuff<00:41:38.720> just<00:41:38.880> to<00:41:39.160> think<00:41:39.400> about<00:41:39.640> the<00:41:39.760> things 00:41:39.950 --> 00:41:39.960 align:start position:0% stuff just to think about the things 00:41:39.960 --> 00:41:41.630 align:start position:0% stuff just to think about the things that<00:41:40.079> I<00:41:40.200> want<00:41:40.319> to<00:41:40.480> do<00:41:40.680> I<00:41:40.760> also<00:41:41.000> write<00:41:41.200> a<00:41:41.319> lot<00:41:41.520> and 00:41:41.630 --> 00:41:41.640 align:start position:0% that I want to do I also write a lot and 00:41:41.640 --> 00:41:44.589 align:start position:0% that I want to do I also write a lot and I<00:41:41.720> will<00:41:41.880> tell<00:41:42.040> you<00:41:42.200> all<00:41:42.440> writing<00:41:43.160> then<00:41:44.160> uh<00:41:44.440> but 00:41:44.589 --> 00:41:44.599 align:start position:0% I will tell you all writing then uh but 00:41:44.599 --> 00:41:47.430 align:start position:0% I will tell you all writing then uh but let's<00:41:44.839> talk<00:41:45.160> diagrams<00:41:45.720> now<00:41:46.720> I<00:41:46.800> use<00:41:47.040> diagrams 00:41:47.430 --> 00:41:47.440 align:start position:0% let's talk diagrams now I use diagrams 00:41:47.440 --> 00:41:49.670 align:start position:0% let's talk diagrams now I use diagrams to<00:41:47.800> understand<00:41:48.040> systems<00:41:48.800> and<00:41:48.960> this<00:41:49.240> I<00:41:49.400> and<00:41:49.520> I 00:41:49.670 --> 00:41:49.680 align:start position:0% to understand systems and this I and I 00:41:49.680 --> 00:41:52.910 align:start position:0% to understand systems and this I and I do<00:41:50.000> different<00:41:50.359> kind<00:41:51.000> of<00:41:52.000> uh<00:41:52.160> level<00:41:52.400> of<00:41:52.560> details 00:41:52.910 --> 00:41:52.920 align:start position:0% do different kind of uh level of details 00:41:52.920 --> 00:41:54.670 align:start position:0% do different kind of uh level of details in<00:41:53.079> diagrams<00:41:53.560> this<00:41:53.720> was<00:41:53.920> me<00:41:54.119> for<00:41:54.319> example 00:41:54.670 --> 00:41:54.680 align:start position:0% in diagrams this was me for example 00:41:54.680 --> 00:41:56.470 align:start position:0% in diagrams this was me for example trying<00:41:54.920> to<00:41:55.280> understand<00:41:55.440> account<00:41:55.760> obstruction 00:41:56.470 --> 00:41:56.480 align:start position:0% trying to understand account obstruction 00:41:56.480 --> 00:41:58.109 align:start position:0% trying to understand account obstruction uh<00:41:56.599> in<00:41:56.720> the<00:41:56.880> past 00:41:58.109 --> 00:41:58.119 align:start position:0% uh in the past 00:41:58.119 --> 00:41:59.990 align:start position:0% uh in the past uh<00:41:58.280> and<00:41:58.400> I<00:41:58.560> ended<00:41:58.800> up<00:41:59.000> drawing<00:41:59.400> this<00:41:59.599> as<00:41:59.720> I<00:41:59.880> was 00:41:59.990 --> 00:42:00.000 align:start position:0% uh and I ended up drawing this as I was 00:42:00.000 --> 00:42:00.950 align:start position:0% uh and I ended up drawing this as I was going<00:42:00.200> through<00:42:00.359> the<00:42:00.520> code<00:42:00.720> through 00:42:00.950 --> 00:42:00.960 align:start position:0% going through the code through 00:42:00.960 --> 00:42:02.710 align:start position:0% going through the code through documentation<00:42:01.520> and<00:42:01.760> everything<00:42:02.240> I<00:42:02.319> was<00:42:02.560> just 00:42:02.710 --> 00:42:02.720 align:start position:0% documentation and everything I was just 00:42:02.720 --> 00:42:04.670 align:start position:0% documentation and everything I was just drawing<00:42:03.240> stuff<00:42:03.720> and<00:42:03.880> trying<00:42:04.119> to<00:42:04.480> understand 00:42:04.670 --> 00:42:04.680 align:start position:0% drawing stuff and trying to understand 00:42:04.680 --> 00:42:06.230 align:start position:0% drawing stuff and trying to understand what<00:42:04.800> I<00:42:04.920> was<00:42:05.160> seeing<00:42:05.440> in<00:42:05.520> this<00:42:05.680> case<00:42:05.839> it's<00:42:06.000> more 00:42:06.230 --> 00:42:06.240 align:start position:0% what I was seeing in this case it's more 00:42:06.240 --> 00:42:09.190 align:start position:0% what I was seeing in this case it's more kind<00:42:06.400> of<00:42:06.599> an<00:42:07.400> architectural<00:42:08.400> diagram<00:42:08.960> I<00:42:09.040> don't 00:42:09.190 --> 00:42:09.200 align:start position:0% kind of an architectural diagram I don't 00:42:09.200 --> 00:42:11.349 align:start position:0% kind of an architectural diagram I don't know<00:42:09.560> I<00:42:09.640> don't<00:42:09.800> even<00:42:10.040> think<00:42:10.240> about<00:42:10.440> it<00:42:10.920> I<00:42:11.040> just 00:42:11.349 --> 00:42:11.359 align:start position:0% know I don't even think about it I just 00:42:11.359 --> 00:42:13.430 align:start position:0% know I don't even think about it I just write<00:42:11.680> components<00:42:12.240> and<00:42:12.359> I<00:42:12.560> write<00:42:12.800> names<00:42:13.240> and 00:42:13.430 --> 00:42:13.440 align:start position:0% write components and I write names and 00:42:13.440 --> 00:42:15.030 align:start position:0% write components and I write names and and<00:42:13.560> try<00:42:13.800> to<00:42:13.880> see<00:42:14.119> which<00:42:14.319> are<00:42:14.640> which<00:42:14.760> are<00:42:14.920> the 00:42:15.030 --> 00:42:15.040 align:start position:0% and try to see which are which are the 00:42:15.040 --> 00:42:17.349 align:start position:0% and try to see which are which are the actors<00:42:15.400> how<00:42:15.520> are<00:42:15.640> the<00:42:16.160> relationships<00:42:17.160> and 00:42:17.349 --> 00:42:17.359 align:start position:0% actors how are the relationships and 00:42:17.359 --> 00:42:19.870 align:start position:0% actors how are the relationships and this<00:42:17.520> at<00:42:17.680> least<00:42:17.839> for<00:42:17.960> me<00:42:18.119> is<00:42:18.319> very<00:42:18.640> useful<00:42:19.640> uh 00:42:19.870 --> 00:42:19.880 align:start position:0% this at least for me is very useful uh 00:42:19.880 --> 00:42:22.390 align:start position:0% this at least for me is very useful uh perhaps<00:42:20.200> for<00:42:20.359> you<00:42:20.559> too<00:42:20.960> so<00:42:21.559> take<00:42:21.720> a<00:42:21.880> look<00:42:22.040> at<00:42:22.200> it 00:42:22.390 --> 00:42:22.400 align:start position:0% perhaps for you too so take a look at it 00:42:22.400 --> 00:42:25.030 align:start position:0% perhaps for you too so take a look at it and<00:42:22.640> perhaps<00:42:23.079> you<00:42:23.359> you<00:42:23.599> will<00:42:23.880> find<00:42:24.119> something 00:42:25.030 --> 00:42:25.040 align:start position:0% and perhaps you you will find something 00:42:25.040 --> 00:42:28.710 align:start position:0% and perhaps you you will find something valuable<00:42:26.040> then<00:42:26.400> I<00:42:26.559> do<00:42:27.200> some<00:42:27.359> other<00:42:27.599> things<00:42:28.520> uh 00:42:28.710 --> 00:42:28.720 align:start position:0% valuable then I do some other things uh 00:42:28.720 --> 00:42:30.750 align:start position:0% valuable then I do some other things uh in<00:42:28.839> terms<00:42:29.079> of<00:42:29.240> tyam<00:42:29.640> I<00:42:29.720> could<00:42:29.920> go<00:42:30.319> into<00:42:30.559> more 00:42:30.750 --> 00:42:30.760 align:start position:0% in terms of tyam I could go into more 00:42:30.760 --> 00:42:32.829 align:start position:0% in terms of tyam I could go into more detail<00:42:31.160> with<00:42:31.319> them<00:42:31.839> in<00:42:32.040> this<00:42:32.200> case<00:42:32.559> this<00:42:32.640> is 00:42:32.829 --> 00:42:32.839 align:start position:0% detail with them in this case this is 00:42:32.839 --> 00:42:34.829 align:start position:0% detail with them in this case this is was<00:42:33.160> me<00:42:33.480> just<00:42:33.800> thinking<00:42:34.119> about<00:42:34.440> the<00:42:34.640> them 00:42:34.829 --> 00:42:34.839 align:start position:0% was me just thinking about the them 00:42:34.839 --> 00:42:37.910 align:start position:0% was me just thinking about the them buner<00:42:35.319> defi<00:42:35.680> this<00:42:35.960> is<00:42:36.960> kind<00:42:37.119> of<00:42:37.280> a<00:42:37.599> set<00:42:37.760> of 00:42:37.910 --> 00:42:37.920 align:start position:0% buner defi this is kind of a set of 00:42:37.920 --> 00:42:40.349 align:start position:0% buner defi this is kind of a set of security<00:42:38.280> challenges<00:42:39.160> that<00:42:39.319> I<00:42:39.440> created<00:42:40.240> this 00:42:40.349 --> 00:42:40.359 align:start position:0% security challenges that I created this 00:42:40.359 --> 00:42:41.950 align:start position:0% security challenges that I created this is<00:42:40.480> one<00:42:40.640> of<00:42:40.760> the<00:42:40.839> solutions<00:42:41.240> for<00:42:41.400> one<00:42:41.520> of<00:42:41.680> them 00:42:41.950 --> 00:42:41.960 align:start position:0% is one of the solutions for one of them 00:42:41.960 --> 00:42:44.069 align:start position:0% is one of the solutions for one of them so<00:42:42.160> I<00:42:42.240> was<00:42:42.440> explaining<00:42:42.839> this<00:42:42.960> at<00:42:43.160> DSS<00:42:43.520> and<00:42:43.640> I<00:42:43.760> Ed 00:42:44.069 --> 00:42:44.079 align:start position:0% so I was explaining this at DSS and I Ed 00:42:44.079 --> 00:42:45.829 align:start position:0% so I was explaining this at DSS and I Ed a<00:42:44.240> diagram<00:42:44.640> to<00:42:44.800> explain<00:42:45.119> the<00:42:45.240> actual<00:42:45.520> solution 00:42:45.829 --> 00:42:45.839 align:start position:0% a diagram to explain the actual solution 00:42:45.839 --> 00:42:47.710 align:start position:0% a diagram to explain the actual solution so<00:42:46.000> you<00:42:46.079> will<00:42:46.240> see<00:42:46.440> me<00:42:46.640> like<00:42:47.000> doing<00:42:47.319> function 00:42:47.710 --> 00:42:47.720 align:start position:0% so you will see me like doing function 00:42:47.720 --> 00:42:49.470 align:start position:0% so you will see me like doing function calls<00:42:48.079> and<00:42:48.319> usually<00:42:48.640> drawing<00:42:49.119> where<00:42:49.240> are<00:42:49.400> the 00:42:49.470 --> 00:42:49.480 align:start position:0% calls and usually drawing where are the 00:42:49.480 --> 00:42:51.150 align:start position:0% calls and usually drawing where are the funds<00:42:49.880> and<00:42:50.079> where<00:42:50.280> we<00:42:50.400> should<00:42:50.559> be<00:42:50.720> putting<00:42:51.000> the 00:42:51.150 --> 00:42:51.160 align:start position:0% funds and where we should be putting the 00:42:51.160 --> 00:42:52.470 align:start position:0% funds and where we should be putting the funds<00:42:51.400> and<00:42:51.559> everything<00:42:51.880> this<00:42:52.079> just<00:42:52.240> one 00:42:52.470 --> 00:42:52.480 align:start position:0% funds and everything this just one 00:42:52.480 --> 00:42:54.630 align:start position:0% funds and everything this just one example<00:42:53.119> in<00:42:53.280> real<00:42:53.559> AIT<00:42:53.880> probably<00:42:54.240> I<00:42:54.359> will<00:42:54.520> be 00:42:54.630 --> 00:42:54.640 align:start position:0% example in real AIT probably I will be 00:42:54.640 --> 00:42:58.309 align:start position:0% example in real AIT probably I will be doing<00:42:55.319> uh<00:42:55.480> bigger<00:42:55.839> things<00:42:56.559> such<00:42:56.800> as 00:42:58.309 --> 00:42:58.319 align:start position:0% doing uh bigger things such as 00:42:58.319 --> 00:43:01.230 align:start position:0% doing uh bigger things such as this<00:42:58.880> h<00:42:59.119> i<00:42:59.280> I<00:42:59.359> do<00:42:59.559> go<00:43:00.119> in<00:43:00.280> depth<00:43:00.800> sometimes<00:43:01.000> so 00:43:01.230 --> 00:43:01.240 align:start position:0% this h i I do go in depth sometimes so 00:43:01.240 --> 00:43:04.829 align:start position:0% this h i I do go in depth sometimes so this<00:43:01.359> was<00:43:01.559> me<00:43:01.760> back<00:43:01.960> hunting<00:43:02.240> in<00:43:02.760> ler<00:43:03.760> um<00:43:04.240> so<00:43:04.680> in 00:43:04.829 --> 00:43:04.839 align:start position:0% this was me back hunting in ler um so in 00:43:04.839 --> 00:43:06.470 align:start position:0% this was me back hunting in ler um so in this<00:43:05.000> case<00:43:05.240> I<00:43:05.359> was<00:43:05.640> reviewing<00:43:06.079> main<00:43:06.319> at 00:43:06.470 --> 00:43:06.480 align:start position:0% this case I was reviewing main at 00:43:06.480 --> 00:43:08.150 align:start position:0% this case I was reviewing main at contract<00:43:06.880> so<00:43:07.040> and<00:43:07.119> I<00:43:07.240> need<00:43:07.520> kind<00:43:07.680> of<00:43:07.760> to<00:43:07.920> create 00:43:08.150 --> 00:43:08.160 align:start position:0% contract so and I need kind of to create 00:43:08.160 --> 00:43:10.430 align:start position:0% contract so and I need kind of to create a<00:43:08.280> mental<00:43:08.599> map<00:43:09.000> of<00:43:09.240> how<00:43:09.520> the<00:43:09.800> contracts<00:43:10.200> work 00:43:10.430 --> 00:43:10.440 align:start position:0% a mental map of how the contracts work 00:43:10.440 --> 00:43:12.030 align:start position:0% a mental map of how the contracts work and<00:43:10.599> how<00:43:10.720> they<00:43:10.880> interact<00:43:11.240> with<00:43:11.400> each<00:43:11.559> other 00:43:12.030 --> 00:43:12.040 align:start position:0% and how they interact with each other 00:43:12.040 --> 00:43:14.430 align:start position:0% and how they interact with each other and<00:43:12.200> where<00:43:12.319> are<00:43:12.480> the<00:43:12.720> addresses<00:43:13.720> and<00:43:13.920> then<00:43:14.160> I 00:43:14.430 --> 00:43:14.440 align:start position:0% and where are the addresses and then I 00:43:14.440 --> 00:43:18.349 align:start position:0% and where are the addresses and then I would<00:43:14.720> use<00:43:15.160> like<00:43:15.800> uh<00:43:16.720> yeah<00:43:17.000> which<00:43:17.160> are<00:43:17.359> the<00:43:17.599> EAS 00:43:18.349 --> 00:43:18.359 align:start position:0% would use like uh yeah which are the EAS 00:43:18.359 --> 00:43:20.549 align:start position:0% would use like uh yeah which are the EAS in<00:43:18.480> this<00:43:18.640> case<00:43:18.839> there's<00:43:19.000> a<00:43:19.119> multi<00:43:19.880> there<00:43:20.440> and 00:43:20.549 --> 00:43:20.559 align:start position:0% in this case there's a multi there and 00:43:20.559 --> 00:43:22.910 align:start position:0% in this case there's a multi there and then<00:43:20.720> I<00:43:20.839> would<00:43:21.240> try<00:43:21.440> to<00:43:21.960> understand<00:43:22.359> how<00:43:22.559> fees 00:43:22.910 --> 00:43:22.920 align:start position:0% then I would try to understand how fees 00:43:22.920 --> 00:43:24.829 align:start position:0% then I would try to understand how fees are<00:43:23.160> distributed<00:43:23.680> and<00:43:23.800> I<00:43:23.920> also<00:43:24.160> use<00:43:24.400> diagrams 00:43:24.829 --> 00:43:24.839 align:start position:0% are distributed and I also use diagrams 00:43:24.839 --> 00:43:26.829 align:start position:0% are distributed and I also use diagrams and<00:43:25.000> I<00:43:25.200> they<00:43:25.359> would<00:43:25.520> try<00:43:25.720> to<00:43:26.079> understand<00:43:26.720> uh 00:43:26.829 --> 00:43:26.839 align:start position:0% and I they would try to understand uh 00:43:26.839 --> 00:43:28.710 align:start position:0% and I they would try to understand uh story<00:43:27.119> St<00:43:27.359> layout<00:43:27.760> and<00:43:27.880> I<00:43:28.000> would<00:43:28.200> also<00:43:28.480> use 00:43:28.710 --> 00:43:28.720 align:start position:0% story St layout and I would also use 00:43:28.720 --> 00:43:31.150 align:start position:0% story St layout and I would also use diagrams<00:43:29.200> and<00:43:29.319> so<00:43:29.440> on<00:43:29.559> and<00:43:29.720> so<00:43:29.880> forth<00:43:30.200> right<00:43:30.359> so 00:43:31.150 --> 00:43:31.160 align:start position:0% diagrams and so on and so forth right so 00:43:31.160 --> 00:43:33.109 align:start position:0% diagrams and so on and so forth right so uh<00:43:31.280> you<00:43:31.440> might<00:43:31.640> say<00:43:31.920> that<00:43:32.359> I'm<00:43:32.599> spending<00:43:32.960> too 00:43:33.109 --> 00:43:33.119 align:start position:0% uh you might say that I'm spending too 00:43:33.119 --> 00:43:34.990 align:start position:0% uh you might say that I'm spending too much<00:43:33.400> time<00:43:33.880> drawing<00:43:34.319> stuff<00:43:34.520> and<00:43:34.640> not<00:43:34.800> looking 00:43:34.990 --> 00:43:35.000 align:start position:0% much time drawing stuff and not looking 00:43:35.000 --> 00:43:37.390 align:start position:0% much time drawing stuff and not looking at<00:43:35.200> code<00:43:35.640> but<00:43:35.800> this<00:43:35.920> is<00:43:36.040> just<00:43:36.240> the<00:43:36.359> way<00:43:36.559> I<00:43:36.760> think 00:43:37.390 --> 00:43:37.400 align:start position:0% at code but this is just the way I think 00:43:37.400 --> 00:43:39.990 align:start position:0% at code but this is just the way I think uh<00:43:37.559> often<00:43:37.880> times<00:43:38.559> and<00:43:38.720> I<00:43:38.839> find<00:43:39.079> this<00:43:39.280> valuable 00:43:39.990 --> 00:43:40.000 align:start position:0% uh often times and I find this valuable 00:43:40.000 --> 00:43:44.829 align:start position:0% uh often times and I find this valuable uh<00:43:40.160> in<00:43:40.760> many<00:43:41.760> cases<00:43:42.520> IED<00:43:43.400> up<00:43:43.720> finding<00:43:44.480> bags 00:43:44.829 --> 00:43:44.839 align:start position:0% uh in many cases IED up finding bags 00:43:44.839 --> 00:43:46.309 align:start position:0% uh in many cases IED up finding bags just<00:43:45.000> by<00:43:45.160> looking<00:43:45.400> at<00:43:45.559> diagrams<00:43:46.000> and<00:43:46.119> trying 00:43:46.309 --> 00:43:46.319 align:start position:0% just by looking at diagrams and trying 00:43:46.319 --> 00:43:48.510 align:start position:0% just by looking at diagrams and trying to<00:43:46.720> understand<00:43:46.920> how<00:43:47.160> actors<00:43:47.880> and<00:43:48.119> contract 00:43:48.510 --> 00:43:48.520 align:start position:0% to understand how actors and contract 00:43:48.520 --> 00:43:49.910 align:start position:0% to understand how actors and contract relate<00:43:48.720> to<00:43:48.839> each<00:43:48.960> other<00:43:49.200> and<00:43:49.440> sometimes<00:43:49.640> I<00:43:49.760> end 00:43:49.910 --> 00:43:49.920 align:start position:0% relate to each other and sometimes I end 00:43:49.920 --> 00:43:52.190 align:start position:0% relate to each other and sometimes I end up<00:43:50.119> finding<00:43:50.720> finding<00:43:51.079> kind<00:43:51.240> of<00:43:51.440> holes<00:43:51.839> in<00:43:52.000> my 00:43:52.190 --> 00:43:52.200 align:start position:0% up finding finding kind of holes in my 00:43:52.200 --> 00:43:53.950 align:start position:0% up finding finding kind of holes in my diagrams<00:43:52.720> so<00:43:52.880> I<00:43:53.000> realize<00:43:53.400> that<00:43:53.559> people<00:43:53.800> can 00:43:53.950 --> 00:43:53.960 align:start position:0% diagrams so I realize that people can 00:43:53.960 --> 00:43:56.270 align:start position:0% diagrams so I realize that people can call<00:43:54.440> things<00:43:54.720> that<00:43:55.200> shouldn't<00:43:55.520> be<00:43:55.800> able<00:43:56.040> to<00:43:56.160> be 00:43:56.270 --> 00:43:56.280 align:start position:0% call things that shouldn't be able to be 00:43:56.280 --> 00:44:00.390 align:start position:0% call things that shouldn't be able to be called 00:44:00.390 --> 00:44:00.400 align:start position:0% 00:44:00.400 --> 00:44:02.190 align:start position:0% so<00:44:00.720> yeah<00:44:00.920> and<00:44:01.359> well<00:44:01.520> you<00:44:01.599> can<00:44:01.720> use<00:44:01.960> whatever 00:44:02.190 --> 00:44:02.200 align:start position:0% so yeah and well you can use whatever 00:44:02.200 --> 00:44:03.870 align:start position:0% so yeah and well you can use whatever tool<00:44:02.520> right<00:44:02.640> so<00:44:02.760> you<00:44:02.839> can<00:44:03.000> use<00:44:03.160> online<00:44:03.480> tools 00:44:03.870 --> 00:44:03.880 align:start position:0% tool right so you can use online tools 00:44:03.880 --> 00:44:05.510 align:start position:0% tool right so you can use online tools your<00:44:04.160> whiteboards<00:44:04.640> in<00:44:04.760> your<00:44:04.880> rooms<00:44:05.240> in<00:44:05.359> your 00:44:05.510 --> 00:44:05.520 align:start position:0% your whiteboards in your rooms in your 00:44:05.520 --> 00:44:07.430 align:start position:0% your whiteboards in your rooms in your offices<00:44:06.040> whatever<00:44:06.359> that<00:44:06.520> you<00:44:06.920> that<00:44:07.040> you<00:44:07.160> feel 00:44:07.430 --> 00:44:07.440 align:start position:0% offices whatever that you that you feel 00:44:07.440 --> 00:44:10.829 align:start position:0% offices whatever that you that you feel like 00:44:10.829 --> 00:44:10.839 align:start position:0% 00:44:10.839 --> 00:44:13.710 align:start position:0% um<00:44:11.839> moving<00:44:12.119> out<00:44:12.319> with<00:44:12.440> the<00:44:12.599> comfort<00:44:12.920> zone<00:44:13.480> is 00:44:13.710 --> 00:44:13.720 align:start position:0% um moving out with the comfort zone is 00:44:13.720 --> 00:44:16.710 align:start position:0% um moving out with the comfort zone is another<00:44:14.200> good<00:44:14.440> thing<00:44:15.040> uh<00:44:15.200> that<00:44:15.359> we<00:44:15.440> should<00:44:15.720> be 00:44:16.710 --> 00:44:16.720 align:start position:0% another good thing uh that we should be 00:44:16.720 --> 00:44:18.630 align:start position:0% another good thing uh that we should be all<00:44:16.920> trying<00:44:17.200> to<00:44:17.319> do<00:44:17.480> in<00:44:17.599> many<00:44:17.839> aspects<00:44:18.160> of<00:44:18.359> life 00:44:18.630 --> 00:44:18.640 align:start position:0% all trying to do in many aspects of life 00:44:18.640 --> 00:44:20.309 align:start position:0% all trying to do in many aspects of life but<00:44:18.839> let's<00:44:19.040> just<00:44:19.240> keep<00:44:19.520> with<00:44:19.760> security 00:44:20.309 --> 00:44:20.319 align:start position:0% but let's just keep with security 00:44:20.319 --> 00:44:22.470 align:start position:0% but let's just keep with security research<00:44:21.319> uh<00:44:21.520> I<00:44:21.599> just<00:44:21.800> put<00:44:21.960> that<00:44:22.079> picture<00:44:22.359> of 00:44:22.470 --> 00:44:22.480 align:start position:0% research uh I just put that picture of 00:44:22.480 --> 00:44:23.790 align:start position:0% research uh I just put that picture of that<00:44:22.640> book<00:44:22.839> because<00:44:23.040> I<00:44:23.160> like<00:44:23.319> it<00:44:23.480> if<00:44:23.559> you<00:44:23.680> want 00:44:23.790 --> 00:44:23.800 align:start position:0% that book because I like it if you want 00:44:23.800 --> 00:44:26.470 align:start position:0% that book because I like it if you want to<00:44:23.920> read<00:44:24.119> it<00:44:24.280> and<00:44:24.440> give<00:44:24.559> it<00:44:24.640> a<00:44:24.920> try<00:44:25.920> uh<00:44:26.079> it<00:44:26.240> has<00:44:26.359> a 00:44:26.470 --> 00:44:26.480 align:start position:0% to read it and give it a try uh it has a 00:44:26.480 --> 00:44:29.950 align:start position:0% to read it and give it a try uh it has a chapter<00:44:26.760> about<00:44:27.400> the<00:44:27.520> comfort<00:44:27.839> zone<00:44:28.559> so<00:44:29.559> um<00:44:29.839> if 00:44:29.950 --> 00:44:29.960 align:start position:0% chapter about the comfort zone so um if 00:44:29.960 --> 00:44:33.470 align:start position:0% chapter about the comfort zone so um if you're<00:44:30.119> a<00:44:30.240> security<00:44:30.760> researcher<00:44:31.760> uh 00:44:33.470 --> 00:44:33.480 align:start position:0% you're a security researcher uh 00:44:33.480 --> 00:44:35.430 align:start position:0% you're a security researcher uh probably<00:44:34.480> sometimes<00:44:34.680> you<00:44:34.839> will<00:44:35.200> yeah<00:44:35.359> you 00:44:35.430 --> 00:44:35.440 align:start position:0% probably sometimes you will yeah you 00:44:35.440 --> 00:44:38.589 align:start position:0% probably sometimes you will yeah you will<00:44:35.599> find<00:44:35.839> yourself<00:44:36.800> uh<00:44:37.559> Growing<00:44:38.000> Experience 00:44:38.589 --> 00:44:38.599 align:start position:0% will find yourself uh Growing Experience 00:44:38.599 --> 00:44:42.109 align:start position:0% will find yourself uh Growing Experience in<00:44:38.800> certain<00:44:39.800> fields<00:44:40.359> in<00:44:40.559> certain<00:44:41.400> categories 00:44:42.109 --> 00:44:42.119 align:start position:0% in certain fields in certain categories 00:44:42.119 --> 00:44:44.990 align:start position:0% in certain fields in certain categories let's<00:44:42.319> call<00:44:42.559> them<00:44:42.839> of<00:44:43.599> vulnerabilities<00:44:44.599> or<00:44:44.839> or 00:44:44.990 --> 00:44:45.000 align:start position:0% let's call them of vulnerabilities or or 00:44:45.000 --> 00:44:45.990 align:start position:0% let's call them of vulnerabilities or or even 00:44:45.990 --> 00:44:46.000 align:start position:0% even 00:44:46.000 --> 00:44:48.829 align:start position:0% even protocols<00:44:47.000> uh<00:44:47.160> but<00:44:47.480> sometimes<00:44:47.680> it's<00:44:47.880> good<00:44:48.040> to 00:44:48.829 --> 00:44:48.839 align:start position:0% protocols uh but sometimes it's good to 00:44:48.839 --> 00:44:51.589 align:start position:0% protocols uh but sometimes it's good to do<00:44:49.040> something<00:44:49.359> else<00:44:50.160> earlier<00:44:50.800> this<00:44:50.920> year<00:44:51.440> I 00:44:51.589 --> 00:44:51.599 align:start position:0% do something else earlier this year I 00:44:51.599 --> 00:44:55.790 align:start position:0% do something else earlier this year I was<00:44:52.400> um<00:44:53.200> I<00:44:53.280> mean<00:44:53.480> I've<00:44:53.720> been<00:44:54.720> for<00:44:55.040> most<00:44:55.240> of<00:44:55.640> my 00:44:55.790 --> 00:44:55.800 align:start position:0% was um I mean I've been for most of my 00:44:55.800 --> 00:44:58.109 align:start position:0% was um I mean I've been for most of my career<00:44:56.119> I've<00:44:56.240> been<00:44:56.359> auditing<00:44:57.200> solid<00:44:57.640> smart 00:44:58.109 --> 00:44:58.119 align:start position:0% career I've been auditing solid smart 00:44:58.119 --> 00:45:00.710 align:start position:0% career I've been auditing solid smart contracts<00:44:59.119> uh<00:44:59.240> so<00:44:59.400> I<00:44:59.480> don't<00:44:59.680> have<00:45:00.200> that<00:45:00.400> much 00:45:00.710 --> 00:45:00.720 align:start position:0% contracts uh so I don't have that much 00:45:00.720 --> 00:45:02.910 align:start position:0% contracts uh so I don't have that much experienceing<00:45:01.720> notes<00:45:02.079> and<00:45:02.280> infrastructure 00:45:02.910 --> 00:45:02.920 align:start position:0% experienceing notes and infrastructure 00:45:02.920 --> 00:45:05.589 align:start position:0% experienceing notes and infrastructure for<00:45:03.079> example<00:45:03.760> but<00:45:04.319> earlier<00:45:04.720> this<00:45:04.880> year<00:45:05.480> uh 00:45:05.589 --> 00:45:05.599 align:start position:0% for example but earlier this year uh 00:45:05.599 --> 00:45:07.109 align:start position:0% for example but earlier this year uh there<00:45:05.720> was<00:45:05.880> a<00:45:06.079> contest<00:45:06.520> I<00:45:06.599> think<00:45:06.760> it<00:45:06.839> was<00:45:06.960> on 00:45:07.109 --> 00:45:07.119 align:start position:0% there was a contest I think it was on 00:45:07.119 --> 00:45:10.109 align:start position:0% there was a contest I think it was on Cantina<00:45:07.559> for<00:45:08.280> blast<00:45:09.280> and<00:45:09.440> I<00:45:09.599> had<00:45:09.720> the<00:45:09.839> chance 00:45:10.109 --> 00:45:10.119 align:start position:0% Cantina for blast and I had the chance 00:45:10.119 --> 00:45:12.270 align:start position:0% Cantina for blast and I had the chance to<00:45:10.400> either<00:45:10.880> go<00:45:11.079> for<00:45:11.240> the<00:45:11.359> smart<00:45:11.640> contracts<00:45:12.240> I 00:45:12.270 --> 00:45:12.280 align:start position:0% to either go for the smart contracts I 00:45:12.280 --> 00:45:14.069 align:start position:0% to either go for the smart contracts I mean<00:45:12.440> I<00:45:12.559> didn't<00:45:12.800> have<00:45:13.040> much<00:45:13.319> time<00:45:13.480> so<00:45:13.680> I<00:45:13.800> had<00:45:13.960> to 00:45:14.069 --> 00:45:14.079 align:start position:0% mean I didn't have much time so I had to 00:45:14.079 --> 00:45:16.349 align:start position:0% mean I didn't have much time so I had to choose<00:45:14.520> smart<00:45:14.800> contracts<00:45:15.520> or<00:45:15.720> go<00:45:15.880> for<00:45:16.040> the 00:45:16.349 --> 00:45:16.359 align:start position:0% choose smart contracts or go for the 00:45:16.359 --> 00:45:19.270 align:start position:0% choose smart contracts or go for the node<00:45:17.359> H<00:45:17.480> which<00:45:17.839> was<00:45:18.000> written<00:45:18.280> in<00:45:18.480> goang<00:45:19.040> it<00:45:19.160> was 00:45:19.270 --> 00:45:19.280 align:start position:0% node H which was written in goang it was 00:45:19.280 --> 00:45:21.150 align:start position:0% node H which was written in goang it was a<00:45:19.400> fork<00:45:19.640> of 00:45:21.150 --> 00:45:21.160 align:start position:0% a fork of 00:45:21.160 --> 00:45:24.270 align:start position:0% a fork of gu<00:45:22.160> and<00:45:22.280> I<00:45:22.480> decided<00:45:22.800> to<00:45:22.880> go<00:45:23.000> for<00:45:23.280> GU<00:45:23.880> H<00:45:23.960> for<00:45:24.119> the 00:45:24.270 --> 00:45:24.280 align:start position:0% gu and I decided to go for GU H for the 00:45:24.280 --> 00:45:26.430 align:start position:0% gu and I decided to go for GU H for the fork<00:45:25.280> uh<00:45:25.440> and<00:45:25.520> I<00:45:25.640> didn't<00:45:25.880> look<00:45:26.000> at<00:45:26.119> the<00:45:26.200> Smart 00:45:26.430 --> 00:45:26.440 align:start position:0% fork uh and I didn't look at the Smart 00:45:26.440 --> 00:45:29.510 align:start position:0% fork uh and I didn't look at the Smart contracts<00:45:26.839> I<00:45:27.079> missed<00:45:27.960> H<00:45:28.520> the<00:45:28.920> all<00:45:29.119> the<00:45:29.240> fun 00:45:29.510 --> 00:45:29.520 align:start position:0% contracts I missed H the all the fun 00:45:29.520 --> 00:45:31.230 align:start position:0% contracts I missed H the all the fun that<00:45:29.640> people<00:45:29.920> had<00:45:30.079> with<00:45:30.200> the<00:45:30.319> smart 00:45:31.230 --> 00:45:31.240 align:start position:0% that people had with the smart 00:45:31.240 --> 00:45:34.349 align:start position:0% that people had with the smart contracts<00:45:32.240> um<00:45:32.960> but<00:45:33.119> I<00:45:33.240> did<00:45:33.480> have<00:45:33.640> lots<00:45:33.839> of<00:45:34.000> fun 00:45:34.349 --> 00:45:34.359 align:start position:0% contracts um but I did have lots of fun 00:45:34.359 --> 00:45:38.349 align:start position:0% contracts um but I did have lots of fun reviewing<00:45:34.960> it<00:45:35.960> um<00:45:36.760> and<00:45:36.880> I<00:45:37.000> learned<00:45:37.359> a<00:45:37.520> lot<00:45:38.200> and 00:45:38.349 --> 00:45:38.359 align:start position:0% reviewing it um and I learned a lot and 00:45:38.359 --> 00:45:39.950 align:start position:0% reviewing it um and I learned a lot and I<00:45:38.480> ended<00:45:38.720> up<00:45:38.880> finding<00:45:39.200> issues<00:45:39.480> and<00:45:39.640> we<00:45:39.760> did 00:45:39.950 --> 00:45:39.960 align:start position:0% I ended up finding issues and we did 00:45:39.960 --> 00:45:41.230 align:start position:0% I ended up finding issues and we did quite 00:45:41.230 --> 00:45:41.240 align:start position:0% quite 00:45:41.240 --> 00:45:43.790 align:start position:0% quite well<00:45:42.240> but<00:45:42.400> I<00:45:42.520> wouldn't<00:45:43.079> have<00:45:43.359> I<00:45:43.440> wouldn't<00:45:43.680> have 00:45:43.790 --> 00:45:43.800 align:start position:0% well but I wouldn't have I wouldn't have 00:45:43.800 --> 00:45:46.630 align:start position:0% well but I wouldn't have I wouldn't have said<00:45:44.000> that<00:45:44.119> I<00:45:44.280> was<00:45:44.599> a<00:45:45.240> an<00:45:45.400> auditor<00:45:46.000> of<00:45:46.200> Goan 00:45:46.630 --> 00:45:46.640 align:start position:0% said that I was a an auditor of Goan 00:45:46.640 --> 00:45:49.710 align:start position:0% said that I was a an auditor of Goan code<00:45:47.440> uh<00:45:47.599> but<00:45:47.720> I<00:45:47.839> ended<00:45:48.040> up<00:45:48.160> finding<00:45:48.720> things 00:45:49.710 --> 00:45:49.720 align:start position:0% code uh but I ended up finding things 00:45:49.720 --> 00:45:52.470 align:start position:0% code uh but I ended up finding things and<00:45:50.119> that<00:45:50.240> only<00:45:50.440> happened<00:45:50.760> just<00:45:51.000> because<00:45:51.359> I<00:45:51.640> I 00:45:52.470 --> 00:45:52.480 align:start position:0% and that only happened just because I I 00:45:52.480 --> 00:45:54.630 align:start position:0% and that only happened just because I I moved<00:45:52.839> out<00:45:53.040> of<00:45:53.200> the<00:45:53.319> comfort<00:45:53.640> zone<00:45:54.400> and<00:45:54.520> I 00:45:54.630 --> 00:45:54.640 align:start position:0% moved out of the comfort zone and I 00:45:54.640 --> 00:45:58.190 align:start position:0% moved out of the comfort zone and I started<00:45:54.920> learning<00:45:55.319> go<00:45:55.640> I<00:45:55.760> had<00:45:55.960> never<00:45:56.520> read 00:45:58.190 --> 00:45:58.200 align:start position:0% started learning go I had never read 00:45:58.200 --> 00:45:59.750 align:start position:0% started learning go I had never read anything<00:45:58.720> about 00:45:59.750 --> 00:45:59.760 align:start position:0% anything about 00:45:59.760 --> 00:46:02.829 align:start position:0% anything about golang<00:46:00.760> um<00:46:01.520> so<00:46:01.640> I<00:46:01.760> learned<00:46:02.040> about<00:46:02.280> it<00:46:02.480> I<00:46:02.559> did<00:46:02.720> a 00:46:02.829 --> 00:46:02.839 align:start position:0% golang um so I learned about it I did a 00:46:02.839 --> 00:46:05.790 align:start position:0% golang um so I learned about it I did a few<00:46:03.000> courses<00:46:03.920> I<00:46:04.000> prepared<00:46:04.400> myself<00:46:05.280> I<00:46:05.359> went<00:46:05.599> in 00:46:05.790 --> 00:46:05.800 align:start position:0% few courses I prepared myself I went in 00:46:05.800 --> 00:46:08.230 align:start position:0% few courses I prepared myself I went in there<00:46:06.160> and<00:46:06.359> ended<00:46:06.559> up<00:46:06.720> finding<00:46:07.079> things<00:46:08.079> and 00:46:08.230 --> 00:46:08.240 align:start position:0% there and ended up finding things and 00:46:08.240 --> 00:46:10.630 align:start position:0% there and ended up finding things and even<00:46:08.520> if<00:46:08.640> you<00:46:08.720> don't<00:46:08.960> find<00:46:09.359> things<00:46:10.359> it<00:46:10.480> might 00:46:10.630 --> 00:46:10.640 align:start position:0% even if you don't find things it might 00:46:10.640 --> 00:46:12.510 align:start position:0% even if you don't find things it might be<00:46:10.760> the<00:46:10.920> case<00:46:11.119> that<00:46:11.200> you<00:46:11.359> end<00:46:11.520> up<00:46:11.720> learning 00:46:12.510 --> 00:46:12.520 align:start position:0% be the case that you end up learning 00:46:12.520 --> 00:46:15.109 align:start position:0% be the case that you end up learning which<00:46:12.640> is<00:46:12.760> always<00:46:13.520> cool<00:46:14.520> and<00:46:14.680> the<00:46:14.800> things<00:46:15.000> that 00:46:15.109 --> 00:46:15.119 align:start position:0% which is always cool and the things that 00:46:15.119 --> 00:46:17.589 align:start position:0% which is always cool and the things that you<00:46:15.240> learn<00:46:15.720> you<00:46:15.920> can<00:46:16.359> actually<00:46:16.720> use<00:46:17.200> in<00:46:17.440> the 00:46:17.589 --> 00:46:17.599 align:start position:0% you learn you can actually use in the 00:46:17.599 --> 00:46:19.950 align:start position:0% you learn you can actually use in the next<00:46:18.240> contest<00:46:18.680> that<00:46:18.800> you<00:46:18.960> do<00:46:19.400> and<00:46:19.559> little<00:46:19.800> by 00:46:19.950 --> 00:46:19.960 align:start position:0% next contest that you do and little by 00:46:19.960 --> 00:46:21.390 align:start position:0% next contest that you do and little by little<00:46:20.119> you<00:46:20.240> can<00:46:20.480> specialize<00:46:20.960> in<00:46:21.079> that<00:46:21.240> new 00:46:21.390 --> 00:46:21.400 align:start position:0% little you can specialize in that new 00:46:21.400 --> 00:46:23.069 align:start position:0% little you can specialize in that new technology<00:46:21.920> that<00:46:22.000> you're 00:46:23.069 --> 00:46:23.079 align:start position:0% technology that you're 00:46:23.079 --> 00:46:25.150 align:start position:0% technology that you're exploring<00:46:24.079> um<00:46:24.359> so<00:46:24.520> I'm<00:46:24.640> not<00:46:24.800> saying<00:46:25.079> you 00:46:25.150 --> 00:46:25.160 align:start position:0% exploring um so I'm not saying you 00:46:25.160 --> 00:46:27.430 align:start position:0% exploring um so I'm not saying you should<00:46:25.480> always<00:46:25.880> be<00:46:26.040> doing<00:46:26.400> this<00:46:27.040> otherwise 00:46:27.430 --> 00:46:27.440 align:start position:0% should always be doing this otherwise 00:46:27.440 --> 00:46:29.270 align:start position:0% should always be doing this otherwise it's<00:46:27.680> like<00:46:28.040> you're<00:46:28.240> not<00:46:28.559> specializing<00:46:29.119> in 00:46:29.270 --> 00:46:29.280 align:start position:0% it's like you're not specializing in 00:46:29.280 --> 00:46:32.630 align:start position:0% it's like you're not specializing in anything<00:46:30.200> but<00:46:30.480> every<00:46:30.680> now<00:46:30.839> and<00:46:31.319> then<00:46:32.319> see 00:46:32.630 --> 00:46:32.640 align:start position:0% anything but every now and then see 00:46:32.640 --> 00:46:34.710 align:start position:0% anything but every now and then see where<00:46:32.880> you<00:46:32.960> can<00:46:33.119> do<00:46:33.280> something<00:46:33.599> else<00:46:34.480> uh<00:46:34.599> if 00:46:34.710 --> 00:46:34.720 align:start position:0% where you can do something else uh if 00:46:34.720 --> 00:46:36.430 align:start position:0% where you can do something else uh if you're<00:46:34.880> are<00:46:35.040> a<00:46:35.240> smart<00:46:35.520> contract<00:46:35.800> auditor<00:46:36.160> see 00:46:36.430 --> 00:46:36.440 align:start position:0% you're are a smart contract auditor see 00:46:36.440 --> 00:46:39.109 align:start position:0% you're are a smart contract auditor see where<00:46:36.599> you<00:46:36.720> can<00:46:36.920> audit<00:46:37.200> a<00:46:37.359> node<00:46:38.359> or<00:46:38.599> the<00:46:39.000> the 00:46:39.109 --> 00:46:39.119 align:start position:0% where you can audit a node or the the 00:46:39.119 --> 00:46:42.589 align:start position:0% where you can audit a node or the the other<00:46:39.359> way<00:46:39.640> around<00:46:40.119> right<00:46:41.119> um<00:46:41.920> just<00:46:42.240> give<00:46:42.400> it<00:46:42.480> a 00:46:42.589 --> 00:46:42.599 align:start position:0% other way around right um just give it a 00:46:42.599 --> 00:46:44.630 align:start position:0% other way around right um just give it a try<00:46:43.119> and<00:46:43.240> see<00:46:43.640> and<00:46:43.800> then<00:46:43.920> you<00:46:44.000> can<00:46:44.160> tell<00:46:44.359> me 00:46:44.630 --> 00:46:44.640 align:start position:0% try and see and then you can tell me 00:46:44.640 --> 00:46:45.430 align:start position:0% try and see and then you can tell me about 00:46:45.430 --> 00:46:45.440 align:start position:0% about 00:46:45.440 --> 00:46:49.270 align:start position:0% about it<00:46:46.440> so<00:46:46.680> writing<00:46:47.400> I<00:46:48.359> told<00:46:48.599> you<00:46:48.760> that<00:46:48.920> I'm<00:46:49.119> a 00:46:49.270 --> 00:46:49.280 align:start position:0% it so writing I told you that I'm a 00:46:49.280 --> 00:46:51.710 align:start position:0% it so writing I told you that I'm a visual<00:46:49.559> thinker<00:46:50.040> but<00:46:50.200> I<00:46:50.359> also<00:46:50.920> like<00:46:51.119> writing<00:46:51.440> a 00:46:51.710 --> 00:46:51.720 align:start position:0% visual thinker but I also like writing a 00:46:51.720 --> 00:46:55.030 align:start position:0% visual thinker but I also like writing a lot<00:46:52.720> uh<00:46:53.160> two<00:46:53.440> articles<00:46:53.960> that<00:46:54.079> I<00:46:54.240> recommend 00:46:55.030 --> 00:46:55.040 align:start position:0% lot uh two articles that I recommend 00:46:55.040 --> 00:46:57.430 align:start position:0% lot uh two articles that I recommend essays<00:46:55.480> about<00:46:55.960> the<00:46:56.119> from<00:46:56.440> from<00:46:56.920> Paul<00:46:57.079> Graham 00:46:57.430 --> 00:46:57.440 align:start position:0% essays about the from from Paul Graham 00:46:57.440 --> 00:46:58.870 align:start position:0% essays about the from from Paul Graham that<00:46:57.559> I<00:46:57.720> recommend<00:46:58.040> reading<00:46:58.319> about<00:46:58.559> writing 00:46:58.870 --> 00:46:58.880 align:start position:0% that I recommend reading about writing 00:46:58.880 --> 00:47:00.990 align:start position:0% that I recommend reading about writing and<00:46:59.079> importance<00:46:59.480> of<00:46:59.680> writing<00:47:00.520> particularly 00:47:00.990 --> 00:47:01.000 align:start position:0% and importance of writing particularly 00:47:01.000 --> 00:47:04.710 align:start position:0% and importance of writing particularly for<00:47:01.559> thinking<00:47:02.559> um<00:47:03.520> I<00:47:03.640> do<00:47:04.079> very<00:47:04.240> much<00:47:04.440> agree 00:47:04.710 --> 00:47:04.720 align:start position:0% for thinking um I do very much agree 00:47:04.720 --> 00:47:08.390 align:start position:0% for thinking um I do very much agree with<00:47:05.119> idea<00:47:06.119> that<00:47:06.920> you<00:47:07.119> only<00:47:07.400> know<00:47:07.720> something 00:47:08.390 --> 00:47:08.400 align:start position:0% with idea that you only know something 00:47:08.400 --> 00:47:10.030 align:start position:0% with idea that you only know something if<00:47:08.559> you<00:47:08.680> can<00:47:08.920> write<00:47:09.200> about<00:47:09.400> it<00:47:09.640> and<00:47:09.760> you<00:47:09.839> can 00:47:10.030 --> 00:47:10.040 align:start position:0% if you can write about it and you can 00:47:10.040 --> 00:47:12.109 align:start position:0% if you can write about it and you can explain<00:47:10.440> that<00:47:10.839> to<00:47:11.040> something<00:47:11.680> to<00:47:11.839> someone 00:47:12.109 --> 00:47:12.119 align:start position:0% explain that to something to someone 00:47:12.119 --> 00:47:15.069 align:start position:0% explain that to something to someone else<00:47:12.359> by<00:47:12.520> writing<00:47:13.280> it<00:47:14.280> and<00:47:14.440> that's<00:47:14.599> the<00:47:14.760> only 00:47:15.069 --> 00:47:15.079 align:start position:0% else by writing it and that's the only 00:47:15.079 --> 00:47:17.390 align:start position:0% else by writing it and that's the only way<00:47:15.240> I'm<00:47:15.359> sure<00:47:15.920> that<00:47:16.040> I<00:47:16.440> understand<00:47:16.640> something 00:47:17.390 --> 00:47:17.400 align:start position:0% way I'm sure that I understand something 00:47:17.400 --> 00:47:20.990 align:start position:0% way I'm sure that I understand something probably<00:47:17.920> if<00:47:18.079> you<00:47:18.280> follow<00:47:18.680> me<00:47:19.680> online<00:47:20.480> H<00:47:20.640> you 00:47:20.990 --> 00:47:21.000 align:start position:0% probably if you follow me online H you 00:47:21.000 --> 00:47:22.910 align:start position:0% probably if you follow me online H you know<00:47:21.240> that<00:47:21.359> I<00:47:21.520> write<00:47:21.760> a<00:47:21.880> lot<00:47:22.160> and<00:47:22.319> I<00:47:22.559> publish 00:47:22.910 --> 00:47:22.920 align:start position:0% know that I write a lot and I publish 00:47:22.920 --> 00:47:25.510 align:start position:0% know that I write a lot and I publish articles<00:47:23.400> on<00:47:23.720> on<00:47:24.079> on<00:47:24.200> the<00:47:24.319> blog<00:47:24.960> of<00:47:25.079> the<00:47:25.200> red 00:47:25.510 --> 00:47:25.520 align:start position:0% articles on on on the blog of the red 00:47:25.520 --> 00:47:28.829 align:start position:0% articles on on on the blog of the red Guild<00:47:26.520> and<00:47:27.079> that's<00:47:27.240> the<00:47:27.359> way<00:47:27.520> I<00:47:27.680> think<00:47:28.599> and<00:47:28.720> I 00:47:28.829 --> 00:47:28.839 align:start position:0% Guild and that's the way I think and I 00:47:28.839 --> 00:47:31.430 align:start position:0% Guild and that's the way I think and I spend<00:47:29.079> a<00:47:29.160> lot<00:47:29.319> of<00:47:29.440> time<00:47:29.880> writing<00:47:30.880> uh<00:47:31.000> so<00:47:31.200> when<00:47:31.319> I 00:47:31.430 --> 00:47:31.440 align:start position:0% spend a lot of time writing uh so when I 00:47:31.440 --> 00:47:33.950 align:start position:0% spend a lot of time writing uh so when I do<00:47:31.640> AIT<00:47:31.920> I<00:47:32.040> explain<00:47:32.359> my<00:47:32.720> functions<00:47:33.319> in<00:47:33.480> writing 00:47:33.950 --> 00:47:33.960 align:start position:0% do AIT I explain my functions in writing 00:47:33.960 --> 00:47:36.349 align:start position:0% do AIT I explain my functions in writing I<00:47:34.079> take<00:47:34.280> down<00:47:34.480> notes<00:47:35.079> and<00:47:35.440> little<00:47:35.920> line<00:47:36.160> by 00:47:36.349 --> 00:47:36.359 align:start position:0% I take down notes and little line by 00:47:36.359 --> 00:47:37.750 align:start position:0% I take down notes and little line by line<00:47:36.559> and<00:47:36.720> explain<00:47:37.119> myself<00:47:37.520> what<00:47:37.640> the 00:47:37.750 --> 00:47:37.760 align:start position:0% line and explain myself what the 00:47:37.760 --> 00:47:40.510 align:start position:0% line and explain myself what the function<00:47:38.079> is<00:47:38.680> doing<00:47:39.680> and<00:47:39.839> in<00:47:40.000> that<00:47:40.160> way<00:47:40.280> I<00:47:40.400> can 00:47:40.510 --> 00:47:40.520 align:start position:0% function is doing and in that way I can 00:47:40.520 --> 00:47:43.549 align:start position:0% function is doing and in that way I can find<00:47:41.000> bags<00:47:42.000> uh<00:47:42.240> because<00:47:42.559> what<00:47:42.680> I<00:47:42.880> write 00:47:43.549 --> 00:47:43.559 align:start position:0% find bags uh because what I write 00:47:43.559 --> 00:47:45.190 align:start position:0% find bags uh because what I write sometimes<00:47:43.760> doesn't<00:47:44.000> make 00:47:45.190 --> 00:47:45.200 align:start position:0% sometimes doesn't make 00:47:45.200 --> 00:47:47.430 align:start position:0% sometimes doesn't make sense<00:47:46.200> also<00:47:46.480> when<00:47:46.599> we<00:47:46.680> are<00:47:46.800> exploring<00:47:47.160> a<00:47:47.280> new 00:47:47.430 --> 00:47:47.440 align:start position:0% sense also when we are exploring a new 00:47:47.440 --> 00:47:50.470 align:start position:0% sense also when we are exploring a new codebase<00:47:48.079> it's<00:47:48.280> the<00:47:48.440> case<00:47:48.800> that<00:47:49.480> uh<00:47:50.280> we 00:47:50.470 --> 00:47:50.480 align:start position:0% codebase it's the case that uh we 00:47:50.480 --> 00:47:53.910 align:start position:0% codebase it's the case that uh we explore<00:47:50.920> many<00:47:51.200> different<00:47:51.800> uh<00:47:51.920> lines<00:47:52.240> of 00:47:53.910 --> 00:47:53.920 align:start position:0% explore many different uh lines of 00:47:53.920 --> 00:47:55.990 align:start position:0% explore many different uh lines of thoughts<00:47:54.920> but<00:47:55.040> you<00:47:55.160> cannot<00:47:55.440> be<00:47:55.559> jamping 00:47:55.990 --> 00:47:56.000 align:start position:0% thoughts but you cannot be jamping 00:47:56.000 --> 00:47:59.349 align:start position:0% thoughts but you cannot be jamping around<00:47:57.160> uh<00:47:57.440> many<00:47:58.119> lines<00:47:58.359> of<00:47:58.520> thought<00:47:58.960> right<00:47:59.200> I 00:47:59.349 --> 00:47:59.359 align:start position:0% around uh many lines of thought right I 00:47:59.359 --> 00:48:01.349 align:start position:0% around uh many lines of thought right I usually<00:47:59.720> I'm<00:47:59.920> single<00:48:00.319> threaded<00:48:00.960> so<00:48:01.119> I<00:48:01.200> can 00:48:01.349 --> 00:48:01.359 align:start position:0% usually I'm single threaded so I can 00:48:01.359 --> 00:48:04.230 align:start position:0% usually I'm single threaded so I can only<00:48:01.559> do<00:48:01.720> one<00:48:01.920> thing<00:48:02.319> right<00:48:03.319> uh<00:48:03.400> so<00:48:03.559> I<00:48:03.680> write 00:48:04.230 --> 00:48:04.240 align:start position:0% only do one thing right uh so I write 00:48:04.240 --> 00:48:07.230 align:start position:0% only do one thing right uh so I write down<00:48:05.240> the<00:48:05.440> other<00:48:05.920> ideas<00:48:06.319> I<00:48:06.520> have<00:48:06.880> and<00:48:07.000> I<00:48:07.079> don't 00:48:07.230 --> 00:48:07.240 align:start position:0% down the other ideas I have and I don't 00:48:07.240 --> 00:48:08.829 align:start position:0% down the other ideas I have and I don't want<00:48:07.359> to<00:48:07.480> forget<00:48:07.800> them<00:48:07.960> so<00:48:08.079> I<00:48:08.240> write<00:48:08.520> I<00:48:08.640> write 00:48:08.829 --> 00:48:08.839 align:start position:0% want to forget them so I write I write 00:48:08.839 --> 00:48:11.510 align:start position:0% want to forget them so I write I write them<00:48:09.000> down<00:48:09.480> and<00:48:09.680> I<00:48:09.839> come<00:48:10.000> back<00:48:10.119> to<00:48:10.240> them<00:48:10.520> later 00:48:11.510 --> 00:48:11.520 align:start position:0% them down and I come back to them later 00:48:11.520 --> 00:48:14.030 align:start position:0% them down and I come back to them later in<00:48:11.640> the<00:48:11.760> next<00:48:11.960> day<00:48:12.160> or<00:48:12.760> whatever<00:48:13.760> and<00:48:13.880> to 00:48:14.030 --> 00:48:14.040 align:start position:0% in the next day or whatever and to 00:48:14.040 --> 00:48:17.470 align:start position:0% in the next day or whatever and to communicate<00:48:14.599> I<00:48:14.720> always<00:48:14.960> say 00:48:17.470 --> 00:48:17.480 align:start position:0% 00:48:17.480 --> 00:48:21.069 align:start position:0% that<00:48:18.480> secur<00:48:18.920> doing<00:48:19.240> security<00:48:19.680> for<00:48:19.880> me<00:48:20.079> is<00:48:20.640> uh 00:48:21.069 --> 00:48:21.079 align:start position:0% that secur doing security for me is uh 00:48:21.079 --> 00:48:24.630 align:start position:0% that secur doing security for me is uh particularly<00:48:21.559> for<00:48:22.040> Auditors<00:48:23.040> 50%<00:48:23.720> finding<00:48:24.119> BS 00:48:24.630 --> 00:48:24.640 align:start position:0% particularly for Auditors 50% finding BS 00:48:24.640 --> 00:48:27.790 align:start position:0% particularly for Auditors 50% finding BS and<00:48:24.839> 50%<00:48:25.480> communicating<00:48:26.079> backs<00:48:27.240> you<00:48:27.400> might<00:48:27.599> be 00:48:27.790 --> 00:48:27.800 align:start position:0% and 50% communicating backs you might be 00:48:27.800 --> 00:48:31.510 align:start position:0% and 50% communicating backs you might be the<00:48:28.160> best<00:48:29.160> finding<00:48:29.559> a<00:48:29.720> bag<00:48:30.640> but<00:48:30.760> if<00:48:30.880> you<00:48:31.040> cannot 00:48:31.510 --> 00:48:31.520 align:start position:0% the best finding a bag but if you cannot 00:48:31.520 --> 00:48:33.670 align:start position:0% the best finding a bag but if you cannot actually<00:48:32.520> write<00:48:32.800> a<00:48:32.960> good<00:48:33.160> report<00:48:33.480> and 00:48:33.670 --> 00:48:33.680 align:start position:0% actually write a good report and 00:48:33.680 --> 00:48:35.549 align:start position:0% actually write a good report and communicate<00:48:34.160> that<00:48:34.280> to<00:48:34.400> someone<00:48:34.880> else<00:48:35.319> and 00:48:35.549 --> 00:48:35.559 align:start position:0% communicate that to someone else and 00:48:35.559 --> 00:48:38.069 align:start position:0% communicate that to someone else and convince<00:48:36.480> that<00:48:36.680> someone<00:48:37.079> else<00:48:37.599> that<00:48:37.720> you're 00:48:38.069 --> 00:48:38.079 align:start position:0% convince that someone else that you're 00:48:38.079 --> 00:48:41.109 align:start position:0% convince that someone else that you're right<00:48:38.359> about<00:48:38.599> it<00:48:39.079> it<00:48:39.240> doesn't<00:48:39.520> make<00:48:39.680> any<00:48:40.119> sense 00:48:41.109 --> 00:48:41.119 align:start position:0% right about it it doesn't make any sense 00:48:41.119 --> 00:48:44.470 align:start position:0% right about it it doesn't make any sense so<00:48:41.960> uh<00:48:42.240> du<00:48:42.520> L<00:48:42.760> to<00:48:42.920> write<00:48:43.240> it's<00:48:43.599> very<00:48:43.920> very<00:48:44.240> very 00:48:44.470 --> 00:48:44.480 align:start position:0% so uh du L to write it's very very very 00:48:44.480 --> 00:48:47.670 align:start position:0% so uh du L to write it's very very very important<00:48:45.440> and<00:48:45.800> it's<00:48:46.040> also<00:48:46.480> somewhat<00:48:46.880> fun<00:48:47.559> uh 00:48:47.670 --> 00:48:47.680 align:start position:0% important and it's also somewhat fun uh 00:48:47.680 --> 00:48:49.950 align:start position:0% important and it's also somewhat fun uh so<00:48:47.920> I<00:48:48.040> do<00:48:48.200> recommend 00:48:49.950 --> 00:48:49.960 align:start position:0% so I do recommend 00:48:49.960 --> 00:48:53.150 align:start position:0% so I do recommend that<00:48:50.960> a<00:48:51.119> particular<00:48:51.599> strategy<00:48:52.000> to<00:48:52.119> find<00:48:52.359> bugs 00:48:53.150 --> 00:48:53.160 align:start position:0% that a particular strategy to find bugs 00:48:53.160 --> 00:48:55.349 align:start position:0% that a particular strategy to find bugs uh<00:48:53.400> It's<00:48:53.680> just<00:48:54.440> sometimes<00:48:54.680> going<00:48:54.880> for<00:48:55.119> what's 00:48:55.349 --> 00:48:55.359 align:start position:0% uh It's just sometimes going for what's 00:48:55.359 --> 00:48:57.670 align:start position:0% uh It's just sometimes going for what's not<00:48:55.559> tested 00:48:57.670 --> 00:48:57.680 align:start position:0% not tested 00:48:57.680 --> 00:49:00.150 align:start position:0% not tested um<00:48:58.280> what<00:48:58.400> I<00:48:58.720> sometimes<00:48:58.920> do<00:48:59.280> is<00:48:59.440> essentially 00:49:00.150 --> 00:49:00.160 align:start position:0% um what I sometimes do is essentially 00:49:00.160 --> 00:49:03.630 align:start position:0% um what I sometimes do is essentially jump<00:49:00.440> into<00:49:00.599> a<00:49:00.760> test<00:49:01.240> Suite<00:49:02.240> see<00:49:02.599> which<00:49:02.760> are<00:49:03.440> the 00:49:03.630 --> 00:49:03.640 align:start position:0% jump into a test Suite see which are the 00:49:03.640 --> 00:49:05.390 align:start position:0% jump into a test Suite see which are the P<00:49:04.040> functions<00:49:04.400> in<00:49:04.520> the<00:49:04.760> contracts<00:49:05.119> that<00:49:05.240> are 00:49:05.390 --> 00:49:05.400 align:start position:0% P functions in the contracts that are 00:49:05.400 --> 00:49:08.549 align:start position:0% P functions in the contracts that are never<00:49:05.680> called<00:49:06.680> and<00:49:06.920> start<00:49:07.119> exploring<00:49:07.599> there 00:49:08.549 --> 00:49:08.559 align:start position:0% never called and start exploring there 00:49:08.559 --> 00:49:10.630 align:start position:0% never called and start exploring there it's<00:49:08.760> usually<00:49:09.119> the<00:49:09.280> case<00:49:10.160> that<00:49:10.319> whenever 00:49:10.630 --> 00:49:10.640 align:start position:0% it's usually the case that whenever 00:49:10.640 --> 00:49:12.150 align:start position:0% it's usually the case that whenever there's<00:49:10.839> a<00:49:11.000> public<00:49:11.280> function<00:49:11.640> that<00:49:11.760> is<00:49:11.880> never 00:49:12.150 --> 00:49:12.160 align:start position:0% there's a public function that is never 00:49:12.160 --> 00:49:14.390 align:start position:0% there's a public function that is never called<00:49:12.440> from<00:49:12.559> the<00:49:12.760> test<00:49:13.119> it<00:49:13.280> could<00:49:13.520> be<00:49:13.920> yeah 00:49:14.390 --> 00:49:14.400 align:start position:0% called from the test it could be yeah 00:49:14.400 --> 00:49:16.950 align:start position:0% called from the test it could be yeah it's<00:49:15.079> sometimes<00:49:15.280> the<00:49:15.480> case<00:49:15.720> that<00:49:16.599> there<00:49:16.760> might 00:49:16.950 --> 00:49:16.960 align:start position:0% it's sometimes the case that there might 00:49:16.960 --> 00:49:18.950 align:start position:0% it's sometimes the case that there might be<00:49:17.119> something<00:49:17.559> at<00:49:17.720> least<00:49:18.240> at<00:49:18.400> least<00:49:18.720> to 00:49:18.950 --> 00:49:18.960 align:start position:0% be something at least at least to 00:49:18.960 --> 00:49:20.430 align:start position:0% be something at least at least to explore<00:49:19.400> in<00:49:19.559> that 00:49:20.430 --> 00:49:20.440 align:start position:0% explore in that 00:49:20.440 --> 00:49:23.309 align:start position:0% explore in that sense<00:49:21.440> then<00:49:21.599> what<00:49:21.720> I<00:49:21.839> would<00:49:22.000> do<00:49:22.799> is<00:49:22.960> that<00:49:23.200> I 00:49:23.309 --> 00:49:23.319 align:start position:0% sense then what I would do is that I 00:49:23.319 --> 00:49:25.789 align:start position:0% sense then what I would do is that I take<00:49:23.520> advantage<00:49:23.960> of<00:49:24.119> the<00:49:24.280> ex<00:49:24.760> existent<00:49:25.200> tests 00:49:25.789 --> 00:49:25.799 align:start position:0% take advantage of the ex existent tests 00:49:25.799 --> 00:49:28.589 align:start position:0% take advantage of the ex existent tests I<00:49:25.920> modify<00:49:26.359> them<00:49:26.520> I<00:49:26.760> hook<00:49:26.960> into<00:49:27.280> them<00:49:27.880> I<00:49:28.040> rework 00:49:28.589 --> 00:49:28.599 align:start position:0% I modify them I hook into them I rework 00:49:28.599 --> 00:49:31.470 align:start position:0% I modify them I hook into them I rework them<00:49:29.200> I<00:49:29.920> bring<00:49:30.240> them<00:49:30.440> around<00:49:30.760> I<00:49:30.920> I<00:49:31.000> do<00:49:31.200> whatever 00:49:31.470 --> 00:49:31.480 align:start position:0% them I bring them around I I do whatever 00:49:31.480 --> 00:49:33.910 align:start position:0% them I bring them around I I do whatever I<00:49:31.599> want<00:49:31.799> with<00:49:31.920> the<00:49:32.160> tests<00:49:33.160> uh<00:49:33.359> but<00:49:33.640> just 00:49:33.910 --> 00:49:33.920 align:start position:0% I want with the tests uh but just 00:49:33.920 --> 00:49:35.589 align:start position:0% I want with the tests uh but just because<00:49:34.119> I<00:49:34.200> don't<00:49:34.359> want<00:49:34.480> to<00:49:34.680> be<00:49:34.920> building<00:49:35.319> test 00:49:35.589 --> 00:49:35.599 align:start position:0% because I don't want to be building test 00:49:35.599 --> 00:49:37.589 align:start position:0% because I don't want to be building test from<00:49:35.799> scratch<00:49:36.280> right<00:49:36.400> so<00:49:36.520> I<00:49:36.599> want<00:49:36.760> to<00:49:36.880> reuse 00:49:37.589 --> 00:49:37.599 align:start position:0% from scratch right so I want to reuse 00:49:37.599 --> 00:49:40.270 align:start position:0% from scratch right so I want to reuse the<00:49:37.720> existing<00:49:38.480> test<00:49:38.680> Suite<00:49:39.400> that's<00:49:39.640> what<00:49:40.079> what 00:49:40.270 --> 00:49:40.280 align:start position:0% the existing test Suite that's what what 00:49:40.280 --> 00:49:42.230 align:start position:0% the existing test Suite that's what what that's<00:49:40.520> why<00:49:40.799> it's<00:49:40.960> very<00:49:41.160> important<00:49:41.480> to<00:49:41.680> always 00:49:42.230 --> 00:49:42.240 align:start position:0% that's why it's very important to always 00:49:42.240 --> 00:49:44.150 align:start position:0% that's why it's very important to always H<00:49:42.359> take<00:49:42.520> a<00:49:42.680> look<00:49:42.839> at<00:49:43.000> them<00:49:43.319> try<00:49:43.559> to<00:49:43.720> use<00:49:43.920> them 00:49:44.150 --> 00:49:44.160 align:start position:0% H take a look at them try to use them 00:49:44.160 --> 00:49:49.270 align:start position:0% H take a look at them try to use them run<00:49:44.440> them<00:49:44.640> and<00:49:44.799> see<00:49:45.000> if<00:49:45.240> if<00:49:45.400> it<00:49:45.559> helps 00:49:49.270 --> 00:49:49.280 align:start position:0% 00:49:49.280 --> 00:49:51.950 align:start position:0% you<00:49:50.280> we<00:49:50.440> could<00:49:51.079> talk<00:49:51.280> a<00:49:51.400> little<00:49:51.559> bit<00:49:51.720> more 00:49:51.950 --> 00:49:51.960 align:start position:0% you we could talk a little bit more 00:49:51.960 --> 00:49:53.990 align:start position:0% you we could talk a little bit more about<00:49:52.240> this<00:49:52.760> uh<00:49:52.920> I<00:49:53.000> don't<00:49:53.160> want<00:49:53.319> to<00:49:53.640> extend 00:49:53.990 --> 00:49:54.000 align:start position:0% about this uh I don't want to extend 00:49:54.000 --> 00:49:56.670 align:start position:0% about this uh I don't want to extend myself<00:49:54.880> uh<00:49:55.319> I<00:49:55.440> do<00:49:55.599> have<00:49:55.760> some<00:49:55.960> minutes<00:49:56.280> left 00:49:56.670 --> 00:49:56.680 align:start position:0% myself uh I do have some minutes left 00:49:56.680 --> 00:49:58.789 align:start position:0% myself uh I do have some minutes left according<00:49:56.960> to<00:49:57.119> Rajiv<00:49:57.559> he<00:49:57.680> told<00:49:57.880> me<00:49:58.079> I<00:49:58.240> had<00:49:58.400> some 00:49:58.789 --> 00:49:58.799 align:start position:0% according to Rajiv he told me I had some 00:49:58.799 --> 00:50:04.430 align:start position:0% according to Rajiv he told me I had some extra<00:49:59.520> time<00:50:00.520> um<00:50:01.440> so<00:50:01.720> for<00:50:02.359> me<00:50:03.359> oing<00:50:03.880> is<00:50:04.040> not<00:50:04.240> back 00:50:04.430 --> 00:50:04.440 align:start position:0% extra time um so for me oing is not back 00:50:04.440 --> 00:50:06.630 align:start position:0% extra time um so for me oing is not back hunting<00:50:04.920> but<00:50:05.160> hunting<00:50:05.480> is<00:50:05.640> not<00:50:05.880> contest<00:50:06.440> and 00:50:06.630 --> 00:50:06.640 align:start position:0% hunting but hunting is not contest and 00:50:06.640 --> 00:50:09.670 align:start position:0% hunting but hunting is not contest and contest<00:50:07.079> are<00:50:07.240> not<00:50:07.799> aiting<00:50:08.799> the<00:50:09.000> skills<00:50:09.520> the 00:50:09.670 --> 00:50:09.680 align:start position:0% contest are not aiting the skills the 00:50:09.680 --> 00:50:12.390 align:start position:0% contest are not aiting the skills the mindset<00:50:10.319> the<00:50:10.480> experience<00:50:11.119> the<00:50:11.400> intuitions 00:50:12.390 --> 00:50:12.400 align:start position:0% mindset the experience the intuitions 00:50:12.400 --> 00:50:14.670 align:start position:0% mindset the experience the intuitions the<00:50:12.559> way<00:50:12.839> that<00:50:12.960> you<00:50:13.160> play<00:50:13.680> these<00:50:13.960> games<00:50:14.440> is 00:50:14.670 --> 00:50:14.680 align:start position:0% the way that you play these games is 00:50:14.680 --> 00:50:17.390 align:start position:0% the way that you play these games is totally<00:50:15.559> different<00:50:16.559> and<00:50:16.720> you<00:50:16.880> might<00:50:17.079> be<00:50:17.240> the 00:50:17.390 --> 00:50:17.400 align:start position:0% totally different and you might be the 00:50:17.400 --> 00:50:20.030 align:start position:0% totally different and you might be the best<00:50:17.559> auditor<00:50:18.000> out<00:50:18.240> there<00:50:18.720> I<00:50:19.040> I<00:50:19.599> consider 00:50:20.030 --> 00:50:20.040 align:start position:0% best auditor out there I I consider 00:50:20.040 --> 00:50:22.630 align:start position:0% best auditor out there I I consider myself<00:50:20.359> a<00:50:20.520> good<00:50:20.680> Auditor<00:50:21.079> in<00:50:21.200> the<00:50:21.480> past<00:50:22.480> and 00:50:22.630 --> 00:50:22.640 align:start position:0% myself a good Auditor in the past and 00:50:22.640 --> 00:50:25.150 align:start position:0% myself a good Auditor in the past and then<00:50:22.760> I<00:50:22.839> moved<00:50:23.119> to<00:50:23.760> contest<00:50:24.359> and<00:50:24.520> I<00:50:24.680> realized 00:50:25.150 --> 00:50:25.160 align:start position:0% then I moved to contest and I realized 00:50:25.160 --> 00:50:26.829 align:start position:0% then I moved to contest and I realized that<00:50:25.359> people<00:50:25.640> play<00:50:25.960> a<00:50:26.160> different<00:50:26.400> kind<00:50:26.520> of 00:50:26.829 --> 00:50:26.839 align:start position:0% that people play a different kind of 00:50:26.839 --> 00:50:29.829 align:start position:0% that people play a different kind of gaming<00:50:27.680> there<00:50:28.680> uh<00:50:28.839> and<00:50:29.000> perhaps<00:50:29.280> I<00:50:29.400> wasn't<00:50:29.680> the 00:50:29.829 --> 00:50:29.839 align:start position:0% gaming there uh and perhaps I wasn't the 00:50:29.839 --> 00:50:31.910 align:start position:0% gaming there uh and perhaps I wasn't the best<00:50:30.280> doing<00:50:30.680> that<00:50:30.960> and<00:50:31.160> about<00:50:31.319> country<00:50:31.599> is<00:50:31.760> the 00:50:31.910 --> 00:50:31.920 align:start position:0% best doing that and about country is the 00:50:31.920 --> 00:50:34.470 align:start position:0% best doing that and about country is the same<00:50:32.280> right<00:50:33.200> uh<00:50:33.359> in<00:50:33.520> aiting<00:50:34.040> you<00:50:34.119> will<00:50:34.280> find 00:50:34.470 --> 00:50:34.480 align:start position:0% same right uh in aiting you will find 00:50:34.480 --> 00:50:36.309 align:start position:0% same right uh in aiting you will find yourself<00:50:34.839> doing<00:50:35.160> client<00:50:35.520> facing<00:50:35.920> work<00:50:36.240> you 00:50:36.309 --> 00:50:36.319 align:start position:0% yourself doing client facing work you 00:50:36.319 --> 00:50:38.190 align:start position:0% yourself doing client facing work you will<00:50:36.480> find<00:50:36.680> yourself<00:50:37.079> going<00:50:37.400> deep<00:50:37.720> and<00:50:37.880> going 00:50:38.190 --> 00:50:38.200 align:start position:0% will find yourself going deep and going 00:50:38.200 --> 00:50:40.589 align:start position:0% will find yourself going deep and going wide<00:50:38.520> and<00:50:38.799> going<00:50:39.319> very<00:50:39.520> detailed<00:50:40.000> and<00:50:40.160> writing 00:50:40.589 --> 00:50:40.599 align:start position:0% wide and going very detailed and writing 00:50:40.599 --> 00:50:43.270 align:start position:0% wide and going very detailed and writing very<00:50:40.799> detailed<00:50:41.240> reports<00:50:42.119> and<00:50:42.359> talking<00:50:42.920> a<00:50:43.079> lot 00:50:43.270 --> 00:50:43.280 align:start position:0% very detailed reports and talking a lot 00:50:43.280 --> 00:50:45.630 align:start position:0% very detailed reports and talking a lot with<00:50:43.480> developers<00:50:44.359> uh<00:50:44.480> not<00:50:44.680> necessarily 00:50:45.630 --> 00:50:45.640 align:start position:0% with developers uh not necessarily 00:50:45.640 --> 00:50:49.030 align:start position:0% with developers uh not necessarily discussing<00:50:46.280> but<00:50:46.520> just<00:50:47.160> thinking<00:50:48.160> along<00:50:48.760> along 00:50:49.030 --> 00:50:49.040 align:start position:0% discussing but just thinking along along 00:50:49.040 --> 00:50:51.270 align:start position:0% discussing but just thinking along along with<00:50:49.280> them<00:50:49.520> just<00:50:49.799> to<00:50:50.160> to<00:50:50.359> find<00:50:50.720> more 00:50:51.270 --> 00:50:51.280 align:start position:0% with them just to to find more 00:50:51.280 --> 00:50:53.430 align:start position:0% with them just to to find more vulnerabilities<00:50:52.040> and<00:50:52.280> backs<00:50:52.920> and<00:50:53.040> you<00:50:53.200> have 00:50:53.430 --> 00:50:53.440 align:start position:0% vulnerabilities and backs and you have 00:50:53.440 --> 00:50:55.430 align:start position:0% vulnerabilities and backs and you have access<00:50:53.799> to<00:50:54.119> to<00:50:54.280> these<00:50:54.520> developers<00:50:55.119> often 00:50:55.430 --> 00:50:55.440 align:start position:0% access to to these developers often 00:50:55.440 --> 00:50:57.990 align:start position:0% access to to these developers often times 00:50:57.990 --> 00:50:58.000 align:start position:0% times 00:50:58.000 --> 00:50:59.870 align:start position:0% times you<00:50:58.160> also<00:50:58.359> feel<00:50:58.559> the<00:50:58.760> responsibility<00:50:59.760> when 00:50:59.870 --> 00:50:59.880 align:start position:0% you also feel the responsibility when 00:50:59.880 --> 00:51:01.589 align:start position:0% you also feel the responsibility when you're<00:51:00.319> an<00:51:00.520> auditor<00:51:00.960> particularly<00:51:01.359> if<00:51:01.440> you're 00:51:01.589 --> 00:51:01.599 align:start position:0% you're an auditor particularly if you're 00:51:01.599 --> 00:51:03.589 align:start position:0% you're an auditor particularly if you're leading<00:51:01.960> audit<00:51:02.319> you<00:51:02.400> feel<00:51:02.760> responsible<00:51:03.359> for 00:51:03.589 --> 00:51:03.599 align:start position:0% leading audit you feel responsible for 00:51:03.599 --> 00:51:07.109 align:start position:0% leading audit you feel responsible for what<00:51:03.720> you're<00:51:04.200> doing<00:51:05.200> which<00:51:05.400> might<00:51:05.599> not<00:51:05.839> be<00:51:06.720> H 00:51:07.109 --> 00:51:07.119 align:start position:0% what you're doing which might not be H 00:51:07.119 --> 00:51:08.430 align:start position:0% what you're doing which might not be H sometimes<00:51:07.319> the<00:51:07.480> case<00:51:07.680> if<00:51:07.799> you're<00:51:08.040> just<00:51:08.200> back 00:51:08.430 --> 00:51:08.440 align:start position:0% sometimes the case if you're just back 00:51:08.440 --> 00:51:10.030 align:start position:0% sometimes the case if you're just back hunting<00:51:08.799> right<00:51:09.040> back<00:51:09.200> hunting<00:51:09.480> you're<00:51:09.760> just 00:51:10.030 --> 00:51:10.040 align:start position:0% hunting right back hunting you're just 00:51:10.040 --> 00:51:14.950 align:start position:0% hunting right back hunting you're just perhaps<00:51:10.440> a<00:51:10.559> Sol<00:51:10.920> back<00:51:11.119> Hunter<00:51:12.119> you're<00:51:13.200> uh<00:51:14.200> um 00:51:14.950 --> 00:51:14.960 align:start position:0% perhaps a Sol back Hunter you're uh um 00:51:14.960 --> 00:51:17.109 align:start position:0% perhaps a Sol back Hunter you're uh um shitless<00:51:15.799> in<00:51:16.000> your<00:51:16.200> home<00:51:16.599> just<00:51:16.839> doing 00:51:17.109 --> 00:51:17.119 align:start position:0% shitless in your home just doing 00:51:17.119 --> 00:51:19.390 align:start position:0% shitless in your home just doing whatever<00:51:17.400> you<00:51:17.520> want<00:51:18.240> and<00:51:18.720> looking<00:51:19.000> at<00:51:19.160> some 00:51:19.390 --> 00:51:19.400 align:start position:0% whatever you want and looking at some 00:51:19.400 --> 00:51:21.589 align:start position:0% whatever you want and looking at some code<00:51:20.079> sometimes<00:51:20.240> you<00:51:20.400> look<00:51:20.599> it<00:51:20.799> more<00:51:21.079> you<00:51:21.240> look 00:51:21.589 --> 00:51:21.599 align:start position:0% code sometimes you look it more you look 00:51:21.599 --> 00:51:23.990 align:start position:0% code sometimes you look it more you look less<00:51:22.520> you<00:51:22.760> you<00:51:22.839> might<00:51:23.040> not<00:51:23.200> feel<00:51:23.760> as 00:51:23.990 --> 00:51:24.000 align:start position:0% less you you might not feel as 00:51:24.000 --> 00:51:27.510 align:start position:0% less you you might not feel as responsible<00:51:24.640> as<00:51:24.839> other<00:51:25.440> people<00:51:26.440> uh<00:51:26.760> um<00:51:27.400> you 00:51:27.510 --> 00:51:27.520 align:start position:0% responsible as other people uh um you 00:51:27.520 --> 00:51:29.589 align:start position:0% responsible as other people uh um you can<00:51:27.720> go<00:51:27.880> as<00:51:28.000> deep<00:51:28.200> as<00:51:28.359> you<00:51:28.559> as<00:51:28.680> you<00:51:28.799> want<00:51:29.440> you 00:51:29.589 --> 00:51:29.599 align:start position:0% can go as deep as you as you want you 00:51:29.599 --> 00:51:31.789 align:start position:0% can go as deep as you as you want you can<00:51:29.920> just<00:51:30.319> get<00:51:30.559> one<00:51:30.799> win<00:51:31.119> and<00:51:31.280> you're<00:51:31.480> done 00:51:31.789 --> 00:51:31.799 align:start position:0% can just get one win and you're done 00:51:31.799 --> 00:51:34.270 align:start position:0% can just get one win and you're done Auditors<00:51:32.359> might<00:51:32.520> need<00:51:32.640> to<00:51:32.799> find<00:51:33.280> everything 00:51:34.270 --> 00:51:34.280 align:start position:0% Auditors might need to find everything 00:51:34.280 --> 00:51:35.950 align:start position:0% Auditors might need to find everything it<00:51:34.559> it's<00:51:34.680> a<00:51:34.799> very<00:51:35.000> different<00:51:35.280> mindset<00:51:35.640> and<00:51:35.760> in 00:51:35.950 --> 00:51:35.960 align:start position:0% it it's a very different mindset and in 00:51:35.960 --> 00:51:37.870 align:start position:0% it it's a very different mindset and in contest<00:51:36.559> well<00:51:36.760> contest<00:51:37.160> for<00:51:37.319> me<00:51:37.440> are<00:51:37.640> just 00:51:37.870 --> 00:51:37.880 align:start position:0% contest well contest for me are just 00:51:37.880 --> 00:51:41.109 align:start position:0% contest well contest for me are just like<00:51:38.960> Madness 00:51:41.109 --> 00:51:41.119 align:start position:0% like Madness 00:51:41.119 --> 00:51:44.190 align:start position:0% like Madness um<00:51:42.119> some<00:51:42.400> people<00:51:42.720> find<00:51:42.920> it<00:51:43.040> fun<00:51:43.640> uh<00:51:44.000> sometimes 00:51:44.190 --> 00:51:44.200 align:start position:0% um some people find it fun uh sometimes 00:51:44.200 --> 00:51:46.710 align:start position:0% um some people find it fun uh sometimes I<00:51:44.359> do<00:51:45.000> but<00:51:45.440> uh<00:51:45.799> again<00:51:46.040> it's<00:51:46.200> a<00:51:46.319> different<00:51:46.559> kind 00:51:46.710 --> 00:51:46.720 align:start position:0% I do but uh again it's a different kind 00:51:46.720 --> 00:51:50.950 align:start position:0% I do but uh again it's a different kind of<00:51:46.880> game<00:51:47.520> you<00:51:47.640> should<00:51:48.280> be<00:51:49.280> finding<00:51:50.200> sometimes 00:51:50.950 --> 00:51:50.960 align:start position:0% of game you should be finding sometimes 00:51:50.960 --> 00:51:53.630 align:start position:0% of game you should be finding sometimes specific<00:51:51.440> bags<00:51:51.760> that<00:51:51.880> are<00:51:52.000> more<00:51:52.480> unique<00:51:53.480> uh 00:51:53.630 --> 00:51:53.640 align:start position:0% specific bags that are more unique uh 00:51:53.640 --> 00:51:55.069 align:start position:0% specific bags that are more unique uh you<00:51:53.760> should<00:51:53.960> be<00:51:54.119> thinking<00:51:54.440> differently<00:51:54.880> about 00:51:55.069 --> 00:51:55.079 align:start position:0% you should be thinking differently about 00:51:55.079 --> 00:51:57.349 align:start position:0% you should be thinking differently about how<00:51:55.280> to<00:51:55.400> report<00:51:56.000> some<00:51:56.200> people<00:51:56.640> leave<00:51:56.799> them 00:51:57.349 --> 00:51:57.359 align:start position:0% how to report some people leave them 00:51:57.359 --> 00:51:59.710 align:start position:0% how to report some people leave them influence<00:51:58.000> judges<00:51:58.559> some<00:51:58.760> people<00:51:59.119> throw 00:51:59.710 --> 00:51:59.720 align:start position:0% influence judges some people throw 00:51:59.720 --> 00:52:01.230 align:start position:0% influence judges some people throw at<00:51:59.920> each<00:52:00.040> other<00:52:00.319> just<00:52:00.480> to<00:52:00.680> escalate<00:52:01.079> their 00:52:01.230 --> 00:52:01.240 align:start position:0% at each other just to escalate their 00:52:01.240 --> 00:52:04.190 align:start position:0% at each other just to escalate their bags<00:52:01.720> I<00:52:01.799> mean<00:52:02.720> they<00:52:02.839> are<00:52:03.000> a<00:52:03.200> different<00:52:03.799> mindset 00:52:04.190 --> 00:52:04.200 align:start position:0% bags I mean they are a different mindset 00:52:04.200 --> 00:52:06.750 align:start position:0% bags I mean they are a different mindset too<00:52:04.559> so<00:52:05.440> uh<00:52:05.559> if<00:52:05.680> you're<00:52:05.799> an<00:52:05.960> auditor<00:52:06.480> perhaps 00:52:06.750 --> 00:52:06.760 align:start position:0% too so uh if you're an auditor perhaps 00:52:06.760 --> 00:52:07.910 align:start position:0% too so uh if you're an auditor perhaps you're<00:52:06.839> not<00:52:06.960> a<00:52:07.079> back<00:52:07.240> Hunter<00:52:07.520> and<00:52:07.640> perhaps 00:52:07.910 --> 00:52:07.920 align:start position:0% you're not a back Hunter and perhaps 00:52:07.920 --> 00:52:09.549 align:start position:0% you're not a back Hunter and perhaps you're<00:52:08.240> not<00:52:08.440> good<00:52:08.599> at<00:52:08.760> contest<00:52:09.119> or<00:52:09.280> the<00:52:09.400> other 00:52:09.549 --> 00:52:09.559 align:start position:0% you're not good at contest or the other 00:52:09.559 --> 00:52:11.470 align:start position:0% you're not good at contest or the other way<00:52:09.760> around<00:52:10.160> but<00:52:10.280> choose<00:52:10.520> your<00:52:10.720> ground<00:52:11.319> and 00:52:11.470 --> 00:52:11.480 align:start position:0% way around but choose your ground and 00:52:11.480 --> 00:52:13.190 align:start position:0% way around but choose your ground and know<00:52:11.760> what<00:52:11.880> you're 00:52:13.190 --> 00:52:13.200 align:start position:0% know what you're 00:52:13.200 --> 00:52:16.230 align:start position:0% know what you're doing<00:52:14.200> uh<00:52:14.400> I<00:52:14.480> about<00:52:14.640> to<00:52:14.760> wrap<00:52:15.000> up 00:52:16.230 --> 00:52:16.240 align:start position:0% doing uh I about to wrap up 00:52:16.240 --> 00:52:19.549 align:start position:0% doing uh I about to wrap up so<00:52:17.240> whatever<00:52:17.880> ground<00:52:18.240> you<00:52:18.359> choose<00:52:19.119> H<00:52:19.280> try<00:52:19.480> to 00:52:19.549 --> 00:52:19.559 align:start position:0% so whatever ground you choose H try to 00:52:19.559 --> 00:52:22.309 align:start position:0% so whatever ground you choose H try to be<00:52:20.119> professional<00:52:21.119> we<00:52:21.240> see<00:52:21.440> lots<00:52:21.640> of<00:52:21.799> people<00:52:22.000> on 00:52:22.309 --> 00:52:22.319 align:start position:0% be professional we see lots of people on 00:52:22.319 --> 00:52:25.950 align:start position:0% be professional we see lots of people on Twitter<00:52:23.799> um<00:52:24.799> not<00:52:25.079> representing<00:52:25.640> very<00:52:25.799> well 00:52:25.950 --> 00:52:25.960 align:start position:0% Twitter um not representing very well 00:52:25.960 --> 00:52:28.630 align:start position:0% Twitter um not representing very well the<00:52:26.079> security<00:52:26.640> community<00:52:26.960> in<00:52:27.119> many<00:52:27.319> ways<00:52:28.280> so<00:52:28.520> I 00:52:28.630 --> 00:52:28.640 align:start position:0% the security community in many ways so I 00:52:28.640 --> 00:52:30.390 align:start position:0% the security community in many ways so I always<00:52:28.839> try<00:52:29.079> to<00:52:29.520> share<00:52:29.799> with<00:52:29.960> people<00:52:30.200> these 00:52:30.390 --> 00:52:30.400 align:start position:0% always try to share with people these 00:52:30.400 --> 00:52:32.190 align:start position:0% always try to share with people these ideas<00:52:30.760> of<00:52:31.000> being<00:52:31.240> assertive<00:52:31.720> without<00:52:31.960> being 00:52:32.190 --> 00:52:32.200 align:start position:0% ideas of being assertive without being 00:52:32.200 --> 00:52:33.789 align:start position:0% ideas of being assertive without being aggressive<00:52:32.720> stand<00:52:33.000> your<00:52:33.200> ground<00:52:33.520> but<00:52:33.640> not 00:52:33.789 --> 00:52:33.799 align:start position:0% aggressive stand your ground but not 00:52:33.799 --> 00:52:34.990 align:start position:0% aggressive stand your ground but not necessarily<00:52:34.200> being<00:52:34.480> aggressive<00:52:34.839> with 00:52:34.990 --> 00:52:35.000 align:start position:0% necessarily being aggressive with 00:52:35.000 --> 00:52:37.510 align:start position:0% necessarily being aggressive with developers<00:52:35.520> be<00:52:35.680> empathetic<00:52:36.160> to<00:52:36.359> them<00:52:37.119> and<00:52:37.280> new 00:52:37.510 --> 00:52:37.520 align:start position:0% developers be empathetic to them and new 00:52:37.520 --> 00:52:39.069 align:start position:0% developers be empathetic to them and new developers<00:52:37.960> with<00:52:38.119> have<00:52:38.319> security<00:52:38.680> research 00:52:39.069 --> 00:52:39.079 align:start position:0% developers with have security research 00:52:39.079 --> 00:52:41.870 align:start position:0% developers with have security research too<00:52:40.040> we<00:52:40.200> try<00:52:40.559> we<00:52:40.680> try<00:52:40.880> to<00:52:41.079> always<00:52:41.319> be<00:52:41.599> as 00:52:41.870 --> 00:52:41.880 align:start position:0% too we try we try to always be as 00:52:41.880 --> 00:52:45.430 align:start position:0% too we try we try to always be as thoughtful<00:52:42.319> as<00:52:42.599> possible<00:52:43.440> we<00:52:43.599> take<00:52:43.799> our<00:52:44.319> time 00:52:45.430 --> 00:52:45.440 align:start position:0% thoughtful as possible we take our time 00:52:45.440 --> 00:52:48.150 align:start position:0% thoughtful as possible we take our time uh<00:52:46.440> to<00:52:46.680> think<00:52:46.960> about<00:52:47.359> the<00:52:47.480> things<00:52:47.720> we<00:52:47.880> want<00:52:48.040> to 00:52:48.150 --> 00:52:48.160 align:start position:0% uh to think about the things we want to 00:52:48.160 --> 00:52:49.990 align:start position:0% uh to think about the things we want to report<00:52:48.520> the<00:52:48.599> things<00:52:48.839> I<00:52:48.960> want<00:52:49.079> to<00:52:49.200> explore<00:52:49.880> the 00:52:49.990 --> 00:52:50.000 align:start position:0% report the things I want to explore the 00:52:50.000 --> 00:52:54.270 align:start position:0% report the things I want to explore the things<00:52:50.319> that<00:52:50.599> we<00:52:50.720> share<00:52:51.079> with<00:52:51.599> you<00:52:52.960> um<00:52:53.960> always 00:52:54.270 --> 00:52:54.280 align:start position:0% things that we share with you um always 00:52:54.280 --> 00:52:56.190 align:start position:0% things that we share with you um always putting<00:52:54.599> as<00:52:54.799> much<00:52:55.079> attention<00:52:55.520> to<00:52:55.720> detail<00:52:56.079> as 00:52:56.190 --> 00:52:56.200 align:start position:0% putting as much attention to detail as 00:52:56.200 --> 00:52:57.309 align:start position:0% putting as much attention to detail as possible 00:52:57.309 --> 00:52:57.319 align:start position:0% possible 00:52:57.319 --> 00:53:00.789 align:start position:0% possible this<00:52:57.440> is<00:52:57.559> a<00:52:57.839> big<00:52:58.400> uh<00:52:58.720> thing<00:52:59.000> to<00:52:59.280> me<00:53:00.280> uh<00:53:00.520> paying 00:53:00.789 --> 00:53:00.799 align:start position:0% this is a big uh thing to me uh paying 00:53:00.799 --> 00:53:03.549 align:start position:0% this is a big uh thing to me uh paying attention<00:53:01.200> to<00:53:01.599> details<00:53:01.960> in 00:53:03.549 --> 00:53:03.559 align:start position:0% attention to details in 00:53:03.559 --> 00:53:05.990 align:start position:0% attention to details in reports<00:53:04.559> to<00:53:04.760> the<00:53:04.920> code<00:53:05.240> when<00:53:05.400> I'm<00:53:05.640> when<00:53:05.760> trying 00:53:05.990 --> 00:53:06.000 align:start position:0% reports to the code when I'm when trying 00:53:06.000 --> 00:53:07.829 align:start position:0% reports to the code when I'm when trying to<00:53:06.160> find<00:53:06.760> uh 00:53:07.829 --> 00:53:07.839 align:start position:0% to find uh 00:53:07.839 --> 00:53:11.230 align:start position:0% to find uh BS<00:53:08.839> so<00:53:09.119> very<00:53:09.319> being<00:53:09.559> very<00:53:09.760> thorough<00:53:10.559> being 00:53:11.230 --> 00:53:11.240 align:start position:0% BS so very being very thorough being 00:53:11.240 --> 00:53:12.950 align:start position:0% BS so very being very thorough being sometimes<00:53:11.440> slow<00:53:12.079> and<00:53:12.200> being<00:53:12.520> thoughtful 00:53:12.950 --> 00:53:12.960 align:start position:0% sometimes slow and being thoughtful 00:53:12.960 --> 00:53:15.950 align:start position:0% sometimes slow and being thoughtful about<00:53:13.200> what<00:53:13.280> I<00:53:13.640> do<00:53:14.640> and<00:53:14.880> always<00:53:15.319> trying<00:53:15.599> to<00:53:15.720> be 00:53:15.950 --> 00:53:15.960 align:start position:0% about what I do and always trying to be 00:53:15.960 --> 00:53:18.109 align:start position:0% about what I do and always trying to be kind<00:53:16.440> to<00:53:16.599> each<00:53:16.760> other<00:53:17.200> I<00:53:17.400> I<00:53:17.599> this<00:53:17.680> is<00:53:17.880> the<00:53:18.000> kind 00:53:18.109 --> 00:53:18.119 align:start position:0% kind to each other I I this is the kind 00:53:18.119 --> 00:53:20.030 align:start position:0% kind to each other I I this is the kind of<00:53:18.240> the<00:53:18.359> hippie<00:53:18.720> part<00:53:18.960> but<00:53:19.359> trying<00:53:19.599> to<00:53:19.720> be<00:53:19.839> kind 00:53:20.030 --> 00:53:20.040 align:start position:0% of the hippie part but trying to be kind 00:53:20.040 --> 00:53:22.510 align:start position:0% of the hippie part but trying to be kind to<00:53:20.160> each<00:53:20.280> other<00:53:20.559> and<00:53:21.000> respectful<00:53:22.000> uh<00:53:22.119> we<00:53:22.240> all 00:53:22.510 --> 00:53:22.520 align:start position:0% to each other and respectful uh we all 00:53:22.520 --> 00:53:24.990 align:start position:0% to each other and respectful uh we all have<00:53:23.160> uh<00:53:23.280> we<00:53:23.400> are<00:53:23.720> humans<00:53:24.359> we<00:53:24.480> have<00:53:24.640> friends 00:53:24.990 --> 00:53:25.000 align:start position:0% have uh we are humans we have friends 00:53:25.000 --> 00:53:27.510 align:start position:0% have uh we are humans we have friends family<00:53:25.480> problems<00:53:26.720> we<00:53:26.839> can<00:53:27.000> get<00:53:27.280> very 00:53:27.510 --> 00:53:27.520 align:start position:0% family problems we can get very 00:53:27.520 --> 00:53:30.309 align:start position:0% family problems we can get very adversarial<00:53:28.520> sometimes<00:53:29.520> uh<00:53:29.760> but<00:53:29.920> as<00:53:30.040> long<00:53:30.200> as 00:53:30.309 --> 00:53:30.319 align:start position:0% adversarial sometimes uh but as long as 00:53:30.319 --> 00:53:32.230 align:start position:0% adversarial sometimes uh but as long as we<00:53:30.400> are<00:53:30.559> respectful<00:53:30.960> to<00:53:31.119> each<00:53:31.280> other<00:53:31.960> uh<00:53:32.079> and 00:53:32.230 --> 00:53:32.240 align:start position:0% we are respectful to each other uh and 00:53:32.240 --> 00:53:34.710 align:start position:0% we are respectful to each other uh and we<00:53:32.319> don't<00:53:33.599> each<00:53:33.720> other<00:53:34.040> publicly<00:53:34.599> on 00:53:34.710 --> 00:53:34.720 align:start position:0% we don't each other publicly on 00:53:34.720 --> 00:53:36.710 align:start position:0% we don't each other publicly on Twitter<00:53:35.480> uh<00:53:35.839> sometimes<00:53:36.079> it<00:53:36.240> could<00:53:36.440> be 00:53:36.710 --> 00:53:36.720 align:start position:0% Twitter uh sometimes it could be 00:53:36.720 --> 00:53:40.870 align:start position:0% Twitter uh sometimes it could be necessary<00:53:37.240> a<00:53:37.359> little<00:53:37.799> bit<00:53:39.000> um<00:53:40.000> but<00:53:40.200> please 00:53:40.870 --> 00:53:40.880 align:start position:0% necessary a little bit um but please 00:53:40.880 --> 00:53:42.870 align:start position:0% necessary a little bit um but please avoid<00:53:41.200> those<00:53:41.839> reports<00:53:42.200> on<00:53:42.319> Twitter 00:53:42.870 --> 00:53:42.880 align:start position:0% avoid those reports on Twitter 00:53:42.880 --> 00:53:44.829 align:start position:0% avoid those reports on Twitter or<00:53:43.040> you<00:53:43.280> just<00:53:43.480> public<00:53:43.760> shaming<00:53:44.240> somebody 00:53:44.829 --> 00:53:44.839 align:start position:0% or you just public shaming somebody 00:53:44.839 --> 00:53:46.349 align:start position:0% or you just public shaming somebody somebody<00:53:45.240> that<00:53:45.359> is<00:53:45.520> not<00:53:45.760> answering<00:53:46.200> your 00:53:46.349 --> 00:53:46.359 align:start position:0% somebody that is not answering your 00:53:46.359 --> 00:53:48.270 align:start position:0% somebody that is not answering your report<00:53:46.680> that<00:53:46.799> you<00:53:46.960> just<00:53:47.160> submitted<00:53:47.920> 15 00:53:48.270 --> 00:53:48.280 align:start position:0% report that you just submitted 15 00:53:48.280 --> 00:53:50.789 align:start position:0% report that you just submitted 15 minutes<00:53:48.640> ago<00:53:49.240> and<00:53:49.400> it's<00:53:50.079> ends<00:53:50.280> up<00:53:50.480> being<00:53:50.640> an 00:53:50.789 --> 00:53:50.799 align:start position:0% minutes ago and it's ends up being an 00:53:50.799 --> 00:53:53.230 align:start position:0% minutes ago and it's ends up being an informational<00:53:51.440> or<00:53:51.640> whatever<00:53:52.599> uh<00:53:52.720> so<00:53:52.960> try<00:53:53.160> to 00:53:53.230 --> 00:53:53.240 align:start position:0% informational or whatever uh so try to 00:53:53.240 --> 00:53:57.150 align:start position:0% informational or whatever uh so try to be<00:53:53.480> professional<00:53:54.240> uh<00:53:54.440> we're<00:53:54.680> try<00:53:54.960> to<00:53:55.079> be<00:53:55.319> like 00:53:57.150 --> 00:53:57.160 align:start position:0% be professional uh we're try to be like 00:53:57.160 --> 00:54:00.829 align:start position:0% be professional uh we're try to be like big<00:53:57.480> security<00:53:57.920> Community 00:54:00.829 --> 00:54:00.839 align:start position:0% 00:54:00.839 --> 00:54:03.670 align:start position:0% here<00:54:01.839> wrapping<00:54:02.240> up<00:54:02.559> have<00:54:02.799> patience 00:54:03.670 --> 00:54:03.680 align:start position:0% here wrapping up have patience 00:54:03.680 --> 00:54:06.430 align:start position:0% here wrapping up have patience everything<00:54:04.040> takes<00:54:04.559> time<00:54:05.559> particularly<00:54:06.280> when 00:54:06.430 --> 00:54:06.440 align:start position:0% everything takes time particularly when 00:54:06.440 --> 00:54:08.030 align:start position:0% everything takes time particularly when you're<00:54:06.640> doing<00:54:06.960> security<00:54:07.559> becoming<00:54:07.880> a 00:54:08.030 --> 00:54:08.040 align:start position:0% you're doing security becoming a 00:54:08.040 --> 00:54:10.349 align:start position:0% you're doing security becoming a security<00:54:08.400> researcher<00:54:08.880> takes<00:54:09.160> time<00:54:09.920> finding 00:54:10.349 --> 00:54:10.359 align:start position:0% security researcher takes time finding 00:54:10.359 --> 00:54:12.829 align:start position:0% security researcher takes time finding backs<00:54:10.720> takes<00:54:11.040> time<00:54:11.559> reporting<00:54:12.200> triaging 00:54:12.829 --> 00:54:12.839 align:start position:0% backs takes time reporting triaging 00:54:12.839 --> 00:54:15.630 align:start position:0% backs takes time reporting triaging judging<00:54:13.799> escalations<00:54:14.799> let's<00:54:15.000> not<00:54:15.200> even<00:54:15.400> talk 00:54:15.630 --> 00:54:15.640 align:start position:0% judging escalations let's not even talk 00:54:15.640 --> 00:54:18.950 align:start position:0% judging escalations let's not even talk about<00:54:15.960> how<00:54:16.240> payment<00:54:16.640> sometime<00:54:17.079> takes<00:54:17.839> endless 00:54:18.950 --> 00:54:18.960 align:start position:0% about how payment sometime takes endless 00:54:18.960 --> 00:54:21.589 align:start position:0% about how payment sometime takes endless time<00:54:19.960> so<00:54:20.200> yeah<00:54:20.319> it's<00:54:20.480> a<00:54:20.599> game<00:54:20.760> of<00:54:20.920> patience 00:54:21.589 --> 00:54:21.599 align:start position:0% time so yeah it's a game of patience 00:54:21.599 --> 00:54:23.430 align:start position:0% time so yeah it's a game of patience lots<00:54:21.799> of<00:54:21.920> people<00:54:22.200> coming<00:54:22.559> to<00:54:22.760> me<00:54:23.119> what<00:54:23.280> should 00:54:23.430 --> 00:54:23.440 align:start position:0% lots of people coming to me what should 00:54:23.440 --> 00:54:25.109 align:start position:0% lots of people coming to me what should I<00:54:23.559> do<00:54:23.839> how<00:54:23.960> should<00:54:24.079> I<00:54:24.200> get<00:54:24.440> started<00:54:24.880> how<00:54:24.960> should 00:54:25.109 --> 00:54:25.119 align:start position:0% I do how should I get started how should 00:54:25.119 --> 00:54:27.150 align:start position:0% I do how should I get started how should I<00:54:25.240> find<00:54:25.640> this<00:54:25.960> this<00:54:26.079> and<00:54:26.240> that 00:54:27.150 --> 00:54:27.160 align:start position:0% I find this this and that 00:54:27.160 --> 00:54:29.390 align:start position:0% I find this this and that and<00:54:27.480> what<00:54:27.599> I<00:54:27.760> always<00:54:27.960> do<00:54:28.160> is<00:54:28.319> be<00:54:28.559> patient<00:54:29.240> uh 00:54:29.390 --> 00:54:29.400 align:start position:0% and what I always do is be patient uh 00:54:29.400 --> 00:54:32.829 align:start position:0% and what I always do is be patient uh because<00:54:30.280> uh<00:54:30.880> we<00:54:31.000> are<00:54:31.200> here<00:54:31.319> for<00:54:31.480> the<00:54:31.599> long 00:54:32.829 --> 00:54:32.839 align:start position:0% because uh we are here for the long 00:54:32.839 --> 00:54:41.910 align:start position:0% because uh we are here for the long run<00:54:33.839> Rajiv<00:54:34.760> you're<00:54:35.040> up<00:54:36.040> thank 00:54:41.910 --> 00:54:41.920 align:start position:0% 00:54:41.920 --> 00:54:45.309 align:start position:0% you<00:54:42.920> great<00:54:43.440> good<00:54:43.599> to<00:54:43.760> see<00:54:44.160> uh<00:54:44.319> people<00:54:44.880> sticking 00:54:45.309 --> 00:54:45.319 align:start position:0% you great good to see uh people sticking 00:54:45.319 --> 00:54:48.829 align:start position:0% you great good to see uh people sticking around<00:54:45.599> till<00:54:46.240> the<00:54:46.400> 30th<00:54:46.920> tip<00:54:47.920> so<00:54:48.520> uh<00:54:48.640> people 00:54:48.829 --> 00:54:48.839 align:start position:0% around till the 30th tip so uh people 00:54:48.839 --> 00:54:50.150 align:start position:0% around till the 30th tip so uh people may<00:54:49.000> be<00:54:49.160> getting<00:54:49.359> hungry<00:54:49.760> but<00:54:49.880> I<00:54:49.960> would 00:54:50.150 --> 00:54:50.160 align:start position:0% may be getting hungry but I would 00:54:50.160 --> 00:54:53.510 align:start position:0% may be getting hungry but I would request<00:54:50.559> you<00:54:50.720> to<00:54:51.000> stick<00:54:51.480> stick<00:54:51.799> around<00:54:52.160> for<00:54:52.960> 12 00:54:53.510 --> 00:54:53.520 align:start position:0% request you to stick stick around for 12 00:54:53.520 --> 00:54:56.589 align:start position:0% request you to stick stick around for 12 more<00:54:54.520> uh<00:54:54.640> there<00:54:54.760> is<00:54:54.920> a<00:54:55.079> fun<00:54:55.520> quiz<00:54:56.119> at<00:54:56.400> at<00:54:56.480> the 00:54:56.589 --> 00:54:56.599 align:start position:0% more uh there is a fun quiz at at the 00:54:56.599 --> 00:54:59.589 align:start position:0% more uh there is a fun quiz at at the end<00:54:57.200> with<00:54:57.480> rewards<00:54:58.200> which<00:54:58.440> may<00:54:58.599> be 00:54:59.589 --> 00:54:59.599 align:start position:0% end with rewards which may be 00:54:59.599 --> 00:55:02.670 align:start position:0% end with rewards which may be interesting<00:55:00.599> all<00:55:00.799> right<00:55:01.119> so<00:55:01.559> uh<00:55:01.760> the<00:55:01.920> next<00:55:02.200> 10 00:55:02.670 --> 00:55:02.680 align:start position:0% interesting all right so uh the next 10 00:55:02.680 --> 00:55:06.750 align:start position:0% interesting all right so uh the next 10 tips<00:55:03.359> more<00:55:04.079> uh<00:55:04.359> memes<00:55:04.880> I<00:55:04.960> would<00:55:05.480> say<00:55:06.480> um<00:55:06.680> I 00:55:06.750 --> 00:55:06.760 align:start position:0% tips more uh memes I would say um I 00:55:06.760 --> 00:55:09.270 align:start position:0% tips more uh memes I would say um I would<00:55:06.960> like<00:55:07.440> like<00:55:07.640> us<00:55:07.799> to<00:55:08.000> zoom<00:55:08.559> zoom<00:55:08.839> out 00:55:09.270 --> 00:55:09.280 align:start position:0% would like like us to zoom zoom out 00:55:09.280 --> 00:55:11.870 align:start position:0% would like like us to zoom zoom out right<00:55:10.040> so<00:55:10.400> you've<00:55:10.640> had<00:55:10.839> fantastic<00:55:11.280> tips<00:55:11.680> sort 00:55:11.870 --> 00:55:11.880 align:start position:0% right so you've had fantastic tips sort 00:55:11.880 --> 00:55:15.270 align:start position:0% right so you've had fantastic tips sort of<00:55:12.240> covering<00:55:13.240> both<00:55:13.559> the<00:55:13.720> security<00:55:14.119> researcher 00:55:15.270 --> 00:55:15.280 align:start position:0% of covering both the security researcher 00:55:15.280 --> 00:55:18.109 align:start position:0% of covering both the security researcher mindset<00:55:16.280> good<00:55:16.440> to<00:55:16.559> see<00:55:16.799> developers<00:55:17.319> as<00:55:17.480> well 00:55:18.109 --> 00:55:18.119 align:start position:0% mindset good to see developers as well 00:55:18.119 --> 00:55:20.390 align:start position:0% mindset good to see developers as well so<00:55:18.480> covering<00:55:18.880> that<00:55:19.119> as<00:55:19.240> well<00:55:19.880> and<00:55:20.040> by<00:55:20.160> the<00:55:20.240> way 00:55:20.390 --> 00:55:20.400 align:start position:0% so covering that as well and by the way 00:55:20.400 --> 00:55:23.029 align:start position:0% so covering that as well and by the way on<00:55:20.599> that<00:55:20.839> we<00:55:21.000> need<00:55:21.520> we<00:55:21.680> need<00:55:21.920> more<00:55:22.280> people<00:55:22.720> in 00:55:23.029 --> 00:55:23.039 align:start position:0% on that we need we need more people in 00:55:23.039 --> 00:55:25.750 align:start position:0% on that we need we need more people in security<00:55:23.480> so<00:55:23.640> if<00:55:23.760> you're<00:55:24.160> devs<00:55:25.160> then<00:55:25.480> do 00:55:25.750 --> 00:55:25.760 align:start position:0% security so if you're devs then do 00:55:25.760 --> 00:55:28.750 align:start position:0% security so if you're devs then do consider<00:55:26.480> not<00:55:26.720> just<00:55:27.359> securing<00:55:27.839> your<00:55:27.960> own<00:55:28.200> code 00:55:28.750 --> 00:55:28.760 align:start position:0% consider not just securing your own code 00:55:28.760 --> 00:55:31.870 align:start position:0% consider not just securing your own code base<00:55:29.760> um<00:55:30.359> and<00:55:30.640> having<00:55:30.880> that<00:55:31.079> attacker<00:55:31.440> mindset 00:55:31.870 --> 00:55:31.880 align:start position:0% base um and having that attacker mindset 00:55:31.880 --> 00:55:34.270 align:start position:0% base um and having that attacker mindset security<00:55:32.319> mindset<00:55:32.720> but<00:55:32.839> do<00:55:33.119> consider<00:55:33.920> looking 00:55:34.270 --> 00:55:34.280 align:start position:0% security mindset but do consider looking 00:55:34.280 --> 00:55:36.710 align:start position:0% security mindset but do consider looking into<00:55:34.599> security<00:55:35.359> getting<00:55:35.640> into<00:55:35.920> more<00:55:36.319> of 00:55:36.710 --> 00:55:36.720 align:start position:0% into security getting into more of 00:55:36.720 --> 00:55:39.470 align:start position:0% into security getting into more of security<00:55:37.160> as<00:55:37.359> well<00:55:38.359> so<00:55:38.520> in<00:55:38.680> this<00:55:38.880> case<00:55:39.319> the 00:55:39.470 --> 00:55:39.480 align:start position:0% security as well so in this case the 00:55:39.480 --> 00:55:43.270 align:start position:0% security as well so in this case the first<00:55:39.799> thing<00:55:40.400> is<00:55:41.000> really<00:55:41.760> both<00:55:42.000> as<00:55:42.079> a<00:55:42.319> Dev<00:55:43.160> as 00:55:43.270 --> 00:55:43.280 align:start position:0% first thing is really both as a Dev as 00:55:43.280 --> 00:55:45.589 align:start position:0% first thing is really both as a Dev as well<00:55:43.440> as<00:55:43.559> a<00:55:43.720> security<00:55:44.079> researcher<00:55:44.640> is<00:55:44.799> to<00:55:45.240> zoom 00:55:45.589 --> 00:55:45.599 align:start position:0% well as a security researcher is to zoom 00:55:45.599 --> 00:55:47.789 align:start position:0% well as a security researcher is to zoom out<00:55:46.400> and<00:55:46.559> sort<00:55:46.799> of 00:55:47.789 --> 00:55:47.799 align:start position:0% out and sort of 00:55:47.799 --> 00:55:50.150 align:start position:0% out and sort of assess<00:55:48.799> the<00:55:49.000> protocol<00:55:49.480> that<00:55:49.599> you're<00:55:49.760> building 00:55:50.150 --> 00:55:50.160 align:start position:0% assess the protocol that you're building 00:55:50.160 --> 00:55:54.069 align:start position:0% assess the protocol that you're building or<00:55:50.400> reviewing<00:55:51.480> right<00:55:52.480> first<00:55:52.760> thing<00:55:53.079> is<00:55:53.880> I<00:55:53.920> mean 00:55:54.069 --> 00:55:54.079 align:start position:0% or reviewing right first thing is I mean 00:55:54.079 --> 00:55:56.750 align:start position:0% or reviewing right first thing is I mean look<00:55:54.240> at<00:55:54.440> this<00:55:54.839> so<00:55:55.280> Billy 00:55:56.750 --> 00:55:56.760 align:start position:0% look at this so Billy 00:55:56.760 --> 00:56:01.309 align:start position:0% look at this so Billy somebody<00:55:57.200> hands<00:55:57.520> them<00:55:58.280> or<00:55:58.640> her<00:55:59.640> um<00:56:00.520> money 00:56:01.309 --> 00:56:01.319 align:start position:0% somebody hands them or her um money 00:56:01.319 --> 00:56:03.829 align:start position:0% somebody hands them or her um money right<00:56:02.280> but<00:56:02.440> would<00:56:02.680> like<00:56:02.880> to<00:56:03.039> sort<00:56:03.240> of<00:56:03.520> take 00:56:03.829 --> 00:56:03.839 align:start position:0% right but would like to sort of take 00:56:03.839 --> 00:56:05.910 align:start position:0% right but would like to sort of take time<00:56:04.280> to<00:56:04.480> explain<00:56:04.880> the<00:56:05.000> importance<00:56:05.440> of<00:56:05.599> smart 00:56:05.910 --> 00:56:05.920 align:start position:0% time to explain the importance of smart 00:56:05.920 --> 00:56:08.630 align:start position:0% time to explain the importance of smart contract<00:56:06.280> security<00:56:06.799> but<00:56:06.920> of<00:56:07.119> course<00:56:07.680> you<00:56:07.799> know 00:56:08.630 --> 00:56:08.640 align:start position:0% contract security but of course you know 00:56:08.640 --> 00:56:12.670 align:start position:0% contract security but of course you know YOLO<00:56:09.640> go<00:56:10.079> and<00:56:10.520> dgen<00:56:10.960> mode<00:56:11.720> look<00:56:11.920> at<00:56:12.359> what<00:56:12.520> the 00:56:12.670 --> 00:56:12.680 align:start position:0% YOLO go and dgen mode look at what the 00:56:12.680 --> 00:56:14.670 align:start position:0% YOLO go and dgen mode look at what the assets<00:56:13.039> are<00:56:13.720> put<00:56:13.920> it<00:56:14.039> into<00:56:14.240> the<00:56:14.319> vending 00:56:14.670 --> 00:56:14.680 align:start position:0% assets are put it into the vending 00:56:14.680 --> 00:56:18.190 align:start position:0% assets are put it into the vending machine<00:56:15.680> do<00:56:15.880> some<00:56:16.200> actions<00:56:17.079> and<00:56:17.319> then<00:56:18.079> you 00:56:18.190 --> 00:56:18.200 align:start position:0% machine do some actions and then you 00:56:18.200 --> 00:56:22.029 align:start position:0% machine do some actions and then you know<00:56:18.880> make<00:56:19.119> money<00:56:19.559> or<00:56:19.760> regret<00:56:20.440> right<00:56:21.240> so<00:56:21.880> this 00:56:22.029 --> 00:56:22.039 align:start position:0% know make money or regret right so this 00:56:22.039 --> 00:56:25.549 align:start position:0% know make money or regret right so this is<00:56:22.520> I<00:56:22.599> mean<00:56:22.960> this<00:56:23.079> may<00:56:23.240> seem<00:56:23.480> like<00:56:23.640> fun<00:56:24.559> but 00:56:25.549 --> 00:56:25.559 align:start position:0% is I mean this may seem like fun but 00:56:25.559 --> 00:56:27.390 align:start position:0% is I mean this may seem like fun but it's<00:56:25.799> all<00:56:26.000> about<00:56:26.400> the<00:56:26.520> assets<00:56:27.000> right<00:56:27.160> I<00:56:27.200> mean 00:56:27.390 --> 00:56:27.400 align:start position:0% it's all about the assets right I mean 00:56:27.400 --> 00:56:28.990 align:start position:0% it's all about the assets right I mean that's<00:56:27.599> that's<00:56:27.760> why<00:56:27.880> we're<00:56:28.119> here<00:56:28.599> all<00:56:28.799> these 00:56:28.990 --> 00:56:29.000 align:start position:0% that's that's why we're here all these 00:56:29.000 --> 00:56:30.670 align:start position:0% that's that's why we're here all these assets<00:56:29.240> are<00:56:29.400> being<00:56:29.559> put<00:56:29.720> on<00:56:29.799> the<00:56:29.920> blockchain 00:56:30.670 --> 00:56:30.680 align:start position:0% assets are being put on the blockchain 00:56:30.680 --> 00:56:32.589 align:start position:0% assets are being put on the blockchain in<00:56:31.240> U<00:56:31.480> various 00:56:32.589 --> 00:56:32.599 align:start position:0% in U various 00:56:32.599 --> 00:56:35.789 align:start position:0% in U various forms<00:56:33.599> what<00:56:33.760> are<00:56:33.960> those<00:56:34.559> assets<00:56:35.559> as<00:56:35.640> a 00:56:35.789 --> 00:56:35.799 align:start position:0% forms what are those assets as a 00:56:35.799 --> 00:56:37.270 align:start position:0% forms what are those assets as a protocol<00:56:36.280> you<00:56:36.400> obviously<00:56:36.720> will<00:56:36.880> have<00:56:37.000> a<00:56:37.119> very 00:56:37.270 --> 00:56:37.280 align:start position:0% protocol you obviously will have a very 00:56:37.280 --> 00:56:39.630 align:start position:0% protocol you obviously will have a very clear<00:56:37.559> view<00:56:37.799> as<00:56:37.880> a<00:56:38.200> developer<00:56:39.200> but<00:56:39.359> as<00:56:39.440> a 00:56:39.630 --> 00:56:39.640 align:start position:0% clear view as a developer but as a 00:56:39.640 --> 00:56:41.349 align:start position:0% clear view as a developer but as a security<00:56:40.039> researcher<00:56:40.760> this<00:56:40.839> is<00:56:41.000> the<00:56:41.160> first 00:56:41.349 --> 00:56:41.359 align:start position:0% security researcher this is the first 00:56:41.359 --> 00:56:44.109 align:start position:0% security researcher this is the first thing<00:56:41.480> you<00:56:41.599> need<00:56:41.760> to<00:56:41.880> see<00:56:42.160> what<00:56:42.400> tokens<00:56:43.119> right 00:56:44.109 --> 00:56:44.119 align:start position:0% thing you need to see what tokens right 00:56:44.119 --> 00:56:45.870 align:start position:0% thing you need to see what tokens right where<00:56:44.319> are<00:56:44.520> they<00:56:44.720> being 00:56:45.870 --> 00:56:45.880 align:start position:0% where are they being 00:56:45.880 --> 00:56:48.829 align:start position:0% where are they being held<00:56:46.880> where<00:56:47.079> is<00:56:47.240> it<00:56:47.400> entering<00:56:47.880> the<00:56:48.039> system<00:56:48.680> and 00:56:48.829 --> 00:56:48.839 align:start position:0% held where is it entering the system and 00:56:48.839 --> 00:56:50.750 align:start position:0% held where is it entering the system and more<00:56:49.079> importantly<00:56:49.640> where<00:56:49.760> is<00:56:49.880> it<00:56:50.160> exiting<00:56:50.599> the 00:56:50.750 --> 00:56:50.760 align:start position:0% more importantly where is it exiting the 00:56:50.760 --> 00:56:53.630 align:start position:0% more importantly where is it exiting the system<00:56:51.799> because<00:56:52.799> attackers<00:56:53.240> are<00:56:53.400> really 00:56:53.630 --> 00:56:53.640 align:start position:0% system because attackers are really 00:56:53.640 --> 00:56:56.069 align:start position:0% system because attackers are really looking<00:56:53.920> to<00:56:54.599> exit<00:56:55.039> out<00:56:55.240> of<00:56:55.359> the<00:56:55.520> system<00:56:55.880> with 00:56:56.069 --> 00:56:56.079 align:start position:0% looking to exit out of the system with 00:56:56.079 --> 00:56:58.990 align:start position:0% looking to exit out of the system with the<00:56:56.280> these<00:56:56.520> assets<00:56:57.280> right<00:56:57.760> so<00:56:58.319> having<00:56:58.720> this 00:56:58.990 --> 00:56:59.000 align:start position:0% the these assets right so having this 00:56:59.000 --> 00:57:01.470 align:start position:0% the these assets right so having this mental<00:56:59.400> model<00:57:00.160> documentation<00:57:00.799> of<00:57:01.000> assets<00:57:01.319> is 00:57:01.470 --> 00:57:01.480 align:start position:0% mental model documentation of assets is 00:57:01.480 --> 00:57:04.630 align:start position:0% mental model documentation of assets is really<00:57:02.119> critical<00:57:03.119> and<00:57:03.280> of<00:57:03.440> course<00:57:03.720> actors 00:57:04.630 --> 00:57:04.640 align:start position:0% really critical and of course actors 00:57:04.640 --> 00:57:07.109 align:start position:0% really critical and of course actors right<00:57:04.799> I<00:57:04.880> mean<00:57:05.079> these<00:57:05.280> actors<00:57:05.920> could<00:57:06.160> be<00:57:06.680> users 00:57:07.109 --> 00:57:07.119 align:start position:0% right I mean these actors could be users 00:57:07.119 --> 00:57:09.430 align:start position:0% right I mean these actors could be users of<00:57:07.280> your<00:57:07.480> system<00:57:08.119> could<00:57:08.280> be<00:57:08.520> abusers<00:57:09.119> could<00:57:09.280> be 00:57:09.430 --> 00:57:09.440 align:start position:0% of your system could be abusers could be 00:57:09.440 --> 00:57:13.309 align:start position:0% of your system could be abusers could be attackers<00:57:10.119> could<00:57:10.760> be<00:57:11.760> um<00:57:12.520> developers 00:57:13.309 --> 00:57:13.319 align:start position:0% attackers could be um developers 00:57:13.319 --> 00:57:15.630 align:start position:0% attackers could be um developers themselves<00:57:13.799> in<00:57:14.039> in<00:57:14.200> the<00:57:14.400> sense<00:57:14.720> of<00:57:15.200> you<00:57:15.359> know 00:57:15.630 --> 00:57:15.640 align:start position:0% themselves in in the sense of you know 00:57:15.640 --> 00:57:18.150 align:start position:0% themselves in in the sense of you know all<00:57:15.839> the<00:57:16.000> code<00:57:16.319> that's<00:57:16.559> gone<00:57:16.839> in<00:57:17.440> and 00:57:18.150 --> 00:57:18.160 align:start position:0% all the code that's gone in and 00:57:18.160 --> 00:57:20.549 align:start position:0% all the code that's gone in and potential<00:57:19.160> um 00:57:20.549 --> 00:57:20.559 align:start position:0% potential um 00:57:20.559 --> 00:57:22.789 align:start position:0% potential um impacts<00:57:21.559> negative<00:57:21.960> impacts<00:57:22.319> as<00:57:22.440> well<00:57:22.599> I'll 00:57:22.789 --> 00:57:22.799 align:start position:0% impacts negative impacts as well I'll 00:57:22.799 --> 00:57:25.029 align:start position:0% impacts negative impacts as well I'll get<00:57:22.920> into<00:57:23.160> more<00:57:23.440> more<00:57:23.599> of<00:57:23.760> that<00:57:23.920> later<00:57:24.880> it 00:57:25.029 --> 00:57:25.039 align:start position:0% get into more more of that later it 00:57:25.039 --> 00:57:26.829 align:start position:0% get into more more of that later it could<00:57:25.200> be<00:57:25.359> even<00:57:25.559> the<00:57:25.720> governance<00:57:26.640> right<00:57:26.760> I 00:57:26.829 --> 00:57:26.839 align:start position:0% could be even the governance right I 00:57:26.839 --> 00:57:27.990 align:start position:0% could be even the governance right I mean<00:57:27.000> here<00:57:27.119> we<00:57:27.240> are<00:57:27.359> talking<00:57:27.559> about<00:57:27.720> smart 00:57:27.990 --> 00:57:28.000 align:start position:0% mean here we are talking about smart 00:57:28.000 --> 00:57:29.870 align:start position:0% mean here we are talking about smart contracts<00:57:28.400> in<00:57:28.480> general<00:57:28.920> right<00:57:29.200> so<00:57:29.599> it<00:57:29.720> could 00:57:29.870 --> 00:57:29.880 align:start position:0% contracts in general right so it could 00:57:29.880 --> 00:57:32.109 align:start position:0% contracts in general right so it could be<00:57:30.000> even<00:57:30.200> the<00:57:30.319> governance<00:57:30.839> and<00:57:31.039> how<00:57:31.200> does<00:57:31.559> that 00:57:32.109 --> 00:57:32.119 align:start position:0% be even the governance and how does that 00:57:32.119 --> 00:57:33.829 align:start position:0% be even the governance and how does that how<00:57:32.280> does<00:57:32.520> governance<00:57:32.960> as<00:57:33.079> an 00:57:33.829 --> 00:57:33.839 align:start position:0% how does governance as an 00:57:33.839 --> 00:57:37.950 align:start position:0% how does governance as an actor<00:57:34.839> factor<00:57:35.280> in<00:57:35.799> to<00:57:36.440> your<00:57:36.839> threat<00:57:37.160> model<00:57:37.480> or 00:57:37.950 --> 00:57:37.960 align:start position:0% actor factor in to your threat model or 00:57:37.960 --> 00:57:40.309 align:start position:0% actor factor in to your threat model or trust<00:57:38.319> model<00:57:38.920> so<00:57:39.119> that<00:57:39.240> has<00:57:39.359> to<00:57:39.440> be<00:57:39.599> considered 00:57:40.309 --> 00:57:40.319 align:start position:0% trust model so that has to be considered 00:57:40.319 --> 00:57:42.190 align:start position:0% trust model so that has to be considered and<00:57:40.480> of<00:57:40.599> course<00:57:40.799> all<00:57:40.960> the<00:57:41.119> actions<00:57:41.599> right<00:57:41.720> so 00:57:42.190 --> 00:57:42.200 align:start position:0% and of course all the actions right so 00:57:42.200 --> 00:57:44.789 align:start position:0% and of course all the actions right so what<00:57:42.359> are<00:57:42.599> what<00:57:42.720> are<00:57:42.839> the<00:57:43.000> various<00:57:43.680> actions<00:57:44.680> uh 00:57:44.789 --> 00:57:44.799 align:start position:0% what are what are the various actions uh 00:57:44.799 --> 00:57:47.349 align:start position:0% what are what are the various actions uh that<00:57:44.920> can<00:57:45.039> be<00:57:45.200> taken<00:57:45.480> by<00:57:45.680> these<00:57:46.200> actors<00:57:47.200> when 00:57:47.349 --> 00:57:47.359 align:start position:0% that can be taken by these actors when 00:57:47.359 --> 00:57:50.750 align:start position:0% that can be taken by these actors when are<00:57:47.599> these<00:57:47.839> actors<00:57:48.640> uh<00:57:48.839> when<00:57:48.960> are<00:57:49.160> these 00:57:50.750 --> 00:57:50.760 align:start position:0% are these actors uh when are these 00:57:50.760 --> 00:57:53.109 align:start position:0% are these actors uh when are these actions<00:57:51.760> happening<00:57:52.359> when<00:57:52.520> does<00:57:52.680> it<00:57:52.880> make 00:57:53.109 --> 00:57:53.119 align:start position:0% actions happening when does it make 00:57:53.119 --> 00:57:55.870 align:start position:0% actions happening when does it make sense<00:57:53.720> when<00:57:53.960> doesn't<00:57:54.319> it<00:57:54.520> make<00:57:54.760> sense<00:57:55.640> right<00:57:55.799> I 00:57:55.870 --> 00:57:55.880 align:start position:0% sense when doesn't it make sense right I 00:57:55.880 --> 00:57:58.710 align:start position:0% sense when doesn't it make sense right I mean<00:57:56.480> these<00:57:57.200> these<00:57:57.440> will<00:57:57.920> be<00:57:58.119> very<00:57:58.319> clear<00:57:58.559> to 00:57:58.710 --> 00:57:58.720 align:start position:0% mean these these will be very clear to 00:57:58.720 --> 00:58:00.150 align:start position:0% mean these these will be very clear to the<00:57:59.039> developers<00:57:59.520> or<00:57:59.680> the<00:57:59.799> security 00:58:00.150 --> 00:58:00.160 align:start position:0% the developers or the security 00:58:00.160 --> 00:58:02.029 align:start position:0% the developers or the security researchers<00:58:00.920> once<00:58:01.200> in<00:58:01.359> the<00:58:01.480> context<00:58:01.799> of<00:58:01.880> the 00:58:02.029 --> 00:58:02.039 align:start position:0% researchers once in the context of the 00:58:02.039 --> 00:58:04.069 align:start position:0% researchers once in the context of the protocol<00:58:02.760> but<00:58:02.880> you<00:58:03.079> really<00:58:03.319> have<00:58:03.440> to<00:58:03.559> zoom<00:58:03.839> out 00:58:04.069 --> 00:58:04.079 align:start position:0% protocol but you really have to zoom out 00:58:04.079 --> 00:58:05.950 align:start position:0% protocol but you really have to zoom out and<00:58:04.319> think<00:58:04.559> about<00:58:04.839> these<00:58:05.119> very 00:58:05.950 --> 00:58:05.960 align:start position:0% and think about these very 00:58:05.960 --> 00:58:09.270 align:start position:0% and think about these very consciously<00:58:06.960> and<00:58:07.119> how<00:58:07.280> are<00:58:07.440> these<00:58:07.680> actions 00:58:09.270 --> 00:58:09.280 align:start position:0% consciously and how are these actions 00:58:09.280 --> 00:58:11.510 align:start position:0% consciously and how are these actions impacting<00:58:10.280> the<00:58:10.520> assets<00:58:11.079> how<00:58:11.200> are<00:58:11.359> they 00:58:11.510 --> 00:58:11.520 align:start position:0% impacting the assets how are they 00:58:11.520 --> 00:58:13.589 align:start position:0% impacting the assets how are they impacting<00:58:11.920> the<00:58:12.039> actors<00:58:12.839> and<00:58:13.079> why<00:58:13.200> does<00:58:13.400> this 00:58:13.589 --> 00:58:13.599 align:start position:0% impacting the actors and why does this 00:58:13.599 --> 00:58:16.950 align:start position:0% impacting the actors and why does this all<00:58:14.000> make<00:58:14.240> sense<00:58:14.480> so<00:58:14.799> that<00:58:15.440> is<00:58:15.920> at<00:58:16.079> a<00:58:16.400> 100,000 00:58:16.950 --> 00:58:16.960 align:start position:0% all make sense so that is at a 100,000 00:58:16.960 --> 00:58:18.990 align:start position:0% all make sense so that is at a 100,000 foot<00:58:17.280> level<00:58:17.640> I<00:58:17.720> think<00:58:17.960> that<00:58:18.079> is<00:58:18.280> really<00:58:18.680> what 00:58:18.990 --> 00:58:19.000 align:start position:0% foot level I think that is really what 00:58:19.000 --> 00:58:20.950 align:start position:0% foot level I think that is really what this<00:58:19.079> is<00:58:19.240> really<00:58:19.480> what<00:58:19.599> security<00:58:20.000> is<00:58:20.160> about<00:58:20.720> so 00:58:20.950 --> 00:58:20.960 align:start position:0% this is really what security is about so 00:58:20.960 --> 00:58:23.910 align:start position:0% this is really what security is about so if<00:58:21.079> you<00:58:21.440> go<00:58:21.720> back<00:58:21.920> I<00:58:22.000> mean<00:58:22.680> uh<00:58:22.799> for<00:58:23.200> for<00:58:23.680> uh 00:58:23.910 --> 00:58:23.920 align:start position:0% if you go back I mean uh for for uh 00:58:23.920 --> 00:58:25.789 align:start position:0% if you go back I mean uh for for uh those<00:58:24.079> who<00:58:24.200> are<00:58:24.880> familiar<00:58:25.280> with<00:58:25.440> security 00:58:25.789 --> 00:58:25.799 align:start position:0% those who are familiar with security 00:58:25.799 --> 00:58:27.750 align:start position:0% those who are familiar with security Theory<00:58:26.359> this<00:58:26.480> is<00:58:26.640> really<00:58:26.960> what<00:58:27.280> an<00:58:27.440> access 00:58:27.750 --> 00:58:27.760 align:start position:0% Theory this is really what an access 00:58:27.760 --> 00:58:29.750 align:start position:0% Theory this is really what an access control<00:58:28.079> Matrix<00:58:28.559> is<00:58:28.880> you<00:58:29.000> have<00:58:29.160> the<00:58:29.319> subjects 00:58:29.750 --> 00:58:29.760 align:start position:0% control Matrix is you have the subjects 00:58:29.760 --> 00:58:31.789 align:start position:0% control Matrix is you have the subjects operating<00:58:30.119> on<00:58:30.240> the<00:58:30.400> objects<00:58:31.000> you<00:58:31.160> have<00:58:31.359> the 00:58:31.789 --> 00:58:31.799 align:start position:0% operating on the objects you have the 00:58:31.799 --> 00:58:34.630 align:start position:0% operating on the objects you have the Matrix<00:58:32.200> of<00:58:32.400> permissions<00:58:33.400> right<00:58:33.760> so<00:58:34.160> this<00:58:34.400> is 00:58:34.630 --> 00:58:34.640 align:start position:0% Matrix of permissions right so this is 00:58:34.640 --> 00:58:38.589 align:start position:0% Matrix of permissions right so this is fundamentally<00:58:35.400> what<00:58:35.559> we<00:58:35.640> are<00:58:35.799> looking 00:58:38.589 --> 00:58:38.599 align:start position:0% 00:58:38.599 --> 00:58:42.510 align:start position:0% at<00:58:39.599> all<00:58:39.720> right<00:58:40.000> the<00:58:40.079> second<00:58:40.520> meme<00:58:41.520> so<00:58:42.200> you<00:58:42.319> may 00:58:42.510 --> 00:58:42.520 align:start position:0% at all right the second meme so you may 00:58:42.520 --> 00:58:44.829 align:start position:0% at all right the second meme so you may see<00:58:42.760> sort<00:58:42.960> of<00:58:43.280> repeating 00:58:44.829 --> 00:58:44.839 align:start position:0% see sort of repeating 00:58:44.839 --> 00:58:48.390 align:start position:0% see sort of repeating repetitive<00:58:46.119> um<00:58:47.119> things<00:58:47.440> in<00:58:47.680> the<00:58:47.799> tips<00:58:48.119> that<00:58:48.280> we 00:58:48.390 --> 00:58:48.400 align:start position:0% repetitive um things in the tips that we 00:58:48.400 --> 00:58:50.990 align:start position:0% repetitive um things in the tips that we have<00:58:49.079> we've<00:58:49.280> been<00:58:49.480> talking<00:58:49.799> about<00:58:50.359> but<00:58:50.760> that 00:58:50.990 --> 00:58:51.000 align:start position:0% have we've been talking about but that 00:58:51.000 --> 00:58:53.270 align:start position:0% have we've been talking about but that this<00:58:51.119> is<00:58:51.799> what<00:58:51.960> we<00:58:52.039> are<00:58:52.160> doing<00:58:52.480> consciously<00:58:53.039> to 00:58:53.270 --> 00:58:53.280 align:start position:0% this is what we are doing consciously to 00:58:53.280 --> 00:58:57.309 align:start position:0% this is what we are doing consciously to drive<00:58:53.720> these<00:58:53.960> points<00:58:54.359> home<00:58:55.160> right 00:58:57.309 --> 00:58:57.319 align:start position:0% drive these points home right 00:58:57.319 --> 00:58:58.349 align:start position:0% drive these points home right as<00:58:57.440> a 00:58:58.349 --> 00:58:58.359 align:start position:0% as a 00:58:58.359 --> 00:59:03.029 align:start position:0% as a developer<00:58:59.359> you<00:58:59.559> may<00:58:59.880> have<00:59:00.480> an<00:59:00.880> expectation<00:59:02.039> of 00:59:03.029 --> 00:59:03.039 align:start position:0% developer you may have an expectation of 00:59:03.039 --> 00:59:06.510 align:start position:0% developer you may have an expectation of your<00:59:03.319> ideal<00:59:03.680> users<00:59:04.640> right<00:59:05.640> or<00:59:05.920> the<00:59:06.039> users<00:59:06.400> of 00:59:06.510 --> 00:59:06.520 align:start position:0% your ideal users right or the users of 00:59:06.520 --> 00:59:09.510 align:start position:0% your ideal users right or the users of your<00:59:06.960> protocol<00:59:07.960> but<00:59:08.119> the<00:59:08.319> reality<00:59:09.240> is<00:59:09.400> going 00:59:09.510 --> 00:59:09.520 align:start position:0% your protocol but the reality is going 00:59:09.520 --> 00:59:12.109 align:start position:0% your protocol but the reality is going to<00:59:09.680> be<00:59:09.920> very 00:59:12.109 --> 00:59:12.119 align:start position:0% to be very 00:59:12.119 --> 00:59:15.309 align:start position:0% to be very different<00:59:13.119> and<00:59:13.280> as<00:59:13.400> a<00:59:13.559> security<00:59:14.319> researcher 00:59:15.309 --> 00:59:15.319 align:start position:0% different and as a security researcher 00:59:15.319 --> 00:59:17.109 align:start position:0% different and as a security researcher this<00:59:15.440> is<00:59:15.599> something<00:59:15.920> you<00:59:16.039> have<00:59:16.160> to<00:59:16.359> pay<00:59:16.960> you 00:59:17.109 --> 00:59:17.119 align:start position:0% this is something you have to pay you 00:59:17.119 --> 00:59:20.029 align:start position:0% this is something you have to pay you know<00:59:17.480> great<00:59:17.760> attention<00:59:18.119> to<00:59:18.480> right<00:59:19.039> again 00:59:20.029 --> 00:59:20.039 align:start position:0% know great attention to right again 00:59:20.039 --> 00:59:22.309 align:start position:0% know great attention to right again users<00:59:21.039> and 00:59:22.309 --> 00:59:22.319 align:start position:0% users and 00:59:22.319 --> 00:59:24.510 align:start position:0% users and abusers<00:59:23.319> how<00:59:23.520> does<00:59:23.839> this<00:59:24.119> particular 00:59:24.510 --> 00:59:24.520 align:start position:0% abusers how does this particular 00:59:24.520 --> 00:59:26.710 align:start position:0% abusers how does this particular protocol<00:59:25.280> get<00:59:25.559> normally 00:59:26.710 --> 00:59:26.720 align:start position:0% protocol get normally 00:59:26.720 --> 00:59:28.829 align:start position:0% protocol get normally um<00:59:26.880> I<00:59:26.960> mean<00:59:27.119> how<00:59:27.280> does<00:59:27.440> it<00:59:27.640> function<00:59:28.240> normally 00:59:28.829 --> 00:59:28.839 align:start position:0% um I mean how does it function normally 00:59:28.839 --> 00:59:31.750 align:start position:0% um I mean how does it function normally what's<00:59:29.079> the<00:59:29.200> normal<00:59:29.640> behavior<00:59:30.640> but<00:59:30.839> then<00:59:31.599> that 00:59:31.750 --> 00:59:31.760 align:start position:0% what's the normal behavior but then that 00:59:31.760 --> 00:59:33.549 align:start position:0% what's the normal behavior but then that is<00:59:32.119> that<00:59:32.240> is<00:59:32.400> fine<00:59:32.640> we<00:59:32.760> need<00:59:32.880> to<00:59:33.000> build<00:59:33.319> that 00:59:33.549 --> 00:59:33.559 align:start position:0% is that is fine we need to build that 00:59:33.559 --> 00:59:35.789 align:start position:0% is that is fine we need to build that model<00:59:34.400> but<00:59:34.599> what<00:59:34.760> we<00:59:34.839> are<00:59:35.000> looking<00:59:35.240> at<00:59:35.480> is<00:59:35.640> the 00:59:35.789 --> 00:59:35.799 align:start position:0% model but what we are looking at is the 00:59:35.799 --> 00:59:39.950 align:start position:0% model but what we are looking at is the anomaly<00:59:36.559> right<00:59:36.799> how<00:59:37.039> can<00:59:37.920> this<00:59:38.200> go<00:59:38.760> wrong<00:59:39.760> now 00:59:39.950 --> 00:59:39.960 align:start position:0% anomaly right how can this go wrong now 00:59:39.960 --> 00:59:42.309 align:start position:0% anomaly right how can this go wrong now not<00:59:40.160> all<00:59:40.400> anomaly<00:59:40.880> is<00:59:41.079> bad<00:59:41.839> right<00:59:42.079> I<00:59:42.160> mean 00:59:42.309 --> 00:59:42.319 align:start position:0% not all anomaly is bad right I mean 00:59:42.319 --> 00:59:44.589 align:start position:0% not all anomaly is bad right I mean obviously<00:59:42.920> there<00:59:43.039> are<00:59:43.200> so<00:59:43.319> many<00:59:43.559> things<00:59:44.359> U 00:59:44.589 --> 00:59:44.599 align:start position:0% obviously there are so many things U 00:59:44.599 --> 00:59:47.109 align:start position:0% obviously there are so many things U that<00:59:45.200> we<00:59:45.720> don't<00:59:46.000> intend<00:59:46.319> to<00:59:46.520> capture<00:59:46.839> in<00:59:46.960> the 00:59:47.109 --> 00:59:47.119 align:start position:0% that we don't intend to capture in the 00:59:47.119 --> 00:59:50.829 align:start position:0% that we don't intend to capture in the protocol<00:59:48.039> which<00:59:48.200> is<00:59:48.799> fine<00:59:49.799> and<00:59:50.079> not<00:59:50.559> every 00:59:50.829 --> 00:59:50.839 align:start position:0% protocol which is fine and not every 00:59:50.839 --> 00:59:52.549 align:start position:0% protocol which is fine and not every anomaly<00:59:51.240> is<00:59:51.319> a<00:59:51.480> security<00:59:51.880> issue<00:59:52.240> right<00:59:52.359> it's 00:59:52.549 --> 00:59:52.559 align:start position:0% anomaly is a security issue right it's 00:59:52.559 --> 00:59:56.029 align:start position:0% anomaly is a security issue right it's really<00:59:52.799> a<00:59:53.000> small<00:59:53.400> subset<00:59:53.880> of<00:59:54.400> that<00:59:55.400> is<00:59:55.839> what 00:59:56.029 --> 00:59:56.039 align:start position:0% really a small subset of that is what 00:59:56.039 --> 00:59:58.390 align:start position:0% really a small subset of that is what what<00:59:56.160> we<00:59:56.400> call<00:59:56.640> as<00:59:56.839> bugs<00:59:57.559> right<00:59:57.760> but<00:59:57.960> really 00:59:58.390 --> 00:59:58.400 align:start position:0% what we call as bugs right but really 00:59:58.400 --> 01:00:00.549 align:start position:0% what we call as bugs right but really vulnerabilities<00:59:59.400> that<00:59:59.640> really<01:00:00.000> impact<01:00:00.400> the 01:00:00.549 --> 01:00:00.559 align:start position:0% vulnerabilities that really impact the 01:00:00.559 --> 01:00:02.950 align:start position:0% vulnerabilities that really impact the system<01:00:01.440> that<01:00:01.839> affect<01:00:02.160> the<01:00:02.319> assets<01:00:02.799> that 01:00:02.950 --> 01:00:02.960 align:start position:0% system that affect the assets that 01:00:02.960 --> 01:00:06.470 align:start position:0% system that affect the assets that affect<01:00:03.240> the<01:00:03.400> actors<01:00:04.160> drain<01:00:04.520> it<01:00:04.720> out<01:00:05.559> and<01:00:05.839> and 01:00:06.470 --> 01:00:06.480 align:start position:0% affect the actors drain it out and and 01:00:06.480 --> 01:00:09.349 align:start position:0% affect the actors drain it out and and everything<01:00:06.839> in<01:00:06.960> between<01:00:07.839> so<01:00:08.200> this<01:00:08.400> is 01:00:09.349 --> 01:00:09.359 align:start position:0% everything in between so this is 01:00:09.359 --> 01:00:11.470 align:start position:0% everything in between so this is something<01:00:10.359> that 01:00:11.470 --> 01:00:11.480 align:start position:0% something that 01:00:11.480 --> 01:00:14.789 align:start position:0% something that is<01:00:12.480> super<01:00:12.839> critical<01:00:13.680> that<01:00:14.480> all<01:00:14.640> the 01:00:14.789 --> 01:00:14.799 align:start position:0% is super critical that all the 01:00:14.799 --> 01:00:16.510 align:start position:0% is super critical that all the developers<01:00:15.280> should<01:00:15.720> really<01:00:15.960> be<01:00:16.160> thinking 01:00:16.510 --> 01:00:16.520 align:start position:0% developers should really be thinking 01:00:16.520 --> 01:00:20.750 align:start position:0% developers should really be thinking about<01:00:17.319> right<01:00:18.200> how<01:00:18.400> is<01:00:18.599> this<01:00:18.920> going<01:00:19.039> to<01:00:19.240> be<01:00:19.760> used 01:00:20.750 --> 01:00:20.760 align:start position:0% about right how is this going to be used 01:00:20.760 --> 01:00:22.750 align:start position:0% about right how is this going to be used how<01:00:20.960> is<01:00:21.079> this<01:00:21.240> going<01:00:21.359> to<01:00:21.480> be<01:00:21.680> abused<01:00:22.599> the 01:00:22.750 --> 01:00:22.760 align:start position:0% how is this going to be abused the 01:00:22.760 --> 01:00:25.630 align:start position:0% how is this going to be abused the reality<01:00:23.400> is<01:00:23.640> going<01:00:23.760> to<01:00:23.960> be<01:00:24.799> right<01:00:25.200> more<01:00:25.480> than 01:00:25.630 --> 01:00:25.640 align:start position:0% reality is going to be right more than 01:00:25.640 --> 01:00:27.710 align:start position:0% reality is going to be right more than one<01:00:26.000> user<01:00:26.200> I<01:00:26.280> mean<01:00:26.640> the<01:00:26.839> the<01:00:27.079> monkeys<01:00:27.480> on<01:00:27.599> the 01:00:27.710 --> 01:00:27.720 align:start position:0% one user I mean the the monkeys on the 01:00:27.720 --> 01:00:30.430 align:start position:0% one user I mean the the monkeys on the keyboard<01:00:28.480> sort<01:00:28.640> of<01:00:28.760> an<01:00:28.920> analogy<01:00:29.440> right<01:00:29.880> so 01:00:30.430 --> 01:00:30.440 align:start position:0% keyboard sort of an analogy right so 01:00:30.440 --> 01:00:32.190 align:start position:0% keyboard sort of an analogy right so really<01:00:30.760> pay<01:00:30.920> attention<01:00:31.200> to<01:00:31.359> this<01:00:31.520> and<01:00:31.720> this<01:00:31.799> is 01:00:32.190 --> 01:00:32.200 align:start position:0% really pay attention to this and this is 01:00:32.200 --> 01:00:34.109 align:start position:0% really pay attention to this and this is not<01:00:32.440> just<01:00:32.640> the<01:00:32.760> users<01:00:33.280> I<01:00:33.319> mean<01:00:33.520> this<01:00:33.640> could<01:00:33.839> be 01:00:34.109 --> 01:00:34.119 align:start position:0% not just the users I mean this could be 01:00:34.119 --> 01:00:35.910 align:start position:0% not just the users I mean this could be again<01:00:34.359> extending<01:00:34.839> to<01:00:35.039> all<01:00:35.200> the<01:00:35.319> actors<01:00:35.760> right 01:00:35.910 --> 01:00:35.920 align:start position:0% again extending to all the actors right 01:00:35.920 --> 01:00:37.349 align:start position:0% again extending to all the actors right it<01:00:36.000> could<01:00:36.119> be<01:00:36.240> the<01:00:36.359> governance<01:00:36.799> as<01:00:36.960> well 01:00:37.349 --> 01:00:37.359 align:start position:0% it could be the governance as well 01:00:37.359 --> 01:00:39.029 align:start position:0% it could be the governance as well you've<01:00:37.559> seen<01:00:38.039> whole<01:00:38.240> bunch<01:00:38.440> of<01:00:38.599> governance 01:00:39.029 --> 01:00:39.039 align:start position:0% you've seen whole bunch of governance 01:00:39.039 --> 01:00:43.109 align:start position:0% you've seen whole bunch of governance attacks<01:00:39.920> where<01:00:40.960> um<01:00:41.960> it<01:00:42.119> wasn't<01:00:42.640> within<01:00:42.960> the 01:00:43.109 --> 01:00:43.119 align:start position:0% attacks where um it wasn't within the 01:00:43.119 --> 01:00:45.029 align:start position:0% attacks where um it wasn't within the attack<01:00:43.799> the<01:00:43.960> threat<01:00:44.280> model<01:00:44.599> to<01:00:44.760> really 01:00:45.029 --> 01:00:45.039 align:start position:0% attack the threat model to really 01:00:45.039 --> 01:00:47.430 align:start position:0% attack the threat model to really consider<01:00:45.880> something<01:00:46.240> like<01:00:46.400> that<01:00:46.599> happening 01:00:47.430 --> 01:00:47.440 align:start position:0% consider something like that happening 01:00:47.440 --> 01:00:50.510 align:start position:0% consider something like that happening but<01:00:47.799> that<01:00:48.000> is<01:00:48.440> really<01:00:48.720> what<01:00:49.200> happens<01:00:50.200> and<01:00:50.319> for 01:00:50.510 --> 01:00:50.520 align:start position:0% but that is really what happens and for 01:00:50.520 --> 01:00:52.270 align:start position:0% but that is really what happens and for the<01:00:50.680> users<01:00:51.280> right<01:00:51.400> I<01:00:51.480> mean<01:00:51.640> this<01:00:51.799> applies 01:00:52.270 --> 01:00:52.280 align:start position:0% the users right I mean this applies 01:00:52.280 --> 01:00:54.750 align:start position:0% the users right I mean this applies really<01:00:52.480> to<01:00:52.680> every<01:00:52.920> scenario<01:00:53.440> so<01:00:53.960> as<01:00:54.160> as<01:00:54.240> a<01:00:54.400> user 01:00:54.750 --> 01:00:54.760 align:start position:0% really to every scenario so as as a user 01:00:54.760 --> 01:00:56.430 align:start position:0% really to every scenario so as as a user or<01:00:54.920> a<01:00:55.079> security<01:00:55.400> researcher 01:00:56.430 --> 01:00:56.440 align:start position:0% or a security researcher 01:00:56.440 --> 01:00:58.950 align:start position:0% or a security researcher one<01:00:56.760> I<01:00:56.839> mean<01:00:57.039> we<01:00:57.200> could<01:00:57.559> expect<01:00:58.559> uh<01:00:58.720> on<01:00:58.839> the 01:00:58.950 --> 01:00:58.960 align:start position:0% one I mean we could expect uh on the 01:00:58.960 --> 01:01:01.430 align:start position:0% one I mean we could expect uh on the flip<01:00:59.359> side<01:01:00.039> a<01:01:00.280> particular<01:01:00.960> sort<01:01:01.160> of<01:01:01.280> a 01:01:01.430 --> 01:01:01.440 align:start position:0% flip side a particular sort of a 01:01:01.440 --> 01:01:04.990 align:start position:0% flip side a particular sort of a behavior<01:01:02.079> from<01:01:02.760> the<01:01:03.200> developers<01:01:04.200> right<01:01:04.839> but 01:01:04.990 --> 01:01:05.000 align:start position:0% behavior from the developers right but 01:01:05.000 --> 01:01:07.190 align:start position:0% behavior from the developers right but of<01:01:05.160> course<01:01:05.480> we<01:01:05.720> have<01:01:06.119> scams<01:01:06.640> we<01:01:06.760> have<01:01:06.880> Rock 01:01:07.190 --> 01:01:07.200 align:start position:0% of course we have scams we have Rock 01:01:07.200 --> 01:01:09.670 align:start position:0% of course we have scams we have Rock pulls<01:01:07.920> so<01:01:08.359> even<01:01:08.680> there<01:01:08.920> the<01:01:09.039> reality<01:01:09.480> might 01:01:09.670 --> 01:01:09.680 align:start position:0% pulls so even there the reality might 01:01:09.680 --> 01:01:12.069 align:start position:0% pulls so even there the reality might really<01:01:09.960> not<01:01:10.240> match<01:01:10.640> what<01:01:10.799> our<01:01:11.039> expectation<01:01:11.559> is 01:01:12.069 --> 01:01:12.079 align:start position:0% really not match what our expectation is 01:01:12.079 --> 01:01:15.470 align:start position:0% really not match what our expectation is so<01:01:12.240> for<01:01:12.440> all<01:01:12.680> the<01:01:13.160> users<01:01:14.160> developers<01:01:15.039> and<01:01:15.319> the 01:01:15.470 --> 01:01:15.480 align:start position:0% so for all the users developers and the 01:01:15.480 --> 01:01:16.950 align:start position:0% so for all the users developers and the security<01:01:15.880> researchers<01:01:16.400> there's<01:01:16.640> really<01:01:16.839> a 01:01:16.950 --> 01:01:16.960 align:start position:0% security researchers there's really a 01:01:16.960 --> 01:01:18.549 align:start position:0% security researchers there's really a message 01:01:18.549 --> 01:01:18.559 align:start position:0% message 01:01:18.559 --> 01:01:22.029 align:start position:0% message here<01:01:19.559> great<01:01:20.039> so<01:01:20.280> third<01:01:20.559> one<01:01:20.920> third 01:01:22.029 --> 01:01:22.039 align:start position:0% here great so third one third 01:01:22.039 --> 01:01:24.990 align:start position:0% here great so third one third meme<01:01:23.039> challenge<01:01:23.720> assumptions<01:01:24.559> I<01:01:24.640> mean<01:01:24.760> we<01:01:24.880> are 01:01:24.990 --> 01:01:25.000 align:start position:0% meme challenge assumptions I mean we are 01:01:25.000 --> 01:01:26.990 align:start position:0% meme challenge assumptions I mean we are saying<01:01:25.280> this<01:01:25.480> repeatedly<01:01:26.079> in<01:01:26.280> different<01:01:26.880> you 01:01:26.990 --> 01:01:27.000 align:start position:0% saying this repeatedly in different you 01:01:27.000 --> 01:01:28.630 align:start position:0% saying this repeatedly in different you know<01:01:27.160> using<01:01:27.480> different<01:01:27.720> memes<01:01:28.160> different 01:01:28.630 --> 01:01:28.640 align:start position:0% know using different memes different 01:01:28.640 --> 01:01:31.870 align:start position:0% know using different memes different ways<01:01:28.839> of<01:01:29.000> saying<01:01:29.280> it<01:01:30.079> but<01:01:30.480> this<01:01:30.680> is<01:01:31.160> really<01:01:31.640> the 01:01:31.870 --> 01:01:31.880 align:start position:0% ways of saying it but this is really the 01:01:31.880 --> 01:01:33.589 align:start position:0% ways of saying it but this is really the root<01:01:32.359> of<01:01:32.640> all 01:01:33.589 --> 01:01:33.599 align:start position:0% root of all 01:01:33.599 --> 01:01:37.109 align:start position:0% root of all bugs<01:01:34.599> right<01:01:35.039> the<01:01:35.400> assumptions<01:01:36.400> made<01:01:36.760> by<01:01:36.920> the 01:01:37.109 --> 01:01:37.119 align:start position:0% bugs right the assumptions made by the 01:01:37.119 --> 01:01:40.230 align:start position:0% bugs right the assumptions made by the developer<01:01:37.799> about<01:01:38.039> the<01:01:38.280> user<01:01:39.280> the<01:01:39.520> assumptions 01:01:40.230 --> 01:01:40.240 align:start position:0% developer about the user the assumptions 01:01:40.240 --> 01:01:42.710 align:start position:0% developer about the user the assumptions made<01:01:40.599> by<01:01:40.799> the<01:01:40.960> security<01:01:41.440> researcher<01:01:42.440> about 01:01:42.710 --> 01:01:42.720 align:start position:0% made by the security researcher about 01:01:42.720 --> 01:01:45.109 align:start position:0% made by the security researcher about the<01:01:42.880> code<01:01:43.200> base<01:01:43.640> about<01:01:43.839> the<01:01:44.000> developer<01:01:44.960> the 01:01:45.109 --> 01:01:45.119 align:start position:0% the code base about the developer the 01:01:45.119 --> 01:01:47.190 align:start position:0% the code base about the developer the assumptions<01:01:45.760> made<01:01:46.079> by<01:01:46.280> the<01:01:46.440> developer<01:01:47.000> and 01:01:47.190 --> 01:01:47.200 align:start position:0% assumptions made by the developer and 01:01:47.200 --> 01:01:50.109 align:start position:0% assumptions made by the developer and the<01:01:47.359> security<01:01:47.760> researcher<01:01:48.319> about<01:01:48.559> the<01:01:49.119> users 01:01:50.109 --> 01:01:50.119 align:start position:0% the security researcher about the users 01:01:50.119 --> 01:01:52.950 align:start position:0% the security researcher about the users I<01:01:50.200> mean<01:01:50.480> all<01:01:50.799> combinations<01:01:51.559> right<01:01:51.799> so<01:01:52.160> this 01:01:52.950 --> 01:01:52.960 align:start position:0% I mean all combinations right so this 01:01:52.960 --> 01:01:56.390 align:start position:0% I mean all combinations right so this is<01:01:53.960> this<01:01:54.079> is<01:01:54.279> really<01:01:54.480> the<01:01:54.640> root 01:01:56.390 --> 01:01:56.400 align:start position:0% is this is really the root 01:01:56.400 --> 01:01:58.630 align:start position:0% is this is really the root of<01:01:56.920> anything<01:01:57.240> that's<01:01:57.440> wrong<01:01:57.680> with<01:01:57.839> security 01:01:58.630 --> 01:01:58.640 align:start position:0% of anything that's wrong with security 01:01:58.640 --> 01:02:02.390 align:start position:0% of anything that's wrong with security right<01:01:59.160> so<01:01:59.640> question<01:02:01.039> everything<01:02:02.039> as<01:02:02.200> a 01:02:02.390 --> 01:02:02.400 align:start position:0% right so question everything as a 01:02:02.400 --> 01:02:04.950 align:start position:0% right so question everything as a developer 01:02:04.950 --> 01:02:04.960 align:start position:0% developer 01:02:04.960 --> 01:02:08.190 align:start position:0% developer question<01:02:05.960> question<01:02:06.680> all<01:02:06.920> possible<01:02:07.279> scenarios 01:02:08.190 --> 01:02:08.200 align:start position:0% question question all possible scenarios 01:02:08.200 --> 01:02:09.630 align:start position:0% question question all possible scenarios all<01:02:08.359> the<01:02:08.480> different<01:02:08.799> ways<01:02:09.079> that<01:02:09.319> you<01:02:09.440> know 01:02:09.630 --> 01:02:09.640 align:start position:0% all the different ways that you know 01:02:09.640 --> 01:02:11.190 align:start position:0% all the different ways that you know maybe<01:02:09.880> you<01:02:10.000> have<01:02:10.119> a<01:02:10.279> design<01:02:10.640> maybe<01:02:10.839> you<01:02:10.920> have<01:02:11.039> a 01:02:11.190 --> 01:02:11.200 align:start position:0% maybe you have a design maybe you have a 01:02:11.200 --> 01:02:14.349 align:start position:0% maybe you have a design maybe you have a spec<01:02:11.680> from<01:02:12.400> uh<01:02:12.520> from<01:02:12.680> your<01:02:12.880> team<01:02:13.720> but<01:02:14.039> how<01:02:14.160> can 01:02:14.349 --> 01:02:14.359 align:start position:0% spec from uh from your team but how can 01:02:14.359 --> 01:02:15.750 align:start position:0% spec from uh from your team but how can this<01:02:14.520> be<01:02:14.640> used<01:02:15.119> right<01:02:15.240> how<01:02:15.359> can<01:02:15.480> this<01:02:15.599> be 01:02:15.750 --> 01:02:15.760 align:start position:0% this be used right how can this be 01:02:15.760 --> 01:02:17.510 align:start position:0% this be used right how can this be abused<01:02:16.240> question<01:02:16.720> everything<01:02:17.279> every 01:02:17.510 --> 01:02:17.520 align:start position:0% abused question everything every 01:02:17.520 --> 01:02:19.470 align:start position:0% abused question everything every scenario<01:02:18.039> all<01:02:18.200> that<01:02:18.359> has<01:02:18.480> to<01:02:18.559> be<01:02:18.720> captured 01:02:19.470 --> 01:02:19.480 align:start position:0% scenario all that has to be captured 01:02:19.480 --> 01:02:22.630 align:start position:0% scenario all that has to be captured within<01:02:19.880> your<01:02:20.440> model<01:02:21.440> and<01:02:21.599> as<01:02:21.720> a<01:02:21.880> security 01:02:22.630 --> 01:02:22.640 align:start position:0% within your model and as a security 01:02:22.640 --> 01:02:25.390 align:start position:0% within your model and as a security researcher<01:02:23.640> again<01:02:24.000> question<01:02:24.520> everything 01:02:25.390 --> 01:02:25.400 align:start position:0% researcher again question everything 01:02:25.400 --> 01:02:28.190 align:start position:0% researcher again question everything right<01:02:25.559> I<01:02:25.640> mean<01:02:26.039> ask<01:02:26.440> Nat<01:02:26.799> mentioned<01:02:27.640> uh<01:02:27.760> tincho 01:02:28.190 --> 01:02:28.200 align:start position:0% right I mean ask Nat mentioned uh tincho 01:02:28.200 --> 01:02:30.470 align:start position:0% right I mean ask Nat mentioned uh tincho as<01:02:28.359> well<01:02:28.839> about 01:02:30.470 --> 01:02:30.480 align:start position:0% as well about 01:02:30.480 --> 01:02:33.470 align:start position:0% as well about questioning<01:02:31.480> everything<01:02:32.279> to<01:02:32.559> yourself<01:02:33.279> and 01:02:33.470 --> 01:02:33.480 align:start position:0% questioning everything to yourself and 01:02:33.480 --> 01:02:35.430 align:start position:0% questioning everything to yourself and as<01:02:33.599> much<01:02:33.880> as<01:02:34.000> you<01:02:34.160> can<01:02:34.440> to<01:02:34.720> the<01:02:34.880> protocol<01:02:35.319> to 01:02:35.430 --> 01:02:35.440 align:start position:0% as much as you can to the protocol to 01:02:35.440 --> 01:02:38.710 align:start position:0% as much as you can to the protocol to the<01:02:35.559> developer<01:02:35.960> team<01:02:36.200> as<01:02:36.480> well<01:02:37.480> right<01:02:38.279> because 01:02:38.710 --> 01:02:38.720 align:start position:0% the developer team as well right because 01:02:38.720 --> 01:02:40.630 align:start position:0% the developer team as well right because if<01:02:38.880> we<01:02:39.079> do<01:02:39.279> not<01:02:39.799> understand<01:02:40.039> as<01:02:40.119> a<01:02:40.279> security 01:02:40.630 --> 01:02:40.640 align:start position:0% if we do not understand as a security 01:02:40.640 --> 01:02:42.510 align:start position:0% if we do not understand as a security researcher<01:02:41.079> if<01:02:41.200> you<01:02:41.319> do<01:02:41.440> not<01:02:41.839> understand<01:02:42.279> what 01:02:42.510 --> 01:02:42.520 align:start position:0% researcher if you do not understand what 01:02:42.520 --> 01:02:44.710 align:start position:0% researcher if you do not understand what this<01:02:42.680> is<01:02:42.920> supposed<01:02:43.240> to<01:02:43.400> do<01:02:44.200> how<01:02:44.359> is<01:02:44.480> this<01:02:44.640> going 01:02:44.710 --> 01:02:44.720 align:start position:0% this is supposed to do how is this going 01:02:44.720 --> 01:02:46.870 align:start position:0% this is supposed to do how is this going to<01:02:44.839> be<01:02:45.000> used<01:02:45.720> we<01:02:45.920> certainly<01:02:46.319> cannot 01:02:46.870 --> 01:02:46.880 align:start position:0% to be used we certainly cannot 01:02:46.880 --> 01:02:47.710 align:start position:0% to be used we certainly cannot understand<01:02:47.039> how<01:02:47.200> this<01:02:47.319> is<01:02:47.400> going<01:02:47.480> to<01:02:47.599> be 01:02:47.710 --> 01:02:47.720 align:start position:0% understand how this is going to be 01:02:47.720 --> 01:02:50.710 align:start position:0% understand how this is going to be abused<01:02:48.720> right<01:02:49.319> so<01:02:49.559> as<01:02:49.760> much<01:02:50.000> as<01:02:50.200> possible 01:02:50.710 --> 01:02:50.720 align:start position:0% abused right so as much as possible 01:02:50.720 --> 01:02:52.309 align:start position:0% abused right so as much as possible obviously<01:02:51.279> practically<01:02:51.760> there's<01:02:52.000> obviously 01:02:52.309 --> 01:02:52.319 align:start position:0% obviously practically there's obviously 01:02:52.319 --> 01:02:54.589 align:start position:0% obviously practically there's obviously a<01:02:52.440> limit<01:02:52.760> it's<01:02:52.920> all<01:02:53.160> time<01:02:53.400> boxed<01:02:54.079> so<01:02:54.279> figure 01:02:54.589 --> 01:02:54.599 align:start position:0% a limit it's all time boxed so figure 01:02:54.599 --> 01:02:56.870 align:start position:0% a limit it's all time boxed so figure out<01:02:54.960> you<01:02:55.079> know<01:02:55.400> and<01:02:55.599> this 01:02:56.870 --> 01:02:56.880 align:start position:0% out you know and this 01:02:56.880 --> 01:02:59.470 align:start position:0% out you know and this uh<01:02:57.039> depends<01:02:57.440> on<01:02:58.279> the<01:02:58.480> model<01:02:58.880> as<01:02:59.000> well<01:02:59.240> so<01:02:59.400> if 01:02:59.470 --> 01:02:59.480 align:start position:0% uh depends on the model as well so if 01:02:59.480 --> 01:03:01.670 align:start position:0% uh depends on the model as well so if you're<01:02:59.839> doing<01:03:00.079> a<01:03:00.200> collaborative<01:03:00.760> review<01:03:01.559> you 01:03:01.670 --> 01:03:01.680 align:start position:0% you're doing a collaborative review you 01:03:01.680 --> 01:03:03.789 align:start position:0% you're doing a collaborative review you know<01:03:01.839> you<01:03:02.079> have<01:03:02.799> quite<01:03:02.960> a<01:03:03.039> bit<01:03:03.160> of<01:03:03.279> leeway<01:03:03.680> in 01:03:03.789 --> 01:03:03.799 align:start position:0% know you have quite a bit of leeway in 01:03:03.799 --> 01:03:05.230 align:start position:0% know you have quite a bit of leeway in terms<01:03:04.039> of<01:03:04.200> asking<01:03:04.520> questions<01:03:04.960> if<01:03:05.039> you're 01:03:05.230 --> 01:03:05.240 align:start position:0% terms of asking questions if you're 01:03:05.240 --> 01:03:07.349 align:start position:0% terms of asking questions if you're doing<01:03:05.440> a<01:03:05.599> contest<01:03:06.119> maybe<01:03:06.359> not<01:03:06.559> as<01:03:06.720> much<01:03:07.240> if 01:03:07.349 --> 01:03:07.359 align:start position:0% doing a contest maybe not as much if 01:03:07.359 --> 01:03:09.269 align:start position:0% doing a contest maybe not as much if you're<01:03:07.559> doing<01:03:07.760> a<01:03:07.920> bug<01:03:08.160> mounty<01:03:08.799> again<01:03:09.079> very 01:03:09.269 --> 01:03:09.279 align:start position:0% you're doing a bug mounty again very 01:03:09.279 --> 01:03:12.309 align:start position:0% you're doing a bug mounty again very limited<01:03:09.720> ways<01:03:10.000> of<01:03:10.400> uh<01:03:10.520> sort<01:03:10.720> of<01:03:11.319> questioning 01:03:12.309 --> 01:03:12.319 align:start position:0% limited ways of uh sort of questioning 01:03:12.319 --> 01:03:16.109 align:start position:0% limited ways of uh sort of questioning the<01:03:12.559> protocol<01:03:13.520> about<01:03:13.960> every<01:03:14.920> U<01:03:15.200> knit<01:03:15.680> and<01:03:16.000> you 01:03:16.109 --> 01:03:16.119 align:start position:0% the protocol about every U knit and you 01:03:16.119 --> 01:03:17.990 align:start position:0% the protocol about every U knit and you know<01:03:16.359> Nitty<01:03:16.760> Gritty<01:03:17.119> detail<01:03:17.520> that<01:03:17.680> you<01:03:17.799> may 01:03:17.990 --> 01:03:18.000 align:start position:0% know Nitty Gritty detail that you may 01:03:18.000 --> 01:03:20.390 align:start position:0% know Nitty Gritty detail that you may want<01:03:18.160> to<01:03:18.400> know<01:03:18.640> about<01:03:19.000> right<01:03:19.720> but<01:03:19.960> try<01:03:20.160> to<01:03:20.279> get 01:03:20.390 --> 01:03:20.400 align:start position:0% want to know about right but try to get 01:03:20.400 --> 01:03:22.549 align:start position:0% want to know about right but try to get an<01:03:20.520> idea<01:03:20.760> of<01:03:20.920> who<01:03:21.200> again<01:03:21.440> actors<01:03:21.920> actions 01:03:22.549 --> 01:03:22.559 align:start position:0% an idea of who again actors actions 01:03:22.559 --> 01:03:25.510 align:start position:0% an idea of who again actors actions assets<01:03:23.039> who<01:03:23.240> is<01:03:23.319> it<01:03:24.119> what<01:03:24.279> is<01:03:24.400> it<01:03:24.559> being<01:03:24.799> done 01:03:25.510 --> 01:03:25.520 align:start position:0% assets who is it what is it being done 01:03:25.520 --> 01:03:27.589 align:start position:0% assets who is it what is it being done when<01:03:25.799> when<01:03:26.119> and<01:03:26.400> where<01:03:27.039> right<01:03:27.160> so<01:03:27.359> that<01:03:27.440> is 01:03:27.589 --> 01:03:27.599 align:start position:0% when when and where right so that is 01:03:27.599 --> 01:03:32.069 align:start position:0% when when and where right so that is really<01:03:27.839> critical<01:03:28.400> question 01:03:32.069 --> 01:03:32.079 align:start position:0% 01:03:32.079 --> 01:03:34.510 align:start position:0% everything<01:03:33.079> and<01:03:33.359> security<01:03:33.880> is<01:03:34.000> nothing 01:03:34.510 --> 01:03:34.520 align:start position:0% everything and security is nothing 01:03:34.520 --> 01:03:36.710 align:start position:0% everything and security is nothing without<01:03:35.000> discovering<01:03:35.319> the<01:03:35.440> misuse<01:03:36.000> scenarios 01:03:36.710 --> 01:03:36.720 align:start position:0% without discovering the misuse scenarios 01:03:36.720 --> 01:03:40.549 align:start position:0% without discovering the misuse scenarios right<01:03:37.559> again<01:03:38.039> repeating<01:03:38.720> myself<01:03:39.720> use<01:03:40.279> and 01:03:40.549 --> 01:03:40.559 align:start position:0% right again repeating myself use and 01:03:40.559 --> 01:03:44.390 align:start position:0% right again repeating myself use and misuse<01:03:41.839> critical<01:03:42.839> and<01:03:43.119> abuse<01:03:43.520> is<01:03:43.720> really<01:03:44.160> a 01:03:44.390 --> 01:03:44.400 align:start position:0% misuse critical and abuse is really a 01:03:44.400 --> 01:03:47.430 align:start position:0% misuse critical and abuse is really a subset<01:03:45.079> of<01:03:45.480> misuse<01:03:46.160> so<01:03:46.319> figuring<01:03:46.760> out<01:03:47.279> just 01:03:47.430 --> 01:03:47.440 align:start position:0% subset of misuse so figuring out just 01:03:47.440 --> 01:03:48.990 align:start position:0% subset of misuse so figuring out just the<01:03:47.599> various<01:03:47.880> misuse<01:03:48.319> things<01:03:48.520> is<01:03:48.680> not<01:03:48.880> going 01:03:48.990 --> 01:03:49.000 align:start position:0% the various misuse things is not going 01:03:49.000 --> 01:03:51.510 align:start position:0% the various misuse things is not going to<01:03:49.680> um<01:03:50.039> you<01:03:50.160> know<01:03:50.319> do<01:03:50.599> much<01:03:50.880> as<01:03:51.000> a<01:03:51.119> security 01:03:51.510 --> 01:03:51.520 align:start position:0% to um you know do much as a security 01:03:51.520 --> 01:03:52.750 align:start position:0% to um you know do much as a security researcher<01:03:51.960> you<01:03:52.079> have<01:03:52.160> to<01:03:52.279> figure<01:03:52.480> out<01:03:52.640> the 01:03:52.750 --> 01:03:52.760 align:start position:0% researcher you have to figure out the 01:03:52.760 --> 01:03:54.870 align:start position:0% researcher you have to figure out the abuse<01:03:53.160> cases<01:03:53.760> and<01:03:53.880> the<01:03:54.000> abuse<01:03:54.319> cases<01:03:54.640> are 01:03:54.870 --> 01:03:54.880 align:start position:0% abuse cases and the abuse cases are 01:03:54.880 --> 01:03:56.670 align:start position:0% abuse cases and the abuse cases are really<01:03:55.079> the<01:03:55.200> vulnerability<01:03:55.880> ities<01:03:56.400> we'll 01:03:56.670 --> 01:03:56.680 align:start position:0% really the vulnerability ities we'll 01:03:56.680 --> 01:03:58.750 align:start position:0% really the vulnerability ities we'll talk<01:03:56.839> about<01:03:57.079> the<01:03:57.200> impact<01:03:57.520> in<01:03:57.599> a<01:03:57.799> bit<01:03:58.559> and 01:03:58.750 --> 01:03:58.760 align:start position:0% talk about the impact in a bit and 01:03:58.760 --> 01:04:00.750 align:start position:0% talk about the impact in a bit and really<01:03:59.039> to<01:03:59.400> map<01:03:59.680> out<01:04:00.079> what<01:04:00.279> the<01:04:00.480> attack 01:04:00.750 --> 01:04:00.760 align:start position:0% really to map out what the attack 01:04:00.760 --> 01:04:04.670 align:start position:0% really to map out what the attack surface<01:04:01.559> is<01:04:02.559> right<01:04:03.039> so<01:04:03.200> for<01:04:03.319> a<01:04:03.480> developer<01:04:04.440> in 01:04:04.670 --> 01:04:04.680 align:start position:0% surface is right so for a developer in 01:04:04.680 --> 01:04:07.990 align:start position:0% surface is right so for a developer in this<01:04:04.960> case<01:04:05.319> it<01:04:05.480> is<01:04:05.799> really<01:04:06.359> to<01:04:07.359> reduce<01:04:07.839> the 01:04:07.990 --> 01:04:08.000 align:start position:0% this case it is really to reduce the 01:04:08.000 --> 01:04:08.950 align:start position:0% this case it is really to reduce the attack 01:04:08.950 --> 01:04:08.960 align:start position:0% attack 01:04:08.960 --> 01:04:12.870 align:start position:0% attack surface<01:04:09.960> of<01:04:10.200> your<01:04:10.559> protocol<01:04:11.559> of<01:04:11.799> your<01:04:12.000> code 01:04:12.870 --> 01:04:12.880 align:start position:0% surface of your protocol of your code 01:04:12.880 --> 01:04:16.990 align:start position:0% surface of your protocol of your code base<01:04:13.880> reduce<01:04:14.359> it<01:04:14.760> so<01:04:15.240> that<01:04:16.240> I<01:04:16.319> mean<01:04:16.520> one<01:04:16.720> way<01:04:16.839> to 01:04:16.990 --> 01:04:17.000 align:start position:0% base reduce it so that I mean one way to 01:04:17.000 --> 01:04:20.109 align:start position:0% base reduce it so that I mean one way to reduce<01:04:17.319> it<01:04:17.480> is<01:04:17.559> to<01:04:17.720> reduce<01:04:18.039> the<01:04:18.359> complexity 01:04:20.109 --> 01:04:20.119 align:start position:0% reduce it is to reduce the complexity 01:04:20.119 --> 01:04:23.630 align:start position:0% reduce it is to reduce the complexity right<01:04:21.119> reduce<01:04:21.559> the<01:04:21.720> number<01:04:21.960> of<01:04:22.720> U<01:04:23.279> actions 01:04:23.630 --> 01:04:23.640 align:start position:0% right reduce the number of U actions 01:04:23.640 --> 01:04:25.069 align:start position:0% right reduce the number of U actions that<01:04:23.799> can<01:04:23.920> be<01:04:24.079> done<01:04:24.319> figure<01:04:24.599> out<01:04:24.799> what<01:04:24.920> is 01:04:25.069 --> 01:04:25.079 align:start position:0% that can be done figure out what is 01:04:25.079 --> 01:04:26.269 align:start position:0% that can be done figure out what is really<01:04:25.319> critical 01:04:26.269 --> 01:04:26.279 align:start position:0% really critical 01:04:26.279 --> 01:04:28.029 align:start position:0% really critical there<01:04:26.400> is<01:04:26.559> a<01:04:26.680> concept<01:04:27.000> called<01:04:27.200> guarded<01:04:27.520> launch 01:04:28.029 --> 01:04:28.039 align:start position:0% there is a concept called guarded launch 01:04:28.039 --> 01:04:30.390 align:start position:0% there is a concept called guarded launch you<01:04:28.160> know<01:04:28.440> maybe<01:04:28.680> you<01:04:28.760> can<01:04:28.960> do<01:04:29.079> it<01:04:29.200> in 01:04:30.390 --> 01:04:30.400 align:start position:0% you know maybe you can do it in 01:04:30.400 --> 01:04:33.349 align:start position:0% you know maybe you can do it in steps<01:04:31.400> various<01:04:31.760> ways<01:04:31.960> to<01:04:32.640> reduce<01:04:33.079> attack 01:04:33.349 --> 01:04:33.359 align:start position:0% steps various ways to reduce attack 01:04:33.359 --> 01:04:36.430 align:start position:0% steps various ways to reduce attack surface<01:04:34.000> because<01:04:34.279> if<01:04:34.400> you<01:04:34.559> reduce<01:04:35.000> it<01:04:35.599> then 01:04:36.430 --> 01:04:36.440 align:start position:0% surface because if you reduce it then 01:04:36.440 --> 01:04:39.630 align:start position:0% surface because if you reduce it then the<01:04:36.640> potential<01:04:37.079> for<01:04:37.319> abuse<01:04:37.720> is<01:04:37.960> much<01:04:38.680> lower 01:04:39.630 --> 01:04:39.640 align:start position:0% the potential for abuse is much lower 01:04:39.640 --> 01:04:41.190 align:start position:0% the potential for abuse is much lower right<01:04:39.799> so<01:04:39.960> the<01:04:40.119> probability 01:04:41.190 --> 01:04:41.200 align:start position:0% right so the probability 01:04:41.200 --> 01:04:43.710 align:start position:0% right so the probability goes 01:04:43.710 --> 01:04:43.720 align:start position:0% goes 01:04:43.720 --> 01:04:47.069 align:start position:0% goes down<01:04:44.720> and<01:04:44.880> your<01:04:45.119> actors<01:04:45.520> and<01:04:46.000> attackers<01:04:47.000> I 01:04:47.069 --> 01:04:47.079 align:start position:0% down and your actors and attackers I 01:04:47.079 --> 01:04:48.990 align:start position:0% down and your actors and attackers I mean<01:04:47.319> we<01:04:47.680> we<01:04:47.799> are<01:04:47.920> in<01:04:48.039> the<01:04:48.200> blockchain 01:04:48.990 --> 01:04:49.000 align:start position:0% mean we we are in the blockchain 01:04:49.000 --> 01:04:51.349 align:start position:0% mean we we are in the blockchain environment<01:04:49.599> right<01:04:49.920> so<01:04:50.079> in<01:04:50.279> this<01:04:50.520> case<01:04:51.079> we 01:04:51.349 --> 01:04:51.359 align:start position:0% environment right so in this case we 01:04:51.359 --> 01:04:54.630 align:start position:0% environment right so in this case we really<01:04:51.640> looking<01:04:52.039> at<01:04:52.760> sort<01:04:53.000> of<01:04:53.720> um<01:04:54.039> the<01:04:54.200> worst 01:04:54.630 --> 01:04:54.640 align:start position:0% really looking at sort of um the worst 01:04:54.640 --> 01:04:59.589 align:start position:0% really looking at sort of um the worst case<01:04:54.799> scenarios<01:04:56.119> from<01:04:56.279> an<01:04:56.880> adversarial<01:04:57.880> um 01:04:59.589 --> 01:04:59.599 align:start position:0% case scenarios from an adversarial um 01:04:59.599 --> 01:05:01.990 align:start position:0% case scenarios from an adversarial um mindset<01:05:00.599> anything<01:05:00.920> and<01:05:01.160> everything<01:05:01.640> can<01:05:01.839> be 01:05:01.990 --> 01:05:02.000 align:start position:0% mindset anything and everything can be 01:05:02.000 --> 01:05:03.870 align:start position:0% mindset anything and everything can be attacked<01:05:02.400> and<01:05:02.599> will<01:05:02.799> be<01:05:02.960> attacked<01:05:03.480> and<01:05:03.720> by 01:05:03.870 --> 01:05:03.880 align:start position:0% attacked and will be attacked and by 01:05:03.880 --> 01:05:07.710 align:start position:0% attacked and will be attacked and by anyone<01:05:04.760> who<01:05:04.920> is<01:05:05.039> a<01:05:05.160> part<01:05:05.319> of<01:05:05.440> the<01:05:05.599> system<01:05:06.599> so<01:05:07.440> we 01:05:07.710 --> 01:05:07.720 align:start position:0% anyone who is a part of the system so we 01:05:07.720 --> 01:05:11.150 align:start position:0% anyone who is a part of the system so we really<01:05:08.000> looking<01:05:08.319> at<01:05:08.680> a<01:05:09.119> very<01:05:10.039> uh<01:05:10.240> High<01:05:10.520> bar 01:05:11.150 --> 01:05:11.160 align:start position:0% really looking at a very uh High bar 01:05:11.160 --> 01:05:13.109 align:start position:0% really looking at a very uh High bar right<01:05:11.359> when<01:05:11.480> it<01:05:11.680> comes<01:05:11.920> to<01:05:12.319> who<01:05:12.520> that<01:05:12.720> attacker 01:05:13.109 --> 01:05:13.119 align:start position:0% right when it comes to who that attacker 01:05:13.119 --> 01:05:15.589 align:start position:0% right when it comes to who that attacker is<01:05:13.559> unlike<01:05:13.920> the<01:05:14.000> web<01:05:14.200> 2<01:05:14.400> or<01:05:14.520> the<01:05:14.599> web<01:05:14.799> 1<01:05:15.039> World 01:05:15.589 --> 01:05:15.599 align:start position:0% is unlike the web 2 or the web 1 World 01:05:15.599 --> 01:05:17.710 align:start position:0% is unlike the web 2 or the web 1 World we<01:05:15.760> do<01:05:15.920> not<01:05:16.200> have<01:05:16.359> an<01:05:16.760> good<01:05:16.960> idea<01:05:17.279> of<01:05:17.400> who<01:05:17.559> the 01:05:17.710 --> 01:05:17.720 align:start position:0% we do not have an good idea of who the 01:05:17.720 --> 01:05:20.029 align:start position:0% we do not have an good idea of who the Insiders<01:05:18.240> are<01:05:18.480> and<01:05:18.640> who<01:05:18.799> The<01:05:18.920> Outsiders<01:05:19.440> are 01:05:20.029 --> 01:05:20.039 align:start position:0% Insiders are and who The Outsiders are 01:05:20.039 --> 01:05:22.670 align:start position:0% Insiders are and who The Outsiders are who<01:05:20.240> what<01:05:20.359> is<01:05:20.440> a<01:05:20.640> characterization<01:05:21.480> of<01:05:22.160> uh<01:05:22.359> the 01:05:22.670 --> 01:05:22.680 align:start position:0% who what is a characterization of uh the 01:05:22.680 --> 01:05:25.109 align:start position:0% who what is a characterization of uh the the<01:05:22.960> normal<01:05:23.319> users<01:05:23.680> of<01:05:23.839> my<01:05:24.000> system<01:05:24.520> so<01:05:24.720> it's<01:05:24.839> a 01:05:25.109 --> 01:05:25.119 align:start position:0% the normal users of my system so it's a 01:05:25.119 --> 01:05:28.549 align:start position:0% the normal users of my system so it's a really<01:05:25.720> adversarial<01:05:26.720> mindset<01:05:27.720> um<01:05:28.240> that 01:05:28.549 --> 01:05:28.559 align:start position:0% really adversarial mindset um that 01:05:28.559 --> 01:05:30.029 align:start position:0% really adversarial mindset um that should<01:05:28.760> be<01:05:28.960> kept<01:05:29.160> in<01:05:29.319> mind<01:05:29.680> when<01:05:29.799> you're 01:05:30.029 --> 01:05:30.039 align:start position:0% should be kept in mind when you're 01:05:30.039 --> 01:05:33.349 align:start position:0% should be kept in mind when you're designing<01:05:30.760> coding<01:05:31.440> and 01:05:33.349 --> 01:05:33.359 align:start position:0% designing coding and 01:05:33.359 --> 01:05:36.349 align:start position:0% designing coding and reviewing<01:05:34.359> great<01:05:34.760> so<01:05:35.200> um<01:05:35.480> severity<01:05:35.960> tincho 01:05:36.349 --> 01:05:36.359 align:start position:0% reviewing great so um severity tincho 01:05:36.359 --> 01:05:38.789 align:start position:0% reviewing great so um severity tincho talked<01:05:36.599> about<01:05:36.839> this<01:05:37.000> in<01:05:37.160> the<01:05:37.599> context<01:05:38.079> of 01:05:38.789 --> 01:05:38.799 align:start position:0% talked about this in the context of 01:05:38.799 --> 01:05:42.069 align:start position:0% talked about this in the context of bounties<01:05:39.400> and<01:05:39.720> and<01:05:40.119> uh 01:05:42.069 --> 01:05:42.079 align:start position:0% bounties and and uh 01:05:42.079 --> 01:05:44.230 align:start position:0% bounties and and uh contest<01:05:43.079> this<01:05:43.160> is<01:05:43.359> probably<01:05:43.599> more<01:05:43.799> relevant 01:05:44.230 --> 01:05:44.240 align:start position:0% contest this is probably more relevant 01:05:44.240 --> 01:05:47.630 align:start position:0% contest this is probably more relevant for<01:05:44.520> the<01:05:44.680> security<01:05:45.079> researchers<01:05:45.799> right<01:05:46.640> if<01:05:47.440> we 01:05:47.630 --> 01:05:47.640 align:start position:0% for the security researchers right if we 01:05:47.640 --> 01:05:49.670 align:start position:0% for the security researchers right if we do<01:05:47.920> not<01:05:48.240> I<01:05:48.279> mean<01:05:48.520> we<01:05:48.720> we<01:05:48.880> great<01:05:49.119> we<01:05:49.240> found<01:05:49.480> a 01:05:49.670 --> 01:05:49.680 align:start position:0% do not I mean we we great we found a 01:05:49.680 --> 01:05:52.150 align:start position:0% do not I mean we we great we found a misuse<01:05:50.079> abuse<01:05:50.359> scenario<01:05:50.960> but<01:05:51.119> if<01:05:51.240> we 01:05:52.150 --> 01:05:52.160 align:start position:0% misuse abuse scenario but if we 01:05:52.160 --> 01:05:55.670 align:start position:0% misuse abuse scenario but if we cannot<01:05:53.160> determine<01:05:54.079> and<01:05:54.440> communicate<01:05:55.400> like 01:05:55.670 --> 01:05:55.680 align:start position:0% cannot determine and communicate like 01:05:55.680 --> 01:05:59.230 align:start position:0% cannot determine and communicate like Ino<01:05:56.119> said<01:05:56.880> what<01:05:57.079> the<01:05:57.319> impact<01:05:57.880> is<01:05:58.720> then<01:05:58.880> it's<01:05:59.079> of 01:05:59.230 --> 01:05:59.240 align:start position:0% Ino said what the impact is then it's of 01:05:59.240 --> 01:06:01.029 align:start position:0% Ino said what the impact is then it's of no<01:05:59.440> use<01:05:59.920> right<01:06:00.119> I<01:06:00.200> mean<01:06:00.400> it's<01:06:00.599> probably<01:06:00.920> going 01:06:01.029 --> 01:06:01.039 align:start position:0% no use right I mean it's probably going 01:06:01.039 --> 01:06:02.549 align:start position:0% no use right I mean it's probably going to<01:06:01.160> be<01:06:01.279> like<01:06:01.400> an<01:06:01.520> informational<01:06:02.039> finding<01:06:02.440> or 01:06:02.549 --> 01:06:02.559 align:start position:0% to be like an informational finding or 01:06:02.559 --> 01:06:05.069 align:start position:0% to be like an informational finding or maybe<01:06:02.760> a<01:06:02.839> low<01:06:03.039> severity<01:06:03.440> one<01:06:03.760> but<01:06:03.920> not<01:06:04.119> much 01:06:05.069 --> 01:06:05.079 align:start position:0% maybe a low severity one but not much 01:06:05.079 --> 01:06:08.829 align:start position:0% maybe a low severity one but not much but<01:06:06.079> quantifying<01:06:06.760> that<01:06:07.000> is<01:06:07.240> super<01:06:07.839> critical 01:06:08.829 --> 01:06:08.839 align:start position:0% but quantifying that is super critical 01:06:08.839 --> 01:06:11.150 align:start position:0% but quantifying that is super critical and<01:06:09.079> the<01:06:09.319> way<01:06:10.319> the<01:06:10.440> sort<01:06:10.640> of<01:06:10.760> the<01:06:10.839> rule<01:06:11.039> of 01:06:11.150 --> 01:06:11.160 align:start position:0% and the way the sort of the rule of 01:06:11.160 --> 01:06:14.230 align:start position:0% and the way the sort of the rule of thumb<01:06:11.480> is<01:06:11.640> to<01:06:12.000> see 01:06:14.230 --> 01:06:14.240 align:start position:0% thumb is to see 01:06:14.240 --> 01:06:17.789 align:start position:0% thumb is to see evaluate<01:06:15.240> the<01:06:15.720> assets<01:06:16.720> are<01:06:16.920> they<01:06:17.079> being<01:06:17.359> lost 01:06:17.789 --> 01:06:17.799 align:start position:0% evaluate the assets are they being lost 01:06:17.799 --> 01:06:21.150 align:start position:0% evaluate the assets are they being lost are<01:06:17.960> they<01:06:18.119> being<01:06:18.640> locked<01:06:19.640> is<01:06:19.720> it<01:06:20.119> temporary<01:06:21.039> is 01:06:21.150 --> 01:06:21.160 align:start position:0% are they being locked is it temporary is 01:06:21.160 --> 01:06:23.510 align:start position:0% are they being locked is it temporary is it 01:06:23.510 --> 01:06:23.520 align:start position:0% it 01:06:23.520 --> 01:06:26.390 align:start position:0% it oops<01:06:24.520> is<01:06:24.640> it<01:06:25.000> uh<01:06:25.200> permanent 01:06:26.390 --> 01:06:26.400 align:start position:0% oops is it uh permanent 01:06:26.400 --> 01:06:28.549 align:start position:0% oops is it uh permanent is<01:06:26.520> it<01:06:26.880> does<01:06:27.000> it<01:06:27.200> apply<01:06:27.480> to<01:06:27.680> all<01:06:27.880> the<01:06:28.079> assets<01:06:28.440> or 01:06:28.549 --> 01:06:28.559 align:start position:0% is it does it apply to all the assets or 01:06:28.559 --> 01:06:30.630 align:start position:0% is it does it apply to all the assets or is<01:06:28.680> it<01:06:28.799> only<01:06:29.000> a<01:06:29.079> few<01:06:29.279> of<01:06:29.400> the<01:06:29.559> assets<01:06:30.359> is<01:06:30.480> it 01:06:30.630 --> 01:06:30.640 align:start position:0% is it only a few of the assets is it 01:06:30.640 --> 01:06:32.549 align:start position:0% is it only a few of the assets is it only<01:06:30.839> the<01:06:30.960> fees<01:06:31.279> or<01:06:31.440> is<01:06:31.559> it<01:06:31.680> the<01:06:31.799> user<01:06:32.160> assets 01:06:32.549 --> 01:06:32.559 align:start position:0% only the fees or is it the user assets 01:06:32.559 --> 01:06:35.750 align:start position:0% only the fees or is it the user assets is<01:06:32.680> it<01:06:32.839> you<01:06:32.960> know<01:06:33.079> can<01:06:33.240> they<01:06:33.400> impact<01:06:34.039> assets<01:06:34.760> of 01:06:35.750 --> 01:06:35.760 align:start position:0% is it you know can they impact assets of 01:06:35.760 --> 01:06:38.630 align:start position:0% is it you know can they impact assets of I<01:06:35.839> mean<01:06:36.359> assets<01:06:36.640> that<01:06:36.839> they<01:06:37.039> own<01:06:38.039> or<01:06:38.279> can<01:06:38.440> they 01:06:38.630 --> 01:06:38.640 align:start position:0% I mean assets that they own or can they 01:06:38.640 --> 01:06:40.390 align:start position:0% I mean assets that they own or can they impact<01:06:39.039> assets<01:06:39.279> of<01:06:39.440> all<01:06:39.599> users<01:06:40.039> there<01:06:40.119> are<01:06:40.279> so 01:06:40.390 --> 01:06:40.400 align:start position:0% impact assets of all users there are so 01:06:40.400 --> 01:06:42.910 align:start position:0% impact assets of all users there are so many<01:06:40.599> ways<01:06:40.839> to<01:06:41.079> sort<01:06:41.279> of<01:06:41.640> slice<01:06:42.000> and<01:06:42.200> dice<01:06:42.559> this 01:06:42.910 --> 01:06:42.920 align:start position:0% many ways to sort of slice and dice this 01:06:42.920 --> 01:06:46.710 align:start position:0% many ways to sort of slice and dice this right<01:06:43.680> so<01:06:43.960> that<01:06:44.119> is<01:06:44.359> critical<01:06:45.039> I<01:06:45.119> mean<01:06:45.720> this 01:06:46.710 --> 01:06:46.720 align:start position:0% right so that is critical I mean this 01:06:46.720 --> 01:06:48.430 align:start position:0% right so that is critical I mean this and<01:06:46.920> and<01:06:47.039> the<01:06:47.200> good<01:06:47.400> thing<01:06:47.640> is<01:06:47.880> I<01:06:48.000> think<01:06:48.200> the 01:06:48.430 --> 01:06:48.440 align:start position:0% and and the good thing is I think the 01:06:48.440 --> 01:06:51.990 align:start position:0% and and the good thing is I think the impact<01:06:49.319> is<01:06:49.880> U<01:06:50.359> objective<01:06:51.359> I<01:06:51.440> mean<01:06:51.640> can<01:06:51.760> be 01:06:51.990 --> 01:06:52.000 align:start position:0% impact is U objective I mean can be 01:06:52.000 --> 01:06:53.589 align:start position:0% impact is U objective I mean can be fairly<01:06:52.480> objective<01:06:52.880> in<01:06:53.000> terms<01:06:53.200> of<01:06:53.359> how<01:06:53.480> we 01:06:53.589 --> 01:06:53.599 align:start position:0% fairly objective in terms of how we 01:06:53.599 --> 01:06:55.829 align:start position:0% fairly objective in terms of how we determine<01:06:54.000> it 01:06:55.829 --> 01:06:55.839 align:start position:0% determine it 01:06:55.839 --> 01:06:57.750 align:start position:0% determine it but<01:06:56.160> likelihood<01:06:57.039> which<01:06:57.160> is<01:06:57.319> really<01:06:57.559> the 01:06:57.750 --> 01:06:57.760 align:start position:0% but likelihood which is really the 01:06:57.760 --> 01:07:01.230 align:start position:0% but likelihood which is really the probability<01:06:58.520> that<01:06:58.880> this<01:06:59.079> can<01:06:59.760> happen<01:07:00.760> that<01:07:01.000> is 01:07:01.230 --> 01:07:01.240 align:start position:0% probability that this can happen that is 01:07:01.240 --> 01:07:03.870 align:start position:0% probability that this can happen that is trickier<01:07:02.240> right<01:07:02.559> is<01:07:02.839> does<01:07:03.039> this<01:07:03.240> happen<01:07:03.680> all 01:07:03.870 --> 01:07:03.880 align:start position:0% trickier right is does this happen all 01:07:03.880 --> 01:07:06.750 align:start position:0% trickier right is does this happen all the<01:07:04.079> time<01:07:04.440> does<01:07:04.599> it<01:07:04.799> happen<01:07:05.640> sometimes<01:07:06.640> what 01:07:06.750 --> 01:07:06.760 align:start position:0% the time does it happen sometimes what 01:07:06.760 --> 01:07:09.150 align:start position:0% the time does it happen sometimes what are<01:07:06.920> really<01:07:07.200> the<01:07:07.520> conditions<01:07:08.119> under<01:07:08.440> which 01:07:09.150 --> 01:07:09.160 align:start position:0% are really the conditions under which 01:07:09.160 --> 01:07:09.910 align:start position:0% are really the conditions under which this 01:07:09.910 --> 01:07:09.920 align:start position:0% this 01:07:09.920 --> 01:07:12.230 align:start position:0% this particular<01:07:10.920> um<01:07:11.240> vulnerability<01:07:11.960> can<01:07:12.079> be 01:07:12.230 --> 01:07:12.240 align:start position:0% particular um vulnerability can be 01:07:12.240 --> 01:07:13.510 align:start position:0% particular um vulnerability can be exploited<01:07:12.799> that's<01:07:13.000> really<01:07:13.200> what<01:07:13.319> we're 01:07:13.510 --> 01:07:13.520 align:start position:0% exploited that's really what we're 01:07:13.520 --> 01:07:16.029 align:start position:0% exploited that's really what we're looking<01:07:13.799> about<01:07:14.160> right<01:07:14.440> uh<01:07:14.559> looking 01:07:16.029 --> 01:07:16.039 align:start position:0% looking about right uh looking 01:07:16.039 --> 01:07:21.109 align:start position:0% looking about right uh looking at<01:07:17.039> so<01:07:17.400> that<01:07:17.720> is<01:07:18.520> um<01:07:18.799> hard<01:07:19.520> uh<01:07:19.960> and<01:07:20.640> typically 01:07:21.109 --> 01:07:21.119 align:start position:0% at so that is um hard uh and typically 01:07:21.119 --> 01:07:22.510 align:start position:0% at so that is um hard uh and typically what<01:07:21.279> ends<01:07:21.520> up<01:07:21.760> I<01:07:21.799> mean<01:07:21.960> that's<01:07:22.119> where<01:07:22.279> all<01:07:22.400> the 01:07:22.510 --> 01:07:22.520 align:start position:0% what ends up I mean that's where all the 01:07:22.520 --> 01:07:24.269 align:start position:0% what ends up I mean that's where all the escalations<01:07:23.079> happen<01:07:23.400> that<01:07:23.559> Ino<01:07:23.880> was<01:07:24.039> talking 01:07:24.269 --> 01:07:24.279 align:start position:0% escalations happen that Ino was talking 01:07:24.279 --> 01:07:26.750 align:start position:0% escalations happen that Ino was talking about<01:07:25.240> and<01:07:25.599> these<01:07:26.000> conditionals<01:07:26.440> there<01:07:26.559> are<01:07:26.640> a 01:07:26.750 --> 01:07:26.760 align:start position:0% about and these conditionals there are a 01:07:26.760 --> 01:07:29.150 align:start position:0% about and these conditionals there are a whole<01:07:26.960> bunch<01:07:27.160> of<01:07:27.440> Nesta<01:07:27.880> ifs<01:07:28.240> right<01:07:28.480> that<01:07:28.799> if 01:07:29.150 --> 01:07:29.160 align:start position:0% whole bunch of Nesta ifs right that if 01:07:29.160 --> 01:07:31.750 align:start position:0% whole bunch of Nesta ifs right that if this<01:07:29.520> condition<01:07:29.760> is<01:07:29.960> met<01:07:30.279> and<01:07:30.599> this<01:07:30.839> and<01:07:31.160> this 01:07:31.750 --> 01:07:31.760 align:start position:0% this condition is met and this and this 01:07:31.760 --> 01:07:35.430 align:start position:0% this condition is met and this and this so<01:07:32.000> you<01:07:32.200> go<01:07:32.400> on<01:07:32.920> and<01:07:33.920> I<01:07:34.000> think<01:07:34.520> realistically 01:07:35.430 --> 01:07:35.440 align:start position:0% so you go on and I think realistically 01:07:35.440 --> 01:07:39.230 align:start position:0% so you go on and I think realistically the<01:07:35.599> more<01:07:35.880> the<01:07:36.039> number<01:07:36.319> of<01:07:36.960> predicates<01:07:37.960> or<01:07:38.240> ifs 01:07:39.230 --> 01:07:39.240 align:start position:0% the more the number of predicates or ifs 01:07:39.240 --> 01:07:42.069 align:start position:0% the more the number of predicates or ifs the<01:07:39.440> lower<01:07:39.839> the<01:07:40.000> likelihood<01:07:41.000> right<01:07:41.520> so<01:07:41.760> figure 01:07:42.069 --> 01:07:42.079 align:start position:0% the lower the likelihood right so figure 01:07:42.079 --> 01:07:44.870 align:start position:0% the lower the likelihood right so figure out<01:07:42.480> what<01:07:43.319> uh<01:07:43.440> the<01:07:43.599> likelihood<01:07:44.200> is<01:07:44.480> what<01:07:44.680> the 01:07:44.870 --> 01:07:44.880 align:start position:0% out what uh the likelihood is what the 01:07:44.880 --> 01:07:48.670 align:start position:0% out what uh the likelihood is what the impact<01:07:45.359> is<01:07:46.359> and<01:07:46.880> uh<01:07:47.200> use<01:07:47.599> that<01:07:47.839> to<01:07:48.079> sort<01:07:48.279> of 01:07:48.670 --> 01:07:48.680 align:start position:0% impact is and uh use that to sort of 01:07:48.680 --> 01:07:50.109 align:start position:0% impact is and uh use that to sort of quantify<01:07:49.160> the<01:07:49.240> severity<01:07:49.799> of<01:07:50.000> the 01:07:50.109 --> 01:07:50.119 align:start position:0% quantify the severity of the 01:07:50.119 --> 01:07:52.269 align:start position:0% quantify the severity of the vulnerability<01:07:50.680> that<01:07:50.799> you're 01:07:52.269 --> 01:07:52.279 align:start position:0% vulnerability that you're 01:07:52.279 --> 01:07:54.430 align:start position:0% vulnerability that you're reporting<01:07:53.279> and<01:07:53.440> on<01:07:53.559> the<01:07:53.640> flip<01:07:53.960> side<01:07:54.160> for<01:07:54.319> the 01:07:54.430 --> 01:07:54.440 align:start position:0% reporting and on the flip side for the 01:07:54.440 --> 01:07:56.589 align:start position:0% reporting and on the flip side for the developers<01:07:54.960> who<01:07:55.079> may<01:07:55.240> be 01:07:56.589 --> 01:07:56.599 align:start position:0% developers who may be 01:07:56.599 --> 01:07:58.430 align:start position:0% developers who may be sort<01:07:56.799> of<01:07:56.960> looking<01:07:57.200> at<01:07:57.400> these<01:07:57.599> audit<01:07:57.920> contests 01:07:58.430 --> 01:07:58.440 align:start position:0% sort of looking at these audit contests 01:07:58.440 --> 01:08:02.430 align:start position:0% sort of looking at these audit contests or<01:07:59.319> bounties<01:08:00.520> right<01:08:01.520> this<01:08:01.640> is<01:08:01.880> again<01:08:02.200> I<01:08:02.279> mean 01:08:02.430 --> 01:08:02.440 align:start position:0% or bounties right this is again I mean 01:08:02.440 --> 01:08:04.269 align:start position:0% or bounties right this is again I mean if<01:08:02.520> you're<01:08:02.720> evaluating<01:08:03.680> uh<01:08:03.799> if<01:08:03.880> you're<01:08:04.079> one<01:08:04.160> of 01:08:04.269 --> 01:08:04.279 align:start position:0% if you're evaluating uh if you're one of 01:08:04.279 --> 01:08:06.910 align:start position:0% if you're evaluating uh if you're one of the<01:08:04.400> judges<01:08:04.880> or<01:08:05.079> if<01:08:05.160> you're<01:08:05.880> on<01:08:06.119> the<01:08:06.319> team 01:08:06.910 --> 01:08:06.920 align:start position:0% the judges or if you're on the team 01:08:06.920 --> 01:08:09.150 align:start position:0% the judges or if you're on the team looking<01:08:07.279> at<01:08:07.880> U<01:08:08.200> any<01:08:08.400> of<01:08:08.559> these<01:08:08.720> contest 01:08:09.150 --> 01:08:09.160 align:start position:0% looking at U any of these contest 01:08:09.160 --> 01:08:11.750 align:start position:0% looking at U any of these contest results<01:08:09.680> or<01:08:10.039> Bounty<01:08:10.480> submissions<01:08:11.480> this<01:08:11.599> is 01:08:11.750 --> 01:08:11.760 align:start position:0% results or Bounty submissions this is 01:08:11.760 --> 01:08:13.589 align:start position:0% results or Bounty submissions this is something<01:08:12.160> that<01:08:12.279> you<01:08:12.400> need<01:08:12.559> to<01:08:13.000> pay<01:08:13.200> attention 01:08:13.589 --> 01:08:13.599 align:start position:0% something that you need to pay attention 01:08:13.599 --> 01:08:16.390 align:start position:0% something that you need to pay attention to<01:08:14.240> right<01:08:14.640> and<01:08:14.920> and<01:08:15.319> it<01:08:15.480> It's<01:08:15.680> Tricky<01:08:16.120> but<01:08:16.279> it 01:08:16.390 --> 01:08:16.400 align:start position:0% to right and and it It's Tricky but it 01:08:16.400 --> 01:08:20.229 align:start position:0% to right and and it It's Tricky but it is<01:08:17.040> really 01:08:20.229 --> 01:08:20.239 align:start position:0% 01:08:20.239 --> 01:08:23.030 align:start position:0% important<01:08:21.239> great<01:08:21.480> so<01:08:21.640> for<01:08:21.799> the<01:08:22.040> star<01:08:22.759> Star 01:08:23.030 --> 01:08:23.040 align:start position:0% important great so for the star Star 01:08:23.040 --> 01:08:23.870 align:start position:0% important great so for the star Star Wars 01:08:23.870 --> 01:08:23.880 align:start position:0% Wars 01:08:23.880 --> 01:08:27.709 align:start position:0% Wars fans<01:08:24.880> it's<01:08:25.120> really<01:08:25.759> all<01:08:26.080> about<01:08:26.640> being 01:08:27.709 --> 01:08:27.719 align:start position:0% fans it's really all about being 01:08:27.719 --> 01:08:30.590 align:start position:0% fans it's really all about being consistent<01:08:28.719> for<01:08:28.920> the<01:08:29.080> developers<01:08:29.839> it's<01:08:30.080> about 01:08:30.590 --> 01:08:30.600 align:start position:0% consistent for the developers it's about 01:08:30.600 --> 01:08:33.550 align:start position:0% consistent for the developers it's about being<01:08:31.000> consistent<01:08:31.839> with<01:08:32.199> your 01:08:33.550 --> 01:08:33.560 align:start position:0% being consistent with your 01:08:33.560 --> 01:08:35.749 align:start position:0% being consistent with your checks<01:08:34.560> in<01:08:34.759> different<01:08:35.040> parts<01:08:35.239> of<01:08:35.359> your<01:08:35.520> code 01:08:35.749 --> 01:08:35.759 align:start position:0% checks in different parts of your code 01:08:35.759 --> 01:08:37.990 align:start position:0% checks in different parts of your code base<01:08:36.679> on<01:08:36.920> the<01:08:37.040> various<01:08:37.400> assets<01:08:37.719> on<01:08:37.880> the 01:08:37.990 --> 01:08:38.000 align:start position:0% base on the various assets on the 01:08:38.000 --> 01:08:39.990 align:start position:0% base on the various assets on the various<01:08:38.319> actors<01:08:38.640> and 01:08:39.990 --> 01:08:40.000 align:start position:0% various actors and 01:08:40.000 --> 01:08:43.550 align:start position:0% various actors and actions<01:08:41.000> if<01:08:41.640> these<01:08:41.839> checks<01:08:42.120> are 01:08:43.550 --> 01:08:43.560 align:start position:0% actions if these checks are 01:08:43.560 --> 01:08:45.390 align:start position:0% actions if these checks are inconsistent<01:08:44.560> then<01:08:44.759> it<01:08:44.880> leads<01:08:45.199> to 01:08:45.390 --> 01:08:45.400 align:start position:0% inconsistent then it leads to 01:08:45.400 --> 01:08:48.390 align:start position:0% inconsistent then it leads to inconsistent<01:08:46.279> transitions<01:08:47.279> right<01:08:47.560> in<01:08:47.719> your 01:08:48.390 --> 01:08:48.400 align:start position:0% inconsistent transitions right in your 01:08:48.400 --> 01:08:50.510 align:start position:0% inconsistent transitions right in your protocol<01:08:49.400> and<01:08:49.719> those<01:08:49.960> result<01:08:50.319> in 01:08:50.510 --> 01:08:50.520 align:start position:0% protocol and those result in 01:08:50.520 --> 01:08:51.829 align:start position:0% protocol and those result in inconsistent 01:08:51.829 --> 01:08:51.839 align:start position:0% inconsistent 01:08:51.839 --> 01:08:54.870 align:start position:0% inconsistent State<01:08:52.839> and<01:08:53.159> that<01:08:53.359> is<01:08:54.000> again<01:08:54.199> the<01:08:54.319> root<01:08:54.560> of<01:08:54.679> all 01:08:54.870 --> 01:08:54.880 align:start position:0% State and that is again the root of all 01:08:54.880 --> 01:08:58.510 align:start position:0% State and that is again the root of all bugs<01:08:55.600> right<01:08:55.799> I<01:08:55.839> mean<01:08:56.120> these<01:08:56.359> may<01:08:56.719> seem<01:08:57.520> very 01:08:58.510 --> 01:08:58.520 align:start position:0% bugs right I mean these may seem very 01:08:58.520 --> 01:09:00.309 align:start position:0% bugs right I mean these may seem very obvious<01:08:59.080> very 01:09:00.309 --> 01:09:00.319 align:start position:0% obvious very 01:09:00.319 --> 01:09:03.470 align:start position:0% obvious very simplistic<01:09:01.319> but<01:09:01.520> at<01:09:01.679> a<01:09:01.880> 100,000<01:09:02.799> foot<01:09:03.080> level 01:09:03.470 --> 01:09:03.480 align:start position:0% simplistic but at a 100,000 foot level 01:09:03.480 --> 01:09:06.390 align:start position:0% simplistic but at a 100,000 foot level that's<01:09:03.719> what<01:09:03.839> it<01:09:04.000> really<01:09:04.319> is<01:09:05.279> right<01:09:05.960> so<01:09:06.159> if<01:09:06.239> you 01:09:06.390 --> 01:09:06.400 align:start position:0% that's what it really is right so if you 01:09:06.400 --> 01:09:07.789 align:start position:0% that's what it really is right so if you go<01:09:06.600> back<01:09:06.719> to<01:09:06.839> the<01:09:06.960> code<01:09:07.239> that<01:09:07.359> you're<01:09:07.520> looking 01:09:07.789 --> 01:09:07.799 align:start position:0% go back to the code that you're looking 01:09:07.799 --> 01:09:10.229 align:start position:0% go back to the code that you're looking at<01:09:08.600> uh<01:09:08.719> that<01:09:08.839> you're<01:09:09.040> developing<01:09:09.679> or<01:09:09.960> the<01:09:10.120> or 01:09:10.229 --> 01:09:10.239 align:start position:0% at uh that you're developing or the or 01:09:10.239 --> 01:09:12.870 align:start position:0% at uh that you're developing or the or you're<01:09:10.640> reviewing<01:09:11.640> look<01:09:11.880> for<01:09:12.199> these<01:09:12.440> patterns 01:09:12.870 --> 01:09:12.880 align:start position:0% you're reviewing look for these patterns 01:09:12.880 --> 01:09:15.189 align:start position:0% you're reviewing look for these patterns of<01:09:13.040> checks<01:09:14.000> anything<01:09:14.359> that's<01:09:14.600> done<01:09:14.759> in<01:09:14.920> one 01:09:15.189 --> 01:09:15.199 align:start position:0% of checks anything that's done in one 01:09:15.199 --> 01:09:17.630 align:start position:0% of checks anything that's done in one place<01:09:15.520> that<01:09:15.640> is<01:09:15.759> missing<01:09:16.080> in<01:09:16.199> other<01:09:16.640> places 01:09:17.630 --> 01:09:17.640 align:start position:0% place that is missing in other places 01:09:17.640 --> 01:09:19.990 align:start position:0% place that is missing in other places that<01:09:17.960> is<01:09:18.520> uh<01:09:18.799> you<01:09:18.920> know<01:09:19.040> it's<01:09:19.199> a<01:09:19.279> big<01:09:19.480> red<01:09:19.719> flag 01:09:19.990 --> 01:09:20.000 align:start position:0% that is uh you know it's a big red flag 01:09:20.000 --> 01:09:24.189 align:start position:0% that is uh you know it's a big red flag it's<01:09:20.120> a<01:09:20.239> good<01:09:20.440> starting 01:09:24.189 --> 01:09:24.199 align:start position:0% 01:09:24.199 --> 01:09:28.950 align:start position:0% point<01:09:25.199> right 01:09:28.950 --> 01:09:28.960 align:start position:0% 01:09:28.960 --> 01:09:30.510 align:start position:0% so<01:09:29.239> web 01:09:30.510 --> 01:09:30.520 align:start position:0% so web 01:09:30.520 --> 01:09:35.269 align:start position:0% so web 3<01:09:31.520> well<01:09:32.000> this<01:09:32.159> is<01:09:32.600> uh<01:09:33.359> this<01:09:33.520> is<01:09:33.920> a<01:09:34.440> meme<01:09:34.839> adopted 01:09:35.269 --> 01:09:35.279 align:start position:0% 3 well this is uh this is a meme adopted 01:09:35.279 --> 01:09:38.349 align:start position:0% 3 well this is uh this is a meme adopted from<01:09:35.520> web<01:09:36.000> 2<01:09:37.000> right<01:09:37.359> and<01:09:37.560> it's<01:09:38.000> I<01:09:38.080> think<01:09:38.199> I've 01:09:38.349 --> 01:09:38.359 align:start position:0% from web 2 right and it's I think I've 01:09:38.359 --> 01:09:39.829 align:start position:0% from web 2 right and it's I think I've seen<01:09:38.560> it<01:09:38.679> used<01:09:38.960> in<01:09:39.080> the<01:09:39.239> context<01:09:39.600> of 01:09:39.829 --> 01:09:39.839 align:start position:0% seen it used in the context of 01:09:39.839 --> 01:09:43.030 align:start position:0% seen it used in the context of dependencies<01:09:40.839> where<01:09:41.640> the<01:09:41.880> the<01:09:42.080> small<01:09:42.920> uh 01:09:43.030 --> 01:09:43.040 align:start position:0% dependencies where the the small uh 01:09:43.040 --> 01:09:45.709 align:start position:0% dependencies where the the small uh block<01:09:43.359> that<01:09:43.480> you<01:09:43.560> see<01:09:44.319> marked<01:09:44.600> out<01:09:44.759> as<01:09:44.960> bug<01:09:45.480> is 01:09:45.709 --> 01:09:45.719 align:start position:0% block that you see marked out as bug is 01:09:45.719 --> 01:09:48.749 align:start position:0% block that you see marked out as bug is really<01:09:45.960> a<01:09:46.239> dependency<01:09:47.279> for<01:09:48.279> almost 01:09:48.749 --> 01:09:48.759 align:start position:0% really a dependency for almost 01:09:48.759 --> 01:09:51.590 align:start position:0% really a dependency for almost everything<01:09:49.239> that<01:09:49.440> you<01:09:49.600> run<01:09:50.520> but<01:09:50.799> it<01:09:50.920> is<01:09:51.159> small 01:09:51.590 --> 01:09:51.600 align:start position:0% everything that you run but it is small 01:09:51.600 --> 01:09:53.189 align:start position:0% everything that you run but it is small nobody<01:09:51.920> really<01:09:52.120> knows<01:09:52.440> about<01:09:52.679> it<01:09:52.880> nobody 01:09:53.189 --> 01:09:53.199 align:start position:0% nobody really knows about it nobody 01:09:53.199 --> 01:09:55.550 align:start position:0% nobody really knows about it nobody really<01:09:53.400> knows<01:09:53.679> when<01:09:53.839> it<01:09:53.960> was<01:09:54.159> developed<01:09:55.159> and 01:09:55.550 --> 01:09:55.560 align:start position:0% really knows when it was developed and 01:09:55.560 --> 01:09:58.030 align:start position:0% really knows when it was developed and whether<01:09:55.760> it's<01:09:55.920> being<01:09:56.159> maintained<01:09:57.159> and 01:09:58.030 --> 01:09:58.040 align:start position:0% whether it's being maintained and 01:09:58.040 --> 01:10:01.430 align:start position:0% whether it's being maintained and breaking<01:09:58.600> that<01:09:59.360> right<01:09:59.640> could<01:10:00.040> really<01:10:01.040> bring 01:10:01.430 --> 01:10:01.440 align:start position:0% breaking that right could really bring 01:10:01.440 --> 01:10:04.350 align:start position:0% breaking that right could really bring down<01:10:02.159> the<01:10:02.360> entire<01:10:02.880> space<01:10:03.679> so<01:10:03.840> in<01:10:03.960> the<01:10:04.080> case<01:10:04.199> of 01:10:04.350 --> 01:10:04.360 align:start position:0% down the entire space so in the case of 01:10:04.360 --> 01:10:07.350 align:start position:0% down the entire space so in the case of web<01:10:04.560> 3<01:10:04.960> I<01:10:05.080> think<01:10:05.920> um<01:10:06.239> it<01:10:06.360> is<01:10:06.640> very<01:10:06.840> similar<01:10:07.280> and 01:10:07.350 --> 01:10:07.360 align:start position:0% web 3 I think um it is very similar and 01:10:07.360 --> 01:10:10.550 align:start position:0% web 3 I think um it is very similar and I<01:10:07.480> think<01:10:07.600> it<01:10:07.679> is<01:10:07.960> even<01:10:08.679> worse<01:10:09.679> because<01:10:10.000> web<01:10:10.320> web 01:10:10.550 --> 01:10:10.560 align:start position:0% I think it is even worse because web web 01:10:10.560 --> 01:10:12.830 align:start position:0% I think it is even worse because web web 3<01:10:10.760> is<01:10:10.920> not<01:10:11.120> of<01:10:11.360> sort<01:10:11.520> of<01:10:11.760> isolated<01:10:12.199> from<01:10:12.360> web<01:10:12.560> 2 01:10:12.830 --> 01:10:12.840 align:start position:0% 3 is not of sort of isolated from web 2 01:10:12.840 --> 01:10:14.510 align:start position:0% 3 is not of sort of isolated from web 2 right<01:10:12.960> it's<01:10:13.080> really<01:10:13.280> building<01:10:13.679> upon<01:10:13.960> web<01:10:14.199> 2 01:10:14.510 --> 01:10:14.520 align:start position:0% right it's really building upon web 2 01:10:14.520 --> 01:10:16.270 align:start position:0% right it's really building upon web 2 and<01:10:14.840> and<01:10:15.120> there<01:10:15.239> have<01:10:15.360> been<01:10:15.560> many<01:10:15.800> talks<01:10:16.120> here 01:10:16.270 --> 01:10:16.280 align:start position:0% and and there have been many talks here 01:10:16.280 --> 01:10:18.149 align:start position:0% and and there have been many talks here that<01:10:16.440> talk<01:10:16.679> about<01:10:16.880> the<01:10:17.040> web<01:10:17.239> 2<01:10:17.679> aspect<01:10:17.960> of 01:10:18.149 --> 01:10:18.159 align:start position:0% that talk about the web 2 aspect of 01:10:18.159 --> 01:10:21.070 align:start position:0% that talk about the web 2 aspect of security<01:10:18.960> so<01:10:19.080> we<01:10:19.199> won't<01:10:19.480> get<01:10:19.600> into<01:10:19.840> that 01:10:21.070 --> 01:10:21.080 align:start position:0% security so we won't get into that 01:10:21.080 --> 01:10:25.470 align:start position:0% security so we won't get into that but<01:10:22.080> the<01:10:22.280> bugs<01:10:22.719> in<01:10:22.960> web<01:10:23.560> 3<01:10:24.560> can<01:10:24.760> be<01:10:24.960> any 01:10:25.470 --> 01:10:25.480 align:start position:0% but the bugs in web 3 can be any 01:10:25.480 --> 01:10:27.910 align:start position:0% but the bugs in web 3 can be any anywhere<01:10:26.480> and<01:10:26.679> really<01:10:26.960> they're<01:10:27.280> everywhere 01:10:27.910 --> 01:10:27.920 align:start position:0% anywhere and really they're everywhere 01:10:27.920 --> 01:10:29.709 align:start position:0% anywhere and really they're everywhere at<01:10:28.120> this 01:10:29.709 --> 01:10:29.719 align:start position:0% at this 01:10:29.719 --> 01:10:33.350 align:start position:0% at this point<01:10:30.719> so<01:10:30.920> this<01:10:31.080> may<01:10:31.400> paint<01:10:31.719> a<01:10:31.920> very<01:10:32.120> sort<01:10:32.360> of 01:10:33.350 --> 01:10:33.360 align:start position:0% point so this may paint a very sort of 01:10:33.360 --> 01:10:37.149 align:start position:0% point so this may paint a very sort of red<01:10:33.679> nasty<01:10:34.400> sort<01:10:34.600> of<01:10:35.000> uh<01:10:35.719> uh<01:10:35.880> picture<01:10:36.640> uh<01:10:36.880> very 01:10:37.149 --> 01:10:37.159 align:start position:0% red nasty sort of uh uh picture uh very 01:10:37.159 --> 01:10:40.430 align:start position:0% red nasty sort of uh uh picture uh very pessimistic<01:10:38.080> Outlook<01:10:39.000> but<01:10:40.000> I<01:10:40.080> think<01:10:40.239> we<01:10:40.360> are 01:10:40.430 --> 01:10:40.440 align:start position:0% pessimistic Outlook but I think we are 01:10:40.440 --> 01:10:42.590 align:start position:0% pessimistic Outlook but I think we are getting<01:10:40.719> better<01:10:41.640> right<01:10:41.800> I<01:10:41.880> mean<01:10:42.080> it's<01:10:42.360> it's 01:10:42.590 --> 01:10:42.600 align:start position:0% getting better right I mean it's it's 01:10:42.600 --> 01:10:45.870 align:start position:0% getting better right I mean it's it's worse<01:10:43.520> it<01:10:43.679> was<01:10:44.000> worse<01:10:45.000> it<01:10:45.199> also<01:10:45.560> sort<01:10:45.760> of 01:10:45.870 --> 01:10:45.880 align:start position:0% worse it was worse it also sort of 01:10:45.880 --> 01:10:48.310 align:start position:0% worse it was worse it also sort of signals<01:10:46.360> the<01:10:46.480> maturity<01:10:47.040> of<01:10:47.480> uh<01:10:47.840> the<01:10:47.960> entire 01:10:48.310 --> 01:10:48.320 align:start position:0% signals the maturity of uh the entire 01:10:48.320 --> 01:10:51.669 align:start position:0% signals the maturity of uh the entire stack<01:10:48.800> the<01:10:48.920> entire<01:10:49.320> space<01:10:50.320> but<01:10:50.679> these<01:10:51.440> are 01:10:51.669 --> 01:10:51.679 align:start position:0% stack the entire space but these are 01:10:51.679 --> 01:10:54.550 align:start position:0% stack the entire space but these are getting<01:10:52.040> better<01:10:52.760> right<01:10:53.719> and<01:10:53.920> as<01:10:54.040> we<01:10:54.159> do<01:10:54.400> this 01:10:54.550 --> 01:10:54.560 align:start position:0% getting better right and as we do this 01:10:54.560 --> 01:10:57.709 align:start position:0% getting better right and as we do this we<01:10:54.760> also<01:10:55.040> add<01:10:55.320> adding<01:10:55.560> a<01:10:55.679> lot<01:10:55.920> more<01:10:56.880> um<01:10:57.560> lot 01:10:57.709 --> 01:10:57.719 align:start position:0% we also add adding a lot more um lot 01:10:57.719 --> 01:10:59.510 align:start position:0% we also add adding a lot more um lot more<01:10:57.960> codebase<01:10:58.520> lot<01:10:58.679> of<01:10:58.960> you<01:10:59.040> know<01:10:59.159> a<01:10:59.239> lot<01:10:59.360> of 01:10:59.510 --> 01:10:59.520 align:start position:0% more codebase lot of you know a lot of 01:10:59.520 --> 01:11:01.830 align:start position:0% more codebase lot of you know a lot of new<01:10:59.719> infra<01:11:00.120> a<01:11:00.199> lot<01:11:00.320> of<01:11:00.440> new<01:11:00.600> tooling<01:11:01.480> so<01:11:01.640> it's 01:11:01.830 --> 01:11:01.840 align:start position:0% new infra a lot of new tooling so it's 01:11:01.840 --> 01:11:03.630 align:start position:0% new infra a lot of new tooling so it's sort<01:11:02.120> of 01:11:03.630 --> 01:11:03.640 align:start position:0% sort of 01:11:03.640 --> 01:11:06.270 align:start position:0% sort of um<01:11:04.640> uh<01:11:04.800> cat<01:11:05.000> and<01:11:05.120> mouse<01:11:05.440> game<01:11:05.760> right<01:11:05.920> you<01:11:06.120> you 01:11:06.270 --> 01:11:06.280 align:start position:0% um uh cat and mouse game right you you 01:11:06.280 --> 01:11:09.070 align:start position:0% um uh cat and mouse game right you you fix<01:11:06.640> these<01:11:06.920> bugs<01:11:07.600> but<01:11:07.920> there<01:11:08.040> are<01:11:08.320> new<01:11:08.560> ones 01:11:09.070 --> 01:11:09.080 align:start position:0% fix these bugs but there are new ones 01:11:09.080 --> 01:11:10.590 align:start position:0% fix these bugs but there are new ones there's<01:11:09.320> new<01:11:09.480> code<01:11:09.719> bases<01:11:10.120> and<01:11:10.239> there<01:11:10.320> are<01:11:10.440> new 01:11:10.590 --> 01:11:10.600 align:start position:0% there's new code bases and there are new 01:11:10.600 --> 01:11:11.830 align:start position:0% there's new code bases and there are new bugs<01:11:10.840> in 01:11:11.830 --> 01:11:11.840 align:start position:0% bugs in 01:11:11.840 --> 01:11:14.950 align:start position:0% bugs in them<01:11:12.840> so<01:11:13.040> for<01:11:13.560> for<01:11:13.760> the<01:11:13.920> developers<01:11:14.679> I<01:11:14.800> guess 01:11:14.950 --> 01:11:14.960 align:start position:0% them so for for the developers I guess 01:11:14.960 --> 01:11:17.550 align:start position:0% them so for for the developers I guess the<01:11:15.120> message<01:11:15.640> here<01:11:16.000> is<01:11:16.360> that<01:11:16.719> every<01:11:17.120> line<01:11:17.440> of 01:11:17.550 --> 01:11:17.560 align:start position:0% the message here is that every line of 01:11:17.560 --> 01:11:21.830 align:start position:0% the message here is that every line of your<01:11:17.760> code<01:11:18.080> M<01:11:18.360> codebase<01:11:19.080> matters<01:11:20.080> right<01:11:20.920> so 01:11:21.830 --> 01:11:21.840 align:start position:0% your code M codebase matters right so 01:11:21.840 --> 01:11:24.070 align:start position:0% your code M codebase matters right so just<01:11:22.040> be<01:11:22.320> very<01:11:22.600> conscious<01:11:23.120> about<01:11:23.480> everything 01:11:24.070 --> 01:11:24.080 align:start position:0% just be very conscious about everything 01:11:24.080 --> 01:11:26.709 align:start position:0% just be very conscious about everything that<01:11:24.560> is<01:11:24.760> getting<01:11:25.000> into<01:11:25.400> your<01:11:25.520> code<01:11:25.760> basee<01:11:26.520> try 01:11:26.709 --> 01:11:26.719 align:start position:0% that is getting into your code basee try 01:11:26.719 --> 01:11:29.189 align:start position:0% that is getting into your code basee try to<01:11:26.880> see<01:11:27.080> if<01:11:27.199> it<01:11:27.280> is<01:11:27.440> really<01:11:27.679> required<01:11:28.120> or<01:11:28.280> not 01:11:29.189 --> 01:11:29.199 align:start position:0% to see if it is really required or not 01:11:29.199 --> 01:11:31.910 align:start position:0% to see if it is really required or not and<01:11:29.320> for<01:11:29.480> the<01:11:29.640> reviewers<01:11:30.159> for<01:11:30.280> the<01:11:30.400> security 01:11:31.910 --> 01:11:31.920 align:start position:0% and for the reviewers for the security 01:11:31.920 --> 01:11:35.630 align:start position:0% and for the reviewers for the security researchers<01:11:32.920> read<01:11:33.920> every<01:11:34.280> line<01:11:35.280> that's<01:11:35.440> not 01:11:35.630 --> 01:11:35.640 align:start position:0% researchers read every line that's not 01:11:35.640 --> 01:11:38.350 align:start position:0% researchers read every line that's not enough<01:11:36.040> read<01:11:36.320> between<01:11:36.640> the<01:11:36.760> lines<01:11:37.080> as 01:11:38.350 --> 01:11:38.360 align:start position:0% enough read between the lines as 01:11:38.360 --> 01:11:41.110 align:start position:0% enough read between the lines as well<01:11:39.360> and<01:11:39.560> what<01:11:39.800> this<01:11:40.000> means 01:11:41.110 --> 01:11:41.120 align:start position:0% well and what this means 01:11:41.120 --> 01:11:44.870 align:start position:0% well and what this means is<01:11:42.120> what<01:11:42.760> it's<01:11:43.080> it's<01:11:43.719> relatively<01:11:44.280> easier<01:11:44.679> to 01:11:44.870 --> 01:11:44.880 align:start position:0% is what it's it's relatively easier to 01:11:44.880 --> 01:11:49.149 align:start position:0% is what it's it's relatively easier to sort<01:11:45.159> of<01:11:46.159> find<01:11:46.520> bugs<01:11:47.239> in<01:11:47.600> the<01:11:47.800> code<01:11:48.360> that<01:11:48.480> you 01:11:49.149 --> 01:11:49.159 align:start position:0% sort of find bugs in the code that you 01:11:49.159 --> 01:11:53.229 align:start position:0% sort of find bugs in the code that you see<01:11:50.159> but<01:11:50.520> it's<01:11:51.000> much<01:11:51.440> harder<01:11:52.440> to<01:11:52.719> imagine 01:11:53.229 --> 01:11:53.239 align:start position:0% see but it's much harder to imagine 01:11:53.239 --> 01:11:55.550 align:start position:0% see but it's much harder to imagine things<01:11:53.679> to<01:11:53.880> imagine<01:11:54.239> bugs<01:11:54.639> in<01:11:54.840> the<01:11:55.000> part<01:11:55.440> That 01:11:55.550 --> 01:11:55.560 align:start position:0% things to imagine bugs in the part That 01:11:55.560 --> 01:11:56.470 align:start position:0% things to imagine bugs in the part That You<01:11:55.679> Don't 01:11:56.470 --> 01:11:56.480 align:start position:0% You Don't 01:11:56.480 --> 01:12:00.870 align:start position:0% You Don't See<01:11:57.639> right<01:11:58.639> so<01:11:59.040> do<01:11:59.360> that<01:11:59.880> and 01:12:00.870 --> 01:12:00.880 align:start position:0% See right so do that and 01:12:00.880 --> 01:12:03.669 align:start position:0% See right so do that and uh<01:12:01.880> and<01:12:02.159> that<01:12:02.520> even<01:12:02.760> then<01:12:02.880> it's<01:12:03.000> on<01:12:03.239> enough 01:12:03.669 --> 01:12:03.679 align:start position:0% uh and that even then it's on enough 01:12:03.679 --> 01:12:07.270 align:start position:0% uh and that even then it's on enough right<01:12:04.320> so<01:12:04.600> it's<01:12:04.920> uh<01:12:05.040> it's<01:12:05.239> almost<01:12:05.880> um<01:12:06.480> an 01:12:07.270 --> 01:12:07.280 align:start position:0% right so it's uh it's almost um an 01:12:07.280 --> 01:12:09.870 align:start position:0% right so it's uh it's almost um an unreachable<01:12:08.000> challenge<01:12:08.480> for<01:12:09.040> the<01:12:09.400> security 01:12:09.870 --> 01:12:09.880 align:start position:0% unreachable challenge for the security 01:12:09.880 --> 01:12:11.709 align:start position:0% unreachable challenge for the security researchers<01:12:10.880> because<01:12:11.199> you<01:12:11.320> have<01:12:11.400> to<01:12:11.520> read 01:12:11.709 --> 01:12:11.719 align:start position:0% researchers because you have to read 01:12:11.719 --> 01:12:13.470 align:start position:0% researchers because you have to read every<01:12:11.960> line<01:12:12.280> between<01:12:12.600> the<01:12:12.719> lines<01:12:13.000> and<01:12:13.199> Beyond 01:12:13.470 --> 01:12:13.480 align:start position:0% every line between the lines and Beyond 01:12:13.480 --> 01:12:14.910 align:start position:0% every line between the lines and Beyond the<01:12:13.600> Lines<01:12:13.960> Beyond<01:12:14.239> the<01:12:14.320> Lines<01:12:14.560> is<01:12:14.719> really 01:12:14.910 --> 01:12:14.920 align:start position:0% the Lines Beyond the Lines is really 01:12:14.920 --> 01:12:17.470 align:start position:0% the Lines Beyond the Lines is really about<01:12:15.159> the<01:12:15.440> dependencies<01:12:16.440> that<01:12:16.679> you<01:12:16.800> see<01:12:17.159> here 01:12:17.470 --> 01:12:17.480 align:start position:0% about the dependencies that you see here 01:12:17.480 --> 01:12:20.070 align:start position:0% about the dependencies that you see here right<01:12:18.239> it's<01:12:18.440> not<01:12:18.679> enough<01:12:18.960> if<01:12:19.199> you<01:12:19.400> look<01:12:19.600> at 01:12:20.070 --> 01:12:20.080 align:start position:0% right it's not enough if you look at 01:12:20.080 --> 01:12:22.950 align:start position:0% right it's not enough if you look at what<01:12:20.280> your<01:12:20.520> code<01:12:20.760> base<01:12:21.080> is<01:12:21.880> but<01:12:22.480> all<01:12:22.639> the<01:12:22.800> other 01:12:22.950 --> 01:12:22.960 align:start position:0% what your code base is but all the other 01:12:22.960 --> 01:12:26.070 align:start position:0% what your code base is but all the other code<01:12:23.159> bases<01:12:23.520> I<01:12:23.560> mean<01:12:23.679> we<01:12:23.880> really<01:12:24.080> building<01:12:24.960> the 01:12:26.070 --> 01:12:26.080 align:start position:0% code bases I mean we really building the 01:12:26.080 --> 01:12:29.790 align:start position:0% code bases I mean we really building the Legos<01:12:26.600> of<01:12:27.000> the<01:12:27.400> future<01:12:28.400> or<01:12:28.840> the<01:12:29.159> the<01:12:29.320> the 01:12:29.790 --> 01:12:29.800 align:start position:0% Legos of the future or the the the 01:12:29.800 --> 01:12:32.910 align:start position:0% Legos of the future or the the the financial<01:12:30.800> uh<01:12:31.080> defi<01:12:31.600> blocks<01:12:32.440> the<01:12:32.560> future 01:12:32.910 --> 01:12:32.920 align:start position:0% financial uh defi blocks the future 01:12:32.920 --> 01:12:36.750 align:start position:0% financial uh defi blocks the future internet<01:12:33.760> 3.0<01:12:34.760> piure<01:12:35.400> term<01:12:35.880> right<01:12:36.480> if<01:12:36.600> you 01:12:36.750 --> 01:12:36.760 align:start position:0% internet 3.0 piure term right if you 01:12:36.760 --> 01:12:38.709 align:start position:0% internet 3.0 piure term right if you want<01:12:36.880> to<01:12:37.080> build<01:12:37.480> that 01:12:38.709 --> 01:12:38.719 align:start position:0% want to build that 01:12:38.719 --> 01:12:41.270 align:start position:0% want to build that then<01:12:39.719> they<01:12:39.880> have<01:12:40.040> to<01:12:40.159> work<01:12:40.560> together<01:12:41.000> and<01:12:41.159> if 01:12:41.270 --> 01:12:41.280 align:start position:0% then they have to work together and if 01:12:41.280 --> 01:12:43.830 align:start position:0% then they have to work together and if they<01:12:41.400> have<01:12:41.480> to<01:12:41.600> work<01:12:42.280> together<01:12:43.280> we<01:12:43.480> cannot 01:12:43.830 --> 01:12:43.840 align:start position:0% they have to work together we cannot 01:12:43.840 --> 01:12:45.830 align:start position:0% they have to work together we cannot afford<01:12:44.120> to<01:12:44.239> have<01:12:44.400> security<01:12:44.840> issues<01:12:45.360> in<01:12:45.639> the 01:12:45.830 --> 01:12:45.840 align:start position:0% afford to have security issues in the 01:12:45.840 --> 01:12:48.270 align:start position:0% afford to have security issues in the glue<01:12:46.360> that<01:12:46.520> is<01:12:46.719> connecting<01:12:47.199> them<01:12:47.840> right<01:12:48.000> so 01:12:48.270 --> 01:12:48.280 align:start position:0% glue that is connecting them right so 01:12:48.280 --> 01:12:50.750 align:start position:0% glue that is connecting them right so that<01:12:48.400> is<01:12:48.920> that<01:12:49.040> is<01:12:49.199> the<01:12:49.360> real<01:12:49.840> part<01:12:50.080> here<01:12:50.280> so<01:12:50.639> in 01:12:50.750 --> 01:12:50.760 align:start position:0% that is that is the real part here so in 01:12:50.760 --> 01:12:52.470 align:start position:0% that is that is the real part here so in the<01:12:50.880> case<01:12:51.040> of<01:12:51.280> web3<01:12:51.679> smart<01:12:51.920> contract 01:12:52.470 --> 01:12:52.480 align:start position:0% the case of web3 smart contract 01:12:52.480 --> 01:12:55.229 align:start position:0% the case of web3 smart contract specifically<01:12:53.480> you<01:12:53.600> may<01:12:53.840> be<01:12:54.280> looking<01:12:54.600> at 01:12:55.229 --> 01:12:55.239 align:start position:0% specifically you may be looking at 01:12:55.239 --> 01:12:57.189 align:start position:0% specifically you may be looking at dependencies<01:12:55.760> on<01:12:55.920> oracles<01:12:56.719> right<01:12:56.920> I<01:12:56.960> mean 01:12:57.189 --> 01:12:57.199 align:start position:0% dependencies on oracles right I mean 01:12:57.199 --> 01:12:59.709 align:start position:0% dependencies on oracles right I mean dependencies<01:12:57.920> on<01:12:58.280> other<01:12:58.719> protocols 01:12:59.709 --> 01:12:59.719 align:start position:0% dependencies on other protocols 01:12:59.719 --> 01:13:03.149 align:start position:0% dependencies on other protocols dependencies<01:13:00.600> on<01:13:00.880> your<01:13:01.159> web<01:13:01.800> tooling<01:13:02.800> all 01:13:03.149 --> 01:13:03.159 align:start position:0% dependencies on your web tooling all 01:13:03.159 --> 01:13:06.470 align:start position:0% dependencies on your web tooling all those<01:13:03.360> can<01:13:03.560> have<01:13:03.760> bugs<01:13:04.239> and<01:13:04.760> has<01:13:04.920> to<01:13:05.120> be<01:13:05.520> within 01:13:06.470 --> 01:13:06.480 align:start position:0% those can have bugs and has to be within 01:13:06.480 --> 01:13:10.790 align:start position:0% those can have bugs and has to be within uh<01:13:06.639> your<01:13:07.320> U<01:13:07.800> uh<01:13:07.920> threat 01:13:10.790 --> 01:13:10.800 align:start position:0% 01:13:10.800 --> 01:13:14.390 align:start position:0% model<01:13:11.800> right<01:13:12.239> so<01:13:13.080> next<01:13:13.360> meme<01:13:13.880> for<01:13:14.159> all<01:13:14.320> the 01:13:14.390 --> 01:13:14.400 align:start position:0% model right so next meme for all the 01:13:14.400 --> 01:13:18.030 align:start position:0% model right so next meme for all the Matrix<01:13:14.800> fans<01:13:15.159> here<01:13:15.760> bugs<01:13:16.120> are<01:13:16.320> really 01:13:18.030 --> 01:13:18.040 align:start position:0% Matrix fans here bugs are really 01:13:18.040 --> 01:13:21.669 align:start position:0% Matrix fans here bugs are really everywhere<01:13:19.040> right<01:13:19.960> they're<01:13:20.280> really<01:13:20.639> there<01:13:21.080> in 01:13:21.669 --> 01:13:21.679 align:start position:0% everywhere right they're really there in 01:13:21.679 --> 01:13:24.030 align:start position:0% everywhere right they're really there in every<01:13:22.040> code<01:13:22.360> base<01:13:22.719> it's<01:13:23.159> it's<01:13:23.440> pretty<01:13:23.679> much<01:13:23.880> a 01:13:24.030 --> 01:13:24.040 align:start position:0% every code base it's it's pretty much a 01:13:24.040 --> 01:13:28.229 align:start position:0% every code base it's it's pretty much a matter<01:13:24.360> of<01:13:25.520> um<01:13:25.960> what<01:13:26.239> incentives<01:13:26.960> are<01:13:27.960> right 01:13:28.229 --> 01:13:28.239 align:start position:0% matter of um what incentives are right 01:13:28.239 --> 01:13:30.229 align:start position:0% matter of um what incentives are right for<01:13:28.600> the<01:13:28.760> developers<01:13:29.280> or<01:13:29.440> the<01:13:29.560> researchers<01:13:30.040> to 01:13:30.229 --> 01:13:30.239 align:start position:0% for the developers or the researchers to 01:13:30.239 --> 01:13:31.110 align:start position:0% for the developers or the researchers to find 01:13:31.110 --> 01:13:31.120 align:start position:0% find 01:13:31.120 --> 01:13:34.629 align:start position:0% find them<01:13:32.120> so<01:13:32.760> the<01:13:32.880> message<01:13:33.360> here<01:13:33.679> is<01:13:34.199> look<01:13:34.400> at 01:13:34.629 --> 01:13:34.639 align:start position:0% them so the message here is look at 01:13:34.639 --> 01:13:36.189 align:start position:0% them so the message here is look at what's<01:13:34.920> there<01:13:35.120> and<01:13:35.280> what's 01:13:36.189 --> 01:13:36.199 align:start position:0% what's there and what's 01:13:36.199 --> 01:13:38.910 align:start position:0% what's there and what's missing<01:13:37.199> for<01:13:37.440> all<01:13:37.600> the<01:13:37.760> developers<01:13:38.600> think 01:13:38.910 --> 01:13:38.920 align:start position:0% missing for all the developers think 01:13:38.920 --> 01:13:40.470 align:start position:0% missing for all the developers think like<01:13:39.080> an<01:13:39.239> attacker<01:13:39.760> right<01:13:39.920> the<01:13:40.040> security 01:13:40.470 --> 01:13:40.480 align:start position:0% like an attacker right the security 01:13:40.480 --> 01:13:42.990 align:start position:0% like an attacker right the security mindset<01:13:41.239> how<01:13:41.400> can<01:13:41.560> it<01:13:41.719> be<01:13:41.960> broken<01:13:42.480> so<01:13:42.679> that<01:13:42.800> is 01:13:42.990 --> 01:13:43.000 align:start position:0% mindset how can it be broken so that is 01:13:43.000 --> 01:13:44.870 align:start position:0% mindset how can it be broken so that is really<01:13:43.320> the<01:13:43.960> sort<01:13:44.120> of<01:13:44.239> the<01:13:44.360> repetitive 01:13:44.870 --> 01:13:44.880 align:start position:0% really the sort of the repetitive 01:13:44.880 --> 01:13:47.470 align:start position:0% really the sort of the repetitive message<01:13:45.400> here<01:13:46.400> and<01:13:46.520> for<01:13:46.719> the<01:13:46.840> researchers 01:13:47.470 --> 01:13:47.480 align:start position:0% message here and for the researchers 01:13:47.480 --> 01:13:49.430 align:start position:0% message here and for the researchers obviously<01:13:48.239> think<01:13:48.520> like<01:13:48.719> that<01:13:48.880> but<01:13:49.080> also<01:13:49.239> act 01:13:49.430 --> 01:13:49.440 align:start position:0% obviously think like that but also act 01:13:49.440 --> 01:13:51.870 align:start position:0% obviously think like that but also act like<01:13:49.560> a<01:13:49.679> white<01:13:49.920> hat<01:13:50.600> right<01:13:51.360> uh<01:13:51.440> we<01:13:51.560> can<01:13:51.719> get 01:13:51.870 --> 01:13:51.880 align:start position:0% like a white hat right uh we can get 01:13:51.880 --> 01:13:53.830 align:start position:0% like a white hat right uh we can get into<01:13:52.120> more<01:13:52.320> of<01:13:52.679> those<01:13:52.840> stories<01:13:53.239> later<01:13:53.480> on<01:13:53.719> I 01:13:53.830 --> 01:13:53.840 align:start position:0% into more of those stories later on I 01:13:53.840 --> 01:13:55.830 align:start position:0% into more of those stories later on I think<01:13:54.199> uh<01:13:54.400> yuran<01:13:54.840> had 01:13:55.830 --> 01:13:55.840 align:start position:0% think uh yuran had 01:13:55.840 --> 01:13:59.629 align:start position:0% think uh yuran had um<01:13:56.840> had<01:13:57.000> a<01:13:57.239> talk<01:13:57.600> earlier<01:13:57.960> on<01:13:58.560> with<01:13:59.120> u<01:13:59.360> talking 01:13:59.629 --> 01:13:59.639 align:start position:0% um had a talk earlier on with u talking 01:13:59.639 --> 01:14:06.550 align:start position:0% um had a talk earlier on with u talking about<01:13:59.880> bouny<01:14:00.639> stories<01:14:01.639> at<01:14:01.760> the<01:14:01.920> security 01:14:06.550 --> 01:14:06.560 align:start position:0% 01:14:06.560 --> 01:14:11.510 align:start position:0% conference<01:14:07.639> okay<01:14:08.639> so<01:14:09.120> this<01:14:09.520> again<01:14:10.520> is 01:14:11.510 --> 01:14:11.520 align:start position:0% conference okay so this again is 01:14:11.520 --> 01:14:12.870 align:start position:0% conference okay so this again is invariance 01:14:12.870 --> 01:14:12.880 align:start position:0% invariance 01:14:12.880 --> 01:14:16.470 align:start position:0% invariance Right<01:14:13.880> a<01:14:14.080> lot<01:14:14.280> of<01:14:14.520> security<01:14:15.080> well<01:14:15.639> lot<01:14:15.800> of<01:14:15.960> it 01:14:16.470 --> 01:14:16.480 align:start position:0% Right a lot of security well lot of it 01:14:16.480 --> 01:14:18.270 align:start position:0% Right a lot of security well lot of it in<01:14:16.600> the<01:14:16.719> smart<01:14:17.040> contract<01:14:17.400> space<01:14:17.679> in<01:14:17.920> in<01:14:18.040> your 01:14:18.270 --> 01:14:18.280 align:start position:0% in the smart contract space in in your 01:14:18.280 --> 01:14:20.669 align:start position:0% in the smart contract space in in your code<01:14:18.560> base<01:14:19.080> boils<01:14:19.440> down<01:14:19.679> to 01:14:20.669 --> 01:14:20.679 align:start position:0% code base boils down to 01:14:20.679 --> 01:14:23.629 align:start position:0% code base boils down to invariance<01:14:21.880> invariance<01:14:22.880> is<01:14:23.159> another<01:14:23.440> term 01:14:23.629 --> 01:14:23.639 align:start position:0% invariance invariance is another term 01:14:23.639 --> 01:14:25.709 align:start position:0% invariance invariance is another term for<01:14:23.920> properties 01:14:25.709 --> 01:14:25.719 align:start position:0% for properties 01:14:25.719 --> 01:14:27.669 align:start position:0% for properties what<01:14:25.960> properties<01:14:26.400> should<01:14:26.639> hold<01:14:26.880> in<01:14:27.040> your<01:14:27.199> code 01:14:27.669 --> 01:14:27.679 align:start position:0% what properties should hold in your code 01:14:27.679 --> 01:14:30.590 align:start position:0% what properties should hold in your code base<01:14:28.679> what<01:14:28.920> properties<01:14:29.639> should<01:14:30.000> not<01:14:30.280> hold 01:14:30.590 --> 01:14:30.600 align:start position:0% base what properties should not hold 01:14:30.600 --> 01:14:34.470 align:start position:0% base what properties should not hold good<01:14:30.840> in<01:14:31.040> this<01:14:31.360> code<01:14:31.719> base<01:14:32.600> right<01:14:33.520> and<01:14:33.880> these 01:14:34.470 --> 01:14:34.480 align:start position:0% good in this code base right and these 01:14:34.480 --> 01:14:35.590 align:start position:0% good in this code base right and these have<01:14:34.679> to 01:14:35.590 --> 01:14:35.600 align:start position:0% have to 01:14:35.600 --> 01:14:38.550 align:start position:0% have to be<01:14:36.600> consciously<01:14:37.159> thought<01:14:37.440> about<01:14:38.320> right<01:14:38.480> I 01:14:38.550 --> 01:14:38.560 align:start position:0% be consciously thought about right I 01:14:38.560 --> 01:14:40.350 align:start position:0% be consciously thought about right I mean<01:14:38.719> this<01:14:38.840> comes<01:14:39.000> up<01:14:39.120> in<01:14:39.239> the<01:14:39.360> context<01:14:39.800> of<01:14:40.199> uh 01:14:40.350 --> 01:14:40.360 align:start position:0% mean this comes up in the context of uh 01:14:40.360 --> 01:14:42.750 align:start position:0% mean this comes up in the context of uh formal<01:14:40.679> verification<01:14:41.639> typically<01:14:42.600> where 01:14:42.750 --> 01:14:42.760 align:start position:0% formal verification typically where 01:14:42.760 --> 01:14:44.350 align:start position:0% formal verification typically where you'll<01:14:42.960> have<01:14:43.159> to<01:14:43.280> specify<01:14:43.679> the<01:14:43.800> invariance 01:14:44.350 --> 01:14:44.360 align:start position:0% you'll have to specify the invariance 01:14:44.360 --> 01:14:46.629 align:start position:0% you'll have to specify the invariance and<01:14:44.480> then<01:14:44.600> use<01:14:44.800> a<01:14:44.960> checker<01:14:45.920> but<01:14:46.120> then<01:14:46.320> even 01:14:46.629 --> 01:14:46.639 align:start position:0% and then use a checker but then even 01:14:46.639 --> 01:14:48.030 align:start position:0% and then use a checker but then even without 01:14:48.030 --> 01:14:48.040 align:start position:0% without 01:14:48.040 --> 01:14:51.470 align:start position:0% without that<01:14:49.040> as<01:14:49.159> a<01:14:49.639> developer<01:14:50.639> before<01:14:50.960> you<01:14:51.120> write<01:14:51.320> a 01:14:51.470 --> 01:14:51.480 align:start position:0% that as a developer before you write a 01:14:51.480 --> 01:14:55.750 align:start position:0% that as a developer before you write a line<01:14:51.679> of<01:14:51.880> code<01:14:52.800> right<01:14:53.800> think<01:14:54.159> about 01:14:55.750 --> 01:14:55.760 align:start position:0% line of code right think about 01:14:55.760 --> 01:14:57.709 align:start position:0% line of code right think about what<01:14:55.920> should<01:14:56.679> what<01:14:56.840> invariant<01:14:57.360> should<01:14:57.520> this 01:14:57.709 --> 01:14:57.719 align:start position:0% what should what invariant should this 01:14:57.719 --> 01:14:59.470 align:start position:0% what should what invariant should this satisfy<01:14:58.199> what<01:14:58.280> are<01:14:58.400> the<01:14:58.600> properties<01:14:59.080> that<01:14:59.239> I'm 01:14:59.470 --> 01:14:59.480 align:start position:0% satisfy what are the properties that I'm 01:14:59.480 --> 01:15:02.870 align:start position:0% satisfy what are the properties that I'm actually<01:15:00.199> coding<01:15:00.719> for 01:15:02.870 --> 01:15:02.880 align:start position:0% actually coding for 01:15:02.880 --> 01:15:04.870 align:start position:0% actually coding for and<01:15:03.880> document 01:15:04.870 --> 01:15:04.880 align:start position:0% and document 01:15:04.880 --> 01:15:07.310 align:start position:0% and document it<01:15:05.880> great<01:15:06.199> if<01:15:06.320> it<01:15:06.480> can<01:15:06.639> be<01:15:06.760> a<01:15:06.880> formal 01:15:07.310 --> 01:15:07.320 align:start position:0% it great if it can be a formal 01:15:07.320 --> 01:15:09.669 align:start position:0% it great if it can be a formal specification<01:15:08.320> fantastic<01:15:09.239> right<01:15:09.400> because 01:15:09.669 --> 01:15:09.679 align:start position:0% specification fantastic right because 01:15:09.679 --> 01:15:11.790 align:start position:0% specification fantastic right because then<01:15:09.800> we<01:15:09.920> can<01:15:10.199> use<01:15:10.400> formal<01:15:10.719> verification 01:15:11.790 --> 01:15:11.800 align:start position:0% then we can use formal verification 01:15:11.800 --> 01:15:16.229 align:start position:0% then we can use formal verification tools<01:15:12.800> but<01:15:13.440> let's<01:15:13.679> even<01:15:13.880> lower<01:15:14.199> the<01:15:14.320> bar<01:15:15.239> right 01:15:16.229 --> 01:15:16.239 align:start position:0% tools but let's even lower the bar right 01:15:16.239 --> 01:15:17.629 align:start position:0% tools but let's even lower the bar right write<01:15:16.440> it<01:15:16.600> in<01:15:16.800> plain 01:15:17.629 --> 01:15:17.639 align:start position:0% write it in plain 01:15:17.639 --> 01:15:21.030 align:start position:0% write it in plain English<01:15:18.639> what<01:15:18.800> is<01:15:19.320> my<01:15:19.480> code<01:15:19.800> supposed<01:15:20.159> to 01:15:21.030 --> 01:15:21.040 align:start position:0% English what is my code supposed to 01:15:21.040 --> 01:15:23.470 align:start position:0% English what is my code supposed to do<01:15:22.040> that<01:15:22.280> is<01:15:22.440> super<01:15:22.719> critical<01:15:23.040> for<01:15:23.199> all<01:15:23.360> the 01:15:23.470 --> 01:15:23.480 align:start position:0% do that is super critical for all the 01:15:23.480 --> 01:15:25.550 align:start position:0% do that is super critical for all the researchers<01:15:24.280> and<01:15:24.480> reviewers<01:15:25.120> who<01:15:25.280> look<01:15:25.440> at 01:15:25.550 --> 01:15:25.560 align:start position:0% researchers and reviewers who look at 01:15:25.560 --> 01:15:28.669 align:start position:0% researchers and reviewers who look at your<01:15:25.719> code<01:15:25.960> basee<01:15:26.320> Nat<01:15:26.600> talked<01:15:26.880> about<01:15:27.159> this<01:15:27.639> as 01:15:28.669 --> 01:15:28.679 align:start position:0% your code basee Nat talked about this as 01:15:28.679 --> 01:15:30.990 align:start position:0% your code basee Nat talked about this as well<01:15:29.679> document 01:15:30.990 --> 01:15:31.000 align:start position:0% well document 01:15:31.000 --> 01:15:34.030 align:start position:0% well document everything<01:15:32.000> right<01:15:32.800> put<01:15:33.040> it<01:15:33.159> in<01:15:33.440> quote 01:15:34.030 --> 01:15:34.040 align:start position:0% everything right put it in quote 01:15:34.040 --> 01:15:37.870 align:start position:0% everything right put it in quote comments<01:15:35.040> inline<01:15:35.679> comments<01:15:36.880> Communications 01:15:37.870 --> 01:15:37.880 align:start position:0% comments inline comments Communications 01:15:37.880 --> 01:15:40.950 align:start position:0% comments inline comments Communications is<01:15:38.760> going<01:15:38.920> to<01:15:39.040> be<01:15:39.239> super<01:15:39.639> critical<01:15:40.520> in<01:15:40.679> the 01:15:40.950 --> 01:15:40.960 align:start position:0% is going to be super critical in the 01:15:40.960 --> 01:15:42.430 align:start position:0% is going to be super critical in the space<01:15:41.320> and<01:15:41.480> all<01:15:41.639> of<01:15:41.760> us<01:15:41.880> are<01:15:42.120> sort<01:15:42.320> of 01:15:42.430 --> 01:15:42.440 align:start position:0% space and all of us are sort of 01:15:42.440 --> 01:15:44.310 align:start position:0% space and all of us are sort of repeating<01:15:43.000> all<01:15:43.159> this<01:15:43.320> over<01:15:43.480> and<01:15:43.639> over<01:15:43.880> again 01:15:44.310 --> 01:15:44.320 align:start position:0% repeating all this over and over again 01:15:44.320 --> 01:15:45.470 align:start position:0% repeating all this over and over again because<01:15:44.560> it's<01:15:44.760> really<01:15:45.080> all<01:15:45.280> these 01:15:45.470 --> 01:15:45.480 align:start position:0% because it's really all these 01:15:45.480 --> 01:15:47.830 align:start position:0% because it's really all these fundamental<01:15:46.080> principles<01:15:46.600> that<01:15:46.800> apply<01:15:47.600> so 01:15:47.830 --> 01:15:47.840 align:start position:0% fundamental principles that apply so 01:15:47.840 --> 01:15:50.189 align:start position:0% fundamental principles that apply so readed<01:15:48.360> as<01:15:48.480> a<01:15:48.600> security<01:15:49.040> researcher<01:15:49.639> read<01:15:49.960> all 01:15:50.189 --> 01:15:50.199 align:start position:0% readed as a security researcher read all 01:15:50.199 --> 01:15:52.110 align:start position:0% readed as a security researcher read all this<01:15:50.719> hopefully<01:15:51.040> the<01:15:51.159> devs<01:15:51.480> have<01:15:51.639> written<01:15:51.920> up 01:15:52.110 --> 01:15:52.120 align:start position:0% this hopefully the devs have written up 01:15:52.120 --> 01:15:53.110 align:start position:0% this hopefully the devs have written up all 01:15:53.110 --> 01:15:53.120 align:start position:0% all 01:15:53.120 --> 01:15:55.830 align:start position:0% all this<01:15:54.120> ask 01:15:55.830 --> 01:15:55.840 align:start position:0% this ask 01:15:55.840 --> 01:16:00.430 align:start position:0% this ask ask<01:15:56.239> questions<01:15:57.239> be<01:15:57.679> direct<01:15:58.679> in<01:15:59.199> asking<01:15:59.679> your 01:16:00.430 --> 01:16:00.440 align:start position:0% ask questions be direct in asking your 01:16:00.440 --> 01:16:03.229 align:start position:0% ask questions be direct in asking your uh<01:16:00.560> protocol<01:16:01.080> teams<01:16:01.639> or<01:16:02.000> your<01:16:02.840> on<01:16:03.040> your 01:16:03.229 --> 01:16:03.239 align:start position:0% uh protocol teams or your on your 01:16:03.239 --> 01:16:06.310 align:start position:0% uh protocol teams or your on your favorite<01:16:03.880> contest<01:16:04.239> or<01:16:04.400> Bounty<01:16:04.800> platforms<01:16:05.520> ask 01:16:06.310 --> 01:16:06.320 align:start position:0% favorite contest or Bounty platforms ask 01:16:06.320 --> 01:16:07.669 align:start position:0% favorite contest or Bounty platforms ask you<01:16:06.440> may<01:16:06.600> not<01:16:06.760> get<01:16:06.960> the<01:16:07.120> answer<01:16:07.440> but<01:16:07.560> it 01:16:07.669 --> 01:16:07.679 align:start position:0% you may not get the answer but it 01:16:07.679 --> 01:16:09.229 align:start position:0% you may not get the answer but it doesn't 01:16:09.229 --> 01:16:09.239 align:start position:0% doesn't 01:16:09.239 --> 01:16:12.310 align:start position:0% doesn't hurt<01:16:10.239> and<01:16:10.400> ultimately<01:16:11.120> try<01:16:11.320> to<01:16:11.560> infer<01:16:12.000> some<01:16:12.159> of 01:16:12.310 --> 01:16:12.320 align:start position:0% hurt and ultimately try to infer some of 01:16:12.320 --> 01:16:13.830 align:start position:0% hurt and ultimately try to infer some of these<01:16:12.520> if<01:16:12.600> you<01:16:12.719> don't<01:16:12.880> get<01:16:13.040> the<01:16:13.199> answers<01:16:13.719> right 01:16:13.830 --> 01:16:13.840 align:start position:0% these if you don't get the answers right 01:16:13.840 --> 01:16:15.350 align:start position:0% these if you don't get the answers right so<01:16:14.040> that's<01:16:14.400> that's<01:16:14.600> possible<01:16:15.000> as<01:16:15.120> well 01:16:15.350 --> 01:16:15.360 align:start position:0% so that's that's possible as well 01:16:15.360 --> 01:16:17.910 align:start position:0% so that's that's possible as well there's<01:16:15.560> a<01:16:16.400> uh<01:16:16.560> fantastic<01:16:17.040> area<01:16:17.280> of<01:16:17.440> research 01:16:17.910 --> 01:16:17.920 align:start position:0% there's a uh fantastic area of research 01:16:17.920 --> 01:16:19.669 align:start position:0% there's a uh fantastic area of research where<01:16:18.080> you<01:16:18.199> can<01:16:18.360> actually<01:16:18.639> infer<01:16:19.080> inv<01:16:19.320> variant 01:16:19.669 --> 01:16:19.679 align:start position:0% where you can actually infer inv variant 01:16:19.679 --> 01:16:21.709 align:start position:0% where you can actually infer inv variant and<01:16:19.800> a<01:16:19.920> simple<01:16:20.239> way<01:16:20.360> of<01:16:20.520> thinking<01:16:20.800> about<01:16:21.000> it<01:16:21.199> is 01:16:21.709 --> 01:16:21.719 align:start position:0% and a simple way of thinking about it is 01:16:21.719 --> 01:16:23.390 align:start position:0% and a simple way of thinking about it is inconsistent<01:16:22.480> checks<01:16:22.800> if<01:16:22.920> there<01:16:23.000> are<01:16:23.159> some 01:16:23.390 --> 01:16:23.400 align:start position:0% inconsistent checks if there are some 01:16:23.400 --> 01:16:25.470 align:start position:0% inconsistent checks if there are some checks<01:16:24.159> if<01:16:24.280> there<01:16:24.400> are<01:16:24.560> checks<01:16:25.080> in<01:16:25.239> some 01:16:25.470 --> 01:16:25.480 align:start position:0% checks if there are checks in some 01:16:25.480 --> 01:16:28.350 align:start position:0% checks if there are checks in some places<01:16:25.800> and<01:16:26.400> not<01:16:27.400> then<01:16:27.719> it's<01:16:27.960> either<01:16:28.159> an 01:16:28.350 --> 01:16:28.360 align:start position:0% places and not then it's either an 01:16:28.360 --> 01:16:30.750 align:start position:0% places and not then it's either an invariant<01:16:29.040> or<01:16:29.280> those<01:16:29.440> missing<01:16:29.760> checks<01:16:30.120> are 01:16:30.750 --> 01:16:30.760 align:start position:0% invariant or those missing checks are 01:16:30.760 --> 01:16:32.629 align:start position:0% invariant or those missing checks are sort<01:16:30.920> of<01:16:31.120> exceptional<01:16:31.560> paths<01:16:32.120> so<01:16:32.320> try<01:16:32.480> to 01:16:32.629 --> 01:16:32.639 align:start position:0% sort of exceptional paths so try to 01:16:32.639 --> 01:16:34.950 align:start position:0% sort of exceptional paths so try to infer<01:16:33.239> looking<01:16:33.520> at<01:16:33.800> clues<01:16:34.199> in<01:16:34.320> the<01:16:34.480> code<01:16:34.760> and 01:16:34.950 --> 01:16:34.960 align:start position:0% infer looking at clues in the code and 01:16:34.960 --> 01:16:39.629 align:start position:0% infer looking at clues in the code and docs<01:16:35.320> and<01:16:35.480> so 01:16:39.629 --> 01:16:39.639 align:start position:0% 01:16:39.639 --> 01:16:43.910 align:start position:0% on<01:16:40.639> all<01:16:40.760> right<01:16:41.239> the<01:16:41.520> the<01:16:41.679> final<01:16:42.120> tip<01:16:42.800> is<01:16:43.679> just 01:16:43.910 --> 01:16:43.920 align:start position:0% on all right the the final tip is just 01:16:43.920 --> 01:16:49.110 align:start position:0% on all right the the final tip is just find<01:16:44.239> it<01:16:45.040> right<01:16:46.000> I<01:16:46.040> mean<01:16:46.560> we<01:16:47.199> tend<01:16:47.600> to 01:16:49.110 --> 01:16:49.120 align:start position:0% find it right I mean we tend to 01:16:49.120 --> 01:16:52.750 align:start position:0% find it right I mean we tend to um<01:16:50.120> talk<01:16:50.400> a<01:16:50.560> lot<01:16:50.920> think<01:16:51.159> a<01:16:51.320> lot<01:16:51.920> but<01:16:52.159> ultimately 01:16:52.750 --> 01:16:52.760 align:start position:0% um talk a lot think a lot but ultimately 01:16:52.760 --> 01:16:55.950 align:start position:0% um talk a lot think a lot but ultimately it<01:16:52.880> is<01:16:53.120> really<01:16:53.600> about 01:16:55.950 --> 01:16:55.960 align:start position:0% it is really about 01:16:55.960 --> 01:16:59.030 align:start position:0% it is really about reading<01:16:56.360> the<01:16:56.719> code<01:16:57.719> right<01:16:58.400> and<01:16:58.560> and<01:16:58.679> the<01:16:58.840> good 01:16:59.030 --> 01:16:59.040 align:start position:0% reading the code right and and the good 01:16:59.040 --> 01:17:01.550 align:start position:0% reading the code right and and the good good<01:16:59.239> part<01:16:59.400> of<01:16:59.520> the<01:16:59.719> space<01:17:00.239> is<01:17:00.719> most<01:17:00.960> of<01:17:01.280> these 01:17:01.550 --> 01:17:01.560 align:start position:0% good part of the space is most of these 01:17:01.560 --> 01:17:02.950 align:start position:0% good part of the space is most of these Protocols 01:17:02.950 --> 01:17:02.960 align:start position:0% Protocols 01:17:02.960 --> 01:17:05.910 align:start position:0% Protocols are<01:17:03.960> open<01:17:04.320> source<01:17:04.719> they<01:17:04.840> have<01:17:05.000> verified 01:17:05.910 --> 01:17:05.920 align:start position:0% are open source they have verified 01:17:05.920 --> 01:17:08.030 align:start position:0% are open source they have verified sources<01:17:06.840> so<01:17:07.000> you<01:17:07.120> can<01:17:07.320> actually<01:17:07.639> look<01:17:07.800> at<01:17:07.920> the 01:17:08.030 --> 01:17:08.040 align:start position:0% sources so you can actually look at the 01:17:08.040 --> 01:17:10.189 align:start position:0% sources so you can actually look at the code<01:17:08.320> base<01:17:08.880> right<01:17:09.080> and<01:17:09.199> know<01:17:09.440> that<01:17:09.639> okay<01:17:09.800> it's 01:17:10.189 --> 01:17:10.199 align:start position:0% code base right and know that okay it's 01:17:10.199 --> 01:17:12.149 align:start position:0% code base right and know that okay it's hopefully<01:17:10.560> the<01:17:10.760> same<01:17:11.000> one<01:17:11.480> that<01:17:11.600> was<01:17:11.760> reviewed 01:17:12.149 --> 01:17:12.159 align:start position:0% hopefully the same one that was reviewed 01:17:12.159 --> 01:17:15.709 align:start position:0% hopefully the same one that was reviewed was<01:17:12.639> deployed<01:17:13.639> look<01:17:13.800> at<01:17:13.960> the<01:17:14.280> code<01:17:15.280> there<01:17:15.480> is 01:17:15.709 --> 01:17:15.719 align:start position:0% was deployed look at the code there is 01:17:15.719 --> 01:17:18.270 align:start position:0% was deployed look at the code there is no<01:17:15.960> buck<01:17:16.280> free<01:17:16.520> code<01:17:17.040> it<01:17:17.159> may<01:17:17.360> not<01:17:17.560> be<01:17:17.800> the<01:17:18.159> you 01:17:18.270 --> 01:17:18.280 align:start position:0% no buck free code it may not be the you 01:17:18.280 --> 01:17:21.189 align:start position:0% no buck free code it may not be the you know<01:17:18.440> critical<01:17:19.239> criticals<01:17:19.719> or<01:17:19.920> the<01:17:20.080> highs<01:17:21.000> but 01:17:21.189 --> 01:17:21.199 align:start position:0% know critical criticals or the highs but 01:17:21.199 --> 01:17:24.510 align:start position:0% know critical criticals or the highs but it<01:17:21.400> may<01:17:21.639> be<01:17:22.159> the<01:17:22.280> lows<01:17:22.600> and<01:17:22.760> the<01:17:23.040> infos<01:17:24.040> but 01:17:24.510 --> 01:17:24.520 align:start position:0% it may be the lows and the infos but 01:17:24.520 --> 01:17:27.830 align:start position:0% it may be the lows and the infos but there<01:17:24.920> are<01:17:25.120> bugs<01:17:25.920> right<01:17:26.480> read<01:17:26.800> the<01:17:26.960> code<01:17:27.560> find 01:17:27.830 --> 01:17:27.840 align:start position:0% there are bugs right read the code find 01:17:27.840 --> 01:17:31.270 align:start position:0% there are bugs right read the code find the<01:17:28.080> bugs<01:17:29.080> and<01:17:29.280> like<01:17:29.480> all<01:17:29.639> of<01:17:29.760> us<01:17:29.880> have<01:17:30.280> said 01:17:31.270 --> 01:17:31.280 align:start position:0% the bugs and like all of us have said 01:17:31.280 --> 01:17:34.149 align:start position:0% the bugs and like all of us have said both<01:17:31.480> for<01:17:31.719> devs<01:17:32.440> and<01:17:32.639> for 01:17:34.149 --> 01:17:34.159 align:start position:0% both for devs and for 01:17:34.159 --> 01:17:36.950 align:start position:0% both for devs and for researchers<01:17:35.159> I<01:17:35.239> think<01:17:35.480> success<01:17:36.239> you<01:17:36.360> know<01:17:36.840> we 01:17:36.950 --> 01:17:36.960 align:start position:0% researchers I think success you know we 01:17:36.960 --> 01:17:38.910 align:start position:0% researchers I think success you know we may<01:17:37.159> think<01:17:37.320> of<01:17:37.480> overnight<01:17:37.920> successes<01:17:38.480> but<01:17:38.800> we 01:17:38.910 --> 01:17:38.920 align:start position:0% may think of overnight successes but we 01:17:38.920 --> 01:17:41.229 align:start position:0% may think of overnight successes but we don't<01:17:39.159> see<01:17:39.600> the<01:17:40.159> sort<01:17:40.360> of<01:17:40.520> the<01:17:40.679> we<01:17:40.880> see<01:17:41.000> the<01:17:41.080> tip 01:17:41.229 --> 01:17:41.239 align:start position:0% don't see the sort of the we see the tip 01:17:41.239 --> 01:17:43.830 align:start position:0% don't see the sort of the we see the tip of<01:17:41.320> the<01:17:41.440> iceberg<01:17:42.120> but<01:17:42.280> there<01:17:42.400> is<01:17:42.560> a<01:17:42.920> lot<01:17:43.199> of 01:17:43.830 --> 01:17:43.840 align:start position:0% of the iceberg but there is a lot of 01:17:43.840 --> 01:17:46.070 align:start position:0% of the iceberg but there is a lot of preparation<01:17:44.840> that<01:17:45.239> people<01:17:45.520> have<01:17:45.679> done<01:17:45.960> right 01:17:46.070 --> 01:17:46.080 align:start position:0% preparation that people have done right 01:17:46.080 --> 01:17:49.110 align:start position:0% preparation that people have done right people<01:17:46.280> have<01:17:46.440> spent<01:17:47.159> uh<01:17:47.520> years<01:17:48.000> decades<01:17:48.960> in 01:17:49.110 --> 01:17:49.120 align:start position:0% people have spent uh years decades in 01:17:49.120 --> 01:17:52.910 align:start position:0% people have spent uh years decades in different<01:17:49.560> different<01:17:50.320> ways<01:17:51.760> practice<01:17:52.760> and 01:17:52.910 --> 01:17:52.920 align:start position:0% different different ways practice and 01:17:52.920 --> 01:17:57.110 align:start position:0% different different ways practice and then<01:17:53.120> ultimately<01:17:53.719> patience 01:17:57.110 --> 01:17:57.120 align:start position:0% 01:17:57.120 --> 01:17:59.189 align:start position:0% so<01:17:57.360> I<01:17:57.480> have<01:17:57.760> I<01:17:57.840> have<01:17:57.960> the<01:17:58.080> pleasure<01:17:58.440> of<01:17:58.800> U<01:17:59.000> also 01:17:59.189 --> 01:17:59.199 align:start position:0% so I have I have the pleasure of U also 01:17:59.199 --> 01:18:02.550 align:start position:0% so I have I have the pleasure of U also sort<01:17:59.360> of<01:17:59.560> summarizing<01:18:00.560> a<01:18:00.719> lot<01:18:00.880> of<01:18:01.560> all<01:18:01.760> these 01:18:02.550 --> 01:18:02.560 align:start position:0% sort of summarizing a lot of all these 01:18:02.560 --> 01:18:06.510 align:start position:0% sort of summarizing a lot of all these steps<01:18:03.560> we'll<01:18:03.760> do<01:18:03.960> that<01:18:04.080> in<01:18:04.199> the<01:18:04.320> next<01:18:04.560> two<01:18:05.560> um 01:18:06.510 --> 01:18:06.520 align:start position:0% steps we'll do that in the next two um 01:18:06.520 --> 01:18:09.470 align:start position:0% steps we'll do that in the next two um next<01:18:06.760> two<01:18:07.679> slides<01:18:08.280> and<01:18:08.480> then<01:18:08.719> we<01:18:08.920> will<01:18:09.239> have 01:18:09.470 --> 01:18:09.480 align:start position:0% next two slides and then we will have 01:18:09.480 --> 01:18:12.149 align:start position:0% next two slides and then we will have time<01:18:09.679> for<01:18:10.000> questions<01:18:10.480> we<01:18:10.679> have<01:18:10.920> 10<01:18:11.480> minutes 01:18:12.149 --> 01:18:12.159 align:start position:0% time for questions we have 10 minutes 01:18:12.159 --> 01:18:13.830 align:start position:0% time for questions we have 10 minutes and<01:18:12.280> then<01:18:12.440> there's<01:18:12.639> also<01:18:12.840> a<01:18:12.960> fun 01:18:13.830 --> 01:18:13.840 align:start position:0% and then there's also a fun 01:18:13.840 --> 01:18:16.950 align:start position:0% and then there's also a fun contest<01:18:14.840> so<01:18:15.159> quickly<01:18:15.920> right<01:18:16.199> for 01:18:16.950 --> 01:18:16.960 align:start position:0% contest so quickly right for 01:18:16.960 --> 01:18:21.709 align:start position:0% contest so quickly right for devs<01:18:17.960> before<01:18:18.239> you<01:18:18.560> code<01:18:19.560> specify<01:18:20.159> and<01:18:20.719> design 01:18:21.709 --> 01:18:21.719 align:start position:0% devs before you code specify and design 01:18:21.719 --> 01:18:25.470 align:start position:0% devs before you code specify and design and<01:18:22.440> after<01:18:22.960> and<01:18:23.159> during<01:18:23.560> you<01:18:23.760> Code<01:18:24.400> test 01:18:25.470 --> 01:18:25.480 align:start position:0% and after and during you Code test 01:18:25.480 --> 01:18:28.550 align:start position:0% and after and during you Code test right<01:18:25.639> so<01:18:25.880> this<01:18:26.000> is<01:18:26.280> not<01:18:26.560> I<01:18:26.639> mean<01:18:27.080> it<01:18:28.080> it's<01:18:28.360> it's 01:18:28.550 --> 01:18:28.560 align:start position:0% right so this is not I mean it it's it's 01:18:28.560 --> 01:18:30.189 align:start position:0% right so this is not I mean it it's it's written<01:18:28.920> as<01:18:29.040> sort<01:18:29.199> of<01:18:29.280> a<01:18:29.360> linear<01:18:29.800> thing<01:18:30.080> but 01:18:30.189 --> 01:18:30.199 align:start position:0% written as sort of a linear thing but 01:18:30.199 --> 01:18:32.149 align:start position:0% written as sort of a linear thing but it's<01:18:30.400> really<01:18:30.639> sort<01:18:30.800> of<01:18:30.880> a<01:18:31.000> cyclical<01:18:31.480> thing<01:18:31.960> it 01:18:32.149 --> 01:18:32.159 align:start position:0% it's really sort of a cyclical thing it 01:18:32.159 --> 01:18:34.830 align:start position:0% it's really sort of a cyclical thing it it<01:18:32.320> happens<01:18:32.760> it's<01:18:32.840> a<01:18:32.960> helical<01:18:33.360> model<01:18:34.199> so<01:18:34.560> do 01:18:34.830 --> 01:18:34.840 align:start position:0% it happens it's a helical model so do 01:18:34.840 --> 01:18:37.510 align:start position:0% it happens it's a helical model so do that<01:18:35.480> repeatedly<01:18:36.480> think<01:18:36.719> about<01:18:37.120> assets 01:18:37.510 --> 01:18:37.520 align:start position:0% that repeatedly think about assets 01:18:37.520 --> 01:18:40.070 align:start position:0% that repeatedly think about assets actors<01:18:37.840> and<01:18:38.080> actions<01:18:38.679> actions<01:18:39.600> think<01:18:39.800> about 01:18:40.070 --> 01:18:40.080 align:start position:0% actors and actions actions think about 01:18:40.080 --> 01:18:42.950 align:start position:0% actors and actions actions think about where<01:18:40.320> assets<01:18:40.760> leave<01:18:41.000> your 01:18:42.950 --> 01:18:42.960 align:start position:0% where assets leave your 01:18:42.960 --> 01:18:45.950 align:start position:0% where assets leave your system<01:18:43.960> security<01:18:44.440> mindset<01:18:45.120> is<01:18:45.360> critical<01:18:45.800> in 01:18:45.950 --> 01:18:45.960 align:start position:0% system security mindset is critical in 01:18:45.960 --> 01:18:47.990 align:start position:0% system security mindset is critical in this<01:18:46.120> space<01:18:46.560> both<01:18:46.719> for<01:18:46.920> devs<01:18:47.360> and<01:18:47.679> and<01:18:47.840> the 01:18:47.990 --> 01:18:48.000 align:start position:0% this space both for devs and and the 01:18:48.000 --> 01:18:49.149 align:start position:0% this space both for devs and and the security 01:18:49.149 --> 01:18:49.159 align:start position:0% security 01:18:49.159 --> 01:18:53.350 align:start position:0% security researchers<01:18:50.159> shift<01:18:50.639> left<01:18:51.239> which<01:18:51.440> is<01:18:52.120> a<01:18:53.120> really 01:18:53.350 --> 01:18:53.360 align:start position:0% researchers shift left which is a really 01:18:53.360 --> 01:18:55.510 align:start position:0% researchers shift left which is a really well-known<01:18:53.800> thing<01:18:53.960> in<01:18:54.040> the<01:18:54.199> space<01:18:55.080> and<01:18:55.239> all<01:18:55.400> it 01:18:55.510 --> 01:18:55.520 align:start position:0% well-known thing in the space and all it 01:18:55.520 --> 01:18:59.470 align:start position:0% well-known thing in the space and all it means<01:18:55.960> is<01:18:56.600> that<01:18:57.120> let's<01:18:57.400> not<01:18:57.719> wait<01:18:58.440> for<01:18:59.320> you 01:18:59.470 --> 01:18:59.480 align:start position:0% means is that let's not wait for you 01:18:59.480 --> 01:19:03.870 align:start position:0% means is that let's not wait for you know<01:19:00.199> uh<01:19:01.199> test<01:19:01.480> in<01:19:01.719> prod<01:19:02.080> kind<01:19:02.239> of<01:19:02.360> a<01:19:02.840> meme 01:19:03.870 --> 01:19:03.880 align:start position:0% know uh test in prod kind of a meme 01:19:03.880 --> 01:19:06.350 align:start position:0% know uh test in prod kind of a meme right<01:19:04.880> think<01:19:05.120> about<01:19:05.400> Security<01:19:05.920> even<01:19:06.159> before 01:19:06.350 --> 01:19:06.360 align:start position:0% right think about Security even before 01:19:06.360 --> 01:19:09.070 align:start position:0% right think about Security even before you<01:19:06.520> start<01:19:06.920> coding<01:19:07.920> for<01:19:08.120> the 01:19:09.070 --> 01:19:09.080 align:start position:0% you start coding for the 01:19:09.080 --> 01:19:11.550 align:start position:0% you start coding for the devs<01:19:10.080> think<01:19:10.320> about<01:19:10.760> I<01:19:10.840> mean<01:19:11.080> that's<01:19:11.320> that's 01:19:11.550 --> 01:19:11.560 align:start position:0% devs think about I mean that's that's 01:19:11.560 --> 01:19:14.030 align:start position:0% devs think about I mean that's that's really<01:19:12.199> what<01:19:12.800> that's<01:19:13.040> really<01:19:13.320> the<01:19:13.920> uh 01:19:14.030 --> 01:19:14.040 align:start position:0% really what that's really the uh 01:19:14.040 --> 01:19:16.669 align:start position:0% really what that's really the uh environment<01:19:14.520> we<01:19:14.600> are<01:19:14.719> in<01:19:15.520> in<01:19:15.679> in<01:19:15.800> this<01:19:16.040> case 01:19:16.669 --> 01:19:16.679 align:start position:0% environment we are in in in this case 01:19:16.679 --> 01:19:20.350 align:start position:0% environment we are in in in this case right<01:19:17.679> test<01:19:18.120> properties<01:19:18.840> trest<01:19:19.360> invariance 01:19:20.350 --> 01:19:20.360 align:start position:0% right test properties trest invariance 01:19:20.360 --> 01:19:22.830 align:start position:0% right test properties trest invariance use<01:19:20.600> your<01:19:20.880> favorite<01:19:21.280> tool<01:19:21.840> it<01:19:22.000> could<01:19:22.239> be<01:19:22.719> you 01:19:22.830 --> 01:19:22.840 align:start position:0% use your favorite tool it could be you 01:19:22.840 --> 01:19:24.709 align:start position:0% use your favorite tool it could be you know<01:19:23.199> the<01:19:23.679> the<01:19:23.800> the<01:19:23.920> provs<01:19:24.280> we<01:19:24.360> have<01:19:24.480> some 01:19:24.709 --> 01:19:24.719 align:start position:0% know the the the provs we have some 01:19:24.719 --> 01:19:27.950 align:start position:0% know the the the provs we have some fantastic<01:19:25.159> ones<01:19:26.000> from<01:19:26.600> um<01:19:27.120> uh<01:19:27.239> the<01:19:27.360> serator 01:19:27.950 --> 01:19:27.960 align:start position:0% fantastic ones from um uh the serator 01:19:27.960 --> 01:19:31.310 align:start position:0% fantastic ones from um uh the serator approver<01:19:28.840> use<01:19:29.480> use<01:19:29.840> fuzzing<01:19:30.520> we<01:19:30.679> have<01:19:31.239> the 01:19:31.310 --> 01:19:31.320 align:start position:0% approver use use fuzzing we have the 01:19:31.320 --> 01:19:35.510 align:start position:0% approver use use fuzzing we have the Medusa<01:19:32.080> from<01:19:32.639> um<01:19:33.199> from<01:19:33.440> Trailer<01:19:34.000> bits<01:19:35.000> use 01:19:35.510 --> 01:19:35.520 align:start position:0% Medusa from um from Trailer bits use 01:19:35.520 --> 01:19:37.910 align:start position:0% Medusa from um from Trailer bits use simpler<01:19:35.960> static<01:19:36.320> analysis<01:19:36.760> tools<01:19:37.360> we<01:19:37.520> have<01:19:37.719> so 01:19:37.910 --> 01:19:37.920 align:start position:0% simpler static analysis tools we have so 01:19:37.920 --> 01:19:41.070 align:start position:0% simpler static analysis tools we have so many<01:19:38.120> of<01:19:38.320> them<01:19:39.000> as<01:19:39.120> an<01:19:39.320> example 01:19:41.070 --> 01:19:41.080 align:start position:0% many of them as an example 01:19:41.080 --> 01:19:44.669 align:start position:0% many of them as an example Slither<01:19:42.080> and<01:19:42.360> if<01:19:42.679> if<01:19:42.800> you're<01:19:43.360> U<01:19:43.960> more<01:19:44.159> into<01:19:44.400> bug 01:19:44.669 --> 01:19:44.679 align:start position:0% Slither and if if you're U more into bug 01:19:44.679 --> 01:19:47.229 align:start position:0% Slither and if if you're U more into bug bounties<01:19:45.400> you<01:19:45.600> have<01:19:46.199> various<01:19:46.520> tools<01:19:46.920> there<01:19:47.120> as 01:19:47.229 --> 01:19:47.239 align:start position:0% bounties you have various tools there as 01:19:47.239 --> 01:19:49.830 align:start position:0% bounties you have various tools there as well<01:19:47.480> use<01:19:48.159> Foundry 01:19:49.830 --> 01:19:49.840 align:start position:0% well use Foundry 01:19:49.840 --> 01:19:53.229 align:start position:0% well use Foundry use<01:19:50.840> solo<01:19:51.320> D<01:19:51.679> to<01:19:52.199> as<01:19:52.280> an<01:19:52.440> example<01:19:52.840> to<01:19:52.960> look<01:19:53.120> at 01:19:53.229 --> 01:19:53.239 align:start position:0% use solo D to as an example to look at 01:19:53.239 --> 01:19:55.430 align:start position:0% use solo D to as an example to look at some<01:19:53.360> of<01:19:53.480> the<01:19:53.639> P<01:19:53.920> to<01:19:54.000> learn<01:19:54.199> from<01:19:54.320> the<01:19:54.440> past 01:19:55.430 --> 01:19:55.440 align:start position:0% some of the P to learn from the past 01:19:55.440 --> 01:19:58.070 align:start position:0% some of the P to learn from the past use<01:19:55.840> glider<01:19:56.360> to<01:19:56.520> look<01:19:56.679> at<01:19:57.199> things<01:19:57.560> on<01:19:57.679> the<01:19:57.800> main 01:19:58.070 --> 01:19:58.080 align:start position:0% use glider to look at things on the main 01:19:58.080 --> 01:20:00.870 align:start position:0% use glider to look at things on the main net<01:19:58.480> there<01:19:58.639> are<01:19:58.920> so<01:19:59.080> many<01:19:59.320> of<01:19:59.520> these 01:20:00.870 --> 01:20:00.880 align:start position:0% net there are so many of these 01:20:00.880 --> 01:20:04.110 align:start position:0% net there are so many of these tools<01:20:01.880> play<01:20:02.120> around<01:20:02.400> with<01:20:02.560> them<01:20:03.120> right<01:20:03.400> I<01:20:03.480> mean 01:20:04.110 --> 01:20:04.120 align:start position:0% tools play around with them right I mean 01:20:04.120 --> 01:20:05.910 align:start position:0% tools play around with them right I mean some<01:20:04.320> of<01:20:04.480> them<01:20:04.800> may 01:20:05.910 --> 01:20:05.920 align:start position:0% some of them may 01:20:05.920 --> 01:20:08.750 align:start position:0% some of them may really<01:20:06.920> work<01:20:07.159> for<01:20:07.360> you<01:20:07.520> some<01:20:07.679> of<01:20:07.800> them<01:20:08.040> not<01:20:08.639> and 01:20:08.750 --> 01:20:08.760 align:start position:0% really work for you some of them not and 01:20:08.760 --> 01:20:10.390 align:start position:0% really work for you some of them not and for<01:20:08.920> the<01:20:09.040> devs<01:20:09.400> obviously<01:20:09.719> the<01:20:09.840> buck<01:20:10.040> bounties 01:20:10.390 --> 01:20:10.400 align:start position:0% for the devs obviously the buck bounties 01:20:10.400 --> 01:20:12.990 align:start position:0% for the devs obviously the buck bounties and<01:20:10.719> you<01:20:10.840> know<01:20:11.320> things<01:20:11.560> may<01:20:11.719> not<01:20:12.199> may<01:20:12.360> not 01:20:12.990 --> 01:20:13.000 align:start position:0% and you know things may not may not 01:20:13.000 --> 01:20:17.030 align:start position:0% and you know things may not may not really<01:20:13.239> matter<01:20:14.159> uh<01:20:14.600> for<01:20:14.760> the<01:20:14.880> devs<01:20:15.800> but<01:20:16.800> all 01:20:17.030 --> 01:20:17.040 align:start position:0% really matter uh for the devs but all 01:20:17.040 --> 01:20:18.669 align:start position:0% really matter uh for the devs but all the<01:20:17.239> various<01:20:17.600> other<01:20:17.840> tools<01:20:18.320> right<01:20:18.440> there<01:20:18.520> are 01:20:18.669 --> 01:20:18.679 align:start position:0% the various other tools right there are 01:20:18.679 --> 01:20:19.910 align:start position:0% the various other tools right there are so<01:20:18.800> many<01:20:19.000> plugins<01:20:19.400> for<01:20:19.520> your<01:20:19.679> Dev 01:20:19.910 --> 01:20:19.920 align:start position:0% so many plugins for your Dev 01:20:19.920 --> 01:20:22.830 align:start position:0% so many plugins for your Dev environments<01:20:20.600> use<01:20:20.960> those<01:20:21.560> to<01:20:21.960> test<01:20:22.199> it<01:20:22.360> out 01:20:22.830 --> 01:20:22.840 align:start position:0% environments use those to test it out 01:20:22.840 --> 01:20:24.709 align:start position:0% environments use those to test it out there<01:20:22.960> are<01:20:23.159> testing<01:20:23.480> Frameworks<01:20:24.239> there<01:20:24.360> are 01:20:24.709 --> 01:20:24.719 align:start position:0% there are testing Frameworks there are 01:20:24.719 --> 01:20:27.629 align:start position:0% there are testing Frameworks there are ious<01:20:25.120> extensions<01:20:26.120> the<01:20:26.320> key<01:20:26.520> is<01:20:26.639> to<01:20:26.920> find<01:20:27.360> your 01:20:27.629 --> 01:20:27.639 align:start position:0% ious extensions the key is to find your 01:20:27.639 --> 01:20:30.709 align:start position:0% ious extensions the key is to find your tools<01:20:28.040> and<01:20:28.239> your<01:20:28.480> techniques<01:20:29.560> right<01:20:30.560> and 01:20:30.709 --> 01:20:30.719 align:start position:0% tools and your techniques right and 01:20:30.719 --> 01:20:32.430 align:start position:0% tools and your techniques right and there<01:20:30.840> are<01:20:31.159> we<01:20:31.400> we<01:20:31.600> I<01:20:31.679> mean<01:20:31.840> we<01:20:32.000> lucky<01:20:32.239> to<01:20:32.360> have 01:20:32.430 --> 01:20:32.440 align:start position:0% there are we we I mean we lucky to have 01:20:32.440 --> 01:20:35.149 align:start position:0% there are we we I mean we lucky to have a<01:20:32.560> good<01:20:33.239> choice<01:20:34.239> think<01:20:34.480> about<01:20:34.679> the<01:20:34.800> use<01:20:35.000> and 01:20:35.149 --> 01:20:35.159 align:start position:0% a good choice think about the use and 01:20:35.159 --> 01:20:37.950 align:start position:0% a good choice think about the use and abuse<01:20:35.600> scenarios<01:20:36.600> think<01:20:36.880> about<01:20:37.679> the 01:20:37.950 --> 01:20:37.960 align:start position:0% abuse scenarios think about the 01:20:37.960 --> 01:20:39.830 align:start position:0% abuse scenarios think about the adversarial<01:20:38.639> environment<01:20:39.360> think<01:20:39.560> about 01:20:39.830 --> 01:20:39.840 align:start position:0% adversarial environment think about 01:20:39.840 --> 01:20:40.990 align:start position:0% adversarial environment think about defense<01:20:40.159> and 01:20:40.990 --> 01:20:41.000 align:start position:0% defense and 01:20:41.000 --> 01:20:44.310 align:start position:0% defense and depth<01:20:42.000> right<01:20:42.320> because<01:20:43.040> if<01:20:43.560> there<01:20:43.679> is<01:20:43.960> any 01:20:44.310 --> 01:20:44.320 align:start position:0% depth right because if there is any 01:20:44.320 --> 01:20:46.149 align:start position:0% depth right because if there is any place<01:20:44.600> where<01:20:44.760> we<01:20:44.960> require<01:20:45.440> defensive 01:20:46.149 --> 01:20:46.159 align:start position:0% place where we require defensive 01:20:46.159 --> 01:20:49.550 align:start position:0% place where we require defensive programming<01:20:47.159> this<01:20:47.320> is<01:20:47.520> it<01:20:48.440> right<01:20:48.840> do<01:20:49.080> not 01:20:49.550 --> 01:20:49.560 align:start position:0% programming this is it right do not 01:20:49.560 --> 01:20:53.390 align:start position:0% programming this is it right do not assume<01:20:50.639> that<01:20:51.639> I<01:20:51.719> have<01:20:52.280> um<01:20:52.400> you<01:20:52.480> know<01:20:52.600> I<01:20:52.719> have<01:20:52.880> an 01:20:53.390 --> 01:20:53.400 align:start position:0% assume that I have um you know I have an 01:20:53.400 --> 01:20:55.590 align:start position:0% assume that I have um you know I have an um<01:20:53.639> I<01:20:53.719> have<01:20:53.840> an<01:20:53.960> array<01:20:54.320> and<01:20:54.639> it<01:20:54.719> won't<01:20:54.920> overflow 01:20:55.590 --> 01:20:55.600 align:start position:0% um I have an array and it won't overflow 01:20:55.600 --> 01:20:57.750 align:start position:0% um I have an array and it won't overflow right<01:20:55.800> or<01:20:56.000> I<01:20:56.120> have<01:20:56.360> this<01:20:56.520> code<01:20:56.880> path<01:20:57.400> nobody 01:20:57.750 --> 01:20:57.760 align:start position:0% right or I have this code path nobody 01:20:57.760 --> 01:21:00.709 align:start position:0% right or I have this code path nobody will<01:20:58.320> uh<01:20:58.920> it<01:20:59.040> won't<01:20:59.239> be<01:20:59.400> executed<01:21:00.120> or<01:21:00.320> nobody 01:21:00.709 --> 01:21:00.719 align:start position:0% will uh it won't be executed or nobody 01:21:00.719 --> 01:21:02.270 align:start position:0% will uh it won't be executed or nobody will 01:21:02.270 --> 01:21:02.280 align:start position:0% will 01:21:02.280 --> 01:21:06.870 align:start position:0% will um<01:21:03.280> create<01:21:03.600> a<01:21:03.760> pool<01:21:04.239> with<01:21:04.960> this<01:21:05.800> uh<01:21:06.280> weird 01:21:06.870 --> 01:21:06.880 align:start position:0% um create a pool with this uh weird 01:21:06.880 --> 01:21:10.270 align:start position:0% um create a pool with this uh weird erc20<01:21:07.679> token<01:21:08.520> right<01:21:09.040> do<01:21:09.280> not<01:21:09.639> make 01:21:10.270 --> 01:21:10.280 align:start position:0% erc20 token right do not make 01:21:10.280 --> 01:21:13.070 align:start position:0% erc20 token right do not make assumptions<01:21:11.280> right<01:21:11.800> and<01:21:11.960> for<01:21:12.159> devs<01:21:12.719> in<01:21:12.880> this 01:21:13.070 --> 01:21:13.080 align:start position:0% assumptions right and for devs in this 01:21:13.080 --> 01:21:17.270 align:start position:0% assumptions right and for devs in this case<01:21:13.960> um<01:21:14.800> yeah<01:21:15.280> so<01:21:16.280> won't<01:21:16.520> repeat<01:21:16.960> we're<01:21:17.159> out 01:21:17.270 --> 01:21:17.280 align:start position:0% case um yeah so won't repeat we're out 01:21:17.280 --> 01:21:18.390 align:start position:0% case um yeah so won't repeat we're out of<01:21:17.440> time<01:21:17.560> we<01:21:17.679> want<01:21:17.760> to<01:21:17.880> save<01:21:18.080> time<01:21:18.199> for 01:21:18.390 --> 01:21:18.400 align:start position:0% of time we want to save time for 01:21:18.400 --> 01:21:21.790 align:start position:0% of time we want to save time for questions<01:21:18.800> as<01:21:18.960> well<01:21:19.719> but<01:21:20.719> all<01:21:20.960> these<01:21:21.159> things 01:21:21.790 --> 01:21:21.800 align:start position:0% questions as well but all these things 01:21:21.800 --> 01:21:23.830 align:start position:0% questions as well but all these things right<01:21:22.800> and<01:21:22.960> all<01:21:23.080> these<01:21:23.239> slides<01:21:23.520> will<01:21:23.679> be 01:21:23.830 --> 01:21:23.840 align:start position:0% right and all these slides will be 01:21:23.840 --> 01:21:26.590 align:start position:0% right and all these slides will be available<01:21:24.760> uh<01:21:24.960> soon<01:21:25.679> the<01:21:25.800> video<01:21:26.120> I<01:21:26.199> believe<01:21:26.440> is 01:21:26.590 --> 01:21:26.600 align:start position:0% available uh soon the video I believe is 01:21:26.600 --> 01:21:28.950 align:start position:0% available uh soon the video I believe is being<01:21:26.840> live<01:21:27.080> streamed<01:21:27.880> but<01:21:28.199> the<01:21:28.360> bottom<01:21:28.679> one<01:21:28.880> I 01:21:28.950 --> 01:21:28.960 align:start position:0% being live streamed but the bottom one I 01:21:28.960 --> 01:21:31.350 align:start position:0% being live streamed but the bottom one I think<01:21:29.080> is<01:21:29.239> critical<01:21:29.719> right<01:21:30.120> we<01:21:30.320> tend<01:21:30.520> to<01:21:30.639> get 01:21:31.350 --> 01:21:31.360 align:start position:0% think is critical right we tend to get 01:21:31.360 --> 01:21:34.390 align:start position:0% think is critical right we tend to get overwhelmed<01:21:32.360> but<01:21:33.000> take<01:21:33.280> care<01:21:33.560> of<01:21:33.719> your<01:21:33.960> code 01:21:34.390 --> 01:21:34.400 align:start position:0% overwhelmed but take care of your code 01:21:34.400 --> 01:21:37.070 align:start position:0% overwhelmed but take care of your code as<01:21:34.600> devs<01:21:35.040> from<01:21:35.199> a<01:21:35.360> security<01:21:35.920> perspective<01:21:36.920> and 01:21:37.070 --> 01:21:37.080 align:start position:0% as devs from a security perspective and 01:21:37.080 --> 01:21:39.310 align:start position:0% as devs from a security perspective and more<01:21:37.280> importantly<01:21:37.760> take<01:21:37.960> care<01:21:38.120> of<01:21:38.320> yourself 01:21:39.310 --> 01:21:39.320 align:start position:0% more importantly take care of yourself 01:21:39.320 --> 01:21:47.669 align:start position:0% more importantly take care of yourself well<01:21:39.600> with<01:21:39.760> that<01:21:40.000> thank 01:21:47.669 --> 01:21:47.679 align:start position:0% 01:21:47.679 --> 01:21:51.270 align:start position:0% you<01:21:48.679> cool<01:21:49.040> so<01:21:49.520> U<01:21:49.840> I<01:21:49.960> think<01:21:50.199> we<01:21:50.400> have<01:21:50.719> questions 01:21:51.270 --> 01:21:51.280 align:start position:0% you cool so U I think we have questions 01:21:51.280 --> 01:21:53.229 align:start position:0% you cool so U I think we have questions we<01:21:51.400> can<01:21:51.679> take<01:21:52.520> I<01:21:52.600> don't<01:21:52.719> know<01:21:52.840> if<01:21:52.960> people<01:21:53.120> in 01:21:53.229 --> 01:21:53.239 align:start position:0% we can take I don't know if people in 01:21:53.239 --> 01:21:55.550 align:start position:0% we can take I don't know if people in the<01:21:53.360> room<01:21:53.600> have<01:21:53.800> questions<01:21:54.360> or<01:21:54.600> or<01:21:54.760> if<01:21:55.320> they 01:21:55.550 --> 01:21:55.560 align:start position:0% the room have questions or or if they 01:21:55.560 --> 01:21:58.910 align:start position:0% the room have questions or or if they have<01:21:55.880> used<01:21:56.239> the<01:21:56.400> tool<01:21:56.760> to<01:21:57.120> put<01:21:57.280> it<01:21:57.400> up<01:21:57.760> here<01:21:58.760> but 01:21:58.910 --> 01:21:58.920 align:start position:0% have used the tool to put it up here but 01:21:58.920 --> 01:22:08.590 align:start position:0% have used the tool to put it up here but maybe<01:21:59.199> we'll<01:21:59.440> start<01:21:59.760> with 01:22:08.590 --> 01:22:08.600 align:start position:0% 01:22:08.600 --> 01:22:12.470 align:start position:0% this<01:22:09.600> hello<01:22:09.840> hello<01:22:10.080> hello<01:22:10.840> we<01:22:11.360> yeah<01:22:12.040> all<01:22:12.199> right 01:22:12.470 --> 01:22:12.480 align:start position:0% this hello hello hello we yeah all right 01:22:12.480 --> 01:22:14.990 align:start position:0% this hello hello hello we yeah all right the<01:22:12.600> first<01:22:12.840> one<01:22:13.719> um<01:22:14.440> what<01:22:14.560> do<01:22:14.679> you<01:22:14.800> think 01:22:14.990 --> 01:22:15.000 align:start position:0% the first one um what do you think 01:22:15.000 --> 01:22:17.189 align:start position:0% the first one um what do you think regarding<01:22:15.360> an<01:22:15.480> issue<01:22:15.719> in<01:22:15.800> erc20<01:22:16.480> standard 01:22:17.189 --> 01:22:17.199 align:start position:0% regarding an issue in erc20 standard 01:22:17.199 --> 01:22:19.550 align:start position:0% regarding an issue in erc20 standard discovered<01:22:17.440> in<01:22:17.600> 2017<01:22:18.280> which<01:22:18.560> caused<01:22:18.800> $15 01:22:19.550 --> 01:22:19.560 align:start position:0% discovered in 2017 which caused $15 01:22:19.560 --> 01:22:24.990 align:start position:0% discovered in 2017 which caused $15 million<01:22:20.280> loss<01:22:20.639> by<01:22:20.800> ethereum<01:22:21.239> users 01:22:24.990 --> 01:22:25.000 align:start position:0% 01:22:25.000 --> 01:22:28.229 align:start position:0% which<01:22:25.159> one<01:22:25.400> is<01:22:25.639> this 01:22:28.229 --> 01:22:28.239 align:start position:0% which one is this 01:22:28.239 --> 01:22:33.350 align:start position:0% which one is this I 01:22:33.350 --> 01:22:33.360 align:start position:0% 01:22:33.360 --> 01:22:40.870 align:start position:0% what<01:22:34.360> I<01:22:34.480> don't<01:22:34.719> recall<01:22:35.159> that<01:22:35.320> one<01:22:35.520> I<01:22:35.600> don't 01:22:40.870 --> 01:22:40.880 align:start position:0% 01:22:40.880 --> 01:22:43.669 align:start position:0% know<01:22:41.880> okay<01:22:42.199> excuse<01:22:42.679> I<01:22:42.760> don't<01:22:42.920> have<01:22:43.080> a<01:22:43.199> formed 01:22:43.669 --> 01:22:43.679 align:start position:0% know okay excuse I don't have a formed 01:22:43.679 --> 01:22:49.270 align:start position:0% know okay excuse I don't have a formed opinion<01:22:44.080> about<01:22:44.400> it<01:22:45.400> thank 01:22:49.270 --> 01:22:49.280 align:start position:0% 01:22:49.280 --> 01:22:51.709 align:start position:0% you<01:22:50.280> okay<01:22:50.520> while<01:22:50.880> while<01:22:51.159> that<01:22:51.320> link<01:22:51.560> is 01:22:51.709 --> 01:22:51.719 align:start position:0% you okay while while that link is 01:22:51.719 --> 01:22:53.270 align:start position:0% you okay while while that link is getting<01:22:51.960> posted<01:22:52.360> I<01:22:52.440> think<01:22:52.560> we<01:22:52.679> have<01:22:52.840> one<01:22:53.120> that 01:22:53.270 --> 01:22:53.280 align:start position:0% getting posted I think we have one that 01:22:53.280 --> 01:22:55.709 align:start position:0% getting posted I think we have one that went<01:22:53.520> up<01:22:54.120> how<01:22:54.239> do<01:22:54.520> you<01:22:54.639> say<01:22:54.920> your<01:22:55.239> process<01:22:55.560> is 01:22:55.709 --> 01:22:55.719 align:start position:0% went up how do you say your process is 01:22:55.719 --> 01:22:57.390 align:start position:0% went up how do you say your process is unique<01:22:56.159> what<01:22:56.280> do<01:22:56.480> each<01:22:56.679> of<01:22:56.800> you<01:22:57.239> do 01:22:57.390 --> 01:22:57.400 align:start position:0% unique what do each of you do 01:22:57.400 --> 01:22:58.870 align:start position:0% unique what do each of you do differently<01:22:57.800> from<01:22:58.000> everyone<01:22:58.320> else<01:22:58.639> oh<01:22:58.760> that's 01:22:58.870 --> 01:22:58.880 align:start position:0% differently from everyone else oh that's 01:22:58.880 --> 01:23:02.149 align:start position:0% differently from everyone else oh that's a<01:22:59.040> good 01:23:02.149 --> 01:23:02.159 align:start position:0% 01:23:02.159 --> 01:23:05.110 align:start position:0% one<01:23:03.159> um<01:23:03.600> I<01:23:03.719> would<01:23:03.920> lie<01:23:04.159> if<01:23:04.360> I'm<01:23:04.600> I<01:23:04.679> would<01:23:04.800> say<01:23:04.960> my 01:23:05.110 --> 01:23:05.120 align:start position:0% one um I would lie if I'm I would say my 01:23:05.120 --> 01:23:06.740 align:start position:0% one um I would lie if I'm I would say my process<01:23:05.440> is<01:23:05.600> unique 01:23:06.740 --> 01:23:06.750 align:start position:0% process is unique 01:23:06.750 --> 01:23:08.350 align:start position:0% process is unique [Music] 01:23:08.350 --> 01:23:08.360 align:start position:0% [Music] 01:23:08.360 --> 01:23:11.430 align:start position:0% [Music] um<01:23:09.360> I<01:23:09.440> don't<01:23:09.679> think<01:23:09.960> it's<01:23:10.840> honestly<01:23:11.159> I<01:23:11.280> don't 01:23:11.430 --> 01:23:11.440 align:start position:0% um I don't think it's honestly I don't 01:23:11.440 --> 01:23:13.550 align:start position:0% um I don't think it's honestly I don't think<01:23:11.560> it's<01:23:11.719> Unique<01:23:12.199> I<01:23:12.280> think<01:23:12.960> uh<01:23:13.280> well<01:23:13.440> I 01:23:13.550 --> 01:23:13.560 align:start position:0% think it's Unique I think uh well I 01:23:13.560 --> 01:23:15.229 align:start position:0% think it's Unique I think uh well I don't<01:23:13.800> I<01:23:13.920> haven't<01:23:14.239> worked<01:23:14.560> with<01:23:14.679> these<01:23:14.880> guys 01:23:15.229 --> 01:23:15.239 align:start position:0% don't I haven't worked with these guys 01:23:15.239 --> 01:23:20.229 align:start position:0% don't I haven't worked with these guys side<01:23:15.480> to<01:23:15.719> side<01:23:16.400> but<01:23:17.760> um<01:23:18.760> I<01:23:18.840> do<01:23:19.320> to<01:23:19.440> some<01:23:19.600> extent 01:23:20.229 --> 01:23:20.239 align:start position:0% side to side but um I do to some extent 01:23:20.239 --> 01:23:23.149 align:start position:0% side to side but um I do to some extent our<01:23:20.480> process<01:23:20.920> might<01:23:21.120> look<01:23:21.880> similar<01:23:22.880> sometimes 01:23:23.149 --> 01:23:23.159 align:start position:0% our process might look similar sometimes 01:23:23.159 --> 01:23:25.390 align:start position:0% our process might look similar sometimes I<01:23:23.320> think<01:23:23.800> we<01:23:23.920> might<01:23:24.080> defeat<01:23:24.520> initiating<01:23:25.199> to 01:23:25.390 --> 01:23:25.400 align:start position:0% I think we might defeat initiating to 01:23:25.400 --> 01:23:27.470 align:start position:0% I think we might defeat initiating to what<01:23:25.560> extent<01:23:25.800> we<01:23:25.960> use<01:23:26.239> tooling<01:23:26.800> for<01:23:26.960> example 01:23:27.470 --> 01:23:27.480 align:start position:0% what extent we use tooling for example 01:23:27.480 --> 01:23:29.790 align:start position:0% what extent we use tooling for example that's<01:23:27.800> one<01:23:28.040> case<01:23:28.239> in<01:23:28.400> my<01:23:28.600> case<01:23:29.239> I<01:23:29.360> don't<01:23:29.600> use 01:23:29.790 --> 01:23:29.800 align:start position:0% that's one case in my case I don't use 01:23:29.800 --> 01:23:32.669 align:start position:0% that's one case in my case I don't use tooling<01:23:30.280> very<01:23:30.440> much<01:23:30.840> I'm<01:23:31.280> very<01:23:31.440> much<01:23:31.600> a<01:23:31.719> manual 01:23:32.669 --> 01:23:32.679 align:start position:0% tooling very much I'm very much a manual 01:23:32.679 --> 01:23:36.189 align:start position:0% tooling very much I'm very much a manual reviewer<01:23:33.679> uh<01:23:34.120> but<01:23:34.320> perhaps<01:23:34.880> not<01:23:35.440> Rajiv<01:23:35.920> or<01:23:36.040> or 01:23:36.189 --> 01:23:36.199 align:start position:0% reviewer uh but perhaps not Rajiv or or 01:23:36.199 --> 01:23:39.229 align:start position:0% reviewer uh but perhaps not Rajiv or or Jonah<01:23:36.760> might<01:23:36.920> use<01:23:37.120> some<01:23:37.320> more<01:23:37.480> tooling 01:23:39.229 --> 01:23:39.239 align:start position:0% Jonah might use some more tooling 01:23:39.239 --> 01:23:44.070 align:start position:0% Jonah might use some more tooling sometimes<01:23:40.239> okay<01:23:40.480> go<01:23:40.679> first<01:23:41.360> okay<01:23:41.800> so<01:23:42.760> um<01:23:43.760> I<01:23:43.840> was 01:23:44.070 --> 01:23:44.080 align:start position:0% sometimes okay go first okay so um I was 01:23:44.080 --> 01:23:46.629 align:start position:0% sometimes okay go first okay so um I was very<01:23:44.320> interested<01:23:44.920> in<01:23:45.040> the<01:23:45.280> to<01:23:45.639> in<01:23:45.800> this<01:23:46.080> topic 01:23:46.629 --> 01:23:46.639 align:start position:0% very interested in the to in this topic 01:23:46.639 --> 01:23:48.750 align:start position:0% very interested in the to in this topic last<01:23:46.960> year<01:23:47.239> or<01:23:47.480> sometime<01:23:47.960> last<01:23:48.199> year<01:23:48.520> like 01:23:48.750 --> 01:23:48.760 align:start position:0% last year or sometime last year like 01:23:48.760 --> 01:23:50.750 align:start position:0% last year or sometime last year like different<01:23:49.120> methods<01:23:49.520> of<01:23:49.840> approaching 01:23:50.750 --> 01:23:50.760 align:start position:0% different methods of approaching 01:23:50.760 --> 01:23:55.149 align:start position:0% different methods of approaching bounties<01:23:52.000> Audits<01:23:53.199> and<01:23:54.199> there<01:23:54.440> there's<01:23:54.920> a<01:23:55.040> lot 01:23:55.149 --> 01:23:55.159 align:start position:0% bounties Audits and there there's a lot 01:23:55.159 --> 01:23:57.830 align:start position:0% bounties Audits and there there's a lot of<01:23:55.560> different<01:23:55.920> ways<01:23:56.120> of<01:23:56.320> going<01:23:56.719> about<01:23:57.440> Audits 01:23:57.830 --> 01:23:57.840 align:start position:0% of different ways of going about Audits 01:23:57.840 --> 01:24:00.110 align:start position:0% of different ways of going about Audits and<01:23:58.120> security<01:23:58.639> research<01:23:59.199> but<01:23:59.520> in<01:23:59.639> the<01:23:59.800> end 01:24:00.110 --> 01:24:00.120 align:start position:0% and security research but in the end 01:24:00.120 --> 01:24:02.709 align:start position:0% and security research but in the end they're<01:24:00.360> all<01:24:00.639> not<01:24:01.080> that<01:24:01.440> dissimilar<01:24:02.360> I<01:24:02.480> think 01:24:02.709 --> 01:24:02.719 align:start position:0% they're all not that dissimilar I think 01:24:02.719 --> 01:24:06.350 align:start position:0% they're all not that dissimilar I think for<01:24:02.960> J's<01:24:03.440> last<01:24:03.679> slide<01:24:04.000> is<01:24:04.600> just<01:24:04.840> read<01:24:05.159> the<01:24:05.360> Cod 01:24:06.350 --> 01:24:06.360 align:start position:0% for J's last slide is just read the Cod 01:24:06.360 --> 01:24:08.990 align:start position:0% for J's last slide is just read the Cod um<01:24:06.719> in<01:24:06.840> the<01:24:07.000> end<01:24:07.480> that's<01:24:07.960> kind<01:24:08.120> of<01:24:08.800> what 01:24:08.990 --> 01:24:09.000 align:start position:0% um in the end that's kind of what 01:24:09.000 --> 01:24:12.550 align:start position:0% um in the end that's kind of what everybody<01:24:09.440> ends<01:24:09.679> up<01:24:09.880> doing<01:24:10.840> um<01:24:11.800> Everybody 01:24:12.550 --> 01:24:12.560 align:start position:0% everybody ends up doing um Everybody 01:24:12.560 --> 01:24:14.629 align:start position:0% everybody ends up doing um Everybody builds<01:24:12.880> this<01:24:13.360> like<01:24:13.719> General<01:24:14.280> mental 01:24:14.629 --> 01:24:14.639 align:start position:0% builds this like General mental 01:24:14.639 --> 01:24:16.149 align:start position:0% builds this like General mental framework<01:24:15.360> that 01:24:16.149 --> 01:24:16.159 align:start position:0% framework that 01:24:16.159 --> 01:24:19.189 align:start position:0% framework that they<01:24:17.159> add<01:24:17.480> information<01:24:18.040> into<01:24:18.600> as<01:24:18.719> they<01:24:18.880> read 01:24:19.189 --> 01:24:19.199 align:start position:0% they add information into as they read 01:24:19.199 --> 01:24:22.470 align:start position:0% they add information into as they read codes<01:24:20.159> um<01:24:20.560> writing<01:24:21.159> specifications<01:24:22.080> running 01:24:22.470 --> 01:24:22.480 align:start position:0% codes um writing specifications running 01:24:22.480 --> 01:24:25.149 align:start position:0% codes um writing specifications running tools<01:24:22.960> they<01:24:23.080> are<01:24:23.199> all<01:24:23.480> just<01:24:23.800> methods<01:24:24.600> thinking 01:24:25.149 --> 01:24:25.159 align:start position:0% tools they are all just methods thinking 01:24:25.159 --> 01:24:28.270 align:start position:0% tools they are all just methods thinking writing<01:24:26.159> another<01:24:26.600> matter<01:24:27.159> of<01:24:27.400> thinking<01:24:28.000> about 01:24:28.270 --> 01:24:28.280 align:start position:0% writing another matter of thinking about 01:24:28.280 --> 01:24:30.709 align:start position:0% writing another matter of thinking about the<01:24:28.440> code<01:24:28.800> but<01:24:28.960> in<01:24:29.120> the<01:24:29.239> end<01:24:29.560> you're<01:24:29.840> all<01:24:30.120> just 01:24:30.709 --> 01:24:30.719 align:start position:0% the code but in the end you're all just 01:24:30.719 --> 01:24:34.350 align:start position:0% the code but in the end you're all just like<01:24:31.360> mentally<01:24:32.239> processing<01:24:33.239> uh<01:24:33.560> and<01:24:34.040> yeah<01:24:34.199> so 01:24:34.350 --> 01:24:34.360 align:start position:0% like mentally processing uh and yeah so 01:24:34.360 --> 01:24:37.510 align:start position:0% like mentally processing uh and yeah so I<01:24:34.480> don't<01:24:34.760> think<01:24:35.560> it's<01:24:35.800> going<01:24:35.920> to<01:24:36.000> be<01:24:36.159> super 01:24:37.510 --> 01:24:37.520 align:start position:0% I don't think it's going to be super 01:24:37.520 --> 01:24:39.790 align:start position:0% I don't think it's going to be super dissimilar<01:24:38.520> yeah<01:24:38.840> I<01:24:38.920> would<01:24:39.159> Echo<01:24:39.480> that<01:24:39.679> I 01:24:39.790 --> 01:24:39.800 align:start position:0% dissimilar yeah I would Echo that I 01:24:39.800 --> 01:24:43.229 align:start position:0% dissimilar yeah I would Echo that I don't<01:24:40.000> think<01:24:40.239> it's<01:24:40.840> that<01:24:41.199> different<01:24:42.040> um<01:24:42.840> I 01:24:43.229 --> 01:24:43.239 align:start position:0% don't think it's that different um I 01:24:43.239 --> 01:24:45.709 align:start position:0% don't think it's that different um I used<01:24:43.520> to<01:24:43.679> do<01:24:43.960> a<01:24:44.080> lot<01:24:44.239> of<01:24:44.440> my<01:24:44.679> reviews<01:24:45.360> with 01:24:45.709 --> 01:24:45.719 align:start position:0% used to do a lot of my reviews with 01:24:45.719 --> 01:24:49.350 align:start position:0% used to do a lot of my reviews with invariant<01:24:46.320> testing<01:24:46.920> and<01:24:47.639> fuzzing<01:24:48.639> um<01:24:49.040> but<01:24:49.239> I 01:24:49.350 --> 01:24:49.360 align:start position:0% invariant testing and fuzzing um but I 01:24:49.360 --> 01:24:52.790 align:start position:0% invariant testing and fuzzing um but I don't<01:24:49.719> think<01:24:50.080> that's<01:24:51.080> atypical<01:24:52.080> um<01:24:52.400> I<01:24:52.480> think 01:24:52.790 --> 01:24:52.800 align:start position:0% don't think that's atypical um I think 01:24:52.800 --> 01:24:54.830 align:start position:0% don't think that's atypical um I think if<01:24:52.920> you<01:24:53.119> put<01:24:53.320> the<01:24:53.520> time<01:24:53.760> into<01:24:54.040> really 01:24:54.830 --> 01:24:54.840 align:start position:0% if you put the time into really 01:24:54.840 --> 01:24:58.830 align:start position:0% if you put the time into really learning<01:24:55.400> how<01:24:55.600> to<01:24:55.880> use<01:24:56.520> the<01:24:56.920> tools<01:24:57.920> um<01:24:58.280> I<01:24:58.400> think 01:24:58.830 --> 01:24:58.840 align:start position:0% learning how to use the tools um I think 01:24:58.840 --> 01:25:01.310 align:start position:0% learning how to use the tools um I think anyone<01:24:59.239> can<01:24:59.440> really<01:24:59.679> spin<01:25:00.040> up<01:25:00.480> like<01:25:00.760> a<01:25:00.920> fuzz 01:25:01.310 --> 01:25:01.320 align:start position:0% anyone can really spin up like a fuzz 01:25:01.320 --> 01:25:04.910 align:start position:0% anyone can really spin up like a fuzz test<01:25:02.239> um<01:25:02.480> it's<01:25:02.920> really<01:25:03.159> just<01:25:03.320> a<01:25:03.520> matter<01:25:03.920> of 01:25:04.910 --> 01:25:04.920 align:start position:0% test um it's really just a matter of 01:25:04.920 --> 01:25:07.109 align:start position:0% test um it's really just a matter of kind<01:25:05.040> of<01:25:05.199> how<01:25:05.480> complex<01:25:06.440> um<01:25:06.560> you<01:25:06.639> want<01:25:06.760> to<01:25:06.920> get 01:25:07.109 --> 01:25:07.119 align:start position:0% kind of how complex um you want to get 01:25:07.119 --> 01:25:13.669 align:start position:0% kind of how complex um you want to get with 01:25:13.669 --> 01:25:13.679 align:start position:0% 01:25:13.679 --> 01:25:17.030 align:start position:0% that<01:25:14.679> there's<01:25:15.239> too<01:25:15.480> many 01:25:17.030 --> 01:25:17.040 align:start position:0% that there's too many 01:25:17.040 --> 01:25:21.390 align:start position:0% that there's too many tools<01:25:18.040> should<01:25:18.360> we<01:25:18.480> pick<01:25:18.760> that<01:25:18.880> one<01:25:19.639> um<01:25:20.199> I<01:25:20.400> think 01:25:21.390 --> 01:25:21.400 align:start position:0% tools should we pick that one um I think 01:25:21.400 --> 01:25:24.950 align:start position:0% tools should we pick that one um I think uh<01:25:21.679> n<01:25:22.119> had<01:25:22.239> a<01:25:22.400> slide<01:25:22.719> on<01:25:23.000> this<01:25:23.840> um<01:25:24.600> doesn't 01:25:24.950 --> 01:25:24.960 align:start position:0% uh n had a slide on this um doesn't 01:25:24.960 --> 01:25:26.830 align:start position:0% uh n had a slide on this um doesn't matter<01:25:25.280> which<01:25:25.440> tool<01:25:25.760> you<01:25:25.920> use<01:25:26.280> just<01:25:26.480> use<01:25:26.679> the 01:25:26.830 --> 01:25:26.840 align:start position:0% matter which tool you use just use the 01:25:26.840 --> 01:25:30.629 align:start position:0% matter which tool you use just use the ones<01:25:27.080> that<01:25:27.280> work<01:25:27.480> for<01:25:27.679> you<01:25:28.639> um<01:25:29.280> I<01:25:29.400> feel<01:25:29.840> like 01:25:30.629 --> 01:25:30.639 align:start position:0% ones that work for you um I feel like 01:25:30.639 --> 01:25:32.910 align:start position:0% ones that work for you um I feel like that's<01:25:30.920> very<01:25:31.159> true<01:25:31.719> there's<01:25:31.920> a<01:25:32.040> couple<01:25:32.360> V<01:25:32.639> code 01:25:32.910 --> 01:25:32.920 align:start position:0% that's very true there's a couple V code 01:25:32.920 --> 01:25:35.030 align:start position:0% that's very true there's a couple V code extensions<01:25:33.560> that<01:25:33.679> are<01:25:33.880> super<01:25:34.199> nice<01:25:34.880> I 01:25:35.030 --> 01:25:35.040 align:start position:0% extensions that are super nice I 01:25:35.040 --> 01:25:37.910 align:start position:0% extensions that are super nice I personally<01:25:35.440> don't<01:25:35.719> end<01:25:36.040> up<01:25:36.320> relying<01:25:36.760> a<01:25:36.960> lot<01:25:37.360> on 01:25:37.910 --> 01:25:37.920 align:start position:0% personally don't end up relying a lot on 01:25:37.920 --> 01:25:41.310 align:start position:0% personally don't end up relying a lot on this<01:25:38.119> kind<01:25:38.239> of<01:25:38.400> tool<01:25:38.960> I<01:25:39.119> use<01:25:39.800> V<01:25:40.119> code<01:25:40.360> bookmarks 01:25:41.310 --> 01:25:41.320 align:start position:0% this kind of tool I use V code bookmarks 01:25:41.320 --> 01:25:44.310 align:start position:0% this kind of tool I use V code bookmarks super<01:25:41.880> useful<01:25:42.880> uh<01:25:43.119> but<01:25:43.400> that's<01:25:43.679> not<01:25:43.960> really 01:25:44.310 --> 01:25:44.320 align:start position:0% super useful uh but that's not really 01:25:44.320 --> 01:25:46.390 align:start position:0% super useful uh but that's not really security<01:25:44.800> researchable<01:25:45.800> obviously<01:25:46.239> you're 01:25:46.390 --> 01:25:46.400 align:start position:0% security researchable obviously you're 01:25:46.400 --> 01:25:48.350 align:start position:0% security researchable obviously you're going<01:25:46.520> to<01:25:46.679> use<01:25:46.840> some<01:25:47.040> syntax<01:25:47.520> highlighting<01:25:48.119> go 01:25:48.350 --> 01:25:48.360 align:start position:0% going to use some syntax highlighting go 01:25:48.360 --> 01:25:51.310 align:start position:0% going to use some syntax highlighting go to<01:25:48.560> definition<01:25:49.040> type<01:25:49.400> tooling<01:25:50.400> um<01:25:50.800> but<01:25:50.960> beyond 01:25:51.310 --> 01:25:51.320 align:start position:0% to definition type tooling um but beyond 01:25:51.320 --> 01:25:53.470 align:start position:0% to definition type tooling um but beyond that<01:25:51.480> is<01:25:51.719> really<01:25:52.080> like<01:25:52.400> what<01:25:52.760> works<01:25:53.080> well<01:25:53.280> for 01:25:53.470 --> 01:25:53.480 align:start position:0% that is really like what works well for 01:25:53.480 --> 01:25:56.149 align:start position:0% that is really like what works well for you<01:25:54.119> um<01:25:54.400> um<01:25:54.600> and<01:25:54.760> I<01:25:54.960> recommend<01:25:55.400> you<01:25:55.600> try<01:25:55.840> out 01:25:56.149 --> 01:25:56.159 align:start position:0% you um um and I recommend you try out 01:25:56.159 --> 01:25:58.750 align:start position:0% you um um and I recommend you try out like<01:25:56.280> all<01:25:56.440> the<01:25:56.600> different<01:25:57.239> things<01:25:58.239> um<01:25:58.639> in 01:25:58.750 --> 01:25:58.760 align:start position:0% like all the different things um in 01:25:58.760 --> 01:26:04.189 align:start position:0% like all the different things um in terms<01:25:59.040> of<01:25:59.840> researchers<01:26:00.440> to<01:26:00.679> recommend<01:26:01.639> these 01:26:04.189 --> 01:26:04.199 align:start position:0% 01:26:04.199 --> 01:26:07.709 align:start position:0% guys<01:26:05.199> there<01:26:05.320> are<01:26:05.400> a<01:26:05.520> whole<01:26:05.679> bunch<01:26:06.040> I<01:26:06.119> mean<01:26:06.719> um 01:26:07.709 --> 01:26:07.719 align:start position:0% guys there are a whole bunch I mean um 01:26:07.719 --> 01:26:11.629 align:start position:0% guys there are a whole bunch I mean um just<01:26:08.000> just<01:26:08.159> go<01:26:08.320> on<01:26:08.639> Twitter<01:26:09.639> um<01:26:09.960> look 01:26:11.629 --> 01:26:11.639 align:start position:0% just just go on Twitter um look 01:26:11.639 --> 01:26:14.109 align:start position:0% just just go on Twitter um look up<01:26:12.639> and<01:26:13.280> let<01:26:13.440> let<01:26:13.560> me<01:26:13.679> look<01:26:13.800> at<01:26:13.920> the 01:26:14.109 --> 01:26:14.119 align:start position:0% up and let let me look at the 01:26:14.119 --> 01:26:16.310 align:start position:0% up and let let me look at the publication<01:26:14.840> right 01:26:16.310 --> 01:26:16.320 align:start position:0% publication right 01:26:16.320 --> 01:26:18.669 align:start position:0% publication right um<01:26:17.320> which<01:26:17.639> publication<01:26:18.280> so<01:26:18.400> I<01:26:18.480> would 01:26:18.669 --> 01:26:18.679 align:start position:0% um which publication so I would 01:26:18.679 --> 01:26:22.310 align:start position:0% um which publication so I would definitely<01:26:19.440> uh<01:26:19.560> do<01:26:19.719> a<01:26:19.880> shout<01:26:20.159> out<01:26:20.480> to<01:26:21.360> uh<01:26:21.920> block 01:26:22.310 --> 01:26:22.320 align:start position:0% definitely uh do a shout out to uh block 01:26:22.320 --> 01:26:25.709 align:start position:0% definitely uh do a shout out to uh block Threat<01:26:23.119> by<01:26:23.440> Peter<01:26:23.920> from<01:26:24.480> from<01:26:24.760> coinbase<01:26:25.400> so<01:26:25.600> as 01:26:25.709 --> 01:26:25.719 align:start position:0% Threat by Peter from from coinbase so as 01:26:25.719 --> 01:26:28.070 align:start position:0% Threat by Peter from from coinbase so as a<01:26:25.880> publication<01:26:26.400> so<01:26:26.560> it's<01:26:26.760> a<01:26:27.280> I<01:26:27.400> think<01:26:27.520> a<01:26:27.639> weekly 01:26:28.070 --> 01:26:28.080 align:start position:0% a publication so it's a I think a weekly 01:26:28.080 --> 01:26:29.790 align:start position:0% a publication so it's a I think a weekly thing<01:26:28.679> where<01:26:28.920> all<01:26:29.080> the<01:26:29.239> threats<01:26:29.520> in<01:26:29.679> this 01:26:29.790 --> 01:26:29.800 align:start position:0% thing where all the threats in this 01:26:29.800 --> 01:26:33.030 align:start position:0% thing where all the threats in this ecosystem<01:26:30.320> are<01:26:30.520> very<01:26:30.719> neatly<01:26:31.320> compiled<01:26:32.320> so<01:26:32.840> do 01:26:33.030 --> 01:26:33.040 align:start position:0% ecosystem are very neatly compiled so do 01:26:33.040 --> 01:26:35.350 align:start position:0% ecosystem are very neatly compiled so do take<01:26:33.199> a<01:26:33.480> look<01:26:33.639> at<01:26:33.800> that<01:26:33.960> if<01:26:34.040> you're<01:26:34.360> interested 01:26:35.350 --> 01:26:35.360 align:start position:0% take a look at that if you're interested 01:26:35.360 --> 01:26:37.629 align:start position:0% take a look at that if you're interested and<01:26:36.000> um<01:26:36.280> if<01:26:36.400> you're<01:26:36.639> specifically<01:26:37.199> interested 01:26:37.629 --> 01:26:37.639 align:start position:0% and um if you're specifically interested 01:26:37.639 --> 01:26:41.030 align:start position:0% and um if you're specifically interested in<01:26:37.880> smart<01:26:38.239> contract<01:26:38.639> bugs<01:26:39.239> then<01:26:39.920> the<01:26:40.080> various 01:26:41.030 --> 01:26:41.040 align:start position:0% in smart contract bugs then the various 01:26:41.040 --> 01:26:45.910 align:start position:0% in smart contract bugs then the various um<01:26:42.040> reports<01:26:43.040> from<01:26:43.440> from<01:26:43.679> contest<01:26:44.679> from<01:26:45.679> U 01:26:45.910 --> 01:26:45.920 align:start position:0% um reports from from contest from U 01:26:45.920 --> 01:26:47.709 align:start position:0% um reports from from contest from U different<01:26:46.280> project<01:26:46.639> I<01:26:46.760> mean<01:26:47.159> different<01:26:47.400> firms 01:26:47.709 --> 01:26:47.719 align:start position:0% different project I mean different firms 01:26:47.719 --> 01:26:49.910 align:start position:0% different project I mean different firms like<01:26:47.880> diligence<01:26:48.560> they<01:26:48.719> all<01:26:48.920> have<01:26:49.239> you 01:26:49.910 --> 01:26:49.920 align:start position:0% like diligence they all have you 01:26:49.920 --> 01:26:51.910 align:start position:0% like diligence they all have you whatever<01:26:50.280> publicly<01:26:50.679> available<01:26:51.360> reports<01:26:51.760> on 01:26:51.910 --> 01:26:51.920 align:start position:0% whatever publicly available reports on 01:26:51.920 --> 01:26:54.149 align:start position:0% whatever publicly available reports on their 01:26:54.149 --> 01:26:54.159 align:start position:0% 01:26:54.159 --> 01:26:56.910 align:start position:0% soloed<01:26:54.800> that<01:26:55.080> com<01:26:55.360> that<01:26:55.600> compiles<01:26:56.080> it<01:26:56.600> so 01:26:56.910 --> 01:26:56.920 align:start position:0% soloed that com that compiles it so 01:26:56.920 --> 01:26:58.669 align:start position:0% soloed that com that compiles it so those<01:26:57.080> would<01:26:57.320> be<01:26:57.679> uh<01:26:57.800> definitely<01:26:58.199> some<01:26:58.560> there 01:26:58.669 --> 01:26:58.679 align:start position:0% those would be uh definitely some there 01:26:58.679 --> 01:27:01.189 align:start position:0% those would be uh definitely some there is<01:26:58.800> a<01:26:59.360> whole<01:26:59.719> I<01:26:59.800> mean<01:27:00.119> all<01:27:00.360> these<01:27:00.679> security 01:27:01.189 --> 01:27:01.199 align:start position:0% is a whole I mean all these security 01:27:01.199 --> 01:27:03.990 align:start position:0% is a whole I mean all these security videos<01:27:01.800> right<01:27:02.480> um<01:27:02.880> recorded<01:27:03.320> talks<01:27:03.679> so<01:27:03.840> there 01:27:03.990 --> 01:27:04.000 align:start position:0% videos right um recorded talks so there 01:27:04.000 --> 01:27:07.229 align:start position:0% videos right um recorded talks so there was<01:27:04.159> a<01:27:05.000> uh<01:27:05.440> defi<01:27:05.960> security<01:27:06.320> Summit<01:27:06.679> DSS 01:27:07.229 --> 01:27:07.239 align:start position:0% was a uh defi security Summit DSS 01:27:07.239 --> 01:27:10.629 align:start position:0% was a uh defi security Summit DSS conference<01:27:07.760> last<01:27:08.000> week<01:27:09.000> and<01:27:09.880> I<01:27:10.000> think<01:27:10.239> we<01:27:10.400> had 01:27:10.629 --> 01:27:10.639 align:start position:0% conference last week and I think we had 01:27:10.639 --> 01:27:14.229 align:start position:0% conference last week and I think we had pretty<01:27:10.840> much<01:27:11.400> every<01:27:12.360> uh<01:27:12.520> well<01:27:13.520> most<01:27:13.719> of<01:27:13.880> the 01:27:14.229 --> 01:27:14.239 align:start position:0% pretty much every uh well most of the 01:27:14.239 --> 01:27:16.470 align:start position:0% pretty much every uh well most of the leading<01:27:14.600> researchers<01:27:15.119> in<01:27:15.239> the<01:27:15.480> space<01:27:15.960> web<01:27:16.199> 3 01:27:16.470 --> 01:27:16.480 align:start position:0% leading researchers in the space web 3 01:27:16.480 --> 01:27:19.470 align:start position:0% leading researchers in the space web 3 web<01:27:16.719> 2<01:27:16.960> anything<01:27:17.239> in<01:27:17.440> between<01:27:18.440> every<01:27:18.840> aspect 01:27:19.470 --> 01:27:19.480 align:start position:0% web 2 anything in between every aspect 01:27:19.480 --> 01:27:21.750 align:start position:0% web 2 anything in between every aspect right<01:27:19.840> were<01:27:20.239> there<01:27:20.760> all<01:27:21.000> their<01:27:21.280> thoughts<01:27:21.600> have 01:27:21.750 --> 01:27:21.760 align:start position:0% right were there all their thoughts have 01:27:21.760 --> 01:27:24.390 align:start position:0% right were there all their thoughts have been<01:27:22.000> captured<01:27:22.920> so<01:27:23.239> just<01:27:23.480> go<01:27:23.679> to<01:27:23.880> those 01:27:24.390 --> 01:27:24.400 align:start position:0% been captured so just go to those 01:27:24.400 --> 01:27:25.790 align:start position:0% been captured so just go to those YouTube<01:27:24.800> channels<01:27:25.199> or<01:27:25.320> wherever<01:27:25.600> they're 01:27:25.790 --> 01:27:25.800 align:start position:0% YouTube channels or wherever they're 01:27:25.800 --> 01:27:28.390 align:start position:0% YouTube channels or wherever they're hosted<01:27:26.320> take<01:27:26.480> a<01:27:26.639> look<01:27:26.760> at<01:27:26.880> it<01:27:27.600> uh<01:27:27.719> so<01:27:28.080> that<01:27:28.239> is 01:27:28.390 --> 01:27:28.400 align:start position:0% hosted take a look at it uh so that is 01:27:28.400 --> 01:27:30.669 align:start position:0% hosted take a look at it uh so that is something<01:27:28.719> I<01:27:28.800> would<01:27:29.280> definitely 01:27:30.669 --> 01:27:30.679 align:start position:0% something I would definitely 01:27:30.679 --> 01:27:33.510 align:start position:0% something I would definitely recommend<01:27:31.679> I<01:27:31.840> found<01:27:32.159> the<01:27:32.239> link<01:27:32.600> by<01:27:32.719> the<01:27:32.840> way 01:27:33.510 --> 01:27:33.520 align:start position:0% recommend I found the link by the way 01:27:33.520 --> 01:27:35.550 align:start position:0% recommend I found the link by the way you<01:27:33.679> can<01:27:33.880> find<01:27:34.080> it<01:27:34.239> in<01:27:34.480> this<01:27:34.840> thread<01:27:35.320> if<01:27:35.400> you 01:27:35.550 --> 01:27:35.560 align:start position:0% you can find it in this thread if you 01:27:35.560 --> 01:27:37.990 align:start position:0% you can find it in this thread if you scroll<01:27:35.920> down<01:27:36.239> the<01:27:36.560> comments<01:27:37.560> okay<01:27:37.800> I<01:27:37.920> don't 01:27:37.990 --> 01:27:38.000 align:start position:0% scroll down the comments okay I don't 01:27:38.000 --> 01:27:43.350 align:start position:0% scroll down the comments okay I don't know<01:27:38.159> how<01:27:38.280> to<01:27:38.400> scroll<01:27:38.800> down<01:27:39.520> um<01:27:40.320> not<01:27:40.520> in 01:27:43.350 --> 01:27:43.360 align:start position:0% 01:27:43.360 --> 01:27:45.830 align:start position:0% this<01:27:44.360> yeah<01:27:44.520> maybe<01:27:45.080> yeah<01:27:45.239> we'll<01:27:45.440> we'll<01:27:45.639> hang 01:27:45.830 --> 01:27:45.840 align:start position:0% this yeah maybe yeah we'll we'll hang 01:27:45.840 --> 01:27:47.470 align:start position:0% this yeah maybe yeah we'll we'll hang around<01:27:46.080> so<01:27:46.239> you<01:27:46.360> can<01:27:46.520> show<01:27:46.719> it<01:27:46.800> to<01:27:46.920> us<01:27:47.080> offline 01:27:47.470 --> 01:27:47.480 align:start position:0% around so you can show it to us offline 01:27:47.480 --> 01:27:50.350 align:start position:0% around so you can show it to us offline as<01:27:47.600> well<01:27:48.600> can<01:27:49.199> yeah<01:27:49.320> sorry<01:27:49.800> I<01:27:49.880> wanted<01:27:50.080> to<01:27:50.199> add 01:27:50.350 --> 01:27:50.360 align:start position:0% as well can yeah sorry I wanted to add 01:27:50.360 --> 01:27:52.910 align:start position:0% as well can yeah sorry I wanted to add something<01:27:50.560> about<01:27:50.760> tooling<01:27:51.760> um<01:27:52.360> I<01:27:52.560> personally 01:27:52.910 --> 01:27:52.920 align:start position:0% something about tooling um I personally 01:27:52.920 --> 01:27:55.109 align:start position:0% something about tooling um I personally use<01:27:53.159> Foundry<01:27:53.600> a<01:27:53.679> lot<01:27:54.360> does<01:27:54.520> it<01:27:54.679> count<01:27:54.880> as<01:27:55.000> a 01:27:55.109 --> 01:27:55.119 align:start position:0% use Foundry a lot does it count as a 01:27:55.119 --> 01:27:57.669 align:start position:0% use Foundry a lot does it count as a tool<01:27:55.360> I<01:27:55.440> don't<01:27:55.600> know<01:27:55.920> but<01:27:56.280> uh<01:27:56.840> I<01:27:57.000> write<01:27:57.280> tests 01:27:57.669 --> 01:27:57.679 align:start position:0% tool I don't know but uh I write tests 01:27:57.679 --> 01:28:00.109 align:start position:0% tool I don't know but uh I write tests and<01:27:57.800> I<01:27:57.920> do<01:27:58.159> fasing<01:27:58.679> with<01:27:58.880> Foundry<01:27:59.719> uh<01:27:59.960> that's 01:28:00.109 --> 01:28:00.119 align:start position:0% and I do fasing with Foundry uh that's 01:28:00.119 --> 01:28:02.350 align:start position:0% and I do fasing with Foundry uh that's mostly<01:28:00.480> what<01:28:00.600> I<01:28:00.719> do<01:28:00.960> and<01:28:01.199> yeah<01:28:01.480> visual<01:28:01.880> code 01:28:02.350 --> 01:28:02.360 align:start position:0% mostly what I do and yeah visual code 01:28:02.360 --> 01:28:05.709 align:start position:0% mostly what I do and yeah visual code visual<01:28:02.760> studio<01:28:03.199> ctions<01:28:04.000> and<01:28:04.119> that<01:28:04.280> kind<01:28:04.400> of 01:28:05.709 --> 01:28:05.719 align:start position:0% visual studio ctions and that kind of 01:28:05.719 --> 01:28:08.310 align:start position:0% visual studio ctions and that kind of things<01:28:06.719> cool<01:28:07.280> can<01:28:07.480> can<01:28:07.600> we<01:28:07.760> go<01:28:07.920> back<01:28:08.040> to<01:28:08.159> the 01:28:08.310 --> 01:28:08.320 align:start position:0% things cool can can we go back to the 01:28:08.320 --> 01:28:10.229 align:start position:0% things cool can can we go back to the slide<01:28:08.679> I<01:28:08.920> I<01:28:09.000> think<01:28:09.119> there<01:28:09.239> was<01:28:09.440> just<01:28:09.639> one<01:28:09.840> slide 01:28:10.229 --> 01:28:10.239 align:start position:0% slide I I think there was just one slide 01:28:10.239 --> 01:28:16.070 align:start position:0% slide I I think there was just one slide we<01:28:10.360> needed<01:28:10.639> to<01:28:10.760> show<01:28:11.040> for<01:28:11.360> the 01:28:16.070 --> 01:28:16.080 align:start position:0% 01:28:16.080 --> 01:28:20.189 align:start position:0% quiz<01:28:17.080> so<01:28:17.760> while<01:28:18.000> it<01:28:18.199> comes<01:28:18.400> up<01:28:18.600> so<01:28:18.840> this<01:28:18.960> is<01:28:19.480> a<01:28:19.880> a 01:28:20.189 --> 01:28:20.199 align:start position:0% quiz so while it comes up so this is a a 01:28:20.199 --> 01:28:26.990 align:start position:0% quiz so while it comes up so this is a a short<01:28:20.600> quiz<01:28:21.119> it's<01:28:21.560> really<01:28:21.880> 15<01:28:22.320> minutes 01:28:26.990 --> 01:28:27.000 align:start position:0% 01:28:27.000 --> 01:28:30.030 align:start position:0% and<01:28:27.360> you<01:28:27.520> don't<01:28:27.719> have<01:28:27.840> to<01:28:27.960> finish<01:28:28.199> it<01:28:28.440> now<01:28:29.280> just 01:28:30.030 --> 01:28:30.040 align:start position:0% and you don't have to finish it now just 01:28:30.040 --> 01:28:32.669 align:start position:0% and you don't have to finish it now just look<01:28:30.159> at<01:28:30.320> the<01:28:30.440> QR<01:28:30.920> code<01:28:31.920> uh<01:28:32.119> it's<01:28:32.400> eight 01:28:32.669 --> 01:28:32.679 align:start position:0% look at the QR code uh it's eight 01:28:32.679 --> 01:28:34.790 align:start position:0% look at the QR code uh it's eight multiple<01:28:33.159> choice<01:28:33.480> questions<01:28:34.159> there's<01:28:34.320> a 01:28:34.790 --> 01:28:34.800 align:start position:0% multiple choice questions there's a 01:28:34.800 --> 01:28:38.669 align:start position:0% multiple choice questions there's a small<01:28:35.239> contract<01:28:36.119> which<01:28:36.320> was<01:28:37.159> designed<01:28:37.920> by<01:28:38.560> uh 01:28:38.669 --> 01:28:38.679 align:start position:0% small contract which was designed by uh 01:28:38.679 --> 01:28:41.229 align:start position:0% small contract which was designed by uh and<01:28:38.800> this<01:28:38.920> was<01:28:39.080> designed<01:28:39.400> by<01:28:39.560> tincho<01:28:40.560> it<01:28:40.800> has 01:28:41.229 --> 01:28:41.239 align:start position:0% and this was designed by tincho it has 01:28:41.239 --> 01:28:43.590 align:start position:0% and this was designed by tincho it has uh<01:28:41.440> you<01:28:41.520> know<01:28:41.920> for<01:28:42.159> for<01:28:42.320> the<01:28:42.480> devs<01:28:43.159> and<01:28:43.320> for<01:28:43.480> the 01:28:43.590 --> 01:28:43.600 align:start position:0% uh you know for for the devs and for the 01:28:43.600 --> 01:28:46.390 align:start position:0% uh you know for for the devs and for the security<01:28:44.080> researchers<01:28:45.080> there<01:28:45.199> are<01:28:45.480> some<01:28:45.960> bugs 01:28:46.390 --> 01:28:46.400 align:start position:0% security researchers there are some bugs 01:28:46.400 --> 01:28:49.950 align:start position:0% security researchers there are some bugs in<01:28:46.679> these<01:28:47.400> uh<01:28:47.600> contract<01:28:48.440> Snippets<01:28:49.440> so<01:28:49.760> if<01:28:49.840> you 01:28:49.950 --> 01:28:49.960 align:start position:0% in these uh contract Snippets so if you 01:28:49.960 --> 01:28:52.629 align:start position:0% in these uh contract Snippets so if you go<01:28:50.119> to<01:28:50.239> that<01:28:50.440> link<01:28:50.920> and<01:28:51.119> if<01:28:51.280> you<01:28:51.960> use<01:28:52.320> this 01:28:52.629 --> 01:28:52.639 align:start position:0% go to that link and if you use this 01:28:52.639 --> 01:28:55.629 align:start position:0% go to that link and if you use this password<01:28:53.639> you'll<01:28:53.880> be<01:28:54.199> able<01:28:54.400> to<01:28:55.000> answer<01:28:55.360> the 01:28:55.629 --> 01:28:55.639 align:start position:0% password you'll be able to answer the 01:28:55.639 --> 01:28:59.109 align:start position:0% password you'll be able to answer the quiz<01:28:56.639> and<01:28:57.080> uh<01:28:57.199> the<01:28:57.400> top 01:28:59.109 --> 01:28:59.119 align:start position:0% quiz and uh the top 01:28:59.119 --> 01:29:02.109 align:start position:0% quiz and uh the top two<01:29:00.119> top<01:29:00.360> two<01:29:00.560> participants<01:29:01.119> will<01:29:01.400> get 01:29:02.109 --> 01:29:02.119 align:start position:0% two top two participants will get 01:29:02.119 --> 01:29:05.510 align:start position:0% two top two participants will get tickets<01:29:02.719> to<01:29:03.239> DSS<01:29:04.040> next<01:29:04.280> year<01:29:04.520> DSS<01:29:04.960> is<01:29:05.040> the<01:29:05.159> defi 01:29:05.510 --> 01:29:05.520 align:start position:0% tickets to DSS next year DSS is the defi 01:29:05.520 --> 01:29:07.510 align:start position:0% tickets to DSS next year DSS is the defi security<01:29:05.880> Summit<01:29:06.639> the<01:29:06.800> security<01:29:07.159> conference 01:29:07.510 --> 01:29:07.520 align:start position:0% security Summit the security conference 01:29:07.520 --> 01:29:09.229 align:start position:0% security Summit the security conference that<01:29:07.639> happened<01:29:07.920> last<01:29:08.080> week<01:29:08.280> here<01:29:08.400> in<01:29:08.560> Bangkok 01:29:09.229 --> 01:29:09.239 align:start position:0% that happened last week here in Bangkok 01:29:09.239 --> 01:29:10.590 align:start position:0% that happened last week here in Bangkok so<01:29:09.400> hopefully<01:29:09.679> it'll<01:29:09.840> happen<01:29:10.080> next<01:29:10.280> year<01:29:10.480> as 01:29:10.590 --> 01:29:10.600 align:start position:0% so hopefully it'll happen next year as 01:29:10.600 --> 01:29:13.390 align:start position:0% so hopefully it'll happen next year as well<01:29:11.239> so<01:29:11.960> yeah<01:29:12.080> if<01:29:12.199> you<01:29:12.320> get<01:29:12.440> a<01:29:12.600> chance<01:29:13.000> do<01:29:13.239> take 01:29:13.390 --> 01:29:13.400 align:start position:0% well so yeah if you get a chance do take 01:29:13.400 --> 01:29:15.590 align:start position:0% well so yeah if you get a chance do take a<01:29:13.520> look<01:29:13.679> it's<01:29:13.800> going<01:29:13.920> to<01:29:14.040> be<01:29:14.159> open<01:29:14.480> for<01:29:14.679> about<01:29:14.840> a 01:29:15.590 --> 01:29:15.600 align:start position:0% a look it's going to be open for about a 01:29:15.600 --> 01:29:17.990 align:start position:0% a look it's going to be open for about a day<01:29:16.600> and<01:29:16.760> any<01:29:16.920> further<01:29:17.239> questions<01:29:17.560> so<01:29:17.760> yes 01:29:17.990 --> 01:29:18.000 align:start position:0% day and any further questions so yes 01:29:18.000 --> 01:29:19.510 align:start position:0% day and any further questions so yes thank<01:29:18.159> you<01:29:18.239> for<01:29:18.360> sticking<01:29:18.639> along<01:29:18.960> any<01:29:19.119> further 01:29:19.510 --> 01:29:19.520 align:start position:0% thank you for sticking along any further 01:29:19.520 --> 01:29:21.430 align:start position:0% thank you for sticking along any further questions<01:29:20.520> uh<01:29:20.600> we're<01:29:20.800> going<01:29:20.880> to<01:29:21.000> be<01:29:21.119> hanging 01:29:21.430 --> 01:29:21.440 align:start position:0% questions uh we're going to be hanging 01:29:21.440 --> 01:29:23.510 align:start position:0% questions uh we're going to be hanging around<01:29:22.239> in<01:29:22.520> oh<01:29:22.679> there's<01:29:22.880> one<01:29:23.040> question<01:29:23.239> in<01:29:23.360> the 01:29:23.510 --> 01:29:23.520 align:start position:0% around in oh there's one question in the 01:29:23.520 --> 01:29:28.510 align:start position:0% around in oh there's one question in the room 01:29:28.510 --> 01:29:28.520 align:start position:0% 01:29:28.520 --> 01:29:30.750 align:start position:0% thank<01:29:28.719> you<01:29:29.199> can<01:29:29.360> I<01:29:29.520> explain<01:29:29.920> the<01:29:30.119> history<01:29:30.520> of 01:29:30.750 --> 01:29:30.760 align:start position:0% thank you can I explain the history of 01:29:30.760 --> 01:29:33.070 align:start position:0% thank you can I explain the history of the<01:29:31.000> issues<01:29:31.400> that<01:29:31.560> was<01:29:31.800> asked<01:29:32.520> regarding<01:29:32.920> the 01:29:33.070 --> 01:29:33.080 align:start position:0% the issues that was asked regarding the 01:29:33.080 --> 01:29:34.669 align:start position:0% the issues that was asked regarding the erc20 01:29:34.669 --> 01:29:34.679 align:start position:0% erc20 01:29:34.679 --> 01:29:37.590 align:start position:0% erc20 standard<01:29:35.679> can<01:29:35.840> I<01:29:36.119> explain<01:29:36.480> it<01:29:36.679> and<01:29:37.040> ask<01:29:37.440> you 01:29:37.590 --> 01:29:37.600 align:start position:0% standard can I explain it and ask you 01:29:37.600 --> 01:29:41.350 align:start position:0% standard can I explain it and ask you for<01:29:37.880> your<01:29:38.119> opinion<01:29:38.520> regarding<01:29:38.920> the 01:29:41.350 --> 01:29:41.360 align:start position:0% 01:29:41.360 --> 01:29:43.390 align:start position:0% issue<01:29:42.360> I<01:29:42.480> I'm<01:29:42.600> sorry<01:29:42.840> I<01:29:42.920> don't<01:29:43.280> understand 01:29:43.390 --> 01:29:43.400 align:start position:0% issue I I'm sorry I don't understand 01:29:43.400 --> 01:29:45.350 align:start position:0% issue I I'm sorry I don't understand your<01:29:43.560> question<01:29:44.000> history<01:29:44.360> of<01:29:44.520> the<01:29:44.639> erc20 01:29:45.350 --> 01:29:45.360 align:start position:0% your question history of the erc20 01:29:45.360 --> 01:29:46.870 align:start position:0% your question history of the erc20 attack<01:29:46.080> the 01:29:46.870 --> 01:29:46.880 align:start position:0% attack the 01:29:46.880 --> 01:29:50.350 align:start position:0% attack the erc20<01:29:47.880> uh<01:29:48.080> problem<01:29:48.600> that<01:29:48.840> was<01:29:49.159> asked<01:29:49.520> in<01:29:49.800> this 01:29:50.350 --> 01:29:50.360 align:start position:0% erc20 uh problem that was asked in this 01:29:50.360 --> 01:29:53.430 align:start position:0% erc20 uh problem that was asked in this uh<01:29:50.560> commments<01:29:50.920> channel<01:29:51.880> the<01:29:52.080> erc20<01:29:52.880> standard 01:29:53.430 --> 01:29:53.440 align:start position:0% uh commments channel the erc20 standard 01:29:53.440 --> 01:29:55.990 align:start position:0% uh commments channel the erc20 standard contain<01:29:54.119> security<01:29:54.480> flaw<01:29:55.280> that<01:29:55.480> the<01:29:55.639> Fabian 01:29:55.990 --> 01:29:56.000 align:start position:0% contain security flaw that the Fabian 01:29:56.000 --> 01:29:58.350 align:start position:0% contain security flaw that the Fabian vage<01:29:56.679> the<01:29:56.800> creator<01:29:57.119> of<01:29:57.280> rc20<01:29:57.920> standard 01:29:58.350 --> 01:29:58.360 align:start position:0% vage the creator of rc20 standard 01:29:58.360 --> 01:29:59.550 align:start position:0% vage the creator of rc20 standard confirmed<01:29:58.880> in 01:29:59.550 --> 01:29:59.560 align:start position:0% confirmed in 01:29:59.560 --> 01:30:02.390 align:start position:0% confirmed in 2023<01:30:00.560> uh<01:30:00.679> it<01:30:00.840> is<01:30:01.040> classified<01:30:01.639> as<01:30:01.760> the<01:30:02.000> lack<01:30:02.239> of 01:30:02.390 --> 01:30:02.400 align:start position:0% 2023 uh it is classified as the lack of 01:30:02.400 --> 01:30:04.510 align:start position:0% 2023 uh it is classified as the lack of transaction<01:30:02.880> handling<01:30:03.400> so<01:30:03.600> the<01:30:03.719> erc20 01:30:04.510 --> 01:30:04.520 align:start position:0% transaction handling so the erc20 01:30:04.520 --> 01:30:07.470 align:start position:0% transaction handling so the erc20 standard<01:30:05.159> is<01:30:05.400> designed<01:30:05.880> in<01:30:06.119> such<01:30:06.280> a<01:30:06.480> way<01:30:07.119> that 01:30:07.470 --> 01:30:07.480 align:start position:0% standard is designed in such a way that 01:30:07.480 --> 01:30:10.030 align:start position:0% standard is designed in such a way that uh<01:30:07.639> when<01:30:07.920> you<01:30:08.199> are<01:30:08.480> trying<01:30:08.800> to<01:30:08.960> send<01:30:09.280> tokens<01:30:09.880> to 01:30:10.030 --> 01:30:10.040 align:start position:0% uh when you are trying to send tokens to 01:30:10.040 --> 01:30:12.149 align:start position:0% uh when you are trying to send tokens to a<01:30:10.199> Smart<01:30:10.520> contract<01:30:11.280> which<01:30:11.440> is<01:30:11.600> not<01:30:11.840> designed 01:30:12.149 --> 01:30:12.159 align:start position:0% a Smart contract which is not designed 01:30:12.159 --> 01:30:14.629 align:start position:0% a Smart contract which is not designed to<01:30:12.360> receive<01:30:12.719> Tokens<01:30:13.320> The<01:30:13.520> Tokens<01:30:13.840> are<01:30:14.080> lost 01:30:14.629 --> 01:30:14.639 align:start position:0% to receive Tokens The Tokens are lost 01:30:14.639 --> 01:30:16.629 align:start position:0% to receive Tokens The Tokens are lost permanently<01:30:15.639> for<01:30:15.840> example<01:30:16.199> if<01:30:16.320> you<01:30:16.440> would 01:30:16.629 --> 01:30:16.639 align:start position:0% permanently for example if you would 01:30:16.639 --> 01:30:18.910 align:start position:0% permanently for example if you would send<01:30:17.159> ethereum<01:30:17.719> to<01:30:18.000> some<01:30:18.159> smart<01:30:18.440> contract 01:30:18.910 --> 01:30:18.920 align:start position:0% send ethereum to some smart contract 01:30:18.920 --> 01:30:20.590 align:start position:0% send ethereum to some smart contract which<01:30:19.080> is<01:30:19.239> not<01:30:19.560> imp<01:30:20.080> which<01:30:20.239> does<01:30:20.440> not 01:30:20.590 --> 01:30:20.600 align:start position:0% which is not imp which does not 01:30:20.600 --> 01:30:22.910 align:start position:0% which is not imp which does not implement<01:30:21.080> the<01:30:21.320> receive<01:30:21.760> function<01:30:22.440> or<01:30:22.679> if<01:30:22.800> you 01:30:22.910 --> 01:30:22.920 align:start position:0% implement the receive function or if you 01:30:22.920 --> 01:30:25.830 align:start position:0% implement the receive function or if you will<01:30:23.119> send<01:30:23.400> the<01:30:23.560> nft<01:30:24.159> token<01:30:24.639> to<01:30:24.960> such<01:30:25.360> contract 01:30:25.830 --> 01:30:25.840 align:start position:0% will send the nft token to such contract 01:30:25.840 --> 01:30:27.590 align:start position:0% will send the nft token to such contract that<01:30:26.000> doesn't<01:30:26.520> that<01:30:26.679> does<01:30:26.840> not<01:30:27.000> implement<01:30:27.400> the 01:30:27.590 --> 01:30:27.600 align:start position:0% that doesn't that does not implement the 01:30:27.600 --> 01:30:29.709 align:start position:0% that doesn't that does not implement the on<01:30:28.000> ERC 01:30:29.709 --> 01:30:29.719 align:start position:0% on ERC 01:30:29.719 --> 01:30:32.790 align:start position:0% on ERC 721<01:30:30.719> uh<01:30:30.920> reception<01:30:31.440> function<01:30:32.280> uh<01:30:32.400> it<01:30:32.520> will<01:30:32.679> not 01:30:32.790 --> 01:30:32.800 align:start position:0% 721 uh reception function uh it will not 01:30:32.800 --> 01:30:36.030 align:start position:0% 721 uh reception function uh it will not be<01:30:32.920> lost<01:30:33.400> but<01:30:33.520> the<01:30:33.679> ec20<01:30:34.520> token<01:30:34.920> cannot<01:30:35.280> be<01:30:35.800> uh 01:30:36.030 --> 01:30:36.040 align:start position:0% be lost but the ec20 token cannot be uh 01:30:36.040 --> 01:30:39.430 align:start position:0% be lost but the ec20 token cannot be uh uh<01:30:36.239> handled<01:30:36.719> on<01:30:37.159> uh<01:30:37.320> the<01:30:37.639> contract's<01:30:38.440> uh<01:30:38.760> side 01:30:39.430 --> 01:30:39.440 align:start position:0% uh handled on uh the contract's uh side 01:30:39.440 --> 01:30:42.109 align:start position:0% uh handled on uh the contract's uh side as<01:30:39.560> a<01:30:39.679> result<01:30:40.440> uh<01:30:40.800> if<01:30:40.920> you<01:30:41.080> send<01:30:41.440> such<01:30:41.679> tokens 01:30:42.109 --> 01:30:42.119 align:start position:0% as a result uh if you send such tokens 01:30:42.119 --> 01:30:44.430 align:start position:0% as a result uh if you send such tokens to<01:30:42.600> a<01:30:42.719> Smart<01:30:43.040> contract<01:30:43.520> that<01:30:43.719> cannot<01:30:44.040> reject 01:30:44.430 --> 01:30:44.440 align:start position:0% to a Smart contract that cannot reject 01:30:44.440 --> 01:30:46.910 align:start position:0% to a Smart contract that cannot reject them<01:30:44.760> they<01:30:44.920> will<01:30:45.040> be<01:30:45.239> permanently<01:30:45.719> lost<01:30:46.040> so<01:30:46.600> in 01:30:46.910 --> 01:30:46.920 align:start position:0% them they will be permanently lost so in 01:30:46.920 --> 01:30:50.990 align:start position:0% them they will be permanently lost so in uh<01:30:47.080> 2017<01:30:48.080> this<01:30:48.280> issue<01:30:48.639> was<01:30:49.400> described<01:30:50.400> uh 01:30:50.990 --> 01:30:51.000 align:start position:0% uh 2017 this issue was described uh 01:30:51.000 --> 01:30:53.350 align:start position:0% uh 2017 this issue was described uh there<01:30:51.159> was<01:30:51.520> 16,000<01:30:52.360> of<01:30:52.520> dollars<01:30:52.840> lost<01:30:53.159> because 01:30:53.350 --> 01:30:53.360 align:start position:0% there was 16,000 of dollars lost because 01:30:53.360 --> 01:30:55.669 align:start position:0% there was 16,000 of dollars lost because of<01:30:53.520> this<01:30:53.679> issue<01:30:54.080> at<01:30:54.280> that<01:30:54.520> time<01:30:55.000> in<01:30:55.159> the<01:30:55.400> next 01:30:55.669 --> 01:30:55.679 align:start position:0% of this issue at that time in the next 01:30:55.679 --> 01:30:57.790 align:start position:0% of this issue at that time in the next year<01:30:56.040> there<01:30:56.239> were<01:30:56.560> $2<01:30:56.880> millions<01:30:57.320> of<01:30:57.480> dollars 01:30:57.790 --> 01:30:57.800 align:start position:0% year there were $2 millions of dollars 01:30:57.800 --> 01:31:01.430 align:start position:0% year there were $2 millions of dollars lost<01:30:58.480> uh<01:30:58.600> in<01:30:59.080> 2023<01:31:00.080> there<01:31:00.280> were<01:31:00.560> $60<01:31:01.040> millions 01:31:01.430 --> 01:31:01.440 align:start position:0% lost uh in 2023 there were $60 millions 01:31:01.440 --> 01:31:03.270 align:start position:0% lost uh in 2023 there were $60 millions of<01:31:01.600> dollar<01:31:01.960> loss<01:31:02.280> because<01:31:02.480> of<01:31:02.719> this<01:31:02.920> issue 01:31:03.270 --> 01:31:03.280 align:start position:0% of dollar loss because of this issue 01:31:03.280 --> 01:31:05.990 align:start position:0% of dollar loss because of this issue because<01:31:03.480> it<01:31:03.639> is<01:31:03.840> still<01:31:04.119> not<01:31:04.520> patched<01:31:05.239> and<01:31:05.639> uh 01:31:05.990 --> 01:31:06.000 align:start position:0% because it is still not patched and uh 01:31:06.000 --> 01:31:08.310 align:start position:0% because it is still not patched and uh on<01:31:06.199> 1st<01:31:06.600> November 01:31:08.310 --> 01:31:08.320 align:start position:0% on 1st November 01:31:08.320 --> 01:31:11.030 align:start position:0% on 1st November 2024<01:31:09.320> there<01:31:09.480> were<01:31:09.920> $90<01:31:10.239> millions<01:31:10.560> of<01:31:10.719> dollars 01:31:11.030 --> 01:31:11.040 align:start position:0% 2024 there were $90 millions of dollars 01:31:11.040 --> 01:31:14.510 align:start position:0% 2024 there were $90 millions of dollars lost<01:31:11.480> and<01:31:11.639> two<01:31:11.880> days<01:31:12.119> ago<01:31:12.440> a<01:31:12.719> user<01:31:13.119> lost<01:31:13.760> $25 01:31:14.510 --> 01:31:14.520 align:start position:0% lost and two days ago a user lost $25 01:31:14.520 --> 01:31:16.149 align:start position:0% lost and two days ago a user lost $25 millions<01:31:14.920> of<01:31:15.119> dollars<01:31:15.480> because<01:31:15.719> of<01:31:15.920> this 01:31:16.149 --> 01:31:16.159 align:start position:0% millions of dollars because of this 01:31:16.159 --> 01:31:17.109 align:start position:0% millions of dollars because of this exact 01:31:17.109 --> 01:31:17.119 align:start position:0% exact 01:31:17.119 --> 01:31:20.550 align:start position:0% exact issue<01:31:18.119> got<01:31:18.280> it<01:31:18.760> yeah<01:31:18.920> I<01:31:19.040> think<01:31:19.480> uh<01:31:20.159> we 01:31:20.550 --> 01:31:20.560 align:start position:0% issue got it yeah I think uh we 01:31:20.560 --> 01:31:21.950 align:start position:0% issue got it yeah I think uh we understand<01:31:20.719> it<01:31:20.840> now<01:31:21.000> so<01:31:21.159> token<01:31:21.480> sent<01:31:21.679> to<01:31:21.800> a 01:31:21.950 --> 01:31:21.960 align:start position:0% understand it now so token sent to a 01:31:21.960 --> 01:31:23.990 align:start position:0% understand it now so token sent to a contract<01:31:22.360> being<01:31:22.639> lost<01:31:23.440> right<01:31:23.639> as<01:31:23.760> a<01:31:23.920> as 01:31:23.990 --> 01:31:24.000 align:start position:0% contract being lost right as a as 01:31:24.000 --> 01:31:26.830 align:start position:0% contract being lost right as a as opposed<01:31:24.280> to<01:31:24.600> being<01:31:24.920> sent<01:31:25.920> uh<01:31:26.119> accidentally<01:31:26.679> to 01:31:26.830 --> 01:31:26.840 align:start position:0% opposed to being sent uh accidentally to 01:31:26.840 --> 01:31:29.229 align:start position:0% opposed to being sent uh accidentally to a<01:31:27.000> contract<01:31:27.679> right 01:31:29.229 --> 01:31:29.239 align:start position:0% a contract right 01:31:29.239 --> 01:31:30.910 align:start position:0% a contract right so<01:31:30.239> I 01:31:30.910 --> 01:31:30.920 align:start position:0% so I 01:31:30.920 --> 01:31:33.870 align:start position:0% so I believe<01:31:31.920> I<01:31:32.000> mean<01:31:32.480> it<01:31:32.639> is<01:31:33.000> it<01:31:33.119> is<01:31:33.400> how<01:31:33.560> it<01:31:33.679> has 01:31:33.870 --> 01:31:33.880 align:start position:0% believe I mean it is it is how it has 01:31:33.880 --> 01:31:36.629 align:start position:0% believe I mean it is it is how it has been<01:31:34.199> designed<01:31:35.040> so<01:31:35.480> users<01:31:35.960> actually<01:31:36.320> excuse 01:31:36.629 --> 01:31:36.639 align:start position:0% been designed so users actually excuse 01:31:36.639 --> 01:31:40.990 align:start position:0% been designed so users actually excuse me<01:31:37.320> uh<01:31:37.800> why<01:31:38.239> is<01:31:38.719> ethereum<01:31:39.320> and<01:31:39.560> NF<01:31:40.280> designed<01:31:40.760> in 01:31:40.990 --> 01:31:41.000 align:start position:0% me uh why is ethereum and NF designed in 01:31:41.000 --> 01:31:42.910 align:start position:0% me uh why is ethereum and NF designed in another<01:31:41.440> way<01:31:41.639> and<01:31:41.840> does<01:31:42.040> not<01:31:42.239> cause<01:31:42.560> the<01:31:42.679> loss 01:31:42.910 --> 01:31:42.920 align:start position:0% another way and does not cause the loss 01:31:42.920 --> 01:31:45.430 align:start position:0% another way and does not cause the loss of<01:31:43.159> money<01:31:43.520> for<01:31:43.800> users<01:31:44.239> do<01:31:44.360> we<01:31:44.520> want<01:31:44.719> to<01:31:45.080> say 01:31:45.430 --> 01:31:45.440 align:start position:0% of money for users do we want to say 01:31:45.440 --> 01:31:48.070 align:start position:0% of money for users do we want to say that<01:31:45.880> the<01:31:46.040> loss<01:31:46.280> of<01:31:46.440> money<01:31:46.800> was<01:31:47.040> designed<01:31:48.000> I 01:31:48.070 --> 01:31:48.080 align:start position:0% that the loss of money was designed I 01:31:48.080 --> 01:31:49.750 align:start position:0% that the loss of money was designed I don't<01:31:48.280> believe<01:31:48.600> so<01:31:48.840> this<01:31:48.960> is<01:31:49.159> very<01:31:49.400> specific 01:31:49.750 --> 01:31:49.760 align:start position:0% don't believe so this is very specific 01:31:49.760 --> 01:31:51.910 align:start position:0% don't believe so this is very specific to<01:31:49.920> Smart<01:31:50.239> contracts<01:31:51.040> right<01:31:51.280> and<01:31:51.400> it's<01:31:51.600> not 01:31:51.910 --> 01:31:51.920 align:start position:0% to Smart contracts right and it's not 01:31:51.920 --> 01:31:53.229 align:start position:0% to Smart contracts right and it's not nothing<01:31:52.159> to<01:31:52.280> do<01:31:52.400> with<01:31:52.520> the<01:31:52.600> ethereum<01:31:53.000> base 01:31:53.229 --> 01:31:53.239 align:start position:0% nothing to do with the ethereum base 01:31:53.239 --> 01:31:56.629 align:start position:0% nothing to do with the ethereum base layer<01:31:53.960> and<01:31:54.080> it<01:31:54.280> also<01:31:54.800> is<01:31:55.119> about<01:31:55.920> how<01:31:56.159> your 01:31:56.629 --> 01:31:56.639 align:start position:0% layer and it also is about how your 01:31:56.639 --> 01:32:00.229 align:start position:0% layer and it also is about how your smart<01:31:57.000> contract<01:31:57.440> works<01:31:58.119> right<01:31:58.520> so<01:31:59.400> we<01:31:59.520> can<01:32:00.000> go 01:32:00.229 --> 01:32:00.239 align:start position:0% smart contract works right so we can go 01:32:00.239 --> 01:32:01.990 align:start position:0% smart contract works right so we can go deeper<01:32:00.600> into<01:32:00.880> this<01:32:01.040> I<01:32:01.119> think<01:32:01.280> there's<01:32:01.440> a 01:32:01.990 --> 01:32:02.000 align:start position:0% deeper into this I think there's a 01:32:02.000 --> 01:32:04.270 align:start position:0% deeper into this I think there's a misunderstanding<01:32:02.760> here<01:32:03.159> so<01:32:03.320> we<01:32:03.480> can<01:32:03.960> uh<01:32:04.080> talk 01:32:04.270 --> 01:32:04.280 align:start position:0% misunderstanding here so we can uh talk 01:32:04.280 --> 01:32:05.830 align:start position:0% misunderstanding here so we can uh talk about<01:32:04.560> this<01:32:04.760> but<01:32:04.920> time's<01:32:05.199> up<01:32:05.400> but<01:32:05.520> we<01:32:05.679> also 01:32:05.830 --> 01:32:05.840 align:start position:0% about this but time's up but we also 01:32:05.840 --> 01:32:07.149 align:start position:0% about this but time's up but we also want<01:32:05.960> to<01:32:06.119> take<01:32:06.280> the<01:32:06.440> last<01:32:06.639> question<01:32:06.880> in<01:32:07.000> this 01:32:07.149 --> 01:32:07.159 align:start position:0% want to take the last question in this 01:32:07.159 --> 01:32:09.550 align:start position:0% want to take the last question in this room<01:32:07.639> uh<01:32:07.800> thank<01:32:08.000> you<01:32:08.320> uh<01:32:08.560> just<01:32:08.840> very<01:32:09.040> curious 01:32:09.550 --> 01:32:09.560 align:start position:0% room uh thank you uh just very curious 01:32:09.560 --> 01:32:12.910 align:start position:0% room uh thank you uh just very curious uh<01:32:10.320> uh<01:32:11.119> perhaps<01:32:11.520> maybe<01:32:11.840> the<01:32:11.920> three<01:32:12.159> of<01:32:12.280> you<01:32:12.440> can 01:32:12.910 --> 01:32:12.920 align:start position:0% uh uh perhaps maybe the three of you can 01:32:12.920 --> 01:32:14.669 align:start position:0% uh uh perhaps maybe the three of you can uh<01:32:13.040> like<01:32:13.199> describe<01:32:13.760> how<01:32:13.960> you<01:32:14.280> approach<01:32:14.600> a 01:32:14.669 --> 01:32:14.679 align:start position:0% uh like describe how you approach a 01:32:14.679 --> 01:32:16.950 align:start position:0% uh like describe how you approach a fresh<01:32:15.080> Cod<01:32:15.320> code<01:32:15.520> base<01:32:15.800> where<01:32:15.920> you<01:32:16.040> studied 01:32:16.950 --> 01:32:16.960 align:start position:0% fresh Cod code base where you studied 01:32:16.960 --> 01:32:19.270 align:start position:0% fresh Cod code base where you studied and<01:32:17.280> like<01:32:17.440> how<01:32:17.520> do<01:32:17.600> you<01:32:17.719> map<01:32:18.040> out<01:32:18.800> and<01:32:19.080> what 01:32:19.270 --> 01:32:19.280 align:start position:0% and like how do you map out and what 01:32:19.280 --> 01:32:21.629 align:start position:0% and like how do you map out and what your<01:32:19.440> workflow<01:32:19.960> like<01:32:20.480> thank 01:32:21.629 --> 01:32:21.639 align:start position:0% your workflow like thank 01:32:21.639 --> 01:32:25.189 align:start position:0% your workflow like thank you<01:32:22.639> how<01:32:22.800> do<01:32:22.920> you<01:32:23.239> look<01:32:23.560> appro<01:32:24.000> a<01:32:24.119> fresh<01:32:24.360> code 01:32:25.189 --> 01:32:25.199 align:start position:0% you how do you look appro a fresh code 01:32:25.199 --> 01:32:28.750 align:start position:0% you how do you look appro a fresh code pleas<01:32:26.199> so<01:32:26.880> I<01:32:27.040> already<01:32:27.920> answered<01:32:28.239> the<01:32:28.440> question 01:32:28.750 --> 01:32:28.760 align:start position:0% pleas so I already answered the question 01:32:28.760 --> 01:32:31.149 align:start position:0% pleas so I already answered the question I<01:32:28.840> think<01:32:29.119> before<01:32:29.840> so<01:32:30.080> me<01:32:30.280> personally<01:32:30.719> I<01:32:30.840> start 01:32:31.149 --> 01:32:31.159 align:start position:0% I think before so me personally I start 01:32:31.159 --> 01:32:32.870 align:start position:0% I think before so me personally I start with<01:32:31.280> the<01:32:31.480> documentation<01:32:32.480> because<01:32:32.679> there's 01:32:32.870 --> 01:32:32.880 align:start position:0% with the documentation because there's 01:32:32.880 --> 01:32:34.910 align:start position:0% with the documentation because there's going<01:32:33.000> to<01:32:33.159> be<01:32:33.760> problem<01:32:34.560> sometimes<01:32:34.760> you 01:32:34.910 --> 01:32:34.920 align:start position:0% going to be problem sometimes you 01:32:34.920 --> 01:32:36.510 align:start position:0% going to be problem sometimes you already<01:32:35.239> find<01:32:35.480> bugs<01:32:35.800> just<01:32:35.960> reading 01:32:36.510 --> 01:32:36.520 align:start position:0% already find bugs just reading 01:32:36.520 --> 01:32:38.510 align:start position:0% already find bugs just reading documentation<01:32:37.520> I<01:32:37.600> think<01:32:37.760> I<01:32:37.840> saw<01:32:38.040> a<01:32:38.159> Twitter 01:32:38.510 --> 01:32:38.520 align:start position:0% documentation I think I saw a Twitter 01:32:38.520 --> 01:32:41.149 align:start position:0% documentation I think I saw a Twitter message<01:32:39.040> like<01:32:39.440> or<01:32:40.119> the<01:32:40.239> other<01:32:40.520> day<01:32:40.960> where 01:32:41.149 --> 01:32:41.159 align:start position:0% message like or the other day where 01:32:41.159 --> 01:32:43.149 align:start position:0% message like or the other day where someone<01:32:41.880> actually<01:32:42.239> did<01:32:42.480> the<01:32:42.639> same<01:32:42.920> thing 01:32:43.149 --> 01:32:43.159 align:start position:0% someone actually did the same thing 01:32:43.159 --> 01:32:45.950 align:start position:0% someone actually did the same thing found<01:32:43.440> a<01:32:43.600> bug<01:32:44.040> reading<01:32:44.440> just<01:32:44.960> documentation 01:32:45.950 --> 01:32:45.960 align:start position:0% found a bug reading just documentation 01:32:45.960 --> 01:32:48.550 align:start position:0% found a bug reading just documentation and<01:32:46.199> then<01:32:46.440> usually<01:32:47.080> like<01:32:47.880> Global<01:32:48.119> scanning<01:32:48.440> of 01:32:48.550 --> 01:32:48.560 align:start position:0% and then usually like Global scanning of 01:32:48.560 --> 01:32:50.510 align:start position:0% and then usually like Global scanning of the<01:32:48.639> code<01:32:48.880> base<01:32:49.400> and<01:32:49.520> then<01:32:49.679> for<01:32:49.840> me<01:32:50.040> I<01:32:50.199> usually 01:32:50.510 --> 01:32:50.520 align:start position:0% the code base and then for me I usually 01:32:50.520 --> 01:32:53.070 align:start position:0% the code base and then for me I usually take<01:32:50.679> the<01:32:50.880> go<01:32:51.159> deep<01:32:51.440> approach<01:32:52.119> so<01:32:52.320> I<01:32:52.520> just<01:32:52.800> like 01:32:53.070 --> 01:32:53.080 align:start position:0% take the go deep approach so I just like 01:32:53.080 --> 01:32:54.830 align:start position:0% take the go deep approach so I just like spearhead<01:32:53.679> for<01:32:53.840> for<01:32:53.960> the<01:32:54.040> parts<01:32:54.280> that<01:32:54.480> I<01:32:54.639> think 01:32:54.830 --> 01:32:54.840 align:start position:0% spearhead for for the parts that I think 01:32:54.840 --> 01:32:57.510 align:start position:0% spearhead for for the parts that I think are<01:32:55.480> uh<01:32:55.719> vulnerable<01:32:56.520> but<01:32:56.719> I<01:32:56.800> think<01:32:57.040> that<01:32:57.280> is 01:32:57.510 --> 01:32:57.520 align:start position:0% are uh vulnerable but I think that is 01:32:57.520 --> 01:32:59.629 align:start position:0% are uh vulnerable but I think that is mostly<01:32:57.920> a<01:32:58.199> bounty<01:32:58.600> hunting<01:32:58.960> approach<01:32:59.400> doesn't 01:32:59.629 --> 01:32:59.639 align:start position:0% mostly a bounty hunting approach doesn't 01:32:59.639 --> 01:33:03.109 align:start position:0% mostly a bounty hunting approach doesn't work<01:32:59.800> for<01:33:00.000> auditing<01:33:00.960> or<01:33:01.719> yeah<01:33:02.440> a<01:33:02.600> let<01:33:02.840> others 01:33:03.109 --> 01:33:03.119 align:start position:0% work for auditing or yeah a let others 01:33:03.119 --> 01:33:05.669 align:start position:0% work for auditing or yeah a let others speak<01:33:03.360> to<01:33:04.000> that<01:33:05.000> hey<01:33:05.199> thanks<01:33:05.360> for<01:33:05.520> the 01:33:05.669 --> 01:33:05.679 align:start position:0% speak to that hey thanks for the 01:33:05.679 --> 01:33:09.590 align:start position:0% speak to that hey thanks for the question<01:33:06.239> uh<01:33:06.360> so<01:33:06.560> in<01:33:06.719> my<01:33:07.440> case<01:33:08.440> um<01:33:09.040> I<01:33:09.159> will<01:33:09.360> say 01:33:09.590 --> 01:33:09.600 align:start position:0% question uh so in my case um I will say 01:33:09.600 --> 01:33:12.430 align:start position:0% question uh so in my case um I will say yeah<01:33:09.840> documentation<01:33:10.760> first<01:33:11.760> uh<01:33:11.920> with<01:33:12.080> a 01:33:12.430 --> 01:33:12.440 align:start position:0% yeah documentation first uh with a 01:33:12.440 --> 01:33:14.310 align:start position:0% yeah documentation first uh with a healthy<01:33:12.880> dose<01:33:13.199> of<01:33:13.440> disrespect<01:33:14.000> for<01:33:14.199> the 01:33:14.310 --> 01:33:14.320 align:start position:0% healthy dose of disrespect for the 01:33:14.320 --> 01:33:16.070 align:start position:0% healthy dose of disrespect for the documentation<01:33:15.119> don't<01:33:15.400> trust<01:33:15.800> everything 01:33:16.070 --> 01:33:16.080 align:start position:0% documentation don't trust everything 01:33:16.080 --> 01:33:17.470 align:start position:0% documentation don't trust everything that<01:33:16.199> you<01:33:16.320> read<01:33:16.639> because<01:33:16.840> it<01:33:16.960> might<01:33:17.119> be<01:33:17.239> a<01:33:17.320> case 01:33:17.470 --> 01:33:17.480 align:start position:0% that you read because it might be a case 01:33:17.480 --> 01:33:18.669 align:start position:0% that you read because it might be a case that<01:33:17.600> in<01:33:17.679> the<01:33:17.840> code<01:33:18.040> doesn't<01:33:18.320> match<01:33:18.560> the 01:33:18.669 --> 01:33:18.679 align:start position:0% that in the code doesn't match the 01:33:18.679 --> 01:33:20.149 align:start position:0% that in the code doesn't match the documentation<01:33:19.239> so<01:33:19.400> you<01:33:19.560> have<01:33:19.719> fun<01:33:19.960> with 01:33:20.149 --> 01:33:20.159 align:start position:0% documentation so you have fun with 01:33:20.159 --> 01:33:21.109 align:start position:0% documentation so you have fun with issues 01:33:21.109 --> 01:33:21.119 align:start position:0% issues 01:33:21.119 --> 01:33:24.310 align:start position:0% issues there<01:33:22.119> um<01:33:22.639> and<01:33:22.880> what<01:33:23.000> I<01:33:23.119> would<01:33:23.280> also<01:33:23.520> do<01:33:23.920> is 01:33:24.310 --> 01:33:24.320 align:start position:0% there um and what I would also do is 01:33:24.320 --> 01:33:25.950 align:start position:0% there um and what I would also do is just<01:33:24.600> this<01:33:24.719> is<01:33:24.920> perhaps<01:33:25.239> something<01:33:25.600> personal 01:33:25.950 --> 01:33:25.960 align:start position:0% just this is perhaps something personal 01:33:25.960 --> 01:33:28.350 align:start position:0% just this is perhaps something personal but<01:33:26.080> I<01:33:26.199> will<01:33:26.520> just<01:33:27.320> start<01:33:27.600> with<01:33:27.760> the<01:33:27.920> little 01:33:28.350 --> 01:33:28.360 align:start position:0% but I will just start with the little 01:33:28.360 --> 01:33:31.149 align:start position:0% but I will just start with the little Parts<01:33:29.119> uh<01:33:29.679> I<01:33:29.800> wouldn't<01:33:30.080> go<01:33:30.280> first<01:33:30.520> for<01:33:30.679> the<01:33:30.840> big 01:33:31.149 --> 01:33:31.159 align:start position:0% Parts uh I wouldn't go first for the big 01:33:31.159 --> 01:33:32.470 align:start position:0% Parts uh I wouldn't go first for the big contracts<01:33:31.639> where<01:33:31.800> you<01:33:31.920> have<01:33:32.080> like<01:33:32.239> all<01:33:32.360> the 01:33:32.470 --> 01:33:32.480 align:start position:0% contracts where you have like all the 01:33:32.480 --> 01:33:34.270 align:start position:0% contracts where you have like all the main<01:33:32.719> interaction<01:33:33.239> everything<01:33:33.880> sometimes<01:33:34.080> I 01:33:34.270 --> 01:33:34.280 align:start position:0% main interaction everything sometimes I 01:33:34.280 --> 01:33:36.629 align:start position:0% main interaction everything sometimes I just<01:33:34.480> start<01:33:34.760> by<01:33:34.960> the<01:33:35.520> small<01:33:35.880> libraries<01:33:36.440> but 01:33:36.629 --> 01:33:36.639 align:start position:0% just start by the small libraries but 01:33:36.639 --> 01:33:40.189 align:start position:0% just start by the small libraries but isolated<01:33:37.320> things<01:33:38.159> that<01:33:38.320> I<01:33:38.440> can<01:33:38.719> then<01:33:39.440> just 01:33:40.189 --> 01:33:40.199 align:start position:0% isolated things that I can then just 01:33:40.199 --> 01:33:42.870 align:start position:0% isolated things that I can then just treat<01:33:40.719> as<01:33:41.040> black<01:33:41.280> boxes<01:33:41.760> in<01:33:41.920> in<01:33:42.040> the<01:33:42.159> future<01:33:42.760> in 01:33:42.870 --> 01:33:42.880 align:start position:0% treat as black boxes in in the future in 01:33:42.880 --> 01:33:44.669 align:start position:0% treat as black boxes in in the future in the<01:33:43.280> so<01:33:43.639> I<01:33:43.719> would<01:33:43.960> start<01:33:44.159> at<01:33:44.280> the<01:33:44.360> beginning 01:33:44.669 --> 01:33:44.679 align:start position:0% the so I would start at the beginning 01:33:44.679 --> 01:33:48.109 align:start position:0% the so I would start at the beginning with<01:33:44.840> those<01:33:45.000> and<01:33:45.119> then<01:33:45.280> move<01:33:45.560> up<01:33:46.040> into 01:33:48.109 --> 01:33:48.119 align:start position:0% with those and then move up into 01:33:48.119 --> 01:33:50.109 align:start position:0% with those and then move up into complexity<01:33:49.119> yeah<01:33:49.320> I<01:33:49.400> would<01:33:49.639> Echo 01:33:50.109 --> 01:33:50.119 align:start position:0% complexity yeah I would Echo 01:33:50.119 --> 01:33:52.669 align:start position:0% complexity yeah I would Echo documentation<01:33:51.119> I<01:33:51.199> would<01:33:51.400> also<01:33:51.840> add<01:33:52.520> um 01:33:52.669 --> 01:33:52.679 align:start position:0% documentation I would also add um 01:33:52.679 --> 01:33:54.709 align:start position:0% documentation I would also add um starting<01:33:53.080> to<01:33:53.320> like<01:33:53.480> find<01:33:54.000> and<01:33:54.159> identify 01:33:54.709 --> 01:33:54.719 align:start position:0% starting to like find and identify 01:33:54.719 --> 01:33:57.310 align:start position:0% starting to like find and identify invariance<01:33:55.360> from<01:33:55.480> the<01:33:55.719> beginning<01:33:56.719> um<01:33:56.880> so<01:33:57.080> I 01:33:57.310 --> 01:33:57.320 align:start position:0% invariance from the beginning um so I 01:33:57.320 --> 01:33:58.390 align:start position:0% invariance from the beginning um so I kind<01:33:57.440> of<01:33:57.560> start<01:33:57.800> with<01:33:57.960> that<01:33:58.119> withd 01:33:58.390 --> 01:33:58.400 align:start position:0% kind of start with that withd 01:33:58.400 --> 01:34:00.030 align:start position:0% kind of start with that withd documentation<01:33:59.040> and<01:33:59.159> then<01:33:59.320> reading<01:33:59.600> the<01:33:59.760> code 01:34:00.030 --> 01:34:00.040 align:start position:0% documentation and then reading the code 01:34:00.040 --> 01:34:01.669 align:start position:0% documentation and then reading the code finding<01:34:00.320> some<01:34:00.480> more<01:34:00.639> invariance<01:34:01.239> and<01:34:01.440> kind<01:34:01.560> of 01:34:01.669 --> 01:34:01.679 align:start position:0% finding some more invariance and kind of 01:34:01.679 --> 01:34:04.629 align:start position:0% finding some more invariance and kind of iterating<01:34:02.239> throughout<01:34:02.600> that<01:34:03.119> process<01:34:04.119> um<01:34:04.520> I 01:34:04.629 --> 01:34:04.639 align:start position:0% iterating throughout that process um I 01:34:04.639 --> 01:34:06.790 align:start position:0% iterating throughout that process um I think<01:34:05.159> over<01:34:05.600> time<01:34:05.960> the<01:34:06.080> more<01:34:06.239> you<01:34:06.639> understand 01:34:06.790 --> 01:34:06.800 align:start position:0% think over time the more you understand 01:34:06.800 --> 01:34:08.950 align:start position:0% think over time the more you understand about<01:34:06.960> the<01:34:07.080> code<01:34:07.360> base<01:34:07.880> the<01:34:08.000> more<01:34:08.400> invariance 01:34:08.950 --> 01:34:08.960 align:start position:0% about the code base the more invariance 01:34:08.960 --> 01:34:11.870 align:start position:0% about the code base the more invariance you<01:34:09.040> can<01:34:09.280> find<01:34:09.760> and<01:34:10.080> very<01:34:10.400> likely<01:34:11.400> um<01:34:11.600> the<01:34:11.719> more 01:34:11.870 --> 01:34:11.880 align:start position:0% you can find and very likely um the more 01:34:11.880 --> 01:34:16.790 align:start position:0% you can find and very likely um the more invariance<01:34:12.360> you<01:34:12.480> can 01:34:16.790 --> 01:34:16.800 align:start position:0% 01:34:16.800 --> 01:34:20.040 align:start position:0% break<01:34:17.800> thank<01:34:17.960> you 01:34:20.040 --> 01:34:20.050 align:start position:0% break thank you 01:34:20.050 --> 01:34:23.169 align:start position:0% break thank you [Applause]