WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.130 align:start position:0% [Applause] 00:00:12.130 --> 00:00:12.140 align:start position:0% 00:00:12.140 --> 00:00:14.510 align:start position:0% you<00:00:13.140> may<00:00:13.290> as<00:00:13.350> well<00:00:13.440> just<00:00:13.710> dive<00:00:14.130> in<00:00:14.340> because 00:00:14.510 --> 00:00:14.520 align:start position:0% you may as well just dive in because 00:00:14.520 --> 00:00:17.210 align:start position:0% you may as well just dive in because there's<00:00:14.760> a<00:00:14.790> lot<00:00:14.940> to<00:00:15.150> to<00:00:15.600> get<00:00:15.809> through<00:00:16.049> here<00:00:16.440> so 00:00:17.210 --> 00:00:17.220 align:start position:0% there's a lot to to get through here so 00:00:17.220 --> 00:00:20.540 align:start position:0% there's a lot to to get through here so today<00:00:17.670> we're<00:00:18.390> gonna<00:00:18.480> be<00:00:18.600> talking<00:00:18.840> about<00:00:19.550> the 00:00:20.540 --> 00:00:20.550 align:start position:0% today we're gonna be talking about the 00:00:20.550 --> 00:00:23.630 align:start position:0% today we're gonna be talking about the dark<00:00:20.850> parts<00:00:21.300> of<00:00:22.170> contract<00:00:22.770> run<00:00:23.010> time<00:00:23.250> new 00:00:23.630 --> 00:00:23.640 align:start position:0% dark parts of contract run time new 00:00:23.640 --> 00:00:27.530 align:start position:0% dark parts of contract run time new ability<00:00:24.800> more<00:00:25.800> specifically<00:00:26.540> defending 00:00:27.530 --> 00:00:27.540 align:start position:0% ability more specifically defending 00:00:27.540 --> 00:00:30.769 align:start position:0% ability more specifically defending against<00:00:27.810> that<00:00:28.110> I'm<00:00:29.040> 0h<00:00:29.640> thank<00:00:30.419> you<00:00:30.509> guys<00:00:30.660> for 00:00:30.769 --> 00:00:30.779 align:start position:0% against that I'm 0h thank you guys for 00:00:30.779 --> 00:00:34.850 align:start position:0% against that I'm 0h thank you guys for being<00:00:30.930> here<00:00:32.180> alright<00:00:33.180> so<00:00:33.480> here's<00:00:34.350> the<00:00:34.500> gist<00:00:34.739> of 00:00:34.850 --> 00:00:34.860 align:start position:0% being here alright so here's the gist of 00:00:34.860 --> 00:00:38.660 align:start position:0% being here alright so here's the gist of it<00:00:35.989> deployed<00:00:36.989> contract<00:00:37.500> code<00:00:37.739> is<00:00:38.100> not 00:00:38.660 --> 00:00:38.670 align:start position:0% it deployed contract code is not 00:00:38.670 --> 00:00:45.680 align:start position:0% it deployed contract code is not immutable<00:00:41.930> here's<00:00:42.930> the<00:00:43.140> link<00:00:43.380> to<00:00:44.300> the<00:00:45.300> repo 00:00:45.680 --> 00:00:45.690 align:start position:0% immutable here's the link to the repo 00:00:45.690 --> 00:00:47.240 align:start position:0% immutable here's the link to the repo that's<00:00:45.840> got<00:00:46.080> all<00:00:46.410> of<00:00:46.650> the<00:00:46.770> code<00:00:46.980> that<00:00:47.160> we're 00:00:47.240 --> 00:00:47.250 align:start position:0% that's got all of the code that we're 00:00:47.250 --> 00:00:50.450 align:start position:0% that's got all of the code that we're going<00:00:47.340> to<00:00:47.400> go<00:00:47.520> through<00:00:47.790> today<00:00:49.220> so<00:00:50.220> you<00:00:50.310> can 00:00:50.450 --> 00:00:50.460 align:start position:0% going to go through today so you can 00:00:50.460 --> 00:00:56.360 align:start position:0% going to go through today so you can kind<00:00:50.700> of<00:00:50.730> review<00:00:51.500> async<00:00:52.500> or<00:00:52.890> follow<00:00:53.220> along<00:00:55.370> so 00:00:56.360 --> 00:00:56.370 align:start position:0% kind of review async or follow along so 00:00:56.370 --> 00:00:59.000 align:start position:0% kind of review async or follow along so we<00:00:56.550> won't<00:00:56.760> get<00:00:56.880> too<00:00:57.150> bogged<00:00:58.110> down<00:00:58.320> in<00:00:58.650> like 00:00:59.000 --> 00:00:59.010 align:start position:0% we won't get too bogged down in like 00:00:59.010 --> 00:01:02.210 align:start position:0% we won't get too bogged down in like working<00:00:59.520> through<00:00:59.700> it<00:00:59.880> and<00:01:00.120> fly<00:01:00.300> it<00:01:00.330> by<00:01:00.570> mind<00:01:01.220> a 00:01:02.210 --> 00:01:02.220 align:start position:0% working through it and fly it by mind a 00:01:02.220 --> 00:01:06.410 align:start position:0% working through it and fly it by mind a lot<00:01:02.880> to<00:01:03.060> digest<00:01:03.180> but<00:01:04.970> that<00:01:05.970> this<00:01:06.150> will<00:01:06.299> have 00:01:06.410 --> 00:01:06.420 align:start position:0% lot to digest but that this will have 00:01:06.420 --> 00:01:09.740 align:start position:0% lot to digest but that this will have everything<00:01:08.090> all<00:01:09.090> right<00:01:09.210> so<00:01:09.420> here's<00:01:09.630> we're 00:01:09.740 --> 00:01:09.750 align:start position:0% everything all right so here's we're 00:01:09.750 --> 00:01:11.920 align:start position:0% everything all right so here's we're going<00:01:09.869> to<00:01:09.930> talk<00:01:10.049> about<00:01:10.200> today<00:01:10.500> first 00:01:11.920 --> 00:01:11.930 align:start position:0% going to talk about today first 00:01:11.930 --> 00:01:15.010 align:start position:0% going to talk about today first contracts<00:01:12.930> can<00:01:13.140> be<00:01:13.170> destroyed<00:01:13.830> and<00:01:14.220> then 00:01:15.010 --> 00:01:15.020 align:start position:0% contracts can be destroyed and then 00:01:15.020 --> 00:01:18.649 align:start position:0% contracts can be destroyed and then redeployed<00:01:16.640> zombie<00:01:17.640> contracts<00:01:18.300> is<00:01:18.390> another 00:01:18.649 --> 00:01:18.659 align:start position:0% redeployed zombie contracts is another 00:01:18.659 --> 00:01:22.880 align:start position:0% redeployed zombie contracts is another sort<00:01:19.230> of<00:01:19.290> term<00:01:19.680> for<00:01:19.950> this<00:01:20.780> secondly<00:01:21.890> depending 00:01:22.880 --> 00:01:22.890 align:start position:0% sort of term for this secondly depending 00:01:22.890 --> 00:01:25.070 align:start position:0% sort of term for this secondly depending on<00:01:22.980> the<00:01:23.130> way<00:01:23.310> that<00:01:23.340> you<00:01:23.610> deploy<00:01:23.850> them<00:01:24.150> these 00:01:25.070 --> 00:01:25.080 align:start position:0% on the way that you deploy them these 00:01:25.080 --> 00:01:26.390 align:start position:0% on the way that you deploy them these contracts<00:01:25.560> can<00:01:25.680> actually<00:01:25.920> be<00:01:26.010> redeployed 00:01:26.390 --> 00:01:26.400 align:start position:0% contracts can actually be redeployed 00:01:26.400 --> 00:01:30.680 align:start position:0% contracts can actually be redeployed brand<00:01:27.360> new<00:01:27.630> runtime<00:01:28.050> code<00:01:29.240> third<00:01:30.240> we're<00:01:30.570> going 00:01:30.680 --> 00:01:30.690 align:start position:0% brand new runtime code third we're going 00:01:30.690 --> 00:01:32.450 align:start position:0% brand new runtime code third we're going to<00:01:30.750> discuss<00:01:31.380> some<00:01:31.409> techniques<00:01:31.740> that<00:01:32.250> you<00:01:32.340> can 00:01:32.450 --> 00:01:32.460 align:start position:0% to discuss some techniques that you can 00:01:32.460 --> 00:01:34.880 align:start position:0% to discuss some techniques that you can use<00:01:32.520> to<00:01:33.030> protect<00:01:33.180> yourself<00:01:33.720> against<00:01:34.380> these 00:01:34.880 --> 00:01:34.890 align:start position:0% use to protect yourself against these 00:01:34.890 --> 00:01:38.240 align:start position:0% use to protect yourself against these mutable<00:01:35.370> contracts<00:01:36.170> finally<00:01:37.170> we'll<00:01:37.830> explore 00:01:38.240 --> 00:01:38.250 align:start position:0% mutable contracts finally we'll explore 00:01:38.250 --> 00:01:40.370 align:start position:0% mutable contracts finally we'll explore any<00:01:38.610> ways<00:01:38.790> that<00:01:39.060> this<00:01:39.210> is<00:01:39.360> actually<00:01:39.840> you<00:01:40.170> can 00:01:40.370 --> 00:01:40.380 align:start position:0% any ways that this is actually you can 00:01:40.380 --> 00:01:44.060 align:start position:0% any ways that this is actually you can build<00:01:40.979> cool<00:01:41.400> new<00:01:42.000> stuff<00:01:42.170> doing<00:01:43.170> this<00:01:43.440> if 00:01:44.060 --> 00:01:44.070 align:start position:0% build cool new stuff doing this if 00:01:44.070 --> 00:01:48.910 align:start position:0% build cool new stuff doing this if you're<00:01:44.400> willing<00:01:44.760> to<00:01:45.049> sort<00:01:46.049> of<00:01:46.250> Trailways 00:01:48.910 --> 00:01:48.920 align:start position:0% you're willing to sort of Trailways 00:01:48.920 --> 00:01:52.670 align:start position:0% you're willing to sort of Trailways okay<00:01:50.180> so<00:01:51.180> just<00:01:51.240> so<00:01:51.570> we're<00:01:51.750> all<00:01:51.780> on<00:01:51.960> the<00:01:52.440> same 00:01:52.670 --> 00:01:52.680 align:start position:0% okay so just so we're all on the same 00:01:52.680 --> 00:01:57.190 align:start position:0% okay so just so we're all on the same page<00:01:54.020> go<00:01:55.020> over<00:01:55.230> some<00:01:55.410> of<00:01:55.500> the<00:01:55.590> four<00:01:56.100> teens 00:01:57.190 --> 00:01:57.200 align:start position:0% page go over some of the four teens 00:01:57.200 --> 00:01:59.210 align:start position:0% page go over some of the four teens basically<00:01:58.200> understand<00:01:58.650> here 00:01:59.210 --> 00:01:59.220 align:start position:0% basically understand here 00:01:59.220 --> 00:02:03.380 align:start position:0% basically understand here first<00:01:59.820> off<00:02:00.770> contact<00:02:01.770> creation<00:02:02.520> code<00:02:02.790> is<00:02:03.240> the 00:02:03.380 --> 00:02:03.390 align:start position:0% first off contact creation code is the 00:02:03.390 --> 00:02:05.140 align:start position:0% first off contact creation code is the byte<00:02:03.570> code<00:02:03.600> that<00:02:04.080> you<00:02:04.170> feed<00:02:04.410> into<00:02:04.590> your 00:02:05.140 --> 00:02:05.150 align:start position:0% byte code that you feed into your 00:02:05.150 --> 00:02:07.910 align:start position:0% byte code that you feed into your creating<00:02:06.150> a<00:02:06.240> contract<00:02:06.690> whereas<00:02:07.170> the<00:02:07.350> runtime 00:02:07.910 --> 00:02:07.920 align:start position:0% creating a contract whereas the runtime 00:02:07.920 --> 00:02:10.130 align:start position:0% creating a contract whereas the runtime code<00:02:08.250> is<00:02:08.850> what<00:02:09.149> gets<00:02:09.360> returned<00:02:09.720> from<00:02:09.990> the 00:02:10.130 --> 00:02:10.140 align:start position:0% code is what gets returned from the 00:02:10.140 --> 00:02:14.360 align:start position:0% code is what gets returned from the creation<00:02:10.590> code<00:02:10.830> and<00:02:11.180> will<00:02:12.180> actually<00:02:13.160> run<00:02:14.160> when 00:02:14.360 --> 00:02:14.370 align:start position:0% creation code and will actually run when 00:02:14.370 --> 00:02:18.050 align:start position:0% creation code and will actually run when you<00:02:14.460> call<00:02:14.670> the<00:02:14.820> contract<00:02:15.530> secondly<00:02:16.850> we've<00:02:17.850> got 00:02:18.050 --> 00:02:18.060 align:start position:0% you call the contract secondly we've got 00:02:18.060 --> 00:02:22.010 align:start position:0% you call the contract secondly we've got contract<00:02:18.840> storage<00:02:19.650> which<00:02:20.280> is<00:02:20.640> a<00:02:21.060> storehouse 00:02:22.010 --> 00:02:22.020 align:start position:0% contract storage which is a storehouse 00:02:22.020 --> 00:02:25.430 align:start position:0% contract storage which is a storehouse load<00:02:22.670> standard<00:02:23.670> storage<00:02:24.140> but<00:02:25.140> then<00:02:25.290> you've 00:02:25.430 --> 00:02:25.440 align:start position:0% load standard storage but then you've 00:02:25.440 --> 00:02:28.610 align:start position:0% load standard storage but then you've also<00:02:25.560> got<00:02:25.740> runtime<00:02:26.400> code<00:02:26.700> from<00:02:27.450> before<00:02:27.620> which 00:02:28.610 --> 00:02:28.620 align:start position:0% also got runtime code from before which 00:02:28.620 --> 00:02:31.400 align:start position:0% also got runtime code from before which in<00:02:28.980> addition<00:02:29.130> to<00:02:29.550> running<00:02:29.670> logic<00:02:30.300> all<00:02:31.080> of<00:02:31.230> that 00:02:31.400 --> 00:02:31.410 align:start position:0% in addition to running logic all of that 00:02:31.410 --> 00:02:34.390 align:start position:0% in addition to running logic all of that is<00:02:31.890> where<00:02:32.160> you're<00:02:32.340> gonna<00:02:32.430> hold<00:02:33.170> the<00:02:34.170> actual 00:02:34.390 --> 00:02:34.400 align:start position:0% is where you're gonna hold the actual 00:02:34.400 --> 00:02:37.490 align:start position:0% is where you're gonna hold the actual like<00:02:35.450> constants<00:02:36.450> and<00:02:36.690> your<00:02:36.840> contracts<00:02:37.320> in 00:02:37.490 --> 00:02:37.500 align:start position:0% like constants and your contracts in 00:02:37.500 --> 00:02:42.320 align:start position:0% like constants and your contracts in that<00:02:37.650> matter<00:02:38.780> okay<00:02:39.780> so<00:02:39.890> the<00:02:40.890> og<00:02:41.490> original 00:02:42.320 --> 00:02:42.330 align:start position:0% that matter okay so the og original 00:02:42.330 --> 00:02:45.170 align:start position:0% that matter okay so the og original method<00:02:42.840> here<00:02:43.110> is<00:02:43.140> create<00:02:43.770> or<00:02:44.370> actually 00:02:45.170 --> 00:02:45.180 align:start position:0% method here is create or actually 00:02:45.180 --> 00:02:47.030 align:start position:0% method here is create or actually deploying<00:02:45.480> contracts<00:02:46.080> that's<00:02:46.410> what<00:02:46.620> happens 00:02:47.030 --> 00:02:47.040 align:start position:0% deploying contracts that's what happens 00:02:47.040 --> 00:02:49.970 align:start position:0% deploying contracts that's what happens when<00:02:47.190> you're<00:02:47.310> actually<00:02:48.410> deploying<00:02:49.410> at<00:02:49.740> a 00:02:49.970 --> 00:02:49.980 align:start position:0% when you're actually deploying at a 00:02:49.980 --> 00:02:52.160 align:start position:0% when you're actually deploying at a contract<00:02:50.820> via<00:02:51.030> transaction<00:02:51.870> to<00:02:51.930> the<00:02:51.959> Bill 00:02:52.160 --> 00:02:52.170 align:start position:0% contract via transaction to the Bill 00:02:52.170 --> 00:02:55.550 align:start position:0% contract via transaction to the Bill aggress<00:02:52.970> uses<00:02:53.970> the<00:02:54.360> employers<00:02:55.019> address<00:02:55.230> and 00:02:55.550 --> 00:02:55.560 align:start position:0% aggress uses the employers address and 00:02:55.560 --> 00:02:57.199 align:start position:0% aggress uses the employers address and the<00:02:55.620> nonce<00:02:55.830> to<00:02:56.100> determine<00:02:56.519> the<00:02:56.580> address<00:02:57.000> the 00:02:57.199 --> 00:02:57.209 align:start position:0% the nonce to determine the address the 00:02:57.209 --> 00:02:59.750 align:start position:0% the nonce to determine the address the new<00:02:57.300> kid<00:02:57.510> on<00:02:57.600> the<00:02:57.660> block<00:02:57.750> create<00:02:58.350> two<00:02:58.760> instead 00:02:59.750 --> 00:02:59.760 align:start position:0% new kid on the block create two instead 00:02:59.760 --> 00:03:01.550 align:start position:0% new kid on the block create two instead of<00:02:59.850> using<00:03:00.000> the<00:03:00.209> nonce<00:03:00.450> of<00:03:00.690> the<00:03:00.780> the<00:03:01.200> deployer 00:03:01.550 --> 00:03:01.560 align:start position:0% of using the nonce of the the deployer 00:03:01.560 --> 00:03:04.580 align:start position:0% of using the nonce of the the deployer it's<00:03:02.160> basing<00:03:03.030> that<00:03:03.180> address<00:03:04.050> and<00:03:04.260> poised<00:03:04.560> to 00:03:04.580 --> 00:03:04.590 align:start position:0% it's basing that address and poised to 00:03:04.590 --> 00:03:07.940 align:start position:0% it's basing that address and poised to off<00:03:04.950> of<00:03:05.130> the<00:03:05.310> deployment<00:03:05.989> address<00:03:06.989> the<00:03:07.560> salt 00:03:07.940 --> 00:03:07.950 align:start position:0% off of the deployment address the salt 00:03:07.950 --> 00:03:11.300 align:start position:0% off of the deployment address the salt and<00:03:08.510> the<00:03:09.510> initialization<00:03:09.959> contract<00:03:10.860> creation 00:03:11.300 --> 00:03:11.310 align:start position:0% and the initialization contract creation 00:03:11.310 --> 00:03:14.449 align:start position:0% and the initialization contract creation code<00:03:11.840> okay<00:03:13.040> self-destructs<00:03:14.040> I'm<00:03:14.190> sure<00:03:14.370> you 00:03:14.449 --> 00:03:14.459 align:start position:0% code okay self-destructs I'm sure you 00:03:14.459 --> 00:03:16.940 align:start position:0% code okay self-destructs I'm sure you guys<00:03:14.610> are<00:03:14.640> all<00:03:14.850> familiar<00:03:15.000> with<00:03:15.330> this<00:03:15.950> to 00:03:16.940 --> 00:03:16.950 align:start position:0% guys are all familiar with this to 00:03:16.950 --> 00:03:20.120 align:start position:0% guys are all familiar with this to actually<00:03:17.480> feature<00:03:18.480> in<00:03:18.930> my<00:03:19.170> original 00:03:20.120 --> 00:03:20.130 align:start position:0% actually feature in my original 00:03:20.130 --> 00:03:22.220 align:start position:0% actually feature in my original aetherium<00:03:20.670> foundation<00:03:21.209> hello<00:03:21.540> world<00:03:21.840> that 00:03:22.220 --> 00:03:22.230 align:start position:0% aetherium foundation hello world that 00:03:22.230 --> 00:03:24.720 align:start position:0% aetherium foundation hello world that this<00:03:22.500> was<00:03:22.709> like<00:03:23.030> seen<00:03:24.030> as<00:03:24.209> you<00:03:24.510> do 00:03:24.720 --> 00:03:24.730 align:start position:0% this was like seen as you do 00:03:24.730 --> 00:03:27.059 align:start position:0% this was like seen as you do your<00:03:25.050> civic<00:03:26.050> duty<00:03:26.080> on<00:03:26.470> the<00:03:26.560> block<00:03:26.739> chaining 00:03:27.059 --> 00:03:27.069 align:start position:0% your civic duty on the block chaining 00:03:27.069 --> 00:03:29.039 align:start position:0% your civic duty on the block chaining cleaning<00:03:27.519> up<00:03:27.610> back<00:03:27.790> to<00:03:27.940> yourself<00:03:28.120> and<00:03:28.690> then<00:03:28.930> of 00:03:29.039 --> 00:03:29.049 align:start position:0% cleaning up back to yourself and then of 00:03:29.049 --> 00:03:31.710 align:start position:0% cleaning up back to yourself and then of course<00:03:29.290> the<00:03:30.040> parody<00:03:30.459> multi-state<00:03:31.060> hack<00:03:31.299> and<00:03:31.659> a 00:03:31.710 --> 00:03:31.720 align:start position:0% course the parody multi-state hack and a 00:03:31.720 --> 00:03:33.899 align:start position:0% course the parody multi-state hack and a whole<00:03:31.989> bunch<00:03:32.019> of<00:03:32.409> very<00:03:32.739> sharp<00:03:33.099> edge<00:03:33.280> cases<00:03:33.580> of 00:03:33.899 --> 00:03:33.909 align:start position:0% whole bunch of very sharp edge cases of 00:03:33.909 --> 00:03:36.149 align:start position:0% whole bunch of very sharp edge cases of that<00:03:34.060> most<00:03:34.330> developers<00:03:34.569> -<00:03:35.140> just<00:03:35.349> saying<00:03:35.890> avoid 00:03:36.149 --> 00:03:36.159 align:start position:0% that most developers - just saying avoid 00:03:36.159 --> 00:03:39.330 align:start position:0% that most developers - just saying avoid this<00:03:36.610> like<00:03:36.819> the<00:03:36.940> plague<00:03:37.950> I'm<00:03:38.950> not<00:03:39.159> most 00:03:39.330 --> 00:03:39.340 align:start position:0% this like the plague I'm not most 00:03:39.340 --> 00:03:42.330 align:start position:0% this like the plague I'm not most developers<00:03:39.790> there<00:03:40.510> are<00:03:40.750> a<00:03:41.379> couple<00:03:41.830> of<00:03:42.010> cool 00:03:42.330 --> 00:03:42.340 align:start position:0% developers there are a couple of cool 00:03:42.340 --> 00:03:44.190 align:start position:0% developers there are a couple of cool things<00:03:42.700> you<00:03:42.790> can<00:03:42.970> do<00:03:43.120> with<00:03:43.269> it<00:03:43.450> if<00:03:43.660> you're 00:03:44.190 --> 00:03:44.200 align:start position:0% things you can do with it if you're 00:03:44.200 --> 00:03:46.039 align:start position:0% things you can do with it if you're willing<00:03:44.410> to<00:03:44.440> take<00:03:44.620> along<00:03:44.830> a<00:03:44.980> wild<00:03:45.370> side<00:03:45.549> but 00:03:46.039 --> 00:03:46.049 align:start position:0% willing to take along a wild side but 00:03:46.049 --> 00:03:48.720 align:start position:0% willing to take along a wild side but always<00:03:47.049> tread<00:03:47.530> with<00:03:47.680> caution<00:03:47.890> when<00:03:48.610> you're 00:03:48.720 --> 00:03:48.730 align:start position:0% always tread with caution when you're 00:03:48.730 --> 00:03:50.280 align:start position:0% always tread with caution when you're using<00:03:49.060> self-destructed<00:03:49.900> one<00:03:50.080> of<00:03:50.170> those 00:03:50.280 --> 00:03:50.290 align:start position:0% using self-destructed one of those 00:03:50.290 --> 00:03:54.770 align:start position:0% using self-destructed one of those things<00:03:50.560> that<00:03:50.739> self<00:03:51.459> destruct<00:03:51.940> can<00:03:52.860> enable<00:03:53.860> or 00:03:54.770 --> 00:03:54.780 align:start position:0% things that self destruct can enable or 00:03:54.780 --> 00:03:59.880 align:start position:0% things that self destruct can enable or exploit<00:03:55.780> is<00:03:56.670> reliance<00:03:57.670> so<00:03:58.349> the<00:03:59.349> gist<00:03:59.680> of<00:03:59.799> a 00:03:59.880 --> 00:03:59.890 align:start position:0% exploit is reliance so the gist of a 00:03:59.890 --> 00:04:03.990 align:start position:0% exploit is reliance so the gist of a contract<00:04:00.459> redeployment<00:04:01.769> let's<00:04:02.769> go<00:04:03.040> over<00:04:03.430> how 00:04:03.990 --> 00:04:04.000 align:start position:0% contract redeployment let's go over how 00:04:04.000 --> 00:04:06.990 align:start position:0% contract redeployment let's go over how this<00:04:04.510> sort<00:04:04.750> of<00:04:04.810> comes<00:04:05.049> down<00:04:05.319> to<00:04:05.590> be<00:04:05.799> if<00:04:06.519> I<00:04:06.670> try 00:04:06.990 --> 00:04:07.000 align:start position:0% this sort of comes down to be if I try 00:04:07.000 --> 00:04:09.030 align:start position:0% this sort of comes down to be if I try an<00:04:07.180> employee<00:04:07.629> to<00:04:08.319> an<00:04:08.410> accountant<00:04:08.890> that's 00:04:09.030 --> 00:04:09.040 align:start position:0% an employee to an accountant that's 00:04:09.040 --> 00:04:10.349 align:start position:0% an employee to an accountant that's already<00:04:09.250> got<00:04:09.459> a<00:04:09.519> contract<00:04:10.030> this<00:04:10.150> is<00:04:10.209> a 00:04:10.349 --> 00:04:10.359 align:start position:0% already got a contract this is a 00:04:10.359 --> 00:04:12.119 align:start position:0% already got a contract this is a scenario<00:04:10.690> that<00:04:10.900> in<00:04:11.140> a<00:04:11.170> creative<00:04:11.590> only<00:04:11.890> world 00:04:12.119 --> 00:04:12.129 align:start position:0% scenario that in a creative only world 00:04:12.129 --> 00:04:14.190 align:start position:0% scenario that in a creative only world isn't<00:04:12.489> going<00:04:12.609> to<00:04:12.670> happen<00:04:12.819> without<00:04:13.510> a<00:04:13.750> hash 00:04:14.190 --> 00:04:14.200 align:start position:0% isn't going to happen without a hash 00:04:14.200 --> 00:04:16.800 align:start position:0% isn't going to happen without a hash collision<00:04:14.769> because<00:04:15.190> the<00:04:15.970> non-singer<00:04:16.570> minute 00:04:16.800 --> 00:04:16.810 align:start position:0% collision because the non-singer minute 00:04:16.810 --> 00:04:20.789 align:start position:0% collision because the non-singer minute every<00:04:17.019> time<00:04:17.260> but<00:04:17.859> pretty<00:04:18.699> to<00:04:18.850> world<00:04:19.650> if<00:04:20.650> you 00:04:20.789 --> 00:04:20.799 align:start position:0% every time but pretty to world if you 00:04:20.799 --> 00:04:23.550 align:start position:0% every time but pretty to world if you try<00:04:21.039> to<00:04:21.570> feed<00:04:22.570> in<00:04:22.720> those<00:04:22.930> exact<00:04:23.260> same 00:04:23.550 --> 00:04:23.560 align:start position:0% try to feed in those exact same 00:04:23.560 --> 00:04:26.070 align:start position:0% try to feed in those exact same arguments<00:04:24.460> it's<00:04:24.940> just<00:04:25.180> gonna<00:04:25.300> fail<00:04:25.600> right 00:04:26.070 --> 00:04:26.080 align:start position:0% arguments it's just gonna fail right 00:04:26.080 --> 00:04:28.320 align:start position:0% arguments it's just gonna fail right there's<00:04:27.070> already<00:04:27.250> a<00:04:27.400> contract<00:04:27.910> there<00:04:28.120> whether 00:04:28.320 --> 00:04:28.330 align:start position:0% there's already a contract there whether 00:04:28.330 --> 00:04:31.770 align:start position:0% there's already a contract there whether or<00:04:28.479> not<00:04:28.570> there's<00:04:28.780> code<00:04:29.080> this<00:04:29.889> is<00:04:30.010> invalid<00:04:30.780> but 00:04:31.770 --> 00:04:31.780 align:start position:0% or not there's code this is invalid but 00:04:31.780 --> 00:04:34.260 align:start position:0% or not there's code this is invalid but when<00:04:31.960> you<00:04:32.050> self-destruct<00:04:32.560> a<00:04:33.010> contract<00:04:33.490> what's 00:04:34.260 --> 00:04:34.270 align:start position:0% when you self-destruct a contract what's 00:04:34.270 --> 00:04:35.580 align:start position:0% when you self-destruct a contract what's actually<00:04:34.479> happening<00:04:34.960> it's<00:04:35.139> more<00:04:35.380> than<00:04:35.530> the 00:04:35.580 --> 00:04:35.590 align:start position:0% actually happening it's more than the 00:04:35.590 --> 00:04:38.190 align:start position:0% actually happening it's more than the runtime<00:04:36.190> code<00:04:36.430> getting<00:04:36.729> in<00:04:36.789> there<00:04:36.940> now<00:04:37.200> the 00:04:38.190 --> 00:04:38.200 align:start position:0% runtime code getting in there now the 00:04:38.200 --> 00:04:40.589 align:start position:0% runtime code getting in there now the entire<00:04:38.560> thing<00:04:38.860> is<00:04:38.979> white<00:04:39.280> you've<00:04:39.970> got<00:04:40.180> no<00:04:40.360> nuts 00:04:40.589 --> 00:04:40.599 align:start position:0% entire thing is white you've got no nuts 00:04:40.599 --> 00:04:43.740 align:start position:0% entire thing is white you've got no nuts no<00:04:41.020> residual<00:04:41.950> balance<00:04:42.400> no<00:04:43.300> it<00:04:43.419> stinks 00:04:43.740 --> 00:04:43.750 align:start position:0% no residual balance no it stinks 00:04:43.750 --> 00:04:45.900 align:start position:0% no residual balance no it stinks everything<00:04:44.500> is<00:04:44.590> going<00:04:44.889> as<00:04:45.460> far<00:04:45.669> as<00:04:45.789> the 00:04:45.900 --> 00:04:45.910 align:start position:0% everything is going as far as the 00:04:45.910 --> 00:04:47.520 align:start position:0% everything is going as far as the blockchain<00:04:46.360> is<00:04:46.389> concerning<00:04:46.840> this<00:04:47.020> contract 00:04:47.520 --> 00:04:47.530 align:start position:0% blockchain is concerning this contract 00:04:47.530 --> 00:04:50.279 align:start position:0% blockchain is concerning this contract it's<00:04:47.680> never<00:04:47.919> intestine<00:04:48.690> so<00:04:49.690> then<00:04:49.870> once<00:04:50.110> it's 00:04:50.279 --> 00:04:50.289 align:start position:0% it's never intestine so then once it's 00:04:50.289 --> 00:04:52.140 align:start position:0% it's never intestine so then once it's already<00:04:50.680> been<00:04:50.800> wiped<00:04:51.099> what<00:04:51.550> happens<00:04:51.910> when<00:04:52.120> I 00:04:52.140 --> 00:04:52.150 align:start position:0% already been wiped what happens when I 00:04:52.150 --> 00:04:54.629 align:start position:0% already been wiped what happens when I haven't<00:04:52.450> went<00:04:52.660> to<00:04:52.870> me<00:04:52.990> again<00:04:53.380> well<00:04:54.250> in<00:04:54.490> that 00:04:54.629 --> 00:04:54.639 align:start position:0% haven't went to me again well in that 00:04:54.639 --> 00:04:58.200 align:start position:0% haven't went to me again well in that case<00:04:54.700> refine<00:04:55.889> the<00:04:56.889> contract<00:04:57.580> can<00:04:57.729> be<00:04:57.789> deployed 00:04:58.200 --> 00:04:58.210 align:start position:0% case refine the contract can be deployed 00:04:58.210 --> 00:05:01.800 align:start position:0% case refine the contract can be deployed no<00:04:58.360> problem<00:04:58.810> but<00:04:59.770> if<00:04:59.800> I<00:05:00.099> was<00:05:00.389> relying<00:05:01.389> on<00:05:01.630> this 00:05:01.800 --> 00:05:01.810 align:start position:0% no problem but if I was relying on this 00:05:01.810 --> 00:05:04.890 align:start position:0% no problem but if I was relying on this estate<00:05:02.020> or<00:05:02.470> the<00:05:02.710> dogs<00:05:02.919> of<00:05:03.250> whatever<00:05:03.900> property 00:05:04.890 --> 00:05:04.900 align:start position:0% estate or the dogs of whatever property 00:05:04.900 --> 00:05:09.360 align:start position:0% estate or the dogs of whatever property you<00:05:04.990> know<00:05:05.110> that<00:05:05.349> contract<00:05:06.030> before<00:05:07.800> this<00:05:08.800> you 00:05:09.360 --> 00:05:09.370 align:start position:0% you know that contract before this you 00:05:09.370 --> 00:05:12.000 align:start position:0% you know that contract before this you got<00:05:09.520> white<00:05:09.789> and<00:05:09.820> then<00:05:10.450> look<00:05:10.690> back<00:05:10.900> well<00:05:11.860> now 00:05:12.000 --> 00:05:12.010 align:start position:0% got white and then look back well now 00:05:12.010 --> 00:05:14.730 align:start position:0% got white and then look back well now you're<00:05:12.490> in<00:05:12.520> trouble<00:05:12.789> right<00:05:13.139> so<00:05:14.139> let's<00:05:14.410> look<00:05:14.620> at 00:05:14.730 --> 00:05:14.740 align:start position:0% you're in trouble right so let's look at 00:05:14.740 --> 00:05:17.780 align:start position:0% you're in trouble right so let's look at an<00:05:14.830> example<00:05:14.919> of<00:05:15.400> how<00:05:15.970> this<00:05:16.150> might<00:05:16.210> work 00:05:17.780 --> 00:05:17.790 align:start position:0% an example of how this might work 00:05:17.790 --> 00:05:21.200 align:start position:0% an example of how this might work and<00:05:18.440> bear<00:05:19.440> in<00:05:19.560> mind<00:05:19.590> that<00:05:20.070> the<00:05:20.580> code<00:05:20.880> won't 00:05:21.200 --> 00:05:21.210 align:start position:0% and bear in mind that the code won't 00:05:21.210 --> 00:05:23.420 align:start position:0% and bear in mind that the code won't actually<00:05:21.390> even<00:05:21.990> be<00:05:22.110> changing<00:05:22.650> this<00:05:22.890> is<00:05:23.070> just 00:05:23.420 --> 00:05:23.430 align:start position:0% actually even be changing this is just 00:05:23.430 --> 00:05:27.530 align:start position:0% actually even be changing this is just an<00:05:23.580> example<00:05:24.860> greatly<00:05:25.860> simplified<00:05:26.460> like<00:05:27.180> a 00:05:27.530 --> 00:05:27.540 align:start position:0% an example greatly simplified like a 00:05:27.540 --> 00:05:30.470 align:start position:0% an example greatly simplified like a more<00:05:27.960> realistic<00:05:28.290> world<00:05:29.070> use<00:05:30.060> case<00:05:30.270> would<00:05:30.450> be 00:05:30.470 --> 00:05:30.480 align:start position:0% more realistic world use case would be 00:05:30.480 --> 00:05:32.690 align:start position:0% more realistic world use case would be like<00:05:30.660> this<00:05:30.810> add<00:05:31.170> X<00:05:31.440> or<00:05:31.710> a<00:05:31.740> swap<00:05:32.100> contract<00:05:32.130> or 00:05:32.690 --> 00:05:32.700 align:start position:0% like this add X or a swap contract or 00:05:32.700 --> 00:05:33.830 align:start position:0% like this add X or a swap contract or something<00:05:32.910> like<00:05:32.970> that<00:05:33.060> but<00:05:33.600> this<00:05:33.660> is<00:05:33.780> a 00:05:33.830 --> 00:05:33.840 align:start position:0% something like that but this is a 00:05:33.840 --> 00:05:36.800 align:start position:0% something like that but this is a contract<00:05:34.230> that<00:05:34.380> we<00:05:35.040> approve<00:05:35.760> to<00:05:36.090> transfer<00:05:36.570> our 00:05:36.800 --> 00:05:36.810 align:start position:0% contract that we approve to transfer our 00:05:36.810 --> 00:05:40.220 align:start position:0% contract that we approve to transfer our ship<00:05:37.080> coins<00:05:37.380> okay<00:05:38.070> and<00:05:38.840> initially<00:05:39.840> it's<00:05:39.960> in 00:05:40.220 --> 00:05:40.230 align:start position:0% ship coins okay and initially it's in 00:05:40.230 --> 00:05:42.770 align:start position:0% ship coins okay and initially it's in testing<00:05:40.740> mode<00:05:40.790> so<00:05:41.790> don't<00:05:42.030> approve<00:05:42.330> and<00:05:42.570> it's<00:05:42.690> a 00:05:42.770 --> 00:05:42.780 align:start position:0% testing mode so don't approve and it's a 00:05:42.780 --> 00:05:45.050 align:start position:0% testing mode so don't approve and it's a testing<00:05:43.170> mode<00:05:43.350> because<00:05:43.740> anyone<00:05:44.730> can<00:05:44.910> move 00:05:45.050 --> 00:05:45.060 align:start position:0% testing mode because anyone can move 00:05:45.060 --> 00:05:46.580 align:start position:0% testing mode because anyone can move your<00:05:45.270> your<00:05:45.600> funds<00:05:45.780> around<00:05:45.930> but<00:05:46.230> then<00:05:46.320> we<00:05:46.410> turn 00:05:46.580 --> 00:05:46.590 align:start position:0% your your funds around but then we turn 00:05:46.590 --> 00:05:50.840 align:start position:0% your your funds around but then we turn the<00:05:46.740> testing<00:05:47.100> mode<00:05:47.250> off<00:05:47.690> but<00:05:48.980> then<00:05:49.980> the 00:05:50.840 --> 00:05:50.850 align:start position:0% the testing mode off but then the 00:05:50.850 --> 00:05:53.270 align:start position:0% the testing mode off but then the contract<00:05:51.660> can<00:05:51.810> be<00:05:51.840> destroyed<00:05:52.260> retired<00:05:52.860> and 00:05:53.270 --> 00:05:53.280 align:start position:0% contract can be destroyed retired and 00:05:53.280 --> 00:05:56.000 align:start position:0% contract can be destroyed retired and once<00:05:54.270> you<00:05:54.450> reapply<00:05:54.870> it<00:05:55.110> it's<00:05:55.290> back<00:05:55.440> in<00:05:55.650> testing 00:05:56.000 --> 00:05:56.010 align:start position:0% once you reapply it it's back in testing 00:05:56.010 --> 00:05:59.060 align:start position:0% once you reapply it it's back in testing mode<00:05:56.160> and<00:05:56.370> into<00:05:56.880> the<00:05:56.970> fund<00:05:57.180> stolen<00:05:57.570> okay<00:05:58.200> so 00:05:59.060 --> 00:05:59.070 align:start position:0% mode and into the fund stolen okay so 00:05:59.070 --> 00:06:03.620 align:start position:0% mode and into the fund stolen okay so this<00:06:00.030> is<00:06:00.210> a<00:06:00.240> problem<00:06:00.810> and<00:06:02.120> really<00:06:03.120> low<00:06:03.390> hanging 00:06:03.620 --> 00:06:03.630 align:start position:0% this is a problem and really low hanging 00:06:03.630 --> 00:06:06.380 align:start position:0% this is a problem and really low hanging fruit<00:06:04.020> if<00:06:04.320> my<00:06:04.710> series<00:06:05.070> be<00:06:05.220> careful<00:06:05.640> with<00:06:06.180> your 00:06:06.380 --> 00:06:06.390 align:start position:0% fruit if my series be careful with your 00:06:06.390 --> 00:06:08.870 align:start position:0% fruit if my series be careful with your giving<00:06:06.840> me<00:06:07.160> approvals<00:06:08.160> out<00:06:08.310> you<00:06:08.520> guys<00:06:08.610> already 00:06:08.870 --> 00:06:08.880 align:start position:0% giving me approvals out you guys already 00:06:08.880 --> 00:06:11.390 align:start position:0% giving me approvals out you guys already know<00:06:09.090> that<00:06:09.120> but<00:06:09.990> let's<00:06:10.170> look<00:06:10.380> at<00:06:10.560> that<00:06:10.830> so 00:06:11.390 --> 00:06:11.400 align:start position:0% know that but let's look at that so 00:06:11.400 --> 00:06:14.240 align:start position:0% know that but let's look at that so remediation<00:06:12.150> to<00:06:12.390> this<00:06:12.620> which<00:06:13.620> here's<00:06:14.100> our 00:06:14.240 --> 00:06:14.250 align:start position:0% remediation to this which here's our 00:06:14.250 --> 00:06:18.560 align:start position:0% remediation to this which here's our same<00:06:14.940> coin<00:06:15.860> mover<00:06:16.860> contract<00:06:17.520> and<00:06:17.850> we've 00:06:18.560 --> 00:06:18.570 align:start position:0% same coin mover contract and we've 00:06:18.570 --> 00:06:20.900 align:start position:0% same coin mover contract and we've stripped<00:06:18.780> out<00:06:18.960> the<00:06:19.110> testing<00:06:19.470> mode<00:06:19.620> so<00:06:20.010> you're 00:06:20.900 --> 00:06:20.910 align:start position:0% stripped out the testing mode so you're 00:06:20.910 --> 00:06:23.330 align:start position:0% stripped out the testing mode so you're good<00:06:21.120> you<00:06:21.450> can<00:06:21.560> approve<00:06:22.560> this<00:06:22.800> contract 00:06:23.330 --> 00:06:23.340 align:start position:0% good you can approve this contract 00:06:23.340 --> 00:06:25.520 align:start position:0% good you can approve this contract you're<00:06:23.940> gonna<00:06:24.060> be<00:06:24.180> the<00:06:24.270> only<00:06:24.390> one<00:06:24.630> that's<00:06:25.260> able 00:06:25.520 --> 00:06:25.530 align:start position:0% you're gonna be the only one that's able 00:06:25.530 --> 00:06:28.580 align:start position:0% you're gonna be the only one that's able to<00:06:26.130> call<00:06:26.400> the<00:06:26.520> transfer<00:06:26.910> from<00:06:27.060> that<00:06:27.330> bit<00:06:27.590> we're 00:06:28.580 --> 00:06:28.590 align:start position:0% to call the transfer from that bit we're 00:06:28.590 --> 00:06:31.480 align:start position:0% to call the transfer from that bit we're all<00:06:28.740> set<00:06:29.100> we've<00:06:29.820> fixed<00:06:30.450> this<00:06:30.690> problem 00:06:31.480 --> 00:06:31.490 align:start position:0% all set we've fixed this problem 00:06:31.490 --> 00:06:35.630 align:start position:0% all set we've fixed this problem everyone<00:06:32.490> you<00:06:32.670> can<00:06:32.880> rest<00:06:33.090> easy<00:06:34.550> except<00:06:35.550> you 00:06:35.630 --> 00:06:35.640 align:start position:0% everyone you can rest easy except you 00:06:35.640 --> 00:06:38.860 align:start position:0% everyone you can rest easy except you can't<00:06:35.880> because<00:06:36.480> if<00:06:36.810> it<00:06:37.290> was<00:06:37.440> deployed<00:06:37.860> via 00:06:38.860 --> 00:06:38.870 align:start position:0% can't because if it was deployed via 00:06:38.870 --> 00:06:41.870 align:start position:0% can't because if it was deployed via some<00:06:39.870> of<00:06:39.960> these<00:06:40.020> tricky<00:06:40.380> methods<00:06:40.770> then<00:06:41.700> you're 00:06:41.870 --> 00:06:41.880 align:start position:0% some of these tricky methods then you're 00:06:41.880 --> 00:06:43.430 align:start position:0% some of these tricky methods then you're you're<00:06:42.270> backing<00:06:42.600> the<00:06:42.690> same<00:06:42.870> problem<00:06:43.260> where 00:06:43.430 --> 00:06:43.440 align:start position:0% you're backing the same problem where 00:06:43.440 --> 00:06:46.790 align:start position:0% you're backing the same problem where they<00:06:43.980> could<00:06:44.190> deploy<00:06:44.460> a<00:06:44.700> contract<00:06:45.270> vendors<00:06:45.800> can 00:06:46.790 --> 00:06:46.800 align:start position:0% they could deploy a contract vendors can 00:06:46.800 --> 00:06:49.220 align:start position:0% they could deploy a contract vendors can move<00:06:46.920> your<00:06:47.040> funds<00:06:47.280> again<00:06:47.550> and<00:06:47.760> the<00:06:48.300> phenomenon 00:06:49.220 --> 00:06:49.230 align:start position:0% move your funds again and the phenomenon 00:06:49.230 --> 00:06:52.670 align:start position:0% move your funds again and the phenomenon here<00:06:49.560> is<00:06:49.680> it<00:06:49.830> the<00:06:50.220> phrasing<00:06:51.180> I<00:06:51.500> started<00:06:52.500> using 00:06:52.670 --> 00:06:52.680 align:start position:0% here is it the phrasing I started using 00:06:52.680 --> 00:06:55.220 align:start position:0% here is it the phrasing I started using for<00:06:53.010> this<00:06:53.160> particular<00:06:53.640> type<00:06:54.360> of<00:06:54.390> redeployment 00:06:55.220 --> 00:06:55.230 align:start position:0% for this particular type of redeployment 00:06:55.230 --> 00:06:57.020 align:start position:0% for this particular type of redeployment where<00:06:55.800> you've<00:06:55.890> got<00:06:56.010> brand<00:06:56.250> new<00:06:56.340> code<00:06:56.670> coming 00:06:57.020 --> 00:06:57.030 align:start position:0% where you've got brand new code coming 00:06:57.030 --> 00:07:00.200 align:start position:0% where you've got brand new code coming in<00:06:57.150> it<00:06:57.270> is<00:06:57.450> metamorphism<00:06:58.940> there's<00:06:59.940> enough 00:07:00.200 --> 00:07:00.210 align:start position:0% in it is metamorphism there's enough 00:07:00.210 --> 00:07:02.300 align:start position:0% in it is metamorphism there's enough this<00:07:00.390> also<00:07:00.630> goes<00:07:01.320> by<00:07:01.530> like<00:07:01.680> malleable 00:07:02.300 --> 00:07:02.310 align:start position:0% this also goes by like malleable 00:07:02.310 --> 00:07:04.340 align:start position:0% this also goes by like malleable contracts<00:07:03.240> this<00:07:03.450> there's<00:07:03.840> a<00:07:03.900> few<00:07:04.080> different 00:07:04.340 --> 00:07:04.350 align:start position:0% contracts this there's a few different 00:07:04.350 --> 00:07:07.940 align:start position:0% contracts this there's a few different ways<00:07:04.380> of<00:07:04.680> describing<00:07:05.160> this<00:07:05.490> a<00:07:06.950> metamorphic 00:07:07.940 --> 00:07:07.950 align:start position:0% ways of describing this a metamorphic 00:07:07.950 --> 00:07:10.540 align:start position:0% ways of describing this a metamorphic contract<00:07:08.460> is<00:07:08.760> one<00:07:09.180> that<00:07:09.540> has 00:07:10.540 --> 00:07:10.550 align:start position:0% contract is one that has 00:07:10.550 --> 00:07:13.220 align:start position:0% contract is one that has non-deterministic<00:07:11.550> creation<00:07:12.300> code<00:07:12.540> so<00:07:13.200> you 00:07:13.220 --> 00:07:13.230 align:start position:0% non-deterministic creation code so you 00:07:13.230 --> 00:07:14.589 align:start position:0% non-deterministic creation code so you feed<00:07:13.590> it<00:07:13.740> the<00:07:13.860> same 00:07:14.589 --> 00:07:14.599 align:start position:0% feed it the same 00:07:14.599 --> 00:07:15.909 align:start position:0% feed it the same Dick's<00:07:14.779> creation<00:07:15.409> code<00:07:15.679> that<00:07:15.830> you're 00:07:15.909 --> 00:07:15.919 align:start position:0% Dick's creation code that you're 00:07:15.919 --> 00:07:19.629 align:start position:0% Dick's creation code that you're sourcing<00:07:16.550> but<00:07:17.919> how<00:07:18.919> you're<00:07:19.099> going<00:07:19.219> to<00:07:19.339> derive 00:07:19.629 --> 00:07:19.639 align:start position:0% sourcing but how you're going to derive 00:07:19.639 --> 00:07:21.669 align:start position:0% sourcing but how you're going to derive the<00:07:19.969> runtime<00:07:20.419> code<00:07:20.719> from<00:07:20.990> something<00:07:21.439> other 00:07:21.669 --> 00:07:21.679 align:start position:0% the runtime code from something other 00:07:21.679 --> 00:07:25.029 align:start position:0% the runtime code from something other than<00:07:22.069> that<00:07:22.729> creation<00:07:23.419> code<00:07:23.629> payload<00:07:24.199> so 00:07:25.029 --> 00:07:25.039 align:start position:0% than that creation code payload so 00:07:25.039 --> 00:07:27.579 align:start position:0% than that creation code payload so here's<00:07:25.249> the<00:07:25.459> basic<00:07:25.669> rules<00:07:26.270> of<00:07:26.479> how<00:07:26.899> this 00:07:27.579 --> 00:07:27.589 align:start position:0% here's the basic rules of how this 00:07:27.589 --> 00:07:30.519 align:start position:0% here's the basic rules of how this happens<00:07:28.099> first<00:07:28.520> off<00:07:28.789> you<00:07:29.419> have<00:07:29.449> to<00:07:29.929> destroy 00:07:30.519 --> 00:07:30.529 align:start position:0% happens first off you have to destroy 00:07:30.529 --> 00:07:32.379 align:start position:0% happens first off you have to destroy the<00:07:30.559> existing<00:07:31.039> contract<00:07:31.610> you<00:07:31.879> have<00:07:32.059> to<00:07:32.209> call 00:07:32.379 --> 00:07:32.389 align:start position:0% the existing contract you have to call 00:07:32.389 --> 00:07:36.100 align:start position:0% the existing contract you have to call self-destruct<00:07:33.080> on<00:07:33.819> second<00:07:34.819> you<00:07:35.629> have<00:07:35.839> to<00:07:35.990> use 00:07:36.100 --> 00:07:36.110 align:start position:0% self-destruct on second you have to use 00:07:36.110 --> 00:07:38.439 align:start position:0% self-destruct on second you have to use create<00:07:36.529> -<00:07:36.800> and<00:07:37.069> the<00:07:37.580> interesting<00:07:38.270> thing<00:07:38.389> about 00:07:38.439 --> 00:07:38.449 align:start position:0% create - and the interesting thing about 00:07:38.449 --> 00:07:40.089 align:start position:0% create - and the interesting thing about this<00:07:38.719> is<00:07:38.899> it<00:07:39.050> doesn't<00:07:39.229> have<00:07:39.379> to<00:07:39.619> be<00:07:39.740> deployed 00:07:40.089 --> 00:07:40.099 align:start position:0% this is it doesn't have to be deployed 00:07:40.099 --> 00:07:43.409 align:start position:0% this is it doesn't have to be deployed directly<00:07:40.550> from<00:07:40.879> creating<00:07:41.389> -<00:07:41.569> because<00:07:42.559> and 00:07:43.409 --> 00:07:43.419 align:start position:0% directly from creating - because and 00:07:43.419 --> 00:07:46.510 align:start position:0% directly from creating - because and anywhere<00:07:44.419> along<00:07:44.659> the<00:07:44.869> chain<00:07:45.139> some<00:07:45.860> contract 00:07:46.510 --> 00:07:46.520 align:start position:0% anywhere along the chain some contract 00:07:46.520 --> 00:07:48.929 align:start position:0% anywhere along the chain some contract uses<00:07:47.509> created<00:07:47.869> -<00:07:48.020> and<00:07:48.050> then<00:07:48.289> all<00:07:48.529> those 00:07:48.929 --> 00:07:48.939 align:start position:0% uses created - and then all those 00:07:48.939 --> 00:07:51.100 align:start position:0% uses created - and then all those intermediate<00:07:49.939> contracts<00:07:50.419> get<00:07:50.569> destroyed 00:07:51.100 --> 00:07:51.110 align:start position:0% intermediate contracts get destroyed 00:07:51.110 --> 00:07:53.760 align:start position:0% intermediate contracts get destroyed that<00:07:51.680> you<00:07:51.860> can<00:07:52.039> redeploy<00:07:52.339> all<00:07:52.639> the<00:07:52.789> way<00:07:52.909> up 00:07:53.760 --> 00:07:53.770 align:start position:0% that you can redeploy all the way up 00:07:53.770 --> 00:07:56.469 align:start position:0% that you can redeploy all the way up third<00:07:54.800> the<00:07:55.430> deployment<00:07:55.699> address<00:07:56.240> the 00:07:56.469 --> 00:07:56.479 align:start position:0% third the deployment address the 00:07:56.479 --> 00:07:58.809 align:start position:0% third the deployment address the creation<00:07:56.959> code<00:07:57.199> and<00:07:57.619> the<00:07:57.830> salt<00:07:58.099> can't<00:07:58.520> change 00:07:58.809 --> 00:07:58.819 align:start position:0% creation code and the salt can't change 00:07:58.819 --> 00:07:59.889 align:start position:0% creation code and the salt can't change because<00:07:59.180> otherwise<00:07:59.389> you're<00:07:59.599> going<00:07:59.629> to<00:07:59.749> have<00:07:59.809> a 00:07:59.889 --> 00:07:59.899 align:start position:0% because otherwise you're going to have a 00:07:59.899 --> 00:08:03.070 align:start position:0% because otherwise you're going to have a new<00:08:00.110> address<00:08:00.319> and<00:08:01.189> lastly<00:08:01.580> once<00:08:02.509> those<00:08:02.719> three 00:08:03.070 --> 00:08:03.080 align:start position:0% new address and lastly once those three 00:08:03.080 --> 00:08:06.699 align:start position:0% new address and lastly once those three rules<00:08:03.319> are<00:08:03.589> are<00:08:04.689> adhered<00:08:05.689> to<00:08:05.749> anything<00:08:06.499> is 00:08:06.699 --> 00:08:06.709 align:start position:0% rules are are adhered to anything is 00:08:06.709 --> 00:08:09.579 align:start position:0% rules are are adhered to anything is fair<00:08:07.039> game<00:08:07.099> and<00:08:07.610> is<00:08:07.729> good<00:08:07.939> so<00:08:08.809> let's<00:08:09.439> talk 00:08:09.579 --> 00:08:09.589 align:start position:0% fair game and is good so let's talk 00:08:09.589 --> 00:08:11.980 align:start position:0% fair game and is good so let's talk about<00:08:09.649> some<00:08:10.039> of<00:08:10.069> the<00:08:10.369> main<00:08:11.269> ways<00:08:11.569> that<00:08:11.869> this 00:08:11.980 --> 00:08:11.990 align:start position:0% about some of the main ways that this 00:08:11.990 --> 00:08:15.070 align:start position:0% about some of the main ways that this would<00:08:12.229> work<00:08:12.379> first<00:08:13.159> off<00:08:13.399> a<00:08:14.080> straightforward 00:08:15.070 --> 00:08:15.080 align:start position:0% would work first off a straightforward 00:08:15.080 --> 00:08:16.899 align:start position:0% would work first off a straightforward way<00:08:15.139> to<00:08:15.169> do<00:08:15.439> this<00:08:15.589> is<00:08:15.769> to<00:08:15.919> go<00:08:16.039> slow<00:08:16.279> man<00:08:16.610> under 00:08:16.899 --> 00:08:16.909 align:start position:0% way to do this is to go slow man under 00:08:16.909 --> 00:08:20.230 align:start position:0% way to do this is to go slow man under contract<00:08:17.389> so<00:08:18.459> what<00:08:19.459> I<00:08:19.490> could<00:08:19.729> do<00:08:19.879> is<00:08:20.059> I<00:08:20.180> can 00:08:20.230 --> 00:08:20.240 align:start position:0% contract so what I could do is I can 00:08:20.240 --> 00:08:22.509 align:start position:0% contract so what I could do is I can store<00:08:20.839> the<00:08:21.110> address<00:08:21.259> that<00:08:21.830> I<00:08:21.949> want<00:08:22.159> to<00:08:22.249> clone 00:08:22.509 --> 00:08:22.519 align:start position:0% store the address that I want to clone 00:08:22.519 --> 00:08:26.859 align:start position:0% store the address that I want to clone in<00:08:22.909> contract<00:08:23.719> storage<00:08:24.110> and<00:08:24.409> then<00:08:24.949> my<00:08:25.869> creation 00:08:26.859 --> 00:08:26.869 align:start position:0% in contract storage and then my creation 00:08:26.869 --> 00:08:29.170 align:start position:0% in contract storage and then my creation code<00:08:27.080> is<00:08:27.529> going<00:08:27.709> to<00:08:27.769> go<00:08:27.889> get<00:08:28.249> that<00:08:28.399> address<00:08:28.909> and 00:08:29.170 --> 00:08:29.180 align:start position:0% code is going to go get that address and 00:08:29.180 --> 00:08:31.659 align:start position:0% code is going to go get that address and clone<00:08:30.050> the<00:08:30.079> contract<00:08:30.709> now<00:08:31.039> this<00:08:31.219> has<00:08:31.369> some 00:08:31.659 --> 00:08:31.669 align:start position:0% clone the contract now this has some 00:08:31.669 --> 00:08:33.490 align:start position:0% clone the contract now this has some limitations<00:08:32.269> you<00:08:32.389> can't<00:08:32.630> use<00:08:32.810> a<00:08:32.839> constructor 00:08:33.490 --> 00:08:33.500 align:start position:0% limitations you can't use a constructor 00:08:33.500 --> 00:08:36.550 align:start position:0% limitations you can't use a constructor sort<00:08:33.949> of<00:08:34.039> like<00:08:34.219> with<00:08:34.959> common<00:08:35.959> upgradability 00:08:36.550 --> 00:08:36.560 align:start position:0% sort of like with common upgradability 00:08:36.560 --> 00:08:37.870 align:start position:0% sort of like with common upgradability patterns<00:08:36.979> you<00:08:37.069> have<00:08:37.099> to<00:08:37.339> call<00:08:37.579> into<00:08:37.729> an 00:08:37.870 --> 00:08:37.880 align:start position:0% patterns you have to call into an 00:08:37.880 --> 00:08:40.779 align:start position:0% patterns you have to call into an initializer<00:08:39.009> another<00:08:40.009> way<00:08:40.159> to<00:08:40.219> do<00:08:40.459> it<00:08:40.610> is 00:08:40.779 --> 00:08:40.789 align:start position:0% initializer another way to do it is 00:08:40.789 --> 00:08:43.089 align:start position:0% initializer another way to do it is using<00:08:41.240> what<00:08:41.360> I<00:08:41.389> call<00:08:41.449> a<00:08:41.659> transient<00:08:42.380> deploy<00:08:42.769> and 00:08:43.089 --> 00:08:43.099 align:start position:0% using what I call a transient deploy and 00:08:43.099 --> 00:08:45.699 align:start position:0% using what I call a transient deploy and the<00:08:43.849> transit<00:08:44.269> deployer<00:08:44.569> is<00:08:45.199> going<00:08:45.500> to<00:08:45.560> use 00:08:45.699 --> 00:08:45.709 align:start position:0% the transit deployer is going to use 00:08:45.709 --> 00:08:46.900 align:start position:0% the transit deployer is going to use this<00:08:45.889> trick<00:08:46.130> where<00:08:46.339> it's<00:08:46.490> going<00:08:46.639> to<00:08:46.699> rather 00:08:46.900 --> 00:08:46.910 align:start position:0% this trick where it's going to rather 00:08:46.910 --> 00:08:48.280 align:start position:0% this trick where it's going to rather than<00:08:47.029> getting<00:08:47.269> if<00:08:47.389> an<00:08:47.540> address<00:08:47.720> it's<00:08:48.019> gonna<00:08:48.110> go 00:08:48.280 --> 00:08:48.290 align:start position:0% than getting if an address it's gonna go 00:08:48.290 --> 00:08:50.019 align:start position:0% than getting if an address it's gonna go get<00:08:48.500> the<00:08:48.649> actual<00:08:48.800> creation<00:08:49.430> code<00:08:49.610> that<00:08:49.790> wants 00:08:50.019 --> 00:08:50.029 align:start position:0% get the actual creation code that wants 00:08:50.029 --> 00:08:52.059 align:start position:0% get the actual creation code that wants to<00:08:50.060> deploy<00:08:50.420> that<00:08:50.990> it's<00:08:51.170> gonna<00:08:51.319> deploy<00:08:51.709> its<00:08:51.920> own 00:08:52.059 --> 00:08:52.069 align:start position:0% to deploy that it's gonna deploy its own 00:08:52.069 --> 00:08:56.139 align:start position:0% to deploy that it's gonna deploy its own contract<00:08:52.730> via<00:08:52.970> create<00:08:53.680> using<00:08:54.680> that<00:08:55.149> creation 00:08:56.139 --> 00:08:56.149 align:start position:0% contract via create using that creation 00:08:56.149 --> 00:08:57.699 align:start position:0% contract via create using that creation code<00:08:56.329> and<00:08:56.569> create<00:08:56.930> doesn't<00:08:57.350> have<00:08:57.439> the<00:08:57.560> same 00:08:57.699 --> 00:08:57.709 align:start position:0% code and create doesn't have the same 00:08:57.709 --> 00:09:00.100 align:start position:0% code and create doesn't have the same limitations<00:08:58.130> on<00:08:58.639> being<00:08:58.699> you<00:08:59.360> can<00:08:59.509> change<00:08:59.779> the 00:09:00.100 --> 00:09:00.110 align:start position:0% limitations on being you can change the 00:09:00.110 --> 00:09:02.439 align:start position:0% limitations on being you can change the creation<00:09:00.769> code<00:09:00.889> all<00:09:01.040> you<00:09:01.189> want<00:09:01.370> but<00:09:02.089> then<00:09:02.269> if 00:09:02.439 --> 00:09:02.449 align:start position:0% creation code all you want but then if 00:09:02.449 --> 00:09:05.620 align:start position:0% creation code all you want but then if if<00:09:02.689> the<00:09:03.759> transient<00:09:04.759> contract<00:09:05.180> immediately 00:09:05.620 --> 00:09:05.630 align:start position:0% if the transient contract immediately 00:09:05.630 --> 00:09:07.840 align:start position:0% if the transient contract immediately destroys<00:09:06.259> itself<00:09:06.560> after<00:09:06.800> it's<00:09:07.069> done<00:09:07.250> so<00:09:07.759> then 00:09:07.840 --> 00:09:07.850 align:start position:0% destroys itself after it's done so then 00:09:07.850 --> 00:09:10.050 align:start position:0% destroys itself after it's done so then if<00:09:07.939> you<00:09:08.029> want<00:09:08.180> to<00:09:08.209> go<00:09:08.300> back<00:09:08.480> and<00:09:08.660> redeploy 00:09:10.050 --> 00:09:10.060 align:start position:0% if you want to go back and redeploy 00:09:10.060 --> 00:09:13.389 align:start position:0% if you want to go back and redeploy remember<00:09:11.060> the<00:09:11.180> nonce<00:09:11.480> of<00:09:11.930> that<00:09:12.800> contract<00:09:13.220> is 00:09:13.389 --> 00:09:13.399 align:start position:0% remember the nonce of that contract is 00:09:13.399 --> 00:09:16.540 align:start position:0% remember the nonce of that contract is reset<00:09:13.850> so<00:09:14.389> create<00:09:15.319> is<00:09:15.560> going<00:09:15.769> to<00:09:15.829> hit<00:09:16.220> the<00:09:16.339> same 00:09:16.540 --> 00:09:16.550 align:start position:0% reset so create is going to hit the same 00:09:16.550 --> 00:09:19.900 align:start position:0% reset so create is going to hit the same ad<00:09:16.730> that's<00:09:16.970> again<00:09:17.290> this<00:09:18.290> has<00:09:18.829> the<00:09:18.980> limitation 00:09:19.900 --> 00:09:19.910 align:start position:0% ad that's again this has the limitation 00:09:19.910 --> 00:09:23.200 align:start position:0% ad that's again this has the limitation you<00:09:20.210> want<00:09:20.360> to<00:09:20.420> do<00:09:20.540> this<00:09:20.690> there's<00:09:21.230> two<00:09:22.210> contract 00:09:23.200 --> 00:09:23.210 align:start position:0% you want to do this there's two contract 00:09:23.210 --> 00:09:25.810 align:start position:0% you want to do this there's two contract appoints<00:09:23.600> so<00:09:24.140> there's<00:09:24.500> some<00:09:24.680> overhead<00:09:25.100> but 00:09:25.810 --> 00:09:25.820 align:start position:0% appoints so there's some overhead but 00:09:25.820 --> 00:09:27.850 align:start position:0% appoints so there's some overhead but it's<00:09:25.970> a<00:09:26.060> way<00:09:26.210> to<00:09:26.240> do<00:09:26.540> it<00:09:26.660> and<00:09:26.870> more<00:09:27.320> flexible 00:09:27.850 --> 00:09:27.860 align:start position:0% it's a way to do it and more flexible 00:09:27.860 --> 00:09:30.610 align:start position:0% it's a way to do it and more flexible fashion<00:09:28.070> and<00:09:28.490> support<00:09:28.790> constructors<00:09:29.620> finally 00:09:30.610 --> 00:09:30.620 align:start position:0% fashion and support constructors finally 00:09:30.620 --> 00:09:32.980 align:start position:0% fashion and support constructors finally my<00:09:30.830> personal<00:09:31.550> favorite<00:09:31.940> pattern<00:09:32.390> for<00:09:32.630> this<00:09:32.780> I 00:09:32.980 --> 00:09:32.990 align:start position:0% my personal favorite pattern for this I 00:09:32.990 --> 00:09:35.380 align:start position:0% my personal favorite pattern for this I call<00:09:33.590> the<00:09:33.680> metamorphic<00:09:34.400> delegator<00:09:34.940> pattern 00:09:35.380 --> 00:09:35.390 align:start position:0% call the metamorphic delegator pattern 00:09:35.390 --> 00:09:37.600 align:start position:0% call the metamorphic delegator pattern I'm<00:09:36.080> going<00:09:36.260> to<00:09:36.320> what<00:09:36.560> you<00:09:36.650> do<00:09:36.770> here<00:09:37.130> is<00:09:37.280> you<00:09:37.460> can 00:09:37.600 --> 00:09:37.610 align:start position:0% I'm going to what you do here is you can 00:09:37.610 --> 00:09:39.550 align:start position:0% I'm going to what you do here is you can actually<00:09:37.670> take<00:09:37.940> your<00:09:38.180> target<00:09:38.810> creation<00:09:39.320> code 00:09:39.550 --> 00:09:39.560 align:start position:0% actually take your target creation code 00:09:39.560 --> 00:09:42.990 align:start position:0% actually take your target creation code and<00:09:39.830> you<00:09:40.310> put<00:09:40.610> it<00:09:40.730> into<00:09:41.030> the<00:09:41.450> runtime<00:09:42.020> code<00:09:42.440> of 00:09:42.990 --> 00:09:43.000 align:start position:0% and you put it into the runtime code of 00:09:43.000 --> 00:09:46.690 align:start position:0% and you put it into the runtime code of another<00:09:44.000> contract<00:09:44.870> then<00:09:45.350> when<00:09:46.220> you<00:09:46.340> deploy 00:09:46.690 --> 00:09:46.700 align:start position:0% another contract then when you deploy 00:09:46.700 --> 00:09:49.660 align:start position:0% another contract then when you deploy this<00:09:47.150> metamorphic<00:09:47.900> contract<00:09:48.440> it's<00:09:49.340> going<00:09:49.610> to 00:09:49.660 --> 00:09:49.670 align:start position:0% this metamorphic contract it's going to 00:09:49.670 --> 00:09:52.750 align:start position:0% this metamorphic contract it's going to delegate<00:09:50.180> call<00:09:50.450> into<00:09:51.080> that<00:09:51.110> that<00:09:51.920> creation 00:09:52.750 --> 00:09:52.760 align:start position:0% delegate call into that that creation 00:09:52.760 --> 00:09:55.900 align:start position:0% delegate call into that that creation code<00:09:52.940> in<00:09:53.120> runtime<00:09:53.570> code<00:09:53.840> contract<00:09:54.530> and<00:09:54.910> it'll 00:09:55.900 --> 00:09:55.910 align:start position:0% code in runtime code contract and it'll 00:09:55.910 --> 00:09:58.930 align:start position:0% code in runtime code contract and it'll set<00:09:56.570> up<00:09:56.600> all<00:09:56.960> the<00:09:57.560> initialization<00:09:58.250> stuff<00:09:58.820> in 00:09:58.930 --> 00:09:58.940 align:start position:0% set up all the initialization stuff in 00:09:58.940 --> 00:10:01.680 align:start position:0% set up all the initialization stuff in the<00:09:59.000> constructor<00:09:59.540> and<00:09:59.810> then<00:10:00.140> return<00:10:00.680> your 00:10:01.680 --> 00:10:01.690 align:start position:0% the constructor and then return your 00:10:01.690 --> 00:10:04.930 align:start position:0% the constructor and then return your target<00:10:02.690> code<00:10:02.900> which<00:10:03.860> had<00:10:04.040> been<00:10:04.280> rights<00:10:04.670> to<00:10:04.820> my 00:10:04.930 --> 00:10:04.940 align:start position:0% target code which had been rights to my 00:10:04.940 --> 00:10:08.260 align:start position:0% target code which had been rights to my time<00:10:05.320> so<00:10:06.320> first<00:10:06.920> let's<00:10:07.160> look<00:10:07.250> at<00:10:07.640> what<00:10:07.880> a 00:10:08.260 --> 00:10:08.270 align:start position:0% time so first let's look at what a 00:10:08.270 --> 00:10:10.780 align:start position:0% time so first let's look at what a cloner<00:10:08.780> might<00:10:09.110> look<00:10:09.290> like<00:10:09.610> this<00:10:10.610> is<00:10:10.760> a 00:10:10.780 --> 00:10:10.790 align:start position:0% cloner might look like this is a 00:10:10.790 --> 00:10:14.380 align:start position:0% cloner might look like this is a standard<00:10:11.780> non<00:10:12.310> metamorphic<00:10:13.310> loner<00:10:13.520> where<00:10:14.180> the 00:10:14.380 --> 00:10:14.390 align:start position:0% standard non metamorphic loner where the 00:10:14.390 --> 00:10:16.690 align:start position:0% standard non metamorphic loner where the creation<00:10:15.170> code<00:10:15.290> changes<00:10:15.800> this<00:10:16.220> is<00:10:16.340> just<00:10:16.550> going 00:10:16.690 --> 00:10:16.700 align:start position:0% creation code changes this is just going 00:10:16.700 --> 00:10:19.630 align:start position:0% creation code changes this is just going to<00:10:16.760> take<00:10:17.600> our<00:10:18.230> target<00:10:18.800> and<00:10:19.040> put<00:10:19.400> it<00:10:19.460> on<00:10:19.550> the 00:10:19.630 --> 00:10:19.640 align:start position:0% to take our target and put it on the 00:10:19.640 --> 00:10:23.290 align:start position:0% to take our target and put it on the stack<00:10:19.880> and<00:10:19.910> then<00:10:20.270> copy<00:10:20.960> the<00:10:21.140> code<00:10:21.320> and<00:10:22.150> this<00:10:23.150> is 00:10:23.290 --> 00:10:23.300 align:start position:0% stack and then copy the code and this is 00:10:23.300 --> 00:10:26.110 align:start position:0% stack and then copy the code and this is what<00:10:23.750> a<00:10:23.780> factory<00:10:24.530> that<00:10:24.560> spits<00:10:25.460> out<00:10:25.580> that<00:10:25.820> clone 00:10:26.110 --> 00:10:26.120 align:start position:0% what a factory that spits out that clone 00:10:26.120 --> 00:10:28.870 align:start position:0% what a factory that spits out that clone might<00:10:26.390> look<00:10:26.600> like<00:10:26.660> as<00:10:27.170> you<00:10:27.800> can<00:10:28.010> see<00:10:28.220> our 00:10:28.870 --> 00:10:28.880 align:start position:0% might look like as you can see our 00:10:28.880 --> 00:10:31.240 align:start position:0% might look like as you can see our creation<00:10:29.780> code<00:10:29.900> is<00:10:29.990> gonna<00:10:30.080> change<00:10:30.440> so<00:10:30.890> if<00:10:31.130> we 00:10:31.240 --> 00:10:31.250 align:start position:0% creation code is gonna change so if we 00:10:31.250 --> 00:10:32.890 align:start position:0% creation code is gonna change so if we try<00:10:31.400> to<00:10:31.490> clone<00:10:31.880> a<00:10:31.910> new<00:10:32.030> address<00:10:32.390> it's<00:10:32.750> not 00:10:32.890 --> 00:10:32.900 align:start position:0% try to clone a new address it's not 00:10:32.900 --> 00:10:35.020 align:start position:0% try to clone a new address it's not going<00:10:33.050> to<00:10:33.110> work<00:10:33.290> so<00:10:33.620> here's<00:10:34.160> a<00:10:34.220> metamorphic 00:10:35.020 --> 00:10:35.030 align:start position:0% going to work so here's a metamorphic 00:10:35.030 --> 00:10:37.780 align:start position:0% going to work so here's a metamorphic version<00:10:35.600> of<00:10:35.900> that<00:10:36.200> clone<00:10:36.560> army<00:10:36.860> and<00:10:37.070> what<00:10:37.640> this 00:10:37.780 --> 00:10:37.790 align:start position:0% version of that clone army and what this 00:10:37.790 --> 00:10:39.970 align:start position:0% version of that clone army and what this is<00:10:37.910> going<00:10:38.030> to<00:10:38.090> do<00:10:38.360> is<00:10:38.630> we<00:10:38.780> store<00:10:39.200> the<00:10:39.590> address 00:10:39.970 --> 00:10:39.980 align:start position:0% is going to do is we store the address 00:10:39.980 --> 00:10:41.710 align:start position:0% is going to do is we store the address you<00:10:40.070> want<00:10:40.160> to<00:10:40.280> clone<00:10:40.490> on<00:10:40.700> the<00:10:40.910> factory<00:10:41.510> and 00:10:41.710 --> 00:10:41.720 align:start position:0% you want to clone on the factory and 00:10:41.720 --> 00:10:44.110 align:start position:0% you want to clone on the factory and then<00:10:41.960> this<00:10:42.440> calls<00:10:42.770> into<00:10:43.190> the<00:10:43.370> fall<00:10:43.610> back<00:10:43.820> on 00:10:44.110 --> 00:10:44.120 align:start position:0% then this calls into the fall back on 00:10:44.120 --> 00:10:46.990 align:start position:0% then this calls into the fall back on the<00:10:44.930> contract<00:10:45.350> it<00:10:45.470> deploys<00:10:45.740> it<00:10:46.010> does<00:10:46.580> a<00:10:46.610> static 00:10:46.990 --> 00:10:47.000 align:start position:0% the contract it deploys it does a static 00:10:47.000 --> 00:10:48.760 align:start position:0% the contract it deploys it does a static column<00:10:47.180> gets<00:10:47.450> that<00:10:47.690> address<00:10:48.050> and<00:10:48.200> then<00:10:48.320> uses 00:10:48.760 --> 00:10:48.770 align:start position:0% column gets that address and then uses 00:10:48.770 --> 00:10:52.400 align:start position:0% column gets that address and then uses that<00:10:48.800> to<00:10:50.080> copy<00:10:51.080> the<00:10:51.530> code 00:10:52.400 --> 00:10:52.410 align:start position:0% that to copy the code 00:10:52.410 --> 00:10:54.680 align:start position:0% that to copy the code contract<00:10:52.980> and<00:10:53.699> this<00:10:54.060> is<00:10:54.209> what<00:10:54.360> that<00:10:54.389> might 00:10:54.680 --> 00:10:54.690 align:start position:0% contract and this is what that might 00:10:54.690 --> 00:10:56.900 align:start position:0% contract and this is what that might look<00:10:54.720> like<00:10:54.870> it<00:10:55.170> does<00:10:55.319> simply<00:10:55.709> fall<00:10:55.920> back<00:10:56.160> that 00:10:56.900 --> 00:10:56.910 align:start position:0% look like it does simply fall back that 00:10:56.910 --> 00:11:00.499 align:start position:0% look like it does simply fall back that is<00:10:57.300> just<00:10:57.509> going<00:10:57.690> to<00:10:58.129> grab<00:10:59.129> the<00:10:59.430> target<00:11:00.389> address 00:11:00.499 --> 00:11:00.509 align:start position:0% is just going to grab the target address 00:11:00.509 --> 00:11:04.100 align:start position:0% is just going to grab the target address and<00:11:01.050> storage<00:11:01.500> and<00:11:01.769> give<00:11:02.430> it<00:11:02.519> back<00:11:02.779> so<00:11:03.779> then<00:11:03.990> you 00:11:04.100 --> 00:11:04.110 align:start position:0% and storage and give it back so then you 00:11:04.110 --> 00:11:05.629 align:start position:0% and storage and give it back so then you can<00:11:04.259> see<00:11:04.440> here<00:11:04.649> your<00:11:04.889> reasonable<00:11:05.310> never 00:11:05.629 --> 00:11:05.639 align:start position:0% can see here your reasonable never 00:11:05.639 --> 00:11:07.970 align:start position:0% can see here your reasonable never changes<00:11:06.180> but<00:11:06.720> every<00:11:06.959> time<00:11:07.139> you<00:11:07.319> call<00:11:07.470> this<00:11:07.680> as 00:11:07.970 --> 00:11:07.980 align:start position:0% changes but every time you call this as 00:11:07.980 --> 00:11:09.920 align:start position:0% changes but every time you call this as long<00:11:08.250> as<00:11:08.370> we<00:11:08.490> can<00:11:08.670> destroy<00:11:09.269> it<00:11:09.329> an<00:11:09.509> existing 00:11:09.920 --> 00:11:09.930 align:start position:0% long as we can destroy it an existing 00:11:09.930 --> 00:11:13.369 align:start position:0% long as we can destroy it an existing clone<00:11:10.230> we<00:11:11.009> can<00:11:11.160> keep<00:11:11.339> adding<00:11:12.199> upgrading<00:11:13.199> to 00:11:13.369 --> 00:11:13.379 align:start position:0% clone we can keep adding upgrading to 00:11:13.379 --> 00:11:17.809 align:start position:0% clone we can keep adding upgrading to new<00:11:13.970> cloned<00:11:14.970> contracts<00:11:16.579> let's<00:11:17.579> look<00:11:17.699> at<00:11:17.759> the 00:11:17.809 --> 00:11:17.819 align:start position:0% new cloned contracts let's look at the 00:11:17.819 --> 00:11:19.670 align:start position:0% new cloned contracts let's look at the transient<00:11:18.240> deployment<00:11:19.050> this<00:11:19.170> is<00:11:19.230> a<00:11:19.410> little 00:11:19.670 --> 00:11:19.680 align:start position:0% transient deployment this is a little 00:11:19.680 --> 00:11:21.710 align:start position:0% transient deployment this is a little more<00:11:19.829> involved<00:11:20.149> but<00:11:21.149> what<00:11:21.389> we're<00:11:21.540> basically 00:11:21.710 --> 00:11:21.720 align:start position:0% more involved but what we're basically 00:11:21.720 --> 00:11:23.480 align:start position:0% more involved but what we're basically going<00:11:21.959> to<00:11:22.019> do<00:11:22.199> here<00:11:22.410> is<00:11:22.649> we're<00:11:22.860> going<00:11:22.949> to<00:11:23.009> call 00:11:23.480 --> 00:11:23.490 align:start position:0% going to do here is we're going to call 00:11:23.490 --> 00:11:25.819 align:start position:0% going to do here is we're going to call in<00:11:23.730> to<00:11:24.060> the<00:11:24.089> fallback<00:11:24.360> same<00:11:24.870> thing<00:11:25.199> but<00:11:25.709> we're 00:11:25.819 --> 00:11:25.829 align:start position:0% in to the fallback same thing but we're 00:11:25.829 --> 00:11:26.900 align:start position:0% in to the fallback same thing but we're not<00:11:25.949> going<00:11:26.069> to<00:11:26.100> add<00:11:26.310> this<00:11:26.430> we're<00:11:26.610> getting<00:11:26.790> the 00:11:26.900 --> 00:11:26.910 align:start position:0% not going to add this we're getting the 00:11:26.910 --> 00:11:29.689 align:start position:0% not going to add this we're getting the creation<00:11:27.300> code<00:11:27.540> then<00:11:28.350> we<00:11:28.500> take<00:11:28.680> that<00:11:28.740> we<00:11:29.490> don't 00:11:29.689 --> 00:11:29.699 align:start position:0% creation code then we take that we don't 00:11:29.699 --> 00:11:31.790 align:start position:0% creation code then we take that we don't know<00:11:29.790> the<00:11:29.970> size<00:11:30.720> of<00:11:30.930> it<00:11:31.079> ahead<00:11:31.350> of<00:11:31.500> time<00:11:31.589> so 00:11:31.790 --> 00:11:31.800 align:start position:0% know the size of it ahead of time so 00:11:31.800 --> 00:11:34.069 align:start position:0% know the size of it ahead of time so we're<00:11:32.490> gonna<00:11:32.610> use<00:11:32.699> return<00:11:33.360> data<00:11:33.629> size<00:11:33.810> when 00:11:34.069 --> 00:11:34.079 align:start position:0% we're gonna use return data size when 00:11:34.079 --> 00:11:36.170 align:start position:0% we're gonna use return data size when turning<00:11:34.410> data<00:11:34.529> copy<00:11:34.829> to<00:11:35.490> put<00:11:35.639> it<00:11:35.730> into<00:11:35.879> memory 00:11:36.170 --> 00:11:36.180 align:start position:0% turning data copy to put it into memory 00:11:36.180 --> 00:11:39.410 align:start position:0% turning data copy to put it into memory and<00:11:36.389> then<00:11:36.480> we<00:11:37.050> create<00:11:37.379> now<00:11:38.009> if<00:11:38.220> this<00:11:38.459> if<00:11:39.120> it 00:11:39.410 --> 00:11:39.420 align:start position:0% and then we create now if this if it 00:11:39.420 --> 00:11:41.600 align:start position:0% and then we create now if this if it reverts<00:11:39.720> your<00:11:40.319> bill<00:11:40.680> and<00:11:40.800> grab<00:11:41.040> that<00:11:41.279> revert 00:11:41.600 --> 00:11:41.610 align:start position:0% reverts your bill and grab that revert 00:11:41.610 --> 00:11:44.569 align:start position:0% reverts your bill and grab that revert the<00:11:41.730> reason<00:11:42.029> and<00:11:42.240> return<00:11:42.839> it<00:11:42.990> otherwise<00:11:43.579> we're 00:11:44.569 --> 00:11:44.579 align:start position:0% the reason and return it otherwise we're 00:11:44.579 --> 00:11:46.369 align:start position:0% the reason and return it otherwise we're gonna<00:11:44.670> self-destruct<00:11:45.149> this<00:11:45.750> contract<00:11:46.230> so 00:11:46.369 --> 00:11:46.379 align:start position:0% gonna self-destruct this contract so 00:11:46.379 --> 00:11:48.499 align:start position:0% gonna self-destruct this contract so that<00:11:46.410> we<00:11:46.589> can<00:11:46.709> do<00:11:46.889> it<00:11:47.040> again<00:11:47.250> and<00:11:47.519> then<00:11:48.269> all<00:11:48.360> we 00:11:48.499 --> 00:11:48.509 align:start position:0% that we can do it again and then all we 00:11:48.509 --> 00:11:50.689 align:start position:0% that we can do it again and then all we got<00:11:48.629> to<00:11:48.750> do<00:11:48.839> is<00:11:48.959> self<00:11:49.170> destruct<00:11:49.560> this<00:11:49.769> up 00:11:50.689 --> 00:11:50.699 align:start position:0% got to do is self destruct this up 00:11:50.699 --> 00:11:55.939 align:start position:0% got to do is self destruct this up contract<00:11:51.600> and<00:11:51.949> redeploy<00:11:53.779> so<00:11:54.779> this<00:11:55.379> one<00:11:55.620> it 00:11:55.939 --> 00:11:55.949 align:start position:0% contract and redeploy so this one it 00:11:55.949 --> 00:11:57.710 align:start position:0% contract and redeploy so this one it looks<00:11:56.220> pretty<00:11:56.550> similar<00:11:56.730> to<00:11:57.060> the<00:11:57.149> last<00:11:57.329> example 00:11:57.710 --> 00:11:57.720 align:start position:0% looks pretty similar to the last example 00:11:57.720 --> 00:12:02.179 align:start position:0% looks pretty similar to the last example of<00:11:58.350> a<00:11:58.470> factory<00:11:59.060> rather<00:12:00.060> than<00:12:00.649> storing<00:12:01.649> an 00:12:02.179 --> 00:12:02.189 align:start position:0% of a factory rather than storing an 00:12:02.189 --> 00:12:06.050 align:start position:0% of a factory rather than storing an address<00:12:02.519> restoring<00:12:03.000> a<00:12:03.149> binary<00:12:03.860> and<00:12:04.939> the<00:12:05.939> other 00:12:06.050 --> 00:12:06.060 align:start position:0% address restoring a binary and the other 00:12:06.060 --> 00:12:07.790 align:start position:0% address restoring a binary and the other the<00:12:06.389> other<00:12:06.480> stuff<00:12:06.810> of<00:12:06.959> this<00:12:07.050> that's<00:12:07.290> important 00:12:07.790 --> 00:12:07.800 align:start position:0% the other stuff of this that's important 00:12:07.800 --> 00:12:10.220 align:start position:0% the other stuff of this that's important is<00:12:07.980> we<00:12:08.519> have<00:12:08.699> to<00:12:08.910> we<00:12:09.300> know<00:12:09.509> what<00:12:09.750> the<00:12:09.839> nonce<00:12:10.050> is 00:12:10.220 --> 00:12:10.230 align:start position:0% is we have to we know what the nonce is 00:12:10.230 --> 00:12:13.850 align:start position:0% is we have to we know what the nonce is gonna<00:12:10.439> be<00:12:10.560> one<00:12:10.800> on<00:12:11.519> the<00:12:12.470> transient<00:12:13.470> deployer 00:12:13.850 --> 00:12:13.860 align:start position:0% gonna be one on the transient deployer 00:12:13.860 --> 00:12:15.980 align:start position:0% gonna be one on the transient deployer so<00:12:14.459> we<00:12:14.550> can<00:12:14.699> use<00:12:14.850> that<00:12:15.000> our<00:12:15.149> LT<00:12:15.389> encoding<00:12:15.810> to 00:12:15.980 --> 00:12:15.990 align:start position:0% so we can use that our LT encoding to 00:12:15.990 --> 00:12:17.389 align:start position:0% so we can use that our LT encoding to figure<00:12:16.290> out<00:12:16.439> what<00:12:16.649> the<00:12:16.769> address<00:12:17.069> is 00:12:17.389 --> 00:12:17.399 align:start position:0% figure out what the address is 00:12:17.399 --> 00:12:20.780 align:start position:0% figure out what the address is and<00:12:18.000> we're<00:12:18.149> pointing<00:12:18.509> to<00:12:19.550> alright<00:12:20.550> and<00:12:20.699> then 00:12:20.780 --> 00:12:20.790 align:start position:0% and we're pointing to alright and then 00:12:20.790 --> 00:12:23.660 align:start position:0% and we're pointing to alright and then the<00:12:20.910> blesses<00:12:21.360> metamorphic<00:12:22.019> delegator<00:12:22.670> this 00:12:23.660 --> 00:12:23.670 align:start position:0% the blesses metamorphic delegator this 00:12:23.670 --> 00:12:26.660 align:start position:0% the blesses metamorphic delegator this one<00:12:23.970> is<00:12:24.509> basically<00:12:24.959> two<00:12:25.230> steps<00:12:25.529> step<00:12:26.160> one<00:12:26.430> is 00:12:26.660 --> 00:12:26.670 align:start position:0% one is basically two steps step one is 00:12:26.670 --> 00:12:29.780 align:start position:0% one is basically two steps step one is that<00:12:27.300> you<00:12:27.449> need<00:12:27.870> to<00:12:28.079> insert<00:12:28.980> that<00:12:29.040> creation 00:12:29.780 --> 00:12:29.790 align:start position:0% that you need to insert that creation 00:12:29.790 --> 00:12:31.579 align:start position:0% that you need to insert that creation code<00:12:29.939> into<00:12:30.449> the<00:12:30.480> runtime<00:12:31.079> code<00:12:31.290> of<00:12:31.410> another 00:12:31.579 --> 00:12:31.589 align:start position:0% code into the runtime code of another 00:12:31.589 --> 00:12:34.129 align:start position:0% code into the runtime code of another contract<00:12:32.130> this<00:12:32.699> is<00:12:32.880> what<00:12:33.329> I<00:12:33.360> called<00:12:33.600> preload 00:12:34.129 --> 00:12:34.139 align:start position:0% contract this is what I called preload 00:12:34.139 --> 00:12:36.799 align:start position:0% contract this is what I called preload or<00:12:34.439> block<00:12:35.370> of<00:12:35.399> code<00:12:35.579> you<00:12:35.850> can<00:12:35.970> insert<00:12:36.329> in<00:12:36.509> front 00:12:36.799 --> 00:12:36.809 align:start position:0% or block of code you can insert in front 00:12:36.809 --> 00:12:39.199 align:start position:0% or block of code you can insert in front of<00:12:36.930> whatever<00:12:37.079> arbitrary<00:12:38.009> runtime<00:12:38.790> you<00:12:39.000> want 00:12:39.199 --> 00:12:39.209 align:start position:0% of whatever arbitrary runtime you want 00:12:39.209 --> 00:12:39.560 align:start position:0% of whatever arbitrary runtime you want to<00:12:39.269> be 00:12:39.560 --> 00:12:39.570 align:start position:0% to be 00:12:39.570 --> 00:12:41.960 align:start position:0% to be deploying<00:12:40.230> and<00:12:41.040> it<00:12:41.160> will<00:12:41.250> play<00:12:41.519> it<00:12:41.579> for<00:12:41.820> you 00:12:41.960 --> 00:12:41.970 align:start position:0% deploying and it will play it for you 00:12:41.970 --> 00:12:45.769 align:start position:0% deploying and it will play it for you you<00:12:42.300> can<00:12:42.420> also<00:12:42.540> use<00:12:42.810> like<00:12:42.959> libraries<00:12:43.649> and<00:12:44.779> the 00:12:45.769 --> 00:12:45.779 align:start position:0% you can also use like libraries and the 00:12:45.779 --> 00:12:48.170 align:start position:0% you can also use like libraries and the cool<00:12:46.560> thing<00:12:46.589> about<00:12:46.800> this<00:12:47.070> is<00:12:47.339> you<00:12:47.759> can<00:12:47.880> do<00:12:48.029> this 00:12:48.170 --> 00:12:48.180 align:start position:0% cool thing about this is you can do this 00:12:48.180 --> 00:12:48.680 align:start position:0% cool thing about this is you can do this ahead<00:12:48.300> of<00:12:48.449> time 00:12:48.680 --> 00:12:48.690 align:start position:0% ahead of time 00:12:48.690 --> 00:12:52.519 align:start position:0% ahead of time you<00:12:49.199> can<00:12:49.320> even<00:12:49.440> reuse<00:12:50.120> the<00:12:51.120> same<00:12:51.529> creation 00:12:52.519 --> 00:12:52.529 align:start position:0% you can even reuse the same creation 00:12:52.529 --> 00:12:55.430 align:start position:0% you can even reuse the same creation code<00:12:52.769> in<00:12:53.130> runtime<00:12:53.519> code<00:12:53.970> blocks<00:12:54.300> then<00:12:55.230> once 00:12:55.430 --> 00:12:55.440 align:start position:0% code in runtime code blocks then once 00:12:55.440 --> 00:12:57.319 align:start position:0% code in runtime code blocks then once you've<00:12:55.589> got<00:12:55.800> that<00:12:56.009> that<00:12:56.459> contract<00:12:56.850> deployed 00:12:57.319 --> 00:12:57.329 align:start position:0% you've got that that contract deployed 00:12:57.329 --> 00:13:02.499 align:start position:0% you've got that that contract deployed then<00:12:59.180> here's<00:13:00.180> a<00:13:00.240> metamorphic<00:13:01.170> delegator 00:13:02.499 --> 00:13:02.509 align:start position:0% then here's a metamorphic delegator 00:13:02.509 --> 00:13:04.790 align:start position:0% then here's a metamorphic delegator payload<00:13:03.509> here<00:13:03.779> we're<00:13:04.410> just<00:13:04.440> gonna<00:13:04.589> put<00:13:04.769> a 00:13:04.790 --> 00:13:04.800 align:start position:0% payload here we're just gonna put a 00:13:04.800 --> 00:13:06.259 align:start position:0% payload here we're just gonna put a bunch<00:13:04.889> of<00:13:05.069> zeros<00:13:05.279> on<00:13:05.370> the<00:13:05.399> stack<00:13:05.670> to<00:13:05.880> use<00:13:06.000> later 00:13:06.259 --> 00:13:06.269 align:start position:0% bunch of zeros on the stack to use later 00:13:06.269 --> 00:13:08.629 align:start position:0% bunch of zeros on the stack to use later then<00:13:06.990> we<00:13:07.079> go<00:13:07.259> and<00:13:07.410> get<00:13:07.500> the<00:13:07.800> address<00:13:07.980> from<00:13:08.490> the 00:13:08.629 --> 00:13:08.639 align:start position:0% then we go and get the address from the 00:13:08.639 --> 00:13:11.240 align:start position:0% then we go and get the address from the fallback<00:13:09.290> the<00:13:10.290> creation<00:13:10.769> and<00:13:10.889> runtime 00:13:11.240 --> 00:13:11.250 align:start position:0% fallback the creation and runtime 00:13:11.250 --> 00:13:13.639 align:start position:0% fallback the creation and runtime address<00:13:11.779> then<00:13:12.779> we're<00:13:12.959> going<00:13:13.110> to<00:13:13.139> delegate 00:13:13.639 --> 00:13:13.649 align:start position:0% address then we're going to delegate 00:13:13.649 --> 00:13:17.240 align:start position:0% address then we're going to delegate call<00:13:13.920> in<00:13:14.250> to<00:13:14.579> that<00:13:14.699> address<00:13:14.910> and<00:13:16.250> either 00:13:17.240 --> 00:13:17.250 align:start position:0% call in to that address and either 00:13:17.250 --> 00:13:20.030 align:start position:0% call in to that address and either bubble<00:13:18.149> up<00:13:18.240> the<00:13:18.360> revert<00:13:18.630> reason<00:13:19.050> or<00:13:19.560> return 00:13:20.030 --> 00:13:20.040 align:start position:0% bubble up the revert reason or return 00:13:20.040 --> 00:13:22.189 align:start position:0% bubble up the revert reason or return the<00:13:20.759> runtime<00:13:21.180> code<00:13:21.300> because<00:13:21.779> we're<00:13:21.990> in<00:13:22.110> a 00:13:22.189 --> 00:13:22.199 align:start position:0% the runtime code because we're in a 00:13:22.199 --> 00:13:24.050 align:start position:0% the runtime code because we're in a constructor<00:13:22.740> by<00:13:23.160> returning<00:13:23.579> that<00:13:23.699> code<00:13:23.910> we 00:13:24.050 --> 00:13:24.060 align:start position:0% constructor by returning that code we 00:13:24.060 --> 00:13:25.309 align:start position:0% constructor by returning that code we write<00:13:24.269> it<00:13:24.389> to<00:13:24.660> storage 00:13:25.309 --> 00:13:25.319 align:start position:0% write it to storage 00:13:25.319 --> 00:13:29.360 align:start position:0% write it to storage or<00:13:26.220> to<00:13:26.399> run<00:13:26.550> times<00:13:27.350> so<00:13:28.350> here's<00:13:28.620> the<00:13:28.889> factory 00:13:29.360 --> 00:13:29.370 align:start position:0% or to run times so here's the factory 00:13:29.370 --> 00:13:32.660 align:start position:0% or to run times so here's the factory for<00:13:29.550> this<00:13:30.079> it's<00:13:31.079> basically<00:13:31.440> going<00:13:31.860> to<00:13:31.920> take 00:13:32.660 --> 00:13:32.670 align:start position:0% for this it's basically going to take 00:13:32.670 --> 00:13:35.629 align:start position:0% for this it's basically going to take our<00:13:32.880> creation<00:13:33.329> code<00:13:33.509> and<00:13:33.870> deploy<00:13:34.470> a<00:13:35.009> creation 00:13:35.629 --> 00:13:35.639 align:start position:0% our creation code and deploy a creation 00:13:35.639 --> 00:13:37.759 align:start position:0% our creation code and deploy a creation and<00:13:35.850> code<00:13:36.180> in<00:13:36.360> run<00:13:36.569> time<00:13:36.600> storage<00:13:37.230> contract 00:13:37.759 --> 00:13:37.769 align:start position:0% and code in run time storage contract 00:13:37.769 --> 00:13:39.710 align:start position:0% and code in run time storage contract once<00:13:38.490> again<00:13:38.699> this<00:13:39.000> is<00:13:39.180> something<00:13:39.360> you<00:13:39.480> could 00:13:39.710 --> 00:13:39.720 align:start position:0% once again this is something you could 00:13:39.720 --> 00:13:42.889 align:start position:0% once again this is something you could do<00:13:39.899> ahead<00:13:40.050> of<00:13:40.199> time<00:13:40.319> and<00:13:40.769> reuse<00:13:41.639> if<00:13:42.569> you<00:13:42.690> wanted 00:13:42.889 --> 00:13:42.899 align:start position:0% do ahead of time and reuse if you wanted 00:13:42.899 --> 00:13:44.420 align:start position:0% do ahead of time and reuse if you wanted to<00:13:43.019> really<00:13:43.170> choose<00:13:43.529> select<00:13:43.829> the<00:13:43.920> efficiency 00:13:44.420 --> 00:13:44.430 align:start position:0% to really choose select the efficiency 00:13:44.430 --> 00:13:46.759 align:start position:0% to really choose select the efficiency out<00:13:44.459> of<00:13:44.579> it<00:13:44.790> and<00:13:45.029> then<00:13:45.540> we're<00:13:46.380> gonna<00:13:46.470> take<00:13:46.709> it 00:13:46.759 --> 00:13:46.769 align:start position:0% out of it and then we're gonna take it 00:13:46.769 --> 00:13:48.980 align:start position:0% out of it and then we're gonna take it and<00:13:47.160> deploy<00:13:47.610> our<00:13:47.850> fix<00:13:48.240> non-deterministic 00:13:48.980 --> 00:13:48.990 align:start position:0% and deploy our fix non-deterministic 00:13:48.990 --> 00:13:52.189 align:start position:0% and deploy our fix non-deterministic byte<00:13:49.319> code<00:13:49.560> that<00:13:49.800> goes<00:13:50.089> graphs<00:13:51.089> that<00:13:51.690> address 00:13:52.189 --> 00:13:52.199 align:start position:0% byte code that goes graphs that address 00:13:52.199 --> 00:13:56.920 align:start position:0% byte code that goes graphs that address and<00:13:52.500> delegate<00:13:53.010> causing<00:13:54.860> so<00:13:55.860> this<00:13:56.399> obviously 00:13:56.920 --> 00:13:56.930 align:start position:0% and delegate causing so this obviously 00:13:56.930 --> 00:13:59.329 align:start position:0% and delegate causing so this obviously if<00:13:57.930> you<00:13:58.079> want<00:13:58.260> to<00:13:58.319> go<00:13:58.410> down<00:13:58.680> this<00:13:58.860> rabbit<00:13:59.069> all 00:13:59.329 --> 00:13:59.339 align:start position:0% if you want to go down this rabbit all 00:13:59.339 --> 00:14:02.360 align:start position:0% if you want to go down this rabbit all there's<00:13:59.519> a<00:13:59.579> lot<00:13:59.610> to<00:14:00.029> it<00:14:00.740> if<00:14:01.740> these<00:14:02.100> are<00:14:02.190> kind<00:14:02.339> of 00:14:02.360 --> 00:14:02.370 align:start position:0% there's a lot to it if these are kind of 00:14:02.370 --> 00:14:05.750 align:start position:0% there's a lot to it if these are kind of minimal<00:14:02.760> examples<00:14:03.269> where<00:14:03.949> you<00:14:04.949> can<00:14:05.130> supply 00:14:05.750 --> 00:14:05.760 align:start position:0% minimal examples where you can supply 00:14:05.760 --> 00:14:07.340 align:start position:0% minimal examples where you can supply your<00:14:06.000> own<00:14:06.029> salts<00:14:06.420> you<00:14:06.510> can<00:14:06.630> do<00:14:06.720> all<00:14:06.990> kinds<00:14:07.290> of 00:14:07.340 --> 00:14:07.350 align:start position:0% your own salts you can do all kinds of 00:14:07.350 --> 00:14:10.009 align:start position:0% your own salts you can do all kinds of tricks<00:14:07.529> so<00:14:07.829> I<00:14:08.190> put<00:14:08.490> together<00:14:08.579> a<00:14:08.959> sort<00:14:09.959> of 00:14:10.009 --> 00:14:10.019 align:start position:0% tricks so I put together a sort of 00:14:10.019 --> 00:14:13.730 align:start position:0% tricks so I put together a sort of utility<00:14:10.500> contract<00:14:10.980> of<00:14:11.190> homework<00:14:11.819> that<00:14:12.120> is<00:14:12.959> it 00:14:13.730 --> 00:14:13.740 align:start position:0% utility contract of homework that is it 00:14:13.740 --> 00:14:15.350 align:start position:0% utility contract of homework that is it uses<00:14:14.190> this<00:14:14.310> a<00:14:14.370> metamorphic<00:14:14.910> delegator 00:14:15.350 --> 00:14:15.360 align:start position:0% uses this a metamorphic delegator 00:14:15.360 --> 00:14:18.949 align:start position:0% uses this a metamorphic delegator pattern<00:14:15.779> but<00:14:16.380> what<00:14:16.500> it<00:14:16.589> does<00:14:16.860> in<00:14:17.610> CNF<00:14:18.180> T's<00:14:18.420> but 00:14:18.949 --> 00:14:18.959 align:start position:0% pattern but what it does in CNF T's but 00:14:18.959 --> 00:14:21.050 align:start position:0% pattern but what it does in CNF T's but you<00:14:19.110> Clark<00:14:19.560> addresses<00:14:20.370> ahead<00:14:20.610> of<00:14:20.699> time<00:14:20.880> and 00:14:21.050 --> 00:14:21.060 align:start position:0% you Clark addresses ahead of time and 00:14:21.060 --> 00:14:24.199 align:start position:0% you Clark addresses ahead of time and then<00:14:21.720> deploy<00:14:22.500> or<00:14:22.949> redeploy<00:14:23.459> contracts<00:14:24.029> to 00:14:24.199 --> 00:14:24.209 align:start position:0% then deploy or redeploy contracts to 00:14:24.209 --> 00:14:26.329 align:start position:0% then deploy or redeploy contracts to those<00:14:24.329> addresses<00:14:24.779> and<00:14:25.470> also<00:14:25.800> sort<00:14:26.069> of<00:14:26.160> makes 00:14:26.329 --> 00:14:26.339 align:start position:0% those addresses and also sort of makes 00:14:26.339 --> 00:14:26.590 align:start position:0% those addresses and also sort of makes the 00:14:26.590 --> 00:14:26.600 align:start position:0% the 00:14:26.600 --> 00:14:29.980 align:start position:0% the Plumtree<00:14:28.550> you're<00:14:29.269> welcome<00:14:29.540> to<00:14:29.569> check<00:14:29.779> it<00:14:29.810> out 00:14:29.980 --> 00:14:29.990 align:start position:0% Plumtree you're welcome to check it out 00:14:29.990 --> 00:14:31.420 align:start position:0% Plumtree you're welcome to check it out and<00:14:30.230> also<00:14:30.380> have<00:14:30.649> you<00:14:30.740> answer<00:14:30.949> any<00:14:31.069> questions 00:14:31.420 --> 00:14:31.430 align:start position:0% and also have you answer any questions 00:14:31.430 --> 00:14:33.069 align:start position:0% and also have you answer any questions about<00:14:31.519> it<00:14:31.819> now 00:14:33.069 --> 00:14:33.079 align:start position:0% about it now 00:14:33.079 --> 00:14:35.290 align:start position:0% about it now a<00:14:33.110> hope<00:14:33.649> this<00:14:33.889> film<00:14:34.130> might<00:14:34.459> make<00:14:34.759> you<00:14:34.970> a<00:14:35.000> bit 00:14:35.290 --> 00:14:35.300 align:start position:0% a hope this film might make you a bit 00:14:35.300 --> 00:14:37.569 align:start position:0% a hope this film might make you a bit squeamish<00:14:35.839> I<00:14:36.319> know<00:14:36.740> most<00:14:37.040> the<00:14:37.160> people<00:14:37.339> I 00:14:37.569 --> 00:14:37.579 align:start position:0% squeamish I know most the people I 00:14:37.579 --> 00:14:41.379 align:start position:0% squeamish I know most the people I explained<00:14:38.329> this<00:14:38.480> to<00:14:38.540> it<00:14:38.839> really<00:14:39.910> goes<00:14:40.910> against 00:14:41.379 --> 00:14:41.389 align:start position:0% explained this to it really goes against 00:14:41.389 --> 00:14:45.610 align:start position:0% explained this to it really goes against the<00:14:41.680> standard<00:14:43.569> immutable<00:14:44.569> principles<00:14:44.839> of 00:14:45.610 --> 00:14:45.620 align:start position:0% the standard immutable principles of 00:14:45.620 --> 00:14:48.819 align:start position:0% the standard immutable principles of what<00:14:45.800> we're<00:14:46.009> doing<00:14:46.310> so<00:14:47.110> let's<00:14:48.110> talk<00:14:48.290> about<00:14:48.350> how 00:14:48.819 --> 00:14:48.829 align:start position:0% what we're doing so let's talk about how 00:14:48.829 --> 00:14:51.069 align:start position:0% what we're doing so let's talk about how you<00:14:49.699> can<00:14:49.880> protect<00:14:50.089> against<00:14:50.600> this<00:14:50.750> because<00:14:50.899> the 00:14:51.069 --> 00:14:51.079 align:start position:0% you can protect against this because the 00:14:51.079 --> 00:14:54.280 align:start position:0% you can protect against this because the truth<00:14:51.259> is<00:14:51.410> it's<00:14:51.589> impossible<00:14:52.149> so<00:14:53.290> there's 00:14:54.280 --> 00:14:54.290 align:start position:0% truth is it's impossible so there's 00:14:54.290 --> 00:14:56.949 align:start position:0% truth is it's impossible so there's three<00:14:54.680> big<00:14:54.980> things<00:14:55.250> first<00:14:55.819> off<00:14:56.060> the<00:14:56.660> best 00:14:56.949 --> 00:14:56.959 align:start position:0% three big things first off the best 00:14:56.959 --> 00:14:58.780 align:start position:0% three big things first off the best protection<00:14:57.410> you<00:14:57.649> can<00:14:57.709> provide<00:14:58.069> is<00:14:58.339> to<00:14:58.370> make 00:14:58.780 --> 00:14:58.790 align:start position:0% protection you can provide is to make 00:14:58.790 --> 00:15:01.449 align:start position:0% protection you can provide is to make sure<00:14:58.819> the<00:14:59.660> contract<00:15:00.170> cannot<00:15:00.529> be<00:15:00.769> destroyed 00:15:01.449 --> 00:15:01.459 align:start position:0% sure the contract cannot be destroyed 00:15:01.459 --> 00:15:03.639 align:start position:0% sure the contract cannot be destroyed it's<00:15:01.940> not<00:15:02.149> quite<00:15:02.509> as<00:15:02.630> simple<00:15:02.810> it's<00:15:03.259> like<00:15:03.380> no 00:15:03.639 --> 00:15:03.649 align:start position:0% it's not quite as simple it's like no 00:15:03.649 --> 00:15:05.800 align:start position:0% it's not quite as simple it's like no self-destruct<00:15:04.069> opcodes<00:15:04.759> because<00:15:05.600> you<00:15:05.690> can 00:15:05.800 --> 00:15:05.810 align:start position:0% self-destruct opcodes because you can 00:15:05.810 --> 00:15:07.629 align:start position:0% self-destruct opcodes because you can also<00:15:05.930> if<00:15:06.319> there's<00:15:06.500> delegate<00:15:06.980> calls<00:15:07.190> with<00:15:07.459> call 00:15:07.629 --> 00:15:07.639 align:start position:0% also if there's delegate calls with call 00:15:07.639 --> 00:15:09.370 align:start position:0% also if there's delegate calls with call codes<00:15:07.940> those<00:15:08.690> could<00:15:08.990> trigger<00:15:09.259> a 00:15:09.370 --> 00:15:09.380 align:start position:0% codes those could trigger a 00:15:09.380 --> 00:15:11.050 align:start position:0% codes those could trigger a self-destruct<00:15:09.589> in<00:15:10.130> the<00:15:10.190> context<00:15:10.699> of<00:15:10.759> your 00:15:11.050 --> 00:15:11.060 align:start position:0% self-destruct in the context of your 00:15:11.060 --> 00:15:13.990 align:start position:0% self-destruct in the context of your contract<00:15:11.810> and<00:15:11.990> in<00:15:12.500> this<00:15:12.620> world<00:15:13.009> where<00:15:13.399> it's 00:15:13.990 --> 00:15:14.000 align:start position:0% contract and in this world where it's 00:15:14.000 --> 00:15:15.759 align:start position:0% contract and in this world where it's upgradeable<00:15:14.569> everything<00:15:15.079> and<00:15:15.410> proxy 00:15:15.759 --> 00:15:15.769 align:start position:0% upgradeable everything and proxy 00:15:15.769 --> 00:15:17.410 align:start position:0% upgradeable everything and proxy everything<00:15:15.889> this<00:15:16.639> is<00:15:16.819> actually<00:15:17.120> a<00:15:17.149> harder 00:15:17.410 --> 00:15:17.420 align:start position:0% everything this is actually a harder 00:15:17.420 --> 00:15:19.990 align:start position:0% everything this is actually a harder guarantee<00:15:17.810> to<00:15:18.380> provide<00:15:18.800> in<00:15:19.130> many<00:15:19.370> cases<00:15:19.790> than 00:15:19.990 --> 00:15:20.000 align:start position:0% guarantee to provide in many cases than 00:15:20.000 --> 00:15:22.689 align:start position:0% guarantee to provide in many cases than many<00:15:20.720> of<00:15:20.810> us<00:15:20.899> would<00:15:21.050> like<00:15:21.339> what<00:15:22.339> you<00:15:22.430> can<00:15:22.550> do 00:15:22.689 --> 00:15:22.699 align:start position:0% many of us would like what you can do 00:15:22.699 --> 00:15:24.460 align:start position:0% many of us would like what you can do though<00:15:22.850> if<00:15:23.000> you<00:15:23.120> can<00:15:23.149> provide<00:15:23.779> this<00:15:23.990> guarantee 00:15:24.460 --> 00:15:24.470 align:start position:0% though if you can provide this guarantee 00:15:24.470 --> 00:15:27.189 align:start position:0% though if you can provide this guarantee if<00:15:25.100> you<00:15:25.250> give<00:15:25.459> your<00:15:25.670> contracts<00:15:26.209> to<00:15:26.329> this<00:15:26.449> this 00:15:27.189 --> 00:15:27.199 align:start position:0% if you give your contracts to this this 00:15:27.199 --> 00:15:30.490 align:start position:0% if you give your contracts to this this registry<00:15:28.009> indestructible<00:15:29.000> buddy<00:15:29.209> it'll<00:15:30.139> scan 00:15:30.490 --> 00:15:30.500 align:start position:0% registry indestructible buddy it'll scan 00:15:30.500 --> 00:15:33.850 align:start position:0% registry indestructible buddy it'll scan them<00:15:30.769> and<00:15:31.839> stamp<00:15:32.839> them<00:15:32.990> it's<00:15:33.199> like<00:15:33.350> this<00:15:33.709> is 00:15:33.850 --> 00:15:33.860 align:start position:0% them and stamp them it's like this is 00:15:33.860 --> 00:15:36.759 align:start position:0% them and stamp them it's like this is indestructible<00:15:34.279> you're<00:15:35.149> good<00:15:35.389> so<00:15:36.380> that's<00:15:36.470> one 00:15:36.759 --> 00:15:36.769 align:start position:0% indestructible you're good so that's one 00:15:36.769 --> 00:15:38.920 align:start position:0% indestructible you're good so that's one way<00:15:36.949> you<00:15:37.009> can<00:15:37.310> protect<00:15:37.639> another<00:15:38.600> thing<00:15:38.839> you 00:15:38.920 --> 00:15:38.930 align:start position:0% way you can protect another thing you 00:15:38.930 --> 00:15:40.840 align:start position:0% way you can protect another thing you can<00:15:39.110> do<00:15:39.259> is<00:15:39.560> you<00:15:40.040> can<00:15:40.130> ensure<00:15:40.459> that<00:15:40.490> the 00:15:40.840 --> 00:15:40.850 align:start position:0% can do is you can ensure that the 00:15:40.850 --> 00:15:43.569 align:start position:0% can do is you can ensure that the contracts<00:15:41.480> are<00:15:41.630> being<00:15:41.930> deployed<00:15:42.410> and<00:15:42.860> mutable 00:15:43.569 --> 00:15:43.579 align:start position:0% contracts are being deployed and mutable 00:15:43.579 --> 00:15:45.879 align:start position:0% contracts are being deployed and mutable it's<00:15:44.329> not<00:15:44.480> just<00:15:44.750> quite<00:15:45.079> as<00:15:45.170> simple<00:15:45.470> as<00:15:45.560> create 00:15:45.879 --> 00:15:45.889 align:start position:0% it's not just quite as simple as create 00:15:45.889 --> 00:15:48.660 align:start position:0% it's not just quite as simple as create has<00:15:46.130> to<00:15:46.250> create<00:15:46.699> all<00:15:46.970> the<00:15:47.660> way<00:15:47.810> down<00:15:48.110> to<00:15:48.410> like 00:15:48.660 --> 00:15:48.670 align:start position:0% has to create all the way down to like 00:15:48.670 --> 00:15:51.100 align:start position:0% has to create all the way down to like something<00:15:49.670> that<00:15:49.819> has<00:15:49.970> never<00:15:50.209> touched<00:15:50.630> create 00:15:51.100 --> 00:15:51.110 align:start position:0% something that has never touched create 00:15:51.110 --> 00:15:52.720 align:start position:0% something that has never touched create two<00:15:51.319> because<00:15:51.620> you<00:15:51.740> can<00:15:51.889> bubble<00:15:52.130> them<00:15:52.370> all<00:15:52.490> up 00:15:52.720 --> 00:15:52.730 align:start position:0% two because you can bubble them all up 00:15:52.730 --> 00:15:54.939 align:start position:0% two because you can bubble them all up or<00:15:53.209> you<00:15:53.870> know<00:15:53.990> it's<00:15:54.170> created<00:15:54.620> by<00:15:54.740> something 00:15:54.939 --> 00:15:54.949 align:start position:0% or you know it's created by something 00:15:54.949 --> 00:15:57.730 align:start position:0% or you know it's created by something that<00:15:55.069> is<00:15:55.189> itself<00:15:55.610> indestructible<00:15:56.740> finally 00:15:57.730 --> 00:15:57.740 align:start position:0% that is itself indestructible finally 00:15:57.740 --> 00:16:00.400 align:start position:0% that is itself indestructible finally you<00:15:58.189> can<00:15:58.339> go<00:15:58.519> through<00:15:58.850> beautiful<00:15:59.569> create<00:16:00.199> two 00:16:00.400 --> 00:16:00.410 align:start position:0% you can go through beautiful create two 00:16:00.410 --> 00:16:02.710 align:start position:0% you can go through beautiful create two factories<00:16:01.009> there<00:16:01.339> is<00:16:01.459> a<00:16:01.490> example<00:16:02.300> of<00:16:02.540> one<00:16:02.689> that 00:16:02.710 --> 00:16:02.720 align:start position:0% factories there is a example of one that 00:16:02.720 --> 00:16:03.550 align:start position:0% factories there is a example of one that you<00:16:02.870> can<00:16:03.050> use 00:16:03.550 --> 00:16:03.560 align:start position:0% you can use 00:16:03.560 --> 00:16:06.189 align:start position:0% you can use they<00:16:04.129> to<00:16:04.189> factory<00:16:04.939> Dottie<00:16:05.180> and<00:16:05.569> other 00:16:06.189 --> 00:16:06.199 align:start position:0% they to factory Dottie and other 00:16:06.199 --> 00:16:08.710 align:start position:0% they to factory Dottie and other contracts<00:16:07.040> that<00:16:07.129> do<00:16:07.279> similar<00:16:07.459> stuff<00:16:07.939> and<00:16:08.149> then 00:16:08.710 --> 00:16:08.720 align:start position:0% contracts that do similar stuff and then 00:16:08.720 --> 00:16:11.139 align:start position:0% contracts that do similar stuff and then you<00:16:08.870> basically<00:16:09.019> just<00:16:09.230> track<00:16:09.709> once<00:16:10.220> you've 00:16:11.139 --> 00:16:11.149 align:start position:0% you basically just track once you've 00:16:11.149 --> 00:16:13.420 align:start position:0% you basically just track once you've used<00:16:11.180> a<00:16:11.600> particular<00:16:11.749> assault<00:16:12.560> and<00:16:12.800> an<00:16:12.860> info<00:16:13.189> or 00:16:13.420 --> 00:16:13.430 align:start position:0% used a particular assault and an info or 00:16:13.430 --> 00:16:17.439 align:start position:0% used a particular assault and an info or whatever<00:16:13.730> and<00:16:14.149> don't<00:16:14.600> let<00:16:14.779> your<00:16:14.899> be<00:16:16.180> the<00:16:17.180> third 00:16:17.439 --> 00:16:17.449 align:start position:0% whatever and don't let your be the third 00:16:17.449 --> 00:16:20.590 align:start position:0% whatever and don't let your be the third thing<00:16:17.720> here<00:16:18.079> is<00:16:18.560> that<00:16:18.610> you<00:16:19.610> can<00:16:19.790> check<00:16:20.120> the<00:16:20.329> run 00:16:20.590 --> 00:16:20.600 align:start position:0% thing here is that you can check the run 00:16:20.600 --> 00:16:23.679 align:start position:0% thing here is that you can check the run time<00:16:20.959> the<00:16:21.259> Xcode<00:16:22.069> hash<00:16:22.339> into<00:16:22.910> the<00:16:23.029> contracts 00:16:23.679 --> 00:16:23.689 align:start position:0% time the Xcode hash into the contracts 00:16:23.689 --> 00:16:25.329 align:start position:0% time the Xcode hash into the contracts that<00:16:23.839> you<00:16:23.899> want<00:16:24.230> to<00:16:24.290> interact<00:16:24.800> with<00:16:24.920> them<00:16:25.160> make 00:16:25.329 --> 00:16:25.339 align:start position:0% that you want to interact with them make 00:16:25.339 --> 00:16:27.069 align:start position:0% that you want to interact with them make sure<00:16:25.370> they<00:16:25.730> haven't<00:16:25.910> changed<00:16:26.240> at<00:16:26.600> the<00:16:26.689> injury 00:16:27.069 --> 00:16:27.079 align:start position:0% sure they haven't changed at the injury 00:16:27.079 --> 00:16:29.139 align:start position:0% sure they haven't changed at the injury now<00:16:27.620> this<00:16:27.800> isn't<00:16:28.009> going<00:16:28.220> to<00:16:28.279> protect<00:16:28.459> against 00:16:29.139 --> 00:16:29.149 align:start position:0% now this isn't going to protect against 00:16:29.149 --> 00:16:31.569 align:start position:0% now this isn't going to protect against a<00:16:29.329> standard<00:16:29.839> read<00:16:30.589> employs<00:16:30.920> the<00:16:31.189> zombie 00:16:31.569 --> 00:16:31.579 align:start position:0% a standard read employs the zombie 00:16:31.579 --> 00:16:32.920 align:start position:0% a standard read employs the zombie deploys<00:16:31.910> it's<00:16:32.059> only<00:16:32.240> gonna<00:16:32.389> protect<00:16:32.689> against 00:16:32.920 --> 00:16:32.930 align:start position:0% deploys it's only gonna protect against 00:16:32.930 --> 00:16:34.720 align:start position:0% deploys it's only gonna protect against a<00:16:32.990> metamorphic<00:16:33.620> contract<00:16:34.100> so<00:16:34.279> you<00:16:34.370> so<00:16:34.519> be 00:16:34.720 --> 00:16:34.730 align:start position:0% a metamorphic contract so you so be 00:16:34.730 --> 00:16:36.939 align:start position:0% a metamorphic contract so you so be careful<00:16:35.149> about<00:16:35.230> steak<00:16:36.230> and<00:16:36.439> might<00:16:36.559> get<00:16:36.709> wiped 00:16:36.939 --> 00:16:36.949 align:start position:0% careful about steak and might get wiped 00:16:36.949 --> 00:16:39.129 align:start position:0% careful about steak and might get wiped in<00:16:37.189> between<00:16:37.550> if<00:16:38.120> something<00:16:38.480> is<00:16:38.569> destructible 00:16:39.129 --> 00:16:39.139 align:start position:0% in between if something is destructible 00:16:39.139 --> 00:16:42.639 align:start position:0% in between if something is destructible and<00:16:39.620> you<00:16:40.069> can<00:16:40.220> register<00:16:41.110> just<00:16:42.110> ahead<00:16:42.379> of<00:16:42.410> time 00:16:42.639 --> 00:16:42.649 align:start position:0% and you can register just ahead of time 00:16:42.649 --> 00:16:44.439 align:start position:0% and you can register just ahead of time and<00:16:42.829> use<00:16:42.980> a<00:16:43.009> registry<00:16:43.550> like<00:16:43.730> this<00:16:43.939> one<00:16:44.120> code 00:16:44.439 --> 00:16:44.449 align:start position:0% and use a registry like this one code 00:16:44.449 --> 00:16:46.569 align:start position:0% and use a registry like this one code cache<00:16:44.689> cache<00:16:45.019> as<00:16:45.230> an<00:16:45.350> example<00:16:45.649> and<00:16:46.309> now<00:16:46.399> if<00:16:46.459> you 00:16:46.569 --> 00:16:46.579 align:start position:0% cache cache as an example and now if you 00:16:46.579 --> 00:16:49.269 align:start position:0% cache cache as an example and now if you combine<00:16:46.759> two<00:16:47.209> and<00:16:47.420> three<00:16:47.689> you've<00:16:48.279> covered 00:16:49.269 --> 00:16:49.279 align:start position:0% combine two and three you've covered 00:16:49.279 --> 00:16:51.999 align:start position:0% combine two and three you've covered most<00:16:49.610> of<00:16:49.730> your<00:16:49.910> bases<00:16:50.360> if<00:16:50.600> one<00:16:51.439> bit<00:16:51.709> is<00:16:51.829> not 00:16:51.999 --> 00:16:52.009 align:start position:0% most of your bases if one bit is not 00:16:52.009 --> 00:16:54.509 align:start position:0% most of your bases if one bit is not available<00:16:52.550> and<00:16:52.910> the<00:16:53.240> biggest<00:16:53.540> thing<00:16:53.720> here<00:16:54.019> is 00:16:54.509 --> 00:16:54.519 align:start position:0% available and the biggest thing here is 00:16:54.519 --> 00:16:57.160 align:start position:0% available and the biggest thing here is educate<00:16:55.519> people<00:16:55.699> about<00:16:55.970> this<00:16:56.360> slate<00:16:56.720> this 00:16:57.160 --> 00:16:57.170 align:start position:0% educate people about this slate this 00:16:57.170 --> 00:16:59.559 align:start position:0% educate people about this slate this should<00:16:57.470> be<00:16:57.620> in<00:16:57.800> the<00:16:57.889> checklist<00:16:58.339> during<00:16:59.180> an 00:16:59.559 --> 00:16:59.569 align:start position:0% should be in the checklist during an 00:16:59.569 --> 00:17:04.569 align:start position:0% should be in the checklist during an audit<00:16:59.839> to<00:17:00.529> make<00:17:00.680> sure<00:17:00.860> that<00:17:01.129> just<00:17:01.879> like<00:17:03.579> can't 00:17:04.569 --> 00:17:04.579 align:start position:0% audit to make sure that just like can't 00:17:04.579 --> 00:17:06.760 align:start position:0% audit to make sure that just like can't you<00:17:05.179> have<00:17:05.270> the<00:17:05.419> right<00:17:05.539> trust<00:17:05.870> assumptions<00:17:06.409> or 00:17:06.760 --> 00:17:06.770 align:start position:0% you have the right trust assumptions or 00:17:06.770 --> 00:17:08.319 align:start position:0% you have the right trust assumptions or dealing<00:17:07.400> with<00:17:07.520> ownership<00:17:07.789> you<00:17:08.089> have<00:17:08.179> the 00:17:08.319 --> 00:17:08.329 align:start position:0% dealing with ownership you have the 00:17:08.329 --> 00:17:09.490 align:start position:0% dealing with ownership you have the trade<00:17:08.539> trust<00:17:08.809> assumptions<00:17:09.289> when<00:17:09.380> you're 00:17:09.490 --> 00:17:09.500 align:start position:0% trade trust assumptions when you're 00:17:09.500 --> 00:17:10.960 align:start position:0% trade trust assumptions when you're doing<00:17:09.679> their<00:17:09.860> deployment<00:17:10.370> methods<00:17:10.669> if 00:17:10.960 --> 00:17:10.970 align:start position:0% doing their deployment methods if 00:17:10.970 --> 00:17:14.980 align:start position:0% doing their deployment methods if they're<00:17:12.309> susceptible<00:17:13.309> to<00:17:13.640> this<00:17:13.850> all<00:17:14.809> right 00:17:14.980 --> 00:17:14.990 align:start position:0% they're susceptible to this all right 00:17:14.990 --> 00:17:17.740 align:start position:0% they're susceptible to this all right all<00:17:15.470> your<00:17:15.709> white<00:17:15.890> hats<00:17:16.100> can<00:17:16.370> take<00:17:16.520> breath<00:17:17.030> for 00:17:17.740 --> 00:17:17.750 align:start position:0% all your white hats can take breath for 00:17:17.750 --> 00:17:21.279 align:start position:0% all your white hats can take breath for the<00:17:17.809> rest<00:17:18.020> of<00:17:18.199> us<00:17:18.319> let's<00:17:19.250> talk<00:17:19.399> about<00:17:20.140> some<00:17:21.140> of 00:17:21.279 --> 00:17:21.289 align:start position:0% the rest of us let's talk about some of 00:17:21.289 --> 00:17:23.799 align:start position:0% the rest of us let's talk about some of the<00:17:21.439> cool<00:17:21.740> things<00:17:22.189> that<00:17:22.549> you<00:17:22.760> can<00:17:22.970> do<00:17:23.270> with 00:17:23.799 --> 00:17:23.809 align:start position:0% the cool things that you can do with 00:17:23.809 --> 00:17:27.819 align:start position:0% the cool things that you can do with this<00:17:23.959> technology<00:17:24.939> so<00:17:25.939> first<00:17:26.569> off<00:17:26.829> contract 00:17:27.819 --> 00:17:27.829 align:start position:0% this technology so first off contract 00:17:27.829 --> 00:17:30.970 align:start position:0% this technology so first off contract deployments<00:17:28.459> it's<00:17:29.240> actually<00:17:29.630> really<00:17:30.080> cool<00:17:30.649> to 00:17:30.970 --> 00:17:30.980 align:start position:0% deployments it's actually really cool to 00:17:30.980 --> 00:17:32.799 align:start position:0% deployments it's actually really cool to be<00:17:31.100> able<00:17:31.250> to<00:17:31.669> park<00:17:31.970> an<00:17:32.059> address<00:17:32.360> ahead<00:17:32.600> of<00:17:32.659> time 00:17:32.799 --> 00:17:32.809 align:start position:0% be able to park an address ahead of time 00:17:32.809 --> 00:17:34.870 align:start position:0% be able to park an address ahead of time and<00:17:32.990> to<00:17:33.110> find<00:17:33.350> an<00:17:33.710> address<00:17:34.070> that's<00:17:34.399> efficient 00:17:34.870 --> 00:17:34.880 align:start position:0% and to find an address that's efficient 00:17:34.880 --> 00:17:37.510 align:start position:0% and to find an address that's efficient without<00:17:35.780> needing<00:17:36.169> to<00:17:36.409> tie<00:17:36.679> that<00:17:36.860> into<00:17:37.070> the 00:17:37.510 --> 00:17:37.520 align:start position:0% without needing to tie that into the 00:17:37.520 --> 00:17:39.850 align:start position:0% without needing to tie that into the creation<00:17:37.909> code<00:17:38.120> so<00:17:38.390> you<00:17:38.659> use<00:17:39.080> an<00:17:39.230> address<00:17:39.380> that 00:17:39.850 --> 00:17:39.860 align:start position:0% creation code so you use an address that 00:17:39.860 --> 00:17:42.100 align:start position:0% creation code so you use an address that has<00:17:40.039> lots<00:17:40.340> of<00:17:40.460> zero<00:17:40.730> lights<00:17:40.970> you<00:17:41.750> can<00:17:41.899> save 00:17:42.100 --> 00:17:42.110 align:start position:0% has lots of zero lights you can save 00:17:42.110 --> 00:17:43.770 align:start position:0% has lots of zero lights you can save quite<00:17:42.260> a<00:17:42.440> bit<00:17:42.559> of<00:17:42.649> gas<00:17:42.770> of<00:17:43.010> servicing<00:17:43.429> areas 00:17:43.770 --> 00:17:43.780 align:start position:0% quite a bit of gas of servicing areas 00:17:43.780 --> 00:17:47.139 align:start position:0% quite a bit of gas of servicing areas also<00:17:44.780> we<00:17:45.770> can<00:17:45.950> know<00:17:46.159> the<00:17:46.190> deployment<00:17:46.880> address 00:17:47.139 --> 00:17:47.149 align:start position:0% also we can know the deployment address 00:17:47.149 --> 00:17:48.940 align:start position:0% also we can know the deployment address of<00:17:47.270> any<00:17:47.390> of<00:17:47.510> our<00:17:47.570> contracts<00:17:48.080> ahead<00:17:48.380> of<00:17:48.500> time<00:17:48.679> so 00:17:48.940 --> 00:17:48.950 align:start position:0% of any of our contracts ahead of time so 00:17:48.950 --> 00:17:50.169 align:start position:0% of any of our contracts ahead of time so you<00:17:49.100> can<00:17:49.280> deploy<00:17:49.429> a<00:17:49.520> whole<00:17:49.640> family<00:17:49.940> of 00:17:50.169 --> 00:17:50.179 align:start position:0% you can deploy a whole family of 00:17:50.179 --> 00:17:52.320 align:start position:0% you can deploy a whole family of contracts<00:17:50.720> that<00:17:50.899> refer<00:17:51.289> to<00:17:51.320> each<00:17:51.620> other<00:17:51.950> as 00:17:52.320 --> 00:17:52.330 align:start position:0% contracts that refer to each other as 00:17:52.330 --> 00:17:56.590 align:start position:0% contracts that refer to each other as constants<00:17:53.330> and<00:17:53.690> are<00:17:53.870> interrelated<00:17:54.820> and<00:17:55.820> save 00:17:56.590 --> 00:17:56.600 align:start position:0% constants and are interrelated and save 00:17:56.600 --> 00:17:59.350 align:start position:0% constants and are interrelated and save gas<00:17:57.230> that<00:17:57.470> way<00:17:57.740> or<00:17:58.130> just<00:17:58.159> have<00:17:58.700> coordinated 00:17:59.350 --> 00:17:59.360 align:start position:0% gas that way or just have coordinated 00:17:59.360 --> 00:18:01.389 align:start position:0% gas that way or just have coordinated plays<00:17:59.539> about<00:17:59.690> having<00:18:00.080> two<00:18:00.230> buses<00:18:00.919> trackers 00:18:01.389 --> 00:18:01.399 align:start position:0% plays about having two buses trackers 00:18:01.399 --> 00:18:03.220 align:start position:0% plays about having two buses trackers all<00:18:01.760> of<00:18:02.059> the<00:18:02.210> nonces<00:18:02.659> appear 00:18:03.220 --> 00:18:03.230 align:start position:0% all of the nonces appear 00:18:03.230 --> 00:18:05.909 align:start position:0% all of the nonces appear an<00:18:03.380> address<00:18:03.740> isn't<00:18:04.040> a<00:18:04.070> really<00:18:04.340> granular<00:18:05.179> way 00:18:05.909 --> 00:18:05.919 align:start position:0% an address isn't a really granular way 00:18:05.919 --> 00:18:09.520 align:start position:0% an address isn't a really granular way finally<00:18:07.299> if<00:18:08.299> this<00:18:08.510> makes<00:18:08.809> it<00:18:08.960> easy<00:18:09.200> to<00:18:09.410> deploy 00:18:09.520 --> 00:18:09.530 align:start position:0% finally if this makes it easy to deploy 00:18:09.530 --> 00:18:11.440 align:start position:0% finally if this makes it easy to deploy different<00:18:10.340> contracts<00:18:10.760> that<00:18:10.910> are<00:18:11.030> slightly 00:18:11.440 --> 00:18:11.450 align:start position:0% different contracts that are slightly 00:18:11.450 --> 00:18:14.500 align:start position:0% different contracts that are slightly different<00:18:11.960> to<00:18:12.710> the<00:18:12.740> same<00:18:13.190> addresses<00:18:13.910> on<00:18:14.030> local 00:18:14.500 --> 00:18:14.510 align:start position:0% different to the same addresses on local 00:18:14.510 --> 00:18:18.580 align:start position:0% different to the same addresses on local test<00:18:15.169> meds<00:18:15.410> main<00:18:15.770> nets<00:18:16.100> other<00:18:16.790> chains<00:18:17.410> as<00:18:18.410> long 00:18:18.580 --> 00:18:18.590 align:start position:0% test meds main nets other chains as long 00:18:18.590 --> 00:18:20.680 align:start position:0% test meds main nets other chains as long as<00:18:18.740> you're<00:18:18.860> coming<00:18:19.040> out<00:18:19.250> of<00:18:19.370> the<00:18:19.460> same<00:18:19.690> factory 00:18:20.680 --> 00:18:20.690 align:start position:0% as you're coming out of the same factory 00:18:20.690 --> 00:18:25.390 align:start position:0% as you're coming out of the same factory its<00:18:21.410> deployed<00:18:22.100> across<00:18:22.309> chance<00:18:23.770> second<00:18:24.770> run 00:18:25.390 --> 00:18:25.400 align:start position:0% its deployed across chance second run 00:18:25.400 --> 00:18:28.090 align:start position:0% its deployed across chance second run time<00:18:25.669> storage<00:18:26.150> so<00:18:26.750> there's<00:18:27.440> a<00:18:27.530> lot<00:18:27.770> of<00:18:27.799> talk 00:18:28.090 --> 00:18:28.100 align:start position:0% time storage so there's a lot of talk 00:18:28.100 --> 00:18:30.610 align:start position:0% time storage so there's a lot of talk with<00:18:28.370> a<00:18:28.400> new<00:18:28.840> assemble<00:18:29.840> artwork<00:18:30.260> that<00:18:30.470> the 00:18:30.610 --> 00:18:30.620 align:start position:0% with a new assemble artwork that the 00:18:30.620 --> 00:18:32.980 align:start position:0% with a new assemble artwork that the price<00:18:30.950> of<00:18:30.980> s<00:18:31.250> low<00:18:31.429> is<00:18:31.490> going<00:18:31.640> to<00:18:31.730> quadruple<00:18:31.990> so 00:18:32.980 --> 00:18:32.990 align:start position:0% price of s low is going to quadruple so 00:18:32.990 --> 00:18:35.500 align:start position:0% price of s low is going to quadruple so you<00:18:33.380> can<00:18:33.530> use<00:18:33.740> run<00:18:34.070> time<00:18:34.340> storage<00:18:34.850> and<00:18:35.059> certain 00:18:35.500 --> 00:18:35.510 align:start position:0% you can use run time storage and certain 00:18:35.510 --> 00:18:39.190 align:start position:0% you can use run time storage and certain breathe<00:18:36.290> heavy<00:18:36.730> applications<00:18:37.730> to<00:18:38.270> make 00:18:39.190 --> 00:18:39.200 align:start position:0% breathe heavy applications to make 00:18:39.200 --> 00:18:42.010 align:start position:0% breathe heavy applications to make storage<00:18:39.740> a<00:18:39.950> lot<00:18:39.980> cheaper<00:18:40.370> and<00:18:40.700> also<00:18:41.390> more 00:18:42.010 --> 00:18:42.020 align:start position:0% storage a lot cheaper and also more 00:18:42.020 --> 00:18:43.840 align:start position:0% storage a lot cheaper and also more accessible<00:18:42.380> so<00:18:42.890> usually<00:18:43.520> when<00:18:43.669> you<00:18:43.730> go 00:18:43.840 --> 00:18:43.850 align:start position:0% accessible so usually when you go 00:18:43.850 --> 00:18:45.970 align:start position:0% accessible so usually when you go through<00:18:44.030> contract<00:18:44.660> storage<00:18:45.140> you<00:18:45.590> have<00:18:45.770> to<00:18:45.890> go 00:18:45.970 --> 00:18:45.980 align:start position:0% through contract storage you have to go 00:18:45.980 --> 00:18:48.430 align:start position:0% through contract storage you have to go through<00:18:46.130> again<00:18:46.370> right<00:18:47.000> and<00:18:47.270> the<00:18:47.780> contract<00:18:48.290> is 00:18:48.430 --> 00:18:48.440 align:start position:0% through again right and the contract is 00:18:48.440 --> 00:18:51.610 align:start position:0% through again right and the contract is dictating<00:18:48.890> how<00:18:49.220> that's<00:18:50.000> gonna<00:18:50.210> be<00:18:51.200> read<00:18:51.410> back 00:18:51.610 --> 00:18:51.620 align:start position:0% dictating how that's gonna be read back 00:18:51.620 --> 00:18:53.080 align:start position:0% dictating how that's gonna be read back to<00:18:51.650> you<00:18:51.919> but<00:18:52.070> if<00:18:52.160> you're<00:18:52.280> using<00:18:52.429> run<00:18:52.790> time 00:18:53.080 --> 00:18:53.090 align:start position:0% to you but if you're using run time 00:18:53.090 --> 00:18:54.669 align:start position:0% to you but if you're using run time storage<00:18:53.570> you're<00:18:53.750> just<00:18:53.900> copy<00:18:54.230> whatever 00:18:54.669 --> 00:18:54.679 align:start position:0% storage you're just copy whatever 00:18:54.679 --> 00:18:58.210 align:start position:0% storage you're just copy whatever portion<00:18:55.190> or<00:18:55.520> section<00:18:55.970> of<00:18:56.169> the<00:18:57.169> data<00:18:57.860> that's 00:18:58.210 --> 00:18:58.220 align:start position:0% portion or section of the data that's 00:18:58.220 --> 00:19:01.120 align:start position:0% portion or section of the data that's relevant<00:18:58.700> to<00:18:59.090> you<00:18:59.270> and<00:18:59.710> so<00:19:00.710> you<00:19:00.770> can<00:19:00.980> access 00:19:01.120 --> 00:19:01.130 align:start position:0% relevant to you and so you can access 00:19:01.130 --> 00:19:02.770 align:start position:0% relevant to you and so you can access storage<00:19:01.669> on<00:19:01.760> your<00:19:01.790> own<00:19:01.970> terms<00:19:02.210> it's<00:19:02.390> like<00:19:02.510> true 00:19:02.770 --> 00:19:02.780 align:start position:0% storage on your own terms it's like true 00:19:02.780 --> 00:19:05.470 align:start position:0% storage on your own terms it's like true public<00:19:03.410> storage<00:19:04.280> in<00:19:04.549> that<00:19:04.730> regard<00:19:05.059> and<00:19:05.270> it's 00:19:05.470 --> 00:19:05.480 align:start position:0% public storage in that regard and it's 00:19:05.480 --> 00:19:08.680 align:start position:0% public storage in that regard and it's also<00:19:05.600> cheaper<00:19:05.960> to<00:19:06.140> do<00:19:06.490> you<00:19:07.490> can<00:19:07.610> also<00:19:07.730> by 00:19:08.680 --> 00:19:08.690 align:start position:0% also cheaper to do you can also by 00:19:08.690 --> 00:19:10.930 align:start position:0% also cheaper to do you can also by transferring<00:19:09.290> ownership<00:19:09.710> over<00:19:10.250> to<00:19:10.429> accounts 00:19:10.930 --> 00:19:10.940 align:start position:0% transferring ownership over to accounts 00:19:10.940 --> 00:19:13.090 align:start position:0% transferring ownership over to accounts that<00:19:11.000> you<00:19:11.120> can<00:19:11.240> deploy<00:19:11.450> to<00:19:11.559> you<00:19:12.559> can<00:19:12.770> give 00:19:13.090 --> 00:19:13.100 align:start position:0% that you can deploy to you can give 00:19:13.100 --> 00:19:14.680 align:start position:0% that you can deploy to you can give ownership<00:19:13.549> of<00:19:13.700> a<00:19:13.760> region<00:19:14.090> of<00:19:14.120> storage<00:19:14.540> in<00:19:14.630> a 00:19:14.680 --> 00:19:14.690 align:start position:0% ownership of a region of storage in a 00:19:14.690 --> 00:19:16.419 align:start position:0% ownership of a region of storage in a way<00:19:14.840> that's<00:19:15.080> really<00:19:15.230> future<00:19:15.710> proof<00:19:15.919> right 00:19:16.419 --> 00:19:16.429 align:start position:0% way that's really future proof right 00:19:16.429 --> 00:19:18.070 align:start position:0% way that's really future proof right it's<00:19:16.640> not<00:19:16.820> tied<00:19:17.450> into<00:19:17.690> any<00:19:17.960> particular 00:19:18.070 --> 00:19:18.080 align:start position:0% it's not tied into any particular 00:19:18.080 --> 00:19:19.870 align:start position:0% it's not tied into any particular implementation<00:19:19.040> on<00:19:19.160> your<00:19:19.280> contract 00:19:19.870 --> 00:19:19.880 align:start position:0% implementation on your contract 00:19:19.880 --> 00:19:22.390 align:start position:0% implementation on your contract finally<00:19:20.780> it's<00:19:21.320> economical<00:19:21.860> as<00:19:21.980> we<00:19:22.160> were<00:19:22.220> sort 00:19:22.390 --> 00:19:22.400 align:start position:0% finally it's economical as we were sort 00:19:22.400 --> 00:19:25.870 align:start position:0% finally it's economical as we were sort of<00:19:22.429> discussing<00:19:23.000> you<00:19:23.690> can<00:19:23.840> save<00:19:24.110> a<00:19:24.440> lot<00:19:24.919> on<00:19:25.160> not 00:19:25.870 --> 00:19:25.880 align:start position:0% of discussing you can save a lot on not 00:19:25.880 --> 00:19:28.659 align:start position:0% of discussing you can save a lot on not only<00:19:26.179> reads<00:19:26.450> which<00:19:26.929> is<00:19:27.140> like<00:19:27.320> big<00:19:27.740> savings<00:19:28.220> but 00:19:28.659 --> 00:19:28.669 align:start position:0% only reads which is like big savings but 00:19:28.669 --> 00:19:31.390 align:start position:0% only reads which is like big savings but also<00:19:28.820> on<00:19:29.510> initial<00:19:30.320> storage<00:19:30.530> rates<00:19:30.830> especially 00:19:31.390 --> 00:19:31.400 align:start position:0% also on initial storage rates especially 00:19:31.400 --> 00:19:33.730 align:start position:0% also on initial storage rates especially for<00:19:31.549> larger<00:19:31.910> payloads<00:19:32.419> because<00:19:32.809> in<00:19:33.470> effect 00:19:33.730 --> 00:19:33.740 align:start position:0% for larger payloads because in effect 00:19:33.740 --> 00:19:36.970 align:start position:0% for larger payloads because in effect you<00:19:33.890> pay<00:19:34.150> twenty<00:19:35.150> thousand<00:19:35.510> gasp<00:19:35.630> a<00:19:35.660> word<00:19:36.020> if 00:19:36.970 --> 00:19:36.980 align:start position:0% you pay twenty thousand gasp a word if 00:19:36.980 --> 00:19:39.070 align:start position:0% you pay twenty thousand gasp a word if you're<00:19:37.160> storing<00:19:37.460> on<00:19:37.700> contract<00:19:38.120> storage<00:19:38.450> or<00:19:38.960> as 00:19:39.070 --> 00:19:39.080 align:start position:0% you're storing on contract storage or as 00:19:39.080 --> 00:19:42.190 align:start position:0% you're storing on contract storage or as you're<00:19:39.230> only<00:19:39.350> paying<00:19:39.880> 6,400<00:19:40.880> a<00:19:41.059> word<00:19:41.600> for 00:19:42.190 --> 00:19:42.200 align:start position:0% you're only paying 6,400 a word for 00:19:42.200 --> 00:19:44.710 align:start position:0% you're only paying 6,400 a word for every<00:19:42.860> read<00:19:43.040> time<00:19:43.280> storage<00:19:43.730> order<00:19:44.030> plus<00:19:44.540> the 00:19:44.710 --> 00:19:44.720 align:start position:0% every read time storage order plus the 00:19:44.720 --> 00:19:47.200 align:start position:0% every read time storage order plus the overhead<00:19:45.110> of<00:19:45.140> the<00:19:45.230> contract<00:19:45.770> and<00:19:46.340> you<00:19:47.059> can 00:19:47.200 --> 00:19:47.210 align:start position:0% overhead of the contract and you can 00:19:47.210 --> 00:19:50.050 align:start position:0% overhead of the contract and you can still<00:19:47.450> do<00:19:47.600> updates<00:19:47.960> by<00:19:48.290> using<00:19:49.220> some<00:19:49.490> kind<00:19:49.640> of 00:19:50.050 --> 00:19:50.060 align:start position:0% still do updates by using some kind of 00:19:50.060 --> 00:19:56.440 align:start position:0% still do updates by using some kind of system<00:19:51.580> third<00:19:52.580> smart<00:19:53.240> walnuts<00:19:53.630> so<00:19:55.210> the<00:19:56.210> theory 00:19:56.440 --> 00:19:56.450 align:start position:0% system third smart walnuts so the theory 00:19:56.450 --> 00:19:58.450 align:start position:0% system third smart walnuts so the theory moxie<00:19:56.810> doesn't<00:19:57.080> have<00:19:57.230> native<00:19:57.680> transactions 00:19:58.450 --> 00:19:58.460 align:start position:0% moxie doesn't have native transactions 00:19:58.460 --> 00:20:01.180 align:start position:0% moxie doesn't have native transactions script<00:19:58.850> support<00:19:59.270> it's<00:20:00.050> just<00:20:00.170> calling<00:20:00.710> into 00:20:01.180 --> 00:20:01.190 align:start position:0% script support it's just calling into 00:20:01.190 --> 00:20:03.850 align:start position:0% script support it's just calling into the<00:20:01.220> contracts<00:20:02.060> but<00:20:02.300> what<00:20:03.200> you<00:20:03.320> can<00:20:03.470> if<00:20:03.710> you 00:20:03.850 --> 00:20:03.860 align:start position:0% the contracts but what you can if you 00:20:03.860 --> 00:20:07.510 align:start position:0% the contracts but what you can if you use<00:20:03.890> one<00:20:04.580> of<00:20:04.610> these<00:20:04.930> Clark<00:20:05.990> addresses<00:20:06.650> as<00:20:07.130> your 00:20:07.510 --> 00:20:07.520 align:start position:0% use one of these Clark addresses as your 00:20:07.520 --> 00:20:10.030 align:start position:0% use one of these Clark addresses as your smart<00:20:08.120> wallet<00:20:08.450> you<00:20:08.990> can<00:20:09.110> deploy<00:20:09.350> contracts 00:20:10.030 --> 00:20:10.040 align:start position:0% smart wallet you can deploy contracts 00:20:10.040 --> 00:20:12.100 align:start position:0% smart wallet you can deploy contracts that<00:20:10.310> will<00:20:10.430> do<00:20:10.700> throw<00:20:11.330> out<00:20:11.420> an<00:20:11.510> arbitrary<00:20:11.870> bark 00:20:12.100 --> 00:20:12.110 align:start position:0% that will do throw out an arbitrary bark 00:20:12.110 --> 00:20:14.860 align:start position:0% that will do throw out an arbitrary bark byte<00:20:12.440> code<00:20:12.710> and<00:20:12.980> then<00:20:13.250> blow<00:20:13.730> up<00:20:13.760> and<00:20:14.630> then<00:20:14.750> you 00:20:14.860 --> 00:20:14.870 align:start position:0% byte code and then blow up and then you 00:20:14.870 --> 00:20:18.640 align:start position:0% byte code and then blow up and then you can<00:20:15.020> do<00:20:15.200> that<00:20:15.410> at<00:20:15.620> na<00:20:15.890> z<00:20:16.630> to<00:20:17.630> sort<00:20:17.960> so<00:20:18.320> sort<00:20:18.560> of 00:20:18.640 --> 00:20:18.650 align:start position:0% can do that at na z to sort so sort of 00:20:18.650 --> 00:20:20.710 align:start position:0% can do that at na z to sort so sort of having<00:20:18.920> the<00:20:18.980> transaction<00:20:19.610> scripts<00:20:20.180> behavior 00:20:20.710 --> 00:20:20.720 align:start position:0% having the transaction scripts behavior 00:20:20.720 --> 00:20:23.320 align:start position:0% having the transaction scripts behavior it's<00:20:21.500> also<00:20:21.620> really<00:20:21.980> secure<00:20:22.520> because<00:20:23.030> there's 00:20:23.320 --> 00:20:23.330 align:start position:0% it's also really secure because there's 00:20:23.330 --> 00:20:25.870 align:start position:0% it's also really secure because there's no<00:20:23.570> code<00:20:24.170> to<00:20:24.470> hack<00:20:24.620> in<00:20:25.250> between<00:20:25.640> these 00:20:25.870 --> 00:20:25.880 align:start position:0% no code to hack in between these 00:20:25.880 --> 00:20:29.440 align:start position:0% no code to hack in between these transactions<00:20:26.510> it's<00:20:27.110> happy<00:20:27.320> to<00:20:27.470> code<00:20:27.650> so<00:20:28.450> there 00:20:29.440 --> 00:20:29.450 align:start position:0% transactions it's happy to code so there 00:20:29.450 --> 00:20:33.550 align:start position:0% transactions it's happy to code so there is<00:20:29.540> not<00:20:29.750> the<00:20:29.870> same<00:20:30.080> like<00:20:31.240> risk<00:20:32.240> at<00:20:32.510> rest<00:20:32.870> for 00:20:33.550 --> 00:20:33.560 align:start position:0% is not the same like risk at rest for 00:20:33.560 --> 00:20:36.940 align:start position:0% is not the same like risk at rest for your<00:20:33.680> fights<00:20:33.890> and<00:20:34.510> this<00:20:35.510> leads<00:20:35.870> to<00:20:36.080> being<00:20:36.830> able 00:20:36.940 --> 00:20:36.950 align:start position:0% your fights and this leads to being able 00:20:36.950 --> 00:20:38.920 align:start position:0% your fights and this leads to being able to<00:20:37.040> support<00:20:37.190> really<00:20:37.520> user<00:20:38.120> friendly<00:20:38.270> stuff 00:20:38.920 --> 00:20:38.930 align:start position:0% to support really user friendly stuff 00:20:38.930 --> 00:20:42.100 align:start position:0% to support really user friendly stuff where<00:20:39.290> you<00:20:39.800> can<00:20:39.980> do<00:20:40.430> these<00:20:40.670> complex<00:20:41.420> actions 00:20:42.100 --> 00:20:42.110 align:start position:0% where you can do these complex actions 00:20:42.110 --> 00:20:45.640 align:start position:0% where you can do these complex actions in<00:20:42.350> a<00:20:42.440> way<00:20:42.760> that<00:20:43.760> includes<00:20:44.420> conditionals<00:20:45.200> and 00:20:45.640 --> 00:20:45.650 align:start position:0% in a way that includes conditionals and 00:20:45.650 --> 00:20:48.190 align:start position:0% in a way that includes conditionals and atomic<00:20:46.100> operations<00:20:46.850> and<00:20:47.150> all<00:20:47.300> of<00:20:47.420> that<00:20:47.450> and<00:20:47.960> is 00:20:48.190 --> 00:20:48.200 align:start position:0% atomic operations and all of that and is 00:20:48.200 --> 00:20:49.690 align:start position:0% atomic operations and all of that and is only<00:20:48.350> one<00:20:48.620> transaction<00:20:49.250> from<00:20:49.550> the 00:20:49.690 --> 00:20:49.700 align:start position:0% only one transaction from the 00:20:49.700 --> 00:20:52.930 align:start position:0% only one transaction from the perspective<00:20:50.240> of<00:20:50.450> the<00:20:50.630> user<00:20:51.640> forth 00:20:52.930 --> 00:20:52.940 align:start position:0% perspective of the user forth 00:20:52.940 --> 00:20:55.870 align:start position:0% perspective of the user forth you<00:20:53.420> can't<00:20:53.570> organize<00:20:53.870> accounts<00:20:54.440> this<00:20:54.860> way<00:20:55.310> so 00:20:55.870 --> 00:20:55.880 align:start position:0% you can't organize accounts this way so 00:20:55.880 --> 00:21:00.360 align:start position:0% you can't organize accounts this way so in<00:20:56.720> effect<00:20:57.430> as<00:20:58.430> long<00:20:58.520> as<00:20:58.850> I<00:20:58.940> own<00:20:59.180> the<00:20:59.720> rights<00:20:59.990> to 00:21:00.360 --> 00:21:00.370 align:start position:0% in effect as long as I own the rights to 00:21:00.370 --> 00:21:02.470 align:start position:0% in effect as long as I own the rights to deploy<00:21:01.370> a<00:21:01.430> little<00:21:01.700> ticular<00:21:01.940> address<00:21:02.300> and<00:21:02.450> I 00:21:02.470 --> 00:21:02.480 align:start position:0% deploy a little ticular address and I 00:21:02.480 --> 00:21:04.090 align:start position:0% deploy a little ticular address and I give<00:21:02.660> that<00:21:02.840> to<00:21:02.870> you 00:21:04.090 --> 00:21:04.100 align:start position:0% give that to you 00:21:04.100 --> 00:21:07.800 align:start position:0% give that to you I<00:21:04.160> can<00:21:04.900> reassign<00:21:05.900> controller<00:21:06.380> this<00:21:06.680> stuff<00:21:07.010> and 00:21:07.800 --> 00:21:07.810 align:start position:0% I can reassign controller this stuff and 00:21:07.810 --> 00:21:11.370 align:start position:0% I can reassign controller this stuff and you're<00:21:08.810> not<00:21:08.960> tied<00:21:09.410> in<00:21:09.680> to<00:21:10.280> any<00:21:10.670> particular 00:21:11.370 --> 00:21:11.380 align:start position:0% you're not tied in to any particular 00:21:11.380 --> 00:21:13.750 align:start position:0% you're not tied in to any particular smart<00:21:12.380> wallet<00:21:12.650> implementation<00:21:13.340> or<00:21:13.520> whatever 00:21:13.750 --> 00:21:13.760 align:start position:0% smart wallet implementation or whatever 00:21:13.760 --> 00:21:15.280 align:start position:0% smart wallet implementation or whatever you<00:21:13.970> can<00:21:14.090> put<00:21:14.240> whatever<00:21:14.390> code<00:21:14.720> you<00:21:14.900> want<00:21:15.020> there 00:21:15.280 --> 00:21:15.290 align:start position:0% you can put whatever code you want there 00:21:15.290 --> 00:21:17.530 align:start position:0% you can put whatever code you want there once<00:21:15.470> you<00:21:15.620> want<00:21:15.800> it's<00:21:15.980> your<00:21:16.190> account<00:21:16.490> as<00:21:17.330> long 00:21:17.530 --> 00:21:17.540 align:start position:0% once you want it's your account as long 00:21:17.540 --> 00:21:20.560 align:start position:0% once you want it's your account as long as<00:21:17.660> it<00:21:17.780> can<00:21:17.900> be<00:21:18.020> destroyed<00:21:19.180> so<00:21:20.180> this<00:21:20.330> way<00:21:20.510> you 00:21:20.560 --> 00:21:20.570 align:start position:0% as it can be destroyed so this way you 00:21:20.570 --> 00:21:23.590 align:start position:0% as it can be destroyed so this way you can<00:21:20.690> create<00:21:21.430> portfolios<00:21:22.430> baskets<00:21:23.090> of<00:21:23.240> assets 00:21:23.590 --> 00:21:23.600 align:start position:0% can create portfolios baskets of assets 00:21:23.600 --> 00:21:25.450 align:start position:0% can create portfolios baskets of assets that<00:21:23.810> are<00:21:24.080> to<00:21:24.230> go<00:21:24.380> beyond<00:21:24.680> just<00:21:24.830> like<00:21:25.100> a 00:21:25.450 --> 00:21:25.460 align:start position:0% that are to go beyond just like a 00:21:25.460 --> 00:21:27.250 align:start position:0% that are to go beyond just like a particular<00:21:26.060> in<00:21:26.240> the<00:21:26.330> year<00:21:26.510> see<00:21:26.660> 20<00:21:26.930> years<00:21:26.960> of 00:21:27.250 --> 00:21:27.260 align:start position:0% particular in the year see 20 years of 00:21:27.260 --> 00:21:28.900 align:start position:0% particular in the year see 20 years of 7.1<00:21:27.740> whatever<00:21:28.070> it<00:21:28.220> may<00:21:28.490> be<00:21:28.520> the<00:21:28.640> ownership 00:21:28.900 --> 00:21:28.910 align:start position:0% 7.1 whatever it may be the ownership 00:21:28.910 --> 00:21:31.990 align:start position:0% 7.1 whatever it may be the ownership reputation<00:21:29.780> all<00:21:30.320> of<00:21:30.650> that<00:21:30.880> because<00:21:31.880> the 00:21:31.990 --> 00:21:32.000 align:start position:0% reputation all of that because the 00:21:32.000 --> 00:21:35.770 align:start position:0% reputation all of that because the accounts<00:21:32.420> is<00:21:32.540> the<00:21:32.570> ultimate<00:21:34.600> abstraction<00:21:35.600> for 00:21:35.770 --> 00:21:35.780 align:start position:0% accounts is the ultimate abstraction for 00:21:35.780 --> 00:21:39.730 align:start position:0% accounts is the ultimate abstraction for doing<00:21:36.020> that<00:21:36.170> and<00:21:37.090> it's<00:21:38.090> a<00:21:38.270> like<00:21:39.080> a<00:21:39.110> reliable 00:21:39.730 --> 00:21:39.740 align:start position:0% doing that and it's a like a reliable 00:21:39.740 --> 00:21:41.710 align:start position:0% doing that and it's a like a reliable way<00:21:39.890> to<00:21:39.920> do<00:21:40.160> as<00:21:40.280> a<00:21:40.310> future<00:21:40.760> perfect<00:21:40.970> manners<00:21:41.570> so 00:21:41.710 --> 00:21:41.720 align:start position:0% way to do as a future perfect manners so 00:21:41.720 --> 00:21:44.350 align:start position:0% way to do as a future perfect manners so that<00:21:41.870> if<00:21:41.930> you<00:21:42.020> do<00:21:42.200> need<00:21:42.380> to<00:21:42.410> make<00:21:42.500> changes<00:21:43.360> down 00:21:44.350 --> 00:21:44.360 align:start position:0% that if you do need to make changes down 00:21:44.360 --> 00:21:45.550 align:start position:0% that if you do need to make changes down why<00:21:44.660> you 00:21:45.550 --> 00:21:45.560 align:start position:0% why you 00:21:45.560 --> 00:21:48.310 align:start position:0% why you whatever<00:21:46.220> your<00:21:46.400> tokenize<00:21:46.820> accountants<00:21:47.420> yeah 00:21:48.310 --> 00:21:48.320 align:start position:0% whatever your tokenize accountants yeah 00:21:48.320 --> 00:21:53.140 align:start position:0% whatever your tokenize accountants yeah this<00:21:48.530> is<00:21:48.910> outfit<00:21:49.910> like<00:21:50.420> the<00:21:50.840> this<00:21:51.320> sort<00:21:52.010> of<00:21:52.150> new 00:21:53.140 --> 00:21:53.150 align:start position:0% this is outfit like the this sort of new 00:21:53.150 --> 00:21:56.830 align:start position:0% this is outfit like the this sort of new use<00:21:53.420> cases<00:21:53.750> for<00:21:54.080> this<00:21:54.820> they're<00:21:55.820> weird 00:21:56.830 --> 00:21:56.840 align:start position:0% use cases for this they're weird 00:21:56.840 --> 00:22:00.070 align:start position:0% use cases for this they're weird but<00:21:57.230> if<00:21:57.850> we<00:21:58.850> weren't<00:21:59.090> willing<00:21:59.330> to<00:21:59.480> get<00:21:59.780> weird 00:22:00.070 --> 00:22:00.080 align:start position:0% but if we weren't willing to get weird 00:22:00.080 --> 00:22:02.950 align:start position:0% but if we weren't willing to get weird like<00:22:00.410> what<00:22:00.710> are<00:22:00.800> we<00:22:00.860> doing<00:22:01.250> here<00:22:01.490> this<00:22:01.850> this<00:22:02.810> is 00:22:02.950 --> 00:22:02.960 align:start position:0% like what are we doing here this this is 00:22:02.960 --> 00:22:06.280 align:start position:0% like what are we doing here this this is a<00:22:02.990> theory<00:22:03.380> anyway<00:22:04.130> right<00:22:04.580> so<00:22:05.510> I'll<00:22:05.930> leave<00:22:06.140> you 00:22:06.280 --> 00:22:06.290 align:start position:0% a theory anyway right so I'll leave you 00:22:06.290 --> 00:22:10.600 align:start position:0% a theory anyway right so I'll leave you with<00:22:06.320> a<00:22:06.470> quote<00:22:06.710> on<00:22:07.580> the<00:22:07.760> dark<00:22:07.940> arts<00:22:08.950> and<00:22:09.950> maybe 00:22:10.600 --> 00:22:10.610 align:start position:0% with a quote on the dark arts and maybe 00:22:10.610 --> 00:22:15.820 align:start position:0% with a quote on the dark arts and maybe a<00:22:11.140> slight<00:22:12.140> modification<00:22:13.210> then<00:22:14.210> I<00:22:14.810> think<00:22:15.680> it's 00:22:15.820 --> 00:22:15.830 align:start position:0% a slight modification then I think it's 00:22:15.830 --> 00:22:21.280 align:start position:0% a slight modification then I think it's more<00:22:16.040> applicable<00:22:16.430> to<00:22:16.700> less<00:22:17.420> here<00:22:17.720> and<00:22:20.290> this 00:22:21.280 --> 00:22:21.290 align:start position:0% more applicable to less here and this 00:22:21.290 --> 00:22:23.790 align:start position:0% more applicable to less here and this moves<00:22:22.040> the<00:22:22.130> talk<00:22:22.310> thank<00:22:22.580> you<00:22:22.700> guys<00:22:22.850> very<00:22:23.090> much 00:22:23.790 --> 00:22:23.800 align:start position:0% moves the talk thank you guys very much 00:22:23.800 --> 00:22:32.520 align:start position:0% moves the talk thank you guys very much I'll<00:22:24.800> put<00:22:25.010> up<00:22:25.040> one<00:22:25.640> more<00:22:25.820> time 00:22:32.520 --> 00:22:32.530 align:start position:0% 00:22:32.530 --> 00:22:36.380 align:start position:0% [Applause] 00:22:36.380 --> 00:22:36.390 align:start position:0% 00:22:36.390 --> 00:22:47.620 align:start position:0% [Music] 00:22:47.620 --> 00:22:47.630 align:start position:0% 00:22:47.630 --> 00:22:50.740 align:start position:0% so<00:22:48.380> when<00:22:49.309> you're<00:22:49.490> accessing<00:22:49.970> contract 00:22:50.740 --> 00:22:50.750 align:start position:0% so when you're accessing contract 00:22:50.750 --> 00:22:54.940 align:start position:0% so when you're accessing contract storage<00:22:51.230> there<00:22:51.830> is<00:22:52.130> an<00:22:52.520> extra<00:22:53.380> you<00:22:54.380> have<00:22:54.530> to<00:22:54.650> go 00:22:54.940 --> 00:22:54.950 align:start position:0% storage there is an extra you have to go 00:22:54.950 --> 00:22:57.250 align:start position:0% storage there is an extra you have to go not<00:22:55.220> only<00:22:55.250> to<00:22:55.549> the<00:22:55.730> contractor<00:22:56.510> then<00:22:56.630> you<00:22:56.720> send 00:22:57.250 --> 00:22:57.260 align:start position:0% not only to the contractor then you send 00:22:57.260 --> 00:22:59.980 align:start position:0% not only to the contractor then you send it<00:22:57.380> into<00:22:57.530> that<00:22:57.830> patrician<00:22:58.700> 3<00:22:58.910> as<00:22:59.120> well<00:22:59.360> so 00:22:59.980 --> 00:22:59.990 align:start position:0% it into that patrician 3 as well so 00:22:59.990 --> 00:23:03.100 align:start position:0% it into that patrician 3 as well so there<00:23:00.110> is<00:23:00.289> an<00:23:00.669> overhead<00:23:01.669> on<00:23:02.450> the<00:23:02.510> machine 00:23:03.100 --> 00:23:03.110 align:start position:0% there is an overhead on the machine 00:23:03.110 --> 00:23:07.000 align:start position:0% there is an overhead on the machine level<00:23:03.590> they're<00:23:04.100> doing<00:23:04.340> it<00:23:04.429> that<00:23:04.580> way<00:23:05.530> now<00:23:06.530> is 00:23:07.000 --> 00:23:07.010 align:start position:0% level they're doing it that way now is 00:23:07.010 --> 00:23:10.330 align:start position:0% level they're doing it that way now is it<00:23:07.340> does<00:23:08.210> it<00:23:08.330> make<00:23:08.480> sense<00:23:08.840> that's<00:23:09.620> like<00:23:10.039> a 00:23:10.330 --> 00:23:10.340 align:start position:0% it does it make sense that's like a 00:23:10.340 --> 00:23:12.760 align:start position:0% it does it make sense that's like a preferred<00:23:11.000> storage<00:23:11.419> method<00:23:11.750> I<00:23:11.960> don't<00:23:12.320> know<00:23:12.470> I 00:23:12.760 --> 00:23:12.770 align:start position:0% preferred storage method I don't know I 00:23:12.770 --> 00:23:15.580 align:start position:0% preferred storage method I don't know I think<00:23:12.950> that<00:23:13.250> it<00:23:13.340> might<00:23:13.539> be<00:23:14.539> an<00:23:15.169> indication 00:23:15.580 --> 00:23:15.590 align:start position:0% think that it might be an indication 00:23:15.590 --> 00:23:17.799 align:start position:0% think that it might be an indication that<00:23:15.770> there's<00:23:16.100> more<00:23:16.970> work<00:23:17.030> that<00:23:17.390> needs<00:23:17.510> to<00:23:17.720> be 00:23:17.799 --> 00:23:17.809 align:start position:0% that there's more work that needs to be 00:23:17.809 --> 00:23:21.250 align:start position:0% that there's more work that needs to be done<00:23:18.020> to<00:23:18.370> out<00:23:19.370> and<00:23:19.549> maybe<00:23:19.789> a<00:23:20.210> gas<00:23:20.659> correction 00:23:21.250 --> 00:23:21.260 align:start position:0% done to out and maybe a gas correction 00:23:21.260 --> 00:23:22.840 align:start position:0% done to out and maybe a gas correction and<00:23:21.440> I<00:23:21.500> think<00:23:21.740> that's<00:23:21.890> also<00:23:22.070> important<00:23:22.730> to 00:23:22.840 --> 00:23:22.850 align:start position:0% and I think that's also important to 00:23:22.850 --> 00:23:25.810 align:start position:0% and I think that's also important to bear<00:23:23.030> in<00:23:23.090> mind<00:23:23.240> with<00:23:24.230> if<00:23:24.919> you<00:23:25.039> decide<00:23:25.429> to<00:23:25.640> use 00:23:25.810 --> 00:23:25.820 align:start position:0% bear in mind with if you decide to use 00:23:25.820 --> 00:23:28.149 align:start position:0% bear in mind with if you decide to use one<00:23:26.059> like<00:23:26.780> exotic<00:23:27.169> storage<00:23:27.679> method<00:23:28.010> over 00:23:28.149 --> 00:23:28.159 align:start position:0% one like exotic storage method over 00:23:28.159 --> 00:23:30.220 align:start position:0% one like exotic storage method over another<00:23:28.220> that<00:23:28.700> you<00:23:29.570> should<00:23:29.780> basically 00:23:30.220 --> 00:23:30.230 align:start position:0% another that you should basically 00:23:30.230 --> 00:23:32.470 align:start position:0% another that you should basically anticipate<00:23:30.919> that<00:23:31.100> things<00:23:31.520> might<00:23:31.760> change<00:23:32.120> in 00:23:32.470 --> 00:23:32.480 align:start position:0% anticipate that things might change in 00:23:32.480 --> 00:23:34.240 align:start position:0% anticipate that things might change in terms<00:23:32.659> of<00:23:32.780> gas<00:23:32.929> pricing<00:23:33.409> online<00:23:33.890> and<00:23:34.190> you 00:23:34.240 --> 00:23:34.250 align:start position:0% terms of gas pricing online and you 00:23:34.250 --> 00:23:36.250 align:start position:0% terms of gas pricing online and you might<00:23:34.400> be<00:23:34.549> stuck<00:23:34.820> with<00:23:35.110> something<00:23:36.110> that's 00:23:36.250 --> 00:23:36.260 align:start position:0% might be stuck with something that's 00:23:36.260 --> 00:23:38.919 align:start position:0% might be stuck with something that's really<00:23:36.530> esoteric<00:23:37.070> and<00:23:37.400> out<00:23:37.520> there<00:23:37.820> but<00:23:38.480> as 00:23:38.919 --> 00:23:38.929 align:start position:0% really esoteric and out there but as 00:23:38.929 --> 00:23:40.480 align:start position:0% really esoteric and out there but as long<00:23:39.110> as<00:23:39.140> couple<00:23:39.620> that<00:23:39.740> with<00:23:39.919> good<00:23:40.130> upgrade 00:23:40.480 --> 00:23:40.490 align:start position:0% long as couple that with good upgrade 00:23:40.490 --> 00:23:42.070 align:start position:0% long as couple that with good upgrade ability<00:23:40.580> and<00:23:40.970> then<00:23:41.059> it's<00:23:41.240> maybe<00:23:41.659> not<00:23:41.840> so<00:23:41.960> much 00:23:42.070 --> 00:23:42.080 align:start position:0% ability and then it's maybe not so much 00:23:42.080 --> 00:23:55.350 align:start position:0% ability and then it's maybe not so much an<00:23:42.230> answer<00:23:44.169> yeah 00:23:55.350 --> 00:23:55.360 align:start position:0% 00:23:55.360 --> 00:23:58.870 align:start position:0% to<00:23:56.360> use<00:23:56.510> like<00:23:56.810> this<00:23:57.620> transaction<00:23:58.160> script<00:23:58.670> type 00:23:58.870 --> 00:23:58.880 align:start position:0% to use like this transaction script type 00:23:58.880 --> 00:24:02.890 align:start position:0% to use like this transaction script type functionality<00:24:00.340> so<00:24:01.340> your<00:24:01.610> your<00:24:02.000> right<00:24:02.720> out<00:24:02.870> of 00:24:02.890 --> 00:24:02.900 align:start position:0% functionality so your your right out of 00:24:02.900 --> 00:24:05.830 align:start position:0% functionality so your your right out of the<00:24:03.140> gates<00:24:03.320> you're<00:24:03.590> dealing<00:24:03.920> with<00:24:04.840> 32,000 00:24:05.830 --> 00:24:05.840 align:start position:0% the gates you're dealing with 32,000 00:24:05.840 --> 00:24:08.380 align:start position:0% the gates you're dealing with 32,000 gasp<00:24:05.990> overhead<00:24:06.560> for<00:24:06.920> deployment<00:24:07.610> then<00:24:08.270> you 00:24:08.380 --> 00:24:08.390 align:start position:0% gasp overhead for deployment then you 00:24:08.390 --> 00:24:10.330 align:start position:0% gasp overhead for deployment then you can<00:24:08.570> deduct<00:24:08.870> out<00:24:09.170> the<00:24:09.470> twenty<00:24:09.740> four<00:24:09.920> thousand 00:24:10.330 --> 00:24:10.340 align:start position:0% can deduct out the twenty four thousand 00:24:10.340 --> 00:24:13.390 align:start position:0% can deduct out the twenty four thousand rebate<00:24:10.870> it<00:24:11.870> starts<00:24:12.560> to<00:24:12.680> make<00:24:12.800> a<00:24:12.830> lot<00:24:13.100> more 00:24:13.390 --> 00:24:13.400 align:start position:0% rebate it starts to make a lot more 00:24:13.400 --> 00:24:15.280 align:start position:0% rebate it starts to make a lot more sense<00:24:13.460> as<00:24:13.940> you<00:24:14.120> get<00:24:14.240> into<00:24:14.360> more<00:24:14.480> complex 00:24:15.280 --> 00:24:15.290 align:start position:0% sense as you get into more complex 00:24:15.290 --> 00:24:20.170 align:start position:0% sense as you get into more complex operations<00:24:16.660> and<00:24:18.610> especially<00:24:19.610> stuff<00:24:19.820> it<00:24:20.030> like 00:24:20.170 --> 00:24:20.180 align:start position:0% operations and especially stuff it like 00:24:20.180 --> 00:24:22.760 align:start position:0% operations and especially stuff it like you<00:24:20.300> couldn't<00:24:20.690> go<00:24:20.930> through<00:24:21.200> another 00:24:22.760 --> 00:24:22.770 align:start position:0% you couldn't go through another 00:24:22.770 --> 00:24:24.870 align:start position:0% you couldn't go through another another<00:24:23.770> helper<00:24:24.190> or<00:24:24.340> something<00:24:24.669> that<00:24:24.789> would 00:24:24.870 --> 00:24:24.880 align:start position:0% another helper or something that would 00:24:24.880 --> 00:24:28.080 align:start position:0% another helper or something that would do<00:24:25.090> that<00:24:25.480> matching<00:24:25.900> for<00:24:26.110> you<00:24:26.370> but<00:24:27.370> the<00:24:27.910> big 00:24:28.080 --> 00:24:28.090 align:start position:0% do that matching for you but the big 00:24:28.090 --> 00:24:30.750 align:start position:0% do that matching for you but the big thing<00:24:28.120> is<00:24:28.360> most<00:24:28.780> like<00:24:29.320> batch<00:24:29.760> transaction 00:24:30.750 --> 00:24:30.760 align:start position:0% thing is most like batch transaction 00:24:30.760 --> 00:24:32.460 align:start position:0% thing is most like batch transaction type<00:24:31.120> things<00:24:31.390> removal<00:24:31.840> tool<00:24:31.960> calls<00:24:32.260> that 00:24:32.460 --> 00:24:32.470 align:start position:0% type things removal tool calls that 00:24:32.470 --> 00:24:34.680 align:start position:0% type things removal tool calls that don't<00:24:32.679> really<00:24:32.980> have<00:24:33.309> a<00:24:33.549> strong<00:24:33.850> ability<00:24:34.360> to 00:24:34.680 --> 00:24:34.690 align:start position:0% don't really have a strong ability to 00:24:34.690 --> 00:24:37.080 align:start position:0% don't really have a strong ability to hook<00:24:35.169> into<00:24:35.380> conditionals<00:24:35.980> alike<00:24:36.220> both<00:24:36.370> based 00:24:37.080 --> 00:24:37.090 align:start position:0% hook into conditionals alike both based 00:24:37.090 --> 00:24:38.730 align:start position:0% hook into conditionals alike both based on<00:24:37.360> this<00:24:37.630> I'm<00:24:37.809> going<00:24:37.840> to<00:24:38.049> go<00:24:38.289> do<00:24:38.440> this<00:24:38.530> other 00:24:38.730 --> 00:24:38.740 align:start position:0% on this I'm going to go do this other 00:24:38.740 --> 00:24:41.520 align:start position:0% on this I'm going to go do this other thing<00:24:38.860> on<00:24:39.309> this<00:24:39.730> other<00:24:39.850> back<00:24:40.090> this<00:24:40.870> way<00:24:41.080> you 00:24:41.520 --> 00:24:41.530 align:start position:0% thing on this other back this way you 00:24:41.530 --> 00:24:43.620 align:start position:0% thing on this other back this way you can<00:24:41.710> like<00:24:41.980> the<00:24:42.130> sky's<00:24:42.340> the<00:24:42.370> limit<00:24:42.580> and<00:24:43.120> there's 00:24:43.620 --> 00:24:43.630 align:start position:0% can like the sky's the limit and there's 00:24:43.630 --> 00:24:57.090 align:start position:0% can like the sky's the limit and there's also<00:24:43.840> the<00:24:44.020> security<00:24:44.700> consideration<00:24:45.700> of<00:24:56.100> the 00:24:57.090 --> 00:24:57.100 align:start position:0% also the security consideration of the 00:24:57.100 --> 00:24:58.649 align:start position:0% also the security consideration of the KOAT<00:24:57.309> action 00:24:58.649 --> 00:24:58.659 align:start position:0% KOAT action 00:24:58.659 --> 00:25:02.610 align:start position:0% KOAT action yes<00:24:59.049> probably<00:24:59.559> what<00:25:00.070> did<00:25:00.190> you<00:25:00.280> into<00:25:00.490> code<00:25:01.620> so 00:25:02.610 --> 00:25:02.620 align:start position:0% yes probably what did you into code so 00:25:02.620 --> 00:25:05.039 align:start position:0% yes probably what did you into code so you<00:25:02.679> don't<00:25:02.950> change<00:25:03.220> the<00:25:03.669> deployer<00:25:04.000> the<00:25:04.780> salt 00:25:05.039 --> 00:25:05.049 align:start position:0% you don't change the deployer the salt 00:25:05.049 --> 00:25:08.159 align:start position:0% you don't change the deployer the salt or<00:25:05.440> the<00:25:06.309> creation<00:25:06.909> code<00:25:07.150> but<00:25:07.659> the<00:25:07.750> creation 00:25:08.159 --> 00:25:08.169 align:start position:0% or the creation code but the creation 00:25:08.169 --> 00:25:10.350 align:start position:0% or the creation code but the creation code<00:25:08.320> is<00:25:08.530> non-deterministic<00:25:09.460> meaning<00:25:10.150> it's 00:25:10.350 --> 00:25:10.360 align:start position:0% code is non-deterministic meaning it's 00:25:10.360 --> 00:25:12.779 align:start position:0% code is non-deterministic meaning it's fixed<00:25:10.929> creation<00:25:11.409> code<00:25:11.620> but<00:25:12.159> during<00:25:12.730> that 00:25:12.779 --> 00:25:12.789 align:start position:0% fixed creation code but during that 00:25:12.789 --> 00:25:15.169 align:start position:0% fixed creation code but during that creation<00:25:13.360> step<00:25:13.659> rather<00:25:13.900> than<00:25:14.200> a<00:25:14.230> standard 00:25:15.169 --> 00:25:15.179 align:start position:0% creation step rather than a standard 00:25:15.179 --> 00:25:17.460 align:start position:0% creation step rather than a standard like<00:25:16.179> solidity<00:25:16.630> and<00:25:16.750> employment<00:25:17.320> that's 00:25:17.460 --> 00:25:17.470 align:start position:0% like solidity and employment that's 00:25:17.470 --> 00:25:19.680 align:start position:0% like solidity and employment that's going<00:25:17.679> to<00:25:17.740> basically<00:25:18.280> have<00:25:18.640> the<00:25:19.059> runtime<00:25:19.450> code 00:25:19.680 --> 00:25:19.690 align:start position:0% going to basically have the runtime code 00:25:19.690 --> 00:25:21.419 align:start position:0% going to basically have the runtime code and<00:25:20.140> just<00:25:20.440> copy<00:25:20.650> that<00:25:20.919> over 00:25:21.419 --> 00:25:21.429 align:start position:0% and just copy that over 00:25:21.429 --> 00:25:23.159 align:start position:0% and just copy that over you're<00:25:21.909> going<00:25:22.030> to<00:25:22.090> say<00:25:22.210> oh<00:25:22.240> instead<00:25:22.870> I'm<00:25:23.049> gonna 00:25:23.159 --> 00:25:23.169 align:start position:0% you're going to say oh instead I'm gonna 00:25:23.169 --> 00:25:26.190 align:start position:0% you're going to say oh instead I'm gonna go<00:25:23.409> ask<00:25:23.740> this<00:25:24.130> other<00:25:24.370> contract<00:25:24.970> for<00:25:25.630> their 00:25:26.190 --> 00:25:26.200 align:start position:0% go ask this other contract for their 00:25:26.200 --> 00:25:30.419 align:start position:0% go ask this other contract for their code<00:25:26.559> that<00:25:26.890> they<00:25:27.010> have<00:25:27.250> right<00:25:27.549> now<00:25:29.280> or<00:25:30.280> some 00:25:30.419 --> 00:25:30.429 align:start position:0% code that they have right now or some 00:25:30.429 --> 00:25:32.630 align:start position:0% code that they have right now or some variation 00:25:32.630 --> 00:25:32.640 align:start position:0% variation 00:25:32.640 --> 00:25:36.279 align:start position:0% variation okay<00:25:33.179> last<00:25:33.390> question<00:25:33.779> is<00:25:34.529> the<00:25:34.860> hands<00:25:35.490> of<00:25:35.730> the 00:25:36.279 --> 00:25:36.289 align:start position:0% okay last question is the hands of the 00:25:36.289 --> 00:25:39.860 align:start position:0% okay last question is the hands of the premise<00:25:37.289> contracting<00:25:38.039> to<00:25:38.159> destroy<00:25:38.690> those<00:25:39.690> who 00:25:39.860 --> 00:25:39.870 align:start position:0% premise contracting to destroy those who 00:25:39.870 --> 00:25:41.930 align:start position:0% premise contracting to destroy those who destroy<00:25:40.100> all<00:25:41.100> you<00:25:41.250> have<00:25:41.370> to<00:25:41.460> kind<00:25:41.640> of<00:25:41.700> move<00:25:41.820> it 00:25:41.930 --> 00:25:41.940 align:start position:0% destroy all you have to kind of move it 00:25:41.940 --> 00:25:42.380 align:start position:0% destroy all you have to kind of move it out 00:25:42.380 --> 00:25:42.390 align:start position:0% out 00:25:42.390 --> 00:25:45.169 align:start position:0% out yes<00:25:43.049> so<00:25:43.500> whenever<00:25:44.010> you're<00:25:44.399> self-destructing 00:25:45.169 --> 00:25:45.179 align:start position:0% yes so whenever you're self-destructing 00:25:45.179 --> 00:25:47.480 align:start position:0% yes so whenever you're self-destructing contracts<00:25:45.600> are<00:25:45.720> to<00:25:45.809> be<00:25:45.929> very<00:25:46.039> careful<00:25:47.039> with 00:25:47.480 --> 00:25:47.490 align:start position:0% contracts are to be very careful with 00:25:47.490 --> 00:25:49.519 align:start position:0% contracts are to be very careful with balances<00:25:48.210> token<00:25:48.720> balances<00:25:49.169> aren't<00:25:49.380> good 00:25:49.519 --> 00:25:49.529 align:start position:0% balances token balances aren't good 00:25:49.529 --> 00:25:51.710 align:start position:0% balances token balances aren't good because<00:25:49.860> they<00:25:50.010> live<00:25:50.220> on<00:25:50.519> the<00:25:50.760> tokens<00:25:51.179> right 00:25:51.710 --> 00:25:51.720 align:start position:0% because they live on the tokens right 00:25:51.720 --> 00:25:54.289 align:start position:0% because they live on the tokens right that's<00:25:52.440> not<00:25:53.190> so<00:25:53.399> much<00:25:53.490> of<00:25:53.610> a<00:25:53.669> concern<00:25:53.700> but<00:25:54.179> if 00:25:54.289 --> 00:25:54.299 align:start position:0% that's not so much of a concern but if 00:25:54.299 --> 00:25:57.110 align:start position:0% that's not so much of a concern but if you<00:25:54.360> have<00:25:54.480> either<00:25:54.990> at<00:25:55.890> the<00:25:56.250> contract<00:25:56.789> when 00:25:57.110 --> 00:25:57.120 align:start position:0% you have either at the contract when 00:25:57.120 --> 00:25:59.930 align:start position:0% you have either at the contract when it's<00:25:57.269> destroyed<00:25:57.500> that<00:25:58.500> your<00:25:58.710> ether<00:25:59.039> is<00:25:59.279> burned 00:25:59.930 --> 00:25:59.940 align:start position:0% it's destroyed that your ether is burned 00:25:59.940 --> 00:26:01.639 align:start position:0% it's destroyed that your ether is burned and<00:26:00.179> not<00:26:00.330> like<00:26:00.510> Sentinel<00:26:01.080> address<00:26:01.380> its 00:26:01.639 --> 00:26:01.649 align:start position:0% and not like Sentinel address its 00:26:01.649 --> 00:26:04.389 align:start position:0% and not like Sentinel address its annihilated<00:26:02.519> your<00:26:02.549> body<00:26:03.090> isn't<00:26:03.269> gone 00:26:04.389 --> 00:26:04.399 align:start position:0% annihilated your body isn't gone 00:26:04.399 --> 00:26:08.480 align:start position:0% annihilated your body isn't gone so<00:26:05.600> obviously<00:26:06.600> self-destruct<00:26:07.440> you<00:26:07.889> specify<00:26:08.460> a 00:26:08.480 --> 00:26:08.490 align:start position:0% so obviously self-destruct you specify a 00:26:08.490 --> 00:26:09.529 align:start position:0% so obviously self-destruct you specify a recipient<00:26:08.909> and<00:26:09.090> it<00:26:09.240> will<00:26:09.330> immediately 00:26:09.529 --> 00:26:09.539 align:start position:0% recipient and it will immediately 00:26:09.539 --> 00:26:11.600 align:start position:0% recipient and it will immediately forward<00:26:10.110> the<00:26:10.169> funds<00:26:10.380> to<00:26:10.559> them<00:26:10.710> but<00:26:11.399> if<00:26:11.460> any 00:26:11.600 --> 00:26:11.610 align:start position:0% forward the funds to them but if any 00:26:11.610 --> 00:26:13.129 align:start position:0% forward the funds to them but if any funds<00:26:11.850> make<00:26:12.090> their<00:26:12.240> way<00:26:12.299> back<00:26:12.330> within<00:26:12.899> that 00:26:13.129 --> 00:26:13.139 align:start position:0% funds make their way back within that 00:26:13.139 --> 00:26:14.990 align:start position:0% funds make their way back within that same<00:26:13.409> transaction<00:26:14.039> the<00:26:14.340> contract<00:26:14.820> hasn't 00:26:14.990 --> 00:26:15.000 align:start position:0% same transaction the contract hasn't 00:26:15.000 --> 00:26:17.210 align:start position:0% same transaction the contract hasn't been<00:26:15.240> deleted<00:26:15.690> until<00:26:16.049> the<00:26:16.200> end<00:26:16.470> of<00:26:16.860> the 00:26:17.210 --> 00:26:17.220 align:start position:0% been deleted until the end of the 00:26:17.220 --> 00:26:18.919 align:start position:0% been deleted until the end of the transaction<00:26:17.610> at<00:26:18.029> which<00:26:18.149> point<00:26:18.450> it's<00:26:18.809> only 00:26:18.919 --> 00:26:18.929 align:start position:0% transaction at which point it's only 00:26:18.929 --> 00:26:20.690 align:start position:0% transaction at which point it's only been<00:26:19.019> scheduled<00:26:19.529> for<00:26:19.740> donations<00:26:20.220> it's 00:26:20.690 --> 00:26:20.700 align:start position:0% been scheduled for donations it's 00:26:20.700 --> 00:26:22.159 align:start position:0% been scheduled for donations it's another<00:26:20.880> limitation<00:26:21.299> to<00:26:21.510> this<00:26:21.630> is<00:26:21.870> that 00:26:22.159 --> 00:26:22.169 align:start position:0% another limitation to this is that 00:26:22.169 --> 00:26:25.970 align:start position:0% another limitation to this is that you're<00:26:22.620> limited<00:26:23.039> to<00:26:23.279> one<00:26:24.059> redeployed<00:26:24.980> per 00:26:25.970 --> 00:26:25.980 align:start position:0% you're limited to one redeployed per 00:26:25.980 --> 00:26:29.990 align:start position:0% you're limited to one redeployed per transaction<00:26:26.809> that's<00:26:27.809> a<00:26:27.960> pretty<00:26:28.740> extreme<00:26:29.580> case 00:26:29.990 --> 00:26:30.000 align:start position:0% transaction that's a pretty extreme case 00:26:30.000 --> 00:26:31.340 align:start position:0% transaction that's a pretty extreme case that<00:26:30.210> you<00:26:30.330> would<00:26:30.419> be<00:26:30.539> doing<00:26:30.570> multiple<00:26:31.080> redo 00:26:31.340 --> 00:26:31.350 align:start position:0% that you would be doing multiple redo 00:26:31.350 --> 00:26:33.289 align:start position:0% that you would be doing multiple redo poisoning<00:26:31.860> in<00:26:32.100> a<00:26:32.220> single<00:26:32.549> transaction<00:26:32.730> but 00:26:33.289 --> 00:26:33.299 align:start position:0% poisoning in a single transaction but 00:26:33.299 --> 00:26:35.000 align:start position:0% poisoning in a single transaction but that's<00:26:33.929> something<00:26:34.260> to<00:26:34.320> be<00:26:34.440> aware<00:26:34.470> of<00:26:34.679> so 00:26:35.000 --> 00:26:35.010 align:start position:0% that's something to be aware of so 00:26:35.010 --> 00:26:37.879 align:start position:0% that's something to be aware of so there's<00:26:35.190> like<00:26:35.279> a<00:26:35.340> slight<00:26:36.200> additional<00:26:37.200> delight 00:26:37.879 --> 00:26:37.889 align:start position:0% there's like a slight additional delight 00:26:37.889 --> 00:26:42.320 align:start position:0% there's like a slight additional delight with<00:26:38.100> fairness<00:26:39.350> okay<00:26:40.350> I'm<00:26:41.130> happy<00:26:41.519> to<00:26:41.730> chat 00:26:42.320 --> 00:26:42.330 align:start position:0% with fairness okay I'm happy to chat 00:26:42.330 --> 00:26:44.779 align:start position:0% with fairness okay I'm happy to chat Laura<00:26:42.600> take<00:26:43.080> some<00:26:43.289> questions<00:26:43.679> after<00:26:44.429> this<00:26:44.549> but 00:26:44.779 --> 00:26:44.789 align:start position:0% Laura take some questions after this but 00:26:44.789 --> 00:26:47.299 align:start position:0% Laura take some questions after this but thank<00:26:45.090> you<00:26:45.149> guys<00:26:45.210> for<00:26:45.480> being<00:26:45.600> here<00:26:45.870> and<00:26:46.309> go 00:26:47.299 --> 00:26:47.309 align:start position:0% thank you guys for being here and go 00:26:47.309 --> 00:26:55.070 align:start position:0% thank you guys for being here and go teach<00:26:47.549> people<00:26:47.760> about<00:26:47.940> this 00:26:55.070 --> 00:26:55.080 align:start position:0% 00:26:55.080 --> 00:27:01.490 align:start position:0% [Applause] 00:27:01.490 --> 00:27:01.500 align:start position:0% 00:27:01.500 --> 00:27:03.560 align:start position:0% you