WEBVTT Kind: captions Language: en 00:00:00.540 --> 00:00:18.730 align:start position:0% [Music] 00:00:18.730 --> 00:00:18.740 align:start position:0% 00:00:18.740 --> 00:00:23.720 align:start position:0% okay<00:00:19.740> so<00:00:19.820> hi<00:00:20.820> guys<00:00:21.180> I'm<00:00:21.450> RJ<00:00:21.660> um<00:00:22.340> for<00:00:23.340> those<00:00:23.550> of 00:00:23.720 --> 00:00:23.730 align:start position:0% okay so hi guys I'm RJ um for those of 00:00:23.730 --> 00:00:26.480 align:start position:0% okay so hi guys I'm RJ um for those of you<00:00:23.760> who<00:00:24.300> have<00:00:24.689> not<00:00:24.900> had<00:00:25.170> to<00:00:25.350> endure<00:00:25.830> my<00:00:26.220> Chatty 00:00:26.480 --> 00:00:26.490 align:start position:0% you who have not had to endure my Chatty 00:00:26.490 --> 00:00:28.220 align:start position:0% you who have not had to endure my Chatty Cathy<00:00:26.970> pneus<00:00:27.180> and<00:00:27.420> had<00:00:27.510> the<00:00:27.630> misfortune<00:00:27.779> of 00:00:28.220 --> 00:00:28.230 align:start position:0% Cathy pneus and had the misfortune of 00:00:28.230 --> 00:00:30.500 align:start position:0% Cathy pneus and had the misfortune of that<00:00:28.500> a<00:00:28.980> little<00:00:29.400> bit<00:00:29.460> about<00:00:29.640> me<00:00:29.790> I<00:00:29.820> helped 00:00:30.500 --> 00:00:30.510 align:start position:0% that a little bit about me I helped 00:00:30.510 --> 00:00:32.119 align:start position:0% that a little bit about me I helped develop<00:00:30.930> solidity<00:00:31.380> and<00:00:31.470> work<00:00:31.890> on<00:00:32.040> the 00:00:32.119 --> 00:00:32.129 align:start position:0% develop solidity and work on the 00:00:32.129 --> 00:00:34.280 align:start position:0% develop solidity and work on the etherion<00:00:32.430> package<00:00:32.700> manager<00:00:33.150> and<00:00:33.420> right<00:00:34.110> now 00:00:34.280 --> 00:00:34.290 align:start position:0% etherion package manager and right now 00:00:34.290 --> 00:00:37.100 align:start position:0% etherion package manager and right now i'm<00:00:34.530> going<00:00:34.650> to<00:00:34.710> go<00:00:34.830> hand<00:00:35.100> it<00:00:35.220> over<00:00:35.370> to<00:00:35.580> zack<00:00:36.210> my 00:00:37.100 --> 00:00:37.110 align:start position:0% i'm going to go hand it over to zack my 00:00:37.110 --> 00:00:39.890 align:start position:0% i'm going to go hand it over to zack my colleague<00:00:38.059> right<00:00:39.059> so<00:00:39.300> our<00:00:39.330> Jay<00:00:39.570> and<00:00:39.690> I<00:00:39.720> are<00:00:39.750> on 00:00:39.890 --> 00:00:39.900 align:start position:0% colleague right so our Jay and I are on 00:00:39.900 --> 00:00:41.390 align:start position:0% colleague right so our Jay and I are on the<00:00:39.989> platform<00:00:40.379> team<00:00:40.530> a<00:00:40.710> terrace<00:00:41.010> and<00:00:41.190> today 00:00:41.390 --> 00:00:41.400 align:start position:0% the platform team a terrace and today 00:00:41.400 --> 00:00:42.439 align:start position:0% the platform team a terrace and today we're<00:00:41.489> going<00:00:41.580> to<00:00:41.640> talk<00:00:41.820> to<00:00:41.940> you<00:00:42.000> about<00:00:42.090> chain 00:00:42.439 --> 00:00:42.449 align:start position:0% we're going to talk to you about chain 00:00:42.449 --> 00:00:43.820 align:start position:0% we're going to talk to you about chain orchestration<00:00:43.050> tooling<00:00:43.410> which<00:00:43.559> is<00:00:43.680> what<00:00:43.800> I 00:00:43.820 --> 00:00:43.830 align:start position:0% orchestration tooling which is what I 00:00:43.830 --> 00:00:46.369 align:start position:0% orchestration tooling which is what I focus<00:00:44.220> on<00:00:44.340> and<00:00:44.580> it's<00:00:45.210> a<00:00:45.360> smart<00:00:45.930> contract 00:00:46.369 --> 00:00:46.379 align:start position:0% focus on and it's a smart contract 00:00:46.379 --> 00:00:47.899 align:start position:0% focus on and it's a smart contract package<00:00:46.680> management<00:00:47.100> which<00:00:47.400> is<00:00:47.519> what<00:00:47.760> RJ 00:00:47.899 --> 00:00:47.909 align:start position:0% package management which is what RJ 00:00:47.909 --> 00:00:50.410 align:start position:0% package management which is what RJ focus<00:00:48.330> is<00:00:48.449> on 00:00:50.410 --> 00:00:50.420 align:start position:0% focus is on 00:00:50.420 --> 00:00:52.270 align:start position:0% focus is on on 00:00:52.270 --> 00:00:52.280 align:start position:0% on 00:00:52.280 --> 00:00:54.399 align:start position:0% on next<00:00:53.280> slide<00:00:53.430> please 00:00:54.399 --> 00:00:54.409 align:start position:0% next slide please 00:00:54.409 --> 00:00:57.649 align:start position:0% next slide please okay<00:00:55.409> so<00:00:55.710> what<00:00:55.979> is<00:00:56.100> eros<00:00:56.460> eros<00:00:56.850> is<00:00:57.239> tooling<00:00:57.629> for 00:00:57.649 --> 00:00:57.659 align:start position:0% okay so what is eros eros is tooling for 00:00:57.659 --> 00:01:01.399 align:start position:0% okay so what is eros eros is tooling for developers<00:00:58.580> we<00:00:59.580> offer<00:00:59.729> a<00:00:59.970> chain<00:01:00.510> maker<00:01:01.049> and 00:01:01.399 --> 00:01:01.409 align:start position:0% developers we offer a chain maker and 00:01:01.409 --> 00:01:04.310 align:start position:0% developers we offer a chain maker and this<00:01:01.949> is<00:01:02.129> a<00:01:02.159> it's<00:01:02.850> got<00:01:03.059> an<00:01:03.239> interactive<00:01:03.960> wizard 00:01:04.310 --> 00:01:04.320 align:start position:0% this is a it's got an interactive wizard 00:01:04.320 --> 00:01:06.410 align:start position:0% this is a it's got an interactive wizard and<00:01:04.559> it<00:01:04.739> helps<00:01:04.920> you<00:01:05.010> set<00:01:05.220> up<00:01:05.370> your<00:01:05.610> chain 00:01:06.410 --> 00:01:06.420 align:start position:0% and it helps you set up your chain 00:01:06.420 --> 00:01:09.020 align:start position:0% and it helps you set up your chain essentially<00:01:07.070> for<00:01:08.070> different<00:01:08.370> accounts<00:01:08.820> and 00:01:09.020 --> 00:01:09.030 align:start position:0% essentially for different accounts and 00:01:09.030 --> 00:01:11.270 align:start position:0% essentially for different accounts and the<00:01:09.090> account<00:01:09.420> types<00:01:09.900> are<00:01:10.200> an<00:01:10.560> abstraction<00:01:11.010> of 00:01:11.270 --> 00:01:11.280 align:start position:0% the account types are an abstraction of 00:01:11.280 --> 00:01:13.719 align:start position:0% the account types are an abstraction of our<00:01:11.430> permission 00:01:13.719 --> 00:01:13.729 align:start position:0% our permission 00:01:13.729 --> 00:01:16.910 align:start position:0% our permission experimenting<00:01:14.729> scheme<00:01:15.060> comes<00:01:15.360> out<00:01:15.570> of<00:01:15.750> air<00:01:16.740> is 00:01:16.910 --> 00:01:16.920 align:start position:0% experimenting scheme comes out of air is 00:01:16.920 --> 00:01:19.490 align:start position:0% experimenting scheme comes out of air is DB<00:01:17.310> which<00:01:17.790> is<00:01:18.060> our<00:01:18.240> blockchain<00:01:18.510> client<00:01:19.080> that 00:01:19.490 --> 00:01:19.500 align:start position:0% DB which is our blockchain client that 00:01:19.500 --> 00:01:21.980 align:start position:0% DB which is our blockchain client that endermen<00:01:20.190> proof<00:01:20.400> of<00:01:20.520> stake<00:01:20.810> can<00:01:21.810> everyone 00:01:21.980 --> 00:01:21.990 align:start position:0% endermen proof of stake can everyone 00:01:21.990 --> 00:01:25.130 align:start position:0% endermen proof of stake can everyone hear<00:01:22.080> me<00:01:22.340> cool<00:01:23.450> and<00:01:24.450> then<00:01:24.810> we<00:01:24.960> have<00:01:25.050> the 00:01:25.130 --> 00:01:25.140 align:start position:0% hear me cool and then we have the 00:01:25.140 --> 00:01:27.830 align:start position:0% hear me cool and then we have the package<00:01:25.440> manager<00:01:26.030> and<00:01:27.030> it's<00:01:27.210> all<00:01:27.390> wrapped<00:01:27.630> up 00:01:27.830 --> 00:01:27.840 align:start position:0% package manager and it's all wrapped up 00:01:27.840 --> 00:01:31.010 align:start position:0% package manager and it's all wrapped up in<00:01:28.080> a<00:01:28.200> command-line<00:01:28.710> tool<00:01:29.450> that's<00:01:30.450> heavily 00:01:31.010 --> 00:01:31.020 align:start position:0% in a command-line tool that's heavily 00:01:31.020 --> 00:01:35.320 align:start position:0% in a command-line tool that's heavily daugher<00:01:31.350> rised 00:01:35.320 --> 00:01:35.330 align:start position:0% 00:01:35.330 --> 00:01:38.840 align:start position:0% next<00:01:36.330> slide<00:01:36.510> please<00:01:36.770> to<00:01:37.770> two<00:01:38.220> things<00:01:38.490> don't 00:01:38.840 --> 00:01:38.850 align:start position:0% next slide please to two things don't 00:01:38.850 --> 00:01:40.400 align:start position:0% next slide please to two things don't work<00:01:38.940> all<00:01:39.120> right<00:01:39.300> so<00:01:39.540> this<00:01:39.690> is<00:01:39.870> what<00:01:40.140> it<00:01:40.230> looks 00:01:40.400 --> 00:01:40.410 align:start position:0% work all right so this is what it looks 00:01:40.410 --> 00:01:43.490 align:start position:0% work all right so this is what it looks like<00:01:40.590> so<00:01:41.160> at<00:01:41.460> errors<00:01:41.880> were<00:01:42.270> providing<00:01:42.840> what 00:01:43.490 --> 00:01:43.500 align:start position:0% like so at errors were providing what 00:01:43.500 --> 00:01:46.520 align:start position:0% like so at errors were providing what you<00:01:43.590> see<00:01:43.800> in<00:01:43.890> green<00:01:44.190> and<00:01:44.460> so<00:01:45.200> through<00:01:46.200> docker 00:01:46.520 --> 00:01:46.530 align:start position:0% you see in green and so through docker 00:01:46.530 --> 00:01:48.790 align:start position:0% you see in green and so through docker we<00:01:47.160> can<00:01:47.340> control<00:01:47.730> all<00:01:48.060> these<00:01:48.270> different 00:01:48.790 --> 00:01:48.800 align:start position:0% we can control all these different 00:01:48.800 --> 00:01:50.540 align:start position:0% we can control all these different requirements<00:01:49.800> for<00:01:50.040> a<00:01:50.070> blockchain 00:01:50.540 --> 00:01:50.550 align:start position:0% requirements for a blockchain 00:01:50.550 --> 00:01:53.930 align:start position:0% requirements for a blockchain application<00:01:51.740> files<00:01:52.740> for<00:01:53.130> example<00:01:53.550> we<00:01:53.670> have<00:01:53.790> an 00:01:53.930 --> 00:01:53.940 align:start position:0% application files for example we have an 00:01:53.940 --> 00:01:57.260 align:start position:0% application files for example we have an IP<00:01:54.300> FS<00:01:54.630> integration<00:01:55.400> keys<00:01:56.400> we<00:01:56.850> outsource<00:01:57.210> that 00:01:57.260 --> 00:01:57.270 align:start position:0% IP FS integration keys we outsource that 00:01:57.270 --> 00:01:59.300 align:start position:0% IP FS integration keys we outsource that transaction<00:01:58.230> a<00:01:58.320> consensus<00:01:58.800> engine<00:01:59.130> that's 00:01:59.300 --> 00:01:59.310 align:start position:0% transaction a consensus engine that's 00:01:59.310 --> 00:02:03.520 align:start position:0% transaction a consensus engine that's tender<00:01:59.610> mint<00:01:59.850> and<00:02:00.540> etc<00:02:01.190> next<00:02:02.190> slide 00:02:03.520 --> 00:02:03.530 align:start position:0% tender mint and etc next slide 00:02:03.530 --> 00:02:05.720 align:start position:0% tender mint and etc next slide okay<00:02:04.530> so<00:02:04.590> here's<00:02:04.860> the<00:02:04.950> demo<00:02:05.159> the<00:02:05.400> internet 00:02:05.720 --> 00:02:05.730 align:start position:0% okay so here's the demo the internet 00:02:05.730 --> 00:02:08.839 align:start position:0% okay so here's the demo the internet gods<00:02:05.940> were<00:02:06.390> not<00:02:06.540> so<00:02:06.750> nice<00:02:06.990> so<00:02:07.489> basically<00:02:08.489> the 00:02:08.839 --> 00:02:08.849 align:start position:0% gods were not so nice so basically the 00:02:08.849 --> 00:02:10.550 align:start position:0% gods were not so nice so basically the way<00:02:09.000> that<00:02:09.239> you<00:02:09.330> would<00:02:09.420> run<00:02:09.599> eros<00:02:10.080> and<00:02:10.289> certain 00:02:10.550 --> 00:02:10.560 align:start position:0% way that you would run eros and certain 00:02:10.560 --> 00:02:12.559 align:start position:0% way that you would run eros and certain errors<00:02:10.769> chain<00:02:11.069> you<00:02:11.610> run<00:02:11.790> errors<00:02:12.060> chains<00:02:12.330> make 00:02:12.559 --> 00:02:12.569 align:start position:0% errors chain you run errors chains make 00:02:12.569 --> 00:02:15.229 align:start position:0% errors chain you run errors chains make that<00:02:13.080> will<00:02:13.230> generate<00:02:13.409> a<00:02:13.620> key<00:02:13.920> or<00:02:14.239> several 00:02:15.229 --> 00:02:15.239 align:start position:0% that will generate a key or several 00:02:15.239 --> 00:02:19.100 align:start position:0% that will generate a key or several there's<00:02:15.900> a<00:02:15.959> whole<00:02:16.110> slew<00:02:16.590> of<00:02:16.620> flags<00:02:17.099> to<00:02:18.000> do<00:02:18.959> that 00:02:19.100 --> 00:02:19.110 align:start position:0% there's a whole slew of flags to do that 00:02:19.110 --> 00:02:21.710 align:start position:0% there's a whole slew of flags to do that and<00:02:19.409> then<00:02:20.250> you<00:02:20.340> start<00:02:20.580> the<00:02:20.670> chain<00:02:20.909> posit<00:02:21.629> the 00:02:21.710 --> 00:02:21.720 align:start position:0% and then you start the chain posit the 00:02:21.720 --> 00:02:23.599 align:start position:0% and then you start the chain posit the directory<00:02:22.620> where<00:02:22.739> all<00:02:23.010> these<00:02:23.159> files<00:02:23.400> were 00:02:23.599 --> 00:02:23.609 align:start position:0% directory where all these files were 00:02:23.609 --> 00:02:26.390 align:start position:0% directory where all these files were generated<00:02:24.120> and<00:02:24.959> then<00:02:25.170> you<00:02:25.290> grab<00:02:25.590> the<00:02:25.920> address 00:02:26.390 --> 00:02:26.400 align:start position:0% generated and then you grab the address 00:02:26.400 --> 00:02:28.899 align:start position:0% generated and then you grab the address that<00:02:26.639> you<00:02:26.670> need<00:02:26.939> or<00:02:27.150> key<00:02:27.680> and<00:02:28.430> you<00:02:28.549> can<00:02:28.700> see 00:02:28.899 --> 00:02:28.909 align:start position:0% that you need or key and you can see 00:02:28.909 --> 00:02:31.509 align:start position:0% that you need or key and you can see there<00:02:29.150> that<00:02:29.379> you've<00:02:30.379> got<00:02:30.590> your<00:02:30.739> keys<00:02:30.980> service 00:02:31.509 --> 00:02:31.519 align:start position:0% there that you've got your keys service 00:02:31.519 --> 00:02:33.940 align:start position:0% there that you've got your keys service running<00:02:31.790> so<00:02:32.060> the<00:02:32.180> keys<00:02:32.420> Damon<00:02:32.959> is<00:02:33.140> in<00:02:33.590> its<00:02:33.769> own 00:02:33.940 --> 00:02:33.950 align:start position:0% running so the keys Damon is in its own 00:02:33.950 --> 00:02:36.160 align:start position:0% running so the keys Damon is in its own daughter<00:02:34.430> container<00:02:34.969> which<00:02:35.480> makes<00:02:35.719> it<00:02:35.930> nice 00:02:36.160 --> 00:02:36.170 align:start position:0% daughter container which makes it nice 00:02:36.170 --> 00:02:38.080 align:start position:0% daughter container which makes it nice and<00:02:36.379> modular<00:02:36.739> and<00:02:36.890> then<00:02:37.370> the<00:02:37.489> chain<00:02:37.760> which 00:02:38.080 --> 00:02:38.090 align:start position:0% and modular and then the chain which 00:02:38.090 --> 00:02:41.740 align:start position:0% and modular and then the chain which I've<00:02:38.209> named<00:02:38.420> DEFCON<00:02:38.900> 2<00:02:39.170> is<00:02:39.950> also<00:02:40.340> running<00:02:40.750> and 00:02:41.740 --> 00:02:41.750 align:start position:0% I've named DEFCON 2 is also running and 00:02:41.750 --> 00:02:43.479 align:start position:0% I've named DEFCON 2 is also running and then<00:02:42.200> the<00:02:42.319> third<00:02:42.379> command<00:02:42.920> basically<00:02:43.370> that 00:02:43.479 --> 00:02:43.489 align:start position:0% then the third command basically that 00:02:43.489 --> 00:02:45.280 align:start position:0% then the third command basically that you<00:02:43.579> would<00:02:43.700> run<00:02:43.879> would<00:02:44.120> be<00:02:44.150> eras<00:02:44.540> packages<00:02:45.019> do 00:02:45.280 --> 00:02:45.290 align:start position:0% you would run would be eras packages do 00:02:45.290 --> 00:02:46.959 align:start position:0% you would run would be eras packages do you<00:02:45.709> give<00:02:45.859> it<00:02:45.889> the<00:02:46.099> chain<00:02:46.340> name<00:02:46.549> you<00:02:46.730> give<00:02:46.849> it 00:02:46.959 --> 00:02:46.969 align:start position:0% you give it the chain name you give it 00:02:46.969 --> 00:02:49.509 align:start position:0% you give it the chain name you give it the<00:02:47.060> address<00:02:47.180> that<00:02:48.079> would<00:02:48.290> have<00:02:48.530> a<00:02:48.889> contract 00:02:49.509 --> 00:02:49.519 align:start position:0% the address that would have a contract 00:02:49.519 --> 00:02:52.539 align:start position:0% the address that would have a contract deploy<00:02:49.909> permission<00:02:50.599> on<00:02:50.810> that<00:02:51.379> chain<00:02:51.709> and 00:02:52.539 --> 00:02:52.549 align:start position:0% deploy permission on that chain and 00:02:52.549 --> 00:02:54.369 align:start position:0% deploy permission on that chain and you're<00:02:52.730> off<00:02:52.849> to<00:02:53.030> the<00:02:53.060> races<00:02:53.150> so<00:02:53.750> so<00:02:54.170> that 00:02:54.369 --> 00:02:54.379 align:start position:0% you're off to the races so so that 00:02:54.379 --> 00:02:56.709 align:start position:0% you're off to the races so so that command<00:02:54.829> eras<00:02:55.250> packages<00:02:55.670> do<00:02:55.879> would<00:02:56.060> be<00:02:56.180> run 00:02:56.709 --> 00:02:56.719 align:start position:0% command eras packages do would be run 00:02:56.719 --> 00:03:00.009 align:start position:0% command eras packages do would be run from<00:02:56.750> a<00:02:57.200> directory<00:02:57.709> that<00:02:57.950> will<00:02:58.549> have<00:02:58.760> um<00:02:59.180> you 00:03:00.009 --> 00:03:00.019 align:start position:0% from a directory that will have um you 00:03:00.019 --> 00:03:02.440 align:start position:0% from a directory that will have um you all<00:03:00.500> your<00:03:00.889> smart<00:03:01.159> contracts<00:03:01.639> and<00:03:01.879> then<00:03:02.299> the 00:03:02.440 --> 00:03:02.450 align:start position:0% all your smart contracts and then the 00:03:02.450 --> 00:03:04.599 align:start position:0% all your smart contracts and then the EPM<00:03:02.870> yamo<00:03:03.200> file<00:03:03.439> which<00:03:03.650> rj<00:03:03.980> will<00:03:04.159> be<00:03:04.250> talking 00:03:04.599 --> 00:03:04.609 align:start position:0% EPM yamo file which rj will be talking 00:03:04.609 --> 00:03:09.149 align:start position:0% EPM yamo file which rj will be talking about<00:03:05.169> eventually<00:03:06.220> next<00:03:07.220> slide 00:03:09.149 --> 00:03:09.159 align:start position:0% about eventually next slide 00:03:09.159 --> 00:03:14.339 align:start position:0% about eventually next slide no<00:03:10.159> forward<00:03:10.730> let's<00:03:11.120> go<00:03:11.209> forward 00:03:14.339 --> 00:03:14.349 align:start position:0% 00:03:14.349 --> 00:03:17.770 align:start position:0% one<00:03:15.349> more<00:03:15.379> yeah<00:03:15.980> great<00:03:16.280> okay<00:03:16.939> so<00:03:17.000> here<00:03:17.419> here's 00:03:17.770 --> 00:03:17.780 align:start position:0% one more yeah great okay so here here's 00:03:17.780 --> 00:03:19.750 align:start position:0% one more yeah great okay so here here's just<00:03:18.019> to<00:03:18.109> show<00:03:18.290> you<00:03:18.319> a<00:03:18.500> little<00:03:18.859> bit<00:03:18.980> about<00:03:19.310> how 00:03:19.750 --> 00:03:19.760 align:start position:0% just to show you a little bit about how 00:03:19.760 --> 00:03:22.440 align:start position:0% just to show you a little bit about how we<00:03:19.819> think<00:03:20.319> services<00:03:21.319> and<00:03:21.590> how<00:03:21.650> a<00:03:21.680> blockchain 00:03:22.440 --> 00:03:22.450 align:start position:0% we think services and how a blockchain 00:03:22.450 --> 00:03:25.599 align:start position:0% we think services and how a blockchain application<00:03:23.450> platform<00:03:24.019> should<00:03:24.319> look<00:03:24.500> like<00:03:24.609> so 00:03:25.599 --> 00:03:25.609 align:start position:0% application platform should look like so 00:03:25.609 --> 00:03:27.789 align:start position:0% application platform should look like so I<00:03:25.639> stopped<00:03:26.150> keys<00:03:26.540> which<00:03:26.840> was<00:03:27.049> started<00:03:27.260> earlier 00:03:27.789 --> 00:03:27.799 align:start position:0% I stopped keys which was started earlier 00:03:27.799 --> 00:03:30.930 align:start position:0% I stopped keys which was started earlier by<00:03:28.639> the<00:03:28.669> chain<00:03:29.030> maker<00:03:29.269> I've<00:03:29.659> started<00:03:30.079> at<00:03:30.409> PFS 00:03:30.930 --> 00:03:30.940 align:start position:0% by the chain maker I've started at PFS 00:03:30.940 --> 00:03:33.399 align:start position:0% by the chain maker I've started at PFS and<00:03:31.940> I've<00:03:32.090> started<00:03:32.329> the<00:03:32.540> compiler<00:03:32.900> service 00:03:33.399 --> 00:03:33.409 align:start position:0% and I've started the compiler service 00:03:33.409 --> 00:03:35.229 align:start position:0% and I've started the compiler service and<00:03:33.680> when<00:03:33.889> I<00:03:33.919> run<00:03:34.129> errands<00:03:34.459> LS<00:03:34.729> you<00:03:34.909> can<00:03:35.060> see 00:03:35.229 --> 00:03:35.239 align:start position:0% and when I run errands LS you can see 00:03:35.239 --> 00:03:37.270 align:start position:0% and when I run errands LS you can see that<00:03:35.269> Keys<00:03:36.109> is<00:03:36.349> not<00:03:36.530> running<00:03:36.859> it's<00:03:37.099> got<00:03:37.250> a 00:03:37.270 --> 00:03:37.280 align:start position:0% that Keys is not running it's got a 00:03:37.280 --> 00:03:40.030 align:start position:0% that Keys is not running it's got a Dodge<00:03:37.579> compilers<00:03:38.359> and<00:03:38.540> I<00:03:38.870> PFS<00:03:39.290> those<00:03:39.889> are 00:03:40.030 --> 00:03:40.040 align:start position:0% Dodge compilers and I PFS those are 00:03:40.040 --> 00:03:41.710 align:start position:0% Dodge compilers and I PFS those are running<00:03:40.340> and<00:03:40.519> the<00:03:40.849> chain<00:03:41.090> is<00:03:41.239> also<00:03:41.479> still 00:03:41.710 --> 00:03:41.720 align:start position:0% running and the chain is also still 00:03:41.720 --> 00:03:43.689 align:start position:0% running and the chain is also still running<00:03:42.049> so<00:03:42.470> with<00:03:42.620> a<00:03:42.650> PFS<00:03:43.040> running<00:03:43.370> we<00:03:43.459> can<00:03:43.489> do 00:03:43.689 --> 00:03:43.699 align:start position:0% running so with a PFS running we can do 00:03:43.699 --> 00:03:45.699 align:start position:0% running so with a PFS running we can do something<00:03:43.939> simple<00:03:44.389> like<00:03:44.419> arrows<00:03:44.900> files<00:03:45.349> put 00:03:45.699 --> 00:03:45.709 align:start position:0% something simple like arrows files put 00:03:45.709 --> 00:03:48.280 align:start position:0% something simple like arrows files put some<00:03:46.400> random<00:03:46.760> file<00:03:47.030> and<00:03:47.299> that<00:03:47.810> will<00:03:47.989> spit<00:03:48.260> you 00:03:48.280 --> 00:03:48.290 align:start position:0% some random file and that will spit you 00:03:48.290 --> 00:03:50.520 align:start position:0% some random file and that will spit you out<00:03:48.379> the<00:03:48.620> hash<00:03:48.829> which<00:03:49.459> you<00:03:49.609> can<00:03:49.760> then<00:03:49.790> get<00:03:50.120> up 00:03:50.520 --> 00:03:50.530 align:start position:0% out the hash which you can then get up 00:03:50.530 --> 00:03:52.929 align:start position:0% out the hash which you can then get up with<00:03:51.530> arrows<00:03:51.829> files<00:03:52.040> get<00:03:52.340> and<00:03:52.579> give<00:03:52.729> it<00:03:52.760> an 00:03:52.929 --> 00:03:52.939 align:start position:0% with arrows files get and give it an 00:03:52.939 --> 00:03:55.659 align:start position:0% with arrows files get and give it an output<00:03:53.269> rename<00:03:53.659> your<00:03:53.780> file<00:03:54.019> or<00:03:54.260> share<00:03:54.500> it<00:03:54.669> with 00:03:55.659 --> 00:03:55.669 align:start position:0% output rename your file or share it with 00:03:55.669 --> 00:03:57.030 align:start position:0% output rename your file or share it with your<00:03:55.790> colleagues 00:03:57.030 --> 00:03:57.040 align:start position:0% your colleagues 00:03:57.040 --> 00:03:59.039 align:start position:0% your colleagues next<00:03:58.040> slide 00:03:59.039 --> 00:03:59.049 align:start position:0% next slide 00:03:59.049 --> 00:04:02.589 align:start position:0% next slide right<00:04:00.049> so<00:04:00.439> I'm<00:04:00.799> on<00:04:01.340> a<00:04:01.400> road<00:04:01.759> map<00:04:01.970> and<00:04:02.239> this<00:04:02.419> is 00:04:02.589 --> 00:04:02.599 align:start position:0% right so I'm on a road map and this is 00:04:02.599 --> 00:04:05.530 align:start position:0% right so I'm on a road map and this is where<00:04:02.840> docker<00:04:03.439> really<00:04:03.829> shines<00:04:04.129> is<00:04:04.489> uh<00:04:04.849> being 00:04:05.530 --> 00:04:05.540 align:start position:0% where docker really shines is uh being 00:04:05.540 --> 00:04:09.729 align:start position:0% where docker really shines is uh being able<00:04:05.930> to<00:04:06.229> modularize<00:04:07.419> the<00:04:08.419> client<00:04:09.229> type<00:04:09.470> and 00:04:09.729 --> 00:04:09.739 align:start position:0% able to modularize the client type and 00:04:09.739 --> 00:04:11.530 align:start position:0% able to modularize the client type and also<00:04:10.129> the<00:04:10.280> consensus<00:04:10.790> type<00:04:11.000> so<00:04:11.239> like<00:04:11.419> I 00:04:11.530 --> 00:04:11.540 align:start position:0% also the consensus type so like I 00:04:11.540 --> 00:04:14.679 align:start position:0% also the consensus type so like I mentioned<00:04:11.569> eras<00:04:12.229> TB<00:04:12.590> uses<00:04:12.979> tenormin<00:04:13.689> under 00:04:14.679 --> 00:04:14.689 align:start position:0% mentioned eras TB uses tenormin under 00:04:14.689 --> 00:04:16.629 align:start position:0% mentioned eras TB uses tenormin under the<00:04:14.810> hood<00:04:14.959> as<00:04:15.199> a<00:04:15.229> proof<00:04:15.560> of<00:04:15.739> stake<00:04:15.799> consensus 00:04:16.629 --> 00:04:16.639 align:start position:0% the hood as a proof of stake consensus 00:04:16.639 --> 00:04:19.060 align:start position:0% the hood as a proof of stake consensus algorithm<00:04:17.199> but<00:04:18.199> there's<00:04:18.380> been<00:04:18.530> a<00:04:18.590> lot<00:04:18.769> of<00:04:18.799> talk 00:04:19.060 --> 00:04:19.070 align:start position:0% algorithm but there's been a lot of talk 00:04:19.070 --> 00:04:21.310 align:start position:0% algorithm but there's been a lot of talk here<00:04:19.340> and<00:04:19.489> some<00:04:19.609> interest<00:04:20.030> by<00:04:20.570> the<00:04:20.599> various 00:04:21.310 --> 00:04:21.320 align:start position:0% here and some interest by the various 00:04:21.320 --> 00:04:24.490 align:start position:0% here and some interest by the various developers<00:04:21.859> of<00:04:22.159> getting<00:04:22.669> gas<00:04:22.970> /<00:04:23.479> TMS<00:04:24.050> P<00:04:24.259> SOT 00:04:24.490 --> 00:04:24.500 align:start position:0% developers of getting gas / TMS P SOT 00:04:24.500 --> 00:04:26.350 align:start position:0% developers of getting gas / TMS P SOT MSP<00:04:25.009> is<00:04:25.070> the<00:04:25.190> tournament<00:04:25.430> socket<00:04:25.909> protocol 00:04:26.350 --> 00:04:26.360 align:start position:0% MSP is the tournament socket protocol 00:04:26.360 --> 00:04:29.589 align:start position:0% MSP is the tournament socket protocol that<00:04:26.870> can<00:04:27.380> communicate<00:04:27.620> with<00:04:28.039> any<00:04:29.030> arbitrary 00:04:29.589 --> 00:04:29.599 align:start position:0% that can communicate with any arbitrary 00:04:29.599 --> 00:04:33.189 align:start position:0% that can communicate with any arbitrary client<00:04:30.080> and<00:04:30.919> so<00:04:31.370> this<00:04:31.669> so<00:04:32.539> you<00:04:32.840> know<00:04:32.930> would<00:04:33.080> be 00:04:33.189 --> 00:04:33.199 align:start position:0% client and so this so you know would be 00:04:33.199 --> 00:04:36.070 align:start position:0% client and so this so you know would be interesting<00:04:33.830> and<00:04:34.039> I<00:04:34.580> would<00:04:35.030> like<00:04:35.180> to<00:04:35.210> see<00:04:35.509> as 00:04:36.070 --> 00:04:36.080 align:start position:0% interesting and I would like to see as 00:04:36.080 --> 00:04:37.690 align:start position:0% interesting and I would like to see as many<00:04:36.320> different<00:04:36.770> clients<00:04:37.340> blockchain 00:04:37.690 --> 00:04:37.700 align:start position:0% many different clients blockchain 00:04:37.700 --> 00:04:40.629 align:start position:0% many different clients blockchain clients<00:04:38.270> oh<00:04:38.419> I<00:04:39.169> forgot<00:04:39.590> to<00:04:39.800> mention<00:04:39.860> eras<00:04:40.370> DB 00:04:40.629 --> 00:04:40.639 align:start position:0% clients oh I forgot to mention eras DB 00:04:40.639 --> 00:04:42.910 align:start position:0% clients oh I forgot to mention eras DB has<00:04:40.820> a<00:04:40.880> full<00:04:41.390> reimplement<00:04:42.020> a<00:04:42.170> shin<00:04:42.350> of<00:04:42.440> the<00:04:42.560> evm 00:04:42.910 --> 00:04:42.920 align:start position:0% has a full reimplement a shin of the evm 00:04:42.920 --> 00:04:45.670 align:start position:0% has a full reimplement a shin of the evm so<00:04:43.190> all<00:04:43.400> of<00:04:43.430> your<00:04:43.790> solidity<00:04:44.180> code<00:04:44.900> that<00:04:45.560> you've 00:04:45.670 --> 00:04:45.680 align:start position:0% so all of your solidity code that you've 00:04:45.680 --> 00:04:47.620 align:start position:0% so all of your solidity code that you've written<00:04:45.830> and<00:04:46.250> can<00:04:46.640> deploy<00:04:46.940> on<00:04:47.120> the<00:04:47.210> etherium 00:04:47.620 --> 00:04:47.630 align:start position:0% written and can deploy on the etherium 00:04:47.630 --> 00:04:50.680 align:start position:0% written and can deploy on the etherium test<00:04:47.930> net<00:04:48.110> or<00:04:48.260> main<00:04:48.410> that<00:04:48.620> will<00:04:49.490> work<00:04:49.670> on<00:04:50.540> an 00:04:50.680 --> 00:04:50.690 align:start position:0% test net or main that will work on an 00:04:50.690 --> 00:04:52.620 align:start position:0% test net or main that will work on an eris<00:04:50.960> DB 00:04:52.620 --> 00:04:52.630 align:start position:0% eris DB 00:04:52.630 --> 00:04:55.170 align:start position:0% eris DB no<00:04:53.630> go<00:04:53.840> back<00:04:53.990> uh 00:04:55.170 --> 00:04:55.180 align:start position:0% no go back uh 00:04:55.180 --> 00:04:58.000 align:start position:0% no go back uh what<00:04:56.180> was<00:04:56.270> my<00:04:56.390> last<00:04:56.570> point<00:04:56.780> here<00:04:57.010> yeah 00:04:58.000 --> 00:04:58.010 align:start position:0% what was my last point here yeah 00:04:58.010 --> 00:04:59.770 align:start position:0% what was my last point here yeah basically<00:04:58.250> so<00:04:58.640> I<00:04:58.670> envisioned<00:04:59.180> and<00:04:59.510> we're 00:04:59.770 --> 00:04:59.780 align:start position:0% basically so I envisioned and we're 00:04:59.780 --> 00:05:01.180 align:start position:0% basically so I envisioned and we're working<00:04:59.960> towards<00:05:00.410> this<00:05:00.590> to<00:05:00.800> be<00:05:00.890> able<00:05:00.980> to 00:05:01.180 --> 00:05:01.190 align:start position:0% working towards this to be able to 00:05:01.190 --> 00:05:03.490 align:start position:0% working towards this to be able to choose<00:05:01.400> any<00:05:01.580> client<00:05:02.000> type<00:05:02.180> B<00:05:02.450> it<00:05:02.540> gasps<00:05:02.810> CPP 00:05:03.490 --> 00:05:03.500 align:start position:0% choose any client type B it gasps CPP 00:05:03.500 --> 00:05:05.920 align:start position:0% choose any client type B it gasps CPP parody<00:05:04.070> and<00:05:04.250> choose<00:05:04.670> any<00:05:04.910> consensus<00:05:05.330> type<00:05:05.690> and 00:05:05.920 --> 00:05:05.930 align:start position:0% parody and choose any consensus type and 00:05:05.930 --> 00:05:08.110 align:start position:0% parody and choose any consensus type and mix<00:05:06.380> and<00:05:06.530> match<00:05:06.680> and<00:05:07.010> so<00:05:07.370> you<00:05:07.460> could<00:05:07.580> start<00:05:07.820> 5 00:05:08.110 --> 00:05:08.120 align:start position:0% mix and match and so you could start 5 00:05:08.120 --> 00:05:11.560 align:start position:0% mix and match and so you could start 5 10<00:05:08.540> chains<00:05:08.900> of<00:05:09.140> any<00:05:09.260> combination<00:05:09.920> and<00:05:10.850> and<00:05:11.240> do 00:05:11.560 --> 00:05:11.570 align:start position:0% 10 chains of any combination and and do 00:05:11.570 --> 00:05:13.750 align:start position:0% 10 chains of any combination and and do your<00:05:11.690> benchmarks<00:05:12.170> with<00:05:12.320> that<00:05:12.500> and<00:05:12.830> to<00:05:13.550> see 00:05:13.750 --> 00:05:13.760 align:start position:0% your benchmarks with that and to see 00:05:13.760 --> 00:05:16.870 align:start position:0% your benchmarks with that and to see what<00:05:14.090> works<00:05:14.330> best<00:05:14.660> for<00:05:14.840> your<00:05:15.350> application<00:05:15.880> and 00:05:16.870 --> 00:05:16.880 align:start position:0% what works best for your application and 00:05:16.880 --> 00:05:18.750 align:start position:0% what works best for your application and I<00:05:16.970> want<00:05:17.120> to<00:05:17.150> make<00:05:17.300> one<00:05:17.330> final<00:05:17.600> point<00:05:17.810> here<00:05:18.110> uh 00:05:18.750 --> 00:05:18.760 align:start position:0% I want to make one final point here uh 00:05:18.760 --> 00:05:21.820 align:start position:0% I want to make one final point here uh yes<00:05:19.760> we<00:05:20.000> make<00:05:20.180> permission<00:05:20.840> chains<00:05:21.290> we're<00:05:21.710> not 00:05:21.820 --> 00:05:21.830 align:start position:0% yes we make permission chains we're not 00:05:21.830 --> 00:05:23.380 align:start position:0% yes we make permission chains we're not we're<00:05:22.160> not<00:05:22.190> necessarily<00:05:22.760> in<00:05:22.850> the<00:05:22.940> private 00:05:23.380 --> 00:05:23.390 align:start position:0% we're not necessarily in the private 00:05:23.390 --> 00:05:24.880 align:start position:0% we're not necessarily in the private chain<00:05:23.720> space<00:05:24.050> and<00:05:24.260> there's<00:05:24.380> a<00:05:24.470> crucial 00:05:24.880 --> 00:05:24.890 align:start position:0% chain space and there's a crucial 00:05:24.890 --> 00:05:27.060 align:start position:0% chain space and there's a crucial distinction<00:05:25.250> there<00:05:25.490> that<00:05:25.670> the<00:05:25.760> media<00:05:26.060> hasn't 00:05:27.060 --> 00:05:27.070 align:start position:0% distinction there that the media hasn't 00:05:27.070 --> 00:05:29.130 align:start position:0% distinction there that the media hasn't noticed<00:05:28.070> and<00:05:28.310> so 00:05:29.130 --> 00:05:29.140 align:start position:0% noticed and so 00:05:29.140 --> 00:05:31.870 align:start position:0% noticed and so yeah<00:05:30.140> we<00:05:30.410> hope<00:05:30.860> that<00:05:30.920> you<00:05:31.160> can<00:05:31.310> try<00:05:31.730> out<00:05:31.760> our 00:05:31.870 --> 00:05:31.880 align:start position:0% yeah we hope that you can try out our 00:05:31.880 --> 00:05:35.550 align:start position:0% yeah we hope that you can try out our tool<00:05:32.090> and<00:05:32.450> up<00:05:33.230> next<00:05:33.680> we'll<00:05:33.800> talk 00:05:35.550 --> 00:05:35.560 align:start position:0% tool and up next we'll talk 00:05:35.560 --> 00:05:38.220 align:start position:0% tool and up next we'll talk hey<00:05:36.560> guys<00:05:36.740> can<00:05:37.100> I<00:05:37.280> get<00:05:37.430> the<00:05:37.490> next<00:05:37.670> slide<00:05:37.790> please 00:05:38.220 --> 00:05:38.230 align:start position:0% hey guys can I get the next slide please 00:05:38.230 --> 00:05:40.420 align:start position:0% hey guys can I get the next slide please alright<00:05:39.230> so<00:05:39.500> here<00:05:40.010> I'm<00:05:40.130> going<00:05:40.250> to<00:05:40.340> be 00:05:40.420 --> 00:05:40.430 align:start position:0% alright so here I'm going to be 00:05:40.430 --> 00:05:42.370 align:start position:0% alright so here I'm going to be presenting<00:05:40.580> the<00:05:40.910> eris<00:05:41.120> package<00:05:41.450> manager<00:05:41.870> and 00:05:42.370 --> 00:05:42.380 align:start position:0% presenting the eris package manager and 00:05:42.380 --> 00:05:43.900 align:start position:0% presenting the eris package manager and I<00:05:42.620> would<00:05:42.740> like<00:05:42.890> to<00:05:42.920> go<00:05:43.130> ahead<00:05:43.160> and<00:05:43.460> frame<00:05:43.610> it<00:05:43.640> as 00:05:43.900 --> 00:05:43.910 align:start position:0% I would like to go ahead and frame it as 00:05:43.910 --> 00:05:46.540 align:start position:0% I would like to go ahead and frame it as the<00:05:44.060> ease<00:05:44.210> of<00:05:44.240> NPM<00:05:44.810> the<00:05:45.500> simple<00:05:45.830> coordination 00:05:46.540 --> 00:05:46.550 align:start position:0% the ease of NPM the simple coordination 00:05:46.550 --> 00:05:50.010 align:start position:0% the ease of NPM the simple coordination of<00:05:46.670> Chef<00:05:47.360> all<00:05:47.630> running<00:05:48.470> through<00:05:48.680> solidity<00:05:49.040> now 00:05:50.010 --> 00:05:50.020 align:start position:0% of Chef all running through solidity now 00:05:50.020 --> 00:05:52.180 align:start position:0% of Chef all running through solidity now this<00:05:51.020> runs<00:05:51.260> through<00:05:51.470> the<00:05:51.590> simple<00:05:51.830> workflow 00:05:52.180 --> 00:05:52.190 align:start position:0% this runs through the simple workflow 00:05:52.190 --> 00:05:54.490 align:start position:0% this runs through the simple workflow right<00:05:52.670> here<00:05:53.030> there<00:05:53.810> is<00:05:53.930> a<00:05:53.960> disclaimer<00:05:54.230> though 00:05:54.490 --> 00:05:54.500 align:start position:0% right here there is a disclaimer though 00:05:54.500 --> 00:05:55.750 align:start position:0% right here there is a disclaimer though in<00:05:54.770> it<00:05:54.920> and<00:05:55.070> installer<00:05:55.400> on<00:05:55.520> the<00:05:55.580> roadmap 00:05:55.750 --> 00:05:55.760 align:start position:0% in it and installer on the roadmap 00:05:55.760 --> 00:05:57.700 align:start position:0% in it and installer on the roadmap they're<00:05:56.210> not<00:05:56.420> yet<00:05:56.630> implemented<00:05:57.020> but<00:05:57.470> is 00:05:57.700 --> 00:05:57.710 align:start position:0% they're not yet implemented but is 00:05:57.710 --> 00:05:59.500 align:start position:0% they're not yet implemented but is simply<00:05:58.190> just<00:05:58.430> this<00:05:58.670> you<00:05:58.970> just<00:05:59.210> go<00:05:59.300> ahead<00:05:59.390> and 00:05:59.500 --> 00:05:59.510 align:start position:0% simply just this you just go ahead and 00:05:59.510 --> 00:06:01.300 align:start position:0% simply just this you just go ahead and is<00:05:59.750> your<00:06:00.110> project<00:06:00.290> install<00:06:01.190> your 00:06:01.300 --> 00:06:01.310 align:start position:0% is your project install your 00:06:01.310 --> 00:06:03.160 align:start position:0% is your project install your dependencies<00:06:01.850> and<00:06:02.120> deploy<00:06:02.630> and<00:06:02.930> run<00:06:02.960> your 00:06:03.160 --> 00:06:03.170 align:start position:0% dependencies and deploy and run your 00:06:03.170 --> 00:06:05.430 align:start position:0% dependencies and deploy and run your code<00:06:03.500> on<00:06:03.800> your<00:06:03.830> running<00:06:04.250> chain 00:06:05.430 --> 00:06:05.440 align:start position:0% code on your running chain 00:06:05.440 --> 00:06:08.590 align:start position:0% code on your running chain next<00:06:06.440> slide<00:06:06.500> please<00:06:06.760> why<00:06:07.760> do<00:06:07.820> we<00:06:08.120> need<00:06:08.300> another 00:06:08.590 --> 00:06:08.600 align:start position:0% next slide please why do we need another 00:06:08.600 --> 00:06:11.230 align:start position:0% next slide please why do we need another package<00:06:09.200> manager<00:06:09.680> why<00:06:10.010> do<00:06:10.550> we<00:06:10.790> need<00:06:10.940> to<00:06:11.000> go 00:06:11.230 --> 00:06:11.240 align:start position:0% package manager why do we need to go 00:06:11.240 --> 00:06:13.000 align:start position:0% package manager why do we need to go ahead<00:06:11.270> and<00:06:11.810> have<00:06:12.020> this<00:06:12.260> when<00:06:12.470> we<00:06:12.590> have<00:06:12.710> so<00:06:12.890> many 00:06:13.000 --> 00:06:13.010 align:start position:0% ahead and have this when we have so many 00:06:13.010 --> 00:06:14.560 align:start position:0% ahead and have this when we have so many others<00:06:13.340> to<00:06:13.730> go<00:06:13.850> ahead<00:06:13.970> and<00:06:14.210> handle<00:06:14.420> ourselves 00:06:14.560 --> 00:06:14.570 align:start position:0% others to go ahead and handle ourselves 00:06:14.570 --> 00:06:16.570 align:start position:0% others to go ahead and handle ourselves well<00:06:15.440> there<00:06:15.740> are<00:06:15.770> specific<00:06:16.250> problems 00:06:16.570 --> 00:06:16.580 align:start position:0% well there are specific problems 00:06:16.580 --> 00:06:18.310 align:start position:0% well there are specific problems inherent<00:06:16.760> in<00:06:17.120> utilizing<00:06:17.630> block<00:06:17.780> chains<00:06:18.050> and 00:06:18.310 --> 00:06:18.320 align:start position:0% inherent in utilizing block chains and 00:06:18.320 --> 00:06:20.950 align:start position:0% inherent in utilizing block chains and smart<00:06:18.560> contracts<00:06:19.360> there's<00:06:20.360> the<00:06:20.540> problem<00:06:20.690> of 00:06:20.950 --> 00:06:20.960 align:start position:0% smart contracts there's the problem of 00:06:20.960 --> 00:06:23.140 align:start position:0% smart contracts there's the problem of single<00:06:21.380> versus<00:06:21.710> multiple<00:06:22.010> parties<00:06:22.430> what<00:06:23.060> do 00:06:23.140 --> 00:06:23.150 align:start position:0% single versus multiple parties what do 00:06:23.150 --> 00:06:25.690 align:start position:0% single versus multiple parties what do we<00:06:23.240> mean<00:06:23.420> by<00:06:23.450> this<00:06:23.860> in<00:06:24.860> the<00:06:24.980> top<00:06:25.190> right<00:06:25.460> right 00:06:25.690 --> 00:06:25.700 align:start position:0% we mean by this in the top right right 00:06:25.700 --> 00:06:28.980 align:start position:0% we mean by this in the top right right here<00:06:26.110> you<00:06:27.110> have<00:06:27.290> the<00:06:27.560> old<00:06:27.950> traditional<00:06:28.550> model 00:06:28.980 --> 00:06:28.990 align:start position:0% here you have the old traditional model 00:06:28.990 --> 00:06:31.660 align:start position:0% here you have the old traditional model this<00:06:29.990> was<00:06:30.230> one<00:06:30.530> person<00:06:30.770> executing<00:06:31.310> code<00:06:31.430> in<00:06:31.610> a 00:06:31.660 --> 00:06:31.670 align:start position:0% this was one person executing code in a 00:06:31.670 --> 00:06:33.910 align:start position:0% this was one person executing code in a file<00:06:31.910> system<00:06:32.180> that<00:06:32.840> one<00:06:33.110> computer<00:06:33.530> and<00:06:33.680> only 00:06:33.910 --> 00:06:33.920 align:start position:0% file system that one computer and only 00:06:33.920 --> 00:06:35.920 align:start position:0% file system that one computer and only that<00:06:34.040> computer<00:06:34.490> controlled<00:06:35.060> as<00:06:35.510> nickel<00:06:35.840> I'm 00:06:35.920 --> 00:06:35.930 align:start position:0% that computer controlled as nickel I'm 00:06:35.930 --> 00:06:38.200 align:start position:0% that computer controlled as nickel I'm asheghi<00:06:36.200> in<00:06:36.380> from<00:06:36.590> dapple<00:06:36.950> explained<00:06:37.730> in<00:06:38.120> his 00:06:38.200 --> 00:06:38.210 align:start position:0% asheghi in from dapple explained in his 00:06:38.210 --> 00:06:40.090 align:start position:0% asheghi in from dapple explained in his talk<00:06:38.360> yesterday<00:06:38.630> we<00:06:39.530> are<00:06:39.680> in<00:06:39.770> a<00:06:39.860> completely 00:06:40.090 --> 00:06:40.100 align:start position:0% talk yesterday we are in a completely 00:06:40.100 --> 00:06:42.130 align:start position:0% talk yesterday we are in a completely new<00:06:40.670> paradigm<00:06:41.210> where<00:06:41.390> about<00:06:41.540> a<00:06:41.570> code<00:06:41.810> is<00:06:41.960> not 00:06:42.130 --> 00:06:42.140 align:start position:0% new paradigm where about a code is not 00:06:42.140 --> 00:06:44.740 align:start position:0% new paradigm where about a code is not meant<00:06:42.560> to<00:06:42.830> be<00:06:42.860> run<00:06:43.460> in<00:06:43.490> an<00:06:43.730> isolated<00:06:44.180> setting 00:06:44.740 --> 00:06:44.750 align:start position:0% meant to be run in an isolated setting 00:06:44.750 --> 00:06:46.990 align:start position:0% meant to be run in an isolated setting but<00:06:45.020> rather<00:06:45.170> collaboratively<00:06:45.950> acted<00:06:46.490> upon<00:06:46.730> as 00:06:46.990 --> 00:06:47.000 align:start position:0% but rather collaboratively acted upon as 00:06:47.000 --> 00:06:49.180 align:start position:0% but rather collaboratively acted upon as can<00:06:47.750> be<00:06:47.780> seen<00:06:47.900> and<00:06:48.470> displayed<00:06:48.800> by<00:06:48.920> the<00:06:48.980> many 00:06:49.180 --> 00:06:49.190 align:start position:0% can be seen and displayed by the many 00:06:49.190 --> 00:06:52.090 align:start position:0% can be seen and displayed by the many smiling<00:06:49.430> faces<00:06:49.610> over<00:06:50.060> here<00:06:50.710> this<00:06:51.710> calls<00:06:51.920> for<00:06:52.070> a 00:06:52.090 --> 00:06:52.100 align:start position:0% smiling faces over here this calls for a 00:06:52.100 --> 00:06:53.530 align:start position:0% smiling faces over here this calls for a specific<00:06:52.280> design<00:06:52.790> to<00:06:53.000> handle<00:06:53.270> this<00:06:53.360> new 00:06:53.530 --> 00:06:53.540 align:start position:0% specific design to handle this new 00:06:53.540 --> 00:06:54.370 align:start position:0% specific design to handle this new paradigm 00:06:54.370 --> 00:06:54.380 align:start position:0% paradigm 00:06:54.380 --> 00:06:57.010 align:start position:0% paradigm secondly<00:06:55.310> a<00:06:55.550> terrace<00:06:56.120> a<00:06:56.300> we<00:06:56.600> don't<00:06:56.780> believe<00:06:56.960> in 00:06:57.010 --> 00:06:57.020 align:start position:0% secondly a terrace a we don't believe in 00:06:57.020 --> 00:06:59.410 align:start position:0% secondly a terrace a we don't believe in a<00:06:57.320> one<00:06:57.560> chain<00:06:57.830> to<00:06:58.010> rule<00:06:58.250> them<00:06:58.430> all<00:06:58.580> design<00:06:59.120> and 00:06:59.410 --> 00:06:59.420 align:start position:0% a one chain to rule them all design and 00:06:59.420 --> 00:07:00.790 align:start position:0% a one chain to rule them all design and believe<00:06:59.570> that<00:06:59.600> the<00:06:59.840> world<00:07:00.020> will<00:07:00.260> inherently 00:07:00.790 --> 00:07:00.800 align:start position:0% believe that the world will inherently 00:07:00.800 --> 00:07:04.000 align:start position:0% believe that the world will inherently cater<00:07:01.220> to<00:07:01.580> a<00:07:01.610> multi-chain<00:07:02.480> mindset<00:07:03.050> even<00:07:03.890> for 00:07:04.000 --> 00:07:04.010 align:start position:0% cater to a multi-chain mindset even for 00:07:04.010 --> 00:07:06.220 align:start position:0% cater to a multi-chain mindset even for those<00:07:04.130> that<00:07:04.310> do<00:07:04.640> believe<00:07:05.420> in<00:07:05.570> a<00:07:05.660> maximalist 00:07:06.220 --> 00:07:06.230 align:start position:0% those that do believe in a maximalist 00:07:06.230 --> 00:07:09.100 align:start position:0% those that do believe in a maximalist one<00:07:06.710> chain<00:07:07.010> to<00:07:07.160> rule<00:07:07.340> them<00:07:07.520> all<00:07:07.640> world<00:07:08.360> can 00:07:09.100 --> 00:07:09.110 align:start position:0% one chain to rule them all world can 00:07:09.110 --> 00:07:10.870 align:start position:0% one chain to rule them all world can agree<00:07:09.410> that<00:07:09.680> there<00:07:09.860> is<00:07:10.010> a<00:07:10.040> high<00:07:10.400> amount<00:07:10.670> of 00:07:10.870 --> 00:07:10.880 align:start position:0% agree that there is a high amount of 00:07:10.880 --> 00:07:12.760 align:start position:0% agree that there is a high amount of utility<00:07:11.300> and<00:07:11.420> separated<00:07:11.810> test<00:07:12.020> networks<00:07:12.410> for 00:07:12.760 --> 00:07:12.770 align:start position:0% utility and separated test networks for 00:07:12.770 --> 00:07:16.500 align:start position:0% utility and separated test networks for chains<00:07:13.570> this<00:07:14.570> calls<00:07:14.870> for<00:07:15.260> package<00:07:15.890> management 00:07:16.500 --> 00:07:16.510 align:start position:0% chains this calls for package management 00:07:16.510 --> 00:07:18.970 align:start position:0% chains this calls for package management that<00:07:17.510> can<00:07:17.630> coordinate<00:07:18.050> and<00:07:18.260> maintain<00:07:18.650> smart 00:07:18.970 --> 00:07:18.980 align:start position:0% that can coordinate and maintain smart 00:07:18.980 --> 00:07:20.770 align:start position:0% that can coordinate and maintain smart contracts<00:07:19.520> over<00:07:19.970> multiple<00:07:20.270> chains<00:07:20.510> and 00:07:20.770 --> 00:07:20.780 align:start position:0% contracts over multiple chains and 00:07:20.780 --> 00:07:24.040 align:start position:0% contracts over multiple chains and distributed<00:07:21.290> ledgers<00:07:21.820> thirdly<00:07:23.050> verification 00:07:24.040 --> 00:07:24.050 align:start position:0% distributed ledgers thirdly verification 00:07:24.050 --> 00:07:26.260 align:start position:0% distributed ledgers thirdly verification simple<00:07:24.560> enough<00:07:24.740> we<00:07:25.220> want<00:07:25.430> to<00:07:25.520> make<00:07:25.610> sure<00:07:25.640> that 00:07:26.260 --> 00:07:26.270 align:start position:0% simple enough we want to make sure that 00:07:26.270 --> 00:07:27.970 align:start position:0% simple enough we want to make sure that what<00:07:26.540> we<00:07:26.660> had<00:07:26.810> exists<00:07:27.410> on<00:07:27.650> the<00:07:27.770> chain<00:07:27.950> and 00:07:27.970 --> 00:07:27.980 align:start position:0% what we had exists on the chain and 00:07:27.980 --> 00:07:30.030 align:start position:0% what we had exists on the chain and works<00:07:28.310> as<00:07:28.430> expected<00:07:28.550> and 00:07:30.030 --> 00:07:30.040 align:start position:0% works as expected and 00:07:30.040 --> 00:07:31.690 align:start position:0% works as expected and expect<00:07:31.040> that<00:07:31.100> we're<00:07:31.400> going<00:07:31.520> to<00:07:31.580> be<00:07:31.640> working 00:07:31.690 --> 00:07:31.700 align:start position:0% expect that we're going to be working 00:07:31.700 --> 00:07:33.600 align:start position:0% expect that we're going to be working with<00:07:31.880> them<00:07:32.180> and<00:07:32.480> upside 00:07:33.600 --> 00:07:33.610 align:start position:0% with them and upside 00:07:33.610 --> 00:07:37.080 align:start position:0% with them and upside forth<00:07:34.610> finally<00:07:35.150> we<00:07:35.600> have<00:07:35.900> to<00:07:36.140> keep<00:07:36.410> in<00:07:36.530> mind 00:07:37.080 --> 00:07:37.090 align:start position:0% forth finally we have to keep in mind 00:07:37.090 --> 00:07:41.290 align:start position:0% forth finally we have to keep in mind contract<00:07:38.090> reuse<00:07:38.450> as<00:07:38.720> we<00:07:38.900> now<00:07:39.200> are<00:07:39.440> acting<00:07:40.300> in 00:07:41.290 --> 00:07:41.300 align:start position:0% contract reuse as we now are acting in 00:07:41.300 --> 00:07:43.540 align:start position:0% contract reuse as we now are acting in an<00:07:41.420> environment<00:07:41.840> where<00:07:41.900> economics<00:07:42.560> is 00:07:43.540 --> 00:07:43.550 align:start position:0% an environment where economics is 00:07:43.550 --> 00:07:46.480 align:start position:0% an environment where economics is actually<00:07:43.970> a<00:07:44.000> factor<00:07:44.360> in<00:07:44.510> your<00:07:44.630> code<00:07:44.870> and<00:07:45.490> calls 00:07:46.480 --> 00:07:46.490 align:start position:0% actually a factor in your code and calls 00:07:46.490 --> 00:07:48.010 align:start position:0% actually a factor in your code and calls for<00:07:46.580> using<00:07:47.030> the<00:07:47.090> least<00:07:47.270> amount<00:07:47.390> of<00:07:47.600> resources 00:07:48.010 --> 00:07:48.020 align:start position:0% for using the least amount of resources 00:07:48.020 --> 00:07:50.610 align:start position:0% for using the least amount of resources AKA<00:07:48.380> gasps<00:07:48.710> as<00:07:49.100> necessary 00:07:50.610 --> 00:07:50.620 align:start position:0% AKA gasps as necessary 00:07:50.620 --> 00:07:53.980 align:start position:0% AKA gasps as necessary next<00:07:51.620> slide<00:07:51.680> please<00:07:52.030> moving<00:07:53.030> to<00:07:53.150> where<00:07:53.180> EPM 00:07:53.980 --> 00:07:53.990 align:start position:0% next slide please moving to where EPM 00:07:53.990 --> 00:07:56.560 align:start position:0% next slide please moving to where EPM chef<00:07:54.260> like<00:07:54.440> qualities<00:07:54.860> shine<00:07:55.180> it's<00:07:56.180> a<00:07:56.360> little 00:07:56.560 --> 00:07:56.570 align:start position:0% chef like qualities shine it's a little 00:07:56.570 --> 00:07:59.740 align:start position:0% chef like qualities shine it's a little thing<00:07:56.720> right<00:07:56.840> here<00:07:56.900> the<00:07:57.380> EPM<00:07:57.790> BPM<00:07:58.790> llamo<00:07:59.330> file 00:07:59.740 --> 00:07:59.750 align:start position:0% thing right here the EPM BPM llamo file 00:07:59.750 --> 00:08:01.930 align:start position:0% thing right here the EPM BPM llamo file is<00:07:59.960> on<00:08:00.050> the<00:08:00.200> right<00:08:00.380> and<00:08:00.650> on<00:08:01.250> my<00:08:01.430> left<00:08:01.460> is<00:08:01.850> a 00:08:01.930 --> 00:08:01.940 align:start position:0% is on the right and on my left is a 00:08:01.940 --> 00:08:03.880 align:start position:0% is on the right and on my left is a solidity<00:08:02.840> smart<00:08:03.140> contract<00:08:03.560> that<00:08:03.680> I<00:08:03.710> thought 00:08:03.880 --> 00:08:03.890 align:start position:0% solidity smart contract that I thought 00:08:03.890 --> 00:08:05.890 align:start position:0% solidity smart contract that I thought would<00:08:04.010> be<00:08:04.070> good<00:08:04.280> for<00:08:04.520> this<00:08:04.670> example<00:08:05.000> you<00:08:05.870> can 00:08:05.890 --> 00:08:05.900 align:start position:0% would be good for this example you can 00:08:05.900 --> 00:08:07.840 align:start position:0% would be good for this example you can see<00:08:06.050> right<00:08:06.170> here<00:08:06.800> that<00:08:06.860> we<00:08:07.250> have<00:08:07.460> numerous 00:08:07.840 --> 00:08:07.850 align:start position:0% see right here that we have numerous 00:08:07.850 --> 00:08:09.430 align:start position:0% see right here that we have numerous different<00:08:08.270> jobs<00:08:08.510> running<00:08:08.780> we<00:08:09.050> can<00:08:09.080> go<00:08:09.350> ahead 00:08:09.430 --> 00:08:09.440 align:start position:0% different jobs running we can go ahead 00:08:09.440 --> 00:08:11.320 align:start position:0% different jobs running we can go ahead and<00:08:09.560> set<00:08:09.920> an<00:08:10.100> initial<00:08:10.280> value<00:08:10.490> that<00:08:11.030> we<00:08:11.120> want<00:08:11.270> to 00:08:11.320 --> 00:08:11.330 align:start position:0% and set an initial value that we want to 00:08:11.330 --> 00:08:13.510 align:start position:0% and set an initial value that we want to go<00:08:11.390> ahead<00:08:11.480> and<00:08:11.660> pass<00:08:11.810> in<00:08:12.080> you<00:08:12.860> go<00:08:13.010> ahead<00:08:13.130> and 00:08:13.510 --> 00:08:13.520 align:start position:0% go ahead and pass in you go ahead and 00:08:13.520 --> 00:08:15.730 align:start position:0% go ahead and pass in you go ahead and can<00:08:13.820> create<00:08:14.180> a<00:08:14.210> deploy<00:08:14.600> method<00:08:15.020> call<00:08:15.620> the 00:08:15.730 --> 00:08:15.740 align:start position:0% can create a deploy method call the 00:08:15.740 --> 00:08:17.770 align:start position:0% can create a deploy method call the contract<00:08:16.310> GS<00:08:16.640> factory<00:08:16.970> that's<00:08:17.060> soul<00:08:17.330> and<00:08:17.630> name 00:08:17.770 --> 00:08:17.780 align:start position:0% contract GS factory that's soul and name 00:08:17.780 --> 00:08:20.440 align:start position:0% contract GS factory that's soul and name an<00:08:17.900> instance<00:08:18.380> of<00:08:18.620> it<00:08:18.800> and<00:08:19.040> then<00:08:19.940> go<00:08:20.120> ahead<00:08:20.150> and 00:08:20.440 --> 00:08:20.450 align:start position:0% an instance of it and then go ahead and 00:08:20.450 --> 00:08:23.170 align:start position:0% an instance of it and then go ahead and call<00:08:20.570> that<00:08:20.810> instance<00:08:21.200> further<00:08:21.470> on<00:08:22.030> then<00:08:23.030> you 00:08:23.170 --> 00:08:23.180 align:start position:0% call that instance further on then you 00:08:23.180 --> 00:08:24.430 align:start position:0% call that instance further on then you can<00:08:23.300> go<00:08:23.390> ahead<00:08:23.480> and<00:08:23.600> continue<00:08:23.810> to<00:08:24.050> call<00:08:24.230> the 00:08:24.430 --> 00:08:24.440 align:start position:0% can go ahead and continue to call the 00:08:24.440 --> 00:08:26.830 align:start position:0% can go ahead and continue to call the contract<00:08:24.950> function<00:08:25.550> for<00:08:25.850> create<00:08:26.180> at<00:08:26.510> that 00:08:26.830 --> 00:08:26.840 align:start position:0% contract function for create at that 00:08:26.840 --> 00:08:29.740 align:start position:0% contract function for create at that deploy<00:08:27.650> GS<00:08:28.040> contract<00:08:28.550> and<00:08:29.060> for<00:08:29.600> those<00:08:29.690> who 00:08:29.740 --> 00:08:29.750 align:start position:0% deploy GS contract and for those who 00:08:29.750 --> 00:08:31.240 align:start position:0% deploy GS contract and for those who have<00:08:30.050> been<00:08:30.230> in<00:08:30.380> the<00:08:30.410> UNIX<00:08:30.800> system<00:08:31.100> that<00:08:31.220> should 00:08:31.240 --> 00:08:31.250 align:start position:0% have been in the UNIX system that should 00:08:31.250 --> 00:08:32.830 align:start position:0% have been in the UNIX system that should be<00:08:31.400> very<00:08:31.580> familiar<00:08:31.670> you<00:08:32.360> have<00:08:32.510> a<00:08:32.539> little 00:08:32.830 --> 00:08:32.840 align:start position:0% be very familiar you have a little 00:08:32.840 --> 00:08:34.600 align:start position:0% be very familiar you have a little dollar<00:08:33.200> sign<00:08:33.469> to<00:08:33.620> go<00:08:33.710> ahead<00:08:33.800> and<00:08:34.039> call<00:08:34.250> back 00:08:34.600 --> 00:08:34.610 align:start position:0% dollar sign to go ahead and call back 00:08:34.610 --> 00:08:37.839 align:start position:0% dollar sign to go ahead and call back what<00:08:35.210> you<00:08:35.330> already<00:08:35.630> set<00:08:36.080> and<00:08:36.430> you<00:08:37.430> have<00:08:37.550> to<00:08:37.640> set 00:08:37.839 --> 00:08:37.849 align:start position:0% what you already set and you have to set 00:08:37.849 --> 00:08:40.089 align:start position:0% what you already set and you have to set storage<00:08:38.330> which<00:08:38.690> will<00:08:38.900> go<00:08:39.020> ahead<00:08:39.140> and<00:08:39.500> call<00:08:39.890> the 00:08:40.089 --> 00:08:40.099 align:start position:0% storage which will go ahead and call the 00:08:40.099 --> 00:08:43.330 align:start position:0% storage which will go ahead and call the set<00:08:40.310> function<00:08:40.550> and<00:08:41.169> input<00:08:42.169> the<00:08:42.200> data<00:08:42.560> from<00:08:43.010> the 00:08:43.330 --> 00:08:43.340 align:start position:0% set function and input the data from the 00:08:43.340 --> 00:08:45.040 align:start position:0% set function and input the data from the set<00:08:43.520> storage<00:08:43.820> base<00:08:44.060> made<00:08:44.420> at<00:08:44.510> the<00:08:44.570> top<00:08:44.780> so 00:08:45.040 --> 00:08:45.050 align:start position:0% set storage base made at the top so 00:08:45.050 --> 00:08:47.770 align:start position:0% set storage base made at the top so passing<00:08:45.380> in<00:08:45.470> the<00:08:45.500> number<00:08:45.770> five<00:08:45.950> and<00:08:46.540> you<00:08:47.540> have 00:08:47.770 --> 00:08:47.780 align:start position:0% passing in the number five and you have 00:08:47.780 --> 00:08:50.790 align:start position:0% passing in the number five and you have a<00:08:48.080> query<00:08:48.320> contract<00:08:48.920> which<00:08:49.130> now<00:08:49.400> for<00:08:50.360> now 00:08:50.790 --> 00:08:50.800 align:start position:0% a query contract which now for now 00:08:50.800 --> 00:08:54.820 align:start position:0% a query contract which now for now forces<00:08:51.800> the<00:08:52.630> the<00:08:53.630> chain<00:08:53.900> to<00:08:53.930> not<00:08:54.230> be<00:08:54.380> altered 00:08:54.820 --> 00:08:54.830 align:start position:0% forces the the chain to not be altered 00:08:54.830 --> 00:08:56.010 align:start position:0% forces the the chain to not be altered and 00:08:56.010 --> 00:08:56.020 align:start position:0% and 00:08:56.020 --> 00:08:59.640 align:start position:0% and next<00:08:57.020> slide<00:08:57.260> please 00:08:59.640 --> 00:08:59.650 align:start position:0% 00:08:59.650 --> 00:09:02.500 align:start position:0% alright<00:09:00.650> and<00:09:00.830> for<00:09:01.220> finally<00:09:01.910> further<00:09:02.240> on<00:09:02.390> our 00:09:02.500 --> 00:09:02.510 align:start position:0% alright and for finally further on our 00:09:02.510 --> 00:09:05.440 align:start position:0% alright and for finally further on our road<00:09:02.660> map<00:09:02.690> we<00:09:03.350> are<00:09:03.680> going<00:09:04.010> to<00:09:04.070> be<00:09:04.190> looking<00:09:05.180> to 00:09:05.440 --> 00:09:05.450 align:start position:0% road map we are going to be looking to 00:09:05.450 --> 00:09:07.810 align:start position:0% road map we are going to be looking to go<00:09:05.570> ahead<00:09:05.750> and<00:09:05.870> integrate<00:09:06.020> I<00:09:06.350> PFS<00:09:06.770> and<00:09:07.040> swarm 00:09:07.810 --> 00:09:07.820 align:start position:0% go ahead and integrate I PFS and swarm 00:09:07.820 --> 00:09:10.020 align:start position:0% go ahead and integrate I PFS and swarm because<00:09:08.030> the<00:09:08.180> kick-ass<00:09:08.360> that's<00:09:08.960> enough<00:09:09.170> said 00:09:10.020 --> 00:09:10.030 align:start position:0% because the kick-ass that's enough said 00:09:10.030 --> 00:09:12.910 align:start position:0% because the kick-ass that's enough said we<00:09:11.030> are<00:09:11.360> also<00:09:11.630> going<00:09:11.930> ahead<00:09:12.080> with<00:09:12.290> a<00:09:12.350> lifecycle 00:09:12.910 --> 00:09:12.920 align:start position:0% we are also going ahead with a lifecycle 00:09:12.920 --> 00:09:14.620 align:start position:0% we are also going ahead with a lifecycle management<00:09:13.370> contract<00:09:13.970> and<00:09:14.150> what<00:09:14.360> that<00:09:14.510> is 00:09:14.620 --> 00:09:14.630 align:start position:0% management contract and what that is 00:09:14.630 --> 00:09:16.860 align:start position:0% management contract and what that is that<00:09:14.840> that<00:09:15.200> is<00:09:15.470> a 00:09:16.860 --> 00:09:16.870 align:start position:0% that that is a 00:09:16.870 --> 00:09:19.270 align:start position:0% that that is a contract<00:09:17.870> that<00:09:17.930> functions<00:09:18.500> as<00:09:18.590> a<00:09:18.740> single 00:09:19.270 --> 00:09:19.280 align:start position:0% contract that functions as a single 00:09:19.280 --> 00:09:21.160 align:start position:0% contract that functions as a single point<00:09:19.460> of<00:09:19.520> communication<00:09:20.150> to<00:09:20.330> deploy<00:09:20.690> update 00:09:21.160 --> 00:09:21.170 align:start position:0% point of communication to deploy update 00:09:21.170 --> 00:09:23.950 align:start position:0% point of communication to deploy update link<00:09:21.560> all<00:09:21.980> your<00:09:22.790> contracts<00:09:23.240> the<00:09:23.570> best<00:09:23.750> way<00:09:23.900> to 00:09:23.950 --> 00:09:23.960 align:start position:0% link all your contracts the best way to 00:09:23.960 --> 00:09:26.290 align:start position:0% link all your contracts the best way to go<00:09:24.140> ahead<00:09:24.260> and<00:09:24.710> frame<00:09:25.130> this<00:09:25.340> for<00:09:25.910> those<00:09:26.030> of<00:09:26.210> you 00:09:26.290 --> 00:09:26.300 align:start position:0% go ahead and frame this for those of you 00:09:26.300 --> 00:09:28.810 align:start position:0% go ahead and frame this for those of you who<00:09:26.390> are<00:09:26.420> familiar<00:09:26.570> with<00:09:26.960> NPM<00:09:27.590> would<00:09:28.310> be<00:09:28.460> it's 00:09:28.810 --> 00:09:28.820 align:start position:0% who are familiar with NPM would be it's 00:09:28.820 --> 00:09:33.520 align:start position:0% who are familiar with NPM would be it's like<00:09:28.970> the<00:09:29.120> index<00:09:30.190> jsf<00:09:31.190> aisle<00:09:31.870> it<00:09:32.870> is<00:09:33.050> the<00:09:33.200> entry 00:09:33.520 --> 00:09:33.530 align:start position:0% like the index jsf aisle it is the entry 00:09:33.530 --> 00:09:36.030 align:start position:0% like the index jsf aisle it is the entry point<00:09:33.560> for<00:09:33.980> all<00:09:34.040> of<00:09:34.460> your<00:09:34.700> projects 00:09:36.030 --> 00:09:36.040 align:start position:0% point for all of your projects 00:09:36.040 --> 00:09:39.150 align:start position:0% point for all of your projects thirdly<00:09:37.040> chain<00:09:37.940> runs 00:09:39.150 --> 00:09:39.160 align:start position:0% thirdly chain runs 00:09:39.160 --> 00:09:42.100 align:start position:0% thirdly chain runs we<00:09:40.160> are<00:09:40.280> going<00:09:40.520> to<00:09:40.610> be<00:09:40.700> going<00:09:40.820> ahead<00:09:41.060> and<00:09:41.450> with 00:09:42.100 --> 00:09:42.110 align:start position:0% we are going to be going ahead and with 00:09:42.110 --> 00:09:44.020 align:start position:0% we are going to be going ahead and with that<00:09:42.260> llamo<00:09:42.620> file<00:09:42.830> you<00:09:43.490> could<00:09:43.640> go<00:09:43.730> ahead<00:09:43.910> and 00:09:44.020 --> 00:09:44.030 align:start position:0% that llamo file you could go ahead and 00:09:44.030 --> 00:09:46.900 align:start position:0% that llamo file you could go ahead and set<00:09:44.180> out<00:09:44.360> set<00:09:45.230> jobs<00:09:45.560> that<00:09:46.070> go<00:09:46.640> ahead<00:09:46.820> and 00:09:46.900 --> 00:09:46.910 align:start position:0% set out set jobs that go ahead and 00:09:46.910 --> 00:09:49.030 align:start position:0% set out set jobs that go ahead and define<00:09:47.000> how<00:09:47.780> you<00:09:47.840> think<00:09:48.290> your<00:09:48.410> project<00:09:48.770> should 00:09:49.030 --> 00:09:49.040 align:start position:0% define how you think your project should 00:09:49.040 --> 00:09:51.700 align:start position:0% define how you think your project should run<00:09:49.400> and<00:09:49.820> then<00:09:50.450> you<00:09:50.600> could<00:09:50.780> chain<00:09:51.080> them<00:09:51.410> all 00:09:51.700 --> 00:09:51.710 align:start position:0% run and then you could chain them all 00:09:51.710 --> 00:09:53.320 align:start position:0% run and then you could chain them all throughout<00:09:52.010> the<00:09:52.130> dependency<00:09:52.670> tree<00:09:52.940> to<00:09:53.150> all 00:09:53.320 --> 00:09:53.330 align:start position:0% throughout the dependency tree to all 00:09:53.330 --> 00:09:56.550 align:start position:0% throughout the dependency tree to all move<00:09:54.200> up<00:09:54.410> through<00:09:54.710> and<00:09:55.010> interact<00:09:55.490> and 00:09:56.550 --> 00:09:56.560 align:start position:0% move up through and interact and 00:09:56.560 --> 00:09:59.500 align:start position:0% move up through and interact and fourthly<00:09:57.560> of<00:09:57.950> course<00:09:58.190> dependency<00:09:59.180> management 00:09:59.500 --> 00:09:59.510 align:start position:0% fourthly of course dependency management 00:09:59.510 --> 00:10:02.890 align:start position:0% fourthly of course dependency management and<00:10:00.020> with<00:10:00.830> that<00:10:01.310> the<00:10:01.820> next<00:10:02.150> slide<00:10:02.420> I'm<00:10:02.630> going 00:10:02.890 --> 00:10:02.900 align:start position:0% and with that the next slide I'm going 00:10:02.900 --> 00:10:05.740 align:start position:0% and with that the next slide I'm going to<00:10:03.020> let<00:10:03.290> Zach<00:10:03.650> finish<00:10:04.010> us<00:10:04.160> off<00:10:04.480> great<00:10:05.480> so<00:10:05.690> if 00:10:05.740 --> 00:10:05.750 align:start position:0% to let Zach finish us off great so if 00:10:05.750 --> 00:10:07.420 align:start position:0% to let Zach finish us off great so if you<00:10:05.870> want<00:10:06.020> to<00:10:06.080> get<00:10:06.140> started<00:10:06.440> on<00:10:06.800> any<00:10:07.190> platform 00:10:07.420 --> 00:10:07.430 align:start position:0% you want to get started on any platform 00:10:07.430 --> 00:10:10.390 align:start position:0% you want to get started on any platform it's<00:10:08.150> a<00:10:08.240> quick<00:10:08.990> out<00:10:09.170> of<00:10:09.260> the<00:10:09.440> box<00:10:09.650> so<00:10:09.950> Bruin 00:10:10.390 --> 00:10:10.400 align:start position:0% it's a quick out of the box so Bruin 00:10:10.400 --> 00:10:13.420 align:start position:0% it's a quick out of the box so Bruin choko<00:10:10.820> work<00:10:11.090> out<00:10:11.450> of<00:10:11.690> the<00:10:11.750> box<00:10:11.960> we<00:10:12.230> just<00:10:12.430> choko 00:10:13.420 --> 00:10:13.430 align:start position:0% choko work out of the box we just choko 00:10:13.430 --> 00:10:16.240 align:start position:0% choko work out of the box we just choko got<00:10:13.610> approved<00:10:13.940> last<00:10:14.150> week<00:10:14.450> and<00:10:15.320> app<00:10:15.530> get<00:10:15.890> if 00:10:16.240 --> 00:10:16.250 align:start position:0% got approved last week and app get if 00:10:16.250 --> 00:10:17.800 align:start position:0% got approved last week and app get if you<00:10:16.400> want<00:10:16.550> to<00:10:16.610> run<00:10:16.760> it<00:10:16.910> on<00:10:16.970> Linux<00:10:17.330> just<00:10:17.630> check 00:10:17.800 --> 00:10:17.810 align:start position:0% you want to run it on Linux just check 00:10:17.810 --> 00:10:20.980 align:start position:0% you want to run it on Linux just check out<00:10:17.930> our<00:10:18.170> documentation<00:10:18.770> and<00:10:19.520> finally<00:10:20.210> join 00:10:20.980 --> 00:10:20.990 align:start position:0% out our documentation and finally join 00:10:20.990 --> 00:10:23.320 align:start position:0% out our documentation and finally join our<00:10:21.140> slack<00:10:21.440> it's<00:10:21.920> open<00:10:22.310> and<00:10:22.940> there's<00:10:23.090> lots<00:10:23.180> of 00:10:23.320 --> 00:10:23.330 align:start position:0% our slack it's open and there's lots of 00:10:23.330 --> 00:10:24.880 align:start position:0% our slack it's open and there's lots of users<00:10:23.510> in<00:10:23.630> there<00:10:23.930> and<00:10:24.140> they<00:10:24.440> can<00:10:24.590> help<00:10:24.710> you<00:10:24.800> get 00:10:24.880 --> 00:10:24.890 align:start position:0% users in there and they can help you get 00:10:24.890 --> 00:10:26.760 align:start position:0% users in there and they can help you get started<00:10:25.100> thank<00:10:25.520> you 00:10:26.760 --> 00:10:26.770 align:start position:0% started thank you 00:10:26.770 --> 00:10:30.020 align:start position:0% started thank you thanks<00:10:27.770> our<00:10:27.890> Jane<00:10:28.130> Zach 00:10:30.020 --> 00:10:30.030 align:start position:0% thanks our Jane Zach 00:10:30.030 --> 00:10:37.379 align:start position:0% thanks our Jane Zach [Music]