WEBVTT Kind: captions Language: en 00:00:05.770 --> 00:00:08.710 align:start position:0% morning<00:00:06.770> guys<00:00:07.220> thanks<00:00:08.180> for<00:00:08.300> coming<00:00:08.540> bright 00:00:08.710 --> 00:00:08.720 align:start position:0% morning guys thanks for coming bright 00:00:08.720 --> 00:00:11.560 align:start position:0% morning guys thanks for coming bright and<00:00:08.870> early<00:00:09.340> so<00:00:10.340> I'm<00:00:10.430> gonna<00:00:10.550> actually<00:00:10.760> tempt 00:00:11.560 --> 00:00:11.570 align:start position:0% and early so I'm gonna actually tempt 00:00:11.570 --> 00:00:14.970 align:start position:0% and early so I'm gonna actually tempt the<00:00:11.930> demo<00:00:12.590> gods<00:00:12.860> today<00:00:13.430> it'll<00:00:14.150> be<00:00:14.240> interesting 00:00:14.970 --> 00:00:14.980 align:start position:0% the demo gods today it'll be interesting 00:00:14.980 --> 00:00:17.440 align:start position:0% the demo gods today it'll be interesting because<00:00:15.980> the<00:00:16.910> things<00:00:17.119> that<00:00:17.150> I'm<00:00:17.300> going<00:00:17.420> to 00:00:17.440 --> 00:00:17.450 align:start position:0% because the things that I'm going to 00:00:17.450 --> 00:00:20.350 align:start position:0% because the things that I'm going to show<00:00:17.660> you<00:00:17.689> today<00:00:18.110> and<00:00:18.290> demonstrate<00:00:19.060> take<00:00:20.060> long 00:00:20.350 --> 00:00:20.360 align:start position:0% show you today and demonstrate take long 00:00:20.360 --> 00:00:22.180 align:start position:0% show you today and demonstrate take long enough<00:00:20.660> to<00:00:20.779> deploy<00:00:21.140> that<00:00:21.530> I<00:00:21.590> kind<00:00:21.890> of<00:00:21.949> want<00:00:22.100> to 00:00:22.180 --> 00:00:22.190 align:start position:0% enough to deploy that I kind of want to 00:00:22.190 --> 00:00:26.260 align:start position:0% enough to deploy that I kind of want to get<00:00:22.310> started<00:00:22.610> right<00:00:23.000> now<00:00:23.449> so<00:00:24.460> I<00:00:25.460> also<00:00:25.850> want<00:00:26.210> to 00:00:26.260 --> 00:00:26.270 align:start position:0% get started right now so I also want to 00:00:26.270 --> 00:00:28.570 align:start position:0% get started right now so I also want to thank<00:00:26.539> the<00:00:26.779> conference<00:00:27.590> organizers<00:00:28.250> for 00:00:28.570 --> 00:00:28.580 align:start position:0% thank the conference organizers for 00:00:28.580 --> 00:00:37.080 align:start position:0% thank the conference organizers for providing<00:00:29.359> us<00:00:29.539> with<00:00:30.279> these<00:00:31.279> free<00:00:35.710> LTE 00:00:37.080 --> 00:00:37.090 align:start position:0% providing us with these free LTE 00:00:37.090 --> 00:00:38.979 align:start position:0% providing us with these free LTE connections<00:00:38.090> because<00:00:38.570> that's<00:00:38.750> what<00:00:38.899> I'm 00:00:38.979 --> 00:00:38.989 align:start position:0% connections because that's what I'm 00:00:38.989 --> 00:00:41.010 align:start position:0% connections because that's what I'm using<00:00:39.260> right<00:00:39.590> now<00:00:39.620> to<00:00:39.770> be<00:00:40.010> able<00:00:40.160> to<00:00:40.250> do<00:00:40.370> this 00:00:41.010 --> 00:00:41.020 align:start position:0% using right now to be able to do this 00:00:41.020 --> 00:00:43.330 align:start position:0% using right now to be able to do this the<00:00:42.020> Wi-Fi<00:00:42.350> hasn't<00:00:42.680> been<00:00:42.800> great<00:00:43.010> but 00:00:43.330 --> 00:00:43.340 align:start position:0% the Wi-Fi hasn't been great but 00:00:43.340 --> 00:00:46.830 align:start position:0% the Wi-Fi hasn't been great but fortunately<00:00:44.180> we<00:00:44.420> have<00:00:44.570> these<00:00:45.100> wireless 00:00:46.830 --> 00:00:46.840 align:start position:0% fortunately we have these wireless 00:00:46.840 --> 00:00:50.530 align:start position:0% fortunately we have these wireless hotspots<00:00:47.840> we<00:00:48.020> can<00:00:48.200> use<00:00:48.410> so<00:00:48.940> I'll<00:00:49.940> just<00:00:50.180> deploy 00:00:50.530 --> 00:00:50.540 align:start position:0% hotspots we can use so I'll just deploy 00:00:50.540 --> 00:00:52.900 align:start position:0% hotspots we can use so I'll just deploy this<00:00:50.750> and<00:00:51.050> then<00:00:51.200> break<00:00:52.070> into<00:00:52.280> it<00:00:52.489> in<00:00:52.579> just<00:00:52.820> a 00:00:52.900 --> 00:00:52.910 align:start position:0% this and then break into it in just a 00:00:52.910 --> 00:01:02.979 align:start position:0% this and then break into it in just a minute<00:00:53.030> so<00:01:00.820> changing<00:01:01.820> my<00:01:01.910> config<00:01:02.360> params<00:01:02.719> to 00:01:02.979 --> 00:01:02.989 align:start position:0% minute so changing my config params to 00:01:02.989 --> 00:01:07.410 align:start position:0% minute so changing my config params to suit<00:01:03.199> my<00:01:03.350> needs<00:01:04.059> then<00:01:05.059> going<00:01:05.449> ahead<00:01:05.570> and 00:01:07.410 --> 00:01:07.420 align:start position:0% suit my needs then going ahead and 00:01:07.420 --> 00:01:27.380 align:start position:0% suit my needs then going ahead and setting<00:01:08.420> up<00:01:08.509> my<00:01:08.660> dependencies 00:01:27.380 --> 00:01:27.390 align:start position:0% 00:01:27.390 --> 00:01:29.470 align:start position:0% and<00:01:27.510> then<00:01:28.080> I<00:01:28.110> go<00:01:28.320> ahead<00:01:28.350> and<00:01:28.620> kick<00:01:28.770> off<00:01:28.950> this 00:01:29.470 --> 00:01:29.480 align:start position:0% and then I go ahead and kick off this 00:01:29.480 --> 00:01:31.760 align:start position:0% and then I go ahead and kick off this cloud<00:01:30.480> formation<00:01:31.020> template<00:01:31.440> that<00:01:31.470> will 00:01:31.760 --> 00:01:31.770 align:start position:0% cloud formation template that will 00:01:31.770 --> 00:01:33.650 align:start position:0% cloud formation template that will deploy<00:01:32.220> the<00:01:32.610> solution<00:01:32.880> that<00:01:33.240> I'll<00:01:33.330> be<00:01:33.450> talking 00:01:33.650 --> 00:01:33.660 align:start position:0% deploy the solution that I'll be talking 00:01:33.660 --> 00:01:36.530 align:start position:0% deploy the solution that I'll be talking about<00:01:33.960> right<00:01:34.320> now<00:01:34.350> so<00:01:34.950> you<00:01:35.850> jump<00:01:36.120> back<00:01:36.300> into 00:01:36.530 --> 00:01:36.540 align:start position:0% about right now so you jump back into 00:01:36.540 --> 00:01:42.380 align:start position:0% about right now so you jump back into that<00:01:36.780> I<00:01:38.420> also<00:01:39.420> want<00:01:39.840> to<00:01:40.670> say<00:01:41.670> hi<00:01:41.850> to<00:01:41.880> one<00:01:42.150> of<00:01:42.270> my 00:01:42.380 --> 00:01:42.390 align:start position:0% that I also want to say hi to one of my 00:01:42.390 --> 00:01:44.150 align:start position:0% that I also want to say hi to one of my local<00:01:42.630> counterparts<00:01:43.110> from<00:01:43.470> Tokyo 00:01:44.150 --> 00:01:44.160 align:start position:0% local counterparts from Tokyo 00:01:44.160 --> 00:01:46.190 align:start position:0% local counterparts from Tokyo Yuki<00:01:44.610> naka<00:01:44.880> taki<00:01:45.270> which<00:01:45.780> is<00:01:45.930> right<00:01:46.170> here 00:01:46.190 --> 00:01:46.200 align:start position:0% Yuki naka taki which is right here 00:01:46.200 --> 00:01:49.660 align:start position:0% Yuki naka taki which is right here joining<00:01:46.590> me<00:01:46.740> thanks<00:01:47.700> for<00:01:47.730> being<00:01:48.030> here 00:01:49.660 --> 00:01:49.670 align:start position:0% joining me thanks for being here 00:01:49.670 --> 00:01:53.690 align:start position:0% joining me thanks for being here so<00:01:50.670> I'm<00:01:51.300> Carl<00:01:51.750> Youngblood<00:01:52.230> I<00:01:52.440> am<00:01:53.250> a<00:01:53.430> senior 00:01:53.690 --> 00:01:53.700 align:start position:0% so I'm Carl Youngblood I am a senior 00:01:53.700 --> 00:01:56.480 align:start position:0% so I'm Carl Youngblood I am a senior blockchain<00:01:54.180> Solutions<00:01:54.960> Architect<00:01:55.260> with<00:01:55.710> AWS 00:01:56.480 --> 00:01:56.490 align:start position:0% blockchain Solutions Architect with AWS 00:01:56.490 --> 00:02:00.050 align:start position:0% blockchain Solutions Architect with AWS and<00:01:57.440> I've<00:01:58.440> been<00:01:58.710> doing<00:01:59.100> work<00:01:59.670> with 00:02:00.050 --> 00:02:00.060 align:start position:0% and I've been doing work with 00:02:00.060 --> 00:02:04.100 align:start position:0% and I've been doing work with blockchains<00:02:00.630> for<00:02:00.990> quite<00:02:01.290> a<00:02:01.320> while<00:02:01.790> I<00:02:03.110> first 00:02:04.100 --> 00:02:04.110 align:start position:0% blockchains for quite a while I first 00:02:04.110 --> 00:02:06.800 align:start position:0% blockchains for quite a while I first became<00:02:04.320> interested<00:02:04.890> in<00:02:05.250> blockchain<00:02:05.790> in<00:02:06.030> 2010 00:02:06.800 --> 00:02:06.810 align:start position:0% became interested in blockchain in 2010 00:02:06.810 --> 00:02:09.350 align:start position:0% became interested in blockchain in 2010 when<00:02:07.020> I<00:02:07.050> read<00:02:07.350> Satoshi's<00:02:07.950> white<00:02:08.190> paper<00:02:08.459> and<00:02:08.790> it 00:02:09.350 --> 00:02:09.360 align:start position:0% when I read Satoshi's white paper and it 00:02:09.360 --> 00:02:11.240 align:start position:0% when I read Satoshi's white paper and it was<00:02:09.479> one<00:02:09.690> of<00:02:09.720> the<00:02:09.899> only<00:02:10.229> white<00:02:10.770> papers<00:02:11.220> that 00:02:11.240 --> 00:02:11.250 align:start position:0% was one of the only white papers that 00:02:11.250 --> 00:02:13.670 align:start position:0% was one of the only white papers that actually<00:02:11.790> came<00:02:12.060> with<00:02:12.090> working<00:02:12.750> software<00:02:13.080> it 00:02:13.670 --> 00:02:13.680 align:start position:0% actually came with working software it 00:02:13.680 --> 00:02:16.190 align:start position:0% actually came with working software it was<00:02:13.890> really<00:02:14.250> exciting<00:02:14.760> to<00:02:14.790> actually<00:02:15.330> set<00:02:16.080> it 00:02:16.190 --> 00:02:16.200 align:start position:0% was really exciting to actually set it 00:02:16.200 --> 00:02:18.800 align:start position:0% was really exciting to actually set it up<00:02:16.290> and<00:02:16.500> run<00:02:16.740> it<00:02:16.890> and<00:02:17.130> I<00:02:17.910> was<00:02:18.120> lucky<00:02:18.510> enough<00:02:18.540> to 00:02:18.800 --> 00:02:18.810 align:start position:0% up and run it and I was lucky enough to 00:02:18.810 --> 00:02:24.230 align:start position:0% up and run it and I was lucky enough to be<00:02:19.560> in<00:02:19.950> living<00:02:20.910> near<00:02:21.090> London<00:02:21.770> in<00:02:22.770> 2014<00:02:23.670> around 00:02:24.230 --> 00:02:24.240 align:start position:0% be in living near London in 2014 around 00:02:24.240 --> 00:02:26.420 align:start position:0% be in living near London in 2014 around the<00:02:24.360> time<00:02:24.540> that<00:02:24.570> like<00:02:24.870> the<00:02:25.050> first<00:02:25.320> theory<00:02:26.310> and 00:02:26.420 --> 00:02:26.430 align:start position:0% the time that like the first theory and 00:02:26.430 --> 00:02:29.750 align:start position:0% the time that like the first theory and meetups<00:02:26.730> got<00:02:26.910> started<00:02:27.300> as<00:02:27.450> well<00:02:28.370> so<00:02:29.370> before<00:02:29.730> I 00:02:29.750 --> 00:02:29.760 align:start position:0% meetups got started as well so before I 00:02:29.760 --> 00:02:32.960 align:start position:0% meetups got started as well so before I joined<00:02:30.090> a<00:02:30.240> AWS<00:02:31.070> my<00:02:32.070> brother<00:02:32.310> and<00:02:32.489> I<00:02:32.550> co-founded 00:02:32.960 --> 00:02:32.970 align:start position:0% joined a AWS my brother and I co-founded 00:02:32.970 --> 00:02:36.100 align:start position:0% joined a AWS my brother and I co-founded a<00:02:33.420> consulting<00:02:34.380> company<00:02:34.560> called<00:02:35.160> black<00:02:35.459> scale 00:02:36.100 --> 00:02:36.110 align:start position:0% a consulting company called black scale 00:02:36.110 --> 00:02:41.270 align:start position:0% a consulting company called black scale and<00:02:37.400> we<00:02:38.400> deployed<00:02:39.269> some<00:02:39.810> node<00:02:40.410> infrastructure 00:02:41.270 --> 00:02:41.280 align:start position:0% and we deployed some node infrastructure 00:02:41.280 --> 00:02:44.630 align:start position:0% and we deployed some node infrastructure solutions<00:02:41.850> for<00:02:42.350> companies<00:02:43.350> like<00:02:43.830> my<00:02:44.130> crypt<00:02:44.489> oh 00:02:44.630 --> 00:02:44.640 align:start position:0% solutions for companies like my crypt oh 00:02:44.640 --> 00:02:47.030 align:start position:0% solutions for companies like my crypt oh and<00:02:44.940> the<00:02:45.090> Tesla<00:02:45.420> Foundation<00:02:46.019> and<00:02:46.260> I'm<00:02:46.890> gonna 00:02:47.030 --> 00:02:47.040 align:start position:0% and the Tesla Foundation and I'm gonna 00:02:47.040 --> 00:02:48.800 align:start position:0% and the Tesla Foundation and I'm gonna be<00:02:47.190> sharing<00:02:47.610> some<00:02:47.640> of<00:02:47.940> the<00:02:48.030> things<00:02:48.269> we<00:02:48.480> learned 00:02:48.800 --> 00:02:48.810 align:start position:0% be sharing some of the things we learned 00:02:48.810 --> 00:02:53.300 align:start position:0% be sharing some of the things we learned in<00:02:49.530> that<00:02:49.590> process<00:02:49.800> today<00:02:50.750> so<00:02:51.750> first<00:02:52.590> I<00:02:52.800> want<00:02:53.250> to 00:02:53.300 --> 00:02:53.310 align:start position:0% in that process today so first I want to 00:02:53.310 --> 00:02:54.199 align:start position:0% in that process today so first I want to share<00:02:53.580> some<00:02:53.790> thoughts<00:02:53.970> about 00:02:54.199 --> 00:02:54.209 align:start position:0% share some thoughts about 00:02:54.209 --> 00:02:56.540 align:start position:0% share some thoughts about decentralization<00:02:54.720> and<00:02:55.590> how<00:02:56.310> it<00:02:56.459> can 00:02:56.540 --> 00:02:56.550 align:start position:0% decentralization and how it can 00:02:56.550 --> 00:02:58.479 align:start position:0% decentralization and how it can sometimes<00:02:56.820> differ<00:02:57.269> in<00:02:57.540> theory<00:02:57.959> and<00:02:58.080> practice 00:02:58.479 --> 00:02:58.489 align:start position:0% sometimes differ in theory and practice 00:02:58.489 --> 00:03:00.890 align:start position:0% sometimes differ in theory and practice so<00:02:59.489> and<00:02:59.790> after<00:02:59.970> that<00:03:00.239> I'm<00:03:00.390> gonna<00:03:00.510> explain<00:03:00.840> a 00:03:00.890 --> 00:03:00.900 align:start position:0% so and after that I'm gonna explain a 00:03:00.900 --> 00:03:03.410 align:start position:0% so and after that I'm gonna explain a strategy<00:03:01.440> that<00:03:01.470> we<00:03:01.830> used<00:03:02.130> for<00:03:02.459> deploying 00:03:03.410 --> 00:03:03.420 align:start position:0% strategy that we used for deploying 00:03:03.420 --> 00:03:06.050 align:start position:0% strategy that we used for deploying highly<00:03:03.900> available<00:03:04.140> node<00:03:05.100> infrastructure<00:03:05.760> and 00:03:06.050 --> 00:03:06.060 align:start position:0% highly available node infrastructure and 00:03:06.060 --> 00:03:09.530 align:start position:0% highly available node infrastructure and then<00:03:06.840> some<00:03:07.830> ways<00:03:08.040> that<00:03:08.280> we<00:03:08.370> DIF<00:03:08.610> mitigated 00:03:09.530 --> 00:03:09.540 align:start position:0% then some ways that we DIF mitigated 00:03:09.540 --> 00:03:11.479 align:start position:0% then some ways that we DIF mitigated against<00:03:09.959> some<00:03:10.260> different<00:03:10.739> challenges<00:03:11.280> and 00:03:11.479 --> 00:03:11.489 align:start position:0% against some different challenges and 00:03:11.489 --> 00:03:15.440 align:start position:0% against some different challenges and problems<00:03:11.700> with<00:03:12.209> you<00:03:12.480> VMs<00:03:13.019> and<00:03:14.269> also<00:03:15.269> how<00:03:15.390> we 00:03:15.440 --> 00:03:15.450 align:start position:0% problems with you VMs and also how we 00:03:15.450 --> 00:03:17.540 align:start position:0% problems with you VMs and also how we made<00:03:15.690> our<00:03:15.720> deployment<00:03:16.620> more<00:03:16.739> cost<00:03:17.010> effective 00:03:17.540 --> 00:03:17.550 align:start position:0% made our deployment more cost effective 00:03:17.550 --> 00:03:20.240 align:start position:0% made our deployment more cost effective and<00:03:17.730> then<00:03:18.720> finally<00:03:19.230> I'll<00:03:19.410> show<00:03:19.920> you<00:03:19.980> a<00:03:20.070> little 00:03:20.240 --> 00:03:20.250 align:start position:0% and then finally I'll show you a little 00:03:20.250 --> 00:03:23.449 align:start position:0% and then finally I'll show you a little bit<00:03:20.400> more<00:03:20.640> of<00:03:20.820> this<00:03:20.989> solution<00:03:21.989> that<00:03:22.140> I<00:03:22.650> just 00:03:23.449 --> 00:03:23.459 align:start position:0% bit more of this solution that I just 00:03:23.459 --> 00:03:26.750 align:start position:0% bit more of this solution that I just deployed<00:03:23.790> so<00:03:24.590> one<00:03:25.590> of<00:03:25.620> the<00:03:25.799> great<00:03:26.010> promises<00:03:26.280> of 00:03:26.750 --> 00:03:26.760 align:start position:0% deployed so one of the great promises of 00:03:26.760 --> 00:03:28.970 align:start position:0% deployed so one of the great promises of blockchain<00:03:27.209> technology<00:03:27.840> was<00:03:28.140> that<00:03:28.410> you<00:03:28.860> know 00:03:28.970 --> 00:03:28.980 align:start position:0% blockchain technology was that you know 00:03:28.980 --> 00:03:32.210 align:start position:0% blockchain technology was that you know it<00:03:29.190> enabled<00:03:29.730> greater<00:03:30.480> decentralization<00:03:31.220> so 00:03:32.210 --> 00:03:32.220 align:start position:0% it enabled greater decentralization so 00:03:32.220 --> 00:03:34.820 align:start position:0% it enabled greater decentralization so in<00:03:32.370> the<00:03:32.459> same<00:03:32.640> way<00:03:32.820> that<00:03:33.060> anybody<00:03:33.930> the 00:03:34.820 --> 00:03:34.830 align:start position:0% in the same way that anybody the 00:03:34.830 --> 00:03:37.070 align:start position:0% in the same way that anybody the Internet<00:03:35.130> is<00:03:35.250> a<00:03:35.280> permissionless<00:03:36.080> network 00:03:37.070 --> 00:03:37.080 align:start position:0% Internet is a permissionless network 00:03:37.080 --> 00:03:39.350 align:start position:0% Internet is a permissionless network that<00:03:37.350> anybody<00:03:37.800> with<00:03:38.069> a<00:03:38.100> computer<00:03:38.340> can 00:03:39.350 --> 00:03:39.360 align:start position:0% that anybody with a computer can 00:03:39.360 --> 00:03:41.180 align:start position:0% that anybody with a computer can and<00:03:39.780> the<00:03:39.990> right<00:03:40.140> equipment<00:03:40.590> can<00:03:40.710> just<00:03:40.890> hook<00:03:41.010> up 00:03:41.180 --> 00:03:41.190 align:start position:0% and the right equipment can just hook up 00:03:41.190 --> 00:03:43.490 align:start position:0% and the right equipment can just hook up to<00:03:41.430> and<00:03:41.700> as<00:03:42.690> long<00:03:42.840> as<00:03:42.870> they're<00:03:43.080> speaking<00:03:43.260> the 00:03:43.490 --> 00:03:43.500 align:start position:0% to and as long as they're speaking the 00:03:43.500 --> 00:03:44.360 align:start position:0% to and as long as they're speaking the right<00:03:43.650> protocols 00:03:44.360 --> 00:03:44.370 align:start position:0% right protocols 00:03:44.370 --> 00:03:47.680 align:start position:0% right protocols they<00:03:45.150> can<00:03:45.560> they<00:03:46.560> can<00:03:46.740> join<00:03:46.950> in<00:03:47.160> this<00:03:47.310> network 00:03:47.680 --> 00:03:47.690 align:start position:0% they can they can join in this network 00:03:47.690 --> 00:03:50.630 align:start position:0% they can they can join in this network blockchain<00:03:48.690> also<00:03:49.310> eliminates<00:03:50.310> the<00:03:50.430> need<00:03:50.580> to 00:03:50.630 --> 00:03:50.640 align:start position:0% blockchain also eliminates the need to 00:03:50.640 --> 00:03:53.240 align:start position:0% blockchain also eliminates the need to trust<00:03:51.060> in<00:03:51.270> these<00:03:51.450> large<00:03:51.840> central<00:03:52.530> authorities 00:03:53.240 --> 00:03:53.250 align:start position:0% trust in these large central authorities 00:03:53.250 --> 00:03:58.010 align:start position:0% trust in these large central authorities to<00:03:53.490> track<00:03:53.730> information<00:03:56.240> even<00:03:57.240> private 00:03:58.010 --> 00:03:58.020 align:start position:0% to track information even private 00:03:58.020 --> 00:04:00.380 align:start position:0% to track information even private permission<00:03:58.590> block<00:03:58.800> chains<00:03:59.130> have<00:04:00.000> the<00:04:00.120> goal<00:04:00.360> of 00:04:00.380 --> 00:04:00.390 align:start position:0% permission block chains have the goal of 00:04:00.390 --> 00:04:03.170 align:start position:0% permission block chains have the goal of leveraging<00:04:01.260> decentralization<00:04:02.070> across<00:04:02.880> all 00:04:03.170 --> 00:04:03.180 align:start position:0% leveraging decentralization across all 00:04:03.180 --> 00:04:05.240 align:start position:0% leveraging decentralization across all the<00:04:03.330> participants<00:04:03.960> to<00:04:04.740> increase<00:04:05.100> the 00:04:05.240 --> 00:04:05.250 align:start position:0% the participants to increase the 00:04:05.250 --> 00:04:07.280 align:start position:0% the participants to increase the security<00:04:05.640> and<00:04:06.120> the<00:04:06.170> reliability<00:04:07.170> of<00:04:07.200> the 00:04:07.280 --> 00:04:07.290 align:start position:0% security and the reliability of the 00:04:07.290 --> 00:04:12.080 align:start position:0% security and the reliability of the network<00:04:08.750> but<00:04:09.750> some<00:04:10.080> of<00:04:10.230> the<00:04:10.350> initial<00:04:11.090> ideas 00:04:12.080 --> 00:04:12.090 align:start position:0% network but some of the initial ideas 00:04:12.090 --> 00:04:13.820 align:start position:0% network but some of the initial ideas about<00:04:12.360> decentralization<00:04:12.750> have<00:04:13.350> been<00:04:13.470> kind<00:04:13.740> of 00:04:13.820 --> 00:04:13.830 align:start position:0% about decentralization have been kind of 00:04:13.830 --> 00:04:14.750 align:start position:0% about decentralization have been kind of naive<00:04:14.220> so 00:04:14.750 --> 00:04:14.760 align:start position:0% naive so 00:04:14.760 --> 00:04:17.960 align:start position:0% naive so Vitalik<00:04:15.600> his<00:04:16.440> earlier<00:04:16.859> claim<00:04:17.160> that<00:04:17.400> aetherium 00:04:17.960 --> 00:04:17.970 align:start position:0% Vitalik his earlier claim that aetherium 00:04:17.970 --> 00:04:19.820 align:start position:0% Vitalik his earlier claim that aetherium should<00:04:18.239> be<00:04:18.390> able<00:04:18.480> to<00:04:18.660> achieve<00:04:18.900> on<00:04:19.380> chain 00:04:19.820 --> 00:04:19.830 align:start position:0% should be able to achieve on chain 00:04:19.830 --> 00:04:22.580 align:start position:0% should be able to achieve on chain scaling<00:04:20.519> while<00:04:21.330> running<00:04:21.660> on<00:04:21.840> nothing<00:04:22.350> other 00:04:22.580 --> 00:04:22.590 align:start position:0% scaling while running on nothing other 00:04:22.590 --> 00:04:25.850 align:start position:0% scaling while running on nothing other than<00:04:23.040> consumer<00:04:23.730> laptops<00:04:24.270> has<00:04:25.110> been<00:04:25.380> forced<00:04:25.680> to 00:04:25.850 --> 00:04:25.860 align:start position:0% than consumer laptops has been forced to 00:04:25.860 --> 00:04:28.340 align:start position:0% than consumer laptops has been forced to confront<00:04:26.220> some<00:04:26.660> perennial<00:04:27.660> challenges<00:04:28.200> in 00:04:28.340 --> 00:04:28.350 align:start position:0% confront some perennial challenges in 00:04:28.350 --> 00:04:31.370 align:start position:0% confront some perennial challenges in computer<00:04:28.800> science<00:04:29.010> about<00:04:29.550> data<00:04:30.270> locality<00:04:30.750> and 00:04:31.370 --> 00:04:31.380 align:start position:0% computer science about data locality and 00:04:31.380 --> 00:04:34.940 align:start position:0% computer science about data locality and constraints<00:04:32.280> of<00:04:32.400> networking<00:04:33.290> so<00:04:34.290> while<00:04:34.920> that 00:04:34.940 --> 00:04:34.950 align:start position:0% constraints of networking so while that 00:04:34.950 --> 00:04:38.030 align:start position:0% constraints of networking so while that scaling<00:04:35.520> work<00:04:35.850> is<00:04:36.030> ongoing<00:04:36.300> and<00:04:37.020> I<00:04:37.320> certainly 00:04:38.030 --> 00:04:38.040 align:start position:0% scaling work is ongoing and I certainly 00:04:38.040 --> 00:04:40.280 align:start position:0% scaling work is ongoing and I certainly applaud<00:04:38.550> it<00:04:38.760> and<00:04:39.360> grateful<00:04:39.810> for<00:04:39.990> their<00:04:40.110> work 00:04:40.280 --> 00:04:40.290 align:start position:0% applaud it and grateful for their work 00:04:40.290 --> 00:04:43.900 align:start position:0% applaud it and grateful for their work their<00:04:40.760> companies<00:04:41.870> still<00:04:42.870> need<00:04:43.140> practical 00:04:43.900 --> 00:04:43.910 align:start position:0% their companies still need practical 00:04:43.910 --> 00:04:46.670 align:start position:0% their companies still need practical blockchain<00:04:44.910> solutions<00:04:45.540> for<00:04:45.930> deploying<00:04:46.350> their 00:04:46.670 --> 00:04:46.680 align:start position:0% blockchain solutions for deploying their 00:04:46.680 --> 00:04:49.280 align:start position:0% blockchain solutions for deploying their infrastructure<00:04:47.300> that<00:04:48.300> are<00:04:48.450> robust<00:04:48.960> and 00:04:49.280 --> 00:04:49.290 align:start position:0% infrastructure that are robust and 00:04:49.290 --> 00:04:51.560 align:start position:0% infrastructure that are robust and reliable<00:04:49.500> enough<00:04:50.070> for<00:04:50.820> their<00:04:50.940> applications 00:04:51.560 --> 00:04:51.570 align:start position:0% reliable enough for their applications 00:04:51.570 --> 00:04:55.760 align:start position:0% reliable enough for their applications right<00:04:51.750> now<00:04:52.880> so<00:04:53.880> some<00:04:54.750> companies<00:04:55.380> rely<00:04:55.740> on 00:04:55.760 --> 00:04:55.770 align:start position:0% right now so some companies rely on 00:04:55.770 --> 00:04:59.690 align:start position:0% right now so some companies rely on third-party<00:04:56.400> RPC<00:04:57.360> services<00:04:57.930> and<00:04:58.400> these<00:04:59.400> are 00:04:59.690 --> 00:04:59.700 align:start position:0% third-party RPC services and these are 00:04:59.700 --> 00:05:01.670 align:start position:0% third-party RPC services and these are very<00:05:00.090> helpful<00:05:00.360> and<00:05:00.720> they<00:05:01.050> definitely<00:05:01.500> have<00:05:01.650> a 00:05:01.670 --> 00:05:01.680 align:start position:0% very helpful and they definitely have a 00:05:01.680 --> 00:05:04.490 align:start position:0% very helpful and they definitely have a place<00:05:01.910> but<00:05:02.910> they<00:05:03.270> also<00:05:03.480> represent<00:05:04.320> a 00:05:04.490 --> 00:05:04.500 align:start position:0% place but they also represent a 00:05:04.500 --> 00:05:06.380 align:start position:0% place but they also represent a significant<00:05:05.340> reduction<00:05:05.940> in<00:05:06.090> the<00:05:06.180> overall 00:05:06.380 --> 00:05:06.390 align:start position:0% significant reduction in the overall 00:05:06.390 --> 00:05:08.780 align:start position:0% significant reduction in the overall level<00:05:07.169> of<00:05:07.320> decentralisation<00:05:08.100> in<00:05:08.669> the 00:05:08.780 --> 00:05:08.790 align:start position:0% level of decentralisation in the 00:05:08.790 --> 00:05:11.270 align:start position:0% level of decentralisation in the ecosystem<00:05:09.450> so<00:05:10.440> there<00:05:10.620> are<00:05:10.680> times<00:05:10.890> when<00:05:11.160> you're 00:05:11.270 --> 00:05:11.280 align:start position:0% ecosystem so there are times when you're 00:05:11.280 --> 00:05:13.159 align:start position:0% ecosystem so there are times when you're building<00:05:11.460> an<00:05:11.669> application<00:05:12.270> that's<00:05:12.630> important 00:05:13.159 --> 00:05:13.169 align:start position:0% building an application that's important 00:05:13.169 --> 00:05:15.740 align:start position:0% building an application that's important enough<00:05:13.440> that<00:05:13.710> you<00:05:14.430> want<00:05:14.669> to<00:05:14.820> reduce<00:05:14.970> your 00:05:15.740 --> 00:05:15.750 align:start position:0% enough that you want to reduce your 00:05:15.750 --> 00:05:18.350 align:start position:0% enough that you want to reduce your reliance<00:05:16.380> on<00:05:16.860> external<00:05:17.430> dependencies<00:05:18.060> as 00:05:18.350 --> 00:05:18.360 align:start position:0% reliance on external dependencies as 00:05:18.360 --> 00:05:19.670 align:start position:0% reliance on external dependencies as much<00:05:18.810> as<00:05:18.990> possible 00:05:19.670 --> 00:05:19.680 align:start position:0% much as possible 00:05:19.680 --> 00:05:22.060 align:start position:0% much as possible by<00:05:20.130> deploying<00:05:20.460> your<00:05:20.820> own<00:05:20.970> infrastructure 00:05:22.060 --> 00:05:22.070 align:start position:0% by deploying your own infrastructure 00:05:22.070 --> 00:05:23.960 align:start position:0% by deploying your own infrastructure something<00:05:23.070> that's<00:05:23.220> fully<00:05:23.460> under<00:05:23.790> your 00:05:23.960 --> 00:05:23.970 align:start position:0% something that's fully under your 00:05:23.970 --> 00:05:26.750 align:start position:0% something that's fully under your control<00:05:24.150> and<00:05:24.740> then<00:05:25.740> you<00:05:25.919> also<00:05:26.100> have<00:05:26.370> the<00:05:26.460> added 00:05:26.750 --> 00:05:26.760 align:start position:0% control and then you also have the added 00:05:26.760 --> 00:05:28.280 align:start position:0% control and then you also have the added benefit<00:05:27.120> when<00:05:27.300> you<00:05:27.390> do<00:05:27.570> this<00:05:27.750> that<00:05:28.140> you're 00:05:28.280 --> 00:05:28.290 align:start position:0% benefit when you do this that you're 00:05:28.290 --> 00:05:29.980 align:start position:0% benefit when you do this that you're actually<00:05:28.590> contributing<00:05:29.160> to<00:05:29.490> the<00:05:29.640> overall 00:05:29.980 --> 00:05:29.990 align:start position:0% actually contributing to the overall 00:05:29.990 --> 00:05:33.500 align:start position:0% actually contributing to the overall decentralization<00:05:30.990> of<00:05:31.290> the<00:05:31.410> blockchain<00:05:32.180> so<00:05:33.180> in 00:05:33.500 --> 00:05:33.510 align:start position:0% decentralization of the blockchain so in 00:05:33.510 --> 00:05:35.540 align:start position:0% decentralization of the blockchain so in practice<00:05:34.050> we've<00:05:34.410> kind<00:05:34.710> of<00:05:34.740> observed<00:05:35.130> that<00:05:35.340> the 00:05:35.540 --> 00:05:35.550 align:start position:0% practice we've kind of observed that the 00:05:35.550 --> 00:05:37.420 align:start position:0% practice we've kind of observed that the best<00:05:35.760> way<00:05:36.030> to<00:05:36.060> birth<00:05:36.600> tomorrow's 00:05:37.420 --> 00:05:37.430 align:start position:0% best way to birth tomorrow's 00:05:37.430 --> 00:05:40.130 align:start position:0% best way to birth tomorrow's decentralized<00:05:38.430> infrastructure<00:05:39.150> is<00:05:39.660> to<00:05:39.930> build 00:05:40.130 --> 00:05:40.140 align:start position:0% decentralized infrastructure is to build 00:05:40.140 --> 00:05:44.120 align:start position:0% decentralized infrastructure is to build on<00:05:40.440> the<00:05:41.220> reliable<00:05:42.210> solutions<00:05:42.630> of<00:05:42.750> today<00:05:43.050> so<00:05:43.890> if 00:05:44.120 --> 00:05:44.130 align:start position:0% on the reliable solutions of today so if 00:05:44.130 --> 00:05:46.180 align:start position:0% on the reliable solutions of today so if you<00:05:44.160> need<00:05:44.490> your<00:05:44.640> DAP<00:05:44.850> to<00:05:45.060> be<00:05:45.180> highly<00:05:45.540> available 00:05:46.180 --> 00:05:46.190 align:start position:0% you need your DAP to be highly available 00:05:46.190 --> 00:05:48.890 align:start position:0% you need your DAP to be highly available the<00:05:47.190> underlying<00:05:47.669> node<00:05:48.030> infrastructure<00:05:48.720> that 00:05:48.890 --> 00:05:48.900 align:start position:0% the underlying node infrastructure that 00:05:48.900 --> 00:05:51.260 align:start position:0% the underlying node infrastructure that it<00:05:49.050> relies<00:05:49.350> on<00:05:49.520> needs<00:05:50.520> to<00:05:50.610> also<00:05:50.820> be<00:05:51.000> highly 00:05:51.260 --> 00:05:51.270 align:start position:0% it relies on needs to also be highly 00:05:51.270 --> 00:05:53.150 align:start position:0% it relies on needs to also be highly available 00:05:53.150 --> 00:05:53.160 align:start position:0% available 00:05:53.160 --> 00:05:55.220 align:start position:0% available by<00:05:53.430> leveraging<00:05:53.640> the<00:05:53.880> services<00:05:54.480> of<00:05:54.750> an 00:05:55.220 --> 00:05:55.230 align:start position:0% by leveraging the services of an 00:05:55.230 --> 00:05:58.730 align:start position:0% by leveraging the services of an experienced<00:05:56.010> cloud<00:05:56.250> provider<00:05:57.650> for<00:05:58.650> your 00:05:58.730 --> 00:05:58.740 align:start position:0% experienced cloud provider for your 00:05:58.740 --> 00:06:00.500 align:start position:0% experienced cloud provider for your blockchain<00:05:59.130> deployments<00:05:59.670> you're<00:06:00.240> gonna<00:06:00.360> be 00:06:00.500 --> 00:06:00.510 align:start position:0% blockchain deployments you're gonna be 00:06:00.510 --> 00:06:03.200 align:start position:0% blockchain deployments you're gonna be able<00:06:00.570> to<00:06:00.690> take<00:06:00.900> advantage<00:06:01.440> of<00:06:01.820> just<00:06:02.820> a<00:06:03.000> lot<00:06:03.180> of 00:06:03.200 --> 00:06:03.210 align:start position:0% able to take advantage of just a lot of 00:06:03.210 --> 00:06:04.910 align:start position:0% able to take advantage of just a lot of different<00:06:03.390> things<00:06:03.720> so<00:06:03.930> their<00:06:04.470> unprecedented 00:06:04.910 --> 00:06:04.920 align:start position:0% different things so their unprecedented 00:06:04.920 --> 00:06:07.160 align:start position:0% different things so their unprecedented scale<00:06:05.550> and<00:06:05.850> efficiency<00:06:06.360> and<00:06:06.600> global<00:06:06.960> reach 00:06:07.160 --> 00:06:07.170 align:start position:0% scale and efficiency and global reach 00:06:07.170 --> 00:06:10.940 align:start position:0% scale and efficiency and global reach and<00:06:07.470> also<00:06:08.190> the<00:06:08.610> cost<00:06:08.880> savings<00:06:09.420> that<00:06:09.870> come<00:06:10.680> from 00:06:10.940 --> 00:06:10.950 align:start position:0% and also the cost savings that come from 00:06:10.950 --> 00:06:14.000 align:start position:0% and also the cost savings that come from like<00:06:11.220> the<00:06:12.090> pay-as-you-go<00:06:12.450> model<00:06:13.260> instead<00:06:13.950> of 00:06:14.000 --> 00:06:14.010 align:start position:0% like the pay-as-you-go model instead of 00:06:14.010 --> 00:06:16.250 align:start position:0% like the pay-as-you-go model instead of the<00:06:14.640> sort<00:06:14.850> of<00:06:15.110> over-provisioning<00:06:16.110> your 00:06:16.250 --> 00:06:16.260 align:start position:0% the sort of over-provisioning your 00:06:16.260 --> 00:06:18.890 align:start position:0% the sort of over-provisioning your resources<00:06:16.830> for<00:06:16.980> periods<00:06:17.610> of<00:06:17.820> peak<00:06:18.030> load<00:06:18.420> right 00:06:18.890 --> 00:06:18.900 align:start position:0% resources for periods of peak load right 00:06:18.900 --> 00:06:21.440 align:start position:0% resources for periods of peak load right so<00:06:19.590> before<00:06:19.800> if<00:06:20.250> you're<00:06:20.400> doing<00:06:20.850> an<00:06:21.000> on-prem 00:06:21.440 --> 00:06:21.450 align:start position:0% so before if you're doing an on-prem 00:06:21.450 --> 00:06:24.710 align:start position:0% so before if you're doing an on-prem solution<00:06:21.930> you<00:06:22.050> have<00:06:22.080> to<00:06:22.380> kind<00:06:22.590> of<00:06:22.680> over<00:06:23.720> you 00:06:24.710 --> 00:06:24.720 align:start position:0% solution you have to kind of over you 00:06:24.720 --> 00:06:27.290 align:start position:0% solution you have to kind of over you know<00:06:24.810> stock<00:06:25.380> up<00:06:25.590> on<00:06:25.800> resources<00:06:26.610> just<00:06:26.820> in<00:06:27.030> case 00:06:27.290 --> 00:06:27.300 align:start position:0% know stock up on resources just in case 00:06:27.300 --> 00:06:30.080 align:start position:0% know stock up on resources just in case you<00:06:27.570> need<00:06:27.780> them<00:06:27.990> and<00:06:28.550> clearly<00:06:29.550> this<00:06:29.669> is<00:06:29.850> less 00:06:30.080 --> 00:06:30.090 align:start position:0% you need them and clearly this is less 00:06:30.090 --> 00:06:32.210 align:start position:0% you need them and clearly this is less efficient<00:06:30.630> it<00:06:30.840> results<00:06:31.530> in<00:06:31.620> a<00:06:31.680> lot<00:06:31.830> of<00:06:31.950> waste 00:06:32.210 --> 00:06:32.220 align:start position:0% efficient it results in a lot of waste 00:06:32.220 --> 00:06:35.390 align:start position:0% efficient it results in a lot of waste and<00:06:32.520> one<00:06:33.210> other<00:06:33.360> huge<00:06:34.320> benefit<00:06:34.800> is<00:06:34.919> that<00:06:34.950> you 00:06:35.390 --> 00:06:35.400 align:start position:0% and one other huge benefit is that you 00:06:35.400 --> 00:06:38.240 align:start position:0% and one other huge benefit is that you know<00:06:35.880> these<00:06:36.000> cloud<00:06:36.390> providers<00:06:36.930> like<00:06:37.380> AWS<00:06:37.919> have 00:06:38.240 --> 00:06:38.250 align:start position:0% know these cloud providers like AWS have 00:06:38.250 --> 00:06:39.770 align:start position:0% know these cloud providers like AWS have been<00:06:38.400> doing<00:06:38.730> this<00:06:38.850> for<00:06:38.910> a<00:06:39.090> long<00:06:39.210> time<00:06:39.510> they 00:06:39.770 --> 00:06:39.780 align:start position:0% been doing this for a long time they 00:06:39.780 --> 00:06:42.100 align:start position:0% been doing this for a long time they really<00:06:40.020> know<00:06:40.140> what<00:06:40.290> they're<00:06:40.410> doing<00:06:40.440> and 00:06:42.100 --> 00:06:42.110 align:start position:0% really know what they're doing and 00:06:42.110 --> 00:06:45.950 align:start position:0% really know what they're doing and they're<00:06:43.110> already<00:06:44.010> running<00:06:44.640> on<00:06:45.060> over<00:06:45.630> fifty 00:06:45.950 --> 00:06:45.960 align:start position:0% they're already running on over fifty 00:06:45.960 --> 00:06:49.130 align:start position:0% they're already running on over fifty percent<00:06:45.990> renewable<00:06:46.590> energy<00:06:47.310> and<00:06:47.550> our<00:06:48.030> AWS<00:06:48.990> is 00:06:49.130 --> 00:06:49.140 align:start position:0% percent renewable energy and our AWS is 00:06:49.140 --> 00:06:51.470 align:start position:0% percent renewable energy and our AWS is committed<00:06:49.620> to<00:06:49.830> getting<00:06:50.760> that<00:06:50.940> to<00:06:51.120> a<00:06:51.150> hundred 00:06:51.470 --> 00:06:51.480 align:start position:0% committed to getting that to a hundred 00:06:51.480 --> 00:06:53.780 align:start position:0% committed to getting that to a hundred percent<00:06:51.950> so<00:06:52.950> that's<00:06:53.010> kind<00:06:53.250> of<00:06:53.280> a<00:06:53.370> nice<00:06:53.550> bonus 00:06:53.780 --> 00:06:53.790 align:start position:0% percent so that's kind of a nice bonus 00:06:53.790 --> 00:06:55.760 align:start position:0% percent so that's kind of a nice bonus so<00:06:54.780> I'm<00:06:54.840> going<00:06:54.960> to<00:06:55.020> talk<00:06:55.200> a<00:06:55.230> little<00:06:55.500> bit<00:06:55.650> about 00:06:55.760 --> 00:06:55.770 align:start position:0% so I'm going to talk a little bit about 00:06:55.770 --> 00:06:59.180 align:start position:0% so I'm going to talk a little bit about how<00:06:56.490> the<00:06:57.090> infrastructure<00:06:57.600> works<00:06:57.990> the<00:06:58.710> AWS 00:06:59.180 --> 00:06:59.190 align:start position:0% how the infrastructure works the AWS 00:06:59.190 --> 00:07:01.130 align:start position:0% how the infrastructure works the AWS cloud<00:06:59.520> is<00:06:59.880> divided<00:07:00.360> into<00:07:00.510> several<00:07:00.990> regions 00:07:01.130 --> 00:07:01.140 align:start position:0% cloud is divided into several regions 00:07:01.140 --> 00:07:04.240 align:start position:0% cloud is divided into several regions and<00:07:01.830> each<00:07:02.460> of<00:07:02.640> them<00:07:02.820> has<00:07:03.060> something<00:07:03.330> we<00:07:03.540> call 00:07:04.240 --> 00:07:04.250 align:start position:0% and each of them has something we call 00:07:04.250 --> 00:07:08.000 align:start position:0% and each of them has something we call availability<00:07:05.250> zones<00:07:05.520> or<00:07:05.820> AZ's<00:07:06.680> so<00:07:07.680> they<00:07:07.890> have 00:07:08.000 --> 00:07:08.010 align:start position:0% availability zones or AZ's so they have 00:07:08.010 --> 00:07:10.730 align:start position:0% availability zones or AZ's so they have several<00:07:08.280> of<00:07:08.520> these<00:07:08.669> and<00:07:08.910> these<00:07:09.510> ACS<00:07:10.140> consist 00:07:10.730 --> 00:07:10.740 align:start position:0% several of these and these ACS consist 00:07:10.740 --> 00:07:13.909 align:start position:0% several of these and these ACS consist of<00:07:10.979> one<00:07:11.729> or<00:07:11.760> more<00:07:11.960> discreet<00:07:12.960> data<00:07:13.200> centers<00:07:13.680> and 00:07:13.909 --> 00:07:13.919 align:start position:0% of one or more discreet data centers and 00:07:13.919 --> 00:07:16.159 align:start position:0% of one or more discreet data centers and they<00:07:14.490> each<00:07:14.640> have<00:07:14.669> redundant<00:07:15.540> power<00:07:15.720> and 00:07:16.159 --> 00:07:16.169 align:start position:0% they each have redundant power and 00:07:16.169 --> 00:07:17.659 align:start position:0% they each have redundant power and networking<00:07:16.620> and<00:07:16.979> they're<00:07:17.250> housed<00:07:17.460> in 00:07:17.659 --> 00:07:17.669 align:start position:0% networking and they're housed in 00:07:17.669 --> 00:07:19.550 align:start position:0% networking and they're housed in separate<00:07:18.030> facilities<00:07:18.180> that<00:07:18.870> are<00:07:19.020> unstable 00:07:19.550 --> 00:07:19.560 align:start position:0% separate facilities that are unstable 00:07:19.560 --> 00:07:22.870 align:start position:0% separate facilities that are unstable floodplains<00:07:21.290> though<00:07:22.290> they're 00:07:22.870 --> 00:07:22.880 align:start position:0% floodplains though they're 00:07:22.880 --> 00:07:25.159 align:start position:0% floodplains though they're geographically<00:07:23.880> isolated<00:07:24.060> from<00:07:24.780> each<00:07:24.840> other 00:07:25.159 --> 00:07:25.169 align:start position:0% geographically isolated from each other 00:07:25.169 --> 00:07:27.469 align:start position:0% geographically isolated from each other for<00:07:25.560> disaster<00:07:26.070> recovery<00:07:26.250> purposes<00:07:26.790> they're 00:07:27.469 --> 00:07:27.479 align:start position:0% for disaster recovery purposes they're 00:07:27.479 --> 00:07:30.380 align:start position:0% for disaster recovery purposes they're also<00:07:27.750> close<00:07:28.350> enough<00:07:28.740> that<00:07:29.550> the<00:07:29.850> pink<00:07:30.120> times 00:07:30.380 --> 00:07:30.390 align:start position:0% also close enough that the pink times 00:07:30.390 --> 00:07:34.340 align:start position:0% also close enough that the pink times between<00:07:30.630> them<00:07:31.020> are<00:07:31.200> very<00:07:31.410> low<00:07:32.090> so<00:07:33.090> the<00:07:33.840> RPC 00:07:34.340 --> 00:07:34.350 align:start position:0% between them are very low so the RPC 00:07:34.350 --> 00:07:35.630 align:start position:0% between them are very low so the RPC service<00:07:34.620> deployment<00:07:35.010> that<00:07:35.310> I'm<00:07:35.400> going<00:07:35.520> to<00:07:35.580> be 00:07:35.630 --> 00:07:35.640 align:start position:0% service deployment that I'm going to be 00:07:35.640 --> 00:07:37.610 align:start position:0% service deployment that I'm going to be showing<00:07:35.850> you<00:07:36.030> today<00:07:36.200> distributes<00:07:37.200> if<00:07:37.410> there 00:07:37.610 --> 00:07:37.620 align:start position:0% showing you today distributes if there 00:07:37.620 --> 00:07:40.040 align:start position:0% showing you today distributes if there are<00:07:37.680> M<00:07:37.740> nodes<00:07:38.010> across<00:07:38.280> different<00:07:38.820> AZ's<00:07:39.300> to 00:07:40.040 --> 00:07:40.050 align:start position:0% are M nodes across different AZ's to 00:07:40.050 --> 00:07:41.840 align:start position:0% are M nodes across different AZ's to ensure<00:07:40.440> that<00:07:40.470> the<00:07:40.860> service<00:07:41.190> continues<00:07:41.729> to 00:07:41.840 --> 00:07:41.850 align:start position:0% ensure that the service continues to 00:07:41.850 --> 00:07:44.180 align:start position:0% ensure that the service continues to function<00:07:42.060> even<00:07:42.510> if<00:07:42.810> one<00:07:43.020> of<00:07:43.169> the<00:07:43.410> AZ<00:07:43.560> suffers 00:07:44.180 --> 00:07:44.190 align:start position:0% function even if one of the AZ suffers 00:07:44.190 --> 00:07:47.659 align:start position:0% function even if one of the AZ suffers an<00:07:44.340> outage<00:07:45.140> so<00:07:46.140> I'm<00:07:46.200> going<00:07:46.320> to<00:07:46.400> go<00:07:47.400> through 00:07:47.659 --> 00:07:47.669 align:start position:0% an outage so I'm going to go through 00:07:47.669 --> 00:07:51.680 align:start position:0% an outage so I'm going to go through some<00:07:48.120> of<00:07:48.240> the<00:07:48.330> architectural<00:07:50.450> approach<00:07:51.450> to 00:07:51.680 --> 00:07:51.690 align:start position:0% some of the architectural approach to 00:07:51.690 --> 00:07:56.900 align:start position:0% some of the architectural approach to this<00:07:51.870> deployment<00:07:53.000> first<00:07:54.000> we<00:07:54.330> have<00:07:55.910> requests 00:07:56.900 --> 00:07:56.910 align:start position:0% this deployment first we have requests 00:07:56.910 --> 00:07:59.900 align:start position:0% this deployment first we have requests that<00:07:57.120> are<00:07:57.270> coming<00:07:57.600> into<00:07:57.810> the<00:07:58.729> Amazon<00:07:59.729> API 00:07:59.900 --> 00:07:59.910 align:start position:0% that are coming into the Amazon API 00:07:59.910 --> 00:08:05.029 align:start position:0% that are coming into the Amazon API gateway<00:08:00.510> and<00:08:02.810> in<00:08:03.810> you<00:08:04.140> know<00:08:04.229> this 00:08:05.029 --> 00:08:05.039 align:start position:0% gateway and in you know this 00:08:05.039 --> 00:08:07.249 align:start position:0% gateway and in you know this Gateway<00:08:05.879> checks<00:08:06.300> to<00:08:06.539> make<00:08:06.569> sure<00:08:07.020> that<00:08:07.139> the 00:08:07.249 --> 00:08:07.259 align:start position:0% Gateway checks to make sure that the 00:08:07.259 --> 00:08:10.249 align:start position:0% Gateway checks to make sure that the requests<00:08:07.710> are<00:08:07.830> recognized<00:08:08.339> and<00:08:09.300> it<00:08:09.990> blocks 00:08:10.249 --> 00:08:10.259 align:start position:0% requests are recognized and it blocks 00:08:10.259 --> 00:08:11.719 align:start position:0% requests are recognized and it blocks certain<00:08:10.589> forbidden<00:08:11.009> methods<00:08:11.400> that<00:08:11.580> are<00:08:11.699> not 00:08:11.719 --> 00:08:11.729 align:start position:0% certain forbidden methods that are not 00:08:11.729 --> 00:08:14.570 align:start position:0% certain forbidden methods that are not really<00:08:12.150> needed<00:08:12.599> for<00:08:12.629> everyday<00:08:13.110> use<00:08:13.580> that 00:08:14.570 --> 00:08:14.580 align:start position:0% really needed for everyday use that 00:08:14.580 --> 00:08:16.489 align:start position:0% really needed for everyday use that might<00:08:14.789> incur<00:08:15.240> additional<00:08:15.419> overhead<00:08:16.080> so<00:08:16.409> it 00:08:16.489 --> 00:08:16.499 align:start position:0% might incur additional overhead so it 00:08:16.499 --> 00:08:21.799 align:start position:0% might incur additional overhead so it kind<00:08:16.649> of<00:08:16.680> keeps<00:08:16.860> your<00:08:18.020> waist<00:08:19.020> down<00:08:19.909> and<00:08:20.909> then 00:08:21.799 --> 00:08:21.809 align:start position:0% kind of keeps your waist down and then 00:08:21.809 --> 00:08:24.049 align:start position:0% kind of keeps your waist down and then if<00:08:22.050> the<00:08:22.199> call<00:08:22.379> is<00:08:22.409> valid<00:08:22.979> we<00:08:23.189> pass<00:08:23.460> it<00:08:23.669> on<00:08:23.789> to<00:08:24.029> a 00:08:24.049 --> 00:08:24.059 align:start position:0% if the call is valid we pass it on to a 00:08:24.059 --> 00:08:27.049 align:start position:0% if the call is valid we pass it on to a network<00:08:24.509> load<00:08:24.779> balancer<00:08:25.259> and<00:08:25.639> that<00:08:26.639> serves 00:08:27.049 --> 00:08:27.059 align:start position:0% network load balancer and that serves 00:08:27.059 --> 00:08:29.329 align:start position:0% network load balancer and that serves the<00:08:27.300> request<00:08:27.659> to<00:08:28.409> several<00:08:28.860> container 00:08:29.329 --> 00:08:29.339 align:start position:0% the request to several container 00:08:29.339 --> 00:08:32.839 align:start position:0% the request to several container instances<00:08:30.029> and<00:08:31.099> each<00:08:32.099> of<00:08:32.279> those<00:08:32.370> container 00:08:32.839 --> 00:08:32.849 align:start position:0% instances and each of those container 00:08:32.849 --> 00:08:34.759 align:start position:0% instances and each of those container instances<00:08:33.539> is<00:08:33.779> running<00:08:34.289> in<00:08:34.380> a<00:08:34.469> separate 00:08:34.759 --> 00:08:34.769 align:start position:0% instances is running in a separate 00:08:34.769 --> 00:08:37.100 align:start position:0% instances is running in a separate availability<00:08:35.459> zone<00:08:35.669> so<00:08:36.329> in<00:08:36.449> our<00:08:36.570> experience 00:08:37.100 --> 00:08:37.110 align:start position:0% availability zone so in our experience 00:08:37.110 --> 00:08:39.829 align:start position:0% availability zone so in our experience the<00:08:37.349> primary<00:08:37.800> bottleneck<00:08:38.430> that<00:08:38.729> you<00:08:39.449> incur 00:08:39.829 --> 00:08:39.839 align:start position:0% the primary bottleneck that you incur 00:08:39.839 --> 00:08:42.409 align:start position:0% the primary bottleneck that you incur when<00:08:39.990> you<00:08:40.139> run<00:08:40.380> nodes<00:08:40.680> is<00:08:40.949> around<00:08:41.430> IO<00:08:41.699> so<00:08:42.269> these 00:08:42.409 --> 00:08:42.419 align:start position:0% when you run nodes is around IO so these 00:08:42.419 --> 00:08:45.759 align:start position:0% when you run nodes is around IO so these are<00:08:42.599> storage<00:08:42.959> optimized<00:08:43.740> I<00:08:44.069> three<00:08:44.459> instances 00:08:45.759 --> 00:08:45.769 align:start position:0% are storage optimized I three instances 00:08:45.769 --> 00:08:48.009 align:start position:0% are storage optimized I three instances they're<00:08:46.769> optimized<00:08:47.160> for<00:08:47.310> very<00:08:47.550> low<00:08:47.760> latency 00:08:48.009 --> 00:08:48.019 align:start position:0% they're optimized for very low latency 00:08:48.019 --> 00:08:51.379 align:start position:0% they're optimized for very low latency high<00:08:49.019> random<00:08:49.589> i/o<00:08:49.740> performance<00:08:50.069> and<00:08:50.699> they 00:08:51.379 --> 00:08:51.389 align:start position:0% high random i/o performance and they 00:08:51.389 --> 00:08:54.379 align:start position:0% high random i/o performance and they each<00:08:51.540> have<00:08:51.810> like<00:08:51.839> an<00:08:52.230> SSD<00:08:52.670> based<00:08:53.670> storage<00:08:53.970> that 00:08:54.379 --> 00:08:54.389 align:start position:0% each have like an SSD based storage that 00:08:54.389 --> 00:08:56.090 align:start position:0% each have like an SSD based storage that you<00:08:54.569> have<00:08:54.720> access<00:08:54.899> to<00:08:55.110> on<00:08:55.440> the<00:08:55.589> on<00:08:55.769> the 00:08:56.090 --> 00:08:56.100 align:start position:0% you have access to on the on the 00:08:56.100 --> 00:08:59.269 align:start position:0% you have access to on the on the container<00:08:57.230> so<00:08:58.230> to<00:08:58.290> optimize<00:08:58.860> the<00:08:59.100> resources 00:08:59.269 --> 00:08:59.279 align:start position:0% container so to optimize the resources 00:08:59.279 --> 00:09:02.689 align:start position:0% container so to optimize the resources we<00:08:59.970> run<00:09:00.269> several<00:09:00.990> processes<00:09:01.769> or<00:09:01.949> tasks<00:09:02.490> per 00:09:02.689 --> 00:09:02.699 align:start position:0% we run several processes or tasks per 00:09:02.699 --> 00:09:04.730 align:start position:0% we run several processes or tasks per container<00:09:03.170> depending<00:09:04.170> on<00:09:04.290> the<00:09:04.380> container 00:09:04.730 --> 00:09:04.740 align:start position:0% container depending on the container 00:09:04.740 --> 00:09:06.769 align:start position:0% container depending on the container size<00:09:05.040> and<00:09:05.399> that<00:09:05.970> technique<00:09:06.389> is<00:09:06.540> sometimes 00:09:06.769 --> 00:09:06.779 align:start position:0% size and that technique is sometimes 00:09:06.779 --> 00:09:08.750 align:start position:0% size and that technique is sometimes called<00:09:07.199> bin<00:09:07.529> packing<00:09:07.800> but<00:09:08.250> it's<00:09:08.370> the<00:09:08.490> idea 00:09:08.750 --> 00:09:08.760 align:start position:0% called bin packing but it's the idea 00:09:08.760 --> 00:09:11.120 align:start position:0% called bin packing but it's the idea that<00:09:08.819> you<00:09:09.240> know<00:09:09.720> the<00:09:09.930> container<00:09:10.649> size<00:09:10.949> you 00:09:11.120 --> 00:09:11.130 align:start position:0% that you know the container size you 00:09:11.130 --> 00:09:14.059 align:start position:0% that you know the container size you have<00:09:11.250> available<00:09:11.730> to<00:09:11.910> you<00:09:12.060> may<00:09:12.690> not<00:09:12.899> be<00:09:13.199> the 00:09:14.059 --> 00:09:14.069 align:start position:0% have available to you may not be the 00:09:14.069 --> 00:09:17.930 align:start position:0% have available to you may not be the perfect<00:09:14.720> use<00:09:15.720> of<00:09:15.990> the<00:09:16.980> resources<00:09:17.490> that<00:09:17.610> each 00:09:17.930 --> 00:09:17.940 align:start position:0% perfect use of the resources that each 00:09:17.940 --> 00:09:22.910 align:start position:0% perfect use of the resources that each node<00:09:18.420> requires<00:09:18.839> so<00:09:19.769> we<00:09:19.949> add<00:09:21.079> we<00:09:22.079> choose<00:09:22.560> how 00:09:22.910 --> 00:09:22.920 align:start position:0% node requires so we add we choose how 00:09:22.920 --> 00:09:24.740 align:start position:0% node requires so we add we choose how many<00:09:23.130> nodes<00:09:23.370> we<00:09:23.550> want<00:09:23.760> to<00:09:23.880> run<00:09:24.060> per<00:09:24.329> container 00:09:24.740 --> 00:09:24.750 align:start position:0% many nodes we want to run per container 00:09:24.750 --> 00:09:27.410 align:start position:0% many nodes we want to run per container and<00:09:25.100> these<00:09:26.100> ratios<00:09:26.610> that<00:09:26.639> I've<00:09:26.940> listed<00:09:27.149> up 00:09:27.410 --> 00:09:27.420 align:start position:0% and these ratios that I've listed up 00:09:27.420 --> 00:09:32.230 align:start position:0% and these ratios that I've listed up here<00:09:27.449> are<00:09:29.389> you<00:09:30.389> know<00:09:30.480> in<00:09:30.720> our<00:09:30.810> latest<00:09:31.199> testing 00:09:32.230 --> 00:09:32.240 align:start position:0% here are you know in our latest testing 00:09:32.240 --> 00:09:34.460 align:start position:0% here are you know in our latest testing these<00:09:33.240> are<00:09:33.449> the<00:09:33.540> ones<00:09:33.720> we<00:09:33.839> recommend<00:09:34.290> at<00:09:34.380> the 00:09:34.460 --> 00:09:34.470 align:start position:0% these are the ones we recommend at the 00:09:34.470 --> 00:09:37.639 align:start position:0% these are the ones we recommend at the moment<00:09:34.889> but<00:09:35.279> they<00:09:35.519> could<00:09:35.760> change<00:09:36.120> as<00:09:36.649> block 00:09:37.639 --> 00:09:37.649 align:start position:0% moment but they could change as block 00:09:37.649 --> 00:09:41.269 align:start position:0% moment but they could change as block chain<00:09:38.300> sizes<00:09:39.300> increase<00:09:39.870> or<00:09:40.170> change<00:09:40.199> so<00:09:40.860> or<00:09:41.220> you 00:09:41.269 --> 00:09:41.279 align:start position:0% chain sizes increase or change so or you 00:09:41.279 --> 00:09:43.460 align:start position:0% chain sizes increase or change so or you know<00:09:41.579> if<00:09:41.819> the<00:09:42.000> efficiency<00:09:42.540> of<00:09:42.569> blockchain 00:09:43.460 --> 00:09:43.470 align:start position:0% know if the efficiency of blockchain 00:09:43.470 --> 00:09:48.079 align:start position:0% know if the efficiency of blockchain storage<00:09:43.800> changes<00:09:45.649> so<00:09:46.649> one<00:09:47.430> particular 00:09:48.079 --> 00:09:48.089 align:start position:0% storage changes so one particular 00:09:48.089 --> 00:09:51.860 align:start position:0% storage changes so one particular challenge<00:09:48.360> that<00:09:49.050> we<00:09:49.170> ran<00:09:49.380> into<00:09:49.589> is<00:09:50.600> how<00:09:51.600> to<00:09:51.660> get 00:09:51.860 --> 00:09:51.870 align:start position:0% challenge that we ran into is how to get 00:09:51.870 --> 00:09:54.379 align:start position:0% challenge that we ran into is how to get around<00:09:52.139> the<00:09:52.500> incredibly<00:09:53.220> long<00:09:53.459> sink<00:09:54.029> times 00:09:54.379 --> 00:09:54.389 align:start position:0% around the incredibly long sink times 00:09:54.389 --> 00:09:57.410 align:start position:0% around the incredibly long sink times for<00:09:54.899> new<00:09:55.110> nodes<00:09:55.380> so<00:09:56.310> if<00:09:56.639> one<00:09:57.000> of<00:09:57.120> our<00:09:57.240> nodes 00:09:57.410 --> 00:09:57.420 align:start position:0% for new nodes so if one of our nodes 00:09:57.420 --> 00:09:59.509 align:start position:0% for new nodes so if one of our nodes becomes<00:09:57.870> unhealthy<00:09:58.199> we<00:09:59.010> want<00:09:59.220> to<00:09:59.279> be<00:09:59.339> able<00:09:59.430> to 00:09:59.509 --> 00:09:59.519 align:start position:0% becomes unhealthy we want to be able to 00:09:59.519 --> 00:10:02.449 align:start position:0% becomes unhealthy we want to be able to start<00:09:59.819> up<00:09:59.910> another<00:10:00.180> node<00:10:00.540> quickly<00:10:01.110> and<00:10:01.459> with 00:10:02.449 --> 00:10:02.459 align:start position:0% start up another node quickly and with 00:10:02.459 --> 00:10:05.389 align:start position:0% start up another node quickly and with death<00:10:02.790> taking<00:10:03.420> several<00:10:03.870> hours<00:10:04.410> like<00:10:04.920> almost<00:10:05.220> a 00:10:05.389 --> 00:10:05.399 align:start position:0% death taking several hours like almost a 00:10:05.399 --> 00:10:08.750 align:start position:0% death taking several hours like almost a day<00:10:05.610> to<00:10:06.180> sink<00:10:06.480> a<00:10:06.660> new<00:10:06.930> blockchain<00:10:07.440> and<00:10:07.760> parity 00:10:08.750 --> 00:10:08.760 align:start position:0% day to sink a new blockchain and parity 00:10:08.760 --> 00:10:11.930 align:start position:0% day to sink a new blockchain and parity taking<00:10:09.149> several<00:10:09.480> days<00:10:10.310> we<00:10:11.310> needed<00:10:11.639> a<00:10:11.730> better 00:10:11.930 --> 00:10:11.940 align:start position:0% taking several days we needed a better 00:10:11.940 --> 00:10:14.210 align:start position:0% taking several days we needed a better strategy<00:10:12.630> than<00:10:12.660> just<00:10:13.470> starting<00:10:13.740> our<00:10:13.980> nodes 00:10:14.210 --> 00:10:14.220 align:start position:0% strategy than just starting our nodes 00:10:14.220 --> 00:10:15.740 align:start position:0% strategy than just starting our nodes from<00:10:14.370> scratch<00:10:14.730> and<00:10:15.029> having<00:10:15.269> them<00:10:15.389> sync<00:10:15.630> with 00:10:15.740 --> 00:10:15.750 align:start position:0% from scratch and having them sync with 00:10:15.750 --> 00:10:16.250 align:start position:0% from scratch and having them sync with the<00:10:15.810> blockchain 00:10:16.250 --> 00:10:16.260 align:start position:0% the blockchain 00:10:16.260 --> 00:10:18.620 align:start position:0% the blockchain so<00:10:16.920> we<00:10:17.100> created<00:10:17.430> a<00:10:17.610> special<00:10:17.730> task 00:10:18.620 --> 00:10:18.630 align:start position:0% so we created a special task 00:10:18.630 --> 00:10:21.020 align:start position:0% so we created a special task on<00:10:18.720> one<00:10:19.650> container<00:10:20.160> that<00:10:20.430> we<00:10:20.550> call<00:10:20.790> the 00:10:21.020 --> 00:10:21.030 align:start position:0% on one container that we call the 00:10:21.030 --> 00:10:23.510 align:start position:0% on one container that we call the updater<00:10:21.660> task<00:10:22.050> it's<00:10:22.860> down<00:10:23.010> in<00:10:23.130> the<00:10:23.220> corner 00:10:23.510 --> 00:10:23.520 align:start position:0% updater task it's down in the corner 00:10:23.520 --> 00:10:27.320 align:start position:0% updater task it's down in the corner there<00:10:23.700> and<00:10:24.980> this<00:10:25.980> task<00:10:26.280> runs<00:10:26.640> a<00:10:26.790> node<00:10:27.030> that's 00:10:27.320 --> 00:10:27.330 align:start position:0% there and this task runs a node that's 00:10:27.330 --> 00:10:29.810 align:start position:0% there and this task runs a node that's periodically<00:10:28.110> taken<00:10:28.680> offline<00:10:28.980> every<00:10:29.610> four 00:10:29.810 --> 00:10:29.820 align:start position:0% periodically taken offline every four 00:10:29.820 --> 00:10:33.200 align:start position:0% periodically taken offline every four hours<00:10:29.850> or<00:10:30.240> so<00:10:30.420> and<00:10:30.690> copied<00:10:31.080> the<00:10:31.170> s3<00:10:31.680> and<00:10:32.210> when 00:10:33.200 --> 00:10:33.210 align:start position:0% hours or so and copied the s3 and when 00:10:33.210 --> 00:10:35.960 align:start position:0% hours or so and copied the s3 and when you<00:10:33.300> copy<00:10:33.630> within<00:10:34.440> the<00:10:34.530> same<00:10:34.740> region<00:10:34.950> to<00:10:35.280> s3<00:10:35.430> it 00:10:35.960 --> 00:10:35.970 align:start position:0% you copy within the same region to s3 it 00:10:35.970 --> 00:10:38.570 align:start position:0% you copy within the same region to s3 it doesn't<00:10:36.300> cost<00:10:36.510> any<00:10:37.380> you<00:10:37.980> don't<00:10:38.160> incur<00:10:38.400> any 00:10:38.570 --> 00:10:38.580 align:start position:0% doesn't cost any you don't incur any 00:10:38.580 --> 00:10:42.140 align:start position:0% doesn't cost any you don't incur any bandwidth<00:10:38.970> charges<00:10:39.740> so<00:10:40.740> when<00:10:41.700> new<00:10:41.940> nodes 00:10:42.140 --> 00:10:42.150 align:start position:0% bandwidth charges so when new nodes 00:10:42.150 --> 00:10:43.850 align:start position:0% bandwidth charges so when new nodes start<00:10:42.510> up<00:10:42.660> they<00:10:42.840> copy<00:10:43.110> the<00:10:43.230> contents<00:10:43.710> of<00:10:43.770> the 00:10:43.850 --> 00:10:43.860 align:start position:0% start up they copy the contents of the 00:10:43.860 --> 00:10:45.470 align:start position:0% start up they copy the contents of the blockchain<00:10:44.070> state<00:10:44.490> from<00:10:44.640> that<00:10:44.700> same<00:10:45.060> s3 00:10:45.470 --> 00:10:45.480 align:start position:0% blockchain state from that same s3 00:10:45.480 --> 00:10:47.780 align:start position:0% blockchain state from that same s3 bucket<00:10:45.840> to<00:10:46.410> their<00:10:46.560> local<00:10:46.890> disk<00:10:47.130> before<00:10:47.520> they 00:10:47.780 --> 00:10:47.790 align:start position:0% bucket to their local disk before they 00:10:47.790 --> 00:10:50.570 align:start position:0% bucket to their local disk before they begin<00:10:48.060> and<00:10:48.300> then<00:10:49.080> this<00:10:49.560> you<00:10:50.010> know<00:10:50.100> enables 00:10:50.570 --> 00:10:50.580 align:start position:0% begin and then this you know enables 00:10:50.580 --> 00:10:52.310 align:start position:0% begin and then this you know enables them<00:10:50.760> to<00:10:50.790> start<00:10:51.180> up<00:10:51.330> within<00:10:51.510> a<00:10:51.660> few<00:10:51.840> minutes<00:10:52.170> if 00:10:52.310 --> 00:10:52.320 align:start position:0% them to start up within a few minutes if 00:10:52.320 --> 00:10:53.960 align:start position:0% them to start up within a few minutes if we're<00:10:52.500> lucky<00:10:52.710> it'll<00:10:53.070> be<00:10:53.340> like<00:10:53.730> actually 00:10:53.960 --> 00:10:53.970 align:start position:0% we're lucky it'll be like actually 00:10:53.970 --> 00:10:58.040 align:start position:0% we're lucky it'll be like actually running<00:10:54.540> by<00:10:54.660> the<00:10:54.720> end<00:10:54.810> of<00:10:54.960> my<00:10:55.080> talk<00:10:55.320> here<00:10:57.050> so 00:10:58.040 --> 00:10:58.050 align:start position:0% running by the end of my talk here so 00:10:58.050 --> 00:11:01.670 align:start position:0% running by the end of my talk here so let's<00:10:58.830> take<00:10:59.040> a<00:10:59.070> look<00:10:59.340> then<00:10:59.700> at<00:10:59.940> the<00:11:00.440> code<00:11:01.440> for 00:11:01.670 --> 00:11:01.680 align:start position:0% let's take a look then at the code for 00:11:01.680 --> 00:11:09.800 align:start position:0% let's take a look then at the code for just<00:11:01.860> a<00:11:01.920> sec<00:11:07.220> so<00:11:08.220> I've<00:11:08.310> got<00:11:08.460> the<00:11:08.670> repo<00:11:09.330> right 00:11:09.800 --> 00:11:09.810 align:start position:0% just a sec so I've got the repo right 00:11:09.810 --> 00:11:13.400 align:start position:0% just a sec so I've got the repo right here<00:11:10.640> for<00:11:11.640> those<00:11:11.760> of<00:11:11.910> you<00:11:12.060> who<00:11:12.420> I'll<00:11:13.050> leave<00:11:13.290> it 00:11:13.400 --> 00:11:13.410 align:start position:0% here for those of you who I'll leave it 00:11:13.410 --> 00:11:14.780 align:start position:0% here for those of you who I'll leave it there<00:11:13.440> for<00:11:13.710> just<00:11:13.860> a<00:11:13.920> second<00:11:14.250> longer<00:11:14.550> for<00:11:14.730> those 00:11:14.780 --> 00:11:14.790 align:start position:0% there for just a second longer for those 00:11:14.790 --> 00:11:17.120 align:start position:0% there for just a second longer for those of<00:11:14.910> you<00:11:15.000> who<00:11:15.120> want<00:11:15.330> the<00:11:15.450> link<00:11:15.830> of<00:11:16.830> course<00:11:17.040> this 00:11:17.120 --> 00:11:17.130 align:start position:0% of you who want the link of course this 00:11:17.130 --> 00:11:23.690 align:start position:0% of you who want the link of course this would<00:11:17.250> be<00:11:17.370> published<00:11:17.700> later<00:11:19.190> and<00:11:21.830> in<00:11:22.830> here<00:11:23.250> you 00:11:23.690 --> 00:11:23.700 align:start position:0% would be published later and in here you 00:11:23.700 --> 00:11:26.330 align:start position:0% would be published later and in here you know<00:11:23.790> I'm<00:11:24.060> a<00:11:24.420> strong<00:11:24.690> believer<00:11:24.870> in<00:11:25.380> a<00:11:25.740> project 00:11:26.330 --> 00:11:26.340 align:start position:0% know I'm a strong believer in a project 00:11:26.340 --> 00:11:28.130 align:start position:0% know I'm a strong believer in a project having<00:11:26.580> all<00:11:26.970> the<00:11:27.210> information<00:11:27.240> that<00:11:27.990> it<00:11:28.110> needs 00:11:28.130 --> 00:11:28.140 align:start position:0% having all the information that it needs 00:11:28.140 --> 00:11:31.190 align:start position:0% having all the information that it needs and<00:11:28.650> it's<00:11:28.770> read<00:11:29.040> me<00:11:29.220> to<00:11:30.210> be<00:11:30.330> able<00:11:30.420> to<00:11:30.570> reproduce 00:11:31.190 --> 00:11:31.200 align:start position:0% and it's read me to be able to reproduce 00:11:31.200 --> 00:11:34.130 align:start position:0% and it's read me to be able to reproduce it<00:11:31.710> and<00:11:31.740> run<00:11:32.010> it<00:11:32.040> and<00:11:32.280> execute<00:11:32.520> it<00:11:32.990> sometime<00:11:33.990> I 00:11:34.130 --> 00:11:34.140 align:start position:0% it and run it and execute it sometime I 00:11:34.140 --> 00:11:36.020 align:start position:0% it and run it and execute it sometime I think<00:11:34.350> Chris<00:11:34.590> landstrass<00:11:35.190> one<00:11:35.730> of<00:11:35.820> the<00:11:35.880> github 00:11:36.020 --> 00:11:36.030 align:start position:0% think Chris landstrass one of the github 00:11:36.030 --> 00:11:38.060 align:start position:0% think Chris landstrass one of the github founders<00:11:36.570> called<00:11:36.840> this<00:11:37.020> readme<00:11:37.710> driven 00:11:38.060 --> 00:11:38.070 align:start position:0% founders called this readme driven 00:11:38.070 --> 00:11:41.480 align:start position:0% founders called this readme driven development<00:11:39.110> but<00:11:40.110> anyway<00:11:40.440> I<00:11:40.650> think<00:11:41.010> this<00:11:41.310> is 00:11:41.480 --> 00:11:41.490 align:start position:0% development but anyway I think this is 00:11:41.490 --> 00:11:43.250 align:start position:0% development but anyway I think this is important<00:11:41.970> so<00:11:42.150> hopefully<00:11:42.720> everything<00:11:43.020> you 00:11:43.250 --> 00:11:43.260 align:start position:0% important so hopefully everything you 00:11:43.260 --> 00:11:46.760 align:start position:0% important so hopefully everything you need<00:11:43.440> to<00:11:44.220> be<00:11:44.310> able<00:11:44.370> to<00:11:44.520> run<00:11:44.640> this<00:11:44.820> is<00:11:45.030> there<00:11:45.770> and 00:11:46.760 --> 00:11:46.770 align:start position:0% need to be able to run this is there and 00:11:46.770 --> 00:11:51.410 align:start position:0% need to be able to run this is there and I'm<00:11:47.370> gonna<00:11:47.490> just<00:11:48.000> bounce<00:11:48.210> over<00:11:48.780> to<00:11:49.050> my<00:11:50.420> AWS 00:11:51.410 --> 00:11:51.420 align:start position:0% I'm gonna just bounce over to my AWS 00:11:51.420 --> 00:11:53.630 align:start position:0% I'm gonna just bounce over to my AWS management<00:11:51.630> console<00:11:52.350> to<00:11:52.590> just<00:11:52.800> see<00:11:53.010> what<00:11:53.490> the 00:11:53.630 --> 00:11:53.640 align:start position:0% management console to just see what the 00:11:53.640 --> 00:11:59.630 align:start position:0% management console to just see what the state<00:11:53.850> of<00:11:53.910> this<00:11:54.180> thing<00:11:54.390> is<00:11:54.570> going<00:11:54.780> so<00:11:58.640> we 00:11:59.630 --> 00:11:59.640 align:start position:0% state of this thing is going so we 00:11:59.640 --> 00:12:06.620 align:start position:0% state of this thing is going so we launched<00:11:59.970> this<00:12:00.180> additional<00:12:00.840> stack<00:12:03.710> and<00:12:05.630> it 00:12:06.620 --> 00:12:06.630 align:start position:0% launched this additional stack and it 00:12:06.630 --> 00:12:12.620 align:start position:0% launched this additional stack and it looks<00:12:06.900> like<00:12:07.760> the<00:12:10.790> connection<00:12:11.790> is<00:12:11.970> so<00:12:12.270> slow 00:12:12.620 --> 00:12:12.630 align:start position:0% looks like the connection is so slow 00:12:12.630 --> 00:12:15.530 align:start position:0% looks like the connection is so slow that<00:12:12.660> it<00:12:13.290> hasn't<00:12:13.530> even<00:12:13.770> fully<00:12:14.300> kicked<00:12:15.300> off 00:12:15.530 --> 00:12:15.540 align:start position:0% that it hasn't even fully kicked off 00:12:15.540 --> 00:12:18.160 align:start position:0% that it hasn't even fully kicked off here<00:12:15.780> yet<00:12:15.960> so<00:12:16.140> it's<00:12:16.320> probably<00:12:16.380> not<00:12:16.920> going<00:12:17.190> to 00:12:18.160 --> 00:12:18.170 align:start position:0% here yet so it's probably not going to 00:12:18.170 --> 00:12:21.530 align:start position:0% here yet so it's probably not going to be<00:12:19.170> finished<00:12:19.590> by<00:12:19.710> the<00:12:19.830> time<00:12:19.950> that<00:12:20.550> I'm<00:12:20.790> done<00:12:21.060> so 00:12:21.530 --> 00:12:21.540 align:start position:0% be finished by the time that I'm done so 00:12:21.540 --> 00:12:24.980 align:start position:0% be finished by the time that I'm done so for<00:12:21.840> that<00:12:21.960> purpose<00:12:22.500> I<00:12:22.740> prepared<00:12:23.280> a<00:12:23.370> video<00:12:23.990> just 00:12:24.980 --> 00:12:24.990 align:start position:0% for that purpose I prepared a video just 00:12:24.990 --> 00:12:26.990 align:start position:0% for that purpose I prepared a video just in<00:12:25.140> case<00:12:25.350> this<00:12:25.620> hat<00:12:25.860> was<00:12:26.340> going<00:12:26.550> to<00:12:26.670> happen 00:12:26.990 --> 00:12:27.000 align:start position:0% in case this hat was going to happen 00:12:27.000 --> 00:12:29.060 align:start position:0% in case this hat was going to happen right<00:12:27.150> I<00:12:27.210> kind<00:12:27.510> of<00:12:27.570> had<00:12:28.020> this<00:12:28.200> feeling<00:12:28.800> last 00:12:29.060 --> 00:12:29.070 align:start position:0% right I kind of had this feeling last 00:12:29.070 --> 00:12:31.940 align:start position:0% right I kind of had this feeling last night<00:12:29.220> that<00:12:29.700> I<00:12:29.970> might<00:12:30.690> run<00:12:30.839> into<00:12:31.020> this 00:12:31.940 --> 00:12:31.950 align:start position:0% night that I might run into this 00:12:31.950 --> 00:12:37.069 align:start position:0% night that I might run into this i<00:12:32.360> tempted<00:12:33.360> the<00:12:33.779> demo<00:12:34.110> gods<00:12:34.350> right<00:12:34.970> so<00:12:36.079> I'm 00:12:37.069 --> 00:12:37.079 align:start position:0% i tempted the demo gods right so I'm 00:12:37.079 --> 00:12:38.990 align:start position:0% i tempted the demo gods right so I'm going<00:12:37.200> to<00:12:37.260> bounce<00:12:37.470> over<00:12:37.709> to<00:12:38.339> kind<00:12:38.579> of<00:12:38.610> what<00:12:38.850> you 00:12:38.990 --> 00:12:39.000 align:start position:0% going to bounce over to kind of what you 00:12:39.000 --> 00:12:41.120 align:start position:0% going to bounce over to kind of what you would<00:12:39.149> see<00:12:39.209> as<00:12:39.959> this<00:12:40.260> progresses<00:12:40.470> a<00:12:40.800> little 00:12:41.120 --> 00:12:41.130 align:start position:0% would see as this progresses a little 00:12:41.130 --> 00:12:44.960 align:start position:0% would see as this progresses a little further<00:12:41.370> along<00:12:42.769> so<00:12:43.769> that<00:12:43.950> kicks<00:12:44.279> off<00:12:44.519> this 00:12:44.960 --> 00:12:44.970 align:start position:0% further along so that kicks off this 00:12:44.970 --> 00:12:47.449 align:start position:0% further along so that kicks off this CloudFormation<00:12:45.839> template<00:12:46.620> and<00:12:46.829> you<00:12:47.040> get<00:12:47.250> this 00:12:47.449 --> 00:12:47.459 align:start position:0% CloudFormation template and you get this 00:12:47.459 --> 00:12:49.519 align:start position:0% CloudFormation template and you get this result<00:12:48.329> saying<00:12:48.660> okay<00:12:48.930> we've<00:12:49.079> just<00:12:49.110> started 00:12:49.519 --> 00:12:49.529 align:start position:0% result saying okay we've just started 00:12:49.529 --> 00:12:54.019 align:start position:0% result saying okay we've just started this<00:12:49.860> and<00:12:51.740> I've<00:12:52.740> got<00:12:53.010> it<00:12:53.160> serviced<00:12:53.760> that's 00:12:54.019 --> 00:12:54.029 align:start position:0% this and I've got it serviced that's 00:12:54.029 --> 00:12:57.139 align:start position:0% this and I've got it serviced that's I've<00:12:54.180> already<00:12:54.779> pre<00:12:55.050> deployed<00:12:55.880> that<00:12:56.880> we<00:12:56.970> can 00:12:57.139 --> 00:12:57.149 align:start position:0% I've already pre deployed that we can 00:12:57.149 --> 00:12:59.990 align:start position:0% I've already pre deployed that we can actually<00:12:57.329> test<00:12:57.750> against<00:12:58.139> so<00:12:58.790> we're<00:12:59.790> seeing 00:12:59.990 --> 00:13:00.000 align:start position:0% actually test against so we're seeing 00:13:00.000 --> 00:13:03.560 align:start position:0% actually test against so we're seeing some<00:13:00.120> of<00:13:00.690> the<00:13:01.050> RPC<00:13:01.769> calls<00:13:02.250> now<00:13:02.579> going<00:13:02.970> out<00:13:03.120> to 00:13:03.560 --> 00:13:03.570 align:start position:0% some of the RPC calls now going out to 00:13:03.570 --> 00:13:07.340 align:start position:0% some of the RPC calls now going out to this<00:13:04.279> node<00:13:05.279> cluster<00:13:05.579> and<00:13:06.170> they're<00:13:07.170> being 00:13:07.340 --> 00:13:07.350 align:start position:0% this node cluster and they're being 00:13:07.350 --> 00:13:10.939 align:start position:0% this node cluster and they're being responded<00:13:08.269> successfully<00:13:09.269> and<00:13:09.920> because<00:13:10.920> I 00:13:10.939 --> 00:13:10.949 align:start position:0% responded successfully and because I 00:13:10.949 --> 00:13:12.800 align:start position:0% responded successfully and because I have<00:13:11.250> another<00:13:11.730> node<00:13:11.970> cluster<00:13:12.209> running 00:13:12.800 --> 00:13:12.810 align:start position:0% have another node cluster running 00:13:12.810 --> 00:13:16.550 align:start position:0% have another node cluster running already<00:13:13.399> I<00:13:14.399> can<00:13:14.820> actually<00:13:15.060> do<00:13:15.899> that<00:13:16.079> as<00:13:16.350> well 00:13:16.550 --> 00:13:16.560 align:start position:0% already I can actually do that as well 00:13:16.560 --> 00:13:26.060 align:start position:0% already I can actually do that as well so<00:13:17.269> if<00:13:18.269> I<00:13:18.510> want<00:13:18.750> to<00:13:18.959> for<00:13:19.290> example<00:13:19.320> I<00:13:24.829> first<00:13:25.829> need 00:13:26.060 --> 00:13:26.070 align:start position:0% so if I want to for example I first need 00:13:26.070 --> 00:13:30.410 align:start position:0% so if I want to for example I first need to<00:13:26.100> go<00:13:26.579> to<00:13:26.639> my<00:13:26.850> API<00:13:27.269> gateway<00:13:27.750> and<00:13:29.240> find<00:13:30.240> out 00:13:30.410 --> 00:13:30.420 align:start position:0% to go to my API gateway and find out 00:13:30.420 --> 00:13:35.300 align:start position:0% to go to my API gateway and find out what<00:13:30.720> the<00:13:30.959> URL<00:13:31.889> of<00:13:32.130> my<00:13:32.389> service<00:13:33.389> is<00:13:34.190> so<00:13:35.190> we'll 00:13:35.300 --> 00:13:35.310 align:start position:0% what the URL of my service is so we'll 00:13:35.310 --> 00:14:00.490 align:start position:0% what the URL of my service is so we'll do<00:13:35.459> that 00:14:00.490 --> 00:14:00.500 align:start position:0% 00:14:00.500 --> 00:14:05.390 align:start position:0% so<00:14:01.500> while<00:14:02.400> this<00:14:02.550> is<00:14:02.760> loading<00:14:03.000> very<00:14:03.900> slowly<00:14:04.400> I 00:14:05.390 --> 00:14:05.400 align:start position:0% so while this is loading very slowly I 00:14:05.400 --> 00:14:09.950 align:start position:0% so while this is loading very slowly I can<00:14:06.330> take<00:14:06.510> you<00:14:06.630> through<00:14:06.980> some<00:14:07.980> of<00:14:08.040> the<00:14:08.960> things 00:14:09.950 --> 00:14:09.960 align:start position:0% can take you through some of the things 00:14:09.960 --> 00:14:11.630 align:start position:0% can take you through some of the things that<00:14:10.200> we're<00:14:10.440> still<00:14:10.650> working<00:14:10.680> on<00:14:11.010> this<00:14:11.220> so<00:14:11.520> this 00:14:11.630 --> 00:14:11.640 align:start position:0% that we're still working on this so this 00:14:11.640 --> 00:14:14.000 align:start position:0% that we're still working on this so this right<00:14:11.910> now<00:14:12.180> supports<00:14:12.840> the<00:14:13.230> parody<00:14:13.620> client 00:14:14.000 --> 00:14:14.010 align:start position:0% right now supports the parody client 00:14:14.010 --> 00:14:16.160 align:start position:0% right now supports the parody client that<00:14:14.490> was<00:14:14.640> one<00:14:15.210> of<00:14:15.330> the<00:14:15.480> you<00:14:15.720> know<00:14:15.810> at<00:14:15.900> the<00:14:15.960> time 00:14:16.160 --> 00:14:16.170 align:start position:0% that was one of the you know at the time 00:14:16.170 --> 00:14:19.160 align:start position:0% that was one of the you know at the time we<00:14:16.350> first<00:14:16.620> developed<00:14:17.070> this<00:14:17.240> parody<00:14:18.240> was<00:14:18.630> a 00:14:19.160 --> 00:14:19.170 align:start position:0% we first developed this parody was a 00:14:19.170 --> 00:14:21.050 align:start position:0% we first developed this parody was a little<00:14:19.590> more<00:14:19.740> stable<00:14:20.010> so<00:14:20.490> that<00:14:20.700> was<00:14:20.850> what<00:14:20.970> we 00:14:21.050 --> 00:14:21.060 align:start position:0% little more stable so that was what we 00:14:21.060 --> 00:14:24.880 align:start position:0% little more stable so that was what we were<00:14:21.150> focusing<00:14:21.510> on<00:14:21.770> and<00:14:22.770> I<00:14:22.830> am<00:14:23.550> very<00:14:24.120> close<00:14:24.510> to 00:14:24.880 --> 00:14:24.890 align:start position:0% were focusing on and I am very close to 00:14:24.890 --> 00:14:28.640 align:start position:0% were focusing on and I am very close to releasing<00:14:25.890> to<00:14:26.850> merging<00:14:27.480> in<00:14:27.630> a<00:14:27.720> PR<00:14:27.960> that<00:14:28.380> will 00:14:28.640 --> 00:14:28.650 align:start position:0% releasing to merging in a PR that will 00:14:28.650 --> 00:14:32.690 align:start position:0% releasing to merging in a PR that will support<00:14:29.310> death<00:14:29.640> as<00:14:29.880> well<00:14:31.220> but<00:14:32.220> it's<00:14:32.340> actually 00:14:32.690 --> 00:14:32.700 align:start position:0% support death as well but it's actually 00:14:32.700 --> 00:14:35.090 align:start position:0% support death as well but it's actually pretty<00:14:32.940> easy<00:14:33.060> because<00:14:33.690> of<00:14:34.440> our<00:14:34.680> approach<00:14:35.070> of 00:14:35.090 --> 00:14:35.100 align:start position:0% pretty easy because of our approach of 00:14:35.100 --> 00:14:39.710 align:start position:0% pretty easy because of our approach of just<00:14:35.280> kind<00:14:35.640> of<00:14:35.700> copying<00:14:36.210> the<00:14:37.520> contents<00:14:38.520> of<00:14:38.720> the 00:14:39.710 --> 00:14:39.720 align:start position:0% just kind of copying the contents of the 00:14:39.720 --> 00:14:43.670 align:start position:0% just kind of copying the contents of the blockchain<00:14:40.200> state<00:14:40.800> off<00:14:41.180> disk<00:14:42.180> and<00:14:43.020> syncing<00:14:43.560> it 00:14:43.670 --> 00:14:43.680 align:start position:0% blockchain state off disk and syncing it 00:14:43.680 --> 00:14:46.190 align:start position:0% blockchain state off disk and syncing it with<00:14:43.800> s3<00:14:44.250> it's<00:14:44.760> very<00:14:45.030> easy<00:14:45.330> for<00:14:45.630> us<00:14:45.690> to<00:14:45.810> kind<00:14:46.140> of 00:14:46.190 --> 00:14:46.200 align:start position:0% with s3 it's very easy for us to kind of 00:14:46.200 --> 00:14:51.310 align:start position:0% with s3 it's very easy for us to kind of support<00:14:46.890> whatever<00:14:48.410> node<00:14:49.640> service<00:14:50.640> we<00:14:50.910> want<00:14:51.120> to 00:14:51.310 --> 00:14:51.320 align:start position:0% support whatever node service we want to 00:14:51.320 --> 00:14:54.740 align:start position:0% support whatever node service we want to so<00:14:52.320> as<00:14:52.500> you<00:14:52.950> know<00:14:53.070> eath<00:14:53.280> 2.0<00:14:53.850> comes<00:14:54.120> online<00:14:54.330> and 00:14:54.740 --> 00:14:54.750 align:start position:0% so as you know eath 2.0 comes online and 00:14:54.750 --> 00:14:58.010 align:start position:0% so as you know eath 2.0 comes online and a<00:14:54.810> lot<00:14:54.960> of<00:14:54.990> new<00:14:56.120> EVM<00:14:57.120> implementations<00:14:57.900> are 00:14:58.010 --> 00:14:58.020 align:start position:0% a lot of new EVM implementations are 00:14:58.020 --> 00:15:03.290 align:start position:0% a lot of new EVM implementations are coming<00:14:58.290> out<00:14:58.440> this<00:14:58.620> shouldn't<00:14:58.920> be<00:14:58.980> too<00:14:59.070> hard<00:15:02.300> so 00:15:03.290 --> 00:15:03.300 align:start position:0% coming out this shouldn't be too hard so 00:15:03.300 --> 00:15:18.710 align:start position:0% coming out this shouldn't be too hard so let's<00:15:03.780> see 00:15:18.710 --> 00:15:18.720 align:start position:0% 00:15:18.720 --> 00:16:02.780 align:start position:0% alright<00:15:19.380> so<00:15:19.530> got<00:15:19.740> that<00:15:19.800> URL 00:16:02.780 --> 00:16:02.790 align:start position:0% 00:16:02.790 --> 00:16:05.780 align:start position:0% and<00:16:03.180> we<00:16:04.020> get<00:16:04.230> a<00:16:04.470> successful<00:16:05.160> result<00:16:05.310> very 00:16:05.780 --> 00:16:05.790 align:start position:0% and we get a successful result very 00:16:05.790 --> 00:16:07.760 align:start position:0% and we get a successful result very slowly<00:16:06.120> because<00:16:06.480> of<00:16:06.660> the<00:16:06.810> network<00:16:07.140> it's<00:16:07.410> it's 00:16:07.760 --> 00:16:07.770 align:start position:0% slowly because of the network it's it's 00:16:07.770 --> 00:16:13.010 align:start position:0% slowly because of the network it's it's not<00:16:07.890> the<00:16:07.950> service<00:16:08.400> I<00:16:08.520> promise<00:16:10.190> anyway<00:16:11.300> so<00:16:12.300> this 00:16:13.010 --> 00:16:13.020 align:start position:0% not the service I promise anyway so this 00:16:13.020 --> 00:16:16.420 align:start position:0% not the service I promise anyway so this is<00:16:13.610> this<00:16:14.610> has<00:16:14.760> been<00:16:14.790> a<00:16:15.000> very<00:16:15.350> stable 00:16:16.420 --> 00:16:16.430 align:start position:0% is this has been a very stable 00:16:16.430 --> 00:16:19.250 align:start position:0% is this has been a very stable successful<00:16:17.430> deployment<00:16:18.210> that's<00:16:18.630> been 00:16:19.250 --> 00:16:19.260 align:start position:0% successful deployment that's been 00:16:19.260 --> 00:16:22.010 align:start position:0% successful deployment that's been running<00:16:19.620> for<00:16:19.890> some<00:16:20.400> of<00:16:20.490> those<00:16:20.840> companies<00:16:21.840> that 00:16:22.010 --> 00:16:22.020 align:start position:0% running for some of those companies that 00:16:22.020 --> 00:16:24.260 align:start position:0% running for some of those companies that I<00:16:22.200> mentioned<00:16:22.560> earlier<00:16:22.650> for<00:16:23.100> quite<00:16:23.790> some<00:16:24.030> time 00:16:24.260 --> 00:16:24.270 align:start position:0% I mentioned earlier for quite some time 00:16:24.270 --> 00:16:27.200 align:start position:0% I mentioned earlier for quite some time we<00:16:25.050> continue<00:16:25.530> to<00:16:25.710> maintain<00:16:25.890> the<00:16:26.460> tezo's 00:16:27.200 --> 00:16:27.210 align:start position:0% we continue to maintain the tezo's 00:16:27.210 --> 00:16:28.850 align:start position:0% we continue to maintain the tezo's foundations<00:16:27.750> note<00:16:27.990> infrastructure<00:16:28.590> in<00:16:28.740> the 00:16:28.850 --> 00:16:28.860 align:start position:0% foundations note infrastructure in the 00:16:28.860 --> 00:16:32.600 align:start position:0% foundations note infrastructure in the similar<00:16:29.160> way<00:16:29.630> and<00:16:31.130> happy<00:16:32.130> to<00:16:32.370> answer 00:16:32.600 --> 00:16:32.610 align:start position:0% similar way and happy to answer 00:16:32.610 --> 00:16:34.850 align:start position:0% similar way and happy to answer questions<00:16:33.180> about<00:16:33.330> how<00:16:33.630> we<00:16:33.690> did<00:16:33.930> anything<00:16:34.380> and 00:16:34.850 --> 00:16:34.860 align:start position:0% questions about how we did anything and 00:16:34.860 --> 00:16:37.040 align:start position:0% questions about how we did anything and talk<00:16:35.520> with<00:16:35.670> you<00:16:35.790> all<00:16:35.820> offline<00:16:36.300> after<00:16:36.510> this<00:16:36.780> but 00:16:37.040 --> 00:16:37.050 align:start position:0% talk with you all offline after this but 00:16:37.050 --> 00:16:47.730 align:start position:0% talk with you all offline after this but thanks<00:16:37.410> a<00:16:37.500> lot<00:16:37.620> for<00:16:37.740> being<00:16:37.860> with<00:16:38.040> me<00:16:38.070> today 00:16:47.730 --> 00:16:47.740 align:start position:0% 00:16:47.740 --> 00:16:49.800 align:start position:0% you