WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.980 align:start position:0% [Applause] 00:00:11.980 --> 00:00:11.990 align:start position:0% 00:00:11.990 --> 00:00:16.870 align:start position:0% all<00:00:12.990> right<00:00:13.170> I<00:00:13.410> am<00:00:14.219> the<00:00:14.580> rook<00:00:14.879> I<00:00:15.120> am<00:00:15.360> the<00:00:15.600> lead<00:00:15.990> on 00:00:16.870 --> 00:00:16.880 align:start position:0% all right I am the rook I am the lead on 00:00:16.880 --> 00:00:20.780 align:start position:0% all right I am the rook I am the lead on ganache<00:00:17.880> that<00:00:17.910> trouble<00:00:18.630> and<00:00:19.250> this<00:00:20.250> here<00:00:20.520> is 00:00:20.780 --> 00:00:20.790 align:start position:0% ganache that trouble and this here is 00:00:20.790 --> 00:00:24.620 align:start position:0% ganache that trouble and this here is the<00:00:21.270> eternal<00:00:22.849> blockchain<00:00:23.849> engine<00:00:24.330> or 00:00:24.620 --> 00:00:24.630 align:start position:0% the eternal blockchain engine or 00:00:24.630 --> 00:00:27.019 align:start position:0% the eternal blockchain engine or engineer<00:00:24.990> consider<00:00:25.859> in<00:00:26.130> this<00:00:26.250> light<00:00:26.400> so<00:00:26.699> it's 00:00:27.019 --> 00:00:27.029 align:start position:0% engineer consider in this light so it's 00:00:27.029 --> 00:00:30.200 align:start position:0% engineer consider in this light so it's shortened<00:00:28.369> and<00:00:29.369> we're<00:00:29.520> going<00:00:29.670> to<00:00:29.760> get<00:00:29.820> in 00:00:30.200 --> 00:00:30.210 align:start position:0% shortened and we're going to get in 00:00:30.210 --> 00:00:34.130 align:start position:0% shortened and we're going to get in trouble<00:00:30.300> teams<00:00:30.890> yeah<00:00:31.890> so<00:00:32.250> if<00:00:32.900> you<00:00:33.900> have<00:00:33.989> can 00:00:34.130 --> 00:00:34.140 align:start position:0% trouble teams yeah so if you have can 00:00:34.140 --> 00:00:36.560 align:start position:0% trouble teams yeah so if you have can ask<00:00:34.260> questions<00:00:34.650> we<00:00:35.040> are<00:00:35.239> the<00:00:36.239> people<00:00:36.540> that 00:00:36.560 --> 00:00:36.570 align:start position:0% ask questions we are the people that 00:00:36.570 --> 00:00:43.100 align:start position:0% ask questions we are the people that trouble<00:00:37.170> to<00:00:37.290> ask<00:00:41.239> so<00:00:42.239> you<00:00:42.300> all<00:00:42.480> probably<00:00:42.840> know 00:00:43.100 --> 00:00:43.110 align:start position:0% trouble to ask so you all probably know 00:00:43.110 --> 00:00:45.680 align:start position:0% trouble to ask so you all probably know who<00:00:43.530> truffle<00:00:44.160> is<00:00:44.280> known<00:00:44.820> residents<00:00:45.360> and<00:00:45.540> do 00:00:45.680 --> 00:00:45.690 align:start position:0% who truffle is known residents and do 00:00:45.690 --> 00:00:49.760 align:start position:0% who truffle is known residents and do what<00:00:45.899> to<00:00:46.020> anyone<00:00:48.050> but<00:00:49.050> if<00:00:49.170> you<00:00:49.290> don't 00:00:49.760 --> 00:00:49.770 align:start position:0% what to anyone but if you don't 00:00:49.770 --> 00:00:52.910 align:start position:0% what to anyone but if you don't so<00:00:49.980> truffle<00:00:50.520> is<00:00:50.820> a<00:00:50.850> company<00:00:51.329> whose<00:00:51.660> goal<00:00:51.930> is<00:00:52.680> to 00:00:52.910 --> 00:00:52.920 align:start position:0% so truffle is a company whose goal is to 00:00:52.920 --> 00:00:54.950 align:start position:0% so truffle is a company whose goal is to build<00:00:53.040> tools<00:00:53.340> to<00:00:53.610> get<00:00:53.700> developers<00:00:54.210> from<00:00:54.480> idea 00:00:54.950 --> 00:00:54.960 align:start position:0% build tools to get developers from idea 00:00:54.960 --> 00:01:00.110 align:start position:0% build tools to get developers from idea to<00:00:55.320> death<00:00:55.530> as<00:00:55.829> comfortably<00:00:56.789> as<00:00:56.879> possible<00:00:59.059> so<00:01:00.059> I 00:01:00.110 --> 00:01:00.120 align:start position:0% to death as comfortably as possible so I 00:01:00.120 --> 00:01:04.450 align:start position:0% to death as comfortably as possible so I think<00:01:00.239> sums<00:01:00.840> up<00:01:01.020> our<00:01:01.289> our<00:01:01.980> goal<00:01:03.170> pretty<00:01:04.170> well 00:01:04.450 --> 00:01:04.460 align:start position:0% think sums up our our goal pretty well 00:01:04.460 --> 00:01:09.910 align:start position:0% think sums up our our goal pretty well so<00:01:05.460> we<00:01:05.580> have<00:01:05.729> three<00:01:06.119> or<00:01:06.930> four<00:01:06.960> but<00:01:07.560> three<00:01:08.570> main 00:01:09.910 --> 00:01:09.920 align:start position:0% so we have three or four but three main 00:01:09.920 --> 00:01:13.030 align:start position:0% so we have three or four but three main open-source<00:01:10.920> tools<00:01:11.300> someone<00:01:12.300> is<00:01:12.420> truffle 00:01:13.030 --> 00:01:13.040 align:start position:0% open-source tools someone is truffle 00:01:13.040 --> 00:01:16.010 align:start position:0% open-source tools someone is truffle which<00:01:14.040> is<00:01:14.310> a<00:01:14.670> dev<00:01:15.060> environment<00:01:15.090> testing 00:01:16.010 --> 00:01:16.020 align:start position:0% which is a dev environment testing 00:01:16.020 --> 00:01:18.050 align:start position:0% which is a dev environment testing chamber<00:01:16.200> in<00:01:16.650> NASA<00:01:16.830> pipe<00:01:17.159> pipe<00:01:17.670> line<00:01:17.850> for 00:01:18.050 --> 00:01:18.060 align:start position:0% chamber in NASA pipe pipe line for 00:01:18.060 --> 00:01:18.710 align:start position:0% chamber in NASA pipe pipe line for blockchains 00:01:18.710 --> 00:01:18.720 align:start position:0% blockchains 00:01:18.720 --> 00:01:20.870 align:start position:0% blockchains drizzle<00:01:19.530> is<00:01:19.710> a<00:01:19.740> front-end<00:01:20.189> library<00:01:20.549> for<00:01:20.729> gaps 00:01:20.870 --> 00:01:20.880 align:start position:0% drizzle is a front-end library for gaps 00:01:20.880 --> 00:01:23.149 align:start position:0% drizzle is a front-end library for gaps and<00:01:21.150> then<00:01:21.240> of<00:01:21.330> course<00:01:21.470> ganache<00:01:22.470> which<00:01:22.770> is<00:01:22.920> your 00:01:23.149 --> 00:01:23.159 align:start position:0% and then of course ganache which is your 00:01:23.159 --> 00:01:26.980 align:start position:0% and then of course ganache which is your one<00:01:23.490> clique<00:01:23.760> blockchain<00:01:25.189> so<00:01:26.189> what<00:01:26.340> is<00:01:26.460> ganache 00:01:26.980 --> 00:01:26.990 align:start position:0% one clique blockchain so what is ganache 00:01:26.990 --> 00:01:29.630 align:start position:0% one clique blockchain so what is ganache so<00:01:27.990> ganache<00:01:28.200> actually<00:01:28.530> comes<00:01:28.740> in<00:01:28.890> three 00:01:29.630 --> 00:01:29.640 align:start position:0% so ganache actually comes in three 00:01:29.640 --> 00:01:31.609 align:start position:0% so ganache actually comes in three variants<00:01:30.299> and<00:01:30.630> most<00:01:31.200> people<00:01:31.380> think<00:01:31.470> of 00:01:31.609 --> 00:01:31.619 align:start position:0% variants and most people think of 00:01:31.619 --> 00:01:34.399 align:start position:0% variants and most people think of ganache<00:01:31.979> as<00:01:32.250> the<00:01:32.460> UI<00:01:32.930> what<00:01:33.930> you<00:01:33.990> guys<00:01:34.080> think 00:01:34.399 --> 00:01:34.409 align:start position:0% ganache as the UI what you guys think 00:01:34.409 --> 00:01:39.050 align:start position:0% ganache as the UI what you guys think like<00:01:35.420> who's<00:01:36.420> here<00:01:36.659> it<00:01:37.350> not<00:01:37.829> who<00:01:38.400> is<00:01:38.520> aware<00:01:38.759> of 00:01:39.050 --> 00:01:39.060 align:start position:0% like who's here it not who is aware of 00:01:39.060 --> 00:01:44.149 align:start position:0% like who's here it not who is aware of UI<00:01:39.630> and<00:01:40.140> CLI<00:01:40.829> and<00:01:41.189> core<00:01:42.170> so<00:01:43.170> who<00:01:43.470> hasn't<00:01:43.979> heard 00:01:44.149 --> 00:01:44.159 align:start position:0% UI and CLI and core so who hasn't heard 00:01:44.159 --> 00:01:47.109 align:start position:0% UI and CLI and core so who hasn't heard of<00:01:44.509> one<00:01:45.509> of<00:01:45.659> those<00:01:45.810> things 00:01:47.109 --> 00:01:47.119 align:start position:0% of one of those things 00:01:47.119 --> 00:01:53.720 align:start position:0% of one of those things wait<00:01:48.119> which<00:01:48.299> one<00:01:48.920> core<00:01:49.920> okay<00:01:50.570> anyone<00:01:51.570> else 00:01:53.720 --> 00:01:53.730 align:start position:0% wait which one core okay anyone else 00:01:53.730 --> 00:01:59.580 align:start position:0% wait which one core okay anyone else okay<00:01:54.730> sir<00:01:55.360> core<00:01:56.910> core<00:01:57.910> is<00:01:58.240> the<00:01:58.960> part<00:01:59.260> of 00:01:59.580 --> 00:01:59.590 align:start position:0% okay sir core core is the part of 00:01:59.590 --> 00:02:02.120 align:start position:0% okay sir core core is the part of ganache<00:02:00.310> that<00:02:00.340> does<00:02:01.000> all<00:02:01.360> the<00:02:01.390> heavy<00:02:01.600> lifting 00:02:02.120 --> 00:02:02.130 align:start position:0% ganache that does all the heavy lifting 00:02:02.130 --> 00:02:05.520 align:start position:0% ganache that does all the heavy lifting and<00:02:03.130> so<00:02:03.490> ganache<00:02:04.360> core<00:02:04.600> is<00:02:04.780> a<00:02:04.810> separate<00:02:05.200> MPM 00:02:05.520 --> 00:02:05.530 align:start position:0% and so ganache core is a separate MPM 00:02:05.530 --> 00:02:09.270 align:start position:0% and so ganache core is a separate MPM projects<00:02:05.980> that<00:02:07.530> CLI<00:02:08.530> actually<00:02:08.950> this<00:02:09.070> wraps 00:02:09.270 --> 00:02:09.280 align:start position:0% projects that CLI actually this wraps 00:02:09.280 --> 00:02:13.590 align:start position:0% projects that CLI actually this wraps around<00:02:09.810> so<00:02:10.810> if<00:02:11.410> you<00:02:11.560> do<00:02:11.710> like<00:02:12.180> require<00:02:13.180> ganache 00:02:13.590 --> 00:02:13.600 align:start position:0% around so if you do like require ganache 00:02:13.600 --> 00:02:16.440 align:start position:0% around so if you do like require ganache pork<00:02:13.930> and<00:02:14.200> your<00:02:14.680> project<00:02:15.190> then<00:02:15.910> you<00:02:16.150> will<00:02:16.270> get 00:02:16.440 --> 00:02:16.450 align:start position:0% pork and your project then you will get 00:02:16.450 --> 00:02:18.360 align:start position:0% pork and your project then you will get the<00:02:16.570> provider<00:02:16.900> and<00:02:17.230> a<00:02:17.290> server<00:02:17.560> that<00:02:17.680> seal<00:02:18.340> I 00:02:18.360 --> 00:02:18.370 align:start position:0% the provider and a server that seal I 00:02:18.370 --> 00:02:21.120 align:start position:0% the provider and a server that seal I give<00:02:18.730> you<00:02:18.850> anything<00:02:19.890> access<00:02:20.890> at<00:02:21.040> the 00:02:21.120 --> 00:02:21.130 align:start position:0% give you anything access at the 00:02:21.130 --> 00:02:23.490 align:start position:0% give you anything access at the programmatic<00:02:21.400> axis<00:02:22.030> rather<00:02:22.540> today<00:02:22.840> on<00:02:23.380> the 00:02:23.490 --> 00:02:23.500 align:start position:0% programmatic axis rather today on the 00:02:23.500 --> 00:02:32.960 align:start position:0% programmatic axis rather today on the sea<00:02:23.620> life 00:02:32.960 --> 00:02:32.970 align:start position:0% 00:02:32.970 --> 00:02:35.370 align:start position:0% so<00:02:33.970> this<00:02:34.090> is<00:02:34.180> what<00:02:34.420> I<00:02:34.600> cannot<00:02:34.870> see<00:02:35.050> why<00:02:35.170> looks 00:02:35.370 --> 00:02:35.380 align:start position:0% so this is what I cannot see why looks 00:02:35.380 --> 00:02:39.480 align:start position:0% so this is what I cannot see why looks like<00:02:36.960> this<00:02:37.960> is<00:02:38.140> the<00:02:38.320> main<00:02:38.680> account<00:02:39.190> screen 00:02:39.480 --> 00:02:39.490 align:start position:0% like this is the main account screen 00:02:39.490 --> 00:02:42.930 align:start position:0% like this is the main account screen that<00:02:40.450> starts<00:02:40.780> up<00:02:40.900> you<00:02:41.080> get<00:02:41.520> 10<00:02:42.520> accounts<00:02:42.700> by 00:02:42.930 --> 00:02:42.940 align:start position:0% that starts up you get 10 accounts by 00:02:42.940 --> 00:02:46.500 align:start position:0% that starts up you get 10 accounts by default<00:02:43.560> you<00:02:44.560> have<00:02:44.650> a<00:02:44.790> mnemonic<00:02:45.790> don't<00:02:46.270> put 00:02:46.500 --> 00:02:46.510 align:start position:0% default you have a mnemonic don't put 00:02:46.510 --> 00:03:02.750 align:start position:0% default you have a mnemonic don't put that<00:02:46.690> on<00:02:47.790> that<00:02:48.790> please<00:02:52.470> assume<00:03:00.360> so<00:03:01.360> this<00:03:01.900> is 00:03:02.750 --> 00:03:02.760 align:start position:0% that on that please assume so this is 00:03:02.760 --> 00:03:05.730 align:start position:0% that on that please assume so this is trouble<00:03:03.760> contract<00:03:04.270> integration<00:03:04.810> so<00:03:05.080> if<00:03:05.530> you 00:03:05.730 --> 00:03:05.740 align:start position:0% trouble contract integration so if you 00:03:05.740 --> 00:03:08.730 align:start position:0% trouble contract integration so if you have<00:03:05.980> a<00:03:06.520> trouble<00:03:07.360> project<00:03:07.780> you<00:03:08.200> can<00:03:08.380> add<00:03:08.560> that 00:03:08.730 --> 00:03:08.740 align:start position:0% have a trouble project you can add that 00:03:08.740 --> 00:03:11.280 align:start position:0% have a trouble project you can add that to<00:03:08.800> your<00:03:09.040> Nashua<00:03:09.670> and<00:03:09.970> you<00:03:10.660> can<00:03:10.810> actually<00:03:11.080> see 00:03:11.280 --> 00:03:11.290 align:start position:0% to your Nashua and you can actually see 00:03:11.290 --> 00:03:13.350 align:start position:0% to your Nashua and you can actually see all<00:03:11.320> of<00:03:11.500> their<00:03:11.770> deployed<00:03:12.190> to<00:03:13.030> your<00:03:13.150> local 00:03:13.350 --> 00:03:13.360 align:start position:0% all of their deployed to your local 00:03:13.360 --> 00:03:15.900 align:start position:0% all of their deployed to your local cosmetic<00:03:13.870> gosh<00:03:14.490> contracts<00:03:15.490> there<00:03:15.640> how<00:03:15.850> many 00:03:15.900 --> 00:03:15.910 align:start position:0% cosmetic gosh contracts there how many 00:03:15.910 --> 00:03:18.420 align:start position:0% cosmetic gosh contracts there how many transactions<00:03:16.570> that<00:03:16.720> our<00:03:16.840> auditor<00:03:17.430> every 00:03:18.420 --> 00:03:18.430 align:start position:0% transactions that our auditor every 00:03:18.430 --> 00:03:24.990 align:start position:0% transactions that our auditor every useful<00:03:18.730> and<00:03:19.800> new<00:03:20.800> as<00:03:21.580> a<00:03:22.200> yesterday<00:03:24.000> ganache 00:03:24.990 --> 00:03:25.000 align:start position:0% useful and new as a yesterday ganache 00:03:25.000 --> 00:03:28.410 align:start position:0% useful and new as a yesterday ganache for<00:03:25.600> King<00:03:25.870> does<00:03:26.350> anyone<00:03:26.740> know<00:03:26.980> what<00:03:27.580> they're 00:03:28.410 --> 00:03:28.420 align:start position:0% for King does anyone know what they're 00:03:28.420 --> 00:03:32.880 align:start position:0% for King does anyone know what they're not<00:03:28.540> just<00:03:28.690> working<00:03:28.960> is<00:03:31.320> nobody<00:03:32.320> alright 00:03:32.880 --> 00:03:32.890 align:start position:0% not just working is nobody alright 00:03:32.890 --> 00:03:33.840 align:start position:0% not just working is nobody alright that's<00:03:33.280> fine 00:03:33.840 --> 00:03:33.850 align:start position:0% that's fine 00:03:33.850 --> 00:03:36.810 align:start position:0% that's fine cannot<00:03:34.480> see<00:03:34.810> alive<00:03:35.080> and<00:03:35.500> for<00:03:36.100> close<00:03:36.400> anyone 00:03:36.810 --> 00:03:36.820 align:start position:0% cannot see alive and for close anyone 00:03:36.820 --> 00:03:40.590 align:start position:0% cannot see alive and for close anyone seen<00:03:37.030> that<00:03:37.590> do<00:03:38.590> okay<00:03:39.580> alright<00:03:40.239> you<00:03:40.330> come<00:03:40.450> up 00:03:40.590 --> 00:03:40.600 align:start position:0% seen that do okay alright you come up 00:03:40.600 --> 00:03:44.910 align:start position:0% seen that do okay alright you come up and<00:03:40.750> teach<00:03:41.400> good<00:03:43.110> so<00:03:44.110> ganache<00:03:44.380> poor<00:03:44.650> thing<00:03:44.830> is 00:03:44.910 --> 00:03:44.920 align:start position:0% and teach good so ganache poor thing is 00:03:44.920 --> 00:03:49.020 align:start position:0% and teach good so ganache poor thing is a<00:03:44.950> really<00:03:45.750> hidden<00:03:46.750> feature<00:03:47.260> of<00:03:47.650> cannot<00:03:48.130> it 00:03:49.020 --> 00:03:49.030 align:start position:0% a really hidden feature of cannot it 00:03:49.030 --> 00:03:51.300 align:start position:0% a really hidden feature of cannot it sounds<00:03:49.360> now<00:03:49.690> on<00:03:49.840> you<00:03:50.020> I<00:03:50.080> and<00:03:50.500> the<00:03:50.530> alpha 00:03:51.300 --> 00:03:51.310 align:start position:0% sounds now on you I and the alpha 00:03:51.310 --> 00:03:52.890 align:start position:0% sounds now on you I and the alpha version<00:03:51.459> you<00:03:51.850> guys<00:03:52.030> come<00:03:52.239> down<00:03:52.270> looking<00:03:52.750> over 00:03:52.890 --> 00:03:52.900 align:start position:0% version you guys come down looking over 00:03:52.900 --> 00:03:56.130 align:start position:0% version you guys come down looking over if<00:03:53.260> it<00:03:53.410> breaks<00:03:53.530> my<00:03:54.720> literally<00:03:55.720> posted 00:03:56.130 --> 00:03:56.140 align:start position:0% if it breaks my literally posted 00:03:56.140 --> 00:03:58.620 align:start position:0% if it breaks my literally posted yesterday<00:03:56.290> so<00:03:56.760> my<00:03:57.760> god<00:03:58.000> might<00:03:58.360> not<00:03:58.450> be<00:03:58.510> too 00:03:58.620 --> 00:03:58.630 align:start position:0% yesterday so my god might not be too 00:03:58.630 --> 00:04:04.910 align:start position:0% yesterday so my god might not be too stable<00:03:58.930> but<00:03:59.890> ganache<00:04:00.190> working<00:04:00.670> lets<00:04:01.060> you 00:04:04.910 --> 00:04:04.920 align:start position:0% 00:04:04.920 --> 00:04:08.160 align:start position:0% easily<00:04:05.920> easy<00:04:06.730> maintenance<00:04:07.180> thing<00:04:07.840> without 00:04:08.160 --> 00:04:08.170 align:start position:0% easily easy maintenance thing without 00:04:08.170 --> 00:04:11.430 align:start position:0% easily easy maintenance thing without the<00:04:08.410> cost<00:04:08.620> so<00:04:09.580> what<00:04:09.700> that<00:04:09.820> means<00:04:10.060> is<00:04:10.450> inside<00:04:11.110> of 00:04:11.430 --> 00:04:11.440 align:start position:0% the cost so what that means is inside of 00:04:11.440 --> 00:04:13.910 align:start position:0% the cost so what that means is inside of ganache<00:04:11.950> UI<00:04:12.280> you<00:04:12.730> can<00:04:12.760> now<00:04:13.090> select 00:04:13.910 --> 00:04:13.920 align:start position:0% ganache UI you can now select 00:04:13.920 --> 00:04:18.349 align:start position:0% ganache UI you can now select maintenance<00:04:15.630> like<00:04:16.630> from<00:04:16.840> Keira<00:04:17.230> as<00:04:17.770> provider 00:04:18.349 --> 00:04:18.359 align:start position:0% maintenance like from Keira as provider 00:04:18.359 --> 00:04:22.230 align:start position:0% maintenance like from Keira as provider or<00:04:19.359> you<00:04:19.510> put<00:04:19.750> your<00:04:19.870> own<00:04:19.900> provider<00:04:20.470> in<00:04:20.770> and<00:04:21.240> it's 00:04:22.230 --> 00:04:22.240 align:start position:0% or you put your own provider in and it's 00:04:22.240 --> 00:04:24.090 align:start position:0% or you put your own provider in and it's a<00:04:22.300> ganache<00:04:22.630> well<00:04:22.900> then<00:04:23.080> fork<00:04:23.470> at<00:04:23.710> a<00:04:23.770> specific 00:04:24.090 --> 00:04:24.100 align:start position:0% a ganache well then fork at a specific 00:04:24.100 --> 00:04:26.010 align:start position:0% a ganache well then fork at a specific block<00:04:24.550> number<00:04:24.850> that<00:04:24.970> you<00:04:25.060> specify<00:04:25.150> or<00:04:25.660> latest 00:04:26.010 --> 00:04:26.020 align:start position:0% block number that you specify or latest 00:04:26.020 --> 00:04:29.159 align:start position:0% block number that you specify or latest and<00:04:26.260> so<00:04:26.860> when<00:04:27.010> you<00:04:27.100> start<00:04:27.160> it<00:04:27.580> up<00:04:27.640> ganache<00:04:28.169> you 00:04:29.159 --> 00:04:29.169 align:start position:0% and so when you start it up ganache you 00:04:29.169 --> 00:04:30.350 align:start position:0% and so when you start it up ganache you will<00:04:29.290> actually<00:04:29.500> get 00:04:30.350 --> 00:04:30.360 align:start position:0% will actually get 00:04:30.360 --> 00:04:33.740 align:start position:0% will actually get instantly<00:04:30.810> well<00:04:31.650> a<00:04:31.680> couple<00:04:32.039> seconds<00:04:32.750> these 00:04:33.740 --> 00:04:33.750 align:start position:0% instantly well a couple seconds these 00:04:33.750 --> 00:04:35.869 align:start position:0% instantly well a couple seconds these are<00:04:33.960> these<00:04:34.199> are<00:04:34.229> mini<00:04:34.500> Matlock<00:04:34.919> members<00:04:35.250> right 00:04:35.869 --> 00:04:35.879 align:start position:0% are these are mini Matlock members right 00:04:35.879 --> 00:04:39.020 align:start position:0% are these are mini Matlock members right here<00:04:36.090> and<00:04:36.360> the<00:04:37.139> dates<00:04:37.319> that<00:04:37.469> they<00:04:37.620> remind<00:04:38.030> and 00:04:39.020 --> 00:04:39.030 align:start position:0% here and the dates that they remind and 00:04:39.030 --> 00:04:40.879 align:start position:0% here and the dates that they remind and I<00:04:39.210> Got<00:04:39.360> News<00:04:39.509> for<00:04:39.659> them<00:04:39.960> and<00:04:40.259> all<00:04:40.680> of<00:04:40.830> the 00:04:40.879 --> 00:04:40.889 align:start position:0% I Got News for them and all of the 00:04:40.889 --> 00:04:42.230 align:start position:0% I Got News for them and all of the transactions<00:04:41.490> are<00:04:41.580> here<00:04:41.729> without<00:04:41.939> sinking 00:04:42.230 --> 00:04:42.240 align:start position:0% transactions are here without sinking 00:04:42.240 --> 00:04:46.869 align:start position:0% transactions are here without sinking and<00:04:42.860> additionally<00:04:43.860> when<00:04:44.400> you<00:04:44.520> now<00:04:44.669> run<00:04:45.060> your 00:04:46.869 --> 00:04:46.879 align:start position:0% and additionally when you now run your 00:04:46.879 --> 00:04:50.749 align:start position:0% and additionally when you now run your contracts<00:04:47.990> against<00:04:48.990> your<00:04:49.500> local<00:04:49.979> ganache<00:04:50.280> it 00:04:50.749 --> 00:04:50.759 align:start position:0% contracts against your local ganache it 00:04:50.759 --> 00:04:54.920 align:start position:0% contracts against your local ganache it actually<00:04:51.120> emulates<00:04:51.900> being<00:04:52.800> on<00:04:52.919> beignet<00:04:53.930> that 00:04:54.920 --> 00:04:54.930 align:start position:0% actually emulates being on beignet that 00:04:54.930 --> 00:04:58.390 align:start position:0% actually emulates being on beignet that coverage<00:04:55.259> is<00:04:55.349> a<00:04:55.580> sound<00:04:56.580> good<00:04:56.699> so<00:04:57.300> so<00:04:57.719> risk<00:04:57.960> free 00:04:58.390 --> 00:04:58.400 align:start position:0% coverage is a sound good so so risk free 00:04:58.400 --> 00:05:01.159 align:start position:0% coverage is a sound good so so risk free no<00:04:59.400> cost<00:04:59.639> so<00:04:59.879> you<00:05:00.000> can<00:05:00.210> deploy<00:05:00.479> your<00:05:00.539> contracts 00:05:01.159 --> 00:05:01.169 align:start position:0% no cost so you can deploy your contracts 00:05:01.169 --> 00:05:05.450 align:start position:0% no cost so you can deploy your contracts to<00:05:02.039> ring<00:05:02.550> that<00:05:02.759> using<00:05:03.919> other<00:05:04.919> contracts<00:05:05.370> that 00:05:05.450 --> 00:05:05.460 align:start position:0% to ring that using other contracts that 00:05:05.460 --> 00:05:07.369 align:start position:0% to ring that using other contracts that are<00:05:05.580> employed<00:05:05.879> on<00:05:06.000> maintenance<00:05:06.210> oh<00:05:06.419> sorry<00:05:06.659> to 00:05:07.369 --> 00:05:07.379 align:start position:0% are employed on maintenance oh sorry to 00:05:07.379 --> 00:05:09.320 align:start position:0% are employed on maintenance oh sorry to ganache<00:05:07.710> you<00:05:07.949> I<00:05:07.979> like<00:05:08.759> it<00:05:08.909> was<00:05:09.000> on<00:05:09.120> maintenance 00:05:09.320 --> 00:05:09.330 align:start position:0% ganache you I like it was on maintenance 00:05:09.330 --> 00:05:12.290 align:start position:0% ganache you I like it was on maintenance so<00:05:09.659> it's<00:05:09.810> like<00:05:10.560> fully<00:05:10.800> emulating<00:05:11.430> men<00:05:12.120> yet 00:05:12.290 --> 00:05:12.300 align:start position:0% so it's like fully emulating men yet 00:05:12.300 --> 00:05:14.570 align:start position:0% so it's like fully emulating men yet maintenance<00:05:12.870> so<00:05:12.960> it's<00:05:13.080> like<00:05:13.199> you<00:05:13.289> fork<00:05:13.650> right 00:05:14.570 --> 00:05:14.580 align:start position:0% maintenance so it's like you fork right 00:05:14.580 --> 00:05:17.719 align:start position:0% maintenance so it's like you fork right at<00:05:14.729> this<00:05:14.879> lock<00:05:15.090> number<00:05:15.860> here<00:05:16.860> the<00:05:17.520> four 00:05:17.719 --> 00:05:17.729 align:start position:0% at this lock number here the four 00:05:17.729 --> 00:05:21.409 align:start position:0% at this lock number here the four o'clock<00:05:17.969> and<00:05:19.279> all<00:05:20.279> the<00:05:20.520> data<00:05:20.789> that<00:05:20.969> is<00:05:21.270> on 00:05:21.409 --> 00:05:21.419 align:start position:0% o'clock and all the data that is on 00:05:21.419 --> 00:05:23.330 align:start position:0% o'clock and all the data that is on magnetic<00:05:21.750> now<00:05:22.050> available<00:05:22.560> to<00:05:22.590> your<00:05:22.770> contracts 00:05:23.330 --> 00:05:23.340 align:start position:0% magnetic now available to your contracts 00:05:23.340 --> 00:05:26.659 align:start position:0% magnetic now available to your contracts under<00:05:23.610> what<00:05:23.789> she<00:05:24.650> paid<00:05:25.650> a<00:05:25.830> feature<00:05:26.069> any<00:05:26.460> new 00:05:26.659 --> 00:05:26.669 align:start position:0% under what she paid a feature any new 00:05:26.669 --> 00:05:29.029 align:start position:0% under what she paid a feature any new transactions<00:05:27.419> will<00:05:27.599> end<00:05:27.750> go<00:05:27.900> on<00:05:28.050> the<00:05:28.139> fork<00:05:28.439> so 00:05:29.029 --> 00:05:29.039 align:start position:0% transactions will end go on the fork so 00:05:29.039 --> 00:05:31.850 align:start position:0% transactions will end go on the fork so you're<00:05:29.189> sort<00:05:29.310> of<00:05:29.400> risk<00:05:29.639> free<00:05:30.020> access<00:05:31.020> and<00:05:31.289> if 00:05:31.850 --> 00:05:31.860 align:start position:0% you're sort of risk free access and if 00:05:31.860 --> 00:05:34.129 align:start position:0% you're sort of risk free access and if you<00:05:31.949> had<00:05:32.129> sort<00:05:32.370> of<00:05:32.460> to<00:05:32.819> access<00:05:33.210> say<00:05:33.419> some<00:05:33.840> seat 00:05:34.129 --> 00:05:34.139 align:start position:0% you had sort of to access say some seat 00:05:34.139 --> 00:05:36.140 align:start position:0% you had sort of to access say some seat or<00:05:34.379> data<00:05:34.620> that<00:05:34.740> was<00:05:35.009> previously<00:05:35.699> on<00:05:35.879> the<00:05:35.940> chain 00:05:36.140 --> 00:05:36.150 align:start position:0% or data that was previously on the chain 00:05:36.150 --> 00:05:39.309 align:start position:0% or data that was previously on the chain was<00:05:36.389> just<00:05:36.569> requested<00:05:37.020> from<00:05:37.139> your<00:05:37.860> provider 00:05:39.309 --> 00:05:39.319 align:start position:0% was just requested from your provider 00:05:39.319 --> 00:05:49.020 align:start position:0% was just requested from your provider questions 00:05:49.020 --> 00:05:49.030 align:start position:0% 00:05:49.030 --> 00:05:52.410 align:start position:0% yeah<00:05:49.540> so<00:05:49.780> we<00:05:50.020> actually<00:05:50.050> just<00:05:50.860> so<00:05:51.700> that<00:05:51.940> counts 00:05:52.410 --> 00:05:52.420 align:start position:0% yeah so we actually just so that counts 00:05:52.420 --> 00:05:54.570 align:start position:0% yeah so we actually just so that counts you<00:05:52.660> something<00:05:53.620> slides<00:05:53.860> back 00:05:54.570 --> 00:05:54.580 align:start position:0% you something slides back 00:05:54.580 --> 00:05:57.750 align:start position:0% you something slides back so<00:05:55.210> you<00:05:55.270> actually<00:05:55.890> the<00:05:56.890> way<00:05:57.010> that<00:05:57.190> works<00:05:57.370> is<00:05:57.520> we 00:05:57.750 --> 00:05:57.760 align:start position:0% so you actually the way that works is we 00:05:57.760 --> 00:05:59.910 align:start position:0% so you actually the way that works is we just<00:05:58.030> lie<00:05:58.210> to<00:05:58.270> the<00:05:58.600> state<00:05:58.870> and<00:05:59.410> we<00:05:59.560> just<00:05:59.740> say 00:05:59.910 --> 00:05:59.920 align:start position:0% just lie to the state and we just say 00:05:59.920 --> 00:06:02.730 align:start position:0% just lie to the state and we just say each<00:06:00.520> of<00:06:00.760> these<00:06:00.910> has<00:06:01.120> 108<00:06:01.720> that<00:06:02.230> says<00:06:02.470> just<00:06:02.620> the 00:06:02.730 --> 00:06:02.740 align:start position:0% each of these has 108 that says just the 00:06:02.740 --> 00:06:04.650 align:start position:0% each of these has 108 that says just the default<00:06:03.160> and<00:06:03.490> so<00:06:03.520> we<00:06:03.670> do<00:06:03.910> the<00:06:04.090> same<00:06:04.300> thing<00:06:04.540> with 00:06:04.650 --> 00:06:04.660 align:start position:0% default and so we do the same thing with 00:06:04.660 --> 00:06:07.200 align:start position:0% default and so we do the same thing with 14<00:06:05.080> as<00:06:05.230> soon<00:06:05.440> as<00:06:05.530> before<00:06:05.980> the<00:06:06.520> very<00:06:06.760> next<00:06:06.940> block 00:06:07.200 --> 00:06:07.210 align:start position:0% 14 as soon as before the very next block 00:06:07.210 --> 00:06:09.300 align:start position:0% 14 as soon as before the very next block number<00:06:07.660> is<00:06:07.780> an<00:06:07.870> empty<00:06:08.170> block<00:06:08.380> that<00:06:08.680> basically 00:06:09.300 --> 00:06:09.310 align:start position:0% number is an empty block that basically 00:06:09.310 --> 00:06:10.710 align:start position:0% number is an empty block that basically just<00:06:09.490> changes<00:06:09.880> the<00:06:10.030> state<00:06:10.210> we<00:06:10.360> just<00:06:10.510> kind<00:06:10.630> of 00:06:10.710 --> 00:06:10.720 align:start position:0% just changes the state we just kind of 00:06:10.720 --> 00:06:11.690 align:start position:0% just changes the state we just kind of forced<00:06:10.960> it<00:06:11.080> to<00:06:11.110> happen 00:06:11.690 --> 00:06:11.700 align:start position:0% forced it to happen 00:06:11.700 --> 00:06:14.100 align:start position:0% forced it to happen in<00:06:12.700> addition<00:06:13.030> on<00:06:13.150> that<00:06:13.360> note<00:06:13.570> actually<00:06:13.750> we 00:06:14.100 --> 00:06:14.110 align:start position:0% in addition on that note actually we 00:06:14.110 --> 00:06:18.600 align:start position:0% in addition on that note actually we also<00:06:14.290> allow<00:06:15.130> you<00:06:15.190> to<00:06:15.370> sort<00:06:15.760> of<00:06:17.190> pretend<00:06:18.190> to<00:06:18.460> be 00:06:18.600 --> 00:06:18.610 align:start position:0% also allow you to sort of pretend to be 00:06:18.610 --> 00:06:20.670 align:start position:0% also allow you to sort of pretend to be any<00:06:19.000> account<00:06:19.630> that<00:06:19.810> you<00:06:19.930> want<00:06:20.170> so<00:06:20.410> if<00:06:20.500> you<00:06:20.530> want 00:06:20.670 --> 00:06:20.680 align:start position:0% any account that you want so if you want 00:06:20.680 --> 00:06:24.030 align:start position:0% any account that you want so if you want it<00:06:20.890> to<00:06:20.980> be<00:06:22.290> issued<00:06:23.290> sends<00:06:23.500> actions<00:06:23.800> on<00:06:23.920> behalf 00:06:24.030 --> 00:06:24.040 align:start position:0% it to be issued sends actions on behalf 00:06:24.040 --> 00:06:25.710 align:start position:0% it to be issued sends actions on behalf of<00:06:24.310> account<00:06:24.610> that<00:06:24.700> you<00:06:24.880> have<00:06:24.910> you<00:06:25.210> being<00:06:25.360> you 00:06:25.710 --> 00:06:25.720 align:start position:0% of account that you have you being you 00:06:25.720 --> 00:06:35.790 align:start position:0% of account that you have you being you can<00:06:25.840> be<00:06:25.930> a<00:06:25.960> count<00:06:26.200> 0<00:06:26.260> if<00:06:26.590> you<00:06:26.680> want<00:06:26.860> bread<00:06:34.800> right 00:06:35.790 --> 00:06:35.800 align:start position:0% can be a count 0 if you want bread right 00:06:35.800 --> 00:06:37.050 align:start position:0% can be a count 0 if you want bread right doing<00:06:36.070> enterprise<00:06:36.400> are<00:06:36.610> you<00:06:36.670> gonna<00:06:36.790> you<00:06:37.030> can 00:06:37.050 --> 00:06:37.060 align:start position:0% doing enterprise are you gonna you can 00:06:37.060 --> 00:06:39.030 align:start position:0% doing enterprise are you gonna you can emulate<00:06:37.300> that<00:06:37.540> so<00:06:38.260> you<00:06:38.320> can<00:06:38.500> unlock<00:06:38.800> those 00:06:39.030 --> 00:06:39.040 align:start position:0% emulate that so you can unlock those 00:06:39.040 --> 00:06:46.590 align:start position:0% emulate that so you can unlock those accounts<00:06:39.400> if<00:06:39.460> you<00:06:39.550> want<00:06:39.700> to<00:06:45.360> so<00:06:46.360> you<00:06:46.420> can 00:06:46.590 --> 00:06:46.600 align:start position:0% accounts if you want to so you can 00:06:46.600 --> 00:06:48.690 align:start position:0% accounts if you want to so you can pretend<00:06:46.900> to<00:06:46.960> be<00:06:47.140> the<00:06:47.680> down<00:06:47.890> hacker<00:06:48.130> and<00:06:48.520> hacked 00:06:48.690 --> 00:06:48.700 align:start position:0% pretend to be the down hacker and hacked 00:06:48.700 --> 00:06:57.870 align:start position:0% pretend to be the down hacker and hacked it<00:06:48.820> out<00:06:53.430> so<00:06:56.040> to<00:06:57.040> me<00:06:57.160> the<00:06:57.460> theory<00:06:57.760> of 00:06:57.870 --> 00:06:57.880 align:start position:0% it out so to me the theory of 00:06:57.880 --> 00:07:00.990 align:start position:0% it out so to me the theory of development<00:06:58.570> is<00:06:59.700> kind<00:07:00.700> of<00:07:00.760> high<00:07:00.850> risk 00:07:00.990 --> 00:07:01.000 align:start position:0% development is kind of high risk 00:07:01.000 --> 00:07:04.650 align:start position:0% development is kind of high risk actually<00:07:01.360> earlier<00:07:01.960> today<00:07:02.230> we<00:07:02.920> burnt<00:07:03.660> some 00:07:04.650 --> 00:07:04.660 align:start position:0% actually earlier today we burnt some 00:07:04.660 --> 00:07:11.100 align:start position:0% actually earlier today we burnt some either<00:07:04.780> trying<00:07:05.440> to<00:07:05.500> deploy<00:07:07.410> and<00:07:09.900> we<00:07:10.900> shouldn't 00:07:11.100 --> 00:07:11.110 align:start position:0% either trying to deploy and we shouldn't 00:07:11.110 --> 00:07:15.900 align:start position:0% either trying to deploy and we shouldn't have<00:07:11.230> but<00:07:11.470> we<00:07:11.770> did<00:07:11.950> and<00:07:13.140> other<00:07:14.140> issues<00:07:15.100> or<00:07:15.610> your 00:07:15.900 --> 00:07:15.910 align:start position:0% have but we did and other issues or your 00:07:15.910 --> 00:07:17.580 align:start position:0% have but we did and other issues or your bytecode<00:07:16.300> is<00:07:16.390> public<00:07:16.720> so<00:07:16.900> you<00:07:16.930> can't<00:07:17.410> hide 00:07:17.580 --> 00:07:17.590 align:start position:0% bytecode is public so you can't hide 00:07:17.590 --> 00:07:20.970 align:start position:0% bytecode is public so you can't hide your<00:07:17.770> source<00:07:18.250> code<00:07:18.430> so<00:07:19.830> you<00:07:20.830> know<00:07:20.920> you 00:07:20.970 --> 00:07:20.980 align:start position:0% your source code so you know you 00:07:20.980 --> 00:07:24.390 align:start position:0% your source code so you know you shouldn't<00:07:21.430> use<00:07:21.910> obscurity<00:07:22.510> by<00:07:22.630> a<00:07:23.190> security<00:07:24.190> by 00:07:24.390 --> 00:07:24.400 align:start position:0% shouldn't use obscurity by a security by 00:07:24.400 --> 00:07:27.959 align:start position:0% shouldn't use obscurity by a security by obscurity<00:07:24.690> but<00:07:25.690> in<00:07:26.230> a<00:07:26.350> way<00:07:26.470> we<00:07:26.650> all<00:07:26.680> kind<00:07:27.010> of<00:07:27.100> do 00:07:27.959 --> 00:07:27.969 align:start position:0% obscurity but in a way we all kind of do 00:07:27.969 --> 00:07:30.659 align:start position:0% obscurity but in a way we all kind of do normal<00:07:28.780> development<00:07:29.199> but<00:07:30.129> theories<00:07:30.430> a<00:07:30.490> little 00:07:30.659 --> 00:07:30.669 align:start position:0% normal development but theories a little 00:07:30.669 --> 00:07:33.059 align:start position:0% normal development but theories a little different<00:07:31.050> all<00:07:32.050> your<00:07:32.229> contracts<00:07:32.590> are<00:07:32.740> public 00:07:33.059 --> 00:07:33.069 align:start position:0% different all your contracts are public 00:07:33.069 --> 00:07:35.129 align:start position:0% different all your contracts are public so<00:07:33.280> anyone<00:07:33.490> can<00:07:33.759> run<00:07:33.939> your<00:07:34.150> software<00:07:34.300> in<00:07:34.840> it<00:07:35.020> I 00:07:35.129 --> 00:07:35.139 align:start position:0% so anyone can run your software in it I 00:07:35.139 --> 00:07:39.059 align:start position:0% so anyone can run your software in it I think<00:07:35.409> you<00:07:35.469> all<00:07:35.560> know<00:07:35.590> this<00:07:35.889> but<00:07:38.069> meanwhile 00:07:39.059 --> 00:07:39.069 align:start position:0% think you all know this but meanwhile 00:07:39.069 --> 00:07:41.939 align:start position:0% think you all know this but meanwhile the<00:07:39.189> hackers<00:07:39.669> are<00:07:40.199> private<00:07:41.199> and<00:07:41.409> anonymous 00:07:41.939 --> 00:07:41.949 align:start position:0% the hackers are private and anonymous 00:07:41.949 --> 00:07:46.290 align:start position:0% the hackers are private and anonymous and<00:07:43.199> there's<00:07:44.199> no<00:07:44.319> recourse<00:07:44.529> for<00:07:45.249> if<00:07:45.729> your 00:07:46.290 --> 00:07:46.300 align:start position:0% and there's no recourse for if your 00:07:46.300 --> 00:07:48.390 align:start position:0% and there's no recourse for if your contract<00:07:47.050> constraint<00:07:47.439> you<00:07:47.560> don't<00:07:47.710> know<00:07:47.860> who 00:07:48.390 --> 00:07:48.400 align:start position:0% contract constraint you don't know who 00:07:48.400 --> 00:07:49.200 align:start position:0% contract constraint you don't know who that<00:07:48.520> is<00:07:48.580> it<00:07:48.849> is<00:07:48.939> no<00:07:49.060> jurisdiction 00:07:49.200 --> 00:07:49.210 align:start position:0% that is it is no jurisdiction 00:07:49.210 --> 00:07:52.170 align:start position:0% that is it is no jurisdiction jurisdiction<00:07:50.370> that<00:07:51.370> can<00:07:51.550> come<00:07:51.759> after<00:07:51.909> those 00:07:52.170 --> 00:07:52.180 align:start position:0% jurisdiction that can come after those 00:07:52.180 --> 00:07:56.100 align:start position:0% jurisdiction that can come after those people<00:07:53.340> so<00:07:54.340> if<00:07:54.430> you<00:07:54.550> mess<00:07:54.699> up<00:07:54.840> you<00:07:55.840> or<00:07:55.990> your 00:07:56.100 --> 00:07:56.110 align:start position:0% people so if you mess up you or your 00:07:56.110 --> 00:07:57.300 align:start position:0% people so if you mess up you or your users<00:07:56.499> lose<00:07:56.740> big 00:07:57.300 --> 00:07:57.310 align:start position:0% users lose big 00:07:57.310 --> 00:08:01.649 align:start position:0% users lose big it's<00:07:57.669> your<00:07:57.819> recourse<00:07:58.319> so<00:08:00.090> some<00:08:01.090> key<00:08:01.270> concepts 00:08:01.649 --> 00:08:01.659 align:start position:0% it's your recourse so some key concepts 00:08:01.659 --> 00:08:03.480 align:start position:0% it's your recourse so some key concepts are<00:08:01.750> gonna<00:08:02.169> go<00:08:02.349> over<00:08:02.379> this<00:08:02.560> real<00:08:02.800> quick 00:08:03.480 --> 00:08:03.490 align:start position:0% are gonna go over this real quick 00:08:03.490 --> 00:08:05.909 align:start position:0% are gonna go over this real quick gasps<00:08:03.849> fallback<00:08:04.389> functions<00:08:04.750> and<00:08:04.990> re-entrant 00:08:05.909 --> 00:08:05.919 align:start position:0% gasps fallback functions and re-entrant 00:08:05.919 --> 00:08:12.230 align:start position:0% gasps fallback functions and re-entrant see<00:08:08.879> sorry<00:08:09.879> I<00:08:09.909> can<00:08:10.090> actually<00:08:10.210> see<00:08:10.539> that<00:08:10.689> slide 00:08:12.230 --> 00:08:12.240 align:start position:0% see sorry I can actually see that slide 00:08:12.240 --> 00:08:14.700 align:start position:0% see sorry I can actually see that slide to<00:08:13.240> transact<00:08:13.659> on<00:08:13.810> theory<00:08:14.080> you<00:08:14.229> must<00:08:14.409> pay<00:08:14.590> a<00:08:14.620> fee 00:08:14.700 --> 00:08:14.710 align:start position:0% to transact on theory you must pay a fee 00:08:14.710 --> 00:08:17.219 align:start position:0% to transact on theory you must pay a fee this<00:08:15.129> fee<00:08:15.279> is<00:08:15.310> paid<00:08:15.639> gasps<00:08:16.020> gasps<00:08:17.020> the 00:08:17.219 --> 00:08:17.229 align:start position:0% this fee is paid gasps gasps the 00:08:17.229 --> 00:08:19.550 align:start position:0% this fee is paid gasps gasps the faithful<00:08:17.590> and<00:08:17.740> Ethan<00:08:18.069> operations<00:08:18.789> on<00:08:18.939> areum 00:08:19.550 --> 00:08:19.560 align:start position:0% faithful and Ethan operations on areum 00:08:19.560 --> 00:08:22.019 align:start position:0% faithful and Ethan operations on areum likes<00:08:20.560> or<00:08:20.740> the<00:08:20.860> changing<00:08:21.159> data<00:08:21.370> transferring 00:08:22.019 --> 00:08:22.029 align:start position:0% likes or the changing data transferring 00:08:22.029 --> 00:08:25.619 align:start position:0% likes or the changing data transferring funds<00:08:22.360> math<00:08:23.259> operations<00:08:23.830> looping<00:08:24.629> collect 00:08:25.619 --> 00:08:25.629 align:start position:0% funds math operations looping collect 00:08:25.629 --> 00:08:28.469 align:start position:0% funds math operations looping collect requires<00:08:26.139> some<00:08:26.589> amount<00:08:26.680> deaths<00:08:27.479> generally 00:08:28.469 --> 00:08:28.479 align:start position:0% requires some amount deaths generally 00:08:28.479 --> 00:08:30.480 align:start position:0% requires some amount deaths generally transaction<00:08:29.139> attempts<00:08:29.620> to<00:08:29.770> use<00:08:29.949> more<00:08:30.279> gas 00:08:30.480 --> 00:08:30.490 align:start position:0% transaction attempts to use more gas 00:08:30.490 --> 00:08:32.610 align:start position:0% transaction attempts to use more gas than<00:08:30.550> it<00:08:30.999> is<00:08:31.150> given<00:08:31.479> the<00:08:31.599> transaction<00:08:32.260> fails 00:08:32.610 --> 00:08:32.620 align:start position:0% than it is given the transaction fails 00:08:32.620 --> 00:08:38.430 align:start position:0% than it is given the transaction fails no<00:08:33.130> state<00:08:33.550> changes<00:08:34.060> birth<00:08:34.269> persisted<00:08:37.440> sonar 00:08:38.430 --> 00:08:38.440 align:start position:0% no state changes birth persisted sonar 00:08:38.440 --> 00:08:41.579 align:start position:0% no state changes birth persisted sonar fallout<00:08:38.860> functions<00:08:39.490> these<00:08:40.209> are<00:08:40.589> functions 00:08:41.579 --> 00:08:41.589 align:start position:0% fallout functions these are functions 00:08:41.589 --> 00:08:44.490 align:start position:0% fallout functions these are functions that<00:08:41.860> can<00:08:42.099> execute<00:08:42.579> operations<00:08:43.240> as<00:08:43.959> long<00:08:44.290> as 00:08:44.490 --> 00:08:44.500 align:start position:0% that can execute operations as long as 00:08:44.500 --> 00:08:47.040 align:start position:0% that can execute operations as long as there<00:08:44.680> were<00:08:44.769> enough<00:08:45.339> gas<00:08:45.640> for<00:08:45.670> t2<00:08:46.120> it<00:08:46.510> a 00:08:47.040 --> 00:08:47.050 align:start position:0% there were enough gas for t2 it a 00:08:47.050 --> 00:08:49.680 align:start position:0% there were enough gas for t2 it a fallback<00:08:47.410> function<00:08:47.860> must<00:08:48.100> be<00:08:48.480> external<00:08:49.480> and 00:08:49.680 --> 00:08:49.690 align:start position:0% fallback function must be external and 00:08:49.690 --> 00:08:51.329 align:start position:0% fallback function must be external and it<00:08:49.959> is<00:08:50.079> the<00:08:50.260> unnamed<00:08:50.680> function<00:08:51.130> in<00:08:51.220> their 00:08:51.329 --> 00:08:51.339 align:start position:0% it is the unnamed function in their 00:08:51.339 --> 00:08:53.730 align:start position:0% it is the unnamed function in their contract<00:08:51.760> it<00:08:52.570> is<00:08:52.630> called<00:08:52.959> for<00:08:53.110> any<00:08:53.320> contracts 00:08:53.730 --> 00:08:53.740 align:start position:0% contract it is called for any contracts 00:08:53.740 --> 00:08:56.790 align:start position:0% contract it is called for any contracts address<00:08:54.220> to<00:08:54.430> set<00:08:54.670> ether<00:08:55.060> or<00:08:55.630> a<00:08:56.140> non-existent 00:08:56.790 --> 00:08:56.800 align:start position:0% address to set ether or a non-existent 00:08:56.800 --> 00:08:59.790 align:start position:0% address to set ether or a non-existent contract<00:08:57.250> function<00:08:57.610> is<00:08:57.760> called<00:08:58.470> who<00:08:59.470> hasn't 00:08:59.790 --> 00:08:59.800 align:start position:0% contract function is called who hasn't 00:08:59.800 --> 00:09:05.590 align:start position:0% contract function is called who hasn't heard<00:08:59.890> of<00:09:00.040> public<00:09:00.640> functions 00:09:05.590 --> 00:09:05.600 align:start position:0% 00:09:05.600 --> 00:09:10.450 align:start position:0% I<00:09:05.800> almost<00:09:06.800> won't<00:09:07.640> go<00:09:07.850> through<00:09:08.390> this<00:09:09.370> skip<00:09:10.370> of 00:09:10.450 --> 00:09:10.460 align:start position:0% I almost won't go through this skip of 00:09:10.460 --> 00:09:15.150 align:start position:0% I almost won't go through this skip of that<00:09:10.870> and<00:09:12.550> re-entrance<00:09:13.550> e<00:09:13.640> Boehner<00:09:14.000> goalie 00:09:15.150 --> 00:09:15.160 align:start position:0% that and re-entrance e Boehner goalie 00:09:15.160 --> 00:09:22.860 align:start position:0% that and re-entrance e Boehner goalie does<00:09:16.160> anyone<00:09:16.400> know<00:09:16.520> what<00:09:16.790> that<00:09:16.850> is<00:09:17.440> already 00:09:22.860 --> 00:09:22.870 align:start position:0% 00:09:22.870 --> 00:09:27.850 align:start position:0% there<00:09:23.870> cup<00:09:24.080> of<00:09:24.350> you<00:09:24.560> so<00:09:24.800> this<00:09:24.890> is<00:09:24.950> fun<00:09:26.050> so<00:09:27.050> I 00:09:27.850 --> 00:09:27.860 align:start position:0% there cup of you so this is fun so I 00:09:27.860 --> 00:09:29.920 align:start position:0% there cup of you so this is fun so I don't<00:09:28.340> know<00:09:28.400> we<00:09:28.520> spent<00:09:28.820> like<00:09:29.210> an<00:09:29.390> hour<00:09:29.420> trying 00:09:29.920 --> 00:09:29.930 align:start position:0% don't know we spent like an hour trying 00:09:29.930 --> 00:09:32.740 align:start position:0% don't know we spent like an hour trying to<00:09:30.080> come<00:09:30.260> up<00:09:30.290> with<00:09:30.560> this<00:09:31.210> line<00:09:32.210> you<00:09:32.390> try<00:09:32.540> to<00:09:32.600> get 00:09:32.740 --> 00:09:32.750 align:start position:0% to come up with this line you try to get 00:09:32.750 --> 00:09:34.210 align:start position:0% to come up with this line you try to get it<00:09:32.840> down<00:09:32.930> to<00:09:33.080> one<00:09:33.230> direction<00:09:33.440> cringe<00:09:33.800> but<00:09:34.010> it's 00:09:34.210 --> 00:09:34.220 align:start position:0% it down to one direction cringe but it's 00:09:34.220 --> 00:09:39.640 align:start position:0% it down to one direction cringe but it's the<00:09:36.370> most<00:09:37.370> basic<00:09:37.790> way<00:09:38.240> I<00:09:38.270> can<00:09:38.810> define<00:09:39.050> Regency 00:09:39.640 --> 00:09:39.650 align:start position:0% the most basic way I can define Regency 00:09:39.650 --> 00:09:41.740 align:start position:0% the most basic way I can define Regency vulnerabilities<00:09:40.280> for<00:09:40.610> smart<00:09:41.030> contracts<00:09:41.480> is 00:09:41.740 --> 00:09:41.750 align:start position:0% vulnerabilities for smart contracts is 00:09:41.750 --> 00:09:44.790 align:start position:0% vulnerabilities for smart contracts is it's<00:09:42.740> when<00:09:42.980> a<00:09:43.010> contract<00:09:43.610> permits<00:09:43.910> unintended 00:09:44.790 --> 00:09:44.800 align:start position:0% it's when a contract permits unintended 00:09:44.800 --> 00:09:47.920 align:start position:0% it's when a contract permits unintended re<00:09:45.800> and<00:09:46.160> rotation<00:09:46.670> of<00:09:46.970> any<00:09:47.210> of<00:09:47.360> its<00:09:47.510> methods 00:09:47.920 --> 00:09:47.930 align:start position:0% re and rotation of any of its methods 00:09:47.930 --> 00:09:50.890 align:start position:0% re and rotation of any of its methods after<00:09:48.740> pulling<00:09:49.520> an<00:09:49.850> external<00:09:50.360> contract 00:09:50.890 --> 00:09:50.900 align:start position:0% after pulling an external contract 00:09:50.900 --> 00:09:52.870 align:start position:0% after pulling an external contract during<00:09:51.650> a<00:09:51.800> single<00:09:52.100> transaction 00:09:52.870 --> 00:09:52.880 align:start position:0% during a single transaction 00:09:52.880 --> 00:09:56.350 align:start position:0% during a single transaction it<00:09:53.540> was<00:09:53.660> pretty<00:09:53.840> dense<00:09:54.610> so<00:09:55.610> I'll<00:09:55.820> say<00:09:56.090> over 00:09:56.350 --> 00:09:56.360 align:start position:0% it was pretty dense so I'll say over 00:09:56.360 --> 00:09:57.910 align:start position:0% it was pretty dense so I'll say over time<00:09:56.390> where<00:09:57.050> the<00:09:57.140> contract<00:09:57.620> permits 00:09:57.910 --> 00:09:57.920 align:start position:0% time where the contract permits 00:09:57.920 --> 00:10:02.320 align:start position:0% time where the contract permits unintended<00:09:59.140> Rhian<00:10:00.140> vocation<00:10:00.680> of<00:10:00.800> any<00:10:01.190> of<00:10:02.180> its 00:10:02.320 --> 00:10:02.330 align:start position:0% unintended Rhian vocation of any of its 00:10:02.330 --> 00:10:08.530 align:start position:0% unintended Rhian vocation of any of its methods<00:10:04.330> during<00:10:05.330> a<00:10:05.480> single<00:10:05.840> transaction<00:10:07.540> so 00:10:08.530 --> 00:10:08.540 align:start position:0% methods during a single transaction so 00:10:08.540 --> 00:10:10.060 align:start position:0% methods during a single transaction so another<00:10:08.780> way<00:10:08.900> of<00:10:08.930> saying<00:10:09.020> it<00:10:09.350> smart<00:10:09.620> contract 00:10:10.060 --> 00:10:10.070 align:start position:0% another way of saying it smart contract 00:10:10.070 --> 00:10:11.440 align:start position:0% another way of saying it smart contract your<00:10:10.280> agency<00:10:10.730> allows<00:10:10.970> for<00:10:11.300> multiple 00:10:11.440 --> 00:10:11.450 align:start position:0% your agency allows for multiple 00:10:11.450 --> 00:10:13.720 align:start position:0% your agency allows for multiple applications<00:10:12.260> other<00:10:12.890> contexts<00:10:13.370> and<00:10:13.460> methods 00:10:13.720 --> 00:10:13.730 align:start position:0% applications other contexts and methods 00:10:13.730 --> 00:10:16.060 align:start position:0% applications other contexts and methods during<00:10:14.030> the<00:10:14.180> same<00:10:14.330> transaction<00:10:15.070> usually 00:10:16.060 --> 00:10:16.070 align:start position:0% during the same transaction usually 00:10:16.070 --> 00:10:18.610 align:start position:0% during the same transaction usually caused<00:10:16.340> by<00:10:16.610> forwarding<00:10:17.120> excess<00:10:17.510> guests<00:10:17.930> to<00:10:18.320> be 00:10:18.610 --> 00:10:18.620 align:start position:0% caused by forwarding excess guests to be 00:10:18.620 --> 00:10:20.170 align:start position:0% caused by forwarding excess guests to be malicious<00:10:18.980> to<00:10:19.190> contracts<00:10:19.760> while<00:10:20.000> that 00:10:20.170 --> 00:10:20.180 align:start position:0% malicious to contracts while that 00:10:20.180 --> 00:10:22.150 align:start position:0% malicious to contracts while that funding<00:10:20.540> them<00:10:20.660> without<00:10:21.080> proper<00:10:21.650> redundancy 00:10:22.150 --> 00:10:22.160 align:start position:0% funding them without proper redundancy 00:10:22.160 --> 00:10:25.900 align:start position:0% funding them without proper redundancy protection<00:10:23.860> so<00:10:24.860> that's<00:10:25.070> that's<00:10:25.400> there's<00:10:25.820> a 00:10:25.900 --> 00:10:25.910 align:start position:0% protection so that's that's there's a 00:10:25.910 --> 00:10:28.750 align:start position:0% protection so that's that's there's a lot<00:10:26.090> to<00:10:26.240> take<00:10:26.360> in<00:10:26.420> there<00:10:26.950> and<00:10:27.950> we're<00:10:28.430> gonna<00:10:28.520> get 00:10:28.750 --> 00:10:28.760 align:start position:0% lot to take in there and we're gonna get 00:10:28.760 --> 00:10:35.410 align:start position:0% lot to take in there and we're gonna get into<00:10:28.970> much<00:10:29.870> more<00:10:30.080> of<00:10:30.140> this<00:10:33.490> so<00:10:34.490> a<00:10:34.790> reentrant 00:10:35.410 --> 00:10:35.420 align:start position:0% into much more of this so a reentrant 00:10:35.420 --> 00:10:38.860 align:start position:0% into much more of this so a reentrant vulnerability<00:10:36.170> example<00:10:37.120> is<00:10:38.120> anyone<00:10:38.540> does 00:10:38.860 --> 00:10:38.870 align:start position:0% vulnerability example is anyone does 00:10:38.870 --> 00:10:40.840 align:start position:0% vulnerability example is anyone does anyone<00:10:39.110> know<00:10:39.320> actually<00:10:40.190> where<00:10:40.430> the 00:10:40.840 --> 00:10:40.850 align:start position:0% anyone know actually where the 00:10:40.850 --> 00:10:43.590 align:start position:0% anyone know actually where the vulnerability<00:10:41.480> is<00:10:41.510> and<00:10:42.050> this<00:10:42.170> code 00:10:43.590 --> 00:10:43.600 align:start position:0% vulnerability is and this code 00:10:43.600 --> 00:10:45.850 align:start position:0% vulnerability is and this code [Music] 00:10:45.850 --> 00:10:45.860 align:start position:0% [Music] 00:10:45.860 --> 00:10:49.120 align:start position:0% [Music] the<00:10:46.220> balances<00:10:46.700> he<00:10:46.820> loved<00:10:47.000> every<00:10:47.390> second<00:10:48.130> there 00:10:49.120 --> 00:10:49.130 align:start position:0% the balances he loved every second there 00:10:49.130 --> 00:10:50.949 align:start position:0% the balances he loved every second there was<00:10:49.430> another<00:10:49.790> Christmas<00:10:50.360> in<00:10:50.570> the<00:10:50.660> Camry 00:10:50.949 --> 00:10:50.959 align:start position:0% was another Christmas in the Camry 00:10:50.959 --> 00:10:52.110 align:start position:0% was another Christmas in the Camry contract 00:10:52.110 --> 00:10:52.120 align:start position:0% contract 00:10:52.120 --> 00:10:57.550 align:start position:0% contract that's<00:10:53.120> it<00:10:53.300> right<00:10:53.600> here<00:10:53.750> yeah<00:10:54.589> so<00:10:56.230> this<00:10:57.230> line 00:10:57.550 --> 00:10:57.560 align:start position:0% that's it right here yeah so this line 00:10:57.560 --> 00:11:00.130 align:start position:0% that's it right here yeah so this line right<00:10:57.860> here<00:10:57.920> is<00:10:58.399> a<00:10:58.640> reaction<00:10:59.000> similar<00:10:59.660> ability 00:11:00.130 --> 00:11:00.140 align:start position:0% right here is a reaction similar ability 00:11:00.140 --> 00:11:03.699 align:start position:0% right here is a reaction similar ability and<00:11:00.740> the<00:11:00.829> reason<00:11:01.190> for<00:11:01.220> that<00:11:01.430> is<00:11:02.529> centered<00:11:03.529> up 00:11:03.699 --> 00:11:03.709 align:start position:0% and the reason for that is centered up 00:11:03.709 --> 00:11:06.460 align:start position:0% and the reason for that is centered up call<00:11:04.010> of<00:11:04.250> value<00:11:04.700> go<00:11:05.300> pass<00:11:05.570> all<00:11:05.899> of<00:11:06.290> these 00:11:06.460 --> 00:11:06.470 align:start position:0% call of value go pass all of these 00:11:06.470 --> 00:11:09.970 align:start position:0% call of value go pass all of these remaining<00:11:07.120> gas<00:11:08.120> that's<00:11:08.959> left<00:11:09.290> for<00:11:09.800> this 00:11:09.970 --> 00:11:09.980 align:start position:0% remaining gas that's left for this 00:11:09.980 --> 00:11:16.000 align:start position:0% remaining gas that's left for this transaction<00:11:10.899> into<00:11:11.950> the<00:11:12.950> sender<00:11:14.410> and<00:11:15.410> sort<00:11:15.980> of 00:11:16.000 --> 00:11:16.010 align:start position:0% transaction into the sender and sort of 00:11:16.010 --> 00:11:18.190 align:start position:0% transaction into the sender and sort of send<00:11:16.279> there<00:11:16.430> is<00:11:16.610> a<00:11:16.640> contract<00:11:17.269> and<00:11:17.660> with<00:11:18.170> a 00:11:18.190 --> 00:11:18.200 align:start position:0% send there is a contract and with a 00:11:18.200 --> 00:11:20.769 align:start position:0% send there is a contract and with a fallback<00:11:18.470> function<00:11:19.070> that<00:11:19.640> is<00:11:19.790> payable<00:11:20.149> then 00:11:20.769 --> 00:11:20.779 align:start position:0% fallback function that is payable then 00:11:20.779 --> 00:11:22.660 align:start position:0% fallback function that is payable then the<00:11:20.959> sender<00:11:21.320> will<00:11:21.500> be<00:11:21.649> able<00:11:21.890> to<00:11:22.220> execute 00:11:22.660 --> 00:11:22.670 align:start position:0% the sender will be able to execute 00:11:22.670 --> 00:11:25.509 align:start position:0% the sender will be able to execute additional<00:11:23.600> transactions<00:11:24.430> after<00:11:25.430> the 00:11:25.509 --> 00:11:25.519 align:start position:0% additional transactions after the 00:11:25.519 --> 00:11:27.699 align:start position:0% additional transactions after the fallback<00:11:25.730> function<00:11:26.329> is<00:11:26.420> called<00:11:26.630> and<00:11:27.050> so<00:11:27.529> one 00:11:27.699 --> 00:11:27.709 align:start position:0% fallback function is called and so one 00:11:27.709 --> 00:11:29.860 align:start position:0% fallback function is called and so one of<00:11:27.740> those<00:11:27.890> transactions<00:11:28.519> may<00:11:28.760> be<00:11:28.820> to<00:11:29.240> recall 00:11:29.860 --> 00:11:29.870 align:start position:0% of those transactions may be to recall 00:11:29.870 --> 00:11:32.199 align:start position:0% of those transactions may be to recall withdrawal<00:11:30.430> and<00:11:31.430> I'm<00:11:31.579> the<00:11:31.670> problem<00:11:31.850> with<00:11:32.060> that 00:11:32.199 --> 00:11:32.209 align:start position:0% withdrawal and I'm the problem with that 00:11:32.209 --> 00:11:35.949 align:start position:0% withdrawal and I'm the problem with that is<00:11:32.540> that<00:11:32.890> this<00:11:33.890> line<00:11:34.190> will<00:11:34.399> execute<00:11:34.760> I<00:11:35.240> think<00:11:35.870> I 00:11:35.949 --> 00:11:35.959 align:start position:0% is that this line will execute I think I 00:11:35.959 --> 00:11:40.180 align:start position:0% is that this line will execute I think I have<00:11:36.140> all<00:11:36.260> this<00:11:36.410> data<00:11:36.620> so<00:11:36.950> here<00:11:37.600> wait<00:11:39.190> I'm 00:11:40.180 --> 00:11:40.190 align:start position:0% have all this data so here wait I'm 00:11:40.190 --> 00:11:40.960 align:start position:0% have all this data so here wait I'm getting<00:11:40.310> ahead<00:11:40.519> of<00:11:40.579> myself 00:11:40.960 --> 00:11:40.970 align:start position:0% getting ahead of myself 00:11:40.970 --> 00:12:16.530 align:start position:0% getting ahead of myself we'll<00:11:41.300> get<00:11:41.420> there<00:11:44.380> fast 00:12:16.530 --> 00:12:16.540 align:start position:0% 00:12:16.540 --> 00:12:18.480 align:start position:0% so<00:12:17.050> before<00:12:17.709> we<00:12:17.800> get<00:12:17.889> started<00:12:17.949> I'm<00:12:18.249> gonna<00:12:18.339> teach 00:12:18.480 --> 00:12:18.490 align:start position:0% so before we get started I'm gonna teach 00:12:18.490 --> 00:12:21.299 align:start position:0% so before we get started I'm gonna teach you<00:12:18.579> guys<00:12:18.699> how<00:12:19.059> to<00:12:19.179> do<00:12:19.329> this<00:12:19.860> this<00:12:20.860> remember 00:12:21.299 --> 00:12:21.309 align:start position:0% you guys how to do this this remember 00:12:21.309 --> 00:12:23.129 align:start position:0% you guys how to do this this remember just<00:12:21.819> because<00:12:21.999> you<00:12:22.089> can<00:12:22.300> doesn't<00:12:22.899> mean<00:12:23.050> you 00:12:23.129 --> 00:12:23.139 align:start position:0% just because you can doesn't mean you 00:12:23.139 --> 00:12:26.699 align:start position:0% just because you can doesn't mean you should<00:12:23.970> the<00:12:24.970> intent<00:12:25.360> of<00:12:25.540> this<00:12:25.779> workshop<00:12:26.259> is<00:12:26.319> to 00:12:26.699 --> 00:12:26.709 align:start position:0% should the intent of this workshop is to 00:12:26.709 --> 00:12:28.829 align:start position:0% should the intent of this workshop is to teach<00:12:26.889> you<00:12:27.009> how<00:12:27.160> to<00:12:27.189> protect<00:12:27.610> your<00:12:28.209> contracts 00:12:28.829 --> 00:12:28.839 align:start position:0% teach you how to protect your contracts 00:12:28.839 --> 00:12:32.069 align:start position:0% teach you how to protect your contracts is<00:12:29.679> not<00:12:30.009> to<00:12:30.579> teach<00:12:31.119> you<00:12:31.300> how<00:12:31.449> to<00:12:31.480> exploit 00:12:32.069 --> 00:12:32.079 align:start position:0% is not to teach you how to exploit 00:12:32.079 --> 00:12:35.489 align:start position:0% is not to teach you how to exploit others<00:12:32.439> contracts<00:12:33.720> so<00:12:34.720> don't<00:12:34.929> steal<00:12:35.139> all<00:12:35.350> the 00:12:35.489 --> 00:12:35.499 align:start position:0% others contracts so don't steal all the 00:12:35.499 --> 00:12:38.389 align:start position:0% others contracts so don't steal all the illegal<00:12:36.600> Unitas<00:12:37.600> people<00:12:37.899> this<00:12:38.110> is<00:12:38.290> for 00:12:38.389 --> 00:12:38.399 align:start position:0% illegal Unitas people this is for 00:12:38.399 --> 00:12:41.280 align:start position:0% illegal Unitas people this is for protesting<00:12:39.399> your<00:12:39.519> own<00:12:39.699> contracts<00:12:40.269> and<00:12:40.689> in<00:12:41.230> a 00:12:41.280 --> 00:12:41.290 align:start position:0% protesting your own contracts and in a 00:12:41.290 --> 00:12:44.939 align:start position:0% protesting your own contracts and in a real<00:12:41.439> world<00:12:41.619> scenario<00:12:41.829> yeah<00:12:43.559> so<00:12:44.559> don't<00:12:44.740> say 00:12:44.939 --> 00:12:44.949 align:start position:0% real world scenario yeah so don't say 00:12:44.949 --> 00:12:53.129 align:start position:0% real world scenario yeah so don't say truffle<00:12:45.339> talking<00:12:45.670> how<00:12:45.790> to<00:12:46.110> steal<00:12:51.569> okay<00:12:52.569> so<00:12:53.110> I 00:12:53.129 --> 00:12:53.139 align:start position:0% truffle talking how to steal okay so I 00:12:53.139 --> 00:12:54.629 align:start position:0% truffle talking how to steal okay so I was<00:12:53.290> getting<00:12:53.470> my<00:12:53.559> help<00:12:53.740> myself<00:12:54.100> there<00:12:54.459> I 00:12:54.629 --> 00:12:54.639 align:start position:0% was getting my help myself there I 00:12:54.639 --> 00:13:00.629 align:start position:0% was getting my help myself there I really<00:12:54.910> wanted<00:12:55.089> to<00:12:55.149> stir<00:12:55.749> this<00:12:55.959> so<00:12:58.800> this<00:12:59.800> would 00:13:00.629 --> 00:13:00.639 align:start position:0% really wanted to stir this so this would 00:13:00.639 --> 00:13:06.840 align:start position:0% really wanted to stir this so this would be<00:13:01.499> an<00:13:02.499> example<00:13:02.829> of<00:13:03.129> a<00:13:03.699> an<00:13:04.509> attackers<00:13:05.850> contract 00:13:06.840 --> 00:13:06.850 align:start position:0% be an example of a an attackers contract 00:13:06.850 --> 00:13:11.699 align:start position:0% be an example of a an attackers contract that<00:13:06.999> they<00:13:07.149> offload<00:13:07.569> in<00:13:07.749> order<00:13:08.379> to<00:13:08.679> be<00:13:09.129> bad<00:13:10.709> so 00:13:11.699 --> 00:13:11.709 align:start position:0% that they offload in order to be bad so 00:13:11.709 --> 00:13:13.169 align:start position:0% that they offload in order to be bad so I<00:13:11.740> miss<00:13:12.069> them<00:13:12.429> here<00:13:12.699> is<00:13:12.819> the<00:13:12.970> fallback 00:13:13.169 --> 00:13:13.179 align:start position:0% I miss them here is the fallback 00:13:13.179 --> 00:13:15.419 align:start position:0% I miss them here is the fallback function<00:13:13.779> and<00:13:14.019> so<00:13:14.529> we<00:13:14.860> saw<00:13:15.009> that<00:13:15.189> in<00:13:15.339> my 00:13:15.419 --> 00:13:15.429 align:start position:0% function and so we saw that in my 00:13:15.429 --> 00:13:18.179 align:start position:0% function and so we saw that in my contract<00:13:15.790> earlier<00:13:16.269> that<00:13:16.689> it<00:13:16.899> was<00:13:17.110> could<00:13:18.100> be 00:13:18.179 --> 00:13:18.189 align:start position:0% contract earlier that it was could be 00:13:18.189 --> 00:13:18.960 align:start position:0% contract earlier that it was could be reinserted 00:13:18.960 --> 00:13:18.970 align:start position:0% reinserted 00:13:18.970 --> 00:13:21.299 align:start position:0% reinserted and<00:13:19.329> so<00:13:19.899> I'll<00:13:20.019> show<00:13:20.230> you<00:13:20.259> how<00:13:20.559> that<00:13:20.800> works<00:13:20.949> here 00:13:21.299 --> 00:13:21.309 align:start position:0% and so I'll show you how that works here 00:13:21.309 --> 00:13:25.470 align:start position:0% and so I'll show you how that works here so<00:13:21.879> what<00:13:22.149> happens<00:13:22.509> is<00:13:23.579> initially<00:13:24.579> that<00:13:25.209> one<00:13:25.389> of 00:13:25.470 --> 00:13:25.480 align:start position:0% so what happens is initially that one of 00:13:25.480 --> 00:13:28.439 align:start position:0% so what happens is initially that one of the<00:13:25.540> cases<00:13:25.899> in<00:13:26.139> a<00:13:26.230> contract<00:13:26.709> is<00:13:27.069> to<00:13:28.059> see<00:13:28.269> it 00:13:28.439 --> 00:13:28.449 align:start position:0% the cases in a contract is to see it 00:13:28.449 --> 00:13:32.129 align:start position:0% the cases in a contract is to see it with<00:13:28.569> some<00:13:28.749> amount<00:13:29.139> of<00:13:29.230> value<00:13:30.600> and<00:13:31.600> so<00:13:31.870> what 00:13:32.129 --> 00:13:32.139 align:start position:0% with some amount of value and so what 00:13:32.139 --> 00:13:34.079 align:start position:0% with some amount of value and so what does<00:13:32.259> them<00:13:32.439> here's<00:13:32.740> it's<00:13:32.980> depositing<00:13:33.699> let's 00:13:34.079 --> 00:13:34.089 align:start position:0% does them here's it's depositing let's 00:13:34.089 --> 00:13:39.569 align:start position:0% does them here's it's depositing let's say<00:13:34.240> wine<00:13:34.480> and<00:13:34.689> ether<00:13:35.610> into<00:13:36.610> the<00:13:37.449> victim<00:13:38.579> the 00:13:39.569 --> 00:13:39.579 align:start position:0% say wine and ether into the victim the 00:13:39.579 --> 00:13:41.369 align:start position:0% say wine and ether into the victim the contract<00:13:40.029> was<00:13:40.120> all<00:13:40.299> just<00:13:40.569> couple<00:13:41.079> slides<00:13:41.230> ago 00:13:41.369 --> 00:13:41.379 align:start position:0% contract was all just couple slides ago 00:13:41.379 --> 00:13:43.799 align:start position:0% contract was all just couple slides ago into<00:13:42.069> that<00:13:42.220> contract<00:13:42.519> so<00:13:42.819> they<00:13:42.939> now<00:13:43.120> home<00:13:43.389> that 00:13:43.799 --> 00:13:43.809 align:start position:0% into that contract so they now home that 00:13:43.809 --> 00:13:46.049 align:start position:0% into that contract so they now home that anchor<00:13:44.199> as<00:13:44.769> a<00:13:44.829> barrel<00:13:45.429> imbalance<00:13:45.879> in<00:13:45.970> that 00:13:46.049 --> 00:13:46.059 align:start position:0% anchor as a barrel imbalance in that 00:13:46.059 --> 00:13:50.100 align:start position:0% anchor as a barrel imbalance in that contract<00:13:47.970> so<00:13:48.970> the<00:13:49.119> attacker<00:13:49.360> then<00:13:49.629> would<00:13:49.869> call 00:13:50.100 --> 00:13:50.110 align:start position:0% contract so the attacker then would call 00:13:50.110 --> 00:13:51.470 align:start position:0% contract so the attacker then would call the<00:13:50.350> BiPAP 00:13:51.470 --> 00:13:51.480 align:start position:0% the BiPAP 00:13:51.480 --> 00:13:53.420 align:start position:0% the BiPAP which<00:13:51.840> were<00:13:51.990> being<00:13:52.200> called<00:13:52.350> withdrawal<00:13:52.830> and 00:13:53.420 --> 00:13:53.430 align:start position:0% which were being called withdrawal and 00:13:53.430 --> 00:13:55.280 align:start position:0% which were being called withdrawal and now<00:13:53.550> this<00:13:53.760> would<00:13:54.090> all<00:13:54.210> work<00:13:54.420> wonderfully<00:13:55.050> so 00:13:55.280 --> 00:13:55.290 align:start position:0% now this would all work wonderfully so 00:13:55.290 --> 00:13:57.290 align:start position:0% now this would all work wonderfully so this<00:13:55.440> withdrawal<00:13:55.680> within<00:13:56.430> just<00:13:56.700> within<00:13:57.000> all 00:13:57.290 --> 00:13:57.300 align:start position:0% this withdrawal within just within all 00:13:57.300 --> 00:14:00.200 align:start position:0% this withdrawal within just within all this<00:13:57.510> one<00:13:57.720> has<00:13:57.930> got<00:13:58.260> value<00:13:58.650> but<00:13:59.580> because<00:13:59.610> of 00:14:00.200 --> 00:14:00.210 align:start position:0% this one has got value but because of 00:14:00.210 --> 00:14:02.150 align:start position:0% this one has got value but because of this<00:14:00.450> hacker<00:14:01.170> being<00:14:01.560> a<00:14:01.620> little<00:14:01.860> bit<00:14:01.950> clever 00:14:02.150 --> 00:14:02.160 align:start position:0% this hacker being a little bit clever 00:14:02.160 --> 00:14:04.490 align:start position:0% this hacker being a little bit clever they<00:14:02.610> implemented<00:14:03.450> this<00:14:03.630> whole<00:14:03.810> hat<00:14:03.990> function 00:14:04.490 --> 00:14:04.500 align:start position:0% they implemented this whole hat function 00:14:04.500 --> 00:14:08.890 align:start position:0% they implemented this whole hat function and<00:14:04.980> what<00:14:05.550> this<00:14:05.760> function<00:14:06.030> is<00:14:06.480> going<00:14:06.840> to<00:14:06.960> do<00:14:07.230> is 00:14:08.890 --> 00:14:08.900 align:start position:0% and what this function is going to do is 00:14:08.900 --> 00:14:13.310 align:start position:0% and what this function is going to do is after<00:14:10.520> the<00:14:11.520> original<00:14:11.730> contract<00:14:12.330> gets<00:14:12.990> this 00:14:13.310 --> 00:14:13.320 align:start position:0% after the original contract gets this 00:14:13.320 --> 00:14:18.350 align:start position:0% after the original contract gets this amount<00:14:13.980> from<00:14:14.220> them<00:14:14.400> from<00:14:14.850> the<00:14:16.460> caller<00:14:17.460> from 00:14:18.350 --> 00:14:18.360 align:start position:0% amount from them from the caller from 00:14:18.360 --> 00:14:20.300 align:start position:0% amount from them from the caller from this<00:14:18.570> concept<00:14:18.900> here<00:14:19.200> it'll<00:14:19.950> get<00:14:20.100> their 00:14:20.300 --> 00:14:20.310 align:start position:0% this concept here it'll get their 00:14:20.310 --> 00:14:23.360 align:start position:0% this concept here it'll get their balance<00:14:20.850> and<00:14:21.180> it<00:14:22.080> will<00:14:22.320> record<00:14:22.770> that<00:14:22.860> and<00:14:23.220> then 00:14:23.360 --> 00:14:23.370 align:start position:0% balance and it will record that and then 00:14:23.370 --> 00:14:26.540 align:start position:0% balance and it will record that and then send<00:14:23.790> that<00:14:24.180> amount<00:14:24.680> back<00:14:25.680> to<00:14:25.950> the<00:14:26.070> contract 00:14:26.540 --> 00:14:26.550 align:start position:0% send that amount back to the contract 00:14:26.550 --> 00:14:30.140 align:start position:0% send that amount back to the contract and<00:14:27.000> at<00:14:27.720> which<00:14:27.900> point<00:14:28.260> the<00:14:28.680> contract<00:14:29.280> will 00:14:30.140 --> 00:14:30.150 align:start position:0% and at which point the contract will 00:14:30.150 --> 00:14:32.870 align:start position:0% and at which point the contract will then<00:14:30.330> be<00:14:30.540> able<00:14:30.720> to<00:14:30.930> go<00:14:31.410> into<00:14:31.890> this<00:14:32.070> fallback 00:14:32.870 --> 00:14:32.880 align:start position:0% then be able to go into this fallback 00:14:32.880 --> 00:14:37.340 align:start position:0% then be able to go into this fallback function<00:14:33.390> and<00:14:33.600> call<00:14:34.140> withdraw<00:14:34.710> again<00:14:36.170> and<00:14:37.170> so 00:14:37.340 --> 00:14:37.350 align:start position:0% function and call withdraw again and so 00:14:37.350 --> 00:14:40.970 align:start position:0% function and call withdraw again and so what<00:14:37.500> this<00:14:37.650> then<00:14:37.980> does<00:14:38.930> is<00:14:39.930> re-enters<00:14:40.710> and 00:14:40.970 --> 00:14:40.980 align:start position:0% what this then does is re-enters and 00:14:40.980 --> 00:14:43.520 align:start position:0% what this then does is re-enters and checks<00:14:41.220> the<00:14:41.280> balance<00:14:41.900> but<00:14:42.900> we<00:14:42.930> haven't<00:14:43.230> zeroed 00:14:43.520 --> 00:14:43.530 align:start position:0% checks the balance but we haven't zeroed 00:14:43.530 --> 00:14:46.130 align:start position:0% checks the balance but we haven't zeroed out<00:14:43.770> the<00:14:43.890> balance<00:14:44.220> yet<00:14:44.430> in<00:14:45.060> the<00:14:45.870> original 00:14:46.130 --> 00:14:46.140 align:start position:0% out the balance yet in the original 00:14:46.140 --> 00:14:48.350 align:start position:0% out the balance yet in the original context<00:14:46.680> so<00:14:47.250> this<00:14:47.430> balance<00:14:47.880> is<00:14:48.000> still<00:14:48.210> the 00:14:48.350 --> 00:14:48.360 align:start position:0% context so this balance is still the 00:14:48.360 --> 00:14:51.140 align:start position:0% context so this balance is still the full<00:14:48.600> one<00:14:48.870> ether<00:14:49.320> and<00:14:49.560> so<00:14:50.400> this<00:14:50.640> is<00:14:50.730> the<00:14:50.820> second 00:14:51.140 --> 00:14:51.150 align:start position:0% full one ether and so this is the second 00:14:51.150 --> 00:14:54.320 align:start position:0% full one ether and so this is the second time<00:14:51.270> we've<00:14:51.420> been<00:14:51.570> here<00:14:51.810> and<00:14:52.430> so<00:14:53.430> the<00:14:54.120> next 00:14:54.320 --> 00:14:54.330 align:start position:0% time we've been here and so the next 00:14:54.330 --> 00:14:56.390 align:start position:0% time we've been here and so the next line<00:14:54.630> is<00:14:54.900> going<00:14:55.170> to<00:14:55.260> be<00:14:55.410> to<00:14:55.860> call<00:14:56.040> that<00:14:56.190> fall 00:14:56.390 --> 00:14:56.400 align:start position:0% line is going to be to call that fall 00:14:56.400 --> 00:14:59.210 align:start position:0% line is going to be to call that fall that<00:14:56.550> function<00:14:57.000> again<00:14:57.180> and<00:14:58.110> so<00:14:58.920> we're<00:14:59.100> back 00:14:59.210 --> 00:14:59.220 align:start position:0% that function again and so we're back 00:14:59.220 --> 00:15:01.760 align:start position:0% that function again and so we're back into<00:14:59.520> the<00:14:59.670> bad<00:15:00.150> guys<00:15:00.360> contract<00:15:00.930> and<00:15:01.230> what<00:15:01.680> are 00:15:01.760 --> 00:15:01.770 align:start position:0% into the bad guys contract and what are 00:15:01.770 --> 00:15:02.600 align:start position:0% into the bad guys contract and what are they<00:15:01.860> going<00:15:02.040> to<00:15:02.130> do<00:15:02.220> they're<00:15:02.430> going<00:15:02.460> to 00:15:02.600 --> 00:15:02.610 align:start position:0% they going to do they're going to 00:15:02.610 --> 00:15:06.920 align:start position:0% they going to do they're going to withdrawal<00:15:03.000> again<00:15:03.980> and<00:15:05.330> they<00:15:06.330> can<00:15:06.480> do<00:15:06.600> that<00:15:06.720> as 00:15:06.920 --> 00:15:06.930 align:start position:0% withdrawal again and they can do that as 00:15:06.930 --> 00:15:09.140 align:start position:0% withdrawal again and they can do that as long<00:15:07.140> as<00:15:07.170> they<00:15:07.710> have<00:15:07.980> enough<00:15:08.010> yeah<00:15:08.580> so<00:15:08.880> that's 00:15:09.140 --> 00:15:09.150 align:start position:0% long as they have enough yeah so that's 00:15:09.150 --> 00:15:11.360 align:start position:0% long as they have enough yeah so that's what<00:15:09.330> this<00:15:09.420> little<00:15:09.780> check<00:15:10.560> here<00:15:10.590> is<00:15:10.950> it<00:15:11.220> just 00:15:11.360 --> 00:15:11.370 align:start position:0% what this little check here is it just 00:15:11.370 --> 00:15:12.620 align:start position:0% what this little check here is it just checks<00:15:11.580> jobs<00:15:11.880> to<00:15:12.000> make<00:15:12.120> sure<00:15:12.300> that<00:15:12.480> the 00:15:12.620 --> 00:15:12.630 align:start position:0% checks jobs to make sure that the 00:15:12.630 --> 00:15:16.840 align:start position:0% checks jobs to make sure that the transaction<00:15:13.140> won't<00:15:13.260> fail<00:15:15.140> so<00:15:16.140> pretty<00:15:16.590> crazy 00:15:16.840 --> 00:15:16.850 align:start position:0% transaction won't fail so pretty crazy 00:15:16.850 --> 00:15:23.120 align:start position:0% transaction won't fail so pretty crazy happens<00:15:17.850> in<00:15:17.910> the<00:15:18.000> real<00:15:18.090> world<00:15:21.020> so<00:15:22.020> this<00:15:22.350> is<00:15:22.680> an 00:15:23.120 --> 00:15:23.130 align:start position:0% happens in the real world so this is an 00:15:23.130 --> 00:15:25.730 align:start position:0% happens in the real world so this is an example<00:15:23.430> of<00:15:23.760> how<00:15:24.600> you<00:15:24.660> would<00:15:24.840> execute<00:15:25.410> this 00:15:25.730 --> 00:15:25.740 align:start position:0% example of how you would execute this 00:15:25.740 --> 00:15:27.980 align:start position:0% example of how you would execute this sort<00:15:26.010> of<00:15:26.040> attack<00:15:26.310> using<00:15:27.210> truffle<00:15:27.600> to<00:15:27.690> run<00:15:27.840> your 00:15:27.980 --> 00:15:27.990 align:start position:0% sort of attack using truffle to run your 00:15:27.990 --> 00:15:30.380 align:start position:0% sort of attack using truffle to run your test<00:15:28.170> so<00:15:28.650> the<00:15:28.770> attacker<00:15:29.070> would<00:15:29.880> deploy<00:15:30.150> their 00:15:30.380 --> 00:15:30.390 align:start position:0% test so the attacker would deploy their 00:15:30.390 --> 00:15:35.480 align:start position:0% test so the attacker would deploy their contract<00:15:30.990> to<00:15:32.990> main<00:15:33.990> app<00:15:34.200> and<00:15:34.470> execute<00:15:35.370> the 00:15:35.480 --> 00:15:35.490 align:start position:0% contract to main app and execute the 00:15:35.490 --> 00:15:37.700 align:start position:0% contract to main app and execute the attack<00:15:35.700> you<00:15:35.820> disappear<00:15:36.210> contact<00:15:36.690> is<00:15:37.170> all<00:15:37.560> you 00:15:37.700 --> 00:15:37.710 align:start position:0% attack you disappear contact is all you 00:15:37.710 --> 00:15:42.550 align:start position:0% attack you disappear contact is all you need<00:15:37.890> to<00:15:38.040> do<00:15:38.160> is<00:15:38.310> run<00:15:38.490> truffle<00:15:39.090> test<00:15:41.060> looks 00:15:42.550 --> 00:15:42.560 align:start position:0% need to do is run truffle test looks 00:15:42.560 --> 00:15:47.769 align:start position:0% need to do is run truffle test looks this<00:15:42.759> and<00:15:43.759> so<00:15:43.879> this<00:15:44.029> is<00:15:45.939> its<00:15:46.939> hang<00:15:47.120> with<00:15:47.360> deploy 00:15:47.769 --> 00:15:47.779 align:start position:0% this and so this is its hang with deploy 00:15:47.779 --> 00:15:49.420 align:start position:0% this and so this is its hang with deploy so<00:15:48.170> we're<00:15:48.379> sitting<00:15:48.560> into<00:15:48.800> the<00:15:48.889> wand<00:15:49.100> ether 00:15:49.420 --> 00:15:49.430 align:start position:0% so we're sitting into the wand ether 00:15:49.430 --> 00:15:54.249 align:start position:0% so we're sitting into the wand ether here<00:15:50.769> pointing<00:15:51.769> it<00:15:51.920> there<00:15:52.100> and<00:15:53.259> it's 00:15:54.249 --> 00:15:54.259 align:start position:0% here pointing it there and it's 00:15:54.259 --> 00:15:56.079 align:start position:0% here pointing it there and it's executing<00:15:54.949> the<00:15:55.040> attack<00:15:55.249> that's<00:15:55.730> it<00:15:55.970> that's 00:15:56.079 --> 00:15:56.089 align:start position:0% executing the attack that's it that's 00:15:56.089 --> 00:16:03.150 align:start position:0% executing the attack that's it that's all<00:15:56.209> it<00:15:56.360> would<00:15:56.420> take 00:16:03.150 --> 00:16:03.160 align:start position:0% 00:16:03.160 --> 00:16:05.999 align:start position:0% all<00:16:04.160> right<00:16:04.249> so<00:16:04.519> what<00:16:04.910> we've<00:16:05.029> covered<00:16:05.209> so<00:16:05.420> far 00:16:05.999 --> 00:16:06.009 align:start position:0% all right so what we've covered so far 00:16:06.009 --> 00:16:09.309 align:start position:0% all right so what we've covered so far truffle<00:16:07.009> ganache<00:16:07.490> nice<00:16:07.910> working<00:16:08.360> gas<00:16:08.689> and 00:16:09.309 --> 00:16:09.319 align:start position:0% truffle ganache nice working gas and 00:16:09.319 --> 00:16:11.860 align:start position:0% truffle ganache nice working gas and fallback<00:16:09.740> functions<00:16:10.220> re-entrance<00:16:11.029> see<00:16:11.240> the 00:16:11.860 --> 00:16:11.870 align:start position:0% fallback functions re-entrance see the 00:16:11.870 --> 00:16:14.110 align:start position:0% fallback functions re-entrance see the exploit<00:16:12.319> and<00:16:12.559> a<00:16:13.129> little<00:16:13.579> bit<00:16:13.670> about<00:16:13.819> truffle 00:16:14.110 --> 00:16:14.120 align:start position:0% exploit and a little bit about truffle 00:16:14.120 --> 00:16:18.900 align:start position:0% exploit and a little bit about truffle test<00:16:15.040> any<00:16:16.040> questions<00:16:16.459> so<00:16:16.550> far 00:16:18.900 --> 00:16:18.910 align:start position:0% 00:16:18.910 --> 00:16:31.430 align:start position:0% someone<00:16:19.910> has<00:16:23.559> no<00:16:26.350> all<00:16:27.350> right 00:16:31.430 --> 00:16:31.440 align:start position:0% 00:16:31.440 --> 00:16:35.300 align:start position:0% we've<00:16:31.890> all<00:16:32.040> heard<00:16:32.220> of<00:16:32.310> the<00:16:32.370> dow<00:16:32.610> hack<00:16:33.230> and<00:16:34.310> the 00:16:35.300 --> 00:16:35.310 align:start position:0% we've all heard of the dow hack and the 00:16:35.310 --> 00:16:38.930 align:start position:0% we've all heard of the dow hack and the dow<00:16:35.430> hack<00:16:35.730> was<00:16:36.120> a<00:16:36.560> hack<00:16:37.560> that<00:16:37.589> was<00:16:37.920> based<00:16:38.820> on 00:16:38.930 --> 00:16:38.940 align:start position:0% dow hack was a hack that was based on 00:16:38.940 --> 00:16:41.660 align:start position:0% dow hack was a hack that was based on Regency<00:16:39.779> it<00:16:40.740> was<00:16:40.860> a<00:16:40.890> Regency<00:16:41.370> bull 00:16:41.660 --> 00:16:41.670 align:start position:0% Regency it was a Regency bull 00:16:41.670 --> 00:16:44.000 align:start position:0% Regency it was a Regency bull vulnerability<00:16:42.420> in<00:16:42.480> this<00:16:42.660> function<00:16:43.050> right 00:16:44.000 --> 00:16:44.010 align:start position:0% vulnerability in this function right 00:16:44.010 --> 00:16:48.019 align:start position:0% vulnerability in this function right here<00:16:45.380> so<00:16:46.380> they<00:16:46.500> are<00:16:46.680> in<00:16:47.160> this<00:16:47.399> function<00:16:47.850> here 00:16:48.019 --> 00:16:48.029 align:start position:0% here so they are in this function here 00:16:48.029 --> 00:16:51.310 align:start position:0% here so they are in this function here in<00:16:48.300> are<00:16:48.420> sending<00:16:48.930> all<00:16:49.709> of<00:16:50.070> the<00:16:50.490> remaining<00:16:50.820> gas 00:16:51.310 --> 00:16:51.320 align:start position:0% in are sending all of the remaining gas 00:16:51.320 --> 00:16:54.769 align:start position:0% in are sending all of the remaining gas to<00:16:52.320> the<00:16:52.380> recipient<00:16:52.920> and<00:16:53.010> that<00:16:53.760> enabled<00:16:54.540> the 00:16:54.769 --> 00:16:54.779 align:start position:0% to the recipient and that enabled the 00:16:54.779 --> 00:16:56.780 align:start position:0% to the recipient and that enabled the recipient<00:16:55.380> to<00:16:55.860> call<00:16:56.100> back<00:16:56.279> into<00:16:56.700> this 00:16:56.780 --> 00:16:56.790 align:start position:0% recipient to call back into this 00:16:56.790 --> 00:16:57.949 align:start position:0% recipient to call back into this function<00:16:57.240> it<00:16:57.300> was<00:16:57.390> actually<00:16:57.690> much<00:16:57.810> more 00:16:57.949 --> 00:16:57.959 align:start position:0% function it was actually much more 00:16:57.959 --> 00:17:00.769 align:start position:0% function it was actually much more complicated<00:16:58.740> than<00:16:59.040> this<00:16:59.250> there's<00:16:59.779> several 00:17:00.769 --> 00:17:00.779 align:start position:0% complicated than this there's several 00:17:00.779 --> 00:17:03.850 align:start position:0% complicated than this there's several methods<00:17:01.260> that<00:17:01.589> they<00:17:01.709> had<00:17:01.920> to<00:17:02.160> go<00:17:02.970> through<00:17:03.360> and 00:17:03.850 --> 00:17:03.860 align:start position:0% methods that they had to go through and 00:17:03.860 --> 00:17:06.590 align:start position:0% methods that they had to go through and kind<00:17:04.860> of<00:17:04.920> kind<00:17:05.670> of<00:17:05.730> figure<00:17:06.120> in<00:17:06.240> order<00:17:06.420> to<00:17:06.510> get 00:17:06.590 --> 00:17:06.600 align:start position:0% kind of kind of figure in order to get 00:17:06.600 --> 00:17:08.449 align:start position:0% kind of kind of figure in order to get this<00:17:06.720> payout<00:17:07.050> to<00:17:07.199> be<00:17:07.290> called<00:17:07.500> again<00:17:07.740> but<00:17:08.339> this 00:17:08.449 --> 00:17:08.459 align:start position:0% this payout to be called again but this 00:17:08.459 --> 00:17:09.260 align:start position:0% this payout to be called again but this is<00:17:08.550> how<00:17:08.670> they<00:17:08.819> did<00:17:08.910> it 00:17:09.260 --> 00:17:09.270 align:start position:0% is how they did it 00:17:09.270 --> 00:17:18.410 align:start position:0% is how they did it I<00:17:11.689> think<00:17:12.689> questions<00:17:13.319> on<00:17:13.559> that<00:17:16.490> I'll<00:17:17.490> leave<00:17:18.329> it 00:17:18.410 --> 00:17:18.420 align:start position:0% I think questions on that I'll leave it 00:17:18.420 --> 00:17:25.210 align:start position:0% I think questions on that I'll leave it up 00:17:25.210 --> 00:17:25.220 align:start position:0% 00:17:25.220 --> 00:17:29.060 align:start position:0% all<00:17:26.220> right<00:17:26.629> well<00:17:27.629> questions<00:17:28.139> anyone<00:17:28.679> have<00:17:28.919> any 00:17:29.060 --> 00:17:29.070 align:start position:0% all right well questions anyone have any 00:17:29.070 --> 00:17:36.210 align:start position:0% all right well questions anyone have any good 00:17:36.210 --> 00:17:36.220 align:start position:0% 00:17:36.220 --> 00:17:45.379 align:start position:0% they<00:17:36.730> skip<00:17:36.940> a<00:17:36.970> slide 00:17:45.379 --> 00:17:45.389 align:start position:0% 00:17:45.389 --> 00:17:46.580 align:start position:0% so<00:17:45.659> there's<00:17:45.840> a<00:17:45.870> bunch<00:17:45.929> of<00:17:46.080> ways<00:17:46.200> to<00:17:46.259> do 00:17:46.580 --> 00:17:46.590 align:start position:0% so there's a bunch of ways to do 00:17:46.590 --> 00:17:49.269 align:start position:0% so there's a bunch of ways to do reentrant<00:17:47.009> sea<00:17:47.190> protection<00:17:47.789> and<00:17:47.970> your 00:17:49.269 --> 00:17:49.279 align:start position:0% reentrant sea protection and your 00:17:49.279 --> 00:17:52.519 align:start position:0% reentrant sea protection and your contracting<00:17:50.279> methods<00:17:50.779> so<00:17:51.779> one<00:17:51.960> is<00:17:52.110> this<00:17:52.259> thing 00:17:52.519 --> 00:17:52.529 align:start position:0% contracting methods so one is this thing 00:17:52.529 --> 00:17:54.560 align:start position:0% contracting methods so one is this thing called<00:17:52.649> the<00:17:52.740> check<00:17:53.039> effects<00:17:53.970> interaction 00:17:54.560 --> 00:17:54.570 align:start position:0% called the check effects interaction 00:17:54.570 --> 00:17:57.169 align:start position:0% called the check effects interaction pattern<00:17:55.049> and<00:17:55.679> so<00:17:55.919> we're<00:17:56.279> first<00:17:56.669> you<00:17:57.000> do<00:17:57.149> a 00:17:57.169 --> 00:17:57.179 align:start position:0% pattern and so we're first you do a 00:17:57.179 --> 00:18:00.470 align:start position:0% pattern and so we're first you do a check<00:17:57.559> so<00:17:58.559> you<00:17:58.590> see<00:17:58.919> that<00:17:59.220> their<00:17:59.429> balance<00:18:00.029> is 00:18:00.470 --> 00:18:00.480 align:start position:0% check so you see that their balance is 00:18:00.480 --> 00:18:03.169 align:start position:0% check so you see that their balance is greater<00:18:00.870> than<00:18:01.080> zero<00:18:01.380> for<00:18:01.500> instance<00:18:02.009> and<00:18:02.549> then 00:18:03.169 --> 00:18:03.179 align:start position:0% greater than zero for instance and then 00:18:03.179 --> 00:18:04.909 align:start position:0% greater than zero for instance and then you<00:18:03.360> perform<00:18:03.809> the<00:18:04.080> effect<00:18:04.470> that<00:18:04.590> an 00:18:04.909 --> 00:18:04.919 align:start position:0% you perform the effect that an 00:18:04.919 --> 00:18:07.759 align:start position:0% you perform the effect that an interaction<00:18:05.159> will<00:18:05.519> help<00:18:05.929> so<00:18:06.929> this<00:18:07.139> is<00:18:07.440> you 00:18:07.759 --> 00:18:07.769 align:start position:0% interaction will help so this is you 00:18:07.769 --> 00:18:10.610 align:start position:0% interaction will help so this is you zero<00:18:08.100> out<00:18:08.220> the<00:18:08.460> balance<00:18:08.880> before<00:18:09.630> you<00:18:10.200> send<00:18:10.470> it 00:18:10.610 --> 00:18:10.620 align:start position:0% zero out the balance before you send it 00:18:10.620 --> 00:18:12.190 align:start position:0% zero out the balance before you send it which<00:18:10.860> is<00:18:11.190> what<00:18:11.370> you<00:18:11.399> were<00:18:11.580> saying<00:18:11.610> earlier 00:18:12.190 --> 00:18:12.200 align:start position:0% which is what you were saying earlier 00:18:12.200 --> 00:18:16.820 align:start position:0% which is what you were saying earlier and<00:18:13.200> then<00:18:14.009> once<00:18:14.309> you<00:18:14.580> do<00:18:14.850> the<00:18:14.970> effect<00:18:15.330> that<00:18:15.830> you 00:18:16.820 --> 00:18:16.830 align:start position:0% and then once you do the effect that you 00:18:16.830 --> 00:18:19.490 align:start position:0% and then once you do the effect that you finally<00:18:17.129> run<00:18:17.669> the<00:18:17.759> interaction<00:18:18.350> another<00:18:19.350> way 00:18:19.490 --> 00:18:19.500 align:start position:0% finally run the interaction another way 00:18:19.500 --> 00:18:23.180 align:start position:0% finally run the interaction another way is<00:18:19.799> using<00:18:20.460> Rafi<00:18:21.389> interview<00:18:21.690> types<00:18:22.190> morbid 00:18:23.180 --> 00:18:23.190 align:start position:0% is using Rafi interview types morbid 00:18:23.190 --> 00:18:24.470 align:start position:0% is using Rafi interview types morbid Zeppelin's<00:18:23.490> like<00:18:23.639> we're<00:18:23.820> in<00:18:23.879> chancy<00:18:24.269> guard 00:18:24.470 --> 00:18:24.480 align:start position:0% Zeppelin's like we're in chancy guard 00:18:24.480 --> 00:18:27.379 align:start position:0% Zeppelin's like we're in chancy guard and<00:18:24.750> this<00:18:25.289> basically<00:18:25.769> is<00:18:26.129> you<00:18:26.730> have<00:18:26.970> a<00:18:27.000> boolean 00:18:27.379 --> 00:18:27.389 align:start position:0% and this basically is you have a boolean 00:18:27.389 --> 00:18:29.869 align:start position:0% and this basically is you have a boolean value<00:18:27.509> you<00:18:28.440> can<00:18:28.620> call<00:18:28.769> it<00:18:28.860> blocker<00:18:29.100> or<00:18:29.580> any 00:18:29.869 --> 00:18:29.879 align:start position:0% value you can call it blocker or any 00:18:29.879 --> 00:18:34.369 align:start position:0% value you can call it blocker or any want<00:18:30.090> which<00:18:30.799> would<00:18:31.799> be<00:18:32.059> true<00:18:33.059> false<00:18:33.690> and<00:18:33.960> so 00:18:34.369 --> 00:18:34.379 align:start position:0% want which would be true false and so 00:18:34.379 --> 00:18:36.490 align:start position:0% want which would be true false and so when<00:18:34.529> you<00:18:34.620> come<00:18:34.830> in<00:18:35.039> together<00:18:35.159> the<00:18:35.429> first<00:18:35.610> time 00:18:36.490 --> 00:18:36.500 align:start position:0% when you come in together the first time 00:18:36.500 --> 00:18:39.590 align:start position:0% when you come in together the first time this<00:18:37.500> requires<00:18:37.980> the<00:18:38.129> middle<00:18:38.399> class<00:18:38.549> event<00:18:39.299> you 00:18:39.590 --> 00:18:39.600 align:start position:0% this requires the middle class event you 00:18:39.600 --> 00:18:42.259 align:start position:0% this requires the middle class event you would<00:18:39.750> immediately<00:18:40.259> lock<00:18:40.860> it<00:18:41.070> so<00:18:41.730> now<00:18:41.909> if 00:18:42.259 --> 00:18:42.269 align:start position:0% would immediately lock it so now if 00:18:42.269 --> 00:18:44.830 align:start position:0% would immediately lock it so now if anything<00:18:42.690> happens<00:18:43.080> when<00:18:43.440> you<00:18:43.500> do<00:18:44.129> the<00:18:44.279> things 00:18:44.830 --> 00:18:44.840 align:start position:0% anything happens when you do the things 00:18:44.840 --> 00:18:48.409 align:start position:0% anything happens when you do the things this<00:18:45.840> condition<00:18:46.559> will<00:18:46.710> fail<00:18:47.009> because<00:18:47.370> lock<00:18:47.820> is 00:18:48.409 --> 00:18:48.419 align:start position:0% this condition will fail because lock is 00:18:48.419 --> 00:18:52.039 align:start position:0% this condition will fail because lock is now<00:18:48.750> true<00:18:50.299> and<00:18:51.299> then<00:18:51.419> when<00:18:51.539> you're<00:18:51.659> done<00:18:51.779> just 00:18:52.039 --> 00:18:52.049 align:start position:0% now true and then when you're done just 00:18:52.049 --> 00:18:54.110 align:start position:0% now true and then when you're done just make<00:18:52.470> sure<00:18:52.649> that<00:18:52.950> you<00:18:53.070> unlock<00:18:53.399> your<00:18:53.460> contract 00:18:54.110 --> 00:18:54.120 align:start position:0% make sure that you unlock your contract 00:18:54.120 --> 00:18:56.180 align:start position:0% make sure that you unlock your contract if<00:18:54.240> you<00:18:54.360> jump<00:18:54.600> if<00:18:54.899> there's<00:18:55.139> an<00:18:55.259> error<00:18:55.559> and<00:18:56.100> this 00:18:56.180 --> 00:18:56.190 align:start position:0% if you jump if there's an error and this 00:18:56.190 --> 00:18:58.519 align:start position:0% if you jump if there's an error and this lock<00:18:56.570> doesn't<00:18:57.570> unlock<00:18:57.929> then<00:18:58.289> you<00:18:58.320> can 00:18:58.519 --> 00:18:58.529 align:start position:0% lock doesn't unlock then you can 00:18:58.529 --> 00:19:01.759 align:start position:0% lock doesn't unlock then you can effectively<00:18:59.070> lock<00:18:59.460> your<00:18:59.639> contract<00:19:00.769> we're 00:19:01.759 --> 00:19:01.769 align:start position:0% effectively lock your contract we're 00:19:01.769 --> 00:19:07.870 align:start position:0% effectively lock your contract we're getting<00:19:01.980> you<00:19:02.129> from 00:19:07.870 --> 00:19:07.880 align:start position:0% 00:19:07.880 --> 00:19:12.820 align:start position:0% okay<00:19:08.600> that<00:19:08.990> myself<00:19:11.200> and<00:19:12.200> this<00:19:12.590> is<00:19:12.650> real 00:19:12.820 --> 00:19:12.830 align:start position:0% okay that myself and this is real 00:19:12.830 --> 00:19:16.630 align:start position:0% okay that myself and this is real important<00:19:13.510> who<00:19:14.510> has<00:19:14.900> heard<00:19:15.230> of<00:19:15.610> Edison<00:19:16.610> and 00:19:16.630 --> 00:19:16.640 align:start position:0% important who has heard of Edison and 00:19:16.640 --> 00:19:19.840 align:start position:0% important who has heard of Edison and had<00:19:16.970> his<00:19:17.090> transfer<00:19:17.510> and<00:19:17.750> why<00:19:18.220> those<00:19:19.220> were<00:19:19.520> out 00:19:19.840 --> 00:19:19.850 align:start position:0% had his transfer and why those were out 00:19:19.850 --> 00:19:26.140 align:start position:0% had his transfer and why those were out or<00:19:20.720> one<00:19:20.870> of<00:19:20.990> the<00:19:21.049> reasons<00:19:21.080> why<00:19:21.410> anyone<00:19:22.010> know<00:19:25.150> so 00:19:26.140 --> 00:19:26.150 align:start position:0% or one of the reasons why anyone know so 00:19:26.150 --> 00:19:29.140 align:start position:0% or one of the reasons why anyone know so these<00:19:26.539> were<00:19:26.690> added<00:19:26.870> because<00:19:27.230> of<00:19:27.820> the<00:19:28.820> answers 00:19:29.140 --> 00:19:29.150 align:start position:0% these were added because of the answers 00:19:29.150 --> 00:19:31.419 align:start position:0% these were added because of the answers that<00:19:29.179> call<00:19:29.510> sending<00:19:30.049> all<00:19:30.320> of<00:19:30.770> the<00:19:31.160> remaining 00:19:31.419 --> 00:19:31.429 align:start position:0% that call sending all of the remaining 00:19:31.429 --> 00:19:35.590 align:start position:0% that call sending all of the remaining guests<00:19:31.880> by<00:19:32.120> default<00:19:32.740> and<00:19:33.740> so<00:19:34.210> that<00:19:35.210> was<00:19:35.360> seen 00:19:35.590 --> 00:19:35.600 align:start position:0% guests by default and so that was seen 00:19:35.600 --> 00:19:38.919 align:start position:0% guests by default and so that was seen as<00:19:35.960> a<00:19:36.410> homeowner<00:19:36.860> ability<00:19:37.390> and<00:19:38.390> that<00:19:38.419> were 00:19:38.919 --> 00:19:38.929 align:start position:0% as a homeowner ability and that were 00:19:38.929 --> 00:19:40.270 align:start position:0% as a homeowner ability and that were really<00:19:39.140> clear<00:19:39.470> that<00:19:39.500> that<00:19:39.980> would<00:19:40.070> enable 00:19:40.270 --> 00:19:40.280 align:start position:0% really clear that that would enable 00:19:40.280 --> 00:19:42.730 align:start position:0% really clear that that would enable Regency<00:19:40.970> and<00:19:41.299> so<00:19:41.510> what<00:19:41.630> they<00:19:41.720> did<00:19:41.780> as<00:19:42.530> they 00:19:42.730 --> 00:19:42.740 align:start position:0% Regency and so what they did as they 00:19:42.740 --> 00:19:44.080 align:start position:0% Regency and so what they did as they come<00:19:43.010> up<00:19:43.070> with<00:19:43.220> either<00:19:43.400> son<00:19:43.789> I<00:19:44.059> just 00:19:44.080 --> 00:19:44.090 align:start position:0% come up with either son I just 00:19:44.090 --> 00:19:46.210 align:start position:0% come up with either son I just transferred<00:19:44.510> which<00:19:45.320> will<00:19:45.500> automatically 00:19:46.210 --> 00:19:46.220 align:start position:0% transferred which will automatically 00:19:46.220 --> 00:19:48.460 align:start position:0% transferred which will automatically limit<00:19:46.850> the<00:19:47.210> amount<00:19:47.360> of<00:19:47.480> gas<00:19:47.659> that's<00:19:47.900> passed<00:19:48.169> to 00:19:48.460 --> 00:19:48.470 align:start position:0% limit the amount of gas that's passed to 00:19:48.470 --> 00:19:53.500 align:start position:0% limit the amount of gas that's passed to 2300<00:19:49.690> ish<00:19:50.690> its<00:19:51.140> talkative<00:19:51.740> but<00:19:52.090> what<00:19:53.090> that<00:19:53.240> did 00:19:53.500 --> 00:19:53.510 align:start position:0% 2300 ish its talkative but what that did 00:19:53.510 --> 00:19:56.289 align:start position:0% 2300 ish its talkative but what that did was<00:19:53.690> effectively<00:19:54.380> make<00:19:54.650> it<00:19:54.830> so<00:19:55.070> that<00:19:55.100> it<00:19:55.789> was 00:19:56.289 --> 00:19:56.299 align:start position:0% was effectively make it so that it was 00:19:56.299 --> 00:19:58.060 align:start position:0% was effectively make it so that it was too<00:19:56.570> expensive<00:19:56.600> to<00:19:57.169> do<00:19:57.409> anything<00:19:57.710> in<00:19:58.010> a 00:19:58.060 --> 00:19:58.070 align:start position:0% too expensive to do anything in a 00:19:58.070 --> 00:20:00.730 align:start position:0% too expensive to do anything in a fallback<00:19:58.370> function<00:19:59.030> that<00:19:59.809> could<00:20:00.140> possibly 00:20:00.730 --> 00:20:00.740 align:start position:0% fallback function that could possibly 00:20:00.740 --> 00:20:04.539 align:start position:0% fallback function that could possibly result<00:20:01.400> in<00:20:01.700> reaction<00:20:02.120> see<00:20:02.270> and<00:20:02.480> so<00:20:03.350> now<00:20:03.559> if<00:20:04.130> he 00:20:04.539 --> 00:20:04.549 align:start position:0% result in reaction see and so now if he 00:20:04.549 --> 00:20:07.899 align:start position:0% result in reaction see and so now if he used<00:20:04.760> how<00:20:05.030> the<00:20:05.090> sender<00:20:05.510> as<00:20:05.690> that<00:20:06.049> transfer<00:20:06.909> and 00:20:07.899 --> 00:20:07.909 align:start position:0% used how the sender as that transfer and 00:20:07.909 --> 00:20:10.330 align:start position:0% used how the sender as that transfer and to<00:20:08.390> send<00:20:08.659> that<00:20:08.809> ether<00:20:09.169> the<00:20:09.620> fallback<00:20:09.799> function 00:20:10.330 --> 00:20:10.340 align:start position:0% to send that ether the fallback function 00:20:10.340 --> 00:20:11.500 align:start position:0% to send that ether the fallback function would<00:20:10.490> be<00:20:10.549> stuck<00:20:10.820> there<00:20:10.970> wouldn't<00:20:11.299> be<00:20:11.330> able<00:20:11.419> to 00:20:11.500 --> 00:20:11.510 align:start position:0% would be stuck there wouldn't be able to 00:20:11.510 --> 00:20:14.200 align:start position:0% would be stuck there wouldn't be able to get<00:20:11.630> back<00:20:11.809> out<00:20:11.990> and<00:20:12.350> into<00:20:12.770> your<00:20:12.919> your<00:20:13.580> contract 00:20:14.200 --> 00:20:14.210 align:start position:0% get back out and into your your contract 00:20:14.210 --> 00:20:15.490 align:start position:0% get back out and into your your contract any<00:20:14.780> which<00:20:15.020> sounds<00:20:15.289> great 00:20:15.490 --> 00:20:15.500 align:start position:0% any which sounds great 00:20:15.500 --> 00:20:16.620 align:start position:0% any which sounds great it<00:20:15.650> sounds<00:20:15.860> like<00:20:15.919> that<00:20:16.039> would<00:20:16.159> fix<00:20:16.370> everything 00:20:16.620 --> 00:20:16.630 align:start position:0% it sounds like that would fix everything 00:20:16.630 --> 00:20:24.130 align:start position:0% it sounds like that would fix everything and<00:20:17.630> it<00:20:17.780> did<00:20:18.020> but<00:20:19.450> problem<00:20:20.830> was<00:20:21.830> I<00:20:22.929> just<00:20:23.929> went 00:20:24.130 --> 00:20:24.140 align:start position:0% and it did but problem was I just went 00:20:24.140 --> 00:20:27.330 align:start position:0% and it did but problem was I just went to<00:20:24.380> slides<00:20:24.650> again<00:20:25.600> Constantinople 00:20:27.330 --> 00:20:27.340 align:start position:0% to slides again Constantinople 00:20:27.340 --> 00:20:29.320 align:start position:0% to slides again Constantinople everyone<00:20:28.340> everyone<00:20:28.850> knows<00:20:29.030> about 00:20:29.320 --> 00:20:29.330 align:start position:0% everyone everyone knows about 00:20:29.330 --> 00:20:33.370 align:start position:0% everyone everyone knows about Constantinople<00:20:30.230> I'm<00:20:30.320> guessing<00:20:30.679> it's<00:20:32.380> it's 00:20:33.370 --> 00:20:33.380 align:start position:0% Constantinople I'm guessing it's it's 00:20:33.380 --> 00:20:36.430 align:start position:0% Constantinople I'm guessing it's it's great<00:20:33.650> so<00:20:34.450> Constantinople<00:20:35.450> had<00:20:35.570> an<00:20:35.720> EIP<00:20:35.929> that 00:20:36.430 --> 00:20:36.440 align:start position:0% great so Constantinople had an EIP that 00:20:36.440 --> 00:20:39.640 align:start position:0% great so Constantinople had an EIP that actually<00:20:36.890> lowered<00:20:37.460> the<00:20:38.270> minimum<00:20:38.659> gas<00:20:39.289> cost 00:20:39.640 --> 00:20:39.650 align:start position:0% actually lowered the minimum gas cost 00:20:39.650 --> 00:20:42.370 align:start position:0% actually lowered the minimum gas cost for<00:20:40.580> storage<00:20:41.090> from<00:20:41.390> five<00:20:41.600> thousand<00:20:42.049> to<00:20:42.080> two 00:20:42.370 --> 00:20:42.380 align:start position:0% for storage from five thousand to two 00:20:42.380 --> 00:20:44.680 align:start position:0% for storage from five thousand to two hundred<00:20:42.409> gas<00:20:42.980> insurance<00:20:43.909> system<00:20:44.210> situation 00:20:44.680 --> 00:20:44.690 align:start position:0% hundred gas insurance system situation 00:20:44.690 --> 00:20:48.640 align:start position:0% hundred gas insurance system situation great<00:20:44.960> ish<00:20:45.429> it's<00:20:46.429> not<00:20:46.580> kid<00:20:47.230> so<00:20:48.230> when<00:20:48.530> that 00:20:48.640 --> 00:20:48.650 align:start position:0% great ish it's not kid so when that 00:20:48.650 --> 00:20:51.279 align:start position:0% great ish it's not kid so when that would<00:20:48.830> happen<00:20:48.940> if<00:20:49.940> all<00:20:50.059> that<00:20:50.270> functions<00:20:50.750> could 00:20:51.279 --> 00:20:51.289 align:start position:0% would happen if all that functions could 00:20:51.289 --> 00:20:55.029 align:start position:0% would happen if all that functions could now<00:20:51.590> fall<00:20:52.159> back<00:20:52.370> in<00:20:52.789> and<00:20:53.200> perform<00:20:54.200> Regency 00:20:55.029 --> 00:20:55.039 align:start position:0% now fall back in and perform Regency 00:20:55.039 --> 00:20:55.920 align:start position:0% now fall back in and perform Regency because<00:20:55.340> the<00:20:55.400> constants 00:20:55.920 --> 00:20:55.930 align:start position:0% because the constants 00:20:55.930 --> 00:20:57.770 align:start position:0% because the constants really<00:20:56.710> caught<00:20:56.860> this<00:20:57.040> a<00:20:57.100> couple<00:20:57.400> days<00:20:57.550> before 00:20:57.770 --> 00:20:57.780 align:start position:0% really caught this a couple days before 00:20:57.780 --> 00:21:04.080 align:start position:0% really caught this a couple days before externalizes<00:20:58.809> crazy<00:21:00.930> so<00:21:02.670> luckily<00:21:03.670> in<00:21:03.880> the<00:21:03.940> con 00:21:04.080 --> 00:21:04.090 align:start position:0% externalizes crazy so luckily in the con 00:21:04.090 --> 00:21:09.150 align:start position:0% externalizes crazy so luckily in the con it<00:21:04.410> it<00:21:05.410> was<00:21:05.530> removed<00:21:05.920> and<00:21:07.710> never<00:21:08.710> made<00:21:08.950> it<00:21:09.100> to 00:21:09.150 --> 00:21:09.160 align:start position:0% it it was removed and never made it to 00:21:09.160 --> 00:21:11.850 align:start position:0% it it was removed and never made it to Maine<00:21:09.340> that<00:21:09.520> also<00:21:09.850> issue<00:21:10.740> because<00:21:11.740> it 00:21:11.850 --> 00:21:11.860 align:start position:0% Maine that also issue because it 00:21:11.860 --> 00:21:15.560 align:start position:0% Maine that also issue because it actually<00:21:12.100> is<00:21:12.280> active<00:21:12.700> on<00:21:12.760> the<00:21:12.880> net<00:21:13.090> was<00:21:13.270> just 00:21:15.560 --> 00:21:15.570 align:start position:0% 00:21:15.570 --> 00:21:20.760 align:start position:0% and<00:21:16.570> then<00:21:16.690> there's<00:21:16.900> Istanbul<00:21:17.680> so<00:21:19.770> it's 00:21:20.760 --> 00:21:20.770 align:start position:0% and then there's Istanbul so it's 00:21:20.770 --> 00:21:23.870 align:start position:0% and then there's Istanbul so it's sampled<00:21:21.100> increased<00:21:21.940> gas<00:21:22.150> costs<00:21:22.840> actually 00:21:23.870 --> 00:21:23.880 align:start position:0% sampled increased gas costs actually 00:21:23.880 --> 00:21:28.010 align:start position:0% sampled increased gas costs actually kind<00:21:24.880> of<00:21:24.910> do<00:21:25.210> the<00:21:25.360> opposite<00:21:26.970> as 00:21:28.010 --> 00:21:28.020 align:start position:0% kind of do the opposite as 00:21:28.020 --> 00:21:30.690 align:start position:0% kind of do the opposite as Constantinople's<00:21:29.280> decreases<00:21:30.280> we're<00:21:30.429> doing 00:21:30.690 --> 00:21:30.700 align:start position:0% Constantinople's decreases we're doing 00:21:30.700 --> 00:21:32.940 align:start position:0% Constantinople's decreases we're doing and<00:21:31.059> that<00:21:31.450> there<00:21:31.690> are<00:21:31.780> now<00:21:31.960> functions<00:21:32.620> on<00:21:32.800> live 00:21:32.940 --> 00:21:32.950 align:start position:0% and that there are now functions on live 00:21:32.950 --> 00:21:35.820 align:start position:0% and that there are now functions on live contracts<00:21:33.490> that<00:21:33.880> can<00:21:34.420> not<00:21:34.750> that<00:21:35.500> will<00:21:35.710> no 00:21:35.820 --> 00:21:35.830 align:start position:0% contracts that can not that will no 00:21:35.830 --> 00:21:38.280 align:start position:0% contracts that can not that will no longer<00:21:35.860> work<00:21:36.160> so<00:21:36.970> this<00:21:37.090> is<00:21:37.240> actually<00:21:37.720> common 00:21:38.280 --> 00:21:38.290 align:start position:0% longer work so this is actually common 00:21:38.290 --> 00:21:40.890 align:start position:0% longer work so this is actually common faces<00:21:38.679> from<00:21:38.860> contract<00:21:39.370> that<00:21:39.820> would<00:21:40.600> be<00:21:40.690> States 00:21:40.890 --> 00:21:40.900 align:start position:0% faces from contract that would be States 00:21:40.900 --> 00:21:43.530 align:start position:0% faces from contract that would be States before<00:21:41.080> incident<00:21:41.530> is<00:21:41.740> stable<00:21:42.130> for<00:21:42.160> a<00:21:42.309> lot<00:21:42.540> but 00:21:43.530 --> 00:21:43.540 align:start position:0% before incident is stable for a lot but 00:21:43.540 --> 00:21:48.060 align:start position:0% before incident is stable for a lot but these<00:21:44.170> three<00:21:44.970> parts<00:21:46.380> are<00:21:47.380> its<00:21:47.650> position<00:21:47.980> in 00:21:48.060 --> 00:21:48.070 align:start position:0% these three parts are its position in 00:21:48.070 --> 00:21:50.190 align:start position:0% these three parts are its position in the<00:21:48.100> total<00:21:48.370> I<00:21:48.700> would<00:21:48.940> actually<00:21:49.120> do<00:21:49.450> like<00:21:49.780> 2x 00:21:50.190 --> 00:21:50.200 align:start position:0% the total I would actually do like 2x 00:21:50.200 --> 00:21:53.160 align:start position:0% the total I would actually do like 2x loads<00:21:50.500> or<00:21:50.740> 1<00:21:50.890> X<00:21:51.010> load<00:21:51.420> and<00:21:52.420> because<00:21:52.990> of 00:21:53.160 --> 00:21:53.170 align:start position:0% loads or 1 X load and because of 00:21:53.170 --> 00:21:56.940 align:start position:0% loads or 1 X load and because of increased<00:21:53.890> cost<00:21:54.220> and<00:21:54.580> s<00:21:54.760> loads<00:21:55.090> and<00:21:55.390> a<00:21:55.950> couple 00:21:56.940 --> 00:21:56.950 align:start position:0% increased cost and s loads and a couple 00:21:56.950 --> 00:21:59.910 align:start position:0% increased cost and s loads and a couple of<00:21:57.040> other<00:21:57.520> optos<00:21:57.970> this<00:21:58.870> one<00:21:59.110> L<00:21:59.260> fail<00:21:59.559> every 00:21:59.910 --> 00:21:59.920 align:start position:0% of other optos this one L fail every 00:21:59.920 --> 00:22:01.410 align:start position:0% of other optos this one L fail every single<00:22:00.190> time<00:22:00.370> there's<00:22:00.550> no<00:22:00.700> way<00:22:00.850> for<00:22:00.880> this<00:22:01.270> to 00:22:01.410 --> 00:22:01.420 align:start position:0% single time there's no way for this to 00:22:01.420 --> 00:22:04.620 align:start position:0% single time there's no way for this to pass<00:22:01.630> up<00:22:01.840> its<00:22:02.020> Istanbul<00:22:02.910> so<00:22:03.910> the<00:22:04.030> point<00:22:04.300> being 00:22:04.620 --> 00:22:04.630 align:start position:0% pass up its Istanbul so the point being 00:22:04.630 --> 00:22:09.330 align:start position:0% pass up its Istanbul so the point being that<00:22:05.380> you<00:22:06.660> cannot<00:22:07.660> rely<00:22:08.080> on<00:22:08.110> gas<00:22:08.590> costs<00:22:09.100> as<00:22:09.250> we 00:22:09.330 --> 00:22:09.340 align:start position:0% that you cannot rely on gas costs as we 00:22:09.340 --> 00:22:14.700 align:start position:0% that you cannot rely on gas costs as we protect<00:22:09.490> its<00:22:10.030> Regency<00:22:12.929> so<00:22:13.929> just<00:22:14.500> remember 00:22:14.700 --> 00:22:14.710 align:start position:0% protect its Regency so just remember 00:22:14.710 --> 00:22:17.580 align:start position:0% protect its Regency so just remember that<00:22:14.830> that's<00:22:15.160> the<00:22:15.309> only<00:22:15.340> thing<00:22:16.110> so<00:22:17.110> always<00:22:17.470> be 00:22:17.580 --> 00:22:17.590 align:start position:0% that that's the only thing so always be 00:22:17.590 --> 00:22:22.230 align:start position:0% that that's the only thing so always be aware<00:22:17.710> that<00:22:19.770> so<00:22:20.770> the<00:22:20.890> honeypot<00:22:21.309> I'm<00:22:21.820> hot<00:22:22.059> is 00:22:22.230 --> 00:22:22.240 align:start position:0% aware that so the honeypot I'm hot is 00:22:22.240 --> 00:22:25.680 align:start position:0% aware that so the honeypot I'm hot is fun<00:22:23.190> and<00:22:24.190> then<00:22:24.520> run<00:22:24.670> heard<00:22:24.970> of<00:22:25.210> a<00:22:25.270> honeypot 00:22:25.680 --> 00:22:25.690 align:start position:0% fun and then run heard of a honeypot 00:22:25.690 --> 00:22:31.110 align:start position:0% fun and then run heard of a honeypot and<00:22:25.900> like<00:22:26.320> infra<00:22:26.800> sec<00:22:27.540> yeah<00:22:28.540> so<00:22:29.670> honey<00:22:30.670> pots<00:22:30.940> in 00:22:31.110 --> 00:22:31.120 align:start position:0% and like infra sec yeah so honey pots in 00:22:31.120 --> 00:22:32.250 align:start position:0% and like infra sec yeah so honey pots in InfoSec<00:22:31.540> are<00:22:31.690> actually<00:22:31.929> a<00:22:31.960> little<00:22:32.140> bit 00:22:32.250 --> 00:22:32.260 align:start position:0% InfoSec are actually a little bit 00:22:32.260 --> 00:22:34.860 align:start position:0% InfoSec are actually a little bit different<00:22:32.650> than<00:22:33.370> what<00:22:33.730> we<00:22:34.210> call<00:22:34.420> honeypot 00:22:34.860 --> 00:22:34.870 align:start position:0% different than what we call honeypot 00:22:34.870 --> 00:22:36.090 align:start position:0% different than what we call honeypot aetherium<00:22:35.380> but<00:22:35.559> we're<00:22:35.650> gonna<00:22:35.740> we're<00:22:36.040> gonna 00:22:36.090 --> 00:22:36.100 align:start position:0% aetherium but we're gonna we're gonna 00:22:36.100 --> 00:22:41.040 align:start position:0% aetherium but we're gonna we're gonna keep<00:22:36.309> calling<00:22:36.640> a<00:22:36.670> honeypot<00:22:38.460> because<00:22:40.050> that's 00:22:41.040 --> 00:22:41.050 align:start position:0% keep calling a honeypot because that's 00:22:41.050 --> 00:22:45.470 align:start position:0% keep calling a honeypot because that's just<00:22:41.230> we<00:22:41.710> make<00:22:41.950> things 00:22:45.470 --> 00:22:45.480 align:start position:0% 00:22:45.480 --> 00:22:51.290 align:start position:0% so<00:22:46.230> a<00:22:46.260> honeypot<00:22:46.680> is<00:22:47.240> a<00:22:48.240> way<00:22:49.050> to<00:22:49.460> trick<00:22:50.460> the<00:22:51.090> bad 00:22:51.290 --> 00:22:51.300 align:start position:0% so a honeypot is a way to trick the bad 00:22:51.300 --> 00:23:01.010 align:start position:0% so a honeypot is a way to trick the bad guy<00:22:51.510> it's<00:22:51.780> becoming<00:22:52.080> a<00:22:52.200> vapor<00:22:54.110> and<00:22:55.110> I<00:22:57.800> so<00:23:00.020> there 00:23:01.010 --> 00:23:01.020 align:start position:0% guy it's becoming a vapor and I so there 00:23:01.020 --> 00:23:03.620 align:start position:0% guy it's becoming a vapor and I so there are<00:23:01.170> several<00:23:01.380> types<00:23:01.590> of<00:23:01.770> processes<00:23:02.550> you<00:23:02.630> you 00:23:03.620 --> 00:23:03.630 align:start position:0% are several types of processes you you 00:23:03.630 --> 00:23:06.080 align:start position:0% are several types of processes you you can<00:23:03.810> go<00:23:03.960> over<00:23:04.500> here<00:23:05.310> there<00:23:05.730> are<00:23:05.850> three 00:23:06.080 --> 00:23:06.090 align:start position:0% can go over here there are three 00:23:06.090 --> 00:23:08.660 align:start position:0% can go over here there are three different<00:23:06.120> sort<00:23:06.810> of<00:23:07.010> general<00:23:08.010> types<00:23:08.340> actually 00:23:08.660 --> 00:23:08.670 align:start position:0% different sort of general types actually 00:23:08.670 --> 00:23:12.290 align:start position:0% different sort of general types actually they're<00:23:09.030> really<00:23:09.300> well<00:23:09.570> laid<00:23:10.020> out<00:23:10.050> at<00:23:11.300> this 00:23:12.290 --> 00:23:12.300 align:start position:0% they're really well laid out at this 00:23:12.300 --> 00:23:12.740 align:start position:0% they're really well laid out at this link 00:23:12.740 --> 00:23:12.750 align:start position:0% link 00:23:12.750 --> 00:23:15.950 align:start position:0% link but<00:23:13.620> in<00:23:14.010> general<00:23:14.190> is<00:23:14.550> sort<00:23:14.760> of<00:23:14.820> taxonomy<00:23:15.660> of 00:23:15.950 --> 00:23:15.960 align:start position:0% but in general is sort of taxonomy of 00:23:15.960 --> 00:23:17.870 align:start position:0% but in general is sort of taxonomy of hot<00:23:16.110> coffee<00:23:16.410> pots<00:23:16.860> are<00:23:17.040> their<00:23:17.310> three<00:23:17.520> main 00:23:17.870 --> 00:23:17.880 align:start position:0% hot coffee pots are their three main 00:23:17.880 --> 00:23:21.320 align:start position:0% hot coffee pots are their three main classes<00:23:18.200> that<00:23:19.200> class<00:23:20.060> honeypot<00:23:21.060> said 00:23:21.320 --> 00:23:21.330 align:start position:0% classes that class honeypot said 00:23:21.330 --> 00:23:26.030 align:start position:0% classes that class honeypot said interact<00:23:22.170> with<00:23:22.400> machine<00:23:23.400> some<00:23:24.180> that<00:23:25.040> happened 00:23:26.030 --> 00:23:26.040 align:start position:0% interact with machine some that happened 00:23:26.040 --> 00:23:28.160 align:start position:0% interact with machine some that happened during<00:23:26.160> compilation<00:23:26.790> and<00:23:27.420> some<00:23:27.840> that<00:23:27.990> are 00:23:28.160 --> 00:23:28.170 align:start position:0% during compilation and some that are 00:23:28.170 --> 00:23:31.250 align:start position:0% during compilation and some that are actually<00:23:29.030> just<00:23:30.030> due<00:23:30.210> to<00:23:30.240> misleading<00:23:30.690> or 00:23:31.250 --> 00:23:31.260 align:start position:0% actually just due to misleading or 00:23:31.260 --> 00:23:35.750 align:start position:0% actually just due to misleading or missing<00:23:31.710> information<00:23:31.860> on<00:23:32.720> block<00:23:33.720> explore<00:23:34.760> so 00:23:35.750 --> 00:23:35.760 align:start position:0% missing information on block explore so 00:23:35.760 --> 00:23:38.860 align:start position:0% missing information on block explore so again<00:23:36.030> for<00:23:36.240> an<00:23:36.330> example<00:23:36.630> like<00:23:36.930> p.m.<00:23:37.890> just<00:23:38.640> a 00:23:38.860 --> 00:23:38.870 align:start position:0% again for an example like p.m. just a 00:23:38.870 --> 00:23:42.980 align:start position:0% again for an example like p.m. just a well-defined<00:23:39.870> set<00:23:40.200> of<00:23:40.290> rules<00:23:40.530> and<00:23:41.990> everyone 00:23:42.980 --> 00:23:42.990 align:start position:0% well-defined set of rules and everyone 00:23:42.990 --> 00:23:45.200 align:start position:0% well-defined set of rules and everyone should<00:23:43.170> be<00:23:43.320> sort<00:23:43.890> of<00:23:43.920> or<00:23:44.190> has<00:23:44.580> access<00:23:44.760> to<00:23:44.970> those 00:23:45.200 --> 00:23:45.210 align:start position:0% should be sort of or has access to those 00:23:45.210 --> 00:23:47.570 align:start position:0% should be sort of or has access to those rules<00:23:45.600> however<00:23:46.050> given<00:23:46.920> the<00:23:46.950> implementation 00:23:47.570 --> 00:23:47.580 align:start position:0% rules however given the implementation 00:23:47.580 --> 00:23:50.420 align:start position:0% rules however given the implementation of<00:23:47.640> some<00:23:47.850> contracts<00:23:48.480> they<00:23:49.020> could<00:23:49.320> look<00:23:49.830> sort 00:23:50.420 --> 00:23:50.430 align:start position:0% of some contracts they could look sort 00:23:50.430 --> 00:23:53.240 align:start position:0% of some contracts they could look sort of<00:23:50.460> non-intuitive<00:23:51.030> and<00:23:51.510> therefore<00:23:52.020> would<00:23:52.950> be 00:23:53.240 --> 00:23:53.250 align:start position:0% of non-intuitive and therefore would be 00:23:53.250 --> 00:23:56.510 align:start position:0% of non-intuitive and therefore would be able<00:23:53.670> to<00:23:53.820> trick<00:23:54.090> you<00:23:54.350> some<00:23:55.350> some<00:23:55.710> bugs 00:23:56.510 --> 00:23:56.520 align:start position:0% able to trick you some some bugs 00:23:56.520 --> 00:23:58.910 align:start position:0% able to trick you some some bugs actually<00:23:56.820> exist<00:23:57.660> in<00:23:57.900> the<00:23:58.020> solidity<00:23:58.350> of<00:23:58.440> pilot 00:23:58.910 --> 00:23:58.920 align:start position:0% actually exist in the solidity of pilot 00:23:58.920 --> 00:24:00.980 align:start position:0% actually exist in the solidity of pilot they're<00:23:59.760> actually<00:24:00.090> usually<00:24:00.390> very<00:24:00.840> well 00:24:00.980 --> 00:24:00.990 align:start position:0% they're actually usually very well 00:24:00.990 --> 00:24:03.680 align:start position:0% they're actually usually very well documented<00:24:01.580> but<00:24:02.580> there<00:24:02.760> can<00:24:03.090> be<00:24:03.120> some<00:24:03.330> that 00:24:03.680 --> 00:24:03.690 align:start position:0% documented but there can be some that 00:24:03.690 --> 00:24:05.620 align:start position:0% documented but there can be some that have<00:24:04.140> not<00:24:04.170> been<00:24:04.350> discovered<00:24:04.530> yet 00:24:05.620 --> 00:24:05.630 align:start position:0% have not been discovered yet 00:24:05.630 --> 00:24:09.680 align:start position:0% have not been discovered yet our<00:24:06.630> sorcerer<00:24:07.170> basil<00:24:07.740> and<00:24:08.250> then<00:24:08.610> for<00:24:08.820> example 00:24:09.680 --> 00:24:09.690 align:start position:0% our sorcerer basil and then for example 00:24:09.690 --> 00:24:12.240 align:start position:0% our sorcerer basil and then for example some<00:24:10.690> things<00:24:10.900> in<00:24:11.200> watching<00:24:11.680> explorers<00:24:12.130> or 00:24:12.240 --> 00:24:12.250 align:start position:0% some things in watching explorers or 00:24:12.250 --> 00:24:14.790 align:start position:0% some things in watching explorers or gently<00:24:12.810> there<00:24:13.810> was<00:24:13.900> a<00:24:13.930> time<00:24:14.230> where<00:24:14.410> we<00:24:14.590> cursed 00:24:14.790 --> 00:24:14.800 align:start position:0% gently there was a time where we cursed 00:24:14.800 --> 00:24:17.100 align:start position:0% gently there was a time where we cursed and<00:24:15.010> only<00:24:15.730> showed<00:24:15.970> you<00:24:16.120> meaty<00:24:16.660> characters 00:24:17.100 --> 00:24:17.110 align:start position:0% and only showed you meaty characters 00:24:17.110 --> 00:24:19.140 align:start position:0% and only showed you meaty characters wide<00:24:17.320> if<00:24:17.710> you<00:24:17.830> were<00:24:17.950> to<00:24:18.040> upload<00:24:18.490> a<00:24:18.520> contract 00:24:19.140 --> 00:24:19.150 align:start position:0% wide if you were to upload a contract 00:24:19.150 --> 00:24:21.090 align:start position:0% wide if you were to upload a contract had<00:24:19.450> something<00:24:19.870> outside<00:24:20.350> of<00:24:20.410> that<00:24:20.710> you 00:24:21.090 --> 00:24:21.100 align:start position:0% had something outside of that you 00:24:21.100 --> 00:24:22.650 align:start position:0% had something outside of that you wouldn't<00:24:21.220> be<00:24:21.370> able<00:24:21.430> to<00:24:21.520> see<00:24:21.790> say<00:24:22.360> that<00:24:22.510> there 00:24:22.650 --> 00:24:22.660 align:start position:0% wouldn't be able to see say that there 00:24:22.660 --> 00:24:25.500 align:start position:0% wouldn't be able to see say that there was<00:24:22.750> a<00:24:22.810> salmon<00:24:23.110> or<00:24:23.200> a<00:24:23.650> trans<00:24:23.950> person<00:24:24.510> that's 00:24:25.500 --> 00:24:25.510 align:start position:0% was a salmon or a trans person that's 00:24:25.510 --> 00:24:27.270 align:start position:0% was a salmon or a trans person that's the<00:24:25.840> general<00:24:26.140> gist<00:24:26.440> and<00:24:26.770> we'll<00:24:26.890> go<00:24:27.010> into<00:24:27.190> some 00:24:27.270 --> 00:24:27.280 align:start position:0% the general gist and we'll go into some 00:24:27.280 --> 00:24:32.730 align:start position:0% the general gist and we'll go into some fees<00:24:29.790> this<00:24:30.790> next<00:24:31.120> slide<00:24:31.180> is<00:24:31.810> fun<00:24:32.260> remember 00:24:32.730 --> 00:24:32.740 align:start position:0% fees this next slide is fun remember 00:24:32.740 --> 00:24:35.400 align:start position:0% fees this next slide is fun remember you'll<00:24:32.830> hear<00:24:33.130> it<00:24:33.250> so<00:24:34.090> just<00:24:34.600> love<00:24:35.020> the<00:24:35.140> slides 00:24:35.400 --> 00:24:35.410 align:start position:0% you'll hear it so just love the slides 00:24:35.410 --> 00:24:41.550 align:start position:0% you'll hear it so just love the slides up<00:24:36.030> some<00:24:37.030> people<00:24:37.240> came<00:24:37.390> in<00:24:38.250> so<00:24:39.250> make<00:24:39.700> sure<00:24:40.560> you 00:24:41.550 --> 00:24:41.560 align:start position:0% up some people came in so make sure you 00:24:41.560 --> 00:24:45.660 align:start position:0% up some people came in so make sure you go<00:24:41.890> to<00:24:41.920> these<00:24:42.730> slides<00:24:43.180> at<00:24:44.010> double<00:24:45.010> codes<00:24:45.460> by 00:24:45.660 --> 00:24:45.670 align:start position:0% go to these slides at double codes by 00:24:45.670 --> 00:24:49.380 align:start position:0% go to these slides at double codes by step<00:24:45.880> compaction<00:24:48.000> so<00:24:49.000> this<00:24:49.090> next<00:24:49.270> one 00:24:49.380 --> 00:24:49.390 align:start position:0% step compaction so this next one 00:24:49.390 --> 00:24:52.110 align:start position:0% step compaction so this next one slightly<00:24:49.900> gonna<00:24:50.170> skip<00:24:50.530> over<00:24:50.710> but<00:24:51.430> it's<00:24:51.790> fun 00:24:52.110 --> 00:24:52.120 align:start position:0% slightly gonna skip over but it's fun 00:24:52.120 --> 00:24:54.900 align:start position:0% slightly gonna skip over but it's fun and<00:24:52.420> I<00:24:52.930> spend<00:24:53.230> too<00:24:53.980> much<00:24:54.070> time<00:24:54.160> on<00:24:54.340> it<00:24:54.520> so<00:24:54.670> you 00:24:54.900 --> 00:24:54.910 align:start position:0% and I spend too much time on it so you 00:24:54.910 --> 00:25:00.000 align:start position:0% and I spend too much time on it so you guys<00:24:55.150> should<00:24:56.940> just<00:24:57.940> check<00:24:58.060> it<00:24:58.210> out<00:24:58.860> just<00:24:59.860> tell 00:25:00.000 --> 00:25:00.010 align:start position:0% guys should just check it out just tell 00:25:00.010 --> 00:25:03.300 align:start position:0% guys should just check it out just tell me<00:25:00.130> if<00:25:00.190> you<00:25:00.250> liked<00:25:00.460> it<00:25:00.670> we'll<00:25:01.090> go<00:25:01.210> ahead<00:25:02.310> the 00:25:03.300 --> 00:25:03.310 align:start position:0% me if you liked it we'll go ahead the 00:25:03.310 --> 00:25:06.540 align:start position:0% me if you liked it we'll go ahead the trace<00:25:03.550> Buster<00:25:03.970> Buster<00:25:04.440> anyway<00:25:05.440> the<00:25:06.040> so<00:25:06.190> far<00:25:06.430> is 00:25:06.540 --> 00:25:06.550 align:start position:0% trace Buster Buster anyway the so far is 00:25:06.550 --> 00:25:08.070 align:start position:0% trace Buster Buster anyway the so far is covered<00:25:06.820> truffle<00:25:07.180> ganache<00:25:07.780> ganache 00:25:08.070 --> 00:25:08.080 align:start position:0% covered truffle ganache ganache 00:25:08.080 --> 00:25:09.960 align:start position:0% covered truffle ganache ganache porkiness<00:25:08.500> fallback<00:25:09.370> functions<00:25:09.790> for 00:25:09.960 --> 00:25:09.970 align:start position:0% porkiness fallback functions for 00:25:09.970 --> 00:25:12.720 align:start position:0% porkiness fallback functions for instance<00:25:10.030> the<00:25:10.480> exploit<00:25:11.380> testing<00:25:12.280> a<00:25:12.310> Dow 00:25:12.720 --> 00:25:12.730 align:start position:0% instance the exploit testing a Dow 00:25:12.730 --> 00:25:16.350 align:start position:0% instance the exploit testing a Dow Constantine<00:25:13.450> elements<00:25:14.320> in<00:25:14.470> Istanbul<00:25:15.360> Regency 00:25:16.350 --> 00:25:16.360 align:start position:0% Constantine elements in Istanbul Regency 00:25:16.360 --> 00:25:19.320 align:start position:0% Constantine elements in Istanbul Regency protection<00:25:16.990> and<00:25:17.200> honey<00:25:17.530> pots<00:25:18.330> questions 00:25:19.320 --> 00:25:19.330 align:start position:0% protection and honey pots questions 00:25:19.330 --> 00:25:25.310 align:start position:0% protection and honey pots questions about<00:25:19.750> any<00:25:20.140> of<00:25:20.290> that 00:25:25.310 --> 00:25:25.320 align:start position:0% 00:25:25.320 --> 00:25:31.010 align:start position:0% yes<00:25:28.700> you<00:25:29.700> remember<00:25:29.760> the<00:25:30.030> the<00:25:30.600> difference<00:25:30.930> is 00:25:31.010 --> 00:25:31.020 align:start position:0% yes you remember the the difference is 00:25:31.020 --> 00:25:32.900 align:start position:0% yes you remember the the difference is something<00:25:31.290> balanced<00:25:31.590> if<00:25:31.890> the<00:25:32.370> way<00:25:32.490> it<00:25:32.640> fails 00:25:32.900 --> 00:25:32.910 align:start position:0% something balanced if the way it fails 00:25:32.910 --> 00:25:40.150 align:start position:0% something balanced if the way it fails right<00:25:34.400> if<00:25:35.400> if<00:25:35.970> I<00:25:36.150> recall<00:25:36.330> correctly<00:25:36.720> is<00:25:37.440> I 00:25:40.150 --> 00:25:40.160 align:start position:0% 00:25:40.160 --> 00:25:43.850 align:start position:0% believe<00:25:41.160> it's<00:25:41.610> what<00:25:41.940> what<00:25:42.600> is<00:25:43.020> passed<00:25:43.440> along 00:25:43.850 --> 00:25:43.860 align:start position:0% believe it's what what is passed along 00:25:43.860 --> 00:25:46.340 align:start position:0% believe it's what what is passed along as<00:25:44.250> your<00:25:44.460> message<00:25:44.820> sender<00:25:45.570> and<00:25:45.930> like<00:25:46.110> sorta 00:25:46.340 --> 00:25:46.350 align:start position:0% as your message sender and like sorta 00:25:46.350 --> 00:25:50.960 align:start position:0% as your message sender and like sorta like<00:25:46.440> a<00:25:46.470> context<00:25:47.160> that<00:25:47.310> is<00:25:47.670> calling<00:25:48.000> or<00:25:49.040> yeah<00:25:50.040> I 00:25:50.960 --> 00:25:50.970 align:start position:0% like a context that is calling or yeah I 00:25:50.970 --> 00:25:52.850 align:start position:0% like a context that is calling or yeah I think<00:25:51.480> it<00:25:51.600> is<00:25:51.720> just<00:25:51.930> the<00:25:51.990> way<00:25:52.230> that<00:25:52.440> it<00:25:52.590> fails 00:25:52.850 --> 00:25:52.860 align:start position:0% think it is just the way that it fails 00:25:52.860 --> 00:25:56.060 align:start position:0% think it is just the way that it fails because<00:25:54.050> actually<00:25:55.050> really<00:25:55.380> excellent<00:25:55.590> answer 00:25:56.060 --> 00:25:56.070 align:start position:0% because actually really excellent answer 00:25:56.070 --> 00:25:57.620 align:start position:0% because actually really excellent answer for<00:25:56.250> on<00:25:56.460> Stack<00:25:56.700> Overflow<00:25:56.820> Isis<00:25:57.420> can't 00:25:57.620 --> 00:25:57.630 align:start position:0% for on Stack Overflow Isis can't 00:25:57.630 --> 00:26:08.650 align:start position:0% for on Stack Overflow Isis can't remember<00:25:58.430> which<00:25:59.430> one 00:26:08.650 --> 00:26:08.660 align:start position:0% 00:26:08.660 --> 00:26:15.730 align:start position:0% [Music] 00:26:15.730 --> 00:26:15.740 align:start position:0% 00:26:15.740 --> 00:26:18.740 align:start position:0% okay<00:26:16.740> so<00:26:16.800> Sandra<00:26:17.310> will<00:26:17.670> return<00:26:18.000> a<00:26:18.060> boolean<00:26:18.240> yes 00:26:18.740 --> 00:26:18.750 align:start position:0% okay so Sandra will return a boolean yes 00:26:18.750 --> 00:26:21.440 align:start position:0% okay so Sandra will return a boolean yes it<00:26:18.930> works<00:26:19.110> or<00:26:19.350> not<00:26:19.380> good<00:26:19.740> and<00:26:20.010> then<00:26:20.640> transfer 00:26:21.440 --> 00:26:21.450 align:start position:0% it works or not good and then transfer 00:26:21.450 --> 00:26:40.670 align:start position:0% it works or not good and then transfer will<00:26:38.000> right<00:26:39.000> yeah<00:26:39.300> so<00:26:39.600> I<00:26:39.630> it's<00:26:40.410> kind<00:26:40.530> of<00:26:40.560> like 00:26:40.670 --> 00:26:40.680 align:start position:0% will right yeah so I it's kind of like 00:26:40.680 --> 00:26:44.630 align:start position:0% will right yeah so I it's kind of like an<00:26:40.950> idea<00:26:41.220> so<00:26:41.490> it's<00:26:41.610> like<00:26:43.070> you<00:26:44.070> can<00:26:44.100> have<00:26:44.310> like 00:26:44.630 --> 00:26:44.640 align:start position:0% an idea so it's like you can have like 00:26:44.640 --> 00:26:47.330 align:start position:0% an idea so it's like you can have like lots<00:26:44.850> of<00:26:44.970> different<00:26:45.210> types<00:26:45.420> of<00:26:45.540> honey<00:26:45.720> pots<00:26:46.340> so 00:26:47.330 --> 00:26:47.340 align:start position:0% lots of different types of honey pots so 00:26:47.340 --> 00:26:49.160 align:start position:0% lots of different types of honey pots so in<00:26:47.790> info<00:26:48.120> set<00:26:48.330> it<00:26:48.660> would<00:26:48.780> be<00:26:48.840> probably<00:26:49.050> a 00:26:49.160 --> 00:26:49.170 align:start position:0% in info set it would be probably a 00:26:49.170 --> 00:26:50.750 align:start position:0% in info set it would be probably a mousetrap 00:26:50.750 --> 00:26:50.760 align:start position:0% mousetrap 00:26:50.760 --> 00:26:52.550 align:start position:0% mousetrap sort<00:26:51.330> of<00:26:51.360> like<00:26:51.510> a<00:26:51.600> honey<00:26:52.020> pot<00:26:52.080> in<00:26:52.380> at<00:26:52.470> the 00:26:52.550 --> 00:26:52.560 align:start position:0% sort of like a honey pot in at the 00:26:52.560 --> 00:26:53.970 align:start position:0% sort of like a honey pot in at the second<00:26:52.890> it<00:26:53.100> is<00:26:53.220> just<00:26:53.460> like 00:26:53.970 --> 00:26:53.980 align:start position:0% second it is just like 00:26:53.980 --> 00:26:56.580 align:start position:0% second it is just like like<00:26:54.340> or<00:26:55.299> our<00:26:55.600> way<00:26:55.750> to<00:26:55.809> learn<00:26:56.169> about<00:26:56.350> your 00:26:56.580 --> 00:26:56.590 align:start position:0% like or our way to learn about your 00:26:56.590 --> 00:26:58.289 align:start position:0% like or our way to learn about your attacker<00:26:56.799> so<00:26:57.070> you<00:26:57.159> set<00:26:57.340> up<00:26:57.429> a<00:26:57.519> network<00:26:57.909> that 00:26:58.289 --> 00:26:58.299 align:start position:0% attacker so you set up a network that 00:26:58.299 --> 00:26:59.879 align:start position:0% attacker so you set up a network that looks<00:26:58.419> open<00:26:58.690> and<00:26:59.260> see<00:26:59.440> what<00:26:59.559> the<00:26:59.649> attacker 00:26:59.879 --> 00:26:59.889 align:start position:0% looks open and see what the attacker 00:26:59.889 --> 00:27:01.889 align:start position:0% looks open and see what the attacker does<00:27:00.580> that's<00:27:01.000> right<00:27:01.210> that<00:27:01.510> we<00:27:01.600> can<00:27:01.750> learn<00:27:01.840> from 00:27:01.889 --> 00:27:01.899 align:start position:0% does that's right that we can learn from 00:27:01.899 --> 00:27:07.879 align:start position:0% does that's right that we can learn from you<00:27:02.460> so<00:27:03.460> an<00:27:03.789> InfoSec<00:27:04.380> mousetrap<00:27:05.380> is<00:27:06.029> a<00:27:07.029> way<00:27:07.539> of 00:27:07.879 --> 00:27:07.889 align:start position:0% you so an InfoSec mousetrap is a way of 00:27:07.889 --> 00:27:11.009 align:start position:0% you so an InfoSec mousetrap is a way of trying<00:27:08.889> to<00:27:09.070> convince<00:27:09.309> the<00:27:09.850> attacker<00:27:10.419> to<00:27:10.809> come 00:27:11.009 --> 00:27:11.019 align:start position:0% trying to convince the attacker to come 00:27:11.019 --> 00:27:13.110 align:start position:0% trying to convince the attacker to come in<00:27:11.169> and<00:27:11.289> see<00:27:11.409> your<00:27:11.529> network<00:27:11.769> and<00:27:12.279> give 00:27:13.110 --> 00:27:13.120 align:start position:0% in and see your network and give 00:27:13.120 --> 00:27:15.810 align:start position:0% in and see your network and give something<00:27:13.419> up<00:27:13.830> somehow<00:27:14.830> and<00:27:15.309> that<00:27:15.610> way<00:27:15.700> you 00:27:15.810 --> 00:27:15.820 align:start position:0% something up somehow and that way you 00:27:15.820 --> 00:27:19.590 align:start position:0% something up somehow and that way you can<00:27:16.000> catch<00:27:16.299> them<00:27:16.600> and<00:27:16.960> win<00:27:17.950> that<00:27:17.980> way<00:27:18.429> so<00:27:19.299> we're 00:27:19.590 --> 00:27:19.600 align:start position:0% can catch them and win that way so we're 00:27:19.600 --> 00:27:21.180 align:start position:0% can catch them and win that way so we're actually<00:27:19.750> so<00:27:20.139> in<00:27:20.289> the<00:27:20.409> theory<00:27:20.649> of<00:27:20.710> them<00:27:20.950> cause 00:27:21.180 --> 00:27:21.190 align:start position:0% actually so in the theory of them cause 00:27:21.190 --> 00:27:25.350 align:start position:0% actually so in the theory of them cause a<00:27:22.029> honeypot<00:27:22.539> or<00:27:23.049> a<00:27:23.519> mastermind<00:27:24.519> so<00:27:25.029> a<00:27:25.059> honeypot 00:27:25.350 --> 00:27:25.360 align:start position:0% a honeypot or a mastermind so a honeypot 00:27:25.360 --> 00:27:28.169 align:start position:0% a honeypot or a mastermind so a honeypot is<00:27:25.720> the<00:27:26.320> contract<00:27:26.830> that<00:27:27.070> fools<00:27:27.340> somebody<00:27:28.029> an 00:27:28.169 --> 00:27:28.179 align:start position:0% is the contract that fools somebody an 00:27:28.179 --> 00:27:30.019 align:start position:0% is the contract that fools somebody an attacker<00:27:28.480> into<00:27:29.260> giving<00:27:29.500> something<00:27:29.679> up 00:27:30.019 --> 00:27:30.029 align:start position:0% attacker into giving something up 00:27:30.029 --> 00:27:37.139 align:start position:0% attacker into giving something up usually<00:27:31.029> that's<00:27:31.210> going<00:27:31.330> to<00:27:31.720> be<00:27:35.850> the<00:27:36.850> trick 00:27:37.139 --> 00:27:37.149 align:start position:0% usually that's going to be the trick 00:27:37.149 --> 00:27:40.590 align:start position:0% usually that's going to be the trick transfer<00:27:37.630> throws<00:27:37.929> in<00:27:38.460> senators<00:27:39.460> box<00:27:39.760> failure 00:27:40.590 --> 00:27:40.600 align:start position:0% transfer throws in senators box failure 00:27:40.600 --> 00:27:43.259 align:start position:0% transfer throws in senators box failure all<00:27:41.230> right<00:27:41.320> so<00:27:41.559> work<00:27:42.190> self<00:27:42.399> time<00:27:42.580> we're<00:27:43.000> going 00:27:43.259 --> 00:27:43.269 align:start position:0% all right so work self time we're going 00:27:43.269 --> 00:27:45.110 align:start position:0% all right so work self time we're going to<00:27:43.330> take<00:27:43.450> all<00:27:43.630> of<00:27:43.659> that<00:27:43.779> and<00:27:43.960> we're<00:27:44.590> going<00:27:44.769> to 00:27:45.110 --> 00:27:45.120 align:start position:0% to take all of that and we're going to 00:27:45.120 --> 00:27:49.529 align:start position:0% to take all of that and we're going to exploit<00:27:46.120> or<00:27:47.159> attempt<00:27:48.159> to<00:27:48.220> exploit<00:27:48.909> ain't<00:27:49.389> no 00:27:49.529 --> 00:27:49.539 align:start position:0% exploit or attempt to exploit ain't no 00:27:49.539 --> 00:27:53.220 align:start position:0% exploit or attempt to exploit ain't no and<00:27:49.750> honeypot<00:27:50.230> on<00:27:50.830> the<00:27:51.250> net<00:27:51.460> and<00:27:51.730> so<00:27:52.110> as<00:27:53.110> an 00:27:53.220 --> 00:27:53.230 align:start position:0% and honeypot on the net and so as an 00:27:53.230 --> 00:27:56.639 align:start position:0% and honeypot on the net and so as an overview<00:27:53.529> what<00:27:53.950> we'll<00:27:54.130> be<00:27:54.250> doing<00:27:54.370> is<00:27:55.649> taking 00:27:56.639 --> 00:27:56.649 align:start position:0% overview what we'll be doing is taking 00:27:56.649 --> 00:27:58.740 align:start position:0% overview what we'll be doing is taking the<00:27:56.980> code<00:27:57.460> that<00:27:57.760> we<00:27:57.880> see<00:27:58.029> young<00:27:58.149> ether<00:27:58.480> scans 00:27:58.740 --> 00:27:58.750 align:start position:0% the code that we see young ether scans 00:27:58.750 --> 00:28:02.399 align:start position:0% the code that we see young ether scans so<00:27:59.080> that<00:27:59.289> this<00:27:59.500> this<00:28:00.340> person<00:28:01.059> that<00:28:01.600> of<00:28:02.139> one<00:28:02.320> of 00:28:02.399 --> 00:28:02.409 align:start position:0% so that this this person that of one of 00:28:02.409 --> 00:28:08.009 align:start position:0% so that this this person that of one of this<00:28:02.500> contract<00:28:02.950> in<00:28:03.279> this<00:28:03.399> one<00:28:06.149> they<00:28:07.149> uploaded 00:28:08.009 --> 00:28:08.019 align:start position:0% this contract in this one they uploaded 00:28:08.019 --> 00:28:11.370 align:start position:0% this contract in this one they uploaded their<00:28:08.380> contract<00:28:08.980> code<00:28:09.820> to<00:28:10.299> ether<00:28:10.570> skin<00:28:10.840> except 00:28:11.370 --> 00:28:11.380 align:start position:0% their contract code to ether skin except 00:28:11.380 --> 00:28:14.039 align:start position:0% their contract code to ether skin except it<00:28:11.679> wasn't<00:28:11.980> their<00:28:12.730> contract<00:28:13.210> code<00:28:13.419> so<00:28:13.899> even 00:28:14.039 --> 00:28:14.049 align:start position:0% it wasn't their contract code so even 00:28:14.049 --> 00:28:15.930 align:start position:0% it wasn't their contract code so even though<00:28:14.139> ethers<00:28:14.559> can't<00:28:14.799> verify<00:28:15.130> this<00:28:15.399> right<00:28:15.760> by 00:28:15.930 --> 00:28:15.940 align:start position:0% though ethers can't verify this right by 00:28:15.940 --> 00:28:18.450 align:start position:0% though ethers can't verify this right by code<00:28:16.240> there's<00:28:16.720> some<00:28:16.840> tricks<00:28:17.169> in<00:28:17.350> there<00:28:17.559> that 00:28:18.450 --> 00:28:18.460 align:start position:0% code there's some tricks in there that 00:28:18.460 --> 00:28:20.639 align:start position:0% code there's some tricks in there that make<00:28:18.610> it<00:28:18.789> actually<00:28:19.779> behave<00:28:20.049> differently<00:28:20.440> than 00:28:20.639 --> 00:28:20.649 align:start position:0% make it actually behave differently than 00:28:20.649 --> 00:28:23.310 align:start position:0% make it actually behave differently than what<00:28:20.710> you<00:28:20.830> see<00:28:21.070> in<00:28:21.100> the<00:28:21.429> code<00:28:21.659> and<00:28:22.659> so<00:28:23.110> we're 00:28:23.310 --> 00:28:23.320 align:start position:0% what you see in the code and so we're 00:28:23.320 --> 00:28:27.060 align:start position:0% what you see in the code and so we're going<00:28:23.470> to<00:28:23.590> see<00:28:23.950> how<00:28:24.750> if<00:28:25.750> you<00:28:26.200> just<00:28:26.440> wanted<00:28:27.039> to 00:28:27.060 --> 00:28:27.070 align:start position:0% going to see how if you just wanted to 00:28:27.070 --> 00:28:29.250 align:start position:0% going to see how if you just wanted to exploit<00:28:27.940> this<00:28:28.179> because<00:28:28.510> you're<00:28:28.659> a<00:28:28.690> bad<00:28:29.080> guy 00:28:29.250 --> 00:28:29.260 align:start position:0% exploit this because you're a bad guy 00:28:29.260 --> 00:28:32.100 align:start position:0% exploit this because you're a bad guy and<00:28:30.070> you<00:28:30.519> wanted<00:28:30.760> to<00:28:30.850> steal<00:28:31.179> the<00:28:31.389> ether<00:28:31.659> stored 00:28:32.100 --> 00:28:32.110 align:start position:0% and you wanted to steal the ether stored 00:28:32.110 --> 00:28:34.110 align:start position:0% and you wanted to steal the ether stored in<00:28:32.230> the<00:28:32.320> contract<00:28:32.830> it<00:28:33.100> would<00:28:33.190> fail<00:28:33.490> and<00:28:33.970> so 00:28:34.110 --> 00:28:34.120 align:start position:0% in the contract it would fail and so 00:28:34.120 --> 00:28:35.310 align:start position:0% in the contract it would fail and so we're<00:28:34.240> going<00:28:34.330> to<00:28:34.389> do<00:28:34.510> that<00:28:34.690> we're<00:28:34.840> gonna<00:28:34.929> we're 00:28:35.310 --> 00:28:35.320 align:start position:0% we're going to do that we're gonna we're 00:28:35.320 --> 00:28:36.450 align:start position:0% we're going to do that we're gonna we're going<00:28:35.440> to<00:28:35.500> run<00:28:35.620> this<00:28:35.740> and<00:28:36.039> we're<00:28:36.220> gonna<00:28:36.309> run 00:28:36.450 --> 00:28:36.460 align:start position:0% going to run this and we're gonna run 00:28:36.460 --> 00:28:38.340 align:start position:0% going to run this and we're gonna run out<00:28:36.610> locally<00:28:37.029> and<00:28:37.149> ganache<00:28:37.389> and<00:28:37.659> we're<00:28:38.260> gonna 00:28:38.340 --> 00:28:38.350 align:start position:0% out locally and ganache and we're gonna 00:28:38.350 --> 00:28:39.930 align:start position:0% out locally and ganache and we're gonna see<00:28:38.529> that<00:28:38.559> it<00:28:38.769> fails<00:28:38.980> and<00:28:39.610> then<00:28:39.700> we're<00:28:39.850> gonna 00:28:39.930 --> 00:28:39.940 align:start position:0% see that it fails and then we're gonna 00:28:39.940 --> 00:28:42.029 align:start position:0% see that it fails and then we're gonna run<00:28:40.149> it<00:28:40.330> locally<00:28:40.510> and<00:28:40.870> ganache<00:28:41.350> with<00:28:41.590> forking 00:28:42.029 --> 00:28:42.039 align:start position:0% run it locally and ganache with forking 00:28:42.039 --> 00:28:43.020 align:start position:0% run it locally and ganache with forking enable<00:28:42.429> off 00:28:43.020 --> 00:28:43.030 align:start position:0% enable off 00:28:43.030 --> 00:28:45.330 align:start position:0% enable off and<00:28:43.630> the<00:28:44.350> conference<00:28:44.710> Wi-Fi<00:28:44.890> is<00:28:45.100> a<00:28:45.160> little 00:28:45.330 --> 00:28:45.340 align:start position:0% and the conference Wi-Fi is a little 00:28:45.340 --> 00:28:49.070 align:start position:0% and the conference Wi-Fi is a little rough<00:28:45.520> but<00:28:46.270> we're<00:28:46.420> gonna<00:28:46.510> try<00:28:46.720> anyway<00:28:47.190> and 00:28:49.070 --> 00:28:49.080 align:start position:0% rough but we're gonna try anyway and 00:28:49.080 --> 00:28:51.300 align:start position:0% rough but we're gonna try anyway and yeah<00:28:50.080> it'll<00:28:50.230> be<00:28:50.320> fun 00:28:51.300 --> 00:28:51.310 align:start position:0% yeah it'll be fun 00:28:51.310 --> 00:28:55.830 align:start position:0% yeah it'll be fun so<00:28:51.940> everyone<00:28:52.480> needs<00:28:52.570> to<00:28:53.700> go<00:28:54.700> to<00:28:55.210> workshop<00:28:55.600> will 00:28:55.830 --> 00:28:55.840 align:start position:0% so everyone needs to go to workshop will 00:28:55.840 --> 00:28:58.830 align:start position:0% so everyone needs to go to workshop will GE<00:28:56.050> to<00:28:56.290> this<00:28:56.410> slide<00:28:56.730> figure<00:28:57.730> on<00:28:57.850> download<00:28:58.720> no 00:28:58.830 --> 00:28:58.840 align:start position:0% GE to this slide figure on download no 00:28:58.840 --> 00:29:00.540 align:start position:0% GE to this slide figure on download no js'<00:28:59.110> I<00:28:59.320> just<00:28:59.470> put<00:28:59.590> 10<00:28:59.830> there<00:29:00.010> it<00:29:00.190> should<00:29:00.370> work 00:29:00.540 --> 00:29:00.550 align:start position:0% js' I just put 10 there it should work 00:29:00.550 --> 00:29:04.320 align:start position:0% js' I just put 10 there it should work on<00:29:00.700> 8<00:29:01.060> it<00:29:01.390> will<00:29:01.900> likely<00:29:02.170> work<00:29:02.470> on<00:29:02.680> 12<00:29:03.330> that's 00:29:04.320 --> 00:29:04.330 align:start position:0% on 8 it will likely work on 12 that's 00:29:04.330 --> 00:29:06.750 align:start position:0% on 8 it will likely work on 12 that's not<00:29:04.480> a<00:29:04.510> lot<00:29:04.720> of<00:29:05.040> very<00:29:06.040> important<00:29:06.460> doesn't<00:29:06.670> work 00:29:06.750 --> 00:29:06.760 align:start position:0% not a lot of very important doesn't work 00:29:06.760 --> 00:29:10.500 align:start position:0% not a lot of very important doesn't work wrong<00:29:07.000> well<00:29:08.460> if<00:29:09.460> you<00:29:09.550> want<00:29:09.790> to<00:29:09.970> use<00:29:10.120> you<00:29:10.360> is 00:29:10.500 --> 00:29:10.510 align:start position:0% wrong well if you want to use you is 00:29:10.510 --> 00:29:12.030 align:start position:0% wrong well if you want to use you is because<00:29:10.990> you're<00:29:11.260> more<00:29:11.380> comfortable<00:29:11.530> you<00:29:12.010> I 00:29:12.030 --> 00:29:12.040 align:start position:0% because you're more comfortable you I 00:29:12.040 --> 00:29:13.680 align:start position:0% because you're more comfortable you I think<00:29:12.370> you<00:29:12.520> down<00:29:12.670> try<00:29:13.030> to<00:29:13.060> download<00:29:13.330> browse 00:29:13.680 --> 00:29:13.690 align:start position:0% think you down try to download browse 00:29:13.690 --> 00:29:17.670 align:start position:0% think you down try to download browse your<00:29:13.840> alpha<00:29:14.320> I<00:29:14.860> can<00:29:15.790> also<00:29:16.240> try<00:29:16.810> to<00:29:16.840> set<00:29:17.290> up<00:29:17.440> I 00:29:17.670 --> 00:29:17.680 align:start position:0% your alpha I can also try to set up I 00:29:17.680 --> 00:29:20.100 align:start position:0% your alpha I can also try to set up I have<00:29:17.950> all<00:29:18.190> the<00:29:18.280> version<00:29:18.610> for<00:29:18.820> Mac<00:29:18.970> Windows<00:29:19.110> my 00:29:20.100 --> 00:29:20.110 align:start position:0% have all the version for Mac Windows my 00:29:20.110 --> 00:29:21.060 align:start position:0% have all the version for Mac Windows my next<00:29:20.350> phone<00:29:20.500> my<00:29:20.620> laptop 00:29:21.060 --> 00:29:21.070 align:start position:0% next phone my laptop 00:29:21.070 --> 00:29:22.830 align:start position:0% next phone my laptop and<00:29:21.250> so<00:29:21.400> I<00:29:21.430> can<00:29:21.610> give<00:29:21.700> you<00:29:21.820> links<00:29:22.330> to<00:29:22.510> try<00:29:22.780> to 00:29:22.830 --> 00:29:22.840 align:start position:0% and so I can give you links to try to 00:29:22.840 --> 00:29:27.870 align:start position:0% and so I can give you links to try to download<00:29:23.020> right<00:29:23.560> from<00:29:23.770> my<00:29:24.340> laptop<00:29:26.430> if<00:29:27.430> we<00:29:27.610> have 00:29:27.870 --> 00:29:27.880 align:start position:0% download right from my laptop if we have 00:29:27.880 --> 00:29:31.950 align:start position:0% download right from my laptop if we have to<00:29:28.090> or<00:29:28.630> install<00:29:29.470> ganache<00:29:29.890> COI<00:29:30.660> and<00:29:31.660> you<00:29:31.780> can 00:29:31.950 --> 00:29:31.960 align:start position:0% to or install ganache COI and you can 00:29:31.960 --> 00:29:34.380 align:start position:0% to or install ganache COI and you can choose<00:29:32.170> the<00:29:32.440> global<00:29:32.740> black<00:29:33.190> here<00:29:33.460> if<00:29:34.090> everyone 00:29:34.380 --> 00:29:34.390 align:start position:0% choose the global black here if everyone 00:29:34.390 --> 00:29:41.070 align:start position:0% choose the global black here if everyone needs<00:29:34.540> help<00:29:34.630> with<00:29:35.530> note<00:29:36.250> or<00:29:36.840> MPN<00:29:37.890> no<00:29:39.270> and<00:29:40.270> then 00:29:41.070 --> 00:29:41.080 align:start position:0% needs help with note or MPN no and then 00:29:41.080 --> 00:29:43.530 align:start position:0% needs help with note or MPN no and then you<00:29:41.410> will<00:29:41.560> want<00:29:41.770> to<00:29:42.160> clone<00:29:42.520> this<00:29:43.000> language 00:29:43.530 --> 00:29:43.540 align:start position:0% you will want to clone this language 00:29:43.540 --> 00:29:47.220 align:start position:0% you will want to clone this language that's<00:29:43.720> we're<00:29:44.020> going<00:29:44.800> to<00:29:45.010> this<00:29:45.160> website<00:29:46.230> will 00:29:47.220 --> 00:29:47.230 align:start position:0% that's we're going to this website will 00:29:47.230 --> 00:29:51.420 align:start position:0% that's we're going to this website will help<00:29:47.500> get<00:29:48.280> this<00:29:48.550> easily<00:29:49.240> so<00:29:50.050> clone<00:29:50.680> this<00:29:50.920> if 00:29:51.420 --> 00:29:51.430 align:start position:0% help get this easily so clone this if 00:29:51.430 --> 00:29:53.670 align:start position:0% help get this easily so clone this if you<00:29:51.490> need<00:29:51.640> help<00:29:51.730> with<00:29:51.880> that<00:29:51.910> let<00:29:52.150> us<00:29:52.240> know<00:29:52.680> and 00:29:53.670 --> 00:29:53.680 align:start position:0% you need help with that let us know and 00:29:53.680 --> 00:29:56.790 align:start position:0% you need help with that let us know and then<00:29:54.640> we<00:29:55.120> run<00:29:55.210> npm<00:29:55.660> install<00:29:56.020> in<00:29:56.170> here<00:29:56.410> again 00:29:56.790 --> 00:29:56.800 align:start position:0% then we run npm install in here again 00:29:56.800 --> 00:30:00.150 align:start position:0% then we run npm install in here again it's<00:29:57.610> workshop<00:29:57.970> so<00:29:58.720> ask<00:29:59.410> your<00:29:59.710> neighbor<00:29:59.890> ask 00:30:00.150 --> 00:30:00.160 align:start position:0% it's workshop so ask your neighbor ask 00:30:00.160 --> 00:30:11.700 align:start position:0% it's workshop so ask your neighbor ask us<00:30:00.400> and<00:30:00.670> we'll<00:30:00.970> help<00:30:01.150> you<00:30:02.430> David<00:30:03.430> Clarke 00:30:11.700 --> 00:30:11.710 align:start position:0% 00:30:11.710 --> 00:30:16.180 align:start position:0% [Applause]