WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:15.310 align:start position:0% [Music] 00:00:15.310 --> 00:00:15.320 align:start position:0% 00:00:15.320 --> 00:00:18.109 align:start position:0% about<00:00:16.320> the<00:00:16.800> quests<00:00:17.160> for<00:00:17.279> the<00:00:17.460> best<00:00:17.640> tests 00:00:18.109 --> 00:00:18.119 align:start position:0% about the quests for the best tests 00:00:18.119 --> 00:00:20.150 align:start position:0% about the quests for the best tests today<00:00:18.260> we're<00:00:19.260> going<00:00:19.500> to<00:00:19.560> look<00:00:19.619> at<00:00:19.800> all<00:00:20.039> the 00:00:20.150 --> 00:00:20.160 align:start position:0% today we're going to look at all the 00:00:20.160 --> 00:00:22.370 align:start position:0% today we're going to look at all the different<00:00:20.279> testing<00:00:20.760> tools<00:00:21.060> that<00:00:21.240> we<00:00:21.420> used<00:00:21.600> and 00:00:22.370 --> 00:00:22.380 align:start position:0% different testing tools that we used and 00:00:22.380 --> 00:00:24.230 align:start position:0% different testing tools that we used and I'm<00:00:22.740> going<00:00:22.859> to<00:00:23.039> be<00:00:23.100> talking<00:00:23.279> about<00:00:23.520> the<00:00:23.760> bugs 00:00:24.230 --> 00:00:24.240 align:start position:0% I'm going to be talking about the bugs 00:00:24.240 --> 00:00:26.870 align:start position:0% I'm going to be talking about the bugs that<00:00:24.600> we<00:00:24.840> didn't<00:00:25.080> find<00:00:25.320> on<00:00:25.560> mainnet<00:00:26.100> if<00:00:26.760> you 00:00:26.870 --> 00:00:26.880 align:start position:0% that we didn't find on mainnet if you 00:00:26.880 --> 00:00:29.330 align:start position:0% that we didn't find on mainnet if you were<00:00:27.060> here<00:00:27.240> for<00:00:27.480> two<00:00:27.720> talks<00:00:28.380> before<00:00:28.980> mine 00:00:29.330 --> 00:00:29.340 align:start position:0% were here for two talks before mine 00:00:29.340 --> 00:00:31.669 align:start position:0% were here for two talks before mine Mario<00:00:30.119> spoke<00:00:30.599> about<00:00:30.720> the<00:00:30.900> bugs<00:00:31.199> that<00:00:31.380> we<00:00:31.500> did 00:00:31.669 --> 00:00:31.679 align:start position:0% Mario spoke about the bugs that we did 00:00:31.679 --> 00:00:35.090 align:start position:0% Mario spoke about the bugs that we did find<00:00:31.859> so<00:00:32.279> I'm<00:00:32.399> gonna<00:00:32.520> do<00:00:32.759> the<00:00:32.940> contract 00:00:35.090 --> 00:00:35.100 align:start position:0% find so I'm gonna do the contract 00:00:35.100 --> 00:00:37.490 align:start position:0% find so I'm gonna do the contract um the<00:00:35.399> first<00:00:35.579> part<00:00:35.820> let's<00:00:36.360> talk<00:00:36.600> about<00:00:36.780> what 00:00:37.490 --> 00:00:37.500 align:start position:0% um the first part let's talk about what 00:00:37.500 --> 00:00:40.910 align:start position:0% um the first part let's talk about what we're<00:00:37.920> actually<00:00:38.399> doing<00:00:39.180> with<00:00:39.540> testing<00:00:39.960> why<00:00:40.680> is 00:00:40.910 --> 00:00:40.920 align:start position:0% we're actually doing with testing why is 00:00:40.920 --> 00:00:43.630 align:start position:0% we're actually doing with testing why is the<00:00:41.100> merge<00:00:41.399> complicated<00:00:41.879> to<00:00:42.180> begin<00:00:42.300> with<00:00:42.600> well 00:00:43.630 --> 00:00:43.640 align:start position:0% the merge complicated to begin with well 00:00:43.640 --> 00:00:46.130 align:start position:0% the merge complicated to begin with well we<00:00:44.640> have<00:00:44.760> roughly<00:00:45.300> 20<00:00:45.600> different<00:00:45.840> client 00:00:46.130 --> 00:00:46.140 align:start position:0% we have roughly 20 different client 00:00:46.140 --> 00:00:48.410 align:start position:0% we have roughly 20 different client combinations<00:00:46.800> and<00:00:47.340> regressions<00:00:47.879> sneak<00:00:48.239> in 00:00:48.410 --> 00:00:48.420 align:start position:0% combinations and regressions sneak in 00:00:48.420 --> 00:00:50.869 align:start position:0% combinations and regressions sneak in very<00:00:48.840> easily<00:00:49.320> you<00:00:49.980> might<00:00:50.100> see<00:00:50.340> a<00:00:50.460> regression 00:00:50.869 --> 00:00:50.879 align:start position:0% very easily you might see a regression 00:00:50.879 --> 00:00:52.490 align:start position:0% very easily you might see a regression in<00:00:51.059> one<00:00:51.300> of<00:00:51.360> the<00:00:51.480> client<00:00:51.780> combinations<00:00:52.200> but 00:00:52.490 --> 00:00:52.500 align:start position:0% in one of the client combinations but 00:00:52.500 --> 00:00:54.290 align:start position:0% in one of the client combinations but none<00:00:52.680> of<00:00:52.860> the<00:00:52.980> other<00:00:53.100> ones<00:00:53.399> and<00:00:53.760> that's<00:00:54.000> very 00:00:54.290 --> 00:00:54.300 align:start position:0% none of the other ones and that's very 00:00:54.300 --> 00:00:55.970 align:start position:0% none of the other ones and that's very tricky<00:00:54.660> to<00:00:54.780> pinpoint 00:00:55.970 --> 00:00:55.980 align:start position:0% tricky to pinpoint 00:00:55.980 --> 00:00:58.549 align:start position:0% tricky to pinpoint the<00:00:56.879> specs<00:00:57.239> for<00:00:57.360> an<00:00:57.539> active<00:00:57.960> development 00:00:58.549 --> 00:00:58.559 align:start position:0% the specs for an active development 00:00:58.559 --> 00:01:00.650 align:start position:0% the specs for an active development there<00:00:59.160> were<00:00:59.280> quite<00:00:59.460> a<00:00:59.579> few<00:00:59.699> of<00:00:59.879> the<00:01:00.120> early<00:01:00.300> test 00:01:00.650 --> 00:01:00.660 align:start position:0% there were quite a few of the early test 00:01:00.660 --> 00:01:03.290 align:start position:0% there were quite a few of the early test Nets<00:01:01.140> where<00:01:01.440> we<00:01:01.980> kind<00:01:02.460> of<00:01:02.579> didn't<00:01:02.760> pin<00:01:03.180> the 00:01:03.290 --> 00:01:03.300 align:start position:0% Nets where we kind of didn't pin the 00:01:03.300 --> 00:01:06.170 align:start position:0% Nets where we kind of didn't pin the spec<00:01:03.480> version<00:01:03.780> so<00:01:04.680> someone<00:01:04.860> was<00:01:05.180> implementing 00:01:06.170 --> 00:01:06.180 align:start position:0% spec version so someone was implementing 00:01:06.180 --> 00:01:07.910 align:start position:0% spec version so someone was implementing something<00:01:06.360> on<00:01:06.600> a<00:01:06.720> different<00:01:06.840> commit<00:01:07.260> so<00:01:07.619> of 00:01:07.910 --> 00:01:07.920 align:start position:0% something on a different commit so of 00:01:07.920 --> 00:01:10.070 align:start position:0% something on a different commit so of course<00:01:08.040> the<00:01:08.280> test<00:01:08.400> net<00:01:08.640> broke<00:01:09.000> so<00:01:09.420> we<00:01:09.659> had<00:01:09.840> to 00:01:10.070 --> 00:01:10.080 align:start position:0% course the test net broke so we had to 00:01:10.080 --> 00:01:12.370 align:start position:0% course the test net broke so we had to actually<00:01:10.500> figure<00:01:10.860> out<00:01:11.159> how<00:01:11.580> to<00:01:11.760> treat 00:01:12.370 --> 00:01:12.380 align:start position:0% actually figure out how to treat 00:01:12.380 --> 00:01:15.170 align:start position:0% actually figure out how to treat modifying<00:01:13.380> specs<00:01:13.920> along<00:01:14.280> with<00:01:14.640> modifying 00:01:15.170 --> 00:01:15.180 align:start position:0% modifying specs along with modifying 00:01:15.180 --> 00:01:17.750 align:start position:0% modifying specs along with modifying test<00:01:15.360> Nets<00:01:15.780> along<00:01:16.439> with<00:01:16.740> 20<00:01:17.100> different 00:01:17.750 --> 00:01:17.760 align:start position:0% test Nets along with 20 different 00:01:17.760 --> 00:01:19.850 align:start position:0% test Nets along with 20 different combinations<00:01:18.479> all<00:01:19.020> changing<00:01:19.439> at<00:01:19.619> the<00:01:19.740> same 00:01:19.850 --> 00:01:19.860 align:start position:0% combinations all changing at the same 00:01:19.860 --> 00:01:21.649 align:start position:0% combinations all changing at the same time 00:01:21.649 --> 00:01:21.659 align:start position:0% time 00:01:21.659 --> 00:01:23.749 align:start position:0% time um communicating<00:01:22.320> and<00:01:22.560> debugging<00:01:23.159> it's 00:01:23.749 --> 00:01:23.759 align:start position:0% um communicating and debugging it's 00:01:23.759 --> 00:01:25.070 align:start position:0% um communicating and debugging it's great<00:01:24.000> that<00:01:24.180> we<00:01:24.299> have<00:01:24.420> a<00:01:24.540> decentralized 00:01:25.070 --> 00:01:25.080 align:start position:0% great that we have a decentralized 00:01:25.080 --> 00:01:26.990 align:start position:0% great that we have a decentralized environment<00:01:25.560> it's<00:01:26.220> horrible<00:01:26.520> if<00:01:26.700> I<00:01:26.820> have<00:01:26.820> to 00:01:26.990 --> 00:01:27.000 align:start position:0% environment it's horrible if I have to 00:01:27.000 --> 00:01:28.609 align:start position:0% environment it's horrible if I have to wait<00:01:27.119> for<00:01:27.299> the<00:01:27.479> Australians<00:01:27.960> to<00:01:28.080> wake<00:01:28.200> up<00:01:28.380> for 00:01:28.609 --> 00:01:28.619 align:start position:0% wait for the Australians to wake up for 00:01:28.619 --> 00:01:30.109 align:start position:0% wait for the Australians to wake up for anything 00:01:30.109 --> 00:01:30.119 align:start position:0% anything 00:01:30.119 --> 00:01:32.330 align:start position:0% anything um<00:01:30.180> it<00:01:31.140> does<00:01:31.320> take<00:01:31.500> quite<00:01:31.680> a<00:01:31.860> bit<00:01:31.920> of<00:01:32.040> effort 00:01:32.330 --> 00:01:32.340 align:start position:0% um it does take quite a bit of effort 00:01:32.340 --> 00:01:34.070 align:start position:0% um it does take quite a bit of effort and<00:01:32.640> quite<00:01:32.759> a<00:01:32.939> bit<00:01:33.000> of<00:01:33.119> planning<00:01:33.420> on<00:01:33.659> our<00:01:33.840> side 00:01:34.070 --> 00:01:34.080 align:start position:0% and quite a bit of planning on our side 00:01:34.080 --> 00:01:36.170 align:start position:0% and quite a bit of planning on our side we<00:01:34.500> had<00:01:34.680> to<00:01:34.860> kind<00:01:34.979> of<00:01:35.100> schedule<00:01:35.280> around<00:01:35.759> people 00:01:36.170 --> 00:01:36.180 align:start position:0% we had to kind of schedule around people 00:01:36.180 --> 00:01:38.569 align:start position:0% we had to kind of schedule around people picking<00:01:36.720> up<00:01:36.900> their<00:01:37.140> kids<00:01:37.320> from<00:01:37.619> school<00:01:37.860> where 00:01:38.569 --> 00:01:38.579 align:start position:0% picking up their kids from school where 00:01:38.579 --> 00:01:40.730 align:start position:0% picking up their kids from school where to<00:01:38.820> schedule<00:01:39.000> around<00:01:39.479> people<00:01:39.900> waking<00:01:40.259> up<00:01:40.500> in 00:01:40.730 --> 00:01:40.740 align:start position:0% to schedule around people waking up in 00:01:40.740 --> 00:01:42.469 align:start position:0% to schedule around people waking up in Australia<00:01:41.340> we<00:01:41.640> have<00:01:41.820> to<00:01:41.939> schedule<00:01:42.060> around 00:01:42.469 --> 00:01:42.479 align:start position:0% Australia we have to schedule around 00:01:42.479 --> 00:01:44.630 align:start position:0% Australia we have to schedule around Americans<00:01:43.140> a<00:01:43.320> lot<00:01:43.439> of<00:01:43.619> different<00:01:43.740> things 00:01:44.630 --> 00:01:44.640 align:start position:0% Americans a lot of different things 00:01:44.640 --> 00:01:46.730 align:start position:0% Americans a lot of different things and<00:01:45.180> figuring<00:01:45.659> out<00:01:45.780> how<00:01:45.960> to<00:01:46.140> do<00:01:46.320> all<00:01:46.500> of<00:01:46.619> this 00:01:46.730 --> 00:01:46.740 align:start position:0% and figuring out how to do all of this 00:01:46.740 --> 00:01:48.590 align:start position:0% and figuring out how to do all of this in<00:01:46.979> a<00:01:47.100> reliable<00:01:47.400> Manner<00:01:47.820> and<00:01:47.939> on<00:01:48.119> a<00:01:48.240> timeline 00:01:48.590 --> 00:01:48.600 align:start position:0% in a reliable Manner and on a timeline 00:01:48.600 --> 00:01:50.870 align:start position:0% in a reliable Manner and on a timeline was<00:01:49.020> crazy 00:01:50.870 --> 00:01:50.880 align:start position:0% was crazy 00:01:50.880 --> 00:01:54.050 align:start position:0% was crazy um<00:01:51.000> the<00:01:51.360> last<00:01:51.540> one<00:01:51.780> was<00:01:52.500> debug<00:01:53.100> knowledge<00:01:53.579> we 00:01:54.050 --> 00:01:54.060 align:start position:0% um the last one was debug knowledge we 00:01:54.060 --> 00:01:55.550 align:start position:0% um the last one was debug knowledge we were<00:01:54.240> really<00:01:54.479> surprised<00:01:54.899> the<00:01:55.200> type<00:01:55.380> of 00:01:55.550 --> 00:01:55.560 align:start position:0% were really surprised the type of 00:01:55.560 --> 00:01:57.289 align:start position:0% were really surprised the type of debugging<00:01:56.040> you<00:01:56.220> need<00:01:56.340> to<00:01:56.460> do<00:01:56.520> for<00:01:56.700> CLS<00:01:57.180> and 00:01:57.289 --> 00:01:57.299 align:start position:0% debugging you need to do for CLS and 00:01:57.299 --> 00:01:58.969 align:start position:0% debugging you need to do for CLS and years<00:01:57.420> are<00:01:57.840> totally<00:01:58.140> different<00:01:58.320> we<00:01:58.740> had<00:01:58.860> to 00:01:58.969 --> 00:01:58.979 align:start position:0% years are totally different we had to 00:01:58.979 --> 00:02:00.649 align:start position:0% years are totally different we had to see<00:01:59.100> how<00:01:59.340> to<00:01:59.520> bring<00:01:59.640> all<00:01:59.939> of<00:02:00.060> that<00:02:00.180> competence 00:02:00.649 --> 00:02:00.659 align:start position:0% see how to bring all of that competence 00:02:00.659 --> 00:02:01.850 align:start position:0% see how to bring all of that competence in<00:02:00.899> one<00:02:01.020> place 00:02:01.850 --> 00:02:01.860 align:start position:0% in one place 00:02:01.860 --> 00:02:04.010 align:start position:0% in one place and<00:02:02.759> how<00:02:03.000> to<00:02:03.180> actually<00:02:03.360> figure<00:02:03.600> out<00:02:03.780> when 00:02:04.010 --> 00:02:04.020 align:start position:0% and how to actually figure out when 00:02:04.020 --> 00:02:05.630 align:start position:0% and how to actually figure out when something<00:02:04.200> goes<00:02:04.560> wrong<00:02:04.680> and<00:02:05.040> they<00:02:05.219> did<00:02:05.399> go 00:02:05.630 --> 00:02:05.640 align:start position:0% something goes wrong and they did go 00:02:05.640 --> 00:02:08.210 align:start position:0% something goes wrong and they did go wrong<00:02:05.880> a<00:02:06.299> lot<00:02:06.420> in<00:02:06.600> the<00:02:06.719> beginning 00:02:08.210 --> 00:02:08.220 align:start position:0% wrong a lot in the beginning 00:02:08.220 --> 00:02:10.130 align:start position:0% wrong a lot in the beginning um<00:02:08.340> and<00:02:09.000> the<00:02:09.119> nice<00:02:09.239> part<00:02:09.479> is<00:02:09.660> if<00:02:09.899> you<00:02:10.020> figure 00:02:10.130 --> 00:02:10.140 align:start position:0% um and the nice part is if you figure 00:02:10.140 --> 00:02:12.110 align:start position:0% um and the nice part is if you figure this<00:02:10.380> out<00:02:10.560> once<00:02:10.979> we<00:02:11.280> figure<00:02:11.459> it<00:02:11.760> out<00:02:11.879> for 00:02:12.110 --> 00:02:12.120 align:start position:0% this out once we figure it out for 00:02:12.120 --> 00:02:14.449 align:start position:0% this out once we figure it out for future<00:02:12.420> test<00:02:12.720> Nets<00:02:13.140> so<00:02:13.500> happy<00:02:13.980> that<00:02:14.280> that 00:02:14.449 --> 00:02:14.459 align:start position:0% future test Nets so happy that that 00:02:14.459 --> 00:02:15.949 align:start position:0% future test Nets so happy that that worked<00:02:14.819> out 00:02:15.949 --> 00:02:15.959 align:start position:0% worked out 00:02:15.959 --> 00:02:19.250 align:start position:0% worked out what<00:02:16.440> could<00:02:16.620> possibly<00:02:16.980> go<00:02:17.220> wrong<00:02:17.599> so<00:02:18.599> the 00:02:19.250 --> 00:02:19.260 align:start position:0% what could possibly go wrong so the 00:02:19.260 --> 00:02:21.589 align:start position:0% what could possibly go wrong so the merge<00:02:19.620> has<00:02:19.800> two<00:02:20.040> parts<00:02:20.280> the<00:02:20.760> consensus<00:02:21.300> layer 00:02:21.589 --> 00:02:21.599 align:start position:0% merge has two parts the consensus layer 00:02:21.599 --> 00:02:23.510 align:start position:0% merge has two parts the consensus layer and<00:02:21.780> the<00:02:21.900> execution<00:02:22.319> layer<00:02:22.680> and<00:02:23.340> they 00:02:23.510 --> 00:02:23.520 align:start position:0% and the execution layer and they 00:02:23.520 --> 00:02:24.949 align:start position:0% and the execution layer and they communicate<00:02:24.000> via<00:02:24.300> this<00:02:24.480> thing<00:02:24.660> called<00:02:24.780> the 00:02:24.949 --> 00:02:24.959 align:start position:0% communicate via this thing called the 00:02:24.959 --> 00:02:26.210 align:start position:0% communicate via this thing called the engine<00:02:25.140> API 00:02:26.210 --> 00:02:26.220 align:start position:0% engine API 00:02:26.220 --> 00:02:28.430 align:start position:0% engine API so<00:02:26.760> if<00:02:27.060> you<00:02:27.180> mess<00:02:27.360> up<00:02:27.480> the<00:02:27.660> consensus<00:02:28.080> layer 00:02:28.430 --> 00:02:28.440 align:start position:0% so if you mess up the consensus layer 00:02:28.440 --> 00:02:30.710 align:start position:0% so if you mess up the consensus layer you're<00:02:28.739> going<00:02:28.860> to<00:02:28.980> have<00:02:29.160> a<00:02:29.520> network<00:02:30.360> that 00:02:30.710 --> 00:02:30.720 align:start position:0% you're going to have a network that 00:02:30.720 --> 00:02:32.690 align:start position:0% you're going to have a network that can't<00:02:30.900> agree<00:02:31.200> on<00:02:31.379> anything<00:02:31.560> if<00:02:32.280> you<00:02:32.400> mess<00:02:32.580> up 00:02:32.690 --> 00:02:32.700 align:start position:0% can't agree on anything if you mess up 00:02:32.700 --> 00:02:34.610 align:start position:0% can't agree on anything if you mess up the<00:02:32.879> execution<00:02:33.300> layer<00:02:33.720> you<00:02:34.140> have<00:02:34.319> a<00:02:34.500> network 00:02:34.610 --> 00:02:34.620 align:start position:0% the execution layer you have a network 00:02:34.620 --> 00:02:36.770 align:start position:0% the execution layer you have a network that<00:02:34.980> can't<00:02:35.160> do<00:02:35.459> anything<00:02:35.640> so<00:02:36.360> those<00:02:36.540> are<00:02:36.660> the 00:02:36.770 --> 00:02:36.780 align:start position:0% that can't do anything so those are the 00:02:36.780 --> 00:02:38.510 align:start position:0% that can't do anything so those are the two<00:02:36.959> high<00:02:37.200> level<00:02:37.379> problems<00:02:37.980> that<00:02:38.160> we're<00:02:38.280> in 00:02:38.510 --> 00:02:38.520 align:start position:0% two high level problems that we're in 00:02:38.520 --> 00:02:41.150 align:start position:0% two high level problems that we're in trying<00:02:38.700> to<00:02:38.879> ensure<00:02:39.120> that<00:02:39.360> never<00:02:39.599> happen 00:02:41.150 --> 00:02:41.160 align:start position:0% trying to ensure that never happen 00:02:41.160 --> 00:02:42.710 align:start position:0% trying to ensure that never happen um just<00:02:41.459> to<00:02:41.580> enumerate<00:02:42.060> a<00:02:42.239> bit<00:02:42.360> from<00:02:42.540> the 00:02:42.710 --> 00:02:42.720 align:start position:0% um just to enumerate a bit from the 00:02:42.720 --> 00:02:44.630 align:start position:0% um just to enumerate a bit from the regular<00:02:43.019> testing<00:02:43.440> world<00:02:43.560> what<00:02:43.980> sort<00:02:44.160> of<00:02:44.280> tests 00:02:44.630 --> 00:02:44.640 align:start position:0% regular testing world what sort of tests 00:02:44.640 --> 00:02:48.110 align:start position:0% regular testing world what sort of tests even<00:02:44.819> exist<00:02:45.300> so<00:02:45.959> we<00:02:46.379> have<00:02:46.500> unit<00:02:46.739> tests<00:02:47.340> and<00:02:47.879> it 00:02:48.110 --> 00:02:48.120 align:start position:0% even exist so we have unit tests and it 00:02:48.120 --> 00:02:50.630 align:start position:0% even exist so we have unit tests and it is<00:02:48.360> in<00:02:48.599> our<00:02:48.739> decentralized<00:02:49.739> uh<00:02:50.220> world<00:02:50.400> with 00:02:50.630 --> 00:02:50.640 align:start position:0% is in our decentralized uh world with 00:02:50.640 --> 00:02:52.250 align:start position:0% is in our decentralized uh world with all<00:02:50.760> the<00:02:50.879> client<00:02:51.120> teams<00:02:51.420> the<00:02:51.720> client<00:02:51.900> teams 00:02:52.250 --> 00:02:52.260 align:start position:0% all the client teams the client teams 00:02:52.260 --> 00:02:53.509 align:start position:0% all the client teams the client teams take<00:02:52.379> care<00:02:52.500> of<00:02:52.560> this<00:02:52.739> themselves<00:02:53.099> we<00:02:53.400> don't 00:02:53.509 --> 00:02:53.519 align:start position:0% take care of this themselves we don't 00:02:53.519 --> 00:02:55.250 align:start position:0% take care of this themselves we don't have<00:02:53.640> to<00:02:53.760> do<00:02:53.879> anything<00:02:54.060> no<00:02:54.540> coordination<00:02:55.019> work 00:02:55.250 --> 00:02:55.260 align:start position:0% have to do anything no coordination work 00:02:55.260 --> 00:02:57.650 align:start position:0% have to do anything no coordination work from<00:02:55.440> our<00:02:55.620> side<00:02:55.819> uh<00:02:56.819> this<00:02:57.060> makes<00:02:57.239> sure<00:02:57.480> that 00:02:57.650 --> 00:02:57.660 align:start position:0% from our side uh this makes sure that 00:02:57.660 --> 00:02:58.970 align:start position:0% from our side uh this makes sure that there's<00:02:57.840> no<00:02:57.959> regression<00:02:58.440> but<00:02:58.680> these<00:02:58.860> are 00:02:58.970 --> 00:02:58.980 align:start position:0% there's no regression but these are 00:02:58.980 --> 00:03:00.350 align:start position:0% there's no regression but these are localized<00:02:59.400> regressions<00:02:59.940> something<00:03:00.120> that 00:03:00.350 --> 00:03:00.360 align:start position:0% localized regressions something that 00:03:00.360 --> 00:03:01.610 align:start position:0% localized regressions something that they<00:03:00.480> might<00:03:00.660> have<00:03:00.780> seen<00:03:00.959> on<00:03:01.200> their<00:03:01.319> client 00:03:01.610 --> 00:03:01.620 align:start position:0% they might have seen on their client 00:03:01.620 --> 00:03:03.770 align:start position:0% they might have seen on their client based<00:03:02.040> on<00:03:02.099> how<00:03:02.280> they've<00:03:02.580> built<00:03:02.819> their<00:03:02.940> client 00:03:03.770 --> 00:03:03.780 align:start position:0% based on how they've built their client 00:03:03.780 --> 00:03:06.350 align:start position:0% based on how they've built their client we<00:03:04.560> have<00:03:04.680> integration<00:03:05.160> tests<00:03:05.700> part<00:03:06.060> of<00:03:06.239> them 00:03:06.350 --> 00:03:06.360 align:start position:0% we have integration tests part of them 00:03:06.360 --> 00:03:08.449 align:start position:0% we have integration tests part of them are<00:03:06.780> done<00:03:07.019> by<00:03:07.140> client<00:03:07.440> teams<00:03:07.800> so<00:03:07.980> for<00:03:08.220> example 00:03:08.449 --> 00:03:08.459 align:start position:0% are done by client teams so for example 00:03:08.459 --> 00:03:10.430 align:start position:0% are done by client teams so for example the<00:03:08.760> Nimbus<00:03:09.060> team<00:03:09.180> spins<00:03:09.540> up<00:03:09.660> a<00:03:09.840> local<00:03:09.959> Nimbus 00:03:10.430 --> 00:03:10.440 align:start position:0% the Nimbus team spins up a local Nimbus 00:03:10.440 --> 00:03:13.070 align:start position:0% the Nimbus team spins up a local Nimbus Network<00:03:10.680> to<00:03:11.099> make<00:03:11.220> sure<00:03:11.400> that<00:03:12.180> their<00:03:12.780> stuff 00:03:13.070 --> 00:03:13.080 align:start position:0% Network to make sure that their stuff 00:03:13.080 --> 00:03:15.490 align:start position:0% Network to make sure that their stuff can<00:03:13.319> always<00:03:13.500> talk<00:03:13.800> to<00:03:13.980> each<00:03:14.159> other 00:03:15.490 --> 00:03:15.500 align:start position:0% can always talk to each other 00:03:15.500 --> 00:03:17.930 align:start position:0% can always talk to each other then<00:03:16.500> on<00:03:16.800> a<00:03:16.920> high<00:03:17.040> level<00:03:17.220> we<00:03:17.580> do<00:03:17.700> some 00:03:17.930 --> 00:03:17.940 align:start position:0% then on a high level we do some 00:03:17.940 --> 00:03:19.550 align:start position:0% then on a high level we do some interrupt<00:03:18.480> tests<00:03:18.840> so<00:03:19.019> these<00:03:19.319> might<00:03:19.440> be 00:03:19.550 --> 00:03:19.560 align:start position:0% interrupt tests so these might be 00:03:19.560 --> 00:03:21.949 align:start position:0% interrupt tests so these might be devnets<00:03:20.040> or<00:03:20.220> whatever<00:03:20.340> they<00:03:20.640> are 00:03:21.949 --> 00:03:21.959 align:start position:0% devnets or whatever they are 00:03:21.959 --> 00:03:24.410 align:start position:0% devnets or whatever they are then<00:03:22.379> we<00:03:22.620> have<00:03:22.739> system<00:03:22.980> tests<00:03:23.640> and<00:03:24.060> this<00:03:24.239> is 00:03:24.410 --> 00:03:24.420 align:start position:0% then we have system tests and this is 00:03:24.420 --> 00:03:27.710 align:start position:0% then we have system tests and this is where<00:03:25.379> external<00:03:26.220> coordinators<00:03:26.940> come<00:03:27.180> in<00:03:27.360> so 00:03:27.710 --> 00:03:27.720 align:start position:0% where external coordinators come in so 00:03:27.720 --> 00:03:29.930 align:start position:0% where external coordinators come in so I'm<00:03:27.959> going<00:03:28.140> to<00:03:28.200> say<00:03:28.319> the<00:03:28.560> EF<00:03:28.920> was<00:03:29.159> part<00:03:29.580> of<00:03:29.760> the 00:03:29.930 --> 00:03:29.940 align:start position:0% I'm going to say the EF was part of the 00:03:29.940 --> 00:03:31.910 align:start position:0% I'm going to say the EF was part of the external<00:03:30.360> coordinator<00:03:30.840> for<00:03:31.260> the<00:03:31.560> testing 00:03:31.910 --> 00:03:31.920 align:start position:0% external coordinator for the testing 00:03:31.920 --> 00:03:34.009 align:start position:0% external coordinator for the testing efforts<00:03:32.340> so<00:03:33.000> these<00:03:33.239> tests<00:03:33.540> end-to-end 00:03:34.009 --> 00:03:34.019 align:start position:0% efforts so these tests end-to-end 00:03:34.019 --> 00:03:36.050 align:start position:0% efforts so these tests end-to-end functionality<00:03:34.560> we<00:03:34.920> spin<00:03:35.159> up<00:03:35.280> a<00:03:35.459> test<00:03:35.580> net<00:03:35.760> we 00:03:36.050 --> 00:03:36.060 align:start position:0% functionality we spin up a test net we 00:03:36.060 --> 00:03:39.649 align:start position:0% functionality we spin up a test net we run<00:03:36.239> transactions<00:03:37.080> we<00:03:38.000> withdraw<00:03:39.000> we<00:03:39.300> set<00:03:39.480> up 00:03:39.649 --> 00:03:39.659 align:start position:0% run transactions we withdraw we set up 00:03:39.659 --> 00:03:42.470 align:start position:0% run transactions we withdraw we set up faucets<00:03:40.140> we<00:03:40.680> look<00:03:40.920> at<00:03:41.040> explorers<00:03:41.819> work<00:03:42.060> and<00:03:42.299> so 00:03:42.470 --> 00:03:42.480 align:start position:0% faucets we look at explorers work and so 00:03:42.480 --> 00:03:43.190 align:start position:0% faucets we look at explorers work and so on 00:03:43.190 --> 00:03:43.200 align:start position:0% on 00:03:43.200 --> 00:03:45.589 align:start position:0% on and<00:03:43.680> then<00:03:43.799> we<00:03:43.980> have<00:03:44.159> production<00:03:44.640> tests<00:03:45.180> this 00:03:45.589 --> 00:03:45.599 align:start position:0% and then we have production tests this 00:03:45.599 --> 00:03:46.850 align:start position:0% and then we have production tests this is<00:03:45.720> something<00:03:45.900> you<00:03:46.200> guys<00:03:46.319> might<00:03:46.500> have<00:03:46.680> seen 00:03:46.850 --> 00:03:46.860 align:start position:0% is something you guys might have seen 00:03:46.860 --> 00:03:50.390 align:start position:0% is something you guys might have seen with<00:03:47.220> shadowfox<00:03:47.819> so<00:03:48.360> production<00:03:49.099> tests<00:03:50.099> sort 00:03:50.390 --> 00:03:50.400 align:start position:0% with shadowfox so production tests sort 00:03:50.400 --> 00:03:53.330 align:start position:0% with shadowfox so production tests sort of<00:03:50.519> work<00:03:50.760> on<00:03:51.060> a<00:03:51.180> prod<00:03:51.360> like<00:03:51.780> environment<00:03:52.379> and 00:03:53.330 --> 00:03:53.340 align:start position:0% of work on a prod like environment and 00:03:53.340 --> 00:03:55.009 align:start position:0% of work on a prod like environment and I'll<00:03:53.519> go<00:03:53.700> into<00:03:53.819> what<00:03:54.060> shadow<00:03:54.239> Fox<00:03:54.480> are<00:03:54.780> later 00:03:55.009 --> 00:03:55.019 align:start position:0% I'll go into what shadow Fox are later 00:03:55.019 --> 00:03:57.470 align:start position:0% I'll go into what shadow Fox are later on<00:03:55.200> but<00:03:55.500> on<00:03:55.799> a<00:03:55.980> high<00:03:56.040> level<00:03:56.280> we<00:03:56.879> inherit<00:03:57.299> all 00:03:57.470 --> 00:03:57.480 align:start position:0% on but on a high level we inherit all 00:03:57.480 --> 00:04:00.289 align:start position:0% on but on a high level we inherit all the<00:03:57.659> complexity<00:03:58.019> of<00:03:58.200> mainnet<00:03:59.159> and<00:03:59.760> this<00:04:00.000> also 00:04:00.289 --> 00:04:00.299 align:start position:0% the complexity of mainnet and this also 00:04:00.299 --> 00:04:02.089 align:start position:0% the complexity of mainnet and this also includes<00:04:00.659> public<00:04:00.840> test<00:04:01.140> Nets<00:04:01.560> so<00:04:01.680> if<00:04:01.860> you<00:04:01.980> guys 00:04:02.089 --> 00:04:02.099 align:start position:0% includes public test Nets so if you guys 00:04:02.099 --> 00:04:04.490 align:start position:0% includes public test Nets so if you guys remember<00:04:02.340> Kiln<00:04:03.000> or<00:04:03.180> kinsuki<00:04:03.840> that<00:04:04.379> falls 00:04:04.490 --> 00:04:04.500 align:start position:0% remember Kiln or kinsuki that falls 00:04:04.500 --> 00:04:06.530 align:start position:0% remember Kiln or kinsuki that falls under<00:04:04.739> this<00:04:05.040> bucket<00:04:05.459> so<00:04:05.879> you<00:04:06.060> have<00:04:06.239> everyone 00:04:06.530 --> 00:04:06.540 align:start position:0% under this bucket so you have everyone 00:04:06.540 --> 00:04:08.630 align:start position:0% under this bucket so you have everyone all<00:04:07.080> over<00:04:07.200> the<00:04:07.440> place<00:04:07.680> testing<00:04:08.280> their<00:04:08.400> things 00:04:08.630 --> 00:04:08.640 align:start position:0% all over the place testing their things 00:04:08.640 --> 00:04:10.729 align:start position:0% all over the place testing their things layer<00:04:09.000> tools<00:04:09.360> are<00:04:09.480> deploying<00:04:09.900> over<00:04:10.080> there<00:04:10.379> we 00:04:10.729 --> 00:04:10.739 align:start position:0% layer tools are deploying over there we 00:04:10.739 --> 00:04:14.030 align:start position:0% layer tools are deploying over there we have<00:04:10.920> random<00:04:11.760> D5<00:04:12.540> protocols<00:04:13.140> deploying<00:04:13.920> over 00:04:14.030 --> 00:04:14.040 align:start position:0% have random D5 protocols deploying over 00:04:14.040 --> 00:04:15.949 align:start position:0% have random D5 protocols deploying over there<00:04:14.280> and<00:04:14.819> these<00:04:15.120> find<00:04:15.239> issues<00:04:15.659> that<00:04:15.780> only 00:04:15.949 --> 00:04:15.959 align:start position:0% there and these find issues that only 00:04:15.959 --> 00:04:18.110 align:start position:0% there and these find issues that only happen<00:04:16.199> on<00:04:16.500> real<00:04:16.680> world<00:04:16.859> workloads<00:04:17.639> you 00:04:18.110 --> 00:04:18.120 align:start position:0% happen on real world workloads you 00:04:18.120 --> 00:04:19.909 align:start position:0% happen on real world workloads you probably<00:04:18.660> can't<00:04:18.900> simulate<00:04:19.380> them<00:04:19.500> any<00:04:19.739> other 00:04:19.909 --> 00:04:19.919 align:start position:0% probably can't simulate them any other 00:04:19.919 --> 00:04:21.770 align:start position:0% probably can't simulate them any other way 00:04:21.770 --> 00:04:21.780 align:start position:0% way 00:04:21.780 --> 00:04:23.810 align:start position:0% way so<00:04:22.500> the<00:04:22.800> second<00:04:22.919> part<00:04:23.220> I'm<00:04:23.400> going<00:04:23.580> to<00:04:23.639> talk 00:04:23.810 --> 00:04:23.820 align:start position:0% so the second part I'm going to talk 00:04:23.820 --> 00:04:25.909 align:start position:0% so the second part I'm going to talk about<00:04:24.000> what<00:04:24.600> different<00:04:24.780> tools<00:04:25.199> we<00:04:25.380> had<00:04:25.560> and 00:04:25.909 --> 00:04:25.919 align:start position:0% about what different tools we had and 00:04:25.919 --> 00:04:28.310 align:start position:0% about what different tools we had and just<00:04:26.040> give<00:04:26.160> you<00:04:26.280> a<00:04:26.460> brief<00:04:26.639> overview<00:04:27.120> and<00:04:28.020> just 00:04:28.310 --> 00:04:28.320 align:start position:0% just give you a brief overview and just 00:04:28.320 --> 00:04:31.189 align:start position:0% just give you a brief overview and just to<00:04:28.560> tell<00:04:29.340> you<00:04:29.460> how<00:04:29.880> this<00:04:30.060> is<00:04:30.180> going<00:04:30.300> to<00:04:30.419> go<00:04:30.540> once 00:04:31.189 --> 00:04:31.199 align:start position:0% to tell you how this is going to go once 00:04:31.199 --> 00:04:32.510 align:start position:0% to tell you how this is going to go once you<00:04:31.259> have<00:04:31.440> an<00:04:31.560> overview<00:04:31.860> what<00:04:32.220> sort<00:04:32.400> of 00:04:32.510 --> 00:04:32.520 align:start position:0% you have an overview what sort of 00:04:32.520 --> 00:04:34.070 align:start position:0% you have an overview what sort of testing<00:04:32.880> tools<00:04:33.120> we<00:04:33.300> have<00:04:33.419> I'm<00:04:33.660> going<00:04:33.840> to<00:04:33.960> talk 00:04:34.070 --> 00:04:34.080 align:start position:0% testing tools we have I'm going to talk 00:04:34.080 --> 00:04:35.689 align:start position:0% testing tools we have I'm going to talk about<00:04:34.199> what<00:04:34.500> we<00:04:34.680> actually<00:04:34.800> did<00:04:35.040> with<00:04:35.220> them<00:04:35.400> and 00:04:35.689 --> 00:04:35.699 align:start position:0% about what we actually did with them and 00:04:35.699 --> 00:04:37.790 align:start position:0% about what we actually did with them and what<00:04:35.880> we<00:04:36.000> didn't<00:04:36.120> find 00:04:37.790 --> 00:04:37.800 align:start position:0% what we didn't find 00:04:37.800 --> 00:04:40.070 align:start position:0% what we didn't find so<00:04:38.220> the<00:04:38.460> first<00:04:38.580> one<00:04:38.820> uh<00:04:39.419> starting<00:04:39.600> at<00:04:39.840> a<00:04:39.960> high 00:04:40.070 --> 00:04:40.080 align:start position:0% so the first one uh starting at a high 00:04:40.080 --> 00:04:42.409 align:start position:0% so the first one uh starting at a high level<00:04:40.259> we<00:04:40.740> have<00:04:40.860> spec<00:04:41.040> tests<00:04:41.520> it's<00:04:42.060> the<00:04:42.240> great 00:04:42.409 --> 00:04:42.419 align:start position:0% level we have spec tests it's the great 00:04:42.419 --> 00:04:43.790 align:start position:0% level we have spec tests it's the great thing<00:04:42.540> about<00:04:42.720> the<00:04:42.960> consensus<00:04:43.380> layer<00:04:43.680> they 00:04:43.790 --> 00:04:43.800 align:start position:0% thing about the consensus layer they 00:04:43.800 --> 00:04:45.530 align:start position:0% thing about the consensus layer they have<00:04:43.979> an<00:04:44.040> executable<00:04:44.460> spec<00:04:44.759> they<00:04:45.360> have 00:04:45.530 --> 00:04:45.540 align:start position:0% have an executable spec they have 00:04:45.540 --> 00:04:47.870 align:start position:0% have an executable spec they have specifications<00:04:46.199> with<00:04:46.919> a<00:04:47.220> ton<00:04:47.340> of<00:04:47.520> tests 00:04:47.870 --> 00:04:47.880 align:start position:0% specifications with a ton of tests 00:04:47.880 --> 00:04:50.510 align:start position:0% specifications with a ton of tests client<00:04:48.780> teams<00:04:49.139> can<00:04:49.320> then<00:04:49.500> import<00:04:49.740> these<00:04:50.160> specs 00:04:50.510 --> 00:04:50.520 align:start position:0% client teams can then import these specs 00:04:50.520 --> 00:04:52.610 align:start position:0% client teams can then import these specs and<00:04:50.759> make<00:04:51.000> sure<00:04:51.180> that<00:04:51.600> they<00:04:51.900> can<00:04:52.080> test<00:04:52.199> them<00:04:52.440> in 00:04:52.610 --> 00:04:52.620 align:start position:0% and make sure that they can test them in 00:04:52.620 --> 00:04:54.469 align:start position:0% and make sure that they can test them in their<00:04:52.740> local<00:04:52.919> CI<00:04:53.340> this<00:04:53.940> means<00:04:54.180> whenever 00:04:54.469 --> 00:04:54.479 align:start position:0% their local CI this means whenever 00:04:54.479 --> 00:04:56.390 align:start position:0% their local CI this means whenever they're<00:04:54.720> making<00:04:54.840> a<00:04:55.080> release<00:04:55.199> at<00:04:56.040> least<00:04:56.220> you 00:04:56.390 --> 00:04:56.400 align:start position:0% they're making a release at least you 00:04:56.400 --> 00:04:58.310 align:start position:0% they're making a release at least you know<00:04:56.520> that<00:04:56.699> they're<00:04:56.820> coherent<00:04:57.300> to<00:04:57.479> the<00:04:57.600> spec 00:04:58.310 --> 00:04:58.320 align:start position:0% know that they're coherent to the spec 00:04:58.320 --> 00:05:01.010 align:start position:0% know that they're coherent to the spec uh<00:04:58.979> this<00:04:59.280> is<00:04:59.400> largely<00:04:59.759> a<00:05:00.000> sanity<00:05:00.360> check<00:05:00.660> it's 00:05:01.010 --> 00:05:01.020 align:start position:0% uh this is largely a sanity check it's 00:05:01.020 --> 00:05:04.550 align:start position:0% uh this is largely a sanity check it's not<00:05:01.259> meant<00:05:01.740> to<00:05:02.040> find<00:05:02.820> any<00:05:03.180> massive<00:05:03.600> bug<00:05:03.780> but<00:05:04.380> it 00:05:04.550 --> 00:05:04.560 align:start position:0% not meant to find any massive bug but it 00:05:04.560 --> 00:05:05.870 align:start position:0% not meant to find any massive bug but it ensures<00:05:04.919> that<00:05:05.100> there's<00:05:05.220> no<00:05:05.400> regressions 00:05:05.870 --> 00:05:05.880 align:start position:0% ensures that there's no regressions 00:05:05.880 --> 00:05:07.969 align:start position:0% ensures that there's no regressions happening 00:05:07.969 --> 00:05:07.979 align:start position:0% happening 00:05:07.979 --> 00:05:09.830 align:start position:0% happening we<00:05:08.460> currently<00:05:08.759> have<00:05:08.940> the<00:05:09.060> spec<00:05:09.240> tests<00:05:09.600> I<00:05:09.720> think 00:05:09.830 --> 00:05:09.840 align:start position:0% we currently have the spec tests I think 00:05:09.840 --> 00:05:13.610 align:start position:0% we currently have the spec tests I think running<00:05:10.020> every<00:05:10.740> night<00:05:11.340> on<00:05:11.880> on<00:05:12.840> a<00:05:13.199> new<00:05:13.320> CI 00:05:13.610 --> 00:05:13.620 align:start position:0% running every night on on a new CI 00:05:13.620 --> 00:05:15.110 align:start position:0% running every night on on a new CI machine 00:05:15.110 --> 00:05:15.120 align:start position:0% machine 00:05:15.120 --> 00:05:17.150 align:start position:0% machine the<00:05:15.419> second<00:05:15.540> one<00:05:15.780> is<00:05:16.139> hype<00:05:16.620> tests<00:05:16.860> you<00:05:17.040> might 00:05:17.150 --> 00:05:17.160 align:start position:0% the second one is hype tests you might 00:05:17.160 --> 00:05:18.469 align:start position:0% the second one is hype tests you might have<00:05:17.340> seen<00:05:17.400> this<00:05:17.580> being<00:05:17.759> referenced<00:05:18.240> a<00:05:18.360> couple 00:05:18.469 --> 00:05:18.479 align:start position:0% have seen this being referenced a couple 00:05:18.479 --> 00:05:19.670 align:start position:0% have seen this being referenced a couple of<00:05:18.600> times 00:05:19.670 --> 00:05:19.680 align:start position:0% of times 00:05:19.680 --> 00:05:22.730 align:start position:0% of times um<00:05:19.740> so<00:05:20.340> Hive<00:05:20.699> tests<00:05:21.060> run<00:05:21.240> with<00:05:21.600> the<00:05:21.720> simulator 00:05:22.730 --> 00:05:22.740 align:start position:0% um so Hive tests run with the simulator 00:05:22.740 --> 00:05:24.469 align:start position:0% um so Hive tests run with the simulator and<00:05:23.340> they<00:05:23.580> essentially<00:05:23.880> start<00:05:24.120> up<00:05:24.300> the 00:05:24.469 --> 00:05:24.479 align:start position:0% and they essentially start up the 00:05:24.479 --> 00:05:26.810 align:start position:0% and they essentially start up the clients<00:05:24.840> and<00:05:25.139> then<00:05:25.320> run<00:05:25.620> the<00:05:25.860> tests<00:05:26.160> against<00:05:26.400> a 00:05:26.810 --> 00:05:26.820 align:start position:0% clients and then run the tests against a 00:05:26.820 --> 00:05:28.969 align:start position:0% clients and then run the tests against a predefined<00:05:27.300> interface<00:05:27.720> these<00:05:28.500> are<00:05:28.560> a<00:05:28.740> couple 00:05:28.969 --> 00:05:28.979 align:start position:0% predefined interface these are a couple 00:05:28.979 --> 00:05:31.490 align:start position:0% predefined interface these are a couple hundred<00:05:29.520> tests<00:05:30.060> these<00:05:30.660> take<00:05:30.900> anywhere 00:05:31.490 --> 00:05:31.500 align:start position:0% hundred tests these take anywhere 00:05:31.500 --> 00:05:33.590 align:start position:0% hundred tests these take anywhere between<00:05:31.740> I<00:05:32.039> think<00:05:32.160> a<00:05:32.340> day<00:05:32.520> or<00:05:32.759> two<00:05:33.060> days<00:05:33.240> to<00:05:33.479> run 00:05:33.590 --> 00:05:33.600 align:start position:0% between I think a day or two days to run 00:05:33.600 --> 00:05:34.570 align:start position:0% between I think a day or two days to run everything 00:05:34.570 --> 00:05:34.580 align:start position:0% everything 00:05:34.580 --> 00:05:38.510 align:start position:0% everything and<00:05:35.580> a<00:05:35.759> brief<00:05:36.120> example<00:05:36.539> of<00:05:36.780> how<00:05:36.960> this<00:05:37.199> is<00:05:37.380> is<00:05:37.800> it 00:05:38.510 --> 00:05:38.520 align:start position:0% and a brief example of how this is is it 00:05:38.520 --> 00:05:40.490 align:start position:0% and a brief example of how this is is it sets<00:05:38.880> up<00:05:38.940> a<00:05:39.180> tiny<00:05:39.539> instance<00:05:39.780> of<00:05:39.960> another<00:05:40.139> mine 00:05:40.490 --> 00:05:40.500 align:start position:0% sets up a tiny instance of another mine 00:05:40.500 --> 00:05:42.529 align:start position:0% sets up a tiny instance of another mine node<00:05:40.800> it<00:05:41.160> sends<00:05:41.520> it<00:05:41.580> two<00:05:41.759> terminal<00:05:42.000> blocks<00:05:42.419> and 00:05:42.529 --> 00:05:42.539 align:start position:0% node it sends it two terminal blocks and 00:05:42.539 --> 00:05:44.529 align:start position:0% node it sends it two terminal blocks and asserts<00:05:42.960> how<00:05:43.080> the<00:05:43.199> transition<00:05:43.560> happens 00:05:44.529 --> 00:05:44.539 align:start position:0% asserts how the transition happens 00:05:44.539 --> 00:05:47.870 align:start position:0% asserts how the transition happens this<00:05:45.539> is<00:05:46.380> a<00:05:46.680> lot<00:05:46.800> of<00:05:46.919> awesome<00:05:47.100> work<00:05:47.460> by<00:05:47.699> Mario 00:05:47.870 --> 00:05:47.880 align:start position:0% this is a lot of awesome work by Mario 00:05:47.880 --> 00:05:49.909 align:start position:0% this is a lot of awesome work by Mario he<00:05:48.300> should<00:05:48.539> be<00:05:48.660> somewhere<00:05:49.259> in<00:05:49.500> the<00:05:49.620> crowd 00:05:49.909 --> 00:05:49.919 align:start position:0% he should be somewhere in the crowd 00:05:49.919 --> 00:05:51.830 align:start position:0% he should be somewhere in the crowd shout<00:05:50.699> out<00:05:50.759> to<00:05:50.940> him<00:05:51.060> and<00:05:51.419> follow<00:05:51.539> him<00:05:51.720> on 00:05:51.830 --> 00:05:51.840 align:start position:0% shout out to him and follow him on 00:05:51.840 --> 00:05:52.629 align:start position:0% shout out to him and follow him on Twitter 00:05:52.629 --> 00:05:52.639 align:start position:0% Twitter 00:05:52.639 --> 00:05:55.969 align:start position:0% Twitter we<00:05:53.639> found<00:05:53.880> a<00:05:54.419> lot<00:05:54.539> of<00:05:54.720> edge<00:05:54.960> cases<00:05:55.380> in<00:05:55.560> this<00:05:55.740> and 00:05:55.969 --> 00:05:55.979 align:start position:0% we found a lot of edge cases in this and 00:05:55.979 --> 00:05:57.830 align:start position:0% we found a lot of edge cases in this and once<00:05:56.220> we<00:05:56.340> do<00:05:56.520> find<00:05:56.699> an<00:05:56.880> edge<00:05:57.060> case<00:05:57.240> it's<00:05:57.600> always 00:05:57.830 --> 00:05:57.840 align:start position:0% once we do find an edge case it's always 00:05:57.840 --> 00:06:01.129 align:start position:0% once we do find an edge case it's always in<00:05:58.199> this<00:05:58.380> so<00:05:58.860> that<00:05:59.039> we<00:05:59.160> make<00:05:59.340> sure<00:05:59.900> in<00:06:00.900> in 00:06:01.129 --> 00:06:01.139 align:start position:0% in this so that we make sure in in 00:06:01.139 --> 00:06:03.290 align:start position:0% in this so that we make sure in in future<00:06:01.440> updates<00:06:02.340> whatever<00:06:02.699> it<00:06:03.120> doesn't 00:06:03.290 --> 00:06:03.300 align:start position:0% future updates whatever it doesn't 00:06:03.300 --> 00:06:06.230 align:start position:0% future updates whatever it doesn't happen<00:06:03.979> if<00:06:04.979> people<00:06:05.220> check<00:06:05.580> the<00:06:05.820> website<00:06:06.120> of 00:06:06.230 --> 00:06:06.240 align:start position:0% happen if people check the website of 00:06:06.240 --> 00:06:07.670 align:start position:0% happen if people check the website of course 00:06:07.670 --> 00:06:07.680 align:start position:0% course 00:06:07.680 --> 00:06:09.830 align:start position:0% course then<00:06:08.220> we<00:06:08.520> have<00:06:08.639> this<00:06:08.820> thing<00:06:09.000> called<00:06:09.180> kurtosis 00:06:09.830 --> 00:06:09.840 align:start position:0% then we have this thing called kurtosis 00:06:09.840 --> 00:06:11.510 align:start position:0% then we have this thing called kurtosis it's<00:06:10.259> an<00:06:10.440> external<00:06:10.800> tool<00:06:11.100> that<00:06:11.220> we're<00:06:11.340> working 00:06:11.510 --> 00:06:11.520 align:start position:0% it's an external tool that we're working 00:06:11.520 --> 00:06:14.689 align:start position:0% it's an external tool that we're working with<00:06:11.759> and<00:06:12.300> kurtosis<00:06:13.100> obfuscates<00:06:14.100> all<00:06:14.520> the 00:06:14.689 --> 00:06:14.699 align:start position:0% with and kurtosis obfuscates all the 00:06:14.699 --> 00:06:16.249 align:start position:0% with and kurtosis obfuscates all the complexity<00:06:15.120> with<00:06:15.360> setting<00:06:15.660> up<00:06:15.720> a<00:06:15.840> test<00:06:16.020> net 00:06:16.249 --> 00:06:16.259 align:start position:0% complexity with setting up a test net 00:06:16.259 --> 00:06:17.629 align:start position:0% complexity with setting up a test net you<00:06:16.740> don't<00:06:16.860> have<00:06:16.979> to<00:06:17.100> worry<00:06:17.220> about<00:06:17.400> how 00:06:17.629 --> 00:06:17.639 align:start position:0% you don't have to worry about how 00:06:17.639 --> 00:06:19.249 align:start position:0% you don't have to worry about how Genesis<00:06:18.120> works<00:06:18.539> you<00:06:18.660> don't<00:06:18.780> have<00:06:18.900> to<00:06:19.020> worry 00:06:19.249 --> 00:06:19.259 align:start position:0% Genesis works you don't have to worry 00:06:19.259 --> 00:06:22.010 align:start position:0% Genesis works you don't have to worry what<00:06:20.039> format<00:06:20.580> that<00:06:20.880> never<00:06:21.120> mind<00:06:21.360> needs<00:06:21.780> its 00:06:22.010 --> 00:06:22.020 align:start position:0% what format that never mind needs its 00:06:22.020 --> 00:06:24.230 align:start position:0% what format that never mind needs its Genesis<00:06:22.259> file<00:06:22.500> in<00:06:22.800> nothing<00:06:23.160> you<00:06:23.880> just<00:06:24.000> Define 00:06:24.230 --> 00:06:24.240 align:start position:0% Genesis file in nothing you just Define 00:06:24.240 --> 00:06:26.689 align:start position:0% Genesis file in nothing you just Define it<00:06:24.539> in<00:06:24.720> a<00:06:24.840> yaml<00:06:25.139> file<00:06:25.440> you<00:06:25.620> say<00:06:25.800> I<00:06:26.100> want<00:06:26.280> a<00:06:26.520> five 00:06:26.689 --> 00:06:26.699 align:start position:0% it in a yaml file you say I want a five 00:06:26.699 --> 00:06:29.210 align:start position:0% it in a yaml file you say I want a five node<00:06:27.000> network<00:06:27.240> with<00:06:27.960> this<00:06:28.319> Docker<00:06:28.740> image<00:06:29.039> and 00:06:29.210 --> 00:06:29.220 align:start position:0% node network with this Docker image and 00:06:29.220 --> 00:06:31.189 align:start position:0% node network with this Docker image and that's<00:06:29.400> what<00:06:29.580> happens<00:06:29.759> for<00:06:30.120> you 00:06:31.189 --> 00:06:31.199 align:start position:0% that's what happens for you 00:06:31.199 --> 00:06:33.529 align:start position:0% that's what happens for you um<00:06:31.259> we<00:06:31.440> time<00:06:31.680> this<00:06:31.919> actually<00:06:32.039> nightly<00:06:32.580> and 00:06:33.529 --> 00:06:33.539 align:start position:0% um we time this actually nightly and 00:06:33.539 --> 00:06:35.870 align:start position:0% um we time this actually nightly and they<00:06:34.020> think<00:06:34.620> we've<00:06:34.979> gone<00:06:35.220> through<00:06:35.400> the<00:06:35.580> merge 00:06:35.870 --> 00:06:35.880 align:start position:0% they think we've gone through the merge 00:06:35.880 --> 00:06:37.610 align:start position:0% they think we've gone through the merge at<00:06:36.060> least<00:06:36.180> a<00:06:36.360> couple<00:06:36.539> hundred<00:06:37.080> times<00:06:37.319> this 00:06:37.610 --> 00:06:37.620 align:start position:0% at least a couple hundred times this 00:06:37.620 --> 00:06:38.990 align:start position:0% at least a couple hundred times this year 00:06:38.990 --> 00:06:39.000 align:start position:0% year 00:06:39.000 --> 00:06:41.689 align:start position:0% year um<00:06:39.080> a<00:06:40.080> lot<00:06:40.199> of<00:06:40.319> them<00:06:40.440> with<00:06:40.680> issues<00:06:41.160> but<00:06:41.400> a<00:06:41.639> lot 00:06:41.689 --> 00:06:41.699 align:start position:0% um a lot of them with issues but a lot 00:06:41.699 --> 00:06:44.450 align:start position:0% um a lot of them with issues but a lot of<00:06:41.819> them<00:06:41.940> without<00:06:42.180> which<00:06:42.660> is<00:06:42.780> great<00:06:43.020> to<00:06:43.199> see<00:06:43.460> we 00:06:44.450 --> 00:06:44.460 align:start position:0% of them without which is great to see we 00:06:44.460 --> 00:06:46.370 align:start position:0% of them without which is great to see we use<00:06:44.580> this<00:06:44.759> also<00:06:45.120> to<00:06:45.240> rapidly<00:06:45.660> iterate<00:06:46.139> ideas 00:06:46.370 --> 00:06:46.380 align:start position:0% use this also to rapidly iterate ideas 00:06:46.380 --> 00:06:48.529 align:start position:0% use this also to rapidly iterate ideas so<00:06:46.800> once<00:06:47.100> there's<00:06:47.220> a<00:06:47.340> new<00:06:47.460> spec<00:06:47.699> version<00:06:48.000> or<00:06:48.419> if 00:06:48.529 --> 00:06:48.539 align:start position:0% so once there's a new spec version or if 00:06:48.539 --> 00:06:49.969 align:start position:0% so once there's a new spec version or if you<00:06:48.660> want<00:06:48.780> to<00:06:48.900> try<00:06:48.960> out<00:06:49.139> a<00:06:49.319> new<00:06:49.440> testing<00:06:49.740> tool 00:06:49.969 --> 00:06:49.979 align:start position:0% you want to try out a new testing tool 00:06:49.979 --> 00:06:52.189 align:start position:0% you want to try out a new testing tool we<00:06:50.220> throw<00:06:50.400> it<00:06:50.580> in<00:06:50.699> there<00:06:50.819> first<00:06:51.000> we<00:06:51.720> also<00:06:52.020> had 00:06:52.189 --> 00:06:52.199 align:start position:0% we throw it in there first we also had 00:06:52.199 --> 00:06:54.469 align:start position:0% we throw it in there first we also had map<00:06:52.500> boost<00:06:52.740> integrated<00:06:53.340> into<00:06:53.580> kurtosis<00:06:54.180> so<00:06:54.360> we 00:06:54.469 --> 00:06:54.479 align:start position:0% map boost integrated into kurtosis so we 00:06:54.479 --> 00:06:56.210 align:start position:0% map boost integrated into kurtosis so we could<00:06:54.539> test<00:06:54.720> it<00:06:54.900> out<00:06:55.080> and<00:06:55.440> do<00:06:55.680> a<00:06:55.860> lot<00:06:55.979> of<00:06:56.100> cool 00:06:56.210 --> 00:06:56.220 align:start position:0% could test it out and do a lot of cool 00:06:56.220 --> 00:06:58.070 align:start position:0% could test it out and do a lot of cool things<00:06:56.460> there 00:06:58.070 --> 00:06:58.080 align:start position:0% things there 00:06:58.080 --> 00:07:01.370 align:start position:0% things there um<00:06:58.139> a<00:06:58.979> general<00:06:59.520> view<00:06:59.940> of<00:07:00.180> kurtosis<00:07:00.660> is<00:07:00.960> it<00:07:01.139> it 00:07:01.370 --> 00:07:01.380 align:start position:0% um a general view of kurtosis is it it 00:07:01.380 --> 00:07:02.930 align:start position:0% um a general view of kurtosis is it it checks<00:07:01.680> the<00:07:01.860> happy<00:07:01.979> case<00:07:02.220> if<00:07:02.699> you<00:07:02.819> can't 00:07:02.930 --> 00:07:02.940 align:start position:0% checks the happy case if you can't 00:07:02.940 --> 00:07:04.249 align:start position:0% checks the happy case if you can't figure<00:07:03.120> out<00:07:03.360> the<00:07:03.539> happy<00:07:03.660> case<00:07:03.900> there's<00:07:04.139> no 00:07:04.249 --> 00:07:04.259 align:start position:0% figure out the happy case there's no 00:07:04.259 --> 00:07:06.170 align:start position:0% figure out the happy case there's no point<00:07:04.440> checking<00:07:04.860> the<00:07:05.039> rest<00:07:05.220> of<00:07:05.400> it<00:07:05.520> so<00:07:05.940> it<00:07:06.060> just 00:07:06.170 --> 00:07:06.180 align:start position:0% point checking the rest of it so it just 00:07:06.180 --> 00:07:07.550 align:start position:0% point checking the rest of it so it just starts<00:07:06.479> up<00:07:06.539> a<00:07:06.720> test<00:07:06.840> net<00:07:07.020> make<00:07:07.380> sure 00:07:07.550 --> 00:07:07.560 align:start position:0% starts up a test net make sure 00:07:07.560 --> 00:07:10.730 align:start position:0% starts up a test net make sure everything<00:07:07.800> is<00:07:08.100> fine<00:07:08.280> if<00:07:08.940> it's<00:07:09.120> fine<00:07:09.360> it<00:07:10.139> shows 00:07:10.730 --> 00:07:10.740 align:start position:0% everything is fine if it's fine it shows 00:07:10.740 --> 00:07:13.850 align:start position:0% everything is fine if it's fine it shows you<00:07:10.800> green<00:07:10.979> on<00:07:11.160> your<00:07:11.280> CI 00:07:13.850 --> 00:07:13.860 align:start position:0% 00:07:13.860 --> 00:07:16.670 align:start position:0% the<00:07:14.280> next<00:07:14.400> one<00:07:14.639> is<00:07:15.060> sync<00:07:15.600> tests 00:07:16.670 --> 00:07:16.680 align:start position:0% the next one is sync tests 00:07:16.680 --> 00:07:18.290 align:start position:0% the next one is sync tests um<00:07:16.800> there's<00:07:16.979> no<00:07:17.220> point<00:07:17.400> on<00:07:17.580> a<00:07:17.699> network<00:07:17.819> if<00:07:18.180> you 00:07:18.290 --> 00:07:18.300 align:start position:0% um there's no point on a network if you 00:07:18.300 --> 00:07:19.909 align:start position:0% um there's no point on a network if you have<00:07:18.419> nodes<00:07:18.720> that<00:07:19.020> can't<00:07:19.139> sync<00:07:19.500> up<00:07:19.560> to<00:07:19.740> the 00:07:19.909 --> 00:07:19.919 align:start position:0% have nodes that can't sync up to the 00:07:19.919 --> 00:07:22.730 align:start position:0% have nodes that can't sync up to the network<00:07:20.039> so<00:07:21.000> what<00:07:21.240> we<00:07:21.419> do<00:07:21.599> is<00:07:22.020> we<00:07:22.259> spin<00:07:22.560> up 00:07:22.730 --> 00:07:22.740 align:start position:0% network so what we do is we spin up 00:07:22.740 --> 00:07:26.029 align:start position:0% network so what we do is we spin up nodes<00:07:23.580> I<00:07:23.759> think<00:07:23.940> at<00:07:24.360> a<00:07:24.539> week's<00:07:25.020> notice<00:07:25.740> right 00:07:26.029 --> 00:07:26.039 align:start position:0% nodes I think at a week's notice right 00:07:26.039 --> 00:07:26.809 align:start position:0% nodes I think at a week's notice right now 00:07:26.809 --> 00:07:26.819 align:start position:0% now 00:07:26.819 --> 00:07:28.270 align:start position:0% now um<00:07:26.880> they<00:07:27.060> sync<00:07:27.360> up<00:07:27.419> to<00:07:27.599> the<00:07:27.720> head<00:07:27.780> of<00:07:27.960> the<00:07:28.080> chain 00:07:28.270 --> 00:07:28.280 align:start position:0% um they sync up to the head of the chain 00:07:28.280 --> 00:07:31.370 align:start position:0% um they sync up to the head of the chain and<00:07:29.280> then<00:07:29.460> they<00:07:29.699> assert<00:07:30.120> whatever<00:07:30.479> we<00:07:30.840> specify 00:07:31.370 --> 00:07:31.380 align:start position:0% and then they assert whatever we specify 00:07:31.380 --> 00:07:33.830 align:start position:0% and then they assert whatever we specify over<00:07:31.740> there<00:07:31.979> so<00:07:32.699> if<00:07:33.060> you<00:07:33.180> notice<00:07:33.479> over<00:07:33.660> here 00:07:33.830 --> 00:07:33.840 align:start position:0% over there so if you notice over here 00:07:33.840 --> 00:07:36.170 align:start position:0% over there so if you notice over here you<00:07:34.020> can<00:07:34.139> say<00:07:34.319> is<00:07:34.560> execution<00:07:35.160> healthy<00:07:36.000> is 00:07:36.170 --> 00:07:36.180 align:start position:0% you can say is execution healthy is 00:07:36.180 --> 00:07:38.570 align:start position:0% you can say is execution healthy is consensus<00:07:36.720> healthy<00:07:37.080> are<00:07:37.319> both<00:07:37.500> synced<00:07:37.979> are 00:07:38.570 --> 00:07:38.580 align:start position:0% consensus healthy are both synced are 00:07:38.580 --> 00:07:41.689 align:start position:0% consensus healthy are both synced are they<00:07:38.759> both<00:07:38.940> reaching<00:07:39.900> head<00:07:40.080> so<00:07:40.560> you<00:07:40.860> can<00:07:41.039> kind 00:07:41.689 --> 00:07:41.699 align:start position:0% they both reaching head so you can kind 00:07:41.699 --> 00:07:44.390 align:start position:0% they both reaching head so you can kind of<00:07:41.819> Define<00:07:42.360> what<00:07:42.900> side<00:07:43.139> a<00:07:43.440> type<00:07:43.680> of<00:07:43.860> syncing 00:07:44.390 --> 00:07:44.400 align:start position:0% of Define what side a type of syncing 00:07:44.400 --> 00:07:46.550 align:start position:0% of Define what side a type of syncing you<00:07:44.580> want<00:07:44.639> to<00:07:44.759> do<00:07:44.880> here 00:07:46.550 --> 00:07:46.560 align:start position:0% you want to do here 00:07:46.560 --> 00:07:48.890 align:start position:0% you want to do here um and<00:07:47.280> as<00:07:47.460> you<00:07:47.580> can<00:07:47.699> see<00:07:47.819> on<00:07:48.000> the<00:07:48.120> right<00:07:48.300> there 00:07:48.890 --> 00:07:48.900 align:start position:0% um and as you can see on the right there 00:07:48.900 --> 00:07:50.809 align:start position:0% um and as you can see on the right there are<00:07:49.080> a<00:07:49.500> ton<00:07:49.740> of<00:07:49.979> different<00:07:50.099> options<00:07:50.460> you<00:07:50.699> can 00:07:50.809 --> 00:07:50.819 align:start position:0% are a ton of different options you can 00:07:50.819 --> 00:07:53.029 align:start position:0% are a ton of different options you can do<00:07:50.880> and<00:07:51.180> a<00:07:51.360> ton<00:07:51.419> of<00:07:51.539> Networks<00:07:52.380> and<00:07:52.800> the<00:07:52.919> cool 00:07:53.029 --> 00:07:53.039 align:start position:0% do and a ton of Networks and the cool 00:07:53.039 --> 00:07:55.129 align:start position:0% do and a ton of Networks and the cool thing<00:07:53.220> is<00:07:53.400> you<00:07:53.639> can<00:07:53.699> also<00:07:53.940> assert<00:07:54.360> bad<00:07:54.720> cases 00:07:55.129 --> 00:07:55.139 align:start position:0% thing is you can also assert bad cases 00:07:55.139 --> 00:07:58.129 align:start position:0% thing is you can also assert bad cases you<00:07:55.440> can<00:07:55.500> say<00:07:55.680> start<00:07:56.039> your<00:07:56.280> El<00:07:56.520> stop<00:07:57.419> once<00:07:58.080> it 00:07:58.129 --> 00:07:58.139 align:start position:0% you can say start your El stop once it 00:07:58.139 --> 00:08:00.770 align:start position:0% you can say start your El stop once it reaches<00:07:58.500> head<00:07:58.680> then<00:07:59.160> start<00:07:59.460> your<00:07:59.639> CL<00:07:59.880> and<00:08:00.660> then 00:08:00.770 --> 00:08:00.780 align:start position:0% reaches head then start your CL and then 00:08:00.780 --> 00:08:03.230 align:start position:0% reaches head then start your CL and then build<00:08:01.259> weird<00:08:01.560> scenarios<00:08:02.220> there 00:08:03.230 --> 00:08:03.240 align:start position:0% build weird scenarios there 00:08:03.240 --> 00:08:05.029 align:start position:0% build weird scenarios there um shout<00:08:03.539> out<00:08:03.660> to<00:08:03.780> Sam<00:08:03.960> for<00:08:04.259> building<00:08:04.380> this<00:08:04.680> he 00:08:05.029 --> 00:08:05.039 align:start position:0% um shout out to Sam for building this he 00:08:05.039 --> 00:08:06.469 align:start position:0% um shout out to Sam for building this he was<00:08:05.160> also<00:08:05.400> running<00:08:05.580> it<00:08:05.819> and<00:08:06.000> sending<00:08:06.360> a 00:08:06.469 --> 00:08:06.479 align:start position:0% was also running it and sending a 00:08:06.479 --> 00:08:08.629 align:start position:0% was also running it and sending a summary<00:08:06.780> I<00:08:07.560> think<00:08:07.680> he<00:08:07.800> even<00:08:07.979> presented<00:08:08.460> it 00:08:08.629 --> 00:08:08.639 align:start position:0% summary I think he even presented it 00:08:08.639 --> 00:08:10.850 align:start position:0% summary I think he even presented it once<00:08:08.940> on<00:08:09.120> Orca<00:08:09.599> devs 00:08:10.850 --> 00:08:10.860 align:start position:0% once on Orca devs 00:08:10.860 --> 00:08:13.070 align:start position:0% once on Orca devs um<00:08:10.919> so<00:08:11.759> we<00:08:11.940> could<00:08:12.060> make<00:08:12.300> sure<00:08:12.419> that<00:08:12.660> at<00:08:12.960> least 00:08:13.070 --> 00:08:13.080 align:start position:0% um so we could make sure that at least 00:08:13.080 --> 00:08:14.809 align:start position:0% um so we could make sure that at least when<00:08:13.440> we're<00:08:13.620> making<00:08:13.860> releases<00:08:14.340> and<00:08:14.520> when<00:08:14.699> we 00:08:14.809 --> 00:08:14.819 align:start position:0% when we're making releases and when we 00:08:14.819 --> 00:08:18.170 align:start position:0% when we're making releases and when we merge<00:08:15.240> that<00:08:15.419> we<00:08:15.660> can<00:08:15.780> sync<00:08:16.080> the<00:08:16.259> network 00:08:18.170 --> 00:08:18.180 align:start position:0% merge that we can sync the network 00:08:18.180 --> 00:08:20.930 align:start position:0% merge that we can sync the network and<00:08:18.780> this<00:08:19.020> is<00:08:19.080> the<00:08:19.259> meaty<00:08:19.560> one<00:08:19.800> we<00:08:20.460> had<00:08:20.639> test 00:08:20.930 --> 00:08:20.940 align:start position:0% and this is the meaty one we had test 00:08:20.940 --> 00:08:24.469 align:start position:0% and this is the meaty one we had test Nets<00:08:21.360> and<00:08:21.539> shadowfox<00:08:22.199> so<00:08:23.099> a<00:08:23.460> shadow<00:08:23.759> fork<00:08:24.240> and 00:08:24.469 --> 00:08:24.479 align:start position:0% Nets and shadowfox so a shadow fork and 00:08:24.479 --> 00:08:27.170 align:start position:0% Nets and shadowfox so a shadow fork and testnet<00:08:25.020> help<00:08:25.259> us<00:08:25.680> coordinate<00:08:26.460> all<00:08:26.819> client 00:08:27.170 --> 00:08:27.180 align:start position:0% testnet help us coordinate all client 00:08:27.180 --> 00:08:29.990 align:start position:0% testnet help us coordinate all client teams<00:08:27.479> in<00:08:27.599> one<00:08:27.780> place<00:08:28.099> and<00:08:29.099> we<00:08:29.639> check 00:08:29.990 --> 00:08:30.000 align:start position:0% teams in one place and we check 00:08:30.000 --> 00:08:32.810 align:start position:0% teams in one place and we check compatibility<00:08:30.720> largely<00:08:31.319> we<00:08:32.219> take<00:08:32.520> whatever 00:08:32.810 --> 00:08:32.820 align:start position:0% compatibility largely we take whatever 00:08:32.820 --> 00:08:34.909 align:start position:0% compatibility largely we take whatever assumptions<00:08:33.479> we<00:08:33.719> have<00:08:33.839> in<00:08:34.020> the<00:08:34.140> spec<00:08:34.320> and<00:08:34.740> we 00:08:34.909 --> 00:08:34.919 align:start position:0% assumptions we have in the spec and we 00:08:34.919 --> 00:08:37.010 align:start position:0% assumptions we have in the spec and we assert<00:08:35.219> if<00:08:35.459> those<00:08:35.580> assumptions<00:08:36.060> are<00:08:36.240> true 00:08:37.010 --> 00:08:37.020 align:start position:0% assert if those assumptions are true 00:08:37.020 --> 00:08:39.230 align:start position:0% assert if those assumptions are true on<00:08:37.560> a<00:08:37.740> large<00:08:37.919> level<00:08:38.159> what<00:08:38.520> we're<00:08:38.640> doing<00:08:38.880> is 00:08:39.230 --> 00:08:39.240 align:start position:0% on a large level what we're doing is 00:08:39.240 --> 00:08:41.029 align:start position:0% on a large level what we're doing is we're<00:08:39.479> taking<00:08:39.659> the<00:08:39.899> Genesis<00:08:40.320> configuration 00:08:41.029 --> 00:08:41.039 align:start position:0% we're taking the Genesis configuration 00:08:41.039 --> 00:08:43.730 align:start position:0% we're taking the Genesis configuration of<00:08:41.459> any<00:08:41.760> one<00:08:42.000> network<00:08:42.300> and<00:08:42.839> then<00:08:42.959> we<00:08:43.140> modify<00:08:43.620> a 00:08:43.730 --> 00:08:43.740 align:start position:0% of any one network and then we modify a 00:08:43.740 --> 00:08:46.010 align:start position:0% of any one network and then we modify a couple<00:08:43.860> of<00:08:43.979> values<00:08:44.399> here<00:08:44.580> and<00:08:44.760> there<00:08:44.940> and<00:08:45.779> what 00:08:46.010 --> 00:08:46.020 align:start position:0% couple of values here and there and what 00:08:46.020 --> 00:08:47.690 align:start position:0% couple of values here and there and what happens<00:08:46.200> when<00:08:46.500> those<00:08:46.680> modified<00:08:47.040> values<00:08:47.580> are 00:08:47.690 --> 00:08:47.700 align:start position:0% happens when those modified values are 00:08:47.700 --> 00:08:49.370 align:start position:0% happens when those modified values are hit<00:08:47.880> is<00:08:48.180> we<00:08:48.360> split<00:08:48.660> away<00:08:48.839> from<00:08:49.019> the<00:08:49.200> main 00:08:49.370 --> 00:08:49.380 align:start position:0% hit is we split away from the main 00:08:49.380 --> 00:08:52.370 align:start position:0% hit is we split away from the main network<00:08:49.700> but<00:08:50.700> we<00:08:51.000> continue<00:08:51.180> staying<00:08:51.899> sync 00:08:52.370 --> 00:08:52.380 align:start position:0% network but we continue staying sync 00:08:52.380 --> 00:08:54.410 align:start position:0% network but we continue staying sync connected<00:08:53.100> on<00:08:53.279> the<00:08:53.399> gossip<00:08:53.700> Network<00:08:53.940> so<00:08:54.240> we're 00:08:54.410 --> 00:08:54.420 align:start position:0% connected on the gossip Network so we're 00:08:54.420 --> 00:08:56.269 align:start position:0% connected on the gossip Network so we're importing<00:08:54.899> all<00:08:55.019> the<00:08:55.200> transactions<00:08:55.800> and<00:08:56.100> we 00:08:56.269 --> 00:08:56.279 align:start position:0% importing all the transactions and we 00:08:56.279 --> 00:08:59.090 align:start position:0% importing all the transactions and we have<00:08:56.399> the<00:08:56.640> old<00:08:56.760> load<00:08:57.240> but<00:08:58.080> it's<00:08:58.500> on<00:08:58.680> our<00:08:58.860> side 00:08:59.090 --> 00:08:59.100 align:start position:0% have the old load but it's on our side 00:08:59.100 --> 00:09:02.389 align:start position:0% have the old load but it's on our side we<00:08:59.640> it's<00:09:00.000> it's<00:09:00.180> just<00:09:00.420> a<00:09:00.540> side<00:09:00.720> Fork<00:09:01.140> it<00:09:01.980> runs 00:09:02.389 --> 00:09:02.399 align:start position:0% we it's it's just a side Fork it runs 00:09:02.399 --> 00:09:04.370 align:start position:0% we it's it's just a side Fork it runs parallel<00:09:02.640> to<00:09:02.940> the<00:09:03.060> main<00:09:03.180> Network<00:09:03.360> and<00:09:03.839> no<00:09:04.080> one 00:09:04.370 --> 00:09:04.380 align:start position:0% parallel to the main Network and no one 00:09:04.380 --> 00:09:07.670 align:start position:0% parallel to the main Network and no one cares<00:09:04.800> about<00:09:04.920> it<00:09:05.300> except<00:09:06.300> for<00:09:06.540> us<00:09:07.019> because<00:09:07.380> we 00:09:07.670 --> 00:09:07.680 align:start position:0% cares about it except for us because we 00:09:07.680 --> 00:09:09.910 align:start position:0% cares about it except for us because we can<00:09:07.800> find<00:09:07.980> dozens<00:09:08.519> and<00:09:08.640> dozens<00:09:08.940> of<00:09:09.060> bugs<00:09:09.420> there 00:09:09.910 --> 00:09:09.920 align:start position:0% can find dozens and dozens of bugs there 00:09:09.920 --> 00:09:12.590 align:start position:0% can find dozens and dozens of bugs there this<00:09:10.920> allows<00:09:11.339> us<00:09:11.459> to<00:09:11.760> stress<00:09:12.120> all<00:09:12.360> of<00:09:12.480> our 00:09:12.590 --> 00:09:12.600 align:start position:0% this allows us to stress all of our 00:09:12.600 --> 00:09:15.230 align:start position:0% this allows us to stress all of our assumptions<00:09:13.160> and<00:09:14.160> we've<00:09:14.580> done<00:09:14.760> a<00:09:14.940> lot<00:09:15.000> of<00:09:15.120> them 00:09:15.230 --> 00:09:15.240 align:start position:0% assumptions and we've done a lot of them 00:09:15.240 --> 00:09:16.670 align:start position:0% assumptions and we've done a lot of them I<00:09:15.420> have<00:09:15.540> a<00:09:15.660> summary<00:09:15.839> on<00:09:16.019> how<00:09:16.200> many<00:09:16.320> we<00:09:16.500> actually 00:09:16.670 --> 00:09:16.680 align:start position:0% I have a summary on how many we actually 00:09:16.680 --> 00:09:17.990 align:start position:0% I have a summary on how many we actually did<00:09:16.920> in<00:09:17.100> the<00:09:17.279> end 00:09:17.990 --> 00:09:18.000 align:start position:0% did in the end 00:09:18.000 --> 00:09:20.509 align:start position:0% did in the end um<00:09:18.480> I<00:09:19.200> sort<00:09:19.500> of<00:09:19.560> look<00:09:19.680> at<00:09:19.860> this<00:09:20.040> as<00:09:20.220> a<00:09:20.399> release 00:09:20.509 --> 00:09:20.519 align:start position:0% um I sort of look at this as a release 00:09:20.519 --> 00:09:22.610 align:start position:0% um I sort of look at this as a release test<00:09:20.940> so<00:09:21.420> it's<00:09:21.540> kind<00:09:21.839> of<00:09:21.899> one<00:09:22.140> of<00:09:22.260> the<00:09:22.380> last 00:09:22.610 --> 00:09:22.620 align:start position:0% test so it's kind of one of the last 00:09:22.620 --> 00:09:25.430 align:start position:0% test so it's kind of one of the last things<00:09:22.860> we<00:09:23.100> would<00:09:23.279> do<00:09:23.519> on<00:09:24.000> any<00:09:24.720> of<00:09:24.959> the<00:09:25.200> future 00:09:25.430 --> 00:09:25.440 align:start position:0% things we would do on any of the future 00:09:25.440 --> 00:09:27.470 align:start position:0% things we would do on any of the future Forks<00:09:25.980> that<00:09:26.040> we<00:09:26.220> have<00:09:26.339> it's<00:09:26.880> kind<00:09:27.120> of<00:09:27.180> when 00:09:27.470 --> 00:09:27.480 align:start position:0% Forks that we have it's kind of when 00:09:27.480 --> 00:09:29.690 align:start position:0% Forks that we have it's kind of when we're<00:09:27.899> almost<00:09:28.500> figuring<00:09:29.040> out<00:09:29.160> are<00:09:29.339> we<00:09:29.519> ready 00:09:29.690 --> 00:09:29.700 align:start position:0% we're almost figuring out are we ready 00:09:29.700 --> 00:09:31.430 align:start position:0% we're almost figuring out are we ready to<00:09:29.940> go<00:09:30.060> ahead<00:09:30.300> with<00:09:30.480> this<00:09:30.600> are<00:09:30.899> we<00:09:31.080> ready<00:09:31.200> to 00:09:31.430 --> 00:09:31.440 align:start position:0% to go ahead with this are we ready to 00:09:31.440 --> 00:09:33.350 align:start position:0% to go ahead with this are we ready to move<00:09:31.620> forward<00:09:31.860> with<00:09:32.279> with<00:09:32.640> committing<00:09:33.180> to 00:09:33.350 --> 00:09:33.360 align:start position:0% move forward with with committing to 00:09:33.360 --> 00:09:35.449 align:start position:0% move forward with with committing to this<00:09:33.480> Fork<00:09:33.899> is<00:09:34.380> there<00:09:34.500> any<00:09:34.680> unknowns<00:09:35.220> that<00:09:35.339> we 00:09:35.449 --> 00:09:35.459 align:start position:0% this Fork is there any unknowns that we 00:09:35.459 --> 00:09:38.630 align:start position:0% this Fork is there any unknowns that we don't<00:09:35.580> know<00:09:35.700> yet<00:09:35.959> and<00:09:36.959> then<00:09:37.320> we<00:09:37.800> have<00:09:37.980> fuzzles 00:09:38.630 --> 00:09:38.640 align:start position:0% don't know yet and then we have fuzzles 00:09:38.640 --> 00:09:40.970 align:start position:0% don't know yet and then we have fuzzles and<00:09:39.180> in<00:09:39.540> external<00:09:40.080> organization<00:09:40.740> called 00:09:40.970 --> 00:09:40.980 align:start position:0% and in external organization called 00:09:40.980 --> 00:09:44.210 align:start position:0% and in external organization called antithesis<00:09:41.700> so<00:09:42.480> antithesis<00:09:43.140> is<00:09:43.320> a 00:09:44.210 --> 00:09:44.220 align:start position:0% antithesis so antithesis is a 00:09:44.220 --> 00:09:46.370 align:start position:0% antithesis so antithesis is a deterministic<00:09:44.880> hypervisor<00:09:45.600> that<00:09:46.019> allows<00:09:46.320> us 00:09:46.370 --> 00:09:46.380 align:start position:0% deterministic hypervisor that allows us 00:09:46.380 --> 00:09:49.130 align:start position:0% deterministic hypervisor that allows us to<00:09:46.680> perform<00:09:46.860> Network<00:09:47.519> splits<00:09:48.120> packet<00:09:48.779> loss 00:09:49.130 --> 00:09:49.140 align:start position:0% to perform Network splits packet loss 00:09:49.140 --> 00:09:51.949 align:start position:0% to perform Network splits packet loss all<00:09:49.680> sorts<00:09:49.980> of<00:09:50.040> really<00:09:50.399> weird<00:09:50.640> edge<00:09:50.940> cases 00:09:51.949 --> 00:09:51.959 align:start position:0% all sorts of really weird edge cases 00:09:51.959 --> 00:09:54.230 align:start position:0% all sorts of really weird edge cases we<00:09:52.560> don't<00:09:52.740> necessarily<00:09:53.399> expect<00:09:53.760> the<00:09:54.120> network 00:09:54.230 --> 00:09:54.240 align:start position:0% we don't necessarily expect the network 00:09:54.240 --> 00:09:56.810 align:start position:0% we don't necessarily expect the network to<00:09:54.660> be<00:09:54.779> put<00:09:54.959> in<00:09:55.140> these<00:09:55.380> edge<00:09:55.560> cases<00:09:55.980> but<00:09:56.519> if 00:09:56.810 --> 00:09:56.820 align:start position:0% to be put in these edge cases but if 00:09:56.820 --> 00:09:58.310 align:start position:0% to be put in these edge cases but if they<00:09:56.940> are<00:09:57.120> we<00:09:57.480> know<00:09:57.600> that<00:09:57.779> the<00:09:57.899> clients<00:09:58.200> can 00:09:58.310 --> 00:09:58.320 align:start position:0% they are we know that the clients can 00:09:58.320 --> 00:10:01.370 align:start position:0% they are we know that the clients can handle<00:09:58.620> it<00:09:59.180> on<00:10:00.180> the<00:10:00.300> right<00:10:00.420> side<00:10:00.660> you<00:10:01.260> could 00:10:01.370 --> 00:10:01.380 align:start position:0% handle it on the right side you could 00:10:01.380 --> 00:10:03.110 align:start position:0% handle it on the right side you could you<00:10:01.680> can't<00:10:01.740> even<00:10:01.920> actually<00:10:02.160> see<00:10:02.459> it<00:10:02.640> but<00:10:02.880> each 00:10:03.110 --> 00:10:03.120 align:start position:0% you can't even actually see it but each 00:10:03.120 --> 00:10:06.470 align:start position:0% you can't even actually see it but each of<00:10:03.300> those<00:10:03.420> is<00:10:03.660> a<00:10:03.899> 256<00:10:04.860> thread<00:10:05.339> machine<00:10:05.640> we<00:10:06.360> have 00:10:06.470 --> 00:10:06.480 align:start position:0% of those is a 256 thread machine we have 00:10:06.480 --> 00:10:08.990 align:start position:0% of those is a 256 thread machine we have three<00:10:06.660> of<00:10:06.839> them<00:10:06.959> all<00:10:07.320> running<00:10:07.560> fuzzles<00:10:08.160> it<00:10:08.880> was 00:10:08.990 --> 00:10:09.000 align:start position:0% three of them all running fuzzles it was 00:10:09.000 --> 00:10:11.150 align:start position:0% three of them all running fuzzles it was insane<00:10:09.420> we<00:10:09.600> had<00:10:09.839> way<00:10:10.140> more<00:10:10.320> uh<00:10:10.800> I've<00:10:10.980> never 00:10:11.150 --> 00:10:11.160 align:start position:0% insane we had way more uh I've never 00:10:11.160 --> 00:10:13.009 align:start position:0% insane we had way more uh I've never seen<00:10:11.339> that<00:10:11.519> much<00:10:11.640> compute<00:10:12.060> in<00:10:12.180> my<00:10:12.300> life<00:10:12.480> we 00:10:13.009 --> 00:10:13.019 align:start position:0% seen that much compute in my life we 00:10:13.019 --> 00:10:16.730 align:start position:0% seen that much compute in my life we actually<00:10:13.260> had<00:10:14.300> the<00:10:15.300> IBM<00:10:15.720> data<00:10:16.140> center<00:10:16.260> go<00:10:16.560> out 00:10:16.730 --> 00:10:16.740 align:start position:0% actually had the IBM data center go out 00:10:16.740 --> 00:10:18.350 align:start position:0% actually had the IBM data center go out and<00:10:16.860> buy<00:10:16.980> more<00:10:17.160> CPUs<00:10:17.580> because<00:10:17.820> we<00:10:18.000> bought<00:10:18.120> up 00:10:18.350 --> 00:10:18.360 align:start position:0% and buy more CPUs because we bought up 00:10:18.360 --> 00:10:20.150 align:start position:0% and buy more CPUs because we bought up all<00:10:18.480> of<00:10:18.660> them 00:10:20.150 --> 00:10:20.160 align:start position:0% all of them 00:10:20.160 --> 00:10:22.730 align:start position:0% all of them um<00:10:20.279> yeah<00:10:20.640> various<00:10:21.420> fuzzles<00:10:21.959> various<00:10:22.380> teams 00:10:22.730 --> 00:10:22.740 align:start position:0% um yeah various fuzzles various teams 00:10:22.740 --> 00:10:25.490 align:start position:0% um yeah various fuzzles various teams running<00:10:22.920> out<00:10:23.160> all<00:10:23.399> of<00:10:23.519> them<00:10:23.640> uh<00:10:24.300> super<00:10:24.540> cool<00:10:24.779> we 00:10:25.490 --> 00:10:25.500 align:start position:0% running out all of them uh super cool we 00:10:25.500 --> 00:10:28.190 align:start position:0% running out all of them uh super cool we found<00:10:25.800> a<00:10:26.100> ton<00:10:26.279> of<00:10:26.399> bugs<00:10:26.760> referred<00:10:27.600> to<00:10:27.720> marius's 00:10:28.190 --> 00:10:28.200 align:start position:0% found a ton of bugs referred to marius's 00:10:28.200 --> 00:10:29.449 align:start position:0% found a ton of bugs referred to marius's talk<00:10:28.380> if<00:10:28.560> you<00:10:28.680> want<00:10:28.740> to<00:10:28.860> know<00:10:28.920> what<00:10:29.220> we 00:10:29.449 --> 00:10:29.459 align:start position:0% talk if you want to know what we 00:10:29.459 --> 00:10:31.670 align:start position:0% talk if you want to know what we actually<00:10:29.700> found<00:10:29.940> there<00:10:30.240> and<00:10:30.899> we<00:10:31.200> hope<00:10:31.440> that 00:10:31.670 --> 00:10:31.680 align:start position:0% actually found there and we hope that 00:10:31.680 --> 00:10:34.250 align:start position:0% actually found there and we hope that some<00:10:31.980> of<00:10:32.100> those<00:10:32.220> bugs<00:10:32.760> change<00:10:33.180> the<00:10:33.480> spec<00:10:33.660> to 00:10:34.250 --> 00:10:34.260 align:start position:0% some of those bugs change the spec to 00:10:34.260 --> 00:10:35.990 align:start position:0% some of those bugs change the spec to make<00:10:34.500> it<00:10:34.680> a<00:10:34.800> lot<00:10:34.860> more<00:10:35.040> stable<00:10:35.279> or<00:10:35.700> sometimes 00:10:35.990 --> 00:10:36.000 align:start position:0% make it a lot more stable or sometimes 00:10:36.000 --> 00:10:39.050 align:start position:0% make it a lot more stable or sometimes than<00:10:36.180> implementation<00:10:36.839> issue 00:10:39.050 --> 00:10:39.060 align:start position:0% than implementation issue 00:10:39.060 --> 00:10:41.150 align:start position:0% than implementation issue so<00:10:39.600> to<00:10:39.720> give<00:10:39.899> you<00:10:40.019> a<00:10:40.200> brief<00:10:40.440> idea<00:10:40.740> on<00:10:41.040> the 00:10:41.150 --> 00:10:41.160 align:start position:0% so to give you a brief idea on the 00:10:41.160 --> 00:10:43.370 align:start position:0% so to give you a brief idea on the testing<00:10:41.519> life<00:10:41.760> cycle<00:10:42.000> let<00:10:42.779> me<00:10:42.899> tell<00:10:43.019> you<00:10:43.140> it's 00:10:43.370 --> 00:10:43.380 align:start position:0% testing life cycle let me tell you it's 00:10:43.380 --> 00:10:45.710 align:start position:0% testing life cycle let me tell you it's never<00:10:43.620> that<00:10:43.920> clean<00:10:44.160> but<00:10:45.000> that's<00:10:45.180> what<00:10:45.420> we<00:10:45.540> want 00:10:45.710 --> 00:10:45.720 align:start position:0% never that clean but that's what we want 00:10:45.720 --> 00:10:47.930 align:start position:0% never that clean but that's what we want to<00:10:45.899> hope<00:10:46.079> to<00:10:46.260> achieve<00:10:46.740> so<00:10:47.339> you<00:10:47.519> have<00:10:47.700> the 00:10:47.930 --> 00:10:47.940 align:start position:0% to hope to achieve so you have the 00:10:47.940 --> 00:10:49.970 align:start position:0% to hope to achieve so you have the client<00:10:48.120> releases<00:10:48.600> happening<00:10:49.079> and<00:10:49.560> once<00:10:49.860> the 00:10:49.970 --> 00:10:49.980 align:start position:0% client releases happening and once the 00:10:49.980 --> 00:10:52.009 align:start position:0% client releases happening and once the client<00:10:50.160> releases<00:10:50.579> happen<00:10:50.880> they<00:10:51.540> go<00:10:51.660> into<00:10:51.779> the 00:10:52.009 --> 00:10:52.019 align:start position:0% client releases happen they go into the 00:10:52.019 --> 00:10:54.230 align:start position:0% client releases happen they go into the integration<00:10:52.440> tests<00:10:52.980> so<00:10:53.279> we<00:10:53.519> make<00:10:53.700> sure<00:10:53.880> that 00:10:54.230 --> 00:10:54.240 align:start position:0% integration tests so we make sure that 00:10:54.240 --> 00:10:56.449 align:start position:0% integration tests so we make sure that testnets<00:10:54.899> can<00:10:55.079> be<00:10:55.200> run<00:10:55.380> that<00:10:55.920> integration 00:10:56.449 --> 00:10:56.459 align:start position:0% testnets can be run that integration 00:10:56.459 --> 00:10:59.210 align:start position:0% testnets can be run that integration tests<00:10:56.880> work<00:10:57.060> fine<00:10:57.360> and<00:10:58.260> once<00:10:58.560> that's<00:10:58.680> done<00:10:58.920> we 00:10:59.210 --> 00:10:59.220 align:start position:0% tests work fine and once that's done we 00:10:59.220 --> 00:11:01.970 align:start position:0% tests work fine and once that's done we move<00:10:59.399> on<00:10:59.579> to<00:10:59.760> test<00:11:00.480> Nets<00:11:01.019> and<00:11:01.380> then<00:11:01.500> we<00:11:01.680> move<00:11:01.800> on 00:11:01.970 --> 00:11:01.980 align:start position:0% move on to test Nets and then we move on 00:11:01.980 --> 00:11:05.569 align:start position:0% move on to test Nets and then we move on to<00:11:02.160> stress<00:11:02.459> tests<00:11:02.880> and<00:11:03.839> we<00:11:04.320> push<00:11:04.800> whatever<00:11:05.160> we 00:11:05.569 --> 00:11:05.579 align:start position:0% to stress tests and we push whatever we 00:11:05.579 --> 00:11:07.630 align:start position:0% to stress tests and we push whatever we find<00:11:05.700> on<00:11:06.060> these<00:11:06.240> stress<00:11:06.540> tests<00:11:06.959> onto 00:11:07.630 --> 00:11:07.640 align:start position:0% find on these stress tests onto 00:11:07.640 --> 00:11:10.730 align:start position:0% find on these stress tests onto specifications<00:11:08.640> we<00:11:09.600> do<00:11:09.839> regression<00:11:10.380> tests 00:11:10.730 --> 00:11:10.740 align:start position:0% specifications we do regression tests 00:11:10.740 --> 00:11:12.530 align:start position:0% specifications we do regression tests and<00:11:10.920> then<00:11:10.980> we<00:11:11.160> do<00:11:11.279> fuzzing<00:11:11.700> and<00:11:12.240> hopefully 00:11:12.530 --> 00:11:12.540 align:start position:0% and then we do fuzzing and hopefully 00:11:12.540 --> 00:11:14.269 align:start position:0% and then we do fuzzing and hopefully whatever<00:11:12.839> we<00:11:13.140> find<00:11:13.380> in<00:11:13.620> the<00:11:13.800> last<00:11:13.920> couple<00:11:14.100> of 00:11:14.269 --> 00:11:14.279 align:start position:0% whatever we find in the last couple of 00:11:14.279 --> 00:11:16.670 align:start position:0% whatever we find in the last couple of stages<00:11:14.519> go<00:11:14.940> back<00:11:15.120> into<00:11:15.300> client<00:11:15.600> releases<00:11:16.019> so 00:11:16.670 --> 00:11:16.680 align:start position:0% stages go back into client releases so 00:11:16.680 --> 00:11:19.250 align:start position:0% stages go back into client releases so that's<00:11:17.040> a<00:11:17.459> kind<00:11:17.940> of<00:11:18.060> a<00:11:18.240> nice<00:11:18.420> way<00:11:18.600> to<00:11:18.779> look<00:11:18.959> at<00:11:19.079> a 00:11:19.250 --> 00:11:19.260 align:start position:0% that's a kind of a nice way to look at a 00:11:19.260 --> 00:11:20.930 align:start position:0% that's a kind of a nice way to look at a full<00:11:19.500> life<00:11:19.800> cycle<00:11:20.040> of<00:11:20.220> how<00:11:20.399> testing<00:11:20.760> would 00:11:20.930 --> 00:11:20.940 align:start position:0% full life cycle of how testing would 00:11:20.940 --> 00:11:23.269 align:start position:0% full life cycle of how testing would work<00:11:21.120> we're<00:11:21.959> hoping<00:11:22.260> to<00:11:22.380> adopt<00:11:22.800> the<00:11:22.860> same<00:11:22.980> life 00:11:23.269 --> 00:11:23.279 align:start position:0% work we're hoping to adopt the same life 00:11:23.279 --> 00:11:25.190 align:start position:0% work we're hoping to adopt the same life cycle<00:11:23.519> for<00:11:23.880> future<00:11:24.060> test<00:11:24.360> Nets<00:11:24.720> maybe<00:11:24.899> we 00:11:25.190 --> 00:11:25.200 align:start position:0% cycle for future test Nets maybe we 00:11:25.200 --> 00:11:26.990 align:start position:0% cycle for future test Nets maybe we moved<00:11:25.560> around<00:11:25.800> a<00:11:26.040> tool<00:11:26.339> here<00:11:26.459> or<00:11:26.640> there<00:11:26.820> but 00:11:26.990 --> 00:11:27.000 align:start position:0% moved around a tool here or there but 00:11:27.000 --> 00:11:30.250 align:start position:0% moved around a tool here or there but that's<00:11:27.180> the<00:11:27.360> general<00:11:27.480> idea 00:11:30.250 --> 00:11:30.260 align:start position:0% 00:11:30.260 --> 00:11:36.650 align:start position:0% and<00:11:31.260> the<00:11:31.500> end<00:11:31.620> game<00:11:31.860> what<00:11:32.279> did<00:11:32.459> we<00:11:32.640> actually<00:11:32.940> do 00:11:36.650 --> 00:11:36.660 align:start position:0% 00:11:36.660 --> 00:11:38.569 align:start position:0% um<00:11:36.779> it<00:11:37.079> was<00:11:37.140> really<00:11:37.440> hard<00:11:37.680> to<00:11:37.860> find<00:11:38.040> a<00:11:38.279> graph 00:11:38.569 --> 00:11:38.579 align:start position:0% um it was really hard to find a graph 00:11:38.579 --> 00:11:40.430 align:start position:0% um it was really hard to find a graph that<00:11:38.940> actually<00:11:39.060> fit<00:11:39.420> all<00:11:39.660> the<00:11:39.779> test<00:11:39.899> Nets<00:11:40.380> we 00:11:40.430 --> 00:11:40.440 align:start position:0% that actually fit all the test Nets we 00:11:40.440 --> 00:11:42.110 align:start position:0% that actually fit all the test Nets we had<00:11:40.620> that's<00:11:40.980> how<00:11:41.220> many 00:11:42.110 --> 00:11:42.120 align:start position:0% had that's how many 00:11:42.120 --> 00:11:44.750 align:start position:0% had that's how many um<00:11:42.180> so<00:11:42.420> we<00:11:42.600> had<00:11:42.839> we<00:11:43.320> started<00:11:43.680> off<00:11:43.920> in<00:11:44.339> April<00:11:44.640> of 00:11:44.750 --> 00:11:44.760 align:start position:0% um so we had we started off in April of 00:11:44.760 --> 00:11:47.569 align:start position:0% um so we had we started off in April of 2021<00:11:45.300> with<00:11:45.540> ryanism<00:11:46.079> and<00:11:46.680> since<00:11:46.920> then<00:11:47.100> we've 00:11:47.569 --> 00:11:47.579 align:start position:0% 2021 with ryanism and since then we've 00:11:47.579 --> 00:11:48.590 align:start position:0% 2021 with ryanism and since then we've had 00:11:48.590 --> 00:11:48.600 align:start position:0% had 00:11:48.600 --> 00:11:51.110 align:start position:0% had four<00:11:49.140> public<00:11:49.500> test<00:11:49.860> Nets<00:11:50.279> that<00:11:50.519> anyone<00:11:50.820> could 00:11:51.110 --> 00:11:51.120 align:start position:0% four public test Nets that anyone could 00:11:51.120 --> 00:11:53.210 align:start position:0% four public test Nets that anyone could permissionlessly<00:11:51.779> join<00:11:52.200> into<00:11:52.320> we<00:11:52.860> had<00:11:53.040> six 00:11:53.210 --> 00:11:53.220 align:start position:0% permissionlessly join into we had six 00:11:53.220 --> 00:11:55.009 align:start position:0% permissionlessly join into we had six devnets<00:11:53.760> meant<00:11:54.060> for<00:11:54.120> all<00:11:54.240> the<00:11:54.360> client<00:11:54.600> teams 00:11:55.009 --> 00:11:55.019 align:start position:0% devnets meant for all the client teams 00:11:55.019 --> 00:11:56.930 align:start position:0% devnets meant for all the client teams we<00:11:55.500> had 00:11:56.930 --> 00:11:56.940 align:start position:0% we had 00:11:56.940 --> 00:11:59.329 align:start position:0% we had um<00:11:57.060> five<00:11:57.420> Gully<00:11:57.899> Shadow<00:11:58.200> Fox<00:11:58.440> and<00:11:58.860> in<00:11:59.040> the<00:11:59.220> end 00:11:59.329 --> 00:11:59.339 align:start position:0% um five Gully Shadow Fox and in the end 00:11:59.339 --> 00:12:02.150 align:start position:0% um five Gully Shadow Fox and in the end 13<00:11:59.700> midnight<00:12:00.240> Shadow<00:12:00.540> Fox<00:12:00.839> and<00:12:01.500> after<00:12:01.680> all<00:12:01.980> of 00:12:02.150 --> 00:12:02.160 align:start position:0% 13 midnight Shadow Fox and after all of 00:12:02.160 --> 00:12:05.509 align:start position:0% 13 midnight Shadow Fox and after all of this<00:12:02.339> we<00:12:03.120> had<00:12:03.360> three<00:12:03.779> test<00:12:04.079> Netflix<00:12:04.380> and<00:12:05.339> only 00:12:05.509 --> 00:12:05.519 align:start position:0% this we had three test Netflix and only 00:12:05.519 --> 00:12:09.350 align:start position:0% this we had three test Netflix and only then<00:12:05.820> we<00:12:06.060> hit<00:12:06.540> mainnet<00:12:07.100> so<00:12:08.100> the<00:12:08.399> whole<00:12:08.700> number 00:12:09.350 --> 00:12:09.360 align:start position:0% then we hit mainnet so the whole number 00:12:09.360 --> 00:12:11.690 align:start position:0% then we hit mainnet so the whole number of<00:12:09.600> just<00:12:09.779> testing<00:12:10.260> hours<00:12:10.560> in<00:12:11.040> the<00:12:11.220> merge<00:12:11.519> is 00:12:11.690 --> 00:12:11.700 align:start position:0% of just testing hours in the merge is 00:12:11.700 --> 00:12:15.050 align:start position:0% of just testing hours in the merge is insane<00:12:12.360> I'm<00:12:12.779> quite<00:12:13.260> sure<00:12:13.560> if<00:12:14.220> we<00:12:14.399> added<00:12:14.760> it<00:12:14.880> all 00:12:15.050 --> 00:12:15.060 align:start position:0% insane I'm quite sure if we added it all 00:12:15.060 --> 00:12:16.610 align:start position:0% insane I'm quite sure if we added it all up<00:12:15.180> it<00:12:15.360> would<00:12:15.480> be<00:12:15.600> at<00:12:15.779> least<00:12:15.899> a<00:12:16.079> couple<00:12:16.200> ten 00:12:16.610 --> 00:12:16.620 align:start position:0% up it would be at least a couple ten 00:12:16.620 --> 00:12:18.889 align:start position:0% up it would be at least a couple ten thousand<00:12:16.920> hours<00:12:17.100> put<00:12:17.399> into<00:12:17.579> this 00:12:18.889 --> 00:12:18.899 align:start position:0% thousand hours put into this 00:12:18.899 --> 00:12:21.470 align:start position:0% thousand hours put into this um<00:12:19.500> so 00:12:21.470 --> 00:12:21.480 align:start position:0% um so 00:12:21.480 --> 00:12:23.410 align:start position:0% um so what<00:12:22.260> didn't<00:12:22.440> we<00:12:22.620> find 00:12:23.410 --> 00:12:23.420 align:start position:0% what didn't we find 00:12:23.420 --> 00:12:25.490 align:start position:0% what didn't we find this<00:12:24.420> is<00:12:24.540> a<00:12:24.720> really<00:12:24.839> interesting<00:12:25.260> part 00:12:25.490 --> 00:12:25.500 align:start position:0% this is a really interesting part 00:12:25.500 --> 00:12:27.230 align:start position:0% this is a really interesting part because<00:12:25.740> even<00:12:26.100> though<00:12:26.279> we<00:12:26.519> have<00:12:26.640> all<00:12:26.880> of<00:12:27.000> these 00:12:27.230 --> 00:12:27.240 align:start position:0% because even though we have all of these 00:12:27.240 --> 00:12:28.910 align:start position:0% because even though we have all of these Cool<00:12:27.420> Tools<00:12:27.839> there's<00:12:28.140> still<00:12:28.440> always<00:12:28.560> going<00:12:28.800> to 00:12:28.910 --> 00:12:28.920 align:start position:0% Cool Tools there's still always going to 00:12:28.920 --> 00:12:30.790 align:start position:0% Cool Tools there's still always going to be<00:12:28.980> something<00:12:29.160> we<00:12:29.399> didn't<00:12:29.579> find<00:12:29.760> this<00:12:30.420> 99 00:12:30.790 --> 00:12:30.800 align:start position:0% be something we didn't find this 99 00:12:30.800 --> 00:12:33.829 align:start position:0% be something we didn't find this 99 participation<00:12:31.800> 98<00:12:32.339> participation<00:12:33.240> or<00:12:33.600> great 00:12:33.829 --> 00:12:33.839 align:start position:0% participation 98 participation or great 00:12:33.839 --> 00:12:35.569 align:start position:0% participation 98 participation or great blocks<00:12:34.140> being<00:12:34.320> produced<00:12:34.740> awesome<00:12:34.920> but<00:12:35.339> I<00:12:35.459> want 00:12:35.569 --> 00:12:35.579 align:start position:0% blocks being produced awesome but I want 00:12:35.579 --> 00:12:37.910 align:start position:0% blocks being produced awesome but I want to<00:12:35.700> know<00:12:35.820> what<00:12:35.940> we<00:12:36.120> still<00:12:36.360> didn't<00:12:36.600> find<00:12:36.920> so 00:12:37.910 --> 00:12:37.920 align:start position:0% to know what we still didn't find so 00:12:37.920 --> 00:12:39.590 align:start position:0% to know what we still didn't find so first<00:12:38.279> one 00:12:39.590 --> 00:12:39.600 align:start position:0% first one 00:12:39.600 --> 00:12:42.710 align:start position:0% first one um<00:12:39.720> we<00:12:40.320> had<00:12:40.500> in-memory<00:12:41.279> databases<00:12:42.060> that<00:12:42.540> were 00:12:42.710 --> 00:12:42.720 align:start position:0% um we had in-memory databases that were 00:12:42.720 --> 00:12:45.110 align:start position:0% um we had in-memory databases that were too<00:12:42.959> low<00:12:43.200> to<00:12:43.380> process<00:12:43.620> main<00:12:43.860> net<00:12:44.100> blocks<00:12:44.519> it 00:12:45.110 --> 00:12:45.120 align:start position:0% too low to process main net blocks it 00:12:45.120 --> 00:12:46.910 align:start position:0% too low to process main net blocks it just<00:12:45.240> so<00:12:45.480> happened<00:12:45.660> that<00:12:46.079> we<00:12:46.200> did<00:12:46.380> too<00:12:46.620> good<00:12:46.800> a 00:12:46.910 --> 00:12:46.920 align:start position:0% just so happened that we did too good a 00:12:46.920 --> 00:12:49.310 align:start position:0% just so happened that we did too good a job<00:12:47.100> of<00:12:47.279> deciding<00:12:47.700> which<00:12:48.060> machines<00:12:48.779> run<00:12:49.139> our 00:12:49.310 --> 00:12:49.320 align:start position:0% job of deciding which machines run our 00:12:49.320 --> 00:12:51.949 align:start position:0% job of deciding which machines run our test<00:12:49.500> Nets<00:12:49.980> which<00:12:50.579> means<00:12:51.000> we<00:12:51.420> didn't<00:12:51.540> have<00:12:51.720> any 00:12:51.949 --> 00:12:51.959 align:start position:0% test Nets which means we didn't have any 00:12:51.959 --> 00:12:54.590 align:start position:0% test Nets which means we didn't have any resource<00:12:52.440> constraints<00:12:52.920> and<00:12:53.880> we<00:12:54.180> kind<00:12:54.420> of 00:12:54.590 --> 00:12:54.600 align:start position:0% resource constraints and we kind of 00:12:54.600 --> 00:12:57.050 align:start position:0% resource constraints and we kind of missed<00:12:55.079> the<00:12:55.260> people<00:12:55.380> running<00:12:55.680> nodes<00:12:56.100> on<00:12:56.279> 8<00:12:56.700> gig 00:12:57.050 --> 00:12:57.060 align:start position:0% missed the people running nodes on 8 gig 00:12:57.060 --> 00:12:59.930 align:start position:0% missed the people running nodes on 8 gig ram<00:12:57.360> machines<00:12:57.959> or<00:12:58.500> people<00:12:58.800> running<00:12:59.100> on<00:12:59.399> 16<00:12:59.639> gig 00:12:59.930 --> 00:12:59.940 align:start position:0% ram machines or people running on 16 gig 00:12:59.940 --> 00:13:01.970 align:start position:0% ram machines or people running on 16 gig ram<00:13:00.240> machines<00:13:00.660> we<00:13:01.200> didn't<00:13:01.380> account<00:13:01.620> for<00:13:01.860> that 00:13:01.970 --> 00:13:01.980 align:start position:0% ram machines we didn't account for that 00:13:01.980 --> 00:13:04.370 align:start position:0% ram machines we didn't account for that or<00:13:02.160> we<00:13:02.339> didn't<00:13:02.519> account<00:13:02.820> for<00:13:03.240> older<00:13:03.839> versions 00:13:04.370 --> 00:13:04.380 align:start position:0% or we didn't account for older versions 00:13:04.380 --> 00:13:07.910 align:start position:0% or we didn't account for older versions of<00:13:04.680> ram<00:13:04.920> being<00:13:05.220> used<00:13:05.459> whatever<00:13:05.880> it<00:13:06.240> is 00:13:07.910 --> 00:13:07.920 align:start position:0% of ram being used whatever it is 00:13:07.920 --> 00:13:09.410 align:start position:0% of ram being used whatever it is um<00:13:07.980> another<00:13:08.279> one<00:13:08.519> that<00:13:08.639> we<00:13:08.760> missed<00:13:09.060> is 00:13:09.410 --> 00:13:09.420 align:start position:0% um another one that we missed is 00:13:09.420 --> 00:13:12.170 align:start position:0% um another one that we missed is non-optimal<00:13:10.200> block<00:13:10.440> production 00:13:12.170 --> 00:13:12.180 align:start position:0% non-optimal block production 00:13:12.180 --> 00:13:14.269 align:start position:0% non-optimal block production um we<00:13:12.839> were<00:13:13.079> super<00:13:13.260> focused<00:13:13.680> on<00:13:13.800> making<00:13:14.100> sure 00:13:14.269 --> 00:13:14.279 align:start position:0% um we were super focused on making sure 00:13:14.279 --> 00:13:16.129 align:start position:0% um we were super focused on making sure that<00:13:14.459> we<00:13:14.639> didn't<00:13:14.760> see<00:13:15.000> any<00:13:15.360> zero<00:13:15.779> transaction 00:13:16.129 --> 00:13:16.139 align:start position:0% that we didn't see any zero transaction 00:13:16.139 --> 00:13:18.650 align:start position:0% that we didn't see any zero transaction blocks<00:13:16.560> on<00:13:16.680> the<00:13:16.800> network<00:13:17.000> we<00:13:18.000> didn't<00:13:18.120> compare 00:13:18.650 --> 00:13:18.660 align:start position:0% blocks on the network we didn't compare 00:13:18.660 --> 00:13:20.690 align:start position:0% blocks on the network we didn't compare that<00:13:18.959> to<00:13:19.200> what<00:13:19.440> the<00:13:19.680> optimal<00:13:20.100> blocks<00:13:20.459> on<00:13:20.579> the 00:13:20.690 --> 00:13:20.700 align:start position:0% that to what the optimal blocks on the 00:13:20.700 --> 00:13:22.730 align:start position:0% that to what the optimal blocks on the network<00:13:20.820> could<00:13:21.180> be<00:13:21.300> so<00:13:22.019> it<00:13:22.380> is<00:13:22.500> an 00:13:22.730 --> 00:13:22.740 align:start position:0% network could be so it is an 00:13:22.740 --> 00:13:25.190 align:start position:0% network could be so it is an optimization<00:13:23.399> problem<00:13:23.760> of<00:13:24.120> course<00:13:24.300> and<00:13:24.779> it<00:13:25.019> is 00:13:25.190 --> 00:13:25.200 align:start position:0% optimization problem of course and it is 00:13:25.200 --> 00:13:26.990 align:start position:0% optimization problem of course and it is an<00:13:25.320> awful<00:13:25.680> that<00:13:25.860> on<00:13:26.040> mainnet<00:13:26.459> we<00:13:26.579> have<00:13:26.760> some 00:13:26.990 --> 00:13:27.000 align:start position:0% an awful that on mainnet we have some 00:13:27.000 --> 00:13:28.970 align:start position:0% an awful that on mainnet we have some reduced<00:13:27.420> load<00:13:27.720> but<00:13:28.260> it<00:13:28.440> is<00:13:28.560> something<00:13:28.740> we 00:13:28.970 --> 00:13:28.980 align:start position:0% reduced load but it is something we 00:13:28.980 --> 00:13:30.290 align:start position:0% reduced load but it is something we missed<00:13:29.279> and<00:13:29.459> something<00:13:29.639> we<00:13:29.940> probably<00:13:30.120> should 00:13:30.290 --> 00:13:30.300 align:start position:0% missed and something we probably should 00:13:30.300 --> 00:13:32.750 align:start position:0% missed and something we probably should look<00:13:30.480> into<00:13:30.600> in<00:13:30.899> the<00:13:31.019> future 00:13:32.750 --> 00:13:32.760 align:start position:0% look into in the future 00:13:32.760 --> 00:13:35.449 align:start position:0% look into in the future um<00:13:32.880> the<00:13:33.420> next<00:13:33.540> one<00:13:33.779> there<00:13:34.740> was<00:13:34.920> a<00:13:35.160> really 00:13:35.449 --> 00:13:35.459 align:start position:0% um the next one there was a really 00:13:35.459 --> 00:13:37.490 align:start position:0% um the next one there was a really specific<00:13:35.940> way<00:13:36.480> in<00:13:36.779> which<00:13:36.959> the<00:13:37.200> terminal 00:13:37.490 --> 00:13:37.500 align:start position:0% specific way in which the terminal 00:13:37.500 --> 00:13:39.410 align:start position:0% specific way in which the terminal blocks<00:13:37.980> could<00:13:38.220> arrive<00:13:38.639> that<00:13:39.120> broke 00:13:39.410 --> 00:13:39.420 align:start position:0% blocks could arrive that broke 00:13:39.420 --> 00:13:42.110 align:start position:0% blocks could arrive that broke Netherland<00:13:39.899> and<00:13:40.860> it<00:13:41.160> broke<00:13:41.339> Netherland<00:13:41.820> by 00:13:42.110 --> 00:13:42.120 align:start position:0% Netherland and it broke Netherland by 00:13:42.120 --> 00:13:45.110 align:start position:0% Netherland and it broke Netherland by causing<00:13:42.480> missing<00:13:43.380> receipts<00:13:43.920> and<00:13:44.639> we<00:13:44.880> only 00:13:45.110 --> 00:13:45.120 align:start position:0% causing missing receipts and we only 00:13:45.120 --> 00:13:47.269 align:start position:0% causing missing receipts and we only noticed<00:13:45.660> that<00:13:45.899> issue<00:13:46.320> when<00:13:46.980> there<00:13:47.160> are 00:13:47.269 --> 00:13:47.279 align:start position:0% noticed that issue when there are 00:13:47.279 --> 00:13:50.329 align:start position:0% noticed that issue when there are deposits<00:13:47.820> being<00:13:47.940> made<00:13:48.200> so<00:13:49.200> we<00:13:49.740> completely 00:13:50.329 --> 00:13:50.339 align:start position:0% deposits being made so we completely 00:13:50.339 --> 00:13:53.090 align:start position:0% deposits being made so we completely missed<00:13:50.880> this<00:13:51.060> and<00:13:51.600> for<00:13:51.839> what<00:13:52.079> we<00:13:52.500> still<00:13:52.740> yet<00:13:52.980> to 00:13:53.090 --> 00:13:53.100 align:start position:0% missed this and for what we still yet to 00:13:53.100 --> 00:13:55.129 align:start position:0% missed this and for what we still yet to figure<00:13:53.220> out<00:13:53.399> why<00:13:53.700> but<00:13:54.180> this<00:13:54.420> is<00:13:54.540> mainly<00:13:54.899> an 00:13:55.129 --> 00:13:55.139 align:start position:0% figure out why but this is mainly an 00:13:55.139 --> 00:13:57.230 align:start position:0% figure out why but this is mainly an issue<00:13:55.380> for<00:13:55.620> lodestar<00:13:56.220> never<00:13:56.399> mind<00:13:56.700> and<00:13:57.060> no 00:13:57.230 --> 00:13:57.240 align:start position:0% issue for lodestar never mind and no 00:13:57.240 --> 00:13:59.090 align:start position:0% issue for lodestar never mind and no other<00:13:57.360> combination<00:13:57.959> or<00:13:58.500> at<00:13:58.680> least<00:13:58.800> we<00:13:58.980> didn't 00:13:59.090 --> 00:13:59.100 align:start position:0% other combination or at least we didn't 00:13:59.100 --> 00:14:01.970 align:start position:0% other combination or at least we didn't get<00:13:59.339> the<00:14:00.060> uh<00:14:00.660> Memo<00:14:01.019> from<00:14:01.200> other<00:14:01.440> breaking 00:14:01.970 --> 00:14:01.980 align:start position:0% get the uh Memo from other breaking 00:14:01.980 --> 00:14:04.069 align:start position:0% get the uh Memo from other breaking combinations<00:14:02.399> so<00:14:02.820> lots<00:14:03.420> of<00:14:03.540> another<00:14:03.660> mind 00:14:04.069 --> 00:14:04.079 align:start position:0% combinations so lots of another mind 00:14:04.079 --> 00:14:05.930 align:start position:0% combinations so lots of another mind figure<00:14:04.380> that<00:14:04.680> out<00:14:04.800> on<00:14:05.040> day<00:14:05.160> one<00:14:05.339> of<00:14:05.519> the<00:14:05.639> merge 00:14:05.930 --> 00:14:05.940 align:start position:0% figure that out on day one of the merge 00:14:05.940 --> 00:14:08.150 align:start position:0% figure that out on day one of the merge and<00:14:06.600> it<00:14:07.019> I<00:14:07.139> think<00:14:07.260> it<00:14:07.380> was<00:14:07.500> passed<00:14:07.800> like<00:14:07.920> a<00:14:07.980> day 00:14:08.150 --> 00:14:08.160 align:start position:0% and it I think it was passed like a day 00:14:08.160 --> 00:14:10.310 align:start position:0% and it I think it was passed like a day later 00:14:10.310 --> 00:14:10.320 align:start position:0% later 00:14:10.320 --> 00:14:12.050 align:start position:0% later um<00:14:10.440> another<00:14:10.740> one<00:14:10.980> that<00:14:11.220> we<00:14:11.399> didn't<00:14:11.579> think<00:14:11.820> of 00:14:12.050 --> 00:14:12.060 align:start position:0% um another one that we didn't think of 00:14:12.060 --> 00:14:14.569 align:start position:0% um another one that we didn't think of all<00:14:12.480> of<00:14:12.600> the<00:14:12.720> Shadow<00:14:12.899> Fox<00:14:13.200> didn't<00:14:14.100> have<00:14:14.339> any 00:14:14.569 --> 00:14:14.579 align:start position:0% all of the Shadow Fox didn't have any 00:14:14.579 --> 00:14:16.610 align:start position:0% all of the Shadow Fox didn't have any nodes<00:14:14.880> syncing<00:14:15.300> up<00:14:15.420> to<00:14:15.540> the<00:14:15.720> network<00:14:15.899> after 00:14:16.610 --> 00:14:16.620 align:start position:0% nodes syncing up to the network after 00:14:16.620 --> 00:14:18.410 align:start position:0% nodes syncing up to the network after the<00:14:16.920> shadowfuck<00:14:17.399> was<00:14:17.639> done 00:14:18.410 --> 00:14:18.420 align:start position:0% the shadowfuck was done 00:14:18.420 --> 00:14:21.110 align:start position:0% the shadowfuck was done which<00:14:18.899> means<00:14:19.320> they<00:14:19.680> weren't<00:14:19.920> serving<00:14:20.639> sync 00:14:21.110 --> 00:14:21.120 align:start position:0% which means they weren't serving sync 00:14:21.120 --> 00:14:22.550 align:start position:0% which means they weren't serving sync data<00:14:21.420> and<00:14:21.779> all<00:14:21.959> they<00:14:22.079> were<00:14:22.260> doing<00:14:22.380> were 00:14:22.550 --> 00:14:22.560 align:start position:0% data and all they were doing were 00:14:22.560 --> 00:14:24.170 align:start position:0% data and all they were doing were keeping<00:14:22.920> up<00:14:22.980> with<00:14:23.160> the<00:14:23.279> chain<00:14:23.459> which<00:14:23.820> is<00:14:23.940> great 00:14:24.170 --> 00:14:24.180 align:start position:0% keeping up with the chain which is great 00:14:24.180 --> 00:14:27.590 align:start position:0% keeping up with the chain which is great but<00:14:25.139> constantly<00:14:25.800> thinking<00:14:26.279> on<00:14:26.579> minet<00:14:27.180> also 00:14:27.590 --> 00:14:27.600 align:start position:0% but constantly thinking on minet also 00:14:27.600 --> 00:14:29.389 align:start position:0% but constantly thinking on minet also adds<00:14:27.899> load<00:14:28.200> on<00:14:28.320> the<00:14:28.500> machine<00:14:28.620> so<00:14:28.980> we<00:14:29.160> want 00:14:29.389 --> 00:14:29.399 align:start position:0% adds load on the machine so we want 00:14:29.399 --> 00:14:31.670 align:start position:0% adds load on the machine so we want accurately<00:14:30.000> simulating<00:14:30.540> that<00:14:30.839> so 00:14:31.670 --> 00:14:31.680 align:start position:0% accurately simulating that so 00:14:31.680 --> 00:14:33.470 align:start position:0% accurately simulating that so potentially<00:14:32.100> on<00:14:32.339> future<00:14:32.519> shadowfox<00:14:33.180> we're 00:14:33.470 --> 00:14:33.480 align:start position:0% potentially on future shadowfox we're 00:14:33.480 --> 00:14:34.970 align:start position:0% potentially on future shadowfox we're gonna<00:14:33.660> have<00:14:33.839> to<00:14:33.959> add<00:14:34.200> a<00:14:34.440> bunch<00:14:34.560> of<00:14:34.680> syncing 00:14:34.970 --> 00:14:34.980 align:start position:0% gonna have to add a bunch of syncing 00:14:34.980 --> 00:14:37.250 align:start position:0% gonna have to add a bunch of syncing nodes<00:14:35.220> that<00:14:35.579> start<00:14:35.760> up<00:14:35.940> later<00:14:36.180> on<00:14:36.420> to<00:14:36.779> see<00:14:36.959> what 00:14:37.250 --> 00:14:37.260 align:start position:0% nodes that start up later on to see what 00:14:37.260 --> 00:14:38.629 align:start position:0% nodes that start up later on to see what could<00:14:37.440> happen<00:14:37.680> there 00:14:38.629 --> 00:14:38.639 align:start position:0% could happen there 00:14:38.639 --> 00:14:41.750 align:start position:0% could happen there and<00:14:39.480> the<00:14:39.660> last<00:14:39.779> one<00:14:39.959> that<00:14:40.139> we<00:14:40.320> didn't<00:14:40.560> find<00:14:40.860> was 00:14:41.750 --> 00:14:41.760 align:start position:0% and the last one that we didn't find was 00:14:41.760 --> 00:14:44.750 align:start position:0% and the last one that we didn't find was a<00:14:42.180> failover<00:14:42.600> beacon<00:14:43.139> note<00:14:43.260> scenario<00:14:43.800> a<00:14:44.579> lot<00:14:44.639> of 00:14:44.750 --> 00:14:44.760 align:start position:0% a failover beacon note scenario a lot of 00:14:44.760 --> 00:14:46.189 align:start position:0% a failover beacon note scenario a lot of people<00:14:44.940> are<00:14:45.240> really<00:14:45.420> obsessed<00:14:45.899> with<00:14:45.959> making 00:14:46.189 --> 00:14:46.199 align:start position:0% people are really obsessed with making 00:14:46.199 --> 00:14:47.449 align:start position:0% people are really obsessed with making sure<00:14:46.380> they<00:14:46.620> don't<00:14:46.740> miss<00:14:46.920> a<00:14:47.160> single 00:14:47.449 --> 00:14:47.459 align:start position:0% sure they don't miss a single 00:14:47.459 --> 00:14:49.430 align:start position:0% sure they don't miss a single attestation<00:14:48.120> which<00:14:48.899> means<00:14:49.139> they<00:14:49.260> have 00:14:49.430 --> 00:14:49.440 align:start position:0% attestation which means they have 00:14:49.440 --> 00:14:52.310 align:start position:0% attestation which means they have multiple<00:14:49.800> Beacon<00:14:50.160> notes<00:14:50.459> set<00:14:50.639> up<00:14:50.959> and<00:14:51.959> that's 00:14:52.310 --> 00:14:52.320 align:start position:0% multiple Beacon notes set up and that's 00:14:52.320 --> 00:14:54.710 align:start position:0% multiple Beacon notes set up and that's something<00:14:52.560> we<00:14:52.860> just<00:14:52.980> never<00:14:53.160> did<00:14:53.399> so<00:14:54.120> a<00:14:54.420> lot<00:14:54.540> of 00:14:54.710 --> 00:14:54.720 align:start position:0% something we just never did so a lot of 00:14:54.720 --> 00:14:56.449 align:start position:0% something we just never did so a lot of the<00:14:54.839> requests<00:14:55.320> were<00:14:55.560> just<00:14:55.800> being<00:14:55.920> sent<00:14:56.160> to<00:14:56.339> the 00:14:56.449 --> 00:14:56.459 align:start position:0% the requests were just being sent to the 00:14:56.459 --> 00:14:58.370 align:start position:0% the requests were just being sent to the primary<00:14:56.760> Beacon<00:14:57.240> node<00:14:57.540> and<00:14:57.839> not<00:14:57.899> the<00:14:58.079> backup 00:14:58.370 --> 00:14:58.380 align:start position:0% primary Beacon node and not the backup 00:14:58.380 --> 00:15:01.850 align:start position:0% primary Beacon node and not the backup so<00:14:59.220> when<00:14:59.699> the<00:14:59.940> failover<00:15:00.300> happens<00:15:00.720> the<00:15:01.560> backup 00:15:01.850 --> 00:15:01.860 align:start position:0% so when the failover happens the backup 00:15:01.860 --> 00:15:03.410 align:start position:0% so when the failover happens the backup wasn't<00:15:02.100> ready 00:15:03.410 --> 00:15:03.420 align:start position:0% wasn't ready 00:15:03.420 --> 00:15:04.910 align:start position:0% wasn't ready um<00:15:03.480> I<00:15:03.839> think<00:15:03.899> this<00:15:04.079> has<00:15:04.199> also<00:15:04.380> been<00:15:04.500> patched 00:15:04.910 --> 00:15:04.920 align:start position:0% um I think this has also been patched 00:15:04.920 --> 00:15:07.370 align:start position:0% um I think this has also been patched right<00:15:05.040> now<00:15:05.279> but<00:15:05.940> it<00:15:06.360> was<00:15:06.600> a<00:15:06.899> really<00:15:06.959> tricky 00:15:07.370 --> 00:15:07.380 align:start position:0% right now but it was a really tricky 00:15:07.380 --> 00:15:09.230 align:start position:0% right now but it was a really tricky thing<00:15:07.500> and<00:15:07.740> we<00:15:07.920> should<00:15:08.100> try 00:15:09.230 --> 00:15:09.240 align:start position:0% thing and we should try 00:15:09.240 --> 00:15:11.629 align:start position:0% thing and we should try more<00:15:10.019> failover<00:15:10.500> backup<00:15:10.920> scenarios<00:15:11.339> in<00:15:11.519> the 00:15:11.629 --> 00:15:11.639 align:start position:0% more failover backup scenarios in the 00:15:11.639 --> 00:15:14.090 align:start position:0% more failover backup scenarios in the future<00:15:11.760> I<00:15:12.000> guess 00:15:14.090 --> 00:15:14.100 align:start position:0% future I guess 00:15:14.100 --> 00:15:16.970 align:start position:0% future I guess um<00:15:14.160> one<00:15:14.880> cool<00:15:15.180> thing<00:15:15.480> about<00:15:15.839> why<00:15:16.440> all<00:15:16.680> of<00:15:16.800> this 00:15:16.970 --> 00:15:16.980 align:start position:0% um one cool thing about why all of this 00:15:16.980 --> 00:15:18.110 align:start position:0% um one cool thing about why all of this wasn't<00:15:17.279> found 00:15:18.110 --> 00:15:18.120 align:start position:0% wasn't found 00:15:18.120 --> 00:15:20.810 align:start position:0% wasn't found most<00:15:18.660> of<00:15:18.779> them<00:15:18.839> are<00:15:19.019> optimization<00:15:19.620> bugs 00:15:20.810 --> 00:15:20.820 align:start position:0% most of them are optimization bugs 00:15:20.820 --> 00:15:22.790 align:start position:0% most of them are optimization bugs um<00:15:20.880> as<00:15:21.360> you<00:15:21.480> can<00:15:21.540> see<00:15:21.720> merge<00:15:22.260> still<00:15:22.380> went<00:15:22.620> fine 00:15:22.790 --> 00:15:22.800 align:start position:0% um as you can see merge still went fine 00:15:22.800 --> 00:15:25.670 align:start position:0% um as you can see merge still went fine but<00:15:23.760> we<00:15:24.120> could<00:15:24.240> there's<00:15:24.660> still<00:15:24.899> some<00:15:25.199> room<00:15:25.440> for 00:15:25.670 --> 00:15:25.680 align:start position:0% but we could there's still some room for 00:15:25.680 --> 00:15:27.590 align:start position:0% but we could there's still some room for improvement<00:15:26.100> and<00:15:26.820> it's<00:15:26.940> a<00:15:27.180> really<00:15:27.360> hard 00:15:27.590 --> 00:15:27.600 align:start position:0% improvement and it's a really hard 00:15:27.600 --> 00:15:29.689 align:start position:0% improvement and it's a really hard trade-off<00:15:28.079> to<00:15:28.320> make<00:15:28.500> between<00:15:28.800> do<00:15:29.220> we<00:15:29.399> want<00:15:29.519> to 00:15:29.689 --> 00:15:29.699 align:start position:0% trade-off to make between do we want to 00:15:29.699 --> 00:15:31.370 align:start position:0% trade-off to make between do we want to spend<00:15:29.880> more<00:15:30.120> depth<00:15:30.480> time<00:15:30.660> in<00:15:30.839> fixing<00:15:31.139> these 00:15:31.370 --> 00:15:31.380 align:start position:0% spend more depth time in fixing these 00:15:31.380 --> 00:15:33.410 align:start position:0% spend more depth time in fixing these optimizations<00:15:31.980> or<00:15:32.519> did<00:15:32.699> we<00:15:32.820> want<00:15:33.000> an<00:15:33.120> earlier 00:15:33.410 --> 00:15:33.420 align:start position:0% optimizations or did we want an earlier 00:15:33.420 --> 00:15:34.310 align:start position:0% optimizations or did we want an earlier much 00:15:34.310 --> 00:15:34.320 align:start position:0% much 00:15:34.320 --> 00:15:36.410 align:start position:0% much and<00:15:34.920> that's<00:15:35.220> kind<00:15:35.399> of<00:15:35.459> the<00:15:35.579> tricky<00:15:35.880> thing<00:15:36.060> do 00:15:36.410 --> 00:15:36.420 align:start position:0% and that's kind of the tricky thing do 00:15:36.420 --> 00:15:38.110 align:start position:0% and that's kind of the tricky thing do we<00:15:36.540> want<00:15:36.660> earlier<00:15:37.019> fox<00:15:37.260> or<00:15:37.560> do<00:15:37.740> we<00:15:37.860> want 00:15:38.110 --> 00:15:38.120 align:start position:0% we want earlier fox or do we want 00:15:38.120 --> 00:15:41.930 align:start position:0% we want earlier fox or do we want completely<00:15:39.120> buckless<00:15:39.839> free<00:15:40.320> free 00:15:41.930 --> 00:15:41.940 align:start position:0% completely buckless free free 00:15:41.940 --> 00:15:45.230 align:start position:0% completely buckless free free um free<00:15:42.360> Fox<00:15:42.720> no<00:15:43.560> idea<00:15:43.920> but<00:15:44.820> we're<00:15:44.940> definitely 00:15:45.230 --> 00:15:45.240 align:start position:0% um free Fox no idea but we're definitely 00:15:45.240 --> 00:15:46.670 align:start position:0% um free Fox no idea but we're definitely going<00:15:45.420> to<00:15:45.540> be<00:15:45.600> adding<00:15:45.899> resource<00:15:46.380> constraint 00:15:46.670 --> 00:15:46.680 align:start position:0% going to be adding resource constraint 00:15:46.680 --> 00:15:48.650 align:start position:0% going to be adding resource constraint machines<00:15:47.519> to<00:15:47.699> the<00:15:47.820> mix<00:15:47.940> next<00:15:48.180> time<00:15:48.360> we're 00:15:48.650 --> 00:15:48.660 align:start position:0% machines to the mix next time we're 00:15:48.660 --> 00:15:49.850 align:start position:0% machines to the mix next time we're thinking<00:15:48.959> of<00:15:49.079> just<00:15:49.199> getting<00:15:49.380> a<00:15:49.620> bunch<00:15:49.740> of 00:15:49.850 --> 00:15:49.860 align:start position:0% thinking of just getting a bunch of 00:15:49.860 --> 00:15:52.370 align:start position:0% thinking of just getting a bunch of Raspberry<00:15:50.279> Pi's<00:15:50.880> and<00:15:51.180> doing<00:15:51.480> some<00:15:51.899> Shadow<00:15:52.079> Fox 00:15:52.370 --> 00:15:52.380 align:start position:0% Raspberry Pi's and doing some Shadow Fox 00:15:52.380 --> 00:15:54.410 align:start position:0% Raspberry Pi's and doing some Shadow Fox on<00:15:52.620> there<00:15:52.740> see<00:15:53.040> what<00:15:53.339> happens<00:15:53.519> there 00:15:54.410 --> 00:15:54.420 align:start position:0% on there see what happens there 00:15:54.420 --> 00:15:56.329 align:start position:0% on there see what happens there and<00:15:55.079> another<00:15:55.260> reason<00:15:55.560> some<00:15:55.860> of<00:15:55.980> the<00:15:56.100> bugs 00:15:56.329 --> 00:15:56.339 align:start position:0% and another reason some of the bugs 00:15:56.339 --> 00:15:58.069 align:start position:0% and another reason some of the bugs appeared<00:15:56.760> but<00:15:57.300> they<00:15:57.480> didn't<00:15:57.540> appear<00:15:57.839> on<00:15:57.959> the 00:15:58.069 --> 00:15:58.079 align:start position:0% appeared but they didn't appear on the 00:15:58.079 --> 00:16:00.949 align:start position:0% appeared but they didn't appear on the shadow<00:15:58.199> Fox<00:15:58.500> is<00:15:59.100> last<00:15:59.459> minute<00:15:59.639> commits 00:16:00.949 --> 00:16:00.959 align:start position:0% shadow Fox is last minute commits 00:16:00.959 --> 00:16:02.689 align:start position:0% shadow Fox is last minute commits um<00:16:01.019> The<00:16:01.320> Last<00:16:01.440> Shadow<00:16:01.620> Focus<00:16:02.040> I<00:16:02.279> think<00:16:02.399> a<00:16:02.579> week 00:16:02.689 --> 00:16:02.699 align:start position:0% um The Last Shadow Focus I think a week 00:16:02.699 --> 00:16:05.449 align:start position:0% um The Last Shadow Focus I think a week before<00:16:03.060> the<00:16:03.720> March<00:16:04.079> and<00:16:04.380> the<00:16:04.620> last<00:16:04.800> releases 00:16:05.449 --> 00:16:05.459 align:start position:0% before the March and the last releases 00:16:05.459 --> 00:16:07.129 align:start position:0% before the March and the last releases also<00:16:05.940> happened<00:16:06.120> a<00:16:06.420> few<00:16:06.540> days<00:16:06.660> before<00:16:06.899> the 00:16:07.129 --> 00:16:07.139 align:start position:0% also happened a few days before the 00:16:07.139 --> 00:16:07.970 align:start position:0% also happened a few days before the March 00:16:07.970 --> 00:16:07.980 align:start position:0% March 00:16:07.980 --> 00:16:12.769 align:start position:0% March so<00:16:08.579> yeah<00:16:09.300> it's<00:16:09.839> a<00:16:09.959> hard<00:16:10.079> trade-off 00:16:12.769 --> 00:16:12.779 align:start position:0% 00:16:12.779 --> 00:16:14.509 align:start position:0% um<00:16:12.959> if<00:16:13.139> you<00:16:13.320> want<00:16:13.500> to<00:16:13.620> join<00:16:13.920> the<00:16:14.040> testing 00:16:14.509 --> 00:16:14.519 align:start position:0% um if you want to join the testing 00:16:14.519 --> 00:16:18.910 align:start position:0% um if you want to join the testing efforts<00:16:15.060> please<00:16:15.839> join<00:16:16.560> Mario<00:16:17.519> Vega 00:16:18.910 --> 00:16:18.920 align:start position:0% efforts please join Mario Vega 00:16:18.920 --> 00:16:21.829 align:start position:0% efforts please join Mario Vega his<00:16:19.920> email<00:16:20.339> address<00:16:20.639> is<00:16:20.940> here<00:16:21.180> send<00:16:21.540> in<00:16:21.660> your 00:16:21.829 --> 00:16:21.839 align:start position:0% his email address is here send in your 00:16:21.839 --> 00:16:25.310 align:start position:0% his email address is here send in your information<00:16:22.019> there<00:16:22.639> and<00:16:23.639> I<00:16:24.120> think<00:16:24.600> I<00:16:24.839> supposed 00:16:25.310 --> 00:16:25.320 align:start position:0% information there and I think I supposed 00:16:25.320 --> 00:16:27.050 align:start position:0% information there and I think I supposed to<00:16:25.680> okay<00:16:26.100> I<00:16:26.279> was<00:16:26.399> supposed<00:16:26.519> to<00:16:26.639> have<00:16:26.760> one<00:16:26.880> more 00:16:27.050 --> 00:16:27.060 align:start position:0% to okay I was supposed to have one more 00:16:27.060 --> 00:16:29.090 align:start position:0% to okay I was supposed to have one more slide<00:16:27.300> but<00:16:27.660> I<00:16:27.899> will<00:16:28.019> just<00:16:28.199> talk<00:16:28.440> about<00:16:28.620> that 00:16:29.090 --> 00:16:29.100 align:start position:0% slide but I will just talk about that 00:16:29.100 --> 00:16:31.250 align:start position:0% slide but I will just talk about that other<00:16:29.459> slide<00:16:29.820> over<00:16:30.000> here 00:16:31.250 --> 00:16:31.260 align:start position:0% other slide over here 00:16:31.260 --> 00:16:34.250 align:start position:0% other slide over here um<00:16:31.680> so<00:16:32.339> we<00:16:32.820> have<00:16:33.000> a<00:16:33.180> bunch<00:16:33.300> of<00:16:33.480> testing<00:16:33.839> tools 00:16:34.250 --> 00:16:34.260 align:start position:0% um so we have a bunch of testing tools 00:16:34.260 --> 00:16:36.650 align:start position:0% um so we have a bunch of testing tools that<00:16:34.680> we've<00:16:34.980> completely<00:16:35.459> open<00:16:35.699> sourced<00:16:36.180> if 00:16:36.650 --> 00:16:36.660 align:start position:0% that we've completely open sourced if 00:16:36.660 --> 00:16:38.749 align:start position:0% that we've completely open sourced if you're<00:16:36.839> someone<00:16:37.259> who<00:16:37.560> wants<00:16:37.920> to<00:16:37.980> run<00:16:38.220> that's 00:16:38.749 --> 00:16:38.759 align:start position:0% you're someone who wants to run that's 00:16:38.759 --> 00:16:40.550 align:start position:0% you're someone who wants to run that's nothing<00:16:39.000> kubernetes<00:16:39.660> if<00:16:39.959> you're<00:16:40.079> someone<00:16:40.320> who 00:16:40.550 --> 00:16:40.560 align:start position:0% nothing kubernetes if you're someone who 00:16:40.560 --> 00:16:42.949 align:start position:0% nothing kubernetes if you're someone who wants<00:16:40.800> to<00:16:40.860> just<00:16:41.040> run<00:16:41.279> kubernetes<00:16:41.880> nodes<00:16:42.300> if 00:16:42.949 --> 00:16:42.959 align:start position:0% wants to just run kubernetes nodes if 00:16:42.959 --> 00:16:45.590 align:start position:0% wants to just run kubernetes nodes if you<00:16:43.259> want<00:16:43.380> to<00:16:43.500> set<00:16:43.680> up<00:16:43.800> your<00:16:44.040> own<00:16:44.160> networks<00:16:44.880> we 00:16:45.590 --> 00:16:45.600 align:start position:0% you want to set up your own networks we 00:16:45.600 --> 00:16:47.930 align:start position:0% you want to set up your own networks we have<00:16:45.779> easy<00:16:46.019> ways<00:16:46.440> to<00:16:46.500> set<00:16:46.680> up<00:16:46.800> Genesis<00:16:47.279> if<00:16:47.759> you 00:16:47.930 --> 00:16:47.940 align:start position:0% have easy ways to set up Genesis if you 00:16:47.940 --> 00:16:49.730 align:start position:0% have easy ways to set up Genesis if you want<00:16:48.180> to 00:16:49.730 --> 00:16:49.740 align:start position:0% want to 00:16:49.740 --> 00:16:51.829 align:start position:0% want to um<00:16:49.800> yeah<00:16:50.459> use<00:16:50.820> the<00:16:51.000> same<00:16:51.120> stuff<00:16:51.300> we<00:16:51.540> use<00:16:51.660> for 00:16:51.829 --> 00:16:51.839 align:start position:0% um yeah use the same stuff we use for 00:16:51.839 --> 00:16:53.810 align:start position:0% um yeah use the same stuff we use for shadowfox<00:16:52.320> all<00:16:52.920> of<00:16:53.040> it<00:16:53.160> is<00:16:53.279> completely<00:16:53.579> open 00:16:53.810 --> 00:16:53.820 align:start position:0% shadowfox all of it is completely open 00:16:53.820 --> 00:16:55.850 align:start position:0% shadowfox all of it is completely open source<00:16:54.240> quite<00:16:54.779> a<00:16:54.899> few<00:16:54.959> organizations<00:16:55.560> are 00:16:55.850 --> 00:16:55.860 align:start position:0% source quite a few organizations are 00:16:55.860 --> 00:16:58.370 align:start position:0% source quite a few organizations are actually<00:16:56.100> reusing<00:16:56.639> our<00:16:57.600> um<00:16:57.600> our<00:16:57.899> stuff<00:16:58.079> so 00:16:58.370 --> 00:16:58.380 align:start position:0% actually reusing our um our stuff so 00:16:58.380 --> 00:17:00.650 align:start position:0% actually reusing our um our stuff so shout<00:16:58.680> out<00:16:58.740> to<00:16:58.920> them<00:16:59.420> contribute<00:17:00.420> back 00:17:00.650 --> 00:17:00.660 align:start position:0% shout out to them contribute back 00:17:00.660 --> 00:17:02.990 align:start position:0% shout out to them contribute back whenever<00:17:01.019> you<00:17:01.259> can<00:17:01.440> you<00:17:02.040> can<00:17:02.220> find<00:17:02.519> most<00:17:02.880> of 00:17:02.990 --> 00:17:03.000 align:start position:0% whenever you can you can find most of 00:17:03.000 --> 00:17:06.110 align:start position:0% whenever you can you can find most of the<00:17:03.180> tools<00:17:03.480> on<00:17:04.100> either<00:17:05.100> on<00:17:05.459> the<00:17:05.579> ethereum 00:17:06.110 --> 00:17:06.120 align:start position:0% the tools on either on the ethereum 00:17:06.120 --> 00:17:09.530 align:start position:0% the tools on either on the ethereum GitHub<00:17:06.720> repo<00:17:07.199> or<00:17:08.040> on<00:17:08.339> the<00:17:08.579> eat<00:17:08.819> Panda<00:17:09.240> Ops 00:17:09.530 --> 00:17:09.540 align:start position:0% GitHub repo or on the eat Panda Ops 00:17:09.540 --> 00:17:13.130 align:start position:0% GitHub repo or on the eat Panda Ops GitHub<00:17:09.839> repo<00:17:10.319> one<00:17:11.160> of<00:17:11.280> the<00:17:11.400> two<00:17:11.720> and<00:17:12.720> yeah 00:17:13.130 --> 00:17:13.140 align:start position:0% GitHub repo one of the two and yeah 00:17:13.140 --> 00:17:15.289 align:start position:0% GitHub repo one of the two and yeah that's<00:17:13.740> about<00:17:14.040> it<00:17:14.280> that's<00:17:14.520> most<00:17:14.760> of<00:17:14.939> what<00:17:15.120> we 00:17:15.289 --> 00:17:15.299 align:start position:0% that's about it that's most of what we 00:17:15.299 --> 00:17:18.370 align:start position:0% that's about it that's most of what we did<00:17:15.600> and<00:17:15.900> did<00:17:16.140> not<00:17:16.260> find<00:17:16.559> on<00:17:16.860> the<00:17:17.040> merge 00:17:18.370 --> 00:17:18.380 align:start position:0% did and did not find on the merge 00:17:18.380 --> 00:17:21.559 align:start position:0% did and did not find on the merge thank<00:17:19.380> you