WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:13.509 align:start position:0% [Music] 00:00:13.509 --> 00:00:13.519 align:start position:0% 00:00:13.519 --> 00:00:16.670 align:start position:0% thanks<00:00:14.519> for<00:00:14.639> having<00:00:14.759> me<00:00:15.000> I'm<00:00:15.900> working<00:00:16.139> the<00:00:16.440> EF 00:00:16.670 --> 00:00:16.680 align:start position:0% thanks for having me I'm working the EF 00:00:16.680 --> 00:00:18.650 align:start position:0% thanks for having me I'm working the EF I<00:00:17.039> work<00:00:17.220> on<00:00:17.340> the<00:00:17.460> research<00:00:17.699> team<00:00:17.880> and<00:00:18.119> name<00:00:18.300> I 00:00:18.650 --> 00:00:18.660 align:start position:0% I work on the research team and name I 00:00:18.660 --> 00:00:20.650 align:start position:0% I work on the research team and name I do<00:00:18.779> a<00:00:18.900> lot<00:00:19.020> of<00:00:19.140> things<00:00:19.380> that<00:00:19.740> aren't<00:00:19.920> just<00:00:20.220> that 00:00:20.650 --> 00:00:20.660 align:start position:0% do a lot of things that aren't just that 00:00:20.660 --> 00:00:24.650 align:start position:0% do a lot of things that aren't just that but<00:00:21.660> you<00:00:22.560> know<00:00:22.680> here<00:00:23.279> we<00:00:23.460> go<00:00:23.580> so<00:00:24.000> resilience<00:00:24.480> I 00:00:24.650 --> 00:00:24.660 align:start position:0% but you know here we go so resilience I 00:00:24.660 --> 00:00:26.090 align:start position:0% but you know here we go so resilience I want<00:00:24.779> to<00:00:24.900> talk<00:00:24.960> about 00:00:26.090 --> 00:00:26.100 align:start position:0% want to talk about 00:00:26.100 --> 00:00:28.009 align:start position:0% want to talk about what<00:00:26.519> we<00:00:26.699> might<00:00:26.820> call<00:00:27.000> the<00:00:27.240> metagame<00:00:27.720> of 00:00:28.009 --> 00:00:28.019 align:start position:0% what we might call the metagame of 00:00:28.019 --> 00:00:29.509 align:start position:0% what we might call the metagame of ethereum<00:00:28.380> L1<00:00:28.680> we're<00:00:28.920> trying<00:00:29.039> to<00:00:29.160> ship<00:00:29.279> a<00:00:29.460> lot 00:00:29.509 --> 00:00:29.519 align:start position:0% ethereum L1 we're trying to ship a lot 00:00:29.519 --> 00:00:31.070 align:start position:0% ethereum L1 we're trying to ship a lot of<00:00:29.640> stuff<00:00:29.820> there's<00:00:30.539> a<00:00:30.660> lot<00:00:30.779> of<00:00:30.900> things 00:00:31.070 --> 00:00:31.080 align:start position:0% of stuff there's a lot of things 00:00:31.080 --> 00:00:33.350 align:start position:0% of stuff there's a lot of things underneath<00:00:31.859> the<00:00:32.220> hood<00:00:32.340> that<00:00:32.640> maybe<00:00:32.820> aren't 00:00:33.350 --> 00:00:33.360 align:start position:0% underneath the hood that maybe aren't 00:00:33.360 --> 00:00:35.030 align:start position:0% underneath the hood that maybe aren't quite<00:00:33.660> clear<00:00:33.899> that<00:00:34.260> that<00:00:34.440> are<00:00:34.620> being<00:00:34.739> worked 00:00:35.030 --> 00:00:35.040 align:start position:0% quite clear that that are being worked 00:00:35.040 --> 00:00:36.229 align:start position:0% quite clear that that are being worked on<00:00:35.100> and<00:00:35.280> thought<00:00:35.460> about<00:00:35.579> kind<00:00:35.880> of<00:00:35.940> at<00:00:36.059> all 00:00:36.229 --> 00:00:36.239 align:start position:0% on and thought about kind of at all 00:00:36.239 --> 00:00:38.150 align:start position:0% on and thought about kind of at all times 00:00:38.150 --> 00:00:38.160 align:start position:0% times 00:00:38.160 --> 00:00:40.069 align:start position:0% times I<00:00:38.700> did<00:00:38.940> ask<00:00:39.120> the<00:00:39.360> internet<00:00:39.480> what<00:00:39.780> should<00:00:39.960> I 00:00:40.069 --> 00:00:40.079 align:start position:0% I did ask the internet what should I 00:00:40.079 --> 00:00:42.830 align:start position:0% I did ask the internet what should I talk<00:00:40.200> about<00:00:40.320> Devcon<00:00:40.800> got<00:00:41.399> some<00:00:41.579> answers 00:00:42.830 --> 00:00:42.840 align:start position:0% talk about Devcon got some answers 00:00:42.840 --> 00:00:44.750 align:start position:0% talk about Devcon got some answers um L2<00:00:43.500> very<00:00:43.800> important<00:00:44.100> it's<00:00:44.280> gonna<00:00:44.399> be<00:00:44.579> a<00:00:44.640> lot 00:00:44.750 --> 00:00:44.760 align:start position:0% um L2 very important it's gonna be a lot 00:00:44.760 --> 00:00:46.850 align:start position:0% um L2 very important it's gonna be a lot of<00:00:44.940> stuff<00:00:45.059> to<00:00:45.180> talk<00:00:45.300> about<00:00:45.420> this<00:00:45.960> week<00:00:46.140> dig<00:00:46.559> in 00:00:46.850 --> 00:00:46.860 align:start position:0% of stuff to talk about this week dig in 00:00:46.860 --> 00:00:47.810 align:start position:0% of stuff to talk about this week dig in deep 00:00:47.810 --> 00:00:47.820 align:start position:0% deep 00:00:47.820 --> 00:00:49.729 align:start position:0% deep um<00:00:47.940> Hudson<00:00:48.360> if<00:00:48.660> you<00:00:48.840> want<00:00:48.960> to<00:00:49.079> talk<00:00:49.260> this 00:00:49.729 --> 00:00:49.739 align:start position:0% um Hudson if you want to talk this 00:00:49.739 --> 00:00:51.410 align:start position:0% um Hudson if you want to talk this evening<00:00:49.860> I<00:00:50.399> got<00:00:50.520> a<00:00:50.640> lot<00:00:50.700> we<00:00:50.879> can<00:00:51.059> we<00:00:51.239> can 00:00:51.410 --> 00:00:51.420 align:start position:0% evening I got a lot we can we can 00:00:51.420 --> 00:00:53.750 align:start position:0% evening I got a lot we can we can exchange<00:00:51.780> some<00:00:52.200> fun<00:00:52.440> stories 00:00:53.750 --> 00:00:53.760 align:start position:0% exchange some fun stories 00:00:53.760 --> 00:00:55.490 align:start position:0% exchange some fun stories Kevin 00:00:55.490 --> 00:00:55.500 align:start position:0% Kevin 00:00:55.500 --> 00:00:57.110 align:start position:0% Kevin um<00:00:55.559> I'm<00:00:55.860> glad<00:00:56.039> it's<00:00:56.219> worked<00:00:56.579> the<00:00:56.760> pseudonym 00:00:57.110 --> 00:00:57.120 align:start position:0% um I'm glad it's worked the pseudonym 00:00:57.120 --> 00:00:59.090 align:start position:0% um I'm glad it's worked the pseudonym has<00:00:57.539> fooled<00:00:57.899> everyone 00:00:59.090 --> 00:00:59.100 align:start position:0% has fooled everyone 00:00:59.100 --> 00:01:01.250 align:start position:0% has fooled everyone um<00:00:59.160> and<00:00:59.399> and<00:00:59.520> Johnny<00:00:59.820> Ray<00:01:00.180> I<00:01:00.840> won't<00:01:00.960> do<00:01:01.140> a 00:01:01.250 --> 00:01:01.260 align:start position:0% um and and Johnny Ray I won't do a 00:01:01.260 --> 00:01:03.049 align:start position:0% um and and Johnny Ray I won't do a handstand<00:01:01.500> up<00:01:01.739> here<00:01:01.860> but<00:01:02.039> I<00:01:02.280> love<00:01:02.399> handstands 00:01:03.049 --> 00:01:03.059 align:start position:0% handstand up here but I love handstands 00:01:03.059 --> 00:01:04.130 align:start position:0% handstand up here but I love handstands and<00:01:03.120> if<00:01:03.239> you<00:01:03.359> want<00:01:03.480> to<00:01:03.539> do<00:01:03.600> handstands<00:01:04.080> out 00:01:04.130 --> 00:01:04.140 align:start position:0% and if you want to do handstands out 00:01:04.140 --> 00:01:05.990 align:start position:0% and if you want to do handstands out there<00:01:04.320> uh<00:01:04.860> we<00:01:05.040> can<00:01:05.159> we<00:01:05.339> can<00:01:05.460> join<00:01:05.700> but<00:01:05.820> that's 00:01:05.990 --> 00:01:06.000 align:start position:0% there uh we can we can join but that's 00:01:06.000 --> 00:01:07.969 align:start position:0% there uh we can we can join but that's not<00:01:06.180> what<00:01:06.240> I'll<00:01:06.360> talk<00:01:06.540> about<00:01:06.659> today 00:01:07.969 --> 00:01:07.979 align:start position:0% not what I'll talk about today 00:01:07.979 --> 00:01:09.649 align:start position:0% not what I'll talk about today um<00:01:08.040> so<00:01:08.400> again 00:01:09.649 --> 00:01:09.659 align:start position:0% um so again 00:01:09.659 --> 00:01:11.630 align:start position:0% um so again being<00:01:10.260> listening<00:01:10.619> to<00:01:10.740> death<00:01:10.860> but<00:01:11.100> the<00:01:11.400> merch 00:01:11.630 --> 00:01:11.640 align:start position:0% being listening to death but the merch 00:01:11.640 --> 00:01:12.590 align:start position:0% being listening to death but the merch happened 00:01:12.590 --> 00:01:12.600 align:start position:0% happened 00:01:12.600 --> 00:01:17.450 align:start position:0% happened finally 00:01:17.450 --> 00:01:17.460 align:start position:0% 00:01:17.460 --> 00:01:19.370 align:start position:0% it<00:01:18.000> did<00:01:18.119> indeed<00:01:18.420> took<00:01:18.659> a<00:01:18.720> village<00:01:18.840> take<00:01:19.200> a 00:01:19.370 --> 00:01:19.380 align:start position:0% it did indeed took a village take a 00:01:19.380 --> 00:01:20.270 align:start position:0% it did indeed took a village take a village 00:01:20.270 --> 00:01:20.280 align:start position:0% village 00:01:20.280 --> 00:01:21.710 align:start position:0% village a<00:01:20.580> lot<00:01:20.700> of<00:01:20.820> those<00:01:20.880> people<00:01:21.060> are<00:01:21.180> up<00:01:21.299> here<00:01:21.479> a<00:01:21.659> lot 00:01:21.710 --> 00:01:21.720 align:start position:0% a lot of those people are up here a lot 00:01:21.720 --> 00:01:23.030 align:start position:0% a lot of those people are up here a lot of<00:01:21.840> people<00:01:22.020> are<00:01:22.140> out<00:01:22.320> in<00:01:22.560> the<00:01:22.680> stage<00:01:22.860> and 00:01:23.030 --> 00:01:23.040 align:start position:0% of people are out in the stage and 00:01:23.040 --> 00:01:24.469 align:start position:0% of people are out in the stage and they're<00:01:23.220> also<00:01:23.520> distributed<00:01:23.939> all<00:01:24.119> across<00:01:24.420> the 00:01:24.469 --> 00:01:24.479 align:start position:0% they're also distributed all across the 00:01:24.479 --> 00:01:26.950 align:start position:0% they're also distributed all across the world<00:01:24.600> thanks<00:01:25.140> guys 00:01:26.950 --> 00:01:26.960 align:start position:0% world thanks guys 00:01:26.960 --> 00:01:30.830 align:start position:0% world thanks guys quick<00:01:27.960> quick<00:01:27.960> just<00:01:28.740> like<00:01:28.979> perspective<00:01:29.939> on<00:01:30.540> on 00:01:30.830 --> 00:01:30.840 align:start position:0% quick quick just like perspective on on 00:01:30.840 --> 00:01:32.450 align:start position:0% quick quick just like perspective on on what<00:01:31.380> happened 00:01:32.450 --> 00:01:32.460 align:start position:0% what happened 00:01:32.460 --> 00:01:33.109 align:start position:0% what happened um 00:01:33.109 --> 00:01:33.119 align:start position:0% um 00:01:33.119 --> 00:01:35.810 align:start position:0% um it's<00:01:33.479> been<00:01:33.720> a<00:01:33.840> bit<00:01:33.960> of<00:01:34.020> a<00:01:34.140> non-event<00:01:34.740> which<00:01:35.640> is 00:01:35.810 --> 00:01:35.820 align:start position:0% it's been a bit of a non-event which is 00:01:35.820 --> 00:01:37.969 align:start position:0% it's been a bit of a non-event which is good<00:01:36.060> it's<00:01:36.420> good<00:01:36.720> that's<00:01:36.900> how<00:01:37.439> it's<00:01:37.619> designed 00:01:37.969 --> 00:01:37.979 align:start position:0% good it's good that's how it's designed 00:01:37.979 --> 00:01:39.950 align:start position:0% good it's good that's how it's designed we<00:01:38.400> can<00:01:38.520> kind<00:01:38.700> of<00:01:38.820> see 00:01:39.950 --> 00:01:39.960 align:start position:0% we can kind of see 00:01:39.960 --> 00:01:41.690 align:start position:0% we can kind of see um<00:01:40.079> in<00:01:40.380> that<00:01:40.500> little<00:01:40.680> Spike<00:01:41.040> towards<00:01:41.460> there's 00:01:41.690 --> 00:01:41.700 align:start position:0% um in that little Spike towards there's 00:01:41.700 --> 00:01:43.550 align:start position:0% um in that little Spike towards there's two<00:01:41.880> little<00:01:42.060> spikes<00:01:42.479> at<00:01:42.840> the<00:01:43.020> end<00:01:43.079> and<00:01:43.500> it 00:01:43.550 --> 00:01:43.560 align:start position:0% two little spikes at the end and it 00:01:43.560 --> 00:01:44.749 align:start position:0% two little spikes at the end and it looks<00:01:43.740> like<00:01:43.860> participation<00:01:44.340> kind<00:01:44.579> of<00:01:44.700> fell 00:01:44.749 --> 00:01:44.759 align:start position:0% looks like participation kind of fell 00:01:44.759 --> 00:01:46.130 align:start position:0% looks like participation kind of fell off<00:01:44.939> a<00:01:45.060> cliff<00:01:45.240> real<00:01:45.420> quick<00:01:45.600> right<00:01:45.780> around<00:01:45.960> the 00:01:46.130 --> 00:01:46.140 align:start position:0% off a cliff real quick right around the 00:01:46.140 --> 00:01:48.890 align:start position:0% off a cliff real quick right around the merge<00:01:46.439> picked<00:01:47.040> up<00:01:47.159> went<00:01:47.939> back<00:01:48.180> down<00:01:48.360> it's<00:01:48.720> been 00:01:48.890 --> 00:01:48.900 align:start position:0% merge picked up went back down it's been 00:01:48.900 --> 00:01:51.109 align:start position:0% merge picked up went back down it's been kind<00:01:49.020> of<00:01:49.140> leveling<00:01:49.500> off<00:01:49.619> and<00:01:49.799> figuring<00:01:50.100> out 00:01:51.109 --> 00:01:51.119 align:start position:0% kind of leveling off and figuring out 00:01:51.119 --> 00:01:52.310 align:start position:0% kind of leveling off and figuring out um 00:01:52.310 --> 00:01:52.320 align:start position:0% um 00:01:52.320 --> 00:01:54.889 align:start position:0% um I<00:01:52.860> think<00:01:52.979> it's<00:01:53.159> worth<00:01:53.460> zooming<00:01:54.119> out<00:01:54.360> because 00:01:54.889 --> 00:01:54.899 align:start position:0% I think it's worth zooming out because 00:01:54.899 --> 00:02:00.469 align:start position:0% I think it's worth zooming out because like<00:01:55.399> this<00:01:56.399> this<00:01:57.299> starts<00:01:57.780> at<00:01:57.899> 94<00:01:58.700> not<00:01:59.700> at<00:02:00.060> zero 00:02:00.469 --> 00:02:00.479 align:start position:0% like this this starts at 94 not at zero 00:02:00.479 --> 00:02:02.270 align:start position:0% like this this starts at 94 not at zero this<00:02:01.079> is<00:02:01.200> actually<00:02:01.439> what<00:02:01.740> participation 00:02:02.270 --> 00:02:02.280 align:start position:0% this is actually what participation 00:02:02.280 --> 00:02:04.010 align:start position:0% this is actually what participation looks<00:02:02.700> like<00:02:02.759> there's<00:02:03.180> a<00:02:03.420> gap<00:02:03.540> because<00:02:03.780> our 00:02:04.010 --> 00:02:04.020 align:start position:0% looks like there's a gap because our 00:02:04.020 --> 00:02:05.690 align:start position:0% looks like there's a gap because our infra<00:02:04.500> wasn't<00:02:04.860> collecting<00:02:05.280> at<00:02:05.399> that<00:02:05.520> point 00:02:05.690 --> 00:02:05.700 align:start position:0% infra wasn't collecting at that point 00:02:05.700 --> 00:02:08.630 align:start position:0% infra wasn't collecting at that point but<00:02:06.060> it's<00:02:06.960> it's<00:02:07.200> pretty<00:02:07.560> damn<00:02:07.799> good<00:02:08.039> when<00:02:08.520> the 00:02:08.630 --> 00:02:08.640 align:start position:0% but it's it's pretty damn good when the 00:02:08.640 --> 00:02:10.910 align:start position:0% but it's it's pretty damn good when the system<00:02:08.819> was<00:02:09.060> designed<00:02:09.420> years<00:02:09.660> ago<00:02:09.959> we<00:02:10.679> we 00:02:10.910 --> 00:02:10.920 align:start position:0% system was designed years ago we we 00:02:10.920 --> 00:02:12.229 align:start position:0% system was designed years ago we we didn't<00:02:11.099> know<00:02:11.280> what<00:02:11.459> participation<00:02:12.000> would 00:02:12.229 --> 00:02:12.239 align:start position:0% didn't know what participation would 00:02:12.239 --> 00:02:14.150 align:start position:0% didn't know what participation would look<00:02:12.360> like<00:02:12.480> we'd<00:02:12.780> think<00:02:12.959> okay<00:02:13.620> so<00:02:13.860> normally 00:02:14.150 --> 00:02:14.160 align:start position:0% look like we'd think okay so normally 00:02:14.160 --> 00:02:15.229 align:start position:0% look like we'd think okay so normally it's<00:02:14.280> going<00:02:14.400> to<00:02:14.459> be<00:02:14.520> above<00:02:14.760> two-thirds 00:02:15.229 --> 00:02:15.239 align:start position:0% it's going to be above two-thirds 00:02:15.239 --> 00:02:16.790 align:start position:0% it's going to be above two-thirds normally<00:02:15.599> people<00:02:15.840> are<00:02:16.020> the<00:02:16.319> incentives<00:02:16.680> are 00:02:16.790 --> 00:02:16.800 align:start position:0% normally people are the incentives are 00:02:16.800 --> 00:02:17.869 align:start position:0% normally people are the incentives are such<00:02:16.980> that<00:02:17.160> people<00:02:17.340> are<00:02:17.459> gonna<00:02:17.580> turn<00:02:17.760> their 00:02:17.869 --> 00:02:17.879 align:start position:0% such that people are gonna turn their 00:02:17.879 --> 00:02:18.890 align:start position:0% such that people are gonna turn their machines<00:02:18.120> on<00:02:18.239> and<00:02:18.420> make<00:02:18.540> sure<00:02:18.660> that<00:02:18.780> we're 00:02:18.890 --> 00:02:18.900 align:start position:0% machines on and make sure that we're 00:02:18.900 --> 00:02:21.050 align:start position:0% machines on and make sure that we're finalizing<00:02:19.500> uh<00:02:19.980> but<00:02:20.160> we<00:02:20.220> thought 00:02:21.050 --> 00:02:21.060 align:start position:0% finalizing uh but we thought 00:02:21.060 --> 00:02:24.050 align:start position:0% finalizing uh but we thought 70<00:02:21.780> 80<00:02:22.140> 85<00:02:22.739> would<00:02:23.160> be<00:02:23.280> like<00:02:23.520> kind<00:02:23.760> of<00:02:23.879> normal 00:02:24.050 --> 00:02:24.060 align:start position:0% 70 80 85 would be like kind of normal 00:02:24.060 --> 00:02:25.970 align:start position:0% 70 80 85 would be like kind of normal but<00:02:24.480> really<00:02:24.660> like<00:02:24.900> people<00:02:25.020> are<00:02:25.260> turns<00:02:25.680> out<00:02:25.739> are 00:02:25.970 --> 00:02:25.980 align:start position:0% but really like people are turns out are 00:02:25.980 --> 00:02:29.570 align:start position:0% but really like people are turns out are extremely<00:02:26.879> obsessive<00:02:27.480> about<00:02:28.200> every<00:02:28.860> last 00:02:29.570 --> 00:02:29.580 align:start position:0% extremely obsessive about every last 00:02:29.580 --> 00:02:31.850 align:start position:0% extremely obsessive about every last attestation<00:02:30.480> I<00:02:30.900> got<00:02:31.080> some<00:02:31.200> laughs<00:02:31.500> up<00:02:31.680> here 00:02:31.850 --> 00:02:31.860 align:start position:0% attestation I got some laughs up here 00:02:31.860 --> 00:02:33.890 align:start position:0% attestation I got some laughs up here because<00:02:32.040> uh<00:02:32.520> if<00:02:32.879> you<00:02:33.000> if<00:02:33.300> you're<00:02:33.480> on<00:02:33.599> a<00:02:33.780> client 00:02:33.890 --> 00:02:33.900 align:start position:0% because uh if you if you're on a client 00:02:33.900 --> 00:02:35.869 align:start position:0% because uh if you if you're on a client Discord<00:02:34.319> it's<00:02:34.620> like<00:02:34.800> somebody<00:02:35.340> misses<00:02:35.760> one 00:02:35.869 --> 00:02:35.879 align:start position:0% Discord it's like somebody misses one 00:02:35.879 --> 00:02:37.250 align:start position:0% Discord it's like somebody misses one out<00:02:36.060> of<00:02:36.239> station<00:02:36.420> in<00:02:36.660> a<00:02:36.780> month<00:02:36.900> they're<00:02:37.080> like 00:02:37.250 --> 00:02:37.260 align:start position:0% out of station in a month they're like 00:02:37.260 --> 00:02:39.170 align:start position:0% out of station in a month they're like what's<00:02:37.379> wrong<00:02:37.620> with<00:02:37.800> my<00:02:37.980> machine 00:02:39.170 --> 00:02:39.180 align:start position:0% what's wrong with my machine 00:02:39.180 --> 00:02:42.650 align:start position:0% what's wrong with my machine um<00:02:39.720> but<00:02:40.140> anyway<00:02:40.260> shit's<00:02:41.040> pretty<00:02:41.160> good<00:02:41.340> like 00:02:42.650 --> 00:02:42.660 align:start position:0% um but anyway shit's pretty good like 00:02:42.660 --> 00:02:44.690 align:start position:0% um but anyway shit's pretty good like and<00:02:43.379> and<00:02:43.560> you<00:02:44.040> know<00:02:44.099> there's<00:02:44.280> there's<00:02:44.519> a 00:02:44.690 --> 00:02:44.700 align:start position:0% and and you know there's there's a 00:02:44.700 --> 00:02:45.830 align:start position:0% and and you know there's there's a couple<00:02:44.879> hiccups<00:02:45.300> here<00:02:45.360> and<00:02:45.480> there<00:02:45.599> with<00:02:45.720> a 00:02:45.830 --> 00:02:45.840 align:start position:0% couple hiccups here and there with a 00:02:45.840 --> 00:02:47.990 align:start position:0% couple hiccups here and there with a couple<00:02:45.959> clients<00:02:46.379> and<00:02:46.560> and<00:02:46.800> people<00:02:47.280> are<00:02:47.580> uh 00:02:47.990 --> 00:02:48.000 align:start position:0% couple clients and and people are uh 00:02:48.000 --> 00:02:50.030 align:start position:0% couple clients and and people are uh resolving<00:02:48.660> them<00:02:48.840> moving<00:02:49.140> forward<00:02:49.379> and<00:02:49.739> we 00:02:50.030 --> 00:02:50.040 align:start position:0% resolving them moving forward and we 00:02:50.040 --> 00:02:51.770 align:start position:0% resolving them moving forward and we have<00:02:50.220> a<00:02:50.340> nice<00:02:50.519> little<00:02:50.700> nice<00:02:51.239> little<00:02:51.480> stable 00:02:51.770 --> 00:02:51.780 align:start position:0% have a nice little nice little stable 00:02:51.780 --> 00:02:52.729 align:start position:0% have a nice little nice little stable graph 00:02:52.729 --> 00:02:52.739 align:start position:0% graph 00:02:52.739 --> 00:02:54.949 align:start position:0% graph blocks<00:02:53.519> turns<00:02:54.239> out<00:02:54.300> those<00:02:54.480> are<00:02:54.660> good<00:02:54.780> too 00:02:54.949 --> 00:02:54.959 align:start position:0% blocks turns out those are good too 00:02:54.959 --> 00:02:56.750 align:start position:0% blocks turns out those are good too they're<00:02:55.739> coming<00:02:55.860> out<00:02:56.040> in<00:02:56.160> a<00:02:56.280> healthy<00:02:56.519> clip 00:02:56.750 --> 00:02:56.760 align:start position:0% they're coming out in a healthy clip 00:02:56.760 --> 00:02:58.910 align:start position:0% they're coming out in a healthy clip blue<00:02:57.360> there's<00:02:57.959> actually<00:02:58.140> three<00:02:58.440> colors<00:02:58.800> on 00:02:58.910 --> 00:02:58.920 align:start position:0% blue there's actually three colors on 00:02:58.920 --> 00:03:01.790 align:start position:0% blue there's actually three colors on this<00:02:59.099> graph<00:02:59.340> blue<00:03:00.120> is<00:03:00.540> uh<00:03:01.019> is<00:03:01.440> successful 00:03:01.790 --> 00:03:01.800 align:start position:0% this graph blue is uh is successful 00:03:01.800 --> 00:03:04.250 align:start position:0% this graph blue is uh is successful blocks<00:03:02.280> each<00:03:02.400> day<00:03:02.580> and<00:03:02.940> almost<00:03:03.599> all<00:03:03.959> of<00:03:04.080> them 00:03:04.250 --> 00:03:04.260 align:start position:0% blocks each day and almost all of them 00:03:04.260 --> 00:03:06.110 align:start position:0% blocks each day and almost all of them are 00:03:06.110 --> 00:03:06.120 align:start position:0% are 00:03:06.120 --> 00:03:08.390 align:start position:0% are let's<00:03:06.900> see 00:03:08.390 --> 00:03:08.400 align:start position:0% let's see 00:03:08.400 --> 00:03:12.170 align:start position:0% let's see but<00:03:09.200> we<00:03:10.200> do<00:03:10.440> we<00:03:10.860> do<00:03:10.980> miss<00:03:11.220> a<00:03:11.400> few<00:03:11.519> slots<00:03:11.819> from 00:03:12.170 --> 00:03:12.180 align:start position:0% but we do we do miss a few slots from 00:03:12.180 --> 00:03:13.550 align:start position:0% but we do we do miss a few slots from people<00:03:12.360> being<00:03:12.599> offline<00:03:13.019> I<00:03:13.319> was<00:03:13.440> actually 00:03:13.550 --> 00:03:13.560 align:start position:0% people being offline I was actually 00:03:13.560 --> 00:03:15.530 align:start position:0% people being offline I was actually talking<00:03:13.800> to<00:03:14.040> Terence<00:03:14.400> and<00:03:14.879> it<00:03:15.000> turns<00:03:15.239> out<00:03:15.300> that 00:03:15.530 --> 00:03:15.540 align:start position:0% talking to Terence and it turns out that 00:03:15.540 --> 00:03:18.050 align:start position:0% talking to Terence and it turns out that we<00:03:15.780> miss<00:03:16.080> fewer<00:03:16.800> slots<00:03:17.099> now 00:03:18.050 --> 00:03:18.060 align:start position:0% we miss fewer slots now 00:03:18.060 --> 00:03:19.790 align:start position:0% we miss fewer slots now than<00:03:18.599> before<00:03:18.780> the<00:03:19.080> merge<00:03:19.379> so<00:03:19.500> even<00:03:19.680> though 00:03:19.790 --> 00:03:19.800 align:start position:0% than before the merge so even though 00:03:19.800 --> 00:03:22.009 align:start position:0% than before the merge so even though there's<00:03:19.980> more<00:03:20.159> complexity<00:03:20.640> in<00:03:20.879> the<00:03:21.000> system 00:03:22.009 --> 00:03:22.019 align:start position:0% there's more complexity in the system 00:03:22.019 --> 00:03:24.470 align:start position:0% there's more complexity in the system um terence's<00:03:22.980> hypothesis<00:03:23.640> is<00:03:23.940> that<00:03:24.239> uh 00:03:24.470 --> 00:03:24.480 align:start position:0% um terence's hypothesis is that uh 00:03:24.480 --> 00:03:26.390 align:start position:0% um terence's hypothesis is that uh there's<00:03:25.140> a<00:03:25.379> bit<00:03:25.440> more<00:03:25.620> money<00:03:25.800> on<00:03:25.980> the<00:03:26.099> line<00:03:26.220> you 00:03:26.390 --> 00:03:26.400 align:start position:0% there's a bit more money on the line you 00:03:26.400 --> 00:03:27.710 align:start position:0% there's a bit more money on the line you really<00:03:26.580> want<00:03:26.760> those<00:03:26.940> blocks<00:03:27.239> now<00:03:27.360> with<00:03:27.540> those 00:03:27.710 --> 00:03:27.720 align:start position:0% really want those blocks now with those 00:03:27.720 --> 00:03:31.369 align:start position:0% really want those blocks now with those fees<00:03:28.019> uh<00:03:28.680> so<00:03:28.920> the<00:03:29.700> the<00:03:29.760> number<00:03:30.480> of<00:03:30.659> blocks<00:03:31.019> is 00:03:31.369 --> 00:03:31.379 align:start position:0% fees uh so the the number of blocks is 00:03:31.379 --> 00:03:33.170 align:start position:0% fees uh so the the number of blocks is even<00:03:31.500> better<00:03:31.680> than<00:03:31.860> it<00:03:31.980> was<00:03:32.099> before 00:03:33.170 --> 00:03:33.180 align:start position:0% even better than it was before 00:03:33.180 --> 00:03:34.850 align:start position:0% even better than it was before and<00:03:33.540> then<00:03:33.659> what<00:03:33.840> about<00:03:33.959> reorgs<00:03:34.680> there's 00:03:34.850 --> 00:03:34.860 align:start position:0% and then what about reorgs there's 00:03:34.860 --> 00:03:36.770 align:start position:0% and then what about reorgs there's another<00:03:35.040> color<00:03:35.400> on<00:03:35.640> this<00:03:35.819> graph<00:03:36.060> presumably 00:03:36.770 --> 00:03:36.780 align:start position:0% another color on this graph presumably 00:03:36.780 --> 00:03:39.229 align:start position:0% another color on this graph presumably it's<00:03:37.200> orange 00:03:39.229 --> 00:03:39.239 align:start position:0% it's orange 00:03:39.239 --> 00:03:41.690 align:start position:0% it's orange but<00:03:39.599> I<00:03:39.780> don't<00:03:39.900> you<00:03:40.379> know<00:03:40.440> there<00:03:41.340> weren't<00:03:41.459> many 00:03:41.690 --> 00:03:41.700 align:start position:0% but I don't you know there weren't many 00:03:41.700 --> 00:03:42.949 align:start position:0% but I don't you know there weren't many before<00:03:41.879> the<00:03:42.120> merge<00:03:42.420> and<00:03:42.540> there's<00:03:42.659> not<00:03:42.840> many 00:03:42.949 --> 00:03:42.959 align:start position:0% before the merge and there's not many 00:03:42.959 --> 00:03:46.610 align:start position:0% before the merge and there's not many after<00:03:43.260> uh<00:03:44.159> in<00:03:44.400> fact<00:03:44.519> Michael<00:03:45.360> Sproul<00:03:46.019> dumped 00:03:46.610 --> 00:03:46.620 align:start position:0% after uh in fact Michael Sproul dumped 00:03:46.620 --> 00:03:49.009 align:start position:0% after uh in fact Michael Sproul dumped from<00:03:46.680> his<00:03:46.860> note<00:03:47.040> he's<00:03:47.400> seen<00:03:47.700> 26<00:03:48.420> reorgs 00:03:49.009 --> 00:03:49.019 align:start position:0% from his note he's seen 26 reorgs 00:03:49.019 --> 00:03:50.210 align:start position:0% from his note he's seen 26 reorgs although<00:03:49.260> some<00:03:49.440> of<00:03:49.560> those<00:03:49.680> might<00:03:49.920> be<00:03:50.040> double 00:03:50.210 --> 00:03:50.220 align:start position:0% although some of those might be double 00:03:50.220 --> 00:03:53.449 align:start position:0% although some of those might be double counted<00:03:50.700> and<00:03:51.000> 85<00:03:51.420> orphaned<00:03:52.080> blocks<00:03:52.620> all<00:03:53.340> of 00:03:53.449 --> 00:03:53.459 align:start position:0% counted and 85 orphaned blocks all of 00:03:53.459 --> 00:03:54.890 align:start position:0% counted and 85 orphaned blocks all of these<00:03:53.640> generally<00:03:54.000> show<00:03:54.299> very<00:03:54.720> late 00:03:54.890 --> 00:03:54.900 align:start position:0% these generally show very late 00:03:54.900 --> 00:03:57.530 align:start position:0% these generally show very late properties<00:03:55.379> so<00:03:56.340> if<00:03:56.640> something's<00:03:57.000> reorged 00:03:57.530 --> 00:03:57.540 align:start position:0% properties so if something's reorged 00:03:57.540 --> 00:03:59.770 align:start position:0% properties so if something's reorged generally<00:03:57.959> we're<00:03:58.200> seeing<00:03:58.440> you<00:03:59.040> know<00:03:59.099> things 00:03:59.770 --> 00:03:59.780 align:start position:0% generally we're seeing you know things 00:03:59.780 --> 00:04:02.690 align:start position:0% generally we're seeing you know things Landing<00:04:00.780> towards<00:04:01.140> like<00:04:01.319> the<00:04:01.500> last<00:04:01.739> two-thirds 00:04:02.690 --> 00:04:02.700 align:start position:0% Landing towards like the last two-thirds 00:04:02.700 --> 00:04:04.190 align:start position:0% Landing towards like the last two-thirds of<00:04:02.819> a<00:04:02.940> slot<00:04:03.180> or<00:04:03.420> even<00:04:03.480> like<00:04:03.780> right<00:04:03.900> on<00:04:04.080> that 00:04:04.190 --> 00:04:04.200 align:start position:0% of a slot or even like right on that 00:04:04.200 --> 00:04:06.050 align:start position:0% of a slot or even like right on that boundary<00:04:04.680> so<00:04:05.040> the<00:04:05.400> network<00:04:05.519> gets<00:04:05.940> a<00:04:06.000> little 00:04:06.050 --> 00:04:06.060 align:start position:0% boundary so the network gets a little 00:04:06.060 --> 00:04:08.630 align:start position:0% boundary so the network gets a little bit<00:04:06.239> confused<00:04:06.720> and<00:04:07.140> then<00:04:07.260> resolves<00:04:07.739> it<00:04:07.920> and<00:04:08.159> I 00:04:08.630 --> 00:04:08.640 align:start position:0% bit confused and then resolves it and I 00:04:08.640 --> 00:04:10.369 align:start position:0% bit confused and then resolves it and I should<00:04:08.700> say<00:04:08.879> all<00:04:09.060> these<00:04:09.239> reorges<00:04:09.720> are<00:04:09.959> depth 00:04:10.369 --> 00:04:10.379 align:start position:0% should say all these reorges are depth 00:04:10.379 --> 00:04:11.210 align:start position:0% should say all these reorges are depth one 00:04:11.210 --> 00:04:11.220 align:start position:0% one 00:04:11.220 --> 00:04:11.929 align:start position:0% one um 00:04:11.929 --> 00:04:11.939 align:start position:0% um 00:04:11.939 --> 00:04:14.270 align:start position:0% um also<00:04:12.659> from<00:04:12.780> Terence<00:04:13.140> check<00:04:13.439> out<00:04:13.620> his<00:04:13.860> talk<00:04:14.040> in 00:04:14.270 --> 00:04:14.280 align:start position:0% also from Terence check out his talk in 00:04:14.280 --> 00:04:15.289 align:start position:0% also from Terence check out his talk in two<00:04:14.400> days 00:04:15.289 --> 00:04:15.299 align:start position:0% two days 00:04:15.299 --> 00:04:17.270 align:start position:0% two days um<00:04:15.360> 50<00:04:15.599> of<00:04:16.139> the<00:04:16.260> orphans<00:04:16.680> so<00:04:16.919> these<00:04:17.100> are<00:04:17.220> the 00:04:17.270 --> 00:04:17.280 align:start position:0% um 50 of the orphans so these are the 00:04:17.280 --> 00:04:18.949 align:start position:0% um 50 of the orphans so these are the blocks<00:04:17.639> that<00:04:17.940> tried<00:04:18.299> to<00:04:18.419> make<00:04:18.540> it<00:04:18.660> on<00:04:18.780> chain 00:04:18.949 --> 00:04:18.959 align:start position:0% blocks that tried to make it on chain 00:04:18.959 --> 00:04:21.050 align:start position:0% blocks that tried to make it on chain and<00:04:19.199> didn't<00:04:19.440> uh<00:04:19.859> come<00:04:20.040> from<00:04:20.160> Mad<00:04:20.400> boost<00:04:20.579> relays 00:04:21.050 --> 00:04:21.060 align:start position:0% and didn't uh come from Mad boost relays 00:04:21.060 --> 00:04:22.129 align:start position:0% and didn't uh come from Mad boost relays there's<00:04:21.180> additional<00:04:21.600> latency<00:04:21.900> and 00:04:22.129 --> 00:04:22.139 align:start position:0% there's additional latency and 00:04:22.139 --> 00:04:23.810 align:start position:0% there's additional latency and complexity<00:04:22.500> that<00:04:22.740> happens<00:04:22.919> there<00:04:23.220> people<00:04:23.639> are 00:04:23.810 --> 00:04:23.820 align:start position:0% complexity that happens there people are 00:04:23.820 --> 00:04:25.730 align:start position:0% complexity that happens there people are working<00:04:24.000> through<00:04:24.240> it<00:04:24.419> but<00:04:24.900> you<00:04:25.259> know<00:04:25.380> that's 00:04:25.730 --> 00:04:25.740 align:start position:0% working through it but you know that's 00:04:25.740 --> 00:04:29.030 align:start position:0% working through it but you know that's that's<00:04:25.979> uh<00:04:26.520> an<00:04:26.940> interesting<00:04:27.360> component<00:04:28.259> here 00:04:29.030 --> 00:04:29.040 align:start position:0% that's uh an interesting component here 00:04:29.040 --> 00:04:30.710 align:start position:0% that's uh an interesting component here also<00:04:29.460> it<00:04:29.580> depends<00:04:29.820> on<00:04:29.940> your<00:04:30.060> perspective<00:04:30.360> you 00:04:30.710 --> 00:04:30.720 align:start position:0% also it depends on your perspective you 00:04:30.720 --> 00:04:32.450 align:start position:0% also it depends on your perspective you know<00:04:30.780> some<00:04:31.020> nodes<00:04:31.320> might<00:04:31.800> see<00:04:32.040> like<00:04:32.220> a<00:04:32.340> little 00:04:32.450 --> 00:04:32.460 align:start position:0% know some nodes might see like a little 00:04:32.460 --> 00:04:34.070 align:start position:0% know some nodes might see like a little reorg<00:04:32.880> and<00:04:33.000> the<00:04:33.120> other<00:04:33.180> node<00:04:33.360> always<00:04:33.600> saw<00:04:33.840> it 00:04:34.070 --> 00:04:34.080 align:start position:0% reorg and the other node always saw it 00:04:34.080 --> 00:04:36.710 align:start position:0% reorg and the other node always saw it as<00:04:34.199> solve<00:04:34.620> the<00:04:34.680> correct<00:04:35.160> head<00:04:35.280> so<00:04:35.699> again<00:04:36.240> these 00:04:36.710 --> 00:04:36.720 align:start position:0% as solve the correct head so again these 00:04:36.720 --> 00:04:38.689 align:start position:0% as solve the correct head so again these numbers<00:04:36.840> I<00:04:37.080> mean<00:04:37.139> that's<00:04:37.259> like<00:04:37.380> one<00:04:37.560> a<00:04:37.800> day<00:04:37.919> so 00:04:38.689 --> 00:04:38.699 align:start position:0% numbers I mean that's like one a day so 00:04:38.699 --> 00:04:40.969 align:start position:0% numbers I mean that's like one a day so things<00:04:39.300> are<00:04:39.600> pretty<00:04:39.960> pretty<00:04:40.259> smooth<00:04:40.560> I<00:04:40.800> think 00:04:40.969 --> 00:04:40.979 align:start position:0% things are pretty pretty smooth I think 00:04:40.979 --> 00:04:43.310 align:start position:0% things are pretty pretty smooth I think the<00:04:41.280> the<00:04:41.580> like<00:04:41.880> Uncle<00:04:42.060> rate<00:04:42.479> in<00:04:42.780> proof<00:04:43.080> of<00:04:43.139> work 00:04:43.310 --> 00:04:43.320 align:start position:0% the the like Uncle rate in proof of work 00:04:43.320 --> 00:04:45.050 align:start position:0% the the like Uncle rate in proof of work obviously<00:04:44.220> because<00:04:44.400> there's<00:04:44.639> a<00:04:44.820> lot<00:04:44.940> of 00:04:45.050 --> 00:04:45.060 align:start position:0% obviously because there's a lot of 00:04:45.060 --> 00:04:46.850 align:start position:0% obviously because there's a lot of redundant<00:04:45.720> work<00:04:45.960> happening<00:04:46.320> because<00:04:46.500> of<00:04:46.740> the 00:04:46.850 --> 00:04:46.860 align:start position:0% redundant work happening because of the 00:04:46.860 --> 00:04:49.249 align:start position:0% redundant work happening because of the way<00:04:47.000> competitions<00:04:48.000> uh<00:04:48.660> improve<00:04:49.080> of<00:04:49.139> work 00:04:49.249 --> 00:04:49.259 align:start position:0% way competitions uh improve of work 00:04:49.259 --> 00:04:50.930 align:start position:0% way competitions uh improve of work happen<00:04:49.440> there's<00:04:50.040> like<00:04:50.220> a<00:04:50.340> four<00:04:50.460> percent<00:04:50.699> or 00:04:50.930 --> 00:04:50.940 align:start position:0% happen there's like a four percent or 00:04:50.940 --> 00:04:52.249 align:start position:0% happen there's like a four percent or eight<00:04:51.060> percent 00:04:52.249 --> 00:04:52.259 align:start position:0% eight percent 00:04:52.259 --> 00:04:54.830 align:start position:0% eight percent um uncle<00:04:53.100> rate<00:04:53.400> and<00:04:53.940> you<00:04:54.180> know<00:04:54.240> we're<00:04:54.419> at<00:04:54.600> near 00:04:54.830 --> 00:04:54.840 align:start position:0% um uncle rate and you know we're at near 00:04:54.840 --> 00:04:57.110 align:start position:0% um uncle rate and you know we're at near zero<00:04:55.440> now<00:04:55.560> so<00:04:55.860> things<00:04:56.280> are<00:04:56.520> things<00:04:56.940> are 00:04:57.110 --> 00:04:57.120 align:start position:0% zero now so things are things are 00:04:57.120 --> 00:04:58.790 align:start position:0% zero now so things are things are generally<00:04:57.300> working<00:04:57.600> this<00:04:58.199> is<00:04:58.320> what<00:04:58.500> it<00:04:58.560> looks 00:04:58.790 --> 00:04:58.800 align:start position:0% generally working this is what it looks 00:04:58.800 --> 00:04:59.629 align:start position:0% generally working this is what it looks like 00:04:59.629 --> 00:04:59.639 align:start position:0% like 00:04:59.639 --> 00:05:02.290 align:start position:0% like it's<00:05:00.240> plain<00:05:00.479> and<00:05:00.660> simply<00:05:00.960> healthy<00:05:01.320> again 00:05:02.290 --> 00:05:02.300 align:start position:0% it's plain and simply healthy again 00:05:02.300 --> 00:05:06.590 align:start position:0% it's plain and simply healthy again finality<00:05:03.300> step<00:05:03.900> wise<00:05:04.460> very<00:05:05.460> nice<00:05:05.639> almost<00:05:06.180> the 00:05:06.590 --> 00:05:06.600 align:start position:0% finality step wise very nice almost the 00:05:06.600 --> 00:05:08.450 align:start position:0% finality step wise very nice almost the entirety<00:05:07.139> of<00:05:07.440> the<00:05:07.680> beacon<00:05:08.040> chain<00:05:08.160> since 00:05:08.450 --> 00:05:08.460 align:start position:0% entirety of the beacon chain since 00:05:08.460 --> 00:05:10.490 align:start position:0% entirety of the beacon chain since Genesis<00:05:09.000> has<00:05:09.300> looked<00:05:09.660> exactly<00:05:10.020> like<00:05:10.259> that 00:05:10.490 --> 00:05:10.500 align:start position:0% Genesis has looked exactly like that 00:05:10.500 --> 00:05:14.390 align:start position:0% Genesis has looked exactly like that it's<00:05:11.400> set<00:05:11.639> for<00:05:11.880> this<00:05:12.060> one<00:05:12.360> time 00:05:14.390 --> 00:05:14.400 align:start position:0% it's set for this one time 00:05:14.400 --> 00:05:16.310 align:start position:0% it's set for this one time I<00:05:14.759> was<00:05:14.820> out<00:05:14.940> to<00:05:15.180> dinner<00:05:15.300> on<00:05:15.600> a<00:05:15.720> Friday<00:05:15.840> and<00:05:16.139> I 00:05:16.310 --> 00:05:16.320 align:start position:0% I was out to dinner on a Friday and I 00:05:16.320 --> 00:05:17.990 align:start position:0% I was out to dinner on a Friday and I got<00:05:16.440> a<00:05:16.560> text<00:05:16.740> and<00:05:17.100> it's<00:05:17.280> not<00:05:17.400> a<00:05:17.520> text<00:05:17.639> you<00:05:17.820> want 00:05:17.990 --> 00:05:18.000 align:start position:0% got a text and it's not a text you want 00:05:18.000 --> 00:05:19.969 align:start position:0% got a text and it's not a text you want to<00:05:18.120> get<00:05:18.240> on<00:05:18.720> a<00:05:18.840> Friday<00:05:18.960> night<00:05:19.259> there's 00:05:19.969 --> 00:05:19.979 align:start position:0% to get on a Friday night there's 00:05:19.979 --> 00:05:23.450 align:start position:0% to get on a Friday night there's something<00:05:20.220> up<00:05:20.639> with<00:05:21.060> mainnet<00:05:21.660> from<00:05:22.139> Paul<00:05:22.460> uh 00:05:23.450 --> 00:05:23.460 align:start position:0% something up with mainnet from Paul uh 00:05:23.460 --> 00:05:26.210 align:start position:0% something up with mainnet from Paul uh there<00:05:23.880> was<00:05:24.000> a<00:05:24.120> little<00:05:24.180> there<00:05:24.479> was<00:05:24.660> yeah<00:05:25.259> the 00:05:26.210 --> 00:05:26.220 align:start position:0% there was a little there was yeah the 00:05:26.220 --> 00:05:28.310 align:start position:0% there was a little there was yeah the network<00:05:26.340> stayed<00:05:26.820> live<00:05:26.940> we<00:05:27.720> lost<00:05:27.960> some<00:05:28.199> block 00:05:28.310 --> 00:05:28.320 align:start position:0% network stayed live we lost some block 00:05:28.320 --> 00:05:30.710 align:start position:0% network stayed live we lost some block proposals<00:05:29.039> and<00:05:29.699> we<00:05:29.940> didn't<00:05:30.120> finalize 00:05:30.710 --> 00:05:30.720 align:start position:0% proposals and we didn't finalize 00:05:30.720 --> 00:05:32.749 align:start position:0% proposals and we didn't finalize perfectly<00:05:31.380> into<00:05:31.680> epochs<00:05:32.340> it<00:05:32.400> looks<00:05:32.580> like<00:05:32.639> we 00:05:32.749 --> 00:05:32.759 align:start position:0% perfectly into epochs it looks like we 00:05:32.759 --> 00:05:35.090 align:start position:0% perfectly into epochs it looks like we finalized<00:05:33.240> a<00:05:33.360> few<00:05:33.479> in<00:05:33.600> three<00:05:33.720> epochs<00:05:34.320> and<00:05:34.919> it's 00:05:35.090 --> 00:05:35.100 align:start position:0% finalized a few in three epochs and it's 00:05:35.100 --> 00:05:37.550 align:start position:0% finalized a few in three epochs and it's been<00:05:35.280> resolved<00:05:35.699> in<00:05:35.940> very<00:05:36.120> clean<00:05:36.300> since 00:05:37.550 --> 00:05:37.560 align:start position:0% been resolved in very clean since 00:05:37.560 --> 00:05:40.310 align:start position:0% been resolved in very clean since um I<00:05:38.460> know<00:05:38.639> Victory<00:05:39.419> lap<00:05:39.660> on<00:05:39.840> the<00:05:39.960> merge<00:05:40.199> but 00:05:40.310 --> 00:05:40.320 align:start position:0% um I know Victory lap on the merge but 00:05:40.320 --> 00:05:41.570 align:start position:0% um I know Victory lap on the merge but like<00:05:40.440> Victory<00:05:40.680> lap<00:05:40.919> on<00:05:41.100> the<00:05:41.160> beacon<00:05:41.400> chain 00:05:41.570 --> 00:05:41.580 align:start position:0% like Victory lap on the beacon chain 00:05:41.580 --> 00:05:43.969 align:start position:0% like Victory lap on the beacon chain it's<00:05:41.759> been<00:05:41.940> an<00:05:42.120> incredible<00:05:42.419> two<00:05:42.600> years 00:05:43.969 --> 00:05:43.979 align:start position:0% it's been an incredible two years 00:05:43.979 --> 00:05:46.730 align:start position:0% it's been an incredible two years uh<00:05:44.699> and<00:05:44.940> ultrasound<00:05:45.539> OnStar<00:05:46.139> ultrasound 00:05:46.730 --> 00:05:46.740 align:start position:0% uh and ultrasound OnStar ultrasound 00:05:46.740 --> 00:05:49.550 align:start position:0% uh and ultrasound OnStar ultrasound money<00:05:47.039> ultrasound<00:05:47.580> uh<00:05:48.360> Justin<00:05:48.600> Drake<00:05:48.960> I'm 00:05:49.550 --> 00:05:49.560 align:start position:0% money ultrasound uh Justin Drake I'm 00:05:49.560 --> 00:05:51.890 align:start position:0% money ultrasound uh Justin Drake I'm scar<00:05:49.740> it's<00:05:50.220> a<00:05:50.400> nod<00:05:50.699> to<00:05:50.880> onskar<00:05:51.300> convincing<00:05:51.780> us 00:05:51.890 --> 00:05:51.900 align:start position:0% scar it's a nod to onskar convincing us 00:05:51.900 --> 00:05:53.930 align:start position:0% scar it's a nod to onskar convincing us to<00:05:52.080> merge<00:05:52.380> like<00:05:52.560> five<00:05:52.800> or<00:05:52.979> seven<00:05:53.160> days<00:05:53.400> earlier 00:05:53.930 --> 00:05:53.940 align:start position:0% to merge like five or seven days earlier 00:05:53.940 --> 00:05:56.810 align:start position:0% to merge like five or seven days earlier uh<00:05:54.660> to<00:05:54.900> to<00:05:55.020> save<00:05:55.320> on<00:05:55.560> issuance 00:05:56.810 --> 00:05:56.820 align:start position:0% uh to to save on issuance 00:05:56.820 --> 00:05:58.249 align:start position:0% uh to to save on issuance um<00:05:56.880> but<00:05:57.300> Justin's<00:05:57.720> given<00:05:57.960> a<00:05:58.020> great<00:05:58.080> talk 00:05:58.249 --> 00:05:58.259 align:start position:0% um but Justin's given a great talk 00:05:58.259 --> 00:06:00.529 align:start position:0% um but Justin's given a great talk tomorrow<00:05:58.440> check<00:05:58.800> it<00:05:58.979> out 00:06:00.529 --> 00:06:00.539 align:start position:0% tomorrow check it out 00:06:00.539 --> 00:06:01.969 align:start position:0% tomorrow check it out and 00:06:01.969 --> 00:06:01.979 align:start position:0% and 00:06:01.979 --> 00:06:03.950 align:start position:0% and before<00:06:02.280> I<00:06:02.460> move<00:06:02.639> on<00:06:02.820> uh<00:06:03.419> there<00:06:03.539> is<00:06:03.660> a<00:06:03.720> merge 00:06:03.950 --> 00:06:03.960 align:start position:0% before I move on uh there is a merge 00:06:03.960 --> 00:06:06.230 align:start position:0% before I move on uh there is a merge data<00:06:04.199> challenge<00:06:04.320> going<00:06:04.620> on<00:06:04.800> all<00:06:05.759> of<00:06:05.880> those<00:06:06.000> are 00:06:06.230 --> 00:06:06.240 align:start position:0% data challenge going on all of those are 00:06:06.240 --> 00:06:07.670 align:start position:0% data challenge going on all of those are like<00:06:06.360> very<00:06:06.600> simple<00:06:06.780> metrics<00:06:07.259> there<00:06:07.440> might<00:06:07.620> be 00:06:07.670 --> 00:06:07.680 align:start position:0% like very simple metrics there might be 00:06:07.680 --> 00:06:08.870 align:start position:0% like very simple metrics there might be some<00:06:07.860> more<00:06:08.039> interesting<00:06:08.340> stuff<00:06:08.580> going<00:06:08.759> on 00:06:08.870 --> 00:06:08.880 align:start position:0% some more interesting stuff going on 00:06:08.880 --> 00:06:11.390 align:start position:0% some more interesting stuff going on underneath<00:06:09.240> the<00:06:09.419> hood<00:06:09.539> check<00:06:10.139> it<00:06:10.320> out<00:06:10.500> and 00:06:11.390 --> 00:06:11.400 align:start position:0% underneath the hood check it out and 00:06:11.400 --> 00:06:13.070 align:start position:0% underneath the hood check it out and submissions<00:06:11.940> are<00:06:12.180> due<00:06:12.419> by<00:06:12.720> the<00:06:12.840> end<00:06:12.960> of<00:06:13.020> the 00:06:13.070 --> 00:06:13.080 align:start position:0% submissions are due by the end of the 00:06:13.080 --> 00:06:14.150 align:start position:0% submissions are due by the end of the month<00:06:13.199> so<00:06:13.380> you<00:06:13.500> still<00:06:13.620> got<00:06:13.740> plenty<00:06:13.979> of<00:06:14.039> time 00:06:14.150 --> 00:06:14.160 align:start position:0% month so you still got plenty of time 00:06:14.160 --> 00:06:16.730 align:start position:0% month so you still got plenty of time certainly<00:06:14.940> from<00:06:15.180> the<00:06:15.360> inside<00:06:15.479> uh<00:06:16.320> we<00:06:16.440> feel<00:06:16.560> the 00:06:16.730 --> 00:06:16.740 align:start position:0% certainly from the inside uh we feel the 00:06:16.740 --> 00:06:18.650 align:start position:0% certainly from the inside uh we feel the pain<00:06:16.860> but<00:06:17.100> I<00:06:17.220> know<00:06:17.280> the<00:06:17.400> pain<00:06:17.940> is<00:06:18.180> felt<00:06:18.479> from 00:06:18.650 --> 00:06:18.660 align:start position:0% pain but I know the pain is felt from 00:06:18.660 --> 00:06:20.450 align:start position:0% pain but I know the pain is felt from the<00:06:18.780> outside<00:06:18.900> as<00:06:19.320> well<00:06:19.500> the<00:06:19.919> interest<00:06:20.160> in<00:06:20.400> fact 00:06:20.450 --> 00:06:20.460 align:start position:0% the outside as well the interest in fact 00:06:20.460 --> 00:06:22.129 align:start position:0% the outside as well the interest in fact was<00:06:20.699> one<00:06:20.940> of<00:06:21.000> the<00:06:21.120> suggestions<00:06:21.539> for<00:06:21.840> my<00:06:22.020> talk 00:06:22.129 --> 00:06:22.139 align:start position:0% was one of the suggestions for my talk 00:06:22.139 --> 00:06:24.710 align:start position:0% was one of the suggestions for my talk how<00:06:22.500> we<00:06:22.740> quote<00:06:23.220> ship<00:06:23.460> faster<00:06:23.759> I<00:06:24.419> don't<00:06:24.539> think 00:06:24.710 --> 00:06:24.720 align:start position:0% how we quote ship faster I don't think 00:06:24.720 --> 00:06:26.210 align:start position:0% how we quote ship faster I don't think I'm<00:06:24.900> going<00:06:25.020> to<00:06:25.139> talk<00:06:25.259> about<00:06:25.440> how<00:06:25.800> we<00:06:25.919> ship 00:06:26.210 --> 00:06:26.220 align:start position:0% I'm going to talk about how we ship 00:06:26.220 --> 00:06:27.890 align:start position:0% I'm going to talk about how we ship faster<00:06:26.520> but<00:06:27.060> I<00:06:27.180> want<00:06:27.300> to<00:06:27.360> talk<00:06:27.419> about<00:06:27.539> why<00:06:27.720> it's 00:06:27.890 --> 00:06:27.900 align:start position:0% faster but I want to talk about why it's 00:06:27.900 --> 00:06:30.170 align:start position:0% faster but I want to talk about why it's slow<00:06:28.080> and<00:06:28.680> it<00:06:28.800> feels<00:06:28.979> like<00:06:29.160> this 00:06:30.170 --> 00:06:30.180 align:start position:0% slow and it feels like this 00:06:30.180 --> 00:06:32.350 align:start position:0% slow and it feels like this both<00:06:30.660> from<00:06:30.840> the<00:06:31.020> internal<00:06:31.440> and<00:06:31.800> the<00:06:31.919> external 00:06:32.350 --> 00:06:32.360 align:start position:0% both from the internal and the external 00:06:32.360 --> 00:06:36.290 align:start position:0% both from the internal and the external hopefully<00:06:33.360> this<00:06:33.660> is<00:06:33.840> not<00:06:34.080> a<00:06:34.199> very<00:06:34.319> busy<00:06:34.620> road 00:06:36.290 --> 00:06:36.300 align:start position:0% hopefully this is not a very busy road 00:06:36.300 --> 00:06:38.270 align:start position:0% hopefully this is not a very busy road so<00:06:36.780> much<00:06:37.080> of<00:06:37.199> much<00:06:37.440> of<00:06:37.560> this<00:06:37.740> is<00:06:37.860> fundamental 00:06:38.270 --> 00:06:38.280 align:start position:0% so much of much of this is fundamental 00:06:38.280 --> 00:06:40.070 align:start position:0% so much of much of this is fundamental much<00:06:38.520> of<00:06:38.699> like<00:06:38.880> the<00:06:39.120> complexity<00:06:39.539> of<00:06:39.780> shipping 00:06:40.070 --> 00:06:40.080 align:start position:0% much of like the complexity of shipping 00:06:40.080 --> 00:06:41.749 align:start position:0% much of like the complexity of shipping here<00:06:40.199> is<00:06:40.440> fundamental<00:06:40.860> it<00:06:41.220> is<00:06:41.340> fundamentally 00:06:41.749 --> 00:06:41.759 align:start position:0% here is fundamental it is fundamentally 00:06:41.759 --> 00:06:43.430 align:start position:0% here is fundamental it is fundamentally new<00:06:42.000> research<00:06:42.360> fundamentally<00:06:43.199> new 00:06:43.430 --> 00:06:43.440 align:start position:0% new research fundamentally new 00:06:43.440 --> 00:06:45.469 align:start position:0% new research fundamentally new mechanisms<00:06:43.919> fundamentally<00:06:44.520> new<00:06:45.000> networking 00:06:45.469 --> 00:06:45.479 align:start position:0% mechanisms fundamentally new networking 00:06:45.479 --> 00:06:48.409 align:start position:0% mechanisms fundamentally new networking and<00:06:45.840> new<00:06:46.020> crop<00:06:46.400> cryptography<00:06:47.400> ethereum<00:06:48.180> has 00:06:48.409 --> 00:06:48.419 align:start position:0% and new crop cryptography ethereum has 00:06:48.419 --> 00:06:50.629 align:start position:0% and new crop cryptography ethereum has the<00:06:48.600> luxury<00:06:48.900> of<00:06:49.259> uh<00:06:49.800> having<00:06:50.220> tons<00:06:50.520> of 00:06:50.629 --> 00:06:50.639 align:start position:0% the luxury of uh having tons of 00:06:50.639 --> 00:06:52.450 align:start position:0% the luxury of uh having tons of backwards<00:06:51.000> compatibility 00:06:52.450 --> 00:06:52.460 align:start position:0% backwards compatibility 00:06:52.460 --> 00:06:54.650 align:start position:0% backwards compatibility considerations<00:06:53.460> at<00:06:53.880> every<00:06:54.000> moment<00:06:54.300> of<00:06:54.479> every 00:06:54.650 --> 00:06:54.660 align:start position:0% considerations at every moment of every 00:06:54.660 --> 00:06:57.529 align:start position:0% considerations at every moment of every day<00:06:54.840> and<00:06:55.680> quite<00:06:56.340> frankly<00:06:56.759> distributed 00:06:57.529 --> 00:06:57.539 align:start position:0% day and quite frankly distributed 00:06:57.539 --> 00:07:00.950 align:start position:0% day and quite frankly distributed systems<00:06:58.020> are<00:06:58.740> complicated<00:06:59.539> it's<00:07:00.539> much<00:07:00.720> easier 00:07:00.950 --> 00:07:00.960 align:start position:0% systems are complicated it's much easier 00:07:00.960 --> 00:07:02.210 align:start position:0% systems are complicated it's much easier to<00:07:01.080> get<00:07:01.199> a<00:07:01.319> computer<00:07:01.440> to<00:07:01.680> do<00:07:01.860> something<00:07:01.979> than 00:07:02.210 --> 00:07:02.220 align:start position:0% to get a computer to do something than 00:07:02.220 --> 00:07:03.529 align:start position:0% to get a computer to do something than to<00:07:02.400> get<00:07:02.520> a<00:07:02.639> bunch<00:07:02.699> of<00:07:02.819> computers<00:07:03.120> that<00:07:03.419> you 00:07:03.529 --> 00:07:03.539 align:start position:0% to get a bunch of computers that you 00:07:03.539 --> 00:07:05.629 align:start position:0% to get a bunch of computers that you don't<00:07:03.600> control<00:07:03.900> to<00:07:04.680> do<00:07:04.800> something<00:07:05.039> together 00:07:05.629 --> 00:07:05.639 align:start position:0% don't control to do something together 00:07:05.639 --> 00:07:07.189 align:start position:0% don't control to do something together and<00:07:06.360> agree 00:07:07.189 --> 00:07:07.199 align:start position:0% and agree 00:07:07.199 --> 00:07:09.710 align:start position:0% and agree always 00:07:09.710 --> 00:07:09.720 align:start position:0% always 00:07:09.720 --> 00:07:12.350 align:start position:0% always and<00:07:10.560> quite<00:07:11.160> frankly<00:07:11.460> much<00:07:11.639> has<00:07:11.819> improved<00:07:12.180> a 00:07:12.350 --> 00:07:12.360 align:start position:0% and quite frankly much has improved a 00:07:12.360 --> 00:07:13.610 align:start position:0% and quite frankly much has improved a lot<00:07:12.479> of<00:07:12.600> the<00:07:12.660> conversation<00:07:13.080> in<00:07:13.319> the<00:07:13.500> past 00:07:13.610 --> 00:07:13.620 align:start position:0% lot of the conversation in the past 00:07:13.620 --> 00:07:15.830 align:start position:0% lot of the conversation in the past couple<00:07:13.800> days<00:07:14.100> with<00:07:14.639> a<00:07:14.880> lot<00:07:14.940> of<00:07:15.060> the<00:07:15.120> L1<00:07:15.419> devs 00:07:15.830 --> 00:07:15.840 align:start position:0% couple days with a lot of the L1 devs 00:07:15.840 --> 00:07:17.390 align:start position:0% couple days with a lot of the L1 devs and<00:07:15.960> a<00:07:16.020> lot<00:07:16.080> of<00:07:16.139> people<00:07:16.259> involved<00:07:16.800> in<00:07:16.979> shipping 00:07:17.390 --> 00:07:17.400 align:start position:0% and a lot of people involved in shipping 00:07:17.400 --> 00:07:19.610 align:start position:0% and a lot of people involved in shipping and<00:07:17.819> improving<00:07:18.180> ethereum 00:07:19.610 --> 00:07:19.620 align:start position:0% and improving ethereum 00:07:19.620 --> 00:07:22.309 align:start position:0% and improving ethereum um<00:07:19.680> has<00:07:20.520> been<00:07:20.699> like<00:07:20.880> wow<00:07:21.300> this<00:07:21.780> this<00:07:22.020> thing's 00:07:22.309 --> 00:07:22.319 align:start position:0% um has been like wow this this thing's 00:07:22.319 --> 00:07:24.469 align:start position:0% um has been like wow this this thing's working<00:07:22.500> well<00:07:22.800> like<00:07:23.099> this<00:07:23.400> is<00:07:23.520> a<00:07:23.880> moderately 00:07:24.469 --> 00:07:24.479 align:start position:0% working well like this is a moderately 00:07:24.479 --> 00:07:26.570 align:start position:0% working well like this is a moderately well-oiled<00:07:25.139> machine<00:07:25.380> like<00:07:25.800> we're<00:07:25.979> moving 00:07:26.570 --> 00:07:26.580 align:start position:0% well-oiled machine like we're moving 00:07:26.580 --> 00:07:28.309 align:start position:0% well-oiled machine like we're moving faster<00:07:26.940> we're<00:07:27.300> getting<00:07:27.479> more<00:07:27.660> done<00:07:27.900> than<00:07:28.139> we 00:07:28.309 --> 00:07:28.319 align:start position:0% faster we're getting more done than we 00:07:28.319 --> 00:07:30.589 align:start position:0% faster we're getting more done than we used<00:07:28.500> to<00:07:28.620> and<00:07:29.099> some<00:07:29.220> of<00:07:29.340> that's<00:07:29.520> because 00:07:30.589 --> 00:07:30.599 align:start position:0% used to and some of that's because 00:07:30.599 --> 00:07:32.930 align:start position:0% used to and some of that's because more<00:07:31.259> core<00:07:31.740> questions<00:07:31.979> of<00:07:32.280> the<00:07:32.400> research<00:07:32.639> have 00:07:32.930 --> 00:07:32.940 align:start position:0% more core questions of the research have 00:07:32.940 --> 00:07:34.670 align:start position:0% more core questions of the research have been<00:07:33.060> answered<00:07:33.419> so<00:07:33.840> it<00:07:34.020> is<00:07:34.199> a<00:07:34.440> lot<00:07:34.560> of 00:07:34.670 --> 00:07:34.680 align:start position:0% been answered so it is a lot of 00:07:34.680 --> 00:07:36.230 align:start position:0% been answered so it is a lot of engineering<00:07:35.099> a<00:07:35.520> lot<00:07:35.639> of<00:07:35.699> that<00:07:35.819> is<00:07:36.000> is 00:07:36.230 --> 00:07:36.240 align:start position:0% engineering a lot of that is is 00:07:36.240 --> 00:07:39.010 align:start position:0% engineering a lot of that is is alignment<00:07:36.780> and<00:07:37.139> Ethos<00:07:37.560> a<00:07:37.919> lot<00:07:37.979> of<00:07:38.099> that<00:07:38.220> is 00:07:39.010 --> 00:07:39.020 align:start position:0% alignment and Ethos a lot of that is 00:07:39.020 --> 00:07:41.029 align:start position:0% alignment and Ethos a lot of that is sophistication<00:07:40.020> and<00:07:40.259> specialization<00:07:40.800> of 00:07:41.029 --> 00:07:41.039 align:start position:0% sophistication and specialization of 00:07:41.039 --> 00:07:42.950 align:start position:0% sophistication and specialization of client<00:07:41.280> devs<00:07:41.699> we<00:07:42.000> have<00:07:42.120> a<00:07:42.180> lot<00:07:42.300> more<00:07:42.419> people<00:07:42.660> on 00:07:42.950 --> 00:07:42.960 align:start position:0% client devs we have a lot more people on 00:07:42.960 --> 00:07:45.710 align:start position:0% client devs we have a lot more people on testing<00:07:43.319> we<00:07:43.800> have<00:07:43.919> devops<00:07:44.520> wizards<00:07:45.360> driving 00:07:45.710 --> 00:07:45.720 align:start position:0% testing we have devops wizards driving 00:07:45.720 --> 00:07:47.330 align:start position:0% testing we have devops wizards driving our<00:07:46.020> test<00:07:46.199> Nets<00:07:46.620> and<00:07:46.680> helping<00:07:46.919> us<00:07:47.039> at<00:07:47.160> every 00:07:47.330 --> 00:07:47.340 align:start position:0% our test Nets and helping us at every 00:07:47.340 --> 00:07:49.010 align:start position:0% our test Nets and helping us at every step<00:07:47.580> of<00:07:47.699> the<00:07:47.819> day<00:07:48.000> dedicated<00:07:48.780> security 00:07:49.010 --> 00:07:49.020 align:start position:0% step of the day dedicated security 00:07:49.020 --> 00:07:51.350 align:start position:0% step of the day dedicated security analysts<00:07:50.160> all<00:07:50.699> sorts<00:07:50.940> of<00:07:51.000> academic 00:07:51.350 --> 00:07:51.360 align:start position:0% analysts all sorts of academic 00:07:51.360 --> 00:07:54.110 align:start position:0% analysts all sorts of academic collaborations<00:07:51.860> really<00:07:52.860> fun<00:07:53.160> development 00:07:54.110 --> 00:07:54.120 align:start position:0% collaborations really fun development 00:07:54.120 --> 00:07:55.309 align:start position:0% collaborations really fun development Retreats 00:07:55.309 --> 00:07:55.319 align:start position:0% Retreats 00:07:55.319 --> 00:07:58.010 align:start position:0% Retreats um<00:07:55.380> and<00:07:55.919> the<00:07:56.400> process<00:07:56.699> is<00:07:56.940> just<00:07:57.240> it's<00:07:57.539> refined 00:07:58.010 --> 00:07:58.020 align:start position:0% um and the process is just it's refined 00:07:58.020 --> 00:08:00.409 align:start position:0% um and the process is just it's refined it's<00:07:58.139> really<00:07:58.319> moving<00:07:58.620> well<00:07:58.860> so 00:08:00.409 --> 00:08:00.419 align:start position:0% it's really moving well so 00:08:00.419 --> 00:08:02.629 align:start position:0% it's really moving well so things<00:08:00.900> are<00:08:01.080> slow<00:08:01.319> things<00:08:02.039> aren't<00:08:02.280> going<00:08:02.460> to 00:08:02.629 --> 00:08:02.639 align:start position:0% things are slow things aren't going to 00:08:02.639 --> 00:08:03.710 align:start position:0% things are slow things aren't going to be<00:08:02.699> fast 00:08:03.710 --> 00:08:03.720 align:start position:0% be fast 00:08:03.720 --> 00:08:06.230 align:start position:0% be fast but<00:08:04.080> they're<00:08:04.199> moving<00:08:04.500> pretty<00:08:04.620> well<00:08:04.740> right<00:08:04.919> now 00:08:06.230 --> 00:08:06.240 align:start position:0% but they're moving pretty well right now 00:08:06.240 --> 00:08:07.550 align:start position:0% but they're moving pretty well right now but 00:08:07.550 --> 00:08:07.560 align:start position:0% but 00:08:07.560 --> 00:08:08.870 align:start position:0% but there<00:08:08.099> are<00:08:08.280> actually<00:08:08.400> a<00:08:08.639> number<00:08:08.759> of 00:08:08.870 --> 00:08:08.880 align:start position:0% there are actually a number of 00:08:08.880 --> 00:08:11.330 align:start position:0% there are actually a number of considerations<00:08:09.419> that<00:08:09.780> are<00:08:09.960> at<00:08:10.319> odds<00:08:10.740> with 00:08:11.330 --> 00:08:11.340 align:start position:0% considerations that are at odds with 00:08:11.340 --> 00:08:12.830 align:start position:0% considerations that are at odds with speed<00:08:11.580> things<00:08:12.060> that<00:08:12.300> we're<00:08:12.419> thinking<00:08:12.780> about 00:08:12.830 --> 00:08:12.840 align:start position:0% speed things that we're thinking about 00:08:12.840 --> 00:08:14.570 align:start position:0% speed things that we're thinking about things<00:08:13.259> that<00:08:13.500> we're<00:08:13.620> optimizing<00:08:14.220> at<00:08:14.400> all 00:08:14.570 --> 00:08:14.580 align:start position:0% things that we're optimizing at all 00:08:14.580 --> 00:08:16.370 align:start position:0% things that we're optimizing at all times<00:08:14.759> that 00:08:16.370 --> 00:08:16.380 align:start position:0% times that 00:08:16.380 --> 00:08:17.930 align:start position:0% times that if<00:08:16.860> you<00:08:16.979> looked<00:08:17.220> at<00:08:17.280> it<00:08:17.400> from<00:08:17.580> a<00:08:17.699> naive 00:08:17.930 --> 00:08:17.940 align:start position:0% if you looked at it from a naive 00:08:17.940 --> 00:08:19.430 align:start position:0% if you looked at it from a naive perspective<00:08:18.300> you'd<00:08:18.599> be<00:08:18.599> like<00:08:18.780> you're<00:08:19.080> you're 00:08:19.430 --> 00:08:19.440 align:start position:0% perspective you'd be like you're you're 00:08:19.440 --> 00:08:20.570 align:start position:0% perspective you'd be like you're you're shooting<00:08:19.680> yourself<00:08:19.860> in<00:08:20.099> the<00:08:20.220> foot<00:08:20.340> you're 00:08:20.570 --> 00:08:20.580 align:start position:0% shooting yourself in the foot you're 00:08:20.580 --> 00:08:22.909 align:start position:0% shooting yourself in the foot you're making<00:08:20.879> this<00:08:21.300> hard<00:08:21.599> and<00:08:22.440> there's<00:08:22.560> but<00:08:22.740> there's 00:08:22.909 --> 00:08:22.919 align:start position:0% making this hard and there's but there's 00:08:22.919 --> 00:08:25.249 align:start position:0% making this hard and there's but there's good<00:08:23.099> reason<00:08:23.220> that<00:08:23.460> we<00:08:23.639> make<00:08:23.759> things<00:08:23.940> hard 00:08:25.249 --> 00:08:25.259 align:start position:0% good reason that we make things hard 00:08:25.259 --> 00:08:27.770 align:start position:0% good reason that we make things hard and<00:08:25.860> that's<00:08:26.039> the<00:08:26.520> the<00:08:26.759> metagame<00:08:27.240> of<00:08:27.419> ethereum 00:08:27.770 --> 00:08:27.780 align:start position:0% and that's the the metagame of ethereum 00:08:27.780 --> 00:08:29.270 align:start position:0% and that's the the metagame of ethereum resilience<00:08:28.199> right 00:08:29.270 --> 00:08:29.280 align:start position:0% resilience right 00:08:29.280 --> 00:08:31.610 align:start position:0% resilience right and<00:08:29.879> I<00:08:30.000> might<00:08:30.300> touch<00:08:30.479> on<00:08:30.660> some<00:08:30.840> of<00:08:30.960> this<00:08:31.080> in<00:08:31.440> in 00:08:31.610 --> 00:08:31.620 align:start position:0% and I might touch on some of this in in 00:08:31.620 --> 00:08:32.750 align:start position:0% and I might touch on some of this in in her<00:08:31.800> talk<00:08:31.979> but<00:08:32.219> we're<00:08:32.399> you<00:08:32.520> know<00:08:32.640> we're 00:08:32.750 --> 00:08:32.760 align:start position:0% her talk but we're you know we're 00:08:32.760 --> 00:08:35.510 align:start position:0% her talk but we're you know we're optimizing<00:08:33.180> for<00:08:33.360> an<00:08:33.860> infinite<00:08:34.860> game<00:08:34.979> we're 00:08:35.510 --> 00:08:35.520 align:start position:0% optimizing for an infinite game we're 00:08:35.520 --> 00:08:38.029 align:start position:0% optimizing for an infinite game we're not<00:08:35.700> optimizing<00:08:36.360> for<00:08:36.779> a<00:08:37.200> pump<00:08:37.320> and<00:08:37.500> dump<00:08:37.680> we're 00:08:38.029 --> 00:08:38.039 align:start position:0% not optimizing for a pump and dump we're 00:08:38.039 --> 00:08:40.070 align:start position:0% not optimizing for a pump and dump we're not<00:08:38.219> optimizing<00:08:38.880> for<00:08:39.180> an<00:08:39.419> acquisition<00:08:39.779> we're 00:08:40.070 --> 00:08:40.080 align:start position:0% not optimizing for an acquisition we're 00:08:40.080 --> 00:08:42.290 align:start position:0% not optimizing for an acquisition we're not<00:08:40.200> optimizing<00:08:40.860> for<00:08:41.279> uh<00:08:41.820> you<00:08:42.000> know<00:08:42.060> people 00:08:42.290 --> 00:08:42.300 align:start position:0% not optimizing for uh you know people 00:08:42.300 --> 00:08:44.089 align:start position:0% not optimizing for uh you know people being<00:08:42.599> rich<00:08:42.899> tomorrow<00:08:43.320> you<00:08:43.919> know<00:08:44.039> we're 00:08:44.089 --> 00:08:44.099 align:start position:0% being rich tomorrow you know we're 00:08:44.099 --> 00:08:47.090 align:start position:0% being rich tomorrow you know we're optimizing<00:08:44.580> for<00:08:44.760> ethereum<00:08:45.720> existing<00:08:46.620> and 00:08:47.090 --> 00:08:47.100 align:start position:0% optimizing for ethereum existing and 00:08:47.100 --> 00:08:49.610 align:start position:0% optimizing for ethereum existing and running<00:08:47.339> for<00:08:47.820> 50<00:08:48.060> plus<00:08:48.360> 100<00:08:48.660> plus<00:08:48.959> years<00:08:49.260> and 00:08:49.610 --> 00:08:49.620 align:start position:0% running for 50 plus 100 plus years and 00:08:49.620 --> 00:08:52.009 align:start position:0% running for 50 plus 100 plus years and being<00:08:49.860> a<00:08:50.160> fundamentally<00:08:50.700> uh<00:08:51.540> foundational 00:08:52.009 --> 00:08:52.019 align:start position:0% being a fundamentally uh foundational 00:08:52.019 --> 00:08:53.570 align:start position:0% being a fundamentally uh foundational protocol<00:08:52.560> of<00:08:52.920> the<00:08:53.040> internet<00:08:53.100> and<00:08:53.399> for 00:08:53.570 --> 00:08:53.580 align:start position:0% protocol of the internet and for 00:08:53.580 --> 00:08:55.910 align:start position:0% protocol of the internet and for Humanity<00:08:54.000> so<00:08:54.540> we're<00:08:54.720> trying<00:08:54.959> to<00:08:55.200> we're<00:08:55.680> trying 00:08:55.910 --> 00:08:55.920 align:start position:0% Humanity so we're trying to we're trying 00:08:55.920 --> 00:08:58.910 align:start position:0% Humanity so we're trying to we're trying to<00:08:56.100> continue<00:08:56.880> to<00:08:57.180> play<00:08:57.360> the<00:08:57.540> game 00:08:58.910 --> 00:08:58.920 align:start position:0% to continue to play the game 00:08:58.920 --> 00:09:01.930 align:start position:0% to continue to play the game nothing 00:09:01.930 --> 00:09:01.940 align:start position:0% 00:09:01.940 --> 00:09:04.490 align:start position:0% we're<00:09:02.940> trying<00:09:03.120> to<00:09:03.240> have<00:09:03.360> redundancy<00:09:04.080> built 00:09:04.490 --> 00:09:04.500 align:start position:0% we're trying to have redundancy built 00:09:04.500 --> 00:09:05.990 align:start position:0% we're trying to have redundancy built into<00:09:04.560> the<00:09:04.800> game<00:09:04.920> we're<00:09:05.279> trying<00:09:05.459> to<00:09:05.580> be<00:09:05.700> able<00:09:05.820> to 00:09:05.990 --> 00:09:06.000 align:start position:0% into the game we're trying to be able to 00:09:06.000 --> 00:09:08.030 align:start position:0% into the game we're trying to be able to recover<00:09:06.540> in<00:09:06.899> the<00:09:07.019> event<00:09:07.140> that<00:09:07.380> the<00:09:07.560> game<00:09:07.620> fails 00:09:08.030 --> 00:09:08.040 align:start position:0% recover in the event that the game fails 00:09:08.040 --> 00:09:09.350 align:start position:0% recover in the event that the game fails when<00:09:08.220> you're<00:09:08.339> thinking<00:09:08.580> about<00:09:08.640> 50<00:09:08.820> plus<00:09:09.120> years 00:09:09.350 --> 00:09:09.360 align:start position:0% when you're thinking about 50 plus years 00:09:09.360 --> 00:09:10.730 align:start position:0% when you're thinking about 50 plus years like 00:09:10.730 --> 00:09:10.740 align:start position:0% like 00:09:10.740 --> 00:09:12.590 align:start position:0% like shit's<00:09:11.220> gonna<00:09:11.399> happen<00:09:11.700> and<00:09:12.180> we<00:09:12.300> need<00:09:12.420> to<00:09:12.480> be 00:09:12.590 --> 00:09:12.600 align:start position:0% shit's gonna happen and we need to be 00:09:12.600 --> 00:09:13.670 align:start position:0% shit's gonna happen and we need to be able<00:09:12.660> to<00:09:12.779> pick<00:09:12.899> up<00:09:13.019> the<00:09:13.140> pieces<00:09:13.440> and<00:09:13.560> keep 00:09:13.670 --> 00:09:13.680 align:start position:0% able to pick up the pieces and keep 00:09:13.680 --> 00:09:15.949 align:start position:0% able to pick up the pieces and keep moving<00:09:13.920> and<00:09:14.399> in<00:09:14.580> fact<00:09:14.700> we<00:09:15.360> need<00:09:15.480> to<00:09:15.600> be<00:09:15.660> able<00:09:15.779> to 00:09:15.949 --> 00:09:15.959 align:start position:0% moving and in fact we need to be able to 00:09:15.959 --> 00:09:19.190 align:start position:0% moving and in fact we need to be able to harden<00:09:16.440> under<00:09:16.920> after<00:09:17.880> this<00:09:18.240> adversity<00:09:18.779> you 00:09:19.190 --> 00:09:19.200 align:start position:0% harden under after this adversity you 00:09:19.200 --> 00:09:20.630 align:start position:0% harden under after this adversity you know<00:09:19.320> not<00:09:19.500> only<00:09:19.680> do<00:09:19.980> you<00:09:20.100> can<00:09:20.279> you<00:09:20.399> pick<00:09:20.519> the 00:09:20.630 --> 00:09:20.640 align:start position:0% know not only do you can you pick the 00:09:20.640 --> 00:09:21.829 align:start position:0% know not only do you can you pick the pieces<00:09:20.880> back<00:09:21.060> up<00:09:21.180> but<00:09:21.300> can<00:09:21.480> you<00:09:21.600> come<00:09:21.660> back 00:09:21.829 --> 00:09:21.839 align:start position:0% pieces back up but can you come back 00:09:21.839 --> 00:09:24.769 align:start position:0% pieces back up but can you come back stronger<00:09:22.260> and<00:09:22.980> tuning<00:09:23.760> for<00:09:23.940> ossification<00:09:24.480> and 00:09:24.769 --> 00:09:24.779 align:start position:0% stronger and tuning for ossification and 00:09:24.779 --> 00:09:26.750 align:start position:0% stronger and tuning for ossification and avoidance<00:09:25.200> of<00:09:25.320> capture<00:09:25.740> you<00:09:26.220> know<00:09:26.279> the<00:09:26.580> the 00:09:26.750 --> 00:09:26.760 align:start position:0% avoidance of capture you know the the 00:09:26.760 --> 00:09:28.970 align:start position:0% avoidance of capture you know the the more<00:09:27.180> valuable<00:09:27.660> this<00:09:27.899> thing<00:09:28.080> is<00:09:28.260> the<00:09:28.860> more 00:09:28.970 --> 00:09:28.980 align:start position:0% more valuable this thing is the more 00:09:28.980 --> 00:09:30.470 align:start position:0% more valuable this thing is the more it's<00:09:29.160> valuable<00:09:29.519> for<00:09:29.820> people<00:09:29.940> to<00:09:30.180> kind<00:09:30.240> of<00:09:30.360> get 00:09:30.470 --> 00:09:30.480 align:start position:0% it's valuable for people to kind of get 00:09:30.480 --> 00:09:32.269 align:start position:0% it's valuable for people to kind of get their<00:09:30.660> hands<00:09:31.019> in<00:09:31.140> get<00:09:31.560> their<00:09:31.740> interests<00:09:32.160> in 00:09:32.269 --> 00:09:32.279 align:start position:0% their hands in get their interests in 00:09:32.279 --> 00:09:34.310 align:start position:0% their hands in get their interests in and<00:09:32.700> this<00:09:33.060> thing<00:09:33.180> needs<00:09:33.540> to<00:09:33.600> be<00:09:33.839> robust 00:09:34.310 --> 00:09:34.320 align:start position:0% and this thing needs to be robust 00:09:34.320 --> 00:09:35.870 align:start position:0% and this thing needs to be robust against 00:09:35.870 --> 00:09:35.880 align:start position:0% against 00:09:35.880 --> 00:09:37.310 align:start position:0% against anything<00:09:36.420> that<00:09:36.720> might<00:09:36.839> happen<00:09:36.959> in<00:09:37.140> the<00:09:37.260> next 00:09:37.310 --> 00:09:37.320 align:start position:0% anything that might happen in the next 00:09:37.320 --> 00:09:40.070 align:start position:0% anything that might happen in the next 50<00:09:37.560> years<00:09:37.740> 100<00:09:37.980> years 00:09:40.070 --> 00:09:40.080 align:start position:0% 50 years 100 years 00:09:40.080 --> 00:09:41.269 align:start position:0% 50 years 100 years and 00:09:41.269 --> 00:09:41.279 align:start position:0% and 00:09:41.279 --> 00:09:42.710 align:start position:0% and one<00:09:41.700> more<00:09:41.820> thing<00:09:41.940> when<00:09:42.180> we're<00:09:42.300> thinking<00:09:42.540> about 00:09:42.710 --> 00:09:42.720 align:start position:0% one more thing when we're thinking about 00:09:42.720 --> 00:09:44.509 align:start position:0% one more thing when we're thinking about ethereum<00:09:43.620> resilience<00:09:43.980> there's<00:09:44.160> a<00:09:44.339> number<00:09:44.399> of 00:09:44.509 --> 00:09:44.519 align:start position:0% ethereum resilience there's a number of 00:09:44.519 --> 00:09:46.250 align:start position:0% ethereum resilience there's a number of like<00:09:44.700> ways<00:09:45.420> that<00:09:45.540> we<00:09:45.660> might<00:09:45.779> think<00:09:45.899> about<00:09:46.080> it 00:09:46.250 --> 00:09:46.260 align:start position:0% like ways that we might think about it 00:09:46.260 --> 00:09:48.350 align:start position:0% like ways that we might think about it the<00:09:46.860> the<00:09:47.040> most<00:09:47.399> obvious<00:09:47.760> is<00:09:48.000> probably<00:09:48.180> the 00:09:48.350 --> 00:09:48.360 align:start position:0% the the most obvious is probably the 00:09:48.360 --> 00:09:50.210 align:start position:0% the the most obvious is probably the first<00:09:48.540> the<00:09:48.779> protocol<00:09:49.140> like<00:09:49.740> we're<00:09:49.920> trying<00:09:50.100> to 00:09:50.210 --> 00:09:50.220 align:start position:0% first the protocol like we're trying to 00:09:50.220 --> 00:09:51.949 align:start position:0% first the protocol like we're trying to make<00:09:50.339> sure<00:09:50.519> this<00:09:50.760> is<00:09:50.880> a<00:09:51.060> resilient<00:09:51.420> protocol 00:09:51.949 --> 00:09:51.959 align:start position:0% make sure this is a resilient protocol 00:09:51.959 --> 00:09:54.829 align:start position:0% make sure this is a resilient protocol that<00:09:52.380> this<00:09:52.620> thing<00:09:52.800> works<00:09:53.399> next<00:09:54.120> is<00:09:54.420> is<00:09:54.600> kind<00:09:54.779> of 00:09:54.829 --> 00:09:54.839 align:start position:0% that this thing works next is is kind of 00:09:54.839 --> 00:09:56.690 align:start position:0% that this thing works next is is kind of the<00:09:54.959> instantiation<00:09:55.740> of<00:09:55.980> the<00:09:56.160> protocol<00:09:56.399> that's 00:09:56.690 --> 00:09:56.700 align:start position:0% the instantiation of the protocol that's 00:09:56.700 --> 00:09:59.750 align:start position:0% the instantiation of the protocol that's the<00:09:56.880> network<00:09:57.060> that's<00:09:57.420> like<00:09:57.600> does<00:09:58.500> this<00:09:58.860> not 00:09:59.750 --> 00:09:59.760 align:start position:0% the network that's like does this not 00:09:59.760 --> 00:10:01.130 align:start position:0% the network that's like does this not only<00:09:59.940> fundamentally<00:10:00.480> this<00:10:00.779> abstract 00:10:01.130 --> 00:10:01.140 align:start position:0% only fundamentally this abstract 00:10:01.140 --> 00:10:03.949 align:start position:0% only fundamentally this abstract protocol<00:10:01.500> work<00:10:01.800> but<00:10:01.980> does<00:10:02.220> it<00:10:02.399> work<00:10:02.760> live<00:10:03.660> and 00:10:03.949 --> 00:10:03.959 align:start position:0% protocol work but does it work live and 00:10:03.959 --> 00:10:06.470 align:start position:0% protocol work but does it work live and is<00:10:04.140> it<00:10:04.320> resilient<00:10:04.740> in<00:10:05.160> its<00:10:05.399> instantiation<00:10:06.060> of 00:10:06.470 --> 00:10:06.480 align:start position:0% is it resilient in its instantiation of 00:10:06.480 --> 00:10:08.329 align:start position:0% is it resilient in its instantiation of tons<00:10:06.779> of<00:10:07.019> computers<00:10:07.500> distributed<00:10:07.920> across<00:10:08.279> the 00:10:08.329 --> 00:10:08.339 align:start position:0% tons of computers distributed across the 00:10:08.339 --> 00:10:10.190 align:start position:0% tons of computers distributed across the world<00:10:08.459> doing<00:10:09.000> their<00:10:09.300> thing<00:10:09.480> and<00:10:09.959> then<00:10:10.019> there's 00:10:10.190 --> 00:10:10.200 align:start position:0% world doing their thing and then there's 00:10:10.200 --> 00:10:11.870 align:start position:0% world doing their thing and then there's the<00:10:10.380> kind<00:10:10.500> of<00:10:10.620> the<00:10:10.740> social<00:10:10.920> layer<00:10:11.399> on<00:10:11.519> top<00:10:11.700> is 00:10:11.870 --> 00:10:11.880 align:start position:0% the kind of the social layer on top is 00:10:11.880 --> 00:10:13.790 align:start position:0% the kind of the social layer on top is the<00:10:12.120> social<00:10:12.240> layer<00:10:12.660> resilient<00:10:13.140> is<00:10:13.500> the<00:10:13.740> social 00:10:13.790 --> 00:10:13.800 align:start position:0% the social layer resilient is the social 00:10:13.800 --> 00:10:16.250 align:start position:0% the social layer resilient is the social error<00:10:14.279> can<00:10:14.399> people<00:10:14.580> come<00:10:14.820> and<00:10:14.940> go<00:10:15.120> Can<00:10:15.720> it<00:10:16.019> can 00:10:16.250 --> 00:10:16.260 align:start position:0% error can people come and go Can it can 00:10:16.260 --> 00:10:18.050 align:start position:0% error can people come and go Can it can we<00:10:16.380> avoid<00:10:16.680> capture<00:10:17.100> can<00:10:17.279> we<00:10:17.459> deal<00:10:17.580> with<00:10:17.760> with 00:10:18.050 --> 00:10:18.060 align:start position:0% we avoid capture can we deal with with 00:10:18.060 --> 00:10:19.850 align:start position:0% we avoid capture can we deal with with issues<00:10:18.540> in<00:10:18.660> that<00:10:18.779> layer 00:10:19.850 --> 00:10:19.860 align:start position:0% issues in that layer 00:10:19.860 --> 00:10:22.430 align:start position:0% issues in that layer and<00:10:20.339> get<00:10:20.519> I<00:10:20.760> can<00:10:20.820> get<00:10:20.940> into<00:10:21.060> each<00:10:21.240> one<00:10:21.420> of<00:10:21.540> those 00:10:22.430 --> 00:10:22.440 align:start position:0% and get I can get into each one of those 00:10:22.440 --> 00:10:24.650 align:start position:0% and get I can get into each one of those oh<00:10:22.980> and<00:10:23.220> shortcuts<00:10:24.120> are<00:10:24.240> obviously<00:10:24.540> available 00:10:24.650 --> 00:10:24.660 align:start position:0% oh and shortcuts are obviously available 00:10:24.660 --> 00:10:26.750 align:start position:0% oh and shortcuts are obviously available we<00:10:25.200> could<00:10:25.260> have<00:10:25.380> a<00:10:25.500> single<00:10:25.740> client<00:10:25.980> we<00:10:26.640> could 00:10:26.750 --> 00:10:26.760 align:start position:0% we could have a single client we could 00:10:26.760 --> 00:10:28.310 align:start position:0% we could have a single client we could have<00:10:26.880> a<00:10:27.000> single<00:10:27.120> dictator<00:10:27.420> we<00:10:28.080> could<00:10:28.200> have 00:10:28.310 --> 00:10:28.320 align:start position:0% have a single dictator we could have 00:10:28.320 --> 00:10:30.290 align:start position:0% have a single dictator we could have truncated<00:10:28.680> r<00:10:28.920> d<00:10:29.100> and<00:10:29.399> just<00:10:29.519> ship<00:10:29.700> it<00:10:29.880> we<00:10:30.180> could 00:10:30.290 --> 00:10:30.300 align:start position:0% truncated r d and just ship it we could 00:10:30.300 --> 00:10:31.910 align:start position:0% truncated r d and just ship it we could have<00:10:30.420> easy<00:10:30.660> centralizing<00:10:31.380> solutions<00:10:31.680> we 00:10:31.910 --> 00:10:31.920 align:start position:0% have easy centralizing solutions we 00:10:31.920 --> 00:10:33.170 align:start position:0% have easy centralizing solutions we could<00:10:32.040> have<00:10:32.160> a<00:10:32.279> willingness<00:10:32.640> for<00:10:32.820> downtime 00:10:33.170 --> 00:10:33.180 align:start position:0% could have a willingness for downtime 00:10:33.180 --> 00:10:34.850 align:start position:0% could have a willingness for downtime and<00:10:33.540> we<00:10:33.660> could<00:10:33.779> have<00:10:33.899> processes<00:10:34.380> that<00:10:34.740> are 00:10:34.850 --> 00:10:34.860 align:start position:0% and we could have processes that are 00:10:34.860 --> 00:10:36.110 align:start position:0% and we could have processes that are right<00:10:34.980> for<00:10:35.160> capture 00:10:36.110 --> 00:10:36.120 align:start position:0% right for capture 00:10:36.120 --> 00:10:37.730 align:start position:0% right for capture that's<00:10:36.540> not<00:10:36.660> what<00:10:36.779> we're<00:10:36.899> doing<00:10:37.080> and<00:10:37.620> that's 00:10:37.730 --> 00:10:37.740 align:start position:0% that's not what we're doing and that's 00:10:37.740 --> 00:10:39.470 align:start position:0% that's not what we're doing and that's why<00:10:37.980> it's<00:10:38.100> taking<00:10:38.339> a<00:10:38.580> long<00:10:38.700> time<00:10:38.880> and<00:10:39.300> that's 00:10:39.470 --> 00:10:39.480 align:start position:0% why it's taking a long time and that's 00:10:39.480 --> 00:10:42.889 align:start position:0% why it's taking a long time and that's why 00:10:42.889 --> 00:10:42.899 align:start position:0% 00:10:42.899 --> 00:10:45.829 align:start position:0% that's<00:10:43.260> how<00:10:43.440> it<00:10:43.560> is 00:10:45.829 --> 00:10:45.839 align:start position:0% 00:10:45.839 --> 00:10:47.690 align:start position:0% so 00:10:47.690 --> 00:10:47.700 align:start position:0% so 00:10:47.700 --> 00:10:49.670 align:start position:0% so protocol<00:10:48.360> resilience 00:10:49.670 --> 00:10:49.680 align:start position:0% protocol resilience 00:10:49.680 --> 00:10:50.810 align:start position:0% protocol resilience there's<00:10:50.040> a<00:10:50.220> lot<00:10:50.279> of<00:10:50.399> things<00:10:50.519> that<00:10:50.640> go<00:10:50.760> into 00:10:50.810 --> 00:10:50.820 align:start position:0% there's a lot of things that go into 00:10:50.820 --> 00:10:52.910 align:start position:0% there's a lot of things that go into this<00:10:51.060> this<00:10:51.720> is<00:10:51.899> probably<00:10:52.140> again<00:10:52.380> one<00:10:52.800> of<00:10:52.860> the 00:10:52.910 --> 00:10:52.920 align:start position:0% this this is probably again one of the 00:10:52.920 --> 00:10:54.650 align:start position:0% this this is probably again one of the more<00:10:52.980> obvious<00:10:53.279> things<00:10:53.519> tons<00:10:54.120> of<00:10:54.240> research<00:10:54.480> and 00:10:54.650 --> 00:10:54.660 align:start position:0% more obvious things tons of research and 00:10:54.660 --> 00:10:56.269 align:start position:0% more obvious things tons of research and design<00:10:54.839> tons<00:10:55.500> of<00:10:55.620> security<00:10:55.740> and<00:10:55.980> testing 00:10:56.269 --> 00:10:56.279 align:start position:0% design tons of security and testing 00:10:56.279 --> 00:10:58.550 align:start position:0% design tons of security and testing nothing<00:10:56.519> goes<00:10:56.820> out<00:10:56.940> lightly<00:10:57.360> the<00:10:58.079> the<00:10:58.200> amount 00:10:58.550 --> 00:10:58.560 align:start position:0% nothing goes out lightly the the amount 00:10:58.560 --> 00:11:01.250 align:start position:0% nothing goes out lightly the the amount of<00:10:58.680> time<00:10:58.980> and<00:10:59.279> effort<00:10:59.519> put<00:10:59.760> on<00:10:59.940> Simplicity<00:11:00.660> in 00:11:01.250 --> 00:11:01.260 align:start position:0% of time and effort put on Simplicity in 00:11:01.260 --> 00:11:02.810 align:start position:0% of time and effort put on Simplicity in ensuring<00:11:01.680> that<00:11:01.860> the<00:11:01.980> system<00:11:02.220> is<00:11:02.579> generally 00:11:02.810 --> 00:11:02.820 align:start position:0% ensuring that the system is generally 00:11:02.820 --> 00:11:06.829 align:start position:0% ensuring that the system is generally extensible<00:11:03.600> over<00:11:04.200> time<00:11:04.440> is<00:11:04.860> is<00:11:05.100> profound<00:11:05.839> if 00:11:06.829 --> 00:11:06.839 align:start position:0% extensible over time is is profound if 00:11:06.839 --> 00:11:07.790 align:start position:0% extensible over time is is profound if you 00:11:07.790 --> 00:11:07.800 align:start position:0% you 00:11:07.800 --> 00:11:10.310 align:start position:0% you there's<00:11:08.339> a<00:11:08.519> lot<00:11:08.579> of<00:11:08.700> hard<00:11:08.940> jobs<00:11:09.240> in<00:11:09.899> ethereum 00:11:10.310 --> 00:11:10.320 align:start position:0% there's a lot of hard jobs in ethereum 00:11:10.320 --> 00:11:13.250 align:start position:0% there's a lot of hard jobs in ethereum L1<00:11:11.040> but<00:11:11.880> if<00:11:12.120> you've<00:11:12.300> done<00:11:12.480> if<00:11:12.839> you've<00:11:12.959> worked 00:11:13.250 --> 00:11:13.260 align:start position:0% L1 but if you've done if you've worked 00:11:13.260 --> 00:11:15.050 align:start position:0% L1 but if you've done if you've worked on<00:11:13.380> research<00:11:13.680> for<00:11:13.860> any<00:11:13.980> amount<00:11:14.279> of<00:11:14.399> time<00:11:14.579> in 00:11:15.050 --> 00:11:15.060 align:start position:0% on research for any amount of time in 00:11:15.060 --> 00:11:17.449 align:start position:0% on research for any amount of time in this<00:11:15.240> space<00:11:15.420> you've<00:11:16.079> thrown<00:11:16.380> out<00:11:16.620> things<00:11:17.220> that 00:11:17.449 --> 00:11:17.459 align:start position:0% this space you've thrown out things that 00:11:17.459 --> 00:11:19.069 align:start position:0% this space you've thrown out things that you've<00:11:17.640> worked<00:11:17.880> on<00:11:18.000> for<00:11:18.360> easily<00:11:18.839> a<00:11:18.959> year 00:11:19.069 --> 00:11:19.079 align:start position:0% you've worked on for easily a year 00:11:19.079 --> 00:11:21.050 align:start position:0% you've worked on for easily a year things<00:11:19.380> you've<00:11:19.620> spent<00:11:19.860> countless<00:11:20.579> amounts<00:11:21.000> of 00:11:21.050 --> 00:11:21.060 align:start position:0% things you've spent countless amounts of 00:11:21.060 --> 00:11:22.009 align:start position:0% things you've spent countless amounts of time<00:11:21.240> and<00:11:21.420> you<00:11:21.540> just<00:11:21.600> been<00:11:21.720> like<00:11:21.839> you<00:11:21.959> know 00:11:22.009 --> 00:11:22.019 align:start position:0% time and you just been like you know 00:11:22.019 --> 00:11:23.150 align:start position:0% time and you just been like you know what<00:11:22.140> it's<00:11:22.260> not<00:11:22.380> right<00:11:22.560> it's<00:11:22.860> not<00:11:22.980> simple 00:11:23.150 --> 00:11:23.160 align:start position:0% what it's not right it's not simple 00:11:23.160 --> 00:11:24.769 align:start position:0% what it's not right it's not simple enough<00:11:23.399> it's<00:11:23.700> not<00:11:23.880> right<00:11:24.000> for<00:11:24.180> ethereum<00:11:24.600> and 00:11:24.769 --> 00:11:24.779 align:start position:0% enough it's not right for ethereum and 00:11:24.779 --> 00:11:26.990 align:start position:0% enough it's not right for ethereum and and<00:11:24.959> that<00:11:25.200> that<00:11:25.440> is<00:11:25.620> a<00:11:25.860> regular<00:11:26.160> regular 00:11:26.990 --> 00:11:27.000 align:start position:0% and that that is a regular regular 00:11:27.000 --> 00:11:29.449 align:start position:0% and that that is a regular regular component<00:11:27.480> of<00:11:27.600> this<00:11:27.720> process<00:11:28.100> being<00:11:29.100> able<00:11:29.339> to 00:11:29.449 --> 00:11:29.459 align:start position:0% component of this process being able to 00:11:29.459 --> 00:11:32.150 align:start position:0% component of this process being able to operate<00:11:29.760> under<00:11:30.000> adverse<00:11:30.620> conditions<00:11:31.620> and<00:11:32.040> be 00:11:32.150 --> 00:11:32.160 align:start position:0% operate under adverse conditions and be 00:11:32.160 --> 00:11:33.470 align:start position:0% operate under adverse conditions and be able<00:11:32.339> to<00:11:32.399> recover<00:11:32.640> under<00:11:32.880> these<00:11:33.120> failure 00:11:33.470 --> 00:11:33.480 align:start position:0% able to recover under these failure 00:11:33.480 --> 00:11:36.230 align:start position:0% able to recover under these failure modes<00:11:33.779> I<00:11:34.380> think<00:11:34.620> one<00:11:35.459> thing<00:11:35.640> that's<00:11:35.940> a<00:11:36.120> very 00:11:36.230 --> 00:11:36.240 align:start position:0% modes I think one thing that's a very 00:11:36.240 --> 00:11:38.210 align:start position:0% modes I think one thing that's a very Guiding<00:11:36.600> Light<00:11:36.779> and<00:11:37.140> I<00:11:37.320> highly<00:11:37.860> recommend 00:11:38.210 --> 00:11:38.220 align:start position:0% Guiding Light and I highly recommend 00:11:38.220 --> 00:11:39.650 align:start position:0% Guiding Light and I highly recommend vitalik's<00:11:38.880> piece<00:11:39.120> on<00:11:39.180> functional<00:11:39.540> escape 00:11:39.650 --> 00:11:39.660 align:start position:0% vitalik's piece on functional escape 00:11:39.660 --> 00:11:42.889 align:start position:0% vitalik's piece on functional escape velocity<00:11:40.260> but<00:11:41.040> we're<00:11:41.399> we're<00:11:41.760> looking<00:11:42.240> for<00:11:42.600> you 00:11:42.889 --> 00:11:42.899 align:start position:0% velocity but we're we're looking for you 00:11:42.899 --> 00:11:44.150 align:start position:0% velocity but we're we're looking for you know<00:11:43.019> you<00:11:43.140> can<00:11:43.260> throw<00:11:43.380> everything<00:11:43.740> out<00:11:44.040> of 00:11:44.150 --> 00:11:44.160 align:start position:0% know you can throw everything out of 00:11:44.160 --> 00:11:45.769 align:start position:0% know you can throw everything out of protocol<00:11:44.399> you<00:11:44.880> can<00:11:44.940> you<00:11:45.240> can<00:11:45.360> try<00:11:45.540> to<00:11:45.660> build 00:11:45.769 --> 00:11:45.779 align:start position:0% protocol you can you can try to build 00:11:45.779 --> 00:11:47.090 align:start position:0% protocol you can you can try to build everything<00:11:46.079> into<00:11:46.260> the<00:11:46.500> protocol<00:11:46.680> you<00:11:46.980> can 00:11:47.090 --> 00:11:47.100 align:start position:0% everything into the protocol you can 00:11:47.100 --> 00:11:48.230 align:start position:0% everything into the protocol you can just<00:11:47.220> be<00:11:47.279> like<00:11:47.459> okay<00:11:47.579> this<00:11:47.880> is<00:11:47.940> good<00:11:48.060> let's 00:11:48.230 --> 00:11:48.240 align:start position:0% just be like okay this is good let's 00:11:48.240 --> 00:11:49.370 align:start position:0% just be like okay this is good let's throw<00:11:48.420> it<00:11:48.540> in<00:11:48.660> okay<00:11:48.839> this<00:11:49.019> is<00:11:49.140> good<00:11:49.260> let's 00:11:49.370 --> 00:11:49.380 align:start position:0% throw it in okay this is good let's 00:11:49.380 --> 00:11:50.690 align:start position:0% throw it in okay this is good let's throw<00:11:49.560> it<00:11:49.680> in<00:11:49.800> but<00:11:50.100> instead<00:11:50.339> we're<00:11:50.519> looking 00:11:50.690 --> 00:11:50.700 align:start position:0% throw it in but instead we're looking 00:11:50.700 --> 00:11:52.250 align:start position:0% throw it in but instead we're looking for<00:11:50.820> that<00:11:51.000> minimum<00:11:51.420> functional<00:11:52.079> escape 00:11:52.250 --> 00:11:52.260 align:start position:0% for that minimum functional escape 00:11:52.260 --> 00:11:54.710 align:start position:0% for that minimum functional escape velocity<00:11:52.800> and<00:11:53.160> that's<00:11:53.279> an<00:11:53.459> art<00:11:53.640> you<00:11:54.540> know<00:11:54.600> you 00:11:54.710 --> 00:11:54.720 align:start position:0% velocity and that's an art you know you 00:11:54.720 --> 00:11:55.730 align:start position:0% velocity and that's an art you know you don't<00:11:54.779> get<00:11:54.899> that<00:11:55.019> easily<00:11:55.320> you<00:11:55.440> get<00:11:55.620> that 00:11:55.730 --> 00:11:55.740 align:start position:0% don't get that easily you get that 00:11:55.740 --> 00:11:57.769 align:start position:0% don't get that easily you get that through<00:11:55.920> years<00:11:56.160> and<00:11:56.820> years<00:11:57.000> of<00:11:57.300> thought<00:11:57.480> and 00:11:57.769 --> 00:11:57.779 align:start position:0% through years and years of thought and 00:11:57.779 --> 00:11:59.269 align:start position:0% through years and years of thought and iteration 00:11:59.269 --> 00:11:59.279 align:start position:0% iteration 00:11:59.279 --> 00:12:02.449 align:start position:0% iteration and<00:12:00.480> many<00:12:00.959> protocols<00:12:01.620> only<00:12:01.800> try<00:12:02.040> to<00:12:02.160> avoid 00:12:02.449 --> 00:12:02.459 align:start position:0% and many protocols only try to avoid 00:12:02.459 --> 00:12:05.030 align:start position:0% and many protocols only try to avoid failure<00:12:02.820> whereas<00:12:03.360> ethereum<00:12:03.839> is<00:12:04.260> borderline 00:12:05.030 --> 00:12:05.040 align:start position:0% failure whereas ethereum is borderline 00:12:05.040 --> 00:12:08.030 align:start position:0% failure whereas ethereum is borderline obsessive<00:12:05.760> with<00:12:06.540> the<00:12:06.959> fact<00:12:07.079> that<00:12:07.440> it<00:12:07.680> likely 00:12:08.030 --> 00:12:08.040 align:start position:0% obsessive with the fact that it likely 00:12:08.040 --> 00:12:10.910 align:start position:0% obsessive with the fact that it likely like<00:12:08.399> something<00:12:08.640> can<00:12:09.180> fail<00:12:09.480> and<00:12:10.079> like<00:12:10.500> all<00:12:10.800> of 00:12:10.910 --> 00:12:10.920 align:start position:0% like something can fail and like all of 00:12:10.920 --> 00:12:12.470 align:start position:0% like something can fail and like all of these<00:12:11.100> protocols 00:12:12.470 --> 00:12:12.480 align:start position:0% these protocols 00:12:12.480 --> 00:12:14.030 align:start position:0% these protocols essentially<00:12:13.200> in<00:12:13.320> a<00:12:13.440> crypto<00:12:13.620> economic 00:12:14.030 --> 00:12:14.040 align:start position:0% essentially in a crypto economic 00:12:14.040 --> 00:12:16.190 align:start position:0% essentially in a crypto economic protocol<00:12:14.279> it's<00:12:14.579> you<00:12:15.240> get<00:12:15.420> X<00:12:15.660> properties 00:12:16.190 --> 00:12:16.200 align:start position:0% protocol it's you get X properties 00:12:16.200 --> 00:12:18.829 align:start position:0% protocol it's you get X properties unless<00:12:16.800> this<00:12:17.700> thing<00:12:17.820> happens<00:12:18.060> usually<00:12:18.540> this 00:12:18.829 --> 00:12:18.839 align:start position:0% unless this thing happens usually this 00:12:18.839 --> 00:12:21.050 align:start position:0% unless this thing happens usually this thing<00:12:18.959> happening<00:12:19.380> being<00:12:19.680> some<00:12:20.220> size<00:12:20.459> attacker 00:12:21.050 --> 00:12:21.060 align:start position:0% thing happening being some size attacker 00:12:21.060 --> 00:12:22.370 align:start position:0% thing happening being some size attacker someone<00:12:21.360> willing<00:12:21.839> to<00:12:21.899> throw<00:12:22.019> a<00:12:22.200> bunch<00:12:22.260> of 00:12:22.370 --> 00:12:22.380 align:start position:0% someone willing to throw a bunch of 00:12:22.380 --> 00:12:24.410 align:start position:0% someone willing to throw a bunch of money<00:12:22.500> or<00:12:22.680> burn<00:12:22.860> a<00:12:23.040> bunch<00:12:23.160> of<00:12:23.220> money<00:12:23.399> and<00:12:24.060> you 00:12:24.410 --> 00:12:24.420 align:start position:0% money or burn a bunch of money and you 00:12:24.420 --> 00:12:25.850 align:start position:0% money or burn a bunch of money and you know<00:12:24.540> protocols<00:12:25.079> work<00:12:25.200> unless<00:12:25.500> you<00:12:25.560> hit<00:12:25.680> those 00:12:25.850 --> 00:12:25.860 align:start position:0% know protocols work unless you hit those 00:12:25.860 --> 00:12:28.430 align:start position:0% know protocols work unless you hit those thresholds<00:12:26.399> but<00:12:26.760> in<00:12:27.540> 50<00:12:27.720> plus<00:12:27.959> year<00:12:28.140> time 00:12:28.430 --> 00:12:28.440 align:start position:0% thresholds but in 50 plus year time 00:12:28.440 --> 00:12:31.069 align:start position:0% thresholds but in 50 plus year time Horizon<00:12:28.740> we're<00:12:29.399> going<00:12:29.579> to<00:12:29.700> hit<00:12:29.820> like 00:12:31.069 --> 00:12:31.079 align:start position:0% Horizon we're going to hit like 00:12:31.079 --> 00:12:33.470 align:start position:0% Horizon we're going to hit like not<00:12:31.740> necessarily<00:12:32.339> you<00:12:32.640> I<00:12:32.880> can't<00:12:33.060> predict<00:12:33.300> the 00:12:33.470 --> 00:12:33.480 align:start position:0% not necessarily you I can't predict the 00:12:33.480 --> 00:12:35.269 align:start position:0% not necessarily you I can't predict the future<00:12:33.600> but<00:12:33.839> like<00:12:34.440> happens<00:12:34.740> and<00:12:35.040> we<00:12:35.160> need 00:12:35.269 --> 00:12:35.279 align:start position:0% future but like happens and we need 00:12:35.279 --> 00:12:37.430 align:start position:0% future but like happens and we need to<00:12:35.459> we're<00:12:35.760> borderline<00:12:36.180> obsessive<00:12:36.720> with<00:12:36.959> not 00:12:37.430 --> 00:12:37.440 align:start position:0% to we're borderline obsessive with not 00:12:37.440 --> 00:12:39.050 align:start position:0% to we're borderline obsessive with not only<00:12:37.560> trying<00:12:37.800> to<00:12:38.040> avoid<00:12:38.339> these<00:12:38.579> failures<00:12:38.820> but 00:12:39.050 --> 00:12:39.060 align:start position:0% only trying to avoid these failures but 00:12:39.060 --> 00:12:40.670 align:start position:0% only trying to avoid these failures but to<00:12:39.180> be<00:12:39.300> able<00:12:39.360> to<00:12:39.480> recover<00:12:39.720> from<00:12:39.959> them 00:12:40.670 --> 00:12:40.680 align:start position:0% to be able to recover from them 00:12:40.680 --> 00:12:42.710 align:start position:0% to be able to recover from them which<00:12:41.160> takes<00:12:41.399> time 00:12:42.710 --> 00:12:42.720 align:start position:0% which takes time 00:12:42.720 --> 00:12:45.050 align:start position:0% which takes time the<00:12:43.139> next<00:12:43.260> is<00:12:43.560> Network<00:12:43.920> resilience<00:12:44.519> and 00:12:45.050 --> 00:12:45.060 align:start position:0% the next is Network resilience and 00:12:45.060 --> 00:12:46.250 align:start position:0% the next is Network resilience and there's<00:12:45.180> really<00:12:45.300> a<00:12:45.480> heterogeneous<00:12:46.079> Network 00:12:46.250 --> 00:12:46.260 align:start position:0% there's really a heterogeneous Network 00:12:46.260 --> 00:12:48.410 align:start position:0% there's really a heterogeneous Network and<00:12:46.620> that<00:12:46.800> provides<00:12:47.220> resilience<00:12:47.700> in<00:12:47.940> so<00:12:48.240> many 00:12:48.410 --> 00:12:48.420 align:start position:0% and that provides resilience in so many 00:12:48.420 --> 00:12:49.870 align:start position:0% and that provides resilience in so many ways<00:12:48.660> so<00:12:49.019> we<00:12:49.200> have<00:12:49.320> multi-client 00:12:49.870 --> 00:12:49.880 align:start position:0% ways so we have multi-client 00:12:49.880 --> 00:12:51.889 align:start position:0% ways so we have multi-client multi-layered<00:12:50.880> Justin<00:12:51.300> actually<00:12:51.660> was 00:12:51.889 --> 00:12:51.899 align:start position:0% multi-layered Justin actually was 00:12:51.899 --> 00:12:53.210 align:start position:0% multi-layered Justin actually was pointing<00:12:52.200> out<00:12:52.320> there's<00:12:52.500> another<00:12:52.680> layer<00:12:53.040> we 00:12:53.210 --> 00:12:53.220 align:start position:0% pointing out there's another layer we 00:12:53.220 --> 00:12:54.350 align:start position:0% pointing out there's another layer we think<00:12:53.399> about<00:12:53.519> the<00:12:53.700> consensus<00:12:54.060> layer<00:12:54.240> the 00:12:54.350 --> 00:12:54.360 align:start position:0% think about the consensus layer the 00:12:54.360 --> 00:12:55.430 align:start position:0% think about the consensus layer the execution<00:12:54.660> layer<00:12:54.959> there's<00:12:55.079> actually<00:12:55.260> this 00:12:55.430 --> 00:12:55.440 align:start position:0% execution layer there's actually this 00:12:55.440 --> 00:12:56.690 align:start position:0% execution layer there's actually this other<00:12:55.620> layer<00:12:55.980> which<00:12:56.279> is<00:12:56.399> kind<00:12:56.519> of<00:12:56.639> the 00:12:56.690 --> 00:12:56.700 align:start position:0% other layer which is kind of the 00:12:56.700 --> 00:12:58.490 align:start position:0% other layer which is kind of the cryptographic<00:12:57.180> layer<00:12:57.420> we<00:12:57.600> rely<00:12:57.899> on<00:12:58.079> a 00:12:58.490 --> 00:12:58.500 align:start position:0% cryptographic layer we rely on a 00:12:58.500 --> 00:13:01.610 align:start position:0% cryptographic layer we rely on a multitude<00:12:58.920> of<00:12:59.160> of<00:12:59.700> black<00:13:00.060> boxed<00:13:00.600> crypto<00:13:01.200> tools 00:13:01.610 --> 00:13:01.620 align:start position:0% multitude of of black boxed crypto tools 00:13:01.620 --> 00:13:04.150 align:start position:0% multitude of of black boxed crypto tools which<00:13:02.040> allow<00:13:02.459> for<00:13:02.700> expertise<00:13:03.240> and<00:13:03.540> and 00:13:04.150 --> 00:13:04.160 align:start position:0% which allow for expertise and and 00:13:04.160 --> 00:13:06.470 align:start position:0% which allow for expertise and and separation<00:13:05.160> of<00:13:05.339> layers<00:13:05.639> here<00:13:05.820> we<00:13:06.300> have 00:13:06.470 --> 00:13:06.480 align:start position:0% separation of layers here we have 00:13:06.480 --> 00:13:07.970 align:start position:0% separation of layers here we have hobbyist<00:13:06.839> stakers<00:13:07.139> we<00:13:07.320> have<00:13:07.440> home<00:13:07.560> nodes<00:13:07.860> and 00:13:07.970 --> 00:13:07.980 align:start position:0% hobbyist stakers we have home nodes and 00:13:07.980 --> 00:13:09.949 align:start position:0% hobbyist stakers we have home nodes and Regional<00:13:08.339> diversity<00:13:08.700> every<00:13:09.420> single<00:13:09.660> one<00:13:09.839> of 00:13:09.949 --> 00:13:09.959 align:start position:0% Regional diversity every single one of 00:13:09.959 --> 00:13:13.269 align:start position:0% Regional diversity every single one of these<00:13:10.200> things<00:13:10.399> makes<00:13:11.399> it<00:13:11.579> harder<00:13:11.940> like<00:13:12.600> every 00:13:13.269 --> 00:13:13.279 align:start position:0% these things makes it harder like every 00:13:13.279 --> 00:13:16.190 align:start position:0% these things makes it harder like every arguably<00:13:14.279> multi-layer<00:13:14.880> doesn't<00:13:15.060> but<00:13:15.600> the 00:13:16.190 --> 00:13:16.200 align:start position:0% arguably multi-layer doesn't but the 00:13:16.200 --> 00:13:17.690 align:start position:0% arguably multi-layer doesn't but the fact<00:13:16.380> that<00:13:16.500> we<00:13:16.680> have<00:13:16.860> like<00:13:17.040> nine<00:13:17.339> clients 00:13:17.690 --> 00:13:17.700 align:start position:0% fact that we have like nine clients 00:13:17.700 --> 00:13:19.370 align:start position:0% fact that we have like nine clients working<00:13:17.880> on<00:13:18.120> this<00:13:18.240> thing<00:13:18.360> does<00:13:19.019> not<00:13:19.200> make 00:13:19.370 --> 00:13:19.380 align:start position:0% working on this thing does not make 00:13:19.380 --> 00:13:21.230 align:start position:0% working on this thing does not make shipping<00:13:19.800> easier<00:13:20.160> but<00:13:20.519> it<00:13:20.639> makes<00:13:20.760> the<00:13:21.060> network 00:13:21.230 --> 00:13:21.240 align:start position:0% shipping easier but it makes the network 00:13:21.240 --> 00:13:23.810 align:start position:0% shipping easier but it makes the network more<00:13:21.779> resilient<00:13:22.200> under<00:13:22.500> failure<00:13:22.920> modes<00:13:23.279> it 00:13:23.810 --> 00:13:23.820 align:start position:0% more resilient under failure modes it 00:13:23.820 --> 00:13:25.910 align:start position:0% more resilient under failure modes it makes<00:13:24.000> users<00:13:24.720> more<00:13:24.959> resilient<00:13:25.380> in<00:13:25.620> that<00:13:25.740> they 00:13:25.910 --> 00:13:25.920 align:start position:0% makes users more resilient in that they 00:13:25.920 --> 00:13:27.590 align:start position:0% makes users more resilient in that they can<00:13:26.100> pick<00:13:26.579> different<00:13:26.820> things<00:13:27.120> in<00:13:27.360> the<00:13:27.480> case 00:13:27.590 --> 00:13:27.600 align:start position:0% can pick different things in the case 00:13:27.600 --> 00:13:30.129 align:start position:0% can pick different things in the case that<00:13:27.720> something<00:13:27.959> fails<00:13:28.380> hobbyist<00:13:29.160> stakers 00:13:30.129 --> 00:13:30.139 align:start position:0% that something fails hobbyist stakers 00:13:30.139 --> 00:13:32.449 align:start position:0% that something fails hobbyist stakers allow<00:13:31.139> for<00:13:31.320> Like<00:13:31.680> A<00:13:31.980> diversity<00:13:32.279> or 00:13:32.449 --> 00:13:32.459 align:start position:0% allow for Like A diversity or 00:13:32.459 --> 00:13:34.370 align:start position:0% allow for Like A diversity or participation<00:13:32.880> they<00:13:33.300> allow<00:13:33.600> for<00:13:33.779> fail<00:13:34.079> like 00:13:34.370 --> 00:13:34.380 align:start position:0% participation they allow for fail like 00:13:34.380 --> 00:13:35.810 align:start position:0% participation they allow for fail like backups<00:13:34.800> in<00:13:34.920> the<00:13:35.040> event<00:13:35.160> of<00:13:35.339> failure<00:13:35.579> modes 00:13:35.810 --> 00:13:35.820 align:start position:0% backups in the event of failure modes 00:13:35.820 --> 00:13:37.910 align:start position:0% backups in the event of failure modes and<00:13:35.880> I'll<00:13:36.000> talk<00:13:36.120> about<00:13:36.300> that<00:13:36.540> home<00:13:37.500> modes 00:13:37.910 --> 00:13:37.920 align:start position:0% and I'll talk about that home modes 00:13:37.920 --> 00:13:40.370 align:start position:0% and I'll talk about that home modes Regional<00:13:38.220> diversity<00:13:38.639> similar<00:13:39.120> things 00:13:40.370 --> 00:13:40.380 align:start position:0% Regional diversity similar things 00:13:40.380 --> 00:13:42.410 align:start position:0% Regional diversity similar things I<00:13:40.800> think<00:13:40.980> one<00:13:41.220> thing<00:13:41.339> that<00:13:41.519> we<00:13:41.700> don't<00:13:41.880> think 00:13:42.410 --> 00:13:42.420 align:start position:0% I think one thing that we don't think 00:13:42.420 --> 00:13:43.670 align:start position:0% I think one thing that we don't think about<00:13:42.540> when<00:13:42.899> we<00:13:43.019> think<00:13:43.139> about<00:13:43.260> like<00:13:43.560> this 00:13:43.670 --> 00:13:43.680 align:start position:0% about when we think about like this 00:13:43.680 --> 00:13:45.350 align:start position:0% about when we think about like this heterogeneous<00:13:44.339> Network<00:13:44.519> and<00:13:44.760> how<00:13:44.940> it<00:13:45.060> helps 00:13:45.350 --> 00:13:45.360 align:start position:0% heterogeneous Network and how it helps 00:13:45.360 --> 00:13:47.990 align:start position:0% heterogeneous Network and how it helps us<00:13:45.480> we<00:13:46.139> really<00:13:46.320> obsess<00:13:46.680> over<00:13:46.860> like<00:13:47.220> we<00:13:47.820> want 00:13:47.990 --> 00:13:48.000 align:start position:0% us we really obsess over like we want 00:13:48.000 --> 00:13:50.509 align:start position:0% us we really obsess over like we want perfect<00:13:48.300> distributions<00:13:48.899> we<00:13:49.200> want<00:13:49.320> like<00:13:49.620> 20<00:13:50.040> of 00:13:50.509 --> 00:13:50.519 align:start position:0% perfect distributions we want like 20 of 00:13:50.519 --> 00:13:52.670 align:start position:0% perfect distributions we want like 20 of each<00:13:50.639> client<00:13:51.000> thus<00:13:51.600> if<00:13:51.779> one<00:13:52.019> goes<00:13:52.320> down<00:13:52.440> then 00:13:52.670 --> 00:13:52.680 align:start position:0% each client thus if one goes down then 00:13:52.680 --> 00:13:55.190 align:start position:0% each client thus if one goes down then like<00:13:52.860> we're<00:13:53.040> 100<00:13:53.220> good<00:13:53.700> that's<00:13:53.940> the<00:13:54.180> ideal<00:13:54.540> and 00:13:55.190 --> 00:13:55.200 align:start position:0% like we're 100 good that's the ideal and 00:13:55.200 --> 00:13:57.050 align:start position:0% like we're 100 good that's the ideal and that<00:13:55.320> actually<00:13:55.560> optimizes<00:13:56.279> for<00:13:56.459> kind<00:13:56.700> of<00:13:56.880> the 00:13:57.050 --> 00:13:57.060 align:start position:0% that actually optimizes for kind of the 00:13:57.060 --> 00:13:59.329 align:start position:0% that actually optimizes for kind of the continuity<00:13:57.720> of<00:13:57.959> the<00:13:58.079> network<00:13:58.200> like<00:13:58.920> the<00:13:59.220> the 00:13:59.329 --> 00:13:59.339 align:start position:0% continuity of the network like the the 00:13:59.339 --> 00:14:01.550 align:start position:0% continuity of the network like the the network<00:13:59.639> can<00:13:59.880> be<00:14:00.060> continuously<00:14:00.600> resilient<00:14:01.200> in 00:14:01.550 --> 00:14:01.560 align:start position:0% network can be continuously resilient in 00:14:01.560 --> 00:14:02.629 align:start position:0% network can be continuously resilient in the<00:14:01.680> event<00:14:01.800> that<00:14:01.980> you<00:14:02.100> get<00:14:02.220> these<00:14:02.459> perfect 00:14:02.629 --> 00:14:02.639 align:start position:0% the event that you get these perfect 00:14:02.639 --> 00:14:05.449 align:start position:0% the event that you get these perfect spreads<00:14:03.240> so<00:14:03.779> for<00:14:04.380> example<00:14:04.620> you<00:14:05.160> know<00:14:05.220> if<00:14:05.279> we 00:14:05.449 --> 00:14:05.459 align:start position:0% spreads so for example you know if we 00:14:05.459 --> 00:14:07.550 align:start position:0% spreads so for example you know if we have<00:14:05.579> five<00:14:05.820> clients<00:14:06.360> uh<00:14:06.959> they're<00:14:07.200> perfectly 00:14:07.550 --> 00:14:07.560 align:start position:0% have five clients uh they're perfectly 00:14:07.560 --> 00:14:09.410 align:start position:0% have five clients uh they're perfectly distributed<00:14:07.980> across<00:14:08.399> the<00:14:08.519> network<00:14:08.639> if<00:14:09.240> one 00:14:09.410 --> 00:14:09.420 align:start position:0% distributed across the network if one 00:14:09.420 --> 00:14:12.650 align:start position:0% distributed across the network if one goes<00:14:09.779> down<00:14:09.959> you<00:14:10.920> might<00:14:11.040> get<00:14:11.160> a<00:14:11.339> few<00:14:11.519> uh<00:14:12.300> fewer 00:14:12.650 --> 00:14:12.660 align:start position:0% goes down you might get a few uh fewer 00:14:12.660 --> 00:14:14.150 align:start position:0% goes down you might get a few uh fewer block<00:14:12.839> proposals<00:14:13.380> until<00:14:13.560> it<00:14:13.740> comes<00:14:13.920> up<00:14:13.980> or 00:14:14.150 --> 00:14:14.160 align:start position:0% block proposals until it comes up or 00:14:14.160 --> 00:14:15.889 align:start position:0% block proposals until it comes up or people<00:14:14.339> switch<00:14:14.519> their<00:14:14.820> nodes<00:14:15.060> but<00:14:15.600> you<00:14:15.720> get 00:14:15.889 --> 00:14:15.899 align:start position:0% people switch their nodes but you get 00:14:15.899 --> 00:14:17.329 align:start position:0% people switch their nodes but you get finality<00:14:16.380> you<00:14:16.620> get<00:14:16.740> like<00:14:16.920> a<00:14:17.040> really<00:14:17.160> nice 00:14:17.329 --> 00:14:17.339 align:start position:0% finality you get like a really nice 00:14:17.339 --> 00:14:19.610 align:start position:0% finality you get like a really nice quality<00:14:17.700> of<00:14:17.880> service<00:14:18.000> it's<00:14:18.300> great 00:14:19.610 --> 00:14:19.620 align:start position:0% quality of service it's great 00:14:19.620 --> 00:14:22.009 align:start position:0% quality of service it's great we<00:14:20.279> should<00:14:20.579> move<00:14:21.420> towards<00:14:21.720> that<00:14:21.839> direction 00:14:22.009 --> 00:14:22.019 align:start position:0% we should move towards that direction 00:14:22.019 --> 00:14:24.290 align:start position:0% we should move towards that direction there's<00:14:22.440> tons<00:14:22.680> of<00:14:22.860> reasons<00:14:23.220> as<00:14:23.760> a<00:14:23.940> whole<00:14:24.060> and 00:14:24.290 --> 00:14:24.300 align:start position:0% there's tons of reasons as a whole and 00:14:24.300 --> 00:14:25.850 align:start position:0% there's tons of reasons as a whole and as<00:14:24.480> individuals<00:14:24.959> you<00:14:25.260> know<00:14:25.320> we<00:14:25.440> should<00:14:25.560> try<00:14:25.740> to 00:14:25.850 --> 00:14:25.860 align:start position:0% as individuals you know we should try to 00:14:25.860 --> 00:14:27.050 align:start position:0% as individuals you know we should try to optimize<00:14:26.220> for<00:14:26.399> this 00:14:27.050 --> 00:14:27.060 align:start position:0% optimize for this 00:14:27.060 --> 00:14:30.170 align:start position:0% optimize for this but<00:14:27.860> they<00:14:28.860> all<00:14:28.980> it<00:14:29.160> also<00:14:29.399> helps<00:14:29.639> us<00:14:29.760> even<00:14:29.940> in 00:14:30.170 --> 00:14:30.180 align:start position:0% but they all it also helps us even in 00:14:30.180 --> 00:14:31.790 align:start position:0% but they all it also helps us even in imperfect<00:14:30.600> distributions<00:14:31.019> and<00:14:31.500> these<00:14:31.680> are 00:14:31.790 --> 00:14:31.800 align:start position:0% imperfect distributions and these are 00:14:31.800 --> 00:14:34.069 align:start position:0% imperfect distributions and these are more<00:14:31.860> in<00:14:32.040> the<00:14:32.160> tailor<00:14:32.459> scenarios<00:14:32.940> so<00:14:33.300> if<00:14:33.899> that 00:14:34.069 --> 00:14:34.079 align:start position:0% more in the tailor scenarios so if that 00:14:34.079 --> 00:14:36.290 align:start position:0% more in the tailor scenarios so if that big<00:14:34.320> if<00:14:34.620> if<00:14:34.800> client<00:14:35.279> diversity<00:14:35.760> looks<00:14:36.120> like 00:14:36.290 --> 00:14:36.300 align:start position:0% big if if client diversity looks like 00:14:36.300 --> 00:14:38.389 align:start position:0% big if if client diversity looks like that<00:14:36.480> on<00:14:36.660> the<00:14:36.779> network<00:14:36.920> that<00:14:37.920> large<00:14:38.100> block 00:14:38.389 --> 00:14:38.399 align:start position:0% that on the network that large block 00:14:38.399 --> 00:14:41.210 align:start position:0% that on the network that large block goes<00:14:39.000> offline<00:14:39.360> and<00:14:39.899> it's<00:14:40.019> chaos<00:14:40.440> right<00:14:40.980> like 00:14:41.210 --> 00:14:41.220 align:start position:0% goes offline and it's chaos right like 00:14:41.220 --> 00:14:42.889 align:start position:0% goes offline and it's chaos right like we're<00:14:41.399> not<00:14:41.579> finalizing<00:14:42.180> we're<00:14:42.540> getting<00:14:42.720> maybe 00:14:42.889 --> 00:14:42.899 align:start position:0% we're not finalizing we're getting maybe 00:14:42.899 --> 00:14:45.350 align:start position:0% we're not finalizing we're getting maybe 50<00:14:43.139> of<00:14:43.560> the<00:14:43.620> blocks<00:14:43.920> that<00:14:44.100> we're<00:14:44.220> expecting 00:14:45.350 --> 00:14:45.360 align:start position:0% 50 of the blocks that we're expecting 00:14:45.360 --> 00:14:48.170 align:start position:0% 50 of the blocks that we're expecting um<00:14:45.480> and<00:14:45.660> and<00:14:45.839> shit's<00:14:46.260> going<00:14:46.440> down<00:14:46.620> but 00:14:48.170 --> 00:14:48.180 align:start position:0% um and and shit's going down but 00:14:48.180 --> 00:14:49.970 align:start position:0% um and and shit's going down but the<00:14:48.600> network<00:14:48.720> continues 00:14:49.970 --> 00:14:49.980 align:start position:0% the network continues 00:14:49.980 --> 00:14:52.069 align:start position:0% the network continues blocks<00:14:50.699> are<00:14:50.760> built<00:14:51.120> transactions<00:14:51.959> are 00:14:52.069 --> 00:14:52.079 align:start position:0% blocks are built transactions are 00:14:52.079 --> 00:14:55.310 align:start position:0% blocks are built transactions are processed<00:14:52.620> and<00:14:53.459> users<00:14:54.300> have<00:14:54.480> options<00:14:54.779> so<00:14:55.199> in 00:14:55.310 --> 00:14:55.320 align:start position:0% processed and users have options so in 00:14:55.320 --> 00:14:57.470 align:start position:0% processed and users have options so in that<00:14:55.500> event<00:14:55.680> users<00:14:56.639> over<00:14:56.880> the<00:14:57.060> course<00:14:57.180> of<00:14:57.360> a 00:14:57.470 --> 00:14:57.480 align:start position:0% that event users over the course of a 00:14:57.480 --> 00:14:59.930 align:start position:0% that event users over the course of a day<00:14:57.600> can<00:14:57.839> dynamically<00:14:58.380> you<00:14:58.740> know<00:14:58.800> either<00:14:59.100> that 00:14:59.930 --> 00:14:59.940 align:start position:0% day can dynamically you know either that 00:14:59.940 --> 00:15:01.550 align:start position:0% day can dynamically you know either that big<00:15:00.060> block<00:15:00.240> gets<00:15:00.660> fixed<00:15:00.839> the<00:15:01.019> network<00:15:01.139> stays 00:15:01.550 --> 00:15:01.560 align:start position:0% big block gets fixed the network stays 00:15:01.560 --> 00:15:04.129 align:start position:0% big block gets fixed the network stays online<00:15:01.680> or<00:15:02.519> that<00:15:02.820> big<00:15:02.940> block<00:15:03.120> has<00:15:03.360> issues<00:15:03.839> and 00:15:04.129 --> 00:15:04.139 align:start position:0% online or that big block has issues and 00:15:04.139 --> 00:15:06.050 align:start position:0% online or that big block has issues and users<00:15:04.440> have<00:15:04.620> options<00:15:04.920> to<00:15:05.160> switch<00:15:05.339> through<00:15:05.579> and 00:15:06.050 --> 00:15:06.060 align:start position:0% users have options to switch through and 00:15:06.060 --> 00:15:07.490 align:start position:0% users have options to switch through and they<00:15:06.240> can<00:15:06.360> recover<00:15:06.660> and<00:15:07.079> make<00:15:07.199> sure<00:15:07.320> the 00:15:07.490 --> 00:15:07.500 align:start position:0% they can recover and make sure the 00:15:07.500 --> 00:15:10.069 align:start position:0% they can recover and make sure the network<00:15:07.620> continues<00:15:08.100> in<00:15:08.519> the<00:15:08.699> event<00:15:08.820> that<00:15:09.300> it's 00:15:10.069 --> 00:15:10.079 align:start position:0% network continues in the event that it's 00:15:10.079 --> 00:15:12.470 align:start position:0% network continues in the event that it's just<00:15:10.320> one<00:15:10.800> block<00:15:11.459> you<00:15:11.880> don't<00:15:12.000> have<00:15:12.180> all<00:15:12.300> of 00:15:12.470 --> 00:15:12.480 align:start position:0% just one block you don't have all of 00:15:12.480 --> 00:15:14.689 align:start position:0% just one block you don't have all of that<00:15:12.660> that<00:15:13.019> you<00:15:13.500> have<00:15:13.920> zero<00:15:14.339> ability<00:15:14.519> to 00:15:14.689 --> 00:15:14.699 align:start position:0% that that you have zero ability to 00:15:14.699 --> 00:15:15.949 align:start position:0% that that you have zero ability to recover 00:15:15.949 --> 00:15:15.959 align:start position:0% recover 00:15:15.959 --> 00:15:17.210 align:start position:0% recover until 00:15:17.210 --> 00:15:17.220 align:start position:0% until 00:15:17.220 --> 00:15:19.730 align:start position:0% until they<00:15:17.699> turn<00:15:17.820> that<00:15:18.000> thing<00:15:18.120> back<00:15:18.300> on<00:15:18.540> so<00:15:19.320> this 00:15:19.730 --> 00:15:19.740 align:start position:0% they turn that thing back on so this 00:15:19.740 --> 00:15:21.230 align:start position:0% they turn that thing back on so this goes<00:15:20.040> this<00:15:20.339> goes<00:15:20.639> for<00:15:20.760> some<00:15:20.940> of<00:15:21.000> the<00:15:21.120> other 00:15:21.230 --> 00:15:21.240 align:start position:0% goes this goes for some of the other 00:15:21.240 --> 00:15:23.930 align:start position:0% goes this goes for some of the other things<00:15:21.420> here<00:15:21.660> I<00:15:22.260> think<00:15:22.440> people<00:15:23.220> sometimes<00:15:23.699> say 00:15:23.930 --> 00:15:23.940 align:start position:0% things here I think people sometimes say 00:15:23.940 --> 00:15:26.090 align:start position:0% things here I think people sometimes say why<00:15:24.300> are<00:15:24.420> we<00:15:24.540> optimizing<00:15:25.019> for<00:15:25.139> home<00:15:25.500> nodes<00:15:25.800> why 00:15:26.090 --> 00:15:26.100 align:start position:0% why are we optimizing for home nodes why 00:15:26.100 --> 00:15:28.069 align:start position:0% why are we optimizing for home nodes why are<00:15:26.220> we<00:15:26.339> optimizing<00:15:26.820> for<00:15:27.000> homesteakers<00:15:27.600> you 00:15:28.069 --> 00:15:28.079 align:start position:0% are we optimizing for homesteakers you 00:15:28.079 --> 00:15:29.930 align:start position:0% are we optimizing for homesteakers you know<00:15:28.139> like<00:15:28.380> if<00:15:29.100> you<00:15:29.220> look<00:15:29.339> at<00:15:29.519> staking 00:15:29.930 --> 00:15:29.940 align:start position:0% know like if you look at staking 00:15:29.940 --> 00:15:31.970 align:start position:0% know like if you look at staking distribution<00:15:30.420> you<00:15:30.660> know<00:15:30.779> homesteakers<00:15:31.680> are<00:15:31.860> a 00:15:31.970 --> 00:15:31.980 align:start position:0% distribution you know homesteakers are a 00:15:31.980 --> 00:15:33.949 align:start position:0% distribution you know homesteakers are a third<00:15:32.100> or<00:15:32.399> less<00:15:32.579> like<00:15:33.060> it's<00:15:33.180> clearly<00:15:33.779> not 00:15:33.949 --> 00:15:33.959 align:start position:0% third or less like it's clearly not 00:15:33.959 --> 00:15:37.310 align:start position:0% third or less like it's clearly not working<00:15:34.199> but<00:15:34.800> it's<00:15:35.399> it<00:15:36.000> does<00:15:36.240> not<00:15:36.420> it's<00:15:37.139> not 00:15:37.310 --> 00:15:37.320 align:start position:0% working but it's it does not it's not 00:15:37.320 --> 00:15:38.689 align:start position:0% working but it's it does not it's not giving<00:15:37.440> us<00:15:37.740> that<00:15:38.040> kind<00:15:38.339> of<00:15:38.459> perfect 00:15:38.689 --> 00:15:38.699 align:start position:0% giving us that kind of perfect 00:15:38.699 --> 00:15:40.430 align:start position:0% giving us that kind of perfect distribution<00:15:39.300> that<00:15:39.660> might<00:15:39.779> help<00:15:40.019> in<00:15:40.260> in 00:15:40.430 --> 00:15:40.440 align:start position:0% distribution that might help in in 00:15:40.440 --> 00:15:42.530 align:start position:0% distribution that might help in in continuity<00:15:41.040> in<00:15:41.220> the<00:15:41.339> event<00:15:41.459> of<00:15:41.760> intermittent 00:15:42.530 --> 00:15:42.540 align:start position:0% continuity in the event of intermittent 00:15:42.540 --> 00:15:45.170 align:start position:0% continuity in the event of intermittent failures<00:15:42.899> but<00:15:43.560> it<00:15:43.740> does<00:15:44.040> help<00:15:44.399> with<00:15:44.699> recovery 00:15:45.170 --> 00:15:45.180 align:start position:0% failures but it does help with recovery 00:15:45.180 --> 00:15:47.449 align:start position:0% failures but it does help with recovery it's<00:15:45.540> critical<00:15:45.959> for<00:15:46.500> Recovery<00:15:46.860> it's<00:15:46.980> critical 00:15:47.449 --> 00:15:47.459 align:start position:0% it's critical for Recovery it's critical 00:15:47.459 --> 00:15:49.370 align:start position:0% it's critical for Recovery it's critical for<00:15:47.880> these<00:15:48.060> failure<00:15:48.360> modes<00:15:48.660> so<00:15:48.899> in<00:15:49.079> the<00:15:49.199> event 00:15:49.370 --> 00:15:49.380 align:start position:0% for these failure modes so in the event 00:15:49.380 --> 00:15:52.449 align:start position:0% for these failure modes so in the event that<00:15:50.040> some<00:15:50.399> of<00:15:50.579> your<00:15:50.699> mega<00:15:51.240> pool<00:15:51.480> and<00:15:51.839> the<00:15:52.019> mega 00:15:52.449 --> 00:15:52.459 align:start position:0% that some of your mega pool and the mega 00:15:52.459 --> 00:15:55.189 align:start position:0% that some of your mega pool and the mega cartel<00:15:53.459> of<00:15:53.639> pools<00:15:54.060> they<00:15:54.600> finalize<00:15:55.019> something 00:15:55.189 --> 00:15:55.199 align:start position:0% cartel of pools they finalize something 00:15:55.199 --> 00:15:57.710 align:start position:0% cartel of pools they finalize something invalid<00:15:55.800> they<00:15:55.980> try<00:15:56.160> to<00:15:56.279> take<00:15:56.459> the<00:15:56.639> chain<00:15:56.760> over 00:15:57.710 --> 00:15:57.720 align:start position:0% invalid they try to take the chain over 00:15:57.720 --> 00:16:00.889 align:start position:0% invalid they try to take the chain over then<00:15:58.139> you<00:15:58.320> have<00:15:58.560> a<00:15:59.339> resilient<00:15:59.820> the<00:16:00.360> ability<00:16:00.600> to 00:16:00.889 --> 00:16:00.899 align:start position:0% then you have a resilient the ability to 00:16:00.899 --> 00:16:02.990 align:start position:0% then you have a resilient the ability to continue<00:16:01.019> like<00:16:01.680> that 00:16:02.990 --> 00:16:03.000 align:start position:0% continue like that 00:16:03.000 --> 00:16:05.269 align:start position:0% continue like that that<00:16:03.600> big<00:16:03.779> block<00:16:03.959> finalizes<00:16:04.740> something<00:16:04.980> crazy 00:16:05.269 --> 00:16:05.279 align:start position:0% that big block finalizes something crazy 00:16:05.279 --> 00:16:08.329 align:start position:0% that big block finalizes something crazy and<00:16:05.820> that<00:16:06.480> small<00:16:06.899> chunk<00:16:07.260> of<00:16:07.500> hobbies 00:16:08.329 --> 00:16:08.339 align:start position:0% and that small chunk of hobbies 00:16:08.339 --> 00:16:09.710 align:start position:0% and that small chunk of hobbies validators<00:16:08.820> become<00:16:09.120> the<00:16:09.240> backbone<00:16:09.600> of 00:16:09.710 --> 00:16:09.720 align:start position:0% validators become the backbone of 00:16:09.720 --> 00:16:11.329 align:start position:0% validators become the backbone of ethereum<00:16:10.079> and<00:16:10.260> continue<00:16:10.440> forward<00:16:10.740> and<00:16:11.220> they 00:16:11.329 --> 00:16:11.339 align:start position:0% ethereum and continue forward and they 00:16:11.339 --> 00:16:12.290 align:start position:0% ethereum and continue forward and they don't<00:16:11.519> care 00:16:12.290 --> 00:16:12.300 align:start position:0% don't care 00:16:12.300 --> 00:16:14.210 align:start position:0% don't care ethereum<00:16:13.019> doesn't<00:16:13.260> care<00:16:13.440> you<00:16:13.860> know<00:16:13.920> and<00:16:14.040> the 00:16:14.210 --> 00:16:14.220 align:start position:0% ethereum doesn't care you know and the 00:16:14.220 --> 00:16:16.670 align:start position:0% ethereum doesn't care you know and the ability<00:16:14.519> like<00:16:15.180> if<00:16:15.360> that<00:16:15.600> was<00:16:15.779> just<00:16:16.079> three 00:16:16.670 --> 00:16:16.680 align:start position:0% ability like if that was just three 00:16:16.680 --> 00:16:19.129 align:start position:0% ability like if that was just three large<00:16:16.980> pools<00:16:17.459> and<00:16:17.880> they<00:16:18.060> their<00:16:18.360> cartel<00:16:18.839> like 00:16:19.129 --> 00:16:19.139 align:start position:0% large pools and they their cartel like 00:16:19.139 --> 00:16:21.710 align:start position:0% large pools and they their cartel like it's<00:16:19.440> so<00:16:19.680> much<00:16:19.800> more<00:16:20.040> difficult<00:16:20.339> to<00:16:20.639> recover 00:16:21.710 --> 00:16:21.720 align:start position:0% it's so much more difficult to recover 00:16:21.720 --> 00:16:25.370 align:start position:0% it's so much more difficult to recover so<00:16:22.260> we<00:16:22.860> do<00:16:22.980> think<00:16:23.100> things<00:16:23.339> are<00:16:23.459> ourselves 00:16:25.370 --> 00:16:25.380 align:start position:0% so we do think things are ourselves 00:16:25.380 --> 00:16:28.490 align:start position:0% so we do think things are ourselves for<00:16:25.680> continuity<00:16:26.339> and<00:16:26.940> Recovery 00:16:28.490 --> 00:16:28.500 align:start position:0% for continuity and Recovery 00:16:28.500 --> 00:16:31.790 align:start position:0% for continuity and Recovery we<00:16:28.860> also<00:16:29.100> have 00:16:31.790 --> 00:16:31.800 align:start position:0% 00:16:31.800 --> 00:16:33.470 align:start position:0% it's<00:16:32.160> kind<00:16:32.339> of<00:16:32.459> like<00:16:32.519> these<00:16:32.820> soft<00:16:33.000> things<00:16:33.300> that 00:16:33.470 --> 00:16:33.480 align:start position:0% it's kind of like these soft things that 00:16:33.480 --> 00:16:34.910 align:start position:0% it's kind of like these soft things that we're<00:16:33.600> optimizing<00:16:34.139> all<00:16:34.260> the<00:16:34.380> time<00:16:34.500> in<00:16:34.860> the 00:16:34.910 --> 00:16:34.920 align:start position:0% we're optimizing all the time in the 00:16:34.920 --> 00:16:37.370 align:start position:0% we're optimizing all the time in the social<00:16:35.279> air<00:16:35.579> you<00:16:36.180> know<00:16:36.240> multi-client<00:16:36.959> is<00:16:37.139> very 00:16:37.370 --> 00:16:37.380 align:start position:0% social air you know multi-client is very 00:16:37.380 --> 00:16:39.170 align:start position:0% social air you know multi-client is very important<00:16:37.740> for 00:16:39.170 --> 00:16:39.180 align:start position:0% important for 00:16:39.180 --> 00:16:40.910 align:start position:0% important for um<00:16:39.240> for<00:16:39.720> Network<00:16:39.839> resilience<00:16:40.320> but<00:16:40.560> it's<00:16:40.680> also 00:16:40.910 --> 00:16:40.920 align:start position:0% um for Network resilience but it's also 00:16:40.920 --> 00:16:42.470 align:start position:0% um for Network resilience but it's also very<00:16:41.040> important<00:16:41.339> for<00:16:41.639> Like<00:16:41.759> A<00:16:41.880> diversity<00:16:42.300> of 00:16:42.470 --> 00:16:42.480 align:start position:0% very important for Like A diversity of 00:16:42.480 --> 00:16:44.629 align:start position:0% very important for Like A diversity of perspective<00:16:42.899> it's<00:16:43.500> very<00:16:43.980> important<00:16:44.279> for 00:16:44.629 --> 00:16:44.639 align:start position:0% perspective it's very important for 00:16:44.639 --> 00:16:47.769 align:start position:0% perspective it's very important for ensuring<00:16:45.180> that<00:16:45.600> every<00:16:46.199> stone<00:16:46.860> is<00:16:47.160> unturned 00:16:47.769 --> 00:16:47.779 align:start position:0% ensuring that every stone is unturned 00:16:47.779 --> 00:16:50.269 align:start position:0% ensuring that every stone is unturned it's<00:16:48.779> important<00:16:49.199> for<00:16:49.560> kind<00:16:49.800> of<00:16:49.860> the<00:16:49.980> security 00:16:50.269 --> 00:16:50.279 align:start position:0% it's important for kind of the security 00:16:50.279 --> 00:16:53.389 align:start position:0% it's important for kind of the security of<00:16:51.120> this<00:16:51.720> thing<00:16:51.899> and<00:16:52.500> how<00:16:52.800> everything<00:16:53.040> kind<00:16:53.339> of 00:16:53.389 --> 00:16:53.399 align:start position:0% of this thing and how everything kind of 00:16:53.399 --> 00:16:55.189 align:start position:0% of this thing and how everything kind of communicates<00:16:53.820> and<00:16:54.000> comes<00:16:54.240> together 00:16:55.189 --> 00:16:55.199 align:start position:0% communicates and comes together 00:16:55.199 --> 00:16:57.410 align:start position:0% communicates and comes together similarly<00:16:55.920> a<00:16:56.160> diverse<00:16:56.399> staking<00:16:56.699> set<00:16:56.940> brings 00:16:57.410 --> 00:16:57.420 align:start position:0% similarly a diverse staking set brings 00:16:57.420 --> 00:16:59.329 align:start position:0% similarly a diverse staking set brings more<00:16:57.660> people<00:16:57.839> to<00:16:58.019> the<00:16:58.139> table<00:16:58.320> ensures<00:16:59.040> there's 00:16:59.329 --> 00:16:59.339 align:start position:0% more people to the table ensures there's 00:16:59.339 --> 00:17:01.030 align:start position:0% more people to the table ensures there's more<00:16:59.759> diverse 00:17:01.030 --> 00:17:01.040 align:start position:0% more diverse 00:17:01.040 --> 00:17:03.769 align:start position:0% more diverse perspective<00:17:02.040> on<00:17:02.279> the<00:17:02.459> needs<00:17:02.759> of<00:17:03.000> stakers<00:17:03.420> and 00:17:03.769 --> 00:17:03.779 align:start position:0% perspective on the needs of stakers and 00:17:03.779 --> 00:17:06.049 align:start position:0% perspective on the needs of stakers and the<00:17:03.899> desires<00:17:04.260> of<00:17:04.380> the<00:17:04.500> network<00:17:05.059> optimizing 00:17:06.049 --> 00:17:06.059 align:start position:0% the desires of the network optimizing 00:17:06.059 --> 00:17:08.569 align:start position:0% the desires of the network optimizing for<00:17:06.179> the<00:17:06.360> global<00:17:06.660> very<00:17:06.959> similar<00:17:07.319> we<00:17:08.220> have<00:17:08.339> this 00:17:08.569 --> 00:17:08.579 align:start position:0% for the global very similar we have this 00:17:08.579 --> 00:17:11.809 align:start position:0% for the global very similar we have this incredibly<00:17:09.179> like<00:17:09.780> if<00:17:10.679> you<00:17:10.799> talk<00:17:10.860> to<00:17:11.040> academics 00:17:11.809 --> 00:17:11.819 align:start position:0% incredibly like if you talk to academics 00:17:11.819 --> 00:17:13.610 align:start position:0% incredibly like if you talk to academics almost<00:17:12.059> comically<00:17:12.600> open<00:17:12.780> research<00:17:13.319> process 00:17:13.610 --> 00:17:13.620 align:start position:0% almost comically open research process 00:17:13.620 --> 00:17:16.130 align:start position:0% almost comically open research process which<00:17:14.400> brings<00:17:15.000> in<00:17:15.240> a<00:17:15.720> multitude<00:17:16.020> of 00:17:16.130 --> 00:17:16.140 align:start position:0% which brings in a multitude of 00:17:16.140 --> 00:17:18.289 align:start position:0% which brings in a multitude of perspectives<00:17:16.559> and<00:17:16.980> helps<00:17:17.280> Harden<00:17:17.699> the<00:17:18.120> social 00:17:18.289 --> 00:17:18.299 align:start position:0% perspectives and helps Harden the social 00:17:18.299 --> 00:17:20.689 align:start position:0% perspectives and helps Harden the social air<00:17:18.600> and<00:17:18.900> ensure<00:17:19.380> that<00:17:19.679> the<00:17:19.919> the<00:17:19.980> social<00:17:20.339> layer 00:17:20.689 --> 00:17:20.699 align:start position:0% air and ensure that the the social layer 00:17:20.699 --> 00:17:23.329 align:start position:0% air and ensure that the the social layer is<00:17:20.819> diverse<00:17:21.299> similarly<00:17:22.199> open<00:17:22.500> processes<00:17:23.040> Open 00:17:23.329 --> 00:17:23.339 align:start position:0% is diverse similarly open processes Open 00:17:23.339 --> 00:17:26.030 align:start position:0% is diverse similarly open processes Open Door<00:17:23.579> all<00:17:23.819> around<00:17:24.000> and 00:17:26.030 --> 00:17:26.040 align:start position:0% Door all around and 00:17:26.040 --> 00:17:29.330 align:start position:0% Door all around and Albert<00:17:26.640> neon<00:17:27.059> said<00:17:27.360> uh<00:17:27.839> the<00:17:28.620> ethereum<00:17:29.040> is<00:17:29.160> an 00:17:29.330 --> 00:17:29.340 align:start position:0% Albert neon said uh the ethereum is an 00:17:29.340 --> 00:17:30.950 align:start position:0% Albert neon said uh the ethereum is an intellectual<00:17:29.640> gravity<00:17:30.059> well<00:17:30.299> and<00:17:30.660> he<00:17:30.780> said 00:17:30.950 --> 00:17:30.960 align:start position:0% intellectual gravity well and he said 00:17:30.960 --> 00:17:33.710 align:start position:0% intellectual gravity well and he said this<00:17:31.260> five<00:17:31.860> years<00:17:32.100> ago<00:17:32.400> and<00:17:32.940> it<00:17:33.059> was<00:17:33.179> it<00:17:33.360> felt 00:17:33.710 --> 00:17:33.720 align:start position:0% this five years ago and it was it felt 00:17:33.720 --> 00:17:35.470 align:start position:0% this five years ago and it was it felt kind<00:17:33.840> of<00:17:33.960> true<00:17:34.140> but<00:17:34.740> it's<00:17:34.860> just<00:17:35.100> like 00:17:35.470 --> 00:17:35.480 align:start position:0% kind of true but it's just like 00:17:35.480 --> 00:17:37.610 align:start position:0% kind of true but it's just like increasingly<00:17:36.480> true<00:17:36.720> like<00:17:37.080> increasingly 00:17:37.610 --> 00:17:37.620 align:start position:0% increasingly true like increasingly 00:17:37.620 --> 00:17:40.010 align:start position:0% increasingly true like increasingly every<00:17:37.919> time<00:17:38.100> I<00:17:38.340> talk<00:17:38.460> to<00:17:38.640> new<00:17:39.120> academics<00:17:39.660> or 00:17:40.010 --> 00:17:40.020 align:start position:0% every time I talk to new academics or 00:17:40.020 --> 00:17:41.870 align:start position:0% every time I talk to new academics or new<00:17:40.620> people<00:17:40.799> joining<00:17:41.220> it's<00:17:41.340> just<00:17:41.520> like<00:17:41.700> the 00:17:41.870 --> 00:17:41.880 align:start position:0% new people joining it's just like the 00:17:41.880 --> 00:17:44.029 align:start position:0% new people joining it's just like the obsession<00:17:42.299> and<00:17:42.840> the<00:17:42.960> fervor<00:17:43.380> to<00:17:43.559> be<00:17:43.679> involved 00:17:44.029 --> 00:17:44.039 align:start position:0% obsession and the fervor to be involved 00:17:44.039 --> 00:17:47.210 align:start position:0% obsession and the fervor to be involved in<00:17:44.400> this<00:17:44.520> this<00:17:44.760> intellectual<00:17:45.360> pursuit<00:17:45.900> of<00:17:46.740> uh 00:17:47.210 --> 00:17:47.220 align:start position:0% in this this intellectual pursuit of uh 00:17:47.220 --> 00:17:49.490 align:start position:0% in this this intellectual pursuit of uh of<00:17:47.460> ethereum<00:17:47.940> the<00:17:48.240> the<00:17:48.419> ultimate<00:17:48.840> nerd<00:17:49.140> snipe 00:17:49.490 --> 00:17:49.500 align:start position:0% of ethereum the the ultimate nerd snipe 00:17:49.500 --> 00:17:52.549 align:start position:0% of ethereum the the ultimate nerd snipe just<00:17:49.980> increases<00:17:50.520> more<00:17:51.059> and<00:17:51.240> more 00:17:52.549 --> 00:17:52.559 align:start position:0% just increases more and more 00:17:52.559 --> 00:17:53.930 align:start position:0% just increases more and more similarly 00:17:53.930 --> 00:17:53.940 align:start position:0% similarly 00:17:53.940 --> 00:17:56.090 align:start position:0% similarly um 00:17:56.090 --> 00:17:56.100 align:start position:0% 00:17:56.100 --> 00:17:58.610 align:start position:0% Ben<00:17:56.700> calls<00:17:57.120> ethereum<00:17:57.600> a<00:17:57.720> bizarre<00:17:58.140> in<00:17:58.440> the 00:17:58.610 --> 00:17:58.620 align:start position:0% Ben calls ethereum a bizarre in the 00:17:58.620 --> 00:18:00.110 align:start position:0% Ben calls ethereum a bizarre in the sense<00:17:58.740> that<00:17:58.919> you<00:17:59.280> know<00:17:59.340> it's<00:17:59.460> not<00:17:59.640> top<00:17:59.880> down 00:18:00.110 --> 00:18:00.120 align:start position:0% sense that you know it's not top down 00:18:00.120 --> 00:18:01.909 align:start position:0% sense that you know it's not top down controlled<00:18:00.600> it's<00:18:00.720> not<00:18:00.900> top<00:18:01.080> down<00:18:01.320> organized 00:18:01.909 --> 00:18:01.919 align:start position:0% controlled it's not top down organized 00:18:01.919 --> 00:18:04.190 align:start position:0% controlled it's not top down organized it's<00:18:02.039> not<00:18:02.280> it's<00:18:02.760> not<00:18:02.940> like<00:18:03.240> a<00:18:03.480> well-structured 00:18:04.190 --> 00:18:04.200 align:start position:0% it's not it's not like a well-structured 00:18:04.200 --> 00:18:07.610 align:start position:0% it's not it's not like a well-structured thing<00:18:04.380> and<00:18:04.559> there's<00:18:04.799> chaos<00:18:05.220> but<00:18:06.320> time<00:18:07.320> and 00:18:07.610 --> 00:18:07.620 align:start position:0% thing and there's chaos but time and 00:18:07.620 --> 00:18:09.830 align:start position:0% thing and there's chaos but time and time<00:18:07.860> again<00:18:08.100> because<00:18:08.640> of<00:18:08.880> this<00:18:09.059> open<00:18:09.299> nature 00:18:09.830 --> 00:18:09.840 align:start position:0% time again because of this open nature 00:18:09.840 --> 00:18:12.049 align:start position:0% time again because of this open nature of<00:18:10.080> this<00:18:10.260> open<00:18:10.440> market<00:18:10.679> of<00:18:10.980> ideas<00:18:11.220> and 00:18:12.049 --> 00:18:12.059 align:start position:0% of this open market of ideas and 00:18:12.059 --> 00:18:14.090 align:start position:0% of this open market of ideas and intellect<00:18:12.539> and<00:18:12.960> engagement<00:18:13.380> and<00:18:13.740> software 00:18:14.090 --> 00:18:14.100 align:start position:0% intellect and engagement and software 00:18:14.100 --> 00:18:16.070 align:start position:0% intellect and engagement and software development<00:18:14.580> like<00:18:15.120> people<00:18:15.419> just<00:18:15.660> show<00:18:15.900> up 00:18:16.070 --> 00:18:16.080 align:start position:0% development like people just show up 00:18:16.080 --> 00:18:18.169 align:start position:0% development like people just show up they<00:18:16.620> join<00:18:16.919> they<00:18:17.280> join<00:18:17.520> the<00:18:17.640> party<00:18:17.820> at<00:18:18.059> the 00:18:18.169 --> 00:18:18.179 align:start position:0% they join they join the party at the 00:18:18.179 --> 00:18:20.510 align:start position:0% they join they join the party at the right<00:18:18.299> time<00:18:18.480> they<00:18:18.900> help<00:18:19.080> move<00:18:20.039> things<00:18:20.280> forward 00:18:20.510 --> 00:18:20.520 align:start position:0% right time they help move things forward 00:18:20.520 --> 00:18:23.330 align:start position:0% right time they help move things forward and<00:18:20.820> and<00:18:21.179> and<00:18:21.539> get<00:18:22.260> things<00:18:22.380> done<00:18:22.620> and<00:18:23.100> this 00:18:23.330 --> 00:18:23.340 align:start position:0% and and and get things done and this 00:18:23.340 --> 00:18:25.310 align:start position:0% and and and get things done and this this<00:18:23.880> is<00:18:24.120> not 00:18:25.310 --> 00:18:25.320 align:start position:0% this is not 00:18:25.320 --> 00:18:27.770 align:start position:0% this is not that<00:18:25.980> this<00:18:26.220> this<00:18:26.280> open<00:18:26.700> wild<00:18:27.059> structure<00:18:27.600> is 00:18:27.770 --> 00:18:27.780 align:start position:0% that this this open wild structure is 00:18:27.780 --> 00:18:29.390 align:start position:0% that this this open wild structure is like<00:18:28.020> not<00:18:28.200> it's<00:18:28.380> not<00:18:28.559> how<00:18:28.740> you<00:18:28.860> optimize 00:18:29.390 --> 00:18:29.400 align:start position:0% like not it's not how you optimize 00:18:29.400 --> 00:18:31.850 align:start position:0% like not it's not how you optimize things<00:18:29.580> and<00:18:29.820> move<00:18:30.120> as<00:18:30.299> quickly<00:18:30.539> as<00:18:30.660> possible 00:18:31.850 --> 00:18:31.860 align:start position:0% things and move as quickly as possible 00:18:31.860 --> 00:18:35.450 align:start position:0% things and move as quickly as possible but<00:18:32.400> is<00:18:33.000> a<00:18:33.179> way<00:18:33.299> to<00:18:33.419> be<00:18:33.539> resilient 00:18:35.450 --> 00:18:35.460 align:start position:0% but is a way to be resilient 00:18:35.460 --> 00:18:37.370 align:start position:0% but is a way to be resilient ethereum's<00:18:36.179> L1<00:18:36.419> structures<00:18:36.780> tend<00:18:36.960> toward<00:18:37.260> a 00:18:37.370 --> 00:18:37.380 align:start position:0% ethereum's L1 structures tend toward a 00:18:37.380 --> 00:18:39.650 align:start position:0% ethereum's L1 structures tend toward a multitude<00:18:37.799> and<00:18:38.700> thus 00:18:39.650 --> 00:18:39.660 align:start position:0% multitude and thus 00:18:39.660 --> 00:18:41.510 align:start position:0% multitude and thus I<00:18:40.140> would<00:18:40.260> say<00:18:40.380> ethereum's<00:18:40.919> L1<00:18:41.220> structures 00:18:41.510 --> 00:18:41.520 align:start position:0% I would say ethereum's L1 structures 00:18:41.520 --> 00:18:43.549 align:start position:0% I would say ethereum's L1 structures tend<00:18:41.700> to<00:18:41.880> sword<00:18:42.000> ossification<00:18:42.539> like<00:18:43.260> the<00:18:43.440> more 00:18:43.549 --> 00:18:43.559 align:start position:0% tend to sword ossification like the more 00:18:43.559 --> 00:18:45.289 align:start position:0% tend to sword ossification like the more people<00:18:43.740> that<00:18:43.919> are<00:18:44.039> at<00:18:44.160> the<00:18:44.280> table<00:18:44.460> the<00:18:44.940> harder 00:18:45.289 --> 00:18:45.299 align:start position:0% people that are at the table the harder 00:18:45.299 --> 00:18:46.789 align:start position:0% people that are at the table the harder the<00:18:45.419> conversation<00:18:45.780> becomes<00:18:46.260> to<00:18:46.559> change 00:18:46.789 --> 00:18:46.799 align:start position:0% the conversation becomes to change 00:18:46.799 --> 00:18:50.210 align:start position:0% the conversation becomes to change things<00:18:47.100> and 00:18:50.210 --> 00:18:50.220 align:start position:0% 00:18:50.220 --> 00:18:52.250 align:start position:0% I<00:18:50.520> won't<00:18:50.640> get<00:18:50.760> into<00:18:50.880> it<00:18:51.120> too<00:18:51.240> deep<00:18:51.419> but<00:18:51.720> I 00:18:52.250 --> 00:18:52.260 align:start position:0% I won't get into it too deep but I 00:18:52.260 --> 00:18:53.810 align:start position:0% I won't get into it too deep but I personally<00:18:52.620> believe<00:18:52.860> ethereum<00:18:53.340> ossification 00:18:53.810 --> 00:18:53.820 align:start position:0% personally believe ethereum ossification 00:18:53.820 --> 00:18:56.150 align:start position:0% personally believe ethereum ossification in<00:18:54.720> the 00:18:56.150 --> 00:18:56.160 align:start position:0% in the 00:18:56.160 --> 00:18:58.370 align:start position:0% in the not<00:18:56.940> so<00:18:57.179> distant<00:18:57.539> future<00:18:57.720> is<00:18:58.020> incredibly 00:18:58.370 --> 00:18:58.380 align:start position:0% not so distant future is incredibly 00:18:58.380 --> 00:19:00.350 align:start position:0% not so distant future is incredibly important<00:18:58.679> incredibly<00:18:59.100> valuable 00:19:00.350 --> 00:19:00.360 align:start position:0% important incredibly valuable 00:19:00.360 --> 00:19:03.830 align:start position:0% important incredibly valuable um<00:19:00.419> like<00:19:00.720> I<00:19:00.900> said<00:19:01.020> earlier<00:19:01.700> the<00:19:02.700> ability<00:19:03.419> to 00:19:03.830 --> 00:19:03.840 align:start position:0% um like I said earlier the ability to 00:19:03.840 --> 00:19:07.850 align:start position:0% um like I said earlier the ability to modify<00:19:04.400> change<00:19:05.400> or<00:19:06.120> manipulate<00:19:06.720> this<00:19:06.900> this<00:19:07.260> uh 00:19:07.850 --> 00:19:07.860 align:start position:0% modify change or manipulate this this uh 00:19:07.860 --> 00:19:10.130 align:start position:0% modify change or manipulate this this uh machine<00:19:08.460> is<00:19:09.120> very<00:19:09.299> valuable<00:19:09.660> to<00:19:09.840> us<00:19:09.960> because 00:19:10.130 --> 00:19:10.140 align:start position:0% machine is very valuable to us because 00:19:10.140 --> 00:19:12.230 align:start position:0% machine is very valuable to us because quite<00:19:10.500> frankly<00:19:10.740> ethereum<00:19:11.220> is<00:19:11.340> not<00:19:11.520> done<00:19:11.760> you 00:19:12.230 --> 00:19:12.240 align:start position:0% quite frankly ethereum is not done you 00:19:12.240 --> 00:19:13.310 align:start position:0% quite frankly ethereum is not done you know<00:19:12.360> ethereum<00:19:12.720> needs<00:19:12.900> to<00:19:12.960> reach<00:19:13.140> that 00:19:13.310 --> 00:19:13.320 align:start position:0% know ethereum needs to reach that 00:19:13.320 --> 00:19:15.169 align:start position:0% know ethereum needs to reach that functional<00:19:13.620> escape<00:19:13.740> velocity<00:19:14.340> but<00:19:14.820> it<00:19:15.059> will 00:19:15.169 --> 00:19:15.179 align:start position:0% functional escape velocity but it will 00:19:15.179 --> 00:19:16.970 align:start position:0% functional escape velocity but it will be<00:19:15.299> increasingly<00:19:15.720> valuable<00:19:16.080> to<00:19:16.200> others<00:19:16.500> to 00:19:16.970 --> 00:19:16.980 align:start position:0% be increasingly valuable to others to 00:19:16.980 --> 00:19:19.310 align:start position:0% be increasingly valuable to others to also<00:19:17.340> potentially<00:19:17.820> attempt<00:19:18.720> to<00:19:18.840> manipulate 00:19:19.310 --> 00:19:19.320 align:start position:0% also potentially attempt to manipulate 00:19:19.320 --> 00:19:22.850 align:start position:0% also potentially attempt to manipulate for<00:19:19.620> their<00:19:19.799> own<00:19:19.980> their<00:19:20.520> own<00:19:20.640> value<00:19:20.940> so<00:19:21.740> a<00:19:22.740> lot 00:19:22.850 --> 00:19:22.860 align:start position:0% for their own their own value so a lot 00:19:22.860 --> 00:19:24.770 align:start position:0% for their own their own value so a lot of<00:19:23.039> what<00:19:23.520> what's<00:19:23.820> involved<00:19:24.360> in<00:19:24.419> kind<00:19:24.720> of 00:19:24.770 --> 00:19:24.780 align:start position:0% of what what's involved in kind of 00:19:24.780 --> 00:19:27.230 align:start position:0% of what what's involved in kind of bringing<00:19:25.020> more<00:19:25.320> people<00:19:25.440> to<00:19:25.679> table<00:19:25.919> is<00:19:26.640> to<00:19:26.880> make 00:19:27.230 --> 00:19:27.240 align:start position:0% bringing more people to table is to make 00:19:27.240 --> 00:19:28.669 align:start position:0% bringing more people to table is to make sure<00:19:27.360> we<00:19:27.480> have<00:19:27.600> a<00:19:27.780> more<00:19:27.960> resilient<00:19:28.320> protocol 00:19:28.669 --> 00:19:28.679 align:start position:0% sure we have a more resilient protocol 00:19:28.679 --> 00:19:32.090 align:start position:0% sure we have a more resilient protocol while<00:19:29.100> we<00:19:29.280> still<00:19:29.520> can<00:19:29.700> manipulate<00:19:30.240> it<00:19:30.419> but 00:19:32.090 --> 00:19:32.100 align:start position:0% while we still can manipulate it but 00:19:32.100 --> 00:19:33.590 align:start position:0% while we still can manipulate it but to<00:19:32.640> ultimately 00:19:33.590 --> 00:19:33.600 align:start position:0% to ultimately 00:19:33.600 --> 00:19:36.049 align:start position:0% to ultimately tie<00:19:34.260> our<00:19:34.740> feet<00:19:34.919> down<00:19:35.100> with<00:19:35.340> bags<00:19:35.640> and<00:19:35.760> not<00:19:35.880> be 00:19:36.049 --> 00:19:36.059 align:start position:0% tie our feet down with bags and not be 00:19:36.059 --> 00:19:39.169 align:start position:0% tie our feet down with bags and not be able<00:19:36.179> to<00:19:36.299> move 00:19:39.169 --> 00:19:39.179 align:start position:0% 00:19:39.179 --> 00:19:40.970 align:start position:0% where<00:19:39.539> does<00:19:39.660> the<00:19:39.720> EF<00:19:39.960> fit<00:19:40.200> in 00:19:40.970 --> 00:19:40.980 align:start position:0% where does the EF fit in 00:19:40.980 --> 00:19:42.770 align:start position:0% where does the EF fit in I<00:19:41.400> think<00:19:41.520> I<00:19:41.880> will<00:19:42.059> probably<00:19:42.240> talk<00:19:42.419> about<00:19:42.539> this 00:19:42.770 --> 00:19:42.780 align:start position:0% I think I will probably talk about this 00:19:42.780 --> 00:19:44.510 align:start position:0% I think I will probably talk about this a<00:19:42.900> bit<00:19:43.020> I<00:19:43.260> think<00:19:43.380> Josh<00:19:43.860> is<00:19:44.100> going<00:19:44.220> to<00:19:44.280> have<00:19:44.400> some 00:19:44.510 --> 00:19:44.520 align:start position:0% a bit I think Josh is going to have some 00:19:44.520 --> 00:19:45.830 align:start position:0% a bit I think Josh is going to have some interesting<00:19:44.820> perspectives<00:19:45.179> on<00:19:45.419> this<00:19:45.539> as<00:19:45.660> well 00:19:45.830 --> 00:19:45.840 align:start position:0% interesting perspectives on this as well 00:19:45.840 --> 00:19:49.909 align:start position:0% interesting perspectives on this as well but<00:19:46.740> in<00:19:47.160> general<00:19:47.340> you<00:19:48.120> know<00:19:48.179> we're 00:19:49.909 --> 00:19:49.919 align:start position:0% but in general you know we're 00:19:49.919 --> 00:19:51.350 align:start position:0% but in general you know we're we're<00:19:49.980> here<00:19:50.460> to<00:19:50.580> help<00:19:50.700> we're<00:19:51.120> here<00:19:51.240> to 00:19:51.350 --> 00:19:51.360 align:start position:0% we're here to help we're here to 00:19:51.360 --> 00:19:52.430 align:start position:0% we're here to help we're here to coordinate<00:19:51.720> we're<00:19:51.900> here<00:19:52.080> to<00:19:52.200> help<00:19:52.260> connect 00:19:52.430 --> 00:19:52.440 align:start position:0% coordinate we're here to help connect 00:19:52.440 --> 00:19:53.750 align:start position:0% coordinate we're here to help connect the<00:19:52.679> dots 00:19:53.750 --> 00:19:53.760 align:start position:0% the dots 00:19:53.760 --> 00:19:55.310 align:start position:0% the dots um<00:19:53.880> some<00:19:54.120> of<00:19:54.240> some<00:19:54.600> very<00:19:54.720> interesting<00:19:55.080> work 00:19:55.310 --> 00:19:55.320 align:start position:0% um some of some very interesting work 00:19:55.320 --> 00:19:56.870 align:start position:0% um some of some very interesting work and<00:19:55.559> valuable<00:19:55.860> work<00:19:56.039> does<00:19:56.280> come<00:19:56.460> out<00:19:56.640> of<00:19:56.760> the 00:19:56.870 --> 00:19:56.880 align:start position:0% and valuable work does come out of the 00:19:56.880 --> 00:19:59.029 align:start position:0% and valuable work does come out of the ethereum<00:19:57.240> foundation<00:19:57.539> but<00:19:57.780> tons<00:19:58.559> and<00:19:58.799> tons 00:19:59.029 --> 00:19:59.039 align:start position:0% ethereum foundation but tons and tons 00:19:59.039 --> 00:20:01.070 align:start position:0% ethereum foundation but tons and tons more<00:19:59.280> you<00:19:59.520> know<00:19:59.640> this<00:19:59.760> is<00:19:59.940> increasingly<00:20:00.840> just 00:20:01.070 --> 00:20:01.080 align:start position:0% more you know this is increasingly just 00:20:01.080 --> 00:20:03.890 align:start position:0% more you know this is increasingly just a<00:20:01.260> small<00:20:01.559> piece<00:20:01.860> of<00:20:01.980> the<00:20:02.039> puzzle 00:20:03.890 --> 00:20:03.900 align:start position:0% a small piece of the puzzle 00:20:03.900 --> 00:20:06.230 align:start position:0% a small piece of the puzzle this<00:20:04.500> is<00:20:04.620> uh<00:20:04.860> the<00:20:05.160> last<00:20:05.280> the<00:20:05.580> last<00:20:05.820> suggestion 00:20:06.230 --> 00:20:06.240 align:start position:0% this is uh the last the last suggestion 00:20:06.240 --> 00:20:07.850 align:start position:0% this is uh the last the last suggestion reporting<00:20:06.720> Back<00:20:06.840> From<00:20:07.020> The<00:20:07.140> Trenches<00:20:07.440> the<00:20:07.679> art 00:20:07.850 --> 00:20:07.860 align:start position:0% reporting Back From The Trenches the art 00:20:07.860 --> 00:20:09.890 align:start position:0% reporting Back From The Trenches the art of<00:20:08.039> project<00:20:08.160> managing<00:20:08.640> the<00:20:08.820> merge 00:20:09.890 --> 00:20:09.900 align:start position:0% of project managing the merge 00:20:09.900 --> 00:20:11.210 align:start position:0% of project managing the merge um 00:20:11.210 --> 00:20:11.220 align:start position:0% um 00:20:11.220 --> 00:20:13.010 align:start position:0% um one 00:20:13.010 --> 00:20:13.020 align:start position:0% one 00:20:13.020 --> 00:20:15.830 align:start position:0% one Evan<00:20:13.679> I'm<00:20:14.100> not<00:20:14.220> a<00:20:14.400> project<00:20:14.520> manager<00:20:15.179> but<00:20:15.600> you 00:20:15.830 --> 00:20:15.840 align:start position:0% Evan I'm not a project manager but you 00:20:15.840 --> 00:20:16.789 align:start position:0% Evan I'm not a project manager but you know 00:20:16.789 --> 00:20:16.799 align:start position:0% know 00:20:16.799 --> 00:20:20.210 align:start position:0% know um<00:20:17.419> the<00:20:18.419> uh 00:20:20.210 --> 00:20:20.220 align:start position:0% um the uh 00:20:20.220 --> 00:20:22.310 align:start position:0% um the uh I<00:20:20.580> think<00:20:20.640> the<00:20:20.820> the<00:20:21.000> biggest<00:20:21.179> thing<00:20:21.480> is 00:20:22.310 --> 00:20:22.320 align:start position:0% I think the the biggest thing is 00:20:22.320 --> 00:20:24.230 align:start position:0% I think the the biggest thing is if<00:20:22.380> if<00:20:22.679> someone<00:20:23.039> were<00:20:23.280> to<00:20:23.460> attempt<00:20:23.640> to<00:20:23.820> do<00:20:23.940> such 00:20:24.230 --> 00:20:24.240 align:start position:0% if if someone were to attempt to do such 00:20:24.240 --> 00:20:26.870 align:start position:0% if if someone were to attempt to do such a<00:20:24.419> process<00:20:24.720> in<00:20:24.900> the<00:20:25.080> future<00:20:25.200> is<00:20:25.559> uh 00:20:26.870 --> 00:20:26.880 align:start position:0% a process in the future is uh 00:20:26.880 --> 00:20:29.750 align:start position:0% a process in the future is uh know<00:20:27.299> enough<00:20:27.539> to<00:20:28.320> connect<00:20:28.500> the<00:20:28.740> dots 00:20:29.750 --> 00:20:29.760 align:start position:0% know enough to connect the dots 00:20:29.760 --> 00:20:32.330 align:start position:0% know enough to connect the dots contribute<00:20:30.480> enough<00:20:30.660> to<00:20:31.260> uh<00:20:31.620> gain<00:20:31.799> the<00:20:32.039> respect 00:20:32.330 --> 00:20:32.340 align:start position:0% contribute enough to uh gain the respect 00:20:32.340 --> 00:20:35.150 align:start position:0% contribute enough to uh gain the respect needed<00:20:32.760> of<00:20:33.179> the<00:20:33.299> group<00:20:33.620> and<00:20:34.620> and<00:20:34.799> ultimately 00:20:35.150 --> 00:20:35.160 align:start position:0% needed of the group and and ultimately 00:20:35.160 --> 00:20:36.890 align:start position:0% needed of the group and and ultimately get<00:20:35.400> out<00:20:35.520> of<00:20:35.640> the<00:20:35.700> way<00:20:35.820> you<00:20:36.600> know<00:20:36.660> there's 00:20:36.890 --> 00:20:36.900 align:start position:0% get out of the way you know there's 00:20:36.900 --> 00:20:39.409 align:start position:0% get out of the way you know there's there<00:20:37.320> are<00:20:37.559> incredible<00:20:38.340> experts<00:20:38.940> at<00:20:39.240> every 00:20:39.409 --> 00:20:39.419 align:start position:0% there are incredible experts at every 00:20:39.419 --> 00:20:41.810 align:start position:0% there are incredible experts at every layer<00:20:39.780> of<00:20:40.020> everything<00:20:40.200> in<00:20:40.559> the<00:20:40.740> stack<00:20:40.980> and<00:20:41.640> in 00:20:41.810 --> 00:20:41.820 align:start position:0% layer of everything in the stack and in 00:20:41.820 --> 00:20:44.450 align:start position:0% layer of everything in the stack and in creating<00:20:42.179> the<00:20:42.360> room<00:20:42.539> for<00:20:43.320> um 00:20:44.450 --> 00:20:44.460 align:start position:0% creating the room for um 00:20:44.460 --> 00:20:46.730 align:start position:0% creating the room for um for<00:20:44.820> people<00:20:45.000> to<00:20:45.179> do<00:20:45.299> the<00:20:45.480> hard<00:20:45.600> work<00:20:45.780> is<00:20:46.080> is<00:20:46.380> one 00:20:46.730 --> 00:20:46.740 align:start position:0% for people to do the hard work is is one 00:20:46.740 --> 00:20:51.289 align:start position:0% for people to do the hard work is is one of<00:20:46.860> the<00:20:46.919> most<00:20:47.039> important<00:20:47.340> things<00:20:47.460> here 00:20:51.289 --> 00:20:51.299 align:start position:0% 00:20:51.299 --> 00:20:53.450 align:start position:0% I<00:20:51.780> do<00:20:51.840> want<00:20:52.020> to<00:20:52.140> flip<00:20:52.380> this 00:20:53.450 --> 00:20:53.460 align:start position:0% I do want to flip this 00:20:53.460 --> 00:20:55.370 align:start position:0% I do want to flip this l1's<00:20:54.240> thinking<00:20:54.419> about<00:20:54.539> resilience<00:20:55.020> all<00:20:55.200> the 00:20:55.370 --> 00:20:55.380 align:start position:0% l1's thinking about resilience all the 00:20:55.380 --> 00:20:58.789 align:start position:0% l1's thinking about resilience all the time<00:20:55.520> like<00:20:56.520> every<00:20:56.880> piece<00:20:57.360> of<00:20:57.660> the<00:20:58.140> puzzle<00:20:58.500> is 00:20:58.789 --> 00:20:58.799 align:start position:0% time like every piece of the puzzle is 00:20:58.799 --> 00:21:00.650 align:start position:0% time like every piece of the puzzle is all<00:20:58.980> about<00:20:59.160> resilience<00:21:00.059> and<00:21:00.299> all<00:21:00.480> about 00:21:00.650 --> 00:21:00.660 align:start position:0% all about resilience and all about 00:21:00.660 --> 00:21:03.409 align:start position:0% all about resilience and all about ethereum<00:21:01.500> lasting<00:21:01.919> and<00:21:02.160> being<00:21:02.340> a<00:21:02.520> utility<00:21:02.880> for 00:21:03.409 --> 00:21:03.419 align:start position:0% ethereum lasting and being a utility for 00:21:03.419 --> 00:21:05.630 align:start position:0% ethereum lasting and being a utility for the<00:21:03.600> future<00:21:03.780> but<00:21:04.679> I<00:21:04.860> do<00:21:04.919> turn<00:21:05.160> this<00:21:05.340> on<00:21:05.520> the 00:21:05.630 --> 00:21:05.640 align:start position:0% the future but I do turn this on the 00:21:05.640 --> 00:21:06.950 align:start position:0% the future but I do turn this on the application<00:21:06.059> layer<00:21:06.360> I<00:21:06.660> think<00:21:06.780> it's 00:21:06.950 --> 00:21:06.960 align:start position:0% application layer I think it's 00:21:06.960 --> 00:21:09.470 align:start position:0% application layer I think it's definitely<00:21:07.260> time<00:21:07.559> to<00:21:07.860> think<00:21:07.980> long<00:21:08.220> term 00:21:09.470 --> 00:21:09.480 align:start position:0% definitely time to think long term 00:21:09.480 --> 00:21:11.029 align:start position:0% definitely time to think long term um<00:21:09.539> you<00:21:10.320> know 00:21:11.029 --> 00:21:11.039 align:start position:0% um you know 00:21:11.039 --> 00:21:14.570 align:start position:0% um you know I<00:21:11.700> see<00:21:12.000> a<00:21:12.600> lot<00:21:12.660> of<00:21:12.780> unnecessary<00:21:13.320> debt<00:21:13.919> taken 00:21:14.570 --> 00:21:14.580 align:start position:0% I see a lot of unnecessary debt taken 00:21:14.580 --> 00:21:16.250 align:start position:0% I see a lot of unnecessary debt taken out<00:21:14.700> in<00:21:14.880> the<00:21:15.059> application<00:21:15.360> layer<00:21:15.720> you<00:21:16.200> know 00:21:16.250 --> 00:21:16.260 align:start position:0% out in the application layer you know 00:21:16.260 --> 00:21:18.529 align:start position:0% out in the application layer you know whether<00:21:16.740> that<00:21:16.919> be<00:21:17.100> complexity<00:21:17.640> governance 00:21:18.529 --> 00:21:18.539 align:start position:0% whether that be complexity governance 00:21:18.539 --> 00:21:20.210 align:start position:0% whether that be complexity governance where<00:21:18.840> things<00:21:19.140> maybe<00:21:19.380> shouldn't<00:21:19.740> be<00:21:19.799> governed 00:21:20.210 --> 00:21:20.220 align:start position:0% where things maybe shouldn't be governed 00:21:20.220 --> 00:21:22.010 align:start position:0% where things maybe shouldn't be governed upgradability 00:21:22.010 --> 00:21:22.020 align:start position:0% upgradability 00:21:22.020 --> 00:21:24.490 align:start position:0% upgradability bad<00:21:22.620> token<00:21:23.039> distributions 00:21:24.490 --> 00:21:24.500 align:start position:0% bad token distributions 00:21:24.500 --> 00:21:27.470 align:start position:0% bad token distributions these<00:21:25.500> things<00:21:25.679> they're<00:21:26.640> liabilities<00:21:27.120> in<00:21:27.360> the 00:21:27.470 --> 00:21:27.480 align:start position:0% these things they're liabilities in the 00:21:27.480 --> 00:21:29.210 align:start position:0% these things they're liabilities in the sense<00:21:27.660> that 00:21:29.210 --> 00:21:29.220 align:start position:0% sense that 00:21:29.220 --> 00:21:32.750 align:start position:0% sense that they<00:21:30.059> can<00:21:30.299> help<00:21:30.659> you<00:21:30.840> small<00:21:31.740> bits<00:21:32.220> of<00:21:32.280> this<00:21:32.520> it 00:21:32.750 --> 00:21:32.760 align:start position:0% they can help you small bits of this it 00:21:32.760 --> 00:21:34.190 align:start position:0% they can help you small bits of this it can<00:21:32.940> be<00:21:33.059> very<00:21:33.240> important<00:21:33.600> to<00:21:33.720> Applications 00:21:34.190 --> 00:21:34.200 align:start position:0% can be very important to Applications 00:21:34.200 --> 00:21:37.789 align:start position:0% can be very important to Applications but<00:21:34.860> I<00:21:34.980> feel<00:21:35.100> like<00:21:35.340> uh<00:21:36.240> naively<00:21:36.960> if<00:21:37.200> we<00:21:37.260> take<00:21:37.679> a 00:21:37.789 --> 00:21:37.799 align:start position:0% but I feel like uh naively if we take a 00:21:37.799 --> 00:21:39.409 align:start position:0% but I feel like uh naively if we take a look<00:21:37.860> at<00:21:37.980> applications<00:21:38.400> they<00:21:38.760> they<00:21:39.000> take<00:21:39.240> out 00:21:39.409 --> 00:21:39.419 align:start position:0% look at applications they they take out 00:21:39.419 --> 00:21:41.270 align:start position:0% look at applications they they take out quite<00:21:39.720> a<00:21:39.900> bit<00:21:40.020> of<00:21:40.140> this<00:21:40.320> debt<00:21:40.620> for<00:21:40.980> very 00:21:41.270 --> 00:21:41.280 align:start position:0% quite a bit of this debt for very 00:21:41.280 --> 00:21:43.610 align:start position:0% quite a bit of this debt for very unclear<00:21:41.760> return 00:21:43.610 --> 00:21:43.620 align:start position:0% unclear return 00:21:43.620 --> 00:21:45.350 align:start position:0% unclear return I<00:21:44.100> would<00:21:44.159> suggest<00:21:44.460> the<00:21:44.700> application<00:21:45.059> layer 00:21:45.350 --> 00:21:45.360 align:start position:0% I would suggest the application layer 00:21:45.360 --> 00:21:48.049 align:start position:0% I would suggest the application layer more<00:21:45.539> Unix<00:21:45.900> philosophy<00:21:46.440> more<00:21:47.340> of<00:21:47.460> doing<00:21:47.700> small 00:21:48.049 --> 00:21:48.059 align:start position:0% more Unix philosophy more of doing small 00:21:48.059 --> 00:21:50.590 align:start position:0% more Unix philosophy more of doing small things<00:21:48.419> more<00:21:48.960> of<00:21:49.080> little<00:21:49.500> widgets<00:21:49.980> on<00:21:50.100> chain 00:21:50.590 --> 00:21:50.600 align:start position:0% things more of little widgets on chain 00:21:50.600 --> 00:21:53.470 align:start position:0% things more of little widgets on chain rather<00:21:51.600> than<00:21:51.840> uh 00:21:53.470 --> 00:21:53.480 align:start position:0% rather than uh 00:21:53.480 --> 00:21:56.210 align:start position:0% rather than uh Behemoth<00:21:54.480> type<00:21:55.020> contracts<00:21:55.679> that<00:21:55.799> try<00:21:55.980> to<00:21:56.100> do 00:21:56.210 --> 00:21:56.220 align:start position:0% Behemoth type contracts that try to do 00:21:56.220 --> 00:21:59.450 align:start position:0% Behemoth type contracts that try to do it<00:21:56.340> all<00:21:57.020> when<00:21:58.020> in<00:21:58.200> doubt<00:21:58.559> minimize<00:21:59.220> or 00:21:59.450 --> 00:21:59.460 align:start position:0% it all when in doubt minimize or 00:21:59.460 --> 00:22:01.909 align:start position:0% it all when in doubt minimize or eliminate<00:21:59.880> governance<00:22:00.299> and<00:22:01.020> when<00:22:01.500> you<00:22:01.799> do 00:22:01.909 --> 00:22:01.919 align:start position:0% eliminate governance and when you do 00:22:01.919 --> 00:22:04.909 align:start position:0% eliminate governance and when you do need<00:22:02.220> governance<00:22:02.760> make<00:22:03.600> it<00:22:03.780> small<00:22:04.080> it<00:22:04.620> governs 00:22:04.909 --> 00:22:04.919 align:start position:0% need governance make it small it governs 00:22:04.919 --> 00:22:06.710 align:start position:0% need governance make it small it governs this<00:22:05.159> one<00:22:05.400> component<00:22:05.880> that<00:22:06.179> interacts<00:22:06.600> with 00:22:06.710 --> 00:22:06.720 align:start position:0% this one component that interacts with 00:22:06.720 --> 00:22:08.570 align:start position:0% this one component that interacts with all<00:22:06.960> of<00:22:07.020> these<00:22:07.260> ungovernable<00:22:07.860> components 00:22:08.570 --> 00:22:08.580 align:start position:0% all of these ungovernable components 00:22:08.580 --> 00:22:11.090 align:start position:0% all of these ungovernable components this<00:22:09.120> is<00:22:09.419> very<00:22:09.539> very<00:22:10.080> important<00:22:10.620> like 00:22:11.090 --> 00:22:11.100 align:start position:0% this is very very important like 00:22:11.100 --> 00:22:13.430 align:start position:0% this is very very important like governance<00:22:11.640> is<00:22:11.880> a<00:22:12.059> liability<00:22:12.480> of<00:22:13.080> being<00:22:13.260> able 00:22:13.430 --> 00:22:13.440 align:start position:0% governance is a liability of being able 00:22:13.440 --> 00:22:15.890 align:start position:0% governance is a liability of being able to<00:22:13.559> manipulate<00:22:14.400> and<00:22:14.520> change<00:22:14.700> things<00:22:15.059> like 00:22:15.890 --> 00:22:15.900 align:start position:0% to manipulate and change things like 00:22:15.900 --> 00:22:18.169 align:start position:0% to manipulate and change things like with<00:22:16.260> L1<00:22:16.740> is<00:22:17.159> going<00:22:17.340> to<00:22:17.460> bite<00:22:17.640> you<00:22:17.760> in<00:22:17.940> the<00:22:18.059> ass 00:22:18.169 --> 00:22:18.179 align:start position:0% with L1 is going to bite you in the ass 00:22:18.179 --> 00:22:20.930 align:start position:0% with L1 is going to bite you in the ass if<00:22:18.419> it's<00:22:18.600> not<00:22:18.780> done<00:22:18.900> with<00:22:19.140> Incredible<00:22:19.559> care 00:22:20.930 --> 00:22:20.940 align:start position:0% if it's not done with Incredible care 00:22:20.940 --> 00:22:23.029 align:start position:0% if it's not done with Incredible care I<00:22:21.480> recommend<00:22:21.780> to<00:22:21.960> tend<00:22:22.200> towards<00:22:22.500> ossification 00:22:23.029 --> 00:22:23.039 align:start position:0% I recommend to tend towards ossification 00:22:23.039 --> 00:22:24.950 align:start position:0% I recommend to tend towards ossification similarly<00:22:23.700> if<00:22:24.000> you<00:22:24.059> need<00:22:24.240> upgrade<00:22:24.659> abilities 00:22:24.950 --> 00:22:24.960 align:start position:0% similarly if you need upgrade abilities 00:22:24.960 --> 00:22:26.870 align:start position:0% similarly if you need upgrade abilities today<00:22:25.200> have<00:22:25.620> a<00:22:25.860> path<00:22:26.039> in<00:22:26.460> which<00:22:26.580> you<00:22:26.760> don't 00:22:26.870 --> 00:22:26.880 align:start position:0% today have a path in which you don't 00:22:26.880 --> 00:22:28.909 align:start position:0% today have a path in which you don't need<00:22:27.120> it<00:22:27.360> in<00:22:27.720> the<00:22:27.840> future 00:22:28.909 --> 00:22:28.919 align:start position:0% need it in the future 00:22:28.919 --> 00:22:31.610 align:start position:0% need it in the future similarly 00:22:31.610 --> 00:22:31.620 align:start position:0% similarly 00:22:31.620 --> 00:22:34.909 align:start position:0% similarly I<00:22:32.280> think<00:22:32.460> there<00:22:33.059> must<00:22:33.240> be<00:22:33.600> more<00:22:34.380> interesting 00:22:34.909 --> 00:22:34.919 align:start position:0% I think there must be more interesting 00:22:34.919 --> 00:22:37.370 align:start position:0% I think there must be more interesting value<00:22:35.460> generation<00:22:36.000> models<00:22:36.539> than<00:22:36.960> the<00:22:37.200> ones 00:22:37.370 --> 00:22:37.380 align:start position:0% value generation models than the ones 00:22:37.380 --> 00:22:39.409 align:start position:0% value generation models than the ones currently<00:22:37.740> being<00:22:37.980> explored<00:22:38.460> today<00:22:38.700> I<00:22:39.240> think 00:22:39.409 --> 00:22:39.419 align:start position:0% currently being explored today I think 00:22:39.419 --> 00:22:40.970 align:start position:0% currently being explored today I think there<00:22:39.720> are<00:22:39.840> clearly<00:22:40.140> some<00:22:40.440> very<00:22:40.620> interesting 00:22:40.970 --> 00:22:40.980 align:start position:0% there are clearly some very interesting 00:22:40.980 --> 00:22:42.710 align:start position:0% there are clearly some very interesting things<00:22:41.220> that<00:22:41.460> are<00:22:41.580> being<00:22:41.700> done<00:22:41.940> on<00:22:42.299> ethereum 00:22:42.710 --> 00:22:42.720 align:start position:0% things that are being done on ethereum 00:22:42.720 --> 00:22:43.909 align:start position:0% things that are being done on ethereum with 00:22:43.909 --> 00:22:43.919 align:start position:0% with 00:22:43.919 --> 00:22:46.190 align:start position:0% with tokens<00:22:44.600> governance 00:22:46.190 --> 00:22:46.200 align:start position:0% tokens governance 00:22:46.200 --> 00:22:47.149 align:start position:0% tokens governance Etc 00:22:47.149 --> 00:22:47.159 align:start position:0% Etc 00:22:47.159 --> 00:22:50.990 align:start position:0% Etc but<00:22:47.820> I<00:22:48.600> promise<00:22:48.960> you<00:22:49.140> on<00:22:50.100> this<00:22:50.280> new<00:22:50.520> landscape 00:22:50.990 --> 00:22:51.000 align:start position:0% but I promise you on this new landscape 00:22:51.000 --> 00:22:53.270 align:start position:0% but I promise you on this new landscape of<00:22:51.480> coordinated<00:22:51.900> games<00:22:52.260> on<00:22:52.559> top<00:22:52.679> of<00:22:52.799> ethereum 00:22:53.270 --> 00:22:53.280 align:start position:0% of coordinated games on top of ethereum 00:22:53.280 --> 00:22:55.730 align:start position:0% of coordinated games on top of ethereum there<00:22:53.880> are<00:22:54.059> going<00:22:54.240> to<00:22:54.360> be<00:22:54.539> interesting<00:22:55.140> and 00:22:55.730 --> 00:22:55.740 align:start position:0% there are going to be interesting and 00:22:55.740 --> 00:22:57.289 align:start position:0% there are going to be interesting and less 00:22:57.289 --> 00:22:57.299 align:start position:0% less 00:22:57.299 --> 00:22:58.070 align:start position:0% less um 00:22:58.070 --> 00:22:58.080 align:start position:0% um 00:22:58.080 --> 00:23:00.590 align:start position:0% um potentially<00:22:58.860> risky<00:22:59.520> value<00:23:00.059> generation 00:23:00.590 --> 00:23:00.600 align:start position:0% potentially risky value generation 00:23:00.600 --> 00:23:02.210 align:start position:0% potentially risky value generation models 00:23:02.210 --> 00:23:02.220 align:start position:0% models 00:23:02.220 --> 00:23:03.830 align:start position:0% models check<00:23:02.760> it<00:23:02.940> out 00:23:03.830 --> 00:23:03.840 align:start position:0% check it out 00:23:03.840 --> 00:23:05.990 align:start position:0% check it out explore<00:23:04.559> the<00:23:04.740> non-financial<00:23:05.400> especially 00:23:05.990 --> 00:23:06.000 align:start position:0% explore the non-financial especially 00:23:06.000 --> 00:23:08.090 align:start position:0% explore the non-financial especially with<00:23:06.240> l2s<00:23:06.840> opening<00:23:07.200> up<00:23:07.320> more<00:23:07.559> scale<00:23:07.860> for 00:23:08.090 --> 00:23:08.100 align:start position:0% with l2s opening up more scale for 00:23:08.100 --> 00:23:10.850 align:start position:0% with l2s opening up more scale for ethereum<00:23:08.580> there's<00:23:09.120> much<00:23:09.360> more<00:23:09.600> room<00:23:09.960> in<00:23:10.679> this 00:23:10.850 --> 00:23:10.860 align:start position:0% ethereum there's much more room in this 00:23:10.860 --> 00:23:13.070 align:start position:0% ethereum there's much more room in this stack<00:23:11.159> to<00:23:11.640> be<00:23:11.760> doing<00:23:11.940> things<00:23:12.179> Beyond<00:23:12.720> just 00:23:13.070 --> 00:23:13.080 align:start position:0% stack to be doing things Beyond just 00:23:13.080 --> 00:23:15.649 align:start position:0% stack to be doing things Beyond just that<00:23:13.559> defy<00:23:14.100> Beyond<00:23:14.580> just<00:23:14.880> that<00:23:15.179> speculative 00:23:15.649 --> 00:23:15.659 align:start position:0% that defy Beyond just that speculative 00:23:15.659 --> 00:23:19.070 align:start position:0% that defy Beyond just that speculative cool<00:23:16.440> little<00:23:16.679> picture<00:23:17.299> I<00:23:18.299> I<00:23:18.480> do<00:23:18.900> think 00:23:19.070 --> 00:23:19.080 align:start position:0% cool little picture I I do think 00:23:19.080 --> 00:23:20.510 align:start position:0% cool little picture I I do think especially<00:23:19.500> in<00:23:19.740> the<00:23:19.860> identity<00:23:20.280> space 00:23:20.510 --> 00:23:20.520 align:start position:0% especially in the identity space 00:23:20.520 --> 00:23:23.330 align:start position:0% especially in the identity space especially<00:23:21.000> in<00:23:21.179> the<00:23:21.360> Privacy<00:23:21.659> space<00:23:22.220> there<00:23:23.220> is 00:23:23.330 --> 00:23:23.340 align:start position:0% especially in the Privacy space there is 00:23:23.340 --> 00:23:25.549 align:start position:0% especially in the Privacy space there is a<00:23:23.580> lot<00:23:23.940> of<00:23:24.179> incredible<00:23:24.480> work<00:23:24.720> to<00:23:24.900> be<00:23:25.020> done<00:23:25.200> in 00:23:25.549 --> 00:23:25.559 align:start position:0% a lot of incredible work to be done in 00:23:25.559 --> 00:23:28.909 align:start position:0% a lot of incredible work to be done in the<00:23:25.679> next<00:23:25.740> few<00:23:25.980> years 00:23:28.909 --> 00:23:28.919 align:start position:0% 00:23:28.919 --> 00:23:32.450 align:start position:0% oh<00:23:29.520> and<00:23:29.820> if<00:23:30.419> you're<00:23:30.539> riding<00:23:30.960> l2s<00:23:31.980> it's<00:23:32.340> time 00:23:32.450 --> 00:23:32.460 align:start position:0% oh and if you're riding l2s it's time 00:23:32.460 --> 00:23:34.070 align:start position:0% oh and if you're riding l2s it's time for<00:23:32.640> fraud<00:23:32.940> proofs<00:23:33.360> it's<00:23:33.720> time<00:23:33.960> for 00:23:34.070 --> 00:23:34.080 align:start position:0% for fraud proofs it's time for 00:23:34.080 --> 00:23:35.690 align:start position:0% for fraud proofs it's time for decentralized<00:23:34.679> sequencers<00:23:35.159> I<00:23:35.460> think<00:23:35.580> that 00:23:35.690 --> 00:23:35.700 align:start position:0% decentralized sequencers I think that 00:23:35.700 --> 00:23:39.830 align:start position:0% decentralized sequencers I think that goes<00:23:36.000> without<00:23:36.059> being<00:23:36.419> said<00:23:36.659> but 00:23:39.830 --> 00:23:39.840 align:start position:0% 00:23:39.840 --> 00:23:43.310 align:start position:0% if<00:23:40.320> l2s<00:23:40.860> are<00:23:41.039> going<00:23:41.100> to<00:23:41.220> inherit<00:23:41.640> the<00:23:42.120> not<00:23:42.360> only 00:23:43.310 --> 00:23:43.320 align:start position:0% if l2s are going to inherit the not only 00:23:43.320 --> 00:23:45.409 align:start position:0% if l2s are going to inherit the not only the<00:23:43.799> security<00:23:43.919> but<00:23:44.340> the<00:23:44.640> legitimacy<00:23:45.179> of 00:23:45.409 --> 00:23:45.419 align:start position:0% the security but the legitimacy of 00:23:45.419 --> 00:23:46.669 align:start position:0% the security but the legitimacy of ethereum 00:23:46.669 --> 00:23:46.679 align:start position:0% ethereum 00:23:46.679 --> 00:23:48.890 align:start position:0% ethereum we<00:23:47.100> can't<00:23:47.159> go<00:23:47.340> without<00:23:47.520> this<00:23:47.820> stuff<00:23:48.059> and<00:23:48.780> I 00:23:48.890 --> 00:23:48.900 align:start position:0% we can't go without this stuff and I 00:23:48.900 --> 00:23:50.690 align:start position:0% we can't go without this stuff and I think<00:23:49.140> the<00:23:49.320> former<00:23:49.679> is<00:23:49.799> is<00:23:49.980> obvious<00:23:50.400> the 00:23:50.690 --> 00:23:50.700 align:start position:0% think the former is is obvious the 00:23:50.700 --> 00:23:53.029 align:start position:0% think the former is is obvious the latter<00:23:50.880> is<00:23:51.179> is<00:23:51.419> not<00:23:51.659> so<00:23:51.840> obvious<00:23:52.140> obviously 00:23:53.029 --> 00:23:53.039 align:start position:0% latter is is not so obvious obviously 00:23:53.039 --> 00:23:54.409 align:start position:0% latter is is not so obvious obviously you<00:23:53.220> can<00:23:53.340> construct 00:23:54.409 --> 00:23:54.419 align:start position:0% you can construct 00:23:54.419 --> 00:23:56.810 align:start position:0% you can construct secure<00:23:54.900> l2s<00:23:55.559> without<00:23:56.100> a<00:23:56.400> decentralized 00:23:56.810 --> 00:23:56.820 align:start position:0% secure l2s without a decentralized 00:23:56.820 --> 00:23:58.610 align:start position:0% secure l2s without a decentralized sequencer<00:23:57.419> but<00:23:57.900> when<00:23:58.020> you<00:23:58.140> start<00:23:58.320> thinking 00:23:58.610 --> 00:23:58.620 align:start position:0% sequencer but when you start thinking 00:23:58.620 --> 00:24:00.230 align:start position:0% sequencer but when you start thinking about 00:24:00.230 --> 00:24:00.240 align:start position:0% about 00:24:00.240 --> 00:24:02.330 align:start position:0% about regulatory<00:24:01.140> risk<00:24:01.500> and<00:24:01.799> other<00:24:01.980> types<00:24:02.220> of 00:24:02.330 --> 00:24:02.340 align:start position:0% regulatory risk and other types of 00:24:02.340 --> 00:24:06.950 align:start position:0% regulatory risk and other types of things<00:24:02.460> at<00:24:02.700> play<00:24:02.940> here<00:24:03.179> these<00:24:03.900> are<00:24:04.020> a<00:24:04.200> must 00:24:06.950 --> 00:24:06.960 align:start position:0% 00:24:06.960 --> 00:24:08.570 align:start position:0% um<00:24:07.020> so<00:24:07.200> I<00:24:07.320> suggest<00:24:07.799> playing<00:24:08.039> the<00:24:08.220> metagame 00:24:08.570 --> 00:24:08.580 align:start position:0% um so I suggest playing the metagame 00:24:08.580 --> 00:24:10.549 align:start position:0% um so I suggest playing the metagame resilience<00:24:09.120> across<00:24:09.539> the<00:24:09.600> stack<00:24:09.840> not<00:24:10.260> at<00:24:10.440> all 00:24:10.549 --> 00:24:10.559 align:start position:0% resilience across the stack not at all 00:24:10.559 --> 00:24:12.710 align:start position:0% resilience across the stack not at all not<00:24:10.860> just<00:24:10.980> at<00:24:11.159> all<00:24:11.340> one<00:24:11.520> unify<00:24:12.360> this<00:24:12.539> whole 00:24:12.710 --> 00:24:12.720 align:start position:0% not just at all one unify this whole 00:24:12.720 --> 00:24:13.730 align:start position:0% not just at all one unify this whole thing 00:24:13.730 --> 00:24:13.740 align:start position:0% thing 00:24:13.740 --> 00:24:16.250 align:start position:0% thing um<00:24:13.799> everything<00:24:14.220> built<00:24:14.640> on<00:24:14.820> ethereum<00:24:15.360> does 00:24:16.250 --> 00:24:16.260 align:start position:0% um everything built on ethereum does 00:24:16.260 --> 00:24:17.930 align:start position:0% um everything built on ethereum does isn't<00:24:16.620> going<00:24:16.740> to<00:24:16.860> necessarily<00:24:17.280> last<00:24:17.520> for<00:24:17.760> 50 00:24:17.930 --> 00:24:17.940 align:start position:0% isn't going to necessarily last for 50 00:24:17.940 --> 00:24:20.210 align:start position:0% isn't going to necessarily last for 50 plus<00:24:18.240> years<00:24:18.480> but<00:24:18.960> the<00:24:19.200> the<00:24:19.500> applications<00:24:19.980> that 00:24:20.210 --> 00:24:20.220 align:start position:0% plus years but the the applications that 00:24:20.220 --> 00:24:22.010 align:start position:0% plus years but the the applications that matter<00:24:20.400> will 00:24:22.010 --> 00:24:22.020 align:start position:0% matter will 00:24:22.020 --> 00:24:24.409 align:start position:0% matter will and<00:24:22.440> uh<00:24:22.740> quick<00:24:22.980> Happy<00:24:23.220> Birthday<00:24:23.520> to<00:24:24.059> someone 00:24:24.409 --> 00:24:24.419 align:start position:0% and uh quick Happy Birthday to someone 00:24:24.419 --> 00:24:27.830 align:start position:0% and uh quick Happy Birthday to someone in<00:24:25.140> the<00:24:25.260> audience<00:24:25.620> that<00:24:26.100> I<00:24:26.940> could<00:24:27.179> not<00:24:27.360> do<00:24:27.659> any 00:24:27.830 --> 00:24:27.840 align:start position:0% in the audience that I could not do any 00:24:27.840 --> 00:24:30.110 align:start position:0% in the audience that I could not do any of<00:24:28.020> this<00:24:28.260> without 00:24:30.110 --> 00:24:30.120 align:start position:0% of this without 00:24:30.120 --> 00:24:32.100 align:start position:0% of this without thank<00:24:30.600> you 00:24:32.100 --> 00:24:32.110 align:start position:0% thank you 00:24:32.110 --> 00:24:34.430 align:start position:0% thank you [Applause] 00:24:34.430 --> 00:24:34.440 align:start position:0% [Applause] 00:24:34.440 --> 00:24:37.519 align:start position:0% [Applause] [Music]