WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:08.709 align:start position:0% [Music] 00:00:08.709 --> 00:00:08.719 align:start position:0% 00:00:08.719 --> 00:00:11.350 align:start position:0% hello<00:00:09.160> everyone<00:00:10.160> um<00:00:10.400> today<00:00:10.679> I'm<00:00:10.920> presenting 00:00:11.350 --> 00:00:11.360 align:start position:0% hello everyone um today I'm presenting 00:00:11.360 --> 00:00:13.629 align:start position:0% hello everyone um today I'm presenting fossil<00:00:12.160> which<00:00:12.280> is<00:00:12.400> our<00:00:12.559> inclusionist<00:00:13.240> design 00:00:13.629 --> 00:00:13.639 align:start position:0% fossil which is our inclusionist design 00:00:13.639 --> 00:00:15.589 align:start position:0% fossil which is our inclusionist design that<00:00:13.759> we're<00:00:14.040> proposing<00:00:14.799> to<00:00:14.960> be<00:00:15.120> implemented 00:00:15.589 --> 00:00:15.599 align:start position:0% that we're proposing to be implemented 00:00:15.599 --> 00:00:18.550 align:start position:0% that we're proposing to be implemented into<00:00:15.879> itan<00:00:16.240> Pro<00:00:16.480> schol<00:00:17.000> via<00:00:17.240> Erp 00:00:18.550 --> 00:00:18.560 align:start position:0% into itan Pro schol via Erp 00:00:18.560 --> 00:00:21.910 align:start position:0% into itan Pro schol via Erp 7805<00:00:19.560> so<00:00:19.960> you<00:00:20.080> may<00:00:20.240> have<00:00:20.439> expected<00:00:20.880> tomma<00:00:21.359> here 00:00:21.910 --> 00:00:21.920 align:start position:0% 7805 so you may have expected tomma here 00:00:21.920 --> 00:00:23.269 align:start position:0% 7805 so you may have expected tomma here uh<00:00:22.000> who<00:00:22.119> is<00:00:22.240> the<00:00:22.359> lead<00:00:22.600> on<00:00:22.720> the<00:00:22.840> fossil 00:00:23.269 --> 00:00:23.279 align:start position:0% uh who is the lead on the fossil 00:00:23.279 --> 00:00:24.589 align:start position:0% uh who is the lead on the fossil projects<00:00:23.640> but<00:00:23.760> unfortunately<00:00:24.199> he<00:00:24.320> couldn't 00:00:24.589 --> 00:00:24.599 align:start position:0% projects but unfortunately he couldn't 00:00:24.599 --> 00:00:26.790 align:start position:0% projects but unfortunately he couldn't make<00:00:24.800> it<00:00:25.320> so<00:00:25.599> I'm<00:00:25.720> Jillian<00:00:26.279> I'm<00:00:26.439> one<00:00:26.560> of<00:00:26.679> his 00:00:26.790 --> 00:00:26.800 align:start position:0% make it so I'm Jillian I'm one of his 00:00:26.800 --> 00:00:28.429 align:start position:0% make it so I'm Jillian I'm one of his teammates<00:00:27.240> at<00:00:27.320> the<00:00:27.439> robust<00:00:27.720> incenters<00:00:28.199> group 00:00:28.429 --> 00:00:28.439 align:start position:0% teammates at the robust incenters group 00:00:28.439 --> 00:00:30.390 align:start position:0% teammates at the robust incenters group at<00:00:28.519> the<00:00:28.599> etherum<00:00:28.960> foundation<00:00:29.800> and<00:00:30.119> and<00:00:30.199> I'll 00:00:30.390 --> 00:00:30.400 align:start position:0% at the etherum foundation and and I'll 00:00:30.400 --> 00:00:32.190 align:start position:0% at the etherum foundation and and I'll presenting<00:00:30.920> be<00:00:31.119> presenting<00:00:31.439> our<00:00:31.599> joint<00:00:31.880> work 00:00:32.190 --> 00:00:32.200 align:start position:0% presenting be presenting our joint work 00:00:32.200 --> 00:00:35.030 align:start position:0% presenting be presenting our joint work with<00:00:32.399> to<00:00:32.759> as<00:00:32.880> the<00:00:33.000> lead<00:00:33.440> Franchesco<00:00:34.320> me<00:00:34.680> barnab 00:00:35.030 --> 00:00:35.040 align:start position:0% with to as the lead Franchesco me barnab 00:00:35.040 --> 00:00:39.029 align:start position:0% with to as the lead Franchesco me barnab Bay<00:00:35.480> Terren<00:00:35.920> who<00:00:36.000> is<00:00:36.160> here<00:00:36.280> as<00:00:36.399> well<00:00:37.000> Jacob<00:00:37.559> and 00:00:39.029 --> 00:00:39.039 align:start position:0% Bay Terren who is here as well Jacob and 00:00:39.039 --> 00:00:42.029 align:start position:0% Bay Terren who is here as well Jacob and Jun<00:00:40.039> so<00:00:40.520> first<00:00:40.680> of<00:00:40.800> all<00:00:41.000> I'll<00:00:41.440> give<00:00:41.559> a<00:00:41.680> bit<00:00:41.840> of<00:00:41.960> a 00:00:42.029 --> 00:00:42.039 align:start position:0% Jun so first of all I'll give a bit of a 00:00:42.039 --> 00:00:43.310 align:start position:0% Jun so first of all I'll give a bit of a high<00:00:42.200> level<00:00:42.440> introduction<00:00:42.840> to<00:00:43.000> what<00:00:43.120> are 00:00:43.310 --> 00:00:43.320 align:start position:0% high level introduction to what are 00:00:43.320 --> 00:00:44.790 align:start position:0% high level introduction to what are inclusion<00:00:43.760> lists<00:00:44.039> and<00:00:44.160> what<00:00:44.280> are<00:00:44.399> we<00:00:44.600> actually 00:00:44.790 --> 00:00:44.800 align:start position:0% inclusion lists and what are we actually 00:00:44.800 --> 00:00:46.389 align:start position:0% inclusion lists and what are we actually trying<00:00:45.039> to<00:00:45.200> achieve<00:00:45.559> here<00:00:46.160> so<00:00:46.320> the 00:00:46.389 --> 00:00:46.399 align:start position:0% trying to achieve here so the 00:00:46.399 --> 00:00:48.549 align:start position:0% trying to achieve here so the inclusionist<00:00:47.000> design<00:00:47.360> philosophy<00:00:47.879> is<00:00:48.079> that 00:00:48.549 --> 00:00:48.559 align:start position:0% inclusionist design philosophy is that 00:00:48.559 --> 00:00:50.350 align:start position:0% inclusionist design philosophy is that ethereum<00:00:49.039> has<00:00:49.239> access<00:00:49.520> to<00:00:49.800> centralized 00:00:50.350 --> 00:00:50.360 align:start position:0% ethereum has access to centralized 00:00:50.360 --> 00:00:52.750 align:start position:0% ethereum has access to centralized agents<00:00:50.840> and<00:00:51.000> decentralized<00:00:51.760> agents<00:00:52.480> and<00:00:52.600> we 00:00:52.750 --> 00:00:52.760 align:start position:0% agents and decentralized agents and we 00:00:52.760 --> 00:00:54.430 align:start position:0% agents and decentralized agents and we want<00:00:52.920> the<00:00:53.120> decentralized<00:00:53.760> agents<00:00:54.120> to<00:00:54.280> have 00:00:54.430 --> 00:00:54.440 align:start position:0% want the decentralized agents to have 00:00:54.440 --> 00:00:56.270 align:start position:0% want the decentralized agents to have some<00:00:54.719> inputs<00:00:55.120> into<00:00:55.359> centralized<00:00:55.800> blood 00:00:56.270 --> 00:00:56.280 align:start position:0% some inputs into centralized blood 00:00:56.280 --> 00:00:58.549 align:start position:0% some inputs into centralized blood construction<00:00:57.280> so<00:00:57.680> inclusion<00:00:58.079> list<00:00:58.359> really 00:00:58.549 --> 00:00:58.559 align:start position:0% construction so inclusion list really 00:00:58.559 --> 00:01:00.389 align:start position:0% construction so inclusion list really Leverage<00:00:59.039> The<00:00:59.160> decentralization<00:01:00.120> in<00:01:00.239> the 00:01:00.389 --> 00:01:00.399 align:start position:0% Leverage The decentralization in the 00:01:00.399 --> 00:01:02.150 align:start position:0% Leverage The decentralization in the validator<00:01:00.960> set<00:01:01.280> that<00:01:01.399> we've<00:01:01.559> gten<00:01:01.960> from 00:01:02.150 --> 00:01:02.160 align:start position:0% validator set that we've gten from 00:01:02.160 --> 00:01:04.229 align:start position:0% validator set that we've gten from proposer<00:01:02.519> Builder<00:01:02.879> separation<00:01:03.760> and<00:01:03.879> it's<00:01:04.040> the 00:01:04.229 --> 00:01:04.239 align:start position:0% proposer Builder separation and it's the 00:01:04.239 --> 00:01:07.590 align:start position:0% proposer Builder separation and it's the first<00:01:04.680> design<00:01:05.000> of<00:01:05.159> its<00:01:05.360> kind<00:01:05.960> uh<00:01:06.040> to<00:01:06.240> do<00:01:06.439> so<00:01:07.439> uh 00:01:07.590 --> 00:01:07.600 align:start position:0% first design of its kind uh to do so uh 00:01:07.600 --> 00:01:10.710 align:start position:0% first design of its kind uh to do so uh and<00:01:08.600> having<00:01:08.880> inclusion<00:01:09.320> list<00:01:09.520> is<00:01:10.159> necessary 00:01:10.710 --> 00:01:10.720 align:start position:0% and having inclusion list is necessary 00:01:10.720 --> 00:01:12.830 align:start position:0% and having inclusion list is necessary to<00:01:10.920> obtain<00:01:11.880> uh<00:01:12.040> the<00:01:12.159> core<00:01:12.400> property<00:01:12.720> of 00:01:12.830 --> 00:01:12.840 align:start position:0% to obtain uh the core property of 00:01:12.840 --> 00:01:14.390 align:start position:0% to obtain uh the core property of ethereum<00:01:13.280> which<00:01:13.360> is<00:01:13.479> to<00:01:13.640> provide<00:01:14.040> CH 00:01:14.390 --> 00:01:14.400 align:start position:0% ethereum which is to provide CH 00:01:14.400 --> 00:01:17.190 align:start position:0% ethereum which is to provide CH neutrality<00:01:15.400> CH<00:01:15.640> neutrality<00:01:16.200> we<00:01:16.360> Define<00:01:16.799> here 00:01:17.190 --> 00:01:17.200 align:start position:0% neutrality CH neutrality we Define here 00:01:17.200 --> 00:01:19.590 align:start position:0% neutrality CH neutrality we Define here as<00:01:17.759> any<00:01:18.080> valid<00:01:18.360> and<00:01:18.560> pending<00:01:18.960> transaction 00:01:19.590 --> 00:01:19.600 align:start position:0% as any valid and pending transaction 00:01:19.600 --> 00:01:21.429 align:start position:0% as any valid and pending transaction that<00:01:19.759> pays<00:01:20.000> the<00:01:20.159> pervading<00:01:20.560> base<00:01:20.840> fee<00:01:21.280> is 00:01:21.429 --> 00:01:21.439 align:start position:0% that pays the pervading base fee is 00:01:21.439 --> 00:01:23.069 align:start position:0% that pays the pervading base fee is included<00:01:21.880> within<00:01:22.119> the<00:01:22.200> block<00:01:22.600> unless<00:01:22.840> there's 00:01:23.069 --> 00:01:23.079 align:start position:0% included within the block unless there's 00:01:23.079 --> 00:01:24.630 align:start position:0% included within the block unless there's no<00:01:23.240> space 00:01:24.630 --> 00:01:24.640 align:start position:0% no space 00:01:24.640 --> 00:01:27.030 align:start position:0% no space anymore<00:01:25.640> so<00:01:25.799> the<00:01:25.960> basic<00:01:26.280> idea<00:01:26.520> of<00:01:26.640> inclusion 00:01:27.030 --> 00:01:27.040 align:start position:0% anymore so the basic idea of inclusion 00:01:27.040 --> 00:01:28.469 align:start position:0% anymore so the basic idea of inclusion list<00:01:27.360> is<00:01:27.479> that<00:01:27.600> there<00:01:27.680> are<00:01:27.840> some<00:01:28.079> lists<00:01:28.320> of 00:01:28.469 --> 00:01:28.479 align:start position:0% list is that there are some lists of 00:01:28.479 --> 00:01:30.510 align:start position:0% list is that there are some lists of transactions<00:01:29.079> that<00:01:29.280> constrains<00:01:30.040> how<00:01:30.159> a<00:01:30.280> block 00:01:30.510 --> 00:01:30.520 align:start position:0% transactions that constrains how a block 00:01:30.520 --> 00:01:32.510 align:start position:0% transactions that constrains how a block is<00:01:30.680> created<00:01:31.479> and<00:01:31.640> usually<00:01:31.960> you<00:01:32.040> would<00:01:32.240> say 00:01:32.510 --> 00:01:32.520 align:start position:0% is created and usually you would say 00:01:32.520 --> 00:01:34.230 align:start position:0% is created and usually you would say that<00:01:32.720> this<00:01:32.880> list<00:01:33.079> of<00:01:33.240> transactions<00:01:33.880> must<00:01:34.079> be 00:01:34.230 --> 00:01:34.240 align:start position:0% that this list of transactions must be 00:01:34.240 --> 00:01:36.830 align:start position:0% that this list of transactions must be included<00:01:34.640> in<00:01:34.759> the<00:01:34.880> Block<00:01:35.119> in<00:01:35.280> some<00:01:35.520> way<00:01:36.280> fosil 00:01:36.830 --> 00:01:36.840 align:start position:0% included in the Block in some way fosil 00:01:36.840 --> 00:01:39.030 align:start position:0% included in the Block in some way fosil doesn't<00:01:37.119> change<00:01:37.520> this<00:01:37.759> basic<00:01:38.280> idea<00:01:38.680> it's<00:01:38.840> more 00:01:39.030 --> 00:01:39.040 align:start position:0% doesn't change this basic idea it's more 00:01:39.040 --> 00:01:40.870 align:start position:0% doesn't change this basic idea it's more about<00:01:39.360> who<00:01:39.600> creates<00:01:39.960> the<00:01:40.159> list<00:01:40.520> and<00:01:40.680> how<00:01:40.799> is 00:01:40.870 --> 00:01:40.880 align:start position:0% about who creates the list and how is 00:01:40.880 --> 00:01:43.030 align:start position:0% about who creates the list and how is the<00:01:41.040> list 00:01:43.030 --> 00:01:43.040 align:start position:0% the list 00:01:43.040 --> 00:01:46.429 align:start position:0% the list enforced<00:01:44.040> so<00:01:44.320> what<00:01:44.439> is<00:01:44.640> fosil<00:01:45.439> fosil<00:01:45.920> is<00:01:46.079> forth 00:01:46.429 --> 00:01:46.439 align:start position:0% enforced so what is fosil fosil is forth 00:01:46.439 --> 00:01:48.389 align:start position:0% enforced so what is fosil fosil is forth Choice<00:01:46.759> enforced<00:01:47.240> inclusion<00:01:47.719> list<00:01:48.159> so<00:01:48.320> the 00:01:48.389 --> 00:01:48.399 align:start position:0% Choice enforced inclusion list so the 00:01:48.399 --> 00:01:50.069 align:start position:0% Choice enforced inclusion list so the four<00:01:48.680> Choice<00:01:49.000> enforced<00:01:49.399> part<00:01:49.600> says<00:01:49.840> something 00:01:50.069 --> 00:01:50.079 align:start position:0% four Choice enforced part says something 00:01:50.079 --> 00:01:53.230 align:start position:0% four Choice enforced part says something about<00:01:50.280> how<00:01:50.439> it's<00:01:50.759> enforced<00:01:51.759> uh<00:01:51.880> and<00:01:52.079> F<00:01:52.439> allows 00:01:53.230 --> 00:01:53.240 align:start position:0% about how it's enforced uh and F allows 00:01:53.240 --> 00:01:55.069 align:start position:0% about how it's enforced uh and F allows multiple<00:01:53.640> validators<00:01:54.280> to<00:01:54.439> provide<00:01:54.719> inputs 00:01:55.069 --> 00:01:55.079 align:start position:0% multiple validators to provide inputs 00:01:55.079 --> 00:01:56.950 align:start position:0% multiple validators to provide inputs into<00:01:55.320> block<00:01:55.560> construction<00:01:56.360> achieving<00:01:56.799> this 00:01:56.950 --> 00:01:56.960 align:start position:0% into block construction achieving this 00:01:56.960 --> 00:01:59.149 align:start position:0% into block construction achieving this core<00:01:57.240> property<00:01:57.799> of<00:01:58.439> uh<00:01:58.560> increasing<00:01:59.000> the 00:01:59.149 --> 00:01:59.159 align:start position:0% core property of uh increasing the 00:01:59.159 --> 00:02:00.789 align:start position:0% core property of uh increasing the credible<00:01:59.439> neutrality<00:02:00.200> so<00:02:00.399> here<00:02:00.520> you<00:02:00.640> can 00:02:00.789 --> 00:02:00.799 align:start position:0% credible neutrality so here you can 00:02:00.799 --> 00:02:02.749 align:start position:0% credible neutrality so here you can think<00:02:01.000> about<00:02:01.240> censorship<00:02:01.759> resistance 00:02:02.749 --> 00:02:02.759 align:start position:0% think about censorship resistance 00:02:02.759 --> 00:02:04.670 align:start position:0% think about censorship resistance whether<00:02:03.039> this<00:02:03.159> is<00:02:03.399> for<00:02:04.079> transactions<00:02:04.600> that 00:02:04.670 --> 00:02:04.680 align:start position:0% whether this is for transactions that 00:02:04.680 --> 00:02:06.350 align:start position:0% whether this is for transactions that are<00:02:04.840> being<00:02:05.039> censored<00:02:05.479> because<00:02:05.640> of<00:02:05.799> regulatory 00:02:06.350 --> 00:02:06.360 align:start position:0% are being censored because of regulatory 00:02:06.360 --> 00:02:08.710 align:start position:0% are being censored because of regulatory reasons<00:02:06.920> for<00:02:07.159> economic<00:02:07.600> reasons<00:02:08.200> or<00:02:08.520> by 00:02:08.710 --> 00:02:08.720 align:start position:0% reasons for economic reasons or by 00:02:08.720 --> 00:02:11.430 align:start position:0% reasons for economic reasons or by chance<00:02:09.520> uh<00:02:09.640> as<00:02:09.840> happens<00:02:10.160> today<00:02:11.160> and<00:02:11.280> then 00:02:11.430 --> 00:02:11.440 align:start position:0% chance uh as happens today and then 00:02:11.440 --> 00:02:12.830 align:start position:0% chance uh as happens today and then there<00:02:11.520> are<00:02:11.680> some<00:02:11.840> other<00:02:12.040> design<00:02:12.400> goals<00:02:12.760> which 00:02:12.830 --> 00:02:12.840 align:start position:0% there are some other design goals which 00:02:12.840 --> 00:02:14.750 align:start position:0% there are some other design goals which is<00:02:13.040> robustness<00:02:13.640> of<00:02:13.760> the<00:02:13.920> system<00:02:14.480> we<00:02:14.599> want 00:02:14.750 --> 00:02:14.760 align:start position:0% is robustness of the system we want 00:02:14.760 --> 00:02:16.470 align:start position:0% is robustness of the system we want fossil<00:02:15.200> to<00:02:15.319> be<00:02:15.440> used<00:02:15.720> and<00:02:15.879> we<00:02:16.000> want<00:02:16.120> it<00:02:16.200> to<00:02:16.319> be 00:02:16.470 --> 00:02:16.480 align:start position:0% fossil to be used and we want it to be 00:02:16.480 --> 00:02:19.390 align:start position:0% fossil to be used and we want it to be only<00:02:16.800> used<00:02:17.280> to<00:02:17.519> provide<00:02:18.080> these<00:02:18.879> um<00:02:19.239> this 00:02:19.390 --> 00:02:19.400 align:start position:0% only used to provide these um this 00:02:19.400 --> 00:02:22.270 align:start position:0% only used to provide these um this increase<00:02:19.720> incedible<00:02:20.480> neutrality<00:02:21.480> and<00:02:22.160> uh 00:02:22.270 --> 00:02:22.280 align:start position:0% increase incedible neutrality and uh 00:02:22.280 --> 00:02:24.350 align:start position:0% increase incedible neutrality and uh another<00:02:22.560> design<00:02:22.840> goal<00:02:23.040> is<00:02:23.160> extendability<00:02:23.560> so 00:02:24.350 --> 00:02:24.360 align:start position:0% another design goal is extendability so 00:02:24.360 --> 00:02:27.270 align:start position:0% another design goal is extendability so we<00:02:24.480> want<00:02:24.680> fil<00:02:25.080> to<00:02:25.160> be<00:02:25.319> very<00:02:25.480> future<00:02:26.280> compatible 00:02:27.270 --> 00:02:27.280 align:start position:0% we want fil to be very future compatible 00:02:27.280 --> 00:02:29.430 align:start position:0% we want fil to be very future compatible um<00:02:27.519> yet<00:02:27.680> we<00:02:27.800> need<00:02:27.959> inclusionist<00:02:28.599> today<00:02:29.000> since 00:02:29.430 --> 00:02:29.440 align:start position:0% um yet we need inclusionist today since 00:02:29.440 --> 00:02:31.990 align:start position:0% um yet we need inclusionist today since block<00:02:29.879> struction<00:02:30.160> is<00:02:30.280> so<00:02:30.440> centralized<00:02:31.400> so<00:02:31.560> fil 00:02:31.990 --> 00:02:32.000 align:start position:0% block struction is so centralized so fil 00:02:32.000 --> 00:02:33.869 align:start position:0% block struction is so centralized so fil is<00:02:32.080> a<00:02:32.200> recurring<00:02:32.599> architecture<00:02:33.200> that<00:02:33.319> we<00:02:33.480> see 00:02:33.869 --> 00:02:33.879 align:start position:0% is a recurring architecture that we see 00:02:33.879 --> 00:02:35.270 align:start position:0% is a recurring architecture that we see in<00:02:34.080> multiple<00:02:34.480> designs<00:02:34.840> that<00:02:34.959> we're 00:02:35.270 --> 00:02:35.280 align:start position:0% in multiple designs that we're 00:02:35.280 --> 00:02:38.630 align:start position:0% in multiple designs that we're considering<00:02:35.840> for<00:02:36.560> other<00:02:37.560> um<00:02:37.760> use<00:02:38.120> cases<00:02:38.480> like 00:02:38.630 --> 00:02:38.640 align:start position:0% considering for other um use cases like 00:02:38.640 --> 00:02:41.630 align:start position:0% considering for other um use cases like pias<00:02:39.280> or<00:02:39.480> other<00:02:39.760> economic 00:02:41.630 --> 00:02:41.640 align:start position:0% pias or other economic 00:02:41.640 --> 00:02:44.990 align:start position:0% pias or other economic benefits<00:02:42.640> so<00:02:42.840> now<00:02:43.000> I'll<00:02:43.200> go<00:02:43.360> over<00:02:43.840> on<00:02:44.000> a<00:02:44.760> more 00:02:44.990 --> 00:02:45.000 align:start position:0% benefits so now I'll go over on a more 00:02:45.000 --> 00:02:46.910 align:start position:0% benefits so now I'll go over on a more specific<00:02:45.400> level<00:02:45.640> of<00:02:45.760> how<00:02:46.120> foso<00:02:46.640> actually 00:02:46.910 --> 00:02:46.920 align:start position:0% specific level of how foso actually 00:02:46.920 --> 00:02:48.309 align:start position:0% specific level of how foso actually works<00:02:47.200> and<00:02:47.319> how<00:02:47.440> these<00:02:47.599> inclusion<00:02:47.959> list<00:02:48.159> are 00:02:48.309 --> 00:02:48.319 align:start position:0% works and how these inclusion list are 00:02:48.319 --> 00:02:50.630 align:start position:0% works and how these inclusion list are created<00:02:48.920> distributed<00:02:49.599> and<00:02:49.800> enforced<00:02:50.519> and 00:02:50.630 --> 00:02:50.640 align:start position:0% created distributed and enforced and 00:02:50.640 --> 00:02:53.309 align:start position:0% created distributed and enforced and later<00:02:50.840> we'll<00:02:51.000> do<00:02:51.080> a<00:02:51.159> bit<00:02:51.319> of<00:02:51.400> a<00:02:51.519> recap<00:02:51.959> again<00:02:52.840> so 00:02:53.309 --> 00:02:53.319 align:start position:0% later we'll do a bit of a recap again so 00:02:53.319 --> 00:02:55.670 align:start position:0% later we'll do a bit of a recap again so I<00:02:53.400> said<00:02:53.640> that<00:02:53.959> F<00:02:54.319> allows<00:02:54.599> multiple<00:02:55.000> validators 00:02:55.670 --> 00:02:55.680 align:start position:0% I said that F allows multiple validators 00:02:55.680 --> 00:02:56.990 align:start position:0% I said that F allows multiple validators to<00:02:55.879> provide<00:02:56.120> some<00:02:56.280> inputs<00:02:56.560> into<00:02:56.760> block 00:02:56.990 --> 00:02:57.000 align:start position:0% to provide some inputs into block 00:02:57.000 --> 00:02:59.270 align:start position:0% to provide some inputs into block Construction<00:02:57.879> in<00:02:58.040> this<00:02:58.200> EIP<00:02:58.760> specifically 00:02:59.270 --> 00:02:59.280 align:start position:0% Construction in this EIP specifically 00:02:59.280 --> 00:03:00.470 align:start position:0% Construction in this EIP specifically we're<00:02:59.440> saying<00:02:59.680> that<00:02:59.879> There<00:02:59.959> are<00:03:00.080> 16 00:03:00.470 --> 00:03:00.480 align:start position:0% we're saying that There are 16 00:03:00.480 --> 00:03:02.190 align:start position:0% we're saying that There are 16 validators<00:03:01.080> that<00:03:01.159> are<00:03:01.319> randomly<00:03:01.720> selected 00:03:02.190 --> 00:03:02.200 align:start position:0% validators that are randomly selected 00:03:02.200 --> 00:03:03.710 align:start position:0% validators that are randomly selected every<00:03:02.400> slot<00:03:02.720> to<00:03:02.840> become<00:03:03.080> inclusion<00:03:03.519> list 00:03:03.710 --> 00:03:03.720 align:start position:0% every slot to become inclusion list 00:03:03.720 --> 00:03:06.110 align:start position:0% every slot to become inclusion list committee<00:03:04.280> members<00:03:05.280> uh<00:03:05.400> and<00:03:05.560> what<00:03:05.680> these 00:03:06.110 --> 00:03:06.120 align:start position:0% committee members uh and what these 00:03:06.120 --> 00:03:07.509 align:start position:0% committee members uh and what these committee<00:03:06.440> members<00:03:06.760> do<00:03:06.959> is<00:03:07.120> they<00:03:07.280> each 00:03:07.509 --> 00:03:07.519 align:start position:0% committee members do is they each 00:03:07.519 --> 00:03:09.789 align:start position:0% committee members do is they each propose<00:03:08.400> uh<00:03:08.519> a<00:03:08.640> single<00:03:08.920> inclusion<00:03:09.319> list<00:03:09.519> by 00:03:09.789 --> 00:03:09.799 align:start position:0% propose uh a single inclusion list by 00:03:09.799 --> 00:03:10.990 align:start position:0% propose uh a single inclusion list by themselves<00:03:10.239> and<00:03:10.360> these<00:03:10.440> are<00:03:10.599> then<00:03:10.720> later 00:03:10.990 --> 00:03:11.000 align:start position:0% themselves and these are then later 00:03:11.000 --> 00:03:13.910 align:start position:0% themselves and these are then later aggregated<00:03:11.560> into<00:03:12.159> one<00:03:12.519> complete<00:03:12.879> one<00:03:13.680> so 00:03:13.910 --> 00:03:13.920 align:start position:0% aggregated into one complete one so 00:03:13.920 --> 00:03:15.789 align:start position:0% aggregated into one complete one so committee<00:03:14.280> members<00:03:14.599> they<00:03:14.760> observe<00:03:15.120> the<00:03:15.239> mol 00:03:15.789 --> 00:03:15.799 align:start position:0% committee members they observe the mol 00:03:15.799 --> 00:03:17.309 align:start position:0% committee members they observe the mol and<00:03:15.959> see<00:03:16.280> transactions<00:03:16.720> in<00:03:16.879> whatever<00:03:17.200> way 00:03:17.309 --> 00:03:17.319 align:start position:0% and see transactions in whatever way 00:03:17.319 --> 00:03:18.589 align:start position:0% and see transactions in whatever way that<00:03:17.440> they<00:03:17.560> see<00:03:17.760> them<00:03:17.959> and<00:03:18.080> they<00:03:18.239> construct 00:03:18.589 --> 00:03:18.599 align:start position:0% that they see them and they construct 00:03:18.599 --> 00:03:20.509 align:start position:0% that they see them and they construct their<00:03:18.720> local<00:03:19.000> inclusion<00:03:19.440> list<00:03:20.080> which<00:03:20.200> is<00:03:20.319> a 00:03:20.509 --> 00:03:20.519 align:start position:0% their local inclusion list which is a 00:03:20.519 --> 00:03:23.270 align:start position:0% their local inclusion list which is a list<00:03:20.879> of<00:03:21.040> transactions<00:03:21.680> that<00:03:21.799> they<00:03:21.959> sign<00:03:22.280> over 00:03:23.270 --> 00:03:23.280 align:start position:0% list of transactions that they sign over 00:03:23.280 --> 00:03:25.270 align:start position:0% list of transactions that they sign over uh<00:03:23.400> which<00:03:23.519> is<00:03:23.640> then<00:03:23.959> distributed<00:03:24.959> and<00:03:25.120> each 00:03:25.270 --> 00:03:25.280 align:start position:0% uh which is then distributed and each 00:03:25.280 --> 00:03:27.750 align:start position:0% uh which is then distributed and each inclusion<00:03:25.799> list<00:03:26.080> is<00:03:26.239> at<00:03:26.400> most<00:03:26.680> 8<00:03:27.000> kilobytes 00:03:27.750 --> 00:03:27.760 align:start position:0% inclusion list is at most 8 kilobytes 00:03:27.760 --> 00:03:29.550 align:start position:0% inclusion list is at most 8 kilobytes which<00:03:27.840> should<00:03:28.040> be<00:03:28.159> around<00:03:28.720> 20<00:03:29.080> transactions 00:03:29.550 --> 00:03:29.560 align:start position:0% which should be around 20 transactions 00:03:29.560 --> 00:03:33.470 align:start position:0% which should be around 20 transactions on<00:03:29.840> average<00:03:30.720> uh<00:03:30.799> so<00:03:31.000> 20<00:03:31.400> *<00:03:31.760> 16<00:03:32.200> gives<00:03:32.360> you<00:03:32.560> 320 00:03:33.470 --> 00:03:33.480 align:start position:0% on average uh so 20 * 16 gives you 320 00:03:33.480 --> 00:03:35.550 align:start position:0% on average uh so 20 * 16 gives you 320 average<00:03:33.840> transactions<00:03:34.840> over<00:03:35.120> all<00:03:35.319> of<00:03:35.439> the 00:03:35.550 --> 00:03:35.560 align:start position:0% average transactions over all of the 00:03:35.560 --> 00:03:38.190 align:start position:0% average transactions over all of the fossil<00:03:35.959> inclusion<00:03:36.360> lists<00:03:37.239> uh<00:03:37.400> and<00:03:37.640> a<00:03:37.799> block<00:03:38.040> on 00:03:38.190 --> 00:03:38.200 align:start position:0% fossil inclusion lists uh and a block on 00:03:38.200 --> 00:03:40.350 align:start position:0% fossil inclusion lists uh and a block on average<00:03:38.519> has<00:03:38.680> about<00:03:39.080> 200<00:03:39.319> transactions<00:03:40.040> so<00:03:40.200> we 00:03:40.350 --> 00:03:40.360 align:start position:0% average has about 200 transactions so we 00:03:40.360 --> 00:03:42.869 align:start position:0% average has about 200 transactions so we allow<00:03:41.200> uh<00:03:41.319> fossil<00:03:41.760> to<00:03:41.959> be<00:03:42.200> used<00:03:42.480> as<00:03:42.599> like<00:03:42.760> a 00:03:42.869 --> 00:03:42.879 align:start position:0% allow uh fossil to be used as like a 00:03:42.879 --> 00:03:44.910 align:start position:0% allow uh fossil to be used as like a block<00:03:43.159> template<00:03:43.799> all<00:03:44.280> transactions<00:03:44.760> in 00:03:44.910 --> 00:03:44.920 align:start position:0% block template all transactions in 00:03:44.920 --> 00:03:48.509 align:start position:0% block template all transactions in principle<00:03:45.319> could<00:03:45.480> be<00:03:45.560> included<00:03:46.000> via<00:03:46.519> foso<00:03:47.519> um 00:03:48.509 --> 00:03:48.519 align:start position:0% principle could be included via foso um 00:03:48.519 --> 00:03:50.509 align:start position:0% principle could be included via foso um with<00:03:48.720> some<00:03:48.959> extra<00:03:49.360> overlap<00:03:49.920> because<00:03:50.200> these 00:03:50.509 --> 00:03:50.519 align:start position:0% with some extra overlap because these 00:03:50.519 --> 00:03:52.190 align:start position:0% with some extra overlap because these agents<00:03:50.959> might<00:03:51.239> the<00:03:51.400> inclusion<00:03:51.760> of<00:03:51.879> committee 00:03:52.190 --> 00:03:52.200 align:start position:0% agents might the inclusion of committee 00:03:52.200 --> 00:03:54.110 align:start position:0% agents might the inclusion of committee members<00:03:52.519> might<00:03:52.680> not<00:03:52.840> be<00:03:53.120> coordinated<00:03:53.760> agents 00:03:54.110 --> 00:03:54.120 align:start position:0% members might not be coordinated agents 00:03:54.120 --> 00:03:56.550 align:start position:0% members might not be coordinated agents so<00:03:54.280> they<00:03:54.400> may<00:03:54.560> choose<00:03:54.879> similar<00:03:55.560> transactions 00:03:56.550 --> 00:03:56.560 align:start position:0% so they may choose similar transactions 00:03:56.560 --> 00:03:58.710 align:start position:0% so they may choose similar transactions um<00:03:56.680> so<00:03:56.840> there<00:03:56.959> needs<00:03:57.120> to<00:03:57.200> be<00:03:57.319> some 00:03:58.710 --> 00:03:58.720 align:start position:0% um so there needs to be some 00:03:58.720 --> 00:04:01.630 align:start position:0% um so there needs to be some overlap<00:03:59.760> so<00:03:59.920> now<00:04:00.040> that<00:04:00.280> these<00:04:01.000> agents<00:04:01.400> make 00:04:01.630 --> 00:04:01.640 align:start position:0% overlap so now that these agents make 00:04:01.640 --> 00:04:03.229 align:start position:0% overlap so now that these agents make their<00:04:01.760> own<00:04:02.000> inclusion<00:04:02.400> list<00:04:02.720> these<00:04:02.879> inclusion 00:04:03.229 --> 00:04:03.239 align:start position:0% their own inclusion list these inclusion 00:04:03.239 --> 00:04:04.910 align:start position:0% their own inclusion list these inclusion List<00:04:03.439> have<00:04:03.560> to<00:04:03.680> be<00:04:03.840> created<00:04:04.360> and<00:04:04.480> they<00:04:04.599> need<00:04:04.720> to 00:04:04.910 --> 00:04:04.920 align:start position:0% List have to be created and they need to 00:04:04.920 --> 00:04:07.069 align:start position:0% List have to be created and they need to go<00:04:05.079> to<00:04:05.360> the<00:04:05.560> proposer<00:04:06.159> who<00:04:06.319> needs<00:04:06.519> to<00:04:06.680> include 00:04:07.069 --> 00:04:07.079 align:start position:0% go to the proposer who needs to include 00:04:07.079 --> 00:04:08.949 align:start position:0% go to the proposer who needs to include them<00:04:07.480> and<00:04:07.640> the<00:04:07.799> testers<00:04:08.239> who<00:04:08.439> enforce<00:04:08.799> them 00:04:08.949 --> 00:04:08.959 align:start position:0% them and the testers who enforce them 00:04:08.959 --> 00:04:10.910 align:start position:0% them and the testers who enforce them via<00:04:09.120> the<00:04:09.200> fork<00:04:09.480> choice<00:04:10.239> so<00:04:10.400> first<00:04:10.560> we'll<00:04:10.760> look 00:04:10.910 --> 00:04:10.920 align:start position:0% via the fork choice so first we'll look 00:04:10.920 --> 00:04:12.110 align:start position:0% via the fork choice so first we'll look at<00:04:11.040> how<00:04:11.200> these<00:04:11.360> inclusion<00:04:11.760> lists<00:04:11.959> are 00:04:12.110 --> 00:04:12.120 align:start position:0% at how these inclusion lists are 00:04:12.120 --> 00:04:14.789 align:start position:0% at how these inclusion lists are distributed<00:04:12.640> to<00:04:12.879> the<00:04:13.239> proposer<00:04:14.239> each<00:04:14.480> I 00:04:14.789 --> 00:04:14.799 align:start position:0% distributed to the proposer each I 00:04:14.799 --> 00:04:17.030 align:start position:0% distributed to the proposer each I Committee<00:04:15.159> Member<00:04:15.920> distributes<00:04:16.519> their<00:04:16.919> uh 00:04:17.030 --> 00:04:17.040 align:start position:0% Committee Member distributes their uh 00:04:17.040 --> 00:04:18.749 align:start position:0% Committee Member distributes their uh inclusion<00:04:17.440> list<00:04:17.600> over<00:04:17.759> the<00:04:17.880> global<00:04:18.239> topic 00:04:18.749 --> 00:04:18.759 align:start position:0% inclusion list over the global topic 00:04:18.759 --> 00:04:20.430 align:start position:0% inclusion list over the global topic this<00:04:18.880> is<00:04:19.079> the<00:04:19.320> the<00:04:19.440> peer-to-peer<00:04:19.840> part<00:04:20.199> of<00:04:20.320> the 00:04:20.430 --> 00:04:20.440 align:start position:0% this is the the peer-to-peer part of the 00:04:20.440 --> 00:04:23.590 align:start position:0% this is the the peer-to-peer part of the network<00:04:20.840> where<00:04:21.320> all<00:04:21.600> participant<00:04:22.120> listen<00:04:22.600> to 00:04:23.590 --> 00:04:23.600 align:start position:0% network where all participant listen to 00:04:23.600 --> 00:04:25.629 align:start position:0% network where all participant listen to uh<00:04:23.880> ATT<00:04:24.040> testers<00:04:24.600> who<00:04:24.759> enforce<00:04:25.120> the<00:04:25.240> inclusion 00:04:25.629 --> 00:04:25.639 align:start position:0% uh ATT testers who enforce the inclusion 00:04:25.639 --> 00:04:27.830 align:start position:0% uh ATT testers who enforce the inclusion list<00:04:26.000> which<00:04:26.120> we'll<00:04:26.280> see<00:04:26.400> in<00:04:26.520> a<00:04:26.639> bit<00:04:27.360> uh<00:04:27.479> freeze 00:04:27.830 --> 00:04:27.840 align:start position:0% list which we'll see in a bit uh freeze 00:04:27.840 --> 00:04:29.350 align:start position:0% list which we'll see in a bit uh freeze their<00:04:28.040> view<00:04:28.400> of<00:04:28.560> the<00:04:28.720> available<00:04:29.039> loal 00:04:29.350 --> 00:04:29.360 align:start position:0% their view of the available loal 00:04:29.360 --> 00:04:31.909 align:start position:0% their view of the available loal inclusion<00:04:29.840> list<00:04:30.120> at<00:04:30.280> second<00:04:30.639> n<00:04:31.440> so<00:04:31.639> what<00:04:31.759> they 00:04:31.909 --> 00:04:31.919 align:start position:0% inclusion list at second n so what they 00:04:31.919 --> 00:04:34.150 align:start position:0% inclusion list at second n so what they do<00:04:32.199> is<00:04:32.720> all<00:04:33.080> inclusion<00:04:33.520> list<00:04:33.759> that<00:04:33.880> they<00:04:34.039> had 00:04:34.150 --> 00:04:34.160 align:start position:0% do is all inclusion list that they had 00:04:34.160 --> 00:04:36.670 align:start position:0% do is all inclusion list that they had seen<00:04:34.520> before<00:04:34.840> second<00:04:35.199> n<00:04:36.080> uh<00:04:36.240> they<00:04:36.400> will 00:04:36.670 --> 00:04:36.680 align:start position:0% seen before second n uh they will 00:04:36.680 --> 00:04:39.270 align:start position:0% seen before second n uh they will enforce<00:04:37.520> and<00:04:38.120> inclusion<00:04:38.520> list<00:04:38.720> that<00:04:38.880> come<00:04:39.039> in 00:04:39.270 --> 00:04:39.280 align:start position:0% enforce and inclusion list that come in 00:04:39.280 --> 00:04:42.189 align:start position:0% enforce and inclusion list that come in later<00:04:40.160> uh<00:04:40.280> they<00:04:40.400> do<00:04:40.560> not<00:04:40.800> enforce<00:04:41.800> but<00:04:42.080> they 00:04:42.189 --> 00:04:42.199 align:start position:0% later uh they do not enforce but they 00:04:42.199 --> 00:04:44.189 align:start position:0% later uh they do not enforce but they still<00:04:42.520> propagate<00:04:43.000> them<00:04:43.120> to<00:04:43.360> the<00:04:43.680> to<00:04:43.840> the<00:04:43.960> block 00:04:44.189 --> 00:04:44.199 align:start position:0% still propagate them to the to the block 00:04:44.199 --> 00:04:46.270 align:start position:0% still propagate them to the to the block producer<00:04:45.080> and<00:04:45.199> this<00:04:45.320> is<00:04:45.479> essential<00:04:46.039> because 00:04:46.270 --> 00:04:46.280 align:start position:0% producer and this is essential because 00:04:46.280 --> 00:04:47.990 align:start position:0% producer and this is essential because this<00:04:46.479> time<00:04:46.680> reference<00:04:47.120> is<00:04:47.320> there<00:04:47.479> to<00:04:47.680> prevent 00:04:47.990 --> 00:04:48.000 align:start position:0% this time reference is there to prevent 00:04:48.000 --> 00:04:50.150 align:start position:0% this time reference is there to prevent split<00:04:48.320> view<00:04:48.600> attacks<00:04:49.280> a<00:04:49.400> split<00:04:49.680> view<00:04:49.919> attack 00:04:50.150 --> 00:04:50.160 align:start position:0% split view attacks a split view attack 00:04:50.160 --> 00:04:51.510 align:start position:0% split view attacks a split view attack is<00:04:50.280> when<00:04:50.440> an<00:04:50.560> inclusion<00:04:51.000> list<00:04:51.160> Committee 00:04:51.510 --> 00:04:51.520 align:start position:0% is when an inclusion list Committee 00:04:51.520 --> 00:04:53.710 align:start position:0% is when an inclusion list Committee Member<00:04:51.759> is<00:04:51.880> trying<00:04:52.120> to<00:04:52.240> split<00:04:52.560> the<00:04:52.680> view<00:04:53.479> of 00:04:53.710 --> 00:04:53.720 align:start position:0% Member is trying to split the view of 00:04:53.720 --> 00:04:55.790 align:start position:0% Member is trying to split the view of the<00:04:53.840> block<00:04:54.160> producer<00:04:54.800> and<00:04:54.960> the<00:04:55.120> attester<00:04:55.639> so 00:04:55.790 --> 00:04:55.800 align:start position:0% the block producer and the attester so 00:04:55.800 --> 00:04:57.430 align:start position:0% the block producer and the attester so the<00:04:55.960> person<00:04:56.160> who<00:04:56.320> has<00:04:56.440> to<00:04:56.560> act<00:04:56.800> on<00:04:57.000> it<00:04:57.240> and 00:04:57.430 --> 00:04:57.440 align:start position:0% the person who has to act on it and 00:04:57.440 --> 00:04:59.430 align:start position:0% the person who has to act on it and those<00:04:57.600> who<00:04:57.759> has<00:04:57.919> to<00:04:58.120> enforce<00:04:58.560> it<00:04:59.160> you<00:04:59.280> could 00:04:59.430 --> 00:04:59.440 align:start position:0% those who has to enforce it you could 00:04:59.440 --> 00:05:01.350 align:start position:0% those who has to enforce it you could imag<00:05:00.000> that<00:05:00.160> if<00:05:00.280> the<00:05:00.440> testers<00:05:00.919> think<00:05:01.240> that 00:05:01.350 --> 00:05:01.360 align:start position:0% imag that if the testers think that 00:05:01.360 --> 00:05:02.870 align:start position:0% imag that if the testers think that there<00:05:01.479> are<00:05:01.639> more<00:05:01.880> inclusion<00:05:02.280> lists<00:05:02.520> than<00:05:02.680> the 00:05:02.870 --> 00:05:02.880 align:start position:0% there are more inclusion lists than the 00:05:02.880 --> 00:05:05.909 align:start position:0% there are more inclusion lists than the proposer<00:05:03.720> then<00:05:03.880> the<00:05:04.039> proposer<00:05:04.840> can't<00:05:05.560> adhere 00:05:05.909 --> 00:05:05.919 align:start position:0% proposer then the proposer can't adhere 00:05:05.919 --> 00:05:07.189 align:start position:0% proposer then the proposer can't adhere to<00:05:06.039> the<00:05:06.120> rules<00:05:06.360> of<00:05:06.479> the<00:05:06.560> inclusion<00:05:06.960> list 00:05:07.189 --> 00:05:07.199 align:start position:0% to the rules of the inclusion list 00:05:07.199 --> 00:05:08.390 align:start position:0% to the rules of the inclusion list because<00:05:07.360> simply<00:05:07.720> doesn't<00:05:07.960> know<00:05:08.160> what's 00:05:08.390 --> 00:05:08.400 align:start position:0% because simply doesn't know what's 00:05:08.400 --> 00:05:10.629 align:start position:0% because simply doesn't know what's available<00:05:09.400> so<00:05:09.560> we<00:05:09.680> give<00:05:09.840> the<00:05:09.919> block<00:05:10.160> producer 00:05:10.629 --> 00:05:10.639 align:start position:0% available so we give the block producer 00:05:10.639 --> 00:05:13.310 align:start position:0% available so we give the block producer three<00:05:10.800> more<00:05:11.120> seconds<00:05:11.479> to<00:05:11.680> act<00:05:11.919> on<00:05:12.080> it<00:05:13.039> uh<00:05:13.160> to 00:05:13.310 --> 00:05:13.320 align:start position:0% three more seconds to act on it uh to 00:05:13.320 --> 00:05:15.270 align:start position:0% three more seconds to act on it uh to prevent<00:05:13.600> the<00:05:13.759> split<00:05:14.039> view<00:05:14.600> so<00:05:14.800> if<00:05:14.919> the<00:05:15.039> block 00:05:15.270 --> 00:05:15.280 align:start position:0% prevent the split view so if the block 00:05:15.280 --> 00:05:17.629 align:start position:0% prevent the split view so if the block producer<00:05:15.680> doesn't<00:05:16.080> have<00:05:16.840> uh<00:05:17.039> inclusion<00:05:17.440> list 00:05:17.629 --> 00:05:17.639 align:start position:0% producer doesn't have uh inclusion list 00:05:17.639 --> 00:05:19.309 align:start position:0% producer doesn't have uh inclusion list at<00:05:17.720> second<00:05:18.039> 9<00:05:18.319> the<00:05:18.440> attestor<00:05:18.960> can<00:05:19.080> still 00:05:19.309 --> 00:05:19.319 align:start position:0% at second 9 the attestor can still 00:05:19.319 --> 00:05:21.029 align:start position:0% at second 9 the attestor can still propagate<00:05:19.720> it<00:05:19.840> to<00:05:19.960> the<00:05:20.039> block 00:05:21.029 --> 00:05:21.039 align:start position:0% propagate it to the block 00:05:21.039 --> 00:05:23.070 align:start position:0% propagate it to the block producer<00:05:22.039> the<00:05:22.160> block<00:05:22.440> also<00:05:22.639> doesn't<00:05:22.880> have<00:05:22.960> to 00:05:23.070 --> 00:05:23.080 align:start position:0% producer the block also doesn't have to 00:05:23.080 --> 00:05:24.710 align:start position:0% producer the block also doesn't have to be<00:05:23.240> entirely<00:05:23.680> rebuilt<00:05:24.160> inclusionist 00:05:24.710 --> 00:05:24.720 align:start position:0% be entirely rebuilt inclusionist 00:05:24.720 --> 00:05:26.230 align:start position:0% be entirely rebuilt inclusionist transactions<00:05:25.199> can<00:05:25.319> be<00:05:25.479> appended<00:05:25.960> to<00:05:26.120> the 00:05:26.230 --> 00:05:26.240 align:start position:0% transactions can be appended to the 00:05:26.240 --> 00:05:28.950 align:start position:0% transactions can be appended to the block<00:05:26.960> uh<00:05:27.080> meaning<00:05:27.440> that<00:05:27.919> it<00:05:28.039> can<00:05:28.160> be<00:05:28.360> fairly 00:05:28.950 --> 00:05:28.960 align:start position:0% block uh meaning that it can be fairly 00:05:28.960 --> 00:05:31.469 align:start position:0% block uh meaning that it can be fairly done<00:05:29.199> fairly<00:05:29.440> quickly 00:05:31.469 --> 00:05:31.479 align:start position:0% done fairly quickly 00:05:31.479 --> 00:05:33.390 align:start position:0% done fairly quickly so<00:05:31.680> then<00:05:31.800> on<00:05:31.960> to<00:05:32.160> enforcement<00:05:32.840> so<00:05:33.000> I've<00:05:33.120> hinted 00:05:33.390 --> 00:05:33.400 align:start position:0% so then on to enforcement so I've hinted 00:05:33.400 --> 00:05:35.189 align:start position:0% so then on to enforcement so I've hinted at<00:05:33.520> this<00:05:33.680> already<00:05:34.120> a<00:05:34.240> bit<00:05:34.720> and<00:05:34.840> it's<00:05:34.960> in<00:05:35.039> the 00:05:35.189 --> 00:05:35.199 align:start position:0% at this already a bit and it's in the 00:05:35.199 --> 00:05:36.950 align:start position:0% at this already a bit and it's in the name<00:05:35.440> of<00:05:35.600> course<00:05:35.960> enforced<00:05:36.400> via<00:05:36.600> the<00:05:36.680> fork 00:05:36.950 --> 00:05:36.960 align:start position:0% name of course enforced via the fork 00:05:36.960 --> 00:05:40.150 align:start position:0% name of course enforced via the fork Choice<00:05:37.960> um<00:05:38.560> the<00:05:38.720> testers<00:05:39.240> enforce<00:05:39.960> whether 00:05:40.150 --> 00:05:40.160 align:start position:0% Choice um the testers enforce whether 00:05:40.160 --> 00:05:42.230 align:start position:0% Choice um the testers enforce whether the<00:05:40.319> proposer<00:05:40.800> did<00:05:40.960> indeed<00:05:41.319> adhere<00:05:41.759> to<00:05:42.120> the 00:05:42.230 --> 00:05:42.240 align:start position:0% the proposer did indeed adhere to the 00:05:42.240 --> 00:05:43.909 align:start position:0% the proposer did indeed adhere to the inclusion<00:05:42.680> list<00:05:43.039> conditions<00:05:43.319> that<00:05:43.400> were 00:05:43.909 --> 00:05:43.919 align:start position:0% inclusion list conditions that were 00:05:43.919 --> 00:05:46.629 align:start position:0% inclusion list conditions that were specified<00:05:44.919> so<00:05:45.520> uh<00:05:45.680> the<00:05:45.759> testers<00:05:46.199> only<00:05:46.360> vote 00:05:46.629 --> 00:05:46.639 align:start position:0% specified so uh the testers only vote 00:05:46.639 --> 00:05:48.189 align:start position:0% specified so uh the testers only vote for<00:05:46.800> the<00:05:46.880> block<00:05:47.280> if<00:05:47.400> the<00:05:47.520> inclusion<00:05:47.919> lists 00:05:48.189 --> 00:05:48.199 align:start position:0% for the block if the inclusion lists 00:05:48.199 --> 00:05:50.150 align:start position:0% for the block if the inclusion lists were<00:05:48.400> indeed<00:05:48.800> adhered<00:05:49.479> and<00:05:49.639> how<00:05:49.759> it<00:05:49.840> works 00:05:50.150 --> 00:05:50.160 align:start position:0% were indeed adhered and how it works 00:05:50.160 --> 00:05:52.029 align:start position:0% were indeed adhered and how it works specifically<00:05:50.759> is<00:05:50.919> the<00:05:51.039> testers<00:05:51.720> have<00:05:51.880> been 00:05:52.029 --> 00:05:52.039 align:start position:0% specifically is the testers have been 00:05:52.039 --> 00:05:54.029 align:start position:0% specifically is the testers have been listening<00:05:52.400> to<00:05:52.520> the<00:05:52.680> global<00:05:53.039> topic<00:05:53.759> where<00:05:53.919> the 00:05:54.029 --> 00:05:54.039 align:start position:0% listening to the global topic where the 00:05:54.039 --> 00:05:56.110 align:start position:0% listening to the global topic where the inclusionist<00:05:54.680> have<00:05:54.800> been<00:05:55.000> propagated<00:05:56.000> and 00:05:56.110 --> 00:05:56.120 align:start position:0% inclusionist have been propagated and 00:05:56.120 --> 00:05:58.110 align:start position:0% inclusionist have been propagated and they<00:05:56.240> freeze<00:05:56.560> their<00:05:56.759> View<00:05:56.960> at<00:05:57.120> second<00:05:57.440> n<00:05:58.000> of 00:05:58.110 --> 00:05:58.120 align:start position:0% they freeze their View at second n of 00:05:58.120 --> 00:05:59.309 align:start position:0% they freeze their View at second n of the<00:05:58.240> inclusionist<00:05:58.800> that<00:05:58.880> they're<00:05:59.039> going<00:05:59.160> to 00:05:59.309 --> 00:05:59.319 align:start position:0% the inclusionist that they're going to 00:05:59.319 --> 00:06:01.590 align:start position:0% the inclusionist that they're going to enforce<00:05:59.639> first<00:06:00.560> uh<00:06:00.680> and<00:06:00.840> they<00:06:01.000> take<00:06:01.199> the<00:06:01.319> union 00:06:01.590 --> 00:06:01.600 align:start position:0% enforce first uh and they take the union 00:06:01.600 --> 00:06:03.150 align:start position:0% enforce first uh and they take the union of<00:06:01.759> all<00:06:01.960> transactions<00:06:02.479> that<00:06:02.600> they<00:06:02.759> had<00:06:02.880> seen 00:06:03.150 --> 00:06:03.160 align:start position:0% of all transactions that they had seen 00:06:03.160 --> 00:06:04.950 align:start position:0% of all transactions that they had seen in<00:06:03.280> these<00:06:03.479> inclusion<00:06:03.919> lists<00:06:04.479> and<00:06:04.600> check 00:06:04.950 --> 00:06:04.960 align:start position:0% in these inclusion lists and check 00:06:04.960 --> 00:06:06.710 align:start position:0% in these inclusion lists and check whether<00:06:05.520> any<00:06:05.680> of<00:06:05.840> these<00:06:06.000> transactions<00:06:06.520> was 00:06:06.710 --> 00:06:06.720 align:start position:0% whether any of these transactions was 00:06:06.720 --> 00:06:08.510 align:start position:0% whether any of these transactions was not<00:06:06.960> included<00:06:07.360> in<00:06:07.440> the<00:06:07.639> execution<00:06:08.080> payload 00:06:08.510 --> 00:06:08.520 align:start position:0% not included in the execution payload 00:06:08.520 --> 00:06:10.830 align:start position:0% not included in the execution payload that<00:06:09.400> that<00:06:09.560> they<00:06:09.919> received<00:06:10.280> so<00:06:10.440> they<00:06:10.560> checked 00:06:10.830 --> 00:06:10.840 align:start position:0% that that they received so they checked 00:06:10.840 --> 00:06:12.309 align:start position:0% that that they received so they checked whether<00:06:11.000> a<00:06:11.120> transaction<00:06:11.639> from<00:06:11.759> the<00:06:11.880> inclusion 00:06:12.309 --> 00:06:12.319 align:start position:0% whether a transaction from the inclusion 00:06:12.319 --> 00:06:15.070 align:start position:0% whether a transaction from the inclusion list<00:06:12.639> was<00:06:12.840> not<00:06:13.000> in<00:06:13.120> the<00:06:13.400> block<00:06:14.400> if<00:06:14.599> this<00:06:14.720> is<00:06:14.919> the 00:06:15.070 --> 00:06:15.080 align:start position:0% list was not in the block if this is the 00:06:15.080 --> 00:06:16.870 align:start position:0% list was not in the block if this is the case<00:06:15.400> they<00:06:15.599> check<00:06:15.800> if<00:06:15.919> the<00:06:16.000> block<00:06:16.240> is<00:06:16.360> full<00:06:16.720> or 00:06:16.870 --> 00:06:16.880 align:start position:0% case they check if the block is full or 00:06:16.880 --> 00:06:18.430 align:start position:0% case they check if the block is full or not<00:06:17.280> so<00:06:17.479> if<00:06:17.599> the<00:06:17.720> block<00:06:17.919> is<00:06:18.000> full<00:06:18.280> then 00:06:18.430 --> 00:06:18.440 align:start position:0% not so if the block is full then 00:06:18.440 --> 00:06:19.589 align:start position:0% not so if the block is full then obviously<00:06:18.800> you<00:06:18.919> can't<00:06:19.160> include<00:06:19.479> the 00:06:19.589 --> 00:06:19.599 align:start position:0% obviously you can't include the 00:06:19.599 --> 00:06:22.749 align:start position:0% obviously you can't include the transactions<00:06:20.160> anymore<00:06:20.720> so<00:06:21.720> um<00:06:22.199> if<00:06:22.400> if<00:06:22.520> the 00:06:22.749 --> 00:06:22.759 align:start position:0% transactions anymore so um if if the 00:06:22.759 --> 00:06:25.629 align:start position:0% transactions anymore so um if if the tester<00:06:23.080> is<00:06:23.240> happy<00:06:23.599> so<00:06:23.800> the<00:06:24.000> block<00:06:25.000> um<00:06:25.240> contains 00:06:25.629 --> 00:06:25.639 align:start position:0% tester is happy so the block um contains 00:06:25.639 --> 00:06:27.189 align:start position:0% tester is happy so the block um contains all<00:06:25.880> the<00:06:26.000> transactions<00:06:26.560> or<00:06:26.759> the<00:06:26.840> block<00:06:27.080> is 00:06:27.189 --> 00:06:27.199 align:start position:0% all the transactions or the block is 00:06:27.199 --> 00:06:29.350 align:start position:0% all the transactions or the block is full<00:06:28.199> and<00:06:28.319> then<00:06:28.440> the<00:06:28.560> attester<00:06:28.960> vote<00:06:29.199> for<00:06:29.280> the 00:06:29.350 --> 00:06:29.360 align:start position:0% full and then the attester vote for the 00:06:29.360 --> 00:06:30.189 align:start position:0% full and then the attester vote for the block 00:06:30.189 --> 00:06:30.199 align:start position:0% block 00:06:30.199 --> 00:06:32.029 align:start position:0% block if<00:06:30.440> the<00:06:30.599> tester<00:06:30.960> is<00:06:31.120> unhappy<00:06:31.599> so<00:06:31.759> the 00:06:32.029 --> 00:06:32.039 align:start position:0% if the tester is unhappy so the 00:06:32.039 --> 00:06:34.469 align:start position:0% if the tester is unhappy so the inclusionist<00:06:33.039> U<00:06:33.240> has<00:06:33.400> more<00:06:33.599> transactions<00:06:34.240> and 00:06:34.469 --> 00:06:34.479 align:start position:0% inclusionist U has more transactions and 00:06:34.479 --> 00:06:36.430 align:start position:0% inclusionist U has more transactions and the<00:06:34.759> the<00:06:35.240> the<00:06:35.360> execution<00:06:35.720> payload<00:06:36.039> misses<00:06:36.280> a 00:06:36.430 --> 00:06:36.440 align:start position:0% the the the execution payload misses a 00:06:36.440 --> 00:06:38.390 align:start position:0% the the the execution payload misses a view<00:06:37.080> then<00:06:37.199> the<00:06:37.319> test<00:06:37.680> does<00:06:37.840> not<00:06:37.960> vote<00:06:38.160> for<00:06:38.319> the 00:06:38.390 --> 00:06:38.400 align:start position:0% view then the test does not vote for the 00:06:38.400 --> 00:06:40.430 align:start position:0% view then the test does not vote for the block<00:06:38.840> so<00:06:39.479> the<00:06:39.720> the<00:06:39.840> property<00:06:40.160> that<00:06:40.280> we're 00:06:40.430 --> 00:06:40.440 align:start position:0% block so the the property that we're 00:06:40.440 --> 00:06:42.589 align:start position:0% block so the the property that we're getting<00:06:40.680> at<00:06:40.960> here<00:06:41.160> is<00:06:41.639> if<00:06:41.840> the<00:06:41.960> block<00:06:42.199> producer 00:06:42.589 --> 00:06:42.599 align:start position:0% getting at here is if the block producer 00:06:42.599 --> 00:06:44.150 align:start position:0% getting at here is if the block producer does<00:06:42.759> not<00:06:42.960> adhere<00:06:43.280> to<00:06:43.400> the<00:06:43.479> inclusion<00:06:43.880> list 00:06:44.150 --> 00:06:44.160 align:start position:0% does not adhere to the inclusion list 00:06:44.160 --> 00:06:45.670 align:start position:0% does not adhere to the inclusion list its<00:06:44.280> block<00:06:44.520> will<00:06:44.639> not<00:06:44.800> become<00:06:45.080> canonical 00:06:45.670 --> 00:06:45.680 align:start position:0% its block will not become canonical 00:06:45.680 --> 00:06:47.589 align:start position:0% its block will not become canonical because<00:06:45.840> in<00:06:46.000> testers<00:06:46.400> enforce 00:06:47.589 --> 00:06:47.599 align:start position:0% because in testers enforce 00:06:47.599 --> 00:06:50.950 align:start position:0% because in testers enforce it<00:06:48.599> so<00:06:48.759> this<00:06:48.880> is<00:06:49.039> the<00:06:49.160> full<00:06:49.440> fil<00:06:49.840> mechanism<00:06:50.840> we 00:06:50.950 --> 00:06:50.960 align:start position:0% it so this is the full fil mechanism we 00:06:50.960 --> 00:06:53.550 align:start position:0% it so this is the full fil mechanism we have<00:06:51.120> 16<00:06:51.599> validators<00:06:52.199> randomly<00:06:52.599> chosen<00:06:53.360> that 00:06:53.550 --> 00:06:53.560 align:start position:0% have 16 validators randomly chosen that 00:06:53.560 --> 00:06:55.710 align:start position:0% have 16 validators randomly chosen that make<00:06:53.800> inclusion<00:06:54.199> list<00:06:54.599> they<00:06:54.759> propagate<00:06:55.280> them 00:06:55.710 --> 00:06:55.720 align:start position:0% make inclusion list they propagate them 00:06:55.720 --> 00:06:57.430 align:start position:0% make inclusion list they propagate them the<00:06:55.800> block<00:06:56.080> producer<00:06:56.599> receives<00:06:56.840> them<00:06:57.280> it 00:06:57.430 --> 00:06:57.440 align:start position:0% the block producer receives them it 00:06:57.440 --> 00:06:59.830 align:start position:0% the block producer receives them it includes<00:06:57.840> all<00:06:58.039> transactions<00:06:58.639> in<00:06:58.759> its<00:06:58.960> block 00:06:59.830 --> 00:06:59.840 align:start position:0% includes all transactions in its block 00:06:59.840 --> 00:07:02.070 align:start position:0% includes all transactions in its block and<00:07:00.000> the<00:07:00.160> testers<00:07:01.120> uh<00:07:01.319> then<00:07:01.479> enforced<00:07:01.960> that 00:07:02.070 --> 00:07:02.080 align:start position:0% and the testers uh then enforced that 00:07:02.080 --> 00:07:04.830 align:start position:0% and the testers uh then enforced that the<00:07:02.160> block<00:07:02.400> producer<00:07:02.800> did<00:07:02.960> in<00:07:03.120> fact<00:07:03.360> do 00:07:04.830 --> 00:07:04.840 align:start position:0% the block producer did in fact do 00:07:04.840 --> 00:07:07.830 align:start position:0% the block producer did in fact do this<00:07:05.840> so<00:07:06.000> the<00:07:06.120> core<00:07:06.560> property<00:07:07.560> that<00:07:07.680> we're 00:07:07.830 --> 00:07:07.840 align:start position:0% this so the core property that we're 00:07:07.840 --> 00:07:09.510 align:start position:0% this so the core property that we're trying<00:07:08.000> to<00:07:08.160> get<00:07:08.319> at<00:07:08.560> here<00:07:08.800> is<00:07:08.919> the<00:07:09.080> censorship 00:07:09.510 --> 00:07:09.520 align:start position:0% trying to get at here is the censorship 00:07:09.520 --> 00:07:11.710 align:start position:0% trying to get at here is the censorship resistance<00:07:10.000> property<00:07:11.000> uh<00:07:11.080> and<00:07:11.240> the<00:07:11.360> idea<00:07:11.599> is 00:07:11.710 --> 00:07:11.720 align:start position:0% resistance property uh and the idea is 00:07:11.720 --> 00:07:13.189 align:start position:0% resistance property uh and the idea is that<00:07:11.960> if<00:07:12.080> there's<00:07:12.280> only<00:07:12.520> one<00:07:12.759> honest 00:07:13.189 --> 00:07:13.199 align:start position:0% that if there's only one honest 00:07:13.199 --> 00:07:14.510 align:start position:0% that if there's only one honest inclusionist<00:07:13.759> Committee<00:07:14.080> Member<00:07:14.319> in<00:07:14.400> the 00:07:14.510 --> 00:07:14.520 align:start position:0% inclusionist Committee Member in the 00:07:14.520 --> 00:07:15.670 align:start position:0% inclusionist Committee Member in the committee<00:07:14.919> it<00:07:15.039> can<00:07:15.160> include<00:07:15.560> the 00:07:15.670 --> 00:07:15.680 align:start position:0% committee it can include the 00:07:15.680 --> 00:07:17.670 align:start position:0% committee it can include the transactions<00:07:16.199> that<00:07:16.280> are<00:07:16.479> most<00:07:16.720> likely<00:07:17.400> to<00:07:17.520> be 00:07:17.670 --> 00:07:17.680 align:start position:0% transactions that are most likely to be 00:07:17.680 --> 00:07:19.869 align:start position:0% transactions that are most likely to be censored<00:07:18.120> by<00:07:18.199> the<00:07:18.319> blood<00:07:18.560> producer<00:07:19.520> uh<00:07:19.680> and 00:07:19.869 --> 00:07:19.879 align:start position:0% censored by the blood producer uh and 00:07:19.879 --> 00:07:21.869 align:start position:0% censored by the blood producer uh and include<00:07:20.280> them<00:07:20.840> uh<00:07:20.919> in<00:07:21.039> its<00:07:21.240> inclusion<00:07:21.680> list 00:07:21.869 --> 00:07:21.879 align:start position:0% include them uh in its inclusion list 00:07:21.879 --> 00:07:23.070 align:start position:0% include them uh in its inclusion list meaning<00:07:22.120> that<00:07:22.240> the<00:07:22.319> blood<00:07:22.520> producer<00:07:22.840> has<00:07:22.960> to 00:07:23.070 --> 00:07:23.080 align:start position:0% meaning that the blood producer has to 00:07:23.080 --> 00:07:25.990 align:start position:0% meaning that the blood producer has to include<00:07:23.400> them<00:07:23.479> in<00:07:23.599> the<00:07:24.000> block<00:07:25.000> if<00:07:25.199> we<00:07:25.479> have<00:07:25.919> a 00:07:25.990 --> 00:07:26.000 align:start position:0% include them in the block if we have a 00:07:26.000 --> 00:07:27.790 align:start position:0% include them in the block if we have a network<00:07:26.360> observation<00:07:27.000> that<00:07:27.160> there<00:07:27.280> is<00:07:27.440> a 00:07:27.790 --> 00:07:27.800 align:start position:0% network observation that there is a 00:07:27.800 --> 00:07:29.869 align:start position:0% network observation that there is a conservative<00:07:28.360> estimate<00:07:28.720> of<00:07:28.879> 6%<00:07:29.360> of<00:07:29.599> solo 00:07:29.869 --> 00:07:29.879 align:start position:0% conservative estimate of 6% of solo 00:07:29.879 --> 00:07:32.710 align:start position:0% conservative estimate of 6% of solo stakers<00:07:30.840> then<00:07:31.000> there's<00:07:31.160> a<00:07:31.360> 63%<00:07:32.240> chance<00:07:32.599> that 00:07:32.710 --> 00:07:32.720 align:start position:0% stakers then there's a 63% chance that 00:07:32.720 --> 00:07:34.670 align:start position:0% stakers then there's a 63% chance that in<00:07:32.879> this<00:07:33.000> single<00:07:33.319> slot<00:07:33.639> there's<00:07:33.840> at<00:07:34.000> least<00:07:34.280> one 00:07:34.670 --> 00:07:34.680 align:start position:0% in this single slot there's at least one 00:07:34.680 --> 00:07:36.029 align:start position:0% in this single slot there's at least one inclusionist<00:07:35.280> Committee<00:07:35.560> Member<00:07:35.800> who's<00:07:35.919> a 00:07:36.029 --> 00:07:36.039 align:start position:0% inclusionist Committee Member who's a 00:07:36.039 --> 00:07:38.110 align:start position:0% inclusionist Committee Member who's a solo<00:07:36.319> Staker<00:07:37.080> but<00:07:37.240> again<00:07:37.520> inclusion<00:07:37.879> lists 00:07:38.110 --> 00:07:38.120 align:start position:0% solo Staker but again inclusion lists 00:07:38.120 --> 00:07:40.469 align:start position:0% solo Staker but again inclusion lists are<00:07:38.240> not<00:07:38.400> only<00:07:38.720> about<00:07:39.400> regulatory<00:07:39.960> censorship 00:07:40.469 --> 00:07:40.479 align:start position:0% are not only about regulatory censorship 00:07:40.479 --> 00:07:41.909 align:start position:0% are not only about regulatory censorship they're<00:07:40.720> very<00:07:40.879> much<00:07:41.120> about<00:07:41.360> economic 00:07:41.909 --> 00:07:41.919 align:start position:0% they're very much about economic 00:07:41.919 --> 00:07:43.430 align:start position:0% they're very much about economic censorship<00:07:42.840> there's<00:07:43.039> been<00:07:43.199> some 00:07:43.430 --> 00:07:43.440 align:start position:0% censorship there's been some 00:07:43.440 --> 00:07:45.149 align:start position:0% censorship there's been some observations<00:07:44.039> of<00:07:44.199> Builders<00:07:44.599> strategically 00:07:45.149 --> 00:07:45.159 align:start position:0% observations of Builders strategically 00:07:45.159 --> 00:07:46.670 align:start position:0% observations of Builders strategically underfilling<00:07:45.759> their<00:07:45.879> blocks<00:07:46.319> perhaps 00:07:46.670 --> 00:07:46.680 align:start position:0% underfilling their blocks perhaps 00:07:46.680 --> 00:07:48.830 align:start position:0% underfilling their blocks perhaps because<00:07:46.840> they<00:07:46.960> want<00:07:47.159> them<00:07:47.280> to<00:07:47.440> be<00:07:47.720> lighter<00:07:48.720> uh 00:07:48.830 --> 00:07:48.840 align:start position:0% because they want them to be lighter uh 00:07:48.840 --> 00:07:51.070 align:start position:0% because they want them to be lighter uh in<00:07:49.000> terms<00:07:49.240> of<00:07:49.479> the<00:07:49.639> the<00:07:49.720> bandwidth<00:07:50.159> that<00:07:50.280> they 00:07:51.070 --> 00:07:51.080 align:start position:0% in terms of the the bandwidth that they 00:07:51.080 --> 00:07:54.149 align:start position:0% in terms of the the bandwidth that they consume<00:07:52.080> uh<00:07:52.199> or<00:07:52.599> maybe<00:07:52.919> perhaps<00:07:53.240> because<00:07:53.400> they 00:07:54.149 --> 00:07:54.159 align:start position:0% consume uh or maybe perhaps because they 00:07:54.159 --> 00:07:55.869 align:start position:0% consume uh or maybe perhaps because they play<00:07:54.440> some<00:07:54.720> games<00:07:55.080> or<00:07:55.240> they<00:07:55.360> simply<00:07:55.639> haven't 00:07:55.869 --> 00:07:55.879 align:start position:0% play some games or they simply haven't 00:07:55.879 --> 00:07:57.309 align:start position:0% play some games or they simply haven't seen<00:07:56.120> some<00:07:56.319> transactions<00:07:56.840> so<00:07:56.960> inclusion 00:07:57.309 --> 00:07:57.319 align:start position:0% seen some transactions so inclusion 00:07:57.319 --> 00:07:58.950 align:start position:0% seen some transactions so inclusion lists<00:07:57.560> are<00:07:57.759> here<00:07:57.919> for<00:07:58.120> all<00:07:58.280> of<00:07:58.440> those<00:07:58.560> sorts<00:07:58.800> of 00:07:58.950 --> 00:07:58.960 align:start position:0% lists are here for all of those sorts of 00:07:58.960 --> 00:08:00.110 align:start position:0% lists are here for all of those sorts of transactions 00:08:00.110 --> 00:08:00.120 align:start position:0% transactions 00:08:00.120 --> 00:08:01.469 align:start position:0% transactions the<00:08:00.240> idea<00:08:00.520> is<00:08:00.599> that<00:08:00.720> we're<00:08:00.919> boosting<00:08:01.319> the 00:08:01.469 --> 00:08:01.479 align:start position:0% the idea is that we're boosting the 00:08:01.479 --> 00:08:04.110 align:start position:0% the idea is that we're boosting the signal<00:08:01.840> that<00:08:01.960> solar<00:08:02.280> stakers<00:08:02.840> provide<00:08:03.840> uh 00:08:04.110 --> 00:08:04.120 align:start position:0% signal that solar stakers provide uh 00:08:04.120 --> 00:08:06.189 align:start position:0% signal that solar stakers provide uh while<00:08:04.280> not<00:08:04.479> relying<00:08:05.039> on<00:08:05.240> economic<00:08:05.680> incentives 00:08:06.189 --> 00:08:06.199 align:start position:0% while not relying on economic incentives 00:08:06.199 --> 00:08:07.270 align:start position:0% while not relying on economic incentives here<00:08:06.400> because<00:08:06.599> they<00:08:06.759> complicate<00:08:07.159> the 00:08:07.270 --> 00:08:07.280 align:start position:0% here because they complicate the 00:08:07.280 --> 00:08:10.869 align:start position:0% here because they complicate the mechanism<00:08:08.120> and<00:08:08.240> it<00:08:08.360> adds<00:08:08.560> a<00:08:08.639> lot<00:08:08.759> of<00:08:08.879> protocol 00:08:10.869 --> 00:08:10.879 align:start position:0% mechanism and it adds a lot of protocol 00:08:10.879 --> 00:08:13.749 align:start position:0% mechanism and it adds a lot of protocol complexity<00:08:11.879> so<00:08:12.039> now<00:08:12.199> I'll<00:08:12.400> go<00:08:12.520> on<00:08:12.759> to<00:08:13.159> show<00:08:13.560> how 00:08:13.749 --> 00:08:13.759 align:start position:0% complexity so now I'll go on to show how 00:08:13.759 --> 00:08:15.390 align:start position:0% complexity so now I'll go on to show how fossils<00:08:14.199> designed<00:08:14.479> to<00:08:14.599> be<00:08:14.720> as<00:08:14.879> robust<00:08:15.240> as 00:08:15.390 --> 00:08:15.400 align:start position:0% fossils designed to be as robust as 00:08:15.400 --> 00:08:17.469 align:start position:0% fossils designed to be as robust as possible<00:08:16.159> and<00:08:16.280> robustness<00:08:16.800> here<00:08:16.960> refers<00:08:17.280> to 00:08:17.469 --> 00:08:17.479 align:start position:0% possible and robustness here refers to 00:08:17.479 --> 00:08:19.950 align:start position:0% possible and robustness here refers to robustness<00:08:18.039> against<00:08:18.879> consensus<00:08:19.520> types<00:08:19.759> of 00:08:19.950 --> 00:08:19.960 align:start position:0% robustness against consensus types of 00:08:19.960 --> 00:08:22.629 align:start position:0% robustness against consensus types of attacks<00:08:20.360> like<00:08:20.599> the<00:08:21.479> um<00:08:21.680> split<00:08:22.000> view<00:08:22.280> attack 00:08:22.629 --> 00:08:22.639 align:start position:0% attacks like the um split view attack 00:08:22.639 --> 00:08:24.950 align:start position:0% attacks like the um split view attack and<00:08:22.919> equivocation<00:08:23.919> and<00:08:24.039> it<00:08:24.199> also<00:08:24.400> refers<00:08:24.720> to 00:08:24.950 --> 00:08:24.960 align:start position:0% and equivocation and it also refers to 00:08:24.960 --> 00:08:27.469 align:start position:0% and equivocation and it also refers to execution<00:08:25.440> layer<00:08:25.879> types<00:08:26.120> of<00:08:26.280> attacks<00:08:26.720> so 00:08:27.469 --> 00:08:27.479 align:start position:0% execution layer types of attacks so 00:08:27.479 --> 00:08:29.749 align:start position:0% execution layer types of attacks so people<00:08:28.159> using<00:08:28.479> fossil<00:08:28.879> for<00:08:29.039> other<00:08:29.199> reason 00:08:29.749 --> 00:08:29.759 align:start position:0% people using fossil for other reason 00:08:29.759 --> 00:08:31.510 align:start position:0% people using fossil for other reason forens<00:08:30.080> of<00:08:30.240> resistance<00:08:30.759> but<00:08:30.919> for<00:08:31.080> example<00:08:31.400> as 00:08:31.510 --> 00:08:31.520 align:start position:0% forens of resistance but for example as 00:08:31.520 --> 00:08:33.070 align:start position:0% forens of resistance but for example as a<00:08:31.720> vehicle<00:08:32.080> to<00:08:32.240> extract<00:08:32.719> maximum 00:08:33.070 --> 00:08:33.080 align:start position:0% a vehicle to extract maximum 00:08:33.080 --> 00:08:34.709 align:start position:0% a vehicle to extract maximum distractable<00:08:33.599> value 00:08:34.709 --> 00:08:34.719 align:start position:0% distractable value 00:08:34.719 --> 00:08:38.230 align:start position:0% distractable value me<00:08:35.719> so<00:08:35.919> first<00:08:36.080> the<00:08:36.240> consensus<00:08:36.640> layer<00:08:37.240> attacks 00:08:38.230 --> 00:08:38.240 align:start position:0% me so first the consensus layer attacks 00:08:38.240 --> 00:08:39.430 align:start position:0% me so first the consensus layer attacks um<00:08:38.360> we've<00:08:38.519> talked<00:08:38.719> a<00:08:38.800> little<00:08:39.039> bit<00:08:39.200> about<00:08:39.320> the 00:08:39.430 --> 00:08:39.440 align:start position:0% um we've talked a little bit about the 00:08:39.440 --> 00:08:41.190 align:start position:0% um we've talked a little bit about the split<00:08:39.719> view<00:08:40.159> but<00:08:40.360> there<00:08:40.479> in<00:08:40.640> fact<00:08:40.880> there<00:08:41.000> are 00:08:41.190 --> 00:08:41.200 align:start position:0% split view but there in fact there are 00:08:41.200 --> 00:08:43.269 align:start position:0% split view but there in fact there are two<00:08:41.360> split<00:08:41.640> view<00:08:41.800> attacks<00:08:42.120> to<00:08:42.279> consider<00:08:43.080> first 00:08:43.269 --> 00:08:43.279 align:start position:0% two split view attacks to consider first 00:08:43.279 --> 00:08:45.509 align:start position:0% two split view attacks to consider first of<00:08:43.440> all<00:08:44.240> um<00:08:44.480> there's<00:08:44.680> the<00:08:44.839> split<00:08:45.080> view<00:08:45.279> that 00:08:45.509 --> 00:08:45.519 align:start position:0% of all um there's the split view that 00:08:45.519 --> 00:08:47.150 align:start position:0% of all um there's the split view that inclusionist<00:08:46.080> committee<00:08:46.360> members<00:08:46.720> ensure 00:08:47.150 --> 00:08:47.160 align:start position:0% inclusionist committee members ensure 00:08:47.160 --> 00:08:49.389 align:start position:0% inclusionist committee members ensure that<00:08:47.800> the<00:08:48.279> block<00:08:48.560> producer<00:08:48.959> would<00:08:49.120> have<00:08:49.240> a 00:08:49.389 --> 00:08:49.399 align:start position:0% that the block producer would have a 00:08:49.399 --> 00:08:51.630 align:start position:0% that the block producer would have a worse<00:08:49.760> view<00:08:50.399> of<00:08:50.720> the<00:08:50.880> available<00:08:51.240> inclusion 00:08:51.630 --> 00:08:51.640 align:start position:0% worse view of the available inclusion 00:08:51.640 --> 00:08:53.710 align:start position:0% worse view of the available inclusion list<00:08:51.800> than<00:08:51.920> the<00:08:52.080> testers<00:08:52.680> and<00:08:52.839> this<00:08:52.920> is<00:08:53.160> bad 00:08:53.710 --> 00:08:53.720 align:start position:0% list than the testers and this is bad 00:08:53.720 --> 00:08:54.990 align:start position:0% list than the testers and this is bad because<00:08:54.000> then<00:08:54.120> the<00:08:54.240> block<00:08:54.480> producer<00:08:54.800> can't 00:08:54.990 --> 00:08:55.000 align:start position:0% because then the block producer can't 00:08:55.000 --> 00:08:57.230 align:start position:0% because then the block producer can't produce<00:08:55.240> a<00:08:55.360> block<00:08:55.640> that<00:08:55.760> becomes<00:08:56.040> chical<00:08:57.040> so 00:08:57.230 --> 00:08:57.240 align:start position:0% produce a block that becomes chical so 00:08:57.240 --> 00:08:59.030 align:start position:0% produce a block that becomes chical so we<00:08:57.560> prevent<00:08:57.920> this<00:08:58.160> by<00:08:58.320> giving<00:08:58.680> the<00:08:58.800> block 00:08:59.030 --> 00:08:59.040 align:start position:0% we prevent this by giving the block 00:08:59.040 --> 00:09:01.350 align:start position:0% we prevent this by giving the block producer<00:08:59.560> three<00:08:59.720> extra<00:09:00.160> seconds<00:09:00.959> u<00:09:01.120> in<00:09:01.240> which 00:09:01.350 --> 00:09:01.360 align:start position:0% producer three extra seconds u in which 00:09:01.360 --> 00:09:03.190 align:start position:0% producer three extra seconds u in which the<00:09:01.519> testers<00:09:01.880> have<00:09:01.959> a<00:09:02.040> really<00:09:02.279> Frozen<00:09:02.600> their 00:09:03.190 --> 00:09:03.200 align:start position:0% the testers have a really Frozen their 00:09:03.200 --> 00:09:05.630 align:start position:0% the testers have a really Frozen their view<00:09:04.200> then<00:09:04.360> secondly<00:09:04.800> there's<00:09:05.000> a<00:09:05.120> split<00:09:05.399> view 00:09:05.630 --> 00:09:05.640 align:start position:0% view then secondly there's a split view 00:09:05.640 --> 00:09:07.470 align:start position:0% view then secondly there's a split view attack<00:09:06.279> uh<00:09:06.360> that's<00:09:06.560> related<00:09:06.880> to<00:09:07.079> I 00:09:07.470 --> 00:09:07.480 align:start position:0% attack uh that's related to I 00:09:07.480 --> 00:09:09.829 align:start position:0% attack uh that's related to I equivocation<00:09:08.440> so<00:09:08.600> you<00:09:08.760> could<00:09:09.160> imagine<00:09:09.680> a 00:09:09.829 --> 00:09:09.839 align:start position:0% equivocation so you could imagine a 00:09:09.839 --> 00:09:11.509 align:start position:0% equivocation so you could imagine a Committee<00:09:10.160> Member<00:09:10.480> signing<00:09:10.839> two<00:09:11.079> inclusion 00:09:11.509 --> 00:09:11.519 align:start position:0% Committee Member signing two inclusion 00:09:11.519 --> 00:09:13.190 align:start position:0% Committee Member signing two inclusion lists<00:09:12.079> and<00:09:12.200> sending<00:09:12.600> one<00:09:12.720> to<00:09:12.839> the<00:09:12.959> block 00:09:13.190 --> 00:09:13.200 align:start position:0% lists and sending one to the block 00:09:13.200 --> 00:09:15.710 align:start position:0% lists and sending one to the block producer<00:09:13.720> and<00:09:13.839> one<00:09:14.000> to<00:09:14.200> the<00:09:14.360> tester<00:09:14.760> set<00:09:15.079> if<00:09:15.200> it 00:09:15.710 --> 00:09:15.720 align:start position:0% producer and one to the tester set if it 00:09:15.720 --> 00:09:18.269 align:start position:0% producer and one to the tester set if it would<00:09:15.920> have<00:09:16.120> control<00:09:16.480> over<00:09:16.800> that<00:09:17.800> um<00:09:18.000> and<00:09:18.120> how 00:09:18.269 --> 00:09:18.279 align:start position:0% would have control over that um and how 00:09:18.279 --> 00:09:20.190 align:start position:0% would have control over that um and how we<00:09:18.519> prevent<00:09:18.880> any<00:09:19.079> bad<00:09:19.320> things<00:09:19.600> from<00:09:19.800> happening 00:09:20.190 --> 00:09:20.200 align:start position:0% we prevent any bad things from happening 00:09:20.200 --> 00:09:23.069 align:start position:0% we prevent any bad things from happening here<00:09:20.399> is<00:09:20.519> we<00:09:20.640> say<00:09:20.800> it<00:09:20.959> as<00:09:21.360> if<00:09:22.360> um<00:09:22.560> there<00:09:22.680> are<00:09:22.880> two 00:09:23.069 --> 00:09:23.079 align:start position:0% here is we say it as if um there are two 00:09:23.079 --> 00:09:25.190 align:start position:0% here is we say it as if um there are two inclusion<00:09:23.600> list<00:09:23.920> so<00:09:24.079> if<00:09:24.200> an<00:09:24.360> attestor<00:09:24.920> blood 00:09:25.190 --> 00:09:25.200 align:start position:0% inclusion list so if an attestor blood 00:09:25.200 --> 00:09:26.790 align:start position:0% inclusion list so if an attestor blood producer<00:09:25.800> receives<00:09:26.000> two<00:09:26.160> inclusion<00:09:26.560> lists 00:09:26.790 --> 00:09:26.800 align:start position:0% producer receives two inclusion lists 00:09:26.800 --> 00:09:29.110 align:start position:0% producer receives two inclusion lists from<00:09:26.920> the<00:09:27.040> same<00:09:27.279> Committee<00:09:27.680> Member<00:09:28.640> then<00:09:28.959> they 00:09:29.110 --> 00:09:29.120 align:start position:0% from the same Committee Member then they 00:09:29.120 --> 00:09:30.790 align:start position:0% from the same Committee Member then they do<00:09:29.480> not<00:09:29.800> impact<00:09:30.200> how<00:09:30.320> the<00:09:30.440> block<00:09:30.640> is 00:09:30.790 --> 00:09:30.800 align:start position:0% do not impact how the block is 00:09:30.800 --> 00:09:33.470 align:start position:0% do not impact how the block is constrained<00:09:31.320> at<00:09:31.600> all<00:09:32.600> um<00:09:32.760> so<00:09:32.920> what<00:09:33.040> this<00:09:33.200> means 00:09:33.470 --> 00:09:33.480 align:start position:0% constrained at all um so what this means 00:09:33.480 --> 00:09:35.269 align:start position:0% constrained at all um so what this means is<00:09:33.640> that<00:09:33.800> if<00:09:33.880> a<00:09:34.040> block<00:09:34.279> producer<00:09:34.959> receives<00:09:35.120> two 00:09:35.269 --> 00:09:35.279 align:start position:0% is that if a block producer receives two 00:09:35.279 --> 00:09:37.389 align:start position:0% is that if a block producer receives two inclusion<00:09:35.680> lists<00:09:36.000> doesn't<00:09:36.279> know<00:09:36.640> how<00:09:36.760> to<00:09:37.000> act 00:09:37.389 --> 00:09:37.399 align:start position:0% inclusion lists doesn't know how to act 00:09:37.399 --> 00:09:39.230 align:start position:0% inclusion lists doesn't know how to act now<00:09:37.600> it<00:09:37.720> knows<00:09:38.160> okay<00:09:38.399> I<00:09:38.519> I<00:09:38.600> do<00:09:38.760> not<00:09:38.920> have<00:09:39.040> to 00:09:39.230 --> 00:09:39.240 align:start position:0% now it knows okay I I do not have to 00:09:39.240 --> 00:09:41.069 align:start position:0% now it knows okay I I do not have to adhere<00:09:39.600> to<00:09:39.839> this<00:09:40.200> this<00:09:40.279> is<00:09:40.399> a<00:09:40.519> weird<00:09:40.800> case<00:09:41.000> it 00:09:41.069 --> 00:09:41.079 align:start position:0% adhere to this this is a weird case it 00:09:41.079 --> 00:09:42.910 align:start position:0% adhere to this this is a weird case it should<00:09:41.240> not<00:09:41.399> be<00:09:41.519> happening<00:09:42.279> and<00:09:42.399> the<00:09:42.560> testers 00:09:42.910 --> 00:09:42.920 align:start position:0% should not be happening and the testers 00:09:42.920 --> 00:09:44.590 align:start position:0% should not be happening and the testers also<00:09:43.120> know<00:09:43.399> this<00:09:43.720> so<00:09:43.880> they<00:09:44.000> don't<00:09:44.200> enforce 00:09:44.590 --> 00:09:44.600 align:start position:0% also know this so they don't enforce 00:09:44.600 --> 00:09:46.269 align:start position:0% also know this so they don't enforce inclusionist<00:09:45.120> where<00:09:45.240> there<00:09:45.360> are<00:09:45.480> two<00:09:46.120> a 00:09:46.269 --> 00:09:46.279 align:start position:0% inclusionist where there are two a 00:09:46.279 --> 00:09:48.030 align:start position:0% inclusionist where there are two a testers<00:09:46.640> have<00:09:46.800> 4<00:09:47.079> seconds<00:09:47.480> after<00:09:47.680> the<00:09:47.800> block 00:09:48.030 --> 00:09:48.040 align:start position:0% testers have 4 seconds after the block 00:09:48.040 --> 00:09:49.790 align:start position:0% testers have 4 seconds after the block is<00:09:48.200> produced<00:09:48.560> to<00:09:48.760> receive<00:09:49.120> these<00:09:49.399> inclusion 00:09:49.790 --> 00:09:49.800 align:start position:0% is produced to receive these inclusion 00:09:49.800 --> 00:09:52.110 align:start position:0% is produced to receive these inclusion list<00:09:50.320> so<00:09:50.560> here<00:09:50.760> again<00:09:51.000> we<00:09:51.600> uh<00:09:51.720> prevent<00:09:52.000> the 00:09:52.110 --> 00:09:52.120 align:start position:0% list so here again we uh prevent the 00:09:52.120 --> 00:09:54.190 align:start position:0% list so here again we uh prevent the split<00:09:52.399> view<00:09:53.360> not<00:09:53.560> enforcing<00:09:54.040> any 00:09:54.190 --> 00:09:54.200 align:start position:0% split view not enforcing any 00:09:54.200 --> 00:09:56.750 align:start position:0% split view not enforcing any inclusionist<00:09:54.880> when<00:09:55.000> two<00:09:55.200> are<00:09:55.360> sent<00:09:56.160> uh<00:09:56.279> is<00:09:56.360> a 00:09:56.750 --> 00:09:56.760 align:start position:0% inclusionist when two are sent uh is a 00:09:56.760 --> 00:09:59.030 align:start position:0% inclusionist when two are sent uh is a deliberate<00:09:57.240> decision<00:09:57.839> because<00:09:58.760> um<00:09:58.880> this 00:09:59.030 --> 00:09:59.040 align:start position:0% deliberate decision because um this 00:09:59.040 --> 00:10:01.350 align:start position:0% deliberate decision because um this should<00:09:59.640> happen<00:10:00.240> either<00:10:00.600> if<00:10:00.839> the<00:10:01.000> node<00:10:01.200> is 00:10:01.350 --> 00:10:01.360 align:start position:0% should happen either if the node is 00:10:01.360 --> 00:10:03.630 align:start position:0% should happen either if the node is configured<00:10:02.079> incorrectly<00:10:02.920> or<00:10:03.120> if<00:10:03.279> it's<00:10:03.440> an 00:10:03.630 --> 00:10:03.640 align:start position:0% configured incorrectly or if it's an 00:10:03.640 --> 00:10:06.470 align:start position:0% configured incorrectly or if it's an attack<00:10:04.480> and<00:10:05.279> um<00:10:05.480> realistically<00:10:06.040> it<00:10:06.200> has<00:10:06.360> the 00:10:06.470 --> 00:10:06.480 align:start position:0% attack and um realistically it has the 00:10:06.480 --> 00:10:08.230 align:start position:0% attack and um realistically it has the same<00:10:06.720> impacts<00:10:07.120> as<00:10:07.399> someone<00:10:07.640> sending<00:10:08.000> no 00:10:08.230 --> 00:10:08.240 align:start position:0% same impacts as someone sending no 00:10:08.240 --> 00:10:09.829 align:start position:0% same impacts as someone sending no inclusion<00:10:08.680> list<00:10:08.959> so<00:10:09.279> if<00:10:09.360> you<00:10:09.440> said<00:10:09.680> no 00:10:09.829 --> 00:10:09.839 align:start position:0% inclusion list so if you said no 00:10:09.839 --> 00:10:11.670 align:start position:0% inclusion list so if you said no inclusion<00:10:10.279> list<00:10:10.519> no<00:10:10.680> inclusion<00:10:11.079> is<00:10:11.240> enforced 00:10:11.670 --> 00:10:11.680 align:start position:0% inclusion list no inclusion is enforced 00:10:11.680 --> 00:10:14.110 align:start position:0% inclusion list no inclusion is enforced if<00:10:11.760> you<00:10:11.839> send<00:10:12.120> two<00:10:12.440> also<00:10:12.720> no<00:10:13.040> is<00:10:13.200> enforced<00:10:14.000> and 00:10:14.110 --> 00:10:14.120 align:start position:0% if you send two also no is enforced and 00:10:14.120 --> 00:10:15.470 align:start position:0% if you send two also no is enforced and the<00:10:14.240> other<00:10:14.440> inclusion<00:10:14.839> list<00:10:15.040> from<00:10:15.160> the<00:10:15.240> other 00:10:15.470 --> 00:10:15.480 align:start position:0% the other inclusion list from the other 00:10:15.480 --> 00:10:18.030 align:start position:0% the other inclusion list from the other committee<00:10:15.839> members<00:10:16.200> are<00:10:16.399> still<00:10:16.640> enforced<00:10:17.079> of 00:10:18.030 --> 00:10:18.040 align:start position:0% committee members are still enforced of 00:10:18.040 --> 00:10:20.230 align:start position:0% committee members are still enforced of course<00:10:19.040> so<00:10:19.240> then<00:10:19.360> there's<00:10:19.600> transaction<00:10:20.040> inv 00:10:20.230 --> 00:10:20.240 align:start position:0% course so then there's transaction inv 00:10:20.240 --> 00:10:22.230 align:start position:0% course so then there's transaction inv validation<00:10:21.160> so<00:10:21.560> transactions<00:10:22.000> in<00:10:22.120> the 00:10:22.230 --> 00:10:22.240 align:start position:0% validation so transactions in the 00:10:22.240 --> 00:10:24.110 align:start position:0% validation so transactions in the inclusion<00:10:22.680> list<00:10:22.920> may<00:10:23.079> be<00:10:23.360> invalid<00:10:23.920> at<00:10:24.000> the 00:10:24.110 --> 00:10:24.120 align:start position:0% inclusion list may be invalid at the 00:10:24.120 --> 00:10:25.389 align:start position:0% inclusion list may be invalid at the time<00:10:24.320> that<00:10:24.440> the<00:10:24.519> inclusionist<00:10:25.079> Committee 00:10:25.389 --> 00:10:25.399 align:start position:0% time that the inclusionist Committee 00:10:25.399 --> 00:10:27.670 align:start position:0% time that the inclusionist Committee Member<00:10:25.920> propagated<00:10:26.560> them<00:10:26.920> towards<00:10:27.440> that<00:10:27.560> the 00:10:27.670 --> 00:10:27.680 align:start position:0% Member propagated them towards that the 00:10:27.680 --> 00:10:29.310 align:start position:0% Member propagated them towards that the block<00:10:27.920> producer<00:10:28.240> must<00:10:28.399> include<00:10:28.760> them<00:10:29.160> there 00:10:29.310 --> 00:10:29.320 align:start position:0% block producer must include them there 00:10:29.320 --> 00:10:30.710 align:start position:0% block producer must include them there there<00:10:29.360> are<00:10:29.480> two<00:10:29.640> reasons<00:10:29.959> for<00:10:30.160> this 00:10:30.710 --> 00:10:30.720 align:start position:0% there are two reasons for this 00:10:30.720 --> 00:10:32.030 align:start position:0% there are two reasons for this potentially<00:10:31.120> the<00:10:31.240> inclusionist<00:10:31.760> Committee 00:10:32.030 --> 00:10:32.040 align:start position:0% potentially the inclusionist Committee 00:10:32.040 --> 00:10:33.550 align:start position:0% potentially the inclusionist Committee Member<00:10:32.320> doesn't<00:10:32.600> know<00:10:32.920> the<00:10:33.120> right<00:10:33.320> head<00:10:33.480> of 00:10:33.550 --> 00:10:33.560 align:start position:0% Member doesn't know the right head of 00:10:33.560 --> 00:10:34.949 align:start position:0% Member doesn't know the right head of the<00:10:33.640> chain<00:10:33.880> so<00:10:34.000> it's<00:10:34.120> building<00:10:34.399> on<00:10:34.560> some<00:10:34.720> other 00:10:34.949 --> 00:10:34.959 align:start position:0% the chain so it's building on some other 00:10:34.959 --> 00:10:36.870 align:start position:0% the chain so it's building on some other head<00:10:35.760> uh<00:10:35.880> and<00:10:36.000> the<00:10:36.120> second<00:10:36.399> reason<00:10:36.639> is<00:10:36.760> that 00:10:36.870 --> 00:10:36.880 align:start position:0% head uh and the second reason is that 00:10:36.880 --> 00:10:38.110 align:start position:0% head uh and the second reason is that the<00:10:36.959> block<00:10:37.200> producer<00:10:37.560> could<00:10:37.760> include 00:10:38.110 --> 00:10:38.120 align:start position:0% the block producer could include 00:10:38.120 --> 00:10:40.230 align:start position:0% the block producer could include transactions<00:10:38.800> before<00:10:39.600> the<00:10:39.800> transactions 00:10:40.230 --> 00:10:40.240 align:start position:0% transactions before the transactions 00:10:40.240 --> 00:10:42.829 align:start position:0% transactions before the transactions from<00:10:40.399> the<00:10:40.480> inclusion<00:10:40.959> list<00:10:41.680> so<00:10:42.240> the<00:10:42.720> the 00:10:42.829 --> 00:10:42.839 align:start position:0% from the inclusion list so the the 00:10:42.839 --> 00:10:44.150 align:start position:0% from the inclusion list so the the inclusive<00:10:43.320> Committee<00:10:43.600> Member<00:10:43.880> cannot 00:10:44.150 --> 00:10:44.160 align:start position:0% inclusive Committee Member cannot 00:10:44.160 --> 00:10:45.509 align:start position:0% inclusive Committee Member cannot possibly<00:10:44.480> know<00:10:44.680> what<00:10:44.839> the<00:10:44.920> block<00:10:45.079> producer<00:10:45.440> is 00:10:45.509 --> 00:10:45.519 align:start position:0% possibly know what the block producer is 00:10:45.519 --> 00:10:47.509 align:start position:0% possibly know what the block producer is going<00:10:45.639> to<00:10:45.760> do<00:10:46.000> since<00:10:46.160> it<00:10:46.279> acts<00:10:46.600> before<00:10:47.200> so 00:10:47.509 --> 00:10:47.519 align:start position:0% going to do since it acts before so 00:10:47.519 --> 00:10:50.110 align:start position:0% going to do since it acts before so transactions<00:10:47.959> could<00:10:48.160> be<00:10:48.600> invalid<00:10:49.600> to<00:10:49.800> prevent 00:10:50.110 --> 00:10:50.120 align:start position:0% transactions could be invalid to prevent 00:10:50.120 --> 00:10:52.509 align:start position:0% transactions could be invalid to prevent free<00:10:50.440> data<00:10:50.720> availability<00:10:51.680> which<00:10:51.800> is<00:10:52.079> a<00:10:52.360> a 00:10:52.509 --> 00:10:52.519 align:start position:0% free data availability which is a a 00:10:52.519 --> 00:10:54.350 align:start position:0% free data availability which is a a problem<00:10:52.839> that<00:10:53.000> arose<00:10:53.360> with<00:10:53.480> a<00:10:53.680> previous<00:10:54.279> uh 00:10:54.350 --> 00:10:54.360 align:start position:0% problem that arose with a previous uh 00:10:54.360 --> 00:10:56.629 align:start position:0% problem that arose with a previous uh inclusionist<00:10:54.920> EIP<00:10:55.920> uh<00:10:56.040> a<00:10:56.160> tester's<00:10:56.480> only 00:10:56.629 --> 00:10:56.639 align:start position:0% inclusionist EIP uh a tester's only 00:10:56.639 --> 00:10:57.870 align:start position:0% inclusionist EIP uh a tester's only check<00:10:56.880> where<00:10:57.079> a<00:10:57.200> transaction<00:10:57.639> could<00:10:57.760> have 00:10:57.870 --> 00:10:57.880 align:start position:0% check where a transaction could have 00:10:57.880 --> 00:10:59.870 align:start position:0% check where a transaction could have been<00:10:58.079> validly<00:10:58.519> appended<00:10:59.000> to<00:10:59.320> the<00:10:59.440> execution 00:10:59.870 --> 00:10:59.880 align:start position:0% been validly appended to the execution 00:10:59.880 --> 00:11:01.990 align:start position:0% been validly appended to the execution payload<00:11:00.600> so<00:11:00.760> if<00:11:00.839> a<00:11:01.000> transaction<00:11:01.399> is<00:11:01.519> invalid 00:11:01.990 --> 00:11:02.000 align:start position:0% payload so if a transaction is invalid 00:11:02.000 --> 00:11:03.389 align:start position:0% payload so if a transaction is invalid then<00:11:02.160> clearly<00:11:02.440> it<00:11:02.560> cannot<00:11:02.839> be<00:11:03.000> validly 00:11:03.389 --> 00:11:03.399 align:start position:0% then clearly it cannot be validly 00:11:03.399 --> 00:11:05.389 align:start position:0% then clearly it cannot be validly appended<00:11:04.079> similar<00:11:04.399> to<00:11:04.600> how<00:11:04.800> if<00:11:04.920> a<00:11:05.079> block<00:11:05.279> is 00:11:05.389 --> 00:11:05.399 align:start position:0% appended similar to how if a block is 00:11:05.399 --> 00:11:06.990 align:start position:0% appended similar to how if a block is full<00:11:05.720> a<00:11:05.839> transaction<00:11:06.240> cannot<00:11:06.519> be<00:11:06.639> validly 00:11:06.990 --> 00:11:07.000 align:start position:0% full a transaction cannot be validly 00:11:07.000 --> 00:11:09.150 align:start position:0% full a transaction cannot be validly appended<00:11:07.519> because<00:11:07.680> it<00:11:08.600> because<00:11:08.839> it<00:11:08.959> would 00:11:09.150 --> 00:11:09.160 align:start position:0% appended because it because it would 00:11:09.160 --> 00:11:12.310 align:start position:0% appended because it because it would raise<00:11:09.399> the<00:11:09.560> gas<00:11:09.800> limit<00:11:10.160> over<00:11:10.519> the<00:11:11.160> maximum<00:11:12.160> uh 00:11:12.310 --> 00:11:12.320 align:start position:0% raise the gas limit over the maximum uh 00:11:12.320 --> 00:11:13.910 align:start position:0% raise the gas limit over the maximum uh and<00:11:12.480> inclusion<00:11:12.880> lists<00:11:13.079> are<00:11:13.200> never<00:11:13.399> written<00:11:13.680> on 00:11:13.910 --> 00:11:13.920 align:start position:0% and inclusion lists are never written on 00:11:13.920 --> 00:11:16.790 align:start position:0% and inclusion lists are never written on chain<00:11:14.920> um<00:11:15.279> it's<00:11:15.440> only<00:11:15.760> the<00:11:16.000> execution<00:11:16.480> payload 00:11:16.790 --> 00:11:16.800 align:start position:0% chain um it's only the execution payload 00:11:16.800 --> 00:11:17.829 align:start position:0% chain um it's only the execution payload that's<00:11:16.920> written<00:11:17.200> on<00:11:17.320> change<00:11:17.560> so<00:11:17.720> this 00:11:17.829 --> 00:11:17.839 align:start position:0% that's written on change so this 00:11:17.839 --> 00:11:20.230 align:start position:0% that's written on change so this prevents<00:11:18.120> free<00:11:18.320> date<00:11:18.560> availability<00:11:19.120> as 00:11:20.230 --> 00:11:20.240 align:start position:0% prevents free date availability as 00:11:20.240 --> 00:11:23.110 align:start position:0% prevents free date availability as well<00:11:21.240> then<00:11:21.880> if<00:11:22.200> there<00:11:22.360> can<00:11:22.519> be<00:11:22.720> invalid 00:11:23.110 --> 00:11:23.120 align:start position:0% well then if there can be invalid 00:11:23.120 --> 00:11:25.230 align:start position:0% well then if there can be invalid transactions<00:11:23.720> in<00:11:23.880> the<00:11:24.040> inclusion<00:11:24.560> list<00:11:25.040> this 00:11:25.230 --> 00:11:25.240 align:start position:0% transactions in the inclusion list this 00:11:25.240 --> 00:11:27.590 align:start position:0% transactions in the inclusion list this may<00:11:25.600> lead<00:11:25.880> to<00:11:26.040> some<00:11:26.279> games<00:11:27.040> uh<00:11:27.160> that<00:11:27.240> you<00:11:27.360> might 00:11:27.590 --> 00:11:27.600 align:start position:0% may lead to some games uh that you might 00:11:27.600 --> 00:11:29.790 align:start position:0% may lead to some games uh that you might think<00:11:27.760> of<00:11:28.000> so<00:11:28.200> it<00:11:28.320> could<00:11:28.519> be<00:11:28.839> that<00:11:29.399> uh<00:11:29.519> someone 00:11:29.790 --> 00:11:29.800 align:start position:0% think of so it could be that uh someone 00:11:29.800 --> 00:11:31.190 align:start position:0% think of so it could be that uh someone knows<00:11:30.079> that<00:11:30.200> it<00:11:30.279> will<00:11:30.440> make<00:11:30.639> the<00:11:30.760> block<00:11:31.040> at 00:11:31.190 --> 00:11:31.200 align:start position:0% knows that it will make the block at 00:11:31.200 --> 00:11:33.430 align:start position:0% knows that it will make the block at second<00:11:31.519> 12<00:11:32.360> uh<00:11:32.480> and<00:11:32.560> it<00:11:32.720> tries<00:11:32.920> to<00:11:33.040> flood<00:11:33.360> the 00:11:33.430 --> 00:11:33.440 align:start position:0% second 12 uh and it tries to flood the 00:11:33.440 --> 00:11:34.870 align:start position:0% second 12 uh and it tries to flood the mle<00:11:33.839> with<00:11:33.959> transactions<00:11:34.440> that<00:11:34.560> it<00:11:34.680> will 00:11:34.870 --> 00:11:34.880 align:start position:0% mle with transactions that it will 00:11:34.880 --> 00:11:37.150 align:start position:0% mle with transactions that it will invalidate<00:11:35.320> in<00:11:35.480> its<00:11:35.639> block<00:11:35.920> later<00:11:36.200> on<00:11:36.800> meaning 00:11:37.150 --> 00:11:37.160 align:start position:0% invalidate in its block later on meaning 00:11:37.160 --> 00:11:40.030 align:start position:0% invalidate in its block later on meaning that<00:11:37.839> um<00:11:38.040> it<00:11:38.160> floods<00:11:39.160> uh<00:11:39.240> the<00:11:39.360> inclusion<00:11:39.760> list 00:11:40.030 --> 00:11:40.040 align:start position:0% that um it floods uh the inclusion list 00:11:40.040 --> 00:11:42.190 align:start position:0% that um it floods uh the inclusion list of<00:11:40.200> transactions<00:11:40.680> that<00:11:40.800> will<00:11:40.920> be<00:11:41.200> invalidated 00:11:42.190 --> 00:11:42.200 align:start position:0% of transactions that will be invalidated 00:11:42.200 --> 00:11:43.590 align:start position:0% of transactions that will be invalidated therefore<00:11:42.519> not<00:11:42.680> really<00:11:42.880> constraining<00:11:43.399> its 00:11:43.590 --> 00:11:43.600 align:start position:0% therefore not really constraining its 00:11:43.600 --> 00:11:46.590 align:start position:0% therefore not really constraining its block<00:11:44.160> uh<00:11:44.279> too<00:11:44.839> much<00:11:45.839> so<00:11:46.040> first<00:11:46.200> of<00:11:46.360> all<00:11:46.519> this 00:11:46.590 --> 00:11:46.600 align:start position:0% block uh too much so first of all this 00:11:46.600 --> 00:11:48.310 align:start position:0% block uh too much so first of all this is<00:11:46.959> a<00:11:47.279> difficult<00:11:47.480> attack<00:11:47.680> to<00:11:47.800> pull<00:11:48.000> off<00:11:48.160> in 00:11:48.310 --> 00:11:48.320 align:start position:0% is a difficult attack to pull off in 00:11:48.320 --> 00:11:50.310 align:start position:0% is a difficult attack to pull off in practice<00:11:48.800> because<00:11:49.079> usually<00:11:49.720> the<00:11:49.880> MEF<00:11:50.079> boost 00:11:50.310 --> 00:11:50.320 align:start position:0% practice because usually the MEF boost 00:11:50.320 --> 00:11:51.430 align:start position:0% practice because usually the MEF boost Builders<00:11:50.639> only<00:11:50.800> know<00:11:51.000> that<00:11:51.120> they're<00:11:51.320> the 00:11:51.430 --> 00:11:51.440 align:start position:0% Builders only know that they're the 00:11:51.440 --> 00:11:53.990 align:start position:0% Builders only know that they're the Builder<00:11:51.880> close<00:11:52.160> to<00:11:52.399> the<00:11:52.760> 12C<00:11:53.399> line<00:11:53.600> or<00:11:53.760> maybe 00:11:53.990 --> 00:11:54.000 align:start position:0% Builder close to the 12C line or maybe 00:11:54.000 --> 00:11:56.350 align:start position:0% Builder close to the 12C line or maybe even<00:11:54.279> past<00:11:54.560> that<00:11:55.440> uh<00:11:55.560> but<00:11:55.720> we<00:11:55.839> have<00:11:56.040> like<00:11:56.200> a 00:11:56.350 --> 00:11:56.360 align:start position:0% even past that uh but we have like a 00:11:56.360 --> 00:11:58.670 align:start position:0% even past that uh but we have like a defense<00:11:56.639> and<00:11:56.839> debt<00:11:57.079> strategy<00:11:57.600> here<00:11:58.279> uh<00:11:58.480> to 00:11:58.670 --> 00:11:58.680 align:start position:0% defense and debt strategy here uh to 00:11:58.680 --> 00:12:00.670 align:start position:0% defense and debt strategy here uh to prevent<00:11:59.040> this<00:11:59.600> so<00:11:59.800> how<00:11:59.920> we<00:12:00.040> do<00:12:00.200> it<00:12:00.480> is 00:12:00.670 --> 00:12:00.680 align:start position:0% prevent this so how we do it is 00:12:00.680 --> 00:12:02.269 align:start position:0% prevent this so how we do it is inclusion<00:12:01.120> list<00:12:01.320> proposers<00:12:01.720> are<00:12:01.880> free<00:12:02.079> to 00:12:02.269 --> 00:12:02.279 align:start position:0% inclusion list proposers are free to 00:12:02.279 --> 00:12:03.910 align:start position:0% inclusion list proposers are free to choose<00:12:02.600> whatever<00:12:02.920> inclusion<00:12:03.320> rule<00:12:03.600> that<00:12:03.760> they 00:12:03.910 --> 00:12:03.920 align:start position:0% choose whatever inclusion rule that they 00:12:03.920 --> 00:12:05.350 align:start position:0% choose whatever inclusion rule that they like<00:12:04.160> so<00:12:04.320> they're<00:12:04.480> free<00:12:04.680> to<00:12:04.839> construct<00:12:05.240> their 00:12:05.350 --> 00:12:05.360 align:start position:0% like so they're free to construct their 00:12:05.360 --> 00:12:07.350 align:start position:0% like so they're free to construct their inclusion<00:12:05.800> list<00:12:06.240> however<00:12:06.480> they<00:12:06.639> like<00:12:07.160> and 00:12:07.350 --> 00:12:07.360 align:start position:0% inclusion list however they like and 00:12:07.360 --> 00:12:11.870 align:start position:0% inclusion list however they like and clients<00:12:07.720> can<00:12:07.880> be<00:12:08.720> um<00:12:09.120> an<00:12:09.320> agent<00:12:09.680> for<00:12:10.399> them<00:12:11.399> so 00:12:11.870 --> 00:12:11.880 align:start position:0% clients can be um an agent for them so 00:12:11.880 --> 00:12:13.990 align:start position:0% clients can be um an agent for them so potentially<00:12:12.360> one<00:12:12.600> client<00:12:12.959> prefers<00:12:13.800> uh<00:12:13.880> the 00:12:13.990 --> 00:12:14.000 align:start position:0% potentially one client prefers uh the 00:12:14.000 --> 00:12:15.870 align:start position:0% potentially one client prefers uh the way<00:12:14.120> of<00:12:14.240> creating<00:12:14.639> inclusionist<00:12:15.279> By<00:12:15.480> Priority 00:12:15.870 --> 00:12:15.880 align:start position:0% way of creating inclusionist By Priority 00:12:15.880 --> 00:12:19.150 align:start position:0% way of creating inclusionist By Priority fee<00:12:16.680> others<00:12:17.040> may<00:12:17.519> prefer<00:12:17.880> to<00:12:18.480> make<00:12:18.760> incl 00:12:19.150 --> 00:12:19.160 align:start position:0% fee others may prefer to make incl 00:12:19.160 --> 00:12:20.750 align:start position:0% fee others may prefer to make incl inclusion<00:12:19.560> list<00:12:19.839> based<00:12:20.079> on<00:12:20.320> how<00:12:20.480> long 00:12:20.750 --> 00:12:20.760 align:start position:0% inclusion list based on how long 00:12:20.760 --> 00:12:21.990 align:start position:0% inclusion list based on how long transactions<00:12:21.240> have<00:12:21.399> been<00:12:21.519> pending<00:12:21.800> in<00:12:21.880> the 00:12:21.990 --> 00:12:22.000 align:start position:0% transactions have been pending in the 00:12:22.000 --> 00:12:24.750 align:start position:0% transactions have been pending in the mle<00:12:23.000> and<00:12:23.240> others<00:12:23.680> might<00:12:23.959> use<00:12:24.240> some<00:12:24.399> sort<00:12:24.600> of 00:12:24.750 --> 00:12:24.760 align:start position:0% mle and others might use some sort of 00:12:24.760 --> 00:12:26.350 align:start position:0% mle and others might use some sort of puristic<00:12:25.399> that<00:12:25.600> they<00:12:25.760> think<00:12:25.959> is<00:12:26.120> most 00:12:26.350 --> 00:12:26.360 align:start position:0% puristic that they think is most 00:12:26.360 --> 00:12:28.509 align:start position:0% puristic that they think is most valuable<00:12:26.720> to<00:12:26.880> create<00:12:27.160> inclusion<00:12:27.600> list<00:12:28.360> if 00:12:28.509 --> 00:12:28.519 align:start position:0% valuable to create inclusion list if 00:12:28.519 --> 00:12:30.150 align:start position:0% valuable to create inclusion list if people<00:12:28.720> create<00:12:29.160> inclusionist<00:12:29.639> in<00:12:29.800> various 00:12:30.150 --> 00:12:30.160 align:start position:0% people create inclusionist in various 00:12:30.160 --> 00:12:31.629 align:start position:0% people create inclusionist in various different<00:12:30.480> ways<00:12:30.760> it's<00:12:30.920> more<00:12:31.279> difficult<00:12:31.440> to 00:12:31.629 --> 00:12:31.639 align:start position:0% different ways it's more difficult to 00:12:31.639 --> 00:12:34.110 align:start position:0% different ways it's more difficult to attack<00:12:32.000> them<00:12:32.680> so<00:12:32.920> if<00:12:33.160> for<00:12:33.320> example<00:12:33.639> one<00:12:33.800> client 00:12:34.110 --> 00:12:34.120 align:start position:0% attack them so if for example one client 00:12:34.120 --> 00:12:36.230 align:start position:0% attack them so if for example one client incluses<00:12:34.959> inclusionist<00:12:35.600> mechanism<00:12:36.079> that 00:12:36.230 --> 00:12:36.240 align:start position:0% incluses inclusionist mechanism that 00:12:36.240 --> 00:12:38.949 align:start position:0% incluses inclusionist mechanism that says<00:12:36.800> I<00:12:36.920> want<00:12:37.160> to<00:12:37.639> make<00:12:37.880> my<00:12:38.079> list<00:12:38.399> based<00:12:38.600> on<00:12:38.800> how 00:12:38.949 --> 00:12:38.959 align:start position:0% says I want to make my list based on how 00:12:38.959 --> 00:12:40.990 align:start position:0% says I want to make my list based on how long<00:12:39.199> transactions<00:12:39.720> have<00:12:39.839> been<00:12:40.000> in<00:12:40.079> a<00:12:40.199> mempo 00:12:40.990 --> 00:12:41.000 align:start position:0% long transactions have been in a mempo 00:12:41.000 --> 00:12:43.069 align:start position:0% long transactions have been in a mempo uh<00:12:41.120> just<00:12:41.279> ordered<00:12:42.160> youd<00:12:42.360> need<00:12:42.519> to<00:12:42.639> flood<00:12:43.000> the 00:12:43.069 --> 00:12:43.079 align:start position:0% uh just ordered youd need to flood the 00:12:43.079 --> 00:12:45.829 align:start position:0% uh just ordered youd need to flood the mempo<00:12:43.560> long<00:12:43.920> before<00:12:44.240> that's<00:12:45.000> uh<00:12:45.360> long<00:12:45.639> before 00:12:45.829 --> 00:12:45.839 align:start position:0% mempo long before that's uh long before 00:12:45.839 --> 00:12:47.670 align:start position:0% mempo long before that's uh long before your<00:12:46.000> slot<00:12:46.639> making<00:12:46.880> it<00:12:47.040> potentially<00:12:47.360> a<00:12:47.440> lot 00:12:47.670 --> 00:12:47.680 align:start position:0% your slot making it potentially a lot 00:12:47.680 --> 00:12:49.230 align:start position:0% your slot making it potentially a lot harder<00:12:48.440> uh<00:12:48.519> to<00:12:48.680> know<00:12:48.839> that<00:12:48.959> you<00:12:49.040> can 00:12:49.230 --> 00:12:49.240 align:start position:0% harder uh to know that you can 00:12:49.240 --> 00:12:52.030 align:start position:0% harder uh to know that you can invalidate<00:12:49.959> them<00:12:50.959> so<00:12:51.199> this<00:12:51.279> is<00:12:51.480> really<00:12:51.920> a 00:12:52.030 --> 00:12:52.040 align:start position:0% invalidate them so this is really a 00:12:52.040 --> 00:12:53.710 align:start position:0% invalidate them so this is really a defense<00:12:52.320> and<00:12:52.480> debt<00:12:52.680> strategy<00:12:53.480> uh<00:12:53.600> it's 00:12:53.710 --> 00:12:53.720 align:start position:0% defense and debt strategy uh it's 00:12:53.720 --> 00:12:55.590 align:start position:0% defense and debt strategy uh it's unlikely<00:12:54.160> that<00:12:54.320> this<00:12:54.440> will<00:12:54.639> happen<00:12:54.959> the<00:12:55.120> G<00:12:55.440> is 00:12:55.590 --> 00:12:55.600 align:start position:0% unlikely that this will happen the G is 00:12:55.600 --> 00:12:58.030 align:start position:0% unlikely that this will happen the G is quite<00:12:55.800> limited<00:12:56.519> uh<00:12:56.639> but<00:12:56.760> even<00:12:57.040> then<00:12:57.800> uh<00:12:57.880> we're 00:12:58.030 --> 00:12:58.040 align:start position:0% quite limited uh but even then uh we're 00:12:58.040 --> 00:13:00.790 align:start position:0% quite limited uh but even then uh we're trying<00:12:58.240> to<00:12:58.440> prevent<00:12:58.720> it 00:13:00.790 --> 00:13:00.800 align:start position:0% trying to prevent it 00:13:00.800 --> 00:13:03.110 align:start position:0% trying to prevent it so<00:13:01.040> then<00:13:01.920> um<00:13:02.040> you<00:13:02.160> could<00:13:02.320> think<00:13:02.519> of<00:13:02.720> commitment 00:13:03.110 --> 00:13:03.120 align:start position:0% so then um you could think of commitment 00:13:03.120 --> 00:13:04.949 align:start position:0% so then um you could think of commitment ATT<00:13:03.320> taxs<00:13:03.720> so<00:13:03.880> an<00:13:04.000> inclusion<00:13:04.399> list<00:13:04.639> is<00:13:04.800> some 00:13:04.949 --> 00:13:04.959 align:start position:0% ATT taxs so an inclusion list is some 00:13:04.959 --> 00:13:06.990 align:start position:0% ATT taxs so an inclusion list is some way<00:13:05.120> to<00:13:05.440> constrain<00:13:06.079> the<00:13:06.240> value<00:13:06.519> that<00:13:06.680> a<00:13:06.800> block 00:13:06.990 --> 00:13:07.000 align:start position:0% way to constrain the value that a block 00:13:07.000 --> 00:13:09.590 align:start position:0% way to constrain the value that a block producer<00:13:07.399> could<00:13:07.959> um<00:13:08.160> extract<00:13:08.920> so<00:13:09.199> inclusion 00:13:09.590 --> 00:13:09.600 align:start position:0% producer could um extract so inclusion 00:13:09.600 --> 00:13:12.750 align:start position:0% producer could um extract so inclusion list<00:13:09.800> Committee<00:13:10.120> Member<00:13:10.519> could<00:13:10.800> say<00:13:11.800> um<00:13:12.480> if 00:13:12.750 --> 00:13:12.760 align:start position:0% list Committee Member could say um if 00:13:12.760 --> 00:13:14.590 align:start position:0% list Committee Member could say um if you<00:13:13.000> pay<00:13:13.240> me<00:13:13.560> then<00:13:13.720> I<00:13:13.880> include<00:13:14.240> something<00:13:14.480> in 00:13:14.590 --> 00:13:14.600 align:start position:0% you pay me then I include something in 00:13:14.600 --> 00:13:16.629 align:start position:0% you pay me then I include something in this<00:13:14.720> block<00:13:15.320> or<00:13:15.519> if<00:13:15.600> you<00:13:15.760> don't<00:13:16.040> pay<00:13:16.199> me<00:13:16.480> or 00:13:16.629 --> 00:13:16.639 align:start position:0% this block or if you don't pay me or 00:13:16.639 --> 00:13:18.269 align:start position:0% this block or if you don't pay me or sorry<00:13:16.920> if<00:13:17.000> you<00:13:17.120> pay<00:13:17.279> me<00:13:17.480> then<00:13:17.600> I<00:13:17.800> exclude 00:13:18.269 --> 00:13:18.279 align:start position:0% sorry if you pay me then I exclude 00:13:18.279 --> 00:13:20.110 align:start position:0% sorry if you pay me then I exclude something<00:13:18.560> from<00:13:18.720> my<00:13:18.880> inclusion<00:13:19.360> list<00:13:19.839> so<00:13:20.000> the 00:13:20.110 --> 00:13:20.120 align:start position:0% something from my inclusion list so the 00:13:20.120 --> 00:13:21.710 align:start position:0% something from my inclusion list so the latter<00:13:20.360> is<00:13:20.480> an<00:13:20.600> extortion<00:13:21.079> attack<00:13:21.360> the<00:13:21.480> first 00:13:21.710 --> 00:13:21.720 align:start position:0% latter is an extortion attack the first 00:13:21.720 --> 00:13:23.470 align:start position:0% latter is an extortion attack the first is<00:13:21.800> an<00:13:21.920> inclusion<00:13:22.399> attack<00:13:23.079> and<00:13:23.279> this<00:13:23.360> is 00:13:23.470 --> 00:13:23.480 align:start position:0% is an inclusion attack and this is 00:13:23.480 --> 00:13:26.189 align:start position:0% is an inclusion attack and this is mainly<00:13:23.760> a<00:13:23.920> worry<00:13:24.680> uh<00:13:24.760> if<00:13:24.920> there's<00:13:25.120> only<00:13:25.440> one<00:13:26.040> uh 00:13:26.189 --> 00:13:26.199 align:start position:0% mainly a worry uh if there's only one uh 00:13:26.199 --> 00:13:28.189 align:start position:0% mainly a worry uh if there's only one uh Committee<00:13:26.560> Member<00:13:27.160> we<00:13:27.399> try<00:13:27.600> to<00:13:27.760> prevent<00:13:28.040> this 00:13:28.189 --> 00:13:28.199 align:start position:0% Committee Member we try to prevent this 00:13:28.199 --> 00:13:29.350 align:start position:0% Committee Member we try to prevent this by<00:13:28.320> having<00:13:28.560> multiple<00:13:28.880> Comm<00:13:29.120> committee 00:13:29.350 --> 00:13:29.360 align:start position:0% by having multiple Comm committee 00:13:29.360 --> 00:13:32.230 align:start position:0% by having multiple Comm committee members<00:13:29.720> making<00:13:30.000> it<00:13:30.880> uh<00:13:31.079> economically<00:13:31.760> less 00:13:32.230 --> 00:13:32.240 align:start position:0% members making it uh economically less 00:13:32.240 --> 00:13:36.430 align:start position:0% members making it uh economically less less<00:13:32.720> important<00:13:33.720> uh<00:13:33.839> and<00:13:34.000> second<00:13:34.720> most<00:13:35.199> less 00:13:36.430 --> 00:13:36.440 align:start position:0% less important uh and second most less 00:13:36.440 --> 00:13:39.150 align:start position:0% less important uh and second most less likely<00:13:37.440> so<00:13:37.680> then<00:13:38.279> uh<00:13:38.399> taking<00:13:38.720> commitments 00:13:39.150 --> 00:13:39.160 align:start position:0% likely so then uh taking commitments 00:13:39.160 --> 00:13:40.590 align:start position:0% likely so then uh taking commitments attached<00:13:39.440> to<00:13:39.560> the<00:13:39.720> extreme<00:13:40.120> you<00:13:40.240> could<00:13:40.399> think 00:13:40.590 --> 00:13:40.600 align:start position:0% attached to the extreme you could think 00:13:40.600 --> 00:13:44.389 align:start position:0% attached to the extreme you could think of<00:13:40.720> fossil<00:13:41.320> as<00:13:42.199> uh<00:13:43.000> a<00:13:43.160> vehicle<00:13:43.480> for<00:13:43.680> meev<00:13:44.279> but 00:13:44.389 --> 00:13:44.399 align:start position:0% of fossil as uh a vehicle for meev but 00:13:44.399 --> 00:13:47.150 align:start position:0% of fossil as uh a vehicle for meev but we<00:13:44.560> try<00:13:44.720> to<00:13:45.079> prove<00:13:45.399> that<00:13:45.680> this<00:13:45.800> is<00:13:46.160> incorrect 00:13:47.150 --> 00:13:47.160 align:start position:0% we try to prove that this is incorrect 00:13:47.160 --> 00:13:48.829 align:start position:0% we try to prove that this is incorrect uh<00:13:47.240> we<00:13:47.360> do<00:13:47.519> this<00:13:47.680> via<00:13:47.920> a<00:13:48.079> concept<00:13:48.399> that<00:13:48.519> we<00:13:48.639> call 00:13:48.829 --> 00:13:48.839 align:start position:0% uh we do this via a concept that we call 00:13:48.839 --> 00:13:50.870 align:start position:0% uh we do this via a concept that we call unability<00:13:49.440> so<00:13:49.959> the<00:13:50.079> inclusion<00:13:50.480> list<00:13:50.639> cannot 00:13:50.870 --> 00:13:50.880 align:start position:0% unability so the inclusion list cannot 00:13:50.880 --> 00:13:53.670 align:start position:0% unability so the inclusion list cannot be<00:13:51.000> crowded<00:13:51.360> out<00:13:51.600> by<00:13:51.759> other<00:13:52.040> users<00:13:53.040> uh<00:13:53.440> than 00:13:53.670 --> 00:13:53.680 align:start position:0% be crowded out by other users uh than 00:13:53.680 --> 00:13:55.030 align:start position:0% be crowded out by other users uh than simply<00:13:54.040> providing<00:13:54.440> this<00:13:54.600> censorship 00:13:55.030 --> 00:13:55.040 align:start position:0% simply providing this censorship 00:13:55.040 --> 00:13:57.509 align:start position:0% simply providing this censorship resistance<00:13:55.680> property<00:13:56.680> so<00:13:56.920> we<00:13:57.040> don't<00:13:57.279> want 00:13:57.509 --> 00:13:57.519 align:start position:0% resistance property so we don't want 00:13:57.519 --> 00:13:59.389 align:start position:0% resistance property so we don't want inclusionist<00:13:58.160> proposers<00:13:58.639> to<00:13:58.759> sell<00:13:59.240> their 00:13:59.389 --> 00:13:59.399 align:start position:0% inclusionist proposers to sell their 00:13:59.399 --> 00:14:01.749 align:start position:0% inclusionist proposers to sell their rights<00:13:59.600> to<00:13:59.800> make<00:14:00.000> Invision<00:14:00.480> list<00:14:01.279> we<00:14:01.440> argue 00:14:01.749 --> 00:14:01.759 align:start position:0% rights to make Invision list we argue 00:14:01.759 --> 00:14:03.230 align:start position:0% rights to make Invision list we argue that<00:14:01.920> fossil<00:14:02.199> is<00:14:02.360> robust<00:14:02.759> against<00:14:03.079> these 00:14:03.230 --> 00:14:03.240 align:start position:0% that fossil is robust against these 00:14:03.240 --> 00:14:05.470 align:start position:0% that fossil is robust against these sorts<00:14:03.519> of<00:14:03.959> Mev<00:14:04.240> boost<00:14:04.560> like<00:14:04.759> markets<00:14:05.199> that<00:14:05.320> you 00:14:05.470 --> 00:14:05.480 align:start position:0% sorts of Mev boost like markets that you 00:14:05.480 --> 00:14:08.629 align:start position:0% sorts of Mev boost like markets that you might<00:14:05.720> think<00:14:06.440> uh<00:14:06.639> arise<00:14:07.199> if<00:14:07.759> um<00:14:08.240> if<00:14:08.440> if<00:14:08.519> you 00:14:08.629 --> 00:14:08.639 align:start position:0% might think uh arise if um if if you 00:14:08.639 --> 00:14:11.069 align:start position:0% might think uh arise if um if if you would<00:14:08.839> believe<00:14:09.160> that<00:14:09.920> um<00:14:10.399> it's<00:14:10.600> valuable<00:14:10.959> to 00:14:11.069 --> 00:14:11.079 align:start position:0% would believe that um it's valuable to 00:14:11.079 --> 00:14:13.509 align:start position:0% would believe that um it's valuable to sell<00:14:11.399> inclusionist<00:14:11.959> proposing<00:14:12.360> rates<00:14:13.160> we<00:14:13.279> say 00:14:13.509 --> 00:14:13.519 align:start position:0% sell inclusionist proposing rates we say 00:14:13.519 --> 00:14:15.829 align:start position:0% sell inclusionist proposing rates we say that<00:14:13.680> fossil<00:14:14.079> is<00:14:14.279> not<00:14:14.839> very<00:14:15.079> useful<00:14:15.399> for<00:14:15.639> this 00:14:15.829 --> 00:14:15.839 align:start position:0% that fossil is not very useful for this 00:14:15.839 --> 00:14:17.430 align:start position:0% that fossil is not very useful for this because<00:14:16.040> there<00:14:16.120> are<00:14:16.279> no<00:14:16.399> ordering<00:14:16.880> guarantees 00:14:17.430 --> 00:14:17.440 align:start position:0% because there are no ordering guarantees 00:14:17.440 --> 00:14:19.110 align:start position:0% because there are no ordering guarantees inclusionist<00:14:18.040> doesn't<00:14:18.360> tell<00:14:18.600> you<00:14:18.800> where<00:14:19.000> in 00:14:19.110 --> 00:14:19.120 align:start position:0% inclusionist doesn't tell you where in 00:14:19.120 --> 00:14:21.150 align:start position:0% inclusionist doesn't tell you where in the<00:14:19.240> block<00:14:19.480> your<00:14:19.639> transaction<00:14:20.040> lands<00:14:21.040> there 00:14:21.150 --> 00:14:21.160 align:start position:0% the block your transaction lands there 00:14:21.160 --> 00:14:22.829 align:start position:0% the block your transaction lands there is<00:14:21.320> no<00:14:21.519> private<00:14:21.800> order<00:14:22.040> flow<00:14:22.360> possible 00:14:22.829 --> 00:14:22.839 align:start position:0% is no private order flow possible 00:14:22.839 --> 00:14:24.629 align:start position:0% is no private order flow possible because<00:14:23.240> any<00:14:23.399> inclusion<00:14:23.880> list<00:14:24.079> is<00:14:24.240> publicly 00:14:24.629 --> 00:14:24.639 align:start position:0% because any inclusion list is publicly 00:14:24.639 --> 00:14:26.710 align:start position:0% because any inclusion list is publicly propagated<00:14:25.160> over<00:14:25.320> the<00:14:25.480> network<00:14:26.320> in<00:14:26.399> order<00:14:26.600> for 00:14:26.710 --> 00:14:26.720 align:start position:0% propagated over the network in order for 00:14:26.720 --> 00:14:29.189 align:start position:0% propagated over the network in order for it<00:14:26.839> to<00:14:26.920> be<00:14:27.480> enforced<00:14:28.480> there<00:14:28.560> are<00:14:28.680> multiple 00:14:29.189 --> 00:14:29.199 align:start position:0% it to be enforced there are multiple 00:14:29.199 --> 00:14:30.749 align:start position:0% it to be enforced there are multiple inclusionist<00:14:29.720> proposal<00:14:30.240> which<00:14:30.399> prevents 00:14:30.749 --> 00:14:30.759 align:start position:0% inclusionist proposal which prevents 00:14:30.759 --> 00:14:32.150 align:start position:0% inclusionist proposal which prevents some<00:14:30.880> of<00:14:31.000> the<00:14:31.120> inclusion<00:14:31.519> and<00:14:31.720> extortion 00:14:32.150 --> 00:14:32.160 align:start position:0% some of the inclusion and extortion 00:14:32.160 --> 00:14:34.470 align:start position:0% some of the inclusion and extortion attacks<00:14:32.480> that<00:14:32.600> we<00:14:32.800> talked<00:14:33.079> about<00:14:33.360> briefly<00:14:34.360> uh 00:14:34.470 --> 00:14:34.480 align:start position:0% attacks that we talked about briefly uh 00:14:34.480 --> 00:14:36.430 align:start position:0% attacks that we talked about briefly uh and<00:14:34.600> the<00:14:34.720> inclusionist<00:14:35.399> created<00:14:35.759> 3<00:14:36.000> seconds 00:14:36.430 --> 00:14:36.440 align:start position:0% and the inclusionist created 3 seconds 00:14:36.440 --> 00:14:37.910 align:start position:0% and the inclusionist created 3 seconds before<00:14:36.680> the<00:14:36.800> block<00:14:37.079> producer<00:14:37.399> acts<00:14:37.680> so<00:14:37.839> the 00:14:37.910 --> 00:14:37.920 align:start position:0% before the block producer acts so the 00:14:37.920 --> 00:14:39.310 align:start position:0% before the block producer acts so the block<00:14:38.160> producer<00:14:38.480> has<00:14:38.639> more<00:14:38.880> information 00:14:39.310 --> 00:14:39.320 align:start position:0% block producer has more information 00:14:39.320 --> 00:14:40.910 align:start position:0% block producer has more information about<00:14:39.600> the<00:14:39.759> external<00:14:40.120> states<00:14:40.399> of<00:14:40.519> the<00:14:40.600> world 00:14:40.910 --> 00:14:40.920 align:start position:0% about the external states of the world 00:14:40.920 --> 00:14:42.629 align:start position:0% about the external states of the world than<00:14:41.160> those<00:14:41.480> who<00:14:41.600> make<00:14:41.800> the<00:14:41.920> inclusionist 00:14:42.629 --> 00:14:42.639 align:start position:0% than those who make the inclusionist 00:14:42.639 --> 00:14:44.910 align:start position:0% than those who make the inclusionist have<00:14:43.519> and<00:14:43.639> this<00:14:43.759> means<00:14:44.040> that<00:14:44.199> no<00:14:44.440> individual 00:14:44.910 --> 00:14:44.920 align:start position:0% have and this means that no individual 00:14:44.920 --> 00:14:46.990 align:start position:0% have and this means that no individual inclusionist<00:14:45.519> proposer<00:14:46.040> has<00:14:46.199> the<00:14:46.639> right<00:14:46.800> to 00:14:46.990 --> 00:14:47.000 align:start position:0% inclusionist proposer has the right to 00:14:47.000 --> 00:14:49.189 align:start position:0% inclusionist proposer has the right to include<00:14:47.519> order<00:14:47.920> or<00:14:48.160> exclude<00:14:48.600> transactions 00:14:49.189 --> 00:14:49.199 align:start position:0% include order or exclude transactions 00:14:49.199 --> 00:14:50.749 align:start position:0% include order or exclude transactions which<00:14:49.320> is<00:14:49.480> like<00:14:49.639> the<00:14:49.839> canonical<00:14:50.360> definition 00:14:50.749 --> 00:14:50.759 align:start position:0% which is like the canonical definition 00:14:50.759 --> 00:14:51.470 align:start position:0% which is like the canonical definition of 00:14:51.470 --> 00:14:51.480 align:start position:0% of 00:14:51.480 --> 00:14:54.749 align:start position:0% of me<00:14:52.480> so<00:14:52.680> fosil<00:14:53.160> is<00:14:53.600> specifically<00:14:54.160> designed<00:14:54.600> to 00:14:54.749 --> 00:14:54.759 align:start position:0% me so fosil is specifically designed to 00:14:54.759 --> 00:14:56.949 align:start position:0% me so fosil is specifically designed to be<00:14:55.040> as<00:14:55.199> robust<00:14:55.600> as<00:14:55.759> possible<00:14:56.240> against<00:14:56.519> meev 00:14:56.949 --> 00:14:56.959 align:start position:0% be as robust as possible against meev 00:14:56.959 --> 00:15:00.870 align:start position:0% be as robust as possible against meev markets<00:14:57.360> for<00:14:57.600> inclusionist<00:14:58.199> proposing<00:14:58.639> rats 00:15:00.870 --> 00:15:00.880 align:start position:0% markets for inclusionist proposing rats 00:15:00.880 --> 00:15:03.990 align:start position:0% markets for inclusionist proposing rats second<00:15:01.240> is<00:15:01.440> extendability<00:15:01.920> and<00:15:02.920> here<00:15:03.680> uh<00:15:03.839> we 00:15:03.990 --> 00:15:04.000 align:start position:0% second is extendability and here uh we 00:15:04.000 --> 00:15:06.430 align:start position:0% second is extendability and here uh we argue<00:15:04.320> that<00:15:04.440> foso<00:15:04.920> is<00:15:05.639> a<00:15:05.800> great<00:15:06.000> step<00:15:06.199> in<00:15:06.320> the 00:15:06.430 --> 00:15:06.440 align:start position:0% argue that foso is a great step in the 00:15:06.440 --> 00:15:08.110 align:start position:0% argue that foso is a great step in the right<00:15:06.600> direction<00:15:07.040> we<00:15:07.160> feel<00:15:07.440> that<00:15:07.639> it's<00:15:07.839> very 00:15:08.110 --> 00:15:08.120 align:start position:0% right direction we feel that it's very 00:15:08.120 --> 00:15:09.470 align:start position:0% right direction we feel that it's very necessary<00:15:08.560> to<00:15:08.720> have<00:15:08.959> some<00:15:09.160> form<00:15:09.320> of 00:15:09.470 --> 00:15:09.480 align:start position:0% necessary to have some form of 00:15:09.480 --> 00:15:11.069 align:start position:0% necessary to have some form of inclusionist<00:15:10.160> today<00:15:10.560> since<00:15:10.720> there<00:15:10.800> are<00:15:10.920> only 00:15:11.069 --> 00:15:11.079 align:start position:0% inclusionist today since there are only 00:15:11.079 --> 00:15:13.670 align:start position:0% inclusionist today since there are only two<00:15:11.440> Builders<00:15:12.440> uh<00:15:12.600> and<00:15:12.759> we<00:15:12.839> see<00:15:13.040> that<00:15:13.199> fos<00:15:13.560> of 00:15:13.670 --> 00:15:13.680 align:start position:0% two Builders uh and we see that fos of 00:15:13.680 --> 00:15:16.030 align:start position:0% two Builders uh and we see that fos of recurring<00:15:14.120> architecture<00:15:14.720> in<00:15:14.920> different<00:15:15.880> uh 00:15:16.030 --> 00:15:16.040 align:start position:0% recurring architecture in different uh 00:15:16.040 --> 00:15:17.790 align:start position:0% recurring architecture in different uh products<00:15:16.399> that<00:15:16.519> we're<00:15:16.680> trying<00:15:17.240> that<00:15:17.519> I<00:15:17.639> guess 00:15:17.790 --> 00:15:17.800 align:start position:0% products that we're trying that I guess 00:15:17.800 --> 00:15:19.910 align:start position:0% products that we're trying that I guess not<00:15:17.920> products<00:15:18.519> uh<00:15:18.839> erps<00:15:19.320> that<00:15:19.399> we're<00:15:19.519> in 00:15:19.910 --> 00:15:19.920 align:start position:0% not products uh erps that we're in 00:15:19.920 --> 00:15:23.269 align:start position:0% not products uh erps that we're in imagining<00:15:20.920> um<00:15:21.839> and<00:15:22.240> so<00:15:22.639> here<00:15:22.800> I'll<00:15:23.040> present 00:15:23.269 --> 00:15:23.279 align:start position:0% imagining um and so here I'll present 00:15:23.279 --> 00:15:25.150 align:start position:0% imagining um and so here I'll present two<00:15:23.519> possible<00:15:23.959> extensions<00:15:24.720> you<00:15:24.800> shouldn't 00:15:25.150 --> 00:15:25.160 align:start position:0% two possible extensions you shouldn't 00:15:25.160 --> 00:15:26.749 align:start position:0% two possible extensions you shouldn't take<00:15:25.399> these<00:15:25.720> as<00:15:25.959> part<00:15:26.120> of<00:15:26.279> fossil<00:15:26.639> because 00:15:26.749 --> 00:15:26.759 align:start position:0% take these as part of fossil because 00:15:26.759 --> 00:15:28.350 align:start position:0% take these as part of fossil because they're<00:15:26.920> not<00:15:27.079> in<00:15:27.199> the<00:15:27.279> Erp<00:15:28.000> but<00:15:28.120> there<00:15:28.199> are 00:15:28.350 --> 00:15:28.360 align:start position:0% they're not in the Erp but there are 00:15:28.360 --> 00:15:29.710 align:start position:0% they're not in the Erp but there are things<00:15:28.560> that<00:15:28.680> could<00:15:28.800> be<00:15:29.000> built<00:15:29.160> on<00:15:29.319> fosil 00:15:29.710 --> 00:15:29.720 align:start position:0% things that could be built on fosil 00:15:29.720 --> 00:15:33.110 align:start position:0% things that could be built on fosil without<00:15:29.920> changing<00:15:30.279> the<00:15:30.399> underlying 00:15:33.110 --> 00:15:33.120 align:start position:0% without changing the underlying 00:15:33.120 --> 00:15:35.990 align:start position:0% without changing the underlying architecture<00:15:34.120> so<00:15:34.319> first<00:15:34.680> is<00:15:35.240> making<00:15:35.639> some 00:15:35.990 --> 00:15:36.000 align:start position:0% architecture so first is making some 00:15:36.000 --> 00:15:37.910 align:start position:0% architecture so first is making some transaction<00:15:36.480> fee<00:15:36.720> mechanism<00:15:37.199> to<00:15:37.360> incentivize 00:15:37.910 --> 00:15:37.920 align:start position:0% transaction fee mechanism to incentivize 00:15:37.920 --> 00:15:40.030 align:start position:0% transaction fee mechanism to incentivize sensorship<00:15:38.440> resistance<00:15:39.399> so<00:15:39.560> the<00:15:39.680> design 00:15:40.030 --> 00:15:40.040 align:start position:0% sensorship resistance so the design 00:15:40.040 --> 00:15:41.910 align:start position:0% sensorship resistance so the design philosophy<00:15:40.519> behind<00:15:40.759> fossil<00:15:41.160> is<00:15:41.279> to<00:15:41.440> boost<00:15:41.720> the 00:15:41.910 --> 00:15:41.920 align:start position:0% philosophy behind fossil is to boost the 00:15:41.920 --> 00:15:44.189 align:start position:0% philosophy behind fossil is to boost the value<00:15:42.399> or<00:15:42.600> boost<00:15:42.880> the<00:15:43.040> signal<00:15:43.519> of<00:15:43.759> those<00:15:44.000> that 00:15:44.189 --> 00:15:44.199 align:start position:0% value or boost the signal of those that 00:15:44.199 --> 00:15:45.790 align:start position:0% value or boost the signal of those that already<00:15:44.480> provide<00:15:44.800> sensor<00:15:45.240> resistance<00:15:45.600> to 00:15:45.790 --> 00:15:45.800 align:start position:0% already provide sensor resistance to 00:15:45.800 --> 00:15:48.309 align:start position:0% already provide sensor resistance to ethereum<00:15:46.800> uh<00:15:46.920> in<00:15:47.000> a<00:15:47.199> way<00:15:47.480> that's<00:15:47.839> doesn't<00:15:48.120> cost 00:15:48.309 --> 00:15:48.319 align:start position:0% ethereum uh in a way that's doesn't cost 00:15:48.319 --> 00:15:49.790 align:start position:0% ethereum uh in a way that's doesn't cost them<00:15:48.519> anything<00:15:48.920> but<00:15:49.079> it<00:15:49.160> doesn't<00:15:49.399> gain<00:15:49.600> them 00:15:49.790 --> 00:15:49.800 align:start position:0% them anything but it doesn't gain them 00:15:49.800 --> 00:15:52.269 align:start position:0% them anything but it doesn't gain them anything<00:15:50.120> either<00:15:51.000> potentially<00:15:51.560> for<00:15:51.720> some<00:15:51.920> use 00:15:52.269 --> 00:15:52.279 align:start position:0% anything either potentially for some use 00:15:52.279 --> 00:15:54.230 align:start position:0% anything either potentially for some use cases<00:15:52.639> you<00:15:52.759> want<00:15:53.480> these<00:15:53.680> inclusionist 00:15:54.230 --> 00:15:54.240 align:start position:0% cases you want these inclusionist 00:15:54.240 --> 00:15:55.829 align:start position:0% cases you want these inclusionist committee<00:15:54.519> members<00:15:54.800> to<00:15:55.000> actually<00:15:55.279> gain 00:15:55.829 --> 00:15:55.839 align:start position:0% committee members to actually gain 00:15:55.839 --> 00:15:59.150 align:start position:0% committee members to actually gain something<00:15:56.839> uh<00:15:57.079> from<00:15:57.480> from<00:15:57.759> providing<00:15:58.240> this 00:15:59.150 --> 00:15:59.160 align:start position:0% something uh from from providing this 00:15:59.160 --> 00:16:00.910 align:start position:0% something uh from from providing this resistance<00:15:59.600> service<00:16:00.399> and<00:16:00.560> what<00:16:00.639> you<00:16:00.759> could 00:16:00.910 --> 00:16:00.920 align:start position:0% resistance service and what you could 00:16:00.920 --> 00:16:03.790 align:start position:0% resistance service and what you could think<00:16:01.240> here<00:16:01.399> is<00:16:01.519> an<00:16:01.680> Erp<00:16:02.319> 1459<00:16:02.880> like<00:16:03.160> mechanism 00:16:03.790 --> 00:16:03.800 align:start position:0% think here is an Erp 1459 like mechanism 00:16:03.800 --> 00:16:06.350 align:start position:0% think here is an Erp 1459 like mechanism where<00:16:04.319> the<00:16:04.519> priority<00:16:05.000> fees<00:16:05.440> are<00:16:05.639> given<00:16:05.959> to 00:16:06.350 --> 00:16:06.360 align:start position:0% where the priority fees are given to 00:16:06.360 --> 00:16:09.430 align:start position:0% where the priority fees are given to those<00:16:06.600> who<00:16:06.800> create<00:16:07.160> the<00:16:07.279> inclusion<00:16:07.759> list<00:16:08.759> um 00:16:09.430 --> 00:16:09.440 align:start position:0% those who create the inclusion list um 00:16:09.440 --> 00:16:10.990 align:start position:0% those who create the inclusion list um potentially<00:16:09.920> subject<00:16:10.279> to<00:16:10.480> how<00:16:10.600> much<00:16:10.800> they 00:16:10.990 --> 00:16:11.000 align:start position:0% potentially subject to how much they 00:16:11.000 --> 00:16:13.069 align:start position:0% potentially subject to how much they contributed<00:16:11.519> to<00:16:12.079> individual<00:16:12.560> transactions 00:16:13.069 --> 00:16:13.079 align:start position:0% contributed to individual transactions 00:16:13.079 --> 00:16:14.069 align:start position:0% contributed to individual transactions being 00:16:14.069 --> 00:16:14.079 align:start position:0% being 00:16:14.079 --> 00:16:16.309 align:start position:0% being included<00:16:15.079> the<00:16:15.199> general<00:16:15.519> idea<00:16:15.759> is<00:16:15.880> to<00:16:16.000> make<00:16:16.120> it 00:16:16.309 --> 00:16:16.319 align:start position:0% included the general idea is to make it 00:16:16.319 --> 00:16:17.990 align:start position:0% included the general idea is to make it a<00:16:16.399> lot<00:16:16.560> more<00:16:16.759> expensive<00:16:17.199> to<00:16:17.360> sensor 00:16:17.990 --> 00:16:18.000 align:start position:0% a lot more expensive to sensor 00:16:18.000 --> 00:16:19.790 align:start position:0% a lot more expensive to sensor transactions<00:16:19.000> uh<00:16:19.079> you<00:16:19.199> could<00:16:19.319> do<00:16:19.480> this<00:16:19.600> via 00:16:19.790 --> 00:16:19.800 align:start position:0% transactions uh you could do this via 00:16:19.800 --> 00:16:21.230 align:start position:0% transactions uh you could do this via this<00:16:19.920> transaction<00:16:20.279> fee<00:16:20.560> mechanism<00:16:21.040> and<00:16:21.160> you 00:16:21.230 --> 00:16:21.240 align:start position:0% this transaction fee mechanism and you 00:16:21.240 --> 00:16:23.309 align:start position:0% this transaction fee mechanism and you could<00:16:21.399> also<00:16:21.680> change<00:16:22.000> the<00:16:22.120> way<00:16:22.319> that<00:16:22.680> tips<00:16:23.079> work 00:16:23.309 --> 00:16:23.319 align:start position:0% could also change the way that tips work 00:16:23.319 --> 00:16:24.749 align:start position:0% could also change the way that tips work in<00:16:23.480> ethereum<00:16:23.959> potentially<00:16:24.319> by<00:16:24.480> having 00:16:24.749 --> 00:16:24.759 align:start position:0% in ethereum potentially by having 00:16:24.759 --> 00:16:27.110 align:start position:0% in ethereum potentially by having separate<00:16:25.079> tips<00:16:25.440> for<00:16:26.199> uh<00:16:26.319> inclusion<00:16:26.759> list 00:16:27.110 --> 00:16:27.120 align:start position:0% separate tips for uh inclusion list 00:16:27.120 --> 00:16:29.189 align:start position:0% separate tips for uh inclusion list inclusion<00:16:27.680> and<00:16:27.800> block<00:16:28.079> inclusion<00:16:28.560> or<00:16:29.000> having 00:16:29.189 --> 00:16:29.199 align:start position:0% inclusion and block inclusion or having 00:16:29.199 --> 00:16:31.069 align:start position:0% inclusion and block inclusion or having a<00:16:29.560> conditional<00:16:30.360> uh<00:16:30.519> tip<00:16:30.800> that<00:16:30.880> was 00:16:31.069 --> 00:16:31.079 align:start position:0% a conditional uh tip that was 00:16:31.079 --> 00:16:34.949 align:start position:0% a conditional uh tip that was popularized<00:16:31.680> by<00:16:31.839> Elijah<00:16:32.240> Fox<00:16:32.639> Mann<00:16:33.279> and 00:16:34.949 --> 00:16:34.959 align:start position:0% popularized by Elijah Fox Mann and 00:16:34.959 --> 00:16:37.749 align:start position:0% popularized by Elijah Fox Mann and mpai<00:16:35.959> and<00:16:36.079> then<00:16:36.279> secondly<00:16:37.000> we're<00:16:37.199> looking<00:16:37.480> at 00:16:37.749 --> 00:16:37.759 align:start position:0% mpai and then secondly we're looking at 00:16:37.759 --> 00:16:41.430 align:start position:0% mpai and then secondly we're looking at fossil<00:16:38.160> for<00:16:38.399> blobes<00:16:39.079> so<00:16:39.360> Erp<00:16:40.079> 7805<00:16:41.040> currently 00:16:41.430 --> 00:16:41.440 align:start position:0% fossil for blobes so Erp 7805 currently 00:16:41.440 --> 00:16:43.309 align:start position:0% fossil for blobes so Erp 7805 currently doesn't<00:16:41.759> support<00:16:42.199> blobes<00:16:42.680> although<00:16:42.959> it<00:16:43.079> could 00:16:43.309 --> 00:16:43.319 align:start position:0% doesn't support blobes although it could 00:16:43.319 --> 00:16:46.069 align:start position:0% doesn't support blobes although it could with<00:16:43.880> some<00:16:44.079> small<00:16:44.360> changes<00:16:44.839> potentially<00:16:45.839> but 00:16:46.069 --> 00:16:46.079 align:start position:0% with some small changes potentially but 00:16:46.079 --> 00:16:48.069 align:start position:0% with some small changes potentially but then<00:16:46.600> uh<00:16:46.680> but<00:16:46.839> taking<00:16:47.040> it<00:16:47.279> a<00:16:47.399> step<00:16:47.639> further<00:16:47.959> and 00:16:48.069 --> 00:16:48.079 align:start position:0% then uh but taking it a step further and 00:16:48.079 --> 00:16:49.910 align:start position:0% then uh but taking it a step further and looking<00:16:48.319> at<00:16:48.440> full<00:16:48.720> data<00:16:49.000> availability 00:16:49.910 --> 00:16:49.920 align:start position:0% looking at full data availability 00:16:49.920 --> 00:16:52.870 align:start position:0% looking at full data availability sampling<00:16:50.920> um<00:16:51.120> enforcing<00:16:51.560> inclusion<00:16:51.959> is 00:16:52.870 --> 00:16:52.880 align:start position:0% sampling um enforcing inclusion is 00:16:52.880 --> 00:16:54.389 align:start position:0% sampling um enforcing inclusion is becomes<00:16:53.079> a<00:16:53.199> bit<00:16:53.319> more<00:16:53.720> difficult<00:16:54.120> because 00:16:54.389 --> 00:16:54.399 align:start position:0% becomes a bit more difficult because 00:16:54.399 --> 00:16:55.949 align:start position:0% becomes a bit more difficult because those<00:16:54.560> who<00:16:54.759> enforce<00:16:55.120> it<00:16:55.319> need<00:16:55.480> to<00:16:55.600> know<00:16:55.759> that 00:16:55.949 --> 00:16:55.959 align:start position:0% those who enforce it need to know that 00:16:55.959 --> 00:16:57.550 align:start position:0% those who enforce it need to know that all<00:16:56.079> of<00:16:56.160> the<00:16:56.319> data<00:16:56.600> was<00:16:56.759> indeed<00:16:57.040> available 00:16:57.550 --> 00:16:57.560 align:start position:0% all of the data was indeed available 00:16:57.560 --> 00:16:59.230 align:start position:0% all of the data was indeed available they<00:16:57.639> need<00:16:57.800> to<00:16:57.920> know<00:16:58.120> that<00:16:58.279> the<00:16:58.399> block<00:16:59.120> could 00:16:59.230 --> 00:16:59.240 align:start position:0% they need to know that the block could 00:16:59.240 --> 00:17:01.189 align:start position:0% they need to know that the block could have<00:16:59.360> included<00:16:59.759> all<00:16:59.839> of<00:17:00.000> these<00:17:00.199> transactions 00:17:01.189 --> 00:17:01.199 align:start position:0% have included all of these transactions 00:17:01.199 --> 00:17:03.030 align:start position:0% have included all of these transactions so<00:17:01.399> then<00:17:01.519> we<00:17:01.639> could<00:17:01.839> extend<00:17:02.120> fil<00:17:02.680> with<00:17:02.800> some 00:17:03.030 --> 00:17:03.040 align:start position:0% so then we could extend fil with some 00:17:03.040 --> 00:17:06.110 align:start position:0% so then we could extend fil with some extra<00:17:03.560> condition<00:17:03.959> where<00:17:04.360> the<00:17:04.720> testers<00:17:05.720> have<00:17:05.959> a 00:17:06.110 --> 00:17:06.120 align:start position:0% extra condition where the testers have a 00:17:06.120 --> 00:17:07.549 align:start position:0% extra condition where the testers have a good<00:17:06.319> view<00:17:06.600> of<00:17:06.760> whether<00:17:07.000> the<00:17:07.120> data<00:17:07.400> is 00:17:07.549 --> 00:17:07.559 align:start position:0% good view of whether the data is 00:17:07.559 --> 00:17:09.590 align:start position:0% good view of whether the data is available<00:17:07.880> or<00:17:08.039> not<00:17:08.319> to<00:17:08.520> again<00:17:08.919> prevent<00:17:09.280> split 00:17:09.590 --> 00:17:09.600 align:start position:0% available or not to again prevent split 00:17:09.600 --> 00:17:11.750 align:start position:0% available or not to again prevent split view<00:17:09.880> types<00:17:10.079> of<00:17:10.240> attach<00:17:11.039> the<00:17:11.160> important<00:17:11.559> thing 00:17:11.750 --> 00:17:11.760 align:start position:0% view types of attach the important thing 00:17:11.760 --> 00:17:13.750 align:start position:0% view types of attach the important thing here<00:17:11.959> is<00:17:12.079> that<00:17:12.319> this<00:17:12.760> fully<00:17:13.039> builds<00:17:13.400> upon<00:17:13.600> the 00:17:13.750 --> 00:17:13.760 align:start position:0% here is that this fully builds upon the 00:17:13.760 --> 00:17:15.309 align:start position:0% here is that this fully builds upon the architecture<00:17:14.280> that<00:17:14.400> we're<00:17:14.600> proposing<00:17:15.000> within 00:17:15.309 --> 00:17:15.319 align:start position:0% architecture that we're proposing within 00:17:15.319 --> 00:17:17.990 align:start position:0% architecture that we're proposing within fosil<00:17:16.319> um<00:17:16.439> so<00:17:16.600> fosil<00:17:16.959> is<00:17:17.079> very<00:17:17.199> future 00:17:17.990 --> 00:17:18.000 align:start position:0% fosil um so fosil is very future 00:17:18.000 --> 00:17:20.750 align:start position:0% fosil um so fosil is very future compatible<00:17:19.000> fil<00:17:19.400> architecture<00:17:19.959> is<00:17:20.199> basis<00:17:20.480> for 00:17:20.750 --> 00:17:20.760 align:start position:0% compatible fil architecture is basis for 00:17:20.760 --> 00:17:22.789 align:start position:0% compatible fil architecture is basis for many<00:17:21.000> more<00:17:21.240> extensions<00:17:22.120> these<00:17:22.280> are<00:17:22.439> just<00:17:22.559> two 00:17:22.789 --> 00:17:22.799 align:start position:0% many more extensions these are just two 00:17:22.799 --> 00:17:24.829 align:start position:0% many more extensions these are just two examples<00:17:23.280> but<00:17:23.400> you<00:17:23.520> could<00:17:23.720> go<00:17:24.240> crazy<00:17:24.600> with 00:17:24.829 --> 00:17:24.839 align:start position:0% examples but you could go crazy with 00:17:24.839 --> 00:17:26.270 align:start position:0% examples but you could go crazy with this<00:17:25.120> and<00:17:25.559> um<00:17:25.679> I<00:17:25.760> think<00:17:25.880> it's<00:17:26.000> a<00:17:26.120> very 00:17:26.270 --> 00:17:26.280 align:start position:0% this and um I think it's a very 00:17:26.280 --> 00:17:28.909 align:start position:0% this and um I think it's a very interesting<00:17:26.640> design<00:17:27.439> space<00:17:28.439> so<00:17:28.600> it's<00:17:28.679> a 00:17:28.909 --> 00:17:28.919 align:start position:0% interesting design space so it's a 00:17:28.919 --> 00:17:31.510 align:start position:0% interesting design space so it's a summarize<00:17:29.600> also<00:17:30.000> allows<00:17:30.320> 16<00:17:30.720> validators<00:17:31.320> to 00:17:31.510 --> 00:17:31.520 align:start position:0% summarize also allows 16 validators to 00:17:31.520 --> 00:17:32.950 align:start position:0% summarize also allows 16 validators to contribute<00:17:31.919> to<00:17:32.039> blood<00:17:32.280> construction<00:17:32.840> which 00:17:32.950 --> 00:17:32.960 align:start position:0% contribute to blood construction which 00:17:32.960 --> 00:17:34.789 align:start position:0% contribute to blood construction which is<00:17:33.120> currently<00:17:33.520> very<00:17:33.720> centralized<00:17:34.400> and<00:17:34.520> mostly 00:17:34.789 --> 00:17:34.799 align:start position:0% is currently very centralized and mostly 00:17:34.799 --> 00:17:37.070 align:start position:0% is currently very centralized and mostly in<00:17:34.880> the<00:17:34.960> hands<00:17:35.160> of<00:17:35.280> two<00:17:35.640> Builders<00:17:36.640> the<00:17:36.880> main 00:17:37.070 --> 00:17:37.080 align:start position:0% in the hands of two Builders the main 00:17:37.080 --> 00:17:38.549 align:start position:0% in the hands of two Builders the main goal<00:17:37.320> is<00:17:37.440> to<00:17:37.600> increase<00:17:38.000> the<00:17:38.120> censal 00:17:38.549 --> 00:17:38.559 align:start position:0% goal is to increase the censal 00:17:38.559 --> 00:17:40.870 align:start position:0% goal is to increase the censal resistance<00:17:38.919> of<00:17:39.080> ethereum<00:17:39.679> right<00:17:39.840> now<00:17:40.640> and<00:17:40.760> the 00:17:40.870 --> 00:17:40.880 align:start position:0% resistance of ethereum right now and the 00:17:40.880 --> 00:17:43.750 align:start position:0% resistance of ethereum right now and the cyles<00:17:41.520> are<00:17:41.720> to<00:17:42.160> provide<00:17:42.520> robustness<00:17:43.360> against 00:17:43.750 --> 00:17:43.760 align:start position:0% cyles are to provide robustness against 00:17:43.760 --> 00:17:45.710 align:start position:0% cyles are to provide robustness against consensus<00:17:44.240> layer<00:17:44.679> and<00:17:44.960> execution<00:17:45.400> layer 00:17:45.710 --> 00:17:45.720 align:start position:0% consensus layer and execution layer 00:17:45.720 --> 00:17:47.470 align:start position:0% consensus layer and execution layer attacks<00:17:46.160> consensus<00:17:46.600> layer<00:17:46.840> attacks<00:17:47.200> again 00:17:47.470 --> 00:17:47.480 align:start position:0% attacks consensus layer attacks again 00:17:47.480 --> 00:17:49.870 align:start position:0% attacks consensus layer attacks again being<00:17:47.760> the<00:17:48.240> equivocation<00:17:48.919> split<00:17:49.240> view 00:17:49.870 --> 00:17:49.880 align:start position:0% being the equivocation split view 00:17:49.880 --> 00:17:51.710 align:start position:0% being the equivocation split view execution<00:17:50.320> layer<00:17:50.640> attacks<00:17:51.000> being<00:17:51.480> being 00:17:51.710 --> 00:17:51.720 align:start position:0% execution layer attacks being being 00:17:51.720 --> 00:17:54.350 align:start position:0% execution layer attacks being being crowded<00:17:52.160> out<00:17:52.400> by<00:17:52.520> me<00:17:53.039> types<00:17:53.240> of<00:17:53.400> markets<00:17:54.240> and 00:17:54.350 --> 00:17:54.360 align:start position:0% crowded out by me types of markets and 00:17:54.360 --> 00:17:56.110 align:start position:0% crowded out by me types of markets and the<00:17:54.520> second<00:17:54.799> side<00:17:55.039> goal<00:17:55.240> would<00:17:55.400> be<00:17:55.559> to<00:17:55.679> be<00:17:55.880> very 00:17:56.110 --> 00:17:56.120 align:start position:0% the second side goal would be to be very 00:17:56.120 --> 00:17:58.149 align:start position:0% the second side goal would be to be very extendable<00:17:56.760> so<00:17:56.880> we<00:17:56.960> want<00:17:57.200> fossil<00:17:57.880> to<00:17:58.000> be 00:17:58.149 --> 00:17:58.159 align:start position:0% extendable so we want fossil to be 00:17:58.159 --> 00:18:00.390 align:start position:0% extendable so we want fossil to be future<00:17:58.520> compat<00:17:58.840> ible<00:17:59.600> and<00:17:59.720> unlock<00:18:00.039> a<00:18:00.200> new 00:18:00.390 --> 00:18:00.400 align:start position:0% future compat ible and unlock a new 00:18:00.400 --> 00:18:01.750 align:start position:0% future compat ible and unlock a new field<00:18:00.640> for<00:18:00.840> ethereum<00:18:01.240> that<00:18:01.320> we<00:18:01.400> cannot 00:18:01.750 --> 00:18:01.760 align:start position:0% field for ethereum that we cannot 00:18:01.760 --> 00:18:05.029 align:start position:0% field for ethereum that we cannot imagine<00:18:02.480> now<00:18:03.480> so<00:18:03.640> the<00:18:03.799> next<00:18:04.000> steps<00:18:04.280> are<00:18:04.640> Erp 00:18:05.029 --> 00:18:05.039 align:start position:0% imagine now so the next steps are Erp 00:18:05.039 --> 00:18:07.430 align:start position:0% imagine now so the next steps are Erp 7805<00:18:05.960> is<00:18:06.120> available<00:18:06.799> if<00:18:06.880> you're<00:18:07.039> interested 00:18:07.430 --> 00:18:07.440 align:start position:0% 7805 is available if you're interested 00:18:07.440 --> 00:18:09.909 align:start position:0% 7805 is available if you're interested please<00:18:07.640> scan<00:18:07.880> the<00:18:08.039> QR<00:18:08.440> code<00:18:09.240> uh<00:18:09.320> and<00:18:09.480> v<00:18:09.720> through 00:18:09.909 --> 00:18:09.919 align:start position:0% please scan the QR code uh and v through 00:18:09.919 --> 00:18:11.549 align:start position:0% please scan the QR code uh and v through it<00:18:10.480> we're<00:18:10.679> trying<00:18:10.880> to<00:18:11.000> move<00:18:11.200> towards 00:18:11.549 --> 00:18:11.559 align:start position:0% it we're trying to move towards 00:18:11.559 --> 00:18:13.990 align:start position:0% it we're trying to move towards implementation<00:18:12.120> in<00:18:12.320> clients<00:18:13.240> and<00:18:13.440> my<00:18:13.600> call<00:18:13.840> to 00:18:13.990 --> 00:18:14.000 align:start position:0% implementation in clients and my call to 00:18:14.000 --> 00:18:15.830 align:start position:0% implementation in clients and my call to action<00:18:14.240> to<00:18:14.400> you<00:18:14.600> is<00:18:14.799> that<00:18:15.280> please<00:18:15.520> reach<00:18:15.720> out 00:18:15.830 --> 00:18:15.840 align:start position:0% action to you is that please reach out 00:18:15.840 --> 00:18:17.230 align:start position:0% action to you is that please reach out to<00:18:16.000> us<00:18:16.200> if<00:18:16.280> you<00:18:16.360> have<00:18:16.520> any<00:18:16.720> questions<00:18:17.080> about 00:18:17.230 --> 00:18:17.240 align:start position:0% to us if you have any questions about 00:18:17.240 --> 00:18:19.549 align:start position:0% to us if you have any questions about fil<00:18:18.159> if<00:18:18.280> you<00:18:18.440> think<00:18:18.720> that<00:18:18.840> fosil<00:18:19.280> could<00:18:19.440> be 00:18:19.549 --> 00:18:19.559 align:start position:0% fil if you think that fosil could be 00:18:19.559 --> 00:18:21.950 align:start position:0% fil if you think that fosil could be used<00:18:19.799> as<00:18:19.919> a<00:18:20.039> vehicle<00:18:20.360> for<00:18:20.520> me<00:18:21.080> so<00:18:21.600> this<00:18:21.720> is<00:18:21.840> the 00:18:21.950 --> 00:18:21.960 align:start position:0% used as a vehicle for me so this is the 00:18:21.960 --> 00:18:23.590 align:start position:0% used as a vehicle for me so this is the thing<00:18:22.120> that<00:18:22.240> we're<00:18:22.400> explicitly<00:18:22.880> designing 00:18:23.590 --> 00:18:23.600 align:start position:0% thing that we're explicitly designing 00:18:23.600 --> 00:18:26.310 align:start position:0% thing that we're explicitly designing against<00:18:24.600> uh<00:18:24.799> and<00:18:25.039> if<00:18:25.120> you<00:18:25.280> think<00:18:25.640> that<00:18:26.080> you'd 00:18:26.310 --> 00:18:26.320 align:start position:0% against uh and if you think that you'd 00:18:26.320 --> 00:18:28.549 align:start position:0% against uh and if you think that you'd like<00:18:26.480> to<00:18:26.600> use<00:18:26.840> fossil<00:18:27.640> uh<00:18:27.720> on<00:18:27.880> your<00:18:28.080> layer<00:18:28.360> to 00:18:28.549 --> 00:18:28.559 align:start position:0% like to use fossil uh on your layer to 00:18:28.559 --> 00:18:30.750 align:start position:0% like to use fossil uh on your layer to to<00:18:28.840> provide<00:18:29.080> censorship<00:18:29.520> resistance 00:18:30.750 --> 00:18:30.760 align:start position:0% to provide censorship resistance 00:18:30.760 --> 00:18:33.549 align:start position:0% to provide censorship resistance there<00:18:31.760> so<00:18:31.919> that<00:18:32.039> was<00:18:32.200> it<00:18:32.440> thank<00:18:32.600> you<00:18:32.760> very<00:18:32.960> much 00:18:33.549 --> 00:18:33.559 align:start position:0% there so that was it thank you very much 00:18:33.559 --> 00:18:35.470 align:start position:0% there so that was it thank you very much uh<00:18:33.679> and<00:18:33.760> I'll<00:18:33.919> be<00:18:34.039> open<00:18:34.200> to<00:18:34.360> any 00:18:35.470 --> 00:18:35.480 align:start position:0% uh and I'll be open to any 00:18:35.480 --> 00:18:38.630 align:start position:0% uh and I'll be open to any [Music] 00:18:38.630 --> 00:18:38.640 align:start position:0% [Music] 00:18:38.640 --> 00:18:41.190 align:start position:0% [Music] questions<00:18:39.640> thank<00:18:39.799> you<00:18:40.120> and<00:18:40.520> uh<00:18:40.640> also<00:18:40.960> big 00:18:41.190 --> 00:18:41.200 align:start position:0% questions thank you and uh also big 00:18:41.200 --> 00:18:43.390 align:start position:0% questions thank you and uh also big apologies<00:18:41.720> for<00:18:42.360> um<00:18:42.520> calling<00:18:42.799> out<00:18:42.960> the<00:18:43.159> wrong 00:18:43.390 --> 00:18:43.400 align:start position:0% apologies for um calling out the wrong 00:18:43.400 --> 00:18:45.230 align:start position:0% apologies for um calling out the wrong name<00:18:43.799> um<00:18:43.960> so<00:18:44.120> this<00:18:44.240> is<00:18:44.360> Julian<00:18:44.760> marah<00:18:45.080> from 00:18:45.230 --> 00:18:45.240 align:start position:0% name um so this is Julian marah from 00:18:45.240 --> 00:18:48.029 align:start position:0% name um so this is Julian marah from robot<00:18:45.640> incentive<00:18:46.039> group<00:18:46.280> at<00:18:46.440> the<00:18:46.760> EF<00:18:47.760> um<00:18:47.880> so 00:18:48.029 --> 00:18:48.039 align:start position:0% robot incentive group at the EF um so 00:18:48.039 --> 00:18:51.430 align:start position:0% robot incentive group at the EF um so let's<00:18:48.240> get<00:18:48.400> into<00:18:48.600> the<00:18:48.760> Q&A<00:18:49.679> um<00:18:50.320> julan<00:18:50.840> please<00:18:51.320> U 00:18:51.430 --> 00:18:51.440 align:start position:0% let's get into the Q&A um julan please U 00:18:51.440 --> 00:18:55.190 align:start position:0% let's get into the Q&A um julan please U maybe<00:18:51.720> oh<00:18:51.880> yeah<00:18:52.640> yeah<00:18:53.640> um<00:18:54.600> so<00:18:54.799> the<00:18:54.960> first 00:18:55.190 --> 00:18:55.200 align:start position:0% maybe oh yeah yeah um so the first 00:18:55.200 --> 00:18:58.430 align:start position:0% maybe oh yeah yeah um so the first question<00:18:55.679> the<00:18:56.120> I<00:18:56.720> committee<00:18:57.720> introduces<00:18:58.320> for 00:18:58.430 --> 00:18:58.440 align:start position:0% question the I committee introduces for 00:18:58.440 --> 00:19:00.710 align:start position:0% question the I committee introduces for the<00:18:58.520> first<00:18:58.919> time<00:18:59.080> a<00:18:59.240> duty<00:18:59.799> for<00:19:00.120> validators 00:19:00.710 --> 00:19:00.720 align:start position:0% the first time a duty for validators 00:19:00.720 --> 00:19:03.390 align:start position:0% the first time a duty for validators that<00:19:00.880> require<00:19:01.240> mempo<00:19:01.760> access<00:19:02.600> are<00:19:02.919> there<00:19:03.200> any 00:19:03.390 --> 00:19:03.400 align:start position:0% that require mempo access are there any 00:19:03.400 --> 00:19:05.470 align:start position:0% that require mempo access are there any concerns<00:19:03.880> with<00:19:04.120> this<00:19:05.120> yeah<00:19:05.200> that's<00:19:05.320> an 00:19:05.470 --> 00:19:05.480 align:start position:0% concerns with this yeah that's an 00:19:05.480 --> 00:19:08.430 align:start position:0% concerns with this yeah that's an interesting<00:19:05.919> question<00:19:06.280> so<00:19:07.280> um<00:19:07.840> currently<00:19:08.280> in 00:19:08.430 --> 00:19:08.440 align:start position:0% interesting question so um currently in 00:19:08.440 --> 00:19:10.230 align:start position:0% interesting question so um currently in ethereum<00:19:08.919> validators<00:19:09.440> need<00:19:09.600> to<00:19:09.760> have<00:19:10.000> access 00:19:10.230 --> 00:19:10.240 align:start position:0% ethereum validators need to have access 00:19:10.240 --> 00:19:12.149 align:start position:0% ethereum validators need to have access to<00:19:10.400> the<00:19:10.520> menol<00:19:10.960> anyway<00:19:11.320> because<00:19:11.799> sometimes 00:19:12.149 --> 00:19:12.159 align:start position:0% to the menol anyway because sometimes 00:19:12.159 --> 00:19:15.390 align:start position:0% to the menol anyway because sometimes they<00:19:13.159> um<00:19:13.520> in<00:19:13.679> principle<00:19:14.159> from<00:19:14.320> the<00:19:14.480> etherum 00:19:15.390 --> 00:19:15.400 align:start position:0% they um in principle from the etherum 00:19:15.400 --> 00:19:17.270 align:start position:0% they um in principle from the etherum protocol<00:19:16.360> they<00:19:16.720> they<00:19:16.799> are<00:19:16.960> asked<00:19:17.159> to 00:19:17.270 --> 00:19:17.280 align:start position:0% protocol they they are asked to 00:19:17.280 --> 00:19:19.190 align:start position:0% protocol they they are asked to construct<00:19:17.679> blocks<00:19:18.280> most<00:19:18.440> of<00:19:18.600> them<00:19:18.760> Outsource 00:19:19.190 --> 00:19:19.200 align:start position:0% construct blocks most of them Outsource 00:19:19.200 --> 00:19:21.270 align:start position:0% construct blocks most of them Outsource this<00:19:19.400> vmf<00:19:19.840> boost<00:19:20.159> but<00:19:20.280> currently<00:19:20.679> validators 00:19:21.270 --> 00:19:21.280 align:start position:0% this vmf boost but currently validators 00:19:21.280 --> 00:19:23.510 align:start position:0% this vmf boost but currently validators have<00:19:21.480> access<00:19:21.720> to<00:19:21.840> the<00:19:22.000> mle<00:19:22.960> uh<00:19:23.080> so<00:19:23.200> now<00:19:23.360> we're 00:19:23.510 --> 00:19:23.520 align:start position:0% have access to the mle uh so now we're 00:19:23.520 --> 00:19:25.789 align:start position:0% have access to the mle uh so now we're introducing<00:19:24.520> uh<00:19:24.640> some<00:19:24.840> way<00:19:25.039> that<00:19:25.240> this<00:19:25.360> is 00:19:25.789 --> 00:19:25.799 align:start position:0% introducing uh some way that this is 00:19:25.799 --> 00:19:28.830 align:start position:0% introducing uh some way that this is necessary<00:19:26.360> I<00:19:26.559> guess<00:19:27.320> even<00:19:28.000> if<00:19:28.159> there's<00:19:28.320> a<00:19:28.440> very 00:19:28.830 --> 00:19:28.840 align:start position:0% necessary I guess even if there's a very 00:19:28.840 --> 00:19:30.110 align:start position:0% necessary I guess even if there's a very strict<00:19:29.080> reason<00:19:29.360> why<00:19:29.480> you<00:19:29.559> don't<00:19:29.720> want<00:19:29.799> to<00:19:29.960> have 00:19:30.110 --> 00:19:30.120 align:start position:0% strict reason why you don't want to have 00:19:30.120 --> 00:19:32.270 align:start position:0% strict reason why you don't want to have access<00:19:30.440> you<00:19:30.520> could<00:19:30.679> also<00:19:30.919> just<00:19:31.600> propose<00:19:32.159> an 00:19:32.270 --> 00:19:32.280 align:start position:0% access you could also just propose an 00:19:32.280 --> 00:19:33.750 align:start position:0% access you could also just propose an empty<00:19:32.559> inclusion<00:19:33.000> list<00:19:33.159> and<00:19:33.280> then<00:19:33.440> again<00:19:33.600> we 00:19:33.750 --> 00:19:33.760 align:start position:0% empty inclusion list and then again we 00:19:33.760 --> 00:19:35.350 align:start position:0% empty inclusion list and then again we rely<00:19:34.039> on<00:19:34.200> that<00:19:34.360> there's<00:19:34.559> at<00:19:34.679> least<00:19:34.880> one<00:19:35.120> person 00:19:35.350 --> 00:19:35.360 align:start position:0% rely on that there's at least one person 00:19:35.360 --> 00:19:38.190 align:start position:0% rely on that there's at least one person willing<00:19:35.679> to<00:19:35.840> make<00:19:36.000> an<00:19:36.120> inclusion<00:19:36.799> list<00:19:37.799> um<00:19:38.080> I 00:19:38.190 --> 00:19:38.200 align:start position:0% willing to make an inclusion list um I 00:19:38.200 --> 00:19:39.310 align:start position:0% willing to make an inclusion list um I think<00:19:38.360> this<00:19:38.480> shouldn't<00:19:38.720> be<00:19:38.840> a<00:19:39.000> problem 00:19:39.310 --> 00:19:39.320 align:start position:0% think this shouldn't be a problem 00:19:39.320 --> 00:19:41.549 align:start position:0% think this shouldn't be a problem validators<00:19:39.960> if<00:19:40.120> they<00:19:40.240> want<00:19:40.520> they<00:19:40.640> can<00:19:40.799> run<00:19:41.440> a 00:19:41.549 --> 00:19:41.559 align:start position:0% validators if they want they can run a 00:19:41.559 --> 00:19:43.590 align:start position:0% validators if they want they can run a version<00:19:41.799> of<00:19:41.919> the<00:19:42.000> mle<00:19:42.400> that's<00:19:43.039> well<00:19:43.240> suited 00:19:43.590 --> 00:19:43.600 align:start position:0% version of the mle that's well suited 00:19:43.600 --> 00:19:46.590 align:start position:0% version of the mle that's well suited for<00:19:43.799> them<00:19:44.600> um<00:19:45.600> yeah<00:19:45.760> so<00:19:46.000> I<00:19:46.120> I<00:19:46.200> don't<00:19:46.360> think<00:19:46.480> this 00:19:46.590 --> 00:19:46.600 align:start position:0% for them um yeah so I I don't think this 00:19:46.600 --> 00:19:47.870 align:start position:0% for them um yeah so I I don't think this should<00:19:46.760> be<00:19:46.840> a<00:19:46.960> big 00:19:47.870 --> 00:19:47.880 align:start position:0% should be a big 00:19:47.880 --> 00:19:50.750 align:start position:0% should be a big problem<00:19:48.880> next<00:19:49.159> question<00:19:50.000> uh<00:19:50.200> how<00:19:50.360> does<00:19:50.559> the 00:19:50.750 --> 00:19:50.760 align:start position:0% problem next question uh how does the 00:19:50.760 --> 00:19:52.830 align:start position:0% problem next question uh how does the validator<00:19:51.440> access<00:19:51.760> the<00:19:51.880> mempo<00:19:52.360> and<00:19:52.480> how<00:19:52.679> does 00:19:52.830 --> 00:19:52.840 align:start position:0% validator access the mempo and how does 00:19:52.840 --> 00:19:55.830 align:start position:0% validator access the mempo and how does it<00:19:52.960> select<00:19:53.679> transactions<00:19:54.679> yeah<00:19:54.919> so<00:19:55.559> um<00:19:55.720> I'm 00:19:55.830 --> 00:19:55.840 align:start position:0% it select transactions yeah so um I'm 00:19:55.840 --> 00:19:57.430 align:start position:0% it select transactions yeah so um I'm not<00:19:55.960> sure<00:19:56.120> if<00:19:56.240> this<00:19:56.320> is<00:19:56.480> like<00:19:56.600> more<00:19:56.760> of<00:19:56.880> a<00:19:57.039> a<00:19:57.159> Dev 00:19:57.430 --> 00:19:57.440 align:start position:0% not sure if this is like more of a a Dev 00:19:57.440 --> 00:20:00.310 align:start position:0% not sure if this is like more of a a Dev side<00:19:57.600> of<00:19:58.080> question<00:19:58.320> or<00:19:58.679> rearch<00:19:59.120> question<00:20:00.120> uh 00:20:00.310 --> 00:20:00.320 align:start position:0% side of question or rearch question uh 00:20:00.320 --> 00:20:01.430 align:start position:0% side of question or rearch question uh coming<00:20:00.559> from<00:20:00.679> the<00:20:00.760> research<00:20:01.120> side<00:20:01.280> I'll 00:20:01.430 --> 00:20:01.440 align:start position:0% coming from the research side I'll 00:20:01.440 --> 00:20:03.070 align:start position:0% coming from the research side I'll answer<00:20:01.640> it<00:20:01.799> as<00:20:01.919> a<00:20:02.120> as<00:20:02.200> a<00:20:02.280> research<00:20:02.679> question<00:20:02.960> I 00:20:03.070 --> 00:20:03.080 align:start position:0% answer it as a as a research question I 00:20:03.080 --> 00:20:05.789 align:start position:0% answer it as a as a research question I guess<00:20:03.480> so<00:20:03.679> how<00:20:03.840> does<00:20:03.960> it<00:20:04.080> select<00:20:04.799> transactions 00:20:05.789 --> 00:20:05.799 align:start position:0% guess so how does it select transactions 00:20:05.799 --> 00:20:08.070 align:start position:0% guess so how does it select transactions um<00:20:06.240> this<00:20:06.480> could<00:20:06.679> be<00:20:06.840> to<00:20:07.000> maximize<00:20:07.520> some<00:20:07.880> some 00:20:08.070 --> 00:20:08.080 align:start position:0% um this could be to maximize some some 00:20:08.080 --> 00:20:09.510 align:start position:0% um this could be to maximize some some objective<00:20:08.440> function<00:20:08.720> that<00:20:08.880> they<00:20:09.000> have<00:20:09.159> for 00:20:09.510 --> 00:20:09.520 align:start position:0% objective function that they have for 00:20:09.520 --> 00:20:11.510 align:start position:0% objective function that they have for themselves<00:20:10.400> uh<00:20:10.559> maybe<00:20:10.760> they<00:20:10.880> want<00:20:11.039> to<00:20:11.159> include 00:20:11.510 --> 00:20:11.520 align:start position:0% themselves uh maybe they want to include 00:20:11.520 --> 00:20:13.510 align:start position:0% themselves uh maybe they want to include transactions<00:20:12.400> because<00:20:12.840> they<00:20:13.159> they<00:20:13.280> think 00:20:13.510 --> 00:20:13.520 align:start position:0% transactions because they they think 00:20:13.520 --> 00:20:15.270 align:start position:0% transactions because they they think that<00:20:13.679> regulatory<00:20:14.159> censorship<00:20:14.679> is<00:20:14.840> very<00:20:15.039> bad 00:20:15.270 --> 00:20:15.280 align:start position:0% that regulatory censorship is very bad 00:20:15.280 --> 00:20:16.350 align:start position:0% that regulatory censorship is very bad or<00:20:15.440> maybe<00:20:15.679> they<00:20:15.799> want<00:20:15.919> to<00:20:16.039> include 00:20:16.350 --> 00:20:16.360 align:start position:0% or maybe they want to include 00:20:16.360 --> 00:20:18.310 align:start position:0% or maybe they want to include transactions<00:20:16.880> because<00:20:17.080> they<00:20:17.200> don't<00:20:17.400> want<00:20:18.200> uh 00:20:18.310 --> 00:20:18.320 align:start position:0% transactions because they don't want uh 00:20:18.320 --> 00:20:20.390 align:start position:0% transactions because they don't want uh people<00:20:18.559> to<00:20:18.760> mess<00:20:19.080> with<00:20:19.360> how<00:20:19.640> their<00:20:19.960> favorite 00:20:20.390 --> 00:20:20.400 align:start position:0% people to mess with how their favorite 00:20:20.400 --> 00:20:22.430 align:start position:0% people to mess with how their favorite application<00:20:20.880> works<00:20:21.159> or<00:20:21.360> whatever<00:20:22.000> for<00:20:22.159> so<00:20:22.280> for 00:20:22.430 --> 00:20:22.440 align:start position:0% application works or whatever for so for 00:20:22.440 --> 00:20:24.630 align:start position:0% application works or whatever for so for economic<00:20:22.960> reasons<00:20:23.960> um<00:20:24.120> in<00:20:24.280> principle 00:20:24.630 --> 00:20:24.640 align:start position:0% economic reasons um in principle 00:20:24.640 --> 00:20:26.149 align:start position:0% economic reasons um in principle inclusionist<00:20:25.159> committee<00:20:25.440> members<00:20:25.720> are<00:20:25.880> free 00:20:26.149 --> 00:20:26.159 align:start position:0% inclusionist committee members are free 00:20:26.159 --> 00:20:27.789 align:start position:0% inclusionist committee members are free to<00:20:26.360> construct<00:20:26.720> their<00:20:26.840> inclusionist<00:20:27.480> as<00:20:27.600> they 00:20:27.789 --> 00:20:27.799 align:start position:0% to construct their inclusionist as they 00:20:27.799 --> 00:20:29.870 align:start position:0% to construct their inclusionist as they like<00:20:28.520> um<00:20:28.799> and<00:20:29.000> since<00:20:29.200> there<00:20:29.320> are<00:20:29.440> no<00:20:29.559> rewards 00:20:29.870 --> 00:20:29.880 align:start position:0% like um and since there are no rewards 00:20:29.880 --> 00:20:32.470 align:start position:0% like um and since there are no rewards for<00:20:30.120> this<00:20:30.840> um<00:20:31.600> there's<00:20:31.799> no<00:20:31.960> reason<00:20:32.240> why<00:20:32.360> you 00:20:32.470 --> 00:20:32.480 align:start position:0% for this um there's no reason why you 00:20:32.480 --> 00:20:33.870 align:start position:0% for this um there's no reason why you wouldn't<00:20:32.760> for<00:20:32.919> example<00:20:33.200> order<00:20:33.520> and<00:20:33.679> buy 00:20:33.870 --> 00:20:33.880 align:start position:0% wouldn't for example order and buy 00:20:33.880 --> 00:20:37.149 align:start position:0% wouldn't for example order and buy priority<00:20:34.320> fee<00:20:35.320> um<00:20:35.559> on<00:20:35.679> the<00:20:35.799> de<00:20:36.240> side<00:20:36.919> um 00:20:37.149 --> 00:20:37.159 align:start position:0% priority fee um on the de side um 00:20:37.159 --> 00:20:39.510 align:start position:0% priority fee um on the de side um potentially<00:20:37.799> like<00:20:38.000> catches<00:20:38.440> later<00:20:39.039> teren<00:20:39.360> is 00:20:39.510 --> 00:20:39.520 align:start position:0% potentially like catches later teren is 00:20:39.520 --> 00:20:42.230 align:start position:0% potentially like catches later teren is here<00:20:39.679> as<00:20:39.840> well<00:20:40.840> um<00:20:41.640> yeah<00:20:41.760> I<00:20:41.840> think<00:20:42.039> that<00:20:42.120> will 00:20:42.230 --> 00:20:42.240 align:start position:0% here as well um yeah I think that will 00:20:42.240 --> 00:20:43.390 align:start position:0% here as well um yeah I think that will be<00:20:42.360> better<00:20:42.559> to<00:20:42.720> do 00:20:43.390 --> 00:20:43.400 align:start position:0% be better to do 00:20:43.400 --> 00:20:46.870 align:start position:0% be better to do later<00:20:44.400> right<00:20:45.200> uh<00:20:45.360> next<00:20:45.640> question<00:20:46.440> will<00:20:46.720> there 00:20:46.870 --> 00:20:46.880 align:start position:0% later right uh next question will there 00:20:46.880 --> 00:20:49.990 align:start position:0% later right uh next question will there be<00:20:47.120> PBS<00:20:47.520> style<00:20:47.840> Marketplace<00:20:48.360> for<00:20:49.280> uh<00:20:49.400> forming 00:20:49.990 --> 00:20:50.000 align:start position:0% be PBS style Marketplace for uh forming 00:20:50.000 --> 00:20:52.310 align:start position:0% be PBS style Marketplace for uh forming for<00:20:50.559> inclusion<00:20:51.039> lists<00:20:51.559> it<00:20:51.679> seems<00:20:51.919> to<00:20:52.000> be<00:20:52.159> just 00:20:52.310 --> 00:20:52.320 align:start position:0% for inclusion lists it seems to be just 00:20:52.320 --> 00:20:54.149 align:start position:0% for inclusion lists it seems to be just another<00:20:52.679> block<00:20:52.960> space<00:20:53.240> consumption<00:20:53.720> design 00:20:54.149 --> 00:20:54.159 align:start position:0% another block space consumption design 00:20:54.159 --> 00:20:57.310 align:start position:0% another block space consumption design from<00:20:54.360> that<00:20:55.039> perspective<00:20:56.039> yeah<00:20:56.600> um<00:20:56.760> so<00:20:57.120> we're 00:20:57.310 --> 00:20:57.320 align:start position:0% from that perspective yeah um so we're 00:20:57.320 --> 00:20:58.990 align:start position:0% from that perspective yeah um so we're very<00:20:57.559> aware<00:20:57.799> of<00:20:57.960> this<00:20:58.240> and<00:20:58.600> fossil<00:20:58.880> is 00:20:58.990 --> 00:20:59.000 align:start position:0% very aware of this and fossil is 00:20:59.000 --> 00:21:01.789 align:start position:0% very aware of this and fossil is designed<00:20:59.600> explicitly<00:21:00.240> to<00:21:00.480> not<00:21:01.200> uh<00:21:01.320> Foster 00:21:01.789 --> 00:21:01.799 align:start position:0% designed explicitly to not uh Foster 00:21:01.799 --> 00:21:05.070 align:start position:0% designed explicitly to not uh Foster such<00:21:02.039> a<00:21:02.600> such<00:21:02.760> a<00:21:02.960> market<00:21:03.600> for<00:21:04.080> outsourcing 00:21:05.070 --> 00:21:05.080 align:start position:0% such a such a market for outsourcing 00:21:05.080 --> 00:21:06.830 align:start position:0% such a such a market for outsourcing some<00:21:05.360> key<00:21:05.600> observations<00:21:06.159> here<00:21:06.320> are<00:21:06.480> that<00:21:06.640> meev 00:21:06.830 --> 00:21:06.840 align:start position:0% some key observations here are that meev 00:21:06.840 --> 00:21:09.070 align:start position:0% some key observations here are that meev boost<00:21:07.120> relies<00:21:07.440> on<00:21:07.679> economies<00:21:08.080> of<00:21:08.240> skill<00:21:08.960> there 00:21:09.070 --> 00:21:09.080 align:start position:0% boost relies on economies of skill there 00:21:09.080 --> 00:21:11.909 align:start position:0% boost relies on economies of skill there are<00:21:09.240> high<00:21:09.440> barriers<00:21:09.799> of<00:21:10.000> Entry<00:21:10.480> because<00:21:10.679> of<00:21:11.679> um 00:21:11.909 --> 00:21:11.919 align:start position:0% are high barriers of Entry because of um 00:21:11.919 --> 00:21:13.070 align:start position:0% are high barriers of Entry because of um because<00:21:12.080> of<00:21:12.240> private<00:21:12.480> order<00:21:12.679> flow<00:21:12.919> and<00:21:13.000> the 00:21:13.070 --> 00:21:13.080 align:start position:0% because of private order flow and the 00:21:13.080 --> 00:21:14.350 align:start position:0% because of private order flow and the economies<00:21:13.440> of<00:21:13.520> skill<00:21:13.840> come<00:21:14.039> because<00:21:14.240> it's 00:21:14.350 --> 00:21:14.360 align:start position:0% economies of skill come because it's 00:21:14.360 --> 00:21:16.870 align:start position:0% economies of skill come because it's very<00:21:14.840> difficult<00:21:14.960> to<00:21:15.200> construct<00:21:16.200> uh<00:21:16.559> a<00:21:16.679> very 00:21:16.870 --> 00:21:16.880 align:start position:0% very difficult to construct uh a very 00:21:16.880 --> 00:21:19.149 align:start position:0% very difficult to construct uh a very valuable<00:21:17.320> block<00:21:18.240> uh<00:21:18.360> and<00:21:18.520> this<00:21:18.679> makes<00:21:19.000> that 00:21:19.149 --> 00:21:19.159 align:start position:0% valuable block uh and this makes that 00:21:19.159 --> 00:21:21.110 align:start position:0% valuable block uh and this makes that it's<00:21:19.400> individually<00:21:20.000> rational<00:21:20.360> to<00:21:20.520> Outsource 00:21:21.110 --> 00:21:21.120 align:start position:0% it's individually rational to Outsource 00:21:21.120 --> 00:21:24.110 align:start position:0% it's individually rational to Outsource my<00:21:21.320> block<00:21:21.600> construction<00:21:22.120> to<00:21:22.320> some<00:21:23.000> M<00:21:23.200> boost<00:21:23.880> uh 00:21:24.110 --> 00:21:24.120 align:start position:0% my block construction to some M boost uh 00:21:24.120 --> 00:21:26.510 align:start position:0% my block construction to some M boost uh builder<00:21:25.120> for<00:21:25.440> FAL<00:21:25.840> inclusion<00:21:26.200> list<00:21:26.400> this 00:21:26.510 --> 00:21:26.520 align:start position:0% builder for FAL inclusion list this 00:21:26.520 --> 00:21:29.310 align:start position:0% builder for FAL inclusion list this isn't<00:21:26.799> the<00:21:26.960> case<00:21:27.440> so<00:21:28.120> uh<00:21:28.559> reting<00:21:28.919> inclusion 00:21:29.310 --> 00:21:29.320 align:start position:0% isn't the case so uh reting inclusion 00:21:29.320 --> 00:21:30.909 align:start position:0% isn't the case so uh reting inclusion list<00:21:29.520> is<00:21:29.679> very<00:21:29.919> easy<00:21:30.320> because<00:21:30.520> you<00:21:30.679> just 00:21:30.909 --> 00:21:30.919 align:start position:0% list is very easy because you just 00:21:30.919 --> 00:21:32.990 align:start position:0% list is very easy because you just select<00:21:31.279> transactions<00:21:31.840> based<00:21:32.039> on<00:21:32.159> some<00:21:32.400> heris 00:21:32.990 --> 00:21:33.000 align:start position:0% select transactions based on some heris 00:21:33.000 --> 00:21:35.190 align:start position:0% select transactions based on some heris that<00:21:33.159> you<00:21:33.360> like<00:21:34.240> uh<00:21:34.360> they're<00:21:34.559> not<00:21:34.760> that<00:21:34.919> big<00:21:35.120> I 00:21:35.190 --> 00:21:35.200 align:start position:0% that you like uh they're not that big I 00:21:35.200 --> 00:21:37.430 align:start position:0% that you like uh they're not that big I mean<00:21:35.360> you<00:21:35.440> could<00:21:35.559> include<00:21:35.880> 12<00:21:36.559> 20<00:21:37.080> average 00:21:37.430 --> 00:21:37.440 align:start position:0% mean you could include 12 20 average 00:21:37.440 --> 00:21:40.190 align:start position:0% mean you could include 12 20 average size<00:21:38.039> transactions<00:21:39.039> um<00:21:39.360> and<00:21:39.679> you<00:21:39.799> don't<00:21:40.039> have 00:21:40.190 --> 00:21:40.200 align:start position:0% size transactions um and you don't have 00:21:40.200 --> 00:21:41.950 align:start position:0% size transactions um and you don't have any<00:21:40.320> ordering<00:21:40.799> guarantees<00:21:41.240> over<00:21:41.480> this<00:21:41.600> so<00:21:41.760> you 00:21:41.950 --> 00:21:41.960 align:start position:0% any ordering guarantees over this so you 00:21:41.960 --> 00:21:43.830 align:start position:0% any ordering guarantees over this so you can't<00:21:42.320> run<00:21:42.600> sophisticated<00:21:43.159> algorithms<00:21:43.679> to 00:21:43.830 --> 00:21:43.840 align:start position:0% can't run sophisticated algorithms to 00:21:43.840 --> 00:21:46.789 align:start position:0% can't run sophisticated algorithms to say<00:21:44.600> what<00:21:45.480> uh<00:21:45.600> value<00:21:45.919> can<00:21:46.039> I<00:21:46.120> extract<00:21:46.559> from 00:21:46.789 --> 00:21:46.799 align:start position:0% say what uh value can I extract from 00:21:46.799 --> 00:21:50.029 align:start position:0% say what uh value can I extract from these<00:21:47.520> um<00:21:48.520> from<00:21:48.720> these<00:21:48.880> transactions<00:21:49.880> you 00:21:50.029 --> 00:21:50.039 align:start position:0% these um from these transactions you 00:21:50.039 --> 00:21:51.630 align:start position:0% these um from these transactions you have<00:21:50.159> to<00:21:50.320> commit<00:21:50.640> 3<00:21:50.840> seconds<00:21:51.240> before<00:21:51.520> the 00:21:51.630 --> 00:21:51.640 align:start position:0% have to commit 3 seconds before the 00:21:51.640 --> 00:21:53.750 align:start position:0% have to commit 3 seconds before the block<00:21:51.880> producer<00:21:52.240> so<00:21:52.400> doing<00:21:52.679> any<00:21:52.840> Arbitrage<00:21:53.440> is 00:21:53.750 --> 00:21:53.760 align:start position:0% block producer so doing any Arbitrage is 00:21:53.760 --> 00:21:55.390 align:start position:0% block producer so doing any Arbitrage is is<00:21:53.960> basically<00:21:54.320> impossible<00:21:54.720> if<00:21:54.799> it<00:21:54.919> were<00:21:55.120> not 00:21:55.390 --> 00:21:55.400 align:start position:0% is basically impossible if it were not 00:21:55.400 --> 00:21:56.549 align:start position:0% is basically impossible if it were not already<00:21:55.600> impossible<00:21:56.159> because<00:21:56.320> of<00:21:56.440> the 00:21:56.549 --> 00:21:56.559 align:start position:0% already impossible because of the 00:21:56.559 --> 00:21:58.830 align:start position:0% already impossible because of the ordering<00:21:57.400> there's<00:21:57.640> no<00:21:57.880> private<00:21:58.159> order 00:21:58.830 --> 00:21:58.840 align:start position:0% ordering there's no private order 00:21:58.840 --> 00:22:01.310 align:start position:0% ordering there's no private order because<00:21:59.080> any<00:21:59.240> inclusion<00:21:59.679> list<00:21:59.919> is<00:22:00.760> propagated 00:22:01.310 --> 00:22:01.320 align:start position:0% because any inclusion list is propagated 00:22:01.320 --> 00:22:03.870 align:start position:0% because any inclusion list is propagated publicly<00:22:01.799> otherwise<00:22:02.200> it's<00:22:02.360> not<00:22:02.720> enforced<00:22:03.720> uh 00:22:03.870 --> 00:22:03.880 align:start position:0% publicly otherwise it's not enforced uh 00:22:03.880 --> 00:22:05.390 align:start position:0% publicly otherwise it's not enforced uh so<00:22:04.360> this<00:22:04.559> makes<00:22:04.760> it<00:22:04.919> that<00:22:05.039> it's<00:22:05.200> not 00:22:05.390 --> 00:22:05.400 align:start position:0% so this makes it that it's not 00:22:05.400 --> 00:22:07.549 align:start position:0% so this makes it that it's not individually<00:22:05.960> rational<00:22:06.279> to<00:22:06.440> oursource<00:22:06.960> block 00:22:07.549 --> 00:22:07.559 align:start position:0% individually rational to oursource block 00:22:07.559 --> 00:22:10.430 align:start position:0% individually rational to oursource block um<00:22:07.880> inclusionist<00:22:08.880> um<00:22:09.159> production<00:22:10.159> I<00:22:10.279> guess 00:22:10.430 --> 00:22:10.440 align:start position:0% um inclusionist um production I guess 00:22:10.440 --> 00:22:11.750 align:start position:0% um inclusionist um production I guess the<00:22:10.600> question<00:22:10.919> here<00:22:11.039> is<00:22:11.159> that<00:22:11.360> we're<00:22:11.559> very 00:22:11.750 --> 00:22:11.760 align:start position:0% the question here is that we're very 00:22:11.760 --> 00:22:13.149 align:start position:0% the question here is that we're very convinced<00:22:12.159> of<00:22:12.320> this<00:22:12.520> and<00:22:12.640> we've<00:22:12.840> talked<00:22:13.080> to 00:22:13.149 --> 00:22:13.159 align:start position:0% convinced of this and we've talked to 00:22:13.159 --> 00:22:14.630 align:start position:0% convinced of this and we've talked to builders<00:22:13.480> and<00:22:13.640> Searchers<00:22:14.080> and<00:22:14.200> no<00:22:14.279> one<00:22:14.440> has 00:22:14.630 --> 00:22:14.640 align:start position:0% builders and Searchers and no one has 00:22:14.640 --> 00:22:16.590 align:start position:0% builders and Searchers and no one has come<00:22:14.799> up<00:22:14.919> with<00:22:15.039> a<00:22:15.159> way<00:22:15.279> to<00:22:15.400> use<00:22:15.880> inclusion<00:22:16.360> list 00:22:16.590 --> 00:22:16.600 align:start position:0% come up with a way to use inclusion list 00:22:16.600 --> 00:22:19.789 align:start position:0% come up with a way to use inclusion list as<00:22:16.679> a<00:22:16.799> vehicle<00:22:17.120> for<00:22:17.400> me<00:22:18.400> if<00:22:18.480> you<00:22:18.640> do<00:22:18.840> find<00:22:19.000> a<00:22:19.200> way 00:22:19.789 --> 00:22:19.799 align:start position:0% as a vehicle for me if you do find a way 00:22:19.799 --> 00:22:21.710 align:start position:0% as a vehicle for me if you do find a way uh<00:22:19.960> I'd<00:22:20.159> be<00:22:20.320> very<00:22:20.520> interested<00:22:21.279> uh<00:22:21.400> in<00:22:21.520> trying 00:22:21.710 --> 00:22:21.720 align:start position:0% uh I'd be very interested uh in trying 00:22:21.720 --> 00:22:22.909 align:start position:0% uh I'd be very interested uh in trying to<00:22:21.840> contradict 00:22:22.909 --> 00:22:22.919 align:start position:0% to contradict 00:22:22.919 --> 00:22:25.669 align:start position:0% to contradict that<00:22:23.919> is<00:22:24.120> this<00:22:24.320> proposal<00:22:24.799> compatible<00:22:25.240> with<00:22:25.400> 4 00:22:25.669 --> 00:22:25.679 align:start position:0% that is this proposal compatible with 4 00:22:25.679 --> 00:22:28.190 align:start position:0% that is this proposal compatible with 4 second<00:22:25.919> block<00:22:26.279> times<00:22:27.279> um<00:22:27.480> so<00:22:27.760> the<00:22:27.880> person<00:22:28.080> who 00:22:28.190 --> 00:22:28.200 align:start position:0% second block times um so the person who 00:22:28.200 --> 00:22:29.230 align:start position:0% second block times um so the person who asked<00:22:28.360> this<00:22:28.520> expression<00:22:28.799> probably<00:22:29.039> thought 00:22:29.230 --> 00:22:29.240 align:start position:0% asked this expression probably thought 00:22:29.240 --> 00:22:30.789 align:start position:0% asked this expression probably thought no<00:22:29.480> but<00:22:29.640> I<00:22:29.720> think<00:22:29.880> is<00:22:30.039> actually<00:22:30.279> very 00:22:30.789 --> 00:22:30.799 align:start position:0% no but I think is actually very 00:22:30.799 --> 00:22:32.870 align:start position:0% no but I think is actually very compatible<00:22:31.799> um<00:22:32.159> the<00:22:32.400> interesting<00:22:32.760> thing 00:22:32.870 --> 00:22:32.880 align:start position:0% compatible um the interesting thing 00:22:32.880 --> 00:22:35.070 align:start position:0% compatible um the interesting thing about<00:22:33.120> inclusion<00:22:33.520> list<00:22:33.799> is<00:22:33.960> that<00:22:34.559> the<00:22:34.720> the 00:22:35.070 --> 00:22:35.080 align:start position:0% about inclusion list is that the the 00:22:35.080 --> 00:22:37.710 align:start position:0% about inclusion list is that the the timeline<00:22:36.080> um<00:22:36.200> doesn't<00:22:36.600> necessarily<00:22:37.200> depend 00:22:37.710 --> 00:22:37.720 align:start position:0% timeline um doesn't necessarily depend 00:22:37.720 --> 00:22:40.510 align:start position:0% timeline um doesn't necessarily depend on<00:22:38.400> uh<00:22:38.559> the<00:22:38.679> block<00:22:38.960> construction<00:22:39.480> timeline<00:22:40.320> so 00:22:40.510 --> 00:22:40.520 align:start position:0% on uh the block construction timeline so 00:22:40.520 --> 00:22:42.149 align:start position:0% on uh the block construction timeline so when<00:22:40.679> inclusion<00:22:41.120> lists<00:22:41.320> are<00:22:41.520> created<00:22:41.960> and 00:22:42.149 --> 00:22:42.159 align:start position:0% when inclusion lists are created and 00:22:42.159 --> 00:22:43.870 align:start position:0% when inclusion lists are created and propagated<00:22:42.840> which<00:22:42.919> is<00:22:43.039> the<00:22:43.159> largest<00:22:43.520> part<00:22:43.760> of 00:22:43.870 --> 00:22:43.880 align:start position:0% propagated which is the largest part of 00:22:43.880 --> 00:22:45.909 align:start position:0% propagated which is the largest part of the<00:22:44.080> timeline<00:22:44.960> uh<00:22:45.080> can<00:22:45.200> be<00:22:45.400> completely 00:22:45.909 --> 00:22:45.919 align:start position:0% the timeline uh can be completely 00:22:45.919 --> 00:22:47.510 align:start position:0% the timeline uh can be completely parallel<00:22:46.320> to<00:22:46.520> block<00:22:46.760> construction 00:22:47.510 --> 00:22:47.520 align:start position:0% parallel to block construction 00:22:47.520 --> 00:22:49.029 align:start position:0% parallel to block construction inclusionists<00:22:48.159> don't<00:22:48.400> have<00:22:48.480> to<00:22:48.640> depend<00:22:48.919> on 00:22:49.029 --> 00:22:49.039 align:start position:0% inclusionists don't have to depend on 00:22:49.039 --> 00:22:50.870 align:start position:0% inclusionists don't have to depend on the<00:22:49.200> head<00:22:49.320> of<00:22:49.440> the<00:22:49.559> chain<00:22:50.279> uh<00:22:50.440> they<00:22:50.559> could<00:22:50.720> be 00:22:50.870 --> 00:22:50.880 align:start position:0% the head of the chain uh they could be 00:22:50.880 --> 00:22:52.950 align:start position:0% the head of the chain uh they could be made<00:22:51.159> for<00:22:51.320> example<00:22:52.200> uh<00:22:52.320> in<00:22:52.480> principle<00:22:52.799> they 00:22:52.950 --> 00:22:52.960 align:start position:0% made for example uh in principle they 00:22:52.960 --> 00:22:54.750 align:start position:0% made for example uh in principle they could<00:22:53.080> be<00:22:53.200> made<00:22:53.440> whenever<00:22:53.799> early<00:22:54.240> let's<00:22:54.440> say 00:22:54.750 --> 00:22:54.760 align:start position:0% could be made whenever early let's say 00:22:54.760 --> 00:22:56.909 align:start position:0% could be made whenever early let's say three<00:22:54.960> blocks<00:22:55.279> early<00:22:55.559> or<00:22:55.720> something<00:22:56.679> and<00:22:56.799> then 00:22:56.909 --> 00:22:56.919 align:start position:0% three blocks early or something and then 00:22:56.919 --> 00:22:58.549 align:start position:0% three blocks early or something and then it<00:22:57.080> could<00:22:57.279> still<00:22:57.640> constrain<00:22:58.080> the<00:22:58.159> current 00:22:58.549 --> 00:22:58.559 align:start position:0% it could still constrain the current 00:22:58.559 --> 00:23:00.710 align:start position:0% it could still constrain the current block<00:22:59.120> and<00:22:59.240> since<00:22:59.559> this<00:22:59.760> timeline<00:23:00.159> is<00:23:00.360> very 00:23:00.710 --> 00:23:00.720 align:start position:0% block and since this timeline is very 00:23:00.720 --> 00:23:02.549 align:start position:0% block and since this timeline is very very<00:23:00.960> easy<00:23:01.320> as<00:23:01.480> in<00:23:01.640> the<00:23:01.720> block<00:23:01.919> producer<00:23:02.320> must 00:23:02.549 --> 00:23:02.559 align:start position:0% very easy as in the block producer must 00:23:02.559 --> 00:23:04.110 align:start position:0% very easy as in the block producer must receive<00:23:02.960> them<00:23:03.279> for<00:23:03.480> which<00:23:03.600> it<00:23:03.720> could<00:23:03.880> have<00:23:04.000> a 00:23:04.110 --> 00:23:04.120 align:start position:0% receive them for which it could have a 00:23:04.120 --> 00:23:05.909 align:start position:0% receive them for which it could have a very<00:23:04.279> long<00:23:04.480> time<00:23:05.000> and<00:23:05.120> the<00:23:05.240> enforcement<00:23:05.760> is 00:23:05.909 --> 00:23:05.919 align:start position:0% very long time and the enforcement is 00:23:05.919 --> 00:23:08.269 align:start position:0% very long time and the enforcement is done<00:23:06.080> by<00:23:06.200> the<00:23:06.480> testers<00:23:06.880> it<00:23:07.000> doesn't<00:23:07.799> add<00:23:08.039> like 00:23:08.269 --> 00:23:08.279 align:start position:0% done by the testers it doesn't add like 00:23:08.279 --> 00:23:10.630 align:start position:0% done by the testers it doesn't add like additional<00:23:08.799> time<00:23:09.400> uh<00:23:09.520> delays<00:23:10.240> that<00:23:10.400> being 00:23:10.630 --> 00:23:10.640 align:start position:0% additional time uh delays that being 00:23:10.640 --> 00:23:12.070 align:start position:0% additional time uh delays that being said<00:23:11.000> if<00:23:11.080> you<00:23:11.240> make<00:23:11.440> them<00:23:11.600> very<00:23:11.760> far<00:23:11.960> in 00:23:12.070 --> 00:23:12.080 align:start position:0% said if you make them very far in 00:23:12.080 --> 00:23:13.750 align:start position:0% said if you make them very far in advance<00:23:12.480> the<00:23:12.559> inclusionist<00:23:13.120> is<00:23:13.240> more<00:23:13.480> likely 00:23:13.750 --> 00:23:13.760 align:start position:0% advance the inclusionist is more likely 00:23:13.760 --> 00:23:15.750 align:start position:0% advance the inclusionist is more likely to<00:23:13.960> hold<00:23:14.240> invalid<00:23:14.760> transactions<00:23:15.360> which<00:23:15.559> may 00:23:15.750 --> 00:23:15.760 align:start position:0% to hold invalid transactions which may 00:23:15.760 --> 00:23:18.190 align:start position:0% to hold invalid transactions which may not<00:23:15.919> contribute<00:23:16.360> much<00:23:16.480> to<00:23:16.640> sens 00:23:18.190 --> 00:23:18.200 align:start position:0% not contribute much to sens 00:23:18.200 --> 00:23:20.590 align:start position:0% not contribute much to sens resistance<00:23:19.200> next<00:23:19.520> question<00:23:20.080> how<00:23:20.240> about<00:23:20.480> the 00:23:20.590 --> 00:23:20.600 align:start position:0% resistance next question how about the 00:23:20.600 --> 00:23:23.350 align:start position:0% resistance next question how about the integration<00:23:21.200> of<00:23:21.400> fossil<00:23:21.919> with<00:23:22.200> e<00:23:22.559> PBS<00:23:23.200> and 00:23:23.350 --> 00:23:23.360 align:start position:0% integration of fossil with e PBS and 00:23:23.360 --> 00:23:25.110 align:start position:0% integration of fossil with e PBS and single<00:23:23.640> slot<00:23:23.960> finality<00:23:24.720> they<00:23:24.840> should<00:23:25.000> be 00:23:25.110 --> 00:23:25.120 align:start position:0% single slot finality they should be 00:23:25.120 --> 00:23:27.390 align:start position:0% single slot finality they should be aligned<00:23:25.640> coordinately<00:23:26.640> so<00:23:26.799> we're<00:23:27.039> proposing 00:23:27.390 --> 00:23:27.400 align:start position:0% aligned coordinately so we're proposing 00:23:27.400 --> 00:23:30.029 align:start position:0% aligned coordinately so we're proposing fil<00:23:27.919> separately<00:23:28.520> from<00:23:28.679> epbs<00:23:29.279> or<00:23:29.480> single<00:23:29.760> Sal 00:23:30.029 --> 00:23:30.039 align:start position:0% fil separately from epbs or single Sal 00:23:30.039 --> 00:23:31.909 align:start position:0% fil separately from epbs or single Sal finality<00:23:30.880> I<00:23:30.960> think<00:23:31.159> this<00:23:31.279> is<00:23:31.440> important 00:23:31.909 --> 00:23:31.919 align:start position:0% finality I think this is important 00:23:31.919 --> 00:23:34.110 align:start position:0% finality I think this is important because<00:23:32.559> I<00:23:32.640> don't<00:23:32.799> see<00:23:33.000> an<00:23:33.159> inherent<00:23:33.679> tension 00:23:34.110 --> 00:23:34.120 align:start position:0% because I don't see an inherent tension 00:23:34.120 --> 00:23:36.070 align:start position:0% because I don't see an inherent tension between<00:23:34.480> these<00:23:34.960> as<00:23:35.159> I<00:23:35.520> explained<00:23:35.880> in<00:23:35.960> the 00:23:36.070 --> 00:23:36.080 align:start position:0% between these as I explained in the 00:23:36.080 --> 00:23:38.110 align:start position:0% between these as I explained in the previous<00:23:36.520> answer<00:23:37.080> the<00:23:37.200> fossil<00:23:37.600> timeline<00:23:38.000> can 00:23:38.110 --> 00:23:38.120 align:start position:0% previous answer the fossil timeline can 00:23:38.120 --> 00:23:40.390 align:start position:0% previous answer the fossil timeline can be<00:23:38.320> completely<00:23:38.799> parallel<00:23:39.279> from<00:23:39.520> other 00:23:40.390 --> 00:23:40.400 align:start position:0% be completely parallel from other 00:23:40.400 --> 00:23:42.990 align:start position:0% be completely parallel from other timelines<00:23:41.400> um<00:23:41.760> so<00:23:42.039> in<00:23:42.159> my<00:23:42.360> view<00:23:42.600> it's<00:23:42.840> it's 00:23:42.990 --> 00:23:43.000 align:start position:0% timelines um so in my view it's it's 00:23:43.000 --> 00:23:44.470 align:start position:0% timelines um so in my view it's it's very<00:23:43.200> compatible<00:23:43.679> with<00:23:43.840> both<00:23:44.039> and<00:23:44.120> they<00:23:44.240> don't 00:23:44.470 --> 00:23:44.480 align:start position:0% very compatible with both and they don't 00:23:44.480 --> 00:23:46.390 align:start position:0% very compatible with both and they don't have<00:23:44.640> to<00:23:44.799> be<00:23:45.279> uh<00:23:45.440> implemented<00:23:45.960> at<00:23:46.080> the<00:23:46.200> same 00:23:46.390 --> 00:23:46.400 align:start position:0% have to be uh implemented at the same 00:23:46.400 --> 00:23:49.870 align:start position:0% have to be uh implemented at the same time<00:23:46.559> they're<00:23:46.799> proposed<00:23:47.200> as<00:23:47.480> different<00:23:48.480> uh 00:23:49.870 --> 00:23:49.880 align:start position:0% time they're proposed as different uh 00:23:49.880 --> 00:23:52.149 align:start position:0% time they're proposed as different uh proposals<00:23:50.880> does<00:23:51.039> it<00:23:51.159> mean<00:23:51.400> transactions<00:23:51.919> from 00:23:52.149 --> 00:23:52.159 align:start position:0% proposals does it mean transactions from 00:23:52.159 --> 00:23:53.830 align:start position:0% proposals does it mean transactions from inclusion<00:23:52.640> list<00:23:52.919> will<00:23:53.120> always<00:23:53.400> be<00:23:53.600> at<00:23:53.720> the 00:23:53.830 --> 00:23:53.840 align:start position:0% inclusion list will always be at the 00:23:53.840 --> 00:23:56.110 align:start position:0% inclusion list will always be at the bottom<00:23:54.120> of<00:23:54.240> the<00:23:54.400> block<00:23:55.159> it<00:23:55.320> mean<00:23:55.600> so<00:23:55.840> first<00:23:56.000> of 00:23:56.110 --> 00:23:56.120 align:start position:0% bottom of the block it mean so first of 00:23:56.120 --> 00:23:58.630 align:start position:0% bottom of the block it mean so first of all<00:23:56.760> transactions<00:23:57.400> aren't<00:23:57.760> necessarily<00:23:58.480> from 00:23:58.630 --> 00:23:58.640 align:start position:0% all transactions aren't necessarily from 00:23:58.640 --> 00:24:00.190 align:start position:0% all transactions aren't necessarily from inclusion<00:23:59.039> list<00:23:59.320> transactions<00:23:59.720> in<00:23:59.840> the<00:23:59.960> men 00:24:00.190 --> 00:24:00.200 align:start position:0% inclusion list transactions in the men 00:24:00.200 --> 00:24:01.830 align:start position:0% inclusion list transactions in the men pool<00:24:00.440> are<00:24:00.559> seen<00:24:00.840> by<00:24:01.000> inclusion<00:24:01.440> list<00:24:01.600> and<00:24:01.720> then 00:24:01.830 --> 00:24:01.840 align:start position:0% pool are seen by inclusion list and then 00:24:01.840 --> 00:24:03.149 align:start position:0% pool are seen by inclusion list and then included<00:24:02.200> in<00:24:02.320> the<00:24:02.440> block<00:24:02.720> but<00:24:02.840> the<00:24:02.919> block 00:24:03.149 --> 00:24:03.159 align:start position:0% included in the block but the block 00:24:03.159 --> 00:24:05.510 align:start position:0% included in the block but the block doesn't<00:24:03.480> contain<00:24:04.240> a<00:24:04.440> set<00:24:04.720> a<00:24:04.880> section<00:24:05.279> that's 00:24:05.510 --> 00:24:05.520 align:start position:0% doesn't contain a set a section that's 00:24:05.520 --> 00:24:08.149 align:start position:0% doesn't contain a set a section that's like<00:24:05.799> this<00:24:05.919> is<00:24:06.080> for<00:24:06.320> inclusion<00:24:06.760> list<00:24:07.720> um<00:24:07.919> so 00:24:08.149 --> 00:24:08.159 align:start position:0% like this is for inclusion list um so 00:24:08.159 --> 00:24:10.669 align:start position:0% like this is for inclusion list um so some<00:24:08.400> transactions<00:24:09.159> that<00:24:09.840> uh<00:24:10.000> you<00:24:10.320> I<00:24:10.480> guess 00:24:10.669 --> 00:24:10.679 align:start position:0% some transactions that uh you I guess 00:24:10.679 --> 00:24:12.110 align:start position:0% some transactions that uh you I guess you<00:24:10.760> could<00:24:10.960> just<00:24:11.080> see<00:24:11.279> them<00:24:11.440> as<00:24:11.600> transactions 00:24:12.110 --> 00:24:12.120 align:start position:0% you could just see them as transactions 00:24:12.120 --> 00:24:15.029 align:start position:0% you could just see them as transactions in<00:24:12.240> the<00:24:12.360> mle<00:24:13.279> mle<00:24:13.679> transactions<00:24:14.159> currently 00:24:15.029 --> 00:24:15.039 align:start position:0% in the mle mle transactions currently 00:24:15.039 --> 00:24:16.590 align:start position:0% in the mle mle transactions currently usually<00:24:15.320> are<00:24:15.480> not<00:24:15.600> put<00:24:15.799> on<00:24:15.880> the<00:24:16.039> top<00:24:16.159> of<00:24:16.320> block 00:24:16.590 --> 00:24:16.600 align:start position:0% usually are not put on the top of block 00:24:16.600 --> 00:24:18.630 align:start position:0% usually are not put on the top of block because<00:24:16.799> this<00:24:16.880> is<00:24:17.000> a<00:24:17.159> very<00:24:17.320> valuable<00:24:17.760> spot 00:24:18.630 --> 00:24:18.640 align:start position:0% because this is a very valuable spot 00:24:18.640 --> 00:24:20.549 align:start position:0% because this is a very valuable spot maybe<00:24:19.080> someone<00:24:19.400> can<00:24:19.559> extract<00:24:19.880> some<00:24:20.000> me<00:24:20.440> from 00:24:20.549 --> 00:24:20.559 align:start position:0% maybe someone can extract some me from 00:24:20.559 --> 00:24:22.510 align:start position:0% maybe someone can extract some me from being<00:24:20.799> at<00:24:20.919> the<00:24:21.000> bottom<00:24:21.279> of<00:24:21.360> the<00:24:21.440> block<00:24:22.120> so<00:24:22.279> I'd 00:24:22.510 --> 00:24:22.520 align:start position:0% being at the bottom of the block so I'd 00:24:22.520 --> 00:24:23.549 align:start position:0% being at the bottom of the block so I'd expect<00:24:22.720> them<00:24:22.880> somewhere<00:24:23.159> to<00:24:23.279> be<00:24:23.400> in<00:24:23.480> the 00:24:23.549 --> 00:24:23.559 align:start position:0% expect them somewhere to be in the 00:24:23.559 --> 00:24:26.070 align:start position:0% expect them somewhere to be in the middle<00:24:24.080> there<00:24:24.200> are<00:24:24.320> no<00:24:24.480> ordering<00:24:25.399> uh<00:24:25.559> or 00:24:26.070 --> 00:24:26.080 align:start position:0% middle there are no ordering uh or 00:24:26.080 --> 00:24:27.750 align:start position:0% middle there are no ordering uh or properties<00:24:26.600> of<00:24:26.840> like<00:24:27.039> where<00:24:27.200> and<00:24:27.360> block<00:24:27.640> it 00:24:27.750 --> 00:24:27.760 align:start position:0% properties of like where and block it 00:24:27.760 --> 00:24:30.190 align:start position:0% properties of like where and block it should<00:24:27.960> be 00:24:30.190 --> 00:24:30.200 align:start position:0% should be 00:24:30.200 --> 00:24:32.590 align:start position:0% should be should<00:24:30.559> equ<00:24:31.279> equivocating<00:24:32.200> committee 00:24:32.590 --> 00:24:32.600 align:start position:0% should equ equivocating committee 00:24:32.600 --> 00:24:35.470 align:start position:0% should equ equivocating committee members<00:24:33.200> be<00:24:33.480> slashed<00:24:34.480> so<00:24:34.720> in<00:24:34.840> our<00:24:35.039> design<00:24:35.360> we 00:24:35.470 --> 00:24:35.480 align:start position:0% members be slashed so in our design we 00:24:35.480 --> 00:24:37.190 align:start position:0% members be slashed so in our design we don't<00:24:35.640> slash<00:24:35.960> committee<00:24:36.279> members<00:24:36.640> we<00:24:36.760> do<00:24:36.960> this 00:24:37.190 --> 00:24:37.200 align:start position:0% don't slash committee members we do this 00:24:37.200 --> 00:24:39.070 align:start position:0% don't slash committee members we do this because<00:24:37.440> there<00:24:37.559> is<00:24:37.760> no<00:24:38.039> reward<00:24:38.399> scheme<00:24:38.960> we 00:24:39.070 --> 00:24:39.080 align:start position:0% because there is no reward scheme we 00:24:39.080 --> 00:24:40.669 align:start position:0% because there is no reward scheme we want<00:24:39.240> to<00:24:39.440> incentivize<00:24:40.240> as<00:24:40.399> much 00:24:40.669 --> 00:24:40.679 align:start position:0% want to incentivize as much 00:24:40.679 --> 00:24:43.630 align:start position:0% want to incentivize as much participation<00:24:41.320> as<00:24:41.520> possible<00:24:42.000> so<00:24:42.720> slashing 00:24:43.630 --> 00:24:43.640 align:start position:0% participation as possible so slashing 00:24:43.640 --> 00:24:45.630 align:start position:0% participation as possible so slashing could<00:24:44.039> be<00:24:44.240> CS<00:24:44.600> because<00:24:44.799> you<00:24:44.919> have<00:24:45.039> a<00:24:45.159> bad<00:24:45.360> not 00:24:45.630 --> 00:24:45.640 align:start position:0% could be CS because you have a bad not 00:24:45.640 --> 00:24:47.029 align:start position:0% could be CS because you have a bad not setup<00:24:46.000> and<00:24:46.080> you<00:24:46.240> accidentally<00:24:46.679> signed 00:24:47.029 --> 00:24:47.039 align:start position:0% setup and you accidentally signed 00:24:47.039 --> 00:24:48.870 align:start position:0% setup and you accidentally signed something<00:24:47.320> twice<00:24:47.919> you<00:24:48.039> don't<00:24:48.200> want<00:24:48.399> to<00:24:48.640> do 00:24:48.870 --> 00:24:48.880 align:start position:0% something twice you don't want to do 00:24:48.880 --> 00:24:51.710 align:start position:0% something twice you don't want to do this<00:24:49.360> uh<00:24:49.440> you<00:24:49.559> want<00:24:49.679> to<00:24:49.880> prevent<00:24:50.200> it<00:24:51.159> um<00:24:51.440> but<00:24:51.600> if 00:24:51.710 --> 00:24:51.720 align:start position:0% this uh you want to prevent it um but if 00:24:51.720 --> 00:24:53.950 align:start position:0% this uh you want to prevent it um but if it<00:24:51.919> happens<00:24:52.640> we<00:24:52.760> don't<00:24:52.919> want<00:24:53.039> to<00:24:53.279> penalize<00:24:53.760> for 00:24:53.950 --> 00:24:53.960 align:start position:0% it happens we don't want to penalize for 00:24:53.960 --> 00:24:57.110 align:start position:0% it happens we don't want to penalize for it<00:24:54.240> slashing<00:24:55.000> in<00:24:55.880> uh<00:24:56.320> equivocating<00:24:56.880> on<00:24:57.000> your 00:24:57.110 --> 00:24:57.120 align:start position:0% it slashing in uh equivocating on your 00:24:57.120 --> 00:24:59.029 align:start position:0% it slashing in uh equivocating on your attestations<00:24:57.760> is<00:24:57.880> important<00:24:58.360> for<00:24:58.559> finality 00:24:59.029 --> 00:24:59.039 align:start position:0% attestations is important for finality 00:24:59.039 --> 00:25:00.990 align:start position:0% attestations is important for finality to<00:24:59.200> give<00:24:59.360> some<00:24:59.600> economic<00:25:00.000> weights<00:25:00.320> behind<00:25:00.840> the 00:25:00.990 --> 00:25:01.000 align:start position:0% to give some economic weights behind the 00:25:01.000 --> 00:25:03.149 align:start position:0% to give some economic weights behind the transactions<00:25:01.440> that<00:25:01.600> land<00:25:01.799> on<00:25:01.960> chain<00:25:02.679> slashing 00:25:03.149 --> 00:25:03.159 align:start position:0% transactions that land on chain slashing 00:25:03.159 --> 00:25:05.909 align:start position:0% transactions that land on chain slashing for<00:25:03.600> double<00:25:03.840> signing<00:25:04.159> a<00:25:04.279> block<00:25:04.640> already<00:25:05.640> uh<00:25:05.760> is 00:25:05.909 --> 00:25:05.919 align:start position:0% for double signing a block already uh is 00:25:05.919 --> 00:25:07.350 align:start position:0% for double signing a block already uh is different<00:25:06.279> it<00:25:06.520> it's<00:25:06.640> not<00:25:06.840> related<00:25:07.159> to 00:25:07.350 --> 00:25:07.360 align:start position:0% different it it's not related to 00:25:07.360 --> 00:25:10.350 align:start position:0% different it it's not related to finality<00:25:08.120> it's<00:25:08.480> it's<00:25:09.440> uh<00:25:09.679> but<00:25:09.799> it<00:25:09.919> does<00:25:10.120> cause 00:25:10.350 --> 00:25:10.360 align:start position:0% finality it's it's uh but it does cause 00:25:10.360 --> 00:25:13.590 align:start position:0% finality it's it's uh but it does cause a<00:25:10.480> bit<00:25:10.600> more<00:25:10.840> stress<00:25:11.159> on<00:25:11.399> the<00:25:11.640> on<00:25:11.799> the<00:25:12.000> Chain<00:25:12.880> SL 00:25:13.590 --> 00:25:13.600 align:start position:0% a bit more stress on the on the Chain SL 00:25:13.600 --> 00:25:15.990 align:start position:0% a bit more stress on the on the Chain SL um<00:25:14.360> equiv<00:25:14.960> with<00:25:15.080> your<00:25:15.159> inclusionist<00:25:15.760> doesn't 00:25:15.990 --> 00:25:16.000 align:start position:0% um equiv with your inclusionist doesn't 00:25:16.000 --> 00:25:17.510 align:start position:0% um equiv with your inclusionist doesn't cause<00:25:16.320> anything<00:25:16.679> it<00:25:16.840> just<00:25:17.000> means<00:25:17.240> that<00:25:17.360> your 00:25:17.510 --> 00:25:17.520 align:start position:0% cause anything it just means that your 00:25:17.520 --> 00:25:18.909 align:start position:0% cause anything it just means that your inclusionist<00:25:18.000> isn't<00:25:18.240> enforced<00:25:18.720> it's 00:25:18.909 --> 00:25:18.919 align:start position:0% inclusionist isn't enforced it's 00:25:18.919 --> 00:25:20.950 align:start position:0% inclusionist isn't enforced it's equivalent<00:25:19.320> to<00:25:19.520> sending<00:25:19.840> no<00:25:20.080> inclusionist<00:25:20.760> so 00:25:20.950 --> 00:25:20.960 align:start position:0% equivalent to sending no inclusionist so 00:25:20.960 --> 00:25:23.590 align:start position:0% equivalent to sending no inclusionist so that's<00:25:21.120> why<00:25:21.399> we<00:25:21.520> don't<00:25:21.679> slash<00:25:21.960> for<00:25:22.399> it<00:25:23.399> right 00:25:23.590 --> 00:25:23.600 align:start position:0% that's why we don't slash for it right 00:25:23.600 --> 00:25:27.559 align:start position:0% that's why we don't slash for it right so<00:25:23.919> unfortunately<00:25:24.679> we<00:25:24.919> have<00:25:25.200> run