WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:39.880 align:start position:0% [Music] 00:00:39.880 --> 00:00:39.890 align:start position:0% 00:00:39.890 --> 00:00:43.260 align:start position:0% so<00:00:40.430> good<00:00:40.760> afternoon<00:00:41.560> earlier<00:00:42.560> this<00:00:42.710> year<00:00:42.770> I 00:00:43.260 --> 00:00:43.270 align:start position:0% so good afternoon earlier this year I 00:00:43.270 --> 00:00:45.880 align:start position:0% so good afternoon earlier this year I started<00:00:44.270> the<00:00:44.510> first<00:00:44.810> underhanded<00:00:45.530> solidity 00:00:45.880 --> 00:00:45.890 align:start position:0% started the first underhanded solidity 00:00:45.890 --> 00:00:50.500 align:start position:0% started the first underhanded solidity coat<00:00:46.220> contest<00:00:46.730> and<00:00:47.030> the<00:00:47.780> goal<00:00:47.960> was<00:00:48.500> to<00:00:49.510> write 00:00:50.500 --> 00:00:50.510 align:start position:0% coat contest and the goal was to write 00:00:50.510 --> 00:00:52.570 align:start position:0% coat contest and the goal was to write code<00:00:50.930> that<00:00:50.990> looked<00:00:51.410> innocent<00:00:51.620> on<00:00:52.100> the<00:00:52.190> surface 00:00:52.570 --> 00:00:52.580 align:start position:0% code that looked innocent on the surface 00:00:52.580 --> 00:00:54.070 align:start position:0% code that looked innocent on the surface but<00:00:52.730> actually<00:00:53.090> concealed<00:00:53.510> a<00:00:53.630> sinister 00:00:54.070 --> 00:00:54.080 align:start position:0% but actually concealed a sinister 00:00:54.080 --> 00:00:57.070 align:start position:0% but actually concealed a sinister purpose<00:00:54.880> the<00:00:55.880> reason<00:00:55.910> that<00:00:56.390> I<00:00:56.450> started<00:00:56.960> this 00:00:57.070 --> 00:00:57.080 align:start position:0% purpose the reason that I started this 00:00:57.080 --> 00:00:59.820 align:start position:0% purpose the reason that I started this was<00:00:57.350> to<00:00:57.470> encourage<00:00:57.910> deeper<00:00:58.910> thought<00:00:59.150> about 00:00:59.820 --> 00:00:59.830 align:start position:0% was to encourage deeper thought about 00:00:59.830 --> 00:01:02.740 align:start position:0% was to encourage deeper thought about smart<00:01:00.830> contract<00:01:01.280> coding<00:01:01.550> practices<00:01:02.030> and<00:01:02.390> and 00:01:02.740 --> 00:01:02.750 align:start position:0% smart contract coding practices and and 00:01:02.750 --> 00:01:05.260 align:start position:0% smart contract coding practices and and good<00:01:02.930> code<00:01:03.460> and<00:01:04.460> to<00:01:04.729> help<00:01:05.000> highlight 00:01:05.260 --> 00:01:05.270 align:start position:0% good code and to help highlight 00:01:05.270 --> 00:01:08.170 align:start position:0% good code and to help highlight potentially<00:01:06.080> issues<00:01:06.890> with<00:01:07.310> unobvious 00:01:08.170 --> 00:01:08.180 align:start position:0% potentially issues with unobvious 00:01:08.180 --> 00:01:10.510 align:start position:0% potentially issues with unobvious features<00:01:08.870> and<00:01:09.080> solidity<00:01:09.470> and<00:01:09.800> and<00:01:10.310> smart 00:01:10.510 --> 00:01:10.520 align:start position:0% features and solidity and and smart 00:01:10.520 --> 00:01:13.180 align:start position:0% features and solidity and and smart contract<00:01:10.970> programming<00:01:11.530> so<00:01:12.530> in<00:01:12.650> an<00:01:12.770> attempt<00:01:13.100> to 00:01:13.180 --> 00:01:13.190 align:start position:0% contract programming so in an attempt to 00:01:13.190 --> 00:01:14.710 align:start position:0% contract programming so in an attempt to capture<00:01:13.430> the<00:01:13.610> sort<00:01:13.880> of<00:01:13.910> current<00:01:14.570> zeitgeist 00:01:14.710 --> 00:01:14.720 align:start position:0% capture the sort of current zeitgeist 00:01:14.720 --> 00:01:17.760 align:start position:0% capture the sort of current zeitgeist the<00:01:15.380> theme<00:01:15.740> was<00:01:16.009> token<00:01:17.000> sales<00:01:17.240> and 00:01:17.760 --> 00:01:17.770 align:start position:0% the theme was token sales and 00:01:17.770 --> 00:01:20.890 align:start position:0% the theme was token sales and participants<00:01:18.770> were<00:01:18.860> challenged<00:01:19.430> to<00:01:19.610> write<00:01:20.600> a 00:01:20.890 --> 00:01:20.900 align:start position:0% participants were challenged to write a 00:01:20.900 --> 00:01:23.469 align:start position:0% participants were challenged to write a contract<00:01:21.770> that<00:01:21.890> was<00:01:22.040> in<00:01:22.190> some<00:01:22.400> way<00:01:22.610> involved 00:01:23.469 --> 00:01:23.479 align:start position:0% contract that was in some way involved 00:01:23.479 --> 00:01:26.430 align:start position:0% contract that was in some way involved with<00:01:23.630> token<00:01:23.930> sales<00:01:24.140> and<00:01:24.560> looked<00:01:25.130> innocent<00:01:25.369> but 00:01:26.430 --> 00:01:26.440 align:start position:0% with token sales and looked innocent but 00:01:26.440 --> 00:01:29.020 align:start position:0% with token sales and looked innocent but had<00:01:27.440> some<00:01:27.770> advantage<00:01:28.369> for<00:01:28.610> the<00:01:28.700> person 00:01:29.020 --> 00:01:29.030 align:start position:0% had some advantage for the person 00:01:29.030 --> 00:01:32.160 align:start position:0% had some advantage for the person running<00:01:29.210> the<00:01:29.390> token<00:01:29.690> sale<00:01:30.160> and<00:01:31.160> ideally<00:01:31.610> the 00:01:32.160 --> 00:01:32.170 align:start position:0% running the token sale and ideally the 00:01:32.170 --> 00:01:35.469 align:start position:0% running the token sale and ideally the sinister<00:01:33.170> purpose<00:01:33.560> should<00:01:33.800> be<00:01:34.009> by<00:01:34.580> ignored<00:01:35.270> by 00:01:35.469 --> 00:01:35.479 align:start position:0% sinister purpose should be by ignored by 00:01:35.479 --> 00:01:37.420 align:start position:0% sinister purpose should be by ignored by an<00:01:35.600> auditor<00:01:35.750> or<00:01:36.170> if<00:01:36.470> it<00:01:36.590> was<00:01:36.680> discovered<00:01:37.040> then 00:01:37.420 --> 00:01:37.430 align:start position:0% an auditor or if it was discovered then 00:01:37.430 --> 00:01:41.710 align:start position:0% an auditor or if it was discovered then easily<00:01:39.580> excusable<00:01:40.580> or<00:01:40.850> explainable<00:01:41.420> as<00:01:41.630> an 00:01:41.710 --> 00:01:41.720 align:start position:0% easily excusable or explainable as an 00:01:41.720 --> 00:01:44.289 align:start position:0% easily excusable or explainable as an innocent<00:01:42.110> mistake<00:01:42.200> and<00:01:42.860> so<00:01:43.700> I<00:01:43.729> have<00:01:43.909> here<00:01:44.090> the 00:01:44.289 --> 00:01:44.299 align:start position:0% innocent mistake and so I have here the 00:01:44.299 --> 00:01:46.870 align:start position:0% innocent mistake and so I have here the three<00:01:44.720> winners<00:01:45.049> of<00:01:45.290> the<00:01:45.710> contest<00:01:46.159> this<00:01:46.580> year 00:01:46.870 --> 00:01:46.880 align:start position:0% three winners of the contest this year 00:01:46.880 --> 00:01:50.890 align:start position:0% three winners of the contest this year we<00:01:47.840> have<00:01:47.990> Joelle<00:01:48.380> who<00:01:48.830> came<00:01:49.100> in<00:01:49.250> third<00:01:49.900> Richard 00:01:50.890 --> 00:01:50.900 align:start position:0% we have Joelle who came in third Richard 00:01:50.900 --> 00:01:52.870 align:start position:0% we have Joelle who came in third Richard who<00:01:51.020> came<00:01:51.229> in<00:01:51.380> second<00:01:51.799> and<00:01:52.040> Martin<00:01:52.580> who<00:01:52.700> came 00:01:52.870 --> 00:01:52.880 align:start position:0% who came in second and Martin who came 00:01:52.880 --> 00:01:56.320 align:start position:0% who came in second and Martin who came in<00:01:53.030> first<00:01:53.240> and<00:01:53.570> so<00:01:54.320> I'd<00:01:54.380> like<00:01:54.530> to<00:01:54.710> start<00:01:55.330> the 00:01:56.320 --> 00:01:56.330 align:start position:0% in first and so I'd like to start the 00:01:56.330 --> 00:01:58.120 align:start position:0% in first and so I'd like to start the our<00:01:56.479> discussion<00:01:57.080> about<00:01:57.170> smart<00:01:57.740> contract 00:01:58.120 --> 00:01:58.130 align:start position:0% our discussion about smart contract 00:01:58.130 --> 00:02:00.700 align:start position:0% our discussion about smart contract security<00:01:58.490> by<00:01:58.640> asking<00:01:59.150> each<00:01:59.510> of<00:01:59.869> the<00:02:00.140> panelists 00:02:00.700 --> 00:02:00.710 align:start position:0% security by asking each of the panelists 00:02:00.710 --> 00:02:02.859 align:start position:0% security by asking each of the panelists to<00:02:00.770> describe<00:02:01.490> their<00:02:01.790> winning<00:02:02.090> salute<00:02:02.420> winning 00:02:02.859 --> 00:02:02.869 align:start position:0% to describe their winning salute winning 00:02:02.869 --> 00:02:05.080 align:start position:0% to describe their winning salute winning entry<00:02:03.110> and<00:02:03.460> what<00:02:04.460> they<00:02:04.580> think<00:02:04.670> is<00:02:04.790> a<00:02:04.880> novel 00:02:05.080 --> 00:02:05.090 align:start position:0% entry and what they think is a novel 00:02:05.090 --> 00:02:07.240 align:start position:0% entry and what they think is a novel about<00:02:05.330> it<00:02:05.510> so<00:02:05.990> would<00:02:06.470> you<00:02:06.590> like<00:02:06.619> to<00:02:06.770> start 00:02:07.240 --> 00:02:07.250 align:start position:0% about it so would you like to start 00:02:07.250 --> 00:02:12.100 align:start position:0% about it so would you like to start sure<00:02:08.119> well<00:02:09.049> my<00:02:09.799> entry<00:02:10.250> is<00:02:10.489> a<00:02:11.209> proposal<00:02:11.780> for<00:02:12.080> a 00:02:12.100 --> 00:02:12.110 align:start position:0% sure well my entry is a proposal for a 00:02:12.110 --> 00:02:14.740 align:start position:0% sure well my entry is a proposal for a Dutch<00:02:12.320> auction<00:02:12.590> crowd<00:02:12.980> sale<00:02:13.400> so<00:02:14.299> in<00:02:14.600> this 00:02:14.740 --> 00:02:14.750 align:start position:0% Dutch auction crowd sale so in this 00:02:14.750 --> 00:02:18.220 align:start position:0% Dutch auction crowd sale so in this model<00:02:15.580> the<00:02:16.580> sale<00:02:16.820> starts<00:02:16.940> with<00:02:17.420> really<00:02:18.049> high 00:02:18.220 --> 00:02:18.230 align:start position:0% model the sale starts with really high 00:02:18.230 --> 00:02:20.560 align:start position:0% model the sale starts with really high price<00:02:18.650> per<00:02:18.890> token<00:02:19.160> that<00:02:19.570> decreases 00:02:20.560 --> 00:02:20.570 align:start position:0% price per token that decreases 00:02:20.570 --> 00:02:23.440 align:start position:0% price per token that decreases continually<00:02:21.170> as<00:02:21.440> the<00:02:22.220> as<00:02:22.580> the<00:02:22.730> patent<00:02:23.030> as<00:02:23.299> the 00:02:23.440 --> 00:02:23.450 align:start position:0% continually as the as the patent as the 00:02:23.450 --> 00:02:27.250 align:start position:0% continually as the as the patent as the time<00:02:23.660> passes<00:02:24.280> so<00:02:25.280> buyers<00:02:25.910> can<00:02:26.120> enter<00:02:26.600> the<00:02:26.780> sale 00:02:27.250 --> 00:02:27.260 align:start position:0% time passes so buyers can enter the sale 00:02:27.260 --> 00:02:29.229 align:start position:0% time passes so buyers can enter the sale in<00:02:27.620> whatever<00:02:27.920> time<00:02:28.340> the<00:02:28.519> issue<00:02:28.700> the<00:02:28.820> price<00:02:29.030> is 00:02:29.229 --> 00:02:29.239 align:start position:0% in whatever time the issue the price is 00:02:29.239 --> 00:02:33.280 align:start position:0% in whatever time the issue the price is fair<00:02:30.250> the<00:02:31.250> CEO<00:02:31.489> ends<00:02:31.880> or<00:02:32.090> when<00:02:32.810> either<00:02:32.989> the<00:02:33.260> the 00:02:33.280 --> 00:02:33.290 align:start position:0% fair the CEO ends or when either the the 00:02:33.290 --> 00:02:36.880 align:start position:0% fair the CEO ends or when either the the time<00:02:33.920> finishes<00:02:34.580> or<00:02:34.850> they<00:02:35.120> cut<00:02:35.570> the<00:02:35.989> door<00:02:36.230> sorry 00:02:36.880 --> 00:02:36.890 align:start position:0% time finishes or they cut the door sorry 00:02:36.890 --> 00:02:40.090 align:start position:0% time finishes or they cut the door sorry or<00:02:37.130> the<00:02:37.340> capped<00:02:37.610> is<00:02:37.880> reached<00:02:38.209> so<00:02:38.650> the<00:02:39.650> thing<00:02:40.070> is 00:02:40.090 --> 00:02:40.100 align:start position:0% or the capped is reached so the thing is 00:02:40.100 --> 00:02:43.720 align:start position:0% or the capped is reached so the thing is I<00:02:40.459> made<00:02:40.880> use<00:02:41.120> of<00:02:41.150> a<00:02:41.930> feature<00:02:42.650> of<00:02:42.769> solidity<00:02:43.459> that 00:02:43.720 --> 00:02:43.730 align:start position:0% I made use of a feature of solidity that 00:02:43.730 --> 00:02:45.670 align:start position:0% I made use of a feature of solidity that is<00:02:43.850> that<00:02:44.090> anyone<00:02:44.510> can<00:02:44.570> forcibly<00:02:45.079> send<00:02:45.470> error 00:02:45.670 --> 00:02:45.680 align:start position:0% is that anyone can forcibly send error 00:02:45.680 --> 00:02:48.339 align:start position:0% is that anyone can forcibly send error to<00:02:46.519> a<00:02:46.549> contract<00:02:47.150> without<00:02:47.540> tricking<00:02:48.140> code 00:02:48.339 --> 00:02:48.349 align:start position:0% to a contract without tricking code 00:02:48.349 --> 00:02:51.380 align:start position:0% to a contract without tricking code execution<00:02:48.830> so<00:02:49.760> in<00:02:49.880> that<00:02:50.000> scenario 00:02:51.380 --> 00:02:51.390 align:start position:0% execution so in that scenario 00:02:51.390 --> 00:02:54.710 align:start position:0% execution so in that scenario the<00:02:52.040> co-owners<00:02:53.040> could<00:02:53.460> sneak<00:02:54.000> in<00:02:54.180> some<00:02:54.450> header 00:02:54.710 --> 00:02:54.720 align:start position:0% the co-owners could sneak in some header 00:02:54.720 --> 00:02:58.550 align:start position:0% the co-owners could sneak in some header during<00:02:55.650> the<00:02:55.740> sale<00:02:56.010> to<00:02:56.550> inflate<00:02:57.090> the<00:02:57.560> token 00:02:58.550 --> 00:02:58.560 align:start position:0% during the sale to inflate the token 00:02:58.560 --> 00:03:01.250 align:start position:0% during the sale to inflate the token price<00:02:58.830> making<00:02:59.280> the<00:02:59.580> touch<00:03:00.330> the<00:03:00.720> traction<00:03:01.140> and 00:03:01.250 --> 00:03:01.260 align:start position:0% price making the touch the traction and 00:03:01.260 --> 00:03:05.180 align:start position:0% price making the touch the traction and earlier<00:03:02.390> so<00:03:03.390> if<00:03:03.660> you<00:03:03.690> couple<00:03:04.140> that<00:03:04.170> with<00:03:04.350> for 00:03:05.180 --> 00:03:05.190 align:start position:0% earlier so if you couple that with for 00:03:05.190 --> 00:03:07.520 align:start position:0% earlier so if you couple that with for example<00:03:05.280> a<00:03:05.670> min<00:03:05.850> table<00:03:06.090> token<00:03:06.450> that<00:03:06.660> is<00:03:07.410> a 00:03:07.520 --> 00:03:07.530 align:start position:0% example a min table token that is a 00:03:07.530 --> 00:03:10.730 align:start position:0% example a min table token that is a token<00:03:08.070> that<00:03:08.100> you<00:03:08.700> only<00:03:09.300> mint<00:03:09.660> amount<00:03:10.110> of<00:03:10.320> token 00:03:10.730 --> 00:03:10.740 align:start position:0% token that you only mint amount of token 00:03:10.740 --> 00:03:11.570 align:start position:0% token that you only mint amount of token that<00:03:10.920> was<00:03:11.040> bought 00:03:11.570 --> 00:03:11.580 align:start position:0% that was bought 00:03:11.580 --> 00:03:15.320 align:start position:0% that was bought you<00:03:12.120> can<00:03:12.390> like<00:03:13.520> really<00:03:14.520> inflate<00:03:14.940> the<00:03:15.060> token 00:03:15.320 --> 00:03:15.330 align:start position:0% you can like really inflate the token 00:03:15.330 --> 00:03:18.230 align:start position:0% you can like really inflate the token price<00:03:15.600> because<00:03:16.320> you<00:03:16.890> put<00:03:17.190> money<00:03:17.459> on<00:03:17.640> the<00:03:17.970> on 00:03:18.230 --> 00:03:18.240 align:start position:0% price because you put money on the on 00:03:18.240 --> 00:03:21.440 align:start position:0% price because you put money on the on the<00:03:18.390> auction<00:03:18.840> but<00:03:19.680> you<00:03:19.800> don't<00:03:20.010> mint<00:03:20.250> tokens<00:03:20.850> so 00:03:21.440 --> 00:03:21.450 align:start position:0% the auction but you don't mint tokens so 00:03:21.450 --> 00:03:24.790 align:start position:0% the auction but you don't mint tokens so you're<00:03:21.690> raising<00:03:22.080> valuation<00:03:22.890> of<00:03:23.010> the<00:03:23.790> token 00:03:24.790 --> 00:03:24.800 align:start position:0% you're raising valuation of the token 00:03:24.800 --> 00:03:27.610 align:start position:0% you're raising valuation of the token artificially<00:03:25.800> irregardless<00:03:26.220> of<00:03:26.520> marketing 00:03:27.610 --> 00:03:27.620 align:start position:0% artificially irregardless of marketing 00:03:27.620 --> 00:03:32.990 align:start position:0% artificially irregardless of marketing interest<00:03:28.620> and<00:03:29.610> another<00:03:30.420> retail<00:03:30.780> is<00:03:31.670> you<00:03:32.670> can 00:03:32.990 --> 00:03:33.000 align:start position:0% interest and another retail is you can 00:03:33.000 --> 00:03:36.680 align:start position:0% interest and another retail is you can kind<00:03:33.330> of<00:03:33.540> use<00:03:33.959> this<00:03:34.260> as<00:03:34.800> an<00:03:35.280> as<00:03:35.970> an<00:03:36.209> influence 00:03:36.680 --> 00:03:36.690 align:start position:0% kind of use this as an as an influence 00:03:36.690 --> 00:03:38.870 align:start position:0% kind of use this as an as an influence it<00:03:36.840> because<00:03:37.230> if<00:03:37.739> people<00:03:38.010> are<00:03:38.250> watching<00:03:38.760> the 00:03:38.870 --> 00:03:38.880 align:start position:0% it because if people are watching the 00:03:38.880 --> 00:03:42.110 align:start position:0% it because if people are watching the sale<00:03:39.150> and<00:03:39.510> they<00:03:39.930> see<00:03:39.989> that<00:03:40.650> it's<00:03:41.130> it's 00:03:42.110 --> 00:03:42.120 align:start position:0% sale and they see that it's it's 00:03:42.120 --> 00:03:44.810 align:start position:0% sale and they see that it's it's reaching<00:03:42.570> the<00:03:42.660> cap<00:03:42.900> really<00:03:43.380> fast<00:03:43.680> they<00:03:44.550> might 00:03:44.810 --> 00:03:44.820 align:start position:0% reaching the cap really fast they might 00:03:44.820 --> 00:03:46.670 align:start position:0% reaching the cap really fast they might want<00:03:45.120> you<00:03:45.300> getting<00:03:45.660> earlier<00:03:46.110> than<00:03:46.290> they<00:03:46.470> would 00:03:46.670 --> 00:03:46.680 align:start position:0% want you getting earlier than they would 00:03:46.680 --> 00:03:50.449 align:start position:0% want you getting earlier than they would if<00:03:46.980> in<00:03:47.520> normal<00:03:47.910> conditions<00:03:48.420> so<00:03:48.690> it's<00:03:49.290> an<00:03:49.739> kind 00:03:50.449 --> 00:03:50.459 align:start position:0% if in normal conditions so it's an kind 00:03:50.459 --> 00:03:52.670 align:start position:0% if in normal conditions so it's an kind of<00:03:50.580> effective<00:03:51.150> way<00:03:51.330> to<00:03:51.390> manipulate<00:03:51.840> market<00:03:52.560> in 00:03:52.670 --> 00:03:52.680 align:start position:0% of effective way to manipulate market in 00:03:52.680 --> 00:03:55.520 align:start position:0% of effective way to manipulate market in your<00:03:52.860> favour<00:03:53.130> using<00:03:54.090> this<00:03:54.239> this<00:03:55.080> little 00:03:55.520 --> 00:03:55.530 align:start position:0% your favour using this this little 00:03:55.530 --> 00:03:59.060 align:start position:0% your favour using this this little feature<00:03:56.690> right<00:03:57.690> and<00:03:57.930> Richard<00:03:58.830> would<00:03:58.950> you 00:03:59.060 --> 00:03:59.070 align:start position:0% feature right and Richard would you 00:03:59.070 --> 00:04:00.979 align:start position:0% feature right and Richard would you describe<00:03:59.370> your<00:03:59.549> submission<00:04:00.030> okay<00:04:00.540> testing 00:04:00.979 --> 00:04:00.989 align:start position:0% describe your submission okay testing 00:04:00.989 --> 00:04:01.699 align:start position:0% describe your submission okay testing there<00:04:01.230> we<00:04:01.320> go 00:04:01.699 --> 00:04:01.709 align:start position:0% there we go 00:04:01.709 --> 00:04:04.640 align:start position:0% there we go so<00:04:02.570> very<00:04:03.570> similar<00:04:03.900> I<00:04:04.110> actually<00:04:04.290> didn't<00:04:04.560> know 00:04:04.640 --> 00:04:04.650 align:start position:0% so very similar I actually didn't know 00:04:04.650 --> 00:04:06.500 align:start position:0% so very similar I actually didn't know about<00:04:04.769> the<00:04:05.040> suicide<00:04:05.640> bug<00:04:05.850> which<00:04:06.120> allowed<00:04:06.330> you 00:04:06.500 --> 00:04:06.510 align:start position:0% about the suicide bug which allowed you 00:04:06.510 --> 00:04:08.660 align:start position:0% about the suicide bug which allowed you to<00:04:06.540> get<00:04:06.989> money<00:04:07.650> into<00:04:07.860> a<00:04:07.890> contract<00:04:08.280> with<00:04:08.340> a<00:04:08.430> code 00:04:08.660 --> 00:04:08.670 align:start position:0% to get money into a contract with a code 00:04:08.670 --> 00:04:11.090 align:start position:0% to get money into a contract with a code execution<00:04:09.090> but<00:04:10.019> it<00:04:10.140> basically<00:04:10.560> uses<00:04:10.739> the<00:04:10.950> same 00:04:11.090 --> 00:04:11.100 align:start position:0% execution but it basically uses the same 00:04:11.100 --> 00:04:15.080 align:start position:0% execution but it basically uses the same idea<00:04:11.670> which<00:04:12.180> is<00:04:12.980> there<00:04:13.980> was<00:04:14.130> a<00:04:14.160> so<00:04:14.730> the<00:04:14.820> basic 00:04:15.080 --> 00:04:15.090 align:start position:0% idea which is there was a so the basic 00:04:15.090 --> 00:04:18.620 align:start position:0% idea which is there was a so the basic idea<00:04:15.269> of<00:04:15.540> the<00:04:15.630> contract<00:04:15.930> is<00:04:16.229> you<00:04:16.380> have<00:04:16.590> a<00:04:17.630> crowd 00:04:18.620 --> 00:04:18.630 align:start position:0% idea of the contract is you have a crowd 00:04:18.630 --> 00:04:22.969 align:start position:0% idea of the contract is you have a crowd sale<00:04:18.870> and<00:04:19.140> the<00:04:19.549> the<00:04:21.229> runner<00:04:22.229> of<00:04:22.470> the<00:04:22.650> the 00:04:22.969 --> 00:04:22.979 align:start position:0% sale and the the runner of the the 00:04:22.979 --> 00:04:26.450 align:start position:0% sale and the the runner of the the runner<00:04:23.430> yeah<00:04:23.669> the<00:04:23.850> issuer<00:04:24.150> of<00:04:24.390> the<00:04:24.419> token<00:04:25.460> gets 00:04:26.450 --> 00:04:26.460 align:start position:0% runner yeah the issuer of the token gets 00:04:26.460 --> 00:04:28.909 align:start position:0% runner yeah the issuer of the token gets one<00:04:27.120> either<00:04:27.570> the<00:04:27.690> first<00:04:27.840> week<00:04:28.140> to<00:04:28.169> ether<00:04:28.770> the 00:04:28.909 --> 00:04:28.919 align:start position:0% one either the first week to ether the 00:04:28.919 --> 00:04:31.250 align:start position:0% one either the first week to ether the second<00:04:29.250> week<00:04:29.340> for<00:04:29.940> the<00:04:30.510> next<00:04:30.690> week<00:04:30.840> so<00:04:30.990> on<00:04:31.110> and 00:04:31.250 --> 00:04:31.260 align:start position:0% second week for the next week so on and 00:04:31.260 --> 00:04:33.860 align:start position:0% second week for the next week so on and so<00:04:31.350> on<00:04:31.380> the<00:04:32.250> idea<00:04:32.280> being<00:04:32.669> that<00:04:32.760> if<00:04:33.120> they're<00:04:33.840> not 00:04:33.860 --> 00:04:33.870 align:start position:0% so on the idea being that if they're not 00:04:33.870 --> 00:04:35.120 align:start position:0% so on the idea being that if they're not doing<00:04:34.110> what<00:04:34.229> you<00:04:34.350> expect<00:04:34.650> you<00:04:34.770> can<00:04:34.919> kind<00:04:35.100> of 00:04:35.120 --> 00:04:35.130 align:start position:0% doing what you expect you can kind of 00:04:35.130 --> 00:04:37.940 align:start position:0% doing what you expect you can kind of yank<00:04:35.370> your<00:04:35.580> money<00:04:35.729> back<00:04:35.910> from<00:04:36.150> them<00:04:36.740> it<00:04:37.740> comes 00:04:37.940 --> 00:04:37.950 align:start position:0% yank your money back from them it comes 00:04:37.950 --> 00:04:41.659 align:start position:0% yank your money back from them it comes down<00:04:38.100> to<00:04:38.160> using<00:04:38.669> this<00:04:38.850> stop<00:04:39.060> balance<00:04:39.450> and<00:04:40.669> so 00:04:41.659 --> 00:04:41.669 align:start position:0% down to using this stop balance and so 00:04:41.669 --> 00:04:43.250 align:start position:0% down to using this stop balance and so again<00:04:42.030> as<00:04:42.180> long<00:04:42.210> as<00:04:42.360> the<00:04:42.720> contract<00:04:43.110> isn't 00:04:43.250 --> 00:04:43.260 align:start position:0% again as long as the contract isn't 00:04:43.260 --> 00:04:45.350 align:start position:0% again as long as the contract isn't executing<00:04:43.950> as<00:04:44.040> you<00:04:44.160> expect<00:04:44.550> this<00:04:45.150> stop 00:04:45.350 --> 00:04:45.360 align:start position:0% executing as you expect this stop 00:04:45.360 --> 00:04:47.390 align:start position:0% executing as you expect this stop balance<00:04:45.690> can<00:04:46.200> never<00:04:46.470> be<00:04:46.710> more<00:04:47.040> than<00:04:47.280> the 00:04:47.390 --> 00:04:47.400 align:start position:0% balance can never be more than the 00:04:47.400 --> 00:04:48.500 align:start position:0% balance can never be more than the amount<00:04:47.610> you<00:04:47.820> received 00:04:48.500 --> 00:04:48.510 align:start position:0% amount you received 00:04:48.510 --> 00:04:51.350 align:start position:0% amount you received unlike<00:04:49.380> the<00:04:49.560> suicided<00:04:50.100> method<00:04:50.400> which<00:04:50.760> again<00:04:51.300> I 00:04:51.350 --> 00:04:51.360 align:start position:0% unlike the suicided method which again I 00:04:51.360 --> 00:04:53.600 align:start position:0% unlike the suicided method which again I don't<00:04:51.450> know<00:04:51.570> about<00:04:51.690> but<00:04:52.200> I<00:04:52.229> have<00:04:52.680> more<00:04:53.370> clever 00:04:53.600 --> 00:04:53.610 align:start position:0% don't know about but I have more clever 00:04:53.610 --> 00:04:56.409 align:start position:0% don't know about but I have more clever solutions<00:04:54.030> now<00:04:54.210> if<00:04:54.360> I<00:04:54.450> was<00:04:54.570> new<00:04:54.990> of<00:04:55.110> that<00:04:55.229> the 00:04:56.409 --> 00:04:56.419 align:start position:0% solutions now if I was new of that the 00:04:56.419 --> 00:04:58.700 align:start position:0% solutions now if I was new of that the basically<00:04:57.419> you<00:04:57.630> compute<00:04:58.080> the<00:04:58.200> address<00:04:58.560> the 00:04:58.700 --> 00:04:58.710 align:start position:0% basically you compute the address the 00:04:58.710 --> 00:05:00.950 align:start position:0% basically you compute the address the contract<00:04:59.220> is<00:04:59.310> going<00:04:59.370> to<00:04:59.640> live<00:04:59.789> at<00:04:59.940> before<00:05:00.840> you 00:05:00.950 --> 00:05:00.960 align:start position:0% contract is going to live at before you 00:05:00.960 --> 00:05:03.560 align:start position:0% contract is going to live at before you deploy<00:05:01.229> it<00:05:01.410> send<00:05:02.190> ether<00:05:02.520> to<00:05:02.669> it<00:05:02.849> and<00:05:03.030> now<00:05:03.510> you 00:05:03.560 --> 00:05:03.570 align:start position:0% deploy it send ether to it and now you 00:05:03.570 --> 00:05:04.730 align:start position:0% deploy it send ether to it and now you deploy<00:05:03.870> the<00:05:03.990> contract<00:05:04.440> at 00:05:04.730 --> 00:05:04.740 align:start position:0% deploy the contract at 00:05:04.740 --> 00:05:06.620 align:start position:0% deploy the contract at now<00:05:04.800> the<00:05:04.860> contract<00:05:05.250> actually<00:05:05.669> is<00:05:05.789> breaking 00:05:06.620 --> 00:05:06.630 align:start position:0% now the contract actually is breaking 00:05:06.630 --> 00:05:09.529 align:start position:0% now the contract actually is breaking the<00:05:07.039> invariant<00:05:08.039> that<00:05:08.250> this<00:05:08.729> stop<00:05:08.940> balance<00:05:09.330> is 00:05:09.529 --> 00:05:09.539 align:start position:0% the invariant that this stop balance is 00:05:09.539 --> 00:05:11.659 align:start position:0% the invariant that this stop balance is strictly<00:05:10.050> less<00:05:10.319> than<00:05:10.380> the<00:05:11.009> amount<00:05:11.160> it<00:05:11.370> thinks 00:05:11.659 --> 00:05:11.669 align:start position:0% strictly less than the amount it thinks 00:05:11.669 --> 00:05:14.150 align:start position:0% strictly less than the amount it thinks it<00:05:11.759> has<00:05:12.949> great 00:05:14.150 --> 00:05:14.160 align:start position:0% it has great 00:05:14.160 --> 00:05:19.779 align:start position:0% it has great and<00:05:14.280> finally<00:05:14.789> Madame's<00:05:15.860> so<00:05:16.860> in<00:05:17.220> my<00:05:18.060> entry<00:05:18.539> I 00:05:19.779 --> 00:05:19.789 align:start position:0% and finally Madame's so in my entry I 00:05:19.789 --> 00:05:24.439 align:start position:0% and finally Madame's so in my entry I I'm<00:05:20.789> gonna<00:05:21.090> start<00:05:21.360> by<00:05:21.599> describing<00:05:21.930> the<00:05:22.650> bug<00:05:23.449> my 00:05:24.439 --> 00:05:24.449 align:start position:0% I'm gonna start by describing the bug my 00:05:24.449 --> 00:05:27.890 align:start position:0% I'm gonna start by describing the bug my entry<00:05:24.780> is<00:05:24.990> based<00:05:25.349> on<00:05:25.740> a<00:05:26.190> bi<00:05:26.550> encoding<00:05:27.360> and<00:05:27.569> how 00:05:27.890 --> 00:05:27.900 align:start position:0% entry is based on a bi encoding and how 00:05:27.900 --> 00:05:31.640 align:start position:0% entry is based on a bi encoding and how solidity<00:05:28.680> handles<00:05:29.310> a<00:05:29.460> bi<00:05:29.759> decoding<00:05:30.509> in<00:05:31.380> run 00:05:31.640 --> 00:05:31.650 align:start position:0% solidity handles a bi decoding in run 00:05:31.650 --> 00:05:35.020 align:start position:0% solidity handles a bi decoding in run time<00:05:32.150> maybe<00:05:33.150> everyone<00:05:33.750> doesn't<00:05:33.780> know<00:05:34.319> that 00:05:35.020 --> 00:05:35.030 align:start position:0% time maybe everyone doesn't know that 00:05:35.030 --> 00:05:39.710 align:start position:0% time maybe everyone doesn't know that actual<00:05:36.030> the<00:05:36.599> EVM<00:05:37.050> and<00:05:37.500> the<00:05:37.860> code<00:05:38.130> in<00:05:38.720> a 00:05:39.710 --> 00:05:39.720 align:start position:0% actual the EVM and the code in a 00:05:39.720 --> 00:05:43.279 align:start position:0% actual the EVM and the code in a contract<00:05:40.819> doesn't<00:05:41.819> really<00:05:42.150> have<00:05:42.449> a<00:05:42.479> notion<00:05:42.810> of 00:05:43.279 --> 00:05:43.289 align:start position:0% contract doesn't really have a notion of 00:05:43.289 --> 00:05:47.240 align:start position:0% contract doesn't really have a notion of methods<00:05:44.060> that's<00:05:45.060> an<00:05:45.419> invention<00:05:46.409> on<00:05:46.860> top<00:05:47.099> of 00:05:47.240 --> 00:05:47.250 align:start position:0% methods that's an invention on top of 00:05:47.250 --> 00:05:51.520 align:start position:0% methods that's an invention on top of the<00:05:47.340> EVM<00:05:47.699> so<00:05:48.479> on<00:05:49.229> the<00:05:49.620> fly 00:05:51.520 --> 00:05:51.530 align:start position:0% the EVM so on the fly 00:05:51.530 --> 00:05:55.370 align:start position:0% the EVM so on the fly some<00:05:52.530> bytecode<00:05:53.509> determines<00:05:54.509> what<00:05:54.930> method<00:05:55.259> is 00:05:55.370 --> 00:05:55.380 align:start position:0% some bytecode determines what method is 00:05:55.380 --> 00:05:57.439 align:start position:0% some bytecode determines what method is called<00:05:55.590> and<00:05:55.860> what<00:05:55.949> the<00:05:56.069> parameters<00:05:56.639> are<00:05:56.880> and 00:05:57.439 --> 00:05:57.449 align:start position:0% called and what the parameters are and 00:05:57.449 --> 00:06:02.450 align:start position:0% called and what the parameters are and this<00:05:57.599> is<00:05:57.780> encoded<00:05:58.259> by<00:05:58.289> a<00:05:58.440> ABI<00:05:59.180> and<00:06:01.460> certain 00:06:02.450 --> 00:06:02.460 align:start position:0% this is encoded by a ABI and certain 00:06:02.460 --> 00:06:04.210 align:start position:0% this is encoded by a ABI and certain types<00:06:02.639> of<00:06:02.789> parameters<00:06:03.300> such<00:06:03.509> as<00:06:03.539> dynamic 00:06:04.210 --> 00:06:04.220 align:start position:0% types of parameters such as dynamic 00:06:04.220 --> 00:06:07.670 align:start position:0% types of parameters such as dynamic dynamic<00:06:05.220> length<00:06:05.669> arrays<00:06:06.210> have<00:06:06.900> a<00:06:06.930> length<00:06:07.289> and 00:06:07.670 --> 00:06:07.680 align:start position:0% dynamic length arrays have a length and 00:06:07.680 --> 00:06:11.839 align:start position:0% dynamic length arrays have a length and that<00:06:08.430> length<00:06:08.490> is<00:06:09.060> not<00:06:09.440> enforced<00:06:10.789> by<00:06:11.789> the 00:06:11.839 --> 00:06:11.849 align:start position:0% that length is not enforced by the 00:06:11.849 --> 00:06:15.890 align:start position:0% that length is not enforced by the decoder<00:06:13.009> so<00:06:14.009> it's<00:06:14.219> possible<00:06:14.669> I<00:06:14.909> noticed<00:06:15.479> to 00:06:15.890 --> 00:06:15.900 align:start position:0% decoder so it's possible I noticed to 00:06:15.900 --> 00:06:20.240 align:start position:0% decoder so it's possible I noticed to specify<00:06:16.440> a<00:06:16.469> very<00:06:16.889> very<00:06:17.130> large<00:06:17.370> length<00:06:19.250> and 00:06:20.240 --> 00:06:20.250 align:start position:0% specify a very very large length and 00:06:20.250 --> 00:06:26.450 align:start position:0% specify a very very large length and make<00:06:20.940> the<00:06:21.180> this<00:06:22.639> value<00:06:23.639> overflow<00:06:25.159> and<00:06:26.159> that's 00:06:26.450 --> 00:06:26.460 align:start position:0% make the this value overflow and that's 00:06:26.460 --> 00:06:28.959 align:start position:0% make the this value overflow and that's what<00:06:26.669> I<00:06:26.699> kind<00:06:26.909> of<00:06:27.060> designed<00:06:27.479> my<00:06:27.960> entry<00:06:28.409> around 00:06:28.959 --> 00:06:28.969 align:start position:0% what I kind of designed my entry around 00:06:28.969 --> 00:06:31.670 align:start position:0% what I kind of designed my entry around and<00:06:29.969> it<00:06:30.090> was<00:06:30.210> a<00:06:30.270> bit<00:06:30.479> difficult<00:06:30.960> because<00:06:31.139> I<00:06:31.500> had 00:06:31.670 --> 00:06:31.680 align:start position:0% and it was a bit difficult because I had 00:06:31.680 --> 00:06:35.029 align:start position:0% and it was a bit difficult because I had to<00:06:31.800> make<00:06:32.009> sure<00:06:32.039> that<00:06:33.139> during<00:06:34.139> a<00:06:34.259> loop 00:06:35.029 --> 00:06:35.039 align:start position:0% to make sure that during a loop 00:06:35.039 --> 00:06:37.850 align:start position:0% to make sure that during a loop I<00:06:35.069> can't<00:06:35.669> loop<00:06:35.969> against<00:06:36.479> the<00:06:36.630> size<00:06:36.900> but<00:06:37.469> still 00:06:37.850 --> 00:06:37.860 align:start position:0% I can't loop against the size but still 00:06:37.860 --> 00:06:40.999 align:start position:0% I can't loop against the size but still use<00:06:38.099> the<00:06:38.340> size<00:06:38.610> to<00:06:39.240> somehow<00:06:40.020> give<00:06:40.469> a<00:06:40.500> kick<00:06:40.770> back 00:06:40.999 --> 00:06:41.009 align:start position:0% use the size to somehow give a kick back 00:06:41.009 --> 00:06:45.920 align:start position:0% use the size to somehow give a kick back to<00:06:41.610> the<00:06:42.030> attacker<00:06:42.330> and<00:06:44.090> in<00:06:45.090> the<00:06:45.210> end<00:06:45.360> it<00:06:45.599> became 00:06:45.920 --> 00:06:45.930 align:start position:0% to the attacker and in the end it became 00:06:45.930 --> 00:06:49.089 align:start position:0% to the attacker and in the end it became a<00:06:45.990> kind<00:06:46.440> of<00:06:46.590> a<00:06:46.800> round<00:06:47.099> table<00:06:47.819> where<00:06:47.969> you<00:06:48.030> can 00:06:49.089 --> 00:06:49.099 align:start position:0% a kind of a round table where you can 00:06:49.099 --> 00:06:53.890 align:start position:0% a kind of a round table where you can round<00:06:50.099> table<00:06:50.669> Dao<00:06:51.449> like<00:06:51.810> thing<00:06:52.229> which<00:06:53.039> you<00:06:53.819> can 00:06:53.890 --> 00:06:53.900 align:start position:0% round table Dao like thing which you can 00:06:53.900 --> 00:06:57.020 align:start position:0% round table Dao like thing which you can pay<00:06:54.900> for<00:06:54.960> try<00:06:55.620> to<00:06:55.680> get<00:06:55.860> a<00:06:55.889> seat<00:06:56.250> on<00:06:56.490> this<00:06:56.699> round 00:06:57.020 --> 00:06:57.030 align:start position:0% pay for try to get a seat on this round 00:06:57.030 --> 00:07:01.850 align:start position:0% pay for try to get a seat on this round table<00:06:57.479> and<00:06:59.000> submit<00:07:00.000> multiple<00:07:00.270> bits<00:07:00.810> and<00:07:01.380> thus 00:07:01.850 --> 00:07:01.860 align:start position:0% table and submit multiple bits and thus 00:07:01.860 --> 00:07:07.670 align:start position:0% table and submit multiple bits and thus get<00:07:02.099> the<00:07:02.280> dynamic<00:07:02.819> arrays<00:07:03.150> in<00:07:03.419> there<00:07:03.659> and<00:07:06.680> what 00:07:07.670 --> 00:07:07.680 align:start position:0% get the dynamic arrays in there and what 00:07:07.680 --> 00:07:11.779 align:start position:0% get the dynamic arrays in there and what I<00:07:07.710> think<00:07:08.520> was<00:07:08.940> pretty<00:07:09.870> good<00:07:10.319> about<00:07:10.560> that<00:07:11.039> entry 00:07:11.779 --> 00:07:11.789 align:start position:0% I think was pretty good about that entry 00:07:11.789 --> 00:07:15.050 align:start position:0% I think was pretty good about that entry is<00:07:11.969> that<00:07:12.330> this<00:07:12.750> exploit<00:07:13.349> is<00:07:13.770> basically<00:07:14.610> not 00:07:15.050 --> 00:07:15.060 align:start position:0% is that this exploit is basically not 00:07:15.060 --> 00:07:17.450 align:start position:0% is that this exploit is basically not possible<00:07:15.779> to<00:07:16.020> exploit 00:07:17.450 --> 00:07:17.460 align:start position:0% possible to exploit 00:07:17.460 --> 00:07:21.200 align:start position:0% possible to exploit using<00:07:18.150> standard<00:07:18.810> tools<00:07:19.760> you<00:07:20.760> need<00:07:20.940> to 00:07:21.200 --> 00:07:21.210 align:start position:0% using standard tools you need to 00:07:21.210 --> 00:07:26.120 align:start position:0% using standard tools you need to generate<00:07:21.480> your<00:07:21.960> own<00:07:22.220> ABI<00:07:23.840> your<00:07:24.840> little<00:07:25.410> bytes 00:07:26.120 --> 00:07:26.130 align:start position:0% generate your own ABI your little bytes 00:07:26.130 --> 00:07:30.140 align:start position:0% generate your own ABI your little bytes of<00:07:26.310> data<00:07:27.260> in<00:07:28.260> order<00:07:28.530> to<00:07:28.650> exploit<00:07:28.920> this<00:07:29.190> and<00:07:29.580> I 00:07:30.140 --> 00:07:30.150 align:start position:0% of data in order to exploit this and I 00:07:30.150 --> 00:07:33.490 align:start position:0% of data in order to exploit this and I think<00:07:30.420> it<00:07:30.540> would<00:07:30.690> be<00:07:30.840> very<00:07:31.020> difficult<00:07:31.290> for 00:07:33.490 --> 00:07:33.500 align:start position:0% think it would be very difficult for 00:07:33.500 --> 00:07:36.980 align:start position:0% think it would be very difficult for solidity<00:07:34.580> contract<00:07:35.580> developer<00:07:36.210> or<00:07:36.420> auditor 00:07:36.980 --> 00:07:36.990 align:start position:0% solidity contract developer or auditor 00:07:36.990 --> 00:07:39.890 align:start position:0% solidity contract developer or auditor without<00:07:37.890> deep<00:07:38.280> insight<00:07:38.850> into<00:07:38.880> other<00:07:39.480> VM 00:07:39.890 --> 00:07:39.900 align:start position:0% without deep insight into other VM 00:07:39.900 --> 00:07:42.460 align:start position:0% without deep insight into other VM functions<00:07:40.470> to<00:07:40.740> actually<00:07:41.100> find<00:07:42.030> the 00:07:42.460 --> 00:07:42.470 align:start position:0% functions to actually find the 00:07:42.470 --> 00:07:48.440 align:start position:0% functions to actually find the vulnerability<00:07:45.830> so<00:07:46.880> first<00:07:47.880> of<00:07:48.000> all<00:07:48.090> in<00:07:48.330> a 00:07:48.440 --> 00:07:48.450 align:start position:0% vulnerability so first of all in a 00:07:48.450 --> 00:07:50.360 align:start position:0% vulnerability so first of all in a question<00:07:48.930> for<00:07:49.230> any<00:07:49.620> of<00:07:49.770> the<00:07:49.830> panelists<00:07:50.280> would 00:07:50.360 --> 00:07:50.370 align:start position:0% question for any of the panelists would 00:07:50.370 --> 00:07:53.350 align:start position:0% question for any of the panelists would like<00:07:50.520> to<00:07:50.670> answer<00:07:50.820> which<00:07:51.210> is<00:07:51.740> what<00:07:52.740> should 00:07:53.350 --> 00:07:53.360 align:start position:0% like to answer which is what should 00:07:53.360 --> 00:07:56.470 align:start position:0% like to answer which is what should smart<00:07:54.360> contract<00:07:54.840> auditors<00:07:55.290> be<00:07:55.530> looking<00:07:55.920> for 00:07:56.470 --> 00:07:56.480 align:start position:0% smart contract auditors be looking for 00:07:56.480 --> 00:07:59.450 align:start position:0% smart contract auditors be looking for in<00:07:57.480> order<00:07:57.690> to<00:07:57.810> try<00:07:58.200> and<00:07:58.410> to<00:07:58.590> take<00:07:58.830> these<00:07:59.040> sort 00:07:59.450 --> 00:07:59.460 align:start position:0% in order to try and to take these sort 00:07:59.460 --> 00:08:04.520 align:start position:0% in order to try and to take these sort of<00:07:59.550> underhanded<00:08:00.360> tricks<00:08:02.540> I<00:08:03.540> mean<00:08:04.080> and<00:08:04.230> I<00:08:04.350> think 00:08:04.520 --> 00:08:04.530 align:start position:0% of underhanded tricks I mean and I think 00:08:04.530 --> 00:08:06.950 align:start position:0% of underhanded tricks I mean and I think in<00:08:04.620> the<00:08:04.680> case<00:08:04.830> of<00:08:05.010> our<00:08:05.330> entries<00:08:06.330> if<00:08:06.660> you<00:08:06.750> see 00:08:06.950 --> 00:08:06.960 align:start position:0% in the case of our entries if you see 00:08:06.960 --> 00:08:08.720 align:start position:0% in the case of our entries if you see this<00:08:07.230> stop<00:08:07.530> balance<00:08:07.920> anywhere<00:08:08.250> it<00:08:08.460> should<00:08:08.640> be 00:08:08.720 --> 00:08:08.730 align:start position:0% this stop balance anywhere it should be 00:08:08.730 --> 00:08:10.400 align:start position:0% this stop balance anywhere it should be I<00:08:09.030> mean<00:08:09.210> this<00:08:09.420> means<00:08:09.660> wrong<00:08:09.930> but<00:08:10.290> it's 00:08:10.400 --> 00:08:10.410 align:start position:0% I mean this means wrong but it's 00:08:10.410 --> 00:08:12.860 align:start position:0% I mean this means wrong but it's certainly<00:08:10.650> a<00:08:10.710> red<00:08:10.950> flag<00:08:11.250> that<00:08:11.870> you're 00:08:12.860 --> 00:08:12.870 align:start position:0% certainly a red flag that you're 00:08:12.870 --> 00:08:15.650 align:start position:0% certainly a red flag that you're accessing<00:08:13.200> data<00:08:13.890> that<00:08:14.240> may<00:08:15.240> or<00:08:15.330> may<00:08:15.450> not<00:08:15.480> be 00:08:15.650 --> 00:08:15.660 align:start position:0% accessing data that may or may not be 00:08:15.660 --> 00:08:18.920 align:start position:0% accessing data that may or may not be what<00:08:15.780> you<00:08:15.870> expect<00:08:16.140> it<00:08:16.230> to<00:08:16.260> be<00:08:17.510> to<00:08:18.510> complement 00:08:18.920 --> 00:08:18.930 align:start position:0% what you expect it to be to complement 00:08:18.930 --> 00:08:21.770 align:start position:0% what you expect it to be to complement on<00:08:19.140> these<00:08:19.350> there<00:08:19.800> are<00:08:19.830> a<00:08:19.950> few<00:08:20.190> things<00:08:20.790> that<00:08:20.940> tip 00:08:21.770 --> 00:08:21.780 align:start position:0% on these there are a few things that tip 00:08:21.780 --> 00:08:24.320 align:start position:0% on these there are a few things that tip me<00:08:21.930> off<00:08:22.110> one<00:08:22.890> example<00:08:23.070> is<00:08:23.400> random<00:08:23.970> numbers 00:08:24.320 --> 00:08:24.330 align:start position:0% me off one example is random numbers 00:08:24.330 --> 00:08:27.290 align:start position:0% me off one example is random numbers because<00:08:25.260> it's<00:08:25.590> usually<00:08:25.950> pretty<00:08:26.520> hard<00:08:26.970> to 00:08:27.290 --> 00:08:27.300 align:start position:0% because it's usually pretty hard to 00:08:27.300 --> 00:08:30.620 align:start position:0% because it's usually pretty hard to generate<00:08:28.140> random<00:08:28.350> numbers<00:08:28.800> and<00:08:29.000> it<00:08:30.000> that<00:08:30.300> kind 00:08:30.620 --> 00:08:30.630 align:start position:0% generate random numbers and it that kind 00:08:30.630 --> 00:08:32.810 align:start position:0% generate random numbers and it that kind of<00:08:30.720> indicates<00:08:31.050> that<00:08:31.800> it's<00:08:32.370> a<00:08:32.520> point<00:08:32.730> of 00:08:32.810 --> 00:08:32.820 align:start position:0% of indicates that it's a point of 00:08:32.820 --> 00:08:39.590 align:start position:0% of indicates that it's a point of failure<00:08:36.800> external<00:08:37.800> calls<00:08:38.010> are<00:08:38.340> also<00:08:38.580> a<00:08:38.760> kind 00:08:39.590 --> 00:08:39.600 align:start position:0% failure external calls are also a kind 00:08:39.600 --> 00:08:44.540 align:start position:0% failure external calls are also a kind of<00:08:39.780> security<00:08:41.750> edge<00:08:42.750> because<00:08:43.440> you<00:08:43.890> know<00:08:44.250> you're 00:08:44.540 --> 00:08:44.550 align:start position:0% of security edge because you know you're 00:08:44.550 --> 00:08:46.370 align:start position:0% of security edge because you know you're calling<00:08:44.880> strong<00:08:45.210> external<00:08:45.570> contracts<00:08:46.170> so 00:08:46.370 --> 00:08:46.380 align:start position:0% calling strong external contracts so 00:08:46.380 --> 00:08:48.800 align:start position:0% calling strong external contracts so it's<00:08:47.070> the<00:08:47.340> thing<00:08:47.640> it's<00:08:47.970> the<00:08:48.330> kind<00:08:48.570> of<00:08:48.630> thing 00:08:48.800 --> 00:08:48.810 align:start position:0% it's the thing it's the kind of thing 00:08:48.810 --> 00:08:51.290 align:start position:0% it's the thing it's the kind of thing that<00:08:48.840> I<00:08:48.990> start<00:08:49.260> looking<00:08:49.620> after<00:08:49.920> when<00:08:50.850> I<00:08:50.880> start 00:08:51.290 --> 00:08:51.300 align:start position:0% that I start looking after when I start 00:08:51.300 --> 00:08:54.890 align:start position:0% that I start looking after when I start looking<00:08:51.690> at<00:08:51.870> a<00:08:51.900> contract<00:08:53.600> yeah<00:08:54.600> I<00:08:54.630> would<00:08:54.810> like 00:08:54.890 --> 00:08:54.900 align:start position:0% looking at a contract yeah I would like 00:08:54.900 --> 00:08:58.130 align:start position:0% looking at a contract yeah I would like to<00:08:55.050> add<00:08:55.170> to<00:08:55.200> that<00:08:55.320> that<00:08:56.210> what<00:08:57.210> you<00:08:57.330> really<00:08:57.600> kind 00:08:58.130 --> 00:08:58.140 align:start position:0% to add to that that what you really kind 00:08:58.140 --> 00:09:00.770 align:start position:0% to add to that that what you really kind of<00:08:58.230> should<00:08:59.130> be<00:08:59.160> looking<00:08:59.550> for<00:08:59.820> one<00:09:00.570> of<00:09:00.600> the 00:09:00.770 --> 00:09:00.780 align:start position:0% of should be looking for one of the 00:09:00.780 --> 00:09:04.490 align:start position:0% of should be looking for one of the things<00:09:00.900> is<00:09:01.310> are<00:09:02.310> these<00:09:02.490> assumptions<00:09:03.500> and 00:09:04.490 --> 00:09:04.500 align:start position:0% things is are these assumptions and 00:09:04.500 --> 00:09:07.130 align:start position:0% things is are these assumptions and they're<00:09:04.650> mainly<00:09:04.970> implicit<00:09:05.970> assumptions<00:09:06.840> that 00:09:07.130 --> 00:09:07.140 align:start position:0% they're mainly implicit assumptions that 00:09:07.140 --> 00:09:12.590 align:start position:0% they're mainly implicit assumptions that are<00:09:07.920> made<00:09:08.450> and<00:09:09.450> it's<00:09:09.840> easy<00:09:10.020> to<00:09:11.360> gloss<00:09:12.360> over 00:09:12.590 --> 00:09:12.600 align:start position:0% are made and it's easy to gloss over 00:09:12.600 --> 00:09:15.320 align:start position:0% are made and it's easy to gloss over that<00:09:12.870> and<00:09:13.200> not<00:09:13.320> notice<00:09:13.770> it<00:09:13.950> but<00:09:14.700> really<00:09:14.880> try<00:09:15.300> to 00:09:15.320 --> 00:09:15.330 align:start position:0% that and not notice it but really try to 00:09:15.330 --> 00:09:17.150 align:start position:0% that and not notice it but really try to investigate<00:09:16.200> where<00:09:16.410> are<00:09:16.560> the<00:09:16.710> implicit 00:09:17.150 --> 00:09:17.160 align:start position:0% investigate where are the implicit 00:09:17.160 --> 00:09:19.940 align:start position:0% investigate where are the implicit assumptions<00:09:17.910> here<00:09:18.150> and<00:09:18.330> in<00:09:18.750> your<00:09:19.170> cases<00:09:19.620> are 00:09:19.940 --> 00:09:19.950 align:start position:0% assumptions here and in your cases are 00:09:19.950 --> 00:09:22.870 align:start position:0% assumptions here and in your cases are just<00:09:20.190> the<00:09:20.310> implicit<00:09:20.520> assumption<00:09:21.180> is<00:09:21.300> that<00:09:21.330> the 00:09:22.870 --> 00:09:22.880 align:start position:0% just the implicit assumption is that the 00:09:22.880 --> 00:09:27.170 align:start position:0% just the implicit assumption is that the balance<00:09:23.880> is<00:09:24.120> zero<00:09:25.010> at<00:09:26.010> the<00:09:26.250> entry<00:09:26.640> or<00:09:26.760> at<00:09:27.000> the 00:09:27.170 --> 00:09:27.180 align:start position:0% balance is zero at the entry or at the 00:09:27.180 --> 00:09:33.080 align:start position:0% balance is zero at the entry or at the exit<00:09:27.600> and<00:09:28.790> start<00:09:29.790> to<00:09:30.000> like<00:09:31.790> make<00:09:32.790> these 00:09:33.080 --> 00:09:33.090 align:start position:0% exit and start to like make these 00:09:33.090 --> 00:09:37.040 align:start position:0% exit and start to like make these assumptions<00:09:33.600> explicit<00:09:34.560> and<00:09:35.060> then<00:09:36.060> see<00:09:36.600> can<00:09:37.020> I 00:09:37.040 --> 00:09:37.050 align:start position:0% assumptions explicit and then see can I 00:09:37.050 --> 00:09:41.240 align:start position:0% assumptions explicit and then see can I violate<00:09:37.680> this<00:09:37.890> assumption<00:09:39.560> in<00:09:40.560> any<00:09:40.920> way<00:09:41.070> shape 00:09:41.240 --> 00:09:41.250 align:start position:0% violate this assumption in any way shape 00:09:41.250 --> 00:09:44.060 align:start position:0% violate this assumption in any way shape or<00:09:41.400> form<00:09:41.460> and<00:09:42.420> just<00:09:43.140> to<00:09:43.230> add<00:09:43.350> my<00:09:43.500> own<00:09:43.620> note<00:09:43.830> do 00:09:44.060 --> 00:09:44.070 align:start position:0% or form and just to add my own note do 00:09:44.070 --> 00:09:47.840 align:start position:0% or form and just to add my own note do you<00:09:45.740> some<00:09:46.740> caution<00:09:47.100> is<00:09:47.190> required<00:09:47.220> there 00:09:47.840 --> 00:09:47.850 align:start position:0% you some caution is required there 00:09:47.850 --> 00:09:49.550 align:start position:0% you some caution is required there unless<00:09:48.210> if<00:09:48.420> you<00:09:48.570> made<00:09:48.930> the<00:09:49.050> assumption<00:09:49.530> that 00:09:49.550 --> 00:09:49.560 align:start position:0% unless if you made the assumption that 00:09:49.560 --> 00:09:51.470 align:start position:0% unless if you made the assumption that the<00:09:49.710> balance<00:09:50.070> is<00:09:50.250> zero<00:09:50.280> and<00:09:50.850> then<00:09:51.360> you've 00:09:51.470 --> 00:09:51.480 align:start position:0% the balance is zero and then you've 00:09:51.480 --> 00:09:53.600 align:start position:0% the balance is zero and then you've coded<00:09:51.750> in<00:09:52.020> an<00:09:52.140> assertion<00:09:52.470> the<00:09:53.160> balance<00:09:53.430> is 00:09:53.600 --> 00:09:53.610 align:start position:0% coded in an assertion the balance is 00:09:53.610 --> 00:09:55.640 align:start position:0% coded in an assertion the balance is zero<00:09:53.790> then<00:09:54.690> now<00:09:54.930> an<00:09:55.050> attacker<00:09:55.350> has<00:09:55.620> a 00:09:55.640 --> 00:09:55.650 align:start position:0% zero then now an attacker has a 00:09:55.650 --> 00:09:57.260 align:start position:0% zero then now an attacker has a mechanism<00:09:55.950> by<00:09:56.460> which<00:09:56.490> they<00:09:56.850> can<00:09:56.910> actually 00:09:57.260 --> 00:09:57.270 align:start position:0% mechanism by which they can actually 00:09:57.270 --> 00:09:59.060 align:start position:0% mechanism by which they can actually just<00:09:57.420> disable<00:09:57.900> your<00:09:57.990> contracts<00:09:58.470> by<00:09:58.740> sending 00:09:59.060 --> 00:09:59.070 align:start position:0% just disable your contracts by sending 00:09:59.070 --> 00:10:02.270 align:start position:0% just disable your contracts by sending someone's<00:09:59.400> to<00:09:59.610> it<00:09:59.760> exactly<00:10:00.360> so<00:10:00.870> so<00:10:01.290> I<00:10:01.320> I<00:10:01.740> didn't 00:10:02.270 --> 00:10:02.280 align:start position:0% someone's to it exactly so so I I didn't 00:10:02.280 --> 00:10:03.200 align:start position:0% someone's to it exactly so so I I didn't mean<00:10:02.370> that<00:10:02.490> you<00:10:02.550> should 00:10:03.200 --> 00:10:03.210 align:start position:0% mean that you should 00:10:03.210 --> 00:10:06.860 align:start position:0% mean that you should you<00:10:03.480> know<00:10:03.570> assert<00:10:04.410> that<00:10:05.240> thing<00:10:06.240> necessarily 00:10:06.860 --> 00:10:06.870 align:start position:0% you know assert that thing necessarily 00:10:06.870 --> 00:10:09.770 align:start position:0% you know assert that thing necessarily but<00:10:07.650> instead<00:10:08.070> question<00:10:09.030> is<00:10:09.150> this<00:10:09.300> the<00:10:09.450> valid 00:10:09.770 --> 00:10:09.780 align:start position:0% but instead question is this the valid 00:10:09.780 --> 00:10:14.090 align:start position:0% but instead question is this the valid assumption<00:10:11.300> that<00:10:12.300> can<00:10:12.570> be<00:10:12.780> made<00:10:12.990> or<00:10:13.680> can<00:10:13.980> this 00:10:14.090 --> 00:10:14.100 align:start position:0% assumption that can be made or can this 00:10:14.100 --> 00:10:19.370 align:start position:0% assumption that can be made or can this be<00:10:14.310> exploited<00:10:14.910> by<00:10:15.770> an<00:10:16.770> attacker<00:10:17.660> so<00:10:18.660> next 00:10:19.370 --> 00:10:19.380 align:start position:0% be exploited by an attacker so next 00:10:19.380 --> 00:10:22.250 align:start position:0% be exploited by an attacker so next question<00:10:19.560> again<00:10:20.040> for<00:10:20.250> any<00:10:20.370> of<00:10:20.520> you<00:10:20.670> is<00:10:21.260> what 00:10:22.250 --> 00:10:22.260 align:start position:0% question again for any of you is what 00:10:22.260 --> 00:10:23.570 align:start position:0% question again for any of you is what sort<00:10:22.500> of<00:10:22.560> improvements<00:10:22.860> would<00:10:23.190> you<00:10:23.280> like<00:10:23.430> to 00:10:23.570 --> 00:10:23.580 align:start position:0% sort of improvements would you like to 00:10:23.580 --> 00:10:26.000 align:start position:0% sort of improvements would you like to see<00:10:23.790> to<00:10:24.090> tolling<00:10:24.330> in<00:10:24.780> two<00:10:24.990> languages<00:10:25.470> and<00:10:25.800> and 00:10:26.000 --> 00:10:26.010 align:start position:0% see to tolling in two languages and and 00:10:26.010 --> 00:10:28.150 align:start position:0% see to tolling in two languages and and other<00:10:26.130> infrastructure<00:10:26.760> pieces<00:10:27.270> in<00:10:27.540> order<00:10:27.750> to 00:10:28.150 --> 00:10:28.160 align:start position:0% other infrastructure pieces in order to 00:10:28.160 --> 00:10:30.980 align:start position:0% other infrastructure pieces in order to make<00:10:29.160> it<00:10:29.310> easier<00:10:29.610> to<00:10:29.640> take<00:10:30.000> these<00:10:30.210> issues<00:10:30.600> and 00:10:30.980 --> 00:10:30.990 align:start position:0% make it easier to take these issues and 00:10:30.990 --> 00:10:34.310 align:start position:0% make it easier to take these issues and and<00:10:32.240> help<00:10:33.240> prevent<00:10:33.660> them<00:10:33.810> from<00:10:33.870> happening<00:10:34.200> in 00:10:34.310 --> 00:10:34.320 align:start position:0% and help prevent them from happening in 00:10:34.320 --> 00:10:38.090 align:start position:0% and help prevent them from happening in the<00:10:34.350> first<00:10:34.500> place<00:10:35.210> so<00:10:36.210> on<00:10:37.020> the<00:10:37.470> tooling<00:10:37.830> front 00:10:38.090 --> 00:10:38.100 align:start position:0% the first place so on the tooling front 00:10:38.100 --> 00:10:42.440 align:start position:0% the first place so on the tooling front I<00:10:38.480> was<00:10:39.480> at<00:10:39.660> the<00:10:40.130> she's<00:10:41.130> me<00:10:41.250> at<00:10:41.970> the<00:10:42.120> breakout 00:10:42.440 --> 00:10:42.450 align:start position:0% I was at the she's me at the breakout 00:10:42.450 --> 00:10:45.320 align:start position:0% I was at the she's me at the breakout session<00:10:43.010> earlier<00:10:44.010> and<00:10:44.190> saw<00:10:45.150> some 00:10:45.320 --> 00:10:45.330 align:start position:0% session earlier and saw some 00:10:45.330 --> 00:10:47.390 align:start position:0% session earlier and saw some presentation<00:10:45.840> about<00:10:45.930> a<00:10:46.290> Yenta<00:10:46.590> and<00:10:47.100> about 00:10:47.390 --> 00:10:47.400 align:start position:0% presentation about a Yenta and about 00:10:47.400 --> 00:10:51.350 align:start position:0% presentation about a Yenta and about sakura<00:10:47.940> phi<00:10:48.210> and<00:10:49.610> for<00:10:50.610> a<00:10:50.640> long<00:10:50.820> time<00:10:51.030> I've<00:10:51.270> had 00:10:51.350 --> 00:10:51.360 align:start position:0% sakura phi and for a long time I've had 00:10:51.360 --> 00:10:55.030 align:start position:0% sakura phi and for a long time I've had this<00:10:51.510> feeling<00:10:51.690> that<00:10:51.870> there<00:10:52.200> are<00:10:52.910> these<00:10:53.910> tools 00:10:55.030 --> 00:10:55.040 align:start position:0% this feeling that there are these tools 00:10:55.040 --> 00:11:00.970 align:start position:0% this feeling that there are these tools to<00:10:56.040> with<00:10:56.460> just<00:10:56.790> analysis<00:10:57.450> on<00:10:57.780> bytecode<00:10:58.560> and 00:11:00.970 --> 00:11:00.980 align:start position:0% 00:11:00.980 --> 00:11:04.330 align:start position:0% either<00:11:01.980> detects<00:11:02.760> vulnerabilities<00:11:03.570> or 00:11:04.330 --> 00:11:04.340 align:start position:0% either detects vulnerabilities or 00:11:04.340 --> 00:11:07.970 align:start position:0% either detects vulnerabilities or provides<00:11:05.340> some<00:11:05.880> kind<00:11:06.150> of<00:11:06.530> analysis<00:11:07.530> on<00:11:07.740> the 00:11:07.970 --> 00:11:07.980 align:start position:0% provides some kind of analysis on the 00:11:07.980 --> 00:11:10.940 align:start position:0% provides some kind of analysis on the bytecode<00:11:08.490> and<00:11:09.290> they're<00:11:10.290> on<00:11:10.440> the<00:11:10.590> kind<00:11:10.860> of 00:11:10.940 --> 00:11:10.950 align:start position:0% bytecode and they're on the kind of 00:11:10.950 --> 00:11:14.720 align:start position:0% bytecode and they're on the kind of fringes<00:11:11.520> but<00:11:12.060> they're<00:11:12.240> not<00:11:12.440> right<00:11:13.440> now<00:11:13.710> in<00:11:14.130> the 00:11:14.720 --> 00:11:14.730 align:start position:0% fringes but they're not right now in the 00:11:14.730 --> 00:11:17.690 align:start position:0% fringes but they're not right now in the in<00:11:15.000> the<00:11:15.300> tool<00:11:16.140> set<00:11:16.530> of<00:11:16.830> most<00:11:17.100> the<00:11:17.610> app 00:11:17.690 --> 00:11:17.700 align:start position:0% in the tool set of most the app 00:11:17.700 --> 00:11:19.340 align:start position:0% in the tool set of most the app developers<00:11:18.300> and<00:11:18.570> that's<00:11:18.750> what<00:11:19.050> I<00:11:19.080> think 00:11:19.340 --> 00:11:19.350 align:start position:0% developers and that's what I think 00:11:19.350 --> 00:11:21.920 align:start position:0% developers and that's what I think should<00:11:19.560> be<00:11:19.620> added<00:11:19.920> so<00:11:20.190> that<00:11:20.370> as<00:11:21.000> part<00:11:21.420> of<00:11:21.720> your 00:11:21.920 --> 00:11:21.930 align:start position:0% should be added so that as part of your 00:11:21.930 --> 00:11:24.110 align:start position:0% should be added so that as part of your development<00:11:22.170> process<00:11:22.500> you<00:11:23.340> can<00:11:23.520> get<00:11:23.700> some<00:11:23.910> aid 00:11:24.110 --> 00:11:24.120 align:start position:0% development process you can get some aid 00:11:24.120 --> 00:11:27.650 align:start position:0% development process you can get some aid by<00:11:25.050> these<00:11:25.350> tools<00:11:25.920> which<00:11:26.310> operates<00:11:26.850> preferably 00:11:27.650 --> 00:11:27.660 align:start position:0% by these tools which operates preferably 00:11:27.660 --> 00:11:31.400 align:start position:0% by these tools which operates preferably on<00:11:27.750> byte<00:11:28.170> code<00:11:28.500> which<00:11:28.860> would<00:11:29.010> also<00:11:29.250> help<00:11:30.410> to 00:11:31.400 --> 00:11:31.410 align:start position:0% on byte code which would also help to 00:11:31.410 --> 00:11:32.590 align:start position:0% on byte code which would also help to protect<00:11:31.590> against 00:11:32.590 --> 00:11:32.600 align:start position:0% protect against 00:11:32.600 --> 00:11:35.210 align:start position:0% protect against failures<00:11:33.600> and<00:11:34.140> better<00:11:34.380> within<00:11:34.620> the<00:11:34.800> solidity 00:11:35.210 --> 00:11:35.220 align:start position:0% failures and better within the solidity 00:11:35.220 --> 00:11:38.480 align:start position:0% failures and better within the solidity and<00:11:35.640> in<00:11:36.120> this<00:11:36.240> step<00:11:36.600> from<00:11:37.380> source<00:11:37.980> code<00:11:38.280> to 00:11:38.480 --> 00:11:38.490 align:start position:0% and in this step from source code to 00:11:38.490 --> 00:11:41.630 align:start position:0% and in this step from source code to byte<00:11:38.820> code 00:11:41.630 --> 00:11:41.640 align:start position:0% 00:11:41.640 --> 00:11:44.449 align:start position:0% all<00:11:42.000> right<00:11:42.120> so<00:11:42.450> you'd<00:11:43.320> say<00:11:43.560> more<00:11:43.800> maturity<00:11:44.130> and 00:11:44.449 --> 00:11:44.459 align:start position:0% all right so you'd say more maturity and 00:11:44.459 --> 00:11:46.130 align:start position:0% all right so you'd say more maturity and the<00:11:44.550> tools<00:11:44.760> were<00:11:44.940> already<00:11:45.089> building<00:11:45.540> and<00:11:45.930> an 00:11:46.130 --> 00:11:46.140 align:start position:0% the tools were already building and an 00:11:46.140 --> 00:11:48.889 align:start position:0% the tools were already building and an easier<00:11:46.560> integration<00:11:47.209> yes<00:11:48.209> in<00:11:48.510> zero 00:11:48.889 --> 00:11:48.899 align:start position:0% easier integration yes in zero 00:11:48.899 --> 00:11:52.460 align:start position:0% easier integration yes in zero integration<00:11:49.970> in<00:11:50.970> the<00:11:51.240> into<00:11:51.600> the<00:11:51.750> developer 00:11:52.460 --> 00:11:52.470 align:start position:0% integration in the into the developer 00:11:52.470 --> 00:11:56.060 align:start position:0% integration in the into the developer pipeline<00:11:52.890> of<00:11:53.250> these<00:11:54.029> tools<00:11:54.300> yeah<00:11:54.890> anyone<00:11:55.890> else 00:11:56.060 --> 00:11:56.070 align:start position:0% pipeline of these tools yeah anyone else 00:11:56.070 --> 00:11:59.329 align:start position:0% pipeline of these tools yeah anyone else I<00:11:56.339> mean<00:11:57.149> I<00:11:57.180> would<00:11:57.480> out<00:11:57.950> yeah<00:11:58.950> that's<00:11:59.250> basically 00:11:59.329 --> 00:11:59.339 align:start position:0% I mean I would out yeah that's basically 00:11:59.339 --> 00:12:01.340 align:start position:0% I mean I would out yeah that's basically why<00:11:59.579> I<00:11:59.610> say<00:11:59.790> like<00:11:59.940> it's<00:12:00.660> really<00:12:00.839> important<00:12:01.290> we 00:12:01.340 --> 00:12:01.350 align:start position:0% why I say like it's really important we 00:12:01.350 --> 00:12:02.960 align:start position:0% why I say like it's really important we have<00:12:01.440> better<00:12:01.649> testing<00:12:02.220> tools<00:12:02.459> as<00:12:02.640> well<00:12:02.730> like 00:12:02.960 --> 00:12:02.970 align:start position:0% have better testing tools as well like 00:12:02.970 --> 00:12:05.810 align:start position:0% have better testing tools as well like being<00:12:03.420> able<00:12:03.510> to<00:12:03.660> run<00:12:03.899> a<00:12:04.260> huge<00:12:05.250> suite<00:12:05.550> of<00:12:05.640> test 00:12:05.810 --> 00:12:05.820 align:start position:0% being able to run a huge suite of test 00:12:05.820 --> 00:12:08.960 align:start position:0% being able to run a huge suite of test cases<00:12:06.060> against<00:12:06.950> both<00:12:07.950> expected<00:12:08.490> behavior<00:12:08.820> and 00:12:08.960 --> 00:12:08.970 align:start position:0% cases against both expected behavior and 00:12:08.970 --> 00:12:10.759 align:start position:0% cases against both expected behavior and unexpected<00:12:09.420> behavior<00:12:09.750> if<00:12:09.899> you<00:12:09.959> feed<00:12:10.290> bad<00:12:10.529> data 00:12:10.759 --> 00:12:10.769 align:start position:0% unexpected behavior if you feed bad data 00:12:10.769 --> 00:12:13.519 align:start position:0% unexpected behavior if you feed bad data in<00:12:11.060> do<00:12:12.060> you<00:12:12.149> still<00:12:12.420> get<00:12:12.600> a<00:12:12.660> result<00:12:13.170> and<00:12:13.410> now 00:12:13.519 --> 00:12:13.529 align:start position:0% in do you still get a result and now 00:12:13.529 --> 00:12:15.019 align:start position:0% in do you still get a result and now you've<00:12:13.680> corrupted<00:12:13.920> something<00:12:14.459> or<00:12:14.730> like<00:12:14.970> I 00:12:15.019 --> 00:12:15.029 align:start position:0% you've corrupted something or like I 00:12:15.029 --> 00:12:17.870 align:start position:0% you've corrupted something or like I just<00:12:15.089> think<00:12:15.390> we<00:12:15.510> need<00:12:15.540> more<00:12:16.130> and<00:12:17.130> I<00:12:17.310> think<00:12:17.820> the 00:12:17.870 --> 00:12:17.880 align:start position:0% just think we need more and I think the 00:12:17.880 --> 00:12:18.949 align:start position:0% just think we need more and I think the tools<00:12:18.060> are<00:12:18.240> there<00:12:18.269> I<00:12:18.420> think<00:12:18.660> it's<00:12:18.779> just 00:12:18.949 --> 00:12:18.959 align:start position:0% tools are there I think it's just 00:12:18.959 --> 00:12:20.480 align:start position:0% tools are there I think it's just they're<00:12:19.140> not<00:12:19.290> easy<00:12:19.529> to<00:12:19.649> use<00:12:19.740> it's<00:12:20.010> not<00:12:20.040> easy<00:12:20.279> to 00:12:20.480 --> 00:12:20.490 align:start position:0% they're not easy to use it's not easy to 00:12:20.490 --> 00:12:22.699 align:start position:0% they're not easy to use it's not easy to make<00:12:20.820> a<00:12:20.880> test<00:12:21.750> we<00:12:21.870> can<00:12:21.959> just<00:12:22.140> run<00:12:22.320> through<00:12:22.500> them 00:12:22.699 --> 00:12:22.709 align:start position:0% make a test we can just run through them 00:12:22.709 --> 00:12:26.569 align:start position:0% make a test we can just run through them you<00:12:23.959> you<00:12:24.959> you<00:12:25.110> see<00:12:25.290> all<00:12:25.410> these<00:12:25.500> contracts<00:12:26.490> they 00:12:26.569 --> 00:12:26.579 align:start position:0% you you you see all these contracts they 00:12:26.579 --> 00:12:28.130 align:start position:0% you you you see all these contracts they have<00:12:26.670> about<00:12:26.760> three<00:12:27.060> test<00:12:27.240> cases<00:12:27.300> and<00:12:27.930> it's 00:12:28.130 --> 00:12:28.140 align:start position:0% have about three test cases and it's 00:12:28.140 --> 00:12:30.620 align:start position:0% have about three test cases and it's testing<00:12:28.500> if<00:12:28.800> I<00:12:29.220> send<00:12:29.430> money<00:12:29.550> to<00:12:29.640> this<00:12:29.820> not<00:12:30.450> like 00:12:30.620 --> 00:12:30.630 align:start position:0% testing if I send money to this not like 00:12:30.630 --> 00:12:33.470 align:start position:0% testing if I send money to this not like this<00:12:30.870> thing<00:12:31.680> doesn't<00:12:32.100> work<00:12:32.310> yes<00:12:32.700> passed<00:12:33.180> and 00:12:33.470 --> 00:12:33.480 align:start position:0% this thing doesn't work yes passed and 00:12:33.480 --> 00:12:35.210 align:start position:0% this thing doesn't work yes passed and so<00:12:33.959> three<00:12:34.200> test<00:12:34.350> cases<00:12:34.410> this<00:12:34.829> should<00:12:34.980> not<00:12:35.160> be 00:12:35.210 --> 00:12:35.220 align:start position:0% so three test cases this should not be 00:12:35.220 --> 00:12:38.420 align:start position:0% so three test cases this should not be sufficient<00:12:35.850> to<00:12:37.130> validate<00:12:38.130> that<00:12:38.310> this 00:12:38.420 --> 00:12:38.430 align:start position:0% sufficient to validate that this 00:12:38.430 --> 00:12:39.530 align:start position:0% sufficient to validate that this contract<00:12:38.760> you're<00:12:39.000> sending<00:12:39.180> billions<00:12:39.360> of 00:12:39.530 --> 00:12:39.540 align:start position:0% contract you're sending billions of 00:12:39.540 --> 00:12:45.220 align:start position:0% contract you're sending billions of dollars<00:12:39.779> to<00:12:39.930> is<00:12:40.079> is<00:12:40.380> working<00:12:40.860> and<00:12:43.190> yeah<00:12:44.190> it's<00:12:44.820> a 00:12:45.220 --> 00:12:45.230 align:start position:0% dollars to is is working and yeah it's a 00:12:45.230 --> 00:12:48.290 align:start position:0% dollars to is is working and yeah it's a and<00:12:46.230> just<00:12:46.620> in<00:12:46.890> addition<00:12:47.370> to<00:12:47.730> that<00:12:47.880> I<00:12:48.120> would 00:12:48.290 --> 00:12:48.300 align:start position:0% and just in addition to that I would 00:12:48.300 --> 00:12:51.439 align:start position:0% and just in addition to that I would like<00:12:48.449> to<00:12:48.660> see<00:12:48.899> some<00:12:49.649> way<00:12:49.800> to<00:12:49.860> test<00:12:50.459> in<00:12:51.180> large 00:12:51.439 --> 00:12:51.449 align:start position:0% like to see some way to test in large 00:12:51.449 --> 00:12:53.930 align:start position:0% like to see some way to test in large scale<00:12:51.779> because<00:12:52.500> most<00:12:52.920> projects<00:12:53.610> when<00:12:53.760> it 00:12:53.930 --> 00:12:53.940 align:start position:0% scale because most projects when it 00:12:53.940 --> 00:12:56.000 align:start position:0% scale because most projects when it tests<00:12:54.180> some<00:12:54.420> behavior<00:12:54.899> they<00:12:55.470> used<00:12:55.680> like<00:12:55.860> the 00:12:56.000 --> 00:12:56.010 align:start position:0% tests some behavior they used like the 00:12:56.010 --> 00:12:58.970 align:start position:0% tests some behavior they used like the minimum<00:12:56.430> the<00:12:56.790> viable<00:12:57.600> number<00:12:58.260> of<00:12:58.410> players<00:12:58.680> in 00:12:58.970 --> 00:12:58.980 align:start position:0% minimum the viable number of players in 00:12:58.980 --> 00:13:01.699 align:start position:0% minimum the viable number of players in the<00:12:59.070> contract<00:12:59.579> to<00:13:00.120> test<00:13:00.360> but<00:13:00.630> if<00:13:01.110> a<00:13:01.320> contract 00:13:01.699 --> 00:13:01.709 align:start position:0% the contract to test but if a contract 00:13:01.709 --> 00:13:03.560 align:start position:0% the contract to test but if a contract work<00:13:01.890> like<00:13:02.160> with<00:13:02.339> ten<00:13:02.610> transactions<00:13:03.209> will<00:13:03.420> it 00:13:03.560 --> 00:13:03.570 align:start position:0% work like with ten transactions will it 00:13:03.570 --> 00:13:05.960 align:start position:0% work like with ten transactions will it work<00:13:03.720> with<00:13:03.779> ten<00:13:04.290> thousand<00:13:04.769> or<00:13:04.920> a<00:13:05.339> million<00:13:05.640> and 00:13:05.960 --> 00:13:05.970 align:start position:0% work with ten thousand or a million and 00:13:05.970 --> 00:13:08.449 align:start position:0% work with ten thousand or a million and there's<00:13:06.630> no<00:13:06.750> H<00:13:06.899> test<00:13:07.230> that<00:13:07.470> there<00:13:08.130> is<00:13:08.250> but 00:13:08.449 --> 00:13:08.459 align:start position:0% there's no H test that there is but 00:13:08.459 --> 00:13:11.269 align:start position:0% there's no H test that there is but there<00:13:08.940> is<00:13:09.029> no<00:13:09.180> no<00:13:09.600> one<00:13:09.779> doing<00:13:10.560> that<00:13:10.769> right<00:13:10.920> now 00:13:11.269 --> 00:13:11.279 align:start position:0% there is no no one doing that right now 00:13:11.279 --> 00:13:14.600 align:start position:0% there is no no one doing that right now so<00:13:11.579> I<00:13:11.610> would<00:13:11.940> like<00:13:12.060> to<00:13:12.240> see<00:13:12.449> some<00:13:12.750> some<00:13:13.529> work<00:13:14.430> on 00:13:14.600 --> 00:13:14.610 align:start position:0% so I would like to see some some work on 00:13:14.610 --> 00:13:18.199 align:start position:0% so I would like to see some some work on that<00:13:15.320> alright<00:13:16.320> and<00:13:16.680> if<00:13:17.310> you<00:13:17.519> each<00:13:17.670> could<00:13:18.000> give 00:13:18.199 --> 00:13:18.209 align:start position:0% that alright and if you each could give 00:13:18.209 --> 00:13:20.870 align:start position:0% that alright and if you each could give one<00:13:19.050> piece<00:13:19.079> of<00:13:19.320> advice<00:13:19.500> to<00:13:20.070> somebody<00:13:20.550> writing 00:13:20.870 --> 00:13:20.880 align:start position:0% one piece of advice to somebody writing 00:13:20.880 --> 00:13:23.420 align:start position:0% one piece of advice to somebody writing a<00:13:21.029> smart<00:13:21.300> contract<00:13:21.510> on<00:13:22.250> something<00:13:23.250> to<00:13:23.339> look 00:13:23.420 --> 00:13:23.430 align:start position:0% a smart contract on something to look 00:13:23.430 --> 00:13:25.009 align:start position:0% a smart contract on something to look out<00:13:23.610> for<00:13:23.850> or<00:13:24.089> something<00:13:24.390> to<00:13:24.480> be<00:13:24.570> careful<00:13:24.839> about 00:13:25.009 --> 00:13:25.019 align:start position:0% out for or something to be careful about 00:13:25.019 --> 00:13:31.550 align:start position:0% out for or something to be careful about what<00:13:25.290> would<00:13:25.440> it<00:13:25.529> be<00:13:28.040> I<00:13:29.040> would<00:13:29.699> I<00:13:29.910> would<00:13:30.529> give<00:13:31.529> a 00:13:31.550 --> 00:13:31.560 align:start position:0% what would it be I would I would give a 00:13:31.560 --> 00:13:33.800 align:start position:0% what would it be I would I would give a device<00:13:31.860> that<00:13:32.130> sometimes<00:13:32.699> the<00:13:32.970> code<00:13:33.240> work<00:13:33.570> has 00:13:33.800 --> 00:13:33.810 align:start position:0% device that sometimes the code work has 00:13:33.810 --> 00:13:36.980 align:start position:0% device that sometimes the code work has intended<00:13:34.399> but<00:13:35.399> they<00:13:35.670> make<00:13:35.940> mechanisms<00:13:36.839> behind 00:13:36.980 --> 00:13:36.990 align:start position:0% intended but they make mechanisms behind 00:13:36.990 --> 00:13:40.490 align:start position:0% intended but they make mechanisms behind it<00:13:37.470> or<00:13:37.800> not<00:13:38.310> so<00:13:39.079> sometimes<00:13:40.079> it's<00:13:40.260> not<00:13:40.320> about 00:13:40.490 --> 00:13:40.500 align:start position:0% it or not so sometimes it's not about 00:13:40.500 --> 00:13:42.230 align:start position:0% it or not so sometimes it's not about the<00:13:40.709> codes<00:13:40.949> about<00:13:41.130> the<00:13:41.399> way<00:13:41.519> you<00:13:41.579> design<00:13:42.060> your 00:13:42.230 --> 00:13:42.240 align:start position:0% the codes about the way you design your 00:13:42.240 --> 00:13:44.240 align:start position:0% the codes about the way you design your contracts<00:13:42.779> about<00:13:42.959> how<00:13:43.320> we<00:13:43.380> interact<00:13:43.860> people 00:13:44.240 --> 00:13:44.250 align:start position:0% contracts about how we interact people 00:13:44.250 --> 00:13:46.340 align:start position:0% contracts about how we interact people interact<00:13:44.670> you<00:13:45.269> don't<00:13:45.480> consider<00:13:45.810> that<00:13:45.959> that 00:13:46.340 --> 00:13:46.350 align:start position:0% interact you don't consider that that 00:13:46.350 --> 00:13:48.610 align:start position:0% interact you don't consider that that might<00:13:46.709> be<00:13:46.740> a<00:13:46.860> malicious<00:13:47.310> player 00:13:48.610 --> 00:13:48.620 align:start position:0% might be a malicious player 00:13:48.620 --> 00:13:51.040 align:start position:0% might be a malicious player interacting<00:13:49.490> with<00:13:49.520> it<00:13:49.910> that<00:13:50.150> someone<00:13:50.390> is<00:13:50.690> like 00:13:51.040 --> 00:13:51.050 align:start position:0% interacting with it that someone is like 00:13:51.050 --> 00:13:54.790 align:start position:0% interacting with it that someone is like no<00:13:51.470> bad<00:13:51.650> behavior<00:13:52.190> and<00:13:52.690> it's<00:13:53.690> kind<00:13:54.290> of<00:13:54.380> easy<00:13:54.650> to 00:13:54.790 --> 00:13:54.800 align:start position:0% no bad behavior and it's kind of easy to 00:13:54.800 --> 00:13:57.790 align:start position:0% no bad behavior and it's kind of easy to oversee<00:13:55.490> that<00:13:55.790> and<00:13:56.090> just<00:13:56.720> like<00:13:57.290> because<00:13:57.680> it 00:13:57.790 --> 00:13:57.800 align:start position:0% oversee that and just like because it 00:13:57.800 --> 00:14:00.460 align:start position:0% oversee that and just like because it passes<00:13:58.190> the<00:13:58.310> test<00:13:58.520> it<00:13:58.940> works<00:13:59.270> but<00:14:00.080> you<00:14:00.170> have<00:14:00.320> to 00:14:00.460 --> 00:14:00.470 align:start position:0% passes the test it works but you have to 00:14:00.470 --> 00:14:03.970 align:start position:0% passes the test it works but you have to account<00:14:00.710> for<00:14:00.890> like<00:14:01.340> bad<00:14:01.700> people<00:14:01.730> right<00:14:02.950> now<00:14:03.950> I 00:14:03.970 --> 00:14:03.980 align:start position:0% account for like bad people right now I 00:14:03.980 --> 00:14:06.010 align:start position:0% account for like bad people right now I again<00:14:04.700> will<00:14:04.910> just<00:14:05.089> mimic<00:14:05.330> the<00:14:05.450> same<00:14:05.570> thing<00:14:05.870> I 00:14:06.010 --> 00:14:06.020 align:start position:0% again will just mimic the same thing I 00:14:06.020 --> 00:14:07.900 align:start position:0% again will just mimic the same thing I mean<00:14:06.290> formal<00:14:06.800> verification<00:14:06.950> everyone<00:14:07.640> thinks 00:14:07.900 --> 00:14:07.910 align:start position:0% mean formal verification everyone thinks 00:14:07.910 --> 00:14:09.550 align:start position:0% mean formal verification everyone thinks is<00:14:08.000> this<00:14:08.120> magic<00:14:08.450> bullet<00:14:08.750> but<00:14:08.779> there's<00:14:09.170> still<00:14:09.350> a 00:14:09.550 --> 00:14:09.560 align:start position:0% is this magic bullet but there's still a 00:14:09.560 --> 00:14:10.870 align:start position:0% is this magic bullet but there's still a gun<00:14:09.800> the<00:14:10.040> game<00:14:10.190> here<00:14:10.460> you<00:14:10.490> have<00:14:10.640> to<00:14:10.700> think 00:14:10.870 --> 00:14:10.880 align:start position:0% gun the game here you have to think 00:14:10.880 --> 00:14:12.610 align:start position:0% gun the game here you have to think about<00:14:10.970> I<00:14:11.300> mean<00:14:11.390> we've<00:14:12.020> heard<00:14:12.170> about<00:14:12.320> minor 00:14:12.610 --> 00:14:12.620 align:start position:0% about I mean we've heard about minor 00:14:12.620 --> 00:14:14.320 align:start position:0% about I mean we've heard about minor front-running<00:14:13.160> this<00:14:13.490> is<00:14:13.610> a<00:14:13.640> great<00:14:13.850> example<00:14:14.270> of 00:14:14.320 --> 00:14:14.330 align:start position:0% front-running this is a great example of 00:14:14.330 --> 00:14:16.960 align:start position:0% front-running this is a great example of the<00:14:14.450> type<00:14:14.630> of<00:14:14.660> things<00:14:15.020> that<00:14:15.580> the<00:14:16.580> code<00:14:16.790> is 00:14:16.960 --> 00:14:16.970 align:start position:0% the type of things that the code is 00:14:16.970 --> 00:14:18.220 align:start position:0% the type of things that the code is doing<00:14:17.060> exactly<00:14:17.570> what<00:14:17.630> you<00:14:17.779> expected<00:14:18.020> to<00:14:18.110> do 00:14:18.220 --> 00:14:18.230 align:start position:0% doing exactly what you expected to do 00:14:18.230 --> 00:14:20.410 align:start position:0% doing exactly what you expected to do there's<00:14:18.589> nothing<00:14:19.160> being<00:14:19.370> lied<00:14:19.640> about<00:14:19.670> about 00:14:20.410 --> 00:14:20.420 align:start position:0% there's nothing being lied about about 00:14:20.420 --> 00:14:22.980 align:start position:0% there's nothing being lied about about what's<00:14:20.600> happening<00:14:21.140> is<00:14:21.290> just<00:14:21.320> people<00:14:21.830> who<00:14:22.130> have 00:14:22.980 --> 00:14:22.990 align:start position:0% what's happening is just people who have 00:14:22.990 --> 00:14:26.230 align:start position:0% what's happening is just people who have weird<00:14:24.640> connections<00:14:25.640> to<00:14:25.850> what's<00:14:26.000> going<00:14:26.150> to 00:14:26.230 --> 00:14:26.240 align:start position:0% weird connections to what's going to 00:14:26.240 --> 00:14:28.960 align:start position:0% weird connections to what's going to happen<00:14:26.630> have<00:14:26.870> too<00:14:27.200> much<00:14:27.290> say<00:14:27.529> and<00:14:27.830> can<00:14:28.430> tweak 00:14:28.960 --> 00:14:28.970 align:start position:0% happen have too much say and can tweak 00:14:28.970 --> 00:14:32.140 align:start position:0% happen have too much say and can tweak what<00:14:29.240> you<00:14:29.630> expected<00:14:30.050> to<00:14:30.730> game<00:14:31.730> theoretically 00:14:32.140 --> 00:14:32.150 align:start position:0% what you expected to game theoretically 00:14:32.150 --> 00:14:37.300 align:start position:0% what you expected to game theoretically or<00:14:32.330> mechanism<00:14:32.839> design<00:14:33.080> wise<00:14:33.290> work<00:14:35.800> yes<00:14:36.800> my<00:14:37.040> top 00:14:37.300 --> 00:14:37.310 align:start position:0% or mechanism design wise work yes my top 00:14:37.310 --> 00:14:40.300 align:start position:0% or mechanism design wise work yes my top recommendations<00:14:38.150> would<00:14:38.360> be<00:14:38.510> no<00:14:39.260> the<00:14:39.529> EVM<00:14:40.010> in 00:14:40.300 --> 00:14:40.310 align:start position:0% recommendations would be no the EVM in 00:14:40.310 --> 00:14:44.200 align:start position:0% recommendations would be no the EVM in detail<00:14:40.880> and<00:14:41.680> keep<00:14:42.680> it<00:14:42.860> simple<00:14:43.490> don't<00:14:43.940> build 00:14:44.200 --> 00:14:44.210 align:start position:0% detail and keep it simple don't build 00:14:44.210 --> 00:14:47.110 align:start position:0% detail and keep it simple don't build like<00:14:44.480> very<00:14:45.020> large<00:14:45.350> inheritance<00:14:46.120> models 00:14:47.110 --> 00:14:47.120 align:start position:0% like very large inheritance models 00:14:47.120 --> 00:14:49.450 align:start position:0% like very large inheritance models because<00:14:47.510> it<00:14:47.810> just<00:14:48.020> try<00:14:48.710> to<00:14:48.770> keep<00:14:48.980> it<00:14:49.100> simple 00:14:49.450 --> 00:14:49.460 align:start position:0% because it just try to keep it simple 00:14:49.460 --> 00:14:56.829 align:start position:0% because it just try to keep it simple and<00:14:49.490> much<00:14:49.700> easier<00:14:50.060> to<00:14:50.480> audit<00:14:55.570> last<00:14:56.570> one 00:14:56.829 --> 00:14:56.839 align:start position:0% and much easier to audit last one 00:14:56.839 --> 00:15:01.360 align:start position:0% and much easier to audit last one dropped<00:14:57.080> out<00:14:57.520> all<00:14:58.520> right<00:14:59.140> so<00:15:00.140> I'd<00:15:00.470> like<00:15:00.650> to<00:15:00.890> see 00:15:01.360 --> 00:15:01.370 align:start position:0% dropped out all right so I'd like to see 00:15:01.370 --> 00:15:02.770 align:start position:0% dropped out all right so I'd like to see are<00:15:01.940> there<00:15:02.089> questions<00:15:02.210> from<00:15:02.510> the<00:15:02.690> audience 00:15:02.770 --> 00:15:02.780 align:start position:0% are there questions from the audience 00:15:02.780 --> 00:15:05.560 align:start position:0% are there questions from the audience for<00:15:03.200> the<00:15:03.290> panelists<00:15:03.820> if<00:15:04.820> you<00:15:05.060> raise<00:15:05.360> your<00:15:05.390> hand 00:15:05.560 --> 00:15:05.570 align:start position:0% for the panelists if you raise your hand 00:15:05.570 --> 00:15:06.910 align:start position:0% for the panelists if you raise your hand and<00:15:05.870> shout<00:15:06.050> it<00:15:06.170> out<00:15:06.290> I'll<00:15:06.530> repeat<00:15:06.800> the 00:15:06.910 --> 00:15:06.920 align:start position:0% and shout it out I'll repeat the 00:15:06.920 --> 00:15:13.330 align:start position:0% and shout it out I'll repeat the questions<00:15:07.339> who've<00:15:07.550> Rankin<00:15:07.880> here 00:15:13.330 --> 00:15:13.340 align:start position:0% 00:15:13.340 --> 00:15:15.950 align:start position:0% nobody<00:15:14.340> has<00:15:14.460> any<00:15:14.640> questions<00:15:15.180> about<00:15:15.450> smart 00:15:15.950 --> 00:15:15.960 align:start position:0% nobody has any questions about smart 00:15:15.960 --> 00:15:30.300 align:start position:0% nobody has any questions about smart contract<00:15:16.320> security<00:15:16.650> okay 00:15:30.300 --> 00:15:30.310 align:start position:0% 00:15:30.310 --> 00:15:33.970 align:start position:0% hi<00:15:31.310> I've<00:15:31.940> seen<00:15:32.210> like<00:15:32.330> it<00:15:32.540> many<00:15:33.110> companies<00:15:33.560> or 00:15:33.970 --> 00:15:33.980 align:start position:0% hi I've seen like it many companies or 00:15:33.980 --> 00:15:36.630 align:start position:0% hi I've seen like it many companies or individuals<00:15:34.190> does<00:15:34.760> like<00:15:35.029> code<00:15:35.510> auditing<00:15:35.990> but 00:15:36.630 --> 00:15:36.640 align:start position:0% individuals does like code auditing but 00:15:36.640 --> 00:15:41.079 align:start position:0% individuals does like code auditing but there's<00:15:37.640> no<00:15:37.820> much<00:15:38.290> standard<00:15:39.290> if<00:15:39.860> you<00:15:40.279> want<00:15:40.940> to 00:15:41.079 --> 00:15:41.089 align:start position:0% there's no much standard if you want to 00:15:41.089 --> 00:15:42.790 align:start position:0% there's no much standard if you want to say<00:15:41.270> like<00:15:41.420> if<00:15:41.630> we're<00:15:41.930> gonna<00:15:42.350> have<00:15:42.560> a<00:15:42.589> code 00:15:42.790 --> 00:15:42.800 align:start position:0% say like if we're gonna have a code 00:15:42.800 --> 00:15:44.650 align:start position:0% say like if we're gonna have a code auditing<00:15:43.220> standard<00:15:43.610> or<00:15:43.700> something<00:15:44.000> what<00:15:44.450> kind 00:15:44.650 --> 00:15:44.660 align:start position:0% auditing standard or something what kind 00:15:44.660 --> 00:15:47.670 align:start position:0% auditing standard or something what kind of<00:15:44.810> stuff<00:15:45.080> should<00:15:45.350> be<00:15:45.380> understand<00:15:46.190> our<00:15:46.310> list 00:15:47.670 --> 00:15:47.680 align:start position:0% of stuff should be understand our list 00:15:47.680 --> 00:15:50.350 align:start position:0% of stuff should be understand our list so<00:15:48.680> effectively<00:15:49.100> you're<00:15:49.400> asking<00:15:49.880> how<00:15:50.300> would 00:15:50.350 --> 00:15:50.360 align:start position:0% so effectively you're asking how would 00:15:50.360 --> 00:15:52.329 align:start position:0% so effectively you're asking how would you<00:15:50.570> recommend<00:15:50.870> people<00:15:51.290> go<00:15:51.620> about<00:15:51.890> auditing 00:15:52.329 --> 00:15:52.339 align:start position:0% you recommend people go about auditing 00:15:52.339 --> 00:15:54.579 align:start position:0% you recommend people go about auditing code<00:15:52.640> is<00:15:52.850> there<00:15:53.060> is<00:15:53.600> there<00:15:53.779> best<00:15:54.020> practice<00:15:54.410> for 00:15:54.579 --> 00:15:54.589 align:start position:0% code is there is there best practice for 00:15:54.589 --> 00:16:00.430 align:start position:0% code is there is there best practice for that<00:15:54.680> is<00:15:54.980> that<00:15:55.100> right<00:15:58.210> yes<00:15:59.210> best<00:15:59.990> practices 00:16:00.430 --> 00:16:00.440 align:start position:0% that is that right yes best practices 00:16:00.440 --> 00:16:04.120 align:start position:0% that is that right yes best practices for<00:16:00.650> auditors<00:16:01.040> and<00:16:01.339> audits<00:16:02.830> so<00:16:03.830> I'll<00:16:03.920> say 00:16:04.120 --> 00:16:04.130 align:start position:0% for auditors and audits so I'll say 00:16:04.130 --> 00:16:05.710 align:start position:0% for auditors and audits so I'll say there's<00:16:04.400> been<00:16:04.520> some<00:16:05.060> work<00:16:05.240> in<00:16:05.420> that<00:16:05.450> direction 00:16:05.710 --> 00:16:05.720 align:start position:0% there's been some work in that direction 00:16:05.720 --> 00:16:08.650 align:start position:0% there's been some work in that direction I<00:16:06.260> think<00:16:06.529> mainly<00:16:06.860> done<00:16:07.490> by<00:16:07.640> consensus<00:16:08.270> they've 00:16:08.650 --> 00:16:08.660 align:start position:0% I think mainly done by consensus they've 00:16:08.660 --> 00:16:13.660 align:start position:0% I think mainly done by consensus they've put<00:16:08.960> together<00:16:09.050> a<00:16:09.820> best<00:16:10.820> practices<00:16:11.390> guide<00:16:12.670> but 00:16:13.660 --> 00:16:13.670 align:start position:0% put together a best practices guide but 00:16:13.670 --> 00:16:18.070 align:start position:0% put together a best practices guide but as<00:16:13.790> I<00:16:14.089> mean<00:16:14.690> in<00:16:14.810> general<00:16:15.730> it's<00:16:16.730> the<00:16:17.510> field<00:16:17.810> is 00:16:18.070 --> 00:16:18.080 align:start position:0% as I mean in general it's the field is 00:16:18.080 --> 00:16:21.850 align:start position:0% as I mean in general it's the field is not<00:16:18.410> yet<00:16:18.680> mature<00:16:19.630> it's<00:16:20.630> taken<00:16:21.110> a<00:16:21.200> lot<00:16:21.410> of<00:16:21.440> years 00:16:21.850 --> 00:16:21.860 align:start position:0% not yet mature it's taken a lot of years 00:16:21.860 --> 00:16:25.180 align:start position:0% not yet mature it's taken a lot of years to<00:16:22.220> even<00:16:22.490> get<00:16:22.940> kind<00:16:23.839> of<00:16:23.870> like<00:16:24.050> rough<00:16:24.410> web 00:16:25.180 --> 00:16:25.190 align:start position:0% to even get kind of like rough web 00:16:25.190 --> 00:16:29.110 align:start position:0% to even get kind of like rough web application<00:16:26.000> security<00:16:26.330> guidelines<00:16:28.120> going 00:16:29.110 --> 00:16:29.120 align:start position:0% application security guidelines going 00:16:29.120 --> 00:16:31.090 align:start position:0% application security guidelines going and<00:16:29.390> still<00:16:29.839> evolving<00:16:30.290> and<00:16:30.470> it's<00:16:30.740> the<00:16:30.890> same 00:16:31.090 --> 00:16:31.100 align:start position:0% and still evolving and it's the same 00:16:31.100 --> 00:16:36.940 align:start position:0% and still evolving and it's the same thing<00:16:31.130> here<00:16:32.890> new<00:16:33.890> things<00:16:34.190> get<00:16:34.520> added<00:16:34.940> as<00:16:35.950> hacks 00:16:36.940 --> 00:16:36.950 align:start position:0% thing here new things get added as hacks 00:16:36.950 --> 00:16:43.660 align:start position:0% thing here new things get added as hacks happen<00:16:40.029> so<00:16:41.029> yeah<00:16:41.570> there's<00:16:42.200> I<00:16:42.589> don't<00:16:42.709> know<00:16:42.980> it's 00:16:43.660 --> 00:16:43.670 align:start position:0% happen so yeah there's I don't know it's 00:16:43.670 --> 00:16:46.449 align:start position:0% happen so yeah there's I don't know it's it's<00:16:44.000> going<00:16:44.209> to<00:16:44.330> continue<00:16:44.720> to<00:16:45.080> evolve<00:16:45.459> there 00:16:46.449 --> 00:16:46.459 align:start position:0% it's going to continue to evolve there 00:16:46.459 --> 00:16:49.030 align:start position:0% it's going to continue to evolve there is<00:16:46.610> one<00:16:46.880> but<00:16:47.330> it's<00:16:47.480> not<00:16:47.660> it's<00:16:48.529> not<00:16:48.680> all 00:16:49.030 --> 00:16:49.040 align:start position:0% is one but it's not it's not all 00:16:49.040 --> 00:16:54.040 align:start position:0% is one but it's not it's not all complete<00:16:49.959> one<00:16:50.959> other<00:16:51.110> thing<00:16:51.290> I<00:16:52.810> agree<00:16:53.810> we<00:16:53.930> need 00:16:54.040 --> 00:16:54.050 align:start position:0% complete one other thing I agree we need 00:16:54.050 --> 00:16:55.510 align:start position:0% complete one other thing I agree we need something<00:16:54.410> like<00:16:54.560> that<00:16:54.740> we<00:16:54.830> also<00:16:54.950> need<00:16:55.160> some<00:16:55.339> I 00:16:55.510 --> 00:16:55.520 align:start position:0% something like that we also need some I 00:16:55.520 --> 00:16:57.519 align:start position:0% something like that we also need some I would<00:16:56.000> like<00:16:56.089> the<00:16:56.150> idea<00:16:56.209> that<00:16:56.390> auditing<00:16:57.260> should 00:16:57.519 --> 00:16:57.529 align:start position:0% would like the idea that auditing should 00:16:57.529 --> 00:17:00.940 align:start position:0% would like the idea that auditing should be<00:16:57.650> a<00:16:57.940> fairly<00:16:58.940> public<00:16:59.420> type<00:16:59.959> thing<00:17:00.230> I've<00:17:00.620> done 00:17:00.940 --> 00:17:00.950 align:start position:0% be a fairly public type thing I've done 00:17:00.950 --> 00:17:02.920 align:start position:0% be a fairly public type thing I've done many<00:17:01.100> audits<00:17:01.339> and<00:17:01.700> often<00:17:02.540> times<00:17:02.750> I'll<00:17:02.900> say 00:17:02.920 --> 00:17:02.930 align:start position:0% many audits and often times I'll say 00:17:02.930 --> 00:17:06.850 align:start position:0% many audits and often times I'll say like<00:17:03.200> oh<00:17:03.350> well<00:17:03.560> your<00:17:04.059> your<00:17:05.260> can<00:17:06.260> be<00:17:06.350> exploited 00:17:06.850 --> 00:17:06.860 align:start position:0% like oh well your your can be exploited 00:17:06.860 --> 00:17:09.429 align:start position:0% like oh well your your can be exploited if<00:17:07.069> this<00:17:07.640> character<00:17:08.150> who<00:17:08.510> owns<00:17:08.720> this<00:17:08.990> address 00:17:09.429 --> 00:17:09.439 align:start position:0% if this character who owns this address 00:17:09.439 --> 00:17:11.260 align:start position:0% if this character who owns this address does<00:17:09.679> this<00:17:09.829> thing<00:17:10.069> and<00:17:10.370> often<00:17:10.939> I<00:17:10.970> hear<00:17:11.120> there's 00:17:11.260 --> 00:17:11.270 align:start position:0% does this thing and often I hear there's 00:17:11.270 --> 00:17:13.000 align:start position:0% does this thing and often I hear there's like<00:17:11.540> oh<00:17:11.660> that's<00:17:12.199> the<00:17:12.260> lead<00:17:12.500> developer<00:17:12.860> he 00:17:13.000 --> 00:17:13.010 align:start position:0% like oh that's the lead developer he 00:17:13.010 --> 00:17:14.949 align:start position:0% like oh that's the lead developer he won't<00:17:13.189> ever<00:17:13.400> do<00:17:13.579> that<00:17:13.670> to<00:17:13.790> us<00:17:13.910> and<00:17:14.150> that's<00:17:14.839> not 00:17:14.949 --> 00:17:14.959 align:start position:0% won't ever do that to us and that's not 00:17:14.959 --> 00:17:16.900 align:start position:0% won't ever do that to us and that's not counting<00:17:15.230> for<00:17:15.559> him<00:17:15.740> a<00:17:15.949> being<00:17:16.189> malicious<00:17:16.490> him 00:17:16.900 --> 00:17:16.910 align:start position:0% counting for him a being malicious him 00:17:16.910 --> 00:17:19.990 align:start position:0% counting for him a being malicious him or<00:17:17.059> her<00:17:17.179> or<00:17:17.360> them<00:17:18.140> being<00:17:18.520> hacked<00:17:19.520> and<00:17:19.850> their 00:17:19.990 --> 00:17:20.000 align:start position:0% or her or them being hacked and their 00:17:20.000 --> 00:17:22.980 align:start position:0% or her or them being hacked and their computers<00:17:20.510> private<00:17:21.079> key<00:17:21.230> being<00:17:21.410> stolen<00:17:21.740> so<00:17:22.220> I 00:17:22.980 --> 00:17:22.990 align:start position:0% computers private key being stolen so I 00:17:22.990 --> 00:17:26.290 align:start position:0% computers private key being stolen so I had<00:17:23.990> to<00:17:24.110> offer<00:17:24.290> inhere<00:17:24.730> in<00:17:25.730> response<00:17:26.120> to<00:17:26.240> a 00:17:26.290 --> 00:17:26.300 align:start position:0% had to offer inhere in response to a 00:17:26.300 --> 00:17:28.419 align:start position:0% had to offer inhere in response to a completely<00:17:26.630> valid<00:17:26.750> audit<00:17:27.439> well<00:17:28.100> that<00:17:28.250> won't 00:17:28.419 --> 00:17:28.429 align:start position:0% completely valid audit well that won't 00:17:28.429 --> 00:17:30.910 align:start position:0% completely valid audit well that won't happen<00:17:28.580> and<00:17:28.970> that's<00:17:29.750> you're<00:17:30.380> losing<00:17:30.710> some<00:17:30.890> of 00:17:30.910 --> 00:17:30.920 align:start position:0% happen and that's you're losing some of 00:17:30.920 --> 00:17:34.390 align:start position:0% happen and that's you're losing some of the<00:17:31.010> value<00:17:31.280> of<00:17:31.370> blockchain 00:17:34.390 --> 00:17:34.400 align:start position:0% 00:17:34.400 --> 00:17:36.279 align:start position:0% so<00:17:35.090> well<00:17:35.240> we're<00:17:35.390> talking<00:17:35.600> about<00:17:35.720> audits<00:17:36.110> at<00:17:36.260> a 00:17:36.279 --> 00:17:36.289 align:start position:0% so well we're talking about audits at a 00:17:36.289 --> 00:17:38.890 align:start position:0% so well we're talking about audits at a very<00:17:36.620> high<00:17:36.830> level<00:17:36.980> would<00:17:37.279> you<00:17:37.490> describe<00:17:38.029> how 00:17:38.890 --> 00:17:38.900 align:start position:0% very high level would you describe how 00:17:38.900 --> 00:17:41.019 align:start position:0% very high level would you describe how you<00:17:38.960> go<00:17:39.260> about<00:17:39.380> an<00:17:39.679> audit<00:17:39.950> like<00:17:40.429> how<00:17:40.669> do<00:17:40.730> you<00:17:40.850> go 00:17:41.019 --> 00:17:41.029 align:start position:0% you go about an audit like how do you go 00:17:41.029 --> 00:17:43.149 align:start position:0% you go about an audit like how do you go from<00:17:41.299> here's<00:17:41.690> a<00:17:41.750> big<00:17:41.929> chunk<00:17:42.140> of<00:17:42.230> code<00:17:42.440> to<00:17:42.860> - 00:17:43.149 --> 00:17:43.159 align:start position:0% from here's a big chunk of code to - 00:17:43.159 --> 00:17:47.620 align:start position:0% from here's a big chunk of code to - here's<00:17:43.309> a<00:17:43.370> finished<00:17:43.640> audit<00:17:43.880> report<00:17:46.360> I<00:17:47.360> would 00:17:47.620 --> 00:17:47.630 align:start position:0% here's a finished audit report I would 00:17:47.630 --> 00:17:52.330 align:start position:0% here's a finished audit report I would say<00:17:47.809> I<00:17:48.049> mean<00:17:48.789> usually<00:17:50.409> to<00:17:51.409> be<00:17:51.470> fair<00:17:51.590> most<00:17:51.860> most 00:17:52.330 --> 00:17:52.340 align:start position:0% say I mean usually to be fair most most 00:17:52.340 --> 00:17:53.860 align:start position:0% say I mean usually to be fair most most audits<00:17:52.669> I<00:17:52.760> feel<00:17:52.940> aren't<00:17:53.179> actually<00:17:53.480> large 00:17:53.860 --> 00:17:53.870 align:start position:0% audits I feel aren't actually large 00:17:53.870 --> 00:17:57.070 align:start position:0% audits I feel aren't actually large amounts<00:17:54.230> of<00:17:54.260> code<00:17:54.440> like<00:17:54.650> the<00:17:54.980> Dow<00:17:55.159> looked<00:17:56.080> way 00:17:57.070 --> 00:17:57.080 align:start position:0% amounts of code like the Dow looked way 00:17:57.080 --> 00:17:58.240 align:start position:0% amounts of code like the Dow looked way larger<00:17:57.440> than<00:17:57.620> anything<00:17:57.799> I've<00:17:57.980> needed<00:17:58.190> to 00:17:58.240 --> 00:17:58.250 align:start position:0% larger than anything I've needed to 00:17:58.250 --> 00:17:59.769 align:start position:0% larger than anything I've needed to audit<00:17:58.490> before<00:17:58.760> that<00:17:58.909> was<00:17:59.000> like<00:17:59.150> a<00:17:59.179> lot<00:17:59.450> of<00:17:59.480> code 00:17:59.769 --> 00:17:59.779 align:start position:0% audit before that was like a lot of code 00:17:59.779 --> 00:18:04.169 align:start position:0% audit before that was like a lot of code for<00:17:59.990> what<00:18:00.110> I<00:18:00.140> was<00:18:00.230> doing<00:18:00.730> but<00:18:01.730> even<00:18:01.970> with<00:18:02.500> one 00:18:04.169 --> 00:18:04.179 align:start position:0% for what I was doing but even with one 00:18:04.179 --> 00:18:06.580 align:start position:0% for what I was doing but even with one issue<00:18:05.179> or<00:18:05.450> thing<00:18:05.929> that<00:18:06.049> actually<00:18:06.110> makes<00:18:06.289> this 00:18:06.580 --> 00:18:06.590 align:start position:0% issue or thing that actually makes this 00:18:06.590 --> 00:18:08.019 align:start position:0% issue or thing that actually makes this describing<00:18:07.309> this<00:18:07.399> process<00:18:07.760> a<00:18:07.820> little<00:18:07.880> bit 00:18:08.019 --> 00:18:08.029 align:start position:0% describing this process a little bit 00:18:08.029 --> 00:18:09.490 align:start position:0% describing this process a little bit easier<00:18:08.299> is<00:18:08.390> usually<00:18:08.690> it's<00:18:09.080> very<00:18:09.320> modular 00:18:09.490 --> 00:18:09.500 align:start position:0% easier is usually it's very modular 00:18:09.500 --> 00:18:12.970 align:start position:0% easier is usually it's very modular usually<00:18:10.100> there<00:18:10.250> is<00:18:10.279> a<00:18:10.659> wack<00:18:11.659> ton<00:18:12.080> of<00:18:12.409> contracts 00:18:12.970 --> 00:18:12.980 align:start position:0% usually there is a wack ton of contracts 00:18:12.980 --> 00:18:14.230 align:start position:0% usually there is a wack ton of contracts that<00:18:13.070> are<00:18:13.250> all<00:18:13.370> inheriting<00:18:13.880> for<00:18:14.000> each<00:18:14.090> other 00:18:14.230 --> 00:18:14.240 align:start position:0% that are all inheriting for each other 00:18:14.240 --> 00:18:16.539 align:start position:0% that are all inheriting for each other using<00:18:14.570> each<00:18:14.809> other<00:18:15.070> so<00:18:16.070> it<00:18:16.130> makes<00:18:16.279> it<00:18:16.309> easy<00:18:16.490> to 00:18:16.539 --> 00:18:16.549 align:start position:0% using each other so it makes it easy to 00:18:16.549 --> 00:18:20.139 align:start position:0% using each other so it makes it easy to kind<00:18:16.789> of<00:18:16.820> break<00:18:17.000> it<00:18:17.149> down<00:18:17.299> and<00:18:17.840> and<00:18:19.120> yeah<00:18:20.120> I 00:18:20.139 --> 00:18:20.149 align:start position:0% kind of break it down and and yeah I 00:18:20.149 --> 00:18:22.000 align:start position:0% kind of break it down and and yeah I usually<00:18:20.630> just<00:18:20.840> start<00:18:21.110> at<00:18:21.200> the<00:18:21.260> top<00:18:21.409> go<00:18:21.710> through 00:18:22.000 --> 00:18:22.010 align:start position:0% usually just start at the top go through 00:18:22.010 --> 00:18:23.799 align:start position:0% usually just start at the top go through it<00:18:22.159> and<00:18:22.450> probably<00:18:23.450> call<00:18:23.570> you<00:18:23.600> browse 00:18:23.799 --> 00:18:23.809 align:start position:0% it and probably call you browse 00:18:23.809 --> 00:18:25.450 align:start position:0% it and probably call you browse Wikipedia<00:18:24.350> you<00:18:24.500> hit<00:18:24.679> like<00:18:24.830> some<00:18:25.010> good<00:18:25.220> class 00:18:25.450 --> 00:18:25.460 align:start position:0% Wikipedia you hit like some good class 00:18:25.460 --> 00:18:26.769 align:start position:0% Wikipedia you hit like some good class you're<00:18:25.760> like<00:18:25.880> I<00:18:25.940> don't<00:18:26.000> wanna<00:18:26.210> means<00:18:26.419> and<00:18:26.690> so 00:18:26.769 --> 00:18:26.779 align:start position:0% you're like I don't wanna means and so 00:18:26.779 --> 00:18:28.149 align:start position:0% you're like I don't wanna means and so you<00:18:26.870> jump<00:18:27.140> with<00:18:27.260> that<00:18:27.350> file<00:18:27.649> and<00:18:27.950> you<00:18:28.010> go 00:18:28.149 --> 00:18:28.159 align:start position:0% you jump with that file and you go 00:18:28.159 --> 00:18:30.789 align:start position:0% you jump with that file and you go through<00:18:28.279> that<00:18:28.490> and<00:18:28.730> it<00:18:29.510> is<00:18:29.630> then<00:18:30.230> you<00:18:30.320> start 00:18:30.789 --> 00:18:30.799 align:start position:0% through that and it is then you start 00:18:30.799 --> 00:18:32.769 align:start position:0% through that and it is then you start popping<00:18:30.950> the<00:18:31.220> stack<00:18:31.250> and<00:18:31.610> get<00:18:31.760> up<00:18:31.880> and<00:18:32.270> you 00:18:32.769 --> 00:18:32.779 align:start position:0% popping the stack and get up and you 00:18:32.779 --> 00:18:34.000 align:start position:0% popping the stack and get up and you have<00:18:32.899> to<00:18:32.960> go<00:18:33.080> over<00:18:33.230> it<00:18:33.289> a<00:18:33.350> few<00:18:33.380> times<00:18:33.740> before 00:18:34.000 --> 00:18:34.010 align:start position:0% have to go over it a few times before 00:18:34.010 --> 00:18:36.220 align:start position:0% have to go over it a few times before yeah<00:18:34.549> that's<00:18:35.270> a<00:18:35.360> good<00:18:35.450> point<00:18:35.630> the<00:18:35.899> first<00:18:36.110> thing 00:18:36.220 --> 00:18:36.230 align:start position:0% yeah that's a good point the first thing 00:18:36.230 --> 00:18:37.419 align:start position:0% yeah that's a good point the first thing you<00:18:36.289> do<00:18:36.500> is<00:18:36.590> really<00:18:36.799> understand<00:18:37.159> what<00:18:37.370> the 00:18:37.419 --> 00:18:37.429 align:start position:0% you do is really understand what the 00:18:37.429 --> 00:18:39.760 align:start position:0% you do is really understand what the code<00:18:37.580> is<00:18:37.610> doing<00:18:37.750> trying<00:18:38.750> to<00:18:38.809> audit<00:18:39.230> code<00:18:39.500> that 00:18:39.760 --> 00:18:39.770 align:start position:0% code is doing trying to audit code that 00:18:39.770 --> 00:18:40.990 align:start position:0% code is doing trying to audit code that you're<00:18:39.890> kind<00:18:40.010> of<00:18:40.039> like<00:18:40.190> well<00:18:40.340> I<00:18:40.370> think<00:18:40.520> it<00:18:40.789> kind 00:18:40.990 --> 00:18:41.000 align:start position:0% you're kind of like well I think it kind 00:18:41.000 --> 00:18:42.669 align:start position:0% you're kind of like well I think it kind of<00:18:41.090> does<00:18:41.240> this<00:18:41.419> you<00:18:42.289> really<00:18:42.440> need<00:18:42.529> to 00:18:42.669 --> 00:18:42.679 align:start position:0% of does this you really need to 00:18:42.679 --> 00:18:44.470 align:start position:0% of does this you really need to understand<00:18:43.039> the<00:18:43.520> assumptions<00:18:43.850> the<00:18:44.179> rest<00:18:44.390> of 00:18:44.470 --> 00:18:44.480 align:start position:0% understand the assumptions the rest of 00:18:44.480 --> 00:18:47.889 align:start position:0% understand the assumptions the rest of the<00:18:44.539> code<00:18:44.659> is<00:18:44.720> making<00:18:45.490> I<00:18:46.490> mean<00:18:46.880> going<00:18:47.630> back<00:18:47.809> I 00:18:47.889 --> 00:18:47.899 align:start position:0% the code is making I mean going back I 00:18:47.899 --> 00:18:49.960 align:start position:0% the code is making I mean going back I guess<00:18:48.020> to<00:18:48.260> a<00:18:48.289> previous<00:18:48.770> thing<00:18:48.950> another<00:18:49.340> like 00:18:49.960 --> 00:18:49.970 align:start position:0% guess to a previous thing another like 00:18:49.970 --> 00:18:52.539 align:start position:0% guess to a previous thing another like thing<00:18:50.510> I<00:18:50.600> often<00:18:50.779> see<00:18:51.200> is<00:18:51.500> let's<00:18:52.399> say<00:18:52.460> you're 00:18:52.539 --> 00:18:52.549 align:start position:0% thing I often see is let's say you're 00:18:52.549 --> 00:18:56.019 align:start position:0% thing I often see is let's say you're counting<00:18:53.059> the<00:18:53.539> number<00:18:53.960> of<00:18:54.260> elements<00:18:54.830> inside<00:18:55.580> a 00:18:56.019 --> 00:18:56.029 align:start position:0% counting the number of elements inside a 00:18:56.029 --> 00:18:59.139 align:start position:0% counting the number of elements inside a mapping<00:18:56.480> I<00:18:56.720> often<00:18:57.470> see<00:18:57.679> you<00:18:58.429> know<00:18:58.520> plus<00:18:58.789> plus 00:18:59.139 --> 00:18:59.149 align:start position:0% mapping I often see you know plus plus 00:18:59.149 --> 00:19:01.360 align:start position:0% mapping I often see you know plus plus and<00:18:59.450> then<00:18:59.630> set<00:18:59.929> but<00:19:00.350> this<00:19:00.470> isn't<00:19:00.620> or<00:19:00.830> in<00:19:01.100> the 00:19:01.360 --> 00:19:01.370 align:start position:0% and then set but this isn't or in the 00:19:01.370 --> 00:19:03.850 align:start position:0% and then set but this isn't or in the other<00:19:01.490> direction<00:19:01.669> -<00:19:02.299> -<00:19:02.659> and<00:19:02.899> then<00:19:03.020> set<00:19:03.470> to<00:19:03.500> zero 00:19:03.850 --> 00:19:03.860 align:start position:0% other direction - - and then set to zero 00:19:03.860 --> 00:19:06.730 align:start position:0% other direction - - and then set to zero and<00:19:04.210> this<00:19:05.210> is<00:19:05.360> a<00:19:05.390> huge<00:19:05.570> problem<00:19:05.750> because<00:19:05.899> if 00:19:06.730 --> 00:19:06.740 align:start position:0% and this is a huge problem because if 00:19:06.740 --> 00:19:08.289 align:start position:0% and this is a huge problem because if you<00:19:06.919> set<00:19:07.130> the<00:19:07.220> same<00:19:07.399> thing<00:19:07.580> twice<00:19:07.789> you<00:19:08.179> now 00:19:08.289 --> 00:19:08.299 align:start position:0% you set the same thing twice you now 00:19:08.299 --> 00:19:09.820 align:start position:0% you set the same thing twice you now think<00:19:08.600> the<00:19:08.690> mapping<00:19:08.960> has<00:19:09.049> to<00:19:09.260> bytom's<00:19:09.559> in<00:19:09.710> it 00:19:09.820 --> 00:19:09.830 align:start position:0% think the mapping has to bytom's in it 00:19:09.830 --> 00:19:14.409 align:start position:0% think the mapping has to bytom's in it and<00:19:09.980> so<00:19:11.950> it's<00:19:12.950> important<00:19:13.340> to<00:19:13.370> kind<00:19:14.000> of<00:19:14.120> be<00:19:14.330> able 00:19:14.409 --> 00:19:14.419 align:start position:0% and so it's important to kind of be able 00:19:14.419 --> 00:19:16.360 align:start position:0% and so it's important to kind of be able to<00:19:14.570> trace<00:19:14.840> back<00:19:15.080> and<00:19:15.350> see<00:19:15.500> well<00:19:15.740> what<00:19:15.980> code 00:19:16.360 --> 00:19:16.370 align:start position:0% to trace back and see well what code 00:19:16.370 --> 00:19:18.970 align:start position:0% to trace back and see well what code paths<00:19:16.640> can<00:19:16.970> get<00:19:17.149> here<00:19:17.360> to<00:19:17.510> even<00:19:17.659> do<00:19:17.960> this<00:19:18.140> maybe 00:19:18.970 --> 00:19:18.980 align:start position:0% paths can get here to even do this maybe 00:19:18.980 --> 00:19:20.350 align:start position:0% paths can get here to even do this maybe they're<00:19:19.279> guarding<00:19:19.520> it<00:19:19.580> somewhere<00:19:19.820> else<00:19:19.970> maybe 00:19:20.350 --> 00:19:20.360 align:start position:0% they're guarding it somewhere else maybe 00:19:20.360 --> 00:19:21.279 align:start position:0% they're guarding it somewhere else maybe they're<00:19:20.600> not<00:19:20.690> maybe<00:19:20.960> they<00:19:21.110> should<00:19:21.230> be 00:19:21.279 --> 00:19:21.289 align:start position:0% they're not maybe they should be 00:19:21.289 --> 00:19:24.190 align:start position:0% they're not maybe they should be checking<00:19:21.679> like<00:19:22.429> gas<00:19:23.210> efficiency<00:19:23.809> may<00:19:24.020> or<00:19:24.110> may 00:19:24.190 --> 00:19:24.200 align:start position:0% checking like gas efficiency may or may 00:19:24.200 --> 00:19:27.250 align:start position:0% checking like gas efficiency may or may not<00:19:24.230> come<00:19:24.409> to<00:19:24.559> play<00:19:24.740> so<00:19:25.250> I<00:19:26.049> don't<00:19:27.049> know<00:19:27.140> if<00:19:27.230> I 00:19:27.250 --> 00:19:27.260 align:start position:0% not come to play so I don't know if I 00:19:27.260 --> 00:19:28.680 align:start position:0% not come to play so I don't know if I really<00:19:27.320> answered<00:19:27.649> the<00:19:27.710> question<00:19:28.070> but<00:19:28.580> what 00:19:28.680 --> 00:19:28.690 align:start position:0% really answered the question but what 00:19:28.690 --> 00:19:31.090 align:start position:0% really answered the question but what seemed<00:19:29.690> like<00:19:29.750> good<00:19:30.020> search<00:19:30.289> do<00:19:30.919> you<00:19:31.010> have 00:19:31.090 --> 00:19:31.100 align:start position:0% seemed like good search do you have 00:19:31.100 --> 00:19:33.159 align:start position:0% seemed like good search do you have anything<00:19:31.279> to<00:19:31.460> add<00:19:31.580> matter<00:19:31.789> no<00:19:32.419> that's<00:19:32.809> that 00:19:33.159 --> 00:19:33.169 align:start position:0% anything to add matter no that's that 00:19:33.169 --> 00:19:35.230 align:start position:0% anything to add matter no that's that sounds<00:19:33.350> very<00:19:33.799> close<00:19:34.100> to<00:19:34.490> what<00:19:34.669> I'm<00:19:34.760> doing<00:19:34.789> I 00:19:35.230 --> 00:19:35.240 align:start position:0% sounds very close to what I'm doing I 00:19:35.240 --> 00:19:37.389 align:start position:0% sounds very close to what I'm doing I mean<00:19:35.390> it's<00:19:35.539> very<00:19:35.600> it's<00:19:36.559> extremely<00:19:37.220> time 00:19:37.389 --> 00:19:37.399 align:start position:0% mean it's very it's extremely time 00:19:37.399 --> 00:19:41.289 align:start position:0% mean it's very it's extremely time consuming<00:19:37.460> to<00:19:38.270> do<00:19:38.390> it<00:19:38.570> this<00:19:39.409> way<00:19:40.000> but<00:19:41.000> really 00:19:41.289 --> 00:19:41.299 align:start position:0% consuming to do it this way but really 00:19:41.299 --> 00:19:43.840 align:start position:0% consuming to do it this way but really get<00:19:41.570> to<00:19:41.929> know<00:19:41.960> the<00:19:42.350> code<00:19:42.620> read<00:19:43.399> it<00:19:43.580> read<00:19:43.820> it 00:19:43.840 --> 00:19:43.850 align:start position:0% get to know the code read it read it 00:19:43.850 --> 00:19:45.490 align:start position:0% get to know the code read it read it read<00:19:44.179> it<00:19:44.390> read<00:19:44.570> it<00:19:44.630> until<00:19:44.960> you<00:19:45.169> know<00:19:45.289> it's 00:19:45.490 --> 00:19:45.500 align:start position:0% read it read it until you know it's 00:19:45.500 --> 00:19:47.570 align:start position:0% read it read it until you know it's forwards<00:19:46.490> and<00:19:46.610> backwards 00:19:47.570 --> 00:19:47.580 align:start position:0% forwards and backwards 00:19:47.580 --> 00:19:50.090 align:start position:0% forwards and backwards and<00:19:47.700> during<00:19:48.630> that<00:19:48.840> and<00:19:49.230> try<00:19:49.740> to<00:19:49.800> have<00:19:49.980> this 00:19:50.090 --> 00:19:50.100 align:start position:0% and during that and try to have this 00:19:50.100 --> 00:19:52.310 align:start position:0% and during that and try to have this aggressive<00:19:50.700> mindset<00:19:51.270> where<00:19:51.660> you<00:19:51.780> know<00:19:52.050> that 00:19:52.310 --> 00:19:52.320 align:start position:0% aggressive mindset where you know that 00:19:52.320 --> 00:19:54.830 align:start position:0% aggressive mindset where you know that there<00:19:52.500> are<00:19:52.740> flaws<00:19:53.640> in<00:19:53.910> it<00:19:54.030> you<00:19:54.300> just<00:19:54.330> need<00:19:54.720> to 00:19:54.830 --> 00:19:54.840 align:start position:0% there are flaws in it you just need to 00:19:54.840 --> 00:19:59.300 align:start position:0% there are flaws in it you just need to find<00:19:55.080> them<00:19:57.590> other<00:19:58.590> questions<00:19:59.070> from<00:19:59.160> the 00:19:59.300 --> 00:19:59.310 align:start position:0% find them other questions from the 00:19:59.310 --> 00:20:04.910 align:start position:0% find them other questions from the audience<00:20:02.420> shout<00:20:03.420> and<00:20:03.690> I'll<00:20:03.780> repeat<00:20:04.080> oh<00:20:04.350> no<00:20:04.650> we 00:20:04.910 --> 00:20:04.920 align:start position:0% audience shout and I'll repeat oh no we 00:20:04.920 --> 00:20:09.620 align:start position:0% audience shout and I'll repeat oh no we have<00:20:05.010> a<00:20:05.040> microphone<00:20:07.820> hi<00:20:08.850> so<00:20:09.210> we<00:20:09.360> heard<00:20:09.510> from 00:20:09.620 --> 00:20:09.630 align:start position:0% have a microphone hi so we heard from 00:20:09.630 --> 00:20:11.630 align:start position:0% have a microphone hi so we heard from Piper<00:20:09.900> yesterday<00:20:10.530> about<00:20:10.710> package<00:20:11.250> management 00:20:11.630 --> 00:20:11.640 align:start position:0% Piper yesterday about package management 00:20:11.640 --> 00:20:15.470 align:start position:0% Piper yesterday about package management for<00:20:12.060> a<00:20:12.090> solidity<00:20:12.630> and<00:20:13.410> in<00:20:13.770> Python<00:20:13.950> as<00:20:14.520> well<00:20:14.730> are 00:20:15.470 --> 00:20:15.480 align:start position:0% for a solidity and in Python as well are 00:20:15.480 --> 00:20:17.390 align:start position:0% for a solidity and in Python as well are you<00:20:15.750> guys<00:20:15.960> or<00:20:16.140> anyone<00:20:16.410> else<00:20:16.560> looking<00:20:16.770> into<00:20:17.130> how 00:20:17.390 --> 00:20:17.400 align:start position:0% you guys or anyone else looking into how 00:20:17.400 --> 00:20:19.250 align:start position:0% you guys or anyone else looking into how we<00:20:17.460> know<00:20:17.730> if<00:20:17.880> we<00:20:18.000> can<00:20:18.150> trust<00:20:18.480> those<00:20:18.690> packages 00:20:19.250 --> 00:20:19.260 align:start position:0% we know if we can trust those packages 00:20:19.260 --> 00:20:21.650 align:start position:0% we know if we can trust those packages especially<00:20:19.410> as<00:20:19.980> the<00:20:20.190> standard<00:20:20.880> library<00:20:21.390> might 00:20:21.650 --> 00:20:21.660 align:start position:0% especially as the standard library might 00:20:21.660 --> 00:20:23.180 align:start position:0% especially as the standard library might be<00:20:21.810> replicated<00:20:22.440> with<00:20:22.470> different<00:20:22.860> package 00:20:23.180 --> 00:20:23.190 align:start position:0% be replicated with different package 00:20:23.190 --> 00:20:25.580 align:start position:0% be replicated with different package sets<00:20:23.460> obviously<00:20:24.360> today<00:20:24.960> in<00:20:25.110> the<00:20:25.200> development 00:20:25.580 --> 00:20:25.590 align:start position:0% sets obviously today in the development 00:20:25.590 --> 00:20:27.170 align:start position:0% sets obviously today in the development world<00:20:25.680> we<00:20:26.010> just<00:20:26.220> hope<00:20:26.370> the<00:20:26.550> code<00:20:26.730> works<00:20:26.970> and 00:20:27.170 --> 00:20:27.180 align:start position:0% world we just hope the code works and 00:20:27.180 --> 00:20:29.540 align:start position:0% world we just hope the code works and then<00:20:27.330> we<00:20:27.390> realize<00:20:27.720> it<00:20:27.960> it<00:20:28.380> doesn't<00:20:28.770> which<00:20:28.980> may 00:20:29.540 --> 00:20:29.550 align:start position:0% then we realize it it doesn't which may 00:20:29.550 --> 00:20:31.100 align:start position:0% then we realize it it doesn't which may not<00:20:29.700> be<00:20:29.760> as<00:20:30.030> big<00:20:30.270> of<00:20:30.300> a<00:20:30.450> deal<00:20:30.630> when<00:20:30.840> it's<00:20:30.960> not 00:20:31.100 --> 00:20:31.110 align:start position:0% not be as big of a deal when it's not 00:20:31.110 --> 00:20:35.510 align:start position:0% not be as big of a deal when it's not solidity<00:20:33.590> well<00:20:34.590> that's<00:20:35.160> an<00:20:35.310> interesting 00:20:35.510 --> 00:20:35.520 align:start position:0% solidity well that's an interesting 00:20:35.520 --> 00:20:40.280 align:start position:0% solidity well that's an interesting question<00:20:35.990> and<00:20:37.010> just<00:20:38.010> will<00:20:38.190> to<00:20:38.580> add<00:20:39.260> there<00:20:40.260> is 00:20:40.280 --> 00:20:40.290 align:start position:0% question and just will to add there is 00:20:40.290 --> 00:20:42.560 align:start position:0% question and just will to add there is also<00:20:40.500> the<00:20:40.680> question<00:20:40.800> that<00:20:41.430> if<00:20:41.700> you<00:20:41.820> can<00:20:42.420> we 00:20:42.560 --> 00:20:42.570 align:start position:0% also the question that if you can we 00:20:42.570 --> 00:20:44.930 align:start position:0% also the question that if you can we trust<00:20:42.870> the<00:20:43.110> standards<00:20:43.590> because<00:20:44.190> a<00:20:44.580> lot<00:20:44.820> of 00:20:44.930 --> 00:20:44.940 align:start position:0% trust the standards because a lot of 00:20:44.940 --> 00:20:46.790 align:start position:0% trust the standards because a lot of contract<00:20:45.390> interacts<00:20:45.960> with<00:20:46.200> tokens<00:20:46.530> for 00:20:46.790 --> 00:20:46.800 align:start position:0% contract interacts with tokens for 00:20:46.800 --> 00:20:49.340 align:start position:0% contract interacts with tokens for example<00:20:47.220> and<00:20:47.670> no<00:20:48.630> one<00:20:48.780> accounts<00:20:49.170> for<00:20:49.290> a 00:20:49.340 --> 00:20:49.350 align:start position:0% example and no one accounts for a 00:20:49.350 --> 00:20:51.320 align:start position:0% example and no one accounts for a malicious<00:20:49.800> token<00:20:50.190> that<00:20:50.220> can<00:20:50.760> implement<00:20:51.030> this 00:20:51.320 --> 00:20:51.330 align:start position:0% malicious token that can implement this 00:20:51.330 --> 00:20:53.420 align:start position:0% malicious token that can implement this standard<00:20:51.750> we<00:20:51.870> can<00:20:51.900> modify<00:20:52.350> in<00:20:52.590> some<00:20:52.920> some<00:20:53.250> way 00:20:53.420 --> 00:20:53.430 align:start position:0% standard we can modify in some some way 00:20:53.430 --> 00:20:58.100 align:start position:0% standard we can modify in some some way that<00:20:55.040> exploits<00:20:56.040> the<00:20:56.250> the<00:20:56.580> other<00:20:56.730> counters<00:20:57.270> so 00:20:58.100 --> 00:20:58.110 align:start position:0% that exploits the the other counters so 00:20:58.110 --> 00:21:01.580 align:start position:0% that exploits the the other counters so it's<00:20:59.000> I'm<00:21:00.000> not<00:21:00.210> sure<00:21:00.390> if<00:21:00.510> I'm<00:21:00.660> answering<00:21:01.170> a 00:21:01.580 --> 00:21:01.590 align:start position:0% it's I'm not sure if I'm answering a 00:21:01.590 --> 00:21:08.360 align:start position:0% it's I'm not sure if I'm answering a question<00:21:01.790> but<00:21:02.790> kind<00:21:03.330> of<00:21:03.450> a<00:21:05.000> bad<00:21:07.100> I'm<00:21:08.100> sorry 00:21:08.360 --> 00:21:08.370 align:start position:0% question but kind of a bad I'm sorry 00:21:08.370 --> 00:21:12.320 align:start position:0% question but kind of a bad I'm sorry it's<00:21:08.910> it's<00:21:09.450> hard<00:21:09.810> to<00:21:10.160> really<00:21:11.160> trust<00:21:11.550> everyone 00:21:12.320 --> 00:21:12.330 align:start position:0% it's it's hard to really trust everyone 00:21:12.330 --> 00:21:14.780 align:start position:0% it's it's hard to really trust everyone so<00:21:12.570> it's<00:21:12.870> kind<00:21:13.110> of<00:21:13.170> what<00:21:13.800> marketing<00:21:14.160> said<00:21:14.430> you 00:21:14.780 --> 00:21:14.790 align:start position:0% so it's kind of what marketing said you 00:21:14.790 --> 00:21:16.640 align:start position:0% so it's kind of what marketing said you have<00:21:14.940> to<00:21:15.120> be<00:21:15.240> aggressive<00:21:15.510> you<00:21:15.990> have<00:21:16.200> to<00:21:16.350> think 00:21:16.640 --> 00:21:16.650 align:start position:0% have to be aggressive you have to think 00:21:16.650 --> 00:21:19.640 align:start position:0% have to be aggressive you have to think that<00:21:16.860> anything<00:21:17.820> can<00:21:18.210> break<00:21:18.390> anytime<00:21:18.810> you<00:21:19.470> have 00:21:19.640 --> 00:21:19.650 align:start position:0% that anything can break anytime you have 00:21:19.650 --> 00:21:23.000 align:start position:0% that anything can break anytime you have the<00:21:19.710> think<00:21:20.550> that<00:21:21.260> anyone<00:21:22.260> is<00:21:22.290> malicious 00:21:23.000 --> 00:21:23.010 align:start position:0% the think that anyone is malicious 00:21:23.010 --> 00:21:26.840 align:start position:0% the think that anyone is malicious anyone<00:21:23.670> is<00:21:24.330> bad<00:21:24.540> and<00:21:25.160> kind<00:21:26.160> of<00:21:26.220> go<00:21:26.430> this<00:21:26.610> way 00:21:26.840 --> 00:21:26.850 align:start position:0% anyone is bad and kind of go this way 00:21:26.850 --> 00:21:32.970 align:start position:0% anyone is bad and kind of go this way don't<00:21:27.330> trust<00:21:27.540> anyone 00:21:32.970 --> 00:21:32.980 align:start position:0% 00:21:32.980 --> 00:21:37.799 align:start position:0% I<00:21:35.400> is<00:21:36.400> anyone<00:21:36.820> thinking<00:21:37.090> about<00:21:37.330> putting<00:21:37.600> in 00:21:37.799 --> 00:21:37.809 align:start position:0% I is anyone thinking about putting in 00:21:37.809 --> 00:21:40.220 align:start position:0% I is anyone thinking about putting in that<00:21:37.900> package<00:21:38.290> management<00:21:38.620> system<00:21:39.090> the 00:21:40.220 --> 00:21:40.230 align:start position:0% that package management system the 00:21:40.230 --> 00:21:42.870 align:start position:0% that package management system the concept<00:21:41.230> of<00:21:41.500> this<00:21:41.770> package<00:21:42.250> has<00:21:42.400> been<00:21:42.429> audited 00:21:42.870 --> 00:21:42.880 align:start position:0% concept of this package has been audited 00:21:42.880 --> 00:21:46.770 align:start position:0% concept of this package has been audited and<00:21:43.179> give<00:21:44.020> some<00:21:44.350> kind<00:21:44.590> of<00:21:44.799> a<00:21:45.490> marking<00:21:46.480> of<00:21:46.570> what 00:21:46.770 --> 00:21:46.780 align:start position:0% and give some kind of a marking of what 00:21:46.780 --> 00:21:48.840 align:start position:0% and give some kind of a marking of what company<00:21:47.140> audited<00:21:47.470> it<00:21:47.740> and<00:21:47.950> of<00:21:48.429> course<00:21:48.460> the 00:21:48.840 --> 00:21:48.850 align:start position:0% company audited it and of course the 00:21:48.850 --> 00:21:52.169 align:start position:0% company audited it and of course the reputation<00:21:49.450> for<00:21:49.809> that<00:21:50.049> company<00:21:50.820> is<00:21:51.820> Piper 00:21:52.169 --> 00:21:52.179 align:start position:0% reputation for that company is Piper 00:21:52.179 --> 00:21:58.020 align:start position:0% reputation for that company is Piper here<00:21:53.880> III<00:21:54.960> I<00:21:55.960> mean<00:21:56.440> my<00:21:56.730> perspective<00:21:57.730> at<00:21:57.820> least 00:21:58.020 --> 00:21:58.030 align:start position:0% here III I mean my perspective at least 00:21:58.030 --> 00:21:59.700 align:start position:0% here III I mean my perspective at least maybe<00:21:58.900> I'm<00:21:59.080> not<00:21:59.169> supposed<00:21:59.290> to<00:21:59.500> have<00:21:59.620> an 00:21:59.700 --> 00:21:59.710 align:start position:0% maybe I'm not supposed to have an 00:21:59.710 --> 00:22:01.460 align:start position:0% maybe I'm not supposed to have an opinion<00:21:59.950> since<00:22:00.340> I'm<00:22:00.520> running<00:22:00.820> the<00:22:00.910> panel<00:22:01.240> but 00:22:01.460 --> 00:22:01.470 align:start position:0% opinion since I'm running the panel but 00:22:01.470 --> 00:22:03.960 align:start position:0% opinion since I'm running the panel but is<00:22:02.470> that<00:22:02.950> it's<00:22:03.309> definitely<00:22:03.460> true<00:22:03.880> that 00:22:03.960 --> 00:22:03.970 align:start position:0% is that it's definitely true that 00:22:03.970 --> 00:22:07.020 align:start position:0% is that it's definitely true that systems<00:22:04.630> like<00:22:05.080> NPM<00:22:05.919> are<00:22:06.100> an<00:22:06.220> unsuitable<00:22:06.669> here 00:22:07.020 --> 00:22:07.030 align:start position:0% systems like NPM are an unsuitable here 00:22:07.030 --> 00:22:08.430 align:start position:0% systems like NPM are an unsuitable here you<00:22:07.240> know<00:22:07.330> you<00:22:07.390> need<00:22:07.600> a<00:22:07.630> lot<00:22:07.840> better<00:22:08.049> control 00:22:08.430 --> 00:22:08.440 align:start position:0% you know you need a lot better control 00:22:08.440 --> 00:22:11.010 align:start position:0% you know you need a lot better control over<00:22:08.470> the<00:22:08.710> code<00:22:08.950> you're<00:22:09.130> running<00:22:09.660> but<00:22:10.660> I<00:22:10.720> think 00:22:11.010 --> 00:22:11.020 align:start position:0% over the code you're running but I think 00:22:11.020 --> 00:22:12.900 align:start position:0% over the code you're running but I think step<00:22:11.260> one<00:22:11.470> and<00:22:11.650> as<00:22:11.770> I<00:22:11.890> understand<00:22:12.370> that<00:22:12.490> ESPM 00:22:12.900 --> 00:22:12.910 align:start position:0% step one and as I understand that ESPM 00:22:12.910 --> 00:22:15.450 align:start position:0% step one and as I understand that ESPM implements<00:22:13.390> that<00:22:13.450> is<00:22:13.660> you<00:22:14.620> specify<00:22:14.860> exact 00:22:15.450 --> 00:22:15.460 align:start position:0% implements that is you specify exact 00:22:15.460 --> 00:22:17.340 align:start position:0% implements that is you specify exact versions<00:22:15.880> of<00:22:16.000> the<00:22:16.059> code<00:22:16.330> it<00:22:16.960> crypt 00:22:17.340 --> 00:22:17.350 align:start position:0% versions of the code it crypt 00:22:17.350 --> 00:22:18.900 align:start position:0% versions of the code it crypt graphically<00:22:17.799> hashed<00:22:18.040> you<00:22:18.370> know<00:22:18.520> so<00:22:18.640> you<00:22:18.760> know 00:22:18.900 --> 00:22:18.910 align:start position:0% graphically hashed you know so you know 00:22:18.910 --> 00:22:22.440 align:start position:0% graphically hashed you know so you know you're<00:22:19.090> getting<00:22:19.330> the<00:22:19.360> right<00:22:19.570> code<00:22:19.840> I<00:22:21.450> don't 00:22:22.440 --> 00:22:22.450 align:start position:0% you're getting the right code I don't 00:22:22.450 --> 00:22:25.409 align:start position:0% you're getting the right code I don't know<00:22:22.540> if<00:22:22.690> any<00:22:22.840> of<00:22:23.559> you<00:22:23.740> know<00:22:23.980> whether<00:22:24.360> sort<00:22:25.360> of 00:22:25.409 --> 00:22:25.419 align:start position:0% know if any of you know whether sort of 00:22:25.419 --> 00:22:27.480 align:start position:0% know if any of you know whether sort of metadata<00:22:25.840> about<00:22:26.169> auditing<00:22:26.590> is<00:22:26.799> is<00:22:27.010> in<00:22:27.190> scope 00:22:27.480 --> 00:22:27.490 align:start position:0% metadata about auditing is is in scope 00:22:27.490 --> 00:22:32.460 align:start position:0% metadata about auditing is is in scope or<00:22:27.700> not<00:22:29.700> with<00:22:30.700> a<00:22:30.730> metadata<00:22:31.299> for<00:22:31.840> whether<00:22:32.350> a 00:22:32.460 --> 00:22:32.470 align:start position:0% or not with a metadata for whether a 00:22:32.470 --> 00:22:34.020 align:start position:0% or not with a metadata for whether a code<00:22:32.770> has<00:22:32.919> been<00:22:32.950> audited<00:22:33.490> and<00:22:33.669> who<00:22:33.730> it's<00:22:33.880> been 00:22:34.020 --> 00:22:34.030 align:start position:0% code has been audited and who it's been 00:22:34.030 --> 00:22:36.120 align:start position:0% code has been audited and who it's been audited<00:22:34.419> Byers<00:22:34.690> is<00:22:35.110> in<00:22:35.320> scope<00:22:35.590> for<00:22:35.799> a<00:22:35.860> package 00:22:36.120 --> 00:22:36.130 align:start position:0% audited Byers is in scope for a package 00:22:36.130 --> 00:22:40.080 align:start position:0% audited Byers is in scope for a package management<00:22:36.490> system<00:22:36.669> I<00:22:38.460> don't<00:22:39.460> know<00:22:39.940> what 00:22:40.080 --> 00:22:40.090 align:start position:0% management system I don't know what 00:22:40.090 --> 00:22:43.530 align:start position:0% management system I don't know what level<00:22:40.240> of<00:22:40.419> metadata<00:22:40.780> then<00:22:42.240> so<00:22:43.240> I<00:22:43.270> guess<00:22:43.450> the 00:22:43.530 --> 00:22:43.540 align:start position:0% level of metadata then so I guess the 00:22:43.540 --> 00:22:45.900 align:start position:0% level of metadata then so I guess the question<00:22:43.900> is<00:22:43.990> ask<00:22:44.260> Piper<00:22:44.590> the<00:22:45.460> answer<00:22:45.760> rather 00:22:45.900 --> 00:22:45.910 align:start position:0% question is ask Piper the answer rather 00:22:45.910 --> 00:22:50.850 align:start position:0% question is ask Piper the answer rather Thanks 00:22:50.850 --> 00:22:50.860 align:start position:0% 00:22:50.860 --> 00:22:58.660 align:start position:0% just<00:22:51.860> over<00:22:52.070> there<00:22:52.520> I<00:22:56.710> was<00:22:57.710> wondering<00:22:58.010> if<00:22:58.130> you 00:22:58.660 --> 00:22:58.670 align:start position:0% just over there I was wondering if you 00:22:58.670 --> 00:23:01.840 align:start position:0% just over there I was wondering if you guys<00:22:58.850> are<00:22:59.210> interested<00:22:59.990> in<00:23:00.290> any<00:23:00.470> other<00:23:00.850> smart 00:23:01.840 --> 00:23:01.850 align:start position:0% guys are interested in any other smart 00:23:01.850 --> 00:23:03.940 align:start position:0% guys are interested in any other smart contract<00:23:02.240> languages<00:23:02.660> and<00:23:02.960> if<00:23:03.440> so<00:23:03.620> what<00:23:03.800> would 00:23:03.940 --> 00:23:03.950 align:start position:0% contract languages and if so what would 00:23:03.950 --> 00:23:07.900 align:start position:0% contract languages and if so what would they<00:23:04.040> be<00:23:05.860> we<00:23:06.860> interested<00:23:07.310> in<00:23:07.400> any<00:23:07.580> smart 00:23:07.900 --> 00:23:07.910 align:start position:0% they be we interested in any smart 00:23:07.910 --> 00:23:09.430 align:start position:0% they be we interested in any smart contract<00:23:08.270> languages<00:23:08.630> other<00:23:08.780> than<00:23:08.900> solidity 00:23:09.430 --> 00:23:09.440 align:start position:0% contract languages other than solidity 00:23:09.440 --> 00:23:17.020 align:start position:0% contract languages other than solidity is<00:23:09.710> that<00:23:09.920> great<00:23:10.210> yep<00:23:12.190> yes<00:23:13.190> definitely<00:23:14.350> I<00:23:16.030> did 00:23:17.020 --> 00:23:17.030 align:start position:0% is that great yep yes definitely I did 00:23:17.030 --> 00:23:19.780 align:start position:0% is that great yep yes definitely I did look<00:23:17.300> a<00:23:17.570> bit<00:23:17.720> into<00:23:18.110> serpent<00:23:18.650> contracts<00:23:19.340> way 00:23:19.780 --> 00:23:19.790 align:start position:0% look a bit into serpent contracts way 00:23:19.790 --> 00:23:26.050 align:start position:0% look a bit into serpent contracts way back<00:23:20.090> did<00:23:21.020> an<00:23:21.170> audit<00:23:21.410> of<00:23:21.530> the<00:23:22.180> BTC<00:23:23.180> relay<00:23:25.060> but 00:23:26.050 --> 00:23:26.060 align:start position:0% back did an audit of the BTC relay but 00:23:26.060 --> 00:23:29.250 align:start position:0% back did an audit of the BTC relay but it's<00:23:26.270> right<00:23:27.050> now<00:23:27.260> solidity<00:23:27.950> is<00:23:28.100> the<00:23:28.670> one<00:23:28.850> which 00:23:29.250 --> 00:23:29.260 align:start position:0% it's right now solidity is the one which 00:23:29.260 --> 00:23:34.210 align:start position:0% it's right now solidity is the one which most<00:23:30.260> contacts<00:23:30.830> are<00:23:30.950> written<00:23:31.220> in<00:23:32.890> but<00:23:33.890> I<00:23:33.920> think 00:23:34.210 --> 00:23:34.220 align:start position:0% most contacts are written in but I think 00:23:34.220 --> 00:23:35.860 align:start position:0% most contacts are written in but I think it'll<00:23:34.340> be<00:23:34.520> actually<00:23:34.940> a<00:23:34.970> refreshing<00:23:35.480> change 00:23:35.860 --> 00:23:35.870 align:start position:0% it'll be actually a refreshing change 00:23:35.870 --> 00:23:39.220 align:start position:0% it'll be actually a refreshing change when<00:23:36.260> serpents<00:23:36.980> hits<00:23:37.610> the<00:23:37.910> road<00:23:38.230> properly 00:23:39.220 --> 00:23:39.230 align:start position:0% when serpents hits the road properly 00:23:39.230 --> 00:23:40.270 align:start position:0% when serpents hits the road properly Viper 00:23:40.270 --> 00:23:40.280 align:start position:0% Viper 00:23:40.280 --> 00:23:42.640 align:start position:0% Viper oh<00:23:40.310> sorry<00:23:40.760> Viper<00:23:41.210> yeah<00:23:41.380> yeah<00:23:42.380> I<00:23:42.410> had<00:23:42.620> a 00:23:42.640 --> 00:23:42.650 align:start position:0% oh sorry Viper yeah yeah I had a 00:23:42.650 --> 00:23:44.410 align:start position:0% oh sorry Viper yeah yeah I had a fascinating<00:23:43.340> chat<00:23:43.670> with<00:23:43.790> the<00:23:43.880> lead<00:23:44.000> developer 00:23:44.410 --> 00:23:44.420 align:start position:0% fascinating chat with the lead developer 00:23:44.420 --> 00:23:47.440 align:start position:0% fascinating chat with the lead developer of<00:23:44.480> Vipers<00:23:44.840> a<00:23:44.870> day<00:23:45.080> I<00:23:46.030> think<00:23:47.030> it<00:23:47.120> shows<00:23:47.270> a<00:23:47.300> lot 00:23:47.440 --> 00:23:47.450 align:start position:0% of Vipers a day I think it shows a lot 00:23:47.450 --> 00:23:50.980 align:start position:0% of Vipers a day I think it shows a lot of<00:23:47.480> promise<00:23:47.690> I'd<00:23:48.620> like<00:23:48.860> to<00:23:49.040> see<00:23:49.220> more<00:23:49.990> smart 00:23:50.980 --> 00:23:50.990 align:start position:0% of promise I'd like to see more smart 00:23:50.990 --> 00:23:53.200 align:start position:0% of promise I'd like to see more smart contract<00:23:51.350> programming<00:23:51.710> languages<00:23:52.100> there<00:23:53.090> are 00:23:53.200 --> 00:23:53.210 align:start position:0% contract programming languages there are 00:23:53.210 --> 00:23:54.550 align:start position:0% contract programming languages there are things<00:23:53.360> I<00:23:53.450> like<00:23:53.600> about<00:23:53.630> Souls<00:23:54.080> II<00:23:54.260> and<00:23:54.380> things 00:23:54.550 --> 00:23:54.560 align:start position:0% things I like about Souls II and things 00:23:54.560 --> 00:23:57.010 align:start position:0% things I like about Souls II and things I<00:23:54.680> don't<00:23:54.920> I<00:23:55.130> have<00:23:55.370> a<00:23:55.400> mental<00:23:56.300> laundry<00:23:56.690> list<00:23:56.900> of 00:23:57.010 --> 00:23:57.020 align:start position:0% I don't I have a mental laundry list of 00:23:57.020 --> 00:23:58.570 align:start position:0% I don't I have a mental laundry list of what<00:23:57.170> my<00:23:57.320> perfect<00:23:57.560> programming<00:23:58.310> language 00:23:58.570 --> 00:23:58.580 align:start position:0% what my perfect programming language 00:23:58.580 --> 00:24:00.370 align:start position:0% what my perfect programming language would<00:23:58.730> look<00:23:58.880> like<00:23:59.030> and<00:23:59.330> the<00:23:59.900> reason<00:24:00.140> I<00:24:00.200> don't 00:24:00.370 --> 00:24:00.380 align:start position:0% would look like and the reason I don't 00:24:00.380 --> 00:24:02.500 align:start position:0% would look like and the reason I don't write<00:24:00.590> us<00:24:00.770> is<00:24:00.950> because<00:24:01.280> I'm<00:24:01.490> aware<00:24:01.730> that<00:24:01.850> 90% 00:24:02.500 --> 00:24:02.510 align:start position:0% write us is because I'm aware that 90% 00:24:02.510 --> 00:24:05.260 align:start position:0% write us is because I'm aware that 90% of<00:24:02.810> the<00:24:02.900> work<00:24:03.020> is<00:24:03.200> the<00:24:03.230> tooling<00:24:03.650> and<00:24:04.270> other 00:24:05.260 --> 00:24:05.270 align:start position:0% of the work is the tooling and other 00:24:05.270 --> 00:24:06.670 align:start position:0% of the work is the tooling and other languages<00:24:05.690> can<00:24:05.870> have<00:24:05.930> a<00:24:06.050> bit<00:24:06.200> to<00:24:06.290> catch<00:24:06.440> up 00:24:06.670 --> 00:24:06.680 align:start position:0% languages can have a bit to catch up 00:24:06.680 --> 00:24:08.740 align:start position:0% languages can have a bit to catch up with<00:24:06.860> salasi<00:24:07.160> before<00:24:07.850> it's<00:24:08.030> before<00:24:08.390> they're 00:24:08.740 --> 00:24:08.750 align:start position:0% with salasi before it's before they're 00:24:08.750 --> 00:24:10.540 align:start position:0% with salasi before it's before they're sort<00:24:09.230> of<00:24:09.290> at<00:24:09.380> the<00:24:09.410> same<00:24:09.560> level<00:24:09.980> in<00:24:10.130> terms<00:24:10.340> of 00:24:10.540 --> 00:24:10.550 align:start position:0% sort of at the same level in terms of 00:24:10.550 --> 00:24:14.440 align:start position:0% sort of at the same level in terms of tooling<00:24:10.850> maturity<00:24:12.730> but<00:24:13.730> I<00:24:13.760> don't<00:24:14.000> think<00:24:14.180> like 00:24:14.440 --> 00:24:14.450 align:start position:0% tooling maturity but I don't think like 00:24:14.450 --> 00:24:16.450 align:start position:0% tooling maturity but I don't think like some<00:24:14.720> of<00:24:14.810> these<00:24:15.050> continued<00:24:15.560> domination<00:24:16.160> is<00:24:16.310> in 00:24:16.450 --> 00:24:16.460 align:start position:0% some of these continued domination is in 00:24:16.460 --> 00:24:20.050 align:start position:0% some of these continued domination is in any<00:24:16.580> way<00:24:16.670> it<00:24:16.880> should<00:24:17.890> and<00:24:18.890> so<00:24:19.520> I'm<00:24:19.760> working<00:24:19.970> on 00:24:20.050 --> 00:24:20.060 align:start position:0% any way it should and so I'm working on 00:24:20.060 --> 00:24:21.430 align:start position:0% any way it should and so I'm working on my<00:24:20.120> own<00:24:20.270> like<00:24:20.630> a<00:24:20.660> little<00:24:20.870> language<00:24:20.990> but<00:24:21.320> more 00:24:21.430 --> 00:24:21.440 align:start position:0% my own like a little language but more 00:24:21.440 --> 00:24:25.450 align:start position:0% my own like a little language but more as<00:24:21.500> a<00:24:21.560> side<00:24:21.740> project<00:24:22.010> than<00:24:22.400> anything<00:24:24.460> the 00:24:25.450 --> 00:24:25.460 align:start position:0% as a side project than anything the 00:24:25.460 --> 00:24:27.520 align:start position:0% as a side project than anything the solidity<00:24:25.790> is<00:24:25.880> by<00:24:26.060> far<00:24:26.300> the<00:24:26.420> most<00:24:26.570> yeah<00:24:27.140> mature 00:24:27.520 --> 00:24:27.530 align:start position:0% solidity is by far the most yeah mature 00:24:27.530 --> 00:24:29.740 align:start position:0% solidity is by far the most yeah mature and<00:24:27.770> it's<00:24:28.580> all<00:24:28.820> those<00:24:28.940> other<00:24:29.150> things<00:24:29.210> on<00:24:29.570> top 00:24:29.740 --> 00:24:29.750 align:start position:0% and it's all those other things on top 00:24:29.750 --> 00:24:31.330 align:start position:0% and it's all those other things on top of<00:24:29.810> it<00:24:30.050> that<00:24:30.140> you<00:24:30.230> really<00:24:30.260> want<00:24:30.620> like<00:24:30.980> you<00:24:31.130> want 00:24:31.330 --> 00:24:31.340 align:start position:0% of it that you really want like you want 00:24:31.340 --> 00:24:34.270 align:start position:0% of it that you really want like you want the<00:24:31.670> the<00:24:32.480> ID<00:24:32.660> ease<00:24:33.050> integration<00:24:33.740> and<00:24:34.100> like 00:24:34.270 --> 00:24:34.280 align:start position:0% the the ID ease integration and like 00:24:34.280 --> 00:24:36.700 align:start position:0% the the ID ease integration and like syntax<00:24:34.520> highlighting<00:24:35.060> like<00:24:35.590> writing<00:24:36.590> a 00:24:36.700 --> 00:24:36.710 align:start position:0% syntax highlighting like writing a 00:24:36.710 --> 00:24:38.050 align:start position:0% syntax highlighting like writing a syntax<00:24:37.010> highlighter<00:24:37.310> is<00:24:37.490> not<00:24:37.640> a<00:24:37.670> fun<00:24:38.030> thing 00:24:38.050 --> 00:24:38.060 align:start position:0% syntax highlighter is not a fun thing 00:24:38.060 --> 00:24:39.700 align:start position:0% syntax highlighter is not a fun thing but<00:24:38.570> it's<00:24:38.690> something<00:24:38.780> that<00:24:38.960> you<00:24:39.080> kind<00:24:39.530> of<00:24:39.650> want 00:24:39.700 --> 00:24:39.710 align:start position:0% but it's something that you kind of want 00:24:39.710 --> 00:24:40.840 align:start position:0% but it's something that you kind of want and<00:24:40.070> that's<00:24:40.160> something<00:24:40.430> you<00:24:40.490> just<00:24:40.580> have<00:24:40.670> to 00:24:40.840 --> 00:24:40.850 align:start position:0% and that's something you just have to 00:24:40.850 --> 00:24:42.820 align:start position:0% and that's something you just have to write<00:24:41.030> if<00:24:41.570> you're<00:24:41.990> doing<00:24:42.200> your<00:24:42.320> own<00:24:42.350> like 00:24:42.820 --> 00:24:42.830 align:start position:0% write if you're doing your own like 00:24:42.830 --> 00:24:47.830 align:start position:0% write if you're doing your own like random<00:24:43.670> stuff<00:24:43.940> I<00:24:46.390> think<00:24:47.390> another<00:24:47.600> cool 00:24:47.830 --> 00:24:47.840 align:start position:0% random stuff I think another cool 00:24:47.840 --> 00:24:50.050 align:start position:0% random stuff I think another cool approach<00:24:48.200> is<00:24:48.590> to<00:24:48.890> have<00:24:48.920> languages<00:24:49.610> which<00:24:49.880> are 00:24:50.050 --> 00:24:50.060 align:start position:0% approach is to have languages which are 00:24:50.060 --> 00:24:53.220 align:start position:0% approach is to have languages which are less<00:24:50.330> capable<00:24:51.430> basically<00:24:52.430> like<00:24:52.580> Babbage 00:24:53.220 --> 00:24:53.230 align:start position:0% less capable basically like Babbage 00:24:53.230 --> 00:24:56.170 align:start position:0% less capable basically like Babbage which<00:24:54.230> and<00:24:55.220> I<00:24:55.310> don't<00:24:55.490> know<00:24:55.610> the<00:24:55.730> details<00:24:56.090> of 00:24:56.170 --> 00:24:56.180 align:start position:0% which and I don't know the details of 00:24:56.180 --> 00:24:59.260 align:start position:0% which and I don't know the details of this<00:24:56.300> but<00:24:56.540> I<00:24:56.630> I<00:24:56.660> think<00:24:56.930> that<00:24:57.350> Babbage<00:24:57.890> is<00:24:58.280> a<00:24:58.970> lot 00:24:59.260 --> 00:24:59.270 align:start position:0% this but I I think that Babbage is a lot 00:24:59.270 --> 00:25:02.230 align:start position:0% this but I I think that Babbage is a lot more<00:24:59.690> restricted<00:25:00.470> in<00:25:00.590> what<00:25:00.800> it<00:25:00.920> can<00:25:01.160> do<00:25:01.520> but 00:25:02.230 --> 00:25:02.240 align:start position:0% more restricted in what it can do but 00:25:02.240 --> 00:25:03.880 align:start position:0% more restricted in what it can do but can<00:25:02.450> thus<00:25:02.630> provide<00:25:03.080> a<00:25:03.110> great 00:25:03.880 --> 00:25:03.890 align:start position:0% can thus provide a great 00:25:03.890 --> 00:25:06.790 align:start position:0% can thus provide a great safety<00:25:04.400> about<00:25:04.880> the<00:25:05.270> you<00:25:05.900> know<00:25:05.930> potential<00:25:06.590> post 00:25:06.790 --> 00:25:06.800 align:start position:0% safety about the you know potential post 00:25:06.800 --> 00:25:10.740 align:start position:0% safety about the you know potential post states<00:25:07.340> after<00:25:07.640> the<00:25:08.150> execution<00:25:09.700> great 00:25:10.740 --> 00:25:10.750 align:start position:0% states after the execution great 00:25:10.750 --> 00:25:12.790 align:start position:0% states after the execution great unfortunately<00:25:11.750> that's<00:25:11.930> all<00:25:12.410> we<00:25:12.500> have<00:25:12.620> time 00:25:12.790 --> 00:25:12.800 align:start position:0% unfortunately that's all we have time 00:25:12.800 --> 00:25:14.800 align:start position:0% unfortunately that's all we have time for<00:25:12.860> so<00:25:13.490> thank<00:25:14.150> you<00:25:14.270> very<00:25:14.390> much<00:25:14.600> to<00:25:14.780> my 00:25:14.800 --> 00:25:14.810 align:start position:0% for so thank you very much to my 00:25:14.810 --> 00:25:22.930 align:start position:0% for so thank you very much to my distinguished<00:25:15.350> panelists<00:25:15.890> thank<00:25:16.250> you<00:25:21.940> up 00:25:22.930 --> 00:25:22.940 align:start position:0% distinguished panelists thank you up 00:25:22.940 --> 00:25:25.300 align:start position:0% distinguished panelists thank you up next<00:25:23.450> we<00:25:23.600> have<00:25:23.720> another<00:25:24.050> panel<00:25:24.320> on<00:25:24.590> formal 00:25:25.300 --> 00:25:25.310 align:start position:0% next we have another panel on formal 00:25:25.310 --> 00:25:38.710 align:start position:0% next we have another panel on formal verification<00:25:25.990> moderated<00:25:26.990> by<00:25:27.020> Rito<00:25:27.710> drinkler 00:25:38.710 --> 00:25:38.720 align:start position:0% 00:25:38.720 --> 00:25:41.020 align:start position:0% you 00:25:41.020 --> 00:25:41.030 align:start position:0% 00:25:41.030 --> 00:25:48.609 align:start position:0% [Music]