WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.870 align:start position:0% [Music] 00:00:09.870 --> 00:00:09.880 align:start position:0% [Music] 00:00:09.880 --> 00:00:11.310 align:start position:0% [Music] hi 00:00:11.310 --> 00:00:11.320 align:start position:0% hi 00:00:11.320 --> 00:00:15.190 align:start position:0% hi hello<00:00:12.320> so<00:00:13.000> yes<00:00:13.320> I<00:00:13.480> have<00:00:13.599> a<00:00:13.679> long<00:00:13.920> title<00:00:14.799> uh<00:00:14.920> so<00:00:15.120> I 00:00:15.190 --> 00:00:15.200 align:start position:0% hello so yes I have a long title uh so I 00:00:15.200 --> 00:00:17.630 align:start position:0% hello so yes I have a long title uh so I will<00:00:15.320> be<00:00:15.519> speaking<00:00:15.839> about<00:00:16.359> data<00:00:16.680> Varity 00:00:17.630 --> 00:00:17.640 align:start position:0% will be speaking about data Varity 00:00:17.640 --> 00:00:20.710 align:start position:0% will be speaking about data Varity sampling<00:00:18.640> and<00:00:19.279> uh<00:00:19.600> it's<00:00:19.720> a<00:00:19.840> long<00:00:20.080> title<00:00:20.480> and<00:00:20.600> I 00:00:20.710 --> 00:00:20.720 align:start position:0% sampling and uh it's a long title and I 00:00:20.720 --> 00:00:22.109 align:start position:0% sampling and uh it's a long title and I didn't<00:00:20.920> want<00:00:21.160> to<00:00:21.279> make<00:00:21.400> it<00:00:21.480> longer<00:00:21.920> but 00:00:22.109 --> 00:00:22.119 align:start position:0% didn't want to make it longer but 00:00:22.119 --> 00:00:25.029 align:start position:0% didn't want to make it longer but actually<00:00:22.439> I<00:00:22.560> have<00:00:22.680> to<00:00:22.800> make<00:00:22.960> a<00:00:23.720> small<00:00:24.720> it's<00:00:24.880> not 00:00:25.029 --> 00:00:25.039 align:start position:0% actually I have to make a small it's not 00:00:25.039 --> 00:00:28.550 align:start position:0% actually I have to make a small it's not even<00:00:25.240> blocks<00:00:26.000> it's<00:00:26.560> data<00:00:26.920> variability<00:00:27.640> space 00:00:28.550 --> 00:00:28.560 align:start position:0% even blocks it's data variability space 00:00:28.560 --> 00:00:32.030 align:start position:0% even blocks it's data variability space that<00:00:28.679> we<00:00:28.760> are<00:00:28.920> speaking<00:00:29.279> of<00:00:30.320> so<00:00:30.560> let's<00:00:30.880> see<00:00:31.880> who 00:00:32.030 --> 00:00:32.040 align:start position:0% that we are speaking of so let's see who 00:00:32.040 --> 00:00:34.869 align:start position:0% that we are speaking of so let's see who we<00:00:32.160> are<00:00:32.520> first<00:00:33.360> uh<00:00:33.640> I'm<00:00:33.840> chabba<00:00:34.399> I'm<00:00:34.559> from<00:00:34.719> the 00:00:34.869 --> 00:00:34.879 align:start position:0% we are first uh I'm chabba I'm from the 00:00:34.879 --> 00:00:37.549 align:start position:0% we are first uh I'm chabba I'm from the resarch<00:00:35.239> team<00:00:35.600> from<00:00:36.200> codex<00:00:37.200> uh<00:00:37.320> we<00:00:37.440> are 00:00:37.549 --> 00:00:37.559 align:start position:0% resarch team from codex uh we are 00:00:37.559 --> 00:00:39.350 align:start position:0% resarch team from codex uh we are working<00:00:37.960> on<00:00:38.320> uh<00:00:38.559> decentralized<00:00:39.079> storage 00:00:39.350 --> 00:00:39.360 align:start position:0% working on uh decentralized storage 00:00:39.360 --> 00:00:41.229 align:start position:0% working on uh decentralized storage Network<00:00:39.760> providing<00:00:40.200> high<00:00:40.399> durability 00:00:41.229 --> 00:00:41.239 align:start position:0% Network providing high durability 00:00:41.239 --> 00:00:43.310 align:start position:0% Network providing high durability guarantees<00:00:42.239> and<00:00:42.360> our<00:00:42.520> research<00:00:42.840> team<00:00:43.000> is<00:00:43.120> also 00:00:43.310 --> 00:00:43.320 align:start position:0% guarantees and our research team is also 00:00:43.320 --> 00:00:46.029 align:start position:0% guarantees and our research team is also working<00:00:43.640> with<00:00:43.800> thef<00:00:44.399> on<00:00:44.640> datability 00:00:46.029 --> 00:00:46.039 align:start position:0% working with thef on datability 00:00:46.039 --> 00:00:50.069 align:start position:0% working with thef on datability sampling<00:00:47.039> and<00:00:47.239> also<00:00:48.039> uh<00:00:48.199> the<00:00:48.320> client<00:00:49.079> themes 00:00:50.069 --> 00:00:50.079 align:start position:0% sampling and also uh the client themes 00:00:50.079 --> 00:00:52.790 align:start position:0% sampling and also uh the client themes okay<00:00:50.640> so<00:00:50.879> I<00:00:50.960> think<00:00:51.920> you<00:00:52.039> are<00:00:52.199> all<00:00:52.399> familiar 00:00:52.790 --> 00:00:52.800 align:start position:0% okay so I think you are all familiar 00:00:52.800 --> 00:00:54.510 align:start position:0% okay so I think you are all familiar with<00:00:52.960> this<00:00:53.079> chart<00:00:53.399> you<00:00:53.480> have<00:00:53.600> seen<00:00:53.760> it<00:00:53.960> like<00:00:54.239> 10 00:00:54.510 --> 00:00:54.520 align:start position:0% with this chart you have seen it like 10 00:00:54.520 --> 00:00:57.869 align:start position:0% with this chart you have seen it like 10 times<00:00:55.000> during<00:00:55.399> this<00:00:55.680> Devcon<00:00:56.199> I<00:00:56.559> suppose<00:00:57.559> uh<00:00:57.760> we 00:00:57.869 --> 00:00:57.879 align:start position:0% times during this Devcon I suppose uh we 00:00:57.879 --> 00:01:00.270 align:start position:0% times during this Devcon I suppose uh we had<00:00:58.039> the<00:00:58.199> IP<00:00:58.760> 4844 00:01:00.270 --> 00:01:00.280 align:start position:0% had the IP 4844 00:01:00.280 --> 00:01:03.029 align:start position:0% had the IP 4844 and<00:01:00.559> the<00:01:00.719> transaction<00:01:01.199> fees<00:01:01.600> on<00:01:01.719> L2<00:01:02.280> went<00:01:02.559> down 00:01:03.029 --> 00:01:03.039 align:start position:0% and the transaction fees on L2 went down 00:01:03.039 --> 00:01:05.189 align:start position:0% and the transaction fees on L2 went down right<00:01:03.760> and<00:01:03.879> on<00:01:04.000> the<00:01:04.159> right<00:01:04.320> side<00:01:04.519> we<00:01:04.680> so<00:01:04.960> see 00:01:05.189 --> 00:01:05.199 align:start position:0% right and on the right side we so see 00:01:05.199 --> 00:01:09.109 align:start position:0% right and on the right side we so see those<00:01:05.799> little<00:01:06.119> little<00:01:06.680> ones<00:01:07.680> uh<00:01:08.640> that's<00:01:08.920> very 00:01:09.109 --> 00:01:09.119 align:start position:0% those little little ones uh that's very 00:01:09.119 --> 00:01:12.390 align:start position:0% those little little ones uh that's very good<00:01:09.799> that's<00:01:10.000> very<00:01:10.200> nice<00:01:10.400> of<00:01:10.880> uh 00:01:12.390 --> 00:01:12.400 align:start position:0% good that's very nice of uh 00:01:12.400 --> 00:01:15.870 align:start position:0% good that's very nice of uh 4844<00:01:13.400> but<00:01:13.520> I<00:01:13.640> hear<00:01:14.200> that<00:01:14.360> we<00:01:14.479> have<00:01:14.600> a<00:01:14.880> problem 00:01:15.870 --> 00:01:15.880 align:start position:0% 4844 but I hear that we have a problem 00:01:15.880 --> 00:01:18.070 align:start position:0% 4844 but I hear that we have a problem uh<00:01:16.439> and<00:01:16.960> uh<00:01:17.119> yeah<00:01:17.280> to<00:01:17.400> see<00:01:17.560> that<00:01:17.759> problem<00:01:18.000> I 00:01:18.070 --> 00:01:18.080 align:start position:0% uh and uh yeah to see that problem I 00:01:18.080 --> 00:01:20.630 align:start position:0% uh and uh yeah to see that problem I have<00:01:18.200> to<00:01:18.280> zoom<00:01:18.520> in<00:01:18.840> sorry<00:01:19.840> so<00:01:20.000> if<00:01:20.119> we<00:01:20.240> zoom<00:01:20.479> in 00:01:20.630 --> 00:01:20.640 align:start position:0% have to zoom in sorry so if we zoom in 00:01:20.640 --> 00:01:24.590 align:start position:0% have to zoom in sorry so if we zoom in we<00:01:20.799> see<00:01:21.040> this<00:01:21.280> problem<00:01:22.200> uh<00:01:23.040> so<00:01:24.040> there<00:01:24.159> is<00:01:24.280> a 00:01:24.590 --> 00:01:24.600 align:start position:0% we see this problem uh so there is a 00:01:24.600 --> 00:01:27.230 align:start position:0% we see this problem uh so there is a slight<00:01:24.960> increase<00:01:25.680> in<00:01:25.920> R2<00:01:26.360> transaction<00:01:26.759> fees 00:01:27.230 --> 00:01:27.240 align:start position:0% slight increase in R2 transaction fees 00:01:27.240 --> 00:01:29.270 align:start position:0% slight increase in R2 transaction fees and<00:01:27.400> actually<00:01:27.720> there<00:01:27.840> is<00:01:27.920> a<00:01:28.119> problem<00:01:28.759> uh<00:01:28.880> A2 00:01:29.270 --> 00:01:29.280 align:start position:0% and actually there is a problem uh A2 00:01:29.280 --> 00:01:32.389 align:start position:0% and actually there is a problem uh A2 transaction<00:01:29.640> fees<00:01:29.920> these<00:01:30.119> are<00:01:30.680> uh<00:01:30.840> driven<00:01:31.399> by 00:01:32.389 --> 00:01:32.399 align:start position:0% transaction fees these are uh driven by 00:01:32.399 --> 00:01:35.870 align:start position:0% transaction fees these are uh driven by uh<00:01:32.799> glob<00:01:33.280> Space<00:01:33.960> by<00:01:34.200> data<00:01:34.479> ver<00:01:34.799> space<00:01:35.680> and 00:01:35.870 --> 00:01:35.880 align:start position:0% uh glob Space by data ver space and 00:01:35.880 --> 00:01:38.670 align:start position:0% uh glob Space by data ver space and that's<00:01:36.479> running<00:01:36.880> out<00:01:37.280> it<00:01:37.399> is<00:01:37.920> problem<00:01:38.320> and<00:01:38.479> if 00:01:38.670 --> 00:01:38.680 align:start position:0% that's running out it is problem and if 00:01:38.680 --> 00:01:41.469 align:start position:0% that's running out it is problem and if that<00:01:38.880> happens<00:01:39.399> prices<00:01:39.759> can<00:01:39.960> rise<00:01:40.360> fast<00:01:41.360> there 00:01:41.469 --> 00:01:41.479 align:start position:0% that happens prices can rise fast there 00:01:41.479 --> 00:01:43.510 align:start position:0% that happens prices can rise fast there are<00:01:41.640> other<00:01:41.880> datability<00:01:42.320> Solutions<00:01:43.280> uh<00:01:43.360> in 00:01:43.510 --> 00:01:43.520 align:start position:0% are other datability Solutions uh in 00:01:43.520 --> 00:01:46.149 align:start position:0% are other datability Solutions uh in codex<00:01:43.840> we<00:01:43.920> are<00:01:44.040> also<00:01:44.280> building<00:01:44.640> one<00:01:45.600> uh<00:01:45.960> but 00:01:46.149 --> 00:01:46.159 align:start position:0% codex we are also building one uh but 00:01:46.159 --> 00:01:48.990 align:start position:0% codex we are also building one uh but here<00:01:46.479> I<00:01:46.560> am<00:01:46.759> to<00:01:47.040> speak<00:01:47.280> of<00:01:47.520> the<00:01:48.439> ethereum 00:01:48.990 --> 00:01:49.000 align:start position:0% here I am to speak of the ethereum 00:01:49.000 --> 00:01:50.870 align:start position:0% here I am to speak of the ethereum datail<00:01:49.600> solution<00:01:49.960> so<00:01:50.119> we<00:01:50.200> should<00:01:50.399> scale<00:01:50.719> that 00:01:50.870 --> 00:01:50.880 align:start position:0% datail solution so we should scale that 00:01:50.880 --> 00:01:52.630 align:start position:0% datail solution so we should scale that ethereum<00:01:51.240> data<00:01:51.439> ability 00:01:52.630 --> 00:01:52.640 align:start position:0% ethereum data ability 00:01:52.640 --> 00:01:56.429 align:start position:0% ethereum data ability solution<00:01:53.640> so<00:01:54.399> uh<00:01:55.079> yeah<00:01:55.520> let's<00:01:55.840> look<00:01:56.039> a<00:01:56.200> little 00:01:56.429 --> 00:01:56.439 align:start position:0% solution so uh yeah let's look a little 00:01:56.439 --> 00:01:58.270 align:start position:0% solution so uh yeah let's look a little bit<00:01:56.960> behind<00:01:57.280> these 00:01:58.270 --> 00:01:58.280 align:start position:0% bit behind these 00:01:58.280 --> 00:02:00.950 align:start position:0% bit behind these numbers<00:01:59.280> what<00:01:59.399> you<00:01:59.520> see<00:01:59.719> here<00:01:59.960> here<00:02:00.479> uh<00:02:00.719> maybe 00:02:00.950 --> 00:02:00.960 align:start position:0% numbers what you see here here uh maybe 00:02:00.960 --> 00:02:03.230 align:start position:0% numbers what you see here here uh maybe you<00:02:01.039> have<00:02:01.159> already<00:02:01.399> seen<00:02:01.960> this<00:02:02.079> one<00:02:02.280> as<00:02:02.399> well 00:02:03.230 --> 00:02:03.240 align:start position:0% you have already seen this one as well 00:02:03.240 --> 00:02:06.190 align:start position:0% you have already seen this one as well this<00:02:03.360> is<00:02:03.520> the<00:02:03.719> daily<00:02:04.039> average<00:02:04.439> size<00:02:04.759> of<00:02:05.200> blocks 00:02:06.190 --> 00:02:06.200 align:start position:0% this is the daily average size of blocks 00:02:06.200 --> 00:02:08.910 align:start position:0% this is the daily average size of blocks uh<00:02:06.399> on<00:02:06.600> the<00:02:06.880> network<00:02:07.880> and<00:02:08.039> you<00:02:08.160> see<00:02:08.479> that<00:02:08.800> it 00:02:08.910 --> 00:02:08.920 align:start position:0% uh on the network and you see that it 00:02:08.920 --> 00:02:11.110 align:start position:0% uh on the network and you see that it was<00:02:09.119> rising<00:02:09.720> and<00:02:09.920> then<00:02:10.360> uh<00:02:10.479> after<00:02:10.679> the<00:02:10.800> merge 00:02:11.110 --> 00:02:11.120 align:start position:0% was rising and then uh after the merge 00:02:11.120 --> 00:02:15.110 align:start position:0% was rising and then uh after the merge it<00:02:11.319> started<00:02:11.640> to<00:02:11.800> rise<00:02:12.560> and<00:02:12.760> then<00:02:13.599> uh<00:02:14.040> with 00:02:15.110 --> 00:02:15.120 align:start position:0% it started to rise and then uh with 00:02:15.120 --> 00:02:17.750 align:start position:0% it started to rise and then uh with 4844<00:02:16.120> it<00:02:16.599> uh 00:02:17.750 --> 00:02:17.760 align:start position:0% 4844 it uh 00:02:17.760 --> 00:02:21.190 align:start position:0% 4844 it uh reduced<00:02:18.760> so<00:02:19.120> this<00:02:19.280> looks<00:02:19.599> fine 00:02:21.190 --> 00:02:21.200 align:start position:0% reduced so this looks fine 00:02:21.200 --> 00:02:25.150 align:start position:0% reduced so this looks fine right<00:02:22.280> now<00:02:23.280> you<00:02:23.400> see<00:02:23.640> this<00:02:23.879> less<00:02:24.080> often<00:02:25.000> uh 00:02:25.150 --> 00:02:25.160 align:start position:0% right now you see this less often uh 00:02:25.160 --> 00:02:27.190 align:start position:0% right now you see this less often uh this<00:02:25.239> is<00:02:25.360> the<00:02:25.560> problem<00:02:26.319> so<00:02:26.560> this<00:02:26.680> is<00:02:26.840> what<00:02:27.000> our 00:02:27.190 --> 00:02:27.200 align:start position:0% this is the problem so this is what our 00:02:27.200 --> 00:02:30.270 align:start position:0% this is the problem so this is what our aerators<00:02:28.000> are<00:02:28.160> seeing<00:02:28.800> this<00:02:28.920> is<00:02:29.040> the<00:02:29.200> blobs<00:02:30.160> uh 00:02:30.270 --> 00:02:30.280 align:start position:0% aerators are seeing this is the blobs uh 00:02:30.280 --> 00:02:32.390 align:start position:0% aerators are seeing this is the blobs uh so<00:02:30.480> this<00:02:30.599> is<00:02:30.720> the<00:02:30.840> blocks<00:02:31.200> and<00:02:31.400> the<00:02:31.480> blocks 00:02:32.390 --> 00:02:32.400 align:start position:0% so this is the blocks and the blocks 00:02:32.400 --> 00:02:35.430 align:start position:0% so this is the blocks and the blocks cumulative<00:02:32.920> plot<00:02:33.720> uh<00:02:34.040> together<00:02:35.040> so<00:02:35.239> this<00:02:35.360> is 00:02:35.430 --> 00:02:35.440 align:start position:0% cumulative plot uh together so this is 00:02:35.440 --> 00:02:37.470 align:start position:0% cumulative plot uh together so this is the<00:02:35.599> data<00:02:35.840> amount<00:02:36.080> that<00:02:36.200> they<00:02:36.319> are<00:02:36.480> seeing<00:02:37.319> and 00:02:37.470 --> 00:02:37.480 align:start position:0% the data amount that they are seeing and 00:02:37.480 --> 00:02:40.229 align:start position:0% the data amount that they are seeing and now<00:02:37.640> we<00:02:37.760> can<00:02:38.040> start<00:02:38.480> worrying<00:02:39.120> right<00:02:39.760> uh<00:02:40.120> there 00:02:40.229 --> 00:02:40.239 align:start position:0% now we can start worrying right uh there 00:02:40.239 --> 00:02:44.030 align:start position:0% now we can start worrying right uh there is<00:02:40.360> more<00:02:40.599> data<00:02:40.800> to<00:02:41.360> handle<00:02:42.720> but<00:02:43.720> we<00:02:43.840> are 00:02:44.030 --> 00:02:44.040 align:start position:0% is more data to handle but we are 00:02:44.040 --> 00:02:45.869 align:start position:0% is more data to handle but we are scientists<00:02:44.879> we<00:02:45.000> can<00:02:45.120> look<00:02:45.280> at<00:02:45.400> this<00:02:45.560> different 00:02:45.869 --> 00:02:45.879 align:start position:0% scientists we can look at this different 00:02:45.879 --> 00:02:48.910 align:start position:0% scientists we can look at this different way<00:02:46.480> so<00:02:46.720> let's<00:02:46.959> see<00:02:47.159> it<00:02:47.239> on<00:02:47.360> a<00:02:47.480> log<00:02:47.720> scale<00:02:48.720> and 00:02:48.910 --> 00:02:48.920 align:start position:0% way so let's see it on a log scale and 00:02:48.920 --> 00:02:51.790 align:start position:0% way so let's see it on a log scale and then<00:02:49.879> it's<00:02:50.040> not<00:02:50.280> that<00:02:50.440> bad<00:02:50.720> actually<00:02:51.599> like 00:02:51.790 --> 00:02:51.800 align:start position:0% then it's not that bad actually like 00:02:51.800 --> 00:02:53.630 align:start position:0% then it's not that bad actually like it's<00:02:52.000> like<00:02:52.159> just<00:02:52.280> like<00:02:52.440> Mo<00:02:52.760> slow<00:02:53.440> it's 00:02:53.630 --> 00:02:53.640 align:start position:0% it's like just like Mo slow it's 00:02:53.640 --> 00:02:56.430 align:start position:0% it's like just like Mo slow it's actually<00:02:54.080> a<00:02:54.640> different<00:02:55.000> exponent<00:02:55.959> uh<00:02:56.120> but<00:02:56.319> we 00:02:56.430 --> 00:02:56.440 align:start position:0% actually a different exponent uh but we 00:02:56.440 --> 00:02:59.229 align:start position:0% actually a different exponent uh but we are<00:02:56.599> better<00:02:56.879> than<00:02:57.000> those<00:02:57.200> CPU<00:02:57.640> guys<00:02:57.959> so<00:02:58.879> uh<00:02:59.080> why 00:02:59.229 --> 00:02:59.239 align:start position:0% are better than those CPU guys so uh why 00:02:59.239 --> 00:03:01.229 align:start position:0% are better than those CPU guys so uh why would<00:02:59.440> worry 00:03:01.229 --> 00:03:01.239 align:start position:0% would worry 00:03:01.239 --> 00:03:02.949 align:start position:0% would worry okay<00:03:01.400> we<00:03:01.560> just<00:03:01.800> have<00:03:01.920> to<00:03:02.080> do<00:03:02.319> that<00:03:02.640> little 00:03:02.949 --> 00:03:02.959 align:start position:0% okay we just have to do that little 00:03:02.959 --> 00:03:06.229 align:start position:0% okay we just have to do that little technology<00:03:03.360> Evolution<00:03:03.920> which<00:03:04.519> keeps<00:03:04.840> this 00:03:06.229 --> 00:03:06.239 align:start position:0% technology Evolution which keeps this 00:03:06.239 --> 00:03:08.470 align:start position:0% technology Evolution which keeps this running<00:03:07.239> and 00:03:08.470 --> 00:03:08.480 align:start position:0% running and 00:03:08.480 --> 00:03:12.670 align:start position:0% running and then<00:03:09.480> we<00:03:09.599> have<00:03:09.720> a<00:03:09.840> solution<00:03:10.720> right<00:03:11.720> we<00:03:11.840> can<00:03:12.360> do 00:03:12.670 --> 00:03:12.680 align:start position:0% then we have a solution right we can do 00:03:12.680 --> 00:03:15.710 align:start position:0% then we have a solution right we can do that<00:03:12.840> line<00:03:13.280> we<00:03:13.400> just<00:03:13.519> need<00:03:13.680> more<00:03:13.920> b<00:03:14.319> space<00:03:15.319> and 00:03:15.710 --> 00:03:15.720 align:start position:0% that line we just need more b space and 00:03:15.720 --> 00:03:20.030 align:start position:0% that line we just need more b space and uh<00:03:16.560> and<00:03:16.840> that's<00:03:17.000> a<00:03:17.640> plan<00:03:18.640> and<00:03:18.799> here's<00:03:19.000> a<00:03:19.159> plan 00:03:20.030 --> 00:03:20.040 align:start position:0% uh and that's a plan and here's a plan 00:03:20.040 --> 00:03:22.830 align:start position:0% uh and that's a plan and here's a plan we<00:03:20.159> need<00:03:20.360> p<00:03:20.640> d<00:03:21.040> and<00:03:21.120> then<00:03:21.280> four<00:03:21.599> D<00:03:22.480> and<00:03:22.599> we<00:03:22.720> just 00:03:22.830 --> 00:03:22.840 align:start position:0% we need p d and then four D and we just 00:03:22.840 --> 00:03:24.589 align:start position:0% we need p d and then four D and we just have<00:03:22.959> to<00:03:23.040> be<00:03:23.200> a<00:03:23.280> bit<00:03:23.440> lousy<00:03:23.840> about<00:03:24.080> the<00:03:24.200> scale 00:03:24.589 --> 00:03:24.599 align:start position:0% have to be a bit lousy about the scale 00:03:24.599 --> 00:03:25.910 align:start position:0% have to be a bit lousy about the scale so<00:03:24.760> it's<00:03:24.840> an<00:03:24.959> unknown<00:03:25.239> scale<00:03:25.480> here<00:03:25.680> unkown 00:03:25.910 --> 00:03:25.920 align:start position:0% so it's an unknown scale here unkown 00:03:25.920 --> 00:03:28.309 align:start position:0% so it's an unknown scale here unkown scale<00:03:26.280> there<00:03:26.799> and<00:03:27.000> then<00:03:27.640> uh<00:03:27.760> we<00:03:27.840> saw<00:03:28.159> the 00:03:28.309 --> 00:03:28.319 align:start position:0% scale there and then uh we saw the 00:03:28.319 --> 00:03:30.949 align:start position:0% scale there and then uh we saw the problem<00:03:28.959> what<00:03:29.080> we<00:03:29.200> want<00:03:29.360> is<00:03:29.480> more<00:03:30.000> space<00:03:30.760> and 00:03:30.949 --> 00:03:30.959 align:start position:0% problem what we want is more space and 00:03:30.959 --> 00:03:33.630 align:start position:0% problem what we want is more space and what<00:03:31.080> we<00:03:31.200> want<00:03:31.400> is<00:03:31.560> less<00:03:31.840> no<00:03:32.159> traffic<00:03:32.480> for<00:03:32.680> our 00:03:33.630 --> 00:03:33.640 align:start position:0% what we want is less no traffic for our 00:03:33.640 --> 00:03:36.070 align:start position:0% what we want is less no traffic for our operators<00:03:34.640> uh<00:03:35.120> yeah<00:03:35.360> we<00:03:35.519> just<00:03:35.640> have<00:03:35.760> to<00:03:35.879> work 00:03:36.070 --> 00:03:36.080 align:start position:0% operators uh yeah we just have to work 00:03:36.080 --> 00:03:38.030 align:start position:0% operators uh yeah we just have to work out<00:03:36.319> these<00:03:36.480> little<00:03:36.760> networking 00:03:38.030 --> 00:03:38.040 align:start position:0% out these little networking 00:03:38.040 --> 00:03:40.990 align:start position:0% out these little networking details<00:03:39.040> so<00:03:39.720> uh<00:03:39.879> let's<00:03:40.080> see<00:03:40.400> those<00:03:40.720> little 00:03:40.990 --> 00:03:41.000 align:start position:0% details so uh let's see those little 00:03:41.000 --> 00:03:42.470 align:start position:0% details so uh let's see those little networking<00:03:41.400> details<00:03:41.760> that<00:03:41.879> we<00:03:41.959> have<00:03:42.080> to<00:03:42.200> work 00:03:42.470 --> 00:03:42.480 align:start position:0% networking details that we have to work 00:03:42.480 --> 00:03:45.789 align:start position:0% networking details that we have to work out<00:03:43.400> uh<00:03:43.519> but<00:03:43.680> first<00:03:43.920> let<00:03:44.040> me<00:03:44.720> uh<00:03:45.200> have<00:03:45.319> a<00:03:45.519> quick 00:03:45.789 --> 00:03:45.799 align:start position:0% out uh but first let me uh have a quick 00:03:45.799 --> 00:03:47.270 align:start position:0% out uh but first let me uh have a quick the<00:03:46.000> tool 00:03:47.270 --> 00:03:47.280 align:start position:0% the tool 00:03:47.280 --> 00:03:50.390 align:start position:0% the tool networking<00:03:48.280> uh<00:03:48.439> but<00:03:48.640> this<00:03:48.799> is<00:03:49.799> I<00:03:49.920> was<00:03:50.080> speaking 00:03:50.390 --> 00:03:50.400 align:start position:0% networking uh but this is I was speaking 00:03:50.400 --> 00:03:54.110 align:start position:0% networking uh but this is I was speaking of<00:03:50.599> average<00:03:50.920> book<00:03:51.280> size<00:03:51.599> till<00:03:52.120> now<00:03:53.120> uh<00:03:53.920> but 00:03:54.110 --> 00:03:54.120 align:start position:0% of average book size till now uh but 00:03:54.120 --> 00:03:56.550 align:start position:0% of average book size till now uh but average<00:03:54.480> is<00:03:54.879> is<00:03:55.000> a<00:03:55.200> was<00:03:55.319> a<00:03:55.400> daily<00:03:55.680> average<00:03:56.400> and 00:03:56.550 --> 00:03:56.560 align:start position:0% average is is a was a daily average and 00:03:56.560 --> 00:03:58.309 align:start position:0% average is is a was a daily average and in<00:03:56.680> the<00:03:56.840> day<00:03:57.000> many<00:03:57.239> things<00:03:57.640> things<00:03:57.920> happen 00:03:58.309 --> 00:03:58.319 align:start position:0% in the day many things things happen 00:03:58.319 --> 00:03:59.949 align:start position:0% in the day many things things happen right<00:03:58.480> every<00:03:58.720> 12<00:03:58.959> seconds<00:03:59.239> something<00:03:59.799> is 00:03:59.949 --> 00:03:59.959 align:start position:0% right every 12 seconds something is 00:03:59.959 --> 00:04:01.869 align:start position:0% right every 12 seconds something is happening<00:04:00.720> so<00:04:00.920> what<00:04:01.040> you<00:04:01.120> see<00:04:01.400> here<00:04:01.560> is<00:04:01.720> the 00:04:01.869 --> 00:04:01.879 align:start position:0% happening so what you see here is the 00:04:01.879 --> 00:04:03.869 align:start position:0% happening so what you see here is the tail<00:04:02.200> distribution<00:04:02.680> of<00:04:02.799> block<00:04:03.120> size<00:04:03.799> uh 00:04:03.869 --> 00:04:03.879 align:start position:0% tail distribution of block size uh 00:04:03.879 --> 00:04:06.229 align:start position:0% tail distribution of block size uh during<00:04:04.159> a<00:04:04.280> long<00:04:04.560> period<00:04:05.439> you<00:04:05.599> don't<00:04:05.799> even<00:04:06.000> see 00:04:06.229 --> 00:04:06.239 align:start position:0% during a long period you don't even see 00:04:06.239 --> 00:04:07.750 align:start position:0% during a long period you don't even see the<00:04:06.360> small<00:04:06.599> blocks<00:04:06.920> you<00:04:07.040> just<00:04:07.159> see<00:04:07.360> the<00:04:07.439> large 00:04:07.750 --> 00:04:07.760 align:start position:0% the small blocks you just see the large 00:04:07.760 --> 00:04:11.270 align:start position:0% the small blocks you just see the large ones<00:04:08.599> uh<00:04:08.720> and<00:04:08.879> this<00:04:09.000> was<00:04:09.319> before 00:04:11.270 --> 00:04:11.280 align:start position:0% ones uh and this was before 00:04:11.280 --> 00:04:13.589 align:start position:0% ones uh and this was before 4844<00:04:12.280> uh<00:04:12.480> and<00:04:12.640> what<00:04:12.760> you<00:04:12.879> see<00:04:13.079> that<00:04:13.239> there<00:04:13.400> were 00:04:13.589 --> 00:04:13.599 align:start position:0% 4844 uh and what you see that there were 00:04:13.599 --> 00:04:16.069 align:start position:0% 4844 uh and what you see that there were blocks<00:04:14.599> Beyond<00:04:14.959> 2 00:04:16.069 --> 00:04:16.079 align:start position:0% blocks Beyond 2 00:04:16.079 --> 00:04:18.990 align:start position:0% blocks Beyond 2 megab<00:04:17.079> and<00:04:17.519> uh<00:04:17.840> our<00:04:18.040> notes<00:04:18.359> have<00:04:18.479> to<00:04:18.639> handle 00:04:18.990 --> 00:04:19.000 align:start position:0% megab and uh our notes have to handle 00:04:19.000 --> 00:04:21.830 align:start position:0% megab and uh our notes have to handle those<00:04:19.840> what<00:04:20.000> if<00:04:20.160> two<00:04:20.440> blocks<00:04:20.720> of<00:04:20.880> such<00:04:21.560> come 00:04:21.830 --> 00:04:21.840 align:start position:0% those what if two blocks of such come 00:04:21.840 --> 00:04:23.990 align:start position:0% those what if two blocks of such come one<00:04:22.000> after<00:04:22.240> another<00:04:22.919> and<00:04:23.040> you<00:04:23.160> have<00:04:23.280> to<00:04:23.560> handle 00:04:23.990 --> 00:04:24.000 align:start position:0% one after another and you have to handle 00:04:24.000 --> 00:04:25.830 align:start position:0% one after another and you have to handle that<00:04:24.280> so<00:04:24.639> you<00:04:25.000> our<00:04:25.199> technology<00:04:25.600> have<00:04:25.720> to 00:04:25.830 --> 00:04:25.840 align:start position:0% that so you our technology have to 00:04:25.840 --> 00:04:27.990 align:start position:0% that so you our technology have to handle<00:04:26.160> these<00:04:26.360> things<00:04:26.639> as<00:04:26.800> well<00:04:27.560> and<00:04:27.680> we<00:04:27.800> were 00:04:27.990 --> 00:04:28.000 align:start position:0% handle these things as well and we were 00:04:28.000 --> 00:04:30.550 align:start position:0% handle these things as well and we were measuring<00:04:28.919> uh<00:04:29.080> whether<00:04:29.280> you<00:04:29.360> can<00:04:29.479> handle<00:04:29.960> that 00:04:30.550 --> 00:04:30.560 align:start position:0% measuring uh whether you can handle that 00:04:30.560 --> 00:04:32.310 align:start position:0% measuring uh whether you can handle that and<00:04:30.680> the<00:04:30.800> good<00:04:30.960> news<00:04:31.199> is<00:04:31.400> that<00:04:31.919> uh<00:04:32.039> you<00:04:32.160> can 00:04:32.310 --> 00:04:32.320 align:start position:0% and the good news is that uh you can 00:04:32.320 --> 00:04:33.830 align:start position:0% and the good news is that uh you can handle<00:04:32.639> that<00:04:32.800> so<00:04:32.960> the<00:04:33.080> network<00:04:33.520> was<00:04:33.720> was 00:04:33.830 --> 00:04:33.840 align:start position:0% handle that so the network was was 00:04:33.840 --> 00:04:35.870 align:start position:0% handle that so the network was was running<00:04:34.160> and<00:04:34.400> live<00:04:34.919> and<00:04:35.080> what<00:04:35.199> you<00:04:35.320> see<00:04:35.639> here 00:04:35.870 --> 00:04:35.880 align:start position:0% running and live and what you see here 00:04:35.880 --> 00:04:39.110 align:start position:0% running and live and what you see here is<00:04:36.520> uh<00:04:36.919> for<00:04:37.160> different<00:04:37.400> block<00:04:37.960> sizes<00:04:38.960> these 00:04:39.110 --> 00:04:39.120 align:start position:0% is uh for different block sizes these 00:04:39.120 --> 00:04:41.550 align:start position:0% is uh for different block sizes these are<00:04:39.280> the<00:04:39.360> bins<00:04:40.000> Smalls<00:04:40.479> up<00:04:40.600> to<00:04:40.759> 32<00:04:41.160> kiloby 00:04:41.550 --> 00:04:41.560 align:start position:0% are the bins Smalls up to 32 kiloby 00:04:41.560 --> 00:04:44.550 align:start position:0% are the bins Smalls up to 32 kiloby blocks<00:04:42.039> and<00:04:42.199> then<00:04:42.960> between<00:04:43.320> one<00:04:44.039> megabyte<00:04:44.440> and 00:04:44.550 --> 00:04:44.560 align:start position:0% blocks and then between one megabyte and 00:04:44.560 --> 00:04:48.629 align:start position:0% blocks and then between one megabyte and 2<00:04:45.080> megabyte<00:04:46.080> how<00:04:46.240> much<00:04:46.560> time<00:04:47.039> nodes<00:04:47.479> need<00:04:48.440> to 00:04:48.629 --> 00:04:48.639 align:start position:0% 2 megabyte how much time nodes need to 00:04:48.639 --> 00:04:50.990 align:start position:0% 2 megabyte how much time nodes need to get<00:04:48.800> the<00:04:49.120> blocks<00:04:50.120> and<00:04:50.360> the<00:04:50.479> bigger<00:04:50.720> the<00:04:50.800> block 00:04:50.990 --> 00:04:51.000 align:start position:0% get the blocks and the bigger the block 00:04:51.000 --> 00:04:52.670 align:start position:0% get the blocks and the bigger the block the<00:04:51.080> more<00:04:51.360> time<00:04:51.560> is<00:04:51.720> needed<00:04:52.280> this<00:04:52.360> is<00:04:52.479> a 00:04:52.670 --> 00:04:52.680 align:start position:0% the more time is needed this is a 00:04:52.680 --> 00:04:55.390 align:start position:0% the more time is needed this is a distribution<00:04:53.440> so<00:04:54.080> the<00:04:54.680> notes<00:04:55.000> which<00:04:55.120> are 00:04:55.390 --> 00:04:55.400 align:start position:0% distribution so the notes which are 00:04:55.400 --> 00:04:56.550 align:start position:0% distribution so the notes which are receiving<00:04:55.560> it<00:04:55.720> only<00:04:56.000> here<00:04:56.199> and<00:04:56.320> there<00:04:56.440> are 00:04:56.550 --> 00:04:56.560 align:start position:0% receiving it only here and there are 00:04:56.560 --> 00:04:58.430 align:start position:0% receiving it only here and there are many<00:04:56.720> notes<00:04:56.960> which<00:04:57.080> are<00:04:57.360> receiving<00:04:57.560> it<00:04:57.759> before 00:04:58.430 --> 00:04:58.440 align:start position:0% many notes which are receiving it before 00:04:58.440 --> 00:05:00.029 align:start position:0% many notes which are receiving it before everyone<00:04:58.800> almost<00:04:59.080> everyone<00:04:59.320> is<00:04:59.400> receiving<00:04:59.919> it 00:05:00.029 --> 00:05:00.039 align:start position:0% everyone almost everyone is receiving it 00:05:00.039 --> 00:05:04.110 align:start position:0% everyone almost everyone is receiving it before<00:05:00.440> 4<00:05:00.840> seconds<00:05:01.680> so<00:05:01.919> things<00:05:02.120> are<00:05:02.759> fine<00:05:03.759> uh 00:05:04.110 --> 00:05:04.120 align:start position:0% before 4 seconds so things are fine uh 00:05:04.120 --> 00:05:07.430 align:start position:0% before 4 seconds so things are fine uh but<00:05:04.680> clearly<00:05:05.680> doesn't<00:05:06.000> scale<00:05:06.479> very<00:05:06.680> well<00:05:07.320> as 00:05:07.430 --> 00:05:07.440 align:start position:0% but clearly doesn't scale very well as 00:05:07.440 --> 00:05:09.350 align:start position:0% but clearly doesn't scale very well as you<00:05:07.680> seen<00:05:08.440> if<00:05:08.600> we<00:05:08.720> want<00:05:08.840> to<00:05:08.960> increase<00:05:09.280> the 00:05:09.350 --> 00:05:09.360 align:start position:0% you seen if we want to increase the 00:05:09.360 --> 00:05:11.629 align:start position:0% you seen if we want to increase the block<00:05:09.639> size<00:05:09.880> then<00:05:09.960> it<00:05:10.080> would<00:05:10.479> go<00:05:10.639> to<00:05:10.759> the 00:05:11.629 --> 00:05:11.639 align:start position:0% block size then it would go to the 00:05:11.639 --> 00:05:16.670 align:start position:0% block size then it would go to the right<00:05:12.960> so<00:05:13.960> we<00:05:14.160> arrived<00:05:14.440> to<00:05:14.560> our<00:05:14.759> Point<00:05:15.280> how<00:05:15.440> to 00:05:16.670 --> 00:05:16.680 align:start position:0% right so we arrived to our Point how to 00:05:16.680 --> 00:05:20.430 align:start position:0% right so we arrived to our Point how to scale<00:05:17.680> layer<00:05:18.080> one<00:05:18.720> from<00:05:18.880> the<00:05:19.039> networking<00:05:19.639> side 00:05:20.430 --> 00:05:20.440 align:start position:0% scale layer one from the networking side 00:05:20.440 --> 00:05:23.189 align:start position:0% scale layer one from the networking side and<00:05:20.560> we<00:05:20.680> can<00:05:20.800> do<00:05:21.000> different<00:05:21.840> things<00:05:22.840> uh<00:05:23.000> first 00:05:23.189 --> 00:05:23.199 align:start position:0% and we can do different things uh first 00:05:23.199 --> 00:05:26.070 align:start position:0% and we can do different things uh first of<00:05:23.319> all<00:05:23.479> we<00:05:23.560> can<00:05:23.800> change<00:05:24.800> the<00:05:24.960> slot<00:05:25.400> time<00:05:25.960> the 00:05:26.070 --> 00:05:26.080 align:start position:0% of all we can change the slot time the 00:05:26.080 --> 00:05:28.230 align:start position:0% of all we can change the slot time the slot<00:05:26.440> timing<00:05:26.800> window<00:05:27.240> and<00:05:27.440> the<00:05:27.680> internal 00:05:28.230 --> 00:05:28.240 align:start position:0% slot timing window and the internal 00:05:28.240 --> 00:05:30.870 align:start position:0% slot timing window and the internal timers<00:05:29.240> uh<00:05:29.360> we<00:05:29.479> can<00:05:29.720> change<00:05:30.000> resource 00:05:30.870 --> 00:05:30.880 align:start position:0% timers uh we can change resource 00:05:30.880 --> 00:05:33.550 align:start position:0% timers uh we can change resource requirements<00:05:31.880> uh<00:05:32.199> it's<00:05:32.319> a<00:05:32.479> good<00:05:32.680> discussion 00:05:33.550 --> 00:05:33.560 align:start position:0% requirements uh it's a good discussion 00:05:33.560 --> 00:05:35.629 align:start position:0% requirements uh it's a good discussion uh<00:05:33.680> it's<00:05:33.759> a<00:05:33.880> bit<00:05:34.360> controversial<00:05:35.360> we<00:05:35.479> have 00:05:35.629 --> 00:05:35.639 align:start position:0% uh it's a bit controversial we have 00:05:35.639 --> 00:05:37.670 align:start position:0% uh it's a bit controversial we have small<00:05:36.000> gains<00:05:36.280> we<00:05:36.400> have<00:05:36.479> lot<00:05:36.680> to<00:05:36.800> lose<00:05:37.319> so<00:05:37.479> let 00:05:37.670 --> 00:05:37.680 align:start position:0% small gains we have lot to lose so let 00:05:37.680 --> 00:05:39.469 align:start position:0% small gains we have lot to lose so let me<00:05:37.800> not<00:05:37.919> go<00:05:38.080> into<00:05:38.319> that<00:05:38.479> one<00:05:38.919> then<00:05:39.120> we<00:05:39.240> can 00:05:39.469 --> 00:05:39.479 align:start position:0% me not go into that one then we can 00:05:39.479 --> 00:05:42.390 align:start position:0% me not go into that one then we can change<00:05:40.280> uh<00:05:40.360> the<00:05:40.479> gossip<00:05:40.800> sub<00:05:41.039> the<00:05:41.319> protocol<00:05:42.319> uh 00:05:42.390 --> 00:05:42.400 align:start position:0% change uh the gossip sub the protocol uh 00:05:42.400 --> 00:05:44.430 align:start position:0% change uh the gossip sub the protocol uh the<00:05:42.520> networking<00:05:42.960> protocol<00:05:43.840> we<00:05:43.960> can<00:05:44.120> do 00:05:44.430 --> 00:05:44.440 align:start position:0% the networking protocol we can do 00:05:44.440 --> 00:05:45.909 align:start position:0% the networking protocol we can do improvements<00:05:44.919> on<00:05:45.039> Gossip<00:05:45.360> sub<00:05:45.520> for<00:05:45.680> large 00:05:45.909 --> 00:05:45.919 align:start position:0% improvements on Gossip sub for large 00:05:45.919 --> 00:05:48.670 align:start position:0% improvements on Gossip sub for large messages<00:05:46.520> and<00:05:46.639> this<00:05:46.759> is<00:05:46.960> in<00:05:47.280> making<00:05:48.199> uh<00:05:48.319> it's 00:05:48.670 --> 00:05:48.680 align:start position:0% messages and this is in making uh it's 00:05:48.680 --> 00:05:51.189 align:start position:0% messages and this is in making uh it's important<00:05:49.680> but<00:05:49.800> this<00:05:49.919> is<00:05:50.039> not<00:05:50.160> my<00:05:50.319> talk<00:05:50.560> today 00:05:51.189 --> 00:05:51.199 align:start position:0% important but this is not my talk today 00:05:51.199 --> 00:05:52.590 align:start position:0% important but this is not my talk today uh<00:05:51.319> and<00:05:51.440> it's<00:05:51.639> relatively<00:05:52.039> small<00:05:52.319> gains 00:05:52.590 --> 00:05:52.600 align:start position:0% uh and it's relatively small gains 00:05:52.600 --> 00:05:55.309 align:start position:0% uh and it's relatively small gains compared<00:05:52.919> to<00:05:53.039> what<00:05:53.160> we<00:05:53.280> need<00:05:53.680> still<00:05:54.319> important 00:05:55.309 --> 00:05:55.319 align:start position:0% compared to what we need still important 00:05:55.319 --> 00:05:57.749 align:start position:0% compared to what we need still important then<00:05:55.479> we<00:05:55.600> can<00:05:55.720> do<00:05:55.840> Shing<00:05:56.560> and<00:05:56.919> dat<00:05:57.280> data<00:05:57.600> with 00:05:57.749 --> 00:05:57.759 align:start position:0% then we can do Shing and dat data with 00:05:57.759 --> 00:06:00.110 align:start position:0% then we can do Shing and dat data with sampling<00:05:58.440> and<00:05:58.600> this<00:05:58.680> is<00:05:58.800> my<00:05:58.960> talk<00:05:59.160> today<00:05:59.919> uh 00:06:00.110 --> 00:06:00.120 align:start position:0% sampling and this is my talk today uh 00:06:00.120 --> 00:06:01.830 align:start position:0% sampling and this is my talk today uh this<00:06:00.240> is<00:06:00.400> large<00:06:00.680> gains<00:06:01.080> I 00:06:01.830 --> 00:06:01.840 align:start position:0% this is large gains I 00:06:01.840 --> 00:06:04.270 align:start position:0% this is large gains I hope<00:06:02.840> and<00:06:02.960> then<00:06:03.120> there<00:06:03.240> the<00:06:03.360> four<00:06:03.639> thing<00:06:04.160> we 00:06:04.270 --> 00:06:04.280 align:start position:0% hope and then there the four thing we 00:06:04.280 --> 00:06:06.629 align:start position:0% hope and then there the four thing we can<00:06:04.400> do<00:06:04.560> distributed<00:06:05.000> block<00:06:05.479> building<00:06:06.479> uh 00:06:06.629 --> 00:06:06.639 align:start position:0% can do distributed block building uh 00:06:06.639 --> 00:06:08.230 align:start position:0% can do distributed block building uh this<00:06:06.759> is<00:06:06.919> kind<00:06:07.039> of<00:06:07.199> intertwined<00:06:07.840> with<00:06:08.000> many 00:06:08.230 --> 00:06:08.240 align:start position:0% this is kind of intertwined with many 00:06:08.240 --> 00:06:11.790 align:start position:0% this is kind of intertwined with many things<00:06:09.240> uh<00:06:09.599> but<00:06:09.960> prises<00:06:10.400> large<00:06:10.680> gains<00:06:11.639> but 00:06:11.790 --> 00:06:11.800 align:start position:0% things uh but prises large gains but 00:06:11.800 --> 00:06:13.589 align:start position:0% things uh but prises large gains but basically<00:06:12.240> that<00:06:12.360> would<00:06:12.479> mean<00:06:12.800> resyncing<00:06:13.440> the 00:06:13.589 --> 00:06:13.599 align:start position:0% basically that would mean resyncing the 00:06:13.599 --> 00:06:15.790 align:start position:0% basically that would mean resyncing the whole<00:06:13.880> data<00:06:14.120> flow<00:06:14.680> of<00:06:14.800> The<00:06:14.960> Blob<00:06:15.280> transaction 00:06:15.790 --> 00:06:15.800 align:start position:0% whole data flow of The Blob transaction 00:06:15.800 --> 00:06:18.350 align:start position:0% whole data flow of The Blob transaction from<00:06:16.120> submission<00:06:16.599> of<00:06:16.800> the<00:06:17.240> the<00:06:17.360> transaction 00:06:18.350 --> 00:06:18.360 align:start position:0% from submission of the the transaction 00:06:18.360 --> 00:06:20.189 align:start position:0% from submission of the the transaction Until<00:06:18.720> the 00:06:20.189 --> 00:06:20.199 align:start position:0% Until the 00:06:20.199 --> 00:06:23.670 align:start position:0% Until the End<00:06:21.199> okay<00:06:21.880> so<00:06:22.280> let's<00:06:22.479> focus<00:06:22.720> on<00:06:22.880> point<00:06:23.120> three 00:06:23.670 --> 00:06:23.680 align:start position:0% End okay so let's focus on point three 00:06:23.680 --> 00:06:27.350 align:start position:0% End okay so let's focus on point three the<00:06:23.759> sharding<00:06:24.240> and<00:06:24.400> data<00:06:24.880> sampling<00:06:25.240> over<00:06:25.400> the 00:06:27.350 --> 00:06:27.360 align:start position:0% the sharding and data sampling over the 00:06:27.360 --> 00:06:30.670 align:start position:0% the sharding and data sampling over the network<00:06:28.360> so<00:06:28.960> uh<00:06:29.120> data<00:06:29.639> sampling<00:06:30.400> uh<00:06:30.520> let's 00:06:30.670 --> 00:06:30.680 align:start position:0% network so uh data sampling uh let's 00:06:30.680 --> 00:06:33.110 align:start position:0% network so uh data sampling uh let's just<00:06:30.840> key<00:06:31.080> Concepts<00:06:31.919> so<00:06:32.280> you<00:06:32.400> need<00:06:32.560> to<00:06:32.759> prepare 00:06:33.110 --> 00:06:33.120 align:start position:0% just key Concepts so you need to prepare 00:06:33.120 --> 00:06:35.710 align:start position:0% just key Concepts so you need to prepare the<00:06:33.280> data<00:06:33.560> we<00:06:33.639> were<00:06:33.800> speaking<00:06:34.039> of<00:06:34.560> blobs<00:06:35.560> uh 00:06:35.710 --> 00:06:35.720 align:start position:0% the data we were speaking of blobs uh 00:06:35.720 --> 00:06:38.309 align:start position:0% the data we were speaking of blobs uh there<00:06:35.880> are<00:06:36.160> blobs<00:06:37.160> there's<00:06:37.360> a<00:06:37.479> package<00:06:37.759> of 00:06:38.309 --> 00:06:38.319 align:start position:0% there are blobs there's a package of 00:06:38.319 --> 00:06:41.670 align:start position:0% there are blobs there's a package of blobs<00:06:39.319> uh<00:06:39.560> and<00:06:39.720> then<00:06:40.120> we<00:06:40.240> need<00:06:40.400> an<00:06:40.599> encoding<00:06:41.599> we 00:06:41.670 --> 00:06:41.680 align:start position:0% blobs uh and then we need an encoding we 00:06:41.680 --> 00:06:42.830 align:start position:0% blobs uh and then we need an encoding we need<00:06:41.840> an<00:06:41.960> encoding<00:06:42.360> because<00:06:42.520> we<00:06:42.599> want<00:06:42.720> to 00:06:42.830 --> 00:06:42.840 align:start position:0% need an encoding because we want to 00:06:42.840 --> 00:06:44.550 align:start position:0% need an encoding because we want to sample<00:06:43.199> from<00:06:43.400> it<00:06:43.599> and<00:06:43.720> for<00:06:43.880> the<00:06:44.000> sampling<00:06:44.440> to 00:06:44.550 --> 00:06:44.560 align:start position:0% sample from it and for the sampling to 00:06:44.560 --> 00:06:47.390 align:start position:0% sample from it and for the sampling to be<00:06:44.919> effective<00:06:45.919> we<00:06:46.039> need<00:06:46.360> AER<00:06:46.840> coding<00:06:47.240> for 00:06:47.390 --> 00:06:47.400 align:start position:0% be effective we need AER coding for 00:06:47.400 --> 00:06:49.749 align:start position:0% be effective we need AER coding for theer<00:06:47.840> coding<00:06:48.120> we<00:06:48.240> need<00:06:48.479> segmentation<00:06:49.479> so<00:06:49.639> we 00:06:49.749 --> 00:06:49.759 align:start position:0% theer coding we need segmentation so we 00:06:49.759 --> 00:06:51.990 align:start position:0% theer coding we need segmentation so we need<00:06:49.880> to<00:06:50.039> segment<00:06:50.440> it<00:06:50.560> chop<00:06:50.800> it<00:06:50.919> to<00:06:51.120> Pieces<00:06:51.880> we 00:06:51.990 --> 00:06:52.000 align:start position:0% need to segment it chop it to Pieces we 00:06:52.000 --> 00:06:54.990 align:start position:0% need to segment it chop it to Pieces we need<00:06:52.160> to<00:06:52.360> extend<00:06:52.759> it<00:06:53.080> with<00:06:53.240> AER<00:06:53.800> coding<00:06:54.800> then 00:06:54.990 --> 00:06:55.000 align:start position:0% need to extend it with AER coding then 00:06:55.000 --> 00:06:56.950 align:start position:0% need to extend it with AER coding then we<00:06:55.120> have<00:06:55.240> to<00:06:55.440> commit<00:06:55.800> to<00:06:56.000> it<00:06:56.440> so<00:06:56.680> that<00:06:56.800> it 00:06:56.950 --> 00:06:56.960 align:start position:0% we have to commit to it so that it 00:06:56.960 --> 00:07:02.150 align:start position:0% we have to commit to it so that it cannot<00:06:57.280> be<00:06:58.080> uh<00:06:59.080> not<00:06:59.800> send<00:07:00.240> for<00:07:00.639> PES<00:07:01.160> basically 00:07:02.150 --> 00:07:02.160 align:start position:0% cannot be uh not send for PES basically 00:07:02.160 --> 00:07:04.350 align:start position:0% cannot be uh not send for PES basically and<00:07:02.319> once<00:07:02.560> we'<00:07:02.840> done<00:07:03.199> this<00:07:03.759> we<00:07:03.879> are<00:07:04.000> ready<00:07:04.199> with 00:07:04.350 --> 00:07:04.360 align:start position:0% and once we' done this we are ready with 00:07:04.360 --> 00:07:06.909 align:start position:0% and once we' done this we are ready with the<00:07:04.479> data<00:07:04.840> preparation<00:07:05.840> okay<00:07:06.479> and<00:07:06.639> here<00:07:06.759> we 00:07:06.909 --> 00:07:06.919 align:start position:0% the data preparation okay and here we 00:07:06.919 --> 00:07:09.430 align:start position:0% the data preparation okay and here we have<00:07:07.080> different<00:07:07.720> structures<00:07:08.720> uh<00:07:09.080> we<00:07:09.240> have 00:07:09.430 --> 00:07:09.440 align:start position:0% have different structures uh we have 00:07:09.440 --> 00:07:11.189 align:start position:0% have different structures uh we have what<00:07:09.560> we<00:07:09.720> call<00:07:09.919> the<00:07:10.039> onedimensional<00:07:10.520> P 00:07:11.189 --> 00:07:11.199 align:start position:0% what we call the onedimensional P 00:07:11.199 --> 00:07:14.189 align:start position:0% what we call the onedimensional P structure<00:07:12.080> where<00:07:12.240> you<00:07:12.360> have<00:07:12.599> blobs<00:07:13.599> which<00:07:13.759> are 00:07:14.189 --> 00:07:14.199 align:start position:0% structure where you have blobs which are 00:07:14.199 --> 00:07:17.350 align:start position:0% structure where you have blobs which are extended<00:07:15.199> and<00:07:15.919> through<00:07:16.199> and<00:07:16.400> committed<00:07:16.759> to<00:07:17.240> or 00:07:17.350 --> 00:07:17.360 align:start position:0% extended and through and committed to or 00:07:17.360 --> 00:07:18.790 align:start position:0% extended and through and committed to or we<00:07:17.479> have<00:07:17.560> the<00:07:17.680> two<00:07:17.879> dimensional<00:07:18.400> structure 00:07:18.790 --> 00:07:18.800 align:start position:0% we have the two dimensional structure 00:07:18.800 --> 00:07:20.550 align:start position:0% we have the two dimensional structure where<00:07:18.879> you<00:07:19.000> have<00:07:19.160> blobs<00:07:19.840> which<00:07:19.960> are<00:07:20.160> extended 00:07:20.550 --> 00:07:20.560 align:start position:0% where you have blobs which are extended 00:07:20.560 --> 00:07:23.150 align:start position:0% where you have blobs which are extended in<00:07:20.720> two<00:07:21.400> Dimension<00:07:22.400> uh<00:07:22.599> if<00:07:22.680> you<00:07:22.919> look 00:07:23.150 --> 00:07:23.160 align:start position:0% in two Dimension uh if you look 00:07:23.160 --> 00:07:24.749 align:start position:0% in two Dimension uh if you look carefully<00:07:23.639> you<00:07:23.759> see<00:07:23.960> that<00:07:24.240> actually<00:07:24.520> this<00:07:24.639> is 00:07:24.749 --> 00:07:24.759 align:start position:0% carefully you see that actually this is 00:07:24.759 --> 00:07:26.510 align:start position:0% carefully you see that actually this is also<00:07:25.000> two-<00:07:25.199> dimensional<00:07:25.800> the<00:07:25.960> difference<00:07:26.360> is 00:07:26.510 --> 00:07:26.520 align:start position:0% also two- dimensional the difference is 00:07:26.520 --> 00:07:28.589 align:start position:0% also two- dimensional the difference is that<00:07:26.680> it's<00:07:26.840> not<00:07:27.080> extended<00:07:27.639> by<00:07:27.759> an<00:07:27.960> addal<00:07:28.360> code 00:07:28.589 --> 00:07:28.599 align:start position:0% that it's not extended by an addal code 00:07:28.599 --> 00:07:32.189 align:start position:0% that it's not extended by an addal code in<00:07:28.759> this<00:07:28.960> dimension<00:07:29.520> and<00:07:29.680> that<00:07:29.840> has 00:07:32.189 --> 00:07:32.199 align:start position:0% 00:07:32.199 --> 00:07:34.710 align:start position:0% consequences<00:07:33.199> okay<00:07:33.840> and<00:07:34.039> then<00:07:34.280> you<00:07:34.440> just<00:07:34.599> have 00:07:34.710 --> 00:07:34.720 align:start position:0% consequences okay and then you just have 00:07:34.720 --> 00:07:38.430 align:start position:0% consequences okay and then you just have to<00:07:34.840> sample<00:07:35.280> it<00:07:35.400> sounds<00:07:36.400> uh<00:07:36.639> easy<00:07:37.199> right<00:07:38.199> uh<00:07:38.319> the 00:07:38.430 --> 00:07:38.440 align:start position:0% to sample it sounds uh easy right uh the 00:07:38.440 --> 00:07:40.230 align:start position:0% to sample it sounds uh easy right uh the question<00:07:38.639> is<00:07:38.840> where<00:07:39.000> you<00:07:39.120> are<00:07:39.280> sampling<00:07:39.720> from 00:07:40.230 --> 00:07:40.240 align:start position:0% question is where you are sampling from 00:07:40.240 --> 00:07:43.230 align:start position:0% question is where you are sampling from and<00:07:40.440> how<00:07:40.599> you<00:07:40.720> do<00:07:40.919> this<00:07:41.120> sample<00:07:42.000> sampling<00:07:42.960> so<00:07:43.120> I 00:07:43.230 --> 00:07:43.240 align:start position:0% and how you do this sample sampling so I 00:07:43.240 --> 00:07:46.350 align:start position:0% and how you do this sample sampling so I wasn't<00:07:43.680> saying<00:07:44.159> anything<00:07:44.520> about<00:07:44.840> that<00:07:45.400> uh<00:07:46.080> so 00:07:46.350 --> 00:07:46.360 align:start position:0% wasn't saying anything about that uh so 00:07:46.360 --> 00:07:49.309 align:start position:0% wasn't saying anything about that uh so let's<00:07:46.960> just<00:07:47.159> see<00:07:48.080> uh 00:07:49.309 --> 00:07:49.319 align:start position:0% let's just see uh 00:07:49.319 --> 00:07:51.629 align:start position:0% let's just see uh that<00:07:50.319> okay<00:07:50.440> so<00:07:50.680> we<00:07:50.840> were<00:07:51.000> typically<00:07:51.400> speaking 00:07:51.629 --> 00:07:51.639 align:start position:0% that okay so we were typically speaking 00:07:51.639 --> 00:07:54.749 align:start position:0% that okay so we were typically speaking of<00:07:51.800> D<00:07:52.240> Das<00:07:52.560> as<00:07:53.560> uh<00:07:53.680> but<00:07:53.800> it's<00:07:53.960> actually<00:07:54.199> a<00:07:54.319> DA 00:07:54.749 --> 00:07:54.759 align:start position:0% of D Das as uh but it's actually a DA 00:07:54.759 --> 00:07:57.990 align:start position:0% of D Das as uh but it's actually a DA plus<00:07:54.919> an<00:07:55.199> S<00:07:56.199> so<00:07:56.400> there<00:07:56.479> is<00:07:56.599> the<00:07:56.720> da<00:07:57.159> part<00:07:57.840> which 00:07:57.990 --> 00:07:58.000 align:start position:0% plus an S so there is the da part which 00:07:58.000 --> 00:08:00.749 align:start position:0% plus an S so there is the da part which is<00:07:58.800> a<00:07:58.960> property<00:07:59.319> of<00:07:59.759> of<00:07:59.919> the<00:08:00.080> of<00:08:00.159> the<00:08:00.319> network 00:08:00.749 --> 00:08:00.759 align:start position:0% is a property of of the of the network 00:08:00.759 --> 00:08:02.430 align:start position:0% is a property of of the of the network it's<00:08:00.879> a<00:08:01.000> global<00:08:01.319> property<00:08:01.840> the<00:08:02.000> data<00:08:02.280> is 00:08:02.430 --> 00:08:02.440 align:start position:0% it's a global property the data is 00:08:02.440 --> 00:08:04.909 align:start position:0% it's a global property the data is available<00:08:02.960> the<00:08:03.120> data<00:08:03.360> is<00:08:03.440> not<00:08:03.800> available<00:08:04.800> and 00:08:04.909 --> 00:08:04.919 align:start position:0% available the data is not available and 00:08:04.919 --> 00:08:07.070 align:start position:0% available the data is not available and to<00:08:05.120> have<00:08:05.280> the<00:08:05.479> data<00:08:05.840> available<00:08:06.400> in<00:08:06.520> the<00:08:06.680> system 00:08:07.070 --> 00:08:07.080 align:start position:0% to have the data available in the system 00:08:07.080 --> 00:08:10.189 align:start position:0% to have the data available in the system I<00:08:07.159> have<00:08:07.280> to<00:08:07.479> dispers<00:08:07.960> it<00:08:08.759> in<00:08:08.879> the<00:08:09.080> system<00:08:09.960> so<00:08:10.080> I 00:08:10.189 --> 00:08:10.199 align:start position:0% I have to dispers it in the system so I 00:08:10.199 --> 00:08:13.270 align:start position:0% I have to dispers it in the system so I have<00:08:10.319> to<00:08:10.800> send<00:08:11.159> it<00:08:11.440> out<00:08:12.440> different<00:08:12.759> pieces<00:08:13.080> to 00:08:13.270 --> 00:08:13.280 align:start position:0% have to send it out different pieces to 00:08:13.280 --> 00:08:17.149 align:start position:0% have to send it out different pieces to different<00:08:13.639> nodes<00:08:14.639> which<00:08:14.800> are<00:08:15.039> custody<00:08:15.879> it<00:08:16.879> and 00:08:17.149 --> 00:08:17.159 align:start position:0% different nodes which are custody it and 00:08:17.159 --> 00:08:20.110 align:start position:0% different nodes which are custody it and only<00:08:17.520> then<00:08:18.520> I<00:08:18.599> can<00:08:18.759> start 00:08:20.110 --> 00:08:20.120 align:start position:0% only then I can start 00:08:20.120 --> 00:08:23.550 align:start position:0% only then I can start sampling<00:08:21.120> so<00:08:21.400> this<00:08:21.520> is<00:08:21.680> the<00:08:22.000> da<00:08:22.479> part<00:08:23.240> it's<00:08:23.479> is 00:08:23.550 --> 00:08:23.560 align:start position:0% sampling so this is the da part it's is 00:08:23.560 --> 00:08:26.790 align:start position:0% sampling so this is the da part it's is uing<00:08:23.960> data<00:08:24.199> ability<00:08:25.159> it<00:08:25.280> is<00:08:25.479> doing<00:08:25.720> the<00:08:25.800> Shing 00:08:26.790 --> 00:08:26.800 align:start position:0% uing data ability it is doing the Shing 00:08:26.800 --> 00:08:29.149 align:start position:0% uing data ability it is doing the Shing not<00:08:27.080> s<00:08:27.360> only<00:08:27.680> receiving<00:08:27.919> pieces<00:08:28.840> and<00:08:29.000> then 00:08:29.149 --> 00:08:29.159 align:start position:0% not s only receiving pieces and then 00:08:29.159 --> 00:08:31.390 align:start position:0% not s only receiving pieces and then there<00:08:29.280> is<00:08:29.560> sampling<00:08:30.039> part<00:08:30.560> once<00:08:30.879> the<00:08:31.039> data<00:08:31.280> is 00:08:31.390 --> 00:08:31.400 align:start position:0% there is sampling part once the data is 00:08:31.400 --> 00:08:33.190 align:start position:0% there is sampling part once the data is in<00:08:31.560> custody<00:08:32.000> at<00:08:32.200> different 00:08:33.190 --> 00:08:33.200 align:start position:0% in custody at different 00:08:33.200 --> 00:08:36.790 align:start position:0% in custody at different nodes<00:08:34.200> uh<00:08:34.360> you<00:08:34.479> can<00:08:34.680> start<00:08:35.200> test<00:08:35.800> sampling 00:08:36.790 --> 00:08:36.800 align:start position:0% nodes uh you can start test sampling 00:08:36.800 --> 00:08:39.870 align:start position:0% nodes uh you can start test sampling asking<00:08:37.080> for<00:08:37.360> pieces<00:08:38.360> and<00:08:38.519> getting 00:08:39.870 --> 00:08:39.880 align:start position:0% asking for pieces and getting 00:08:39.880 --> 00:08:42.310 align:start position:0% asking for pieces and getting pieces<00:08:40.880> little<00:08:41.519> uh<00:08:41.680> graphical 00:08:42.310 --> 00:08:42.320 align:start position:0% pieces little uh graphical 00:08:42.320 --> 00:08:45.190 align:start position:0% pieces little uh graphical representation<00:08:43.320> so<00:08:43.959> uh<00:08:44.080> you<00:08:44.159> have<00:08:44.279> a<00:08:44.399> builder 00:08:45.190 --> 00:08:45.200 align:start position:0% representation so uh you have a builder 00:08:45.200 --> 00:08:47.470 align:start position:0% representation so uh you have a builder it<00:08:45.480> does<00:08:46.120> here<00:08:46.480> in<00:08:46.560> the<00:08:46.680> example<00:08:47.040> I<00:08:47.120> was<00:08:47.279> doing 00:08:47.470 --> 00:08:47.480 align:start position:0% it does here in the example I was doing 00:08:47.480 --> 00:08:49.949 align:start position:0% it does here in the example I was doing it<00:08:47.640> with<00:08:47.800> the<00:08:47.959> 2D<00:08:48.440> encoding<00:08:49.440> so<00:08:49.600> it<00:08:49.720> does<00:08:49.880> the 00:08:49.949 --> 00:08:49.959 align:start position:0% it with the 2D encoding so it does the 00:08:49.959 --> 00:08:52.230 align:start position:0% it with the 2D encoding so it does the 2D<00:08:50.440> encoding<00:08:51.440> and<00:08:51.600> then<00:08:51.760> you<00:08:51.880> have<00:08:52.080> those 00:08:52.230 --> 00:08:52.240 align:start position:0% 2D encoding and then you have those 00:08:52.240 --> 00:08:55.430 align:start position:0% 2D encoding and then you have those Beacon<00:08:52.600> nodes<00:08:53.480> in<00:08:53.600> the<00:08:54.040> system<00:08:55.040> and<00:08:55.240> what<00:08:55.360> you 00:08:55.430 --> 00:08:55.440 align:start position:0% Beacon nodes in the system and what you 00:08:55.440 --> 00:08:57.509 align:start position:0% Beacon nodes in the system and what you are<00:08:55.560> doing<00:08:55.880> you<00:08:55.959> are<00:08:56.120> sending<00:08:56.560> out<00:08:57.040> these 00:08:57.509 --> 00:08:57.519 align:start position:0% are doing you are sending out these 00:08:57.519 --> 00:09:00.269 align:start position:0% are doing you are sending out these things<00:08:58.519> uh<00:08:58.760> pieces<00:08:59.120> of<00:08:59.279> this<00:08:59.720> actually<00:09:00.040> rows 00:09:00.269 --> 00:09:00.279 align:start position:0% things uh pieces of this actually rows 00:09:00.279 --> 00:09:03.990 align:start position:0% things uh pieces of this actually rows and<00:09:00.760> columns<00:09:01.760> two<00:09:02.000> different<00:09:02.680> nodes<00:09:03.680> someone 00:09:03.990 --> 00:09:04.000 align:start position:0% and columns two different nodes someone 00:09:04.000 --> 00:09:05.949 align:start position:0% and columns two different nodes someone is<00:09:04.200> getting<00:09:04.519> only<00:09:04.760> two<00:09:05.000> rows<00:09:05.279> and<00:09:05.399> two<00:09:05.600> columns 00:09:05.949 --> 00:09:05.959 align:start position:0% is getting only two rows and two columns 00:09:05.959 --> 00:09:07.430 align:start position:0% is getting only two rows and two columns someone<00:09:06.200> is<00:09:06.320> getting<00:09:06.560> a<00:09:06.680> bit<00:09:06.839> more<00:09:07.079> someone<00:09:07.279> is 00:09:07.430 --> 00:09:07.440 align:start position:0% someone is getting a bit more someone is 00:09:07.440 --> 00:09:08.590 align:start position:0% someone is getting a bit more someone is getting<00:09:07.640> the<00:09:07.760> whole<00:09:07.959> thing<00:09:08.240> because<00:09:08.440> he's 00:09:08.590 --> 00:09:08.600 align:start position:0% getting the whole thing because he's 00:09:08.600 --> 00:09:10.750 align:start position:0% getting the whole thing because he's running<00:09:08.920> hands<00:09:09.120> of<00:09:09.360> validators<00:09:10.360> and<00:09:10.560> he's 00:09:10.750 --> 00:09:10.760 align:start position:0% running hands of validators and he's 00:09:10.760 --> 00:09:12.350 align:start position:0% running hands of validators and he's securing<00:09:11.200> so<00:09:11.320> much<00:09:11.480> money<00:09:11.800> but<00:09:11.920> it's<00:09:12.120> better 00:09:12.350 --> 00:09:12.360 align:start position:0% securing so much money but it's better 00:09:12.360 --> 00:09:14.750 align:start position:0% securing so much money but it's better for<00:09:12.560> him<00:09:12.720> to<00:09:12.880> get<00:09:13.040> the<00:09:13.160> whole<00:09:13.440> thing<00:09:14.279> plus 00:09:14.750 --> 00:09:14.760 align:start position:0% for him to get the whole thing plus 00:09:14.760 --> 00:09:17.230 align:start position:0% for him to get the whole thing plus doing<00:09:15.079> that<00:09:15.240> he<00:09:15.399> can<00:09:15.519> support<00:09:15.920> the 00:09:17.230 --> 00:09:17.240 align:start position:0% doing that he can support the 00:09:17.240 --> 00:09:19.670 align:start position:0% doing that he can support the system<00:09:18.240> that's<00:09:18.480> one<00:09:18.760> side<00:09:19.200> that's<00:09:19.399> just<00:09:19.519> the 00:09:19.670 --> 00:09:19.680 align:start position:0% system that's one side that's just the 00:09:19.680 --> 00:09:21.790 align:start position:0% system that's one side that's just the data<00:09:19.920> viability<00:09:20.640> now<00:09:20.800> you<00:09:20.920> have<00:09:21.040> to<00:09:21.200> sample 00:09:21.790 --> 00:09:21.800 align:start position:0% data viability now you have to sample 00:09:21.800 --> 00:09:23.750 align:start position:0% data viability now you have to sample and<00:09:22.000> that's<00:09:22.320> an<00:09:22.480> individual 00:09:23.750 --> 00:09:23.760 align:start position:0% and that's an individual 00:09:23.760 --> 00:09:26.150 align:start position:0% and that's an individual node<00:09:24.760> and<00:09:24.920> actually<00:09:25.240> every<00:09:25.480> individual<00:09:25.880> node 00:09:26.150 --> 00:09:26.160 align:start position:0% node and actually every individual node 00:09:26.160 --> 00:09:29.230 align:start position:0% node and actually every individual node has<00:09:26.240> to<00:09:26.839> sample<00:09:27.839> that's<00:09:28.040> his<00:09:28.160> own<00:09:28.360> view<00:09:28.880> so<00:09:29.079> he 00:09:29.230 --> 00:09:29.240 align:start position:0% has to sample that's his own view so he 00:09:29.240 --> 00:09:31.870 align:start position:0% has to sample that's his own view so he is<00:09:29.720> picking<00:09:30.200> a<00:09:30.320> few 00:09:31.870 --> 00:09:31.880 align:start position:0% is picking a few 00:09:31.880 --> 00:09:36.190 align:start position:0% is picking a few pieces<00:09:32.880> and<00:09:33.120> then<00:09:33.680> asking<00:09:34.000> for<00:09:34.320> those<00:09:35.320> from 00:09:36.190 --> 00:09:36.200 align:start position:0% pieces and then asking for those from 00:09:36.200 --> 00:09:38.190 align:start position:0% pieces and then asking for those from custody<00:09:37.200> so<00:09:37.399> you're<00:09:37.519> getting<00:09:37.800> this<00:09:38.000> piece 00:09:38.190 --> 00:09:38.200 align:start position:0% custody so you're getting this piece 00:09:38.200 --> 00:09:39.750 align:start position:0% custody so you're getting this piece from<00:09:38.440> here<00:09:38.760> that<00:09:38.959> from<00:09:39.160> there<00:09:39.360> that<00:09:39.480> from 00:09:39.750 --> 00:09:39.760 align:start position:0% from here that from there that from 00:09:39.760 --> 00:09:42.750 align:start position:0% from here that from there that from there<00:09:40.320> and<00:09:40.839> if<00:09:40.959> it<00:09:41.079> manages<00:09:41.399> to<00:09:41.560> sample<00:09:42.519> then 00:09:42.750 --> 00:09:42.760 align:start position:0% there and if it manages to sample then 00:09:42.760 --> 00:09:44.030 align:start position:0% there and if it manages to sample then things<00:09:42.959> are 00:09:44.030 --> 00:09:44.040 align:start position:0% things are 00:09:44.040 --> 00:09:45.550 align:start position:0% things are good 00:09:45.550 --> 00:09:45.560 align:start position:0% good 00:09:45.560 --> 00:09:49.389 align:start position:0% good okay<00:09:46.760> so<00:09:47.760> we<00:09:47.920> have<00:09:48.160> this<00:09:48.360> kind<00:09:48.519> of<00:09:48.880> two<00:09:49.120> sides 00:09:49.389 --> 00:09:49.399 align:start position:0% okay so we have this kind of two sides 00:09:49.399 --> 00:09:50.710 align:start position:0% okay so we have this kind of two sides of<00:09:49.519> things<00:09:49.800> and<00:09:49.920> you<00:09:50.000> can<00:09:50.120> see<00:09:50.320> that<00:09:50.480> on<00:09:50.600> the 00:09:50.710 --> 00:09:50.720 align:start position:0% of things and you can see that on the 00:09:50.720 --> 00:09:53.030 align:start position:0% of things and you can see that on the network<00:09:51.120> these<00:09:51.240> are<00:09:51.399> a<00:09:51.519> little<00:09:51.720> bit<00:09:52.040> different 00:09:53.030 --> 00:09:53.040 align:start position:0% network these are a little bit different 00:09:53.040 --> 00:09:55.269 align:start position:0% network these are a little bit different and<00:09:53.160> we<00:09:53.279> need<00:09:53.519> them<00:09:53.680> to 00:09:55.269 --> 00:09:55.279 align:start position:0% and we need them to 00:09:55.279 --> 00:09:59.389 align:start position:0% and we need them to behave<00:09:56.440> differently<00:09:57.440> so<00:09:57.600> we<00:09:57.760> need<00:09:58.079> them<00:09:58.519> to<00:09:58.720> be 00:09:59.389 --> 00:09:59.399 align:start position:0% behave differently so we need them to be 00:09:59.399 --> 00:10:02.269 align:start position:0% behave differently so we need them to be secure<00:09:59.800> robust<00:10:00.279> fast<00:10:00.519> and<00:10:00.839> cheap<00:10:01.839> and<00:10:02.000> we<00:10:02.120> need 00:10:02.269 --> 00:10:02.279 align:start position:0% secure robust fast and cheap and we need 00:10:02.279 --> 00:10:04.389 align:start position:0% secure robust fast and cheap and we need sampling<00:10:02.680> to<00:10:02.800> be<00:10:02.920> secure<00:10:03.240> robust<00:10:03.600> fast<00:10:03.800> and 00:10:04.389 --> 00:10:04.399 align:start position:0% sampling to be secure robust fast and 00:10:04.399 --> 00:10:07.110 align:start position:0% sampling to be secure robust fast and cheap<00:10:05.399> um<00:10:06.000> so<00:10:06.120> we<00:10:06.240> need<00:10:06.360> the<00:10:06.480> same<00:10:06.720> properties 00:10:07.110 --> 00:10:07.120 align:start position:0% cheap um so we need the same properties 00:10:07.120 --> 00:10:09.269 align:start position:0% cheap um so we need the same properties for<00:10:07.200> the<00:10:07.360> two<00:10:07.519> things<00:10:08.200> it's<00:10:08.480> just<00:10:08.959> uh 00:10:09.269 --> 00:10:09.279 align:start position:0% for the two things it's just uh 00:10:09.279 --> 00:10:11.829 align:start position:0% for the two things it's just uh different 00:10:11.829 --> 00:10:11.839 align:start position:0% different 00:10:11.839 --> 00:10:13.870 align:start position:0% different protocols 00:10:13.870 --> 00:10:13.880 align:start position:0% protocols 00:10:13.880 --> 00:10:18.190 align:start position:0% protocols okay 00:10:18.190 --> 00:10:18.200 align:start position:0% 00:10:18.200 --> 00:10:21.350 align:start position:0% so<00:10:19.200> I<00:10:19.320> was<00:10:19.519> saying<00:10:20.000> that<00:10:20.519> there<00:10:20.640> is<00:10:20.800> peas<00:10:21.240> and 00:10:21.350 --> 00:10:21.360 align:start position:0% so I was saying that there is peas and 00:10:21.360 --> 00:10:23.030 align:start position:0% so I was saying that there is peas and there<00:10:21.440> is<00:10:21.519> FAS<00:10:22.200> and<00:10:22.320> there<00:10:22.399> is<00:10:22.600> difference<00:10:22.920> in 00:10:23.030 --> 00:10:23.040 align:start position:0% there is FAS and there is difference in 00:10:23.040 --> 00:10:24.630 align:start position:0% there is FAS and there is difference in the<00:10:23.160> data<00:10:23.440> structure<00:10:23.920> actually<00:10:24.200> there<00:10:24.279> are<00:10:24.519> a 00:10:24.630 --> 00:10:24.640 align:start position:0% the data structure actually there are a 00:10:24.640 --> 00:10:27.230 align:start position:0% the data structure actually there are a number<00:10:24.839> of<00:10:25.399> differences<00:10:26.399> uh<00:10:26.560> if<00:10:26.640> you<00:10:26.880> scan 00:10:27.230 --> 00:10:27.240 align:start position:0% number of differences uh if you scan 00:10:27.240 --> 00:10:28.990 align:start position:0% number of differences uh if you scan that<00:10:27.399> QR<00:10:27.720> code<00:10:27.959> we<00:10:28.079> have<00:10:28.160> a<00:10:28.320> right<00:10:28.560> up<00:10:28.720> on<00:10:28.880> on 00:10:28.990 --> 00:10:29.000 align:start position:0% that QR code we have a right up on on 00:10:29.000 --> 00:10:31.790 align:start position:0% that QR code we have a right up on on full<00:10:29.640> which<00:10:29.720> is<00:10:29.880> starting<00:10:30.279> from<00:10:30.680> uh<00:10:30.839> from<00:10:31.040> pust 00:10:31.790 --> 00:10:31.800 align:start position:0% full which is starting from uh from pust 00:10:31.800 --> 00:10:34.670 align:start position:0% full which is starting from uh from pust and<00:10:32.160> uh<00:10:32.519> some<00:10:32.720> of<00:10:32.920> these<00:10:33.120> techniques<00:10:33.800> apply<00:10:34.480> to 00:10:34.670 --> 00:10:34.680 align:start position:0% and uh some of these techniques apply to 00:10:34.680 --> 00:10:36.590 align:start position:0% and uh some of these techniques apply to pust<00:10:35.200> some<00:10:35.320> of<00:10:35.480> them<00:10:35.600> to<00:10:35.720> fust<00:10:36.240> so<00:10:36.360> what<00:10:36.480> you 00:10:36.590 --> 00:10:36.600 align:start position:0% pust some of them to fust so what you 00:10:36.600 --> 00:10:41.230 align:start position:0% pust some of them to fust so what you see<00:10:36.920> here<00:10:37.720> is<00:10:37.920> peas<00:10:38.560> and<00:10:38.680> in<00:10:39.240> pillas<00:10:40.240> you<00:10:40.480> have 00:10:41.230 --> 00:10:41.240 align:start position:0% see here is peas and in pillas you have 00:10:41.240 --> 00:10:42.350 align:start position:0% see here is peas and in pillas you have onedimensional 00:10:42.350 --> 00:10:42.360 align:start position:0% onedimensional 00:10:42.360 --> 00:10:44.509 align:start position:0% onedimensional extension<00:10:43.360> and<00:10:43.560> that<00:10:43.720> also<00:10:43.959> means<00:10:44.240> that<00:10:44.399> when 00:10:44.509 --> 00:10:44.519 align:start position:0% extension and that also means that when 00:10:44.519 --> 00:10:48.069 align:start position:0% extension and that also means that when you<00:10:44.600> are<00:10:45.160> sampling<00:10:46.160> you<00:10:46.360> cannot<00:10:46.720> just<00:10:46.959> get<00:10:47.920> a 00:10:48.069 --> 00:10:48.079 align:start position:0% you are sampling you cannot just get a 00:10:48.079 --> 00:10:49.750 align:start position:0% you are sampling you cannot just get a small<00:10:48.399> piece<00:10:48.839> because<00:10:49.040> it<00:10:49.120> would<00:10:49.320> not<00:10:49.519> tell 00:10:49.750 --> 00:10:49.760 align:start position:0% small piece because it would not tell 00:10:49.760 --> 00:10:51.990 align:start position:0% small piece because it would not tell you<00:10:50.000> probabilistically<00:10:50.839> enough<00:10:51.519> you<00:10:51.680> have<00:10:51.839> to 00:10:51.990 --> 00:10:52.000 align:start position:0% you probabilistically enough you have to 00:10:52.000 --> 00:10:53.150 align:start position:0% you probabilistically enough you have to get<00:10:52.120> a<00:10:52.240> full 00:10:53.150 --> 00:10:53.160 align:start position:0% get a full 00:10:53.160 --> 00:10:56.949 align:start position:0% get a full column<00:10:54.160> so<00:10:54.360> your<00:10:54.600> sample<00:10:55.360> is<00:10:55.480> a<00:10:55.800> column<00:10:56.800> which 00:10:56.949 --> 00:10:56.959 align:start position:0% column so your sample is a column which 00:10:56.959 --> 00:11:00.190 align:start position:0% column so your sample is a column which is<00:10:57.079> more<00:10:57.519> data<00:10:58.519> than<00:10:58.639> a<00:10:58.800> cell 00:11:00.190 --> 00:11:00.200 align:start position:0% is more data than a cell 00:11:00.200 --> 00:11:02.230 align:start position:0% is more data than a cell that<00:11:00.320> you<00:11:00.440> can<00:11:00.600> sample<00:11:01.480> if<00:11:01.600> you<00:11:01.720> have<00:11:01.880> this<00:11:02.040> two 00:11:02.230 --> 00:11:02.240 align:start position:0% that you can sample if you have this two 00:11:02.240 --> 00:11:04.829 align:start position:0% that you can sample if you have this two dimensional 00:11:04.829 --> 00:11:04.839 align:start position:0% 00:11:04.839 --> 00:11:07.350 align:start position:0% extension<00:11:05.839> uh<00:11:06.079> but<00:11:06.200> to<00:11:06.360> make<00:11:06.560> this<00:11:06.760> work<00:11:07.200> you 00:11:07.350 --> 00:11:07.360 align:start position:0% extension uh but to make this work you 00:11:07.360 --> 00:11:08.949 align:start position:0% extension uh but to make this work you need<00:11:07.600> changes<00:11:07.920> in<00:11:08.079> the<00:11:08.200> networking<00:11:08.680> changes 00:11:08.949 --> 00:11:08.959 align:start position:0% need changes in the networking changes 00:11:08.959 --> 00:11:10.829 align:start position:0% need changes in the networking changes in<00:11:09.079> the<00:11:09.160> other<00:11:09.519> coding<00:11:09.839> changes<00:11:10.079> in<00:11:10.240> many 00:11:10.829 --> 00:11:10.839 align:start position:0% in the other coding changes in many 00:11:10.839 --> 00:11:13.030 align:start position:0% in the other coding changes in many things 00:11:13.030 --> 00:11:13.040 align:start position:0% things 00:11:13.040 --> 00:11:16.629 align:start position:0% things okay 00:11:16.629 --> 00:11:16.639 align:start position:0% 00:11:16.639 --> 00:11:19.710 align:start position:0% so<00:11:17.639> let<00:11:17.760> me<00:11:18.200> just<00:11:18.360> give<00:11:18.480> you<00:11:18.600> a<00:11:18.720> comparision<00:11:19.480> of 00:11:19.710 --> 00:11:19.720 align:start position:0% so let me just give you a comparision of 00:11:19.720 --> 00:11:23.470 align:start position:0% so let me just give you a comparision of peas<00:11:20.160> and 00:11:23.470 --> 00:11:23.480 align:start position:0% 00:11:23.480 --> 00:11:26.750 align:start position:0% foras<00:11:24.480> actually<00:11:24.760> let<00:11:24.920> me<00:11:25.519> go<00:11:25.720> back<00:11:26.120> and<00:11:26.440> and 00:11:26.750 --> 00:11:26.760 align:start position:0% foras actually let me go back and and 00:11:26.760 --> 00:11:29.430 align:start position:0% foras actually let me go back and and just<00:11:27.079> go<00:11:27.200> through<00:11:27.480> this<00:11:27.639> list<00:11:28.200> so<00:11:28.399> we<00:11:28.600> have 00:11:29.430 --> 00:11:29.440 align:start position:0% just go through this list so we have 00:11:29.440 --> 00:11:33.509 align:start position:0% just go through this list so we have techniques<00:11:29.920> here<00:11:30.920> uh<00:11:31.760> the<00:11:31.920> first<00:11:32.320> category<00:11:33.320> is 00:11:33.509 --> 00:11:33.519 align:start position:0% techniques here uh the first category is 00:11:33.519 --> 00:11:35.750 align:start position:0% techniques here uh the first category is about<00:11:34.160> sampling<00:11:34.720> is<00:11:34.880> about<00:11:35.320> how<00:11:35.560> I'm 00:11:35.750 --> 00:11:35.760 align:start position:0% about sampling is about how I'm 00:11:35.760 --> 00:11:37.590 align:start position:0% about sampling is about how I'm selecting<00:11:36.480> what<00:11:36.639> to<00:11:36.800> sample<00:11:37.279> how<00:11:37.440> I'm 00:11:37.590 --> 00:11:37.600 align:start position:0% selecting what to sample how I'm 00:11:37.600 --> 00:11:40.350 align:start position:0% selecting what to sample how I'm selecting<00:11:38.079> those<00:11:38.560> small<00:11:38.920> pieces<00:11:39.920> that<00:11:40.040> I<00:11:40.160> will 00:11:40.350 --> 00:11:40.360 align:start position:0% selecting those small pieces that I will 00:11:40.360 --> 00:11:43.350 align:start position:0% selecting those small pieces that I will be<00:11:40.480> looking<00:11:41.040> for<00:11:42.040> then<00:11:42.360> the<00:11:42.480> second<00:11:42.800> category 00:11:43.350 --> 00:11:43.360 align:start position:0% be looking for then the second category 00:11:43.360 --> 00:11:47.430 align:start position:0% be looking for then the second category is<00:11:43.959> about<00:11:45.079> uh<00:11:46.079> AER<00:11:46.560> coding<00:11:46.839> and<00:11:46.959> the<00:11:47.040> using<00:11:47.320> of 00:11:47.430 --> 00:11:47.440 align:start position:0% is about uh AER coding and the using of 00:11:47.440 --> 00:11:50.990 align:start position:0% is about uh AER coding and the using of the<00:11:47.560> aure<00:11:48.000> coding<00:11:49.000> because<00:11:49.240> what<00:11:49.360> I<00:11:49.480> can<00:11:49.680> do<00:11:50.519> is 00:11:50.990 --> 00:11:51.000 align:start position:0% the aure coding because what I can do is 00:11:51.000 --> 00:11:53.790 align:start position:0% the aure coding because what I can do is if<00:11:51.200> the<00:11:51.320> data<00:11:51.560> is<00:11:51.639> AER<00:11:52.079> coded<00:11:53.000> I<00:11:53.120> can<00:11:53.320> use<00:11:53.560> that 00:11:53.790 --> 00:11:53.800 align:start position:0% if the data is AER coded I can use that 00:11:53.800 --> 00:11:56.829 align:start position:0% if the data is AER coded I can use that as<00:11:54.079> part<00:11:54.320> of<00:11:54.560> the<00:11:55.040> transmission<00:11:55.800> so<00:11:56.160> when<00:11:56.480> I'm 00:11:56.829 --> 00:11:56.839 align:start position:0% as part of the transmission so when I'm 00:11:56.839 --> 00:11:59.310 align:start position:0% as part of the transmission so when I'm sending<00:11:57.279> the<00:11:57.480> data<00:11:58.399> I<00:11:58.480> can<00:11:58.639> already<00:11:58.920> use<00:11:59.279> the 00:11:59.310 --> 00:11:59.320 align:start position:0% sending the data I can already use the 00:11:59.320 --> 00:12:01.790 align:start position:0% sending the data I can already use the aure<00:11:59.680> coding<00:12:00.079> to<00:12:00.279> recover<00:12:00.839> data<00:12:01.399> and<00:12:01.560> then 00:12:01.790 --> 00:12:01.800 align:start position:0% aure coding to recover data and then 00:12:01.800 --> 00:12:03.870 align:start position:0% aure coding to recover data and then send<00:12:02.040> it<00:12:02.160> on<00:12:02.320> to<00:12:02.480> others<00:12:03.360> and<00:12:03.480> that's<00:12:03.600> a<00:12:03.760> very 00:12:03.870 --> 00:12:03.880 align:start position:0% send it on to others and that's a very 00:12:03.880 --> 00:12:05.310 align:start position:0% send it on to others and that's a very important<00:12:04.279> property<00:12:04.600> we<00:12:04.680> are<00:12:04.839> always<00:12:05.040> using 00:12:05.310 --> 00:12:05.320 align:start position:0% important property we are always using 00:12:05.320 --> 00:12:06.509 align:start position:0% important property we are always using aure<00:12:05.680> coding<00:12:05.959> when<00:12:06.079> we<00:12:06.160> are<00:12:06.279> doing 00:12:06.509 --> 00:12:06.519 align:start position:0% aure coding when we are doing 00:12:06.519 --> 00:12:08.110 align:start position:0% aure coding when we are doing transmission<00:12:07.040> actually<00:12:07.519> take<00:12:07.680> your<00:12:07.839> mobile 00:12:08.110 --> 00:12:08.120 align:start position:0% transmission actually take your mobile 00:12:08.120 --> 00:12:11.870 align:start position:0% transmission actually take your mobile phone<00:12:08.399> take<00:12:08.800> whatever<00:12:10.040> uh<00:12:11.040> here<00:12:11.320> we<00:12:11.399> can<00:12:11.560> use 00:12:11.870 --> 00:12:11.880 align:start position:0% phone take whatever uh here we can use 00:12:11.880 --> 00:12:14.910 align:start position:0% phone take whatever uh here we can use aure<00:12:12.240> coding<00:12:13.040> uh<00:12:13.199> very<00:12:13.440> efficiently<00:12:14.360> to<00:12:14.519> send 00:12:14.910 --> 00:12:14.920 align:start position:0% aure coding uh very efficiently to send 00:12:14.920 --> 00:12:17.629 align:start position:0% aure coding uh very efficiently to send data<00:12:15.440> and<00:12:15.560> when<00:12:15.680> we<00:12:15.760> are<00:12:15.880> sending<00:12:16.199> a<00:12:16.519> row<00:12:17.519> we 00:12:17.629 --> 00:12:17.639 align:start position:0% data and when we are sending a row we 00:12:17.639 --> 00:12:20.750 align:start position:0% data and when we are sending a row we can<00:12:18.120> take<00:12:18.279> a<00:12:18.720> piece<00:12:19.720> and<00:12:19.839> we<00:12:19.959> can<00:12:20.160> send<00:12:20.399> it<00:12:20.519> on<00:12:20.639> a 00:12:20.750 --> 00:12:20.760 align:start position:0% can take a piece and we can send it on a 00:12:20.760 --> 00:12:22.910 align:start position:0% can take a piece and we can send it on a column<00:12:21.120> and<00:12:21.320> then<00:12:21.519> we<00:12:21.720> we<00:12:22.160> have<00:12:22.360> when<00:12:22.480> we<00:12:22.600> have 00:12:22.910 --> 00:12:22.920 align:start position:0% column and then we we have when we have 00:12:22.920 --> 00:12:26.470 align:start position:0% column and then we we have when we have received<00:12:23.320> half<00:12:23.519> of<00:12:23.680> a<00:12:23.880> row<00:12:24.680> we<00:12:24.800> can<00:12:25.000> extend<00:12:25.480> it 00:12:26.470 --> 00:12:26.480 align:start position:0% received half of a row we can extend it 00:12:26.480 --> 00:12:31.509 align:start position:0% received half of a row we can extend it uh<00:12:27.279> to<00:12:28.279> uh<00:12:28.880> to<00:12:29.279> whole<00:12:29.519> row<00:12:29.880> for 00:12:31.509 --> 00:12:31.519 align:start position:0% uh to uh to whole row for 00:12:31.519 --> 00:12:33.949 align:start position:0% uh to uh to whole row for example<00:12:32.519> uh<00:12:32.680> and<00:12:32.839> then<00:12:33.040> there<00:12:33.160> are<00:12:33.399> techniques 00:12:33.949 --> 00:12:33.959 align:start position:0% example uh and then there are techniques 00:12:33.959 --> 00:12:37.590 align:start position:0% example uh and then there are techniques which<00:12:34.360> are<00:12:35.360> protocol<00:12:36.160> changes<00:12:37.160> and<00:12:37.320> I'm<00:12:37.440> not 00:12:37.590 --> 00:12:37.600 align:start position:0% which are protocol changes and I'm not 00:12:37.600 --> 00:12:39.990 align:start position:0% which are protocol changes and I'm not going<00:12:37.800> through<00:12:38.079> all<00:12:38.199> of<00:12:38.560> them<00:12:39.560> just<00:12:39.720> showing 00:12:39.990 --> 00:12:40.000 align:start position:0% going through all of them just showing 00:12:40.000 --> 00:12:43.670 align:start position:0% going through all of them just showing you<00:12:40.120> the<00:12:40.279> comparision<00:12:40.760> so<00:12:40.959> p<00:12:41.360> and 00:12:43.670 --> 00:12:43.680 align:start position:0% 00:12:43.680 --> 00:12:47.110 align:start position:0% FAS<00:12:44.680> uh<00:12:45.160> so<00:12:45.320> one<00:12:45.480> is<00:12:45.600> cheap<00:12:46.160> robust<00:12:46.680> fast<00:12:46.959> and 00:12:47.110 --> 00:12:47.120 align:start position:0% FAS uh so one is cheap robust fast and 00:12:47.120 --> 00:12:48.910 align:start position:0% FAS uh so one is cheap robust fast and secure<00:12:47.480> and<00:12:47.600> the<00:12:47.680> other<00:12:47.839> is<00:12:47.959> cheaper<00:12:48.680> more 00:12:48.910 --> 00:12:48.920 align:start position:0% secure and the other is cheaper more 00:12:48.920 --> 00:12:52.189 align:start position:0% secure and the other is cheaper more robust<00:12:49.519> faster<00:12:50.000> and<00:12:50.160> more<00:12:50.680> secure<00:12:51.680> and<00:12:51.800> I<00:12:51.920> was 00:12:52.189 --> 00:12:52.199 align:start position:0% robust faster and more secure and I was 00:12:52.199 --> 00:12:56.110 align:start position:0% robust faster and more secure and I was inclined<00:12:52.680> to<00:12:52.839> stop<00:12:53.480> here<00:12:54.480> uh<00:12:55.440> but<00:12:55.600> let's<00:12:55.760> see<00:12:55.959> a 00:12:56.110 --> 00:12:56.120 align:start position:0% inclined to stop here uh but let's see a 00:12:56.120 --> 00:13:00.269 align:start position:0% inclined to stop here uh but let's see a little<00:12:56.320> bit<00:12:56.440> more<00:12:56.639> in<00:12:56.800> detail 00:13:00.269 --> 00:13:00.279 align:start position:0% 00:13:00.279 --> 00:13:03.629 align:start position:0% okay<00:13:01.279> so<00:13:01.480> Fus<00:13:01.920> is<00:13:02.000> cheaper<00:13:02.959> uh<00:13:03.079> it's<00:13:03.240> cheaper 00:13:03.629 --> 00:13:03.639 align:start position:0% okay so Fus is cheaper uh it's cheaper 00:13:03.639 --> 00:13:05.790 align:start position:0% okay so Fus is cheaper uh it's cheaper because<00:13:03.880> it's<00:13:04.120> as<00:13:04.199> I<00:13:04.360> shown<00:13:04.959> it's<00:13:05.120> sampling<00:13:05.639> at 00:13:05.790 --> 00:13:05.800 align:start position:0% because it's as I shown it's sampling at 00:13:05.800 --> 00:13:09.910 align:start position:0% because it's as I shown it's sampling at the<00:13:05.880> cell<00:13:06.199> level<00:13:07.040> and<00:13:07.199> the<00:13:07.360> cell<00:13:08.040> is<00:13:08.560> 512<00:13:09.560> bytes 00:13:09.910 --> 00:13:09.920 align:start position:0% the cell level and the cell is 512 bytes 00:13:09.920 --> 00:13:11.110 align:start position:0% the cell level and the cell is 512 bytes actually<00:13:10.160> it's 00:13:11.110 --> 00:13:11.120 align:start position:0% actually it's 00:13:11.120 --> 00:13:13.990 align:start position:0% actually it's 590<00:13:12.120> bytes<00:13:12.440> because<00:13:12.639> it's<00:13:12.839> the<00:13:13.040> data<00:13:13.320> plus<00:13:13.480> the 00:13:13.990 --> 00:13:14.000 align:start position:0% 590 bytes because it's the data plus the 00:13:14.000 --> 00:13:16.389 align:start position:0% 590 bytes because it's the data plus the proof<00:13:15.000> uh<00:13:15.160> which<00:13:15.279> is<00:13:15.399> still<00:13:15.680> much<00:13:15.880> smaller 00:13:16.389 --> 00:13:16.399 align:start position:0% proof uh which is still much smaller 00:13:16.399 --> 00:13:19.150 align:start position:0% proof uh which is still much smaller than<00:13:16.600> than<00:13:16.720> a<00:13:16.800> whole<00:13:17.480> column<00:13:18.480> so<00:13:18.680> whenever<00:13:19.040> we 00:13:19.150 --> 00:13:19.160 align:start position:0% than than a whole column so whenever we 00:13:19.160 --> 00:13:22.030 align:start position:0% than than a whole column so whenever we are<00:13:19.800> uh<00:13:20.760> so<00:13:20.920> the 00:13:22.030 --> 00:13:22.040 align:start position:0% are uh so the 00:13:22.040 --> 00:13:24.509 align:start position:0% are uh so the sampling<00:13:23.040> uh<00:13:23.279> becomes 00:13:24.509 --> 00:13:24.519 align:start position:0% sampling uh becomes 00:13:24.519 --> 00:13:28.750 align:start position:0% sampling uh becomes cheaper<00:13:25.519> it's<00:13:25.680> more<00:13:26.240> robust<00:13:27.240> because<00:13:28.199> it<00:13:28.399> can 00:13:28.750 --> 00:13:28.760 align:start position:0% cheaper it's more robust because it can 00:13:28.760 --> 00:13:31.430 align:start position:0% cheaper it's more robust because it can do<00:13:29.120> arure<00:13:29.519> coding<00:13:30.240> which<00:13:30.360> is<00:13:30.519> allowing<00:13:31.320> uh 00:13:31.430 --> 00:13:31.440 align:start position:0% do arure coding which is allowing uh 00:13:31.440 --> 00:13:33.629 align:start position:0% do arure coding which is allowing uh what<00:13:31.560> I<00:13:31.920> was<00:13:32.079> calling<00:13:32.320> local<00:13:32.639> repair<00:13:33.160> but<00:13:33.480> uh 00:13:33.629 --> 00:13:33.639 align:start position:0% what I was calling local repair but uh 00:13:33.639 --> 00:13:36.629 align:start position:0% what I was calling local repair but uh what<00:13:33.800> local<00:13:34.440> means<00:13:35.440> uh<00:13:35.639> is<00:13:35.839> important<00:13:36.199> to 00:13:36.629 --> 00:13:36.639 align:start position:0% what local means uh is important to 00:13:36.639 --> 00:13:38.189 align:start position:0% what local means uh is important to understand<00:13:36.800> local<00:13:37.160> means<00:13:37.560> in<00:13:37.680> the<00:13:37.800> sense<00:13:38.040> of 00:13:38.189 --> 00:13:38.199 align:start position:0% understand local means in the sense of 00:13:38.199 --> 00:13:41.430 align:start position:0% understand local means in the sense of the<00:13:38.399> code<00:13:38.920> in<00:13:39.040> the<00:13:39.199> sense<00:13:39.519> of<00:13:40.519> let<00:13:40.639> me<00:13:40.880> go<00:13:41.079> back 00:13:41.430 --> 00:13:41.440 align:start position:0% the code in the sense of let me go back 00:13:41.440 --> 00:13:44.430 align:start position:0% the code in the sense of let me go back here<00:13:42.199> in<00:13:42.320> the<00:13:42.480> sense<00:13:42.720> of<00:13:43.320> this<00:13:43.600> Square<00:13:44.120> so<00:13:44.320> I 00:13:44.430 --> 00:13:44.440 align:start position:0% here in the sense of this Square so I 00:13:44.440 --> 00:13:46.870 align:start position:0% here in the sense of this Square so I only<00:13:44.639> have<00:13:44.760> a<00:13:44.880> few<00:13:45.240> data<00:13:45.600> I<00:13:45.720> only<00:13:46.000> have<00:13:46.519> half<00:13:46.760> of 00:13:46.870 --> 00:13:46.880 align:start position:0% only have a few data I only have half of 00:13:46.880 --> 00:13:49.310 align:start position:0% only have a few data I only have half of a<00:13:47.040> column<00:13:47.880> and<00:13:48.040> I<00:13:48.120> can<00:13:48.320> repair<00:13:48.800> something<00:13:49.240> I 00:13:49.310 --> 00:13:49.320 align:start position:0% a column and I can repair something I 00:13:49.320 --> 00:13:52.189 align:start position:0% a column and I can repair something I can<00:13:49.959> generate<00:13:50.519> these<00:13:51.040> or<00:13:51.199> I<00:13:51.320> have<00:13:51.519> these<00:13:52.000> and<00:13:52.120> I 00:13:52.189 --> 00:13:52.199 align:start position:0% can generate these or I have these and I 00:13:52.199 --> 00:13:54.829 align:start position:0% can generate these or I have these and I can<00:13:52.360> generate<00:13:52.720> these<00:13:53.519> well<00:13:53.639> I<00:13:53.759> have<00:13:53.920> a<00:13:54.519> half<00:13:54.720> of 00:13:54.829 --> 00:13:54.839 align:start position:0% can generate these well I have a half of 00:13:54.839 --> 00:13:56.629 align:start position:0% can generate these well I have a half of the<00:13:55.000> pieces<00:13:55.399> here<00:13:55.560> and<00:13:55.759> I<00:13:55.839> can<00:13:56.000> generate<00:13:56.440> this 00:13:56.629 --> 00:13:56.639 align:start position:0% the pieces here and I can generate this 00:13:56.639 --> 00:13:59.829 align:start position:0% the pieces here and I can generate this one<00:13:57.639> I<00:13:57.800> cannot<00:13:58.120> do<00:13:58.279> that<00:13:58.440> up<00:13:58.680> there 00:13:59.829 --> 00:13:59.839 align:start position:0% one I cannot do that up there 00:13:59.839 --> 00:14:02.069 align:start position:0% one I cannot do that up there and<00:14:00.000> that's<00:14:00.160> a<00:14:00.320> huge<00:14:00.759> difference<00:14:01.759> that's<00:14:01.920> a 00:14:02.069 --> 00:14:02.079 align:start position:0% and that's a huge difference that's a 00:14:02.079 --> 00:14:04.990 align:start position:0% and that's a huge difference that's a huge<00:14:02.720> difference<00:14:03.720> because<00:14:04.040> that<00:14:04.199> means<00:14:04.759> that 00:14:04.990 --> 00:14:05.000 align:start position:0% huge difference because that means that 00:14:05.000 --> 00:14:08.389 align:start position:0% huge difference because that means that every<00:14:05.279> single<00:14:05.639> node<00:14:06.440> can<00:14:06.600> do<00:14:06.800> repair<00:14:07.800> not<00:14:08.079> just 00:14:08.389 --> 00:14:08.399 align:start position:0% every single node can do repair not just 00:14:08.399 --> 00:14:11.470 align:start position:0% every single node can do repair not just big<00:14:08.600> nodes<00:14:08.959> who<00:14:09.079> are<00:14:09.240> having<00:14:09.480> old<00:14:10.160> data<00:14:11.160> uh<00:14:11.320> but 00:14:11.470 --> 00:14:11.480 align:start position:0% big nodes who are having old data uh but 00:14:11.480 --> 00:14:13.470 align:start position:0% big nodes who are having old data uh but every<00:14:11.680> single<00:14:11.959> node<00:14:12.320> actually<00:14:13.120> in<00:14:13.279> that 00:14:13.470 --> 00:14:13.480 align:start position:0% every single node actually in that 00:14:13.480 --> 00:14:16.470 align:start position:0% every single node actually in that construct<00:14:13.920> we<00:14:14.040> don't<00:14:14.279> need<00:14:14.560> big<00:14:15.120> nodes<00:14:16.120> uh 00:14:16.470 --> 00:14:16.480 align:start position:0% construct we don't need big nodes uh 00:14:16.480 --> 00:14:17.990 align:start position:0% construct we don't need big nodes uh which<00:14:16.680> by<00:14:16.800> the<00:14:16.920> way<00:14:17.040> we<00:14:17.160> have<00:14:17.279> in<00:14:17.440> etherum<00:14:17.880> so 00:14:17.990 --> 00:14:18.000 align:start position:0% which by the way we have in etherum so 00:14:18.000 --> 00:14:20.470 align:start position:0% which by the way we have in etherum so it's<00:14:18.120> not<00:14:18.360> like<00:14:18.720> we<00:14:18.839> don't<00:14:19.079> have<00:14:19.279> them<00:14:20.279> uh<00:14:20.399> but 00:14:20.470 --> 00:14:20.480 align:start position:0% it's not like we don't have them uh but 00:14:20.480 --> 00:14:23.749 align:start position:0% it's not like we don't have them uh but we<00:14:20.600> are<00:14:20.680> not<00:14:20.920> relying<00:14:21.399> on<00:14:21.920> them<00:14:22.600> doing<00:14:23.240> the 00:14:23.749 --> 00:14:23.759 align:start position:0% we are not relying on them doing the 00:14:23.759 --> 00:14:27.550 align:start position:0% we are not relying on them doing the repair<00:14:24.759> in<00:14:25.000> the<00:14:25.399> in<00:14:25.519> the<00:14:25.680> data<00:14:26.399> structure<00:14:27.399> and 00:14:27.550 --> 00:14:27.560 align:start position:0% repair in the in the data structure and 00:14:27.560 --> 00:14:29.910 align:start position:0% repair in the in the data structure and it's<00:14:27.759> faster<00:14:28.639> why<00:14:28.720> it's<00:14:28.839> faster 00:14:29.910 --> 00:14:29.920 align:start position:0% it's faster why it's faster 00:14:29.920 --> 00:14:31.629 align:start position:0% it's faster why it's faster uh<00:14:30.040> because<00:14:30.240> we<00:14:30.320> are<00:14:30.440> working<00:14:30.680> on<00:14:30.880> new 00:14:31.629 --> 00:14:31.639 align:start position:0% uh because we are working on new 00:14:31.639 --> 00:14:34.790 align:start position:0% uh because we are working on new protocols<00:14:32.639> and<00:14:33.120> uh<00:14:33.279> both<00:14:33.480> for<00:14:33.920> the<00:14:34.079> pops<00:14:34.360> up 00:14:34.790 --> 00:14:34.800 align:start position:0% protocols and uh both for the pops up 00:14:34.800 --> 00:14:37.749 align:start position:0% protocols and uh both for the pops up part<00:14:35.800> and<00:14:35.959> both<00:14:36.120> for<00:14:36.240> the<00:14:36.360> sampling 00:14:37.749 --> 00:14:37.759 align:start position:0% part and both for the sampling 00:14:37.759 --> 00:14:39.870 align:start position:0% part and both for the sampling part 00:14:39.870 --> 00:14:39.880 align:start position:0% part 00:14:39.880 --> 00:14:44.590 align:start position:0% part so<00:14:40.880> and<00:14:41.279> yes<00:14:42.279> uh<00:14:42.399> is<00:14:42.519> it<00:14:42.680> more<00:14:42.920> secure<00:14:43.920> uh<00:14:44.399> so 00:14:44.590 --> 00:14:44.600 align:start position:0% so and yes uh is it more secure uh so 00:14:44.600 --> 00:14:46.389 align:start position:0% so and yes uh is it more secure uh so the<00:14:44.759> right<00:14:44.959> size<00:14:45.320> is<00:14:45.440> still<00:14:45.600> in 00:14:46.389 --> 00:14:46.399 align:start position:0% the right size is still in 00:14:46.399 --> 00:14:48.790 align:start position:0% the right size is still in resarch<00:14:47.399> uh<00:14:47.680> should<00:14:47.880> it<00:14:48.040> be<00:14:48.199> more<00:14:48.440> secure 00:14:48.790 --> 00:14:48.800 align:start position:0% resarch uh should it be more secure 00:14:48.800 --> 00:14:50.749 align:start position:0% resarch uh should it be more secure actually<00:14:49.279> when<00:14:49.440> this<00:14:49.560> is<00:14:49.680> secure<00:14:50.040> enough<00:14:50.639> uh 00:14:50.749 --> 00:14:50.759 align:start position:0% actually when this is secure enough uh 00:14:50.759 --> 00:14:52.310 align:start position:0% actually when this is secure enough uh that<00:14:50.880> we<00:14:50.959> are<00:14:51.079> changing<00:14:51.360> to<00:14:51.519> this<00:14:52.000> actually<00:14:52.240> it 00:14:52.310 --> 00:14:52.320 align:start position:0% that we are changing to this actually it 00:14:52.320 --> 00:14:54.949 align:start position:0% that we are changing to this actually it doesn't<00:14:53.320> uh<00:14:53.440> it<00:14:53.519> shouldn't<00:14:53.800> be<00:14:53.959> less<00:14:54.199> secure 00:14:54.949 --> 00:14:54.959 align:start position:0% doesn't uh it shouldn't be less secure 00:14:54.959 --> 00:14:56.430 align:start position:0% doesn't uh it shouldn't be less secure uh<00:14:55.079> that's<00:14:55.279> still<00:14:55.480> in<00:14:55.600> research<00:14:56.199> this<00:14:56.320> is 00:14:56.430 --> 00:14:56.440 align:start position:0% uh that's still in research this is 00:14:56.440 --> 00:14:59.470 align:start position:0% uh that's still in research this is still<00:14:56.680> in<00:14:56.839> specification<00:14:57.360> and<00:14:57.720> changing<00:14:58.720> so 00:14:59.470 --> 00:14:59.480 align:start position:0% still in specification and changing so 00:14:59.480 --> 00:15:01.430 align:start position:0% still in specification and changing so uh<00:14:59.720> let<00:14:59.880> me<00:15:00.040> not<00:15:00.480> do<00:15:00.600> more<00:15:00.800> comparisions 00:15:01.430 --> 00:15:01.440 align:start position:0% uh let me not do more comparisions 00:15:01.440 --> 00:15:02.949 align:start position:0% uh let me not do more comparisions because<00:15:01.720> this<00:15:01.839> will<00:15:02.040> change<00:15:02.480> and<00:15:02.639> actually 00:15:02.949 --> 00:15:02.959 align:start position:0% because this will change and actually 00:15:02.959 --> 00:15:05.069 align:start position:0% because this will change and actually this<00:15:03.120> is<00:15:03.320> still<00:15:03.519> in 00:15:05.069 --> 00:15:05.079 align:start position:0% this is still in 00:15:05.079 --> 00:15:07.710 align:start position:0% this is still in changing 00:15:07.710 --> 00:15:07.720 align:start position:0% changing 00:15:07.720 --> 00:15:14.030 align:start position:0% changing okay<00:15:08.720> sorry<00:15:09.639> uh<00:15:10.440> last 00:15:14.030 --> 00:15:14.040 align:start position:0% 00:15:14.040 --> 00:15:16.910 align:start position:0% slide<00:15:15.040> as<00:15:15.199> I<00:15:15.320> said<00:15:15.759> it<00:15:15.880> is<00:15:16.000> not<00:15:16.160> just<00:15:16.360> peas<00:15:16.759> and 00:15:16.910 --> 00:15:16.920 align:start position:0% slide as I said it is not just peas and 00:15:16.920 --> 00:15:20.829 align:start position:0% slide as I said it is not just peas and FAS<00:15:17.839> uh<00:15:17.959> but<00:15:18.079> we<00:15:18.199> can<00:15:18.360> go<00:15:18.680> beyond<00:15:19.680> and<00:15:20.279> uh<00:15:20.519> to<00:15:20.680> go 00:15:20.829 --> 00:15:20.839 align:start position:0% FAS uh but we can go beyond and uh to go 00:15:20.839 --> 00:15:23.550 align:start position:0% FAS uh but we can go beyond and uh to go beyond<00:15:21.120> we<00:15:21.240> have<00:15:21.360> to<00:15:21.480> resync<00:15:21.880> the<00:15:22.040> data<00:15:22.560> flow 00:15:23.550 --> 00:15:23.560 align:start position:0% beyond we have to resync the data flow 00:15:23.560 --> 00:15:25.350 align:start position:0% beyond we have to resync the data flow so<00:15:23.800> how<00:15:23.959> is<00:15:24.120> this<00:15:24.279> data 00:15:25.350 --> 00:15:25.360 align:start position:0% so how is this data 00:15:25.360 --> 00:15:27.990 align:start position:0% so how is this data flow<00:15:26.360> what<00:15:26.480> is<00:15:26.680> happening<00:15:27.600> what<00:15:27.720> I<00:15:27.839> was 00:15:27.990 --> 00:15:28.000 align:start position:0% flow what is happening what I was 00:15:28.000 --> 00:15:29.389 align:start position:0% flow what is happening what I was speaking<00:15:28.360> about<00:15:28.600> is<00:15:28.720> what's<00:15:29.000> happening<00:15:29.240> in<00:15:29.319> a 00:15:29.389 --> 00:15:29.399 align:start position:0% speaking about is what's happening in a 00:15:29.399 --> 00:15:32.470 align:start position:0% speaking about is what's happening in a consensus<00:15:30.120> layer<00:15:31.120> so<00:15:31.880> when<00:15:32.000> a<00:15:32.120> block<00:15:32.360> is 00:15:32.470 --> 00:15:32.480 align:start position:0% consensus layer so when a block is 00:15:32.480 --> 00:15:34.710 align:start position:0% consensus layer so when a block is generated<00:15:33.079> how<00:15:33.279> that's<00:15:33.720> distributed<00:15:34.519> but 00:15:34.710 --> 00:15:34.720 align:start position:0% generated how that's distributed but 00:15:34.720 --> 00:15:38.509 align:start position:0% generated how that's distributed but actually<00:15:35.399> these<00:15:35.560> blobs<00:15:35.880> are<00:15:36.079> coming<00:15:36.759> as 00:15:38.509 --> 00:15:38.519 align:start position:0% actually these blobs are coming as 00:15:38.519 --> 00:15:42.030 align:start position:0% actually these blobs are coming as transactions<00:15:39.519> from<00:15:39.720> the<00:15:40.079> world<00:15:41.079> okay<00:15:41.839> so 00:15:42.030 --> 00:15:42.040 align:start position:0% transactions from the world okay so 00:15:42.040 --> 00:15:44.790 align:start position:0% transactions from the world okay so let's<00:15:42.279> say<00:15:42.600> one<00:15:42.800> blob<00:15:43.040> is<00:15:43.160> coming 00:15:44.790 --> 00:15:44.800 align:start position:0% let's say one blob is coming 00:15:44.800 --> 00:15:47.710 align:start position:0% let's say one blob is coming in<00:15:45.800> and<00:15:45.920> that<00:15:46.079> goes<00:15:46.240> to<00:15:46.360> the<00:15:46.480> execution<00:15:46.959> layer 00:15:47.710 --> 00:15:47.720 align:start position:0% in and that goes to the execution layer 00:15:47.720 --> 00:15:49.790 align:start position:0% in and that goes to the execution layer and<00:15:47.839> the<00:15:48.000> execution<00:15:48.519> layer<00:15:48.880> has<00:15:49.000> the<00:15:49.120> mol<00:15:49.680> and 00:15:49.790 --> 00:15:49.800 align:start position:0% and the execution layer has the mol and 00:15:49.800 --> 00:15:52.069 align:start position:0% and the execution layer has the mol and the<00:15:49.880> mol<00:15:50.240> is<00:15:50.399> redistributing<00:15:51.199> this<00:15:51.480> sharing 00:15:52.069 --> 00:15:52.079 align:start position:0% the mol is redistributing this sharing 00:15:52.079 --> 00:15:54.949 align:start position:0% the mol is redistributing this sharing this<00:15:52.240> blob<00:15:53.079> between<00:15:53.360> nodes<00:15:54.279> actually<00:15:54.839> when 00:15:54.949 --> 00:15:54.959 align:start position:0% this blob between nodes actually when 00:15:54.959 --> 00:15:57.470 align:start position:0% this blob between nodes actually when it's<00:15:55.160> blobs<00:15:56.040> it's<00:15:56.240> not<00:15:56.399> shared<00:15:57.120> like<00:15:57.360> when 00:15:57.470 --> 00:15:57.480 align:start position:0% it's blobs it's not shared like when 00:15:57.480 --> 00:16:00.230 align:start position:0% it's blobs it's not shared like when it's<00:15:58.399> normal<00:15:59.000> for<00:15:59.160> small<00:15:59.519> transactions<00:16:00.120> when 00:16:00.230 --> 00:16:00.240 align:start position:0% it's normal for small transactions when 00:16:00.240 --> 00:16:02.350 align:start position:0% it's normal for small transactions when it's<00:16:00.360> normal<00:16:00.720> small<00:16:01.040> transactions<00:16:01.680> these 00:16:02.350 --> 00:16:02.360 align:start position:0% it's normal small transactions these 00:16:02.360 --> 00:16:05.150 align:start position:0% it's normal small transactions these transactions<00:16:02.880> are<00:16:03.120> pushed<00:16:03.480> to<00:16:04.000> others<00:16:05.000> when 00:16:05.150 --> 00:16:05.160 align:start position:0% transactions are pushed to others when 00:16:05.160 --> 00:16:07.350 align:start position:0% transactions are pushed to others when it<00:16:05.319> blobs<00:16:06.000> is<00:16:06.240> just<00:16:06.440> information<00:16:07.000> that<00:16:07.120> I<00:16:07.240> have 00:16:07.350 --> 00:16:07.360 align:start position:0% it blobs is just information that I have 00:16:07.360 --> 00:16:08.430 align:start position:0% it blobs is just information that I have this<00:16:07.480> blob<00:16:07.759> and<00:16:07.880> then<00:16:08.040> the<00:16:08.120> others<00:16:08.319> are 00:16:08.430 --> 00:16:08.440 align:start position:0% this blob and then the others are 00:16:08.440 --> 00:16:10.910 align:start position:0% this blob and then the others are pulling<00:16:09.000> it<00:16:10.000> overall 00:16:10.910 --> 00:16:10.920 align:start position:0% pulling it overall 00:16:10.920 --> 00:16:13.749 align:start position:0% pulling it overall effect<00:16:11.920> these<00:16:12.079> blobs<00:16:12.440> are<00:16:12.639> spreading<00:16:13.120> in<00:16:13.240> the 00:16:13.749 --> 00:16:13.759 align:start position:0% effect these blobs are spreading in the 00:16:13.759 --> 00:16:16.110 align:start position:0% effect these blobs are spreading in the network<00:16:14.759> let's<00:16:14.959> see<00:16:15.120> there<00:16:15.199> is<00:16:15.319> another<00:16:15.639> blob 00:16:16.110 --> 00:16:16.120 align:start position:0% network let's see there is another blob 00:16:16.120 --> 00:16:18.670 align:start position:0% network let's see there is another blob that's<00:16:16.319> spreading<00:16:16.720> also<00:16:16.959> in<00:16:17.079> the<00:16:17.519> network<00:16:18.519> and 00:16:18.670 --> 00:16:18.680 align:start position:0% that's spreading also in the network and 00:16:18.680 --> 00:16:21.550 align:start position:0% that's spreading also in the network and then<00:16:18.920> there<00:16:19.079> is<00:16:19.800> one<00:16:20.000> node<00:16:20.680> which<00:16:20.839> is 00:16:21.550 --> 00:16:21.560 align:start position:0% then there is one node which is 00:16:21.560 --> 00:16:25.030 align:start position:0% then there is one node which is selected<00:16:22.560> as<00:16:23.160> block 00:16:25.030 --> 00:16:25.040 align:start position:0% selected as block 00:16:25.040 --> 00:16:26.910 align:start position:0% selected as block proposal<00:16:26.040> takes<00:16:26.279> the 00:16:26.910 --> 00:16:26.920 align:start position:0% proposal takes the 00:16:26.920 --> 00:16:30.990 align:start position:0% proposal takes the blobs<00:16:27.920> packages<00:16:28.440> them<00:16:29.160> does<00:16:29.399> the<00:16:30.000> encoding 00:16:30.990 --> 00:16:31.000 align:start position:0% blobs packages them does the encoding 00:16:31.000 --> 00:16:33.430 align:start position:0% blobs packages them does the encoding and<00:16:31.199> then<00:16:32.079> the<00:16:32.199> encoded<00:16:32.639> version<00:16:32.920> is<00:16:33.079> getting 00:16:33.430 --> 00:16:33.440 align:start position:0% and then the encoded version is getting 00:16:33.440 --> 00:16:35.829 align:start position:0% and then the encoded version is getting spread<00:16:33.800> in<00:16:33.920> the<00:16:34.079> consensus<00:16:34.560> layer<00:16:35.480> everyone 00:16:35.829 --> 00:16:35.839 align:start position:0% spread in the consensus layer everyone 00:16:35.839 --> 00:16:38.110 align:start position:0% spread in the consensus layer everyone is<00:16:35.959> getting<00:16:36.240> his<00:16:36.560> place<00:16:37.560> I<00:16:37.639> think<00:16:37.800> you<00:16:37.920> start 00:16:38.110 --> 00:16:38.120 align:start position:0% is getting his place I think you start 00:16:38.120 --> 00:16:40.590 align:start position:0% is getting his place I think you start to<00:16:38.240> see<00:16:38.440> the<00:16:38.600> problem<00:16:39.199> right<00:16:39.959> it's<00:16:40.120> not<00:16:40.399> the 00:16:40.590 --> 00:16:40.600 align:start position:0% to see the problem right it's not the 00:16:40.600 --> 00:16:43.150 align:start position:0% to see the problem right it's not the problem<00:16:41.160> it's<00:16:41.319> an<00:16:41.720> inefficiency<00:16:42.720> we<00:16:42.880> have<00:16:43.040> an 00:16:43.150 --> 00:16:43.160 align:start position:0% problem it's an inefficiency we have an 00:16:43.160 --> 00:16:45.710 align:start position:0% problem it's an inefficiency we have an inefficiency<00:16:43.720> in<00:16:43.839> the<00:16:44.000> system<00:16:44.519> in<00:16:44.680> which<00:16:45.600> we 00:16:45.710 --> 00:16:45.720 align:start position:0% inefficiency in the system in which we 00:16:45.720 --> 00:16:48.350 align:start position:0% inefficiency in the system in which we are<00:16:45.880> Distributing<00:16:46.399> the<00:16:46.560> data<00:16:47.079> here<00:16:48.079> and<00:16:48.199> then 00:16:48.350 --> 00:16:48.360 align:start position:0% are Distributing the data here and then 00:16:48.360 --> 00:16:50.189 align:start position:0% are Distributing the data here and then we<00:16:48.480> are<00:16:48.720> actually<00:16:49.040> redistributing<00:16:49.720> the<00:16:49.880> data 00:16:50.189 --> 00:16:50.199 align:start position:0% we are actually redistributing the data 00:16:50.199 --> 00:16:52.870 align:start position:0% we are actually redistributing the data there<00:16:50.680> and<00:16:50.839> is<00:16:51.040> the<00:16:51.160> same<00:16:51.440> data<00:16:52.440> so<00:16:52.600> we<00:16:52.720> can 00:16:52.870 --> 00:16:52.880 align:start position:0% there and is the same data so we can 00:16:52.880 --> 00:16:55.030 align:start position:0% there and is the same data so we can optimize<00:16:53.279> it<00:16:53.360> a<00:16:53.440> lot<00:16:53.639> which<00:16:53.720> is<00:16:53.920> good<00:16:54.279> right<00:16:54.880> we 00:16:55.030 --> 00:16:55.040 align:start position:0% optimize it a lot which is good right we 00:16:55.040 --> 00:16:56.910 align:start position:0% optimize it a lot which is good right we need<00:16:55.360> these<00:16:55.560> optimizations<00:16:56.079> for<00:16:56.240> Mo<00:16:56.519> roow<00:16:56.800> to 00:16:56.910 --> 00:16:56.920 align:start position:0% need these optimizations for Mo roow to 00:16:56.920 --> 00:16:59.590 align:start position:0% need these optimizations for Mo roow to happen<00:16:57.639> so<00:16:58.279> uh<00:16:58.480> we<00:16:58.600> found<00:16:59.040> another<00:16:59.319> place 00:16:59.590 --> 00:16:59.600 align:start position:0% happen so uh we found another place 00:16:59.600 --> 00:17:02.870 align:start position:0% happen so uh we found another place where<00:16:59.720> we<00:16:59.880> can<00:17:00.480> save<00:17:00.720> a<00:17:01.000> lot<00:17:02.000> and<00:17:02.519> have<00:17:02.720> that 00:17:02.870 --> 00:17:02.880 align:start position:0% where we can save a lot and have that 00:17:02.880 --> 00:17:06.789 align:start position:0% where we can save a lot and have that curve<00:17:03.399> go<00:17:03.560> up<00:17:04.439> so<00:17:04.679> what<00:17:04.760> you<00:17:04.880> can<00:17:05.079> do<00:17:05.880> in<00:17:06.120> first 00:17:06.789 --> 00:17:06.799 align:start position:0% curve go up so what you can do in first 00:17:06.799 --> 00:17:09.630 align:start position:0% curve go up so what you can do in first instance<00:17:07.799> is<00:17:07.919> that<00:17:08.079> we<00:17:08.240> do<00:17:08.439> the<00:17:08.640> distribution 00:17:09.630 --> 00:17:09.640 align:start position:0% instance is that we do the distribution 00:17:09.640 --> 00:17:12.669 align:start position:0% instance is that we do the distribution up<00:17:10.039> there<00:17:11.039> but<00:17:11.199> whenever<00:17:11.520> the<00:17:11.679> node<00:17:12.480> is 00:17:12.669 --> 00:17:12.679 align:start position:0% up there but whenever the node is 00:17:12.679 --> 00:17:15.590 align:start position:0% up there but whenever the node is realizing<00:17:13.199> that<00:17:13.360> he<00:17:13.480> has<00:17:13.600> a<00:17:14.240> piece<00:17:15.240> he<00:17:15.360> would 00:17:15.590 --> 00:17:15.600 align:start position:0% realizing that he has a piece he would 00:17:15.600 --> 00:17:18.390 align:start position:0% realizing that he has a piece he would need<00:17:15.919> this<00:17:16.039> and<00:17:16.319> this<00:17:17.120> but<00:17:17.280> he<00:17:17.439> has<00:17:17.600> the<00:17:17.720> blobs 00:17:18.390 --> 00:17:18.400 align:start position:0% need this and this but he has the blobs 00:17:18.400 --> 00:17:20.630 align:start position:0% need this and this but he has the blobs he<00:17:18.559> has<00:17:18.720> the<00:17:18.880> data<00:17:19.720> he<00:17:19.839> can<00:17:20.000> just<00:17:20.199> pop<00:17:20.360> it<00:17:20.480> up 00:17:20.630 --> 00:17:20.640 align:start position:0% he has the data he can just pop it up 00:17:20.640 --> 00:17:22.590 align:start position:0% he has the data he can just pop it up from<00:17:20.919> the<00:17:21.319> execution 00:17:22.590 --> 00:17:22.600 align:start position:0% from the execution 00:17:22.600 --> 00:17:25.710 align:start position:0% from the execution client<00:17:23.600> because<00:17:23.799> the<00:17:23.959> data<00:17:24.160> is<00:17:24.280> also 00:17:25.710 --> 00:17:25.720 align:start position:0% client because the data is also 00:17:25.720 --> 00:17:27.710 align:start position:0% client because the data is also there<00:17:26.720> now<00:17:26.880> of<00:17:27.000> course<00:17:27.240> this<00:17:27.360> plot<00:17:27.600> is 00:17:27.710 --> 00:17:27.720 align:start position:0% there now of course this plot is 00:17:27.720 --> 00:17:30.430 align:start position:0% there now of course this plot is optimistic<00:17:28.600> because<00:17:29.039> I<00:17:29.160> was<00:17:29.880> putting<00:17:30.200> this 00:17:30.430 --> 00:17:30.440 align:start position:0% optimistic because I was putting this 00:17:30.440 --> 00:17:32.909 align:start position:0% optimistic because I was putting this white<00:17:30.720> blob<00:17:31.160> almost<00:17:31.559> everywhere<00:17:32.520> and<00:17:32.640> I<00:17:32.760> was 00:17:32.909 --> 00:17:32.919 align:start position:0% white blob almost everywhere and I was 00:17:32.919 --> 00:17:35.190 align:start position:0% white blob almost everywhere and I was putting<00:17:33.200> this<00:17:33.360> red<00:17:33.640> blob<00:17:34.480> almost<00:17:34.840> everywhere 00:17:35.190 --> 00:17:35.200 align:start position:0% putting this red blob almost everywhere 00:17:35.200 --> 00:17:38.669 align:start position:0% putting this red blob almost everywhere in<00:17:35.280> the<00:17:35.679> network<00:17:36.679> in<00:17:37.000> reality<00:17:38.000> you<00:17:38.160> don't<00:17:38.480> have 00:17:38.669 --> 00:17:38.679 align:start position:0% in the network in reality you don't have 00:17:38.679 --> 00:17:41.230 align:start position:0% in the network in reality you don't have every<00:17:38.960> blob<00:17:39.840> everywhere<00:17:40.840> uh<00:17:40.960> in<00:17:41.080> the 00:17:41.230 --> 00:17:41.240 align:start position:0% every blob everywhere uh in the 00:17:41.240 --> 00:17:43.470 align:start position:0% every blob everywhere uh in the execution<00:17:41.760> layer<00:17:42.400> because<00:17:42.679> if<00:17:42.880> we<00:17:43.120> we<00:17:43.240> would 00:17:43.470 --> 00:17:43.480 align:start position:0% execution layer because if we we would 00:17:43.480 --> 00:17:45.990 align:start position:0% execution layer because if we we would we<00:17:43.600> could<00:17:43.799> do<00:17:44.039> that<00:17:44.640> like<00:17:45.160> now<00:17:45.360> you<00:17:45.559> actually 00:17:45.990 --> 00:17:46.000 align:start position:0% we could do that like now you actually 00:17:46.000 --> 00:17:48.190 align:start position:0% we could do that like now you actually have<00:17:46.960> but<00:17:47.120> when<00:17:47.280> we<00:17:47.400> are 00:17:48.190 --> 00:17:48.200 align:start position:0% have but when we are 00:17:48.200 --> 00:17:50.430 align:start position:0% have but when we are scaling<00:17:49.200> we<00:17:49.320> will<00:17:49.480> not<00:17:49.640> be<00:17:49.760> able<00:17:49.960> to<00:17:50.080> do<00:17:50.240> that 00:17:50.430 --> 00:17:50.440 align:start position:0% scaling we will not be able to do that 00:17:50.440 --> 00:17:52.870 align:start position:0% scaling we will not be able to do that because<00:17:50.679> if<00:17:50.799> we<00:17:50.960> can<00:17:51.200> do<00:17:51.480> that<00:17:52.440> then<00:17:52.559> we<00:17:52.679> don't 00:17:52.870 --> 00:17:52.880 align:start position:0% because if we can do that then we don't 00:17:52.880 --> 00:17:54.870 align:start position:0% because if we can do that then we don't have<00:17:53.000> a<00:17:53.160> problem<00:17:53.720> every<00:17:54.000> note<00:17:54.240> can<00:17:54.400> handle<00:17:54.679> all 00:17:54.870 --> 00:17:54.880 align:start position:0% have a problem every note can handle all 00:17:54.880 --> 00:17:57.710 align:start position:0% have a problem every note can handle all the<00:17:55.039> data<00:17:55.360> which<00:17:55.480> is<00:17:55.919> there<00:17:56.919> we<00:17:57.080> want<00:17:57.200> to<00:17:57.360> scale 00:17:57.710 --> 00:17:57.720 align:start position:0% the data which is there we want to scale 00:17:57.720 --> 00:18:00.149 align:start position:0% the data which is there we want to scale beyond<00:17:58.200> that<00:17:59.000> so<00:17:59.159> in<00:17:59.320> reality<00:17:59.720> you<00:17:59.799> would<00:18:00.000> have 00:18:00.149 --> 00:18:00.159 align:start position:0% beyond that so in reality you would have 00:18:00.159 --> 00:18:02.070 align:start position:0% beyond that so in reality you would have some<00:18:00.360> blobs<00:18:00.799> here<00:18:01.039> some<00:18:01.240> blobs<00:18:01.679> there<00:18:01.919> some 00:18:02.070 --> 00:18:02.080 align:start position:0% some blobs here some blobs there some 00:18:02.080 --> 00:18:04.070 align:start position:0% some blobs here some blobs there some blobs<00:18:02.480> there<00:18:03.039> but<00:18:03.200> then<00:18:03.360> when<00:18:03.480> you<00:18:03.559> do<00:18:03.720> that 00:18:04.070 --> 00:18:04.080 align:start position:0% blobs there but then when you do that 00:18:04.080 --> 00:18:06.390 align:start position:0% blobs there but then when you do that distribution<00:18:05.080> data<00:18:05.320> can<00:18:05.559> pop 00:18:06.390 --> 00:18:06.400 align:start position:0% distribution data can pop 00:18:06.400 --> 00:18:08.870 align:start position:0% distribution data can pop up<00:18:07.400> and<00:18:07.880> uh<00:18:08.080> that's<00:18:08.280> one<00:18:08.400> of<00:18:08.520> the 00:18:08.870 --> 00:18:08.880 align:start position:0% up and uh that's one of the 00:18:08.880 --> 00:18:11.230 align:start position:0% up and uh that's one of the optimizations<00:18:09.880> of<00:18:10.039> course<00:18:10.520> that's<00:18:10.720> a<00:18:10.919> simple 00:18:11.230 --> 00:18:11.240 align:start position:0% optimizations of course that's a simple 00:18:11.240 --> 00:18:13.549 align:start position:0% optimizations of course that's a simple one<00:18:12.120> we<00:18:12.240> can<00:18:12.400> do<00:18:12.559> much<00:18:12.720> more<00:18:12.880> complex<00:18:13.240> ones 00:18:13.549 --> 00:18:13.559 align:start position:0% one we can do much more complex ones 00:18:13.559 --> 00:18:14.990 align:start position:0% one we can do much more complex ones where<00:18:13.720> we<00:18:13.840> have<00:18:14.039> interaction<00:18:14.559> between<00:18:14.880> the 00:18:14.990 --> 00:18:15.000 align:start position:0% where we have interaction between the 00:18:15.000 --> 00:18:18.070 align:start position:0% where we have interaction between the two<00:18:15.760> and<00:18:15.880> we<00:18:16.000> are<00:18:16.200> avoiding<00:18:17.200> some<00:18:17.400> of<00:18:17.559> these 00:18:18.070 --> 00:18:18.080 align:start position:0% two and we are avoiding some of these 00:18:18.080 --> 00:18:21.350 align:start position:0% two and we are avoiding some of these duplications<00:18:19.080> uh<00:18:19.799> but<00:18:19.919> for<00:18:20.200> that<00:18:20.360> we<00:18:20.480> have<00:18:20.600> to 00:18:21.350 --> 00:18:21.360 align:start position:0% duplications uh but for that we have to 00:18:21.360 --> 00:18:24.630 align:start position:0% duplications uh but for that we have to resync<00:18:22.360> uh<00:18:22.480> the<00:18:22.600> networking<00:18:23.120> stack<00:18:24.080> here 00:18:24.630 --> 00:18:24.640 align:start position:0% resync uh the networking stack here 00:18:24.640 --> 00:18:27.070 align:start position:0% resync uh the networking stack here which<00:18:24.760> is<00:18:25.080> that<00:18:25.280> P2P<00:18:26.120> here<00:18:26.360> which<00:18:26.480> is<00:18:26.600> using<00:18:26.840> Li 00:18:27.070 --> 00:18:27.080 align:start position:0% which is that P2P here which is using Li 00:18:27.080 --> 00:18:29.470 align:start position:0% which is that P2P here which is using Li P2P<00:18:28.039> they<00:18:28.159> are<00:18:28.280> doing<00:18:28.480> different<00:18:28.880> kinds<00:18:29.080> of 00:18:29.470 --> 00:18:29.480 align:start position:0% P2P they are doing different kinds of 00:18:29.480 --> 00:18:31.710 align:start position:0% P2P they are doing different kinds of gossiping<00:18:30.039> distribution<00:18:31.039> uh<00:18:31.200> this<00:18:31.320> is<00:18:31.440> using 00:18:31.710 --> 00:18:31.720 align:start position:0% gossiping distribution uh this is using 00:18:31.720 --> 00:18:34.190 align:start position:0% gossiping distribution uh this is using gossip<00:18:32.080> sub<00:18:32.360> this<00:18:32.480> is<00:18:32.600> using<00:18:32.880> other<00:18:33.200> protocols 00:18:34.190 --> 00:18:34.200 align:start position:0% gossip sub this is using other protocols 00:18:34.200 --> 00:18:39.190 align:start position:0% gossip sub this is using other protocols so<00:18:34.960> this<00:18:35.080> is<00:18:35.240> all<00:18:36.000> uh<00:18:36.159> this<00:18:36.280> can<00:18:36.400> all<00:18:36.520> be 00:18:39.190 --> 00:18:39.200 align:start position:0% 00:18:39.200 --> 00:18:42.830 align:start position:0% Ling<00:18:40.200> uh<00:18:40.400> but<00:18:40.679> that's<00:18:41.679> just 00:18:42.830 --> 00:18:42.840 align:start position:0% Ling uh but that's just 00:18:42.840 --> 00:18:51.149 align:start position:0% Ling uh but that's just starting<00:18:43.960> okay<00:18:44.960> thank 00:18:51.149 --> 00:18:51.159 align:start position:0% 00:18:51.159 --> 00:18:54.510 align:start position:0% you<00:18:52.159> okay<00:18:52.400> we<00:18:52.520> are<00:18:52.760> now<00:18:53.039> here<00:18:53.200> to<00:18:53.400> take<00:18:53.640> some 00:18:54.510 --> 00:18:54.520 align:start position:0% you okay we are now here to take some 00:18:54.520 --> 00:18:57.110 align:start position:0% you okay we are now here to take some Q&A<00:18:55.520> um<00:18:55.640> so<00:18:55.880> starting<00:18:56.120> from<00:18:56.280> the<00:18:56.520> top<00:18:57.000> there 00:18:57.110 --> 00:18:57.120 align:start position:0% Q&A um so starting from the top there 00:18:57.120 --> 00:18:59.830 align:start position:0% Q&A um so starting from the top there are<00:18:57.320> blob<00:18:57.679> fees<00:18:58.000> that<00:18:58.200> play<00:18:58.799> blah<00:18:59.000> blah<00:18:59.240> blah 00:18:59.830 --> 00:18:59.840 align:start position:0% are blob fees that play blah blah blah 00:18:59.840 --> 00:19:01.750 align:start position:0% are blob fees that play blah blah blah blah<00:19:00.120> blah<00:19:00.320> blah<00:19:00.640> there<00:19:00.720> are<00:19:00.880> blob<00:19:01.240> fees<00:19:01.520> that 00:19:01.750 --> 00:19:01.760 align:start position:0% blah blah blah there are blob fees that 00:19:01.760 --> 00:19:03.590 align:start position:0% blah blah blah there are blob fees that pay<00:19:01.919> for<00:19:02.120> blob<00:19:02.520> storage<00:19:03.039> but<00:19:03.240> is<00:19:03.360> this 00:19:03.590 --> 00:19:03.600 align:start position:0% pay for blob storage but is this 00:19:03.600 --> 00:19:05.909 align:start position:0% pay for blob storage but is this verified<00:19:04.200> at<00:19:04.400> all<00:19:05.000> what<00:19:05.200> happens<00:19:05.520> if<00:19:05.640> I<00:19:05.760> get 00:19:05.909 --> 00:19:05.919 align:start position:0% verified at all what happens if I get 00:19:05.919 --> 00:19:07.789 align:start position:0% verified at all what happens if I get the<00:19:06.080> fee<00:19:06.400> but<00:19:06.559> don't<00:19:07.000> actually<00:19:07.320> Store<00:19:07.679> The 00:19:07.789 --> 00:19:07.799 align:start position:0% the fee but don't actually Store The 00:19:07.799 --> 00:19:11.029 align:start position:0% the fee but don't actually Store The Blob 00:19:11.029 --> 00:19:11.039 align:start position:0% 00:19:11.039 --> 00:19:14.909 align:start position:0% data<00:19:12.039> um<00:19:12.640> okay<00:19:13.520> blob<00:19:13.840> fees<00:19:14.120> that<00:19:14.280> pay<00:19:14.480> for<00:19:14.640> BL 00:19:14.909 --> 00:19:14.919 align:start position:0% data um okay blob fees that pay for BL 00:19:14.919 --> 00:19:18.390 align:start position:0% data um okay blob fees that pay for BL storage<00:19:15.760> I<00:19:15.880> don't<00:19:16.120> know 00:19:18.390 --> 00:19:18.400 align:start position:0% storage I don't know 00:19:18.400 --> 00:19:21.789 align:start position:0% storage I don't know yeah<00:19:19.400> I'm<00:19:19.559> not<00:19:19.679> sure<00:19:19.960> what<00:19:20.400> the<00:19:21.400> question<00:19:21.640> is 00:19:21.789 --> 00:19:21.799 align:start position:0% yeah I'm not sure what the question is 00:19:21.799 --> 00:19:24.990 align:start position:0% yeah I'm not sure what the question is about<00:19:22.400> no<00:19:22.679> worry<00:19:23.679> question<00:19:24.039> answer<00:19:24.559> question 00:19:24.990 --> 00:19:25.000 align:start position:0% about no worry question answer question 00:19:25.000 --> 00:19:27.270 align:start position:0% about no worry question answer question asker<00:19:25.520> if<00:19:25.600> you<00:19:25.799> have<00:19:25.919> the<00:19:26.120> question<00:19:26.600> still 00:19:27.270 --> 00:19:27.280 align:start position:0% asker if you have the question still 00:19:27.280 --> 00:19:29.230 align:start position:0% asker if you have the question still feel<00:19:27.679> to<00:19:27.799> clarify<00:19:28.320> clarify 00:19:29.230 --> 00:19:29.240 align:start position:0% feel to clarify clarify 00:19:29.240 --> 00:19:31.070 align:start position:0% feel to clarify clarify um<00:19:29.400> but<00:19:29.520> I'll<00:19:29.640> mark<00:19:29.880> this<00:19:30.000> as<00:19:30.240> answered<00:19:30.960> what 00:19:31.070 --> 00:19:31.080 align:start position:0% um but I'll mark this as answered what 00:19:31.080 --> 00:19:32.669 align:start position:0% um but I'll mark this as answered what are<00:19:31.320> standing<00:19:31.760> problems<00:19:32.159> that<00:19:32.280> hinder 00:19:32.669 --> 00:19:32.679 align:start position:0% are standing problems that hinder 00:19:32.679 --> 00:19:34.430 align:start position:0% are standing problems that hinder current 00:19:34.430 --> 00:19:34.440 align:start position:0% current 00:19:34.440 --> 00:19:37.149 align:start position:0% current adoption<00:19:35.440> okay<00:19:35.760> so 00:19:37.149 --> 00:19:37.159 align:start position:0% adoption okay so 00:19:37.159 --> 00:19:40.590 align:start position:0% adoption okay so um<00:19:38.159> it's<00:19:38.440> just<00:19:39.039> in<00:19:39.240> implementation<00:19:39.840> so<00:19:40.039> the<00:19:40.200> p 00:19:40.590 --> 00:19:40.600 align:start position:0% um it's just in implementation so the p 00:19:40.600 --> 00:19:43.710 align:start position:0% um it's just in implementation so the p is<00:19:40.679> in<00:19:41.159> implementation<00:19:42.159> uh<00:19:42.400> it's<00:19:43.039> still 00:19:43.710 --> 00:19:43.720 align:start position:0% is in implementation uh it's still 00:19:43.720 --> 00:19:46.390 align:start position:0% is in implementation uh it's still compatibility<00:19:44.280> Problems<00:19:45.000> P<00:19:45.400> will<00:19:45.559> be<00:19:45.760> here<00:19:46.240> uh 00:19:46.390 --> 00:19:46.400 align:start position:0% compatibility Problems P will be here uh 00:19:46.400 --> 00:19:48.270 align:start position:0% compatibility Problems P will be here uh very<00:19:46.600> soon<00:19:46.960> it<00:19:47.080> will<00:19:47.240> not<00:19:47.360> be<00:19:47.480> in<00:19:47.640> pcta<00:19:48.039> but<00:19:48.159> it 00:19:48.270 --> 00:19:48.280 align:start position:0% very soon it will not be in pcta but it 00:19:48.280 --> 00:19:51.549 align:start position:0% very soon it will not be in pcta but it will<00:19:48.440> be<00:19:48.679> in<00:19:48.799> the<00:19:48.919> next<00:19:49.640> for<00:19:50.640> uh<00:19:50.760> for<00:19:50.919> FAS<00:19:51.440> we 00:19:51.549 --> 00:19:51.559 align:start position:0% will be in the next for uh for FAS we 00:19:51.559 --> 00:19:53.630 align:start position:0% will be in the next for uh for FAS we still<00:19:51.720> have<00:19:51.840> to<00:19:51.919> figure<00:19:52.200> out<00:19:52.720> uh<00:19:52.880> many<00:19:53.080> things 00:19:53.630 --> 00:19:53.640 align:start position:0% still have to figure out uh many things 00:19:53.640 --> 00:19:55.789 align:start position:0% still have to figure out uh many things so<00:19:54.320> uh<00:19:54.640> there<00:19:54.799> was<00:19:54.919> that<00:19:55.120> question<00:19:55.320> mark<00:19:55.640> on 00:19:55.789 --> 00:19:55.799 align:start position:0% so uh there was that question mark on 00:19:55.799 --> 00:19:58.350 align:start position:0% so uh there was that question mark on the<00:19:55.960> on<00:19:56.080> the<00:19:56.200> on<00:19:56.320> the<00:19:56.799> security<00:19:57.799> uh<00:19:58.039> and<00:19:58.200> we 00:19:58.350 --> 00:19:58.360 align:start position:0% the on the on the security uh and we 00:19:58.360 --> 00:20:00.430 align:start position:0% the on the on the security uh and we have<00:19:58.720> to<00:19:58.960> work<00:19:59.159> on<00:19:59.320> that<00:19:59.440> to<00:19:59.600> make<00:19:59.760> sure<00:20:00.039> that 00:20:00.430 --> 00:20:00.440 align:start position:0% have to work on that to make sure that 00:20:00.440 --> 00:20:02.789 align:start position:0% have to work on that to make sure that there<00:20:00.559> are<00:20:00.720> no<00:20:00.880> issues<00:20:01.240> with 00:20:02.789 --> 00:20:02.799 align:start position:0% there are no issues with 00:20:02.799 --> 00:20:06.070 align:start position:0% there are no issues with that<00:20:03.799> cool<00:20:04.200> why<00:20:04.320> do<00:20:04.440> we<00:20:04.640> need<00:20:05.000> 2D<00:20:05.520> eraser 00:20:06.070 --> 00:20:06.080 align:start position:0% that cool why do we need 2D eraser 00:20:06.080 --> 00:20:08.110 align:start position:0% that cool why do we need 2D eraser coding<00:20:06.679> can't<00:20:06.880> we<00:20:07.039> put<00:20:07.240> all<00:20:07.360> of<00:20:07.480> the<00:20:07.640> points<00:20:07.919> on 00:20:08.110 --> 00:20:08.120 align:start position:0% coding can't we put all of the points on 00:20:08.120 --> 00:20:11.510 align:start position:0% coding can't we put all of the points on one<00:20:08.360> polinomial<00:20:09.000> and<00:20:09.240> extend<00:20:10.039> it<00:20:11.039> so<00:20:11.280> putting 00:20:11.510 --> 00:20:11.520 align:start position:0% one polinomial and extend it so putting 00:20:11.520 --> 00:20:13.270 align:start position:0% one polinomial and extend it so putting them<00:20:11.799> on<00:20:11.960> one<00:20:12.159> point<00:20:12.440> and<00:20:12.600> extending<00:20:13.000> it<00:20:13.120> would 00:20:13.270 --> 00:20:13.280 align:start position:0% them on one point and extending it would 00:20:13.280 --> 00:20:18.669 align:start position:0% them on one point and extending it would be<00:20:13.840> uh<00:20:14.720> one<00:20:15.320> huge<00:20:16.320> uher<00:20:16.960> code<00:20:17.919> uh<00:20:18.039> one 00:20:18.669 --> 00:20:18.679 align:start position:0% be uh one huge uher code uh one 00:20:18.679 --> 00:20:21.070 align:start position:0% be uh one huge uher code uh one dimensional<00:20:19.679> and<00:20:19.880> that<00:20:20.039> would<00:20:20.240> be<00:20:20.600> very<00:20:20.880> bad 00:20:21.070 --> 00:20:21.080 align:start position:0% dimensional and that would be very bad 00:20:21.080 --> 00:20:23.310 align:start position:0% dimensional and that would be very bad for<00:20:21.320> repair<00:20:22.039> in<00:20:22.159> the<00:20:22.320> sense<00:20:22.520> that<00:20:22.760> then<00:20:22.919> you 00:20:23.310 --> 00:20:23.320 align:start position:0% for repair in the sense that then you 00:20:23.320 --> 00:20:25.909 align:start position:0% for repair in the sense that then you can<00:20:23.440> only<00:20:23.720> repair<00:20:24.080> if<00:20:24.159> you<00:20:24.280> have<00:20:24.400> all<00:20:24.600> the<00:20:24.919> data 00:20:25.909 --> 00:20:25.919 align:start position:0% can only repair if you have all the data 00:20:25.919 --> 00:20:29.630 align:start position:0% can only repair if you have all the data and<00:20:26.120> that<00:20:26.400> just<00:20:27.039> uh<00:20:28.039> means<00:20:28.440> that 00:20:29.630 --> 00:20:29.640 align:start position:0% and that just uh means that 00:20:29.640 --> 00:20:31.590 align:start position:0% and that just uh means that uh<00:20:29.760> you<00:20:29.919> have<00:20:30.120> difficulties<00:20:30.640> repairing<00:20:31.480> the 00:20:31.590 --> 00:20:31.600 align:start position:0% uh you have difficulties repairing the 00:20:31.600 --> 00:20:34.990 align:start position:0% uh you have difficulties repairing the 2D<00:20:32.360> has<00:20:32.559> this<00:20:32.799> advantage<00:20:33.200> of<00:20:33.400> having<00:20:33.679> this<00:20:34.559> Cod 00:20:34.990 --> 00:20:35.000 align:start position:0% 2D has this advantage of having this Cod 00:20:35.000 --> 00:20:38.149 align:start position:0% 2D has this advantage of having this Cod local<00:20:35.679> repair<00:20:36.320> property<00:20:37.120> so<00:20:37.400> that<00:20:37.679> the<00:20:37.919> code 00:20:38.149 --> 00:20:38.159 align:start position:0% local repair property so that the code 00:20:38.159 --> 00:20:41.270 align:start position:0% local repair property so that the code distance<00:20:38.480> is<00:20:38.600> small<00:20:39.400> and<00:20:39.559> you<00:20:39.720> can<00:20:40.360> uh<00:20:40.960> you<00:20:41.080> can 00:20:41.270 --> 00:20:41.280 align:start position:0% distance is small and you can uh you can 00:20:41.280 --> 00:20:43.149 align:start position:0% distance is small and you can uh you can repair<00:20:41.760> pieces<00:20:42.159> so<00:20:42.320> you<00:20:42.400> can<00:20:42.559> repair<00:20:42.840> a<00:20:42.919> single 00:20:43.149 --> 00:20:43.159 align:start position:0% repair pieces so you can repair a single 00:20:43.159 --> 00:20:45.070 align:start position:0% repair pieces so you can repair a single column<00:20:43.440> you<00:20:43.520> can<00:20:43.640> repair<00:20:43.919> a<00:20:44.000> single<00:20:44.280> row<00:20:44.880> and 00:20:45.070 --> 00:20:45.080 align:start position:0% column you can repair a single row and 00:20:45.080 --> 00:20:47.310 align:start position:0% column you can repair a single row and that<00:20:45.320> gives<00:20:45.600> notes<00:20:46.159> the<00:20:46.320> possibility<00:20:46.760> to<00:20:47.000> rep 00:20:47.310 --> 00:20:47.320 align:start position:0% that gives notes the possibility to rep 00:20:47.320 --> 00:20:49.270 align:start position:0% that gives notes the possibility to rep start<00:20:47.600> repairing<00:20:48.080> and<00:20:48.280> contributing<00:20:49.000> even 00:20:49.270 --> 00:20:49.280 align:start position:0% start repairing and contributing even 00:20:49.280 --> 00:20:51.470 align:start position:0% start repairing and contributing even before<00:20:49.600> getting<00:20:49.840> the<00:20:49.960> food 00:20:51.470 --> 00:20:51.480 align:start position:0% before getting the food 00:20:51.480 --> 00:20:54.549 align:start position:0% before getting the food data<00:20:52.480> if<00:20:52.679> full<00:20:52.960> dos<00:20:53.240> is<00:20:53.480> way<00:20:53.720> better<00:20:54.080> than<00:20:54.280> pure 00:20:54.549 --> 00:20:54.559 align:start position:0% data if full dos is way better than pure 00:20:54.559 --> 00:20:56.630 align:start position:0% data if full dos is way better than pure dos<00:20:55.120> why<00:20:55.320> not<00:20:55.559> choose<00:20:55.840> to<00:20:56.000> implement<00:20:56.400> it<00:20:56.520> in 00:20:56.630 --> 00:20:56.640 align:start position:0% dos why not choose to implement it in 00:20:56.640 --> 00:21:00.390 align:start position:0% dos why not choose to implement it in the<00:20:56.799> first<00:20:57.440> place<00:20:58.440> uh<00:20:58.760> uh<00:20:58.919> so<00:20:59.120> as<00:20:59.240> I<00:20:59.360> said<00:20:59.960> uh 00:21:00.390 --> 00:21:00.400 align:start position:0% the first place uh uh so as I said uh 00:21:00.400 --> 00:21:03.470 align:start position:0% the first place uh uh so as I said uh buas<00:21:00.840> itself<00:21:01.120> is<00:21:01.240> changing<00:21:01.919> we<00:21:02.240> have<00:21:03.240> we<00:21:03.320> were 00:21:03.470 --> 00:21:03.480 align:start position:0% buas itself is changing we have we were 00:21:03.480 --> 00:21:05.830 align:start position:0% buas itself is changing we have we were thinking<00:21:03.760> of<00:21:03.919> techniques<00:21:04.240> for<00:21:04.360> FAS<00:21:05.280> then<00:21:05.600> we 00:21:05.830 --> 00:21:05.840 align:start position:0% thinking of techniques for FAS then we 00:21:05.840 --> 00:21:07.149 align:start position:0% thinking of techniques for FAS then we realized<00:21:06.280> that<00:21:06.360> they<00:21:06.480> are<00:21:06.640> actually<00:21:06.840> applying 00:21:07.149 --> 00:21:07.159 align:start position:0% realized that they are actually applying 00:21:07.159 --> 00:21:10.110 align:start position:0% realized that they are actually applying to<00:21:07.280> pilas<00:21:08.080> and<00:21:08.200> then<00:21:08.360> they<00:21:08.480> are<00:21:08.640> part<00:21:08.840> of<00:21:09.120> pilas 00:21:10.110 --> 00:21:10.120 align:start position:0% to pilas and then they are part of pilas 00:21:10.120 --> 00:21:12.310 align:start position:0% to pilas and then they are part of pilas uh<00:21:10.240> we're<00:21:10.400> still<00:21:10.600> changing<00:21:11.000> that<00:21:11.600> uh<00:21:11.760> FAS<00:21:12.200> is 00:21:12.310 --> 00:21:12.320 align:start position:0% uh we're still changing that uh FAS is 00:21:12.320 --> 00:21:15.190 align:start position:0% uh we're still changing that uh FAS is still<00:21:12.520> much<00:21:12.640> more<00:21:12.960> resurge<00:21:13.960> uh<00:21:14.120> it's<00:21:14.240> a<00:21:14.400> simple 00:21:15.190 --> 00:21:15.200 align:start position:0% still much more resurge uh it's a simple 00:21:15.200 --> 00:21:17.950 align:start position:0% still much more resurge uh it's a simple fact<00:21:15.520> of<00:21:15.880> life<00:21:16.240> that<00:21:16.799> uh<00:21:17.400> there's<00:21:17.640> too<00:21:17.799> much 00:21:17.950 --> 00:21:17.960 align:start position:0% fact of life that uh there's too much 00:21:17.960 --> 00:21:20.269 align:start position:0% fact of life that uh there's too much pieces<00:21:18.320> still<00:21:18.480> moving<00:21:18.760> in<00:21:18.919> F<00:21:19.200> us<00:21:19.880> uh<00:21:20.080> to 00:21:20.269 --> 00:21:20.279 align:start position:0% pieces still moving in F us uh to 00:21:20.279 --> 00:21:21.350 align:start position:0% pieces still moving in F us uh to implement 00:21:21.350 --> 00:21:21.360 align:start position:0% implement 00:21:21.360 --> 00:21:24.549 align:start position:0% implement that<00:21:22.360> Co<00:21:22.679> and<00:21:22.799> to<00:21:22.960> cap<00:21:23.159> us<00:21:23.320> off<00:21:23.600> it<00:21:23.720> seems<00:21:23.960> FS 00:21:24.549 --> 00:21:24.559 align:start position:0% that Co and to cap us off it seems FS 00:21:24.559 --> 00:21:27.029 align:start position:0% that Co and to cap us off it seems FS approach<00:21:25.000> are<00:21:25.279> much<00:21:25.640> much<00:21:25.880> better<00:21:26.120> than<00:21:26.279> pios 00:21:27.029 --> 00:21:27.039 align:start position:0% approach are much much better than pios 00:21:27.039 --> 00:21:29.549 align:start position:0% approach are much much better than pios should<00:21:27.279> we<00:21:27.440> Skip<00:21:27.720> pios<00:21:28.159> and<00:21:28.240> imp<00:21:28.760> the<00:21:28.840> FAS<00:21:29.440> is 00:21:29.549 --> 00:21:29.559 align:start position:0% should we Skip pios and imp the FAS is 00:21:29.559 --> 00:21:33.549 align:start position:0% should we Skip pios and imp the FAS is there<00:21:29.760> any<00:21:30.000> other 00:21:33.549 --> 00:21:33.559 align:start position:0% 00:21:33.559 --> 00:21:37.149 align:start position:0% tradeoff<00:21:34.559> I<00:21:35.320> so<00:21:35.720> FAS<00:21:36.279> is<00:21:36.400> using<00:21:36.760> many<00:21:36.960> things 00:21:37.149 --> 00:21:37.159 align:start position:0% tradeoff I so FAS is using many things 00:21:37.159 --> 00:21:41.510 align:start position:0% tradeoff I so FAS is using many things that<00:21:37.360> pus<00:21:38.320> uh<00:21:38.440> does<00:21:38.840> so<00:21:39.240> skipping<00:21:39.880> is<00:21:40.279> is<00:21:40.480> not<00:21:40.799> a 00:21:41.510 --> 00:21:41.520 align:start position:0% that pus uh does so skipping is is not a 00:21:41.520 --> 00:21:44.430 align:start position:0% that pus uh does so skipping is is not a a<00:21:41.679> direct<00:21:42.039> Skip<00:21:42.440> it's<00:21:42.600> not<00:21:43.080> fully<00:21:43.520> different 00:21:44.430 --> 00:21:44.440 align:start position:0% a direct Skip it's not fully different 00:21:44.440 --> 00:21:47.710 align:start position:0% a direct Skip it's not fully different uh<00:21:45.200> it's<00:21:45.679> it's<00:21:46.000> giving<00:21:46.240> the<00:21:46.320> 2D<00:21:46.880> C<00:21:47.080> so<00:21:47.400> it<00:21:47.520> has 00:21:47.710 --> 00:21:47.720 align:start position:0% uh it's it's giving the 2D C so it has 00:21:47.720 --> 00:21:50.430 align:start position:0% uh it's it's giving the 2D C so it has advantages<00:21:48.320> but<00:21:48.440> it<00:21:48.600> has<00:21:48.720> also<00:21:49.440> complexities 00:21:50.430 --> 00:21:50.440 align:start position:0% advantages but it has also complexities 00:21:50.440 --> 00:21:53.269 align:start position:0% advantages but it has also complexities uh<00:21:50.559> whether<00:21:50.840> we<00:21:51.080> keep<00:21:51.400> or<00:21:51.600> not<00:21:51.880> is<00:21:52.760> uh<00:21:53.120> might 00:21:53.269 --> 00:21:53.279 align:start position:0% uh whether we keep or not is uh might 00:21:53.279 --> 00:21:57.029 align:start position:0% uh whether we keep or not is uh might save<00:21:53.600> something<00:21:53.880> on<00:21:54.039> the<00:21:54.520> implementation 00:21:57.029 --> 00:21:57.039 align:start position:0% save something on the implementation 00:21:57.039 --> 00:22:00.470 align:start position:0% save something on the implementation uh<00:21:58.039> when<00:21:58.279> we<00:21:58.679> introducing<00:21:59.320> it<00:21:59.480> it<00:21:59.640> might<00:21:59.919> also 00:22:00.470 --> 00:22:00.480 align:start position:0% uh when we introducing it it might also 00:22:00.480 --> 00:22:02.390 align:start position:0% uh when we introducing it it might also skip<00:22:00.840> something<00:22:01.360> but<00:22:01.520> we<00:22:01.600> are<00:22:01.760> losing<00:22:02.080> also 00:22:02.390 --> 00:22:02.400 align:start position:0% skip something but we are losing also 00:22:02.400 --> 00:22:05.269 align:start position:0% skip something but we are losing also the<00:22:02.559> graduality<00:22:03.440> so<00:22:03.880> overall<00:22:04.720> I'm<00:22:04.880> not<00:22:05.039> sure 00:22:05.269 --> 00:22:05.279 align:start position:0% the graduality so overall I'm not sure 00:22:05.279 --> 00:22:08.070 align:start position:0% the graduality so overall I'm not sure it's<00:22:05.520> good<00:22:05.760> to<00:22:05.960> skip<00:22:06.760> uh<00:22:06.960> but<00:22:07.159> we<00:22:07.279> can<00:22:07.880> uh<00:22:07.960> we 00:22:08.070 --> 00:22:08.080 align:start position:0% it's good to skip uh but we can uh we 00:22:08.080 --> 00:22:10.029 align:start position:0% it's good to skip uh but we can uh we can<00:22:08.200> think<00:22:08.440> of<00:22:08.559> it<00:22:08.799> once<00:22:09.039> food<00:22:09.279> us<00:22:09.440> is<00:22:09.559> fully 00:22:10.029 --> 00:22:10.039 align:start position:0% can think of it once food us is fully 00:22:10.039 --> 00:22:13.909 align:start position:0% can think of it once food us is fully evaluated<00:22:11.039> what<00:22:11.200> are<00:22:11.520> open<00:22:11.840> research 00:22:13.909 --> 00:22:13.919 align:start position:0% evaluated what are open research 00:22:13.919 --> 00:22:16.310 align:start position:0% evaluated what are open research questions<00:22:14.919> so<00:22:15.520> uh<00:22:15.640> the<00:22:15.760> open<00:22:15.960> research 00:22:16.310 --> 00:22:16.320 align:start position:0% questions so uh the open research 00:22:16.320 --> 00:22:18.390 align:start position:0% questions so uh the open research questions<00:22:16.720> is<00:22:17.159> uh<00:22:17.279> so<00:22:17.480> the<00:22:17.600> last<00:22:17.799> slide<00:22:18.159> was 00:22:18.390 --> 00:22:18.400 align:start position:0% questions is uh so the last slide was 00:22:18.400 --> 00:22:21.310 align:start position:0% questions is uh so the last slide was was<00:22:18.679> was<00:22:18.799> fully<00:22:19.080> open<00:22:19.919> uh<00:22:20.080> research<00:22:20.480> question 00:22:21.310 --> 00:22:21.320 align:start position:0% was was fully open uh research question 00:22:21.320 --> 00:22:25.909 align:start position:0% was was fully open uh research question or<00:22:21.520> everything<00:22:21.840> around<00:22:22.279> that<00:22:23.279> uh<00:22:24.039> the<00:22:25.039> on<00:22:25.440> on 00:22:25.909 --> 00:22:25.919 align:start position:0% or everything around that uh the on on 00:22:25.919 --> 00:22:28.669 align:start position:0% or everything around that uh the on on FAS<00:22:26.919> uh<00:22:27.360> there<00:22:27.480> are<00:22:27.880> several<00:22:28.240> questions 00:22:28.669 --> 00:22:28.679 align:start position:0% FAS uh there are several questions 00:22:28.679 --> 00:22:30.750 align:start position:0% FAS uh there are several questions around<00:22:28.880> the<00:22:29.080> sampling<00:22:30.080> how<00:22:30.200> we<00:22:30.320> can<00:22:30.440> do<00:22:30.600> the 00:22:30.750 --> 00:22:30.760 align:start position:0% around the sampling how we can do the 00:22:30.760 --> 00:22:33.470 align:start position:0% around the sampling how we can do the sampling<00:22:31.760> safely<00:22:32.480> in<00:22:32.600> the<00:22:32.720> sense<00:22:32.960> that<00:22:33.080> c 00:22:33.470 --> 00:22:33.480 align:start position:0% sampling safely in the sense that c 00:22:33.480 --> 00:22:34.909 align:start position:0% sampling safely in the sense that c nodes<00:22:33.760> cannot<00:22:34.039> attack<00:22:34.279> the<00:22:34.400> system<00:22:34.720> for 00:22:34.909 --> 00:22:34.919 align:start position:0% nodes cannot attack the system for 00:22:34.919 --> 00:22:38.190 align:start position:0% nodes cannot attack the system for example<00:22:35.919> so<00:22:36.440> uh<00:22:36.840> there<00:22:36.960> are<00:22:37.159> still<00:22:37.760> things<00:22:38.039> to 00:22:38.190 --> 00:22:38.200 align:start position:0% example so uh there are still things to 00:22:38.200 --> 00:22:41.510 align:start position:0% example so uh there are still things to clarify<00:22:39.080> there<00:22:40.080> uh<00:22:40.279> especially<00:22:40.720> attacks 00:22:41.510 --> 00:22:41.520 align:start position:0% clarify there uh especially attacks 00:22:41.520 --> 00:22:43.789 align:start position:0% clarify there uh especially attacks Network<00:22:41.960> partitioning<00:22:42.880> and<00:22:43.080> other<00:22:43.320> things 00:22:43.789 --> 00:22:43.799 align:start position:0% Network partitioning and other things 00:22:43.799 --> 00:22:46.310 align:start position:0% Network partitioning and other things how<00:22:44.000> they<00:22:44.200> affect 00:22:46.310 --> 00:22:46.320 align:start position:0% how they affect 00:22:46.320 --> 00:22:48.310 align:start position:0% how they affect security<00:22:47.320> there's<00:22:47.480> some<00:22:47.679> fighting<00:22:47.960> and<00:22:48.159> up 00:22:48.310 --> 00:22:48.320 align:start position:0% security there's some fighting and up 00:22:48.320 --> 00:22:50.630 align:start position:0% security there's some fighting and up voting<00:22:48.640> going<00:22:48.799> on<00:22:49.039> this<00:22:49.120> is<00:22:49.279> fun<00:22:49.799> if<00:22:50.000> 2D<00:22:50.440> is 00:22:50.630 --> 00:22:50.640 align:start position:0% voting going on this is fun if 2D is 00:22:50.640 --> 00:22:54.430 align:start position:0% voting going on this is fun if 2D is better<00:22:51.120> would<00:22:51.320> there<00:22:51.520> be<00:22:51.760> any<00:22:52.039> benefits<00:22:52.600> of<00:22:53.200> 3D 00:22:54.430 --> 00:22:54.440 align:start position:0% better would there be any benefits of 3D 00:22:54.440 --> 00:22:56.710 align:start position:0% better would there be any benefits of 3D absolutely<00:22:55.440> uh<00:22:55.559> multi-dimensional<00:22:56.320> encoding 00:22:56.710 --> 00:22:56.720 align:start position:0% absolutely uh multi-dimensional encoding 00:22:56.720 --> 00:23:00.669 align:start position:0% absolutely uh multi-dimensional encoding is<00:22:56.880> fun<00:22:57.720> uh<00:22:58.559> but<00:22:58.720> no<00:22:59.200> actually<00:22:59.480> not<00:22:59.919> so<00:23:00.279> we<00:23:00.480> just 00:23:00.669 --> 00:23:00.679 align:start position:0% is fun uh but no actually not so we just 00:23:00.679 --> 00:23:03.190 align:start position:0% is fun uh but no actually not so we just need<00:23:01.080> the<00:23:01.520> uh<00:23:02.159> the<00:23:02.240> local<00:23:02.600> reparability 00:23:03.190 --> 00:23:03.200 align:start position:0% need the uh the local reparability 00:23:03.200 --> 00:23:05.470 align:start position:0% need the uh the local reparability property<00:23:04.039> and<00:23:04.200> we<00:23:04.440> have<00:23:04.760> enough<00:23:05.039> of<00:23:05.200> that<00:23:05.360> in 00:23:05.470 --> 00:23:05.480 align:start position:0% property and we have enough of that in 00:23:05.480 --> 00:23:09.870 align:start position:0% property and we have enough of that in 2D<00:23:06.200> 3D<00:23:06.679> would<00:23:07.279> not<00:23:08.279> contribute<00:23:08.799> to<00:23:09.000> that<00:23:09.720> uh 00:23:09.870 --> 00:23:09.880 align:start position:0% 2D 3D would not contribute to that uh 00:23:09.880 --> 00:23:11.230 align:start position:0% 2D 3D would not contribute to that uh too 00:23:11.230 --> 00:23:11.240 align:start position:0% too 00:23:11.240 --> 00:23:14.549 align:start position:0% too much<00:23:12.240> uh<00:23:12.400> can<00:23:12.559> fust<00:23:13.159> be<00:23:13.440> implemented 00:23:14.549 --> 00:23:14.559 align:start position:0% much uh can fust be implemented 00:23:14.559 --> 00:23:17.350 align:start position:0% much uh can fust be implemented progressively<00:23:15.559> I<00:23:15.799> think<00:23:16.120> so<00:23:16.799> but<00:23:16.960> we<00:23:17.080> didn't 00:23:17.350 --> 00:23:17.360 align:start position:0% progressively I think so but we didn't 00:23:17.360 --> 00:23:20.230 align:start position:0% progressively I think so but we didn't Define<00:23:18.000> plugless<00:23:19.000> so<00:23:19.600> uh<00:23:19.720> it's<00:23:19.880> something<00:23:20.120> to 00:23:20.230 --> 00:23:20.240 align:start position:0% Define plugless so uh it's something to 00:23:20.240 --> 00:23:23.230 align:start position:0% Define plugless so uh it's something to think<00:23:20.480> of<00:23:21.400> but<00:23:21.720> uh<00:23:21.880> but<00:23:22.000> we<00:23:22.080> didn't<00:23:22.279> Define<00:23:22.600> it 00:23:23.230 --> 00:23:23.240 align:start position:0% think of but uh but we didn't Define it 00:23:23.240 --> 00:23:27.110 align:start position:0% think of but uh but we didn't Define it yet<00:23:24.240> cool<00:23:25.039> then<00:23:25.279> I<00:23:25.480> think<00:23:26.480> this<00:23:26.720> question<00:23:26.960> was 00:23:27.110 --> 00:23:27.120 align:start position:0% yet cool then I think this question was 00:23:27.120 --> 00:23:28.230 align:start position:0% yet cool then I think this question was already<00:23:27.440> answered<00:23:27.720> I<00:23:27.799> think<00:23:27.840> you<00:23:27.919> already<00:23:28.080> had 00:23:28.230 --> 00:23:28.240 align:start position:0% already answered I think you already had 00:23:28.240 --> 00:23:29.950 align:start position:0% already answered I think you already had that<00:23:28.679> right<00:23:28.960> yeah<00:23:29.200> unless<00:23:29.480> someone's 00:23:29.950 --> 00:23:29.960 align:start position:0% that right yeah unless someone's 00:23:29.960 --> 00:23:31.630 align:start position:0% that right yeah unless someone's aggressively<00:23:30.679> or<00:23:30.840> I<00:23:30.960> just<00:23:31.039> forgot<00:23:31.279> to<00:23:31.400> mark 00:23:31.630 --> 00:23:31.640 align:start position:0% aggressively or I just forgot to mark 00:23:31.640 --> 00:23:34.350 align:start position:0% aggressively or I just forgot to mark his<00:23:32.000> answered<00:23:33.000> um<00:23:33.440> cool<00:23:33.640> so<00:23:33.760> we<00:23:33.880> have<00:23:34.000> a<00:23:34.120> minute 00:23:34.350 --> 00:23:34.360 align:start position:0% his answered um cool so we have a minute 00:23:34.360 --> 00:23:36.590 align:start position:0% his answered um cool so we have a minute and<00:23:34.559> 34<00:23:35.080> seconds<00:23:35.559> left<00:23:36.120> I<00:23:36.279> was<00:23:36.360> actually<00:23:36.440> she's 00:23:36.590 --> 00:23:36.600 align:start position:0% and 34 seconds left I was actually she's 00:23:36.600 --> 00:23:39.470 align:start position:0% and 34 seconds left I was actually she's spending<00:23:36.960> time<00:23:37.640> yeah<00:23:37.880> no<00:23:38.480> but<00:23:38.880> so<00:23:39.240> I<00:23:39.320> guess 00:23:39.470 --> 00:23:39.480 align:start position:0% spending time yeah no but so I guess 00:23:39.480 --> 00:23:41.950 align:start position:0% spending time yeah no but so I guess there's<00:23:39.720> one<00:23:39.919> piece<00:23:40.159> to<00:23:40.360> this<00:23:40.840> question<00:23:41.840> you 00:23:41.950 --> 00:23:41.960 align:start position:0% there's one piece to this question you 00:23:41.960 --> 00:23:44.029 align:start position:0% there's one piece to this question you can<00:23:42.120> give<00:23:42.240> him<00:23:42.440> feedback<00:23:42.799> on<00:23:42.919> the<00:23:43.080> QR<00:23:43.440> code<00:23:43.799> so 00:23:44.029 --> 00:23:44.039 align:start position:0% can give him feedback on the QR code so 00:23:44.039 --> 00:23:45.710 align:start position:0% can give him feedback on the QR code so we'll<00:23:44.240> give<00:23:44.360> you<00:23:44.559> some<00:23:44.799> time<00:23:45.039> to<00:23:45.240> tell<00:23:45.400> him<00:23:45.559> how 00:23:45.710 --> 00:23:45.720 align:start position:0% we'll give you some time to tell him how 00:23:45.720 --> 00:23:48.029 align:start position:0% we'll give you some time to tell him how great<00:23:45.880> he<00:23:46.039> did<00:23:46.559> collect<00:23:46.840> a<00:23:47.000> card<00:23:47.559> um<00:23:47.679> but<00:23:47.840> other 00:23:48.029 --> 00:23:48.039 align:start position:0% great he did collect a card um but other 00:23:48.039 --> 00:23:49.870 align:start position:0% great he did collect a card um but other than<00:23:48.240> that<00:23:48.440> I<00:23:48.480> think<00:23:48.640> our<00:23:48.880> next 00:23:49.870 --> 00:23:49.880 align:start position:0% than that I think our next 00:23:49.880 --> 00:23:53.919 align:start position:0% than that I think our next session<00:23:50.880> um<00:23:51.120> well<00:23:51.279> I<00:23:51.400> guess