WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:14.940 align:start position:0% [Music] 00:00:14.940 --> 00:00:14.950 align:start position:0% [Music] 00:00:14.950 --> 00:00:21.220 align:start position:0% [Music] let's<00:00:15.950> see<00:00:16.280> hello<00:00:16.850> everybody<00:00:18.460> I'm<00:00:19.460> Piper<00:00:20.230> I've 00:00:21.220 --> 00:00:21.230 align:start position:0% let's see hello everybody I'm Piper I've 00:00:21.230 --> 00:00:24.130 align:start position:0% let's see hello everybody I'm Piper I've been<00:00:21.740> working<00:00:22.400> on<00:00:22.730> a<00:00:22.790> lot<00:00:23.390> of<00:00:23.540> things<00:00:23.780> in<00:00:24.020> the 00:00:24.130 --> 00:00:24.140 align:start position:0% been working on a lot of things in the 00:00:24.140 --> 00:00:26.140 align:start position:0% been working on a lot of things in the etherium<00:00:24.530> ecosystem<00:00:25.160> since<00:00:25.580> the<00:00:25.760> frontier 00:00:26.140 --> 00:00:26.150 align:start position:0% etherium ecosystem since the frontier 00:00:26.150 --> 00:00:29.410 align:start position:0% etherium ecosystem since the frontier network<00:00:26.420> launched<00:00:26.810> and<00:00:27.080> today<00:00:28.010> today<00:00:28.970> I<00:00:29.000> would 00:00:29.410 --> 00:00:29.420 align:start position:0% network launched and today today I would 00:00:29.420 --> 00:00:31.090 align:start position:0% network launched and today today I would like<00:00:29.540> to<00:00:29.660> talk<00:00:29.810> to<00:00:29.930> you<00:00:30.020> about<00:00:30.080> packaging<00:00:30.980> up 00:00:31.090 --> 00:00:31.100 align:start position:0% like to talk to you about packaging up 00:00:31.100 --> 00:00:33.510 align:start position:0% like to talk to you about packaging up smart<00:00:31.400> contracts 00:00:33.510 --> 00:00:33.520 align:start position:0% smart contracts 00:00:33.520 --> 00:00:36.940 align:start position:0% smart contracts so<00:00:34.520> first<00:00:35.180> let's<00:00:35.480> establish<00:00:36.380> what<00:00:36.620> we<00:00:36.650> mean 00:00:36.940 --> 00:00:36.950 align:start position:0% so first let's establish what we mean 00:00:36.950 --> 00:00:39.970 align:start position:0% so first let's establish what we mean when<00:00:37.220> we<00:00:37.400> say<00:00:37.690> package<00:00:38.690> management<00:00:39.110> Thank<00:00:39.860> You 00:00:39.970 --> 00:00:39.980 align:start position:0% when we say package management Thank You 00:00:39.980 --> 00:00:43.510 align:start position:0% when we say package management Thank You Wikipedia<00:00:41.260> package<00:00:42.260> management<00:00:42.590> system<00:00:42.890> is<00:00:43.460> a 00:00:43.510 --> 00:00:43.520 align:start position:0% Wikipedia package management system is a 00:00:43.520 --> 00:00:45.310 align:start position:0% Wikipedia package management system is a collection<00:00:43.970> of<00:00:44.210> software<00:00:44.480> tools<00:00:44.989> that 00:00:45.310 --> 00:00:45.320 align:start position:0% collection of software tools that 00:00:45.320 --> 00:00:47.229 align:start position:0% collection of software tools that automates<00:00:45.980> the<00:00:46.160> process<00:00:46.610> of<00:00:46.850> installing 00:00:47.229 --> 00:00:47.239 align:start position:0% automates the process of installing 00:00:47.239 --> 00:00:49.510 align:start position:0% automates the process of installing upgrading<00:00:48.079> configuring<00:00:48.739> and<00:00:49.010> removing 00:00:49.510 --> 00:00:49.520 align:start position:0% upgrading configuring and removing 00:00:49.520 --> 00:00:52.120 align:start position:0% upgrading configuring and removing computer<00:00:49.880> programs<00:00:50.620> for<00:00:51.620> a<00:00:51.649> computer's 00:00:52.120 --> 00:00:52.130 align:start position:0% computer programs for a computer's 00:00:52.130 --> 00:00:54.540 align:start position:0% computer programs for a computer's operating<00:00:52.310> system<00:00:53.000> in<00:00:53.210> a<00:00:53.300> consistent<00:00:53.870> manner 00:00:54.540 --> 00:00:54.550 align:start position:0% operating system in a consistent manner 00:00:54.550 --> 00:00:56.920 align:start position:0% operating system in a consistent manner hopefully<00:00:55.550> that's<00:00:55.790> the<00:00:55.880> last<00:00:56.180> reading<00:00:56.600> from 00:00:56.920 --> 00:00:56.930 align:start position:0% hopefully that's the last reading from 00:00:56.930 --> 00:00:59.799 align:start position:0% hopefully that's the last reading from my<00:00:57.140> slides<00:00:57.500> I<00:00:57.970> want<00:00:58.970> to<00:00:59.059> point<00:00:59.300> out<00:00:59.420> the<00:00:59.570> part 00:00:59.799 --> 00:00:59.809 align:start position:0% my slides I want to point out the part 00:00:59.809 --> 00:01:02.260 align:start position:0% my slides I want to point out the part here<00:01:00.050> that<00:01:00.230> says<00:01:00.469> that<00:01:01.040> it<00:01:01.219> is<00:01:01.250> a<00:01:01.399> system<00:01:02.000> it's 00:01:02.260 --> 00:01:02.270 align:start position:0% here that says that it is a system it's 00:01:02.270 --> 00:01:04.179 align:start position:0% here that says that it is a system it's a<00:01:02.390> collection<00:01:02.870> of<00:01:03.140> software<00:01:03.530> tools<00:01:03.800> so<00:01:04.070> we're 00:01:04.179 --> 00:01:04.189 align:start position:0% a collection of software tools so we're 00:01:04.189 --> 00:01:06.370 align:start position:0% a collection of software tools so we're not<00:01:04.309> talking<00:01:04.549> about<00:01:04.579> one<00:01:04.909> thing<00:01:05.380> we're 00:01:06.370 --> 00:01:06.380 align:start position:0% not talking about one thing we're 00:01:06.380 --> 00:01:09.340 align:start position:0% not talking about one thing we're talking<00:01:06.680> about<00:01:07.390> specifications<00:01:08.390> and<00:01:08.840> tooling 00:01:09.340 --> 00:01:09.350 align:start position:0% talking about specifications and tooling 00:01:09.350 --> 00:01:11.289 align:start position:0% talking about specifications and tooling support<00:01:09.590> and<00:01:10.220> all<00:01:10.430> of<00:01:10.580> these<00:01:10.700> things<00:01:10.940> coming 00:01:11.289 --> 00:01:11.299 align:start position:0% support and all of these things coming 00:01:11.299 --> 00:01:14.020 align:start position:0% support and all of these things coming together<00:01:11.479> to<00:01:12.470> allow<00:01:12.770> us<00:01:12.950> to<00:01:13.100> package<00:01:13.370> up<00:01:13.820> a 00:01:14.020 --> 00:01:14.030 align:start position:0% together to allow us to package up a 00:01:14.030 --> 00:01:17.950 align:start position:0% together to allow us to package up a smart<00:01:14.390> contract<00:01:14.540> system<00:01:16.270> so<00:01:17.270> let's<00:01:17.750> take<00:01:17.930> a 00:01:17.950 --> 00:01:17.960 align:start position:0% smart contract system so let's take a 00:01:17.960 --> 00:01:19.870 align:start position:0% smart contract system so let's take a look<00:01:18.200> at<00:01:18.290> what<00:01:18.500> a<00:01:18.710> smart<00:01:19.100> contract<00:01:19.280> package 00:01:19.870 --> 00:01:19.880 align:start position:0% look at what a smart contract package 00:01:19.880 --> 00:01:24.340 align:start position:0% look at what a smart contract package actually<00:01:20.060> is<00:01:22.600> so<00:01:23.600> at<00:01:23.690> the<00:01:23.780> beginning<00:01:24.049> of<00:01:24.200> this 00:01:24.340 --> 00:01:24.350 align:start position:0% actually is so at the beginning of this 00:01:24.350 --> 00:01:26.469 align:start position:0% actually is so at the beginning of this year<00:01:24.619> myself<00:01:25.280> and<00:01:25.670> a<00:01:25.970> number<00:01:26.150> of<00:01:26.299> other 00:01:26.469 --> 00:01:26.479 align:start position:0% year myself and a number of other 00:01:26.479 --> 00:01:28.560 align:start position:0% year myself and a number of other framework<00:01:26.990> developers<00:01:27.530> came<00:01:27.710> together<00:01:27.920> and 00:01:28.560 --> 00:01:28.570 align:start position:0% framework developers came together and 00:01:28.570 --> 00:01:32.620 align:start position:0% framework developers came together and we<00:01:29.570> hashed<00:01:30.200> out<00:01:30.470> what<00:01:30.979> is<00:01:31.310> referred<00:01:31.880> to<00:01:31.939> as<00:01:32.180> ERC 00:01:32.620 --> 00:01:32.630 align:start position:0% we hashed out what is referred to as ERC 00:01:32.630 --> 00:01:36.490 align:start position:0% we hashed out what is referred to as ERC 190<00:01:33.260> this<00:01:34.250> is<00:01:34.430> a<00:01:34.460> spec<00:01:35.000> for<00:01:35.600> how<00:01:35.840> smart 00:01:36.490 --> 00:01:36.500 align:start position:0% 190 this is a spec for how smart 00:01:36.500 --> 00:01:38.980 align:start position:0% 190 this is a spec for how smart contracts<00:01:36.920> can<00:01:37.159> be<00:01:37.189> packaged<00:01:37.670> you<00:01:38.600> can<00:01:38.750> find 00:01:38.980 --> 00:01:38.990 align:start position:0% contracts can be packaged you can find 00:01:38.990 --> 00:01:41.500 align:start position:0% contracts can be packaged you can find it<00:01:39.110> in<00:01:39.229> the<00:01:39.380> AP's<00:01:39.830> repo<00:01:40.280> as<00:01:40.640> well<00:01:40.880> as<00:01:41.060> in<00:01:41.270> a 00:01:41.500 --> 00:01:41.510 align:start position:0% it in the AP's repo as well as in a 00:01:41.510 --> 00:01:43.990 align:start position:0% it in the AP's repo as well as in a dedicated<00:01:41.810> get<00:01:42.320> github<00:01:43.280> repo<00:01:43.610> for<00:01:43.790> this 00:01:43.990 --> 00:01:44.000 align:start position:0% dedicated get github repo for this 00:01:44.000 --> 00:01:50.050 align:start position:0% dedicated get github repo for this specification<00:01:46.450> so<00:01:47.710> what<00:01:48.710> Air<00:01:48.890> c90<00:01:49.400> specifies 00:01:50.050 --> 00:01:50.060 align:start position:0% specification so what Air c90 specifies 00:01:50.060 --> 00:01:53.980 align:start position:0% specification so what Air c90 specifies is<00:01:50.450> a<00:01:50.540> format<00:01:51.229> for<00:01:51.259> a<00:01:51.500> JSON<00:01:51.860> document<00:01:52.990> it 00:01:53.980 --> 00:01:53.990 align:start position:0% is a format for a JSON document it 00:01:53.990 --> 00:01:56.710 align:start position:0% is a format for a JSON document it allows<00:01:54.500> for<00:01:55.220> all<00:01:55.790> of<00:01:56.090> the<00:01:56.240> rest<00:01:56.450> of<00:01:56.600> these 00:01:56.710 --> 00:01:56.720 align:start position:0% allows for all of the rest of these 00:01:56.720 --> 00:01:58.330 align:start position:0% allows for all of the rest of these bullet<00:01:57.229> points<00:01:57.259> are<00:01:57.650> effectively<00:01:58.070> the<00:01:58.189> same 00:01:58.330 --> 00:01:58.340 align:start position:0% bullet points are effectively the same 00:01:58.340 --> 00:02:01.060 align:start position:0% bullet points are effectively the same thing<00:01:58.820> it<00:01:59.390> allows<00:01:59.509> for<00:01:59.990> you<00:02:00.439> to<00:02:00.470> create<00:02:01.040> a 00:02:01.060 --> 00:02:01.070 align:start position:0% thing it allows for you to create a 00:02:01.070 --> 00:02:03.210 align:start position:0% thing it allows for you to create a package<00:02:01.310> that<00:02:01.820> allows<00:02:02.420> other<00:02:02.810> people<00:02:02.900> to 00:02:03.210 --> 00:02:03.220 align:start position:0% package that allows other people to 00:02:03.220 --> 00:02:06.310 align:start position:0% package that allows other people to deterministically<00:02:04.540> rebuild<00:02:05.540> the<00:02:05.900> assets 00:02:06.310 --> 00:02:06.320 align:start position:0% deterministically rebuild the assets 00:02:06.320 --> 00:02:09.339 align:start position:0% deterministically rebuild the assets from<00:02:06.470> that<00:02:06.680> package<00:02:06.939> to<00:02:07.939> verify<00:02:08.659> on<00:02:08.989> chain 00:02:09.339 --> 00:02:09.349 align:start position:0% from that package to verify on chain 00:02:09.349 --> 00:02:11.530 align:start position:0% from that package to verify on chain assets<00:02:09.830> or<00:02:10.039> assets<00:02:10.550> that<00:02:10.940> are<00:02:11.030> included<00:02:11.450> in 00:02:11.530 --> 00:02:11.540 align:start position:0% assets or assets that are included in 00:02:11.540 --> 00:02:14.050 align:start position:0% assets or assets that are included in the<00:02:11.660> package<00:02:12.080> and<00:02:12.380> the<00:02:12.980> packages<00:02:13.430> themselves 00:02:14.050 --> 00:02:14.060 align:start position:0% the package and the packages themselves 00:02:14.060 --> 00:02:16.510 align:start position:0% the package and the packages themselves are<00:02:14.209> designed<00:02:14.840> to<00:02:14.989> be<00:02:15.200> immutable<00:02:15.440> which<00:02:16.280> means 00:02:16.510 --> 00:02:16.520 align:start position:0% are designed to be immutable which means 00:02:16.520 --> 00:02:18.190 align:start position:0% are designed to be immutable which means once<00:02:16.760> you<00:02:16.819> have<00:02:17.030> a<00:02:17.060> reference<00:02:17.510> to<00:02:17.720> a<00:02:17.750> package 00:02:18.190 --> 00:02:18.200 align:start position:0% once you have a reference to a package 00:02:18.200 --> 00:02:20.140 align:start position:0% once you have a reference to a package that<00:02:18.800> thing<00:02:19.010> can<00:02:19.190> never<00:02:19.370> change<00:02:19.459> out<00:02:19.940> from 00:02:20.140 --> 00:02:20.150 align:start position:0% that thing can never change out from 00:02:20.150 --> 00:02:24.699 align:start position:0% that thing can never change out from under<00:02:20.360> you<00:02:22.510> package<00:02:23.510> because<00:02:23.720> the<00:02:23.930> packages 00:02:24.699 --> 00:02:24.709 align:start position:0% under you package because the packages 00:02:24.709 --> 00:02:27.400 align:start position:0% under you package because the packages ERC<00:02:25.520> 190<00:02:25.940> packages<00:02:26.450> can<00:02:26.690> include<00:02:26.989> a<00:02:27.080> number<00:02:27.319> of 00:02:27.400 --> 00:02:27.410 align:start position:0% ERC 190 packages can include a number of 00:02:27.410 --> 00:02:30.220 align:start position:0% ERC 190 packages can include a number of things<00:02:28.120> full<00:02:29.120> source<00:02:29.450> code<00:02:29.540> for<00:02:29.930> the<00:02:30.020> source 00:02:30.220 --> 00:02:30.230 align:start position:0% things full source code for the source 00:02:30.230 --> 00:02:36.059 align:start position:0% things full source code for the source files<00:02:32.260> assets<00:02:33.260> that<00:02:33.500> have<00:02:33.620> been<00:02:33.700> precompiled 00:02:36.059 --> 00:02:36.069 align:start position:0% files assets that have been precompiled 00:02:36.069 --> 00:02:39.580 align:start position:0% files assets that have been precompiled ABI<00:02:37.069> for<00:02:37.580> contracts<00:02:38.030> that<00:02:38.209> are<00:02:38.300> included<00:02:38.690> the 00:02:39.580 --> 00:02:39.590 align:start position:0% ABI for contracts that are included the 00:02:39.590 --> 00:02:41.979 align:start position:0% ABI for contracts that are included the addresses<00:02:40.400> of<00:02:40.580> actual<00:02:40.940> deployed<00:02:41.300> assets<00:02:41.780> on 00:02:41.979 --> 00:02:41.989 align:start position:0% addresses of actual deployed assets on 00:02:41.989 --> 00:02:44.979 align:start position:0% addresses of actual deployed assets on the<00:02:42.080> blockchain<00:02:42.620> and<00:02:43.550> as<00:02:44.300> well<00:02:44.510> as<00:02:44.660> sort<00:02:44.900> of 00:02:44.979 --> 00:02:44.989 align:start position:0% the blockchain and as well as sort of 00:02:44.989 --> 00:02:47.170 align:start position:0% the blockchain and as well as sort of nitty-gritty<00:02:45.260> data<00:02:45.860> like<00:02:46.220> link<00:02:46.549> references 00:02:47.170 --> 00:02:47.180 align:start position:0% nitty-gritty data like link references 00:02:47.180 --> 00:02:49.120 align:start position:0% nitty-gritty data like link references when<00:02:47.660> people<00:02:48.380> are<00:02:48.470> using<00:02:48.650> things<00:02:48.980> like 00:02:49.120 --> 00:02:49.130 align:start position:0% when people are using things like 00:02:49.130 --> 00:02:51.940 align:start position:0% when people are using things like libraries<00:02:49.850> from<00:02:50.090> solidity<00:02:50.569> so<00:02:51.560> that<00:02:51.709> you<00:02:51.799> can 00:02:51.940 --> 00:02:51.950 align:start position:0% libraries from solidity so that you can 00:02:51.950 --> 00:02:53.830 align:start position:0% libraries from solidity so that you can actually<00:02:52.100> do<00:02:52.400> verification<00:02:53.090> all<00:02:53.299> the<00:02:53.750> way 00:02:53.830 --> 00:02:53.840 align:start position:0% actually do verification all the way 00:02:53.840 --> 00:02:57.340 align:start position:0% actually do verification all the way down<00:02:54.019> the<00:02:54.200> chain<00:02:55.720> we<00:02:56.720> also<00:02:56.840> covered<00:02:57.230> a<00:02:57.319> number 00:02:57.340 --> 00:02:57.350 align:start position:0% down the chain we also covered a number 00:02:57.350 --> 00:02:59.830 align:start position:0% down the chain we also covered a number of<00:02:57.590> use<00:02:57.799> cases<00:02:58.069> so<00:02:58.700> base<00:02:59.269> things<00:02:59.630> like 00:02:59.830 --> 00:02:59.840 align:start position:0% of use cases so base things like 00:02:59.840 --> 00:03:01.960 align:start position:0% of use cases so base things like reusable<00:03:00.440> contracts<00:03:00.950> you<00:03:01.250> can<00:03:01.400> think<00:03:01.640> of<00:03:01.760> like 00:03:01.960 --> 00:03:01.970 align:start position:0% reusable contracts you can think of like 00:03:01.970 --> 00:03:05.170 align:start position:0% reusable contracts you can think of like the<00:03:02.690> ERC<00:03:03.049> 20<00:03:03.500> contracts<00:03:04.040> that<00:03:04.400> ship<00:03:04.760> with<00:03:05.060> the 00:03:05.170 --> 00:03:05.180 align:start position:0% the ERC 20 contracts that ship with the 00:03:05.180 --> 00:03:09.789 align:start position:0% the ERC 20 contracts that ship with the Zeppelin<00:03:05.599> OS<00:03:07.299> sort<00:03:08.299> of<00:03:08.420> normal<00:03:09.349> common 00:03:09.789 --> 00:03:09.799 align:start position:0% Zeppelin OS sort of normal common 00:03:09.799 --> 00:03:12.339 align:start position:0% Zeppelin OS sort of normal common patterns<00:03:10.160> like<00:03:10.370> the<00:03:10.519> owned<00:03:10.700> pattern<00:03:11.360> as<00:03:12.110> well 00:03:12.339 --> 00:03:12.349 align:start position:0% patterns like the owned pattern as well 00:03:12.349 --> 00:03:15.539 align:start position:0% patterns like the owned pattern as well as<00:03:12.530> live<00:03:12.769> contracts<00:03:13.459> deployed<00:03:14.450> instances 00:03:15.539 --> 00:03:15.549 align:start position:0% as live contracts deployed instances 00:03:15.549 --> 00:03:19.840 align:start position:0% as live contracts deployed instances things<00:03:16.549> like<00:03:16.700> that<00:03:17.980> we<00:03:18.980> also<00:03:19.280> made<00:03:19.640> sure<00:03:19.670> that 00:03:19.840 --> 00:03:19.850 align:start position:0% things like that we also made sure that 00:03:19.850 --> 00:03:22.960 align:start position:0% things like that we also made sure that we<00:03:20.060> covered<00:03:20.420> both<00:03:20.780> the<00:03:21.739> theory<00:03:22.430> of<00:03:22.519> main<00:03:22.730> net 00:03:22.960 --> 00:03:22.970 align:start position:0% we covered both the theory of main net 00:03:22.970 --> 00:03:25.780 align:start position:0% we covered both the theory of main net case<00:03:23.299> which<00:03:24.109> is<00:03:24.290> a<00:03:24.650> place<00:03:25.100> where<00:03:25.370> we<00:03:25.519> don't 00:03:25.780 --> 00:03:25.790 align:start position:0% case which is a place where we don't 00:03:25.790 --> 00:03:27.670 align:start position:0% case which is a place where we don't want<00:03:25.940> to<00:03:26.000> have<00:03:26.120> to<00:03:26.269> trust<00:03:26.480> things<00:03:26.780> and<00:03:27.140> we<00:03:27.350> want 00:03:27.670 --> 00:03:27.680 align:start position:0% want to have to trust things and we want 00:03:27.680 --> 00:03:29.979 align:start position:0% want to have to trust things and we want to<00:03:27.859> be<00:03:27.980> able<00:03:28.070> to<00:03:28.220> verify<00:03:28.400> everything<00:03:28.850> as<00:03:29.780> well 00:03:29.979 --> 00:03:29.989 align:start position:0% to be able to verify everything as well 00:03:29.989 --> 00:03:34.870 align:start position:0% to be able to verify everything as well as<00:03:30.109> stuff<00:03:30.319> for<00:03:32.109> private<00:03:33.109> chains<00:03:33.609> places<00:03:34.609> where 00:03:34.870 --> 00:03:34.880 align:start position:0% as stuff for private chains places where 00:03:34.880 --> 00:03:36.729 align:start position:0% as stuff for private chains places where you're<00:03:35.390> working<00:03:35.840> in<00:03:36.019> an<00:03:36.140> environment<00:03:36.290> where 00:03:36.729 --> 00:03:36.739 align:start position:0% you're working in an environment where 00:03:36.739 --> 00:03:39.190 align:start position:0% you're working in an environment where Trust<00:03:37.010> is<00:03:37.190> okay<00:03:37.549> where<00:03:38.420> potentially<00:03:39.049> the 00:03:39.190 --> 00:03:39.200 align:start position:0% Trust is okay where potentially the 00:03:39.200 --> 00:03:41.680 align:start position:0% Trust is okay where potentially the packages<00:03:39.709> that<00:03:39.980> you're<00:03:40.160> using<00:03:40.579> are<00:03:40.970> all<00:03:41.390> made 00:03:41.680 --> 00:03:41.690 align:start position:0% packages that you're using are all made 00:03:41.690 --> 00:03:44.110 align:start position:0% packages that you're using are all made by<00:03:41.900> you<00:03:41.959> so<00:03:42.530> you<00:03:42.590> are<00:03:42.950> happy<00:03:43.280> to<00:03:43.489> just<00:03:43.760> trust 00:03:44.110 --> 00:03:44.120 align:start position:0% by you so you are happy to just trust 00:03:44.120 --> 00:03:46.059 align:start position:0% by you so you are happy to just trust embedded<00:03:44.810> byte<00:03:45.019> code<00:03:45.260> in<00:03:45.410> them<00:03:45.590> rather<00:03:45.829> than 00:03:46.059 --> 00:03:46.069 align:start position:0% embedded byte code in them rather than 00:03:46.069 --> 00:03:49.390 align:start position:0% embedded byte code in them rather than verifying<00:03:46.760> that<00:03:47.060> that<00:03:47.870> matches<00:03:48.260> the<00:03:48.530> source 00:03:49.390 --> 00:03:49.400 align:start position:0% verifying that that matches the source 00:03:49.400 --> 00:03:52.870 align:start position:0% verifying that that matches the source code<00:03:50.410> so<00:03:51.410> let's<00:03:51.709> look<00:03:51.980> at<00:03:52.069> some<00:03:52.220> examples<00:03:52.670> of 00:03:52.870 --> 00:03:52.880 align:start position:0% code so let's look at some examples of 00:03:52.880 --> 00:03:54.370 align:start position:0% code so let's look at some examples of what<00:03:53.150> a<00:03:53.180> smart<00:03:53.540> contract<00:03:53.690> package<00:03:54.230> actually 00:03:54.370 --> 00:03:54.380 align:start position:0% what a smart contract package actually 00:03:54.380 --> 00:03:57.640 align:start position:0% what a smart contract package actually looks<00:03:54.769> like<00:03:55.900> this<00:03:56.900> should<00:03:57.019> be<00:03:57.139> familiar<00:03:57.590> to 00:03:57.640 --> 00:03:57.650 align:start position:0% looks like this should be familiar to 00:03:57.650 --> 00:03:59.830 align:start position:0% looks like this should be familiar to anybody<00:03:58.040> who's<00:03:58.370> worked<00:03:58.579> in<00:03:58.700> solidity<00:03:59.120> this<00:03:59.660> is 00:03:59.830 --> 00:03:59.840 align:start position:0% anybody who's worked in solidity this is 00:03:59.840 --> 00:04:03.460 align:start position:0% anybody who's worked in solidity this is a<00:03:59.870> very<00:04:00.290> standard<00:04:00.680> pattern<00:04:01.810> I'm<00:04:02.810> sure<00:04:03.260> that 00:04:03.460 --> 00:04:03.470 align:start position:0% a very standard pattern I'm sure that 00:04:03.470 --> 00:04:06.370 align:start position:0% a very standard pattern I'm sure that you<00:04:03.950> can<00:04:04.130> find<00:04:04.430> almost<00:04:04.850> this<00:04:05.389> exact<00:04:05.780> contract 00:04:06.370 --> 00:04:06.380 align:start position:0% you can find almost this exact contract 00:04:06.380 --> 00:04:10.690 align:start position:0% you can find almost this exact contract in<00:04:06.620> hundreds<00:04:07.370> of<00:04:07.519> different<00:04:07.670> code<00:04:08.299> bases<00:04:09.700> so 00:04:10.690 --> 00:04:10.700 align:start position:0% in hundreds of different code bases so 00:04:10.700 --> 00:04:13.140 align:start position:0% in hundreds of different code bases so this<00:04:11.030> is<00:04:11.209> what<00:04:11.420> I<00:04:11.450> call<00:04:12.170> an<00:04:12.380> inheritable 00:04:13.140 --> 00:04:13.150 align:start position:0% this is what I call an inheritable 00:04:13.150 --> 00:04:15.550 align:start position:0% this is what I call an inheritable contract<00:04:14.150> this<00:04:14.870> contract<00:04:15.230> is<00:04:15.290> not<00:04:15.350> really 00:04:15.550 --> 00:04:15.560 align:start position:0% contract this contract is not really 00:04:15.560 --> 00:04:18.490 align:start position:0% contract this contract is not really useful<00:04:15.709> on<00:04:16.010> its<00:04:16.190> own<00:04:16.430> but<00:04:17.269> it<00:04:17.810> is<00:04:17.930> useful<00:04:18.139> when 00:04:18.490 --> 00:04:18.500 align:start position:0% useful on its own but it is useful when 00:04:18.500 --> 00:04:20.740 align:start position:0% useful on its own but it is useful when when<00:04:18.889> you<00:04:19.039> when<00:04:19.400> you<00:04:19.519> inherit<00:04:20.030> from<00:04:20.389> it<00:04:20.570> and 00:04:20.740 --> 00:04:20.750 align:start position:0% when you when you inherit from it and 00:04:20.750 --> 00:04:24.460 align:start position:0% when you when you inherit from it and make<00:04:20.930> use<00:04:21.109> of<00:04:21.139> some<00:04:21.470> of<00:04:21.500> these<00:04:21.769> modifiers<00:04:23.470> this 00:04:24.460 --> 00:04:24.470 align:start position:0% make use of some of these modifiers this 00:04:24.470 --> 00:04:26.260 align:start position:0% make use of some of these modifiers this is<00:04:24.710> a<00:04:24.740> very<00:04:25.220> simple<00:04:25.610> version<00:04:25.760> of<00:04:26.030> what<00:04:26.150> this 00:04:26.260 --> 00:04:26.270 align:start position:0% is a very simple version of what this 00:04:26.270 --> 00:04:27.760 align:start position:0% is a very simple version of what this package<00:04:26.630> looks<00:04:26.870> like 00:04:27.760 --> 00:04:27.770 align:start position:0% package looks like 00:04:27.770 --> 00:04:29.830 align:start position:0% package looks like is<00:04:27.860> a<00:04:28.009> JSON<00:04:28.370> document<00:04:28.400> it<00:04:29.090> defines<00:04:29.419> a<00:04:29.539> couple 00:04:29.830 --> 00:04:29.840 align:start position:0% is a JSON document it defines a couple 00:04:29.840 --> 00:04:32.110 align:start position:0% is a JSON document it defines a couple of<00:04:29.930> bits<00:04:30.080> of<00:04:30.229> metadata<00:04:30.620> and<00:04:30.919> it<00:04:31.550> uses<00:04:31.759> a 00:04:32.110 --> 00:04:32.120 align:start position:0% of bits of metadata and it uses a 00:04:32.120 --> 00:04:35.740 align:start position:0% of bits of metadata and it uses a content<00:04:32.840> addressable<00:04:33.020> URI<00:04:33.620> an<00:04:34.039> IP<00:04:34.310> FS<00:04:34.699> URI<00:04:35.060> to 00:04:35.740 --> 00:04:35.750 align:start position:0% content addressable URI an IP FS URI to 00:04:35.750 --> 00:04:40.570 align:start position:0% content addressable URI an IP FS URI to reference<00:04:36.259> the<00:04:36.620> actual<00:04:37.220> source<00:04:37.460> code<00:04:39.580> and 00:04:40.570 --> 00:04:40.580 align:start position:0% reference the actual source code and 00:04:40.580 --> 00:04:43.899 align:start position:0% reference the actual source code and then<00:04:41.509> if<00:04:41.810> you<00:04:42.050> pipe<00:04:42.289> that<00:04:42.889> lock<00:04:43.159> file<00:04:43.460> from<00:04:43.789> the 00:04:43.899 --> 00:04:43.909 align:start position:0% then if you pipe that lock file from the 00:04:43.909 --> 00:04:46.059 align:start position:0% then if you pipe that lock file from the previous<00:04:43.940> version<00:04:44.690> by<00:04:45.259> the<00:04:45.289> way<00:04:45.470> IU<00:04:45.650> we<00:04:45.919> use 00:04:46.059 --> 00:04:46.069 align:start position:0% previous version by the way IU we use 00:04:46.069 --> 00:04:47.649 align:start position:0% previous version by the way IU we use the<00:04:46.250> term<00:04:46.430> lock<00:04:46.639> file<00:04:46.940> it's<00:04:47.300> roughly 00:04:47.649 --> 00:04:47.659 align:start position:0% the term lock file it's roughly 00:04:47.659 --> 00:04:51.309 align:start position:0% the term lock file it's roughly interchangeable<00:04:48.319> with<00:04:48.470> package<00:04:49.780> then<00:04:50.780> this 00:04:51.309 --> 00:04:51.319 align:start position:0% interchangeable with package then this 00:04:51.319 --> 00:04:54.339 align:start position:0% interchangeable with package then this right<00:04:51.650> here<00:04:51.710> is<00:04:52.099> the<00:04:52.280> actual<00:04:52.610> IP<00:04:53.030> FS<00:04:53.449> URI<00:04:53.750> for 00:04:54.339 --> 00:04:54.349 align:start position:0% right here is the actual IP FS URI for 00:04:54.349 --> 00:04:57.100 align:start position:0% right here is the actual IP FS URI for that<00:04:54.500> package<00:04:54.770> and<00:04:55.220> in<00:04:55.970> theory<00:04:56.300> with<00:04:57.080> a 00:04:57.100 --> 00:04:57.110 align:start position:0% that package and in theory with a 00:04:57.110 --> 00:05:00.219 align:start position:0% that package and in theory with a supporting<00:04:58.000> development<00:04:59.000> tool<00:04:59.240> you<00:04:59.840> can<00:04:59.990> take 00:05:00.219 --> 00:05:00.229 align:start position:0% supporting development tool you can take 00:05:00.229 --> 00:05:02.200 align:start position:0% supporting development tool you can take this<00:05:00.440> and<00:05:00.710> use<00:05:00.919> it<00:05:00.949> to<00:05:01.220> install<00:05:01.490> the<00:05:02.000> owned 00:05:02.200 --> 00:05:02.210 align:start position:0% this and use it to install the owned 00:05:02.210 --> 00:05:08.020 align:start position:0% this and use it to install the owned package<00:05:03.520> now<00:05:04.520> that's<00:05:04.849> a<00:05:05.210> very<00:05:05.720> ugly<00:05:07.030> reference 00:05:08.020 --> 00:05:08.030 align:start position:0% package now that's a very ugly reference 00:05:08.030 --> 00:05:11.890 align:start position:0% package now that's a very ugly reference to<00:05:08.270> own<00:05:08.449> it's<00:05:09.050> not<00:05:09.110> a<00:05:09.229> very<00:05:09.470> nice<00:05:09.650> URL<00:05:10.840> way<00:05:11.840> to 00:05:11.890 --> 00:05:11.900 align:start position:0% to own it's not a very nice URL way to 00:05:11.900 --> 00:05:13.480 align:start position:0% to own it's not a very nice URL way to install<00:05:12.440> things<00:05:12.650> so<00:05:12.889> we'll<00:05:13.039> talk<00:05:13.190> about<00:05:13.250> that 00:05:13.480 --> 00:05:13.490 align:start position:0% install things so we'll talk about that 00:05:13.490 --> 00:05:16.570 align:start position:0% install things so we'll talk about that in<00:05:13.639> a<00:05:13.759> little<00:05:13.880> bit<00:05:14.120> here<00:05:14.330> so<00:05:15.190> we<00:05:16.190> have<00:05:16.310> a<00:05:16.340> source 00:05:16.570 --> 00:05:16.580 align:start position:0% in a little bit here so we have a source 00:05:16.580 --> 00:05:18.879 align:start position:0% in a little bit here so we have a source file<00:05:16.849> we<00:05:17.720> have<00:05:17.750> this<00:05:17.930> lock<00:05:18.199> file<00:05:18.470> which<00:05:18.770> you 00:05:18.879 --> 00:05:18.889 align:start position:0% file we have this lock file which you 00:05:18.889 --> 00:05:20.770 align:start position:0% file we have this lock file which you can<00:05:19.009> also<00:05:19.130> think<00:05:19.400> of<00:05:19.460> as<00:05:19.610> a<00:05:19.639> package<00:05:20.090> and<00:05:20.300> then 00:05:20.770 --> 00:05:20.780 align:start position:0% can also think of as a package and then 00:05:20.780 --> 00:05:22.270 align:start position:0% can also think of as a package and then we<00:05:20.930> can<00:05:21.080> reference<00:05:21.259> it<00:05:21.590> using<00:05:21.949> its<00:05:22.130> own 00:05:22.270 --> 00:05:22.280 align:start position:0% we can reference it using its own 00:05:22.280 --> 00:05:27.369 align:start position:0% we can reference it using its own content<00:05:22.789> addressable<00:05:22.969> URI<00:05:25.810> so<00:05:26.810> let's<00:05:27.139> look<00:05:27.229> at 00:05:27.369 --> 00:05:27.379 align:start position:0% content addressable URI so let's look at 00:05:27.379 --> 00:05:29.499 align:start position:0% content addressable URI so let's look at what<00:05:27.560> dependencies<00:05:28.280> look<00:05:28.490> like<00:05:28.699> so<00:05:29.240> we<00:05:29.479> can 00:05:29.499 --> 00:05:29.509 align:start position:0% what dependencies look like so we can 00:05:29.509 --> 00:05:31.990 align:start position:0% what dependencies look like so we can actually<00:05:29.780> extend<00:05:30.379> the<00:05:30.680> owned<00:05:30.979> concept<00:05:31.819> with 00:05:31.990 --> 00:05:32.000 align:start position:0% actually extend the owned concept with 00:05:32.000 --> 00:05:35.140 align:start position:0% actually extend the owned concept with this<00:05:32.090> transferable<00:05:32.990> contract<00:05:33.500> it<00:05:34.190> depends<00:05:35.030> on 00:05:35.140 --> 00:05:35.150 align:start position:0% this transferable contract it depends on 00:05:35.150 --> 00:05:37.689 align:start position:0% this transferable contract it depends on the<00:05:35.360> previous<00:05:35.599> example<00:05:36.380> and<00:05:37.039> this<00:05:37.370> is<00:05:37.520> what 00:05:37.689 --> 00:05:37.699 align:start position:0% the previous example and this is what 00:05:37.699 --> 00:05:39.189 align:start position:0% the previous example and this is what the<00:05:37.819> lock<00:05:38.000> file<00:05:38.240> is<00:05:38.479> gonna<00:05:38.659> look<00:05:38.840> like<00:05:39.020> for 00:05:39.189 --> 00:05:39.199 align:start position:0% the lock file is gonna look like for 00:05:39.199 --> 00:05:42.459 align:start position:0% the lock file is gonna look like for that<00:05:39.259> package<00:05:39.909> it<00:05:40.909> references<00:05:41.750> the<00:05:42.199> other 00:05:42.459 --> 00:05:42.469 align:start position:0% that package it references the other 00:05:42.469 --> 00:05:45.129 align:start position:0% that package it references the other lock<00:05:42.889> file<00:05:43.190> using<00:05:44.060> the<00:05:44.330> build<00:05:44.509> dependency 00:05:45.129 --> 00:05:45.139 align:start position:0% lock file using the build dependency 00:05:45.139 --> 00:05:50.920 align:start position:0% lock file using the build dependency this<00:05:45.590> build<00:05:45.860> dependencies<00:05:46.250> key<00:05:49.419> which<00:05:50.419> makes 00:05:50.920 --> 00:05:50.930 align:start position:0% this build dependencies key which makes 00:05:50.930 --> 00:05:53.589 align:start position:0% this build dependencies key which makes the<00:05:51.199> the<00:05:51.440> entire<00:05:51.800> dependency<00:05:52.610> tree<00:05:52.909> immutable 00:05:53.589 --> 00:05:53.599 align:start position:0% the the entire dependency tree immutable 00:05:53.599 --> 00:05:55.120 align:start position:0% the the entire dependency tree immutable because<00:05:53.840> everything<00:05:54.349> is<00:05:54.469> using<00:05:54.740> content 00:05:55.120 --> 00:05:55.130 align:start position:0% because everything is using content 00:05:55.130 --> 00:05:58.719 align:start position:0% because everything is using content addressable<00:05:55.370> your<00:05:55.789> eyes<00:05:57.250> we<00:05:58.250> can<00:05:58.370> move<00:05:58.490> on<00:05:58.639> to 00:05:58.719 --> 00:05:58.729 align:start position:0% addressable your eyes we can move on to 00:05:58.729 --> 00:06:00.490 align:start position:0% addressable your eyes we can move on to things<00:05:58.969> like<00:05:59.060> ready-to-use<00:05:59.569> contracts<00:06:00.229> like 00:06:00.490 --> 00:06:00.500 align:start position:0% things like ready-to-use contracts like 00:06:00.500 --> 00:06:02.439 align:start position:0% things like ready-to-use contracts like a<00:06:00.759> ready<00:06:01.759> to<00:06:01.940> go 00:06:02.439 --> 00:06:02.449 align:start position:0% a ready to go 00:06:02.449 --> 00:06:05.379 align:start position:0% a ready to go er<00:06:02.719> C<00:06:02.930> 20<00:06:03.229> contract<00:06:03.740> that<00:06:04.190> can<00:06:04.940> just<00:06:05.120> be<00:06:05.210> used 00:06:05.379 --> 00:06:05.389 align:start position:0% er C 20 contract that can just be used 00:06:05.389 --> 00:06:09.370 align:start position:0% er C 20 contract that can just be used right<00:06:05.630> out<00:06:05.779> of<00:06:05.810> the<00:06:05.960> box<00:06:06.550> here's<00:06:07.550> some<00:06:08.380> we've 00:06:09.370 --> 00:06:09.380 align:start position:0% right out of the box here's some we've 00:06:09.380 --> 00:06:11.439 align:start position:0% right out of the box here's some we've got<00:06:09.590> two<00:06:09.770> source<00:06:10.069> files<00:06:10.340> here<00:06:10.819> that<00:06:10.849> that<00:06:11.300> are 00:06:11.439 --> 00:06:11.449 align:start position:0% got two source files here that that are 00:06:11.449 --> 00:06:15.100 align:start position:0% got two source files here that that are the<00:06:11.740> an<00:06:13.300> abstract<00:06:14.300> version<00:06:14.539> of<00:06:14.810> it<00:06:14.930> and<00:06:15.050> the 00:06:15.100 --> 00:06:15.110 align:start position:0% the an abstract version of it and the 00:06:15.110 --> 00:06:18.159 align:start position:0% the an abstract version of it and the actual<00:06:15.409> implementation<00:06:15.680> and<00:06:16.550> in<00:06:17.449> this<00:06:17.630> one<00:06:17.900> we 00:06:18.159 --> 00:06:18.169 align:start position:0% actual implementation and in this one we 00:06:18.169 --> 00:06:19.600 align:start position:0% actual implementation and in this one we actually<00:06:18.529> include<00:06:18.860> some<00:06:19.039> information<00:06:19.099> about 00:06:19.600 --> 00:06:19.610 align:start position:0% actually include some information about 00:06:19.610 --> 00:06:21.999 align:start position:0% actually include some information about the<00:06:19.789> contract<00:06:20.270> types<00:06:20.539> themselves<00:06:21.259> we<00:06:21.830> say 00:06:21.999 --> 00:06:22.009 align:start position:0% the contract types themselves we say 00:06:22.009 --> 00:06:23.830 align:start position:0% the contract types themselves we say this<00:06:22.190> includes<00:06:22.669> the<00:06:22.909> standard<00:06:23.180> token 00:06:23.830 --> 00:06:23.840 align:start position:0% this includes the standard token 00:06:23.840 --> 00:06:26.019 align:start position:0% this includes the standard token contract<00:06:24.469> there's<00:06:25.219> maybe<00:06:25.550> some<00:06:25.819> meta 00:06:26.019 --> 00:06:26.029 align:start position:0% contract there's maybe some meta 00:06:26.029 --> 00:06:27.820 align:start position:0% contract there's maybe some meta information<00:06:26.659> included<00:06:27.139> with<00:06:27.349> it<00:06:27.529> like<00:06:27.710> the 00:06:27.820 --> 00:06:27.830 align:start position:0% information included with it like the 00:06:27.830 --> 00:06:30.370 align:start position:0% information included with it like the ABI<00:06:28.159> that<00:06:28.610> allows<00:06:28.819> people<00:06:29.090> to<00:06:29.270> use<00:06:29.810> this 00:06:30.370 --> 00:06:30.380 align:start position:0% ABI that allows people to use this 00:06:30.380 --> 00:06:31.809 align:start position:0% ABI that allows people to use this package<00:06:30.620> to<00:06:30.919> interact<00:06:31.250> with<00:06:31.370> it 00:06:31.809 --> 00:06:31.819 align:start position:0% package to interact with it 00:06:31.819 --> 00:06:35.620 align:start position:0% package to interact with it and<00:06:32.919> we<00:06:33.919> can<00:06:34.069> also<00:06:34.219> include<00:06:34.639> bits<00:06:35.360> of<00:06:35.509> extra 00:06:35.620 --> 00:06:35.630 align:start position:0% and we can also include bits of extra 00:06:35.630 --> 00:06:38.200 align:start position:0% and we can also include bits of extra information<00:06:36.349> like<00:06:36.800> the<00:06:37.070> compiled<00:06:37.639> bytecode 00:06:38.200 --> 00:06:38.210 align:start position:0% information like the compiled bytecode 00:06:38.210 --> 00:06:39.969 align:start position:0% information like the compiled bytecode and<00:06:38.479> the<00:06:38.719> information<00:06:39.080> about<00:06:39.380> the<00:06:39.469> compiler 00:06:39.969 --> 00:06:39.979 align:start position:0% and the information about the compiler 00:06:39.979 --> 00:06:41.080 align:start position:0% and the information about the compiler that<00:06:40.009> we<00:06:40.250> used 00:06:41.080 --> 00:06:41.090 align:start position:0% that we used 00:06:41.090 --> 00:06:43.450 align:start position:0% that we used to<00:06:41.210> actually<00:06:41.510> compile<00:06:41.870> this<00:06:42.160> no<00:06:43.160> this<00:06:43.310> is 00:06:43.450 --> 00:06:43.460 align:start position:0% to actually compile this no this is 00:06:43.460 --> 00:06:45.430 align:start position:0% to actually compile this no this is where<00:06:43.699> we<00:06:43.820> get<00:06:43.970> into<00:06:44.090> different<00:06:44.330> use<00:06:44.600> cases<00:06:44.870> if 00:06:45.430 --> 00:06:45.440 align:start position:0% where we get into different use cases if 00:06:45.440 --> 00:06:47.409 align:start position:0% where we get into different use cases if this<00:06:46.130> were<00:06:46.280> a<00:06:46.310> package<00:06:46.610> I<00:06:46.850> was<00:06:46.940> using<00:06:47.150> on<00:06:47.330> the 00:06:47.409 --> 00:06:47.419 align:start position:0% this were a package I was using on the 00:06:47.419 --> 00:06:49.210 align:start position:0% this were a package I was using on the main<00:06:47.630> net<00:06:47.870> then<00:06:48.380> what<00:06:48.590> I'm<00:06:48.680> gonna<00:06:48.800> do<00:06:49.070> is<00:06:49.190> use 00:06:49.210 --> 00:06:49.220 align:start position:0% main net then what I'm gonna do is use 00:06:49.220 --> 00:06:51.700 align:start position:0% main net then what I'm gonna do is use this<00:06:49.729> compiler<00:06:50.240> information<00:06:50.810> to<00:06:51.050> recompile 00:06:51.700 --> 00:06:51.710 align:start position:0% this compiler information to recompile 00:06:51.710 --> 00:06:53.980 align:start position:0% this compiler information to recompile this<00:06:52.070> and<00:06:52.400> verify<00:06:53.180> that<00:06:53.210> the<00:06:53.540> included 00:06:53.980 --> 00:06:53.990 align:start position:0% this and verify that the included 00:06:53.990 --> 00:06:56.200 align:start position:0% this and verify that the included bytecode<00:06:54.410> does<00:06:54.710> in<00:06:54.949> fact<00:06:55.160> match<00:06:55.430> the<00:06:55.850> compiled 00:06:56.200 --> 00:06:56.210 align:start position:0% bytecode does in fact match the compiled 00:06:56.210 --> 00:06:58.689 align:start position:0% bytecode does in fact match the compiled output<00:06:56.419> but<00:06:57.410> in<00:06:57.530> a<00:06:57.620> trusted<00:06:57.979> environment<00:06:58.160> we 00:06:58.689 --> 00:06:58.699 align:start position:0% output but in a trusted environment we 00:06:58.699 --> 00:07:00.580 align:start position:0% output but in a trusted environment we can<00:06:58.790> actually<00:06:59.090> just<00:06:59.240> use<00:06:59.360> the<00:06:59.750> bytecode 00:07:00.580 --> 00:07:00.590 align:start position:0% can actually just use the bytecode 00:07:00.590 --> 00:07:05.860 align:start position:0% can actually just use the bytecode embedded<00:07:01.220> in<00:07:01.340> this<00:07:01.490> in<00:07:01.699> this<00:07:01.970> package<00:07:04.060> cool<00:07:05.060> so 00:07:05.860 --> 00:07:05.870 align:start position:0% embedded in this in this package cool so 00:07:05.870 --> 00:07:07.090 align:start position:0% embedded in this in this package cool so now<00:07:06.020> let's<00:07:06.229> look<00:07:06.290> at<00:07:06.470> what<00:07:06.590> it<00:07:06.680> looks<00:07:06.710> like<00:07:06.979> if 00:07:07.090 --> 00:07:07.100 align:start position:0% now let's look at what it looks like if 00:07:07.100 --> 00:07:08.890 align:start position:0% now let's look at what it looks like if we<00:07:07.130> have<00:07:07.340> a<00:07:07.370> smart<00:07:08.060> contract<00:07:08.240> that's<00:07:08.690> been 00:07:08.890 --> 00:07:08.900 align:start position:0% we have a smart contract that's been 00:07:08.900 --> 00:07:11.830 align:start position:0% we have a smart contract that's been actually<00:07:09.260> deployed<00:07:09.770> to<00:07:10.010> the<00:07:10.100> blockchain<00:07:10.840> so 00:07:11.830 --> 00:07:11.840 align:start position:0% actually deployed to the blockchain so 00:07:11.840 --> 00:07:15.070 align:start position:0% actually deployed to the blockchain so this<00:07:12.290> is<00:07:12.500> a<00:07:12.830> safe<00:07:13.310> math<00:07:13.700> library<00:07:14.419> it<00:07:14.600> does<00:07:14.870> some 00:07:15.070 --> 00:07:15.080 align:start position:0% this is a safe math library it does some 00:07:15.080 --> 00:07:17.860 align:start position:0% this is a safe math library it does some underflow<00:07:15.530> and<00:07:15.700> overflow<00:07:16.700> protection<00:07:17.030> and 00:07:17.860 --> 00:07:17.870 align:start position:0% underflow and overflow protection and 00:07:17.870 --> 00:07:20.350 align:start position:0% underflow and overflow protection and this<00:07:18.800> is<00:07:19.010> what<00:07:19.160> it<00:07:19.250> looks<00:07:19.430> like<00:07:19.520> to<00:07:19.790> package<00:07:20.150> up 00:07:20.350 --> 00:07:20.360 align:start position:0% this is what it looks like to package up 00:07:20.360 --> 00:07:21.969 align:start position:0% this is what it looks like to package up a<00:07:20.510> smart<00:07:21.020> contract<00:07:21.169> that<00:07:21.560> has<00:07:21.710> a<00:07:21.740> live 00:07:21.969 --> 00:07:21.979 align:start position:0% a smart contract that has a live 00:07:21.979 --> 00:07:25.750 align:start position:0% a smart contract that has a live deployment<00:07:22.720> so<00:07:23.720> we<00:07:24.139> have<00:07:24.290> references<00:07:24.860> to<00:07:25.160> you 00:07:25.750 --> 00:07:25.760 align:start position:0% deployment so we have references to you 00:07:25.760 --> 00:07:28.120 align:start position:0% deployment so we have references to you can<00:07:25.910> see<00:07:26.030> this<00:07:26.150> blockchain<00:07:26.780> URI<00:07:27.110> up<00:07:27.380> here<00:07:27.650> this 00:07:28.120 --> 00:07:28.130 align:start position:0% can see this blockchain URI up here this 00:07:28.130 --> 00:07:30.070 align:start position:0% can see this blockchain URI up here this is<00:07:28.250> how<00:07:28.340> we<00:07:28.400> reference<00:07:28.880> what<00:07:29.210> chain<00:07:29.630> this<00:07:29.900> is 00:07:30.070 --> 00:07:30.080 align:start position:0% is how we reference what chain this is 00:07:30.080 --> 00:07:33.510 align:start position:0% is how we reference what chain this is deployed<00:07:30.440> to<00:07:30.680> this<00:07:31.130> is<00:07:31.340> also<00:07:31.520> how<00:07:31.790> we<00:07:32.350> support 00:07:33.510 --> 00:07:33.520 align:start position:0% deployed to this is also how we support 00:07:33.520 --> 00:07:36.610 align:start position:0% deployed to this is also how we support deployments<00:07:34.550> across<00:07:35.060> multiple<00:07:35.479> chains<00:07:35.900> this 00:07:36.610 --> 00:07:36.620 align:start position:0% deployments across multiple chains this 00:07:36.620 --> 00:07:38.440 align:start position:0% deployments across multiple chains this means<00:07:36.860> that<00:07:37.160> we<00:07:37.610> aren't<00:07:38.030> locked<00:07:38.210> into 00:07:38.440 --> 00:07:38.450 align:start position:0% means that we aren't locked into 00:07:38.450 --> 00:07:40.000 align:start position:0% means that we aren't locked into something<00:07:38.750> like<00:07:39.050> just<00:07:39.260> supporting<00:07:39.740> the<00:07:39.830> main 00:07:40.000 --> 00:07:40.010 align:start position:0% something like just supporting the main 00:07:40.010 --> 00:07:43.379 align:start position:0% something like just supporting the main net<00:07:40.280> or<00:07:40.490> just<00:07:41.360> supporting<00:07:41.780> Rob's<00:07:41.990> tenoram 00:07:43.379 --> 00:07:43.389 align:start position:0% net or just supporting Rob's tenoram 00:07:43.389 --> 00:07:46.000 align:start position:0% net or just supporting Rob's tenoram predefined<00:07:44.389> set<00:07:44.660> of<00:07:44.750> them<00:07:44.930> you<00:07:45.560> can<00:07:45.710> use<00:07:45.830> this 00:07:46.000 --> 00:07:46.010 align:start position:0% predefined set of them you can use this 00:07:46.010 --> 00:07:48.400 align:start position:0% predefined set of them you can use this for<00:07:46.310> private<00:07:46.669> blockchains<00:07:46.880> for<00:07:47.690> local<00:07:48.139> test 00:07:48.400 --> 00:07:48.410 align:start position:0% for private blockchains for local test 00:07:48.410 --> 00:07:51.219 align:start position:0% for private blockchains for local test chains<00:07:49.240> anything<00:07:50.240> like<00:07:50.389> that<00:07:50.419> and<00:07:50.780> then 00:07:51.219 --> 00:07:51.229 align:start position:0% chains anything like that and then 00:07:51.229 --> 00:07:52.960 align:start position:0% chains anything like that and then within<00:07:51.500> it<00:07:51.620> we<00:07:51.770> actually<00:07:51.950> get<00:07:52.310> a<00:07:52.340> reference<00:07:52.700> to 00:07:52.960 --> 00:07:52.970 align:start position:0% within it we actually get a reference to 00:07:52.970 --> 00:07:54.790 align:start position:0% within it we actually get a reference to you<00:07:53.270> know<00:07:53.360> which<00:07:53.570> contract<00:07:54.169> did<00:07:54.320> we<00:07:54.410> deploy 00:07:54.790 --> 00:07:54.800 align:start position:0% you know which contract did we deploy 00:07:54.800 --> 00:07:57.279 align:start position:0% you know which contract did we deploy what<00:07:55.669> address<00:07:56.120> can<00:07:56.330> I<00:07:56.389> find<00:07:56.660> it<00:07:56.810> at<00:07:56.960> and<00:07:57.200> then 00:07:57.279 --> 00:07:57.289 align:start position:0% what address can I find it at and then 00:07:57.289 --> 00:07:59.409 align:start position:0% what address can I find it at and then we've<00:07:57.410> got<00:07:57.560> some<00:07:57.620> convenient<00:07:58.370> stuff<00:07:58.729> which 00:07:59.409 --> 00:07:59.419 align:start position:0% we've got some convenient stuff which 00:07:59.419 --> 00:08:02.290 align:start position:0% we've got some convenient stuff which are<00:07:59.660> the<00:08:00.080> transaction<00:08:00.919> that<00:08:01.729> it<00:08:01.820> was<00:08:01.940> deployed 00:08:02.290 --> 00:08:02.300 align:start position:0% are the transaction that it was deployed 00:08:02.300 --> 00:08:04.930 align:start position:0% are the transaction that it was deployed with<00:08:02.650> or<00:08:03.650> the<00:08:03.889> block<00:08:04.160> that<00:08:04.400> it<00:08:04.490> was<00:08:04.580> deployed 00:08:04.930 --> 00:08:04.940 align:start position:0% with or the block that it was deployed 00:08:04.940 --> 00:08:07.060 align:start position:0% with or the block that it was deployed on<00:08:05.150> again<00:08:06.050> these<00:08:06.260> are<00:08:06.380> things<00:08:06.590> that<00:08:06.680> are<00:08:06.860> easy 00:08:07.060 --> 00:08:07.070 align:start position:0% on again these are things that are easy 00:08:07.070 --> 00:08:10.300 align:start position:0% on again these are things that are easy to<00:08:07.190> verify<00:08:07.870> but<00:08:08.870> they're<00:08:09.650> convenient<00:08:10.160> to 00:08:10.300 --> 00:08:10.310 align:start position:0% to verify but they're convenient to 00:08:10.310 --> 00:08:15.159 align:start position:0% to verify but they're convenient to include<00:08:10.610> in<00:08:10.729> the<00:08:10.820> actual<00:08:11.120> package<00:08:12.880> so<00:08:14.169> with 00:08:15.159 --> 00:08:15.169 align:start position:0% include in the actual package so with 00:08:15.169 --> 00:08:17.920 align:start position:0% include in the actual package so with packages<00:08:15.830> we<00:08:16.430> it<00:08:16.970> enables<00:08:17.450> a<00:08:17.539> number<00:08:17.810> of 00:08:17.920 --> 00:08:17.930 align:start position:0% packages we it enables a number of 00:08:17.930 --> 00:08:19.210 align:start position:0% packages we it enables a number of things<00:08:18.139> that<00:08:18.320> we<00:08:18.500> can<00:08:18.650> actually<00:08:18.770> do<00:08:19.070> with 00:08:19.210 --> 00:08:19.220 align:start position:0% things that we can actually do with 00:08:19.220 --> 00:08:21.129 align:start position:0% things that we can actually do with these<00:08:19.370> the<00:08:19.849> most<00:08:20.030> obvious<00:08:20.450> is<00:08:20.570> just<00:08:20.870> using 00:08:21.129 --> 00:08:21.139 align:start position:0% these the most obvious is just using 00:08:21.139 --> 00:08:23.800 align:start position:0% these the most obvious is just using them<00:08:21.410> in<00:08:21.530> our<00:08:21.620> code<00:08:21.860> a<00:08:22.479> tool<00:08:23.479> that<00:08:23.660> supports 00:08:23.800 --> 00:08:23.810 align:start position:0% them in our code a tool that supports 00:08:23.810 --> 00:08:27.070 align:start position:0% them in our code a tool that supports these<00:08:24.260> packages<00:08:24.770> in<00:08:25.010> theory<00:08:25.760> you<00:08:26.330> run<00:08:26.870> some 00:08:27.070 --> 00:08:27.080 align:start position:0% these packages in theory you run some 00:08:27.080 --> 00:08:29.560 align:start position:0% these packages in theory you run some installation<00:08:27.680> command<00:08:28.099> you<00:08:29.090> can<00:08:29.180> see<00:08:29.300> that<00:08:29.450> on 00:08:29.560 --> 00:08:29.570 align:start position:0% installation command you can see that on 00:08:29.570 --> 00:08:31.540 align:start position:0% installation command you can see that on the<00:08:29.660> upper<00:08:29.750> left<00:08:30.139> on<00:08:30.440> the<00:08:30.889> upper<00:08:31.099> right<00:08:31.280> here 00:08:31.540 --> 00:08:31.550 align:start position:0% the upper left on the upper right here 00:08:31.550 --> 00:08:33.399 align:start position:0% the upper left on the upper right here this<00:08:31.760> is<00:08:31.820> what<00:08:32.150> likely<00:08:32.419> results<00:08:32.990> in<00:08:33.080> our<00:08:33.169> file 00:08:33.399 --> 00:08:33.409 align:start position:0% this is what likely results in our file 00:08:33.409 --> 00:08:35.769 align:start position:0% this is what likely results in our file system<00:08:33.789> this<00:08:34.789> should<00:08:34.969> be<00:08:35.089> familiar<00:08:35.330> to<00:08:35.750> people 00:08:35.769 --> 00:08:35.779 align:start position:0% system this should be familiar to people 00:08:35.779 --> 00:08:37.899 align:start position:0% system this should be familiar to people who<00:08:36.110> are<00:08:36.200> used<00:08:36.409> to<00:08:36.529> node<00:08:36.890> development<00:08:37.520> this<00:08:37.760> is 00:08:37.899 --> 00:08:37.909 align:start position:0% who are used to node development this is 00:08:37.909 --> 00:08:40.180 align:start position:0% who are used to node development this is much<00:08:38.120> like<00:08:38.390> the<00:08:38.419> node<00:08:38.779> modules<00:08:39.409> directory<00:08:39.469> and 00:08:40.180 --> 00:08:40.190 align:start position:0% much like the node modules directory and 00:08:40.190 --> 00:08:43.000 align:start position:0% much like the node modules directory and then<00:08:41.120> from<00:08:41.390> within<00:08:41.539> our<00:08:41.839> actual<00:08:42.229> code<00:08:42.529> we<00:08:42.860> can 00:08:43.000 --> 00:08:43.010 align:start position:0% then from within our actual code we can 00:08:43.010 --> 00:08:47.680 align:start position:0% then from within our actual code we can import<00:08:43.339> these<00:08:43.520> and<00:08:43.760> use<00:08:43.909> them<00:08:46.510> but<00:08:47.510> there's 00:08:47.680 --> 00:08:47.690 align:start position:0% import these and use them but there's 00:08:47.690 --> 00:08:48.910 align:start position:0% import these and use them but there's some<00:08:47.810> really<00:08:47.930> cool<00:08:48.170> other<00:08:48.410> things<00:08:48.680> that<00:08:48.860> we 00:08:48.910 --> 00:08:48.920 align:start position:0% some really cool other things that we 00:08:48.920 --> 00:08:51.840 align:start position:0% some really cool other things that we can<00:08:49.040> do<00:08:49.160> so<00:08:49.579> this<00:08:49.790> is<00:08:49.850> the 00:08:51.840 --> 00:08:51.850 align:start position:0% can do so this is the 00:08:51.850 --> 00:08:54.360 align:start position:0% can do so this is the interface<00:08:52.750> from<00:08:53.410> ether<00:08:53.710> scan<00:08:53.980> for<00:08:54.220> how<00:08:54.310> you 00:08:54.360 --> 00:08:54.370 align:start position:0% interface from ether scan for how you 00:08:54.370 --> 00:08:56.940 align:start position:0% interface from ether scan for how you verify<00:08:54.940> contracts<00:08:55.450> and<00:08:55.720> anybody<00:08:56.350> who's<00:08:56.710> ever 00:08:56.940 --> 00:08:56.950 align:start position:0% verify contracts and anybody who's ever 00:08:56.950 --> 00:08:59.220 align:start position:0% verify contracts and anybody who's ever tried<00:08:57.430> to<00:08:57.610> verify<00:08:57.790> a<00:08:58.330> complex<00:08:58.870> set<00:08:59.200> of 00:08:59.220 --> 00:08:59.230 align:start position:0% tried to verify a complex set of 00:08:59.230 --> 00:09:02.070 align:start position:0% tried to verify a complex set of contracts<00:09:00.000> knows<00:09:01.000> some<00:09:01.360> of<00:09:01.480> the<00:09:01.570> pain<00:09:01.750> points 00:09:02.070 --> 00:09:02.080 align:start position:0% contracts knows some of the pain points 00:09:02.080 --> 00:09:04.920 align:start position:0% contracts knows some of the pain points of<00:09:02.200> this<00:09:02.940> you<00:09:03.940> have<00:09:04.030> to<00:09:04.150> munch<00:09:04.390> together<00:09:04.720> all 00:09:04.920 --> 00:09:04.930 align:start position:0% of this you have to munch together all 00:09:04.930 --> 00:09:07.320 align:start position:0% of this you have to munch together all of<00:09:05.050> your<00:09:05.200> source<00:09:05.440> code<00:09:05.710> into<00:09:05.980> one<00:09:06.220> file<00:09:06.550> you've 00:09:07.320 --> 00:09:07.330 align:start position:0% of your source code into one file you've 00:09:07.330 --> 00:09:08.940 align:start position:0% of your source code into one file you've got<00:09:07.510> to<00:09:07.600> pick<00:09:07.750> the<00:09:07.870> exact<00:09:08.200> right<00:09:08.350> compiler 00:09:08.940 --> 00:09:08.950 align:start position:0% got to pick the exact right compiler 00:09:08.950 --> 00:09:10.530 align:start position:0% got to pick the exact right compiler version<00:09:09.220> you've<00:09:09.820> got<00:09:09.940> a<00:09:09.970> reference<00:09:10.180> if<00:09:10.450> you 00:09:10.530 --> 00:09:10.540 align:start position:0% version you've got a reference if you 00:09:10.540 --> 00:09:13.020 align:start position:0% version you've got a reference if you want<00:09:10.720> to<00:09:10.840> verify<00:09:11.500> multiple<00:09:12.340> contracts<00:09:12.910> you've 00:09:13.020 --> 00:09:13.030 align:start position:0% want to verify multiple contracts you've 00:09:13.030 --> 00:09:16.580 align:start position:0% want to verify multiple contracts you've got<00:09:13.180> to<00:09:13.300> go<00:09:13.390> through<00:09:13.420> this<00:09:13.690> multiple<00:09:14.080> times 00:09:16.580 --> 00:09:16.590 align:start position:0% 00:09:16.590 --> 00:09:19.620 align:start position:0% smart<00:09:17.590> contract<00:09:18.010> packages<00:09:18.520> can<00:09:18.970> replace<00:09:19.600> that 00:09:19.620 --> 00:09:19.630 align:start position:0% smart contract packages can replace that 00:09:19.630 --> 00:09:22.160 align:start position:0% smart contract packages can replace that entire<00:09:19.930> thing<00:09:20.170> with<00:09:20.770> just<00:09:20.980> a<00:09:21.070> single<00:09:21.250> upload 00:09:22.160 --> 00:09:22.170 align:start position:0% entire thing with just a single upload 00:09:22.170 --> 00:09:24.360 align:start position:0% entire thing with just a single upload since<00:09:23.170> packages<00:09:23.800> include<00:09:24.100> enough 00:09:24.360 --> 00:09:24.370 align:start position:0% since packages include enough 00:09:24.370 --> 00:09:27.600 align:start position:0% since packages include enough information<00:09:24.430> to<00:09:25.000> verify<00:09:25.270> everything<00:09:26.610> instead 00:09:27.600 --> 00:09:27.610 align:start position:0% information to verify everything instead 00:09:27.610 --> 00:09:29.970 align:start position:0% information to verify everything instead of<00:09:27.700> having<00:09:27.850> to<00:09:28.110> manually<00:09:29.110> put<00:09:29.650> all<00:09:29.800> of<00:09:29.830> that 00:09:29.970 --> 00:09:29.980 align:start position:0% of having to manually put all of that 00:09:29.980 --> 00:09:32.310 align:start position:0% of having to manually put all of that information<00:09:30.220> in<00:09:30.820> you<00:09:31.390> could<00:09:31.570> just<00:09:31.750> upload<00:09:32.170> the 00:09:32.310 --> 00:09:32.320 align:start position:0% information in you could just upload the 00:09:32.320 --> 00:09:33.810 align:start position:0% information in you could just upload the lock<00:09:32.500> file<00:09:32.800> and<00:09:33.130> either<00:09:33.220> scan<00:09:33.580> can 00:09:33.810 --> 00:09:33.820 align:start position:0% lock file and either scan can 00:09:33.820 --> 00:09:36.840 align:start position:0% lock file and either scan can automatically<00:09:34.770> verify<00:09:35.770> every<00:09:36.280> deployed 00:09:36.840 --> 00:09:36.850 align:start position:0% automatically verify every deployed 00:09:36.850 --> 00:09:38.940 align:start position:0% automatically verify every deployed instance<00:09:37.480> of<00:09:37.690> the<00:09:37.930> contract<00:09:38.380> included<00:09:38.830> in 00:09:38.940 --> 00:09:38.950 align:start position:0% instance of the contract included in 00:09:38.950 --> 00:09:42.330 align:start position:0% instance of the contract included in that<00:09:39.100> package<00:09:39.460> I<00:09:40.830> also<00:09:41.830> think<00:09:42.100> that<00:09:42.130> this 00:09:42.330 --> 00:09:42.340 align:start position:0% that package I also think that this 00:09:42.340 --> 00:09:44.790 align:start position:0% that package I also think that this would<00:09:42.520> be<00:09:42.550> useful<00:09:43.000> in<00:09:43.120> wallets<00:09:43.620> this<00:09:44.620> is<00:09:44.740> a 00:09:44.790 --> 00:09:44.800 align:start position:0% would be useful in wallets this is a 00:09:44.800 --> 00:09:48.780 align:start position:0% would be useful in wallets this is a pretty<00:09:44.980> common<00:09:45.490> interface<00:09:46.000> for<00:09:46.780> wallets<00:09:47.790> give 00:09:48.780 --> 00:09:48.790 align:start position:0% pretty common interface for wallets give 00:09:48.790 --> 00:09:50.610 align:start position:0% pretty common interface for wallets give me<00:09:48.970> the<00:09:49.090> contract<00:09:49.300> address<00:09:49.930> tell<00:09:50.230> me<00:09:50.320> what<00:09:50.500> the 00:09:50.610 --> 00:09:50.620 align:start position:0% me the contract address tell me what the 00:09:50.620 --> 00:09:53.100 align:start position:0% me the contract address tell me what the ABI<00:09:50.950> and<00:09:51.460> then<00:09:52.210> I<00:09:52.390> will<00:09:52.540> generate<00:09:52.930> an 00:09:53.100 --> 00:09:53.110 align:start position:0% ABI and then I will generate an 00:09:53.110 --> 00:09:55.460 align:start position:0% ABI and then I will generate an interface<00:09:53.530> and<00:09:53.770> you<00:09:53.830> can<00:09:53.860> interact<00:09:54.160> with<00:09:54.550> it 00:09:55.460 --> 00:09:55.470 align:start position:0% interface and you can interact with it 00:09:55.470 --> 00:09:58.980 align:start position:0% interface and you can interact with it this<00:09:56.470> is<00:09:56.680> often<00:09:57.190> sufficient<00:09:57.700> but<00:09:58.360> it<00:09:58.570> leaves<00:09:58.780> a 00:09:58.980 --> 00:09:58.990 align:start position:0% this is often sufficient but it leaves a 00:09:58.990 --> 00:10:01.080 align:start position:0% this is often sufficient but it leaves a lot<00:09:59.140> of<00:09:59.260> things<00:09:59.800> desired<00:10:00.280> because<00:10:00.820> you<00:10:00.940> don't 00:10:01.080 --> 00:10:01.090 align:start position:0% lot of things desired because you don't 00:10:01.090 --> 00:10:02.580 align:start position:0% lot of things desired because you don't really<00:10:01.210> know<00:10:01.330> what<00:10:01.690> you're<00:10:01.870> interacting<00:10:02.230> with 00:10:02.580 --> 00:10:02.590 align:start position:0% really know what you're interacting with 00:10:02.590 --> 00:10:04.230 align:start position:0% really know what you're interacting with you<00:10:03.250> don't<00:10:03.430> know<00:10:03.520> if<00:10:03.640> it's<00:10:03.760> been<00:10:03.970> verified 00:10:04.230 --> 00:10:04.240 align:start position:0% you don't know if it's been verified 00:10:04.240 --> 00:10:07.380 align:start position:0% you don't know if it's been verified that's<00:10:05.170> sort<00:10:05.380> of<00:10:05.410> sort<00:10:06.250> of<00:10:06.310> thing<00:10:06.490> if<00:10:06.790> we 00:10:07.380 --> 00:10:07.390 align:start position:0% that's sort of sort of thing if we 00:10:07.390 --> 00:10:11.370 align:start position:0% that's sort of sort of thing if we replace<00:10:07.780> this<00:10:08.050> with<00:10:09.420> with<00:10:10.420> a<00:10:10.450> package<00:10:10.930> where 00:10:11.370 --> 00:10:11.380 align:start position:0% replace this with with a package where 00:10:11.380 --> 00:10:14.610 align:start position:0% replace this with with a package where you<00:10:11.440> upload<00:10:11.800> a<00:10:11.920> package<00:10:13.200> wallets<00:10:14.200> can<00:10:14.410> still 00:10:14.610 --> 00:10:14.620 align:start position:0% you upload a package wallets can still 00:10:14.620 --> 00:10:16.800 align:start position:0% you upload a package wallets can still generate<00:10:15.010> the<00:10:15.160> same<00:10:15.400> interface<00:10:15.970> but<00:10:16.630> they<00:10:16.690> can 00:10:16.800 --> 00:10:16.810 align:start position:0% generate the same interface but they can 00:10:16.810 --> 00:10:18.180 align:start position:0% generate the same interface but they can also<00:10:16.930> show<00:10:17.230> you<00:10:17.290> a<00:10:17.410> lot<00:10:17.650> of<00:10:17.680> extra<00:10:18.070> information 00:10:18.180 --> 00:10:18.190 align:start position:0% also show you a lot of extra information 00:10:18.190 --> 00:10:22.050 align:start position:0% also show you a lot of extra information such<00:10:18.790> as<00:10:19.110> yes<00:10:20.110> this<00:10:20.530> does<00:10:20.860> actually<00:10:21.220> verify 00:10:22.050 --> 00:10:22.060 align:start position:0% such as yes this does actually verify 00:10:22.060 --> 00:10:24.690 align:start position:0% such as yes this does actually verify whenever<00:10:22.720> I<00:10:23.040> recompile<00:10:24.040> the<00:10:24.220> source<00:10:24.460> code<00:10:24.670> and 00:10:24.690 --> 00:10:24.700 align:start position:0% whenever I recompile the source code and 00:10:24.700 --> 00:10:27.570 align:start position:0% whenever I recompile the source code and check<00:10:25.030> it<00:10:25.120> against<00:10:25.420> the<00:10:25.510> byte<00:10:25.690> code<00:10:25.890> or<00:10:26.890> or 00:10:27.570 --> 00:10:27.580 align:start position:0% check it against the byte code or or 00:10:27.580 --> 00:10:29.760 align:start position:0% check it against the byte code or or there<00:10:28.360> is<00:10:28.570> not<00:10:28.780> enough<00:10:29.110> information<00:10:29.260> to 00:10:29.760 --> 00:10:29.770 align:start position:0% there is not enough information to 00:10:29.770 --> 00:10:31.620 align:start position:0% there is not enough information to verify<00:10:29.950> this<00:10:30.190> or<00:10:30.580> it<00:10:30.760> can<00:10:30.790> even<00:10:31.120> just<00:10:31.270> let<00:10:31.510> you 00:10:31.620 --> 00:10:31.630 align:start position:0% verify this or it can even just let you 00:10:31.630 --> 00:10:35.340 align:start position:0% verify this or it can even just let you browse<00:10:31.900> the<00:10:32.170> source<00:10:32.410> code<00:10:34.020> but<00:10:35.020> this<00:10:35.200> right 00:10:35.340 --> 00:10:35.350 align:start position:0% browse the source code but this right 00:10:35.350 --> 00:10:38.910 align:start position:0% browse the source code but this right here's<00:10:35.560> my<00:10:35.740> favorite<00:10:35.950> idea<00:10:37.560> come<00:10:38.560> with<00:10:38.680> me<00:10:38.830> on 00:10:38.910 --> 00:10:38.920 align:start position:0% here's my favorite idea come with me on 00:10:38.920 --> 00:10:40.980 align:start position:0% here's my favorite idea come with me on a<00:10:38.950> journey<00:10:39.040> to<00:10:39.400> the<00:10:39.430> future<00:10:39.820> where<00:10:40.150> the<00:10:40.420> EVM<00:10:40.810> is 00:10:40.980 --> 00:10:40.990 align:start position:0% a journey to the future where the EVM is 00:10:40.990 --> 00:10:44.400 align:start position:0% a journey to the future where the EVM is everywhere<00:10:42.450> where<00:10:43.450> there<00:10:43.630> are<00:10:43.660> packages<00:10:44.230> for 00:10:44.400 --> 00:10:44.410 align:start position:0% everywhere where there are packages for 00:10:44.410 --> 00:10:47.760 align:start position:0% everywhere where there are packages for all<00:10:44.530> kinds<00:10:44.890> of<00:10:44.950> things<00:10:45.250> and<00:10:45.990> where<00:10:46.990> the<00:10:47.260> EVM<00:10:47.620> is 00:10:47.760 --> 00:10:47.770 align:start position:0% all kinds of things and where the EVM is 00:10:47.770 --> 00:10:51.960 align:start position:0% all kinds of things and where the EVM is really<00:10:48.130> fast<00:10:49.140> so<00:10:50.140> I<00:10:50.500> think<00:10:50.560> that<00:10:51.010> EVM<00:10:51.400> packages 00:10:51.960 --> 00:10:51.970 align:start position:0% really fast so I think that EVM packages 00:10:51.970 --> 00:10:54.390 align:start position:0% really fast so I think that EVM packages are<00:10:52.270> capable<00:10:52.960> of<00:10:53.110> being<00:10:53.380> a<00:10:53.650> cross<00:10:53.980> language 00:10:54.390 --> 00:10:54.400 align:start position:0% are capable of being a cross language 00:10:54.400 --> 00:10:56.850 align:start position:0% are capable of being a cross language packaging<00:10:55.240> system<00:10:55.660> and<00:10:56.050> what<00:10:56.200> I<00:10:56.230> mean<00:10:56.470> by<00:10:56.530> that 00:10:56.850 --> 00:10:56.860 align:start position:0% packaging system and what I mean by that 00:10:56.860 --> 00:11:00.920 align:start position:0% packaging system and what I mean by that is<00:10:57.100> that<00:10:58.350> we<00:10:59.350> can<00:10:59.380> actually<00:10:59.950> use<00:11:00.220> the<00:11:00.430> EVM 00:11:00.920 --> 00:11:00.930 align:start position:0% is that we can actually use the EVM 00:11:00.930 --> 00:11:03.420 align:start position:0% is that we can actually use the EVM implementation<00:11:01.930> natively<00:11:02.530> in<00:11:02.890> our<00:11:02.980> code<00:11:03.220> this 00:11:03.420 --> 00:11:03.430 align:start position:0% implementation natively in our code this 00:11:03.430 --> 00:11:04.519 align:start position:0% implementation natively in our code this is<00:11:03.580> sort<00:11:03.790> of<00:11:03.850> an<00:11:03.970> imagined 00:11:04.519 --> 00:11:04.529 align:start position:0% is sort of an imagined 00:11:04.529 --> 00:11:08.480 align:start position:0% is sort of an imagined the<00:11:04.620> Python<00:11:04.980> library<00:11:05.220> here<00:11:05.930> that<00:11:07.279> makes<00:11:08.279> use 00:11:08.480 --> 00:11:08.490 align:start position:0% the Python library here that makes use 00:11:08.490 --> 00:11:11.329 align:start position:0% the Python library here that makes use of<00:11:08.519> some<00:11:08.970> mystical<00:11:09.779> sha<00:11:10.110> seven<00:11:10.589> package<00:11:11.069> and 00:11:11.329 --> 00:11:11.339 align:start position:0% of some mystical sha seven package and 00:11:11.339 --> 00:11:13.610 align:start position:0% of some mystical sha seven package and rather<00:11:11.819> than<00:11:12.120> needing<00:11:12.720> and<00:11:12.899> implementation 00:11:13.610 --> 00:11:13.620 align:start position:0% rather than needing and implementation 00:11:13.620 --> 00:11:16.489 align:start position:0% rather than needing and implementation of<00:11:13.860> sha<00:11:14.100> seven<00:11:14.490> and<00:11:14.639> python<00:11:15.029> instead<00:11:15.930> we<00:11:16.230> use 00:11:16.489 --> 00:11:16.499 align:start position:0% of sha seven and python instead we use 00:11:16.499 --> 00:11:19.670 align:start position:0% of sha seven and python instead we use the<00:11:16.800> EVM<00:11:17.220> implementation<00:11:18.060> in<00:11:18.269> our<00:11:18.389> code<00:11:18.660> and<00:11:19.319> I 00:11:19.670 --> 00:11:19.680 align:start position:0% the EVM implementation in our code and I 00:11:19.680 --> 00:11:21.110 align:start position:0% the EVM implementation in our code and I think<00:11:19.860> that's<00:11:20.009> really<00:11:20.249> powerful<00:11:20.430> because 00:11:21.110 --> 00:11:21.120 align:start position:0% think that's really powerful because 00:11:21.120 --> 00:11:24.019 align:start position:0% think that's really powerful because that<00:11:21.449> means<00:11:21.600> that<00:11:21.899> we<00:11:21.990> can<00:11:22.170> have<00:11:22.399> single<00:11:23.399> well 00:11:24.019 --> 00:11:24.029 align:start position:0% that means that we can have single well 00:11:24.029 --> 00:11:26.179 align:start position:0% that means that we can have single well tested<00:11:24.569> battle-tested<00:11:25.199> implementations 00:11:26.179 --> 00:11:26.189 align:start position:0% tested battle-tested implementations 00:11:26.189 --> 00:11:28.280 align:start position:0% tested battle-tested implementations that<00:11:26.490> are<00:11:26.850> then<00:11:27.089> usable<00:11:27.600> across<00:11:27.930> many 00:11:28.280 --> 00:11:28.290 align:start position:0% that are then usable across many 00:11:28.290 --> 00:11:31.999 align:start position:0% that are then usable across many different<00:11:28.529> languages<00:11:30.559> so<00:11:31.559> let's<00:11:31.740> talk<00:11:31.860> about 00:11:31.999 --> 00:11:32.009 align:start position:0% different languages so let's talk about 00:11:32.009 --> 00:11:37.129 align:start position:0% different languages so let's talk about the<00:11:32.160> standard<00:11:32.339> library<00:11:35.300> so<00:11:36.300> to<00:11:36.899> talk<00:11:37.079> about 00:11:37.129 --> 00:11:37.139 align:start position:0% the standard library so to talk about 00:11:37.139 --> 00:11:38.960 align:start position:0% the standard library so to talk about the<00:11:37.410> standard<00:11:37.740> library<00:11:38.160> I<00:11:38.339> actually<00:11:38.610> want<00:11:38.910> to 00:11:38.960 --> 00:11:38.970 align:start position:0% the standard library I actually want to 00:11:38.970 --> 00:11:40.910 align:start position:0% the standard library I actually want to back<00:11:39.149> up<00:11:39.180> and<00:11:39.540> talk<00:11:39.749> about<00:11:39.899> packaged<00:11:40.350> indexes 00:11:40.910 --> 00:11:40.920 align:start position:0% back up and talk about packaged indexes 00:11:40.920 --> 00:11:43.009 align:start position:0% back up and talk about packaged indexes this<00:11:41.399> is<00:11:41.579> sort<00:11:41.819> of<00:11:41.910> the<00:11:42.149> like<00:11:42.360> default<00:11:42.779> state 00:11:43.009 --> 00:11:43.019 align:start position:0% this is sort of the like default state 00:11:43.019 --> 00:11:44.660 align:start position:0% this is sort of the like default state of<00:11:43.170> the<00:11:43.259> world<00:11:43.439> right<00:11:43.709> now<00:11:43.740> is<00:11:44.069> that<00:11:44.220> packaged 00:11:44.660 --> 00:11:44.670 align:start position:0% of the world right now is that packaged 00:11:44.670 --> 00:11:47.090 align:start position:0% of the world right now is that packaged indexes<00:11:45.240> are<00:11:45.480> centralized<00:11:46.019> there's<00:11:46.680> often 00:11:47.090 --> 00:11:47.100 align:start position:0% indexes are centralized there's often 00:11:47.100 --> 00:11:50.030 align:start position:0% indexes are centralized there's often sort<00:11:47.879> of<00:11:47.999> one<00:11:48.300> centralized<00:11:48.959> system<00:11:49.709> that 00:11:50.030 --> 00:11:50.040 align:start position:0% sort of one centralized system that 00:11:50.040 --> 00:11:51.829 align:start position:0% sort of one centralized system that handles<00:11:50.370> all<00:11:50.579> of<00:11:50.639> the<00:11:50.850> packages<00:11:51.509> for<00:11:51.749> an 00:11:51.829 --> 00:11:51.839 align:start position:0% handles all of the packages for an 00:11:51.839 --> 00:11:54.799 align:start position:0% handles all of the packages for an ecosystem<00:11:52.290> we've<00:11:52.800> got<00:11:52.980> NPM<00:11:53.430> we've<00:11:53.759> got<00:11:53.939> pi<00:11:54.149> PI 00:11:54.799 --> 00:11:54.809 align:start position:0% ecosystem we've got NPM we've got pi PI 00:11:54.809 --> 00:11:59.329 align:start position:0% ecosystem we've got NPM we've got pi PI we've<00:11:55.410> got<00:11:55.970> whatever<00:11:56.970> else<00:11:57.389> is<00:11:57.629> out<00:11:57.809> there<00:11:58.339> but 00:11:59.329 --> 00:11:59.339 align:start position:0% we've got whatever else is out there but 00:11:59.339 --> 00:12:01.249 align:start position:0% we've got whatever else is out there but this<00:11:59.579> is<00:11:59.639> what<00:11:59.939> I'd<00:12:00.059> like<00:12:00.240> I'd<00:12:00.449> like<00:12:00.600> everybody 00:12:01.249 --> 00:12:01.259 align:start position:0% this is what I'd like I'd like everybody 00:12:01.259 --> 00:12:02.720 align:start position:0% this is what I'd like I'd like everybody out<00:12:01.470> here<00:12:01.709> to<00:12:01.769> have<00:12:02.009> their<00:12:02.220> own<00:12:02.370> packaged 00:12:02.720 --> 00:12:02.730 align:start position:0% out here to have their own packaged 00:12:02.730 --> 00:12:06.139 align:start position:0% out here to have their own packaged index<00:12:03.139> and<00:12:04.249> that<00:12:05.249> is<00:12:05.459> actually<00:12:05.819> really<00:12:06.029> easy 00:12:06.139 --> 00:12:06.149 align:start position:0% index and that is actually really easy 00:12:06.149 --> 00:12:10.960 align:start position:0% index and that is actually really easy with<00:12:06.629> the<00:12:06.749> ethereum<00:12:07.110> blockchain<00:12:07.939> so<00:12:09.110> with<00:12:10.110> a 00:12:10.960 --> 00:12:10.970 align:start position:0% with the ethereum blockchain so with a 00:12:10.970 --> 00:12:14.269 align:start position:0% with the ethereum blockchain so with a with<00:12:11.970> a<00:12:12.000> reusable<00:12:12.559> implementation<00:12:13.559> of<00:12:13.889> a 00:12:14.269 --> 00:12:14.279 align:start position:0% with a reusable implementation of a 00:12:14.279 --> 00:12:16.929 align:start position:0% with a reusable implementation of a packaged<00:12:14.730> index<00:12:15.059> contract<00:12:15.600> a<00:12:15.930> contract<00:12:16.050> that 00:12:16.929 --> 00:12:16.939 align:start position:0% packaged index contract a contract that 00:12:16.939 --> 00:12:20.660 align:start position:0% packaged index contract a contract that manages<00:12:18.529> tracking<00:12:19.529> versions<00:12:20.009> and<00:12:20.309> tracking 00:12:20.660 --> 00:12:20.670 align:start position:0% manages tracking versions and tracking 00:12:20.670 --> 00:12:24.019 align:start position:0% manages tracking versions and tracking what<00:12:20.790> packages<00:12:21.300> are<00:12:21.449> available<00:12:22.519> that<00:12:23.519> plus<00:12:24.000> a 00:12:24.019 --> 00:12:24.029 align:start position:0% what packages are available that plus a 00:12:24.029 --> 00:12:26.139 align:start position:0% what packages are available that plus a little<00:12:24.300> bit<00:12:24.420> of<00:12:24.600> tooling<00:12:24.959> integration 00:12:26.139 --> 00:12:26.149 align:start position:0% little bit of tooling integration 00:12:26.149 --> 00:12:29.449 align:start position:0% little bit of tooling integration combined<00:12:27.149> with<00:12:27.420> ens<00:12:27.899> means<00:12:28.829> that<00:12:29.069> we<00:12:29.160> have<00:12:29.279> a 00:12:29.449 --> 00:12:29.459 align:start position:0% combined with ens means that we have a 00:12:29.459 --> 00:12:32.749 align:start position:0% combined with ens means that we have a very<00:12:30.029> easy<00:12:30.360> system<00:12:30.720> for<00:12:31.500> every<00:12:32.009> team<00:12:32.250> to<00:12:32.550> set 00:12:32.749 --> 00:12:32.759 align:start position:0% very easy system for every team to set 00:12:32.759 --> 00:12:35.090 align:start position:0% very easy system for every team to set up<00:12:32.879> their<00:12:33.089> own<00:12:33.120> packaged<00:12:33.750> index<00:12:34.139> where<00:12:34.800> they 00:12:35.090 --> 00:12:35.100 align:start position:0% up their own packaged index where they 00:12:35.100 --> 00:12:36.559 align:start position:0% up their own packaged index where they are<00:12:35.250> in<00:12:35.399> full<00:12:35.610> control<00:12:35.850> of<00:12:36.029> all<00:12:36.269> of<00:12:36.449> their 00:12:36.559 --> 00:12:36.569 align:start position:0% are in full control of all of their 00:12:36.569 --> 00:12:39.860 align:start position:0% are in full control of all of their packages<00:12:37.850> now<00:12:38.850> how<00:12:39.029> this<00:12:39.209> relates<00:12:39.569> to<00:12:39.689> the 00:12:39.860 --> 00:12:39.870 align:start position:0% packages now how this relates to the 00:12:39.870 --> 00:12:44.350 align:start position:0% packages now how this relates to the standard<00:12:40.199> library<00:12:42.139> so<00:12:43.139> and<00:12:43.500> and<00:12:43.860> this<00:12:43.980> is<00:12:44.040> a 00:12:44.350 --> 00:12:44.360 align:start position:0% standard library so and and this is a 00:12:44.360 --> 00:12:46.490 align:start position:0% standard library so and and this is a theoretical<00:12:45.360> way<00:12:45.779> of<00:12:45.899> how<00:12:46.079> you<00:12:46.139> would<00:12:46.379> install 00:12:46.490 --> 00:12:46.500 align:start position:0% theoretical way of how you would install 00:12:46.500 --> 00:12:49.340 align:start position:0% theoretical way of how you would install this<00:12:47.240> we've<00:12:48.240> got<00:12:48.480> the<00:12:48.660> part<00:12:48.899> on<00:12:48.990> the<00:12:49.110> Left 00:12:49.340 --> 00:12:49.350 align:start position:0% this we've got the part on the Left 00:12:49.350 --> 00:12:50.900 align:start position:0% this we've got the part on the Left which<00:12:49.559> is<00:12:49.679> handled<00:12:50.009> by<00:12:50.040> the<00:12:50.129> dev<00:12:50.399> framework 00:12:50.900 --> 00:12:50.910 align:start position:0% which is handled by the dev framework 00:12:50.910 --> 00:12:52.730 align:start position:0% which is handled by the dev framework and<00:12:51.120> the<00:12:51.209> part<00:12:51.389> on<00:12:51.480> the<00:12:51.509> right<00:12:51.600> which<00:12:52.350> is<00:12:52.529> the 00:12:52.730 --> 00:12:52.740 align:start position:0% and the part on the right which is the 00:12:52.740 --> 00:12:55.780 align:start position:0% and the part on the right which is the namespace<00:12:53.100> piece<00:12:53.490> which<00:12:53.730> is<00:12:53.850> handled<00:12:54.179> by<00:12:54.209> ENS 00:12:55.780 --> 00:12:55.790 align:start position:0% namespace piece which is handled by ENS 00:12:55.790 --> 00:12:58.879 align:start position:0% namespace piece which is handled by ENS so<00:12:56.790> our<00:12:57.449> ecosystem<00:12:58.139> might<00:12:58.290> look<00:12:58.439> like<00:12:58.500> this 00:12:58.879 --> 00:12:58.889 align:start position:0% so our ecosystem might look like this 00:12:58.889 --> 00:13:01.879 align:start position:0% so our ecosystem might look like this maybe<00:12:59.819> I've<00:13:00.089> deployed<00:13:00.720> a<00:13:00.990> couple<00:13:01.259> packages<00:13:01.470> to 00:13:01.879 --> 00:13:01.889 align:start position:0% maybe I've deployed a couple packages to 00:13:01.889 --> 00:13:04.460 align:start position:0% maybe I've deployed a couple packages to my<00:13:02.040> index<00:13:02.459> maybe<00:13:03.059> the<00:13:03.240> Maker<00:13:03.449> Dow<00:13:03.720> teams<00:13:04.110> and 00:13:04.460 --> 00:13:04.470 align:start position:0% my index maybe the Maker Dow teams and 00:13:04.470 --> 00:13:06.530 align:start position:0% my index maybe the Maker Dow teams and deployed<00:13:04.889> a<00:13:04.920> couple<00:13:05.309> there<00:13:05.579> maybe<00:13:05.999> zeppelins 00:13:06.530 --> 00:13:06.540 align:start position:0% deployed a couple there maybe zeppelins 00:13:06.540 --> 00:13:08.569 align:start position:0% deployed a couple there maybe zeppelins got<00:13:06.749> some<00:13:06.959> there<00:13:07.199> and<00:13:07.439> there's<00:13:08.069> some<00:13:08.249> overlap 00:13:08.569 --> 00:13:08.579 align:start position:0% got some there and there's some overlap 00:13:08.579 --> 00:13:10.699 align:start position:0% got some there and there's some overlap right<00:13:09.149> like<00:13:09.420> I've<00:13:09.569> got<00:13:09.779> my<00:13:09.959> own<00:13:10.139> version<00:13:10.410> of 00:13:10.699 --> 00:13:10.709 align:start position:0% right like I've got my own version of 00:13:10.709 --> 00:13:13.610 align:start position:0% right like I've got my own version of owned<00:13:10.980> up<00:13:11.309> here<00:13:11.670> I<00:13:11.959> hope<00:13:12.959> that<00:13:13.259> one<00:13:13.439> doesn't 00:13:13.610 --> 00:13:13.620 align:start position:0% owned up here I hope that one doesn't 00:13:13.620 --> 00:13:15.860 align:start position:0% owned up here I hope that one doesn't overlap<00:13:14.009> safe<00:13:14.370> math<00:13:14.639> I've<00:13:14.939> got<00:13:15.509> my<00:13:15.720> own 00:13:15.860 --> 00:13:15.870 align:start position:0% overlap safe math I've got my own 00:13:15.870 --> 00:13:17.419 align:start position:0% overlap safe math I've got my own version<00:13:16.230> of<00:13:16.290> safe<00:13:16.529> math<00:13:16.769> on<00:13:16.980> my<00:13:17.160> side 00:13:17.419 --> 00:13:17.429 align:start position:0% version of safe math on my side 00:13:17.429 --> 00:13:18.570 align:start position:0% version of safe math on my side Zeppelin's<00:13:18.000> got<00:13:18.209> they 00:13:18.570 --> 00:13:18.580 align:start position:0% Zeppelin's got they 00:13:18.580 --> 00:13:21.030 align:start position:0% Zeppelin's got they and<00:13:18.880> the<00:13:19.420> idea<00:13:19.750> here<00:13:19.959> is<00:13:20.019> that<00:13:20.170> somebody<00:13:20.830> can 00:13:21.030 --> 00:13:21.040 align:start position:0% and the idea here is that somebody can 00:13:21.040 --> 00:13:24.240 align:start position:0% and the idea here is that somebody can then<00:13:21.339> come<00:13:21.670> along<00:13:22.029> and<00:13:22.630> pick<00:13:23.350> and<00:13:23.560> choose<00:13:23.620> out 00:13:24.240 --> 00:13:24.250 align:start position:0% then come along and pick and choose out 00:13:24.250 --> 00:13:26.490 align:start position:0% then come along and pick and choose out of<00:13:24.279> each<00:13:24.550> of<00:13:24.730> these<00:13:24.880> different<00:13:25.149> indexes<00:13:25.810> which 00:13:26.490 --> 00:13:26.500 align:start position:0% of each of these different indexes which 00:13:26.500 --> 00:13:28.560 align:start position:0% of each of these different indexes which ones<00:13:26.830> they<00:13:27.130> think<00:13:27.370> need<00:13:27.700> to<00:13:27.730> come<00:13:28.029> can<00:13:28.330> come 00:13:28.560 --> 00:13:28.570 align:start position:0% ones they think need to come can come 00:13:28.570 --> 00:13:32.370 align:start position:0% ones they think need to come can come together<00:13:28.720> to<00:13:29.170> form<00:13:29.560> one<00:13:30.540> rich<00:13:31.540> reusable 00:13:32.370 --> 00:13:32.380 align:start position:0% together to form one rich reusable 00:13:32.380 --> 00:13:37.110 align:start position:0% together to form one rich reusable standard<00:13:32.740> library<00:13:34.170> and<00:13:35.640> well<00:13:36.640> it's<00:13:36.850> great 00:13:37.110 --> 00:13:37.120 align:start position:0% standard library and well it's great 00:13:37.120 --> 00:13:39.630 align:start position:0% standard library and well it's great that<00:13:37.450> we<00:13:37.570> all<00:13:37.779> get<00:13:38.050> different<00:13:38.920> packaged 00:13:39.630 --> 00:13:39.640 align:start position:0% that we all get different packaged 00:13:39.640 --> 00:13:41.280 align:start position:0% that we all get different packaged indexes<00:13:40.209> and<00:13:40.360> we<00:13:40.420> all<00:13:40.540> have<00:13:40.720> our<00:13:40.750> own<00:13:40.839> packaged 00:13:41.280 --> 00:13:41.290 align:start position:0% indexes and we all have our own packaged 00:13:41.290 --> 00:13:43.199 align:start position:0% indexes and we all have our own packaged indexes<00:13:41.829> I<00:13:41.980> think<00:13:42.700> that's<00:13:42.850> the<00:13:43.000> way<00:13:43.089> the 00:13:43.199 --> 00:13:43.209 align:start position:0% indexes I think that's the way the 00:13:43.209 --> 00:13:45.300 align:start position:0% indexes I think that's the way the standard<00:13:43.570> library<00:13:43.990> can<00:13:44.200> work<00:13:44.350> -<00:13:44.649> it<00:13:45.070> can<00:13:45.190> look 00:13:45.300 --> 00:13:45.310 align:start position:0% standard library can work - it can look 00:13:45.310 --> 00:13:46.860 align:start position:0% standard library can work - it can look a<00:13:45.430> lot<00:13:45.610> like<00:13:45.760> Linux<00:13:46.180> where<00:13:46.390> there's<00:13:46.540> different 00:13:46.860 --> 00:13:46.870 align:start position:0% a lot like Linux where there's different 00:13:46.870 --> 00:13:48.900 align:start position:0% a lot like Linux where there's different flavors<00:13:46.990> of<00:13:47.440> the<00:13:47.560> standard<00:13:47.920> library<00:13:48.070> where 00:13:48.900 --> 00:13:48.910 align:start position:0% flavors of the standard library where 00:13:48.910 --> 00:13:50.579 align:start position:0% flavors of the standard library where there's<00:13:49.120> different<00:13:49.269> curators<00:13:49.930> and<00:13:50.200> different 00:13:50.579 --> 00:13:50.589 align:start position:0% there's different curators and different 00:13:50.589 --> 00:13:53.009 align:start position:0% there's different curators and different people<00:13:51.279> who've<00:13:51.459> picked<00:13:52.120> and<00:13:52.329> choose<00:13:52.570> which 00:13:53.009 --> 00:13:53.019 align:start position:0% people who've picked and choose which 00:13:53.019 --> 00:13:54.960 align:start position:0% people who've picked and choose which packages<00:13:53.740> from<00:13:53.920> which<00:13:54.160> place<00:13:54.459> they<00:13:54.760> think 00:13:54.960 --> 00:13:54.970 align:start position:0% packages from which place they think 00:13:54.970 --> 00:13:57.120 align:start position:0% packages from which place they think make<00:13:55.240> up<00:13:55.390> the<00:13:55.570> best<00:13:55.779> standard<00:13:56.170> library<00:13:56.560> which 00:13:57.120 --> 00:13:57.130 align:start position:0% make up the best standard library which 00:13:57.130 --> 00:13:58.769 align:start position:0% make up the best standard library which means<00:13:57.370> we're<00:13:57.550> not<00:13:57.670> stuck<00:13:58.000> with<00:13:58.029> one<00:13:58.390> packaged 00:13:58.769 --> 00:13:58.779 align:start position:0% means we're not stuck with one packaged 00:13:58.779 --> 00:14:01.560 align:start position:0% means we're not stuck with one packaged index<00:13:59.190> we're<00:14:00.190> not<00:14:00.310> stuck<00:14:00.550> with<00:14:00.579> one<00:14:00.910> standard 00:14:01.560 --> 00:14:01.570 align:start position:0% index we're not stuck with one standard 00:14:01.570 --> 00:14:03.030 align:start position:0% index we're not stuck with one standard library<00:14:02.050> but<00:14:02.320> we<00:14:02.410> actually<00:14:02.529> have<00:14:02.800> a<00:14:02.829> lot<00:14:03.010> of 00:14:03.030 --> 00:14:03.040 align:start position:0% library but we actually have a lot of 00:14:03.040 --> 00:14:06.180 align:start position:0% library but we actually have a lot of choice<00:14:03.399> to<00:14:03.700> pick<00:14:03.880> and<00:14:04.029> choose<00:14:04.890> this<00:14:05.890> can<00:14:06.100> be 00:14:06.180 --> 00:14:06.190 align:start position:0% choice to pick and choose this can be 00:14:06.190 --> 00:14:08.040 align:start position:0% choice to pick and choose this can be thought<00:14:06.310> of<00:14:06.370> sort<00:14:06.730> of<00:14:06.790> as<00:14:06.940> the<00:14:07.149> spread<00:14:07.839> a<00:14:07.870> bunch 00:14:08.040 --> 00:14:08.050 align:start position:0% thought of sort of as the spread a bunch 00:14:08.050 --> 00:14:11.400 align:start position:0% thought of sort of as the spread a bunch of<00:14:08.200> seeds<00:14:08.500> and<00:14:08.740> see<00:14:08.950> which<00:14:09.100> flowers<00:14:09.550> bloom<00:14:10.410> but 00:14:11.400 --> 00:14:11.410 align:start position:0% of seeds and see which flowers bloom but 00:14:11.410 --> 00:14:14.670 align:start position:0% of seeds and see which flowers bloom but I<00:14:11.440> think<00:14:11.740> this<00:14:12.040> has<00:14:12.519> some<00:14:13.240> is<00:14:13.510> very<00:14:14.050> promising 00:14:14.670 --> 00:14:14.680 align:start position:0% I think this has some is very promising 00:14:14.680 --> 00:14:18.870 align:start position:0% I think this has some is very promising for<00:14:15.010> a<00:14:15.070> rich<00:14:15.250> ecosystem<00:14:15.880> of<00:14:15.940> packages<00:14:17.430> so<00:14:18.430> what 00:14:18.870 --> 00:14:18.880 align:start position:0% for a rich ecosystem of packages so what 00:14:18.880 --> 00:14:21.870 align:start position:0% for a rich ecosystem of packages so what do<00:14:18.940> we<00:14:19.029> need<00:14:19.180> to<00:14:19.300> make<00:14:19.420> this<00:14:19.540> a<00:14:19.600> reality<00:14:19.890> um<00:14:20.890> so 00:14:21.870 --> 00:14:21.880 align:start position:0% do we need to make this a reality um so 00:14:21.880 --> 00:14:24.060 align:start position:0% do we need to make this a reality um so right<00:14:22.180> now<00:14:22.329> we<00:14:22.390> need<00:14:22.720> more<00:14:22.750> support<00:14:23.410> for<00:14:23.649> erc 00:14:24.060 --> 00:14:24.070 align:start position:0% right now we need more support for erc 00:14:24.070 --> 00:14:27.000 align:start position:0% right now we need more support for erc 90<00:14:24.100> and<00:14:24.520> tooling<00:14:25.140> populous<00:14:26.140> has<00:14:26.440> some<00:14:26.649> basic 00:14:27.000 --> 00:14:27.010 align:start position:0% 90 and tooling populous has some basic 00:14:27.010 --> 00:14:29.460 align:start position:0% 90 and tooling populous has some basic support<00:14:27.339> in<00:14:27.520> it<00:14:27.640> same<00:14:28.329> with<00:14:28.510> truffled<00:14:28.930> but<00:14:29.230> in 00:14:29.460 --> 00:14:29.470 align:start position:0% support in it same with truffled but in 00:14:29.470 --> 00:14:33.090 align:start position:0% support in it same with truffled but in we<00:14:29.860> need<00:14:29.980> more<00:14:30.250> tools<00:14:30.610> to<00:14:30.820> support<00:14:31.000> this<00:14:32.100> we 00:14:33.090 --> 00:14:33.100 align:start position:0% we need more tools to support this we 00:14:33.100 --> 00:14:35.370 align:start position:0% we need more tools to support this we need<00:14:33.279> a<00:14:33.700> standard<00:14:34.329> implementation<00:14:35.230> of<00:14:35.320> a 00:14:35.370 --> 00:14:35.380 align:start position:0% need a standard implementation of a 00:14:35.380 --> 00:14:36.930 align:start position:0% need a standard implementation of a package<00:14:35.709> registry<00:14:36.190> something<00:14:36.610> that<00:14:36.730> we<00:14:36.820> can 00:14:36.930 --> 00:14:36.940 align:start position:0% package registry something that we can 00:14:36.940 --> 00:14:38.760 align:start position:0% package registry something that we can ship<00:14:37.180> around<00:14:37.480> in<00:14:37.720> those<00:14:37.810> tools<00:14:38.140> so<00:14:38.470> those 00:14:38.760 --> 00:14:38.770 align:start position:0% ship around in those tools so those 00:14:38.770 --> 00:14:41.940 align:start position:0% ship around in those tools so those tools<00:14:39.040> can<00:14:39.310> set<00:14:39.550> them<00:14:39.700> up<00:14:39.850> for<00:14:39.880> us<00:14:40.260> and<00:14:41.260> then<00:14:41.829> we 00:14:41.940 --> 00:14:41.950 align:start position:0% tools can set them up for us and then we 00:14:41.950 --> 00:14:43.560 align:start position:0% tools can set them up for us and then we need<00:14:42.100> automation<00:14:42.730> for<00:14:42.970> setting<00:14:43.390> these 00:14:43.560 --> 00:14:43.570 align:start position:0% need automation for setting these 00:14:43.570 --> 00:14:45.780 align:start position:0% need automation for setting these registries<00:14:44.110> up<00:14:44.380> and<00:14:44.620> that's<00:14:45.010> both<00:14:45.190> automation 00:14:45.780 --> 00:14:45.790 align:start position:0% registries up and that's both automation 00:14:45.790 --> 00:14:47.760 align:start position:0% registries up and that's both automation for<00:14:45.970> deploying<00:14:46.329> them<00:14:46.630> as<00:14:46.839> well<00:14:47.079> as<00:14:47.170> automation 00:14:47.760 --> 00:14:47.770 align:start position:0% for deploying them as well as automation 00:14:47.770 --> 00:14:49.910 align:start position:0% for deploying them as well as automation for<00:14:47.950> getting<00:14:48.220> the<00:14:48.339> ens<00:14:48.760> piece<00:14:49.149> tied<00:14:49.630> together 00:14:49.910 --> 00:14:49.920 align:start position:0% for getting the ens piece tied together 00:14:49.920 --> 00:14:54.210 align:start position:0% for getting the ens piece tied together and<00:14:51.329> we<00:14:52.329> need<00:14:52.540> a<00:14:52.839> feature<00:14:53.140> request<00:14:53.380> into 00:14:54.210 --> 00:14:54.220 align:start position:0% and we need a feature request into 00:14:54.220 --> 00:14:58.170 align:start position:0% and we need a feature request into solidity<00:14:54.820> and<00:14:55.180> other<00:14:55.770> EVM<00:14:56.770> languages<00:14:57.490> to 00:14:58.170 --> 00:14:58.180 align:start position:0% solidity and other EVM languages to 00:14:58.180 --> 00:15:00.630 align:start position:0% solidity and other EVM languages to allow<00:14:58.420> us<00:14:58.600> to<00:14:58.870> inject<00:14:59.500> pre-compiled<00:15:00.220> byte 00:15:00.630 --> 00:15:00.640 align:start position:0% allow us to inject pre-compiled byte 00:15:00.640 --> 00:15:02.910 align:start position:0% allow us to inject pre-compiled byte code<00:15:00.910> into<00:15:01.360> the<00:15:01.390> compilation<00:15:01.810> process<00:15:02.110> and 00:15:02.910 --> 00:15:02.920 align:start position:0% code into the compilation process and 00:15:02.920 --> 00:15:05.430 align:start position:0% code into the compilation process and the<00:15:03.370> reason<00:15:03.699> for<00:15:03.880> this<00:15:04.000> is<00:15:04.240> that<00:15:04.270> as<00:15:04.630> our 00:15:05.430 --> 00:15:05.440 align:start position:0% the reason for this is that as our 00:15:05.440 --> 00:15:07.829 align:start position:0% the reason for this is that as our package<00:15:05.860> ecosystem<00:15:06.459> grows<00:15:06.670> we're<00:15:07.480> gonna<00:15:07.600> have 00:15:07.829 --> 00:15:07.839 align:start position:0% package ecosystem grows we're gonna have 00:15:07.839 --> 00:15:10.800 align:start position:0% package ecosystem grows we're gonna have many<00:15:08.199> different<00:15:08.949> versions<00:15:09.520> of<00:15:09.970> solidity<00:15:10.480> that 00:15:10.800 --> 00:15:10.810 align:start position:0% many different versions of solidity that 00:15:10.810 --> 00:15:12.930 align:start position:0% many different versions of solidity that are<00:15:10.899> required<00:15:11.350> to<00:15:11.620> recompile<00:15:12.130> certain<00:15:12.640> things 00:15:12.930 --> 00:15:12.940 align:start position:0% are required to recompile certain things 00:15:12.940 --> 00:15:16.730 align:start position:0% are required to recompile certain things and<00:15:13.209> in<00:15:14.199> order<00:15:14.529> to<00:15:14.589> require<00:15:15.180> compile<00:15:16.180> a<00:15:16.449> very 00:15:16.730 --> 00:15:16.740 align:start position:0% and in order to require compile a very 00:15:16.740 --> 00:15:19.620 align:start position:0% and in order to require compile a very complex<00:15:17.740> dependency<00:15:18.519> tree<00:15:18.850> that<00:15:19.120> has<00:15:19.240> lots<00:15:19.510> of 00:15:19.620 --> 00:15:19.630 align:start position:0% complex dependency tree that has lots of 00:15:19.630 --> 00:15:21.870 align:start position:0% complex dependency tree that has lots of different<00:15:19.779> versions<00:15:20.529> of<00:15:20.829> solidity<00:15:21.279> we're 00:15:21.870 --> 00:15:21.880 align:start position:0% different versions of solidity we're 00:15:21.880 --> 00:15:23.069 align:start position:0% different versions of solidity we're gonna<00:15:21.970> need<00:15:22.209> to<00:15:22.360> be<00:15:22.449> able<00:15:22.540> to<00:15:22.690> compile<00:15:23.050> all 00:15:23.069 --> 00:15:23.079 align:start position:0% gonna need to be able to compile all 00:15:23.079 --> 00:15:24.870 align:start position:0% gonna need to be able to compile all those<00:15:23.500> individually<00:15:24.250> and<00:15:24.370> then<00:15:24.519> slowly 00:15:24.870 --> 00:15:24.880 align:start position:0% those individually and then slowly 00:15:24.880 --> 00:15:26.370 align:start position:0% those individually and then slowly combine<00:15:25.390> them<00:15:25.570> together<00:15:25.750> into<00:15:26.079> one<00:15:26.350> big 00:15:26.370 --> 00:15:26.380 align:start position:0% combine them together into one big 00:15:26.380 --> 00:15:28.860 align:start position:0% combine them together into one big compiled<00:15:27.070> asset<00:15:27.520> so<00:15:28.180> there's<00:15:28.510> gonna<00:15:28.660> be<00:15:28.750> some 00:15:28.860 --> 00:15:28.870 align:start position:0% compiled asset so there's gonna be some 00:15:28.870 --> 00:15:31.500 align:start position:0% compiled asset so there's gonna be some compiler<00:15:29.380> or<00:15:29.589> if<00:15:29.649> it<00:15:29.770> has<00:15:29.890> to<00:15:30.010> be<00:15:30.070> done<00:15:30.250> but<00:15:31.209> in 00:15:31.500 --> 00:15:31.510 align:start position:0% compiler or if it has to be done but in 00:15:31.510 --> 00:15:34.740 align:start position:0% compiler or if it has to be done but in general<00:15:31.780> most<00:15:32.110> of<00:15:32.350> these<00:15:32.500> pieces<00:15:32.800> are<00:15:33.250> at<00:15:34.060> the 00:15:34.740 --> 00:15:34.750 align:start position:0% general most of these pieces are at the 00:15:34.750 --> 00:15:37.320 align:start position:0% general most of these pieces are at the 80%<00:15:35.290> mark<00:15:35.800> or<00:15:35.980> more<00:15:36.220> we're<00:15:36.640> very<00:15:36.880> close<00:15:37.150> to 00:15:37.320 --> 00:15:37.330 align:start position:0% 80% mark or more we're very close to 00:15:37.330 --> 00:15:39.540 align:start position:0% 80% mark or more we're very close to this<00:15:37.480> and<00:15:37.780> all<00:15:38.170> of<00:15:38.350> this<00:15:38.500> is<00:15:38.680> about<00:15:39.130> ready<00:15:39.460> to 00:15:39.540 --> 00:15:39.550 align:start position:0% this and all of this is about ready to 00:15:39.550 --> 00:15:47.870 align:start position:0% this and all of this is about ready to come<00:15:39.820> together<00:15:40.920> thank<00:15:41.920> you 00:15:47.870 --> 00:15:47.880 align:start position:0% 00:15:47.880 --> 00:15:55.370 align:start position:0% [Music]