WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.150 align:start position:0% [Music] 00:00:09.150 --> 00:00:09.160 align:start position:0% [Music] 00:00:09.160 --> 00:00:11.270 align:start position:0% [Music] on<00:00:09.320> what<00:00:09.480> is<00:00:09.599> going<00:00:09.840> into<00:00:10.120> the<00:00:10.240> Petra<00:00:10.639> upgrade 00:00:11.270 --> 00:00:11.280 align:start position:0% on what is going into the Petra upgrade 00:00:11.280 --> 00:00:12.749 align:start position:0% on what is going into the Petra upgrade we're<00:00:11.480> going<00:00:11.559> to<00:00:11.719> talk<00:00:11.880> about<00:00:12.080> all<00:00:12.200> the<00:00:12.320> eops 00:00:12.749 --> 00:00:12.759 align:start position:0% we're going to talk about all the eops 00:00:12.759 --> 00:00:14.509 align:start position:0% we're going to talk about all the eops that<00:00:12.840> are<00:00:12.960> going<00:00:13.080> to<00:00:13.240> the<00:00:13.320> Petra<00:00:13.639> upgrade 00:00:14.509 --> 00:00:14.519 align:start position:0% that are going to the Petra upgrade 00:00:14.519 --> 00:00:15.829 align:start position:0% that are going to the Petra upgrade quick<00:00:14.719> disclaimer<00:00:15.240> before<00:00:15.440> I<00:00:15.559> start 00:00:15.829 --> 00:00:15.839 align:start position:0% quick disclaimer before I start 00:00:15.839 --> 00:00:17.429 align:start position:0% quick disclaimer before I start everything<00:00:16.160> I'm<00:00:16.240> about<00:00:16.400> to<00:00:16.560> say<00:00:16.840> is<00:00:17.119> all 00:00:17.429 --> 00:00:17.439 align:start position:0% everything I'm about to say is all 00:00:17.439 --> 00:00:19.670 align:start position:0% everything I'm about to say is all informational<00:00:18.359> uh<00:00:18.480> for<00:00:18.720> informational<00:00:19.279> per 00:00:19.670 --> 00:00:19.680 align:start position:0% informational uh for informational per 00:00:19.680 --> 00:00:21.590 align:start position:0% informational uh for informational per purposes<00:00:20.439> should<00:00:20.640> not<00:00:20.800> be<00:00:20.960> construed<00:00:21.439> as 00:00:21.590 --> 00:00:21.600 align:start position:0% purposes should not be construed as 00:00:21.600 --> 00:00:23.109 align:start position:0% purposes should not be construed as Financial<00:00:22.000> or<00:00:22.160> investment 00:00:23.109 --> 00:00:23.119 align:start position:0% Financial or investment 00:00:23.119 --> 00:00:25.429 align:start position:0% Financial or investment advice<00:00:24.119> before<00:00:24.320> we<00:00:24.439> get<00:00:24.599> into<00:00:25.080> what's<00:00:25.240> going 00:00:25.429 --> 00:00:25.439 align:start position:0% advice before we get into what's going 00:00:25.439 --> 00:00:27.109 align:start position:0% advice before we get into what's going into<00:00:25.720> pectra<00:00:26.320> the<00:00:26.480> question<00:00:26.720> that<00:00:26.840> I<00:00:26.960> get 00:00:27.109 --> 00:00:27.119 align:start position:0% into pectra the question that I get 00:00:27.119 --> 00:00:28.790 align:start position:0% into pectra the question that I get asked<00:00:27.359> the<00:00:27.480> most<00:00:27.760> is<00:00:27.960> when<00:00:28.199> pectra<00:00:28.560> is<00:00:28.640> going 00:00:28.790 --> 00:00:28.800 align:start position:0% asked the most is when pectra is going 00:00:28.800 --> 00:00:30.150 align:start position:0% asked the most is when pectra is going on<00:00:28.920> to<00:00:29.039> main<00:00:29.279> T<00:00:29.519> so<00:00:29.599> I'm<00:00:29.679> just<00:00:29.759> going<00:00:29.840> to<00:00:30.000> get 00:00:30.150 --> 00:00:30.160 align:start position:0% on to main T so I'm just going to get 00:00:30.160 --> 00:00:31.749 align:start position:0% on to main T so I'm just going to get that<00:00:30.240> out<00:00:30.359> of<00:00:30.439> the<00:00:30.560> way<00:00:31.160> um<00:00:31.279> so<00:00:31.439> we<00:00:31.519> can<00:00:31.640> get 00:00:31.749 --> 00:00:31.759 align:start position:0% that out of the way um so we can get 00:00:31.759 --> 00:00:34.229 align:start position:0% that out of the way um so we can get into<00:00:31.960> the<00:00:32.079> technical<00:00:32.520> stuff<00:00:33.360> um<00:00:33.640> this<00:00:33.920> is<00:00:34.040> a 00:00:34.229 --> 00:00:34.239 align:start position:0% into the technical stuff um this is a 00:00:34.239 --> 00:00:37.229 align:start position:0% into the technical stuff um this is a very<00:00:34.640> tentative<00:00:35.640> timeline<00:00:36.120> analysis<00:00:37.079> and 00:00:37.229 --> 00:00:37.239 align:start position:0% very tentative timeline analysis and 00:00:37.239 --> 00:00:39.750 align:start position:0% very tentative timeline analysis and everyone's<00:00:37.559> taking<00:00:37.760> pictures<00:00:38.120> already<00:00:39.120> um 00:00:39.750 --> 00:00:39.760 align:start position:0% everyone's taking pictures already um 00:00:39.760 --> 00:00:41.510 align:start position:0% everyone's taking pictures already um when<00:00:40.000> people<00:00:40.239> ask<00:00:40.440> me<00:00:40.680> when<00:00:40.840> is<00:00:41.000> Petra<00:00:41.280> gon<00:00:41.360> to 00:00:41.510 --> 00:00:41.520 align:start position:0% when people ask me when is Petra gon to 00:00:41.520 --> 00:00:44.029 align:start position:0% when people ask me when is Petra gon to happen<00:00:42.200> I<00:00:42.360> say<00:00:42.760> it's<00:00:42.920> too<00:00:43.160> early<00:00:43.480> to<00:00:43.640> tell 00:00:44.029 --> 00:00:44.039 align:start position:0% happen I say it's too early to tell 00:00:44.039 --> 00:00:46.430 align:start position:0% happen I say it's too early to tell because<00:00:44.239> it's<00:00:44.480> true<00:00:45.120> te<00:00:45.360> Petra<00:00:45.719> is<00:00:45.840> still<00:00:46.120> in 00:00:46.430 --> 00:00:46.440 align:start position:0% because it's true te Petra is still in 00:00:46.440 --> 00:00:49.150 align:start position:0% because it's true te Petra is still in very<00:00:46.680> early<00:00:47.039> stages<00:00:47.719> of<00:00:48.079> its<00:00:48.480> development 00:00:49.150 --> 00:00:49.160 align:start position:0% very early stages of its development 00:00:49.160 --> 00:00:51.709 align:start position:0% very early stages of its development specifications<00:00:49.800> are<00:00:50.120> changing<00:00:51.039> there's<00:00:51.559> the 00:00:51.709 --> 00:00:51.719 align:start position:0% specifications are changing there's the 00:00:51.719 --> 00:00:54.029 align:start position:0% specifications are changing there's the scope<00:00:52.039> of<00:00:52.199> pectra<00:00:52.719> even<00:00:53.079> has<00:00:53.239> not<00:00:53.520> really 00:00:54.029 --> 00:00:54.039 align:start position:0% scope of pectra even has not really 00:00:54.039 --> 00:00:55.950 align:start position:0% scope of pectra even has not really truly<00:00:54.440> been<00:00:54.640> finalized<00:00:55.239> quite<00:00:55.440> yet<00:00:55.680> as<00:00:55.800> we'll 00:00:55.950 --> 00:00:55.960 align:start position:0% truly been finalized quite yet as we'll 00:00:55.960 --> 00:00:58.349 align:start position:0% truly been finalized quite yet as we'll talk<00:00:56.199> about<00:00:57.160> um<00:00:57.399> but<00:00:57.520> through<00:00:57.760> this<00:00:58.000> process 00:00:58.349 --> 00:00:58.359 align:start position:0% talk about um but through this process 00:00:58.359 --> 00:00:59.709 align:start position:0% talk about um but through this process one<00:00:58.480> of<00:00:58.559> the<00:00:58.680> things<00:00:58.920> that<00:00:59.000> you<00:00:59.120> can<00:00:59.239> learn<00:00:59.519> is 00:00:59.709 --> 00:00:59.719 align:start position:0% one of the things that you can learn is 00:00:59.719 --> 00:01:02.910 align:start position:0% one of the things that you can learn is how<00:01:00.320> upgrades<00:01:01.320> get<00:01:01.519> developed<00:01:02.160> how<00:01:02.440> upgrades 00:01:02.910 --> 00:01:02.920 align:start position:0% how upgrades get developed how upgrades 00:01:02.920 --> 00:01:04.950 align:start position:0% how upgrades get developed how upgrades get<00:01:03.080> tested<00:01:04.080> um<00:01:04.239> and<00:01:04.400> eventually<00:01:04.760> make<00:01:04.879> it 00:01:04.950 --> 00:01:04.960 align:start position:0% get tested um and eventually make it 00:01:04.960 --> 00:01:07.390 align:start position:0% get tested um and eventually make it onto<00:01:05.199> mainnet<00:01:05.840> so<00:01:06.560> initially<00:01:06.960> what<00:01:07.080> happens 00:01:07.390 --> 00:01:07.400 align:start position:0% onto mainnet so initially what happens 00:01:07.400 --> 00:01:09.350 align:start position:0% onto mainnet so initially what happens is<00:01:07.640> developers<00:01:08.159> decide<00:01:08.479> on<00:01:08.560> a<00:01:08.640> couple<00:01:08.880> eips<00:01:09.280> to 00:01:09.350 --> 00:01:09.360 align:start position:0% is developers decide on a couple eips to 00:01:09.360 --> 00:01:11.230 align:start position:0% is developers decide on a couple eips to include<00:01:09.600> in<00:01:09.680> an<00:01:09.880> upgrade<00:01:10.720> and<00:01:10.840> then<00:01:11.080> they 00:01:11.230 --> 00:01:11.240 align:start position:0% include in an upgrade and then they 00:01:11.240 --> 00:01:13.310 align:start position:0% include in an upgrade and then they Implement<00:01:11.640> those<00:01:11.799> eips<00:01:12.400> onto<00:01:12.920> private 00:01:13.310 --> 00:01:13.320 align:start position:0% Implement those eips onto private 00:01:13.320 --> 00:01:15.429 align:start position:0% Implement those eips onto private developer<00:01:13.840> focused<00:01:14.280> test<00:01:14.560> Nets<00:01:14.880> called<00:01:15.159> Dev 00:01:15.429 --> 00:01:15.439 align:start position:0% developer focused test Nets called Dev 00:01:15.439 --> 00:01:16.670 align:start position:0% developer focused test Nets called Dev Nets<00:01:15.720> and<00:01:15.840> developers<00:01:16.280> have<00:01:16.479> already 00:01:16.670 --> 00:01:16.680 align:start position:0% Nets and developers have already 00:01:16.680 --> 00:01:18.310 align:start position:0% Nets and developers have already launched<00:01:17.119> a<00:01:17.240> couple<00:01:17.479> of<00:01:17.600> Dev<00:01:17.840> Nets<00:01:18.080> already 00:01:18.310 --> 00:01:18.320 align:start position:0% launched a couple of Dev Nets already 00:01:18.320 --> 00:01:20.870 align:start position:0% launched a couple of Dev Nets already for<00:01:18.520> pectra<00:01:19.520> um<00:01:19.680> so<00:01:19.880> these<00:01:20.079> eaps<00:01:20.560> have<00:01:20.680> already 00:01:20.870 --> 00:01:20.880 align:start position:0% for pectra um so these eaps have already 00:01:20.880 --> 00:01:22.630 align:start position:0% for pectra um so these eaps have already undergone<00:01:21.560> a<00:01:21.680> couple<00:01:21.920> of<00:01:22.079> rounds<00:01:22.439> of 00:01:22.630 --> 00:01:22.640 align:start position:0% undergone a couple of rounds of 00:01:22.640 --> 00:01:24.230 align:start position:0% undergone a couple of rounds of implementation<00:01:23.479> and<00:01:23.600> developers<00:01:24.119> have 00:01:24.230 --> 00:01:24.240 align:start position:0% implementation and developers have 00:01:24.240 --> 00:01:26.590 align:start position:0% implementation and developers have noticed<00:01:24.600> edge<00:01:24.960> cases<00:01:25.479> have<00:01:25.640> noticed<00:01:26.000> various 00:01:26.590 --> 00:01:26.600 align:start position:0% noticed edge cases have noticed various 00:01:26.600 --> 00:01:29.270 align:start position:0% noticed edge cases have noticed various bugs<00:01:26.960> that<00:01:27.079> they<00:01:27.200> want<00:01:27.320> to<00:01:27.479> fix<00:01:28.240> and<00:01:28.520> they<00:01:29.000> uh 00:01:29.270 --> 00:01:29.280 align:start position:0% bugs that they want to fix and they uh 00:01:29.280 --> 00:01:31.830 align:start position:0% bugs that they want to fix and they uh iterate<00:01:29.720> they<00:01:30.000> iterate<00:01:30.360> on<00:01:30.560> these<00:01:30.759> eips<00:01:31.600> uh<00:01:31.720> by 00:01:31.830 --> 00:01:31.840 align:start position:0% iterate they iterate on these eips uh by 00:01:31.840 --> 00:01:33.789 align:start position:0% iterate they iterate on these eips uh by launching<00:01:32.159> new<00:01:32.320> Dev<00:01:32.560> Nets<00:01:32.840> devet<00:01:33.200> 4<00:01:33.640> was 00:01:33.789 --> 00:01:33.799 align:start position:0% launching new Dev Nets devet 4 was 00:01:33.799 --> 00:01:36.950 align:start position:0% launching new Dev Nets devet 4 was launched<00:01:34.439> um<00:01:34.759> last<00:01:34.960> month<00:01:35.320> October<00:01:36.320> and<00:01:36.759> this 00:01:36.950 --> 00:01:36.960 align:start position:0% launched um last month October and this 00:01:36.960 --> 00:01:39.870 align:start position:0% launched um last month October and this doesn't<00:01:37.320> usually<00:01:37.720> happen<00:01:38.680> but<00:01:39.159> developers 00:01:39.870 --> 00:01:39.880 align:start position:0% doesn't usually happen but developers 00:01:39.880 --> 00:01:41.270 align:start position:0% doesn't usually happen but developers very<00:01:40.079> specially<00:01:40.520> for<00:01:40.720> this<00:01:40.880> entire 00:01:41.270 --> 00:01:41.280 align:start position:0% very specially for this entire 00:01:41.280 --> 00:01:42.550 align:start position:0% very specially for this entire conference<00:01:41.759> and<00:01:41.840> for<00:01:42.040> everybody<00:01:42.360> in<00:01:42.439> the 00:01:42.550 --> 00:01:42.560 align:start position:0% conference and for everybody in the 00:01:42.560 --> 00:01:44.670 align:start position:0% conference and for everybody in the audience<00:01:43.200> launched<00:01:43.720> the<00:01:43.920> first<00:01:44.320> public 00:01:44.670 --> 00:01:44.680 align:start position:0% audience launched the first public 00:01:44.680 --> 00:01:47.230 align:start position:0% audience launched the first public pectra<00:01:45.079> test<00:01:45.360> net<00:01:46.079> um<00:01:46.439> this<00:01:46.640> month<00:01:47.079> it's 00:01:47.230 --> 00:01:47.240 align:start position:0% pectra test net um this month it's 00:01:47.240 --> 00:01:50.149 align:start position:0% pectra test net um this month it's called<00:01:47.479> me<00:01:47.799> Kong<00:01:48.399> so<00:01:48.799> you<00:01:49.040> can<00:01:49.439> go<00:01:49.880> and 00:01:50.149 --> 00:01:50.159 align:start position:0% called me Kong so you can go and 00:01:50.159 --> 00:01:51.630 align:start position:0% called me Kong so you can go and interact<00:01:50.600> with<00:01:50.719> some<00:01:50.840> of<00:01:50.920> the<00:01:51.000> eips<00:01:51.439> that<00:01:51.520> are 00:01:51.630 --> 00:01:51.640 align:start position:0% interact with some of the eips that are 00:01:51.640 --> 00:01:54.230 align:start position:0% interact with some of the eips that are going<00:01:51.719> to<00:01:51.840> be<00:01:52.000> in<00:01:52.200> pectra<00:01:52.880> early<00:01:53.240> on<00:01:53.880> um<00:01:54.079> it's 00:01:54.230 --> 00:01:54.240 align:start position:0% going to be in pectra early on um it's 00:01:54.240 --> 00:01:56.709 align:start position:0% going to be in pectra early on um it's based<00:01:54.520> on<00:01:54.640> devet<00:01:55.000> 4<00:01:55.360> specifications<00:01:56.360> um<00:01:56.560> but 00:01:56.709 --> 00:01:56.719 align:start position:0% based on devet 4 specifications um but 00:01:56.719 --> 00:01:58.550 align:start position:0% based on devet 4 specifications um but please<00:01:57.000> note<00:01:57.360> that<00:01:57.520> those<00:01:57.719> specifications 00:01:58.550 --> 00:01:58.560 align:start position:0% please note that those specifications 00:01:58.560 --> 00:02:03.190 align:start position:0% please note that those specifications are<00:01:59.200> changing<00:02:00.280> there<00:02:00.560> is<00:02:00.840> a<00:02:01.200> list<00:02:02.039> of<00:02:02.600> changes 00:02:03.190 --> 00:02:03.200 align:start position:0% are changing there is a list of changes 00:02:03.200 --> 00:02:05.469 align:start position:0% are changing there is a list of changes specifications<00:02:03.880> changes<00:02:04.240> to<00:02:04.399> the<00:02:04.520> eips<00:02:05.320> that 00:02:05.469 --> 00:02:05.479 align:start position:0% specifications changes to the eips that 00:02:05.479 --> 00:02:08.109 align:start position:0% specifications changes to the eips that developers<00:02:06.039> already<00:02:06.600> want<00:02:06.840> to<00:02:07.399> uh<00:02:07.520> include 00:02:08.109 --> 00:02:08.119 align:start position:0% developers already want to uh include 00:02:08.119 --> 00:02:10.510 align:start position:0% developers already want to uh include into<00:02:08.440> pectra<00:02:08.800> devet<00:02:09.160> 5<00:02:09.720> so<00:02:09.920> there's<00:02:10.200> things 00:02:10.510 --> 00:02:10.520 align:start position:0% into pectra devet 5 so there's things 00:02:10.520 --> 00:02:14.110 align:start position:0% into pectra devet 5 so there's things like<00:02:11.080> uh<00:02:11.200> BLS<00:02:12.160> um<00:02:12.360> pre-compile<00:02:13.000> repricing<00:02:14.000> uh 00:02:14.110 --> 00:02:14.120 align:start position:0% like uh BLS um pre-compile repricing uh 00:02:14.120 --> 00:02:16.070 align:start position:0% like uh BLS um pre-compile repricing uh a<00:02:14.239> new<00:02:14.480> EIP<00:02:15.080> that<00:02:15.239> hasn't<00:02:15.440> been<00:02:15.599> implemented 00:02:16.070 --> 00:02:16.080 align:start position:0% a new EIP that hasn't been implemented 00:02:16.080 --> 00:02:18.350 align:start position:0% a new EIP that hasn't been implemented into<00:02:16.319> devet<00:02:16.680> 4<00:02:17.000> but<00:02:17.519> uh<00:02:17.640> developers<00:02:18.160> are 00:02:18.350 --> 00:02:18.360 align:start position:0% into devet 4 but uh developers are 00:02:18.360 --> 00:02:20.790 align:start position:0% into devet 4 but uh developers are aiming<00:02:18.680> to<00:02:18.840> implement<00:02:19.200> it<00:02:19.319> in<00:02:19.440> for<00:02:19.640> devet<00:02:20.040> 5<00:02:20.280> or 00:02:20.790 --> 00:02:20.800 align:start position:0% aiming to implement it in for devet 5 or 00:02:20.800 --> 00:02:23.470 align:start position:0% aiming to implement it in for devet 5 or a<00:02:20.920> future<00:02:21.280> upgrade<00:02:22.200> so<00:02:22.560> Petra<00:02:22.920> specifications 00:02:23.470 --> 00:02:23.480 align:start position:0% a future upgrade so Petra specifications 00:02:23.480 --> 00:02:26.110 align:start position:0% a future upgrade so Petra specifications are<00:02:23.640> changing<00:02:24.200> I<00:02:24.280> foresee<00:02:25.120> multiple<00:02:25.560> more<00:02:25.800> Dev 00:02:26.110 --> 00:02:26.120 align:start position:0% are changing I foresee multiple more Dev 00:02:26.120 --> 00:02:28.470 align:start position:0% are changing I foresee multiple more Dev Nets<00:02:26.599> still<00:02:26.840> to<00:02:27.080> go<00:02:27.440> before<00:02:27.800> specifications 00:02:28.470 --> 00:02:28.480 align:start position:0% Nets still to go before specifications 00:02:28.480 --> 00:02:30.990 align:start position:0% Nets still to go before specifications can<00:02:28.640> really<00:02:28.840> be<00:02:28.959> frozen<00:02:30.160> and<00:02:30.400> the<00:02:30.519> other<00:02:30.800> part 00:02:30.990 --> 00:02:31.000 align:start position:0% can really be frozen and the other part 00:02:31.000 --> 00:02:32.750 align:start position:0% can really be frozen and the other part that's<00:02:31.239> really<00:02:31.480> important<00:02:32.000> for<00:02:32.280> the<00:02:32.440> Petra 00:02:32.750 --> 00:02:32.760 align:start position:0% that's really important for the Petra 00:02:32.760 --> 00:02:35.470 align:start position:0% that's really important for the Petra upgrade<00:02:33.319> in<00:02:33.800> its<00:02:34.120> progress<00:02:34.519> to<00:02:34.720> mainnet<00:02:35.360> is 00:02:35.470 --> 00:02:35.480 align:start position:0% upgrade in its progress to mainnet is 00:02:35.480 --> 00:02:37.869 align:start position:0% upgrade in its progress to mainnet is for<00:02:35.680> the<00:02:35.800> scope<00:02:36.160> to<00:02:36.280> be<00:02:36.440> finalized<00:02:37.280> for<00:02:37.519> all<00:02:37.680> of 00:02:37.869 --> 00:02:37.879 align:start position:0% for the scope to be finalized for all of 00:02:37.879 --> 00:02:40.390 align:start position:0% for the scope to be finalized for all of the<00:02:37.959> eips<00:02:38.400> going<00:02:38.599> into<00:02:38.840> Petra<00:02:39.800> um<00:02:40.040> to<00:02:40.200> be 00:02:40.390 --> 00:02:40.400 align:start position:0% the eips going into Petra um to be 00:02:40.400 --> 00:02:43.190 align:start position:0% the eips going into Petra um to be decided<00:02:40.879> on<00:02:41.400> decided<00:02:41.840> upon<00:02:42.159> with<00:02:42.400> developers 00:02:43.190 --> 00:02:43.200 align:start position:0% decided on decided upon with developers 00:02:43.200 --> 00:02:45.949 align:start position:0% decided on decided upon with developers and<00:02:43.800> there<00:02:43.959> is<00:02:44.159> one<00:02:44.400> EIP<00:02:45.319> it's<00:02:45.440> not<00:02:45.599> really<00:02:45.879> an 00:02:45.949 --> 00:02:45.959 align:start position:0% and there is one EIP it's not really an 00:02:45.959 --> 00:02:48.750 align:start position:0% and there is one EIP it's not really an EIP<00:02:46.440> yet<00:02:47.159> but<00:02:47.319> it's<00:02:47.519> the<00:02:47.680> blob<00:02:48.200> capacity 00:02:48.750 --> 00:02:48.760 align:start position:0% EIP yet but it's the blob capacity 00:02:48.760 --> 00:02:50.830 align:start position:0% EIP yet but it's the blob capacity increase<00:02:49.519> that<00:02:49.680> is<00:02:49.840> what<00:02:50.040> developers<00:02:50.680> have 00:02:50.830 --> 00:02:50.840 align:start position:0% increase that is what developers have 00:02:50.840 --> 00:02:53.670 align:start position:0% increase that is what developers have not<00:02:51.200> yet<00:02:51.599> formally<00:02:52.159> included<00:02:52.599> into<00:02:52.959> pectra 00:02:53.670 --> 00:02:53.680 align:start position:0% not yet formally included into pectra 00:02:53.680 --> 00:02:55.270 align:start position:0% not yet formally included into pectra but<00:02:53.959> it<00:02:54.080> seems<00:02:54.319> as<00:02:54.440> though<00:02:54.560> they're<00:02:54.800> likely<00:02:55.080> to 00:02:55.270 --> 00:02:55.280 align:start position:0% but it seems as though they're likely to 00:02:55.280 --> 00:02:57.110 align:start position:0% but it seems as though they're likely to include<00:02:55.599> a<00:02:55.720> blob<00:02:56.040> capacity<00:02:56.480> increase<00:02:56.920> some 00:02:57.110 --> 00:02:57.120 align:start position:0% include a blob capacity increase some 00:02:57.120 --> 00:02:58.869 align:start position:0% include a blob capacity increase some kind<00:02:57.280> of<00:02:57.400> a<00:02:57.519> blob<00:02:57.800> capacity<00:02:58.200> increase<00:02:58.560> into 00:02:58.869 --> 00:02:58.879 align:start position:0% kind of a blob capacity increase into 00:02:58.879 --> 00:03:01.070 align:start position:0% kind of a blob capacity increase into pectra<00:02:59.519> because<00:03:00.000> of<00:03:00.120> the<00:03:00.239> fact<00:03:00.480> that<00:03:00.680> they 00:03:01.070 --> 00:03:01.080 align:start position:0% pectra because of the fact that they 00:03:01.080 --> 00:03:03.830 align:start position:0% pectra because of the fact that they have<00:03:01.280> recently<00:03:01.720> included<00:03:02.720> uh<00:03:02.879> this<00:03:03.040> EIP<00:03:03.720> which 00:03:03.830 --> 00:03:03.840 align:start position:0% have recently included uh this EIP which 00:03:03.840 --> 00:03:04.830 align:start position:0% have recently included uh this EIP which we're<00:03:03.959> going<00:03:04.040> to<00:03:04.200> talk<00:03:04.400> about<00:03:04.720> which 00:03:04.830 --> 00:03:04.840 align:start position:0% we're going to talk about which 00:03:04.840 --> 00:03:07.470 align:start position:0% we're going to talk about which introduces<00:03:05.360> a<00:03:05.519> mechanism<00:03:06.440> to<00:03:06.720> be<00:03:06.879> able<00:03:07.159> to 00:03:07.470 --> 00:03:07.480 align:start position:0% introduces a mechanism to be able to 00:03:07.480 --> 00:03:09.949 align:start position:0% introduces a mechanism to be able to update<00:03:07.959> the<00:03:08.120> blob<00:03:08.599> gas<00:03:08.879> Target<00:03:09.360> and<00:03:09.480> the<00:03:09.599> blob 00:03:09.949 --> 00:03:09.959 align:start position:0% update the blob gas Target and the blob 00:03:09.959 --> 00:03:12.229 align:start position:0% update the blob gas Target and the blob gas<00:03:10.239> Max<00:03:11.200> um<00:03:11.400> dynamically<00:03:11.959> through<00:03:12.120> the 00:03:12.229 --> 00:03:12.239 align:start position:0% gas Max um dynamically through the 00:03:12.239 --> 00:03:14.030 align:start position:0% gas Max um dynamically through the consensus<00:03:12.640> layer<00:03:13.080> rather<00:03:13.640> rather<00:03:13.879> than 00:03:14.030 --> 00:03:14.040 align:start position:0% consensus layer rather rather than 00:03:14.040 --> 00:03:15.910 align:start position:0% consensus layer rather rather than having<00:03:14.280> those<00:03:14.480> par<00:03:14.799> parameters<00:03:15.319> hard-coded 00:03:15.910 --> 00:03:15.920 align:start position:0% having those par parameters hard-coded 00:03:15.920 --> 00:03:17.350 align:start position:0% having those par parameters hard-coded in<00:03:16.000> the<00:03:16.159> execution<00:03:16.560> layer<00:03:16.760> and<00:03:16.879> the<00:03:16.959> consensus 00:03:17.350 --> 00:03:17.360 align:start position:0% in the execution layer and the consensus 00:03:17.360 --> 00:03:19.350 align:start position:0% in the execution layer and the consensus layer<00:03:18.120> um<00:03:18.319> so<00:03:18.560> the<00:03:18.680> addition<00:03:19.040> of<00:03:19.200> that 00:03:19.350 --> 00:03:19.360 align:start position:0% layer um so the addition of that 00:03:19.360 --> 00:03:21.390 align:start position:0% layer um so the addition of that mechanism<00:03:19.799> into<00:03:20.120> pectra<00:03:20.760> suggests<00:03:21.280> that 00:03:21.390 --> 00:03:21.400 align:start position:0% mechanism into pectra suggests that 00:03:21.400 --> 00:03:23.550 align:start position:0% mechanism into pectra suggests that developers<00:03:22.000> are<00:03:22.680> doing<00:03:23.040> all<00:03:23.200> the<00:03:23.360> heavy 00:03:23.550 --> 00:03:23.560 align:start position:0% developers are doing all the heavy 00:03:23.560 --> 00:03:27.350 align:start position:0% developers are doing all the heavy lifting<00:03:24.560> of<00:03:25.080> trying<00:03:25.400> to<00:03:26.000> um<00:03:26.760> Implement<00:03:27.200> a 00:03:27.350 --> 00:03:27.360 align:start position:0% lifting of trying to um Implement a 00:03:27.360 --> 00:03:29.990 align:start position:0% lifting of trying to um Implement a change<00:03:27.640> to<00:03:27.879> blob<00:03:28.200> capacity<00:03:28.599> increase<00:03:29.319> or<00:03:29.840> a 00:03:29.990 --> 00:03:30.000 align:start position:0% change to blob capacity increase or a 00:03:30.000 --> 00:03:33.630 align:start position:0% change to blob capacity increase or a change<00:03:30.400> to<00:03:30.959> the<00:03:31.080> blob<00:03:31.480> capacity<00:03:32.080> in<00:03:32.519> pectra<00:03:33.519> um 00:03:33.630 --> 00:03:33.640 align:start position:0% change to the blob capacity in pectra um 00:03:33.640 --> 00:03:35.830 align:start position:0% change to the blob capacity in pectra um but<00:03:33.799> developers<00:03:34.280> have<00:03:34.439> not<00:03:34.680> formally<00:03:35.640> um 00:03:35.830 --> 00:03:35.840 align:start position:0% but developers have not formally um 00:03:35.840 --> 00:03:39.309 align:start position:0% but developers have not formally um decided<00:03:36.360> or<00:03:36.560> formally<00:03:37.360> included<00:03:38.360> um<00:03:38.799> that 00:03:39.309 --> 00:03:39.319 align:start position:0% decided or formally included um that 00:03:39.319 --> 00:03:41.229 align:start position:0% decided or formally included um that increase<00:03:39.840> like<00:03:40.080> right<00:03:40.239> now<00:03:40.480> it's<00:03:40.640> a<00:03:40.799> target<00:03:41.080> of 00:03:41.229 --> 00:03:41.239 align:start position:0% increase like right now it's a target of 00:03:41.239 --> 00:03:44.030 align:start position:0% increase like right now it's a target of three<00:03:41.560> and<00:03:41.680> a<00:03:41.799> Max<00:03:42.080> of<00:03:42.280> six<00:03:43.239> um<00:03:43.560> they're<00:03:43.799> not 00:03:44.030 --> 00:03:44.040 align:start position:0% three and a Max of six um they're not 00:03:44.040 --> 00:03:46.229 align:start position:0% three and a Max of six um they're not sure<00:03:44.640> if<00:03:44.760> it's<00:03:44.920> going<00:03:45.040> to<00:03:45.200> be<00:03:45.560> an<00:03:45.760> increase<00:03:46.080> of 00:03:46.229 --> 00:03:46.239 align:start position:0% sure if it's going to be an increase of 00:03:46.239 --> 00:03:49.550 align:start position:0% sure if it's going to be an increase of four<00:03:46.560> or<00:03:46.760> five<00:03:47.000> or<00:03:47.239> six<00:03:48.239> um<00:03:48.480> so<00:03:48.920> ideally 00:03:49.550 --> 00:03:49.560 align:start position:0% four or five or six um so ideally 00:03:49.560 --> 00:03:52.190 align:start position:0% four or five or six um so ideally hopefully<00:03:50.080> developers<00:03:50.640> will<00:03:50.879> be<00:03:51.080> able<00:03:51.360> to<00:03:52.040> uh 00:03:52.190 --> 00:03:52.200 align:start position:0% hopefully developers will be able to uh 00:03:52.200 --> 00:03:55.190 align:start position:0% hopefully developers will be able to uh finalize<00:03:52.799> that<00:03:53.239> early<00:03:53.599> next<00:03:53.920> year<00:03:54.680> um<00:03:54.920> and<00:03:55.040> I 00:03:55.190 --> 00:03:55.200 align:start position:0% finalize that early next year um and I 00:03:55.200 --> 00:03:57.390 align:start position:0% finalize that early next year um and I think<00:03:55.599> as<00:03:55.959> the<00:03:56.200> specifications<00:03:56.959> for<00:03:57.280> the 00:03:57.390 --> 00:03:57.400 align:start position:0% think as the specifications for the 00:03:57.400 --> 00:04:00.789 align:start position:0% think as the specifications for the other<00:03:57.640> pectra<00:03:58.040> eips<00:03:58.799> become<00:03:59.239> hardened<00:04:00.200> more 00:04:00.789 --> 00:04:00.799 align:start position:0% other pectra eips become hardened more 00:04:00.799 --> 00:04:02.670 align:start position:0% other pectra eips become hardened more uh<00:04:00.959> finalized<00:04:01.840> it<00:04:01.959> puts<00:04:02.239> pressure<00:04:02.480> on 00:04:02.670 --> 00:04:02.680 align:start position:0% uh finalized it puts pressure on 00:04:02.680 --> 00:04:04.589 align:start position:0% uh finalized it puts pressure on developers<00:04:03.239> to<00:04:03.400> kind<00:04:03.519> of<00:04:03.879> activate<00:04:04.280> them<00:04:04.439> on 00:04:04.589 --> 00:04:04.599 align:start position:0% developers to kind of activate them on 00:04:04.599 --> 00:04:06.270 align:start position:0% developers to kind of activate them on mainnet<00:04:05.040> and<00:04:05.159> in<00:04:05.239> order<00:04:05.480> to<00:04:05.599> do<00:04:05.799> that<00:04:05.959> you<00:04:06.159> have 00:04:06.270 --> 00:04:06.280 align:start position:0% mainnet and in order to do that you have 00:04:06.280 --> 00:04:08.110 align:start position:0% mainnet and in order to do that you have to<00:04:06.799> ensure<00:04:07.120> that<00:04:07.200> the<00:04:07.319> scope<00:04:07.519> of<00:04:07.640> the<00:04:07.760> upgrade 00:04:08.110 --> 00:04:08.120 align:start position:0% to ensure that the scope of the upgrade 00:04:08.120 --> 00:04:11.710 align:start position:0% to ensure that the scope of the upgrade is<00:04:08.239> fully<00:04:08.560> complete<00:04:09.000> so<00:04:09.680> um<00:04:09.920> you<00:04:10.040> know<00:04:10.439> strong 00:04:11.710 --> 00:04:11.720 align:start position:0% is fully complete so um you know strong 00:04:11.720 --> 00:04:14.789 align:start position:0% is fully complete so um you know strong strong<00:04:12.720> strong<00:04:13.159> I<00:04:13.280> guess<00:04:13.560> like<00:04:14.040> thinking<00:04:14.519> or 00:04:14.789 --> 00:04:14.799 align:start position:0% strong strong I guess like thinking or 00:04:14.799 --> 00:04:18.909 align:start position:0% strong strong I guess like thinking or or<00:04:15.519> reasoning<00:04:16.519> that<00:04:16.799> the<00:04:17.359> uh<00:04:17.759> fusaka<00:04:18.759> not 00:04:18.909 --> 00:04:18.919 align:start position:0% or reasoning that the uh fusaka not 00:04:18.919 --> 00:04:21.590 align:start position:0% or reasoning that the uh fusaka not fusaka<00:04:19.400> that<00:04:19.519> the<00:04:19.639> pectra<00:04:20.320> scope<00:04:20.840> will<00:04:21.040> be<00:04:21.479> uh 00:04:21.590 --> 00:04:21.600 align:start position:0% fusaka that the pectra scope will be uh 00:04:21.600 --> 00:04:24.230 align:start position:0% fusaka that the pectra scope will be uh finalized<00:04:22.360> by<00:04:22.600> early<00:04:22.960> next<00:04:23.199> year<00:04:23.880> um<00:04:24.000> and<00:04:24.080> then 00:04:24.230 --> 00:04:24.240 align:start position:0% finalized by early next year um and then 00:04:24.240 --> 00:04:27.310 align:start position:0% finalized by early next year um and then once<00:04:24.360> it<00:04:24.479> is<00:04:24.720> finalized<00:04:25.720> you<00:04:26.199> start<00:04:26.560> testing 00:04:27.310 --> 00:04:27.320 align:start position:0% once it is finalized you start testing 00:04:27.320 --> 00:04:28.670 align:start position:0% once it is finalized you start testing uh<00:04:27.440> whatever<00:04:27.720> new<00:04:27.919> eips<00:04:28.400> that<00:04:28.520> you've 00:04:28.670 --> 00:04:28.680 align:start position:0% uh whatever new eips that you've 00:04:28.680 --> 00:04:30.870 align:start position:0% uh whatever new eips that you've implemented<00:04:29.440> the<00:04:29.720> full<00:04:30.000> scope<00:04:30.320> of<00:04:30.440> the<00:04:30.560> Petra 00:04:30.870 --> 00:04:30.880 align:start position:0% implemented the full scope of the Petra 00:04:30.880 --> 00:04:33.070 align:start position:0% implemented the full scope of the Petra upgrade<00:04:31.240> you<00:04:31.400> test<00:04:31.759> that<00:04:32.280> um<00:04:32.400> and<00:04:32.560> battle<00:04:32.880> test 00:04:33.070 --> 00:04:33.080 align:start position:0% upgrade you test that um and battle test 00:04:33.080 --> 00:04:35.830 align:start position:0% upgrade you test that um and battle test it<00:04:33.320> on<00:04:33.639> a<00:04:33.720> couple<00:04:33.960> more<00:04:34.120> Dev<00:04:34.440> Nets<00:04:35.440> um<00:04:35.680> I 00:04:35.830 --> 00:04:35.840 align:start position:0% it on a couple more Dev Nets um I 00:04:35.840 --> 00:04:39.230 align:start position:0% it on a couple more Dev Nets um I Envision<00:04:36.400> say<00:04:36.639> you<00:04:37.240> know<00:04:38.240> until<00:04:38.639> maybe<00:04:38.840> devet 00:04:39.230 --> 00:04:39.240 align:start position:0% Envision say you know until maybe devet 00:04:39.240 --> 00:04:41.990 align:start position:0% Envision say you know until maybe devet 6<00:04:39.440> or<00:04:39.560> S<00:04:40.440> um<00:04:40.639> and<00:04:40.759> then<00:04:41.000> once<00:04:41.320> the<00:04:41.479> Petra 00:04:41.990 --> 00:04:42.000 align:start position:0% 6 or S um and then once the Petra 00:04:42.000 --> 00:04:44.749 align:start position:0% 6 or S um and then once the Petra specifications<00:04:42.759> are<00:04:42.960> frozen<00:04:43.960> they<00:04:44.160> are<00:04:44.520> ready 00:04:44.749 --> 00:04:44.759 align:start position:0% specifications are frozen they are ready 00:04:44.759 --> 00:04:47.070 align:start position:0% specifications are frozen they are ready to<00:04:44.960> go<00:04:45.520> all<00:04:45.720> the<00:04:45.840> edge<00:04:46.080> cases<00:04:46.759> uh<00:04:46.919> that 00:04:47.070 --> 00:04:47.080 align:start position:0% to go all the edge cases uh that 00:04:47.080 --> 00:04:49.110 align:start position:0% to go all the edge cases uh that developers<00:04:47.600> can<00:04:47.800> find<00:04:48.120> on<00:04:48.400> dev<00:04:48.720> Nets<00:04:49.000> have 00:04:49.110 --> 00:04:49.120 align:start position:0% developers can find on dev Nets have 00:04:49.120 --> 00:04:51.430 align:start position:0% developers can find on dev Nets have been<00:04:49.280> found<00:04:49.960> they<00:04:50.080> will<00:04:50.400> then<00:04:50.759> release<00:04:51.240> the 00:04:51.430 --> 00:04:51.440 align:start position:0% been found they will then release the 00:04:51.440 --> 00:04:53.270 align:start position:0% been found they will then release the Petra<00:04:51.840> specifications<00:04:52.759> uh<00:04:52.840> release<00:04:53.160> the 00:04:53.270 --> 00:04:53.280 align:start position:0% Petra specifications uh release the 00:04:53.280 --> 00:04:55.510 align:start position:0% Petra specifications uh release the Petra<00:04:53.560> upgrade<00:04:53.960> onto<00:04:54.440> public<00:04:54.800> ethereum<00:04:55.240> test 00:04:55.510 --> 00:04:55.520 align:start position:0% Petra upgrade onto public ethereum test 00:04:55.520 --> 00:04:57.550 align:start position:0% Petra upgrade onto public ethereum test Nets<00:04:56.039> there<00:04:56.120> are<00:04:56.280> two<00:04:56.520> right<00:04:56.639> now<00:04:56.840> sooa<00:04:57.440> and 00:04:57.550 --> 00:04:57.560 align:start position:0% Nets there are two right now sooa and 00:04:57.560 --> 00:05:00.430 align:start position:0% Nets there are two right now sooa and heski<00:04:58.479> heski<00:04:59.479> um 00:05:00.430 --> 00:05:00.440 align:start position:0% heski heski um 00:05:00.440 --> 00:05:03.990 align:start position:0% heski heski um Gorly<00:05:01.120> is<00:05:01.320> deprecated<00:05:02.000> I<00:05:02.160> believe<00:05:03.000> um<00:05:03.360> and 00:05:03.990 --> 00:05:04.000 align:start position:0% Gorly is deprecated I believe um and 00:05:04.000 --> 00:05:05.469 align:start position:0% Gorly is deprecated I believe um and historically<00:05:04.440> developers<00:05:04.880> have<00:05:05.039> budgeted 00:05:05.469 --> 00:05:05.479 align:start position:0% historically developers have budgeted 00:05:05.479 --> 00:05:08.230 align:start position:0% historically developers have budgeted about<00:05:05.720> two<00:05:06.000> weeks<00:05:06.600> between<00:05:07.400> um<00:05:07.680> public<00:05:07.960> test 00:05:08.230 --> 00:05:08.240 align:start position:0% about two weeks between um public test 00:05:08.240 --> 00:05:10.710 align:start position:0% about two weeks between um public test net<00:05:08.440> upgrades<00:05:09.440> um<00:05:09.919> in<00:05:10.199> kind<00:05:10.280> of<00:05:10.440> rare 00:05:10.710 --> 00:05:10.720 align:start position:0% net upgrades um in kind of rare 00:05:10.720 --> 00:05:12.749 align:start position:0% net upgrades um in kind of rare occasions<00:05:11.199> developers<00:05:11.680> kind<00:05:11.800> of<00:05:11.880> shrunk<00:05:12.360> that 00:05:12.749 --> 00:05:12.759 align:start position:0% occasions developers kind of shrunk that 00:05:12.759 --> 00:05:14.390 align:start position:0% occasions developers kind of shrunk that timeline<00:05:13.160> down<00:05:13.320> to<00:05:13.520> even<00:05:13.720> just<00:05:13.880> one<00:05:14.080> week 00:05:14.390 --> 00:05:14.400 align:start position:0% timeline down to even just one week 00:05:14.400 --> 00:05:16.350 align:start position:0% timeline down to even just one week between<00:05:14.919> um<00:05:15.080> test<00:05:15.360> Nets<00:05:15.800> but<00:05:15.960> because<00:05:16.120> of<00:05:16.240> the 00:05:16.350 --> 00:05:16.360 align:start position:0% between um test Nets but because of the 00:05:16.360 --> 00:05:18.350 align:start position:0% between um test Nets but because of the size<00:05:16.520> of<00:05:16.680> pectra<00:05:17.560> um<00:05:17.759> I<00:05:17.880> imagine<00:05:18.240> that 00:05:18.350 --> 00:05:18.360 align:start position:0% size of pectra um I imagine that 00:05:18.360 --> 00:05:20.189 align:start position:0% size of pectra um I imagine that developers<00:05:18.840> will<00:05:19.160> want<00:05:19.319> to<00:05:19.520> take<00:05:19.759> the<00:05:19.880> full 00:05:20.189 --> 00:05:20.199 align:start position:0% developers will want to take the full 00:05:20.199 --> 00:05:22.790 align:start position:0% developers will want to take the full time<00:05:20.560> to<00:05:21.039> um<00:05:21.199> see<00:05:21.520> how<00:05:21.680> the<00:05:21.840> Petra<00:05:22.199> upgrade 00:05:22.790 --> 00:05:22.800 align:start position:0% time to um see how the Petra upgrade 00:05:22.800 --> 00:05:26.150 align:start position:0% time to um see how the Petra upgrade fares<00:05:23.400> on<00:05:23.880> public<00:05:24.160> test<00:05:24.479> net<00:05:24.919> environments<00:05:25.919> um 00:05:26.150 --> 00:05:26.160 align:start position:0% fares on public test net environments um 00:05:26.160 --> 00:05:28.790 align:start position:0% fares on public test net environments um so<00:05:26.960> I<00:05:27.120> am<00:05:27.280> budgeting<00:05:27.759> roughly<00:05:28.039> about<00:05:28.199> a<00:05:28.319> month 00:05:28.790 --> 00:05:28.800 align:start position:0% so I am budgeting roughly about a month 00:05:28.800 --> 00:05:31.790 align:start position:0% so I am budgeting roughly about a month for<00:05:29.280> the<00:05:29.840> sepolia<00:05:30.360> and<00:05:30.520> the<00:05:30.759> heski<00:05:31.240> heski<00:05:31.759> I 00:05:31.790 --> 00:05:31.800 align:start position:0% for the sepolia and the heski heski I 00:05:31.800 --> 00:05:33.110 align:start position:0% for the sepolia and the heski heski I don't<00:05:31.919> even<00:05:32.080> know<00:05:32.199> how<00:05:32.319> you<00:05:32.400> would<00:05:32.560> say<00:05:32.680> it 00:05:33.110 --> 00:05:33.120 align:start position:0% don't even know how you would say it 00:05:33.120 --> 00:05:36.950 align:start position:0% don't even know how you would say it right<00:05:33.400> but<00:05:33.919> heski<00:05:34.520> thank<00:05:34.639> you<00:05:34.840> sir<00:05:35.840> um<00:05:36.440> yeah<00:05:36.639> so 00:05:36.950 --> 00:05:36.960 align:start position:0% right but heski thank you sir um yeah so 00:05:36.960 --> 00:05:38.430 align:start position:0% right but heski thank you sir um yeah so that<00:05:37.120> that's<00:05:37.280> going<00:05:37.360> to<00:05:37.479> happen<00:05:38.039> and<00:05:38.280> I'm 00:05:38.430 --> 00:05:38.440 align:start position:0% that that's going to happen and I'm 00:05:38.440 --> 00:05:39.990 align:start position:0% that that's going to happen and I'm budgeting<00:05:38.840> about<00:05:38.960> a<00:05:39.080> month<00:05:39.240> for<00:05:39.479> that<00:05:39.919> and 00:05:39.990 --> 00:05:40.000 align:start position:0% budgeting about a month for that and 00:05:40.000 --> 00:05:42.070 align:start position:0% budgeting about a month for that and then<00:05:40.199> after<00:05:40.759> that's<00:05:41.039> when<00:05:41.319> you<00:05:41.440> can<00:05:41.680> finally 00:05:42.070 --> 00:05:42.080 align:start position:0% then after that's when you can finally 00:05:42.080 --> 00:05:44.830 align:start position:0% then after that's when you can finally have<00:05:42.440> the<00:05:42.600> main<00:05:42.880> net<00:05:43.199> activation<00:05:44.199> um<00:05:44.319> so<00:05:44.520> given 00:05:44.830 --> 00:05:44.840 align:start position:0% have the main net activation um so given 00:05:44.840 --> 00:05:46.629 align:start position:0% have the main net activation um so given all<00:05:45.000> of<00:05:45.160> the<00:05:45.280> information<00:05:45.960> that<00:05:46.080> I<00:05:46.199> know<00:05:46.479> right 00:05:46.629 --> 00:05:46.639 align:start position:0% all of the information that I know right 00:05:46.639 --> 00:05:49.670 align:start position:0% all of the information that I know right now<00:05:47.199> and<00:05:48.199> the<00:05:48.800> progress<00:05:49.120> that<00:05:49.280> developers 00:05:49.670 --> 00:05:49.680 align:start position:0% now and the progress that developers 00:05:49.680 --> 00:05:52.070 align:start position:0% now and the progress that developers have<00:05:49.800> made<00:05:49.960> so<00:05:50.080> far<00:05:50.240> on<00:05:50.440> pectra<00:05:51.360> my<00:05:51.639> best 00:05:52.070 --> 00:05:52.080 align:start position:0% have made so far on pectra my best 00:05:52.080 --> 00:05:54.070 align:start position:0% have made so far on pectra my best analysis<00:05:52.639> and<00:05:52.840> guess<00:05:53.080> is<00:05:53.199> that<00:05:53.360> pectra<00:05:53.680> maina 00:05:54.070 --> 00:05:54.080 align:start position:0% analysis and guess is that pectra maina 00:05:54.080 --> 00:05:56.469 align:start position:0% analysis and guess is that pectra maina will<00:05:54.240> realistically<00:05:55.039> happen<00:05:55.560> next<00:05:55.840> April 00:05:56.469 --> 00:05:56.479 align:start position:0% will realistically happen next April 00:05:56.479 --> 00:06:00.110 align:start position:0% will realistically happen next April 2025<00:05:57.479> um<00:05:57.759> again<00:05:58.039> this<00:05:58.160> is<00:05:58.400> very<00:05:58.720> tentative<00:05:59.880> um 00:06:00.110 --> 00:06:00.120 align:start position:0% 2025 um again this is very tentative um 00:06:00.120 --> 00:06:02.909 align:start position:0% 2025 um again this is very tentative um because<00:06:00.440> a<00:06:00.560> lot<00:06:00.759> can<00:06:00.919> change<00:06:01.360> between<00:06:01.720> now<00:06:02.240> and 00:06:02.909 --> 00:06:02.919 align:start position:0% because a lot can change between now and 00:06:02.919 --> 00:06:05.550 align:start position:0% because a lot can change between now and um<00:06:03.080> April<00:06:03.639> development<00:06:04.639> uh<00:06:05.039> happens<00:06:05.360> on<00:06:05.479> a 00:06:05.550 --> 00:06:05.560 align:start position:0% um April development uh happens on a 00:06:05.560 --> 00:06:07.990 align:start position:0% um April development uh happens on a week<00:06:05.759> toe<00:06:06.319> basis<00:06:06.759> developers<00:06:07.240> are<00:06:07.720> are<00:06:07.840> on 00:06:07.990 --> 00:06:08.000 align:start position:0% week toe basis developers are are on 00:06:08.000 --> 00:06:10.629 align:start position:0% week toe basis developers are are on these<00:06:08.160> ACD<00:06:08.599> calls<00:06:08.919> talking<00:06:09.240> about<00:06:10.039> um<00:06:10.440> this 00:06:10.629 --> 00:06:10.639 align:start position:0% these ACD calls talking about um this 00:06:10.639 --> 00:06:12.629 align:start position:0% these ACD calls talking about um this bug<00:06:10.960> that<00:06:11.080> they<00:06:11.199> didn't<00:06:11.520> expect<00:06:11.800> in<00:06:11.960> this<00:06:12.120> EIP 00:06:12.629 --> 00:06:12.639 align:start position:0% bug that they didn't expect in this EIP 00:06:12.639 --> 00:06:14.510 align:start position:0% bug that they didn't expect in this EIP or<00:06:12.840> this<00:06:12.960> new<00:06:13.160> EIP<00:06:13.720> that<00:06:13.840> they<00:06:13.919> do<00:06:14.080> want<00:06:14.199> to<00:06:14.360> add 00:06:14.510 --> 00:06:14.520 align:start position:0% or this new EIP that they do want to add 00:06:14.520 --> 00:06:17.550 align:start position:0% or this new EIP that they do want to add into<00:06:14.759> Petra<00:06:15.160> now<00:06:15.960> um<00:06:16.240> so<00:06:16.759> a<00:06:16.880> lot<00:06:17.000> of<00:06:17.160> things<00:06:17.400> can 00:06:17.550 --> 00:06:17.560 align:start position:0% into Petra now um so a lot of things can 00:06:17.560 --> 00:06:20.550 align:start position:0% into Petra now um so a lot of things can change<00:06:17.919> this<00:06:18.120> timeline<00:06:19.039> um<00:06:19.639> but<00:06:20.120> looking<00:06:20.360> into 00:06:20.550 --> 00:06:20.560 align:start position:0% change this timeline um but looking into 00:06:20.560 --> 00:06:22.510 align:start position:0% change this timeline um but looking into my<00:06:20.720> crystal<00:06:21.039> ball<00:06:21.560> there<00:06:21.680> you<00:06:21.840> have<00:06:22.000> it<00:06:22.319> my 00:06:22.510 --> 00:06:22.520 align:start position:0% my crystal ball there you have it my 00:06:22.520 --> 00:06:26.430 align:start position:0% my crystal ball there you have it my timeline<00:06:23.520> um<00:06:23.759> let's<00:06:24.000> move<00:06:24.240> on<00:06:25.000> to<00:06:26.000> what<00:06:26.120> is<00:06:26.319> the 00:06:26.430 --> 00:06:26.440 align:start position:0% timeline um let's move on to what is the 00:06:26.440 --> 00:06:27.909 align:start position:0% timeline um let's move on to what is the meat<00:06:26.840> you<00:06:26.960> know<00:06:27.120> the<00:06:27.240> bread<00:06:27.400> and<00:06:27.520> butter<00:06:27.800> of 00:06:27.909 --> 00:06:27.919 align:start position:0% meat you know the bread and butter of 00:06:27.919 --> 00:06:29.629 align:start position:0% meat you know the bread and butter of this<00:06:28.080> talk<00:06:28.599> which<00:06:28.720> is<00:06:28.880> what<00:06:29.039> is<00:06:29.160> going<00:06:29.319> into 00:06:29.629 --> 00:06:29.639 align:start position:0% this talk which is what is going into 00:06:29.639 --> 00:06:31.870 align:start position:0% this talk which is what is going into Petra<00:06:29.960> upgrade<00:06:30.639> there<00:06:30.759> are<00:06:31.000> 10<00:06:31.280> eips<00:06:31.720> that<00:06:31.800> are 00:06:31.870 --> 00:06:31.880 align:start position:0% Petra upgrade there are 10 eips that are 00:06:31.880 --> 00:06:34.270 align:start position:0% Petra upgrade there are 10 eips that are going<00:06:32.080> into<00:06:32.520> Petra<00:06:33.520> and<00:06:33.680> four<00:06:33.919> of<00:06:34.039> them<00:06:34.160> are 00:06:34.270 --> 00:06:34.280 align:start position:0% going into Petra and four of them are 00:06:34.280 --> 00:06:36.270 align:start position:0% going into Petra and four of them are focused<00:06:34.560> on<00:06:34.680> the<00:06:34.800> execution<00:06:35.199> layer<00:06:35.960> oh<00:06:36.120> my 00:06:36.270 --> 00:06:36.280 align:start position:0% focused on the execution layer oh my 00:06:36.280 --> 00:06:38.469 align:start position:0% focused on the execution layer oh my gosh<00:06:36.479> the<00:06:36.599> print<00:06:36.840> is<00:06:36.960> so<00:06:37.120> small<00:06:37.360> there<00:06:37.840> um<00:06:37.960> EIP 00:06:38.469 --> 00:06:38.479 align:start position:0% gosh the print is so small there um EIP 00:06:38.479 --> 00:06:42.110 align:start position:0% gosh the print is so small there um EIP 2537<00:06:39.479> it<00:06:39.680> is<00:06:40.000> a<00:06:40.360> uh<00:06:40.479> new<00:06:40.720> pre-compile<00:06:41.479> yay<00:06:41.919> new 00:06:42.110 --> 00:06:42.120 align:start position:0% 2537 it is a uh new pre-compile yay new 00:06:42.120 --> 00:06:46.309 align:start position:0% 2537 it is a uh new pre-compile yay new pre-compile<00:06:42.639> into<00:06:42.800> the<00:06:43.000> evm<00:06:44.000> um<00:06:44.160> BLS<00:06:45.319> 12381 00:06:46.309 --> 00:06:46.319 align:start position:0% pre-compile into the evm um BLS 12381 00:06:46.319 --> 00:06:48.230 align:start position:0% pre-compile into the evm um BLS 12381 curve<00:06:46.680> operation<00:06:47.639> this<00:06:47.800> is<00:06:47.919> a<00:06:48.039> new 00:06:48.230 --> 00:06:48.240 align:start position:0% curve operation this is a new 00:06:48.240 --> 00:06:50.390 align:start position:0% curve operation this is a new cryptographic<00:06:48.800> signature<00:06:49.240> scheme<00:06:49.840> um<00:06:50.039> that 00:06:50.390 --> 00:06:50.400 align:start position:0% cryptographic signature scheme um that 00:06:50.400 --> 00:06:51.790 align:start position:0% cryptographic signature scheme um that uh<00:06:50.479> smart<00:06:50.759> contract<00:06:51.039> developers<00:06:51.479> have<00:06:51.599> been 00:06:51.790 --> 00:06:51.800 align:start position:0% uh smart contract developers have been 00:06:51.800 --> 00:06:53.469 align:start position:0% uh smart contract developers have been asking<00:06:52.039> for<00:06:52.240> for<00:06:52.360> a<00:06:52.520> very<00:06:52.720> long<00:06:52.919> time<00:06:53.280> this<00:06:53.360> is 00:06:53.469 --> 00:06:53.479 align:start position:0% asking for for a very long time this is 00:06:53.479 --> 00:06:55.990 align:start position:0% asking for for a very long time this is an<00:06:53.599> EAP<00:06:53.919> that<00:06:54.000> was<00:06:54.120> created<00:06:54.400> in<00:06:54.599> 2020<00:06:55.599> and<00:06:55.879> at 00:06:55.990 --> 00:06:56.000 align:start position:0% an EAP that was created in 2020 and at 00:06:56.000 --> 00:06:57.390 align:start position:0% an EAP that was created in 2020 and at the<00:06:56.120> time<00:06:56.319> dap<00:06:56.560> developers<00:06:56.960> were<00:06:57.120> like<00:06:57.280> we 00:06:57.390 --> 00:06:57.400 align:start position:0% the time dap developers were like we 00:06:57.400 --> 00:06:59.230 align:start position:0% the time dap developers were like we really<00:06:57.560> want<00:06:57.840> this<00:06:58.160> because<00:06:58.400> it<00:06:58.479> would<00:06:58.639> be<00:06:59.039> um 00:06:59.230 --> 00:06:59.240 align:start position:0% really want this because it would be um 00:06:59.240 --> 00:07:02.070 align:start position:0% really want this because it would be um it<00:06:59.319> would<00:06:59.639> give<00:06:59.919> daps<00:07:00.919> um<00:07:01.039> certain<00:07:01.360> daps<00:07:01.960> that 00:07:02.070 --> 00:07:02.080 align:start position:0% it would give daps um certain daps that 00:07:02.080 --> 00:07:03.230 align:start position:0% it would give daps um certain daps that are<00:07:02.240> relying<00:07:02.560> on<00:07:02.720> zero<00:07:03.000> knowledge 00:07:03.230 --> 00:07:03.240 align:start position:0% are relying on zero knowledge 00:07:03.240 --> 00:07:05.430 align:start position:0% are relying on zero knowledge cryptography<00:07:04.039> um<00:07:04.280> stronger<00:07:05.120> stronger 00:07:05.430 --> 00:07:05.440 align:start position:0% cryptography um stronger stronger 00:07:05.440 --> 00:07:07.749 align:start position:0% cryptography um stronger stronger privacy<00:07:05.960> guarantees<00:07:06.960> um<00:07:07.120> potentially 00:07:07.749 --> 00:07:07.759 align:start position:0% privacy guarantees um potentially 00:07:07.759 --> 00:07:09.990 align:start position:0% privacy guarantees um potentially increased<00:07:08.199> security<00:07:08.840> and<00:07:09.000> scalability<00:07:09.919> I 00:07:09.990 --> 00:07:10.000 align:start position:0% increased security and scalability I 00:07:10.000 --> 00:07:11.909 align:start position:0% increased security and scalability I believe<00:07:10.319> BLS<00:07:10.759> signatures<00:07:11.479> that<00:07:11.759> that 00:07:11.909 --> 00:07:11.919 align:start position:0% believe BLS signatures that that 00:07:11.919 --> 00:07:14.350 align:start position:0% believe BLS signatures that that signature<00:07:12.440> scheme<00:07:12.800> or<00:07:13.039> that<00:07:13.240> aggregation<00:07:14.000> is 00:07:14.350 --> 00:07:14.360 align:start position:0% signature scheme or that aggregation is 00:07:14.360 --> 00:07:16.070 align:start position:0% signature scheme or that aggregation is also<00:07:14.720> the<00:07:14.919> signature<00:07:15.440> aggregation<00:07:15.960> that 00:07:16.070 --> 00:07:16.080 align:start position:0% also the signature aggregation that 00:07:16.080 --> 00:07:17.430 align:start position:0% also the signature aggregation that happens<00:07:16.319> on<00:07:16.440> the<00:07:16.520> consensus<00:07:16.960> layer<00:07:17.199> for 00:07:17.430 --> 00:07:17.440 align:start position:0% happens on the consensus layer for 00:07:17.440 --> 00:07:21.469 align:start position:0% happens on the consensus layer for validator<00:07:18.080> um<00:07:18.720> attestations<00:07:19.720> um<00:07:20.319> it<00:07:20.919> this<00:07:21.080> CIP 00:07:21.469 --> 00:07:21.479 align:start position:0% validator um attestations um it this CIP 00:07:21.479 --> 00:07:23.350 align:start position:0% validator um attestations um it this CIP is<00:07:21.599> a<00:07:21.680> long<00:07:21.840> time<00:07:22.039> coming<00:07:22.520> and<00:07:22.680> so<00:07:23.000> I<00:07:23.080> think<00:07:23.240> one 00:07:23.350 --> 00:07:23.360 align:start position:0% is a long time coming and so I think one 00:07:23.360 --> 00:07:25.749 align:start position:0% is a long time coming and so I think one of<00:07:23.479> the<00:07:23.759> concerns<00:07:24.160> around<00:07:24.360> the<00:07:24.479> CIP<00:07:25.160> is<00:07:25.599> are 00:07:25.749 --> 00:07:25.759 align:start position:0% of the concerns around the CIP is are 00:07:25.759 --> 00:07:28.230 align:start position:0% of the concerns around the CIP is are there<00:07:26.000> still<00:07:26.360> apps<00:07:26.960> that<00:07:27.160> are<00:07:27.400> waiting<00:07:27.759> for 00:07:28.230 --> 00:07:28.240 align:start position:0% there still apps that are waiting for 00:07:28.240 --> 00:07:30.309 align:start position:0% there still apps that are waiting for the<00:07:28.360> BLS<00:07:28.720> precompile<00:07:29.280> and<00:07:29.560> will<00:07:30.039> are<00:07:30.199> they 00:07:30.309 --> 00:07:30.319 align:start position:0% the BLS precompile and will are they 00:07:30.319 --> 00:07:32.749 align:start position:0% the BLS precompile and will are they going<00:07:30.400> to<00:07:30.560> use<00:07:30.720> it<00:07:31.440> uh<00:07:31.639> when<00:07:31.919> that<00:07:32.080> precompile 00:07:32.749 --> 00:07:32.759 align:start position:0% going to use it uh when that precompile 00:07:32.759 --> 00:07:35.990 align:start position:0% going to use it uh when that precompile goes<00:07:33.080> live<00:07:33.919> um<00:07:34.199> so<00:07:34.840> kind<00:07:34.960> of<00:07:35.080> an<00:07:35.199> open<00:07:35.520> question 00:07:35.990 --> 00:07:36.000 align:start position:0% goes live um so kind of an open question 00:07:36.000 --> 00:07:38.469 align:start position:0% goes live um so kind of an open question but<00:07:36.360> if<00:07:36.479> you're<00:07:36.639> in<00:07:36.800> this<00:07:36.919> audience<00:07:37.479> and<00:07:38.080> um 00:07:38.469 --> 00:07:38.479 align:start position:0% but if you're in this audience and um 00:07:38.479 --> 00:07:40.270 align:start position:0% but if you're in this audience and um didn't<00:07:38.759> know<00:07:39.000> that<00:07:39.120> the<00:07:39.199> BLS<00:07:39.639> pre-compile<00:07:40.120> is 00:07:40.270 --> 00:07:40.280 align:start position:0% didn't know that the BLS pre-compile is 00:07:40.280 --> 00:07:43.110 align:start position:0% didn't know that the BLS pre-compile is finally<00:07:40.599> coming<00:07:40.960> it's<00:07:41.120> coming<00:07:41.960> um<00:07:42.160> and<00:07:42.319> maybe 00:07:43.110 --> 00:07:43.120 align:start position:0% finally coming it's coming um and maybe 00:07:43.120 --> 00:07:45.350 align:start position:0% finally coming it's coming um and maybe you<00:07:43.280> know<00:07:43.520> you're<00:07:44.159> you<00:07:44.360> have<00:07:44.479> an<00:07:44.680> app<00:07:45.000> that 00:07:45.350 --> 00:07:45.360 align:start position:0% you know you're you have an app that 00:07:45.360 --> 00:07:47.629 align:start position:0% you know you're you have an app that hasn't<00:07:45.720> already<00:07:45.919> moved<00:07:46.240> on<00:07:46.680> from<00:07:47.039> this<00:07:47.280> vision 00:07:47.629 --> 00:07:47.639 align:start position:0% hasn't already moved on from this vision 00:07:47.639 --> 00:07:49.670 align:start position:0% hasn't already moved on from this vision and<00:07:47.840> can<00:07:48.000> still<00:07:48.240> utilize<00:07:48.759> this<00:07:49.080> pre-compile 00:07:49.670 --> 00:07:49.680 align:start position:0% and can still utilize this pre-compile 00:07:49.680 --> 00:07:52.670 align:start position:0% and can still utilize this pre-compile in<00:07:49.800> some<00:07:50.000> pretty<00:07:50.240> cool<00:07:50.440> ways<00:07:51.240> um<00:07:51.479> so<00:07:52.440> it's 00:07:52.670 --> 00:07:52.680 align:start position:0% in some pretty cool ways um so it's 00:07:52.680 --> 00:07:56.070 align:start position:0% in some pretty cool ways um so it's going<00:07:52.879> into<00:07:53.080> pectra<00:07:54.039> uh<00:07:54.199> EIP<00:07:54.599> 2935<00:07:55.520> serve 00:07:56.070 --> 00:07:56.080 align:start position:0% going into pectra uh EIP 2935 serve 00:07:56.080 --> 00:07:58.710 align:start position:0% going into pectra uh EIP 2935 serve historical<00:07:56.520> blasters<00:07:57.120> from<00:07:57.360> State<00:07:58.240> um<00:07:58.599> this 00:07:58.710 --> 00:07:58.720 align:start position:0% historical blasters from State um this 00:07:58.720 --> 00:08:00.309 align:start position:0% historical blasters from State um this one<00:07:58.960> introduces<00:07:59.520> is<00:07:59.599> a<00:07:59.720> change<00:07:59.960> to<00:08:00.159> the 00:08:00.309 --> 00:08:00.319 align:start position:0% one introduces is a change to the 00:08:00.319 --> 00:08:01.950 align:start position:0% one introduces is a change to the execution<00:08:00.759> layer<00:08:01.159> such<00:08:01.360> that<00:08:01.520> proofs<00:08:01.800> of 00:08:01.950 --> 00:08:01.960 align:start position:0% execution layer such that proofs of 00:08:01.960 --> 00:08:03.390 align:start position:0% execution layer such that proofs of historical<00:08:02.360> blocks<00:08:02.639> can<00:08:02.759> be<00:08:02.879> generated<00:08:03.280> from 00:08:03.390 --> 00:08:03.400 align:start position:0% historical blocks can be generated from 00:08:03.400 --> 00:08:05.070 align:start position:0% historical blocks can be generated from the<00:08:03.560> state<00:08:04.280> um<00:08:04.440> this<00:08:04.599> does<00:08:04.800> have<00:08:04.919> some 00:08:05.070 --> 00:08:05.080 align:start position:0% the state um this does have some 00:08:05.080 --> 00:08:07.909 align:start position:0% the state um this does have some near-term<00:08:05.599> benefits<00:08:06.319> so<00:08:07.159> um<00:08:07.360> it<00:08:07.560> has<00:08:07.720> some 00:08:07.909 --> 00:08:07.919 align:start position:0% near-term benefits so um it has some 00:08:07.919 --> 00:08:10.309 align:start position:0% near-term benefits so um it has some benefits<00:08:08.280> for<00:08:08.400> light<00:08:08.639> cin<00:08:08.919> syncing<00:08:09.599> has<00:08:10.120> um 00:08:10.309 --> 00:08:10.319 align:start position:0% benefits for light cin syncing has um 00:08:10.319 --> 00:08:12.270 align:start position:0% benefits for light cin syncing has um some<00:08:10.560> benefits<00:08:11.000> for<00:08:11.240> smart<00:08:11.560> contracts<00:08:12.039> that 00:08:12.270 --> 00:08:12.280 align:start position:0% some benefits for smart contracts that 00:08:12.280 --> 00:08:15.469 align:start position:0% some benefits for smart contracts that may<00:08:12.560> want<00:08:12.759> to<00:08:13.120> utilize<00:08:14.120> um<00:08:14.360> data<00:08:14.879> about<00:08:15.199> the 00:08:15.469 --> 00:08:15.479 align:start position:0% may want to utilize um data about the 00:08:15.479 --> 00:08:17.990 align:start position:0% may want to utilize um data about the state<00:08:15.840> of<00:08:15.960> a<00:08:16.240> prior<00:08:16.639> block<00:08:17.520> um<00:08:17.680> directly 00:08:17.990 --> 00:08:18.000 align:start position:0% state of a prior block um directly 00:08:18.000 --> 00:08:19.510 align:start position:0% state of a prior block um directly through<00:08:18.159> the<00:08:18.280> evm<00:08:18.720> you<00:08:18.840> can't<00:08:19.039> actually<00:08:19.319> do 00:08:19.510 --> 00:08:19.520 align:start position:0% through the evm you can't actually do 00:08:19.520 --> 00:08:22.149 align:start position:0% through the evm you can't actually do that<00:08:19.759> right<00:08:19.879> now<00:08:20.639> um<00:08:21.000> but<00:08:21.280> those<00:08:21.599> near-term 00:08:22.149 --> 00:08:22.159 align:start position:0% that right now um but those near-term 00:08:22.159 --> 00:08:24.189 align:start position:0% that right now um but those near-term benefits<00:08:22.639> is<00:08:22.800> not<00:08:22.960> the<00:08:23.120> reason<00:08:23.520> that<00:08:23.680> this<00:08:23.800> EIP 00:08:24.189 --> 00:08:24.199 align:start position:0% benefits is not the reason that this EIP 00:08:24.199 --> 00:08:26.749 align:start position:0% benefits is not the reason that this EIP was<00:08:24.319> included<00:08:24.680> into<00:08:24.960> pectra<00:08:25.840> um<00:08:26.080> because 00:08:26.749 --> 00:08:26.759 align:start position:0% was included into pectra um because 00:08:26.759 --> 00:08:28.390 align:start position:0% was included into pectra um because clearly<00:08:27.120> those<00:08:27.319> benefits<00:08:27.680> are<00:08:27.800> a<00:08:27.879> little<00:08:28.080> bit 00:08:28.390 --> 00:08:28.400 align:start position:0% clearly those benefits are a little bit 00:08:28.400 --> 00:08:31.430 align:start position:0% clearly those benefits are a little bit iffy<00:08:29.199> um<00:08:29.639> not<00:08:29.840> like<00:08:30.000> super<00:08:30.319> important<00:08:30.759> I<00:08:30.919> guess 00:08:31.430 --> 00:08:31.440 align:start position:0% iffy um not like super important I guess 00:08:31.440 --> 00:08:32.550 align:start position:0% iffy um not like super important I guess but<00:08:31.599> the<00:08:31.680> main<00:08:31.919> reason<00:08:32.200> why<00:08:32.320> that<00:08:32.440> was 00:08:32.550 --> 00:08:32.560 align:start position:0% but the main reason why that was 00:08:32.560 --> 00:08:34.110 align:start position:0% but the main reason why that was included<00:08:32.919> into<00:08:33.159> Petra<00:08:33.560> is<00:08:33.719> because<00:08:33.880> it's<00:08:34.000> a 00:08:34.110 --> 00:08:34.120 align:start position:0% included into Petra is because it's a 00:08:34.120 --> 00:08:36.949 align:start position:0% included into Petra is because it's a prerequisite<00:08:34.680> for<00:08:34.839> veral<00:08:35.560> and<00:08:35.680> veral<00:08:36.360> is<00:08:36.760> uh 00:08:36.949 --> 00:08:36.959 align:start position:0% prerequisite for veral and veral is uh 00:08:36.959 --> 00:08:39.949 align:start position:0% prerequisite for veral and veral is uh this<00:08:37.200> major<00:08:38.080> overhaul<00:08:38.599> to<00:08:38.800> ethereum's<00:08:39.680> uh<00:08:39.839> the 00:08:39.949 --> 00:08:39.959 align:start position:0% this major overhaul to ethereum's uh the 00:08:39.959 --> 00:08:42.350 align:start position:0% this major overhaul to ethereum's uh the structure<00:08:40.320> for<00:08:40.800> uh<00:08:40.919> State<00:08:41.200> data<00:08:41.479> on<00:08:41.640> ethereum 00:08:42.350 --> 00:08:42.360 align:start position:0% structure for uh State data on ethereum 00:08:42.360 --> 00:08:43.670 align:start position:0% structure for uh State data on ethereum that<00:08:42.519> developers<00:08:43.039> had<00:08:43.200> thought<00:08:43.479> that 00:08:43.670 --> 00:08:43.680 align:start position:0% that developers had thought that 00:08:43.680 --> 00:08:45.030 align:start position:0% that developers had thought that transition<00:08:44.120> was<00:08:44.279> going<00:08:44.360> to<00:08:44.560> happen<00:08:44.880> right 00:08:45.030 --> 00:08:45.040 align:start position:0% transition was going to happen right 00:08:45.040 --> 00:08:46.829 align:start position:0% transition was going to happen right after<00:08:45.279> Petra<00:08:45.839> so<00:08:46.040> they're<00:08:46.240> like<00:08:46.399> oh<00:08:46.600> you<00:08:46.680> know 00:08:46.829 --> 00:08:46.839 align:start position:0% after Petra so they're like oh you know 00:08:46.839 --> 00:08:48.310 align:start position:0% after Petra so they're like oh you know faka<00:08:47.440> this<00:08:47.519> is<00:08:47.600> when<00:08:47.760> veral<00:08:48.040> is<00:08:48.080> going<00:08:48.200> to 00:08:48.310 --> 00:08:48.320 align:start position:0% faka this is when veral is going to 00:08:48.320 --> 00:08:49.949 align:start position:0% faka this is when veral is going to happen<00:08:48.640> oh<00:08:48.800> well<00:08:48.959> we<00:08:49.040> need<00:08:49.240> this<00:08:49.399> EAP<00:08:49.800> if<00:08:49.880> we're 00:08:49.949 --> 00:08:49.959 align:start position:0% happen oh well we need this EAP if we're 00:08:49.959 --> 00:08:51.949 align:start position:0% happen oh well we need this EAP if we're going<00:08:50.080> to<00:08:50.160> do<00:08:50.240> that<00:08:50.360> veral<00:08:50.680> transition<00:08:51.680> um<00:08:51.839> but 00:08:51.949 --> 00:08:51.959 align:start position:0% going to do that veral transition um but 00:08:51.959 --> 00:08:53.470 align:start position:0% going to do that veral transition um but turns<00:08:52.240> out<00:08:52.560> as<00:08:52.680> we're<00:08:52.800> going<00:08:52.920> to<00:08:53.040> talk<00:08:53.200> later 00:08:53.470 --> 00:08:53.480 align:start position:0% turns out as we're going to talk later 00:08:53.480 --> 00:08:55.990 align:start position:0% turns out as we're going to talk later in<00:08:53.640> this<00:08:54.160> uh<00:08:54.519> presentation<00:08:55.519> verl<00:08:55.839> is<00:08:55.920> not 00:08:55.990 --> 00:08:56.000 align:start position:0% in this uh presentation verl is not 00:08:56.000 --> 00:08:58.509 align:start position:0% in this uh presentation verl is not going<00:08:56.120> to<00:08:56.240> go<00:08:56.360> into<00:08:56.920> um<00:08:57.240> fusaka<00:08:57.880> or<00:08:58.000> at<00:08:58.120> least 00:08:58.509 --> 00:08:58.519 align:start position:0% going to go into um fusaka or at least 00:08:58.519 --> 00:08:59.870 align:start position:0% going to go into um fusaka or at least that's<00:08:58.680> not<00:08:58.800> what<00:08:58.920> developers<00:08:59.240> are<00:08:59.480> expecting 00:08:59.870 --> 00:08:59.880 align:start position:0% that's not what developers are expecting 00:08:59.880 --> 00:09:03.670 align:start position:0% that's not what developers are expecting right<00:09:00.000> now<00:09:00.880> um<00:09:01.880> they've<00:09:02.160> punted<00:09:02.640> it<00:09:02.760> out<00:09:03.000> to 00:09:03.670 --> 00:09:03.680 align:start position:0% right now um they've punted it out to 00:09:03.680 --> 00:09:05.790 align:start position:0% right now um they've punted it out to another<00:09:04.320> upgrade<00:09:04.920> but<00:09:05.120> it's<00:09:05.279> still<00:09:05.560> there 00:09:05.790 --> 00:09:05.800 align:start position:0% another upgrade but it's still there 00:09:05.800 --> 00:09:08.389 align:start position:0% another upgrade but it's still there developers<00:09:06.320> did<00:09:06.519> implement<00:09:06.920> it<00:09:07.800> um<00:09:08.000> and<00:09:08.120> it'll 00:09:08.389 --> 00:09:08.399 align:start position:0% developers did implement it um and it'll 00:09:08.399 --> 00:09:10.030 align:start position:0% developers did implement it um and it'll have<00:09:08.519> some<00:09:08.640> near-term<00:09:09.120> benefits<00:09:09.600> but<00:09:09.839> the 00:09:10.030 --> 00:09:10.040 align:start position:0% have some near-term benefits but the 00:09:10.040 --> 00:09:11.870 align:start position:0% have some near-term benefits but the primary<00:09:10.440> reason<00:09:10.760> for<00:09:10.920> it<00:09:11.160> is<00:09:11.480> um<00:09:11.640> as<00:09:11.760> a 00:09:11.870 --> 00:09:11.880 align:start position:0% primary reason for it is um as a 00:09:11.880 --> 00:09:14.310 align:start position:0% primary reason for it is um as a prerequisite<00:09:12.440> to<00:09:12.720> to<00:09:12.880> veral<00:09:13.640> um<00:09:13.839> which<00:09:14.200> you 00:09:14.310 --> 00:09:14.320 align:start position:0% prerequisite to to veral um which you 00:09:14.320 --> 00:09:16.750 align:start position:0% prerequisite to to veral um which you know<00:09:15.079> could<00:09:15.240> happen<00:09:15.519> down<00:09:15.680> the<00:09:15.839> road<00:09:16.480> um<00:09:16.640> and 00:09:16.750 --> 00:09:16.760 align:start position:0% know could happen down the road um and 00:09:16.760 --> 00:09:19.389 align:start position:0% know could happen down the road um and if<00:09:16.880> it<00:09:17.040> does<00:09:18.000> you<00:09:18.120> know<00:09:18.560> this<00:09:18.880> this<00:09:19.079> stepping 00:09:19.389 --> 00:09:19.399 align:start position:0% if it does you know this this stepping 00:09:19.399 --> 00:09:20.670 align:start position:0% if it does you know this this stepping stone<00:09:19.720> has<00:09:19.839> already<00:09:20.040> been<00:09:20.160> checked<00:09:20.440> off<00:09:20.560> the 00:09:20.670 --> 00:09:20.680 align:start position:0% stone has already been checked off the 00:09:20.680 --> 00:09:23.470 align:start position:0% stone has already been checked off the list<00:09:21.200> EIP<00:09:21.680> 7685<00:09:22.680> uh<00:09:22.839> general<00:09:23.120> purpose 00:09:23.470 --> 00:09:23.480 align:start position:0% list EIP 7685 uh general purpose 00:09:23.480 --> 00:09:26.069 align:start position:0% list EIP 7685 uh general purpose execution<00:09:23.839> layer<00:09:24.120> requests<00:09:25.000> this<00:09:25.120> is<00:09:25.240> an<00:09:25.399> EIP 00:09:26.069 --> 00:09:26.079 align:start position:0% execution layer requests this is an EIP 00:09:26.079 --> 00:09:27.190 align:start position:0% execution layer requests this is an EIP that<00:09:26.240> doesn't<00:09:26.480> really<00:09:26.680> introduce<00:09:27.079> new 00:09:27.190 --> 00:09:27.200 align:start position:0% that doesn't really introduce new 00:09:27.200 --> 00:09:29.389 align:start position:0% that doesn't really introduce new features<00:09:27.519> to<00:09:27.680> ethereum<00:09:28.279> it's<00:09:28.440> really<00:09:28.640> an<00:09:28.800> EIP 00:09:29.389 --> 00:09:29.399 align:start position:0% features to ethereum it's really an EIP 00:09:29.399 --> 00:09:33.190 align:start position:0% features to ethereum it's really an EIP to<00:09:29.519> support<00:09:30.000> other<00:09:30.279> eips<00:09:31.120> in<00:09:31.320> pectra<00:09:32.320> um<00:09:32.640> so<00:09:32.959> in 00:09:33.190 --> 00:09:33.200 align:start position:0% to support other eips in pectra um so in 00:09:33.200 --> 00:09:35.670 align:start position:0% to support other eips in pectra um so in pectra<00:09:33.600> there's<00:09:33.800> a<00:09:33.880> couple<00:09:34.079> of<00:09:34.680> eips<00:09:35.279> where 00:09:35.670 --> 00:09:35.680 align:start position:0% pectra there's a couple of eips where 00:09:35.680 --> 00:09:37.230 align:start position:0% pectra there's a couple of eips where the<00:09:35.839> execution<00:09:36.240> layer<00:09:36.519> will<00:09:36.640> be<00:09:36.720> able<00:09:36.880> to<00:09:37.000> pass 00:09:37.230 --> 00:09:37.240 align:start position:0% the execution layer will be able to pass 00:09:37.240 --> 00:09:38.750 align:start position:0% the execution layer will be able to pass way<00:09:37.440> more<00:09:37.640> messages<00:09:38.240> different<00:09:38.480> kinds<00:09:38.640> of 00:09:38.750 --> 00:09:38.760 align:start position:0% way more messages different kinds of 00:09:38.760 --> 00:09:40.110 align:start position:0% way more messages different kinds of messages<00:09:39.079> to<00:09:39.200> the<00:09:39.279> consensus<00:09:39.680> layer<00:09:39.920> that<00:09:40.000> it 00:09:40.110 --> 00:09:40.120 align:start position:0% messages to the consensus layer that it 00:09:40.120 --> 00:09:42.150 align:start position:0% messages to the consensus layer that it couldn't<00:09:40.360> before<00:09:41.240> um<00:09:41.440> the<00:09:41.560> execution<00:09:41.920> layer 00:09:42.150 --> 00:09:42.160 align:start position:0% couldn't before um the execution layer 00:09:42.160 --> 00:09:43.430 align:start position:0% couldn't before um the execution layer smart<00:09:42.399> contracts<00:09:42.680> on<00:09:42.800> the<00:09:42.880> execution<00:09:43.240> layer 00:09:43.430 --> 00:09:43.440 align:start position:0% smart contracts on the execution layer 00:09:43.440 --> 00:09:44.829 align:start position:0% smart contracts on the execution layer will<00:09:43.560> be<00:09:43.640> able<00:09:43.800> to<00:09:43.920> trigger<00:09:44.240> like<00:09:44.399> validator 00:09:44.829 --> 00:09:44.839 align:start position:0% will be able to trigger like validator 00:09:44.839 --> 00:09:47.430 align:start position:0% will be able to trigger like validator withdrawals<00:09:45.360> consolidations<00:09:46.320> deposits<00:09:47.320> um 00:09:47.430 --> 00:09:47.440 align:start position:0% withdrawals consolidations deposits um 00:09:47.440 --> 00:09:49.990 align:start position:0% withdrawals consolidations deposits um and<00:09:47.640> rather<00:09:47.880> than<00:09:48.079> implementing<00:09:48.920> these<00:09:49.360> new 00:09:49.990 --> 00:09:50.000 align:start position:0% and rather than implementing these new 00:09:50.000 --> 00:09:51.870 align:start position:0% and rather than implementing these new um<00:09:50.560> messages<00:09:51.079> these<00:09:51.240> new<00:09:51.399> communication 00:09:51.870 --> 00:09:51.880 align:start position:0% um messages these new communication 00:09:51.880 --> 00:09:53.710 align:start position:0% um messages these new communication channels<00:09:52.360> all<00:09:52.560> in<00:09:52.680> a<00:09:52.839> separate<00:09:53.440> kind<00:09:53.560> of 00:09:53.710 --> 00:09:53.720 align:start position:0% channels all in a separate kind of 00:09:53.720 --> 00:09:56.630 align:start position:0% channels all in a separate kind of unique<00:09:54.160> faction<00:09:55.000> fashion<00:09:56.000> uh<00:09:56.120> the 00:09:56.630 --> 00:09:56.640 align:start position:0% unique faction fashion uh the 00:09:56.640 --> 00:10:00.790 align:start position:0% unique faction fashion uh the implementation<00:09:57.640> of<00:09:58.519> these<00:09:59.800> generalized 00:10:00.790 --> 00:10:00.800 align:start position:0% implementation of these generalized 00:10:00.800 --> 00:10:02.430 align:start position:0% implementation of these generalized these<00:10:01.079> execution<00:10:01.560> layer<00:10:01.839> triggerable 00:10:02.430 --> 00:10:02.440 align:start position:0% these execution layer triggerable 00:10:02.440 --> 00:10:04.550 align:start position:0% these execution layer triggerable requests<00:10:03.360> um<00:10:03.480> the<00:10:03.600> implementation<00:10:04.240> of<00:10:04.360> all 00:10:04.550 --> 00:10:04.560 align:start position:0% requests um the implementation of all 00:10:04.560 --> 00:10:05.990 align:start position:0% requests um the implementation of all these<00:10:04.880> requests<00:10:05.240> instead<00:10:05.480> of<00:10:05.560> doing<00:10:05.760> it<00:10:05.880> in 00:10:05.990 --> 00:10:06.000 align:start position:0% these requests instead of doing it in 00:10:06.000 --> 00:10:08.190 align:start position:0% these requests instead of doing it in kind<00:10:06.120> of<00:10:06.240> like<00:10:06.360> a<00:10:06.440> siloed<00:10:06.920> fashion<00:10:07.760> why<00:10:07.959> not 00:10:08.190 --> 00:10:08.200 align:start position:0% kind of like a siloed fashion why not 00:10:08.200 --> 00:10:09.870 align:start position:0% kind of like a siloed fashion why not create<00:10:08.480> like<00:10:08.560> a<00:10:08.720> generalized<00:10:09.279> structure<00:10:09.720> a 00:10:09.870 --> 00:10:09.880 align:start position:0% create like a generalized structure a 00:10:09.880 --> 00:10:13.030 align:start position:0% create like a generalized structure a generalized<00:10:10.440> bus<00:10:10.959> to<00:10:11.240> house<00:10:11.839> these<00:10:12.079> requests 00:10:13.030 --> 00:10:13.040 align:start position:0% generalized bus to house these requests 00:10:13.040 --> 00:10:14.870 align:start position:0% generalized bus to house these requests um<00:10:13.160> it<00:10:13.200> will<00:10:13.360> be<00:10:13.519> easier<00:10:13.800> to<00:10:14.000> test<00:10:14.399> easier<00:10:14.720> to 00:10:14.870 --> 00:10:14.880 align:start position:0% um it will be easier to test easier to 00:10:14.880 --> 00:10:16.910 align:start position:0% um it will be easier to test easier to implement<00:10:15.360> across<00:10:15.720> clients<00:10:16.160> easier<00:10:16.480> to<00:10:16.800> kind 00:10:16.910 --> 00:10:16.920 align:start position:0% implement across clients easier to kind 00:10:16.920 --> 00:10:18.590 align:start position:0% implement across clients easier to kind of<00:10:17.040> standardize<00:10:17.720> especially<00:10:18.040> if<00:10:18.200> developers 00:10:18.590 --> 00:10:18.600 align:start position:0% of standardize especially if developers 00:10:18.600 --> 00:10:20.310 align:start position:0% of standardize especially if developers want<00:10:18.720> to<00:10:18.839> introduce<00:10:19.279> new<00:10:19.519> types<00:10:19.760> of<00:10:19.920> execution 00:10:20.310 --> 00:10:20.320 align:start position:0% want to introduce new types of execution 00:10:20.320 --> 00:10:22.590 align:start position:0% want to introduce new types of execution layer<00:10:20.560> triggerable<00:10:21.040> requests<00:10:21.760> so<00:10:22.120> G 00:10:22.590 --> 00:10:22.600 align:start position:0% layer triggerable requests so G 00:10:22.600 --> 00:10:25.590 align:start position:0% layer triggerable requests so G developer<00:10:23.279> um<00:10:23.440> like<00:10:23.839> client<00:10:24.839> he<00:10:24.959> was<00:10:25.160> like<00:10:25.519> I 00:10:25.590 --> 00:10:25.600 align:start position:0% developer um like client he was like I 00:10:25.600 --> 00:10:27.389 align:start position:0% developer um like client he was like I think<00:10:25.760> this<00:10:25.839> would<00:10:25.959> be<00:10:26.079> a<00:10:26.160> good<00:10:26.320> EIP<00:10:26.760> to<00:10:26.959> add 00:10:27.389 --> 00:10:27.399 align:start position:0% think this would be a good EIP to add 00:10:27.399 --> 00:10:28.790 align:start position:0% think this would be a good EIP to add once<00:10:27.640> developers<00:10:28.040> started<00:10:28.360> implementing 00:10:28.790 --> 00:10:28.800 align:start position:0% once developers started implementing 00:10:28.800 --> 00:10:30.470 align:start position:0% once developers started implementing those<00:10:28.920> other<00:10:29.079> e<00:10:29.560> are<00:10:29.680> like<00:10:29.839> oh<00:10:30.079> actually<00:10:30.399> this 00:10:30.470 --> 00:10:30.480 align:start position:0% those other e are like oh actually this 00:10:30.480 --> 00:10:32.430 align:start position:0% those other e are like oh actually this is<00:10:30.640> something<00:10:30.920> that<00:10:31.040> would<00:10:31.160> be<00:10:31.320> pretty<00:10:31.560> useful 00:10:32.430 --> 00:10:32.440 align:start position:0% is something that would be pretty useful 00:10:32.440 --> 00:10:35.629 align:start position:0% is something that would be pretty useful um<00:10:32.680> so<00:10:33.200> that's<00:10:33.399> why<00:10:33.640> EIP<00:10:34.040> 7685<00:10:34.839> is<00:10:34.959> in<00:10:35.120> there<00:10:35.519> um 00:10:35.629 --> 00:10:35.639 align:start position:0% um so that's why EIP 7685 is in there um 00:10:35.639 --> 00:10:38.590 align:start position:0% um so that's why EIP 7685 is in there um and<00:10:35.839> EIP<00:10:36.200> to<00:10:36.360> support<00:10:36.639> the<00:10:36.760> other<00:10:37.079> eips<00:10:38.079> uh<00:10:38.200> e 00:10:38.590 --> 00:10:38.600 align:start position:0% and EIP to support the other eips uh e 00:10:38.600 --> 00:10:40.710 align:start position:0% and EIP to support the other eips uh e 772<00:10:39.440> this<00:10:39.560> one's<00:10:40.079> kind<00:10:40.200> of<00:10:40.360> I<00:10:40.480> guess<00:10:40.600> an 00:10:40.710 --> 00:10:40.720 align:start position:0% 772 this one's kind of I guess an 00:10:40.720 --> 00:10:43.150 align:start position:0% 772 this one's kind of I guess an exciting<00:10:41.079> one<00:10:41.880> um<00:10:42.079> a<00:10:42.200> new<00:10:42.399> transaction<00:10:42.920> type 00:10:43.150 --> 00:10:43.160 align:start position:0% exciting one um a new transaction type 00:10:43.160 --> 00:10:44.670 align:start position:0% exciting one um a new transaction type is<00:10:43.279> coming<00:10:43.519> into<00:10:43.720> ethereum<00:10:44.360> and<00:10:44.519> this 00:10:44.670 --> 00:10:44.680 align:start position:0% is coming into ethereum and this 00:10:44.680 --> 00:10:46.710 align:start position:0% is coming into ethereum and this transaction<00:10:45.160> type<00:10:45.480> is<00:10:45.639> going<00:10:45.800> to<00:10:46.040> temporarily 00:10:46.710 --> 00:10:46.720 align:start position:0% transaction type is going to temporarily 00:10:46.720 --> 00:10:48.790 align:start position:0% transaction type is going to temporarily allow<00:10:47.000> a<00:10:47.079> user<00:10:47.360> controlled<00:10:47.720> account<00:10:47.920> an<00:10:48.120> eoa 00:10:48.790 --> 00:10:48.800 align:start position:0% allow a user controlled account an eoa 00:10:48.800 --> 00:10:50.829 align:start position:0% allow a user controlled account an eoa externally<00:10:49.160> owned<00:10:49.480> account<00:10:50.200> um<00:10:50.360> to<00:10:50.680> have 00:10:50.829 --> 00:10:50.839 align:start position:0% externally owned account um to have 00:10:50.839 --> 00:10:52.990 align:start position:0% externally owned account um to have greater<00:10:51.120> flexibility<00:10:51.760> and<00:10:51.880> enable<00:10:52.240> features 00:10:52.990 --> 00:10:53.000 align:start position:0% greater flexibility and enable features 00:10:53.000 --> 00:10:55.389 align:start position:0% greater flexibility and enable features like<00:10:53.639> what<00:10:53.800> some<00:10:54.160> that<00:10:54.440> I<00:10:54.600> think<00:10:54.800> many<00:10:55.200> people 00:10:55.389 --> 00:10:55.399 align:start position:0% like what some that I think many people 00:10:55.399 --> 00:10:56.590 align:start position:0% like what some that I think many people in<00:10:55.480> the<00:10:55.600> audience<00:10:55.959> have<00:10:56.079> been<00:10:56.200> waiting<00:10:56.399> for 00:10:56.590 --> 00:10:56.600 align:start position:0% in the audience have been waiting for 00:10:56.600 --> 00:10:59.949 align:start position:0% in the audience have been waiting for for<00:10:56.720> a<00:10:56.880> while<00:10:57.560> um<00:10:57.680> to<00:10:57.920> enable<00:10:58.639> EAS<00:10:59.480> to<00:10:59.720> have 00:10:59.949 --> 00:10:59.959 align:start position:0% for a while um to enable EAS to have 00:10:59.959 --> 00:11:01.470 align:start position:0% for a while um to enable EAS to have features<00:11:00.399> like<00:11:00.600> transaction<00:11:01.079> batching 00:11:01.470 --> 00:11:01.480 align:start position:0% features like transaction batching 00:11:01.480 --> 00:11:02.910 align:start position:0% features like transaction batching sponsored<00:11:01.880> transactions<00:11:02.600> conditional 00:11:02.910 --> 00:11:02.920 align:start position:0% sponsored transactions conditional 00:11:02.920 --> 00:11:05.069 align:start position:0% sponsored transactions conditional transactions<00:11:03.560> delegated<00:11:04.040> security<00:11:04.839> pretty 00:11:05.069 --> 00:11:05.079 align:start position:0% transactions delegated security pretty 00:11:05.079 --> 00:11:06.790 align:start position:0% transactions delegated security pretty cool<00:11:05.320> stuff<00:11:05.760> like<00:11:05.920> you're<00:11:06.200> thinking<00:11:06.519> oh<00:11:06.639> my 00:11:06.790 --> 00:11:06.800 align:start position:0% cool stuff like you're thinking oh my 00:11:06.800 --> 00:11:08.110 align:start position:0% cool stuff like you're thinking oh my gosh<00:11:07.040> is<00:11:07.279> this<00:11:07.440> like<00:11:07.560> the<00:11:07.720> account 00:11:08.110 --> 00:11:08.120 align:start position:0% gosh is this like the account 00:11:08.120 --> 00:11:10.430 align:start position:0% gosh is this like the account abstraction<00:11:09.120> Vision<00:11:09.680> coming<00:11:09.959> alive<00:11:10.279> on 00:11:10.430 --> 00:11:10.440 align:start position:0% abstraction Vision coming alive on 00:11:10.440 --> 00:11:13.590 align:start position:0% abstraction Vision coming alive on ethereum<00:11:11.079> no<00:11:11.240> it's<00:11:11.399> not<00:11:11.680> it's<00:11:11.800> a<00:11:11.920> baby<00:11:12.200> step<00:11:12.720> um 00:11:13.590 --> 00:11:13.600 align:start position:0% ethereum no it's not it's a baby step um 00:11:13.600 --> 00:11:15.470 align:start position:0% ethereum no it's not it's a baby step um so<00:11:13.800> it's<00:11:14.000> kind<00:11:14.120> of<00:11:14.279> like<00:11:14.360> a<00:11:14.480> baby<00:11:14.760> step<00:11:15.040> to 00:11:15.470 --> 00:11:15.480 align:start position:0% so it's kind of like a baby step to 00:11:15.480 --> 00:11:17.670 align:start position:0% so it's kind of like a baby step to seeing<00:11:16.040> how<00:11:16.519> um<00:11:16.680> this<00:11:16.760> will<00:11:16.920> improve<00:11:17.240> the<00:11:17.320> user 00:11:17.670 --> 00:11:17.680 align:start position:0% seeing how um this will improve the user 00:11:17.680 --> 00:11:20.350 align:start position:0% seeing how um this will improve the user experience<00:11:18.560> um<00:11:18.680> it<00:11:18.800> is<00:11:19.000> cool<00:11:19.440> that<00:11:19.959> um<00:11:20.240> you 00:11:20.350 --> 00:11:20.360 align:start position:0% experience um it is cool that um you 00:11:20.360 --> 00:11:21.670 align:start position:0% experience um it is cool that um you know<00:11:20.639> some<00:11:20.920> kind<00:11:21.079> of<00:11:21.240> temporary 00:11:21.670 --> 00:11:21.680 align:start position:0% know some kind of temporary 00:11:21.680 --> 00:11:24.150 align:start position:0% know some kind of temporary functionality<00:11:22.480> will<00:11:23.240> um<00:11:23.720> that<00:11:23.839> you'll<00:11:24.040> be 00:11:24.150 --> 00:11:24.160 align:start position:0% functionality will um that you'll be 00:11:24.160 --> 00:11:25.910 align:start position:0% functionality will um that you'll be able<00:11:24.360> to<00:11:24.760> create<00:11:25.040> some<00:11:25.240> kind<00:11:25.360> of<00:11:25.480> temporary 00:11:25.910 --> 00:11:25.920 align:start position:0% able to create some kind of temporary 00:11:25.920 --> 00:11:28.710 align:start position:0% able to create some kind of temporary new<00:11:26.320> um<00:11:26.480> flexibility<00:11:27.120> into<00:11:27.440> eoas<00:11:28.440> um<00:11:28.600> but 00:11:28.710 --> 00:11:28.720 align:start position:0% new um flexibility into eoas um but 00:11:28.720 --> 00:11:32.389 align:start position:0% new um flexibility into eoas um but really<00:11:28.880> it's<00:11:29.000> an<00:11:29.320> early<00:11:29.680> step<00:11:30.240> um<00:11:30.480> to<00:11:31.000> see<00:11:32.000> what 00:11:32.389 --> 00:11:32.399 align:start position:0% really it's an early step um to see what 00:11:32.399 --> 00:11:35.069 align:start position:0% really it's an early step um to see what the<00:11:32.920> real<00:11:33.240> road<00:11:33.560> map<00:11:33.839> to<00:11:34.160> True<00:11:34.480> native<00:11:34.839> account 00:11:35.069 --> 00:11:35.079 align:start position:0% the real road map to True native account 00:11:35.079 --> 00:11:37.069 align:start position:0% the real road map to True native account abstraction<00:11:35.560> could<00:11:35.680> look<00:11:35.839> like<00:11:35.959> on<00:11:36.079> ethereum 00:11:37.069 --> 00:11:37.079 align:start position:0% abstraction could look like on ethereum 00:11:37.079 --> 00:11:39.150 align:start position:0% abstraction could look like on ethereum um<00:11:37.360> this<00:11:37.519> had<00:11:37.760> quite<00:11:37.920> a<00:11:38.000> bit<00:11:38.160> of<00:11:38.320> debate<00:11:38.839> um<00:11:39.040> in 00:11:39.150 --> 00:11:39.160 align:start position:0% um this had quite a bit of debate um in 00:11:39.160 --> 00:11:40.790 align:start position:0% um this had quite a bit of debate um in terms<00:11:39.399> of<00:11:39.639> how<00:11:39.880> developers<00:11:40.320> should<00:11:40.480> take<00:11:40.639> that 00:11:40.790 --> 00:11:40.800 align:start position:0% terms of how developers should take that 00:11:40.800 --> 00:11:43.150 align:start position:0% terms of how developers should take that first<00:11:41.040> step<00:11:41.880> um<00:11:42.040> a<00:11:42.120> lot<00:11:42.240> of<00:11:42.360> controversy<00:11:42.959> of 00:11:43.150 --> 00:11:43.160 align:start position:0% first step um a lot of controversy of 00:11:43.160 --> 00:11:45.190 align:start position:0% first step um a lot of controversy of this<00:11:43.240> one<00:11:43.480> getting<00:11:43.720> in<00:11:43.920> and<00:11:44.079> its<00:11:44.320> design<00:11:45.040> but 00:11:45.190 --> 00:11:45.200 align:start position:0% this one getting in and its design but 00:11:45.200 --> 00:11:47.750 align:start position:0% this one getting in and its design but it's<00:11:45.360> in<00:11:45.600> there<00:11:45.959> and<00:11:46.200> I'm<00:11:46.399> pretty<00:11:46.560> sure<00:11:47.440> um<00:11:47.600> of 00:11:47.750 --> 00:11:47.760 align:start position:0% it's in there and I'm pretty sure um of 00:11:47.760 --> 00:11:49.509 align:start position:0% it's in there and I'm pretty sure um of all<00:11:47.880> the<00:11:48.040> eips<00:11:48.560> that<00:11:48.680> developers<00:11:49.120> want<00:11:49.279> you<00:11:49.360> to 00:11:49.509 --> 00:11:49.519 align:start position:0% all the eips that developers want you to 00:11:49.519 --> 00:11:50.829 align:start position:0% all the eips that developers want you to interact<00:11:49.920> with<00:11:50.040> and<00:11:50.200> kind<00:11:50.279> of<00:11:50.399> test<00:11:50.639> on<00:11:50.760> the 00:11:50.829 --> 00:11:50.839 align:start position:0% interact with and kind of test on the 00:11:50.839 --> 00:11:52.430 align:start position:0% interact with and kind of test on the meong<00:11:51.240> test<00:11:51.440> net<00:11:51.639> this<00:11:51.720> is<00:11:51.880> probably<00:11:52.120> high<00:11:52.279> up 00:11:52.430 --> 00:11:52.440 align:start position:0% meong test net this is probably high up 00:11:52.440 --> 00:11:55.030 align:start position:0% meong test net this is probably high up on<00:11:52.560> the<00:11:52.680> list<00:11:53.160> um<00:11:53.560> you<00:11:53.639> know<00:11:53.880> trying<00:11:54.200> out<00:11:54.920> this 00:11:55.030 --> 00:11:55.040 align:start position:0% on the list um you know trying out this 00:11:55.040 --> 00:11:56.870 align:start position:0% on the list um you know trying out this new<00:11:55.240> transaction<00:11:55.720> type<00:11:56.040> so<00:11:56.519> if<00:11:56.600> you're<00:11:56.720> on 00:11:56.870 --> 00:11:56.880 align:start position:0% new transaction type so if you're on 00:11:56.880 --> 00:11:59.629 align:start position:0% new transaction type so if you're on meong<00:11:57.639> um<00:11:57.760> you<00:11:57.880> know<00:11:58.360> thow<00:11:58.680> developers<00:11:59.000> a<00:11:59.079> bone 00:11:59.629 --> 00:11:59.639 align:start position:0% meong um you know thow developers a bone 00:11:59.639 --> 00:12:00.949 align:start position:0% meong um you know thow developers a bone try<00:11:59.839> it 00:12:00.949 --> 00:12:00.959 align:start position:0% try it 00:12:00.959 --> 00:12:04.310 align:start position:0% try it out<00:12:01.959> there<00:12:02.160> are<00:12:02.760> six<00:12:03.079> others<00:12:03.720> these<00:12:03.880> ones<00:12:04.079> are 00:12:04.310 --> 00:12:04.320 align:start position:0% out there are six others these ones are 00:12:04.320 --> 00:12:06.030 align:start position:0% out there are six others these ones are consensus<00:12:04.760> layer<00:12:05.079> eips<00:12:05.720> and<00:12:05.800> I'm<00:12:05.880> going<00:12:05.959> to 00:12:06.030 --> 00:12:06.040 align:start position:0% consensus layer eips and I'm going to 00:12:06.040 --> 00:12:07.350 align:start position:0% consensus layer eips and I'm going to run<00:12:06.200> through<00:12:06.360> these<00:12:06.560> really<00:12:06.720> quickly<00:12:07.000> because 00:12:07.350 --> 00:12:07.360 align:start position:0% run through these really quickly because 00:12:07.360 --> 00:12:08.829 align:start position:0% run through these really quickly because after<00:12:07.560> me<00:12:07.920> there's<00:12:08.079> going<00:12:08.160> to<00:12:08.240> be<00:12:08.320> some<00:12:08.480> talks 00:12:08.829 --> 00:12:08.839 align:start position:0% after me there's going to be some talks 00:12:08.839 --> 00:12:11.470 align:start position:0% after me there's going to be some talks that<00:12:09.000> go<00:12:09.240> deeper<00:12:09.600> into<00:12:09.839> each<00:12:10.000> of<00:12:10.200> these<00:12:10.480> eips 00:12:11.470 --> 00:12:11.480 align:start position:0% that go deeper into each of these eips 00:12:11.480 --> 00:12:13.509 align:start position:0% that go deeper into each of these eips so<00:12:11.639> this<00:12:11.720> is<00:12:11.920> just<00:12:12.279> you<00:12:12.399> know<00:12:12.959> summary 00:12:13.509 --> 00:12:13.519 align:start position:0% so this is just you know summary 00:12:13.519 --> 00:12:16.949 align:start position:0% so this is just you know summary overview<00:12:14.519> um<00:12:14.680> EIP<00:12:15.040> 7742<00:12:15.959> uncouple<00:12:16.480> blob<00:12:16.760> count 00:12:16.949 --> 00:12:16.959 align:start position:0% overview um EIP 7742 uncouple blob count 00:12:16.959 --> 00:12:18.389 align:start position:0% overview um EIP 7742 uncouple blob count between<00:12:17.199> the<00:12:17.279> consensus<00:12:17.680> layer<00:12:18.040> and<00:12:18.199> the 00:12:18.389 --> 00:12:18.399 align:start position:0% between the consensus layer and the 00:12:18.399 --> 00:12:21.350 align:start position:0% between the consensus layer and the execution<00:12:19.199> layer<00:12:20.199> this<00:12:20.360> one<00:12:20.800> is<00:12:20.959> the<00:12:21.120> most 00:12:21.350 --> 00:12:21.360 align:start position:0% execution layer this one is the most 00:12:21.360 --> 00:12:24.470 align:start position:0% execution layer this one is the most recent<00:12:21.800> EIP<00:12:22.279> to<00:12:22.399> be<00:12:22.560> included<00:12:22.920> into<00:12:23.199> Petra<00:12:23.920> um 00:12:24.470 --> 00:12:24.480 align:start position:0% recent EIP to be included into Petra um 00:12:24.480 --> 00:12:26.990 align:start position:0% recent EIP to be included into Petra um developers<00:12:25.480> like<00:12:25.600> I<00:12:25.760> said<00:12:26.360> um<00:12:26.680> was 00:12:26.990 --> 00:12:27.000 align:start position:0% developers like I said um was 00:12:27.000 --> 00:12:28.509 align:start position:0% developers like I said um was considering<00:12:27.560> should<00:12:27.760> we<00:12:27.920> include<00:12:28.320> an 00:12:28.509 --> 00:12:28.519 align:start position:0% considering should we include an 00:12:28.519 --> 00:12:31.430 align:start position:0% considering should we include an increase<00:12:28.880> to<00:12:29.040> the<00:12:29.199> blob<00:12:29.639> capacity<00:12:30.639> um<00:12:31.120> and<00:12:31.320> if 00:12:31.430 --> 00:12:31.440 align:start position:0% increase to the blob capacity um and if 00:12:31.440 --> 00:12:32.829 align:start position:0% increase to the blob capacity um and if we're<00:12:31.560> going<00:12:31.680> to<00:12:31.839> do<00:12:32.040> that<00:12:32.399> currently<00:12:32.760> the 00:12:32.829 --> 00:12:32.839 align:start position:0% we're going to do that currently the 00:12:32.839 --> 00:12:34.629 align:start position:0% we're going to do that currently the blob<00:12:33.120> capacity<00:12:33.519> is<00:12:33.639> hardcoded<00:12:34.279> into<00:12:34.480> the 00:12:34.629 --> 00:12:34.639 align:start position:0% blob capacity is hardcoded into the 00:12:34.639 --> 00:12:36.629 align:start position:0% blob capacity is hardcoded into the execution<00:12:35.040> layer<00:12:35.320> and<00:12:35.440> the<00:12:35.519> consensus<00:12:35.959> layer 00:12:36.629 --> 00:12:36.639 align:start position:0% execution layer and the consensus layer 00:12:36.639 --> 00:12:38.509 align:start position:0% execution layer and the consensus layer and<00:12:36.800> the<00:12:36.920> hard<00:12:37.199> coding<00:12:37.639> of<00:12:37.839> these<00:12:38.079> constants 00:12:38.509 --> 00:12:38.519 align:start position:0% and the hard coding of these constants 00:12:38.519 --> 00:12:39.910 align:start position:0% and the hard coding of these constants are<00:12:38.720> all<00:12:38.959> kind<00:12:39.079> of<00:12:39.199> different<00:12:39.480> in<00:12:39.600> all<00:12:39.760> the 00:12:39.910 --> 00:12:39.920 align:start position:0% are all kind of different in all the 00:12:39.920 --> 00:12:42.509 align:start position:0% are all kind of different in all the clients<00:12:40.920> um<00:12:41.160> and<00:12:41.279> so<00:12:41.519> updating<00:12:42.120> that<00:12:42.240> hard 00:12:42.509 --> 00:12:42.519 align:start position:0% clients um and so updating that hard 00:12:42.519 --> 00:12:44.750 align:start position:0% clients um and so updating that hard coding<00:12:42.800> is<00:12:42.920> not<00:12:43.120> as<00:12:43.320> easy<00:12:43.839> as<00:12:44.199> um<00:12:44.320> some<00:12:44.560> may 00:12:44.750 --> 00:12:44.760 align:start position:0% coding is not as easy as um some may 00:12:44.760 --> 00:12:47.750 align:start position:0% coding is not as easy as um some may think<00:12:45.680> um<00:12:46.000> so<00:12:46.279> creating<00:12:46.639> a<00:12:46.800> mechanism<00:12:47.360> to<00:12:47.600> kind 00:12:47.750 --> 00:12:47.760 align:start position:0% think um so creating a mechanism to kind 00:12:47.760 --> 00:12:50.430 align:start position:0% think um so creating a mechanism to kind of<00:12:48.440> be<00:12:48.600> able<00:12:48.800> to<00:12:49.000> change<00:12:49.399> the<00:12:49.600> blog<00:12:49.959> capacity 00:12:50.430 --> 00:12:50.440 align:start position:0% of be able to change the blog capacity 00:12:50.440 --> 00:12:52.189 align:start position:0% of be able to change the blog capacity and<00:12:50.560> have<00:12:50.680> it<00:12:50.839> dynamically<00:12:51.399> set<00:12:51.959> by<00:12:52.079> the 00:12:52.189 --> 00:12:52.199 align:start position:0% and have it dynamically set by the 00:12:52.199 --> 00:12:54.430 align:start position:0% and have it dynamically set by the consensus<00:12:52.639> layer<00:12:53.440> um<00:12:53.560> will<00:12:53.800> ensure<00:12:54.199> that<00:12:54.320> in 00:12:54.430 --> 00:12:54.440 align:start position:0% consensus layer um will ensure that in 00:12:54.440 --> 00:12:56.509 align:start position:0% consensus layer um will ensure that in the<00:12:54.519> future<00:12:54.880> developers<00:12:55.399> can<00:12:55.680> easily<00:12:56.079> change 00:12:56.509 --> 00:12:56.519 align:start position:0% the future developers can easily change 00:12:56.519 --> 00:12:58.269 align:start position:0% the future developers can easily change the<00:12:56.720> blob<00:12:57.079> capacity<00:12:57.480> of<00:12:57.560> ethereum<00:12:58.040> if<00:12:58.160> they 00:12:58.269 --> 00:12:58.279 align:start position:0% the blob capacity of ethereum if they 00:12:58.279 --> 00:13:01.150 align:start position:0% the blob capacity of ethereum if they want<00:12:58.440> to<00:12:59.000> and<00:12:59.279> and<00:12:59.760> um<00:13:00.240> ensure<00:13:00.680> that<00:13:00.880> that<00:13:01.040> kind 00:13:01.150 --> 00:13:01.160 align:start position:0% want to and and um ensure that that kind 00:13:01.160 --> 00:13:03.069 align:start position:0% want to and and um ensure that that kind of<00:13:01.320> upgrade<00:13:01.880> it<00:13:02.040> only<00:13:02.279> requires<00:13:02.680> consensus 00:13:03.069 --> 00:13:03.079 align:start position:0% of upgrade it only requires consensus 00:13:03.079 --> 00:13:04.509 align:start position:0% of upgrade it only requires consensus layer<00:13:03.320> changes<00:13:03.680> doesn't<00:13:03.920> require<00:13:04.199> a<00:13:04.320> change 00:13:04.509 --> 00:13:04.519 align:start position:0% layer changes doesn't require a change 00:13:04.519 --> 00:13:06.189 align:start position:0% layer changes doesn't require a change to<00:13:04.680> both<00:13:04.839> the<00:13:04.959> execution<00:13:05.360> layer<00:13:05.959> and<00:13:06.079> the 00:13:06.189 --> 00:13:06.199 align:start position:0% to both the execution layer and the 00:13:06.199 --> 00:13:10.430 align:start position:0% to both the execution layer and the consensus<00:13:06.639> layer<00:13:07.800> um<00:13:08.800> so<00:13:09.279> yeah<00:13:09.600> but<00:13:09.800> it's<00:13:10.040> like 00:13:10.430 --> 00:13:10.440 align:start position:0% consensus layer um so yeah but it's like 00:13:10.440 --> 00:13:12.189 align:start position:0% consensus layer um so yeah but it's like heavy<00:13:10.720> work<00:13:11.040> upfront<00:13:11.639> right<00:13:11.800> because<00:13:12.079> the 00:13:12.189 --> 00:13:12.199 align:start position:0% heavy work upfront right because the 00:13:12.199 --> 00:13:14.230 align:start position:0% heavy work upfront right because the mechanism<00:13:12.680> doesn't<00:13:13.000> exist<00:13:13.360> right<00:13:13.519> now<00:13:14.000> once 00:13:14.230 --> 00:13:14.240 align:start position:0% mechanism doesn't exist right now once 00:13:14.240 --> 00:13:16.189 align:start position:0% mechanism doesn't exist right now once the<00:13:14.399> mechanism<00:13:14.880> exists<00:13:15.519> yes<00:13:15.680> it'll<00:13:15.880> be<00:13:16.000> easy 00:13:16.189 --> 00:13:16.199 align:start position:0% the mechanism exists yes it'll be easy 00:13:16.199 --> 00:13:17.670 align:start position:0% the mechanism exists yes it'll be easy to<00:13:16.360> use<00:13:16.560> that<00:13:16.720> mechanism<00:13:17.160> and<00:13:17.279> update<00:13:17.560> the 00:13:17.670 --> 00:13:17.680 align:start position:0% to use that mechanism and update the 00:13:17.680 --> 00:13:18.990 align:start position:0% to use that mechanism and update the blob<00:13:18.040> capacity<00:13:18.399> but<00:13:18.560> right<00:13:18.680> now<00:13:18.839> that 00:13:18.990 --> 00:13:19.000 align:start position:0% blob capacity but right now that 00:13:19.000 --> 00:13:20.230 align:start position:0% blob capacity but right now that mechanism<00:13:19.360> doesn't<00:13:19.639> exist<00:13:19.839> so<00:13:19.920> it<00:13:20.000> takes 00:13:20.230 --> 00:13:20.240 align:start position:0% mechanism doesn't exist so it takes 00:13:20.240 --> 00:13:22.030 align:start position:0% mechanism doesn't exist so it takes quite<00:13:20.360> a<00:13:20.440> bit<00:13:20.560> of<00:13:20.680> work<00:13:21.320> um<00:13:21.480> which<00:13:21.600> is<00:13:21.720> why<00:13:21.880> when 00:13:22.030 --> 00:13:22.040 align:start position:0% quite a bit of work um which is why when 00:13:22.040 --> 00:13:23.269 align:start position:0% quite a bit of work um which is why when developers<00:13:22.440> were<00:13:22.600> like<00:13:22.760> look<00:13:22.920> if<00:13:23.040> we're 00:13:23.269 --> 00:13:23.279 align:start position:0% developers were like look if we're 00:13:23.279 --> 00:13:24.670 align:start position:0% developers were like look if we're really<00:13:23.519> serious<00:13:23.920> about<00:13:24.160> including<00:13:24.560> an 00:13:24.670 --> 00:13:24.680 align:start position:0% really serious about including an 00:13:24.680 --> 00:13:27.509 align:start position:0% really serious about including an increase<00:13:25.040> the<00:13:25.160> blob<00:13:25.480> capacity<00:13:26.360> in<00:13:26.680> pectra<00:13:27.440> we 00:13:27.509 --> 00:13:27.519 align:start position:0% increase the blob capacity in pectra we 00:13:27.519 --> 00:13:28.670 align:start position:0% increase the blob capacity in pectra we should<00:13:27.800> really<00:13:28.000> get<00:13:28.120> started<00:13:28.440> on<00:13:28.560> this 00:13:28.670 --> 00:13:28.680 align:start position:0% should really get started on this 00:13:28.680 --> 00:13:30.550 align:start position:0% should really get started on this mechanism<00:13:29.160> them<00:13:29.279> sooner<00:13:29.600> rather<00:13:29.800> than<00:13:29.959> later 00:13:30.550 --> 00:13:30.560 align:start position:0% mechanism them sooner rather than later 00:13:30.560 --> 00:13:32.470 align:start position:0% mechanism them sooner rather than later and<00:13:30.639> so<00:13:30.839> developers<00:13:31.240> were<00:13:31.480> like<00:13:31.720> actually<00:13:32.160> yes 00:13:32.470 --> 00:13:32.480 align:start position:0% and so developers were like actually yes 00:13:32.480 --> 00:13:33.990 align:start position:0% and so developers were like actually yes other<00:13:32.639> developers<00:13:33.040> on<00:13:33.160> the<00:13:33.279> call<00:13:33.440> and<00:13:33.560> the<00:13:33.639> ACD 00:13:33.990 --> 00:13:34.000 align:start position:0% other developers on the call and the ACD 00:13:34.000 --> 00:13:35.350 align:start position:0% other developers on the call and the ACD calls<00:13:34.279> I'm<00:13:34.399> talking<00:13:34.600> about<00:13:34.880> they're<00:13:35.040> like<00:13:35.160> you 00:13:35.350 --> 00:13:35.360 align:start position:0% calls I'm talking about they're like you 00:13:35.360 --> 00:13:36.509 align:start position:0% calls I'm talking about they're like you what<00:13:35.519> that's<00:13:35.680> probably<00:13:35.880> a<00:13:36.000> good<00:13:36.120> idea<00:13:36.399> so 00:13:36.509 --> 00:13:36.519 align:start position:0% what that's probably a good idea so 00:13:36.519 --> 00:13:39.189 align:start position:0% what that's probably a good idea so that's<00:13:36.639> why<00:13:36.760> it<00:13:36.800> was<00:13:36.959> included<00:13:37.959> but<00:13:38.440> the<00:13:38.720> last 00:13:39.189 --> 00:13:39.199 align:start position:0% that's why it was included but the last 00:13:39.199 --> 00:13:42.069 align:start position:0% that's why it was included but the last little<00:13:39.399> lineup<00:13:39.880> here<00:13:40.480> TBD<00:13:41.480> that's<00:13:41.639> the<00:13:41.760> blob 00:13:42.069 --> 00:13:42.079 align:start position:0% little lineup here TBD that's the blob 00:13:42.079 --> 00:13:43.710 align:start position:0% little lineup here TBD that's the blob capacity<00:13:42.440> increase<00:13:42.800> developers<00:13:43.279> have<00:13:43.440> not 00:13:43.710 --> 00:13:43.720 align:start position:0% capacity increase developers have not 00:13:43.720 --> 00:13:45.629 align:start position:0% capacity increase developers have not decided<00:13:44.320> on<00:13:44.600> what<00:13:45.079> specifically<00:13:45.519> that 00:13:45.629 --> 00:13:45.639 align:start position:0% decided on what specifically that 00:13:45.639 --> 00:13:48.069 align:start position:0% decided on what specifically that increase<00:13:45.959> is<00:13:46.040> going<00:13:46.160> to<00:13:46.279> be<00:13:46.480> quite<00:13:46.880> yet<00:13:47.880> um 00:13:48.069 --> 00:13:48.079 align:start position:0% increase is going to be quite yet um 00:13:48.079 --> 00:13:49.829 align:start position:0% increase is going to be quite yet um let's<00:13:48.880> dive<00:13:49.079> deeper<00:13:49.360> into<00:13:49.519> some<00:13:49.600> of<00:13:49.720> these 00:13:49.829 --> 00:13:49.839 align:start position:0% let's dive deeper into some of these 00:13:49.839 --> 00:13:52.550 align:start position:0% let's dive deeper into some of these other<00:13:50.000> ones<00:13:50.160> EIP<00:13:50.639> 6110<00:13:51.639> Spide<00:13:52.040> to<00:13:52.199> validator 00:13:52.550 --> 00:13:52.560 align:start position:0% other ones EIP 6110 Spide to validator 00:13:52.560 --> 00:13:54.590 align:start position:0% other ones EIP 6110 Spide to validator deposits<00:13:52.880> on<00:13:53.079> chain<00:13:53.639> um<00:13:53.920> Vall<00:13:54.320> you<00:13:54.399> know<00:13:54.519> he 00:13:54.590 --> 00:13:54.600 align:start position:0% deposits on chain um Vall you know he 00:13:54.600 --> 00:13:56.189 align:start position:0% deposits on chain um Vall you know he was<00:13:54.720> like<00:13:54.880> woohoo<00:13:55.279> you<00:13:55.399> know<00:13:55.639> then<00:13:55.880> the 00:13:56.189 --> 00:13:56.199 align:start position:0% was like woohoo you know then the 00:13:56.199 --> 00:13:58.430 align:start position:0% was like woohoo you know then the mainstage<00:13:56.759> talk<00:13:57.079> like<00:13:57.240> the<00:13:57.360> merge<00:13:57.680> happened 00:13:58.430 --> 00:13:58.440 align:start position:0% mainstage talk like the merge happened 00:13:58.440 --> 00:14:00.310 align:start position:0% mainstage talk like the merge happened um<00:13:58.560> the<00:13:58.680> merge<00:13:59.240> happen<00:13:59.480> and<00:13:59.600> ethereum<00:14:00.040> is<00:14:00.160> more 00:14:00.310 --> 00:14:00.320 align:start position:0% um the merge happen and ethereum is more 00:14:00.320 --> 00:14:02.509 align:start position:0% um the merge happen and ethereum is more mature<00:14:00.639> as<00:14:00.759> a<00:14:00.880> proof<00:14:01.079> of<00:14:01.480> stake<00:14:01.800> blockchain 00:14:02.509 --> 00:14:02.519 align:start position:0% mature as a proof of stake blockchain 00:14:02.519 --> 00:14:03.910 align:start position:0% mature as a proof of stake blockchain there<00:14:02.600> are<00:14:02.759> certain<00:14:03.000> security<00:14:03.360> assumptions 00:14:03.910 --> 00:14:03.920 align:start position:0% there are certain security assumptions 00:14:03.920 --> 00:14:05.910 align:start position:0% there are certain security assumptions that<00:14:04.000> can<00:14:04.079> be<00:14:04.199> relaxed<00:14:04.680> now<00:14:05.360> um<00:14:05.560> and<00:14:05.680> one<00:14:05.800> of 00:14:05.910 --> 00:14:05.920 align:start position:0% that can be relaxed now um and one of 00:14:05.920 --> 00:14:07.269 align:start position:0% that can be relaxed now um and one of those<00:14:06.079> security<00:14:06.399> assumptions<00:14:06.920> is<00:14:07.120> an 00:14:07.269 --> 00:14:07.279 align:start position:0% those security assumptions is an 00:14:07.279 --> 00:14:09.069 align:start position:0% those security assumptions is an additional<00:14:07.600> round<00:14:07.800> of<00:14:07.959> voting<00:14:08.839> um<00:14:08.959> that 00:14:09.069 --> 00:14:09.079 align:start position:0% additional round of voting um that 00:14:09.079 --> 00:14:11.470 align:start position:0% additional round of voting um that happens<00:14:09.399> every<00:14:09.639> time<00:14:09.880> you<00:14:10.160> deposit<00:14:10.639> a<00:14:10.759> 32<00:14:11.199> eth 00:14:11.470 --> 00:14:11.480 align:start position:0% happens every time you deposit a 32 eth 00:14:11.480 --> 00:14:13.350 align:start position:0% happens every time you deposit a 32 eth on<00:14:11.680> the<00:14:11.839> ethereum<00:14:12.199> 2.0<00:14:12.639> deposit<00:14:12.959> contract 00:14:13.350 --> 00:14:13.360 align:start position:0% on the ethereum 2.0 deposit contract 00:14:13.360 --> 00:14:14.749 align:start position:0% on the ethereum 2.0 deposit contract there's<00:14:13.519> an<00:14:13.680> additional<00:14:14.040> round<00:14:14.279> of<00:14:14.440> voting 00:14:14.749 --> 00:14:14.759 align:start position:0% there's an additional round of voting 00:14:14.759 --> 00:14:16.389 align:start position:0% there's an additional round of voting that<00:14:14.880> happens<00:14:15.160> on<00:14:15.240> the<00:14:15.360> consensus<00:14:15.720> layer<00:14:16.040> side 00:14:16.389 --> 00:14:16.399 align:start position:0% that happens on the consensus layer side 00:14:16.399 --> 00:14:18.870 align:start position:0% that happens on the consensus layer side to<00:14:16.560> verify<00:14:16.959> those<00:14:17.199> deposits<00:14:18.120> um<00:14:18.240> this<00:14:18.399> EIP 00:14:18.870 --> 00:14:18.880 align:start position:0% to verify those deposits um this EIP 00:14:18.880 --> 00:14:21.470 align:start position:0% to verify those deposits um this EIP removes<00:14:19.839> that<00:14:20.480> additional<00:14:20.839> round<00:14:21.120> of<00:14:21.240> voting 00:14:21.470 --> 00:14:21.480 align:start position:0% removes that additional round of voting 00:14:21.480 --> 00:14:24.110 align:start position:0% removes that additional round of voting on<00:14:21.600> the<00:14:21.680> consensus<00:14:22.079> layer<00:14:22.399> side<00:14:23.040> um<00:14:23.720> ensures 00:14:24.110 --> 00:14:24.120 align:start position:0% on the consensus layer side um ensures 00:14:24.120 --> 00:14:25.749 align:start position:0% on the consensus layer side um ensures all<00:14:24.240> the<00:14:24.399> deposit<00:14:24.880> validation<00:14:25.360> happens<00:14:25.639> on 00:14:25.749 --> 00:14:25.759 align:start position:0% all the deposit validation happens on 00:14:25.759 --> 00:14:28.430 align:start position:0% all the deposit validation happens on the<00:14:25.880> execution<00:14:26.320> layer<00:14:27.160> um<00:14:27.440> this<00:14:27.600> has<00:14:27.800> some<00:14:28.279> uh 00:14:28.430 --> 00:14:28.440 align:start position:0% the execution layer um this has some uh 00:14:28.440 --> 00:14:30.590 align:start position:0% the execution layer um this has some uh benefits<00:14:28.800> for<00:14:29.160> validator<00:14:29.560> ux<00:14:29.920> it<00:14:30.000> will<00:14:30.199> shrink 00:14:30.590 --> 00:14:30.600 align:start position:0% benefits for validator ux it will shrink 00:14:30.600 --> 00:14:33.030 align:start position:0% benefits for validator ux it will shrink the<00:14:30.759> time<00:14:31.600> um<00:14:31.800> between<00:14:32.199> when<00:14:32.440> you<00:14:32.680> deposit 00:14:33.030 --> 00:14:33.040 align:start position:0% the time um between when you deposit 00:14:33.040 --> 00:14:34.629 align:start position:0% the time um between when you deposit your<00:14:33.160> 32<00:14:33.600> eth<00:14:33.880> and<00:14:34.000> when<00:14:34.120> you<00:14:34.240> see<00:14:34.480> the 00:14:34.629 --> 00:14:34.639 align:start position:0% your 32 eth and when you see the 00:14:34.639 --> 00:14:36.749 align:start position:0% your 32 eth and when you see the validator<00:14:35.199> actually<00:14:35.720> be<00:14:35.959> activated<00:14:36.480> on<00:14:36.639> the 00:14:36.749 --> 00:14:36.759 align:start position:0% validator actually be activated on the 00:14:36.759 --> 00:14:40.710 align:start position:0% validator actually be activated on the beacon<00:14:37.079> chain<00:14:38.040> um<00:14:38.240> EIP<00:14:39.160> 70002<00:14:40.160> uh<00:14:40.320> execution 00:14:40.710 --> 00:14:40.720 align:start position:0% beacon chain um EIP 70002 uh execution 00:14:40.720 --> 00:14:43.230 align:start position:0% beacon chain um EIP 70002 uh execution layer<00:14:41.000> triggerable<00:14:41.920> withdrawals<00:14:42.920> this<00:14:43.040> is 00:14:43.230 --> 00:14:43.240 align:start position:0% layer triggerable withdrawals this is 00:14:43.240 --> 00:14:45.710 align:start position:0% layer triggerable withdrawals this is very<00:14:43.440> good<00:14:43.600> for<00:14:43.959> sticking<00:14:44.360> pools<00:14:45.000> um<00:14:45.560> right 00:14:45.710 --> 00:14:45.720 align:start position:0% very good for sticking pools um right 00:14:45.720 --> 00:14:48.189 align:start position:0% very good for sticking pools um right now<00:14:46.680> validators<00:14:47.279> if<00:14:47.399> you<00:14:47.480> want<00:14:47.600> to<00:14:47.759> fully 00:14:48.189 --> 00:14:48.199 align:start position:0% now validators if you want to fully 00:14:48.199 --> 00:14:51.310 align:start position:0% now validators if you want to fully withdraw<00:14:48.639> a<00:14:48.839> validator<00:14:49.839> the<00:14:50.040> node<00:14:50.440> operator 00:14:51.310 --> 00:14:51.320 align:start position:0% withdraw a validator the node operator 00:14:51.320 --> 00:14:52.829 align:start position:0% withdraw a validator the node operator that<00:14:51.480> controls<00:14:52.120> that<00:14:52.279> operates<00:14:52.720> that 00:14:52.829 --> 00:14:52.839 align:start position:0% that controls that operates that 00:14:52.839 --> 00:14:56.069 align:start position:0% that controls that operates that validator<00:14:53.399> needs<00:14:53.720> to<00:14:54.320> um<00:14:54.920> withdraw<00:14:55.720> they<00:14:55.880> need 00:14:56.069 --> 00:14:56.079 align:start position:0% validator needs to um withdraw they need 00:14:56.079 --> 00:14:59.189 align:start position:0% validator needs to um withdraw they need to<00:14:56.600> uh<00:14:56.720> use<00:14:56.920> their<00:14:57.120> withdrawal<00:14:57.680> key<00:14:58.320> to<00:14:58.600> fully 00:14:59.189 --> 00:14:59.199 align:start position:0% to uh use their withdrawal key to fully 00:14:59.199 --> 00:15:01.710 align:start position:0% to uh use their withdrawal key to fully exit<00:14:59.600> the<00:14:59.920> validator<00:15:00.920> um<00:15:01.199> but<00:15:01.360> through<00:15:01.560> the 00:15:01.710 --> 00:15:01.720 align:start position:0% exit the validator um but through the 00:15:01.720 --> 00:15:04.870 align:start position:0% exit the validator um but through the CIP<00:15:02.639> smart<00:15:03.040> contracts<00:15:03.920> will<00:15:04.079> be<00:15:04.240> able<00:15:04.480> to 00:15:04.870 --> 00:15:04.880 align:start position:0% CIP smart contracts will be able to 00:15:04.880 --> 00:15:07.550 align:start position:0% CIP smart contracts will be able to initiate<00:15:05.720> those<00:15:05.959> full<00:15:06.240> withdrawals<00:15:07.199> so<00:15:07.360> it's 00:15:07.550 --> 00:15:07.560 align:start position:0% initiate those full withdrawals so it's 00:15:07.560 --> 00:15:09.550 align:start position:0% initiate those full withdrawals so it's kind<00:15:07.680> of<00:15:07.839> a<00:15:08.199> a<00:15:08.440> trust<00:15:08.759> assumption<00:15:09.279> that<00:15:09.399> you 00:15:09.550 --> 00:15:09.560 align:start position:0% kind of a a trust assumption that you 00:15:09.560 --> 00:15:12.710 align:start position:0% kind of a a trust assumption that you can<00:15:09.759> now<00:15:10.079> remove<00:15:10.560> from<00:15:10.759> staking<00:15:11.160> pools<00:15:12.120> um<00:15:12.519> the 00:15:12.710 --> 00:15:12.720 align:start position:0% can now remove from staking pools um the 00:15:12.720 --> 00:15:14.829 align:start position:0% can now remove from staking pools um the likes<00:15:13.000> of<00:15:13.160> say<00:15:13.440> like<00:15:13.600> Lio<00:15:14.120> rocket<00:15:14.399> pool<00:15:14.680> other 00:15:14.829 --> 00:15:14.839 align:start position:0% likes of say like Lio rocket pool other 00:15:14.839 --> 00:15:16.910 align:start position:0% likes of say like Lio rocket pool other smart<00:15:15.160> contract<00:15:15.440> based<00:15:15.639> staking<00:15:15.920> pools<00:15:16.680> you 00:15:16.910 --> 00:15:16.920 align:start position:0% smart contract based staking pools you 00:15:16.920 --> 00:15:18.910 align:start position:0% smart contract based staking pools you can<00:15:17.519> um<00:15:17.680> those<00:15:17.839> smart<00:15:18.120> contracts<00:15:18.560> can<00:15:18.720> now 00:15:18.910 --> 00:15:18.920 align:start position:0% can um those smart contracts can now 00:15:18.920 --> 00:15:21.150 align:start position:0% can um those smart contracts can now trigger<00:15:19.360> full<00:15:19.680> withdrawals<00:15:20.320> of<00:15:20.519> validators 00:15:21.150 --> 00:15:21.160 align:start position:0% trigger full withdrawals of validators 00:15:21.160 --> 00:15:24.870 align:start position:0% trigger full withdrawals of validators if<00:15:21.320> they<00:15:21.480> wish<00:15:22.199> um<00:15:22.320> so<00:15:22.440> a<00:15:22.600> very<00:15:22.759> nice<00:15:23.880> nice 00:15:24.870 --> 00:15:24.880 align:start position:0% if they wish um so a very nice nice 00:15:24.880 --> 00:15:28.430 align:start position:0% if they wish um so a very nice nice feature<00:15:25.360> for<00:15:25.639> trustless<00:15:26.639> and<00:15:27.120> um<00:15:27.959> improving 00:15:28.430 --> 00:15:28.440 align:start position:0% feature for trustless and um improving 00:15:28.440 --> 00:15:30.910 align:start position:0% feature for trustless and um improving the<00:15:29.360> yes<00:15:29.720> this<00:15:30.120> I<00:15:30.199> don't<00:15:30.360> know<00:15:30.639> like 00:15:30.910 --> 00:15:30.920 align:start position:0% the yes this I don't know like 00:15:30.920 --> 00:15:33.590 align:start position:0% the yes this I don't know like resiliency<00:15:31.639> yes<00:15:31.920> resiliency<00:15:32.600> of<00:15:32.959> uh<00:15:33.079> smart 00:15:33.590 --> 00:15:33.600 align:start position:0% resiliency yes resiliency of uh smart 00:15:33.600 --> 00:15:34.829 align:start position:0% resiliency yes resiliency of uh smart staking<00:15:33.920> pool<00:15:34.160> smart<00:15:34.360> contract<00:15:34.639> based 00:15:34.829 --> 00:15:34.839 align:start position:0% staking pool smart contract based 00:15:34.839 --> 00:15:37.670 align:start position:0% staking pool smart contract based staking<00:15:35.079> pools<00:15:35.959> EAP<00:15:36.360> 7251<00:15:37.199> increasing<00:15:37.600> the 00:15:37.670 --> 00:15:37.680 align:start position:0% staking pools EAP 7251 increasing the 00:15:37.680 --> 00:15:39.110 align:start position:0% staking pools EAP 7251 increasing the maximum<00:15:38.040> effect<00:15:38.240> of<00:15:38.360> balance<00:15:38.639> I<00:15:38.720> have<00:15:38.839> written 00:15:39.110 --> 00:15:39.120 align:start position:0% maximum effect of balance I have written 00:15:39.120 --> 00:15:41.309 align:start position:0% maximum effect of balance I have written so<00:15:39.319> many<00:15:39.560> reports<00:15:39.959> on<00:15:40.120> the<00:15:40.399> problem<00:15:41.120> of 00:15:41.309 --> 00:15:41.319 align:start position:0% so many reports on the problem of 00:15:41.319 --> 00:15:43.749 align:start position:0% so many reports on the problem of ethereum's<00:15:42.120> growing<00:15:42.600> validator<00:15:43.040> set<00:15:43.279> size 00:15:43.749 --> 00:15:43.759 align:start position:0% ethereum's growing validator set size 00:15:43.759 --> 00:15:45.790 align:start position:0% ethereum's growing validator set size this<00:15:43.920> really<00:15:44.160> is<00:15:44.399> an<00:15:44.560> issue<00:15:45.199> I<00:15:45.319> guess<00:15:45.519> we<00:15:45.639> know 00:15:45.790 --> 00:15:45.800 align:start position:0% this really is an issue I guess we know 00:15:45.800 --> 00:15:46.870 align:start position:0% this really is an issue I guess we know when<00:15:45.959> developers<00:15:46.319> were<00:15:46.480> thinking<00:15:46.680> about<00:15:46.800> the 00:15:46.870 --> 00:15:46.880 align:start position:0% when developers were thinking about the 00:15:46.880 --> 00:15:48.749 align:start position:0% when developers were thinking about the beacon<00:15:47.160> chain<00:15:47.880> um<00:15:48.000> they<00:15:48.120> did<00:15:48.240> not<00:15:48.440> expect<00:15:48.639> the 00:15:48.749 --> 00:15:48.759 align:start position:0% beacon chain um they did not expect the 00:15:48.759 --> 00:15:50.829 align:start position:0% beacon chain um they did not expect the validator<00:15:49.199> set<00:15:49.399> to<00:15:49.519> grow<00:15:49.800> so<00:15:50.079> quickly<00:15:50.519> and<00:15:50.639> for 00:15:50.829 --> 00:15:50.839 align:start position:0% validator set to grow so quickly and for 00:15:50.839 --> 00:15:52.350 align:start position:0% validator set to grow so quickly and for the<00:15:51.079> peer-to-peer<00:15:51.399> network<00:15:51.839> of<00:15:51.920> ethereum<00:15:52.279> not 00:15:52.350 --> 00:15:52.360 align:start position:0% the peer-to-peer network of ethereum not 00:15:52.360 --> 00:15:55.389 align:start position:0% the peer-to-peer network of ethereum not to<00:15:52.480> be<00:15:52.560> able<00:15:52.720> to<00:15:52.839> handle<00:15:53.839> um<00:15:54.160> 1.5<00:15:55.000> million 00:15:55.389 --> 00:15:55.399 align:start position:0% to be able to handle um 1.5 million 00:15:55.399 --> 00:15:57.309 align:start position:0% to be able to handle um 1.5 million validators<00:15:55.959> I<00:15:56.040> think<00:15:56.120> we're<00:15:56.240> at<00:15:56.399> like<00:15:56.519> 1.2<00:15:57.000> or 00:15:57.309 --> 00:15:57.319 align:start position:0% validators I think we're at like 1.2 or 00:15:57.319 --> 00:16:00.069 align:start position:0% validators I think we're at like 1.2 or 1.3<00:15:58.319> somebody<00:15:58.560> can<00:15:58.680> check<00:15:58.800> me<00:15:59.040> on<00:15:59.240> that<00:15:59.680> um<00:15:59.959> but 00:16:00.069 --> 00:16:00.079 align:start position:0% 1.3 somebody can check me on that um but 00:16:00.079 --> 00:16:01.790 align:start position:0% 1.3 somebody can check me on that um but there's<00:16:00.279> a<00:16:00.440> lot<00:16:00.639> of<00:16:00.839> validators<00:16:01.440> a<00:16:01.560> lot<00:16:01.680> of 00:16:01.790 --> 00:16:01.800 align:start position:0% there's a lot of validators a lot of 00:16:01.800 --> 00:16:03.309 align:start position:0% there's a lot of validators a lot of active<00:16:02.079> validators<00:16:02.600> a<00:16:02.720> lot<00:16:02.839> of<00:16:02.920> messages 00:16:03.309 --> 00:16:03.319 align:start position:0% active validators a lot of messages 00:16:03.319 --> 00:16:04.990 align:start position:0% active validators a lot of messages being<00:16:03.560> passed<00:16:03.839> around<00:16:04.360> on<00:16:04.480> the<00:16:04.600> networking 00:16:04.990 --> 00:16:05.000 align:start position:0% being passed around on the networking 00:16:05.000 --> 00:16:07.790 align:start position:0% being passed around on the networking layer<00:16:05.319> and<00:16:05.399> it's<00:16:05.600> too<00:16:05.800> much<00:16:06.399> um<00:16:06.800> really<00:16:07.079> is<00:16:07.240> too 00:16:07.790 --> 00:16:07.800 align:start position:0% layer and it's too much um really is too 00:16:07.800 --> 00:16:12.590 align:start position:0% layer and it's too much um really is too much<00:16:08.800> so<00:16:09.160> it's<00:16:09.560> um<00:16:09.920> straining<00:16:10.800> nodes<00:16:11.800> um<00:16:12.240> and 00:16:12.590 --> 00:16:12.600 align:start position:0% much so it's um straining nodes um and 00:16:12.600 --> 00:16:14.710 align:start position:0% much so it's um straining nodes um and you<00:16:12.720> know<00:16:12.959> left<00:16:13.360> unchecked<00:16:14.120> it<00:16:14.199> would<00:16:14.399> be<00:16:14.600> a 00:16:14.710 --> 00:16:14.720 align:start position:0% you know left unchecked it would be a 00:16:14.720 --> 00:16:17.389 align:start position:0% you know left unchecked it would be a major<00:16:15.160> problem<00:16:15.560> for<00:16:15.800> the<00:16:15.959> health<00:16:16.319> of<00:16:16.480> ethereum 00:16:17.389 --> 00:16:17.399 align:start position:0% major problem for the health of ethereum 00:16:17.399 --> 00:16:21.110 align:start position:0% major problem for the health of ethereum so<00:16:18.040> uh<00:16:18.160> EIP<00:16:18.519> 7251<00:16:19.480> is<00:16:19.720> designed<00:16:20.199> to<00:16:20.680> encourage 00:16:21.110 --> 00:16:21.120 align:start position:0% so uh EIP 7251 is designed to encourage 00:16:21.120 --> 00:16:23.749 align:start position:0% so uh EIP 7251 is designed to encourage validators<00:16:21.639> to<00:16:21.800> consolidate<00:16:22.519> their<00:16:22.720> eth<00:16:23.639> um 00:16:23.749 --> 00:16:23.759 align:start position:0% validators to consolidate their eth um 00:16:23.759 --> 00:16:25.629 align:start position:0% validators to consolidate their eth um and<00:16:23.920> have<00:16:24.120> a<00:16:24.519> maximum<00:16:24.920> effective<00:16:25.279> balance 00:16:25.629 --> 00:16:25.639 align:start position:0% and have a maximum effective balance 00:16:25.639 --> 00:16:28.030 align:start position:0% and have a maximum effective balance higher<00:16:25.839> than<00:16:26.000> 32<00:16:26.399> eth<00:16:26.720> and<00:16:26.920> reduce<00:16:27.560> the<00:16:27.680> number 00:16:28.030 --> 00:16:28.040 align:start position:0% higher than 32 eth and reduce the number 00:16:28.040 --> 00:16:30.389 align:start position:0% higher than 32 eth and reduce the number of<00:16:28.199> active<00:16:28.480> validator<00:16:29.120> on<00:16:29.240> ethereum<00:16:30.199> that<00:16:30.279> is 00:16:30.389 --> 00:16:30.399 align:start position:0% of active validator on ethereum that is 00:16:30.399 --> 00:16:32.910 align:start position:0% of active validator on ethereum that is the<00:16:30.560> goal<00:16:30.880> of<00:16:31.000> EIP<00:16:31.360> 7251<00:16:32.319> let's<00:16:32.480> see<00:16:32.680> how 00:16:32.910 --> 00:16:32.920 align:start position:0% the goal of EIP 7251 let's see how 00:16:32.920 --> 00:16:34.749 align:start position:0% the goal of EIP 7251 let's see how quickly<00:16:33.279> it<00:16:33.399> is<00:16:33.600> adopted<00:16:33.959> once<00:16:34.199> preure<00:16:34.480> goes 00:16:34.749 --> 00:16:34.759 align:start position:0% quickly it is adopted once preure goes 00:16:34.759 --> 00:16:37.350 align:start position:0% quickly it is adopted once preure goes live<00:16:35.120> because<00:16:35.759> that<00:16:36.000> you<00:16:36.079> know<00:16:36.319> depends<00:16:36.639> on 00:16:37.350 --> 00:16:37.360 align:start position:0% live because that you know depends on 00:16:37.360 --> 00:16:39.030 align:start position:0% live because that you know depends on all<00:16:37.480> of<00:16:37.600> the<00:16:37.720> staking<00:16:38.079> pools<00:16:38.440> and 00:16:39.030 --> 00:16:39.040 align:start position:0% all of the staking pools and 00:16:39.040 --> 00:16:40.550 align:start position:0% all of the staking pools and stakeholders<00:16:39.519> of<00:16:39.639> the<00:16:39.720> staking<00:16:40.079> Community 00:16:40.550 --> 00:16:40.560 align:start position:0% stakeholders of the staking Community 00:16:40.560 --> 00:16:42.870 align:start position:0% stakeholders of the staking Community really<00:16:41.319> you<00:16:41.399> know<00:16:41.600> getting<00:16:41.839> it<00:16:42.079> together<00:16:42.600> okay 00:16:42.870 --> 00:16:42.880 align:start position:0% really you know getting it together okay 00:16:42.880 --> 00:16:46.590 align:start position:0% really you know getting it together okay so<00:16:43.680> uh<00:16:43.800> EAP<00:16:44.440> 7549<00:16:45.440> um<00:16:45.720> move<00:16:46.000> committee<00:16:46.319> index 00:16:46.590 --> 00:16:46.600 align:start position:0% so uh EAP 7549 um move committee index 00:16:46.600 --> 00:16:48.069 align:start position:0% so uh EAP 7549 um move committee index outside<00:16:47.040> attestation<00:16:47.639> kind<00:16:47.759> of<00:16:47.880> like<00:16:47.959> a 00:16:48.069 --> 00:16:48.079 align:start position:0% outside attestation kind of like a 00:16:48.079 --> 00:16:50.069 align:start position:0% outside attestation kind of like a restructuring<00:16:48.759> refactoring<00:16:49.480> of<00:16:49.639> the<00:16:49.800> way 00:16:50.069 --> 00:16:50.079 align:start position:0% restructuring refactoring of the way 00:16:50.079 --> 00:16:53.790 align:start position:0% restructuring refactoring of the way that<00:16:50.600> attestations<00:16:51.600> are<00:16:52.120> um<00:16:52.680> aggregated<00:16:53.680> uh 00:16:53.790 --> 00:16:53.800 align:start position:0% that attestations are um aggregated uh 00:16:53.800 --> 00:16:56.710 align:start position:0% that attestations are um aggregated uh to<00:16:54.079> make<00:16:54.759> blocks<00:16:55.399> or<00:16:55.920> to<00:16:56.199> reduce<00:16:56.600> the 00:16:56.710 --> 00:16:56.720 align:start position:0% to make blocks or to reduce the 00:16:56.720 --> 00:16:58.990 align:start position:0% to make blocks or to reduce the networking<00:16:57.279> load<00:16:57.560> of<00:16:57.680> ethereum<00:16:58.160> again<00:16:58.440> see 00:16:58.990 --> 00:16:59.000 align:start position:0% networking load of ethereum again see 00:16:59.000 --> 00:17:01.990 align:start position:0% networking load of ethereum again see there's<00:16:59.440> clearly<00:16:59.880> networking<00:17:00.639> pains<00:17:01.639> um<00:17:01.839> and 00:17:01.990 --> 00:17:02.000 align:start position:0% there's clearly networking pains um and 00:17:02.000 --> 00:17:04.630 align:start position:0% there's clearly networking pains um and save<00:17:02.319> node<00:17:02.560> bandwidth<00:17:03.519> um<00:17:03.800> and<00:17:04.120> kind<00:17:04.240> of<00:17:04.439> quick 00:17:04.630 --> 00:17:04.640 align:start position:0% save node bandwidth um and kind of quick 00:17:04.640 --> 00:17:06.350 align:start position:0% save node bandwidth um and kind of quick note<00:17:04.839> about<00:17:05.000> the<00:17:05.120> CIP<00:17:05.720> developers<00:17:06.160> when<00:17:06.280> they 00:17:06.350 --> 00:17:06.360 align:start position:0% note about the CIP developers when they 00:17:06.360 --> 00:17:07.789 align:start position:0% note about the CIP developers when they were<00:17:06.520> including<00:17:06.880> an<00:17:07.000> incture<00:17:07.360> I<00:17:07.439> was<00:17:07.520> like<00:17:07.640> oh 00:17:07.789 --> 00:17:07.799 align:start position:0% were including an incture I was like oh 00:17:07.799 --> 00:17:09.630 align:start position:0% were including an incture I was like oh this<00:17:07.919> is<00:17:08.039> a<00:17:08.360> this<00:17:08.439> is<00:17:08.559> a<00:17:08.679> great<00:17:08.880> change<00:17:09.319> clearly 00:17:09.630 --> 00:17:09.640 align:start position:0% this is a this is a great change clearly 00:17:09.640 --> 00:17:11.990 align:start position:0% this is a this is a great change clearly has<00:17:09.799> wonderful<00:17:10.160> benefits<00:17:10.760> an<00:17:10.919> easy<00:17:11.160> one<00:17:11.360> to<00:17:11.760> to 00:17:11.990 --> 00:17:12.000 align:start position:0% has wonderful benefits an easy one to to 00:17:12.000 --> 00:17:14.630 align:start position:0% has wonderful benefits an easy one to to go<00:17:12.199> ahead<00:17:12.520> with<00:17:13.199> um<00:17:13.400> in<00:17:13.600> practice<00:17:14.039> though<00:17:14.520> um 00:17:14.630 --> 00:17:14.640 align:start position:0% go ahead with um in practice though um 00:17:14.640 --> 00:17:16.270 align:start position:0% go ahead with um in practice though um turned<00:17:14.959> out<00:17:15.079> to<00:17:15.160> be<00:17:15.520> a<00:17:15.600> lot<00:17:15.760> harder<00:17:16.079> to 00:17:16.270 --> 00:17:16.280 align:start position:0% turned out to be a lot harder to 00:17:16.280 --> 00:17:18.429 align:start position:0% turned out to be a lot harder to implement<00:17:16.799> than<00:17:17.120> expected<00:17:17.720> so<00:17:18.160> sometimes 00:17:18.429 --> 00:17:18.439 align:start position:0% implement than expected so sometimes 00:17:18.439 --> 00:17:20.990 align:start position:0% implement than expected so sometimes that's<00:17:18.559> the<00:17:18.720> way<00:17:18.880> the<00:17:19.000> cookie<00:17:19.280> crumbles<00:17:20.280> wow<00:17:20.880> I 00:17:20.990 --> 00:17:21.000 align:start position:0% that's the way the cookie crumbles wow I 00:17:21.000 --> 00:17:22.390 align:start position:0% that's the way the cookie crumbles wow I cannot<00:17:21.319> believe<00:17:21.679> I<00:17:21.799> only<00:17:22.000> have<00:17:22.120> two<00:17:22.240> more 00:17:22.390 --> 00:17:22.400 align:start position:0% cannot believe I only have two more 00:17:22.400 --> 00:17:25.230 align:start position:0% cannot believe I only have two more minutes<00:17:22.799> um<00:17:23.199> okay<00:17:23.360> so<00:17:23.640> in<00:17:24.360> like<00:17:24.480> the<00:17:24.600> Outlook 00:17:25.230 --> 00:17:25.240 align:start position:0% minutes um okay so in like the Outlook 00:17:25.240 --> 00:17:26.829 align:start position:0% minutes um okay so in like the Outlook if<00:17:25.600> you<00:17:25.720> know<00:17:25.839> I<00:17:25.959> Blaze<00:17:26.280> through<00:17:26.439> that<00:17:26.600> really 00:17:26.829 --> 00:17:26.839 align:start position:0% if you know I Blaze through that really 00:17:26.839 --> 00:17:29.390 align:start position:0% if you know I Blaze through that really fast<00:17:27.199> don't<00:17:27.400> worry<00:17:28.120> in<00:17:28.240> summary<00:17:29.080> ra<00:17:29.240> is<00:17:29.320> a 00:17:29.390 --> 00:17:29.400 align:start position:0% fast don't worry in summary ra is a 00:17:29.400 --> 00:17:31.110 align:start position:0% fast don't worry in summary ra is a mixed<00:17:29.679> bag<00:17:29.880> of<00:17:30.000> updates<00:17:30.600> it's<00:17:30.720> going<00:17:30.840> to<00:17:30.919> do 00:17:31.110 --> 00:17:31.120 align:start position:0% mixed bag of updates it's going to do 00:17:31.120 --> 00:17:32.390 align:start position:0% mixed bag of updates it's going to do three<00:17:31.320> things<00:17:31.600> it's<00:17:31.720> going<00:17:31.799> to<00:17:31.919> fix<00:17:32.120> critical 00:17:32.390 --> 00:17:32.400 align:start position:0% three things it's going to fix critical 00:17:32.400 --> 00:17:34.870 align:start position:0% three things it's going to fix critical shortcomings<00:17:33.080> of<00:17:33.280> ethereums<00:17:34.280> as<00:17:34.400> a<00:17:34.559> proof<00:17:34.760> of 00:17:34.870 --> 00:17:34.880 align:start position:0% shortcomings of ethereums as a proof of 00:17:34.880 --> 00:17:37.190 align:start position:0% shortcomings of ethereums as a proof of stake<00:17:35.080> blockchain<00:17:35.600> think<00:17:35.760> about<00:17:35.960> Max<00:17:36.240> evb 00:17:37.190 --> 00:17:37.200 align:start position:0% stake blockchain think about Max evb 00:17:37.200 --> 00:17:38.830 align:start position:0% stake blockchain think about Max evb right<00:17:37.440> like<00:17:37.600> that's<00:17:37.760> a<00:17:37.960> critical<00:17:38.400> fix<00:17:38.720> that 00:17:38.830 --> 00:17:38.840 align:start position:0% right like that's a critical fix that 00:17:38.840 --> 00:17:40.430 align:start position:0% right like that's a critical fix that needs<00:17:39.000> to<00:17:39.200> happen<00:17:39.720> because<00:17:39.880> the<00:17:40.000> validator 00:17:40.430 --> 00:17:40.440 align:start position:0% needs to happen because the validator 00:17:40.440 --> 00:17:42.750 align:start position:0% needs to happen because the validator set<00:17:40.679> size<00:17:40.919> can<00:17:41.160> continue<00:17:41.440> to<00:17:41.559> grow<00:17:41.760> unchecked 00:17:42.750 --> 00:17:42.760 align:start position:0% set size can continue to grow unchecked 00:17:42.760 --> 00:17:44.270 align:start position:0% set size can continue to grow unchecked um<00:17:42.919> improve<00:17:43.240> the<00:17:43.320> user<00:17:43.640> experience<00:17:44.160> right 00:17:44.270 --> 00:17:44.280 align:start position:0% um improve the user experience right 00:17:44.280 --> 00:17:45.230 align:start position:0% um improve the user experience right we're<00:17:44.440> talking<00:17:44.679> about<00:17:44.880> like<00:17:45.000> the<00:17:45.080> new 00:17:45.230 --> 00:17:45.240 align:start position:0% we're talking about like the new 00:17:45.240 --> 00:17:47.310 align:start position:0% we're talking about like the new transaction<00:17:45.720> type<00:17:45.960> make<00:17:46.440> is<00:17:46.559> more<00:17:46.679> flexible 00:17:47.310 --> 00:17:47.320 align:start position:0% transaction type make is more flexible 00:17:47.320 --> 00:17:50.270 align:start position:0% transaction type make is more flexible some<00:17:48.280> improvements<00:17:48.760> for<00:17:49.320> uh<00:17:49.440> more<00:17:49.760> trustless 00:17:50.270 --> 00:17:50.280 align:start position:0% some improvements for uh more trustless 00:17:50.280 --> 00:17:52.190 align:start position:0% some improvements for uh more trustless designs<00:17:50.559> for<00:17:50.679> sticking<00:17:51.000> pools<00:17:51.360> Etc<00:17:52.000> some 00:17:52.190 --> 00:17:52.200 align:start position:0% designs for sticking pools Etc some 00:17:52.200 --> 00:17:54.270 align:start position:0% designs for sticking pools Etc some minor<00:17:52.559> ux<00:17:52.960> improvements<00:17:53.480> there<00:17:53.880> and<00:17:54.039> number 00:17:54.270 --> 00:17:54.280 align:start position:0% minor ux improvements there and number 00:17:54.280 --> 00:17:56.430 align:start position:0% minor ux improvements there and number three<00:17:54.720> uh<00:17:54.840> ethereum's<00:17:55.320> data<00:17:55.840> availability 00:17:56.430 --> 00:17:56.440 align:start position:0% three uh ethereum's data availability 00:17:56.440 --> 00:17:58.230 align:start position:0% three uh ethereum's data availability capacity<00:17:56.840> increasing<00:17:57.360> that<00:17:57.840> that<00:17:58.000> hasn't 00:17:58.230 --> 00:17:58.240 align:start position:0% capacity increasing that that hasn't 00:17:58.240 --> 00:18:00.430 align:start position:0% capacity increasing that that hasn't been<00:17:58.360> formally<00:17:58.960> included<00:17:59.400> into<00:17:59.720> Petra<00:18:00.280> but 00:18:00.430 --> 00:18:00.440 align:start position:0% been formally included into Petra but 00:18:00.440 --> 00:18:03.549 align:start position:0% been formally included into Petra but again<00:18:00.760> seems<00:18:01.080> likely<00:18:01.640> moving<00:18:01.919> on<00:18:02.600> um<00:18:03.360> okay 00:18:03.549 --> 00:18:03.559 align:start position:0% again seems likely moving on um okay 00:18:03.559 --> 00:18:05.789 align:start position:0% again seems likely moving on um okay here<00:18:03.720> are<00:18:03.919> all<00:18:04.120> the<00:18:04.240> eips<00:18:05.000> that<00:18:05.080> were<00:18:05.280> removed 00:18:05.789 --> 00:18:05.799 align:start position:0% here are all the eips that were removed 00:18:05.799 --> 00:18:07.190 align:start position:0% here are all the eips that were removed from<00:18:05.960> pectra<00:18:06.440> this<00:18:06.559> is<00:18:06.799> kind<00:18:06.919> of<00:18:07.000> like<00:18:07.120> a 00:18:07.190 --> 00:18:07.200 align:start position:0% from pectra this is kind of like a 00:18:07.200 --> 00:18:09.470 align:start position:0% from pectra this is kind of like a firsttime<00:18:07.640> thing<00:18:07.880> for<00:18:08.679> um<00:18:08.799> an<00:18:08.960> upgrade<00:18:09.360> to 00:18:09.470 --> 00:18:09.480 align:start position:0% firsttime thing for um an upgrade to 00:18:09.480 --> 00:18:12.070 align:start position:0% firsttime thing for um an upgrade to have<00:18:09.679> so<00:18:09.880> many<00:18:10.120> eips<00:18:10.640> removed<00:18:11.080> from<00:18:11.400> for<00:18:11.880> from 00:18:12.070 --> 00:18:12.080 align:start position:0% have so many eips removed from for from 00:18:12.080 --> 00:18:14.830 align:start position:0% have so many eips removed from for from it<00:18:12.960> um<00:18:13.200> the<00:18:13.320> first<00:18:13.520> one<00:18:13.679> is<00:18:13.840> pias<00:18:14.440> honestly 00:18:14.830 --> 00:18:14.840 align:start position:0% it um the first one is pias honestly 00:18:14.840 --> 00:18:16.470 align:start position:0% it um the first one is pias honestly there<00:18:14.960> was<00:18:15.080> going<00:18:15.159> to<00:18:15.280> be<00:18:15.480> a<00:18:15.799> much<00:18:16.120> bigger 00:18:16.470 --> 00:18:16.480 align:start position:0% there was going to be a much bigger 00:18:16.480 --> 00:18:19.070 align:start position:0% there was going to be a much bigger increase<00:18:16.919> to<00:18:17.320> data<00:18:17.640> availability<00:18:18.200> capacity 00:18:19.070 --> 00:18:19.080 align:start position:0% increase to data availability capacity 00:18:19.080 --> 00:18:20.990 align:start position:0% increase to data availability capacity um<00:18:19.240> in<00:18:19.480> Petra<00:18:20.039> initially<00:18:20.440> when<00:18:20.600> Petra<00:18:20.919> was 00:18:20.990 --> 00:18:21.000 align:start position:0% um in Petra initially when Petra was 00:18:21.000 --> 00:18:24.029 align:start position:0% um in Petra initially when Petra was being<00:18:21.120> scoped<00:18:21.480> out<00:18:21.679> pias<00:18:22.200> is<00:18:22.320> going<00:18:22.520> to<00:18:23.520> um 00:18:24.029 --> 00:18:24.039 align:start position:0% being scoped out pias is going to um 00:18:24.039 --> 00:18:27.270 align:start position:0% being scoped out pias is going to um allow<00:18:24.440> developers<00:18:25.039> to<00:18:25.360> increase<00:18:26.200> the<00:18:26.679> blob 00:18:27.270 --> 00:18:27.280 align:start position:0% allow developers to increase the blob 00:18:27.280 --> 00:18:29.549 align:start position:0% allow developers to increase the blob Target<00:18:27.720> of<00:18:27.880> ethereum<00:18:28.520> not<00:18:28.880> from<00:18:29.039> like<00:18:29.200> 3<00:18:29.440> to 00:18:29.549 --> 00:18:29.559 align:start position:0% Target of ethereum not from like 3 to 00:18:29.559 --> 00:18:31.669 align:start position:0% Target of ethereum not from like 3 to four<00:18:29.880> to<00:18:30.080> like<00:18:30.200> four<00:18:30.400> to<00:18:30.600> five<00:18:31.120> but<00:18:31.280> like<00:18:31.440> by 00:18:31.669 --> 00:18:31.679 align:start position:0% four to like four to five but like by 00:18:31.679 --> 00:18:34.789 align:start position:0% four to like four to five but like by multiples<00:18:32.440> more<00:18:33.039> without<00:18:33.640> um<00:18:33.840> impacting 00:18:34.789 --> 00:18:34.799 align:start position:0% multiples more without um impacting 00:18:34.799 --> 00:18:37.590 align:start position:0% multiples more without um impacting greatly<00:18:35.400> the<00:18:36.039> um<00:18:36.240> bandwidth<00:18:36.840> consumption<00:18:37.400> and 00:18:37.590 --> 00:18:37.600 align:start position:0% greatly the um bandwidth consumption and 00:18:37.600 --> 00:18:39.149 align:start position:0% greatly the um bandwidth consumption and the<00:18:38.000> uh<00:18:38.159> computational<00:18:38.679> requirements<00:18:39.039> of 00:18:39.149 --> 00:18:39.159 align:start position:0% the uh computational requirements of 00:18:39.159 --> 00:18:41.510 align:start position:0% the uh computational requirements of running<00:18:39.400> in<00:18:39.720> ethereum<00:18:40.120> node<00:18:40.760> but<00:18:41.039> it's<00:18:41.240> still 00:18:41.510 --> 00:18:41.520 align:start position:0% running in ethereum node but it's still 00:18:41.520 --> 00:18:43.710 align:start position:0% running in ethereum node but it's still in<00:18:41.720> research<00:18:42.039> and<00:18:42.200> development<00:18:42.679> phase<00:18:43.520> um 00:18:43.710 --> 00:18:43.720 align:start position:0% in research and development phase um 00:18:43.720 --> 00:18:45.669 align:start position:0% in research and development phase um it's<00:18:43.880> still<00:18:44.039> being<00:18:44.240> developed<00:18:45.120> and<00:18:45.520> these 00:18:45.669 --> 00:18:45.679 align:start position:0% it's still being developed and these 00:18:45.679 --> 00:18:47.750 align:start position:0% it's still being developed and these other<00:18:45.880> 11<00:18:46.240> code<00:18:46.480> changes<00:18:47.080> as<00:18:47.200> a<00:18:47.320> bundle<00:18:47.640> are 00:18:47.750 --> 00:18:47.760 align:start position:0% other 11 code changes as a bundle are 00:18:47.760 --> 00:18:49.710 align:start position:0% other 11 code changes as a bundle are called<00:18:48.000> eoff<00:18:48.360> it's<00:18:48.520> this<00:18:48.640> major<00:18:48.919> update<00:18:49.240> to 00:18:49.710 --> 00:18:49.720 align:start position:0% called eoff it's this major update to 00:18:49.720 --> 00:18:52.190 align:start position:0% called eoff it's this major update to the<00:18:49.840> ethereum<00:18:50.360> evm 00:18:52.190 --> 00:18:52.200 align:start position:0% the ethereum evm 00:18:52.200 --> 00:18:56.350 align:start position:0% the ethereum evm and<00:18:53.200> both<00:18:53.760> of<00:18:54.039> these<00:18:54.600> eips<00:18:55.600> all<00:18:55.840> these<00:18:55.960> eips 00:18:56.350 --> 00:18:56.360 align:start position:0% and both of these eips all these eips 00:18:56.360 --> 00:18:58.510 align:start position:0% and both of these eips all these eips were<00:18:56.520> really<00:18:57.120> initially<00:18:57.480> included<00:18:57.799> in<00:18:57.919> pectra 00:18:58.510 --> 00:18:58.520 align:start position:0% were really initially included in pectra 00:18:58.520 --> 00:19:00.310 align:start position:0% were really initially included in pectra but<00:18:58.799> they<00:18:58.880> were<00:18:59.039> being<00:18:59.320> tested<00:18:59.840> on<00:19:00.000> separate 00:19:00.310 --> 00:19:00.320 align:start position:0% but they were being tested on separate 00:19:00.320 --> 00:19:02.350 align:start position:0% but they were being tested on separate devet<00:19:00.799> so<00:19:00.880> you<00:19:01.000> had<00:19:01.159> the<00:19:01.280> pectra<00:19:01.640> eips<00:19:02.240> that 00:19:02.350 --> 00:19:02.360 align:start position:0% devet so you had the pectra eips that 00:19:02.360 --> 00:19:04.830 align:start position:0% devet so you had the pectra eips that were<00:19:02.600> moving<00:19:02.880> along<00:19:03.480> progressing<00:19:04.480> um 00:19:04.830 --> 00:19:04.840 align:start position:0% were moving along progressing um 00:19:04.840 --> 00:19:07.590 align:start position:0% were moving along progressing um starting<00:19:05.280> to<00:19:06.159> solidify<00:19:06.960> um<00:19:07.080> starting<00:19:07.400> to 00:19:07.590 --> 00:19:07.600 align:start position:0% starting to solidify um starting to 00:19:07.600 --> 00:19:09.190 align:start position:0% starting to solidify um starting to become<00:19:07.880> more<00:19:08.320> aspects<00:19:08.640> of<00:19:08.760> it<00:19:08.840> were<00:19:09.000> starting 00:19:09.190 --> 00:19:09.200 align:start position:0% become more aspects of it were starting 00:19:09.200 --> 00:19:11.110 align:start position:0% become more aspects of it were starting to<00:19:09.320> become<00:19:09.520> more<00:19:09.640> or<00:19:09.760> less<00:19:09.919> finalized<00:19:10.919> but 00:19:11.110 --> 00:19:11.120 align:start position:0% to become more or less finalized but 00:19:11.120 --> 00:19:14.270 align:start position:0% to become more or less finalized but pias<00:19:11.679> and<00:19:11.799> eof<00:19:12.679> um<00:19:13.000> there<00:19:13.120> were<00:19:13.760> developers 00:19:14.270 --> 00:19:14.280 align:start position:0% pias and eof um there were developers 00:19:14.280 --> 00:19:16.110 align:start position:0% pias and eof um there were developers thought<00:19:14.480> that<00:19:14.600> it<00:19:14.760> would<00:19:15.039> require<00:19:15.440> a<00:19:15.600> lot<00:19:15.799> more 00:19:16.110 --> 00:19:16.120 align:start position:0% thought that it would require a lot more 00:19:16.120 --> 00:19:18.990 align:start position:0% thought that it would require a lot more time<00:19:16.679> to<00:19:17.280> get<00:19:17.440> them<00:19:17.640> really<00:19:17.919> ready<00:19:18.240> for<00:19:18.520> mayet 00:19:18.990 --> 00:19:19.000 align:start position:0% time to get them really ready for mayet 00:19:19.000 --> 00:19:20.950 align:start position:0% time to get them really ready for mayet Activation<00:19:19.760> and<00:19:19.880> developers<00:19:20.360> did<00:19:20.520> not<00:19:20.799> want 00:19:20.950 --> 00:19:20.960 align:start position:0% Activation and developers did not want 00:19:20.960 --> 00:19:22.990 align:start position:0% Activation and developers did not want to<00:19:21.159> delay<00:19:21.720> the<00:19:21.880> activation<00:19:22.320> of<00:19:22.440> the<00:19:22.600> Petra 00:19:22.990 --> 00:19:23.000 align:start position:0% to delay the activation of the Petra 00:19:23.000 --> 00:19:25.029 align:start position:0% to delay the activation of the Petra eips<00:19:23.720> from<00:19:23.919> getting<00:19:24.080> onto<00:19:24.320> Main<00:19:24.520> net<00:19:24.760> which<00:19:24.880> is 00:19:25.029 --> 00:19:25.039 align:start position:0% eips from getting onto Main net which is 00:19:25.039 --> 00:19:26.669 align:start position:0% eips from getting onto Main net which is why<00:19:25.240> one<00:19:25.360> of<00:19:25.480> the<00:19:25.559> reasons<00:19:26.080> was<00:19:26.320> they<00:19:26.440> wanted 00:19:26.669 --> 00:19:26.679 align:start position:0% why one of the reasons was they wanted 00:19:26.679 --> 00:19:28.350 align:start position:0% why one of the reasons was they wanted to<00:19:26.760> get<00:19:26.919> Petra<00:19:27.240> out<00:19:27.440> the<00:19:27.520> Petra<00:19:27.799> eips<00:19:28.200> out 00:19:28.350 --> 00:19:28.360 align:start position:0% to get Petra out the Petra eips out 00:19:28.360 --> 00:19:31.510 align:start position:0% to get Petra out the Petra eips out sooner<00:19:28.919> so<00:19:29.240> they<00:19:29.440> said<00:19:29.720> pias<00:19:30.200> and<00:19:30.320> eof<00:19:31.320> um 00:19:31.510 --> 00:19:31.520 align:start position:0% sooner so they said pias and eof um 00:19:31.520 --> 00:19:33.549 align:start position:0% sooner so they said pias and eof um clearly<00:19:31.880> needs<00:19:32.159> more<00:19:32.360> time<00:19:32.520> to<00:19:32.640> be<00:19:32.799> worked<00:19:33.039> on 00:19:33.549 --> 00:19:33.559 align:start position:0% clearly needs more time to be worked on 00:19:33.559 --> 00:19:35.470 align:start position:0% clearly needs more time to be worked on we'll<00:19:33.799> pump<00:19:34.039> that<00:19:34.159> to<00:19:34.360> another<00:19:34.679> upgrade<00:19:35.280> and 00:19:35.470 --> 00:19:35.480 align:start position:0% we'll pump that to another upgrade and 00:19:35.480 --> 00:19:37.270 align:start position:0% we'll pump that to another upgrade and not<00:19:35.760> hold<00:19:36.039> back<00:19:36.240> these<00:19:36.400> other<00:19:36.600> pector<00:19:36.919> eips 00:19:37.270 --> 00:19:37.280 align:start position:0% not hold back these other pector eips 00:19:37.280 --> 00:19:39.149 align:start position:0% not hold back these other pector eips from<00:19:37.400> mainnet<00:19:38.080> another<00:19:38.360> reason<00:19:38.640> is<00:19:38.840> this<00:19:38.960> is<00:19:39.080> a 00:19:39.149 --> 00:19:39.159 align:start position:0% from mainnet another reason is this is a 00:19:39.159 --> 00:19:41.390 align:start position:0% from mainnet another reason is this is a lot<00:19:39.280> of<00:19:39.400> eips<00:19:40.360> in<00:19:40.480> addition<00:19:40.760> to<00:19:40.880> the<00:19:41.000> other<00:19:41.159> 10 00:19:41.390 --> 00:19:41.400 align:start position:0% lot of eips in addition to the other 10 00:19:41.400 --> 00:19:44.190 align:start position:0% lot of eips in addition to the other 10 that<00:19:41.520> I<00:19:41.600> talked<00:19:41.840> about<00:19:42.440> um<00:19:42.760> so<00:19:43.200> lots<00:19:43.400> of<00:19:43.600> risk 00:19:44.190 --> 00:19:44.200 align:start position:0% that I talked about um so lots of risk 00:19:44.200 --> 00:19:45.750 align:start position:0% that I talked about um so lots of risk right<00:19:44.480> um<00:19:44.679> with<00:19:44.760> the<00:19:44.840> interdependencies<00:19:45.640> of 00:19:45.750 --> 00:19:45.760 align:start position:0% right um with the interdependencies of 00:19:45.760 --> 00:19:47.789 align:start position:0% right um with the interdependencies of this<00:19:46.000> code<00:19:46.640> um<00:19:46.760> trying<00:19:46.960> to<00:19:47.120> implement<00:19:47.480> it<00:19:47.640> all 00:19:47.789 --> 00:19:47.799 align:start position:0% this code um trying to implement it all 00:19:47.799 --> 00:19:51.029 align:start position:0% this code um trying to implement it all at<00:19:47.960> once<00:19:48.640> this<00:19:48.760> is<00:19:49.000> a<00:19:49.200> lot<00:19:49.559> of<00:19:50.200> of<00:19:50.440> work<00:19:50.760> and 00:19:51.029 --> 00:19:51.039 align:start position:0% at once this is a lot of of work and 00:19:51.039 --> 00:19:52.750 align:start position:0% at once this is a lot of of work and time<00:19:51.360> for<00:19:51.600> the<00:19:51.760> testing<00:19:52.039> team<00:19:52.280> and<00:19:52.400> the<00:19:52.480> client 00:19:52.750 --> 00:19:52.760 align:start position:0% time for the testing team and the client 00:19:52.760 --> 00:19:54.549 align:start position:0% time for the testing team and the client teams<00:19:53.080> to<00:19:53.159> be<00:19:53.280> able<00:19:53.440> to<00:19:53.559> ensure<00:19:54.200> there<00:19:54.280> aren't 00:19:54.549 --> 00:19:54.559 align:start position:0% teams to be able to ensure there aren't 00:19:54.559 --> 00:19:58.710 align:start position:0% teams to be able to ensure there aren't any<00:19:54.760> bugs<00:19:55.600> um<00:19:55.799> so<00:19:56.200> lots<00:19:56.720> of<00:19:57.080> reasons<00:19:57.600> for<00:19:57.960> to<00:19:58.360> I 00:19:58.710 --> 00:19:58.720 align:start position:0% any bugs um so lots of reasons for to I 00:19:58.720 --> 00:20:00.470 align:start position:0% any bugs um so lots of reasons for to I I<00:19:58.760> would<00:19:58.919> say<00:19:59.159> actually<00:19:59.440> main<00:19:59.640> reasons<00:20:00.240> for 00:20:00.470 --> 00:20:00.480 align:start position:0% I would say actually main reasons for 00:20:00.480 --> 00:20:02.430 align:start position:0% I would say actually main reasons for why<00:20:00.640> these<00:20:00.799> eips<00:20:01.200> were<00:20:01.320> removed<00:20:01.600> from 00:20:02.430 --> 00:20:02.440 align:start position:0% why these eips were removed from 00:20:02.440 --> 00:20:06.510 align:start position:0% why these eips were removed from Petra<00:20:03.440> and<00:20:03.880> now<00:20:04.559> they<00:20:04.760> are<00:20:05.200> moved<00:20:05.600> to<00:20:05.799> fusaka 00:20:06.510 --> 00:20:06.520 align:start position:0% Petra and now they are moved to fusaka 00:20:06.520 --> 00:20:08.149 align:start position:0% Petra and now they are moved to fusaka so<00:20:06.880> again<00:20:07.120> I<00:20:07.240> have<00:20:07.360> verl<00:20:07.679> up<00:20:07.799> there<00:20:07.960> because 00:20:08.149 --> 00:20:08.159 align:start position:0% so again I have verl up there because 00:20:08.159 --> 00:20:11.110 align:start position:0% so again I have verl up there because verl<00:20:08.640> was<00:20:08.960> initially<00:20:09.320> slated<00:20:09.720> for<00:20:09.880> fusaka<00:20:10.880> but 00:20:11.110 --> 00:20:11.120 align:start position:0% verl was initially slated for fusaka but 00:20:11.120 --> 00:20:13.190 align:start position:0% verl was initially slated for fusaka but then<00:20:11.640> now<00:20:11.840> it's<00:20:11.960> not<00:20:12.159> going<00:20:12.360> to<00:20:12.840> because 00:20:13.190 --> 00:20:13.200 align:start position:0% then now it's not going to because 00:20:13.200 --> 00:20:14.270 align:start position:0% then now it's not going to because developers<00:20:13.559> have<00:20:13.679> given<00:20:13.880> a<00:20:14.039> soft 00:20:14.270 --> 00:20:14.280 align:start position:0% developers have given a soft 00:20:14.280 --> 00:20:16.630 align:start position:0% developers have given a soft confirmation<00:20:14.960> that<00:20:15.120> eof<00:20:15.520> and<00:20:15.679> pias<00:20:16.240> are<00:20:16.480> going 00:20:16.630 --> 00:20:16.640 align:start position:0% confirmation that eof and pias are going 00:20:16.640 --> 00:20:19.510 align:start position:0% confirmation that eof and pias are going to<00:20:16.799> be<00:20:17.039> into<00:20:17.320> in<00:20:17.440> faka<00:20:18.039> but<00:20:18.200> again<00:20:18.720> obviously 00:20:19.510 --> 00:20:19.520 align:start position:0% to be into in faka but again obviously 00:20:19.520 --> 00:20:22.190 align:start position:0% to be into in faka but again obviously there's<00:20:19.960> um<00:20:20.720> changes<00:20:21.159> happen<00:20:21.559> like<00:20:21.799> in<00:20:22.039> the 00:20:22.190 --> 00:20:22.200 align:start position:0% there's um changes happen like in the 00:20:22.200 --> 00:20:24.029 align:start position:0% there's um changes happen like in the moment<00:20:22.679> developers<00:20:23.080> should<00:20:23.360> be<00:20:23.520> able<00:20:23.760> to 00:20:24.029 --> 00:20:24.039 align:start position:0% moment developers should be able to 00:20:24.039 --> 00:20:26.270 align:start position:0% moment developers should be able to reassess<00:20:24.720> priorities<00:20:25.520> and<00:20:25.919> uh<00:20:26.039> make 00:20:26.270 --> 00:20:26.280 align:start position:0% reassess priorities and uh make 00:20:26.280 --> 00:20:28.950 align:start position:0% reassess priorities and uh make decisions<00:20:26.679> accordingly<00:20:27.679> um<00:20:27.880> so<00:20:28.280> it's<00:20:28.720> like 00:20:28.950 --> 00:20:28.960 align:start position:0% decisions accordingly um so it's like 00:20:28.960 --> 00:20:30.430 align:start position:0% decisions accordingly um so it's like it's<00:20:29.200> unlikely<00:20:29.679> but<00:20:29.760> there's<00:20:29.880> a<00:20:30.000> non-zero 00:20:30.430 --> 00:20:30.440 align:start position:0% it's unlikely but there's a non-zero 00:20:30.440 --> 00:20:33.029 align:start position:0% it's unlikely but there's a non-zero chance<00:20:30.799> Anything<00:20:31.039> Could<00:20:31.240> Happen<00:20:31.799> um<00:20:31.919> verl<00:20:32.720> so 00:20:33.029 --> 00:20:33.039 align:start position:0% chance Anything Could Happen um verl so 00:20:33.039 --> 00:20:35.870 align:start position:0% chance Anything Could Happen um verl so verl<00:20:33.440> is<00:20:33.559> not<00:20:33.720> in<00:20:33.840> fusaka<00:20:34.360> for<00:20:34.520> now<00:20:35.159> and<00:20:35.400> eof<00:20:35.760> in 00:20:35.870 --> 00:20:35.880 align:start position:0% verl is not in fusaka for now and eof in 00:20:35.880 --> 00:20:40.350 align:start position:0% verl is not in fusaka for now and eof in pias<00:20:36.320> for<00:20:36.520> now<00:20:37.280> is<00:20:37.600> in<00:20:37.840> P<00:20:38.200> in<00:20:38.720> um<00:20:39.720> fusaka<00:20:40.240> and 00:20:40.350 --> 00:20:40.360 align:start position:0% pias for now is in P in um fusaka and 00:20:40.360 --> 00:20:42.669 align:start position:0% pias for now is in P in um fusaka and there's<00:20:40.520> a<00:20:40.679> couple<00:20:41.000> other<00:20:41.320> eips<00:20:42.280> that<00:20:42.400> I<00:20:42.480> think 00:20:42.669 --> 00:20:42.679 align:start position:0% there's a couple other eips that I think 00:20:42.679 --> 00:20:44.830 align:start position:0% there's a couple other eips that I think developers<00:20:43.200> will<00:20:43.480> reconsider<00:20:44.159> for<00:20:44.360> inclusion 00:20:44.830 --> 00:20:44.840 align:start position:0% developers will reconsider for inclusion 00:20:44.840 --> 00:20:46.830 align:start position:0% developers will reconsider for inclusion in<00:20:44.960> fusaka<00:20:45.840> once<00:20:46.120> developers<00:20:46.600> have<00:20:46.720> the 00:20:46.830 --> 00:20:46.840 align:start position:0% in fusaka once developers have the 00:20:46.840 --> 00:20:49.149 align:start position:0% in fusaka once developers have the bandwidth<00:20:47.320> to<00:20:47.480> really<00:20:47.679> think<00:20:47.880> about<00:20:48.080> it<00:20:48.679> um 00:20:49.149 --> 00:20:49.159 align:start position:0% bandwidth to really think about it um 00:20:49.159 --> 00:20:51.789 align:start position:0% bandwidth to really think about it um and<00:20:50.159> give<00:20:50.360> their<00:20:50.480> full<00:20:50.720> attention<00:20:51.080> to<00:20:51.280> fusaka 00:20:51.789 --> 00:20:51.799 align:start position:0% and give their full attention to fusaka 00:20:51.799 --> 00:20:53.789 align:start position:0% and give their full attention to fusaka after<00:20:52.039> Petra<00:20:52.880> um<00:20:53.120> these<00:20:53.240> are<00:20:53.440> some<00:20:53.559> of<00:20:53.679> the 00:20:53.789 --> 00:20:53.799 align:start position:0% after Petra um these are some of the 00:20:53.799 --> 00:20:55.029 align:start position:0% after Petra um these are some of the other<00:20:53.960> ones<00:20:54.159> that<00:20:54.280> were<00:20:54.440> considered<00:20:54.799> for 00:20:55.029 --> 00:20:55.039 align:start position:0% other ones that were considered for 00:20:55.039 --> 00:20:58.270 align:start position:0% other ones that were considered for pectra<00:20:55.919> um<00:20:56.159> but<00:20:56.520> never<00:20:56.720> made<00:20:56.919> it<00:20:57.039> in<00:20:57.559> um<00:20:57.960> but 00:20:58.270 --> 00:20:58.280 align:start position:0% pectra um but never made it in um but 00:20:58.280 --> 00:20:59.870 align:start position:0% pectra um but never made it in um but now<00:20:58.640> there's<00:20:58.840> more<00:20:59.039> time<00:20:59.320> for<00:20:59.520> these<00:20:59.679> other 00:20:59.870 --> 00:20:59.880 align:start position:0% now there's more time for these other 00:20:59.880 --> 00:21:01.590 align:start position:0% now there's more time for these other code<00:21:00.080> changes<00:21:00.480> to<00:21:00.600> be<00:21:00.760> worked<00:21:01.000> on<00:21:01.280> they<00:21:01.440> could 00:21:01.590 --> 00:21:01.600 align:start position:0% code changes to be worked on they could 00:21:01.600 --> 00:21:03.630 align:start position:0% code changes to be worked on they could be<00:21:02.000> a<00:21:02.120> lot<00:21:02.320> more<00:21:02.480> ready<00:21:02.679> for<00:21:02.880> implementation 00:21:03.630 --> 00:21:03.640 align:start position:0% be a lot more ready for implementation 00:21:03.640 --> 00:21:05.950 align:start position:0% be a lot more ready for implementation six<00:21:03.880> months<00:21:04.159> from<00:21:04.320> now<00:21:04.919> than<00:21:05.440> right<00:21:05.600> now<00:21:05.799> so 00:21:05.950 --> 00:21:05.960 align:start position:0% six months from now than right now so 00:21:05.960 --> 00:21:07.710 align:start position:0% six months from now than right now so there's<00:21:06.200> like<00:21:06.320> the<00:21:06.440> S<00:21:06.880> transition<00:21:07.320> inclusion 00:21:07.710 --> 00:21:07.720 align:start position:0% there's like the S transition inclusion 00:21:07.720 --> 00:21:09.990 align:start position:0% there's like the S transition inclusion list<00:21:08.440> um<00:21:08.600> change<00:21:08.919> to<00:21:09.120> issuance<00:21:09.679> everybody 00:21:09.990 --> 00:21:10.000 align:start position:0% list um change to issuance everybody 00:21:10.000 --> 00:21:12.470 align:start position:0% list um change to issuance everybody remember<00:21:10.320> that<00:21:10.520> debate<00:21:11.000> um<00:21:11.640> could<00:21:11.840> come<00:21:12.039> back 00:21:12.470 --> 00:21:12.480 align:start position:0% remember that debate um could come back 00:21:12.480 --> 00:21:15.390 align:start position:0% remember that debate um could come back history<00:21:12.880> expiry<00:21:13.760> epbs<00:21:14.760> um<00:21:14.880> and<00:21:15.039> accounts 00:21:15.390 --> 00:21:15.400 align:start position:0% history expiry epbs um and accounts 00:21:15.400 --> 00:21:16.669 align:start position:0% history expiry epbs um and accounts direction<00:21:16.000> right<00:21:16.159> like<00:21:16.279> with<00:21:16.400> the<00:21:16.520> new 00:21:16.669 --> 00:21:16.679 align:start position:0% direction right like with the new 00:21:16.679 --> 00:21:18.029 align:start position:0% direction right like with the new transaction<00:21:17.159> type<00:21:17.440> maybe<00:21:17.640> there'll<00:21:17.799> be<00:21:17.919> some 00:21:18.029 --> 00:21:18.039 align:start position:0% transaction type maybe there'll be some 00:21:18.039 --> 00:21:19.789 align:start position:0% transaction type maybe there'll be some learnings<00:21:18.400> from<00:21:18.600> that<00:21:18.720> from<00:21:18.919> pectra<00:21:19.600> that 00:21:19.789 --> 00:21:19.799 align:start position:0% learnings from that from pectra that 00:21:19.799 --> 00:21:22.269 align:start position:0% learnings from that from pectra that inform<00:21:20.279> next<00:21:20.480> steps<00:21:21.039> so<00:21:21.320> lots<00:21:21.559> of<00:21:21.919> of<00:21:22.080> other 00:21:22.269 --> 00:21:22.279 align:start position:0% inform next steps so lots of of other 00:21:22.279 --> 00:21:24.990 align:start position:0% inform next steps so lots of of other eips<00:21:23.000> that<00:21:23.159> could<00:21:23.360> be<00:21:23.840> um<00:21:24.279> included<00:21:24.880> the 00:21:24.990 --> 00:21:25.000 align:start position:0% eips that could be um included the 00:21:25.000 --> 00:21:27.789 align:start position:0% eips that could be um included the scoping<00:21:25.520> discussion<00:21:25.880> for<00:21:26.080> fusaka<00:21:26.960> will<00:21:27.159> be<00:21:27.640> an 00:21:27.789 --> 00:21:27.799 align:start position:0% scoping discussion for fusaka will be an 00:21:27.799 --> 00:21:29.630 align:start position:0% scoping discussion for fusaka will be an interesting<00:21:28.120> one<00:21:28.279> to<00:21:28.640> watch<00:21:28.919> so<00:21:29.400> in<00:21:29.520> the 00:21:29.630 --> 00:21:29.640 align:start position:0% interesting one to watch so in the 00:21:29.640 --> 00:21:31.630 align:start position:0% interesting one to watch so in the audience<00:21:30.200> I<00:21:30.279> hope<00:21:30.480> this<00:21:30.679> just<00:21:30.799> goes<00:21:31.000> to<00:21:31.159> show 00:21:31.630 --> 00:21:31.640 align:start position:0% audience I hope this just goes to show 00:21:31.640 --> 00:21:34.549 align:start position:0% audience I hope this just goes to show please<00:21:32.159> be<00:21:32.440> engaged<00:21:33.000> in<00:21:33.159> ethereum<00:21:33.600> governance 00:21:34.549 --> 00:21:34.559 align:start position:0% please be engaged in ethereum governance 00:21:34.559 --> 00:21:36.630 align:start position:0% please be engaged in ethereum governance um<00:21:34.840> I<00:21:35.080> don't<00:21:35.240> foresee<00:21:35.720> you<00:21:35.840> know<00:21:36.120> very<00:21:36.320> many 00:21:36.630 --> 00:21:36.640 align:start position:0% um I don't foresee you know very many 00:21:36.640 --> 00:21:38.269 align:start position:0% um I don't foresee you know very many upgrades<00:21:37.000> left<00:21:37.159> in<00:21:37.320> ethereum's<00:21:37.760> future<00:21:38.080> so 00:21:38.269 --> 00:21:38.279 align:start position:0% upgrades left in ethereum's future so 00:21:38.279 --> 00:21:39.990 align:start position:0% upgrades left in ethereum's future so every<00:21:38.520> upgrade<00:21:38.960> counts<00:21:39.480> and<00:21:39.600> there's<00:21:39.760> a<00:21:39.880> lot 00:21:39.990 --> 00:21:40.000 align:start position:0% every upgrade counts and there's a lot 00:21:40.000 --> 00:21:42.350 align:start position:0% every upgrade counts and there's a lot of<00:21:40.159> priorities<00:21:40.720> on<00:21:40.880> the<00:21:41.039> list<00:21:41.559> um<00:21:41.720> and<00:21:41.840> so<00:21:42.200> it's 00:21:42.350 --> 00:21:42.360 align:start position:0% of priorities on the list um and so it's 00:21:42.360 --> 00:21:44.590 align:start position:0% of priorities on the list um and so it's worth<00:21:42.600> it<00:21:42.919> in<00:21:43.360> the<00:21:43.480> ethereum<00:21:43.919> ecosystem<00:21:44.400> to 00:21:44.590 --> 00:21:44.600 align:start position:0% worth it in the ethereum ecosystem to 00:21:44.600 --> 00:21:46.350 align:start position:0% worth it in the ethereum ecosystem to make<00:21:44.760> sure<00:21:44.960> that<00:21:45.080> your<00:21:45.240> voice<00:21:45.440> is<00:21:45.600> heard<00:21:46.200> and 00:21:46.350 --> 00:21:46.360 align:start position:0% make sure that your voice is heard and 00:21:46.360 --> 00:21:47.909 align:start position:0% make sure that your voice is heard and that<00:21:46.520> decisions<00:21:47.080> about<00:21:47.320> where<00:21:47.520> ethereum 00:21:47.909 --> 00:21:47.919 align:start position:0% that decisions about where ethereum 00:21:47.919 --> 00:21:50.830 align:start position:0% that decisions about where ethereum protocol<00:21:48.320> is<00:21:48.440> heading<00:21:48.840> is<00:21:48.960> not<00:21:49.200> made<00:21:49.559> by<00:21:50.240> like 00:21:50.830 --> 00:21:50.840 align:start position:0% protocol is heading is not made by like 00:21:50.840 --> 00:21:53.430 align:start position:0% protocol is heading is not made by like a<00:21:50.960> few<00:21:51.400> individuals<00:21:52.000> or<00:21:52.159> a<00:21:52.240> few<00:21:52.480> groups<00:21:53.200> um<00:21:53.320> but 00:21:53.430 --> 00:21:53.440 align:start position:0% a few individuals or a few groups um but 00:21:53.440 --> 00:21:55.110 align:start position:0% a few individuals or a few groups um but that<00:21:53.600> the<00:21:53.720> whole<00:21:53.919> community<00:21:54.400> and<00:21:54.600> ecosystem 00:21:55.110 --> 00:21:55.120 align:start position:0% that the whole community and ecosystem 00:21:55.120 --> 00:21:57.230 align:start position:0% that the whole community and ecosystem gets<00:21:55.320> involved<00:21:55.840> so<00:21:56.480> thank<00:21:56.679> you<00:21:56.960> I<00:21:57.039> hope<00:21:57.159> you 00:21:57.230 --> 00:21:57.240 align:start position:0% gets involved so thank you I hope you 00:21:57.240 --> 00:22:00.110 align:start position:0% gets involved so thank you I hope you learned<00:21:57.520> something<00:21:57.760> new<00:21:58.159> about<00:21:58.640> ethereum<00:21:59.640> and 00:22:00.110 --> 00:22:00.120 align:start position:0% learned something new about ethereum and 00:22:00.120 --> 00:22:02.350 align:start position:0% learned something new about ethereum and Petra<00:22:01.120> thank<00:22:01.279> you<00:22:01.600> thank<00:22:01.760> you<00:22:02.000> thank<00:22:02.159> you 00:22:02.350 --> 00:22:02.360 align:start position:0% Petra thank you thank you thank you 00:22:02.360 --> 00:22:05.350 align:start position:0% Petra thank you thank you thank you Christine<00:22:02.880> we<00:22:03.039> have<00:22:03.240> a<00:22:03.640> couple<00:22:04.640> we<00:22:04.799> have<00:22:04.960> a<00:22:05.080> few 00:22:05.350 --> 00:22:05.360 align:start position:0% Christine we have a couple we have a few 00:22:05.360 --> 00:22:08.669 align:start position:0% Christine we have a couple we have a few minutes<00:22:05.880> for<00:22:06.480> a<00:22:06.720> Q&A<00:22:07.320> as<00:22:07.440> you<00:22:07.559> can<00:22:07.679> see<00:22:08.000> you<00:22:08.200> can 00:22:08.669 --> 00:22:08.679 align:start position:0% minutes for a Q&A as you can see you can 00:22:08.679 --> 00:22:10.590 align:start position:0% minutes for a Q&A as you can see you can sort<00:22:08.880> of<00:22:09.080> upvote<00:22:09.520> them<00:22:09.799> there<00:22:10.039> so<00:22:10.240> if<00:22:10.320> you<00:22:10.480> have 00:22:10.590 --> 00:22:10.600 align:start position:0% sort of upvote them there so if you have 00:22:10.600 --> 00:22:11.870 align:start position:0% sort of upvote them there so if you have one<00:22:10.760> that<00:22:10.840> you<00:22:10.960> really<00:22:11.080> want<00:22:11.279> answered<00:22:11.640> please 00:22:11.870 --> 00:22:11.880 align:start position:0% one that you really want answered please 00:22:11.880 --> 00:22:14.070 align:start position:0% one that you really want answered please upvote<00:22:12.320> right<00:22:12.440> now<00:22:12.640> but<00:22:12.840> I<00:22:12.919> will<00:22:13.080> let<00:22:13.279> you<00:22:13.880> take 00:22:14.070 --> 00:22:14.080 align:start position:0% upvote right now but I will let you take 00:22:14.080 --> 00:22:16.789 align:start position:0% upvote right now but I will let you take it<00:22:14.240> away<00:22:14.559> with<00:22:14.880> when<00:22:15.279> eof<00:22:16.159> when<00:22:16.400> eof<00:22:16.720> I 00:22:16.789 --> 00:22:16.799 align:start position:0% it away with when eof when eof I 00:22:16.799 --> 00:22:19.029 align:start position:0% it away with when eof when eof I literally<00:22:17.159> just<00:22:17.279> said<00:22:17.840> the<00:22:18.360> devs<00:22:18.679> literally 00:22:19.029 --> 00:22:19.039 align:start position:0% literally just said the devs literally 00:22:19.039 --> 00:22:20.430 align:start position:0% literally just said the devs literally said<00:22:19.320> that<00:22:19.440> they<00:22:19.520> are<00:22:19.679> going<00:22:19.840> to<00:22:20.000> try<00:22:20.159> and<00:22:20.279> put 00:22:20.430 --> 00:22:20.440 align:start position:0% said that they are going to try and put 00:22:20.440 --> 00:22:22.149 align:start position:0% said that they are going to try and put it<00:22:20.559> into<00:22:20.919> fusaka<00:22:21.480> do<00:22:21.600> I<00:22:21.720> think<00:22:21.840> that<00:22:22.000> it's 00:22:22.149 --> 00:22:22.159 align:start position:0% it into fusaka do I think that it's 00:22:22.159 --> 00:22:24.190 align:start position:0% it into fusaka do I think that it's likely<00:22:22.720> probably<00:22:23.159> not<00:22:23.640> do<00:22:23.799> I<00:22:23.919> think<00:22:24.039> that 00:22:24.190 --> 00:22:24.200 align:start position:0% likely probably not do I think that 00:22:24.200 --> 00:22:26.070 align:start position:0% likely probably not do I think that fusaka<00:22:24.679> is<00:22:24.760> going<00:22:24.840> to<00:22:24.960> happen<00:22:25.159> in<00:22:25.279> 2025 00:22:26.070 --> 00:22:26.080 align:start position:0% fusaka is going to happen in 2025 00:22:26.080 --> 00:22:27.630 align:start position:0% fusaka is going to happen in 2025 absolutely<00:22:26.640> not<00:22:26.880> I<00:22:26.960> think<00:22:27.159> that<00:22:27.320> the<00:22:27.440> amount 00:22:27.630 --> 00:22:27.640 align:start position:0% absolutely not I think that the amount 00:22:27.640 --> 00:22:29.190 align:start position:0% absolutely not I think that the amount of<00:22:27.760> time<00:22:27.880> is<00:22:28.000> taken<00:22:28.200> to<00:22:28.279> prep<00:22:28.559> par<00:22:28.760> pectra 00:22:29.190 --> 00:22:29.200 align:start position:0% of time is taken to prep par pectra 00:22:29.200 --> 00:22:30.990 align:start position:0% of time is taken to prep par pectra fusaka<00:22:29.640> will<00:22:29.760> take<00:22:29.880> a<00:22:30.000> similar<00:22:30.400> if<00:22:30.480> not<00:22:30.679> longer 00:22:30.990 --> 00:22:31.000 align:start position:0% fusaka will take a similar if not longer 00:22:31.000 --> 00:22:33.029 align:start position:0% fusaka will take a similar if not longer time<00:22:31.640> awesome<00:22:32.039> and<00:22:32.200> then<00:22:32.559> if<00:22:32.640> we<00:22:32.760> want<00:22:32.880> to 00:22:33.029 --> 00:22:33.039 align:start position:0% time awesome and then if we want to 00:22:33.039 --> 00:22:35.990 align:start position:0% time awesome and then if we want to answer<00:22:33.559> I<00:22:33.640> think<00:22:33.799> we<00:22:33.919> have<00:22:34.080> time<00:22:34.240> for<00:22:34.760> one<00:22:35.000> more 00:22:35.990 --> 00:22:36.000 align:start position:0% answer I think we have time for one more 00:22:36.000 --> 00:22:39.630 align:start position:0% answer I think we have time for one more um<00:22:36.600> is<00:22:36.799> there<00:22:37.799> for<00:22:37.960> us<00:22:38.080> to<00:22:38.200> increase<00:22:39.120> Petra<00:22:39.520> in 00:22:39.630 --> 00:22:39.640 align:start position:0% um is there for us to increase Petra in 00:22:39.640 --> 00:22:43.390 align:start position:0% um is there for us to increase Petra in case<00:22:39.840> they<00:22:40.039> get<00:22:40.559> too<00:22:40.960> expensive<00:22:41.480> and<00:22:42.000> start<00:22:43.000> um 00:22:43.390 --> 00:22:43.400 align:start position:0% case they get too expensive and start um 00:22:43.400 --> 00:22:45.190 align:start position:0% case they get too expensive and start um yes<00:22:43.679> there<00:22:43.880> definitely<00:22:44.240> is<00:22:44.480> an<00:22:44.600> emergency 00:22:45.190 --> 00:22:45.200 align:start position:0% yes there definitely is an emergency 00:22:45.200 --> 00:22:47.950 align:start position:0% yes there definitely is an emergency path<00:22:45.520> for<00:22:45.799> increasing<00:22:46.279> blob<00:22:46.640> Target<00:22:47.640> oh 00:22:47.950 --> 00:22:47.960 align:start position:0% path for increasing blob Target oh 00:22:47.960 --> 00:22:52.149 align:start position:0% path for increasing blob Target oh between<00:22:48.400> now<00:22:48.880> and<00:22:49.159> Petra<00:22:49.880> activation<00:22:50.880> hm<00:22:51.559> no 00:22:52.149 --> 00:22:52.159 align:start position:0% between now and Petra activation hm no 00:22:52.159 --> 00:22:55.590 align:start position:0% between now and Petra activation hm no cuz<00:22:52.360> blob<00:22:52.679> Target<00:22:53.080> is<00:22:53.400> is<00:22:53.520> a<00:22:54.120> hardcoded<00:22:55.120> Target 00:22:55.590 --> 00:22:55.600 align:start position:0% cuz blob Target is is a hardcoded Target 00:22:55.600 --> 00:22:57.470 align:start position:0% cuz blob Target is is a hardcoded Target and<00:22:55.840> Max<00:22:56.360> in<00:22:56.520> the<00:22:56.679> execution<00:22:57.080> layer<00:22:57.360> and 00:22:57.470 --> 00:22:57.480 align:start position:0% and Max in the execution layer and 00:22:57.480 --> 00:22:59.549 align:start position:0% and Max in the execution layer and consensus<00:22:57.880> layer<00:22:58.120> for<00:22:58.640> that<00:22:58.760> to<00:22:58.960> change<00:22:59.279> for 00:22:59.549 --> 00:22:59.559 align:start position:0% consensus layer for that to change for 00:22:59.559 --> 00:23:01.549 align:start position:0% consensus layer for that to change for blob<00:22:59.880> capacity<00:23:00.320> to<00:23:00.440> change<00:23:00.919> developers<00:23:01.400> need 00:23:01.549 --> 00:23:01.559 align:start position:0% blob capacity to change developers need 00:23:01.559 --> 00:23:04.710 align:start position:0% blob capacity to change developers need to<00:23:01.679> do<00:23:01.840> a<00:23:01.960> hard<00:23:02.159> Fork<00:23:02.960> so<00:23:03.559> no<00:23:03.919> I<00:23:04.080> do<00:23:04.279> not<00:23:04.480> think 00:23:04.710 --> 00:23:04.720 align:start position:0% to do a hard Fork so no I do not think 00:23:04.720 --> 00:23:06.510 align:start position:0% to do a hard Fork so no I do not think that<00:23:04.880> there's<00:23:05.600> any<00:23:05.799> way<00:23:05.960> for<00:23:06.080> the<00:23:06.200> blob 00:23:06.510 --> 00:23:06.520 align:start position:0% that there's any way for the blob 00:23:06.520 --> 00:23:08.830 align:start position:0% that there's any way for the blob capacity<00:23:07.000> to<00:23:07.679> increase<00:23:08.159> between<00:23:08.480> now<00:23:08.679> and 00:23:08.830 --> 00:23:08.840 align:start position:0% capacity to increase between now and 00:23:08.840 --> 00:23:11.630 align:start position:0% capacity to increase between now and pectra<00:23:09.480> um<00:23:09.640> without<00:23:09.840> a<00:23:09.960> hard<00:23:10.120> Fork<00:23:10.640> yeah 00:23:11.630 --> 00:23:11.640 align:start position:0% pectra um without a hard Fork yeah 00:23:11.640 --> 00:23:13.310 align:start position:0% pectra um without a hard Fork yeah actually<00:23:12.039> we<00:23:12.159> are<00:23:12.279> doing<00:23:12.600> okay<00:23:12.799> on<00:23:12.960> time<00:23:13.200> so 00:23:13.310 --> 00:23:13.320 align:start position:0% actually we are doing okay on time so 00:23:13.320 --> 00:23:14.789 align:start position:0% actually we are doing okay on time so we're<00:23:13.480> going<00:23:13.559> to<00:23:13.760> keep<00:23:14.039> cycling<00:23:14.559> through 00:23:14.789 --> 00:23:14.799 align:start position:0% we're going to keep cycling through 00:23:14.799 --> 00:23:17.350 align:start position:0% we're going to keep cycling through these<00:23:15.279> is<00:23:15.400> the<00:23:15.600> proposal<00:23:16.000> to<00:23:16.120> change<00:23:16.840> the<00:23:17.039> blob 00:23:17.350 --> 00:23:17.360 align:start position:0% these is the proposal to change the blob 00:23:17.360 --> 00:23:20.149 align:start position:0% these is the proposal to change the blob limit<00:23:17.799> only<00:23:18.320> or<00:23:18.559> also<00:23:18.799> the<00:23:18.919> blob<00:23:19.279> Target<00:23:20.039> okay 00:23:20.149 --> 00:23:20.159 align:start position:0% limit only or also the blob Target okay 00:23:20.159 --> 00:23:22.110 align:start position:0% limit only or also the blob Target okay so<00:23:20.320> that's<00:23:20.440> a<00:23:20.559> great<00:23:20.840> question<00:23:21.400> um<00:23:21.679> blob 00:23:22.110 --> 00:23:22.120 align:start position:0% so that's a great question um blob 00:23:22.120 --> 00:23:24.269 align:start position:0% so that's a great question um blob Target<00:23:22.919> there<00:23:23.159> the<00:23:23.360> most<00:23:23.640> conservative 00:23:24.269 --> 00:23:24.279 align:start position:0% Target there the most conservative 00:23:24.279 --> 00:23:26.430 align:start position:0% Target there the most conservative increase<00:23:24.840> is<00:23:25.000> three<00:23:25.240> to<00:23:25.400> four<00:23:25.799> just<00:23:26.039> changing 00:23:26.430 --> 00:23:26.440 align:start position:0% increase is three to four just changing 00:23:26.440 --> 00:23:28.510 align:start position:0% increase is three to four just changing the<00:23:26.600> target<00:23:27.000> not<00:23:27.200> changing<00:23:27.600> the<00:23:27.720> max<00:23:27.960> at<00:23:28.080> all 00:23:28.510 --> 00:23:28.520 align:start position:0% the target not changing the max at all 00:23:28.520 --> 00:23:30.630 align:start position:0% the target not changing the max at all but<00:23:28.679> that's<00:23:28.919> not<00:23:29.360> what<00:23:29.799> uh<00:23:30.000> layer<00:23:30.320> 2 00:23:30.630 --> 00:23:30.640 align:start position:0% but that's not what uh layer 2 00:23:30.640 --> 00:23:33.310 align:start position:0% but that's not what uh layer 2 developers<00:23:31.360> have<00:23:31.600> asked<00:23:31.919> for<00:23:32.240> base<00:23:33.159> um 00:23:33.310 --> 00:23:33.320 align:start position:0% developers have asked for base um 00:23:33.320 --> 00:23:34.750 align:start position:0% developers have asked for base um there's<00:23:33.520> this<00:23:33.720> representative<00:23:34.279> of<00:23:34.400> the<00:23:34.520> base 00:23:34.750 --> 00:23:34.760 align:start position:0% there's this representative of the base 00:23:34.760 --> 00:23:37.190 align:start position:0% there's this representative of the base team<00:23:35.120> a<00:23:35.240> coin<00:23:35.480> bases<00:23:35.880> base<00:23:36.159> team<00:23:36.799> and<00:23:37.000> he's 00:23:37.190 --> 00:23:37.200 align:start position:0% team a coin bases base team and he's 00:23:37.200 --> 00:23:39.149 align:start position:0% team a coin bases base team and he's been<00:23:37.360> vying<00:23:37.679> for<00:23:37.880> more<00:23:38.240> aggressive<00:23:39.000> um 00:23:39.149 --> 00:23:39.159 align:start position:0% been vying for more aggressive um 00:23:39.159 --> 00:23:41.230 align:start position:0% been vying for more aggressive um increases<00:23:39.760> he's<00:23:39.960> shown<00:23:40.320> data<00:23:40.600> to<00:23:40.799> suggest 00:23:41.230 --> 00:23:41.240 align:start position:0% increases he's shown data to suggest 00:23:41.240 --> 00:23:43.350 align:start position:0% increases he's shown data to suggest that<00:23:41.799> uh<00:23:41.919> the<00:23:42.039> increase<00:23:42.360> wouldn't<00:23:42.720> impact<00:23:43.159> the 00:23:43.350 --> 00:23:43.360 align:start position:0% that uh the increase wouldn't impact the 00:23:43.360 --> 00:23:44.830 align:start position:0% that uh the increase wouldn't impact the the<00:23:43.480> decentral<00:23:44.039> negatively<00:23:44.480> impact<00:23:44.720> the 00:23:44.830 --> 00:23:44.840 align:start position:0% the decentral negatively impact the 00:23:44.840 --> 00:23:46.950 align:start position:0% the decentral negatively impact the decentralization<00:23:45.600> of<00:23:45.760> ethereum<00:23:46.480> so<00:23:46.679> there's 00:23:46.950 --> 00:23:46.960 align:start position:0% decentralization of ethereum so there's 00:23:46.960 --> 00:23:49.430 align:start position:0% decentralization of ethereum so there's actually<00:23:47.320> both<00:23:47.919> uh<00:23:48.240> there's<00:23:48.400> a<00:23:48.600> conservative 00:23:49.430 --> 00:23:49.440 align:start position:0% actually both uh there's a conservative 00:23:49.440 --> 00:23:51.430 align:start position:0% actually both uh there's a conservative proposal<00:23:49.840> to<00:23:50.039> just<00:23:50.200> change<00:23:50.520> the<00:23:50.679> Target<00:23:51.360> and 00:23:51.430 --> 00:23:51.440 align:start position:0% proposal to just change the Target and 00:23:51.440 --> 00:23:53.350 align:start position:0% proposal to just change the Target and then<00:23:51.600> there's<00:23:51.760> a<00:23:51.960> more<00:23:52.320> ambitious<00:23:52.960> proposal 00:23:53.350 --> 00:23:53.360 align:start position:0% then there's a more ambitious proposal 00:23:53.360 --> 00:23:56.430 align:start position:0% then there's a more ambitious proposal to<00:23:53.480> change<00:23:53.880> both<00:23:54.080> the<00:23:54.240> Max<00:23:55.039> and<00:23:55.360> the<00:23:55.679> target<00:23:56.120> to 00:23:56.430 --> 00:23:56.440 align:start position:0% to change both the Max and the target to 00:23:56.440 --> 00:23:58.789 align:start position:0% to change both the Max and the target to like<00:23:57.039> it's<00:23:57.200> like<00:23:57.360> eight<00:23:57.559> and<00:23:57.799> four<00:23:58.480> if<00:23:58.600> not 00:23:58.789 --> 00:23:58.799 align:start position:0% like it's like eight and four if not 00:23:58.799 --> 00:24:01.110 align:start position:0% like it's like eight and four if not like<00:23:58.960> six<00:23:59.200> and<00:23:59.400> 12<00:24:00.200> um<00:24:00.320> so<00:24:00.440> there's<00:24:00.679> varying 00:24:01.110 --> 00:24:01.120 align:start position:0% like six and 12 um so there's varying 00:24:01.120 --> 00:24:03.909 align:start position:0% like six and 12 um so there's varying gradients<00:24:01.600> there's<00:24:01.919> actually<00:24:02.600> a<00:24:03.120> a<00:24:03.320> lot<00:24:03.640> of 00:24:03.909 --> 00:24:03.919 align:start position:0% gradients there's actually a a lot of 00:24:03.919 --> 00:24:05.669 align:start position:0% gradients there's actually a a lot of different<00:24:04.240> ways<00:24:04.480> in<00:24:04.640> which<00:24:05.000> uh<00:24:05.120> devs<00:24:05.480> could 00:24:05.669 --> 00:24:05.679 align:start position:0% different ways in which uh devs could 00:24:05.679 --> 00:24:08.590 align:start position:0% different ways in which uh devs could increase<00:24:06.679> uh<00:24:06.840> the<00:24:06.960> target<00:24:07.640> um<00:24:07.960> we'll<00:24:08.120> see<00:24:08.400> how 00:24:08.590 --> 00:24:08.600 align:start position:0% increase uh the target um we'll see how 00:24:08.600 --> 00:24:11.110 align:start position:0% increase uh the target um we'll see how conservative<00:24:09.600> they<00:24:10.080> uh<00:24:10.159> choose<00:24:10.440> to<00:24:10.559> go<00:24:10.679> for 00:24:11.110 --> 00:24:11.120 align:start position:0% conservative they uh choose to go for 00:24:11.120 --> 00:24:13.269 align:start position:0% conservative they uh choose to go for but<00:24:11.360> yeah<00:24:12.320> and<00:24:12.480> I<00:24:12.559> think<00:24:12.760> I'm<00:24:12.880> going<00:24:13.000> to<00:24:13.120> go 00:24:13.269 --> 00:24:13.279 align:start position:0% but yeah and I think I'm going to go 00:24:13.279 --> 00:24:16.110 align:start position:0% but yeah and I think I'm going to go first<00:24:13.799> so<00:24:14.159> you<00:24:14.640> just<00:24:15.200> urge<00:24:15.559> people<00:24:15.720> to<00:24:15.840> be<00:24:15.960> more 00:24:16.110 --> 00:24:16.120 align:start position:0% first so you just urge people to be more 00:24:16.120 --> 00:24:17.269 align:start position:0% first so you just urge people to be more involved<00:24:16.440> in<00:24:16.559> governance<00:24:17.000> we're<00:24:17.120> going<00:24:17.200> to 00:24:17.269 --> 00:24:17.279 align:start position:0% involved in governance we're going to 00:24:17.279 --> 00:24:18.870 align:start position:0% involved in governance we're going to jump<00:24:17.480> to<00:24:17.679> that<00:24:17.880> question<00:24:18.320> how<00:24:18.559> can<00:24:18.760> the 00:24:18.870 --> 00:24:18.880 align:start position:0% jump to that question how can the 00:24:18.880 --> 00:24:21.149 align:start position:0% jump to that question how can the community<00:24:19.279> get<00:24:19.400> more<00:24:19.640> involved<00:24:20.360> in 00:24:21.149 --> 00:24:21.159 align:start position:0% community get more involved in 00:24:21.159 --> 00:24:22.710 align:start position:0% community get more involved in governance 00:24:22.710 --> 00:24:22.720 align:start position:0% governance 00:24:22.720 --> 00:24:25.630 align:start position:0% governance yes<00:24:23.720> well<00:24:23.880> so<00:24:24.159> eth<00:24:24.559> research<00:24:25.120> and<00:24:25.320> eth 00:24:25.630 --> 00:24:25.640 align:start position:0% yes well so eth research and eth 00:24:25.640 --> 00:24:27.430 align:start position:0% yes well so eth research and eth magicians<00:24:26.279> are<00:24:26.559> two<00:24:26.840> really<00:24:27.120> great 00:24:27.430 --> 00:24:27.440 align:start position:0% magicians are two really great 00:24:27.440 --> 00:24:29.830 align:start position:0% magicians are two really great discussion<00:24:27.880> forums<00:24:28.480> for<00:24:28.840> up<00:24:29.120> voting<00:24:29.480> certain 00:24:29.830 --> 00:24:29.840 align:start position:0% discussion forums for up voting certain 00:24:29.840 --> 00:24:33.350 align:start position:0% discussion forums for up voting certain eips<00:24:30.520> showing<00:24:30.880> your<00:24:31.080> support<00:24:31.399> for<00:24:31.600> an<00:24:31.960> EIP<00:24:32.960> um 00:24:33.350 --> 00:24:33.360 align:start position:0% eips showing your support for an EIP um 00:24:33.360 --> 00:24:34.830 align:start position:0% eips showing your support for an EIP um I<00:24:33.520> would<00:24:33.679> say<00:24:33.880> those<00:24:34.000> are<00:24:34.200> two<00:24:34.440> really<00:24:34.640> good 00:24:34.830 --> 00:24:34.840 align:start position:0% I would say those are two really good 00:24:34.840 --> 00:24:38.549 align:start position:0% I would say those are two really good ones<00:24:35.720> um<00:24:36.200> another<00:24:36.960> one<00:24:37.399> that<00:24:37.640> is<00:24:38.080> good<00:24:38.360> but 00:24:38.549 --> 00:24:38.559 align:start position:0% ones um another one that is good but 00:24:38.559 --> 00:24:39.909 align:start position:0% ones um another one that is good but probably<00:24:38.840> a<00:24:38.960> little<00:24:39.120> bit<00:24:39.320> harder<00:24:39.640> for 00:24:39.909 --> 00:24:39.919 align:start position:0% probably a little bit harder for 00:24:39.919 --> 00:24:42.029 align:start position:0% probably a little bit harder for everyone<00:24:40.360> to<00:24:40.559> do<00:24:41.399> um<00:24:41.559> if<00:24:41.640> you<00:24:41.799> have<00:24:41.880> a 00:24:42.029 --> 00:24:42.039 align:start position:0% everyone to do um if you have a 00:24:42.039 --> 00:24:43.909 align:start position:0% everyone to do um if you have a representative<00:24:42.640> from<00:24:43.159> from<00:24:43.279> your<00:24:43.480> company 00:24:43.909 --> 00:24:43.919 align:start position:0% representative from from your company 00:24:43.919 --> 00:24:45.750 align:start position:0% representative from from your company that<00:24:44.039> wants<00:24:44.279> to<00:24:44.480> really<00:24:44.880> uh<00:24:45.080> advocate<00:24:45.440> for<00:24:45.600> an 00:24:45.750 --> 00:24:45.760 align:start position:0% that wants to really uh advocate for an 00:24:45.760 --> 00:24:48.149 align:start position:0% that wants to really uh advocate for an EIP<00:24:46.279> the<00:24:46.440> ACD<00:24:46.919> calls<00:24:47.200> are<00:24:47.399> probably<00:24:47.679> the<00:24:47.840> most 00:24:48.149 --> 00:24:48.159 align:start position:0% EIP the ACD calls are probably the most 00:24:48.159 --> 00:24:50.029 align:start position:0% EIP the ACD calls are probably the most high<00:24:48.399> signal<00:24:48.760> place<00:24:48.960> to<00:24:49.120> do<00:24:49.279> it<00:24:49.720> all<00:24:49.840> you<00:24:49.919> have 00:24:50.029 --> 00:24:50.039 align:start position:0% high signal place to do it all you have 00:24:50.039 --> 00:24:52.630 align:start position:0% high signal place to do it all you have to<00:24:50.159> do<00:24:50.320> is<00:24:50.520> just<00:24:50.880> leave<00:24:51.120> a<00:24:51.320> comment<00:24:51.679> on<00:24:51.919> the<00:24:52.080> ACD 00:24:52.630 --> 00:24:52.640 align:start position:0% to do is just leave a comment on the ACD 00:24:52.640 --> 00:24:54.950 align:start position:0% to do is just leave a comment on the ACD call<00:24:52.919> agenda<00:24:53.320> on<00:24:53.520> GitHub<00:24:54.159> and<00:24:54.279> say<00:24:54.559> like<00:24:54.840> this 00:24:54.950 --> 00:24:54.960 align:start position:0% call agenda on GitHub and say like this 00:24:54.960 --> 00:24:57.070 align:start position:0% call agenda on GitHub and say like this is<00:24:55.080> an<00:24:55.240> EIP<00:24:55.720> that<00:24:55.840> I'd<00:24:56.000> like<00:24:56.200> to<00:24:56.679> uh<00:24:56.799> speak 00:24:57.070 --> 00:24:57.080 align:start position:0% is an EIP that I'd like to uh speak 00:24:57.080 --> 00:24:59.630 align:start position:0% is an EIP that I'd like to uh speak about<00:24:57.360> or<00:24:57.600> present<00:24:58.480> um<00:24:58.640> and<00:24:58.760> the<00:24:58.880> moderator<00:24:59.520> of 00:24:59.630 --> 00:24:59.640 align:start position:0% about or present um and the moderator of 00:24:59.640 --> 00:25:02.149 align:start position:0% about or present um and the moderator of the<00:24:59.799> call<00:25:00.080> is<00:25:00.240> usually<00:25:00.640> very<00:25:00.919> agreeable<00:25:01.480> to<00:25:02.000> uh 00:25:02.149 --> 00:25:02.159 align:start position:0% the call is usually very agreeable to uh 00:25:02.159 --> 00:25:04.830 align:start position:0% the call is usually very agreeable to uh giving<00:25:02.559> you<00:25:02.880> the<00:25:03.360> time<00:25:03.919> um<00:25:04.240> don't<00:25:04.399> take<00:25:04.559> up<00:25:04.679> too 00:25:04.830 --> 00:25:04.840 align:start position:0% giving you the time um don't take up too 00:25:04.840 --> 00:25:06.269 align:start position:0% giving you the time um don't take up too much<00:25:05.000> time<00:25:05.240> though<00:25:05.480> like<00:25:05.760> maybe<00:25:05.960> like<00:25:06.080> 5 00:25:06.269 --> 00:25:06.279 align:start position:0% much time though like maybe like 5 00:25:06.279 --> 00:25:08.590 align:start position:0% much time though like maybe like 5 minutes<00:25:07.080> um<00:25:07.279> for<00:25:07.520> you<00:25:07.720> to<00:25:08.039> like<00:25:08.200> say<00:25:08.440> your 00:25:08.590 --> 00:25:08.600 align:start position:0% minutes um for you to like say your 00:25:08.600 --> 00:25:11.230 align:start position:0% minutes um for you to like say your peace<00:25:08.960> so<00:25:09.679> um<00:25:10.000> you<00:25:10.120> know<00:25:10.320> use<00:25:10.600> that<00:25:10.799> chip 00:25:11.230 --> 00:25:11.240 align:start position:0% peace so um you know use that chip 00:25:11.240 --> 00:25:13.990 align:start position:0% peace so um you know use that chip sparingly<00:25:12.240> but<00:25:12.640> um<00:25:12.880> that<00:25:13.000> is<00:25:13.240> probably<00:25:13.760> one<00:25:13.880> of 00:25:13.990 --> 00:25:14.000 align:start position:0% sparingly but um that is probably one of 00:25:14.000 --> 00:25:17.720 align:start position:0% sparingly but um that is probably one of the<00:25:14.120> most<00:25:14.440> like<00:25:15.200> uh