WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:10.749 align:start position:0% [Music] 00:00:10.749 --> 00:00:10.759 align:start position:0% [Music] 00:00:10.759 --> 00:00:12.910 align:start position:0% [Music] hey<00:00:10.960> everybody<00:00:11.559> great<00:00:11.759> to<00:00:12.040> see<00:00:12.240> you<00:00:12.360> all<00:00:12.639> here 00:00:12.910 --> 00:00:12.920 align:start position:0% hey everybody great to see you all here 00:00:12.920 --> 00:00:15.150 align:start position:0% hey everybody great to see you all here thanks<00:00:13.080> for<00:00:13.240> coming<00:00:13.480> out<00:00:14.200> I'm<00:00:14.360> Jack<00:00:14.599> Sanford 00:00:15.150 --> 00:00:15.160 align:start position:0% thanks for coming out I'm Jack Sanford 00:00:15.160 --> 00:00:17.870 align:start position:0% thanks for coming out I'm Jack Sanford I'm<00:00:15.280> the<00:00:15.440> CEO<00:00:16.160> and<00:00:16.440> co-founder<00:00:17.000> of<00:00:17.160> Sherlock 00:00:17.870 --> 00:00:17.880 align:start position:0% I'm the CEO and co-founder of Sherlock 00:00:17.880 --> 00:00:20.070 align:start position:0% I'm the CEO and co-founder of Sherlock Sherlock<00:00:18.359> is<00:00:18.480> one<00:00:18.640> of<00:00:18.800> the<00:00:19.359> largest<00:00:19.760> audit 00:00:20.070 --> 00:00:20.080 align:start position:0% Sherlock is one of the largest audit 00:00:20.080 --> 00:00:22.310 align:start position:0% Sherlock is one of the largest audit contest<00:00:20.519> providers<00:00:20.880> in<00:00:21.039> the<00:00:21.199> space<00:00:22.000> and<00:00:22.119> today 00:00:22.310 --> 00:00:22.320 align:start position:0% contest providers in the space and today 00:00:22.320 --> 00:00:24.070 align:start position:0% contest providers in the space and today we're<00:00:22.439> going<00:00:22.560> to<00:00:22.680> talk<00:00:22.880> a<00:00:22.960> little<00:00:23.119> bit<00:00:23.320> about 00:00:24.070 --> 00:00:24.080 align:start position:0% we're going to talk a little bit about 00:00:24.080 --> 00:00:25.950 align:start position:0% we're going to talk a little bit about the<00:00:24.240> most<00:00:24.519> common<00:00:24.880> bugs<00:00:25.199> found<00:00:25.439> in<00:00:25.599> audit 00:00:25.950 --> 00:00:25.960 align:start position:0% the most common bugs found in audit 00:00:25.960 --> 00:00:27.870 align:start position:0% the most common bugs found in audit contests<00:00:26.679> so<00:00:27.039> if<00:00:27.119> you're<00:00:27.279> a<00:00:27.439> protocol 00:00:27.870 --> 00:00:27.880 align:start position:0% contests so if you're a protocol 00:00:27.880 --> 00:00:29.589 align:start position:0% contests so if you're a protocol developer<00:00:28.439> or<00:00:28.560> if<00:00:28.679> you<00:00:28.880> want<00:00:29.080> to<00:00:29.279> become<00:00:29.480> a 00:00:29.589 --> 00:00:29.599 align:start position:0% developer or if you want to become a 00:00:29.599 --> 00:00:31.910 align:start position:0% developer or if you want to become a protocol<00:00:30.199> developer<00:00:30.560> one<00:00:30.759> day<00:00:31.519> you<00:00:31.679> are<00:00:31.800> going 00:00:31.910 --> 00:00:31.920 align:start position:0% protocol developer one day you are going 00:00:31.920 --> 00:00:34.950 align:start position:0% protocol developer one day you are going to<00:00:32.040> be<00:00:32.239> ahead<00:00:32.559> of<00:00:33.200> 90%<00:00:34.160> of<00:00:34.320> other<00:00:34.520> protocol 00:00:34.950 --> 00:00:34.960 align:start position:0% to be ahead of 90% of other protocol 00:00:34.960 --> 00:00:37.110 align:start position:0% to be ahead of 90% of other protocol developers<00:00:35.640> just<00:00:35.800> by<00:00:35.960> being<00:00:36.239> aware<00:00:36.719> of<00:00:36.920> these 00:00:37.110 --> 00:00:37.120 align:start position:0% developers just by being aware of these 00:00:37.120 --> 00:00:40.190 align:start position:0% developers just by being aware of these 10<00:00:37.480> common 00:00:40.190 --> 00:00:40.200 align:start position:0% 00:00:40.200 --> 00:00:43.150 align:start position:0% bugs<00:00:41.200> so<00:00:41.480> just<00:00:41.600> a<00:00:41.800> quick<00:00:42.000> intro<00:00:42.640> on<00:00:42.800> audit 00:00:43.150 --> 00:00:43.160 align:start position:0% bugs so just a quick intro on audit 00:00:43.160 --> 00:00:45.670 align:start position:0% bugs so just a quick intro on audit contest<00:00:43.559> and<00:00:43.680> why<00:00:43.800> you<00:00:43.879> should<00:00:44.160> care<00:00:45.120> um<00:00:45.320> audit 00:00:45.670 --> 00:00:45.680 align:start position:0% contest and why you should care um audit 00:00:45.680 --> 00:00:47.869 align:start position:0% contest and why you should care um audit contests<00:00:46.440> have<00:00:46.680> become<00:00:47.039> and<00:00:47.199> are<00:00:47.440> becoming 00:00:47.869 --> 00:00:47.879 align:start position:0% contests have become and are becoming 00:00:47.879 --> 00:00:50.470 align:start position:0% contests have become and are becoming one<00:00:48.000> of<00:00:48.120> the<00:00:48.239> most<00:00:48.520> popular<00:00:48.960> ways<00:00:49.239> to<00:00:49.559> secure 00:00:50.470 --> 00:00:50.480 align:start position:0% one of the most popular ways to secure 00:00:50.480 --> 00:00:52.670 align:start position:0% one of the most popular ways to secure smart<00:00:50.879> contract<00:00:51.399> code<00:00:51.800> before<00:00:52.160> deploying<00:00:52.559> a 00:00:52.670 --> 00:00:52.680 align:start position:0% smart contract code before deploying a 00:00:52.680 --> 00:00:55.869 align:start position:0% smart contract code before deploying a protocol<00:00:53.079> to<00:00:53.280> mainnet<00:00:54.280> uh<00:00:54.359> there's<00:00:54.559> been<00:00:54.879> 625 00:00:55.869 --> 00:00:55.879 align:start position:0% protocol to mainnet uh there's been 625 00:00:55.879 --> 00:00:58.549 align:start position:0% protocol to mainnet uh there's been 625 audit<00:00:56.239> contests<00:00:56.719> run<00:00:57.719> uh<00:00:57.920> the<00:00:58.079> most<00:00:58.359> have 00:00:58.549 --> 00:00:58.559 align:start position:0% audit contests run uh the most have 00:00:58.559 --> 00:01:00.270 align:start position:0% audit contests run uh the most have happened<00:00:58.960> this<00:00:59.120> year<00:00:59.320> of<00:00:59.440> any<00:00:59.640> years<00:01:00.000> so<00:01:00.120> it's 00:01:00.270 --> 00:01:00.280 align:start position:0% happened this year of any years so it's 00:01:00.280 --> 00:01:02.910 align:start position:0% happened this year of any years so it's really<00:01:00.519> taking<00:01:00.879> off<00:01:01.440> 36,000<00:01:02.239> vulnerabilities 00:01:02.910 --> 00:01:02.920 align:start position:0% really taking off 36,000 vulnerabilities 00:01:02.920 --> 00:01:05.590 align:start position:0% really taking off 36,000 vulnerabilities found<00:01:03.640> 36<00:01:04.239> million<00:01:04.600> in<00:01:04.839> prizes<00:01:05.239> have<00:01:05.400> been 00:01:05.590 --> 00:01:05.600 align:start position:0% found 36 million in prizes have been 00:01:05.600 --> 00:01:08.910 align:start position:0% found 36 million in prizes have been paid<00:01:05.840> out<00:01:06.159> to<00:01:07.119> thousands<00:01:07.680> tens<00:01:08.040> of<00:01:08.240> thousands 00:01:08.910 --> 00:01:08.920 align:start position:0% paid out to thousands tens of thousands 00:01:08.920 --> 00:01:10.670 align:start position:0% paid out to thousands tens of thousands of<00:01:09.240> Security<00:01:09.720> Experts<00:01:10.280> people<00:01:10.479> who<00:01:10.560> are 00:01:10.670 --> 00:01:10.680 align:start position:0% of Security Experts people who are 00:01:10.680 --> 00:01:12.910 align:start position:0% of Security Experts people who are learning<00:01:10.960> to<00:01:11.080> be<00:01:11.280> Security<00:01:11.720> Experts<00:01:12.479> all<00:01:12.680> from 00:01:12.910 --> 00:01:12.920 align:start position:0% learning to be Security Experts all from 00:01:12.920 --> 00:01:15.070 align:start position:0% learning to be Security Experts all from finding<00:01:13.320> bugs<00:01:13.680> in<00:01:13.840> these<00:01:14.000> audit<00:01:14.360> contests<00:01:14.880> and 00:01:15.070 --> 00:01:15.080 align:start position:0% finding bugs in these audit contests and 00:01:15.080 --> 00:01:17.230 align:start position:0% finding bugs in these audit contests and as<00:01:15.159> you<00:01:15.280> can<00:01:15.439> see<00:01:16.159> the<00:01:16.320> biggest<00:01:16.640> teams<00:01:16.920> in<00:01:17.040> the 00:01:17.230 --> 00:01:17.240 align:start position:0% as you can see the biggest teams in the 00:01:17.240 --> 00:01:19.350 align:start position:0% as you can see the biggest teams in the space<00:01:17.799> are<00:01:17.960> using<00:01:18.280> audit<00:01:18.640> contests<00:01:19.119> all<00:01:19.240> of 00:01:19.350 --> 00:01:19.360 align:start position:0% space are using audit contests all of 00:01:19.360 --> 00:01:20.950 align:start position:0% space are using audit contests all of these<00:01:19.560> teams<00:01:19.840> have<00:01:19.960> done<00:01:20.119> an<00:01:20.240> audit<00:01:20.520> contest 00:01:20.950 --> 00:01:20.960 align:start position:0% these teams have done an audit contest 00:01:20.960 --> 00:01:24.069 align:start position:0% these teams have done an audit contest this<00:01:21.119> year<00:01:21.840> in<00:01:21.960> order<00:01:22.159> to<00:01:22.360> secure<00:01:22.680> their 00:01:24.069 --> 00:01:24.079 align:start position:0% this year in order to secure their 00:01:24.079 --> 00:01:26.670 align:start position:0% this year in order to secure their code<00:01:25.079> so<00:01:25.360> what<00:01:25.479> is<00:01:25.600> an<00:01:25.720> audit<00:01:26.000> contest 00:01:26.670 --> 00:01:26.680 align:start position:0% code so what is an audit contest 00:01:26.680 --> 00:01:28.310 align:start position:0% code so what is an audit contest essentially<00:01:27.040> the<00:01:27.200> goal<00:01:27.400> is<00:01:27.520> to<00:01:27.680> find<00:01:27.920> bugs<00:01:28.159> and 00:01:28.310 --> 00:01:28.320 align:start position:0% essentially the goal is to find bugs and 00:01:28.320 --> 00:01:30.270 align:start position:0% essentially the goal is to find bugs and code<00:01:28.720> usually<00:01:29.079> critical<00:01:29.439> bugs<00:01:29.920> bugs<00:01:30.119> that<00:01:30.200> are 00:01:30.270 --> 00:01:30.280 align:start position:0% code usually critical bugs bugs that are 00:01:30.280 --> 00:01:32.310 align:start position:0% code usually critical bugs bugs that are going<00:01:30.360> to<00:01:30.439> cause<00:01:30.680> losses<00:01:31.000> for<00:01:31.200> users<00:01:31.759> on 00:01:32.310 --> 00:01:32.320 align:start position:0% going to cause losses for users on 00:01:32.320 --> 00:01:34.429 align:start position:0% going to cause losses for users on mainnet<00:01:33.320> you<00:01:33.439> start<00:01:33.640> with<00:01:33.759> a<00:01:33.880> pot<00:01:34.040> of<00:01:34.159> money 00:01:34.429 --> 00:01:34.439 align:start position:0% mainnet you start with a pot of money 00:01:34.439 --> 00:01:36.950 align:start position:0% mainnet you start with a pot of money you<00:01:34.560> say<00:01:34.880> hey<00:01:35.200> here's<00:01:35.560> 100K<00:01:36.040> or<00:01:36.159> in<00:01:36.280> some<00:01:36.520> cases 00:01:36.950 --> 00:01:36.960 align:start position:0% you say hey here's 100K or in some cases 00:01:36.960 --> 00:01:38.990 align:start position:0% you say hey here's 100K or in some cases here's<00:01:37.119> a<00:01:37.280> million<00:01:37.600> dollars<00:01:38.560> and<00:01:38.720> we're<00:01:38.880> going 00:01:38.990 --> 00:01:39.000 align:start position:0% here's a million dollars and we're going 00:01:39.000 --> 00:01:41.149 align:start position:0% here's a million dollars and we're going to<00:01:39.200> pay<00:01:39.640> people<00:01:40.079> based<00:01:40.360> on<00:01:40.560> the<00:01:40.680> bugs<00:01:41.000> that 00:01:41.149 --> 00:01:41.159 align:start position:0% to pay people based on the bugs that 00:01:41.159 --> 00:01:43.270 align:start position:0% to pay people based on the bugs that they<00:01:41.320> find<00:01:41.799> and<00:01:42.000> anybody<00:01:42.439> can<00:01:42.640> participate<00:01:43.159> so 00:01:43.270 --> 00:01:43.280 align:start position:0% they find and anybody can participate so 00:01:43.280 --> 00:01:44.789 align:start position:0% they find and anybody can participate so it's<00:01:43.360> a<00:01:43.560> really<00:01:43.759> great<00:01:43.960> way<00:01:44.079> to<00:01:44.200> onboard<00:01:44.640> to 00:01:44.789 --> 00:01:44.799 align:start position:0% it's a really great way to onboard to 00:01:44.799 --> 00:01:46.670 align:start position:0% it's a really great way to onboard to crypto<00:01:45.320> really<00:01:45.560> great<00:01:45.799> way<00:01:46.000> to<00:01:46.119> onboard<00:01:46.520> to 00:01:46.670 --> 00:01:46.680 align:start position:0% crypto really great way to onboard to 00:01:46.680 --> 00:01:49.030 align:start position:0% crypto really great way to onboard to web<00:01:46.840> 3<00:01:47.119> security<00:01:47.960> participating<00:01:48.520> in<00:01:48.640> audit 00:01:49.030 --> 00:01:49.040 align:start position:0% web 3 security participating in audit 00:01:49.040 --> 00:01:52.109 align:start position:0% web 3 security participating in audit contests<00:01:50.040> and<00:01:50.840> depending<00:01:51.240> on<00:01:51.560> the<00:01:51.680> severity 00:01:52.109 --> 00:01:52.119 align:start position:0% contests and depending on the severity 00:01:52.119 --> 00:01:53.389 align:start position:0% contests and depending on the severity of<00:01:52.200> the<00:01:52.280> bugs<00:01:52.560> you<00:01:52.680> find<00:01:52.920> so<00:01:53.119> if<00:01:53.240> they're 00:01:53.389 --> 00:01:53.399 align:start position:0% of the bugs you find so if they're 00:01:53.399 --> 00:01:54.670 align:start position:0% of the bugs you find so if they're critical<00:01:53.759> severity<00:01:54.200> you're<00:01:54.320> going<00:01:54.399> to<00:01:54.520> get 00:01:54.670 --> 00:01:54.680 align:start position:0% critical severity you're going to get 00:01:54.680 --> 00:01:56.310 align:start position:0% critical severity you're going to get paid<00:01:54.880> more<00:01:55.040> for<00:01:55.280> them<00:01:55.680> if<00:01:55.799> they're<00:01:56.000> super 00:01:56.310 --> 00:01:56.320 align:start position:0% paid more for them if they're super 00:01:56.320 --> 00:01:58.190 align:start position:0% paid more for them if they're super unique<00:01:56.719> and<00:01:56.920> other<00:01:57.079> people<00:01:57.280> don't<00:01:57.520> find<00:01:57.799> them 00:01:58.190 --> 00:01:58.200 align:start position:0% unique and other people don't find them 00:01:58.200 --> 00:02:00.109 align:start position:0% unique and other people don't find them you're<00:01:58.360> going<00:01:58.439> to<00:01:58.560> get<00:01:58.719> paid<00:01:58.920> more<00:01:59.119> for<00:01:59.360> that 00:02:00.109 --> 00:02:00.119 align:start position:0% you're going to get paid more for that 00:02:00.119 --> 00:02:02.310 align:start position:0% you're going to get paid more for that and<00:02:00.600> if<00:02:00.719> you<00:02:00.880> find<00:02:01.360> you<00:02:01.479> know<00:02:01.759> three<00:02:02.079> of<00:02:02.200> the 00:02:02.310 --> 00:02:02.320 align:start position:0% and if you find you know three of the 00:02:02.320 --> 00:02:04.149 align:start position:0% and if you find you know three of the four<00:02:02.600> bugs<00:02:03.000> that<00:02:03.119> are<00:02:03.240> in<00:02:03.399> that<00:02:03.600> protocol 00:02:04.149 --> 00:02:04.159 align:start position:0% four bugs that are in that protocol 00:02:04.159 --> 00:02:05.830 align:start position:0% four bugs that are in that protocol during<00:02:04.439> that<00:02:04.560> audit<00:02:04.880> contest<00:02:05.600> you're<00:02:05.719> going 00:02:05.830 --> 00:02:05.840 align:start position:0% during that audit contest you're going 00:02:05.840 --> 00:02:07.990 align:start position:0% during that audit contest you're going to<00:02:05.920> get<00:02:06.039> paid<00:02:06.200> a<00:02:06.280> lot<00:02:06.399> of<00:02:06.479> money<00:02:06.680> for<00:02:06.880> that<00:02:07.520> so 00:02:07.990 --> 00:02:08.000 align:start position:0% to get paid a lot of money for that so 00:02:08.000 --> 00:02:09.469 align:start position:0% to get paid a lot of money for that so really<00:02:08.200> cool<00:02:08.440> thing<00:02:08.720> and<00:02:08.800> we're<00:02:08.920> going<00:02:09.039> to<00:02:09.160> rip 00:02:09.469 --> 00:02:09.479 align:start position:0% really cool thing and we're going to rip 00:02:09.479 --> 00:02:11.670 align:start position:0% really cool thing and we're going to rip through<00:02:10.000> super<00:02:10.319> quickly<00:02:11.039> the<00:02:11.239> top<00:02:11.440> 10 00:02:11.670 --> 00:02:11.680 align:start position:0% through super quickly the top 10 00:02:11.680 --> 00:02:13.190 align:start position:0% through super quickly the top 10 vulnerabilities<00:02:12.319> that<00:02:12.440> are<00:02:12.560> found<00:02:12.760> in<00:02:12.879> audit 00:02:13.190 --> 00:02:13.200 align:start position:0% vulnerabilities that are found in audit 00:02:13.200 --> 00:02:15.309 align:start position:0% vulnerabilities that are found in audit contest<00:02:13.640> these 00:02:15.309 --> 00:02:15.319 align:start position:0% contest these 00:02:15.319 --> 00:02:18.550 align:start position:0% contest these days<00:02:16.319> so<00:02:16.840> number<00:02:17.160> one<00:02:17.599> first<00:02:17.959> depositor 00:02:18.550 --> 00:02:18.560 align:start position:0% days so number one first depositor 00:02:18.560 --> 00:02:22.030 align:start position:0% days so number one first depositor inflation<00:02:19.080> attack<00:02:19.440> in<00:02:19.599> ERC<00:02:20.120> 4626<00:02:21.080> volts<00:02:21.959> this 00:02:22.030 --> 00:02:22.040 align:start position:0% inflation attack in ERC 4626 volts this 00:02:22.040 --> 00:02:24.350 align:start position:0% inflation attack in ERC 4626 volts this is<00:02:22.160> a<00:02:22.319> super<00:02:22.599> famous<00:02:23.000> attack<00:02:23.560> really<00:02:23.920> annoying 00:02:24.350 --> 00:02:24.360 align:start position:0% is a super famous attack really annoying 00:02:24.360 --> 00:02:26.790 align:start position:0% is a super famous attack really annoying because<00:02:24.680> anytime<00:02:25.080> you<00:02:25.239> deploy<00:02:25.560> a<00:02:25.680> new<00:02:25.879> Vault 00:02:26.790 --> 00:02:26.800 align:start position:0% because anytime you deploy a new Vault 00:02:26.800 --> 00:02:29.910 align:start position:0% because anytime you deploy a new Vault um<00:02:27.239> on<00:02:27.360> a<00:02:27.560> blockchain<00:02:28.319> you're<00:02:28.599> essentially<00:02:29.480> uh 00:02:29.910 --> 00:02:29.920 align:start position:0% um on a blockchain you're essentially uh 00:02:29.920 --> 00:02:32.670 align:start position:0% um on a blockchain you're essentially uh exposed<00:02:30.280> to<00:02:30.440> this<00:02:30.640> attack<00:02:31.560> um<00:02:31.920> because<00:02:32.480> the 00:02:32.670 --> 00:02:32.680 align:start position:0% exposed to this attack um because the 00:02:32.680 --> 00:02:36.270 align:start position:0% exposed to this attack um because the person<00:02:33.080> who<00:02:33.280> puts<00:02:33.560> in<00:02:34.120> the<00:02:35.120> first<00:02:35.519> deposit<00:02:36.080> can 00:02:36.270 --> 00:02:36.280 align:start position:0% person who puts in the first deposit can 00:02:36.280 --> 00:02:37.869 align:start position:0% person who puts in the first deposit can essentially<00:02:36.640> put<00:02:36.760> in<00:02:36.920> such<00:02:37.040> a<00:02:37.160> tiny<00:02:37.440> deposit 00:02:37.869 --> 00:02:37.879 align:start position:0% essentially put in such a tiny deposit 00:02:37.879 --> 00:02:39.869 align:start position:0% essentially put in such a tiny deposit that<00:02:37.959> it<00:02:38.080> causes<00:02:38.440> sort<00:02:38.560> of<00:02:38.640> a<00:02:38.760> rounding<00:02:39.159> issue 00:02:39.869 --> 00:02:39.879 align:start position:0% that it causes sort of a rounding issue 00:02:39.879 --> 00:02:42.030 align:start position:0% that it causes sort of a rounding issue and<00:02:40.040> then<00:02:40.280> all<00:02:40.440> the<00:02:40.599> deposits<00:02:41.120> after<00:02:41.400> that<00:02:41.760> are 00:02:42.030 --> 00:02:42.040 align:start position:0% and then all the deposits after that are 00:02:42.040 --> 00:02:43.710 align:start position:0% and then all the deposits after that are a<00:02:42.120> little<00:02:42.280> bit<00:02:42.480> messed<00:02:42.800> up<00:02:43.159> and<00:02:43.319> the<00:02:43.400> first 00:02:43.710 --> 00:02:43.720 align:start position:0% a little bit messed up and the first 00:02:43.720 --> 00:02:46.390 align:start position:0% a little bit messed up and the first depositor<00:02:44.319> can<00:02:44.840> steal<00:02:45.239> funds<00:02:45.680> that<00:02:45.879> way<00:02:46.200> and 00:02:46.390 --> 00:02:46.400 align:start position:0% depositor can steal funds that way and 00:02:46.400 --> 00:02:49.630 align:start position:0% depositor can steal funds that way and kind<00:02:46.519> of<00:02:46.680> Dos<00:02:47.360> the<00:02:47.640> The 00:02:49.630 --> 00:02:49.640 align:start position:0% kind of Dos the The 00:02:49.640 --> 00:02:53.229 align:start position:0% kind of Dos the The Vault<00:02:50.640> second<00:02:50.959> one<00:02:51.640> using<00:02:52.400> transfer<00:02:53.000> instead 00:02:53.229 --> 00:02:53.239 align:start position:0% Vault second one using transfer instead 00:02:53.239 --> 00:02:55.910 align:start position:0% Vault second one using transfer instead of<00:02:53.400> safe<00:02:53.680> transfer<00:02:54.599> so<00:02:55.239> just<00:02:55.440> using<00:02:55.760> the 00:02:55.910 --> 00:02:55.920 align:start position:0% of safe transfer so just using the 00:02:55.920 --> 00:02:58.470 align:start position:0% of safe transfer so just using the transfer<00:02:56.400> function<00:02:56.760> in<00:02:57.000> solidity<00:02:58.000> doesn't 00:02:58.470 --> 00:02:58.480 align:start position:0% transfer function in solidity doesn't 00:02:58.480 --> 00:03:00.869 align:start position:0% transfer function in solidity doesn't actually<00:02:58.800> check<00:02:59.280> the<00:02:59.440> success<00:03:00.040> or<00:03:00.159> failure<00:03:00.760> of 00:03:00.869 --> 00:03:00.879 align:start position:0% actually check the success or failure of 00:03:00.879 --> 00:03:03.229 align:start position:0% actually check the success or failure of a<00:03:01.040> transfer<00:03:01.920> and<00:03:02.040> it<00:03:02.159> can<00:03:02.360> also<00:03:02.640> allow<00:03:02.959> for 00:03:03.229 --> 00:03:03.239 align:start position:0% a transfer and it can also allow for 00:03:03.239 --> 00:03:05.149 align:start position:0% a transfer and it can also allow for really<00:03:03.519> bad<00:03:03.720> things<00:03:03.959> like<00:03:04.120> re-entrancy<00:03:04.640> with 00:03:05.149 --> 00:03:05.159 align:start position:0% really bad things like re-entrancy with 00:03:05.159 --> 00:03:09.190 align:start position:0% really bad things like re-entrancy with non-standard<00:03:05.879> tokens<00:03:06.400> such<00:03:06.640> as 00:03:09.190 --> 00:03:09.200 align:start position:0% non-standard tokens such as 00:03:09.200 --> 00:03:12.470 align:start position:0% non-standard tokens such as usdt<00:03:10.200> number<00:03:10.519> three<00:03:11.239> missing<00:03:11.680> validation<00:03:12.280> and 00:03:12.470 --> 00:03:12.480 align:start position:0% usdt number three missing validation and 00:03:12.480 --> 00:03:15.470 align:start position:0% usdt number three missing validation and admin<00:03:12.840> checks<00:03:13.480> so<00:03:13.799> let's<00:03:14.080> say<00:03:14.480> you<00:03:14.680> only<00:03:15.080> want 00:03:15.470 --> 00:03:15.480 align:start position:0% admin checks so let's say you only want 00:03:15.480 --> 00:03:17.309 align:start position:0% admin checks so let's say you only want the<00:03:15.840> owner<00:03:16.120> of<00:03:16.239> a<00:03:16.400> contract<00:03:16.840> to<00:03:17.000> call<00:03:17.200> a 00:03:17.309 --> 00:03:17.319 align:start position:0% the owner of a contract to call a 00:03:17.319 --> 00:03:19.229 align:start position:0% the owner of a contract to call a function<00:03:17.959> or<00:03:18.159> someone<00:03:18.440> on<00:03:18.560> a<00:03:18.680> white<00:03:18.920> list<00:03:19.120> to 00:03:19.229 --> 00:03:19.239 align:start position:0% function or someone on a white list to 00:03:19.239 --> 00:03:21.630 align:start position:0% function or someone on a white list to call<00:03:19.440> a<00:03:19.560> function<00:03:20.440> a<00:03:20.560> lot<00:03:20.680> of<00:03:20.920> times<00:03:21.440> there's 00:03:21.630 --> 00:03:21.640 align:start position:0% call a function a lot of times there's 00:03:21.640 --> 00:03:23.309 align:start position:0% call a function a lot of times there's so<00:03:21.799> many<00:03:22.000> functions<00:03:22.400> you<00:03:22.560> just<00:03:22.720> forget<00:03:23.200> you 00:03:23.309 --> 00:03:23.319 align:start position:0% so many functions you just forget you 00:03:23.319 --> 00:03:24.869 align:start position:0% so many functions you just forget you just<00:03:23.440> forget<00:03:23.799> one<00:03:24.200> essentially<00:03:24.640> or<00:03:24.760> you 00:03:24.869 --> 00:03:24.879 align:start position:0% just forget one essentially or you 00:03:24.879 --> 00:03:26.149 align:start position:0% just forget one essentially or you forget<00:03:25.159> to<00:03:25.280> check<00:03:25.480> for<00:03:25.680> something<00:03:25.959> that<00:03:26.040> you 00:03:26.149 --> 00:03:26.159 align:start position:0% forget to check for something that you 00:03:26.159 --> 00:03:27.949 align:start position:0% forget to check for something that you meant<00:03:26.360> to<00:03:26.480> check<00:03:26.720> for<00:03:27.480> and<00:03:27.640> that's<00:03:27.799> what 00:03:27.949 --> 00:03:27.959 align:start position:0% meant to check for and that's what 00:03:27.959 --> 00:03:29.470 align:start position:0% meant to check for and that's what Auditors<00:03:28.319> are<00:03:28.519> here<00:03:28.680> for<00:03:28.959> and<00:03:29.080> they're<00:03:29.319> really 00:03:29.470 --> 00:03:29.480 align:start position:0% Auditors are here for and they're really 00:03:29.480 --> 00:03:31.670 align:start position:0% Auditors are here for and they're really good<00:03:29.640> at<00:03:29.799> finding<00:03:30.120> that<00:03:30.319> stuff<00:03:31.159> um<00:03:31.280> so<00:03:31.519> this 00:03:31.670 --> 00:03:31.680 align:start position:0% good at finding that stuff um so this 00:03:31.680 --> 00:03:33.830 align:start position:0% good at finding that stuff um so this happens<00:03:32.000> more<00:03:32.159> often<00:03:32.400> than<00:03:32.519> youd 00:03:33.830 --> 00:03:33.840 align:start position:0% happens more often than youd 00:03:33.840 --> 00:03:36.429 align:start position:0% happens more often than youd think<00:03:34.840> okay<00:03:35.040> missing<00:03:35.360> check<00:03:35.599> for<00:03:35.799> active<00:03:36.080> L2 00:03:36.429 --> 00:03:36.439 align:start position:0% think okay missing check for active L2 00:03:36.439 --> 00:03:38.509 align:start position:0% think okay missing check for active L2 sequencer<00:03:37.239> so<00:03:37.400> essentially<00:03:37.959> if<00:03:38.080> you<00:03:38.239> are 00:03:38.509 --> 00:03:38.519 align:start position:0% sequencer so essentially if you are 00:03:38.519 --> 00:03:40.630 align:start position:0% sequencer so essentially if you are deploying<00:03:38.920> a<00:03:39.040> protocol<00:03:39.519> on<00:03:39.680> top<00:03:39.840> of<00:03:39.959> an<00:03:40.040> L2 00:03:40.630 --> 00:03:40.640 align:start position:0% deploying a protocol on top of an L2 00:03:40.640 --> 00:03:44.309 align:start position:0% deploying a protocol on top of an L2 like<00:03:41.080> arbitrum<00:03:41.799> or<00:03:42.239> optimism<00:03:43.239> um<00:03:43.840> sometimes 00:03:44.309 --> 00:03:44.319 align:start position:0% like arbitrum or optimism um sometimes 00:03:44.319 --> 00:03:46.509 align:start position:0% like arbitrum or optimism um sometimes the<00:03:44.439> sequencer<00:03:44.959> goes<00:03:45.200> down<00:03:45.519> not<00:03:45.760> very<00:03:46.000> often 00:03:46.509 --> 00:03:46.519 align:start position:0% the sequencer goes down not very often 00:03:46.519 --> 00:03:47.990 align:start position:0% the sequencer goes down not very often but<00:03:46.720> it<00:03:46.840> could<00:03:47.000> happen<00:03:47.239> in<00:03:47.319> the<00:03:47.439> future<00:03:47.760> and<00:03:47.879> it 00:03:47.990 --> 00:03:48.000 align:start position:0% but it could happen in the future and it 00:03:48.000 --> 00:03:50.270 align:start position:0% but it could happen in the future and it could<00:03:48.159> happen<00:03:48.400> for<00:03:48.760> long<00:03:48.959> periods<00:03:49.280> of<00:03:49.480> time 00:03:50.270 --> 00:03:50.280 align:start position:0% could happen for long periods of time 00:03:50.280 --> 00:03:52.149 align:start position:0% could happen for long periods of time and<00:03:50.519> if<00:03:50.599> you're<00:03:50.840> a<00:03:51.000> derivatives<00:03:51.560> protocol<00:03:52.000> or 00:03:52.149 --> 00:03:52.159 align:start position:0% and if you're a derivatives protocol or 00:03:52.159 --> 00:03:53.630 align:start position:0% and if you're a derivatives protocol or something<00:03:52.439> where<00:03:52.599> real-time<00:03:53.079> information<00:03:53.480> is 00:03:53.630 --> 00:03:53.640 align:start position:0% something where real-time information is 00:03:53.640 --> 00:03:55.750 align:start position:0% something where real-time information is super<00:03:53.959> important<00:03:54.799> malicious<00:03:55.280> actors<00:03:55.599> can 00:03:55.750 --> 00:03:55.760 align:start position:0% super important malicious actors can 00:03:55.760 --> 00:03:58.069 align:start position:0% super important malicious actors can take<00:03:55.959> advantage<00:03:56.640> of<00:03:56.840> stale<00:03:57.360> prices<00:03:57.879> because 00:03:58.069 --> 00:03:58.079 align:start position:0% take advantage of stale prices because 00:03:58.079 --> 00:04:01.390 align:start position:0% take advantage of stale prices because of<00:03:58.200> the<00:03:58.280> sequencer<00:03:58.879> being<00:03:59.079> down 00:04:01.390 --> 00:04:01.400 align:start position:0% of the sequencer being down 00:04:01.400 --> 00:04:04.069 align:start position:0% of the sequencer being down number<00:04:01.720> five<00:04:02.120> the<00:04:02.280> classic<00:04:02.840> re-entrancy<00:04:03.360> very 00:04:04.069 --> 00:04:04.079 align:start position:0% number five the classic re-entrancy very 00:04:04.079 --> 00:04:06.429 align:start position:0% number five the classic re-entrancy very first<00:04:04.640> major<00:04:05.000> vulnerability<00:04:05.920> ever<00:04:06.239> in 00:04:06.429 --> 00:04:06.439 align:start position:0% first major vulnerability ever in 00:04:06.439 --> 00:04:09.869 align:start position:0% first major vulnerability ever in ethereum<00:04:07.000> the<00:04:07.120> Dow<00:04:07.439> hack<00:04:08.360> um<00:04:08.840> basically<00:04:09.760> there 00:04:09.869 --> 00:04:09.879 align:start position:0% ethereum the Dow hack um basically there 00:04:09.879 --> 00:04:12.670 align:start position:0% ethereum the Dow hack um basically there are<00:04:10.079> certain<00:04:10.439> functions<00:04:11.079> where<00:04:12.000> essentially 00:04:12.670 --> 00:04:12.680 align:start position:0% are certain functions where essentially 00:04:12.680 --> 00:04:14.550 align:start position:0% are certain functions where essentially you<00:04:12.840> can<00:04:13.079> continue<00:04:13.439> the<00:04:13.640> execution<00:04:14.200> outside 00:04:14.550 --> 00:04:14.560 align:start position:0% you can continue the execution outside 00:04:14.560 --> 00:04:16.270 align:start position:0% you can continue the execution outside of<00:04:14.680> the<00:04:14.799> function<00:04:15.120> and<00:04:15.280> call<00:04:15.560> that<00:04:15.799> very<00:04:16.040> same 00:04:16.270 --> 00:04:16.280 align:start position:0% of the function and call that very same 00:04:16.280 --> 00:04:18.270 align:start position:0% of the function and call that very same function<00:04:16.680> again<00:04:17.199> and<00:04:17.320> this<00:04:17.440> can<00:04:17.639> cause<00:04:18.079> all 00:04:18.270 --> 00:04:18.280 align:start position:0% function again and this can cause all 00:04:18.280 --> 00:04:19.670 align:start position:0% function again and this can cause all kinds<00:04:18.479> of<00:04:18.720> problems<00:04:19.040> there's<00:04:19.199> a<00:04:19.359> bunch<00:04:19.519> of 00:04:19.670 --> 00:04:19.680 align:start position:0% kinds of problems there's a bunch of 00:04:19.680 --> 00:04:22.069 align:start position:0% kinds of problems there's a bunch of different<00:04:20.400> like<00:04:20.799> surface<00:04:21.239> area<00:04:21.600> for<00:04:21.840> what 00:04:22.069 --> 00:04:22.079 align:start position:0% different like surface area for what 00:04:22.079 --> 00:04:25.510 align:start position:0% different like surface area for what these<00:04:22.960> um<00:04:23.320> vulnerabilities<00:04:24.080> can<00:04:24.280> do<00:04:25.040> but<00:04:25.400> I'm 00:04:25.510 --> 00:04:25.520 align:start position:0% these um vulnerabilities can do but I'm 00:04:25.520 --> 00:04:26.710 align:start position:0% these um vulnerabilities can do but I'm sure<00:04:25.880> a<00:04:26.000> lot<00:04:26.120> of<00:04:26.199> you<00:04:26.320> have<00:04:26.440> heard<00:04:26.600> of 00:04:26.710 --> 00:04:26.720 align:start position:0% sure a lot of you have heard of 00:04:26.720 --> 00:04:28.710 align:start position:0% sure a lot of you have heard of re-entrance<00:04:27.120> C 00:04:28.710 --> 00:04:28.720 align:start position:0% re-entrance C 00:04:28.720 --> 00:04:31.629 align:start position:0% re-entrance C already<00:04:29.720> Beyond<00:04:29.960> transfer<00:04:30.400> rebasing<00:04:30.919> tokens 00:04:31.629 --> 00:04:31.639 align:start position:0% already Beyond transfer rebasing tokens 00:04:31.639 --> 00:04:33.670 align:start position:0% already Beyond transfer rebasing tokens so<00:04:32.320> if<00:04:32.400> you<00:04:32.520> want<00:04:32.680> your<00:04:32.840> protocol<00:04:33.280> to<00:04:33.400> be<00:04:33.520> able 00:04:33.670 --> 00:04:33.680 align:start position:0% so if you want your protocol to be able 00:04:33.680 --> 00:04:36.790 align:start position:0% so if you want your protocol to be able to<00:04:33.880> handle<00:04:34.360> any<00:04:34.639> token<00:04:34.960> out<00:04:35.240> there<00:04:35.960> um<00:04:36.160> or<00:04:36.600> even 00:04:36.790 --> 00:04:36.800 align:start position:0% to handle any token out there um or even 00:04:36.800 --> 00:04:39.510 align:start position:0% to handle any token out there um or even a<00:04:37.039> pretty<00:04:37.360> General<00:04:37.880> set<00:04:38.080> of<00:04:38.280> tokens<00:04:39.160> a<00:04:39.240> lot<00:04:39.400> of 00:04:39.510 --> 00:04:39.520 align:start position:0% a pretty General set of tokens a lot of 00:04:39.520 --> 00:04:41.070 align:start position:0% a pretty General set of tokens a lot of them<00:04:39.639> are<00:04:39.800> non-standard<00:04:40.520> a<00:04:40.639> lot<00:04:40.759> of<00:04:40.880> them 00:04:41.070 --> 00:04:41.080 align:start position:0% them are non-standard a lot of them 00:04:41.080 --> 00:04:44.110 align:start position:0% them are non-standard a lot of them don't<00:04:41.800> conform<00:04:42.400> to<00:04:43.080> you<00:04:43.240> know<00:04:43.759> things<00:04:44.000> that 00:04:44.110 --> 00:04:44.120 align:start position:0% don't conform to you know things that 00:04:44.120 --> 00:04:46.150 align:start position:0% don't conform to you know things that you<00:04:44.199> would<00:04:44.400> think<00:04:44.600> that<00:04:44.720> they<00:04:44.919> conform<00:04:45.360> to<00:04:46.000> and 00:04:46.150 --> 00:04:46.160 align:start position:0% you would think that they conform to and 00:04:46.160 --> 00:04:48.950 align:start position:0% you would think that they conform to and so<00:04:46.639> smart<00:04:47.000> contracts<00:04:47.600> can<00:04:47.759> get<00:04:48.039> completely 00:04:48.950 --> 00:04:48.960 align:start position:0% so smart contracts can get completely 00:04:48.960 --> 00:04:52.430 align:start position:0% so smart contracts can get completely dosed<00:04:49.880> or<00:04:50.320> or<00:04:50.919> um<00:04:51.160> funds<00:04:51.520> can<00:04:51.639> be<00:04:51.800> lost<00:04:52.199> because 00:04:52.430 --> 00:04:52.440 align:start position:0% dosed or or um funds can be lost because 00:04:52.440 --> 00:04:54.870 align:start position:0% dosed or or um funds can be lost because of<00:04:52.600> these<00:04:52.840> tokens<00:04:53.800> um<00:04:53.960> having<00:04:54.199> non-standard 00:04:54.870 --> 00:04:54.880 align:start position:0% of these tokens um having non-standard 00:04:54.880 --> 00:04:56.150 align:start position:0% of these tokens um having non-standard behavior<00:04:55.280> with<00:04:55.400> your 00:04:56.150 --> 00:04:56.160 align:start position:0% behavior with your 00:04:56.160 --> 00:04:59.230 align:start position:0% behavior with your functions<00:04:57.160> so<00:04:58.080> rounding<00:04:58.600> Precision<00:04:58.960> loss 00:04:59.230 --> 00:04:59.240 align:start position:0% functions so rounding Precision loss 00:04:59.240 --> 00:05:01.469 align:start position:0% functions so rounding Precision loss issues<00:04:59.840> this<00:04:59.960> one<00:05:00.160> has<00:05:00.360> become<00:05:00.840> really<00:05:01.120> famous 00:05:01.469 --> 00:05:01.479 align:start position:0% issues this one has become really famous 00:05:01.479 --> 00:05:03.870 align:start position:0% issues this one has become really famous in<00:05:01.639> the<00:05:01.800> last<00:05:02.039> 12<00:05:02.360> months<00:05:03.120> even<00:05:03.400> if<00:05:03.560> something 00:05:03.870 --> 00:05:03.880 align:start position:0% in the last 12 months even if something 00:05:03.880 --> 00:05:07.230 align:start position:0% in the last 12 months even if something is<00:05:04.080> off<00:05:04.479> by<00:05:04.800> a<00:05:04.960> couple<00:05:05.280> of<00:05:05.479> way<00:05:06.240> or<00:05:06.680> you<00:05:06.800> know<00:05:07.039> to 00:05:07.230 --> 00:05:07.240 align:start position:0% is off by a couple of way or you know to 00:05:07.240 --> 00:05:10.150 align:start position:0% is off by a couple of way or you know to the<00:05:07.360> 18th<00:05:08.000> 17th<00:05:08.520> decimal<00:05:09.000> place<00:05:09.600> you<00:05:09.720> can<00:05:09.880> have 00:05:10.150 --> 00:05:10.160 align:start position:0% the 18th 17th decimal place you can have 00:05:10.160 --> 00:05:12.110 align:start position:0% the 18th 17th decimal place you can have major<00:05:10.520> issues<00:05:11.080> because<00:05:11.320> of<00:05:11.479> the<00:05:11.639> way<00:05:11.919> that 00:05:12.110 --> 00:05:12.120 align:start position:0% major issues because of the way that 00:05:12.120 --> 00:05:14.390 align:start position:0% major issues because of the way that solidity<00:05:12.720> essentially<00:05:13.199> or<00:05:13.720> the<00:05:13.840> evm 00:05:14.390 --> 00:05:14.400 align:start position:0% solidity essentially or the evm 00:05:14.400 --> 00:05:16.029 align:start position:0% solidity essentially or the evm essentially<00:05:14.880> doesn't<00:05:15.240> have<00:05:15.400> floating<00:05:15.840> Point 00:05:16.029 --> 00:05:16.039 align:start position:0% essentially doesn't have floating Point 00:05:16.039 --> 00:05:18.710 align:start position:0% essentially doesn't have floating Point arithmetic<00:05:16.960> so<00:05:17.160> it<00:05:17.320> truncates<00:05:17.960> things<00:05:18.440> it<00:05:18.600> it 00:05:18.710 --> 00:05:18.720 align:start position:0% arithmetic so it truncates things it it 00:05:18.720 --> 00:05:20.390 align:start position:0% arithmetic so it truncates things it it rounds<00:05:19.120> things<00:05:19.319> a<00:05:19.440> little<00:05:19.639> bit<00:05:20.039> and<00:05:20.160> that<00:05:20.280> can 00:05:20.390 --> 00:05:20.400 align:start position:0% rounds things a little bit and that can 00:05:20.400 --> 00:05:22.830 align:start position:0% rounds things a little bit and that can cause<00:05:20.600> a<00:05:20.720> lot<00:05:20.840> of<00:05:21.080> issues<00:05:22.080> um<00:05:22.240> hit<00:05:22.400> in<00:05:22.520> the<00:05:22.680> last 00:05:22.830 --> 00:05:22.840 align:start position:0% cause a lot of issues um hit in the last 00:05:22.840 --> 00:05:24.870 align:start position:0% cause a lot of issues um hit in the last three<00:05:23.080> really<00:05:23.280> quickly<00:05:23.600> here<00:05:24.160> using<00:05:24.520> spot 00:05:24.870 --> 00:05:24.880 align:start position:0% three really quickly here using spot 00:05:24.880 --> 00:05:27.390 align:start position:0% three really quickly here using spot price<00:05:25.600> uh<00:05:25.720> instead<00:05:25.960> of<00:05:26.080> t-w<00:05:26.520> and<00:05:26.639> Unis<00:05:26.960> swap<00:05:27.199> so 00:05:27.390 --> 00:05:27.400 align:start position:0% price uh instead of t-w and Unis swap so 00:05:27.400 --> 00:05:28.749 align:start position:0% price uh instead of t-w and Unis swap so this<00:05:27.479> is<00:05:27.639> something<00:05:28.000> that<00:05:28.199> I<00:05:28.280> think<00:05:28.440> we've<00:05:28.639> all 00:05:28.749 --> 00:05:28.759 align:start position:0% this is something that I think we've all 00:05:28.759 --> 00:05:31.029 align:start position:0% this is something that I think we've all seen<00:05:29.080> price<00:05:29.319> manip<00:05:29.880> ation<00:05:30.120> attacks<00:05:30.639> where 00:05:31.029 --> 00:05:31.039 align:start position:0% seen price manip ation attacks where 00:05:31.039 --> 00:05:33.950 align:start position:0% seen price manip ation attacks where someone<00:05:32.039> um<00:05:32.639> basically<00:05:33.080> inflates<00:05:33.560> the<00:05:33.680> value 00:05:33.950 --> 00:05:33.960 align:start position:0% someone um basically inflates the value 00:05:33.960 --> 00:05:35.629 align:start position:0% someone um basically inflates the value of<00:05:34.039> a<00:05:34.160> certain<00:05:34.440> currency<00:05:34.840> in<00:05:34.919> a<00:05:35.039> Unis<00:05:35.400> swap 00:05:35.629 --> 00:05:35.639 align:start position:0% of a certain currency in a Unis swap 00:05:35.639 --> 00:05:38.430 align:start position:0% of a certain currency in a Unis swap pool<00:05:36.000> for<00:05:36.319> even<00:05:36.560> one<00:05:36.840> block<00:05:37.479> and<00:05:37.680> then<00:05:38.160> does 00:05:38.430 --> 00:05:38.440 align:start position:0% pool for even one block and then does 00:05:38.440 --> 00:05:40.309 align:start position:0% pool for even one block and then does some<00:05:38.680> attack<00:05:39.120> using<00:05:39.360> a<00:05:39.479> flash<00:05:39.800> loan<00:05:40.080> and<00:05:40.199> then 00:05:40.309 --> 00:05:40.319 align:start position:0% some attack using a flash loan and then 00:05:40.319 --> 00:05:42.510 align:start position:0% some attack using a flash loan and then it<00:05:40.440> goes<00:05:40.680> back<00:05:40.919> down<00:05:41.560> so<00:05:41.800> that<00:05:41.919> one<00:05:42.039> is<00:05:42.240> really 00:05:42.510 --> 00:05:42.520 align:start position:0% it goes back down so that one is really 00:05:42.520 --> 00:05:44.469 align:start position:0% it goes back down so that one is really common<00:05:43.319> uh<00:05:43.440> less<00:05:43.680> common<00:05:43.960> these<00:05:44.160> days 00:05:44.469 --> 00:05:44.479 align:start position:0% common uh less common these days 00:05:44.479 --> 00:05:46.710 align:start position:0% common uh less common these days thankfully<00:05:45.479> incorrect<00:05:46.000> implementation<00:05:46.560> of 00:05:46.710 --> 00:05:46.720 align:start position:0% thankfully incorrect implementation of 00:05:46.720 --> 00:05:48.950 align:start position:0% thankfully incorrect implementation of upgradeability<00:05:47.639> so<00:05:47.880> essentially<00:05:48.520> you<00:05:48.720> want 00:05:48.950 --> 00:05:48.960 align:start position:0% upgradeability so essentially you want 00:05:48.960 --> 00:05:50.590 align:start position:0% upgradeability so essentially you want you<00:05:49.080> want<00:05:49.240> your<00:05:49.440> contracts<00:05:49.880> to<00:05:50.000> be<00:05:50.120> able<00:05:50.280> to<00:05:50.400> be 00:05:50.590 --> 00:05:50.600 align:start position:0% you want your contracts to be able to be 00:05:50.600 --> 00:05:53.870 align:start position:0% you want your contracts to be able to be upgraded<00:05:51.600> and<00:05:51.800> it<00:05:51.919> turns<00:05:52.280> out<00:05:52.639> you<00:05:53.199> hardcoded 00:05:53.870 --> 00:05:53.880 align:start position:0% upgraded and it turns out you hardcoded 00:05:53.880 --> 00:05:55.550 align:start position:0% upgraded and it turns out you hardcoded something<00:05:54.240> in<00:05:54.360> an<00:05:54.720> initializer<00:05:55.440> you 00:05:55.550 --> 00:05:55.560 align:start position:0% something in an initializer you 00:05:55.560 --> 00:05:57.350 align:start position:0% something in an initializer you hardcoded<00:05:56.080> something<00:05:56.280> in<00:05:56.360> the<00:05:56.520> Constructor 00:05:57.350 --> 00:05:57.360 align:start position:0% hardcoded something in the Constructor 00:05:57.360 --> 00:05:58.909 align:start position:0% hardcoded something in the Constructor and<00:05:57.479> you<00:05:57.639> can't<00:05:57.919> actually<00:05:58.199> upgrade<00:05:58.639> your 00:05:58.909 --> 00:05:58.919 align:start position:0% and you can't actually upgrade your 00:05:58.919 --> 00:06:00.350 align:start position:0% and you can't actually upgrade your contracts<00:05:59.319> and<00:05:59.400> you<00:05:59.680> only<00:05:59.840> find<00:06:00.039> that<00:06:00.160> out 00:06:00.350 --> 00:06:00.360 align:start position:0% contracts and you only find that out 00:06:00.360 --> 00:06:02.230 align:start position:0% contracts and you only find that out later<00:06:00.919> so<00:06:01.080> that's<00:06:01.280> kind<00:06:01.400> of<00:06:01.520> annoying<00:06:01.880> but<00:06:02.039> not 00:06:02.230 --> 00:06:02.240 align:start position:0% later so that's kind of annoying but not 00:06:02.240 --> 00:06:04.430 align:start position:0% later so that's kind of annoying but not too<00:06:02.440> big<00:06:02.560> of<00:06:02.680> a<00:06:02.800> deal<00:06:03.199> unless<00:06:03.560> it's<00:06:04.039> uh<00:06:04.160> unless 00:06:04.430 --> 00:06:04.440 align:start position:0% too big of a deal unless it's uh unless 00:06:04.440 --> 00:06:06.469 align:start position:0% too big of a deal unless it's uh unless the<00:06:04.639> initial<00:06:05.319> deployment<00:06:05.759> of<00:06:05.880> your<00:06:06.039> contracts 00:06:06.469 --> 00:06:06.479 align:start position:0% the initial deployment of your contracts 00:06:06.479 --> 00:06:07.830 align:start position:0% the initial deployment of your contracts is<00:06:06.639> super 00:06:07.830 --> 00:06:07.840 align:start position:0% is super 00:06:07.840 --> 00:06:10.790 align:start position:0% is super critical<00:06:08.840> last<00:06:09.080> one<00:06:09.560> no<00:06:09.840> slippage<00:06:10.319> check<00:06:10.560> in 00:06:10.790 --> 00:06:10.800 align:start position:0% critical last one no slippage check in 00:06:10.800 --> 00:06:14.670 align:start position:0% critical last one no slippage check in custom<00:06:11.120> vaults<00:06:11.479> and<00:06:11.680> pools<00:06:12.280> so<00:06:12.560> ERC<00:06:13.240> ERC<00:06:13.759> 4626 00:06:14.670 --> 00:06:14.680 align:start position:0% custom vaults and pools so ERC ERC 4626 00:06:14.680 --> 00:06:17.870 align:start position:0% custom vaults and pools so ERC ERC 4626 is<00:06:14.919> great<00:06:15.720> use<00:06:16.280> you<00:06:16.440> know<00:06:16.880> standards<00:06:17.520> whenever 00:06:17.870 --> 00:06:17.880 align:start position:0% is great use you know standards whenever 00:06:17.880 --> 00:06:19.830 align:start position:0% is great use you know standards whenever you<00:06:18.080> can<00:06:18.680> uh<00:06:18.759> when<00:06:18.880> you're<00:06:19.039> developing<00:06:19.440> in 00:06:19.830 --> 00:06:19.840 align:start position:0% you can uh when you're developing in 00:06:19.840 --> 00:06:22.309 align:start position:0% you can uh when you're developing in solidity<00:06:20.840> um<00:06:21.240> because<00:06:21.840> if<00:06:21.919> you<00:06:22.120> have 00:06:22.309 --> 00:06:22.319 align:start position:0% solidity um because if you have 00:06:22.319 --> 00:06:25.510 align:start position:0% solidity um because if you have non-standard<00:06:23.000> pools<00:06:23.800> you<00:06:23.919> can<00:06:24.280> actually<00:06:24.880> have 00:06:25.510 --> 00:06:25.520 align:start position:0% non-standard pools you can actually have 00:06:25.520 --> 00:06:28.309 align:start position:0% non-standard pools you can actually have um<00:06:25.720> your<00:06:25.960> user<00:06:26.720> sign<00:06:27.000> up<00:06:27.240> to<00:06:27.440> get<00:06:27.720> a<00:06:27.880> trade<00:06:28.120> done 00:06:28.309 --> 00:06:28.319 align:start position:0% um your user sign up to get a trade done 00:06:28.319 --> 00:06:30.029 align:start position:0% um your user sign up to get a trade done at<00:06:28.479> one<00:06:28.759> price<00:06:29.080> and<00:06:29.199> then<00:06:29.319> at<00:06:29.400> the<00:06:29.639> very<00:06:29.840> next 00:06:30.029 --> 00:06:30.039 align:start position:0% at one price and then at the very next 00:06:30.039 --> 00:06:32.909 align:start position:0% at one price and then at the very next block<00:06:30.319> or<00:06:30.440> the<00:06:30.599> very<00:06:30.800> next<00:06:31.360> execution<00:06:32.360> um<00:06:32.720> that 00:06:32.909 --> 00:06:32.919 align:start position:0% block or the very next execution um that 00:06:32.919 --> 00:06:34.469 align:start position:0% block or the very next execution um that price<00:06:33.120> is<00:06:33.360> completely<00:06:33.840> different<00:06:34.160> and<00:06:34.280> it<00:06:34.360> can 00:06:34.469 --> 00:06:34.479 align:start position:0% price is completely different and it can 00:06:34.479 --> 00:06:36.909 align:start position:0% price is completely different and it can be<00:06:34.639> off<00:06:35.039> by<00:06:35.360> a<00:06:35.599> massive<00:06:35.960> amount<00:06:36.240> of<00:06:36.440> percentage 00:06:36.909 --> 00:06:36.919 align:start position:0% be off by a massive amount of percentage 00:06:36.919 --> 00:06:39.710 align:start position:0% be off by a massive amount of percentage points<00:06:37.680> so<00:06:37.919> your<00:06:38.080> users<00:06:38.479> can<00:06:38.680> get<00:06:38.880> really<00:06:39.400> into 00:06:39.710 --> 00:06:39.720 align:start position:0% points so your users can get really into 00:06:39.720 --> 00:06:41.110 align:start position:0% points so your users can get really into trouble<00:06:40.120> if<00:06:40.240> you<00:06:40.319> don't<00:06:40.520> have<00:06:40.680> slippage 00:06:41.110 --> 00:06:41.120 align:start position:0% trouble if you don't have slippage 00:06:41.120 --> 00:06:43.589 align:start position:0% trouble if you don't have slippage checks<00:06:41.360> on<00:06:41.479> your<00:06:41.639> functions<00:06:42.120> there<00:06:42.880> so<00:06:43.400> that's 00:06:43.589 --> 00:06:43.599 align:start position:0% checks on your functions there so that's 00:06:43.599 --> 00:06:45.629 align:start position:0% checks on your functions there so that's the<00:06:43.759> whole<00:06:44.000> talk<00:06:44.880> if<00:06:45.000> you're<00:06:45.199> looking<00:06:45.440> to 00:06:45.629 --> 00:06:45.639 align:start position:0% the whole talk if you're looking to 00:06:45.639 --> 00:06:47.870 align:start position:0% the whole talk if you're looking to become<00:06:45.840> a<00:06:46.000> protocol<00:06:46.479> developer<00:06:47.400> check<00:06:47.639> on 00:06:47.870 --> 00:06:47.880 align:start position:0% become a protocol developer check on 00:06:47.880 --> 00:06:49.790 align:start position:0% become a protocol developer check on these<00:06:48.080> 10<00:06:48.360> things<00:06:48.800> before<00:06:49.080> you<00:06:49.360> send<00:06:49.639> your 00:06:49.790 --> 00:06:49.800 align:start position:0% these 10 things before you send your 00:06:49.800 --> 00:06:51.469 align:start position:0% these 10 things before you send your protocol<00:06:50.199> to<00:06:50.360> Audits<00:06:50.840> and<00:06:50.919> you'll<00:06:51.080> be<00:06:51.280> ahead 00:06:51.469 --> 00:06:51.479 align:start position:0% protocol to Audits and you'll be ahead 00:06:51.479 --> 00:06:57.990 align:start position:0% protocol to Audits and you'll be ahead of<00:06:51.680> 90%<00:06:52.240> of<00:06:52.360> the<00:06:52.440> other<00:06:52.599> developers<00:06:53.080> out 00:06:57.990 --> 00:06:58.000 align:start position:0% 00:06:58.000 --> 00:07:00.469 align:start position:0% there<00:06:59.000> thank<00:06:59.160> you<00:06:59.319> Jack 00:07:00.469 --> 00:07:00.479 align:start position:0% there thank you Jack 00:07:00.479 --> 00:07:05.230 align:start position:0% there thank you Jack I<00:07:00.560> see<00:07:00.759> a<00:07:00.919> question<00:07:01.280> over 00:07:05.230 --> 00:07:05.240 align:start position:0% 00:07:05.240 --> 00:07:08.830 align:start position:0% there<00:07:06.360> um<00:07:07.360> when<00:07:07.720> when<00:07:07.840> would<00:07:07.960> you<00:07:08.080> do<00:07:08.240> an<00:07:08.440> audit 00:07:08.830 --> 00:07:08.840 align:start position:0% there um when when would you do an audit 00:07:08.840 --> 00:07:10.670 align:start position:0% there um when when would you do an audit contest<00:07:09.319> would<00:07:09.440> it<00:07:09.599> be<00:07:10.000> like<00:07:10.240> after<00:07:10.479> you've 00:07:10.670 --> 00:07:10.680 align:start position:0% contest would it be like after you've 00:07:10.680 --> 00:07:12.990 align:start position:0% contest would it be like after you've done<00:07:11.400> an<00:07:11.560> audit<00:07:11.960> or<00:07:12.240> before<00:07:12.520> you<00:07:12.639> do<00:07:12.840> your 00:07:12.990 --> 00:07:13.000 align:start position:0% done an audit or before you do your 00:07:13.000 --> 00:07:15.189 align:start position:0% done an audit or before you do your first<00:07:13.199> audit<00:07:13.639> like<00:07:13.879> or<00:07:14.080> instead<00:07:14.599> of<00:07:14.720> a<00:07:14.879> regular 00:07:15.189 --> 00:07:15.199 align:start position:0% first audit like or instead of a regular 00:07:15.199 --> 00:07:17.629 align:start position:0% first audit like or instead of a regular audit<00:07:15.720> what<00:07:15.960> what's<00:07:16.199> the<00:07:16.560> goal<00:07:16.879> there<00:07:17.440> yeah 00:07:17.629 --> 00:07:17.639 align:start position:0% audit what what's the goal there yeah 00:07:17.639 --> 00:07:19.110 align:start position:0% audit what what's the goal there yeah it's<00:07:17.759> a<00:07:17.919> great<00:07:18.199> question<00:07:18.599> if<00:07:18.720> you<00:07:18.800> can<00:07:18.919> do 00:07:19.110 --> 00:07:19.120 align:start position:0% it's a great question if you can do 00:07:19.120 --> 00:07:21.270 align:start position:0% it's a great question if you can do multiple<00:07:19.560> audits<00:07:20.280> I<00:07:20.360> would<00:07:20.520> normally<00:07:20.879> say<00:07:21.080> do 00:07:21.270 --> 00:07:21.280 align:start position:0% multiple audits I would normally say do 00:07:21.280 --> 00:07:23.830 align:start position:0% multiple audits I would normally say do the<00:07:21.400> audit<00:07:21.680> contest<00:07:22.160> last<00:07:22.759> because<00:07:23.199> you<00:07:23.360> get 00:07:23.830 --> 00:07:23.840 align:start position:0% the audit contest last because you get 00:07:23.840 --> 00:07:27.070 align:start position:0% the audit contest last because you get 300<00:07:24.440> people<00:07:25.080> it's<00:07:25.199> a<00:07:25.360> little<00:07:25.599> bit<00:07:26.199> um<00:07:26.680> there's 00:07:27.070 --> 00:07:27.080 align:start position:0% 300 people it's a little bit um there's 00:07:27.080 --> 00:07:29.749 align:start position:0% 300 people it's a little bit um there's there's<00:07:27.280> more<00:07:27.759> operational<00:07:28.759> um<00:07:29.039> complexity 00:07:29.749 --> 00:07:29.759 align:start position:0% there's more operational um complexity 00:07:29.759 --> 00:07:30.710 align:start position:0% there's more operational um complexity with<00:07:29.840> it<00:07:30.000> because<00:07:30.080> you<00:07:30.199> have<00:07:30.280> to<00:07:30.400> deal<00:07:30.560> with 00:07:30.710 --> 00:07:30.720 align:start position:0% with it because you have to deal with 00:07:30.720 --> 00:07:32.950 align:start position:0% with it because you have to deal with 300<00:07:31.240> people<00:07:31.879> you<00:07:31.960> know<00:07:32.160> Sherlock<00:07:32.639> and<00:07:32.759> others 00:07:32.950 --> 00:07:32.960 align:start position:0% 300 people you know Sherlock and others 00:07:32.960 --> 00:07:35.909 align:start position:0% 300 people you know Sherlock and others will<00:07:33.120> D<00:07:33.319> duplicate<00:07:33.759> the<00:07:33.879> issues<00:07:34.240> for<00:07:34.440> you<00:07:35.280> um 00:07:35.909 --> 00:07:35.919 align:start position:0% will D duplicate the issues for you um 00:07:35.919 --> 00:07:37.790 align:start position:0% will D duplicate the issues for you um so<00:07:36.360> if<00:07:36.440> you<00:07:36.560> can<00:07:36.720> do<00:07:36.879> a<00:07:37.039> traditional<00:07:37.479> audit<00:07:37.720> or 00:07:37.790 --> 00:07:37.800 align:start position:0% so if you can do a traditional audit or 00:07:37.800 --> 00:07:39.430 align:start position:0% so if you can do a traditional audit or two<00:07:38.080> before<00:07:38.400> that<00:07:38.680> that's<00:07:38.879> even<00:07:39.120> better 00:07:39.430 --> 00:07:39.440 align:start position:0% two before that that's even better 00:07:39.440 --> 00:07:40.589 align:start position:0% two before that that's even better because<00:07:39.639> you<00:07:39.759> get<00:07:39.879> to<00:07:40.080> have<00:07:40.280> kind<00:07:40.400> of 00:07:40.589 --> 00:07:40.599 align:start position:0% because you get to have kind of 00:07:40.599 --> 00:07:42.469 align:start position:0% because you get to have kind of consultation<00:07:41.280> with<00:07:41.440> somebody<00:07:42.160> and<00:07:42.280> really 00:07:42.469 --> 00:07:42.479 align:start position:0% consultation with somebody and really 00:07:42.479 --> 00:07:44.390 align:start position:0% consultation with somebody and really fix<00:07:42.759> a<00:07:42.840> lot<00:07:43.000> of<00:07:43.080> the<00:07:43.199> things<00:07:43.440> early<00:07:43.759> on<00:07:44.319> and 00:07:44.390 --> 00:07:44.400 align:start position:0% fix a lot of the things early on and 00:07:44.400 --> 00:07:45.830 align:start position:0% fix a lot of the things early on and then<00:07:44.560> when<00:07:44.680> you're<00:07:44.879> like<00:07:45.120> hey<00:07:45.479> I<00:07:45.599> think<00:07:45.720> this 00:07:45.830 --> 00:07:45.840 align:start position:0% then when you're like hey I think this 00:07:45.840 --> 00:07:47.589 align:start position:0% then when you're like hey I think this thing's<00:07:46.120> ready<00:07:46.280> to<00:07:46.400> go<00:07:46.520> to<00:07:46.639> mainnet<00:07:47.319> do<00:07:47.479> an 00:07:47.589 --> 00:07:47.599 align:start position:0% thing's ready to go to mainnet do an 00:07:47.599 --> 00:07:49.869 align:start position:0% thing's ready to go to mainnet do an audit<00:07:47.919> contest<00:07:48.440> and<00:07:48.560> you'll<00:07:48.800> find<00:07:49.560> all<00:07:49.720> the 00:07:49.869 --> 00:07:49.879 align:start position:0% audit contest and you'll find all the 00:07:49.879 --> 00:08:04.510 align:start position:0% audit contest and you'll find all the other<00:07:50.120> stuff<00:07:50.639> essentially<00:07:51.639> that's<00:07:51.759> the<00:07:51.919> goal 00:08:04.510 --> 00:08:04.520 align:start position:0% 00:08:04.520 --> 00:08:07.230 align:start position:0% hi<00:08:05.000> um<00:08:05.159> are<00:08:05.280> there<00:08:05.440> any<00:08:05.720> standard<00:08:06.560> protocols 00:08:07.230 --> 00:08:07.240 align:start position:0% hi um are there any standard protocols 00:08:07.240 --> 00:08:10.189 align:start position:0% hi um are there any standard protocols or<00:08:07.560> platforms<00:08:08.080> for<00:08:08.280> holding<00:08:08.680> these<00:08:09.199> contests 00:08:10.189 --> 00:08:10.199 align:start position:0% or platforms for holding these contests 00:08:10.199 --> 00:08:12.670 align:start position:0% or platforms for holding these contests that<00:08:10.319> you<00:08:10.440> can<00:08:10.919> recommend<00:08:11.919> yeah<00:08:12.159> so<00:08:12.440> I'm<00:08:12.560> the 00:08:12.670 --> 00:08:12.680 align:start position:0% that you can recommend yeah so I'm the 00:08:12.680 --> 00:08:14.710 align:start position:0% that you can recommend yeah so I'm the CEO<00:08:13.120> co-founder<00:08:13.520> of<00:08:13.639> Sherlock<00:08:14.159> Sherlock<00:08:14.599> is 00:08:14.710 --> 00:08:14.720 align:start position:0% CEO co-founder of Sherlock Sherlock is 00:08:14.720 --> 00:08:16.510 align:start position:0% CEO co-founder of Sherlock Sherlock is one<00:08:14.840> of<00:08:15.039> the<00:08:15.400> the<00:08:15.560> main<00:08:15.800> ones<00:08:16.080> so<00:08:16.319> I'm 00:08:16.510 --> 00:08:16.520 align:start position:0% one of the the main ones so I'm 00:08:16.520 --> 00:08:18.790 align:start position:0% one of the the main ones so I'm obviously<00:08:16.879> very<00:08:17.120> biased<00:08:17.919> um<00:08:18.240> but<00:08:18.599> there's 00:08:18.790 --> 00:08:18.800 align:start position:0% obviously very biased um but there's 00:08:18.800 --> 00:08:21.589 align:start position:0% obviously very biased um but there's Sherlock<00:08:19.479> there's<00:08:19.680> Cod<00:08:19.919> Arina<00:08:20.800> there<00:08:21.039> is 00:08:21.589 --> 00:08:21.599 align:start position:0% Sherlock there's Cod Arina there is 00:08:21.599 --> 00:08:23.670 align:start position:0% Sherlock there's Cod Arina there is immuni<00:08:22.159> does<00:08:22.360> them<00:08:22.560> as<00:08:22.680> well<00:08:22.919> now<00:08:23.360> there's<00:08:23.560> a 00:08:23.670 --> 00:08:23.680 align:start position:0% immuni does them as well now there's a 00:08:23.680 --> 00:08:26.390 align:start position:0% immuni does them as well now there's a platform<00:08:24.039> called<00:08:24.280> Cantina<00:08:24.919> Cod<00:08:25.280> Hawks<00:08:25.759> hats 00:08:26.390 --> 00:08:26.400 align:start position:0% platform called Cantina Cod Hawks hats 00:08:26.400 --> 00:08:28.550 align:start position:0% platform called Cantina Cod Hawks hats so<00:08:26.560> there's<00:08:26.720> a<00:08:26.840> few<00:08:27.080> platforms<00:08:27.560> out<00:08:27.759> there 00:08:28.550 --> 00:08:28.560 align:start position:0% so there's a few platforms out there 00:08:28.560 --> 00:08:32.870 align:start position:0% so there's a few platforms out there thank<00:08:28.759> you 00:08:32.870 --> 00:08:32.880 align:start position:0% 00:08:32.880 --> 00:08:39.750 align:start position:0% any<00:08:33.080> other<00:08:33.719> questions<00:08:34.719> oh<00:08:34.880> we<00:08:35.039> have<00:08:35.200> one 00:08:39.750 --> 00:08:39.760 align:start position:0% 00:08:39.760 --> 00:08:43.829 align:start position:0% here<00:08:40.760> thank<00:08:41.159> you<00:08:42.159> a<00:08:42.599> is<00:08:42.800> very 00:08:43.829 --> 00:08:43.839 align:start position:0% here thank you a is very 00:08:43.839 --> 00:08:48.030 align:start position:0% here thank you a is very expensive<00:08:44.839> so<00:08:45.160> what<00:08:45.279> is<00:08:46.040> uh<00:08:47.040> your<00:08:47.399> suggestion 00:08:48.030 --> 00:08:48.040 align:start position:0% expensive so what is uh your suggestion 00:08:48.040 --> 00:08:49.430 align:start position:0% expensive so what is uh your suggestion for 00:08:49.430 --> 00:08:49.440 align:start position:0% for 00:08:49.440 --> 00:08:54.070 align:start position:0% for small<00:08:50.440> uh<00:08:51.000> dab<00:08:51.600> with<00:08:51.839> the<00:08:52.040> very<00:08:52.399> tight<00:08:53.080> boxes 00:08:54.070 --> 00:08:54.080 align:start position:0% small uh dab with the very tight boxes 00:08:54.080 --> 00:08:57.030 align:start position:0% small uh dab with the very tight boxes thank<00:08:54.279> you<00:08:55.240> yeah<00:08:55.800> um<00:08:56.360> if<00:08:56.480> you're<00:08:56.760> if<00:08:56.839> you<00:08:56.959> have 00:08:57.030 --> 00:08:57.040 align:start position:0% thank you yeah um if you're if you have 00:08:57.040 --> 00:08:58.990 align:start position:0% thank you yeah um if you're if you have a<00:08:57.160> tight<00:08:57.440> budget<00:08:58.079> uh<00:08:58.240> I<00:08:58.320> would<00:08:58.480> say<00:08:58.720> just<00:08:58.839> try 00:08:58.990 --> 00:08:59.000 align:start position:0% a tight budget uh I would say just try 00:08:59.000 --> 00:09:00.630 align:start position:0% a tight budget uh I would say just try to<00:08:59.120> keep<00:08:59.240> your<00:08:59.560> contracts<00:08:59.959> as<00:09:00.120> simple<00:09:00.399> as 00:09:00.630 --> 00:09:00.640 align:start position:0% to keep your contracts as simple as 00:09:00.640 --> 00:09:02.590 align:start position:0% to keep your contracts as simple as possible<00:09:01.440> every<00:09:01.680> line<00:09:01.839> of<00:09:02.000> code<00:09:02.200> is<00:09:02.320> going<00:09:02.399> to 00:09:02.590 --> 00:09:02.600 align:start position:0% possible every line of code is going to 00:09:02.600 --> 00:09:04.389 align:start position:0% possible every line of code is going to cost<00:09:02.800> you<00:09:02.920> money<00:09:03.600> uh<00:09:03.720> when<00:09:03.839> it<00:09:03.920> comes<00:09:04.120> to<00:09:04.279> the 00:09:04.389 --> 00:09:04.399 align:start position:0% cost you money uh when it comes to the 00:09:04.399 --> 00:09:07.670 align:start position:0% cost you money uh when it comes to the auditing<00:09:04.880> phase<00:09:05.839> and<00:09:06.200> you<00:09:06.399> really<00:09:06.720> want<00:09:06.959> to 00:09:07.670 --> 00:09:07.680 align:start position:0% auditing phase and you really want to 00:09:07.680 --> 00:09:10.190 align:start position:0% auditing phase and you really want to pay<00:09:07.920> per<00:09:08.120> line<00:09:08.279> of<00:09:08.440> code<00:09:08.839> like<00:09:09.320> essentially 00:09:10.190 --> 00:09:10.200 align:start position:0% pay per line of code like essentially 00:09:10.200 --> 00:09:11.790 align:start position:0% pay per line of code like essentially you<00:09:10.320> need<00:09:10.480> to<00:09:10.640> pay<00:09:10.760> for<00:09:10.920> the<00:09:11.079> best<00:09:11.360> people 00:09:11.790 --> 00:09:11.800 align:start position:0% you need to pay for the best people 00:09:11.800 --> 00:09:13.630 align:start position:0% you need to pay for the best people because<00:09:12.320> those<00:09:12.440> are<00:09:12.600> the<00:09:12.760> people<00:09:12.959> who<00:09:13.160> know 00:09:13.630 --> 00:09:13.640 align:start position:0% because those are the people who know 00:09:13.640 --> 00:09:16.310 align:start position:0% because those are the people who know how<00:09:13.760> to<00:09:13.959> hack<00:09:14.279> contracts<00:09:15.240> and<00:09:15.800> those<00:09:15.959> people 00:09:16.310 --> 00:09:16.320 align:start position:0% how to hack contracts and those people 00:09:16.320 --> 00:09:18.269 align:start position:0% how to hack contracts and those people exist<00:09:16.680> on<00:09:16.800> the<00:09:16.920> black<00:09:17.279> hat<00:09:17.519> side<00:09:17.720> like<00:09:17.920> the<00:09:18.040> bad 00:09:18.269 --> 00:09:18.279 align:start position:0% exist on the black hat side like the bad 00:09:18.279 --> 00:09:19.670 align:start position:0% exist on the black hat side like the bad guys<00:09:18.720> so<00:09:18.839> you<00:09:18.920> need<00:09:19.079> to<00:09:19.200> make<00:09:19.320> sure<00:09:19.480> you're 00:09:19.670 --> 00:09:19.680 align:start position:0% guys so you need to make sure you're 00:09:19.680 --> 00:09:21.829 align:start position:0% guys so you need to make sure you're paying<00:09:19.880> for<00:09:20.040> the<00:09:20.200> best<00:09:20.440> good<00:09:20.680> guys<00:09:20.959> as<00:09:21.120> well<00:09:21.640> to 00:09:21.829 --> 00:09:21.839 align:start position:0% paying for the best good guys as well to 00:09:21.839 --> 00:09:22.750 align:start position:0% paying for the best good guys as well to ensure<00:09:22.160> that<00:09:22.240> you<00:09:22.360> find<00:09:22.600> those 00:09:22.750 --> 00:09:22.760 align:start position:0% ensure that you find those 00:09:22.760 --> 00:09:24.630 align:start position:0% ensure that you find those vulnerabilities<00:09:23.519> before<00:09:23.760> you<00:09:23.880> go<00:09:24.000> to<00:09:24.079> mainnet 00:09:24.630 --> 00:09:24.640 align:start position:0% vulnerabilities before you go to mainnet 00:09:24.640 --> 00:09:27.230 align:start position:0% vulnerabilities before you go to mainnet so<00:09:25.320> if<00:09:25.440> you're<00:09:25.839> kind<00:09:25.959> of<00:09:26.079> bootstrapping<00:09:27.079> just 00:09:27.230 --> 00:09:27.240 align:start position:0% so if you're kind of bootstrapping just 00:09:27.240 --> 00:09:28.990 align:start position:0% so if you're kind of bootstrapping just try<00:09:27.399> to<00:09:27.560> keep<00:09:27.760> your<00:09:27.959> code<00:09:28.399> as<00:09:28.560> small<00:09:28.839> as 00:09:28.990 --> 00:09:29.000 align:start position:0% try to keep your code as small as 00:09:29.000 --> 00:09:31.750 align:start position:0% try to keep your code as small as possible<00:09:29.519> as<00:09:29.640> simple<00:09:29.959> as<00:09:30.160> possible<00:09:31.000> use<00:09:31.480> other 00:09:31.750 --> 00:09:31.760 align:start position:0% possible as simple as possible use other 00:09:31.760 --> 00:09:33.430 align:start position:0% possible as simple as possible use other code<00:09:32.079> that's<00:09:32.320> already<00:09:32.560> been<00:09:32.720> audited<00:09:33.160> if 00:09:33.430 --> 00:09:33.440 align:start position:0% code that's already been audited if 00:09:33.440 --> 00:09:36.470 align:start position:0% code that's already been audited if possible<00:09:34.440> um<00:09:35.160> and<00:09:35.440> when<00:09:35.600> you<00:09:35.839> actually<00:09:36.120> do<00:09:36.320> do 00:09:36.470 --> 00:09:36.480 align:start position:0% possible um and when you actually do do 00:09:36.480 --> 00:09:38.350 align:start position:0% possible um and when you actually do do an<00:09:36.640> audit<00:09:37.360> don't<00:09:37.560> go<00:09:37.680> for<00:09:37.839> the<00:09:37.959> cheapest 00:09:38.350 --> 00:09:38.360 align:start position:0% an audit don't go for the cheapest 00:09:38.360 --> 00:09:39.829 align:start position:0% an audit don't go for the cheapest provider<00:09:38.839> because<00:09:39.040> you<00:09:39.200> really<00:09:39.399> want<00:09:39.560> to<00:09:39.720> get 00:09:39.829 --> 00:09:39.839 align:start position:0% provider because you really want to get 00:09:39.839 --> 00:09:41.550 align:start position:0% provider because you really want to get that<00:09:40.040> top<00:09:40.279> talent<00:09:40.720> even<00:09:40.880> if<00:09:41.000> you<00:09:41.120> have<00:09:41.200> a<00:09:41.320> small 00:09:41.550 --> 00:09:41.560 align:start position:0% that top talent even if you have a small 00:09:41.560 --> 00:09:44.800 align:start position:0% that top talent even if you have a small code<00:09:41.800> base