WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.430 align:start position:0% [Music] 00:00:12.430 --> 00:00:12.440 align:start position:0% 00:00:12.440 --> 00:00:15.709 align:start position:0% we<00:00:13.440> work<00:00:13.559> on<00:00:13.740> the<00:00:13.920> lighthouse<00:00:14.219> client<00:00:14.599> so<00:00:15.599> we 00:00:15.709 --> 00:00:15.719 align:start position:0% we work on the lighthouse client so we 00:00:15.719 --> 00:00:17.029 align:start position:0% we work on the lighthouse client so we we're<00:00:16.020> going<00:00:16.139> to<00:00:16.199> be<00:00:16.199> talking<00:00:16.320> about<00:00:16.500> reducing 00:00:17.029 --> 00:00:17.039 align:start position:0% we're going to be talking about reducing 00:00:17.039 --> 00:00:18.830 align:start position:0% we're going to be talking about reducing Beacon<00:00:17.460> chain<00:00:17.580> bandwidth<00:00:18.119> for<00:00:18.300> institutional 00:00:18.830 --> 00:00:18.840 align:start position:0% Beacon chain bandwidth for institutional 00:00:18.840 --> 00:00:21.230 align:start position:0% Beacon chain bandwidth for institutional and<00:00:19.080> home<00:00:19.320> stakers<00:00:19.859> and<00:00:20.640> I'm<00:00:20.820> going<00:00:21.000> to<00:00:21.119> leave 00:00:21.230 --> 00:00:21.240 align:start position:0% and home stakers and I'm going to leave 00:00:21.240 --> 00:00:24.230 align:start position:0% and home stakers and I'm going to leave it<00:00:21.359> up<00:00:21.539> to<00:00:21.720> Diva<00:00:22.260> who's<00:00:22.439> a<00:00:22.800> Bogota<00:00:23.279> local<00:00:23.640> and 00:00:24.230 --> 00:00:24.240 align:start position:0% it up to Diva who's a Bogota local and 00:00:24.240 --> 00:00:26.750 align:start position:0% it up to Diva who's a Bogota local and our<00:00:24.480> peer-to-peer<00:00:25.080> Network<00:00:25.320> expert<00:00:25.920> to<00:00:26.460> kick 00:00:26.750 --> 00:00:26.760 align:start position:0% our peer-to-peer Network expert to kick 00:00:26.760 --> 00:00:29.509 align:start position:0% our peer-to-peer Network expert to kick us<00:00:26.939> off<00:00:27.119> okay<00:00:27.539> so<00:00:27.840> first<00:00:28.380> thing<00:00:28.680> that<00:00:29.039> we<00:00:29.279> need 00:00:29.509 --> 00:00:29.519 align:start position:0% us off okay so first thing that we need 00:00:29.519 --> 00:00:31.730 align:start position:0% us off okay so first thing that we need to<00:00:29.760> check<00:00:30.000> in<00:00:30.420> order<00:00:30.539> to<00:00:30.779> analyze<00:00:31.320> how<00:00:31.619> to 00:00:31.730 --> 00:00:31.740 align:start position:0% to check in order to analyze how to 00:00:31.740 --> 00:00:34.069 align:start position:0% to check in order to analyze how to reduce<00:00:31.859> bandwidth<00:00:32.579> for<00:00:32.840> institutional<00:00:33.840> and 00:00:34.069 --> 00:00:34.079 align:start position:0% reduce bandwidth for institutional and 00:00:34.079 --> 00:00:37.010 align:start position:0% reduce bandwidth for institutional and homesteakers<00:00:34.739> is<00:00:35.160> how<00:00:36.059> does<00:00:36.360> the<00:00:36.600> what<00:00:36.899> does 00:00:37.010 --> 00:00:37.020 align:start position:0% homesteakers is how does the what does 00:00:37.020 --> 00:00:39.590 align:start position:0% homesteakers is how does the what does the<00:00:37.140> bandwidth<00:00:37.739> look<00:00:38.040> like<00:00:38.160> right<00:00:38.640> now<00:00:38.820> we<00:00:39.480> are 00:00:39.590 --> 00:00:39.600 align:start position:0% the bandwidth look like right now we are 00:00:39.600 --> 00:00:41.209 align:start position:0% the bandwidth look like right now we are going<00:00:39.719> to<00:00:39.840> be<00:00:39.960> looking<00:00:40.200> at<00:00:40.680> data<00:00:41.100> from 00:00:41.209 --> 00:00:41.219 align:start position:0% going to be looking at data from 00:00:41.219 --> 00:00:44.630 align:start position:0% going to be looking at data from Lighthouse<00:00:41.640> like<00:00:42.540> age<00:00:42.840> said<00:00:43.280> we<00:00:44.280> work<00:00:44.460> on 00:00:44.630 --> 00:00:44.640 align:start position:0% Lighthouse like age said we work on 00:00:44.640 --> 00:00:46.010 align:start position:0% Lighthouse like age said we work on Lighthouse<00:00:45.000> is<00:00:45.239> one<00:00:45.480> of<00:00:45.540> the<00:00:45.719> production 00:00:46.010 --> 00:00:46.020 align:start position:0% Lighthouse is one of the production 00:00:46.020 --> 00:00:49.069 align:start position:0% Lighthouse is one of the production Beacon<00:00:46.500> notes<00:00:46.800> there<00:00:47.460> are<00:00:47.640> many<00:00:47.760> others<00:00:48.239> techu 00:00:49.069 --> 00:00:49.079 align:start position:0% Beacon notes there are many others techu 00:00:49.079 --> 00:00:52.069 align:start position:0% Beacon notes there are many others techu prism<00:00:49.520> Nimbus<00:00:50.520> low<00:00:50.940> star<00:00:51.180> we<00:00:51.600> are<00:00:51.719> the<00:00:51.960> second 00:00:52.069 --> 00:00:52.079 align:start position:0% prism Nimbus low star we are the second 00:00:52.079 --> 00:00:55.729 align:start position:0% prism Nimbus low star we are the second most<00:00:52.379> popular<00:00:52.620> one<00:00:53.059> and<00:00:54.059> while<00:00:54.480> the<00:00:55.379> data 00:00:55.729 --> 00:00:55.739 align:start position:0% most popular one and while the data 00:00:55.739 --> 00:00:57.049 align:start position:0% most popular one and while the data we're<00:00:55.860> going<00:00:56.100> to<00:00:56.160> be<00:00:56.280> looking<00:00:56.460> at<00:00:56.699> is 00:00:57.049 --> 00:00:57.059 align:start position:0% we're going to be looking at is 00:00:57.059 --> 00:00:59.330 align:start position:0% we're going to be looking at is lighthouse 00:00:59.330 --> 00:00:59.340 align:start position:0% lighthouse 00:00:59.340 --> 00:01:01.430 align:start position:0% lighthouse we<00:00:59.940> are<00:01:00.059> certain<00:01:00.239> that<00:01:00.600> this<00:01:00.780> applies<00:01:01.079> to<00:01:01.260> any 00:01:01.430 --> 00:01:01.440 align:start position:0% we are certain that this applies to any 00:01:01.440 --> 00:01:03.170 align:start position:0% we are certain that this applies to any other<00:01:01.620> client<00:01:01.860> across<00:01:02.340> the<00:01:02.399> network 00:01:03.170 --> 00:01:03.180 align:start position:0% other client across the network 00:01:03.180 --> 00:01:06.230 align:start position:0% other client across the network so<00:01:03.899> have<00:01:04.500> that<00:01:04.680> in<00:01:04.860> mind<00:01:04.979> first<00:01:05.880> thing<00:01:06.060> to 00:01:06.230 --> 00:01:06.240 align:start position:0% so have that in mind first thing to 00:01:06.240 --> 00:01:08.630 align:start position:0% so have that in mind first thing to notice<00:01:06.600> is<00:01:06.960> that<00:01:07.140> bandwidth<00:01:07.740> Associated<00:01:08.280> to<00:01:08.520> a 00:01:08.630 --> 00:01:08.640 align:start position:0% notice is that bandwidth Associated to a 00:01:08.640 --> 00:01:10.910 align:start position:0% notice is that bandwidth Associated to a beacon<00:01:08.939> node<00:01:09.180> is<00:01:09.560> proportional<00:01:10.560> to<00:01:10.740> the 00:01:10.910 --> 00:01:10.920 align:start position:0% beacon node is proportional to the 00:01:10.920 --> 00:01:12.830 align:start position:0% beacon node is proportional to the number<00:01:11.100> of<00:01:11.280> validators<00:01:11.880> is<00:01:12.180> how<00:01:12.360> it<00:01:12.659> has 00:01:12.830 --> 00:01:12.840 align:start position:0% number of validators is how it has 00:01:12.840 --> 00:01:14.570 align:start position:0% number of validators is how it has attached 00:01:14.570 --> 00:01:14.580 align:start position:0% attached 00:01:14.580 --> 00:01:17.090 align:start position:0% attached um<00:01:14.700> you<00:01:15.360> can<00:01:15.420> see<00:01:15.600> that<00:01:15.900> it<00:01:16.080> increases<00:01:16.619> when 00:01:17.090 --> 00:01:17.100 align:start position:0% um you can see that it increases when 00:01:17.100 --> 00:01:19.250 align:start position:0% um you can see that it increases when the<00:01:17.400> number<00:01:17.460> of<00:01:17.580> validators<00:01:18.060> goes<00:01:18.420> up<00:01:18.540> but 00:01:19.250 --> 00:01:19.260 align:start position:0% the number of validators goes up but 00:01:19.260 --> 00:01:22.390 align:start position:0% the number of validators goes up but then<00:01:19.500> at<00:01:20.100> 64<00:01:20.520> validators<00:01:21.060> it 00:01:22.390 --> 00:01:22.400 align:start position:0% then at 64 validators it 00:01:22.400 --> 00:01:25.310 align:start position:0% then at 64 validators it stays<00:01:23.400> more<00:01:23.640> or<00:01:23.700> less<00:01:23.759> the<00:01:24.000> same<00:01:24.180> 64<00:01:24.960> is<00:01:25.140> going 00:01:25.310 --> 00:01:25.320 align:start position:0% stays more or less the same 64 is going 00:01:25.320 --> 00:01:27.710 align:start position:0% stays more or less the same 64 is going to<00:01:25.439> be<00:01:25.560> a<00:01:25.740> really<00:01:25.920> important<00:01:26.340> number<00:01:26.939> in<00:01:27.600> this 00:01:27.710 --> 00:01:27.720 align:start position:0% to be a really important number in this 00:01:27.720 --> 00:01:30.370 align:start position:0% to be a really important number in this talk<00:01:27.960> H<00:01:28.740> is<00:01:28.979> going<00:01:29.220> to<00:01:29.340> explain 00:01:30.370 --> 00:01:30.380 align:start position:0% talk H is going to explain 00:01:30.380 --> 00:01:34.429 align:start position:0% talk H is going to explain further<00:01:31.380> why<00:01:32.340> and<00:01:33.060> why<00:01:33.240> it's<00:01:33.420> important 00:01:34.429 --> 00:01:34.439 align:start position:0% further why and why it's important 00:01:34.439 --> 00:01:38.210 align:start position:0% further why and why it's important so<00:01:35.100> yeah<00:01:35.400> we<00:01:36.060> need<00:01:36.180> to<00:01:36.360> remember<00:01:36.720> simply<00:01:37.320> that 00:01:38.210 --> 00:01:38.220 align:start position:0% so yeah we need to remember simply that 00:01:38.220 --> 00:01:41.030 align:start position:0% so yeah we need to remember simply that we<00:01:38.880> are<00:01:39.000> going<00:01:39.119> to<00:01:39.240> stop<00:01:39.420> at<00:01:39.659> 64<00:01:40.200> and<00:01:40.680> this<00:01:40.920> is 00:01:41.030 --> 00:01:41.040 align:start position:0% we are going to stop at 64 and this is 00:01:41.040 --> 00:01:42.830 align:start position:0% we are going to stop at 64 and this is where<00:01:41.280> bandwidth<00:01:41.759> is<00:01:41.880> going<00:01:42.060> to<00:01:42.180> be<00:01:42.540> more<00:01:42.720> or 00:01:42.830 --> 00:01:42.840 align:start position:0% where bandwidth is going to be more or 00:01:42.840 --> 00:01:45.530 align:start position:0% where bandwidth is going to be more or less<00:01:42.900> stable<00:01:43.680> now<00:01:44.220> if<00:01:44.460> we<00:01:44.640> look<00:01:44.759> at<00:01:45.180> how<00:01:45.420> many 00:01:45.530 --> 00:01:45.540 align:start position:0% less stable now if we look at how many 00:01:45.540 --> 00:01:49.130 align:start position:0% less stable now if we look at how many validators<00:01:46.140> does<00:01:46.939> every<00:01:47.939> Beacon<00:01:48.360> node<00:01:48.659> on<00:01:49.020> the 00:01:49.130 --> 00:01:49.140 align:start position:0% validators does every Beacon node on the 00:01:49.140 --> 00:01:50.210 align:start position:0% validators does every Beacon node on the network 00:01:50.210 --> 00:01:50.220 align:start position:0% network 00:01:50.220 --> 00:01:53.690 align:start position:0% network has<00:01:50.700> we're<00:01:51.659> going<00:01:51.899> to<00:01:52.079> have<00:01:52.259> like<00:01:52.560> main<00:01:53.040> three 00:01:53.690 --> 00:01:53.700 align:start position:0% has we're going to have like main three 00:01:53.700 --> 00:01:56.030 align:start position:0% has we're going to have like main three groups<00:01:54.180> we're<00:01:54.780> going<00:01:54.960> to<00:01:55.079> have<00:01:55.200> those<00:01:55.560> that 00:01:56.030 --> 00:01:56.040 align:start position:0% groups we're going to have those that 00:01:56.040 --> 00:01:57.710 align:start position:0% groups we're going to have those that don't<00:01:56.159> have<00:01:56.399> any<00:01:56.579> validator<00:01:57.060> attached<00:01:57.540> only 00:01:57.710 --> 00:01:57.720 align:start position:0% don't have any validator attached only 00:01:57.720 --> 00:02:00.770 align:start position:0% don't have any validator attached only simple<00:01:58.140> Beacon<00:01:58.680> notes<00:01:59.040> uh<00:01:59.939> notice<00:02:00.299> taking<00:02:00.479> big 00:02:00.770 --> 00:02:00.780 align:start position:0% simple Beacon notes uh notice taking big 00:02:00.780 --> 00:02:02.510 align:start position:0% simple Beacon notes uh notice taking big notes<00:02:01.140> now<00:02:01.380> we're<00:02:01.560> going<00:02:01.680> to<00:02:01.860> have<00:02:01.979> those<00:02:02.220> that 00:02:02.510 --> 00:02:02.520 align:start position:0% notes now we're going to have those that 00:02:02.520 --> 00:02:04.670 align:start position:0% notes now we're going to have those that we<00:02:02.640> are<00:02:02.759> going<00:02:02.880> to<00:02:03.000> come<00:02:03.119> homesteakers<00:02:03.899> which 00:02:04.670 --> 00:02:04.680 align:start position:0% we are going to come homesteakers which 00:02:04.680 --> 00:02:07.850 align:start position:0% we are going to come homesteakers which have<00:02:04.979> less<00:02:05.700> than<00:02:05.820> 10<00:02:06.060> validators<00:02:06.740> in<00:02:07.740> this 00:02:07.850 --> 00:02:07.860 align:start position:0% have less than 10 validators in this 00:02:07.860 --> 00:02:11.029 align:start position:0% have less than 10 validators in this graph<00:02:08.099> you're<00:02:08.340> going<00:02:08.580> to<00:02:08.759> see<00:02:09.000> a<00:02:09.720> very<00:02:10.020> big<00:02:10.440> bar 00:02:11.029 --> 00:02:11.039 align:start position:0% graph you're going to see a very big bar 00:02:11.039 --> 00:02:13.910 align:start position:0% graph you're going to see a very big bar that's<00:02:11.819> the<00:02:12.060> one<00:02:12.180> with<00:02:12.900> see<00:02:13.319> your<00:02:13.500> evaluators 00:02:13.910 --> 00:02:13.920 align:start position:0% that's the one with see your evaluators 00:02:13.920 --> 00:02:15.170 align:start position:0% that's the one with see your evaluators I<00:02:14.040> hope<00:02:14.160> you<00:02:14.280> can<00:02:14.400> see<00:02:14.459> it 00:02:15.170 --> 00:02:15.180 align:start position:0% I hope you can see it 00:02:15.180 --> 00:02:18.110 align:start position:0% I hope you can see it those<00:02:16.020> are<00:02:16.440> a<00:02:17.280> very<00:02:17.400> big<00:02:17.520> chunk<00:02:17.760> of<00:02:18.000> the 00:02:18.110 --> 00:02:18.120 align:start position:0% those are a very big chunk of the 00:02:18.120 --> 00:02:20.229 align:start position:0% those are a very big chunk of the network<00:02:18.300> almost<00:02:18.840> 60<00:02:19.080> percent<00:02:19.379> of<00:02:19.680> the<00:02:19.800> network 00:02:20.229 --> 00:02:20.239 align:start position:0% network almost 60 percent of the network 00:02:20.239 --> 00:02:23.530 align:start position:0% network almost 60 percent of the network then<00:02:21.239> we<00:02:22.020> have 00:02:23.530 --> 00:02:23.540 align:start position:0% then we have 00:02:23.540 --> 00:02:26.570 align:start position:0% then we have those<00:02:24.540> that<00:02:25.020> we<00:02:25.260> call<00:02:25.379> homesteakers 00:02:26.570 --> 00:02:26.580 align:start position:0% those that we call homesteakers 00:02:26.580 --> 00:02:28.970 align:start position:0% those that we call homesteakers most<00:02:27.180> of<00:02:27.300> them<00:02:27.420> have<00:02:27.720> just<00:02:27.959> one<00:02:28.200> validator<00:02:28.680> and 00:02:28.970 --> 00:02:28.980 align:start position:0% most of them have just one validator and 00:02:28.980 --> 00:02:30.710 align:start position:0% most of them have just one validator and then<00:02:29.160> we<00:02:29.340> have<00:02:29.520> those<00:02:30.120> that<00:02:30.420> we<00:02:30.540> call 00:02:30.710 --> 00:02:30.720 align:start position:0% then we have those that we call 00:02:30.720 --> 00:02:33.650 align:start position:0% then we have those that we call institutional<00:02:31.620> stakers<00:02:32.160> those<00:02:33.000> are<00:02:33.180> the<00:02:33.360> ones 00:02:33.650 --> 00:02:33.660 align:start position:0% institutional stakers those are the ones 00:02:33.660 --> 00:02:36.470 align:start position:0% institutional stakers those are the ones that<00:02:34.200> have<00:02:34.379> more<00:02:34.739> than<00:02:34.860> 64<00:02:35.280> validators 00:02:36.470 --> 00:02:36.480 align:start position:0% that have more than 64 validators 00:02:36.480 --> 00:02:40.010 align:start position:0% that have more than 64 validators which<00:02:37.020> is<00:02:37.200> the<00:02:37.739> big<00:02:37.920> board<00:02:38.160> at<00:02:38.640> the<00:02:38.819> end<00:02:39.020> now 00:02:40.010 --> 00:02:40.020 align:start position:0% which is the big board at the end now 00:02:40.020 --> 00:02:42.770 align:start position:0% which is the big board at the end now why<00:02:40.560> do<00:02:40.739> we<00:02:40.860> care<00:02:41.099> about<00:02:41.400> bandwidth<00:02:42.300> to<00:02:42.660> begin 00:02:42.770 --> 00:02:42.780 align:start position:0% why do we care about bandwidth to begin 00:02:42.780 --> 00:02:43.729 align:start position:0% why do we care about bandwidth to begin with 00:02:43.729 --> 00:02:43.739 align:start position:0% with 00:02:43.739 --> 00:02:46.850 align:start position:0% with so<00:02:44.459> there<00:02:44.819> are<00:02:45.060> a<00:02:45.120> couple<00:02:45.420> of<00:02:45.620> downsides<00:02:46.620> of 00:02:46.850 --> 00:02:46.860 align:start position:0% so there are a couple of downsides of 00:02:46.860 --> 00:02:49.309 align:start position:0% so there are a couple of downsides of high<00:02:47.040> bandwidth<00:02:47.640> the<00:02:48.360> first<00:02:48.480> one<00:02:48.660> is<00:02:49.080> of 00:02:49.309 --> 00:02:49.319 align:start position:0% high bandwidth the first one is of 00:02:49.319 --> 00:02:51.350 align:start position:0% high bandwidth the first one is of course<00:02:49.500> an<00:02:50.099> increased<00:02:50.580> cost 00:02:51.350 --> 00:02:51.360 align:start position:0% course an increased cost 00:02:51.360 --> 00:02:54.890 align:start position:0% course an increased cost if<00:02:52.260> this<00:02:52.620> cost<00:02:52.800> comes<00:02:53.220> from<00:02:53.459> running<00:02:53.900> for 00:02:54.890 --> 00:02:54.900 align:start position:0% if this cost comes from running for 00:02:54.900 --> 00:02:56.630 align:start position:0% if this cost comes from running for example<00:02:55.080> in<00:02:55.260> the<00:02:55.440> cloud<00:02:55.560> where<00:02:56.099> your<00:02:56.340> chart 00:02:56.630 --> 00:02:56.640 align:start position:0% example in the cloud where your chart 00:02:56.640 --> 00:03:01.130 align:start position:0% example in the cloud where your chart charged<00:02:57.599> for<00:02:58.440> uh<00:02:59.220> data<00:02:59.700> data<00:03:00.120> transfer 00:03:01.130 --> 00:03:01.140 align:start position:0% charged for uh data data transfer 00:03:01.140 --> 00:03:03.949 align:start position:0% charged for uh data data transfer and<00:03:01.920> it's<00:03:02.400> also<00:03:02.760> a<00:03:02.879> matter<00:03:03.060> of<00:03:03.300> diversity 00:03:03.949 --> 00:03:03.959 align:start position:0% and it's also a matter of diversity 00:03:03.959 --> 00:03:06.350 align:start position:0% and it's also a matter of diversity because<00:03:04.739> this<00:03:05.040> means<00:03:05.340> that<00:03:05.580> you're<00:03:05.819> only<00:03:06.060> able 00:03:06.350 --> 00:03:06.360 align:start position:0% because this means that you're only able 00:03:06.360 --> 00:03:08.570 align:start position:0% because this means that you're only able to<00:03:06.480> run<00:03:06.660> a<00:03:06.900> full<00:03:07.019> node<00:03:07.319> in<00:03:07.920> devices<00:03:08.220> that 00:03:08.570 --> 00:03:08.580 align:start position:0% to run a full node in devices that 00:03:08.580 --> 00:03:11.030 align:start position:0% to run a full node in devices that support<00:03:09.200> processing<00:03:10.200> all<00:03:10.440> the<00:03:10.620> data<00:03:10.920> that 00:03:11.030 --> 00:03:11.040 align:start position:0% support processing all the data that 00:03:11.040 --> 00:03:13.250 align:start position:0% support processing all the data that you're<00:03:11.280> receiving<00:03:11.580> from<00:03:11.879> the<00:03:12.000> network<00:03:12.260> and 00:03:13.250 --> 00:03:13.260 align:start position:0% you're receiving from the network and 00:03:13.260 --> 00:03:16.369 align:start position:0% you're receiving from the network and for<00:03:13.800> people<00:03:14.099> that<00:03:14.400> are<00:03:14.519> able<00:03:14.819> to<00:03:15.060> pay<00:03:15.300> for<00:03:16.200> the 00:03:16.369 --> 00:03:16.379 align:start position:0% for people that are able to pay for the 00:03:16.379 --> 00:03:18.470 align:start position:0% for people that are able to pay for the services<00:03:16.560> in<00:03:17.099> which<00:03:17.340> these<00:03:17.940> nodes<00:03:18.180> have<00:03:18.360> been 00:03:18.470 --> 00:03:18.480 align:start position:0% services in which these nodes have been 00:03:18.480 --> 00:03:19.670 align:start position:0% services in which these nodes have been running 00:03:19.670 --> 00:03:19.680 align:start position:0% running 00:03:19.680 --> 00:03:22.070 align:start position:0% running um I<00:03:20.099> see<00:03:20.220> a<00:03:20.340> few<00:03:20.459> devs<00:03:20.879> here<00:03:21.000> more<00:03:21.720> my 00:03:22.070 --> 00:03:22.080 align:start position:0% um I see a few devs here more my 00:03:22.080 --> 00:03:23.930 align:start position:0% um I see a few devs here more my colleges<00:03:22.440> for<00:03:22.620> example 00:03:23.930 --> 00:03:23.940 align:start position:0% colleges for example 00:03:23.940 --> 00:03:26.630 align:start position:0% colleges for example um<00:03:24.000> we<00:03:24.780> know<00:03:24.959> that<00:03:25.200> there<00:03:25.379> is<00:03:25.560> going<00:03:25.680> to<00:03:25.800> be<00:03:26.040> an 00:03:26.630 --> 00:03:26.640 align:start position:0% um we know that there is going to be an 00:03:26.640 --> 00:03:28.490 align:start position:0% um we know that there is going to be an upgrade<00:03:26.940> to<00:03:27.120> the<00:03:27.300> network<00:03:27.480> that<00:03:28.080> is<00:03:28.200> going<00:03:28.379> to 00:03:28.490 --> 00:03:28.500 align:start position:0% upgrade to the network that is going to 00:03:28.500 --> 00:03:32.270 align:start position:0% upgrade to the network that is going to bring<00:03:28.860> a<00:03:29.760> lot<00:03:29.940> of<00:03:30.060> big<00:03:31.019> big<00:03:31.500> increase<00:03:31.980> in 00:03:32.270 --> 00:03:32.280 align:start position:0% bring a lot of big big increase in 00:03:32.280 --> 00:03:35.030 align:start position:0% bring a lot of big big increase in bandwidth<00:03:32.879> like<00:03:33.120> a<00:03:33.540> lot<00:03:33.659> so<00:03:34.440> we<00:03:34.560> need<00:03:34.680> to<00:03:34.860> start 00:03:35.030 --> 00:03:35.040 align:start position:0% bandwidth like a lot so we need to start 00:03:35.040 --> 00:03:37.369 align:start position:0% bandwidth like a lot so we need to start tackling<00:03:35.519> this<00:03:36.239> problem<00:03:36.420> right<00:03:36.959> now<00:03:37.140> before 00:03:37.369 --> 00:03:37.379 align:start position:0% tackling this problem right now before 00:03:37.379 --> 00:03:39.830 align:start position:0% tackling this problem right now before this<00:03:37.800> happens<00:03:38.000> that's<00:03:39.000> another<00:03:39.180> big<00:03:39.599> reason 00:03:39.830 --> 00:03:39.840 align:start position:0% this happens that's another big reason 00:03:39.840 --> 00:03:43.070 align:start position:0% this happens that's another big reason why<00:03:40.379> this<00:03:41.340> is<00:03:41.459> important 00:03:43.070 --> 00:03:43.080 align:start position:0% why this is important 00:03:43.080 --> 00:03:45.289 align:start position:0% why this is important um also<00:03:43.500> another<00:03:43.680> really<00:03:44.640> really<00:03:44.760> important 00:03:45.289 --> 00:03:45.299 align:start position:0% um also another really really important 00:03:45.299 --> 00:03:48.350 align:start position:0% um also another really really important reason<00:03:45.599> is<00:03:46.260> when<00:03:47.220> we<00:03:47.340> say<00:03:47.519> for<00:03:47.879> example<00:03:48.060> A 00:03:48.350 --> 00:03:48.360 align:start position:0% reason is when we say for example A 00:03:48.360 --> 00:03:51.289 align:start position:0% reason is when we say for example A diversity<00:03:48.780> problem<00:03:49.080> the<00:03:49.799> truth<00:03:50.040> is<00:03:50.400> if<00:03:51.120> you 00:03:51.289 --> 00:03:51.299 align:start position:0% diversity problem the truth is if you 00:03:51.299 --> 00:03:53.449 align:start position:0% diversity problem the truth is if you are<00:03:51.420> for<00:03:51.540> example<00:03:51.720> a<00:03:51.900> homesteaker<00:03:52.560> and<00:03:53.220> you're 00:03:53.449 --> 00:03:53.459 align:start position:0% are for example a homesteaker and you're 00:03:53.459 --> 00:03:55.490 align:start position:0% are for example a homesteaker and you're running<00:03:53.640> your<00:03:53.879> beacon<00:03:54.239> note<00:03:54.480> with<00:03:55.019> your 00:03:55.490 --> 00:03:55.500 align:start position:0% running your beacon note with your 00:03:55.500 --> 00:03:57.890 align:start position:0% running your beacon note with your single<00:03:55.799> body<00:03:55.920> data<00:03:56.340> attached<00:03:56.760> and<00:03:57.420> then<00:03:57.599> your 00:03:57.890 --> 00:03:57.900 align:start position:0% single body data attached and then your 00:03:57.900 --> 00:03:59.390 align:start position:0% single body data attached and then your brother<00:03:58.019> or<00:03:58.319> your<00:03:58.440> sister<00:03:58.620> starts<00:03:59.220> playing 00:03:59.390 --> 00:03:59.400 align:start position:0% brother or your sister starts playing 00:03:59.400 --> 00:04:02.690 align:start position:0% brother or your sister starts playing video<00:03:59.640> games<00:04:00.379> then<00:04:01.379> you're<00:04:01.920> going<00:04:02.159> to<00:04:02.280> have<00:04:02.459> a 00:04:02.690 --> 00:04:02.700 align:start position:0% video games then you're going to have a 00:04:02.700 --> 00:04:05.690 align:start position:0% video games then you're going to have a bandwidth<00:04:03.239> Spike<00:04:03.900> and<00:04:04.560> you<00:04:04.799> might<00:04:04.980> lose<00:04:05.459> at 00:04:05.690 --> 00:04:05.700 align:start position:0% bandwidth Spike and you might lose at 00:04:05.700 --> 00:04:07.309 align:start position:0% bandwidth Spike and you might lose at the<00:04:05.879> stations<00:04:06.299> you<00:04:06.720> might<00:04:06.900> miss<00:04:07.080> other 00:04:07.309 --> 00:04:07.319 align:start position:0% the stations you might miss other 00:04:07.319 --> 00:04:10.789 align:start position:0% the stations you might miss other stations<00:04:08.060> blocks<00:04:09.060> so<00:04:09.959> basically<00:04:10.379> you're 00:04:10.789 --> 00:04:10.799 align:start position:0% stations blocks so basically you're 00:04:10.799 --> 00:04:13.789 align:start position:0% stations blocks so basically you're losing<00:04:11.280> money<00:04:11.700> simply<00:04:12.540> because<00:04:12.780> very<00:04:13.560> very 00:04:13.789 --> 00:04:13.799 align:start position:0% losing money simply because very very 00:04:13.799 --> 00:04:17.689 align:start position:0% losing money simply because very very short<00:04:14.220> the<00:04:15.000> spikes<00:04:15.360> in<00:04:15.480> bandwidth<00:04:16.560> so<00:04:17.220> yeah<00:04:17.400> we 00:04:17.689 --> 00:04:17.699 align:start position:0% short the spikes in bandwidth so yeah we 00:04:17.699 --> 00:04:18.890 align:start position:0% short the spikes in bandwidth so yeah we don't<00:04:17.880> want<00:04:18.060> that 00:04:18.890 --> 00:04:18.900 align:start position:0% don't want that 00:04:18.900 --> 00:04:21.409 align:start position:0% don't want that now<00:04:19.680> let's<00:04:19.919> check<00:04:20.160> where<00:04:20.579> is<00:04:20.760> the<00:04:20.880> bandwidth 00:04:21.409 --> 00:04:21.419 align:start position:0% now let's check where is the bandwidth 00:04:21.419 --> 00:04:24.590 align:start position:0% now let's check where is the bandwidth coming<00:04:21.600> from<00:04:21.959> for<00:04:22.919> the<00:04:23.160> sake<00:04:23.340> of<00:04:23.520> this<00:04:23.699> talk<00:04:23.940> we 00:04:24.590 --> 00:04:24.600 align:start position:0% coming from for the sake of this talk we 00:04:24.600 --> 00:04:26.330 align:start position:0% coming from for the sake of this talk we are<00:04:24.780> going<00:04:24.900> to<00:04:25.020> separate<00:04:25.440> protocols<00:04:26.040> between 00:04:26.330 --> 00:04:26.340 align:start position:0% are going to separate protocols between 00:04:26.340 --> 00:04:30.230 align:start position:0% are going to separate protocols between discovery<00:04:27.600> and<00:04:28.139> non-discovery<00:04:28.919> so<00:04:29.460> why<00:04:30.000> is 00:04:30.230 --> 00:04:30.240 align:start position:0% discovery and non-discovery so why is 00:04:30.240 --> 00:04:32.230 align:start position:0% discovery and non-discovery so why is that<00:04:30.360> because<00:04:30.600> Discovery<00:04:31.199> has 00:04:32.230 --> 00:04:32.240 align:start position:0% that because Discovery has 00:04:32.240 --> 00:04:34.870 align:start position:0% that because Discovery has its<00:04:33.240> own<00:04:33.300> transport<00:04:33.720> its<00:04:34.080> own<00:04:34.139> encryption 00:04:34.870 --> 00:04:34.880 align:start position:0% its own transport its own encryption 00:04:34.880 --> 00:04:39.350 align:start position:0% its own transport its own encryption it's<00:04:35.880> over<00:04:36.540> UDP<00:04:37.320> whereas<00:04:38.220> all<00:04:38.520> the<00:04:38.699> leave<00:04:38.820> P2P 00:04:39.350 --> 00:04:39.360 align:start position:0% it's over UDP whereas all the leave P2P 00:04:39.360 --> 00:04:41.090 align:start position:0% it's over UDP whereas all the leave P2P we're<00:04:39.540> going<00:04:39.660> to<00:04:39.780> call<00:04:39.840> them<00:04:40.020> lip<00:04:40.800> P2P 00:04:41.090 --> 00:04:41.100 align:start position:0% we're going to call them lip P2P 00:04:41.100 --> 00:04:44.930 align:start position:0% we're going to call them lip P2P protocols<00:04:41.759> uh<00:04:42.540> they're<00:04:42.840> over<00:04:43.080> TCP<00:04:43.979> we<00:04:44.699> have 00:04:44.930 --> 00:04:44.940 align:start position:0% protocols uh they're over TCP we have 00:04:44.940 --> 00:04:48.590 align:start position:0% protocols uh they're over TCP we have gossips<00:04:45.900> of<00:04:46.199> and<00:04:46.919> the<00:04:47.100> request<00:04:47.460> response<00:04:48.000> the 00:04:48.590 --> 00:04:48.600 align:start position:0% gossips of and the request response the 00:04:48.600 --> 00:04:50.810 align:start position:0% gossips of and the request response the one<00:04:48.720> we<00:04:48.960> are<00:04:49.080> going<00:04:49.259> to<00:04:49.440> be<00:04:49.680> focusing<00:04:50.400> mainly 00:04:50.810 --> 00:04:50.820 align:start position:0% one we are going to be focusing mainly 00:04:50.820 --> 00:04:53.150 align:start position:0% one we are going to be focusing mainly in<00:04:51.000> the<00:04:51.120> stock<00:04:51.240> is<00:04:51.540> Gossip<00:04:52.020> so 00:04:53.150 --> 00:04:53.160 align:start position:0% in the stock is Gossip so 00:04:53.160 --> 00:04:55.249 align:start position:0% in the stock is Gossip so now<00:04:53.699> that<00:04:53.940> we<00:04:54.120> have<00:04:54.180> this<00:04:54.419> separation<00:04:54.840> between 00:04:55.249 --> 00:04:55.259 align:start position:0% now that we have this separation between 00:04:55.259 --> 00:04:58.310 align:start position:0% now that we have this separation between let's<00:04:56.220> say<00:04:56.340> Discovery<00:04:57.060> and<00:04:57.479> not<00:04:57.720> Discovery 00:04:58.310 --> 00:04:58.320 align:start position:0% let's say Discovery and not Discovery 00:04:58.320 --> 00:05:00.770 align:start position:0% let's say Discovery and not Discovery let's<00:04:59.280> check<00:04:59.580> where<00:05:00.120> is<00:05:00.240> the<00:05:00.360> bandwidth 00:05:00.770 --> 00:05:00.780 align:start position:0% let's check where is the bandwidth 00:05:00.780 --> 00:05:03.469 align:start position:0% let's check where is the bandwidth coming<00:05:00.960> from<00:05:01.199> this<00:05:01.919> is<00:05:02.040> what<00:05:02.759> the<00:05:03.000> bandwidth 00:05:03.469 --> 00:05:03.479 align:start position:0% coming from this is what the bandwidth 00:05:03.479 --> 00:05:06.050 align:start position:0% coming from this is what the bandwidth total<00:05:04.259> bandwidth<00:05:04.800> looks<00:05:05.400> like<00:05:05.460> for<00:05:05.759> one<00:05:05.940> of 00:05:06.050 --> 00:05:06.060 align:start position:0% total bandwidth looks like for one of 00:05:06.060 --> 00:05:08.510 align:start position:0% total bandwidth looks like for one of our<00:05:06.180> nodes<00:05:06.540> for<00:05:06.960> the<00:05:07.139> last<00:05:07.320> couple<00:05:07.500> of<00:05:07.620> days 00:05:08.510 --> 00:05:08.520 align:start position:0% our nodes for the last couple of days 00:05:08.520 --> 00:05:11.510 align:start position:0% our nodes for the last couple of days is<00:05:08.880> it<00:05:09.060> Discovery<00:05:09.540> is<00:05:10.199> it<00:05:10.320> live<00:05:10.560> PDP<00:05:11.040> where<00:05:11.340> is 00:05:11.510 --> 00:05:11.520 align:start position:0% is it Discovery is it live PDP where is 00:05:11.520 --> 00:05:14.330 align:start position:0% is it Discovery is it live PDP where is it<00:05:12.120> so<00:05:12.600> now<00:05:12.720> we<00:05:12.960> have<00:05:13.080> two<00:05:13.380> graphs<00:05:13.800> the<00:05:14.160> purple 00:05:14.330 --> 00:05:14.340 align:start position:0% it so now we have two graphs the purple 00:05:14.340 --> 00:05:17.689 align:start position:0% it so now we have two graphs the purple one<00:05:14.699> is<00:05:15.600> going<00:05:15.780> to<00:05:15.960> be<00:05:16.080> Discovery<00:05:16.740> as<00:05:17.220> all<00:05:17.520> the 00:05:17.689 --> 00:05:17.699 align:start position:0% one is going to be Discovery as all the 00:05:17.699 --> 00:05:20.030 align:start position:0% one is going to be Discovery as all the discovery<00:05:18.000> bandwidth<00:05:18.479> and<00:05:19.380> the<00:05:19.560> other<00:05:19.680> one<00:05:19.800> in 00:05:20.030 --> 00:05:20.040 align:start position:0% discovery bandwidth and the other one in 00:05:20.040 --> 00:05:22.850 align:start position:0% discovery bandwidth and the other one in the<00:05:20.160> bottom<00:05:20.400> is<00:05:20.940> dollar<00:05:21.360> v2p<00:05:21.900> bandwidth<00:05:22.440> now 00:05:22.850 --> 00:05:22.860 align:start position:0% the bottom is dollar v2p bandwidth now 00:05:22.860 --> 00:05:24.350 align:start position:0% the bottom is dollar v2p bandwidth now forget<00:05:23.039> about<00:05:23.340> the<00:05:23.520> scales<00:05:23.880> this<00:05:24.120> is<00:05:24.180> just 00:05:24.350 --> 00:05:24.360 align:start position:0% forget about the scales this is just 00:05:24.360 --> 00:05:28.249 align:start position:0% forget about the scales this is just like<00:05:24.600> a<00:05:24.960> non<00:05:25.740> node<00:05:26.280> very<00:05:26.520> sciency<00:05:26.940> analysis<00:05:27.720> of 00:05:28.249 --> 00:05:28.259 align:start position:0% like a non node very sciency analysis of 00:05:28.259 --> 00:05:30.590 align:start position:0% like a non node very sciency analysis of the<00:05:28.440> shape<00:05:28.740> of<00:05:29.340> the<00:05:29.460> shape<00:05:29.699> of<00:05:29.880> the<00:05:30.000> bandwidth 00:05:30.590 --> 00:05:30.600 align:start position:0% the shape of the shape of the bandwidth 00:05:30.600 --> 00:05:33.290 align:start position:0% the shape of the shape of the bandwidth so<00:05:31.560> I<00:05:32.100> guess<00:05:32.220> we<00:05:32.460> can 00:05:33.290 --> 00:05:33.300 align:start position:0% so I guess we can 00:05:33.300 --> 00:05:37.189 align:start position:0% so I guess we can more<00:05:33.960> or<00:05:34.080> less<00:05:34.139> agree<00:05:34.560> that<00:05:35.600> bandwidth<00:05:36.600> has 00:05:37.189 --> 00:05:37.199 align:start position:0% more or less agree that bandwidth has 00:05:37.199 --> 00:05:40.310 align:start position:0% more or less agree that bandwidth has the<00:05:37.380> shape<00:05:37.620> of<00:05:38.100> the<00:05:38.220> leaf<00:05:38.400> P2P<00:05:38.880> when<00:05:39.320> whereas 00:05:40.310 --> 00:05:40.320 align:start position:0% the shape of the leaf P2P when whereas 00:05:40.320 --> 00:05:43.790 align:start position:0% the shape of the leaf P2P when whereas Discovery<00:05:40.800> is<00:05:41.460> well<00:05:41.880> it's<00:05:42.419> very<00:05:42.960> magical<00:05:43.380> as 00:05:43.790 --> 00:05:43.800 align:start position:0% Discovery is well it's very magical as 00:05:43.800 --> 00:05:45.290 align:start position:0% Discovery is well it's very magical as we<00:05:44.039> will<00:05:44.160> see 00:05:45.290 --> 00:05:45.300 align:start position:0% we will see 00:05:45.300 --> 00:05:47.650 align:start position:0% we will see so<00:05:45.600> the<00:05:45.780> total<00:05:45.960> bandwidth<00:05:46.500> is<00:05:46.800> around 00:05:47.650 --> 00:05:47.660 align:start position:0% so the total bandwidth is around 00:05:47.660 --> 00:05:50.810 align:start position:0% so the total bandwidth is around 250<00:05:48.660> kilobytes<00:05:49.320> per<00:05:49.560> second 00:05:50.810 --> 00:05:50.820 align:start position:0% 250 kilobytes per second 00:05:50.820 --> 00:05:52.790 align:start position:0% 250 kilobytes per second is<00:05:51.240> it<00:05:51.360> better<00:05:51.479> like<00:05:51.780> this<00:05:51.960> yeah 00:05:52.790 --> 00:05:52.800 align:start position:0% is it better like this yeah 00:05:52.800 --> 00:05:57.050 align:start position:0% is it better like this yeah okay<00:05:53.479> about<00:05:54.680> 250<00:05:55.680> kilobytes<00:05:56.400> per<00:05:56.520> sec<00:05:56.699> per 00:05:57.050 --> 00:05:57.060 align:start position:0% okay about 250 kilobytes per sec per 00:05:57.060 --> 00:05:59.629 align:start position:0% okay about 250 kilobytes per sec per second<00:05:57.240> then<00:05:58.080> we<00:05:58.320> have<00:05:58.380> lip<00:05:58.740> PDP<00:05:59.100> which<00:05:59.520> is 00:05:59.629 --> 00:05:59.639 align:start position:0% second then we have lip PDP which is 00:05:59.639 --> 00:06:02.870 align:start position:0% second then we have lip PDP which is around<00:05:59.840> 200<00:06:00.840> kilobytes<00:06:01.500> and<00:06:01.979> then<00:06:02.220> discovery 00:06:02.870 --> 00:06:02.880 align:start position:0% around 200 kilobytes and then discovery 00:06:02.880 --> 00:06:06.409 align:start position:0% around 200 kilobytes and then discovery which<00:06:03.419> is<00:06:03.600> between<00:06:04.380> 40<00:06:04.919> and<00:06:05.400> 60<00:06:05.639> kilobytes<00:06:06.240> per 00:06:06.409 --> 00:06:06.419 align:start position:0% which is between 40 and 60 kilobytes per 00:06:06.419 --> 00:06:09.890 align:start position:0% which is between 40 and 60 kilobytes per second<00:06:06.660> so<00:06:07.380> for<00:06:07.680> the<00:06:07.800> sake<00:06:07.979> of<00:06:08.360> doing<00:06:09.360> analysis 00:06:09.890 --> 00:06:09.900 align:start position:0% second so for the sake of doing analysis 00:06:09.900 --> 00:06:12.650 align:start position:0% second so for the sake of doing analysis over<00:06:10.139> pan<00:06:10.500> with<00:06:10.820> Discovery<00:06:11.820> is<00:06:12.000> really<00:06:12.360> not 00:06:12.650 --> 00:06:12.660 align:start position:0% over pan with Discovery is really not 00:06:12.660 --> 00:06:14.990 align:start position:0% over pan with Discovery is really not important<00:06:13.199> so<00:06:13.680> we're<00:06:13.860> going<00:06:14.039> to<00:06:14.160> focus<00:06:14.460> only 00:06:14.990 --> 00:06:15.000 align:start position:0% important so we're going to focus only 00:06:15.000 --> 00:06:16.370 align:start position:0% important so we're going to focus only with<00:06:15.240> P2P 00:06:16.370 --> 00:06:16.380 align:start position:0% with P2P 00:06:16.380 --> 00:06:20.029 align:start position:0% with P2P so<00:06:17.039> I<00:06:17.340> was<00:06:17.520> saying<00:06:18.120> we<00:06:18.600> have<00:06:18.840> gossips<00:06:19.440> up<00:06:19.740> and 00:06:20.029 --> 00:06:20.039 align:start position:0% so I was saying we have gossips up and 00:06:20.039 --> 00:06:22.129 align:start position:0% so I was saying we have gossips up and request<00:06:20.400> response<00:06:20.940> we're<00:06:21.060> going<00:06:21.240> to<00:06:21.360> focus 00:06:22.129 --> 00:06:22.139 align:start position:0% request response we're going to focus 00:06:22.139 --> 00:06:24.230 align:start position:0% request response we're going to focus on<00:06:22.919> Gossip<00:06:23.340> stuff 00:06:24.230 --> 00:06:24.240 align:start position:0% on Gossip stuff 00:06:24.240 --> 00:06:26.749 align:start position:0% on Gossip stuff so<00:06:24.720> in<00:06:24.960> Gossip<00:06:25.380> so<00:06:25.560> gossip<00:06:26.100> soap<00:06:26.460> is<00:06:26.580> a 00:06:26.749 --> 00:06:26.759 align:start position:0% so in Gossip so gossip soap is a 00:06:26.759 --> 00:06:30.290 align:start position:0% so in Gossip so gossip soap is a published<00:06:27.240> subscribe<00:06:27.660> system<00:06:27.860> protocol<00:06:29.300> we 00:06:30.290 --> 00:06:30.300 align:start position:0% published subscribe system protocol we 00:06:30.300 --> 00:06:33.650 align:start position:0% published subscribe system protocol we publish<00:06:30.780> messages<00:06:31.620> to<00:06:32.400> the<00:06:32.699> network<00:06:32.880> those 00:06:33.650 --> 00:06:33.660 align:start position:0% publish messages to the network those 00:06:33.660 --> 00:06:36.409 align:start position:0% publish messages to the network those get<00:06:34.020> disseminated<00:06:34.800> to<00:06:35.039> other<00:06:35.220> peers<00:06:35.639> and<00:06:36.240> we 00:06:36.409 --> 00:06:36.419 align:start position:0% get disseminated to other peers and we 00:06:36.419 --> 00:06:38.450 align:start position:0% get disseminated to other peers and we receive<00:06:36.720> messages<00:06:37.020> to<00:06:37.440> subnets<00:06:37.979> where<00:06:38.280> are 00:06:38.450 --> 00:06:38.460 align:start position:0% receive messages to subnets where are 00:06:38.460 --> 00:06:41.930 align:start position:0% receive messages to subnets where are two<00:06:38.639> topics<00:06:38.880> to<00:06:39.180> which<00:06:39.419> we<00:06:39.600> are<00:06:39.840> subscribed 00:06:41.930 --> 00:06:41.940 align:start position:0% two topics to which we are subscribed 00:06:41.940 --> 00:06:44.510 align:start position:0% two topics to which we are subscribed we<00:06:42.479> have<00:06:42.600> large<00:06:42.900> amounts<00:06:43.319> of<00:06:43.380> data<00:06:43.740> and<00:06:44.220> those 00:06:44.510 --> 00:06:44.520 align:start position:0% we have large amounts of data and those 00:06:44.520 --> 00:06:47.450 align:start position:0% we have large amounts of data and those will<00:06:44.759> split<00:06:45.240> between<00:06:45.840> subnets<00:06:46.560> again<00:06:46.919> here<00:06:47.280> we 00:06:47.450 --> 00:06:47.460 align:start position:0% will split between subnets again here we 00:06:47.460 --> 00:06:50.150 align:start position:0% will split between subnets again here we have<00:06:47.580> 64<00:06:48.060> attestation<00:06:48.660> subnets<00:06:49.139> which<00:06:49.979> again 00:06:50.150 --> 00:06:50.160 align:start position:0% have 64 attestation subnets which again 00:06:50.160 --> 00:06:54.230 align:start position:0% have 64 attestation subnets which again age<00:06:50.460> is<00:06:50.759> going<00:06:50.940> to<00:06:51.060> be<00:06:51.300> talking<00:06:52.259> further<00:06:53.280> in<00:06:54.120> a 00:06:54.230 --> 00:06:54.240 align:start position:0% age is going to be talking further in a 00:06:54.240 --> 00:06:55.790 align:start position:0% age is going to be talking further in a moment 00:06:55.790 --> 00:06:55.800 align:start position:0% moment 00:06:55.800 --> 00:06:58.790 align:start position:0% moment and<00:06:56.580> then<00:06:56.759> we<00:06:57.539> need<00:06:57.660> to<00:06:57.900> think<00:06:58.139> how<00:06:58.680> many 00:06:58.790 --> 00:06:58.800 align:start position:0% and then we need to think how many 00:06:58.800 --> 00:07:00.770 align:start position:0% and then we need to think how many subnets<00:06:59.280> are<00:06:59.639> we<00:06:59.759> subscribed<00:07:00.180> to<00:07:00.300> since<00:07:00.539> this 00:07:00.770 --> 00:07:00.780 align:start position:0% subnets are we subscribed to since this 00:07:00.780 --> 00:07:03.050 align:start position:0% subnets are we subscribed to since this is<00:07:00.960> since<00:07:01.259> this<00:07:01.500> is<00:07:01.620> the<00:07:01.800> reason<00:07:01.979> why<00:07:02.759> we<00:07:02.940> get 00:07:03.050 --> 00:07:03.060 align:start position:0% is since this is the reason why we get 00:07:03.060 --> 00:07:05.510 align:start position:0% is since this is the reason why we get so<00:07:03.360> many<00:07:03.539> so<00:07:04.139> much<00:07:04.259> bandwidth<00:07:04.800> and<00:07:05.280> the<00:07:05.400> reason 00:07:05.510 --> 00:07:05.520 align:start position:0% so many so much bandwidth and the reason 00:07:05.520 --> 00:07:07.790 align:start position:0% so many so much bandwidth and the reason is<00:07:05.880> that<00:07:06.180> right<00:07:06.419> now<00:07:06.660> is<00:07:07.080> because<00:07:07.380> now<00:07:07.620> they're 00:07:07.790 --> 00:07:07.800 align:start position:0% is that right now is because now they're 00:07:07.800 --> 00:07:10.070 align:start position:0% is that right now is because now they're subscribing<00:07:08.160> to<00:07:08.340> one<00:07:08.520> subnet<00:07:09.000> for<00:07:09.660> each 00:07:10.070 --> 00:07:10.080 align:start position:0% subscribing to one subnet for each 00:07:10.080 --> 00:07:13.969 align:start position:0% subscribing to one subnet for each validator<00:07:10.979> that<00:07:11.340> it<00:07:11.460> has<00:07:11.699> attached<00:07:12.600> and<00:07:13.199> yeah 00:07:13.969 --> 00:07:13.979 align:start position:0% validator that it has attached and yeah 00:07:13.979 --> 00:07:16.550 align:start position:0% validator that it has attached and yeah well<00:07:14.160> subscribing<00:07:14.639> to<00:07:14.759> a<00:07:14.880> subnet<00:07:15.300> means<00:07:16.139> a<00:07:16.380> lot 00:07:16.550 --> 00:07:16.560 align:start position:0% well subscribing to a subnet means a lot 00:07:16.560 --> 00:07:18.529 align:start position:0% well subscribing to a subnet means a lot more<00:07:16.740> of<00:07:17.100> bandwidth 00:07:18.529 --> 00:07:18.539 align:start position:0% more of bandwidth 00:07:18.539 --> 00:07:20.629 align:start position:0% more of bandwidth so<00:07:19.020> a<00:07:19.139> very<00:07:19.319> simple<00:07:19.440> example<00:07:19.860> of<00:07:20.039> how<00:07:20.280> gossip 00:07:20.629 --> 00:07:20.639 align:start position:0% so a very simple example of how gossip 00:07:20.639 --> 00:07:24.650 align:start position:0% so a very simple example of how gossip stuff<00:07:20.880> works<00:07:21.780> gossip<00:07:22.560> stuff<00:07:22.740> has<00:07:23.639> a<00:07:24.180> lot<00:07:24.419> of 00:07:24.650 --> 00:07:24.660 align:start position:0% stuff works gossip stuff has a lot of 00:07:24.660 --> 00:07:28.129 align:start position:0% stuff works gossip stuff has a lot of parameters<00:07:25.400> but<00:07:26.400> one<00:07:26.880> that<00:07:27.120> we<00:07:27.300> care<00:07:27.419> a<00:07:27.599> lot<00:07:27.720> is 00:07:28.129 --> 00:07:28.139 align:start position:0% parameters but one that we care a lot is 00:07:28.139 --> 00:07:30.350 align:start position:0% parameters but one that we care a lot is the<00:07:28.319> match<00:07:28.500> degree<00:07:28.800> so<00:07:29.099> this<00:07:29.340> example<00:07:29.699> is<00:07:30.060> the 00:07:30.350 --> 00:07:30.360 align:start position:0% the match degree so this example is the 00:07:30.360 --> 00:07:34.010 align:start position:0% the match degree so this example is the three<00:07:30.660> three<00:07:31.259> match<00:07:31.979> degree<00:07:32.880> so<00:07:33.539> we<00:07:33.720> are<00:07:33.900> going 00:07:34.010 --> 00:07:34.020 align:start position:0% three three match degree so we are going 00:07:34.020 --> 00:07:36.890 align:start position:0% three three match degree so we are going to<00:07:34.199> start<00:07:34.440> with<00:07:34.800> our<00:07:34.979> guy<00:07:35.220> in<00:07:35.880> the<00:07:36.000> middle<00:07:36.180> that 00:07:36.890 --> 00:07:36.900 align:start position:0% to start with our guy in the middle that 00:07:36.900 --> 00:07:39.650 align:start position:0% to start with our guy in the middle that one<00:07:37.080> I<00:07:37.259> hope<00:07:37.380> you<00:07:37.560> are<00:07:37.800> seeing<00:07:37.979> the<00:07:38.220> red<00:07:38.340> circle 00:07:39.650 --> 00:07:39.660 align:start position:0% one I hope you are seeing the red circle 00:07:39.660 --> 00:07:42.050 align:start position:0% one I hope you are seeing the red circle just<00:07:40.020> right<00:07:40.199> in<00:07:40.319> the<00:07:40.440> middle<00:07:41.039> so<00:07:41.460> this<00:07:41.639> guy<00:07:41.819> has 00:07:42.050 --> 00:07:42.060 align:start position:0% just right in the middle so this guy has 00:07:42.060 --> 00:07:43.490 align:start position:0% just right in the middle so this guy has a<00:07:42.180> validator<00:07:42.539> attached<00:07:43.020> it's<00:07:43.199> going<00:07:43.380> to 00:07:43.490 --> 00:07:43.500 align:start position:0% a validator attached it's going to 00:07:43.500 --> 00:07:45.770 align:start position:0% a validator attached it's going to publish<00:07:43.979> a<00:07:44.340> block 00:07:45.770 --> 00:07:45.780 align:start position:0% publish a block 00:07:45.780 --> 00:07:48.469 align:start position:0% publish a block so<00:07:46.199> it's<00:07:46.319> going<00:07:46.560> to<00:07:46.620> beg<00:07:47.039> to<00:07:47.400> pick<00:07:47.580> three<00:07:48.060> Piers 00:07:48.469 --> 00:07:48.479 align:start position:0% so it's going to beg to pick three Piers 00:07:48.479 --> 00:07:50.089 align:start position:0% so it's going to beg to pick three Piers it's<00:07:48.840> going<00:07:49.020> to<00:07:49.139> disseminate<00:07:49.800> the<00:07:49.919> message 00:07:50.089 --> 00:07:50.099 align:start position:0% it's going to disseminate the message 00:07:50.099 --> 00:07:52.189 align:start position:0% it's going to disseminate the message and<00:07:50.759> then<00:07:50.880> each<00:07:51.060> period<00:07:51.419> is<00:07:51.539> going<00:07:51.720> to<00:07:51.840> do<00:07:51.960> the 00:07:52.189 --> 00:07:52.199 align:start position:0% and then each period is going to do the 00:07:52.199 --> 00:07:55.550 align:start position:0% and then each period is going to do the same<00:07:52.319> with<00:07:52.860> some<00:07:53.580> other<00:07:53.759> three<00:07:54.000> peers 00:07:55.550 --> 00:07:55.560 align:start position:0% same with some other three peers 00:07:55.560 --> 00:07:58.129 align:start position:0% same with some other three peers and<00:07:56.099> so<00:07:56.340> on<00:07:56.520> and<00:07:57.060> so<00:07:57.300> on 00:07:58.129 --> 00:07:58.139 align:start position:0% and so on and so on 00:07:58.139 --> 00:08:00.469 align:start position:0% and so on and so on so<00:07:58.740> if<00:07:58.919> you<00:07:59.099> think<00:07:59.280> about<00:07:59.520> this<00:07:59.880> for<00:08:00.120> a<00:08:00.240> moment 00:08:00.469 --> 00:08:00.479 align:start position:0% so if you think about this for a moment 00:08:00.479 --> 00:08:02.870 align:start position:0% so if you think about this for a moment you're<00:08:00.900> going<00:08:01.080> to<00:08:01.199> realize<00:08:01.620> that<00:08:02.039> is<00:08:02.580> very 00:08:02.870 --> 00:08:02.880 align:start position:0% you're going to realize that is very 00:08:02.880 --> 00:08:04.610 align:start position:0% you're going to realize that is very likely<00:08:03.300> that<00:08:03.780> I<00:08:04.020> know<00:08:04.080> this<00:08:04.259> is<00:08:04.380> going<00:08:04.500> to 00:08:04.610 --> 00:08:04.620 align:start position:0% likely that I know this is going to 00:08:04.620 --> 00:08:05.689 align:start position:0% likely that I know this is going to receive 00:08:05.689 --> 00:08:05.699 align:start position:0% receive 00:08:05.699 --> 00:08:08.210 align:start position:0% receive one<00:08:06.300> single<00:08:06.599> one<00:08:06.720> unique<00:08:07.199> message<00:08:07.500> a<00:08:07.979> lot<00:08:08.099> of 00:08:08.210 --> 00:08:08.220 align:start position:0% one single one unique message a lot of 00:08:08.220 --> 00:08:11.029 align:start position:0% one single one unique message a lot of times<00:08:08.340> from<00:08:08.759> very<00:08:09.000> different<00:08:09.560> uh<00:08:10.560> notes 00:08:11.029 --> 00:08:11.039 align:start position:0% times from very different uh notes 00:08:11.039 --> 00:08:13.790 align:start position:0% times from very different uh notes across<00:08:11.639> very<00:08:11.880> different<00:08:12.120> paths<00:08:13.020> in<00:08:13.620> the 00:08:13.790 --> 00:08:13.800 align:start position:0% across very different paths in the 00:08:13.800 --> 00:08:16.969 align:start position:0% across very different paths in the network<00:08:13.919> from<00:08:14.220> the<00:08:14.400> source<00:08:14.759> to<00:08:15.300> themselves 00:08:16.969 --> 00:08:16.979 align:start position:0% network from the source to themselves 00:08:16.979 --> 00:08:19.610 align:start position:0% network from the source to themselves Okay<00:08:17.660> so 00:08:19.610 --> 00:08:19.620 align:start position:0% Okay so 00:08:19.620 --> 00:08:21.830 align:start position:0% Okay so why<00:08:19.979> do<00:08:20.220> we<00:08:20.280> like<00:08:20.460> gossip<00:08:20.879> stuff<00:08:21.060> or<00:08:21.419> why<00:08:21.539> do<00:08:21.720> we 00:08:21.830 --> 00:08:21.840 align:start position:0% why do we like gossip stuff or why do we 00:08:21.840 --> 00:08:24.589 align:start position:0% why do we like gossip stuff or why do we like<00:08:22.020> the<00:08:22.319> way<00:08:22.440> we<00:08:22.680> do<00:08:22.800> this<00:08:23.039> uh 00:08:24.589 --> 00:08:24.599 align:start position:0% like the way we do this uh 00:08:24.599 --> 00:08:27.589 align:start position:0% like the way we do this uh this<00:08:25.259> message<00:08:25.500> propagation<00:08:26.160> so<00:08:27.000> it<00:08:27.180> makes<00:08:27.360> for 00:08:27.589 --> 00:08:27.599 align:start position:0% this message propagation so it makes for 00:08:27.599 --> 00:08:29.930 align:start position:0% this message propagation so it makes for a<00:08:27.780> very<00:08:27.900> robust<00:08:28.379> Network<00:08:28.740> in<00:08:29.460> the<00:08:29.580> sense<00:08:29.759> that 00:08:29.930 --> 00:08:29.940 align:start position:0% a very robust Network in the sense that 00:08:29.940 --> 00:08:32.089 align:start position:0% a very robust Network in the sense that we<00:08:30.120> are<00:08:30.300> sure<00:08:30.479> that<00:08:30.900> if<00:08:31.379> we<00:08:31.500> publish<00:08:31.800> a<00:08:31.979> message 00:08:32.089 --> 00:08:32.099 align:start position:0% we are sure that if we publish a message 00:08:32.099 --> 00:08:35.209 align:start position:0% we are sure that if we publish a message and<00:08:32.459> we<00:08:32.640> have<00:08:32.820> this<00:08:33.360> kind<00:08:33.539> of<00:08:33.719> topology<00:08:34.620> the 00:08:35.209 --> 00:08:35.219 align:start position:0% and we have this kind of topology the 00:08:35.219 --> 00:08:36.529 align:start position:0% and we have this kind of topology the message<00:08:35.339> is<00:08:35.580> going<00:08:35.760> to<00:08:35.880> reach<00:08:36.180> all<00:08:36.360> other 00:08:36.529 --> 00:08:36.539 align:start position:0% message is going to reach all other 00:08:36.539 --> 00:08:38.990 align:start position:0% message is going to reach all other nodes<00:08:36.899> in<00:08:37.200> the<00:08:37.320> network<00:08:37.500> in<00:08:37.860> a<00:08:37.919> timely<00:08:38.219> manner 00:08:38.990 --> 00:08:39.000 align:start position:0% nodes in the network in a timely manner 00:08:39.000 --> 00:08:42.130 align:start position:0% nodes in the network in a timely manner we<00:08:39.539> also<00:08:39.839> know<00:08:40.080> that<00:08:40.440> we<00:08:41.099> have<00:08:41.279> low<00:08:41.580> message 00:08:42.130 --> 00:08:42.140 align:start position:0% we also know that we have low message 00:08:42.140 --> 00:08:45.250 align:start position:0% we also know that we have low message latency<00:08:43.140> does<00:08:43.740> mean<00:08:43.979> that<00:08:44.399> means 00:08:45.250 --> 00:08:45.260 align:start position:0% latency does mean that means 00:08:45.260 --> 00:08:49.009 align:start position:0% latency does mean that means the<00:08:46.260> time<00:08:46.440> that<00:08:46.860> hap<00:08:47.160> the<00:08:47.640> is<00:08:48.180> spent<00:08:48.779> between 00:08:49.009 --> 00:08:49.019 align:start position:0% the time that hap the is spent between 00:08:49.019 --> 00:08:51.170 align:start position:0% the time that hap the is spent between the<00:08:49.680> creation<00:08:49.980> of<00:08:50.160> the<00:08:50.399> message<00:08:50.580> in<00:08:51.060> the 00:08:51.170 --> 00:08:51.180 align:start position:0% the creation of the message in the 00:08:51.180 --> 00:08:53.690 align:start position:0% the creation of the message in the source<00:08:51.540> node<00:08:51.720> to<00:08:52.380> when<00:08:52.620> you<00:08:52.800> receive<00:08:53.100> it<00:08:53.220> is 00:08:53.690 --> 00:08:53.700 align:start position:0% source node to when you receive it is 00:08:53.700 --> 00:08:56.329 align:start position:0% source node to when you receive it is not<00:08:54.000> very<00:08:54.839> long<00:08:55.019> and<00:08:55.320> this<00:08:55.560> is<00:08:55.680> as<00:08:56.100> I<00:08:56.279> was 00:08:56.329 --> 00:08:56.339 align:start position:0% not very long and this is as I was 00:08:56.339 --> 00:09:00.170 align:start position:0% not very long and this is as I was saying<00:08:56.519> because<00:08:56.760> of<00:08:57.120> uh<00:08:57.959> lower<00:08:58.459> paths<00:08:59.459> smaller 00:09:00.170 --> 00:09:00.180 align:start position:0% saying because of uh lower paths smaller 00:09:00.180 --> 00:09:03.110 align:start position:0% saying because of uh lower paths smaller paths<00:09:00.540> lower<00:09:00.779> Hoops<00:09:01.260> but<00:09:01.980> then<00:09:02.160> again<00:09:02.399> we<00:09:02.940> have 00:09:03.110 --> 00:09:03.120 align:start position:0% paths lower Hoops but then again we have 00:09:03.120 --> 00:09:06.650 align:start position:0% paths lower Hoops but then again we have a<00:09:03.360> lot<00:09:03.480> of<00:09:03.660> duplicates<00:09:04.560> and<00:09:05.339> these<00:09:06.060> redundancy 00:09:06.650 --> 00:09:06.660 align:start position:0% a lot of duplicates and these redundancy 00:09:06.660 --> 00:09:08.449 align:start position:0% a lot of duplicates and these redundancy results<00:09:06.839> in<00:09:07.080> higher<00:09:07.380> boundaries 00:09:08.449 --> 00:09:08.459 align:start position:0% results in higher boundaries 00:09:08.459 --> 00:09:11.930 align:start position:0% results in higher boundaries this<00:09:09.060> is<00:09:09.120> a<00:09:09.300> graph<00:09:09.480> that<00:09:10.440> we<00:09:10.680> have<00:09:10.980> for<00:09:11.519> nodes 00:09:11.930 --> 00:09:11.940 align:start position:0% this is a graph that we have for nodes 00:09:11.940 --> 00:09:14.329 align:start position:0% this is a graph that we have for nodes so<00:09:12.600> this<00:09:12.839> is<00:09:12.959> like<00:09:13.140> real<00:09:13.380> data 00:09:14.329 --> 00:09:14.339 align:start position:0% so this is like real data 00:09:14.339 --> 00:09:17.750 align:start position:0% so this is like real data for<00:09:14.820> the<00:09:15.060> gossips<00:09:15.300> of<00:09:15.420> duplicates<00:09:16.019> now 00:09:17.750 --> 00:09:17.760 align:start position:0% for the gossips of duplicates now 00:09:17.760 --> 00:09:19.430 align:start position:0% for the gossips of duplicates now this<00:09:18.240> is<00:09:18.300> going<00:09:18.480> to<00:09:18.600> be<00:09:18.660> weird<00:09:18.839> but<00:09:19.080> I'm<00:09:19.260> going 00:09:19.430 --> 00:09:19.440 align:start position:0% this is going to be weird but I'm going 00:09:19.440 --> 00:09:21.530 align:start position:0% this is going to be weird but I'm going to<00:09:19.560> ask<00:09:19.680> you<00:09:19.860> to<00:09:20.100> focus<00:09:20.339> on 00:09:21.530 --> 00:09:21.540 align:start position:0% to ask you to focus on 00:09:21.540 --> 00:09:25.070 align:start position:0% to ask you to focus on this<00:09:22.500> number<00:09:22.680> the<00:09:23.160> beacon<00:09:23.519> block<00:09:23.720> so<00:09:24.720> we<00:09:24.959> know 00:09:25.070 --> 00:09:25.080 align:start position:0% this number the beacon block so we know 00:09:25.080 --> 00:09:29.449 align:start position:0% this number the beacon block so we know we<00:09:25.320> need<00:09:25.560> to<00:09:25.680> publish<00:09:26.279> one<00:09:27.019> block<00:09:28.019> each<00:09:28.920> slot 00:09:29.449 --> 00:09:29.459 align:start position:0% we need to publish one block each slot 00:09:29.459 --> 00:09:32.150 align:start position:0% we need to publish one block each slot so<00:09:30.420> we<00:09:30.600> know<00:09:30.899> for<00:09:31.260> this<00:09:31.440> topic<00:09:31.800> we<00:09:32.040> are 00:09:32.150 --> 00:09:32.160 align:start position:0% so we know for this topic we are 00:09:32.160 --> 00:09:34.070 align:start position:0% so we know for this topic we are supposed<00:09:32.279> to<00:09:32.399> receive<00:09:32.820> a<00:09:33.420> single<00:09:33.660> unique 00:09:34.070 --> 00:09:34.080 align:start position:0% supposed to receive a single unique 00:09:34.080 --> 00:09:37.910 align:start position:0% supposed to receive a single unique message<00:09:34.519> however<00:09:35.519> we<00:09:36.300> are<00:09:36.480> getting<00:09:36.720> six<00:09:37.500> or 00:09:37.910 --> 00:09:37.920 align:start position:0% message however we are getting six or 00:09:37.920 --> 00:09:40.610 align:start position:0% message however we are getting six or seven<00:09:38.160> messages<00:09:38.600> across<00:09:39.600> the<00:09:39.720> network<00:09:39.899> that 00:09:40.610 --> 00:09:40.620 align:start position:0% seven messages across the network that 00:09:40.620 --> 00:09:42.170 align:start position:0% seven messages across the network that means<00:09:40.920> an<00:09:41.100> application<00:09:41.459> an<00:09:41.700> amplification 00:09:42.170 --> 00:09:42.180 align:start position:0% means an application an amplification 00:09:42.180 --> 00:09:44.930 align:start position:0% means an application an amplification factor<00:09:42.660> of<00:09:42.839> about<00:09:43.019> seven<00:09:43.380> so<00:09:44.220> imagine<00:09:44.399> what 00:09:44.930 --> 00:09:44.940 align:start position:0% factor of about seven so imagine what 00:09:44.940 --> 00:09:47.570 align:start position:0% factor of about seven so imagine what happens<00:09:45.180> if<00:09:46.080> we<00:09:46.260> were<00:09:46.440> able<00:09:46.800> to<00:09:47.040> reduce<00:09:47.220> that 00:09:47.570 --> 00:09:47.580 align:start position:0% happens if we were able to reduce that 00:09:47.580 --> 00:09:50.750 align:start position:0% happens if we were able to reduce that kind<00:09:47.760> of<00:09:47.820> duplicates<00:09:48.839> that<00:09:49.500> was<00:09:49.740> like<00:09:50.220> a<00:09:50.399> huge 00:09:50.750 --> 00:09:50.760 align:start position:0% kind of duplicates that was like a huge 00:09:50.760 --> 00:09:52.430 align:start position:0% kind of duplicates that was like a huge huge<00:09:51.300> gain<00:09:51.540> there 00:09:52.430 --> 00:09:52.440 align:start position:0% huge gain there 00:09:52.440 --> 00:09:55.970 align:start position:0% huge gain there okay<00:09:52.920> so<00:09:53.279> a<00:09:53.700> summary<00:09:54.000> of<00:09:54.959> the<00:09:55.440> current<00:09:55.620> state 00:09:55.970 --> 00:09:55.980 align:start position:0% okay so a summary of the current state 00:09:55.980 --> 00:09:58.430 align:start position:0% okay so a summary of the current state so<00:09:56.760> bandwidth<00:09:57.360> is<00:09:57.480> proportional<00:09:57.959> to<00:09:58.200> the 00:09:58.430 --> 00:09:58.440 align:start position:0% so bandwidth is proportional to the 00:09:58.440 --> 00:10:01.370 align:start position:0% so bandwidth is proportional to the number<00:09:58.620> of<00:09:58.860> validators<00:09:59.580> I<00:09:59.820> know<00:10:00.000> it<00:10:00.120> has<00:10:00.300> H<00:10:01.080> is 00:10:01.370 --> 00:10:01.380 align:start position:0% number of validators I know it has H is 00:10:01.380 --> 00:10:04.430 align:start position:0% number of validators I know it has H is going<00:10:01.560> to<00:10:01.740> speak<00:10:02.519> about<00:10:02.700> how<00:10:03.360> we<00:10:03.600> intend<00:10:04.260> to 00:10:04.430 --> 00:10:04.440 align:start position:0% going to speak about how we intend to 00:10:04.440 --> 00:10:05.810 align:start position:0% going to speak about how we intend to tackle<00:10:04.800> this 00:10:05.810 --> 00:10:05.820 align:start position:0% tackle this 00:10:05.820 --> 00:10:07.370 align:start position:0% tackle this and<00:10:06.420> the<00:10:06.660> other<00:10:06.720> one<00:10:06.899> is<00:10:07.080> the<00:10:07.260> high 00:10:07.370 --> 00:10:07.380 align:start position:0% and the other one is the high 00:10:07.380 --> 00:10:09.470 align:start position:0% and the other one is the high amplification<00:10:07.860> in<00:10:08.160> Gossip<00:10:08.580> so<00:10:08.760> how<00:10:09.240> are<00:10:09.360> you 00:10:09.470 --> 00:10:09.480 align:start position:0% amplification in Gossip so how are you 00:10:09.480 --> 00:10:13.430 align:start position:0% amplification in Gossip so how are you going<00:10:09.600> to<00:10:09.779> do<00:10:10.019> to<00:10:10.920> reduce<00:10:11.540> duplicates<00:10:12.540> without 00:10:13.430 --> 00:10:13.440 align:start position:0% going to do to reduce duplicates without 00:10:13.440 --> 00:10:16.430 align:start position:0% going to do to reduce duplicates without harming<00:10:14.040> the<00:10:14.220> network<00:10:14.459> so<00:10:15.420> I'm<00:10:15.899> going<00:10:16.260> to 00:10:16.430 --> 00:10:16.440 align:start position:0% harming the network so I'm going to 00:10:16.440 --> 00:10:20.269 align:start position:0% harming the network so I'm going to leave<00:10:16.920> Ash<00:10:17.580> to<00:10:17.880> continue<00:10:18.000> this<00:10:18.360> talk 00:10:20.269 --> 00:10:20.279 align:start position:0% leave Ash to continue this talk 00:10:20.279 --> 00:10:25.790 align:start position:0% leave Ash to continue this talk foreign 00:10:25.790 --> 00:10:25.800 align:start position:0% 00:10:25.800 --> 00:10:28.250 align:start position:0% yeah<00:10:26.279> thanks<00:10:26.519> Diva<00:10:26.940> so<00:10:27.180> I'm<00:10:27.420> gonna<00:10:27.540> try<00:10:28.140> and 00:10:28.250 --> 00:10:28.260 align:start position:0% yeah thanks Diva so I'm gonna try and 00:10:28.260 --> 00:10:30.170 align:start position:0% yeah thanks Diva so I'm gonna try and have<00:10:28.440> a<00:10:28.620> crack<00:10:28.800> at<00:10:29.100> explaining<00:10:29.640> how<00:10:29.880> we<00:10:30.060> can 00:10:30.170 --> 00:10:30.180 align:start position:0% have a crack at explaining how we can 00:10:30.180 --> 00:10:32.509 align:start position:0% have a crack at explaining how we can potentially<00:10:30.660> reduce<00:10:30.839> some<00:10:31.200> of<00:10:31.320> these<00:10:31.500> so<00:10:32.220> I'm 00:10:32.509 --> 00:10:32.519 align:start position:0% potentially reduce some of these so I'm 00:10:32.519 --> 00:10:33.889 align:start position:0% potentially reduce some of these so I'm Australian<00:10:32.940> and<00:10:33.240> I<00:10:33.360> can<00:10:33.480> see<00:10:33.600> a<00:10:33.779> few 00:10:33.889 --> 00:10:33.899 align:start position:0% Australian and I can see a few 00:10:33.899 --> 00:10:35.449 align:start position:0% Australian and I can see a few Australians<00:10:34.260> in<00:10:34.440> the<00:10:34.560> audience<00:10:34.800> I<00:10:35.279> think 00:10:35.449 --> 00:10:35.459 align:start position:0% Australians in the audience I think 00:10:35.459 --> 00:10:37.250 align:start position:0% Australians in the audience I think they'll<00:10:35.640> agree<00:10:35.880> with<00:10:36.120> me<00:10:36.300> that<00:10:36.779> we<00:10:37.140> have 00:10:37.250 --> 00:10:37.260 align:start position:0% they'll agree with me that we have 00:10:37.260 --> 00:10:39.230 align:start position:0% they'll agree with me that we have terrible<00:10:37.620> internet<00:10:37.860> like<00:10:38.580> ridiculous 00:10:39.230 --> 00:10:39.240 align:start position:0% terrible internet like ridiculous 00:10:39.240 --> 00:10:42.590 align:start position:0% terrible internet like ridiculous internet<00:10:39.480> I<00:10:40.200> run<00:10:40.440> a<00:10:41.220> validator<00:10:41.700> at<00:10:42.000> home<00:10:42.120> and 00:10:42.590 --> 00:10:42.600 align:start position:0% internet I run a validator at home and 00:10:42.600 --> 00:10:44.750 align:start position:0% internet I run a validator at home and someone<00:10:42.839> that<00:10:43.320> watches<00:10:43.800> Netflix<00:10:44.040> in<00:10:44.579> another 00:10:44.750 --> 00:10:44.760 align:start position:0% someone that watches Netflix in another 00:10:44.760 --> 00:10:48.050 align:start position:0% someone that watches Netflix in another room<00:10:45.060> causes<00:10:45.600> me<00:10:45.720> to<00:10:45.839> lose<00:10:45.959> attestations<00:10:46.500> so<00:10:47.399> I 00:10:48.050 --> 00:10:48.060 align:start position:0% room causes me to lose attestations so I 00:10:48.060 --> 00:10:49.610 align:start position:0% room causes me to lose attestations so I as<00:10:48.360> a<00:10:48.540> disclaimer<00:10:48.959> I<00:10:49.200> have<00:10:49.320> a<00:10:49.440> personal 00:10:49.610 --> 00:10:49.620 align:start position:0% as a disclaimer I have a personal 00:10:49.620 --> 00:10:51.350 align:start position:0% as a disclaimer I have a personal Vendetta<00:10:50.279> to<00:10:50.459> try<00:10:50.579> and<00:10:50.700> actually<00:10:50.880> reduce<00:10:51.120> this 00:10:51.350 --> 00:10:51.360 align:start position:0% Vendetta to try and actually reduce this 00:10:51.360 --> 00:10:52.850 align:start position:0% Vendetta to try and actually reduce this bandwidth<00:10:51.779> so<00:10:51.959> that<00:10:52.019> I<00:10:52.140> stop<00:10:52.260> losing<00:10:52.560> out<00:10:52.680> of 00:10:52.850 --> 00:10:52.860 align:start position:0% bandwidth so that I stop losing out of 00:10:52.860 --> 00:10:56.329 align:start position:0% bandwidth so that I stop losing out of stations<00:10:53.579> yeah 00:10:56.329 --> 00:10:56.339 align:start position:0% 00:10:56.339 --> 00:10:59.569 align:start position:0% so<00:10:57.240> there's<00:10:57.660> probably<00:10:58.140> two<00:10:58.860> solutions<00:10:59.339> we 00:10:59.569 --> 00:10:59.579 align:start position:0% so there's probably two solutions we 00:10:59.579 --> 00:11:00.889 align:start position:0% so there's probably two solutions we have<00:10:59.700> to<00:10:59.820> these<00:11:00.060> kinds<00:11:00.300> of<00:11:00.300> problems<00:11:00.600> which<00:11:00.720> I 00:11:00.889 --> 00:11:00.899 align:start position:0% have to these kinds of problems which I 00:11:00.899 --> 00:11:02.030 align:start position:0% have to these kinds of problems which I just<00:11:00.959> want<00:11:01.079> to<00:11:01.260> kind<00:11:01.380> of<00:11:01.500> briefly<00:11:01.680> touch<00:11:01.860> on 00:11:02.030 --> 00:11:02.040 align:start position:0% just want to kind of briefly touch on 00:11:02.040 --> 00:11:03.710 align:start position:0% just want to kind of briefly touch on and<00:11:02.220> give<00:11:02.339> you<00:11:02.459> a<00:11:02.640> feel<00:11:03.120> for<00:11:03.360> what<00:11:03.600> we're 00:11:03.710 --> 00:11:03.720 align:start position:0% and give you a feel for what we're 00:11:03.720 --> 00:11:05.870 align:start position:0% and give you a feel for what we're trying<00:11:03.899> to<00:11:04.079> work<00:11:04.260> on<00:11:04.380> one<00:11:04.980> of<00:11:05.160> them<00:11:05.279> is<00:11:05.640> called 00:11:05.870 --> 00:11:05.880 align:start position:0% trying to work on one of them is called 00:11:05.880 --> 00:11:08.449 align:start position:0% trying to work on one of them is called minimizing<00:11:06.480> topic<00:11:07.019> subscriptions<00:11:07.620> let<00:11:08.339> me 00:11:08.449 --> 00:11:08.459 align:start position:0% minimizing topic subscriptions let me 00:11:08.459 --> 00:11:09.590 align:start position:0% minimizing topic subscriptions let me try<00:11:08.700> and<00:11:08.760> explain<00:11:08.940> that<00:11:09.180> if<00:11:09.300> you<00:11:09.420> haven't 00:11:09.590 --> 00:11:09.600 align:start position:0% try and explain that if you haven't 00:11:09.600 --> 00:11:11.509 align:start position:0% try and explain that if you haven't already<00:11:10.140> covered<00:11:10.620> some<00:11:10.800> of<00:11:10.920> this<00:11:11.040> kind<00:11:11.399> of 00:11:11.509 --> 00:11:11.519 align:start position:0% already covered some of this kind of 00:11:11.519 --> 00:11:13.610 align:start position:0% already covered some of this kind of stuff<00:11:11.640> before<00:11:11.880> so<00:11:12.240> a<00:11:12.480> validator<00:11:12.839> in<00:11:13.019> an<00:11:13.140> Epoch 00:11:13.610 --> 00:11:13.620 align:start position:0% stuff before so a validator in an Epoch 00:11:13.620 --> 00:11:15.829 align:start position:0% stuff before so a validator in an Epoch needs<00:11:13.920> to<00:11:14.100> do<00:11:14.820> some<00:11:15.000> kind<00:11:15.120> needs<00:11:15.540> to<00:11:15.600> publish 00:11:15.829 --> 00:11:15.839 align:start position:0% needs to do some kind needs to publish 00:11:15.839 --> 00:11:17.329 align:start position:0% needs to do some kind needs to publish the<00:11:15.959> messages<00:11:16.200> on<00:11:16.860> these<00:11:17.040> things<00:11:17.160> called 00:11:17.329 --> 00:11:17.339 align:start position:0% the messages on these things called 00:11:17.339 --> 00:11:19.670 align:start position:0% the messages on these things called subnets<00:11:17.820> in<00:11:18.660> order<00:11:18.779> to<00:11:18.959> do<00:11:19.079> that<00:11:19.200> you<00:11:19.440> need<00:11:19.560> to 00:11:19.670 --> 00:11:19.680 align:start position:0% subnets in order to do that you need to 00:11:19.680 --> 00:11:20.990 align:start position:0% subnets in order to do that you need to have<00:11:19.740> peers<00:11:20.100> to<00:11:20.279> be<00:11:20.339> able<00:11:20.459> to<00:11:20.579> publish<00:11:20.820> those 00:11:20.990 --> 00:11:21.000 align:start position:0% have peers to be able to publish those 00:11:21.000 --> 00:11:22.730 align:start position:0% have peers to be able to publish those messages<00:11:21.180> on<00:11:21.540> those<00:11:21.660> subnets<00:11:22.019> now<00:11:22.560> the 00:11:22.730 --> 00:11:22.740 align:start position:0% messages on those subnets now the 00:11:22.740 --> 00:11:24.650 align:start position:0% messages on those subnets now the problem<00:11:22.860> with<00:11:22.980> this<00:11:23.160> is<00:11:23.339> that<00:11:23.640> peer<00:11:24.240> Discovery 00:11:24.650 --> 00:11:24.660 align:start position:0% problem with this is that peer Discovery 00:11:24.660 --> 00:11:26.870 align:start position:0% problem with this is that peer Discovery is<00:11:25.019> kind<00:11:25.200> of<00:11:25.380> is<00:11:25.560> a<00:11:25.680> slow<00:11:25.980> process<00:11:26.279> it<00:11:26.519> takes<00:11:26.700> a 00:11:26.870 --> 00:11:26.880 align:start position:0% is kind of is a slow process it takes a 00:11:26.880 --> 00:11:28.490 align:start position:0% is kind of is a slow process it takes a while<00:11:26.940> to<00:11:27.180> actually<00:11:27.300> find<00:11:27.540> some<00:11:27.779> peers<00:11:28.140> and 00:11:28.490 --> 00:11:28.500 align:start position:0% while to actually find some peers and 00:11:28.500 --> 00:11:30.230 align:start position:0% while to actually find some peers and it's<00:11:28.620> even<00:11:28.800> harder<00:11:29.160> to<00:11:29.279> find<00:11:29.399> a<00:11:29.640> peer<00:11:29.940> on<00:11:30.120> a 00:11:30.230 --> 00:11:30.240 align:start position:0% it's even harder to find a peer on a 00:11:30.240 --> 00:11:32.449 align:start position:0% it's even harder to find a peer on a specific<00:11:30.480> subnet<00:11:30.959> that<00:11:31.200> you<00:11:31.320> need<00:11:31.500> to<00:11:32.160> publish 00:11:32.449 --> 00:11:32.459 align:start position:0% specific subnet that you need to publish 00:11:32.459 --> 00:11:34.550 align:start position:0% specific subnet that you need to publish an<00:11:32.579> attestation<00:11:33.060> so<00:11:33.720> the<00:11:33.899> problem<00:11:34.079> we've<00:11:34.380> got 00:11:34.550 --> 00:11:34.560 align:start position:0% an attestation so the problem we've got 00:11:34.560 --> 00:11:37.910 align:start position:0% an attestation so the problem we've got essentially<00:11:35.100> is<00:11:35.940> that<00:11:36.480> we<00:11:36.720> need<00:11:36.959> a<00:11:37.440> stable<00:11:37.740> set 00:11:37.910 --> 00:11:37.920 align:start position:0% essentially is that we need a stable set 00:11:37.920 --> 00:11:40.009 align:start position:0% essentially is that we need a stable set of<00:11:38.100> subnet<00:11:38.459> a<00:11:38.760> stable<00:11:38.940> set<00:11:39.120> of<00:11:39.300> pairs<00:11:39.720> that 00:11:40.009 --> 00:11:40.019 align:start position:0% of subnet a stable set of pairs that 00:11:40.019 --> 00:11:41.930 align:start position:0% of subnet a stable set of pairs that exist<00:11:40.260> on<00:11:40.440> each<00:11:40.620> subnet<00:11:41.040> that<00:11:41.519> we<00:11:41.700> can<00:11:41.820> find 00:11:41.930 --> 00:11:41.940 align:start position:0% exist on each subnet that we can find 00:11:41.940 --> 00:11:43.550 align:start position:0% exist on each subnet that we can find them<00:11:42.120> easily<00:11:42.540> when<00:11:42.779> we<00:11:42.899> need<00:11:43.019> to<00:11:43.140> publish<00:11:43.380> a 00:11:43.550 --> 00:11:43.560 align:start position:0% them easily when we need to publish a 00:11:43.560 --> 00:11:46.550 align:start position:0% them easily when we need to publish a message<00:11:43.740> so<00:11:44.459> it's<00:11:44.579> not<00:11:44.820> really<00:11:45.120> an<00:11:45.660> uh<00:11:46.200> an<00:11:46.440> easy 00:11:46.550 --> 00:11:46.560 align:start position:0% message so it's not really an uh an easy 00:11:46.560 --> 00:11:48.769 align:start position:0% message so it's not really an uh an easy problem<00:11:46.800> to<00:11:47.100> solve<00:11:47.339> the<00:11:48.060> the<00:11:48.240> way<00:11:48.480> that<00:11:48.600> we 00:11:48.769 --> 00:11:48.779 align:start position:0% problem to solve the the way that we 00:11:48.779 --> 00:11:51.530 align:start position:0% problem to solve the the way that we currently<00:11:49.079> have<00:11:49.519> this<00:11:50.519> solution<00:11:50.880> I<00:11:51.120> guess<00:11:51.240> is 00:11:51.530 --> 00:11:51.540 align:start position:0% currently have this solution I guess is 00:11:51.540 --> 00:11:54.230 align:start position:0% currently have this solution I guess is that<00:11:51.839> every<00:11:52.320> time<00:11:52.500> a<00:11:52.680> validator<00:11:53.100> is<00:11:53.579> attached 00:11:54.230 --> 00:11:54.240 align:start position:0% that every time a validator is attached 00:11:54.240 --> 00:11:56.329 align:start position:0% that every time a validator is attached or<00:11:54.660> sends<00:11:55.260> a<00:11:55.380> message<00:11:55.500> to<00:11:55.740> your<00:11:55.800> beacon<00:11:56.100> node 00:11:56.329 --> 00:11:56.339 align:start position:0% or sends a message to your beacon node 00:11:56.339 --> 00:11:58.490 align:start position:0% or sends a message to your beacon node that<00:11:56.820> Baker<00:11:57.180> note<00:11:57.300> is<00:11:57.480> required<00:11:57.899> to<00:11:58.079> subscribe 00:11:58.490 --> 00:11:58.500 align:start position:0% that Baker note is required to subscribe 00:11:58.500 --> 00:12:00.410 align:start position:0% that Baker note is required to subscribe to<00:11:58.860> one<00:11:59.040> subnet<00:11:59.399> for<00:11:59.640> a<00:11:59.760> very<00:11:59.880> long<00:12:00.060> period<00:12:00.360> of 00:12:00.410 --> 00:12:00.420 align:start position:0% to one subnet for a very long period of 00:12:00.420 --> 00:12:03.350 align:start position:0% to one subnet for a very long period of time<00:12:00.600> it's<00:12:00.839> about<00:12:01.019> 27<00:12:01.560> hours<00:12:01.740> or<00:12:01.980> 256<00:12:02.760> epochs 00:12:03.350 --> 00:12:03.360 align:start position:0% time it's about 27 hours or 256 epochs 00:12:03.360 --> 00:12:05.269 align:start position:0% time it's about 27 hours or 256 epochs so<00:12:03.779> what<00:12:04.019> that<00:12:04.140> means<00:12:04.380> is<00:12:04.500> the<00:12:04.740> more<00:12:04.860> validated 00:12:05.269 --> 00:12:05.279 align:start position:0% so what that means is the more validated 00:12:05.279 --> 00:12:06.769 align:start position:0% so what that means is the more validated you<00:12:05.579> have<00:12:05.700> attached<00:12:06.000> to<00:12:06.120> your<00:12:06.240> Beaker<00:12:06.600> node 00:12:06.769 --> 00:12:06.779 align:start position:0% you have attached to your Beaker node 00:12:06.779 --> 00:12:08.630 align:start position:0% you have attached to your Beaker node the<00:12:07.260> more<00:12:07.380> subnets<00:12:07.800> you<00:12:08.040> need<00:12:08.160> to<00:12:08.279> subscribe 00:12:08.630 --> 00:12:08.640 align:start position:0% the more subnets you need to subscribe 00:12:08.640 --> 00:12:10.910 align:start position:0% the more subnets you need to subscribe to<00:12:08.820> and<00:12:09.480> subscribing<00:12:09.959> to<00:12:10.079> a<00:12:10.200> subnet<00:12:10.560> means 00:12:10.910 --> 00:12:10.920 align:start position:0% to and subscribing to a subnet means 00:12:10.920 --> 00:12:12.170 align:start position:0% to and subscribing to a subnet means that<00:12:10.980> you<00:12:11.160> have<00:12:11.279> to<00:12:11.459> get<00:12:11.640> all<00:12:11.820> of<00:12:11.940> the<00:12:12.060> messages 00:12:12.170 --> 00:12:12.180 align:start position:0% that you have to get all of the messages 00:12:12.180 --> 00:12:14.090 align:start position:0% that you have to get all of the messages on<00:12:12.540> that<00:12:12.660> subnet<00:12:13.019> you<00:12:13.260> need<00:12:13.380> to<00:12:13.500> verify<00:12:13.860> those 00:12:14.090 --> 00:12:14.100 align:start position:0% on that subnet you need to verify those 00:12:14.100 --> 00:12:15.350 align:start position:0% on that subnet you need to verify those messages<00:12:14.279> and<00:12:14.519> then<00:12:14.700> you<00:12:14.760> need<00:12:14.940> to<00:12:15.060> send<00:12:15.180> them 00:12:15.350 --> 00:12:15.360 align:start position:0% messages and then you need to send them 00:12:15.360 --> 00:12:17.449 align:start position:0% messages and then you need to send them on<00:12:15.660> to<00:12:15.779> other<00:12:16.079> peers<00:12:16.500> so<00:12:16.920> you're<00:12:17.040> doing<00:12:17.220> this 00:12:17.449 --> 00:12:17.459 align:start position:0% on to other peers so you're doing this 00:12:17.459 --> 00:12:19.069 align:start position:0% on to other peers so you're doing this there's<00:12:17.880> a<00:12:18.060> lot<00:12:18.120> of<00:12:18.240> bandwidth<00:12:18.660> and<00:12:18.779> a<00:12:18.899> lot<00:12:18.959> of 00:12:19.069 --> 00:12:19.079 align:start position:0% there's a lot of bandwidth and a lot of 00:12:19.079 --> 00:12:21.110 align:start position:0% there's a lot of bandwidth and a lot of processing<00:12:19.519> so<00:12:20.519> essentially<00:12:20.880> you're 00:12:21.110 --> 00:12:21.120 align:start position:0% processing so essentially you're 00:12:21.120 --> 00:12:22.910 align:start position:0% processing so essentially you're supporting<00:12:21.540> the<00:12:21.660> network<00:12:21.839> at<00:12:22.440> the<00:12:22.560> cost<00:12:22.680> of 00:12:22.910 --> 00:12:22.920 align:start position:0% supporting the network at the cost of 00:12:22.920 --> 00:12:24.710 align:start position:0% supporting the network at the cost of bandwidth<00:12:23.399> on<00:12:23.519> your<00:12:23.640> node<00:12:23.820> so<00:12:24.000> you're<00:12:24.240> kind<00:12:24.600> of 00:12:24.710 --> 00:12:24.720 align:start position:0% bandwidth on your node so you're kind of 00:12:24.720 --> 00:12:28.970 align:start position:0% bandwidth on your node so you're kind of being<00:12:24.839> like<00:12:25.079> a<00:12:25.320> good<00:12:25.620> actor<00:12:26.420> so<00:12:27.420> there's 00:12:28.970 --> 00:12:28.980 align:start position:0% being like a good actor so there's 00:12:28.980 --> 00:12:30.710 align:start position:0% being like a good actor so there's a<00:12:29.399> number<00:12:29.640> of<00:12:29.760> downsides<00:12:30.180> to<00:12:30.300> this<00:12:30.420> approach 00:12:30.710 --> 00:12:30.720 align:start position:0% a number of downsides to this approach 00:12:30.720 --> 00:12:33.170 align:start position:0% a number of downsides to this approach one<00:12:31.140> is<00:12:31.380> that<00:12:31.560> it's<00:12:31.680> not<00:12:31.860> enforceable<00:12:32.339> so<00:12:32.940> what 00:12:33.170 --> 00:12:33.180 align:start position:0% one is that it's not enforceable so what 00:12:33.180 --> 00:12:36.470 align:start position:0% one is that it's not enforceable so what that<00:12:33.300> means<00:12:33.540> is<00:12:33.720> you<00:12:34.440> as<00:12:35.279> a<00:12:35.399> beacon<00:12:35.760> node<00:12:36.060> you 00:12:36.470 --> 00:12:36.480 align:start position:0% that means is you as a beacon node you 00:12:36.480 --> 00:12:37.790 align:start position:0% that means is you as a beacon node you can<00:12:36.600> essentially<00:12:36.839> lie<00:12:37.140> to<00:12:37.200> us<00:12:37.320> and<00:12:37.440> you<00:12:37.560> say<00:12:37.680> I 00:12:37.790 --> 00:12:37.800 align:start position:0% can essentially lie to us and you say I 00:12:37.800 --> 00:12:39.050 align:start position:0% can essentially lie to us and you say I don't<00:12:37.980> have<00:12:38.100> any<00:12:38.220> validators<00:12:38.640> even<00:12:38.880> though 00:12:39.050 --> 00:12:39.060 align:start position:0% don't have any validators even though 00:12:39.060 --> 00:12:40.490 align:start position:0% don't have any validators even though you've<00:12:39.180> got<00:12:39.300> like<00:12:39.480> 2<00:12:39.839> 000<00:12:39.899> attached<00:12:40.320> to<00:12:40.380> you 00:12:40.490 --> 00:12:40.500 align:start position:0% you've got like 2 000 attached to you 00:12:40.500 --> 00:12:42.170 align:start position:0% you've got like 2 000 attached to you and<00:12:40.980> you<00:12:41.160> just<00:12:41.279> don't<00:12:41.459> subscribe<00:12:41.760> to<00:12:41.940> any 00:12:42.170 --> 00:12:42.180 align:start position:0% and you just don't subscribe to any 00:12:42.180 --> 00:12:44.150 align:start position:0% and you just don't subscribe to any long-lived<00:12:42.779> subnet<00:12:43.079> so<00:12:43.260> you<00:12:43.440> don't<00:12:43.560> consume 00:12:44.150 --> 00:12:44.160 align:start position:0% long-lived subnet so you don't consume 00:12:44.160 --> 00:12:45.530 align:start position:0% long-lived subnet so you don't consume any<00:12:44.279> bandwidth<00:12:44.820> so<00:12:45.180> you<00:12:45.300> kind<00:12:45.480> of 00:12:45.530 --> 00:12:45.540 align:start position:0% any bandwidth so you kind of 00:12:45.540 --> 00:12:46.850 align:start position:0% any bandwidth so you kind of incentivized<00:12:46.079> to<00:12:46.200> do<00:12:46.320> this<00:12:46.380> and<00:12:46.560> there's<00:12:46.680> no 00:12:46.850 --> 00:12:46.860 align:start position:0% incentivized to do this and there's no 00:12:46.860 --> 00:12:48.230 align:start position:0% incentivized to do this and there's no way<00:12:47.040> that<00:12:47.279> any<00:12:47.459> other<00:12:47.639> node<00:12:47.880> on<00:12:48.000> the<00:12:48.120> network 00:12:48.230 --> 00:12:48.240 align:start position:0% way that any other node on the network 00:12:48.240 --> 00:12:49.730 align:start position:0% way that any other node on the network can<00:12:48.480> tell<00:12:48.660> whether<00:12:48.959> you're<00:12:49.139> lying<00:12:49.380> to<00:12:49.500> us<00:12:49.620> or 00:12:49.730 --> 00:12:49.740 align:start position:0% can tell whether you're lying to us or 00:12:49.740 --> 00:12:52.370 align:start position:0% can tell whether you're lying to us or not<00:12:49.860> the<00:12:50.820> next<00:12:50.940> thing<00:12:51.120> is<00:12:51.420> potentially<00:12:52.079> our 00:12:52.370 --> 00:12:52.380 align:start position:0% not the next thing is potentially our 00:12:52.380 --> 00:12:54.530 align:start position:0% not the next thing is potentially our subnets<00:12:52.800> are<00:12:53.100> oversubscribed<00:12:54.000> we<00:12:54.420> actually 00:12:54.530 --> 00:12:54.540 align:start position:0% subnets are oversubscribed we actually 00:12:54.540 --> 00:12:56.509 align:start position:0% subnets are oversubscribed we actually have<00:12:54.899> quite<00:12:55.200> an<00:12:55.440> uh<00:12:55.860> a<00:12:56.100> large<00:12:56.220> number<00:12:56.399> of 00:12:56.509 --> 00:12:56.519 align:start position:0% have quite an uh a large number of 00:12:56.519 --> 00:12:58.490 align:start position:0% have quite an uh a large number of Beaker<00:12:56.940> nodes<00:12:57.060> on<00:12:57.240> mainnet<00:12:57.660> today<00:12:57.779> and<00:12:58.320> when 00:12:58.490 --> 00:12:58.500 align:start position:0% Beaker nodes on mainnet today and when 00:12:58.500 --> 00:13:00.230 align:start position:0% Beaker nodes on mainnet today and when we<00:12:58.620> originally<00:12:59.040> designed<00:12:59.820> this<00:13:00.000> kind<00:13:00.120> of 00:13:00.230 --> 00:13:00.240 align:start position:0% we originally designed this kind of 00:13:00.240 --> 00:13:02.569 align:start position:0% we originally designed this kind of process<00:13:00.480> we<00:13:00.899> we<00:13:01.320> didn't<00:13:01.500> really<00:13:01.800> realize<00:13:02.220> how 00:13:02.569 --> 00:13:02.579 align:start position:0% process we we didn't really realize how 00:13:02.579 --> 00:13:05.389 align:start position:0% process we we didn't really realize how many<00:13:02.760> nodes<00:13:03.420> would<00:13:03.839> be<00:13:04.260> participating<00:13:05.160> in<00:13:05.339> the 00:13:05.389 --> 00:13:05.399 align:start position:0% many nodes would be participating in the 00:13:05.399 --> 00:13:06.530 align:start position:0% many nodes would be participating in the network<00:13:05.519> so<00:13:05.760> potentially<00:13:06.180> we<00:13:06.360> have<00:13:06.420> more 00:13:06.530 --> 00:13:06.540 align:start position:0% network so potentially we have more 00:13:06.540 --> 00:13:08.030 align:start position:0% network so potentially we have more nodes<00:13:06.839> than<00:13:07.019> we<00:13:07.139> need<00:13:07.260> on<00:13:07.620> each<00:13:07.800> of<00:13:07.920> these 00:13:08.030 --> 00:13:08.040 align:start position:0% nodes than we need on each of these 00:13:08.040 --> 00:13:11.449 align:start position:0% nodes than we need on each of these subnets<00:13:08.399> so<00:13:09.000> that<00:13:09.600> would<00:13:09.839> lead<00:13:10.320> us<00:13:10.860> to<00:13:11.160> think 00:13:11.449 --> 00:13:11.459 align:start position:0% subnets so that would lead us to think 00:13:11.459 --> 00:13:12.889 align:start position:0% subnets so that would lead us to think that<00:13:11.579> we<00:13:11.760> have<00:13:11.880> excess<00:13:12.300> bandwidth<00:13:12.720> on<00:13:12.779> the 00:13:12.889 --> 00:13:12.899 align:start position:0% that we have excess bandwidth on the 00:13:12.899 --> 00:13:14.530 align:start position:0% that we have excess bandwidth on the network<00:13:13.019> that<00:13:13.260> potentially<00:13:13.620> we<00:13:13.740> can<00:13:13.920> remove 00:13:14.530 --> 00:13:14.540 align:start position:0% network that potentially we can remove 00:13:14.540 --> 00:13:17.750 align:start position:0% network that potentially we can remove so<00:13:15.540> the<00:13:15.720> idea<00:13:15.959> that's<00:13:16.139> being<00:13:16.320> proposed<00:13:16.800> is<00:13:17.160> why 00:13:17.750 --> 00:13:17.760 align:start position:0% so the idea that's being proposed is why 00:13:17.760 --> 00:13:19.370 align:start position:0% so the idea that's being proposed is why don't<00:13:18.000> just<00:13:18.240> every<00:13:18.540> single<00:13:18.779> Beaker<00:13:19.079> node<00:13:19.200> on 00:13:19.370 --> 00:13:19.380 align:start position:0% don't just every single Beaker node on 00:13:19.380 --> 00:13:21.230 align:start position:0% don't just every single Beaker node on the<00:13:19.500> network<00:13:19.560> subscribe<00:13:20.100> to<00:13:20.339> one<00:13:20.639> or<00:13:21.000> many 00:13:21.230 --> 00:13:21.240 align:start position:0% the network subscribe to one or many 00:13:21.240 --> 00:13:23.930 align:start position:0% the network subscribe to one or many subnets<00:13:21.779> the<00:13:22.680> there's<00:13:23.220> some<00:13:23.459> benefits<00:13:23.820> to 00:13:23.930 --> 00:13:23.940 align:start position:0% subnets the there's some benefits to 00:13:23.940 --> 00:13:26.569 align:start position:0% subnets the there's some benefits to this<00:13:24.120> but<00:13:24.420> the<00:13:25.139> journal<00:13:25.560> discussion<00:13:25.980> is<00:13:26.160> in<00:13:26.339> is 00:13:26.569 --> 00:13:26.579 align:start position:0% this but the journal discussion is in is 00:13:26.579 --> 00:13:30.290 align:start position:0% this but the journal discussion is in is in<00:13:26.820> this<00:13:27.480> um<00:13:27.480> specs<00:13:28.320> repo<00:13:28.680> as<00:13:29.279> an<00:13:29.459> issue<00:13:29.760> so 00:13:30.290 --> 00:13:30.300 align:start position:0% in this um specs repo as an issue so 00:13:30.300 --> 00:13:31.910 align:start position:0% in this um specs repo as an issue so what<00:13:30.480> would<00:13:30.660> the<00:13:30.779> bandwidth<00:13:31.200> graph<00:13:31.560> look<00:13:31.800> like 00:13:31.910 --> 00:13:31.920 align:start position:0% what would the bandwidth graph look like 00:13:31.920 --> 00:13:33.829 align:start position:0% what would the bandwidth graph look like if<00:13:32.160> we<00:13:32.339> did<00:13:32.579> this<00:13:32.760> if<00:13:33.000> one<00:13:33.120> Beaker<00:13:33.540> node<00:13:33.720> were 00:13:33.829 --> 00:13:33.839 align:start position:0% if we did this if one Beaker node were 00:13:33.839 --> 00:13:35.829 align:start position:0% if we did this if one Beaker node were subscribed<00:13:34.079> to<00:13:34.139> one<00:13:34.440> subnet 00:13:35.829 --> 00:13:35.839 align:start position:0% subscribed to one subnet 00:13:35.839 --> 00:13:38.150 align:start position:0% subscribed to one subnet rather<00:13:36.839> than<00:13:37.079> having<00:13:37.380> it<00:13:37.740> for<00:13:37.920> being 00:13:38.150 --> 00:13:38.160 align:start position:0% rather than having it for being 00:13:38.160 --> 00:13:39.889 align:start position:0% rather than having it for being proportional<00:13:38.639> to<00:13:38.820> the<00:13:39.240> number<00:13:39.360> of<00:13:39.480> validators 00:13:39.889 --> 00:13:39.899 align:start position:0% proportional to the number of validators 00:13:39.899 --> 00:13:41.449 align:start position:0% proportional to the number of validators attached<00:13:40.260> to<00:13:40.320> you<00:13:40.440> you<00:13:40.860> would<00:13:41.040> then<00:13:41.160> get<00:13:41.279> this 00:13:41.449 --> 00:13:41.459 align:start position:0% attached to you you would then get this 00:13:41.459 --> 00:13:42.949 align:start position:0% attached to you you would then get this green<00:13:41.639> line<00:13:41.820> on<00:13:42.120> this<00:13:42.240> graph<00:13:42.480> which<00:13:42.720> hopefully 00:13:42.949 --> 00:13:42.959 align:start position:0% green line on this graph which hopefully 00:13:42.959 --> 00:13:44.990 align:start position:0% green line on this graph which hopefully everyone<00:13:43.079> can<00:13:43.380> see<00:13:43.560> and<00:13:44.399> that<00:13:44.639> green<00:13:44.820> line 00:13:44.990 --> 00:13:45.000 align:start position:0% everyone can see and that green line 00:13:45.000 --> 00:13:47.030 align:start position:0% everyone can see and that green line sits<00:13:45.420> at<00:13:45.480> around<00:13:45.660> 500<00:13:46.139> kilobytes<00:13:46.620> a<00:13:46.740> second<00:13:46.860> at 00:13:47.030 --> 00:13:47.040 align:start position:0% sits at around 500 kilobytes a second at 00:13:47.040 --> 00:13:48.290 align:start position:0% sits at around 500 kilobytes a second at the<00:13:47.160> moment<00:13:47.279> from<00:13:47.519> what<00:13:47.700> we've<00:13:47.880> what<00:13:48.060> we've 00:13:48.290 --> 00:13:48.300 align:start position:0% the moment from what we've what we've 00:13:48.300 --> 00:13:50.690 align:start position:0% the moment from what we've what we've measured<00:13:49.079> so<00:13:49.500> essentially<00:13:49.860> everybody<00:13:50.279> on<00:13:50.579> the 00:13:50.690 --> 00:13:50.700 align:start position:0% measured so essentially everybody on the 00:13:50.700 --> 00:13:52.490 align:start position:0% measured so essentially everybody on the network<00:13:50.820> that<00:13:51.120> has<00:13:51.240> a<00:13:51.360> validator 00:13:52.490 --> 00:13:52.500 align:start position:0% network that has a validator 00:13:52.500 --> 00:13:54.710 align:start position:0% network that has a validator wins<00:13:53.160> in<00:13:53.519> this<00:13:53.639> in<00:13:53.880> this<00:13:54.060> scenario<00:13:54.300> except<00:13:54.600> for 00:13:54.710 --> 00:13:54.720 align:start position:0% wins in this in this scenario except for 00:13:54.720 --> 00:13:56.389 align:start position:0% wins in this in this scenario except for those<00:13:54.899> that<00:13:55.079> have<00:13:55.260> one<00:13:55.440> so<00:13:55.740> sorry<00:13:56.040> for<00:13:56.279> the 00:13:56.389 --> 00:13:56.399 align:start position:0% those that have one so sorry for the 00:13:56.399 --> 00:13:57.949 align:start position:0% those that have one so sorry for the people<00:13:56.519> that<00:13:56.880> only<00:13:57.060> have<00:13:57.240> one<00:13:57.360> validator<00:13:57.779> in 00:13:57.949 --> 00:13:57.959 align:start position:0% people that only have one validator in 00:13:57.959 --> 00:14:00.290 align:start position:0% people that only have one validator in this<00:13:58.079> room<00:13:58.200> you<00:13:58.920> guys<00:13:58.980> then<00:13:59.220> have<00:13:59.459> to<00:13:59.639> your 00:14:00.290 --> 00:14:00.300 align:start position:0% this room you guys then have to your 00:14:00.300 --> 00:14:01.910 align:start position:0% this room you guys then have to your bandwidth<00:14:00.720> will<00:14:00.839> increase<00:14:00.959> by<00:14:01.200> about<00:14:01.320> 500<00:14:01.740> to 00:14:01.910 --> 00:14:01.920 align:start position:0% bandwidth will increase by about 500 to 00:14:01.920 --> 00:14:04.790 align:start position:0% bandwidth will increase by about 500 to 100<00:14:02.100> kilobytes<00:14:02.839> the<00:14:03.839> other<00:14:03.959> benefit<00:14:04.380> that<00:14:04.680> we 00:14:04.790 --> 00:14:04.800 align:start position:0% 100 kilobytes the other benefit that we 00:14:04.800 --> 00:14:06.889 align:start position:0% 100 kilobytes the other benefit that we get<00:14:04.920> from<00:14:05.100> this<00:14:05.279> so<00:14:05.880> from<00:14:06.120> a<00:14:06.300> quick<00:14:06.420> scan<00:14:06.720> that 00:14:06.889 --> 00:14:06.899 align:start position:0% get from this so from a quick scan that 00:14:06.899 --> 00:14:09.410 align:start position:0% get from this so from a quick scan that we<00:14:07.019> did<00:14:07.200> of<00:14:07.440> the<00:14:07.620> of<00:14:07.860> the<00:14:08.160> DHT<00:14:08.579> or<00:14:08.880> or<00:14:09.120> the 00:14:09.410 --> 00:14:09.420 align:start position:0% we did of the of the DHT or or the 00:14:09.420 --> 00:14:10.730 align:start position:0% we did of the of the DHT or or the current<00:14:09.540> nodes<00:14:09.839> on<00:14:10.079> the<00:14:10.139> network<00:14:10.260> we<00:14:10.560> found 00:14:10.730 --> 00:14:10.740 align:start position:0% current nodes on the network we found 00:14:10.740 --> 00:14:12.530 align:start position:0% current nodes on the network we found that<00:14:10.920> 57<00:14:11.519> percent 00:14:12.530 --> 00:14:12.540 align:start position:0% that 57 percent 00:14:12.540 --> 00:14:15.410 align:start position:0% that 57 percent of<00:14:13.079> nodes<00:14:13.639> apparently<00:14:14.639> don't<00:14:15.060> have<00:14:15.240> any 00:14:15.410 --> 00:14:15.420 align:start position:0% of nodes apparently don't have any 00:14:15.420 --> 00:14:16.670 align:start position:0% of nodes apparently don't have any validators<00:14:15.899> attached<00:14:16.200> to<00:14:16.260> them<00:14:16.380> so<00:14:16.560> they're 00:14:16.670 --> 00:14:16.680 align:start position:0% validators attached to them so they're 00:14:16.680 --> 00:14:18.290 align:start position:0% validators attached to them so they're either<00:14:16.860> lying<00:14:17.220> to<00:14:17.339> us<00:14:17.459> or<00:14:17.820> they<00:14:17.940> actually 00:14:18.290 --> 00:14:18.300 align:start position:0% either lying to us or they actually 00:14:18.300 --> 00:14:19.670 align:start position:0% either lying to us or they actually don't<00:14:18.540> have<00:14:18.720> validators<00:14:19.139> attached<00:14:19.500> to<00:14:19.560> them 00:14:19.670 --> 00:14:19.680 align:start position:0% don't have validators attached to them 00:14:19.680 --> 00:14:20.509 align:start position:0% don't have validators attached to them and<00:14:19.860> they're<00:14:19.980> not<00:14:20.160> they're<00:14:20.399> not 00:14:20.509 --> 00:14:20.519 align:start position:0% and they're not they're not 00:14:20.519 --> 00:14:22.490 align:start position:0% and they're not they're not participating<00:14:21.000> in<00:14:21.240> any<00:14:21.360> of<00:14:21.480> the<00:14:21.600> subnets<00:14:21.899> so 00:14:22.490 --> 00:14:22.500 align:start position:0% participating in any of the subnets so 00:14:22.500 --> 00:14:24.710 align:start position:0% participating in any of the subnets so if<00:14:22.680> we<00:14:22.860> do<00:14:23.040> Transition<00:14:23.820> over<00:14:24.120> into<00:14:24.360> this<00:14:24.540> state 00:14:24.710 --> 00:14:24.720 align:start position:0% if we do Transition over into this state 00:14:24.720 --> 00:14:25.730 align:start position:0% if we do Transition over into this state they<00:14:24.959> actually<00:14:25.320> have<00:14:25.500> to<00:14:25.620> start 00:14:25.730 --> 00:14:25.740 align:start position:0% they actually have to start 00:14:25.740 --> 00:14:27.050 align:start position:0% they actually have to start participating<00:14:26.220> in<00:14:26.399> helping<00:14:26.639> out<00:14:26.760> and<00:14:26.880> it 00:14:27.050 --> 00:14:27.060 align:start position:0% participating in helping out and it 00:14:27.060 --> 00:14:28.610 align:start position:0% participating in helping out and it lowers<00:14:27.300> the<00:14:27.420> bandwidth<00:14:27.839> for<00:14:28.079> the 00:14:28.610 --> 00:14:28.620 align:start position:0% lowers the bandwidth for the 00:14:28.620 --> 00:14:29.870 align:start position:0% lowers the bandwidth for the institutional<00:14:29.040> stakers<00:14:29.399> or<00:14:29.519> the<00:14:29.639> ones<00:14:29.760> that 00:14:29.870 --> 00:14:29.880 align:start position:0% institutional stakers or the ones that 00:14:29.880 --> 00:14:32.210 align:start position:0% institutional stakers or the ones that have<00:14:30.000> high<00:14:30.240> number<00:14:30.480> of<00:14:30.660> validators<00:14:31.380> yeah<00:14:31.920> so 00:14:32.210 --> 00:14:32.220 align:start position:0% have high number of validators yeah so 00:14:32.220 --> 00:14:33.410 align:start position:0% have high number of validators yeah so essentially<00:14:32.579> all<00:14:32.760> the<00:14:32.880> beaker<00:14:33.120> nodes<00:14:33.300> will 00:14:33.410 --> 00:14:33.420 align:start position:0% essentially all the beaker nodes will 00:14:33.420 --> 00:14:35.449 align:start position:0% essentially all the beaker nodes will now<00:14:33.540> contribute<00:14:33.899> to<00:14:34.200> to<00:14:34.440> doing 00:14:35.449 --> 00:14:35.459 align:start position:0% now contribute to to doing 00:14:35.459 --> 00:14:38.150 align:start position:0% now contribute to to doing um<00:14:35.519> to<00:14:36.060> to<00:14:36.360> helping<00:14:37.200> with<00:14:37.440> this<00:14:37.740> subnet 00:14:38.150 --> 00:14:38.160 align:start position:0% um to to helping with this subnet 00:14:38.160 --> 00:14:40.850 align:start position:0% um to to helping with this subnet stability<00:14:38.579> so<00:14:39.540> it<00:14:40.320> kind<00:14:40.500> of<00:14:40.560> sounds<00:14:40.680> pretty 00:14:40.850 --> 00:14:40.860 align:start position:0% stability so it kind of sounds pretty 00:14:40.860 --> 00:14:43.129 align:start position:0% stability so it kind of sounds pretty good<00:14:41.040> that<00:14:41.160> we<00:14:41.339> get<00:14:41.459> a<00:14:41.760> massive<00:14:42.660> reduction<00:14:42.959> in 00:14:43.129 --> 00:14:43.139 align:start position:0% good that we get a massive reduction in 00:14:43.139 --> 00:14:45.230 align:start position:0% good that we get a massive reduction in bandwidth<00:14:43.620> but<00:14:43.800> there<00:14:44.040> is<00:14:44.220> a<00:14:44.399> cost<00:14:44.519> and<00:14:45.120> the 00:14:45.230 --> 00:14:45.240 align:start position:0% bandwidth but there is a cost and the 00:14:45.240 --> 00:14:48.650 align:start position:0% bandwidth but there is a cost and the cost<00:14:45.420> is<00:14:45.660> how<00:14:46.500> many<00:14:46.680> what<00:14:47.220> is<00:14:47.579> the<00:14:47.699> density<00:14:48.060> of 00:14:48.650 --> 00:14:48.660 align:start position:0% cost is how many what is the density of 00:14:48.660 --> 00:14:51.290 align:start position:0% cost is how many what is the density of of<00:14:49.320> nodes<00:14:49.980> that<00:14:50.220> you<00:14:50.339> can<00:14:50.459> find<00:14:50.639> that<00:14:50.940> exist<00:14:51.180> on 00:14:51.290 --> 00:14:51.300 align:start position:0% of nodes that you can find that exist on 00:14:51.300 --> 00:14:53.150 align:start position:0% of nodes that you can find that exist on these<00:14:51.480> subnets<00:14:51.839> so<00:14:52.260> if<00:14:52.380> no<00:14:52.560> one<00:14:52.680> was<00:14:52.800> subscribe 00:14:53.150 --> 00:14:53.160 align:start position:0% these subnets so if no one was subscribe 00:14:53.160 --> 00:14:54.230 align:start position:0% these subnets so if no one was subscribe to<00:14:53.220> there<00:14:53.399> we<00:14:53.579> wouldn't<00:14:53.639> be<00:14:53.880> able<00:14:54.000> to<00:14:54.060> find 00:14:54.230 --> 00:14:54.240 align:start position:0% to there we wouldn't be able to find 00:14:54.240 --> 00:14:56.150 align:start position:0% to there we wouldn't be able to find those<00:14:54.420> pairs<00:14:54.720> in<00:14:54.839> order<00:14:54.959> to<00:14:55.139> publish<00:14:55.440> publish 00:14:56.150 --> 00:14:56.160 align:start position:0% those pairs in order to publish publish 00:14:56.160 --> 00:14:58.009 align:start position:0% those pairs in order to publish publish our<00:14:56.279> messages<00:14:56.579> on<00:14:56.940> these<00:14:57.060> subnets<00:14:57.420> so<00:14:57.660> we 00:14:58.009 --> 00:14:58.019 align:start position:0% our messages on these subnets so we 00:14:58.019 --> 00:14:59.810 align:start position:0% our messages on these subnets so we still<00:14:58.199> need<00:14:58.380> a<00:14:58.740> decent<00:14:59.040> density<00:14:59.339> so<00:14:59.519> that<00:14:59.639> if 00:14:59.810 --> 00:14:59.820 align:start position:0% still need a decent density so that if 00:14:59.820 --> 00:15:01.370 align:start position:0% still need a decent density so that if you<00:15:00.060> just<00:15:00.180> randomly<00:15:00.540> look<00:15:00.660> through<00:15:00.839> the<00:15:00.959> PSA 00:15:01.370 --> 00:15:01.380 align:start position:0% you just randomly look through the PSA 00:15:01.380 --> 00:15:02.750 align:start position:0% you just randomly look through the PSA you<00:15:01.560> can<00:15:01.680> actually<00:15:01.800> find<00:15:02.040> nodes<00:15:02.459> on<00:15:02.639> those 00:15:02.750 --> 00:15:02.760 align:start position:0% you can actually find nodes on those 00:15:02.760 --> 00:15:04.670 align:start position:0% you can actually find nodes on those subnets<00:15:03.120> and<00:15:03.300> kind<00:15:03.420> of<00:15:03.480> hold<00:15:03.600> on<00:15:03.720> to<00:15:03.899> them<00:15:04.019> and 00:15:04.670 --> 00:15:04.680 align:start position:0% subnets and kind of hold on to them and 00:15:04.680 --> 00:15:07.670 align:start position:0% subnets and kind of hold on to them and so<00:15:04.920> this<00:15:05.220> graph<00:15:05.459> here<00:15:05.639> is<00:15:05.880> a<00:15:06.180> distribution<00:15:06.839> of 00:15:07.670 --> 00:15:07.680 align:start position:0% so this graph here is a distribution of 00:15:07.680 --> 00:15:09.949 align:start position:0% so this graph here is a distribution of the<00:15:08.399> current<00:15:08.519> density<00:15:08.940> and<00:15:09.300> what<00:15:09.600> the<00:15:09.720> density 00:15:09.949 --> 00:15:09.959 align:start position:0% the current density and what the density 00:15:09.959 --> 00:15:11.750 align:start position:0% the current density and what the density would<00:15:10.139> look<00:15:10.320> like<00:15:10.440> if<00:15:10.620> we<00:15:10.800> switch<00:15:10.980> to<00:15:11.399> having 00:15:11.750 --> 00:15:11.760 align:start position:0% would look like if we switch to having 00:15:11.760 --> 00:15:16.129 align:start position:0% would look like if we switch to having one<00:15:12.480> and<00:15:13.139> one<00:15:13.560> big<00:15:13.680> node<00:15:14.160> per<00:15:14.639> one<00:15:15.060> topic<00:15:15.540> so<00:15:16.019> at 00:15:16.129 --> 00:15:16.139 align:start position:0% one and one big node per one topic so at 00:15:16.139 --> 00:15:17.750 align:start position:0% one and one big node per one topic so at the<00:15:16.260> moment<00:15:16.440> it's<00:15:16.800> it<00:15:16.980> looks<00:15:17.279> roughly<00:15:17.579> like 00:15:17.750 --> 00:15:17.760 align:start position:0% the moment it's it looks roughly like 00:15:17.760 --> 00:15:19.850 align:start position:0% the moment it's it looks roughly like eight<00:15:18.240> percent<00:15:18.420> so<00:15:18.839> you<00:15:19.019> randomly<00:15:19.440> pick<00:15:19.620> a 00:15:19.850 --> 00:15:19.860 align:start position:0% eight percent so you randomly pick a 00:15:19.860 --> 00:15:21.110 align:start position:0% eight percent so you randomly pick a node<00:15:20.220> there's<00:15:20.399> an<00:15:20.519> eight<00:15:20.579> percent<00:15:20.760> chance 00:15:21.110 --> 00:15:21.120 align:start position:0% node there's an eight percent chance 00:15:21.120 --> 00:15:23.329 align:start position:0% node there's an eight percent chance that<00:15:21.420> it's<00:15:21.600> going<00:15:21.899> to<00:15:21.959> exist<00:15:22.139> on<00:15:22.380> any<00:15:22.620> given 00:15:23.329 --> 00:15:23.339 align:start position:0% that it's going to exist on any given 00:15:23.339 --> 00:15:25.550 align:start position:0% that it's going to exist on any given subnet<00:15:23.699> if<00:15:24.240> we<00:15:24.360> switch<00:15:24.480> to<00:15:24.720> one<00:15:24.899> Beaker<00:15:25.380> node 00:15:25.550 --> 00:15:25.560 align:start position:0% subnet if we switch to one Beaker node 00:15:25.560 --> 00:15:28.370 align:start position:0% subnet if we switch to one Beaker node per<00:15:25.920> one<00:15:26.399> subnet<00:15:26.880> it<00:15:27.180> drops<00:15:27.600> to<00:15:27.779> about<00:15:27.899> one<00:15:28.199> and 00:15:28.370 --> 00:15:28.380 align:start position:0% per one subnet it drops to about one and 00:15:28.380 --> 00:15:29.990 align:start position:0% per one subnet it drops to about one and a<00:15:28.500> half<00:15:28.500> percent<00:15:28.740> which<00:15:29.339> is<00:15:29.399> one<00:15:29.579> on<00:15:29.760> sixty 00:15:29.990 --> 00:15:30.000 align:start position:0% a half percent which is one on sixty 00:15:30.000 --> 00:15:31.490 align:start position:0% a half percent which is one on sixty four<00:15:30.120> as<00:15:30.300> you<00:15:30.420> would<00:15:30.540> expect 00:15:31.490 --> 00:15:31.500 align:start position:0% four as you would expect 00:15:31.500 --> 00:15:33.350 align:start position:0% four as you would expect um<00:15:31.560> the<00:15:31.860> benefit<00:15:32.040> of<00:15:32.339> that<00:15:32.459> is<00:15:32.880> that<00:15:33.120> it's 00:15:33.350 --> 00:15:33.360 align:start position:0% um the benefit of that is that it's 00:15:33.360 --> 00:15:34.910 align:start position:0% um the benefit of that is that it's configurable<00:15:33.839> we<00:15:34.199> don't<00:15:34.320> have<00:15:34.500> to<00:15:34.620> say<00:15:34.680> one 00:15:34.910 --> 00:15:34.920 align:start position:0% configurable we don't have to say one 00:15:34.920 --> 00:15:36.590 align:start position:0% configurable we don't have to say one bigger<00:15:35.279> node<00:15:35.399> one<00:15:35.579> subnet<00:15:35.940> we<00:15:36.120> can<00:15:36.240> say<00:15:36.420> one 00:15:36.590 --> 00:15:36.600 align:start position:0% bigger node one subnet we can say one 00:15:36.600 --> 00:15:38.210 align:start position:0% bigger node one subnet we can say one Beacon<00:15:36.959> no<00:15:37.139> two<00:15:37.260> subnets<00:15:37.620> one<00:15:37.800> bigger<00:15:38.160> no 00:15:38.210 --> 00:15:38.220 align:start position:0% Beacon no two subnets one bigger no 00:15:38.220 --> 00:15:40.129 align:start position:0% Beacon no two subnets one bigger no three<00:15:38.339> so<00:15:38.459> now<00:15:38.639> so<00:15:38.699> we<00:15:38.880> can<00:15:38.940> adjust<00:15:39.060> that<00:15:39.899> that 00:15:40.129 --> 00:15:40.139 align:start position:0% three so now so we can adjust that that 00:15:40.139 --> 00:15:42.230 align:start position:0% three so now so we can adjust that that kind<00:15:40.380> of<00:15:40.500> differential<00:15:40.920> and<00:15:41.639> whether<00:15:42.000> that's 00:15:42.230 --> 00:15:42.240 align:start position:0% kind of differential and whether that's 00:15:42.240 --> 00:15:44.090 align:start position:0% kind of differential and whether that's feasible<00:15:42.779> is<00:15:43.199> dependent<00:15:43.620> on<00:15:43.740> the<00:15:43.860> number<00:15:43.920> of 00:15:44.090 --> 00:15:44.100 align:start position:0% feasible is dependent on the number of 00:15:44.100 --> 00:15:45.290 align:start position:0% feasible is dependent on the number of nodes<00:15:44.279> on<00:15:44.459> the<00:15:44.579> network<00:15:44.699> so<00:15:45.000> that's<00:15:45.120> something 00:15:45.290 --> 00:15:45.300 align:start position:0% nodes on the network so that's something 00:15:45.300 --> 00:15:47.569 align:start position:0% nodes on the network so that's something we<00:15:45.540> need<00:15:45.660> to<00:15:45.779> measure<00:15:46.079> but<00:15:46.740> the<00:15:47.100> benefits<00:15:47.399> that 00:15:47.569 --> 00:15:47.579 align:start position:0% we need to measure but the benefits that 00:15:47.579 --> 00:15:49.790 align:start position:0% we need to measure but the benefits that we<00:15:47.699> get<00:15:47.820> from<00:15:48.000> this<00:15:48.180> is<00:15:48.600> essentially<00:15:49.019> for<00:15:49.680> the 00:15:49.790 --> 00:15:49.800 align:start position:0% we get from this is essentially for the 00:15:49.800 --> 00:15:51.410 align:start position:0% we get from this is essentially for the institutional<00:15:50.279> stakers<00:15:50.699> which<00:15:50.880> represent 00:15:51.410 --> 00:15:51.420 align:start position:0% institutional stakers which represent 00:15:51.420 --> 00:15:53.509 align:start position:0% institutional stakers which represent roughly<00:15:51.779> like<00:15:52.019> 10<00:15:52.199> of<00:15:52.740> all<00:15:52.920> the<00:15:53.100> validating 00:15:53.509 --> 00:15:53.519 align:start position:0% roughly like 10 of all the validating 00:15:53.519 --> 00:15:55.250 align:start position:0% roughly like 10 of all the validating nodes<00:15:53.820> on<00:15:54.000> the<00:15:54.120> network<00:15:54.180> their<00:15:54.720> bandwidth 00:15:55.250 --> 00:15:55.260 align:start position:0% nodes on the network their bandwidth 00:15:55.260 --> 00:15:57.590 align:start position:0% nodes on the network their bandwidth will<00:15:55.380> drop<00:15:55.560> by<00:15:55.740> about<00:15:55.920> over<00:15:56.279> 90<00:15:56.579> which<00:15:57.240> is<00:15:57.360> kind 00:15:57.590 --> 00:15:57.600 align:start position:0% will drop by about over 90 which is kind 00:15:57.600 --> 00:15:59.090 align:start position:0% will drop by about over 90 which is kind of<00:15:57.660> Handy<00:15:57.959> and<00:15:58.260> as<00:15:58.620> I<00:15:58.740> mentioned<00:15:58.980> before 00:15:59.090 --> 00:15:59.100 align:start position:0% of Handy and as I mentioned before 00:15:59.100 --> 00:16:00.290 align:start position:0% of Handy and as I mentioned before everyone<00:15:59.399> that<00:15:59.699> has<00:15:59.880> more<00:16:00.060> than<00:16:00.120> one 00:16:00.290 --> 00:16:00.300 align:start position:0% everyone that has more than one 00:16:00.300 --> 00:16:01.790 align:start position:0% everyone that has more than one validator<00:16:00.660> will<00:16:00.839> have<00:16:01.019> a<00:16:01.079> reduced<00:16:01.320> bandwidth 00:16:01.790 --> 00:16:01.800 align:start position:0% validator will have a reduced bandwidth 00:16:01.800 --> 00:16:04.310 align:start position:0% validator will have a reduced bandwidth so<00:16:02.519> fundamentally<00:16:03.180> we're<00:16:03.360> talking<00:16:03.540> about<00:16:03.720> do 00:16:04.310 --> 00:16:04.320 align:start position:0% so fundamentally we're talking about do 00:16:04.320 --> 00:16:05.689 align:start position:0% so fundamentally we're talking about do we<00:16:04.500> need<00:16:04.680> all<00:16:04.920> of<00:16:04.980> these<00:16:05.160> nodes<00:16:05.399> on<00:16:05.579> the 00:16:05.689 --> 00:16:05.699 align:start position:0% we need all of these nodes on the 00:16:05.699 --> 00:16:06.829 align:start position:0% we need all of these nodes on the network<00:16:05.820> to 00:16:06.829 --> 00:16:06.839 align:start position:0% network to 00:16:06.839 --> 00:16:09.110 align:start position:0% network to support<00:16:07.380> these<00:16:07.740> subnets<00:16:08.100> at<00:16:08.519> the<00:16:08.639> cost<00:16:08.760> of<00:16:08.940> the 00:16:09.110 --> 00:16:09.120 align:start position:0% support these subnets at the cost of the 00:16:09.120 --> 00:16:10.129 align:start position:0% support these subnets at the cost of the huge<00:16:09.420> amount<00:16:09.540> of<00:16:09.660> bandwidth<00:16:10.019> they're 00:16:10.129 --> 00:16:10.139 align:start position:0% huge amount of bandwidth they're 00:16:10.139 --> 00:16:12.170 align:start position:0% huge amount of bandwidth they're currently<00:16:10.440> using<00:16:10.740> and<00:16:11.459> so<00:16:11.579> potentially<00:16:12.000> not 00:16:12.170 --> 00:16:12.180 align:start position:0% currently using and so potentially not 00:16:12.180 --> 00:16:14.629 align:start position:0% currently using and so potentially not and<00:16:12.480> it's<00:16:12.660> customizable<00:16:13.380> the<00:16:14.339> second<00:16:14.459> thing 00:16:14.629 --> 00:16:14.639 align:start position:0% and it's customizable the second thing 00:16:14.639 --> 00:16:16.310 align:start position:0% and it's customizable the second thing is<00:16:14.820> it's<00:16:15.000> also<00:16:15.300> enforceable<00:16:15.779> because<00:16:16.019> we 00:16:16.310 --> 00:16:16.320 align:start position:0% is it's also enforceable because we 00:16:16.320 --> 00:16:18.949 align:start position:0% is it's also enforceable because we would<00:16:16.440> tag<00:16:16.800> a<00:16:17.279> beaker<00:16:17.639> node's<00:16:17.940> node<00:16:18.120> ID<00:16:18.300> to<00:16:18.839> a 00:16:18.949 --> 00:16:18.959 align:start position:0% would tag a beaker node's node ID to a 00:16:18.959 --> 00:16:20.569 align:start position:0% would tag a beaker node's node ID to a subnet<00:16:19.380> and<00:16:19.740> so<00:16:19.860> when<00:16:19.980> we<00:16:20.160> connect<00:16:20.279> to<00:16:20.459> a 00:16:20.569 --> 00:16:20.579 align:start position:0% subnet and so when we connect to a 00:16:20.579 --> 00:16:22.189 align:start position:0% subnet and so when we connect to a weaker<00:16:20.940> node<00:16:21.120> and<00:16:21.360> it's<00:16:21.480> not<00:16:21.660> subscribed<00:16:22.079> to 00:16:22.189 --> 00:16:22.199 align:start position:0% weaker node and it's not subscribed to 00:16:22.199 --> 00:16:23.329 align:start position:0% weaker node and it's not subscribed to that<00:16:22.320> subnet<00:16:22.620> that<00:16:22.800> we<00:16:22.860> know<00:16:22.980> that<00:16:23.100> it's<00:16:23.160> being 00:16:23.329 --> 00:16:23.339 align:start position:0% that subnet that we know that it's being 00:16:23.339 --> 00:16:24.949 align:start position:0% that subnet that we know that it's being naughty<00:16:23.639> or<00:16:23.760> relying<00:16:24.060> to<00:16:24.120> it<00:16:24.240> so<00:16:24.360> we<00:16:24.480> can<00:16:24.660> kick 00:16:24.949 --> 00:16:24.959 align:start position:0% naughty or relying to it so we can kick 00:16:24.959 --> 00:16:26.689 align:start position:0% naughty or relying to it so we can kick it<00:16:25.079> off<00:16:25.199> so<00:16:25.500> we<00:16:26.100> actually<00:16:26.220> have<00:16:26.459> the 00:16:26.689 --> 00:16:26.699 align:start position:0% it off so we actually have the 00:16:26.699 --> 00:16:28.910 align:start position:0% it off so we actually have the enforceability<00:16:27.300> property<00:16:27.720> yeah<00:16:28.380> so<00:16:28.680> that's 00:16:28.910 --> 00:16:28.920 align:start position:0% enforceability property yeah so that's 00:16:28.920 --> 00:16:30.590 align:start position:0% enforceability property yeah so that's one<00:16:29.579> solution 00:16:30.590 --> 00:16:30.600 align:start position:0% one solution 00:16:30.600 --> 00:16:32.329 align:start position:0% one solution and<00:16:30.959> that's<00:16:31.079> kind<00:16:31.320> of<00:16:31.440> a<00:16:31.680> low<00:16:31.860> hanging<00:16:32.220> fruit 00:16:32.329 --> 00:16:32.339 align:start position:0% and that's kind of a low hanging fruit 00:16:32.339 --> 00:16:33.850 align:start position:0% and that's kind of a low hanging fruit it's<00:16:32.519> kind<00:16:32.699> of<00:16:32.820> easy<00:16:32.880> to<00:16:33.120> do<00:16:33.180> we<00:16:33.420> get 00:16:33.850 --> 00:16:33.860 align:start position:0% it's kind of easy to do we get 00:16:33.860 --> 00:16:36.590 align:start position:0% it's kind of easy to do we get substantial<00:16:34.860> gains<00:16:35.279> the<00:16:35.820> other<00:16:35.940> thing<00:16:36.180> that 00:16:36.590 --> 00:16:36.600 align:start position:0% substantial gains the other thing that 00:16:36.600 --> 00:16:37.910 align:start position:0% substantial gains the other thing that Diva<00:16:37.019> was<00:16:37.139> talking<00:16:37.320> about<00:16:37.500> is<00:16:37.740> message 00:16:37.910 --> 00:16:37.920 align:start position:0% Diva was talking about is message 00:16:37.920 --> 00:16:40.249 align:start position:0% Diva was talking about is message amplification<00:16:38.579> in<00:16:38.759> gossips<00:16:39.060> app<00:16:39.360> so<00:16:39.959> if 00:16:40.249 --> 00:16:40.259 align:start position:0% amplification in gossips app so if 00:16:40.259 --> 00:16:42.249 align:start position:0% amplification in gossips app so if there's<00:16:40.560> anything<00:16:40.740> we<00:16:40.980> can<00:16:41.100> do<00:16:41.220> about<00:16:41.339> that 00:16:42.249 --> 00:16:42.259 align:start position:0% there's anything we can do about that 00:16:42.259 --> 00:16:45.829 align:start position:0% there's anything we can do about that the<00:16:43.259> idea<00:16:43.800> that<00:16:44.100> we<00:16:45.000> want<00:16:45.120> to<00:16:45.300> try<00:16:45.480> and<00:16:45.600> push 00:16:45.829 --> 00:16:45.839 align:start position:0% the idea that we want to try and push 00:16:45.839 --> 00:16:48.230 align:start position:0% the idea that we want to try and push forward<00:16:46.019> is<00:16:46.380> a<00:16:46.560> concept<00:16:46.800> called<00:16:46.980> appisub<00:16:47.639> so 00:16:48.230 --> 00:16:48.240 align:start position:0% forward is a concept called appisub so 00:16:48.240 --> 00:16:50.689 align:start position:0% forward is a concept called appisub so gossip<00:16:48.600> sub<00:16:48.779> is<00:16:49.199> a<00:16:49.560> protocol<00:16:49.980> that<00:16:50.279> exists<00:16:50.519> in 00:16:50.689 --> 00:16:50.699 align:start position:0% gossip sub is a protocol that exists in 00:16:50.699 --> 00:16:52.790 align:start position:0% gossip sub is a protocol that exists in lib<00:16:51.000> P2P<00:16:51.300> as<00:16:51.480> Diva<00:16:51.899> was<00:16:52.019> mentioning<00:16:52.259> and<00:16:52.620> the 00:16:52.790 --> 00:16:52.800 align:start position:0% lib P2P as Diva was mentioning and the 00:16:52.800 --> 00:16:55.009 align:start position:0% lib P2P as Diva was mentioning and the lip<00:16:53.040> p2b<00:16:53.399> guys<00:16:53.639> which<00:16:53.880> is<00:16:54.060> kind<00:16:54.300> of<00:16:54.420> run<00:16:54.779> by 00:16:55.009 --> 00:16:55.019 align:start position:0% lip p2b guys which is kind of run by 00:16:55.019 --> 00:16:58.430 align:start position:0% lip p2b guys which is kind of run by protocol<00:16:55.320> Labs<00:16:55.800> have<00:16:56.220> had<00:16:56.519> a<00:16:57.060> Evolution<00:16:57.720> stage 00:16:58.430 --> 00:16:58.440 align:start position:0% protocol Labs have had a Evolution stage 00:16:58.440 --> 00:17:01.009 align:start position:0% protocol Labs have had a Evolution stage of<00:16:58.740> Gossip<00:16:59.100> sub<00:16:59.279> they've<00:17:00.180> talked<00:17:00.480> about<00:17:00.600> Epi 00:17:01.009 --> 00:17:01.019 align:start position:0% of Gossip sub they've talked about Epi 00:17:01.019 --> 00:17:03.530 align:start position:0% of Gossip sub they've talked about Epi sub<00:17:01.139> for<00:17:01.380> quite<00:17:01.560> a<00:17:01.800> period<00:17:02.339> of<00:17:02.459> time<00:17:02.639> they've 00:17:03.530 --> 00:17:03.540 align:start position:0% sub for quite a period of time they've 00:17:03.540 --> 00:17:05.150 align:start position:0% sub for quite a period of time they've done<00:17:03.720> a<00:17:03.839> bunch<00:17:04.199> of<00:17:04.319> research<00:17:04.620> in<00:17:04.860> particular 00:17:05.150 --> 00:17:05.160 align:start position:0% done a bunch of research in particular 00:17:05.160 --> 00:17:08.090 align:start position:0% done a bunch of research in particular viso<00:17:05.819> or<00:17:06.540> Dimitri<00:17:07.020> who<00:17:07.319> works<00:17:07.679> for<00:17:07.799> protocol 00:17:08.090 --> 00:17:08.100 align:start position:0% viso or Dimitri who works for protocol 00:17:08.100 --> 00:17:11.870 align:start position:0% viso or Dimitri who works for protocol Labs<00:17:08.520> has<00:17:09.620> has<00:17:10.620> had<00:17:10.919> this<00:17:11.160> kind<00:17:11.339> of<00:17:11.400> vision<00:17:11.579> for 00:17:11.870 --> 00:17:11.880 align:start position:0% Labs has has had this kind of vision for 00:17:11.880 --> 00:17:13.429 align:start position:0% Labs has has had this kind of vision for episod<00:17:12.419> for<00:17:12.540> a<00:17:12.660> while<00:17:12.720> but<00:17:12.839> has<00:17:13.079> never<00:17:13.199> had<00:17:13.319> the 00:17:13.429 --> 00:17:13.439 align:start position:0% episod for a while but has never had the 00:17:13.439 --> 00:17:14.870 align:start position:0% episod for a while but has never had the push<00:17:13.559> or<00:17:13.799> the<00:17:13.919> drive<00:17:14.040> to<00:17:14.220> do<00:17:14.339> it<00:17:14.400> but<00:17:14.579> now<00:17:14.699> that 00:17:14.870 --> 00:17:14.880 align:start position:0% push or the drive to do it but now that 00:17:14.880 --> 00:17:16.789 align:start position:0% push or the drive to do it but now that we're<00:17:15.059> seeing<00:17:15.660> quite<00:17:16.020> substantial<00:17:16.500> amounts 00:17:16.789 --> 00:17:16.799 align:start position:0% we're seeing quite substantial amounts 00:17:16.799 --> 00:17:18.650 align:start position:0% we're seeing quite substantial amounts of<00:17:16.919> bandwidth<00:17:17.400> it's<00:17:17.520> it's<00:17:17.579> probably<00:17:18.120> time<00:17:18.419> we 00:17:18.650 --> 00:17:18.660 align:start position:0% of bandwidth it's it's probably time we 00:17:18.660 --> 00:17:20.329 align:start position:0% of bandwidth it's it's probably time we try<00:17:18.839> and<00:17:19.020> realize<00:17:19.620> this<00:17:19.799> thing<00:17:19.980> so<00:17:20.040> I<00:17:20.220> just 00:17:20.329 --> 00:17:20.339 align:start position:0% try and realize this thing so I just 00:17:20.339 --> 00:17:21.289 align:start position:0% try and realize this thing so I just want<00:17:20.459> to 00:17:21.289 --> 00:17:21.299 align:start position:0% want to 00:17:21.299 --> 00:17:23.210 align:start position:0% want to briefly<00:17:21.959> go<00:17:22.079> over<00:17:22.199> the<00:17:22.380> concept<00:17:22.620> and<00:17:22.860> what 00:17:23.210 --> 00:17:23.220 align:start position:0% briefly go over the concept and what 00:17:23.220 --> 00:17:24.289 align:start position:0% briefly go over the concept and what it's<00:17:23.339> what<00:17:23.579> it's<00:17:23.699> going<00:17:23.880> to<00:17:23.880> do<00:17:23.939> and<00:17:24.059> how<00:17:24.179> it 00:17:24.289 --> 00:17:24.299 align:start position:0% it's what it's going to do and how it 00:17:24.299 --> 00:17:26.750 align:start position:0% it's what it's going to do and how it could<00:17:24.419> help<00:17:24.540> us<00:17:24.600> with<00:17:24.780> bandwidth<00:17:25.260> okay<00:17:25.980> so<00:17:26.400> app 00:17:26.750 --> 00:17:26.760 align:start position:0% could help us with bandwidth okay so app 00:17:26.760 --> 00:17:29.510 align:start position:0% could help us with bandwidth okay so app is<00:17:27.000> up<00:17:27.240> you<00:17:28.140> what<00:17:28.679> the<00:17:28.980> biggest<00:17:29.040> problem<00:17:29.280> that 00:17:29.510 --> 00:17:29.520 align:start position:0% is up you what the biggest problem that 00:17:29.520 --> 00:17:31.430 align:start position:0% is up you what the biggest problem that we<00:17:29.640> have<00:17:29.820> is<00:17:30.179> that<00:17:30.419> if<00:17:30.600> you<00:17:30.720> have<00:17:30.840> a<00:17:30.960> high<00:17:31.080> mesh 00:17:31.430 --> 00:17:31.440 align:start position:0% we have is that if you have a high mesh 00:17:31.440 --> 00:17:32.990 align:start position:0% we have is that if you have a high mesh degree<00:17:31.620> as<00:17:31.919> Diva<00:17:32.280> was<00:17:32.460> saying<00:17:32.700> that<00:17:32.760> that 00:17:32.990 --> 00:17:33.000 align:start position:0% degree as Diva was saying that that 00:17:33.000 --> 00:17:34.850 align:start position:0% degree as Diva was saying that that means<00:17:33.299> you<00:17:33.419> have<00:17:33.600> a<00:17:33.780> high<00:17:33.900> connectivity<00:17:34.440> of 00:17:34.850 --> 00:17:34.860 align:start position:0% means you have a high connectivity of 00:17:34.860 --> 00:17:36.590 align:start position:0% means you have a high connectivity of nodes<00:17:35.160> in<00:17:35.340> your<00:17:35.460> network<00:17:35.640> so<00:17:36.059> every<00:17:36.299> node 00:17:36.590 --> 00:17:36.600 align:start position:0% nodes in your network so every node 00:17:36.600 --> 00:17:38.810 align:start position:0% nodes in your network so every node could<00:17:36.840> be<00:17:36.960> connected<00:17:37.260> to<00:17:37.440> another<00:17:37.679> 10<00:17:38.520> or 00:17:38.810 --> 00:17:38.820 align:start position:0% could be connected to another 10 or 00:17:38.820 --> 00:17:40.549 align:start position:0% could be connected to another 10 or eight<00:17:39.059> other<00:17:39.240> nodes<00:17:39.539> and<00:17:39.780> then<00:17:39.960> you<00:17:40.080> get<00:17:40.200> huge 00:17:40.549 --> 00:17:40.559 align:start position:0% eight other nodes and then you get huge 00:17:40.559 --> 00:17:42.230 align:start position:0% eight other nodes and then you get huge message<00:17:40.740> amplification<00:17:41.400> so<00:17:41.700> every<00:17:41.940> time<00:17:42.120> you 00:17:42.230 --> 00:17:42.240 align:start position:0% message amplification so every time you 00:17:42.240 --> 00:17:44.029 align:start position:0% message amplification so every time you send<00:17:42.419> one<00:17:42.720> message<00:17:42.960> most<00:17:43.679> of<00:17:43.860> the<00:17:43.919> network 00:17:44.029 --> 00:17:44.039 align:start position:0% send one message most of the network 00:17:44.039 --> 00:17:45.529 align:start position:0% send one message most of the network will<00:17:44.340> probably<00:17:44.580> have<00:17:44.820> to<00:17:44.940> download<00:17:45.059> it<00:17:45.299> eight 00:17:45.529 --> 00:17:45.539 align:start position:0% will probably have to download it eight 00:17:45.539 --> 00:17:47.750 align:start position:0% will probably have to download it eight times<00:17:45.720> so<00:17:46.320> if<00:17:46.559> you<00:17:46.679> increase<00:17:46.980> that<00:17:47.280> message<00:17:47.460> by 00:17:47.750 --> 00:17:47.760 align:start position:0% times so if you increase that message by 00:17:47.760 --> 00:17:49.430 align:start position:0% times so if you increase that message by one<00:17:47.940> megabyte<00:17:48.419> you're<00:17:48.660> actually<00:17:48.960> increasing 00:17:49.430 --> 00:17:49.440 align:start position:0% one megabyte you're actually increasing 00:17:49.440 --> 00:17:50.930 align:start position:0% one megabyte you're actually increasing it<00:17:49.559> by<00:17:49.799> eight<00:17:50.039> times<00:17:50.220> eight<00:17:50.460> megabytes 00:17:50.930 --> 00:17:50.940 align:start position:0% it by eight times eight megabytes 00:17:50.940 --> 00:17:52.130 align:start position:0% it by eight times eight megabytes because<00:17:51.179> that's<00:17:51.360> the<00:17:51.539> amount<00:17:51.720> of<00:17:51.840> boundaries 00:17:52.130 --> 00:17:52.140 align:start position:0% because that's the amount of boundaries 00:17:52.140 --> 00:17:53.630 align:start position:0% because that's the amount of boundaries that<00:17:52.320> has<00:17:52.500> to<00:17:52.620> be<00:17:52.740> downloaded<00:17:53.340> and<00:17:53.520> then 00:17:53.630 --> 00:17:53.640 align:start position:0% that has to be downloaded and then 00:17:53.640 --> 00:17:56.270 align:start position:0% that has to be downloaded and then propagated<00:17:54.120> so<00:17:54.960> natively<00:17:55.919> you<00:17:56.039> would<00:17:56.100> first 00:17:56.270 --> 00:17:56.280 align:start position:0% propagated so natively you would first 00:17:56.280 --> 00:17:57.470 align:start position:0% propagated so natively you would first think<00:17:56.400> okay<00:17:56.580> why<00:17:56.820> don't<00:17:56.940> we<00:17:57.059> just<00:17:57.120> lower<00:17:57.240> the 00:17:57.470 --> 00:17:57.480 align:start position:0% think okay why don't we just lower the 00:17:57.480 --> 00:17:59.330 align:start position:0% think okay why don't we just lower the mesh<00:17:57.660> degree<00:17:57.900> I<00:17:58.380> did<00:17:58.500> try<00:17:58.679> to<00:17:58.799> do<00:17:58.919> that<00:17:59.039> at<00:17:59.220> one 00:17:59.330 --> 00:17:59.340 align:start position:0% mesh degree I did try to do that at one 00:17:59.340 --> 00:18:01.490 align:start position:0% mesh degree I did try to do that at one point<00:17:59.520> but<00:17:59.880> as<00:18:00.419> everyone<00:18:00.600> points<00:18:01.080> out<00:18:01.140> that's 00:18:01.490 --> 00:18:01.500 align:start position:0% point but as everyone points out that's 00:18:01.500 --> 00:18:03.289 align:start position:0% point but as everyone points out that's not<00:18:01.799> very<00:18:02.039> it's<00:18:02.280> not<00:18:02.460> a<00:18:02.580> safe<00:18:02.700> thing<00:18:02.880> to<00:18:03.059> do<00:18:03.120> we 00:18:03.289 --> 00:18:03.299 align:start position:0% not very it's not a safe thing to do we 00:18:03.299 --> 00:18:04.370 align:start position:0% not very it's not a safe thing to do we don't<00:18:03.419> really<00:18:03.539> know<00:18:03.720> how<00:18:03.900> the<00:18:04.020> network<00:18:04.140> is 00:18:04.370 --> 00:18:04.380 align:start position:0% don't really know how the network is 00:18:04.380 --> 00:18:06.650 align:start position:0% don't really know how the network is going<00:18:04.559> to<00:18:04.620> behave<00:18:05.000> we<00:18:06.000> can<00:18:06.120> try<00:18:06.240> it<00:18:06.360> on<00:18:06.480> test 00:18:06.650 --> 00:18:06.660 align:start position:0% going to behave we can try it on test 00:18:06.660 --> 00:18:09.049 align:start position:0% going to behave we can try it on test Nets<00:18:07.080> but<00:18:07.260> the<00:18:07.620> topology<00:18:08.280> or<00:18:08.640> the<00:18:08.760> structure 00:18:09.049 --> 00:18:09.059 align:start position:0% Nets but the topology or the structure 00:18:09.059 --> 00:18:11.090 align:start position:0% Nets but the topology or the structure of<00:18:09.240> a<00:18:09.360> test<00:18:09.480> net<00:18:09.720> doesn't<00:18:10.140> look<00:18:10.380> like<00:18:10.559> mainnet 00:18:11.090 --> 00:18:11.100 align:start position:0% of a test net doesn't look like mainnet 00:18:11.100 --> 00:18:12.650 align:start position:0% of a test net doesn't look like mainnet if<00:18:11.340> we<00:18:11.460> just<00:18:11.580> lower<00:18:11.700> the<00:18:11.940> mesh<00:18:12.120> degree<00:18:12.360> to<00:18:12.480> two 00:18:12.650 --> 00:18:12.660 align:start position:0% if we just lower the mesh degree to two 00:18:12.660 --> 00:18:14.330 align:start position:0% if we just lower the mesh degree to two for<00:18:12.840> for<00:18:13.200> example<00:18:13.440> a<00:18:13.620> mainnet<00:18:13.980> you<00:18:14.160> might<00:18:14.220> just 00:18:14.330 --> 00:18:14.340 align:start position:0% for for example a mainnet you might just 00:18:14.340 --> 00:18:16.909 align:start position:0% for for example a mainnet you might just not<00:18:14.460> restart<00:18:14.640> receiving<00:18:15.179> blocks<00:18:15.600> so<00:18:16.140> we<00:18:16.559> have 00:18:16.909 --> 00:18:16.919 align:start position:0% not restart receiving blocks so we have 00:18:16.919 --> 00:18:18.830 align:start position:0% not restart receiving blocks so we have to<00:18:17.039> do<00:18:17.100> that<00:18:17.160> with<00:18:17.340> either<00:18:17.460> great<00:18:17.820> care<00:18:18.059> or 00:18:18.830 --> 00:18:18.840 align:start position:0% to do that with either great care or 00:18:18.840 --> 00:18:21.710 align:start position:0% to do that with either great care or with<00:18:19.140> a<00:18:19.380> lot<00:18:19.500> of<00:18:19.559> testing<00:18:19.980> so<00:18:20.520> it's<00:18:21.000> it's<00:18:21.240> an 00:18:21.710 --> 00:18:21.720 align:start position:0% with a lot of testing so it's it's an 00:18:21.720 --> 00:18:23.450 align:start position:0% with a lot of testing so it's it's an interesting<00:18:22.140> idea<00:18:22.440> but<00:18:22.679> we<00:18:23.039> could<00:18:23.280> probably 00:18:23.450 --> 00:18:23.460 align:start position:0% interesting idea but we could probably 00:18:23.460 --> 00:18:25.250 align:start position:0% interesting idea but we could probably do<00:18:23.640> better<00:18:23.820> so<00:18:24.120> another<00:18:24.600> idea<00:18:24.900> is<00:18:25.020> to 00:18:25.250 --> 00:18:25.260 align:start position:0% do better so another idea is to 00:18:25.260 --> 00:18:27.110 align:start position:0% do better so another idea is to dynamically<00:18:26.039> adjust<00:18:26.280> adjust<00:18:26.700> the 00:18:27.110 --> 00:18:27.120 align:start position:0% dynamically adjust adjust the 00:18:27.120 --> 00:18:29.930 align:start position:0% dynamically adjust adjust the connectivity<00:18:28.039> we<00:18:29.039> also<00:18:29.220> run<00:18:29.340> into<00:18:29.520> a<00:18:29.700> kind<00:18:29.820> of 00:18:29.930 --> 00:18:29.940 align:start position:0% connectivity we also run into a kind of 00:18:29.940 --> 00:18:33.169 align:start position:0% connectivity we also run into a kind of a<00:18:30.000> similar<00:18:30.299> problem<00:18:30.500> and<00:18:31.500> typically<00:18:32.160> a<00:18:32.880> lot<00:18:33.059> of 00:18:33.169 --> 00:18:33.179 align:start position:0% a similar problem and typically a lot of 00:18:33.179 --> 00:18:35.390 align:start position:0% a similar problem and typically a lot of the<00:18:33.720> people<00:18:33.840> that<00:18:34.080> use<00:18:34.200> our<00:18:34.440> client<00:18:34.740> they<00:18:35.160> they 00:18:35.390 --> 00:18:35.400 align:start position:0% the people that use our client they they 00:18:35.400 --> 00:18:38.270 align:start position:0% the people that use our client they they suggest<00:18:35.760> lowering<00:18:36.299> the<00:18:36.660> P<00:18:36.780> account<00:18:37.020> which<00:18:37.320> is 00:18:38.270 --> 00:18:38.280 align:start position:0% suggest lowering the P account which is 00:18:38.280 --> 00:18:39.710 align:start position:0% suggest lowering the P account which is um<00:18:38.340> it's<00:18:38.640> a<00:18:38.820> fault<00:18:39.000> it<00:18:39.179> doesn't<00:18:39.299> quite<00:18:39.480> help 00:18:39.710 --> 00:18:39.720 align:start position:0% um it's a fault it doesn't quite help 00:18:39.720 --> 00:18:42.169 align:start position:0% um it's a fault it doesn't quite help you<00:18:39.900> so<00:18:40.860> that's<00:18:41.100> also<00:18:41.400> not<00:18:41.580> the<00:18:41.700> best<00:18:41.820> solution 00:18:42.169 --> 00:18:42.179 align:start position:0% you so that's also not the best solution 00:18:42.179 --> 00:18:44.930 align:start position:0% you so that's also not the best solution so<00:18:42.720> the<00:18:42.900> idea<00:18:43.140> with<00:18:43.320> appisub<00:18:43.919> is<00:18:44.460> to<00:18:44.640> try<00:18:44.760> and 00:18:44.930 --> 00:18:44.940 align:start position:0% so the idea with appisub is to try and 00:18:44.940 --> 00:18:47.510 align:start position:0% so the idea with appisub is to try and minimize<00:18:45.360> duplication<00:18:46.080> and<00:18:46.620> latency<00:18:47.039> by 00:18:47.510 --> 00:18:47.520 align:start position:0% minimize duplication and latency by 00:18:47.520 --> 00:18:49.430 align:start position:0% minimize duplication and latency by making<00:18:47.760> the<00:18:48.000> mesh<00:18:48.360> it<00:18:48.780> keeps<00:18:49.200> the<00:18:49.320> same 00:18:49.430 --> 00:18:49.440 align:start position:0% making the mesh it keeps the same 00:18:49.440 --> 00:18:51.169 align:start position:0% making the mesh it keeps the same connectivity<00:18:49.860> but<00:18:50.160> making<00:18:50.700> it<00:18:50.880> a<00:18:51.000> little<00:18:51.059> bit 00:18:51.169 --> 00:18:51.179 align:start position:0% connectivity but making it a little bit 00:18:51.179 --> 00:18:53.150 align:start position:0% connectivity but making it a little bit more<00:18:51.360> efficient<00:18:51.720> and<00:18:52.260> by<00:18:52.380> efficient<00:18:52.799> I<00:18:52.980> mean 00:18:53.150 --> 00:18:53.160 align:start position:0% more efficient and by efficient I mean 00:18:53.160 --> 00:18:55.430 align:start position:0% more efficient and by efficient I mean we're<00:18:53.340> trying<00:18:53.640> to<00:18:53.880> remove<00:18:54.000> the<00:18:54.720> number<00:18:54.960> of 00:18:55.430 --> 00:18:55.440 align:start position:0% we're trying to remove the number of 00:18:55.440 --> 00:18:57.590 align:start position:0% we're trying to remove the number of duplicates<00:18:56.160> and<00:18:56.640> at<00:18:56.760> the<00:18:56.940> same<00:18:57.059> time<00:18:57.179> either 00:18:57.590 --> 00:18:57.600 align:start position:0% duplicates and at the same time either 00:18:57.600 --> 00:18:59.690 align:start position:0% duplicates and at the same time either maintain<00:18:58.080> or<00:18:58.320> lower<00:18:58.559> the<00:18:58.799> latency<00:18:59.100> inside<00:18:59.460> the 00:18:59.690 --> 00:18:59.700 align:start position:0% maintain or lower the latency inside the 00:18:59.700 --> 00:19:02.630 align:start position:0% maintain or lower the latency inside the mesh<00:19:00.059> and<00:19:00.480> the<00:19:00.539> mesh<00:19:00.840> is<00:19:00.960> just<00:19:01.200> a<00:19:02.100> subset<00:19:02.580> of 00:19:02.630 --> 00:19:02.640 align:start position:0% mesh and the mesh is just a subset of 00:19:02.640 --> 00:19:03.650 align:start position:0% mesh and the mesh is just a subset of your<00:19:02.760> peers<00:19:03.000> that<00:19:03.179> you're<00:19:03.240> connected<00:19:03.539> to 00:19:03.650 --> 00:19:03.660 align:start position:0% your peers that you're connected to 00:19:03.660 --> 00:19:04.669 align:start position:0% your peers that you're connected to that's<00:19:03.840> where<00:19:03.960> you<00:19:04.080> receive<00:19:04.320> your<00:19:04.440> messages 00:19:04.669 --> 00:19:04.679 align:start position:0% that's where you receive your messages 00:19:04.679 --> 00:19:07.430 align:start position:0% that's where you receive your messages from<00:19:05.059> so<00:19:06.059> that<00:19:06.720> kind<00:19:06.840> of<00:19:06.960> sounds<00:19:07.080> like<00:19:07.260> we're 00:19:07.430 --> 00:19:07.440 align:start position:0% from so that kind of sounds like we're 00:19:07.440 --> 00:19:10.010 align:start position:0% from so that kind of sounds like we're trying<00:19:07.679> to<00:19:07.860> win<00:19:08.220> on<00:19:08.400> two<00:19:08.580> fronts<00:19:08.940> we<00:19:09.120> get<00:19:09.299> less 00:19:10.010 --> 00:19:10.020 align:start position:0% trying to win on two fronts we get less 00:19:10.020 --> 00:19:12.650 align:start position:0% trying to win on two fronts we get less bandwidth<00:19:10.740> and<00:19:11.100> higher<00:19:11.460> latency<00:19:11.760> which<00:19:12.419> kind 00:19:12.650 --> 00:19:12.660 align:start position:0% bandwidth and higher latency which kind 00:19:12.660 --> 00:19:13.850 align:start position:0% bandwidth and higher latency which kind of<00:19:12.780> doesn't<00:19:13.020> sound<00:19:13.260> like<00:19:13.380> we<00:19:13.500> should<00:19:13.620> be<00:19:13.740> able 00:19:13.850 --> 00:19:13.860 align:start position:0% of doesn't sound like we should be able 00:19:13.860 --> 00:19:15.350 align:start position:0% of doesn't sound like we should be able to<00:19:13.919> do<00:19:13.980> it<00:19:14.100> but<00:19:14.220> let<00:19:14.400> me<00:19:14.520> explain<00:19:14.640> the<00:19:15.059> the 00:19:15.350 --> 00:19:15.360 align:start position:0% to do it but let me explain the the 00:19:15.360 --> 00:19:17.270 align:start position:0% to do it but let me explain the the general<00:19:15.600> principle<00:19:16.140> and<00:19:16.500> and<00:19:16.679> maybe<00:19:16.860> it<00:19:17.100> makes 00:19:17.270 --> 00:19:17.280 align:start position:0% general principle and and maybe it makes 00:19:17.280 --> 00:19:17.990 align:start position:0% general principle and and maybe it makes sense 00:19:17.990 --> 00:19:18.000 align:start position:0% sense 00:19:18.000 --> 00:19:20.210 align:start position:0% sense so<00:19:18.419> the<00:19:18.539> general<00:19:18.720> principle<00:19:19.140> is<00:19:19.559> you're<00:19:19.980> a 00:19:20.210 --> 00:19:20.220 align:start position:0% so the general principle is you're a 00:19:20.220 --> 00:19:21.529 align:start position:0% so the general principle is you're a node<00:19:20.340> on<00:19:20.520> the<00:19:20.640> network 00:19:21.529 --> 00:19:21.539 align:start position:0% node on the network 00:19:21.539 --> 00:19:24.049 align:start position:0% node on the network you're<00:19:22.020> receiving<00:19:22.440> all<00:19:22.679> of<00:19:22.799> these<00:19:22.980> messages<00:19:23.100> a 00:19:24.049 --> 00:19:24.059 align:start position:0% you're receiving all of these messages a 00:19:24.059 --> 00:19:25.610 align:start position:0% you're receiving all of these messages a lot<00:19:24.179> of<00:19:24.240> them<00:19:24.360> are<00:19:24.480> duplicates<00:19:24.960> you<00:19:25.380> want<00:19:25.500> to 00:19:25.610 --> 00:19:25.620 align:start position:0% lot of them are duplicates you want to 00:19:25.620 --> 00:19:27.230 align:start position:0% lot of them are duplicates you want to just<00:19:25.740> start<00:19:25.860> collecting<00:19:26.340> Statistics<00:19:26.820> over 00:19:27.230 --> 00:19:27.240 align:start position:0% just start collecting Statistics over 00:19:27.240 --> 00:19:30.230 align:start position:0% just start collecting Statistics over which<00:19:28.020> nodes<00:19:28.440> uh<00:19:29.160> are<00:19:29.400> you<00:19:29.580> sending<00:19:29.880> you<00:19:29.940> these 00:19:30.230 --> 00:19:30.240 align:start position:0% which nodes uh are you sending you these 00:19:30.240 --> 00:19:31.909 align:start position:0% which nodes uh are you sending you these duplicates<00:19:30.720> and<00:19:31.140> which<00:19:31.260> ones<00:19:31.500> are<00:19:31.620> sending 00:19:31.909 --> 00:19:31.919 align:start position:0% duplicates and which ones are sending 00:19:31.919 --> 00:19:33.470 align:start position:0% duplicates and which ones are sending you<00:19:32.039> late<00:19:32.340> duplicates<00:19:32.880> and<00:19:33.059> you'll<00:19:33.240> end<00:19:33.360> up 00:19:33.470 --> 00:19:33.480 align:start position:0% you late duplicates and you'll end up 00:19:33.480 --> 00:19:35.750 align:start position:0% you late duplicates and you'll end up having<00:19:33.660> some<00:19:33.960> distribution<00:19:34.440> of 00:19:35.750 --> 00:19:35.760 align:start position:0% having some distribution of 00:19:35.760 --> 00:19:37.850 align:start position:0% having some distribution of um<00:19:35.820> the<00:19:36.539> the<00:19:36.660> number<00:19:36.840> of<00:19:37.020> duplicates<00:19:37.440> you<00:19:37.679> get 00:19:37.850 --> 00:19:37.860 align:start position:0% um the the number of duplicates you get 00:19:37.860 --> 00:19:40.549 align:start position:0% um the the number of duplicates you get and<00:19:38.400> the<00:19:38.580> latency<00:19:38.940> so<00:19:39.299> it<00:19:39.419> could<00:19:39.600> be<00:19:39.720> that<00:19:40.080> Paul 00:19:40.549 --> 00:19:40.559 align:start position:0% and the latency so it could be that Paul 00:19:40.559 --> 00:19:42.350 align:start position:0% and the latency so it could be that Paul over<00:19:40.860> here<00:19:40.980> in<00:19:41.160> the<00:19:41.280> front<00:19:41.400> constantly<00:19:42.000> sends 00:19:42.350 --> 00:19:42.360 align:start position:0% over here in the front constantly sends 00:19:42.360 --> 00:19:44.510 align:start position:0% over here in the front constantly sends me<00:19:42.480> some<00:19:42.960> late<00:19:43.200> duplicate<00:19:43.740> three<00:19:44.280> seconds 00:19:44.510 --> 00:19:44.520 align:start position:0% me some late duplicate three seconds 00:19:44.520 --> 00:19:46.970 align:start position:0% me some late duplicate three seconds late<00:19:44.880> whereas<00:19:45.780> Sean's<00:19:46.380> sending<00:19:46.620> it<00:19:46.740> to<00:19:46.860> me 00:19:46.970 --> 00:19:46.980 align:start position:0% late whereas Sean's sending it to me 00:19:46.980 --> 00:19:49.010 align:start position:0% late whereas Sean's sending it to me straight<00:19:47.160> away<00:19:47.280> instantly<00:19:47.820> so<00:19:48.360> I<00:19:48.660> come<00:19:48.840> up 00:19:49.010 --> 00:19:49.020 align:start position:0% straight away instantly so I come up 00:19:49.020 --> 00:19:51.350 align:start position:0% straight away instantly so I come up with<00:19:49.280> essentially<00:19:50.280> a<00:19:50.460> choking<00:19:50.820> strategy<00:19:51.240> is 00:19:51.350 --> 00:19:51.360 align:start position:0% with essentially a choking strategy is 00:19:51.360 --> 00:19:53.990 align:start position:0% with essentially a choking strategy is what<00:19:51.539> we<00:19:51.660> call<00:19:51.840> it<00:19:52.020> where<00:19:52.740> we<00:19:53.340> look<00:19:53.520> at<00:19:53.640> all<00:19:53.880> of 00:19:53.990 --> 00:19:54.000 align:start position:0% what we call it where we look at all of 00:19:54.000 --> 00:19:56.110 align:start position:0% what we call it where we look at all of the<00:19:54.120> distribution<00:19:54.539> of<00:19:55.080> people<00:19:55.320> sending<00:19:55.799> us 00:19:56.110 --> 00:19:56.120 align:start position:0% the distribution of people sending us 00:19:56.120 --> 00:19:58.549 align:start position:0% the distribution of people sending us duplicates<00:19:57.120> and<00:19:57.600> the<00:19:57.720> ones<00:19:57.900> that<00:19:58.020> are<00:19:58.140> late<00:19:58.320> or 00:19:58.549 --> 00:19:58.559 align:start position:0% duplicates and the ones that are late or 00:19:58.559 --> 00:20:00.230 align:start position:0% duplicates and the ones that are late or the<00:19:58.679> ones<00:19:58.799> that<00:19:58.919> have<00:19:59.039> lower<00:19:59.220> latency<00:19:59.700> and<00:20:00.120> we 00:20:00.230 --> 00:20:00.240 align:start position:0% the ones that have lower latency and we 00:20:00.240 --> 00:20:02.330 align:start position:0% the ones that have lower latency and we send<00:20:00.419> a<00:20:00.660> message<00:20:00.840> called<00:20:01.080> a<00:20:01.320> choke<00:20:01.500> so<00:20:02.039> in<00:20:02.160> this 00:20:02.330 --> 00:20:02.340 align:start position:0% send a message called a choke so in this 00:20:02.340 --> 00:20:04.310 align:start position:0% send a message called a choke so in this example<00:20:02.640> we<00:20:02.880> say<00:20:03.059> I'm<00:20:03.539> going<00:20:03.720> to<00:20:03.780> choke<00:20:04.020> Paul 00:20:04.310 --> 00:20:04.320 align:start position:0% example we say I'm going to choke Paul 00:20:04.320 --> 00:20:07.310 align:start position:0% example we say I'm going to choke Paul because<00:20:05.039> he<00:20:06.000> is<00:20:06.179> sending<00:20:06.660> me<00:20:06.780> late<00:20:06.960> messages 00:20:07.310 --> 00:20:07.320 align:start position:0% because he is sending me late messages 00:20:07.320 --> 00:20:09.650 align:start position:0% because he is sending me late messages all<00:20:07.679> the<00:20:07.799> time<00:20:07.919> what<00:20:08.820> the<00:20:08.880> choke<00:20:09.120> message<00:20:09.360> does 00:20:09.650 --> 00:20:09.660 align:start position:0% all the time what the choke message does 00:20:09.660 --> 00:20:11.810 align:start position:0% all the time what the choke message does is<00:20:09.780> it<00:20:09.960> indicates<00:20:10.320> to<00:20:10.559> Paul<00:20:10.799> to<00:20:11.039> no<00:20:11.580> longer 00:20:11.810 --> 00:20:11.820 align:start position:0% is it indicates to Paul to no longer 00:20:11.820 --> 00:20:14.810 align:start position:0% is it indicates to Paul to no longer send<00:20:12.059> me<00:20:12.299> these<00:20:12.960> messages<00:20:13.280> over<00:20:14.280> the<00:20:14.520> mesh 00:20:14.810 --> 00:20:14.820 align:start position:0% send me these messages over the mesh 00:20:14.820 --> 00:20:16.789 align:start position:0% send me these messages over the mesh instead<00:20:15.240> he<00:20:15.480> does<00:20:15.660> a<00:20:15.900> process<00:20:16.200> called<00:20:16.440> gossip 00:20:16.789 --> 00:20:16.799 align:start position:0% instead he does a process called gossip 00:20:16.799 --> 00:20:18.049 align:start position:0% instead he does a process called gossip where<00:20:17.039> he<00:20:17.160> just<00:20:17.280> sends<00:20:17.520> me<00:20:17.580> like<00:20:17.760> the<00:20:17.880> message 00:20:18.049 --> 00:20:18.059 align:start position:0% where he just sends me like the message 00:20:18.059 --> 00:20:21.049 align:start position:0% where he just sends me like the message ID<00:20:18.240> which<00:20:18.600> is<00:20:18.660> a<00:20:18.840> much<00:20:18.960> smaller<00:20:19.320> thing<00:20:19.940> so<00:20:20.940> over 00:20:21.049 --> 00:20:21.059 align:start position:0% ID which is a much smaller thing so over 00:20:21.059 --> 00:20:23.390 align:start position:0% ID which is a much smaller thing so over time<00:20:21.299> if<00:20:21.480> eventually<00:20:22.140> based<00:20:22.860> on<00:20:22.919> your<00:20:22.980> choking 00:20:23.390 --> 00:20:23.400 align:start position:0% time if eventually based on your choking 00:20:23.400 --> 00:20:24.710 align:start position:0% time if eventually based on your choking strategy<00:20:23.700> you<00:20:24.059> should<00:20:24.179> have<00:20:24.419> a<00:20:24.660> more 00:20:24.710 --> 00:20:24.720 align:start position:0% strategy you should have a more 00:20:24.720 --> 00:20:26.150 align:start position:0% strategy you should have a more efficient<00:20:25.020> Mass<00:20:25.260> where<00:20:25.740> you're<00:20:25.919> only 00:20:26.150 --> 00:20:26.160 align:start position:0% efficient Mass where you're only 00:20:26.160 --> 00:20:29.330 align:start position:0% efficient Mass where you're only receiving<00:20:26.700> the<00:20:26.940> messages<00:20:27.620> with<00:20:28.620> a<00:20:29.220> lower 00:20:29.330 --> 00:20:29.340 align:start position:0% receiving the messages with a lower 00:20:29.340 --> 00:20:31.370 align:start position:0% receiving the messages with a lower number<00:20:29.580> of<00:20:29.700> duplicates<00:20:30.179> maybe<00:20:30.780> from<00:20:31.020> just<00:20:31.200> one 00:20:31.370 --> 00:20:31.380 align:start position:0% number of duplicates maybe from just one 00:20:31.380 --> 00:20:32.750 align:start position:0% number of duplicates maybe from just one or<00:20:31.500> two<00:20:31.559> peers<00:20:31.860> where<00:20:32.100> the<00:20:32.220> rest<00:20:32.340> of<00:20:32.460> them<00:20:32.580> are 00:20:32.750 --> 00:20:32.760 align:start position:0% or two peers where the rest of them are 00:20:32.760 --> 00:20:34.909 align:start position:0% or two peers where the rest of them are choked<00:20:33.120> and<00:20:33.780> you<00:20:33.960> still<00:20:34.140> receive<00:20:34.380> gossip<00:20:34.740> from 00:20:34.909 --> 00:20:34.919 align:start position:0% choked and you still receive gossip from 00:20:34.919 --> 00:20:36.770 align:start position:0% choked and you still receive gossip from them<00:20:35.039> so<00:20:35.220> if<00:20:35.340> the<00:20:35.580> two<00:20:35.880> peers<00:20:36.360> that<00:20:36.539> you<00:20:36.660> have 00:20:36.770 --> 00:20:36.780 align:start position:0% them so if the two peers that you have 00:20:36.780 --> 00:20:39.830 align:start position:0% them so if the two peers that you have in<00:20:36.960> your<00:20:37.080> mesh<00:20:37.440> are<00:20:37.980> slow<00:20:38.220> and<00:20:39.179> the<00:20:39.480> other<00:20:39.600> ones 00:20:39.830 --> 00:20:39.840 align:start position:0% in your mesh are slow and the other ones 00:20:39.840 --> 00:20:41.150 align:start position:0% in your mesh are slow and the other ones that<00:20:40.020> you<00:20:40.080> have<00:20:40.200> choked<00:20:40.500> are<00:20:40.620> started<00:20:40.860> sending 00:20:41.150 --> 00:20:41.160 align:start position:0% that you have choked are started sending 00:20:41.160 --> 00:20:42.650 align:start position:0% that you have choked are started sending you<00:20:41.220> message<00:20:41.340> IDs<00:20:41.820> before<00:20:42.000> you<00:20:42.240> send<00:20:42.419> them<00:20:42.539> in 00:20:42.650 --> 00:20:42.660 align:start position:0% you message IDs before you send them in 00:20:42.660 --> 00:20:44.390 align:start position:0% you message IDs before you send them in the<00:20:42.780> mesh<00:20:43.020> we<00:20:43.200> have<00:20:43.380> an<00:20:43.500> unchoked<00:20:44.039> message<00:20:44.100> so 00:20:44.390 --> 00:20:44.400 align:start position:0% the mesh we have an unchoked message so 00:20:44.400 --> 00:20:45.529 align:start position:0% the mesh we have an unchoked message so we<00:20:44.520> can<00:20:44.640> uncheck<00:20:45.000> them<00:20:45.059> and<00:20:45.179> put<00:20:45.299> them<00:20:45.360> back 00:20:45.529 --> 00:20:45.539 align:start position:0% we can uncheck them and put them back 00:20:45.539 --> 00:20:48.890 align:start position:0% we can uncheck them and put them back into<00:20:45.660> the<00:20:45.840> mesh<00:20:46.580> so<00:20:47.580> ultimately<00:20:48.179> the<00:20:48.660> idea 00:20:48.890 --> 00:20:48.900 align:start position:0% into the mesh so ultimately the idea 00:20:48.900 --> 00:20:50.029 align:start position:0% into the mesh so ultimately the idea would<00:20:49.080> be<00:20:49.140> is<00:20:49.320> that<00:20:49.500> you're<00:20:49.740> you're 00:20:50.029 --> 00:20:50.039 align:start position:0% would be is that you're you're 00:20:50.039 --> 00:20:53.930 align:start position:0% would be is that you're you're dynamically<00:20:50.700> changing<00:20:51.539> uh<00:20:52.440> your<00:20:53.220> mesh<00:20:53.580> and 00:20:53.930 --> 00:20:53.940 align:start position:0% dynamically changing uh your mesh and 00:20:53.940 --> 00:20:55.850 align:start position:0% dynamically changing uh your mesh and how<00:20:54.299> many<00:20:54.360> what<00:20:54.660> peers<00:20:55.020> what<00:20:55.380> peers<00:20:55.679> are 00:20:55.850 --> 00:20:55.860 align:start position:0% how many what peers what peers are 00:20:55.860 --> 00:20:57.590 align:start position:0% how many what peers what peers are sending<00:20:56.220> you<00:20:56.280> messages<00:20:56.580> and<00:20:57.299> how<00:20:57.480> fast 00:20:57.590 --> 00:20:57.600 align:start position:0% sending you messages and how fast 00:20:57.600 --> 00:21:00.049 align:start position:0% sending you messages and how fast they're<00:20:57.780> doing<00:20:58.020> it<00:20:58.460> in<00:20:59.460> order<00:20:59.580> to<00:20:59.760> try<00:20:59.880> and 00:21:00.049 --> 00:21:00.059 align:start position:0% they're doing it in order to try and 00:21:00.059 --> 00:21:02.210 align:start position:0% they're doing it in order to try and make<00:21:00.179> it<00:21:00.360> essentially<00:21:00.840> more<00:21:01.020> efficient 00:21:02.210 --> 00:21:02.220 align:start position:0% make it essentially more efficient 00:21:02.220 --> 00:21:04.070 align:start position:0% make it essentially more efficient hopefully<00:21:02.820> that<00:21:03.000> makes<00:21:03.179> sense<00:21:03.299> I<00:21:03.539> take 00:21:04.070 --> 00:21:04.080 align:start position:0% hopefully that makes sense I take 00:21:04.080 --> 00:21:05.810 align:start position:0% hopefully that makes sense I take questions<00:21:04.260> afterwards 00:21:05.810 --> 00:21:05.820 align:start position:0% questions afterwards 00:21:05.820 --> 00:21:07.789 align:start position:0% questions afterwards does<00:21:06.419> this<00:21:06.600> work<00:21:06.840> I<00:21:07.140> guess<00:21:07.260> is<00:21:07.440> the<00:21:07.620> question 00:21:07.789 --> 00:21:07.799 align:start position:0% does this work I guess is the question 00:21:07.799 --> 00:21:09.169 align:start position:0% does this work I guess is the question there's<00:21:08.220> been<00:21:08.460> some<00:21:08.640> preliminary 00:21:09.169 --> 00:21:09.179 align:start position:0% there's been some preliminary 00:21:09.179 --> 00:21:11.450 align:start position:0% there's been some preliminary simulations<00:21:09.900> on<00:21:10.200> this<00:21:10.320> uh<00:21:10.919> as<00:21:11.100> I<00:21:11.220> mentioned 00:21:11.450 --> 00:21:11.460 align:start position:0% simulations on this uh as I mentioned 00:21:11.460 --> 00:21:13.970 align:start position:0% simulations on this uh as I mentioned viso<00:21:12.000> from<00:21:12.240> lip<00:21:12.539> P2P<00:21:12.840> and<00:21:13.020> protocol<00:21:13.200> Labs<00:21:13.620> has 00:21:13.970 --> 00:21:13.980 align:start position:0% viso from lip P2P and protocol Labs has 00:21:13.980 --> 00:21:16.310 align:start position:0% viso from lip P2P and protocol Labs has done<00:21:14.280> a<00:21:14.760> work<00:21:14.880> done<00:21:15.299> some<00:21:15.480> work<00:21:15.600> on<00:21:15.780> this<00:21:15.900> he's 00:21:16.310 --> 00:21:16.320 align:start position:0% done a work done some work on this he's 00:21:16.320 --> 00:21:18.890 align:start position:0% done a work done some work on this he's built<00:21:16.740> a<00:21:16.799> generic<00:21:17.160> simulation<00:21:17.640> uh<00:21:18.240> from<00:21:18.480> for 00:21:18.890 --> 00:21:18.900 align:start position:0% built a generic simulation uh from for 00:21:18.900 --> 00:21:22.789 align:start position:0% built a generic simulation uh from for the<00:21:19.500> Go<00:21:19.919> version<00:21:20.280> of<00:21:20.520> this<00:21:20.700> with<00:21:21.179> 250<00:21:21.840> 500<00:21:22.500> and 00:21:22.789 --> 00:21:22.799 align:start position:0% the Go version of this with 250 500 and 00:21:22.799 --> 00:21:24.250 align:start position:0% the Go version of this with 250 500 and a<00:21:22.919> thousand<00:21:23.220> nodes 00:21:24.250 --> 00:21:24.260 align:start position:0% a thousand nodes 00:21:24.260 --> 00:21:27.169 align:start position:0% a thousand nodes and<00:21:25.260> so<00:21:25.440> this<00:21:25.679> is<00:21:25.799> this<00:21:26.520> is<00:21:26.580> with<00:21:26.760> a<00:21:26.940> mesh 00:21:27.169 --> 00:21:27.179 align:start position:0% and so this is this is with a mesh 00:21:27.179 --> 00:21:28.970 align:start position:0% and so this is this is with a mesh degree<00:21:27.360> of<00:21:27.539> six<00:21:27.720> so<00:21:27.960> there's<00:21:28.140> roughly<00:21:28.620> about<00:21:28.740> a 00:21:28.970 --> 00:21:28.980 align:start position:0% degree of six so there's roughly about a 00:21:28.980 --> 00:21:30.409 align:start position:0% degree of six so there's roughly about a six<00:21:29.100> times<00:21:29.280> amplification<00:21:29.940> if<00:21:30.120> you<00:21:30.240> look<00:21:30.360> at 00:21:30.409 --> 00:21:30.419 align:start position:0% six times amplification if you look at 00:21:30.419 --> 00:21:32.149 align:start position:0% six times amplification if you look at the<00:21:30.539> messages<00:21:30.720> in<00:21:31.020> these<00:21:31.140> simulations<00:21:31.559> but 00:21:32.149 --> 00:21:32.159 align:start position:0% the messages in these simulations but 00:21:32.159 --> 00:21:33.710 align:start position:0% the messages in these simulations but pretty<00:21:32.400> much<00:21:32.520> in<00:21:32.700> all<00:21:33.059> of<00:21:33.179> the<00:21:33.299> simulations 00:21:33.710 --> 00:21:33.720 align:start position:0% pretty much in all of the simulations 00:21:33.720 --> 00:21:36.230 align:start position:0% pretty much in all of the simulations what<00:21:34.320> this<00:21:34.500> graph<00:21:34.679> is<00:21:34.860> showing<00:21:35.159> you<00:21:35.280> is<00:21:36.000> that 00:21:36.230 --> 00:21:36.240 align:start position:0% what this graph is showing you is that 00:21:36.240 --> 00:21:38.390 align:start position:0% what this graph is showing you is that you<00:21:36.419> get<00:21:36.539> roughly<00:21:36.960> a<00:21:37.140> 50<00:21:37.320> reduction<00:21:38.100> in<00:21:38.280> the 00:21:38.390 --> 00:21:38.400 align:start position:0% you get roughly a 50 reduction in the 00:21:38.400 --> 00:21:41.029 align:start position:0% you get roughly a 50 reduction in the duplicates<00:21:38.820> from<00:21:39.000> every<00:21:39.240> sub<00:21:39.600> now<00:21:40.320> as<00:21:40.740> I<00:21:40.919> said 00:21:41.029 --> 00:21:41.039 align:start position:0% duplicates from every sub now as I said 00:21:41.039 --> 00:21:42.529 align:start position:0% duplicates from every sub now as I said there's<00:21:41.220> a<00:21:41.400> choking<00:21:41.760> and<00:21:41.940> a<00:21:42.059> non-choking 00:21:42.529 --> 00:21:42.539 align:start position:0% there's a choking and a non-choking 00:21:42.539 --> 00:21:44.210 align:start position:0% there's a choking and a non-choking strategy<00:21:42.840> which<00:21:43.080> are<00:21:43.200> left<00:21:43.440> somewhat<00:21:43.860> generic 00:21:44.210 --> 00:21:44.220 align:start position:0% strategy which are left somewhat generic 00:21:44.220 --> 00:21:46.010 align:start position:0% strategy which are left somewhat generic and<00:21:44.400> I<00:21:44.520> think<00:21:44.640> we<00:21:44.820> can<00:21:44.940> tune<00:21:45.179> this<00:21:45.539> to<00:21:45.840> be 00:21:46.010 --> 00:21:46.020 align:start position:0% and I think we can tune this to be 00:21:46.020 --> 00:21:47.930 align:start position:0% and I think we can tune this to be significant<00:21:46.559> especially<00:21:47.220> if<00:21:47.340> we<00:21:47.520> target<00:21:47.640> it 00:21:47.930 --> 00:21:47.940 align:start position:0% significant especially if we target it 00:21:47.940 --> 00:21:49.909 align:start position:0% significant especially if we target it for<00:21:48.179> the<00:21:48.360> ethereum<00:21:48.780> network<00:21:48.960> I<00:21:49.500> think<00:21:49.620> we<00:21:49.740> can 00:21:49.909 --> 00:21:49.919 align:start position:0% for the ethereum network I think we can 00:21:49.919 --> 00:21:52.789 align:start position:0% for the ethereum network I think we can get<00:21:50.039> better<00:21:50.340> versions<00:21:50.820> of<00:21:50.940> this<00:21:51.059> but<00:21:51.780> at<00:21:52.320> face 00:21:52.789 --> 00:21:52.799 align:start position:0% get better versions of this but at face 00:21:52.799 --> 00:21:53.930 align:start position:0% get better versions of this but at face value<00:21:53.039> it<00:21:53.220> looks<00:21:53.400> like<00:21:53.460> you<00:21:53.580> can<00:21:53.640> reduce<00:21:53.760> the 00:21:53.930 --> 00:21:53.940 align:start position:0% value it looks like you can reduce the 00:21:53.940 --> 00:21:56.270 align:start position:0% value it looks like you can reduce the GPS<00:21:54.120> by<00:21:54.539> 50<00:21:54.659> just<00:21:55.140> by<00:21:55.380> adding<00:21:55.860> these<00:21:56.039> kinds<00:21:56.220> of 00:21:56.270 --> 00:21:56.280 align:start position:0% GPS by 50 just by adding these kinds of 00:21:56.280 --> 00:21:57.470 align:start position:0% GPS by 50 just by adding these kinds of messages 00:21:57.470 --> 00:21:57.480 align:start position:0% messages 00:21:57.480 --> 00:21:58.430 align:start position:0% messages um the<00:21:57.600> next<00:21:57.780> thing<00:21:57.900> we<00:21:58.020> probably<00:21:58.260> should 00:21:58.430 --> 00:21:58.440 align:start position:0% um the next thing we probably should 00:21:58.440 --> 00:22:00.950 align:start position:0% um the next thing we probably should talk<00:21:58.620> about<00:21:58.679> is<00:21:58.980> latency<00:21:59.400> uh 00:22:00.950 --> 00:22:00.960 align:start position:0% talk about is latency uh 00:22:00.960 --> 00:22:03.110 align:start position:0% talk about is latency uh I<00:22:01.559> kind<00:22:01.740> of<00:22:01.860> suggested<00:22:02.220> that<00:22:02.340> we<00:22:02.460> could<00:22:02.580> get<00:22:02.760> a 00:22:03.110 --> 00:22:03.120 align:start position:0% I kind of suggested that we could get a 00:22:03.120 --> 00:22:04.970 align:start position:0% I kind of suggested that we could get a reduction<00:22:03.659> in<00:22:03.900> duplicates<00:22:04.380> and<00:22:04.559> reduction<00:22:04.860> in 00:22:04.970 --> 00:22:04.980 align:start position:0% reduction in duplicates and reduction in 00:22:04.980 --> 00:22:07.850 align:start position:0% reduction in duplicates and reduction in latency<00:22:05.340> uh<00:22:05.940> the<00:22:06.120> initial<00:22:06.360> results<00:22:06.539> that<00:22:06.900> uh 00:22:07.850 --> 00:22:07.860 align:start position:0% latency uh the initial results that uh 00:22:07.860 --> 00:22:10.250 align:start position:0% latency uh the initial results that uh visor<00:22:08.460> has<00:22:08.820> uh<00:22:09.299> completed<00:22:09.600> in<00:22:09.720> a<00:22:09.900> simulation 00:22:10.250 --> 00:22:10.260 align:start position:0% visor has uh completed in a simulation 00:22:10.260 --> 00:22:13.610 align:start position:0% visor has uh completed in a simulation seems<00:22:11.159> that<00:22:11.280> the<00:22:11.520> latency<00:22:11.940> increases<00:22:12.539> so<00:22:12.960> on 00:22:13.610 --> 00:22:13.620 align:start position:0% seems that the latency increases so on 00:22:13.620 --> 00:22:15.770 align:start position:0% seems that the latency increases so on the<00:22:13.740> left<00:22:13.919> is<00:22:14.460> uh<00:22:14.880> Gossip<00:22:15.179> sub<00:22:15.360> latency 00:22:15.770 --> 00:22:15.780 align:start position:0% the left is uh Gossip sub latency 00:22:15.780 --> 00:22:17.770 align:start position:0% the left is uh Gossip sub latency distribution<00:22:16.200> where<00:22:16.500> the<00:22:16.740> buckets<00:22:17.039> are<00:22:17.400> like 00:22:17.770 --> 00:22:17.780 align:start position:0% distribution where the buckets are like 00:22:17.780 --> 00:22:20.210 align:start position:0% distribution where the buckets are like milliseconds<00:22:18.780> since<00:22:19.500> you<00:22:19.679> received<00:22:20.100> the 00:22:20.210 --> 00:22:20.220 align:start position:0% milliseconds since you received the 00:22:20.220 --> 00:22:22.310 align:start position:0% milliseconds since you received the message<00:22:20.340> and<00:22:20.880> on<00:22:21.059> the<00:22:21.179> right<00:22:21.299> is<00:22:21.720> uh<00:22:22.020> episode 00:22:22.310 --> 00:22:22.320 align:start position:0% message and on the right is uh episode 00:22:22.320 --> 00:22:25.190 align:start position:0% message and on the right is uh episode so<00:22:23.220> you<00:22:23.400> we<00:22:23.820> receive<00:22:24.480> more<00:22:24.659> messages<00:22:24.900> with 00:22:25.190 --> 00:22:25.200 align:start position:0% so you we receive more messages with 00:22:25.200 --> 00:22:27.470 align:start position:0% so you we receive more messages with higher<00:22:25.500> latency<00:22:25.799> in<00:22:26.100> these<00:22:26.340> simulations<00:22:26.760> but 00:22:27.470 --> 00:22:27.480 align:start position:0% higher latency in these simulations but 00:22:27.480 --> 00:22:30.230 align:start position:0% higher latency in these simulations but as<00:22:27.659> I<00:22:27.840> was<00:22:27.960> saying<00:22:28.260> uh<00:22:28.740> these<00:22:29.220> are 00:22:30.230 --> 00:22:30.240 align:start position:0% as I was saying uh these are 00:22:30.240 --> 00:22:32.810 align:start position:0% as I was saying uh these are somewhat<00:22:30.900> generic<00:22:31.320> the<00:22:31.799> the<00:22:31.980> topology<00:22:32.580> of 00:22:32.810 --> 00:22:32.820 align:start position:0% somewhat generic the the topology of 00:22:32.820 --> 00:22:34.190 align:start position:0% somewhat generic the the topology of these<00:22:33.000> does<00:22:33.179> not<00:22:33.360> look<00:22:33.480> like<00:22:33.659> the<00:22:33.840> ethereum 00:22:34.190 --> 00:22:34.200 align:start position:0% these does not look like the ethereum 00:22:34.200 --> 00:22:36.649 align:start position:0% these does not look like the ethereum network<00:22:34.320> that<00:22:35.220> we<00:22:35.340> have<00:22:35.460> and<00:22:36.120> these<00:22:36.419> can<00:22:36.539> be 00:22:36.649 --> 00:22:36.659 align:start position:0% network that we have and these can be 00:22:36.659 --> 00:22:38.750 align:start position:0% network that we have and these can be highly<00:22:37.140> tuned<00:22:37.620> to<00:22:37.740> what<00:22:38.159> we<00:22:38.280> need<00:22:38.400> there's<00:22:38.580> a 00:22:38.750 --> 00:22:38.760 align:start position:0% highly tuned to what we need there's a 00:22:38.760 --> 00:22:40.430 align:start position:0% highly tuned to what we need there's a lot<00:22:38.820> of<00:22:38.940> like<00:22:39.240> research<00:22:39.659> work<00:22:39.840> going<00:22:40.020> in<00:22:40.260> there 00:22:40.430 --> 00:22:40.440 align:start position:0% lot of like research work going in there 00:22:40.440 --> 00:22:42.350 align:start position:0% lot of like research work going in there there's<00:22:41.280> a<00:22:41.460> few<00:22:41.580> people<00:22:41.820> in<00:22:42.059> the<00:22:42.120> audience 00:22:42.350 --> 00:22:42.360 align:start position:0% there's a few people in the audience 00:22:42.360 --> 00:22:44.270 align:start position:0% there's a few people in the audience where<00:22:42.600> I<00:22:42.780> think<00:22:43.080> that<00:22:43.260> I've<00:22:43.440> promised<00:22:43.860> uh 00:22:44.270 --> 00:22:44.280 align:start position:0% where I think that I've promised uh 00:22:44.280 --> 00:22:47.990 align:start position:0% where I think that I've promised uh results<00:22:44.520> for<00:22:44.940> a<00:22:45.620> mainnet<00:22:46.620> version<00:22:46.860> of<00:22:47.100> this<00:22:47.280> so 00:22:47.990 --> 00:22:48.000 align:start position:0% results for a mainnet version of this so 00:22:48.000 --> 00:22:50.390 align:start position:0% results for a mainnet version of this so uh<00:22:48.419> asset<00:22:48.720> Sigma<00:22:49.020> Prime<00:22:49.200> we've<00:22:49.559> built<00:22:49.980> uh 00:22:50.390 --> 00:22:50.400 align:start position:0% uh asset Sigma Prime we've built uh 00:22:50.400 --> 00:22:51.770 align:start position:0% uh asset Sigma Prime we've built uh essentially<00:22:50.760> a<00:22:50.940> production<00:22:51.299> version<00:22:51.539> of 00:22:51.770 --> 00:22:51.780 align:start position:0% essentially a production version of 00:22:51.780 --> 00:22:54.230 align:start position:0% essentially a production version of episode<00:22:52.020> inside<00:22:52.500> gossip<00:22:52.980> sub<00:22:53.159> the<00:22:53.820> advantages 00:22:54.230 --> 00:22:54.240 align:start position:0% episode inside gossip sub the advantages 00:22:54.240 --> 00:22:56.149 align:start position:0% episode inside gossip sub the advantages are<00:22:54.539> that<00:22:54.720> it's<00:22:54.840> backwards<00:22:55.260> compatible<00:22:55.559> so<00:22:55.919> we 00:22:56.149 --> 00:22:56.159 align:start position:0% are that it's backwards compatible so we 00:22:56.159 --> 00:22:59.090 align:start position:0% are that it's backwards compatible so we can<00:22:56.340> release<00:22:56.640> it<00:22:57.000> in<00:22:57.600> in<00:22:57.960> our<00:22:58.200> clients<00:22:58.620> it'll 00:22:59.090 --> 00:22:59.100 align:start position:0% can release it in in our clients it'll 00:22:59.100 --> 00:23:00.830 align:start position:0% can release it in in our clients it'll work<00:22:59.280> existingly<00:23:00.000> with<00:23:00.179> every<00:23:00.360> other<00:23:00.480> peer 00:23:00.830 --> 00:23:00.840 align:start position:0% work existingly with every other peer 00:23:00.840 --> 00:23:02.750 align:start position:0% work existingly with every other peer and<00:23:00.960> every<00:23:01.080> other<00:23:01.260> gossip<00:23:01.620> sub 00:23:02.750 --> 00:23:02.760 align:start position:0% and every other gossip sub 00:23:02.760 --> 00:23:04.669 align:start position:0% and every other gossip sub um<00:23:02.820> node<00:23:03.480> on<00:23:03.600> the<00:23:03.720> network<00:23:03.840> but<00:23:04.320> if<00:23:04.500> there 00:23:04.669 --> 00:23:04.679 align:start position:0% um node on the network but if there 00:23:04.679 --> 00:23:06.649 align:start position:0% um node on the network but if there happens<00:23:04.980> to<00:23:05.220> be<00:23:05.340> another<00:23:05.520> episode<00:23:05.820> node<00:23:06.539> on 00:23:06.649 --> 00:23:06.659 align:start position:0% happens to be another episode node on 00:23:06.659 --> 00:23:07.909 align:start position:0% happens to be another episode node on the<00:23:06.780> network<00:23:06.840> we<00:23:07.140> can<00:23:07.260> start 00:23:07.909 --> 00:23:07.919 align:start position:0% the network we can start 00:23:07.919 --> 00:23:09.649 align:start position:0% the network we can start getting<00:23:08.400> this<00:23:08.640> bandwidth<00:23:09.059> minimization<00:23:09.480> so 00:23:09.649 --> 00:23:09.659 align:start position:0% getting this bandwidth minimization so 00:23:09.659 --> 00:23:10.789 align:start position:0% getting this bandwidth minimization so the<00:23:09.780> fact<00:23:09.900> that<00:23:10.020> it's<00:23:10.140> backwards<00:23:10.500> compatible 00:23:10.789 --> 00:23:10.799 align:start position:0% the fact that it's backwards compatible 00:23:10.799 --> 00:23:12.350 align:start position:0% the fact that it's backwards compatible is<00:23:11.220> super<00:23:11.400> handy<00:23:11.760> we<00:23:11.880> can<00:23:12.000> kind<00:23:12.179> of<00:23:12.240> just 00:23:12.350 --> 00:23:12.360 align:start position:0% is super handy we can kind of just 00:23:12.360 --> 00:23:14.690 align:start position:0% is super handy we can kind of just release<00:23:12.480> it<00:23:12.720> whenever<00:23:12.960> we<00:23:13.140> want<00:23:13.400> we're<00:23:14.400> also 00:23:14.690 --> 00:23:14.700 align:start position:0% release it whenever we want we're also 00:23:14.700 --> 00:23:16.490 align:start position:0% release it whenever we want we're also working<00:23:14.820> on<00:23:15.059> a<00:23:15.179> mainnet<00:23:15.600> simulation<00:23:16.020> so<00:23:16.380> that 00:23:16.490 --> 00:23:16.500 align:start position:0% working on a mainnet simulation so that 00:23:16.500 --> 00:23:18.710 align:start position:0% working on a mainnet simulation so that we<00:23:16.620> can<00:23:16.740> actually<00:23:16.860> simulate<00:23:17.460> the<00:23:18.240> bandwidth 00:23:18.710 --> 00:23:18.720 align:start position:0% we can actually simulate the bandwidth 00:23:18.720 --> 00:23:21.409 align:start position:0% we can actually simulate the bandwidth that<00:23:18.780> exists<00:23:19.080> on<00:23:19.200> mainnet<00:23:19.679> and<00:23:19.919> then<00:23:20.240> apply<00:23:21.240> Fe 00:23:21.409 --> 00:23:21.419 align:start position:0% that exists on mainnet and then apply Fe 00:23:21.419 --> 00:23:23.270 align:start position:0% that exists on mainnet and then apply Fe sub<00:23:21.720> and<00:23:21.960> then<00:23:22.080> get<00:23:22.260> essentially<00:23:22.740> more 00:23:23.270 --> 00:23:23.280 align:start position:0% sub and then get essentially more 00:23:23.280 --> 00:23:25.850 align:start position:0% sub and then get essentially more specific<00:23:24.240> data<00:23:24.720> that's<00:23:24.900> more<00:23:25.200> robust<00:23:25.500> and<00:23:25.679> how 00:23:25.850 --> 00:23:25.860 align:start position:0% specific data that's more robust and how 00:23:25.860 --> 00:23:28.430 align:start position:0% specific data that's more robust and how we<00:23:26.159> can<00:23:26.280> actually<00:23:26.400> apply<00:23:26.760> this<00:23:26.940> to<00:23:27.360> what<00:23:28.260> it 00:23:28.430 --> 00:23:28.440 align:start position:0% we can actually apply this to what it 00:23:28.440 --> 00:23:29.750 align:start position:0% we can actually apply this to what it would<00:23:28.559> look<00:23:28.620> like<00:23:28.740> on<00:23:28.860> an<00:23:29.039> ethereum<00:23:29.400> two<00:23:29.580> main 00:23:29.750 --> 00:23:29.760 align:start position:0% would look like on an ethereum two main 00:23:29.760 --> 00:23:30.610 align:start position:0% would look like on an ethereum two main net 00:23:30.610 --> 00:23:30.620 align:start position:0% net 00:23:30.620 --> 00:23:32.990 align:start position:0% net these<00:23:31.620> will<00:23:31.740> publish<00:23:32.159> results<00:23:32.520> from<00:23:32.820> this 00:23:32.990 --> 00:23:33.000 align:start position:0% these will publish results from this 00:23:33.000 --> 00:23:35.330 align:start position:0% these will publish results from this very<00:23:33.840> soon<00:23:34.020> and<00:23:34.140> if<00:23:34.260> you're<00:23:34.380> interested<00:23:34.679> just 00:23:35.330 --> 00:23:35.340 align:start position:0% very soon and if you're interested just 00:23:35.340 --> 00:23:36.830 align:start position:0% very soon and if you're interested just let<00:23:35.520> us<00:23:35.640> know 00:23:36.830 --> 00:23:36.840 align:start position:0% let us know 00:23:36.840 --> 00:23:40.250 align:start position:0% let us know so<00:23:37.559> the<00:23:37.980> title<00:23:38.220> of<00:23:38.280> the<00:23:38.400> talk<00:23:38.580> was<00:23:38.940> reducing<00:23:39.780> if 00:23:40.250 --> 00:23:40.260 align:start position:0% so the title of the talk was reducing if 00:23:40.260 --> 00:23:41.510 align:start position:0% so the title of the talk was reducing if I<00:23:40.440> can<00:23:40.559> remember<00:23:40.679> the<00:23:40.860> title<00:23:41.100> of<00:23:41.159> the<00:23:41.220> talk<00:23:41.340> was 00:23:41.510 --> 00:23:41.520 align:start position:0% I can remember the title of the talk was 00:23:41.520 --> 00:23:43.510 align:start position:0% I can remember the title of the talk was reducing<00:23:42.120> bandwidth<00:23:42.539> for 00:23:43.510 --> 00:23:43.520 align:start position:0% reducing bandwidth for 00:23:43.520 --> 00:23:45.830 align:start position:0% reducing bandwidth for institutional<00:23:44.520> and<00:23:44.760> homesteakers<00:23:45.360> so<00:23:45.539> if 00:23:45.830 --> 00:23:45.840 align:start position:0% institutional and homesteakers so if 00:23:45.840 --> 00:23:47.930 align:start position:0% institutional and homesteakers so if you're<00:23:46.020> an<00:23:46.320> Institutional<00:23:46.919> or<00:23:47.280> a<00:23:47.400> homesteaker 00:23:47.930 --> 00:23:47.940 align:start position:0% you're an Institutional or a homesteaker 00:23:47.940 --> 00:23:49.549 align:start position:0% you're an Institutional or a homesteaker and<00:23:48.000> you<00:23:48.120> came<00:23:48.240> here<00:23:48.480> being<00:23:48.659> like<00:23:48.900> how<00:23:49.380> do<00:23:49.500> I 00:23:49.549 --> 00:23:49.559 align:start position:0% and you came here being like how do I 00:23:49.559 --> 00:23:51.350 align:start position:0% and you came here being like how do I get<00:23:49.679> all<00:23:49.740> these<00:23:49.919> bandwidth<00:23:50.340> gains 00:23:51.350 --> 00:23:51.360 align:start position:0% get all these bandwidth gains 00:23:51.360 --> 00:23:53.690 align:start position:0% get all these bandwidth gains what<00:23:51.900> do<00:23:52.080> you<00:23:52.200> need<00:23:52.260> to<00:23:52.380> do<00:23:52.500> in<00:23:52.740> order<00:23:52.919> to<00:23:53.159> get<00:23:53.460> a 00:23:53.690 --> 00:23:53.700 align:start position:0% what do you need to do in order to get a 00:23:53.700 --> 00:23:57.110 align:start position:0% what do you need to do in order to get a 90<00:23:53.880> reduction<00:23:54.679> the<00:23:55.679> answer<00:23:55.799> is<00:23:56.159> nothing<00:23:56.520> you 00:23:57.110 --> 00:23:57.120 align:start position:0% 90 reduction the answer is nothing you 00:23:57.120 --> 00:23:59.210 align:start position:0% 90 reduction the answer is nothing you just<00:23:57.360> have<00:23:57.480> to<00:23:57.600> wait<00:23:57.780> we'll<00:23:58.140> release<00:23:58.320> it<00:23:58.679> maybe 00:23:59.210 --> 00:23:59.220 align:start position:0% just have to wait we'll release it maybe 00:23:59.220 --> 00:24:00.789 align:start position:0% just have to wait we'll release it maybe run<00:23:59.460> a<00:23:59.640> lighthouse<00:23:59.880> node 00:24:00.789 --> 00:24:00.799 align:start position:0% run a lighthouse node 00:24:00.799 --> 00:24:03.649 align:start position:0% run a lighthouse node and<00:24:01.799> hopefully<00:24:02.460> yeah<00:24:02.700> we'll<00:24:02.940> we'll<00:24:03.179> be<00:24:03.600> able 00:24:03.649 --> 00:24:03.659 align:start position:0% and hopefully yeah we'll we'll be able 00:24:03.659 --> 00:24:05.330 align:start position:0% and hopefully yeah we'll we'll be able to<00:24:03.720> reduce<00:24:03.840> the<00:24:04.080> bandwidth<00:24:04.500> but<00:24:04.980> that's<00:24:05.220> the 00:24:05.330 --> 00:24:05.340 align:start position:0% to reduce the bandwidth but that's the 00:24:05.340 --> 00:24:07.010 align:start position:0% to reduce the bandwidth but that's the end<00:24:05.460> of<00:24:05.580> our<00:24:05.640> talk<00:24:05.820> thank<00:24:06.179> you 00:24:07.010 --> 00:24:07.020 align:start position:0% end of our talk thank you 00:24:07.020 --> 00:24:08.930 align:start position:0% end of our talk thank you [Applause] 00:24:08.930 --> 00:24:08.940 align:start position:0% [Applause] 00:24:08.940 --> 00:24:11.090 align:start position:0% [Applause] some<00:24:09.360> minutes<00:24:09.600> for<00:24:09.960> questions 00:24:11.090 --> 00:24:11.100 align:start position:0% some minutes for questions 00:24:11.100 --> 00:24:12.830 align:start position:0% some minutes for questions um<00:24:11.220> great<00:24:11.460> talk<00:24:11.700> guys<00:24:12.059> is<00:24:12.480> this<00:24:12.659> something 00:24:12.830 --> 00:24:12.840 align:start position:0% um great talk guys is this something 00:24:12.840 --> 00:24:14.990 align:start position:0% um great talk guys is this something that's<00:24:13.140> bad<00:24:13.380> was<00:24:13.620> compatible<00:24:14.159> meaning<00:24:14.580> that 00:24:14.990 --> 00:24:15.000 align:start position:0% that's bad was compatible meaning that 00:24:15.000 --> 00:24:17.510 align:start position:0% that's bad was compatible meaning that clients<00:24:15.600> can<00:24:15.840> gradually<00:24:16.200> roll<00:24:16.620> this<00:24:16.860> out<00:24:17.159> as 00:24:17.510 --> 00:24:17.520 align:start position:0% clients can gradually roll this out as 00:24:17.520 --> 00:24:19.789 align:start position:0% clients can gradually roll this out as time<00:24:17.700> goes<00:24:18.120> or<00:24:18.480> is<00:24:18.780> it<00:24:19.020> something<00:24:19.200> that<00:24:19.500> we<00:24:19.679> all 00:24:19.789 --> 00:24:19.799 align:start position:0% time goes or is it something that we all 00:24:19.799 --> 00:24:22.549 align:start position:0% time goes or is it something that we all have<00:24:19.980> to<00:24:20.159> upgrade<00:24:20.700> at<00:24:21.000> once<00:24:21.380> here<00:24:22.380> we're 00:24:22.549 --> 00:24:22.559 align:start position:0% have to upgrade at once here we're 00:24:22.559 --> 00:24:25.970 align:start position:0% have to upgrade at once here we're handling<00:24:23.100> basically<00:24:23.700> protocol<00:24:24.120> versions<00:24:24.980> so 00:24:25.970 --> 00:24:25.980 align:start position:0% handling basically protocol versions so 00:24:25.980 --> 00:24:29.210 align:start position:0% handling basically protocol versions so we<00:24:26.640> can<00:24:26.820> run<00:24:27.059> against<00:24:27.360> nodes<00:24:28.020> that<00:24:28.380> are 00:24:29.210 --> 00:24:29.220 align:start position:0% we can run against nodes that are 00:24:29.220 --> 00:24:31.669 align:start position:0% we can run against nodes that are episodes<00:24:29.580> compatible<00:24:30.299> and<00:24:30.960> if<00:24:31.320> they're<00:24:31.500> not 00:24:31.669 --> 00:24:31.679 align:start position:0% episodes compatible and if they're not 00:24:31.679 --> 00:24:33.710 align:start position:0% episodes compatible and if they're not then<00:24:31.919> we're<00:24:32.220> just<00:24:32.400> going<00:24:32.520> to<00:24:32.640> run<00:24:32.940> episode 00:24:33.710 --> 00:24:33.720 align:start position:0% then we're just going to run episode 00:24:33.720 --> 00:24:37.789 align:start position:0% then we're just going to run episode version<00:24:34.559> one<00:24:35.220> that<00:24:35.700> one<00:24:35.940> so<00:24:36.480> yeah<00:24:37.260> that's<00:24:37.620> what 00:24:37.789 --> 00:24:37.799 align:start position:0% version one that one so yeah that's what 00:24:37.799 --> 00:24:40.250 align:start position:0% version one that one so yeah that's what we<00:24:38.039> mean<00:24:38.280> with<00:24:38.640> that<00:24:38.820> yeah<00:24:39.539> we<00:24:39.720> add<00:24:39.900> a<00:24:40.080> protocol 00:24:40.250 --> 00:24:40.260 align:start position:0% we mean with that yeah we add a protocol 00:24:40.260 --> 00:24:42.770 align:start position:0% we mean with that yeah we add a protocol ID<00:24:40.500> into<00:24:40.980> the<00:24:41.280> gossips<00:24:41.640> app<00:24:41.880> and<00:24:42.240> so<00:24:42.419> when<00:24:42.659> you 00:24:42.770 --> 00:24:42.780 align:start position:0% ID into the gossips app and so when you 00:24:42.780 --> 00:24:44.330 align:start position:0% ID into the gossips app and so when you connect<00:24:43.020> to<00:24:43.200> appear<00:24:43.500> you<00:24:43.679> can<00:24:43.740> identify<00:24:44.100> which 00:24:44.330 --> 00:24:44.340 align:start position:0% connect to appear you can identify which 00:24:44.340 --> 00:24:45.830 align:start position:0% connect to appear you can identify which protocols<00:24:44.820> they<00:24:44.940> support<00:24:45.120> if<00:24:45.600> they<00:24:45.720> don't 00:24:45.830 --> 00:24:45.840 align:start position:0% protocols they support if they don't 00:24:45.840 --> 00:24:47.210 align:start position:0% protocols they support if they don't support<00:24:46.020> episode<00:24:46.200> you<00:24:46.679> don't<00:24:46.799> choke<00:24:47.039> or 00:24:47.210 --> 00:24:47.220 align:start position:0% support episode you don't choke or 00:24:47.220 --> 00:24:48.830 align:start position:0% support episode you don't choke or uncheck<00:24:47.640> them<00:24:47.760> if<00:24:47.940> they<00:24:48.059> do<00:24:48.179> support<00:24:48.360> it<00:24:48.600> you 00:24:48.830 --> 00:24:48.840 align:start position:0% uncheck them if they do support it you 00:24:48.840 --> 00:24:50.990 align:start position:0% uncheck them if they do support it you can<00:24:49.080> choke<00:24:49.440> and<00:24:49.620> uncheck<00:24:50.039> so<00:24:50.520> it<00:24:50.700> works 00:24:50.990 --> 00:24:51.000 align:start position:0% can choke and uncheck so it works 00:24:51.000 --> 00:24:53.810 align:start position:0% can choke and uncheck so it works perfectly<00:24:51.240> with<00:24:51.539> 1.1<00:24:52.200> notes<00:24:52.919> yeah<00:24:53.460> I<00:24:53.700> was 00:24:53.810 --> 00:24:53.820 align:start position:0% perfectly with 1.1 notes yeah I was 00:24:53.820 --> 00:24:55.730 align:start position:0% perfectly with 1.1 notes yeah I was trying<00:24:54.000> to<00:24:54.240> ask<00:24:54.419> why<00:24:54.900> do<00:24:55.080> we<00:24:55.200> want<00:24:55.380> to<00:24:55.559> reduce 00:24:55.730 --> 00:24:55.740 align:start position:0% trying to ask why do we want to reduce 00:24:55.740 --> 00:24:58.070 align:start position:0% trying to ask why do we want to reduce bandwidth<00:24:56.400> for<00:24:56.520> institutional<00:24:57.120> stakers<00:24:57.600> like 00:24:58.070 --> 00:24:58.080 align:start position:0% bandwidth for institutional stakers like 00:24:58.080 --> 00:25:00.770 align:start position:0% bandwidth for institutional stakers like isn't<00:24:58.559> it<00:24:58.740> kind<00:24:58.919> of<00:24:59.039> a<00:24:59.340> nice<00:24:59.820> property<00:25:00.360> that 00:25:00.770 --> 00:25:00.780 align:start position:0% isn't it kind of a nice property that 00:25:00.780 --> 00:25:02.750 align:start position:0% isn't it kind of a nice property that there<00:25:01.380> is<00:25:01.559> no<00:25:01.740> economies<00:25:02.159> of<00:25:02.280> scale<00:25:02.460> at<00:25:02.640> least 00:25:02.750 --> 00:25:02.760 align:start position:0% there is no economies of scale at least 00:25:02.760 --> 00:25:04.010 align:start position:0% there is no economies of scale at least if<00:25:03.000> the 00:25:04.010 --> 00:25:04.020 align:start position:0% if the 00:25:04.020 --> 00:25:06.169 align:start position:0% if the um if<00:25:04.140> it's<00:25:04.380> enforceable<00:25:04.919> that<00:25:05.340> they<00:25:05.640> have<00:25:05.940> to 00:25:06.169 --> 00:25:06.179 align:start position:0% um if it's enforceable that they have to 00:25:06.179 --> 00:25:07.789 align:start position:0% um if it's enforceable that they have to subscribe<00:25:06.600> to<00:25:06.720> things 00:25:07.789 --> 00:25:07.799 align:start position:0% subscribe to things 00:25:07.799 --> 00:25:09.890 align:start position:0% subscribe to things um it<00:25:08.340> just<00:25:08.520> seems<00:25:08.760> like<00:25:08.880> I<00:25:09.539> don't<00:25:09.600> know<00:25:09.659> it's 00:25:09.890 --> 00:25:09.900 align:start position:0% um it just seems like I don't know it's 00:25:09.900 --> 00:25:12.590 align:start position:0% um it just seems like I don't know it's weird<00:25:10.140> to<00:25:10.320> me<00:25:10.440> as<00:25:10.620> a<00:25:10.799> concept<00:25:11.039> to<00:25:11.220> shift<00:25:11.580> uh<00:25:12.360> the 00:25:12.590 --> 00:25:12.600 align:start position:0% weird to me as a concept to shift uh the 00:25:12.600 --> 00:25:14.690 align:start position:0% weird to me as a concept to shift uh the load<00:25:12.840> from<00:25:13.020> institutional<00:25:13.559> stakers<00:25:14.039> to<00:25:14.460> like 00:25:14.690 --> 00:25:14.700 align:start position:0% load from institutional stakers to like 00:25:14.700 --> 00:25:16.970 align:start position:0% load from institutional stakers to like normal<00:25:14.880> Beacon<00:25:15.299> nodes<00:25:15.600> or<00:25:15.840> like 00:25:16.970 --> 00:25:16.980 align:start position:0% normal Beacon nodes or like 00:25:16.980 --> 00:25:18.770 align:start position:0% normal Beacon nodes or like um<00:25:17.039> I<00:25:17.640> don't<00:25:17.820> know<00:25:17.820> homesteakers<00:25:18.360> even<00:25:18.600> if 00:25:18.770 --> 00:25:18.780 align:start position:0% um I don't know homesteakers even if 00:25:18.780 --> 00:25:20.149 align:start position:0% um I don't know homesteakers even if it's<00:25:18.840> like<00:25:19.020> a<00:25:19.140> little<00:25:19.200> bit<00:25:19.380> but<00:25:19.559> just<00:25:19.799> it 00:25:20.149 --> 00:25:20.159 align:start position:0% it's like a little bit but just it 00:25:20.159 --> 00:25:22.909 align:start position:0% it's like a little bit but just it generally<00:25:20.400> seems<00:25:20.700> like<00:25:20.820> we<00:25:21.600> want<00:25:21.840> those<00:25:22.440> the 00:25:22.909 --> 00:25:22.919 align:start position:0% generally seems like we want those the 00:25:22.919 --> 00:25:25.130 align:start position:0% generally seems like we want those the lack<00:25:23.159> of<00:25:23.340> economies<00:25:23.760> of<00:25:23.880> scale<00:25:24.120> good<00:25:24.659> part<00:25:24.900> of 00:25:25.130 --> 00:25:25.140 align:start position:0% lack of economies of scale good part of 00:25:25.140 --> 00:25:27.769 align:start position:0% lack of economies of scale good part of this<00:25:25.380> is<00:25:26.100> the<00:25:26.460> part<00:25:26.700> that<00:25:27.120> edge<00:25:27.299> mentioned 00:25:27.769 --> 00:25:27.779 align:start position:0% this is the part that edge mentioned 00:25:27.779 --> 00:25:31.730 align:start position:0% this is the part that edge mentioned about<00:25:27.960> being<00:25:28.440> enforceable<00:25:29.640> so<00:25:30.539> having<00:25:31.380> 60 00:25:31.730 --> 00:25:31.740 align:start position:0% about being enforceable so having 60 00:25:31.740 --> 00:25:34.610 align:start position:0% about being enforceable so having 60 almost<00:25:32.640> 60<00:25:32.940> percent<00:25:33.240> of<00:25:33.659> the<00:25:33.900> network<00:25:34.080> being 00:25:34.610 --> 00:25:34.620 align:start position:0% almost 60 percent of the network being 00:25:34.620 --> 00:25:37.669 align:start position:0% almost 60 percent of the network being knows<00:25:35.360> that<00:25:36.360> don't<00:25:36.659> have<00:25:36.900> any<00:25:37.080> validators 00:25:37.669 --> 00:25:37.679 align:start position:0% knows that don't have any validators 00:25:37.679 --> 00:25:40.490 align:start position:0% knows that don't have any validators we're<00:25:38.279> not<00:25:38.580> so<00:25:38.880> sure<00:25:39.120> that's<00:25:39.419> true<00:25:39.720> those 00:25:40.490 --> 00:25:40.500 align:start position:0% we're not so sure that's true those 00:25:40.500 --> 00:25:44.090 align:start position:0% we're not so sure that's true those might<00:25:40.860> as<00:25:40.980> well<00:25:41.159> be<00:25:41.520> institutional<00:25:42.480> stickers 00:25:44.090 --> 00:25:44.100 align:start position:0% might as well be institutional stickers 00:25:44.100 --> 00:25:46.669 align:start position:0% might as well be institutional stickers so<00:25:44.700> the<00:25:44.940> truth<00:25:45.179> is<00:25:45.360> that<00:25:45.720> this<00:25:46.140> is<00:25:46.260> more<00:25:46.440> like 00:25:46.669 --> 00:25:46.679 align:start position:0% so the truth is that this is more like 00:25:46.679 --> 00:25:47.870 align:start position:0% so the truth is that this is more like about 00:25:47.870 --> 00:25:47.880 align:start position:0% about 00:25:47.880 --> 00:25:50.990 align:start position:0% about being<00:25:48.419> fair<00:25:48.720> across<00:25:49.620> the<00:25:49.740> network 00:25:50.990 --> 00:25:51.000 align:start position:0% being fair across the network 00:25:51.000 --> 00:25:55.010 align:start position:0% being fair across the network so<00:25:51.659> it's<00:25:52.380> more<00:25:52.620> about<00:25:52.799> that<00:25:53.159> than<00:25:54.020> targeting 00:25:55.010 --> 00:25:55.020 align:start position:0% so it's more about that than targeting 00:25:55.020 --> 00:25:58.130 align:start position:0% so it's more about that than targeting something<00:25:55.700> uh<00:25:56.700> that<00:25:57.299> is<00:25:57.419> going<00:25:57.600> to<00:25:57.720> be<00:25:57.900> better 00:25:58.130 --> 00:25:58.140 align:start position:0% something uh that is going to be better 00:25:58.140 --> 00:26:00.590 align:start position:0% something uh that is going to be better for<00:25:58.559> institutional<00:25:59.100> stakers<00:25:59.640> it's<00:26:00.179> just<00:26:00.419> that 00:26:00.590 --> 00:26:00.600 align:start position:0% for institutional stakers it's just that 00:26:00.600 --> 00:26:03.710 align:start position:0% for institutional stakers it's just that they<00:26:00.840> happen<00:26:01.020> to<00:26:01.320> get<00:26:01.820> more<00:26:02.820> gains<00:26:03.240> because<00:26:03.419> of 00:26:03.710 --> 00:26:03.720 align:start position:0% they happen to get more gains because of 00:26:03.720 --> 00:26:06.649 align:start position:0% they happen to get more gains because of this<00:26:03.900> so<00:26:04.679> I<00:26:04.980> know<00:26:05.159> with<00:26:05.940> four<00:26:06.120> eight<00:26:06.299> four<00:26:06.539> four 00:26:06.649 --> 00:26:06.659 align:start position:0% this so I know with four eight four four 00:26:06.659 --> 00:26:07.970 align:start position:0% this so I know with four eight four four we're<00:26:07.020> going<00:26:07.140> to<00:26:07.260> be<00:26:07.320> exploding<00:26:07.860> our 00:26:07.970 --> 00:26:07.980 align:start position:0% we're going to be exploding our 00:26:07.980 --> 00:26:09.649 align:start position:0% we're going to be exploding our bandwidth<00:26:08.580> costs<00:26:08.880> I<00:26:09.000> was<00:26:09.120> curious<00:26:09.360> if<00:26:09.539> you 00:26:09.649 --> 00:26:09.659 align:start position:0% bandwidth costs I was curious if you 00:26:09.659 --> 00:26:11.990 align:start position:0% bandwidth costs I was curious if you guys<00:26:09.779> knew<00:26:10.260> if<00:26:10.919> that<00:26:11.159> scales<00:26:11.580> with<00:26:11.700> the<00:26:11.880> number 00:26:11.990 --> 00:26:12.000 align:start position:0% guys knew if that scales with the number 00:26:12.000 --> 00:26:14.570 align:start position:0% guys knew if that scales with the number of<00:26:12.179> stakers<00:26:12.720> you<00:26:12.960> have<00:26:13.140> or<00:26:13.919> number<00:26:14.340> of 00:26:14.570 --> 00:26:14.580 align:start position:0% of stakers you have or number of 00:26:14.580 --> 00:26:17.029 align:start position:0% of stakers you have or number of validators<00:26:15.120> you<00:26:15.299> have<00:26:15.559> so<00:26:16.559> I<00:26:16.679> just<00:26:16.799> the 00:26:17.029 --> 00:26:17.039 align:start position:0% validators you have so I just the 00:26:17.039 --> 00:26:18.110 align:start position:0% validators you have so I just the question<00:26:17.220> is<00:26:17.400> that<00:26:17.580> we're<00:26:17.760> going<00:26:17.880> to<00:26:18.000> increase 00:26:18.110 --> 00:26:18.120 align:start position:0% question is that we're going to increase 00:26:18.120 --> 00:26:21.169 align:start position:0% question is that we're going to increase the<00:26:18.419> the<00:26:18.600> block<00:26:18.779> size<00:26:19.080> in<00:26:19.320> 4i44<00:26:20.220> and<00:26:20.700> how<00:26:21.059> that 00:26:21.169 --> 00:26:21.179 align:start position:0% the the block size in 4i44 and how that 00:26:21.179 --> 00:26:24.110 align:start position:0% the the block size in 4i44 and how that applies<00:26:21.480> with<00:26:21.659> here<00:26:21.960> if<00:26:22.799> that<00:26:23.100> scales<00:26:23.580> the<00:26:24.000> way 00:26:24.110 --> 00:26:24.120 align:start position:0% applies with here if that scales the way 00:26:24.120 --> 00:26:27.890 align:start position:0% applies with here if that scales the way that<00:26:24.779> under<00:26:25.500> current<00:26:25.799> gossip<00:26:26.279> our<00:26:26.760> bandwidth 00:26:27.890 --> 00:26:27.900 align:start position:0% that under current gossip our bandwidth 00:26:27.900 --> 00:26:29.390 align:start position:0% that under current gossip our bandwidth um<00:26:27.960> increases<00:26:28.860> with<00:26:29.039> the<00:26:29.159> number<00:26:29.279> of 00:26:29.390 --> 00:26:29.400 align:start position:0% um increases with the number of 00:26:29.400 --> 00:26:30.950 align:start position:0% um increases with the number of validators<00:26:29.880> you<00:26:30.059> have<00:26:30.179> I<00:26:30.480> was<00:26:30.600> curious<00:26:30.840> if 00:26:30.950 --> 00:26:30.960 align:start position:0% validators you have I was curious if 00:26:30.960 --> 00:26:32.330 align:start position:0% validators you have I was curious if that<00:26:31.140> was<00:26:31.260> the<00:26:31.440> case<00:26:31.559> for<00:26:31.740> the<00:26:31.860> increase<00:26:32.039> in 00:26:32.330 --> 00:26:32.340 align:start position:0% that was the case for the increase in 00:26:32.340 --> 00:26:35.390 align:start position:0% that was the case for the increase in 4844<00:26:32.940> as<00:26:33.240> well<00:26:33.419> yeah<00:26:33.960> yeah<00:26:34.260> it's<00:26:34.679> not<00:26:34.860> so<00:26:35.159> the 00:26:35.390 --> 00:26:35.400 align:start position:0% 4844 as well yeah yeah it's not so the 00:26:35.400 --> 00:26:37.250 align:start position:0% 4844 as well yeah yeah it's not so the the<00:26:35.580> bandwidth<00:26:36.179> increase<00:26:36.360> is<00:26:36.659> due<00:26:36.900> to<00:26:37.080> the 00:26:37.250 --> 00:26:37.260 align:start position:0% the bandwidth increase is due to the 00:26:37.260 --> 00:26:38.990 align:start position:0% the bandwidth increase is due to the subnet<00:26:37.860> subscription 00:26:38.990 --> 00:26:39.000 align:start position:0% subnet subscription 00:26:39.000 --> 00:26:40.190 align:start position:0% subnet subscription um<00:26:39.059> when<00:26:39.240> you<00:26:39.419> increase<00:26:39.539> the<00:26:39.779> block<00:26:39.960> size 00:26:40.190 --> 00:26:40.200 align:start position:0% um when you increase the block size 00:26:40.200 --> 00:26:41.870 align:start position:0% um when you increase the block size everybody<00:26:40.559> feels<00:26:41.220> that<00:26:41.340> because<00:26:41.640> everyone 00:26:41.870 --> 00:26:41.880 align:start position:0% everybody feels that because everyone 00:26:41.880 --> 00:26:43.909 align:start position:0% everybody feels that because everyone subscribed<00:26:42.419> to<00:26:42.539> the<00:26:42.600> Vlog<00:26:42.900> topic 00:26:43.909 --> 00:26:43.919 align:start position:0% subscribed to the Vlog topic 00:26:43.919 --> 00:26:45.710 align:start position:0% subscribed to the Vlog topic yeah<00:26:44.159> so<00:26:44.400> that's<00:26:44.580> that's<00:26:44.820> felt<00:26:45.240> uniformly 00:26:45.710 --> 00:26:45.720 align:start position:0% yeah so that's that's felt uniformly 00:26:45.720 --> 00:26:48.230 align:start position:0% yeah so that's that's felt uniformly here<00:26:46.440> the<00:26:46.620> part<00:26:46.799> that<00:26:47.039> matters<00:26:47.400> for<00:26:47.700> what<00:26:47.940> Mark 00:26:48.230 --> 00:26:48.240 align:start position:0% here the part that matters for what Mark 00:26:48.240 --> 00:26:51.890 align:start position:0% here the part that matters for what Mark asked<00:26:49.260> is<00:26:50.220> mainly<00:26:50.640> the<00:26:50.820> amplification<00:26:51.360> factor 00:26:51.890 --> 00:26:51.900 align:start position:0% asked is mainly the amplification factor 00:26:51.900 --> 00:26:53.810 align:start position:0% asked is mainly the amplification factor and<00:26:52.140> not<00:26:52.320> that<00:26:52.559> much 00:26:53.810 --> 00:26:53.820 align:start position:0% and not that much 00:26:53.820 --> 00:26:56.330 align:start position:0% and not that much um<00:26:53.880> how<00:26:54.779> it<00:26:54.960> behaves<00:26:55.500> regarding<00:26:55.980> the<00:26:56.220> number 00:26:56.330 --> 00:26:56.340 align:start position:0% um how it behaves regarding the number 00:26:56.340 --> 00:26:58.909 align:start position:0% um how it behaves regarding the number of<00:26:56.520> validators<00:26:57.240> so<00:26:57.900> since<00:26:58.080> we<00:26:58.320> have<00:26:58.500> an 00:26:58.909 --> 00:26:58.919 align:start position:0% of validators so since we have an 00:26:58.919 --> 00:27:01.789 align:start position:0% of validators so since we have an amplification<00:26:59.400> factor<00:26:59.880> of<00:27:00.000> about<00:27:00.179> six<00:27:00.600> so<00:27:01.500> now 00:27:01.789 --> 00:27:01.799 align:start position:0% amplification factor of about six so now 00:27:01.799 --> 00:27:05.750 align:start position:0% amplification factor of about six so now with<00:27:02.220> this<00:27:03.080> uh<00:27:04.080> this<00:27:04.500> Improvement 00:27:05.750 --> 00:27:05.760 align:start position:0% with this uh this Improvement 00:27:05.760 --> 00:27:07.310 align:start position:0% with this uh this Improvement we're<00:27:06.240> going<00:27:06.480> to<00:27:06.600> have 00:27:07.310 --> 00:27:07.320 align:start position:0% we're going to have 00:27:07.320 --> 00:27:10.490 align:start position:0% we're going to have huge<00:27:07.860> block<00:27:08.039> sizes<00:27:08.600> which<00:27:09.600> if<00:27:10.140> we<00:27:10.320> continue 00:27:10.490 --> 00:27:10.500 align:start position:0% huge block sizes which if we continue 00:27:10.500 --> 00:27:12.350 align:start position:0% huge block sizes which if we continue doing<00:27:10.860> things<00:27:11.100> the<00:27:11.340> way<00:27:11.520> we<00:27:11.760> are<00:27:11.880> are<00:27:12.059> going<00:27:12.240> to 00:27:12.350 --> 00:27:12.360 align:start position:0% doing things the way we are are going to 00:27:12.360 --> 00:27:14.029 align:start position:0% doing things the way we are are going to be<00:27:12.539> sent<00:27:12.779> across<00:27:13.260> the<00:27:13.320> network<00:27:13.440> six<00:27:13.799> times 00:27:14.029 --> 00:27:14.039 align:start position:0% be sent across the network six times 00:27:14.039 --> 00:27:17.210 align:start position:0% be sent across the network six times each<00:27:14.460> time<00:27:14.700> each<00:27:15.419> block<00:27:15.659> so<00:27:16.500> that's<00:27:16.860> that's 00:27:17.210 --> 00:27:17.220 align:start position:0% each time each block so that's that's 00:27:17.220 --> 00:27:20.210 align:start position:0% each time each block so that's that's insane<00:27:17.760> but<00:27:18.299> there<00:27:18.480> is<00:27:18.840> yeah<00:27:19.380> so<00:27:19.620> it's<00:27:19.799> related 00:27:20.210 --> 00:27:20.220 align:start position:0% insane but there is yeah so it's related 00:27:20.220 --> 00:27:22.789 align:start position:0% insane but there is yeah so it's related more<00:27:20.460> about<00:27:20.640> duplicates<00:27:21.240> that<00:27:21.600> part 00:27:22.789 --> 00:27:22.799 align:start position:0% more about duplicates that part 00:27:22.799 --> 00:27:24.710 align:start position:0% more about duplicates that part than<00:27:23.279> the<00:27:23.520> number<00:27:23.640> of<00:27:23.760> validators<00:27:24.240> for<00:27:24.539> each 00:27:24.710 --> 00:27:24.720 align:start position:0% than the number of validators for each 00:27:24.720 --> 00:27:27.409 align:start position:0% than the number of validators for each node<00:27:25.440> so<00:27:25.919> you<00:27:26.279> showed<00:27:26.580> that<00:27:26.640> by<00:27:27.000> modal 00:27:27.409 --> 00:27:27.419 align:start position:0% node so you showed that by modal 00:27:27.419 --> 00:27:30.529 align:start position:0% node so you showed that by modal distribution<00:27:27.840> where<00:27:28.380> there's<00:27:29.279> a<00:27:29.640> lot<00:27:29.760> of<00:27:29.940> one 00:27:30.529 --> 00:27:30.539 align:start position:0% distribution where there's a lot of one 00:27:30.539 --> 00:27:32.570 align:start position:0% distribution where there's a lot of one validator<00:27:30.960> nodes<00:27:31.440> and<00:27:32.100> then<00:27:32.159> there's<00:27:32.340> that 00:27:32.570 --> 00:27:32.580 align:start position:0% validator nodes and then there's that 00:27:32.580 --> 00:27:34.430 align:start position:0% validator nodes and then there's that sixty<00:27:32.940> percent<00:27:33.059> that<00:27:33.480> were<00:27:33.720> just<00:27:33.960> regular 00:27:34.430 --> 00:27:34.440 align:start position:0% sixty percent that were just regular 00:27:34.440 --> 00:27:36.470 align:start position:0% sixty percent that were just regular full<00:27:34.620> nodes<00:27:34.919> like<00:27:35.039> not<00:27:35.159> validators<00:27:35.640> and<00:27:35.820> then 00:27:36.470 --> 00:27:36.480 align:start position:0% full nodes like not validators and then 00:27:36.480 --> 00:27:39.289 align:start position:0% full nodes like not validators and then you<00:27:37.080> know<00:27:37.200> uh<00:27:37.799> the<00:27:38.400> institutional<00:27:38.880> notes<00:27:39.179> with 00:27:39.289 --> 00:27:39.299 align:start position:0% you know uh the institutional notes with 00:27:39.299 --> 00:27:43.070 align:start position:0% you know uh the institutional notes with like<00:27:39.480> more<00:27:39.600> than<00:27:39.779> 64.<00:27:40.799> so<00:27:41.340> that<00:27:41.820> uh 00:27:43.070 --> 00:27:43.080 align:start position:0% like more than 64. so that uh 00:27:43.080 --> 00:27:46.370 align:start position:0% like more than 64. so that uh I<00:27:43.500> understand<00:27:43.620> how<00:27:44.279> the<00:27:44.760> Epi<00:27:45.600> sub<00:27:45.720> like<00:27:46.020> helps 00:27:46.370 --> 00:27:46.380 align:start position:0% I understand how the Epi sub like helps 00:27:46.380 --> 00:27:47.810 align:start position:0% I understand how the Epi sub like helps everyone<00:27:46.559> and<00:27:47.220> it<00:27:47.340> like<00:27:47.460> helps<00:27:47.700> the 00:27:47.810 --> 00:27:47.820 align:start position:0% everyone and it like helps the 00:27:47.820 --> 00:27:49.850 align:start position:0% everyone and it like helps the homesteaker<00:27:48.299> it<00:27:48.360> helps<00:27:48.600> the<00:27:48.659> Netflix<00:27:48.779> problem 00:27:49.850 --> 00:27:49.860 align:start position:0% homesteaker it helps the Netflix problem 00:27:49.860 --> 00:27:53.930 align:start position:0% homesteaker it helps the Netflix problem for<00:27:50.220> the<00:27:50.400> institutional<00:27:51.120> stakers<00:27:52.080> their 00:27:53.930 --> 00:27:53.940 align:start position:0% for the institutional stakers their 00:27:53.940 --> 00:27:55.730 align:start position:0% for the institutional stakers their all<00:27:54.240> running<00:27:54.539> like<00:27:54.779> data<00:27:55.200> center<00:27:55.260> nodes 00:27:55.730 --> 00:27:55.740 align:start position:0% all running like data center nodes 00:27:55.740 --> 00:27:58.789 align:start position:0% all running like data center nodes anyway<00:27:56.340> so<00:27:57.000> I<00:27:57.419> I<00:27:57.779> don't<00:27:57.960> understand<00:27:58.080> as<00:27:58.620> much 00:27:58.789 --> 00:27:58.799 align:start position:0% anyway so I I don't understand as much 00:27:58.799 --> 00:28:02.450 align:start position:0% anyway so I I don't understand as much how<00:27:59.460> the<00:27:59.640> like<00:28:00.000> subscribing<00:28:00.659> to<00:28:00.960> fewer<00:28:01.500> gossip 00:28:02.450 --> 00:28:02.460 align:start position:0% how the like subscribing to fewer gossip 00:28:02.460 --> 00:28:05.330 align:start position:0% how the like subscribing to fewer gossip sub<00:28:02.640> topics<00:28:03.120> uh<00:28:03.659> helps<00:28:04.020> so<00:28:04.740> I<00:28:04.980> think<00:28:05.100> I<00:28:05.220> think 00:28:05.330 --> 00:28:05.340 align:start position:0% sub topics uh helps so I think I think 00:28:05.340 --> 00:28:07.490 align:start position:0% sub topics uh helps so I think I think this<00:28:05.400> is<00:28:05.520> a<00:28:05.580> very<00:28:05.760> similar<00:28:06.059> question<00:28:06.299> uh<00:28:07.080> over 00:28:07.490 --> 00:28:07.500 align:start position:0% this is a very similar question uh over 00:28:07.500 --> 00:28:09.890 align:start position:0% this is a very similar question uh over here<00:28:07.679> so<00:28:08.340> I<00:28:08.940> think<00:28:09.059> fundamentally<00:28:09.600> we<00:28:09.779> were 00:28:09.890 --> 00:28:09.900 align:start position:0% here so I think fundamentally we were 00:28:09.900 --> 00:28:11.230 align:start position:0% here so I think fundamentally we were looking<00:28:10.020> at 00:28:11.230 --> 00:28:11.240 align:start position:0% looking at 00:28:11.240 --> 00:28:15.049 align:start position:0% looking at as<00:28:12.240> as<00:28:12.900> a<00:28:13.140> whole<00:28:13.320> the<00:28:14.039> the<00:28:14.220> network<00:28:14.460> may<00:28:14.940> be 00:28:15.049 --> 00:28:15.059 align:start position:0% as as a whole the the network may be 00:28:15.059 --> 00:28:16.730 align:start position:0% as as a whole the the network may be consuming<00:28:15.480> more<00:28:15.659> bandwidth<00:28:16.140> than<00:28:16.320> we<00:28:16.500> need<00:28:16.620> to 00:28:16.730 --> 00:28:16.740 align:start position:0% consuming more bandwidth than we need to 00:28:16.740 --> 00:28:18.890 align:start position:0% consuming more bandwidth than we need to be<00:28:16.860> you<00:28:17.520> depending<00:28:18.000> on<00:28:18.120> how<00:28:18.360> how<00:28:18.360> you<00:28:18.720> build 00:28:18.890 --> 00:28:18.900 align:start position:0% be you depending on how how you build 00:28:18.900 --> 00:28:20.630 align:start position:0% be you depending on how how you build your<00:28:19.080> client<00:28:19.320> You<00:28:19.679> Can<00:28:19.740> Be<00:28:19.980> Clever<00:28:20.400> about 00:28:20.630 --> 00:28:20.640 align:start position:0% your client You Can Be Clever about 00:28:20.640 --> 00:28:22.970 align:start position:0% your client You Can Be Clever about which<00:28:21.000> peers<00:28:21.360> that<00:28:21.600> you<00:28:21.720> connect<00:28:21.840> to 00:28:22.970 --> 00:28:22.980 align:start position:0% which peers that you connect to 00:28:22.980 --> 00:28:24.649 align:start position:0% which peers that you connect to um when<00:28:23.520> you<00:28:23.640> have 00:28:24.649 --> 00:28:24.659 align:start position:0% um when you have 00:28:24.659 --> 00:28:26.570 align:start position:0% um when you have so<00:28:25.320> at<00:28:25.740> the<00:28:26.039> moment<00:28:26.100> you<00:28:26.279> have<00:28:26.400> these 00:28:26.570 --> 00:28:26.580 align:start position:0% so at the moment you have these 00:28:26.580 --> 00:28:27.890 align:start position:0% so at the moment you have these institutional<00:28:27.120> notes<00:28:27.480> all<00:28:27.600> right<00:28:27.659> they've 00:28:27.890 --> 00:28:27.900 align:start position:0% institutional notes all right they've 00:28:27.900 --> 00:28:29.450 align:start position:0% institutional notes all right they've got<00:28:27.960> that<00:28:28.260> they're<00:28:28.559> not<00:28:28.679> just<00:28:28.799> institutional 00:28:29.450 --> 00:28:29.460 align:start position:0% got that they're not just institutional 00:28:29.460 --> 00:28:31.730 align:start position:0% got that they're not just institutional uh<00:28:30.000> some<00:28:30.179> people<00:28:30.419> there's<00:28:31.080> a<00:28:31.260> usually 00:28:31.730 --> 00:28:31.740 align:start position:0% uh some people there's a usually 00:28:31.740 --> 00:28:32.990 align:start position:0% uh some people there's a usually parameter<00:28:32.100> I<00:28:32.220> think<00:28:32.279> in<00:28:32.400> most<00:28:32.580> clients<00:28:32.820> which 00:28:32.990 --> 00:28:33.000 align:start position:0% parameter I think in most clients which 00:28:33.000 --> 00:28:35.330 align:start position:0% parameter I think in most clients which is<00:28:33.179> called<00:28:33.299> subscribe<00:28:34.020> or<00:28:34.140> subnets<00:28:34.559> so<00:28:35.220> you 00:28:35.330 --> 00:28:35.340 align:start position:0% is called subscribe or subnets so you 00:28:35.340 --> 00:28:36.470 align:start position:0% is called subscribe or subnets so you can<00:28:35.460> even<00:28:35.640> if<00:28:35.820> you<00:28:35.940> have<00:28:36.000> one<00:28:36.179> validity 00:28:36.470 --> 00:28:36.480 align:start position:0% can even if you have one validity 00:28:36.480 --> 00:28:37.789 align:start position:0% can even if you have one validity subscribe<00:28:36.960> to<00:28:37.020> all<00:28:37.140> the<00:28:37.260> subnets<00:28:37.559> and<00:28:37.740> the 00:28:37.789 --> 00:28:37.799 align:start position:0% subscribe to all the subnets and the 00:28:37.799 --> 00:28:39.110 align:start position:0% subscribe to all the subnets and the reason<00:28:37.919> you<00:28:38.100> do<00:28:38.220> that<00:28:38.340> is<00:28:38.520> because<00:28:38.640> you<00:28:38.940> get 00:28:39.110 --> 00:28:39.120 align:start position:0% reason you do that is because you get 00:28:39.120 --> 00:28:41.570 align:start position:0% reason you do that is because you get some<00:28:39.480> benefit<00:28:39.840> from<00:28:40.440> seeing<00:28:41.340> all<00:28:41.460> the 00:28:41.570 --> 00:28:41.580 align:start position:0% some benefit from seeing all the 00:28:41.580 --> 00:28:43.190 align:start position:0% some benefit from seeing all the attestations<00:28:42.000> you<00:28:42.299> get<00:28:42.600> a<00:28:42.720> slight<00:28:43.020> increase 00:28:43.190 --> 00:28:43.200 align:start position:0% attestations you get a slight increase 00:28:43.200 --> 00:28:44.930 align:start position:0% attestations you get a slight increase in<00:28:43.440> performance<00:28:43.799> so<00:28:44.220> it's<00:28:44.340> not<00:28:44.520> necessarily 00:28:44.930 --> 00:28:44.940 align:start position:0% in performance so it's not necessarily 00:28:44.940 --> 00:28:46.789 align:start position:0% in performance so it's not necessarily just<00:28:45.120> institutional<00:28:45.779> people 00:28:46.789 --> 00:28:46.799 align:start position:0% just institutional people 00:28:46.799 --> 00:28:52.190 align:start position:0% just institutional people um<00:28:46.860> but<00:28:47.840> the<00:28:49.320> the<00:28:50.059> institutional<00:28:51.059> I<00:28:51.900> forgot 00:28:52.190 --> 00:28:52.200 align:start position:0% um but the the institutional I forgot 00:28:52.200 --> 00:28:53.690 align:start position:0% um but the the institutional I forgot what<00:28:52.320> for<00:28:52.440> my<00:28:52.559> train<00:28:52.679> of<00:28:52.860> thought 00:28:53.690 --> 00:28:53.700 align:start position:0% what for my train of thought 00:28:53.700 --> 00:28:54.590 align:start position:0% what for my train of thought um 00:28:54.590 --> 00:28:54.600 align:start position:0% um 00:28:54.600 --> 00:28:58.250 align:start position:0% um the<00:28:55.559> no<00:28:56.159> I<00:28:56.340> forgot<00:28:56.580> what<00:28:56.640> I<00:28:56.760> was<00:28:56.880> saying 00:28:58.250 --> 00:28:58.260 align:start position:0% the no I forgot what I was saying 00:28:58.260 --> 00:29:00.529 align:start position:0% the no I forgot what I was saying and<00:28:58.740> I<00:28:59.039> just<00:28:59.159> have<00:28:59.279> a<00:28:59.400> point<00:28:59.460> it's<00:29:00.120> part<00:29:00.360> of 00:29:00.529 --> 00:29:00.539 align:start position:0% and I just have a point it's part of 00:29:00.539 --> 00:29:03.289 align:start position:0% and I just have a point it's part of what<00:29:00.779> age<00:29:01.020> was<00:29:01.320> saying<00:29:01.679> is<00:29:02.279> that 00:29:03.289 --> 00:29:03.299 align:start position:0% what age was saying is that 00:29:03.299 --> 00:29:05.630 align:start position:0% what age was saying is that well<00:29:03.659> subscribing<00:29:04.200> to<00:29:04.320> a<00:29:04.500> subnet 00:29:05.630 --> 00:29:05.640 align:start position:0% well subscribing to a subnet 00:29:05.640 --> 00:29:08.870 align:start position:0% well subscribing to a subnet we<00:29:06.539> also<00:29:06.900> advertise<00:29:07.500> that<00:29:07.799> we<00:29:08.100> are<00:29:08.340> inside<00:29:08.580> the 00:29:08.870 --> 00:29:08.880 align:start position:0% we also advertise that we are inside the 00:29:08.880 --> 00:29:11.750 align:start position:0% we also advertise that we are inside the subnet<00:29:09.299> inside<00:29:09.900> Discovery<00:29:10.740> so<00:29:11.340> that<00:29:11.460> means 00:29:11.750 --> 00:29:11.760 align:start position:0% subnet inside Discovery so that means 00:29:11.760 --> 00:29:14.210 align:start position:0% subnet inside Discovery so that means that<00:29:12.000> we<00:29:12.480> need<00:29:12.900> to<00:29:13.080> find<00:29:13.260> peers<00:29:13.740> using 00:29:14.210 --> 00:29:14.220 align:start position:0% that we need to find peers using 00:29:14.220 --> 00:29:17.090 align:start position:0% that we need to find peers using discovery<00:29:14.760> that<00:29:15.059> are<00:29:15.240> useful<00:29:15.539> for<00:29:15.840> us<00:29:16.080> so<00:29:16.799> one 00:29:17.090 --> 00:29:17.100 align:start position:0% discovery that are useful for us so one 00:29:17.100 --> 00:29:19.730 align:start position:0% discovery that are useful for us so one strategy<00:29:17.580> that<00:29:17.820> people<00:29:18.059> who<00:29:18.659> have<00:29:19.559> the 00:29:19.730 --> 00:29:19.740 align:start position:0% strategy that people who have the 00:29:19.740 --> 00:29:22.549 align:start position:0% strategy that people who have the bandwidth<00:29:20.220> for<00:29:20.340> that<00:29:20.580> used<00:29:21.539> to<00:29:21.840> be<00:29:22.020> sure<00:29:22.200> that 00:29:22.549 --> 00:29:22.559 align:start position:0% bandwidth for that used to be sure that 00:29:22.559 --> 00:29:25.010 align:start position:0% bandwidth for that used to be sure that they<00:29:22.799> have<00:29:23.100> publishing<00:29:24.000> all<00:29:24.299> in<00:29:24.539> time<00:29:24.779> and 00:29:25.010 --> 00:29:25.020 align:start position:0% they have publishing all in time and 00:29:25.020 --> 00:29:26.990 align:start position:0% they have publishing all in time and everything<00:29:25.260> is<00:29:25.620> timely<00:29:26.159> is<00:29:26.340> subscribing<00:29:26.820> to 00:29:26.990 --> 00:29:27.000 align:start position:0% everything is timely is subscribing to 00:29:27.000 --> 00:29:28.789 align:start position:0% everything is timely is subscribing to all<00:29:27.179> subnets<00:29:27.659> regardless<00:29:28.200> of<00:29:28.500> how<00:29:28.740> many 00:29:28.789 --> 00:29:28.799 align:start position:0% all subnets regardless of how many 00:29:28.799 --> 00:29:31.310 align:start position:0% all subnets regardless of how many validators<00:29:29.399> they<00:29:29.700> have<00:29:29.940> this<00:29:30.899> is<00:29:30.960> what<00:29:31.200> age 00:29:31.310 --> 00:29:31.320 align:start position:0% validators they have this is what age 00:29:31.320 --> 00:29:33.950 align:start position:0% validators they have this is what age was<00:29:31.620> saying<00:29:31.919> about<00:29:32.100> maybe<00:29:33.000> it's<00:29:33.240> not<00:29:33.539> exactly 00:29:33.950 --> 00:29:33.960 align:start position:0% was saying about maybe it's not exactly 00:29:33.960 --> 00:29:36.110 align:start position:0% was saying about maybe it's not exactly true<00:29:34.320> that<00:29:35.220> all 00:29:36.110 --> 00:29:36.120 align:start position:0% true that all 00:29:36.120 --> 00:29:39.769 align:start position:0% true that all nodes<00:29:36.960> that<00:29:37.200> have<00:29:37.440> more<00:29:37.799> than<00:29:37.980> 64 00:29:39.769 --> 00:29:39.779 align:start position:0% nodes that have more than 64 00:29:39.779 --> 00:29:42.649 align:start position:0% nodes that have more than 64 subscribed<00:29:40.620> softness<00:29:41.100> actually<00:29:41.580> have<00:29:42.059> more 00:29:42.649 --> 00:29:42.659 align:start position:0% subscribed softness actually have more 00:29:42.659 --> 00:29:45.830 align:start position:0% subscribed softness actually have more than<00:29:42.840> 64<00:29:43.399> validators<00:29:44.399> attached<00:29:44.880> to<00:29:45.000> them 00:29:45.830 --> 00:29:45.840 align:start position:0% than 64 validators attached to them 00:29:45.840 --> 00:29:47.630 align:start position:0% than 64 validators attached to them yeah<00:29:46.320> sorry<00:29:46.440> I<00:29:46.679> remember<00:29:46.799> my<00:29:47.039> point<00:29:47.159> my<00:29:47.520> point 00:29:47.630 --> 00:29:47.640 align:start position:0% yeah sorry I remember my point my point 00:29:47.640 --> 00:29:49.610 align:start position:0% yeah sorry I remember my point my point was<00:29:47.820> that<00:29:48.120> we<00:29:48.840> have<00:29:48.960> these<00:29:49.200> institutional 00:29:49.610 --> 00:29:49.620 align:start position:0% was that we have these institutional 00:29:49.620 --> 00:29:51.169 align:start position:0% was that we have these institutional Stakes<00:29:49.919> or<00:29:50.220> people<00:29:50.520> that<00:29:50.640> are<00:29:50.820> subscribed<00:29:51.059> to 00:29:51.169 --> 00:29:51.179 align:start position:0% Stakes or people that are subscribed to 00:29:51.179 --> 00:29:52.370 align:start position:0% Stakes or people that are subscribed to all<00:29:51.299> the<00:29:51.419> subnets<00:29:51.659> and<00:29:51.840> they<00:29:52.020> become<00:29:52.260> more 00:29:52.370 --> 00:29:52.380 align:start position:0% all the subnets and they become more 00:29:52.380 --> 00:29:53.810 align:start position:0% all the subnets and they become more valuable<00:29:52.740> than<00:29:52.980> every<00:29:53.159> other<00:29:53.279> node<00:29:53.580> on<00:29:53.700> the 00:29:53.810 --> 00:29:53.820 align:start position:0% valuable than every other node on the 00:29:53.820 --> 00:29:55.850 align:start position:0% valuable than every other node on the network<00:29:53.940> if<00:29:54.480> from<00:29:54.720> a<00:29:54.840> client<00:29:55.020> perspective<00:29:55.440> if 00:29:55.850 --> 00:29:55.860 align:start position:0% network if from a client perspective if 00:29:55.860 --> 00:29:57.470 align:start position:0% network if from a client perspective if you<00:29:56.340> have<00:29:56.460> peers<00:29:56.760> that<00:29:56.940> are<00:29:57.059> connecting<00:29:57.360> to 00:29:57.470 --> 00:29:57.480 align:start position:0% you have peers that are connecting to 00:29:57.480 --> 00:29:59.389 align:start position:0% you have peers that are connecting to you<00:29:57.600> and<00:29:57.960> one<00:29:58.380> is<00:29:58.500> subscribe<00:29:58.919> to<00:29:59.039> just<00:29:59.159> one 00:29:59.389 --> 00:29:59.399 align:start position:0% you and one is subscribe to just one 00:29:59.399 --> 00:30:00.710 align:start position:0% you and one is subscribe to just one subnet<00:29:59.820> and<00:30:00.000> you<00:30:00.120> have<00:30:00.179> another<00:30:00.299> pair<00:30:00.539> that 00:30:00.710 --> 00:30:00.720 align:start position:0% subnet and you have another pair that 00:30:00.720 --> 00:30:02.630 align:start position:0% subnet and you have another pair that subscribe<00:30:01.020> to<00:30:01.140> all<00:30:01.260> 64.<00:30:01.919> you're<00:30:02.399> more 00:30:02.630 --> 00:30:02.640 align:start position:0% subscribe to all 64. you're more 00:30:02.640 --> 00:30:04.909 align:start position:0% subscribe to all 64. you're more inclined<00:30:03.000> to<00:30:03.120> be<00:30:03.240> like<00:30:03.360> I<00:30:03.539> want<00:30:03.659> to<00:30:03.840> stick<00:30:04.500> keep 00:30:04.909 --> 00:30:04.919 align:start position:0% inclined to be like I want to stick keep 00:30:04.919 --> 00:30:06.409 align:start position:0% inclined to be like I want to stick keep a<00:30:05.100> peer<00:30:05.340> connection<00:30:05.460> to<00:30:05.700> that<00:30:05.820> guy<00:30:06.000> because<00:30:06.179> in 00:30:06.409 --> 00:30:06.419 align:start position:0% a peer connection to that guy because in 00:30:06.419 --> 00:30:07.789 align:start position:0% a peer connection to that guy because in case<00:30:06.539> I<00:30:06.720> need<00:30:06.840> to<00:30:06.960> I<00:30:07.200> need<00:30:07.440> to<00:30:07.500> send<00:30:07.620> a<00:30:07.740> message 00:30:07.789 --> 00:30:07.799 align:start position:0% case I need to I need to send a message 00:30:07.799 --> 00:30:10.490 align:start position:0% case I need to I need to send a message on<00:30:07.980> one<00:30:08.159> of<00:30:08.220> the<00:30:08.279> subnets<00:30:08.580> he's<00:30:09.000> he's<00:30:09.539> uh<00:30:10.200> he<00:30:10.440> or 00:30:10.490 --> 00:30:10.500 align:start position:0% on one of the subnets he's he's uh he or 00:30:10.500 --> 00:30:12.110 align:start position:0% on one of the subnets he's he's uh he or she<00:30:10.679> is<00:30:10.740> connected<00:30:11.039> to<00:30:11.100> that<00:30:11.279> subnet<00:30:11.640> so 00:30:12.110 --> 00:30:12.120 align:start position:0% she is connected to that subnet so 00:30:12.120 --> 00:30:14.570 align:start position:0% she is connected to that subnet so you're<00:30:12.539> left<00:30:12.720> with<00:30:12.899> like<00:30:13.140> uh<00:30:13.679> 10<00:30:13.980> of<00:30:14.460> these 00:30:14.570 --> 00:30:14.580 align:start position:0% you're left with like uh 10 of these 00:30:14.580 --> 00:30:16.730 align:start position:0% you're left with like uh 10 of these nodes<00:30:14.880> are<00:30:15.419> super<00:30:15.720> valuable<00:30:16.080> nodes<00:30:16.380> across 00:30:16.730 --> 00:30:16.740 align:start position:0% nodes are super valuable nodes across 00:30:16.740 --> 00:30:17.750 align:start position:0% nodes are super valuable nodes across the network<00:30:16.919> whereas<00:30:17.220> everyone<00:30:17.399> else<00:30:17.580> you 00:30:17.750 --> 00:30:17.760 align:start position:0% the network whereas everyone else you 00:30:17.760 --> 00:30:19.250 align:start position:0% the network whereas everyone else you kind<00:30:17.940> of<00:30:18.059> just<00:30:18.179> throw<00:30:18.360> them<00:30:18.539> away<00:30:18.720> they're<00:30:19.140> not 00:30:19.250 --> 00:30:19.260 align:start position:0% kind of just throw them away they're not 00:30:19.260 --> 00:30:20.750 align:start position:0% kind of just throw them away they're not they're<00:30:19.440> not<00:30:19.559> all<00:30:19.679> that<00:30:19.799> valuable<00:30:20.100> whereas<00:30:20.640> if 00:30:20.750 --> 00:30:20.760 align:start position:0% they're not all that valuable whereas if 00:30:20.760 --> 00:30:22.490 align:start position:0% they're not all that valuable whereas if we<00:30:20.880> transition<00:30:21.179> over<00:30:21.480> to<00:30:21.659> this<00:30:21.840> thing<00:30:22.020> one 00:30:22.490 --> 00:30:22.500 align:start position:0% we transition over to this thing one 00:30:22.500 --> 00:30:23.870 align:start position:0% we transition over to this thing one it's<00:30:22.740> enforceable<00:30:23.220> which<00:30:23.460> is<00:30:23.520> something<00:30:23.700> that 00:30:23.870 --> 00:30:23.880 align:start position:0% it's enforceable which is something that 00:30:23.880 --> 00:30:26.029 align:start position:0% it's enforceable which is something that we<00:30:24.000> want<00:30:24.179> two<00:30:24.840> we're<00:30:25.140> not<00:30:25.320> entirely<00:30:25.740> sure 00:30:26.029 --> 00:30:26.039 align:start position:0% we want two we're not entirely sure 00:30:26.039 --> 00:30:27.769 align:start position:0% we want two we're not entirely sure whether<00:30:26.460> the<00:30:26.820> amount<00:30:27.000> of<00:30:27.120> banter<00:30:27.419> for<00:30:27.539> using 00:30:27.769 --> 00:30:27.779 align:start position:0% whether the amount of banter for using 00:30:27.779 --> 00:30:29.269 align:start position:0% whether the amount of banter for using across<00:30:28.020> the<00:30:28.080> entire<00:30:28.380> network<00:30:28.559> is<00:30:28.860> necessary 00:30:29.269 --> 00:30:29.279 align:start position:0% across the entire network is necessary 00:30:29.279 --> 00:30:31.430 align:start position:0% across the entire network is necessary so<00:30:29.520> we<00:30:29.640> reduce<00:30:29.880> that<00:30:30.179> as<00:30:30.360> a<00:30:30.600> I<00:30:30.899> guess<00:30:31.020> maybe<00:30:31.200> a 00:30:31.430 --> 00:30:31.440 align:start position:0% so we reduce that as a I guess maybe a 00:30:31.440 --> 00:30:35.330 align:start position:0% so we reduce that as a I guess maybe a side<00:30:31.620> effect<00:30:31.880> and<00:30:32.880> the<00:30:33.720> the<00:30:34.200> third<00:30:34.740> example<00:30:35.159> is 00:30:35.330 --> 00:30:35.340 align:start position:0% side effect and the the third example is 00:30:35.340 --> 00:30:38.330 align:start position:0% side effect and the the third example is that<00:30:35.700> all<00:30:36.419> be<00:30:36.659> all<00:30:37.140> the<00:30:37.320> nodes<00:30:37.620> are<00:30:38.039> equally 00:30:38.330 --> 00:30:38.340 align:start position:0% that all be all the nodes are equally 00:30:38.340 --> 00:30:40.250 align:start position:0% that all be all the nodes are equally kind<00:30:38.700> of<00:30:38.820> valuable<00:30:39.120> to<00:30:39.299> you<00:30:39.419> and<00:30:39.779> because<00:30:40.020> we 00:30:40.250 --> 00:30:40.260 align:start position:0% kind of valuable to you and because we 00:30:40.260 --> 00:30:43.549 align:start position:0% kind of valuable to you and because we tie<00:30:40.440> it<00:30:40.559> to<00:30:40.679> the<00:30:40.799> node<00:30:40.980> ID<00:30:41.159> it<00:30:41.700> makes<00:30:42.380> the<00:30:43.380> node 00:30:43.549 --> 00:30:43.559 align:start position:0% tie it to the node ID it makes the node 00:30:43.559 --> 00:30:45.289 align:start position:0% tie it to the node ID it makes the node ID<00:30:43.799> specifies<00:30:44.399> which<00:30:44.640> subnet<00:30:45.120> they're 00:30:45.289 --> 00:30:45.299 align:start position:0% ID specifies which subnet they're 00:30:45.299 --> 00:30:46.730 align:start position:0% ID specifies which subnet they're supposed<00:30:45.480> to<00:30:45.600> be<00:30:45.659> subscribed<00:30:46.080> to<00:30:46.200> so<00:30:46.559> when 00:30:46.730 --> 00:30:46.740 align:start position:0% supposed to be subscribed to so when 00:30:46.740 --> 00:30:48.289 align:start position:0% supposed to be subscribed to so when we're<00:30:46.860> doing<00:30:47.039> Discovery<00:30:47.520> queries<00:30:47.880> we<00:30:48.179> can 00:30:48.289 --> 00:30:48.299 align:start position:0% we're doing Discovery queries we can 00:30:48.299 --> 00:30:50.930 align:start position:0% we're doing Discovery queries we can actually<00:30:48.480> search<00:30:49.440> more<00:30:50.340> efficiently<00:30:50.700> for 00:30:50.930 --> 00:30:50.940 align:start position:0% actually search more efficiently for 00:30:50.940 --> 00:30:52.789 align:start position:0% actually search more efficiently for nodes<00:30:51.360> on<00:30:51.659> a<00:30:51.840> specific<00:30:52.080> subnet<00:30:52.440> because<00:30:52.620> it's 00:30:52.789 --> 00:30:52.799 align:start position:0% nodes on a specific subnet because it's 00:30:52.799 --> 00:30:54.529 align:start position:0% nodes on a specific subnet because it's tied<00:30:52.980> to<00:30:53.100> that<00:30:53.220> node<00:30:53.399> ID<00:30:53.580> so<00:30:54.059> there's<00:30:54.240> a<00:30:54.419> number 00:30:54.529 --> 00:30:54.539 align:start position:0% tied to that node ID so there's a number 00:30:54.539 --> 00:30:56.330 align:start position:0% tied to that node ID so there's a number of<00:30:54.659> benefits<00:30:54.960> it's<00:30:55.140> not<00:30:55.320> just<00:30:55.500> uh<00:30:56.039> we're 00:30:56.330 --> 00:30:56.340 align:start position:0% of benefits it's not just uh we're 00:30:56.340 --> 00:30:57.950 align:start position:0% of benefits it's not just uh we're helping<00:30:56.640> institutional<00:30:57.120> stakers<00:30:57.539> that's 00:30:57.950 --> 00:30:57.960 align:start position:0% helping institutional stakers that's 00:30:57.960 --> 00:31:00.169 align:start position:0% helping institutional stakers that's just<00:30:58.200> kind<00:30:58.380> of<00:30:58.500> like<00:30:58.559> a<00:30:58.740> byproduct<00:30:59.279> hey<00:30:59.880> uh 00:31:00.169 --> 00:31:00.179 align:start position:0% just kind of like a byproduct hey uh 00:31:00.179 --> 00:31:01.789 align:start position:0% just kind of like a byproduct hey uh cool<00:31:00.360> could<00:31:00.539> talk<00:31:00.720> to<00:31:00.840> you<00:31:00.899> guys<00:31:00.960> thanks<00:31:01.559> um<00:31:01.620> so 00:31:01.789 --> 00:31:01.799 align:start position:0% cool could talk to you guys thanks um so 00:31:01.799 --> 00:31:04.430 align:start position:0% cool could talk to you guys thanks um so you<00:31:01.919> mentioned<00:31:02.279> uh<00:31:02.760> reducing<00:31:03.539> bandwidth<00:31:04.380> um 00:31:04.430 --> 00:31:04.440 align:start position:0% you mentioned uh reducing bandwidth um 00:31:04.440 --> 00:31:07.070 align:start position:0% you mentioned uh reducing bandwidth um and<00:31:05.220> reducing<00:31:05.820> latency<00:31:06.240> to<00:31:06.720> like<00:31:06.840> avoid 00:31:07.070 --> 00:31:07.080 align:start position:0% and reducing latency to like avoid 00:31:07.080 --> 00:31:08.930 align:start position:0% and reducing latency to like avoid missing<00:31:07.440> expectations<00:31:07.980> something<00:31:08.700> that 00:31:08.930 --> 00:31:08.940 align:start position:0% missing expectations something that 00:31:08.940 --> 00:31:10.070 align:start position:0% missing expectations something that we've<00:31:09.120> looked<00:31:09.299> at<00:31:09.360> as<00:31:09.600> well<00:31:09.720> is<00:31:09.899> like 00:31:10.070 --> 00:31:10.080 align:start position:0% we've looked at as well is like 00:31:10.080 --> 00:31:12.169 align:start position:0% we've looked at as well is like affecting<00:31:10.440> the<00:31:10.620> effectiveness<00:31:11.279> ratings<00:31:12.120> um 00:31:12.169 --> 00:31:12.179 align:start position:0% affecting the effectiveness ratings um 00:31:12.179 --> 00:31:14.029 align:start position:0% affecting the effectiveness ratings um with<00:31:12.360> validators<00:31:13.320> um<00:31:13.380> can<00:31:13.620> you<00:31:13.740> guys<00:31:13.799> speak 00:31:14.029 --> 00:31:14.039 align:start position:0% with validators um can you guys speak 00:31:14.039 --> 00:31:16.130 align:start position:0% with validators um can you guys speak which<00:31:14.279> can<00:31:14.580> result<00:31:14.820> in<00:31:15.059> like<00:31:15.240> penalties<00:31:15.899> or 00:31:16.130 --> 00:31:16.140 align:start position:0% which can result in like penalties or 00:31:16.140 --> 00:31:18.830 align:start position:0% which can result in like penalties or loss<00:31:16.559> reduction<00:31:17.460> in<00:31:17.700> rewards<00:31:18.600> um<00:31:18.600> can<00:31:18.779> you 00:31:18.830 --> 00:31:18.840 align:start position:0% loss reduction in rewards um can you 00:31:18.840 --> 00:31:20.389 align:start position:0% loss reduction in rewards um can you guys<00:31:18.960> speak<00:31:19.140> to<00:31:19.320> how<00:31:19.559> this<00:31:19.860> would<00:31:19.980> help<00:31:20.159> with 00:31:20.389 --> 00:31:20.399 align:start position:0% guys speak to how this would help with 00:31:20.399 --> 00:31:23.029 align:start position:0% guys speak to how this would help with effective<00:31:20.880> Effectiveness<00:31:21.779> ratings<00:31:22.679> um<00:31:22.740> if<00:31:22.919> it 00:31:23.029 --> 00:31:23.039 align:start position:0% effective Effectiveness ratings um if it 00:31:23.039 --> 00:31:25.190 align:start position:0% effective Effectiveness ratings um if it would<00:31:23.640> um<00:31:23.700> which<00:31:23.880> I<00:31:24.059> I<00:31:24.360> guess<00:31:24.720> the<00:31:24.840> first<00:31:25.020> one 00:31:25.190 --> 00:31:25.200 align:start position:0% would um which I I guess the first one 00:31:25.200 --> 00:31:28.250 align:start position:0% would um which I I guess the first one is<00:31:25.559> kind<00:31:26.100> of<00:31:26.159> what<00:31:26.279> I<00:31:26.399> introde<00:31:26.880> with<00:31:27.000> my<00:31:27.840> my 00:31:28.250 --> 00:31:28.260 align:start position:0% is kind of what I introde with my my 00:31:28.260 --> 00:31:30.110 align:start position:0% is kind of what I introde with my my personal<00:31:28.559> uh<00:31:29.159> attestation<00:31:29.580> Effectiveness 00:31:30.110 --> 00:31:30.120 align:start position:0% personal uh attestation Effectiveness 00:31:30.120 --> 00:31:33.049 align:start position:0% personal uh attestation Effectiveness drops<00:31:30.419> when<00:31:30.539> someone<00:31:30.720> watches<00:31:31.260> Netflix<00:31:31.440> so<00:31:32.159> uh 00:31:33.049 --> 00:31:33.059 align:start position:0% drops when someone watches Netflix so uh 00:31:33.059 --> 00:31:35.389 align:start position:0% drops when someone watches Netflix so uh I<00:31:33.419> imagine<00:31:33.779> for<00:31:34.440> a<00:31:34.559> lot<00:31:34.620> more<00:31:34.740> homesteakers 00:31:35.389 --> 00:31:35.399 align:start position:0% I imagine for a lot more homesteakers 00:31:35.399 --> 00:31:36.649 align:start position:0% I imagine for a lot more homesteakers that<00:31:35.520> are<00:31:35.700> kind<00:31:35.880> of<00:31:35.940> on<00:31:36.000> the<00:31:36.120> bandwidth<00:31:36.480> limit 00:31:36.649 --> 00:31:36.659 align:start position:0% that are kind of on the bandwidth limit 00:31:36.659 --> 00:31:38.750 align:start position:0% that are kind of on the bandwidth limit or<00:31:37.080> their<00:31:37.320> upload<00:31:37.860> speed<00:31:38.039> is<00:31:38.220> quite<00:31:38.399> low<00:31:38.520> like 00:31:38.750 --> 00:31:38.760 align:start position:0% or their upload speed is quite low like 00:31:38.760 --> 00:31:40.970 align:start position:0% or their upload speed is quite low like in<00:31:38.940> like<00:31:39.179> in<00:31:39.299> Australia<00:31:39.720> and<00:31:40.200> we<00:31:40.380> reduce<00:31:40.679> the 00:31:40.970 --> 00:31:40.980 align:start position:0% in like in Australia and we reduce the 00:31:40.980 --> 00:31:43.010 align:start position:0% in like in Australia and we reduce the bandwidth<00:31:41.340> requirements<00:31:41.760> a<00:31:41.880> lot<00:31:42.000> Diva<00:31:42.899> said 00:31:43.010 --> 00:31:43.020 align:start position:0% bandwidth requirements a lot Diva said 00:31:43.020 --> 00:31:44.510 align:start position:0% bandwidth requirements a lot Diva said that<00:31:43.320> when<00:31:43.559> you<00:31:43.679> have<00:31:43.799> these<00:31:44.039> peaks<00:31:44.340> in 00:31:44.510 --> 00:31:44.520 align:start position:0% that when you have these peaks in 00:31:44.520 --> 00:31:46.070 align:start position:0% that when you have these peaks in bandwidth<00:31:44.940> you<00:31:45.120> you<00:31:45.360> can<00:31:45.480> miss<00:31:45.659> out<00:31:45.779> our 00:31:46.070 --> 00:31:46.080 align:start position:0% bandwidth you you can miss out our 00:31:46.080 --> 00:31:48.049 align:start position:0% bandwidth you you can miss out our stations<00:31:46.380> you<00:31:46.740> don't<00:31:46.860> you<00:31:47.100> don't<00:31:47.279> publish 00:31:48.049 --> 00:31:48.059 align:start position:0% stations you don't you don't publish 00:31:48.059 --> 00:31:49.909 align:start position:0% stations you don't you don't publish them<00:31:48.240> in<00:31:48.419> time<00:31:48.600> and<00:31:48.840> it's<00:31:49.200> not<00:31:49.320> just<00:31:49.500> missed 00:31:49.909 --> 00:31:49.919 align:start position:0% them in time and it's not just missed 00:31:49.919 --> 00:31:51.529 align:start position:0% them in time and it's not just missed but<00:31:50.039> you<00:31:50.220> also<00:31:50.460> get<00:31:50.700> penalized<00:31:51.179> if<00:31:51.360> they're 00:31:51.529 --> 00:31:51.539 align:start position:0% but you also get penalized if they're 00:31:51.539 --> 00:31:53.510 align:start position:0% but you also get penalized if they're late<00:31:51.779> uh<00:31:52.380> so<00:31:52.559> even<00:31:52.679> if<00:31:52.860> you<00:31:52.980> even<00:31:53.220> if<00:31:53.399> they 00:31:53.510 --> 00:31:53.520 align:start position:0% late uh so even if you even if they 00:31:53.520 --> 00:31:54.710 align:start position:0% late uh so even if you even if they still<00:31:53.640> get<00:31:53.760> included<00:31:54.059> in<00:31:54.120> a<00:31:54.240> block<00:31:54.360> but<00:31:54.539> later 00:31:54.710 --> 00:31:54.720 align:start position:0% still get included in a block but later 00:31:54.720 --> 00:31:56.450 align:start position:0% still get included in a block but later you<00:31:54.960> get<00:31:55.080> you<00:31:55.200> get<00:31:55.440> less<00:31:55.559> so<00:31:55.799> that<00:31:55.980> that<00:31:56.100> lowers 00:31:56.450 --> 00:31:56.460 align:start position:0% you get you get less so that that lowers 00:31:56.460 --> 00:31:58.669 align:start position:0% you get you get less so that that lowers the<00:31:56.640> attestation<00:31:57.059> Effectiveness 00:31:58.669 --> 00:31:58.679 align:start position:0% the attestation Effectiveness 00:31:58.679 --> 00:32:00.289 align:start position:0% the attestation Effectiveness um from<00:31:59.460> a<00:31:59.640> lot<00:31:59.700> of<00:31:59.760> the<00:31:59.880> people<00:31:59.940> that<00:32:00.120> use 00:32:00.289 --> 00:32:00.299 align:start position:0% um from a lot of the people that use 00:32:00.299 --> 00:32:03.590 align:start position:0% um from a lot of the people that use lighthouse<00:32:00.659> we<00:32:00.899> find<00:32:01.200> that<00:32:01.799> uh<00:32:02.460> that<00:32:03.179> there's 00:32:03.590 --> 00:32:03.600 align:start position:0% lighthouse we find that uh that there's 00:32:03.600 --> 00:32:06.409 align:start position:0% lighthouse we find that uh that there's a<00:32:03.720> number<00:32:03.960> of<00:32:04.020> Main<00:32:04.500> that<00:32:05.159> that<00:32:05.460> impact<00:32:06.240> the 00:32:06.409 --> 00:32:06.419 align:start position:0% a number of Main that that impact the 00:32:06.419 --> 00:32:08.210 align:start position:0% a number of Main that that impact the attestation<00:32:06.899> efficiency<00:32:07.320> and<00:32:07.620> that's<00:32:07.799> one<00:32:08.100> is 00:32:08.210 --> 00:32:08.220 align:start position:0% attestation efficiency and that's one is 00:32:08.220 --> 00:32:10.430 align:start position:0% attestation efficiency and that's one is bandwidth<00:32:08.820> and<00:32:09.120> the<00:32:09.240> other<00:32:09.360> one<00:32:09.539> is<00:32:09.720> CPU 00:32:10.430 --> 00:32:10.440 align:start position:0% bandwidth and the other one is CPU 00:32:10.440 --> 00:32:13.190 align:start position:0% bandwidth and the other one is CPU limitation<00:32:10.980> flight<00:32:11.279> processing<00:32:11.880> so<00:32:12.539> if 00:32:13.190 --> 00:32:13.200 align:start position:0% limitation flight processing so if 00:32:13.200 --> 00:32:14.990 align:start position:0% limitation flight processing so if you're<00:32:13.320> running<00:32:13.559> a<00:32:14.159> a<00:32:14.399> node<00:32:14.820> that's 00:32:14.990 --> 00:32:15.000 align:start position:0% you're running a a node that's 00:32:15.000 --> 00:32:18.289 align:start position:0% you're running a a node that's overburdened<00:32:15.659> and<00:32:16.140> and<00:32:16.640> this<00:32:17.640> the<00:32:18.000> topic 00:32:18.289 --> 00:32:18.299 align:start position:0% overburdened and and this the topic 00:32:18.299 --> 00:32:19.789 align:start position:0% overburdened and and this the topic subscription<00:32:18.659> is<00:32:18.899> another<00:32:19.260> thing<00:32:19.500> that<00:32:19.679> can 00:32:19.789 --> 00:32:19.799 align:start position:0% subscription is another thing that can 00:32:19.799 --> 00:32:20.930 align:start position:0% subscription is another thing that can overburden<00:32:20.220> a<00:32:20.340> node<00:32:20.520> because<00:32:20.640> if<00:32:20.820> you're 00:32:20.930 --> 00:32:20.940 align:start position:0% overburden a node because if you're 00:32:20.940 --> 00:32:22.250 align:start position:0% overburden a node because if you're subscribed<00:32:21.299> to<00:32:21.419> a<00:32:21.539> lot<00:32:21.600> of<00:32:21.720> notes<00:32:21.960> let's<00:32:22.140> say 00:32:22.250 --> 00:32:22.260 align:start position:0% subscribed to a lot of notes let's say 00:32:22.260 --> 00:32:24.049 align:start position:0% subscribed to a lot of notes let's say you<00:32:22.440> have<00:32:22.559> five<00:32:23.039> validators<00:32:23.580> attached<00:32:23.940> to<00:32:23.940> you 00:32:24.049 --> 00:32:24.059 align:start position:0% you have five validators attached to you 00:32:24.059 --> 00:32:25.669 align:start position:0% you have five validators attached to you and<00:32:24.179> you<00:32:24.299> have<00:32:24.360> five<00:32:24.480> Long<00:32:24.659> Live<00:32:24.899> subnets<00:32:25.320> you 00:32:25.669 --> 00:32:25.679 align:start position:0% and you have five Long Live subnets you 00:32:25.679 --> 00:32:27.169 align:start position:0% and you have five Long Live subnets you have<00:32:25.799> to<00:32:25.919> get<00:32:26.039> all<00:32:26.159> the<00:32:26.279> messages<00:32:26.399> and<00:32:27.059> you 00:32:27.169 --> 00:32:27.179 align:start position:0% have to get all the messages and you 00:32:27.179 --> 00:32:28.549 align:start position:0% have to get all the messages and you have<00:32:27.360> to<00:32:27.480> process<00:32:27.720> them<00:32:27.899> so<00:32:28.080> the<00:32:28.200> processing 00:32:28.549 --> 00:32:28.559 align:start position:0% have to process them so the processing 00:32:28.559 --> 00:32:30.350 align:start position:0% have to process them so the processing also<00:32:28.919> kills<00:32:29.220> you<00:32:29.279> and<00:32:29.460> lowers<00:32:29.880> your<00:32:30.059> average 00:32:30.350 --> 00:32:30.360 align:start position:0% also kills you and lowers your average 00:32:30.360 --> 00:32:32.149 align:start position:0% also kills you and lowers your average Effectiveness<00:32:31.020> so<00:32:31.380> if<00:32:31.500> we<00:32:31.620> get<00:32:31.799> that<00:32:31.919> in<00:32:32.039> there 00:32:32.149 --> 00:32:32.159 align:start position:0% Effectiveness so if we get that in there 00:32:32.159 --> 00:32:34.130 align:start position:0% Effectiveness so if we get that in there that<00:32:32.399> all<00:32:32.580> should<00:32:32.880> in<00:32:33.120> principle<00:32:33.659> improve<00:32:34.020> the 00:32:34.130 --> 00:32:34.140 align:start position:0% that all should in principle improve the 00:32:34.140 --> 00:32:35.630 align:start position:0% that all should in principle improve the effectiveness<00:32:34.620> because<00:32:34.919> of<00:32:35.100> the<00:32:35.220> bandwidth 00:32:35.630 --> 00:32:35.640 align:start position:0% effectiveness because of the bandwidth 00:32:35.640 --> 00:32:37.430 align:start position:0% effectiveness because of the bandwidth and<00:32:35.760> and<00:32:36.059> because<00:32:36.299> it<00:32:36.480> lowers<00:32:36.779> the<00:32:36.899> CPU<00:32:37.200> usage 00:32:37.430 --> 00:32:37.440 align:start position:0% and and because it lowers the CPU usage 00:32:37.440 --> 00:32:39.230 align:start position:0% and and because it lowers the CPU usage of<00:32:37.559> your<00:32:37.740> node<00:32:37.980> would<00:32:38.340> it<00:32:38.460> be<00:32:38.580> possible<00:32:38.880> for<00:32:39.120> a 00:32:39.230 --> 00:32:39.240 align:start position:0% of your node would it be possible for a 00:32:39.240 --> 00:32:41.330 align:start position:0% of your node would it be possible for a node<00:32:39.419> to<00:32:39.539> detect<00:32:39.779> that<00:32:40.020> it's<00:32:40.140> been<00:32:40.440> choked<00:32:40.919> if 00:32:41.330 --> 00:32:41.340 align:start position:0% node to detect that it's been choked if 00:32:41.340 --> 00:32:42.769 align:start position:0% node to detect that it's been choked if so 00:32:42.769 --> 00:32:42.779 align:start position:0% so 00:32:42.779 --> 00:32:46.010 align:start position:0% so um<00:32:42.840> could<00:32:43.380> it<00:32:43.500> somehow<00:32:43.799> combine<00:32:44.220> that<00:32:44.460> uh<00:32:45.360> with 00:32:46.010 --> 00:32:46.020 align:start position:0% um could it somehow combine that uh with 00:32:46.020 --> 00:32:48.610 align:start position:0% um could it somehow combine that uh with being<00:32:46.260> dishonest<00:32:46.740> about<00:32:46.860> its<00:32:47.520> subnet<00:32:48.000> account 00:32:48.610 --> 00:32:48.620 align:start position:0% being dishonest about its subnet account 00:32:48.620 --> 00:32:51.769 align:start position:0% being dishonest about its subnet account and<00:32:49.620> other<00:32:49.860> grief<00:32:50.340> or<00:32:50.580> otherwise<00:32:51.000> stall<00:32:51.419> its 00:32:51.769 --> 00:32:51.779 align:start position:0% and other grief or otherwise stall its 00:32:51.779 --> 00:32:53.690 align:start position:0% and other grief or otherwise stall its local<00:32:51.899> node<00:32:52.380> graph<00:32:52.740> sorry<00:32:53.159> I<00:32:53.279> missed<00:32:53.520> the<00:32:53.580> last 00:32:53.690 --> 00:32:53.700 align:start position:0% local node graph sorry I missed the last 00:32:53.700 --> 00:32:56.029 align:start position:0% local node graph sorry I missed the last part<00:32:53.880> could<00:32:54.600> it<00:32:54.779> either<00:32:54.960> if<00:32:55.440> it<00:32:55.559> could<00:32:55.679> combine 00:32:56.029 --> 00:32:56.039 align:start position:0% part could it either if it could combine 00:32:56.039 --> 00:32:57.889 align:start position:0% part could it either if it could combine that<00:32:56.159> with<00:32:56.399> uh<00:32:56.760> being<00:32:56.940> dishonest<00:32:57.419> about<00:32:57.600> its 00:32:57.889 --> 00:32:57.899 align:start position:0% that with uh being dishonest about its 00:32:57.899 --> 00:33:00.710 align:start position:0% that with uh being dishonest about its subnet<00:32:58.320> account<00:32:58.860> connection<00:32:59.399> could<00:33:00.299> it<00:33:00.539> just 00:33:00.710 --> 00:33:00.720 align:start position:0% subnet account connection could it just 00:33:00.720 --> 00:33:04.430 align:start position:0% subnet account connection could it just stall<00:33:01.200> or<00:33:01.380> otherwise<00:33:01.799> grief<00:33:02.220> it's<00:33:02.520> local<00:33:02.820> node 00:33:04.430 --> 00:33:04.440 align:start position:0% stall or otherwise grief it's local node 00:33:04.440 --> 00:33:08.330 align:start position:0% stall or otherwise grief it's local node graph<00:33:05.460> oh<00:33:05.880> wow<00:33:06.120> stream<00:33:06.600> is<00:33:06.960> explicit 00:33:08.330 --> 00:33:08.340 align:start position:0% graph oh wow stream is explicit 00:33:08.340 --> 00:33:11.510 align:start position:0% graph oh wow stream is explicit so<00:33:08.940> I<00:33:09.179> know<00:33:09.299> this<00:33:09.539> is<00:33:09.720> actually<00:33:09.840> going<00:33:10.260> to 00:33:11.510 --> 00:33:11.520 align:start position:0% so I know this is actually going to 00:33:11.520 --> 00:33:13.669 align:start position:0% so I know this is actually going to know<00:33:12.179> it's<00:33:12.539> going<00:33:12.779> to<00:33:12.899> be<00:33:13.080> showed<00:33:13.500> we're 00:33:13.669 --> 00:33:13.679 align:start position:0% know it's going to be showed we're 00:33:13.679 --> 00:33:16.549 align:start position:0% know it's going to be showed we're asking<00:33:14.159> him<00:33:14.399> to<00:33:14.760> stop<00:33:15.419> sending<00:33:15.899> messages<00:33:16.080> to 00:33:16.549 --> 00:33:16.559 align:start position:0% asking him to stop sending messages to 00:33:16.559 --> 00:33:20.210 align:start position:0% asking him to stop sending messages to us<00:33:16.760> it's<00:33:17.760> not<00:33:18.120> yeah<00:33:18.840> you<00:33:19.080> know<00:33:19.200> it's<00:33:19.380> I<00:33:19.919> know<00:33:20.100> it 00:33:20.210 --> 00:33:20.220 align:start position:0% us it's not yeah you know it's I know it 00:33:20.220 --> 00:33:23.870 align:start position:0% us it's not yeah you know it's I know it sounds<00:33:20.399> similar<00:33:20.820> to<00:33:20.940> what<00:33:21.440> is<00:33:22.440> happening<00:33:22.980> for 00:33:23.870 --> 00:33:23.880 align:start position:0% sounds similar to what is happening for 00:33:23.880 --> 00:33:26.990 align:start position:0% sounds similar to what is happening for example<00:33:24.179> in<00:33:24.480> in<00:33:25.440> strategies<00:33:26.100> for<00:33:26.399> example<00:33:26.640> in 00:33:26.990 --> 00:33:27.000 align:start position:0% example in in strategies for example in 00:33:27.000 --> 00:33:28.970 align:start position:0% example in in strategies for example in I<00:33:27.240> don't<00:33:27.360> know<00:33:27.419> follow<00:33:27.960> sharing 00:33:28.970 --> 00:33:28.980 align:start position:0% I don't know follow sharing 00:33:28.980 --> 00:33:30.649 align:start position:0% I don't know follow sharing but<00:33:29.399> it's<00:33:29.519> different<00:33:29.820> in<00:33:30.179> the<00:33:30.299> sense<00:33:30.419> that 00:33:30.649 --> 00:33:30.659 align:start position:0% but it's different in the sense that 00:33:30.659 --> 00:33:32.930 align:start position:0% but it's different in the sense that we're<00:33:30.899> the<00:33:31.380> ones<00:33:31.620> asking<00:33:32.039> the<00:33:32.220> peer<00:33:32.519> to<00:33:32.760> just 00:33:32.930 --> 00:33:32.940 align:start position:0% we're the ones asking the peer to just 00:33:32.940 --> 00:33:34.610 align:start position:0% we're the ones asking the peer to just stop<00:33:33.240> sending<00:33:33.659> the<00:33:33.779> messages 00:33:34.610 --> 00:33:34.620 align:start position:0% stop sending the messages 00:33:34.620 --> 00:33:37.430 align:start position:0% stop sending the messages so<00:33:35.279> it's<00:33:35.460> kind<00:33:35.820> of<00:33:35.940> a<00:33:36.059> benefit<00:33:36.299> for<00:33:36.720> them<00:33:36.899> so 00:33:37.430 --> 00:33:37.440 align:start position:0% so it's kind of a benefit for them so 00:33:37.440 --> 00:33:40.130 align:start position:0% so it's kind of a benefit for them so when<00:33:37.799> uh<00:33:38.460> when<00:33:38.940> we<00:33:39.059> connect<00:33:39.179> to<00:33:39.360> appear<00:33:39.720> uh 00:33:40.130 --> 00:33:40.140 align:start position:0% when uh when we connect to appear uh 00:33:40.140 --> 00:33:41.690 align:start position:0% when uh when we connect to appear uh let's<00:33:40.320> say<00:33:40.440> let's<00:33:40.620> say<00:33:40.799> in<00:33:40.980> this<00:33:41.159> new<00:33:41.340> regime 00:33:41.690 --> 00:33:41.700 align:start position:0% let's say let's say in this new regime 00:33:41.700 --> 00:33:43.430 align:start position:0% let's say let's say in this new regime where<00:33:41.880> we<00:33:42.059> have<00:33:42.240> every<00:33:42.840> node<00:33:43.140> has<00:33:43.320> to 00:33:43.430 --> 00:33:43.440 align:start position:0% where we have every node has to 00:33:43.440 --> 00:33:44.750 align:start position:0% where we have every node has to subscribe<00:33:43.679> to<00:33:43.799> atopic<00:33:44.100> based<00:33:44.279> on<00:33:44.340> its<00:33:44.460> node<00:33:44.640> ID 00:33:44.750 --> 00:33:44.760 align:start position:0% subscribe to atopic based on its node ID 00:33:44.760 --> 00:33:47.210 align:start position:0% subscribe to atopic based on its node ID we<00:33:45.179> can<00:33:45.299> look<00:33:45.360> at<00:33:45.539> its<00:33:45.840> its<00:33:46.320> peer<00:33:46.500> ID<00:33:46.620> but<00:33:46.919> let's 00:33:47.210 --> 00:33:47.220 align:start position:0% we can look at its its peer ID but let's 00:33:47.220 --> 00:33:48.769 align:start position:0% we can look at its its peer ID but let's say<00:33:47.340> it's<00:33:47.460> node<00:33:47.700> ID<00:33:47.880> we<00:33:48.360> know<00:33:48.480> that<00:33:48.600> it's 00:33:48.769 --> 00:33:48.779 align:start position:0% say it's node ID we know that it's 00:33:48.779 --> 00:33:49.850 align:start position:0% say it's node ID we know that it's supposed<00:33:48.899> to<00:33:49.019> be<00:33:49.140> subscribed<00:33:49.440> to<00:33:49.559> let's<00:33:49.679> say 00:33:49.850 --> 00:33:49.860 align:start position:0% supposed to be subscribed to let's say 00:33:49.860 --> 00:33:51.110 align:start position:0% supposed to be subscribed to let's say topic<00:33:50.159> three 00:33:51.110 --> 00:33:51.120 align:start position:0% topic three 00:33:51.120 --> 00:33:52.850 align:start position:0% topic three um<00:33:51.179> the<00:33:51.480> way<00:33:51.600> that<00:33:51.779> we<00:33:51.960> when<00:33:52.140> we<00:33:52.380> connect<00:33:52.440> via 00:33:52.850 --> 00:33:52.860 align:start position:0% um the way that we when we connect via 00:33:52.860 --> 00:33:55.130 align:start position:0% um the way that we when we connect via gossip<00:33:53.159> sub<00:33:53.340> uh<00:33:54.179> they<00:33:54.600> should<00:33:54.720> send<00:33:54.960> our 00:33:55.130 --> 00:33:55.140 align:start position:0% gossip sub uh they should send our 00:33:55.140 --> 00:33:56.570 align:start position:0% gossip sub uh they should send our subscriptions<00:33:55.559> about<00:33:55.740> what<00:33:56.039> it's<00:33:56.159> subscribed 00:33:56.570 --> 00:33:56.580 align:start position:0% subscriptions about what it's subscribed 00:33:56.580 --> 00:33:58.850 align:start position:0% subscriptions about what it's subscribed to<00:33:56.700> and<00:33:57.360> and<00:33:57.659> if<00:33:57.960> it's<00:33:58.140> not<00:33:58.320> if<00:33:58.620> it's<00:33:58.740> not 00:33:58.850 --> 00:33:58.860 align:start position:0% to and and if it's not if it's not 00:33:58.860 --> 00:33:59.930 align:start position:0% to and and if it's not if it's not subscribed<00:33:59.220> to<00:33:59.340> that<00:33:59.460> we<00:33:59.580> know<00:33:59.700> that<00:33:59.820> it's 00:33:59.930 --> 00:33:59.940 align:start position:0% subscribed to that we know that it's 00:33:59.940 --> 00:34:01.370 align:start position:0% subscribed to that we know that it's being<00:34:00.120> malicious<00:34:00.480> or<00:34:00.659> faulty<00:34:01.019> straight<00:34:01.200> away 00:34:01.370 --> 00:34:01.380 align:start position:0% being malicious or faulty straight away 00:34:01.380 --> 00:34:03.470 align:start position:0% being malicious or faulty straight away and<00:34:01.559> we<00:34:01.679> can<00:34:01.860> just<00:34:01.980> disconnect<00:34:02.159> it<00:34:02.580> uh<00:34:03.179> there's 00:34:03.470 --> 00:34:03.480 align:start position:0% and we can just disconnect it uh there's 00:34:03.480 --> 00:34:04.909 align:start position:0% and we can just disconnect it uh there's technicalities<00:34:04.019> where<00:34:04.260> I<00:34:04.380> can<00:34:04.500> say<00:34:04.620> that<00:34:04.740> it's 00:34:04.909 --> 00:34:04.919 align:start position:0% technicalities where I can say that it's 00:34:04.919 --> 00:34:07.430 align:start position:0% technicalities where I can say that it's subscribed<00:34:05.279> but<00:34:05.460> then<00:34:05.760> won't<00:34:06.179> let<00:34:06.419> us<00:34:06.600> uh<00:34:07.140> so 00:34:07.430 --> 00:34:07.440 align:start position:0% subscribed but then won't let us uh so 00:34:07.440 --> 00:34:09.290 align:start position:0% subscribed but then won't let us uh so the<00:34:07.919> next<00:34:08.040> the<00:34:08.220> next<00:34:08.399> phase<00:34:08.639> of<00:34:08.820> the<00:34:08.940> thing<00:34:09.060> is 00:34:09.290 --> 00:34:09.300 align:start position:0% the next the next phase of the thing is 00:34:09.300 --> 00:34:11.869 align:start position:0% the next the next phase of the thing is we<00:34:09.720> try<00:34:09.899> and<00:34:10.020> create<00:34:10.200> a<00:34:10.440> mesh<00:34:10.800> mesh<00:34:11.339> Network<00:34:11.460> so 00:34:11.869 --> 00:34:11.879 align:start position:0% we try and create a mesh mesh Network so 00:34:11.879 --> 00:34:14.089 align:start position:0% we try and create a mesh mesh Network so if<00:34:12.540> we're<00:34:13.139> if<00:34:13.379> we're<00:34:13.440> connected<00:34:13.740> to<00:34:13.859> let's<00:34:14.040> say 00:34:14.089 --> 00:34:14.099 align:start position:0% if we're if we're connected to let's say 00:34:14.099 --> 00:34:16.369 align:start position:0% if we're if we're connected to let's say 100<00:34:14.339> pairs<00:34:14.760> we<00:34:15.000> only<00:34:15.119> really<00:34:15.419> form<00:34:15.839> a<00:34:16.020> mesh 00:34:16.369 --> 00:34:16.379 align:start position:0% 100 pairs we only really form a mesh 00:34:16.379 --> 00:34:17.869 align:start position:0% 100 pairs we only really form a mesh with<00:34:16.500> with<00:34:16.859> the<00:34:17.099> mesh<00:34:17.280> degree<00:34:17.520> with<00:34:17.700> like 00:34:17.869 --> 00:34:17.879 align:start position:0% with with the mesh degree with like 00:34:17.879 --> 00:34:20.210 align:start position:0% with with the mesh degree with like three<00:34:18.000> of<00:34:18.179> them<00:34:18.300> so<00:34:19.020> in<00:34:19.500> principle<00:34:19.800> they<00:34:20.040> could 00:34:20.210 --> 00:34:20.220 align:start position:0% three of them so in principle they could 00:34:20.220 --> 00:34:22.010 align:start position:0% three of them so in principle they could always<00:34:20.399> just<00:34:20.940> say<00:34:21.060> no<00:34:21.240> no<00:34:21.359> you<00:34:21.599> can't<00:34:21.659> go<00:34:21.839> on<00:34:21.899> my 00:34:22.010 --> 00:34:22.020 align:start position:0% always just say no no you can't go on my 00:34:22.020 --> 00:34:23.450 align:start position:0% always just say no no you can't go on my Mash<00:34:22.260> you<00:34:22.440> can't<00:34:22.500> call<00:34:22.679> my<00:34:22.800> mesh<00:34:23.040> I'm<00:34:23.159> full<00:34:23.280> I'm 00:34:23.450 --> 00:34:23.460 align:start position:0% Mash you can't call my mesh I'm full I'm 00:34:23.460 --> 00:34:24.710 align:start position:0% Mash you can't call my mesh I'm full I'm full<00:34:23.580> I'm<00:34:23.700> full<00:34:23.879> so<00:34:24.060> that's<00:34:24.179> one<00:34:24.359> way<00:34:24.480> to<00:34:24.599> kind 00:34:24.710 --> 00:34:24.720 align:start position:0% full I'm full so that's one way to kind 00:34:24.720 --> 00:34:27.770 align:start position:0% full I'm full so that's one way to kind of<00:34:24.839> grief<00:34:25.080> Us<00:34:25.260> in<00:34:25.679> that<00:34:26.040> scenario<00:34:26.599> they<00:34:27.599> still 00:34:27.770 --> 00:34:27.780 align:start position:0% of grief Us in that scenario they still 00:34:27.780 --> 00:34:29.149 align:start position:0% of grief Us in that scenario they still have<00:34:27.899> to<00:34:28.080> forward<00:34:28.260> us<00:34:28.500> gossip<00:34:28.800> sub<00:34:28.919> messages 00:34:29.149 --> 00:34:29.159 align:start position:0% have to forward us gossip sub messages 00:34:29.159 --> 00:34:31.730 align:start position:0% have to forward us gossip sub messages there's<00:34:29.940> a<00:34:30.119> there's<00:34:30.599> a<00:34:30.899> small<00:34:31.320> mechanism 00:34:31.730 --> 00:34:31.740 align:start position:0% there's a there's a small mechanism 00:34:31.740 --> 00:34:34.070 align:start position:0% there's a there's a small mechanism inside<00:34:32.040> gossip<00:34:32.520> sub<00:34:32.700> that<00:34:33.240> is<00:34:33.599> called<00:34:33.720> gossip 00:34:34.070 --> 00:34:34.080 align:start position:0% inside gossip sub that is called gossip 00:34:34.080 --> 00:34:36.409 align:start position:0% inside gossip sub that is called gossip subscribing<00:34:34.379> as<00:34:34.500> you<00:34:34.679> just<00:34:34.980> in<00:34:35.220> 1.1<00:34:35.700> which 00:34:36.409 --> 00:34:36.419 align:start position:0% subscribing as you just in 1.1 which 00:34:36.419 --> 00:34:39.050 align:start position:0% subscribing as you just in 1.1 which somehow<00:34:36.899> mitigates<00:34:37.440> uh<00:34:38.000> attempts<00:34:39.000> to 00:34:39.050 --> 00:34:39.060 align:start position:0% somehow mitigates uh attempts to 00:34:39.060 --> 00:34:40.669 align:start position:0% somehow mitigates uh attempts to mitigate<00:34:39.359> censoring<00:34:39.839> so<00:34:40.020> where<00:34:40.260> where<00:34:40.500> you 00:34:40.669 --> 00:34:40.679 align:start position:0% mitigate censoring so where where you 00:34:40.679 --> 00:34:41.990 align:start position:0% mitigate censoring so where where you just<00:34:40.800> say<00:34:41.099> that<00:34:41.220> you're<00:34:41.339> subscribe<00:34:41.879> you<00:34:41.879> do 00:34:41.990 --> 00:34:42.000 align:start position:0% just say that you're subscribe you do 00:34:42.000 --> 00:34:43.730 align:start position:0% just say that you're subscribe you do nothing<00:34:42.179> and<00:34:43.020> and<00:34:43.200> the<00:34:43.500> whole<00:34:43.619> network 00:34:43.730 --> 00:34:43.740 align:start position:0% nothing and and the whole network 00:34:43.740 --> 00:34:44.990 align:start position:0% nothing and and the whole network essentially<00:34:44.159> tries<00:34:44.339> to<00:34:44.460> kick<00:34:44.580> you<00:34:44.700> out<00:34:44.820> of<00:34:44.940> the 00:34:44.990 --> 00:34:45.000 align:start position:0% essentially tries to kick you out of the 00:34:45.000 --> 00:34:47.629 align:start position:0% essentially tries to kick you out of the mesh<00:34:45.240> in<00:34:45.899> terms<00:34:46.080> of<00:34:46.200> while<00:34:46.320> being<00:34:46.560> choked<00:34:47.040> we 00:34:47.629 --> 00:34:47.639 align:start position:0% mesh in terms of while being choked we 00:34:47.639 --> 00:34:49.010 align:start position:0% mesh in terms of while being choked we only<00:34:47.760> choke<00:34:48.060> people<00:34:48.240> that<00:34:48.419> are<00:34:48.540> in<00:34:48.599> our<00:34:48.720> mesh 00:34:49.010 --> 00:34:49.020 align:start position:0% only choke people that are in our mesh 00:34:49.020 --> 00:34:50.570 align:start position:0% only choke people that are in our mesh so<00:34:49.139> only<00:34:49.320> people<00:34:49.560> that<00:34:49.740> are<00:34:49.919> subscribed<00:34:50.339> and 00:34:50.570 --> 00:34:50.580 align:start position:0% so only people that are subscribed and 00:34:50.580 --> 00:34:52.310 align:start position:0% so only people that are subscribed and then<00:34:50.700> once<00:34:51.000> they've<00:34:51.240> grafted<00:34:51.659> with<00:34:51.780> us<00:34:51.960> so<00:34:52.139> we 00:34:52.310 --> 00:34:52.320 align:start position:0% then once they've grafted with us so we 00:34:52.320 --> 00:34:53.690 align:start position:0% then once they've grafted with us so we form<00:34:52.500> this<00:34:52.740> mesh<00:34:53.040> connection<00:34:53.159> which<00:34:53.520> means 00:34:53.690 --> 00:34:53.700 align:start position:0% form this mesh connection which means 00:34:53.700 --> 00:34:55.250 align:start position:0% form this mesh connection which means they<00:34:53.820> have<00:34:54.000> to<00:34:54.060> be<00:34:54.179> subscribed<00:34:54.659> they<00:34:55.020> have<00:34:55.200> to 00:34:55.250 --> 00:34:55.260 align:start position:0% they have to be subscribed they have to 00:34:55.260 --> 00:34:56.510 align:start position:0% they have to be subscribed they have to be<00:34:55.379> sending<00:34:55.619> us<00:34:55.740> messages<00:34:55.919> if<00:34:56.280> they're<00:34:56.399> not 00:34:56.510 --> 00:34:56.520 align:start position:0% be sending us messages if they're not 00:34:56.520 --> 00:34:58.790 align:start position:0% be sending us messages if they're not sending<00:34:56.760> us<00:34:56.820> messages<00:34:57.060> 1.1<00:34:57.960> scoring<00:34:58.619> we'll 00:34:58.790 --> 00:34:58.800 align:start position:0% sending us messages 1.1 scoring we'll 00:34:58.800 --> 00:35:00.470 align:start position:0% sending us messages 1.1 scoring we'll kick<00:34:58.920> them<00:34:59.040> out<00:34:59.220> and<00:34:59.760> then<00:34:59.820> we<00:35:00.000> then<00:35:00.180> we<00:35:00.359> choke 00:35:00.470 --> 00:35:00.480 align:start position:0% kick them out and then we then we choke 00:35:00.480 --> 00:35:02.810 align:start position:0% kick them out and then we then we choke or<00:35:00.720> unchoke<00:35:01.080> them<00:35:01.260> in<00:35:01.740> order<00:35:01.920> for<00:35:02.400> them<00:35:02.580> to<00:35:02.760> be 00:35:02.810 --> 00:35:02.820 align:start position:0% or unchoke them in order for them to be 00:35:02.820 --> 00:35:04.970 align:start position:0% or unchoke them in order for them to be malicious<00:35:03.240> and<00:35:03.420> try<00:35:03.660> and<00:35:04.140> cheat<00:35:04.440> that<00:35:04.740> system 00:35:04.970 --> 00:35:04.980 align:start position:0% malicious and try and cheat that system 00:35:04.980 --> 00:35:07.250 align:start position:0% malicious and try and cheat that system they're<00:35:05.580> choking<00:35:05.940> abstract<00:35:06.359> the<00:35:06.780> choking 00:35:07.250 --> 00:35:07.260 align:start position:0% they're choking abstract the choking 00:35:07.260 --> 00:35:09.290 align:start position:0% they're choking abstract the choking strategy<00:35:07.680> is<00:35:07.980> is<00:35:08.160> abstract<00:35:08.580> and<00:35:08.880> can<00:35:09.060> be 00:35:09.290 --> 00:35:09.300 align:start position:0% strategy is is abstract and can be 00:35:09.300 --> 00:35:11.150 align:start position:0% strategy is is abstract and can be implemented<00:35:09.839> independently<00:35:10.380> on<00:35:10.619> each<00:35:10.800> node 00:35:11.150 --> 00:35:11.160 align:start position:0% implemented independently on each node 00:35:11.160 --> 00:35:13.130 align:start position:0% implemented independently on each node so<00:35:11.700> you<00:35:11.940> don't<00:35:12.119> know<00:35:12.300> on<00:35:12.540> each<00:35:12.660> of<00:35:12.780> your<00:35:12.900> peers 00:35:13.130 --> 00:35:13.140 align:start position:0% so you don't know on each of your peers 00:35:13.140 --> 00:35:14.810 align:start position:0% so you don't know on each of your peers what<00:35:13.320> what<00:35:13.500> is<00:35:13.740> specifically<00:35:14.220> their<00:35:14.400> choking 00:35:14.810 --> 00:35:14.820 align:start position:0% what what is specifically their choking 00:35:14.820 --> 00:35:16.250 align:start position:0% what what is specifically their choking strategy<00:35:15.060> they<00:35:15.300> could<00:35:15.480> just<00:35:15.599> pick<00:35:15.839> random 00:35:16.250 --> 00:35:16.260 align:start position:0% strategy they could just pick random 00:35:16.260 --> 00:35:18.170 align:start position:0% strategy they could just pick random nodes<00:35:16.500> on<00:35:16.619> their<00:35:16.680> mash<00:35:16.920> and<00:35:17.040> choke<00:35:17.220> people<00:35:17.460> so 00:35:18.170 --> 00:35:18.180 align:start position:0% nodes on their mash and choke people so 00:35:18.180 --> 00:35:20.030 align:start position:0% nodes on their mash and choke people so I<00:35:18.599> think<00:35:18.660> there<00:35:18.900> is<00:35:19.020> an<00:35:19.320> Avenue<00:35:19.560> of<00:35:19.920> security 00:35:20.030 --> 00:35:20.040 align:start position:0% I think there is an Avenue of security 00:35:20.040 --> 00:35:21.890 align:start position:0% I think there is an Avenue of security to<00:35:20.520> to<00:35:20.640> look<00:35:20.820> in<00:35:21.000> there<00:35:21.180> that<00:35:21.480> hasn't<00:35:21.780> been 00:35:21.890 --> 00:35:21.900 align:start position:0% to to look in there that hasn't been 00:35:21.900 --> 00:35:23.810 align:start position:0% to to look in there that hasn't been done<00:35:22.020> yet<00:35:22.260> but<00:35:22.740> I<00:35:22.920> imagine<00:35:23.040> we<00:35:23.460> can<00:35:23.640> probably 00:35:23.810 --> 00:35:23.820 align:start position:0% done yet but I imagine we can probably 00:35:23.820 --> 00:35:24.950 align:start position:0% done yet but I imagine we can probably solve<00:35:24.180> that<00:35:24.300> with<00:35:24.420> some<00:35:24.540> of<00:35:24.660> the<00:35:24.720> scoring 00:35:24.950 --> 00:35:24.960 align:start position:0% solve that with some of the scoring 00:35:24.960 --> 00:35:26.690 align:start position:0% solve that with some of the scoring parameters<00:35:25.260> in<00:35:25.380> gossips<00:35:25.680> up<00:35:25.920> thank<00:35:26.460> you<00:35:26.579> very 00:35:26.690 --> 00:35:26.700 align:start position:0% parameters in gossips up thank you very 00:35:26.700 --> 00:35:29.030 align:start position:0% parameters in gossips up thank you very much<00:35:26.880> Diva<00:35:27.660> thank<00:35:28.020> you<00:35:28.140> very<00:35:28.320> much<00:35:28.440> Adrian 00:35:29.030 --> 00:35:29.040 align:start position:0% much Diva thank you very much Adrian 00:35:29.040 --> 00:35:31.820 align:start position:0% much Diva thank you very much Adrian thanks