WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:15.660 align:start position:0% [Music] 00:00:15.660 --> 00:00:15.670 align:start position:0% [Music] 00:00:15.670 --> 00:00:17.700 align:start position:0% [Music] okay<00:00:16.179> so<00:00:16.240> I'm<00:00:16.960> gonna<00:00:17.080> do<00:00:17.289> a<00:00:17.320> quick 00:00:17.700 --> 00:00:17.710 align:start position:0% okay so I'm gonna do a quick 00:00:17.710 --> 00:00:20.159 align:start position:0% okay so I'm gonna do a quick presentation<00:00:18.009> on<00:00:18.839> some<00:00:19.839> aetherium 00:00:20.159 --> 00:00:20.169 align:start position:0% presentation on some aetherium 00:00:20.169 --> 00:00:23.909 align:start position:0% presentation on some aetherium JavaScript<00:00:20.619> stuff<00:00:20.829> and<00:00:22.529> you<00:00:23.529> guys<00:00:23.679> hear<00:00:23.829> me 00:00:23.909 --> 00:00:23.919 align:start position:0% JavaScript stuff and you guys hear me 00:00:23.919 --> 00:00:24.329 align:start position:0% JavaScript stuff and you guys hear me okay 00:00:24.329 --> 00:00:24.339 align:start position:0% okay 00:00:24.339 --> 00:00:27.380 align:start position:0% okay so<00:00:24.519> everything<00:00:24.759> good<00:00:25.119> all<00:00:25.630> right<00:00:25.720> cool<00:00:26.140> so 00:00:27.380 --> 00:00:27.390 align:start position:0% so everything good all right cool so 00:00:27.390 --> 00:00:29.700 align:start position:0% so everything good all right cool so it's<00:00:28.390> going<00:00:28.539> to<00:00:28.630> be<00:00:28.720> on<00:00:28.869> some<00:00:29.109> alternatives 00:00:29.700 --> 00:00:29.710 align:start position:0% it's going to be on some alternatives 00:00:29.710 --> 00:00:32.580 align:start position:0% it's going to be on some alternatives that<00:00:30.550> are<00:00:30.609> available<00:00:30.849> in<00:00:31.689> the<00:00:31.779> ecosystem<00:00:32.349> that 00:00:32.580 --> 00:00:32.590 align:start position:0% that are available in the ecosystem that 00:00:32.590 --> 00:00:35.970 align:start position:0% that are available in the ecosystem that you<00:00:32.649> may<00:00:33.010> not<00:00:33.160> be<00:00:33.309> aware<00:00:33.370> of<00:00:33.520> and<00:00:33.880> I<00:00:34.570> think<00:00:34.980> it 00:00:35.970 --> 00:00:35.980 align:start position:0% you may not be aware of and I think it 00:00:35.980 --> 00:00:38.190 align:start position:0% you may not be aware of and I think it should<00:00:36.130> open<00:00:36.280> you<00:00:36.490> up<00:00:36.520> to<00:00:37.050> kind<00:00:38.050> of<00:00:38.140> the 00:00:38.190 --> 00:00:38.200 align:start position:0% should open you up to kind of the 00:00:38.200 --> 00:00:43.140 align:start position:0% should open you up to kind of the possibilities<00:00:38.890> on<00:00:39.790> the<00:00:39.970> RPC<00:00:40.300> layer<00:00:40.690> and<00:00:42.150> and 00:00:43.140 --> 00:00:43.150 align:start position:0% possibilities on the RPC layer and and 00:00:43.150 --> 00:00:44.130 align:start position:0% possibilities on the RPC layer and and kind<00:00:43.360> of<00:00:43.420> how<00:00:43.570> you<00:00:43.630> want<00:00:43.840> to<00:00:43.930> approach 00:00:44.130 --> 00:00:44.140 align:start position:0% kind of how you want to approach 00:00:44.140 --> 00:00:45.930 align:start position:0% kind of how you want to approach designing<00:00:44.590> your<00:00:44.800> app<00:00:45.190> or<00:00:45.400> Deb 00:00:45.930 --> 00:00:45.940 align:start position:0% designing your app or Deb 00:00:45.940 --> 00:00:49.050 align:start position:0% designing your app or Deb so<00:00:46.780> right<00:00:47.380> now<00:00:47.500> the<00:00:47.560> etherium<00:00:48.130> ecosystem 00:00:49.050 --> 00:00:49.060 align:start position:0% so right now the etherium ecosystem 00:00:49.060 --> 00:00:51.480 align:start position:0% so right now the etherium ecosystem especially<00:00:49.990> on<00:00:50.290> the<00:00:50.380> RPC<00:00:50.620> layer<00:00:50.980> is<00:00:51.130> kind<00:00:51.370> of 00:00:51.480 --> 00:00:51.490 align:start position:0% especially on the RPC layer is kind of 00:00:51.490 --> 00:00:54.569 align:start position:0% especially on the RPC layer is kind of dominated<00:00:52.120> by<00:00:52.240> these<00:00:52.300> modules<00:00:53.050> web<00:00:53.470> 3<00:00:53.800> theory 00:00:54.569 --> 00:00:54.579 align:start position:0% dominated by these modules web 3 theory 00:00:54.579 --> 00:00:57.990 align:start position:0% dominated by these modules web 3 theory MJS<00:00:55.060> parity<00:00:55.750> api<00:00:56.020> ethers<00:00:56.980> j/s<00:00:57.370> which<00:00:57.640> was<00:00:57.790> just 00:00:57.990 --> 00:00:58.000 align:start position:0% MJS parity api ethers j/s which was just 00:00:58.000 --> 00:01:01.200 align:start position:0% MJS parity api ethers j/s which was just recently<00:00:58.210> released<00:00:58.650> and<00:00:59.650> eath<00:00:59.890> j/s<00:01:00.370> which<00:01:01.060> has 00:01:01.200 --> 00:01:01.210 align:start position:0% recently released and eath j/s which has 00:01:01.210 --> 00:01:02.640 align:start position:0% recently released and eath j/s which has kind<00:01:01.360> of<00:01:01.480> been<00:01:01.600> in<00:01:01.930> the<00:01:02.050> background<00:01:02.470> for<00:01:02.620> a 00:01:02.640 --> 00:01:02.650 align:start position:0% kind of been in the background for a 00:01:02.650 --> 00:01:06.599 align:start position:0% kind of been in the background for a little<00:01:02.829> while<00:01:03.780> so<00:01:05.100> to<00:01:06.100> go<00:01:06.219> through<00:01:06.249> a<00:01:06.460> bit<00:01:06.579> of 00:01:06.599 --> 00:01:06.609 align:start position:0% little while so to go through a bit of 00:01:06.609 --> 00:01:10.940 align:start position:0% little while so to go through a bit of an<00:01:06.759> overview<00:01:07.649> ejs<00:01:08.649> is<00:01:08.979> a<00:01:09.700> small<00:01:10.390> organization 00:01:10.940 --> 00:01:10.950 align:start position:0% an overview ejs is a small organization 00:01:10.950 --> 00:01:15.389 align:start position:0% an overview ejs is a small organization that<00:01:11.950> has<00:01:12.100> a<00:01:12.130> few<00:01:12.789> modules<00:01:12.939> 15<00:01:13.659> in<00:01:13.869> total<00:01:14.399> and 00:01:15.389 --> 00:01:15.399 align:start position:0% that has a few modules 15 in total and 00:01:15.399 --> 00:01:17.849 align:start position:0% that has a few modules 15 in total and we<00:01:15.880> have<00:01:15.999> one<00:01:16.240> boilerplate<00:01:16.990> and<00:01:17.350> a<00:01:17.649> few 00:01:17.849 --> 00:01:17.859 align:start position:0% we have one boilerplate and a few 00:01:17.859 --> 00:01:20.190 align:start position:0% we have one boilerplate and a few development<00:01:18.369> tools<00:01:18.579> so<00:01:19.060> some<00:01:19.539> command<00:01:20.049> line 00:01:20.190 --> 00:01:20.200 align:start position:0% development tools so some command line 00:01:20.200 --> 00:01:22.980 align:start position:0% development tools so some command line stuff<00:01:20.409> as<00:01:20.679> well<00:01:21.719> everything's<00:01:22.719> fully 00:01:22.980 --> 00:01:22.990 align:start position:0% stuff as well everything's fully 00:01:22.990 --> 00:01:24.539 align:start position:0% stuff as well everything's fully documented<00:01:23.469> everything's<00:01:24.340> fully 00:01:24.539 --> 00:01:24.549 align:start position:0% documented everything's fully 00:01:24.549 --> 00:01:29.219 align:start position:0% documented everything's fully exemplified<00:01:25.259> and<00:01:26.369> MIT<00:01:27.369> licensed<00:01:28.229> its 00:01:29.219 --> 00:01:29.229 align:start position:0% exemplified and MIT licensed its 00:01:29.229 --> 00:01:31.469 align:start position:0% exemplified and MIT licensed its production<00:01:29.710> ready<00:01:29.889> although<00:01:30.459> there's<00:01:30.850> one 00:01:31.469 --> 00:01:31.479 align:start position:0% production ready although there's one 00:01:31.479 --> 00:01:33.149 align:start position:0% production ready although there's one module<00:01:31.899> that<00:01:32.289> you<00:01:32.409> probably<00:01:32.649> shouldn't<00:01:33.069> use 00:01:33.149 --> 00:01:33.159 align:start position:0% module that you probably shouldn't use 00:01:33.159 --> 00:01:36.209 align:start position:0% module that you probably shouldn't use because<00:01:33.549> it's<00:01:33.909> not<00:01:34.090> a<00:01:34.240> IP<00:01:34.389> 155<00:01:35.229> so<00:01:35.740> Richard 00:01:36.209 --> 00:01:36.219 align:start position:0% because it's not a IP 155 so Richard 00:01:36.219 --> 00:01:41.910 align:start position:0% because it's not a IP 155 so Richard tells<00:01:36.429> me<00:01:36.609> and<00:01:39.659> 100%<00:01:40.659> test<00:01:40.899> coverage<00:01:40.959> and<00:01:41.499> 98% 00:01:41.910 --> 00:01:41.920 align:start position:0% tells me and 100% test coverage and 98% 00:01:41.920 --> 00:01:44.840 align:start position:0% tells me and 100% test coverage and 98% build<00:01:42.310> up<00:01:42.459> time<00:01:42.729> as<00:01:43.090> a<00:01:43.149> general<00:01:43.539> policy<00:01:43.689> so 00:01:44.840 --> 00:01:44.850 align:start position:0% build up time as a general policy so 00:01:44.850 --> 00:01:48.330 align:start position:0% build up time as a general policy so this<00:01:45.850> is<00:01:46.029> kind<00:01:46.270> of<00:01:46.619> the<00:01:47.619> organization<00:01:48.189> as<00:01:48.310> a 00:01:48.330 --> 00:01:48.340 align:start position:0% this is kind of the organization as a 00:01:48.340 --> 00:01:52.649 align:start position:0% this is kind of the organization as a whole<00:01:48.429> and<00:01:50.219> it's<00:01:51.219> it's<00:01:51.609> on<00:01:51.789> github<00:01:51.969> so<00:01:52.479> just 00:01:52.649 --> 00:01:52.659 align:start position:0% whole and it's it's on github so just 00:01:52.659 --> 00:01:56.519 align:start position:0% whole and it's it's on github so just github.com<00:01:52.959> slash<00:01:53.709> eath<00:01:54.039> j/s<00:01:54.490> and<00:01:55.420> we've<00:01:56.380> had 00:01:56.519 --> 00:01:56.529 align:start position:0% github.com slash eath j/s and we've had 00:01:56.529 --> 00:01:59.849 align:start position:0% github.com slash eath j/s and we've had 20<00:01:56.829> repositories<00:01:57.599> so<00:01:58.599> initially<00:01:59.319> a<00:01:59.349> few 00:01:59.849 --> 00:01:59.859 align:start position:0% 20 repositories so initially a few 00:01:59.859 --> 00:02:02.910 align:start position:0% 20 repositories so initially a few months<00:02:00.069> ago<00:02:00.270> I<00:02:01.270> had<00:02:01.810> gotten<00:02:02.349> a<00:02:02.740> little 00:02:02.910 --> 00:02:02.920 align:start position:0% months ago I had gotten a little 00:02:02.920 --> 00:02:06.749 align:start position:0% months ago I had gotten a little frustrated<00:02:03.459> with<00:02:03.520> web<00:02:03.729> 3<00:02:03.969> and<00:02:05.159> I<00:02:06.159> had<00:02:06.639> also 00:02:06.749 --> 00:02:06.759 align:start position:0% frustrated with web 3 and I had also 00:02:06.759 --> 00:02:08.760 align:start position:0% frustrated with web 3 and I had also been<00:02:06.999> working<00:02:07.389> and<00:02:07.779> talking<00:02:07.929> with<00:02:08.289> Richard 00:02:08.760 --> 00:02:08.770 align:start position:0% been working and talking with Richard 00:02:08.770 --> 00:02:13.080 align:start position:0% been working and talking with Richard Moore<00:02:09.039> on<00:02:09.580> a<00:02:09.790> few<00:02:10.030> different<00:02:10.780> points<00:02:10.960> and<00:02:12.090> kind 00:02:13.080 --> 00:02:13.090 align:start position:0% Moore on a few different points and kind 00:02:13.090 --> 00:02:15.030 align:start position:0% Moore on a few different points and kind of<00:02:13.180> wrote<00:02:13.900> a<00:02:13.930> different<00:02:14.170> approach 00:02:15.030 --> 00:02:15.040 align:start position:0% of wrote a different approach 00:02:15.040 --> 00:02:18.059 align:start position:0% of wrote a different approach when<00:02:15.340> three<00:02:15.610> so<00:02:16.200> and<00:02:17.200> also<00:02:17.530> a<00:02:17.560> little 00:02:18.059 --> 00:02:18.069 align:start position:0% when three so and also a little 00:02:18.069 --> 00:02:19.800 align:start position:0% when three so and also a little different<00:02:18.250> approach<00:02:18.670> to<00:02:18.940> how<00:02:18.970> ethers<00:02:19.540> Janis 00:02:19.800 --> 00:02:19.810 align:start position:0% different approach to how ethers Janis 00:02:19.810 --> 00:02:22.680 align:start position:0% different approach to how ethers Janis was<00:02:19.989> doing<00:02:20.230> it<00:02:20.349> at<00:02:20.440> the<00:02:20.530> time<00:02:20.819> and<00:02:21.819> I 00:02:22.680 --> 00:02:22.690 align:start position:0% was doing it at the time and I 00:02:22.690 --> 00:02:24.360 align:start position:0% was doing it at the time and I definitely<00:02:23.230> encourage<00:02:23.769> you<00:02:23.799> to<00:02:23.890> check<00:02:24.040> out 00:02:24.360 --> 00:02:24.370 align:start position:0% definitely encourage you to check out 00:02:24.370 --> 00:02:27.479 align:start position:0% definitely encourage you to check out all<00:02:24.879> the<00:02:25.150> alternatives<00:02:25.720> and<00:02:25.930> kind<00:02:26.590> of<00:02:26.709> make<00:02:27.459> a 00:02:27.479 --> 00:02:27.489 align:start position:0% all the alternatives and kind of make a 00:02:27.489 --> 00:02:30.390 align:start position:0% all the alternatives and kind of make a decision<00:02:27.879> for<00:02:28.060> what's<00:02:28.269> right<00:02:29.080> if<00:02:29.739> you<00:02:29.950> do<00:02:30.129> want 00:02:30.390 --> 00:02:30.400 align:start position:0% decision for what's right if you do want 00:02:30.400 --> 00:02:33.619 align:start position:0% decision for what's right if you do want to<00:02:30.459> use<00:02:30.610> an<00:02:30.730> alternative<00:02:30.790> to<00:02:31.330> web<00:02:31.480> three<00:02:32.129> and 00:02:33.619 --> 00:02:33.629 align:start position:0% to use an alternative to web three and 00:02:33.629 --> 00:02:39.240 align:start position:0% to use an alternative to web three and so<00:02:36.239> basically<00:02:37.239> there's<00:02:38.170> a<00:02:38.230> few<00:02:38.470> different 00:02:39.240 --> 00:02:39.250 align:start position:0% so basically there's a few different 00:02:39.250 --> 00:02:42.030 align:start position:0% so basically there's a few different philosophies<00:02:40.150> and<00:02:40.420> things<00:02:40.810> and<00:02:41.110> to<00:02:41.769> keep<00:02:41.920> in 00:02:42.030 --> 00:02:42.040 align:start position:0% philosophies and things and to keep in 00:02:42.040 --> 00:02:42.330 align:start position:0% philosophies and things and to keep in mind 00:02:42.330 --> 00:02:42.340 align:start position:0% mind 00:02:42.340 --> 00:02:44.910 align:start position:0% mind so<00:02:43.030> each<00:02:43.660> s<00:02:43.900> can<00:02:44.260> be<00:02:44.290> used<00:02:44.560> as<00:02:44.680> an<00:02:44.799> alternative 00:02:44.910 --> 00:02:44.920 align:start position:0% so each s can be used as an alternative 00:02:44.920 --> 00:02:47.009 align:start position:0% so each s can be used as an alternative to<00:02:45.310> web<00:02:45.519> three<00:02:45.760> but<00:02:45.940> I<00:02:45.970> actually<00:02:46.150> like<00:02:46.780> it<00:02:46.989> to 00:02:47.009 --> 00:02:47.019 align:start position:0% to web three but I actually like it to 00:02:47.019 --> 00:02:49.619 align:start position:0% to web three but I actually like it to be<00:02:47.230> used<00:02:47.440> more<00:02:47.590> for<00:02:47.950> architecture<00:02:48.519> it's<00:02:49.360> used 00:02:49.619 --> 00:02:49.629 align:start position:0% be used more for architecture it's used 00:02:49.629 --> 00:02:51.869 align:start position:0% be used more for architecture it's used in<00:02:49.840> quite<00:02:50.470> a<00:02:50.500> few<00:02:50.680> projects<00:02:51.040> I'll<00:02:51.340> go<00:02:51.489> over<00:02:51.579> in 00:02:51.869 --> 00:02:51.879 align:start position:0% in quite a few projects I'll go over in 00:02:51.879 --> 00:02:55.740 align:start position:0% in quite a few projects I'll go over in a<00:02:51.970> bit<00:02:52.090> I<00:02:52.900> think<00:02:53.709> diversity<00:02:54.250> and<00:02:54.970> modules<00:02:55.480> and 00:02:55.740 --> 00:02:55.750 align:start position:0% a bit I think diversity and modules and 00:02:55.750 --> 00:02:57.509 align:start position:0% a bit I think diversity and modules and libraries<00:02:56.170> kind<00:02:56.530> of<00:02:56.590> makes<00:02:56.739> the<00:02:56.950> community 00:02:57.509 --> 00:02:57.519 align:start position:0% libraries kind of makes the community 00:02:57.519 --> 00:02:59.789 align:start position:0% libraries kind of makes the community stronger<00:02:57.970> I<00:02:58.150> think<00:02:58.629> you<00:02:59.410> know<00:02:59.530> having 00:02:59.789 --> 00:02:59.799 align:start position:0% stronger I think you know having 00:02:59.799 --> 00:03:02.280 align:start position:0% stronger I think you know having different<00:03:00.370> options<00:03:00.790> and<00:03:01.090> different<00:03:01.329> opinions 00:03:02.280 --> 00:03:02.290 align:start position:0% different options and different opinions 00:03:02.290 --> 00:03:04.020 align:start position:0% different options and different opinions and<00:03:02.500> different<00:03:02.560> ways<00:03:02.890> to<00:03:02.920> interact<00:03:03.579> with 00:03:04.020 --> 00:03:04.030 align:start position:0% and different ways to interact with 00:03:04.030 --> 00:03:05.849 align:start position:0% and different ways to interact with aetherium<00:03:04.989> is<00:03:05.109> kind<00:03:05.319> of<00:03:05.349> critical<00:03:05.799> to 00:03:05.849 --> 00:03:05.859 align:start position:0% aetherium is kind of critical to 00:03:05.859 --> 00:03:07.500 align:start position:0% aetherium is kind of critical to building<00:03:06.370> a<00:03:06.489> stronger<00:03:06.790> community<00:03:06.940> and 00:03:07.500 --> 00:03:07.510 align:start position:0% building a stronger community and 00:03:07.510 --> 00:03:10.500 align:start position:0% building a stronger community and stronger<00:03:07.900> infrastructure<00:03:09.510> companion 00:03:10.500 --> 00:03:10.510 align:start position:0% stronger infrastructure companion 00:03:10.510 --> 00:03:12.150 align:start position:0% stronger infrastructure companion libraries<00:03:11.049> help<00:03:11.319> influence<00:03:11.590> each<00:03:11.890> other's 00:03:12.150 --> 00:03:12.160 align:start position:0% libraries help influence each other's 00:03:12.160 --> 00:03:14.520 align:start position:0% libraries help influence each other's design<00:03:12.549> so<00:03:12.970> some<00:03:13.299> of<00:03:13.420> each<00:03:13.540> s<00:03:13.870> kind<00:03:14.230> of<00:03:14.290> helped 00:03:14.520 --> 00:03:14.530 align:start position:0% design so some of each s kind of helped 00:03:14.530 --> 00:03:18.839 align:start position:0% design so some of each s kind of helped web<00:03:14.799> 31.0<00:03:15.750> ethers<00:03:16.750> j/s<00:03:17.109> helped<00:03:17.530> me<00:03:17.799> build<00:03:18.640> some 00:03:18.839 --> 00:03:18.849 align:start position:0% web 31.0 ethers j/s helped me build some 00:03:18.849 --> 00:03:22.289 align:start position:0% web 31.0 ethers j/s helped me build some interests<00:03:19.299> of<00:03:19.599> so<00:03:20.380> and<00:03:21.340> in<00:03:21.489> fact<00:03:21.519> I<00:03:21.849> use<00:03:22.090> some 00:03:22.289 --> 00:03:22.299 align:start position:0% interests of so and in fact I use some 00:03:22.299 --> 00:03:24.360 align:start position:0% interests of so and in fact I use some of<00:03:22.329> some<00:03:22.690> of<00:03:22.810> their<00:03:22.900> modules<00:03:23.079> in<00:03:23.530> in<00:03:24.160> my 00:03:24.360 --> 00:03:24.370 align:start position:0% of some of their modules in in my 00:03:24.370 --> 00:03:28.020 align:start position:0% of some of their modules in in my libraries<00:03:24.900> and<00:03:26.130> of<00:03:27.130> course<00:03:27.400> we<00:03:27.579> still<00:03:27.790> follow 00:03:28.020 --> 00:03:28.030 align:start position:0% libraries and of course we still follow 00:03:28.030 --> 00:03:30.629 align:start position:0% libraries and of course we still follow all<00:03:28.480> the<00:03:28.630> RPC<00:03:28.900> specifications<00:03:29.829> and<00:03:30.220> the 00:03:30.629 --> 00:03:30.639 align:start position:0% all the RPC specifications and the 00:03:30.639 --> 00:03:32.839 align:start position:0% all the RPC specifications and the provider<00:03:30.970> models<00:03:31.389> that<00:03:31.720> people<00:03:32.049> are<00:03:32.290> used<00:03:32.470> to 00:03:32.839 --> 00:03:32.849 align:start position:0% provider models that people are used to 00:03:32.849 --> 00:03:36.270 align:start position:0% provider models that people are used to but<00:03:33.849> we<00:03:34.720> kind<00:03:35.109> of<00:03:35.260> have<00:03:35.650> different<00:03:35.950> opinions 00:03:36.270 --> 00:03:36.280 align:start position:0% but we kind of have different opinions 00:03:36.280 --> 00:03:37.940 align:start position:0% but we kind of have different opinions on<00:03:36.430> approaching<00:03:36.760> how<00:03:37.209> to<00:03:37.269> interact<00:03:37.540> with<00:03:37.720> it 00:03:37.940 --> 00:03:37.950 align:start position:0% on approaching how to interact with it 00:03:37.950 --> 00:03:42.509 align:start position:0% on approaching how to interact with it and<00:03:40.410> so<00:03:41.410> the<00:03:41.680> way<00:03:41.769> that<00:03:41.980> I've<00:03:42.250> kind<00:03:42.459> of 00:03:42.509 --> 00:03:42.519 align:start position:0% and so the way that I've kind of 00:03:42.519 --> 00:03:45.270 align:start position:0% and so the way that I've kind of constructed<00:03:43.030> eath<00:03:43.389> j/s<00:03:43.780> at<00:03:44.230> least<00:03:44.440> the<00:03:44.650> core 00:03:45.270 --> 00:03:45.280 align:start position:0% constructed eath j/s at least the core 00:03:45.280 --> 00:03:47.400 align:start position:0% constructed eath j/s at least the core interface<00:03:45.459> there<00:03:45.910> is<00:03:46.200> you<00:03:47.200> give<00:03:47.290> your 00:03:47.400 --> 00:03:47.410 align:start position:0% interface there is you give your 00:03:47.410 --> 00:03:49.500 align:start position:0% interface there is you give your contract<00:03:47.829> module<00:03:48.190> filtering<00:03:48.639> modules<00:03:49.030> and<00:03:49.389> so 00:03:49.500 --> 00:03:49.510 align:start position:0% contract module filtering modules and so 00:03:49.510 --> 00:03:51.180 align:start position:0% contract module filtering modules and so forth<00:03:49.780> this<00:03:49.959> has<00:03:50.109> become<00:03:50.410> kind<00:03:50.590> of<00:03:50.769> a<00:03:50.859> standard 00:03:51.180 --> 00:03:51.190 align:start position:0% forth this has become kind of a standard 00:03:51.190 --> 00:03:54.089 align:start position:0% forth this has become kind of a standard practice<00:03:51.609> now<00:03:51.989> I<00:03:52.989> have<00:03:53.319> my<00:03:53.440> querying<00:03:53.739> layer 00:03:54.089 --> 00:03:54.099 align:start position:0% practice now I have my querying layer 00:03:54.099 --> 00:03:57.180 align:start position:0% practice now I have my querying layer which<00:03:54.519> combines<00:03:54.970> both<00:03:55.299> an<00:03:56.019> RPC<00:03:56.349> module<00:03:56.950> and<00:03:57.160> a 00:03:57.180 --> 00:03:57.190 align:start position:0% which combines both an RPC module and a 00:03:57.190 --> 00:04:00.240 align:start position:0% which combines both an RPC module and a formatting<00:03:57.669> module<00:03:58.019> and<00:03:59.019> basically<00:03:59.620> formats 00:04:00.240 --> 00:04:00.250 align:start position:0% formatting module and basically formats 00:04:00.250 --> 00:04:02.550 align:start position:0% formatting module and basically formats all<00:04:00.760> your<00:04:01.000> input<00:04:01.239> inputs<00:04:01.870> and<00:04:02.019> outputs<00:04:02.319> to<00:04:02.440> the 00:04:02.550 --> 00:04:02.560 align:start position:0% all your input inputs and outputs to the 00:04:02.560 --> 00:04:05.909 align:start position:0% all your input inputs and outputs to the RPC<00:04:02.859> layer<00:04:03.389> automatically<00:04:04.389> and<00:04:05.379> each<00:04:05.590> jeaious 00:04:05.909 --> 00:04:05.919 align:start position:0% RPC layer automatically and each jeaious 00:04:05.919 --> 00:04:08.610 align:start position:0% RPC layer automatically and each jeaious schema<00:04:06.220> is<00:04:06.400> actually<00:04:06.849> I<00:04:07.090> think<00:04:07.510> one<00:04:08.349> of<00:04:08.379> the 00:04:08.610 --> 00:04:08.620 align:start position:0% schema is actually I think one of the 00:04:08.620 --> 00:04:10.589 align:start position:0% schema is actually I think one of the the<00:04:09.129> better<00:04:09.519> things<00:04:09.790> that<00:04:09.910> I<00:04:10.090> definitely<00:04:10.480> did 00:04:10.589 --> 00:04:10.599 align:start position:0% the better things that I definitely did 00:04:10.599 --> 00:04:13.050 align:start position:0% the better things that I definitely did here<00:04:10.930> so<00:04:11.230> I<00:04:11.530> just<00:04:11.560> laid<00:04:11.889> out<00:04:12.099> in<00:04:12.340> a<00:04:12.430> JSON<00:04:12.609> file 00:04:13.050 --> 00:04:13.060 align:start position:0% here so I just laid out in a JSON file 00:04:13.060 --> 00:04:15.780 align:start position:0% here so I just laid out in a JSON file the<00:04:13.720> entire<00:04:13.870> RPC<00:04:14.560> specification<00:04:15.310> and<00:04:15.519> all<00:04:15.639> the 00:04:15.780 --> 00:04:15.790 align:start position:0% the entire RPC specification and all the 00:04:15.790 --> 00:04:18.360 align:start position:0% the entire RPC specification and all the inputs<00:04:16.090> and<00:04:16.209> outputs<00:04:16.349> so<00:04:17.349> you<00:04:18.010> can<00:04:18.190> basically 00:04:18.360 --> 00:04:18.370 align:start position:0% inputs and outputs so you can basically 00:04:18.370 --> 00:04:21.360 align:start position:0% inputs and outputs so you can basically take<00:04:18.880> that<00:04:18.940> and<00:04:19.359> auto<00:04:19.510> generate<00:04:20.079> the<00:04:21.070> entire 00:04:21.360 --> 00:04:21.370 align:start position:0% take that and auto generate the entire 00:04:21.370 --> 00:04:23.690 align:start position:0% take that and auto generate the entire RPC<00:04:22.000> query<00:04:22.300> layer 00:04:23.690 --> 00:04:23.700 align:start position:0% RPC query layer 00:04:23.700 --> 00:04:25.640 align:start position:0% RPC query layer and<00:04:23.790> and<00:04:24.600> have<00:04:24.780> that<00:04:24.930> an<00:04:25.080> automated<00:04:25.380> process 00:04:25.640 --> 00:04:25.650 align:start position:0% and and have that an automated process 00:04:25.650 --> 00:04:28.790 align:start position:0% and and have that an automated process so<00:04:26.370> this<00:04:26.790> is<00:04:26.970> kept<00:04:27.180> it<00:04:27.330> to<00:04:27.420> be<00:04:27.570> very<00:04:27.810> you<00:04:28.740> know 00:04:28.790 --> 00:04:28.800 align:start position:0% so this is kept it to be very you know 00:04:28.800 --> 00:04:30.650 align:start position:0% so this is kept it to be very you know easy<00:04:29.130> process<00:04:29.670> for<00:04:29.850> me<00:04:29.910> to<00:04:30.000> update<00:04:30.180> or<00:04:30.540> for 00:04:30.650 --> 00:04:30.660 align:start position:0% easy process for me to update or for 00:04:30.660 --> 00:04:33.020 align:start position:0% easy process for me to update or for others<00:04:30.840> to<00:04:31.020> come<00:04:31.170> along<00:04:31.380> and<00:04:31.650> add<00:04:32.010> my<00:04:32.250> methods 00:04:33.020 --> 00:04:33.030 align:start position:0% others to come along and add my methods 00:04:33.030 --> 00:04:36.490 align:start position:0% others to come along and add my methods and<00:04:33.210> so<00:04:33.330> forth<00:04:33.630> it<00:04:33.870> really<00:04:34.140> is<00:04:34.350> all<00:04:35.250> automatic 00:04:36.490 --> 00:04:36.500 align:start position:0% and so forth it really is all automatic 00:04:36.500 --> 00:04:39.890 align:start position:0% and so forth it really is all automatic and<00:04:37.700> so<00:04:38.700> just<00:04:38.910> a<00:04:39.030> little<00:04:39.240> more<00:04:39.390> in-depth<00:04:39.720> on 00:04:39.890 --> 00:04:39.900 align:start position:0% and so just a little more in-depth on 00:04:39.900 --> 00:04:42.250 align:start position:0% and so just a little more in-depth on some<00:04:40.110> of<00:04:40.200> the<00:04:40.260> modules<00:04:40.650> is<00:04:41.160> some<00:04:41.400> providers 00:04:42.250 --> 00:04:42.260 align:start position:0% some of the modules is some providers 00:04:42.260 --> 00:04:47.210 align:start position:0% some of the modules is some providers for<00:04:43.260> signing<00:04:43.650> HTTP<00:04:44.430> HTTP<00:04:45.090> querying<00:04:45.920> some<00:04:46.920> unit 00:04:47.210 --> 00:04:47.220 align:start position:0% for signing HTTP HTTP querying some unit 00:04:47.220 --> 00:04:50.720 align:start position:0% for signing HTTP HTTP querying some unit handling<00:04:47.610> formatting<00:04:49.190> event<00:04:50.190> filtering 00:04:50.720 --> 00:04:50.730 align:start position:0% handling formatting event filtering 00:04:50.730 --> 00:04:53.630 align:start position:0% handling formatting event filtering contract<00:04:51.540> handling<00:04:52.040> transaction<00:04:53.040> signing 00:04:53.630 --> 00:04:53.640 align:start position:0% contract handling transaction signing 00:04:53.640 --> 00:04:55.310 align:start position:0% contract handling transaction signing although<00:04:54.060> definitely<00:04:54.540> just<00:04:54.690> use<00:04:54.810> ethers<00:04:55.110> for 00:04:55.310 --> 00:04:55.320 align:start position:0% although definitely just use ethers for 00:04:55.320 --> 00:05:00.470 align:start position:0% although definitely just use ethers for that<00:04:55.470> because<00:04:55.860> the<00:04:56.460> IP<00:04:56.610> 155<00:04:57.330> and<00:04:59.120> accounts<00:05:00.120> so 00:05:00.470 --> 00:05:00.480 align:start position:0% that because the IP 155 and accounts so 00:05:00.480 --> 00:05:01.760 align:start position:0% that because the IP 155 and accounts so just<00:05:00.690> generating<00:05:01.140> and<00:05:01.260> managing<00:05:01.530> accounts 00:05:01.760 --> 00:05:01.770 align:start position:0% just generating and managing accounts 00:05:01.770 --> 00:05:03.560 align:start position:0% just generating and managing accounts although<00:05:02.310> you<00:05:02.550> have<00:05:02.760> to<00:05:02.850> be<00:05:02.940> very<00:05:03.090> careful 00:05:03.560 --> 00:05:03.570 align:start position:0% although you have to be very careful 00:05:03.570 --> 00:05:05.600 align:start position:0% although you have to be very careful because<00:05:03.750> you<00:05:04.380> do<00:05:04.470> have<00:05:04.500> to<00:05:04.650> supply<00:05:05.070> your<00:05:05.550> own 00:05:05.600 --> 00:05:05.610 align:start position:0% because you do have to supply your own 00:05:05.610 --> 00:05:07.490 align:start position:0% because you do have to supply your own good<00:05:06.030> source<00:05:06.240> of<00:05:06.390> entropy<00:05:06.690> and<00:05:07.140> while<00:05:07.320> I<00:05:07.350> do 00:05:07.490 --> 00:05:07.500 align:start position:0% good source of entropy and while I do 00:05:07.500 --> 00:05:09.800 align:start position:0% good source of entropy and while I do supply<00:05:07.980> some<00:05:08.580> sources<00:05:08.970> of<00:05:09.240> entropy<00:05:09.630> with 00:05:09.800 --> 00:05:09.810 align:start position:0% supply some sources of entropy with 00:05:09.810 --> 00:05:11.660 align:start position:0% supply some sources of entropy with random<00:05:10.140> bytes<00:05:10.320> which<00:05:10.710> is<00:05:10.920> known<00:05:11.220> to<00:05:11.250> be<00:05:11.370> safe 00:05:11.660 --> 00:05:11.670 align:start position:0% random bytes which is known to be safe 00:05:11.670 --> 00:05:14.030 align:start position:0% random bytes which is known to be safe it's<00:05:12.510> basically<00:05:12.900> you<00:05:13.230> want<00:05:13.380> to<00:05:13.410> bring<00:05:13.590> a<00:05:13.800> lot 00:05:14.030 --> 00:05:14.040 align:start position:0% it's basically you want to bring a lot 00:05:14.040 --> 00:05:15.470 align:start position:0% it's basically you want to bring a lot of<00:05:14.070> entropy<00:05:14.430> to<00:05:14.550> the<00:05:14.670> table<00:05:14.970> that's<00:05:15.180> very 00:05:15.470 --> 00:05:15.480 align:start position:0% of entropy to the table that's very 00:05:15.480 --> 00:05:19.130 align:start position:0% of entropy to the table that's very healthy<00:05:16.280> and<00:05:17.280> some<00:05:17.820> util<00:05:18.120> modules<00:05:18.540> and<00:05:18.870> some 00:05:19.130 --> 00:05:19.140 align:start position:0% healthy and some util modules and some 00:05:19.140 --> 00:05:22.880 align:start position:0% healthy and some util modules and some ENS<00:05:19.620> resolving<00:05:20.070> modules<00:05:21.290> so<00:05:22.290> here's<00:05:22.710> the 00:05:22.880 --> 00:05:22.890 align:start position:0% ENS resolving modules so here's the 00:05:22.890 --> 00:05:24.860 align:start position:0% ENS resolving modules so here's the schema<00:05:23.430> that<00:05:23.550> I<00:05:23.580> was<00:05:23.700> talking<00:05:24.030> about<00:05:24.060> so<00:05:24.690> this 00:05:24.860 --> 00:05:24.870 align:start position:0% schema that I was talking about so this 00:05:24.870 --> 00:05:26.900 align:start position:0% schema that I was talking about so this just<00:05:25.020> lays<00:05:25.230> out<00:05:25.440> the<00:05:25.680> entire<00:05:26.010> RPC 00:05:26.900 --> 00:05:26.910 align:start position:0% just lays out the entire RPC 00:05:26.910 --> 00:05:29.750 align:start position:0% just lays out the entire RPC specification<00:05:27.660> in<00:05:27.870> a<00:05:28.290> very<00:05:28.470> data<00:05:28.830> lean<00:05:29.250> format 00:05:29.750 --> 00:05:29.760 align:start position:0% specification in a very data lean format 00:05:29.760 --> 00:05:31.430 align:start position:0% specification in a very data lean format I'm<00:05:30.180> not<00:05:30.510> gonna<00:05:30.660> say<00:05:30.900> it's<00:05:31.050> particularly 00:05:31.430 --> 00:05:31.440 align:start position:0% I'm not gonna say it's particularly 00:05:31.440 --> 00:05:34.460 align:start position:0% I'm not gonna say it's particularly standardized<00:05:32.250> but<00:05:32.670> it<00:05:33.510> essentially<00:05:33.900> lays<00:05:34.230> out 00:05:34.460 --> 00:05:34.470 align:start position:0% standardized but it essentially lays out 00:05:34.470 --> 00:05:36.440 align:start position:0% standardized but it essentially lays out all<00:05:34.830> the<00:05:34.950> inputs<00:05:35.460> and<00:05:35.580> outputs<00:05:35.670> so<00:05:36.270> if<00:05:36.360> you 00:05:36.440 --> 00:05:36.450 align:start position:0% all the inputs and outputs so if you 00:05:36.450 --> 00:05:38.690 align:start position:0% all the inputs and outputs so if you want<00:05:36.570> to<00:05:36.630> take<00:05:36.810> this<00:05:36.990> and<00:05:37.320> go<00:05:37.560> into<00:05:37.920> you<00:05:38.670> know 00:05:38.690 --> 00:05:38.700 align:start position:0% want to take this and go into you know 00:05:38.700 --> 00:05:40.400 align:start position:0% want to take this and go into you know objective-c<00:05:39.390> or<00:05:39.750> if<00:05:39.810> you<00:05:39.870> want<00:05:40.020> to<00:05:40.110> take<00:05:40.260> this 00:05:40.400 --> 00:05:40.410 align:start position:0% objective-c or if you want to take this 00:05:40.410 --> 00:05:42.110 align:start position:0% objective-c or if you want to take this and<00:05:40.620> go<00:05:40.710> into<00:05:40.830> another<00:05:41.010> language<00:05:41.340> and<00:05:41.820> build 00:05:42.110 --> 00:05:42.120 align:start position:0% and go into another language and build 00:05:42.120 --> 00:05:44.360 align:start position:0% and go into another language and build an<00:05:42.330> RPC<00:05:42.630> layer<00:05:42.960> for<00:05:43.230> aetherium<00:05:43.650> you<00:05:44.070> can<00:05:44.190> just 00:05:44.360 --> 00:05:44.370 align:start position:0% an RPC layer for aetherium you can just 00:05:44.370 --> 00:05:45.710 align:start position:0% an RPC layer for aetherium you can just take<00:05:44.520> this<00:05:44.700> JSON<00:05:45.090> and<00:05:45.210> automatically 00:05:45.710 --> 00:05:45.720 align:start position:0% take this JSON and automatically 00:05:45.720 --> 00:05:48.440 align:start position:0% take this JSON and automatically generate<00:05:45.810> the<00:05:46.140> whole<00:05:46.380> thing<00:05:47.060> so<00:05:48.060> and<00:05:48.390> I 00:05:48.440 --> 00:05:48.450 align:start position:0% generate the whole thing so and I 00:05:48.450 --> 00:05:50.900 align:start position:0% generate the whole thing so and I actually<00:05:48.660> encourage<00:05:49.170> people<00:05:49.590> as<00:05:49.680> well<00:05:49.910> one 00:05:50.900 --> 00:05:50.910 align:start position:0% actually encourage people as well one 00:05:50.910 --> 00:05:52.940 align:start position:0% actually encourage people as well one thing<00:05:51.660> that<00:05:51.690> I've<00:05:51.930> found<00:05:51.960> with<00:05:52.410> doing<00:05:52.740> a<00:05:52.830> lot 00:05:52.940 --> 00:05:52.950 align:start position:0% thing that I've found with doing a lot 00:05:52.950 --> 00:05:54.200 align:start position:0% thing that I've found with doing a lot of<00:05:52.980> these<00:05:53.100> modules<00:05:53.310> is<00:05:53.790> it's<00:05:53.970> helped<00:05:54.150> people 00:05:54.200 --> 00:05:54.210 align:start position:0% of these modules is it's helped people 00:05:54.210 --> 00:05:56.780 align:start position:0% of these modules is it's helped people learn<00:05:54.750> more<00:05:55.050> about<00:05:55.440> what<00:05:55.830> the<00:05:55.920> RPC<00:05:56.250> layer<00:05:56.580> is 00:05:56.780 --> 00:05:56.790 align:start position:0% learn more about what the RPC layer is 00:05:56.790 --> 00:05:58.100 align:start position:0% learn more about what the RPC layer is and<00:05:57.090> what<00:05:57.180> it's<00:05:57.300> actually<00:05:57.420> doing<00:05:57.690> because 00:05:58.100 --> 00:05:58.110 align:start position:0% and what it's actually doing because 00:05:58.110 --> 00:06:00.560 align:start position:0% and what it's actually doing because it's<00:05:58.320> really<00:05:58.530> simple<00:05:58.890> like<00:05:59.280> what<00:06:00.000> web<00:06:00.210> freeze 00:06:00.560 --> 00:06:00.570 align:start position:0% it's really simple like what web freeze 00:06:00.570 --> 00:06:04.550 align:start position:0% it's really simple like what web freeze job<00:06:00.840> is<00:06:01.080> or<00:06:01.350> ethers<00:06:02.310> or<00:06:02.550> ETS<00:06:03.210> is<00:06:04.050> basically 00:06:04.550 --> 00:06:04.560 align:start position:0% job is or ethers or ETS is basically 00:06:04.560 --> 00:06:06.620 align:start position:0% job is or ethers or ETS is basically just<00:06:04.830> to<00:06:05.010> help<00:06:05.190> you<00:06:05.520> interact<00:06:05.850> with<00:06:06.180> the<00:06:06.390> node 00:06:06.620 --> 00:06:06.630 align:start position:0% just to help you interact with the node 00:06:06.630 --> 00:06:08.780 align:start position:0% just to help you interact with the node on<00:06:06.900> the<00:06:06.990> RPC<00:06:07.500> layer<00:06:07.710> and<00:06:07.980> format<00:06:08.400> some<00:06:08.580> data 00:06:08.780 --> 00:06:08.790 align:start position:0% on the RPC layer and format some data 00:06:08.790 --> 00:06:10.490 align:start position:0% on the RPC layer and format some data and<00:06:09.030> that's<00:06:09.180> it<00:06:09.420> and<00:06:09.630> it's<00:06:09.810> a<00:06:10.290> very 00:06:10.490 --> 00:06:10.500 align:start position:0% and that's it and it's a very 00:06:10.500 --> 00:06:13.070 align:start position:0% and that's it and it's a very straightforward<00:06:10.800> process<00:06:11.720> number<00:06:12.720> handling 00:06:13.070 --> 00:06:13.080 align:start position:0% straightforward process number handling 00:06:13.080 --> 00:06:15.740 align:start position:0% straightforward process number handling and<00:06:13.200> these<00:06:13.290> other<00:06:13.440> things<00:06:13.620> are<00:06:14.420> is<00:06:15.420> well 00:06:15.740 --> 00:06:15.750 align:start position:0% and these other things are is well 00:06:15.750 --> 00:06:18.070 align:start position:0% and these other things are is well something<00:06:16.320> that<00:06:16.350> should<00:06:17.160> be<00:06:17.190> simple<00:06:17.580> but 00:06:18.070 --> 00:06:18.080 align:start position:0% something that should be simple but 00:06:18.080 --> 00:06:20.810 align:start position:0% something that should be simple but turned<00:06:19.080> out<00:06:19.170> to<00:06:19.290> be<00:06:19.440> a<00:06:19.620> little<00:06:20.340> complicated 00:06:20.810 --> 00:06:20.820 align:start position:0% turned out to be a little complicated 00:06:20.820 --> 00:06:23.390 align:start position:0% turned out to be a little complicated for<00:06:21.150> some<00:06:21.270> reason<00:06:21.600> I<00:06:21.660> don't<00:06:21.720> know<00:06:22.020> why<00:06:22.400> so 00:06:23.390 --> 00:06:23.400 align:start position:0% for some reason I don't know why so 00:06:23.400 --> 00:06:26.260 align:start position:0% for some reason I don't know why so here's<00:06:24.090> just<00:06:24.150> each<00:06:24.840> J's<00:06:25.170> kind<00:06:25.560> of<00:06:25.620> an<00:06:25.710> action 00:06:26.260 --> 00:06:26.270 align:start position:0% here's just each J's kind of an action 00:06:26.270 --> 00:06:29.270 align:start position:0% here's just each J's kind of an action looks<00:06:27.270> very<00:06:27.450> similar<00:06:27.720> to<00:06:27.840> web<00:06:28.080> 3<00:06:28.350> and<00:06:28.560> I<00:06:29.010> follow 00:06:29.270 --> 00:06:29.280 align:start position:0% looks very similar to web 3 and I follow 00:06:29.280 --> 00:06:32.630 align:start position:0% looks very similar to web 3 and I follow a<00:06:29.400> very<00:06:29.550> similar<00:06:29.760> format<00:06:30.300> to<00:06:30.360> web<00:06:30.600> 3<00:06:30.900> and<00:06:31.830> other 00:06:32.630 --> 00:06:32.640 align:start position:0% a very similar format to web 3 and other 00:06:32.640 --> 00:06:35.340 align:start position:0% a very similar format to web 3 and other other<00:06:32.880> libraries<00:06:33.450> don't<00:06:33.630> necessarily 00:06:35.340 --> 00:06:35.350 align:start position:0% other libraries don't necessarily 00:06:35.350 --> 00:06:37.500 align:start position:0% other libraries don't necessarily so<00:06:35.950> just<00:06:36.640> just<00:06:36.850> to<00:06:36.910> give<00:06:37.030> you<00:06:37.090> an<00:06:37.150> idea<00:06:37.270> of<00:06:37.420> what 00:06:37.500 --> 00:06:37.510 align:start position:0% so just just to give you an idea of what 00:06:37.510 --> 00:06:40.380 align:start position:0% so just just to give you an idea of what that<00:06:37.630> looks<00:06:37.690> like<00:06:37.900> so<00:06:38.890> the<00:06:39.610> modules<00:06:40.030> are<00:06:40.240> all 00:06:40.380 --> 00:06:40.390 align:start position:0% that looks like so the modules are all 00:06:40.390 --> 00:06:42.150 align:start position:0% that looks like so the modules are all designed<00:06:41.230> with<00:06:41.500> the<00:06:41.650> same<00:06:41.680> kind<00:06:42.070> of 00:06:42.150 --> 00:06:42.160 align:start position:0% designed with the same kind of 00:06:42.160 --> 00:06:44.460 align:start position:0% designed with the same kind of documentation<00:06:42.760> and<00:06:43.270> standards<00:06:44.080> in<00:06:44.230> mind 00:06:44.460 --> 00:06:44.470 align:start position:0% documentation and standards in mind 00:06:44.470 --> 00:06:48.210 align:start position:0% documentation and standards in mind around<00:06:45.190> testing<00:06:45.700> and<00:06:45.850> so<00:06:46.000> forth<00:06:46.270> and<00:06:47.230> try<00:06:48.160> to 00:06:48.210 --> 00:06:48.220 align:start position:0% around testing and so forth and try to 00:06:48.220 --> 00:06:50.220 align:start position:0% around testing and so forth and try to make<00:06:48.550> the<00:06:48.730> exports<00:06:49.240> clean<00:06:49.540> and<00:06:49.750> simple<00:06:49.900> and 00:06:50.220 --> 00:06:50.230 align:start position:0% make the exports clean and simple and 00:06:50.230 --> 00:06:53.790 align:start position:0% make the exports clean and simple and easy<00:06:50.380> to<00:06:50.620> update<00:06:50.980> and<00:06:51.160> upgrade<00:06:52.200> so<00:06:53.200> basically 00:06:53.790 --> 00:06:53.800 align:start position:0% easy to update and upgrade so basically 00:06:53.800 --> 00:06:56.100 align:start position:0% easy to update and upgrade so basically like<00:06:54.010> you<00:06:54.340> know<00:06:54.370> I<00:06:54.760> wanted<00:06:55.420> to<00:06:55.510> build<00:06:55.660> a<00:06:55.840> set<00:06:55.990> of 00:06:56.100 --> 00:06:56.110 align:start position:0% like you know I wanted to build a set of 00:06:56.110 --> 00:06:57.900 align:start position:0% like you know I wanted to build a set of modules<00:06:56.230> that<00:06:56.770> the<00:06:57.160> community<00:06:57.550> could<00:06:57.670> help 00:06:57.900 --> 00:06:57.910 align:start position:0% modules that the community could help 00:06:57.910 --> 00:07:00.150 align:start position:0% modules that the community could help out<00:06:58.060> with<00:06:58.090> and<00:06:58.660> if<00:06:59.260> anything<00:06:59.590> just<00:06:59.920> learn 00:07:00.150 --> 00:07:00.160 align:start position:0% out with and if anything just learn 00:07:00.160 --> 00:07:03.360 align:start position:0% out with and if anything just learn about<00:07:00.490> the<00:07:01.240> layer<00:07:01.480> and<00:07:01.900> also<00:07:02.110> if<00:07:02.620> they<00:07:03.160> need 00:07:03.360 --> 00:07:03.370 align:start position:0% about the layer and also if they need 00:07:03.370 --> 00:07:05.010 align:start position:0% about the layer and also if they need things<00:07:03.670> for<00:07:03.880> certain<00:07:04.000> architecture<00:07:04.630> pieces 00:07:05.010 --> 00:07:05.020 align:start position:0% things for certain architecture pieces 00:07:05.020 --> 00:07:07.920 align:start position:0% things for certain architecture pieces they<00:07:05.170> can<00:07:05.200> use<00:07:05.830> these<00:07:05.980> modules<00:07:06.360> so<00:07:07.360> if<00:07:07.660> chess 00:07:07.920 --> 00:07:07.930 align:start position:0% they can use these modules so if chess 00:07:07.930 --> 00:07:11.070 align:start position:0% they can use these modules so if chess is<00:07:08.170> used<00:07:08.440> in<00:07:08.740> production<00:07:09.390> for<00:07:10.390> meta<00:07:10.540> masks<00:07:10.750> and 00:07:11.070 --> 00:07:11.080 align:start position:0% is used in production for meta masks and 00:07:11.080 --> 00:07:13.620 align:start position:0% is used in production for meta masks and Fuhrer<00:07:11.350> and<00:07:11.500> truffle<00:07:11.860> mainly<00:07:12.520> for<00:07:12.820> certain 00:07:13.620 --> 00:07:13.630 align:start position:0% Fuhrer and truffle mainly for certain 00:07:13.630 --> 00:07:15.540 align:start position:0% Fuhrer and truffle mainly for certain bits<00:07:13.810> of<00:07:13.930> encoding<00:07:14.380> and<00:07:14.470> decoding<00:07:14.590> and<00:07:15.160> RPC 00:07:15.540 --> 00:07:15.550 align:start position:0% bits of encoding and decoding and RPC 00:07:15.550 --> 00:07:19.680 align:start position:0% bits of encoding and decoding and RPC layer<00:07:15.730> stuff<00:07:16.230> and<00:07:17.670> just<00:07:18.670> to<00:07:18.790> go<00:07:18.940> over<00:07:18.970> a<00:07:19.240> little 00:07:19.680 --> 00:07:19.690 align:start position:0% layer stuff and just to go over a little 00:07:19.690 --> 00:07:21.870 align:start position:0% layer stuff and just to go over a little bit<00:07:19.840> of<00:07:19.900> the<00:07:20.080> thinking<00:07:20.440> behind<00:07:20.730> how<00:07:21.730> its 00:07:21.870 --> 00:07:21.880 align:start position:0% bit of the thinking behind how its 00:07:21.880 --> 00:07:24.300 align:start position:0% bit of the thinking behind how its developed<00:07:22.360> so<00:07:22.630> I<00:07:22.900> like<00:07:23.470> safe<00:07:23.770> versioning 00:07:24.300 --> 00:07:24.310 align:start position:0% developed so I like safe versioning 00:07:24.310 --> 00:07:25.950 align:start position:0% developed so I like safe versioning where<00:07:24.640> while<00:07:24.970> I<00:07:25.030> call<00:07:25.270> it<00:07:25.360> safe<00:07:25.540> versioning 00:07:25.950 --> 00:07:25.960 align:start position:0% where while I call it safe versioning 00:07:25.960 --> 00:07:27.690 align:start position:0% where while I call it safe versioning where<00:07:26.530> you<00:07:26.620> don't<00:07:26.800> have<00:07:26.920> floating<00:07:27.370> NPM 00:07:27.690 --> 00:07:27.700 align:start position:0% where you don't have floating NPM 00:07:27.700 --> 00:07:30.330 align:start position:0% where you don't have floating NPM versions<00:07:28.150> across<00:07:28.840> the<00:07:28.990> modules<00:07:29.380> just<00:07:29.560> because 00:07:30.330 --> 00:07:30.340 align:start position:0% versions across the modules just because 00:07:30.340 --> 00:07:33.120 align:start position:0% versions across the modules just because I<00:07:30.610> found<00:07:30.880> that<00:07:31.150> when<00:07:31.540> modules<00:07:31.960> update<00:07:32.440> the<00:07:32.800> NPM 00:07:33.120 --> 00:07:33.130 align:start position:0% I found that when modules update the NPM 00:07:33.130 --> 00:07:34.950 align:start position:0% I found that when modules update the NPM versions<00:07:33.520> they<00:07:33.790> shove<00:07:34.030> up<00:07:34.210> to<00:07:34.330> the<00:07:34.450> top<00:07:34.660> and 00:07:34.950 --> 00:07:34.960 align:start position:0% versions they shove up to the top and 00:07:34.960 --> 00:07:36.300 align:start position:0% versions they shove up to the top and then<00:07:35.050> potentially<00:07:35.560> cause<00:07:35.740> problems<00:07:36.160> you 00:07:36.300 --> 00:07:36.310 align:start position:0% then potentially cause problems you 00:07:36.310 --> 00:07:38.790 align:start position:0% then potentially cause problems you can't<00:07:36.550> foresee<00:07:36.880> so<00:07:37.690> I<00:07:37.720> like<00:07:38.170> to<00:07:38.200> use<00:07:38.440> hardened 00:07:38.790 --> 00:07:38.800 align:start position:0% can't foresee so I like to use hardened 00:07:38.800 --> 00:07:41.460 align:start position:0% can't foresee so I like to use hardened versions<00:07:39.190> across<00:07:39.490> NPM<00:07:40.150> and<00:07:40.570> just<00:07:41.200> kind<00:07:41.380> of 00:07:41.460 --> 00:07:41.470 align:start position:0% versions across NPM and just kind of 00:07:41.470 --> 00:07:44.070 align:start position:0% versions across NPM and just kind of keep<00:07:41.620> the<00:07:41.740> updating<00:07:42.570> kind<00:07:43.570> of<00:07:43.660> slow<00:07:43.870> and 00:07:44.070 --> 00:07:44.080 align:start position:0% keep the updating kind of slow and 00:07:44.080 --> 00:07:45.750 align:start position:0% keep the updating kind of slow and boring<00:07:44.230> but<00:07:44.650> more<00:07:44.920> meticulous<00:07:45.430> and<00:07:45.670> more 00:07:45.750 --> 00:07:45.760 align:start position:0% boring but more meticulous and more 00:07:45.760 --> 00:07:49.050 align:start position:0% boring but more meticulous and more tested<00:07:46.350> all<00:07:47.350> the<00:07:47.410> modules<00:07:48.010> are<00:07:48.250> driven<00:07:48.850> by 00:07:49.050 --> 00:07:49.060 align:start position:0% tested all the modules are driven by 00:07:49.060 --> 00:07:51.000 align:start position:0% tested all the modules are driven by what<00:07:49.360> their<00:07:49.540> dependencies<00:07:50.080> are<00:07:50.260> so<00:07:50.710> there's<00:07:50.980> a 00:07:51.000 --> 00:07:51.010 align:start position:0% what their dependencies are so there's a 00:07:51.010 --> 00:07:53.550 align:start position:0% what their dependencies are so there's a lot<00:07:51.160> of<00:07:51.250> nice<00:07:51.430> isolation<00:07:52.150> between<00:07:52.420> all<00:07:53.410> the 00:07:53.550 --> 00:07:53.560 align:start position:0% lot of nice isolation between all the 00:07:53.560 --> 00:07:56.370 align:start position:0% lot of nice isolation between all the different<00:07:53.830> the<00:07:53.860> various<00:07:54.190> modules<00:07:55.110> it's<00:07:56.110> built 00:07:56.370 --> 00:07:56.380 align:start position:0% different the various modules it's built 00:07:56.380 --> 00:07:58.620 align:start position:0% different the various modules it's built with<00:07:56.590> the<00:07:56.740> DAP<00:07:56.920> and<00:07:56.950> app<00:07:57.310> architecture<00:07:58.300> kind 00:07:58.620 --> 00:07:58.630 align:start position:0% with the DAP and app architecture kind 00:07:58.630 --> 00:08:02.400 align:start position:0% with the DAP and app architecture kind target<00:07:59.050> in<00:07:59.110> mind<00:07:59.340> small<00:08:00.340> and<00:08:00.520> concise<00:08:01.410> async 00:08:02.400 --> 00:08:02.410 align:start position:0% target in mind small and concise async 00:08:02.410 --> 00:08:04.980 align:start position:0% target in mind small and concise async only<00:08:02.790> and<00:08:03.790> I<00:08:03.880> try<00:08:04.090> to<00:08:04.120> fail<00:08:04.390> as<00:08:04.540> loudly<00:08:04.780> as 00:08:04.980 --> 00:08:04.990 align:start position:0% only and I try to fail as loudly as 00:08:04.990 --> 00:08:06.150 align:start position:0% only and I try to fail as loudly as quickly<00:08:05.350> as<00:08:05.560> possible 00:08:06.150 --> 00:08:06.160 align:start position:0% quickly as possible 00:08:06.160 --> 00:08:09.120 align:start position:0% quickly as possible everywhere<00:08:06.670> strong<00:08:07.660> types<00:08:07.960> as<00:08:08.380> best<00:08:08.680> as<00:08:08.890> you 00:08:09.120 --> 00:08:09.130 align:start position:0% everywhere strong types as best as you 00:08:09.130 --> 00:08:11.370 align:start position:0% everywhere strong types as best as you can<00:08:09.310> get<00:08:09.460> JavaScript<00:08:09.940> strong<00:08:10.450> types<00:08:10.690> although 00:08:11.370 --> 00:08:11.380 align:start position:0% can get JavaScript strong types although 00:08:11.380 --> 00:08:13.560 align:start position:0% can get JavaScript strong types although I<00:08:11.530> do<00:08:11.650> support<00:08:12.190> some<00:08:12.550> a<00:08:12.730> morphic<00:08:13.150> number 00:08:13.560 --> 00:08:13.570 align:start position:0% I do support some a morphic number 00:08:13.570 --> 00:08:15.900 align:start position:0% I do support some a morphic number handling<00:08:13.930> and<00:08:14.250> I'm<00:08:15.250> kind<00:08:15.460> of<00:08:15.490> looking<00:08:15.610> to 00:08:15.900 --> 00:08:15.910 align:start position:0% handling and I'm kind of looking to 00:08:15.910 --> 00:08:18.870 align:start position:0% handling and I'm kind of looking to remove<00:08:16.120> that<00:08:16.440> is<00:08:17.440> well<00:08:17.980> community<00:08:18.610> driven 00:08:18.870 --> 00:08:18.880 align:start position:0% remove that is well community driven 00:08:18.880 --> 00:08:20.820 align:start position:0% remove that is well community driven design<00:08:19.000> so<00:08:19.450> keeping<00:08:19.810> the<00:08:19.930> code<00:08:20.080> clean<00:08:20.380> simple 00:08:20.820 --> 00:08:20.830 align:start position:0% design so keeping the code clean simple 00:08:20.830 --> 00:08:23.970 align:start position:0% design so keeping the code clean simple and<00:08:20.980> being<00:08:21.430> able<00:08:21.520> to<00:08:21.670> be<00:08:22.660> upgraded<00:08:23.170> very 00:08:23.970 --> 00:08:23.980 align:start position:0% and being able to be upgraded very 00:08:23.980 --> 00:08:26.250 align:start position:0% and being able to be upgraded very easily<00:08:24.160> and<00:08:24.670> as<00:08:25.060> well<00:08:25.240> trying<00:08:26.050> to<00:08:26.110> keep 00:08:26.250 --> 00:08:26.260 align:start position:0% easily and as well trying to keep 00:08:26.260 --> 00:08:27.990 align:start position:0% easily and as well trying to keep opinions<00:08:26.740> off<00:08:27.100> the<00:08:27.280> table<00:08:27.610> as<00:08:27.700> best<00:08:27.880> as 00:08:27.990 --> 00:08:28.000 align:start position:0% opinions off the table as best as 00:08:28.000 --> 00:08:30.060 align:start position:0% opinions off the table as best as possible<00:08:28.030> and<00:08:28.720> keep<00:08:28.810> configurability<00:08:29.650> really 00:08:30.060 --> 00:08:30.070 align:start position:0% possible and keep configurability really 00:08:30.070 --> 00:08:33.089 align:start position:0% possible and keep configurability really high<00:08:30.220> across<00:08:31.000> the<00:08:31.180> whole<00:08:31.300> stack<00:08:31.680> so<00:08:32.680> a<00:08:32.710> big 00:08:33.089 --> 00:08:33.099 align:start position:0% high across the whole stack so a big 00:08:33.099 --> 00:08:37.700 align:start position:0% high across the whole stack so a big feature<00:08:33.660> and<00:08:34.770> kind<00:08:35.770> of<00:08:35.830> a<00:08:35.919> big<00:08:36.099> note<00:08:36.580> is<00:08:36.880> that 00:08:37.700 --> 00:08:37.710 align:start position:0% feature and kind of a big note is that 00:08:37.710 --> 00:08:41.250 align:start position:0% feature and kind of a big note is that we<00:08:38.710> use<00:08:38.890> be<00:08:39.219> naso<00:08:39.910> not<00:08:40.210> big<00:08:40.419> number<00:08:40.660> j/s<00:08:40.990> and 00:08:41.250 --> 00:08:41.260 align:start position:0% we use be naso not big number j/s and 00:08:41.260 --> 00:08:43.409 align:start position:0% we use be naso not big number j/s and the<00:08:42.099> pros<00:08:42.340> of<00:08:42.370> that<00:08:42.700> are<00:08:42.849> that<00:08:43.000> its<00:08:43.210> absolute 00:08:43.409 --> 00:08:43.419 align:start position:0% the pros of that are that its absolute 00:08:43.419 --> 00:08:45.810 align:start position:0% the pros of that are that its absolute precision<00:08:44.110> by<00:08:44.350> default<00:08:44.710> so<00:08:45.250> it<00:08:45.430> doesn't 00:08:45.810 --> 00:08:45.820 align:start position:0% precision by default so it doesn't 00:08:45.820 --> 00:08:47.940 align:start position:0% precision by default so it doesn't support<00:08:45.940> decimals<00:08:46.540> and<00:08:46.720> floats<00:08:46.960> which<00:08:47.740> are 00:08:47.940 --> 00:08:47.950 align:start position:0% support decimals and floats which are 00:08:47.950 --> 00:08:49.170 align:start position:0% support decimals and floats which are potentially<00:08:48.460> very<00:08:48.610> dangerous 00:08:49.170 --> 00:08:49.180 align:start position:0% potentially very dangerous 00:08:49.180 --> 00:08:50.730 align:start position:0% potentially very dangerous considering<00:08:49.779> you<00:08:50.080> know<00:08:50.200> that<00:08:50.529> we're<00:08:50.649> working 00:08:50.730 --> 00:08:50.740 align:start position:0% considering you know that we're working 00:08:50.740 --> 00:08:52.470 align:start position:0% considering you know that we're working with<00:08:50.920> money<00:08:51.220> and<00:08:51.520> rounding<00:08:52.060> is<00:08:52.210> not 00:08:52.470 --> 00:08:52.480 align:start position:0% with money and rounding is not 00:08:52.480 --> 00:08:57.240 align:start position:0% with money and rounding is not necessarily<00:08:53.070> the<00:08:54.070> greatest<00:08:54.250> thing<00:08:54.630> and<00:08:56.250> it's 00:08:57.240 --> 00:08:57.250 align:start position:0% necessarily the greatest thing and it's 00:08:57.250 --> 00:08:59.370 align:start position:0% necessarily the greatest thing and it's heavily<00:08:57.550> used<00:08:57.820> in<00:08:57.940> interoperable<00:08:58.510> Viator<00:08:58.930> MJS 00:08:59.370 --> 00:08:59.380 align:start position:0% heavily used in interoperable Viator MJS 00:08:59.380 --> 00:09:02.730 align:start position:0% heavily used in interoperable Viator MJS and<00:08:59.680> ethers<00:09:00.040> Jess<00:09:00.570> but<00:09:01.570> the<00:09:02.050> cons<00:09:02.410> are<00:09:02.680> that 00:09:02.730 --> 00:09:02.740 align:start position:0% and ethers Jess but the cons are that 00:09:02.740 --> 00:09:04.470 align:start position:0% and ethers Jess but the cons are that it's<00:09:03.070> not<00:09:03.220> necessarily<00:09:03.700> interoperable<00:09:04.300> with 00:09:04.470 --> 00:09:04.480 align:start position:0% it's not necessarily interoperable with 00:09:04.480 --> 00:09:08.910 align:start position:0% it's not necessarily interoperable with big<00:09:04.720> number<00:09:05.050> Jas<00:09:06.029> web<00:09:07.029> 3<00:09:07.360> and<00:09:07.740> sometimes<00:09:08.740> it 00:09:08.910 --> 00:09:08.920 align:start position:0% big number Jas web 3 and sometimes it 00:09:08.920 --> 00:09:11.370 align:start position:0% big number Jas web 3 and sometimes it accepts<00:09:09.310> invalid<00:09:09.940> values<00:09:10.300> i'm<00:09:10.660> prefix<00:09:11.110> X 00:09:11.370 --> 00:09:11.380 align:start position:0% accepts invalid values i'm prefix X 00:09:11.380 --> 00:09:14.400 align:start position:0% accepts invalid values i'm prefix X which<00:09:12.100> is<00:09:12.279> somewhat<00:09:12.700> dangerous<00:09:12.880> but<00:09:13.390> we<00:09:14.200> kind 00:09:14.400 --> 00:09:14.410 align:start position:0% which is somewhat dangerous but we kind 00:09:14.410 --> 00:09:16.590 align:start position:0% which is somewhat dangerous but we kind of<00:09:14.470> take<00:09:14.620> care<00:09:14.800> of<00:09:14.920> that<00:09:15.100> on<00:09:15.370> another<00:09:16.120> layer<00:09:16.390> so 00:09:16.590 --> 00:09:16.600 align:start position:0% of take care of that on another layer so 00:09:16.600 --> 00:09:17.579 align:start position:0% of take care of that on another layer so you<00:09:16.750> don't<00:09:16.930> really<00:09:17.020> have<00:09:17.200> to<00:09:17.260> think<00:09:17.290> about 00:09:17.579 --> 00:09:17.589 align:start position:0% you don't really have to think about 00:09:17.589 --> 00:09:20.340 align:start position:0% you don't really have to think about that<00:09:17.740> but<00:09:18.399> it's<00:09:18.520> just<00:09:18.610> something<00:09:18.850> to<00:09:18.910> consider 00:09:20.340 --> 00:09:20.350 align:start position:0% that but it's just something to consider 00:09:20.350 --> 00:09:22.650 align:start position:0% that but it's just something to consider so<00:09:20.649> signing<00:09:21.610> providers<00:09:22.089> and<00:09:22.420> account 00:09:22.650 --> 00:09:22.660 align:start position:0% so signing providers and account 00:09:22.660 --> 00:09:25.710 align:start position:0% so signing providers and account generation<00:09:23.170> so<00:09:23.800> just<00:09:24.730> simple<00:09:24.970> providers<00:09:25.420> to 00:09:25.710 --> 00:09:25.720 align:start position:0% generation so just simple providers to 00:09:25.720 --> 00:09:28.199 align:start position:0% generation so just simple providers to kind<00:09:26.200> of<00:09:26.260> shove<00:09:26.529> in<00:09:26.709> sign<00:09:27.640> transaction 00:09:28.199 --> 00:09:28.209 align:start position:0% kind of shove in sign transaction 00:09:28.209 --> 00:09:33.320 align:start position:0% kind of shove in sign transaction packets<00:09:28.920> and<00:09:29.920> and<00:09:30.790> kind<00:09:31.360> of<00:09:31.420> handle<00:09:31.720> accounts 00:09:33.320 --> 00:09:33.330 align:start position:0% packets and and kind of handle accounts 00:09:33.330 --> 00:09:36.690 align:start position:0% packets and and kind of handle accounts we<00:09:34.330> provide<00:09:34.600> those<00:09:34.810> too<00:09:35.020> and<00:09:35.230> as<00:09:36.160> for<00:09:36.459> some<00:09:36.580> of 00:09:36.690 --> 00:09:36.700 align:start position:0% we provide those too and as for some of 00:09:36.700 --> 00:09:38.639 align:start position:0% we provide those too and as for some of the<00:09:36.790> dev<00:09:36.970> tools<00:09:37.180> that<00:09:37.450> we<00:09:37.540> offer<00:09:37.690> so<00:09:38.290> this<00:09:38.470> is<00:09:38.620> a 00:09:38.639 --> 00:09:38.649 align:start position:0% the dev tools that we offer so this is a 00:09:38.649 --> 00:09:40.290 align:start position:0% the dev tools that we offer so this is a tool<00:09:38.980> that<00:09:39.010> I've<00:09:39.310> been<00:09:39.339> working<00:09:39.700> on<00:09:39.850> for<00:09:40.270> quite 00:09:40.290 --> 00:09:40.300 align:start position:0% tool that I've been working on for quite 00:09:40.300 --> 00:09:43.070 align:start position:0% tool that I've been working on for quite some<00:09:40.779> time<00:09:40.810> so<00:09:41.290> it's<00:09:42.100> a<00:09:42.310> highly<00:09:42.700> configurable 00:09:43.070 --> 00:09:43.080 align:start position:0% some time so it's a highly configurable 00:09:43.080 --> 00:09:45.930 align:start position:0% some time so it's a highly configurable multistage<00:09:44.080> language<00:09:44.860> agnostic<00:09:45.040> contract 00:09:45.930 --> 00:09:45.940 align:start position:0% multistage language agnostic contract 00:09:45.940 --> 00:09:48.540 align:start position:0% multistage language agnostic contract deployment<00:09:46.420> facility<00:09:46.810> so<00:09:47.649> the<00:09:47.920> idea<00:09:48.220> here<00:09:48.279> is 00:09:48.540 --> 00:09:48.550 align:start position:0% deployment facility so the idea here is 00:09:48.550 --> 00:09:50.400 align:start position:0% deployment facility so the idea here is is<00:09:48.940> that<00:09:49.180> you<00:09:49.390> have<00:09:49.570> something<00:09:49.930> similar<00:09:50.080> to 00:09:50.400 --> 00:09:50.410 align:start position:0% is that you have something similar to 00:09:50.410 --> 00:09:52.800 align:start position:0% is that you have something similar to web<00:09:50.560> pack<00:09:50.800> where<00:09:51.459> you<00:09:52.240> have<00:09:52.360> this<00:09:52.540> single 00:09:52.800 --> 00:09:52.810 align:start position:0% web pack where you have this single 00:09:52.810 --> 00:09:54.390 align:start position:0% web pack where you have this single JavaScript<00:09:53.529> module<00:09:53.920> it's<00:09:54.040> a<00:09:54.100> highly 00:09:54.390 --> 00:09:54.400 align:start position:0% JavaScript module it's a highly 00:09:54.400 --> 00:09:58.350 align:start position:0% JavaScript module it's a highly configured<00:09:55.230> deployment<00:09:56.230> stage<00:09:56.440> module<00:09:57.360> and 00:09:58.350 --> 00:09:58.360 align:start position:0% configured deployment stage module and 00:09:58.360 --> 00:10:00.269 align:start position:0% configured deployment stage module and basically<00:09:58.900> the<00:09:59.080> idea<00:09:59.320> is<00:09:59.380> you<00:09:59.529> take<00:09:59.950> all<00:10:00.130> these 00:10:00.269 --> 00:10:00.279 align:start position:0% basically the idea is you take all these 00:10:00.279 --> 00:10:02.960 align:start position:0% basically the idea is you take all these raw<00:10:00.550> imports<00:10:01.120> like<00:10:01.330> JSON<00:10:01.870> files<00:10:02.140> contracts 00:10:02.960 --> 00:10:02.970 align:start position:0% raw imports like JSON files contracts 00:10:02.970 --> 00:10:05.040 align:start position:0% raw imports like JSON files contracts you<00:10:03.970> know<00:10:04.000> things<00:10:04.270> that<00:10:04.420> need<00:10:04.540> to<00:10:04.570> be<00:10:04.660> plotted 00:10:05.040 --> 00:10:05.050 align:start position:0% you know things that need to be plotted 00:10:05.050 --> 00:10:09.150 align:start position:0% you know things that need to be plotted out<00:10:05.520> you<00:10:06.520> shove<00:10:07.240> them<00:10:07.390> through<00:10:07.920> loaders<00:10:08.920> that 00:10:09.150 --> 00:10:09.160 align:start position:0% out you shove them through loaders that 00:10:09.160 --> 00:10:11.300 align:start position:0% out you shove them through loaders that you<00:10:09.700> can<00:10:09.850> define<00:10:10.089> yourself<00:10:10.510> like<00:10:10.750> web<00:10:10.930> pack 00:10:11.300 --> 00:10:11.310 align:start position:0% you can define yourself like web pack 00:10:11.310 --> 00:10:13.440 align:start position:0% you can define yourself like web pack and<00:10:12.310> then<00:10:12.520> you<00:10:12.790> run<00:10:13.120> them<00:10:13.270> through<00:10:13.300> a 00:10:13.440 --> 00:10:13.450 align:start position:0% and then you run them through a 00:10:13.450 --> 00:10:15.570 align:start position:0% and then you run them through a deployment<00:10:13.779> module<00:10:14.320> that<00:10:15.310> can<00:10:15.490> basically 00:10:15.570 --> 00:10:15.580 align:start position:0% deployment module that can basically 00:10:15.580 --> 00:10:17.730 align:start position:0% deployment module that can basically take<00:10:16.060> that<00:10:16.089> data<00:10:16.510> it's<00:10:17.170> formatted<00:10:17.589> the<00:10:17.709> way 00:10:17.730 --> 00:10:17.740 align:start position:0% take that data it's formatted the way 00:10:17.740 --> 00:10:19.500 align:start position:0% take that data it's formatted the way you<00:10:17.890> want<00:10:18.160> and<00:10:18.490> now<00:10:18.700> you<00:10:18.760> you<00:10:19.240> run<00:10:19.390> the 00:10:19.500 --> 00:10:19.510 align:start position:0% you want and now you you run the 00:10:19.510 --> 00:10:21.030 align:start position:0% you want and now you you run the deployment<00:10:19.959> staging<00:10:20.350> the<00:10:20.470> way<00:10:20.589> that<00:10:20.740> you<00:10:20.800> want 00:10:21.030 --> 00:10:21.040 align:start position:0% deployment staging the way that you want 00:10:21.040 --> 00:10:24.449 align:start position:0% deployment staging the way that you want it<00:10:21.180> and<00:10:22.180> then<00:10:22.779> you<00:10:23.080> kind<00:10:23.290> of<00:10:23.320> fire<00:10:23.529> done<00:10:24.220> at<00:10:24.339> the 00:10:24.449 --> 00:10:24.459 align:start position:0% it and then you kind of fire done at the 00:10:24.459 --> 00:10:28.320 align:start position:0% it and then you kind of fire done at the end<00:10:24.779> and<00:10:25.779> then<00:10:25.930> you<00:10:26.050> can<00:10:26.230> output<00:10:26.770> your<00:10:27.520> data 00:10:28.320 --> 00:10:28.330 align:start position:0% end and then you can output your data 00:10:28.330 --> 00:10:30.860 align:start position:0% end and then you can output your data with<00:10:28.900> simple<00:10:29.529> output<00:10:29.890> formatting<00:10:30.430> plugins 00:10:30.860 --> 00:10:30.870 align:start position:0% with simple output formatting plugins 00:10:30.870 --> 00:10:33.600 align:start position:0% with simple output formatting plugins and<00:10:31.870> the<00:10:32.140> result<00:10:32.500> is<00:10:32.709> that<00:10:32.740> you<00:10:33.010> get<00:10:33.130> this<00:10:33.279> very 00:10:33.600 --> 00:10:33.610 align:start position:0% and the result is that you get this very 00:10:33.610 --> 00:10:35.819 align:start position:0% and the result is that you get this very complex<00:10:34.150> deployment<00:10:34.839> staging<00:10:35.200> facility<00:10:35.680> for 00:10:35.819 --> 00:10:35.829 align:start position:0% complex deployment staging facility for 00:10:35.829 --> 00:10:38.810 align:start position:0% complex deployment staging facility for contracts<00:10:36.339> that<00:10:36.730> you<00:10:36.790> can<00:10:37.240> kind<00:10:37.450> of<00:10:37.510> tuck<00:10:38.140> into 00:10:38.810 --> 00:10:38.820 align:start position:0% contracts that you can kind of tuck into 00:10:38.820 --> 00:10:41.519 align:start position:0% contracts that you can kind of tuck into mocha<00:10:39.820> you<00:10:40.060> can<00:10:40.270> tuck<00:10:40.450> into<00:10:40.600> whatever<00:10:41.050> testing 00:10:41.519 --> 00:10:41.529 align:start position:0% mocha you can tuck into whatever testing 00:10:41.529 --> 00:10:44.130 align:start position:0% mocha you can tuck into whatever testing facility<00:10:41.950> you<00:10:42.040> want<00:10:42.420> and<00:10:43.420> you<00:10:43.870> can<00:10:43.990> also 00:10:44.130 --> 00:10:44.140 align:start position:0% facility you want and you can also 00:10:44.140 --> 00:10:46.290 align:start position:0% facility you want and you can also define<00:10:44.470> your<00:10:44.950> environment<00:10:45.550> really<00:10:45.820> easily<00:10:46.209> so 00:10:46.290 --> 00:10:46.300 align:start position:0% define your environment really easily so 00:10:46.300 --> 00:10:47.970 align:start position:0% define your environment really easily so you're<00:10:46.690> just<00:10:46.810> putting<00:10:47.079> in<00:10:47.290> the<00:10:47.320> raw<00:10:47.560> provider 00:10:47.970 --> 00:10:47.980 align:start position:0% you're just putting in the raw provider 00:10:47.980 --> 00:10:52.050 align:start position:0% you're just putting in the raw provider object<00:10:48.520> and<00:10:49.420> a<00:10:50.170> name<00:10:50.649> and<00:10:50.980> your<00:10:51.700> default 00:10:52.050 --> 00:10:52.060 align:start position:0% object and a name and your default 00:10:52.060 --> 00:10:54.480 align:start position:0% object and a name and your default transactions<00:10:52.660> and<00:10:52.839> objects<00:10:53.589> and<00:10:53.829> then<00:10:54.370> you're 00:10:54.480 --> 00:10:54.490 align:start position:0% transactions and objects and then you're 00:10:54.490 --> 00:10:55.500 align:start position:0% transactions and objects and then you're just<00:10:54.579> going<00:10:54.730> to<00:10:54.820> run<00:10:55.000> that<00:10:55.149> deployment 00:10:55.500 --> 00:10:55.510 align:start position:0% just going to run that deployment 00:10:55.510 --> 00:10:57.780 align:start position:0% just going to run that deployment sequence<00:10:56.050> and<00:10:56.440> the<00:10:56.829> thing<00:10:57.040> is<00:10:57.190> is<00:10:57.430> there's<00:10:57.760> a 00:10:57.780 --> 00:10:57.790 align:start position:0% sequence and the thing is is there's a 00:10:57.790 --> 00:10:59.220 align:start position:0% sequence and the thing is is there's a lot<00:10:57.940> of<00:10:58.060> tools<00:10:58.300> out<00:10:58.480> there<00:10:58.510> like<00:10:58.839> truffle<00:10:59.200> and 00:10:59.220 --> 00:10:59.230 align:start position:0% lot of tools out there like truffle and 00:10:59.230 --> 00:11:00.510 align:start position:0% lot of tools out there like truffle and everything<00:10:59.680> and<00:11:00.010> they're<00:11:00.160> getting<00:11:00.279> better 00:11:00.510 --> 00:11:00.520 align:start position:0% everything and they're getting better 00:11:00.520 --> 00:11:01.500 align:start position:0% everything and they're getting better all<00:11:00.910> the<00:11:00.940> time 00:11:01.500 --> 00:11:01.510 align:start position:0% all the time 00:11:01.510 --> 00:11:02.910 align:start position:0% all the time but<00:11:02.079> the<00:11:02.529> this 00:11:02.910 --> 00:11:02.920 align:start position:0% but the this 00:11:02.920 --> 00:11:04.410 align:start position:0% but the this essentially<00:11:03.519> what<00:11:03.730> I<00:11:03.760> wanted<00:11:04.120> from<00:11:04.300> the 00:11:04.410 --> 00:11:04.420 align:start position:0% essentially what I wanted from the 00:11:04.420 --> 00:11:06.240 align:start position:0% essentially what I wanted from the beginning<00:11:04.810> which<00:11:05.170> is<00:11:05.380> just<00:11:05.920> the<00:11:06.040> sequence 00:11:06.240 --> 00:11:06.250 align:start position:0% beginning which is just the sequence 00:11:06.250 --> 00:11:08.069 align:start position:0% beginning which is just the sequence tool<00:11:06.730> that<00:11:07.060> I<00:11:07.089> could<00:11:07.360> run<00:11:07.540> complex 00:11:08.069 --> 00:11:08.079 align:start position:0% tool that I could run complex 00:11:08.079 --> 00:11:10.560 align:start position:0% tool that I could run complex deployments<00:11:08.769> with<00:11:08.920> and<00:11:09.220> just<00:11:09.519> do<00:11:10.149> that<00:11:10.300> in<00:11:10.510> a 00:11:10.560 --> 00:11:10.570 align:start position:0% deployments with and just do that in a 00:11:10.570 --> 00:11:12.930 align:start position:0% deployments with and just do that in a very<00:11:10.690> fluent<00:11:11.139> way<00:11:11.339> it<00:11:12.339> is<00:11:12.639> high 00:11:12.930 --> 00:11:12.940 align:start position:0% very fluent way it is high 00:11:12.940 --> 00:11:14.579 align:start position:0% very fluent way it is high configurability<00:11:13.630> which<00:11:13.990> means<00:11:14.230> there's<00:11:14.500> a 00:11:14.579 --> 00:11:14.589 align:start position:0% configurability which means there's a 00:11:14.589 --> 00:11:16.680 align:start position:0% configurability which means there's a high<00:11:14.829> you<00:11:15.370> know<00:11:15.490> set<00:11:15.820> up<00:11:15.850> overhead<00:11:16.209> when<00:11:16.570> you 00:11:16.680 --> 00:11:16.690 align:start position:0% high you know set up overhead when you 00:11:16.690 --> 00:11:18.540 align:start position:0% high you know set up overhead when you when<00:11:16.870> you<00:11:16.930> initially<00:11:17.320> start<00:11:17.560> using<00:11:17.769> it<00:11:18.010> but 00:11:18.540 --> 00:11:18.550 align:start position:0% when you initially start using it but 00:11:18.550 --> 00:11:20.660 align:start position:0% when you initially start using it but basically<00:11:18.700> once<00:11:19.240> once<00:11:19.779> you<00:11:19.930> get<00:11:20.470> your 00:11:20.660 --> 00:11:20.670 align:start position:0% basically once once you get your 00:11:20.670 --> 00:11:22.530 align:start position:0% basically once once you get your deployment<00:11:21.670> environment<00:11:22.180> the<00:11:22.240> way<00:11:22.329> that<00:11:22.480> you 00:11:22.530 --> 00:11:22.540 align:start position:0% deployment environment the way that you 00:11:22.540 --> 00:11:23.970 align:start position:0% deployment environment the way that you want<00:11:22.779> it<00:11:22.899> with<00:11:23.079> the<00:11:23.199> loaders<00:11:23.500> that<00:11:23.680> you<00:11:23.769> want 00:11:23.970 --> 00:11:23.980 align:start position:0% want it with the loaders that you want 00:11:23.980 --> 00:11:26.009 align:start position:0% want it with the loaders that you want so<00:11:24.279> soul<00:11:24.519> sea<00:11:24.760> and<00:11:25.029> some<00:11:25.329> environment<00:11:25.779> loading 00:11:26.009 --> 00:11:26.019 align:start position:0% so soul sea and some environment loading 00:11:26.019 --> 00:11:28.439 align:start position:0% so soul sea and some environment loading and<00:11:26.139> stuff<00:11:26.339> then<00:11:27.339> you<00:11:27.880> don't<00:11:28.089> have<00:11:28.209> to<00:11:28.300> do 00:11:28.439 --> 00:11:28.449 align:start position:0% and stuff then you don't have to do 00:11:28.449 --> 00:11:30.000 align:start position:0% and stuff then you don't have to do anything<00:11:28.690> you<00:11:28.930> can<00:11:28.990> just<00:11:29.260> reuse<00:11:29.470> your<00:11:29.769> same 00:11:30.000 --> 00:11:30.010 align:start position:0% anything you can just reuse your same 00:11:30.010 --> 00:11:34.439 align:start position:0% anything you can just reuse your same modules<00:11:30.430> over<00:11:30.670> and<00:11:31.269> over<00:11:31.389> again<00:11:31.480> so<00:11:33.209> this<00:11:34.209> is 00:11:34.439 --> 00:11:34.449 align:start position:0% modules over and over again so this is 00:11:34.449 --> 00:11:36.240 align:start position:0% modules over and over again so this is one<00:11:35.139> thing<00:11:35.320> that's<00:11:35.529> going<00:11:35.620> to<00:11:35.680> be<00:11:35.740> moved<00:11:36.070> into 00:11:36.240 --> 00:11:36.250 align:start position:0% one thing that's going to be moved into 00:11:36.250 --> 00:11:39.300 align:start position:0% one thing that's going to be moved into ejs<00:11:36.790> right<00:11:37.720> now<00:11:37.870> it<00:11:38.019> only<00:11:38.110> has<00:11:38.380> about<00:11:38.980> 30 00:11:39.300 --> 00:11:39.310 align:start position:0% ejs right now it only has about 30 00:11:39.310 --> 00:11:41.310 align:start position:0% ejs right now it only has about 30 percent<00:11:39.550> test<00:11:39.910> coverage<00:11:40.209> so<00:11:40.510> I<00:11:40.540> need<00:11:41.110> to<00:11:41.199> get 00:11:41.310 --> 00:11:41.320 align:start position:0% percent test coverage so I need to get 00:11:41.320 --> 00:11:43.860 align:start position:0% percent test coverage so I need to get that<00:11:41.440> around<00:11:41.769> 104<00:11:42.670> I'm<00:11:42.760> moving<00:11:43.000> into<00:11:43.209> its<00:11:43.449> HS 00:11:43.860 --> 00:11:43.870 align:start position:0% that around 104 I'm moving into its HS 00:11:43.870 --> 00:11:45.810 align:start position:0% that around 104 I'm moving into its HS so<00:11:44.350> but<00:11:44.709> that's<00:11:44.829> called<00:11:45.100> eath<00:11:45.250> deploy<00:11:45.579> and 00:11:45.810 --> 00:11:45.820 align:start position:0% so but that's called eath deploy and 00:11:45.820 --> 00:11:48.720 align:start position:0% so but that's called eath deploy and that's<00:11:45.940> available<00:11:46.410> on<00:11:47.410> my<00:11:47.620> github<00:11:47.680> so<00:11:48.279> silence 00:11:48.720 --> 00:11:48.730 align:start position:0% that's available on my github so silence 00:11:48.730 --> 00:11:54.019 align:start position:0% that's available on my github so silence is<00:11:48.850> Rho<00:11:49.500> /e<00:11:50.500> deploy<00:11:51.810> so<00:11:52.810> a<00:11:53.320> bit<00:11:53.620> of<00:11:53.709> the<00:11:53.800> roadmap 00:11:54.019 --> 00:11:54.029 align:start position:0% is Rho /e deploy so a bit of the roadmap 00:11:54.029 --> 00:11:58.019 align:start position:0% is Rho /e deploy so a bit of the roadmap so<00:11:55.029> I'm<00:11:55.720> gonna<00:11:55.899> move<00:11:56.139> the<00:11:56.440> ABI<00:11:56.800> work<00:11:57.160> from<00:11:57.910> each 00:11:58.019 --> 00:11:58.029 align:start position:0% so I'm gonna move the ABI work from each 00:11:58.029 --> 00:12:00.680 align:start position:0% so I'm gonna move the ABI work from each s<00:11:58.269> just<00:11:58.600> over<00:11:58.810> to<00:11:58.930> ethers<00:11:59.230> J<00:11:59.410> s<00:11:59.560> because 00:12:00.680 --> 00:12:00.690 align:start position:0% s just over to ethers J s because 00:12:00.690 --> 00:12:03.480 align:start position:0% s just over to ethers J s because Richard<00:12:01.690> Moore<00:12:01.899> is<00:12:02.199> literally<00:12:02.620> the<00:12:03.279> God 00:12:03.480 --> 00:12:03.490 align:start position:0% Richard Moore is literally the God 00:12:03.490 --> 00:12:07.139 align:start position:0% Richard Moore is literally the God you've<00:12:03.850> never<00:12:04.240> met<00:12:04.480> yet<00:12:04.690> and<00:12:04.870> it's<00:12:05.529> amazing<00:12:06.149> so 00:12:07.139 --> 00:12:07.149 align:start position:0% you've never met yet and it's amazing so 00:12:07.149 --> 00:12:09.259 align:start position:0% you've never met yet and it's amazing so he's<00:12:07.540> in<00:12:07.720> the<00:12:07.810> room<00:12:07.990> he's<00:12:08.290> in<00:12:08.320> the<00:12:08.500> room 00:12:09.259 --> 00:12:09.269 align:start position:0% he's in the room he's in the room 00:12:09.269 --> 00:12:13.920 align:start position:0% he's in the room he's in the room personal<00:12:10.269> hero<00:12:10.800> so<00:12:11.880> as<00:12:12.880> well<00:12:13.089> the<00:12:13.480> removal<00:12:13.839> of 00:12:13.920 --> 00:12:13.930 align:start position:0% personal hero so as well the removal of 00:12:13.930 --> 00:12:16.410 align:start position:0% personal hero so as well the removal of buffer<00:12:14.260> across<00:12:14.620> the<00:12:14.800> modules<00:12:15.209> which<00:12:16.209> should 00:12:16.410 --> 00:12:16.420 align:start position:0% buffer across the modules which should 00:12:16.420 --> 00:12:19.410 align:start position:0% buffer across the modules which should reduce<00:12:16.570> the<00:12:17.230> non<00:12:18.100> account<00:12:18.519> handling<00:12:19.000> module 00:12:19.410 --> 00:12:19.420 align:start position:0% reduce the non account handling module 00:12:19.420 --> 00:12:22.800 align:start position:0% reduce the non account handling module to<00:12:19.570> around<00:12:19.720> 50<00:12:20.019> kilobytes<00:12:20.579> and<00:12:21.579> as<00:12:22.570> well 00:12:22.800 --> 00:12:22.810 align:start position:0% to around 50 kilobytes and as well 00:12:22.810 --> 00:12:25.019 align:start position:0% to around 50 kilobytes and as well better<00:12:23.140> account<00:12:23.649> handling<00:12:24.100> and<00:12:24.310> filtering<00:12:24.730> so 00:12:25.019 --> 00:12:25.029 align:start position:0% better account handling and filtering so 00:12:25.029 --> 00:12:27.389 align:start position:0% better account handling and filtering so right<00:12:25.180> now<00:12:25.300> I've<00:12:25.420> pretty<00:12:25.690> good<00:12:26.250> filtering<00:12:27.250> and 00:12:27.389 --> 00:12:27.399 align:start position:0% right now I've pretty good filtering and 00:12:27.399 --> 00:12:28.949 align:start position:0% right now I've pretty good filtering and event<00:12:27.579> handling<00:12:27.640> but<00:12:28.480> I<00:12:28.540> think<00:12:28.720> I'd<00:12:28.779> like<00:12:28.899> to 00:12:28.949 --> 00:12:28.959 align:start position:0% event handling but I think I'd like to 00:12:28.959 --> 00:12:30.900 align:start position:0% event handling but I think I'd like to get<00:12:29.140> that<00:12:29.290> better<00:12:29.529> some<00:12:30.250> people<00:12:30.490> complained 00:12:30.900 --> 00:12:30.910 align:start position:0% get that better some people complained 00:12:30.910 --> 00:12:33.780 align:start position:0% get that better some people complained about<00:12:31.470> certain<00:12:32.470> certain<00:12:32.860> aspects<00:12:33.190> of<00:12:33.310> that<00:12:33.459> so 00:12:33.780 --> 00:12:33.790 align:start position:0% about certain certain aspects of that so 00:12:33.790 --> 00:12:36.750 align:start position:0% about certain certain aspects of that so that'll<00:12:34.420> get<00:12:34.600> improved<00:12:34.930> I<00:12:35.829> really<00:12:36.519> want<00:12:36.670> to 00:12:36.750 --> 00:12:36.760 align:start position:0% that'll get improved I really want to 00:12:36.760 --> 00:12:39.030 align:start position:0% that'll get improved I really want to integrate<00:12:37.149> some<00:12:37.779> new<00:12:37.930> bounties<00:12:38.320> networks 00:12:39.030 --> 00:12:39.040 align:start position:0% integrate some new bounties networks 00:12:39.040 --> 00:12:40.740 align:start position:0% integrate some new bounties networks that<00:12:39.250> are<00:12:39.339> coming<00:12:39.579> about<00:12:39.670> so<00:12:40.149> bounties<00:12:40.540> dot 00:12:40.740 --> 00:12:40.750 align:start position:0% that are coming about so bounties dot 00:12:40.750 --> 00:12:42.000 align:start position:0% that are coming about so bounties dot network<00:12:41.079> it's<00:12:41.320> very<00:12:41.529> cool 00:12:42.000 --> 00:12:42.010 align:start position:0% network it's very cool 00:12:42.010 --> 00:12:45.240 align:start position:0% network it's very cool and<00:12:42.100> get<00:12:42.490> coin<00:12:42.730> and<00:12:43.740> and<00:12:44.740> that's<00:12:44.890> just<00:12:44.949> for 00:12:45.240 --> 00:12:45.250 align:start position:0% and get coin and and that's just for 00:12:45.250 --> 00:12:47.509 align:start position:0% and get coin and and that's just for keeping<00:12:45.670> the<00:12:45.910> libraries<00:12:46.300> updated<00:12:46.810> and<00:12:47.050> and 00:12:47.509 --> 00:12:47.519 align:start position:0% keeping the libraries updated and and 00:12:47.519 --> 00:12:51.990 align:start position:0% keeping the libraries updated and and keeping<00:12:48.519> bugs<00:12:48.870> you<00:12:49.870> know<00:12:49.899> way<00:12:50.910> removing<00:12:51.910> a 00:12:51.990 --> 00:12:52.000 align:start position:0% keeping bugs you know way removing a 00:12:52.000 --> 00:12:54.449 align:start position:0% keeping bugs you know way removing a morphic<00:12:52.390> number<00:12:52.630> handling<00:12:53.019> so<00:12:53.459> basically 00:12:54.449 --> 00:12:54.459 align:start position:0% morphic number handling so basically 00:12:54.459 --> 00:12:56.430 align:start position:0% morphic number handling so basically right<00:12:54.699> now<00:12:54.760> we<00:12:54.940> support<00:12:55.569> multiple<00:12:55.810> kinds<00:12:56.350> of 00:12:56.430 --> 00:12:56.440 align:start position:0% right now we support multiple kinds of 00:12:56.440 --> 00:12:58.860 align:start position:0% right now we support multiple kinds of types<00:12:56.649> going<00:12:57.010> into<00:12:57.220> number<00:12:57.459> handling<00:12:57.850> I<00:12:58.029> think 00:12:58.860 --> 00:12:58.870 align:start position:0% types going into number handling I think 00:12:58.870 --> 00:13:01.350 align:start position:0% types going into number handling I think I'm<00:12:59.290> just<00:12:59.470> gonna<00:12:59.620> support<00:13:00.040> probably<00:13:00.790> just<00:13:01.209> big 00:13:01.350 --> 00:13:01.360 align:start position:0% I'm just gonna support probably just big 00:13:01.360 --> 00:13:03.030 align:start position:0% I'm just gonna support probably just big numbers<00:13:01.720> and<00:13:02.410> while<00:13:02.560> that's<00:13:02.709> a<00:13:02.829> little 00:13:03.030 --> 00:13:03.040 align:start position:0% numbers and while that's a little 00:13:03.040 --> 00:13:05.100 align:start position:0% numbers and while that's a little bulkier<00:13:03.459> and<00:13:03.699> definitely<00:13:04.180> not<00:13:04.630> everyone's 00:13:05.100 --> 00:13:05.110 align:start position:0% bulkier and definitely not everyone's 00:13:05.110 --> 00:13:07.710 align:start position:0% bulkier and definitely not everyone's favorite<00:13:05.610> sometimes<00:13:06.610> I<00:13:06.699> prefer<00:13:07.149> that<00:13:07.480> just 00:13:07.710 --> 00:13:07.720 align:start position:0% favorite sometimes I prefer that just 00:13:07.720 --> 00:13:10.920 align:start position:0% favorite sometimes I prefer that just because<00:13:07.899> it<00:13:08.019> keeps<00:13:08.139> type<00:13:08.410> strong<00:13:09.420> and<00:13:10.420> then<00:13:10.779> as 00:13:10.920 --> 00:13:10.930 align:start position:0% because it keeps type strong and then as 00:13:10.930 --> 00:13:13.980 align:start position:0% because it keeps type strong and then as well<00:13:11.110> more<00:13:11.860> detailed<00:13:12.339> error<00:13:12.699> handling<00:13:12.990> so 00:13:13.980 --> 00:13:13.990 align:start position:0% well more detailed error handling so 00:13:13.990 --> 00:13:16.590 align:start position:0% well more detailed error handling so just<00:13:14.380> I'd<00:13:15.339> like<00:13:15.550> the<00:13:15.699> errors<00:13:16.000> right 00:13:16.590 --> 00:13:16.600 align:start position:0% just I'd like the errors right 00:13:16.600 --> 00:13:18.090 align:start position:0% just I'd like the errors right now<00:13:16.690> they<00:13:16.870> are<00:13:17.019> pretty<00:13:17.319> detailed<00:13:17.529> but<00:13:17.980> I'd 00:13:18.090 --> 00:13:18.100 align:start position:0% now they are pretty detailed but I'd 00:13:18.100 --> 00:13:20.160 align:start position:0% now they are pretty detailed but I'd like<00:13:18.220> them<00:13:18.399> to<00:13:18.430> also<00:13:18.730> be<00:13:18.880> user-friendly<00:13:19.180> for 00:13:20.160 --> 00:13:20.170 align:start position:0% like them to also be user-friendly for 00:13:20.170 --> 00:13:22.410 align:start position:0% like them to also be user-friendly for new<00:13:20.290> users<00:13:20.649> I<00:13:21.430> think<00:13:21.850> that's<00:13:22.000> that's<00:13:22.240> pretty 00:13:22.410 --> 00:13:22.420 align:start position:0% new users I think that's that's pretty 00:13:22.420 --> 00:13:23.759 align:start position:0% new users I think that's that's pretty critical<00:13:22.660> to<00:13:23.079> new<00:13:23.199> people<00:13:23.319> entering<00:13:23.680> the 00:13:23.759 --> 00:13:23.769 align:start position:0% critical to new people entering the 00:13:23.769 --> 00:13:26.400 align:start position:0% critical to new people entering the space<00:13:24.149> and<00:13:25.149> then<00:13:25.300> give<00:13:25.540> book<00:13:25.690> documentation 00:13:26.400 --> 00:13:26.410 align:start position:0% space and then give book documentation 00:13:26.410 --> 00:13:28.590 align:start position:0% space and then give book documentation right<00:13:26.800> now<00:13:26.949> the<00:13:27.009> documentation<00:13:27.850> is<00:13:28.000> in<00:13:28.149> a<00:13:28.240> in<00:13:28.509> a 00:13:28.590 --> 00:13:28.600 align:start position:0% right now the documentation is in a in a 00:13:28.600 --> 00:13:30.300 align:start position:0% right now the documentation is in a in a repo<00:13:28.930> through<00:13:29.259> read<00:13:29.410> Me's<00:13:29.589> so<00:13:30.009> I'd<00:13:30.130> like<00:13:30.250> to 00:13:30.300 --> 00:13:30.310 align:start position:0% repo through read Me's so I'd like to 00:13:30.310 --> 00:13:35.449 align:start position:0% repo through read Me's so I'd like to move<00:13:30.430> that<00:13:30.610> skip<00:13:30.819> book<00:13:31.620> and<00:13:32.730> just<00:13:33.730> as<00:13:34.389> well<00:13:34.690> so 00:13:35.449 --> 00:13:35.459 align:start position:0% move that skip book and just as well so 00:13:35.459 --> 00:13:38.999 align:start position:0% move that skip book and just as well so because<00:13:36.459> I<00:13:36.550> have<00:13:36.730> just<00:13:37.060> a<00:13:37.180> few<00:13:37.360> minutes<00:13:38.009> yeah 00:13:38.999 --> 00:13:39.009 align:start position:0% because I have just a few minutes yeah 00:13:39.009 --> 00:13:41.189 align:start position:0% because I have just a few minutes yeah so<00:13:39.310> there's<00:13:39.850> definitely<00:13:40.300> been<00:13:40.839> a<00:13:40.870> lot<00:13:41.170> of 00:13:41.189 --> 00:13:41.199 align:start position:0% so there's definitely been a lot of 00:13:41.199 --> 00:13:43.350 align:start position:0% so there's definitely been a lot of discussion<00:13:41.740> before<00:13:42.430> I<00:13:42.459> just<00:13:42.670> thank<00:13:43.089> all<00:13:43.240> the 00:13:43.350 --> 00:13:43.360 align:start position:0% discussion before I just thank all the 00:13:43.360 --> 00:13:45.329 align:start position:0% discussion before I just thank all the people<00:13:43.480> that<00:13:43.769> heavily<00:13:44.769> influenced<00:13:45.250> my 00:13:45.329 --> 00:13:45.339 align:start position:0% people that heavily influenced my 00:13:45.339 --> 00:13:48.030 align:start position:0% people that heavily influenced my thinking<00:13:46.410> there's<00:13:47.410> definitely<00:13:47.769> a<00:13:47.829> lot<00:13:47.980> of 00:13:48.030 --> 00:13:48.040 align:start position:0% thinking there's definitely a lot of 00:13:48.040 --> 00:13:51.629 align:start position:0% thinking there's definitely a lot of discussion<00:13:48.579> around<00:13:48.699> like<00:13:49.630> alternatives<00:13:50.639> to 00:13:51.629 --> 00:13:51.639 align:start position:0% discussion around like alternatives to 00:13:51.639 --> 00:13:53.519 align:start position:0% discussion around like alternatives to web<00:13:51.790> 3<00:13:52.029> I<00:13:52.060> think<00:13:52.329> web<00:13:52.630> 3<00:13:52.899> has<00:13:52.990> been<00:13:53.170> quite<00:13:53.500> a 00:13:53.519 --> 00:13:53.529 align:start position:0% web 3 I think web 3 has been quite a 00:13:53.529 --> 00:13:54.480 align:start position:0% web 3 I think web 3 has been quite a journey 00:13:54.480 --> 00:13:54.490 align:start position:0% journey 00:13:54.490 --> 00:13:57.689 align:start position:0% journey i-i've<00:13:55.269> been<00:13:55.300> using<00:13:56.190> aetherium<00:13:57.190> since<00:13:57.490> proof 00:13:57.689 --> 00:13:57.699 align:start position:0% i-i've been using aetherium since proof 00:13:57.699 --> 00:14:00.449 align:start position:0% i-i've been using aetherium since proof of<00:13:57.819> concept<00:13:58.240> 5<00:13:58.480> so<00:13:59.019> I've<00:13:59.139> kind<00:13:59.350> of<00:13:59.470> sludged 00:14:00.449 --> 00:14:00.459 align:start position:0% of concept 5 so I've kind of sludged 00:14:00.459 --> 00:14:03.180 align:start position:0% of concept 5 so I've kind of sludged through<00:14:00.940> the<00:14:01.149> journey<00:14:01.389> at<00:14:01.839> every<00:14:02.259> stage<00:14:02.529> when 00:14:03.180 --> 00:14:03.190 align:start position:0% through the journey at every stage when 00:14:03.190 --> 00:14:05.699 align:start position:0% through the journey at every stage when etherium<00:14:03.910> barely<00:14:04.899> worked<00:14:05.110> and<00:14:05.350> there<00:14:05.440> was<00:14:05.560> no 00:14:05.699 --> 00:14:05.709 align:start position:0% etherium barely worked and there was no 00:14:05.709 --> 00:14:08.850 align:start position:0% etherium barely worked and there was no tools<00:14:05.949> -<00:14:06.519> now<00:14:07.000> it's<00:14:07.470> fantastically<00:14:08.470> working 00:14:08.850 --> 00:14:08.860 align:start position:0% tools - now it's fantastically working 00:14:08.860 --> 00:14:11.370 align:start position:0% tools - now it's fantastically working and<00:14:09.069> there's<00:14:09.370> so<00:14:10.029> many<00:14:10.120> tools<00:14:10.480> but<00:14:10.930> still<00:14:11.350> a 00:14:11.370 --> 00:14:11.380 align:start position:0% and there's so many tools but still a 00:14:11.380 --> 00:14:16.050 align:start position:0% and there's so many tools but still a lot<00:14:11.620> of<00:14:11.800> you<00:14:12.130> know<00:14:12.250> room<00:14:12.699> to<00:14:12.819> grow<00:14:13.350> I<00:14:14.350> think<00:14:15.060> you 00:14:16.050 --> 00:14:16.060 align:start position:0% lot of you know room to grow I think you 00:14:16.060 --> 00:14:17.999 align:start position:0% lot of you know room to grow I think you know<00:14:16.149> the<00:14:16.839> architecture<00:14:17.589> is<00:14:17.709> growing 00:14:17.999 --> 00:14:18.009 align:start position:0% know the architecture is growing 00:14:18.009 --> 00:14:20.879 align:start position:0% know the architecture is growing significantly<00:14:18.220> and<00:14:18.940> we<00:14:19.300> have<00:14:19.540> a<00:14:20.440> lot<00:14:20.800> of 00:14:20.879 --> 00:14:20.889 align:start position:0% significantly and we have a lot of 00:14:20.889 --> 00:14:25.790 align:start position:0% significantly and we have a lot of really<00:14:21.069> cool<00:14:21.279> stuff<00:14:21.509> coming<00:14:22.509> up<00:14:23.130> and<00:14:24.130> I<00:14:24.790> think 00:14:25.790 --> 00:14:25.800 align:start position:0% really cool stuff coming up and I think 00:14:25.800 --> 00:14:28.470 align:start position:0% really cool stuff coming up and I think the<00:14:26.800> thing<00:14:27.220> with<00:14:27.370> alternatives<00:14:28.000> and 00:14:28.470 --> 00:14:28.480 align:start position:0% the thing with alternatives and 00:14:28.480 --> 00:14:30.689 align:start position:0% the thing with alternatives and especially<00:14:28.810> having<00:14:29.139> kind<00:14:29.680> of<00:14:29.769> a<00:14:29.889> diverse<00:14:30.519> set 00:14:30.689 --> 00:14:30.699 align:start position:0% especially having kind of a diverse set 00:14:30.699 --> 00:14:34.079 align:start position:0% especially having kind of a diverse set of<00:14:30.759> tools<00:14:31.139> at<00:14:32.139> this<00:14:32.410> layer<00:14:32.649> is<00:14:32.949> just<00:14:33.430> you<00:14:33.970> know 00:14:34.079 --> 00:14:34.089 align:start position:0% of tools at this layer is just you know 00:14:34.089 --> 00:14:36.090 align:start position:0% of tools at this layer is just you know this<00:14:34.240> is<00:14:34.420> like<00:14:34.449> the<00:14:34.600> front<00:14:34.959> door<00:14:35.259> to<00:14:35.620> aetherium 00:14:36.090 --> 00:14:36.100 align:start position:0% this is like the front door to aetherium 00:14:36.100 --> 00:14:39.030 align:start position:0% this is like the front door to aetherium and<00:14:36.509> it's<00:14:37.509> very<00:14:37.870> critical<00:14:38.410> that<00:14:38.620> everything 00:14:39.030 --> 00:14:39.040 align:start position:0% and it's very critical that everything 00:14:39.040 --> 00:14:40.980 align:start position:0% and it's very critical that everything works<00:14:39.220> properly<00:14:39.430> that<00:14:40.209> errors<00:14:40.630> are<00:14:40.779> thrown 00:14:40.980 --> 00:14:40.990 align:start position:0% works properly that errors are thrown 00:14:40.990 --> 00:14:42.749 align:start position:0% works properly that errors are thrown where<00:14:41.170> they<00:14:41.259> should<00:14:41.500> be<00:14:41.649> the<00:14:42.069> throat<00:14:42.550> loudly 00:14:42.749 --> 00:14:42.759 align:start position:0% where they should be the throat loudly 00:14:42.759 --> 00:14:45.329 align:start position:0% where they should be the throat loudly that<00:14:43.630> you<00:14:44.110> know<00:14:44.199> early<00:14:44.560> users<00:14:44.920> to<00:14:45.189> our 00:14:45.329 --> 00:14:45.339 align:start position:0% that you know early users to our 00:14:45.339 --> 00:14:47.639 align:start position:0% that you know early users to our technology<00:14:45.959> can<00:14:46.959> kind<00:14:47.170> of<00:14:47.199> get<00:14:47.350> a<00:14:47.380> great 00:14:47.639 --> 00:14:47.649 align:start position:0% technology can kind of get a great 00:14:47.649 --> 00:14:49.319 align:start position:0% technology can kind of get a great experience<00:14:47.800> out<00:14:48.399> of<00:14:48.550> it<00:14:48.670> because<00:14:48.880> right<00:14:49.180> now 00:14:49.319 --> 00:14:49.329 align:start position:0% experience out of it because right now 00:14:49.329 --> 00:14:51.780 align:start position:0% experience out of it because right now it's<00:14:49.930> not<00:14:50.019> a<00:14:50.139> great<00:14:50.350> experience<00:14:50.470> and<00:14:51.250> right 00:14:51.780 --> 00:14:51.790 align:start position:0% it's not a great experience and right 00:14:51.790 --> 00:14:55.110 align:start position:0% it's not a great experience and right now<00:14:51.970> we<00:14:52.720> have<00:14:52.899> a<00:14:52.930> lot<00:14:53.170> of<00:14:53.610> you<00:14:54.610> know<00:14:54.639> junior 00:14:55.110 --> 00:14:55.120 align:start position:0% now we have a lot of you know junior 00:14:55.120 --> 00:14:56.970 align:start position:0% now we have a lot of you know junior devs<00:14:55.300> and<00:14:55.600> stuff<00:14:55.779> who<00:14:56.470> are<00:14:56.589> definitely 00:14:56.970 --> 00:14:56.980 align:start position:0% devs and stuff who are definitely 00:14:56.980 --> 00:14:58.920 align:start position:0% devs and stuff who are definitely melting<00:14:57.370> when<00:14:57.759> they<00:14:57.850> start<00:14:58.120> using<00:14:58.329> aetherium 00:14:58.920 --> 00:14:58.930 align:start position:0% melting when they start using aetherium 00:14:58.930 --> 00:15:00.480 align:start position:0% melting when they start using aetherium when<00:14:59.829> they<00:14:59.980> shouldn't<00:15:00.250> be 00:15:00.480 --> 00:15:00.490 align:start position:0% when they shouldn't be 00:15:00.490 --> 00:15:03.689 align:start position:0% when they shouldn't be it<00:15:00.790> should<00:15:01.060> be<00:15:01.180> a<00:15:01.209> very<00:15:01.389> simple<00:15:01.720> process<00:15:02.189> and<00:15:03.189> I 00:15:03.689 --> 00:15:03.699 align:start position:0% it should be a very simple process and I 00:15:03.699 --> 00:15:05.879 align:start position:0% it should be a very simple process and I think<00:15:03.730> that<00:15:04.300> we<00:15:05.079> kind<00:15:05.199> of<00:15:05.319> need<00:15:05.470> to<00:15:05.500> get<00:15:05.649> more 00:15:05.879 --> 00:15:05.889 align:start position:0% think that we kind of need to get more 00:15:05.889 --> 00:15:08.220 align:start position:0% think that we kind of need to get more realistic<00:15:06.519> with<00:15:06.790> our<00:15:06.970> expectations<00:15:07.630> and<00:15:07.930> what 00:15:08.220 --> 00:15:08.230 align:start position:0% realistic with our expectations and what 00:15:08.230 --> 00:15:10.079 align:start position:0% realistic with our expectations and what we<00:15:08.350> want<00:15:08.500> to<00:15:08.589> achieve<00:15:08.680> especially<00:15:09.550> when<00:15:10.000> it 00:15:10.079 --> 00:15:10.089 align:start position:0% we want to achieve especially when it 00:15:10.089 --> 00:15:12.870 align:start position:0% we want to achieve especially when it comes<00:15:10.209> to<00:15:10.449> just<00:15:10.660> like<00:15:11.019> an<00:15:11.290> effing<00:15:11.829> RPC<00:15:12.699> layer 00:15:12.870 --> 00:15:12.880 align:start position:0% comes to just like an effing RPC layer 00:15:12.880 --> 00:15:15.240 align:start position:0% comes to just like an effing RPC layer that<00:15:13.269> has<00:15:13.449> some<00:15:13.689> data<00:15:13.839> formatting<00:15:14.439> and<00:15:14.949> some 00:15:15.240 --> 00:15:15.250 align:start position:0% that has some data formatting and some 00:15:15.250 --> 00:15:17.100 align:start position:0% that has some data formatting and some contract<00:15:15.670> handling<00:15:16.060> like<00:15:16.660> it<00:15:16.750> drives<00:15:16.959> me 00:15:17.100 --> 00:15:17.110 align:start position:0% contract handling like it drives me 00:15:17.110 --> 00:15:21.660 align:start position:0% contract handling like it drives me crazy<00:15:17.139> I'm<00:15:17.560> like<00:15:18.569> so<00:15:19.569> you<00:15:20.529> know<00:15:20.649> I<00:15:20.680> think<00:15:20.889> if 00:15:21.660 --> 00:15:21.670 align:start position:0% crazy I'm like so you know I think if 00:15:21.670 --> 00:15:25.110 align:start position:0% crazy I'm like so you know I think if you<00:15:21.939> see<00:15:22.380> potential<00:15:23.380> to<00:15:23.620> fix<00:15:23.889> modules<00:15:24.430> or<00:15:24.760> to 00:15:25.110 --> 00:15:25.120 align:start position:0% you see potential to fix modules or to 00:15:25.120 --> 00:15:26.850 align:start position:0% you see potential to fix modules or to make<00:15:25.240> them<00:15:25.420> better<00:15:25.569> or<00:15:25.720> even<00:15:26.170> to<00:15:26.439> do<00:15:26.529> your<00:15:26.709> own 00:15:26.850 --> 00:15:26.860 align:start position:0% make them better or even to do your own 00:15:26.860 --> 00:15:28.799 align:start position:0% make them better or even to do your own you<00:15:27.430> should<00:15:27.459> definitely<00:15:28.000> do<00:15:28.120> that 00:15:28.799 --> 00:15:28.809 align:start position:0% you should definitely do that 00:15:28.809 --> 00:15:30.720 align:start position:0% you should definitely do that you<00:15:28.990> should<00:15:29.170> definitely<00:15:29.260> expand<00:15:29.829> the<00:15:29.920> eCos 00:15:30.720 --> 00:15:30.730 align:start position:0% you should definitely expand the eCos 00:15:30.730 --> 00:15:32.610 align:start position:0% you should definitely expand the eCos and<00:15:30.819> and<00:15:31.480> try<00:15:31.629> to<00:15:31.689> help<00:15:31.870> out<00:15:32.050> where<00:15:32.199> you<00:15:32.290> can<00:15:32.470> on 00:15:32.610 --> 00:15:32.620 align:start position:0% and and try to help out where you can on 00:15:32.620 --> 00:15:35.489 align:start position:0% and and try to help out where you can on existing<00:15:33.069> modules<00:15:33.600> and<00:15:34.600> you<00:15:35.050> know<00:15:35.139> once<00:15:35.350> again 00:15:35.489 --> 00:15:35.499 align:start position:0% existing modules and you know once again 00:15:35.499 --> 00:15:37.619 align:start position:0% existing modules and you know once again like<00:15:35.980> my<00:15:36.129> personal<00:15:36.819> favorites<00:15:37.240> definitely 00:15:37.619 --> 00:15:37.629 align:start position:0% like my personal favorites definitely 00:15:37.629 --> 00:15:41.009 align:start position:0% like my personal favorites definitely lieth<00:15:37.959> with<00:15:37.990> ethers<00:15:38.529> je<00:15:38.740> s<00:15:38.860> and<00:15:39.249> and<00:15:40.019> the 00:15:41.009 --> 00:15:41.019 align:start position:0% lieth with ethers je s and and the 00:15:41.019 --> 00:15:43.259 align:start position:0% lieth with ethers je s and and the modules<00:15:41.350> that<00:15:41.470> I've<00:15:41.559> been<00:15:41.620> using<00:15:42.120> and<00:15:43.120> I 00:15:43.259 --> 00:15:43.269 align:start position:0% modules that I've been using and I 00:15:43.269 --> 00:15:45.720 align:start position:0% modules that I've been using and I actively<00:15:43.660> developed<00:15:44.259> apps<00:15:44.470> so<00:15:44.889> I'm<00:15:45.279> currently 00:15:45.720 --> 00:15:45.730 align:start position:0% actively developed apps so I'm currently 00:15:45.730 --> 00:15:48.509 align:start position:0% actively developed apps so I'm currently developing<00:15:46.569> board<00:15:47.529> room<00:15:47.740> which<00:15:47.980> has<00:15:48.160> been<00:15:48.399> in 00:15:48.509 --> 00:15:48.519 align:start position:0% developing board room which has been in 00:15:48.519 --> 00:15:49.920 align:start position:0% developing board room which has been in stealth<00:15:48.819> mode<00:15:48.999> for<00:15:49.209> like<00:15:49.329> two<00:15:49.629> and<00:15:49.749> a<00:15:49.809> half 00:15:49.920 --> 00:15:49.930 align:start position:0% stealth mode for like two and a half 00:15:49.930 --> 00:15:54.600 align:start position:0% stealth mode for like two and a half years<00:15:50.170> a<00:15:50.350> super<00:15:50.740> old<00:15:51.339> project<00:15:52.110> and<00:15:53.110> so<00:15:53.860> I'm 00:15:54.600 --> 00:15:54.610 align:start position:0% years a super old project and so I'm 00:15:54.610 --> 00:15:57.030 align:start position:0% years a super old project and so I'm constantly<00:15:55.269> using<00:15:55.360> this<00:15:55.749> tech<00:15:56.019> that<00:15:56.410> that 00:15:57.030 --> 00:15:57.040 align:start position:0% constantly using this tech that that 00:15:57.040 --> 00:15:59.220 align:start position:0% constantly using this tech that that I've<00:15:57.129> been<00:15:57.249> implementing<00:15:57.730> and<00:15:58.569> that's<00:15:58.990> kind 00:15:59.220 --> 00:15:59.230 align:start position:0% I've been implementing and that's kind 00:15:59.230 --> 00:16:00.239 align:start position:0% I've been implementing and that's kind of<00:15:59.290> giving<00:15:59.499> me<00:15:59.620> a<00:15:59.649> completely<00:16:00.160> different 00:16:00.239 --> 00:16:00.249 align:start position:0% of giving me a completely different 00:16:00.249 --> 00:16:02.879 align:start position:0% of giving me a completely different perspective<00:16:00.519> on<00:16:00.850> architecture<00:16:01.589> but<00:16:02.589> as<00:16:02.709> well 00:16:02.879 --> 00:16:02.889 align:start position:0% perspective on architecture but as well 00:16:02.889 --> 00:16:04.410 align:start position:0% perspective on architecture but as well I<00:16:02.920> just<00:16:03.309> like<00:16:03.730> to<00:16:03.879> be<00:16:03.999> a<00:16:04.029> little<00:16:04.300> more 00:16:04.410 --> 00:16:04.420 align:start position:0% I just like to be a little more 00:16:04.420 --> 00:16:07.530 align:start position:0% I just like to be a little more old-school<00:16:04.839> with<00:16:05.139> my<00:16:05.290> thinking<00:16:05.649> so<00:16:06.449> you<00:16:07.449> know 00:16:07.530 --> 00:16:07.540 align:start position:0% old-school with my thinking so you know 00:16:07.540 --> 00:16:08.939 align:start position:0% old-school with my thinking so you know the<00:16:07.809> UNIX<00:16:08.019> philosophy<00:16:08.110> and<00:16:08.559> all<00:16:08.620> that<00:16:08.709> sort<00:16:08.889> of 00:16:08.939 --> 00:16:08.949 align:start position:0% the UNIX philosophy and all that sort of 00:16:08.949 --> 00:16:11.639 align:start position:0% the UNIX philosophy and all that sort of stuff<00:16:09.009> in<00:16:09.249> mind<00:16:09.490> has<00:16:10.449> kind<00:16:10.720> of<00:16:10.749> led<00:16:10.899> me<00:16:10.959> to<00:16:11.259> this 00:16:11.639 --> 00:16:11.649 align:start position:0% stuff in mind has kind of led me to this 00:16:11.649 --> 00:16:15.329 align:start position:0% stuff in mind has kind of led me to this sort<00:16:11.889> of<00:16:11.920> design<00:16:12.660> so<00:16:13.660> yeah<00:16:14.050> just<00:16:14.339> special 00:16:15.329 --> 00:16:15.339 align:start position:0% sort of design so yeah just special 00:16:15.339 --> 00:16:17.519 align:start position:0% sort of design so yeah just special thanks<00:16:15.699> to<00:16:15.939> a<00:16:15.970> few<00:16:16.300> people<00:16:16.420> so<00:16:16.899> Richard<00:16:17.319> Moore 00:16:17.519 --> 00:16:17.529 align:start position:0% thanks to a few people so Richard Moore 00:16:17.529 --> 00:16:20.960 align:start position:0% thanks to a few people so Richard Moore for<00:16:17.829> doing<00:16:18.100> Easy's<00:16:18.399> J<00:16:18.610> s<00:16:18.730> web<00:16:19.329> 3j<00:16:19.959> s<00:16:20.079> and<00:16:20.379> Fabian 00:16:20.960 --> 00:16:20.970 align:start position:0% for doing Easy's J s web 3j s and Fabian 00:16:20.970 --> 00:16:23.730 align:start position:0% for doing Easy's J s web 3j s and Fabian for<00:16:21.970> you<00:16:22.180> know<00:16:22.300> Manning<00:16:22.870> the<00:16:22.990> ship<00:16:23.199> and<00:16:23.529> like 00:16:23.730 --> 00:16:23.740 align:start position:0% for you know Manning the ship and like 00:16:23.740 --> 00:16:25.980 align:start position:0% for you know Manning the ship and like holy<00:16:24.819> it's<00:16:25.209> been<00:16:25.389> just<00:16:25.629> like<00:16:25.660> a<00:16:25.779> crazy 00:16:25.980 --> 00:16:25.990 align:start position:0% holy it's been just like a crazy 00:16:25.990 --> 00:16:27.449 align:start position:0% holy it's been just like a crazy ride<00:16:26.319> and<00:16:26.680> now<00:16:26.800> there's<00:16:26.980> like<00:16:27.100> a<00:16:27.160> bazillion 00:16:27.449 --> 00:16:27.459 align:start position:0% ride and now there's like a bazillion 00:16:27.459 --> 00:16:30.449 align:start position:0% ride and now there's like a bazillion people<00:16:27.639> in<00:16:28.300> the<00:16:28.629> DEF<00:16:28.959> CON<00:16:29.139> room<00:16:29.439> and<00:16:30.069> not<00:16:30.279> just 00:16:30.449 --> 00:16:30.459 align:start position:0% people in the DEF CON room and not just 00:16:30.459 --> 00:16:34.559 align:start position:0% people in the DEF CON room and not just like<00:16:30.639> a<00:16:30.850> hundred<00:16:31.620> and<00:16:32.759> in<00:16:33.759> Dan<00:16:34.089> Finley<00:16:34.449> from 00:16:34.559 --> 00:16:34.569 align:start position:0% like a hundred and in Dan Finley from 00:16:34.569 --> 00:16:37.739 align:start position:0% like a hundred and in Dan Finley from meadow<00:16:34.779> mask<00:16:34.990> and<00:16:35.470> Pele<00:16:35.679> and<00:16:36.670> martin<00:16:37.480> betsy 00:16:37.739 --> 00:16:37.749 align:start position:0% meadow mask and Pele and martin betsy 00:16:37.749 --> 00:16:40.619 align:start position:0% meadow mask and Pele and martin betsy and<00:16:38.279> metallic<00:16:39.279> for<00:16:39.459> creating<00:16:39.730> a<00:16:39.819> cerium<00:16:40.179> which 00:16:40.619 --> 00:16:40.629 align:start position:0% and metallic for creating a cerium which 00:16:40.629 --> 00:16:42.629 align:start position:0% and metallic for creating a cerium which I<00:16:40.899> always<00:16:41.079> think<00:16:41.379> at<00:16:41.620> the<00:16:41.709> end<00:16:41.740> I<00:16:42.100> just<00:16:42.490> think 00:16:42.629 --> 00:16:42.639 align:start position:0% I always think at the end I just think 00:16:42.639 --> 00:16:46.319 align:start position:0% I always think at the end I just think it's<00:16:42.819> great<00:16:43.240> you<00:16:43.509> know<00:16:43.920> and<00:16:44.920> then<00:16:45.670> Joe<00:16:46.300> and 00:16:46.319 --> 00:16:46.329 align:start position:0% it's great you know and then Joe and 00:16:46.329 --> 00:16:49.799 align:start position:0% it's great you know and then Joe and consensus<00:16:47.290> for<00:16:48.100> funding<00:16:48.610> everything<00:16:48.970> this<00:16:49.720> is 00:16:49.799 --> 00:16:49.809 align:start position:0% consensus for funding everything this is 00:16:49.809 --> 00:16:53.429 align:start position:0% consensus for funding everything this is my<00:16:49.899> contact<00:16:50.399> and<00:16:51.399> that's<00:16:51.759> the<00:16:52.029> link<00:16:52.540> to<00:16:52.749> EJ<00:16:53.350> s 00:16:53.429 --> 00:16:53.439 align:start position:0% my contact and that's the link to EJ s 00:16:53.439 --> 00:17:00.790 align:start position:0% my contact and that's the link to EJ s and<00:16:54.009> thank<00:16:54.429> you 00:17:00.790 --> 00:17:00.800 align:start position:0% 00:17:00.800 --> 00:17:08.380 align:start position:0% [Music]