WEBVTT Kind: captions Language: en 00:00:01.110 --> 00:00:06.650 align:start position:0% [Music] 00:00:06.650 --> 00:00:06.660 align:start position:0% 00:00:06.660 --> 00:00:10.509 align:start position:0% [Music] 00:00:10.509 --> 00:00:10.519 align:start position:0% [Music] 00:00:10.519 --> 00:00:13.270 align:start position:0% [Music] wow<00:00:10.679> a<00:00:10.759> lot<00:00:10.920> of<00:00:11.040> fans<00:00:11.280> in<00:00:11.400> the<00:00:11.799> audience<00:00:12.799> yeah 00:00:13.270 --> 00:00:13.280 align:start position:0% wow a lot of fans in the audience yeah 00:00:13.280 --> 00:00:16.510 align:start position:0% wow a lot of fans in the audience yeah hello<00:00:13.679> everybody<00:00:14.480> hi<00:00:15.160> everybody<00:00:16.160> yeah<00:00:16.279> today 00:00:16.510 --> 00:00:16.520 align:start position:0% hello everybody hi everybody yeah today 00:00:16.520 --> 00:00:19.349 align:start position:0% hello everybody hi everybody yeah today we'll<00:00:16.720> talk<00:00:16.960> about<00:00:17.680> uh<00:00:18.320> FK<00:00:18.560> Choice<00:00:18.880> compliance 00:00:19.349 --> 00:00:19.359 align:start position:0% we'll talk about uh FK Choice compliance 00:00:19.359 --> 00:00:22.109 align:start position:0% we'll talk about uh FK Choice compliance and<00:00:19.560> how<00:00:19.720> we<00:00:19.960> approached<00:00:20.400> it<00:00:21.240> and<00:00:21.439> to<00:00:21.680> start 00:00:22.109 --> 00:00:22.119 align:start position:0% and how we approached it and to start 00:00:22.119 --> 00:00:24.950 align:start position:0% and how we approached it and to start let's<00:00:22.800> understand<00:00:23.240> uh<00:00:23.400> first<00:00:23.920> why<00:00:24.400> FK<00:00:24.680> Choice 00:00:24.950 --> 00:00:24.960 align:start position:0% let's understand uh first why FK Choice 00:00:24.960 --> 00:00:27.669 align:start position:0% let's understand uh first why FK Choice compliance<00:00:25.680> is<00:00:25.960> important<00:00:26.960> uh<00:00:27.080> the<00:00:27.160> FK<00:00:27.439> Choice 00:00:27.669 --> 00:00:27.679 align:start position:0% compliance is important uh the FK Choice 00:00:27.679 --> 00:00:29.710 align:start position:0% compliance is important uh the FK Choice rule<00:00:28.080> is<00:00:28.240> the<00:00:28.400> part<00:00:28.599> of<00:00:28.760> etherum<00:00:29.160> protocols 00:00:29.710 --> 00:00:29.720 align:start position:0% rule is the part of etherum protocols 00:00:29.720 --> 00:00:32.310 align:start position:0% rule is the part of etherum protocols that<00:00:30.080> that<00:00:30.240> decides<00:00:30.759> on<00:00:31.080> the<00:00:31.720> head<00:00:31.920> of<00:00:32.119> the 00:00:32.310 --> 00:00:32.320 align:start position:0% that that decides on the head of the 00:00:32.320 --> 00:00:34.709 align:start position:0% that that decides on the head of the canonical<00:00:32.840> chain<00:00:33.760> uh<00:00:33.879> that<00:00:34.000> is<00:00:34.160> the<00:00:34.320> chain 00:00:34.709 --> 00:00:34.719 align:start position:0% canonical chain uh that is the chain 00:00:34.719 --> 00:00:36.350 align:start position:0% canonical chain uh that is the chain that<00:00:34.840> is<00:00:35.120> the<00:00:35.239> chain<00:00:35.600> that<00:00:35.719> you<00:00:35.840> use<00:00:36.120> to 00:00:36.350 --> 00:00:36.360 align:start position:0% that is the chain that you use to 00:00:36.360 --> 00:00:38.270 align:start position:0% that is the chain that you use to confirm<00:00:36.800> your<00:00:37.040> transactions<00:00:37.800> that<00:00:38.000> is<00:00:38.160> the 00:00:38.270 --> 00:00:38.280 align:start position:0% confirm your transactions that is the 00:00:38.280 --> 00:00:41.350 align:start position:0% confirm your transactions that is the chain<00:00:38.719> that<00:00:39.000> will<00:00:39.239> be<00:00:39.800> eventually<00:00:40.360> finalized 00:00:41.350 --> 00:00:41.360 align:start position:0% chain that will be eventually finalized 00:00:41.360 --> 00:00:44.510 align:start position:0% chain that will be eventually finalized uh<00:00:41.520> by<00:00:41.680> the<00:00:42.079> protocol<00:00:43.079> and<00:00:43.440> uh<00:00:43.600> a<00:00:43.760> noncompliant 00:00:44.510 --> 00:00:44.520 align:start position:0% uh by the protocol and uh a noncompliant 00:00:44.520 --> 00:00:46.830 align:start position:0% uh by the protocol and uh a noncompliant with<00:00:44.680> the<00:00:44.760> FTR<00:00:45.280> speack<00:00:45.559> implementation<00:00:46.559> can 00:00:46.830 --> 00:00:46.840 align:start position:0% with the FTR speack implementation can 00:00:46.840 --> 00:00:49.709 align:start position:0% with the FTR speack implementation can cause<00:00:47.559> uh<00:00:47.800> different<00:00:48.199> security<00:00:48.680> issues<00:00:49.480> such 00:00:49.709 --> 00:00:49.719 align:start position:0% cause uh different security issues such 00:00:49.719 --> 00:00:52.189 align:start position:0% cause uh different security issues such as<00:00:50.480> confirming<00:00:51.120> your<00:00:51.360> transaction<00:00:51.879> with<00:00:52.079> the 00:00:52.189 --> 00:00:52.199 align:start position:0% as confirming your transaction with the 00:00:52.199 --> 00:00:54.910 align:start position:0% as confirming your transaction with the chain<00:00:52.640> that<00:00:52.800> your<00:00:52.960> local<00:00:53.239> node<00:00:53.520> pretends<00:00:54.079> to 00:00:54.910 --> 00:00:54.920 align:start position:0% chain that your local node pretends to 00:00:54.920 --> 00:00:57.910 align:start position:0% chain that your local node pretends to to<00:00:55.160> say<00:00:55.480> that<00:00:56.039> this<00:00:56.160> chain<00:00:56.399> is<00:00:56.559> canonical<00:00:57.280> but 00:00:57.910 --> 00:00:57.920 align:start position:0% to say that this chain is canonical but 00:00:57.920 --> 00:00:59.670 align:start position:0% to say that this chain is canonical but the<00:00:58.039> chain<00:00:58.280> is<00:00:58.480> effectively<00:00:59.000> not<00:00:59.160> canonical 00:00:59.670 --> 00:00:59.680 align:start position:0% the chain is effectively not canonical 00:00:59.680 --> 00:01:01.110 align:start position:0% the chain is effectively not canonical and<00:01:00.039> it's<00:01:00.160> not<00:01:00.359> canonical<00:01:00.800> to<00:01:00.920> the 00:01:01.110 --> 00:01:01.120 align:start position:0% and it's not canonical to the 00:01:01.120 --> 00:01:03.430 align:start position:0% and it's not canonical to the observation<00:01:01.680> of<00:01:02.280> uh<00:01:02.399> the<00:01:02.559> majority<00:01:03.039> notes<00:01:03.320> in 00:01:03.430 --> 00:01:03.440 align:start position:0% observation of uh the majority notes in 00:01:03.440 --> 00:01:06.910 align:start position:0% observation of uh the majority notes in the<00:01:03.760> network<00:01:04.760> um<00:01:05.119> in<00:01:05.280> some<00:01:05.560> situations<00:01:06.560> uh 00:01:06.910 --> 00:01:06.920 align:start position:0% the network um in some situations uh 00:01:06.920 --> 00:01:10.190 align:start position:0% the network um in some situations uh this<00:01:07.880> uh<00:01:08.400> non-compliant<00:01:09.159> implementation<00:01:09.880> can 00:01:10.190 --> 00:01:10.200 align:start position:0% this uh non-compliant implementation can 00:01:10.200 --> 00:01:13.789 align:start position:0% this uh non-compliant implementation can cause<00:01:10.759> uh<00:01:10.920> Network<00:01:12.040> splits<00:01:13.040> uh<00:01:13.240> which<00:01:13.560> can 00:01:13.789 --> 00:01:13.799 align:start position:0% cause uh Network splits uh which can 00:01:13.799 --> 00:01:16.990 align:start position:0% cause uh Network splits uh which can affect<00:01:14.280> validator<00:01:14.880> voting<00:01:15.880> uh<00:01:16.280> participate 00:01:16.990 --> 00:01:17.000 align:start position:0% affect validator voting uh participate 00:01:17.000 --> 00:01:20.789 align:start position:0% affect validator voting uh participate valer<00:01:17.439> voting<00:01:17.799> rate<00:01:18.320> uh<00:01:18.479> in<00:01:18.600> a<00:01:19.280> bad<00:01:19.600> way<00:01:20.040> and<00:01:20.560> uh 00:01:20.789 --> 00:01:20.799 align:start position:0% valer voting rate uh in a bad way and uh 00:01:20.799 --> 00:01:22.429 align:start position:0% valer voting rate uh in a bad way and uh in<00:01:20.920> the<00:01:21.040> worst<00:01:21.360> case<00:01:21.520> scenario<00:01:21.960> it<00:01:22.119> could 00:01:22.429 --> 00:01:22.439 align:start position:0% in the worst case scenario it could 00:01:22.439 --> 00:01:23.390 align:start position:0% in the worst case scenario it could delay 00:01:23.390 --> 00:01:23.400 align:start position:0% delay 00:01:23.400 --> 00:01:28.190 align:start position:0% delay finality<00:01:24.400> um<00:01:24.560> in<00:01:24.759> Ideal<00:01:25.159> World<00:01:26.040> uh 00:01:28.190 --> 00:01:28.200 align:start position:0% finality um in Ideal World uh 00:01:28.200 --> 00:01:30.870 align:start position:0% finality um in Ideal World uh every<00:01:29.200> every<00:01:29.520> implement<00:01:29.920> mentation<00:01:30.720> is 00:01:30.870 --> 00:01:30.880 align:start position:0% every every implement mentation is 00:01:30.880 --> 00:01:32.950 align:start position:0% every every implement mentation is formally<00:01:31.360> verified<00:01:31.960> to<00:01:32.119> be<00:01:32.360> compliant<00:01:32.840> with 00:01:32.950 --> 00:01:32.960 align:start position:0% formally verified to be compliant with 00:01:32.960 --> 00:01:35.149 align:start position:0% formally verified to be compliant with the<00:01:33.040> for<00:01:33.320> CH<00:01:33.560> spec<00:01:34.040> but<00:01:34.200> we<00:01:34.360> cannot<00:01:34.759> expect 00:01:35.149 --> 00:01:35.159 align:start position:0% the for CH spec but we cannot expect 00:01:35.159 --> 00:01:36.789 align:start position:0% the for CH spec but we cannot expect this<00:01:35.320> to<00:01:35.520> happen<00:01:35.960> because<00:01:36.200> it<00:01:36.320> is<00:01:36.520> quite 00:01:36.789 --> 00:01:36.799 align:start position:0% this to happen because it is quite 00:01:36.799 --> 00:01:39.670 align:start position:0% this to happen because it is quite challenging<00:01:37.399> and<00:01:37.640> costly<00:01:38.640> and<00:01:38.880> our<00:01:39.240> approach 00:01:39.670 --> 00:01:39.680 align:start position:0% challenging and costly and our approach 00:01:39.680 --> 00:01:42.630 align:start position:0% challenging and costly and our approach to<00:01:40.399> the<00:01:40.600> compliance<00:01:41.280> is<00:01:41.439> to<00:01:41.640> extensively<00:01:42.280> test 00:01:42.630 --> 00:01:42.640 align:start position:0% to the compliance is to extensively test 00:01:42.640 --> 00:01:44.550 align:start position:0% to the compliance is to extensively test every<00:01:42.960> implementation<00:01:43.840> against<00:01:44.159> the<00:01:44.280> FK 00:01:44.550 --> 00:01:44.560 align:start position:0% every implementation against the FK 00:01:44.560 --> 00:01:45.429 align:start position:0% every implementation against the FK Choice 00:01:45.429 --> 00:01:45.439 align:start position:0% Choice 00:01:45.439 --> 00:01:48.670 align:start position:0% Choice spec<00:01:46.439> uh<00:01:46.560> so<00:01:46.759> now<00:01:46.960> a<00:01:47.119> bit<00:01:47.759> uh<00:01:48.000> about<00:01:48.280> the<00:01:48.399> folk 00:01:48.670 --> 00:01:48.680 align:start position:0% spec uh so now a bit uh about the folk 00:01:48.680 --> 00:01:51.030 align:start position:0% spec uh so now a bit uh about the folk Choice<00:01:48.960> rule<00:01:49.280> itself<00:01:49.960> so<00:01:50.200> imagine<00:01:50.640> there<00:01:50.759> is<00:01:50.880> a 00:01:51.030 --> 00:01:51.040 align:start position:0% Choice rule itself so imagine there is a 00:01:51.040 --> 00:01:54.230 align:start position:0% Choice rule itself so imagine there is a node<00:01:51.399> state<00:01:52.040> that<00:01:52.200> is<00:01:52.439> computed<00:01:53.439> from<00:01:53.719> the 00:01:54.230 --> 00:01:54.240 align:start position:0% node state that is computed from the 00:01:54.240 --> 00:01:56.069 align:start position:0% node state that is computed from the messages<00:01:55.240> that<00:01:55.360> are<00:01:55.520> coming<00:01:55.759> from<00:01:55.960> the 00:01:56.069 --> 00:01:56.079 align:start position:0% messages that are coming from the 00:01:56.079 --> 00:02:00.109 align:start position:0% messages that are coming from the network<00:01:56.560> such<00:01:56.880> as<00:01:57.119> blogs<00:01:57.719> votes<00:01:58.320> and<00:01:58.680> others 00:02:00.109 --> 00:02:00.119 align:start position:0% network such as blogs votes and others 00:02:00.119 --> 00:02:02.870 align:start position:0% network such as blogs votes and others and<00:02:00.320> the<00:02:00.479> folk<00:02:00.799> Choice<00:02:01.039> rule<00:02:01.840> algorithm<00:02:02.560> is 00:02:02.870 --> 00:02:02.880 align:start position:0% and the folk Choice rule algorithm is 00:02:02.880 --> 00:02:05.950 align:start position:0% and the folk Choice rule algorithm is executed<00:02:03.600> over<00:02:04.520> this<00:02:04.960> state<00:02:05.520> in<00:02:05.719> in<00:02:05.840> the 00:02:05.950 --> 00:02:05.960 align:start position:0% executed over this state in in the 00:02:05.960 --> 00:02:08.550 align:start position:0% executed over this state in in the following<00:02:06.360> three<00:02:06.640> steps<00:02:07.399> so<00:02:08.039> at<00:02:08.160> the<00:02:08.319> first 00:02:08.550 --> 00:02:08.560 align:start position:0% following three steps so at the first 00:02:08.560 --> 00:02:11.270 align:start position:0% following three steps so at the first step<00:02:08.879> there<00:02:09.000> is<00:02:09.080> a<00:02:09.280> filtering<00:02:09.800> function<00:02:10.399> that 00:02:11.270 --> 00:02:11.280 align:start position:0% step there is a filtering function that 00:02:11.280 --> 00:02:14.390 align:start position:0% step there is a filtering function that uh<00:02:11.440> selects<00:02:12.239> blocks<00:02:12.640> that<00:02:12.800> are<00:02:13.160> candidate<00:02:13.720> for 00:02:14.390 --> 00:02:14.400 align:start position:0% uh selects blocks that are candidate for 00:02:14.400 --> 00:02:17.030 align:start position:0% uh selects blocks that are candidate for head<00:02:14.920> we<00:02:15.040> call<00:02:15.239> them<00:02:15.440> viable<00:02:15.879> for<00:02:16.080> head<00:02:16.280> blocks 00:02:17.030 --> 00:02:17.040 align:start position:0% head we call them viable for head blocks 00:02:17.040 --> 00:02:18.350 align:start position:0% head we call them viable for head blocks at<00:02:17.200> the<00:02:17.400> Second 00:02:18.350 --> 00:02:18.360 align:start position:0% at the Second 00:02:18.360 --> 00:02:22.070 align:start position:0% at the Second Step<00:02:19.360> uh<00:02:19.599> validator<00:02:20.519> votes<00:02:21.000> are<00:02:21.239> used<00:02:21.560> to 00:02:22.070 --> 00:02:22.080 align:start position:0% Step uh validator votes are used to 00:02:22.080 --> 00:02:25.509 align:start position:0% Step uh validator votes are used to compute<00:02:23.080> uh<00:02:23.480> weights<00:02:23.879> of<00:02:24.080> sub<00:02:24.360> trees<00:02:25.200> uh<00:02:25.319> which 00:02:25.509 --> 00:02:25.519 align:start position:0% compute uh weights of sub trees uh which 00:02:25.519 --> 00:02:29.150 align:start position:0% compute uh weights of sub trees uh which contains<00:02:26.040> those<00:02:26.560> uh<00:02:26.760> wable<00:02:27.560> blocks<00:02:28.560> and<00:02:28.879> uh<00:02:29.000> at 00:02:29.150 --> 00:02:29.160 align:start position:0% contains those uh wable blocks and uh at 00:02:29.160 --> 00:02:30.830 align:start position:0% contains those uh wable blocks and uh at the<00:02:29.280> last<00:02:29.480> step<00:02:30.080> uh<00:02:30.200> the<00:02:30.319> algorithm 00:02:30.830 --> 00:02:30.840 align:start position:0% the last step uh the algorithm 00:02:30.840 --> 00:02:34.390 align:start position:0% the last step uh the algorithm recursively<00:02:31.599> goes<00:02:32.360> uh<00:02:32.720> down<00:02:33.160> to<00:02:33.480> the<00:02:33.760> heaviest 00:02:34.390 --> 00:02:34.400 align:start position:0% recursively goes uh down to the heaviest 00:02:34.400 --> 00:02:37.550 align:start position:0% recursively goes uh down to the heaviest sub<00:02:34.680> tree<00:02:35.640> until<00:02:36.120> the<00:02:36.440> leaf<00:02:36.760> block<00:02:37.000> is<00:02:37.120> found 00:02:37.550 --> 00:02:37.560 align:start position:0% sub tree until the leaf block is found 00:02:37.560 --> 00:02:39.750 align:start position:0% sub tree until the leaf block is found and<00:02:37.680> that<00:02:37.879> Lea<00:02:38.120> block<00:02:38.599> uh<00:02:38.720> will<00:02:38.879> be<00:02:39.040> the<00:02:39.200> head 00:02:39.750 --> 00:02:39.760 align:start position:0% and that Lea block uh will be the head 00:02:39.760 --> 00:02:43.790 align:start position:0% and that Lea block uh will be the head so<00:02:40.040> the<00:02:40.239> algorithm<00:02:40.840> doesn't<00:02:41.239> look<00:02:42.239> uh<00:02:43.239> um 00:02:43.790 --> 00:02:43.800 align:start position:0% so the algorithm doesn't look uh um 00:02:43.800 --> 00:02:46.030 align:start position:0% so the algorithm doesn't look uh um quite<00:02:44.200> doesn't<00:02:44.519> look<00:02:44.720> complex<00:02:45.280> it's<00:02:45.599> Rel 00:02:46.030 --> 00:02:46.040 align:start position:0% quite doesn't look complex it's Rel 00:02:46.040 --> 00:02:47.149 align:start position:0% quite doesn't look complex it's Rel relatively 00:02:47.149 --> 00:02:47.159 align:start position:0% relatively 00:02:47.159 --> 00:02:50.910 align:start position:0% relatively simple<00:02:48.159> but<00:02:48.560> uh<00:02:48.680> the<00:02:48.879> complexities<00:02:49.840> here<00:02:50.599> uh 00:02:50.910 --> 00:02:50.920 align:start position:0% simple but uh the complexities here uh 00:02:50.920 --> 00:02:52.910 align:start position:0% simple but uh the complexities here uh coming<00:02:51.319> from<00:02:51.599> the<00:02:51.840> different<00:02:52.200> place<00:02:52.680> uh<00:02:52.800> there 00:02:52.910 --> 00:02:52.920 align:start position:0% coming from the different place uh there 00:02:52.920 --> 00:02:55.229 align:start position:0% coming from the different place uh there are<00:02:53.080> many<00:02:53.360> many<00:02:53.800> inter<00:02:54.200> notd<00:02:54.599> interacting<00:02:55.120> in 00:02:55.229 --> 00:02:55.239 align:start position:0% are many many inter notd interacting in 00:02:55.239 --> 00:02:57.190 align:start position:0% are many many inter notd interacting in the<00:02:55.400> network<00:02:56.120> and<00:02:56.280> they<00:02:56.440> produce<00:02:56.840> many 00:02:57.190 --> 00:02:57.200 align:start position:0% the network and they produce many 00:02:57.200 --> 00:03:00.309 align:start position:0% the network and they produce many messages<00:02:58.080> blocks<00:02:58.519> and<00:02:58.720> votes<00:02:59.720> uh<00:03:00.120> that 00:03:00.309 --> 00:03:00.319 align:start position:0% messages blocks and votes uh that 00:03:00.319 --> 00:03:02.710 align:start position:0% messages blocks and votes uh that results<00:03:00.720> in<00:03:00.879> a<00:03:01.040> huge<00:03:01.360> variety<00:03:01.760> of<00:03:01.920> States<00:03:02.440> over 00:03:02.710 --> 00:03:02.720 align:start position:0% results in a huge variety of States over 00:03:02.720 --> 00:03:05.390 align:start position:0% results in a huge variety of States over which<00:03:02.959> the<00:03:03.200> folk<00:03:03.560> Choice<00:03:03.959> algorithm<00:03:04.720> is 00:03:05.390 --> 00:03:05.400 align:start position:0% which the folk Choice algorithm is 00:03:05.400 --> 00:03:07.589 align:start position:0% which the folk Choice algorithm is evaluated<00:03:06.400> and<00:03:06.959> every<00:03:07.239> client 00:03:07.589 --> 00:03:07.599 align:start position:0% evaluated and every client 00:03:07.599 --> 00:03:10.190 align:start position:0% evaluated and every client implementations<00:03:08.519> use<00:03:09.120> uses<00:03:09.519> their<00:03:09.799> own 00:03:10.190 --> 00:03:10.200 align:start position:0% implementations use uses their own 00:03:10.200 --> 00:03:12.190 align:start position:0% implementations use uses their own optimization<00:03:11.120> in<00:03:11.239> order<00:03:11.480> to<00:03:11.680> compute<00:03:12.040> the 00:03:12.190 --> 00:03:12.200 align:start position:0% optimization in order to compute the 00:03:12.200 --> 00:03:15.430 align:start position:0% optimization in order to compute the state<00:03:12.560> fast<00:03:13.519> and<00:03:13.959> uh<00:03:14.040> in<00:03:14.159> order<00:03:14.400> to<00:03:14.879> uh<00:03:15.000> run<00:03:15.280> the 00:03:15.430 --> 00:03:15.440 align:start position:0% state fast and uh in order to uh run the 00:03:15.440 --> 00:03:18.990 align:start position:0% state fast and uh in order to uh run the FTR<00:03:16.000> rule<00:03:16.640> so<00:03:17.080> those<00:03:17.680> makes<00:03:18.319> those<00:03:18.519> two<00:03:18.720> things 00:03:18.990 --> 00:03:19.000 align:start position:0% FTR rule so those makes those two things 00:03:19.000 --> 00:03:21.750 align:start position:0% FTR rule so those makes those two things makes<00:03:19.560> the<00:03:20.159> the<00:03:20.360> F<00:03:20.879> compliance<00:03:21.239> incredibly 00:03:21.750 --> 00:03:21.760 align:start position:0% makes the the F compliance incredibly 00:03:21.760 --> 00:03:25.110 align:start position:0% makes the the F compliance incredibly complicated<00:03:22.760> uh<00:03:23.280> and<00:03:23.599> now<00:03:23.840> over<00:03:24.080> to<00:03:24.319> Alex<00:03:24.799> on 00:03:25.110 --> 00:03:25.120 align:start position:0% complicated uh and now over to Alex on 00:03:25.120 --> 00:03:26.630 align:start position:0% complicated uh and now over to Alex on how<00:03:25.239> do<00:03:25.400> we<00:03:25.560> fight<00:03:25.879> those 00:03:26.630 --> 00:03:26.640 align:start position:0% how do we fight those 00:03:26.640 --> 00:03:29.350 align:start position:0% how do we fight those complexities<00:03:27.640> uh<00:03:27.799> so<00:03:28.040> our<00:03:28.319> goal<00:03:28.640> is<00:03:28.760> to<00:03:29.000> reveal 00:03:29.350 --> 00:03:29.360 align:start position:0% complexities uh so our goal is to reveal 00:03:29.360 --> 00:03:31.309 align:start position:0% complexities uh so our goal is to reveal difference<00:03:30.000> between<00:03:30.560> Fork<00:03:30.959> Choice 00:03:31.309 --> 00:03:31.319 align:start position:0% difference between Fork Choice 00:03:31.319 --> 00:03:33.630 align:start position:0% difference between Fork Choice specification<00:03:32.080> and<00:03:32.319> implementations<00:03:33.319> and<00:03:33.519> we 00:03:33.630 --> 00:03:33.640 align:start position:0% specification and implementations and we 00:03:33.640 --> 00:03:36.990 align:start position:0% specification and implementations and we need<00:03:33.840> a<00:03:34.040> lot<00:03:34.239> of<00:03:34.920> interesting<00:03:35.920> test<00:03:36.239> scenarios 00:03:36.990 --> 00:03:37.000 align:start position:0% need a lot of interesting test scenarios 00:03:37.000 --> 00:03:39.470 align:start position:0% need a lot of interesting test scenarios but<00:03:37.360> generating<00:03:38.360> lots<00:03:38.720> of<00:03:39.200> really 00:03:39.470 --> 00:03:39.480 align:start position:0% but generating lots of really 00:03:39.480 --> 00:03:41.270 align:start position:0% but generating lots of really interesting<00:03:39.879> scenarios<00:03:40.400> is<00:03:40.560> a<00:03:40.680> challenging 00:03:41.270 --> 00:03:41.280 align:start position:0% interesting scenarios is a challenging 00:03:41.280 --> 00:03:43.949 align:start position:0% interesting scenarios is a challenging problem<00:03:41.959> and<00:03:42.080> so<00:03:42.319> to<00:03:42.879> overcome<00:03:43.400> that<00:03:43.640> we 00:03:43.949 --> 00:03:43.959 align:start position:0% problem and so to overcome that we 00:03:43.959 --> 00:03:46.190 align:start position:0% problem and so to overcome that we developed<00:03:44.400> a<00:03:44.599> strategy<00:03:45.439> which<00:03:45.760> based<00:03:45.959> on<00:03:46.080> the 00:03:46.190 --> 00:03:46.200 align:start position:0% developed a strategy which based on the 00:03:46.200 --> 00:03:49.149 align:start position:0% developed a strategy which based on the following<00:03:46.720> principle<00:03:47.519> differential<00:03:48.239> testing 00:03:49.149 --> 00:03:49.159 align:start position:0% following principle differential testing 00:03:49.159 --> 00:03:51.750 align:start position:0% following principle differential testing property<00:03:49.640> based<00:03:50.000> testing<00:03:51.000> modelbased 00:03:51.750 --> 00:03:51.760 align:start position:0% property based testing modelbased 00:03:51.760 --> 00:03:55.830 align:start position:0% property based testing modelbased testing<00:03:52.239> and<00:03:52.400> final<00:03:52.760> ingredient<00:03:53.319> fing<00:03:53.840> and 00:03:55.830 --> 00:03:55.840 align:start position:0% testing and final ingredient fing and 00:03:55.840 --> 00:03:57.630 align:start position:0% testing and final ingredient fing and randomization<00:03:56.840> and<00:03:57.079> okay<00:03:57.319> about 00:03:57.630 --> 00:03:57.640 align:start position:0% randomization and okay about 00:03:57.640 --> 00:03:59.470 align:start position:0% randomization and okay about differential<00:03:58.200> property<00:03:58.599> testing<00:03:58.920> for<00:03:59.200> Choice 00:03:59.470 --> 00:03:59.480 align:start position:0% differential property testing for Choice 00:03:59.480 --> 00:04:00.589 align:start position:0% differential property testing for Choice spec<00:03:59.879> is 00:04:00.589 --> 00:04:00.599 align:start position:0% spec is 00:04:00.599 --> 00:04:02.990 align:start position:0% spec is executable<00:04:01.599> so<00:04:02.040> we<00:04:02.200> can<00:04:02.480> compare 00:04:02.990 --> 00:04:03.000 align:start position:0% executable so we can compare 00:04:03.000 --> 00:04:05.190 align:start position:0% executable so we can compare implementation<00:04:03.840> Behavior<00:04:04.840> against 00:04:05.190 --> 00:04:05.200 align:start position:0% implementation Behavior against 00:04:05.200 --> 00:04:07.309 align:start position:0% implementation Behavior against specification<00:04:05.920> directly<00:04:06.599> and<00:04:06.799> this<00:04:06.879> is<00:04:07.079> why 00:04:07.309 --> 00:04:07.319 align:start position:0% specification directly and this is why 00:04:07.319 --> 00:04:10.470 align:start position:0% specification directly and this is why differential<00:04:07.959> testing<00:04:08.920> and<00:04:09.280> we<00:04:09.519> want<00:04:10.200> to 00:04:10.470 --> 00:04:10.480 align:start position:0% differential testing and we want to 00:04:10.480 --> 00:04:13.949 align:start position:0% differential testing and we want to check<00:04:11.239> that<00:04:11.799> uh<00:04:12.159> every<00:04:12.959> implementation 00:04:13.949 --> 00:04:13.959 align:start position:0% check that uh every implementation 00:04:13.959 --> 00:04:16.509 align:start position:0% check that uh every implementation calculates<00:04:14.560> the<00:04:14.760> head<00:04:15.000> of<00:04:15.120> canonical<00:04:15.760> chain 00:04:16.509 --> 00:04:16.519 align:start position:0% calculates the head of canonical chain 00:04:16.519 --> 00:04:20.150 align:start position:0% calculates the head of canonical chain correctly<00:04:17.519> but<00:04:17.759> it<00:04:17.959> does<00:04:18.199> not<00:04:18.479> mean<00:04:19.479> that<00:04:19.919> so 00:04:20.150 --> 00:04:20.160 align:start position:0% correctly but it does not mean that so 00:04:20.160 --> 00:04:22.430 align:start position:0% correctly but it does not mean that so if<00:04:20.320> the<00:04:20.519> check<00:04:21.079> the<00:04:21.280> head<00:04:21.600> is<00:04:21.799> correct<00:04:22.160> it<00:04:22.280> does 00:04:22.430 --> 00:04:22.440 align:start position:0% if the check the head is correct it does 00:04:22.440 --> 00:04:24.430 align:start position:0% if the check the head is correct it does not<00:04:22.560> mean<00:04:22.800> that<00:04:23.000> protocol<00:04:23.479> state<00:04:23.880> is<00:04:24.080> correct 00:04:24.430 --> 00:04:24.440 align:start position:0% not mean that protocol state is correct 00:04:24.440 --> 00:04:27.230 align:start position:0% not mean that protocol state is correct too<00:04:24.960> and<00:04:25.080> so<00:04:25.280> we<00:04:25.400> can<00:04:25.560> check<00:04:25.880> additional 00:04:27.230 --> 00:04:27.240 align:start position:0% too and so we can check additional 00:04:27.240 --> 00:04:29.749 align:start position:0% too and so we can check additional properties<00:04:28.240> uh<00:04:28.360> to<00:04:28.560> reveal<00:04:28.919> more<00:04:29.120> buxs<00:04:29.520> with 00:04:29.749 --> 00:04:29.759 align:start position:0% properties uh to reveal more buxs with 00:04:29.759 --> 00:04:32.189 align:start position:0% properties uh to reveal more buxs with using<00:04:30.199> essentially<00:04:30.720> the<00:04:30.880> same<00:04:31.160> test 00:04:32.189 --> 00:04:32.199 align:start position:0% using essentially the same test 00:04:32.199 --> 00:04:35.390 align:start position:0% using essentially the same test seed<00:04:33.199> and<00:04:33.600> uh<00:04:33.759> here<00:04:33.880> is<00:04:34.080> the<00:04:34.280> example<00:04:34.800> of<00:04:35.160> how 00:04:35.390 --> 00:04:35.400 align:start position:0% seed and uh here is the example of how 00:04:35.400 --> 00:04:37.390 align:start position:0% seed and uh here is the example of how the<00:04:35.639> property<00:04:36.039> checks<00:04:36.440> can<00:04:36.600> be<00:04:36.840> really 00:04:37.390 --> 00:04:37.400 align:start position:0% the property checks can be really 00:04:37.400 --> 00:04:39.870 align:start position:0% the property checks can be really helpful<00:04:38.400> uh<00:04:38.680> on<00:04:38.840> the<00:04:39.000> left<00:04:39.240> side<00:04:39.440> there<00:04:39.560> is<00:04:39.680> a 00:04:39.870 --> 00:04:39.880 align:start position:0% helpful uh on the left side there is a 00:04:39.880 --> 00:04:42.189 align:start position:0% helpful uh on the left side there is a buy<00:04:40.240> implementation<00:04:41.080> that<00:04:41.320> for<00:04:41.639> some<00:04:41.880> reason 00:04:42.189 --> 00:04:42.199 align:start position:0% buy implementation that for some reason 00:04:42.199 --> 00:04:46.270 align:start position:0% buy implementation that for some reason just<00:04:42.400> missed<00:04:42.759> one<00:04:43.080> vote<00:04:44.080> uh<00:04:44.320> and<00:04:44.840> uh<00:04:45.800> the<00:04:46.000> head 00:04:46.270 --> 00:04:46.280 align:start position:0% just missed one vote uh and uh the head 00:04:46.280 --> 00:04:47.870 align:start position:0% just missed one vote uh and uh the head in<00:04:46.600> in<00:04:46.759> both<00:04:47.039> cases<00:04:47.320> in<00:04:47.520> case<00:04:47.720> of 00:04:47.870 --> 00:04:47.880 align:start position:0% in in both cases in case of 00:04:47.880 --> 00:04:49.909 align:start position:0% in in both cases in case of implementation<00:04:48.440> and<00:04:48.639> specification<00:04:49.600> is<00:04:49.759> the 00:04:49.909 --> 00:04:49.919 align:start position:0% implementation and specification is the 00:04:49.919 --> 00:04:53.110 align:start position:0% implementation and specification is the Block<00:04:50.160> C<00:04:50.960> so<00:04:51.199> this<00:04:51.479> V<00:04:51.880> this<00:04:52.120> Miss<00:04:52.479> vote<00:04:52.759> Miss 00:04:53.110 --> 00:04:53.120 align:start position:0% Block C so this V this Miss vote Miss 00:04:53.120 --> 00:04:57.469 align:start position:0% Block C so this V this Miss vote Miss did<00:04:53.280> not<00:04:53.560> affect<00:04:54.360> uh<00:04:54.520> the<00:04:54.759> had<00:04:55.880> computation<00:04:56.880> uh 00:04:57.469 --> 00:04:57.479 align:start position:0% did not affect uh the had computation uh 00:04:57.479 --> 00:05:00.629 align:start position:0% did not affect uh the had computation uh and<00:04:57.880> if<00:04:58.120> the<00:04:58.280> test<00:04:58.600> case<00:04:58.919> would<00:04:59.199> just<00:05:00.080> compare 00:05:00.629 --> 00:05:00.639 align:start position:0% and if the test case would just compare 00:05:00.639 --> 00:05:04.189 align:start position:0% and if the test case would just compare the<00:05:00.880> head<00:05:01.840> uh<00:05:02.240> and<00:05:02.680> uh<00:05:02.919> the<00:05:03.080> the<00:05:03.240> client<00:05:04.000> this 00:05:04.189 --> 00:05:04.199 align:start position:0% the head uh and uh the the client this 00:05:04.199 --> 00:05:06.430 align:start position:0% the head uh and uh the the client this bu<00:05:04.520> implementation<00:05:05.479> uh<00:05:05.600> running<00:05:06.000> this<00:05:06.160> test 00:05:06.430 --> 00:05:06.440 align:start position:0% bu implementation uh running this test 00:05:06.440 --> 00:05:08.870 align:start position:0% bu implementation uh running this test case<00:05:07.000> uh<00:05:07.280> would<00:05:07.479> pass<00:05:07.800> it 00:05:08.870 --> 00:05:08.880 align:start position:0% case uh would pass it 00:05:08.880 --> 00:05:11.710 align:start position:0% case uh would pass it successfully<00:05:09.880> and<00:05:10.280> uh<00:05:10.680> directly<00:05:11.160> comparing 00:05:11.710 --> 00:05:11.720 align:start position:0% successfully and uh directly comparing 00:05:11.720 --> 00:05:13.950 align:start position:0% successfully and uh directly comparing the<00:05:11.840> weight<00:05:12.080> of<00:05:12.199> Block<00:05:12.440> C<00:05:12.680> in<00:05:12.880> this<00:05:13.080> case<00:05:13.800> uh 00:05:13.950 --> 00:05:13.960 align:start position:0% the weight of Block C in this case uh 00:05:13.960 --> 00:05:16.990 align:start position:0% the weight of Block C in this case uh would<00:05:14.240> help<00:05:14.600> us<00:05:14.800> to<00:05:15.120> reveal<00:05:15.680> bug<00:05:16.039> much<00:05:16.280> easier 00:05:16.990 --> 00:05:17.000 align:start position:0% would help us to reveal bug much easier 00:05:17.000 --> 00:05:18.390 align:start position:0% would help us to reveal bug much easier because<00:05:17.320> otherwise<00:05:17.800> we<00:05:17.919> would<00:05:18.080> need<00:05:18.240> to 00:05:18.390 --> 00:05:18.400 align:start position:0% because otherwise we would need to 00:05:18.400 --> 00:05:21.670 align:start position:0% because otherwise we would need to create<00:05:18.639> a<00:05:18.800> test<00:05:19.360> that<00:05:20.240> uh<00:05:20.360> in<00:05:20.560> which<00:05:21.240> run<00:05:21.520> in 00:05:21.670 --> 00:05:21.680 align:start position:0% create a test that uh in which run in 00:05:21.680 --> 00:05:24.150 align:start position:0% create a test that uh in which run in which<00:05:22.080> this<00:05:22.280> bug<00:05:22.800> implementation<00:05:23.800> would 00:05:24.150 --> 00:05:24.160 align:start position:0% which this bug implementation would 00:05:24.160 --> 00:05:26.469 align:start position:0% which this bug implementation would would<00:05:24.319> lead<00:05:24.600> us<00:05:24.800> to<00:05:25.400> uh<00:05:25.560> the<00:05:25.720> different<00:05:26.360> uh 00:05:26.469 --> 00:05:26.479 align:start position:0% would lead us to uh the different uh 00:05:26.479 --> 00:05:27.990 align:start position:0% would lead us to uh the different uh block<00:05:26.720> to<00:05:26.840> be<00:05:27.000> the<00:05:27.160> head<00:05:27.400> like<00:05:27.560> for<00:05:27.680> instance 00:05:27.990 --> 00:05:28.000 align:start position:0% block to be the head like for instance 00:05:28.000 --> 00:05:33.710 align:start position:0% block to be the head like for instance Block<00:05:28.240> B<00:05:28.919> so<00:05:29.400> is<00:05:30.000> just<00:05:31.240> uh<00:05:32.240> like<00:05:32.440> less<00:05:32.759> test<00:05:33.120> can 00:05:33.710 --> 00:05:33.720 align:start position:0% Block B so is just uh like less test can 00:05:33.720 --> 00:05:36.790 align:start position:0% Block B so is just uh like less test can can<00:05:33.919> reveal<00:05:34.240> more<00:05:34.479> boxs<00:05:34.880> that's<00:05:35.360> uh<00:05:35.600> the<00:05:35.720> short 00:05:36.790 --> 00:05:36.800 align:start position:0% can reveal more boxs that's uh the short 00:05:36.800 --> 00:05:40.309 align:start position:0% can reveal more boxs that's uh the short uh<00:05:37.800> description<00:05:38.800> so<00:05:39.319> uh<00:05:39.800> yeah<00:05:40.039> what<00:05:40.160> we 00:05:40.309 --> 00:05:40.319 align:start position:0% uh description so uh yeah what we 00:05:40.319 --> 00:05:42.070 align:start position:0% uh description so uh yeah what we haven't<00:05:40.680> yet<00:05:40.840> mentioned<00:05:41.360> is<00:05:41.600> that<00:05:41.800> our 00:05:42.070 --> 00:05:42.080 align:start position:0% haven't yet mentioned is that our 00:05:42.080 --> 00:05:45.270 align:start position:0% haven't yet mentioned is that our compliance<00:05:42.880> uh<00:05:43.000> Tool<00:05:43.759> uh<00:05:44.160> leverages<00:05:44.800> on<00:05:45.080> the 00:05:45.270 --> 00:05:45.280 align:start position:0% compliance uh Tool uh leverages on the 00:05:45.280 --> 00:05:47.270 align:start position:0% compliance uh Tool uh leverages on the already<00:05:45.759> existing<00:05:46.120> folk<00:05:46.440> Choice<00:05:46.759> testing 00:05:47.270 --> 00:05:47.280 align:start position:0% already existing folk Choice testing 00:05:47.280 --> 00:05:50.029 align:start position:0% already existing folk Choice testing framework<00:05:48.280> uh<00:05:48.400> there<00:05:48.520> is<00:05:48.720> the<00:05:48.919> consensus<00:05:49.919> in 00:05:50.029 --> 00:05:50.039 align:start position:0% framework uh there is the consensus in 00:05:50.039 --> 00:05:52.070 align:start position:0% framework uh there is the consensus in the<00:05:50.199> consensus<00:05:50.720> specs<00:05:51.080> there<00:05:51.240> is<00:05:51.440> the<00:05:51.759> fork 00:05:52.070 --> 00:05:52.080 align:start position:0% the consensus specs there is the fork 00:05:52.080 --> 00:05:54.189 align:start position:0% the consensus specs there is the fork Choice<00:05:52.360> testing<00:05:53.280> uh<00:05:53.400> format<00:05:53.919> there<00:05:54.039> are 00:05:54.189 --> 00:05:54.199 align:start position:0% Choice testing uh format there are 00:05:54.199 --> 00:05:56.990 align:start position:0% Choice testing uh format there are manually<00:05:54.919> written<00:05:55.639> uh<00:05:55.759> Fork<00:05:56.080> Choice<00:05:56.440> tests 00:05:56.990 --> 00:05:57.000 align:start position:0% manually written uh Fork Choice tests 00:05:57.000 --> 00:05:59.029 align:start position:0% manually written uh Fork Choice tests and<00:05:57.280> clients<00:05:57.720> already<00:05:58.039> run<00:05:58.360> them<00:05:58.680> those<00:05:58.840> are 00:05:59.029 --> 00:05:59.039 align:start position:0% and clients already run them those are 00:05:59.039 --> 00:06:02.189 align:start position:0% and clients already run them those are integrated<00:06:00.080> uh<00:06:00.280> and<00:06:00.759> yeah<00:06:01.319> the<00:06:01.600> the<00:06:01.720> clients 00:06:02.189 --> 00:06:02.199 align:start position:0% integrated uh and yeah the the clients 00:06:02.199 --> 00:06:05.990 align:start position:0% integrated uh and yeah the the clients already<00:06:03.160> uh<00:06:03.400> check<00:06:04.000> some<00:06:04.240> of<00:06:04.880> the<00:06:05.120> properties 00:06:05.990 --> 00:06:06.000 align:start position:0% already uh check some of the properties 00:06:06.000 --> 00:06:07.670 align:start position:0% already uh check some of the properties so<00:06:06.199> the<00:06:06.360> differential<00:06:06.960> property<00:06:07.319> based 00:06:07.670 --> 00:06:07.680 align:start position:0% so the differential property based 00:06:07.680 --> 00:06:09.990 align:start position:0% so the differential property based testing<00:06:08.120> is<00:06:08.280> already<00:06:08.639> in<00:06:08.800> place<00:06:09.080> and<00:06:09.319> what<00:06:09.680> we 00:06:09.990 --> 00:06:10.000 align:start position:0% testing is already in place and what we 00:06:10.000 --> 00:06:12.950 align:start position:0% testing is already in place and what we we<00:06:10.160> do<00:06:10.440> with<00:06:10.840> uh<00:06:11.000> our<00:06:11.520> in<00:06:11.680> our<00:06:11.919> compliance<00:06:12.400> tool 00:06:12.950 --> 00:06:12.960 align:start position:0% we do with uh our in our compliance tool 00:06:12.960 --> 00:06:16.230 align:start position:0% we do with uh our in our compliance tool is<00:06:13.160> just<00:06:13.479> add<00:06:13.800> one<00:06:14.000> more<00:06:14.440> property<00:06:15.440> uh<00:06:15.680> which 00:06:16.230 --> 00:06:16.240 align:start position:0% is just add one more property uh which 00:06:16.240 --> 00:06:19.670 align:start position:0% is just add one more property uh which uh<00:06:16.400> is<00:06:16.599> to<00:06:16.840> check<00:06:17.160> weights<00:06:17.479> of<00:06:17.720> viable<00:06:18.120> for<00:06:18.360> hat 00:06:19.670 --> 00:06:19.680 align:start position:0% uh is to check weights of viable for hat 00:06:19.680 --> 00:06:23.390 align:start position:0% uh is to check weights of viable for hat blocks<00:06:20.680> okay<00:06:20.840> so<00:06:21.039> we<00:06:21.160> want<00:06:21.440> to<00:06:21.919> check<00:06:22.199> that<00:06:22.360> for 00:06:23.390 --> 00:06:23.400 align:start position:0% blocks okay so we want to check that for 00:06:23.400 --> 00:06:27.909 align:start position:0% blocks okay so we want to check that for Choice<00:06:24.400> uh<00:06:24.599> Ro<00:06:25.280> is<00:06:25.479> executed<00:06:26.479> correctly<00:06:27.479> but 00:06:27.909 --> 00:06:27.919 align:start position:0% Choice uh Ro is executed correctly but 00:06:27.919 --> 00:06:30.550 align:start position:0% Choice uh Ro is executed correctly but just<00:06:28.199> covering<00:06:28.680> various<00:06:29.080> execution<00:06:29.759> pass<00:06:30.360> is 00:06:30.550 --> 00:06:30.560 align:start position:0% just covering various execution pass is 00:06:30.560 --> 00:06:34.270 align:start position:0% just covering various execution pass is not<00:06:30.840> enough<00:06:31.840> because<00:06:32.599> um<00:06:33.319> the<00:06:33.599> through 00:06:34.270 --> 00:06:34.280 align:start position:0% not enough because um the through 00:06:34.280 --> 00:06:36.670 align:start position:0% not enough because um the through executed<00:06:34.880> on<00:06:35.080> many<00:06:35.360> nodes<00:06:35.759> and<00:06:35.919> they're 00:06:36.670 --> 00:06:36.680 align:start position:0% executed on many nodes and they're 00:06:36.680 --> 00:06:39.029 align:start position:0% executed on many nodes and they're interacting<00:06:37.680> and<00:06:37.840> building<00:06:38.280> blocks<00:06:38.720> using 00:06:39.029 --> 00:06:39.039 align:start position:0% interacting and building blocks using 00:06:39.039 --> 00:06:42.589 align:start position:0% interacting and building blocks using the<00:06:39.240> rule<00:06:40.199> and<00:06:40.280> so<00:06:40.560> we<00:06:40.960> actually<00:06:41.599> what<00:06:41.800> we<00:06:42.000> want 00:06:42.589 --> 00:06:42.599 align:start position:0% the rule and so we actually what we want 00:06:42.599 --> 00:06:46.309 align:start position:0% the rule and so we actually what we want is<00:06:43.080> to<00:06:44.080> capture<00:06:44.960> this 00:06:46.309 --> 00:06:46.319 align:start position:0% is to capture this 00:06:46.319 --> 00:06:50.909 align:start position:0% is to capture this interactions<00:06:47.319> but<00:06:47.599> we<00:06:48.280> do<00:06:48.560> not<00:06:49.560> uh<00:06:50.319> enumerate 00:06:50.909 --> 00:06:50.919 align:start position:0% interactions but we do not uh enumerate 00:06:50.919 --> 00:06:53.390 align:start position:0% interactions but we do not uh enumerate all<00:06:51.240> possible<00:06:51.759> scenarios<00:06:52.720> and<00:06:52.840> so<00:06:53.000> we<00:06:53.160> use 00:06:53.390 --> 00:06:53.400 align:start position:0% all possible scenarios and so we use 00:06:53.400 --> 00:06:54.790 align:start position:0% all possible scenarios and so we use modelbased 00:06:54.790 --> 00:06:54.800 align:start position:0% modelbased 00:06:54.800 --> 00:06:58.309 align:start position:0% modelbased approach<00:06:55.800> um<00:06:56.280> our<00:06:56.560> models<00:06:57.080> basically<00:06:57.879> allows 00:06:58.309 --> 00:06:58.319 align:start position:0% approach um our models basically allows 00:06:58.319 --> 00:07:00.990 align:start position:0% approach um our models basically allows us<00:06:58.479> to<00:06:58.680> focus<00:06:59.080> on<00:06:59.319> the<00:06:59.759> aspects<00:07:00.240> that<00:07:00.479> are 00:07:00.990 --> 00:07:01.000 align:start position:0% us to focus on the aspects that are 00:07:01.000 --> 00:07:03.629 align:start position:0% us to focus on the aspects that are interesting<00:07:02.000> abstract<00:07:02.560> away<00:07:02.879> from<00:07:03.120> other 00:07:03.629 --> 00:07:03.639 align:start position:0% interesting abstract away from other 00:07:03.639 --> 00:07:07.150 align:start position:0% interesting abstract away from other stuff<00:07:04.639> and<00:07:04.840> we<00:07:05.039> have<00:07:05.240> three<00:07:05.479> models<00:07:06.039> here<00:07:06.599> FFG 00:07:07.150 --> 00:07:07.160 align:start position:0% stuff and we have three models here FFG 00:07:07.160 --> 00:07:09.430 align:start position:0% stuff and we have three models here FFG checkpoint<00:07:07.800> three<00:07:08.120> shapes<00:07:08.800> block<00:07:09.160> three 00:07:09.430 --> 00:07:09.440 align:start position:0% checkpoint three shapes block three 00:07:09.440 --> 00:07:11.749 align:start position:0% checkpoint three shapes block three shapes<00:07:10.199> and<00:07:10.400> also<00:07:10.759> filter<00:07:11.199> block<00:07:11.520> three 00:07:11.749 --> 00:07:11.759 align:start position:0% shapes and also filter block three 00:07:11.759 --> 00:07:14.710 align:start position:0% shapes and also filter block three predicates<00:07:12.360> coverage<00:07:13.160> model<00:07:14.160> and<00:07:14.479> each 00:07:14.710 --> 00:07:14.720 align:start position:0% predicates coverage model and each 00:07:14.720 --> 00:07:18.110 align:start position:0% predicates coverage model and each models<00:07:15.319> for<00:07:15.560> example<00:07:15.960> we<00:07:16.160> have<00:07:16.840> 10<00:07:17.199> blocks<00:07:17.960> and 00:07:18.110 --> 00:07:18.120 align:start position:0% models for example we have 10 blocks and 00:07:18.120 --> 00:07:21.629 align:start position:0% models for example we have 10 blocks and we<00:07:18.319> have<00:07:18.800> various<00:07:19.520> trees<00:07:19.960> constructed<00:07:20.479> of<00:07:21.120> of 00:07:21.629 --> 00:07:21.639 align:start position:0% we have various trees constructed of of 00:07:21.639 --> 00:07:23.950 align:start position:0% we have various trees constructed of of these<00:07:21.840> 10<00:07:22.160> blocks<00:07:22.800> and<00:07:22.919> so<00:07:23.120> we<00:07:23.319> basically<00:07:23.800> want 00:07:23.950 --> 00:07:23.960 align:start position:0% these 10 blocks and so we basically want 00:07:23.960 --> 00:07:27.150 align:start position:0% these 10 blocks and so we basically want to<00:07:24.160> generate<00:07:24.599> a<00:07:24.800> test<00:07:25.120> Vector<00:07:25.479> for<00:07:25.919> each<00:07:26.919> of 00:07:27.150 --> 00:07:27.160 align:start position:0% to generate a test Vector for each of 00:07:27.160 --> 00:07:29.510 align:start position:0% to generate a test Vector for each of these<00:07:27.360> three<00:07:27.680> shape<00:07:28.400> and<00:07:28.599> if<00:07:28.759> we<00:07:28.919> are<00:07:29.120> able<00:07:29.360> to 00:07:29.510 --> 00:07:29.520 align:start position:0% these three shape and if we are able to 00:07:29.520 --> 00:07:32.950 align:start position:0% these three shape and if we are able to to<00:07:29.639> do<00:07:29.800> that<00:07:30.039> then<00:07:30.160> we<00:07:30.520> have<00:07:31.520> 100%<00:07:32.280> coverage<00:07:32.759> of 00:07:32.950 --> 00:07:32.960 align:start position:0% to do that then we have 100% coverage of 00:07:32.960 --> 00:07:36.150 align:start position:0% to do that then we have 100% coverage of our<00:07:33.440> model<00:07:34.440> and<00:07:34.639> for<00:07:34.879> our<00:07:35.240> three<00:07:35.479> models<00:07:35.879> we 00:07:36.150 --> 00:07:36.160 align:start position:0% our model and for our three models we 00:07:36.160 --> 00:07:39.270 align:start position:0% our model and for our three models we currently<00:07:37.160> uh<00:07:37.319> optained<00:07:38.000> a<00:07:38.199> thousand<00:07:38.800> of 00:07:39.270 --> 00:07:39.280 align:start position:0% currently uh optained a thousand of 00:07:39.280 --> 00:07:42.230 align:start position:0% currently uh optained a thousand of solutions<00:07:40.280> but<00:07:40.720> in<00:07:40.919> practice<00:07:41.280> it<00:07:41.440> can<00:07:41.639> be 00:07:42.230 --> 00:07:42.240 align:start position:0% solutions but in practice it can be 00:07:42.240 --> 00:07:45.029 align:start position:0% solutions but in practice it can be arbitrarily<00:07:43.240> larger<00:07:44.240> so<00:07:44.479> it<00:07:44.639> can<00:07:44.800> be<00:07:44.919> a 00:07:45.029 --> 00:07:45.039 align:start position:0% arbitrarily larger so it can be a 00:07:45.039 --> 00:07:47.909 align:start position:0% arbitrarily larger so it can be a million<00:07:45.400> models<00:07:45.800> no<00:07:46.440> problem<00:07:47.440> yeah<00:07:47.560> so<00:07:47.720> to 00:07:47.909 --> 00:07:47.919 align:start position:0% million models no problem yeah so to 00:07:47.919 --> 00:07:49.869 align:start position:0% million models no problem yeah so to give<00:07:48.080> you<00:07:48.319> like<00:07:48.560> more<00:07:48.759> intuition<00:07:49.280> behind<00:07:49.639> how 00:07:49.869 --> 00:07:49.879 align:start position:0% give you like more intuition behind how 00:07:49.879 --> 00:07:52.189 align:start position:0% give you like more intuition behind how this<00:07:50.240> uh<00:07:50.360> model<00:07:50.720> based<00:07:51.120> generation<00:07:51.680> Works 00:07:52.189 --> 00:07:52.199 align:start position:0% this uh model based generation Works 00:07:52.199 --> 00:07:53.710 align:start position:0% this uh model based generation Works let's<00:07:52.400> consider<00:07:52.720> the<00:07:52.840> F<00:07:52.960> ofg<00:07:53.199> check<00:07:53.400> points 00:07:53.710 --> 00:07:53.720 align:start position:0% let's consider the F ofg check points 00:07:53.720 --> 00:07:56.390 align:start position:0% let's consider the F ofg check points model<00:07:54.720> uh<00:07:54.879> this<00:07:55.000> model<00:07:55.319> is<00:07:55.479> parameterized<00:07:56.199> by 00:07:56.390 --> 00:07:56.400 align:start position:0% model uh this model is parameterized by 00:07:56.400 --> 00:07:59.749 align:start position:0% model uh this model is parameterized by two<00:07:56.599> main<00:07:56.919> parameters<00:07:57.919> uh<00:07:58.080> which<00:07:58.199> are<00:07:58.879> uh<00:07:59.639> of 00:07:59.749 --> 00:07:59.759 align:start position:0% two main parameters uh which are uh of 00:07:59.759 --> 00:08:02.710 align:start position:0% two main parameters uh which are uh of EPO<00:08:00.360> and<00:08:00.759> number<00:08:00.960> of<00:08:01.120> Super<00:08:01.479> majority<00:08:01.879> links 00:08:02.710 --> 00:08:02.720 align:start position:0% EPO and number of Super majority links 00:08:02.720 --> 00:08:04.790 align:start position:0% EPO and number of Super majority links and<00:08:02.960> here<00:08:03.080> is<00:08:03.280> the<00:08:03.479> example<00:08:03.919> of<00:08:04.240> a<00:08:04.400> couple<00:08:04.639> of 00:08:04.790 --> 00:08:04.800 align:start position:0% and here is the example of a couple of 00:08:04.800 --> 00:08:08.270 align:start position:0% and here is the example of a couple of solutions<00:08:05.639> that<00:08:05.840> satisfy<00:08:06.840> uh<00:08:07.720> this<00:08:07.879> model 00:08:08.270 --> 00:08:08.280 align:start position:0% solutions that satisfy uh this model 00:08:08.280 --> 00:08:11.270 align:start position:0% solutions that satisfy uh this model with<00:08:08.840> four<00:08:09.199> EPO<00:08:09.960> and<00:08:10.240> two<00:08:10.479> super<00:08:10.800> majority 00:08:11.270 --> 00:08:11.280 align:start position:0% with four EPO and two super majority 00:08:11.280 --> 00:08:14.670 align:start position:0% with four EPO and two super majority links<00:08:12.280> and<00:08:12.680> uh<00:08:13.319> on<00:08:13.520> the<00:08:13.680> on<00:08:13.879> the<00:08:14.319> if<00:08:14.400> you<00:08:14.520> look 00:08:14.670 --> 00:08:14.680 align:start position:0% links and uh on the on the if you look 00:08:14.680 --> 00:08:18.029 align:start position:0% links and uh on the on the if you look at<00:08:14.840> the<00:08:15.039> top<00:08:15.479> uh<00:08:15.680> deok<00:08:16.120> number<00:08:16.360> four<00:08:17.360> uh<00:08:17.879> in 00:08:18.029 --> 00:08:18.039 align:start position:0% at the top uh deok number four uh in 00:08:18.039 --> 00:08:20.350 align:start position:0% at the top uh deok number four uh in this<00:08:18.280> case<00:08:18.479> will<00:08:18.680> be<00:08:18.840> finalized<00:08:19.840> according<00:08:20.159> to 00:08:20.350 --> 00:08:20.360 align:start position:0% this case will be finalized according to 00:08:20.360 --> 00:08:24.309 align:start position:0% this case will be finalized according to FFG<00:08:21.199> checkpoint<00:08:22.039> to<00:08:22.240> to<00:08:22.400> to<00:08:22.759> to<00:08:22.960> the<00:08:23.759> finality 00:08:24.309 --> 00:08:24.319 align:start position:0% FFG checkpoint to to to to the finality 00:08:24.319 --> 00:08:27.270 align:start position:0% FFG checkpoint to to to to the finality Gadget<00:08:25.080> rules<00:08:25.639> and<00:08:26.039> uh<00:08:26.240> in<00:08:26.360> the<00:08:26.560> SEC<00:08:26.800> in<00:08:26.960> the<00:08:27.159> in 00:08:27.270 --> 00:08:27.280 align:start position:0% Gadget rules and uh in the SEC in the in 00:08:27.280 --> 00:08:29.029 align:start position:0% Gadget rules and uh in the SEC in the in the<00:08:27.479> second<00:08:27.840> case<00:08:28.039> which<00:08:28.199> is<00:08:28.319> on<00:08:28.479> the<00:08:28.639> bottom 00:08:29.029 --> 00:08:29.039 align:start position:0% the second case which is on the bottom 00:08:29.039 --> 00:08:32.310 align:start position:0% the second case which is on the bottom the<00:08:29.520> e<00:08:29.680> book<00:08:29.919> number<00:08:30.599> two<00:08:30.919> will<00:08:31.080> be<00:08:31.320> finalized 00:08:32.310 --> 00:08:32.320 align:start position:0% the e book number two will be finalized 00:08:32.320 --> 00:08:35.110 align:start position:0% the e book number two will be finalized so<00:08:33.039> basically<00:08:33.959> uh<00:08:34.240> when<00:08:34.399> we<00:08:34.519> do<00:08:34.719> the<00:08:34.880> test 00:08:35.110 --> 00:08:35.120 align:start position:0% so basically uh when we do the test 00:08:35.120 --> 00:08:37.230 align:start position:0% so basically uh when we do the test generation<00:08:35.640> we<00:08:35.839> ask<00:08:36.200> the<00:08:36.399> constraint<00:08:36.839> solver 00:08:37.230 --> 00:08:37.240 align:start position:0% generation we ask the constraint solver 00:08:37.240 --> 00:08:38.790 align:start position:0% generation we ask the constraint solver to<00:08:37.519> find<00:08:37.880> all 00:08:38.790 --> 00:08:38.800 align:start position:0% to find all 00:08:38.800 --> 00:08:42.430 align:start position:0% to find all possible<00:08:39.800> uh<00:08:40.800> combinations<00:08:41.519> of<00:08:41.760> Justified 00:08:42.430 --> 00:08:42.440 align:start position:0% possible uh combinations of Justified 00:08:42.440 --> 00:08:46.070 align:start position:0% possible uh combinations of Justified and<00:08:42.599> finalized<00:08:43.479> points<00:08:43.919> given<00:08:44.320> the<00:08:44.839> um<00:08:45.839> some 00:08:46.070 --> 00:08:46.080 align:start position:0% and finalized points given the um some 00:08:46.080 --> 00:08:49.710 align:start position:0% and finalized points given the um some certain<00:08:46.399> model<00:08:46.839> inputs<00:08:47.600> and<00:08:48.000> uh<00:08:48.360> we<00:08:48.519> also<00:08:48.839> run 00:08:49.710 --> 00:08:49.720 align:start position:0% certain model inputs and uh we also run 00:08:49.720 --> 00:08:53.590 align:start position:0% certain model inputs and uh we also run uh<00:08:50.240> this<00:08:51.160> these<00:08:51.360> models<00:08:52.279> uh<00:08:52.720> with<00:08:53.240> uh 00:08:53.590 --> 00:08:53.600 align:start position:0% uh this these models uh with uh 00:08:53.600 --> 00:08:56.310 align:start position:0% uh this these models uh with uh different<00:08:53.920> inputs<00:08:54.519> like<00:08:55.519> uh<00:08:55.640> you<00:08:55.720> can<00:08:55.920> run<00:08:56.120> it 00:08:56.310 --> 00:08:56.320 align:start position:0% different inputs like uh you can run it 00:08:56.320 --> 00:08:58.829 align:start position:0% different inputs like uh you can run it like<00:08:56.519> with<00:08:56.680> 10<00:08:56.920> EPO<00:08:57.399> and<00:08:57.720> five<00:08:58.040> Super<00:08:58.399> majority 00:08:58.829 --> 00:08:58.839 align:start position:0% like with 10 EPO and five Super majority 00:08:58.839 --> 00:09:00.670 align:start position:0% like with 10 EPO and five Super majority links<00:08:59.120> with<00:08:59.279> 10<00:08:59.560> ooks<00:08:59.920> and<00:09:00.079> four<00:09:00.320> super 00:09:00.670 --> 00:09:00.680 align:start position:0% links with 10 ooks and four super 00:09:00.680 --> 00:09:02.710 align:start position:0% links with 10 ooks and four super majority<00:09:01.079> links<00:09:01.399> and<00:09:01.600> so<00:09:01.760> on<00:09:02.240> and<00:09:02.399> this<00:09:02.519> is 00:09:02.710 --> 00:09:02.720 align:start position:0% majority links and so on and this is 00:09:02.720 --> 00:09:06.710 align:start position:0% majority links and so on and this is gives<00:09:02.959> us<00:09:03.279> a<00:09:03.519> lot<00:09:03.959> of<00:09:04.560> uh<00:09:05.279> a<00:09:05.440> lot<00:09:05.640> of<00:09:06.279> uh 00:09:06.710 --> 00:09:06.720 align:start position:0% gives us a lot of uh a lot of uh 00:09:06.720 --> 00:09:12.030 align:start position:0% gives us a lot of uh a lot of uh solutions<00:09:07.440> to<00:09:07.800> further<00:09:08.399> work<00:09:08.880> with<00:09:09.720> uh<00:09:10.480> in<00:09:10.680> our 00:09:12.030 --> 00:09:12.040 align:start position:0% solutions to further work with uh in our 00:09:12.040 --> 00:09:15.150 align:start position:0% solutions to further work with uh in our generation<00:09:13.040> okay<00:09:13.399> so<00:09:13.600> now<00:09:13.800> we<00:09:14.000> have<00:09:14.560> uh<00:09:14.839> many 00:09:15.150 --> 00:09:15.160 align:start position:0% generation okay so now we have uh many 00:09:15.160 --> 00:09:17.949 align:start position:0% generation okay so now we have uh many model<00:09:15.560> Solutions<00:09:16.200> and<00:09:16.920> everyone<00:09:17.600> can<00:09:17.800> be 00:09:17.949 --> 00:09:17.959 align:start position:0% model Solutions and everyone can be 00:09:17.959 --> 00:09:20.230 align:start position:0% model Solutions and everyone can be turned<00:09:18.440> into<00:09:18.760> a<00:09:18.959> test<00:09:19.279> Vector<00:09:19.760> but<00:09:19.920> that<00:09:20.079> can 00:09:20.230 --> 00:09:20.240 align:start position:0% turned into a test Vector but that can 00:09:20.240 --> 00:09:22.110 align:start position:0% turned into a test Vector but that can be<00:09:20.399> done<00:09:20.600> in<00:09:20.800> different<00:09:21.120> ways<00:09:21.399> for<00:09:21.560> example 00:09:22.110 --> 00:09:22.120 align:start position:0% be done in different ways for example 00:09:22.120 --> 00:09:25.790 align:start position:0% be done in different ways for example validators<00:09:22.800> can<00:09:23.040> vote<00:09:23.800> for<00:09:24.200> different<00:09:25.200> blocks 00:09:25.790 --> 00:09:25.800 align:start position:0% validators can vote for different blocks 00:09:25.800 --> 00:09:28.630 align:start position:0% validators can vote for different blocks but<00:09:26.279> as<00:09:26.399> a<00:09:26.600> result<00:09:26.959> we<00:09:27.120> can<00:09:27.399> have<00:09:27.680> the<00:09:27.880> same 00:09:28.630 --> 00:09:28.640 align:start position:0% but as a result we can have the same 00:09:28.640 --> 00:09:31.590 align:start position:0% but as a result we can have the same shape 00:09:31.590 --> 00:09:31.600 align:start position:0% 00:09:31.600 --> 00:09:34.949 align:start position:0% and<00:09:31.880> and<00:09:32.120> so<00:09:33.120> we<00:09:33.320> use<00:09:33.920> randomization<00:09:34.760> to 00:09:34.949 --> 00:09:34.959 align:start position:0% and and so we use randomization to 00:09:34.959 --> 00:09:36.910 align:start position:0% and and so we use randomization to instantiate<00:09:35.720> these<00:09:35.959> model<00:09:36.320> Solutions 00:09:36.910 --> 00:09:36.920 align:start position:0% instantiate these model Solutions 00:09:36.920 --> 00:09:38.550 align:start position:0% instantiate these model Solutions basically<00:09:37.360> flipping<00:09:37.720> a 00:09:38.550 --> 00:09:38.560 align:start position:0% basically flipping a 00:09:38.560 --> 00:09:43.069 align:start position:0% basically flipping a coin<00:09:39.560> and<00:09:40.440> uh<00:09:40.640> after<00:09:41.079> we<00:09:41.680> have<00:09:41.839> a<00:09:42.480> test<00:09:42.760> Suite 00:09:43.069 --> 00:09:43.079 align:start position:0% coin and uh after we have a test Suite 00:09:43.079 --> 00:09:46.509 align:start position:0% coin and uh after we have a test Suite of<00:09:43.240> test<00:09:43.519> vectors<00:09:43.959> we<00:09:44.079> can<00:09:44.279> additionally<00:09:45.040> do 00:09:46.509 --> 00:09:46.519 align:start position:0% of test vectors we can additionally do 00:09:46.519 --> 00:09:49.630 align:start position:0% of test vectors we can additionally do fing<00:09:47.519> um<00:09:48.240> it's<00:09:48.519> important<00:09:49.040> because<00:09:49.320> our 00:09:49.630 --> 00:09:49.640 align:start position:0% fing um it's important because our 00:09:49.640 --> 00:09:52.790 align:start position:0% fing um it's important because our models<00:09:50.200> actually<00:09:50.959> assume<00:09:51.959> that<00:09:52.120> all<00:09:52.399> events 00:09:52.790 --> 00:09:52.800 align:start position:0% models actually assume that all events 00:09:52.800 --> 00:09:54.990 align:start position:0% models actually assume that all events arrive<00:09:53.399> in<00:09:53.640> time<00:09:54.160> which<00:09:54.320> is 00:09:54.990 --> 00:09:55.000 align:start position:0% arrive in time which is 00:09:55.000 --> 00:09:56.870 align:start position:0% arrive in time which is unrealistically<00:09:56.000> but<00:09:56.160> we<00:09:56.279> can<00:09:56.519> easily 00:09:56.870 --> 00:09:56.880 align:start position:0% unrealistically but we can easily 00:09:56.880 --> 00:09:59.790 align:start position:0% unrealistically but we can easily overcome<00:09:57.360> it<00:09:57.560> by<00:09:57.720> shuffling<00:09:58.560> uh<00:09:58.720> duplication 00:09:59.790 --> 00:09:59.800 align:start position:0% overcome it by shuffling uh duplication 00:09:59.800 --> 00:10:01.990 align:start position:0% overcome it by shuffling uh duplication of<00:10:00.040> messages<00:10:00.680> and<00:10:00.839> dropping<00:10:01.240> some<00:10:01.519> messages 00:10:01.990 --> 00:10:02.000 align:start position:0% of messages and dropping some messages 00:10:02.000 --> 00:10:04.269 align:start position:0% of messages and dropping some messages and<00:10:02.240> also<00:10:02.800> by<00:10:03.000> mutating 00:10:04.269 --> 00:10:04.279 align:start position:0% and also by mutating 00:10:04.279 --> 00:10:07.230 align:start position:0% and also by mutating messages<00:10:05.279> we<00:10:05.480> will<00:10:05.880> also<00:10:06.320> plan<00:10:06.600> to<00:10:06.800> implement 00:10:07.230 --> 00:10:07.240 align:start position:0% messages we will also plan to implement 00:10:07.240 --> 00:10:10.030 align:start position:0% messages we will also plan to implement in<00:10:07.440> future<00:10:08.079> coverage<00:10:08.560> guided<00:10:08.920> fing<00:10:09.360> of 00:10:10.030 --> 00:10:10.040 align:start position:0% in future coverage guided fing of 00:10:10.040 --> 00:10:12.990 align:start position:0% in future coverage guided fing of implementations<00:10:11.040> and<00:10:11.320> this<00:10:11.920> uh<00:10:12.360> randomized 00:10:12.990 --> 00:10:13.000 align:start position:0% implementations and this uh randomized 00:10:13.000 --> 00:10:15.350 align:start position:0% implementations and this uh randomized instantiation<00:10:13.680> and<00:10:13.800> fing<00:10:14.279> allows<00:10:14.680> us<00:10:15.079> to 00:10:15.350 --> 00:10:15.360 align:start position:0% instantiation and fing allows us to 00:10:15.360 --> 00:10:17.630 align:start position:0% instantiation and fing allows us to increase<00:10:15.640> the<00:10:15.800> number<00:10:16.079> of<00:10:16.279> tests<00:10:17.040> in<00:10:17.440> by 00:10:17.630 --> 00:10:17.640 align:start position:0% increase the number of tests in by 00:10:17.640 --> 00:10:19.949 align:start position:0% increase the number of tests in by orders<00:10:17.959> of 00:10:19.949 --> 00:10:19.959 align:start position:0% orders of 00:10:19.959 --> 00:10:22.509 align:start position:0% orders of magnitude<00:10:20.959> yeah<00:10:21.160> here<00:10:21.320> is<00:10:21.560> the<00:10:21.800> example<00:10:22.279> of 00:10:22.509 --> 00:10:22.519 align:start position:0% magnitude yeah here is the example of 00:10:22.519 --> 00:10:25.870 align:start position:0% magnitude yeah here is the example of how<00:10:22.760> the<00:10:22.920> randomization<00:10:23.720> is<00:10:23.959> used<00:10:24.680> uh<00:10:25.320> as<00:10:25.519> Alex 00:10:25.870 --> 00:10:25.880 align:start position:0% how the randomization is used uh as Alex 00:10:25.880 --> 00:10:27.949 align:start position:0% how the randomization is used uh as Alex mentioned<00:10:26.399> we<00:10:26.560> have<00:10:26.760> these<00:10:26.959> model<00:10:27.360> Solutions 00:10:27.949 --> 00:10:27.959 align:start position:0% mentioned we have these model Solutions 00:10:27.959 --> 00:10:33.230 align:start position:0% mentioned we have these model Solutions and<00:10:28.120> we<00:10:28.240> use<00:10:28.560> them<00:10:28.800> to<00:10:29.800> uh<00:10:30.120> produce<00:10:31.440> uh<00:10:32.440> like 00:10:33.230 --> 00:10:33.240 align:start position:0% and we use them to uh produce uh like 00:10:33.240 --> 00:10:36.310 align:start position:0% and we use them to uh produce uh like various<00:10:33.640> test<00:10:34.000> vectors<00:10:35.000> and<00:10:35.760> on<00:10:35.920> the<00:10:36.079> top 00:10:36.310 --> 00:10:36.320 align:start position:0% various test vectors and on the top 00:10:36.320 --> 00:10:38.629 align:start position:0% various test vectors and on the top there<00:10:36.440> is<00:10:36.639> just<00:10:36.880> a<00:10:37.079> model<00:10:37.880> uh<00:10:38.120> which<00:10:38.480> which 00:10:38.629 --> 00:10:38.639 align:start position:0% there is just a model uh which which 00:10:38.639 --> 00:10:40.790 align:start position:0% there is just a model uh which which says<00:10:39.360> that<00:10:39.600> basically<00:10:40.079> there<00:10:40.200> is<00:10:40.320> a<00:10:40.480> block 00:10:40.790 --> 00:10:40.800 align:start position:0% says that basically there is a block 00:10:40.800 --> 00:10:43.430 align:start position:0% says that basically there is a block that<00:10:41.000> has<00:10:41.240> two<00:10:41.639> children<00:10:42.639> the<00:10:42.800> client<00:10:43.200> has 00:10:43.430 --> 00:10:43.440 align:start position:0% that has two children the client has 00:10:43.440 --> 00:10:45.030 align:start position:0% that has two children the client has nothing<00:10:43.680> to<00:10:43.800> do<00:10:43.959> with<00:10:44.120> this<00:10:44.279> model<00:10:44.560> it<00:10:44.720> cannot 00:10:45.030 --> 00:10:45.040 align:start position:0% nothing to do with this model it cannot 00:10:45.040 --> 00:10:48.430 align:start position:0% nothing to do with this model it cannot run<00:10:45.800> uh<00:10:46.000> this<00:10:46.160> model<00:10:46.600> because<00:10:47.600> uh<00:10:47.839> to<00:10:48.040> to<00:10:48.240> to 00:10:48.430 --> 00:10:48.440 align:start position:0% run uh this model because uh to to to 00:10:48.440 --> 00:10:51.509 align:start position:0% run uh this model because uh to to to make<00:10:48.639> it<00:10:49.360> a<00:10:49.480> real<00:10:49.760> test<00:10:50.040> Vector<00:10:50.560> to<00:10:50.760> make<00:10:50.880> it<00:10:51.320> we 00:10:51.509 --> 00:10:51.519 align:start position:0% make it a real test Vector to make it we 00:10:51.519 --> 00:10:53.030 align:start position:0% make it a real test Vector to make it we have<00:10:51.639> to<00:10:51.800> make<00:10:51.959> it<00:10:52.079> a<00:10:52.200> real<00:10:52.440> blockchain<00:10:52.920> that 00:10:53.030 --> 00:10:53.040 align:start position:0% have to make it a real blockchain that 00:10:53.040 --> 00:10:55.949 align:start position:0% have to make it a real blockchain that follows<00:10:53.440> the<00:10:53.560> ethereum<00:10:54.040> protocol<00:10:54.600> rules<00:10:55.600> and 00:10:55.949 --> 00:10:55.959 align:start position:0% follows the ethereum protocol rules and 00:10:55.959 --> 00:10:59.509 align:start position:0% follows the ethereum protocol rules and uh<00:10:56.079> we<00:10:56.240> use<00:10:56.519> consensus<00:10:57.360> spec<00:10:58.360> uh<00:10:58.600> specs<00:10:58.959> for 00:10:59.509 --> 00:10:59.519 align:start position:0% uh we use consensus spec uh specs for 00:10:59.519 --> 00:11:01.990 align:start position:0% uh we use consensus spec uh specs for for<00:10:59.760> doing<00:11:00.120> this<00:11:00.279> for<00:11:00.519> making<00:11:00.920> a<00:11:01.440> these<00:11:01.639> blocks 00:11:01.990 --> 00:11:02.000 align:start position:0% for doing this for making a these blocks 00:11:02.000 --> 00:11:05.190 align:start position:0% for doing this for making a these blocks turn<00:11:02.399> into<00:11:03.160> uh<00:11:03.560> making<00:11:03.959> this<00:11:04.480> uh<00:11:04.880> block 00:11:05.190 --> 00:11:05.200 align:start position:0% turn into uh making this uh block 00:11:05.200 --> 00:11:07.110 align:start position:0% turn into uh making this uh block dependency<00:11:05.760> to<00:11:05.880> turn<00:11:06.120> it<00:11:06.240> into<00:11:06.480> real<00:11:06.800> blocks 00:11:07.110 --> 00:11:07.120 align:start position:0% dependency to turn it into real blocks 00:11:07.120 --> 00:11:09.870 align:start position:0% dependency to turn it into real blocks and<00:11:07.320> real<00:11:07.680> votes<00:11:08.680> and<00:11:09.160> in<00:11:09.320> this<00:11:09.519> case<00:11:09.760> the 00:11:09.870 --> 00:11:09.880 align:start position:0% and real votes and in this case the 00:11:09.880 --> 00:11:12.150 align:start position:0% and real votes and in this case the model<00:11:10.200> does<00:11:10.399> not<00:11:10.720> answer<00:11:11.040> you<00:11:11.200> to<00:11:11.480> many<00:11:11.800> many 00:11:12.150 --> 00:11:12.160 align:start position:0% model does not answer you to many many 00:11:12.160 --> 00:11:14.670 align:start position:0% model does not answer you to many many questions<00:11:12.760> that<00:11:13.320> the<00:11:13.440> protocol<00:11:13.880> need<00:11:14.200> to<00:11:14.519> you 00:11:14.670 --> 00:11:14.680 align:start position:0% questions that the protocol need to you 00:11:14.680 --> 00:11:17.030 align:start position:0% questions that the protocol need to you know<00:11:14.880> to<00:11:15.360> to<00:11:15.639> to<00:11:15.839> create<00:11:16.120> an<00:11:16.320> instance<00:11:16.720> of<00:11:16.839> a 00:11:17.030 --> 00:11:17.040 align:start position:0% know to to to create an instance of a 00:11:17.040 --> 00:11:19.990 align:start position:0% know to to to create an instance of a blockchain<00:11:18.040> those<00:11:18.279> questions<00:11:18.680> such<00:11:18.920> as<00:11:19.440> like 00:11:19.990 --> 00:11:20.000 align:start position:0% blockchain those questions such as like 00:11:20.000 --> 00:11:22.990 align:start position:0% blockchain those questions such as like uh<00:11:20.760> which<00:11:20.959> validators<00:11:21.639> are<00:11:21.839> voting<00:11:22.279> for<00:11:22.760> which 00:11:22.990 --> 00:11:23.000 align:start position:0% uh which validators are voting for which 00:11:23.000 --> 00:11:25.710 align:start position:0% uh which validators are voting for which block<00:11:23.639> every<00:11:23.920> single<00:11:24.279> slot<00:11:25.040> uh<00:11:25.399> where<00:11:25.600> where 00:11:25.710 --> 00:11:25.720 align:start position:0% block every single slot uh where where 00:11:25.720 --> 00:11:28.069 align:start position:0% block every single slot uh where where is<00:11:26.000> the<00:11:26.560> maybe<00:11:26.839> there<00:11:26.959> is<00:11:27.079> an<00:11:27.320> empty<00:11:27.680> slot 00:11:28.069 --> 00:11:28.079 align:start position:0% is the maybe there is an empty slot 00:11:28.079 --> 00:11:29.990 align:start position:0% is the maybe there is an empty slot between<00:11:28.440> those<00:11:28.680> blocks 00:11:29.990 --> 00:11:30.000 align:start position:0% between those blocks 00:11:30.000 --> 00:11:32.629 align:start position:0% between those blocks uh<00:11:31.000> which<00:11:31.160> is<00:11:31.480> the<00:11:31.720> total<00:11:32.079> number<00:11:32.480> of 00:11:32.629 --> 00:11:32.639 align:start position:0% uh which is the total number of 00:11:32.639 --> 00:11:35.230 align:start position:0% uh which is the total number of validators<00:11:33.560> participating<00:11:34.279> at<00:11:34.680> Moment<00:11:35.000> In 00:11:35.230 --> 00:11:35.240 align:start position:0% validators participating at Moment In 00:11:35.240 --> 00:11:38.110 align:start position:0% validators participating at Moment In Time<00:11:35.800> whether<00:11:36.000> the<00:11:36.160> message<00:11:36.839> is<00:11:37.399> like<00:11:37.880> some 00:11:38.110 --> 00:11:38.120 align:start position:0% Time whether the message is like some 00:11:38.120 --> 00:11:41.150 align:start position:0% Time whether the message is like some message<00:11:38.480> is<00:11:38.760> invalid<00:11:39.320> or<00:11:39.560> not<00:11:40.120> and<00:11:40.200> so<00:11:40.399> forth 00:11:41.150 --> 00:11:41.160 align:start position:0% message is invalid or not and so forth 00:11:41.160 --> 00:11:44.350 align:start position:0% message is invalid or not and so forth and<00:11:41.519> for<00:11:42.079> every<00:11:42.959> case<00:11:43.360> for<00:11:43.600> every<00:11:43.880> possible 00:11:44.350 --> 00:11:44.360 align:start position:0% and for every case for every possible 00:11:44.360 --> 00:11:47.190 align:start position:0% and for every case for every possible case<00:11:44.760> here<00:11:45.560> uh<00:11:45.639> to<00:11:45.839> answer<00:11:46.240> such<00:11:46.519> questions<00:11:46.959> to 00:11:47.190 --> 00:11:47.200 align:start position:0% case here uh to answer such questions to 00:11:47.200 --> 00:11:49.710 align:start position:0% case here uh to answer such questions to to<00:11:47.360> decide<00:11:47.639> on<00:11:47.920> such<00:11:48.320> uh<00:11:48.519> things<00:11:48.959> we<00:11:49.240> flip<00:11:49.560> a 00:11:49.710 --> 00:11:49.720 align:start position:0% to decide on such uh things we flip a 00:11:49.720 --> 00:11:53.670 align:start position:0% to decide on such uh things we flip a coin<00:11:50.519> so<00:11:50.720> we<00:11:50.920> have<00:11:51.160> like<00:11:51.480> a<00:11:52.360> every<00:11:52.880> every<00:11:53.399> test 00:11:53.670 --> 00:11:53.680 align:start position:0% coin so we have like a every every test 00:11:53.680 --> 00:11:55.910 align:start position:0% coin so we have like a every every test generator<00:11:54.120> run<00:11:54.440> there<00:11:54.560> is<00:11:54.720> a<00:11:55.200> combination<00:11:55.760> of 00:11:55.910 --> 00:11:55.920 align:start position:0% generator run there is a combination of 00:11:55.920 --> 00:11:58.629 align:start position:0% generator run there is a combination of model<00:11:56.279> solutions<00:11:56.920> that<00:11:57.040> we<00:11:57.240> use<00:11:58.120> and<00:11:58.440> a 00:11:58.629 --> 00:11:58.639 align:start position:0% model solutions that we use and a 00:11:58.639 --> 00:12:02.269 align:start position:0% model solutions that we use and a randomness<00:11:59.240> seed<00:11:59.920> and<00:12:00.320> uh<00:12:00.920> running<00:12:01.399> the<00:12:01.639> same 00:12:02.269 --> 00:12:02.279 align:start position:0% randomness seed and uh running the same 00:12:02.279 --> 00:12:04.110 align:start position:0% randomness seed and uh running the same uh<00:12:02.440> combination<00:12:02.920> of<00:12:03.079> model<00:12:03.399> Solutions<00:12:03.920> with 00:12:04.110 --> 00:12:04.120 align:start position:0% uh combination of model Solutions with 00:12:04.120 --> 00:12:06.949 align:start position:0% uh combination of model Solutions with different<00:12:04.440> Randomness<00:12:05.000> seed<00:12:05.360> can<00:12:05.920> yield<00:12:06.440> a 00:12:06.949 --> 00:12:06.959 align:start position:0% different Randomness seed can yield a 00:12:06.959 --> 00:12:10.110 align:start position:0% different Randomness seed can yield a different<00:12:07.800> uh<00:12:07.920> test<00:12:08.279> Vector<00:12:09.279> what<00:12:09.440> matters 00:12:10.110 --> 00:12:10.120 align:start position:0% different uh test Vector what matters 00:12:10.120 --> 00:12:11.829 align:start position:0% different uh test Vector what matters here<00:12:10.360> is<00:12:10.560> that<00:12:10.720> this<00:12:10.880> test<00:12:11.120> Vector<00:12:11.440> will<00:12:11.600> be 00:12:11.829 --> 00:12:11.839 align:start position:0% here is that this test Vector will be 00:12:11.839 --> 00:12:13.870 align:start position:0% here is that this test Vector will be completely<00:12:12.399> different<00:12:13.120> uh<00:12:13.240> from<00:12:13.440> the<00:12:13.560> FK 00:12:13.870 --> 00:12:13.880 align:start position:0% completely different uh from the FK 00:12:13.880 --> 00:12:16.790 align:start position:0% completely different uh from the FK Choice<00:12:14.639> point<00:12:14.839> of<00:12:15.000> view<00:12:15.440> so<00:12:15.720> like<00:12:15.880> in<00:12:16.120> this<00:12:16.600> uh 00:12:16.790 --> 00:12:16.800 align:start position:0% Choice point of view so like in this uh 00:12:16.800 --> 00:12:20.189 align:start position:0% Choice point of view so like in this uh example<00:12:17.279> there<00:12:17.600> are<00:12:18.600> the<00:12:18.800> had<00:12:19.320> TS<00:12:19.560> a<00:12:19.720> different 00:12:20.189 --> 00:12:20.199 align:start position:0% example there are the had TS a different 00:12:20.199 --> 00:12:22.470 align:start position:0% example there are the had TS a different so<00:12:20.480> but<00:12:20.720> the<00:12:20.880> model<00:12:21.199> is<00:12:21.440> the 00:12:22.470 --> 00:12:22.480 align:start position:0% so but the model is the 00:12:22.480 --> 00:12:25.269 align:start position:0% so but the model is the same<00:12:23.480> so<00:12:23.680> we<00:12:23.839> have<00:12:24.040> implemented<00:12:24.639> the<00:12:24.800> initial 00:12:25.269 --> 00:12:25.279 align:start position:0% same so we have implemented the initial 00:12:25.279 --> 00:12:27.430 align:start position:0% same so we have implemented the initial phase<00:12:25.560> of<00:12:25.720> the<00:12:25.880> strategy<00:12:26.480> and<00:12:26.680> this<00:12:26.880> work<00:12:27.240> was 00:12:27.430 --> 00:12:27.440 align:start position:0% phase of the strategy and this work was 00:12:27.440 --> 00:12:29.829 align:start position:0% phase of the strategy and this work was supported<00:12:27.920> by<00:12:28.040> a<00:12:28.160> grant<00:12:28.440> from<00:12:28.600> eum<00:12:29.199> foundation 00:12:29.829 --> 00:12:29.839 align:start position:0% supported by a grant from eum foundation 00:12:29.839 --> 00:12:32.790 align:start position:0% supported by a grant from eum foundation and<00:12:30.120> but<00:12:30.320> from<00:12:30.839> consensus<00:12:31.839> and<00:12:31.959> so<00:12:32.279> we<00:12:32.480> have<00:12:32.639> a 00:12:32.790 --> 00:12:32.800 align:start position:0% and but from consensus and so we have a 00:12:32.800 --> 00:12:35.910 align:start position:0% and but from consensus and so we have a test<00:12:33.120> generator<00:12:34.000> we<00:12:34.120> have<00:12:34.279> a<00:12:34.440> PR<00:12:35.000> in<00:12:35.360> consensus 00:12:35.910 --> 00:12:35.920 align:start position:0% test generator we have a PR in consensus 00:12:35.920 --> 00:12:39.230 align:start position:0% test generator we have a PR in consensus spec<00:12:36.800> repository<00:12:37.800> we<00:12:38.000> have<00:12:38.240> generated<00:12:38.920> three 00:12:39.230 --> 00:12:39.240 align:start position:0% spec repository we have generated three 00:12:39.240 --> 00:12:42.590 align:start position:0% spec repository we have generated three test<00:12:39.519> Suites<00:12:40.360> to<00:12:40.720> Tiny<00:12:41.040> and<00:12:41.279> small<00:12:42.240> uh<00:12:42.399> the 00:12:42.590 --> 00:12:42.600 align:start position:0% test Suites to Tiny and small uh the 00:12:42.600 --> 00:12:44.990 align:start position:0% test Suites to Tiny and small uh the test<00:12:42.800> Suites<00:12:43.120> for<00:12:43.320> initial<00:12:43.760> adoption<00:12:44.279> and<00:12:44.440> we 00:12:44.990 --> 00:12:45.000 align:start position:0% test Suites for initial adoption and we 00:12:45.000 --> 00:12:48.310 align:start position:0% test Suites for initial adoption and we also<00:12:45.920> the<00:12:46.079> main<00:12:46.440> standard<00:12:47.000> test<00:12:47.320> Suite<00:12:47.720> which 00:12:48.310 --> 00:12:48.320 align:start position:0% also the main standard test Suite which 00:12:48.320 --> 00:12:51.350 align:start position:0% also the main standard test Suite which contains<00:12:48.920> about<00:12:49.480> 13,000<00:12:50.480> of<00:12:50.720> test<00:12:51.079> which<00:12:51.240> I 00:12:51.350 --> 00:12:51.360 align:start position:0% contains about 13,000 of test which I 00:12:51.360 --> 00:12:55.470 align:start position:0% contains about 13,000 of test which I believe<00:12:51.639> is<00:12:51.839> enough<00:12:52.480> for<00:12:52.760> initial 00:12:55.470 --> 00:12:55.480 align:start position:0% 00:12:55.480 --> 00:12:59.230 align:start position:0% phase<00:12:56.480> yeah<00:12:57.040> and<00:12:57.320> so<00:12:57.560> we<00:12:57.720> did<00:12:58.040> the<00:12:58.839> as<00:12:58.959> a 00:12:59.230 --> 00:12:59.240 align:start position:0% phase yeah and so we did the as a 00:12:59.240 --> 00:13:01.550 align:start position:0% phase yeah and so we did the as a prototype<00:12:59.760> we<00:12:59.880> did<00:13:00.120> the<00:13:00.440> integration<00:13:01.199> of<00:13:01.399> this 00:13:01.550 --> 00:13:01.560 align:start position:0% prototype we did the integration of this 00:13:01.560 --> 00:13:05.550 align:start position:0% prototype we did the integration of this tool<00:13:01.839> in<00:13:02.199> taku<00:13:03.199> as<00:13:03.320> I<00:13:03.519> mentioned<00:13:04.320> before<00:13:05.320> uh 00:13:05.550 --> 00:13:05.560 align:start position:0% tool in taku as I mentioned before uh 00:13:05.560 --> 00:13:07.629 align:start position:0% tool in taku as I mentioned before uh there<00:13:05.760> there<00:13:05.880> is<00:13:06.079> already<00:13:06.880> uh<00:13:07.000> the<00:13:07.160> F<00:13:07.360> choice 00:13:07.629 --> 00:13:07.639 align:start position:0% there there is already uh the F choice 00:13:07.639 --> 00:13:09.629 align:start position:0% there there is already uh the F choice test<00:13:07.959> and<00:13:08.160> clients<00:13:08.560> already<00:13:08.839> know<00:13:09.079> how<00:13:09.199> to<00:13:09.360> run 00:13:09.629 --> 00:13:09.639 align:start position:0% test and clients already know how to run 00:13:09.639 --> 00:13:12.189 align:start position:0% test and clients already know how to run them<00:13:10.120> so<00:13:10.360> this<00:13:10.560> integration<00:13:11.199> was<00:13:11.639> relatively 00:13:12.189 --> 00:13:12.199 align:start position:0% them so this integration was relatively 00:13:12.199 --> 00:13:14.110 align:start position:0% them so this integration was relatively straightforward<00:13:13.199> we<00:13:13.360> added<00:13:13.720> the<00:13:13.880> new 00:13:14.110 --> 00:13:14.120 align:start position:0% straightforward we added the new 00:13:14.120 --> 00:13:16.829 align:start position:0% straightforward we added the new property<00:13:14.560> check<00:13:14.880> that<00:13:15.160> mentioned<00:13:15.560> before<00:13:16.560> uh 00:13:16.829 --> 00:13:16.839 align:start position:0% property check that mentioned before uh 00:13:16.839 --> 00:13:19.310 align:start position:0% property check that mentioned before uh found<00:13:17.720> some<00:13:18.000> issues<00:13:18.440> a<00:13:18.560> couple<00:13:18.800> of<00:13:18.959> them<00:13:19.120> are 00:13:19.310 --> 00:13:19.320 align:start position:0% found some issues a couple of them are 00:13:19.320 --> 00:13:21.790 align:start position:0% found some issues a couple of them are related<00:13:19.680> to<00:13:19.959> optimizations<00:13:20.800> I'll<00:13:21.000> cover<00:13:21.360> this 00:13:21.790 --> 00:13:21.800 align:start position:0% related to optimizations I'll cover this 00:13:21.800 --> 00:13:24.310 align:start position:0% related to optimizations I'll cover this uh<00:13:21.920> on<00:13:22.040> the<00:13:22.160> next<00:13:22.399> slide<00:13:23.079> and<00:13:23.240> we<00:13:23.399> found<00:13:23.959> four 00:13:24.310 --> 00:13:24.320 align:start position:0% uh on the next slide and we found four 00:13:24.320 --> 00:13:29.150 align:start position:0% uh on the next slide and we found four Edge<00:13:24.720> case<00:13:25.959> uh<00:13:26.959> four<00:13:27.279> edge<00:13:27.680> cases<00:13:28.560> uh<00:13:28.959> where 00:13:29.150 --> 00:13:29.160 align:start position:0% Edge case uh four edge cases uh where 00:13:29.160 --> 00:13:32.269 align:start position:0% Edge case uh four edge cases uh where where<00:13:29.560> TECO<00:13:30.120> is<00:13:30.320> not<00:13:30.680> kind<00:13:30.839> of<00:13:31.120> like<00:13:31.800> compliant 00:13:32.269 --> 00:13:32.279 align:start position:0% where TECO is not kind of like compliant 00:13:32.279 --> 00:13:35.189 align:start position:0% where TECO is not kind of like compliant to<00:13:32.480> the<00:13:32.680> spec<00:13:33.040> but<00:13:33.519> these<00:13:33.760> edge<00:13:34.079> cases<00:13:34.600> are 00:13:35.189 --> 00:13:35.199 align:start position:0% to the spec but these edge cases are 00:13:35.199 --> 00:13:38.310 align:start position:0% to the spec but these edge cases are very<00:13:35.600> very<00:13:36.240> unlikely<00:13:36.760> to<00:13:36.959> happen<00:13:37.360> on<00:13:37.639> any<00:13:38.079> any 00:13:38.310 --> 00:13:38.320 align:start position:0% very very unlikely to happen on any any 00:13:38.320 --> 00:13:41.629 align:start position:0% very very unlikely to happen on any any test<00:13:38.639> net<00:13:39.560> uh<00:13:39.680> including<00:13:40.079> the<00:13:40.199> main<00:13:40.480> net<00:13:41.240> and 00:13:41.629 --> 00:13:41.639 align:start position:0% test net uh including the main net and 00:13:41.639 --> 00:13:43.990 align:start position:0% test net uh including the main net and uh<00:13:42.279> uh<00:13:42.399> the<00:13:42.560> fact<00:13:42.760> that<00:13:42.880> we<00:13:43.040> found<00:13:43.360> those<00:13:43.680> edge 00:13:43.990 --> 00:13:44.000 align:start position:0% uh uh the fact that we found those edge 00:13:44.000 --> 00:13:47.470 align:start position:0% uh uh the fact that we found those edge cases<00:13:44.839> uh<00:13:45.079> shows<00:13:45.399> us<00:13:46.120> how<00:13:46.399> powerful<00:13:46.959> this<00:13:47.120> tool 00:13:47.470 --> 00:13:47.480 align:start position:0% cases uh shows us how powerful this tool 00:13:47.480 --> 00:13:50.910 align:start position:0% cases uh shows us how powerful this tool is<00:13:47.720> with<00:13:47.920> only<00:13:48.240> 13,000<00:13:49.240> tests<00:13:50.240> just<00:13:50.440> imagine 00:13:50.910 --> 00:13:50.920 align:start position:0% is with only 13,000 tests just imagine 00:13:50.920 --> 00:13:54.069 align:start position:0% is with only 13,000 tests just imagine what<00:13:51.800> would<00:13:52.000> it<00:13:52.160> be<00:13:52.639> like<00:13:53.000> uh<00:13:53.199> if<00:13:53.320> we<00:13:53.519> have<00:13:53.759> like 00:13:54.069 --> 00:13:54.079 align:start position:0% what would it be like uh if we have like 00:13:54.079 --> 00:13:57.550 align:start position:0% what would it be like uh if we have like a<00:13:54.320> thousand<00:13:55.120> uh<00:13:55.720> 100<00:13:56.279> 100,000<00:13:57.000> tests<00:13:57.320> or<00:13:57.440> a 00:13:57.550 --> 00:13:57.560 align:start position:0% a thousand uh 100 100,000 tests or a 00:13:57.560 --> 00:13:59.790 align:start position:0% a thousand uh 100 100,000 tests or a million<00:13:57.959> tests<00:13:58.639> and<00:13:59.079> we're<00:13:59.240> looking<00:13:59.440> forward 00:13:59.790 --> 00:13:59.800 align:start position:0% million tests and we're looking forward 00:13:59.800 --> 00:14:02.509 align:start position:0% million tests and we're looking forward to<00:14:00.160> have<00:14:00.480> this<00:14:00.680> tool<00:14:01.079> in<00:14:01.560> to<00:14:01.720> have<00:14:01.959> this<00:14:02.399> uh 00:14:02.509 --> 00:14:02.519 align:start position:0% to have this tool in to have this uh 00:14:02.519 --> 00:14:05.470 align:start position:0% to have this tool in to have this uh suit<00:14:02.880> integrated<00:14:03.480> with<00:14:03.880> other<00:14:04.880> uh<00:14:05.000> consens 00:14:05.470 --> 00:14:05.480 align:start position:0% suit integrated with other uh consens 00:14:05.480 --> 00:14:08.150 align:start position:0% suit integrated with other uh consens layer<00:14:05.759> clients<00:14:06.120> to<00:14:06.279> find<00:14:06.560> issues<00:14:06.880> in<00:14:07.120> them<00:14:07.399> as 00:14:08.150 --> 00:14:08.160 align:start position:0% layer clients to find issues in them as 00:14:08.160 --> 00:14:11.430 align:start position:0% layer clients to find issues in them as well<00:14:09.160> so<00:14:09.480> let's<00:14:09.680> look<00:14:09.880> at<00:14:10.040> test<00:14:10.240> Suite<00:14:10.560> details 00:14:11.430 --> 00:14:11.440 align:start position:0% well so let's look at test Suite details 00:14:11.440 --> 00:14:14.870 align:start position:0% well so let's look at test Suite details so<00:14:11.639> we<00:14:11.880> have<00:14:12.880> uh<00:14:13.399> test<00:14:13.720> groups<00:14:14.079> inside<00:14:14.680> test 00:14:14.870 --> 00:14:14.880 align:start position:0% so we have uh test groups inside test 00:14:14.880 --> 00:14:17.710 align:start position:0% so we have uh test groups inside test suits<00:14:15.240> for<00:14:15.360> example<00:14:15.720> block<00:14:16.040> three<00:14:16.399> focuses<00:14:17.000> on 00:14:17.710 --> 00:14:17.720 align:start position:0% suits for example block three focuses on 00:14:17.720 --> 00:14:20.629 align:start position:0% suits for example block three focuses on trees<00:14:18.120> of<00:14:18.440> various<00:14:18.880> shapes<00:14:19.519> and<00:14:19.759> block<00:14:20.120> weight 00:14:20.629 --> 00:14:20.639 align:start position:0% trees of various shapes and block weight 00:14:20.639 --> 00:14:23.910 align:start position:0% trees of various shapes and block weight we<00:14:21.360> try<00:14:21.600> to<00:14:21.839> produce<00:14:22.240> block<00:14:22.560> trees<00:14:23.000> where 00:14:23.910 --> 00:14:23.920 align:start position:0% we try to produce block trees where 00:14:23.920 --> 00:14:25.790 align:start position:0% we try to produce block trees where weights<00:14:24.199> are<00:14:24.399> different<00:14:24.920> distant<00:14:25.279> from<00:14:25.519> each 00:14:25.790 --> 00:14:25.800 align:start position:0% weights are different distant from each 00:14:25.800 --> 00:14:29.870 align:start position:0% weights are different distant from each other<00:14:26.800> we<00:14:27.000> also<00:14:27.399> have<00:14:27.560> a<00:14:27.720> shuffling<00:14:28.360> group<00:14:29.399> and 00:14:29.870 --> 00:14:29.880 align:start position:0% other we also have a shuffling group and 00:14:29.880 --> 00:14:33.230 align:start position:0% other we also have a shuffling group and uh<00:14:30.160> test<00:14:30.440> group<00:14:30.759> which<00:14:30.959> focus<00:14:31.320> on<00:14:32.120> a<00:14:32.360> test<00:14:32.720> s 00:14:33.230 --> 00:14:33.240 align:start position:0% uh test group which focus on a test s 00:14:33.240 --> 00:14:35.670 align:start position:0% uh test group which focus on a test s invalid<00:14:33.720> messages<00:14:34.480> and<00:14:34.759> combinations<00:14:35.440> of 00:14:35.670 --> 00:14:35.680 align:start position:0% invalid messages and combinations of 00:14:35.680 --> 00:14:38.670 align:start position:0% invalid messages and combinations of filter<00:14:36.120> B<00:14:36.480> three<00:14:36.839> predicates<00:14:37.839> and<00:14:38.000> overall<00:14:38.519> we 00:14:38.670 --> 00:14:38.680 align:start position:0% filter B three predicates and overall we 00:14:38.680 --> 00:14:42.990 align:start position:0% filter B three predicates and overall we have<00:14:39.040> about<00:14:39.519> 13,000<00:14:40.519> of<00:14:40.680> tests<00:14:41.480> right 00:14:42.990 --> 00:14:43.000 align:start position:0% have about 13,000 of tests right 00:14:43.000 --> 00:14:47.150 align:start position:0% have about 13,000 of tests right now<00:14:44.000> okay<00:14:44.320> uh<00:14:44.480> so<00:14:45.079> we<00:14:45.320> have<00:14:45.639> problems<00:14:46.519> and<00:14:46.800> one 00:14:47.150 --> 00:14:47.160 align:start position:0% now okay uh so we have problems and one 00:14:47.160 --> 00:14:49.269 align:start position:0% now okay uh so we have problems and one pro<00:14:47.600> uh<00:14:47.839> problems<00:14:48.399> is<00:14:48.600> that<00:14:48.839> advanced 00:14:49.269 --> 00:14:49.279 align:start position:0% pro uh problems is that advanced 00:14:49.279 --> 00:14:51.550 align:start position:0% pro uh problems is that advanced mutation<00:14:49.759> are<00:14:49.959> challenging<00:14:50.440> to<00:14:50.600> implement 00:14:51.550 --> 00:14:51.560 align:start position:0% mutation are challenging to implement 00:14:51.560 --> 00:14:54.430 align:start position:0% mutation are challenging to implement for<00:14:51.720> example<00:14:52.120> if<00:14:52.279> you<00:14:52.720> change<00:14:53.720> a<00:14:53.920> block<00:14:54.279> we 00:14:54.430 --> 00:14:54.440 align:start position:0% for example if you change a block we 00:14:54.440 --> 00:14:58.470 align:start position:0% for example if you change a block we need<00:14:54.680> to<00:14:55.440> rec<00:14:55.639> compul<00:14:56.519> recalculate<00:14:57.160> its<00:14:57.480> cash 00:14:58.470 --> 00:14:58.480 align:start position:0% need to rec compul recalculate its cash 00:14:58.480 --> 00:15:02.269 align:start position:0% need to rec compul recalculate its cash and<00:14:59.079> descendant<00:14:59.759> blocks<00:15:00.399> and<00:15:01.279> attestations 00:15:02.269 --> 00:15:02.279 align:start position:0% and descendant blocks and attestations 00:15:02.279 --> 00:15:05.790 align:start position:0% and descendant blocks and attestations should<00:15:02.480> be<00:15:02.680> recalculated<00:15:03.800> too<00:15:04.800> and<00:15:05.040> this<00:15:05.639> uh 00:15:05.790 --> 00:15:05.800 align:start position:0% should be recalculated too and this uh 00:15:05.800 --> 00:15:09.189 align:start position:0% should be recalculated too and this uh takes<00:15:06.199> time<00:15:06.600> so<00:15:07.199> test<00:15:07.839> generation<00:15:08.399> is<00:15:08.759> slow 00:15:09.189 --> 00:15:09.199 align:start position:0% takes time so test generation is slow 00:15:09.199 --> 00:15:11.509 align:start position:0% takes time so test generation is slow currently<00:15:09.639> it<00:15:09.759> takes<00:15:10.040> about<00:15:10.320> 10<00:15:10.600> seconds<00:15:11.000> per 00:15:11.509 --> 00:15:11.519 align:start position:0% currently it takes about 10 seconds per 00:15:11.519 --> 00:15:14.189 align:start position:0% currently it takes about 10 seconds per second<00:15:12.519> we<00:15:12.720> have<00:15:12.959> investigated<00:15:13.720> the<00:15:13.880> reasons 00:15:14.189 --> 00:15:14.199 align:start position:0% second we have investigated the reasons 00:15:14.199 --> 00:15:16.710 align:start position:0% second we have investigated the reasons for<00:15:14.480> that<00:15:14.759> and<00:15:15.040> okay<00:15:15.240> one<00:15:15.480> reason<00:15:15.800> is<00:15:16.000> that 00:15:16.710 --> 00:15:16.720 align:start position:0% for that and okay one reason is that 00:15:16.720 --> 00:15:20.629 align:start position:0% for that and okay one reason is that fork<00:15:17.160> Choice<00:15:17.440> Ru<00:15:18.279> is<00:15:19.160> expressed<00:15:19.600> using<00:15:20.000> python 00:15:20.629 --> 00:15:20.639 align:start position:0% fork Choice Ru is expressed using python 00:15:20.639 --> 00:15:22.389 align:start position:0% fork Choice Ru is expressed using python which<00:15:20.759> is<00:15:20.880> an<00:15:21.079> interpreted<00:15:21.720> language<00:15:22.240> and 00:15:22.389 --> 00:15:22.399 align:start position:0% which is an interpreted language and 00:15:22.399 --> 00:15:24.949 align:start position:0% which is an interpreted language and it's<00:15:22.600> low<00:15:23.560> we<00:15:23.839> but<00:15:24.120> that's<00:15:24.320> not<00:15:24.560> the<00:15:24.680> only 00:15:24.949 --> 00:15:24.959 align:start position:0% it's low we but that's not the only 00:15:24.959 --> 00:15:26.670 align:start position:0% it's low we but that's not the only source<00:15:25.279> of<00:15:25.440> the<00:15:25.639> problem<00:15:26.000> because<00:15:26.320> there<00:15:26.440> are 00:15:26.670 --> 00:15:26.680 align:start position:0% source of the problem because there are 00:15:26.680 --> 00:15:29.309 align:start position:0% source of the problem because there are also<00:15:27.120> some<00:15:27.360> slow<00:15:27.839> spec<00:15:28.160> components<00:15:28.800> they<00:15:29.079> are 00:15:29.309 --> 00:15:29.319 align:start position:0% also some slow spec components they are 00:15:29.319 --> 00:15:32.030 align:start position:0% also some slow spec components they are optimized<00:15:30.000> actually<00:15:30.480> but<00:15:30.839> there<00:15:30.959> are<00:15:31.160> still<00:15:31.880> a 00:15:32.030 --> 00:15:32.040 align:start position:0% optimized actually but there are still a 00:15:32.040 --> 00:15:33.189 align:start position:0% optimized actually but there are still a room<00:15:32.279> for 00:15:33.189 --> 00:15:33.199 align:start position:0% room for 00:15:33.199 --> 00:15:35.870 align:start position:0% room for improvement<00:15:34.199> and<00:15:34.480> this<00:15:34.920> uh<00:15:35.199> slow<00:15:35.600> test 00:15:35.870 --> 00:15:35.880 align:start position:0% improvement and this uh slow test 00:15:35.880 --> 00:15:39.430 align:start position:0% improvement and this uh slow test generation<00:15:36.440> limits<00:15:37.279> uh<00:15:37.480> the<00:15:37.720> Practical<00:15:38.440> size 00:15:39.430 --> 00:15:39.440 align:start position:0% generation limits uh the Practical size 00:15:39.440 --> 00:15:40.550 align:start position:0% generation limits uh the Practical size which<00:15:39.639> we<00:15:39.759> can 00:15:40.550 --> 00:15:40.560 align:start position:0% which we can 00:15:40.560 --> 00:15:42.870 align:start position:0% which we can achieve<00:15:41.560> yeah<00:15:41.839> as<00:15:41.959> I<00:15:42.079> mentioned<00:15:42.480> before<00:15:42.759> there 00:15:42.870 --> 00:15:42.880 align:start position:0% achieve yeah as I mentioned before there 00:15:42.880 --> 00:15:45.389 align:start position:0% achieve yeah as I mentioned before there are<00:15:43.040> some<00:15:43.240> optimizations<00:15:44.199> that<00:15:44.759> uh<00:15:45.079> cause 00:15:45.389 --> 00:15:45.399 align:start position:0% are some optimizations that uh cause 00:15:45.399 --> 00:15:47.790 align:start position:0% are some optimizations that uh cause some<00:15:45.639> test<00:15:46.040> fail<00:15:47.040> uh<00:15:47.279> and<00:15:47.560> those 00:15:47.790 --> 00:15:47.800 align:start position:0% some test fail uh and those 00:15:47.800 --> 00:15:50.590 align:start position:0% some test fail uh and those optimizations<00:15:48.680> are<00:15:49.600> that<00:15:49.800> we<00:15:50.040> have<00:15:50.240> faced 00:15:50.590 --> 00:15:50.600 align:start position:0% optimizations are that we have faced 00:15:50.600 --> 00:15:53.629 align:start position:0% optimizations are that we have faced with<00:15:50.880> are<00:15:51.160> related<00:15:51.639> to<00:15:52.279> uh<00:15:52.399> dos<00:15:52.759> protection<00:15:53.399> so 00:15:53.629 --> 00:15:53.639 align:start position:0% with are related to uh dos protection so 00:15:53.639 --> 00:15:55.790 align:start position:0% with are related to uh dos protection so some<00:15:53.880> AR<00:15:54.279> stations<00:15:54.600> some<00:15:54.800> old<00:15:55.120> attestations 00:15:55.790 --> 00:15:55.800 align:start position:0% some AR stations some old attestations 00:15:55.800 --> 00:15:59.670 align:start position:0% some AR stations some old attestations that<00:15:55.920> are<00:15:56.160> not<00:15:56.959> going<00:15:57.079> to<00:15:57.440> affect<00:15:57.880> the<00:15:58.480> uh<00:15:59.240> folk 00:15:59.670 --> 00:15:59.680 align:start position:0% that are not going to affect the uh folk 00:15:59.680 --> 00:16:03.110 align:start position:0% that are not going to affect the uh folk Choice<00:16:00.040> decision<00:16:01.040> are<00:16:01.440> discarded<00:16:02.399> in<00:16:02.600> Teo<00:16:02.959> for 00:16:03.110 --> 00:16:03.120 align:start position:0% Choice decision are discarded in Teo for 00:16:03.120 --> 00:16:05.350 align:start position:0% Choice decision are discarded in Teo for instance<00:16:03.560> and<00:16:04.040> in<00:16:04.240> other<00:16:04.519> clients<00:16:04.959> as<00:16:05.120> well 00:16:05.350 --> 00:16:05.360 align:start position:0% instance and in other clients as well 00:16:05.360 --> 00:16:07.110 align:start position:0% instance and in other clients as well and<00:16:05.680> different<00:16:06.000> clients<00:16:06.319> use<00:16:06.560> different<00:16:06.959> her 00:16:07.110 --> 00:16:07.120 align:start position:0% and different clients use different her 00:16:07.120 --> 00:16:09.790 align:start position:0% and different clients use different her istics<00:16:07.440> to<00:16:07.600> discard<00:16:08.079> such<00:16:08.600> attestations<00:16:09.600> and 00:16:09.790 --> 00:16:09.800 align:start position:0% istics to discard such attestations and 00:16:09.800 --> 00:16:12.509 align:start position:0% istics to discard such attestations and here<00:16:10.160> we<00:16:10.319> have<00:16:10.519> another<00:16:10.920> problem<00:16:11.800> uh<00:16:11.959> is<00:16:12.199> that 00:16:12.509 --> 00:16:12.519 align:start position:0% here we have another problem uh is that 00:16:12.519 --> 00:16:16.509 align:start position:0% here we have another problem uh is that the<00:16:12.920> uh<00:16:13.240> the<00:16:13.399> two<00:16:14.279> the<00:16:15.160> the<00:16:15.399> cute<00:16:15.880> cannot<00:16:16.279> be 00:16:16.509 --> 00:16:16.519 align:start position:0% the uh the two the the cute cannot be 00:16:16.519 --> 00:16:21.189 align:start position:0% the uh the two the the cute cannot be designed<00:16:17.120> to<00:16:18.519> uh<00:16:19.519> to<00:16:19.839> avoid<00:16:20.240> all<00:16:20.480> those<00:16:20.920> uh 00:16:21.189 --> 00:16:21.199 align:start position:0% designed to uh to avoid all those uh 00:16:21.199 --> 00:16:24.829 align:start position:0% designed to uh to avoid all those uh failures<00:16:22.199> and<00:16:22.680> uh<00:16:23.000> diff<00:16:23.959> and<00:16:24.399> because<00:16:24.639> of 00:16:24.829 --> 00:16:24.839 align:start position:0% failures and uh diff and because of 00:16:24.839 --> 00:16:26.829 align:start position:0% failures and uh diff and because of different<00:16:25.560> clients<00:16:25.920> has<00:16:26.160> different 00:16:26.829 --> 00:16:26.839 align:start position:0% different clients has different 00:16:26.839 --> 00:16:28.910 align:start position:0% different clients has different optimizations<00:16:27.519> and<00:16:27.680> different<00:16:27.959> her<00:16:28.160> ristics 00:16:28.910 --> 00:16:28.920 align:start position:0% optimizations and different her ristics 00:16:28.920 --> 00:16:31.110 align:start position:0% optimizations and different her ristics there<00:16:29.040> will<00:16:29.199> be<00:16:29.560> different<00:16:29.880> subset<00:16:30.360> of<00:16:30.600> tests 00:16:31.110 --> 00:16:31.120 align:start position:0% there will be different subset of tests 00:16:31.120 --> 00:16:34.069 align:start position:0% there will be different subset of tests that<00:16:31.360> are<00:16:31.680> failing<00:16:32.480> and<00:16:32.880> uh<00:16:33.519> we<00:16:33.680> have<00:16:33.920> like 00:16:34.069 --> 00:16:34.079 align:start position:0% that are failing and uh we have like 00:16:34.079 --> 00:16:36.189 align:start position:0% that are failing and uh we have like just<00:16:34.279> 13,000<00:16:35.079> tests<00:16:35.319> but<00:16:35.480> imagine<00:16:35.759> if<00:16:35.880> we<00:16:36.040> have 00:16:36.189 --> 00:16:36.199 align:start position:0% just 13,000 tests but imagine if we have 00:16:36.199 --> 00:16:39.069 align:start position:0% just 13,000 tests but imagine if we have a<00:16:36.319> million<00:16:36.720> tests<00:16:37.279> and<00:16:37.480> you<00:16:37.639> have<00:16:37.880> like<00:16:38.720> uh<00:16:39.000> I 00:16:39.069 --> 00:16:39.079 align:start position:0% a million tests and you have like uh I 00:16:39.079 --> 00:16:40.829 align:start position:0% a million tests and you have like uh I don't<00:16:39.199> know<00:16:39.440> thousand<00:16:39.800> of<00:16:39.959> tests<00:16:40.240> failing<00:16:40.720> and 00:16:40.829 --> 00:16:40.839 align:start position:0% don't know thousand of tests failing and 00:16:40.839 --> 00:16:42.790 align:start position:0% don't know thousand of tests failing and you<00:16:41.000> have<00:16:41.120> to<00:16:41.600> ensure 00:16:42.790 --> 00:16:42.800 align:start position:0% you have to ensure 00:16:42.800 --> 00:16:45.430 align:start position:0% you have to ensure that<00:16:43.800> you<00:16:43.920> have<00:16:44.040> to<00:16:44.279> real<00:16:44.680> you<00:16:44.880> have<00:16:45.000> to 00:16:45.430 --> 00:16:45.440 align:start position:0% that you have to real you have to 00:16:45.440 --> 00:16:47.389 align:start position:0% that you have to real you have to understand<00:16:45.680> whether<00:16:46.000> those<00:16:46.199> are<00:16:47.040> uh<00:16:47.160> because 00:16:47.389 --> 00:16:47.399 align:start position:0% understand whether those are uh because 00:16:47.399 --> 00:16:49.550 align:start position:0% understand whether those are uh because of<00:16:47.519> such<00:16:47.759> optimizations<00:16:48.519> and<00:16:48.759> this<00:16:48.839> is<00:16:49.120> legit 00:16:49.550 --> 00:16:49.560 align:start position:0% of such optimizations and this is legit 00:16:49.560 --> 00:16:51.590 align:start position:0% of such optimizations and this is legit case<00:16:49.759> or<00:16:50.040> whe<00:16:50.240> this<00:16:50.360> is<00:16:50.440> a<00:16:50.600> real<00:16:50.880> bug<00:16:51.240> so<00:16:51.480> this 00:16:51.590 --> 00:16:51.600 align:start position:0% case or whe this is a real bug so this 00:16:51.600 --> 00:16:53.389 align:start position:0% case or whe this is a real bug so this is<00:16:51.759> something<00:16:52.079> to<00:16:52.399> work<00:16:52.680> with<00:16:52.959> the<00:16:53.120> client 00:16:53.389 --> 00:16:53.399 align:start position:0% is something to work with the client 00:16:53.399 --> 00:16:54.629 align:start position:0% is something to work with the client developers 00:16:54.629 --> 00:16:54.639 align:start position:0% developers 00:16:54.639 --> 00:16:57.870 align:start position:0% developers on<00:16:55.639> and<00:16:56.040> as<00:16:56.120> a<00:16:56.279> Next<00:16:56.519> Step<00:16:56.839> as<00:16:56.959> a<00:16:57.079> next<00:16:57.240> low<00:16:57.560> step 00:16:57.870 --> 00:16:57.880 align:start position:0% on and as a Next Step as a next low step 00:16:57.880 --> 00:16:59.870 align:start position:0% on and as a Next Step as a next low step we<00:16:58.079> want<00:16:58.279> to<00:16:58.440> integrate<00:16:59.040> this<00:16:59.160> test<00:16:59.360> you<00:16:59.639> into 00:16:59.870 --> 00:16:59.880 align:start position:0% we want to integrate this test you into 00:16:59.880 --> 00:17:02.749 align:start position:0% we want to integrate this test you into other<00:17:00.360> consens<00:17:00.880> clients<00:17:01.360> here<00:17:01.560> we<00:17:01.759> engage 00:17:02.749 --> 00:17:02.759 align:start position:0% other consens clients here we engage 00:17:02.759 --> 00:17:06.510 align:start position:0% other consens clients here we engage other<00:17:03.000> client<00:17:03.360> developers<00:17:04.360> to<00:17:04.520> to<00:17:04.679> help<00:17:04.919> us 00:17:06.510 --> 00:17:06.520 align:start position:0% other client developers to to help us 00:17:06.520 --> 00:17:09.750 align:start position:0% other client developers to to help us with<00:17:07.520> and<00:17:08.000> yeah<00:17:08.280> yeah<00:17:08.520> okay<00:17:08.679> so<00:17:09.039> one<00:17:09.400> of<00:17:09.600> the 00:17:09.750 --> 00:17:09.760 align:start position:0% with and yeah yeah okay so one of the 00:17:09.760 --> 00:17:12.270 align:start position:0% with and yeah yeah okay so one of the most<00:17:10.120> important<00:17:11.120> things<00:17:11.360> to<00:17:11.520> do<00:17:11.720> is<00:17:11.839> to<00:17:12.000> speed 00:17:12.270 --> 00:17:12.280 align:start position:0% most important things to do is to speed 00:17:12.280 --> 00:17:15.429 align:start position:0% most important things to do is to speed up<00:17:12.480> test<00:17:13.000> generation<00:17:14.000> and<00:17:14.319> okay<00:17:14.559> one<00:17:15.079> thing 00:17:15.429 --> 00:17:15.439 align:start position:0% up test generation and okay one thing 00:17:15.439 --> 00:17:17.150 align:start position:0% up test generation and okay one thing that<00:17:15.559> we<00:17:15.679> want<00:17:15.839> to<00:17:16.000> do<00:17:16.120> is<00:17:16.240> to<00:17:16.439> transpile 00:17:17.150 --> 00:17:17.160 align:start position:0% that we want to do is to transpile 00:17:17.160 --> 00:17:20.230 align:start position:0% that we want to do is to transpile specification<00:17:17.799> to<00:17:18.000> C<00:17:18.400> or<00:17:18.600> to<00:17:18.839> n<00:17:19.199> rust<00:17:19.720> other 00:17:20.230 --> 00:17:20.240 align:start position:0% specification to C or to n rust other 00:17:20.240 --> 00:17:23.710 align:start position:0% specification to C or to n rust other compiled<00:17:21.120> language<00:17:22.120> and<00:17:22.280> of<00:17:22.400> course<00:17:22.640> there<00:17:23.480> a 00:17:23.710 --> 00:17:23.720 align:start position:0% compiled language and of course there a 00:17:23.720 --> 00:17:27.069 align:start position:0% compiled language and of course there a problem<00:17:24.280> that<00:17:24.640> a<00:17:24.880> transpired<00:17:25.760> code<00:17:26.760> there<00:17:26.919> can 00:17:27.069 --> 00:17:27.079 align:start position:0% problem that a transpired code there can 00:17:27.079 --> 00:17:29.710 align:start position:0% problem that a transpired code there can be<00:17:27.240> a<00:17:27.360> bu<00:17:27.679> into<00:17:27.959> the<00:17:28.199> translation 00:17:29.710 --> 00:17:29.720 align:start position:0% be a bu into the translation 00:17:29.720 --> 00:17:32.230 align:start position:0% be a bu into the translation but<00:17:30.400> uh<00:17:30.600> since<00:17:30.880> we<00:17:31.000> are<00:17:31.160> translating<00:17:31.880> function 00:17:32.230 --> 00:17:32.240 align:start position:0% but uh since we are translating function 00:17:32.240 --> 00:17:34.630 align:start position:0% but uh since we are translating function to<00:17:32.480> function<00:17:32.919> it's<00:17:33.200> actually<00:17:33.720> much<00:17:34.000> easier<00:17:34.400> to 00:17:34.630 --> 00:17:34.640 align:start position:0% to function it's actually much easier to 00:17:34.640 --> 00:17:37.710 align:start position:0% to function it's actually much easier to test<00:17:35.080> each<00:17:35.280> function<00:17:35.720> individually 00:17:37.710 --> 00:17:37.720 align:start position:0% test each function individually 00:17:37.720 --> 00:17:40.789 align:start position:0% test each function individually individually<00:17:38.720> and<00:17:39.080> another<00:17:39.720> approach<00:17:40.600> uh 00:17:40.789 --> 00:17:40.799 align:start position:0% individually and another approach uh 00:17:40.799 --> 00:17:43.669 align:start position:0% individually and another approach uh another<00:17:41.799> important<00:17:42.799> thing<00:17:43.120> is<00:17:43.280> that<00:17:43.480> to 00:17:43.669 --> 00:17:43.679 align:start position:0% another important thing is that to 00:17:43.679 --> 00:17:45.950 align:start position:0% another important thing is that to optimize<00:17:44.200> all<00:17:44.520> components<00:17:45.080> we<00:17:45.320> have<00:17:45.559> already 00:17:45.950 --> 00:17:45.960 align:start position:0% optimize all components we have already 00:17:45.960 --> 00:17:48.669 align:start position:0% optimize all components we have already experimented<00:17:46.640> with<00:17:46.880> faster<00:17:47.679> implementation 00:17:48.669 --> 00:17:48.679 align:start position:0% experimented with faster implementation 00:17:48.679 --> 00:17:53.190 align:start position:0% experimented with faster implementation so<00:17:49.120> we<00:17:49.919> as<00:17:50.039> a<00:17:50.240> result<00:17:50.640> we<00:17:50.919> expect<00:17:51.880> uh<00:17:52.120> that<00:17:52.679> our 00:17:53.190 --> 00:17:53.200 align:start position:0% so we as a result we expect uh that our 00:17:53.200 --> 00:17:55.870 align:start position:0% so we as a result we expect uh that our test<00:17:53.720> should<00:17:54.039> run<00:17:54.840> uh<00:17:55.120> test<00:17:55.400> should<00:17:55.600> be 00:17:55.870 --> 00:17:55.880 align:start position:0% test should run uh test should be 00:17:55.880 --> 00:17:59.390 align:start position:0% test should run uh test should be generated<00:17:56.520> at<00:17:56.679> least<00:17:56.919> 10<00:17:57.280> times<00:17:57.640> faster<00:17:59.080> and 00:17:59.390 --> 00:17:59.400 align:start position:0% generated at least 10 times faster and 00:17:59.400 --> 00:18:03.190 align:start position:0% generated at least 10 times faster and also<00:17:59.960> an<00:18:00.159> important<00:18:00.840> thing<00:18:01.840> is<00:18:02.080> to<00:18:02.440> implement 00:18:03.190 --> 00:18:03.200 align:start position:0% also an important thing is to implement 00:18:03.200 --> 00:18:06.630 align:start position:0% also an important thing is to implement coverage<00:18:03.760> guided<00:18:04.760> fast<00:18:05.159> testing<00:18:05.760> of<00:18:06.280> client 00:18:06.630 --> 00:18:06.640 align:start position:0% coverage guided fast testing of client 00:18:06.640 --> 00:18:09.510 align:start position:0% coverage guided fast testing of client implementation<00:18:07.559> and<00:18:07.760> for<00:18:08.039> this<00:18:08.280> reason<00:18:08.720> we 00:18:09.510 --> 00:18:09.520 align:start position:0% implementation and for this reason we 00:18:09.520 --> 00:18:14.149 align:start position:0% implementation and for this reason we it's<00:18:10.120> critical<00:18:10.720> to<00:18:10.960> have<00:18:11.919> fast<00:18:12.480> test 00:18:14.149 --> 00:18:14.159 align:start position:0% it's critical to have fast test 00:18:14.159 --> 00:18:16.669 align:start position:0% it's critical to have fast test Generation<00:18:15.159> Um<00:18:15.400> so<00:18:15.919> if<00:18:16.039> you<00:18:16.159> want<00:18:16.240> to<00:18:16.440> talk 00:18:16.669 --> 00:18:16.679 align:start position:0% Generation Um so if you want to talk 00:18:16.679 --> 00:18:18.870 align:start position:0% Generation Um so if you want to talk about<00:18:17.080> this<00:18:17.440> topic<00:18:17.799> reaches<00:18:18.240> out<00:18:18.559> you<00:18:18.640> can 00:18:18.870 --> 00:18:18.880 align:start position:0% about this topic reaches out you can 00:18:18.880 --> 00:18:21.789 align:start position:0% about this topic reaches out you can also<00:18:19.159> find<00:18:19.440> us<00:18:19.600> on<00:18:19.840> E<00:18:20.200> andd<00:18:20.600> Discord<00:18:21.440> here<00:18:21.600> is 00:18:21.789 --> 00:18:21.799 align:start position:0% also find us on E andd Discord here is 00:18:21.799 --> 00:18:24.549 align:start position:0% also find us on E andd Discord here is the<00:18:21.960> core<00:18:22.320> code<00:18:22.840> which<00:18:23.480> uh<00:18:23.679> links<00:18:24.000> you<00:18:24.159> to<00:18:24.320> a 00:18:24.549 --> 00:18:24.559 align:start position:0% the core code which uh links you to a 00:18:24.559 --> 00:18:27.510 align:start position:0% the core code which uh links you to a page<00:18:25.240> uh<00:18:25.480> with<00:18:25.600> the<00:18:25.840> references<00:18:26.840> uh<00:18:27.000> to<00:18:27.400> the 00:18:27.510 --> 00:18:27.520 align:start position:0% page uh with the references uh to the 00:18:27.520 --> 00:18:29.549 align:start position:0% page uh with the references uh to the work<00:18:27.760> we<00:18:27.919> did<00:18:28.440> there<00:18:28.559> is<00:18:28.840> a<00:18:29.039> description<00:18:29.440> of 00:18:29.549 --> 00:18:29.559 align:start position:0% work we did there is a description of 00:18:29.559 --> 00:18:32.110 align:start position:0% work we did there is a description of the<00:18:29.720> test<00:18:29.919> and<00:18:30.080> methodology<00:18:30.720> there<00:18:30.840> is<00:18:30.960> a<00:18:31.919> uh 00:18:32.110 --> 00:18:32.120 align:start position:0% the test and methodology there is a uh 00:18:32.120 --> 00:18:34.270 align:start position:0% the test and methodology there is a uh link<00:18:32.360> to<00:18:32.480> the<00:18:32.640> pr<00:18:33.000> to<00:18:33.200> this<00:18:33.400> pack<00:18:34.120> which 00:18:34.270 --> 00:18:34.280 align:start position:0% link to the pr to this pack which 00:18:34.280 --> 00:18:36.390 align:start position:0% link to the pr to this pack which introduces<00:18:34.840> the<00:18:34.960> test<00:18:35.200> generator<00:18:35.679> for<00:18:36.120> this 00:18:36.390 --> 00:18:36.400 align:start position:0% introduces the test generator for this 00:18:36.400 --> 00:18:40.990 align:start position:0% introduces the test generator for this suit<00:18:36.840> and<00:18:37.039> also<00:18:37.320> there<00:18:37.480> is<00:18:37.720> the<00:18:38.440> pr<00:18:39.320> uh<00:18:39.600> that<00:18:40.320> uh 00:18:40.990 --> 00:18:41.000 align:start position:0% suit and also there is the pr uh that uh 00:18:41.000 --> 00:18:44.310 align:start position:0% suit and also there is the pr uh that uh PR<00:18:41.320> to<00:18:41.480> te<00:18:42.039> that<00:18:42.200> integrates<00:18:42.720> the<00:18:42.880> Su<00:18:43.200> into<00:18:43.799> Teo 00:18:44.310 --> 00:18:44.320 align:start position:0% PR to te that integrates the Su into Teo 00:18:44.320 --> 00:18:46.950 align:start position:0% PR to te that integrates the Su into Teo thank<00:18:44.440> you<00:18:44.559> very<00:18:44.799> much<00:18:45.679> thank<00:18:45.880> you<00:18:46.640> thank<00:18:46.799> you 00:18:46.950 --> 00:18:46.960 align:start position:0% thank you very much thank you thank you 00:18:46.960 --> 00:18:49.750 align:start position:0% thank you very much thank you thank you very<00:18:47.159> much<00:18:47.400> Alex<00:18:47.720> and<00:18:47.919> mik<00:18:48.840> all 00:18:49.750 --> 00:18:49.760 align:start position:0% very much Alex and mik all 00:18:49.760 --> 00:18:52.029 align:start position:0% very much Alex and mik all right<00:18:50.760> great<00:18:51.000> to<00:18:51.120> see<00:18:51.360> you<00:18:51.480> got<00:18:51.640> a<00:18:51.720> lot<00:18:51.880> of 00:18:52.029 --> 00:18:52.039 align:start position:0% right great to see you got a lot of 00:18:52.039 --> 00:18:53.549 align:start position:0% right great to see you got a lot of support<00:18:52.400> from<00:18:52.600> the<00:18:52.799> audience<00:18:53.280> that's 00:18:53.549 --> 00:18:53.559 align:start position:0% support from the audience that's 00:18:53.559 --> 00:18:55.470 align:start position:0% support from the audience that's fantastic<00:18:54.440> now<00:18:54.679> I<00:18:54.799> wish<00:18:55.000> I<00:18:55.080> could<00:18:55.240> say<00:18:55.360> I 00:18:55.470 --> 00:18:55.480 align:start position:0% fantastic now I wish I could say I 00:18:55.480 --> 00:18:57.070 align:start position:0% fantastic now I wish I could say I understood<00:18:55.919> the<00:18:56.080> topic<00:18:56.320> of<00:18:56.480> the<00:18:56.600> content<00:18:56.960> but 00:18:57.070 --> 00:18:57.080 align:start position:0% understood the topic of the content but 00:18:57.080 --> 00:18:59.029 align:start position:0% understood the topic of the content but I<00:18:57.200> didn't<00:18:57.559> but<00:18:57.880> I'm<00:18:57.960> sure<00:18:58.200> the<00:18:58.280> audience 00:18:59.029 --> 00:18:59.039 align:start position:0% I didn't but I'm sure the audience 00:18:59.039 --> 00:19:00.710 align:start position:0% I didn't but I'm sure the audience because<00:18:59.200> they're<00:18:59.360> asking<00:18:59.679> lots<00:18:59.840> of<00:19:00.039> questions 00:19:00.710 --> 00:19:00.720 align:start position:0% because they're asking lots of questions 00:19:00.720 --> 00:19:02.549 align:start position:0% because they're asking lots of questions I'm<00:19:00.960> very<00:19:01.120> honest<00:19:01.520> about<00:19:01.760> it<00:19:01.919> you<00:19:02.039> know<00:19:02.440> uh 00:19:02.549 --> 00:19:02.559 align:start position:0% I'm very honest about it you know uh 00:19:02.559 --> 00:19:04.110 align:start position:0% I'm very honest about it you know uh please<00:19:02.799> upvote<00:19:03.240> your<00:19:03.400> questions<00:19:03.760> which<00:19:03.919> are 00:19:04.110 --> 00:19:04.120 align:start position:0% please upvote your questions which are 00:19:04.120 --> 00:19:05.510 align:start position:0% please upvote your questions which are most<00:19:04.360> popular<00:19:04.840> and<00:19:04.960> we're<00:19:05.080> going<00:19:05.200> to<00:19:05.280> look<00:19:05.400> at 00:19:05.510 --> 00:19:05.520 align:start position:0% most popular and we're going to look at 00:19:05.520 --> 00:19:07.110 align:start position:0% most popular and we're going to look at the<00:19:05.640> screen<00:19:05.919> and<00:19:06.240> take<00:19:06.400> a<00:19:06.520> run<00:19:06.799> through<00:19:06.960> the 00:19:07.110 --> 00:19:07.120 align:start position:0% the screen and take a run through the 00:19:07.120 --> 00:19:09.230 align:start position:0% the screen and take a run through the questions<00:19:07.520> right<00:19:07.679> at<00:19:07.799> the<00:19:08.000> top<00:19:08.480> do<00:19:08.679> you<00:19:08.919> run 00:19:09.230 --> 00:19:09.240 align:start position:0% questions right at the top do you run 00:19:09.240 --> 00:19:11.590 align:start position:0% questions right at the top do you run Fork<00:19:09.640> Choice<00:19:10.039> tests<00:19:10.520> covering<00:19:11.000> nonf 00:19:11.590 --> 00:19:11.600 align:start position:0% Fork Choice tests covering nonf 00:19:11.600 --> 00:19:13.950 align:start position:0% Fork Choice tests covering nonf finalization<00:19:12.600> with<00:19:12.880> multiple<00:19:13.400> Forks<00:19:13.799> who'd 00:19:13.950 --> 00:19:13.960 align:start position:0% finalization with multiple Forks who'd 00:19:13.960 --> 00:19:15.669 align:start position:0% finalization with multiple Forks who'd like<00:19:14.120> to<00:19:14.200> take<00:19:14.320> this<00:19:14.559> question<00:19:14.919> I<00:19:15.039> I<00:19:15.159> love<00:19:15.480> this 00:19:15.669 --> 00:19:15.679 align:start position:0% like to take this question I I love this 00:19:15.679 --> 00:19:18.750 align:start position:0% like to take this question I I love this question<00:19:16.120> because<00:19:16.679> I<00:19:17.320> before<00:19:17.840> this<00:19:18.080> talk<00:19:18.559> an 00:19:18.750 --> 00:19:18.760 align:start position:0% question because I before this talk an 00:19:18.760 --> 00:19:20.549 align:start position:0% question because I before this talk an hour<00:19:19.200> before<00:19:19.480> this<00:19:19.640> talk<00:19:19.880> I<00:19:20.000> was<00:19:20.200> thinking 00:19:20.549 --> 00:19:20.559 align:start position:0% hour before this talk I was thinking 00:19:20.559 --> 00:19:22.990 align:start position:0% hour before this talk I was thinking about<00:19:21.000> having<00:19:21.280> this<00:19:21.480> test<00:19:21.720> in<00:19:21.919> suit<00:19:22.320> because 00:19:22.990 --> 00:19:23.000 align:start position:0% about having this test in suit because 00:19:23.000 --> 00:19:24.950 align:start position:0% about having this test in suit because if<00:19:23.120> you<00:19:23.360> have<00:19:23.720> if<00:19:23.840> you've<00:19:24.120> been<00:19:24.320> at<00:19:24.480> the<00:19:24.640> dep 00:19:24.950 --> 00:19:24.960 align:start position:0% if you have if you've been at the dep 00:19:24.960 --> 00:19:27.190 align:start position:0% if you have if you've been at the dep Lance<00:19:25.559> presentation<00:19:26.280> who<00:19:26.440> was<00:19:26.640> presenting<00:19:27.080> on 00:19:27.190 --> 00:19:27.200 align:start position:0% Lance presentation who was presenting on 00:19:27.200 --> 00:19:29.230 align:start position:0% Lance presentation who was presenting on the<00:19:27.320> non-f<00:19:27.640> finality<00:19:28.280> and<00:19:28.440> how<00:19:28.760> can<00:19:28.880> it<00:19:29.039> kill 00:19:29.230 --> 00:19:29.240 align:start position:0% the non-f finality and how can it kill 00:19:29.240 --> 00:19:31.190 align:start position:0% the non-f finality and how can it kill ethereum<00:19:30.080> this<00:19:30.200> is<00:19:30.400> very<00:19:30.640> important<00:19:31.000> for 00:19:31.190 --> 00:19:31.200 align:start position:0% ethereum this is very important for 00:19:31.200 --> 00:19:33.230 align:start position:0% ethereum this is very important for clients<00:19:31.520> to<00:19:31.720> have<00:19:31.919> this<00:19:32.120> kind<00:19:32.280> of<00:19:32.799> testing 00:19:33.230 --> 00:19:33.240 align:start position:0% clients to have this kind of testing 00:19:33.240 --> 00:19:35.830 align:start position:0% clients to have this kind of testing suit<00:19:34.039> uh<00:19:34.159> we<00:19:34.280> haven't<00:19:34.720> think<00:19:35.240> thought<00:19:35.520> about 00:19:35.830 --> 00:19:35.840 align:start position:0% suit uh we haven't think thought about 00:19:35.840 --> 00:19:39.190 align:start position:0% suit uh we haven't think thought about this<00:19:36.039> much<00:19:36.440> but<00:19:36.840> I<00:19:37.039> think<00:19:37.360> it<00:19:37.480> is<00:19:37.919> doable<00:19:38.919> uh 00:19:39.190 --> 00:19:39.200 align:start position:0% this much but I think it is doable uh 00:19:39.200 --> 00:19:41.390 align:start position:0% this much but I think it is doable uh and<00:19:39.640> yeah<00:19:39.919> I'm<00:19:40.080> I'm<00:19:40.240> very<00:19:40.480> happy<00:19:40.720> to<00:19:40.919> discuss 00:19:41.390 --> 00:19:41.400 align:start position:0% and yeah I'm I'm very happy to discuss 00:19:41.400 --> 00:19:45.029 align:start position:0% and yeah I'm I'm very happy to discuss this<00:19:41.880> um<00:19:42.120> and<00:19:42.520> try<00:19:42.799> to<00:19:43.000> make<00:19:43.559> something<00:19:44.559> uh<00:19:44.880> and 00:19:45.029 --> 00:19:45.039 align:start position:0% this um and try to make something uh and 00:19:45.039 --> 00:19:47.110 align:start position:0% this um and try to make something uh and try<00:19:45.240> to<00:19:45.400> make<00:19:45.520> a<00:19:45.679> suit<00:19:46.080> that<00:19:46.280> would<00:19:46.559> test<00:19:46.840> nonf 00:19:47.110 --> 00:19:47.120 align:start position:0% try to make a suit that would test nonf 00:19:47.120 --> 00:19:49.029 align:start position:0% try to make a suit that would test nonf finality<00:19:47.679> and<00:19:47.919> let<00:19:48.240> clients<00:19:48.600> do<00:19:48.840> their 00:19:49.029 --> 00:19:49.039 align:start position:0% finality and let clients do their 00:19:49.039 --> 00:19:51.710 align:start position:0% finality and let clients do their optimizations<00:19:50.000> and<00:19:50.400> uh<00:19:50.799> check<00:19:51.120> them<00:19:51.320> by<00:19:51.559> just 00:19:51.710 --> 00:19:51.720 align:start position:0% optimizations and uh check them by just 00:19:51.720 --> 00:19:54.070 align:start position:0% optimizations and uh check them by just running<00:19:52.240> this<00:19:52.480> on<00:19:52.799> the<00:19:53.039> computer<00:19:53.679> excellent 00:19:54.070 --> 00:19:54.080 align:start position:0% running this on the computer excellent 00:19:54.080 --> 00:19:56.190 align:start position:0% running this on the computer excellent from<00:19:54.360> one<00:19:54.880> one<00:19:55.159> question<00:19:55.480> can<00:19:55.679> change 00:19:56.190 --> 00:19:56.200 align:start position:0% from one one question can change 00:19:56.200 --> 00:19:58.270 align:start position:0% from one one question can change everything<00:19:56.720> right<00:19:57.320> uh<00:19:57.520> now<00:19:57.760> the<00:19:57.919> question<00:19:58.200> at 00:19:58.270 --> 00:19:58.280 align:start position:0% everything right uh now the question at 00:19:58.280 --> 00:20:00.750 align:start position:0% everything right uh now the question at the<00:19:58.400> top<00:19:58.720> this<00:19:58.880> test<00:19:59.280> generator<00:20:00.080> Rock<00:20:00.520> so 00:20:00.750 --> 00:20:00.760 align:start position:0% the top this test generator Rock so 00:20:00.760 --> 00:20:02.470 align:start position:0% the top this test generator Rock so another<00:20:01.080> round<00:20:01.280> of<00:20:01.400> applause<00:20:01.720> for<00:20:02.039> creating 00:20:02.470 --> 00:20:02.480 align:start position:0% another round of applause for creating 00:20:02.480 --> 00:20:04.909 align:start position:0% another round of applause for creating such<00:20:02.640> a<00:20:02.799> wonderful<00:20:03.280> test 00:20:04.909 --> 00:20:04.919 align:start position:0% such a wonderful test 00:20:04.919 --> 00:20:07.029 align:start position:0% such a wonderful test generator<00:20:05.919> again<00:20:06.159> if<00:20:06.240> you<00:20:06.360> want<00:20:06.440> to<00:20:06.679> give 00:20:07.029 --> 00:20:07.039 align:start position:0% generator again if you want to give 00:20:07.039 --> 00:20:09.070 align:start position:0% generator again if you want to give feedback<00:20:07.720> before<00:20:07.960> you<00:20:08.120> go<00:20:08.320> into<00:20:08.520> the<00:20:08.640> Q&A 00:20:09.070 --> 00:20:09.080 align:start position:0% feedback before you go into the Q&A 00:20:09.080 --> 00:20:10.230 align:start position:0% feedback before you go into the Q&A there's<00:20:09.200> a<00:20:09.320> little<00:20:09.520> box<00:20:09.720> for<00:20:09.880> speaker 00:20:10.230 --> 00:20:10.240 align:start position:0% there's a little box for speaker 00:20:10.240 --> 00:20:11.990 align:start position:0% there's a little box for speaker feedback<00:20:10.880> please<00:20:11.080> go<00:20:11.280> and<00:20:11.400> write<00:20:11.600> it<00:20:11.720> there<00:20:11.840> so 00:20:11.990 --> 00:20:12.000 align:start position:0% feedback please go and write it there so 00:20:12.000 --> 00:20:13.549 align:start position:0% feedback please go and write it there so the<00:20:12.120> speakers<00:20:12.520> can<00:20:12.760> take<00:20:13.080> take<00:20:13.240> a<00:20:13.320> look<00:20:13.440> at 00:20:13.549 --> 00:20:13.559 align:start position:0% the speakers can take take a look at 00:20:13.559 --> 00:20:14.950 align:start position:0% the speakers can take take a look at that<00:20:13.679> but<00:20:13.799> well<00:20:13.960> done<00:20:14.120> to<00:20:14.280> both<00:20:14.400> of<00:20:14.520> you<00:20:14.679> let's 00:20:14.950 --> 00:20:14.960 align:start position:0% that but well done to both of you let's 00:20:14.960 --> 00:20:17.310 align:start position:0% that but well done to both of you let's go<00:20:15.120> to<00:20:15.240> the<00:20:15.400> next<00:20:15.600> few<00:20:15.840> questions<00:20:16.559> do<00:20:16.720> you<00:20:17.000> plan 00:20:17.310 --> 00:20:17.320 align:start position:0% go to the next few questions do you plan 00:20:17.320 --> 00:20:20.110 align:start position:0% go to the next few questions do you plan to<00:20:17.559> set<00:20:17.760> up<00:20:18.000> a<00:20:18.240> dashboard<00:20:19.200> to<00:20:19.360> show<00:20:19.720> test 00:20:20.110 --> 00:20:20.120 align:start position:0% to set up a dashboard to show test 00:20:20.120 --> 00:20:22.710 align:start position:0% to set up a dashboard to show test results<00:20:20.640> from<00:20:20.919> different<00:20:21.240> CL<00:20:21.799> clients<00:20:22.400> like 00:20:22.710 --> 00:20:22.720 align:start position:0% results from different CL clients like 00:20:22.720 --> 00:20:24.510 align:start position:0% results from different CL clients like Hive<00:20:23.120> who<00:20:23.200> wouldd<00:20:23.360> like<00:20:23.480> to<00:20:23.640> take<00:20:23.840> this<00:20:24.320> um 00:20:24.510 --> 00:20:24.520 align:start position:0% Hive who wouldd like to take this um 00:20:24.520 --> 00:20:27.669 align:start position:0% Hive who wouldd like to take this um I'll<00:20:24.760> take<00:20:25.000> this<00:20:25.559> I<00:20:26.559> we<00:20:26.799> don't<00:20:27.159> have<00:20:27.400> such 00:20:27.669 --> 00:20:27.679 align:start position:0% I'll take this I we don't have such 00:20:27.679 --> 00:20:30.070 align:start position:0% I'll take this I we don't have such dashboard<00:20:28.240> for<00:20:28.720> other<00:20:29.000> CL<00:20:29.400> tests<00:20:29.720> we<00:20:29.840> have<00:20:29.960> a 00:20:30.070 --> 00:20:30.080 align:start position:0% dashboard for other CL tests we have a 00:20:30.080 --> 00:20:32.909 align:start position:0% dashboard for other CL tests we have a plenty<00:20:30.320> of<00:20:30.440> Cl<00:20:30.720> tests<00:20:31.080> that<00:20:31.400> are<00:20:32.120> uh<00:20:32.400> run<00:20:32.720> by 00:20:32.909 --> 00:20:32.919 align:start position:0% plenty of Cl tests that are uh run by 00:20:32.919 --> 00:20:34.950 align:start position:0% plenty of Cl tests that are uh run by clients<00:20:33.799> and<00:20:34.159> yeah<00:20:34.280> I<00:20:34.360> haven't<00:20:34.640> thought 00:20:34.950 --> 00:20:34.960 align:start position:0% clients and yeah I haven't thought 00:20:34.960 --> 00:20:36.149 align:start position:0% clients and yeah I haven't thought thought<00:20:35.200> about<00:20:35.400> it<00:20:35.600> we<00:20:35.720> haven't<00:20:35.919> thought 00:20:36.149 --> 00:20:36.159 align:start position:0% thought about it we haven't thought 00:20:36.159 --> 00:20:38.230 align:start position:0% thought about it we haven't thought about<00:20:36.360> it<00:20:36.480> so<00:20:36.799> probably<00:20:37.159> not<00:20:37.520> because<00:20:37.960> yeah<00:20:38.080> if 00:20:38.230 --> 00:20:38.240 align:start position:0% about it so probably not because yeah if 00:20:38.240 --> 00:20:41.510 align:start position:0% about it so probably not because yeah if it<00:20:38.360> will<00:20:38.520> be<00:20:38.640> useful<00:20:39.039> we<00:20:39.200> can<00:20:39.520> but<00:20:40.400> maybe<00:20:40.679> not 00:20:41.510 --> 00:20:41.520 align:start position:0% it will be useful we can but maybe not 00:20:41.520 --> 00:20:43.710 align:start position:0% it will be useful we can but maybe not okay<00:20:42.520> all<00:20:42.679> right<00:20:42.840> let's<00:20:43.039> go<00:20:43.200> straight<00:20:43.440> to<00:20:43.559> the 00:20:43.710 --> 00:20:43.720 align:start position:0% okay all right let's go straight to the 00:20:43.720 --> 00:20:46.350 align:start position:0% okay all right let's go straight to the next<00:20:43.919> one<00:20:44.400> what<00:20:44.640> does<00:20:44.760> it<00:20:44.960> mean<00:20:45.559> for<00:20:45.799> the<00:20:45.919> fork 00:20:46.350 --> 00:20:46.360 align:start position:0% next one what does it mean for the fork 00:20:46.360 --> 00:20:49.470 align:start position:0% next one what does it mean for the fork Choice<00:20:46.720> spec<00:20:47.080> to<00:20:47.240> be<00:20:48.159> executable<00:20:49.159> go<00:20:49.280> ahead 00:20:49.470 --> 00:20:49.480 align:start position:0% Choice spec to be executable go ahead 00:20:49.480 --> 00:20:52.390 align:start position:0% Choice spec to be executable go ahead yeah<00:20:49.640> I'll<00:20:49.799> take<00:20:49.960> one<00:20:50.559> okay<00:20:51.080> so<00:20:51.760> um<00:20:52.120> it's 00:20:52.390 --> 00:20:52.400 align:start position:0% yeah I'll take one okay so um it's 00:20:52.400 --> 00:20:54.789 align:start position:0% yeah I'll take one okay so um it's expressed<00:20:52.960> as<00:20:53.080> a<00:20:53.360> python<00:20:53.880> code<00:20:54.400> so<00:20:54.559> it's 00:20:54.789 --> 00:20:54.799 align:start position:0% expressed as a python code so it's 00:20:54.799 --> 00:20:57.070 align:start position:0% expressed as a python code so it's basically<00:20:55.280> a<00:20:55.400> number<00:20:55.679> of<00:20:55.840> functions<00:20:56.640> and<00:20:56.799> some 00:20:57.070 --> 00:20:57.080 align:start position:0% basically a number of functions and some 00:20:57.080 --> 00:21:00.149 align:start position:0% basically a number of functions and some functions<00:20:57.640> prescribe<00:20:58.240> how<00:20:58.679> to<00:20:59.280> react<00:20:59.799> to 00:21:00.149 --> 00:21:00.159 align:start position:0% functions prescribe how to react to 00:21:00.159 --> 00:21:02.710 align:start position:0% functions prescribe how to react to events<00:21:00.760> or<00:21:01.000> messages<00:21:01.480> arriving<00:21:01.960> from<00:21:02.200> Network 00:21:02.710 --> 00:21:02.720 align:start position:0% events or messages arriving from Network 00:21:02.720 --> 00:21:06.909 align:start position:0% events or messages arriving from Network it's<00:21:03.280> on<00:21:03.840> block<00:21:04.840> on<00:21:05.520> attestation<00:21:06.240> on<00:21:06.640> on<00:21:06.760> a 00:21:06.909 --> 00:21:06.919 align:start position:0% it's on block on attestation on on a 00:21:06.919 --> 00:21:08.909 align:start position:0% it's on block on attestation on on a tester<00:21:07.320> session<00:21:07.720> and<00:21:07.919> some<00:21:08.200> others<00:21:08.679> there's 00:21:08.909 --> 00:21:08.919 align:start position:0% tester session and some others there's 00:21:08.919 --> 00:21:12.470 align:start position:0% tester session and some others there's also<00:21:09.360> time<00:21:10.000> tick<00:21:11.000> and<00:21:11.559> finally<00:21:11.960> you<00:21:12.120> have<00:21:12.279> a 00:21:12.470 --> 00:21:12.480 align:start position:0% also time tick and finally you have a 00:21:12.480 --> 00:21:16.549 align:start position:0% also time tick and finally you have a method<00:21:12.919> to<00:21:13.159> get<00:21:13.760> head<00:21:14.760> so<00:21:15.000> this<00:21:15.080> is<00:21:15.279> just<00:21:15.640> by<00:21:16.080> PL 00:21:16.549 --> 00:21:16.559 align:start position:0% method to get head so this is just by PL 00:21:16.559 --> 00:21:18.950 align:start position:0% method to get head so this is just by PL python<00:21:16.880> code<00:21:17.159> you<00:21:17.240> can<00:21:17.400> run<00:21:17.600> it<00:21:18.559> all<00:21:18.720> right 00:21:18.950 --> 00:21:18.960 align:start position:0% python code you can run it all right 00:21:18.960 --> 00:21:20.710 align:start position:0% python code you can run it all right let's<00:21:19.159> go<00:21:19.400> right<00:21:19.520> to<00:21:19.679> the<00:21:19.840> next<00:21:20.080> one<00:21:20.440> we<00:21:20.559> got 00:21:20.710 --> 00:21:20.720 align:start position:0% let's go right to the next one we got 00:21:20.720 --> 00:21:21.990 align:start position:0% let's go right to the next one we got three<00:21:20.960> questions<00:21:21.279> left<00:21:21.520> I<00:21:21.600> think<00:21:21.679> we<00:21:21.840> got 00:21:21.990 --> 00:21:22.000 align:start position:0% three questions left I think we got 00:21:22.000 --> 00:21:24.070 align:start position:0% three questions left I think we got enough<00:21:22.279> time<00:21:22.799> the<00:21:22.960> randomizing<00:21:23.679> weights 00:21:24.070 --> 00:21:24.080 align:start position:0% enough time the randomizing weights 00:21:24.080 --> 00:21:26.190 align:start position:0% enough time the randomizing weights model<00:21:24.559> can<00:21:24.760> take<00:21:24.960> an<00:21:25.200> arbitrary<00:21:25.760> tree<00:21:26.039> as 00:21:26.190 --> 00:21:26.200 align:start position:0% model can take an arbitrary tree as 00:21:26.200 --> 00:21:28.830 align:start position:0% model can take an arbitrary tree as model<00:21:26.559> question<00:21:26.880> mark<00:21:27.440> how<00:21:27.679> about<00:21:27.960> FFG 00:21:28.830 --> 00:21:28.840 align:start position:0% model question mark how about FFG 00:21:28.840 --> 00:21:30.470 align:start position:0% model question mark how about FFG information<00:21:29.640> who<00:21:29.720> would<00:21:29.880> like<00:21:30.039> to<00:21:30.159> answer 00:21:30.470 --> 00:21:30.480 align:start position:0% information who would like to answer 00:21:30.480 --> 00:21:33.630 align:start position:0% information who would like to answer this<00:21:30.640> one<00:21:31.480> I<00:21:31.760> can<00:21:32.760> yeah 00:21:33.630 --> 00:21:33.640 align:start position:0% this one I can yeah 00:21:33.640 --> 00:21:37.710 align:start position:0% this one I can yeah so<00:21:34.640> uh<00:21:34.960> the<00:21:35.600> Tre<00:21:36.600> block<00:21:36.840> tree<00:21:37.080> model<00:21:37.360> is<00:21:37.559> just 00:21:37.710 --> 00:21:37.720 align:start position:0% so uh the Tre block tree model is just 00:21:37.720 --> 00:21:40.390 align:start position:0% so uh the Tre block tree model is just one<00:21:37.840> of<00:21:37.960> the<00:21:38.120> models<00:21:39.080> uh<00:21:39.760> and<00:21:39.919> there<00:21:40.080> was<00:21:40.279> just 00:21:40.390 --> 00:21:40.400 align:start position:0% one of the models uh and there was just 00:21:40.400 --> 00:21:43.669 align:start position:0% one of the models uh and there was just an<00:21:40.640> example<00:21:41.159> so<00:21:41.600> with<00:21:42.200> randomization<00:21:43.200> and<00:21:43.559> uh 00:21:43.669 --> 00:21:43.679 align:start position:0% an example so with randomization and uh 00:21:43.679 --> 00:21:45.950 align:start position:0% an example so with randomization and uh we<00:21:43.840> also<00:21:44.159> have<00:21:44.320> the<00:21:44.559> F<00:21:44.679> ofg<00:21:44.960> checkpoints<00:21:45.480> model 00:21:45.950 --> 00:21:45.960 align:start position:0% we also have the F ofg checkpoints model 00:21:45.960 --> 00:21:49.630 align:start position:0% we also have the F ofg checkpoints model that<00:21:46.320> gives<00:21:46.679> the<00:21:47.400> all<00:21:47.919> all<00:21:48.520> possible<00:21:49.520> uh 00:21:49.630 --> 00:21:49.640 align:start position:0% that gives the all all possible uh 00:21:49.640 --> 00:21:52.269 align:start position:0% that gives the all all possible uh combinations<00:21:50.320> of<00:21:50.600> Justified<00:21:51.559> and<00:21:51.760> finalized 00:21:52.269 --> 00:21:52.279 align:start position:0% combinations of Justified and finalized 00:21:52.279 --> 00:21:54.470 align:start position:0% combinations of Justified and finalized checkpoints<00:21:53.159> given<00:21:53.440> the<00:21:53.520> model<00:21:53.840> input<00:21:54.159> so<00:21:54.360> it 00:21:54.470 --> 00:21:54.480 align:start position:0% checkpoints given the model input so it 00:21:54.480 --> 00:21:55.950 align:start position:0% checkpoints given the model input so it was<00:21:54.600> in<00:21:54.720> the<00:21:54.880> presentation<00:21:55.400> as<00:21:55.520> well<00:21:55.679> so<00:21:55.840> we 00:21:55.950 --> 00:21:55.960 align:start position:0% was in the presentation as well so we 00:21:55.960 --> 00:21:58.110 align:start position:0% was in the presentation as well so we have<00:21:56.080> a<00:21:56.200> model<00:21:56.480> for<00:21:56.720> that<00:21:57.240> it<00:21:57.360> is<00:21:57.640> also<00:21:57.960> this 00:21:58.110 --> 00:21:58.120 align:start position:0% have a model for that it is also this 00:21:58.120 --> 00:21:59.909 align:start position:0% have a model for that it is also this information<00:21:58.960> also<00:21:59.200> used<00:21:59.480> by<00:21:59.600> the<00:21:59.720> test 00:21:59.909 --> 00:21:59.919 align:start position:0% information also used by the test 00:21:59.919 --> 00:22:01.750 align:start position:0% information also used by the test generator<00:22:00.840> all<00:22:01.000> right<00:22:01.279> thank<00:22:01.440> you<00:22:01.559> for 00:22:01.750 --> 00:22:01.760 align:start position:0% generator all right thank you for 00:22:01.760 --> 00:22:03.269 align:start position:0% generator all right thank you for answering<00:22:02.240> that<00:22:02.360> I'm<00:22:02.480> going<00:22:02.559> to<00:22:02.720> mark<00:22:02.919> it<00:22:03.039> as 00:22:03.269 --> 00:22:03.279 align:start position:0% answering that I'm going to mark it as 00:22:03.279 --> 00:22:06.350 align:start position:0% answering that I'm going to mark it as answered<00:22:04.000> last<00:22:04.240> two<00:22:04.679> are<00:22:05.000> attestations<00:22:06.000> only 00:22:06.350 --> 00:22:06.360 align:start position:0% answered last two are attestations only 00:22:06.360 --> 00:22:09.909 align:start position:0% answered last two are attestations only on<00:22:06.679> chain<00:22:07.240> coming<00:22:07.600> from<00:22:07.880> blocks<00:22:08.760> uh<00:22:08.960> no<00:22:09.320> no<00:22:09.760> uh 00:22:09.909 --> 00:22:09.919 align:start position:0% on chain coming from blocks uh no no uh 00:22:09.919 --> 00:22:14.029 align:start position:0% on chain coming from blocks uh no no uh we<00:22:10.120> have<00:22:11.080> both<00:22:11.520> cases<00:22:12.080> so<00:22:12.520> we<00:22:12.679> have<00:22:13.440> uh<00:22:13.720> get<00:22:13.919> a 00:22:14.029 --> 00:22:14.039 align:start position:0% we have both cases so we have uh get a 00:22:14.039 --> 00:22:16.630 align:start position:0% we have both cases so we have uh get a two<00:22:14.200> station<00:22:14.559> from<00:22:14.720> blocks<00:22:15.200> also<00:22:16.200> produce 00:22:16.630 --> 00:22:16.640 align:start position:0% two station from blocks also produce 00:22:16.640 --> 00:22:19.549 align:start position:0% two station from blocks also produce them<00:22:17.240> separately<00:22:18.240> very<00:22:18.600> um<00:22:18.720> I<00:22:18.799> can<00:22:19.080> expand<00:22:19.400> on 00:22:19.549 --> 00:22:19.559 align:start position:0% them separately very um I can expand on 00:22:19.559 --> 00:22:22.190 align:start position:0% them separately very um I can expand on this<00:22:19.720> we<00:22:19.919> have<00:22:20.440> actually<00:22:20.760> have<00:22:21.000> three<00:22:21.720> uh 00:22:22.190 --> 00:22:22.200 align:start position:0% this we have actually have three uh 00:22:22.200 --> 00:22:24.870 align:start position:0% this we have actually have three uh possible<00:22:22.679> cases<00:22:22.960> for<00:22:23.200> this<00:22:23.799> one<00:22:24.000> is<00:22:24.240> that<00:22:24.559> just 00:22:24.870 --> 00:22:24.880 align:start position:0% possible cases for this one is that just 00:22:24.880 --> 00:22:27.510 align:start position:0% possible cases for this one is that just in<00:22:25.520> pure<00:22:25.840> onchain<00:22:26.480> attestation<00:22:27.159> the<00:22:27.320> other 00:22:27.510 --> 00:22:27.520 align:start position:0% in pure onchain attestation the other 00:22:27.520 --> 00:22:30.230 align:start position:0% in pure onchain attestation the other one<00:22:27.720> is<00:22:28.400> uh<00:22:28.720> pure<00:22:29.000> Network<00:22:29.440> attestation<00:22:30.039> that 00:22:30.230 --> 00:22:30.240 align:start position:0% one is uh pure Network attestation that 00:22:30.240 --> 00:22:31.830 align:start position:0% one is uh pure Network attestation that the<00:22:30.360> attestation<00:22:30.919> that<00:22:31.039> is<00:22:31.159> not<00:22:31.360> included<00:22:31.720> in 00:22:31.830 --> 00:22:31.840 align:start position:0% the attestation that is not included in 00:22:31.840 --> 00:22:34.510 align:start position:0% the attestation that is not included in any<00:22:32.039> Block<00:22:32.880> in<00:22:33.039> any<00:22:33.279> block<00:22:33.720> and<00:22:34.039> the<00:22:34.200> third 00:22:34.510 --> 00:22:34.520 align:start position:0% any Block in any block and the third 00:22:34.520 --> 00:22:36.710 align:start position:0% any Block in any block and the third case<00:22:34.799> is<00:22:35.080> both<00:22:35.440> it<00:22:35.559> is<00:22:35.799> in<00:22:35.919> the<00:22:36.039> block<00:22:36.320> it<00:22:36.400> is<00:22:36.559> on 00:22:36.710 --> 00:22:36.720 align:start position:0% case is both it is in the block it is on 00:22:36.720 --> 00:22:38.430 align:start position:0% case is both it is in the block it is on chain<00:22:37.000> and<00:22:37.120> it<00:22:37.200> is<00:22:37.400> coming<00:22:37.679> from<00:22:37.880> the<00:22:38.000> network 00:22:38.430 --> 00:22:38.440 align:start position:0% chain and it is coming from the network 00:22:38.440 --> 00:22:40.870 align:start position:0% chain and it is coming from the network as<00:22:38.559> well<00:22:39.000> and<00:22:39.159> this<00:22:39.279> is<00:22:39.559> all<00:22:40.039> decided<00:22:40.520> by<00:22:40.720> the 00:22:40.870 --> 00:22:40.880 align:start position:0% as well and this is all decided by the 00:22:40.880 --> 00:22:42.669 align:start position:0% as well and this is all decided by the randomization<00:22:41.520> so<00:22:41.679> we<00:22:41.799> flip<00:22:42.039> a<00:22:42.200> coin<00:22:42.520> and 00:22:42.669 --> 00:22:42.679 align:start position:0% randomization so we flip a coin and 00:22:42.679 --> 00:22:45.190 align:start position:0% randomization so we flip a coin and decide<00:22:43.000> which<00:22:43.440> station<00:22:44.080> uh<00:22:44.279> would<00:22:44.720> will<00:22:44.919> be<00:22:45.039> in 00:22:45.190 --> 00:22:45.200 align:start position:0% decide which station uh would will be in 00:22:45.200 --> 00:22:46.870 align:start position:0% decide which station uh would will be in which<00:22:45.400> state<00:22:46.000> all<00:22:46.159> right<00:22:46.400> thank<00:22:46.559> you<00:22:46.679> for 00:22:46.870 --> 00:22:46.880 align:start position:0% which state all right thank you for 00:22:46.880 --> 00:22:48.549 align:start position:0% which state all right thank you for answering<00:22:47.360> that<00:22:47.720> you're<00:22:47.880> looking<00:22:48.120> at<00:22:48.240> me<00:22:48.400> like 00:22:48.549 --> 00:22:48.559 align:start position:0% answering that you're looking at me like 00:22:48.559 --> 00:22:50.549 align:start position:0% answering that you're looking at me like I<00:22:48.960> understand<00:22:49.120> the<00:22:49.240> answer<00:22:49.520> I<00:22:49.640> don't<00:22:50.159> but<00:22:50.360> the 00:22:50.549 --> 00:22:50.559 align:start position:0% I understand the answer I don't but the 00:22:50.559 --> 00:22:52.750 align:start position:0% I understand the answer I don't but the audience<00:22:51.559> I<00:22:51.640> can<00:22:51.760> tell<00:22:51.919> from<00:22:52.080> the<00:22:52.360> audience<00:22:52.640> is 00:22:52.750 --> 00:22:52.760 align:start position:0% audience I can tell from the audience is 00:22:52.760 --> 00:22:54.390 align:start position:0% audience I can tell from the audience is nodding<00:22:53.120> and<00:22:53.240> I'm<00:22:53.400> just<00:22:53.520> nodding<00:22:53.919> along<00:22:54.159> with 00:22:54.390 --> 00:22:54.400 align:start position:0% nodding and I'm just nodding along with 00:22:54.400 --> 00:22:56.750 align:start position:0% nodding and I'm just nodding along with them<00:22:55.080> U<00:22:55.240> okay<00:22:55.400> we<00:22:55.559> got<00:22:55.799> uh<00:22:55.919> one<00:22:56.120> vter<00:22:56.520> okay<00:22:56.640> we 00:22:56.750 --> 00:22:56.760 align:start position:0% them U okay we got uh one vter okay we 00:22:56.760 --> 00:22:58.870 align:start position:0% them U okay we got uh one vter okay we got<00:22:56.919> 51<00:22:57.279> seconds<00:22:57.600> let's<00:22:57.760> do<00:22:57.880> it<00:22:58.200> if<00:22:58.559> the<00:22:58.640> model 00:22:58.870 --> 00:22:58.880 align:start position:0% got 51 seconds let's do it if the model 00:22:58.880 --> 00:23:00.430 align:start position:0% got 51 seconds let's do it if the model is<00:22:59.039> written<00:22:59.360> to<00:22:59.559> test<00:22:59.840> the<00:23:00.000> spec 00:23:00.430 --> 00:23:00.440 align:start position:0% is written to test the spec 00:23:00.440 --> 00:23:02.549 align:start position:0% is written to test the spec implementation<00:23:01.440> how<00:23:01.600> do<00:23:01.760> you<00:23:01.960> guarantee<00:23:02.440> the 00:23:02.549 --> 00:23:02.559 align:start position:0% implementation how do you guarantee the 00:23:02.559 --> 00:23:05.830 align:start position:0% implementation how do you guarantee the model<00:23:03.000> correctness<00:23:04.000> okay<00:23:04.200> the<00:23:04.320> model<00:23:05.120> uh<00:23:05.559> does 00:23:05.830 --> 00:23:05.840 align:start position:0% model correctness okay the model uh does 00:23:05.840 --> 00:23:08.149 align:start position:0% model correctness okay the model uh does not<00:23:06.080> have<00:23:06.240> to<00:23:06.480> be<00:23:06.640> correct<00:23:07.279> because<00:23:07.720> we 00:23:08.149 --> 00:23:08.159 align:start position:0% not have to be correct because we 00:23:08.159 --> 00:23:11.190 align:start position:0% not have to be correct because we execute<00:23:08.840> python<00:23:09.279> specs<00:23:09.760> directly<00:23:10.679> so<00:23:10.880> we<00:23:11.000> use 00:23:11.190 --> 00:23:11.200 align:start position:0% execute python specs directly so we use 00:23:11.200 --> 00:23:13.149 align:start position:0% execute python specs directly so we use it<00:23:11.440> just<00:23:11.600> to<00:23:11.799> produce<00:23:12.159> interest<00:23:12.480> in<00:23:12.720> test 00:23:13.149 --> 00:23:13.159 align:start position:0% it just to produce interest in test 00:23:13.159 --> 00:23:17.070 align:start position:0% it just to produce interest in test vectors<00:23:14.159> and<00:23:15.120> yeah<00:23:15.320> we<00:23:15.440> are<00:23:15.720> using<00:23:16.200> spec<00:23:16.679> code 00:23:17.070 --> 00:23:17.080 align:start position:0% vectors and yeah we are using spec code 00:23:17.080 --> 00:23:19.430 align:start position:0% vectors and yeah we are using spec code to<00:23:17.360> produce<00:23:17.799> the<00:23:18.000> text<00:23:18.279> vectors<00:23:18.840> but<00:23:19.039> finally 00:23:19.430 --> 00:23:19.440 align:start position:0% to produce the text vectors but finally 00:23:19.440 --> 00:23:22.669 align:start position:0% to produce the text vectors but finally we<00:23:19.640> have<00:23:19.799> a<00:23:20.480> special<00:23:21.039> procedure<00:23:21.559> to<00:23:21.760> run<00:23:22.480> the 00:23:22.669 --> 00:23:22.679 align:start position:0% we have a special procedure to run the 00:23:22.679 --> 00:23:24.710 align:start position:0% we have a special procedure to run the generated<00:23:23.320> test 00:23:24.710 --> 00:23:24.720 align:start position:0% generated test 00:23:24.720 --> 00:23:28.669 align:start position:0% generated test using<00:23:25.720> um<00:23:26.520> the<00:23:26.799> python<00:23:27.200> spec<00:23:27.919> and<00:23:28.080> check<00:23:28.320> the 00:23:28.669 --> 00:23:28.679 align:start position:0% using um the python spec and check the 00:23:28.679 --> 00:23:30.950 align:start position:0% using um the python spec and check the everything<00:23:28.960> is<00:23:29.320> okay<00:23:30.320> very<00:23:30.520> good<00:23:30.679> and<00:23:30.840> I 00:23:30.950 --> 00:23:30.960 align:start position:0% everything is okay very good and I 00:23:30.960 --> 00:23:32.470 align:start position:0% everything is okay very good and I believe<00:23:31.240> I<00:23:31.320> can<00:23:31.520> help<00:23:31.679> you<00:23:31.840> answer<00:23:32.159> do<00:23:32.279> you 00:23:32.470 --> 00:23:32.480 align:start position:0% believe I can help you answer do you 00:23:32.480 --> 00:23:35.310 align:start position:0% believe I can help you answer do you execute<00:23:32.880> the<00:23:33.039> python<00:23:33.400> spec<00:23:33.679> directly<00:23:34.559> yes<00:23:34.799> you 00:23:35.310 --> 00:23:35.320 align:start position:0% execute the python spec directly yes you 00:23:35.320 --> 00:23:37.630 align:start position:0% execute the python spec directly yes you do<00:23:36.320> ladies<00:23:36.679> and<00:23:36.799> Gentlemen<00:23:37.159> let's<00:23:37.360> give<00:23:37.480> our 00:23:37.630 --> 00:23:37.640 align:start position:0% do ladies and Gentlemen let's give our 00:23:37.640 --> 00:23:39.230 align:start position:0% do ladies and Gentlemen let's give our two<00:23:37.840> speakers<00:23:38.159> a<00:23:38.360> wonderful<00:23:38.840> Round<00:23:39.080> of 00:23:39.230 --> 00:23:39.240 align:start position:0% two speakers a wonderful Round of 00:23:39.240 --> 00:23:42.310 align:start position:0% two speakers a wonderful Round of Applause<00:23:39.880> to<00:23:40.039> Alex<00:23:40.360> and<00:23:40.760> mik<00:23:41.760> thank<00:23:42.039> thank<00:23:42.200> you 00:23:42.310 --> 00:23:42.320 align:start position:0% Applause to Alex and mik thank thank you 00:23:42.320 --> 00:23:46.320 align:start position:0% Applause to Alex and mik thank thank you gentlemen<00:23:42.799> thank<00:23:42.919> you<00:23:43.159> thank<00:23:43.320> you<00:23:43.480> very<00:23:43.679> much