WEBVTT Kind: captions Language: en 00:00:04.700 --> 00:00:07.120 align:start position:0% I'm<00:00:05.120> Danny<00:00:05.600> Ryan<00:00:05.870> I<00:00:06.080> work<00:00:06.259> with<00:00:06.440> the<00:00:06.620> etherion 00:00:07.120 --> 00:00:07.130 align:start position:0% I'm Danny Ryan I work with the etherion 00:00:07.130 --> 00:00:09.549 align:start position:0% I'm Danny Ryan I work with the etherion foundation<00:00:07.640> on<00:00:08.000> the<00:00:08.389> research<00:00:08.660> team<00:00:08.990> I<00:00:09.320> do<00:00:09.469> a 00:00:09.549 --> 00:00:09.559 align:start position:0% foundation on the research team I do a 00:00:09.559 --> 00:00:13.270 align:start position:0% foundation on the research team I do a lot<00:00:09.740> of<00:00:09.770> work<00:00:09.950> on<00:00:10.160> e<00:00:10.670> to<00:00:11.330> specs<00:00:12.280> research 00:00:13.270 --> 00:00:13.280 align:start position:0% lot of work on e to specs research 00:00:13.280 --> 00:00:15.370 align:start position:0% lot of work on e to specs research coordination<00:00:14.120> of<00:00:14.360> client<00:00:14.719> development<00:00:14.870> and 00:00:15.370 --> 00:00:15.380 align:start position:0% coordination of client development and 00:00:15.380 --> 00:00:18.850 align:start position:0% coordination of client development and all<00:00:15.650> sorts<00:00:15.950> of<00:00:15.980> fun<00:00:16.189> stuff<00:00:16.720> today<00:00:17.720> give<00:00:18.680> you<00:00:18.770> an 00:00:18.850 --> 00:00:18.860 align:start position:0% all sorts of fun stuff today give you an 00:00:18.860 --> 00:00:22.359 align:start position:0% all sorts of fun stuff today give you an update<00:00:19.189> on<00:00:20.439> what's<00:00:21.439> going<00:00:21.500> on<00:00:21.830> because 00:00:22.359 --> 00:00:22.369 align:start position:0% update on what's going on because 00:00:22.369 --> 00:00:24.790 align:start position:0% update on what's going on because there's<00:00:22.640> a<00:00:22.699> lot<00:00:22.820> going<00:00:23.090> on<00:00:23.320> it's<00:00:24.320> kind<00:00:24.560> of<00:00:24.650> hard 00:00:24.790 --> 00:00:24.800 align:start position:0% there's a lot going on it's kind of hard 00:00:24.800 --> 00:00:26.679 align:start position:0% there's a lot going on it's kind of hard to<00:00:24.830> keep<00:00:24.949> up<00:00:25.100> with<00:00:25.130> and<00:00:25.580> hopefully<00:00:26.180> also<00:00:26.539> help 00:00:26.679 --> 00:00:26.689 align:start position:0% to keep up with and hopefully also help 00:00:26.689 --> 00:00:28.420 align:start position:0% to keep up with and hopefully also help give<00:00:26.869> you<00:00:26.960> the<00:00:26.990> lay<00:00:27.199> of<00:00:27.320> the<00:00:27.349> land<00:00:27.410> and<00:00:28.010> also 00:00:28.420 --> 00:00:28.430 align:start position:0% give you the lay of the land and also 00:00:28.430 --> 00:00:29.950 align:start position:0% give you the lay of the land and also help<00:00:28.849> you<00:00:28.910> become<00:00:29.029> acquainted<00:00:29.570> with<00:00:29.720> some<00:00:29.930> of 00:00:29.950 --> 00:00:29.960 align:start position:0% help you become acquainted with some of 00:00:29.960 --> 00:00:32.799 align:start position:0% help you become acquainted with some of the<00:00:30.580> fun<00:00:31.580> and<00:00:32.029> interesting<00:00:32.239> talks<00:00:32.629> that<00:00:32.750> are 00:00:32.799 --> 00:00:32.809 align:start position:0% the fun and interesting talks that are 00:00:32.809 --> 00:00:35.200 align:start position:0% the fun and interesting talks that are gonna<00:00:32.930> happen<00:00:33.080> over<00:00:33.320> the<00:00:33.410> next<00:00:33.530> few<00:00:33.680> days<00:00:33.879> so<00:00:34.879> a 00:00:35.200 --> 00:00:35.210 align:start position:0% gonna happen over the next few days so a 00:00:35.210 --> 00:00:38.829 align:start position:0% gonna happen over the next few days so a lots<00:00:35.780> going<00:00:35.989> on<00:00:36.610> but<00:00:37.610> first<00:00:37.850> I<00:00:38.150> always<00:00:38.570> like<00:00:38.750> to 00:00:38.829 --> 00:00:38.839 align:start position:0% lots going on but first I always like to 00:00:38.839 --> 00:00:44.579 align:start position:0% lots going on but first I always like to talk<00:00:38.989> about<00:00:39.110> the<00:00:39.710> architecture<00:00:40.519> of<00:00:40.729> e<00:00:40.940> to<00:00:41.199> the 00:00:44.579 --> 00:00:44.589 align:start position:0% 00:00:44.589 --> 00:00:47.140 align:start position:0% simple<00:00:45.589> single<00:00:46.070> blockchain<00:00:46.699> of<00:00:46.820> it<00:00:46.909> there<00:00:47.030> in 00:00:47.140 --> 00:00:47.150 align:start position:0% simple single blockchain of it there in 00:00:47.150 --> 00:00:49.450 align:start position:0% simple single blockchain of it there in one<00:00:47.299> so<00:00:47.750> it's<00:00:47.900> not<00:00:47.989> very<00:00:48.559> simple<00:00:48.949> but<00:00:49.129> a<00:00:49.159> lot<00:00:49.280> of 00:00:49.450 --> 00:00:49.460 align:start position:0% one so it's not very simple but a lot of 00:00:49.460 --> 00:00:50.890 align:start position:0% one so it's not very simple but a lot of us<00:00:49.549> have<00:00:49.699> a<00:00:49.729> good<00:00:49.909> intuition<00:00:50.119> for<00:00:50.479> it<00:00:50.629> and<00:00:50.809> I 00:00:50.890 --> 00:00:50.900 align:start position:0% us have a good intuition for it and I 00:00:50.900 --> 00:00:53.079 align:start position:0% us have a good intuition for it and I hope<00:00:51.290> that<00:00:51.500> we<00:00:51.559> can<00:00:51.710> carry<00:00:51.949> a<00:00:52.129> good<00:00:52.850> model 00:00:53.079 --> 00:00:53.089 align:start position:0% hope that we can carry a good model 00:00:53.089 --> 00:00:55.299 align:start position:0% hope that we can carry a good model mental<00:00:53.600> model<00:00:53.809> of<00:00:53.989> the<00:00:54.440> intuition<00:00:54.769> of<00:00:54.979> e<00:00:55.100> - 00:00:55.299 --> 00:00:55.309 align:start position:0% mental model of the intuition of e - 00:00:55.309 --> 00:00:58.810 align:start position:0% mental model of the intuition of e - moving<00:00:55.879> forward<00:00:56.210> so<00:00:57.110> we<00:00:57.379> divided<00:00:57.820> production 00:00:58.810 --> 00:00:58.820 align:start position:0% moving forward so we divided production 00:00:58.820 --> 00:01:01.479 align:start position:0% moving forward so we divided production in<00:00:59.750> implementation<00:01:00.680> of<00:01:00.769> this<00:01:00.890> in<00:01:01.040> two<00:01:01.129> phases 00:01:01.479 --> 00:01:01.489 align:start position:0% in implementation of this in two phases 00:01:01.489 --> 00:01:03.490 align:start position:0% in implementation of this in two phases the<00:01:01.790> initial<00:01:02.089> phase<00:01:02.210> phase<00:01:02.510> zero<00:01:02.839> called<00:01:03.199> the 00:01:03.490 --> 00:01:03.500 align:start position:0% the initial phase phase zero called the 00:01:03.500 --> 00:01:06.940 align:start position:0% the initial phase phase zero called the beacon<00:01:03.830> chain<00:01:04.070> is<00:01:05.000> a<00:01:05.140> pure<00:01:06.140> proof<00:01:06.590> of<00:01:06.740> stake 00:01:06.940 --> 00:01:06.950 align:start position:0% beacon chain is a pure proof of stake 00:01:06.950 --> 00:01:10.510 align:start position:0% beacon chain is a pure proof of stake blockchain<00:01:07.810> that<00:01:08.810> uses<00:01:09.410> kasparov<00:01:09.980> of<00:01:10.130> G<00:01:10.280> as 00:01:10.510 --> 00:01:10.520 align:start position:0% blockchain that uses kasparov of G as 00:01:10.520 --> 00:01:15.520 align:start position:0% blockchain that uses kasparov of G as its<00:01:10.700> core<00:01:10.910> consensus<00:01:11.560> and<00:01:12.560> builds<00:01:13.070> blocks<00:01:14.530> has 00:01:15.520 --> 00:01:15.530 align:start position:0% its core consensus and builds blocks has 00:01:15.530 --> 00:01:19.420 align:start position:0% its core consensus and builds blocks has validators<00:01:16.270> and<00:01:17.270> it<00:01:17.810> has<00:01:18.050> this<00:01:18.320> loose<00:01:18.680> tie<00:01:19.010> to 00:01:19.420 --> 00:01:19.430 align:start position:0% validators and it has this loose tie to 00:01:19.430 --> 00:01:22.030 align:start position:0% validators and it has this loose tie to the<00:01:19.940> existing<00:01:20.780> theorem<00:01:21.260> one<00:01:21.380> chain<00:01:21.620> to<00:01:21.770> handle 00:01:22.030 --> 00:01:22.040 align:start position:0% the existing theorem one chain to handle 00:01:22.040 --> 00:01:24.010 align:start position:0% the existing theorem one chain to handle deposits<00:01:22.490> there's<00:01:23.060> a<00:01:23.120> couple<00:01:23.420> of<00:01:23.510> rolls<00:01:23.750> of 00:01:24.010 --> 00:01:24.020 align:start position:0% deposits there's a couple of rolls of 00:01:24.020 --> 00:01:25.960 align:start position:0% deposits there's a couple of rolls of validators<00:01:24.500> do<00:01:24.710> on<00:01:25.010> this<00:01:25.190> chain<00:01:25.490> they<00:01:25.730> build 00:01:25.960 --> 00:01:25.970 align:start position:0% validators do on this chain they build 00:01:25.970 --> 00:01:28.810 align:start position:0% validators do on this chain they build blocks<00:01:26.770> but<00:01:27.770> just<00:01:28.010> as<00:01:28.100> importantly<00:01:28.550> if<00:01:28.670> not 00:01:28.810 --> 00:01:28.820 align:start position:0% blocks but just as importantly if not 00:01:28.820 --> 00:01:30.520 align:start position:0% blocks but just as importantly if not more<00:01:29.030> importantly<00:01:29.450> they<00:01:29.630> attest<00:01:30.020> to<00:01:30.200> blocks 00:01:30.520 --> 00:01:30.530 align:start position:0% more importantly they attest to blocks 00:01:30.530 --> 00:01:33.120 align:start position:0% more importantly they attest to blocks so<00:01:30.770> every<00:01:31.040> epoch<00:01:31.250> or<00:01:31.760> unit<00:01:32.150> of<00:01:32.540> time 00:01:33.120 --> 00:01:33.130 align:start position:0% so every epoch or unit of time 00:01:33.130 --> 00:01:35.590 align:start position:0% so every epoch or unit of time validators<00:01:34.130> are<00:01:34.250> called<00:01:34.490> upon<00:01:34.670> to<00:01:34.880> vote<00:01:35.420> on 00:01:35.590 --> 00:01:35.600 align:start position:0% validators are called upon to vote on 00:01:35.600 --> 00:01:37.120 align:start position:0% validators are called upon to vote on what<00:01:35.810> they<00:01:35.930> see<00:01:35.990> is<00:01:36.380> the<00:01:36.500> head<00:01:36.650> of<00:01:36.680> the<00:01:36.890> chain 00:01:37.120 --> 00:01:37.130 align:start position:0% what they see is the head of the chain 00:01:37.130 --> 00:01:38.790 align:start position:0% what they see is the head of the chain to<00:01:37.340> give<00:01:37.460> weight<00:01:37.670> to<00:01:37.700> the<00:01:37.940> fork<00:01:38.180> choice<00:01:38.420> and 00:01:38.790 --> 00:01:38.800 align:start position:0% to give weight to the fork choice and 00:01:38.800 --> 00:01:41.110 align:start position:0% to give weight to the fork choice and don't<00:01:39.800> allow<00:01:40.010> a<00:01:40.310> small<00:01:40.580> minority<00:01:41.090> of 00:01:41.110 --> 00:01:41.120 align:start position:0% don't allow a small minority of 00:01:41.120 --> 00:01:44.440 align:start position:0% don't allow a small minority of proposers<00:01:41.659> to<00:01:41.810> take<00:01:41.990> over<00:01:42.170> the<00:01:42.830> chain<00:01:43.450> so 00:01:44.440 --> 00:01:44.450 align:start position:0% proposers to take over the chain so 00:01:44.450 --> 00:01:47.140 align:start position:0% proposers to take over the chain so that's<00:01:44.930> phase<00:01:45.140> zero<00:01:45.440> it<00:01:45.710> is<00:01:45.890> a<00:01:45.920> simple<00:01:46.730> proof 00:01:47.140 --> 00:01:47.150 align:start position:0% that's phase zero it is a simple proof 00:01:47.150 --> 00:01:49.000 align:start position:0% that's phase zero it is a simple proof of<00:01:47.300> stake<00:01:47.479> chain<00:01:47.780> it<00:01:48.020> doesn't<00:01:48.320> do<00:01:48.470> that<00:01:48.500> much 00:01:49.000 --> 00:01:49.010 align:start position:0% of stake chain it doesn't do that much 00:01:49.010 --> 00:01:51.070 align:start position:0% of stake chain it doesn't do that much but<00:01:49.670> it<00:01:49.760> is<00:01:49.850> the<00:01:49.970> core<00:01:50.270> infrastructure<00:01:50.780> that 00:01:51.070 --> 00:01:51.080 align:start position:0% but it is the core infrastructure that 00:01:51.080 --> 00:01:53.230 align:start position:0% but it is the core infrastructure that upon<00:01:51.440> which<00:01:51.650> we<00:01:51.860> build<00:01:52.030> additional<00:01:53.030> phases 00:01:53.230 --> 00:01:53.240 align:start position:0% upon which we build additional phases 00:01:53.240 --> 00:01:55.719 align:start position:0% upon which we build additional phases phase<00:01:54.080> one<00:01:54.320> we<00:01:54.470> have<00:01:54.560> the<00:01:54.620> shard<00:01:54.830> chains<00:01:55.100> the 00:01:55.719 --> 00:01:55.729 align:start position:0% phase one we have the shard chains the 00:01:55.729 --> 00:01:57.820 align:start position:0% phase one we have the shard chains the shard<00:01:55.970> chains<00:01:56.210> ask<00:01:56.510> data<00:01:56.900> and<00:01:57.290> I'll<00:01:57.380> talk 00:01:57.820 --> 00:01:57.830 align:start position:0% shard chains ask data and I'll talk 00:01:57.830 --> 00:02:00.670 align:start position:0% shard chains ask data and I'll talk about<00:01:57.860> that<00:01:58.100> nuance<00:01:58.310> in<00:01:58.580> a<00:01:58.640> second<00:01:59.000> so<00:01:59.990> instead 00:02:00.670 --> 00:02:00.680 align:start position:0% about that nuance in a second so instead 00:02:00.680 --> 00:02:02.200 align:start position:0% about that nuance in a second so instead of<00:02:00.740> just<00:02:00.920> the<00:02:01.070> beacon<00:02:01.340> chain<00:02:01.549> being<00:02:01.790> built<00:02:02.030> we 00:02:02.200 --> 00:02:02.210 align:start position:0% of just the beacon chain being built we 00:02:02.210 --> 00:02:03.640 align:start position:0% of just the beacon chain being built we have<00:02:02.330> these<00:02:02.420> other<00:02:02.659> shard<00:02:03.049> chains<00:02:03.350> being 00:02:03.640 --> 00:02:03.650 align:start position:0% have these other shard chains being 00:02:03.650 --> 00:02:06.850 align:start position:0% have these other shard chains being built<00:02:03.920> in<00:02:04.130> parallel<00:02:05.020> these<00:02:06.020> shard<00:02:06.380> chains<00:02:06.680> are 00:02:06.850 --> 00:02:06.860 align:start position:0% built in parallel these shard chains are 00:02:06.860 --> 00:02:09.369 align:start position:0% built in parallel these shard chains are also<00:02:07.030> cross-linked<00:02:08.030> back<00:02:08.479> into<00:02:08.959> the<00:02:09.080> beacon 00:02:09.369 --> 00:02:09.379 align:start position:0% also cross-linked back into the beacon 00:02:09.379 --> 00:02:12.190 align:start position:0% also cross-linked back into the beacon chain<00:02:09.590> and<00:02:09.830> when<00:02:10.549> this<00:02:10.789> happens<00:02:11.239> it<00:02:11.569> serves<00:02:12.080> a 00:02:12.190 --> 00:02:12.200 align:start position:0% chain and when this happens it serves a 00:02:12.200 --> 00:02:14.559 align:start position:0% chain and when this happens it serves a few<00:02:12.590> purposes<00:02:12.650> one<00:02:13.340> it<00:02:13.640> routes<00:02:14.030> the<00:02:14.300> fork 00:02:14.559 --> 00:02:14.569 align:start position:0% few purposes one it routes the fork 00:02:14.569 --> 00:02:16.660 align:start position:0% few purposes one it routes the fork choice<00:02:14.870> of<00:02:15.200> the<00:02:15.350> shard<00:02:15.590> chain<00:02:15.890> into<00:02:16.550> the 00:02:16.660 --> 00:02:16.670 align:start position:0% choice of the shard chain into the 00:02:16.670 --> 00:02:17.630 align:start position:0% choice of the shard chain into the beacon<00:02:16.940> chain<00:02:17.150> which<00:02:17.360> should<00:02:17.450> be 00:02:17.630 --> 00:02:17.640 align:start position:0% beacon chain which should be 00:02:17.640 --> 00:02:19.900 align:start position:0% beacon chain which should be kind<00:02:17.940> of<00:02:18.000> canonical<00:02:18.390> a<00:02:18.870> canonical<00:02:19.290> reference 00:02:19.900 --> 00:02:19.910 align:start position:0% kind of canonical a canonical reference 00:02:19.910 --> 00:02:22.820 align:start position:0% kind of canonical a canonical reference it<00:02:20.910> also<00:02:21.240> serves<00:02:21.780> these<00:02:22.110> points<00:02:22.470> of<00:02:22.590> cross 00:02:22.820 --> 00:02:22.830 align:start position:0% it also serves these points of cross 00:02:22.830 --> 00:02:25.670 align:start position:0% it also serves these points of cross links<00:02:23.250> serve<00:02:24.030> as<00:02:24.390> the<00:02:25.320> point<00:02:25.470> for 00:02:25.670 --> 00:02:25.680 align:start position:0% links serve as the point for 00:02:25.680 --> 00:02:28.940 align:start position:0% links serve as the point for asynchronous<00:02:26.130> communication<00:02:26.810> between<00:02:27.950> shard 00:02:28.940 --> 00:02:28.950 align:start position:0% asynchronous communication between shard 00:02:28.950 --> 00:02:33.890 align:start position:0% asynchronous communication between shard chains<00:02:30.230> so<00:02:31.230> with<00:02:31.950> phase<00:02:32.310> two<00:02:32.820> we've<00:02:33.450> take<00:02:33.690> this 00:02:33.890 --> 00:02:33.900 align:start position:0% chains so with phase two we've take this 00:02:33.900 --> 00:02:36.050 align:start position:0% chains so with phase two we've take this take<00:02:34.320> the<00:02:34.440> shard<00:02:34.740> at<00:02:34.860> infrastructure<00:02:35.340> and<00:02:35.940> we 00:02:36.050 --> 00:02:36.060 align:start position:0% take the shard at infrastructure and we 00:02:36.060 --> 00:02:39.500 align:start position:0% take the shard at infrastructure and we actually<00:02:36.390> add<00:02:36.540> state<00:02:37.470> and<00:02:37.700> execution<00:02:38.700> and<00:02:39.390> a 00:02:39.500 --> 00:02:39.510 align:start position:0% actually add state and execution and a 00:02:39.510 --> 00:02:41.870 align:start position:0% actually add state and execution and a layer<00:02:39.720> one<00:02:39.990> interpretation<00:02:40.710> of<00:02:41.220> shard<00:02:41.610> chains 00:02:41.870 --> 00:02:41.880 align:start position:0% layer one interpretation of shard chains 00:02:41.880 --> 00:02:43.910 align:start position:0% layer one interpretation of shard chains and<00:02:42.120> data<00:02:42.270> and<00:02:43.200> I'll<00:02:43.290> get<00:02:43.440> in<00:02:43.530> a<00:02:43.620> little<00:02:43.800> bit 00:02:43.910 --> 00:02:43.920 align:start position:0% and data and I'll get in a little bit 00:02:43.920 --> 00:02:46.250 align:start position:0% and data and I'll get in a little bit more<00:02:44.220> into<00:02:44.790> what<00:02:44.820> that<00:02:45.120> means<00:02:45.360> a<00:02:45.810> little 00:02:46.250 --> 00:02:46.260 align:start position:0% more into what that means a little 00:02:46.260 --> 00:02:47.030 align:start position:0% more into what that means a little further<00:02:46.380> down<00:02:46.560> the<00:02:46.620> line 00:02:47.030 --> 00:02:47.040 align:start position:0% further down the line 00:02:47.040 --> 00:02:50.150 align:start position:0% further down the line so<00:02:47.780> in<00:02:48.780> theorem<00:02:49.170> two<00:02:49.350> it's<00:02:49.830> not<00:02:49.980> that 00:02:50.150 --> 00:02:50.160 align:start position:0% so in theorem two it's not that 00:02:50.160 --> 00:02:52.940 align:start position:0% so in theorem two it's not that complicated<00:02:50.459> and<00:02:50.959> the<00:02:51.959> next<00:02:52.200> phase<00:02:52.320> part<00:02:52.860> of 00:02:52.940 --> 00:02:52.950 align:start position:0% complicated and the next phase part of 00:02:52.950 --> 00:02:55.390 align:start position:0% complicated and the next phase part of phase<00:02:53.100> two<00:02:53.340> would<00:02:53.459> be<00:02:53.610> to<00:02:53.850> get<00:02:54.510> rid<00:02:54.570> of<00:02:54.780> the 00:02:55.390 --> 00:02:55.400 align:start position:0% phase two would be to get rid of the 00:02:55.400 --> 00:02:58.190 align:start position:0% phase two would be to get rid of the work<00:02:56.400> chain<00:02:56.670> role<00:02:57.000> each<00:02:57.209> one<00:02:57.420> into<00:02:57.660> eath<00:02:57.900> to 00:02:58.190 --> 00:02:58.200 align:start position:0% work chain role each one into eath to 00:02:58.200 --> 00:03:00.020 align:start position:0% work chain role each one into eath to which<00:02:59.040> we<00:02:59.220> can<00:02:59.340> talk<00:02:59.459> about<00:02:59.520> a<00:02:59.790> little<00:02:59.910> bit 00:03:00.020 --> 00:03:00.030 align:start position:0% which we can talk about a little bit 00:03:00.030 --> 00:03:06.020 align:start position:0% which we can talk about a little bit later<00:03:00.380> so<00:03:02.000> theorem<00:03:03.000> two<00:03:04.850> sometimes<00:03:05.850> I<00:03:05.970> think 00:03:06.020 --> 00:03:06.030 align:start position:0% later so theorem two sometimes I think 00:03:06.030 --> 00:03:08.180 align:start position:0% later so theorem two sometimes I think about<00:03:06.180> it<00:03:06.480> abstractly<00:03:07.410> it's<00:03:07.620> kind<00:03:07.890> of<00:03:07.920> like<00:03:08.070> a 00:03:08.180 --> 00:03:08.190 align:start position:0% about it abstractly it's kind of like a 00:03:08.190 --> 00:03:10.760 align:start position:0% about it abstractly it's kind of like a concrete<00:03:08.880> object<00:03:09.060> that<00:03:09.750> we're<00:03:10.230> building<00:03:10.410> in 00:03:10.760 --> 00:03:10.770 align:start position:0% concrete object that we're building in 00:03:10.770 --> 00:03:13.070 align:start position:0% concrete object that we're building in an<00:03:10.890> abstract<00:03:11.190> void<00:03:11.700> of<00:03:11.970> space<00:03:12.020> sometimes<00:03:13.020> I 00:03:13.070 --> 00:03:13.080 align:start position:0% an abstract void of space sometimes I 00:03:13.080 --> 00:03:15.800 align:start position:0% an abstract void of space sometimes I think<00:03:13.170> about<00:03:13.760> sometimes<00:03:14.760> like<00:03:15.030> these<00:03:15.239> like 00:03:15.800 --> 00:03:15.810 align:start position:0% think about sometimes like these like 00:03:15.810 --> 00:03:18.229 align:start position:0% think about sometimes like these like massive<00:03:16.260> space<00:03:16.470> habitats<00:03:17.010> and<00:03:17.250> this<00:03:17.610> Stanford 00:03:18.229 --> 00:03:18.239 align:start position:0% massive space habitats and this Stanford 00:03:18.239 --> 00:03:20.150 align:start position:0% massive space habitats and this Stanford torus<00:03:18.420> is<00:03:18.780> particularly<00:03:19.200> apt<00:03:19.530> because<00:03:20.040> you 00:03:20.150 --> 00:03:20.160 align:start position:0% torus is particularly apt because you 00:03:20.160 --> 00:03:23.750 align:start position:0% torus is particularly apt because you have<00:03:20.250> this<00:03:20.370> like<00:03:20.550> core<00:03:20.910> central<00:03:22.400> component<00:03:23.400> to 00:03:23.750 --> 00:03:23.760 align:start position:0% have this like core central component to 00:03:23.760 --> 00:03:25.640 align:start position:0% have this like core central component to the<00:03:23.850> space<00:03:24.060> habitat<00:03:24.540> that<00:03:24.720> serves<00:03:25.019> as<00:03:25.470> the 00:03:25.640 --> 00:03:25.650 align:start position:0% the space habitat that serves as the 00:03:25.650 --> 00:03:27.259 align:start position:0% the space habitat that serves as the infrastructure<00:03:26.310> the<00:03:26.640> energy<00:03:26.940> generation 00:03:27.259 --> 00:03:27.269 align:start position:0% infrastructure the energy generation 00:03:27.269 --> 00:03:30.020 align:start position:0% infrastructure the energy generation where<00:03:28.019> light<00:03:28.500> is<00:03:28.530> refracted<00:03:29.010> into<00:03:29.489> the<00:03:29.820> outer 00:03:30.020 --> 00:03:30.030 align:start position:0% where light is refracted into the outer 00:03:30.030 --> 00:03:34.370 align:start position:0% where light is refracted into the outer torus<00:03:30.660> which<00:03:31.230> is<00:03:31.500> where<00:03:31.940> the<00:03:32.940> actual<00:03:33.380> people 00:03:34.370 --> 00:03:34.380 align:start position:0% torus which is where the actual people 00:03:34.380 --> 00:03:36.979 align:start position:0% torus which is where the actual people live<00:03:34.530> the<00:03:34.830> user<00:03:35.070> level<00:03:35.519> activity<00:03:35.940> and<00:03:36.750> so<00:03:36.900> to 00:03:36.979 --> 00:03:36.989 align:start position:0% live the user level activity and so to 00:03:36.989 --> 00:03:39.289 align:start position:0% live the user level activity and so to build<00:03:37.260> this<00:03:37.470> thing<00:03:37.739> sanely<00:03:38.100> you<00:03:38.850> can't<00:03:39.090> just 00:03:39.289 --> 00:03:39.299 align:start position:0% build this thing sanely you can't just 00:03:39.299 --> 00:03:40.220 align:start position:0% build this thing sanely you can't just like<00:03:39.450> build<00:03:39.690> the<00:03:39.780> whole<00:03:39.900> thing<00:03:40.080> on<00:03:40.170> earth 00:03:40.220 --> 00:03:40.230 align:start position:0% like build the whole thing on earth 00:03:40.230 --> 00:03:41.960 align:start position:0% like build the whole thing on earth because<00:03:40.650> it's<00:03:40.769> too<00:03:40.920> big<00:03:40.950> you<00:03:41.340> have<00:03:41.700> to<00:03:41.820> build 00:03:41.960 --> 00:03:41.970 align:start position:0% because it's too big you have to build 00:03:41.970 --> 00:03:44.750 align:start position:0% because it's too big you have to build it<00:03:42.090> in<00:03:42.180> space<00:03:42.420> and<00:03:43.290> you<00:03:43.440> obviously<00:03:43.860> start<00:03:44.549> is 00:03:44.750 --> 00:03:44.760 align:start position:0% it in space and you obviously start is 00:03:44.760 --> 00:03:47.300 align:start position:0% it in space and you obviously start is this<00:03:44.940> core<00:03:45.180> system<00:03:45.630> this<00:03:46.500> core<00:03:46.769> like<00:03:46.980> central 00:03:47.300 --> 00:03:47.310 align:start position:0% this core system this core like central 00:03:47.310 --> 00:03:49.160 align:start position:0% this core system this core like central infrastructure<00:03:47.730> building<00:03:48.630> it<00:03:48.720> out<00:03:48.780> until<00:03:49.080> we 00:03:49.160 --> 00:03:49.170 align:start position:0% infrastructure building it out until we 00:03:49.170 --> 00:03:51.500 align:start position:0% infrastructure building it out until we finally<00:03:49.500> have<00:03:49.709> paradise<00:03:50.489> user<00:03:50.760> activity<00:03:51.269> so 00:03:51.500 --> 00:03:51.510 align:start position:0% finally have paradise user activity so 00:03:51.510 --> 00:03:54.979 align:start position:0% finally have paradise user activity so those<00:03:51.840> are<00:03:52.019> the<00:03:52.080> phases<00:03:52.440> of<00:03:52.470> v2<00:03:53.600> so<00:03:54.600> what's 00:03:54.979 --> 00:03:54.989 align:start position:0% those are the phases of v2 so what's 00:03:54.989 --> 00:03:57.590 align:start position:0% those are the phases of v2 so what's been<00:03:55.140> going<00:03:55.170> on<00:03:55.380> with<00:03:55.500> specs<00:03:55.769> and<00:03:56.010> research<00:03:56.600> we 00:03:57.590 --> 00:03:57.600 align:start position:0% been going on with specs and research we 00:03:57.600 --> 00:03:59.720 align:start position:0% been going on with specs and research we froze<00:03:57.810> the<00:03:57.989> spec<00:03:58.200> July<00:03:58.470> first<00:03:58.769> phase<00:03:59.040> zero<00:03:59.430> of 00:03:59.720 --> 00:03:59.730 align:start position:0% froze the spec July first phase zero of 00:03:59.730 --> 00:04:03.380 align:start position:0% froze the spec July first phase zero of the<00:03:59.850> spec<00:04:00.090> that<00:04:00.120> is<00:04:00.530> and<00:04:01.880> today<00:04:02.880> later<00:04:03.209> today 00:04:03.380 --> 00:04:03.390 align:start position:0% the spec that is and today later today 00:04:03.390 --> 00:04:05.330 align:start position:0% the spec that is and today later today we're<00:04:03.630> doing<00:04:03.780> a<00:04:03.870> deep<00:04:04.080> dive<00:04:04.110> on<00:04:04.350> this<00:04:04.709> spec<00:04:05.010> it 00:04:05.330 --> 00:04:05.340 align:start position:0% we're doing a deep dive on this spec it 00:04:05.340 --> 00:04:07.789 align:start position:0% we're doing a deep dive on this spec it should<00:04:05.549> be<00:04:05.610> a<00:04:06.000> good<00:04:06.480> time<00:04:06.750> I<00:04:06.959> think<00:04:07.140> it's<00:04:07.260> an 00:04:07.789 --> 00:04:07.799 align:start position:0% should be a good time I think it's an 00:04:07.799 --> 00:04:10.580 align:start position:0% should be a good time I think it's an hour<00:04:08.040> workshop<00:04:08.820> digging<00:04:09.570> into<00:04:09.690> that<00:04:09.930> this 00:04:10.580 --> 00:04:10.590 align:start position:0% hour workshop digging into that this 00:04:10.590 --> 00:04:12.910 align:start position:0% hour workshop digging into that this point<00:04:11.010> really<00:04:11.250> marks<00:04:11.640> the<00:04:11.730> transition 00:04:12.910 --> 00:04:12.920 align:start position:0% point really marks the transition 00:04:12.920 --> 00:04:15.229 align:start position:0% point really marks the transition towards<00:04:13.920> production<00:04:14.519> for<00:04:14.760> client<00:04:15.090> and 00:04:15.229 --> 00:04:15.239 align:start position:0% towards production for client and 00:04:15.239 --> 00:04:17.539 align:start position:0% towards production for client and implementation<00:04:15.989> teams<00:04:16.229> I<00:04:16.739> finally<00:04:17.250> gave<00:04:17.400> them 00:04:17.539 --> 00:04:17.549 align:start position:0% implementation teams I finally gave them 00:04:17.549 --> 00:04:19.330 align:start position:0% implementation teams I finally gave them something<00:04:17.729> very<00:04:18.120> stable<00:04:18.510> to<00:04:18.690> work<00:04:18.989> towards 00:04:19.330 --> 00:04:19.340 align:start position:0% something very stable to work towards 00:04:19.340 --> 00:04:22.039 align:start position:0% something very stable to work towards and<00:04:20.340> and<00:04:20.700> I'll<00:04:21.090> give<00:04:21.479> you<00:04:21.570> an<00:04:21.630> update<00:04:21.660> on<00:04:21.930> their 00:04:22.039 --> 00:04:22.049 align:start position:0% and and I'll give you an update on their 00:04:22.049 --> 00:04:25.820 align:start position:0% and and I'll give you an update on their progress<00:04:22.109> soon<00:04:23.010> a<00:04:23.690> lot<00:04:24.690> of<00:04:24.810> consensus<00:04:25.440> tests 00:04:25.820 --> 00:04:25.830 align:start position:0% progress soon a lot of consensus tests 00:04:25.830 --> 00:04:28.600 align:start position:0% progress soon a lot of consensus tests hand<00:04:26.070> written<00:04:26.280> tests<00:04:26.849> that<00:04:27.060> help<00:04:27.570> us 00:04:28.600 --> 00:04:28.610 align:start position:0% hand written tests that help us 00:04:28.610 --> 00:04:30.070 align:start position:0% hand written tests that help us make<00:04:28.789> sure<00:04:28.939> that<00:04:29.090> clients<00:04:29.449> come<00:04:29.569> to<00:04:29.659> consensus 00:04:30.070 --> 00:04:30.080 align:start position:0% make sure that clients come to consensus 00:04:30.080 --> 00:04:32.020 align:start position:0% make sure that clients come to consensus with<00:04:30.229> each<00:04:30.319> other<00:04:30.530> before<00:04:30.740> we<00:04:31.639> actually<00:04:31.759> get 00:04:32.020 --> 00:04:32.030 align:start position:0% with each other before we actually get 00:04:32.030 --> 00:04:34.330 align:start position:0% with each other before we actually get to<00:04:32.090> production<00:04:32.270> the<00:04:32.629> networks<00:04:33.069> shout<00:04:34.069> out<00:04:34.189> to 00:04:34.330 --> 00:04:34.340 align:start position:0% to production the networks shout out to 00:04:34.340 --> 00:04:36.040 align:start position:0% to production the networks shout out to proto<00:04:34.610> lambda<00:04:35.120> he<00:04:35.300> did<00:04:35.419> a<00:04:35.449> lot<00:04:35.599> of<00:04:35.719> work<00:04:35.870> on 00:04:36.040 --> 00:04:36.050 align:start position:0% proto lambda he did a lot of work on 00:04:36.050 --> 00:04:37.719 align:start position:0% proto lambda he did a lot of work on this<00:04:36.259> and<00:04:36.979> has<00:04:37.099> saved<00:04:37.280> us 00:04:37.719 --> 00:04:37.729 align:start position:0% this and has saved us 00:04:37.729 --> 00:04:41.619 align:start position:0% this and has saved us huge<00:04:38.500> huge<00:04:39.500> headache<00:04:40.300> debugging<00:04:41.300> things<00:04:41.449> on 00:04:41.619 --> 00:04:41.629 align:start position:0% huge huge headache debugging things on 00:04:41.629 --> 00:04:44.080 align:start position:0% huge huge headache debugging things on instance<00:04:42.379> on<00:04:42.590> networks<00:04:43.069> been<00:04:43.759> a<00:04:43.819> lot<00:04:43.939> of<00:04:44.000> work 00:04:44.080 --> 00:04:44.090 align:start position:0% instance on networks been a lot of work 00:04:44.090 --> 00:04:45.600 align:start position:0% instance on networks been a lot of work on<00:04:44.180> efficient<00:04:44.539> merkel<00:04:44.780> proofs<00:04:44.990> we<00:04:45.229> have<00:04:45.349> these 00:04:45.600 --> 00:04:45.610 align:start position:0% on efficient merkel proofs we have these 00:04:45.610 --> 00:04:49.360 align:start position:0% on efficient merkel proofs we have these pretty<00:04:46.610> cool<00:04:47.289> tree<00:04:48.289> structure<00:04:48.680> called<00:04:48.919> simple 00:04:49.360 --> 00:04:49.370 align:start position:0% pretty cool tree structure called simple 00:04:49.370 --> 00:04:51.100 align:start position:0% pretty cool tree structure called simple serialize<00:04:49.759> tree<00:04:50.180> hashing<00:04:50.569> which<00:04:50.719> allows<00:04:50.930> us 00:04:51.100 --> 00:04:51.110 align:start position:0% serialize tree hashing which allows us 00:04:51.110 --> 00:04:53.290 align:start position:0% serialize tree hashing which allows us to<00:04:51.139> take<00:04:51.409> generally<00:04:51.800> objects<00:04:52.610> and<00:04:52.849> fit<00:04:53.150> them 00:04:53.290 --> 00:04:53.300 align:start position:0% to take generally objects and fit them 00:04:53.300 --> 00:04:56.140 align:start position:0% to take generally objects and fit them into<00:04:53.800> Merkle<00:04:54.800> trees<00:04:55.009> and<00:04:55.729> so<00:04:55.969> we've<00:04:56.090> been 00:04:56.140 --> 00:04:56.150 align:start position:0% into Merkle trees and so we've been 00:04:56.150 --> 00:04:57.429 align:start position:0% into Merkle trees and so we've been working<00:04:56.210> on<00:04:56.509> how<00:04:56.659> to<00:04:56.719> efficiently<00:04:57.229> make 00:04:57.429 --> 00:04:57.439 align:start position:0% working on how to efficiently make 00:04:57.439 --> 00:04:59.020 align:start position:0% working on how to efficiently make proofs<00:04:57.740> about<00:04:58.189> these<00:04:58.400> which<00:04:58.759> will<00:04:58.909> be 00:04:59.020 --> 00:04:59.030 align:start position:0% proofs about these which will be 00:04:59.030 --> 00:05:01.209 align:start position:0% proofs about these which will be relevant<00:04:59.509> to<00:04:59.870> execution<00:05:00.560> environment<00:05:01.039> state 00:05:01.209 --> 00:05:01.219 align:start position:0% relevant to execution environment state 00:05:01.219 --> 00:05:03.999 align:start position:0% relevant to execution environment state execution<00:05:01.729> needs<00:05:01.849> to<00:05:02.120> and<00:05:02.500> like<00:05:03.500> clients<00:05:03.889> and 00:05:03.999 --> 00:05:04.009 align:start position:0% execution needs to and like clients and 00:05:04.009 --> 00:05:06.879 align:start position:0% execution needs to and like clients and all<00:05:04.069> sorts<00:05:04.279> of<00:05:04.340> other<00:05:04.550> cool<00:05:04.879> things<00:05:05.319> a<00:05:06.319> lot<00:05:06.800> of 00:05:06.879 --> 00:05:06.889 align:start position:0% all sorts of other cool things a lot of 00:05:06.889 --> 00:05:08.439 align:start position:0% all sorts of other cool things a lot of works<00:05:07.039> been<00:05:07.099> going<00:05:07.400> on<00:05:07.490> to<00:05:07.669> decentralize 00:05:08.439 --> 00:05:08.449 align:start position:0% works been going on to decentralize 00:05:08.449 --> 00:05:10.149 align:start position:0% works been going on to decentralize staking<00:05:08.900> pools<00:05:09.169> this<00:05:09.620> is<00:05:09.800> kind<00:05:10.009> of<00:05:10.039> a 00:05:10.149 --> 00:05:10.159 align:start position:0% staking pools this is kind of a 00:05:10.159 --> 00:05:11.860 align:start position:0% staking pools this is kind of a little-known<00:05:10.580> component<00:05:11.270> of<00:05:11.360> the<00:05:11.449> protocol 00:05:11.860 --> 00:05:11.870 align:start position:0% little-known component of the protocol 00:05:11.870 --> 00:05:14.260 align:start position:0% little-known component of the protocol but<00:05:11.900> all<00:05:12.349> of<00:05:12.710> the<00:05:12.919> different<00:05:13.310> things<00:05:13.639> that<00:05:14.210> a 00:05:14.260 --> 00:05:14.270 align:start position:0% but all of the different things that a 00:05:14.270 --> 00:05:17.290 align:start position:0% but all of the different things that a validator<00:05:14.719> must<00:05:15.680> do<00:05:15.889> their<00:05:16.189> duties<00:05:16.580> we've 00:05:17.290 --> 00:05:17.300 align:start position:0% validator must do their duties we've 00:05:17.300 --> 00:05:18.850 align:start position:0% validator must do their duties we've been<00:05:17.479> designing<00:05:17.689> in<00:05:18.139> a<00:05:18.439> way<00:05:18.560> that<00:05:18.770> is 00:05:18.850 --> 00:05:18.860 align:start position:0% been designing in a way that is 00:05:18.860 --> 00:05:21.279 align:start position:0% been designing in a way that is multi-party<00:05:19.490> computation<00:05:19.789> friendly<00:05:20.419> and 00:05:21.279 --> 00:05:21.289 align:start position:0% multi-party computation friendly and 00:05:21.289 --> 00:05:23.890 align:start position:0% multi-party computation friendly and there's<00:05:21.439> a<00:05:21.500> talk<00:05:21.770> later<00:05:22.370> today<00:05:22.699> on<00:05:23.120> that<00:05:23.360> about 00:05:23.890 --> 00:05:23.900 align:start position:0% there's a talk later today on that about 00:05:23.900 --> 00:05:26.649 align:start position:0% there's a talk later today on that about decentralized<00:05:24.469> taking<00:05:24.770> pools<00:05:25.009> if<00:05:25.879> this<00:05:26.479> is 00:05:26.649 --> 00:05:26.659 align:start position:0% decentralized taking pools if this is 00:05:26.659 --> 00:05:29.379 align:start position:0% decentralized taking pools if this is this<00:05:26.779> is<00:05:26.930> kind<00:05:27.110> of<00:05:27.139> a<00:05:27.229> little-known<00:05:28.090> area<00:05:29.090> so 00:05:29.379 --> 00:05:29.389 align:start position:0% this is kind of a little-known area so 00:05:29.389 --> 00:05:32.070 align:start position:0% this is kind of a little-known area so go<00:05:29.599> to<00:05:29.659> that<00:05:29.810> talk<00:05:30.020> check<00:05:30.289> it<00:05:30.409> out<00:05:30.500> and<00:05:30.889> and 00:05:32.070 --> 00:05:32.080 align:start position:0% go to that talk check it out and and 00:05:32.080 --> 00:05:33.790 align:start position:0% go to that talk check it out and and some<00:05:33.080> of<00:05:33.110> y'all<00:05:33.319> should<00:05:33.440> probably<00:05:33.589> start 00:05:33.790 --> 00:05:33.800 align:start position:0% some of y'all should probably start 00:05:33.800 --> 00:05:36.129 align:start position:0% some of y'all should probably start building<00:05:34.129> these<00:05:34.779> multi-party<00:05:35.779> all<00:05:35.900> things 00:05:36.129 --> 00:05:36.139 align:start position:0% building these multi-party all things 00:05:36.139 --> 00:05:38.350 align:start position:0% building these multi-party all things there's<00:05:37.009> been<00:05:37.099> a<00:05:37.159> lot<00:05:37.279> of<00:05:37.310> academic<00:05:37.789> analysis 00:05:38.350 --> 00:05:38.360 align:start position:0% there's been a lot of academic analysis 00:05:38.360 --> 00:05:41.050 align:start position:0% there's been a lot of academic analysis audits<00:05:38.900> and<00:05:39.169> formal<00:05:39.500> verification<00:05:39.650> I<00:05:40.580> want<00:05:41.000> to 00:05:41.050 --> 00:05:41.060 align:start position:0% audits and formal verification I want to 00:05:41.060 --> 00:05:43.510 align:start position:0% audits and formal verification I want to thank<00:05:41.240> you<00:05:41.330> on<00:05:41.449> Zang<00:05:42.009> who's<00:05:43.009> been<00:05:43.190> doing<00:05:43.279> a<00:05:43.430> lot 00:05:43.510 --> 00:05:43.520 align:start position:0% thank you on Zang who's been doing a lot 00:05:43.520 --> 00:05:45.579 align:start position:0% thank you on Zang who's been doing a lot of<00:05:43.550> work<00:05:43.729> on<00:05:43.909> formalizing<00:05:44.750> Kasper<00:05:45.080> F<00:05:45.169> of<00:05:45.289> G<00:05:45.469> in 00:05:45.579 --> 00:05:45.589 align:start position:0% of work on formalizing Kasper F of G in 00:05:45.589 --> 00:05:48.279 align:start position:0% of work on formalizing Kasper F of G in this<00:05:45.680> new<00:05:45.860> context<00:05:46.370> of<00:05:46.460> proof<00:05:46.610> of<00:05:46.729> stake<00:05:46.940> a<00:05:47.930> lot 00:05:48.279 --> 00:05:48.289 align:start position:0% this new context of proof of stake a lot 00:05:48.289 --> 00:05:49.869 align:start position:0% this new context of proof of stake a lot of<00:05:48.379> audits<00:05:48.680> been<00:05:48.860> going<00:05:49.069> on<00:05:49.190> and<00:05:49.550> runtime 00:05:49.869 --> 00:05:49.879 align:start position:0% of audits been going on and runtime 00:05:49.879 --> 00:05:51.610 align:start position:0% of audits been going on and runtime verifications<00:05:50.539> been<00:05:50.750> doing<00:05:50.930> some<00:05:51.139> great 00:05:51.610 --> 00:05:51.620 align:start position:0% verifications been doing some great 00:05:51.620 --> 00:05:53.409 align:start position:0% verifications been doing some great formal<00:05:52.370> verification<00:05:52.520> work<00:05:53.000> both<00:05:53.210> in<00:05:53.330> the 00:05:53.409 --> 00:05:53.419 align:start position:0% formal verification work both in the 00:05:53.419 --> 00:05:56.680 align:start position:0% formal verification work both in the deposit<00:05:53.839> contract<00:05:54.050> and<00:05:55.060> recently<00:05:56.060> created<00:05:56.300> a 00:05:56.680 --> 00:05:56.690 align:start position:0% deposit contract and recently created a 00:05:56.690 --> 00:05:59.439 align:start position:0% deposit contract and recently created a model<00:05:57.409> of<00:05:57.500> the<00:05:57.620> KB<00:05:58.039> contain<00:05:58.400> a<00:05:58.789> formal<00:05:59.330> model 00:05:59.439 --> 00:05:59.449 align:start position:0% model of the KB contain a formal model 00:05:59.449 --> 00:06:02.170 align:start position:0% model of the KB contain a formal model in<00:05:59.779> which<00:05:59.900> we<00:05:59.960> plan<00:06:00.500> on<00:06:00.710> verifying<00:06:01.610> properties 00:06:02.170 --> 00:06:02.180 align:start position:0% in which we plan on verifying properties 00:06:02.180 --> 00:06:03.700 align:start position:0% in which we plan on verifying properties of<00:06:02.270> the<00:06:02.330> protocol<00:06:02.750> such<00:06:02.960> as<00:06:03.020> safety<00:06:03.379> aliveness 00:06:03.700 --> 00:06:03.710 align:start position:0% of the protocol such as safety aliveness 00:06:03.710 --> 00:06:06.070 align:start position:0% of the protocol such as safety aliveness and<00:06:03.919> other<00:06:04.159> other<00:06:04.520> things<00:06:04.719> there's<00:06:05.719> a<00:06:05.779> short 00:06:06.070 --> 00:06:06.080 align:start position:0% and other other things there's a short 00:06:06.080 --> 00:06:07.450 align:start position:0% and other other things there's a short talk<00:06:06.379> during<00:06:06.650> the<00:06:06.770> climate<00:06:07.099> summit<00:06:07.219> tomorrow 00:06:07.450 --> 00:06:07.460 align:start position:0% talk during the climate summit tomorrow 00:06:07.460 --> 00:06:09.070 align:start position:0% talk during the climate summit tomorrow if<00:06:07.729> you<00:06:07.819> want<00:06:07.939> to<00:06:08.000> hear<00:06:08.089> more<00:06:08.210> about<00:06:08.270> the<00:06:08.569> KP 00:06:09.070 --> 00:06:09.080 align:start position:0% if you want to hear more about the KP 00:06:09.080 --> 00:06:12.129 align:start position:0% if you want to hear more about the KP keychain<00:06:10.509> networking<00:06:11.509> spec<00:06:11.719> out<00:06:11.870> a<00:06:11.900> lot<00:06:12.110> of 00:06:12.129 --> 00:06:12.139 align:start position:0% keychain networking spec out a lot of 00:06:12.139 --> 00:06:16.300 align:start position:0% keychain networking spec out a lot of love<00:06:12.490> recently<00:06:13.719> it<00:06:14.719> kind<00:06:15.319> of<00:06:15.409> existed<00:06:16.039> in<00:06:16.129> just 00:06:16.300 --> 00:06:16.310 align:start position:0% love recently it kind of existed in just 00:06:16.310 --> 00:06:18.850 align:start position:0% love recently it kind of existed in just a<00:06:16.400> proto<00:06:16.639> form<00:06:16.969> until<00:06:17.509> a<00:06:17.569> few<00:06:17.779> months<00:06:17.870> ago 00:06:18.850 --> 00:06:18.860 align:start position:0% a proto form until a few months ago 00:06:18.860 --> 00:06:21.670 align:start position:0% a proto form until a few months ago shout<00:06:19.430> out<00:06:19.550> to<00:06:20.180> Nimbus<00:06:21.080> lighthouse<00:06:21.500> and 00:06:21.670 --> 00:06:21.680 align:start position:0% shout out to Nimbus lighthouse and 00:06:21.680 --> 00:06:23.140 align:start position:0% shout out to Nimbus lighthouse and protocol<00:06:22.009> labs<00:06:22.189> remembers<00:06:22.580> that<00:06:22.699> those<00:06:22.909> team 00:06:23.140 --> 00:06:23.150 align:start position:0% protocol labs remembers that those team 00:06:23.150 --> 00:06:25.149 align:start position:0% protocol labs remembers that those team stepped<00:06:23.509> up<00:06:23.659> and<00:06:23.839> helped<00:06:23.990> drive<00:06:24.229> this<00:06:24.529> which 00:06:25.149 --> 00:06:25.159 align:start position:0% stepped up and helped drive this which 00:06:25.159 --> 00:06:27.760 align:start position:0% stepped up and helped drive this which was<00:06:25.339> critical<00:06:25.789> to<00:06:25.960> getting<00:06:26.960> initial<00:06:27.409> Interop 00:06:27.760 --> 00:06:27.770 align:start position:0% was critical to getting initial Interop 00:06:27.770 --> 00:06:30.369 align:start position:0% was critical to getting initial Interop of<00:06:28.009> our<00:06:28.159> clients<00:06:28.550> working<00:06:28.909> and<00:06:29.719> I<00:06:29.810> do<00:06:29.870> just 00:06:30.369 --> 00:06:30.379 align:start position:0% of our clients working and I do just 00:06:30.379 --> 00:06:33.610 align:start position:0% of our clients working and I do just want<00:06:30.710> a<00:06:30.740> quick<00:06:30.979> side<00:06:31.250> Ghaleb<00:06:32.000> p2p<00:06:32.620> there's 00:06:33.610 --> 00:06:33.620 align:start position:0% want a quick side Ghaleb p2p there's 00:06:33.620 --> 00:06:36.490 align:start position:0% want a quick side Ghaleb p2p there's been<00:06:33.830> a<00:06:33.860> lot<00:06:34.039> of<00:06:34.180> quite<00:06:35.180> frankly<00:06:35.479> food<00:06:35.779> around 00:06:36.490 --> 00:06:36.500 align:start position:0% been a lot of quite frankly food around 00:06:36.500 --> 00:06:37.240 align:start position:0% been a lot of quite frankly food around the<00:06:36.770> p2p 00:06:37.240 --> 00:06:37.250 align:start position:0% the p2p 00:06:37.250 --> 00:06:38.170 align:start position:0% the p2p weather 00:06:38.170 --> 00:06:38.180 align:start position:0% weather 00:06:38.180 --> 00:06:41.560 align:start position:0% weather it's<00:06:38.330> sudo<00:06:38.600> a<00:06:38.630> suitable<00:06:39.110> choice<00:06:39.320> and<00:06:40.190> as<00:06:40.970> teams 00:06:41.560 --> 00:06:41.570 align:start position:0% it's sudo a suitable choice and as teams 00:06:41.570 --> 00:06:42.850 align:start position:0% it's sudo a suitable choice and as teams have<00:06:41.720> been<00:06:41.840> taking<00:06:42.110> more<00:06:42.230> ownership<00:06:42.290> over 00:06:42.850 --> 00:06:42.860 align:start position:0% have been taking more ownership over 00:06:42.860 --> 00:06:45.820 align:start position:0% have been taking more ownership over this<00:06:43.240> over<00:06:44.240> their<00:06:44.390> domains<00:06:45.020> of<00:06:45.260> this<00:06:45.380> project 00:06:45.820 --> 00:06:45.830 align:start position:0% this over their domains of this project 00:06:45.830 --> 00:06:48.430 align:start position:0% this over their domains of this project and<00:06:46.040> finally<00:06:46.700> integrating<00:06:47.330> them<00:06:47.450> in<00:06:47.660> we've 00:06:48.430 --> 00:06:48.440 align:start position:0% and finally integrating them in we've 00:06:48.440 --> 00:06:50.200 align:start position:0% and finally integrating them in we've had<00:06:48.590> a<00:06:48.620> great<00:06:49.040> success<00:06:49.400> and<00:06:49.430> are<00:06:49.730> excited<00:06:50.000> to 00:06:50.200 --> 00:06:50.210 align:start position:0% had a great success and are excited to 00:06:50.210 --> 00:06:52.540 align:start position:0% had a great success and are excited to continue<00:06:50.660> to<00:06:50.750> use<00:06:50.840> it 00:06:52.540 --> 00:06:52.550 align:start position:0% continue to use it 00:06:52.550 --> 00:06:54.730 align:start position:0% continue to use it phase<00:06:52.910> one<00:06:53.150> speck<00:06:53.480> Justin<00:06:54.200> Drake's<00:06:54.440> given 00:06:54.730 --> 00:06:54.740 align:start position:0% phase one speck Justin Drake's given 00:06:54.740 --> 00:06:56.020 align:start position:0% phase one speck Justin Drake's given this<00:06:54.830> thing<00:06:55.040> a<00:06:55.100> lot<00:06:55.220> of<00:06:55.310> love<00:06:55.460> recently<00:06:55.880> it's 00:06:56.020 --> 00:06:56.030 align:start position:0% this thing a lot of love recently it's 00:06:56.030 --> 00:06:58.780 align:start position:0% this thing a lot of love recently it's now<00:06:56.330> quite<00:06:56.690> frankly<00:06:56.720> pretty<00:06:57.290> elegant<00:06:57.790> mirrors 00:06:58.780 --> 00:06:58.790 align:start position:0% now quite frankly pretty elegant mirrors 00:06:58.790 --> 00:07:00.730 align:start position:0% now quite frankly pretty elegant mirrors the<00:06:59.000> phase<00:06:59.360> zero<00:06:59.660> specification<00:07:00.350> a<00:07:00.380> lot<00:07:00.620> of 00:07:00.730 --> 00:07:00.740 align:start position:0% the phase zero specification a lot of 00:07:00.740 --> 00:07:03.400 align:start position:0% the phase zero specification a lot of work<00:07:00.830> on<00:07:01.010> testing<00:07:01.660> ironing<00:07:02.660> out<00:07:02.750> some<00:07:03.080> of<00:07:03.200> the 00:07:03.400 --> 00:07:03.410 align:start position:0% work on testing ironing out some of the 00:07:03.410 --> 00:07:05.830 align:start position:0% work on testing ironing out some of the more<00:07:04.130> nuanced<00:07:04.430> details<00:07:04.850> and<00:07:05.210> exploring<00:07:05.660> some 00:07:05.830 --> 00:07:05.840 align:start position:0% more nuanced details and exploring some 00:07:05.840 --> 00:07:08.800 align:start position:0% more nuanced details and exploring some opportunities<00:07:06.410> to<00:07:06.440> maybe<00:07:06.770> increase<00:07:07.810> the 00:07:08.800 --> 00:07:08.810 align:start position:0% opportunities to maybe increase the 00:07:08.810 --> 00:07:10.390 align:start position:0% opportunities to maybe increase the amount<00:07:08.990> of<00:07:09.020> cross-linking<00:07:09.710> that<00:07:09.890> happens<00:07:10.250> to 00:07:10.390 --> 00:07:10.400 align:start position:0% amount of cross-linking that happens to 00:07:10.400 --> 00:07:12.450 align:start position:0% amount of cross-linking that happens to help<00:07:10.550> facilitate<00:07:10.700> crush<00:07:11.210> our<00:07:11.390> communication 00:07:12.450 --> 00:07:12.460 align:start position:0% help facilitate crush our communication 00:07:12.460 --> 00:07:16.060 align:start position:0% help facilitate crush our communication so<00:07:13.780> something<00:07:14.780> that's<00:07:14.810> in<00:07:15.380> the<00:07:15.470> past<00:07:15.650> six 00:07:16.060 --> 00:07:16.070 align:start position:0% so something that's in the past six 00:07:16.070 --> 00:07:17.890 align:start position:0% so something that's in the past six months<00:07:16.190> the<00:07:16.790> lay<00:07:17.240> of<00:07:17.360> the<00:07:17.390> land<00:07:17.510> in<00:07:17.840> the 00:07:17.890 --> 00:07:17.900 align:start position:0% months the lay of the land in the 00:07:17.900 --> 00:07:19.600 align:start position:0% months the lay of the land in the direction<00:07:18.020> of<00:07:18.530> what<00:07:18.740> we<00:07:18.830> call<00:07:19.010> phase<00:07:19.280> two 00:07:19.600 --> 00:07:19.610 align:start position:0% direction of what we call phase two 00:07:19.610 --> 00:07:21.790 align:start position:0% direction of what we call phase two which<00:07:19.820> is<00:07:19.970> that<00:07:20.150> state<00:07:20.450> and<00:07:20.690> execution<00:07:21.650> of 00:07:21.790 --> 00:07:21.800 align:start position:0% which is that state and execution of 00:07:21.800 --> 00:07:25.180 align:start position:0% which is that state and execution of eath<00:07:22.100> to<00:07:22.340> has<00:07:23.050> radically<00:07:24.050> changed<00:07:24.260> and 00:07:25.180 --> 00:07:25.190 align:start position:0% eath to has radically changed and 00:07:25.190 --> 00:07:26.770 align:start position:0% eath to has radically changed and actually<00:07:25.550> it's<00:07:25.850> not<00:07:25.970> state<00:07:26.210> an<00:07:26.300> execution 00:07:26.770 --> 00:07:26.780 align:start position:0% actually it's not state an execution 00:07:26.780 --> 00:07:30.370 align:start position:0% actually it's not state an execution it's<00:07:26.960> stateless<00:07:27.470> execution<00:07:28.570> KC<00:07:29.570> from<00:07:30.200> the<00:07:30.350> e 00:07:30.370 --> 00:07:30.380 align:start position:0% it's stateless execution KC from the e 00:07:30.380 --> 00:07:33.510 align:start position:0% it's stateless execution KC from the e azam<00:07:30.860> team<00:07:31.010> put<00:07:31.310> out<00:07:31.400> a<00:07:31.430> post<00:07:31.700> in<00:07:32.000> April<00:07:32.510> about 00:07:33.510 --> 00:07:33.520 align:start position:0% azam team put out a post in April about 00:07:33.520 --> 00:07:36.160 align:start position:0% azam team put out a post in April about using<00:07:34.520> kind<00:07:34.970> of<00:07:35.060> reframing<00:07:35.690> how<00:07:35.840> we<00:07:35.960> think 00:07:36.160 --> 00:07:36.170 align:start position:0% using kind of reframing how we think 00:07:36.170 --> 00:07:40.180 align:start position:0% using kind of reframing how we think about<00:07:36.290> this<00:07:36.680> highly<00:07:37.430> scalable<00:07:38.080> system<00:07:39.080> so<00:07:39.530> at 00:07:40.180 --> 00:07:40.190 align:start position:0% about this highly scalable system so at 00:07:40.190 --> 00:07:43.900 align:start position:0% about this highly scalable system so at its<00:07:40.490> core<00:07:40.610> what<00:07:41.270> e2<00:07:41.810> does<00:07:42.080> is<00:07:42.410> it<00:07:42.920> solves<00:07:43.490> data 00:07:43.900 --> 00:07:43.910 align:start position:0% its core what e2 does is it solves data 00:07:43.910 --> 00:07:46.120 align:start position:0% its core what e2 does is it solves data availability<00:07:44.390> and<00:07:44.780> it's<00:07:45.380> a<00:07:45.470> date 00:07:46.120 --> 00:07:46.130 align:start position:0% availability and it's a date 00:07:46.130 --> 00:07:47.740 align:start position:0% availability and it's a date availability<00:07:46.550> engine<00:07:47.090> that<00:07:47.480> comes<00:07:47.630> to 00:07:47.740 --> 00:07:47.750 align:start position:0% availability engine that comes to 00:07:47.750 --> 00:07:49.600 align:start position:0% availability engine that comes to consensus<00:07:48.200> on<00:07:48.320> anywhere<00:07:48.620> between<00:07:48.770> like<00:07:48.920> one 00:07:49.600 --> 00:07:49.610 align:start position:0% consensus on anywhere between like one 00:07:49.610 --> 00:07:52.930 align:start position:0% consensus on anywhere between like one and<00:07:50.030> ten<00:07:50.270> megabytes<00:07:50.720> of<00:07:51.050> data<00:07:51.290> per<00:07:51.620> second<00:07:52.010> and 00:07:52.930 --> 00:07:52.940 align:start position:0% and ten megabytes of data per second and 00:07:52.940 --> 00:07:56.890 align:start position:0% and ten megabytes of data per second and so<00:07:53.240> reframing<00:07:54.110> the<00:07:54.970> phase<00:07:55.970> two<00:07:56.270> conversation 00:07:56.890 --> 00:07:56.900 align:start position:0% so reframing the phase two conversation 00:07:56.900 --> 00:07:59.410 align:start position:0% so reframing the phase two conversation around<00:07:57.050> how<00:07:57.950> we<00:07:58.010> can<00:07:58.370> more<00:07:58.550> abstractly<00:07:59.120> just 00:07:59.410 --> 00:07:59.420 align:start position:0% around how we can more abstractly just 00:07:59.420 --> 00:08:01.180 align:start position:0% around how we can more abstractly just use<00:07:59.630> this<00:07:59.900> highly<00:08:00.440> scalable<00:08:00.800> data<00:08:00.980> layer 00:08:01.180 --> 00:08:01.190 align:start position:0% use this highly scalable data layer 00:08:01.190 --> 00:08:03.580 align:start position:0% use this highly scalable data layer instead<00:08:01.700> of<00:08:01.850> having<00:08:02.330> to<00:08:02.630> bake<00:08:02.870> all<00:08:03.200> of<00:08:03.260> the 00:08:03.580 --> 00:08:03.590 align:start position:0% instead of having to bake all of the 00:08:03.590 --> 00:08:07.510 align:start position:0% instead of having to bake all of the execution<00:08:04.100> and<00:08:04.250> things<00:08:04.430> into<00:08:04.850> layer<00:08:05.510> one<00:08:06.520> now 00:08:07.510 --> 00:08:07.520 align:start position:0% execution and things into layer one now 00:08:07.520 --> 00:08:10.150 align:start position:0% execution and things into layer one now what<00:08:07.730> does<00:08:07.820> that<00:08:07.850> actually<00:08:08.090> mean<00:08:09.070> state<00:08:10.070> an 00:08:10.150 --> 00:08:10.160 align:start position:0% what does that actually mean state an 00:08:10.160 --> 00:08:13.960 align:start position:0% what does that actually mean state an execution<00:08:10.640> an<00:08:10.730> eighth<00:08:10.820> one<00:08:11.030> this<00:08:12.700> is<00:08:13.700> very 00:08:13.960 --> 00:08:13.970 align:start position:0% execution an eighth one this is very 00:08:13.970 --> 00:08:16.030 align:start position:0% execution an eighth one this is very limited<00:08:14.510> view<00:08:14.630> of<00:08:14.870> over<00:08:15.350> the<00:08:15.440> world<00:08:15.590> there<00:08:15.830> but 00:08:16.030 --> 00:08:16.040 align:start position:0% limited view of over the world there but 00:08:16.040 --> 00:08:17.890 align:start position:0% limited view of over the world there but in<00:08:16.490> in<00:08:16.850> consensus<00:08:17.360> we<00:08:17.450> have<00:08:17.540> this<00:08:17.630> strong 00:08:17.890 --> 00:08:17.900 align:start position:0% in in consensus we have this strong 00:08:17.900 --> 00:08:20.290 align:start position:0% in in consensus we have this strong notion<00:08:18.320> of<00:08:18.410> state<00:08:18.680> you<00:08:19.490> assume<00:08:19.820> when<00:08:20.120> you're 00:08:20.290 --> 00:08:20.300 align:start position:0% notion of state you assume when you're 00:08:20.300 --> 00:08:21.610 align:start position:0% notion of state you assume when you're processing<00:08:20.450> a<00:08:20.690> block<00:08:20.870> that<00:08:20.900> you<00:08:21.080> have<00:08:21.230> access 00:08:21.610 --> 00:08:21.620 align:start position:0% processing a block that you have access 00:08:21.620 --> 00:08:24.370 align:start position:0% processing a block that you have access to<00:08:21.650> all<00:08:21.920> state<00:08:22.190> and<00:08:23.090> you<00:08:23.210> also<00:08:23.390> have<00:08:23.690> a<00:08:23.960> strong 00:08:24.370 --> 00:08:24.380 align:start position:0% to all state and you also have a strong 00:08:24.380 --> 00:08:27.700 align:start position:0% to all state and you also have a strong embedded<00:08:25.300> execution<00:08:26.300> engine<00:08:26.570> where<00:08:27.020> we<00:08:27.560> have 00:08:27.700 --> 00:08:27.710 align:start position:0% embedded execution engine where we have 00:08:27.710 --> 00:08:31.570 align:start position:0% embedded execution engine where we have these<00:08:28.010> formal<00:08:28.760> and<00:08:29.770> hard-coded<00:08:30.770> rules<00:08:31.100> and 00:08:31.570 --> 00:08:31.580 align:start position:0% these formal and hard-coded rules and 00:08:31.580 --> 00:08:34.090 align:start position:0% these formal and hard-coded rules and notions<00:08:32.030> of<00:08:32.180> account<00:08:32.510> and<00:08:32.780> account<00:08:33.020> model<00:08:33.260> and 00:08:34.090 --> 00:08:34.100 align:start position:0% notions of account and account model and 00:08:34.100 --> 00:08:36.550 align:start position:0% notions of account and account model and so<00:08:34.280> your<00:08:34.700> changes<00:08:35.270> has<00:08:35.420> transaction<00:08:36.050> data<00:08:36.260> and 00:08:36.550 --> 00:08:36.560 align:start position:0% so your changes has transaction data and 00:08:36.560 --> 00:08:39.790 align:start position:0% so your changes has transaction data and execute<00:08:37.690> using<00:08:38.690> these<00:08:38.780> rules<00:08:39.080> upon<00:08:39.590> that 00:08:39.790 --> 00:08:39.800 align:start position:0% execute using these rules upon that 00:08:39.800 --> 00:08:42.190 align:start position:0% execute using these rules upon that state<00:08:40.600> transitioning<00:08:41.600> that<00:08:41.750> state<00:08:41.990> within 00:08:42.190 --> 00:08:42.200 align:start position:0% state transitioning that state within 00:08:42.200 --> 00:08:45.460 align:start position:0% state transitioning that state within the<00:08:42.380> consensus<00:08:42.860> but<00:08:43.760> in<00:08:44.150> e2<00:08:44.900> we're<00:08:45.110> moving<00:08:45.350> to 00:08:45.460 --> 00:08:45.470 align:start position:0% the consensus but in e2 we're moving to 00:08:45.470 --> 00:08:48.340 align:start position:0% the consensus but in e2 we're moving to a<00:08:45.500> more<00:08:45.830> abstracted<00:08:46.640> model<00:08:47.030> where<00:08:47.630> instead<00:08:48.170> of 00:08:48.340 --> 00:08:48.350 align:start position:0% a more abstracted model where instead of 00:08:48.350 --> 00:08:49.970 align:start position:0% a more abstracted model where instead of having<00:08:48.590> the<00:08:48.800> heart<00:08:49.040> could<00:08:49.280> its 00:08:49.970 --> 00:08:49.980 align:start position:0% having the heart could its 00:08:49.980 --> 00:08:52.519 align:start position:0% having the heart could its State<00:08:50.610> execution<00:08:51.389> rules<00:08:51.600> and<00:08:51.839> having<00:08:52.439> the 00:08:52.519 --> 00:08:52.529 align:start position:0% State execution rules and having the 00:08:52.529 --> 00:08:54.439 align:start position:0% State execution rules and having the entirety<00:08:53.040> of<00:08:53.069> state<00:08:53.369> available<00:08:53.670> within<00:08:54.149> the 00:08:54.439 --> 00:08:54.449 align:start position:0% entirety of state available within the 00:08:54.449 --> 00:08:56.749 align:start position:0% entirety of state available within the consensus<00:08:55.019> removing<00:08:55.889> to<00:08:55.980> this<00:08:56.069> abstracted 00:08:56.749 --> 00:08:56.759 align:start position:0% consensus removing to this abstracted 00:08:56.759 --> 00:08:58.369 align:start position:0% consensus removing to this abstracted model<00:08:57.059> which<00:08:57.420> we<00:08:57.600> call<00:08:57.779> execution 00:08:58.369 --> 00:08:58.379 align:start position:0% model which we call execution 00:08:58.379 --> 00:09:02.299 align:start position:0% model which we call execution environments<00:08:58.889> or<00:08:59.040> E's<00:08:59.819> in<00:09:00.149> which<00:09:00.720> state<00:09:01.679> the 00:09:02.299 --> 00:09:02.309 align:start position:0% environments or E's in which state the 00:09:02.309 --> 00:09:04.939 align:start position:0% environments or E's in which state the the<00:09:02.389> notion<00:09:03.389> of<00:09:03.600> state<00:09:03.929> the<00:09:04.410> notion<00:09:04.860> of 00:09:04.939 --> 00:09:04.949 align:start position:0% the notion of state the notion of 00:09:04.949 --> 00:09:06.859 align:start position:0% the notion of state the notion of account<00:09:05.309> and<00:09:05.610> the<00:09:05.670> notion<00:09:05.939> of<00:09:05.999> execution<00:09:06.540> upon 00:09:06.859 --> 00:09:06.869 align:start position:0% account and the notion of execution upon 00:09:06.869 --> 00:09:09.139 align:start position:0% account and the notion of execution upon that<00:09:07.079> can<00:09:07.649> be<00:09:07.769> defined<00:09:08.189> in<00:09:08.489> a<00:09:08.819> more<00:09:08.999> abstract 00:09:09.139 --> 00:09:09.149 align:start position:0% that can be defined in a more abstract 00:09:09.149 --> 00:09:13.160 align:start position:0% that can be defined in a more abstract way<00:09:10.189> and<00:09:11.189> can<00:09:11.429> be<00:09:11.459> defined<00:09:11.910> actually<00:09:12.179> not<00:09:12.959> in 00:09:13.160 --> 00:09:13.170 align:start position:0% way and can be defined actually not in 00:09:13.170 --> 00:09:15.289 align:start position:0% way and can be defined actually not in the<00:09:13.290> core<00:09:13.499> consensus<00:09:14.009> but<00:09:14.399> at<00:09:14.639> the<00:09:14.819> user<00:09:14.999> level 00:09:15.289 --> 00:09:15.299 align:start position:0% the core consensus but at the user level 00:09:15.299 --> 00:09:19.160 align:start position:0% the core consensus but at the user level and<00:09:16.290> so<00:09:16.410> we<00:09:16.529> have<00:09:16.709> these<00:09:17.360> at<00:09:18.360> each<00:09:18.600> of<00:09:18.779> these<00:09:18.899> is 00:09:19.160 --> 00:09:19.170 align:start position:0% and so we have these at each of these is 00:09:19.170 --> 00:09:20.689 align:start position:0% and so we have these at each of these is an<00:09:19.259> execution<00:09:19.709> environment<00:09:20.279> which<00:09:20.519> is<00:09:20.670> a 00:09:20.689 --> 00:09:20.699 align:start position:0% an execution environment which is a 00:09:20.699 --> 00:09:23.269 align:start position:0% an execution environment which is a chunk<00:09:21.209> of<00:09:21.329> code<00:09:21.600> wasum<00:09:22.379> code<00:09:22.589> which<00:09:23.100> would 00:09:23.269 --> 00:09:23.279 align:start position:0% chunk of code wasum code which would 00:09:23.279 --> 00:09:25.639 align:start position:0% chunk of code wasum code which would specify<00:09:23.879> the<00:09:23.939> rules<00:09:24.449> of<00:09:24.809> execution<00:09:25.439> within 00:09:25.639 --> 00:09:25.649 align:start position:0% specify the rules of execution within 00:09:25.649 --> 00:09:27.679 align:start position:0% specify the rules of execution within that<00:09:26.040> realm<00:09:26.309> within<00:09:26.639> that<00:09:26.790> domain<00:09:26.939> and<00:09:27.480> you 00:09:27.679 --> 00:09:27.689 align:start position:0% that realm within that domain and you 00:09:27.689 --> 00:09:29.660 align:start position:0% that realm within that domain and you can<00:09:27.839> actually<00:09:27.959> deploy<00:09:28.829> more<00:09:29.100> of<00:09:29.249> these<00:09:29.369> the 00:09:29.660 --> 00:09:29.670 align:start position:0% can actually deploy more of these the 00:09:29.670 --> 00:09:33.259 align:start position:0% can actually deploy more of these the actual<00:09:30.029> model<00:09:30.420> on<00:09:30.720> the<00:09:31.350> cost<00:09:31.759> of<00:09:32.759> either 00:09:33.259 --> 00:09:33.269 align:start position:0% actual model on the cost of either 00:09:33.269 --> 00:09:35.179 align:start position:0% actual model on the cost of either burning<00:09:33.779> or<00:09:33.899> locking<00:09:34.230> capitols<00:09:34.769> deploy<00:09:35.009> these 00:09:35.179 --> 00:09:35.189 align:start position:0% burning or locking capitols deploy these 00:09:35.189 --> 00:09:37.299 align:start position:0% burning or locking capitols deploy these is<00:09:35.369> still<00:09:35.610> up<00:09:36.119> for<00:09:36.149> debate<00:09:36.360> but<00:09:36.660> it<00:09:36.779> would<00:09:36.869> be 00:09:37.299 --> 00:09:37.309 align:start position:0% is still up for debate but it would be 00:09:37.309 --> 00:09:40.400 align:start position:0% is still up for debate but it would be expensive<00:09:38.309> because<00:09:38.489> you're<00:09:39.299> deploying<00:09:39.720> code 00:09:40.400 --> 00:09:40.410 align:start position:0% expensive because you're deploying code 00:09:40.410 --> 00:09:42.859 align:start position:0% expensive because you're deploying code on<00:09:40.860> this<00:09:41.309> globally<00:09:41.759> accessible<00:09:42.059> thing<00:09:42.629> called 00:09:42.859 --> 00:09:42.869 align:start position:0% on this globally accessible thing called 00:09:42.869 --> 00:09:45.049 align:start position:0% on this globally accessible thing called the<00:09:42.929> beacon<00:09:43.170> chain<00:09:43.379> and<00:09:43.619> so<00:09:44.129> where's<00:09:44.879> the 00:09:45.049 --> 00:09:45.059 align:start position:0% the beacon chain and so where's the 00:09:45.059 --> 00:09:46.999 align:start position:0% the beacon chain and so where's the state<00:09:45.269> the<00:09:45.809> state<00:09:46.019> does<00:09:46.199> not<00:09:46.319> exist<00:09:46.679> in<00:09:46.829> the 00:09:46.999 --> 00:09:47.009 align:start position:0% state the state does not exist in the 00:09:47.009 --> 00:09:50.929 align:start position:0% state the state does not exist in the consensus<00:09:47.459> the<00:09:48.149> state<00:09:48.569> actually<00:09:49.549> exists<00:09:50.549> the 00:09:50.929 --> 00:09:50.939 align:start position:0% consensus the state actually exists the 00:09:50.939 --> 00:09:52.970 align:start position:0% consensus the state actually exists the state<00:09:51.149> that<00:09:51.360> you<00:09:51.569> need<00:09:51.869> to<00:09:52.079> operate<00:09:52.529> blocks 00:09:52.970 --> 00:09:52.980 align:start position:0% state that you need to operate blocks 00:09:52.980 --> 00:09:54.619 align:start position:0% state that you need to operate blocks which<00:09:53.369> these<00:09:53.610> blocks<00:09:53.879> you<00:09:53.999> know<00:09:54.209> are<00:09:54.420> a<00:09:54.480> little 00:09:54.619 --> 00:09:54.629 align:start position:0% which these blocks you know are a little 00:09:54.629 --> 00:09:58.039 align:start position:0% which these blocks you know are a little bit<00:09:54.809> fatter<00:09:55.019> than<00:09:55.850> previous<00:09:56.850> because<00:09:57.839> now 00:09:58.039 --> 00:09:58.049 align:start position:0% bit fatter than previous because now 00:09:58.049 --> 00:10:00.259 align:start position:0% bit fatter than previous because now instead<00:09:58.410> of<00:09:58.740> just<00:09:58.889> transaction<00:09:59.730> user<00:09:59.939> level 00:10:00.259 --> 00:10:00.269 align:start position:0% instead of just transaction user level 00:10:00.269 --> 00:10:02.090 align:start position:0% instead of just transaction user level data<00:10:00.449> we<00:10:00.990> have<00:10:01.170> what<00:10:01.290> we<00:10:01.410> call<00:10:01.529> witnesses 00:10:02.090 --> 00:10:02.100 align:start position:0% data we have what we call witnesses 00:10:02.100 --> 00:10:04.639 align:start position:0% data we have what we call witnesses which<00:10:02.369> are<00:10:02.600> the<00:10:03.600> components<00:10:04.259> of<00:10:04.350> state 00:10:04.639 --> 00:10:04.649 align:start position:0% which are the components of state 00:10:04.649 --> 00:10:06.530 align:start position:0% which are the components of state required<00:10:05.279> to<00:10:05.519> operate<00:10:05.670> on<00:10:06.029> that<00:10:06.059> block<00:10:06.389> so 00:10:06.530 --> 00:10:06.540 align:start position:0% required to operate on that block so 00:10:06.540 --> 00:10:08.480 align:start position:0% required to operate on that block so it's<00:10:06.660> kind<00:10:06.809> of<00:10:06.839> like<00:10:06.959> a<00:10:07.019> the<00:10:07.769> database<00:10:08.220> and 00:10:08.480 --> 00:10:08.490 align:start position:0% it's kind of like a the database and 00:10:08.490 --> 00:10:12.470 align:start position:0% it's kind of like a the database and proofs<00:10:08.970> that<00:10:09.389> that<00:10:10.350> data<00:10:10.649> is<00:10:11.009> valid<00:10:11.819> against 00:10:12.470 --> 00:10:12.480 align:start position:0% proofs that that data is valid against 00:10:12.480 --> 00:10:14.689 align:start position:0% proofs that that data is valid against the<00:10:13.049> state<00:10:13.290> route<00:10:13.499> and<00:10:13.799> so<00:10:14.160> when<00:10:14.309> you<00:10:14.369> update<00:10:14.519> a 00:10:14.689 --> 00:10:14.699 align:start position:0% the state route and so when you update a 00:10:14.699 --> 00:10:16.669 align:start position:0% the state route and so when you update a block<00:10:15.149> you're<00:10:15.360> actually<00:10:15.629> not<00:10:15.779> modifying<00:10:16.499> the 00:10:16.669 --> 00:10:16.679 align:start position:0% block you're actually not modifying the 00:10:16.679 --> 00:10:18.319 align:start position:0% block you're actually not modifying the state<00:10:16.920> within<00:10:17.309> the<00:10:17.519> consensus<00:10:17.939> you're<00:10:18.089> just 00:10:18.319 --> 00:10:18.329 align:start position:0% state within the consensus you're just 00:10:18.329 --> 00:10:20.449 align:start position:0% state within the consensus you're just updating<00:10:18.899> the<00:10:19.499> state<00:10:19.769> route<00:10:19.980> which<00:10:20.160> is<00:10:20.189> kind 00:10:20.449 --> 00:10:20.459 align:start position:0% updating the state route which is kind 00:10:20.459 --> 00:10:23.780 align:start position:0% updating the state route which is kind of<00:10:20.490> like<00:10:20.639> the<00:10:20.759> digests<00:10:21.420> of<00:10:21.569> the<00:10:22.170> state<00:10:22.670> you<00:10:23.670> can 00:10:23.780 --> 00:10:23.790 align:start position:0% of like the digests of the state you can 00:10:23.790 --> 00:10:25.369 align:start position:0% of like the digests of the state you can do<00:10:23.850> a<00:10:23.879> lot<00:10:24.059> of<00:10:24.089> really<00:10:24.299> cool<00:10:25.049> and<00:10:25.170> interesting 00:10:25.369 --> 00:10:25.379 align:start position:0% do a lot of really cool and interesting 00:10:25.379 --> 00:10:28.340 align:start position:0% do a lot of really cool and interesting things<00:10:25.740> here<00:10:25.980> and<00:10:26.660> from<00:10:27.660> my<00:10:27.779> perspective<00:10:28.019> and 00:10:28.340 --> 00:10:28.350 align:start position:0% things here and from my perspective and 00:10:28.350 --> 00:10:30.410 align:start position:0% things here and from my perspective and what<00:10:28.860> this<00:10:28.949> allows<00:10:29.220> us<00:10:29.249> to<00:10:29.519> do<00:10:29.670> is<00:10:29.879> instead<00:10:30.360> of 00:10:30.410 --> 00:10:30.420 align:start position:0% what this allows us to do is instead of 00:10:30.420 --> 00:10:34.129 align:start position:0% what this allows us to do is instead of us<00:10:30.660> guessing<00:10:31.379> what<00:10:32.279> aetherium<00:10:32.720> can<00:10:33.720> or<00:10:33.959> should 00:10:34.129 --> 00:10:34.139 align:start position:0% us guessing what aetherium can or should 00:10:34.139 --> 00:10:37.730 align:start position:0% us guessing what aetherium can or should be<00:10:34.199> in<00:10:34.759> 20<00:10:35.759> 30<00:10:36.240> years<00:10:36.329> this<00:10:36.959> allows<00:10:37.259> us<00:10:37.439> to<00:10:37.559> like 00:10:37.730 --> 00:10:37.740 align:start position:0% be in 20 30 years this allows us to like 00:10:37.740 --> 00:10:40.159 align:start position:0% be in 20 30 years this allows us to like naturally<00:10:38.429> extend<00:10:38.970> and<00:10:39.209> upgrade<00:10:39.569> and<00:10:39.749> modify 00:10:40.159 --> 00:10:40.169 align:start position:0% naturally extend and upgrade and modify 00:10:40.169 --> 00:10:42.919 align:start position:0% naturally extend and upgrade and modify execution<00:10:40.980> as<00:10:41.160> there's<00:10:42.029> innovations<00:10:42.629> on<00:10:42.809> that 00:10:42.919 --> 00:10:42.929 align:start position:0% execution as there's innovations on that 00:10:42.929 --> 00:10:45.859 align:start position:0% execution as there's innovations on that layer<00:10:43.110> and<00:10:44.100> the<00:10:44.490> really<00:10:44.850> nice<00:10:44.999> thing<00:10:45.299> is<00:10:45.569> that 00:10:45.859 --> 00:10:45.869 align:start position:0% layer and the really nice thing is that 00:10:45.869 --> 00:10:49.369 align:start position:0% layer and the really nice thing is that it<00:10:46.169> gives<00:10:46.230> us<00:10:46.439> a<00:10:47.239> clear<00:10:48.239> trajectory<00:10:48.569> and<00:10:49.139> model 00:10:49.369 --> 00:10:49.379 align:start position:0% it gives us a clear trajectory and model 00:10:49.379 --> 00:10:51.470 align:start position:0% it gives us a clear trajectory and model on<00:10:49.529> how<00:10:49.559> eath<00:10:50.100> one<00:10:50.369> can<00:10:50.549> actually<00:10:50.999> be<00:10:51.149> slotted 00:10:51.470 --> 00:10:51.480 align:start position:0% on how eath one can actually be slotted 00:10:51.480 --> 00:10:55.309 align:start position:0% on how eath one can actually be slotted into<00:10:51.809> eath<00:10:52.139> 2<00:10:52.410> and<00:10:52.769> has<00:10:52.980> given<00:10:53.100> us<00:10:54.169> more<00:10:55.169> of<00:10:55.230> a 00:10:55.309 --> 00:10:55.319 align:start position:0% into eath 2 and has given us more of a 00:10:55.319 --> 00:10:57.150 align:start position:0% into eath 2 and has given us more of a concrete<00:10:55.739> idea<00:10:56.220> of<00:10:56.399> how<00:10:56.549> to<00:10:56.610> handle 00:10:57.150 --> 00:10:57.160 align:start position:0% concrete idea of how to handle 00:10:57.160 --> 00:10:59.940 align:start position:0% concrete idea of how to handle create<00:10:57.520> and<00:10:57.790> trajectory<00:10:58.780> so<00:10:59.020> eath<00:10:59.620> one 00:10:59.940 --> 00:10:59.950 align:start position:0% create and trajectory so eath one 00:10:59.950 --> 00:11:01.920 align:start position:0% create and trajectory so eath one actually<00:11:00.670> can<00:11:01.210> become<00:11:01.570> one<00:11:01.780> of<00:11:01.810> these 00:11:01.920 --> 00:11:01.930 align:start position:0% actually can become one of these 00:11:01.930 --> 00:11:04.230 align:start position:0% actually can become one of these execution<00:11:02.500> environments<00:11:03.010> where<00:11:03.280> essentially 00:11:04.230 --> 00:11:04.240 align:start position:0% execution environments where essentially 00:11:04.240 --> 00:11:06.960 align:start position:0% execution environments where essentially the<00:11:04.390> EVM<00:11:04.870> interpreter<00:11:05.560> written<00:11:06.040> as<00:11:06.190> wasum<00:11:06.820> can 00:11:06.960 --> 00:11:06.970 align:start position:0% the EVM interpreter written as wasum can 00:11:06.970 --> 00:11:08.940 align:start position:0% the EVM interpreter written as wasum can become<00:11:07.210> the<00:11:07.360> exec<00:11:07.690> code<00:11:08.380> within<00:11:08.710> this 00:11:08.940 --> 00:11:08.950 align:start position:0% become the exec code within this 00:11:08.950 --> 00:11:10.980 align:start position:0% become the exec code within this execution<00:11:09.310> environment<00:11:09.880> and<00:11:10.000> the<00:11:10.600> state 00:11:10.980 --> 00:11:10.990 align:start position:0% execution environment and the state 00:11:10.990 --> 00:11:12.810 align:start position:0% execution environment and the state route<00:11:11.350> the<00:11:11.620> existing<00:11:12.010> current<00:11:12.400> state<00:11:12.640> route 00:11:12.810 --> 00:11:12.820 align:start position:0% route the existing current state route 00:11:12.820 --> 00:11:14.490 align:start position:0% route the existing current state route within<00:11:13.030> eath<00:11:13.300> one<00:11:13.510> would<00:11:13.780> be<00:11:13.900> forked<00:11:14.170> in<00:11:14.290> here 00:11:14.490 --> 00:11:14.500 align:start position:0% within eath one would be forked in here 00:11:14.500 --> 00:11:16.590 align:start position:0% within eath one would be forked in here along<00:11:14.680> with<00:11:14.860> the<00:11:14.950> ether<00:11:15.190> balances<00:11:15.610> there's<00:11:16.570> a 00:11:16.590 --> 00:11:16.600 align:start position:0% along with the ether balances there's a 00:11:16.600 --> 00:11:19.460 align:start position:0% along with the ether balances there's a lot<00:11:16.720> of<00:11:16.840> work<00:11:16.990> going<00:11:17.260> on<00:11:17.530> on<00:11:18.450> evaluating 00:11:19.460 --> 00:11:19.470 align:start position:0% lot of work going on on evaluating 00:11:19.470 --> 00:11:22.710 align:start position:0% lot of work going on on evaluating evaluating<00:11:20.470> stateless<00:11:20.860> execution<00:11:21.660> trying<00:11:22.660> to 00:11:22.710 --> 00:11:22.720 align:start position:0% evaluating stateless execution trying to 00:11:22.720 --> 00:11:24.390 align:start position:0% evaluating stateless execution trying to understand<00:11:23.110> and<00:11:23.380> capture<00:11:23.710> the<00:11:23.800> complexity<00:11:24.280> of 00:11:24.390 --> 00:11:24.400 align:start position:0% understand and capture the complexity of 00:11:24.400 --> 00:11:27.690 align:start position:0% understand and capture the complexity of each<00:11:25.090> one<00:11:25.480> as<00:11:25.720> an<00:11:25.930> ee<00:11:26.160> and<00:11:27.160> there's<00:11:27.310> a<00:11:27.370> there's 00:11:27.690 --> 00:11:27.700 align:start position:0% each one as an ee and there's a there's 00:11:27.700 --> 00:11:31.260 align:start position:0% each one as an ee and there's a there's a<00:11:27.820> workshop<00:11:28.630> I<00:11:28.810> think<00:11:29.700> it's<00:11:30.700> a<00:11:30.790> couple<00:11:31.240> of 00:11:31.260 --> 00:11:31.270 align:start position:0% a workshop I think it's a couple of 00:11:31.270 --> 00:11:32.550 align:start position:0% a workshop I think it's a couple of walls<00:11:31.450> and<00:11:31.630> workshops<00:11:31.960> in<00:11:32.110> the<00:11:32.140> last<00:11:32.380> day 00:11:32.550 --> 00:11:32.560 align:start position:0% walls and workshops in the last day 00:11:32.560 --> 00:11:34.350 align:start position:0% walls and workshops in the last day there's<00:11:32.770> a<00:11:32.830> fishbowl<00:11:33.490> conversation<00:11:34.150> about 00:11:34.350 --> 00:11:34.360 align:start position:0% there's a fishbowl conversation about 00:11:34.360 --> 00:11:38.160 align:start position:0% there's a fishbowl conversation about all<00:11:34.540> of<00:11:34.630> this<00:11:34.780> so<00:11:35.500> check<00:11:35.710> it<00:11:35.800> out<00:11:35.860> cool<00:11:36.810> a<00:11:37.810> lot 00:11:38.160 --> 00:11:38.170 align:start position:0% all of this so check it out cool a lot 00:11:38.170 --> 00:11:40.380 align:start position:0% all of this so check it out cool a lot of<00:11:38.260> work<00:11:38.380> going<00:11:38.530> on<00:11:38.620> a<00:11:38.680> light<00:11:38.860> clients<00:11:39.270> we<00:11:40.270> have 00:11:40.380 --> 00:11:40.390 align:start position:0% of work going on a light clients we have 00:11:40.390 --> 00:11:42.330 align:start position:0% of work going on a light clients we have a<00:11:40.420> super<00:11:40.810> light<00:11:40.960> sync<00:11:41.260> protocol<00:11:41.710> on<00:11:42.010> the<00:11:42.100> order 00:11:42.330 --> 00:11:42.340 align:start position:0% a super light sync protocol on the order 00:11:42.340 --> 00:11:44.880 align:start position:0% a super light sync protocol on the order overhead<00:11:42.760> of<00:11:42.880> Bitcoin<00:11:43.210> SP<00:11:43.620> been<00:11:44.620> a<00:11:44.650> lot<00:11:44.800> of 00:11:44.880 --> 00:11:44.890 align:start position:0% overhead of Bitcoin SP been a lot of 00:11:44.890 --> 00:11:46.830 align:start position:0% overhead of Bitcoin SP been a lot of work<00:11:45.010> on<00:11:45.160> incentivized<00:11:45.700> servers<00:11:46.240> Zolt<00:11:46.630> is 00:11:46.830 --> 00:11:46.840 align:start position:0% work on incentivized servers Zolt is 00:11:46.840 --> 00:11:48.830 align:start position:0% work on incentivized servers Zolt is giving<00:11:47.110> a<00:11:47.170> talk<00:11:47.380> soon<00:11:47.710> after<00:11:47.950> this<00:11:48.100> about<00:11:48.400> that 00:11:48.830 --> 00:11:48.840 align:start position:0% giving a talk soon after this about that 00:11:48.840 --> 00:11:51.000 align:start position:0% giving a talk soon after this about that starting<00:11:49.840> now<00:11:50.020> let's<00:11:50.050> starts<00:11:50.680> been<00:11:50.800> digging 00:11:51.000 --> 00:11:51.010 align:start position:0% starting now let's starts been digging 00:11:51.010 --> 00:11:53.070 align:start position:0% starting now let's starts been digging into<00:11:51.160> it<00:11:51.310> and<00:11:51.610> there's<00:11:51.790> a<00:11:51.850> lot<00:11:51.970> of<00:11:52.120> le<00:11:52.570> s<00:11:52.840> work 00:11:53.070 --> 00:11:53.080 align:start position:0% into it and there's a lot of le s work 00:11:53.080 --> 00:11:55.320 align:start position:0% into it and there's a lot of le s work that<00:11:53.350> will<00:11:53.470> inform<00:11:53.800> he's<00:11:54.040> to<00:11:54.250> learn<00:11:55.150> more 00:11:55.320 --> 00:11:55.330 align:start position:0% that will inform he's to learn more 00:11:55.330 --> 00:12:00.680 align:start position:0% that will inform he's to learn more there's<00:11:55.600> some<00:11:55.750> talks<00:11:57.540> the<00:11:58.540> client<00:11:59.470> journey<00:11:59.800> a 00:12:00.680 --> 00:12:00.690 align:start position:0% there's some talks the client journey a 00:12:00.690 --> 00:12:03.990 align:start position:0% there's some talks the client journey a lot<00:12:01.690> has<00:12:02.230> transpired<00:12:02.740> in<00:12:03.430> the<00:12:03.490> past<00:12:03.700> year 00:12:03.990 --> 00:12:04.000 align:start position:0% lot has transpired in the past year 00:12:04.000 --> 00:12:07.650 align:start position:0% lot has transpired in the past year we've<00:12:04.600> gone<00:12:04.810> around<00:12:05.020> son<00:12:05.320> once<00:12:05.560> and<00:12:06.660> clients 00:12:07.650 --> 00:12:07.660 align:start position:0% we've gone around son once and clients 00:12:07.660 --> 00:12:11.210 align:start position:0% we've gone around son once and clients have<00:12:07.780> also<00:12:07.930> gone<00:12:08.320> from<00:12:09.270> early<00:12:10.270> legend 00:12:11.210 --> 00:12:11.220 align:start position:0% have also gone from early legend 00:12:11.220 --> 00:12:13.410 align:start position:0% have also gone from early legend prototypes<00:12:12.220> into<00:12:12.580> what<00:12:12.880> are<00:12:13.030> beginning<00:12:13.270> to 00:12:13.410 --> 00:12:13.420 align:start position:0% prototypes into what are beginning to 00:12:13.420 --> 00:12:17.340 align:start position:0% prototypes into what are beginning to look<00:12:13.540> like<00:12:13.600> production<00:12:14.410> grade<00:12:14.970> systems<00:12:16.350> the 00:12:17.340 --> 00:12:17.350 align:start position:0% look like production grade systems the 00:12:17.350 --> 00:12:19.740 align:start position:0% look like production grade systems the journey<00:12:17.740> was<00:12:18.190> as<00:12:18.640> you<00:12:19.210> if<00:12:19.480> you've<00:12:19.600> been 00:12:19.740 --> 00:12:19.750 align:start position:0% journey was as you if you've been 00:12:19.750 --> 00:12:21.120 align:start position:0% journey was as you if you've been following<00:12:19.900> it<00:12:20.260> was<00:12:20.380> difficult<00:12:20.560> for<00:12:20.830> a<00:12:20.980> while 00:12:21.120 --> 00:12:21.130 align:start position:0% following it was difficult for a while 00:12:21.130 --> 00:12:22.950 align:start position:0% following it was difficult for a while because<00:12:21.370> they<00:12:21.700> were<00:12:21.760> beginning<00:12:22.060> to<00:12:22.330> work<00:12:22.720> as 00:12:22.950 --> 00:12:22.960 align:start position:0% because they were beginning to work as 00:12:22.960 --> 00:12:25.620 align:start position:0% because they were beginning to work as we<00:12:23.530> were<00:12:23.680> still<00:12:23.920> writing<00:12:24.190> specifications<00:12:24.630> but 00:12:25.620 --> 00:12:25.630 align:start position:0% we were still writing specifications but 00:12:25.630 --> 00:12:27.630 align:start position:0% we were still writing specifications but as<00:12:25.750> I<00:12:25.870> said<00:12:26.110> we've<00:12:26.410> definitely<00:12:27.010> moved<00:12:27.400> into 00:12:27.630 --> 00:12:27.640 align:start position:0% as I said we've definitely moved into 00:12:27.640 --> 00:12:29.580 align:start position:0% as I said we've definitely moved into that<00:12:27.850> production<00:12:28.480> engineering<00:12:28.990> phase<00:12:29.230> for 00:12:29.580 --> 00:12:29.590 align:start position:0% that production engineering phase for 00:12:29.590 --> 00:12:32.580 align:start position:0% that production engineering phase for phase<00:12:29.770> zero<00:12:30.540> something<00:12:31.590> particularly 00:12:32.580 --> 00:12:32.590 align:start position:0% phase zero something particularly 00:12:32.590 --> 00:12:33.960 align:start position:0% phase zero something particularly exciting<00:12:33.010> that<00:12:33.160> happened<00:12:33.190> recently<00:12:33.550> was 00:12:33.960 --> 00:12:33.970 align:start position:0% exciting that happened recently was 00:12:33.970 --> 00:12:36.180 align:start position:0% exciting that happened recently was interrupt<00:12:34.540> Thank<00:12:34.900> You<00:12:35.050> Joseph<00:12:35.560> DeLong<00:12:35.920> and 00:12:36.180 --> 00:12:36.190 align:start position:0% interrupt Thank You Joseph DeLong and 00:12:36.190 --> 00:12:38.880 align:start position:0% interrupt Thank You Joseph DeLong and consensus<00:12:36.760> for<00:12:37.360> putting<00:12:37.630> this<00:12:37.720> on<00:12:37.900> at<00:12:38.620> the 00:12:38.880 --> 00:12:38.890 align:start position:0% consensus for putting this on at the 00:12:38.890 --> 00:12:40.890 align:start position:0% consensus for putting this on at the time<00:12:39.250> when<00:12:39.610> they<00:12:39.700> came<00:12:39.880> up<00:12:40.030> with<00:12:40.060> the<00:12:40.210> idea<00:12:40.540> I 00:12:40.890 --> 00:12:40.900 align:start position:0% time when they came up with the idea I 00:12:40.900 --> 00:12:42.630 align:start position:0% time when they came up with the idea I was<00:12:41.290> a<00:12:41.320> little<00:12:41.530> skeptical<00:12:41.800> it<00:12:42.250> sounded<00:12:42.580> a 00:12:42.630 --> 00:12:42.640 align:start position:0% was a little skeptical it sounded a 00:12:42.640 --> 00:12:44.130 align:start position:0% was a little skeptical it sounded a little<00:12:42.700> bit<00:12:42.910> crazy<00:12:43.150> and<00:12:43.270> I<00:12:43.480> wasn't<00:12:43.630> sure<00:12:43.810> if<00:12:44.050> it 00:12:44.130 --> 00:12:44.140 align:start position:0% little bit crazy and I wasn't sure if it 00:12:44.140 --> 00:12:45.300 align:start position:0% little bit crazy and I wasn't sure if it was<00:12:44.230> going<00:12:44.380> to<00:12:44.440> actually<00:12:44.800> be<00:12:44.890> a<00:12:44.920> good<00:12:45.160> use<00:12:45.280> of 00:12:45.300 --> 00:12:45.310 align:start position:0% was going to actually be a good use of 00:12:45.310 --> 00:12:48.510 align:start position:0% was going to actually be a good use of our<00:12:45.520> time<00:12:45.960> by<00:12:46.960> day<00:12:47.020> two<00:12:47.350> we<00:12:48.010> were<00:12:48.190> quite 00:12:48.510 --> 00:12:48.520 align:start position:0% our time by day two we were quite 00:12:48.520 --> 00:12:50.580 align:start position:0% our time by day two we were quite ecstatic<00:12:49.210> about<00:12:49.420> being<00:12:49.840> all<00:12:49.990> together<00:12:50.140> and 00:12:50.580 --> 00:12:50.590 align:start position:0% ecstatic about being all together and 00:12:50.590 --> 00:12:52.500 align:start position:0% ecstatic about being all together and getting<00:12:51.430> things<00:12:51.550> to<00:12:51.730> Interop<00:12:52.000> because<00:12:52.330> we 00:12:52.500 --> 00:12:52.510 align:start position:0% getting things to Interop because we 00:12:52.510 --> 00:12:55.620 align:start position:0% getting things to Interop because we were<00:12:52.630> making<00:12:52.980> incredible<00:12:53.980> progress<00:12:54.270> so<00:12:55.270> I 00:12:55.620 --> 00:12:55.630 align:start position:0% were making incredible progress so I 00:12:55.630 --> 00:12:57.210 align:start position:0% were making incredible progress so I think<00:12:55.900> all<00:12:56.110> seven<00:12:56.440> clients<00:12:56.740> that<00:12:56.860> showed<00:12:57.040> up 00:12:57.210 --> 00:12:57.220 align:start position:0% think all seven clients that showed up 00:12:57.220 --> 00:12:59.640 align:start position:0% think all seven clients that showed up successfully<00:12:57.960> interrupts<00:12:58.960> I<00:12:59.290> think<00:12:59.500> that's 00:12:59.640 --> 00:12:59.650 align:start position:0% successfully interrupts I think that's 00:12:59.650 --> 00:13:03.140 align:start position:0% successfully interrupts I think that's actually<00:12:59.970> five<00:13:00.970> of<00:13:01.360> them<00:13:01.600> right<00:13:01.630> there<00:13:02.050> and 00:13:03.140 --> 00:13:03.150 align:start position:0% actually five of them right there and 00:13:03.150 --> 00:13:05.610 align:start position:0% actually five of them right there and parody<00:13:04.150> Jasper<00:13:04.600> which<00:13:04.810> could<00:13:05.140> not<00:13:05.350> be<00:13:05.530> in 00:13:05.610 --> 00:13:05.620 align:start position:0% parody Jasper which could not be in 00:13:05.620 --> 00:13:07.290 align:start position:0% parody Jasper which could not be in attendance<00:13:05.800> has<00:13:06.190> also<00:13:06.580> begun<00:13:06.940> to<00:13:07.150> work 00:13:07.290 --> 00:13:07.300 align:start position:0% attendance has also begun to work 00:13:07.300 --> 00:13:10.590 align:start position:0% attendance has also begun to work through<00:13:07.480> some<00:13:07.600> of<00:13:07.720> these<00:13:07.810> exercises<00:13:09.600> beyond 00:13:10.590 --> 00:13:10.600 align:start position:0% through some of these exercises beyond 00:13:10.600 --> 00:13:11.160 align:start position:0% through some of these exercises beyond that 00:13:11.160 --> 00:13:11.170 align:start position:0% that 00:13:11.170 --> 00:13:13.110 align:start position:0% that discussions<00:13:11.680> on<00:13:11.829> sink<00:13:12.160> and<00:13:12.430> ironing<00:13:13.029> out 00:13:13.110 --> 00:13:13.120 align:start position:0% discussions on sink and ironing out 00:13:13.120 --> 00:13:16.650 align:start position:0% discussions on sink and ironing out other<00:13:13.360> cornets<00:13:14.019> of<00:13:14.139> the<00:13:14.200> protocol<00:13:15.360> fun<00:13:16.360> little 00:13:16.650 --> 00:13:16.660 align:start position:0% other cornets of the protocol fun little 00:13:16.660 --> 00:13:19.230 align:start position:0% other cornets of the protocol fun little side<00:13:16.899> projects<00:13:17.500> I<00:13:17.620> think<00:13:17.860> we<00:13:18.399> had<00:13:18.550> a<00:13:18.579> test<00:13:18.910> net 00:13:19.230 --> 00:13:19.240 align:start position:0% side projects I think we had a test net 00:13:19.240 --> 00:13:23.100 align:start position:0% side projects I think we had a test net with<00:13:20.670> 2000<00:13:21.670> validators<00:13:22.360> on<00:13:22.540> a<00:13:22.570> few<00:13:22.779> different 00:13:23.100 --> 00:13:23.110 align:start position:0% with 2000 validators on a few different 00:13:23.110 --> 00:13:24.900 align:start position:0% with 2000 validators on a few different machines<00:13:23.440> which<00:13:23.920> was<00:13:24.070> particularly<00:13:24.430> exciting 00:13:24.900 --> 00:13:24.910 align:start position:0% machines which was particularly exciting 00:13:24.910 --> 00:13:27.150 align:start position:0% machines which was particularly exciting so<00:13:25.060> some<00:13:25.240> initial<00:13:25.540> load<00:13:25.720> testing<00:13:26.260> and<00:13:26.620> this 00:13:27.150 --> 00:13:27.160 align:start position:0% so some initial load testing and this 00:13:27.160 --> 00:13:28.860 align:start position:0% so some initial load testing and this was<00:13:27.310> a<00:13:27.339> fun<00:13:27.579> one<00:13:27.760> this<00:13:27.940> is<00:13:28.060> a<00:13:28.089> couple<00:13:28.389> raspberry 00:13:28.860 --> 00:13:28.870 align:start position:0% was a fun one this is a couple raspberry 00:13:28.870 --> 00:13:31.410 align:start position:0% was a fun one this is a couple raspberry PI's<00:13:29.110> on<00:13:29.529> a<00:13:29.589> small<00:13:30.190> network<00:13:31.000> with<00:13:31.180> deacon 00:13:31.410 --> 00:13:31.420 align:start position:0% PI's on a small network with deacon 00:13:31.420 --> 00:13:34.290 align:start position:0% PI's on a small network with deacon chains<00:13:31.660> running<00:13:31.990> on<00:13:32.079> them<00:13:32.290> mommy<00:13:33.279> later<00:13:34.029> today 00:13:34.290 --> 00:13:34.300 align:start position:0% chains running on them mommy later today 00:13:34.300 --> 00:13:37.439 align:start position:0% chains running on them mommy later today I<00:13:34.449> think<00:13:34.750> on<00:13:35.130> this<00:13:36.130> stage<00:13:36.399> is<00:13:36.940> giving<00:13:37.209> a<00:13:37.269> talk 00:13:37.439 --> 00:13:37.449 align:start position:0% I think on this stage is giving a talk 00:13:37.449 --> 00:13:38.759 align:start position:0% I think on this stage is giving a talk about<00:13:37.720> the<00:13:37.810> Raspberry<00:13:38.170> Pi<00:13:38.199> it<00:13:38.380> should<00:13:38.680> be<00:13:38.740> a 00:13:38.759 --> 00:13:38.769 align:start position:0% about the Raspberry Pi it should be a 00:13:38.769 --> 00:13:40.710 align:start position:0% about the Raspberry Pi it should be a pretty<00:13:39.070> fun<00:13:39.250> one<00:13:39.310> it's<00:13:39.970> about<00:13:40.060> like<00:13:40.360> the<00:13:40.540> load 00:13:40.710 --> 00:13:40.720 align:start position:0% pretty fun one it's about like the load 00:13:40.720 --> 00:13:43.379 align:start position:0% pretty fun one it's about like the load of<00:13:41.050> eath<00:13:41.829> -<00:13:42.100> and<00:13:42.459> the<00:13:42.519> expected<00:13:42.760> requirements 00:13:43.379 --> 00:13:43.389 align:start position:0% of eath - and the expected requirements 00:13:43.389 --> 00:13:44.610 align:start position:0% of eath - and the expected requirements and<00:13:43.510> actually<00:13:43.750> getting<00:13:43.959> it<00:13:44.050> to<00:13:44.139> run<00:13:44.290> and<00:13:44.440> build 00:13:44.610 --> 00:13:44.620 align:start position:0% and actually getting it to run and build 00:13:44.620 --> 00:13:48.990 align:start position:0% and actually getting it to run and build on<00:13:44.800> these<00:13:45.190> small<00:13:46.120> devices<00:13:47.040> so<00:13:48.040> what<00:13:48.459> is<00:13:48.639> coming 00:13:48.990 --> 00:13:49.000 align:start position:0% on these small devices so what is coming 00:13:49.000 --> 00:13:54.509 align:start position:0% on these small devices so what is coming up<00:13:49.180> for<00:13:49.570> clients<00:13:50.579> optimizations<00:13:51.579> so<00:13:53.490> one<00:13:54.490> of 00:13:54.509 --> 00:13:54.519 align:start position:0% up for clients optimizations so one of 00:13:54.519 --> 00:13:57.720 align:start position:0% up for clients optimizations so one of the<00:13:54.940> I<00:13:55.540> think<00:13:56.050> probably<00:13:56.320> the<00:13:56.680> the<00:13:57.010> most 00:13:57.720 --> 00:13:57.730 align:start position:0% the I think probably the the most 00:13:57.730 --> 00:13:59.460 align:start position:0% the I think probably the the most obvious<00:13:58.149> place<00:13:58.329> for<00:13:58.360> optimizations<00:13:59.050> is<00:13:59.230> first 00:13:59.460 --> 00:13:59.470 align:start position:0% obvious place for optimizations is first 00:13:59.470 --> 00:14:02.639 align:start position:0% obvious place for optimizations is first BLS<00:14:00.310> signature<00:14:00.940> processing<00:14:01.510> we<00:14:02.019> process<00:14:02.470> a 00:14:02.639 --> 00:14:02.649 align:start position:0% BLS signature processing we process a 00:14:02.649 --> 00:14:03.840 align:start position:0% BLS signature processing we process a lot<00:14:02.860> of<00:14:02.949> signatures<00:14:03.399> we<00:14:03.550> have<00:14:03.639> a<00:14:03.699> lot<00:14:03.820> of 00:14:03.840 --> 00:14:03.850 align:start position:0% lot of signatures we have a lot of 00:14:03.850 --> 00:14:05.250 align:start position:0% lot of signatures we have a lot of validators<00:14:04.420> and<00:14:04.600> even<00:14:04.899> though<00:14:04.990> we<00:14:05.110> can 00:14:05.250 --> 00:14:05.260 align:start position:0% validators and even though we can 00:14:05.260 --> 00:14:06.900 align:start position:0% validators and even though we can aggregate<00:14:05.470> these<00:14:05.920> signatures<00:14:06.399> that's<00:14:06.639> still 00:14:06.900 --> 00:14:06.910 align:start position:0% aggregate these signatures that's still 00:14:06.910 --> 00:14:09.689 align:start position:0% aggregate these signatures that's still a<00:14:06.970> high<00:14:07.300> source<00:14:07.660> of<00:14:07.839> load<00:14:08.019> so<00:14:08.920> we've<00:14:09.430> seen 00:14:09.689 --> 00:14:09.699 align:start position:0% a high source of load so we've seen 00:14:09.699 --> 00:14:11.490 align:start position:0% a high source of load so we've seen people<00:14:09.940> begin<00:14:10.510> to<00:14:10.660> open<00:14:10.810> up<00:14:11.019> the<00:14:11.170> BLS 00:14:11.490 --> 00:14:11.500 align:start position:0% people begin to open up the BLS 00:14:11.500 --> 00:14:14.040 align:start position:0% people begin to open up the BLS implementations<00:14:12.220> and<00:14:12.490> optimize<00:14:13.300> optimize 00:14:14.040 --> 00:14:14.050 align:start position:0% implementations and optimize optimize 00:14:14.050 --> 00:14:16.319 align:start position:0% implementations and optimize optimize them<00:14:14.260> seeing<00:14:14.620> some<00:14:14.920> gains<00:14:15.760> order<00:14:16.269> of 00:14:16.319 --> 00:14:16.329 align:start position:0% them seeing some gains order of 00:14:16.329 --> 00:14:21.509 align:start position:0% them seeing some gains order of magnitude<00:14:16.690> gains<00:14:16.930> there<00:14:18.510> what<00:14:19.510> else<00:14:19.810> the<00:14:20.519> tree 00:14:21.509 --> 00:14:21.519 align:start position:0% magnitude gains there what else the tree 00:14:21.519 --> 00:14:22.740 align:start position:0% magnitude gains there what else the tree hashing<00:14:21.910> structure<00:14:22.360> we<00:14:22.480> have<00:14:22.570> a<00:14:22.600> lot<00:14:22.720> of 00:14:22.740 --> 00:14:22.750 align:start position:0% hashing structure we have a lot of 00:14:22.750 --> 00:14:24.540 align:start position:0% hashing structure we have a lot of hashing<00:14:23.140> that<00:14:23.260> goes<00:14:23.410> on<00:14:23.589> and<00:14:23.800> if<00:14:24.190> you<00:14:24.310> do<00:14:24.430> it 00:14:24.540 --> 00:14:24.550 align:start position:0% hashing that goes on and if you do it 00:14:24.550 --> 00:14:26.759 align:start position:0% hashing that goes on and if you do it naively<00:14:25.029> it<00:14:25.570> takes<00:14:25.750> an<00:14:26.050> incredible<00:14:26.260> amount<00:14:26.589> of 00:14:26.759 --> 00:14:26.769 align:start position:0% naively it takes an incredible amount of 00:14:26.769 --> 00:14:28.560 align:start position:0% naively it takes an incredible amount of load<00:14:26.949> but<00:14:27.220> fortunately<00:14:27.760> much<00:14:28.060> of<00:14:28.269> the<00:14:28.360> tree 00:14:28.560 --> 00:14:28.570 align:start position:0% load but fortunately much of the tree 00:14:28.570 --> 00:14:30.480 align:start position:0% load but fortunately much of the tree doesn't<00:14:28.899> change<00:14:29.110> this<00:14:29.529> is<00:14:29.709> a<00:14:29.740> lot<00:14:29.920> of<00:14:30.040> caching 00:14:30.480 --> 00:14:30.490 align:start position:0% doesn't change this is a lot of caching 00:14:30.490 --> 00:14:33.569 align:start position:0% doesn't change this is a lot of caching optimizations<00:14:31.209> going<00:14:31.600> on<00:14:32.339> stabilized<00:14:33.339> we 00:14:33.569 --> 00:14:33.579 align:start position:0% optimizations going on stabilized we 00:14:33.579 --> 00:14:34.829 align:start position:0% optimizations going on stabilized we need<00:14:33.699> to<00:14:33.760> bring<00:14:33.910> these<00:14:34.000> things<00:14:34.060> towards 00:14:34.829 --> 00:14:34.839 align:start position:0% need to bring these things towards 00:14:34.839 --> 00:14:37.590 align:start position:0% need to bring these things towards production<00:14:35.649> stability<00:14:36.279> and<00:14:36.670> grade<00:14:36.970> such<00:14:37.360> that 00:14:37.590 --> 00:14:37.600 align:start position:0% production stability and grade such that 00:14:37.600 --> 00:14:39.800 align:start position:0% production stability and grade such that they<00:14:37.990> can<00:14:38.170> run<00:14:38.519> essentially<00:14:39.519> forever 00:14:39.800 --> 00:14:39.810 align:start position:0% they can run essentially forever 00:14:39.810 --> 00:14:44.220 align:start position:0% they can run essentially forever unstopped<00:14:40.829> and<00:14:41.880> usability<00:14:42.880> eyes<00:14:43.120> that's<00:14:43.959> not 00:14:44.220 --> 00:14:44.230 align:start position:0% unstopped and usability eyes that's not 00:14:44.230 --> 00:14:48.569 align:start position:0% unstopped and usability eyes that's not a<00:14:44.260> word<00:14:44.470> but<00:14:44.709> the<00:14:45.690> usability<00:14:46.690> UX<00:14:47.579> getting 00:14:48.569 --> 00:14:48.579 align:start position:0% a word but the usability UX getting 00:14:48.579 --> 00:14:50.370 align:start position:0% a word but the usability UX getting these<00:14:48.699> hands<00:14:49.120> getting<00:14:49.449> these<00:14:49.930> things<00:14:50.170> in<00:14:50.290> the 00:14:50.370 --> 00:14:50.380 align:start position:0% these hands getting these things in the 00:14:50.380 --> 00:14:52.620 align:start position:0% these hands getting these things in the hands<00:14:50.589> of<00:14:50.680> users<00:14:50.829> and<00:14:51.790> making<00:14:52.029> them<00:14:52.269> actual 00:14:52.620 --> 00:14:52.630 align:start position:0% hands of users and making them actual 00:14:52.630 --> 00:14:55.769 align:start position:0% hands of users and making them actual products<00:14:53.199> is<00:14:54.100> instead<00:14:55.000> of<00:14:55.060> command-line 00:14:55.769 --> 00:14:55.779 align:start position:0% products is instead of command-line 00:14:55.779 --> 00:14:57.750 align:start position:0% products is instead of command-line tools<00:14:56.079> that<00:14:56.440> someone<00:14:57.100> that<00:14:57.250> built<00:14:57.430> them<00:14:57.550> can 00:14:57.750 --> 00:14:57.760 align:start position:0% tools that someone that built them can 00:14:57.760 --> 00:15:01.170 align:start position:0% tools that someone that built them can sophisticatedly<00:14:58.420> use<00:14:58.660> more<00:14:59.529> usable<00:15:00.010> and<00:15:00.190> real 00:15:01.170 --> 00:15:01.180 align:start position:0% sophisticatedly use more usable and real 00:15:01.180 --> 00:15:03.600 align:start position:0% sophisticatedly use more usable and real products<00:15:01.510> there's<00:15:01.990> good<00:15:02.310> some<00:15:03.310> people<00:15:03.519> are 00:15:03.600 --> 00:15:03.610 align:start position:0% products there's good some people are 00:15:03.610 --> 00:15:05.040 align:start position:0% products there's good some people are actually<00:15:03.699> doing<00:15:04.000> some<00:15:04.300> independent<00:15:04.779> work<00:15:04.810> on 00:15:05.040 --> 00:15:05.050 align:start position:0% actually doing some independent work on 00:15:05.050 --> 00:15:07.470 align:start position:0% actually doing some independent work on validator<00:15:05.500> clients<00:15:05.890> right<00:15:06.040> now<00:15:06.120> to<00:15:07.120> actually 00:15:07.470 --> 00:15:07.480 align:start position:0% validator clients right now to actually 00:15:07.480 --> 00:15:09.930 align:start position:0% validator clients right now to actually like<00:15:07.630> make<00:15:07.959> nice<00:15:08.560> buoys<00:15:09.040> and<00:15:09.310> there's<00:15:09.790> some 00:15:09.930 --> 00:15:09.940 align:start position:0% like make nice buoys and there's some 00:15:09.940 --> 00:15:14.519 align:start position:0% like make nice buoys and there's some promising<00:15:10.630> things<00:15:10.810> in<00:15:10.990> that<00:15:11.139> respect<00:15:13.529> this 00:15:14.519 --> 00:15:14.529 align:start position:0% promising things in that respect this 00:15:14.529 --> 00:15:19.500 align:start position:0% promising things in that respect this guy<00:15:17.279> right<00:15:18.279> so<00:15:18.490> we're<00:15:18.639> also<00:15:18.760> doing<00:15:18.970> some 00:15:19.500 --> 00:15:19.510 align:start position:0% guy right so we're also doing some 00:15:19.510 --> 00:15:24.160 align:start position:0% guy right so we're also doing some fuzzing<00:15:19.779> efforts<00:15:20.430> guido<00:15:22.140> recently<00:15:23.140> a<00:15:23.560> while 00:15:24.160 --> 00:15:24.170 align:start position:0% fuzzing efforts guido recently a while 00:15:24.170 --> 00:15:25.750 align:start position:0% fuzzing efforts guido recently a while built<00:15:24.529> out<00:15:24.680> kind<00:15:24.920> of<00:15:24.980> a<00:15:25.040> core<00:15:25.250> infrastructure 00:15:25.750 --> 00:15:25.760 align:start position:0% built out kind of a core infrastructure 00:15:25.760 --> 00:15:27.730 align:start position:0% built out kind of a core infrastructure for<00:15:26.120> handling<00:15:26.389> differentials<00:15:27.230> buzzing<00:15:27.620> of 00:15:27.730 --> 00:15:27.740 align:start position:0% for handling differentials buzzing of 00:15:27.740 --> 00:15:30.009 align:start position:0% for handling differentials buzzing of clients<00:15:28.250> and<00:15:28.910> recently<00:15:29.269> mehdi<00:15:29.570> from 00:15:30.009 --> 00:15:30.019 align:start position:0% clients and recently mehdi from 00:15:30.019 --> 00:15:31.540 align:start position:0% clients and recently mehdi from lighthouse<00:15:30.500> has<00:15:30.920> taken<00:15:31.220> over<00:15:31.279> that 00:15:31.540 --> 00:15:31.550 align:start position:0% lighthouse has taken over that 00:15:31.550 --> 00:15:34.240 align:start position:0% lighthouse has taken over that integrated<00:15:32.389> a<00:15:32.450> couple<00:15:32.720> clients<00:15:32.870> in<00:15:33.200> and<00:15:34.100> it's 00:15:34.240 --> 00:15:34.250 align:start position:0% integrated a couple clients in and it's 00:15:34.250 --> 00:15:36.790 align:start position:0% integrated a couple clients in and it's figuring<00:15:34.579> out<00:15:34.670> how<00:15:34.850> to<00:15:34.959> randomly<00:15:35.959> throw<00:15:36.470> all 00:15:36.790 --> 00:15:36.800 align:start position:0% figuring out how to randomly throw all 00:15:36.800 --> 00:15:39.250 align:start position:0% figuring out how to randomly throw all sorts<00:15:37.130> of<00:15:37.220> junk<00:15:37.519> at<00:15:37.790> these<00:15:38.360> clients<00:15:38.870> to<00:15:39.050> see 00:15:39.250 --> 00:15:39.260 align:start position:0% sorts of junk at these clients to see 00:15:39.260 --> 00:15:43.389 align:start position:0% sorts of junk at these clients to see that<00:15:39.620> they<00:15:39.769> all<00:15:41.050> handle<00:15:42.050> these<00:15:42.199> crazy<00:15:42.920> inputs 00:15:43.389 --> 00:15:43.399 align:start position:0% that they all handle these crazy inputs 00:15:43.399 --> 00:15:45.610 align:start position:0% that they all handle these crazy inputs the<00:15:43.550> same<00:15:43.760> what<00:15:44.389> this<00:15:44.540> does<00:15:44.720> is<00:15:44.959> it<00:15:45.110> takes<00:15:45.290> we 00:15:45.610 --> 00:15:45.620 align:start position:0% the same what this does is it takes we 00:15:45.620 --> 00:15:47.170 align:start position:0% the same what this does is it takes we have<00:15:45.709> our<00:15:45.829> consensus<00:15:46.279> tests<00:15:46.579> where<00:15:46.970> all<00:15:47.029> the 00:15:47.170 --> 00:15:47.180 align:start position:0% have our consensus tests where all the 00:15:47.180 --> 00:15:48.759 align:start position:0% have our consensus tests where all the all<00:15:47.480> the<00:15:47.600> scenarios<00:15:47.839> that<00:15:48.019> we<00:15:48.199> could<00:15:48.440> think<00:15:48.589> of 00:15:48.759 --> 00:15:48.769 align:start position:0% all the scenarios that we could think of 00:15:48.769 --> 00:15:52.030 align:start position:0% all the scenarios that we could think of but<00:15:49.839> fortunately<00:15:50.839> with<00:15:51.199> randomization<00:15:51.829> we 00:15:52.030 --> 00:15:52.040 align:start position:0% but fortunately with randomization we 00:15:52.040 --> 00:15:53.079 align:start position:0% but fortunately with randomization we can<00:15:52.160> come<00:15:52.279> up<00:15:52.370> with<00:15:52.490> all<00:15:52.550> sorts<00:15:52.579> scenarios 00:15:53.079 --> 00:15:53.089 align:start position:0% can come up with all sorts scenarios 00:15:53.089 --> 00:15:55.090 align:start position:0% can come up with all sorts scenarios that<00:15:53.209> we<00:15:53.269> didn't<00:15:53.540> think<00:15:53.630> of<00:15:53.810> and<00:15:54.050> find<00:15:54.860> the 00:15:55.090 --> 00:15:55.100 align:start position:0% that we didn't think of and find the 00:15:55.100 --> 00:15:59.050 align:start position:0% that we didn't think of and find the edge<00:15:55.250> cases<00:15:55.610> before<00:15:56.000> production<00:15:57.100> so<00:15:58.100> what's 00:15:59.050 --> 00:15:59.060 align:start position:0% edge cases before production so what's 00:15:59.060 --> 00:15:59.470 align:start position:0% edge cases before production so what's next 00:15:59.470 --> 00:15:59.480 align:start position:0% next 00:15:59.480 --> 00:16:02.740 align:start position:0% next as<00:15:59.769> i<00:16:00.769> mentioned<00:16:01.209> we're<00:16:02.209> moving<00:16:02.510> we're<00:16:02.660> in 00:16:02.740 --> 00:16:02.750 align:start position:0% as i mentioned we're moving we're in 00:16:02.750 --> 00:16:03.939 align:start position:0% as i mentioned we're moving we're in that<00:16:02.899> production<00:16:03.199> phase<00:16:03.500> we're<00:16:03.740> removing 00:16:03.939 --> 00:16:03.949 align:start position:0% that production phase we're removing 00:16:03.949 --> 00:16:06.490 align:start position:0% that production phase we're removing phase<00:16:04.459> zero<00:16:04.760> towards<00:16:05.180> production<00:16:05.510> a<00:16:05.839> lot<00:16:06.380> of 00:16:06.490 --> 00:16:06.500 align:start position:0% phase zero towards production a lot of 00:16:06.500 --> 00:16:08.379 align:start position:0% phase zero towards production a lot of the<00:16:06.620> conversation<00:16:07.310> since<00:16:07.579> Interop<00:16:08.000> has<00:16:08.209> been 00:16:08.379 --> 00:16:08.389 align:start position:0% the conversation since Interop has been 00:16:08.389 --> 00:16:11.230 align:start position:0% the conversation since Interop has been about<00:16:09.699> continued<00:16:10.699> test<00:16:10.910> nuts 00:16:11.230 --> 00:16:11.240 align:start position:0% about continued test nuts 00:16:11.240 --> 00:16:14.079 align:start position:0% about continued test nuts so<00:16:11.600> both<00:16:11.810> private<00:16:12.470> doing<00:16:13.310> some<00:16:13.519> private<00:16:13.880> load 00:16:14.079 --> 00:16:14.089 align:start position:0% so both private doing some private load 00:16:14.089 --> 00:16:17.980 align:start position:0% so both private doing some private load tests<00:16:14.630> on<00:16:14.839> clients<00:16:15.709> but<00:16:16.459> also<00:16:16.870> opening<00:16:17.870> up 00:16:17.980 --> 00:16:17.990 align:start position:0% tests on clients but also opening up 00:16:17.990 --> 00:16:20.259 align:start position:0% tests on clients but also opening up towards<00:16:18.410> public<00:16:18.769> test<00:16:18.980> nuts<00:16:19.220> and<00:16:19.459> incentivize 00:16:20.259 --> 00:16:20.269 align:start position:0% towards public test nuts and incentivize 00:16:20.269 --> 00:16:23.620 align:start position:0% towards public test nuts and incentivize test<00:16:20.660> nuts<00:16:21.220> so<00:16:22.220> keep<00:16:22.850> your<00:16:22.970> eyes<00:16:23.149> peeled<00:16:23.540> for 00:16:23.620 --> 00:16:23.630 align:start position:0% test nuts so keep your eyes peeled for 00:16:23.630 --> 00:16:25.660 align:start position:0% test nuts so keep your eyes peeled for that<00:16:23.810> if<00:16:24.230> you're<00:16:24.560> thinking<00:16:25.220> about<00:16:25.310> being<00:16:25.519> a 00:16:25.660 --> 00:16:25.670 align:start position:0% that if you're thinking about being a 00:16:25.670 --> 00:16:27.670 align:start position:0% that if you're thinking about being a validator<00:16:26.149> this<00:16:26.779> is<00:16:26.959> your<00:16:27.110> handi<00:16:27.350> your<00:16:27.470> chance 00:16:27.670 --> 00:16:27.680 align:start position:0% validator this is your handi your chance 00:16:27.680 --> 00:16:30.069 align:start position:0% validator this is your handi your chance to<00:16:27.829> get<00:16:27.889> your<00:16:28.040> hands<00:16:28.220> dirty<00:16:28.339> and<00:16:29.209> be<00:16:29.750> in<00:16:29.930> an 00:16:30.069 --> 00:16:30.079 align:start position:0% to get your hands dirty and be in an 00:16:30.079 --> 00:16:31.990 align:start position:0% to get your hands dirty and be in an active<00:16:30.320> when<00:16:30.980> these<00:16:31.100> public<00:16:31.430> test<00:16:31.610> sets<00:16:31.790> come 00:16:31.990 --> 00:16:32.000 align:start position:0% active when these public test sets come 00:16:32.000 --> 00:16:34.540 align:start position:0% active when these public test sets come out<00:16:32.120> be<00:16:32.750> an<00:16:32.839> active<00:16:33.199> participant<00:16:33.620> if<00:16:34.370> it 00:16:34.540 --> 00:16:34.550 align:start position:0% out be an active participant if it 00:16:34.550 --> 00:16:36.610 align:start position:0% out be an active participant if it doesn't<00:16:34.850> work<00:16:34.970> tell<00:16:35.630> somebody<00:16:35.959> if<00:16:36.199> it's<00:16:36.380> hard 00:16:36.610 --> 00:16:36.620 align:start position:0% doesn't work tell somebody if it's hard 00:16:36.620 --> 00:16:39.639 align:start position:0% doesn't work tell somebody if it's hard to<00:16:36.709> install<00:16:37.070> file<00:16:37.790> an<00:16:37.970> issue<00:16:38.089> like<00:16:38.750> if<00:16:39.019> you 00:16:39.639 --> 00:16:39.649 align:start position:0% to install file an issue like if you 00:16:39.649 --> 00:16:41.110 align:start position:0% to install file an issue like if you have<00:16:39.860> an<00:16:39.949> idea<00:16:40.279> for<00:16:40.339> increasing<00:16:41.029> the 00:16:41.110 --> 00:16:41.120 align:start position:0% have an idea for increasing the 00:16:41.120 --> 00:16:43.600 align:start position:0% have an idea for increasing the usability<00:16:41.480> either<00:16:42.339> open<00:16:43.339> up<00:16:43.399> an<00:16:43.519> issue 00:16:43.600 --> 00:16:43.610 align:start position:0% usability either open up an issue 00:16:43.610 --> 00:16:48.730 align:start position:0% usability either open up an issue suggesting<00:16:44.300> it<00:16:44.420> or<00:16:44.690> go<00:16:45.140> and<00:16:45.320> fix<00:16:45.440> it<00:16:45.620> so<00:16:47.740> this 00:16:48.730 --> 00:16:48.740 align:start position:0% suggesting it or go and fix it so this 00:16:48.740 --> 00:16:51.519 align:start position:0% suggesting it or go and fix it so this is<00:16:48.890> definitely<00:16:49.220> an<00:16:49.760> exciting<00:16:50.390> time<00:16:50.779> this<00:16:51.170> this 00:16:51.519 --> 00:16:51.529 align:start position:0% is definitely an exciting time this this 00:16:51.529 --> 00:16:53.650 align:start position:0% is definitely an exciting time this this last<00:16:51.980> mile<00:16:52.459> getting<00:16:53.240> these<00:16:53.360> things<00:16:53.570> to 00:16:53.650 --> 00:16:53.660 align:start position:0% last mile getting these things to 00:16:53.660 --> 00:16:55.269 align:start position:0% last mile getting these things to production<00:16:53.930> so<00:16:54.079> be<00:16:54.410> active<00:16:54.769> and<00:16:55.070> be<00:16:55.130> engaged 00:16:55.269 --> 00:16:55.279 align:start position:0% production so be active and be engaged 00:16:55.279 --> 00:17:00.819 align:start position:0% production so be active and be engaged with<00:16:55.579> it<00:16:56.440> phase<00:16:57.440> one<00:16:57.709> and<00:16:57.829> two<00:16:57.949> rd<00:16:59.290> the<00:17:00.290> specs 00:17:00.819 --> 00:17:00.829 align:start position:0% with it phase one and two rd the specs 00:17:00.829 --> 00:17:04.510 align:start position:0% with it phase one and two rd the specs for<00:17:01.670> phase<00:17:01.970> one<00:17:02.240> are<00:17:02.829> coming<00:17:03.829> i<00:17:03.980> mean<00:17:04.160> they're 00:17:04.510 --> 00:17:04.520 align:start position:0% for phase one are coming i mean they're 00:17:04.520 --> 00:17:05.679 align:start position:0% for phase one are coming i mean they're they're<00:17:04.819> they're<00:17:05.120> in<00:17:05.150> a<00:17:05.270> place<00:17:05.449> in<00:17:05.600> which 00:17:05.679 --> 00:17:05.689 align:start position:0% they're they're in a place in which 00:17:05.689 --> 00:17:08.620 align:start position:0% they're they're in a place in which people<00:17:05.959> are<00:17:06.049> prototyping<00:17:07.059> props<00:17:08.059> the<00:17:08.360> quilt 00:17:08.620 --> 00:17:08.630 align:start position:0% people are prototyping props the quilt 00:17:08.630 --> 00:17:11.110 align:start position:0% people are prototyping props the quilt team<00:17:08.839> yesterday<00:17:09.290> they<00:17:09.470> did<00:17:09.620> a<00:17:09.650> demo<00:17:10.069> of<00:17:10.120> phase 00:17:11.110 --> 00:17:11.120 align:start position:0% team yesterday they did a demo of phase 00:17:11.120 --> 00:17:13.539 align:start position:0% team yesterday they did a demo of phase one<00:17:11.390> and<00:17:11.689> a<00:17:11.809> minimal<00:17:12.169> phase<00:17:12.380> two<00:17:12.740> built<00:17:13.130> on<00:17:13.339> top 00:17:13.539 --> 00:17:13.549 align:start position:0% one and a minimal phase two built on top 00:17:13.549 --> 00:17:17.980 align:start position:0% one and a minimal phase two built on top of<00:17:13.610> lighthouse<00:17:14.169> and<00:17:15.169> beyond<00:17:15.620> that<00:17:16.000> a<00:17:17.000> lot<00:17:17.959> of 00:17:17.980 --> 00:17:17.990 align:start position:0% of lighthouse and beyond that a lot of 00:17:17.990 --> 00:17:20.079 align:start position:0% of lighthouse and beyond that a lot of work<00:17:18.230> going<00:17:18.439> on<00:17:18.709> just<00:17:19.160> kind<00:17:19.429> of<00:17:19.459> refining<00:17:19.970> this 00:17:20.079 --> 00:17:20.089 align:start position:0% work going on just kind of refining this 00:17:20.089 --> 00:17:22.299 align:start position:0% work going on just kind of refining this idea<00:17:20.449> of<00:17:20.750> execution<00:17:21.319> environments<00:17:21.860> it's 00:17:22.299 --> 00:17:22.309 align:start position:0% idea of execution environments it's 00:17:22.309 --> 00:17:24.850 align:start position:0% idea of execution environments it's quite<00:17:22.549> a<00:17:22.579> blind<00:17:22.939> a<00:17:23.179> large<00:17:23.510> design<00:17:23.929> space<00:17:24.260> so 00:17:24.850 --> 00:17:24.860 align:start position:0% quite a blind a large design space so 00:17:24.860 --> 00:17:26.620 align:start position:0% quite a blind a large design space so we're<00:17:24.980> trying<00:17:25.189> to<00:17:25.339> hone<00:17:25.520> that<00:17:25.549> in<00:17:26.179> the<00:17:26.360> coming 00:17:26.620 --> 00:17:26.630 align:start position:0% we're trying to hone that in the coming 00:17:26.630 --> 00:17:30.640 align:start position:0% we're trying to hone that in the coming months<00:17:27.910> developer<00:17:28.910> tooling<00:17:29.270> and<00:17:29.630> dialogue<00:17:30.140> so 00:17:30.640 --> 00:17:30.650 align:start position:0% months developer tooling and dialogue so 00:17:30.650 --> 00:17:33.700 align:start position:0% months developer tooling and dialogue so as<00:17:31.040> Casey<00:17:31.940> from<00:17:32.690> wasman<00:17:33.080> likes<00:17:33.260> to<00:17:33.350> say<00:17:33.530> this 00:17:33.700 --> 00:17:33.710 align:start position:0% as Casey from wasman likes to say this 00:17:33.710 --> 00:17:35.880 align:start position:0% as Casey from wasman likes to say this this<00:17:34.340> needs<00:17:34.549> to<00:17:34.640> be<00:17:34.700> a<00:17:34.730> humanistic 00:17:35.880 --> 00:17:35.890 align:start position:0% this needs to be a humanistic 00:17:35.890 --> 00:17:38.100 align:start position:0% this needs to be a humanistic humanist<00:17:36.220> process<00:17:36.730> a<00:17:36.760> human<00:17:37.120> focused<00:17:37.600> process 00:17:38.100 --> 00:17:38.110 align:start position:0% humanist process a human focused process 00:17:38.110 --> 00:17:40.200 align:start position:0% humanist process a human focused process the<00:17:38.320> reason<00:17:38.650> that<00:17:38.800> aetherium<00:17:39.550> is<00:17:39.610> so<00:17:39.760> great<00:17:39.970> is 00:17:40.200 --> 00:17:40.210 align:start position:0% the reason that aetherium is so great is 00:17:40.210 --> 00:17:42.180 align:start position:0% the reason that aetherium is so great is the<00:17:40.240> developer's<00:17:40.990> unity<00:17:41.650> that<00:17:41.770> we<00:17:41.890> have<00:17:42.040> out 00:17:42.180 --> 00:17:42.190 align:start position:0% the developer's unity that we have out 00:17:42.190 --> 00:17:44.910 align:start position:0% the developer's unity that we have out here<00:17:42.270> and<00:17:43.270> so<00:17:43.450> making<00:17:44.020> sure<00:17:44.470> that<00:17:44.740> the 00:17:44.910 --> 00:17:44.920 align:start position:0% here and so making sure that the 00:17:44.920 --> 00:17:47.840 align:start position:0% here and so making sure that the transition<00:17:45.550> from<00:17:45.730> eighth<00:17:46.030> one<00:17:46.300> to<00:17:46.510> eath<00:17:46.690> two 00:17:47.840 --> 00:17:47.850 align:start position:0% transition from eighth one to eath two 00:17:47.850 --> 00:17:50.700 align:start position:0% transition from eighth one to eath two enables<00:17:48.850> and<00:17:49.150> enhances<00:17:49.750> the<00:17:50.140> experience<00:17:50.620> of 00:17:50.700 --> 00:17:50.710 align:start position:0% enables and enhances the experience of 00:17:50.710 --> 00:17:53.310 align:start position:0% enables and enhances the experience of developers<00:17:51.220> is<00:17:51.880> very<00:17:52.090> important<00:17:52.540> if<00:17:52.990> this 00:17:53.310 --> 00:17:53.320 align:start position:0% developers is very important if this 00:17:53.320 --> 00:17:55.350 align:start position:0% developers is very important if this goes<00:17:53.620> according<00:17:54.610> to<00:17:54.820> plan 00:17:55.350 --> 00:17:55.360 align:start position:0% goes according to plan 00:17:55.360 --> 00:17:57.570 align:start position:0% goes according to plan we<00:17:55.630> can<00:17:55.780> kind<00:17:55.930> of<00:17:56.020> rewire<00:17:56.530> and<00:17:56.950> rework<00:17:57.280> some<00:17:57.520> of 00:17:57.570 --> 00:17:57.580 align:start position:0% we can kind of rewire and rework some of 00:17:57.580 --> 00:17:59.340 align:start position:0% we can kind of rewire and rework some of the<00:17:57.670> interfaces<00:17:58.300> and<00:17:58.630> things<00:17:58.690> the<00:17:59.140> things 00:17:59.340 --> 00:17:59.350 align:start position:0% the interfaces and things the things 00:17:59.350 --> 00:18:01.860 align:start position:0% the interfaces and things the things behind<00:17:59.590> and<00:18:00.100> underneath<00:18:00.490> our<00:18:01.180> current<00:18:01.630> tools 00:18:01.860 --> 00:18:01.870 align:start position:0% behind and underneath our current tools 00:18:01.870 --> 00:18:05.040 align:start position:0% behind and underneath our current tools and<00:18:02.290> developer<00:18:02.800> interfaces<00:18:03.750> such<00:18:04.750> that 00:18:05.040 --> 00:18:05.050 align:start position:0% and developer interfaces such that 00:18:05.050 --> 00:18:06.990 align:start position:0% and developer interfaces such that developers<00:18:05.740> can<00:18:05.860> continue<00:18:06.250> using<00:18:06.550> the<00:18:06.790> things 00:18:06.990 --> 00:18:07.000 align:start position:0% developers can continue using the things 00:18:07.000 --> 00:18:08.700 align:start position:0% developers can continue using the things that<00:18:07.210> they<00:18:07.330> use<00:18:07.540> to<00:18:07.870> continue<00:18:08.170> building<00:18:08.440> on 00:18:08.700 --> 00:18:08.710 align:start position:0% that they use to continue building on 00:18:08.710 --> 00:18:12.870 align:start position:0% that they use to continue building on ethereum<00:18:08.980> and<00:18:09.280> making<00:18:09.850> it<00:18:09.910> great<00:18:11.820> here's<00:18:12.820> a 00:18:12.870 --> 00:18:12.880 align:start position:0% ethereum and making it great here's a 00:18:12.880 --> 00:18:14.520 align:start position:0% ethereum and making it great here's a quick<00:18:13.060> glance<00:18:13.240> at<00:18:13.480> you<00:18:13.600> to<00:18:13.810> track<00:18:14.110> i'm<00:18:14.380> sure 00:18:14.520 --> 00:18:14.530 align:start position:0% quick glance at you to track i'm sure 00:18:14.530 --> 00:18:15.780 align:start position:0% quick glance at you to track i'm sure you<00:18:14.620> have<00:18:14.770> it<00:18:14.860> in<00:18:14.950> your<00:18:15.010> hat<00:18:15.190> but<00:18:15.490> there's<00:18:15.730> a 00:18:15.780 --> 00:18:15.790 align:start position:0% you have it in your hat but there's a 00:18:15.790 --> 00:18:18.240 align:start position:0% you have it in your hat but there's a quick<00:18:16.330> view<00:18:16.570> if<00:18:16.660> you<00:18:16.750> want<00:18:16.960> it<00:18:17.080> lots<00:18:17.860> of<00:18:18.040> fun 00:18:18.240 --> 00:18:18.250 align:start position:0% quick view if you want it lots of fun 00:18:18.250 --> 00:18:20.100 align:start position:0% quick view if you want it lots of fun stuff<00:18:18.280> putting<00:18:19.120> it<00:18:19.210> to<00:18:19.390> to<00:18:19.510> work<00:18:19.660> that<00:18:20.020> should 00:18:20.100 --> 00:18:20.110 align:start position:0% stuff putting it to to work that should 00:18:20.110 --> 00:18:22.080 align:start position:0% stuff putting it to to work that should be<00:18:20.200> fun<00:18:20.440> checking<00:18:21.100> out<00:18:21.220> how<00:18:21.700> we<00:18:21.760> can<00:18:21.940> use 00:18:22.080 --> 00:18:22.090 align:start position:0% be fun checking out how we can use 00:18:22.090 --> 00:18:24.690 align:start position:0% be fun checking out how we can use finality<00:18:22.960> on<00:18:23.260> eighth<00:18:23.590> one<00:18:23.860> to<00:18:24.250> enhance<00:18:24.520> the 00:18:24.690 --> 00:18:24.700 align:start position:0% finality on eighth one to enhance the 00:18:24.700 --> 00:18:29.580 align:start position:0% finality on eighth one to enhance the security<00:18:27.240> all<00:18:28.240> sorts<00:18:28.570> of<00:18:28.600> stuff<00:18:28.810> check<00:18:29.110> it<00:18:29.230> out 00:18:29.580 --> 00:18:29.590 align:start position:0% security all sorts of stuff check it out 00:18:29.590 --> 00:18:31.110 align:start position:0% security all sorts of stuff check it out I'll<00:18:29.740> be<00:18:29.920> at<00:18:30.010> the<00:18:30.040> phase<00:18:30.550> zero<00:18:30.760> deep<00:18:30.940> dive 00:18:31.110 --> 00:18:31.120 align:start position:0% I'll be at the phase zero deep dive 00:18:31.120 --> 00:18:34.110 align:start position:0% I'll be at the phase zero deep dive today<00:18:31.510> we'll<00:18:32.380> be<00:18:32.500> digging<00:18:32.920> into<00:18:33.100> I<00:18:33.760> know<00:18:34.030> I 00:18:34.110 --> 00:18:34.120 align:start position:0% today we'll be digging into I know I 00:18:34.120 --> 00:18:35.850 align:start position:0% today we'll be digging into I know I like<00:18:34.420> we<00:18:34.690> do<00:18:34.780> this<00:18:34.930> high-level<00:18:35.140> thing<00:18:35.620> where 00:18:35.850 --> 00:18:35.860 align:start position:0% like we do this high-level thing where 00:18:35.860 --> 00:18:38.610 align:start position:0% like we do this high-level thing where we<00:18:35.950> just<00:18:36.100> show<00:18:36.310> it<00:18:36.460> all<00:18:36.930> where<00:18:37.930> I<00:18:37.960> kind<00:18:38.440> of<00:18:38.470> go 00:18:38.610 --> 00:18:38.620 align:start position:0% we just show it all where I kind of go 00:18:38.620 --> 00:18:40.020 align:start position:0% we just show it all where I kind of go through<00:18:38.800> it<00:18:38.860> very<00:18:39.100> simply<00:18:39.430> but<00:18:39.700> we're<00:18:39.910> gonna 00:18:40.020 --> 00:18:40.030 align:start position:0% through it very simply but we're gonna 00:18:40.030 --> 00:18:41.580 align:start position:0% through it very simply but we're gonna dig<00:18:40.360> into<00:18:40.540> the<00:18:40.750> different<00:18:41.020> components<00:18:41.470> and 00:18:41.580 --> 00:18:41.590 align:start position:0% dig into the different components and 00:18:41.590 --> 00:18:43.140 align:start position:0% dig into the different components and help<00:18:41.980> you<00:18:42.070> read<00:18:42.310> and<00:18:42.490> understand<00:18:42.820> the<00:18:42.910> specs 00:18:43.140 --> 00:18:43.150 align:start position:0% help you read and understand the specs 00:18:43.150 --> 00:18:45.810 align:start position:0% help you read and understand the specs today<00:18:43.560> I<00:18:44.560> want<00:18:44.920> to<00:18:44.980> highlight<00:18:45.160> the<00:18:45.460> two<00:18:45.790> Oh 00:18:45.810 --> 00:18:45.820 align:start position:0% today I want to highlight the two Oh 00:18:45.820 --> 00:18:50.730 align:start position:0% today I want to highlight the two Oh client<00:18:46.570> summit<00:18:47.700> which<00:18:48.700> is<00:18:48.730> tomorrow<00:18:49.620> we<00:18:50.620> have 00:18:50.730 --> 00:18:50.740 align:start position:0% client summit which is tomorrow we have 00:18:50.740 --> 00:18:52.440 align:start position:0% client summit which is tomorrow we have a<00:18:50.800> number<00:18:51.160> of<00:18:51.340> clients<00:18:51.700> working<00:18:52.240> on<00:18:52.330> this 00:18:52.440 --> 00:18:52.450 align:start position:0% a number of clients working on this 00:18:52.450 --> 00:18:54.090 align:start position:0% a number of clients working on this problem<00:18:52.870> as<00:18:53.200> you're<00:18:53.410> aware<00:18:53.500> and<00:18:54.010> they're 00:18:54.090 --> 00:18:54.100 align:start position:0% problem as you're aware and they're 00:18:54.100 --> 00:18:56.160 align:start position:0% problem as you're aware and they're going<00:18:54.220> to<00:18:54.280> be<00:18:54.460> doing<00:18:55.300> these<00:18:55.600> like<00:18:55.780> twelve<00:18:56.080> to 00:18:56.160 --> 00:18:56.170 align:start position:0% going to be doing these like twelve to 00:18:56.170 --> 00:18:58.740 align:start position:0% going to be doing these like twelve to fifteen<00:18:56.290> minute<00:18:56.710> talks<00:18:57.750> discussing 00:18:58.740 --> 00:18:58.750 align:start position:0% fifteen minute talks discussing 00:18:58.750 --> 00:19:00.150 align:start position:0% fifteen minute talks discussing different<00:18:59.080> components<00:18:59.590> of<00:18:59.740> the<00:18:59.860> design 00:19:00.150 --> 00:19:00.160 align:start position:0% different components of the design 00:19:00.160 --> 00:19:02.730 align:start position:0% different components of the design different<00:19:00.550> challenges<00:19:01.030> at<00:19:01.210> hand<00:19:01.480> and<00:19:02.470> after 00:19:02.730 --> 00:19:02.740 align:start position:0% different challenges at hand and after 00:19:02.740 --> 00:19:05.340 align:start position:0% different challenges at hand and after that<00:19:03.370> there'll<00:19:03.940> be<00:19:03.970> a<00:19:04.060> panel<00:19:04.810> talking<00:19:05.050> about 00:19:05.340 --> 00:19:05.350 align:start position:0% that there'll be a panel talking about 00:19:05.350 --> 00:19:09.960 align:start position:0% that there'll be a panel talking about upcoming<00:19:05.530> tests<00:19:06.070> nuts<00:19:06.280> challenges<00:19:06.870> etc<00:19:08.970> it's 00:19:09.960 --> 00:19:09.970 align:start position:0% upcoming tests nuts challenges etc it's 00:19:09.970 --> 00:19:12.090 align:start position:0% upcoming tests nuts challenges etc it's all<00:19:10.060> I<00:19:10.120> got<00:19:10.300> for<00:19:10.510> you<00:19:10.570> today<00:19:10.950> build<00:19:11.950> in<00:19:12.010> the 00:19:12.090 --> 00:19:12.100 align:start position:0% all I got for you today build in the 00:19:12.100 --> 00:19:15.240 align:start position:0% all I got for you today build in the future<00:19:13.050> thanks<00:19:14.050> for<00:19:14.140> having<00:19:14.320> me 00:19:15.240 --> 00:19:15.250 align:start position:0% future thanks for having me 00:19:15.250 --> 00:19:25.680 align:start position:0% future thanks for having me [Applause] 00:19:25.680 --> 00:19:25.690 align:start position:0% 00:19:25.690 --> 00:19:27.750 align:start position:0% you