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:10.629 align:start position:0% [Music] 00:00:10.629 --> 00:00:10.639 align:start position:0% [Music] 00:00:10.639 --> 00:00:13.910 align:start position:0% [Music] hi<00:00:11.160> everyone<00:00:11.759> thank<00:00:12.000> you<00:00:13.000> um<00:00:13.320> my<00:00:13.440> name<00:00:13.559> is<00:00:13.679> D 00:00:13.910 --> 00:00:13.920 align:start position:0% hi everyone thank you um my name is D 00:00:13.920 --> 00:00:17.230 align:start position:0% hi everyone thank you um my name is D kopic<00:00:14.519> and<00:00:14.759> I<00:00:14.960> worked<00:00:15.360> on<00:00:15.719> Shadow<00:00:16.119> nworting 00:00:17.230 --> 00:00:17.240 align:start position:0% kopic and I worked on Shadow nworting 00:00:17.240 --> 00:00:21.750 align:start position:0% kopic and I worked on Shadow nworting relations<00:00:18.240> yeah 00:00:21.750 --> 00:00:21.760 align:start position:0% 00:00:21.760 --> 00:00:38.670 align:start position:0% um<00:00:22.760> the<00:00:22.920> usual<00:00:23.199> clickup<00:00:23.680> problems 00:00:38.670 --> 00:00:38.680 align:start position:0% 00:00:38.680 --> 00:00:43.029 align:start position:0% thanks<00:00:39.680> um<00:00:40.440> yeah<00:00:40.920> so<00:00:41.480> in<00:00:41.640> my<00:00:41.840> opinion<00:00:42.640> Network 00:00:43.029 --> 00:00:43.039 align:start position:0% thanks um yeah so in my opinion Network 00:00:43.039 --> 00:00:46.430 align:start position:0% thanks um yeah so in my opinion Network donations<00:00:43.520> are<00:00:43.680> awesome<00:00:44.360> because<00:00:45.239> they<00:00:45.480> allow 00:00:46.430 --> 00:00:46.440 align:start position:0% donations are awesome because they allow 00:00:46.440 --> 00:00:48.630 align:start position:0% donations are awesome because they allow testing<00:00:46.760> changes<00:00:47.280> without<00:00:47.600> rolling<00:00:47.960> out<00:00:48.199> to 00:00:48.630 --> 00:00:48.640 align:start position:0% testing changes without rolling out to 00:00:48.640 --> 00:00:50.950 align:start position:0% testing changes without rolling out to public<00:00:48.920> death<00:00:49.199> Nets<00:00:49.640> or<00:00:50.039> even<00:00:50.280> test<00:00:50.520> Nets 00:00:50.950 --> 00:00:50.960 align:start position:0% public death Nets or even test Nets 00:00:50.960 --> 00:00:52.709 align:start position:0% public death Nets or even test Nets which<00:00:51.280> is<00:00:51.399> slow<00:00:51.680> and<00:00:51.840> takes<00:00:52.079> synchronization 00:00:52.709 --> 00:00:52.719 align:start position:0% which is slow and takes synchronization 00:00:52.719 --> 00:00:57.029 align:start position:0% which is slow and takes synchronization and<00:00:52.920> time<00:00:53.800> and<00:00:54.879> um<00:00:55.879> small<00:00:56.320> local<00:00:56.640> definites 00:00:57.029 --> 00:00:57.039 align:start position:0% and time and um small local definites 00:00:57.039 --> 00:00:59.270 align:start position:0% and time and um small local definites are<00:00:57.239> possible<00:00:57.680> but<00:00:57.960> with<00:00:58.440> um<00:00:58.760> a<00:00:58.920> software 00:00:59.270 --> 00:00:59.280 align:start position:0% are possible but with um a software 00:00:59.280 --> 00:01:02.310 align:start position:0% are possible but with um a software called<00:00:59.480> shadow<00:01:00.280> we<00:01:00.480> can<00:01:01.160> actually<00:01:01.640> run<00:01:02.000> huge 00:01:02.310 --> 00:01:02.320 align:start position:0% called shadow we can actually run huge 00:01:02.320 --> 00:01:05.270 align:start position:0% called shadow we can actually run huge simulations<00:01:03.079> with<00:01:03.399> thousands<00:01:04.199> of<00:01:04.360> notes<00:01:05.080> and 00:01:05.270 --> 00:01:05.280 align:start position:0% simulations with thousands of notes and 00:01:05.280 --> 00:01:09.870 align:start position:0% simulations with thousands of notes and also<00:01:05.640> with<00:01:05.880> actual<00:01:06.200> clients<00:01:06.680> like<00:01:06.920> not<00:01:07.400> any<00:01:08.880> um 00:01:09.870 --> 00:01:09.880 align:start position:0% also with actual clients like not any um 00:01:09.880 --> 00:01:13.149 align:start position:0% also with actual clients like not any um like<00:01:10.520> code<00:01:10.840> written<00:01:11.320> dedicated<00:01:11.960> to<00:01:12.200> the<00:01:12.680> um 00:01:13.149 --> 00:01:13.159 align:start position:0% like code written dedicated to the um 00:01:13.159 --> 00:01:16.270 align:start position:0% like code written dedicated to the um simulations<00:01:14.159> so<00:01:14.840> I<00:01:15.520> kind<00:01:15.720> of<00:01:15.960> had<00:01:16.080> a 00:01:16.270 --> 00:01:16.280 align:start position:0% simulations so I kind of had a 00:01:16.280 --> 00:01:18.429 align:start position:0% simulations so I kind of had a three-phase<00:01:16.880> project<00:01:17.600> first<00:01:17.920> I<00:01:18.040> wanted<00:01:18.280> to 00:01:18.429 --> 00:01:18.439 align:start position:0% three-phase project first I wanted to 00:01:18.439 --> 00:01:20.230 align:start position:0% three-phase project first I wanted to prepare<00:01:18.759> a<00:01:18.840> tool<00:01:19.119> that<00:01:19.280> allowed<00:01:19.560> me<00:01:19.680> to<00:01:19.840> easily 00:01:20.230 --> 00:01:20.240 align:start position:0% prepare a tool that allowed me to easily 00:01:20.240 --> 00:01:22.429 align:start position:0% prepare a tool that allowed me to easily set<00:01:20.439> up<00:01:20.720> these<00:01:20.880> Shadow<00:01:21.240> simulations<00:01:21.960> with 00:01:22.429 --> 00:01:22.439 align:start position:0% set up these Shadow simulations with 00:01:22.439 --> 00:01:26.390 align:start position:0% set up these Shadow simulations with etherum<00:01:22.920> clients<00:01:24.119> um<00:01:25.119> that<00:01:25.400> is<00:01:25.720> easier<00:01:26.119> said 00:01:26.390 --> 00:01:26.400 align:start position:0% etherum clients um that is easier said 00:01:26.400 --> 00:01:28.749 align:start position:0% etherum clients um that is easier said than<00:01:26.600> done<00:01:27.040> because<00:01:27.680> Shadow<00:01:28.200> can<00:01:28.360> be<00:01:28.520> kind<00:01:28.640> of 00:01:28.749 --> 00:01:28.759 align:start position:0% than done because Shadow can be kind of 00:01:28.759 --> 00:01:33.030 align:start position:0% than done because Shadow can be kind of finicky<00:01:29.439> sometimes<00:01:30.079> so<00:01:30.880> it<00:01:31.119> it<00:01:31.240> took<00:01:31.400> a<00:01:32.040> while 00:01:33.030 --> 00:01:33.040 align:start position:0% finicky sometimes so it it took a while 00:01:33.040 --> 00:01:36.710 align:start position:0% finicky sometimes so it it took a while um<00:01:33.720> yeah<00:01:34.240> in<00:01:34.399> the<00:01:34.560> second<00:01:35.079> phase<00:01:36.079> um<00:01:36.360> I<00:01:36.439> want<00:01:36.640> to 00:01:36.710 --> 00:01:36.720 align:start position:0% um yeah in the second phase um I want to 00:01:36.720 --> 00:01:39.710 align:start position:0% um yeah in the second phase um I want to run<00:01:36.960> experiments<00:01:37.799> uh<00:01:38.079> specifically<00:01:38.799> on<00:01:39.079> pias 00:01:39.710 --> 00:01:39.720 align:start position:0% run experiments uh specifically on pias 00:01:39.720 --> 00:01:41.550 align:start position:0% run experiments uh specifically on pias and<00:01:40.040> I<00:01:40.240> don't<00:01:40.399> want<00:01:40.640> also<00:01:40.840> known<00:01:41.079> as<00:01:41.240> gossip 00:01:41.550 --> 00:01:41.560 align:start position:0% and I don't want also known as gossip 00:01:41.560 --> 00:01:42.550 align:start position:0% and I don't want also known as gossip sub 00:01:42.550 --> 00:01:42.560 align:start position:0% sub 00:01:42.560 --> 00:01:45.870 align:start position:0% sub 1.2<00:01:43.560> and<00:01:44.119> in<00:01:44.360> the<00:01:44.560> third<00:01:44.880> phase<00:01:45.200> I<00:01:45.360> thought 00:01:45.870 --> 00:01:45.880 align:start position:0% 1.2 and in the third phase I thought 00:01:45.880 --> 00:01:48.910 align:start position:0% 1.2 and in the third phase I thought maybe<00:01:46.320> if<00:01:46.560> I<00:01:46.880> saw<00:01:47.240> in<00:01:47.439> the<00:01:47.759> experiments<00:01:48.479> that 00:01:48.910 --> 00:01:48.920 align:start position:0% maybe if I saw in the experiments that 00:01:48.920 --> 00:01:51.429 align:start position:0% maybe if I saw in the experiments that this<00:01:49.040> is<00:01:49.200> actually<00:01:49.399> a<00:01:49.520> useful<00:01:49.880> tool<00:01:50.840> um<00:01:51.360> I 00:01:51.429 --> 00:01:51.439 align:start position:0% this is actually a useful tool um I 00:01:51.439 --> 00:01:53.910 align:start position:0% this is actually a useful tool um I wanted<00:01:51.680> to<00:01:51.799> polish<00:01:52.159> it<00:01:52.439> and<00:01:52.759> actually<00:01:53.119> did<00:01:53.719> uh 00:01:53.910 --> 00:01:53.920 align:start position:0% wanted to polish it and actually did uh 00:01:53.920 --> 00:01:59.190 align:start position:0% wanted to polish it and actually did uh and<00:01:54.200> S<00:01:54.960> thus<00:01:55.479> uh<00:01:55.960> e<00:01:56.240> Shadow<00:01:56.520> was<00:01:56.680> born<00:01:57.680> um<00:01:58.159> so<00:01:59.039> to 00:01:59.190 --> 00:01:59.200 align:start position:0% and S thus uh e Shadow was born um so to 00:01:59.200 --> 00:02:01.590 align:start position:0% and S thus uh e Shadow was born um so to sum<00:01:59.439> it<00:01:59.560> up<00:02:00.000> are<00:02:00.240> like<00:02:00.439> two<00:02:00.799> main<00:02:01.039> artifacts 00:02:01.590 --> 00:02:01.600 align:start position:0% sum it up are like two main artifacts 00:02:01.600 --> 00:02:04.270 align:start position:0% sum it up are like two main artifacts from<00:02:01.799> my<00:02:02.280> project<00:02:03.280> um<00:02:03.600> the<00:02:03.759> experiment 00:02:04.270 --> 00:02:04.280 align:start position:0% from my project um the experiment 00:02:04.280 --> 00:02:07.670 align:start position:0% from my project um the experiment results<00:02:05.039> and<00:02:05.399> E<00:02:05.680> Shadow<00:02:06.200> itself<00:02:07.200> in<00:02:07.520> this 00:02:07.670 --> 00:02:07.680 align:start position:0% results and E Shadow itself in this 00:02:07.680 --> 00:02:10.949 align:start position:0% results and E Shadow itself in this presentation<00:02:08.440> I<00:02:08.520> will<00:02:08.920> kind<00:02:09.080> of<00:02:09.360> focus<00:02:09.920> on<00:02:10.679> on 00:02:10.949 --> 00:02:10.959 align:start position:0% presentation I will kind of focus on on 00:02:10.959 --> 00:02:15.190 align:start position:0% presentation I will kind of focus on on my<00:02:11.360> results<00:02:11.720> from<00:02:12.400> pias<00:02:13.400> and<00:02:14.160> afterwards<00:02:15.040> uh 00:02:15.190 --> 00:02:15.200 align:start position:0% my results from pias and afterwards uh 00:02:15.200 --> 00:02:19.350 align:start position:0% my results from pias and afterwards uh also<00:02:15.920> show<00:02:16.200> you<00:02:17.120> slowly<00:02:18.080> um<00:02:18.480> or 00:02:19.350 --> 00:02:19.360 align:start position:0% also show you slowly um or 00:02:19.360 --> 00:02:26.589 align:start position:0% also show you slowly um or quickly<00:02:20.480> um<00:02:21.480> e<00:02:22.480> Shadow<00:02:23.480> right<00:02:24.360> so<00:02:24.680> pias<00:02:25.680> um<00:02:26.519> I 00:02:26.589 --> 00:02:26.599 align:start position:0% quickly um e Shadow right so pias um I 00:02:26.599 --> 00:02:28.470 align:start position:0% quickly um e Shadow right so pias um I won't<00:02:26.840> have<00:02:27.000> time<00:02:27.120> to<00:02:27.280> explain<00:02:27.599> pias<00:02:28.000> fully<00:02:28.280> so 00:02:28.470 --> 00:02:28.480 align:start position:0% won't have time to explain pias fully so 00:02:28.480 --> 00:02:30.390 align:start position:0% won't have time to explain pias fully so I'm<00:02:28.680> just<00:02:28.840> going<00:02:29.040> to<00:02:29.200> assume<00:02:29.519> there's 00:02:30.390 --> 00:02:30.400 align:start position:0% I'm just going to assume there's 00:02:30.400 --> 00:02:33.910 align:start position:0% I'm just going to assume there's uh<00:02:30.560> some<00:02:30.959> awareness<00:02:31.400> of<00:02:31.560> what<00:02:31.720> that<00:02:31.879> is<00:02:32.640> um<00:02:33.599> few 00:02:33.910 --> 00:02:33.920 align:start position:0% uh some awareness of what that is um few 00:02:33.920 --> 00:02:37.030 align:start position:0% uh some awareness of what that is um few points<00:02:34.360> it's<00:02:34.480> a<00:02:34.760> update<00:02:35.080> to<00:02:35.239> scale<00:02:35.879> blobs<00:02:36.640> and 00:02:37.030 --> 00:02:37.040 align:start position:0% points it's a update to scale blobs and 00:02:37.040 --> 00:02:39.470 align:start position:0% points it's a update to scale blobs and the<00:02:37.239> basic<00:02:37.560> principle<00:02:38.080> is<00:02:38.319> that<00:02:38.480> we<00:02:38.599> want<00:02:38.800> to 00:02:39.470 --> 00:02:39.480 align:start position:0% the basic principle is that we want to 00:02:39.480 --> 00:02:41.949 align:start position:0% the basic principle is that we want to split<00:02:40.080> the<00:02:40.239> blobs<00:02:40.680> into<00:02:41.159> Parts<00:02:41.480> which<00:02:41.599> we<00:02:41.760> call 00:02:41.949 --> 00:02:41.959 align:start position:0% split the blobs into Parts which we call 00:02:41.959 --> 00:02:44.430 align:start position:0% split the blobs into Parts which we call columns<00:02:42.760> with<00:02:42.920> every<00:02:43.120> note<00:02:43.440> taking<00:02:43.920> custody 00:02:44.430 --> 00:02:44.440 align:start position:0% columns with every note taking custody 00:02:44.440 --> 00:02:48.110 align:start position:0% columns with every note taking custody of<00:02:44.680> some<00:02:44.959> of<00:02:45.200> those<00:02:45.640> columns<00:02:46.800> and<00:02:47.800> there<00:02:47.920> are 00:02:48.110 --> 00:02:48.120 align:start position:0% of some of those columns and there are 00:02:48.120 --> 00:02:50.190 align:start position:0% of some of those columns and there are some<00:02:48.360> Network<00:02:48.800> CH<00:02:49.159> changes<00:02:49.599> required<00:02:49.959> for 00:02:50.190 --> 00:02:50.200 align:start position:0% some Network CH changes required for 00:02:50.200 --> 00:02:52.309 align:start position:0% some Network CH changes required for this<00:02:50.440> to<00:02:50.599> make<00:02:50.760> sure<00:02:51.000> that<00:02:51.159> the<00:02:51.280> nodes<00:02:52.120> um 00:02:52.309 --> 00:02:52.319 align:start position:0% this to make sure that the nodes um 00:02:52.319 --> 00:02:54.949 align:start position:0% this to make sure that the nodes um properly<00:02:53.239> um<00:02:53.480> distribute<00:02:54.360> uh<00:02:54.519> The<00:02:54.640> Columns 00:02:54.949 --> 00:02:54.959 align:start position:0% properly um distribute uh The Columns 00:02:54.959 --> 00:02:57.390 align:start position:0% properly um distribute uh The Columns across<00:02:55.159> the<00:02:55.280> network<00:02:55.760> and<00:02:56.000> also<00:02:56.959> so-called 00:02:57.390 --> 00:02:57.400 align:start position:0% across the network and also so-called 00:02:57.400 --> 00:02:59.630 align:start position:0% across the network and also so-called supernes<00:02:58.040> can<00:02:58.360> reconstruct<00:02:59.000> the<00:02:59.120> blobs<00:02:59.519> if 00:02:59.630 --> 00:02:59.640 align:start position:0% supernes can reconstruct the blobs if 00:02:59.640 --> 00:03:03.670 align:start position:0% supernes can reconstruct the blobs if they<00:02:59.920> have<00:03:00.080> enough<00:03:00.840> columns<00:03:02.239> and<00:03:03.239> right<00:03:03.400> now 00:03:03.670 --> 00:03:03.680 align:start position:0% they have enough columns and right now 00:03:03.680 --> 00:03:07.430 align:start position:0% they have enough columns and right now there's<00:03:04.000> like<00:03:04.560> 128<00:03:05.560> additional<00:03:05.959> subnets<00:03:06.959> um 00:03:07.430 --> 00:03:07.440 align:start position:0% there's like 128 additional subnets um 00:03:07.440 --> 00:03:11.990 align:start position:0% there's like 128 additional subnets um in<00:03:07.640> gosip<00:03:08.120> sub<00:03:08.959> uh<00:03:09.879> which<00:03:10.120> all<00:03:10.280> need<00:03:10.480> to<00:03:10.599> be<00:03:11.400> uh 00:03:11.990 --> 00:03:12.000 align:start position:0% in gosip sub uh which all need to be uh 00:03:12.000 --> 00:03:14.270 align:start position:0% in gosip sub uh which all need to be uh covered<00:03:13.000> by<00:03:13.280> when<00:03:13.400> a<00:03:13.519> note<00:03:13.720> wants<00:03:13.920> to<00:03:14.040> be 00:03:14.270 --> 00:03:14.280 align:start position:0% covered by when a note wants to be 00:03:14.280 --> 00:03:16.149 align:start position:0% covered by when a note wants to be proposed<00:03:14.840> right<00:03:14.959> we<00:03:15.080> need<00:03:15.480> to<00:03:15.799> get<00:03:15.959> every 00:03:16.149 --> 00:03:16.159 align:start position:0% proposed right we need to get every 00:03:16.159 --> 00:03:18.470 align:start position:0% proposed right we need to get every column<00:03:16.519> out<00:03:16.840> so 00:03:18.470 --> 00:03:18.480 align:start position:0% column out so 00:03:18.480 --> 00:03:20.750 align:start position:0% column out so yeah<00:03:19.480> okay<00:03:19.720> so<00:03:19.879> I<00:03:20.000> decided<00:03:20.280> to<00:03:20.440> run<00:03:20.599> some 00:03:20.750 --> 00:03:20.760 align:start position:0% yeah okay so I decided to run some 00:03:20.760 --> 00:03:22.110 align:start position:0% yeah okay so I decided to run some simulations<00:03:21.280> to<00:03:21.440> help<00:03:21.599> the<00:03:21.720> research<00:03:22.000> and 00:03:22.110 --> 00:03:22.120 align:start position:0% simulations to help the research and 00:03:22.120 --> 00:03:24.430 align:start position:0% simulations to help the research and development<00:03:22.599> effort<00:03:23.599> um<00:03:23.879> keep<00:03:24.040> in<00:03:24.159> mind<00:03:24.319> that 00:03:24.430 --> 00:03:24.440 align:start position:0% development effort um keep in mind that 00:03:24.440 --> 00:03:26.630 align:start position:0% development effort um keep in mind that all<00:03:25.000> results<00:03:25.319> that<00:03:25.440> I<00:03:25.599> present<00:03:25.920> here<00:03:26.120> are<00:03:26.519> like 00:03:26.630 --> 00:03:26.640 align:start position:0% all results that I present here are like 00:03:26.640 --> 00:03:28.670 align:start position:0% all results that I present here are like a<00:03:26.760> few<00:03:26.920> months<00:03:27.120> old<00:03:27.360> at<00:03:27.480> this<00:03:27.640> point<00:03:28.280> so<00:03:28.560> the 00:03:28.670 --> 00:03:28.680 align:start position:0% a few months old at this point so the 00:03:28.680 --> 00:03:30.949 align:start position:0% a few months old at this point so the situation<00:03:29.040> might<00:03:29.200> be<00:03:29.439> uh<00:03:29.560> better<00:03:29.920> at<00:03:30.040> this 00:03:30.949 --> 00:03:30.959 align:start position:0% situation might be uh better at this 00:03:30.959 --> 00:03:34.070 align:start position:0% situation might be uh better at this point<00:03:31.959> so<00:03:32.400> my<00:03:32.519> simulation<00:03:33.040> setup<00:03:33.599> involved 00:03:34.070 --> 00:03:34.080 align:start position:0% point so my simulation setup involved 00:03:34.080 --> 00:03:36.309 align:start position:0% point so my simulation setup involved 1,000<00:03:34.599> notes<00:03:35.080> with<00:03:35.239> r<00:03:35.680> Lighthouse<00:03:36.120> and 00:03:36.309 --> 00:03:36.319 align:start position:0% 1,000 notes with r Lighthouse and 00:03:36.319 --> 00:03:39.990 align:start position:0% 1,000 notes with r Lighthouse and Lighthouse<00:03:36.680> Val<00:03:37.480> on<00:03:37.599> each<00:03:38.599> uh<00:03:38.799> with<00:03:39.159> 4,000 00:03:39.990 --> 00:03:40.000 align:start position:0% Lighthouse Val on each uh with 4,000 00:03:40.000 --> 00:03:42.550 align:start position:0% Lighthouse Val on each uh with 4,000 validators<00:03:41.000> and<00:03:41.319> in<00:03:41.519> each<00:03:41.879> experiment<00:03:42.400> I 00:03:42.550 --> 00:03:42.560 align:start position:0% validators and in each experiment I 00:03:42.560 --> 00:03:45.830 align:start position:0% validators and in each experiment I simulated<00:03:43.239> 45<00:03:43.799> minutes<00:03:44.040> of<00:03:44.159> simulated<00:03:44.720> time 00:03:45.830 --> 00:03:45.840 align:start position:0% simulated 45 minutes of simulated time 00:03:45.840 --> 00:03:49.670 align:start position:0% simulated 45 minutes of simulated time um<00:03:46.840> for<00:03:47.599> a<00:03:47.799> large<00:03:48.159> simulation<00:03:48.799> like<00:03:49.080> this<00:03:49.519> we 00:03:49.670 --> 00:03:49.680 align:start position:0% um for a large simulation like this we 00:03:49.680 --> 00:03:52.149 align:start position:0% um for a large simulation like this we want<00:03:49.920> to<00:03:50.280> run<00:03:50.640> on<00:03:50.920> some<00:03:51.519> server<00:03:51.920> that<00:03:52.000> is 00:03:52.149 --> 00:03:52.159 align:start position:0% want to run on some server that is 00:03:52.159 --> 00:03:54.390 align:start position:0% want to run on some server that is sufficiently<00:03:52.720> large<00:03:53.319> though<00:03:53.879> the<00:03:54.040> simulation 00:03:54.390 --> 00:03:54.400 align:start position:0% sufficiently large though the simulation 00:03:54.400 --> 00:03:56.789 align:start position:0% sufficiently large though the simulation is<00:03:54.560> fast<00:03:54.840> enough<00:03:55.120> for<00:03:55.280> us 00:03:56.789 --> 00:03:56.799 align:start position:0% is fast enough for us 00:03:56.799 --> 00:04:00.710 align:start position:0% is fast enough for us and<00:03:57.799> I<00:03:58.239> kind<00:03:58.400> of<00:03:58.599> experimented<00:03:59.439> around<00:04:00.200> a<00:04:00.360> lot 00:04:00.710 --> 00:04:00.720 align:start position:0% and I kind of experimented around a lot 00:04:00.720 --> 00:04:04.110 align:start position:0% and I kind of experimented around a lot to<00:04:00.959> make<00:04:01.159> sure<00:04:01.439> to<00:04:01.720> get<00:04:02.599> like<00:04:03.599> get<00:04:03.840> nice 00:04:04.110 --> 00:04:04.120 align:start position:0% to make sure to get like get nice 00:04:04.120 --> 00:04:07.429 align:start position:0% to make sure to get like get nice performance<00:04:04.640> going<00:04:05.640> and<00:04:06.519> kind<00:04:06.680> of<00:04:06.799> settled<00:04:07.239> on 00:04:07.429 --> 00:04:07.439 align:start position:0% performance going and kind of settled on 00:04:07.439 --> 00:04:09.750 align:start position:0% performance going and kind of settled on a<00:04:07.560> certain<00:04:07.920> instance<00:04:08.360> type<00:04:09.159> um<00:04:09.400> you<00:04:09.480> can<00:04:09.599> see 00:04:09.750 --> 00:04:09.760 align:start position:0% a certain instance type um you can see 00:04:09.760 --> 00:04:11.190 align:start position:0% a certain instance type um you can see it<00:04:09.920> there<00:04:10.040> if<00:04:10.159> you<00:04:10.239> want<00:04:10.400> to<00:04:10.720> run<00:04:10.920> your<00:04:11.000> own 00:04:11.190 --> 00:04:11.200 align:start position:0% it there if you want to run your own 00:04:11.200 --> 00:04:14.069 align:start position:0% it there if you want to run your own simulations<00:04:11.879> with<00:04:12.040> this<00:04:12.360> size 00:04:14.069 --> 00:04:14.079 align:start position:0% simulations with this size 00:04:14.079 --> 00:04:17.909 align:start position:0% simulations with this size and<00:04:15.079> my<00:04:15.280> simulations<00:04:16.040> took<00:04:16.400> a<00:04:16.680> round<00:04:17.239> of<00:04:17.519> 4 00:04:17.909 --> 00:04:17.919 align:start position:0% and my simulations took a round of 4 00:04:17.919 --> 00:04:20.870 align:start position:0% and my simulations took a round of 4 hours<00:04:18.479> per<00:04:18.840> like<00:04:19.239> 45<00:04:19.959> minutes<00:04:20.239> of<00:04:20.359> simulated 00:04:20.870 --> 00:04:20.880 align:start position:0% hours per like 45 minutes of simulated 00:04:20.880 --> 00:04:23.749 align:start position:0% hours per like 45 minutes of simulated time<00:04:21.799> and<00:04:22.040> so<00:04:22.440> the<00:04:22.720> the<00:04:22.880> cost<00:04:23.199> of<00:04:23.520> per 00:04:23.749 --> 00:04:23.759 align:start position:0% time and so the the cost of per 00:04:23.759 --> 00:04:28.189 align:start position:0% time and so the the cost of per simulation<00:04:24.240> came<00:04:24.479> around<00:04:24.800> at<00:04:25.360> uh 00:04:28.189 --> 00:04:28.199 align:start position:0% 00:04:28.199 --> 00:04:32.230 align:start position:0% $10<00:04:29.199> right<00:04:30.000> um<00:04:30.280> but<00:04:30.479> if<00:04:30.600> you<00:04:31.080> want<00:04:31.680> like<00:04:31.960> also 00:04:32.230 --> 00:04:32.240 align:start position:0% $10 right um but if you want like also 00:04:32.240 --> 00:04:34.150 align:start position:0% $10 right um but if you want like also run<00:04:32.520> smaller<00:04:32.919> simulations<00:04:33.440> we<00:04:33.720> you<00:04:33.800> can<00:04:33.960> also 00:04:34.150 --> 00:04:34.160 align:start position:0% run smaller simulations we you can also 00:04:34.160 --> 00:04:35.550 align:start position:0% run smaller simulations we you can also do<00:04:34.320> this<00:04:34.440> on<00:04:34.560> your<00:04:34.720> laptop<00:04:35.120> like<00:04:35.240> you<00:04:35.360> don't 00:04:35.550 --> 00:04:35.560 align:start position:0% do this on your laptop like you don't 00:04:35.560 --> 00:04:37.870 align:start position:0% do this on your laptop like you don't need<00:04:35.919> such<00:04:36.080> a<00:04:36.240> PV<00:04:36.560> server<00:04:37.160> this<00:04:37.280> is<00:04:37.400> just<00:04:37.560> like 00:04:37.870 --> 00:04:37.880 align:start position:0% need such a PV server this is just like 00:04:37.880 --> 00:04:41.270 align:start position:0% need such a PV server this is just like my<00:04:38.120> setup<00:04:38.520> for<00:04:38.840> the<00:04:39.240> P 00:04:41.270 --> 00:04:41.280 align:start position:0% my setup for the P 00:04:41.280 --> 00:04:45.510 align:start position:0% my setup for the P simulations<00:04:42.280> um<00:04:43.560> so<00:04:44.560> first<00:04:44.840> I<00:04:45.000> just<00:04:45.160> tried 00:04:45.510 --> 00:04:45.520 align:start position:0% simulations um so first I just tried 00:04:45.520 --> 00:04:47.749 align:start position:0% simulations um so first I just tried running<00:04:46.160> it<00:04:46.360> on<00:04:46.680> the<00:04:46.880> current<00:04:47.160> implementation 00:04:47.749 --> 00:04:47.759 align:start position:0% running it on the current implementation 00:04:47.759 --> 00:04:48.550 align:start position:0% running it on the current implementation in 00:04:48.550 --> 00:04:48.560 align:start position:0% in 00:04:48.560 --> 00:04:51.270 align:start position:0% in Lighthouse<00:04:49.560> and<00:04:50.320> the<00:04:50.440> simulated<00:04:50.880> networks 00:04:51.270 --> 00:04:51.280 align:start position:0% Lighthouse and the simulated networks 00:04:51.280 --> 00:04:54.350 align:start position:0% Lighthouse and the simulated networks quickly<00:04:51.520> fell<00:04:51.840> apart<00:04:52.840> because<00:04:53.479> they<00:04:54.080> lost 00:04:54.350 --> 00:04:54.360 align:start position:0% quickly fell apart because they lost 00:04:54.360 --> 00:04:56.749 align:start position:0% quickly fell apart because they lost sync<00:04:54.880> and<00:04:55.120> cannot<00:04:55.560> really<00:04:55.800> sync<00:04:56.199> back<00:04:56.360> up 00:04:56.749 --> 00:04:56.759 align:start position:0% sync and cannot really sync back up 00:04:56.759 --> 00:04:59.469 align:start position:0% sync and cannot really sync back up again<00:04:57.759> um<00:04:58.039> and<00:04:58.240> that<00:04:58.360> was<00:04:58.600> kind<00:04:58.759> of<00:04:59.039> similar 00:04:59.469 --> 00:04:59.479 align:start position:0% again um and that was kind of similar 00:04:59.479 --> 00:05:02.110 align:start position:0% again um and that was kind of similar what<00:04:59.759> was<00:04:59.840> seen<00:05:00.039> on<00:05:00.160> Def<00:05:00.440> Nets<00:05:00.759> at<00:05:00.880> the<00:05:01.080> time<00:05:01.960> uh 00:05:02.110 --> 00:05:02.120 align:start position:0% what was seen on Def Nets at the time uh 00:05:02.120 --> 00:05:03.670 align:start position:0% what was seen on Def Nets at the time uh across<00:05:02.639> basically<00:05:03.000> all 00:05:03.670 --> 00:05:03.680 align:start position:0% across basically all 00:05:03.680 --> 00:05:06.390 align:start position:0% across basically all clients<00:05:04.680> um<00:05:04.880> so<00:05:05.039> I<00:05:05.160> thought<00:05:05.360> about<00:05:05.600> how<00:05:05.880> do<00:05:06.000> I 00:05:06.390 --> 00:05:06.400 align:start position:0% clients um so I thought about how do I 00:05:06.400 --> 00:05:08.350 align:start position:0% clients um so I thought about how do I measure<00:05:06.880> performance<00:05:07.680> and<00:05:07.840> I<00:05:07.919> had<00:05:08.080> several 00:05:08.350 --> 00:05:08.360 align:start position:0% measure performance and I had several 00:05:08.360 --> 00:05:12.189 align:start position:0% measure performance and I had several metrics<00:05:08.840> but<00:05:09.039> right<00:05:09.240> here<00:05:10.000> I<00:05:10.080> will<00:05:10.639> focus<00:05:11.199> on 00:05:12.189 --> 00:05:12.199 align:start position:0% metrics but right here I will focus on 00:05:12.199 --> 00:05:15.070 align:start position:0% metrics but right here I will focus on what<00:05:12.320> I<00:05:12.479> call<00:05:12.680> score<00:05:13.680> uh<00:05:13.840> which<00:05:13.960> is<00:05:14.240> how<00:05:14.720> many 00:05:15.070 --> 00:05:15.080 align:start position:0% what I call score uh which is how many 00:05:15.080 --> 00:05:20.510 align:start position:0% what I call score uh which is how many slots<00:05:16.400> can<00:05:17.400> um<00:05:17.919> over<00:05:18.360> 66%<00:05:19.360> of<00:05:19.520> the<00:05:19.680> network<00:05:20.400> uh 00:05:20.510 --> 00:05:20.520 align:start position:0% slots can um over 66% of the network uh 00:05:20.520 --> 00:05:23.670 align:start position:0% slots can um over 66% of the network uh stay<00:05:20.800> in<00:05:21.080> sync<00:05:22.080> and<00:05:22.479> with<00:05:22.880> the 00:05:23.670 --> 00:05:23.680 align:start position:0% stay in sync and with the 00:05:23.680 --> 00:05:26.029 align:start position:0% stay in sync and with the unmodified<00:05:24.680> uh<00:05:25.039> client<00:05:25.440> with<00:05:25.560> the<00:05:25.680> default 00:05:26.029 --> 00:05:26.039 align:start position:0% unmodified uh client with the default 00:05:26.039 --> 00:05:28.029 align:start position:0% unmodified uh client with the default configuration<00:05:26.960> zero<00:05:27.400> like<00:05:27.560> immediately 00:05:28.029 --> 00:05:28.039 align:start position:0% configuration zero like immediately 00:05:28.039 --> 00:05:30.870 align:start position:0% configuration zero like immediately after<00:05:28.240> we<00:05:28.560> posted<00:05:28.960> blobs<00:05:29.319> to<00:05:29.440> the<00:05:29.720> Network<00:05:30.720> um 00:05:30.870 --> 00:05:30.880 align:start position:0% after we posted blobs to the Network um 00:05:30.880 --> 00:05:33.950 align:start position:0% after we posted blobs to the Network um we<00:05:31.000> lost<00:05:31.280> sync<00:05:32.280> um<00:05:32.600> but<00:05:32.759> I<00:05:32.919> also<00:05:33.160> noticed<00:05:33.680> that 00:05:33.950 --> 00:05:33.960 align:start position:0% we lost sync um but I also noticed that 00:05:33.960 --> 00:05:37.670 align:start position:0% we lost sync um but I also noticed that if<00:05:34.199> I<00:05:34.919> designate<00:05:35.680> every<00:05:35.880> node<00:05:36.160> as<00:05:36.479> super<00:05:36.759> no<00:05:37.199> so 00:05:37.670 --> 00:05:37.680 align:start position:0% if I designate every node as super no so 00:05:37.680 --> 00:05:41.629 align:start position:0% if I designate every node as super no so coding<00:05:38.600> all<00:05:38.880> the<00:05:39.080> columns<00:05:39.520> not<00:05:39.680> just<00:05:40.199> uh<00:05:40.639> eight 00:05:41.629 --> 00:05:41.639 align:start position:0% coding all the columns not just uh eight 00:05:41.639 --> 00:05:46.270 align:start position:0% coding all the columns not just uh eight uh<00:05:41.759> or<00:05:42.000> four<00:05:43.080> um<00:05:44.080> then<00:05:45.080> um<00:05:45.280> the<00:05:45.400> network<00:05:45.840> stayed 00:05:46.270 --> 00:05:46.280 align:start position:0% uh or four um then um the network stayed 00:05:46.280 --> 00:05:49.150 align:start position:0% uh or four um then um the network stayed stable<00:05:46.639> until<00:05:46.919> the<00:05:47.039> end<00:05:47.400> so<00:05:48.400> I<00:05:48.520> had<00:05:48.759> like<00:05:48.960> the 00:05:49.150 --> 00:05:49.160 align:start position:0% stable until the end so I had like the 00:05:49.160 --> 00:05:51.029 align:start position:0% stable until the end so I had like the suspicion<00:05:49.600> that<00:05:49.759> something<00:05:50.039> is<00:05:50.199> wrong<00:05:50.520> with 00:05:51.029 --> 00:05:51.039 align:start position:0% suspicion that something is wrong with 00:05:51.039 --> 00:05:55.430 align:start position:0% suspicion that something is wrong with um<00:05:52.000> the<00:05:52.440> distribution<00:05:53.360> of<00:05:54.039> uh<00:05:54.240> columns<00:05:54.840> when 00:05:55.430 --> 00:05:55.440 align:start position:0% um the distribution of uh columns when 00:05:55.440 --> 00:05:58.870 align:start position:0% um the distribution of uh columns when we<00:05:55.680> just<00:05:56.160> you<00:05:56.319> know<00:05:56.960> don't<00:05:57.520> broadcast<00:05:58.160> all<00:05:58.400> the 00:05:58.870 --> 00:05:58.880 align:start position:0% we just you know don't broadcast all the 00:05:58.880 --> 00:06:01.909 align:start position:0% we just you know don't broadcast all the columns<00:05:59.240> at<00:05:59.400> all<00:05:59.759> time<00:05:59.919> to<00:06:00.520> everyone<00:06:01.520> and<00:06:01.680> also 00:06:01.909 --> 00:06:01.919 align:start position:0% columns at all time to everyone and also 00:06:01.919 --> 00:06:04.150 align:start position:0% columns at all time to everyone and also that<00:06:02.120> might<00:06:02.280> be<00:06:02.479> something<00:06:03.160> with<00:06:03.400> super<00:06:03.759> node 00:06:04.150 --> 00:06:04.160 align:start position:0% that might be something with super node 00:06:04.160 --> 00:06:07.270 align:start position:0% that might be something with super node reconstruction<00:06:05.120> of<00:06:05.800> the<00:06:05.919> blobs<00:06:06.400> might<00:06:06.560> be 00:06:07.270 --> 00:06:07.280 align:start position:0% reconstruction of the blobs might be 00:06:07.280 --> 00:06:11.430 align:start position:0% reconstruction of the blobs might be wrong<00:06:08.280> yeah<00:06:09.360> um<00:06:10.360> so<00:06:10.720> and<00:06:10.960> yeah<00:06:11.319> the 00:06:11.430 --> 00:06:11.440 align:start position:0% wrong yeah um so and yeah the 00:06:11.440 --> 00:06:13.510 align:start position:0% wrong yeah um so and yeah the investigation<00:06:12.120> showed<00:06:12.560> that<00:06:12.720> the<00:06:12.919> problem<00:06:13.240> is 00:06:13.510 --> 00:06:13.520 align:start position:0% investigation showed that the problem is 00:06:13.520 --> 00:06:16.029 align:start position:0% investigation showed that the problem is that<00:06:14.039> if<00:06:14.319> a<00:06:14.479> node<00:06:14.840> could<00:06:15.000> not<00:06:15.199> send<00:06:15.680> all<00:06:15.800> the 00:06:16.029 --> 00:06:16.039 align:start position:0% that if a node could not send all the 00:06:16.039 --> 00:06:19.749 align:start position:0% that if a node could not send all the data<00:06:16.919> out<00:06:17.319> it<00:06:17.440> would<00:06:17.599> not<00:06:17.800> retry<00:06:18.360> that<00:06:18.720> at<00:06:18.880> all 00:06:19.749 --> 00:06:19.759 align:start position:0% data out it would not retry that at all 00:06:19.759 --> 00:06:21.710 align:start position:0% data out it would not retry that at all causing<00:06:20.039> some<00:06:20.199> columns<00:06:20.520> to<00:06:20.639> get<00:06:20.759> lost<00:06:21.240> and 00:06:21.710 --> 00:06:21.720 align:start position:0% causing some columns to get lost and 00:06:21.720 --> 00:06:26.390 align:start position:0% causing some columns to get lost and custody<00:06:22.280> nodes<00:06:23.199> uh<00:06:23.400> for<00:06:24.080> those<00:06:24.720> columns<00:06:25.720> would 00:06:26.390 --> 00:06:26.400 align:start position:0% custody nodes uh for those columns would 00:06:26.400 --> 00:06:29.670 align:start position:0% custody nodes uh for those columns would just<00:06:26.599> not<00:06:27.240> deem<00:06:27.800> the<00:06:27.960> datas<00:06:28.319> available<00:06:29.080> and 00:06:29.670 --> 00:06:29.680 align:start position:0% just not deem the datas available and 00:06:29.680 --> 00:06:32.189 align:start position:0% just not deem the datas available and would<00:06:29.919> just<00:06:30.120> not<00:06:30.400> accept<00:06:30.639> the<00:06:30.759> block<00:06:31.080> and<00:06:31.560> lose 00:06:32.189 --> 00:06:32.199 align:start position:0% would just not accept the block and lose 00:06:32.199 --> 00:06:35.309 align:start position:0% would just not accept the block and lose sync<00:06:33.199> and<00:06:33.360> they<00:06:33.479> could<00:06:33.599> not<00:06:34.080> catch<00:06:34.280> up<00:06:34.639> I<00:06:34.800> guess 00:06:35.309 --> 00:06:35.319 align:start position:0% sync and they could not catch up I guess 00:06:35.319 --> 00:06:37.270 align:start position:0% sync and they could not catch up I guess the<00:06:35.440> supernes<00:06:35.919> were<00:06:36.120> not<00:06:36.560> uh<00:06:36.680> not<00:06:36.880> enough<00:06:37.080> for 00:06:37.270 --> 00:06:37.280 align:start position:0% the supernes were not uh not enough for 00:06:37.280 --> 00:06:40.670 align:start position:0% the supernes were not uh not enough for that<00:06:37.960> so<00:06:38.759> how<00:06:38.880> do<00:06:39.000> we<00:06:39.120> fix<00:06:39.400> this<00:06:39.880> I<00:06:40.280> did<00:06:40.479> some 00:06:40.670 --> 00:06:40.680 align:start position:0% that so how do we fix this I did some 00:06:40.680 --> 00:06:43.830 align:start position:0% that so how do we fix this I did some simulations<00:06:41.400> where<00:06:41.560> I<00:06:41.720> varied<00:06:42.120> the<00:06:42.280> specs<00:06:43.080> and 00:06:43.830 --> 00:06:43.840 align:start position:0% simulations where I varied the specs and 00:06:43.840 --> 00:06:46.909 align:start position:0% simulations where I varied the specs and um<00:06:44.560> I<00:06:44.759> did<00:06:44.960> a<00:06:45.120> lot<00:06:45.280> of<00:06:45.639> different<00:06:46.639> um 00:06:46.909 --> 00:06:46.919 align:start position:0% um I did a lot of different um 00:06:46.919 --> 00:06:49.790 align:start position:0% um I did a lot of different um variations<00:06:47.800> I<00:06:47.880> will<00:06:48.080> focus<00:06:48.319> on<00:06:48.479> three<00:06:48.800> here<00:06:49.680> uh 00:06:49.790 --> 00:06:49.800 align:start position:0% variations I will focus on three here uh 00:06:49.800 --> 00:06:51.309 align:start position:0% variations I will focus on three here uh we<00:06:49.919> could<00:06:50.080> increase<00:06:50.400> the<00:06:50.560> number<00:06:50.759> of<00:06:50.919> peers 00:06:51.309 --> 00:06:51.319 align:start position:0% we could increase the number of peers 00:06:51.319 --> 00:06:52.710 align:start position:0% we could increase the number of peers because<00:06:51.520> if<00:06:51.639> we<00:06:51.759> have<00:06:51.919> more<00:06:52.160> Pi<00:06:52.560> the 00:06:52.710 --> 00:06:52.720 align:start position:0% because if we have more Pi the 00:06:52.720 --> 00:06:54.990 align:start position:0% because if we have more Pi the likelihood<00:06:53.120> that<00:06:53.280> we<00:06:53.560> actually<00:06:53.960> cover<00:06:54.759> all 00:06:54.990 --> 00:06:55.000 align:start position:0% likelihood that we actually cover all 00:06:55.000 --> 00:06:58.710 align:start position:0% likelihood that we actually cover all the<00:06:55.400> columns<00:06:56.240> uh<00:06:56.360> when<00:06:56.639> proposing<00:06:57.120> a<00:06:57.360> block<00:06:58.360> um 00:06:58.710 --> 00:06:58.720 align:start position:0% the columns uh when proposing a block um 00:06:58.720 --> 00:07:03.189 align:start position:0% the columns uh when proposing a block um with<00:06:58.879> our<00:06:59.160> peers<00:06:59.919> uh<00:07:00.120> is<00:07:00.319> higher<00:07:01.599> so<00:07:02.599> yeah<00:07:03.080> the 00:07:03.189 --> 00:07:03.199 align:start position:0% with our peers uh is higher so yeah the 00:07:03.199 --> 00:07:05.909 align:start position:0% with our peers uh is higher so yeah the base<00:07:03.520> back<00:07:04.360> or<00:07:04.560> the<00:07:04.680> base<00:07:05.240> configuration<00:07:05.759> in 00:07:05.909 --> 00:07:05.919 align:start position:0% base back or the base configuration in 00:07:05.919 --> 00:07:10.230 align:start position:0% base back or the base configuration in Lighthouse<00:07:06.879> uh<00:07:07.639> looks<00:07:07.840> for<00:07:08.280> 100<00:07:08.680> Pi<00:07:09.680> 150 00:07:10.230 --> 00:07:10.240 align:start position:0% Lighthouse uh looks for 100 Pi 150 00:07:10.240 --> 00:07:13.270 align:start position:0% Lighthouse uh looks for 100 Pi 150 Pierce<00:07:10.800> scored<00:07:11.560> 10<00:07:11.879> with<00:07:11.960> the<00:07:12.080> metric<00:07:12.520> I<00:07:13.080> just 00:07:13.270 --> 00:07:13.280 align:start position:0% Pierce scored 10 with the metric I just 00:07:13.280 --> 00:07:18.230 align:start position:0% Pierce scored 10 with the metric I just mentioned<00:07:14.280> 200<00:07:15.120> uh<00:07:16.039> already<00:07:16.680> uh<00:07:16.800> 56<00:07:17.680> and<00:07:17.879> 300 00:07:18.230 --> 00:07:18.240 align:start position:0% mentioned 200 uh already uh 56 and 300 00:07:18.240 --> 00:07:19.749 align:start position:0% mentioned 200 uh already uh 56 and 300 Sur<00:07:18.560> the<00:07:18.599> whole<00:07:18.759> simulation<00:07:19.160> so<00:07:19.280> we<00:07:19.400> could<00:07:19.520> see 00:07:19.749 --> 00:07:19.759 align:start position:0% Sur the whole simulation so we could see 00:07:19.759 --> 00:07:22.070 align:start position:0% Sur the whole simulation so we could see that<00:07:20.440> confirming<00:07:20.840> our<00:07:21.080> Theory<00:07:21.520> this<00:07:21.680> improves 00:07:22.070 --> 00:07:22.080 align:start position:0% that confirming our Theory this improves 00:07:22.080 --> 00:07:22.909 align:start position:0% that confirming our Theory this improves the 00:07:22.909 --> 00:07:22.919 align:start position:0% the 00:07:22.919 --> 00:07:25.830 align:start position:0% the situation<00:07:23.919> next<00:07:24.199> up<00:07:24.599> I<00:07:25.039> increased<00:07:25.520> the<00:07:25.639> number 00:07:25.830 --> 00:07:25.840 align:start position:0% situation next up I increased the number 00:07:25.840 --> 00:07:28.309 align:start position:0% situation next up I increased the number of<00:07:26.000> columns<00:07:26.360> covered<00:07:26.720> per<00:07:26.960> each<00:07:27.280> Pier<00:07:27.960> which 00:07:28.309 --> 00:07:28.319 align:start position:0% of columns covered per each Pier which 00:07:28.319 --> 00:07:29.830 align:start position:0% of columns covered per each Pier which should<00:07:28.639> have<00:07:28.800> the<00:07:28.960> same<00:07:29.240> effect<00:07:29.720> right 00:07:29.830 --> 00:07:29.840 align:start position:0% should have the same effect right 00:07:29.840 --> 00:07:31.710 align:start position:0% should have the same effect right because<00:07:30.039> the<00:07:30.160> total<00:07:30.400> number<00:07:30.599> of<00:07:30.759> cover 00:07:31.710 --> 00:07:31.720 align:start position:0% because the total number of cover 00:07:31.720 --> 00:07:34.469 align:start position:0% because the total number of cover columns<00:07:32.680> also<00:07:32.919> increases<00:07:33.599> with<00:07:33.879> uh<00:07:34.000> changing 00:07:34.469 --> 00:07:34.479 align:start position:0% columns also increases with uh changing 00:07:34.479 --> 00:07:37.670 align:start position:0% columns also increases with uh changing this<00:07:35.319> um<00:07:35.759> increasing<00:07:36.199> from<00:07:36.319> 4<00:07:36.560> to<00:07:36.680> 8<00:07:37.000> score<00:07:37.319> 10 00:07:37.670 --> 00:07:37.680 align:start position:0% this um increasing from 4 to 8 score 10 00:07:37.680 --> 00:07:39.070 align:start position:0% this um increasing from 4 to 8 score 10 and<00:07:37.840> 16<00:07:38.240> already<00:07:38.440> so<00:07:38.639> we<00:07:38.720> have<00:07:38.840> the<00:07:38.879> whole 00:07:39.070 --> 00:07:39.080 align:start position:0% and 16 already so we have the whole 00:07:39.080 --> 00:07:41.869 align:start position:0% and 16 already so we have the whole simulation<00:07:40.080> finally<00:07:41.000> uh<00:07:41.440> there<00:07:41.560> should<00:07:41.720> be 00:07:41.869 --> 00:07:41.879 align:start position:0% simulation finally uh there should be 00:07:41.879 --> 00:07:46.230 align:start position:0% simulation finally uh there should be Anem<00:07:42.440> Emoji<00:07:42.879> here<00:07:43.800> the<00:07:44.280> the<00:07:45.039> you<00:07:45.159> know<00:07:45.400> the<00:07:45.840> the 00:07:46.230 --> 00:07:46.240 align:start position:0% Anem Emoji here the the you know the the 00:07:46.240 --> 00:07:50.070 align:start position:0% Anem Emoji here the the you know the the diagonal<00:07:46.759> face<00:07:48.000> um<00:07:49.000> right<00:07:49.479> uh<00:07:49.599> increasing<00:07:49.960> the 00:07:50.070 --> 00:07:50.080 align:start position:0% diagonal face um right uh increasing the 00:07:50.080 --> 00:07:51.029 align:start position:0% diagonal face um right uh increasing the number<00:07:50.240> of 00:07:51.029 --> 00:07:51.039 align:start position:0% number of 00:07:51.039 --> 00:07:55.149 align:start position:0% number of supernotes<00:07:52.039> which<00:07:52.360> should<00:07:52.840> reconstruct<00:07:54.159> the 00:07:55.149 --> 00:07:55.159 align:start position:0% supernotes which should reconstruct the 00:07:55.159 --> 00:07:57.390 align:start position:0% supernotes which should reconstruct the um<00:07:55.520> full<00:07:55.919> blobs<00:07:56.400> like<00:07:56.560> all<00:07:56.759> columns<00:07:57.159> if<00:07:57.280> they 00:07:57.390 --> 00:07:57.400 align:start position:0% um full blobs like all columns if they 00:07:57.400 --> 00:08:00.029 align:start position:0% um full blobs like all columns if they have<00:07:57.599> half<00:07:57.759> or<00:07:58.080> more<00:07:59.080> um 00:08:00.029 --> 00:08:00.039 align:start position:0% have half or more um 00:08:00.039 --> 00:08:03.670 align:start position:0% have half or more um increasing<00:08:00.520> to<00:08:00.720> 10<00:08:01.159> scored<00:08:01.759> zero<00:08:02.159> to<00:08:02.400> 25<00:08:03.400> of 00:08:03.670 --> 00:08:03.680 align:start position:0% increasing to 10 scored zero to 25 of 00:08:03.680 --> 00:08:08.550 align:start position:0% increasing to 10 scored zero to 25 of thousand<00:08:04.520> uh<00:08:04.840> right<00:08:05.479> scored<00:08:05.840> two<00:08:06.479> and<00:08:07.479> 75<00:08:08.199> also 00:08:08.550 --> 00:08:08.560 align:start position:0% thousand uh right scored two and 75 also 00:08:08.560 --> 00:08:10.869 align:start position:0% thousand uh right scored two and 75 also too<00:08:09.199> and<00:08:09.680> at<00:08:09.800> that<00:08:09.960> point<00:08:10.120> I<00:08:10.199> didn't<00:08:10.400> test<00:08:10.680> any 00:08:10.869 --> 00:08:10.879 align:start position:0% too and at that point I didn't test any 00:08:10.879 --> 00:08:13.790 align:start position:0% too and at that point I didn't test any further<00:08:11.720> because<00:08:12.720> I<00:08:12.800> want<00:08:13.000> to<00:08:13.240> kind<00:08:13.400> of<00:08:13.599> keep 00:08:13.790 --> 00:08:13.800 align:start position:0% further because I want to kind of keep 00:08:13.800 --> 00:08:18.309 align:start position:0% further because I want to kind of keep it<00:08:14.680> in<00:08:15.280> a<00:08:15.639> somewhat<00:08:16.039> realistic<00:08:16.919> scape<00:08:17.440> and<00:08:18.159> I'm 00:08:18.309 --> 00:08:18.319 align:start position:0% it in a somewhat realistic scape and I'm 00:08:18.319 --> 00:08:20.309 align:start position:0% it in a somewhat realistic scape and I'm not<00:08:18.479> sure<00:08:18.680> how<00:08:18.800> many<00:08:19.039> supernes<00:08:19.639> there<00:08:19.759> will<00:08:19.960> be 00:08:20.309 --> 00:08:20.319 align:start position:0% not sure how many supernes there will be 00:08:20.319 --> 00:08:22.749 align:start position:0% not sure how many supernes there will be but<00:08:20.919> we<00:08:21.039> shouldn't<00:08:21.479> in<00:08:21.599> my<00:08:21.800> opinion<00:08:22.280> set<00:08:22.599> the 00:08:22.749 --> 00:08:22.759 align:start position:0% but we shouldn't in my opinion set the 00:08:22.759 --> 00:08:24.309 align:start position:0% but we shouldn't in my opinion set the Assumption<00:08:23.199> too 00:08:24.309 --> 00:08:24.319 align:start position:0% Assumption too 00:08:24.319 --> 00:08:27.589 align:start position:0% Assumption too high<00:08:25.319> all<00:08:25.479> right 00:08:27.589 --> 00:08:27.599 align:start position:0% high all right 00:08:27.599 --> 00:08:30.270 align:start position:0% high all right um<00:08:28.599> if<00:08:28.720> you<00:08:28.840> want<00:08:28.960> to<00:08:29.080> know<00:08:29.199> more<00:08:29.560> about<00:08:29.800> that 00:08:30.270 --> 00:08:30.280 align:start position:0% um if you want to know more about that 00:08:30.280 --> 00:08:32.070 align:start position:0% um if you want to know more about that um<00:08:30.520> there<00:08:30.639> are<00:08:30.840> my<00:08:31.000> weekly<00:08:31.400> reports<00:08:31.840> where<00:08:31.960> I 00:08:32.070 --> 00:08:32.080 align:start position:0% um there are my weekly reports where I 00:08:32.080 --> 00:08:34.589 align:start position:0% um there are my weekly reports where I got<00:08:32.320> into<00:08:32.560> a<00:08:32.719> bit<00:08:32.880> more<00:08:33.080> detail<00:08:33.800> so<00:08:34.039> let's<00:08:34.519> uh 00:08:34.589 --> 00:08:34.599 align:start position:0% got into a bit more detail so let's uh 00:08:34.599 --> 00:08:36.709 align:start position:0% got into a bit more detail so let's uh move<00:08:34.800> on<00:08:34.959> to<00:08:35.120> the<00:08:35.279> state<00:08:35.560> of<00:08:35.719> each<00:08:35.959> Shadow<00:08:36.399> like 00:08:36.709 --> 00:08:36.719 align:start position:0% move on to the state of each Shadow like 00:08:36.719 --> 00:08:39.430 align:start position:0% move on to the state of each Shadow like the<00:08:36.839> tool<00:08:37.080> I<00:08:37.440> developed<00:08:38.440> um<00:08:38.640> because<00:08:39.000> seeing 00:08:39.430 --> 00:08:39.440 align:start position:0% the tool I developed um because seeing 00:08:39.440 --> 00:08:42.750 align:start position:0% the tool I developed um because seeing these<00:08:39.959> simulations<00:08:40.959> um<00:08:41.959> I<00:08:42.080> thought<00:08:42.440> this<00:08:42.519> is 00:08:42.750 --> 00:08:42.760 align:start position:0% these simulations um I thought this is 00:08:42.760 --> 00:08:45.030 align:start position:0% these simulations um I thought this is hey<00:08:42.880> it's<00:08:43.080> kind<00:08:43.159> of<00:08:43.279> useful<00:08:43.719> I<00:08:43.839> have<00:08:44.080> like<00:08:44.920> an 00:08:45.030 --> 00:08:45.040 align:start position:0% hey it's kind of useful I have like an 00:08:45.040 --> 00:08:46.710 align:start position:0% hey it's kind of useful I have like an iterative<00:08:45.600> approach<00:08:45.959> and<00:08:46.080> can<00:08:46.279> evaluate 00:08:46.710 --> 00:08:46.720 align:start position:0% iterative approach and can evaluate 00:08:46.720 --> 00:08:48.949 align:start position:0% iterative approach and can evaluate different<00:08:47.040> configurations<00:08:47.680> so<00:08:47.959> I<00:08:48.519> yeah<00:08:48.680> spent 00:08:48.949 --> 00:08:48.959 align:start position:0% different configurations so I yeah spent 00:08:48.959 --> 00:08:50.310 align:start position:0% different configurations so I yeah spent some<00:08:49.120> weeks<00:08:49.320> in<00:08:49.440> the<00:08:49.560> end<00:08:49.800> to<00:08:50.000> make<00:08:50.120> it 00:08:50.310 --> 00:08:50.320 align:start position:0% some weeks in the end to make it 00:08:50.320 --> 00:08:52.630 align:start position:0% some weeks in the end to make it available<00:08:50.720> for<00:08:51.040> everyone<00:08:51.920> and<00:08:52.120> the<00:08:52.279> source<00:08:52.480> is 00:08:52.630 --> 00:08:52.640 align:start position:0% available for everyone and the source is 00:08:52.640 --> 00:08:56.230 align:start position:0% available for everyone and the source is available<00:08:53.000> on<00:08:53.160> GitHub<00:08:53.640> at<00:08:54.240> ethereum<00:08:55.240> Shadow 00:08:56.230 --> 00:08:56.240 align:start position:0% available on GitHub at ethereum Shadow 00:08:56.240 --> 00:08:57.910 align:start position:0% available on GitHub at ethereum Shadow uh<00:08:56.399> right<00:08:56.600> now<00:08:56.800> there's<00:08:57.080> like<00:08:57.279> first<00:08:57.640> class 00:08:57.910 --> 00:08:57.920 align:start position:0% uh right now there's like first class 00:08:57.920 --> 00:08:59.949 align:start position:0% uh right now there's like first class support<00:08:58.279> for<00:08:58.760> GU<00:08:58.959> and<00:08:59.120> lighthous<00:08:59.480> house<00:08:59.800> and 00:08:59.949 --> 00:08:59.959 align:start position:0% support for GU and lighthous house and 00:08:59.959 --> 00:09:02.470 align:start position:0% support for GU and lighthous house and there<00:09:00.040> is<00:09:00.279> some<00:09:01.000> experimental<00:09:02.000> uh<00:09:02.120> support 00:09:02.470 --> 00:09:02.480 align:start position:0% there is some experimental uh support 00:09:02.480 --> 00:09:03.750 align:start position:0% there is some experimental uh support for<00:09:02.720> re<00:09:02.920> and 00:09:03.750 --> 00:09:03.760 align:start position:0% for re and 00:09:03.760 --> 00:09:07.150 align:start position:0% for re and tiu<00:09:04.760> um<00:09:05.640> there<00:09:05.800> is<00:09:06.040> some<00:09:06.320> documentation<00:09:07.000> left 00:09:07.150 --> 00:09:07.160 align:start position:0% tiu um there is some documentation left 00:09:07.160 --> 00:09:10.190 align:start position:0% tiu um there is some documentation left to<00:09:07.240> be<00:09:07.480> written<00:09:08.480> um<00:09:09.120> for<00:09:09.360> basic<00:09:09.600> use<00:09:09.839> cases 00:09:10.190 --> 00:09:10.200 align:start position:0% to be written um for basic use cases 00:09:10.200 --> 00:09:12.829 align:start position:0% to be written um for basic use cases there's<00:09:10.640> like<00:09:11.240> good<00:09:12.000> uh<00:09:12.160> documentation 00:09:12.829 --> 00:09:12.839 align:start position:0% there's like good uh documentation 00:09:12.839 --> 00:09:15.630 align:start position:0% there's like good uh documentation already<00:09:13.360> so<00:09:13.480> you<00:09:13.560> can<00:09:13.680> check<00:09:13.839> it<00:09:13.959> out<00:09:14.839> um<00:09:15.240> and<00:09:15.519> I 00:09:15.630 --> 00:09:15.640 align:start position:0% already so you can check it out um and I 00:09:15.640 --> 00:09:17.949 align:start position:0% already so you can check it out um and I think<00:09:15.959> in<00:09:16.160> some<00:09:16.320> cases<00:09:16.600> usability<00:09:17.160> can<00:09:17.279> be 00:09:17.949 --> 00:09:17.959 align:start position:0% think in some cases usability can be 00:09:17.959 --> 00:09:20.910 align:start position:0% think in some cases usability can be improved<00:09:18.959> um<00:09:19.440> but<00:09:19.600> the<00:09:19.760> hard<00:09:20.000> part<00:09:20.240> is<00:09:20.399> that 00:09:20.910 --> 00:09:20.920 align:start position:0% improved um but the hard part is that 00:09:20.920 --> 00:09:24.190 align:start position:0% improved um but the hard part is that shadow<00:09:21.920> needs<00:09:22.440> a<00:09:22.600> lot<00:09:22.760> of<00:09:23.000> work<00:09:23.640> for<00:09:23.880> all 00:09:24.190 --> 00:09:24.200 align:start position:0% shadow needs a lot of work for all 00:09:24.200 --> 00:09:26.110 align:start position:0% shadow needs a lot of work for all clients<00:09:24.720> to<00:09:25.040> work<00:09:25.360> in 00:09:26.110 --> 00:09:26.120 align:start position:0% clients to work in 00:09:26.120 --> 00:09:28.350 align:start position:0% clients to work in Shadow<00:09:27.120> the<00:09:27.240> reason<00:09:27.480> for<00:09:27.640> that<00:09:27.800> is<00:09:27.959> are 00:09:28.350 --> 00:09:28.360 align:start position:0% Shadow the reason for that is are 00:09:28.360 --> 00:09:32.150 align:start position:0% Shadow the reason for that is are technical<00:09:29.399> basically<00:09:30.320> we<00:09:31.320> need<00:09:31.640> support<00:09:31.959> for 00:09:32.150 --> 00:09:32.160 align:start position:0% technical basically we need support for 00:09:32.160 --> 00:09:36.430 align:start position:0% technical basically we need support for more<00:09:32.680> Linux<00:09:33.079> system<00:09:33.399> calls<00:09:33.720> in<00:09:34.200> shadow<00:09:35.240> um<00:09:36.240> and 00:09:36.430 --> 00:09:36.440 align:start position:0% more Linux system calls in shadow um and 00:09:36.440 --> 00:09:39.750 align:start position:0% more Linux system calls in shadow um and this<00:09:36.560> is<00:09:36.800> a<00:09:36.920> lot<00:09:37.040> of<00:09:37.160> effort<00:09:37.880> unfortunately<00:09:38.800> I 00:09:39.750 --> 00:09:39.760 align:start position:0% this is a lot of effort unfortunately I 00:09:39.760 --> 00:09:43.670 align:start position:0% this is a lot of effort unfortunately I um<00:09:40.279> kind<00:09:40.440> of<00:09:40.560> won't<00:09:40.839> have<00:09:41.079> much<00:09:41.680> uh<00:09:41.880> time<00:09:42.640> so<00:09:43.519> I 00:09:43.670 --> 00:09:43.680 align:start position:0% um kind of won't have much uh time so I 00:09:43.680 --> 00:09:46.069 align:start position:0% um kind of won't have much uh time so I hope<00:09:44.000> that<00:09:44.160> in<00:09:44.320> the<00:09:44.519> coming<00:09:45.480> uh<00:09:45.640> weeks<00:09:45.880> and 00:09:46.069 --> 00:09:46.079 align:start position:0% hope that in the coming uh weeks and 00:09:46.079 --> 00:09:48.790 align:start position:0% hope that in the coming uh weeks and month<00:09:46.399> I<00:09:46.519> can<00:09:47.040> at<00:09:47.160> least<00:09:47.440> help<00:09:48.079> on<00:09:48.240> the<00:09:48.440> side<00:09:48.640> a 00:09:48.790 --> 00:09:48.800 align:start position:0% month I can at least help on the side a 00:09:48.800 --> 00:09:51.630 align:start position:0% month I can at least help on the side a bit<00:09:49.519> to<00:09:49.720> maintain<00:09:50.160> this<00:09:50.480> but<00:09:50.640> I<00:09:50.760> hope<00:09:51.120> to<00:09:51.320> also 00:09:51.630 --> 00:09:51.640 align:start position:0% bit to maintain this but I hope to also 00:09:51.640 --> 00:09:54.710 align:start position:0% bit to maintain this but I hope to also get<00:09:52.000> the<00:09:52.160> attention<00:09:52.640> from<00:09:53.360> from<00:09:53.600> the<00:09:53.800> C<00:09:54.120> devs 00:09:54.710 --> 00:09:54.720 align:start position:0% get the attention from from the C devs 00:09:54.720 --> 00:09:57.710 align:start position:0% get the attention from from the C devs to<00:09:54.959> help<00:09:55.200> me<00:09:55.760> uh<00:09:55.920> or<00:09:56.079> help<00:09:56.360> us<00:09:56.600> all<00:09:57.560> um 00:09:57.710 --> 00:09:57.720 align:start position:0% to help me uh or help us all um 00:09:57.720 --> 00:10:01.550 align:start position:0% to help me uh or help us all um hopefully<00:09:58.360> soon<00:09:58.800> have<00:09:58.959> each<00:09:59.680> for<00:09:59.920> all<00:10:00.079> the 00:10:01.550 --> 00:10:01.560 align:start position:0% hopefully soon have each for all the 00:10:01.560 --> 00:10:04.550 align:start position:0% hopefully soon have each for all the clients<00:10:02.560> okay<00:10:03.360> uh<00:10:03.440> there<00:10:03.560> are<00:10:03.720> some<00:10:04.120> thanks<00:10:04.440> to 00:10:04.550 --> 00:10:04.560 align:start position:0% clients okay uh there are some thanks to 00:10:04.560 --> 00:10:06.790 align:start position:0% clients okay uh there are some thanks to be<00:10:04.720> said<00:10:05.680> uh<00:10:05.839> first<00:10:06.040> of<00:10:06.160> all<00:10:06.360> thanks<00:10:06.519> to<00:10:06.680> my 00:10:06.790 --> 00:10:06.800 align:start position:0% be said uh first of all thanks to my 00:10:06.800 --> 00:10:08.990 align:start position:0% be said uh first of all thanks to my mentors<00:10:07.200> Aran<00:10:07.519> Manning<00:10:07.800> from<00:10:07.959> Sigma<00:10:08.279> Prime 00:10:08.990 --> 00:10:09.000 align:start position:0% mentors Aran Manning from Sigma Prime 00:10:09.000 --> 00:10:11.550 align:start position:0% mentors Aran Manning from Sigma Prime and<00:10:09.320> pup<00:10:09.640> from<00:10:10.000> etherum<00:10:10.399> Foundation<00:10:10.800> research 00:10:11.550 --> 00:10:11.560 align:start position:0% and pup from etherum Foundation research 00:10:11.560 --> 00:10:14.550 align:start position:0% and pup from etherum Foundation research and<00:10:11.760> also<00:10:12.120> thanks<00:10:12.440> for<00:10:12.720> to<00:10:12.920> J<00:10:13.279> oliviera<00:10:14.279> and 00:10:14.550 --> 00:10:14.560 align:start position:0% and also thanks for to J oliviera and 00:10:14.560 --> 00:10:15.949 align:start position:0% and also thanks for to J oliviera and Jimmy<00:10:14.800> Chen<00:10:15.040> from<00:10:15.160> Sigma<00:10:15.560> Prime<00:10:15.800> who 00:10:15.949 --> 00:10:15.959 align:start position:0% Jimmy Chen from Sigma Prime who 00:10:15.959 --> 00:10:18.630 align:start position:0% Jimmy Chen from Sigma Prime who supported<00:10:16.320> me<00:10:16.480> with<00:10:16.640> some<00:10:17.440> of<00:10:17.560> their<00:10:17.760> time<00:10:18.440> and 00:10:18.630 --> 00:10:18.640 align:start position:0% supported me with some of their time and 00:10:18.640 --> 00:10:22.110 align:start position:0% supported me with some of their time and thanks<00:10:18.800> to<00:10:18.959> Anon<00:10:19.279> nurv<00:10:19.920> from<00:10:20.120> consensus<00:10:21.040> uh<00:10:21.200> he 00:10:22.110 --> 00:10:22.120 align:start position:0% thanks to Anon nurv from consensus uh he 00:10:22.120 --> 00:10:24.350 align:start position:0% thanks to Anon nurv from consensus uh he uh<00:10:22.240> spare<00:10:22.600> headed<00:10:23.240> the<00:10:23.360> tech<00:10:23.720> support<00:10:24.040> in<00:10:24.160> a 00:10:24.350 --> 00:10:24.360 align:start position:0% uh spare headed the tech support in a 00:10:24.360 --> 00:10:26.750 align:start position:0% uh spare headed the tech support in a couple<00:10:24.959> last<00:10:25.200> couple<00:10:25.399> of<00:10:25.519> weeks<00:10:26.240> uh<00:10:26.399> thanks<00:10:26.600> to 00:10:26.750 --> 00:10:26.760 align:start position:0% couple last couple of weeks uh thanks to 00:10:26.760 --> 00:10:30.590 align:start position:0% couple last couple of weeks uh thanks to EPF<00:10:27.160> organization<00:10:28.040> uh<00:10:28.160> to<00:10:28.720> Josh<00:10:29.040> and<00:10:29.600> uh<00:10:29.800> Mario 00:10:30.590 --> 00:10:30.600 align:start position:0% EPF organization uh to Josh and uh Mario 00:10:30.600 --> 00:10:32.069 align:start position:0% EPF organization uh to Josh and uh Mario thanks<00:10:30.800> to<00:10:30.920> etherum<00:10:31.240> Foundation<00:10:31.560> for<00:10:31.680> hosting 00:10:32.069 --> 00:10:32.079 align:start position:0% thanks to etherum Foundation for hosting 00:10:32.079 --> 00:10:34.750 align:start position:0% thanks to etherum Foundation for hosting the<00:10:32.200> EPF<00:10:33.040> and<00:10:33.760> uh<00:10:33.920> thank<00:10:34.120> you<00:10:34.279> for<00:10:34.399> to<00:10:34.560> all<00:10:34.640> the 00:10:34.750 --> 00:10:34.760 align:start position:0% the EPF and uh thank you for to all the 00:10:34.760 --> 00:10:37.750 align:start position:0% the EPF and uh thank you for to all the fellows<00:10:35.760> it<00:10:35.920> was<00:10:36.240> really<00:10:36.560> Pleasant<00:10:37.200> uh<00:10:37.560> and 00:10:37.750 --> 00:10:37.760 align:start position:0% fellows it was really Pleasant uh and 00:10:37.760 --> 00:10:41.350 align:start position:0% fellows it was really Pleasant uh and great<00:10:38.079> to<00:10:38.279> work<00:10:38.720> with<00:10:38.880> you<00:10:39.279> all<00:10:40.279> and<00:10:40.560> finally 00:10:41.350 --> 00:10:41.360 align:start position:0% great to work with you all and finally 00:10:41.360 --> 00:10:44.190 align:start position:0% great to work with you all and finally I'm<00:10:41.519> going<00:10:41.720> to<00:10:41.959> pluck<00:10:42.360> my<00:10:43.000> talk<00:10:43.240> tomorrow<00:10:43.800> or 00:10:44.190 --> 00:10:44.200 align:start position:0% I'm going to pluck my talk tomorrow or 00:10:44.200 --> 00:10:47.030 align:start position:0% I'm going to pluck my talk tomorrow or our<00:10:44.519> talk<00:10:44.880> tomorrow<00:10:45.880> um<00:10:46.160> simulating<00:10:46.800> an 00:10:47.030 --> 00:10:47.040 align:start position:0% our talk tomorrow um simulating an 00:10:47.040 --> 00:10:49.590 align:start position:0% our talk tomorrow um simulating an ethereum<00:10:47.480> Network<00:10:48.320> scale<00:10:48.920> which<00:10:49.040> will<00:10:49.279> go 00:10:49.590 --> 00:10:49.600 align:start position:0% ethereum Network scale which will go 00:10:49.600 --> 00:10:51.790 align:start position:0% ethereum Network scale which will go more<00:10:49.800> into<00:10:50.000> detail<00:10:50.360> on<00:10:50.600> how<00:10:50.839> you<00:10:51.000> can<00:10:51.320> run<00:10:51.600> the 00:10:51.790 --> 00:10:51.800 align:start position:0% more into detail on how you can run the 00:10:51.800 --> 00:10:54.389 align:start position:0% more into detail on how you can run the simulation<00:10:52.480> yourself<00:10:53.040> so<00:10:53.720> maybe<00:10:54.000> see<00:10:54.200> some<00:10:54.320> of 00:10:54.389 --> 00:10:54.399 align:start position:0% simulation yourself so maybe see some of 00:10:54.399 --> 00:10:57.829 align:start position:0% simulation yourself so maybe see some of you<00:10:54.600> there<00:10:54.880> on<00:10:55.079> stage<00:10:55.399> one<00:10:55.839> at<00:10:56.160> 10<00:10:56.600> 1<00:10:56.839> p.m. 00:10:57.829 --> 00:10:57.839 align:start position:0% you there on stage one at 10 1 p.m. 00:10:57.839 --> 00:11:02.829 align:start position:0% you there on stage one at 10 1 p.m. thank<00:10:57.959> you<00:10:58.040> for<00:10:58.160> your<00:10:58.279> attention 00:11:02.829 --> 00:11:02.839 align:start position:0% 00:11:02.839 --> 00:11:06.829 align:start position:0% all<00:11:03.040> right<00:11:03.279> any<00:11:03.519> questions<00:11:03.880> for 00:11:06.829 --> 00:11:06.839 align:start position:0% 00:11:06.839 --> 00:11:09.430 align:start position:0% Daniel<00:11:07.839> um<00:11:08.040> hi<00:11:08.320> just<00:11:08.600> a<00:11:08.680> couple<00:11:08.959> questions<00:11:09.320> one 00:11:09.430 --> 00:11:09.440 align:start position:0% Daniel um hi just a couple questions one 00:11:09.440 --> 00:11:10.990 align:start position:0% Daniel um hi just a couple questions one is<00:11:09.680> um<00:11:09.839> when<00:11:09.959> you're<00:11:10.279> making<00:11:10.519> all<00:11:10.639> of<00:11:10.800> these 00:11:10.990 --> 00:11:11.000 align:start position:0% is um when you're making all of these 00:11:11.000 --> 00:11:13.350 align:start position:0% is um when you're making all of these changes<00:11:11.720> to<00:11:12.120> do<00:11:12.320> these<00:11:12.519> simulations<00:11:13.079> are<00:11:13.200> you 00:11:13.350 --> 00:11:13.360 align:start position:0% changes to do these simulations are you 00:11:13.360 --> 00:11:14.790 align:start position:0% changes to do these simulations are you actually<00:11:13.560> like<00:11:13.720> updating<00:11:14.079> the<00:11:14.240> client<00:11:14.519> code 00:11:14.790 --> 00:11:14.800 align:start position:0% actually like updating the client code 00:11:14.800 --> 00:11:16.590 align:start position:0% actually like updating the client code or<00:11:14.920> is<00:11:15.040> it<00:11:15.279> kind<00:11:15.360> of<00:11:15.480> like<00:11:15.600> Network 00:11:16.590 --> 00:11:16.600 align:start position:0% or is it kind of like Network 00:11:16.600 --> 00:11:19.550 align:start position:0% or is it kind of like Network configurations<00:11:17.600> um<00:11:18.240> yeah<00:11:18.519> this<00:11:18.639> is<00:11:18.880> like<00:11:19.399> the 00:11:19.550 --> 00:11:19.560 align:start position:0% configurations um yeah this is like the 00:11:19.560 --> 00:11:23.470 align:start position:0% configurations um yeah this is like the great<00:11:19.839> advantage<00:11:20.880> to<00:11:21.880> change<00:11:22.560> these<00:11:23.000> or<00:11:23.320> to 00:11:23.470 --> 00:11:23.480 align:start position:0% great advantage to change these or to 00:11:23.480 --> 00:11:26.710 align:start position:0% great advantage to change these or to test<00:11:23.639> these<00:11:23.839> changes<00:11:24.720> I<00:11:25.320> actually<00:11:26.000> can<00:11:26.240> change 00:11:26.710 --> 00:11:26.720 align:start position:0% test these changes I actually can change 00:11:26.720 --> 00:11:28.910 align:start position:0% test these changes I actually can change just<00:11:26.880> the<00:11:27.040> client<00:11:27.440> I<00:11:27.560> don't<00:11:27.760> need<00:11:27.959> to<00:11:28.519> develop 00:11:28.910 --> 00:11:28.920 align:start position:0% just the client I don't need to develop 00:11:28.920 --> 00:11:31.870 align:start position:0% just the client I don't need to develop anything<00:11:29.639> just<00:11:30.040> for<00:11:30.560> that<00:11:30.880> I<00:11:31.360> changed<00:11:31.720> the 00:11:31.870 --> 00:11:31.880 align:start position:0% anything just for that I changed the 00:11:31.880 --> 00:11:35.710 align:start position:0% anything just for that I changed the actual<00:11:32.200> client<00:11:33.040> but<00:11:33.200> for<00:11:33.560> like<00:11:34.399> the<00:11:35.120> things<00:11:35.519> I 00:11:35.710 --> 00:11:35.720 align:start position:0% actual client but for like the things I 00:11:35.720 --> 00:11:38.389 align:start position:0% actual client but for like the things I showed<00:11:36.160> you<00:11:36.959> I<00:11:37.040> think<00:11:37.279> I<00:11:37.399> only<00:11:37.560> needed<00:11:37.839> to 00:11:38.389 --> 00:11:38.399 align:start position:0% showed you I think I only needed to 00:11:38.399 --> 00:11:41.710 align:start position:0% showed you I think I only needed to varry<00:11:38.800> the<00:11:39.120> configuration<00:11:40.120> a<00:11:40.480> bit<00:11:41.399> right<00:11:41.600> but 00:11:41.710 --> 00:11:41.720 align:start position:0% varry the configuration a bit right but 00:11:41.720 --> 00:11:43.269 align:start position:0% varry the configuration a bit right but I<00:11:41.880> also<00:11:42.079> did<00:11:42.279> some<00:11:42.440> changes<00:11:42.800> that<00:11:43.040> actually 00:11:43.269 --> 00:11:43.279 align:start position:0% I also did some changes that actually 00:11:43.279 --> 00:11:45.910 align:start position:0% I also did some changes that actually tried<00:11:43.560> to<00:11:44.079> fix<00:11:44.440> these<00:11:44.600> underlying<00:11:45.160> problems 00:11:45.910 --> 00:11:45.920 align:start position:0% tried to fix these underlying problems 00:11:45.920 --> 00:11:48.069 align:start position:0% tried to fix these underlying problems uh<00:11:46.200> in<00:11:46.360> L<00:11:46.839> itself<00:11:47.320> cool<00:11:47.639> yeah<00:11:47.760> and<00:11:47.880> then<00:11:48.000> I 00:11:48.069 --> 00:11:48.079 align:start position:0% uh in L itself cool yeah and then I 00:11:48.079 --> 00:11:49.430 align:start position:0% uh in L itself cool yeah and then I guess<00:11:48.200> my<00:11:48.320> other<00:11:48.519> question<00:11:48.839> um<00:11:49.000> so<00:11:49.240> are<00:11:49.320> you 00:11:49.430 --> 00:11:49.440 align:start position:0% guess my other question um so are you 00:11:49.440 --> 00:11:51.069 align:start position:0% guess my other question um so are you starting<00:11:49.800> simulations<00:11:50.279> from<00:11:50.480> like<00:11:50.560> a<00:11:50.680> Genesis 00:11:51.069 --> 00:11:51.079 align:start position:0% starting simulations from like a Genesis 00:11:51.079 --> 00:11:52.470 align:start position:0% starting simulations from like a Genesis state<00:11:51.279> or<00:11:51.399> is<00:11:51.480> it<00:11:51.600> like<00:11:51.680> a<00:11:51.720> fork<00:11:51.959> of<00:11:52.079> main<00:11:52.320> net 00:11:52.470 --> 00:11:52.480 align:start position:0% state or is it like a fork of main net 00:11:52.480 --> 00:11:55.590 align:start position:0% state or is it like a fork of main net and<00:11:52.680> can<00:11:52.800> you<00:11:52.920> do<00:11:53.079> Forks<00:11:53.760> of<00:11:54.000> like<00:11:54.160> existing 00:11:55.590 --> 00:11:55.600 align:start position:0% and can you do Forks of like existing 00:11:55.600 --> 00:11:59.430 align:start position:0% and can you do Forks of like existing networks<00:11:56.600> well<00:11:57.440> um<00:11:57.920> I<00:11:58.079> I<00:11:58.200> start<00:11:58.440> from<00:11:58.560> a<00:11:58.760> j<00:11:59.279> St 00:11:59.430 --> 00:11:59.440 align:start position:0% networks well um I I start from a j St 00:11:59.440 --> 00:12:01.230 align:start position:0% networks well um I I start from a j St my<00:11:59.560> tool<00:11:59.760> supports<00:12:00.200> this<00:12:00.399> it<00:12:00.600> it<00:12:00.800> just<00:12:01.000> does 00:12:01.230 --> 00:12:01.240 align:start position:0% my tool supports this it it just does 00:12:01.240 --> 00:12:04.430 align:start position:0% my tool supports this it it just does this<00:12:01.399> for<00:12:01.600> us<00:12:02.040> uh<00:12:02.160> which<00:12:02.279> is<00:12:02.480> nice<00:12:03.360> and<00:12:03.760> forking 00:12:04.430 --> 00:12:04.440 align:start position:0% this for us uh which is nice and forking 00:12:04.440 --> 00:12:07.509 align:start position:0% this for us uh which is nice and forking main<00:12:05.200> net<00:12:06.200> I<00:12:06.279> mean<00:12:06.720> I'm<00:12:06.839> aware<00:12:07.120> that<00:12:07.240> they<00:12:07.360> are 00:12:07.509 --> 00:12:07.519 align:start position:0% main net I mean I'm aware that they are 00:12:07.519 --> 00:12:09.629 align:start position:0% main net I mean I'm aware that they are Shadow<00:12:07.800> Forks<00:12:08.240> they<00:12:08.360> are<00:12:08.560> unrelated<00:12:09.120> to<00:12:09.480> the 00:12:09.629 --> 00:12:09.639 align:start position:0% Shadow Forks they are unrelated to the 00:12:09.639 --> 00:12:12.509 align:start position:0% Shadow Forks they are unrelated to the name<00:12:09.920> of<00:12:10.360> uh<00:12:10.480> the<00:12:10.800> simulation<00:12:11.200> tool<00:12:12.120> um<00:12:12.399> I 00:12:12.509 --> 00:12:12.519 align:start position:0% name of uh the simulation tool um I 00:12:12.519 --> 00:12:16.269 align:start position:0% name of uh the simulation tool um I haven't<00:12:12.760> tried<00:12:13.440> it<00:12:14.440> uh<00:12:14.639> the<00:12:14.880> problem<00:12:15.480> is<00:12:15.800> that 00:12:16.269 --> 00:12:16.279 align:start position:0% haven't tried it uh the problem is that 00:12:16.279 --> 00:12:20.750 align:start position:0% haven't tried it uh the problem is that the<00:12:16.760> Genesis<00:12:17.760> state<00:12:18.279> is<00:12:18.760> quite<00:12:19.440> large<00:12:20.440> and 00:12:20.750 --> 00:12:20.760 align:start position:0% the Genesis state is quite large and 00:12:20.760 --> 00:12:23.550 align:start position:0% the Genesis state is quite large and this<00:12:21.040> might<00:12:21.839> actually<00:12:22.120> be<00:12:22.360> really<00:12:22.600> hard<00:12:22.839> to 00:12:23.550 --> 00:12:23.560 align:start position:0% this might actually be really hard to 00:12:23.560 --> 00:12:27.310 align:start position:0% this might actually be really hard to simulate<00:12:24.279> like<00:12:24.440> on<00:12:24.560> a<00:12:24.800> single<00:12:25.800> uh<00:12:26.360> node<00:12:26.880> right 00:12:27.310 --> 00:12:27.320 align:start position:0% simulate like on a single uh node right 00:12:27.320 --> 00:12:29.189 align:start position:0% simulate like on a single uh node right we<00:12:27.399> have<00:12:27.720> all<00:12:27.880> the<00:12:28.000> simulation<00:12:28.360> running<00:12:28.680> on<00:12:28.959> a 00:12:29.189 --> 00:12:29.199 align:start position:0% we have all the simulation running on a 00:12:29.199 --> 00:12:31.069 align:start position:0% we have all the simulation running on a single<00:12:29.480> server<00:12:30.160> and<00:12:30.320> that<00:12:30.480> might<00:12:30.639> be<00:12:30.760> hard<00:12:30.959> to 00:12:31.069 --> 00:12:31.079 align:start position:0% single server and that might be hard to 00:12:31.079 --> 00:12:33.230 align:start position:0% single server and that might be hard to have<00:12:31.240> multiple<00:12:31.720> clients<00:12:32.120> in<00:12:32.320> parallel<00:12:33.079> uh 00:12:33.230 --> 00:12:33.240 align:start position:0% have multiple clients in parallel uh 00:12:33.240 --> 00:12:35.350 align:start position:0% have multiple clients in parallel uh working<00:12:33.519> on<00:12:33.800> that<00:12:34.199> so<00:12:34.440> I<00:12:34.880> guess<00:12:35.040> it's<00:12:35.199> not 00:12:35.350 --> 00:12:35.360 align:start position:0% working on that so I guess it's not 00:12:35.360 --> 00:12:42.509 align:start position:0% working on that so I guess it's not really 00:12:42.509 --> 00:12:42.519 align:start position:0% 00:12:42.519 --> 00:12:45.030 align:start position:0% feasible<00:12:43.519> so<00:12:43.720> I<00:12:43.839> was<00:12:44.000> wondering<00:12:44.360> like<00:12:44.680> once 00:12:45.030 --> 00:12:45.040 align:start position:0% feasible so I was wondering like once 00:12:45.040 --> 00:12:47.590 align:start position:0% feasible so I was wondering like once the<00:12:45.399> simulation<00:12:46.040> completes<00:12:46.600> can<00:12:46.760> we<00:12:46.920> see<00:12:47.199> like 00:12:47.590 --> 00:12:47.600 align:start position:0% the simulation completes can we see like 00:12:47.600 --> 00:12:49.949 align:start position:0% the simulation completes can we see like consolidated<00:12:48.440> metrics<00:12:48.920> on<00:12:49.079> the<00:12:49.480> Node<00:12:49.800> or 00:12:49.949 --> 00:12:49.959 align:start position:0% consolidated metrics on the Node or 00:12:49.959 --> 00:12:51.870 align:start position:0% consolidated metrics on the Node or something<00:12:50.480> logs<00:12:50.920> something<00:12:51.199> like<00:12:51.360> that<00:12:51.680> very 00:12:51.870 --> 00:12:51.880 align:start position:0% something logs something like that very 00:12:51.880 --> 00:12:54.470 align:start position:0% something logs something like that very good<00:12:52.120> question<00:12:52.800> uh<00:12:52.920> this<00:12:53.040> is<00:12:53.240> how<00:12:53.440> I<00:12:53.639> evaluated 00:12:54.470 --> 00:12:54.480 align:start position:0% good question uh this is how I evaluated 00:12:54.480 --> 00:12:56.790 align:start position:0% good question uh this is how I evaluated uh<00:12:54.639> those<00:12:54.839> simulations<00:12:55.839> um<00:12:56.199> I<00:12:56.320> kind<00:12:56.440> of<00:12:56.560> forgot 00:12:56.790 --> 00:12:56.800 align:start position:0% uh those simulations um I kind of forgot 00:12:56.800 --> 00:13:00.550 align:start position:0% uh those simulations um I kind of forgot to<00:12:56.880> mention<00:12:57.240> that<00:12:57.399> here<00:12:58.320> um<00:12:58.880> this<00:12:59.560> simulation 00:13:00.550 --> 00:13:00.560 align:start position:0% to mention that here um this simulation 00:13:00.560 --> 00:13:03.310 align:start position:0% to mention that here um this simulation um<00:13:00.800> you<00:13:01.120> it<00:13:01.199> is<00:13:01.440> really<00:13:02.120> really<00:13:02.320> easy<00:13:02.600> to<00:13:02.959> add<00:13:03.120> a 00:13:03.310 --> 00:13:03.320 align:start position:0% um you it is really really easy to add a 00:13:03.320 --> 00:13:05.629 align:start position:0% um you it is really really easy to add a Prometheus<00:13:03.880> note<00:13:04.440> in<00:13:04.920> the<00:13:05.160> simulation 00:13:05.629 --> 00:13:05.639 align:start position:0% Prometheus note in the simulation 00:13:05.639 --> 00:13:07.550 align:start position:0% Prometheus note in the simulation configuration<00:13:06.519> and<00:13:06.680> that<00:13:06.839> automatically 00:13:07.550 --> 00:13:07.560 align:start position:0% configuration and that automatically 00:13:07.560 --> 00:13:09.910 align:start position:0% configuration and that automatically gets<00:13:07.800> configured<00:13:08.399> to<00:13:08.800> pull<00:13:09.360> uh<00:13:09.440> the<00:13:09.560> metrics 00:13:09.910 --> 00:13:09.920 align:start position:0% gets configured to pull uh the metrics 00:13:09.920 --> 00:13:12.269 align:start position:0% gets configured to pull uh the metrics from<00:13:10.120> all<00:13:10.320> the<00:13:10.480> lighthouse<00:13:11.000> clients<00:13:12.000> and<00:13:12.199> in 00:13:12.269 --> 00:13:12.279 align:start position:0% from all the lighthouse clients and in 00:13:12.279 --> 00:13:14.750 align:start position:0% from all the lighthouse clients and in the<00:13:12.399> end<00:13:12.560> we<00:13:12.680> have<00:13:12.880> like<00:13:13.040> one<00:13:13.320> huge<00:13:14.160> Prometheus 00:13:14.750 --> 00:13:14.760 align:start position:0% the end we have like one huge Prometheus 00:13:14.760 --> 00:13:17.990 align:start position:0% the end we have like one huge Prometheus database<00:13:15.760> which<00:13:15.959> allows<00:13:16.320> us<00:13:16.560> to<00:13:17.320> just<00:13:17.639> pull<00:13:17.839> up 00:13:17.990 --> 00:13:18.000 align:start position:0% database which allows us to just pull up 00:13:18.000 --> 00:13:21.269 align:start position:0% database which allows us to just pull up some<00:13:18.279> grafana<00:13:19.279> uh<00:13:19.440> dashboards<00:13:20.000> or<00:13:20.360> any<00:13:20.600> other 00:13:21.269 --> 00:13:21.279 align:start position:0% some grafana uh dashboards or any other 00:13:21.279 --> 00:13:23.670 align:start position:0% some grafana uh dashboards or any other analysis<00:13:22.199> also<00:13:22.399> we<00:13:22.480> have<00:13:22.600> all<00:13:22.720> the<00:13:22.839> locks<00:13:23.480> so 00:13:23.670 --> 00:13:23.680 align:start position:0% analysis also we have all the locks so 00:13:23.680 --> 00:13:25.550 align:start position:0% analysis also we have all the locks so we<00:13:23.800> can<00:13:23.959> also<00:13:24.519> look<00:13:24.720> into<00:13:25.000> those<00:13:25.199> if<00:13:25.320> there<00:13:25.399> are 00:13:25.550 --> 00:13:25.560 align:start position:0% we can also look into those if there are 00:13:25.560 --> 00:13:27.949 align:start position:0% we can also look into those if there are any<00:13:25.760> like<00:13:26.040> specific<00:13:26.440> noes<00:13:26.920> that<00:13:27.399> seem<00:13:27.639> to<00:13:27.760> be 00:13:27.949 --> 00:13:27.959 align:start position:0% any like specific noes that seem to be 00:13:27.959 --> 00:13:40.829 align:start position:0% any like specific noes that seem to be acting<00:13:28.160> strange<00:13:28.519> or<00:13:28.680> something 00:13:40.829 --> 00:13:40.839 align:start position:0% 00:13:40.839 --> 00:13:45.870 align:start position:0% yeah<00:13:42.199> right<00:13:43.320> um<00:13:44.320> You<00:13:44.440> can<00:13:44.639> also<00:13:44.880> like<00:13:45.440> run<00:13:45.680> a 00:13:45.870 --> 00:13:45.880 align:start position:0% yeah right um You can also like run a 00:13:45.880 --> 00:13:48.870 align:start position:0% yeah right um You can also like run a note<00:13:46.440> on<00:13:46.800> a<00:13:47.399> data<00:13:47.680> directory<00:13:48.120> that<00:13:48.240> has<00:13:48.399> been 00:13:48.870 --> 00:13:48.880 align:start position:0% note on a data directory that has been 00:13:48.880 --> 00:13:51.069 align:start position:0% note on a data directory that has been generated<00:13:49.480> by<00:13:49.639> the<00:13:49.800> simulation<00:13:50.399> afterwards 00:13:51.069 --> 00:13:51.079 align:start position:0% generated by the simulation afterwards 00:13:51.079 --> 00:13:53.990 align:start position:0% generated by the simulation afterwards it's<00:13:51.199> a<00:13:51.320> bit<00:13:51.880> weird<00:13:52.680> because<00:13:53.680> uh<00:13:53.839> the 00:13:53.990 --> 00:13:54.000 align:start position:0% it's a bit weird because uh the 00:13:54.000 --> 00:13:55.670 align:start position:0% it's a bit weird because uh the simulation<00:13:54.480> time<00:13:54.680> always<00:13:55.040> takes<00:13:55.360> place<00:13:55.560> in 00:13:55.670 --> 00:13:55.680 align:start position:0% simulation time always takes place in 00:13:55.680 --> 00:13:58.189 align:start position:0% simulation time always takes place in the<00:13:55.800> year<00:13:55.959> 2000<00:13:56.680> so<00:13:56.959> it's<00:13:57.199> really<00:13:57.440> old<00:13:57.759> data<00:13:58.040> to 00:13:58.189 --> 00:13:58.199 align:start position:0% the year 2000 so it's really old data to 00:13:58.199 --> 00:14:00.069 align:start position:0% the year 2000 so it's really old data to the<00:13:58.279> note<00:13:58.519> if<00:13:58.600> you<00:13:58.680> started<00:13:59.480> right<00:13:59.639> now<00:13:59.959> but 00:14:00.069 --> 00:14:00.079 align:start position:0% the note if you started right now but 00:14:00.079 --> 00:14:01.910 align:start position:0% the note if you started right now but you<00:14:00.160> can<00:14:00.360> run<00:14:00.560> that<00:14:00.720> Noe<00:14:01.000> and<00:14:01.079> you<00:14:01.240> can<00:14:01.560> attach 00:14:01.910 --> 00:14:01.920 align:start position:0% you can run that Noe and you can attach 00:14:01.920 --> 00:14:04.110 align:start position:0% you can run that Noe and you can attach like<00:14:02.120> a<00:14:02.320> block<00:14:02.720> Explorer<00:14:03.360> or<00:14:03.639> the<00:14:03.759> Explorer 00:14:04.110 --> 00:14:04.120 align:start position:0% like a block Explorer or the Explorer 00:14:04.120 --> 00:14:06.949 align:start position:0% like a block Explorer or the Explorer for<00:14:04.279> example<00:14:04.600> by<00:14:04.800> the<00:14:04.880> e<00:14:05.399> p<00:14:05.639> Ops<00:14:05.880> Team<00:14:06.360> to<00:14:06.600> it 00:14:06.949 --> 00:14:06.959 align:start position:0% for example by the e p Ops Team to it 00:14:06.959 --> 00:14:08.749 align:start position:0% for example by the e p Ops Team to it it's<00:14:07.199> just<00:14:07.320> a<00:14:07.440> bit<00:14:07.600> wonky<00:14:08.320> because<00:14:08.519> of<00:14:08.600> the 00:14:08.749 --> 00:14:08.759 align:start position:0% it's just a bit wonky because of the 00:14:08.759 --> 00:14:22.749 align:start position:0% it's just a bit wonky because of the timing 00:14:22.749 --> 00:14:22.759 align:start position:0% 00:14:22.759 --> 00:14:24.870 align:start position:0% issue<00:14:23.759> yeah 00:14:24.870 --> 00:14:24.880 align:start position:0% issue yeah 00:14:24.880 --> 00:14:27.509 align:start position:0% issue yeah basically<00:14:25.880> the<00:14:26.079> simulation<00:14:26.720> Shadow<00:14:27.079> starts 00:14:27.509 --> 00:14:27.519 align:start position:0% basically the simulation Shadow starts 00:14:27.519 --> 00:14:29.670 align:start position:0% basically the simulation Shadow starts the<00:14:27.639> simulation<00:14:28.160> time<00:14:28.440> always<00:14:29.120> at<00:14:29.199> the<00:14:29.320> 1<00:14:29.560> of 00:14:29.670 --> 00:14:29.680 align:start position:0% the simulation time always at the 1 of 00:14:29.680 --> 00:14:31.910 align:start position:0% the simulation time always at the 1 of January<00:14:30.079> in<00:14:30.160> the<00:14:30.279> year<00:14:30.519> 2000<00:14:31.199> so<00:14:31.600> every<00:14:31.800> time 00:14:31.910 --> 00:14:31.920 align:start position:0% January in the year 2000 so every time 00:14:31.920 --> 00:14:35.949 align:start position:0% January in the year 2000 so every time you<00:14:32.079> do<00:14:32.199> a<00:14:32.360> Prometheus<00:14:32.920> query<00:14:33.839> or<00:14:34.839> um<00:14:35.800> yeah 00:14:35.949 --> 00:14:35.959 align:start position:0% you do a Prometheus query or um yeah 00:14:35.959 --> 00:14:37.430 align:start position:0% you do a Prometheus query or um yeah look<00:14:36.160> into<00:14:36.560> the<00:14:36.639> block<00:14:36.839> explore<00:14:37.160> you<00:14:37.240> have<00:14:37.360> to 00:14:37.430 --> 00:14:37.440 align:start position:0% look into the block explore you have to 00:14:37.440 --> 00:14:40.269 align:start position:0% look into the block explore you have to keep<00:14:37.600> in<00:14:37.759> mind<00:14:38.160> that<00:14:38.279> you<00:14:38.480> have<00:14:38.600> to<00:14:39.600> act<00:14:39.880> as<00:14:40.079> if 00:14:40.269 --> 00:14:40.279 align:start position:0% keep in mind that you have to act as if 00:14:40.279 --> 00:14:44.670 align:start position:0% keep in mind that you have to act as if it<00:14:40.399> were<00:14:40.639> the<00:14:40.759> year<00:14:41.320> 2000 00:14:44.670 --> 00:14:44.680 align:start position:0% 00:14:44.680 --> 00:14:46.990 align:start position:0% yeah<00:14:45.680> any<00:14:46.000> final 00:14:46.990 --> 00:14:47.000 align:start position:0% yeah any final 00:14:47.000 --> 00:14:50.110 align:start position:0% yeah any final questions<00:14:48.000> there<00:14:48.120> are<00:14:48.320> some<00:14:48.800> up<00:14:49.040> there<00:14:49.759> oh<00:14:49.959> we 00:14:50.110 --> 00:14:50.120 align:start position:0% questions there are some up there oh we 00:14:50.120 --> 00:14:53.710 align:start position:0% questions there are some up there oh we got<00:14:50.320> one<00:14:50.519> more<00:14:51.079> uh<00:14:51.199> how<00:14:51.360> is<00:14:51.440> it<00:14:51.639> different<00:14:51.880> from 00:14:53.710 --> 00:14:53.720 align:start position:0% got one more uh how is it different from 00:14:53.720 --> 00:14:57.189 align:start position:0% got one more uh how is it different from curtosis<00:14:54.720> okay<00:14:55.000> in<00:14:55.120> a<00:14:55.240> nutshell<00:14:56.199> uh 00:14:57.189 --> 00:14:57.199 align:start position:0% curtosis okay in a nutshell uh 00:14:57.199 --> 00:15:01.870 align:start position:0% curtosis okay in a nutshell uh kosis<00:14:58.199> um<00:14:58.800> you<00:14:59.040> you<00:14:59.240> cannot<00:15:00.120> run<00:15:01.040> networks<00:15:01.680> at 00:15:01.870 --> 00:15:01.880 align:start position:0% kosis um you you cannot run networks at 00:15:01.880 --> 00:15:04.470 align:start position:0% kosis um you you cannot run networks at of<00:15:02.079> this<00:15:02.279> scale<00:15:02.720> on<00:15:03.000> a<00:15:03.199> single<00:15:03.920> server<00:15:04.320> with 00:15:04.470 --> 00:15:04.480 align:start position:0% of this scale on a single server with 00:15:04.480 --> 00:15:07.790 align:start position:0% of this scale on a single server with kosis<00:15:05.199> because<00:15:05.480> kosis<00:15:06.079> is<00:15:06.199> not<00:15:06.440> capable<00:15:06.880> of 00:15:07.790 --> 00:15:07.800 align:start position:0% kosis because kosis is not capable of 00:15:07.800 --> 00:15:09.910 align:start position:0% kosis because kosis is not capable of like<00:15:08.160> pretending<00:15:08.639> to<00:15:08.800> the<00:15:09.000> processes<00:15:09.720> that 00:15:09.910 --> 00:15:09.920 align:start position:0% like pretending to the processes that 00:15:09.920 --> 00:15:11.749 align:start position:0% like pretending to the processes that time<00:15:10.160> is<00:15:10.360> running<00:15:10.720> faster<00:15:11.000> or<00:15:11.120> slower<00:15:11.440> than<00:15:11.560> it 00:15:11.749 --> 00:15:11.759 align:start position:0% time is running faster or slower than it 00:15:11.759 --> 00:15:16.949 align:start position:0% time is running faster or slower than it actually<00:15:12.079> is<00:15:12.399> basically<00:15:13.360> like<00:15:14.279> um<00:15:15.000> having<00:15:16.000> a 00:15:16.949 --> 00:15:16.959 align:start position:0% actually is basically like um having a 00:15:16.959 --> 00:15:20.990 align:start position:0% actually is basically like um having a separated<00:15:17.720> simulation<00:15:18.360> time<00:15:18.639> from<00:15:18.880> real<00:15:19.320> time 00:15:20.990 --> 00:15:21.000 align:start position:0% separated simulation time from real time 00:15:21.000 --> 00:15:23.509 align:start position:0% separated simulation time from real time um<00:15:22.000> yeah<00:15:22.240> I<00:15:22.320> would<00:15:22.519> say<00:15:22.680> that<00:15:22.800> is<00:15:23.160> the<00:15:23.279> main 00:15:23.509 --> 00:15:23.519 align:start position:0% um yeah I would say that is the main 00:15:23.519 --> 00:15:25.949 align:start position:0% um yeah I would say that is the main difference<00:15:24.199> that<00:15:24.320> you<00:15:24.399> can<00:15:24.560> scale<00:15:25.000> way<00:15:25.440> higher 00:15:25.949 --> 00:15:25.959 align:start position:0% difference that you can scale way higher 00:15:25.959 --> 00:15:31.069 align:start position:0% difference that you can scale way higher with<00:15:26.560> uh<00:15:27.040> shadow 00:15:31.069 --> 00:15:31.079 align:start position:0% 00:15:31.079 --> 00:15:34.400 align:start position:0% all<00:15:31.279> right<00:15:31.480> thanks<00:15:31.800> Daniel 00:15:34.400 --> 00:15:34.410 align:start position:0% all right thanks Daniel 00:15:34.410 --> 00:15:37.650 align:start position:0% all right thanks Daniel [Applause]