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.750 align:start position:0% [Music] 00:00:09.750 --> 00:00:09.760 align:start position:0% [Music] 00:00:09.760 --> 00:00:12.789 align:start position:0% [Music] thank<00:00:09.920> you<00:00:10.440> but<00:00:10.799> just<00:00:11.799> in<00:00:11.920> my<00:00:12.120> defense<00:00:12.639> I 00:00:12.789 --> 00:00:12.799 align:start position:0% thank you but just in my defense I 00:00:12.799 --> 00:00:15.070 align:start position:0% thank you but just in my defense I opened<00:00:13.120> my<00:00:13.240> Twitter<00:00:13.639> account<00:00:14.080> only<00:00:14.480> to<00:00:14.679> pitch 00:00:15.070 --> 00:00:15.080 align:start position:0% opened my Twitter account only to pitch 00:00:15.080 --> 00:00:16.750 align:start position:0% opened my Twitter account only to pitch this<00:00:15.400> and<00:00:15.639> as<00:00:15.719> soon<00:00:15.879> as<00:00:16.039> this<00:00:16.160> is<00:00:16.279> shipped<00:00:16.640> I'm 00:00:16.750 --> 00:00:16.760 align:start position:0% this and as soon as this is shipped I'm 00:00:16.760 --> 00:00:19.310 align:start position:0% this and as soon as this is shipped I'm going<00:00:16.880> to<00:00:17.080> shut<00:00:17.400> up<00:00:17.560> on<00:00:17.800> Twitter<00:00:18.800> anyway<00:00:19.119> so 00:00:19.310 --> 00:00:19.320 align:start position:0% going to shut up on Twitter anyway so 00:00:19.320 --> 00:00:20.870 align:start position:0% going to shut up on Twitter anyway so today<00:00:19.640> I'm<00:00:19.800> going<00:00:19.920> to<00:00:20.000> be<00:00:20.160> talking<00:00:20.439> about<00:00:20.760> the 00:00:20.870 --> 00:00:20.880 align:start position:0% today I'm going to be talking about the 00:00:20.880 --> 00:00:24.550 align:start position:0% today I'm going to be talking about the status<00:00:21.199> of<00:00:21.640> epbs<00:00:22.640> and<00:00:23.160> epbs<00:00:23.840> during<00:00:24.160> this<00:00:24.320> talk 00:00:24.550 --> 00:00:24.560 align:start position:0% status of epbs and epbs during this talk 00:00:24.560 --> 00:00:27.950 align:start position:0% status of epbs and epbs during this talk is<00:00:24.680> going<00:00:24.840> to<00:00:25.000> mean<00:00:25.680> enshrined<00:00:26.679> payload<00:00:27.199> block 00:00:27.950 --> 00:00:27.960 align:start position:0% is going to mean enshrined payload block 00:00:27.960 --> 00:00:30.749 align:start position:0% is going to mean enshrined payload block separation<00:00:28.960> this<00:00:29.080> is<00:00:29.240> not<00:00:29.400> the<00:00:29.480> usual<00:00:29.720> meaning 00:00:30.749 --> 00:00:30.759 align:start position:0% separation this is not the usual meaning 00:00:30.759 --> 00:00:33.270 align:start position:0% separation this is not the usual meaning and<00:00:30.920> you'll<00:00:31.199> notice<00:00:31.599> that<00:00:31.800> I'll<00:00:32.079> only<00:00:32.439> mention 00:00:33.270 --> 00:00:33.280 align:start position:0% and you'll notice that I'll only mention 00:00:33.280 --> 00:00:36.590 align:start position:0% and you'll notice that I'll only mention proposers<00:00:33.840> and<00:00:34.040> Builders<00:00:34.920> towards<00:00:35.480> the<00:00:35.760> last 00:00:36.590 --> 00:00:36.600 align:start position:0% proposers and Builders towards the last 00:00:36.600 --> 00:00:38.150 align:start position:0% proposers and Builders towards the last couple<00:00:36.840> of 00:00:38.150 --> 00:00:38.160 align:start position:0% couple of 00:00:38.160 --> 00:00:40.869 align:start position:0% couple of slides<00:00:39.160> um<00:00:39.640> the<00:00:39.960> talk<00:00:40.239> is<00:00:40.360> going<00:00:40.520> to<00:00:40.680> be 00:00:40.869 --> 00:00:40.879 align:start position:0% slides um the talk is going to be 00:00:40.879 --> 00:00:43.510 align:start position:0% slides um the talk is going to be divided<00:00:41.239> in<00:00:41.520> three 00:00:43.510 --> 00:00:43.520 align:start position:0% divided in three 00:00:43.520 --> 00:00:45.790 align:start position:0% divided in three sections<00:00:44.520> the<00:00:44.680> first<00:00:44.960> section<00:00:45.440> I<00:00:45.520> want<00:00:45.680> to 00:00:45.790 --> 00:00:45.800 align:start position:0% sections the first section I want to 00:00:45.800 --> 00:00:49.110 align:start position:0% sections the first section I want to convince<00:00:46.239> you<00:00:46.360> for<00:00:46.520> a<00:00:46.640> while<00:00:47.000> that<00:00:48.120> um 00:00:49.110 --> 00:00:49.120 align:start position:0% convince you for a while that um 00:00:49.120 --> 00:00:51.590 align:start position:0% convince you for a while that um dividing<00:00:50.000> the<00:00:50.160> payload<00:00:51.000> the<00:00:51.160> execution 00:00:51.590 --> 00:00:51.600 align:start position:0% dividing the payload the execution 00:00:51.600 --> 00:00:53.430 align:start position:0% dividing the payload the execution payload<00:00:52.000> from<00:00:52.120> the<00:00:52.280> consensus<00:00:52.719> block<00:00:53.280> is 00:00:53.430 --> 00:00:53.440 align:start position:0% payload from the consensus block is 00:00:53.440 --> 00:00:55.349 align:start position:0% payload from the consensus block is something<00:00:53.719> that<00:00:53.879> is<00:00:54.120> necessary<00:00:54.559> in<00:00:54.680> ethereum 00:00:55.349 --> 00:00:55.359 align:start position:0% something that is necessary in ethereum 00:00:55.359 --> 00:00:57.830 align:start position:0% something that is necessary in ethereum it<00:00:55.480> is<00:00:55.680> highly<00:00:55.960> beneficial<00:00:56.920> it<00:00:57.039> is<00:00:57.160> a<00:00:57.320> scaling 00:00:57.830 --> 00:00:57.840 align:start position:0% it is highly beneficial it is a scaling 00:00:57.840 --> 00:01:00.110 align:start position:0% it is highly beneficial it is a scaling factor<00:00:58.399> and<00:00:58.559> it<00:00:58.719> enables<00:00:59.320> other<00:00:59.559> scaling 00:01:00.110 --> 00:01:00.120 align:start position:0% factor and it enables other scaling 00:01:00.120 --> 00:01:01.869 align:start position:0% factor and it enables other scaling Solutions<00:01:00.480> like<00:01:00.600> PR<00:01:00.920> Das<00:01:01.359> to<00:01:01.600> actually 00:01:01.869 --> 00:01:01.879 align:start position:0% Solutions like PR Das to actually 00:01:01.879 --> 00:01:04.509 align:start position:0% Solutions like PR Das to actually fulfill<00:01:02.359> its<00:01:02.559> full 00:01:04.509 --> 00:01:04.519 align:start position:0% fulfill its full 00:01:04.519 --> 00:01:07.270 align:start position:0% fulfill its full potential<00:01:05.519> we<00:01:05.680> have<00:01:06.000> this<00:01:06.360> problem<00:01:06.960> that<00:01:07.119> we 00:01:07.270 --> 00:01:07.280 align:start position:0% potential we have this problem that we 00:01:07.280 --> 00:01:09.429 align:start position:0% potential we have this problem that we have<00:01:07.439> since<00:01:07.680> emerge<00:01:08.439> which<00:01:08.560> is<00:01:08.799> our<00:01:09.119> Tech 00:01:09.429 --> 00:01:09.439 align:start position:0% have since emerge which is our Tech 00:01:09.439 --> 00:01:11.749 align:start position:0% have since emerge which is our Tech depth<00:01:10.000> that<00:01:10.159> we<00:01:10.320> adopted<00:01:10.720> this<00:01:10.920> minimalistic 00:01:11.749 --> 00:01:11.759 align:start position:0% depth that we adopted this minimalistic 00:01:11.759 --> 00:01:14.749 align:start position:0% depth that we adopted this minimalistic way<00:01:12.159> of<00:01:12.320> merging<00:01:13.000> out<00:01:13.200> of<00:01:13.560> proof<00:01:13.799> of<00:01:14.000> work<00:01:14.600> in 00:01:14.749 --> 00:01:14.759 align:start position:0% way of merging out of proof of work in 00:01:14.759 --> 00:01:17.670 align:start position:0% way of merging out of proof of work in which<00:01:14.960> we<00:01:15.759> included<00:01:16.360> the<00:01:16.600> execution<00:01:17.040> block 00:01:17.670 --> 00:01:17.680 align:start position:0% which we included the execution block 00:01:17.680 --> 00:01:19.469 align:start position:0% which we included the execution block the<00:01:17.799> one<00:01:17.960> that<00:01:18.119> has<00:01:18.240> the<00:01:18.439> transactions<00:01:19.320> and 00:01:19.469 --> 00:01:19.479 align:start position:0% the one that has the transactions and 00:01:19.479 --> 00:01:22.429 align:start position:0% the one that has the transactions and everything<00:01:19.759> that<00:01:19.880> we<00:01:20.240> need<00:01:21.240> to<00:01:21.759> like<00:01:21.960> modify 00:01:22.429 --> 00:01:22.439 align:start position:0% everything that we need to like modify 00:01:22.439 --> 00:01:24.510 align:start position:0% everything that we need to like modify the<00:01:22.560> ethereum<00:01:22.960> machine<00:01:23.680> inside<00:01:24.200> of<00:01:24.360> the 00:01:24.510 --> 00:01:24.520 align:start position:0% the ethereum machine inside of the 00:01:24.520 --> 00:01:26.390 align:start position:0% the ethereum machine inside of the consensus<00:01:25.040> block<00:01:25.920> that<00:01:26.079> has<00:01:26.280> the 00:01:26.390 --> 00:01:26.400 align:start position:0% consensus block that has the 00:01:26.400 --> 00:01:28.310 align:start position:0% consensus block that has the attestations<00:01:27.119> the<00:01:27.240> deposits<00:01:27.720> the<00:01:27.880> exits 00:01:28.310 --> 00:01:28.320 align:start position:0% attestations the deposits the exits 00:01:28.320 --> 00:01:29.910 align:start position:0% attestations the deposits the exits everything<00:01:28.640> that<00:01:28.720> we<00:01:28.840> need<00:01:29.240> to<00:01:29.479> decide<00:01:29.759> what 00:01:29.910 --> 00:01:29.920 align:start position:0% everything that we need to decide what 00:01:29.920 --> 00:01:32.069 align:start position:0% everything that we need to decide what what<00:01:30.040> is<00:01:30.119> our<00:01:30.320> current<00:01:30.759> head<00:01:31.759> and<00:01:31.960> we 00:01:32.069 --> 00:01:32.079 align:start position:0% what is our current head and we 00:01:32.079 --> 00:01:34.429 align:start position:0% what is our current head and we distribute<00:01:32.560> them<00:01:32.759> both<00:01:33.240> together<00:01:34.000> this<00:01:34.159> makes 00:01:34.429 --> 00:01:34.439 align:start position:0% distribute them both together this makes 00:01:34.439 --> 00:01:36.590 align:start position:0% distribute them both together this makes for<00:01:34.600> a<00:01:34.799> large<00:01:35.159> Chun<00:01:35.560> of<00:01:35.759> data<00:01:36.040> that<00:01:36.159> is 00:01:36.590 --> 00:01:36.600 align:start position:0% for a large Chun of data that is 00:01:36.600 --> 00:01:38.749 align:start position:0% for a large Chun of data that is distributed<00:01:37.439> among<00:01:37.640> the 00:01:38.749 --> 00:01:38.759 align:start position:0% distributed among the 00:01:38.759 --> 00:01:42.789 align:start position:0% distributed among the nodes<00:01:39.759> when<00:01:40.720> this<00:01:41.040> data<00:01:41.600> has<00:01:42.079> logically 00:01:42.789 --> 00:01:42.799 align:start position:0% nodes when this data has logically 00:01:42.799 --> 00:01:44.789 align:start position:0% nodes when this data has logically different<00:01:43.640> purposes<00:01:44.159> and<00:01:44.360> logically 00:01:44.789 --> 00:01:44.799 align:start position:0% different purposes and logically 00:01:44.799 --> 00:01:45.870 align:start position:0% different purposes and logically different 00:01:45.870 --> 00:01:45.880 align:start position:0% different 00:01:45.880 --> 00:01:49.830 align:start position:0% different validations<00:01:46.880> what<00:01:47.040> a<00:01:47.200> node<00:01:47.560> does<00:01:48.640> when<00:01:49.640> when 00:01:49.830 --> 00:01:49.840 align:start position:0% validations what a node does when when 00:01:49.840 --> 00:01:52.389 align:start position:0% validations what a node does when when it<00:01:50.280> reaches<00:01:50.759> gets<00:01:51.000> a<00:01:51.159> block<00:01:51.600> it<00:01:51.759> needs<00:01:52.000> to<00:01:52.240> get 00:01:52.389 --> 00:01:52.399 align:start position:0% it reaches gets a block it needs to get 00:01:52.399 --> 00:01:54.950 align:start position:0% it reaches gets a block it needs to get to<00:01:52.640> consensus<00:01:53.320> in<00:01:53.479> two<00:01:53.680> different<00:01:54.119> things<00:01:54.759> one 00:01:54.950 --> 00:01:54.960 align:start position:0% to consensus in two different things one 00:01:54.960 --> 00:01:56.230 align:start position:0% to consensus in two different things one thing<00:01:55.119> is<00:01:55.280> what<00:01:55.399> is<00:01:55.479> the<00:01:55.680> status<00:01:56.000> of<00:01:56.119> the 00:01:56.230 --> 00:01:56.240 align:start position:0% thing is what is the status of the 00:01:56.240 --> 00:01:58.149 align:start position:0% thing is what is the status of the network<00:01:56.640> what<00:01:56.759> is<00:01:57.159> the<00:01:57.320> execution<00:01:57.759> status<00:01:58.079> of 00:01:58.149 --> 00:01:58.159 align:start position:0% network what is the execution status of 00:01:58.159 --> 00:02:00.469 align:start position:0% network what is the execution status of the<00:01:58.280> network<00:01:58.840> the<00:01:59.000> validity<00:01:59.399> of<00:01:59.520> the<00:01:59.600> block 00:02:00.469 --> 00:02:00.479 align:start position:0% the network the validity of the block 00:02:00.479 --> 00:02:02.190 align:start position:0% the network the validity of the block and<00:02:00.640> the<00:02:00.759> other<00:02:01.000> thing<00:02:01.240> is<00:02:01.680> given<00:02:02.000> two 00:02:02.190 --> 00:02:02.200 align:start position:0% and the other thing is given two 00:02:02.200 --> 00:02:05.469 align:start position:0% and the other thing is given two different<00:02:02.520> views<00:02:03.119> of<00:02:03.240> the<00:02:03.520> network<00:02:04.520> which<00:02:04.719> one 00:02:05.469 --> 00:02:05.479 align:start position:0% different views of the network which one 00:02:05.479 --> 00:02:07.469 align:start position:0% different views of the network which one even<00:02:05.759> both<00:02:05.960> of<00:02:06.079> them<00:02:06.320> possibly<00:02:06.719> valid<00:02:07.360> which 00:02:07.469 --> 00:02:07.479 align:start position:0% even both of them possibly valid which 00:02:07.479 --> 00:02:09.109 align:start position:0% even both of them possibly valid which one<00:02:07.640> is<00:02:07.759> the<00:02:07.880> one<00:02:08.039> that<00:02:08.160> we<00:02:08.360> consider<00:02:08.800> the<00:02:08.959> head 00:02:09.109 --> 00:02:09.119 align:start position:0% one is the one that we consider the head 00:02:09.119 --> 00:02:11.670 align:start position:0% one is the one that we consider the head of<00:02:09.200> the<00:02:09.319> chain<00:02:10.039> these<00:02:10.239> two<00:02:10.479> validations<00:02:11.039> are 00:02:11.670 --> 00:02:11.680 align:start position:0% of the chain these two validations are 00:02:11.680 --> 00:02:13.910 align:start position:0% of the chain these two validations are completely<00:02:12.200> independent<00:02:13.200> and<00:02:13.319> they<00:02:13.440> are<00:02:13.640> done 00:02:13.910 --> 00:02:13.920 align:start position:0% completely independent and they are done 00:02:13.920 --> 00:02:15.309 align:start position:0% completely independent and they are done by<00:02:14.080> two<00:02:14.280> different<00:02:14.560> clients<00:02:14.959> even<00:02:15.160> two 00:02:15.309 --> 00:02:15.319 align:start position:0% by two different clients even two 00:02:15.319 --> 00:02:17.190 align:start position:0% by two different clients even two different<00:02:15.560> soft<00:02:15.920> pieces<00:02:16.200> of<00:02:16.400> software<00:02:17.000> the 00:02:17.190 --> 00:02:17.200 align:start position:0% different soft pieces of software the 00:02:17.200 --> 00:02:18.990 align:start position:0% different soft pieces of software the validator<00:02:17.640> runs<00:02:17.879> in<00:02:18.040> the<00:02:18.400> running<00:02:18.640> in<00:02:18.720> the 00:02:18.990 --> 00:02:19.000 align:start position:0% validator runs in the running in the 00:02:19.000 --> 00:02:22.509 align:start position:0% validator runs in the running in the computers<00:02:20.000> the<00:02:20.160> execution<00:02:21.120> consensus<00:02:22.120> is 00:02:22.509 --> 00:02:22.519 align:start position:0% computers the execution consensus is 00:02:22.519 --> 00:02:25.150 align:start position:0% computers the execution consensus is about<00:02:22.879> validity<00:02:23.480> the<00:02:23.640> consensus<00:02:24.280> consensus 00:02:25.150 --> 00:02:25.160 align:start position:0% about validity the consensus consensus 00:02:25.160 --> 00:02:27.110 align:start position:0% about validity the consensus consensus is<00:02:25.360> about<00:02:25.800> which<00:02:26.000> one<00:02:26.200> of<00:02:26.360> the<00:02:26.519> world<00:02:27.000> the 00:02:27.110 --> 00:02:27.120 align:start position:0% is about which one of the world the 00:02:27.120 --> 00:02:32.949 align:start position:0% is about which one of the world the viewers<00:02:27.599> of<00:02:27.760> the<00:02:27.879> world<00:02:28.280> is<00:02:28.400> the<00:02:28.519> current<00:02:28.879> one 00:02:32.949 --> 00:02:32.959 align:start position:0% 00:02:32.959 --> 00:02:35.350 align:start position:0% because<00:02:33.480> of<00:02:33.640> our<00:02:33.840> Tech<00:02:34.160> Deb<00:02:34.760> the<00:02:34.879> way<00:02:35.080> that<00:02:35.239> we 00:02:35.350 --> 00:02:35.360 align:start position:0% because of our Tech Deb the way that we 00:02:35.360 --> 00:02:38.630 align:start position:0% because of our Tech Deb the way that we validate<00:02:35.760> blocks<00:02:36.760> puts<00:02:37.280> all<00:02:37.480> of<00:02:37.680> the<00:02:37.879> strain 00:02:38.630 --> 00:02:38.640 align:start position:0% validate blocks puts all of the strain 00:02:38.640 --> 00:02:41.149 align:start position:0% validate blocks puts all of the strain of<00:02:38.800> the<00:02:39.000> network<00:02:39.680> in<00:02:39.920> the<00:02:40.120> very<00:02:40.440> first<00:02:40.800> few 00:02:41.149 --> 00:02:41.159 align:start position:0% of the network in the very first few 00:02:41.159 --> 00:02:43.990 align:start position:0% of the network in the very first few seconds<00:02:41.640> of<00:02:41.800> the<00:02:41.920> slot<00:02:42.720> a<00:02:42.879> block<00:02:43.159> is<00:02:43.280> broadcast 00:02:43.990 --> 00:02:44.000 align:start position:0% seconds of the slot a block is broadcast 00:02:44.000 --> 00:02:46.390 align:start position:0% seconds of the slot a block is broadcast at<00:02:44.120> the<00:02:44.239> beginning<00:02:44.519> of<00:02:44.640> a<00:02:44.800> slot<00:02:45.800> and<00:02:46.040> it<00:02:46.200> needs 00:02:46.390 --> 00:02:46.400 align:start position:0% at the beginning of a slot and it needs 00:02:46.400 --> 00:02:47.910 align:start position:0% at the beginning of a slot and it needs to<00:02:46.519> be<00:02:46.720> validated<00:02:47.280> it<00:02:47.480> needs<00:02:47.640> to<00:02:47.760> be 00:02:47.910 --> 00:02:47.920 align:start position:0% to be validated it needs to be 00:02:47.920 --> 00:02:49.710 align:start position:0% to be validated it needs to be downloaded<00:02:48.480> entirely<00:02:49.000> by<00:02:49.319> by<00:02:49.400> the<00:02:49.519> whole 00:02:49.710 --> 00:02:49.720 align:start position:0% downloaded entirely by by the whole 00:02:49.720 --> 00:02:52.270 align:start position:0% downloaded entirely by by the whole network<00:02:50.360> and<00:02:50.519> by<00:02:50.680> 4<00:02:51.000> seconds<00:02:51.599> validators<00:02:52.120> need 00:02:52.270 --> 00:02:52.280 align:start position:0% network and by 4 seconds validators need 00:02:52.280 --> 00:02:54.550 align:start position:0% network and by 4 seconds validators need to<00:02:52.480> have<00:02:52.640> already<00:02:53.200> checked<00:02:53.560> consensus 00:02:54.550 --> 00:02:54.560 align:start position:0% to have already checked consensus 00:02:54.560 --> 00:02:56.589 align:start position:0% to have already checked consensus executed<00:02:55.040> the<00:02:55.239> execution<00:02:56.040> check<00:02:56.360> that<00:02:56.480> the 00:02:56.589 --> 00:02:56.599 align:start position:0% executed the execution check that the 00:02:56.599 --> 00:02:58.710 align:start position:0% executed the execution check that the blob<00:02:56.920> data<00:02:57.159> was<00:02:57.360> available<00:02:58.120> in<00:02:58.239> the<00:02:58.360> future 00:02:58.710 --> 00:02:58.720 align:start position:0% blob data was available in the future 00:02:58.720 --> 00:03:00.589 align:start position:0% blob data was available in the future check<00:02:59.040> that<00:02:59.239> inclusion<00:02:59.640> list<00:02:59.840> this<00:03:00.000> were're 00:03:00.589 --> 00:03:00.599 align:start position:0% check that inclusion list this were're 00:03:00.599 --> 00:03:04.309 align:start position:0% check that inclusion list this were're satisfied<00:03:01.599> and<00:03:02.360> a<00:03:02.560> test<00:03:02.800> for<00:03:03.040> this<00:03:03.879> the<00:03:04.080> rest 00:03:04.309 --> 00:03:04.319 align:start position:0% satisfied and a test for this the rest 00:03:04.319 --> 00:03:06.589 align:start position:0% satisfied and a test for this the rest of<00:03:04.440> the<00:03:04.599> slots<00:03:04.959> is<00:03:05.159> useless<00:03:05.799> time<00:03:06.080> essentially 00:03:06.589 --> 00:03:06.599 align:start position:0% of the slots is useless time essentially 00:03:06.599 --> 00:03:08.670 align:start position:0% of the slots is useless time essentially we're<00:03:06.840> just<00:03:07.200> counting<00:03:07.680> attestations 00:03:08.670 --> 00:03:08.680 align:start position:0% we're just counting attestations 00:03:08.680 --> 00:03:10.509 align:start position:0% we're just counting attestations aggregating<00:03:09.280> them<00:03:09.640> the<00:03:09.799> node<00:03:10.080> doesn't<00:03:10.319> do 00:03:10.509 --> 00:03:10.519 align:start position:0% aggregating them the node doesn't do 00:03:10.519 --> 00:03:12.470 align:start position:0% aggregating them the node doesn't do anything<00:03:10.840> if<00:03:11.040> anyone<00:03:11.440> here<00:03:11.640> runs<00:03:11.879> a<00:03:12.040> node 00:03:12.470 --> 00:03:12.480 align:start position:0% anything if anyone here runs a node 00:03:12.480 --> 00:03:15.149 align:start position:0% anything if anyone here runs a node you're<00:03:12.640> going<00:03:12.760> to<00:03:12.959> see<00:03:13.440> here<00:03:14.159> the<00:03:14.280> fans<00:03:14.840> going 00:03:15.149 --> 00:03:15.159 align:start position:0% you're going to see here the fans going 00:03:15.159 --> 00:03:18.630 align:start position:0% you're going to see here the fans going off<00:03:15.599> exactly<00:03:16.200> every<00:03:16.440> 12 00:03:18.630 --> 00:03:18.640 align:start position:0% off exactly every 12 00:03:18.640 --> 00:03:21.030 align:start position:0% off exactly every 12 seconds<00:03:19.640> so<00:03:19.879> that's<00:03:20.319> what<00:03:20.480> the<00:03:20.599> ethereum 00:03:21.030 --> 00:03:21.040 align:start position:0% seconds so that's what the ethereum 00:03:21.040 --> 00:03:24.070 align:start position:0% seconds so that's what the ethereum validation<00:03:21.560> is<00:03:22.080> today<00:03:23.080> and<00:03:23.400> the<00:03:23.560> question<00:03:23.879> is 00:03:24.070 --> 00:03:24.080 align:start position:0% validation is today and the question is 00:03:24.080 --> 00:03:26.990 align:start position:0% validation is today and the question is can<00:03:24.239> we<00:03:24.480> make<00:03:24.760> this<00:03:25.200> better<00:03:26.200> can<00:03:26.360> we<00:03:26.560> make<00:03:26.760> the 00:03:26.990 --> 00:03:27.000 align:start position:0% can we make this better can we make the 00:03:27.000 --> 00:03:29.229 align:start position:0% can we make this better can we make the timings<00:03:27.480> better<00:03:27.879> presumably<00:03:28.519> yes<00:03:28.720> we<00:03:28.840> have<00:03:29.000> 4 00:03:29.229 --> 00:03:29.239 align:start position:0% timings better presumably yes we have 4 00:03:29.239 --> 00:03:30.990 align:start position:0% timings better presumably yes we have 4 seconds<00:03:29.519> and<00:03:29.959> we<00:03:30.080> don't<00:03:30.280> use<00:03:30.519> those<00:03:30.680> for 00:03:30.990 --> 00:03:31.000 align:start position:0% seconds and we don't use those for 00:03:31.000 --> 00:03:32.990 align:start position:0% seconds and we don't use those for seconds<00:03:31.760> but<00:03:31.879> the<00:03:32.040> problem<00:03:32.400> is<00:03:32.799> that 00:03:32.990 --> 00:03:33.000 align:start position:0% seconds but the problem is that 00:03:33.000 --> 00:03:37.229 align:start position:0% seconds but the problem is that validators<00:03:33.640> are<00:03:34.640> incentivized<00:03:35.640> to<00:03:36.239> actually 00:03:37.229 --> 00:03:37.239 align:start position:0% validators are incentivized to actually 00:03:37.239 --> 00:03:39.429 align:start position:0% validators are incentivized to actually propose<00:03:37.760> their<00:03:37.920> blocks<00:03:38.360> as<00:03:38.519> late<00:03:38.760> as<00:03:39.000> possible 00:03:39.429 --> 00:03:39.439 align:start position:0% propose their blocks as late as possible 00:03:39.439 --> 00:03:41.229 align:start position:0% propose their blocks as late as possible so<00:03:39.599> that<00:03:39.720> they<00:03:39.840> can<00:03:40.040> extract<00:03:40.400> more<00:03:40.560> M<00:03:40.959> out<00:03:41.080> of 00:03:41.229 --> 00:03:41.239 align:start position:0% so that they can extract more M out of 00:03:41.239 --> 00:03:43.429 align:start position:0% so that they can extract more M out of them<00:03:41.799> and<00:03:41.959> these<00:03:42.120> timing<00:03:42.439> games<00:03:42.840> make 00:03:43.429 --> 00:03:43.439 align:start position:0% them and these timing games make 00:03:43.439 --> 00:03:45.830 align:start position:0% them and these timing games make twigling<00:03:44.080> with<00:03:44.280> this<00:03:44.920> these<00:03:45.120> timings<00:03:45.519> for 00:03:45.830 --> 00:03:45.840 align:start position:0% twigling with this these timings for 00:03:45.840 --> 00:03:48.110 align:start position:0% twigling with this these timings for attestations<00:03:46.840> a<00:03:47.159> an<00:03:47.319> impossible<00:03:47.760> problem<00:03:48.000> to 00:03:48.110 --> 00:03:48.120 align:start position:0% attestations a an impossible problem to 00:03:48.120 --> 00:03:50.429 align:start position:0% attestations a an impossible problem to solve<00:03:48.680> if<00:03:48.799> we<00:03:49.040> gave<00:03:49.480> more<00:03:49.760> time<00:03:50.000> to<00:03:50.200> actually 00:03:50.429 --> 00:03:50.439 align:start position:0% solve if we gave more time to actually 00:03:50.439 --> 00:03:53.149 align:start position:0% solve if we gave more time to actually sync<00:03:50.920> better<00:03:51.200> blocks<00:03:51.799> larger<00:03:52.200> blocks<00:03:52.959> have 00:03:53.149 --> 00:03:53.159 align:start position:0% sync better blocks larger blocks have 00:03:53.159 --> 00:03:55.990 align:start position:0% sync better blocks larger blocks have more<00:03:53.439> blobs<00:03:53.840> in<00:03:53.959> the<00:03:54.519> network<00:03:55.519> what<00:03:55.720> would 00:03:55.990 --> 00:03:56.000 align:start position:0% more blobs in the network what would 00:03:56.000 --> 00:03:57.229 align:start position:0% more blobs in the network what would happen<00:03:56.280> is<00:03:56.400> that<00:03:56.560> validator<00:03:56.959> would<00:03:57.120> just 00:03:57.229 --> 00:03:57.239 align:start position:0% happen is that validator would just 00:03:57.239 --> 00:04:02.630 align:start position:0% happen is that validator would just propose<00:03:57.560> later<00:03:57.879> and<00:03:58.040> extract<00:03:58.360> more<00:03:58.519> m 00:04:02.630 --> 00:04:02.640 align:start position:0% 00:04:02.640 --> 00:04:05.789 align:start position:0% so<00:04:03.000> why<00:04:03.439> separating<00:04:04.079> them<00:04:04.840> since<00:04:05.159> we<00:04:05.319> do<00:04:05.519> not 00:04:05.789 --> 00:04:05.799 align:start position:0% so why separating them since we do not 00:04:05.799 --> 00:04:07.949 align:start position:0% so why separating them since we do not need<00:04:06.159> to<00:04:06.360> validate<00:04:06.840> execution<00:04:07.280> to<00:04:07.480> decide 00:04:07.949 --> 00:04:07.959 align:start position:0% need to validate execution to decide 00:04:07.959 --> 00:04:11.429 align:start position:0% need to validate execution to decide what<00:04:08.120> is<00:04:08.239> our<00:04:08.640> head<00:04:09.640> why<00:04:09.840> not<00:04:10.159> just<00:04:10.799> broadcast 00:04:11.429 --> 00:04:11.439 align:start position:0% what is our head why not just broadcast 00:04:11.439 --> 00:04:13.630 align:start position:0% what is our head why not just broadcast the<00:04:11.560> block<00:04:12.360> which<00:04:12.480> is<00:04:12.599> a<00:04:12.760> minimal<00:04:13.200> block<00:04:13.519> which 00:04:13.630 --> 00:04:13.640 align:start position:0% the block which is a minimal block which 00:04:13.640 --> 00:04:16.030 align:start position:0% the block which is a minimal block which is<00:04:13.760> just<00:04:14.000> consensus<00:04:14.920> validate<00:04:15.400> consensus 00:04:16.030 --> 00:04:16.040 align:start position:0% is just consensus validate consensus 00:04:16.040 --> 00:04:18.110 align:start position:0% is just consensus validate consensus decide<00:04:16.440> what<00:04:16.600> is<00:04:16.959> our<00:04:17.280> status<00:04:17.600> of<00:04:17.759> the<00:04:17.959> of<00:04:18.040> the 00:04:18.110 --> 00:04:18.120 align:start position:0% decide what is our status of the of the 00:04:18.120 --> 00:04:20.590 align:start position:0% decide what is our status of the of the chain<00:04:18.600> and<00:04:18.720> then<00:04:18.919> use<00:04:19.359> the<00:04:19.600> rest<00:04:19.880> of<00:04:20.079> those<00:04:20.280> 12 00:04:20.590 --> 00:04:20.600 align:start position:0% chain and then use the rest of those 12 00:04:20.600 --> 00:04:22.670 align:start position:0% chain and then use the rest of those 12 seconds<00:04:21.120> to<00:04:21.320> validate<00:04:21.720> execution<00:04:22.280> check<00:04:22.560> if 00:04:22.670 --> 00:04:22.680 align:start position:0% seconds to validate execution check if 00:04:22.680 --> 00:04:25.150 align:start position:0% seconds to validate execution check if the<00:04:22.800> blobs<00:04:23.120> are<00:04:23.720> available<00:04:24.720> validate 00:04:25.150 --> 00:04:25.160 align:start position:0% the blobs are available validate 00:04:25.160 --> 00:04:27.189 align:start position:0% the blobs are available validate inclusion<00:04:25.600> list<00:04:26.120> do<00:04:26.440> all<00:04:26.600> of<00:04:26.720> the<00:04:26.880> stuff<00:04:27.120> that 00:04:27.189 --> 00:04:27.199 align:start position:0% inclusion list do all of the stuff that 00:04:27.199 --> 00:04:30.550 align:start position:0% inclusion list do all of the stuff that is<00:04:27.360> actually<00:04:27.680> heavy<00:04:28.320> in<00:04:28.840> the 00:04:30.550 --> 00:04:30.560 align:start position:0% is actually heavy in the 00:04:30.560 --> 00:04:32.870 align:start position:0% is actually heavy in the High<00:04:30.840> latency<00:04:31.479> path<00:04:31.960> and<00:04:32.080> the<00:04:32.199> low<00:04:32.400> latency 00:04:32.870 --> 00:04:32.880 align:start position:0% High latency path and the low latency 00:04:32.880 --> 00:04:34.590 align:start position:0% High latency path and the low latency path<00:04:33.120> which<00:04:33.199> is<00:04:33.360> validation<00:04:33.720> of<00:04:33.880> consensus 00:04:34.590 --> 00:04:34.600 align:start position:0% path which is validation of consensus 00:04:34.600 --> 00:04:36.749 align:start position:0% path which is validation of consensus that<00:04:34.759> takes<00:04:35.400> two<00:04:35.639> seconds<00:04:36.120> you<00:04:36.240> just<00:04:36.400> download 00:04:36.749 --> 00:04:36.759 align:start position:0% that takes two seconds you just download 00:04:36.759 --> 00:04:38.830 align:start position:0% that takes two seconds you just download the<00:04:36.919> tiny<00:04:37.160> block<00:04:37.680> validated<00:04:38.120> immediately<00:04:38.680> it 00:04:38.830 --> 00:04:38.840 align:start position:0% the tiny block validated immediately it 00:04:38.840 --> 00:04:41.110 align:start position:0% the tiny block validated immediately it takes<00:04:39.360> 7<00:04:39.840> 70<00:04:40.199> milliseconds<00:04:40.720> today<00:04:41.000> to 00:04:41.110 --> 00:04:41.120 align:start position:0% takes 7 70 milliseconds today to 00:04:41.120 --> 00:04:43.870 align:start position:0% takes 7 70 milliseconds today to validate<00:04:41.440> the<00:04:41.520> consensus<00:04:42.039> side<00:04:42.720> and<00:04:42.919> just<00:04:43.199> a 00:04:43.870 --> 00:04:43.880 align:start position:0% validate the consensus side and just a 00:04:43.880 --> 00:04:47.110 align:start position:0% validate the consensus side and just a test<00:04:44.880> so<00:04:45.160> that's<00:04:45.759> that's<00:04:45.919> a<00:04:46.080> scaling<00:04:46.600> feature 00:04:47.110 --> 00:04:47.120 align:start position:0% test so that's that's a scaling feature 00:04:47.120 --> 00:04:50.189 align:start position:0% test so that's that's a scaling feature of<00:04:47.280> separating<00:04:47.840> the<00:04:48.120> the<00:04:48.240> payload<00:04:48.720> From<00:04:48.880> the 00:04:50.189 --> 00:04:50.199 align:start position:0% of separating the the payload From the 00:04:50.199 --> 00:04:53.070 align:start position:0% of separating the the payload From the Block<00:04:51.199> so<00:04:51.400> that<00:04:51.520> was<00:04:52.080> the<00:04:52.440> first<00:04:52.720> part<00:04:52.880> of<00:04:52.960> the 00:04:53.070 --> 00:04:53.080 align:start position:0% Block so that was the first part of the 00:04:53.080 --> 00:04:55.029 align:start position:0% Block so that was the first part of the talk<00:04:53.320> I<00:04:53.400> want<00:04:53.520> to<00:04:54.000> I<00:04:54.120> hope<00:04:54.360> I<00:04:54.520> convince<00:04:54.880> you 00:04:55.029 --> 00:04:55.039 align:start position:0% talk I want to I hope I convince you 00:04:55.039 --> 00:04:57.469 align:start position:0% talk I want to I hope I convince you that<00:04:55.280> the<00:04:55.440> separation<00:04:56.080> gives<00:04:56.320> us<00:04:56.720> a 00:04:57.469 --> 00:04:57.479 align:start position:0% that the separation gives us a 00:04:57.479 --> 00:05:00.270 align:start position:0% that the separation gives us a lot<00:04:58.479> of<00:04:58.680> benefits<00:04:59.080> for<00:04:59.240> ethereum<00:05:00.000> now<00:05:00.160> the 00:05:00.270 --> 00:05:00.280 align:start position:0% lot of benefits for ethereum now the 00:05:00.280 --> 00:05:02.550 align:start position:0% lot of benefits for ethereum now the question<00:05:00.520> is<00:05:00.800> what<00:05:01.039> have<00:05:01.360> how<00:05:01.600> can<00:05:01.720> we<00:05:01.919> achieve 00:05:02.550 --> 00:05:02.560 align:start position:0% question is what have how can we achieve 00:05:02.560 --> 00:05:05.670 align:start position:0% question is what have how can we achieve separating<00:05:03.080> the<00:05:03.199> block<00:05:03.639> from<00:05:03.960> the<00:05:04.560> payload 00:05:05.670 --> 00:05:05.680 align:start position:0% separating the block from the payload 00:05:05.680 --> 00:05:08.150 align:start position:0% separating the block from the payload and<00:05:06.680> the<00:05:06.800> minimum<00:05:07.320> features<00:05:07.680> that<00:05:07.800> we<00:05:07.919> want 00:05:08.150 --> 00:05:08.160 align:start position:0% and the minimum features that we want 00:05:08.160 --> 00:05:11.070 align:start position:0% and the minimum features that we want that<00:05:08.280> we<00:05:08.440> need<00:05:08.960> if<00:05:09.080> we<00:05:09.240> want<00:05:09.360> to<00:05:09.520> separate<00:05:10.080> them 00:05:11.070 --> 00:05:11.080 align:start position:0% that we need if we want to separate them 00:05:11.080 --> 00:05:13.950 align:start position:0% that we need if we want to separate them would<00:05:11.320> be<00:05:11.759> this<00:05:12.160> so<00:05:12.400> what's<00:05:12.639> what<00:05:12.800> we<00:05:13.479> desire 00:05:13.950 --> 00:05:13.960 align:start position:0% would be this so what's what we desire 00:05:13.960 --> 00:05:16.310 align:start position:0% would be this so what's what we desire of<00:05:14.120> such<00:05:14.280> a<00:05:14.440> s<00:05:14.759> of<00:05:14.960> such<00:05:15.120> a<00:05:15.320> separation<00:05:16.160> we 00:05:16.310 --> 00:05:16.320 align:start position:0% of such a s of such a separation we 00:05:16.320 --> 00:05:18.670 align:start position:0% of such a s of such a separation we would<00:05:17.120> want<00:05:17.320> to<00:05:17.720> have<00:05:17.880> these<00:05:18.080> validations 00:05:18.670 --> 00:05:18.680 align:start position:0% would want to have these validations 00:05:18.680 --> 00:05:21.390 align:start position:0% would want to have these validations done<00:05:19.000> completely<00:05:19.919> independent<00:05:20.919> we<00:05:21.080> want<00:05:21.240> to 00:05:21.390 --> 00:05:21.400 align:start position:0% done completely independent we want to 00:05:21.400 --> 00:05:23.309 align:start position:0% done completely independent we want to validate<00:05:21.800> the<00:05:21.919> consensus<00:05:22.360> side<00:05:22.600> in<00:05:22.680> the<00:05:22.840> fast 00:05:23.309 --> 00:05:23.319 align:start position:0% validate the consensus side in the fast 00:05:23.319 --> 00:05:26.150 align:start position:0% validate the consensus side in the fast path<00:05:23.759> and<00:05:23.919> the<00:05:24.039> execution<00:05:24.560> side<00:05:25.160> in<00:05:25.280> the<00:05:25.479> low 00:05:26.150 --> 00:05:26.160 align:start position:0% path and the execution side in the low 00:05:26.160 --> 00:05:27.590 align:start position:0% path and the execution side in the low in<00:05:26.319> the<00:05:26.440> in<00:05:26.560> the<00:05:26.680> slow 00:05:27.590 --> 00:05:27.600 align:start position:0% in the in the slow 00:05:27.600 --> 00:05:30.029 align:start position:0% in the in the slow path<00:05:28.600> we<00:05:28.720> want<00:05:28.880> to<00:05:29.000> separate<00:05:29.280> the<00:05:29.360> propag<00:05:29.960> of 00:05:30.029 --> 00:05:30.039 align:start position:0% path we want to separate the propag of 00:05:30.039 --> 00:05:31.790 align:start position:0% path we want to separate the propag of these<00:05:30.160> two<00:05:30.319> blocks<00:05:30.720> the<00:05:30.919> large<00:05:31.240> chunks<00:05:31.639> of 00:05:31.790 --> 00:05:31.800 align:start position:0% these two blocks the large chunks of 00:05:31.800 --> 00:05:33.950 align:start position:0% these two blocks the large chunks of transactions<00:05:32.759> might<00:05:32.960> take<00:05:33.160> longer<00:05:33.440> to<00:05:33.600> come 00:05:33.950 --> 00:05:33.960 align:start position:0% transactions might take longer to come 00:05:33.960 --> 00:05:35.629 align:start position:0% transactions might take longer to come the<00:05:34.120> blobs<00:05:34.520> that<00:05:34.639> are<00:05:34.800> the<00:05:35.000> huge<00:05:35.240> chance<00:05:35.520> of 00:05:35.629 --> 00:05:35.639 align:start position:0% the blobs that are the huge chance of 00:05:35.639 --> 00:05:37.309 align:start position:0% the blobs that are the huge chance of transaction<00:05:36.120> might<00:05:36.319> take<00:05:36.479> longer<00:05:36.800> to<00:05:37.000> to<00:05:37.199> to 00:05:37.309 --> 00:05:37.319 align:start position:0% transaction might take longer to to to 00:05:37.319 --> 00:05:40.270 align:start position:0% transaction might take longer to to to come<00:05:37.800> we<00:05:37.919> do<00:05:38.080> not<00:05:38.240> need<00:05:38.400> to<00:05:38.560> have<00:05:38.720> a<00:05:39.000> very<00:05:39.360> high 00:05:40.270 --> 00:05:40.280 align:start position:0% come we do not need to have a very high 00:05:40.280 --> 00:05:42.790 align:start position:0% come we do not need to have a very high uh<00:05:40.440> Uplink<00:05:41.160> bandwidth<00:05:41.720> to<00:05:41.919> submit<00:05:42.280> the<00:05:42.360> blobs 00:05:42.790 --> 00:05:42.800 align:start position:0% uh Uplink bandwidth to submit the blobs 00:05:42.800 --> 00:05:44.790 align:start position:0% uh Uplink bandwidth to submit the blobs because<00:05:43.039> it<00:05:43.160> takes<00:05:43.400> 12<00:05:43.720> seconds<00:05:44.039> to<00:05:44.560> be 00:05:44.790 --> 00:05:44.800 align:start position:0% because it takes 12 seconds to be 00:05:44.800 --> 00:05:47.230 align:start position:0% because it takes 12 seconds to be disseminated<00:05:45.680> so<00:05:46.039> we<00:05:46.160> solve<00:05:46.520> the<00:05:46.600> bottlenecks 00:05:47.230 --> 00:05:47.240 align:start position:0% disseminated so we solve the bottlenecks 00:05:47.240 --> 00:05:48.950 align:start position:0% disseminated so we solve the bottlenecks that<00:05:47.400> we<00:05:47.560> have<00:05:47.759> we<00:05:47.880> have<00:05:48.039> today<00:05:48.479> in<00:05:48.720> things 00:05:48.950 --> 00:05:48.960 align:start position:0% that we have we have today in things 00:05:48.960 --> 00:05:52.070 align:start position:0% that we have we have today in things like<00:05:49.120> perer<00:05:49.400> D<00:05:50.160> or<00:05:50.479> full 00:05:52.070 --> 00:05:52.080 align:start position:0% like perer D or full 00:05:52.080 --> 00:05:55.390 align:start position:0% like perer D or full D<00:05:53.080> and<00:05:53.240> we<00:05:53.319> see<00:05:53.560> immediately<00:05:54.039> one<00:05:54.319> problem<00:05:55.240> and 00:05:55.390 --> 00:05:55.400 align:start position:0% D and we see immediately one problem and 00:05:55.400 --> 00:05:57.790 align:start position:0% D and we see immediately one problem and is<00:05:55.639> that<00:05:55.960> well<00:05:56.520> since<00:05:56.759> now<00:05:56.960> you<00:05:57.080> cannot<00:05:57.440> sign 00:05:57.790 --> 00:05:57.800 align:start position:0% is that well since now you cannot sign 00:05:57.800 --> 00:05:59.629 align:start position:0% is that well since now you cannot sign the<00:05:57.919> block<00:05:58.520> with<00:05:58.759> with<00:05:58.880> the<00:05:59.039> payload<00:05:59.440> because 00:05:59.629 --> 00:05:59.639 align:start position:0% the block with with the payload because 00:05:59.639 --> 00:06:01.469 align:start position:0% the block with with the payload because because<00:05:59.800> otherwise<00:06:00.440> we<00:06:00.560> would<00:06:00.919> have<00:06:01.080> a<00:06:01.240> free 00:06:01.469 --> 00:06:01.479 align:start position:0% because otherwise we would have a free 00:06:01.479 --> 00:06:03.550 align:start position:0% because otherwise we would have a free data<00:06:01.759> availability<00:06:02.360> problem<00:06:03.039> we<00:06:03.160> need<00:06:03.319> to 00:06:03.550 --> 00:06:03.560 align:start position:0% data availability problem we need to 00:06:03.560 --> 00:06:06.270 align:start position:0% data availability problem we need to have<00:06:03.960> those<00:06:04.199> two<00:06:04.440> objects<00:06:04.759> being<00:06:05.280> signed 00:06:06.270 --> 00:06:06.280 align:start position:0% have those two objects being signed 00:06:06.280 --> 00:06:07.950 align:start position:0% have those two objects being signed that's<00:06:06.440> it<00:06:06.639> that's<00:06:06.800> not<00:06:06.919> so<00:06:07.120> hard<00:06:07.599> verifying 00:06:07.950 --> 00:06:07.960 align:start position:0% that's it that's not so hard verifying 00:06:07.960 --> 00:06:11.150 align:start position:0% that's it that's not so hard verifying signatures<00:06:08.360> is<00:06:08.479> not<00:06:08.639> a 00:06:11.150 --> 00:06:11.160 align:start position:0% 00:06:11.160 --> 00:06:13.909 align:start position:0% problem<00:06:12.160> here's<00:06:12.400> a<00:06:12.560> real<00:06:12.919> problem<00:06:13.440> the<00:06:13.599> real 00:06:13.909 --> 00:06:13.919 align:start position:0% problem here's a real problem the real 00:06:13.919 --> 00:06:16.110 align:start position:0% problem here's a real problem the real problem<00:06:14.199> is<00:06:14.360> that<00:06:14.560> now<00:06:14.960> whatever<00:06:15.319> the<00:06:15.479> situ 00:06:16.110 --> 00:06:16.120 align:start position:0% problem is that now whatever the situ 00:06:16.120 --> 00:06:18.029 align:start position:0% problem is that now whatever the situ whatever<00:06:16.599> the<00:06:17.000> designed<00:06:17.440> the<00:06:17.560> mechanism 00:06:18.029 --> 00:06:18.039 align:start position:0% whatever the designed the mechanism 00:06:18.039 --> 00:06:19.589 align:start position:0% whatever the designed the mechanism designed<00:06:18.520> to<00:06:18.720> separate<00:06:19.080> the<00:06:19.160> block<00:06:19.400> from<00:06:19.520> the 00:06:19.589 --> 00:06:19.599 align:start position:0% designed to separate the block from the 00:06:19.599 --> 00:06:21.950 align:start position:0% designed to separate the block from the payload<00:06:20.360> you<00:06:20.520> will<00:06:20.800> have<00:06:20.919> to<00:06:21.120> deal<00:06:21.479> with<00:06:21.720> new 00:06:21.950 --> 00:06:21.960 align:start position:0% payload you will have to deal with new 00:06:21.960 --> 00:06:25.390 align:start position:0% payload you will have to deal with new features<00:06:22.960> uh<00:06:23.039> with<00:06:23.199> new<00:06:23.360> situations<00:06:24.280> uh<00:06:24.440> today 00:06:25.390 --> 00:06:25.400 align:start position:0% features uh with new situations uh today 00:06:25.400 --> 00:06:28.469 align:start position:0% features uh with new situations uh today a<00:06:25.560> slot<00:06:26.080> either<00:06:26.520> has<00:06:26.680> a<00:06:26.880> block<00:06:27.400> or<00:06:27.560> it<00:06:27.720> doesn't 00:06:28.469 --> 00:06:28.479 align:start position:0% a slot either has a block or it doesn't 00:06:28.479 --> 00:06:30.230 align:start position:0% a slot either has a block or it doesn't those<00:06:28.599> are<00:06:28.759> the<00:06:28.840> two<00:06:29.000> possible<00:06:29.280> stat<00:06:29.960> if<00:06:30.080> you 00:06:30.230 --> 00:06:30.240 align:start position:0% those are the two possible stat if you 00:06:30.240 --> 00:06:31.990 align:start position:0% those are the two possible stat if you have<00:06:30.360> a<00:06:30.479> consensus<00:06:30.880> blog<00:06:31.160> you<00:06:31.240> have<00:06:31.360> a<00:06:31.479> payload 00:06:31.990 --> 00:06:32.000 align:start position:0% have a consensus blog you have a payload 00:06:32.000 --> 00:06:33.430 align:start position:0% have a consensus blog you have a payload and<00:06:32.120> if<00:06:32.199> you<00:06:32.360> don't<00:06:32.680> well<00:06:32.840> you<00:06:32.919> don't<00:06:33.120> have<00:06:33.240> a 00:06:33.430 --> 00:06:33.440 align:start position:0% and if you don't well you don't have a 00:06:33.440 --> 00:06:35.950 align:start position:0% and if you don't well you don't have a payload<00:06:34.440> but<00:06:34.840> in<00:06:34.919> a<00:06:35.080> situation<00:06:35.479> in<00:06:35.639> which<00:06:35.800> you 00:06:35.950 --> 00:06:35.960 align:start position:0% payload but in a situation in which you 00:06:35.960 --> 00:06:37.550 align:start position:0% payload but in a situation in which you have<00:06:36.120> validated<00:06:36.599> the<00:06:36.680> blog<00:06:36.919> the<00:06:37.039> consensus 00:06:37.550 --> 00:06:37.560 align:start position:0% have validated the blog the consensus 00:06:37.560 --> 00:06:39.390 align:start position:0% have validated the blog the consensus block<00:06:37.960> you<00:06:38.199> attested<00:06:38.560> to<00:06:38.720> it<00:06:38.840> and<00:06:38.960> it's<00:06:39.120> your 00:06:39.390 --> 00:06:39.400 align:start position:0% block you attested to it and it's your 00:06:39.400 --> 00:06:41.670 align:start position:0% block you attested to it and it's your head<00:06:39.960> and<00:06:40.120> the<00:06:40.240> payload<00:06:40.599> might<00:06:40.759> be<00:06:40.880> invalid<00:06:41.479> or 00:06:41.670 --> 00:06:41.680 align:start position:0% head and the payload might be invalid or 00:06:41.680 --> 00:06:43.550 align:start position:0% head and the payload might be invalid or might<00:06:41.919> not<00:06:42.120> come<00:06:42.479> or<00:06:42.639> the<00:06:42.759> blobs<00:06:43.160> were<00:06:43.319> not 00:06:43.550 --> 00:06:43.560 align:start position:0% might not come or the blobs were not 00:06:43.560 --> 00:06:45.390 align:start position:0% might not come or the blobs were not available<00:06:44.199> or<00:06:44.400> it<00:06:44.560> didn't<00:06:44.840> satisfy<00:06:45.240> an 00:06:45.390 --> 00:06:45.400 align:start position:0% available or it didn't satisfy an 00:06:45.400 --> 00:06:47.150 align:start position:0% available or it didn't satisfy an inclusion<00:06:45.800> list<00:06:46.319> the<00:06:46.440> situation<00:06:46.800> is<00:06:46.880> that<00:06:47.039> we 00:06:47.150 --> 00:06:47.160 align:start position:0% inclusion list the situation is that we 00:06:47.160 --> 00:06:49.430 align:start position:0% inclusion list the situation is that we have<00:06:47.319> two<00:06:47.639> we<00:06:47.800> have<00:06:48.000> one<00:06:48.280> extra<00:06:48.680> status<00:06:49.319> which 00:06:49.430 --> 00:06:49.440 align:start position:0% have two we have one extra status which 00:06:49.440 --> 00:06:51.070 align:start position:0% have two we have one extra status which is<00:06:49.560> the<00:06:49.759> status<00:06:50.120> in<00:06:50.280> which<00:06:50.479> the<00:06:50.639> consensus 00:06:51.070 --> 00:06:51.080 align:start position:0% is the status in which the consensus 00:06:51.080 --> 00:06:53.830 align:start position:0% is the status in which the consensus block<00:06:51.360> was<00:06:51.560> valid<00:06:52.080> and<00:06:52.240> the<00:06:52.360> payload<00:06:52.800> was<00:06:53.000> not 00:06:53.830 --> 00:06:53.840 align:start position:0% block was valid and the payload was not 00:06:53.840 --> 00:06:56.110 align:start position:0% block was valid and the payload was not and<00:06:54.039> this<00:06:54.360> gives<00:06:54.840> a<00:06:55.039> problem<00:06:55.360> which<00:06:55.479> is<00:06:55.680> a<00:06:55.800> for 00:06:56.110 --> 00:06:56.120 align:start position:0% and this gives a problem which is a for 00:06:56.120 --> 00:06:57.670 align:start position:0% and this gives a problem which is a for Choice<00:06:56.400> problem<00:06:56.680> you<00:06:56.759> need<00:06:56.919> to<00:06:57.080> change<00:06:57.360> for 00:06:57.670 --> 00:06:57.680 align:start position:0% Choice problem you need to change for 00:06:57.680 --> 00:06:59.670 align:start position:0% Choice problem you need to change for choice<00:06:57.879> to<00:06:58.080> account<00:06:58.440> for<00:06:58.680> this<00:06:59.160> for<00:06:59.360> this 00:06:59.670 --> 00:06:59.680 align:start position:0% choice to account for this for this 00:06:59.680 --> 00:07:01.670 align:start position:0% choice to account for this for this statuses<00:07:00.280> you<00:07:00.400> need<00:07:00.560> to<00:07:00.720> check<00:07:01.039> that<00:07:01.360> if<00:07:01.479> I 00:07:01.670 --> 00:07:01.680 align:start position:0% statuses you need to check that if I 00:07:01.680 --> 00:07:04.189 align:start position:0% statuses you need to check that if I attested<00:07:02.160> to<00:07:02.360> a<00:07:02.560> to<00:07:02.720> a<00:07:02.879> block<00:07:03.639> that<00:07:03.919> whose 00:07:04.189 --> 00:07:04.199 align:start position:0% attested to a to a block that whose 00:07:04.199 --> 00:07:07.469 align:start position:0% attested to a to a block that whose parent<00:07:04.639> did<00:07:04.840> not<00:07:05.039> have<00:07:05.160> a<00:07:05.319> payload<00:07:06.080> well<00:07:07.080> that 00:07:07.469 --> 00:07:07.479 align:start position:0% parent did not have a payload well that 00:07:07.479 --> 00:07:09.550 align:start position:0% parent did not have a payload well that attestation<00:07:08.199> this<00:07:08.520> does<00:07:08.720> not<00:07:08.960> count<00:07:09.240> towards 00:07:09.550 --> 00:07:09.560 align:start position:0% attestation this does not count towards 00:07:09.560 --> 00:07:12.350 align:start position:0% attestation this does not count towards a<00:07:09.720> parent<00:07:10.000> that<00:07:10.160> did<00:07:10.400> had<00:07:10.560> a<00:07:10.680> payload<00:07:11.680> and<00:07:11.879> this 00:07:12.350 --> 00:07:12.360 align:start position:0% a parent that did had a payload and this 00:07:12.360 --> 00:07:14.230 align:start position:0% a parent that did had a payload and this is<00:07:12.639> completely<00:07:13.039> independent<00:07:13.479> of<00:07:13.639> any<00:07:13.840> auction 00:07:14.230 --> 00:07:14.240 align:start position:0% is completely independent of any auction 00:07:14.240 --> 00:07:15.990 align:start position:0% is completely independent of any auction mechanism<00:07:15.039> this<00:07:15.160> is<00:07:15.280> the<00:07:15.440> complication<00:07:15.879> of 00:07:15.990 --> 00:07:16.000 align:start position:0% mechanism this is the complication of 00:07:16.000 --> 00:07:17.749 align:start position:0% mechanism this is the complication of for 00:07:17.749 --> 00:07:17.759 align:start position:0% for 00:07:17.759 --> 00:07:19.790 align:start position:0% for choice<00:07:18.759> of<00:07:18.879> course<00:07:19.039> you<00:07:19.120> need<00:07:19.240> to<00:07:19.440> still 00:07:19.790 --> 00:07:19.800 align:start position:0% choice of course you need to still 00:07:19.800 --> 00:07:21.189 align:start position:0% choice of course you need to still provide<00:07:20.160> security<00:07:20.680> that<00:07:20.800> you're<00:07:20.960> not<00:07:21.080> going 00:07:21.189 --> 00:07:21.199 align:start position:0% provide security that you're not going 00:07:21.199 --> 00:07:23.749 align:start position:0% provide security that you're not going to<00:07:21.280> be<00:07:21.400> reared<00:07:21.919> for<00:07:22.080> free<00:07:22.960> but<00:07:23.120> anyway<00:07:23.479> so<00:07:23.639> in 00:07:23.749 --> 00:07:23.759 align:start position:0% to be reared for free but anyway so in 00:07:23.759 --> 00:07:25.990 align:start position:0% to be reared for free but anyway so in such<00:07:23.919> a<00:07:24.039> word<00:07:24.879> the<00:07:25.039> other<00:07:25.400> complication<00:07:25.879> that 00:07:25.990 --> 00:07:26.000 align:start position:0% such a word the other complication that 00:07:26.000 --> 00:07:27.790 align:start position:0% such a word the other complication that you<00:07:26.160> have<00:07:26.400> that<00:07:26.599> client<00:07:27.000> implementers<00:07:27.560> will 00:07:27.790 --> 00:07:27.800 align:start position:0% you have that client implementers will 00:07:27.800 --> 00:07:29.909 align:start position:0% you have that client implementers will have<00:07:28.360> is<00:07:28.520> the<00:07:28.680> fact<00:07:28.919> that<00:07:29.360> we<00:07:29.520> we<00:07:29.599> have<00:07:29.720> it 00:07:29.909 --> 00:07:29.919 align:start position:0% have is the fact that we we have it 00:07:29.919 --> 00:07:32.950 align:start position:0% have is the fact that we we have it enshrined<00:07:30.599> in<00:07:30.720> our<00:07:31.319> coding<00:07:32.240> that<00:07:32.479> we<00:07:32.639> get<00:07:32.800> the 00:07:32.950 --> 00:07:32.960 align:start position:0% enshrined in our coding that we get the 00:07:32.960 --> 00:07:35.110 align:start position:0% enshrined in our coding that we get the block<00:07:33.440> we<00:07:33.639> validate<00:07:34.000> in<00:07:34.160> certain<00:07:34.440> order<00:07:34.879> we<00:07:35.039> we 00:07:35.110 --> 00:07:35.120 align:start position:0% block we validate in certain order we we 00:07:35.120 --> 00:07:37.070 align:start position:0% block we validate in certain order we we can<00:07:35.319> validate<00:07:35.680> in<00:07:35.840> parallel<00:07:36.280> execution<00:07:36.960> and 00:07:37.070 --> 00:07:37.080 align:start position:0% can validate in parallel execution and 00:07:37.080 --> 00:07:39.350 align:start position:0% can validate in parallel execution and consensus<00:07:37.560> and<00:07:37.720> we<00:07:37.800> all<00:07:37.960> do<00:07:38.520> because<00:07:39.199> the 00:07:39.350 --> 00:07:39.360 align:start position:0% consensus and we all do because the 00:07:39.360 --> 00:07:41.110 align:start position:0% consensus and we all do because the validations<00:07:39.759> are<00:07:39.960> independent<00:07:40.680> but<00:07:40.840> then<00:07:40.960> we 00:07:41.110 --> 00:07:41.120 align:start position:0% validations are independent but then we 00:07:41.120 --> 00:07:43.430 align:start position:0% validations are independent but then we wait<00:07:41.319> until<00:07:41.599> both<00:07:41.840> validations<00:07:42.280> are<00:07:42.479> done<00:07:43.080> and 00:07:43.430 --> 00:07:43.440 align:start position:0% wait until both validations are done and 00:07:43.440 --> 00:07:46.550 align:start position:0% wait until both validations are done and we<00:07:43.879> attest<00:07:44.879> now<00:07:45.120> one<00:07:45.280> would<00:07:45.479> naively<00:07:46.000> think 00:07:46.550 --> 00:07:46.560 align:start position:0% we attest now one would naively think 00:07:46.560 --> 00:07:49.469 align:start position:0% we attest now one would naively think that<00:07:47.319> uh<00:07:47.960> that's<00:07:48.280> easy<00:07:48.520> to<00:07:48.720> separate<00:07:49.280> because 00:07:49.469 --> 00:07:49.479 align:start position:0% that uh that's easy to separate because 00:07:49.479 --> 00:07:50.869 align:start position:0% that uh that's easy to separate because you<00:07:49.639> just<00:07:49.800> send<00:07:50.280> the<00:07:50.440> things<00:07:50.599> that<00:07:50.720> we're 00:07:50.869 --> 00:07:50.879 align:start position:0% you just send the things that we're 00:07:50.879 --> 00:07:52.510 align:start position:0% you just send the things that we're doing<00:07:51.080> in<00:07:51.199> parallel<00:07:51.560> you<00:07:51.680> just<00:07:51.840> no<00:07:52.319> just 00:07:52.510 --> 00:07:52.520 align:start position:0% doing in parallel you just no just 00:07:52.520 --> 00:07:54.510 align:start position:0% doing in parallel you just no just validate<00:07:52.919> consensus<00:07:53.560> a<00:07:53.800> test<00:07:54.240> and<00:07:54.360> then 00:07:54.510 --> 00:07:54.520 align:start position:0% validate consensus a test and then 00:07:54.520 --> 00:07:55.990 align:start position:0% validate consensus a test and then validate<00:07:54.919> execution<00:07:55.280> in<00:07:55.400> the<00:07:55.520> rest<00:07:55.840> and 00:07:55.990 --> 00:07:56.000 align:start position:0% validate execution in the rest and 00:07:56.000 --> 00:07:58.430 align:start position:0% validate execution in the rest and that's<00:07:56.159> it<00:07:56.680> but<00:07:56.800> that's<00:07:57.000> not<00:07:57.120> so<00:07:57.319> easy<00:07:57.800> because 00:07:58.430 --> 00:07:58.440 align:start position:0% that's it but that's not so easy because 00:07:58.440 --> 00:08:00.670 align:start position:0% that's it but that's not so easy because unfortunately<00:07:59.479> the<00:07:59.560> merge<00:07:59.840> was<00:08:00.000> minimalistic 00:08:00.670 --> 00:08:00.680 align:start position:0% unfortunately the merge was minimalistic 00:08:00.680 --> 00:08:02.390 align:start position:0% unfortunately the merge was minimalistic but<00:08:00.800> then<00:08:00.919> we<00:08:01.039> had<00:08:01.240> capella<00:08:01.800> and<00:08:01.919> in<00:08:02.039> Capella 00:08:02.390 --> 00:08:02.400 align:start position:0% but then we had capella and in Capella 00:08:02.400 --> 00:08:05.350 align:start position:0% but then we had capella and in Capella we<00:08:02.520> added<00:08:02.800> new<00:08:03.360> messages<00:08:04.199> that<00:08:04.560> came<00:08:04.960> from<00:08:05.199> the 00:08:05.350 --> 00:08:05.360 align:start position:0% we added new messages that came from the 00:08:05.360 --> 00:08:07.230 align:start position:0% we added new messages that came from the consensus<00:08:05.800> layer<00:08:06.120> to<00:08:06.280> the<00:08:06.440> execution<00:08:06.840> layer 00:08:07.230 --> 00:08:07.240 align:start position:0% consensus layer to the execution layer 00:08:07.240 --> 00:08:09.270 align:start position:0% consensus layer to the execution layer in<00:08:07.479> Capella<00:08:07.879> we<00:08:07.960> have<00:08:08.120> withdrawals<00:08:08.960> that<00:08:09.080> are 00:08:09.270 --> 00:08:09.280 align:start position:0% in Capella we have withdrawals that are 00:08:09.280 --> 00:08:11.270 align:start position:0% in Capella we have withdrawals that are deducted<00:08:09.720> in<00:08:09.800> the<00:08:09.960> consensus<00:08:10.400> layer<00:08:10.919> and<00:08:11.080> then 00:08:11.270 --> 00:08:11.280 align:start position:0% deducted in the consensus layer and then 00:08:11.280 --> 00:08:13.990 align:start position:0% deducted in the consensus layer and then later<00:08:11.599> on<00:08:12.000> are<00:08:12.680> well<00:08:13.039> and<00:08:13.199> and<00:08:13.319> are<00:08:13.560> Credit<00:08:13.879> in 00:08:13.990 --> 00:08:14.000 align:start position:0% later on are well and and are Credit in 00:08:14.000 --> 00:08:15.589 align:start position:0% later on are well and and are Credit in the<00:08:14.120> execution<00:08:14.479> layer<00:08:14.960> if<00:08:15.080> we<00:08:15.199> have<00:08:15.360> them 00:08:15.589 --> 00:08:15.599 align:start position:0% the execution layer if we have them 00:08:15.599 --> 00:08:17.350 align:start position:0% the execution layer if we have them separated<00:08:16.360> we're<00:08:16.560> going<00:08:16.639> to<00:08:16.800> have<00:08:16.879> to<00:08:17.000> do<00:08:17.199> that 00:08:17.350 --> 00:08:17.360 align:start position:0% separated we're going to have to do that 00:08:17.360 --> 00:08:19.350 align:start position:0% separated we're going to have to do that logic<00:08:17.759> theed<00:08:18.000> duct<00:08:18.159> first<00:08:18.400> when<00:08:18.560> withdrawals 00:08:19.350 --> 00:08:19.360 align:start position:0% logic theed duct first when withdrawals 00:08:19.360 --> 00:08:21.270 align:start position:0% logic theed duct first when withdrawals and<00:08:19.520> then<00:08:20.240> uh<00:08:20.400> credit<00:08:20.680> on<00:08:20.800> the<00:08:20.919> execution 00:08:21.270 --> 00:08:21.280 align:start position:0% and then uh credit on the execution 00:08:21.280 --> 00:08:23.550 align:start position:0% and then uh credit on the execution layer<00:08:21.520> when<00:08:21.639> we<00:08:21.759> see<00:08:21.879> a<00:08:22.000> payload<00:08:23.000> so<00:08:23.159> that's<00:08:23.360> a 00:08:23.550 --> 00:08:23.560 align:start position:0% layer when we see a payload so that's a 00:08:23.560 --> 00:08:26.149 align:start position:0% layer when we see a payload so that's a complication<00:08:24.280> and<00:08:24.479> Electra<00:08:25.319> gives<00:08:25.560> us<00:08:25.919> many 00:08:26.149 --> 00:08:26.159 align:start position:0% complication and Electra gives us many 00:08:26.159 --> 00:08:28.070 align:start position:0% complication and Electra gives us many more<00:08:26.400> headaches<00:08:27.080> now<00:08:27.240> in<00:08:27.360> Electra<00:08:27.800> we<00:08:27.919> have 00:08:28.070 --> 00:08:28.080 align:start position:0% more headaches now in Electra we have 00:08:28.080 --> 00:08:29.869 align:start position:0% more headaches now in Electra we have messages<00:08:28.479> in<00:08:28.599> the<00:08:28.720> other<00:08:29.000> direction<00:08:29.599> and<00:08:29.759> in 00:08:29.869 --> 00:08:29.879 align:start position:0% messages in the other direction and in 00:08:29.879 --> 00:08:32.029 align:start position:0% messages in the other direction and in future<00:08:30.159> Forks<00:08:30.800> we<00:08:31.000> expect<00:08:31.280> to<00:08:31.479> get<00:08:31.680> more<00:08:31.879> and 00:08:32.029 --> 00:08:32.039 align:start position:0% future Forks we expect to get more and 00:08:32.039 --> 00:08:33.870 align:start position:0% future Forks we expect to get more and more<00:08:32.320> messages<00:08:32.919> in<00:08:33.080> the<00:08:33.200> direction<00:08:33.560> from<00:08:33.719> the 00:08:33.870 --> 00:08:33.880 align:start position:0% more messages in the direction from the 00:08:33.880 --> 00:08:36.110 align:start position:0% more messages in the direction from the L<00:08:34.200> triggered<00:08:34.680> in<00:08:34.800> the<00:08:34.959> L<00:08:35.519> towards<00:08:35.959> the 00:08:36.110 --> 00:08:36.120 align:start position:0% L triggered in the L towards the 00:08:36.120 --> 00:08:37.990 align:start position:0% L triggered in the L towards the consensus<00:08:36.560> layer<00:08:37.200> these<00:08:37.320> are<00:08:37.519> for<00:08:37.680> example 00:08:37.990 --> 00:08:38.000 align:start position:0% consensus layer these are for example 00:08:38.000 --> 00:08:39.990 align:start position:0% consensus layer these are for example deposit<00:08:38.440> requests<00:08:38.919> withdrawal<00:08:39.519> requests<00:08:39.839> and 00:08:39.990 --> 00:08:40.000 align:start position:0% deposit requests withdrawal requests and 00:08:40.000 --> 00:08:42.509 align:start position:0% deposit requests withdrawal requests and so<00:08:40.159> forth<00:08:41.039> which<00:08:41.519> you<00:08:41.640> will<00:08:41.919> have<00:08:42.080> to<00:08:42.240> change 00:08:42.509 --> 00:08:42.519 align:start position:0% so forth which you will have to change 00:08:42.519 --> 00:08:44.230 align:start position:0% so forth which you will have to change your<00:08:42.719> code<00:08:43.279> in<00:08:43.399> such<00:08:43.560> a<00:08:43.680> way<00:08:43.839> that<00:08:44.000> when<00:08:44.120> the 00:08:44.230 --> 00:08:44.240 align:start position:0% your code in such a way that when the 00:08:44.240 --> 00:08:47.829 align:start position:0% your code in such a way that when the payload<00:08:44.720> comes<00:08:45.560> you<00:08:45.880> process 00:08:47.829 --> 00:08:47.839 align:start position:0% payload comes you process 00:08:47.839 --> 00:08:51.310 align:start position:0% payload comes you process those<00:08:48.839> okay<00:08:49.360> so<00:08:50.360> the<00:08:50.519> point<00:08:50.800> I'm<00:08:50.920> trying<00:08:51.160> to 00:08:51.310 --> 00:08:51.320 align:start position:0% those okay so the point I'm trying to 00:08:51.320 --> 00:08:53.630 align:start position:0% those okay so the point I'm trying to make<00:08:51.560> is<00:08:51.680> that<00:08:51.880> the<00:08:52.040> complication<00:08:53.040> has 00:08:53.630 --> 00:08:53.640 align:start position:0% make is that the complication has 00:08:53.640 --> 00:08:57.230 align:start position:0% make is that the complication has nothing<00:08:54.160> to<00:08:54.360> do<00:08:54.800> with<00:08:55.040> neither<00:08:55.519> me<00:08:56.519> and<00:08:57.080> the 00:08:57.230 --> 00:08:57.240 align:start position:0% nothing to do with neither me and the 00:08:57.240 --> 00:08:59.630 align:start position:0% nothing to do with neither me and the auction<00:08:57.880> mechanism<00:08:58.880> so<00:08:59.040> now<00:08:59.160> we're<00:08:59.480> going<00:08:59.560> to 00:08:59.630 --> 00:08:59.640 align:start position:0% auction mechanism so now we're going to 00:08:59.640 --> 00:09:02.030 align:start position:0% auction mechanism so now we're going to start<00:08:59.839> moving<00:09:00.120> to<00:09:00.440> auctioning<00:09:01.000> but<00:09:01.680> before 00:09:02.030 --> 00:09:02.040 align:start position:0% start moving to auctioning but before 00:09:02.040 --> 00:09:03.870 align:start position:0% start moving to auctioning but before that<00:09:02.320> let<00:09:02.399> me<00:09:02.560> tell<00:09:02.680> you<00:09:02.839> what<00:09:02.959> the<00:09:03.240> slot<00:09:03.640> will 00:09:03.870 --> 00:09:03.880 align:start position:0% that let me tell you what the slot will 00:09:03.880 --> 00:09:05.910 align:start position:0% that let me tell you what the slot will look<00:09:04.079> like<00:09:04.279> in<00:09:04.399> a<00:09:05.079> in<00:09:05.160> a<00:09:05.320> way<00:09:05.480> in<00:09:05.600> which<00:09:05.760> we 00:09:05.910 --> 00:09:05.920 align:start position:0% look like in a in a way in which we 00:09:05.920 --> 00:09:07.509 align:start position:0% look like in a in a way in which we separated<00:09:06.399> the<00:09:06.480> payLo<00:09:06.880> From<00:09:07.000> the<00:09:07.079> Block 00:09:07.509 --> 00:09:07.519 align:start position:0% separated the payLo From the Block 00:09:07.519 --> 00:09:10.350 align:start position:0% separated the payLo From the Block regardless<00:09:08.079> of<00:09:08.880> of<00:09:09.079> auctioning<00:09:09.560> mechanism<00:09:10.240> we 00:09:10.350 --> 00:09:10.360 align:start position:0% regardless of of auctioning mechanism we 00:09:10.360 --> 00:09:11.790 align:start position:0% regardless of of auctioning mechanism we will<00:09:10.560> have<00:09:10.680> a<00:09:10.800> broadcast<00:09:11.360> you're<00:09:11.519> going<00:09:11.640> to 00:09:11.790 --> 00:09:11.800 align:start position:0% will have a broadcast you're going to 00:09:11.800 --> 00:09:14.030 align:start position:0% will have a broadcast you're going to have<00:09:11.880> to<00:09:12.079> validate<00:09:12.640> quickly<00:09:13.399> execution<00:09:13.920> which 00:09:14.030 --> 00:09:14.040 align:start position:0% have to validate quickly execution which 00:09:14.040 --> 00:09:15.990 align:start position:0% have to validate quickly execution which is<00:09:14.200> fast<00:09:14.640> and<00:09:14.760> then<00:09:14.880> you<00:09:15.040> have<00:09:15.240> the<00:09:15.519> rest<00:09:15.839> of 00:09:15.990 --> 00:09:16.000 align:start position:0% is fast and then you have the rest of 00:09:16.000 --> 00:09:18.630 align:start position:0% is fast and then you have the rest of the<00:09:16.160> slot<00:09:16.800> to<00:09:17.079> just<00:09:17.519> get<00:09:17.839> consensus<00:09:18.399> on 00:09:18.630 --> 00:09:18.640 align:start position:0% the slot to just get consensus on 00:09:18.640 --> 00:09:22.269 align:start position:0% the slot to just get consensus on whether<00:09:18.839> or<00:09:19.000> not<00:09:19.200> the<00:09:19.360> payload<00:09:19.800> was 00:09:22.269 --> 00:09:22.279 align:start position:0% 00:09:22.279 --> 00:09:25.550 align:start position:0% there<00:09:23.279> okay<00:09:23.519> so<00:09:23.959> that<00:09:24.079> was<00:09:24.200> the<00:09:24.440> part<00:09:24.839> of 00:09:25.550 --> 00:09:25.560 align:start position:0% there okay so that was the part of 00:09:25.560 --> 00:09:27.949 align:start position:0% there okay so that was the part of payload<00:09:26.480> block 00:09:27.949 --> 00:09:27.959 align:start position:0% payload block 00:09:27.959 --> 00:09:31.829 align:start position:0% payload block separation<00:09:28.959> now<00:09:29.079> we<00:09:29.680> we<00:09:29.880> come<00:09:30.079> to<00:09:30.240> the<00:09:30.399> section 00:09:31.829 --> 00:09:31.839 align:start position:0% separation now we we come to the section 00:09:31.839 --> 00:09:34.550 align:start position:0% separation now we we come to the section of<00:09:32.839> proposer<00:09:33.360> Builder 00:09:34.550 --> 00:09:34.560 align:start position:0% of proposer Builder 00:09:34.560 --> 00:09:37.990 align:start position:0% of proposer Builder separation<00:09:35.839> so<00:09:36.839> I've<00:09:37.040> describe<00:09:37.519> the<00:09:37.720> problem 00:09:37.990 --> 00:09:38.000 align:start position:0% separation so I've describe the problem 00:09:38.000 --> 00:09:40.110 align:start position:0% separation so I've describe the problem the<00:09:38.160> big<00:09:38.519> lifting<00:09:39.120> of<00:09:39.399> separating<00:09:39.839> the<00:09:39.920> block 00:09:40.110 --> 00:09:40.120 align:start position:0% the big lifting of separating the block 00:09:40.120 --> 00:09:42.550 align:start position:0% the big lifting of separating the block and<00:09:40.240> the<00:09:40.320> payload<00:09:41.079> is<00:09:41.279> in<00:09:41.480> two<00:09:41.920> sections 00:09:42.550 --> 00:09:42.560 align:start position:0% and the payload is in two sections 00:09:42.560 --> 00:09:44.670 align:start position:0% and the payload is in two sections changing<00:09:42.959> for<00:09:43.320> choice<00:09:43.600> to<00:09:43.800> achieve<00:09:44.240> consensus 00:09:44.670 --> 00:09:44.680 align:start position:0% changing for choice to achieve consensus 00:09:44.680 --> 00:09:47.150 align:start position:0% changing for choice to achieve consensus on<00:09:44.920> what<00:09:45.079> is<00:09:45.920> the<00:09:46.120> head<00:09:46.279> of<00:09:46.360> the<00:09:46.480> chain<00:09:47.000> and 00:09:47.150 --> 00:09:47.160 align:start position:0% on what is the head of the chain and 00:09:47.160 --> 00:09:49.790 align:start position:0% on what is the head of the chain and changing<00:09:47.839> clients<00:09:48.839> uh<00:09:48.959> implementations<00:09:49.600> on 00:09:49.790 --> 00:09:49.800 align:start position:0% changing clients uh implementations on 00:09:49.800 --> 00:09:52.150 align:start position:0% changing clients uh implementations on how<00:09:50.000> they<00:09:50.279> sync<00:09:50.640> their<00:09:50.800> block<00:09:51.440> because<00:09:51.760> they 00:09:52.150 --> 00:09:52.160 align:start position:0% how they sync their block because they 00:09:52.160 --> 00:09:54.630 align:start position:0% how they sync their block because they they<00:09:52.320> need<00:09:52.519> to<00:09:52.720> do<00:09:53.000> things<00:09:53.640> in<00:09:53.800> a<00:09:54.160> in<00:09:54.279> a 00:09:54.630 --> 00:09:54.640 align:start position:0% they need to do things in a in a 00:09:54.640 --> 00:09:55.870 align:start position:0% they need to do things in a in a essentially<00:09:55.079> different<00:09:55.320> way<00:09:55.519> they<00:09:55.600> need<00:09:55.720> to 00:09:55.870 --> 00:09:55.880 align:start position:0% essentially different way they need to 00:09:55.880 --> 00:09:57.509 align:start position:0% essentially different way they need to access<00:09:56.120> the<00:09:56.240> databases<00:09:56.720> in<00:09:56.880> essentially 00:09:57.509 --> 00:09:57.519 align:start position:0% access the databases in essentially 00:09:57.519 --> 00:09:59.470 align:start position:0% access the databases in essentially different<00:09:57.839> way<00:09:58.600> but<00:09:58.720> now<00:09:58.839> the<00:09:58.959> question<00:09:59.160> is 00:09:59.470 --> 00:09:59.480 align:start position:0% different way but now the question is 00:09:59.480 --> 00:10:01.870 align:start position:0% different way but now the question is well<00:09:59.800> how<00:09:59.920> do<00:10:00.079> we<00:10:00.200> implement<00:10:00.680> this<00:10:01.240> how<00:10:01.399> do<00:10:01.560> we 00:10:01.870 --> 00:10:01.880 align:start position:0% well how do we implement this how do we 00:10:01.880 --> 00:10:03.590 align:start position:0% well how do we implement this how do we achieve<00:10:02.360> an<00:10:02.519> implementation<00:10:03.079> that<00:10:03.200> separates 00:10:03.590 --> 00:10:03.600 align:start position:0% achieve an implementation that separates 00:10:03.600 --> 00:10:04.870 align:start position:0% achieve an implementation that separates the<00:10:03.680> block<00:10:03.920> and<00:10:04.040> the<00:10:04.120> payload<00:10:04.640> in<00:10:04.760> a 00:10:04.870 --> 00:10:04.880 align:start position:0% the block and the payload in a 00:10:04.880 --> 00:10:06.910 align:start position:0% the block and the payload in a minimalistic 00:10:06.910 --> 00:10:06.920 align:start position:0% minimalistic 00:10:06.920 --> 00:10:10.750 align:start position:0% minimalistic way<00:10:07.920> and<00:10:08.680> I<00:10:08.800> want<00:10:09.000> to<00:10:09.320> convince<00:10:09.760> you<00:10:10.160> well 00:10:10.750 --> 00:10:10.760 align:start position:0% way and I want to convince you well 00:10:10.760 --> 00:10:12.470 align:start position:0% way and I want to convince you well which<00:10:10.880> is<00:10:11.040> probably<00:10:11.399> hard<00:10:11.680> but<00:10:11.839> I<00:10:11.920> want<00:10:12.040> to 00:10:12.470 --> 00:10:12.480 align:start position:0% which is probably hard but I want to 00:10:12.480 --> 00:10:15.710 align:start position:0% which is probably hard but I want to make<00:10:12.720> a<00:10:13.000> case<00:10:13.640> that<00:10:14.200> with<00:10:14.399> minimal 00:10:15.710 --> 00:10:15.720 align:start position:0% make a case that with minimal 00:10:15.720 --> 00:10:18.430 align:start position:0% make a case that with minimal assumptions<00:10:16.720> uh<00:10:17.200> EIP 00:10:18.430 --> 00:10:18.440 align:start position:0% assumptions uh EIP 00:10:18.440 --> 00:10:21.230 align:start position:0% assumptions uh EIP 7732<00:10:19.440> is<00:10:19.680> a<00:10:19.880> system<00:10:20.279> that<00:10:20.440> achieves<00:10:20.920> this<00:10:21.079> in 00:10:21.230 --> 00:10:21.240 align:start position:0% 7732 is a system that achieves this in 00:10:21.240 --> 00:10:23.670 align:start position:0% 7732 is a system that achieves this in an<00:10:21.440> actual<00:10:21.720> minimal 00:10:23.670 --> 00:10:23.680 align:start position:0% an actual minimal 00:10:23.680 --> 00:10:25.269 align:start position:0% an actual minimal way 00:10:25.269 --> 00:10:25.279 align:start position:0% way 00:10:25.279 --> 00:10:28.150 align:start position:0% way so<00:10:26.279> we<00:10:26.399> need<00:10:26.560> to<00:10:26.720> decide<00:10:26.959> a<00:10:27.160> way<00:10:27.320> of<00:10:27.760> how<00:10:28.040> the 00:10:28.150 --> 00:10:28.160 align:start position:0% so we need to decide a way of how the 00:10:28.160 --> 00:10:29.590 align:start position:0% so we need to decide a way of how the payload<00:10:28.560> appears<00:10:29.040> and<00:10:29.200> I'm<00:10:29.320> I'm<00:10:29.399> going<00:10:29.519> to 00:10:29.590 --> 00:10:29.600 align:start position:0% payload appears and I'm I'm going to 00:10:29.600 --> 00:10:30.750 align:start position:0% payload appears and I'm I'm going to talk<00:10:29.720> a<00:10:29.800> little<00:10:29.920> bit<00:10:30.079> about<00:10:30.240> auctions<00:10:30.680> there 00:10:30.750 --> 00:10:30.760 align:start position:0% talk a little bit about auctions there 00:10:30.760 --> 00:10:33.990 align:start position:0% talk a little bit about auctions there are<00:10:31.519> many<00:10:31.839> ideas<00:10:32.200> going<00:10:32.480> around<00:10:33.120> on<00:10:33.640> they<00:10:33.760> all 00:10:33.990 --> 00:10:34.000 align:start position:0% are many ideas going around on they all 00:10:34.000 --> 00:10:35.910 align:start position:0% are many ideas going around on they all have<00:10:34.200> acronyms<00:10:35.079> that<00:10:35.279> that<00:10:35.399> are<00:10:35.560> hard<00:10:35.720> to 00:10:35.910 --> 00:10:35.920 align:start position:0% have acronyms that that are hard to 00:10:35.920 --> 00:10:41.509 align:start position:0% have acronyms that that are hard to remember<00:10:36.680> epbs<00:10:37.600> slot<00:10:38.040> auctions<00:10:39.040> APS<00:10:39.839> ETS<00:10:40.519> ATS 00:10:41.509 --> 00:10:41.519 align:start position:0% remember epbs slot auctions APS ETS ATS 00:10:41.519 --> 00:10:43.750 align:start position:0% remember epbs slot auctions APS ETS ATS I<00:10:41.600> don't<00:10:41.760> know<00:10:42.760> but<00:10:42.959> they<00:10:43.120> all<00:10:43.320> more<00:10:43.480> or<00:10:43.639> less 00:10:43.750 --> 00:10:43.760 align:start position:0% I don't know but they all more or less 00:10:43.760 --> 00:10:45.350 align:start position:0% I don't know but they all more or less are<00:10:43.920> in<00:10:44.000> the<00:10:44.120> same<00:10:44.279> way<00:10:44.480> there's<00:10:44.760> someone<00:10:45.160> that 00:10:45.350 --> 00:10:45.360 align:start position:0% are in the same way there's someone that 00:10:45.360 --> 00:10:48.949 align:start position:0% are in the same way there's someone that sells<00:10:45.720> a<00:10:46.000> right<00:10:46.600> to<00:10:47.079> produce<00:10:47.440> a<00:10:47.560> payload<00:10:48.560> in 00:10:48.949 --> 00:10:48.959 align:start position:0% sells a right to produce a payload in 00:10:48.959 --> 00:10:50.910 align:start position:0% sells a right to produce a payload in Block<00:10:49.279> auctions<00:10:49.720> the<00:10:49.880> proposer<00:10:50.360> submits<00:10:50.800> a 00:10:50.910 --> 00:10:50.920 align:start position:0% Block auctions the proposer submits a 00:10:50.920 --> 00:10:52.790 align:start position:0% Block auctions the proposer submits a block<00:10:51.279> a<00:10:51.399> consensus<00:10:51.880> block<00:10:52.480> with<00:10:52.639> a 00:10:52.790 --> 00:10:52.800 align:start position:0% block a consensus block with a 00:10:52.800 --> 00:10:55.670 align:start position:0% block a consensus block with a commitment<00:10:53.160> to<00:10:53.360> a<00:10:53.519> particular<00:10:54.320> payload<00:10:55.320> and 00:10:55.670 --> 00:10:55.680 align:start position:0% commitment to a particular payload and 00:10:55.680 --> 00:10:57.550 align:start position:0% commitment to a particular payload and the<00:10:55.839> Builder<00:10:56.440> that's<00:10:56.720> committing<00:10:57.200> for<00:10:57.360> that 00:10:57.550 --> 00:10:57.560 align:start position:0% the Builder that's committing for that 00:10:57.560 --> 00:10:59.910 align:start position:0% the Builder that's committing for that particular<00:10:57.920> payload<00:10:58.360> promises<00:10:58.760> to<00:10:58.959> pay 00:10:59.910 --> 00:10:59.920 align:start position:0% particular payload promises to pay 00:10:59.920 --> 00:11:01.670 align:start position:0% particular payload promises to pay uh<00:11:00.040> a<00:11:00.240> value<00:11:00.639> to<00:11:00.920> for<00:11:01.079> the<00:11:01.279> rights<00:11:01.519> of 00:11:01.670 --> 00:11:01.680 align:start position:0% uh a value to for the rights of 00:11:01.680 --> 00:11:04.550 align:start position:0% uh a value to for the rights of producing<00:11:02.040> that<00:11:02.200> payload<00:11:02.800> in<00:11:02.959> slot<00:11:03.560> auctions 00:11:04.550 --> 00:11:04.560 align:start position:0% producing that payload in slot auctions 00:11:04.560 --> 00:11:06.389 align:start position:0% producing that payload in slot auctions the<00:11:04.839> proposer<00:11:05.360> does<00:11:05.560> not<00:11:05.800> commit<00:11:06.120> to<00:11:06.240> a 00:11:06.389 --> 00:11:06.399 align:start position:0% the proposer does not commit to a 00:11:06.399 --> 00:11:08.069 align:start position:0% the proposer does not commit to a particular<00:11:06.760> payload<00:11:07.120> it<00:11:07.279> only<00:11:07.519> commits<00:11:07.839> to<00:11:07.959> a 00:11:08.069 --> 00:11:08.079 align:start position:0% particular payload it only commits to a 00:11:08.079 --> 00:11:09.870 align:start position:0% particular payload it only commits to a particular<00:11:08.480> Builder<00:11:09.240> and<00:11:09.360> then<00:11:09.480> the<00:11:09.560> Builder 00:11:09.870 --> 00:11:09.880 align:start position:0% particular Builder and then the Builder 00:11:09.880 --> 00:11:12.110 align:start position:0% particular Builder and then the Builder later<00:11:10.120> on<00:11:10.399> produces<00:11:10.920> any<00:11:11.160> payload<00:11:11.720> that<00:11:11.920> he 00:11:12.110 --> 00:11:12.120 align:start position:0% later on produces any payload that he 00:11:12.120 --> 00:11:14.990 align:start position:0% later on produces any payload that he wishes<00:11:12.880> to<00:11:13.200> produce<00:11:14.200> there's<00:11:14.560> execution 00:11:14.990 --> 00:11:15.000 align:start position:0% wishes to produce there's execution 00:11:15.000 --> 00:11:16.790 align:start position:0% wishes to produce there's execution tickets<00:11:15.360> or<00:11:15.519> execution<00:11:15.920> auctions<00:11:16.440> in<00:11:16.600> which 00:11:16.790 --> 00:11:16.800 align:start position:0% tickets or execution auctions in which 00:11:16.800 --> 00:11:19.790 align:start position:0% tickets or execution auctions in which the<00:11:16.959> auctioneer<00:11:17.800> is<00:11:18.040> not<00:11:18.560> a<00:11:18.760> validator<00:11:19.440> but<00:11:19.600> is 00:11:19.790 --> 00:11:19.800 align:start position:0% the auctioneer is not a validator but is 00:11:19.800 --> 00:11:22.389 align:start position:0% the auctioneer is not a validator but is the<00:11:19.959> protocol<00:11:20.480> itself<00:11:21.200> the<00:11:21.360> protocol<00:11:21.800> sells 00:11:22.389 --> 00:11:22.399 align:start position:0% the protocol itself the protocol sells 00:11:22.399 --> 00:11:24.910 align:start position:0% the protocol itself the protocol sells far<00:11:22.680> in<00:11:22.839> advance<00:11:23.440> 32<00:11:23.920> slots<00:11:24.200> in<00:11:24.320> advance 00:11:24.910 --> 00:11:24.920 align:start position:0% far in advance 32 slots in advance 00:11:24.920 --> 00:11:26.629 align:start position:0% far in advance 32 slots in advance either<00:11:25.360> tickets<00:11:26.079> and<00:11:26.200> then<00:11:26.360> there's<00:11:26.480> a 00:11:26.629 --> 00:11:26.639 align:start position:0% either tickets and then there's a 00:11:26.639 --> 00:11:29.470 align:start position:0% either tickets and then there's a lottery<00:11:27.079> that<00:11:27.200> is<00:11:27.320> run<00:11:28.279> uh<00:11:28.560> by<00:11:28.720> random<00:11:29.040> n<00:11:29.360> and 00:11:29.470 --> 00:11:29.480 align:start position:0% lottery that is run uh by random n and 00:11:29.480 --> 00:11:32.110 align:start position:0% lottery that is run uh by random n and we<00:11:29.600> choose<00:11:29.920> who<00:11:30.240> later<00:11:30.519> 30<00:11:31.360> later<00:11:31.880> who 00:11:32.110 --> 00:11:32.120 align:start position:0% we choose who later 30 later who 00:11:32.120 --> 00:11:34.750 align:start position:0% we choose who later 30 later who proposes<00:11:32.560> a<00:11:32.720> payload<00:11:33.519> or<00:11:34.120> you<00:11:34.240> can<00:11:34.480> actually 00:11:34.750 --> 00:11:34.760 align:start position:0% proposes a payload or you can actually 00:11:34.760 --> 00:11:36.829 align:start position:0% proposes a payload or you can actually sell<00:11:35.160> the<00:11:35.279> protocol<00:11:35.720> can<00:11:35.880> sell<00:11:36.240> can<00:11:36.440> hold<00:11:36.680> an 00:11:36.829 --> 00:11:36.839 align:start position:0% sell the protocol can sell can hold an 00:11:36.839 --> 00:11:39.230 align:start position:0% sell the protocol can sell can hold an auction<00:11:37.519> and<00:11:37.639> sell<00:11:38.000> the<00:11:38.160> rights<00:11:38.480> to<00:11:38.680> propose<00:11:39.040> a 00:11:39.230 --> 00:11:39.240 align:start position:0% auction and sell the rights to propose a 00:11:39.240 --> 00:11:42.430 align:start position:0% auction and sell the rights to propose a slot<00:11:39.920> 302<00:11:40.480> slots<00:11:40.760> in<00:11:40.880> advance<00:11:41.880> and<00:11:42.120> all<00:11:42.279> of 00:11:42.430 --> 00:11:42.440 align:start position:0% slot 302 slots in advance and all of 00:11:42.440 --> 00:11:44.829 align:start position:0% slot 302 slots in advance and all of these<00:11:42.639> mechanisms<00:11:43.320> have<00:11:43.519> their<00:11:43.839> tradeoffs 00:11:44.829 --> 00:11:44.839 align:start position:0% these mechanisms have their tradeoffs 00:11:44.839 --> 00:11:47.069 align:start position:0% these mechanisms have their tradeoffs none<00:11:45.079> of<00:11:45.279> them<00:11:45.440> come<00:11:45.639> for<00:11:45.839> free<00:11:46.519> they<00:11:46.720> all<00:11:46.920> of 00:11:47.069 --> 00:11:47.079 align:start position:0% none of them come for free they all of 00:11:47.079 --> 00:11:49.870 align:start position:0% none of them come for free they all of them<00:11:47.399> impact<00:11:47.959> the<00:11:48.120> me<00:11:48.560> chain<00:11:49.160> and<00:11:49.320> they<00:11:49.440> all<00:11:49.639> of 00:11:49.870 --> 00:11:49.880 align:start position:0% them impact the me chain and they all of 00:11:49.880 --> 00:11:53.509 align:start position:0% them impact the me chain and they all of them<00:11:50.880> uh<00:11:51.839> produce<00:11:52.320> different<00:11:52.639> kinds<00:11:52.839> of 00:11:53.509 --> 00:11:53.519 align:start position:0% them uh produce different kinds of 00:11:53.519 --> 00:11:55.470 align:start position:0% them uh produce different kinds of centralizations<00:11:54.519> all<00:11:54.680> of<00:11:54.880> these<00:11:55.040> mechanisms 00:11:55.470 --> 00:11:55.480 align:start position:0% centralizations all of these mechanisms 00:11:55.480 --> 00:11:58.150 align:start position:0% centralizations all of these mechanisms that<00:11:55.600> I'm<00:11:55.760> describing<00:11:56.240> here<00:11:57.040> you<00:11:57.320> can<00:11:57.600> or<00:11:57.920> may 00:11:58.150 --> 00:11:58.160 align:start position:0% that I'm describing here you can or may 00:11:58.160 --> 00:12:01.629 align:start position:0% that I'm describing here you can or may not<00:11:58.399> run<00:11:58.680> them<00:11:58.839> with<00:11:59.720> burn<00:12:00.320> that<00:12:00.440> means<00:12:00.880> that 00:12:01.629 --> 00:12:01.639 align:start position:0% not run them with burn that means that 00:12:01.639 --> 00:12:04.030 align:start position:0% not run them with burn that means that even<00:12:01.880> if<00:12:02.040> the<00:12:02.240> proposer<00:12:03.200> is<00:12:03.399> choosing<00:12:03.839> and 00:12:04.030 --> 00:12:04.040 align:start position:0% even if the proposer is choosing and 00:12:04.040 --> 00:12:05.629 align:start position:0% even if the proposer is choosing and getting<00:12:04.279> some<00:12:04.519> value<00:12:04.760> out<00:12:04.920> of<00:12:05.040> the<00:12:05.120> Builder 00:12:05.629 --> 00:12:05.639 align:start position:0% getting some value out of the Builder 00:12:05.639 --> 00:12:08.949 align:start position:0% getting some value out of the Builder you<00:12:05.800> could<00:12:06.000> in<00:12:06.440> principle<00:12:07.440> include<00:12:08.120> a<00:12:08.399> burning 00:12:08.949 --> 00:12:08.959 align:start position:0% you could in principle include a burning 00:12:08.959 --> 00:12:12.269 align:start position:0% you could in principle include a burning of<00:12:09.200> that<00:12:09.800> value<00:12:10.399> towards<00:12:10.680> the<00:12:11.160> protocol<00:12:12.160> the 00:12:12.269 --> 00:12:12.279 align:start position:0% of that value towards the protocol the 00:12:12.279 --> 00:12:14.590 align:start position:0% of that value towards the protocol the one<00:12:12.440> that<00:12:12.560> I<00:12:12.680> didn't<00:12:12.959> include<00:12:13.320> is<00:12:13.519> no<00:12:13.839> auction 00:12:14.590 --> 00:12:14.600 align:start position:0% one that I didn't include is no auction 00:12:14.600 --> 00:12:17.150 align:start position:0% one that I didn't include is no auction but<00:12:14.760> that's<00:12:15.440> certainly<00:12:15.920> possible<00:12:16.680> we<00:12:16.800> wanted 00:12:17.150 --> 00:12:17.160 align:start position:0% but that's certainly possible we wanted 00:12:17.160 --> 00:12:20.230 align:start position:0% but that's certainly possible we wanted to<00:12:17.360> St<00:12:17.720> it<00:12:17.839> was<00:12:18.000> about<00:12:18.639> enrin<00:12:19.480> payload<00:12:20.000> block 00:12:20.230 --> 00:12:20.240 align:start position:0% to St it was about enrin payload block 00:12:20.240 --> 00:12:21.990 align:start position:0% to St it was about enrin payload block separation<00:12:20.839> in<00:12:21.000> principle<00:12:21.360> I<00:12:21.480> could<00:12:21.639> just 00:12:21.990 --> 00:12:22.000 align:start position:0% separation in principle I could just 00:12:22.000 --> 00:12:25.269 align:start position:0% separation in principle I could just enforce<00:12:22.920> that<00:12:23.480> the<00:12:23.839> proposer<00:12:24.399> is<00:12:24.639> the<00:12:24.839> same 00:12:25.269 --> 00:12:25.279 align:start position:0% enforce that the proposer is the same 00:12:25.279 --> 00:12:27.430 align:start position:0% enforce that the proposer is the same signature<00:12:25.880> as<00:12:26.360> as<00:12:26.480> the 00:12:27.430 --> 00:12:27.440 align:start position:0% signature as as the 00:12:27.440 --> 00:12:29.829 align:start position:0% signature as as the Builder<00:12:28.440> keep<00:12:28.680> everything<00:12:29.199> exactly<00:12:29.480> as<00:12:29.600> it<00:12:29.720> is 00:12:29.829 --> 00:12:29.839 align:start position:0% Builder keep everything exactly as it is 00:12:29.839 --> 00:12:33.230 align:start position:0% Builder keep everything exactly as it is today<00:12:30.120> in<00:12:30.199> the<00:12:30.360> M<00:12:30.760> chain<00:12:31.560> and<00:12:32.199> keep<00:12:32.440> using<00:12:32.760> me 00:12:33.230 --> 00:12:33.240 align:start position:0% today in the M chain and keep using me 00:12:33.240 --> 00:12:35.829 align:start position:0% today in the M chain and keep using me boost<00:12:34.240> nothing<00:12:34.519> would<00:12:34.680> change<00:12:35.120> except<00:12:35.519> that 00:12:35.829 --> 00:12:35.839 align:start position:0% boost nothing would change except that 00:12:35.839 --> 00:12:37.269 align:start position:0% boost nothing would change except that we<00:12:36.000> have<00:12:36.120> all<00:12:36.240> the<00:12:36.360> Machinery<00:12:36.760> to<00:12:36.880> separate 00:12:37.269 --> 00:12:37.279 align:start position:0% we have all the Machinery to separate 00:12:37.279 --> 00:12:39.269 align:start position:0% we have all the Machinery to separate the<00:12:37.360> block<00:12:37.560> and<00:12:37.680> the 00:12:39.269 --> 00:12:39.279 align:start position:0% the block and the 00:12:39.279 --> 00:12:42.230 align:start position:0% the block and the payload<00:12:40.279> however<00:12:41.160> if<00:12:41.279> we've<00:12:41.519> already<00:12:41.880> did<00:12:42.079> the 00:12:42.230 --> 00:12:42.240 align:start position:0% payload however if we've already did the 00:12:42.240 --> 00:12:43.710 align:start position:0% payload however if we've already did the heavy<00:12:42.480> lifting<00:12:42.880> which<00:12:43.000> is<00:12:43.120> changing<00:12:43.440> for 00:12:43.710 --> 00:12:43.720 align:start position:0% heavy lifting which is changing for 00:12:43.720 --> 00:12:46.509 align:start position:0% heavy lifting which is changing for choice<00:12:43.959> and<00:12:44.160> changing<00:12:44.560> block<00:12:45.519> processing 00:12:46.509 --> 00:12:46.519 align:start position:0% choice and changing block processing 00:12:46.519 --> 00:12:49.030 align:start position:0% choice and changing block processing changing<00:12:46.920> the<00:12:47.040> auction<00:12:47.519> is<00:12:47.720> zero<00:12:48.079> work<00:12:48.320> for<00:12:48.519> us 00:12:49.030 --> 00:12:49.040 align:start position:0% changing the auction is zero work for us 00:12:49.040 --> 00:12:51.150 align:start position:0% changing the auction is zero work for us changing<00:12:49.399> the<00:12:49.519> auction<00:12:49.800> is<00:12:50.040> nothing<00:12:50.560> because 00:12:51.150 --> 00:12:51.160 align:start position:0% changing the auction is nothing because 00:12:51.160 --> 00:12:52.949 align:start position:0% changing the auction is nothing because the<00:12:51.279> auction<00:12:51.680> we<00:12:51.839> already<00:12:52.199> have<00:12:52.320> it<00:12:52.639> we<00:12:52.800> have 00:12:52.949 --> 00:12:52.959 align:start position:0% the auction we already have it we have 00:12:52.959 --> 00:12:55.430 align:start position:0% the auction we already have it we have the<00:12:53.199> code<00:12:53.800> that<00:12:54.160> requests<00:12:54.760> header<00:12:55.160> from<00:12:55.320> the 00:12:55.430 --> 00:12:55.440 align:start position:0% the code that requests header from the 00:12:55.440 --> 00:12:57.670 align:start position:0% the code that requests header from the Builder<00:12:56.040> we<00:12:56.120> don't<00:12:56.279> need<00:12:56.399> to<00:12:56.519> change<00:12:56.839> that<00:12:57.560> the 00:12:57.670 --> 00:12:57.680 align:start position:0% Builder we don't need to change that the 00:12:57.680 --> 00:12:58.870 align:start position:0% Builder we don't need to change that the only<00:12:57.920> thing<00:12:58.079> that<00:12:58.160> we<00:12:58.279> need<00:12:58.360> to<00:12:58.480> check<00:12:58.680> is<00:12:58.760> that 00:12:58.870 --> 00:12:58.880 align:start position:0% only thing that we need to check is that 00:12:58.880 --> 00:13:00.870 align:start position:0% only thing that we need to check is that the<00:12:59.199> signature<00:12:59.680> will<00:12:59.839> be<00:13:00.040> different<00:13:00.720> it's 00:13:00.870 --> 00:13:00.880 align:start position:0% the signature will be different it's 00:13:00.880 --> 00:13:02.430 align:start position:0% the signature will be different it's coming<00:13:01.120> from<00:13:01.279> a<00:13:01.440> particular 00:13:02.430 --> 00:13:02.440 align:start position:0% coming from a particular 00:13:02.440 --> 00:13:04.949 align:start position:0% coming from a particular validator<00:13:03.440> so<00:13:03.839> the<00:13:04.000> heavy<00:13:04.199> lifting<00:13:04.560> is<00:13:04.680> done 00:13:04.949 --> 00:13:04.959 align:start position:0% validator so the heavy lifting is done 00:13:04.959 --> 00:13:06.790 align:start position:0% validator so the heavy lifting is done in<00:13:05.040> a<00:13:05.160> minimal<00:13:05.560> way<00:13:05.800> and<00:13:06.000> adding<00:13:06.320> an<00:13:06.480> auction 00:13:06.790 --> 00:13:06.800 align:start position:0% in a minimal way and adding an auction 00:13:06.800 --> 00:13:10.189 align:start position:0% in a minimal way and adding an auction to<00:13:07.000> get<00:13:07.279> Block<00:13:07.560> auctions<00:13:08.120> is 00:13:10.189 --> 00:13:10.199 align:start position:0% to get Block auctions is 00:13:10.199 --> 00:13:12.790 align:start position:0% to get Block auctions is Trivial<00:13:11.199> so<00:13:11.480> what<00:13:11.600> are<00:13:12.160> the<00:13:12.320> things<00:13:12.560> that 00:13:12.790 --> 00:13:12.800 align:start position:0% Trivial so what are the things that 00:13:12.800 --> 00:13:15.230 align:start position:0% Trivial so what are the things that actually<00:13:13.120> change<00:13:13.920> the<00:13:14.120> problems<00:13:14.560> that<00:13:14.800> adding 00:13:15.230 --> 00:13:15.240 align:start position:0% actually change the problems that adding 00:13:15.240 --> 00:13:18.550 align:start position:0% actually change the problems that adding the<00:13:15.360> auction<00:13:16.040> increases<00:13:17.040> is<00:13:17.279> that<00:13:17.680> in<00:13:17.920> a<00:13:18.120> world 00:13:18.550 --> 00:13:18.560 align:start position:0% the auction increases is that in a world 00:13:18.560 --> 00:13:21.150 align:start position:0% the auction increases is that in a world in<00:13:18.760> which<00:13:18.959> the<00:13:19.120> proposer<00:13:19.880> and<00:13:20.040> the<00:13:20.160> Builder 00:13:21.150 --> 00:13:21.160 align:start position:0% in which the proposer and the Builder 00:13:21.160 --> 00:13:24.269 align:start position:0% in which the proposer and the Builder may<00:13:21.360> be<00:13:21.639> different<00:13:22.639> then<00:13:22.800> you<00:13:22.920> need<00:13:23.160> to<00:13:23.880> give 00:13:24.269 --> 00:13:24.279 align:start position:0% may be different then you need to give 00:13:24.279 --> 00:13:26.910 align:start position:0% may be different then you need to give certain<00:13:24.760> safeties<00:13:25.320> to<00:13:25.480> the<00:13:25.600> Builder<00:13:26.600> if<00:13:26.760> the 00:13:26.910 --> 00:13:26.920 align:start position:0% certain safeties to the Builder if the 00:13:26.920 --> 00:13:28.230 align:start position:0% certain safeties to the Builder if the proposer<00:13:27.279> and<00:13:27.360> the<00:13:27.440> Builder<00:13:27.720> is<00:13:27.839> the<00:13:27.959> same 00:13:28.230 --> 00:13:28.240 align:start position:0% proposer and the Builder is the same 00:13:28.240 --> 00:13:30.590 align:start position:0% proposer and the Builder is the same then<00:13:28.360> you<00:13:28.480> don't<00:13:28.760> care<00:13:29.399> about<00:13:29.880> protecting<00:13:30.399> the 00:13:30.590 --> 00:13:30.600 align:start position:0% then you don't care about protecting the 00:13:30.600 --> 00:13:33.230 align:start position:0% then you don't care about protecting the Builder<00:13:31.600> if<00:13:31.800> the<00:13:31.959> payload<00:13:32.440> came<00:13:32.639> late<00:13:33.000> or<00:13:33.120> if 00:13:33.230 --> 00:13:33.240 align:start position:0% Builder if the payload came late or if 00:13:33.240 --> 00:13:35.990 align:start position:0% Builder if the payload came late or if the<00:13:33.360> payload<00:13:34.279> did<00:13:34.720> if<00:13:34.880> the<00:13:35.000> Builder<00:13:35.320> wanted<00:13:35.600> to 00:13:35.990 --> 00:13:36.000 align:start position:0% the payload did if the Builder wanted to 00:13:36.000 --> 00:13:38.670 align:start position:0% the payload did if the Builder wanted to withhold<00:13:36.440> the<00:13:36.600> payload<00:13:37.600> this<00:13:37.680> is<00:13:37.920> because 00:13:38.670 --> 00:13:38.680 align:start position:0% withhold the payload this is because 00:13:38.680 --> 00:13:39.910 align:start position:0% withhold the payload this is because well<00:13:38.839> the<00:13:38.959> proposer<00:13:39.360> is<00:13:39.480> the<00:13:39.600> same<00:13:39.760> as<00:13:39.839> the 00:13:39.910 --> 00:13:39.920 align:start position:0% well the proposer is the same as the 00:13:39.920 --> 00:13:41.470 align:start position:0% well the proposer is the same as the Builder<00:13:40.320> he<00:13:40.440> should<00:13:40.600> have<00:13:40.760> sent<00:13:41.040> everything 00:13:41.470 --> 00:13:41.480 align:start position:0% Builder he should have sent everything 00:13:41.480 --> 00:13:43.629 align:start position:0% Builder he should have sent everything together<00:13:42.360> but<00:13:42.480> in<00:13:42.600> a<00:13:42.680> world<00:13:42.920> in<00:13:43.040> with<00:13:43.199> the<00:13:43.560> in 00:13:43.629 --> 00:13:43.639 align:start position:0% together but in a world in with the in 00:13:43.639 --> 00:13:44.910 align:start position:0% together but in a world in with the in which<00:13:43.800> the<00:13:43.920> proposer<00:13:44.320> and<00:13:44.440> the<00:13:44.519> Builder<00:13:44.760> are 00:13:44.910 --> 00:13:44.920 align:start position:0% which the proposer and the Builder are 00:13:44.920 --> 00:13:46.230 align:start position:0% which the proposer and the Builder are different<00:13:45.480> you<00:13:45.600> need<00:13:45.720> to<00:13:45.880> protect<00:13:46.160> the 00:13:46.230 --> 00:13:46.240 align:start position:0% different you need to protect the 00:13:46.240 --> 00:13:48.470 align:start position:0% different you need to protect the Builder<00:13:47.120> you<00:13:47.240> need<00:13:47.399> to<00:13:47.680> give<00:13:47.880> assurances<00:13:48.360> to 00:13:48.470 --> 00:13:48.480 align:start position:0% Builder you need to give assurances to 00:13:48.480 --> 00:13:49.629 align:start position:0% Builder you need to give assurances to the<00:13:48.560> Builder<00:13:48.920> that<00:13:49.040> if<00:13:49.160> the<00:13:49.279> Builder 00:13:49.629 --> 00:13:49.639 align:start position:0% the Builder that if the Builder 00:13:49.639 --> 00:13:52.430 align:start position:0% the Builder that if the Builder submitted<00:13:50.240> his<00:13:50.440> block<00:13:51.320> on<00:13:51.560> time<00:13:52.000> the<00:13:52.120> block<00:13:52.320> is 00:13:52.430 --> 00:13:52.440 align:start position:0% submitted his block on time the block is 00:13:52.440 --> 00:13:54.509 align:start position:0% submitted his block on time the block is canonical<00:13:53.000> the<00:13:53.120> payload<00:13:53.440> is<00:13:53.519> canonical<00:13:54.399> and 00:13:54.509 --> 00:13:54.519 align:start position:0% canonical the payload is canonical and 00:13:54.519 --> 00:13:56.350 align:start position:0% canonical the payload is canonical and you<00:13:54.600> need<00:13:54.759> to<00:13:54.880> give<00:13:55.040> assurances<00:13:55.480> of<00:13:55.720> hard<00:13:55.959> one 00:13:56.350 --> 00:13:56.360 align:start position:0% you need to give assurances of hard one 00:13:56.360 --> 00:13:59.110 align:start position:0% you need to give assurances of hard one is<00:13:56.519> a<00:13:56.720> new<00:13:57.320> situation<00:13:58.279> this<00:13:58.399> was<00:13:58.519> a<00:13:58.639> previous 00:13:59.110 --> 00:13:59.120 align:start position:0% is a new situation this was a previous 00:13:59.120 --> 00:14:01.030 align:start position:0% is a new situation this was a previous slide<00:13:59.759> where<00:13:59.959> the<00:14:00.079> three<00:14:00.320> phenomenas<00:14:00.800> could 00:14:01.030 --> 00:14:01.040 align:start position:0% slide where the three phenomenas could 00:14:01.040 --> 00:14:03.069 align:start position:0% slide where the three phenomenas could happen<00:14:01.680> this<00:14:01.800> is<00:14:02.160> the<00:14:02.279> full<00:14:02.560> the<00:14:02.680> block<00:14:02.920> was 00:14:03.069 --> 00:14:03.079 align:start position:0% happen this is the full the block was 00:14:03.079 --> 00:14:06.509 align:start position:0% happen this is the full the block was full<00:14:03.880> here<00:14:04.519> the<00:14:04.680> proposal<00:14:05.079> of<00:14:05.320> slot<00:14:05.680> n<00:14:06.320> is 00:14:06.509 --> 00:14:06.519 align:start position:0% full here the proposal of slot n is 00:14:06.519 --> 00:14:09.110 align:start position:0% full here the proposal of slot n is building<00:14:06.880> on<00:14:07.079> top<00:14:07.240> of<00:14:07.320> an<00:14:07.480> empty<00:14:08.079> slot<00:14:08.880> here 00:14:09.110 --> 00:14:09.120 align:start position:0% building on top of an empty slot here 00:14:09.120 --> 00:14:12.350 align:start position:0% building on top of an empty slot here the<00:14:09.279> proposer<00:14:09.639> of<00:14:09.759> slot<00:14:10.040> n<00:14:10.440> is<00:14:10.639> reorg<00:14:11.360> entirely 00:14:12.350 --> 00:14:12.360 align:start position:0% the proposer of slot n is reorg entirely 00:14:12.360 --> 00:14:14.509 align:start position:0% the proposer of slot n is reorg entirely the<00:14:12.839> previous<00:14:13.199> block<00:14:13.759> but<00:14:13.880> now<00:14:14.040> we<00:14:14.120> have<00:14:14.240> a<00:14:14.320> new 00:14:14.509 --> 00:14:14.519 align:start position:0% the previous block but now we have a new 00:14:14.519 --> 00:14:16.550 align:start position:0% the previous block but now we have a new situation<00:14:15.120> in<00:14:15.279> which<00:14:15.440> the<00:14:15.560> proposer<00:14:15.920> of<00:14:16.040> slot 00:14:16.550 --> 00:14:16.560 align:start position:0% situation in which the proposer of slot 00:14:16.560 --> 00:14:19.910 align:start position:0% situation in which the proposer of slot n<00:14:17.560> is<00:14:17.759> trying<00:14:18.120> to<00:14:18.399> make<00:14:18.759> the<00:14:18.920> Builder<00:14:19.440> pay<00:14:19.680> for 00:14:19.910 --> 00:14:19.920 align:start position:0% n is trying to make the Builder pay for 00:14:19.920 --> 00:14:22.509 align:start position:0% n is trying to make the Builder pay for a<00:14:20.199> payload<00:14:20.920> that<00:14:21.040> he<00:14:21.160> didn't<00:14:21.399> reveal<00:14:22.160> because 00:14:22.509 --> 00:14:22.519 align:start position:0% a payload that he didn't reveal because 00:14:22.519 --> 00:14:24.990 align:start position:0% a payload that he didn't reveal because the<00:14:22.680> previous<00:14:23.079> block<00:14:23.399> was<00:14:23.600> weak<00:14:24.600> so<00:14:24.759> we<00:14:24.880> need 00:14:24.990 --> 00:14:25.000 align:start position:0% the previous block was weak so we need 00:14:25.000 --> 00:14:27.110 align:start position:0% the previous block was weak so we need to<00:14:25.399> prevent<00:14:25.800> that<00:14:25.959> situation<00:14:26.360> from<00:14:26.600> happening 00:14:27.110 --> 00:14:27.120 align:start position:0% to prevent that situation from happening 00:14:27.120 --> 00:14:28.749 align:start position:0% to prevent that situation from happening and<00:14:27.279> this<00:14:27.399> is<00:14:27.480> a<00:14:27.639> minimal<00:14:28.000> change<00:14:28.240> likely<00:14:28.600> for 00:14:28.749 --> 00:14:28.759 align:start position:0% and this is a minimal change likely for 00:14:28.759 --> 00:14:29.910 align:start position:0% and this is a minimal change likely for us 00:14:29.910 --> 00:14:29.920 align:start position:0% us 00:14:29.920 --> 00:14:32.670 align:start position:0% us uh<00:14:30.800> EF<00:14:31.199> researchers<00:14:31.639> on<00:14:31.759> for<00:14:32.040> Choice<00:14:32.279> are<00:14:32.440> very 00:14:32.670 --> 00:14:32.680 align:start position:0% uh EF researchers on for Choice are very 00:14:32.680 --> 00:14:35.069 align:start position:0% uh EF researchers on for Choice are very good<00:14:33.240> and<00:14:33.480> we<00:14:33.680> have<00:14:34.079> minimal<00:14:34.519> solutions<00:14:34.880> for 00:14:35.069 --> 00:14:35.079 align:start position:0% good and we have minimal solutions for 00:14:35.079 --> 00:14:37.550 align:start position:0% good and we have minimal solutions for this<00:14:35.240> that<00:14:35.399> are<00:14:36.040> a<00:14:36.240> tiny<00:14:36.519> bit<00:14:36.720> more<00:14:36.880> of<00:14:37.120> code<00:14:37.399> to 00:14:37.550 --> 00:14:37.560 align:start position:0% this that are a tiny bit more of code to 00:14:37.560 --> 00:14:39.470 align:start position:0% this that are a tiny bit more of code to the<00:14:37.800> previous<00:14:38.160> heavy<00:14:38.399> lifting<00:14:38.880> which<00:14:39.000> is 00:14:39.470 --> 00:14:39.480 align:start position:0% the previous heavy lifting which is 00:14:39.480 --> 00:14:42.189 align:start position:0% the previous heavy lifting which is dealing<00:14:40.040> with<00:14:40.360> the<00:14:40.519> whole 00:14:42.189 --> 00:14:42.199 align:start position:0% dealing with the whole 00:14:42.199 --> 00:14:45.430 align:start position:0% dealing with the whole tree<00:14:43.199> so<00:14:43.399> how<00:14:43.600> does<00:14:43.759> the<00:14:43.959> PB<00:14:44.519> epbs<00:14:45.079> slot 00:14:45.430 --> 00:14:45.440 align:start position:0% tree so how does the PB epbs slot 00:14:45.440 --> 00:14:48.389 align:start position:0% tree so how does the PB epbs slot actually<00:14:45.720> work<00:14:46.480> on<00:14:46.720> an<00:14:46.920> auction<00:14:47.399> mechanism 00:14:48.389 --> 00:14:48.399 align:start position:0% actually work on an auction mechanism 00:14:48.399 --> 00:14:51.150 align:start position:0% actually work on an auction mechanism the<00:14:49.360> builder<00:14:50.040> at<00:14:50.279> the<00:14:50.440> proposer<00:14:50.959> at<00:14:51.079> the 00:14:51.150 --> 00:14:51.160 align:start position:0% the builder at the proposer at the 00:14:51.160 --> 00:14:53.550 align:start position:0% the builder at the proposer at the beginning<00:14:51.440> of<00:14:51.519> the<00:14:51.680> slot<00:14:52.160> requests<00:14:53.079> exactly 00:14:53.550 --> 00:14:53.560 align:start position:0% beginning of the slot requests exactly 00:14:53.560 --> 00:14:55.870 align:start position:0% beginning of the slot requests exactly as<00:14:53.720> with<00:14:53.920> me<00:14:54.160> boo<00:14:54.399> today<00:14:54.759> with<00:14:54.880> the<00:14:55.199> exact 00:14:55.870 --> 00:14:55.880 align:start position:0% as with me boo today with the exact 00:14:55.880 --> 00:14:58.430 align:start position:0% as with me boo today with the exact lines<00:14:56.160> of<00:14:56.399> code<00:14:57.040> will<00:14:57.320> request<00:14:57.800> directly<00:14:58.240> from 00:14:58.430 --> 00:14:58.440 align:start position:0% lines of code will request directly from 00:14:58.440 --> 00:15:01.509 align:start position:0% lines of code will request directly from the<00:14:58.560> builders<00:14:59.199> not<00:14:59.399> the<00:14:59.600> relays<00:15:00.600> their<00:15:01.120> best 00:15:01.509 --> 00:15:01.519 align:start position:0% the builders not the relays their best 00:15:01.519 --> 00:15:03.590 align:start position:0% the builders not the relays their best bid<00:15:02.360> it<00:15:02.480> would<00:15:02.639> choose<00:15:02.920> whatever<00:15:03.240> bit<00:15:03.440> he 00:15:03.590 --> 00:15:03.600 align:start position:0% bid it would choose whatever bit he 00:15:03.600 --> 00:15:05.550 align:start position:0% bid it would choose whatever bit he wants<00:15:04.079> it<00:15:04.199> would<00:15:04.360> include<00:15:04.639> it<00:15:04.720> in<00:15:04.839> the<00:15:04.959> blog 00:15:05.550 --> 00:15:05.560 align:start position:0% wants it would include it in the blog 00:15:05.560 --> 00:15:08.189 align:start position:0% wants it would include it in the blog and<00:15:05.759> submit<00:15:06.199> his<00:15:06.639> consensus<00:15:07.199> block<00:15:07.800> that<00:15:07.959> can 00:15:08.189 --> 00:15:08.199 align:start position:0% and submit his consensus block that can 00:15:08.199 --> 00:15:10.829 align:start position:0% and submit his consensus block that can be<00:15:08.519> validated<00:15:09.120> immediately<00:15:10.120> before<00:15:10.560> 3 00:15:10.829 --> 00:15:10.839 align:start position:0% be validated immediately before 3 00:15:10.839 --> 00:15:12.430 align:start position:0% be validated immediately before 3 seconds<00:15:11.199> we<00:15:11.320> could<00:15:11.440> have<00:15:11.560> been<00:15:11.800> two<00:15:12.040> seconds 00:15:12.430 --> 00:15:12.440 align:start position:0% seconds we could have been two seconds 00:15:12.440 --> 00:15:14.189 align:start position:0% seconds we could have been two seconds actually<00:15:13.040> because<00:15:13.279> we<00:15:13.399> don't<00:15:13.560> need<00:15:13.800> time<00:15:14.000> to 00:15:14.189 --> 00:15:14.199 align:start position:0% actually because we don't need time to 00:15:14.199 --> 00:15:16.430 align:start position:0% actually because we don't need time to propose<00:15:14.639> blocks<00:15:15.279> consensus 00:15:16.430 --> 00:15:16.440 align:start position:0% propose blocks consensus 00:15:16.440 --> 00:15:19.710 align:start position:0% propose blocks consensus blocks<00:15:17.440> the<00:15:17.639> rest<00:15:17.920> of<00:15:18.120> the<00:15:18.240> slot<00:15:18.759> well<00:15:19.040> the<00:15:19.360> the 00:15:19.710 --> 00:15:19.720 align:start position:0% blocks the rest of the slot well the the 00:15:19.720 --> 00:15:22.430 align:start position:0% blocks the rest of the slot well the the Builder<00:15:20.360> would<00:15:20.959> now<00:15:21.320> have<00:15:21.440> to<00:15:21.600> be<00:15:21.800> protected 00:15:22.430 --> 00:15:22.440 align:start position:0% Builder would now have to be protected 00:15:22.440 --> 00:15:24.389 align:start position:0% Builder would now have to be protected is<00:15:22.560> going<00:15:22.759> to<00:15:23.000> count<00:15:23.360> attestations<00:15:24.000> for<00:15:24.240> that 00:15:24.389 --> 00:15:24.399 align:start position:0% is going to count attestations for that 00:15:24.399 --> 00:15:26.629 align:start position:0% is going to count attestations for that block<00:15:24.839> it's<00:15:25.040> going<00:15:25.199> to<00:15:25.360> count<00:15:25.600> for<00:15:25.839> one<00:15:26.120> second 00:15:26.629 --> 00:15:26.639 align:start position:0% block it's going to count for one second 00:15:26.639 --> 00:15:29.150 align:start position:0% block it's going to count for one second until<00:15:26.920> he<00:15:27.120> reaches<00:15:27.560> enough<00:15:27.959> attestations<00:15:29.000> in 00:15:29.150 --> 00:15:29.160 align:start position:0% until he reaches enough attestations in 00:15:29.160 --> 00:15:30.670 align:start position:0% until he reaches enough attestations in practice<00:15:29.480> it's<00:15:29.600> going<00:15:29.720> to<00:15:29.800> be<00:15:29.920> 40%<00:15:30.480> of 00:15:30.670 --> 00:15:30.680 align:start position:0% practice it's going to be 40% of 00:15:30.680 --> 00:15:33.870 align:start position:0% practice it's going to be 40% of attestations<00:15:31.680> once<00:15:32.040> the<00:15:32.160> Builder<00:15:32.600> saw<00:15:33.079> 40%<00:15:33.720> of 00:15:33.870 --> 00:15:33.880 align:start position:0% attestations once the Builder saw 40% of 00:15:33.880 --> 00:15:35.710 align:start position:0% attestations once the Builder saw 40% of attestations<00:15:34.399> for<00:15:34.600> the<00:15:34.720> block<00:15:35.199> the<00:15:35.319> Builder 00:15:35.710 --> 00:15:35.720 align:start position:0% attestations for the block the Builder 00:15:35.720 --> 00:15:38.069 align:start position:0% attestations for the block the Builder knows<00:15:36.160> that<00:15:36.360> that<00:15:36.519> block<00:15:36.800> cannot<00:15:37.160> be 00:15:38.069 --> 00:15:38.079 align:start position:0% knows that that block cannot be 00:15:38.079 --> 00:15:41.189 align:start position:0% knows that that block cannot be reor<00:15:39.079> therefore<00:15:39.360> the<00:15:39.440> Builder<00:15:39.759> Reveals<00:15:40.160> His 00:15:41.189 --> 00:15:41.199 align:start position:0% reor therefore the Builder Reveals His 00:15:41.199 --> 00:15:43.749 align:start position:0% reor therefore the Builder Reveals His payload<00:15:42.199> this<00:15:42.319> is<00:15:42.440> a<00:15:42.680> 4<00:15:43.000> seconds<00:15:43.319> so<00:15:43.440> you<00:15:43.560> have 00:15:43.749 --> 00:15:43.759 align:start position:0% payload this is a 4 seconds so you have 00:15:43.759 --> 00:15:46.790 align:start position:0% payload this is a 4 seconds so you have since<00:15:44.160> then<00:15:44.600> until<00:15:45.160> the<00:15:45.480> very<00:15:45.800> next<00:15:46.120> slot<00:15:46.600> to 00:15:46.790 --> 00:15:46.800 align:start position:0% since then until the very next slot to 00:15:46.800 --> 00:15:48.189 align:start position:0% since then until the very next slot to validate<00:15:47.160> the<00:15:47.240> payload<00:15:47.639> you<00:15:47.720> can<00:15:47.839> just 00:15:48.189 --> 00:15:48.199 align:start position:0% validate the payload you can just 00:15:48.199 --> 00:15:49.949 align:start position:0% validate the payload you can just increase<00:15:48.600> the<00:15:48.720> gas<00:15:48.920> limit<00:15:49.160> a<00:15:49.279> lot<00:15:49.480> if<00:15:49.600> we<00:15:49.720> could 00:15:49.949 --> 00:15:49.959 align:start position:0% increase the gas limit a lot if we could 00:15:49.959 --> 00:15:53.949 align:start position:0% increase the gas limit a lot if we could manage<00:15:50.560> to<00:15:50.759> solve<00:15:51.639> the<00:15:52.480> disk<00:15:53.360> uh<00:15:53.519> the<00:15:53.680> state 00:15:53.949 --> 00:15:53.959 align:start position:0% manage to solve the disk uh the state 00:15:53.959 --> 00:15:56.990 align:start position:0% manage to solve the disk uh the state growth<00:15:54.639> problem<00:15:55.639> uh<00:15:55.920> you<00:15:56.120> can<00:15:56.319> increase<00:15:56.800> the 00:15:56.990 --> 00:15:57.000 align:start position:0% growth problem uh you can increase the 00:15:57.000 --> 00:15:59.030 align:start position:0% growth problem uh you can increase the blob<00:15:57.399> number<00:15:57.880> a<00:15:58.040> lot<00:15:58.399> because<00:15:58.600> now<00:15:58.720> we<00:15:58.800> have 00:15:59.030 --> 00:15:59.040 align:start position:0% blob number a lot because now we have 00:15:59.040 --> 00:16:00.749 align:start position:0% blob number a lot because now we have have<00:15:59.120> 12<00:15:59.399> seconds<00:15:59.680> to<00:15:59.839> distribute<00:16:00.240> the<00:16:00.319> blocks 00:16:00.749 --> 00:16:00.759 align:start position:0% have 12 seconds to distribute the blocks 00:16:00.759 --> 00:16:02.309 align:start position:0% have 12 seconds to distribute the blocks you<00:16:00.880> don't<00:16:01.079> have<00:16:01.279> two<00:16:01.759> two<00:16:01.920> seconds<00:16:02.160> to 00:16:02.309 --> 00:16:02.319 align:start position:0% you don't have two two seconds to 00:16:02.319 --> 00:16:03.550 align:start position:0% you don't have two two seconds to distribute<00:16:02.759> the 00:16:03.550 --> 00:16:03.560 align:start position:0% distribute the 00:16:03.560 --> 00:16:05.990 align:start position:0% distribute the blocks<00:16:04.560> later<00:16:04.800> on<00:16:05.000> there's<00:16:05.160> a<00:16:05.279> light<00:16:05.519> vote 00:16:05.990 --> 00:16:06.000 align:start position:0% blocks later on there's a light vote 00:16:06.000 --> 00:16:08.470 align:start position:0% blocks later on there's a light vote there's<00:16:06.199> a<00:16:06.319> light<00:16:06.560> vote<00:16:06.959> by<00:16:07.319> a<00:16:07.560> committee<00:16:08.000> of 00:16:08.470 --> 00:16:08.480 align:start position:0% there's a light vote by a committee of 00:16:08.480 --> 00:16:13.389 align:start position:0% there's a light vote by a committee of 512<00:16:09.759> members<00:16:10.759> and<00:16:11.000> that<00:16:11.199> vote<00:16:11.480> is<00:16:11.639> to<00:16:12.399> Signal 00:16:13.389 --> 00:16:13.399 align:start position:0% 512 members and that vote is to Signal 00:16:13.399 --> 00:16:15.749 align:start position:0% 512 members and that vote is to Signal the<00:16:13.639> rest<00:16:13.880> of<00:16:14.000> the<00:16:14.120> chain<00:16:14.600> that<00:16:15.160> the<00:16:15.319> payload 00:16:15.749 --> 00:16:15.759 align:start position:0% the rest of the chain that the payload 00:16:15.759 --> 00:16:18.030 align:start position:0% the rest of the chain that the payload was<00:16:15.959> on<00:16:16.160> time<00:16:16.880> that<00:16:17.040> the<00:16:17.160> next<00:16:17.399> proposer 00:16:18.030 --> 00:16:18.040 align:start position:0% was on time that the next proposer 00:16:18.040 --> 00:16:20.230 align:start position:0% was on time that the next proposer should<00:16:18.319> not<00:16:18.560> reort<00:16:19.079> the 00:16:20.230 --> 00:16:20.240 align:start position:0% should not reort the 00:16:20.240 --> 00:16:22.870 align:start position:0% should not reort the payload<00:16:21.240> there<00:16:21.360> are<00:16:21.519> other<00:16:21.839> designs<00:16:22.440> that<00:16:22.639> do 00:16:22.870 --> 00:16:22.880 align:start position:0% payload there are other designs that do 00:16:22.880 --> 00:16:24.949 align:start position:0% payload there are other designs that do not<00:16:23.120> include<00:16:23.759> uh<00:16:24.199> that<00:16:24.319> do<00:16:24.440> not<00:16:24.600> include<00:16:24.880> a 00:16:24.949 --> 00:16:24.959 align:start position:0% not include uh that do not include a 00:16:24.959 --> 00:16:26.309 align:start position:0% not include uh that do not include a light<00:16:25.160> vote<00:16:25.440> there<00:16:25.639> there<00:16:25.720> were<00:16:25.959> previous 00:16:26.309 --> 00:16:26.319 align:start position:0% light vote there there were previous 00:16:26.319 --> 00:16:28.509 align:start position:0% light vote there there were previous designs<00:16:26.800> that<00:16:26.959> included<00:16:27.560> a<00:16:27.720> full<00:16:28.079> vote<00:16:28.360> an 00:16:28.509 --> 00:16:28.519 align:start position:0% designs that included a full vote an 00:16:28.519 --> 00:16:30.350 align:start position:0% designs that included a full vote an aggregated<00:16:29.120> vote<00:16:29.519> an<00:16:29.639> attestation<00:16:30.120> of<00:16:30.240> the 00:16:30.350 --> 00:16:30.360 align:start position:0% aggregated vote an attestation of the 00:16:30.360 --> 00:16:33.030 align:start position:0% aggregated vote an attestation of the whole<00:16:30.639> committee<00:16:31.120> for<00:16:31.319> the<00:16:31.440> payload<00:16:31.839> or<00:16:32.040> not 00:16:33.030 --> 00:16:33.040 align:start position:0% whole committee for the payload or not 00:16:33.040 --> 00:16:34.990 align:start position:0% whole committee for the payload or not uh<00:16:33.160> but<00:16:33.319> this<00:16:33.519> design<00:16:33.880> is<00:16:34.160> robust<00:16:34.600> enough<00:16:34.920> and 00:16:34.990 --> 00:16:35.000 align:start position:0% uh but this design is robust enough and 00:16:35.000 --> 00:16:39.269 align:start position:0% uh but this design is robust enough and it<00:16:35.160> requires<00:16:35.560> only<00:16:36.040> 512 00:16:39.269 --> 00:16:39.279 align:start position:0% 00:16:39.279 --> 00:16:41.110 align:start position:0% signatures<00:16:40.279> so<00:16:40.440> let<00:16:40.560> me<00:16:40.639> tell<00:16:40.759> you<00:16:40.880> about 00:16:41.110 --> 00:16:41.120 align:start position:0% signatures so let me tell you about 00:16:41.120 --> 00:16:44.710 align:start position:0% signatures so let me tell you about implementation<00:16:41.759> status<00:16:42.639> of<00:16:43.360> uh<00:16:44.319> I'm<00:16:44.440> not<00:16:44.560> sure 00:16:44.710 --> 00:16:44.720 align:start position:0% implementation status of uh I'm not sure 00:16:44.720 --> 00:16:48.910 align:start position:0% implementation status of uh I'm not sure if<00:16:44.839> I<00:16:44.959> can<00:16:45.639> ah<00:16:46.040> yes<00:16:47.040> it's<00:16:47.279> an<00:16:47.480> empty<00:16:48.000> video<00:16:48.440> but 00:16:48.910 --> 00:16:48.920 align:start position:0% if I can ah yes it's an empty video but 00:16:48.920 --> 00:16:50.189 align:start position:0% if I can ah yes it's an empty video but uh<00:16:49.040> let<00:16:49.120> me<00:16:49.240> tell<00:16:49.360> you<00:16:49.440> about<00:16:49.639> implementation 00:16:50.189 --> 00:16:50.199 align:start position:0% uh let me tell you about implementation 00:16:50.199 --> 00:16:52.030 align:start position:0% uh let me tell you about implementation status<00:16:50.519> of<00:16:50.680> this<00:16:50.959> so<00:16:51.240> we<00:16:51.360> wanted<00:16:51.639> to<00:16:51.800> have<00:16:51.920> a 00:16:52.030 --> 00:16:52.040 align:start position:0% status of this so we wanted to have a 00:16:52.040 --> 00:16:54.949 align:start position:0% status of this so we wanted to have a proof<00:16:52.240> of<00:16:53.160> uh<00:16:53.600> yeah<00:16:53.720> a<00:16:53.839> proof<00:16:54.040> of<00:16:54.240> concept 00:16:54.949 --> 00:16:54.959 align:start position:0% proof of uh yeah a proof of concept 00:16:54.959 --> 00:16:58.629 align:start position:0% proof of uh yeah a proof of concept model<00:16:55.360> for<00:16:55.800> EBS<00:16:56.600> and<00:16:56.720> we<00:16:56.880> have<00:16:57.000> it<00:16:57.680> there's<00:16:58.399> uh 00:16:58.629 --> 00:16:58.639 align:start position:0% model for EBS and we have it there's uh 00:16:58.639 --> 00:17:01.069 align:start position:0% model for EBS and we have it there's uh we<00:16:58.880> we<00:16:58.959> are<00:16:59.160> finalizing<00:16:59.839> epbs<00:17:00.680> locally 00:17:01.069 --> 00:17:01.079 align:start position:0% we we are finalizing epbs locally 00:17:01.079 --> 00:17:02.350 align:start position:0% we we are finalizing epbs locally constructing<00:17:01.560> blocks<00:17:01.839> so<00:17:02.000> we're<00:17:02.160> not 00:17:02.350 --> 00:17:02.360 align:start position:0% constructing blocks so we're not 00:17:02.360 --> 00:17:04.110 align:start position:0% constructing blocks so we're not contacting<00:17:02.720> a<00:17:02.839> builder<00:17:03.519> but<00:17:03.759> we<00:17:03.880> are 00:17:04.110 --> 00:17:04.120 align:start position:0% contacting a builder but we are 00:17:04.120 --> 00:17:06.710 align:start position:0% contacting a builder but we are finalizing<00:17:04.799> a<00:17:04.959> Network<00:17:05.559> that<00:17:06.160> has<00:17:06.559> the 00:17:06.710 --> 00:17:06.720 align:start position:0% finalizing a Network that has the 00:17:06.720 --> 00:17:09.669 align:start position:0% finalizing a Network that has the payload<00:17:07.120> and<00:17:07.240> the<00:17:07.319> block<00:17:08.000> separated<00:17:09.000> um<00:17:09.400> two 00:17:09.669 --> 00:17:09.679 align:start position:0% payload and the block separated um two 00:17:09.679 --> 00:17:12.470 align:start position:0% payload and the block separated um two clients<00:17:10.079> two<00:17:10.280> consensus<00:17:10.760> clients<00:17:11.679> have<00:17:12.280> have 00:17:12.470 --> 00:17:12.480 align:start position:0% clients two consensus clients have have 00:17:12.480 --> 00:17:14.789 align:start position:0% clients two consensus clients have have already<00:17:13.000> the<00:17:13.079> implementation<00:17:13.559> is<00:17:13.799> underway 00:17:14.789 --> 00:17:14.799 align:start position:0% already the implementation is underway 00:17:14.799 --> 00:17:17.630 align:start position:0% already the implementation is underway um<00:17:15.439> te<00:17:16.079> I<00:17:16.160> believe<00:17:16.480> is<00:17:16.679> close<00:17:17.000> to<00:17:17.120> being<00:17:17.319> an 00:17:17.630 --> 00:17:17.640 align:start position:0% um te I believe is close to being an 00:17:17.640 --> 00:17:20.750 align:start position:0% um te I believe is close to being an interupt<00:17:18.640> uh<00:17:18.799> Nimbus<00:17:19.319> has<00:17:19.480> two<00:17:19.720> EPF<00:17:20.640> uh 00:17:20.750 --> 00:17:20.760 align:start position:0% interupt uh Nimbus has two EPF uh 00:17:20.760 --> 00:17:23.270 align:start position:0% interupt uh Nimbus has two EPF uh working<00:17:21.039> on<00:17:21.319> this<00:17:22.000> uh<00:17:22.120> loads<00:17:22.439> are<00:17:22.600> on<00:17:22.760> Li<00:17:23.039> house 00:17:23.270 --> 00:17:23.280 align:start position:0% working on this uh loads are on Li house 00:17:23.280 --> 00:17:24.710 align:start position:0% working on this uh loads are on Li house I<00:17:23.400> think<00:17:23.559> they<00:17:23.720> initiated<00:17:24.319> at<00:17:24.400> least<00:17:24.559> they 00:17:24.710 --> 00:17:24.720 align:start position:0% I think they initiated at least they 00:17:24.720 --> 00:17:26.270 align:start position:0% I think they initiated at least they have<00:17:24.839> the<00:17:25.000> typing<00:17:25.600> but<00:17:25.880> they<00:17:26.039> haven't 00:17:26.270 --> 00:17:26.280 align:start position:0% have the typing but they haven't 00:17:26.280 --> 00:17:28.189 align:start position:0% have the typing but they haven't Advanced<00:17:26.640> much<00:17:26.839> more<00:17:27.319> but<00:17:27.480> the<00:17:27.679> point<00:17:27.880> is<00:17:28.039> that 00:17:28.189 --> 00:17:28.199 align:start position:0% Advanced much more but the point is that 00:17:28.199 --> 00:17:30.909 align:start position:0% Advanced much more but the point is that it<00:17:28.319> takes<00:17:29.320> it<00:17:29.480> took<00:17:29.720> us<00:17:30.120> a<00:17:30.280> couple<00:17:30.480> of<00:17:30.640> months 00:17:30.909 --> 00:17:30.919 align:start position:0% it takes it took us a couple of months 00:17:30.919 --> 00:17:33.870 align:start position:0% it takes it took us a couple of months of<00:17:31.080> sitting<00:17:31.400> down<00:17:31.640> and<00:17:31.799> coding<00:17:32.320> not<00:17:32.760> more<00:17:33.760> uh 00:17:33.870 --> 00:17:33.880 align:start position:0% of sitting down and coding not more uh 00:17:33.880 --> 00:17:35.430 align:start position:0% of sitting down and coding not more uh it's<00:17:34.080> not<00:17:34.400> production<00:17:34.840> code<00:17:35.160> but<00:17:35.280> it's 00:17:35.430 --> 00:17:35.440 align:start position:0% it's not production code but it's 00:17:35.440 --> 00:17:38.630 align:start position:0% it's not production code but it's certainly<00:17:35.880> ready<00:17:36.440> the<00:17:36.720> the<00:17:36.960> EIP<00:17:37.440> is<00:17:37.600> ready<00:17:37.840> to 00:17:38.630 --> 00:17:38.640 align:start position:0% certainly ready the the EIP is ready to 00:17:38.640 --> 00:17:40.430 align:start position:0% certainly ready the the EIP is ready to go 00:17:40.430 --> 00:17:40.440 align:start position:0% go 00:17:40.440 --> 00:17:43.909 align:start position:0% go uh<00:17:41.440> as<00:17:41.600> I<00:17:41.840> described<00:17:42.720> there's<00:17:43.039> no<00:17:43.280> changes<00:17:43.799> I'm 00:17:43.909 --> 00:17:43.919 align:start position:0% uh as I described there's no changes I'm 00:17:43.919 --> 00:17:45.950 align:start position:0% uh as I described there's no changes I'm only<00:17:44.120> mentioning<00:17:44.679> consensus<00:17:45.120> layer<00:17:45.400> changes 00:17:45.950 --> 00:17:45.960 align:start position:0% only mentioning consensus layer changes 00:17:45.960 --> 00:17:47.390 align:start position:0% only mentioning consensus layer changes there's<00:17:46.160> no<00:17:46.360> changes<00:17:46.679> on<00:17:46.880> the<00:17:47.000> execution 00:17:47.390 --> 00:17:47.400 align:start position:0% there's no changes on the execution 00:17:47.400 --> 00:17:49.150 align:start position:0% there's no changes on the execution layer<00:17:47.960> that's<00:17:48.160> why<00:17:48.320> the<00:17:48.480> execution<00:17:48.880> layer 00:17:49.150 --> 00:17:49.160 align:start position:0% layer that's why the execution layer 00:17:49.160 --> 00:17:50.630 align:start position:0% layer that's why the execution layer guys<00:17:49.360> are<00:17:49.559> happy<00:17:49.880> because<00:17:50.200> we're<00:17:50.360> going<00:17:50.480> to 00:17:50.630 --> 00:17:50.640 align:start position:0% guys are happy because we're going to 00:17:50.640 --> 00:17:52.270 align:start position:0% guys are happy because we're going to give<00:17:50.840> them<00:17:51.080> a<00:17:51.200> lot<00:17:51.360> of<00:17:51.520> time<00:17:51.640> to<00:17:51.840> validate<00:17:52.160> the 00:17:52.270 --> 00:17:52.280 align:start position:0% give them a lot of time to validate the 00:17:52.280 --> 00:17:55.230 align:start position:0% give them a lot of time to validate the block<00:17:52.880> without<00:17:53.360> anything<00:17:53.840> on<00:17:54.240> without<00:17:54.880> them 00:17:55.230 --> 00:17:55.240 align:start position:0% block without anything on without them 00:17:55.240 --> 00:17:59.390 align:start position:0% block without anything on without them writing<00:17:55.600> a<00:17:55.720> single<00:17:55.960> line<00:17:56.120> of<00:17:56.520> quote<00:17:57.520> however 00:17:59.390 --> 00:17:59.400 align:start position:0% writing a single line of quote however 00:17:59.400 --> 00:18:01.470 align:start position:0% writing a single line of quote however the<00:17:59.600> interaction<00:18:00.159> with<00:18:00.360> fossil<00:18:01.039> is<00:18:01.240> not 00:18:01.470 --> 00:18:01.480 align:start position:0% the interaction with fossil is not 00:18:01.480 --> 00:18:03.590 align:start position:0% the interaction with fossil is not trivial<00:18:02.440> if<00:18:02.559> we<00:18:02.679> want<00:18:02.799> to<00:18:02.919> include<00:18:03.200> inclusion 00:18:03.590 --> 00:18:03.600 align:start position:0% trivial if we want to include inclusion 00:18:03.600 --> 00:18:04.909 align:start position:0% trivial if we want to include inclusion list<00:18:03.919> which<00:18:04.039> is<00:18:04.159> something<00:18:04.440> that<00:18:04.559> we<00:18:04.720> really 00:18:04.909 --> 00:18:04.919 align:start position:0% list which is something that we really 00:18:04.919 --> 00:18:07.029 align:start position:0% list which is something that we really need<00:18:05.200> in<00:18:05.520> in<00:18:05.640> ethereum<00:18:06.400> we're<00:18:06.640> going<00:18:06.760> to<00:18:06.919> have 00:18:07.029 --> 00:18:07.039 align:start position:0% need in in ethereum we're going to have 00:18:07.039 --> 00:18:08.549 align:start position:0% need in in ethereum we're going to have to<00:18:07.159> involve<00:18:07.480> the<00:18:07.600> execution<00:18:08.000> layer<00:18:08.320> and<00:18:08.440> the 00:18:08.549 --> 00:18:08.559 align:start position:0% to involve the execution layer and the 00:18:08.559 --> 00:18:10.590 align:start position:0% to involve the execution layer and the interaction<00:18:08.960> of<00:18:09.120> fossil<00:18:09.520> with<00:18:09.640> the<00:18:09.840> IP<00:18:10.240> with 00:18:10.590 --> 00:18:10.600 align:start position:0% interaction of fossil with the IP with 00:18:10.600 --> 00:18:12.990 align:start position:0% interaction of fossil with the IP with epbs<00:18:11.200> is<00:18:11.360> not<00:18:11.559> entirely<00:18:11.919> trivial<00:18:12.320> it's<00:18:12.480> not<00:18:12.919> uh 00:18:12.990 --> 00:18:13.000 align:start position:0% epbs is not entirely trivial it's not uh 00:18:13.000 --> 00:18:14.990 align:start position:0% epbs is not entirely trivial it's not uh something<00:18:13.280> that<00:18:13.400> I'll<00:18:13.600> describe<00:18:13.919> today<00:18:14.240> here 00:18:14.990 --> 00:18:15.000 align:start position:0% something that I'll describe today here 00:18:15.000 --> 00:18:20.549 align:start position:0% something that I'll describe today here all<00:18:15.159> right<00:18:15.600> thank<00:18:15.760> you<00:18:15.880> very<00:18:16.039> much 00:18:20.549 --> 00:18:20.559 align:start position:0% 00:18:20.559 --> 00:18:23.070 align:start position:0% guys<00:18:21.559> all<00:18:21.760> right<00:18:22.200> we'll<00:18:22.400> go<00:18:22.559> through<00:18:22.840> some 00:18:23.070 --> 00:18:23.080 align:start position:0% guys all right we'll go through some 00:18:23.080 --> 00:18:25.149 align:start position:0% guys all right we'll go through some questions<00:18:23.600> from<00:18:24.080> most<00:18:24.320> upvoted<00:18:24.880> are<00:18:25.000> there 00:18:25.149 --> 00:18:25.159 align:start position:0% questions from most upvoted are there 00:18:25.159 --> 00:18:26.590 align:start position:0% questions from most upvoted are there any<00:18:25.400> other<00:18:25.600> protocols<00:18:26.039> or<00:18:26.240> message 00:18:26.590 --> 00:18:26.600 align:start position:0% any other protocols or message 00:18:26.600 --> 00:18:28.430 align:start position:0% any other protocols or message propagation<00:18:27.120> mechanism<00:18:27.679> being<00:18:27.960> explored 00:18:28.430 --> 00:18:28.440 align:start position:0% propagation mechanism being explored 00:18:28.440 --> 00:18:31.029 align:start position:0% propagation mechanism being explored other<00:18:28.600> than<00:18:28.960> Li<00:18:29.240> P<00:18:29.400> to<00:18:29.600> be<00:18:29.960> not<00:18:30.120> that<00:18:30.240> I 00:18:31.029 --> 00:18:31.039 align:start position:0% other than Li P to be not that I 00:18:31.039 --> 00:18:33.909 align:start position:0% other than Li P to be not that I know<00:18:32.039> simple 00:18:33.909 --> 00:18:33.919 align:start position:0% know simple 00:18:33.919 --> 00:18:36.789 align:start position:0% know simple answer<00:18:34.919> after<00:18:35.200> implementing<00:18:35.679> epbs<00:18:36.240> on<00:18:36.400> prism 00:18:36.789 --> 00:18:36.799 align:start position:0% answer after implementing epbs on prism 00:18:36.799 --> 00:18:37.990 align:start position:0% answer after implementing epbs on prism how<00:18:36.919> would<00:18:37.039> you<00:18:37.120> rate<00:18:37.320> the<00:18:37.440> complexity<00:18:37.880> of 00:18:37.990 --> 00:18:38.000 align:start position:0% how would you rate the complexity of 00:18:38.000 --> 00:18:40.230 align:start position:0% how would you rate the complexity of changing<00:18:38.360> the<00:18:38.520> entire<00:18:38.960> consensus<00:18:39.720> execution 00:18:40.230 --> 00:18:40.240 align:start position:0% changing the entire consensus execution 00:18:40.240 --> 00:18:42.149 align:start position:0% changing the entire consensus execution validation<00:18:40.799> sync<00:18:41.280> Etc<00:18:41.840> while<00:18:42.000> still 00:18:42.149 --> 00:18:42.159 align:start position:0% validation sync Etc while still 00:18:42.159 --> 00:18:43.669 align:start position:0% validation sync Etc while still maintaining<00:18:42.640> backwards<00:18:43.000> compatibility 00:18:43.669 --> 00:18:43.679 align:start position:0% maintaining backwards compatibility 00:18:43.679 --> 00:18:45.950 align:start position:0% maintaining backwards compatibility that's<00:18:43.919> that's<00:18:44.039> a<00:18:44.200> great<00:18:44.480> question 00:18:45.950 --> 00:18:45.960 align:start position:0% that's that's a great question 00:18:45.960 --> 00:18:50.430 align:start position:0% that's that's a great question uh<00:18:46.960> it<00:18:47.120> was<00:18:47.679> much<00:18:48.000> harder<00:18:48.480> than<00:18:48.679> I<00:18:49.120> thought<00:18:50.120> uh 00:18:50.430 --> 00:18:50.440 align:start position:0% uh it was much harder than I thought uh 00:18:50.440 --> 00:18:55.549 align:start position:0% uh it was much harder than I thought uh Fortress<00:18:51.440> was<00:18:51.760> the<00:18:52.280> problem<00:18:53.280> and<00:18:53.840> uh<00:18:54.640> but<00:18:55.240> uh 00:18:55.549 --> 00:18:55.559 align:start position:0% Fortress was the problem and uh but uh 00:18:55.559 --> 00:18:58.190 align:start position:0% Fortress was the problem and uh but uh we<00:18:55.840> have<00:18:56.120> now<00:18:56.440> a<00:18:57.360> because<00:18:57.600> we<00:18:57.760> iterated 00:18:58.190 --> 00:18:58.200 align:start position:0% we have now a because we iterated 00:18:58.200 --> 00:19:00.110 align:start position:0% we have now a because we iterated several<00:18:58.480> times<00:18:58.919> until<00:18:59.200> we<00:18:59.360> realize<00:18:59.840> what<00:18:59.960> is 00:19:00.110 --> 00:19:00.120 align:start position:0% several times until we realize what is 00:19:00.120 --> 00:19:01.909 align:start position:0% several times until we realize what is the<00:19:00.280> right<00:19:00.440> way<00:19:00.559> of<00:19:00.720> doing<00:19:00.919> it<00:19:01.240> so<00:19:01.440> now 00:19:01.909 --> 00:19:01.919 align:start position:0% the right way of doing it so now 00:19:01.919 --> 00:19:03.669 align:start position:0% the right way of doing it so now backwards<00:19:02.400> looking<00:19:03.120> there<00:19:03.200> was<00:19:03.360> a<00:19:03.480> very 00:19:03.669 --> 00:19:03.679 align:start position:0% backwards looking there was a very 00:19:03.679 --> 00:19:05.350 align:start position:0% backwards looking there was a very simple<00:19:03.960> way<00:19:04.080> of<00:19:04.200> doing<00:19:04.440> it<00:19:04.600> so<00:19:04.799> my<00:19:04.960> original 00:19:05.350 --> 00:19:05.360 align:start position:0% simple way of doing it so my original 00:19:05.360 --> 00:19:07.230 align:start position:0% simple way of doing it so my original implementation<00:19:05.960> was<00:19:06.400> hard<00:19:06.760> but<00:19:06.880> now<00:19:07.039> we<00:19:07.120> have 00:19:07.230 --> 00:19:07.240 align:start position:0% implementation was hard but now we have 00:19:07.240 --> 00:19:08.470 align:start position:0% implementation was hard but now we have a<00:19:07.400> very<00:19:07.600> simple 00:19:08.470 --> 00:19:08.480 align:start position:0% a very simple 00:19:08.480 --> 00:19:11.470 align:start position:0% a very simple change<00:19:09.480> as<00:19:09.600> I<00:19:09.720> said<00:19:09.880> in<00:19:10.000> two<00:19:10.200> months<00:19:10.600> we<00:19:10.760> did<00:19:10.919> it 00:19:11.470 --> 00:19:11.480 align:start position:0% change as I said in two months we did it 00:19:11.480 --> 00:19:13.830 align:start position:0% change as I said in two months we did it now<00:19:11.720> I<00:19:11.840> believe<00:19:12.760> knowing<00:19:13.200> what<00:19:13.320> is<00:19:13.440> the<00:19:13.640> right 00:19:13.830 --> 00:19:13.840 align:start position:0% now I believe knowing what is the right 00:19:13.840 --> 00:19:15.549 align:start position:0% now I believe knowing what is the right design<00:19:14.320> we<00:19:14.440> could<00:19:14.559> have<00:19:14.760> done<00:19:14.919> it<00:19:15.039> in<00:19:15.120> two 00:19:15.549 --> 00:19:15.559 align:start position:0% design we could have done it in two 00:19:15.559 --> 00:19:18.149 align:start position:0% design we could have done it in two weeks<00:19:16.559> what<00:19:16.679> if<00:19:16.799> there's<00:19:16.960> a<00:19:17.280> reorg<00:19:17.840> larger 00:19:18.149 --> 00:19:18.159 align:start position:0% weeks what if there's a reorg larger 00:19:18.159 --> 00:19:21.669 align:start position:0% weeks what if there's a reorg larger than<00:19:18.360> depth<00:19:18.960> uh<00:19:19.080> of<00:19:19.240> one<00:19:19.760> nothing<00:19:20.200> changes<00:19:21.200> uh 00:19:21.669 --> 00:19:21.679 align:start position:0% than depth uh of one nothing changes uh 00:19:21.679 --> 00:19:24.350 align:start position:0% than depth uh of one nothing changes uh absolutely<00:19:22.120> nothing<00:19:22.360> changes<00:19:22.960> for<00:19:23.320> Choice<00:19:24.159> uh 00:19:24.350 --> 00:19:24.360 align:start position:0% absolutely nothing changes for Choice uh 00:19:24.360 --> 00:19:28.830 align:start position:0% absolutely nothing changes for Choice uh my<00:19:24.559> original<00:19:25.039> design<00:19:25.679> used<00:19:26.679> boosts<00:19:27.600> to<00:19:28.159> rely 00:19:28.830 --> 00:19:28.840 align:start position:0% my original design used boosts to rely 00:19:28.840 --> 00:19:32.870 align:start position:0% my original design used boosts to rely on<00:19:29.799> the<00:19:30.120> if<00:19:30.280> the<00:19:30.520> block<00:19:30.840> was<00:19:31.360> poor<00:19:32.120> and<00:19:32.320> the<00:19:32.520> pay 00:19:32.870 --> 00:19:32.880 align:start position:0% on the if the block was poor and the pay 00:19:32.880 --> 00:19:34.950 align:start position:0% on the if the block was poor and the pay the<00:19:33.280> the<00:19:33.400> Builder<00:19:33.799> did<00:19:34.000> not<00:19:34.200> want<00:19:34.360> to<00:19:34.840> uh 00:19:34.950 --> 00:19:34.960 align:start position:0% the the Builder did not want to uh 00:19:34.960 --> 00:19:37.350 align:start position:0% the the Builder did not want to uh reveal<00:19:35.360> the<00:19:35.600> the<00:19:35.720> payload<00:19:36.600> my<00:19:36.799> original<00:19:37.120> for 00:19:37.350 --> 00:19:37.360 align:start position:0% reveal the the payload my original for 00:19:37.360 --> 00:19:40.190 align:start position:0% reveal the the payload my original for Choice<00:19:37.640> design<00:19:38.520> uh<00:19:38.720> relied<00:19:39.120> on<00:19:39.360> the<00:19:39.600> network 00:19:40.190 --> 00:19:40.200 align:start position:0% Choice design uh relied on the network 00:19:40.200 --> 00:19:42.710 align:start position:0% Choice design uh relied on the network reorg<00:19:40.799> the<00:19:40.919> whole<00:19:41.159> thing<00:19:42.159> uh<00:19:42.360> luckily 00:19:42.710 --> 00:19:42.720 align:start position:0% reorg the whole thing uh luckily 00:19:42.720 --> 00:19:44.230 align:start position:0% reorg the whole thing uh luckily Francesco<00:19:43.240> came<00:19:43.360> up<00:19:43.480> with<00:19:43.559> a<00:19:43.720> simplest 00:19:44.230 --> 00:19:44.240 align:start position:0% Francesco came up with a simplest 00:19:44.240 --> 00:19:46.230 align:start position:0% Francesco came up with a simplest solution<00:19:44.720> that<00:19:44.880> doesn't<00:19:45.159> touch<00:19:45.720> for<00:19:46.039> choice 00:19:46.230 --> 00:19:46.240 align:start position:0% solution that doesn't touch for choice 00:19:46.240 --> 00:19:48.750 align:start position:0% solution that doesn't touch for choice at<00:19:46.360> all<00:19:46.640> it's<00:19:46.799> the<00:19:47.039> usual<00:19:47.480> lmg<00:19:48.039> ghost 00:19:48.750 --> 00:19:48.760 align:start position:0% at all it's the usual lmg ghost 00:19:48.760 --> 00:19:51.630 align:start position:0% at all it's the usual lmg ghost mechanism<00:19:49.559> without<00:19:49.840> any<00:19:50.039> boosts<00:19:50.760> so<00:19:51.280> for 00:19:51.630 --> 00:19:51.640 align:start position:0% mechanism without any boosts so for 00:19:51.640 --> 00:19:54.390 align:start position:0% mechanism without any boosts so for choice<00:19:51.919> is<00:19:52.080> not<00:19:52.679> change<00:19:53.000> is<00:19:53.120> not<00:19:53.440> different<00:19:54.080> in 00:19:54.390 --> 00:19:54.400 align:start position:0% choice is not change is not different in 00:19:54.400 --> 00:19:56.390 align:start position:0% choice is not change is not different in the<00:19:54.520> way<00:19:54.679> that<00:19:54.840> we<00:19:55.000> count<00:19:55.320> weights<00:19:55.919> the<00:19:56.080> only 00:19:56.390 --> 00:19:56.400 align:start position:0% the way that we count weights the only 00:19:56.400 --> 00:19:57.870 align:start position:0% the way that we count weights the only difference<00:19:56.760> is<00:19:56.880> in<00:19:57.039> the<00:19:57.200> way<00:19:57.400> that<00:19:57.600> there<00:19:57.720> are 00:19:57.870 --> 00:19:57.880 align:start position:0% difference is in the way that there are 00:19:57.880 --> 00:20:00.390 align:start position:0% difference is in the way that there are nodes<00:19:58.480> that<00:19:58.799> may<00:19:58.960> or<00:19:59.120> may<00:19:59.280> not<00:19:59.480> have<00:19:59.559> a 00:20:00.390 --> 00:20:00.400 align:start position:0% nodes that may or may not have a 00:20:00.400 --> 00:20:02.070 align:start position:0% nodes that may or may not have a payload<00:20:01.400> what<00:20:01.520> do<00:20:01.600> you<00:20:01.720> think<00:20:01.880> about 00:20:02.070 --> 00:20:02.080 align:start position:0% payload what do you think about 00:20:02.080 --> 00:20:03.750 align:start position:0% payload what do you think about implementing<00:20:02.640> consensus<00:20:03.200> execution 00:20:03.750 --> 00:20:03.760 align:start position:0% implementing consensus execution 00:20:03.760 --> 00:20:07.470 align:start position:0% implementing consensus execution separation<00:20:04.320> without<00:20:04.960> epbs<00:20:05.960> uh<00:20:06.320> I<00:20:06.520> so<00:20:07.000> the<00:20:07.320> I 00:20:07.470 --> 00:20:07.480 align:start position:0% separation without epbs uh I so the I 00:20:07.480 --> 00:20:09.830 align:start position:0% separation without epbs uh I so the I think<00:20:07.720> that<00:20:07.880> I<00:20:08.159> the<00:20:08.679> the<00:20:08.840> way<00:20:09.039> I<00:20:09.240> phrase<00:20:09.640> this 00:20:09.830 --> 00:20:09.840 align:start position:0% think that I the the way I phrase this 00:20:09.840 --> 00:20:13.270 align:start position:0% think that I the the way I phrase this talk<00:20:10.799> is<00:20:11.080> that<00:20:12.080> uh<00:20:12.240> there's<00:20:12.440> a<00:20:12.600> big<00:20:12.799> chunk<00:20:13.120> of 00:20:13.270 --> 00:20:13.280 align:start position:0% talk is that uh there's a big chunk of 00:20:13.280 --> 00:20:14.950 align:start position:0% talk is that uh there's a big chunk of changes<00:20:13.720> that<00:20:13.840> are<00:20:14.039> completely<00:20:14.440> independent 00:20:14.950 --> 00:20:14.960 align:start position:0% changes that are completely independent 00:20:14.960 --> 00:20:17.549 align:start position:0% changes that are completely independent of<00:20:15.120> any<00:20:15.320> kind<00:20:15.480> of<00:20:15.640> mechanism<00:20:16.360> for<00:20:16.559> auctioning 00:20:17.549 --> 00:20:17.559 align:start position:0% of any kind of mechanism for auctioning 00:20:17.559 --> 00:20:19.190 align:start position:0% of any kind of mechanism for auctioning and<00:20:17.799> those<00:20:17.960> changes<00:20:18.400> are<00:20:18.640> going<00:20:18.799> to<00:20:18.960> have<00:20:19.080> to 00:20:19.190 --> 00:20:19.200 align:start position:0% and those changes are going to have to 00:20:19.200 --> 00:20:22.909 align:start position:0% and those changes are going to have to be<00:20:19.360> included<00:20:19.840> in<00:20:20.280> any<00:20:21.039> known<00:20:22.039> road<00:20:22.440> map<00:20:22.799> for 00:20:22.909 --> 00:20:22.919 align:start position:0% be included in any known road map for 00:20:22.919 --> 00:20:24.909 align:start position:0% be included in any known road map for ethereum<00:20:23.520> ethereum<00:20:23.960> in<00:20:24.200> all<00:20:24.320> of<00:20:24.480> the<00:20:24.600> known 00:20:24.909 --> 00:20:24.919 align:start position:0% ethereum ethereum in all of the known 00:20:24.919 --> 00:20:26.669 align:start position:0% ethereum ethereum in all of the known road<00:20:25.159> maps<00:20:25.400> for<00:20:25.520> ethereum<00:20:26.159> we<00:20:26.320> have<00:20:26.520> the 00:20:26.669 --> 00:20:26.679 align:start position:0% road maps for ethereum we have the 00:20:26.679 --> 00:20:28.310 align:start position:0% road maps for ethereum we have the separation<00:20:27.080> between<00:20:27.320> payload<00:20:27.640> and<00:20:27.760> block<00:20:28.159> and 00:20:28.310 --> 00:20:28.320 align:start position:0% separation between payload and block and 00:20:28.320 --> 00:20:29.590 align:start position:0% separation between payload and block and that's<00:20:28.440> the<00:20:28.679> heavy<00:20:28.880> lifting<00:20:29.159> that<00:20:29.280> has<00:20:29.440> been 00:20:29.590 --> 00:20:29.600 align:start position:0% that's the heavy lifting that has been 00:20:29.600 --> 00:20:31.230 align:start position:0% that's the heavy lifting that has been done<00:20:30.120> now<00:20:30.240> you<00:20:30.360> need<00:20:30.480> to<00:20:30.600> put<00:20:30.720> on<00:20:30.880> top<00:20:31.000> of<00:20:31.080> this 00:20:31.230 --> 00:20:31.240 align:start position:0% done now you need to put on top of this 00:20:31.240 --> 00:20:33.310 align:start position:0% done now you need to put on top of this an<00:20:31.400> auction<00:20:31.840> just<00:20:31.960> to<00:20:32.440> as<00:20:32.640> an<00:20:32.799> implementation 00:20:33.310 --> 00:20:33.320 align:start position:0% an auction just to as an implementation 00:20:33.320 --> 00:20:35.590 align:start position:0% an auction just to as an implementation detail<00:20:34.080> and<00:20:34.320> the<00:20:34.520> way<00:20:34.760> the<00:20:34.960> reason<00:20:35.320> why<00:20:35.480> we 00:20:35.590 --> 00:20:35.600 align:start position:0% detail and the way the reason why we 00:20:35.600 --> 00:20:38.909 align:start position:0% detail and the way the reason why we chose<00:20:36.200> uh<00:20:36.280> block<00:20:36.640> auctions<00:20:37.520> is<00:20:37.880> because<00:20:38.640> I<00:20:38.760> do 00:20:38.909 --> 00:20:38.919 align:start position:0% chose uh block auctions is because I do 00:20:38.919 --> 00:20:40.710 align:start position:0% chose uh block auctions is because I do not<00:20:39.120> know<00:20:39.360> how<00:20:39.480> to<00:20:39.760> implement<00:20:40.280> any<00:20:40.440> of<00:20:40.600> the 00:20:40.710 --> 00:20:40.720 align:start position:0% not know how to implement any of the 00:20:40.720 --> 00:20:43.190 align:start position:0% not know how to implement any of the other<00:20:40.880> ones<00:20:41.799> and<00:20:42.080> if<00:20:42.200> anyone<00:20:42.520> gives<00:20:42.720> me<00:20:43.080> an 00:20:43.190 --> 00:20:43.200 align:start position:0% other ones and if anyone gives me an 00:20:43.200 --> 00:20:45.070 align:start position:0% other ones and if anyone gives me an actual<00:20:43.520> spec<00:20:43.840> to<00:20:44.039> implement<00:20:44.640> execution 00:20:45.070 --> 00:20:45.080 align:start position:0% actual spec to implement execution 00:20:45.080 --> 00:20:47.950 align:start position:0% actual spec to implement execution tickets<00:20:45.720> or<00:20:45.960> future<00:20:46.400> slots<00:20:47.320> without<00:20:47.640> single 00:20:47.950 --> 00:20:47.960 align:start position:0% tickets or future slots without single 00:20:47.960 --> 00:20:51.029 align:start position:0% tickets or future slots without single slot<00:20:48.280> finality<00:20:48.840> I'll<00:20:49.039> be<00:20:49.280> happy<00:20:49.520> to<00:20:49.960> code<00:20:50.280> it 00:20:51.029 --> 00:20:51.039 align:start position:0% slot finality I'll be happy to code it 00:20:51.039 --> 00:20:53.350 align:start position:0% slot finality I'll be happy to code it but<00:20:52.000> these<00:20:52.120> are<00:20:52.280> the<00:20:52.360> only<00:20:52.640> two<00:20:53.000> that<00:20:53.159> we 00:20:53.350 --> 00:20:53.360 align:start position:0% but these are the only two that we 00:20:53.360 --> 00:20:54.990 align:start position:0% but these are the only two that we actually<00:20:53.600> have<00:20:53.720> a<00:20:53.880> spec<00:20:54.120> and<00:20:54.320> we<00:20:54.440> know<00:20:54.880> that 00:20:54.990 --> 00:20:55.000 align:start position:0% actually have a spec and we know that 00:20:55.000 --> 00:20:58.070 align:start position:0% actually have a spec and we know that it's<00:20:55.200> robust<00:20:56.039> and<00:20:56.600> safe<00:20:57.600> what<00:20:57.720> about<00:20:57.919> the 00:20:58.070 --> 00:20:58.080 align:start position:0% it's robust and safe what about the 00:20:58.080 --> 00:20:59.830 align:start position:0% it's robust and safe what about the impact<00:20:58.360> on<00:20:58.480> the<00:20:58.640> the<00:20:58.720> late<00:20:58.960> block<00:20:59.240> of<00:20:59.400> proposer 00:20:59.830 --> 00:20:59.840 align:start position:0% impact on the the late block of proposer 00:20:59.840 --> 00:21:02.110 align:start position:0% impact on the the late block of proposer boost<00:21:00.640> uh<00:21:00.799> what<00:21:00.960> about<00:21:01.240> the<00:21:01.640> could<00:21:01.760> you<00:21:01.880> repeat 00:21:02.110 --> 00:21:02.120 align:start position:0% boost uh what about the could you repeat 00:21:02.120 --> 00:21:04.430 align:start position:0% boost uh what about the could you repeat that<00:21:02.280> one<00:21:02.840> what<00:21:02.960> about<00:21:03.240> the<00:21:03.440> impact<00:21:04.080> on<00:21:04.280> the 00:21:04.430 --> 00:21:04.440 align:start position:0% that one what about the impact on the 00:21:04.440 --> 00:21:06.909 align:start position:0% that one what about the impact on the late<00:21:04.880> block<00:21:05.240> of<00:21:05.520> proposer 00:21:06.909 --> 00:21:06.919 align:start position:0% late block of proposer 00:21:06.919 --> 00:21:10.390 align:start position:0% late block of proposer boost<00:21:07.919> we<00:21:08.840> I'm<00:21:09.039> not<00:21:09.200> sure<00:21:09.559> if<00:21:09.799> I<00:21:10.240> understand 00:21:10.390 --> 00:21:10.400 align:start position:0% boost we I'm not sure if I understand 00:21:10.400 --> 00:21:14.549 align:start position:0% boost we I'm not sure if I understand the<00:21:10.559> question<00:21:11.039> but<00:21:11.400> uh<00:21:11.880> so<00:21:13.120> perhaps<00:21:14.120> oh<00:21:14.360> okay 00:21:14.549 --> 00:21:14.559 align:start position:0% the question but uh so perhaps oh okay 00:21:14.559 --> 00:21:17.350 align:start position:0% the question but uh so perhaps oh okay so<00:21:15.440> the<00:21:15.720> the<00:21:15.840> question<00:21:16.120> is<00:21:16.360> perhaps<00:21:16.720> that<00:21:16.880> if<00:21:17.000> a 00:21:17.350 --> 00:21:17.360 align:start position:0% so the the question is perhaps that if a 00:21:17.360 --> 00:21:19.430 align:start position:0% so the the question is perhaps that if a block<00:21:17.679> comes<00:21:18.000> late<00:21:18.600> proposer<00:21:19.039> boots<00:21:19.320> can 00:21:19.430 --> 00:21:19.440 align:start position:0% block comes late proposer boots can 00:21:19.440 --> 00:21:21.390 align:start position:0% block comes late proposer boots can reorg<00:21:20.159> yes<00:21:20.440> and<00:21:20.640> this<00:21:20.760> is<00:21:20.919> something<00:21:21.159> that<00:21:21.279> we 00:21:21.390 --> 00:21:21.400 align:start position:0% reorg yes and this is something that we 00:21:21.400 --> 00:21:23.710 align:start position:0% reorg yes and this is something that we do<00:21:21.600> today<00:21:22.159> today<00:21:22.640> in<00:21:22.760> order<00:21:22.960> to<00:21:23.200> not 00:21:23.710 --> 00:21:23.720 align:start position:0% do today today in order to not 00:21:23.720 --> 00:21:25.950 align:start position:0% do today today in order to not incentivize<00:21:24.720> seeing<00:21:25.080> late<00:21:25.320> blocks<00:21:25.720> we 00:21:25.950 --> 00:21:25.960 align:start position:0% incentivize seeing late blocks we 00:21:25.960 --> 00:21:27.789 align:start position:0% incentivize seeing late blocks we actually<00:21:26.279> have<00:21:26.440> seen<00:21:26.679> blocks<00:21:27.240> coming<00:21:27.559> in<00:21:27.679> the 00:21:27.789 --> 00:21:27.799 align:start position:0% actually have seen blocks coming in the 00:21:27.799 --> 00:21:30.149 align:start position:0% actually have seen blocks coming in the early<00:21:28.080> days<00:21:28.600> at<00:21:28.760> 12<00:21:29.080> seconds<00:21:29.440> trying<00:21:29.640> to<00:21:29.799> reorg 00:21:30.149 --> 00:21:30.159 align:start position:0% early days at 12 seconds trying to reorg 00:21:30.159 --> 00:21:31.470 align:start position:0% early days at 12 seconds trying to reorg the<00:21:30.279> next<00:21:30.440> block<00:21:30.799> in<00:21:30.919> order<00:21:31.120> to<00:21:31.279> not 00:21:31.470 --> 00:21:31.480 align:start position:0% the next block in order to not 00:21:31.480 --> 00:21:34.149 align:start position:0% the next block in order to not incentivize<00:21:32.159> this<00:21:32.679> we<00:21:33.080> actually<00:21:33.480> actively 00:21:34.149 --> 00:21:34.159 align:start position:0% incentivize this we actually actively 00:21:34.159 --> 00:21:36.630 align:start position:0% incentivize this we actually actively reorg<00:21:34.720> a<00:21:34.840> block<00:21:35.120> that<00:21:35.279> comes<00:21:35.520> late<00:21:36.240> and<00:21:36.400> that's 00:21:36.630 --> 00:21:36.640 align:start position:0% reorg a block that comes late and that's 00:21:36.640 --> 00:21:38.710 align:start position:0% reorg a block that comes late and that's not<00:21:36.799> going<00:21:36.960> to<00:21:37.120> change<00:21:37.440> here<00:21:38.200> uh<00:21:38.360> the<00:21:38.480> only 00:21:38.710 --> 00:21:38.720 align:start position:0% not going to change here uh the only 00:21:38.720 --> 00:21:40.230 align:start position:0% not going to change here uh the only thing<00:21:38.880> that<00:21:39.000> is<00:21:39.120> going<00:21:39.360> to<00:21:39.520> change<00:21:39.919> is<00:21:40.080> that 00:21:40.230 --> 00:21:40.240 align:start position:0% thing that is going to change is that 00:21:40.240 --> 00:21:43.590 align:start position:0% thing that is going to change is that the<00:21:40.559> Builder<00:21:41.559> uh<00:21:41.919> has<00:21:42.240> a<00:21:42.440> safety<00:21:43.039> mechanism 00:21:43.590 --> 00:21:43.600 align:start position:0% the Builder uh has a safety mechanism 00:21:43.600 --> 00:21:45.310 align:start position:0% the Builder uh has a safety mechanism that<00:21:43.760> if<00:21:43.919> the<00:21:44.039> block<00:21:44.320> came<00:21:44.600> late<00:21:45.039> with<00:21:45.200> a 00:21:45.310 --> 00:21:45.320 align:start position:0% that if the block came late with a 00:21:45.320 --> 00:21:46.990 align:start position:0% that if the block came late with a commitment<00:21:45.720> to<00:21:45.880> its<00:21:46.080> payload<00:21:46.760> then<00:21:46.880> the 00:21:46.990 --> 00:21:47.000 align:start position:0% commitment to its payload then the 00:21:47.000 --> 00:21:48.590 align:start position:0% commitment to its payload then the Builder<00:21:47.320> may<00:21:47.520> not<00:21:47.720> reveal<00:21:48.080> it<00:21:48.279> because<00:21:48.480> he 00:21:48.590 --> 00:21:48.600 align:start position:0% Builder may not reveal it because he 00:21:48.600 --> 00:21:49.830 align:start position:0% Builder may not reveal it because he knows<00:21:48.799> that<00:21:48.919> it's<00:21:49.039> not<00:21:49.200> going<00:21:49.320> to<00:21:49.440> be<00:21:49.520> forced 00:21:49.830 --> 00:21:49.840 align:start position:0% knows that it's not going to be forced 00:21:49.840 --> 00:21:50.590 align:start position:0% knows that it's not going to be forced to 00:21:50.590 --> 00:21:50.600 align:start position:0% to 00:21:50.600 --> 00:21:53.990 align:start position:0% to pay<00:21:51.600> because<00:21:51.799> it<00:21:51.960> has<00:21:52.080> to<00:21:52.159> be<00:21:52.559> reor<00:21:53.559> does<00:21:53.799> this 00:21:53.990 --> 00:21:54.000 align:start position:0% pay because it has to be reor does this 00:21:54.000 --> 00:21:56.470 align:start position:0% pay because it has to be reor does this proposed<00:21:54.360> change<00:21:54.640> require<00:21:55.000> an<00:21:55.240> e<00:21:55.640> spec<00:21:55.960> change 00:21:56.470 --> 00:21:56.480 align:start position:0% proposed change require an e spec change 00:21:56.480 --> 00:21:59.149 align:start position:0% proposed change require an e spec change or<00:21:56.760> an<00:21:56.960> EIP<00:21:57.720> and<00:21:57.919> or<00:21:58.080> does<00:21:58.240> it 00:21:59.149 --> 00:21:59.159 align:start position:0% or an EIP and or does it 00:21:59.159 --> 00:22:01.070 align:start position:0% or an EIP and or does it only<00:21:59.600> require<00:22:00.080> client<00:22:00.679> client 00:22:01.070 --> 00:22:01.080 align:start position:0% only require client client 00:22:01.080 --> 00:22:03.110 align:start position:0% only require client client implementation<00:22:01.880> it<00:22:02.000> is<00:22:02.159> a<00:22:02.400> it<00:22:02.480> is<00:22:02.600> a<00:22:02.720> consensus 00:22:03.110 --> 00:22:03.120 align:start position:0% implementation it is a it is a consensus 00:22:03.120 --> 00:22:05.110 align:start position:0% implementation it is a it is a consensus breaking<00:22:03.559> protocol<00:22:04.120> it's<00:22:04.320> a<00:22:04.520> it's<00:22:04.720> it's<00:22:04.880> not 00:22:05.110 --> 00:22:05.120 align:start position:0% breaking protocol it's a it's it's not 00:22:05.120 --> 00:22:07.029 align:start position:0% breaking protocol it's a it's it's not backwards<00:22:05.520> compatible<00:22:06.120> it's<00:22:06.360> requires<00:22:06.799> any 00:22:07.029 --> 00:22:07.039 align:start position:0% backwards compatible it's requires any 00:22:07.039 --> 00:22:09.230 align:start position:0% backwards compatible it's requires any IP<00:22:07.320> the<00:22:07.480> IP<00:22:07.760> is 00:22:09.230 --> 00:22:09.240 align:start position:0% IP the IP is 00:22:09.240 --> 00:22:11.430 align:start position:0% IP the IP is 7732<00:22:10.240> we<00:22:10.360> have<00:22:10.520> two<00:22:10.679> more<00:22:10.880> minutes<00:22:11.159> so<00:22:11.320> if 00:22:11.430 --> 00:22:11.440 align:start position:0% 7732 we have two more minutes so if 00:22:11.440 --> 00:22:12.789 align:start position:0% 7732 we have two more minutes so if anybody<00:22:11.760> has<00:22:11.880> a<00:22:12.039> Live<00:22:12.320> question<00:22:12.559> that<00:22:12.679> they 00:22:12.789 --> 00:22:12.799 align:start position:0% anybody has a Live question that they 00:22:12.799 --> 00:22:20.230 align:start position:0% anybody has a Live question that they want<00:22:12.919> to 00:22:20.230 --> 00:22:20.240 align:start position:0% 00:22:20.240 --> 00:22:22.909 align:start position:0% ask<00:22:21.240> oh<00:22:21.480> that's<00:22:22.039> uh<00:22:22.279> that<00:22:22.480> that<00:22:22.679> that's<00:22:22.799> a 00:22:22.909 --> 00:22:22.919 align:start position:0% ask oh that's uh that that that's a 00:22:22.919 --> 00:22:24.110 align:start position:0% ask oh that's uh that that that's a great<00:22:23.120> question<00:22:23.520> can<00:22:23.600> you<00:22:23.760> repeat<00:22:24.039> the 00:22:24.110 --> 00:22:24.120 align:start position:0% great question can you repeat the 00:22:24.120 --> 00:22:25.750 align:start position:0% great question can you repeat the question<00:22:24.840> so<00:22:24.960> the<00:22:25.039> question<00:22:25.240> is<00:22:25.400> whether<00:22:25.600> or 00:22:25.750 --> 00:22:25.760 align:start position:0% question so the question is whether or 00:22:25.760 --> 00:22:28.669 align:start position:0% question so the question is whether or not<00:22:25.960> we<00:22:26.080> have<00:22:26.880> we<00:22:27.080> if<00:22:27.200> we've<00:22:27.480> implemented<00:22:28.080> syn 00:22:28.669 --> 00:22:28.679 align:start position:0% not we have we if we've implemented syn 00:22:28.679 --> 00:22:31.310 align:start position:0% not we have we if we've implemented syn no<00:22:29.000> I<00:22:29.159> have<00:22:29.360> not<00:22:30.200> uh<00:22:30.360> purposely<00:22:30.919> because<00:22:31.159> I 00:22:31.310 --> 00:22:31.320 align:start position:0% no I have not uh purposely because I 00:22:31.320 --> 00:22:32.950 align:start position:0% no I have not uh purposely because I really<00:22:31.480> wanted<00:22:31.760> to<00:22:31.919> have<00:22:32.120> the<00:22:32.400> the<00:22:32.600> proof<00:22:32.799> of 00:22:32.950 --> 00:22:32.960 align:start position:0% really wanted to have the the proof of 00:22:32.960 --> 00:22:35.630 align:start position:0% really wanted to have the the proof of concept<00:22:33.279> before<00:22:33.520> Devcon<00:22:34.480> it<00:22:35.039> nothing<00:22:35.400> really 00:22:35.630 --> 00:22:35.640 align:start position:0% concept before Devcon it nothing really 00:22:35.640 --> 00:22:38.669 align:start position:0% concept before Devcon it nothing really changes<00:22:36.159> though<00:22:36.679> because<00:22:36.919> for<00:22:37.159> sync<00:22:37.880> what<00:22:38.080> you 00:22:38.669 --> 00:22:38.679 align:start position:0% changes though because for sync what you 00:22:38.679 --> 00:22:40.870 align:start position:0% changes though because for sync what you you<00:22:38.799> don't<00:22:39.039> you<00:22:39.120> can<00:22:39.799> pck<00:22:40.000> it<00:22:40.320> you<00:22:40.440> can<00:22:40.559> pick<00:22:40.760> it 00:22:40.870 --> 00:22:40.880 align:start position:0% you don't you can pck it you can pick it 00:22:40.880 --> 00:22:42.750 align:start position:0% you don't you can pck it you can pick it back<00:22:41.200> what<00:22:41.320> we<00:22:41.480> already<00:22:41.760> have<00:22:41.919> today<00:22:42.440> so<00:22:42.600> for 00:22:42.750 --> 00:22:42.760 align:start position:0% back what we already have today so for 00:22:42.760 --> 00:22:45.710 align:start position:0% back what we already have today so for sync<00:22:43.039> you're<00:22:43.159> going<00:22:43.240> to<00:22:43.320> send<00:22:43.520> the<00:22:43.600> full<00:22:43.799> block 00:22:45.710 --> 00:22:45.720 align:start position:0% sync you're going to send the full block 00:22:45.720 --> 00:22:50.750 align:start position:0% sync you're going to send the full block together<00:22:46.960> anymore<00:22:48.080> yes<00:22:49.080> are<00:22:49.279> you<00:22:49.760> afraid<00:22:50.320> that 00:22:50.750 --> 00:22:50.760 align:start position:0% together anymore yes are you afraid that 00:22:50.760 --> 00:22:53.510 align:start position:0% together anymore yes are you afraid that given<00:22:51.240> the<00:22:51.919> changes<00:22:52.480> and<00:22:52.720> introduction<00:22:53.240> of 00:22:53.510 --> 00:22:53.520 align:start position:0% given the changes and introduction of 00:22:53.520 --> 00:22:57.590 align:start position:0% given the changes and introduction of new<00:22:54.039> features<00:22:55.039> of<00:22:55.240> the<00:22:55.440> offchain<00:22:56.320> PBS<00:22:57.320> uh 00:22:57.590 --> 00:22:57.600 align:start position:0% new features of the offchain PBS uh 00:22:57.600 --> 00:23:01.149 align:start position:0% new features of the offchain PBS uh pipeline<00:22:58.880> we<00:22:59.120> are<00:22:59.960> soon<00:23:00.360> going<00:23:00.600> to<00:23:00.760> reach<00:23:01.000> a 00:23:01.149 --> 00:23:01.159 align:start position:0% pipeline we are soon going to reach a 00:23:01.159 --> 00:23:04.470 align:start position:0% pipeline we are soon going to reach a point<00:23:01.360> of<00:23:01.520> no<00:23:01.919> return<00:23:02.200> where<00:23:02.480> epbs<00:23:03.200> is<00:23:04.080> pretty 00:23:04.470 --> 00:23:04.480 align:start position:0% point of no return where epbs is pretty 00:23:04.480 --> 00:23:08.630 align:start position:0% point of no return where epbs is pretty hard<00:23:04.760> to<00:23:04.960> even<00:23:05.200> be<00:23:05.880> realized<00:23:06.880> uh<00:23:07.679> I'm<00:23:07.799> not<00:23:08.000> sure 00:23:08.630 --> 00:23:08.640 align:start position:0% hard to even be realized uh I'm not sure 00:23:08.640 --> 00:23:09.789 align:start position:0% hard to even be realized uh I'm not sure I'm<00:23:08.720> not<00:23:08.840> sure<00:23:08.960> I<00:23:09.320> understand<00:23:09.440> the<00:23:09.600> question 00:23:09.789 --> 00:23:09.799 align:start position:0% I'm not sure I understand the question 00:23:09.799 --> 00:23:12.669 align:start position:0% I'm not sure I understand the question I'm<00:23:09.919> sorry<00:23:10.640> for<00:23:10.799> example<00:23:11.240> when<00:23:11.760> PBS<00:23:12.200> started 00:23:12.669 --> 00:23:12.679 align:start position:0% I'm sorry for example when PBS started 00:23:12.679 --> 00:23:15.070 align:start position:0% I'm sorry for example when PBS started we<00:23:12.880> had<00:23:13.039> the<00:23:13.159> relayer<00:23:14.039> just<00:23:14.240> do<00:23:14.480> one<00:23:14.679> thing<00:23:14.919> but 00:23:15.070 --> 00:23:15.080 align:start position:0% we had the relayer just do one thing but 00:23:15.080 --> 00:23:17.269 align:start position:0% we had the relayer just do one thing but then<00:23:15.200> we<00:23:15.360> did<00:23:15.600> stuff<00:23:15.880> like<00:23:16.120> optimistic<00:23:16.679> relays 00:23:17.269 --> 00:23:17.279 align:start position:0% then we did stuff like optimistic relays 00:23:17.279 --> 00:23:19.070 align:start position:0% then we did stuff like optimistic relays recently<00:23:17.720> there<00:23:17.919> have<00:23:18.080> been<00:23:18.360> proposals<00:23:18.880> of 00:23:19.070 --> 00:23:19.080 align:start position:0% recently there have been proposals of 00:23:19.080 --> 00:23:21.070 align:start position:0% recently there have been proposals of stuff<00:23:19.400> like<00:23:19.640> gateways<00:23:20.240> which<00:23:20.440> again<00:23:20.640> relays 00:23:21.070 --> 00:23:21.080 align:start position:0% stuff like gateways which again relays 00:23:21.080 --> 00:23:23.830 align:start position:0% stuff like gateways which again relays do<00:23:21.320> so<00:23:21.960> we<00:23:22.120> keep<00:23:22.400> adding<00:23:22.760> complexity<00:23:23.400> into<00:23:23.640> the 00:23:23.830 --> 00:23:23.840 align:start position:0% do so we keep adding complexity into the 00:23:23.840 --> 00:23:26.990 align:start position:0% do so we keep adding complexity into the offchain<00:23:24.360> PBS<00:23:24.840> stuff<00:23:25.360> that<00:23:25.559> would<00:23:26.080> need<00:23:26.320> to<00:23:26.480> be 00:23:26.990 --> 00:23:27.000 align:start position:0% offchain PBS stuff that would need to be 00:23:27.000 --> 00:23:30.750 align:start position:0% offchain PBS stuff that would need to be matched<00:23:27.640> or<00:23:28.679> very<00:23:29.080> or<00:23:29.240> or<00:23:29.720> improved<00:23:30.360> within 00:23:30.750 --> 00:23:30.760 align:start position:0% matched or very or or improved within 00:23:30.760 --> 00:23:34.110 align:start position:0% matched or very or or improved within epbs<00:23:31.760> do<00:23:31.960> you<00:23:32.600> is<00:23:32.799> this<00:23:33.000> a<00:23:33.480> problem<00:23:33.880> that<00:23:34.000> you 00:23:34.110 --> 00:23:34.120 align:start position:0% epbs do you is this a problem that you 00:23:34.120 --> 00:23:36.310 align:start position:0% epbs do you is this a problem that you see<00:23:34.480> or<00:23:34.640> foresee<00:23:35.159> or<00:23:35.320> is<00:23:35.440> this<00:23:35.559> a<00:23:35.720> viable<00:23:36.080> risk 00:23:36.310 --> 00:23:36.320 align:start position:0% see or foresee or is this a viable risk 00:23:36.320 --> 00:23:38.510 align:start position:0% see or foresee or is this a viable risk for<00:23:36.559> you<00:23:37.000> I<00:23:37.120> I<00:23:37.200> don't<00:23:37.480> I<00:23:37.559> don't<00:23:37.720> see<00:23:38.000> this<00:23:38.279> I<00:23:38.440> I 00:23:38.510 --> 00:23:38.520 align:start position:0% for you I I don't I don't see this I I 00:23:38.520 --> 00:23:39.789 align:start position:0% for you I I don't I don't see this I I can<00:23:38.640> tell<00:23:38.760> you<00:23:38.919> something<00:23:39.200> that<00:23:39.279> I<00:23:39.400> see<00:23:39.559> as<00:23:39.640> a 00:23:39.789 --> 00:23:39.799 align:start position:0% can tell you something that I see as a 00:23:39.799 --> 00:23:41.470 align:start position:0% can tell you something that I see as a risk<00:23:40.400> uh<00:23:40.480> I<00:23:40.559> don't<00:23:40.679> see<00:23:40.919> this<00:23:41.080> particular 00:23:41.470 --> 00:23:41.480 align:start position:0% risk uh I don't see this particular 00:23:41.480 --> 00:23:42.950 align:start position:0% risk uh I don't see this particular thing<00:23:41.640> a<00:23:41.799> risk<00:23:42.039> because<00:23:42.279> complexity<00:23:42.720> on<00:23:42.840> the 00:23:42.950 --> 00:23:42.960 align:start position:0% thing a risk because complexity on the 00:23:42.960 --> 00:23:46.350 align:start position:0% thing a risk because complexity on the relay<00:23:43.960> all<00:23:44.200> that<00:23:44.320> it<00:23:44.720> will<00:23:45.120> CH<00:23:45.400> change<00:23:45.880> what 00:23:46.350 --> 00:23:46.360 align:start position:0% relay all that it will CH change what 00:23:46.360 --> 00:23:48.470 align:start position:0% relay all that it will CH change what epbs<00:23:46.880> the<00:23:47.039> way<00:23:47.159> we<00:23:47.400> proposing<00:23:47.880> is<00:23:48.240> what<00:23:48.360> it 00:23:48.470 --> 00:23:48.480 align:start position:0% epbs the way we proposing is what it 00:23:48.480 --> 00:23:50.350 align:start position:0% epbs the way we proposing is what it does<00:23:48.799> is<00:23:49.000> it<00:23:49.240> allows<00:23:49.559> the<00:23:49.679> Builder<00:23:50.000> to<00:23:50.120> be<00:23:50.240> a 00:23:50.350 --> 00:23:50.360 align:start position:0% does is it allows the Builder to be a 00:23:50.360 --> 00:23:54.269 align:start position:0% does is it allows the Builder to be a relay<00:23:51.080> directly<00:23:52.000> and<00:23:52.640> permissionless<00:23:53.640> so 00:23:54.269 --> 00:23:54.279 align:start position:0% relay directly and permissionless so 00:23:54.279 --> 00:23:56.350 align:start position:0% relay directly and permissionless so what<00:23:54.960> what<00:23:55.080> you're<00:23:55.320> describing<00:23:55.760> to<00:23:55.880> me<00:23:56.039> sounds 00:23:56.350 --> 00:23:56.360 align:start position:0% what what you're describing to me sounds 00:23:56.360 --> 00:23:58.190 align:start position:0% what what you're describing to me sounds like<00:23:56.679> builders<00:23:57.120> in<00:23:57.279> the<00:23:57.440> protocol<00:23:57.880> which<00:23:58.080> they 00:23:58.190 --> 00:23:58.200 align:start position:0% like builders in the protocol which they 00:23:58.200 --> 00:23:59.669 align:start position:0% like builders in the protocol which they are<00:23:58.480> already<00:23:58.720> are<00:23:58.919> because<00:23:59.120> relays<00:23:59.480> are 00:23:59.669 --> 00:23:59.679 align:start position:0% are already are because relays are 00:23:59.679 --> 00:24:01.710 align:start position:0% are already are because relays are Builders<00:24:00.600> uh<00:24:00.799> they<00:24:00.919> will<00:24:01.120> have<00:24:01.240> to<00:24:01.360> have<00:24:01.520> this 00:24:01.710 --> 00:24:01.720 align:start position:0% Builders uh they will have to have this 00:24:01.720 --> 00:24:03.190 align:start position:0% Builders uh they will have to have this complexity<00:24:02.200> if<00:24:02.320> they<00:24:02.440> want<00:24:02.559> to<00:24:02.720> compete<00:24:03.039> be 00:24:03.190 --> 00:24:03.200 align:start position:0% complexity if they want to compete be 00:24:03.200 --> 00:24:05.430 align:start position:0% complexity if they want to compete be competitive<00:24:03.640> in<00:24:03.760> the<00:24:03.840> market<00:24:04.480> but<00:24:04.760> from<00:24:04.919> the 00:24:05.430 --> 00:24:05.440 align:start position:0% competitive in the market but from the 00:24:05.440 --> 00:24:07.269 align:start position:0% competitive in the market but from the protocol<00:24:05.919> perspective<00:24:06.400> we<00:24:06.480> don't<00:24:06.640> care<00:24:07.159> what 00:24:07.269 --> 00:24:07.279 align:start position:0% protocol perspective we don't care what 00:24:07.279 --> 00:24:09.590 align:start position:0% protocol perspective we don't care what I<00:24:07.400> do<00:24:07.559> see<00:24:07.760> as<00:24:07.840> a<00:24:08.000> risk<00:24:08.360> though<00:24:08.760> is<00:24:09.120> other 00:24:09.590 --> 00:24:09.600 align:start position:0% I do see as a risk though is other 00:24:09.600 --> 00:24:11.630 align:start position:0% I do see as a risk though is other things<00:24:09.880> that<00:24:10.000> are<00:24:10.120> being<00:24:10.440> piggy<00:24:10.840> back<00:24:11.039> on<00:24:11.200> PBS 00:24:11.630 --> 00:24:11.640 align:start position:0% things that are being piggy back on PBS 00:24:11.640 --> 00:24:14.630 align:start position:0% things that are being piggy back on PBS say<00:24:11.880> for<00:24:12.080> example<00:24:12.919> uh<00:24:13.039> pre-confirmation<00:24:13.640> uh 00:24:14.630 --> 00:24:14.640 align:start position:0% say for example uh pre-confirmation uh 00:24:14.640 --> 00:24:16.470 align:start position:0% say for example uh pre-confirmation uh and<00:24:14.880> all<00:24:15.000> of<00:24:15.200> these<00:24:15.559> extra<00:24:15.880> markets<00:24:16.279> that<00:24:16.360> are 00:24:16.470 --> 00:24:16.480 align:start position:0% and all of these extra markets that are 00:24:16.480 --> 00:24:19.070 align:start position:0% and all of these extra markets that are being<00:24:16.679> done<00:24:17.120> I<00:24:17.200> would<00:24:17.480> require<00:24:17.840> I<00:24:17.919> would<00:24:18.559> ask 00:24:19.070 --> 00:24:19.080 align:start position:0% being done I would require I would ask 00:24:19.080 --> 00:24:20.909 align:start position:0% being done I would require I would ask for<00:24:19.400> the<00:24:19.600> teams<00:24:20.000> that<00:24:20.120> are<00:24:20.240> working<00:24:20.520> on<00:24:20.679> pre- 00:24:20.909 --> 00:24:20.919 align:start position:0% for the teams that are working on pre- 00:24:20.919 --> 00:24:23.350 align:start position:0% for the teams that are working on pre- comps<00:24:21.400> to<00:24:21.960> make<00:24:22.200> it<00:24:22.480> compatible<00:24:22.960> forward 00:24:23.350 --> 00:24:23.360 align:start position:0% comps to make it compatible forward 00:24:23.360 --> 00:24:26.230 align:start position:0% comps to make it compatible forward looking<00:24:23.679> compatible<00:24:24.320> with<00:24:25.000> mechanisms<00:24:25.480> of 00:24:26.230 --> 00:24:26.240 align:start position:0% looking compatible with mechanisms of 00:24:26.240 --> 00:24:28.870 align:start position:0% looking compatible with mechanisms of separation<00:24:27.240> and<00:24:27.480> if<00:24:27.640> the<00:24:27.799> person<00:24:28.000> who<00:24:28.200> has<00:24:28.679> um 00:24:28.870 --> 00:24:28.880 align:start position:0% separation and if the person who has um 00:24:28.880 --> 00:24:31.190 align:start position:0% separation and if the person who has um answered<00:24:29.240> the<00:24:29.399> multiple<00:24:30.200> current<00:24:30.679> concurrent 00:24:31.190 --> 00:24:31.200 align:start position:0% answered the multiple current concurrent 00:24:31.200 --> 00:24:32.870 align:start position:0% answered the multiple current concurrent proposer<00:24:31.760> question<00:24:32.080> wants<00:24:32.279> to<00:24:32.440> ask<00:24:32.640> him 00:24:32.870 --> 00:24:32.880 align:start position:0% proposer question wants to ask him 00:24:32.880 --> 00:24:34.149 align:start position:0% proposer question wants to ask him afterwards<00:24:33.320> we're<00:24:33.520> out<00:24:33.679> of<00:24:33.840> time<00:24:33.960> for 00:24:34.149 --> 00:24:34.159 align:start position:0% afterwards we're out of time for 00:24:34.159 --> 00:24:35.870 align:start position:0% afterwards we're out of time for questions<00:24:34.799> um<00:24:34.960> but<00:24:35.080> he'll<00:24:35.279> be<00:24:35.440> around<00:24:35.640> in<00:24:35.760> the 00:24:35.870 --> 00:24:35.880 align:start position:0% questions um but he'll be around in the 00:24:35.880 --> 00:24:40.670 align:start position:0% questions um but he'll be around in the room<00:24:36.799> um<00:24:37.080> thank<00:24:37.399> give<00:24:37.520> a<00:24:37.640> hand<00:24:37.799> to<00:24:37.919> pus 00:24:40.670 --> 00:24:40.680 align:start position:0% room um thank give a hand to pus 00:24:40.680 --> 00:24:44.739 align:start position:0% room um thank give a hand to pus [Applause]