WEBVTT Kind: captions Language: en 00:00:01.010 --> 00:00:09.709 align:start position:0% [Music] 00:00:09.709 --> 00:00:09.719 align:start position:0% [Music] 00:00:09.719 --> 00:00:11.589 align:start position:0% [Music] hi<00:00:09.920> everyone<00:00:10.519> uh<00:00:10.679> I'm<00:00:10.960> Francesco<00:00:11.440> I'm<00:00:11.519> a 00:00:11.589 --> 00:00:11.599 align:start position:0% hi everyone uh I'm Francesco I'm a 00:00:11.599 --> 00:00:13.390 align:start position:0% hi everyone uh I'm Francesco I'm a researcher<00:00:11.960> at<00:00:12.120> EF<00:00:12.639> and<00:00:12.759> I'm<00:00:12.880> here<00:00:13.000> to<00:00:13.160> talk<00:00:13.320> to 00:00:13.390 --> 00:00:13.400 align:start position:0% researcher at EF and I'm here to talk to 00:00:13.400 --> 00:00:15.829 align:start position:0% researcher at EF and I'm here to talk to you<00:00:13.599> about<00:00:14.400> uh<00:00:14.559> making<00:00:15.000> ethereum<00:00:15.400> finalized 00:00:15.829 --> 00:00:15.839 align:start position:0% you about uh making ethereum finalized 00:00:15.839 --> 00:00:17.390 align:start position:0% you about uh making ethereum finalized faster<00:00:16.440> and<00:00:16.560> how<00:00:16.720> this<00:00:16.840> relates<00:00:17.160> to<00:00:17.279> the 00:00:17.390 --> 00:00:17.400 align:start position:0% faster and how this relates to the 00:00:17.400 --> 00:00:19.349 align:start position:0% faster and how this relates to the future<00:00:17.640> of<00:00:17.760> staking<00:00:18.160> to<00:00:18.400> potential<00:00:18.920> staking 00:00:19.349 --> 00:00:19.359 align:start position:0% future of staking to potential staking 00:00:19.359 --> 00:00:22.550 align:start position:0% future of staking to potential staking changes<00:00:19.760> to<00:00:20.000> to<00:00:20.560> come<00:00:21.560> um<00:00:21.760> so<00:00:22.080> first<00:00:22.240> of<00:00:22.359> all 00:00:22.550 --> 00:00:22.560 align:start position:0% changes to to come um so first of all 00:00:22.560 --> 00:00:23.870 align:start position:0% changes to to come um so first of all let's<00:00:22.720> let's<00:00:22.960> recap<00:00:23.359> what<00:00:23.480> are<00:00:23.560> we<00:00:23.680> actually 00:00:23.870 --> 00:00:23.880 align:start position:0% let's let's recap what are we actually 00:00:23.880 --> 00:00:25.670 align:start position:0% let's let's recap what are we actually trying<00:00:24.119> to<00:00:24.279> achieve<00:00:24.720> with<00:00:25.160> single<00:00:25.439> SL 00:00:25.670 --> 00:00:25.680 align:start position:0% trying to achieve with single SL 00:00:25.680 --> 00:00:28.230 align:start position:0% trying to achieve with single SL finality<00:00:26.080> or<00:00:26.240> generally<00:00:26.640> faster<00:00:27.080> finality<00:00:28.080> um 00:00:28.230 --> 00:00:28.240 align:start position:0% finality or generally faster finality um 00:00:28.240 --> 00:00:30.029 align:start position:0% finality or generally faster finality um there's<00:00:28.439> actually<00:00:29.000> one<00:00:29.240> goal<00:00:29.439> is<00:00:29.640> faster 00:00:30.029 --> 00:00:30.039 align:start position:0% there's actually one goal is faster 00:00:30.039 --> 00:00:32.069 align:start position:0% there's actually one goal is faster finality<00:00:30.480> in<00:00:30.640> itself<00:00:31.160> so<00:00:31.359> we<00:00:31.560> we<00:00:31.759> don't<00:00:31.920> want 00:00:32.069 --> 00:00:32.079 align:start position:0% finality in itself so we we don't want 00:00:32.079 --> 00:00:34.069 align:start position:0% finality in itself so we we don't want to<00:00:32.239> have<00:00:32.439> a<00:00:32.640> ux<00:00:33.040> and<00:00:33.280> security<00:00:33.640> trade-off 00:00:34.069 --> 00:00:34.079 align:start position:0% to have a ux and security trade-off 00:00:34.079 --> 00:00:37.110 align:start position:0% to have a ux and security trade-off you're<00:00:34.239> not<00:00:34.440> supposed<00:00:34.800> to<00:00:35.640> need<00:00:35.920> to<00:00:36.440> uh<00:00:36.520> choose 00:00:37.110 --> 00:00:37.120 align:start position:0% you're not supposed to need to uh choose 00:00:37.120 --> 00:00:40.910 align:start position:0% you're not supposed to need to uh choose between<00:00:38.120> um<00:00:38.320> waiting<00:00:38.600> for<00:00:38.800> finality<00:00:39.559> or<00:00:40.120> um 00:00:40.910 --> 00:00:40.920 align:start position:0% between um waiting for finality or um 00:00:40.920 --> 00:00:42.990 align:start position:0% between um waiting for finality or um and<00:00:41.079> and<00:00:41.200> getting<00:00:41.480> higher<00:00:41.840> security<00:00:42.559> or 00:00:42.990 --> 00:00:43.000 align:start position:0% and and getting higher security or 00:00:43.000 --> 00:00:44.830 align:start position:0% and and getting higher security or accepting<00:00:43.360> something<00:00:43.960> confirmation<00:00:44.480> faster 00:00:44.830 --> 00:00:44.840 align:start position:0% accepting something confirmation faster 00:00:44.840 --> 00:00:47.189 align:start position:0% accepting something confirmation faster but<00:00:45.000> at<00:00:45.200> lower<00:00:45.480> security<00:00:46.480> and<00:00:46.840> uh<00:00:46.960> this<00:00:47.079> is 00:00:47.189 --> 00:00:47.199 align:start position:0% but at lower security and uh this is 00:00:47.199 --> 00:00:49.069 align:start position:0% but at lower security and uh this is also<00:00:47.399> not<00:00:47.520> just<00:00:47.640> for<00:00:47.800> regular<00:00:48.120> users<00:00:48.600> but<00:00:48.920> but 00:00:49.069 --> 00:00:49.079 align:start position:0% also not just for regular users but but 00:00:49.079 --> 00:00:51.430 align:start position:0% also not just for regular users but but for<00:00:49.480> uh<00:00:49.559> rollups<00:00:50.480> uh<00:00:50.559> whose<00:00:50.760> interrupt<00:00:51.239> speed 00:00:51.430 --> 00:00:51.440 align:start position:0% for uh rollups uh whose interrupt speed 00:00:51.440 --> 00:00:52.910 align:start position:0% for uh rollups uh whose interrupt speed is<00:00:51.600> essentially<00:00:51.960> bottlenecked<00:00:52.559> by<00:00:52.719> the 00:00:52.910 --> 00:00:52.920 align:start position:0% is essentially bottlenecked by the 00:00:52.920 --> 00:00:55.270 align:start position:0% is essentially bottlenecked by the finality<00:00:53.359> time<00:00:53.520> on<00:00:53.680> L1<00:00:54.600> but<00:00:54.760> this<00:00:54.840> is<00:00:55.000> not<00:00:55.160> the 00:00:55.270 --> 00:00:55.280 align:start position:0% finality time on L1 but this is not the 00:00:55.280 --> 00:00:57.029 align:start position:0% finality time on L1 but this is not the only<00:00:55.520> motivation<00:00:56.039> actually<00:00:56.280> for<00:00:56.440> a<00:00:56.680> faster 00:00:57.029 --> 00:00:57.039 align:start position:0% only motivation actually for a faster 00:00:57.039 --> 00:00:59.509 align:start position:0% only motivation actually for a faster finality<00:00:57.719> road<00:00:58.000> map<00:00:58.680> uh<00:00:58.760> one<00:00:58.960> reason<00:00:59.199> is<00:00:59.320> also 00:00:59.509 --> 00:00:59.519 align:start position:0% finality road map uh one reason is also 00:00:59.519 --> 00:01:01.630 align:start position:0% finality road map uh one reason is also just<00:00:59.600> to<00:01:00.239> improve<00:01:00.600> the<00:01:00.760> consensus<00:01:01.239> protocol 00:01:01.630 --> 00:01:01.640 align:start position:0% just to improve the consensus protocol 00:01:01.640 --> 00:01:03.590 align:start position:0% just to improve the consensus protocol that<00:01:01.760> we<00:01:01.879> have<00:01:02.039> and<00:01:02.199> kind<00:01:02.320> of<00:01:02.440> fix<00:01:02.760> some<00:01:03.440> uh 00:01:03.590 --> 00:01:03.600 align:start position:0% that we have and kind of fix some uh 00:01:03.600 --> 00:01:05.710 align:start position:0% that we have and kind of fix some uh essentially<00:01:04.040> security<00:01:04.760> uh<00:01:04.960> problems<00:01:05.560> that 00:01:05.710 --> 00:01:05.720 align:start position:0% essentially security uh problems that 00:01:05.720 --> 00:01:07.789 align:start position:0% essentially security uh problems that that<00:01:05.840> exist<00:01:06.119> in<00:01:06.240> it<00:01:06.680> not<00:01:06.920> really<00:01:07.439> uh<00:01:07.520> you<00:01:07.600> know 00:01:07.789 --> 00:01:07.799 align:start position:0% that exist in it not really uh you know 00:01:07.799 --> 00:01:10.270 align:start position:0% that exist in it not really uh you know critical<00:01:08.200> security<00:01:08.560> problems<00:01:08.840> were<00:01:09.040> more<00:01:09.759> um 00:01:10.270 --> 00:01:10.280 align:start position:0% critical security problems were more um 00:01:10.280 --> 00:01:12.749 align:start position:0% critical security problems were more um B<00:01:10.439> basically<00:01:10.759> going<00:01:11.159> from<00:01:12.159> uh<00:01:12.360> the<00:01:12.680> the 00:01:12.749 --> 00:01:12.759 align:start position:0% B basically going from uh the the 00:01:12.759 --> 00:01:14.109 align:start position:0% B basically going from uh the the current<00:01:13.080> security<00:01:13.400> proper<00:01:13.720> that<00:01:13.840> we<00:01:13.960> have 00:01:14.109 --> 00:01:14.119 align:start position:0% current security proper that we have 00:01:14.119 --> 00:01:15.550 align:start position:0% current security proper that we have which<00:01:14.240> are<00:01:14.400> suboptimal<00:01:15.040> to<00:01:15.200> really<00:01:15.400> like 00:01:15.550 --> 00:01:15.560 align:start position:0% which are suboptimal to really like 00:01:15.560 --> 00:01:17.630 align:start position:0% which are suboptimal to really like Optimal<00:01:16.040> like<00:01:16.200> provable<00:01:16.640> security 00:01:17.630 --> 00:01:17.640 align:start position:0% Optimal like provable security 00:01:17.640 --> 00:01:20.590 align:start position:0% Optimal like provable security properties<00:01:18.640> and<00:01:19.000> uh<00:01:19.119> yeah<00:01:19.280> one<00:01:19.520> question<00:01:20.520> that 00:01:20.590 --> 00:01:20.600 align:start position:0% properties and uh yeah one question that 00:01:20.600 --> 00:01:22.109 align:start position:0% properties and uh yeah one question that should<00:01:20.799> come<00:01:20.920> to<00:01:21.079> you<00:01:21.200> is<00:01:21.560> why<00:01:21.680> don't<00:01:21.880> we<00:01:22.000> just 00:01:22.109 --> 00:01:22.119 align:start position:0% should come to you is why don't we just 00:01:22.119 --> 00:01:24.630 align:start position:0% should come to you is why don't we just do<00:01:22.360> it<00:01:23.000> immediately<00:01:23.680> and<00:01:23.960> the<00:01:24.040> main<00:01:24.320> reason 00:01:24.630 --> 00:01:24.640 align:start position:0% do it immediately and the main reason 00:01:24.640 --> 00:01:26.830 align:start position:0% do it immediately and the main reason why<00:01:24.840> we<00:01:25.000> can't<00:01:25.759> uh<00:01:25.920> in<00:01:26.040> the<00:01:26.159> in<00:01:26.240> the<00:01:26.320> short<00:01:26.560> term 00:01:26.830 --> 00:01:26.840 align:start position:0% why we can't uh in the in the short term 00:01:26.840 --> 00:01:28.069 align:start position:0% why we can't uh in the in the short term is<00:01:26.960> that<00:01:27.119> we<00:01:27.240> just<00:01:27.360> have<00:01:27.560> way<00:01:27.720> too<00:01:27.880> many 00:01:28.069 --> 00:01:28.079 align:start position:0% is that we just have way too many 00:01:28.079 --> 00:01:29.910 align:start position:0% is that we just have way too many validators<00:01:28.720> we<00:01:28.840> have<00:01:28.960> 1<00:01:29.119> million<00:01:29.439> plus<00:01:29.640> valid 00:01:29.910 --> 00:01:29.920 align:start position:0% validators we have 1 million plus valid 00:01:29.920 --> 00:01:32.030 align:start position:0% validators we have 1 million plus valid validators<00:01:30.640> I<00:01:30.720> think<00:01:30.880> it's<00:01:31.079> almost<00:01:31.479> like<00:01:31.880> uh 00:01:32.030 --> 00:01:32.040 align:start position:0% validators I think it's almost like uh 00:01:32.040 --> 00:01:34.190 align:start position:0% validators I think it's almost like uh another<00:01:32.439> 100,000<00:01:32.960> on<00:01:33.119> top<00:01:33.280> of<00:01:33.399> that<00:01:33.840> it's<00:01:34.000> just 00:01:34.190 --> 00:01:34.200 align:start position:0% another 100,000 on top of that it's just 00:01:34.200 --> 00:01:36.149 align:start position:0% another 100,000 on top of that it's just way<00:01:34.360> too<00:01:34.560> many<00:01:34.840> to<00:01:35.240> just<00:01:35.560> consistently 00:01:36.149 --> 00:01:36.159 align:start position:0% way too many to just consistently 00:01:36.159 --> 00:01:38.510 align:start position:0% way too many to just consistently aggregate<00:01:36.560> in<00:01:36.680> each<00:01:36.840> slot<00:01:37.720> uh<00:01:37.880> and<00:01:38.040> it's<00:01:38.360> yeah 00:01:38.510 --> 00:01:38.520 align:start position:0% aggregate in each slot uh and it's yeah 00:01:38.520 --> 00:01:39.789 align:start position:0% aggregate in each slot uh and it's yeah this<00:01:38.680> essentially<00:01:39.079> is<00:01:39.479> a<00:01:39.560> lot<00:01:39.680> of 00:01:39.789 --> 00:01:39.799 align:start position:0% this essentially is a lot of 00:01:39.799 --> 00:01:41.429 align:start position:0% this essentially is a lot of verification<00:01:40.360> time<00:01:40.520> for<00:01:40.680> the<00:01:40.840> signature<00:01:41.320> and 00:01:41.429 --> 00:01:41.439 align:start position:0% verification time for the signature and 00:01:41.439 --> 00:01:44.030 align:start position:0% verification time for the signature and a<00:01:41.560> lot<00:01:41.640> of<00:01:41.759> bandwidth<00:01:42.200> to<00:01:42.320> propagate<00:01:42.759> them<00:01:43.720> um 00:01:44.030 --> 00:01:44.040 align:start position:0% a lot of bandwidth to propagate them um 00:01:44.040 --> 00:01:45.350 align:start position:0% a lot of bandwidth to propagate them um the<00:01:44.159> thing<00:01:44.280> is<00:01:44.439> we<00:01:44.560> don't<00:01:44.719> actually<00:01:45.000> have<00:01:45.200> 1 00:01:45.350 --> 00:01:45.360 align:start position:0% the thing is we don't actually have 1 00:01:45.360 --> 00:01:48.069 align:start position:0% the thing is we don't actually have 1 million<00:01:45.640> validators<00:01:46.240> we<00:01:46.399> have<00:01:46.719> maybe<00:01:47.520> 10,000 00:01:48.069 --> 00:01:48.079 align:start position:0% million validators we have maybe 10,000 00:01:48.079 --> 00:01:50.109 align:start position:0% million validators we have maybe 10,000 nodes<00:01:48.560> it's<00:01:48.920> the<00:01:49.040> exact<00:01:49.320> number<00:01:49.520> is<00:01:49.640> not<00:01:49.799> clear 00:01:50.109 --> 00:01:50.119 align:start position:0% nodes it's the exact number is not clear 00:01:50.119 --> 00:01:52.429 align:start position:0% nodes it's the exact number is not clear but<00:01:50.320> something<00:01:50.719> on<00:01:50.880> that<00:01:51.000> order<00:01:51.439> magnitude 00:01:52.429 --> 00:01:52.439 align:start position:0% but something on that order magnitude 00:01:52.439 --> 00:01:54.069 align:start position:0% but something on that order magnitude and<00:01:52.880> we<00:01:53.159> we<00:01:53.280> already<00:01:53.479> know<00:01:53.640> that<00:01:53.759> we<00:01:53.920> can 00:01:54.069 --> 00:01:54.079 align:start position:0% and we we already know that we can 00:01:54.079 --> 00:01:56.270 align:start position:0% and we we already know that we can handle<00:01:54.399> more<00:01:54.600> than<00:01:54.799> that<00:01:55.000> per<00:01:55.159> slot<00:01:55.920> uh<00:01:56.000> so<00:01:56.159> we 00:01:56.270 --> 00:01:56.280 align:start position:0% handle more than that per slot uh so we 00:01:56.280 --> 00:01:58.270 align:start position:0% handle more than that per slot uh so we already<00:01:56.600> have<00:01:56.840> Committees<00:01:57.280> of<00:01:57.479> around<00:01:57.759> 30,000 00:01:58.270 --> 00:01:58.280 align:start position:0% already have Committees of around 30,000 00:01:58.280 --> 00:02:00.190 align:start position:0% already have Committees of around 30,000 validators<00:01:58.759> per<00:01:58.920> slot<00:01:59.159> so<00:01:59.439> that<00:01:59.600> load<00:01:59.960> we<00:02:00.039> know 00:02:00.190 --> 00:02:00.200 align:start position:0% validators per slot so that load we know 00:02:00.200 --> 00:02:04.230 align:start position:0% validators per slot so that load we know we<00:02:00.280> can<00:02:00.399> deal<00:02:00.960> with<00:02:01.960> um<00:02:02.159> oh<00:02:02.320> sorry<00:02:03.119> um<00:02:03.719> yeah<00:02:03.880> so 00:02:04.230 --> 00:02:04.240 align:start position:0% we can deal with um oh sorry um yeah so 00:02:04.240 --> 00:02:05.749 align:start position:0% we can deal with um oh sorry um yeah so one<00:02:04.399> thing<00:02:04.640> that<00:02:04.880> that's<00:02:05.119> coming<00:02:05.360> up<00:02:05.600> that's 00:02:05.749 --> 00:02:05.759 align:start position:0% one thing that that's coming up that's 00:02:05.759 --> 00:02:08.029 align:start position:0% one thing that that's coming up that's going<00:02:05.880> to<00:02:06.000> help<00:02:06.200> us<00:02:06.360> is<00:02:06.520> Max<00:02:06.799> CB<00:02:07.479> the<00:02:07.640> ability 00:02:08.029 --> 00:02:08.039 align:start position:0% going to help us is Max CB the ability 00:02:08.039 --> 00:02:11.029 align:start position:0% going to help us is Max CB the ability for<00:02:08.239> validators<00:02:08.759> to<00:02:08.879> have<00:02:09.080> up<00:02:09.239> to<00:02:09.399> 248<00:02:10.239> e<00:02:10.920> uh 00:02:11.029 --> 00:02:11.039 align:start position:0% for validators to have up to 248 e uh 00:02:11.039 --> 00:02:12.670 align:start position:0% for validators to have up to 248 e uh and<00:02:11.360> to<00:02:11.520> allow<00:02:11.760> for 00:02:12.670 --> 00:02:12.680 align:start position:0% and to allow for 00:02:12.680 --> 00:02:14.910 align:start position:0% and to allow for consolidation<00:02:13.680> and<00:02:13.920> but<00:02:14.239> okay<00:02:14.480> so<00:02:14.640> we<00:02:14.760> have 00:02:14.910 --> 00:02:14.920 align:start position:0% consolidation and but okay so we have 00:02:14.920 --> 00:02:16.630 align:start position:0% consolidation and but okay so we have Max<00:02:15.120> CB<00:02:15.400> in<00:02:15.519> the<00:02:15.640> in<00:02:15.720> the<00:02:15.840> next<00:02:16.000> Fork<00:02:16.360> what<00:02:16.480> else 00:02:16.630 --> 00:02:16.640 align:start position:0% Max CB in the in the next Fork what else 00:02:16.640 --> 00:02:18.790 align:start position:0% Max CB in the in the next Fork what else do<00:02:16.800> we<00:02:16.920> need<00:02:17.319> so<00:02:17.480> first<00:02:17.640> of<00:02:17.760> all<00:02:17.920> we<00:02:18.000> need<00:02:18.200> a<00:02:18.519> a 00:02:18.790 --> 00:02:18.800 align:start position:0% do we need so first of all we need a a 00:02:18.800 --> 00:02:20.710 align:start position:0% do we need so first of all we need a a protocol<00:02:19.480> that<00:02:19.840> actually<00:02:20.160> is<00:02:20.319> like<00:02:20.440> Fast 00:02:20.710 --> 00:02:20.720 align:start position:0% protocol that actually is like Fast 00:02:20.720 --> 00:02:22.350 align:start position:0% protocol that actually is like Fast finalizing<00:02:21.319> and<00:02:21.480> still<00:02:21.680> has<00:02:21.920> all<00:02:22.040> of<00:02:22.200> the 00:02:22.350 --> 00:02:22.360 align:start position:0% finalizing and still has all of the 00:02:22.360 --> 00:02:24.110 align:start position:0% finalizing and still has all of the properties<00:02:22.920> that<00:02:23.120> that<00:02:23.239> we<00:02:23.360> want<00:02:23.720> which<00:02:23.920> is 00:02:24.110 --> 00:02:24.120 align:start position:0% properties that that we want which is 00:02:24.120 --> 00:02:25.670 align:start position:0% properties that that we want which is are<00:02:24.319> are<00:02:24.480> many<00:02:24.840> and<00:02:24.959> we<00:02:25.080> have<00:02:25.200> like<00:02:25.319> a<00:02:25.440> quite 00:02:25.670 --> 00:02:25.680 align:start position:0% are are many and we have like a quite 00:02:25.680 --> 00:02:27.910 align:start position:0% are are many and we have like a quite unique<00:02:26.440> uh<00:02:26.519> sort<00:02:26.720> of<00:02:26.879> model<00:02:27.239> that<00:02:27.400> we<00:02:27.560> operate 00:02:27.910 --> 00:02:27.920 align:start position:0% unique uh sort of model that we operate 00:02:27.920 --> 00:02:29.670 align:start position:0% unique uh sort of model that we operate in<00:02:28.599> and<00:02:28.720> then<00:02:28.879> the<00:02:29.000> other<00:02:29.160> thing<00:02:29.280> that<00:02:29.360> we<00:02:29.480> need 00:02:29.670 --> 00:02:29.680 align:start position:0% in and then the other thing that we need 00:02:29.680 --> 00:02:32.070 align:start position:0% in and then the other thing that we need is<00:02:29.920> is<00:02:30.400> uh<00:02:30.519> validator<00:02:31.000> set<00:02:31.280> capping<00:02:31.760> so<00:02:31.959> we 00:02:32.070 --> 00:02:32.080 align:start position:0% is is uh validator set capping so we 00:02:32.080 --> 00:02:34.910 align:start position:0% is is uh validator set capping so we don't<00:02:32.280> want<00:02:32.519> to<00:02:33.239> um<00:02:33.720> let's<00:02:33.920> say<00:02:34.120> go<00:02:34.319> from<00:02:34.760> 1 00:02:34.910 --> 00:02:34.920 align:start position:0% don't want to um let's say go from 1 00:02:34.920 --> 00:02:37.869 align:start position:0% don't want to um let's say go from 1 million<00:02:35.239> validators<00:02:35.800> to<00:02:36.040> 30,000<00:02:37.040> then<00:02:37.280> we<00:02:37.400> are 00:02:37.869 --> 00:02:37.879 align:start position:0% million validators to 30,000 then we are 00:02:37.879 --> 00:02:39.470 align:start position:0% million validators to 30,000 then we are comfortable<00:02:38.280> that<00:02:38.400> we<00:02:38.519> can<00:02:38.640> handle<00:02:38.920> this<00:02:39.080> load 00:02:39.470 --> 00:02:39.480 align:start position:0% comfortable that we can handle this load 00:02:39.480 --> 00:02:41.869 align:start position:0% comfortable that we can handle this load we<00:02:39.599> turn<00:02:39.800> on<00:02:40.480> uh<00:02:40.599> single<00:02:40.959> s<00:02:41.159> finality<00:02:41.599> or 00:02:41.869 --> 00:02:41.879 align:start position:0% we turn on uh single s finality or 00:02:41.879 --> 00:02:44.350 align:start position:0% we turn on uh single s finality or faster<00:02:42.239> finality<00:02:43.080> and<00:02:43.200> then<00:02:43.360> we<00:02:43.760> round<00:02:44.120> trip 00:02:44.350 --> 00:02:44.360 align:start position:0% faster finality and then we round trip 00:02:44.360 --> 00:02:46.229 align:start position:0% faster finality and then we round trip all<00:02:44.480> the<00:02:44.599> way<00:02:44.760> back<00:02:44.920> to<00:02:45.120> 1<00:02:45.280> million<00:02:45.560> validators 00:02:46.229 --> 00:02:46.239 align:start position:0% all the way back to 1 million validators 00:02:46.239 --> 00:02:48.430 align:start position:0% all the way back to 1 million validators because<00:02:46.440> you<00:02:46.560> know<00:02:46.680> more<00:02:47.159> uh<00:02:47.280> small<00:02:48.040> uh 00:02:48.430 --> 00:02:48.440 align:start position:0% because you know more uh small uh 00:02:48.440 --> 00:02:50.670 align:start position:0% because you know more uh small uh stakers<00:02:48.959> come<00:02:49.159> in<00:02:49.360> or<00:02:49.680> deconsolidate<00:02:50.519> or 00:02:50.670 --> 00:02:50.680 align:start position:0% stakers come in or deconsolidate or 00:02:50.680 --> 00:02:52.110 align:start position:0% stakers come in or deconsolidate or something<00:02:51.000> like<00:02:51.159> that<00:02:51.560> and<00:02:51.680> we're<00:02:51.840> back<00:02:52.000> to 00:02:52.110 --> 00:02:52.120 align:start position:0% something like that and we're back to 00:02:52.120 --> 00:02:54.350 align:start position:0% something like that and we're back to square<00:02:52.400> one<00:02:52.680> and<00:02:52.840> the<00:02:52.959> system<00:02:53.280> actually 00:02:54.350 --> 00:02:54.360 align:start position:0% square one and the system actually 00:02:54.360 --> 00:02:58.270 align:start position:0% square one and the system actually breaks<00:02:55.360> and<00:02:55.840> um<00:02:56.159> yeah<00:02:56.560> the<00:02:56.800> first<00:02:57.440> part<00:02:57.720> of<00:02:58.120> of 00:02:58.270 --> 00:02:58.280 align:start position:0% breaks and um yeah the first part of of 00:02:58.280 --> 00:02:59.910 align:start position:0% breaks and um yeah the first part of of this<00:02:58.480> just<00:02:58.640> the<00:02:58.760> consensus<00:02:59.120> protocol<00:02:59.480> part<00:02:59.599> we 00:02:59.910 --> 00:02:59.920 align:start position:0% this just the consensus protocol part we 00:02:59.920 --> 00:03:01.550 align:start position:0% this just the consensus protocol part we actually<00:03:00.480> have<00:03:00.680> a<00:03:00.800> lot<00:03:00.959> of<00:03:01.080> progress<00:03:01.400> in 00:03:01.550 --> 00:03:01.560 align:start position:0% actually have a lot of progress in 00:03:01.560 --> 00:03:02.910 align:start position:0% actually have a lot of progress in already<00:03:01.959> there's<00:03:02.120> been<00:03:02.280> a<00:03:02.360> lot<00:03:02.480> of<00:03:02.599> work<00:03:02.800> in 00:03:02.910 --> 00:03:02.920 align:start position:0% already there's been a lot of work in 00:03:02.920 --> 00:03:04.309 align:start position:0% already there's been a lot of work in the<00:03:03.040> last<00:03:03.200> two<00:03:03.400> years<00:03:03.599> and<00:03:03.799> we<00:03:03.920> essentially 00:03:04.309 --> 00:03:04.319 align:start position:0% the last two years and we essentially 00:03:04.319 --> 00:03:05.710 align:start position:0% the last two years and we essentially have<00:03:04.480> protocols<00:03:04.920> that<00:03:05.040> we're<00:03:05.280> quite<00:03:05.480> happy 00:03:05.710 --> 00:03:05.720 align:start position:0% have protocols that we're quite happy 00:03:05.720 --> 00:03:08.070 align:start position:0% have protocols that we're quite happy with<00:03:05.959> in<00:03:06.159> in<00:03:06.360> theory<00:03:07.239> uh<00:03:07.360> the<00:03:07.480> second<00:03:07.879> part 00:03:08.070 --> 00:03:08.080 align:start position:0% with in in theory uh the second part 00:03:08.080 --> 00:03:09.830 align:start position:0% with in in theory uh the second part it's<00:03:08.280> it's<00:03:08.400> a<00:03:08.480> bit<00:03:08.599> fresher<00:03:09.000> area<00:03:09.440> but<00:03:09.599> I'll 00:03:09.830 --> 00:03:09.840 align:start position:0% it's it's a bit fresher area but I'll 00:03:09.840 --> 00:03:11.670 align:start position:0% it's it's a bit fresher area but I'll essentially<00:03:10.239> talk<00:03:10.440> to<00:03:10.560> you<00:03:11.000> uh<00:03:11.120> about<00:03:11.440> both 00:03:11.670 --> 00:03:11.680 align:start position:0% essentially talk to you uh about both 00:03:11.680 --> 00:03:13.990 align:start position:0% essentially talk to you uh about both parts<00:03:11.959> in<00:03:12.159> in<00:03:12.239> the<00:03:12.360> rest<00:03:12.519> of<00:03:12.599> the<00:03:12.760> talk<00:03:13.599> so<00:03:13.799> with 00:03:13.990 --> 00:03:14.000 align:start position:0% parts in in the rest of the talk so with 00:03:14.000 --> 00:03:16.070 align:start position:0% parts in in the rest of the talk so with the<00:03:14.200> the<00:03:14.319> first<00:03:14.599> part<00:03:15.120> uh<00:03:15.239> I'll<00:03:15.440> focus<00:03:15.799> on<00:03:15.920> a 00:03:16.070 --> 00:03:16.080 align:start position:0% the the first part uh I'll focus on a 00:03:16.080 --> 00:03:18.869 align:start position:0% the the first part uh I'll focus on a specific<00:03:16.480> protocol<00:03:17.440> which<00:03:17.959> uh<00:03:18.120> We've<00:03:18.360> call 00:03:18.869 --> 00:03:18.879 align:start position:0% specific protocol which uh We've call 00:03:18.879 --> 00:03:21.229 align:start position:0% specific protocol which uh We've call three<00:03:19.159> slot<00:03:19.480> finality<00:03:20.280> so<00:03:20.599> yeah<00:03:20.760> single<00:03:21.000> slot 00:03:21.229 --> 00:03:21.239 align:start position:0% three slot finality so yeah single slot 00:03:21.239 --> 00:03:23.350 align:start position:0% three slot finality so yeah single slot finality<00:03:21.560> is<00:03:21.640> a<00:03:21.799> bit<00:03:21.920> of<00:03:22.360> a<00:03:22.480> meme<00:03:22.879> it<00:03:23.120> doesn't 00:03:23.350 --> 00:03:23.360 align:start position:0% finality is a bit of a meme it doesn't 00:03:23.360 --> 00:03:25.030 align:start position:0% finality is a bit of a meme it doesn't necessarily<00:03:23.680> mean<00:03:24.000> single<00:03:24.319> slot<00:03:24.720> it<00:03:24.879> really 00:03:25.030 --> 00:03:25.040 align:start position:0% necessarily mean single slot it really 00:03:25.040 --> 00:03:28.509 align:start position:0% necessarily mean single slot it really just<00:03:25.159> means<00:03:25.440> like<00:03:25.760> we<00:03:25.879> want<00:03:26.040> to<00:03:26.159> have<00:03:26.319> faster 00:03:28.509 --> 00:03:28.519 align:start position:0% just means like we want to have faster 00:03:28.519 --> 00:03:31.309 align:start position:0% just means like we want to have faster finality<00:03:29.519> and<00:03:29.920> yeah<00:03:30.040> so<00:03:30.239> what<00:03:30.360> is<00:03:30.920> uh<00:03:31.200> what 00:03:31.309 --> 00:03:31.319 align:start position:0% finality and yeah so what is uh what 00:03:31.319 --> 00:03:33.589 align:start position:0% finality and yeah so what is uh what does<00:03:31.840> roughly<00:03:32.519> this<00:03:32.680> three<00:03:32.920> slot<00:03:33.159> finality 00:03:33.589 --> 00:03:33.599 align:start position:0% does roughly this three slot finality 00:03:33.599 --> 00:03:35.949 align:start position:0% does roughly this three slot finality protocol<00:03:34.040> look<00:03:34.239> like<00:03:34.920> it's<00:03:35.120> more<00:03:35.239> or<00:03:35.439> less 00:03:35.949 --> 00:03:35.959 align:start position:0% protocol look like it's more or less 00:03:35.959 --> 00:03:38.229 align:start position:0% protocol look like it's more or less much<00:03:36.159> like<00:03:36.319> the<00:03:36.400> current<00:03:36.680> protocol<00:03:37.519> we<00:03:38.000> really 00:03:38.229 --> 00:03:38.239 align:start position:0% much like the current protocol we really 00:03:38.239 --> 00:03:40.229 align:start position:0% much like the current protocol we really reusing<00:03:38.799> a<00:03:38.879> lot<00:03:39.040> of<00:03:39.159> the<00:03:39.280> same<00:03:39.760> at<00:03:39.840> least<00:03:40.080> like 00:03:40.229 --> 00:03:40.239 align:start position:0% reusing a lot of the same at least like 00:03:40.239 --> 00:03:43.229 align:start position:0% reusing a lot of the same at least like conceptual<00:03:40.720> components<00:03:41.640> so<00:03:41.840> it<00:03:41.959> still<00:03:42.319> has<00:03:42.720> a 00:03:43.229 --> 00:03:43.239 align:start position:0% conceptual components so it still has a 00:03:43.239 --> 00:03:44.990 align:start position:0% conceptual components so it still has a um<00:03:43.480> what<00:03:43.599> we<00:03:43.720> call<00:03:43.920> a<00:03:44.040> dynamically<00:03:44.519> available 00:03:44.990 --> 00:03:45.000 align:start position:0% um what we call a dynamically available 00:03:45.000 --> 00:03:46.869 align:start position:0% um what we call a dynamically available component<00:03:45.920> which<00:03:46.000> is<00:03:46.200> essentially<00:03:46.640> like<00:03:46.760> a 00:03:46.869 --> 00:03:46.879 align:start position:0% component which is essentially like a 00:03:46.879 --> 00:03:49.390 align:start position:0% component which is essentially like a lmy<00:03:47.239> ghost<00:03:47.720> which<00:03:47.840> is<00:03:47.959> what<00:03:48.120> we<00:03:48.239> have<00:03:48.400> today<00:03:49.239> um 00:03:49.390 --> 00:03:49.400 align:start position:0% lmy ghost which is what we have today um 00:03:49.400 --> 00:03:50.630 align:start position:0% lmy ghost which is what we have today um and<00:03:49.519> this<00:03:49.599> is<00:03:49.720> the<00:03:49.840> part<00:03:50.040> that's<00:03:50.239> supposed<00:03:50.519> to 00:03:50.630 --> 00:03:50.640 align:start position:0% and this is the part that's supposed to 00:03:50.640 --> 00:03:52.630 align:start position:0% and this is the part that's supposed to keep<00:03:50.840> working<00:03:51.239> even<00:03:51.439> if<00:03:51.560> we<00:03:51.720> cannot<00:03:52.000> finalize 00:03:52.630 --> 00:03:52.640 align:start position:0% keep working even if we cannot finalize 00:03:52.640 --> 00:03:55.069 align:start position:0% keep working even if we cannot finalize for<00:03:52.920> essentially<00:03:53.319> extra<00:03:54.000> resilience<00:03:55.000> and 00:03:55.069 --> 00:03:55.079 align:start position:0% for essentially extra resilience and 00:03:55.079 --> 00:03:57.069 align:start position:0% for essentially extra resilience and then<00:03:55.200> we<00:03:55.319> also<00:03:55.519> have<00:03:55.680> Casper<00:03:56.079> 5G<00:03:56.799> uh<00:03:56.920> this 00:03:57.069 --> 00:03:57.079 align:start position:0% then we also have Casper 5G uh this 00:03:57.079 --> 00:03:58.990 align:start position:0% then we also have Casper 5G uh this finality<00:03:57.560> Gadget<00:03:58.040> that<00:03:58.280> eventually<00:03:58.640> gives<00:03:58.840> us 00:03:58.990 --> 00:03:59.000 align:start position:0% finality Gadget that eventually gives us 00:03:59.000 --> 00:04:01.470 align:start position:0% finality Gadget that eventually gives us Economic<00:03:59.360> Security<00:04:00.040> as<00:04:00.159> long<00:04:00.360> as<00:04:00.879> two3<00:04:01.319> of<00:04:01.400> the 00:04:01.470 --> 00:04:01.480 align:start position:0% Economic Security as long as two3 of the 00:04:01.480 --> 00:04:05.110 align:start position:0% Economic Security as long as two3 of the de<00:04:01.599> validator<00:04:02.040> set<00:04:02.200> is<00:04:02.799> online<00:04:03.799> and<00:04:04.079> the<00:04:04.200> other 00:04:05.110 --> 00:04:05.120 align:start position:0% de validator set is online and the other 00:04:05.120 --> 00:04:06.350 align:start position:0% de validator set is online and the other another<00:04:05.400> component<00:04:05.840> that's<00:04:06.040> that's<00:04:06.200> quite 00:04:06.350 --> 00:04:06.360 align:start position:0% another component that's that's quite 00:04:06.360 --> 00:04:09.069 align:start position:0% another component that's that's quite different<00:04:06.599> from<00:04:06.760> today<00:04:07.599> is<00:04:07.760> that<00:04:08.239> um<00:04:08.920> well 00:04:09.069 --> 00:04:09.079 align:start position:0% different from today is that um well 00:04:09.079 --> 00:04:10.429 align:start position:0% different from today is that um well first<00:04:09.239> of<00:04:09.360> all<00:04:09.519> we<00:04:09.799> we<00:04:09.879> would<00:04:10.040> be<00:04:10.159> able<00:04:10.319> to 00:04:10.429 --> 00:04:10.439 align:start position:0% first of all we we would be able to 00:04:10.439 --> 00:04:12.069 align:start position:0% first of all we we would be able to finalize<00:04:10.840> fast<00:04:11.239> but<00:04:11.360> specifically<00:04:11.840> we<00:04:11.920> would 00:04:12.069 --> 00:04:12.079 align:start position:0% finalize fast but specifically we would 00:04:12.079 --> 00:04:14.030 align:start position:0% finalize fast but specifically we would be<00:04:12.200> able<00:04:12.319> to<00:04:12.439> finalize<00:04:12.840> in<00:04:13.000> three<00:04:13.200> slots<00:04:13.879> with 00:04:14.030 --> 00:04:14.040 align:start position:0% be able to finalize in three slots with 00:04:14.040 --> 00:04:16.749 align:start position:0% be able to finalize in three slots with finality<00:04:14.519> being<00:04:14.799> pipelined<00:04:15.400> so<00:04:15.599> that<00:04:16.479> uh<00:04:16.639> you 00:04:16.749 --> 00:04:16.759 align:start position:0% finality being pipelined so that uh you 00:04:16.759 --> 00:04:17.949 align:start position:0% finality being pipelined so that uh you know<00:04:16.880> you<00:04:17.000> don't<00:04:17.199> need<00:04:17.359> you<00:04:17.479> need<00:04:17.639> multiple 00:04:17.949 --> 00:04:17.959 align:start position:0% know you don't need you need multiple 00:04:17.959 --> 00:04:19.509 align:start position:0% know you don't need you need multiple voting<00:04:18.239> rounds<00:04:18.479> for<00:04:18.720> finality<00:04:19.239> but<00:04:19.400> these 00:04:19.509 --> 00:04:19.519 align:start position:0% voting rounds for finality but these 00:04:19.519 --> 00:04:22.110 align:start position:0% voting rounds for finality but these would<00:04:19.720> be<00:04:20.720> essentially<00:04:21.079> pipeline<00:04:21.560> over<00:04:22.000> uh 00:04:22.110 --> 00:04:22.120 align:start position:0% would be essentially pipeline over uh 00:04:22.120 --> 00:04:24.310 align:start position:0% would be essentially pipeline over uh multiple<00:04:22.479> slots<00:04:23.120> and<00:04:23.360> so<00:04:23.479> that<00:04:23.639> we<00:04:23.880> can<00:04:24.080> still 00:04:24.310 --> 00:04:24.320 align:start position:0% multiple slots and so that we can still 00:04:24.320 --> 00:04:28.310 align:start position:0% multiple slots and so that we can still have<00:04:24.520> blocks<00:04:24.880> coming<00:04:25.120> in<00:04:25.680> in<00:04:25.800> between<00:04:26.080> these 00:04:28.310 --> 00:04:28.320 align:start position:0% 00:04:28.320 --> 00:04:30.710 align:start position:0% rounds<00:04:29.320> uh<00:04:29.400> so<00:04:29.759> yeah<00:04:29.960> this<00:04:30.240> this<00:04:30.360> is<00:04:30.479> what<00:04:30.600> it 00:04:30.710 --> 00:04:30.720 align:start position:0% rounds uh so yeah this this is what it 00:04:30.720 --> 00:04:32.629 align:start position:0% rounds uh so yeah this this is what it would<00:04:30.880> look<00:04:31.080> like<00:04:31.560> uh<00:04:31.639> we<00:04:31.759> have<00:04:31.880> a<00:04:32.000> first<00:04:32.199> slot 00:04:32.629 --> 00:04:32.639 align:start position:0% would look like uh we have a first slot 00:04:32.639 --> 00:04:34.909 align:start position:0% would look like uh we have a first slot a<00:04:32.759> block<00:04:33.000> comes<00:04:33.199> in<00:04:33.400> just<00:04:33.560> like<00:04:33.759> today<00:04:34.680> we<00:04:34.800> have 00:04:34.909 --> 00:04:34.919 align:start position:0% a block comes in just like today we have 00:04:34.919 --> 00:04:37.670 align:start position:0% a block comes in just like today we have a<00:04:35.039> first<00:04:35.240> round<00:04:35.479> of<00:04:35.600> votes<00:04:36.400> um<00:04:36.840> at<00:04:37.000> first<00:04:37.520> uh 00:04:37.670 --> 00:04:37.680 align:start position:0% a first round of votes um at first uh 00:04:37.680 --> 00:04:39.070 align:start position:0% a first round of votes um at first uh you<00:04:37.759> know<00:04:37.880> votes<00:04:38.240> just<00:04:38.400> like<00:04:38.600> today<00:04:38.880> have 00:04:39.070 --> 00:04:39.080 align:start position:0% you know votes just like today have 00:04:39.080 --> 00:04:41.230 align:start position:0% you know votes just like today have three<00:04:39.320> components<00:04:39.880> a<00:04:40.080> source<00:04:40.440> a<00:04:40.600> Target<00:04:41.120> which 00:04:41.230 --> 00:04:41.240 align:start position:0% three components a source a Target which 00:04:41.240 --> 00:04:43.909 align:start position:0% three components a source a Target which are<00:04:41.600> Casper<00:04:42.000> 5G<00:04:42.360> Concepts<00:04:42.960> and<00:04:43.080> a<00:04:43.280> head<00:04:43.720> which 00:04:43.909 --> 00:04:43.919 align:start position:0% are Casper 5G Concepts and a head which 00:04:43.919 --> 00:04:45.749 align:start position:0% are Casper 5G Concepts and a head which just<00:04:44.039> says<00:04:44.479> this<00:04:44.600> is<00:04:44.759> the<00:04:44.880> thing<00:04:45.120> that<00:04:45.280> I<00:04:45.600> uh 00:04:45.749 --> 00:04:45.759 align:start position:0% just says this is the thing that I uh 00:04:45.759 --> 00:04:48.070 align:start position:0% just says this is the thing that I uh beli<00:04:46.080> to<00:04:46.160> be<00:04:46.280> the<00:04:46.400> head<00:04:46.520> of<00:04:46.639> the<00:04:46.720> chain<00:04:47.720> um<00:04:47.960> at 00:04:48.070 --> 00:04:48.080 align:start position:0% beli to be the head of the chain um at 00:04:48.080 --> 00:04:49.390 align:start position:0% beli to be the head of the chain um at first<00:04:48.280> we<00:04:48.360> would<00:04:48.520> only<00:04:48.680> care<00:04:48.880> about<00:04:49.120> the<00:04:49.240> this 00:04:49.390 --> 00:04:49.400 align:start position:0% first we would only care about the this 00:04:49.400 --> 00:04:51.150 align:start position:0% first we would only care about the this head<00:04:49.560> vote<00:04:49.919> which<00:04:50.000> would<00:04:50.160> be<00:04:50.240> for<00:04:50.440> B<00:04:50.919> in<00:04:51.039> the 00:04:51.150 --> 00:04:51.160 align:start position:0% head vote which would be for B in the 00:04:51.160 --> 00:04:53.310 align:start position:0% head vote which would be for B in the ideal<00:04:51.560> case<00:04:52.360> then<00:04:52.520> we<00:04:52.639> would<00:04:52.800> move<00:04:52.960> on<00:04:53.080> to<00:04:53.199> the 00:04:53.310 --> 00:04:53.320 align:start position:0% ideal case then we would move on to the 00:04:53.320 --> 00:04:56.710 align:start position:0% ideal case then we would move on to the next<00:04:53.479> slot<00:04:54.320> new<00:04:54.520> block<00:04:54.759> comes<00:04:54.960> in<00:04:55.320> B<00:04:55.560> Prime<00:04:56.520> uh 00:04:56.710 --> 00:04:56.720 align:start position:0% next slot new block comes in B Prime uh 00:04:56.720 --> 00:04:58.950 align:start position:0% next slot new block comes in B Prime uh now<00:04:57.240> the<00:04:57.440> head<00:04:57.840> the<00:04:58.080> head<00:04:58.280> vote<00:04:58.520> would<00:04:58.639> be<00:04:58.759> for 00:04:58.950 --> 00:04:58.960 align:start position:0% now the head the head vote would be for 00:04:58.960 --> 00:05:00.710 align:start position:0% now the head the head vote would be for B<00:04:59.160> Prime<00:04:59.680> so<00:04:59.759> we've<00:04:59.880> moved<00:05:00.080> on<00:05:00.240> to<00:05:00.400> to<00:05:00.560> this 00:05:00.710 --> 00:05:00.720 align:start position:0% B Prime so we've moved on to to this 00:05:00.720 --> 00:05:02.990 align:start position:0% B Prime so we've moved on to to this next<00:05:00.919> block<00:05:01.639> the<00:05:01.800> target<00:05:02.120> vote<00:05:02.440> would<00:05:02.639> now<00:05:02.840> be 00:05:02.990 --> 00:05:03.000 align:start position:0% next block the target vote would now be 00:05:03.000 --> 00:05:05.990 align:start position:0% next block the target vote would now be for<00:05:03.600> the<00:05:03.759> checkpoint<00:05:04.440> BT<00:05:05.240> so<00:05:05.560> you<00:05:05.639> know<00:05:05.800> just 00:05:05.990 --> 00:05:06.000 align:start position:0% for the checkpoint BT so you know just 00:05:06.000 --> 00:05:07.790 align:start position:0% for the checkpoint BT so you know just like<00:05:06.160> today<00:05:06.440> we<00:05:06.560> have<00:05:06.800> this<00:05:07.000> concept<00:05:07.360> of<00:05:07.479> check 00:05:07.790 --> 00:05:07.800 align:start position:0% like today we have this concept of check 00:05:07.800 --> 00:05:09.710 align:start position:0% like today we have this concept of check points<00:05:08.039> that<00:05:08.120> are<00:05:08.280> essentially<00:05:09.199> uh<00:05:09.320> blocks 00:05:09.710 --> 00:05:09.720 align:start position:0% points that are essentially uh blocks 00:05:09.720 --> 00:05:12.469 align:start position:0% points that are essentially uh blocks and<00:05:09.919> EPO<00:05:10.560> for<00:05:10.840> for<00:05:11.360> Casper<00:05:11.720> 5G<00:05:12.120> and<00:05:12.240> these<00:05:12.320> are 00:05:12.469 --> 00:05:12.479 align:start position:0% and EPO for for Casper 5G and these are 00:05:12.479 --> 00:05:14.029 align:start position:0% and EPO for for Casper 5G and these are the<00:05:12.639> objects<00:05:12.960> that<00:05:13.120> we<00:05:13.360> essentially<00:05:13.840> do 00:05:14.029 --> 00:05:14.039 align:start position:0% the objects that we essentially do 00:05:14.039 --> 00:05:15.830 align:start position:0% the objects that we essentially do finality<00:05:14.560> over<00:05:15.080> here<00:05:15.240> we<00:05:15.320> would<00:05:15.479> have<00:05:15.600> these 00:05:15.830 --> 00:05:15.840 align:start position:0% finality over here we would have these 00:05:15.840 --> 00:05:19.390 align:start position:0% finality over here we would have these like<00:05:16.039> block<00:05:16.479> slot<00:05:17.160> checkpoints<00:05:18.160> uh<00:05:18.280> so<00:05:19.039> a<00:05:19.160> vote 00:05:19.390 --> 00:05:19.400 align:start position:0% like block slot checkpoints uh so a vote 00:05:19.400 --> 00:05:21.350 align:start position:0% like block slot checkpoints uh so a vote for<00:05:19.639> BT<00:05:20.080> as<00:05:20.199> a<00:05:20.360> Target<00:05:20.680> would<00:05:20.880> essentially<00:05:21.240> be 00:05:21.350 --> 00:05:21.360 align:start position:0% for BT as a Target would essentially be 00:05:21.360 --> 00:05:23.909 align:start position:0% for BT as a Target would essentially be trying<00:05:21.560> to<00:05:21.720> say<00:05:22.479> I<00:05:22.600> think<00:05:22.840> that<00:05:23.039> b<00:05:23.360> is<00:05:23.479> ready<00:05:23.800> to 00:05:23.909 --> 00:05:23.919 align:start position:0% trying to say I think that b is ready to 00:05:23.919 --> 00:05:26.629 align:start position:0% trying to say I think that b is ready to be<00:05:24.080> finalized<00:05:25.039> uh<00:05:25.160> or<00:05:25.840> to<00:05:26.000> be<00:05:26.120> to<00:05:26.240> enter<00:05:26.479> the 00:05:26.629 --> 00:05:26.639 align:start position:0% be finalized uh or to be to enter the 00:05:26.639 --> 00:05:29.830 align:start position:0% be finalized uh or to be to enter the finality<00:05:27.120> pipeline<00:05:27.919> essentially<00:05:28.919> uh<00:05:29.160> then<00:05:29.720> we 00:05:29.830 --> 00:05:29.840 align:start position:0% finality pipeline essentially uh then we 00:05:29.840 --> 00:05:32.070 align:start position:0% finality pipeline essentially uh then we move<00:05:30.000> on<00:05:30.160> to<00:05:30.520> the<00:05:30.680> next<00:05:30.880> slot<00:05:31.479> uh<00:05:31.560> we<00:05:31.680> get<00:05:31.800> a<00:05:31.919> b 00:05:32.070 --> 00:05:32.080 align:start position:0% move on to the next slot uh we get a b 00:05:32.080 --> 00:05:34.790 align:start position:0% move on to the next slot uh we get a b double<00:05:32.400> Prime<00:05:32.800> again<00:05:33.080> this<00:05:33.440> gets<00:05:33.600> a<00:05:33.800> head<00:05:34.000> vote 00:05:34.790 --> 00:05:34.800 align:start position:0% double Prime again this gets a head vote 00:05:34.800 --> 00:05:36.430 align:start position:0% double Prime again this gets a head vote uh<00:05:34.960> now<00:05:35.199> the<00:05:35.319> the<00:05:35.440> target<00:05:35.880> is<00:05:36.039> the<00:05:36.120> one<00:05:36.280> from 00:05:36.430 --> 00:05:36.440 align:start position:0% uh now the the target is the one from 00:05:36.440 --> 00:05:39.230 align:start position:0% uh now the the target is the one from the<00:05:36.600> previous<00:05:36.880> slot<00:05:37.160> so<00:05:37.400> B<00:05:37.680> Prime<00:05:38.080> t+1<00:05:39.080> and 00:05:39.230 --> 00:05:39.240 align:start position:0% the previous slot so B Prime t+1 and 00:05:39.240 --> 00:05:41.950 align:start position:0% the previous slot so B Prime t+1 and then<00:05:39.520> the<00:05:39.680> source<00:05:40.120> is<00:05:40.360> BT<00:05:41.160> so<00:05:41.319> now<00:05:41.479> this<00:05:41.639> Source 00:05:41.950 --> 00:05:41.960 align:start position:0% then the source is BT so now this Source 00:05:41.960 --> 00:05:44.550 align:start position:0% then the source is BT so now this Source vote<00:05:42.280> is<00:05:42.440> essentially<00:05:42.840> saying<00:05:43.639> I<00:05:43.720> know<00:05:44.000> that<00:05:44.280> b 00:05:44.550 --> 00:05:44.560 align:start position:0% vote is essentially saying I know that b 00:05:44.560 --> 00:05:47.510 align:start position:0% vote is essentially saying I know that b Prime<00:05:45.120> uh<00:05:45.240> sorry<00:05:45.520> that<00:05:45.680> b<00:05:46.120> is<00:05:46.479> Justified<00:05:47.360> and 00:05:47.510 --> 00:05:47.520 align:start position:0% Prime uh sorry that b is Justified and 00:05:47.520 --> 00:05:49.189 align:start position:0% Prime uh sorry that b is Justified and is<00:05:47.680> ready<00:05:47.880> to<00:05:48.120> actually<00:05:48.319> be<00:05:48.479> finalized<00:05:49.080> and 00:05:49.189 --> 00:05:49.199 align:start position:0% is ready to actually be finalized and 00:05:49.199 --> 00:05:51.950 align:start position:0% is ready to actually be finalized and we're<00:05:49.400> kind<00:05:49.520> of<00:05:50.120> getting<00:05:50.360> to<00:05:50.560> the<00:05:50.680> end<00:05:50.880> of<00:05:51.280> the 00:05:51.950 --> 00:05:51.960 align:start position:0% we're kind of getting to the end of the 00:05:51.960 --> 00:05:54.230 align:start position:0% we're kind of getting to the end of the finality<00:05:52.479> pipeline<00:05:52.840> for<00:05:53.039> B<00:05:53.800> but<00:05:53.960> as<00:05:54.039> you<00:05:54.120> can 00:05:54.230 --> 00:05:54.240 align:start position:0% finality pipeline for B but as you can 00:05:54.240 --> 00:05:56.029 align:start position:0% finality pipeline for B but as you can see<00:05:54.560> the<00:05:54.720> there's<00:05:55.240> three<00:05:55.520> things<00:05:55.800> kind<00:05:55.919> of 00:05:56.029 --> 00:05:56.039 align:start position:0% see the there's three things kind of 00:05:56.039 --> 00:05:58.909 align:start position:0% see the there's three things kind of going<00:05:56.240> on<00:05:56.400> at<00:05:56.560> once<00:05:57.319> uh<00:05:57.520> the<00:05:57.759> the<00:05:58.440> you<00:05:58.520> know<00:05:58.680> B 00:05:58.909 --> 00:05:58.919 align:start position:0% going on at once uh the the you know B 00:05:58.919 --> 00:06:00.670 align:start position:0% going on at once uh the the you know B is<00:05:59.120> enters<00:05:59.440> the<00:05:59.680> finality<00:06:00.080> pipeline<00:06:00.440> at<00:06:00.560> the 00:06:00.670 --> 00:06:00.680 align:start position:0% is enters the finality pipeline at the 00:06:00.680 --> 00:06:02.990 align:start position:0% is enters the finality pipeline at the beginning<00:06:01.199> then<00:06:01.400> B<00:06:01.639> Prime<00:06:01.960> enters<00:06:02.639> in<00:06:02.800> the<00:06:02.919> in 00:06:02.990 --> 00:06:03.000 align:start position:0% beginning then B Prime enters in the in 00:06:03.000 --> 00:06:04.909 align:start position:0% beginning then B Prime enters in the in the<00:06:03.120> middle<00:06:03.360> slot<00:06:03.759> and<00:06:03.840> then<00:06:04.000> b<00:06:04.160> double<00:06:04.440> Prime 00:06:04.909 --> 00:06:04.919 align:start position:0% the middle slot and then b double Prime 00:06:04.919 --> 00:06:06.390 align:start position:0% the middle slot and then b double Prime so<00:06:05.160> all<00:06:05.280> of<00:06:05.400> them<00:06:05.520> are<00:06:05.639> in<00:06:05.840> kind<00:06:05.960> of<00:06:06.120> different 00:06:06.390 --> 00:06:06.400 align:start position:0% so all of them are in kind of different 00:06:06.400 --> 00:06:08.589 align:start position:0% so all of them are in kind of different stages<00:06:06.759> of<00:06:06.919> the<00:06:07.080> finality<00:06:07.639> Pipeline<00:06:08.319> and<00:06:08.479> you 00:06:08.589 --> 00:06:08.599 align:start position:0% stages of the finality Pipeline and you 00:06:08.599 --> 00:06:10.550 align:start position:0% stages of the finality Pipeline and you can<00:06:09.120> that's<00:06:09.319> reflected<00:06:09.800> by<00:06:10.000> the<00:06:10.160> kinds<00:06:10.400> of 00:06:10.550 --> 00:06:10.560 align:start position:0% can that's reflected by the kinds of 00:06:10.560 --> 00:06:13.230 align:start position:0% can that's reflected by the kinds of votes<00:06:10.960> that<00:06:11.120> they<00:06:11.599> receive<00:06:12.599> uh<00:06:12.720> and<00:06:13.039> yeah 00:06:13.230 --> 00:06:13.240 align:start position:0% votes that they receive uh and yeah 00:06:13.240 --> 00:06:15.469 align:start position:0% votes that they receive uh and yeah essentially<00:06:14.000> the<00:06:14.360> the<00:06:14.520> this<00:06:14.680> pipeline<00:06:15.039> for<00:06:15.199> B 00:06:15.469 --> 00:06:15.479 align:start position:0% essentially the the this pipeline for B 00:06:15.479 --> 00:06:17.270 align:start position:0% essentially the the this pipeline for B would<00:06:15.680> look<00:06:15.880> like<00:06:16.080> this<00:06:16.400> in<00:06:16.599> already<00:06:16.960> after 00:06:17.270 --> 00:06:17.280 align:start position:0% would look like this in already after 00:06:17.280 --> 00:06:18.870 align:start position:0% would look like this in already after the<00:06:17.400> first<00:06:17.639> round<00:06:17.880> of<00:06:18.000> voting<00:06:18.440> we<00:06:18.560> could 00:06:18.870 --> 00:06:18.880 align:start position:0% the first round of voting we could 00:06:18.880 --> 00:06:20.790 align:start position:0% the first round of voting we could confirm<00:06:19.280> it<00:06:19.759> at<00:06:19.880> this<00:06:20.039> point<00:06:20.240> we<00:06:20.360> have<00:06:20.599> no 00:06:20.790 --> 00:06:20.800 align:start position:0% confirm it at this point we have no 00:06:20.800 --> 00:06:22.710 align:start position:0% confirm it at this point we have no Economic<00:06:21.240> Security<00:06:21.759> but<00:06:21.880> we<00:06:22.000> already<00:06:22.280> have 00:06:22.710 --> 00:06:22.720 align:start position:0% Economic Security but we already have 00:06:22.720 --> 00:06:24.110 align:start position:0% Economic Security but we already have very<00:06:23.000> strong<00:06:23.160> guarantee<00:06:23.599> that<00:06:23.800> it's<00:06:23.960> not 00:06:24.110 --> 00:06:24.120 align:start position:0% very strong guarantee that it's not 00:06:24.120 --> 00:06:26.270 align:start position:0% very strong guarantee that it's not going<00:06:24.240> to<00:06:24.360> be<00:06:24.479> reorg<00:06:25.440> after<00:06:25.680> the<00:06:25.800> second<00:06:26.080> round 00:06:26.270 --> 00:06:26.280 align:start position:0% going to be reorg after the second round 00:06:26.280 --> 00:06:27.909 align:start position:0% going to be reorg after the second round of<00:06:26.440> voting<00:06:26.800> once<00:06:26.960> we've<00:06:27.160> gotten<00:06:27.400> these<00:06:27.560> Target 00:06:27.909 --> 00:06:27.919 align:start position:0% of voting once we've gotten these Target 00:06:27.919 --> 00:06:31.350 align:start position:0% of voting once we've gotten these Target votes<00:06:28.680> uh<00:06:28.840> b<00:06:29.240> b<00:06:29.360> would<00:06:29.680> be<00:06:30.080> um<00:06:30.319> Justified<00:06:31.199> and 00:06:31.350 --> 00:06:31.360 align:start position:0% votes uh b b would be um Justified and 00:06:31.360 --> 00:06:32.950 align:start position:0% votes uh b b would be um Justified and after<00:06:31.560> the<00:06:31.720> third<00:06:31.919> round<00:06:32.120> of<00:06:32.240> voting<00:06:32.599> after<00:06:32.800> we 00:06:32.950 --> 00:06:32.960 align:start position:0% after the third round of voting after we 00:06:32.960 --> 00:06:34.749 align:start position:0% after the third round of voting after we gotten<00:06:33.280> all<00:06:33.360> of<00:06:33.479> the<00:06:33.599> source<00:06:33.880> votes<00:06:34.479> it<00:06:34.560> would 00:06:34.749 --> 00:06:34.759 align:start position:0% gotten all of the source votes it would 00:06:34.759 --> 00:06:36.309 align:start position:0% gotten all of the source votes it would be 00:06:36.309 --> 00:06:36.319 align:start position:0% be 00:06:36.319 --> 00:06:38.830 align:start position:0% be finalized<00:06:37.319> and<00:06:37.720> yeah<00:06:37.880> actually<00:06:38.319> we<00:06:38.639> don't 00:06:38.830 --> 00:06:38.840 align:start position:0% finalized and yeah actually we don't 00:06:38.840 --> 00:06:41.629 align:start position:0% finalized and yeah actually we don't even<00:06:39.039> need<00:06:39.199> to<00:06:39.400> think<00:06:39.960> about<00:06:40.240> the<00:06:40.560> blocks<00:06:41.560> you 00:06:41.629 --> 00:06:41.639 align:start position:0% even need to think about the blocks you 00:06:41.639 --> 00:06:43.790 align:start position:0% even need to think about the blocks you know<00:06:41.759> B<00:06:42.000> Prime<00:06:42.240> and<00:06:42.479> B<00:06:42.840> Double<00:06:43.120> Prime<00:06:43.400> existing 00:06:43.790 --> 00:06:43.800 align:start position:0% know B Prime and B Double Prime existing 00:06:43.800 --> 00:06:45.469 align:start position:0% know B Prime and B Double Prime existing in<00:06:43.919> the<00:06:44.000> middle<00:06:44.560> we<00:06:44.680> could<00:06:44.840> also<00:06:45.000> just<00:06:45.120> focus 00:06:45.469 --> 00:06:45.479 align:start position:0% in the middle we could also just focus 00:06:45.479 --> 00:06:47.189 align:start position:0% in the middle we could also just focus about<00:06:45.800> the<00:06:45.919> votes<00:06:46.199> that<00:06:46.280> are<00:06:46.440> relevant<00:06:46.800> to<00:06:47.039> to 00:06:47.189 --> 00:06:47.199 align:start position:0% about the votes that are relevant to to 00:06:47.199 --> 00:06:49.150 align:start position:0% about the votes that are relevant to to be<00:06:47.599> so<00:06:47.759> the<00:06:47.919> head<00:06:48.120> vote<00:06:48.400> the<00:06:48.520> target<00:06:48.840> vote<00:06:49.039> and 00:06:49.150 --> 00:06:49.160 align:start position:0% be so the head vote the target vote and 00:06:49.160 --> 00:06:50.629 align:start position:0% be so the head vote the target vote and the<00:06:49.240> source<00:06:49.560> vote<00:06:49.919> if<00:06:50.039> you<00:06:50.160> really<00:06:50.360> just<00:06:50.479> want 00:06:50.629 --> 00:06:50.639 align:start position:0% the source vote if you really just want 00:06:50.639 --> 00:06:52.469 align:start position:0% the source vote if you really just want to<00:06:50.759> focus<00:06:51.039> on<00:06:51.680> uh<00:06:51.880> the<00:06:52.000> essentially<00:06:52.360> the 00:06:52.469 --> 00:06:52.479 align:start position:0% to focus on uh the essentially the 00:06:52.479 --> 00:06:55.390 align:start position:0% to focus on uh the essentially the finality<00:06:52.960> pipeline<00:06:53.759> uh<00:06:53.880> for<00:06:54.160> B<00:06:54.520> specifically 00:06:55.390 --> 00:06:55.400 align:start position:0% finality pipeline uh for B specifically 00:06:55.400 --> 00:06:57.950 align:start position:0% finality pipeline uh for B specifically and<00:06:55.599> even<00:06:55.960> you<00:06:56.080> know<00:06:56.240> if<00:06:56.720> uh<00:06:56.840> B<00:06:57.120> Prime<00:06:57.639> uh<00:06:57.720> b 00:06:57.950 --> 00:06:57.960 align:start position:0% and even you know if uh B Prime uh b 00:06:57.960 --> 00:06:59.830 align:start position:0% and even you know if uh B Prime uh b double<00:06:58.199> Prime<00:06:58.479> like<00:06:58.639> these<00:06:58.840> other<00:06:59.160> blocks<00:06:59.680> in 00:06:59.830 --> 00:06:59.840 align:start position:0% double Prime like these other blocks in 00:06:59.840 --> 00:07:01.830 align:start position:0% double Prime like these other blocks in the<00:07:00.120> subsequent<00:07:00.599> slots<00:07:00.919> were<00:07:01.160> to<00:07:01.280> be<00:07:01.400> missed 00:07:01.830 --> 00:07:01.840 align:start position:0% the subsequent slots were to be missed 00:07:01.840 --> 00:07:03.430 align:start position:0% the subsequent slots were to be missed for<00:07:02.000> example<00:07:02.280> the<00:07:02.400> proposer<00:07:02.879> does<00:07:03.039> not<00:07:03.199> show 00:07:03.430 --> 00:07:03.440 align:start position:0% for example the proposer does not show 00:07:03.440 --> 00:07:05.510 align:start position:0% for example the proposer does not show up<00:07:04.160> uh<00:07:04.240> the<00:07:04.360> protocol<00:07:04.759> actually<00:07:04.960> guarantees 00:07:05.510 --> 00:07:05.520 align:start position:0% up uh the protocol actually guarantees 00:07:05.520 --> 00:07:07.830 align:start position:0% up uh the protocol actually guarantees that<00:07:06.120> B<00:07:06.400> can<00:07:06.520> still<00:07:06.800> complete<00:07:07.199> its<00:07:07.400> pipeline 00:07:07.830 --> 00:07:07.840 align:start position:0% that B can still complete its pipeline 00:07:07.840 --> 00:07:09.710 align:start position:0% that B can still complete its pipeline essentially<00:07:08.240> that<00:07:08.440> like<00:07:08.759> no<00:07:08.960> matter<00:07:09.240> what<00:07:09.520> if 00:07:09.710 --> 00:07:09.720 align:start position:0% essentially that like no matter what if 00:07:09.720 --> 00:07:13.390 align:start position:0% essentially that like no matter what if the<00:07:10.080> uh<00:07:10.280> proposer<00:07:10.879> of<00:07:11.560> uh<00:07:11.680> slot<00:07:12.039> T<00:07:12.479> is<00:07:12.680> honest 00:07:13.390 --> 00:07:13.400 align:start position:0% the uh proposer of uh slot T is honest 00:07:13.400 --> 00:07:15.550 align:start position:0% the uh proposer of uh slot T is honest in<00:07:13.599> in<00:07:14.080> uh<00:07:14.160> you<00:07:14.280> know<00:07:14.440> the<00:07:14.560> way<00:07:14.680> it<00:07:14.840> creates<00:07:15.240> B 00:07:15.550 --> 00:07:15.560 align:start position:0% in in uh you know the way it creates B 00:07:15.560 --> 00:07:17.469 align:start position:0% in in uh you know the way it creates B and<00:07:15.680> sends<00:07:16.080> it<00:07:16.280> in<00:07:16.360> a<00:07:16.479> in<00:07:16.560> a<00:07:16.680> timely<00:07:17.000> manner 00:07:17.469 --> 00:07:17.479 align:start position:0% and sends it in a in a timely manner 00:07:17.479 --> 00:07:19.270 align:start position:0% and sends it in a in a timely manner then<00:07:17.680> B<00:07:17.960> will<00:07:18.199> successfully<00:07:18.720> go<00:07:18.879> through<00:07:19.120> this 00:07:19.270 --> 00:07:19.280 align:start position:0% then B will successfully go through this 00:07:19.280 --> 00:07:21.550 align:start position:0% then B will successfully go through this whole<00:07:19.479> Pipeline<00:07:19.919> and<00:07:20.440> be 00:07:21.550 --> 00:07:21.560 align:start position:0% whole Pipeline and be 00:07:21.560 --> 00:07:24.150 align:start position:0% whole Pipeline and be finalized<00:07:22.560> and<00:07:22.800> yeah<00:07:22.919> I<00:07:23.000> didn't<00:07:23.720> you<00:07:23.840> know<00:07:23.960> go 00:07:24.150 --> 00:07:24.160 align:start position:0% finalized and yeah I didn't you know go 00:07:24.160 --> 00:07:25.790 align:start position:0% finalized and yeah I didn't you know go into<00:07:24.440> more<00:07:24.639> details<00:07:25.000> of<00:07:25.160> why<00:07:25.319> this<00:07:25.479> is<00:07:25.639> the 00:07:25.790 --> 00:07:25.800 align:start position:0% into more details of why this is the 00:07:25.800 --> 00:07:28.869 align:start position:0% into more details of why this is the case<00:07:26.560> but<00:07:27.560> you<00:07:27.720> you<00:07:27.800> can<00:07:27.960> check<00:07:28.120> out<00:07:28.280> the<00:07:28.440> paper 00:07:28.869 --> 00:07:28.879 align:start position:0% case but you you can check out the paper 00:07:28.879 --> 00:07:31.350 align:start position:0% case but you you can check out the paper or<00:07:29.039> blog<00:07:29.240> post<00:07:29.520> for<00:07:29.720> that<00:07:30.319> and<00:07:30.680> uh<00:07:30.800> now<00:07:31.039> this<00:07:31.160> is 00:07:31.350 --> 00:07:31.360 align:start position:0% or blog post for that and uh now this is 00:07:31.360 --> 00:07:33.430 align:start position:0% or blog post for that and uh now this is the<00:07:31.879> um<00:07:32.039> there's<00:07:32.280> this<00:07:32.440> other<00:07:32.720> part<00:07:33.000> to<00:07:33.319> to 00:07:33.430 --> 00:07:33.440 align:start position:0% the um there's this other part to to 00:07:33.440 --> 00:07:35.950 align:start position:0% the um there's this other part to to this<00:07:33.560> whole<00:07:33.800> discussion<00:07:34.280> which<00:07:34.720> is<00:07:35.720> uh<00:07:35.840> the 00:07:35.950 --> 00:07:35.960 align:start position:0% this whole discussion which is uh the 00:07:35.960 --> 00:07:38.309 align:start position:0% this whole discussion which is uh the one<00:07:36.160> that's<00:07:36.319> a<00:07:36.440> bit<00:07:36.680> less<00:07:37.319> uh<00:07:37.599> understood<00:07:38.160> like 00:07:38.309 --> 00:07:38.319 align:start position:0% one that's a bit less uh understood like 00:07:38.319 --> 00:07:40.469 align:start position:0% one that's a bit less uh understood like more<00:07:38.680> kind<00:07:38.800> of<00:07:38.919> earlier<00:07:39.360> research<00:07:40.199> which<00:07:40.319> is 00:07:40.469 --> 00:07:40.479 align:start position:0% more kind of earlier research which is 00:07:40.479 --> 00:07:42.909 align:start position:0% more kind of earlier research which is validator<00:07:41.039> capping<00:07:41.879> uh<00:07:42.000> so<00:07:42.199> the<00:07:42.400> problem<00:07:42.680> of 00:07:42.909 --> 00:07:42.919 align:start position:0% validator capping uh so the problem of 00:07:42.919 --> 00:07:46.029 align:start position:0% validator capping uh so the problem of making<00:07:43.199> sure<00:07:43.479> that<00:07:43.879> uh<00:07:44.039> we<00:07:44.440> we<00:07:45.240> um<00:07:45.720> always 00:07:46.029 --> 00:07:46.039 align:start position:0% making sure that uh we we um always 00:07:46.039 --> 00:07:48.029 align:start position:0% making sure that uh we we um always maintain<00:07:46.680> a<00:07:46.919> kind<00:07:47.039> of<00:07:47.199> constant<00:07:47.560> load<00:07:47.840> that<00:07:47.960> we 00:07:48.029 --> 00:07:48.039 align:start position:0% maintain a kind of constant load that we 00:07:48.039 --> 00:07:50.230 align:start position:0% maintain a kind of constant load that we know<00:07:48.199> how<00:07:48.319> to<00:07:48.479> handle<00:07:49.120> and<00:07:49.360> we<00:07:49.520> don't<00:07:50.000> you<00:07:50.120> know 00:07:50.230 --> 00:07:50.240 align:start position:0% know how to handle and we don't you know 00:07:50.240 --> 00:07:52.070 align:start position:0% know how to handle and we don't you know do<00:07:50.400> this<00:07:50.520> roundt<00:07:50.800> tripping<00:07:51.159> of<00:07:51.560> reducing<00:07:51.960> the 00:07:52.070 --> 00:07:52.080 align:start position:0% do this roundt tripping of reducing the 00:07:52.080 --> 00:07:53.909 align:start position:0% do this roundt tripping of reducing the validator<00:07:52.560> set<00:07:52.800> through<00:07:52.960> consolidation<00:07:53.800> and 00:07:53.909 --> 00:07:53.919 align:start position:0% validator set through consolidation and 00:07:53.919 --> 00:07:55.230 align:start position:0% validator set through consolidation and then<00:07:54.080> going<00:07:54.360> back<00:07:54.520> up<00:07:54.639> to<00:07:54.800> like<00:07:54.919> a 00:07:55.230 --> 00:07:55.240 align:start position:0% then going back up to like a 00:07:55.240 --> 00:07:57.149 align:start position:0% then going back up to like a unsustainable<00:07:56.240> uh<00:07:56.360> validator<00:07:56.919> set 00:07:57.149 --> 00:07:57.159 align:start position:0% unsustainable uh validator set 00:07:57.159 --> 00:07:59.869 align:start position:0% unsustainable uh validator set essentially<00:07:58.039> and<00:07:58.240> in<00:07:58.720> specifically<00:07:59.520> I'll 00:07:59.869 --> 00:07:59.879 align:start position:0% essentially and in specifically I'll 00:07:59.879 --> 00:08:02.350 align:start position:0% essentially and in specifically I'll focus<00:08:00.159> on<00:08:00.479> a<00:08:00.800> quite<00:08:01.039> recent<00:08:01.599> idea<00:08:02.080> called 00:08:02.350 --> 00:08:02.360 align:start position:0% focus on a quite recent idea called 00:08:02.360 --> 00:08:05.430 align:start position:0% focus on a quite recent idea called orbit<00:08:03.280> that's<00:08:03.680> one<00:08:04.000> way<00:08:04.639> one<00:08:04.840> point<00:08:05.120> inter 00:08:05.430 --> 00:08:05.440 align:start position:0% orbit that's one way one point inter 00:08:05.440 --> 00:08:06.950 align:start position:0% orbit that's one way one point inter trate<00:08:05.639> of<00:08:05.800> space<00:08:06.039> of<00:08:06.199> how<00:08:06.319> to<00:08:06.440> handle<00:08:06.759> this 00:08:06.950 --> 00:08:06.960 align:start position:0% trate of space of how to handle this 00:08:06.960 --> 00:08:08.950 align:start position:0% trate of space of how to handle this problem<00:08:07.840> but<00:08:07.960> I'll<00:08:08.080> try<00:08:08.240> to<00:08:08.319> also<00:08:08.520> introduce 00:08:08.950 --> 00:08:08.960 align:start position:0% problem but I'll try to also introduce 00:08:08.960 --> 00:08:11.390 align:start position:0% problem but I'll try to also introduce the<00:08:09.120> the<00:08:09.280> problem<00:08:09.479> in<00:08:09.800> general<00:08:10.800> um<00:08:11.000> so<00:08:11.159> this<00:08:11.280> is 00:08:11.390 --> 00:08:11.400 align:start position:0% the the problem in general um so this is 00:08:11.400 --> 00:08:14.790 align:start position:0% the the problem in general um so this is from<00:08:11.599> balic<00:08:12.440> uh<00:08:13.199> lat<00:08:13.520> one<00:08:13.639> of<00:08:13.800> vitalic<00:08:14.319> many<00:08:14.720> uh 00:08:14.790 --> 00:08:14.800 align:start position:0% from balic uh lat one of vitalic many uh 00:08:14.800 --> 00:08:16.469 align:start position:0% from balic uh lat one of vitalic many uh latest<00:08:15.120> posts<00:08:15.479> on<00:08:15.680> the<00:08:15.879> future<00:08:16.280> of<00:08:16.360> the 00:08:16.469 --> 00:08:16.479 align:start position:0% latest posts on the future of the 00:08:16.479 --> 00:08:18.189 align:start position:0% latest posts on the future of the protocol<00:08:16.919> in<00:08:17.080> particular<00:08:17.599> the<00:08:17.720> the<00:08:17.840> one<00:08:17.960> from 00:08:18.189 --> 00:08:18.199 align:start position:0% protocol in particular the the one from 00:08:18.199 --> 00:08:21.149 align:start position:0% protocol in particular the the one from the<00:08:18.599> uh<00:08:18.800> about<00:08:19.000> the<00:08:19.120> merge<00:08:20.000> so<00:08:20.680> um<00:08:20.840> you<00:08:20.960> can 00:08:21.149 --> 00:08:21.159 align:start position:0% the uh about the merge so um you can 00:08:21.159 --> 00:08:23.149 align:start position:0% the uh about the merge so um you can kind<00:08:21.280> of<00:08:21.400> see<00:08:21.680> essentially<00:08:22.080> this<00:08:22.280> spectrum<00:08:22.800> of 00:08:23.149 --> 00:08:23.159 align:start position:0% kind of see essentially this spectrum of 00:08:23.159 --> 00:08:25.909 align:start position:0% kind of see essentially this spectrum of possible<00:08:23.680> ways<00:08:23.919> to<00:08:24.120> to<00:08:24.280> handle<00:08:24.879> this<00:08:25.080> problem 00:08:25.909 --> 00:08:25.919 align:start position:0% possible ways to to handle this problem 00:08:25.919 --> 00:08:27.550 align:start position:0% possible ways to to handle this problem uh<00:08:26.039> on<00:08:26.199> the<00:08:26.560> right<00:08:26.840> all<00:08:27.000> the<00:08:27.080> way<00:08:27.199> on<00:08:27.280> the<00:08:27.400> right 00:08:27.550 --> 00:08:27.560 align:start position:0% uh on the right all the way on the right 00:08:27.560 --> 00:08:29.830 align:start position:0% uh on the right all the way on the right you<00:08:27.639> have<00:08:27.800> this<00:08:28.080> tender<00:08:28.680> style<00:08:29.120> kind<00:08:29.240> of<00:08:29.639> a 00:08:29.830 --> 00:08:29.840 align:start position:0% you have this tender style kind of a 00:08:29.840 --> 00:08:31.950 align:start position:0% you have this tender style kind of a small<00:08:30.120> validator<00:08:30.639> Set<00:08:31.360> uh<00:08:31.440> you<00:08:31.520> know<00:08:31.639> maybe<00:08:31.879> a 00:08:31.950 --> 00:08:31.960 align:start position:0% small validator Set uh you know maybe a 00:08:31.960 --> 00:08:33.350 align:start position:0% small validator Set uh you know maybe a few<00:08:32.120> hundreds<00:08:32.519> or<00:08:32.680> in<00:08:32.800> the<00:08:32.919> context<00:08:33.240> of 00:08:33.350 --> 00:08:33.360 align:start position:0% few hundreds or in the context of 00:08:33.360 --> 00:08:35.149 align:start position:0% few hundreds or in the context of ethereum<00:08:33.760> this<00:08:33.880> could<00:08:34.000> be<00:08:34.120> a<00:08:34.200> few<00:08:34.399> thousands 00:08:35.149 --> 00:08:35.159 align:start position:0% ethereum this could be a few thousands 00:08:35.159 --> 00:08:36.550 align:start position:0% ethereum this could be a few thousands and<00:08:35.320> these<00:08:35.440> are<00:08:35.640> really<00:08:35.919> you<00:08:36.000> know<00:08:36.279> large 00:08:36.550 --> 00:08:36.560 align:start position:0% and these are really you know large 00:08:36.560 --> 00:08:38.589 align:start position:0% and these are really you know large validators<00:08:37.120> with<00:08:37.240> a<00:08:37.320> lot<00:08:37.479> of<00:08:37.599> stake<00:08:38.120> so<00:08:38.440> there 00:08:38.589 --> 00:08:38.599 align:start position:0% validators with a lot of stake so there 00:08:38.599 --> 00:08:40.350 align:start position:0% validators with a lot of stake so there it's<00:08:38.800> quite<00:08:39.000> simple<00:08:39.279> to<00:08:39.399> do<00:08:40.039> you<00:08:40.120> know<00:08:40.279> for 00:08:40.350 --> 00:08:40.360 align:start position:0% it's quite simple to do you know for 00:08:40.360 --> 00:08:41.670 align:start position:0% it's quite simple to do you know for example<00:08:40.599> in<00:08:40.680> ethereum<00:08:41.080> we<00:08:41.159> could<00:08:41.279> say<00:08:41.479> that 00:08:41.670 --> 00:08:41.680 align:start position:0% example in ethereum we could say that 00:08:41.680 --> 00:08:43.790 align:start position:0% example in ethereum we could say that there's<00:08:42.080> 30,000<00:08:42.640> validators<00:08:43.320> as<00:08:43.440> we<00:08:43.599> already 00:08:43.790 --> 00:08:43.800 align:start position:0% there's 30,000 validators as we already 00:08:43.800 --> 00:08:45.590 align:start position:0% there's 30,000 validators as we already said<00:08:44.039> this<00:08:44.159> is<00:08:44.240> a<00:08:44.360> number<00:08:44.720> that<00:08:45.120> we<00:08:45.240> know<00:08:45.480> we 00:08:45.590 --> 00:08:45.600 align:start position:0% said this is a number that we know we 00:08:45.600 --> 00:08:48.630 align:start position:0% said this is a number that we know we can<00:08:45.760> handle<00:08:46.760> uh<00:08:46.880> and<00:08:47.000> so<00:08:47.519> we<00:08:47.680> could<00:08:48.040> just<00:08:48.240> say 00:08:48.630 --> 00:08:48.640 align:start position:0% can handle uh and so we could just say 00:08:48.640 --> 00:08:50.230 align:start position:0% can handle uh and so we could just say okay<00:08:48.760> we<00:08:48.880> only<00:08:49.080> have<00:08:49.200> space<00:08:49.440> for<00:08:49.640> 30,000 00:08:50.230 --> 00:08:50.240 align:start position:0% okay we only have space for 30,000 00:08:50.240 --> 00:08:52.110 align:start position:0% okay we only have space for 30,000 validators<00:08:51.240> that's<00:08:51.480> that's<00:08:51.640> the<00:08:51.760> most<00:08:51.959> that 00:08:52.110 --> 00:08:52.120 align:start position:0% validators that's that's the most that 00:08:52.120 --> 00:08:53.670 align:start position:0% validators that's that's the most that we<00:08:52.200> can<00:08:52.320> do<00:08:52.480> if<00:08:52.600> we<00:08:52.720> want<00:08:52.839> to<00:08:53.040> have<00:08:53.200> faster 00:08:53.670 --> 00:08:53.680 align:start position:0% we can do if we want to have faster 00:08:53.680 --> 00:08:56.230 align:start position:0% we can do if we want to have faster finality<00:08:54.680> uh<00:08:54.920> but<00:08:55.080> this<00:08:55.200> means<00:08:55.560> that<00:08:56.000> each 00:08:56.230 --> 00:08:56.240 align:start position:0% finality uh but this means that each 00:08:56.240 --> 00:08:57.949 align:start position:0% finality uh but this means that each validator<00:08:56.839> would<00:08:57.000> have<00:08:57.120> to<00:08:57.279> have<00:08:57.440> like<00:08:57.560> a<00:08:57.720> very 00:08:57.949 --> 00:08:57.959 align:start position:0% validator would have to have like a very 00:08:57.959 --> 00:08:59.910 align:start position:0% validator would have to have like a very high<00:08:58.120> balance<00:08:58.800> not<00:08:58.959> incredibly<00:08:59.560> high<00:08:59.720> but<00:08:59.839> you 00:08:59.910 --> 00:08:59.920 align:start position:0% high balance not incredibly high but you 00:08:59.920 --> 00:09:03.590 align:start position:0% high balance not incredibly high but you know<00:09:00.160> a<00:09:00.279> couple<00:09:00.560> thousand<00:09:01.160> e<00:09:01.480> or<00:09:01.959> one<00:09:02.240> 1,000<00:09:02.720> e 00:09:03.590 --> 00:09:03.600 align:start position:0% know a couple thousand e or one 1,000 e 00:09:03.600 --> 00:09:05.230 align:start position:0% know a couple thousand e or one 1,000 e um<00:09:03.760> which<00:09:03.839> is<00:09:04.040> much<00:09:04.240> much<00:09:04.440> higher<00:09:04.760> than<00:09:04.959> the 00:09:05.230 --> 00:09:05.240 align:start position:0% um which is much much higher than the 00:09:05.240 --> 00:09:07.190 align:start position:0% um which is much much higher than the barrier<00:09:05.560> to<00:09:05.720> entry<00:09:06.000> that<00:09:06.120> we<00:09:06.200> have<00:09:06.360> today<00:09:06.760> of 00:09:07.190 --> 00:09:07.200 align:start position:0% barrier to entry that we have today of 00:09:07.200 --> 00:09:10.350 align:start position:0% barrier to entry that we have today of 30<00:09:07.480> to<00:09:07.680> e<00:09:08.600> um<00:09:08.760> so<00:09:09.040> that's<00:09:09.240> kind<00:09:09.360> of<00:09:09.519> one<00:09:09.720> extreme 00:09:10.350 --> 00:09:10.360 align:start position:0% 30 to e um so that's kind of one extreme 00:09:10.360 --> 00:09:12.670 align:start position:0% 30 to e um so that's kind of one extreme that<00:09:10.519> would<00:09:11.040> significantly<00:09:11.560> change<00:09:12.200> um<00:09:12.519> the 00:09:12.670 --> 00:09:12.680 align:start position:0% that would significantly change um the 00:09:12.680 --> 00:09:14.949 align:start position:0% that would significantly change um the the<00:09:12.800> barrier<00:09:13.120> to<00:09:13.279> be<00:09:13.399> a<00:09:13.560> Staker<00:09:14.560> uh<00:09:14.720> then<00:09:14.839> the 00:09:14.949 --> 00:09:14.959 align:start position:0% the barrier to be a Staker uh then the 00:09:14.959 --> 00:09:16.470 align:start position:0% the barrier to be a Staker uh then the other<00:09:15.120> extreme<00:09:15.519> is<00:09:15.640> that<00:09:15.839> all<00:09:15.959> the<00:09:16.040> way<00:09:16.200> on<00:09:16.320> the 00:09:16.470 --> 00:09:16.480 align:start position:0% other extreme is that all the way on the 00:09:16.480 --> 00:09:19.750 align:start position:0% other extreme is that all the way on the left<00:09:17.440> um<00:09:17.920> which<00:09:18.320> is<00:09:18.519> essentially 00:09:19.750 --> 00:09:19.760 align:start position:0% left um which is essentially 00:09:19.760 --> 00:09:22.190 align:start position:0% left um which is essentially we<00:09:20.760> just<00:09:20.959> do<00:09:21.240> random<00:09:21.560> sampling<00:09:21.959> of<00:09:22.079> a 00:09:22.190 --> 00:09:22.200 align:start position:0% we just do random sampling of a 00:09:22.200 --> 00:09:23.829 align:start position:0% we just do random sampling of a committee<00:09:22.600> so<00:09:22.760> we<00:09:22.880> say<00:09:23.320> there<00:09:23.480> are<00:09:23.680> no 00:09:23.829 --> 00:09:23.839 align:start position:0% committee so we say there are no 00:09:23.839 --> 00:09:25.550 align:start position:0% committee so we say there are no barriers<00:09:24.160> to<00:09:24.320> entry<00:09:24.720> we<00:09:24.800> could<00:09:24.959> even<00:09:25.160> say<00:09:25.480> you 00:09:25.550 --> 00:09:25.560 align:start position:0% barriers to entry we could even say you 00:09:25.560 --> 00:09:28.710 align:start position:0% barriers to entry we could even say you can<00:09:25.760> be<00:09:25.920> a<00:09:26.800> um<00:09:27.000> Staker<00:09:27.440> with<00:09:27.600> one<00:09:27.800> e<00:09:28.399> or<00:09:28.600> you 00:09:28.710 --> 00:09:28.720 align:start position:0% can be a um Staker with one e or you 00:09:28.720 --> 00:09:30.790 align:start position:0% can be a um Staker with one e or you know<00:09:28.920> maybe<00:09:29.120> we<00:09:29.240> don't<00:09:29.480> even<00:09:29.600> have<00:09:29.720> a<00:09:29.839> minimum 00:09:30.790 --> 00:09:30.800 align:start position:0% know maybe we don't even have a minimum 00:09:30.800 --> 00:09:32.910 align:start position:0% know maybe we don't even have a minimum uh<00:09:30.959> but<00:09:31.279> then<00:09:31.440> we<00:09:31.600> sample<00:09:32.200> we<00:09:32.279> do<00:09:32.480> like<00:09:32.640> random 00:09:32.910 --> 00:09:32.920 align:start position:0% uh but then we sample we do like random 00:09:32.920 --> 00:09:35.509 align:start position:0% uh but then we sample we do like random sampling<00:09:33.360> essentially<00:09:33.760> of<00:09:33.920> a<00:09:34.040> committee<00:09:34.959> and 00:09:35.509 --> 00:09:35.519 align:start position:0% sampling essentially of a committee and 00:09:35.519 --> 00:09:37.870 align:start position:0% sampling essentially of a committee and the<00:09:35.640> issue<00:09:35.880> with<00:09:36.040> this<00:09:36.200> is<00:09:36.399> that<00:09:37.120> um<00:09:37.640> this 00:09:37.870 --> 00:09:37.880 align:start position:0% the issue with this is that um this 00:09:37.880 --> 00:09:39.829 align:start position:0% the issue with this is that um this committee<00:09:38.240> size<00:09:38.440> is<00:09:38.600> fixed<00:09:39.079> so<00:09:39.279> if<00:09:39.399> the<00:09:39.560> total 00:09:39.829 --> 00:09:39.839 align:start position:0% committee size is fixed so if the total 00:09:39.839 --> 00:09:41.870 align:start position:0% committee size is fixed so if the total validator<00:09:40.279> set<00:09:40.519> is<00:09:40.760> much<00:09:41.000> much<00:09:41.240> bigger<00:09:41.720> than 00:09:41.870 --> 00:09:41.880 align:start position:0% validator set is much much bigger than 00:09:41.880 --> 00:09:44.350 align:start position:0% validator set is much much bigger than the<00:09:42.000> committee<00:09:42.440> size<00:09:43.399> then<00:09:43.760> the<00:09:44.120> uh<00:09:44.240> the 00:09:44.350 --> 00:09:44.360 align:start position:0% the committee size then the uh the 00:09:44.360 --> 00:09:46.389 align:start position:0% the committee size then the uh the committee<00:09:44.680> will<00:09:44.839> in<00:09:45.360> inevitably<00:09:45.920> have<00:09:46.079> like<00:09:46.200> a 00:09:46.389 --> 00:09:46.399 align:start position:0% committee will in inevitably have like a 00:09:46.399 --> 00:09:48.590 align:start position:0% committee will in inevitably have like a very<00:09:46.839> uh<00:09:47.040> small<00:09:47.320> amount<00:09:47.519> of<00:09:47.680> stake<00:09:48.279> like<00:09:48.399> if 00:09:48.590 --> 00:09:48.600 align:start position:0% very uh small amount of stake like if 00:09:48.600 --> 00:09:50.750 align:start position:0% very uh small amount of stake like if only<00:09:49.320> uh<00:09:49.440> you<00:09:49.519> know<00:09:49.640> today<00:09:49.920> we<00:09:50.040> have<00:09:50.279> 1<00:09:50.480> million 00:09:50.750 --> 00:09:50.760 align:start position:0% only uh you know today we have 1 million 00:09:50.760 --> 00:09:53.190 align:start position:0% only uh you know today we have 1 million validators<00:09:51.600> only<00:09:51.839> 30,000<00:09:52.480> can<00:09:52.680> participate 00:09:53.190 --> 00:09:53.200 align:start position:0% validators only 30,000 can participate 00:09:53.200 --> 00:09:56.870 align:start position:0% validators only 30,000 can participate in<00:09:53.360> each<00:09:53.560> slot<00:09:54.399> uh<00:09:54.600> then<00:09:55.040> about<00:09:55.399> 13th<00:09:56.279> of<00:09:56.480> the 00:09:56.870 --> 00:09:56.880 align:start position:0% in each slot uh then about 13th of the 00:09:56.880 --> 00:09:59.990 align:start position:0% in each slot uh then about 13th of the only<00:09:57.079> 13th<00:09:57.680> of<00:09:57.800> the<00:09:57.880> stake<00:09:58.279> will<00:09:59.200> uh<00:09:59.480> um<00:09:59.680> exist 00:09:59.990 --> 00:10:00.000 align:start position:0% only 13th of the stake will uh um exist 00:10:00.000 --> 00:10:02.030 align:start position:0% only 13th of the stake will uh um exist within<00:10:00.240> each<00:10:00.399> committee<00:10:01.040> so<00:10:01.440> essentially 00:10:02.030 --> 00:10:02.040 align:start position:0% within each committee so essentially 00:10:02.040 --> 00:10:04.310 align:start position:0% within each committee so essentially very<00:10:02.279> low<00:10:02.800> economic<00:10:03.240> finality<00:10:03.959> so<00:10:04.160> that's 00:10:04.310 --> 00:10:04.320 align:start position:0% very low economic finality so that's 00:10:04.320 --> 00:10:05.470 align:start position:0% very low economic finality so that's like<00:10:04.440> kind<00:10:04.560> of<00:10:04.680> all<00:10:04.839> the<00:10:04.920> way<00:10:05.079> on<00:10:05.200> the<00:10:05.320> other 00:10:05.470 --> 00:10:05.480 align:start position:0% like kind of all the way on the other 00:10:05.480 --> 00:10:07.030 align:start position:0% like kind of all the way on the other end<00:10:05.680> of<00:10:05.800> the<00:10:05.920> of<00:10:06.000> the<00:10:06.120> trade-off<00:10:06.480> space 00:10:07.030 --> 00:10:07.040 align:start position:0% end of the of the trade-off space 00:10:07.040 --> 00:10:08.350 align:start position:0% end of the of the trade-off space somewhere<00:10:07.399> in<00:10:07.480> the<00:10:07.560> middle<00:10:07.800> of<00:10:07.880> the<00:10:07.959> tradeoff 00:10:08.350 --> 00:10:08.360 align:start position:0% somewhere in the middle of the tradeoff 00:10:08.360 --> 00:10:11.470 align:start position:0% somewhere in the middle of the tradeoff space<00:10:08.959> is<00:10:09.560> a<00:10:09.720> solution<00:10:10.200> where<00:10:10.640> we<00:10:10.839> do<00:10:11.000> sampling 00:10:11.470 --> 00:10:11.480 align:start position:0% space is a solution where we do sampling 00:10:11.480 --> 00:10:13.590 align:start position:0% space is a solution where we do sampling in<00:10:11.640> a<00:10:11.839> a<00:10:12.040> somewhat<00:10:12.440> different<00:10:12.800> way<00:10:13.360> that's 00:10:13.590 --> 00:10:13.600 align:start position:0% in a a somewhat different way that's 00:10:13.600 --> 00:10:15.710 align:start position:0% in a a somewhat different way that's still<00:10:13.839> trying<00:10:14.120> to<00:10:14.279> ensure<00:10:14.680> that<00:10:14.880> we<00:10:15.079> have<00:10:15.440> a 00:10:15.710 --> 00:10:15.720 align:start position:0% still trying to ensure that we have a 00:10:15.720 --> 00:10:18.030 align:start position:0% still trying to ensure that we have a fixed<00:10:16.079> size<00:10:16.360> committee<00:10:17.240> but<00:10:17.399> it<00:10:17.519> is<00:10:17.640> trying<00:10:17.880> to 00:10:18.030 --> 00:10:18.040 align:start position:0% fixed size committee but it is trying to 00:10:18.040 --> 00:10:21.190 align:start position:0% fixed size committee but it is trying to take<00:10:18.240> advantage<00:10:18.800> of<00:10:19.160> existing<00:10:20.200> heterogeneity 00:10:21.190 --> 00:10:21.200 align:start position:0% take advantage of existing heterogeneity 00:10:21.200 --> 00:10:22.710 align:start position:0% take advantage of existing heterogeneity in<00:10:21.440> the<00:10:21.720> the<00:10:21.880> way<00:10:22.079> that<00:10:22.279> the<00:10:22.399> stake 00:10:22.710 --> 00:10:22.720 align:start position:0% in the the way that the stake 00:10:22.720 --> 00:10:24.750 align:start position:0% in the the way that the stake distribution<00:10:23.240> is<00:10:23.640> so<00:10:23.800> you<00:10:23.880> know<00:10:24.040> today<00:10:24.399> we<00:10:24.600> we 00:10:24.750 --> 00:10:24.760 align:start position:0% distribution is so you know today we we 00:10:24.760 --> 00:10:27.430 align:start position:0% distribution is so you know today we we have<00:10:25.000> sure<00:10:25.320> 1<00:10:25.519> million<00:10:25.839> validators<00:10:26.839> but<00:10:27.120> many 00:10:27.430 --> 00:10:27.440 align:start position:0% have sure 1 million validators but many 00:10:27.440 --> 00:10:30.230 align:start position:0% have sure 1 million validators but many validators<00:10:28.000> are<00:10:28.240> actually<00:10:29.040> um<00:10:29.440> clustered<00:10:30.120> in 00:10:30.230 --> 00:10:30.240 align:start position:0% validators are actually um clustered in 00:10:30.240 --> 00:10:31.590 align:start position:0% validators are actually um clustered in in<00:10:30.399> staking<00:10:30.800> pools<00:10:31.160> even<00:10:31.360> though<00:10:31.480> the 00:10:31.590 --> 00:10:31.600 align:start position:0% in staking pools even though the 00:10:31.600 --> 00:10:33.150 align:start position:0% in staking pools even though the protocol<00:10:32.000> does<00:10:32.160> not<00:10:32.480> actually<00:10:32.680> know<00:10:32.920> about 00:10:33.150 --> 00:10:33.160 align:start position:0% protocol does not actually know about 00:10:33.160 --> 00:10:35.550 align:start position:0% protocol does not actually know about that<00:10:33.839> and<00:10:33.920> so<00:10:34.120> there<00:10:34.240> is<00:10:34.480> this<00:10:34.959> uh<00:10:35.079> you<00:10:35.200> know 00:10:35.550 --> 00:10:35.560 align:start position:0% that and so there is this uh you know 00:10:35.560 --> 00:10:37.269 align:start position:0% that and so there is this uh you know natural<00:10:36.000> concentration<00:10:36.480> of<00:10:36.600> steak<00:10:36.959> that 00:10:37.269 --> 00:10:37.279 align:start position:0% natural concentration of steak that 00:10:37.279 --> 00:10:39.310 align:start position:0% natural concentration of steak that already<00:10:37.560> does<00:10:37.839> exist<00:10:38.519> and<00:10:38.680> it<00:10:38.800> is<00:10:39.079> you<00:10:39.160> know<00:10:39.240> a 00:10:39.310 --> 00:10:39.320 align:start position:0% already does exist and it is you know a 00:10:39.320 --> 00:10:41.629 align:start position:0% already does exist and it is you know a natural<00:10:39.639> thing<00:10:39.839> to<00:10:40.040> to<00:10:40.200> occur<00:10:41.079> um<00:10:41.240> and<00:10:41.399> we<00:10:41.519> can 00:10:41.629 --> 00:10:41.639 align:start position:0% natural thing to to occur um and we can 00:10:41.639 --> 00:10:43.670 align:start position:0% natural thing to to occur um and we can try<00:10:41.880> to<00:10:42.040> actually<00:10:42.279> take<00:10:42.440> advantage<00:10:42.839> of<00:10:43.040> that 00:10:43.670 --> 00:10:43.680 align:start position:0% try to actually take advantage of that 00:10:43.680 --> 00:10:45.470 align:start position:0% try to actually take advantage of that um<00:10:43.839> to<00:10:44.120> to<00:10:44.279> find<00:10:44.480> the<00:10:44.639> point<00:10:44.880> that's<00:10:45.079> somewhere 00:10:45.470 --> 00:10:45.480 align:start position:0% um to to find the point that's somewhere 00:10:45.480 --> 00:10:48.190 align:start position:0% um to to find the point that's somewhere in<00:10:45.600> between<00:10:45.920> these<00:10:46.079> two<00:10:46.720> extremes<00:10:47.720> and<00:10:48.079> just 00:10:48.190 --> 00:10:48.200 align:start position:0% in between these two extremes and just 00:10:48.200 --> 00:10:50.389 align:start position:0% in between these two extremes and just to<00:10:48.360> call<00:10:48.560> it<00:10:48.680> out<00:10:49.040> this<00:10:49.639> though<00:10:49.839> there<00:10:50.000> it<00:10:50.120> says 00:10:50.389 --> 00:10:50.399 align:start position:0% to call it out this though there it says 00:10:50.399 --> 00:10:52.870 align:start position:0% to call it out this though there it says tender<00:10:50.920> style<00:10:51.320> in<00:10:51.480> the<00:10:51.680> context<00:10:52.000> of<00:10:52.160> ethereum 00:10:52.870 --> 00:10:52.880 align:start position:0% tender style in the context of ethereum 00:10:52.880 --> 00:10:54.590 align:start position:0% tender style in the context of ethereum most<00:10:53.279> more<00:10:53.480> likely<00:10:53.920> what<00:10:54.079> this<00:10:54.200> would<00:10:54.399> look 00:10:54.590 --> 00:10:54.600 align:start position:0% most more likely what this would look 00:10:54.600 --> 00:10:57.269 align:start position:0% most more likely what this would look like<00:10:54.839> it's<00:10:55.120> what<00:10:55.600> has<00:10:55.800> been<00:10:56.600> uh<00:10:56.760> called 00:10:57.269 --> 00:10:57.279 align:start position:0% like it's what has been uh called 00:10:57.279 --> 00:10:59.629 align:start position:0% like it's what has been uh called sometimes<00:10:57.519> rainbow<00:10:57.920> staking<00:10:58.360> so<00:10:58.519> where<00:10:58.720> Maybe 00:10:59.629 --> 00:10:59.639 align:start position:0% sometimes rainbow staking so where Maybe 00:10:59.639 --> 00:11:01.829 align:start position:0% sometimes rainbow staking so where Maybe we<00:10:59.800> essentially<00:11:00.200> split<00:11:00.519> up<00:11:00.680> staking<00:11:01.160> into<00:11:01.560> two 00:11:01.829 --> 00:11:01.839 align:start position:0% we essentially split up staking into two 00:11:01.839 --> 00:11:04.069 align:start position:0% we essentially split up staking into two different<00:11:02.120> classes<00:11:02.399> of<00:11:02.639> validators<00:11:03.639> uh<00:11:03.800> one 00:11:04.069 --> 00:11:04.079 align:start position:0% different classes of validators uh one 00:11:04.079 --> 00:11:06.110 align:start position:0% different classes of validators uh one which<00:11:04.320> do<00:11:04.920> uh<00:11:05.079> are<00:11:05.360> responsible<00:11:05.880> for 00:11:06.110 --> 00:11:06.120 align:start position:0% which do uh are responsible for 00:11:06.120 --> 00:11:08.509 align:start position:0% which do uh are responsible for essentially<00:11:06.519> finality<00:11:07.079> or<00:11:07.360> or<00:11:07.519> a<00:11:07.720> testing<00:11:08.399> and 00:11:08.509 --> 00:11:08.519 align:start position:0% essentially finality or or a testing and 00:11:08.519 --> 00:11:10.550 align:start position:0% essentially finality or or a testing and are<00:11:08.720> more<00:11:09.000> restricted<00:11:09.560> or<00:11:09.800> like<00:11:10.200> have<00:11:10.360> this 00:11:10.550 --> 00:11:10.560 align:start position:0% are more restricted or like have this 00:11:10.560 --> 00:11:12.590 align:start position:0% are more restricted or like have this higher<00:11:10.839> barrier<00:11:11.160> to<00:11:11.320> entry<00:11:11.920> of<00:11:12.120> having<00:11:12.360> a 00:11:12.590 --> 00:11:12.600 align:start position:0% higher barrier to entry of having a 00:11:12.600 --> 00:11:16.550 align:start position:0% higher barrier to entry of having a higher<00:11:13.279> um<00:11:13.720> amount<00:11:13.959> of<00:11:14.120> e<00:11:14.680> so<00:11:14.880> that<00:11:15.040> we<00:11:15.160> can 00:11:16.550 --> 00:11:16.560 align:start position:0% higher um amount of e so that we can 00:11:16.560 --> 00:11:19.150 align:start position:0% higher um amount of e so that we can um<00:11:17.560> essentially<00:11:17.959> limit<00:11:18.360> the<00:11:18.519> the<00:11:18.639> number<00:11:19.000> of 00:11:19.150 --> 00:11:19.160 align:start position:0% um essentially limit the the number of 00:11:19.160 --> 00:11:21.190 align:start position:0% um essentially limit the the number of these<00:11:19.360> entities<00:11:20.240> whereas<00:11:20.720> there<00:11:20.880> could<00:11:21.040> be 00:11:21.190 --> 00:11:21.200 align:start position:0% these entities whereas there could be 00:11:21.200 --> 00:11:23.150 align:start position:0% these entities whereas there could be like<00:11:21.320> a<00:11:21.440> lighter<00:11:21.800> class<00:11:22.040> of<00:11:22.160> stakers<00:11:22.880> that<00:11:23.000> are 00:11:23.150 --> 00:11:23.160 align:start position:0% like a lighter class of stakers that are 00:11:23.160 --> 00:11:25.829 align:start position:0% like a lighter class of stakers that are still<00:11:23.480> responsible<00:11:24.000> for<00:11:24.440> things<00:11:24.720> like<00:11:25.560> um 00:11:25.829 --> 00:11:25.839 align:start position:0% still responsible for things like um 00:11:25.839 --> 00:11:27.910 align:start position:0% still responsible for things like um making<00:11:26.279> inclusion<00:11:26.720> list<00:11:27.120> or<00:11:27.320> or<00:11:27.440> even<00:11:27.639> block 00:11:27.910 --> 00:11:27.920 align:start position:0% making inclusion list or or even block 00:11:27.920 --> 00:11:29.949 align:start position:0% making inclusion list or or even block proposing<00:11:28.480> or<00:11:28.720> essentially<00:11:29.040> other<00:11:29.480> parts<00:11:29.720> of 00:11:29.949 --> 00:11:29.959 align:start position:0% proposing or essentially other parts of 00:11:29.959 --> 00:11:32.910 align:start position:0% proposing or essentially other parts of the<00:11:30.639> uh<00:11:30.720> of<00:11:30.839> the<00:11:30.959> stick<00:11:31.240> in<00:11:31.680> uh<00:11:31.839> pipeline<00:11:32.720> that 00:11:32.910 --> 00:11:32.920 align:start position:0% the uh of the stick in uh pipeline that 00:11:32.920 --> 00:11:34.389 align:start position:0% the uh of the stick in uh pipeline that don't<00:11:33.240> really<00:11:33.480> have<00:11:33.680> this<00:11:33.839> like<00:11:34.040> technical 00:11:34.389 --> 00:11:34.399 align:start position:0% don't really have this like technical 00:11:34.399 --> 00:11:37.430 align:start position:0% don't really have this like technical limitation<00:11:35.079> that<00:11:35.240> a<00:11:35.399> testing<00:11:36.120> does<00:11:37.120> but<00:11:37.320> yeah 00:11:37.430 --> 00:11:37.440 align:start position:0% limitation that a testing does but yeah 00:11:37.440 --> 00:11:39.910 align:start position:0% limitation that a testing does but yeah so<00:11:37.600> that's<00:11:37.920> that's<00:11:38.120> one<00:11:38.399> possible<00:11:39.200> um<00:11:39.600> way<00:11:39.760> to 00:11:39.910 --> 00:11:39.920 align:start position:0% so that's that's one possible um way to 00:11:39.920 --> 00:11:41.509 align:start position:0% so that's that's one possible um way to go<00:11:40.120> about<00:11:40.320> it<00:11:40.519> but<00:11:40.720> I'll<00:11:40.920> discuss<00:11:41.279> this<00:11:41.399> kind 00:11:41.509 --> 00:11:41.519 align:start position:0% go about it but I'll discuss this kind 00:11:41.519 --> 00:11:44.949 align:start position:0% go about it but I'll discuss this kind of<00:11:41.639> middle<00:11:42.519> uh<00:11:42.680> one<00:11:43.399> that<00:11:43.639> that<00:11:43.839> we<00:11:44.000> call 00:11:44.949 --> 00:11:44.959 align:start position:0% of middle uh one that that we call 00:11:44.959 --> 00:11:48.710 align:start position:0% of middle uh one that that we call orbit<00:11:45.959> so<00:11:46.600> um<00:11:47.160> what<00:11:47.320> is<00:11:47.480> orbit<00:11:48.279> um<00:11:48.440> there's 00:11:48.710 --> 00:11:48.720 align:start position:0% orbit so um what is orbit um there's 00:11:48.720 --> 00:11:51.069 align:start position:0% orbit so um what is orbit um there's this<00:11:49.519> um<00:11:49.760> orbit<00:11:50.079> essentially<00:11:50.480> is<00:11:50.560> a<00:11:50.760> technique 00:11:51.069 --> 00:11:51.079 align:start position:0% this um orbit essentially is a technique 00:11:51.079 --> 00:11:52.990 align:start position:0% this um orbit essentially is a technique for<00:11:51.279> sampling<00:11:51.720> a<00:11:51.839> committee<00:11:52.320> in<00:11:52.440> a<00:11:52.600> particular 00:11:52.990 --> 00:11:53.000 align:start position:0% for sampling a committee in a particular 00:11:53.000 --> 00:11:54.350 align:start position:0% for sampling a committee in a particular way<00:11:53.279> that<00:11:53.360> tries<00:11:53.600> to<00:11:53.720> achieve<00:11:54.040> these<00:11:54.160> two 00:11:54.350 --> 00:11:54.360 align:start position:0% way that tries to achieve these two 00:11:54.360 --> 00:11:56.310 align:start position:0% way that tries to achieve these two things<00:11:54.680> of<00:11:54.839> having<00:11:55.279> the<00:11:55.440> committee<00:11:55.839> being<00:11:56.160> of 00:11:56.310 --> 00:11:56.320 align:start position:0% things of having the committee being of 00:11:56.320 --> 00:11:58.509 align:start position:0% things of having the committee being of a<00:11:56.760> fixed<00:11:57.279> uh<00:11:57.399> predetermined<00:11:58.040> size<00:11:58.279> that<00:11:58.399> we 00:11:58.509 --> 00:11:58.519 align:start position:0% a fixed uh predetermined size that we 00:11:58.519 --> 00:12:01.069 align:start position:0% a fixed uh predetermined size that we can<00:11:58.680> handle<00:11:59.279> and<00:11:59.440> of<00:11:59.600> having<00:11:59.800> a<00:11:59.880> lot<00:12:00.040> of<00:12:00.120> stake 00:12:01.069 --> 00:12:01.079 align:start position:0% can handle and of having a lot of stake 00:12:01.079 --> 00:12:03.870 align:start position:0% can handle and of having a lot of stake um<00:12:01.240> so<00:12:01.440> let's<00:12:02.200> uh<00:12:02.360> call<00:12:02.680> T<00:12:03.200> the<00:12:03.399> maximum 00:12:03.870 --> 00:12:03.880 align:start position:0% um so let's uh call T the maximum 00:12:03.880 --> 00:12:06.550 align:start position:0% um so let's uh call T the maximum effective<00:12:04.240> balance<00:12:04.680> which<00:12:04.839> is<00:12:05.000> becoming<00:12:05.680> 2048 00:12:06.550 --> 00:12:06.560 align:start position:0% effective balance which is becoming 2048 00:12:06.560 --> 00:12:09.350 align:start position:0% effective balance which is becoming 2048 eth<00:12:06.959> as<00:12:07.120> of<00:12:07.279> the<00:12:07.360> next<00:12:07.560> Fork<00:12:08.560> um<00:12:09.000> once<00:12:09.200> we 00:12:09.350 --> 00:12:09.360 align:start position:0% eth as of the next Fork um once we 00:12:09.360 --> 00:12:12.790 align:start position:0% eth as of the next Fork um once we select<00:12:09.720> this<00:12:09.880> committee<00:12:10.560> we'll<00:12:10.920> take<00:12:11.399> a<00:12:11.920> um<00:12:12.399> so 00:12:12.790 --> 00:12:12.800 align:start position:0% select this committee we'll take a um so 00:12:12.800 --> 00:12:16.030 align:start position:0% select this committee we'll take a um so let's<00:12:12.920> look<00:12:13.079> at<00:12:13.480> how<00:12:14.480> how<00:12:14.639> does<00:12:14.839> a<00:12:15.399> Staker<00:12:15.880> with 00:12:16.030 --> 00:12:16.040 align:start position:0% let's look at how how does a Staker with 00:12:16.040 --> 00:12:18.310 align:start position:0% let's look at how how does a Staker with s<00:12:16.360> stake<00:12:16.959> so<00:12:17.160> this<00:12:17.279> could<00:12:17.440> be<00:12:17.560> you<00:12:17.600> know<00:12:17.760> 32e 00:12:18.310 --> 00:12:18.320 align:start position:0% s stake so this could be you know 32e 00:12:18.320 --> 00:12:20.949 align:start position:0% s stake so this could be you know 32e 364<00:12:19.199> etc<00:12:19.519> etc<00:12:20.079> how<00:12:20.199> does<00:12:20.360> it<00:12:20.480> get<00:12:20.600> into<00:12:20.800> the 00:12:20.949 --> 00:12:20.959 align:start position:0% 364 etc etc how does it get into the 00:12:20.959 --> 00:12:22.990 align:start position:0% 364 etc etc how does it get into the committee<00:12:21.800> uh<00:12:21.920> it<00:12:22.000> is<00:12:22.199> selected<00:12:22.800> with 00:12:22.990 --> 00:12:23.000 align:start position:0% committee uh it is selected with 00:12:23.000 --> 00:12:26.069 align:start position:0% committee uh it is selected with probability<00:12:24.000> s<00:12:24.279> overt<00:12:25.000> so<00:12:25.399> proportional<00:12:25.880> to 00:12:26.069 --> 00:12:26.079 align:start position:0% probability s overt so proportional to 00:12:26.079 --> 00:12:29.750 align:start position:0% probability s overt so proportional to stake<00:12:27.079> and<00:12:27.639> uh<00:12:27.800> it<00:12:28.040> has<00:12:28.440> uh<00:12:28.519> it<00:12:28.639> gets<00:12:28.880> reward<00:12:29.160> Ed 00:12:29.750 --> 00:12:29.760 align:start position:0% stake and uh it has uh it gets reward Ed 00:12:29.760 --> 00:12:31.350 align:start position:0% stake and uh it has uh it gets reward Ed when<00:12:29.920> it<00:12:30.040> is<00:12:30.199> in<00:12:30.279> the<00:12:30.399> committee<00:12:30.800> so<00:12:30.959> if<00:12:31.079> it<00:12:31.199> is 00:12:31.350 --> 00:12:31.360 align:start position:0% when it is in the committee so if it is 00:12:31.360 --> 00:12:32.430 align:start position:0% when it is in the committee so if it is actually<00:12:31.560> in<00:12:31.639> the<00:12:31.760> committee<00:12:32.160> it<00:12:32.240> is 00:12:32.430 --> 00:12:32.440 align:start position:0% actually in the committee it is 00:12:32.440 --> 00:12:34.509 align:start position:0% actually in the committee it is participating<00:12:33.120> it's<00:12:33.240> a<00:12:33.440> testing<00:12:34.160> it<00:12:34.279> gets 00:12:34.509 --> 00:12:34.519 align:start position:0% participating it's a testing it gets 00:12:34.519 --> 00:12:36.230 align:start position:0% participating it's a testing it gets rewarded<00:12:34.959> with<00:12:35.120> some<00:12:35.320> constant<00:12:35.680> reward<00:12:36.120> that 00:12:36.230 --> 00:12:36.240 align:start position:0% rewarded with some constant reward that 00:12:36.240 --> 00:12:38.269 align:start position:0% rewarded with some constant reward that does<00:12:36.399> not<00:12:36.560> depend<00:12:36.839> on<00:12:36.959> stake<00:12:37.680> so<00:12:37.880> this<00:12:38.000> is<00:12:38.120> sort 00:12:38.269 --> 00:12:38.279 align:start position:0% does not depend on stake so this is sort 00:12:38.279 --> 00:12:40.350 align:start position:0% does not depend on stake so this is sort of<00:12:38.440> the<00:12:38.600> opposite<00:12:39.000> of<00:12:39.160> what<00:12:39.279> happens<00:12:40.120> uh<00:12:40.279> you 00:12:40.350 --> 00:12:40.360 align:start position:0% of the opposite of what happens uh you 00:12:40.360 --> 00:12:42.750 align:start position:0% of the opposite of what happens uh you know<00:12:40.600> how<00:12:40.760> you<00:12:40.920> normally<00:12:41.240> do<00:12:41.480> this<00:12:41.959> where<00:12:42.519> the 00:12:42.750 --> 00:12:42.760 align:start position:0% know how you normally do this where the 00:12:42.760 --> 00:12:45.269 align:start position:0% know how you normally do this where the selection<00:12:43.240> is<00:12:43.440> random<00:12:44.079> so<00:12:44.800> you<00:12:44.880> don't<00:12:45.160> make 00:12:45.269 --> 00:12:45.279 align:start position:0% selection is random so you don't make 00:12:45.279 --> 00:12:47.069 align:start position:0% selection is random so you don't make the<00:12:45.399> selection<00:12:45.760> proportional<00:12:46.199> to<00:12:46.360> stake<00:12:46.920> but 00:12:47.069 --> 00:12:47.079 align:start position:0% the selection proportional to stake but 00:12:47.079 --> 00:12:49.430 align:start position:0% the selection proportional to stake but the<00:12:47.279> rewards<00:12:47.600> are<00:12:47.800> proportional<00:12:48.160> to<00:12:48.320> stake<00:12:49.160> um 00:12:49.430 --> 00:12:49.440 align:start position:0% the rewards are proportional to stake um 00:12:49.440 --> 00:12:51.470 align:start position:0% the rewards are proportional to stake um but<00:12:50.000> because<00:12:50.600> you<00:12:50.680> know<00:12:50.800> we<00:12:50.920> still<00:12:51.120> have<00:12:51.240> this 00:12:51.470 --> 00:12:51.480 align:start position:0% but because you know we still have this 00:12:51.480 --> 00:12:53.389 align:start position:0% but because you know we still have this proportionality<00:12:52.040> in<00:12:52.199> one<00:12:52.320> of<00:12:52.440> the<00:12:52.560> two<00:12:52.720> terms 00:12:53.389 --> 00:12:53.399 align:start position:0% proportionality in one of the two terms 00:12:53.399 --> 00:12:55.430 align:start position:0% proportionality in one of the two terms you<00:12:53.600> still<00:12:53.839> get<00:12:54.040> that<00:12:54.240> the<00:12:54.440> expected<00:12:54.880> rewards 00:12:55.430 --> 00:12:55.440 align:start position:0% you still get that the expected rewards 00:12:55.440 --> 00:12:57.389 align:start position:0% you still get that the expected rewards per<00:12:55.680> validator<00:12:56.360> are<00:12:56.519> still<00:12:56.800> proportional<00:12:57.240> to 00:12:57.389 --> 00:12:57.399 align:start position:0% per validator are still proportional to 00:12:57.399 --> 00:13:00.550 align:start position:0% per validator are still proportional to stake<00:12:57.720> as<00:12:57.959> they<00:12:58.320> of<00:12:58.480> course<00:12:58.680> should<00:12:58.839> be 00:13:00.550 --> 00:13:00.560 align:start position:0% stake as they of course should be 00:13:00.560 --> 00:13:02.230 align:start position:0% stake as they of course should be and<00:13:00.920> so<00:13:01.199> what<00:13:01.399> what<00:13:01.480> does<00:13:01.600> this<00:13:01.760> look<00:13:01.920> like<00:13:02.040> in 00:13:02.230 --> 00:13:02.240 align:start position:0% and so what what does this look like in 00:13:02.240 --> 00:13:04.470 align:start position:0% and so what what does this look like in practice<00:13:03.160> um<00:13:03.279> on<00:13:03.440> the<00:13:03.639> top<00:13:03.839> you<00:13:03.959> see<00:13:04.320> a 00:13:04.470 --> 00:13:04.480 align:start position:0% practice um on the top you see a 00:13:04.480 --> 00:13:06.350 align:start position:0% practice um on the top you see a representation<00:13:05.000> of<00:13:05.120> a<00:13:05.240> validator<00:13:05.720> set<00:13:06.040> with 00:13:06.350 --> 00:13:06.360 align:start position:0% representation of a validator set with 00:13:06.360 --> 00:13:08.550 align:start position:0% representation of a validator set with different<00:13:07.000> uh<00:13:07.160> sizes<00:13:07.480> of<00:13:07.639> validators<00:13:08.399> for 00:13:08.550 --> 00:13:08.560 align:start position:0% different uh sizes of validators for 00:13:08.560 --> 00:13:10.629 align:start position:0% different uh sizes of validators for example<00:13:08.920> validator<00:13:09.360> with<00:13:09.560> the<00:13:09.680> size<00:13:09.920> T<00:13:10.480> could 00:13:10.629 --> 00:13:10.639 align:start position:0% example validator with the size T could 00:13:10.639 --> 00:13:13.590 align:start position:0% example validator with the size T could be<00:13:10.800> would<00:13:10.959> be<00:13:11.120> like<00:13:11.399> 248<00:13:12.199> e<00:13:12.839> and<00:13:12.959> then<00:13:13.120> there's 00:13:13.590 --> 00:13:13.600 align:start position:0% be would be like 248 e and then there's 00:13:13.600 --> 00:13:15.310 align:start position:0% be would be like 248 e and then there's uh<00:13:13.680> you<00:13:13.760> know<00:13:13.920> the<00:13:14.040> same<00:13:14.360> amount<00:13:14.600> of<00:13:14.760> stake 00:13:15.310 --> 00:13:15.320 align:start position:0% uh you know the same amount of stake 00:13:15.320 --> 00:13:17.269 align:start position:0% uh you know the same amount of stake split<00:13:15.639> up<00:13:15.800> in<00:13:15.920> different<00:13:16.199> ways<00:13:16.560> like<00:13:16.720> t<00:13:16.920> over2 00:13:17.269 --> 00:13:17.279 align:start position:0% split up in different ways like t over2 00:13:17.279 --> 00:13:19.990 align:start position:0% split up in different ways like t over2 t<00:13:17.519> over2<00:13:18.040> or<00:13:18.440> four<00:13:18.760> validators<00:13:19.240> of<00:13:19.440> size<00:13:19.720> T 00:13:19.990 --> 00:13:20.000 align:start position:0% t over2 or four validators of size T 00:13:20.000 --> 00:13:22.030 align:start position:0% t over2 or four validators of size T over4<00:13:21.000> and<00:13:21.079> then<00:13:21.199> you<00:13:21.320> see<00:13:21.519> this<00:13:21.680> kind<00:13:21.800> of 00:13:22.030 --> 00:13:22.040 align:start position:0% over4 and then you see this kind of 00:13:22.040 --> 00:13:24.110 align:start position:0% over4 and then you see this kind of projection<00:13:23.040> uh<00:13:23.320> down<00:13:23.519> to<00:13:23.680> the<00:13:23.800> orbit 00:13:24.110 --> 00:13:24.120 align:start position:0% projection uh down to the orbit 00:13:24.120 --> 00:13:26.110 align:start position:0% projection uh down to the orbit committee<00:13:24.880> this<00:13:25.079> projection<00:13:25.480> is<00:13:25.639> essentially 00:13:26.110 --> 00:13:26.120 align:start position:0% committee this projection is essentially 00:13:26.120 --> 00:13:28.430 align:start position:0% committee this projection is essentially trying<00:13:26.360> to<00:13:26.519> tell<00:13:26.720> you<00:13:27.399> what<00:13:27.560> is<00:13:27.760> the<00:13:27.959> expected 00:13:28.430 --> 00:13:28.440 align:start position:0% trying to tell you what is the expected 00:13:28.440 --> 00:13:30.509 align:start position:0% trying to tell you what is the expected outcome<00:13:29.160> when<00:13:29.279> you're<00:13:29.480> sampling<00:13:30.040> from<00:13:30.360> the 00:13:30.509 --> 00:13:30.519 align:start position:0% outcome when you're sampling from the 00:13:30.519 --> 00:13:32.350 align:start position:0% outcome when you're sampling from the validator<00:13:31.000> set<00:13:31.199> on<00:13:31.360> top<00:13:31.880> and<00:13:32.000> you're<00:13:32.160> getting 00:13:32.350 --> 00:13:32.360 align:start position:0% validator set on top and you're getting 00:13:32.360 --> 00:13:34.910 align:start position:0% validator set on top and you're getting an<00:13:32.519> orbit<00:13:32.839> committee<00:13:33.839> um<00:13:34.160> expected<00:13:34.600> here<00:13:34.760> is 00:13:34.910 --> 00:13:34.920 align:start position:0% an orbit committee um expected here is 00:13:34.920 --> 00:13:36.629 align:start position:0% an orbit committee um expected here is really<00:13:35.120> like<00:13:35.240> in<00:13:35.320> the<00:13:35.440> probability<00:13:35.920> sense<00:13:36.320> of 00:13:36.629 --> 00:13:36.639 align:start position:0% really like in the probability sense of 00:13:36.639 --> 00:13:39.430 align:start position:0% really like in the probability sense of expectation<00:13:37.639> so<00:13:38.480> the<00:13:38.760> let's<00:13:38.920> start<00:13:39.160> with<00:13:39.320> the 00:13:39.430 --> 00:13:39.440 align:start position:0% expectation so the let's start with the 00:13:39.440 --> 00:13:41.710 align:start position:0% expectation so the let's start with the with<00:13:39.519> the<00:13:39.600> one<00:13:39.720> on<00:13:39.839> the<00:13:40.000> left<00:13:40.440> the<00:13:40.760> Staker<00:13:41.240> with 00:13:41.710 --> 00:13:41.720 align:start position:0% with the one on the left the Staker with 00:13:41.720 --> 00:13:45.150 align:start position:0% with the one on the left the Staker with um<00:13:42.199> T<00:13:42.519> stake<00:13:43.079> 20048<00:13:43.800> e<00:13:44.000> for<00:13:44.160> example<00:13:44.760> will<00:13:44.920> be 00:13:45.150 --> 00:13:45.160 align:start position:0% um T stake 20048 e for example will be 00:13:45.160 --> 00:13:47.269 align:start position:0% um T stake 20048 e for example will be selected<00:13:45.639> always<00:13:46.120> with<00:13:46.279> probability<00:13:46.760> one 00:13:47.269 --> 00:13:47.279 align:start position:0% selected always with probability one 00:13:47.279 --> 00:13:48.750 align:start position:0% selected always with probability one it's<00:13:47.440> always<00:13:47.680> going<00:13:47.839> to<00:13:47.920> be<00:13:48.000> in<00:13:48.079> the<00:13:48.199> committee 00:13:48.750 --> 00:13:48.760 align:start position:0% it's always going to be in the committee 00:13:48.760 --> 00:13:50.749 align:start position:0% it's always going to be in the committee because<00:13:49.360> as<00:13:49.480> we<00:13:49.600> said<00:13:49.800> the<00:13:49.920> probability<00:13:50.360> was<00:13:50.519> s 00:13:50.749 --> 00:13:50.759 align:start position:0% because as we said the probability was s 00:13:50.759 --> 00:13:54.550 align:start position:0% because as we said the probability was s over<00:13:51.000> T<00:13:51.360> So<00:13:51.680> T<00:13:51.920> over<00:13:52.120> t<00:13:52.959> uh<00:13:53.199> just<00:13:53.680> always<00:13:53.959> in<00:13:54.079> the 00:13:54.550 --> 00:13:54.560 align:start position:0% over T So T over t uh just always in the 00:13:54.560 --> 00:13:57.269 align:start position:0% over T So T over t uh just always in the committee<00:13:55.560> uh<00:13:55.680> we<00:13:55.800> move<00:13:56.320> uh<00:13:56.519> next<00:13:56.759> to<00:13:56.920> the<00:13:57.079> T 00:13:57.269 --> 00:13:57.279 align:start position:0% committee uh we move uh next to the T 00:13:57.279 --> 00:13:59.550 align:start position:0% committee uh we move uh next to the T over2<00:13:57.639> and<00:13:57.759> T<00:13:57.920> over2<00:13:58.279> stakers<00:13:58.880> there<00:13:59.199> selected 00:13:59.550 --> 00:13:59.560 align:start position:0% over2 and T over2 stakers there selected 00:13:59.560 --> 00:14:01.110 align:start position:0% over2 and T over2 stakers there selected with<00:13:59.720> probability<00:14:00.120> one<00:14:00.360> half<00:14:00.759> so<00:14:00.920> they'll 00:14:01.110 --> 00:14:01.120 align:start position:0% with probability one half so they'll 00:14:01.120 --> 00:14:02.430 align:start position:0% with probability one half so they'll only<00:14:01.279> be<00:14:01.440> in<00:14:01.519> the<00:14:01.639> committee<00:14:02.000> half<00:14:02.120> of<00:14:02.240> the 00:14:02.430 --> 00:14:02.440 align:start position:0% only be in the committee half of the 00:14:02.440 --> 00:14:05.269 align:start position:0% only be in the committee half of the time<00:14:03.079> and<00:14:03.199> so<00:14:03.839> um<00:14:04.480> when<00:14:04.639> you<00:14:04.880> when<00:14:05.000> we<00:14:05.120> think 00:14:05.269 --> 00:14:05.279 align:start position:0% time and so um when you when we think 00:14:05.279 --> 00:14:07.550 align:start position:0% time and so um when you when we think about<00:14:05.519> expectations<00:14:06.320> essentially<00:14:06.839> we<00:14:07.120> expect 00:14:07.550 --> 00:14:07.560 align:start position:0% about expectations essentially we expect 00:14:07.560 --> 00:14:08.749 align:start position:0% about expectations essentially we expect that<00:14:07.759> one<00:14:07.920> of<00:14:08.079> the<00:14:08.160> two<00:14:08.320> will<00:14:08.440> be<00:14:08.560> in<00:14:08.639> the 00:14:08.749 --> 00:14:08.759 align:start position:0% that one of the two will be in the 00:14:08.759 --> 00:14:10.990 align:start position:0% that one of the two will be in the committee<00:14:09.279> but<00:14:09.440> only<00:14:09.680> one<00:14:09.839> of<00:14:09.959> the<00:14:10.079> two<00:14:10.800> of 00:14:10.990 --> 00:14:11.000 align:start position:0% committee but only one of the two of 00:14:11.000 --> 00:14:12.910 align:start position:0% committee but only one of the two of course<00:14:11.160> it<00:14:11.279> can<00:14:11.440> be<00:14:11.639> that<00:14:11.800> it's<00:14:12.040> both<00:14:12.320> or<00:14:12.480> none 00:14:12.910 --> 00:14:12.920 align:start position:0% course it can be that it's both or none 00:14:12.920 --> 00:14:14.829 align:start position:0% course it can be that it's both or none but<00:14:13.079> that's<00:14:13.279> just<00:14:13.519> the<00:14:13.720> expected<00:14:14.399> uh<00:14:14.600> case 00:14:14.829 --> 00:14:14.839 align:start position:0% but that's just the expected uh case 00:14:14.839 --> 00:14:17.030 align:start position:0% but that's just the expected uh case let's<00:14:15.000> say<00:14:15.639> and<00:14:15.800> two<00:14:16.040> over<00:14:16.240> four<00:14:16.600> same<00:14:16.800> thing 00:14:17.030 --> 00:14:17.040 align:start position:0% let's say and two over four same thing 00:14:17.040 --> 00:14:19.910 align:start position:0% let's say and two over four same thing they're<00:14:17.240> all<00:14:17.399> selectability<00:14:18.279> 1/4<00:14:19.279> so<00:14:19.519> that<00:14:19.720> we 00:14:19.910 --> 00:14:19.920 align:start position:0% they're all selectability 1/4 so that we 00:14:19.920 --> 00:14:21.230 align:start position:0% they're all selectability 1/4 so that we expect<00:14:20.199> one<00:14:20.360> of<00:14:20.480> them<00:14:20.639> to<00:14:20.759> be<00:14:20.839> in<00:14:20.959> the 00:14:21.230 --> 00:14:21.240 align:start position:0% expect one of them to be in the 00:14:21.240 --> 00:14:24.189 align:start position:0% expect one of them to be in the committee<00:14:22.240> and<00:14:22.600> this<00:14:22.800> way<00:14:23.000> of<00:14:23.199> selecting<00:14:23.959> as 00:14:24.189 --> 00:14:24.199 align:start position:0% committee and this way of selecting as 00:14:24.199 --> 00:14:25.870 align:start position:0% committee and this way of selecting as essentially<00:14:24.639> this<00:14:24.839> interes<00:14:25.199> in<00:14:25.399> property 00:14:25.870 --> 00:14:25.880 align:start position:0% essentially this interes in property 00:14:25.880 --> 00:14:27.949 align:start position:0% essentially this interes in property that<00:14:26.600> um<00:14:26.920> no<00:14:27.079> matter<00:14:27.320> how<00:14:27.440> you<00:14:27.560> split<00:14:27.839> the 00:14:27.949 --> 00:14:27.959 align:start position:0% that um no matter how you split the 00:14:27.959 --> 00:14:30.790 align:start position:0% that um no matter how you split the stake<00:14:28.399> so<00:14:28.600> in<00:14:28.800> very<00:14:29.279> to<00:14:29.480> the<00:14:29.759> stake<00:14:30.360> uh<00:14:30.440> to<00:14:30.639> the 00:14:30.790 --> 00:14:30.800 align:start position:0% stake so in very to the stake uh to the 00:14:30.800 --> 00:14:33.829 align:start position:0% stake so in very to the stake uh to the stake<00:14:31.399> distribution<00:14:32.399> the<00:14:32.759> size<00:14:33.000> of<00:14:33.160> the<00:14:33.519> orbit 00:14:33.829 --> 00:14:33.839 align:start position:0% stake distribution the size of the orbit 00:14:33.839 --> 00:14:35.550 align:start position:0% stake distribution the size of the orbit committee<00:14:34.240> is<00:14:34.360> always<00:14:34.639> the<00:14:34.759> same<00:14:35.199> so<00:14:35.320> you<00:14:35.440> can 00:14:35.550 --> 00:14:35.560 align:start position:0% committee is always the same so you can 00:14:35.560 --> 00:14:37.749 align:start position:0% committee is always the same so you can see<00:14:35.839> you<00:14:35.959> know<00:14:36.079> on<00:14:36.199> the<00:14:36.360> orbit<00:14:36.680> committee<00:14:37.079> line 00:14:37.749 --> 00:14:37.759 align:start position:0% see you know on the orbit committee line 00:14:37.759 --> 00:14:39.590 align:start position:0% see you know on the orbit committee line uh<00:14:37.839> it<00:14:37.959> doesn't<00:14:38.279> matter<00:14:38.920> if<00:14:39.000> we<00:14:39.160> split<00:14:39.480> the 00:14:39.590 --> 00:14:39.600 align:start position:0% uh it doesn't matter if we split the 00:14:39.600 --> 00:14:42.790 align:start position:0% uh it doesn't matter if we split the stake<00:14:39.920> as<00:14:40.480> t<00:14:40.920> or<00:14:41.120> T<00:14:41.320> over2<00:14:41.680> and<00:14:41.800> T<00:14:41.959> over2<00:14:42.519> or<00:14:42.680> the 00:14:42.790 --> 00:14:42.800 align:start position:0% stake as t or T over2 and T over2 or the 00:14:42.800 --> 00:14:45.110 align:start position:0% stake as t or T over2 and T over2 or the other<00:14:43.079> case<00:14:43.759> the<00:14:43.959> expected<00:14:44.399> case<00:14:44.600> is<00:14:44.720> that<00:14:44.920> we 00:14:45.110 --> 00:14:45.120 align:start position:0% other case the expected case is that we 00:14:45.120 --> 00:14:48.550 align:start position:0% other case the expected case is that we always<00:14:45.360> get<00:14:45.680> one<00:14:46.199> validator<00:14:47.120> per<00:14:47.480> T<00:14:47.880> stake 00:14:48.550 --> 00:14:48.560 align:start position:0% always get one validator per T stake 00:14:48.560 --> 00:14:50.150 align:start position:0% always get one validator per T stake essentially<00:14:49.399> and<00:14:49.480> so<00:14:49.639> this<00:14:49.759> is<00:14:49.880> essentially 00:14:50.150 --> 00:14:50.160 align:start position:0% essentially and so this is essentially 00:14:50.160 --> 00:14:52.030 align:start position:0% essentially and so this is essentially what<00:14:50.279> gives<00:14:50.440> us<00:14:50.600> validator<00:14:51.040> set<00:14:51.320> capping<00:14:51.880> at 00:14:52.030 --> 00:14:52.040 align:start position:0% what gives us validator set capping at 00:14:52.040 --> 00:14:54.350 align:start position:0% what gives us validator set capping at least<00:14:52.240> in<00:14:52.560> expectation<00:14:53.560> but<00:14:53.720> then<00:14:54.040> this<00:14:54.160> is 00:14:54.350 --> 00:14:54.360 align:start position:0% least in expectation but then this is 00:14:54.360 --> 00:14:56.350 align:start position:0% least in expectation but then this is easy<00:14:54.560> to<00:14:54.720> turn<00:14:54.920> into<00:14:55.279> actual<00:14:55.639> validator<00:14:56.160> set 00:14:56.350 --> 00:14:56.360 align:start position:0% easy to turn into actual validator set 00:14:56.360 --> 00:14:58.790 align:start position:0% easy to turn into actual validator set capping<00:14:56.959> in<00:14:57.160> practice<00:14:58.040> because<00:14:58.360> the<00:14:58.519> variance 00:14:58.790 --> 00:14:58.800 align:start position:0% capping in practice because the variance 00:14:58.800 --> 00:15:00.910 align:start position:0% capping in practice because the variance is<00:14:59.040> low<00:14:59.360> basically<00:14:59.959> and<00:15:00.199> we<00:15:00.320> can<00:15:00.480> we<00:15:00.600> can<00:15:00.720> just 00:15:00.910 --> 00:15:00.920 align:start position:0% is low basically and we can we can just 00:15:00.920 --> 00:15:03.110 align:start position:0% is low basically and we can we can just cap<00:15:01.160> it<00:15:01.360> and<00:15:01.600> and<00:15:01.880> and<00:15:02.320> yeah<00:15:02.720> it's<00:15:02.839> not<00:15:03.040> it's 00:15:03.110 --> 00:15:03.120 align:start position:0% cap it and and and yeah it's not it's 00:15:03.120 --> 00:15:05.230 align:start position:0% cap it and and and yeah it's not it's not<00:15:03.240> a<00:15:03.360> big<00:15:03.480> deal<00:15:03.759> then<00:15:04.600> um<00:15:04.759> so<00:15:04.959> yeah<00:15:05.079> more 00:15:05.230 --> 00:15:05.240 align:start position:0% not a big deal then um so yeah more 00:15:05.240 --> 00:15:06.990 align:start position:0% not a big deal then um so yeah more concretely<00:15:06.079> with<00:15:06.240> a<00:15:06.360> bit<00:15:06.519> more<00:15:06.680> you<00:15:06.800> know 00:15:06.990 --> 00:15:07.000 align:start position:0% concretely with a bit more you know 00:15:07.000 --> 00:15:09.550 align:start position:0% concretely with a bit more you know dramatic<00:15:07.399> effect<00:15:08.040> of<00:15:08.399> uh<00:15:08.480> looking<00:15:08.759> at<00:15:08.920> a<00:15:09.279> much 00:15:09.550 --> 00:15:09.560 align:start position:0% dramatic effect of uh looking at a much 00:15:09.560 --> 00:15:12.749 align:start position:0% dramatic effect of uh looking at a much much<00:15:10.399> um<00:15:11.399> more<00:15:11.600> out<00:15:11.759> of<00:15:11.959> proportion<00:15:12.399> kind<00:15:12.560> of 00:15:12.749 --> 00:15:12.759 align:start position:0% much um more out of proportion kind of 00:15:12.759 --> 00:15:15.189 align:start position:0% much um more out of proportion kind of way<00:15:12.920> of<00:15:13.000> splitting<00:15:13.399> stake<00:15:14.199> uh<00:15:14.320> we<00:15:14.440> have<00:15:15.000> still 00:15:15.189 --> 00:15:15.199 align:start position:0% way of splitting stake uh we have still 00:15:15.199 --> 00:15:17.590 align:start position:0% way of splitting stake uh we have still this<00:15:15.360> like<00:15:15.560> 2048<00:15:16.279> e<00:15:16.519> validator<00:15:17.079> this<00:15:17.199> like<00:15:17.360> Max 00:15:17.590 --> 00:15:17.600 align:start position:0% this like 2048 e validator this like Max 00:15:17.600 --> 00:15:19.269 align:start position:0% this like 2048 e validator this like Max balance<00:15:17.920> validator<00:15:18.720> again<00:15:18.959> it<00:15:19.079> gets 00:15:19.269 --> 00:15:19.279 align:start position:0% balance validator again it gets 00:15:19.279 --> 00:15:22.749 align:start position:0% balance validator again it gets projected<00:15:19.759> down<00:15:20.240> to<00:15:20.480> a<00:15:20.639> single<00:15:21.600> uh<00:15:21.759> 2048<00:15:22.519> e 00:15:22.749 --> 00:15:22.759 align:start position:0% projected down to a single uh 2048 e 00:15:22.759 --> 00:15:25.949 align:start position:0% projected down to a single uh 2048 e validator<00:15:23.600> itself<00:15:24.160> so<00:15:24.320> it's<00:15:24.519> always<00:15:24.959> selected 00:15:25.949 --> 00:15:25.959 align:start position:0% validator itself so it's always selected 00:15:25.959 --> 00:15:27.829 align:start position:0% validator itself so it's always selected when<00:15:26.160> we<00:15:26.560> uh<00:15:26.720> take<00:15:27.000> the<00:15:27.360> uh<00:15:27.519> look<00:15:27.639> at<00:15:27.720> the 00:15:27.829 --> 00:15:27.839 align:start position:0% when we uh take the uh look at the 00:15:27.839 --> 00:15:29.509 align:start position:0% when we uh take the uh look at the picture<00:15:28.040> on<00:15:28.160> the<00:15:28.279> right<00:15:28.480> it's<00:15:28.680> the<00:15:29.160> amount<00:15:29.360> of 00:15:29.509 --> 00:15:29.519 align:start position:0% picture on the right it's the amount of 00:15:29.519 --> 00:15:31.389 align:start position:0% picture on the right it's the amount of stake<00:15:30.120> but<00:15:30.279> split<00:15:30.639> up<00:15:31.000> much<00:15:31.199> more 00:15:31.389 --> 00:15:31.399 align:start position:0% stake but split up much more 00:15:31.399 --> 00:15:34.230 align:start position:0% stake but split up much more dramatically<00:15:32.040> in<00:15:32.600> uh<00:15:33.440> however<00:15:33.639> many<00:15:33.880> it<00:15:33.959> is<00:15:34.120> I 00:15:34.230 --> 00:15:34.240 align:start position:0% dramatically in uh however many it is I 00:15:34.240 --> 00:15:37.949 align:start position:0% dramatically in uh however many it is I guess<00:15:34.399> 64<00:15:34.880> validators<00:15:35.800> of<00:15:36.199> uh<00:15:36.319> 32<00:15:37.000> with<00:15:37.160> 32 00:15:37.949 --> 00:15:37.959 align:start position:0% guess 64 validators of uh 32 with 32 00:15:37.959 --> 00:15:39.389 align:start position:0% guess 64 validators of uh 32 with 32 each<00:15:38.199> each<00:15:38.480> so<00:15:38.639> this<00:15:38.720> could<00:15:38.880> be<00:15:38.959> you<00:15:39.000> know<00:15:39.120> Soul 00:15:39.389 --> 00:15:39.399 align:start position:0% each each so this could be you know Soul 00:15:39.399 --> 00:15:41.710 align:start position:0% each each so this could be you know Soul stakers<00:15:39.800> just<00:15:40.160> complete<00:15:40.480> different<00:15:40.720> entities 00:15:41.710 --> 00:15:41.720 align:start position:0% stakers just complete different entities 00:15:41.720 --> 00:15:43.350 align:start position:0% stakers just complete different entities and<00:15:41.920> again<00:15:42.120> when<00:15:42.240> we<00:15:42.399> project<00:15:42.759> down<00:15:43.079> we<00:15:43.199> only 00:15:43.350 --> 00:15:43.360 align:start position:0% and again when we project down we only 00:15:43.360 --> 00:15:45.269 align:start position:0% and again when we project down we only get<00:15:43.560> one<00:15:43.759> validator<00:15:44.399> so<00:15:44.600> what<00:15:44.720> does<00:15:44.839> this<00:15:45.040> mean 00:15:45.269 --> 00:15:45.279 align:start position:0% get one validator so what does this mean 00:15:45.279 --> 00:15:47.790 align:start position:0% get one validator so what does this mean that<00:15:45.600> just<00:15:46.000> on<00:15:46.279> average<00:15:46.800> each<00:15:46.959> of<00:15:47.199> those<00:15:47.560> will 00:15:47.790 --> 00:15:47.800 align:start position:0% that just on average each of those will 00:15:47.800 --> 00:15:50.509 align:start position:0% that just on average each of those will participate<00:15:48.319> only<00:15:48.600> once<00:15:49.040> every<00:15:49.279> 64<00:15:49.759> slots 00:15:50.509 --> 00:15:50.519 align:start position:0% participate only once every 64 slots 00:15:50.519 --> 00:15:53.069 align:start position:0% participate only once every 64 slots essentially<00:15:51.519> so<00:15:51.800> that<00:15:52.120> still<00:15:52.480> the<00:15:52.639> expected 00:15:53.069 --> 00:15:53.079 align:start position:0% essentially so that still the expected 00:15:53.079 --> 00:15:54.629 align:start position:0% essentially so that still the expected contribution<00:15:53.519> to<00:15:53.680> the<00:15:53.759> orbit<00:15:54.040> committee<00:15:54.480> is 00:15:54.629 --> 00:15:54.639 align:start position:0% contribution to the orbit committee is 00:15:54.639 --> 00:15:55.749 align:start position:0% contribution to the orbit committee is just 00:15:55.749 --> 00:15:55.759 align:start position:0% just 00:15:55.759 --> 00:15:59.150 align:start position:0% just one<00:15:56.759> and<00:15:57.240> um<00:15:57.800> again<00:15:58.000> to<00:15:58.199> to<00:15:58.319> repeat<00:15:58.680> like<00:15:59.040> what 00:15:59.150 --> 00:15:59.160 align:start position:0% one and um again to to repeat like what 00:15:59.160 --> 00:16:01.870 align:start position:0% one and um again to to repeat like what does<00:15:59.319> this<00:15:59.480> get<00:15:59.639> us<00:16:00.160> first<00:16:00.319> of<00:16:00.600> all<00:16:01.600> uh<00:16:01.759> what 00:16:01.870 --> 00:16:01.880 align:start position:0% does this get us first of all uh what 00:16:01.880 --> 00:16:03.550 align:start position:0% does this get us first of all uh what I've<00:16:02.279> tried<00:16:02.480> to<00:16:02.600> argue<00:16:03.040> uh<00:16:03.160> in<00:16:03.240> the<00:16:03.319> previous 00:16:03.550 --> 00:16:03.560 align:start position:0% I've tried to argue uh in the previous 00:16:03.560 --> 00:16:05.470 align:start position:0% I've tried to argue uh in the previous slides<00:16:03.880> is<00:16:04.040> it<00:16:04.199> gets<00:16:04.399> us<00:16:04.759> validator<00:16:05.199> set 00:16:05.470 --> 00:16:05.480 align:start position:0% slides is it gets us validator set 00:16:05.480 --> 00:16:08.350 align:start position:0% slides is it gets us validator set capping<00:16:06.399> basically<00:16:06.720> out<00:16:06.880> of<00:16:07.000> the<00:16:07.120> box<00:16:07.880> so<00:16:08.240> if 00:16:08.350 --> 00:16:08.360 align:start position:0% capping basically out of the box so if 00:16:08.360 --> 00:16:10.829 align:start position:0% capping basically out of the box so if you<00:16:08.480> say<00:16:08.720> that<00:16:08.959> D<00:16:09.319> is<00:16:09.480> the<00:16:09.639> total<00:16:10.000> deposit<00:16:10.399> size 00:16:10.829 --> 00:16:10.839 align:start position:0% you say that D is the total deposit size 00:16:10.839 --> 00:16:12.430 align:start position:0% you say that D is the total deposit size so<00:16:11.000> today<00:16:11.319> this<00:16:11.440> is<00:16:11.639> just<00:16:11.880> the<00:16:12.000> total<00:16:12.240> amount 00:16:12.430 --> 00:16:12.440 align:start position:0% so today this is just the total amount 00:16:12.440 --> 00:16:14.309 align:start position:0% so today this is just the total amount of<00:16:12.560> stake<00:16:13.160> which<00:16:13.319> today<00:16:13.560> would<00:16:13.720> be<00:16:13.880> 35 00:16:14.309 --> 00:16:14.319 align:start position:0% of stake which today would be 35 00:16:14.319 --> 00:16:16.670 align:start position:0% of stake which today would be 35 Millions<00:16:15.319> uh<00:16:15.480> this<00:16:15.680> potentially<00:16:16.079> means<00:16:16.399> that 00:16:16.670 --> 00:16:16.680 align:start position:0% Millions uh this potentially means that 00:16:16.680 --> 00:16:19.069 align:start position:0% Millions uh this potentially means that the<00:16:16.920> expected<00:16:17.440> size<00:16:17.839> of<00:16:17.959> the<00:16:18.079> orbit<00:16:18.440> committee 00:16:19.069 --> 00:16:19.079 align:start position:0% the expected size of the orbit committee 00:16:19.079 --> 00:16:22.509 align:start position:0% the expected size of the orbit committee is<00:16:19.279> D<00:16:19.800> overt<00:16:20.800> and<00:16:21.000> this<00:16:21.120> would<00:16:21.319> be<00:16:21.759> basically 00:16:22.509 --> 00:16:22.519 align:start position:0% is D overt and this would be basically 00:16:22.519 --> 00:16:26.189 align:start position:0% is D overt and this would be basically with<00:16:22.800> this<00:16:23.040> parameters<00:16:23.880> around<00:16:24.600> 177,000<00:16:25.600> so 00:16:26.189 --> 00:16:26.199 align:start position:0% with this parameters around 177,000 so 00:16:26.199 --> 00:16:28.470 align:start position:0% with this parameters around 177,000 so uh<00:16:26.319> before<00:16:26.560> I<00:16:26.680> said<00:16:27.160> today<00:16:27.440> we<00:16:27.600> handle<00:16:28.120> exactly 00:16:28.470 --> 00:16:28.480 align:start position:0% uh before I said today we handle exactly 00:16:28.480 --> 00:16:30.949 align:start position:0% uh before I said today we handle exactly twice<00:16:28.720> as<00:16:29.000> much<00:16:29.120> of<00:16:29.240> that<00:16:29.440> 34,000<00:16:30.240> each<00:16:30.440> slot 00:16:30.949 --> 00:16:30.959 align:start position:0% twice as much of that 34,000 each slot 00:16:30.959 --> 00:16:31.949 align:start position:0% twice as much of that 34,000 each slot so<00:16:31.079> we<00:16:31.199> already<00:16:31.399> know<00:16:31.639> that<00:16:31.759> this<00:16:31.800> is 00:16:31.949 --> 00:16:31.959 align:start position:0% so we already know that this is 00:16:31.959 --> 00:16:33.590 align:start position:0% so we already know that this is something<00:16:32.319> that<00:16:32.600> we're<00:16:32.839> perfectly<00:16:33.279> able 00:16:33.590 --> 00:16:33.600 align:start position:0% something that we're perfectly able 00:16:33.600 --> 00:16:36.069 align:start position:0% something that we're perfectly able technically<00:16:34.360> to<00:16:34.600> to<00:16:34.800> handle<00:16:35.720> and<00:16:35.839> then<00:16:35.959> it 00:16:36.069 --> 00:16:36.079 align:start position:0% technically to to handle and then it 00:16:36.079 --> 00:16:38.269 align:start position:0% technically to to handle and then it gets<00:16:36.279> us<00:16:36.720> uh<00:16:37.040> if<00:16:37.240> we<00:16:37.440> have<00:16:37.959> enough 00:16:38.269 --> 00:16:38.279 align:start position:0% gets us uh if we have enough 00:16:38.279 --> 00:16:40.269 align:start position:0% gets us uh if we have enough consolidation<00:16:38.959> like<00:16:39.120> if<00:16:39.279> we<00:16:39.440> have<00:16:39.639> you<00:16:39.720> know 00:16:40.269 --> 00:16:40.279 align:start position:0% consolidation like if we have you know 00:16:40.279 --> 00:16:43.749 align:start position:0% consolidation like if we have you know um<00:16:41.120> staking<00:16:41.600> pools<00:16:42.360> and<00:16:42.480> so<00:16:42.639> on<00:16:42.920> consolidate 00:16:43.749 --> 00:16:43.759 align:start position:0% um staking pools and so on consolidate 00:16:43.759 --> 00:16:46.430 align:start position:0% um staking pools and so on consolidate enough<00:16:44.360> it<00:16:44.519> gets<00:16:44.759> us<00:16:45.600> uh<00:16:45.720> the<00:16:45.880> possibility<00:16:46.279> of 00:16:46.430 --> 00:16:46.440 align:start position:0% enough it gets us uh the possibility of 00:16:46.440 --> 00:16:48.309 align:start position:0% enough it gets us uh the possibility of having<00:16:46.759> high<00:16:46.959> economic<00:16:47.360> finality 00:16:48.309 --> 00:16:48.319 align:start position:0% having high economic finality 00:16:48.319 --> 00:16:49.990 align:start position:0% having high economic finality immediately<00:16:49.079> like<00:16:49.240> a<00:16:49.399> single<00:16:49.680> orbit 00:16:49.990 --> 00:16:50.000 align:start position:0% immediately like a single orbit 00:16:50.000 --> 00:16:51.509 align:start position:0% immediately like a single orbit committee<00:16:50.360> might<00:16:50.480> be<00:16:50.680> small<00:16:51.040> it<00:16:51.120> might<00:16:51.319> only 00:16:51.509 --> 00:16:51.519 align:start position:0% committee might be small it might only 00:16:51.519 --> 00:16:53.949 align:start position:0% committee might be small it might only be<00:16:51.720> 17,000<00:16:52.399> validators<00:16:53.360> but<00:16:53.560> it<00:16:53.680> should 00:16:53.949 --> 00:16:53.959 align:start position:0% be 17,000 validators but it should 00:16:53.959 --> 00:16:56.470 align:start position:0% be 17,000 validators but it should contain<00:16:54.800> most<00:16:55.079> of<00:16:55.240> the<00:16:55.399> stake<00:16:56.000> essentially 00:16:56.470 --> 00:16:56.480 align:start position:0% contain most of the stake essentially 00:16:56.480 --> 00:16:58.309 align:start position:0% contain most of the stake essentially like<00:16:56.680> most<00:16:56.920> of<00:16:57.120> the<00:16:57.319> Consolidated<00:16:57.839> stake<00:16:58.120> will 00:16:58.309 --> 00:16:58.319 align:start position:0% like most of the Consolidated stake will 00:16:58.319 --> 00:17:01.309 align:start position:0% like most of the Consolidated stake will always<00:16:58.560> be<00:16:58.920> in<00:16:59.279> it<00:17:00.279> and<00:17:00.399> then<00:17:00.639> another<00:17:01.079> aspect 00:17:01.309 --> 00:17:01.319 align:start position:0% always be in it and then another aspect 00:17:01.319 --> 00:17:02.949 align:start position:0% always be in it and then another aspect that<00:17:01.440> I<00:17:01.519> did<00:17:01.680> not<00:17:01.839> touch<00:17:02.079> on<00:17:02.360> is<00:17:02.519> that<00:17:02.720> in 00:17:02.949 --> 00:17:02.959 align:start position:0% that I did not touch on is that in 00:17:02.959 --> 00:17:05.029 align:start position:0% that I did not touch on is that in principle<00:17:03.600> it<00:17:03.759> could<00:17:03.959> mean<00:17:04.319> that<00:17:04.600> it's<00:17:04.799> more 00:17:05.029 --> 00:17:05.039 align:start position:0% principle it could mean that it's more 00:17:05.039 --> 00:17:07.150 align:start position:0% principle it could mean that it's more plausible<00:17:05.520> to<00:17:05.679> lower<00:17:06.240> the<00:17:06.360> minimum<00:17:06.799> effective 00:17:07.150 --> 00:17:07.160 align:start position:0% plausible to lower the minimum effective 00:17:07.160 --> 00:17:09.590 align:start position:0% plausible to lower the minimum effective balance<00:17:07.640> so<00:17:07.839> this<00:17:07.959> is<00:17:08.079> the<00:17:08.240> 32<00:17:08.760> e<00:17:09.160> threshold 00:17:09.590 --> 00:17:09.600 align:start position:0% balance so this is the 32 e threshold 00:17:09.600 --> 00:17:12.069 align:start position:0% balance so this is the 32 e threshold for<00:17:09.839> entering<00:17:10.600> the<00:17:10.760> set<00:17:11.439> which<00:17:11.559> is<00:17:11.720> not<00:17:11.880> being 00:17:12.069 --> 00:17:12.079 align:start position:0% for entering the set which is not being 00:17:12.079 --> 00:17:14.710 align:start position:0% for entering the set which is not being touched<00:17:12.400> in<00:17:12.520> the<00:17:12.720> in<00:17:12.839> the<00:17:13.079> maxb<00:17:13.679> upgrade<00:17:14.559> this 00:17:14.710 --> 00:17:14.720 align:start position:0% touched in the in the maxb upgrade this 00:17:14.720 --> 00:17:17.189 align:start position:0% touched in the in the maxb upgrade this could<00:17:15.240> in<00:17:15.400> principle<00:17:15.839> be<00:17:16.079> be<00:17:16.360> actually<00:17:17.079> U 00:17:17.189 --> 00:17:17.199 align:start position:0% could in principle be be actually U 00:17:17.199 --> 00:17:18.949 align:start position:0% could in principle be be actually U easier<00:17:17.559> to<00:17:17.720> reduce<00:17:18.360> with<00:17:18.520> something<00:17:18.799> like 00:17:18.949 --> 00:17:18.959 align:start position:0% easier to reduce with something like 00:17:18.959 --> 00:17:21.110 align:start position:0% easier to reduce with something like orbit<00:17:19.439> just<00:17:19.640> because<00:17:20.039> the<00:17:20.240> mechanism<00:17:20.799> isn't 00:17:21.110 --> 00:17:21.120 align:start position:0% orbit just because the mechanism isn't 00:17:21.120 --> 00:17:22.710 align:start position:0% orbit just because the mechanism isn't really<00:17:21.400> sensitive<00:17:22.079> to<00:17:22.240> the<00:17:22.360> minimum 00:17:22.710 --> 00:17:22.720 align:start position:0% really sensitive to the minimum 00:17:22.720 --> 00:17:24.309 align:start position:0% really sensitive to the minimum effective<00:17:23.079> balance<00:17:23.439> if<00:17:23.520> you<00:17:23.640> notice<00:17:23.919> I<00:17:24.079> never 00:17:24.309 --> 00:17:24.319 align:start position:0% effective balance if you notice I never 00:17:24.319 --> 00:17:26.110 align:start position:0% effective balance if you notice I never actually<00:17:24.679> brought<00:17:24.919> it<00:17:25.039> up<00:17:25.400> in<00:17:25.600> any<00:17:25.799> of<00:17:25.919> the 00:17:26.110 --> 00:17:26.120 align:start position:0% actually brought it up in any of the 00:17:26.120 --> 00:17:27.189 align:start position:0% actually brought it up in any of the arguments 00:17:27.189 --> 00:17:27.199 align:start position:0% arguments 00:17:27.199 --> 00:17:29.470 align:start position:0% arguments before<00:17:28.199> and<00:17:28.559> uh<00:17:28.679> yeah<00:17:28.960> one<00:17:29.120> important 00:17:29.470 --> 00:17:29.480 align:start position:0% before and uh yeah one important 00:17:29.480 --> 00:17:31.230 align:start position:0% before and uh yeah one important question<00:17:29.760> here<00:17:29.960> is<00:17:30.400> so<00:17:30.600> this<00:17:30.720> sounds<00:17:31.000> like<00:17:31.120> a 00:17:31.230 --> 00:17:31.240 align:start position:0% question here is so this sounds like a 00:17:31.240 --> 00:17:32.750 align:start position:0% question here is so this sounds like a big<00:17:31.400> change<00:17:31.679> you're<00:17:31.880> s<00:17:32.160> you're<00:17:32.280> changing 00:17:32.750 --> 00:17:32.760 align:start position:0% big change you're s you're changing 00:17:32.760 --> 00:17:34.390 align:start position:0% big change you're s you're changing who's<00:17:33.120> participating<00:17:33.960> the<00:17:34.080> way<00:17:34.200> they're 00:17:34.390 --> 00:17:34.400 align:start position:0% who's participating the way they're 00:17:34.400 --> 00:17:37.029 align:start position:0% who's participating the way they're chosen<00:17:34.679> to<00:17:35.000> participate<00:17:36.000> um<00:17:36.400> what<00:17:36.559> does 00:17:37.029 --> 00:17:37.039 align:start position:0% chosen to participate um what does 00:17:37.039 --> 00:17:38.590 align:start position:0% chosen to participate um what does actually<00:17:37.600> you<00:17:37.679> know<00:17:37.840> what<00:17:37.960> changes<00:17:38.360> what<00:17:38.480> does 00:17:38.590 --> 00:17:38.600 align:start position:0% actually you know what changes what does 00:17:38.600 --> 00:17:41.110 align:start position:0% actually you know what changes what does home<00:17:38.799> staking<00:17:39.200> in<00:17:39.320> particular<00:17:40.000> uh<00:17:40.760> look<00:17:40.960> like 00:17:41.110 --> 00:17:41.120 align:start position:0% home staking in particular uh look like 00:17:41.120 --> 00:17:43.630 align:start position:0% home staking in particular uh look like in<00:17:41.240> this<00:17:41.440> world<00:17:42.160> so<00:17:42.400> let's<00:17:42.720> first<00:17:42.919> start<00:17:43.200> from 00:17:43.630 --> 00:17:43.640 align:start position:0% in this world so let's first start from 00:17:43.640 --> 00:17:45.430 align:start position:0% in this world so let's first start from actually<00:17:43.840> from<00:17:44.039> what<00:17:44.160> stays<00:17:44.440> the<00:17:44.559> same<00:17:45.280> which 00:17:45.430 --> 00:17:45.440 align:start position:0% actually from what stays the same which 00:17:45.440 --> 00:17:48.310 align:start position:0% actually from what stays the same which is<00:17:46.080> uh<00:17:46.240> the<00:17:46.440> frequency<00:17:47.240> of<00:17:47.600> participating<00:17:48.160> in 00:17:48.310 --> 00:17:48.320 align:start position:0% is uh the frequency of participating in 00:17:48.320 --> 00:17:50.830 align:start position:0% is uh the frequency of participating in Block<00:17:48.559> construction<00:17:49.280> so<00:17:49.720> proposals<00:17:50.600> and 00:17:50.830 --> 00:17:50.840 align:start position:0% Block construction so proposals and 00:17:50.840 --> 00:17:52.630 align:start position:0% Block construction so proposals and inclusion<00:17:51.240> list<00:17:51.520> proposals<00:17:52.000> once<00:17:52.200> we<00:17:52.320> do<00:17:52.480> have 00:17:52.630 --> 00:17:52.640 align:start position:0% inclusion list proposals once we do have 00:17:52.640 --> 00:17:54.990 align:start position:0% inclusion list proposals once we do have inclusion<00:17:53.080> list<00:17:53.600> which<00:17:53.760> hopefully<00:17:54.120> is<00:17:54.240> soon 00:17:54.990 --> 00:17:55.000 align:start position:0% inclusion list which hopefully is soon 00:17:55.000 --> 00:17:56.669 align:start position:0% inclusion list which hopefully is soon this<00:17:55.120> is<00:17:55.240> not<00:17:55.360> going<00:17:55.440> to<00:17:55.559> change<00:17:55.799> at<00:17:55.919> all<00:17:56.320> like 00:17:56.669 --> 00:17:56.679 align:start position:0% this is not going to change at all like 00:17:56.679 --> 00:17:58.590 align:start position:0% this is not going to change at all like uh<00:17:56.880> this<00:17:57.039> does<00:17:57.240> not<00:17:57.720> depend<00:17:58.039> at<00:17:58.159> all<00:17:58.360> on<00:17:58.480> the 00:17:58.590 --> 00:17:58.600 align:start position:0% uh this does not depend at all on the 00:17:58.600 --> 00:18:01.149 align:start position:0% uh this does not depend at all on the way<00:17:58.840> your<00:17:59.000> sample<00:17:59.280> to<00:17:59.440> ATT<00:17:59.679> test<00:18:00.679> uh<00:18:00.880> because 00:18:01.149 --> 00:18:01.159 align:start position:0% way your sample to ATT test uh because 00:18:01.159 --> 00:18:02.190 align:start position:0% way your sample to ATT test uh because essentially<00:18:01.520> there's<00:18:01.720> no<00:18:01.840> technical 00:18:02.190 --> 00:18:02.200 align:start position:0% essentially there's no technical 00:18:02.200 --> 00:18:04.029 align:start position:0% essentially there's no technical limitations<00:18:02.799> on<00:18:03.320> you<00:18:03.400> know<00:18:03.520> there's<00:18:03.679> only<00:18:03.880> one 00:18:04.029 --> 00:18:04.039 align:start position:0% limitations on you know there's only one 00:18:04.039 --> 00:18:05.710 align:start position:0% limitations on you know there's only one person<00:18:04.280> proposing<00:18:04.760> each<00:18:04.919> slot<00:18:05.320> there's<00:18:05.520> only 00:18:05.710 --> 00:18:05.720 align:start position:0% person proposing each slot there's only 00:18:05.720 --> 00:18:07.750 align:start position:0% person proposing each slot there's only maybe<00:18:05.919> a<00:18:06.000> few<00:18:06.240> people<00:18:06.440> making<00:18:06.760> inclusion<00:18:07.120> list 00:18:07.750 --> 00:18:07.760 align:start position:0% maybe a few people making inclusion list 00:18:07.760 --> 00:18:10.549 align:start position:0% maybe a few people making inclusion list uh<00:18:07.880> this<00:18:08.000> has<00:18:08.200> nothing<00:18:08.400> to<00:18:08.559> do<00:18:08.760> with<00:18:09.559> um<00:18:10.240> we<00:18:10.440> we 00:18:10.549 --> 00:18:10.559 align:start position:0% uh this has nothing to do with um we we 00:18:10.559 --> 00:18:12.070 align:start position:0% uh this has nothing to do with um we we don't<00:18:10.679> need<00:18:10.840> to<00:18:11.039> restrict<00:18:11.440> this<00:18:11.559> any<00:18:11.720> further 00:18:12.070 --> 00:18:12.080 align:start position:0% don't need to restrict this any further 00:18:12.080 --> 00:18:14.470 align:start position:0% don't need to restrict this any further essentially<00:18:13.080> and<00:18:13.480> uh<00:18:13.640> another<00:18:14.080> point<00:18:14.360> that 00:18:14.470 --> 00:18:14.480 align:start position:0% essentially and uh another point that 00:18:14.480 --> 00:18:15.870 align:start position:0% essentially and uh another point that I'm<00:18:14.600> not<00:18:14.799> going<00:18:14.919> to<00:18:15.000> be<00:18:15.120> able<00:18:15.280> to<00:18:15.400> get<00:18:15.520> into<00:18:15.760> is 00:18:15.870 --> 00:18:15.880 align:start position:0% I'm not going to be able to get into is 00:18:15.880 --> 00:18:18.830 align:start position:0% I'm not going to be able to get into is that<00:18:16.120> actually<00:18:16.480> the<00:18:16.799> influence<00:18:17.480> of<00:18:18.280> uh<00:18:18.559> home 00:18:18.830 --> 00:18:18.840 align:start position:0% that actually the influence of uh home 00:18:18.840 --> 00:18:20.510 align:start position:0% that actually the influence of uh home stay<00:18:19.159> carees<00:18:19.400> or<00:18:19.559> any<00:18:19.760> stares<00:18:20.240> for<00:18:20.360> that 00:18:20.510 --> 00:18:20.520 align:start position:0% stay carees or any stares for that 00:18:20.520 --> 00:18:23.789 align:start position:0% stay carees or any stares for that matter<00:18:21.039> on<00:18:21.280> lmd<00:18:21.840> ghost<00:18:22.679> uh<00:18:23.080> on<00:18:23.280> the<00:18:23.480> basically 00:18:23.789 --> 00:18:23.799 align:start position:0% matter on lmd ghost uh on the basically 00:18:23.799 --> 00:18:25.149 align:start position:0% matter on lmd ghost uh on the basically the<00:18:23.919> regular<00:18:24.200> fourth<00:18:24.520> choice<00:18:24.799> that<00:18:24.919> comes 00:18:25.149 --> 00:18:25.159 align:start position:0% the regular fourth choice that comes 00:18:25.159 --> 00:18:27.110 align:start position:0% the regular fourth choice that comes before<00:18:25.520> finality<00:18:26.240> would<00:18:26.480> completely<00:18:26.880> stay 00:18:27.110 --> 00:18:27.120 align:start position:0% before finality would completely stay 00:18:27.120 --> 00:18:28.990 align:start position:0% before finality would completely stay the<00:18:27.280> same<00:18:27.799> but<00:18:27.919> I'm<00:18:28.080> just<00:18:28.200> not<00:18:28.360> going<00:18:28.520> to<00:18:28.880> be 00:18:28.990 --> 00:18:29.000 align:start position:0% the same but I'm just not going to be 00:18:29.000 --> 00:18:30.630 align:start position:0% the same but I'm just not going to be able<00:18:29.159> to<00:18:29.280> explain<00:18:29.600> exactly<00:18:30.080> why<00:18:30.240> that<00:18:30.360> is<00:18:30.480> the 00:18:30.630 --> 00:18:30.640 align:start position:0% able to explain exactly why that is the 00:18:30.640 --> 00:18:32.870 align:start position:0% able to explain exactly why that is the casee<00:18:31.640> um<00:18:32.000> with<00:18:32.120> the<00:18:32.240> with<00:18:32.360> the<00:18:32.440> time<00:18:32.600> that<00:18:32.720> we 00:18:32.870 --> 00:18:32.880 align:start position:0% casee um with the with the time that we 00:18:32.880 --> 00:18:36.190 align:start position:0% casee um with the with the time that we have<00:18:33.720> and<00:18:34.120> uh<00:18:34.280> now<00:18:34.520> what<00:18:34.679> changes<00:18:35.440> so<00:18:36.000> one 00:18:36.190 --> 00:18:36.200 align:start position:0% have and uh now what changes so one 00:18:36.200 --> 00:18:38.110 align:start position:0% have and uh now what changes so one important<00:18:36.559> point<00:18:36.799> is<00:18:36.960> that<00:18:37.200> you<00:18:37.400> attest<00:18:37.880> less 00:18:38.110 --> 00:18:38.120 align:start position:0% important point is that you attest less 00:18:38.120 --> 00:18:40.149 align:start position:0% important point is that you attest less often<00:18:38.799> so<00:18:39.080> if<00:18:39.200> you<00:18:39.360> go<00:18:39.520> back<00:18:39.640> to<00:18:39.760> the<00:18:39.880> picture 00:18:40.149 --> 00:18:40.159 align:start position:0% often so if you go back to the picture 00:18:40.159 --> 00:18:42.549 align:start position:0% often so if you go back to the picture that<00:18:40.280> we<00:18:40.360> had<00:18:40.559> before<00:18:40.880> with<00:18:41.039> the<00:18:41.240> 64<00:18:42.159> small 00:18:42.549 --> 00:18:42.559 align:start position:0% that we had before with the 64 small 00:18:42.559 --> 00:18:45.870 align:start position:0% that we had before with the 64 small validators<00:18:43.320> with<00:18:43.480> 32<00:18:43.919> e<00:18:44.880> they're<00:18:45.080> only<00:18:45.320> chosen 00:18:45.870 --> 00:18:45.880 align:start position:0% validators with 32 e they're only chosen 00:18:45.880 --> 00:18:48.190 align:start position:0% validators with 32 e they're only chosen once<00:18:46.320> every<00:18:46.640> two<00:18:46.880> EPO<00:18:47.320> essentially<00:18:47.840> like<00:18:47.960> once 00:18:48.190 --> 00:18:48.200 align:start position:0% once every two EPO essentially like once 00:18:48.200 --> 00:18:50.909 align:start position:0% once every two EPO essentially like once every<00:18:48.520> 64<00:18:49.039> slots<00:18:49.840> uh<00:18:49.919> and<00:18:50.039> so<00:18:50.200> you<00:18:50.640> but<00:18:50.840> you 00:18:50.909 --> 00:18:50.919 align:start position:0% every 64 slots uh and so you but you 00:18:50.919 --> 00:18:52.950 align:start position:0% every 64 slots uh and so you but you know<00:18:51.080> it's<00:18:51.280> less<00:18:51.520> often<00:18:51.840> than<00:18:52.120> Consolidated 00:18:52.950 --> 00:18:52.960 align:start position:0% know it's less often than Consolidated 00:18:52.960 --> 00:18:56.310 align:start position:0% know it's less often than Consolidated validators<00:18:53.960> um<00:18:54.440> but<00:18:54.679> it's<00:18:54.919> it's<00:18:55.480> more<00:18:55.640> or<00:18:55.799> less 00:18:56.310 --> 00:18:56.320 align:start position:0% validators um but it's it's more or less 00:18:56.320 --> 00:18:58.510 align:start position:0% validators um but it's it's more or less as<00:18:56.480> often<00:18:56.720> as<00:18:56.880> today<00:18:57.440> just<00:18:57.720> half<00:18:57.919> as<00:18:58.080> often<00:18:58.440> as 00:18:58.510 --> 00:18:58.520 align:start position:0% as often as today just half as often as 00:18:58.520 --> 00:19:00.470 align:start position:0% as often as today just half as often as to<00:18:58.840> day<00:18:59.039> with<00:18:59.159> the<00:18:59.240> parameters<00:18:59.880> that<00:19:00.000> I<00:19:00.120> said 00:19:00.470 --> 00:19:00.480 align:start position:0% to day with the parameters that I said 00:19:00.480 --> 00:19:01.990 align:start position:0% to day with the parameters that I said you<00:19:00.679> instead<00:19:00.919> of<00:19:01.039> once<00:19:01.200> an<00:19:01.360> Epoch<00:19:01.720> you<00:19:01.799> only 00:19:01.990 --> 00:19:02.000 align:start position:0% you instead of once an Epoch you only 00:19:02.000 --> 00:19:04.149 align:start position:0% you instead of once an Epoch you only attest<00:19:02.320> once<00:19:02.480> every<00:19:02.679> two<00:19:02.880> EPO<00:19:03.799> but<00:19:04.000> the 00:19:04.149 --> 00:19:04.159 align:start position:0% attest once every two EPO but the 00:19:04.159 --> 00:19:06.510 align:start position:0% attest once every two EPO but the rewards<00:19:04.600> are<00:19:04.760> changed<00:19:05.120> in<00:19:05.280> such<00:19:05.440> a<00:19:05.559> way<00:19:05.760> that 00:19:06.510 --> 00:19:06.520 align:start position:0% rewards are changed in such a way that 00:19:06.520 --> 00:19:08.990 align:start position:0% rewards are changed in such a way that you're<00:19:06.799> not<00:19:07.320> earning<00:19:07.760> less<00:19:08.080> than<00:19:08.280> than<00:19:08.440> other 00:19:08.990 --> 00:19:09.000 align:start position:0% you're not earning less than than other 00:19:09.000 --> 00:19:11.430 align:start position:0% you're not earning less than than other Consolidated<00:19:09.840> validators<00:19:10.840> and<00:19:11.080> another 00:19:11.430 --> 00:19:11.440 align:start position:0% Consolidated validators and another 00:19:11.440 --> 00:19:13.669 align:start position:0% Consolidated validators and another point<00:19:11.799> that<00:19:12.000> it's<00:19:12.120> maybe<00:19:12.400> more<00:19:12.559> important<00:19:13.039> is 00:19:13.669 --> 00:19:13.679 align:start position:0% point that it's maybe more important is 00:19:13.679 --> 00:19:15.510 align:start position:0% point that it's maybe more important is uh<00:19:13.799> home<00:19:14.039> sakers<00:19:14.440> would<00:19:14.559> generally<00:19:14.960> have<00:19:15.240> less 00:19:15.510 --> 00:19:15.520 align:start position:0% uh home sakers would generally have less 00:19:15.520 --> 00:19:18.950 align:start position:0% uh home sakers would generally have less influence<00:19:15.919> over<00:19:16.440> finality<00:19:17.440> um<00:19:18.080> because<00:19:18.760> again 00:19:18.950 --> 00:19:18.960 align:start position:0% influence over finality um because again 00:19:18.960 --> 00:19:20.149 align:start position:0% influence over finality um because again if<00:19:19.039> you<00:19:19.159> think<00:19:19.320> about<00:19:19.520> that<00:19:19.679> picture<00:19:19.960> from 00:19:20.149 --> 00:19:20.159 align:start position:0% if you think about that picture from 00:19:20.159 --> 00:19:22.549 align:start position:0% if you think about that picture from before<00:19:20.480> you<00:19:20.600> have<00:19:20.720> the<00:19:20.880> 64<00:19:21.360> small<00:19:21.640> validator 00:19:22.549 --> 00:19:22.559 align:start position:0% before you have the 64 small validator 00:19:22.559 --> 00:19:24.630 align:start position:0% before you have the 64 small validator validators<00:19:23.200> they're<00:19:23.400> kind<00:19:23.520> of<00:19:23.760> compressed<00:19:24.400> to 00:19:24.630 --> 00:19:24.640 align:start position:0% validators they're kind of compressed to 00:19:24.640 --> 00:19:27.350 align:start position:0% validators they're kind of compressed to one<00:19:24.960> so<00:19:25.159> only<00:19:25.480> one<00:19:25.640> of<00:19:25.880> them<00:19:26.880> will<00:19:27.120> actually 00:19:27.350 --> 00:19:27.360 align:start position:0% one so only one of them will actually 00:19:27.360 --> 00:19:30.310 align:start position:0% one so only one of them will actually end<00:19:27.520> up<00:19:27.679> in<00:19:27.799> the<00:19:27.960> set<00:19:28.600> um<00:19:28.799> um<00:19:28.960> so<00:19:29.520> even<00:19:29.760> if<00:19:30.200> uh 00:19:30.310 --> 00:19:30.320 align:start position:0% end up in the set um um so even if uh 00:19:30.320 --> 00:19:32.669 align:start position:0% end up in the set um um so even if uh home<00:19:30.520> stakers<00:19:30.960> have<00:19:31.159> you<00:19:31.240> know<00:19:31.480> maybe<00:19:32.039> 10%<00:19:32.559> of 00:19:32.669 --> 00:19:32.679 align:start position:0% home stakers have you know maybe 10% of 00:19:32.679 --> 00:19:34.470 align:start position:0% home stakers have you know maybe 10% of the<00:19:32.799> stake<00:19:33.480> the<00:19:33.600> amount<00:19:33.840> of<00:19:33.960> stake<00:19:34.240> that<00:19:34.400> they 00:19:34.470 --> 00:19:34.480 align:start position:0% the stake the amount of stake that they 00:19:34.480 --> 00:19:36.149 align:start position:0% the stake the amount of stake that they will<00:19:34.720> have<00:19:34.880> in<00:19:35.039> the<00:19:35.200> orbit<00:19:35.520> committee<00:19:35.960> might 00:19:36.149 --> 00:19:36.159 align:start position:0% will have in the orbit committee might 00:19:36.159 --> 00:19:39.070 align:start position:0% will have in the orbit committee might be<00:19:36.640> compressed<00:19:37.640> one<00:19:37.919> point<00:19:38.240> there<00:19:38.440> is<00:19:38.679> so<00:19:38.960> this 00:19:39.070 --> 00:19:39.080 align:start position:0% be compressed one point there is so this 00:19:39.080 --> 00:19:40.750 align:start position:0% be compressed one point there is so this is<00:19:39.280> probably<00:19:39.960> I<00:19:40.039> would<00:19:40.200> say<00:19:40.360> the<00:19:40.480> most 00:19:40.750 --> 00:19:40.760 align:start position:0% is probably I would say the most 00:19:40.760 --> 00:19:43.870 align:start position:0% is probably I would say the most contentious<00:19:41.480> uh<00:19:41.640> part<00:19:42.120> of<00:19:42.280> of<00:19:42.440> this<00:19:42.880> proposal 00:19:43.870 --> 00:19:43.880 align:start position:0% contentious uh part of of this proposal 00:19:43.880 --> 00:19:46.630 align:start position:0% contentious uh part of of this proposal um<00:19:44.280> but<00:19:44.679> yeah<00:19:44.880> one<00:19:45.120> one<00:19:45.280> point<00:19:45.520> there<00:19:45.679> is<00:19:45.840> that 00:19:46.630 --> 00:19:46.640 align:start position:0% um but yeah one one point there is that 00:19:46.640 --> 00:19:48.430 align:start position:0% um but yeah one one point there is that it's<00:19:46.840> already<00:19:47.120> kind<00:19:47.280> of<00:19:47.440> the<00:19:47.600> case<00:19:48.240> there's 00:19:48.430 --> 00:19:48.440 align:start position:0% it's already kind of the case there's 00:19:48.440 --> 00:19:50.470 align:start position:0% it's already kind of the case there's already<00:19:48.960> very<00:19:49.200> little<00:19:49.840> uh<00:19:49.960> influence<00:19:50.320> that 00:19:50.470 --> 00:19:50.480 align:start position:0% already very little uh influence that 00:19:50.480 --> 00:19:51.950 align:start position:0% already very little uh influence that they<00:19:50.600> have<00:19:50.720> or<00:19:50.919> finality<00:19:51.520> because<00:19:51.760> there's 00:19:51.950 --> 00:19:51.960 align:start position:0% they have or finality because there's 00:19:51.960 --> 00:19:54.310 align:start position:0% they have or finality because there's only<00:19:52.360> maybe<00:19:52.760> 5<00:19:52.960> to<00:19:53.120> 10%<00:19:53.600> of<00:19:53.760> stake<00:19:54.120> that 00:19:54.310 --> 00:19:54.320 align:start position:0% only maybe 5 to 10% of stake that 00:19:54.320 --> 00:19:56.310 align:start position:0% only maybe 5 to 10% of stake that actually<00:19:54.559> belongs<00:19:54.919> to<00:19:55.120> to<00:19:55.240> home 00:19:56.310 --> 00:19:56.320 align:start position:0% actually belongs to to home 00:19:56.320 --> 00:19:59.149 align:start position:0% actually belongs to to home stakers<00:19:57.320> and<00:19:57.799> uh<00:19:58.039> yeah<00:19:58.200> I<00:19:58.280> mean<00:19:58.400> this<00:19:58.520> was 00:19:59.149 --> 00:19:59.159 align:start position:0% stakers and uh yeah I mean this was 00:19:59.159 --> 00:20:01.390 align:start position:0% stakers and uh yeah I mean this was just<00:19:59.640> bringing<00:20:00.280> uh<00:20:00.480> yeah<00:20:00.840> just<00:20:00.919> showing<00:20:01.240> you 00:20:01.390 --> 00:20:01.400 align:start position:0% just bringing uh yeah just showing you 00:20:01.400 --> 00:20:03.950 align:start position:0% just bringing uh yeah just showing you why<00:20:01.720> this<00:20:01.880> compression<00:20:02.280> happens<00:20:02.720> again<00:20:03.720> um 00:20:03.950 --> 00:20:03.960 align:start position:0% why this compression happens again um 00:20:03.960 --> 00:20:05.909 align:start position:0% why this compression happens again um and<00:20:04.200> one<00:20:04.400> last<00:20:04.600> point<00:20:04.880> is<00:20:05.320> we<00:20:05.440> would<00:20:05.640> probably 00:20:05.909 --> 00:20:05.919 align:start position:0% and one last point is we would probably 00:20:05.919 --> 00:20:07.870 align:start position:0% and one last point is we would probably want<00:20:06.080> to<00:20:06.240> ensure<00:20:06.600> that<00:20:07.159> we<00:20:07.280> do<00:20:07.480> have<00:20:07.600> enough 00:20:07.870 --> 00:20:07.880 align:start position:0% want to ensure that we do have enough 00:20:07.880 --> 00:20:09.350 align:start position:0% want to ensure that we do have enough consolidation<00:20:08.480> since<00:20:08.679> this<00:20:08.799> is<00:20:08.880> an<00:20:09.000> important 00:20:09.350 --> 00:20:09.360 align:start position:0% consolidation since this is an important 00:20:09.360 --> 00:20:11.270 align:start position:0% consolidation since this is an important part<00:20:09.559> of<00:20:09.679> how<00:20:09.799> we<00:20:09.960> get<00:20:10.400> better<00:20:10.799> guarantees 00:20:11.270 --> 00:20:11.280 align:start position:0% part of how we get better guarantees 00:20:11.280 --> 00:20:13.669 align:start position:0% part of how we get better guarantees from<00:20:11.480> this<00:20:11.799> mechanism<00:20:12.799> um<00:20:12.960> how<00:20:13.080> do<00:20:13.240> we<00:20:13.360> do<00:20:13.480> so 00:20:13.669 --> 00:20:13.679 align:start position:0% from this mechanism um how do we do so 00:20:13.679 --> 00:20:15.630 align:start position:0% from this mechanism um how do we do so is<00:20:13.880> probably<00:20:14.159> to<00:20:14.320> have<00:20:14.799> consolidation 00:20:15.630 --> 00:20:15.640 align:start position:0% is probably to have consolidation 00:20:15.640 --> 00:20:18.630 align:start position:0% is probably to have consolidation incentives<00:20:16.640> that<00:20:17.159> uh<00:20:17.320> essentially<00:20:18.200> go<00:20:18.440> down 00:20:18.630 --> 00:20:18.640 align:start position:0% incentives that uh essentially go down 00:20:18.640 --> 00:20:20.669 align:start position:0% incentives that uh essentially go down to<00:20:18.840> zero<00:20:19.400> once<00:20:19.640> we<00:20:19.799> reach<00:20:20.039> a<00:20:20.159> certain<00:20:20.480> amount 00:20:20.669 --> 00:20:20.679 align:start position:0% to zero once we reach a certain amount 00:20:20.679 --> 00:20:22.430 align:start position:0% to zero once we reach a certain amount of<00:20:20.840> consolidation<00:20:21.400> that<00:20:21.559> we're<00:20:21.799> okay<00:20:22.000> with<00:20:22.240> so 00:20:22.430 --> 00:20:22.440 align:start position:0% of consolidation that we're okay with so 00:20:22.440 --> 00:20:25.029 align:start position:0% of consolidation that we're okay with so maybe<00:20:22.840> you<00:20:22.919> know<00:20:23.039> 75%<00:20:23.960> or<00:20:24.240> some<00:20:24.440> other<00:20:24.720> amount 00:20:25.029 --> 00:20:25.039 align:start position:0% maybe you know 75% or some other amount 00:20:25.039 --> 00:20:27.430 align:start position:0% maybe you know 75% or some other amount that<00:20:25.200> that<00:20:25.280> we're<00:20:25.480> happy<00:20:25.760> with<00:20:26.559> and<00:20:26.919> uh<00:20:27.120> yeah 00:20:27.430 --> 00:20:27.440 align:start position:0% that that we're happy with and uh yeah 00:20:27.440 --> 00:20:30.149 align:start position:0% that that we're happy with and uh yeah when<00:20:27.600> we're<00:20:27.880> outside<00:20:28.200> of<00:20:28.320> this<00:20:28.880> uh<00:20:29.039> regime<00:20:29.880> you 00:20:30.149 --> 00:20:30.159 align:start position:0% when we're outside of this uh regime you 00:20:30.159 --> 00:20:31.870 align:start position:0% when we're outside of this uh regime you have<00:20:30.440> basically<00:20:30.720> this<00:20:30.919> incentive<00:20:31.600> if<00:20:31.720> you're 00:20:31.870 --> 00:20:31.880 align:start position:0% have basically this incentive if you're 00:20:31.880 --> 00:20:34.549 align:start position:0% have basically this incentive if you're a<00:20:32.039> saking<00:20:32.400> pool<00:20:32.679> or<00:20:32.919> so<00:20:33.080> on<00:20:33.320> to 00:20:34.549 --> 00:20:34.559 align:start position:0% a saking pool or so on to 00:20:34.559 --> 00:20:36.669 align:start position:0% a saking pool or so on to consolidate<00:20:35.559> and<00:20:35.919> yeah<00:20:36.080> what's<00:20:36.280> left 00:20:36.669 --> 00:20:36.679 align:start position:0% consolidate and yeah what's left 00:20:36.679 --> 00:20:38.190 align:start position:0% consolidate and yeah what's left essentially<00:20:37.080> for<00:20:37.240> the<00:20:37.400> consensus<00:20:37.799> protocol 00:20:38.190 --> 00:20:38.200 align:start position:0% essentially for the consensus protocol 00:20:38.200 --> 00:20:40.270 align:start position:0% essentially for the consensus protocol part<00:20:38.440> we<00:20:38.559> have<00:20:38.720> to<00:20:38.840> spec<00:20:39.159> it<00:20:39.280> and<00:20:39.440> prototype<00:20:39.880> it 00:20:40.270 --> 00:20:40.280 align:start position:0% part we have to spec it and prototype it 00:20:40.280 --> 00:20:42.230 align:start position:0% part we have to spec it and prototype it for<00:20:40.480> the<00:20:40.640> rest<00:20:41.039> a<00:20:41.120> lot<00:20:41.240> of<00:20:41.360> it<00:20:41.520> is<00:20:41.760> really<00:20:42.000> like 00:20:42.230 --> 00:20:42.240 align:start position:0% for the rest a lot of it is really like 00:20:42.240 --> 00:20:43.549 align:start position:0% for the rest a lot of it is really like having<00:20:42.480> these<00:20:42.640> hard<00:20:42.880> discussions<00:20:43.320> in<00:20:43.440> the 00:20:43.549 --> 00:20:43.559 align:start position:0% having these hard discussions in the 00:20:43.559 --> 00:20:45.669 align:start position:0% having these hard discussions in the community<00:20:44.039> around<00:20:44.640> the<00:20:44.760> future<00:20:45.000> of<00:20:45.159> staking 00:20:45.669 --> 00:20:45.679 align:start position:0% community around the future of staking 00:20:45.679 --> 00:20:47.669 align:start position:0% community around the future of staking and<00:20:45.840> you<00:20:45.960> know<00:20:46.280> what<00:20:46.440> of<00:20:46.600> these<00:20:46.760> trade-offs<00:20:47.559> uh 00:20:47.669 --> 00:20:47.679 align:start position:0% and you know what of these trade-offs uh 00:20:47.679 --> 00:20:50.430 align:start position:0% and you know what of these trade-offs uh we're<00:20:47.919> happy<00:20:48.240> with<00:20:49.000> um<00:20:49.520> decide<00:20:49.960> what<00:20:50.120> the<00:20:50.320> what 00:20:50.430 --> 00:20:50.440 align:start position:0% we're happy with um decide what the what 00:20:50.440 --> 00:20:52.430 align:start position:0% we're happy with um decide what the what what<00:20:50.559> failure<00:20:50.919> case<00:20:51.159> we're<00:20:51.400> happy<00:20:51.720> with<00:20:52.280> and 00:20:52.430 --> 00:20:52.440 align:start position:0% what failure case we're happy with and 00:20:52.440 --> 00:20:54.310 align:start position:0% what failure case we're happy with and then<00:20:52.840> yeah<00:20:53.240> we<00:20:53.360> could<00:20:53.520> introduce<00:20:53.960> orbit 00:20:54.310 --> 00:20:54.320 align:start position:0% then yeah we could introduce orbit 00:20:54.320 --> 00:20:56.390 align:start position:0% then yeah we could introduce orbit sampling<00:20:54.640> in<00:20:54.720> the<00:20:54.840> current<00:20:55.120> protocol<00:20:56.120> uh<00:20:56.280> and 00:20:56.390 --> 00:20:56.400 align:start position:0% sampling in the current protocol uh and 00:20:56.400 --> 00:20:58.029 align:start position:0% sampling in the current protocol uh and then<00:20:56.559> we<00:20:56.679> could<00:20:56.840> eventually<00:20:57.559> uh<00:20:57.679> move 00:20:58.029 --> 00:20:58.039 align:start position:0% then we could eventually uh move 00:20:58.039 --> 00:21:00.510 align:start position:0% then we could eventually uh move actually<00:20:58.280> to<00:20:58.760> to<00:20:59.080> 3sf<00:20:59.760> or<00:21:00.000> you<00:21:00.080> know<00:21:00.200> to<00:21:00.360> some 00:21:00.510 --> 00:21:00.520 align:start position:0% actually to to 3sf or you know to some 00:21:00.520 --> 00:21:04.510 align:start position:0% actually to to 3sf or you know to some faster<00:21:00.840> finality<00:21:01.640> protocol<00:21:02.640> thank 00:21:04.510 --> 00:21:04.520 align:start position:0% faster finality protocol thank 00:21:04.520 --> 00:21:08.830 align:start position:0% faster finality protocol thank you<00:21:05.520> okay<00:21:06.360> okay<00:21:07.360> I'm<00:21:07.480> going<00:21:07.600> to<00:21:08.120> shuffle<00:21:08.600> you 00:21:08.830 --> 00:21:08.840 align:start position:0% you okay okay I'm going to shuffle you 00:21:08.840 --> 00:21:10.990 align:start position:0% you okay okay I'm going to shuffle you along<00:21:09.280> towards<00:21:09.600> the<00:21:09.720> center<00:21:10.080> so<00:21:10.320> everyone<00:21:10.799> can 00:21:10.990 --> 00:21:11.000 align:start position:0% along towards the center so everyone can 00:21:11.000 --> 00:21:13.310 align:start position:0% along towards the center so everyone can look<00:21:11.159> at<00:21:11.320> your<00:21:11.520> beautiful<00:21:12.039> face<00:21:12.799> um<00:21:12.960> thank<00:21:13.120> you 00:21:13.310 --> 00:21:13.320 align:start position:0% look at your beautiful face um thank you 00:21:13.320 --> 00:21:16.510 align:start position:0% look at your beautiful face um thank you guys<00:21:13.520> again<00:21:14.000> give<00:21:14.200> another<00:21:14.440> round<00:21:14.720> for 00:21:16.510 --> 00:21:16.520 align:start position:0% guys again give another round for 00:21:16.520 --> 00:21:19.029 align:start position:0% guys again give another round for Franchesco<00:21:17.520> perfect<00:21:18.000> so<00:21:18.159> let's<00:21:18.440> dive<00:21:18.760> into 00:21:19.029 --> 00:21:19.039 align:start position:0% Franchesco perfect so let's dive into 00:21:19.039 --> 00:21:20.830 align:start position:0% Franchesco perfect so let's dive into the<00:21:19.240> question<00:21:19.600> starting<00:21:19.880> from<00:21:20.039> the<00:21:20.240> top 00:21:20.830 --> 00:21:20.840 align:start position:0% the question starting from the top 00:21:20.840 --> 00:21:22.669 align:start position:0% the question starting from the top Avalanche<00:21:21.360> already<00:21:21.760> has<00:21:21.960> single<00:21:22.320> block 00:21:22.669 --> 00:21:22.679 align:start position:0% Avalanche already has single block 00:21:22.679 --> 00:21:24.909 align:start position:0% Avalanche already has single block finality<00:21:23.279> with<00:21:23.440> subsec<00:21:24.039> block<00:21:24.360> times<00:21:24.720> where 00:21:24.909 --> 00:21:24.919 align:start position:0% finality with subsec block times where 00:21:24.919 --> 00:21:27.230 align:start position:0% finality with subsec block times where every<00:21:25.200> validator<00:21:25.720> votes<00:21:26.039> on<00:21:26.279> every<00:21:26.520> block 00:21:27.230 --> 00:21:27.240 align:start position:0% every validator votes on every block 00:21:27.240 --> 00:21:28.830 align:start position:0% every validator votes on every block does<00:21:27.440> this<00:21:27.640> proposed<00:21:28.039> system<00:21:28.360> have<00:21:28.679> any 00:21:28.830 --> 00:21:28.840 align:start position:0% does this proposed system have any 00:21:28.840 --> 00:21:30.990 align:start position:0% does this proposed system have any Competitive<00:21:29.360> Edge<00:21:29.720> against<00:21:30.039> Avalanche 00:21:30.990 --> 00:21:31.000 align:start position:0% Competitive Edge against Avalanche 00:21:31.000 --> 00:21:33.190 align:start position:0% Competitive Edge against Avalanche consensus<00:21:32.000> yeah<00:21:32.120> so<00:21:32.279> to<00:21:32.400> my<00:21:32.559> knowledge<00:21:32.960> and<00:21:33.120> I 00:21:33.190 --> 00:21:33.200 align:start position:0% consensus yeah so to my knowledge and I 00:21:33.200 --> 00:21:35.070 align:start position:0% consensus yeah so to my knowledge and I mean<00:21:33.440> it<00:21:33.559> might<00:21:33.720> be<00:21:33.880> outdated<00:21:34.360> but<00:21:34.600> I<00:21:34.799> don't 00:21:35.070 --> 00:21:35.080 align:start position:0% mean it might be outdated but I don't 00:21:35.080 --> 00:21:37.390 align:start position:0% mean it might be outdated but I don't think<00:21:35.240> so<00:21:36.120> um<00:21:36.279> avalanch<00:21:36.720> does<00:21:36.880> not<00:21:37.039> have<00:21:37.200> any 00:21:37.390 --> 00:21:37.400 align:start position:0% think so um avalanch does not have any 00:21:37.400 --> 00:21:39.070 align:start position:0% think so um avalanch does not have any accountable<00:21:37.880> safety<00:21:38.279> so<00:21:38.400> there's<00:21:38.600> no<00:21:38.760> way<00:21:38.919> to 00:21:39.070 --> 00:21:39.080 align:start position:0% accountable safety so there's no way to 00:21:39.080 --> 00:21:41.230 align:start position:0% accountable safety so there's no way to actually<00:21:39.840> say<00:21:40.240> if<00:21:40.400> there<00:21:40.520> is<00:21:40.640> a<00:21:40.760> consensus 00:21:41.230 --> 00:21:41.240 align:start position:0% actually say if there is a consensus 00:21:41.240 --> 00:21:43.070 align:start position:0% actually say if there is a consensus failure<00:21:42.240> for<00:21:42.360> example<00:21:42.600> let's<00:21:42.720> say<00:21:42.880> double 00:21:43.070 --> 00:21:43.080 align:start position:0% failure for example let's say double 00:21:43.080 --> 00:21:44.789 align:start position:0% failure for example let's say double finality<00:21:43.520> there's<00:21:43.679> no<00:21:43.840> way<00:21:43.960> to<00:21:44.080> say<00:21:44.640> which 00:21:44.789 --> 00:21:44.799 align:start position:0% finality there's no way to say which 00:21:44.799 --> 00:21:46.990 align:start position:0% finality there's no way to say which valers<00:21:45.360> exactly<00:21:45.679> were<00:21:45.880> responsible<00:21:46.360> for<00:21:46.559> it 00:21:46.990 --> 00:21:47.000 align:start position:0% valers exactly were responsible for it 00:21:47.000 --> 00:21:48.390 align:start position:0% valers exactly were responsible for it because<00:21:47.240> the<00:21:47.440> way<00:21:47.600> they<00:21:47.720> reach<00:21:47.919> consensus 00:21:48.390 --> 00:21:48.400 align:start position:0% because the way they reach consensus 00:21:48.400 --> 00:21:50.269 align:start position:0% because the way they reach consensus through<00:21:48.600> this<00:21:48.760> like<00:21:48.919> subsampling<00:21:49.640> mechanism 00:21:50.269 --> 00:21:50.279 align:start position:0% through this like subsampling mechanism 00:21:50.279 --> 00:21:52.390 align:start position:0% through this like subsampling mechanism that<00:21:50.400> doesn't<00:21:50.679> really<00:21:51.360> uh<00:21:51.520> get<00:21:51.760> everyone<00:21:52.159> to 00:21:52.390 --> 00:21:52.400 align:start position:0% that doesn't really uh get everyone to 00:21:52.400 --> 00:21:54.870 align:start position:0% that doesn't really uh get everyone to to<00:21:52.760> express<00:21:53.080> an<00:21:53.240> opinion<00:21:53.520> on<00:21:53.640> a 00:21:54.870 --> 00:21:54.880 align:start position:0% to express an opinion on a 00:21:54.880 --> 00:21:58.590 align:start position:0% to express an opinion on a block<00:21:55.880> okay<00:21:56.159> cool<00:21:56.760> next<00:21:57.080> does<00:21:57.279> 3sf<00:21:57.960> work<00:21:58.200> with 00:21:58.590 --> 00:21:58.600 align:start position:0% block okay cool next does 3sf work with 00:21:58.600 --> 00:22:01.870 align:start position:0% block okay cool next does 3sf work with lower<00:21:58.840> slot<00:21:59.200> times<00:22:00.120> so<00:22:00.559> 3sf<00:22:01.200> is<00:22:01.400> kind<00:22:01.520> of<00:22:01.640> built 00:22:01.870 --> 00:22:01.880 align:start position:0% lower slot times so 3sf is kind of built 00:22:01.880 --> 00:22:04.630 align:start position:0% lower slot times so 3sf is kind of built in<00:22:01.960> a<00:22:02.080> way<00:22:02.240> that<00:22:02.440> doesn't<00:22:02.799> really<00:22:03.400> change<00:22:04.120> the 00:22:04.630 --> 00:22:04.640 align:start position:0% in a way that doesn't really change the 00:22:04.640 --> 00:22:07.190 align:start position:0% in a way that doesn't really change the the<00:22:04.720> way<00:22:04.840> the<00:22:04.960> slot<00:22:05.320> Works<00:22:06.120> uh<00:22:06.240> too<00:22:06.440> much<00:22:07.039> so 00:22:07.190 --> 00:22:07.200 align:start position:0% the way the slot Works uh too much so 00:22:07.200 --> 00:22:09.230 align:start position:0% the way the slot Works uh too much so it's<00:22:07.480> it<00:22:07.600> would<00:22:07.760> be<00:22:07.919> a<00:22:08.080> slot<00:22:08.440> that<00:22:08.720> it<00:22:08.840> looks 00:22:09.230 --> 00:22:09.240 align:start position:0% it's it would be a slot that it looks 00:22:09.240 --> 00:22:11.830 align:start position:0% it's it would be a slot that it looks quite<00:22:09.440> similar<00:22:09.799> to<00:22:09.960> today<00:22:10.799> there's<00:22:11.039> some<00:22:11.360> like 00:22:11.830 --> 00:22:11.840 align:start position:0% quite similar to today there's some like 00:22:11.840 --> 00:22:13.430 align:start position:0% quite similar to today there's some like minor<00:22:12.320> things<00:22:12.679> that<00:22:12.799> that<00:22:12.919> I<00:22:13.000> didn't<00:22:13.240> talk 00:22:13.430 --> 00:22:13.440 align:start position:0% minor things that that I didn't talk 00:22:13.440 --> 00:22:15.630 align:start position:0% minor things that that I didn't talk about<00:22:13.799> that<00:22:14.039> kind<00:22:14.120> of<00:22:14.240> deviate<00:22:14.679> from<00:22:14.880> this<00:22:15.520> but 00:22:15.630 --> 00:22:15.640 align:start position:0% about that kind of deviate from this but 00:22:15.640 --> 00:22:17.830 align:start position:0% about that kind of deviate from this but generally<00:22:16.000> speaking<00:22:17.000> most<00:22:17.200> of<00:22:17.400> what<00:22:17.520> we<00:22:17.679> could 00:22:17.830 --> 00:22:17.840 align:start position:0% generally speaking most of what we could 00:22:17.840 --> 00:22:19.630 align:start position:0% generally speaking most of what we could do<00:22:18.080> with<00:22:18.240> today's<00:22:18.679> slot<00:22:19.080> we<00:22:19.159> would<00:22:19.360> also<00:22:19.520> be 00:22:19.630 --> 00:22:19.640 align:start position:0% do with today's slot we would also be 00:22:19.640 --> 00:22:23.710 align:start position:0% do with today's slot we would also be able<00:22:19.840> to<00:22:19.960> do<00:22:20.159> with<00:22:20.279> 3sf<00:22:20.960> I<00:22:21.039> would<00:22:21.679> say<00:22:22.679> cool<00:22:23.600> it 00:22:23.710 --> 00:22:23.720 align:start position:0% able to do with 3sf I would say cool it 00:22:23.720 --> 00:22:25.990 align:start position:0% able to do with 3sf I would say cool it seems<00:22:24.039> three<00:22:24.320> slot<00:22:24.600> finality<00:22:25.279> provides<00:22:25.760> both 00:22:25.990 --> 00:22:26.000 align:start position:0% seems three slot finality provides both 00:22:26.000 --> 00:22:28.190 align:start position:0% seems three slot finality provides both constant<00:22:26.440> time<00:22:26.679> finality<00:22:27.279> and<00:22:27.480> liveness<00:22:28.080> what 00:22:28.190 --> 00:22:28.200 align:start position:0% constant time finality and liveness what 00:22:28.200 --> 00:22:30.830 align:start position:0% constant time finality and liveness what hypo<00:22:28.520> hypothesis<00:22:28.960> do<00:22:29.080> you<00:22:29.240> make<00:22:29.400> to<00:22:29.600> guarantee 00:22:30.830 --> 00:22:30.840 align:start position:0% hypo hypothesis do you make to guarantee 00:22:30.840 --> 00:22:34.190 align:start position:0% hypo hypothesis do you make to guarantee both<00:22:31.840> um 00:22:34.190 --> 00:22:34.200 align:start position:0% both um 00:22:34.200 --> 00:22:39.230 align:start position:0% both um so<00:22:35.200> I'm<00:22:35.320> not<00:22:35.640> entirely<00:22:36.120> sure<00:22:37.400> um<00:22:38.400> what<00:22:38.640> exactly 00:22:39.230 --> 00:22:39.240 align:start position:0% so I'm not entirely sure um what exactly 00:22:39.240 --> 00:22:41.549 align:start position:0% so I'm not entirely sure um what exactly the<00:22:40.240> yeah<00:22:40.600> I'm<00:22:40.679> not<00:22:40.799> entirely<00:22:41.080> sure<00:22:41.279> but<00:22:41.400> let's 00:22:41.549 --> 00:22:41.559 align:start position:0% the yeah I'm not entirely sure but let's 00:22:41.559 --> 00:22:43.310 align:start position:0% the yeah I'm not entirely sure but let's say<00:22:41.799> like 00:22:43.310 --> 00:22:43.320 align:start position:0% say like 00:22:43.320 --> 00:22:46.430 align:start position:0% say like um<00:22:44.320> the<00:22:44.679> if<00:22:45.000> by<00:22:45.120> liveness<00:22:45.520> you<00:22:45.640> mean 00:22:46.430 --> 00:22:46.440 align:start position:0% um the if by liveness you mean 00:22:46.440 --> 00:22:48.710 align:start position:0% um the if by liveness you mean availability<00:22:47.200> more<00:22:47.440> specifically<00:22:48.400> then<00:22:48.600> this 00:22:48.710 --> 00:22:48.720 align:start position:0% availability more specifically then this 00:22:48.720 --> 00:22:50.390 align:start position:0% availability more specifically then this is<00:22:48.880> something<00:22:49.200> that<00:22:49.320> relates<00:22:49.679> to<00:22:49.799> this<00:22:49.960> lmd 00:22:50.390 --> 00:22:50.400 align:start position:0% is something that relates to this lmd 00:22:50.400 --> 00:22:52.909 align:start position:0% is something that relates to this lmd Ghost<00:22:50.640> part<00:22:50.760> of<00:22:50.880> the<00:22:51.080> protocol<00:22:52.080> um<00:22:52.320> and<00:22:52.720> yeah 00:22:52.909 --> 00:22:52.919 align:start position:0% Ghost part of the protocol um and yeah 00:22:52.919 --> 00:22:54.789 align:start position:0% Ghost part of the protocol um and yeah it's<00:22:53.520> it's<00:22:53.720> possible<00:22:54.039> to<00:22:54.200> have<00:22:54.360> both<00:22:54.520> of<00:22:54.640> them 00:22:54.789 --> 00:22:54.799 align:start position:0% it's it's possible to have both of them 00:22:54.799 --> 00:22:56.149 align:start position:0% it's it's possible to have both of them finality<00:22:55.240> and<00:22:55.360> availability<00:22:55.880> because<00:22:56.039> we 00:22:56.149 --> 00:22:56.159 align:start position:0% finality and availability because we 00:22:56.159 --> 00:22:58.789 align:start position:0% finality and availability because we have<00:22:56.360> these<00:22:56.559> two<00:22:56.840> different<00:22:57.760> uh<00:22:57.919> kind<00:22:58.080> of 00:22:58.789 --> 00:22:58.799 align:start position:0% have these two different uh kind of 00:22:58.799 --> 00:23:00.029 align:start position:0% have these two different uh kind of chains<00:22:59.159> in<00:22:59.279> a<00:22:59.400> way<00:22:59.600> we<00:22:59.679> have<00:22:59.799> like<00:22:59.960> the 00:23:00.029 --> 00:23:00.039 align:start position:0% chains in a way we have like the 00:23:00.039 --> 00:23:02.070 align:start position:0% chains in a way we have like the available<00:23:00.400> chain<00:23:00.640> and<00:23:00.760> then<00:23:00.960> finality<00:23:01.400> on<00:23:01.600> top 00:23:02.070 --> 00:23:02.080 align:start position:0% available chain and then finality on top 00:23:02.080 --> 00:23:02.830 align:start position:0% available chain and then finality on top otherwise<00:23:02.440> there<00:23:02.520> would<00:23:02.640> be<00:23:02.720> an 00:23:02.830 --> 00:23:02.840 align:start position:0% otherwise there would be an 00:23:02.840 --> 00:23:04.430 align:start position:0% otherwise there would be an impossibility<00:23:03.400> result<00:23:03.880> maybe<00:23:04.080> you<00:23:04.240> mean 00:23:04.430 --> 00:23:04.440 align:start position:0% impossibility result maybe you mean 00:23:04.440 --> 00:23:05.990 align:start position:0% impossibility result maybe you mean something<00:23:04.720> else<00:23:05.080> in<00:23:05.279> which<00:23:05.480> case<00:23:05.720> maybe<00:23:05.880> we 00:23:05.990 --> 00:23:06.000 align:start position:0% something else in which case maybe we 00:23:06.000 --> 00:23:07.350 align:start position:0% something else in which case maybe we can<00:23:06.120> chat<00:23:06.320> about<00:23:06.520> it 00:23:07.350 --> 00:23:07.360 align:start position:0% can chat about it 00:23:07.360 --> 00:23:11.190 align:start position:0% can chat about it later<00:23:08.360> cool<00:23:09.080> does<00:23:09.400> Orbit<00:23:09.799> changes<00:23:10.679> um<00:23:10.919> how 00:23:11.190 --> 00:23:11.200 align:start position:0% later cool does Orbit changes um how 00:23:11.200 --> 00:23:13.269 align:start position:0% later cool does Orbit changes um how aggregators<00:23:11.919> are<00:23:12.120> sampled<00:23:12.600> from<00:23:12.760> the<00:23:12.880> beacon 00:23:13.269 --> 00:23:13.279 align:start position:0% aggregators are sampled from the beacon 00:23:13.279 --> 00:23:14.350 align:start position:0% aggregators are sampled from the beacon ATT<00:23:13.440> tester 00:23:14.350 --> 00:23:14.360 align:start position:0% ATT tester 00:23:14.360 --> 00:23:17.549 align:start position:0% ATT tester sets<00:23:15.360> um<00:23:16.120> no<00:23:16.360> most<00:23:16.600> likely<00:23:16.919> wouldn't<00:23:17.360> I<00:23:17.440> would 00:23:17.549 --> 00:23:17.559 align:start position:0% sets um no most likely wouldn't I would 00:23:17.559 --> 00:23:19.870 align:start position:0% sets um no most likely wouldn't I would say<00:23:17.840> yeah<00:23:18.039> we<00:23:18.120> could<00:23:18.279> just<00:23:18.960> one<00:23:19.240> way<00:23:19.559> to<00:23:19.679> do 00:23:19.870 --> 00:23:19.880 align:start position:0% say yeah we could just one way to do 00:23:19.880 --> 00:23:21.350 align:start position:0% say yeah we could just one way to do this<00:23:20.159> is<00:23:20.279> that<00:23:20.440> we<00:23:20.520> could<00:23:20.679> just<00:23:20.799> reuse<00:23:21.159> all<00:23:21.279> of 00:23:21.350 --> 00:23:21.360 align:start position:0% this is that we could just reuse all of 00:23:21.360 --> 00:23:22.750 align:start position:0% this is that we could just reuse all of the<00:23:21.480> aggregation<00:23:21.960> infrastructure<00:23:22.520> that<00:23:22.640> we 00:23:22.750 --> 00:23:22.760 align:start position:0% the aggregation infrastructure that we 00:23:22.760 --> 00:23:24.470 align:start position:0% the aggregation infrastructure that we have<00:23:22.919> now<00:23:23.159> including<00:23:23.640> the<00:23:23.799> way<00:23:24.000> the<00:23:24.120> specific 00:23:24.470 --> 00:23:24.480 align:start position:0% have now including the way the specific 00:23:24.480 --> 00:23:26.190 align:start position:0% have now including the way the specific way<00:23:24.640> the<00:23:24.760> aggregators<00:23:25.200> are 00:23:26.190 --> 00:23:26.200 align:start position:0% way the aggregators are 00:23:26.200 --> 00:23:28.669 align:start position:0% way the aggregators are selected<00:23:27.200> the<00:23:27.360> majority<00:23:27.760> of<00:23:27.919> homes<00:23:28.200> take 00:23:28.669 --> 00:23:28.679 align:start position:0% selected the majority of homes take 00:23:28.679 --> 00:23:30.669 align:start position:0% selected the majority of homes take reward<00:23:29.120> actually<00:23:29.440> from<00:23:29.640> the<00:23:29.799> attestation 00:23:30.669 --> 00:23:30.679 align:start position:0% reward actually from the attestation 00:23:30.679 --> 00:23:32.590 align:start position:0% reward actually from the attestation does<00:23:30.880> this<00:23:31.120> change 00:23:32.590 --> 00:23:32.600 align:start position:0% does this change 00:23:32.600 --> 00:23:35.029 align:start position:0% does this change would<00:23:33.600> I'm<00:23:33.760> not<00:23:33.960> speaking<00:23:34.320> English<00:23:34.600> correctly 00:23:35.029 --> 00:23:35.039 align:start position:0% would I'm not speaking English correctly 00:23:35.039 --> 00:23:37.630 align:start position:0% would I'm not speaking English correctly does<00:23:35.240> this<00:23:35.400> change<00:23:35.919> would<00:23:36.919> this<00:23:37.159> change<00:23:37.480> would 00:23:37.630 --> 00:23:37.640 align:start position:0% does this change would this change would 00:23:37.640 --> 00:23:40.029 align:start position:0% does this change would this change would make<00:23:37.840> home<00:23:38.120> Saker<00:23:38.520> suffer<00:23:38.840> by<00:23:39.000> a<00:23:39.159> lot<00:23:39.679> and<00:23:39.840> just 00:23:40.029 --> 00:23:40.039 align:start position:0% make home Saker suffer by a lot and just 00:23:40.039 --> 00:23:41.909 align:start position:0% make home Saker suffer by a lot and just withdrawn<00:23:40.559> being<00:23:40.760> a<00:23:40.880> home<00:23:41.159> steaker<00:23:41.520> and<00:23:41.640> go<00:23:41.760> to 00:23:41.909 --> 00:23:41.919 align:start position:0% withdrawn being a home steaker and go to 00:23:41.919 --> 00:23:44.350 align:start position:0% withdrawn being a home steaker and go to liquid<00:23:42.200> staking<00:23:42.640> or<00:23:42.799> something<00:23:43.240> s<00:23:43.840> oh<00:23:44.080> okay<00:23:44.200> no 00:23:44.350 --> 00:23:44.360 align:start position:0% liquid staking or something s oh okay no 00:23:44.360 --> 00:23:46.990 align:start position:0% liquid staking or something s oh okay no it's<00:23:44.559> not<00:23:44.720> me<00:23:44.960> it's 00:23:46.990 --> 00:23:47.000 align:start position:0% it's not me it's 00:23:47.000 --> 00:23:49.630 align:start position:0% it's not me it's question<00:23:48.000> uh<00:23:48.120> so<00:23:48.279> no<00:23:48.520> like<00:23:49.120> the<00:23:49.240> answer<00:23:49.440> is 00:23:49.630 --> 00:23:49.640 align:start position:0% question uh so no like the answer is 00:23:49.640 --> 00:23:53.390 align:start position:0% question uh so no like the answer is like<00:23:50.320> um<00:23:51.320> the<00:23:51.600> rewards<00:23:52.320> would<00:23:52.640> actually<00:23:52.960> be<00:23:53.200> um 00:23:53.390 --> 00:23:53.400 align:start position:0% like um the rewards would actually be um 00:23:53.400 --> 00:23:55.149 align:start position:0% like um the rewards would actually be um the<00:23:53.520> expected<00:23:53.960> rewards<00:23:54.640> but<00:23:54.760> when<00:23:54.880> we<00:23:55.000> talk 00:23:55.149 --> 00:23:55.159 align:start position:0% the expected rewards but when we talk 00:23:55.159 --> 00:23:56.789 align:start position:0% the expected rewards but when we talk about<00:23:55.320> attestations<00:23:56.039> expected<00:23:56.360> rewards<00:23:56.679> and 00:23:56.789 --> 00:23:56.799 align:start position:0% about attestations expected rewards and 00:23:56.799 --> 00:23:58.110 align:start position:0% about attestations expected rewards and rewards<00:23:57.080> are<00:23:57.240> kind<00:23:57.360> of<00:23:57.520> the<00:23:57.640> same<00:23:57.919> because 00:23:58.110 --> 00:23:58.120 align:start position:0% rewards are kind of the same because 00:23:58.120 --> 00:23:59.750 align:start position:0% rewards are kind of the same because your<00:23:58.440> test<00:23:58.640> so<00:23:58.799> frequently<00:23:59.279> like<00:23:59.400> even<00:23:59.600> with 00:23:59.750 --> 00:23:59.760 align:start position:0% your test so frequently like even with 00:23:59.760 --> 00:24:01.430 align:start position:0% your test so frequently like even with orbit<00:24:00.080> you<00:24:00.200> still<00:24:00.400> be<00:24:00.640> testing<00:24:01.039> once<00:24:01.240> every 00:24:01.430 --> 00:24:01.440 align:start position:0% orbit you still be testing once every 00:24:01.440 --> 00:24:03.710 align:start position:0% orbit you still be testing once every two<00:24:01.679> Appo<00:24:02.679> um<00:24:02.919> yeah<00:24:03.039> you<00:24:03.279> you<00:24:03.360> would<00:24:03.520> not 00:24:03.710 --> 00:24:03.720 align:start position:0% two Appo um yeah you you would not 00:24:03.720 --> 00:24:05.310 align:start position:0% two Appo um yeah you you would not suffer<00:24:04.159> because<00:24:04.360> of<00:24:04.520> that<00:24:04.799> because<00:24:05.159> the 00:24:05.310 --> 00:24:05.320 align:start position:0% suffer because of that because the 00:24:05.320 --> 00:24:06.830 align:start position:0% suffer because of that because the expected<00:24:05.679> rewards<00:24:05.960> are<00:24:06.120> still<00:24:06.440> proportional 00:24:06.830 --> 00:24:06.840 align:start position:0% expected rewards are still proportional 00:24:06.840 --> 00:24:10.230 align:start position:0% expected rewards are still proportional to<00:24:07.000> stake<00:24:07.640> so<00:24:08.640> whether<00:24:08.840> you<00:24:08.960> stake<00:24:09.360> 32<00:24:09.880> e 00:24:10.230 --> 00:24:10.240 align:start position:0% to stake so whether you stake 32 e 00:24:10.240 --> 00:24:12.350 align:start position:0% to stake so whether you stake 32 e whether<00:24:10.400> you<00:24:10.520> stake<00:24:10.760> 64<00:24:11.200> e<00:24:11.480> in<00:24:11.640> one<00:24:11.799> validator 00:24:12.350 --> 00:24:12.360 align:start position:0% whether you stake 64 e in one validator 00:24:12.360 --> 00:24:14.310 align:start position:0% whether you stake 64 e in one validator or<00:24:12.480> you<00:24:12.600> have<00:24:12.760> two<00:24:12.919> validators<00:24:13.440> of<00:24:13.559> 32<00:24:13.960> eth 00:24:14.310 --> 00:24:14.320 align:start position:0% or you have two validators of 32 eth 00:24:14.320 --> 00:24:16.029 align:start position:0% or you have two validators of 32 eth your<00:24:14.559> expected<00:24:14.880> rewards<00:24:15.159> are<00:24:15.360> the<00:24:15.440> same<00:24:15.919> you 00:24:16.029 --> 00:24:16.039 align:start position:0% your expected rewards are the same you 00:24:16.039 --> 00:24:17.350 align:start position:0% your expected rewards are the same you might<00:24:16.200> have<00:24:16.320> a<00:24:16.400> little<00:24:16.559> bit<00:24:16.720> more<00:24:16.880> variance 00:24:17.350 --> 00:24:17.360 align:start position:0% might have a little bit more variance 00:24:17.360 --> 00:24:18.909 align:start position:0% might have a little bit more variance but<00:24:17.600> it's<00:24:17.840> attestations<00:24:18.400> that<00:24:18.480> we're<00:24:18.679> talking 00:24:18.909 --> 00:24:18.919 align:start position:0% but it's attestations that we're talking 00:24:18.919 --> 00:24:20.350 align:start position:0% but it's attestations that we're talking about<00:24:19.159> you<00:24:19.320> attest<00:24:19.640> so<00:24:19.799> often<00:24:20.080> then<00:24:20.240> the 00:24:20.350 --> 00:24:20.360 align:start position:0% about you attest so often then the 00:24:20.360 --> 00:24:23.789 align:start position:0% about you attest so often then the variance<00:24:20.720> is<00:24:20.880> essentially 00:24:23.789 --> 00:24:23.799 align:start position:0% 00:24:23.799 --> 00:24:27.110 align:start position:0% irrelevant<00:24:24.799> cool<00:24:25.360> okay<00:24:26.159> uh<00:24:26.480> would<00:24:26.720> this 00:24:27.110 --> 00:24:27.120 align:start position:0% irrelevant cool okay uh would this 00:24:27.120 --> 00:24:29.990 align:start position:0% irrelevant cool okay uh would this change<00:24:27.559> the<00:24:27.720> staking<00:24:28.120> AP<00:24:28.440> PR<00:24:29.279> uh<00:24:29.399> as<00:24:29.559> not<00:24:29.760> all 00:24:29.990 --> 00:24:30.000 align:start position:0% change the staking AP PR uh as not all 00:24:30.000 --> 00:24:31.909 align:start position:0% change the staking AP PR uh as not all validators<00:24:30.480> are<00:24:30.679> testing<00:24:31.039> anymore<00:24:31.559> only<00:24:31.760> the 00:24:31.909 --> 00:24:31.919 align:start position:0% validators are testing anymore only the 00:24:31.919 --> 00:24:34.350 align:start position:0% validators are testing anymore only the selected<00:24:32.320> set<00:24:33.080> um<00:24:33.520> same<00:24:33.720> kind<00:24:33.840> of<00:24:34.000> answer<00:24:34.200> as 00:24:34.350 --> 00:24:34.360 align:start position:0% selected set um same kind of answer as 00:24:34.360 --> 00:24:36.190 align:start position:0% selected set um same kind of answer as before<00:24:34.640> like<00:24:34.919> it<00:24:35.039> wouldn't<00:24:35.520> like<00:24:35.799> when<00:24:36.000> you're 00:24:36.190 --> 00:24:36.200 align:start position:0% before like it wouldn't like when you're 00:24:36.200 --> 00:24:38.750 align:start position:0% before like it wouldn't like when you're not<00:24:36.440> in<00:24:36.600> the<00:24:36.720> set<00:24:37.039> you<00:24:37.159> don't<00:24:37.360> get<00:24:37.559> paid<00:24:38.320> but 00:24:38.750 --> 00:24:38.760 align:start position:0% not in the set you don't get paid but 00:24:38.760 --> 00:24:40.549 align:start position:0% not in the set you don't get paid but when<00:24:38.919> you're<00:24:39.120> in<00:24:39.240> the<00:24:39.399> set<00:24:39.840> you<00:24:40.000> get<00:24:40.200> paid<00:24:40.360> a 00:24:40.549 --> 00:24:40.559 align:start position:0% when you're in the set you get paid a 00:24:40.559 --> 00:24:42.950 align:start position:0% when you're in the set you get paid a constant<00:24:41.000> amount<00:24:41.600> so<00:24:42.039> whether<00:24:42.240> you<00:24:42.399> are<00:24:42.520> a 00:24:42.950 --> 00:24:42.960 align:start position:0% constant amount so whether you are a 00:24:42.960 --> 00:24:46.070 align:start position:0% constant amount so whether you are a 2,000<00:24:43.640> validator<00:24:44.120> or<00:24:44.360> a<00:24:44.520> 32<00:24:44.960> E<00:24:45.200> validator<00:24:45.919> when 00:24:46.070 --> 00:24:46.080 align:start position:0% 2,000 validator or a 32 E validator when 00:24:46.080 --> 00:24:47.510 align:start position:0% 2,000 validator or a 32 E validator when you're<00:24:46.200> in<00:24:46.320> the<00:24:46.440> set<00:24:46.640> you<00:24:46.760> get<00:24:46.880> paid<00:24:47.080> the<00:24:47.200> same 00:24:47.510 --> 00:24:47.520 align:start position:0% you're in the set you get paid the same 00:24:47.520 --> 00:24:49.110 align:start position:0% you're in the set you get paid the same so<00:24:47.640> you<00:24:47.720> can<00:24:47.880> think<00:24:48.039> about<00:24:48.200> it<00:24:48.320> as<00:24:48.520> like<00:24:48.919> once 00:24:49.110 --> 00:24:49.120 align:start position:0% so you can think about it as like once 00:24:49.120 --> 00:24:51.430 align:start position:0% so you can think about it as like once you're<00:24:49.399> in<00:24:49.799> you<00:24:49.960> get<00:24:50.120> paid<00:24:50.440> way<00:24:50.600> more<00:24:51.120> than<00:24:51.279> you 00:24:51.430 --> 00:24:51.440 align:start position:0% you're in you get paid way more than you 00:24:51.440 --> 00:24:52.909 align:start position:0% you're in you get paid way more than you should<00:24:51.960> like<00:24:52.120> based<00:24:52.360> on<00:24:52.440> your<00:24:52.559> stake<00:24:52.799> like 00:24:52.909 --> 00:24:52.919 align:start position:0% should like based on your stake like 00:24:52.919 --> 00:24:54.430 align:start position:0% should like based on your stake like you're<00:24:53.039> not<00:24:53.200> paid<00:24:53.440> proportionally<00:24:53.919> to<00:24:54.039> stake 00:24:54.430 --> 00:24:54.440 align:start position:0% you're not paid proportionally to stake 00:24:54.440 --> 00:24:56.470 align:start position:0% you're not paid proportionally to stake so<00:24:54.640> overall<00:24:55.000> the<00:24:55.120> two<00:24:55.240> things<00:24:55.480> balance<00:24:55.880> each 00:24:56.470 --> 00:24:56.480 align:start position:0% so overall the two things balance each 00:24:56.480 --> 00:24:59.669 align:start position:0% so overall the two things balance each other<00:24:57.480> okay<00:24:58.000> well<00:24:58.559> I<00:24:58.679> just<00:24:58.840> got<00:24:59.000> the<00:24:59.120> sign<00:24:59.440> so<00:24:59.600> I 00:24:59.669 --> 00:24:59.679 align:start position:0% other okay well I just got the sign so I 00:24:59.679 --> 00:25:01.310 align:start position:0% other okay well I just got the sign so I think<00:24:59.799> that's<00:24:59.960> all<00:25:00.120> the<00:25:00.240> time<00:25:00.360> we<00:25:00.480> have<00:25:00.600> today 00:25:01.310 --> 00:25:01.320 align:start position:0% think that's all the time we have today 00:25:01.320 --> 00:25:02.510 align:start position:0% think that's all the time we have today thank<00:25:01.440> you<00:25:01.559> so<00:25:01.679> much<00:25:01.840> Franchesco<00:25:02.320> thanks 00:25:02.510 --> 00:25:02.520 align:start position:0% thank you so much Franchesco thanks 00:25:02.520 --> 00:25:04.549 align:start position:0% thank you so much Franchesco thanks everyone<00:25:03.240> um<00:25:03.559> we<00:25:03.679> have<00:25:03.799> another<00:25:04.080> five<00:25:04.279> minute 00:25:04.549 --> 00:25:04.559 align:start position:0% everyone um we have another five minute 00:25:04.559 --> 00:25:08.389 align:start position:0% everyone um we have another five minute break<00:25:05.159> until<00:25:05.679> it's<00:25:05.960> actually<00:25:06.399> 410<00:25:07.039> this<00:25:07.399> time 00:25:08.389 --> 00:25:08.399 align:start position:0% break until it's actually 410 this time 00:25:08.399 --> 00:25:12.480 align:start position:0% break until it's actually 410 this time from<00:25:08.679> Pure<00:25:08.960> Das<00:25:09.440> to<00:25:09.600> full<00:25:09.799> dasas