WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.430 align:start position:0% [Music] 00:00:12.430 --> 00:00:12.440 align:start position:0% 00:00:12.440 --> 00:00:15.049 align:start position:0% if<00:00:13.440> you're<00:00:13.559> in<00:00:13.679> the<00:00:13.799> wrong<00:00:13.920> room<00:00:14.040> this<00:00:14.519> room<00:00:14.880> is 00:00:15.049 --> 00:00:15.059 align:start position:0% if you're in the wrong room this room is 00:00:15.059 --> 00:00:17.210 align:start position:0% if you're in the wrong room this room is talking<00:00:15.240> about<00:00:15.420> testing<00:00:15.900> the<00:00:16.020> merge<00:00:16.320> with 00:00:17.210 --> 00:00:17.220 align:start position:0% talking about testing the merge with 00:00:17.220 --> 00:00:18.950 align:start position:0% talking about testing the merge with parallel<00:00:17.699> universes 00:00:18.950 --> 00:00:18.960 align:start position:0% parallel universes 00:00:18.960 --> 00:00:21.410 align:start position:0% parallel universes my<00:00:19.560> name<00:00:19.680> is<00:00:19.740> David<00:00:19.920> Searle<00:00:20.460> and<00:00:21.060> I'm<00:00:21.180> the<00:00:21.300> head 00:00:21.410 --> 00:00:21.420 align:start position:0% my name is David Searle and I'm the head 00:00:21.420 --> 00:00:23.870 align:start position:0% my name is David Searle and I'm the head of<00:00:21.480> Amir<00:00:21.779> for<00:00:22.140> a<00:00:22.439> small<00:00:22.560> startup<00:00:23.100> that's<00:00:23.640> been 00:00:23.870 --> 00:00:23.880 align:start position:0% of Amir for a small startup that's been 00:00:23.880 --> 00:00:25.550 align:start position:0% of Amir for a small startup that's been working<00:00:24.000> with<00:00:24.180> the<00:00:24.240> ethereum<00:00:24.600> foundation<00:00:25.019> for 00:00:25.550 --> 00:00:25.560 align:start position:0% working with the ethereum foundation for 00:00:25.560 --> 00:00:27.609 align:start position:0% working with the ethereum foundation for just<00:00:25.740> over<00:00:25.920> a<00:00:26.100> year<00:00:26.220> now 00:00:27.609 --> 00:00:27.619 align:start position:0% just over a year now 00:00:27.619 --> 00:00:31.250 align:start position:0% just over a year now who<00:00:28.619> likes<00:00:29.220> Bugs<00:00:29.699> okay<00:00:30.300> I<00:00:30.599> brought<00:00:30.779> some<00:00:30.960> bugs 00:00:31.250 --> 00:00:31.260 align:start position:0% who likes Bugs okay I brought some bugs 00:00:31.260 --> 00:00:32.450 align:start position:0% who likes Bugs okay I brought some bugs along<00:00:31.380> with<00:00:31.560> me<00:00:31.679> today<00:00:31.800> so<00:00:32.099> you're<00:00:32.279> going<00:00:32.399> to 00:00:32.450 --> 00:00:32.460 align:start position:0% along with me today so you're going to 00:00:32.460 --> 00:00:34.069 align:start position:0% along with me today so you're going to have<00:00:32.579> to<00:00:32.700> be<00:00:32.880> like<00:00:33.239> who<00:00:33.540> would<00:00:33.660> like<00:00:33.780> a<00:00:33.960> bug 00:00:34.069 --> 00:00:34.079 align:start position:0% have to be like who would like a bug 00:00:34.079 --> 00:00:35.450 align:start position:0% have to be like who would like a bug because<00:00:34.320> I've<00:00:34.500> got<00:00:34.680> some<00:00:34.800> bugs<00:00:35.160> that<00:00:35.280> actually 00:00:35.450 --> 00:00:35.460 align:start position:0% because I've got some bugs that actually 00:00:35.460 --> 00:00:37.190 align:start position:0% because I've got some bugs that actually I'd<00:00:35.700> like<00:00:35.820> to<00:00:35.940> give<00:00:36.059> to<00:00:36.300> various<00:00:36.840> members<00:00:37.140> of 00:00:37.190 --> 00:00:37.200 align:start position:0% I'd like to give to various members of 00:00:37.200 --> 00:00:39.110 align:start position:0% I'd like to give to various members of the<00:00:37.320> audience<00:00:37.559> anybody<00:00:37.980> you'd<00:00:38.700> like<00:00:38.820> one<00:00:38.940> okay 00:00:39.110 --> 00:00:39.120 align:start position:0% the audience anybody you'd like one okay 00:00:39.120 --> 00:00:41.209 align:start position:0% the audience anybody you'd like one okay here<00:00:39.420> we<00:00:39.540> go<00:00:39.600> just<00:00:39.840> after<00:00:40.079> a<00:00:40.440> little<00:00:40.800> you're 00:00:41.209 --> 00:00:41.219 align:start position:0% here we go just after a little you're 00:00:41.219 --> 00:00:43.970 align:start position:0% here we go just after a little you're gonna<00:00:41.340> catching<00:00:41.820> so<00:00:42.360> little<00:00:42.960> bugs<00:00:43.379> we've<00:00:43.920> been 00:00:43.970 --> 00:00:43.980 align:start position:0% gonna catching so little bugs we've been 00:00:43.980 --> 00:00:45.650 align:start position:0% gonna catching so little bugs we've been spending<00:00:44.399> the<00:00:44.579> last<00:00:44.760> year<00:00:45.000> kind<00:00:45.300> of<00:00:45.420> really 00:00:45.650 --> 00:00:45.660 align:start position:0% spending the last year kind of really 00:00:45.660 --> 00:00:48.350 align:start position:0% spending the last year kind of really stress<00:00:46.200> testing<00:00:46.559> for<00:00:47.100> my<00:00:47.340> boat<00:00:47.520> so<00:00:48.059> you<00:00:48.180> see 00:00:48.350 --> 00:00:48.360 align:start position:0% stress testing for my boat so you see 00:00:48.360 --> 00:00:49.369 align:start position:0% stress testing for my boat so you see this<00:00:48.480> is<00:00:48.600> why<00:00:48.660> you<00:00:48.780> should<00:00:48.899> stay<00:00:49.020> at<00:00:49.200> the<00:00:49.260> front 00:00:49.369 --> 00:00:49.379 align:start position:0% this is why you should stay at the front 00:00:49.379 --> 00:00:51.350 align:start position:0% this is why you should stay at the front I've<00:00:49.739> got<00:00:49.860> three<00:00:50.039> more<00:00:50.219> to<00:00:50.399> go<00:00:50.579> there<00:00:51.000> we<00:00:51.239> go 00:00:51.350 --> 00:00:51.360 align:start position:0% I've got three more to go there we go 00:00:51.360 --> 00:00:53.270 align:start position:0% I've got three more to go there we go see 00:00:53.270 --> 00:00:53.280 align:start position:0% see 00:00:53.280 --> 00:00:56.630 align:start position:0% see so<00:00:54.000> the<00:00:54.780> it<00:00:55.140> talks<00:00:55.440> about<00:00:55.559> testing<00:00:56.160> ethereum 00:00:56.630 --> 00:00:56.640 align:start position:0% so the it talks about testing ethereum 00:00:56.640 --> 00:00:59.869 align:start position:0% so the it talks about testing ethereum and<00:00:57.300> is<00:00:57.600> is<00:00:57.960> basically<00:00:58.440> looking<00:00:58.980> at<00:00:59.219> using<00:00:59.520> a 00:00:59.869 --> 00:00:59.879 align:start position:0% and is is basically looking at using a 00:00:59.879 --> 00:01:03.349 align:start position:0% and is is basically looking at using a pretty<00:01:00.320> sophisticated<00:01:01.320> and<00:01:01.980> unique<00:01:02.359> testing 00:01:03.349 --> 00:01:03.359 align:start position:0% pretty sophisticated and unique testing 00:01:03.359 --> 00:01:05.690 align:start position:0% pretty sophisticated and unique testing methodology<00:01:03.860> which<00:01:04.860> is<00:01:05.040> based<00:01:05.460> from<00:01:05.580> a 00:01:05.690 --> 00:01:05.700 align:start position:0% methodology which is based from a 00:01:05.700 --> 00:01:07.609 align:start position:0% methodology which is based from a company<00:01:05.820> called<00:01:06.060> antithesis<00:01:06.780> which<00:01:07.200> I<00:01:07.320> belong 00:01:07.609 --> 00:01:07.619 align:start position:0% company called antithesis which I belong 00:01:07.619 --> 00:01:08.570 align:start position:0% company called antithesis which I belong to 00:01:08.570 --> 00:01:08.580 align:start position:0% to 00:01:08.580 --> 00:01:11.630 align:start position:0% to um<00:01:08.640> the<00:01:09.240> the<00:01:09.600> company<00:01:09.900> is<00:01:10.140> involved<00:01:10.740> in<00:01:11.100> using 00:01:11.630 --> 00:01:11.640 align:start position:0% um the the company is involved in using 00:01:11.640 --> 00:01:14.270 align:start position:0% um the the company is involved in using deterministic<00:01:12.360> simulation<00:01:12.900> techniques<00:01:13.560> to 00:01:14.270 --> 00:01:14.280 align:start position:0% deterministic simulation techniques to 00:01:14.280 --> 00:01:17.270 align:start position:0% deterministic simulation techniques to allow<00:01:14.520> us<00:01:14.640> to<00:01:14.880> basically<00:01:15.780> explore<00:01:16.200> a<00:01:17.040> whole 00:01:17.270 --> 00:01:17.280 align:start position:0% allow us to basically explore a whole 00:01:17.280 --> 00:01:19.910 align:start position:0% allow us to basically explore a whole host<00:01:17.520> of<00:01:17.939> iterations<00:01:18.479> of<00:01:19.020> of<00:01:19.439> complex 00:01:19.910 --> 00:01:19.920 align:start position:0% host of iterations of of complex 00:01:19.920 --> 00:01:22.370 align:start position:0% host of iterations of of complex distributive<00:01:20.720> technology<00:01:21.720> that's<00:01:22.140> running 00:01:22.370 --> 00:01:22.380 align:start position:0% distributive technology that's running 00:01:22.380 --> 00:01:24.770 align:start position:0% distributive technology that's running in<00:01:22.740> a<00:01:22.860> simulated<00:01:23.400> environment<00:01:23.880> so<00:01:24.540> let<00:01:24.659> me 00:01:24.770 --> 00:01:24.780 align:start position:0% in a simulated environment so let me 00:01:24.780 --> 00:01:26.749 align:start position:0% in a simulated environment so let me just<00:01:24.840> get<00:01:25.020> my<00:01:25.200> my<00:01:25.500> little<00:01:25.680> Clicker 00:01:26.749 --> 00:01:26.759 align:start position:0% just get my my little Clicker 00:01:26.759 --> 00:01:28.910 align:start position:0% just get my my little Clicker I<00:01:27.180> brought<00:01:27.360> a<00:01:27.540> few<00:01:27.659> uh<00:01:28.020> Stars<00:01:28.439> along<00:01:28.560> to<00:01:28.799> the 00:01:28.910 --> 00:01:28.920 align:start position:0% I brought a few uh Stars along to the 00:01:28.920 --> 00:01:32.030 align:start position:0% I brought a few uh Stars along to the show<00:01:29.580> um<00:01:29.640> obviously<00:01:30.619> I've<00:01:31.619> just<00:01:31.680> explained 00:01:32.030 --> 00:01:32.040 align:start position:0% show um obviously I've just explained 00:01:32.040 --> 00:01:32.929 align:start position:0% show um obviously I've just explained who<00:01:32.159> I<00:01:32.280> am 00:01:32.929 --> 00:01:32.939 align:start position:0% who I am 00:01:32.939 --> 00:01:34.670 align:start position:0% who I am um<00:01:33.060> little<00:01:33.420> did<00:01:33.659> you<00:01:33.840> know<00:01:33.960> that<00:01:34.200> uh<00:01:34.380> doctor 00:01:34.670 --> 00:01:34.680 align:start position:0% um little did you know that uh doctor 00:01:34.680 --> 00:01:37.249 align:start position:0% um little did you know that uh doctor strange<00:01:35.100> and<00:01:35.520> Cher<00:01:35.939> are<00:01:36.720> also<00:01:36.900> going<00:01:37.079> to 00:01:37.249 --> 00:01:37.259 align:start position:0% strange and Cher are also going to 00:01:37.259 --> 00:01:39.950 align:start position:0% strange and Cher are also going to participate<00:01:37.740> in<00:01:37.979> this<00:01:38.159> this<00:01:38.400> presentation 00:01:39.950 --> 00:01:39.960 align:start position:0% participate in this this presentation 00:01:39.960 --> 00:01:41.690 align:start position:0% participate in this this presentation um I've<00:01:40.560> got<00:01:40.680> about<00:01:40.799> 25<00:01:41.040> years<00:01:41.340> worth<00:01:41.520> of 00:01:41.690 --> 00:01:41.700 align:start position:0% um I've got about 25 years worth of 00:01:41.700 --> 00:01:43.550 align:start position:0% um I've got about 25 years worth of experiences<00:01:42.119> in<00:01:42.360> the<00:01:42.479> tech<00:01:42.600> industry 00:01:43.550 --> 00:01:43.560 align:start position:0% experiences in the tech industry 00:01:43.560 --> 00:01:45.410 align:start position:0% experiences in the tech industry um<00:01:43.619> for<00:01:43.860> the<00:01:43.979> last<00:01:44.100> two<00:01:44.460> and<00:01:44.640> a<00:01:44.820> bit<00:01:44.939> years<00:01:45.119> now 00:01:45.410 --> 00:01:45.420 align:start position:0% um for the last two and a bit years now 00:01:45.420 --> 00:01:46.370 align:start position:0% um for the last two and a bit years now I've<00:01:45.600> been<00:01:45.780> working<00:01:45.900> for<00:01:46.079> this<00:01:46.200> business 00:01:46.370 --> 00:01:46.380 align:start position:0% I've been working for this business 00:01:46.380 --> 00:01:49.010 align:start position:0% I've been working for this business antithesis<00:01:47.220> and<00:01:47.939> they've 00:01:49.010 --> 00:01:49.020 align:start position:0% antithesis and they've 00:01:49.020 --> 00:01:50.810 align:start position:0% antithesis and they've um<00:01:49.140> you<00:01:49.380> know<00:01:49.500> basically<00:01:50.159> made<00:01:50.460> me<00:01:50.640> into 00:01:50.810 --> 00:01:50.820 align:start position:0% um you know basically made me into 00:01:50.820 --> 00:01:52.310 align:start position:0% um you know basically made me into somebody<00:01:51.119> of<00:01:51.420> that<00:01:51.600> there's<00:01:51.780> a<00:01:51.960> bug<00:01:52.079> Hunter 00:01:52.310 --> 00:01:52.320 align:start position:0% somebody of that there's a bug Hunter 00:01:52.320 --> 00:01:54.410 align:start position:0% somebody of that there's a bug Hunter buyer<00:01:52.920> by<00:01:53.100> trade<00:01:53.820> um<00:01:53.939> I<00:01:54.060> never<00:01:54.240> thought 00:01:54.410 --> 00:01:54.420 align:start position:0% buyer by trade um I never thought 00:01:54.420 --> 00:01:56.510 align:start position:0% buyer by trade um I never thought testing<00:01:54.899> could<00:01:55.079> be<00:01:55.200> fun<00:01:55.439> but<00:01:56.220> there's<00:01:56.340> nothing 00:01:56.510 --> 00:01:56.520 align:start position:0% testing could be fun but there's nothing 00:01:56.520 --> 00:01:58.069 align:start position:0% testing could be fun but there's nothing like<00:01:56.759> hitting<00:01:57.119> a<00:01:57.240> seg<00:01:57.479> fault<00:01:57.720> and<00:01:57.899> actually 00:01:58.069 --> 00:01:58.079 align:start position:0% like hitting a seg fault and actually 00:01:58.079 --> 00:01:59.929 align:start position:0% like hitting a seg fault and actually getting<00:01:58.380> a<00:01:58.619> real<00:01:58.740> kick<00:01:58.979> out<00:01:59.040> of<00:01:59.220> it<00:01:59.340> and<00:01:59.700> that's 00:01:59.929 --> 00:01:59.939 align:start position:0% getting a real kick out of it and that's 00:01:59.939 --> 00:02:02.030 align:start position:0% getting a real kick out of it and that's what<00:02:00.060> I<00:02:00.180> do<00:02:00.299> on<00:02:00.420> a<00:02:00.540> day-to-day<00:02:00.899> basis<00:02:01.200> this<00:02:01.920> is 00:02:02.030 --> 00:02:02.040 align:start position:0% what I do on a day-to-day basis this is 00:02:02.040 --> 00:02:03.649 align:start position:0% what I do on a day-to-day basis this is my<00:02:02.159> house<00:02:02.340> in<00:02:02.579> the<00:02:02.759> UK<00:02:02.939> you<00:02:03.119> can<00:02:03.240> tell<00:02:03.299> from<00:02:03.540> my 00:02:03.649 --> 00:02:03.659 align:start position:0% my house in the UK you can tell from my 00:02:03.659 --> 00:02:05.330 align:start position:0% my house in the UK you can tell from my my<00:02:03.899> accent 00:02:05.330 --> 00:02:05.340 align:start position:0% my accent 00:02:05.340 --> 00:02:06.889 align:start position:0% my accent um and<00:02:05.640> as<00:02:05.759> you<00:02:05.880> can<00:02:06.000> see<00:02:06.060> I've<00:02:06.240> mostly<00:02:06.600> got<00:02:06.780> a 00:02:06.889 --> 00:02:06.899 align:start position:0% um and as you can see I've mostly got a 00:02:06.899 --> 00:02:09.229 align:start position:0% um and as you can see I've mostly got a few<00:02:07.020> gpus<00:02:07.439> I've<00:02:07.799> got<00:02:07.979> to<00:02:08.099> sell<00:02:08.340> so<00:02:09.000> if<00:02:09.119> you're 00:02:09.229 --> 00:02:09.239 align:start position:0% few gpus I've got to sell so if you're 00:02:09.239 --> 00:02:10.969 align:start position:0% few gpus I've got to sell so if you're interested<00:02:09.599> please<00:02:09.840> let<00:02:10.020> me<00:02:10.200> know 00:02:10.969 --> 00:02:10.979 align:start position:0% interested please let me know 00:02:10.979 --> 00:02:14.990 align:start position:0% interested please let me know um<00:02:11.039> no<00:02:11.459> joke<00:02:12.140> but<00:02:13.140> some<00:02:13.319> the<00:02:14.220> the<00:02:14.520> day<00:02:14.760> of<00:02:14.879> the 00:02:14.990 --> 00:02:15.000 align:start position:0% um no joke but some the the day of the 00:02:15.000 --> 00:02:16.430 align:start position:0% um no joke but some the the day of the merge<00:02:15.239> came<00:02:15.360> round<00:02:15.540> and<00:02:15.840> we've<00:02:16.080> been<00:02:16.140> doing<00:02:16.319> a 00:02:16.430 --> 00:02:16.440 align:start position:0% merge came round and we've been doing a 00:02:16.440 --> 00:02:18.050 align:start position:0% merge came round and we've been doing a lot<00:02:16.560> of<00:02:16.680> work<00:02:16.800> with<00:02:17.160> with<00:02:17.340> all<00:02:17.700> the<00:02:17.879> various 00:02:18.050 --> 00:02:18.060 align:start position:0% lot of work with with all the various 00:02:18.060 --> 00:02:19.190 align:start position:0% lot of work with with all the various clients 00:02:19.190 --> 00:02:19.200 align:start position:0% clients 00:02:19.200 --> 00:02:23.330 align:start position:0% clients um all<00:02:20.099> that<00:02:20.340> hard<00:02:21.020> arduous<00:02:22.020> testing<00:02:22.560> making 00:02:23.330 --> 00:02:23.340 align:start position:0% um all that hard arduous testing making 00:02:23.340 --> 00:02:26.150 align:start position:0% um all that hard arduous testing making sure<00:02:23.640> that<00:02:23.819> we<00:02:23.940> call<00:02:24.120> every<00:02:24.599> last<00:02:24.959> bug 00:02:26.150 --> 00:02:26.160 align:start position:0% sure that we call every last bug 00:02:26.160 --> 00:02:28.430 align:start position:0% sure that we call every last bug um<00:02:26.700> what<00:02:27.180> was<00:02:27.360> going<00:02:27.540> to<00:02:27.660> happen<00:02:27.780> was<00:02:28.260> it 00:02:28.430 --> 00:02:28.440 align:start position:0% um what was going to happen was it 00:02:28.440 --> 00:02:30.350 align:start position:0% um what was going to happen was it really<00:02:28.560> going<00:02:28.800> to<00:02:28.920> be<00:02:29.040> smooth<00:02:29.580> sailing<00:02:30.060> yeah<00:02:30.180> I 00:02:30.350 --> 00:02:30.360 align:start position:0% really going to be smooth sailing yeah I 00:02:30.360 --> 00:02:32.210 align:start position:0% really going to be smooth sailing yeah I think<00:02:30.420> we<00:02:30.540> saw<00:02:30.900> this<00:02:31.080> morning<00:02:31.200> uh<00:02:31.920> which 00:02:32.210 --> 00:02:32.220 align:start position:0% think we saw this morning uh which 00:02:32.220 --> 00:02:34.970 align:start position:0% think we saw this morning uh which obviously<00:02:32.580> is<00:02:32.760> great<00:02:33.000> news<00:02:33.599> um<00:02:33.720> but<00:02:34.200> um<00:02:34.200> yeah<00:02:34.620> I 00:02:34.970 --> 00:02:34.980 align:start position:0% obviously is great news um but um yeah I 00:02:34.980 --> 00:02:36.410 align:start position:0% obviously is great news um but um yeah I was<00:02:35.040> wondering<00:02:35.340> if<00:02:35.520> we<00:02:35.640> were<00:02:35.819> going<00:02:35.940> to<00:02:36.060> see 00:02:36.410 --> 00:02:36.420 align:start position:0% was wondering if we were going to see 00:02:36.420 --> 00:02:38.690 align:start position:0% was wondering if we were going to see this<00:02:36.720> you<00:02:37.500> have<00:02:37.620> to<00:02:37.739> press<00:02:37.860> play<00:02:38.099> on<00:02:38.400> the<00:02:38.580> uh 00:02:38.690 --> 00:02:38.700 align:start position:0% this you have to press play on the uh 00:02:38.700 --> 00:02:44.449 align:start position:0% this you have to press play on the uh the<00:02:39.000> video 00:02:44.449 --> 00:02:44.459 align:start position:0% 00:02:44.459 --> 00:02:46.970 align:start position:0% there<00:02:45.180> is<00:02:45.300> sound<00:02:45.420> as<00:02:45.599> well<00:02:45.720> but<00:02:46.019> uh 00:02:46.970 --> 00:02:46.980 align:start position:0% there is sound as well but uh 00:02:46.980 --> 00:02:48.350 align:start position:0% there is sound as well but uh um<00:02:47.099> I<00:02:47.400> couldn't<00:02:47.580> believe<00:02:47.760> this<00:02:47.940> when<00:02:48.120> I<00:02:48.239> saw 00:02:48.350 --> 00:02:48.360 align:start position:0% um I couldn't believe this when I saw 00:02:48.360 --> 00:03:06.130 align:start position:0% um I couldn't believe this when I saw this<00:02:48.599> but<00:02:48.780> uh<00:02:49.019> this<00:02:49.319> is<00:02:49.440> real 00:03:06.130 --> 00:03:06.140 align:start position:0% 00:03:06.140 --> 00:03:08.390 align:start position:0% yeah<00:03:07.140> it's<00:03:07.260> pretty<00:03:07.440> bad<00:03:07.620> eh 00:03:08.390 --> 00:03:08.400 align:start position:0% yeah it's pretty bad eh 00:03:08.400 --> 00:03:12.770 align:start position:0% yeah it's pretty bad eh um<00:03:08.580> not<00:03:08.940> my<00:03:09.120> fun<00:03:09.300> Garden<00:03:09.540> again<00:03:10.500> so 00:03:12.770 --> 00:03:12.780 align:start position:0% um not my fun Garden again so 00:03:12.780 --> 00:03:14.630 align:start position:0% um not my fun Garden again so um yeah<00:03:13.200> testing<00:03:13.620> is<00:03:13.739> really<00:03:13.980> important<00:03:14.340> and 00:03:14.630 --> 00:03:14.640 align:start position:0% um yeah testing is really important and 00:03:14.640 --> 00:03:16.670 align:start position:0% um yeah testing is really important and this<00:03:15.060> is<00:03:15.180> where<00:03:15.480> you<00:03:15.840> know<00:03:15.959> we<00:03:16.080> talk<00:03:16.319> about<00:03:16.500> it 00:03:16.670 --> 00:03:16.680 align:start position:0% this is where you know we talk about it 00:03:16.680 --> 00:03:18.530 align:start position:0% this is where you know we talk about it but<00:03:16.860> the<00:03:17.220> merge<00:03:17.519> was<00:03:17.640> a<00:03:17.819> significant<00:03:18.239> event 00:03:18.530 --> 00:03:18.540 align:start position:0% but the merge was a significant event 00:03:18.540 --> 00:03:20.869 align:start position:0% but the merge was a significant event that's<00:03:19.200> why<00:03:19.379> we<00:03:19.560> had<00:03:19.680> so<00:03:19.920> so<00:03:20.159> much<00:03:20.400> celebration 00:03:20.869 --> 00:03:20.879 align:start position:0% that's why we had so so much celebration 00:03:20.879 --> 00:03:23.210 align:start position:0% that's why we had so so much celebration across<00:03:21.599> the<00:03:21.720> world<00:03:21.840> about<00:03:22.200> kind<00:03:22.560> of<00:03:22.680> what<00:03:22.920> was 00:03:23.210 --> 00:03:23.220 align:start position:0% across the world about kind of what was 00:03:23.220 --> 00:03:25.430 align:start position:0% across the world about kind of what was really<00:03:23.459> going<00:03:23.760> on<00:03:24.000> uh<00:03:24.659> when<00:03:24.840> when<00:03:24.959> the<00:03:25.140> modes 00:03:25.430 --> 00:03:25.440 align:start position:0% really going on uh when when the modes 00:03:25.440 --> 00:03:26.630 align:start position:0% really going on uh when when the modes took<00:03:25.680> place 00:03:26.630 --> 00:03:26.640 align:start position:0% took place 00:03:26.640 --> 00:03:28.190 align:start position:0% took place um<00:03:26.760> so<00:03:27.000> congratulations<00:03:27.480> to<00:03:27.780> anybody<00:03:28.080> that 00:03:28.190 --> 00:03:28.200 align:start position:0% um so congratulations to anybody that 00:03:28.200 --> 00:03:29.570 align:start position:0% um so congratulations to anybody that was<00:03:28.319> involved<00:03:28.620> in<00:03:28.680> the<00:03:28.800> merge<00:03:29.159> you<00:03:29.459> know 00:03:29.570 --> 00:03:29.580 align:start position:0% was involved in the merge you know 00:03:29.580 --> 00:03:31.790 align:start position:0% was involved in the merge you know phenomenal<00:03:30.180> job<00:03:30.420> and<00:03:30.959> uh<00:03:31.080> yeah<00:03:31.379> I<00:03:31.560> think<00:03:31.620> we 00:03:31.790 --> 00:03:31.800 align:start position:0% phenomenal job and uh yeah I think we 00:03:31.800 --> 00:03:34.070 align:start position:0% phenomenal job and uh yeah I think we can<00:03:32.040> you<00:03:32.459> know<00:03:32.580> hold<00:03:33.239> our<00:03:33.420> heads<00:03:33.720> up<00:03:33.840> high 00:03:34.070 --> 00:03:34.080 align:start position:0% can you know hold our heads up high 00:03:34.080 --> 00:03:35.390 align:start position:0% can you know hold our heads up high there 00:03:35.390 --> 00:03:35.400 align:start position:0% there 00:03:35.400 --> 00:03:38.330 align:start position:0% there so<00:03:36.060> I'll<00:03:36.599> say<00:03:36.780> testing<00:03:37.140> is<00:03:37.260> hard<00:03:37.500> and<00:03:37.800> you<00:03:38.159> only 00:03:38.330 --> 00:03:38.340 align:start position:0% so I'll say testing is hard and you only 00:03:38.340 --> 00:03:40.070 align:start position:0% so I'll say testing is hard and you only got<00:03:38.459> to<00:03:38.580> use<00:03:38.700> Cura<00:03:39.120> to<00:03:39.300> basically<00:03:39.720> you<00:03:39.959> know 00:03:40.070 --> 00:03:40.080 align:start position:0% got to use Cura to basically you know 00:03:40.080 --> 00:03:42.170 align:start position:0% got to use Cura to basically you know ask<00:03:40.200> a<00:03:40.440> question<00:03:40.620> you<00:03:41.040> know<00:03:41.099> what<00:03:41.760> you<00:03:42.060> know 00:03:42.170 --> 00:03:42.180 align:start position:0% ask a question you know what you know 00:03:42.180 --> 00:03:43.729 align:start position:0% ask a question you know what you know what<00:03:42.480> makes<00:03:42.659> software<00:03:43.019> testing<00:03:43.440> difficult 00:03:43.729 --> 00:03:43.739 align:start position:0% what makes software testing difficult 00:03:43.739 --> 00:03:45.110 align:start position:0% what makes software testing difficult yeah<00:03:43.980> it's<00:03:44.159> a<00:03:44.280> bit<00:03:44.340> of<00:03:44.459> a<00:03:44.519> high<00:03:44.640> level<00:03:44.819> question 00:03:45.110 --> 00:03:45.120 align:start position:0% yeah it's a bit of a high level question 00:03:45.120 --> 00:03:46.910 align:start position:0% yeah it's a bit of a high level question you<00:03:45.420> know<00:03:45.540> apologies<00:03:45.959> for<00:03:46.140> that 00:03:46.910 --> 00:03:46.920 align:start position:0% you know apologies for that 00:03:46.920 --> 00:03:49.309 align:start position:0% you know apologies for that um<00:03:46.980> but<00:03:47.280> you<00:03:47.459> know<00:03:47.580> these<00:03:48.120> two<00:03:48.299> really<00:03:49.080> um<00:03:49.080> kind 00:03:49.309 --> 00:03:49.319 align:start position:0% um but you know these two really um kind 00:03:49.319 --> 00:03:51.710 align:start position:0% um but you know these two really um kind of<00:03:49.440> uh<00:03:50.340> sort<00:03:50.519> of<00:03:50.640> struck<00:03:51.000> me<00:03:51.120> here<00:03:51.299> like<00:03:51.480> the 00:03:51.710 --> 00:03:51.720 align:start position:0% of uh sort of struck me here like the 00:03:51.720 --> 00:03:53.809 align:start position:0% of uh sort of struck me here like the first<00:03:51.840> one<00:03:52.080> you<00:03:52.680> know<00:03:52.799> this<00:03:52.980> is<00:03:53.040> the<00:03:53.220> basically 00:03:53.809 --> 00:03:53.819 align:start position:0% first one you know this is the basically 00:03:53.819 --> 00:03:55.970 align:start position:0% first one you know this is the basically fundamentally<00:03:54.480> this<00:03:55.379> is<00:03:55.440> an<00:03:55.620> impossible 00:03:55.970 --> 00:03:55.980 align:start position:0% fundamentally this is an impossible 00:03:55.980 --> 00:03:58.369 align:start position:0% fundamentally this is an impossible requirement<00:03:56.519> because<00:03:56.940> absence<00:03:57.840> of<00:03:58.019> evidence 00:03:58.369 --> 00:03:58.379 align:start position:0% requirement because absence of evidence 00:03:58.379 --> 00:04:01.009 align:start position:0% requirement because absence of evidence is<00:03:58.860> not<00:03:59.040> the<00:03:59.220> evidence<00:03:59.459> of<00:03:59.760> absence<00:04:00.120> and<00:04:00.840> so 00:04:01.009 --> 00:04:01.019 align:start position:0% is not the evidence of absence and so 00:04:01.019 --> 00:04:02.990 align:start position:0% is not the evidence of absence and so often<00:04:01.560> we<00:04:01.680> run<00:04:01.860> these<00:04:02.220> simulations<00:04:02.640> in 00:04:02.990 --> 00:04:03.000 align:start position:0% often we run these simulations in 00:04:03.000 --> 00:04:05.149 align:start position:0% often we run these simulations in parallel<00:04:03.299> universes<00:04:03.799> hitting<00:04:04.799> you<00:04:05.040> know 00:04:05.149 --> 00:04:05.159 align:start position:0% parallel universes hitting you know 00:04:05.159 --> 00:04:08.089 align:start position:0% parallel universes hitting you know hitting<00:04:05.459> a<00:04:05.640> whole<00:04:05.760> host<00:04:06.000> of<00:04:06.299> code<00:04:06.599> and<00:04:07.560> it's 00:04:08.089 --> 00:04:08.099 align:start position:0% hitting a whole host of code and it's 00:04:08.099 --> 00:04:11.210 align:start position:0% hitting a whole host of code and it's clear<00:04:08.400> and<00:04:08.879> you're<00:04:09.000> like<00:04:09.180> well<00:04:09.420> is<00:04:10.200> that<00:04:10.379> good 00:04:11.210 --> 00:04:11.220 align:start position:0% clear and you're like well is that good 00:04:11.220 --> 00:04:13.130 align:start position:0% clear and you're like well is that good who<00:04:11.760> knows<00:04:12.000> like<00:04:12.239> you<00:04:12.420> know<00:04:12.480> we<00:04:12.659> we<00:04:12.840> can<00:04:13.019> only 00:04:13.130 --> 00:04:13.140 align:start position:0% who knows like you know we we can only 00:04:13.140 --> 00:04:14.390 align:start position:0% who knows like you know we we can only really<00:04:13.319> understand<00:04:13.620> how<00:04:13.980> much<00:04:14.099> coverage 00:04:14.390 --> 00:04:14.400 align:start position:0% really understand how much coverage 00:04:14.400 --> 00:04:17.210 align:start position:0% really understand how much coverage we've<00:04:14.640> got<00:04:14.819> and<00:04:15.060> it<00:04:16.019> may<00:04:16.139> be<00:04:16.320> maybe<00:04:16.799> good<00:04:17.040> maybe 00:04:17.210 --> 00:04:17.220 align:start position:0% we've got and it may be maybe good maybe 00:04:17.220 --> 00:04:19.670 align:start position:0% we've got and it may be maybe good maybe bad<00:04:17.459> who<00:04:17.760> knows<00:04:18.000> so<00:04:18.419> that's<00:04:19.320> that's<00:04:19.500> a 00:04:19.670 --> 00:04:19.680 align:start position:0% bad who knows so that's that's a 00:04:19.680 --> 00:04:21.170 align:start position:0% bad who knows so that's that's a phenomenal<00:04:20.040> kind<00:04:20.220> of<00:04:20.340> you<00:04:20.519> know<00:04:20.639> kind<00:04:20.760> of<00:04:20.940> you 00:04:21.170 --> 00:04:21.180 align:start position:0% phenomenal kind of you know kind of you 00:04:21.180 --> 00:04:23.810 align:start position:0% phenomenal kind of you know kind of you know<00:04:21.299> requirement<00:04:21.900> the<00:04:22.620> the<00:04:22.740> second<00:04:23.040> one<00:04:23.280> is 00:04:23.810 --> 00:04:23.820 align:start position:0% know requirement the the second one is 00:04:23.820 --> 00:04:25.610 align:start position:0% know requirement the the second one is then<00:04:24.060> about<00:04:24.300> kind<00:04:24.660> of<00:04:24.720> understanding<00:04:25.199> like 00:04:25.610 --> 00:04:25.620 align:start position:0% then about kind of understanding like 00:04:25.620 --> 00:04:27.110 align:start position:0% then about kind of understanding like testers<00:04:25.979> have<00:04:26.160> to<00:04:26.280> think<00:04:26.400> about<00:04:26.580> all<00:04:26.880> those 00:04:27.110 --> 00:04:27.120 align:start position:0% testers have to think about all those 00:04:27.120 --> 00:04:29.629 align:start position:0% testers have to think about all those possible<00:04:27.540> scenarios<00:04:28.139> where<00:04:29.100> issues<00:04:29.520> may 00:04:29.629 --> 00:04:29.639 align:start position:0% possible scenarios where issues may 00:04:29.639 --> 00:04:31.490 align:start position:0% possible scenarios where issues may arise<00:04:30.000> and<00:04:30.240> ensure<00:04:30.660> that<00:04:30.960> they<00:04:31.080> are<00:04:31.259> handled 00:04:31.490 --> 00:04:31.500 align:start position:0% arise and ensure that they are handled 00:04:31.500 --> 00:04:34.370 align:start position:0% arise and ensure that they are handled by<00:04:31.680> the<00:04:31.860> code<00:04:31.979> and<00:04:32.280> you<00:04:33.060> know<00:04:33.120> that's<00:04:33.360> just<00:04:33.540> not 00:04:34.370 --> 00:04:34.380 align:start position:0% by the code and you know that's just not 00:04:34.380 --> 00:04:36.530 align:start position:0% by the code and you know that's just not it's<00:04:34.680> just<00:04:35.520> like<00:04:35.699> how<00:04:35.940> do<00:04:36.060> you<00:04:36.120> how<00:04:36.360> do<00:04:36.479> you 00:04:36.530 --> 00:04:36.540 align:start position:0% it's just like how do you how do you 00:04:36.540 --> 00:04:38.150 align:start position:0% it's just like how do you how do you approach<00:04:36.780> that<00:04:37.020> with<00:04:37.259> a<00:04:37.380> distributed<00:04:37.919> you 00:04:38.150 --> 00:04:38.160 align:start position:0% approach that with a distributed you 00:04:38.160 --> 00:04:39.830 align:start position:0% approach that with a distributed you know<00:04:38.280> kind<00:04:38.460> of<00:04:38.580> architecture<00:04:39.300> like<00:04:39.540> we<00:04:39.720> have 00:04:39.830 --> 00:04:39.840 align:start position:0% know kind of architecture like we have 00:04:39.840 --> 00:04:41.090 align:start position:0% know kind of architecture like we have with<00:04:39.960> ethereum 00:04:41.090 --> 00:04:41.100 align:start position:0% with ethereum 00:04:41.100 --> 00:04:43.010 align:start position:0% with ethereum um<00:04:41.220> we've<00:04:42.000> got<00:04:42.180> a<00:04:42.360> whole<00:04:42.479> host<00:04:42.660> of<00:04:42.840> different 00:04:43.010 --> 00:04:43.020 align:start position:0% um we've got a whole host of different 00:04:43.020 --> 00:04:44.930 align:start position:0% um we've got a whole host of different clients<00:04:43.500> using<00:04:44.160> different<00:04:44.280> architectures 00:04:44.930 --> 00:04:44.940 align:start position:0% clients using different architectures 00:04:44.940 --> 00:04:46.850 align:start position:0% clients using different architectures we've<00:04:45.600> got<00:04:45.720> the<00:04:45.840> execution<00:04:46.199> layout<00:04:46.620> we've<00:04:46.800> got 00:04:46.850 --> 00:04:46.860 align:start position:0% we've got the execution layout we've got 00:04:46.860 --> 00:04:49.670 align:start position:0% we've got the execution layout we've got the<00:04:46.979> consensus<00:04:47.400> layer<00:04:47.780> it's<00:04:48.780> just<00:04:49.020> it's 00:04:49.670 --> 00:04:49.680 align:start position:0% the consensus layer it's just it's 00:04:49.680 --> 00:04:51.469 align:start position:0% the consensus layer it's just it's amazing<00:04:50.040> to<00:04:50.220> see<00:04:50.340> it<00:04:50.460> actually<00:04:50.639> working<00:04:50.940> and 00:04:51.469 --> 00:04:51.479 align:start position:0% amazing to see it actually working and 00:04:51.479 --> 00:04:53.749 align:start position:0% amazing to see it actually working and and<00:04:51.660> but<00:04:51.960> the<00:04:52.139> complexity<00:04:52.680> of<00:04:52.979> that<00:04:53.160> and<00:04:53.639> the 00:04:53.749 --> 00:04:53.759 align:start position:0% and but the complexity of that and the 00:04:53.759 --> 00:04:55.730 align:start position:0% and but the complexity of that and the is<00:04:54.060> just<00:04:54.240> is<00:04:54.419> just<00:04:54.600> phenomenal 00:04:55.730 --> 00:04:55.740 align:start position:0% is just is just phenomenal 00:04:55.740 --> 00:04:56.810 align:start position:0% is just is just phenomenal um 00:04:56.810 --> 00:04:56.820 align:start position:0% um 00:04:56.820 --> 00:04:58.730 align:start position:0% um if<00:04:57.300> we<00:04:57.419> then<00:04:57.540> look<00:04:57.720> at<00:04:57.900> kind<00:04:58.080> of<00:04:58.139> what<00:04:58.380> ethereum 00:04:58.730 --> 00:04:58.740 align:start position:0% if we then look at kind of what ethereum 00:04:58.740 --> 00:05:00.350 align:start position:0% if we then look at kind of what ethereum has<00:04:58.919> done<00:04:59.040> to<00:04:59.160> approach<00:04:59.580> this<00:04:59.759> task<00:04:59.940> and<00:05:00.180> this 00:05:00.350 --> 00:05:00.360 align:start position:0% has done to approach this task and this 00:05:00.360 --> 00:05:01.550 align:start position:0% has done to approach this task and this is<00:05:00.479> you<00:05:00.660> know<00:05:00.720> this<00:05:00.840> is<00:05:01.020> not<00:05:01.080> just<00:05:01.259> looking 00:05:01.550 --> 00:05:01.560 align:start position:0% is you know this is not just looking 00:05:01.560 --> 00:05:04.129 align:start position:0% is you know this is not just looking specific<00:05:01.919> antithesis<00:05:02.820> we<00:05:03.300> are<00:05:03.479> a<00:05:03.600> part<00:05:03.780> of<00:05:03.960> the 00:05:04.129 --> 00:05:04.139 align:start position:0% specific antithesis we are a part of the 00:05:04.139 --> 00:05:05.210 align:start position:0% specific antithesis we are a part of the equation 00:05:05.210 --> 00:05:05.220 align:start position:0% equation 00:05:05.220 --> 00:05:06.590 align:start position:0% equation um<00:05:05.280> and<00:05:05.400> I<00:05:05.699> think<00:05:05.880> we're<00:05:06.060> very<00:05:06.180> much<00:05:06.300> of<00:05:06.479> a 00:05:06.590 --> 00:05:06.600 align:start position:0% um and I think we're very much of a 00:05:06.600 --> 00:05:08.570 align:start position:0% um and I think we're very much of a complementary<00:05:07.080> is<00:05:07.259> is<00:05:07.620> that<00:05:07.860> ethereum<00:05:08.400> is 00:05:08.570 --> 00:05:08.580 align:start position:0% complementary is is that ethereum is 00:05:08.580 --> 00:05:11.270 align:start position:0% complementary is is that ethereum is using<00:05:08.820> unit<00:05:09.060> testing<00:05:09.600> test<00:05:10.080> Nets<00:05:10.620> we've<00:05:10.979> got<00:05:11.100> a 00:05:11.270 --> 00:05:11.280 align:start position:0% using unit testing test Nets we've got a 00:05:11.280 --> 00:05:12.830 align:start position:0% using unit testing test Nets we've got a list<00:05:11.460> of<00:05:11.639> Shadow<00:05:11.880> forks<00:05:12.360> and<00:05:12.540> test<00:05:12.660> net 00:05:12.830 --> 00:05:12.840 align:start position:0% list of Shadow forks and test net 00:05:12.840 --> 00:05:14.629 align:start position:0% list of Shadow forks and test net mergers<00:05:13.199> occurred 00:05:14.629 --> 00:05:14.639 align:start position:0% mergers occurred 00:05:14.639 --> 00:05:16.670 align:start position:0% mergers occurred um<00:05:14.759> some<00:05:15.419> technologies<00:05:15.780> that<00:05:15.960> are<00:05:16.320> being<00:05:16.500> used 00:05:16.670 --> 00:05:16.680 align:start position:0% um some technologies that are being used 00:05:16.680 --> 00:05:18.590 align:start position:0% um some technologies that are being used called<00:05:16.919> Hive<00:05:17.220> and<00:05:17.460> ketosis 00:05:18.590 --> 00:05:18.600 align:start position:0% called Hive and ketosis 00:05:18.600 --> 00:05:20.810 align:start position:0% called Hive and ketosis um<00:05:18.660> that<00:05:19.380> do<00:05:19.500> similar 00:05:20.810 --> 00:05:20.820 align:start position:0% um that do similar 00:05:20.820 --> 00:05:23.510 align:start position:0% um that do similar um<00:05:20.960> heaters<00:05:21.960> to<00:05:22.199> the<00:05:22.320> equation<00:05:22.620> we<00:05:23.160> then<00:05:23.340> have 00:05:23.510 --> 00:05:23.520 align:start position:0% um heaters to the equation we then have 00:05:23.520 --> 00:05:24.950 align:start position:0% um heaters to the equation we then have antithesis<00:05:24.060> that<00:05:24.300> is<00:05:24.419> then<00:05:24.600> doing<00:05:24.780> this 00:05:24.950 --> 00:05:24.960 align:start position:0% antithesis that is then doing this 00:05:24.960 --> 00:05:28.070 align:start position:0% antithesis that is then doing this deterministic<00:05:25.820> piece<00:05:26.820> which<00:05:27.060> allows<00:05:27.720> us<00:05:27.780> to 00:05:28.070 --> 00:05:28.080 align:start position:0% deterministic piece which allows us to 00:05:28.080 --> 00:05:30.230 align:start position:0% deterministic piece which allows us to to<00:05:28.199> Really<00:05:28.860> you<00:05:29.220> know<00:05:29.280> get<00:05:29.639> into<00:05:29.759> the<00:05:29.940> detail 00:05:30.230 --> 00:05:30.240 align:start position:0% to Really you know get into the detail 00:05:30.240 --> 00:05:33.110 align:start position:0% to Really you know get into the detail of<00:05:30.479> of<00:05:30.840> all<00:05:31.199> the<00:05:31.380> different<00:05:31.560> iterations 00:05:33.110 --> 00:05:33.120 align:start position:0% of of all the different iterations 00:05:33.120 --> 00:05:35.029 align:start position:0% of of all the different iterations um<00:05:33.180> that<00:05:33.360> are<00:05:33.479> possible<00:05:33.840> and<00:05:34.259> then<00:05:34.380> we<00:05:34.620> we<00:05:34.860> have 00:05:35.029 --> 00:05:35.039 align:start position:0% um that are possible and then we we have 00:05:35.039 --> 00:05:36.469 align:start position:0% um that are possible and then we we have a<00:05:35.160> host<00:05:35.280> of<00:05:35.460> different<00:05:35.580> fuzzing<00:05:36.060> technologies 00:05:36.469 --> 00:05:36.479 align:start position:0% a host of different fuzzing technologies 00:05:36.479 --> 00:05:38.330 align:start position:0% a host of different fuzzing technologies that<00:05:36.840> the<00:05:37.020> ethereum<00:05:37.380> are<00:05:37.500> using 00:05:38.330 --> 00:05:38.340 align:start position:0% that the ethereum are using 00:05:38.340 --> 00:05:40.850 align:start position:0% that the ethereum are using um<00:05:38.460> to<00:05:38.639> to<00:05:38.820> really<00:05:39.000> try<00:05:39.300> and<00:05:39.479> isolate<00:05:40.320> and<00:05:40.560> kind 00:05:40.850 --> 00:05:40.860 align:start position:0% um to to really try and isolate and kind 00:05:40.860 --> 00:05:43.850 align:start position:0% um to to really try and isolate and kind of<00:05:40.979> hammer<00:05:41.400> areas<00:05:42.180> that<00:05:42.479> are<00:05:42.600> of<00:05:42.720> concern<00:05:43.440> so 00:05:43.850 --> 00:05:43.860 align:start position:0% of hammer areas that are of concern so 00:05:43.860 --> 00:05:46.430 align:start position:0% of hammer areas that are of concern so you<00:05:44.460> know<00:05:44.580> throughout<00:05:45.180> the<00:05:45.300> entire<00:05:45.600> year<00:05:45.840> you 00:05:46.430 --> 00:05:46.440 align:start position:0% you know throughout the entire year you 00:05:46.440 --> 00:05:48.050 align:start position:0% you know throughout the entire year you know<00:05:46.560> a<00:05:46.860> huge<00:05:47.220> amount<00:05:47.460> of<00:05:47.520> testing<00:05:47.820> has<00:05:47.940> been 00:05:48.050 --> 00:05:48.060 align:start position:0% know a huge amount of testing has been 00:05:48.060 --> 00:05:50.029 align:start position:0% know a huge amount of testing has been done<00:05:48.240> and<00:05:48.780> on<00:05:48.960> top<00:05:49.139> of<00:05:49.259> that<00:05:49.380> they've<00:05:49.800> also 00:05:50.029 --> 00:05:50.039 align:start position:0% done and on top of that they've also 00:05:50.039 --> 00:05:52.129 align:start position:0% done and on top of that they've also used<00:05:50.160> static<00:05:50.520> analysis<00:05:50.940> to<00:05:51.240> just<00:05:51.660> you<00:05:52.080> know 00:05:52.129 --> 00:05:52.139 align:start position:0% used static analysis to just you know 00:05:52.139 --> 00:05:54.290 align:start position:0% used static analysis to just you know help<00:05:52.320> with<00:05:52.680> doing<00:05:53.280> code<00:05:53.520> Audits<00:05:54.000> and<00:05:54.120> making 00:05:54.290 --> 00:05:54.300 align:start position:0% help with doing code Audits and making 00:05:54.300 --> 00:05:56.390 align:start position:0% help with doing code Audits and making sure<00:05:54.600> that<00:05:55.139> we<00:05:55.259> catch<00:05:55.560> things<00:05:55.680> before<00:05:56.039> the 00:05:56.390 --> 00:05:56.400 align:start position:0% sure that we catch things before the 00:05:56.400 --> 00:05:59.810 align:start position:0% sure that we catch things before the merge<00:05:57.060> was<00:05:57.539> to<00:05:57.840> take<00:05:57.960> place<00:05:58.220> I'd<00:05:59.220> step<00:05:59.520> back<00:05:59.639> a 00:05:59.810 --> 00:05:59.820 align:start position:0% merge was to take place I'd step back a 00:05:59.820 --> 00:06:00.950 align:start position:0% merge was to take place I'd step back a little<00:05:59.940> bit<00:06:00.060> in<00:06:00.240> terms<00:06:00.419> of<00:06:00.479> kind<00:06:00.720> of<00:06:00.840> the 00:06:00.950 --> 00:06:00.960 align:start position:0% little bit in terms of kind of the 00:06:00.960 --> 00:06:03.590 align:start position:0% little bit in terms of kind of the testing<00:06:01.380> as<00:06:01.500> hard<00:06:01.680> statement<00:06:02.160> you<00:06:02.759> know<00:06:02.940> it<00:06:03.479> is 00:06:03.590 --> 00:06:03.600 align:start position:0% testing as hard statement you know it is 00:06:03.600 --> 00:06:05.330 align:start position:0% testing as hard statement you know it is a<00:06:03.720> phenomenal<00:06:04.139> kind<00:06:04.440> of<00:06:04.500> like<00:06:05.039> you<00:06:05.280> know 00:06:05.330 --> 00:06:05.340 align:start position:0% a phenomenal kind of like you know 00:06:05.340 --> 00:06:07.129 align:start position:0% a phenomenal kind of like you know obstacle<00:06:05.880> to<00:06:06.000> try<00:06:06.180> and<00:06:06.300> get<00:06:06.419> over<00:06:06.539> like<00:06:06.780> how 00:06:07.129 --> 00:06:07.139 align:start position:0% obstacle to try and get over like how 00:06:07.139 --> 00:06:09.830 align:start position:0% obstacle to try and get over like how how<00:06:07.560> do<00:06:07.800> we<00:06:08.039> find<00:06:08.340> every<00:06:08.880> iteration<00:06:09.360> and<00:06:09.600> how 00:06:09.830 --> 00:06:09.840 align:start position:0% how do we find every iteration and how 00:06:09.840 --> 00:06:12.170 align:start position:0% how do we find every iteration and how do<00:06:09.960> we<00:06:10.020> find<00:06:10.199> those<00:06:10.500> hard<00:06:10.979> to<00:06:11.100> reach<00:06:11.460> bugs<00:06:11.880> that 00:06:12.170 --> 00:06:12.180 align:start position:0% do we find those hard to reach bugs that 00:06:12.180 --> 00:06:15.110 align:start position:0% do we find those hard to reach bugs that you<00:06:12.780> know<00:06:12.900> may<00:06:13.320> not<00:06:13.500> be<00:06:13.740> common<00:06:14.100> ground<00:06:14.400> but<00:06:14.820> if 00:06:15.110 --> 00:06:15.120 align:start position:0% you know may not be common ground but if 00:06:15.120 --> 00:06:17.570 align:start position:0% you know may not be common ground but if they<00:06:15.240> do<00:06:15.419> occur<00:06:15.780> will<00:06:16.139> be<00:06:16.320> catastrophic 00:06:17.570 --> 00:06:17.580 align:start position:0% they do occur will be catastrophic 00:06:17.580 --> 00:06:19.550 align:start position:0% they do occur will be catastrophic um<00:06:17.639> and<00:06:17.820> so<00:06:18.060> if<00:06:18.840> we<00:06:18.960> just<00:06:19.080> look<00:06:19.199> at<00:06:19.320> the<00:06:19.440> right 00:06:19.550 --> 00:06:19.560 align:start position:0% um and so if we just look at the right 00:06:19.560 --> 00:06:20.870 align:start position:0% um and so if we just look at the right hand<00:06:19.740> side 00:06:20.870 --> 00:06:20.880 align:start position:0% hand side 00:06:20.880 --> 00:06:22.790 align:start position:0% hand side this<00:06:21.300> is<00:06:21.360> a<00:06:21.539> representation<00:06:22.440> of<00:06:22.680> a 00:06:22.790 --> 00:06:22.800 align:start position:0% this is a representation of a 00:06:22.800 --> 00:06:24.710 align:start position:0% this is a representation of a distribution<00:06:23.160> Network<00:06:23.460> so<00:06:24.000> on<00:06:24.479> the<00:06:24.600> right 00:06:24.710 --> 00:06:24.720 align:start position:0% distribution Network so on the right 00:06:24.720 --> 00:06:25.610 align:start position:0% distribution Network so on the right we're<00:06:24.840> going<00:06:24.960> to<00:06:25.020> we're<00:06:25.139> going<00:06:25.259> to<00:06:25.319> call<00:06:25.440> this 00:06:25.610 --> 00:06:25.620 align:start position:0% we're going to we're going to call this 00:06:25.620 --> 00:06:27.529 align:start position:0% we're going to we're going to call this node<00:06:25.919> we're<00:06:26.280> going<00:06:26.400> to<00:06:26.460> call<00:06:26.580> this<00:06:26.699> node 00:06:27.529 --> 00:06:27.539 align:start position:0% node we're going to call this node 00:06:27.539 --> 00:06:29.390 align:start position:0% node we're going to call this node um<00:06:27.600> you<00:06:27.720> know<00:06:27.840> using<00:06:28.080> Lighthouse<00:06:28.440> and<00:06:28.680> Geth<00:06:28.979> so 00:06:29.390 --> 00:06:29.400 align:start position:0% um you know using Lighthouse and Geth so 00:06:29.400 --> 00:06:30.590 align:start position:0% um you know using Lighthouse and Geth so the<00:06:29.580> lighthouse<00:06:29.880> and<00:06:30.000> gether<00:06:30.180> running<00:06:30.360> on 00:06:30.590 --> 00:06:30.600 align:start position:0% the lighthouse and gether running on 00:06:30.600 --> 00:06:31.850 align:start position:0% the lighthouse and gether running on this<00:06:30.720> node<00:06:31.020> they're<00:06:31.319> running<00:06:31.560> on<00:06:31.740> an 00:06:31.850 --> 00:06:31.860 align:start position:0% this node they're running on an 00:06:31.860 --> 00:06:35.270 align:start position:0% this node they're running on an operating<00:06:32.160> system<00:06:32.460> you<00:06:33.120> know<00:06:33.240> leveraging<00:06:33.600> CPU 00:06:35.270 --> 00:06:35.280 align:start position:0% operating system you know leveraging CPU 00:06:35.280 --> 00:06:37.070 align:start position:0% operating system you know leveraging CPU um<00:06:35.400> we've<00:06:35.699> got<00:06:35.759> a<00:06:35.880> file<00:06:36.060> system<00:06:36.240> we've<00:06:37.020> got 00:06:37.070 --> 00:06:37.080 align:start position:0% um we've got a file system we've got 00:06:37.080 --> 00:06:38.930 align:start position:0% um we've got a file system we've got different<00:06:37.259> processes<00:06:37.740> happening<00:06:38.160> and<00:06:38.819> then 00:06:38.930 --> 00:06:38.940 align:start position:0% different processes happening and then 00:06:38.940 --> 00:06:40.010 align:start position:0% different processes happening and then inside<00:06:39.060> those<00:06:39.419> processes<00:06:39.780> we've<00:06:39.960> got 00:06:40.010 --> 00:06:40.020 align:start position:0% inside those processes we've got 00:06:40.020 --> 00:06:41.270 align:start position:0% inside those processes we've got different<00:06:40.139> threads<00:06:40.440> being<00:06:40.620> used<00:06:40.740> as<00:06:40.919> well<00:06:41.039> so 00:06:41.270 --> 00:06:41.280 align:start position:0% different threads being used as well so 00:06:41.280 --> 00:06:44.270 align:start position:0% different threads being used as well so just<00:06:41.880> in<00:06:42.060> its<00:06:42.419> own<00:06:42.479> sort<00:06:43.259> of<00:06:43.380> node<00:06:43.680> there's<00:06:44.039> a 00:06:44.270 --> 00:06:44.280 align:start position:0% just in its own sort of node there's a 00:06:44.280 --> 00:06:45.710 align:start position:0% just in its own sort of node there's a lot<00:06:44.340> of<00:06:44.460> complexity<00:06:44.940> about<00:06:45.180> what's<00:06:45.419> going<00:06:45.600> on 00:06:45.710 --> 00:06:45.720 align:start position:0% lot of complexity about what's going on 00:06:45.720 --> 00:06:47.510 align:start position:0% lot of complexity about what's going on and<00:06:45.960> we<00:06:46.080> can<00:06:46.199> we<00:06:46.560> can<00:06:46.680> test<00:06:46.800> the<00:06:46.979> nodes<00:06:47.220> we<00:06:47.400> can 00:06:47.510 --> 00:06:47.520 align:start position:0% and we can we can test the nodes we can 00:06:47.520 --> 00:06:49.430 align:start position:0% and we can we can test the nodes we can test<00:06:47.639> maybe<00:06:47.880> a<00:06:48.120> combination<00:06:48.479> of<00:06:48.660> Lighthouse 00:06:49.430 --> 00:06:49.440 align:start position:0% test maybe a combination of Lighthouse 00:06:49.440 --> 00:06:51.409 align:start position:0% test maybe a combination of Lighthouse and<00:06:49.620> guests<00:06:49.979> working<00:06:50.160> together<00:06:50.400> making<00:06:51.180> sure 00:06:51.409 --> 00:06:51.419 align:start position:0% and guests working together making sure 00:06:51.419 --> 00:06:53.270 align:start position:0% and guests working together making sure that<00:06:51.600> we're<00:06:51.720> kind<00:06:51.960> of<00:06:52.080> you<00:06:52.500> know<00:06:52.620> pushing<00:06:53.160> the 00:06:53.270 --> 00:06:53.280 align:start position:0% that we're kind of you know pushing the 00:06:53.280 --> 00:06:54.409 align:start position:0% that we're kind of you know pushing the boundaries<00:06:53.580> but 00:06:54.409 --> 00:06:54.419 align:start position:0% boundaries but 00:06:54.419 --> 00:06:56.629 align:start position:0% boundaries but if<00:06:54.900> we<00:06:55.020> then<00:06:55.139> think<00:06:55.319> about<00:06:55.440> how<00:06:55.740> we<00:06:55.919> then<00:06:56.160> have 00:06:56.629 --> 00:06:56.639 align:start position:0% if we then think about how we then have 00:06:56.639 --> 00:06:59.029 align:start position:0% if we then think about how we then have a<00:06:57.120> network<00:06:57.300> and<00:06:57.960> we<00:06:58.199> have<00:06:58.319> a<00:06:58.500> whole<00:06:58.680> host<00:06:58.860> of 00:06:59.029 --> 00:06:59.039 align:start position:0% a network and we have a whole host of 00:06:59.039 --> 00:07:02.210 align:start position:0% a network and we have a whole host of different<00:06:59.160> nodes<00:06:59.460> running<00:07:00.419> together<00:07:01.039> and<00:07:02.039> may 00:07:02.210 --> 00:07:02.220 align:start position:0% different nodes running together and may 00:07:02.220 --> 00:07:03.529 align:start position:0% different nodes running together and may have<00:07:02.340> other<00:07:02.520> underlying<00:07:03.120> pieces<00:07:03.360> like 00:07:03.529 --> 00:07:03.539 align:start position:0% have other underlying pieces like 00:07:03.539 --> 00:07:05.090 align:start position:0% have other underlying pieces like databases<00:07:04.020> other<00:07:04.259> pieces<00:07:04.560> kind<00:07:04.860> of<00:07:04.979> actually 00:07:05.090 --> 00:07:05.100 align:start position:0% databases other pieces kind of actually 00:07:05.100 --> 00:07:06.890 align:start position:0% databases other pieces kind of actually on<00:07:05.639> on<00:07:05.819> top<00:07:06.000> of<00:07:06.120> that 00:07:06.890 --> 00:07:06.900 align:start position:0% on on top of that 00:07:06.900 --> 00:07:08.749 align:start position:0% on on top of that um<00:07:06.960> the<00:07:07.620> the<00:07:07.620> complexity<00:07:08.220> of<00:07:08.520> all<00:07:08.639> those 00:07:08.749 --> 00:07:08.759 align:start position:0% um the the complexity of all those 00:07:08.759 --> 00:07:09.950 align:start position:0% um the the complexity of all those different<00:07:09.000> communication<00:07:09.479> channels 00:07:09.950 --> 00:07:09.960 align:start position:0% different communication channels 00:07:09.960 --> 00:07:12.710 align:start position:0% different communication channels operating<00:07:10.580> just<00:07:11.580> means<00:07:11.880> that<00:07:12.060> the<00:07:12.360> search 00:07:12.710 --> 00:07:12.720 align:start position:0% operating just means that the search 00:07:12.720 --> 00:07:15.890 align:start position:0% operating just means that the search space<00:07:13.020> for<00:07:13.680> Hidden<00:07:14.160> Away<00:07:14.280> Little<00:07:14.639> Gems<00:07:15.120> I<00:07:15.780> call 00:07:15.890 --> 00:07:15.900 align:start position:0% space for Hidden Away Little Gems I call 00:07:15.900 --> 00:07:17.150 align:start position:0% space for Hidden Away Little Gems I call them<00:07:16.020> gems<00:07:16.380> but<00:07:16.500> you<00:07:16.620> know<00:07:16.740> they're<00:07:16.800> bugs 00:07:17.150 --> 00:07:17.160 align:start position:0% them gems but you know they're bugs 00:07:17.160 --> 00:07:18.050 align:start position:0% them gems but you know they're bugs basically 00:07:18.050 --> 00:07:18.060 align:start position:0% basically 00:07:18.060 --> 00:07:19.969 align:start position:0% basically those<00:07:18.479> those<00:07:18.539> they<00:07:19.020> can<00:07:19.139> hide<00:07:19.259> away<00:07:19.440> for<00:07:19.680> a 00:07:19.969 --> 00:07:19.979 align:start position:0% those those they can hide away for a 00:07:19.979 --> 00:07:22.189 align:start position:0% those those they can hide away for a long<00:07:20.099> time<00:07:20.220> and<00:07:20.520> you<00:07:21.360> may<00:07:21.479> never<00:07:21.660> find<00:07:21.960> that 00:07:22.189 --> 00:07:22.199 align:start position:0% long time and you may never find that 00:07:22.199 --> 00:07:24.770 align:start position:0% long time and you may never find that search<00:07:22.940> when<00:07:23.940> you're<00:07:24.060> looking<00:07:24.240> at<00:07:24.419> testing 00:07:24.770 --> 00:07:24.780 align:start position:0% search when you're looking at testing 00:07:24.780 --> 00:07:26.210 align:start position:0% search when you're looking at testing you<00:07:24.900> may<00:07:24.960> never<00:07:25.139> find<00:07:25.380> that<00:07:25.620> that<00:07:25.860> particular 00:07:26.210 --> 00:07:26.220 align:start position:0% you may never find that that particular 00:07:26.220 --> 00:07:28.790 align:start position:0% you may never find that that particular condition<00:07:26.599> where<00:07:27.599> the<00:07:27.720> network<00:07:27.900> was<00:07:28.259> slow<00:07:28.500> and 00:07:28.790 --> 00:07:28.800 align:start position:0% condition where the network was slow and 00:07:28.800 --> 00:07:29.990 align:start position:0% condition where the network was slow and there's<00:07:28.979> some<00:07:29.160> there's<00:07:29.400> a<00:07:29.520> bit<00:07:29.580> of<00:07:29.699> thread 00:07:29.990 --> 00:07:30.000 align:start position:0% there's some there's a bit of thread 00:07:30.000 --> 00:07:32.510 align:start position:0% there's some there's a bit of thread pausing<00:07:30.360> going<00:07:30.960> on<00:07:31.139> in<00:07:31.380> a<00:07:31.500> certain<00:07:31.680> node<00:07:31.979> and 00:07:32.510 --> 00:07:32.520 align:start position:0% pausing going on in a certain node and 00:07:32.520 --> 00:07:34.370 align:start position:0% pausing going on in a certain node and you<00:07:32.819> know<00:07:32.940> the<00:07:33.120> the<00:07:33.180> the<00:07:33.360> the<00:07:33.539> number<00:07:34.139> of 00:07:34.370 --> 00:07:34.380 align:start position:0% you know the the the the number of 00:07:34.380 --> 00:07:36.290 align:start position:0% you know the the the the number of things<00:07:34.740> that<00:07:35.039> have<00:07:35.220> to<00:07:35.340> happen<00:07:35.520> could<00:07:36.060> could 00:07:36.290 --> 00:07:36.300 align:start position:0% things that have to happen could could 00:07:36.300 --> 00:07:39.469 align:start position:0% things that have to happen could could have<00:07:36.479> a<00:07:36.660> bug<00:07:36.960> manifest<00:07:37.500> and<00:07:38.340> so<00:07:38.580> this<00:07:39.300> is 00:07:39.469 --> 00:07:39.479 align:start position:0% have a bug manifest and so this is 00:07:39.479 --> 00:07:41.210 align:start position:0% have a bug manifest and so this is really<00:07:39.599> where<00:07:40.020> where<00:07:40.199> we<00:07:40.680> step<00:07:40.860> in<00:07:40.979> because 00:07:41.210 --> 00:07:41.220 align:start position:0% really where where we step in because 00:07:41.220 --> 00:07:44.089 align:start position:0% really where where we step in because you<00:07:42.060> know<00:07:42.240> we<00:07:42.900> then<00:07:43.080> we<00:07:43.319> then<00:07:43.440> have<00:07:43.680> you<00:07:43.979> know 00:07:44.089 --> 00:07:44.099 align:start position:0% you know we then we then have you know 00:07:44.099 --> 00:07:45.950 align:start position:0% you know we then we then have you know the<00:07:44.460> complete<00:07:44.880> picture<00:07:45.060> and<00:07:45.419> this<00:07:45.539> is<00:07:45.660> what<00:07:45.840> we 00:07:45.950 --> 00:07:45.960 align:start position:0% the complete picture and this is what we 00:07:45.960 --> 00:07:48.050 align:start position:0% the complete picture and this is what we build<00:07:46.199> inside<00:07:46.560> our<00:07:46.860> simulation 00:07:48.050 --> 00:07:48.060 align:start position:0% build inside our simulation 00:07:48.060 --> 00:07:50.450 align:start position:0% build inside our simulation um we<00:07:48.419> have<00:07:48.539> the<00:07:49.020> ability<00:07:49.259> to<00:07:49.800> kind<00:07:50.099> of<00:07:50.160> run 00:07:50.450 --> 00:07:50.460 align:start position:0% um we have the ability to kind of run 00:07:50.460 --> 00:07:52.850 align:start position:0% um we have the ability to kind of run the<00:07:50.819> entire<00:07:51.120> collection<00:07:51.960> of<00:07:52.259> consensus 00:07:52.850 --> 00:07:52.860 align:start position:0% the entire collection of consensus 00:07:52.860 --> 00:07:56.150 align:start position:0% the entire collection of consensus clients<00:07:53.340> and<00:07:53.819> execution<00:07:54.300> clients<00:07:54.840> in<00:07:55.740> in<00:07:56.039> a 00:07:56.150 --> 00:07:56.160 align:start position:0% clients and execution clients in in a 00:07:56.160 --> 00:07:58.550 align:start position:0% clients and execution clients in in a simulation<00:07:56.580> run<00:07:57.180> it<00:07:57.360> and<00:07:58.020> and<00:07:58.259> understand 00:07:58.550 --> 00:07:58.560 align:start position:0% simulation run it and and understand 00:07:58.560 --> 00:08:01.490 align:start position:0% simulation run it and and understand exactly<00:07:59.280> kind<00:07:59.819> of<00:07:59.940> every<00:08:00.539> way<00:08:00.960> in<00:08:01.199> which<00:08:01.319> we 00:08:01.490 --> 00:08:01.500 align:start position:0% exactly kind of every way in which we 00:08:01.500 --> 00:08:03.350 align:start position:0% exactly kind of every way in which we can<00:08:01.620> actually<00:08:01.800> kind<00:08:01.979> of<00:08:02.099> see<00:08:02.280> outcomes 00:08:03.350 --> 00:08:03.360 align:start position:0% can actually kind of see outcomes 00:08:03.360 --> 00:08:04.129 align:start position:0% can actually kind of see outcomes um 00:08:04.129 --> 00:08:04.139 align:start position:0% um 00:08:04.139 --> 00:08:05.870 align:start position:0% um that's<00:08:04.680> pretty<00:08:04.919> intense<00:08:05.280> you<00:08:05.520> know<00:08:05.639> how<00:08:05.759> do 00:08:05.870 --> 00:08:05.880 align:start position:0% that's pretty intense you know how do 00:08:05.880 --> 00:08:07.969 align:start position:0% that's pretty intense you know how do you<00:08:06.000> do<00:08:06.060> that<00:08:06.180> and<00:08:06.440> fundamentally<00:08:07.440> how<00:08:07.740> do<00:08:07.860> you 00:08:07.969 --> 00:08:07.979 align:start position:0% you do that and fundamentally how do you 00:08:07.979 --> 00:08:10.430 align:start position:0% you do that and fundamentally how do you do<00:08:08.099> that<00:08:08.280> in<00:08:08.759> a<00:08:08.880> deterministic<00:08:09.419> fashion<00:08:09.780> if<00:08:10.259> we 00:08:10.430 --> 00:08:10.440 align:start position:0% do that in a deterministic fashion if we 00:08:10.440 --> 00:08:12.589 align:start position:0% do that in a deterministic fashion if we find<00:08:10.740> a<00:08:11.400> certain<00:08:11.520> situation<00:08:12.120> where 00:08:12.589 --> 00:08:12.599 align:start position:0% find a certain situation where 00:08:12.599 --> 00:08:15.529 align:start position:0% find a certain situation where Lighthouse<00:08:13.259> crashes<00:08:13.819> well<00:08:14.819> can<00:08:15.060> we<00:08:15.180> represent 00:08:15.529 --> 00:08:15.539 align:start position:0% Lighthouse crashes well can we represent 00:08:15.539 --> 00:08:17.150 align:start position:0% Lighthouse crashes well can we represent that<00:08:15.660> again<00:08:15.840> can<00:08:16.080> we<00:08:16.199> replay<00:08:16.380> it<00:08:16.680> can<00:08:16.860> we<00:08:16.979> yes 00:08:17.150 --> 00:08:17.160 align:start position:0% that again can we replay it can we yes 00:08:17.160 --> 00:08:18.290 align:start position:0% that again can we replay it can we yes the<00:08:17.340> first<00:08:17.460> thing<00:08:17.580> you<00:08:17.699> do<00:08:17.819> right<00:08:17.940> can<00:08:18.180> we 00:08:18.290 --> 00:08:18.300 align:start position:0% the first thing you do right can we 00:08:18.300 --> 00:08:20.809 align:start position:0% the first thing you do right can we reproduce<00:08:18.660> it<00:08:18.840> and<00:08:19.139> often<00:08:19.440> bugs<00:08:19.919> are<00:08:20.220> not 00:08:20.809 --> 00:08:20.819 align:start position:0% reproduce it and often bugs are not 00:08:20.819 --> 00:08:22.730 align:start position:0% reproduce it and often bugs are not reproducible<00:08:21.479> they<00:08:22.080> often<00:08:22.379> you<00:08:22.560> know<00:08:22.620> they 00:08:22.730 --> 00:08:22.740 align:start position:0% reproducible they often you know they 00:08:22.740 --> 00:08:24.230 align:start position:0% reproducible they often you know they might<00:08:22.860> try<00:08:23.039> something<00:08:23.280> different<00:08:23.580> they<00:08:24.120> might 00:08:24.230 --> 00:08:24.240 align:start position:0% might try something different they might 00:08:24.240 --> 00:08:27.409 align:start position:0% might try something different they might move<00:08:24.479> around<00:08:24.740> what<00:08:25.740> like<00:08:26.099> how<00:08:26.639> do<00:08:26.699> we<00:08:27.120> how<00:08:27.300> do 00:08:27.409 --> 00:08:27.419 align:start position:0% move around what like how do we how do 00:08:27.419 --> 00:08:29.270 align:start position:0% move around what like how do we how do we<00:08:27.539> debug<00:08:27.960> this<00:08:28.139> and<00:08:28.440> and<00:08:28.560> this<00:08:28.860> is<00:08:28.979> again 00:08:29.270 --> 00:08:29.280 align:start position:0% we debug this and and this is again 00:08:29.280 --> 00:08:32.149 align:start position:0% we debug this and and this is again where<00:08:29.699> we<00:08:30.060> step<00:08:30.240> in 00:08:32.149 --> 00:08:32.159 align:start position:0% where we step in 00:08:32.159 --> 00:08:34.850 align:start position:0% where we step in so<00:08:32.580> what<00:08:32.700> do<00:08:32.820> we<00:08:32.940> do<00:08:33.120> we<00:08:34.080> leveraged<00:08:34.500> the 00:08:34.850 --> 00:08:34.860 align:start position:0% so what do we do we leveraged the 00:08:34.860 --> 00:08:36.889 align:start position:0% so what do we do we leveraged the ability<00:08:35.039> to<00:08:35.279> Auto<00:08:35.459> generate<00:08:35.880> networks<00:08:36.539> inside 00:08:36.889 --> 00:08:36.899 align:start position:0% ability to Auto generate networks inside 00:08:36.899 --> 00:08:38.990 align:start position:0% ability to Auto generate networks inside the<00:08:37.200> simulation<00:08:37.560> environment<00:08:38.039> and<00:08:38.580> stand<00:08:38.820> up 00:08:38.990 --> 00:08:39.000 align:start position:0% the simulation environment and stand up 00:08:39.000 --> 00:08:40.550 align:start position:0% the simulation environment and stand up all<00:08:39.180> the<00:08:39.300> containers<00:08:39.659> that<00:08:39.959> were<00:08:40.080> necessary 00:08:40.550 --> 00:08:40.560 align:start position:0% all the containers that were necessary 00:08:40.560 --> 00:08:42.409 align:start position:0% all the containers that were necessary to<00:08:40.800> bring<00:08:41.099> up<00:08:41.279> ethereum 00:08:42.409 --> 00:08:42.419 align:start position:0% to bring up ethereum 00:08:42.419 --> 00:08:45.110 align:start position:0% to bring up ethereum um<00:08:42.479> we<00:08:43.260> then<00:08:43.380> were<00:08:43.560> able<00:08:43.740> to<00:08:43.860> then<00:08:44.099> use<00:08:44.399> Network 00:08:45.110 --> 00:08:45.120 align:start position:0% um we then were able to then use Network 00:08:45.120 --> 00:08:47.690 align:start position:0% um we then were able to then use Network faults<00:08:45.779> and<00:08:46.080> other<00:08:46.260> types<00:08:46.500> of<00:08:46.560> faults<00:08:46.980> to<00:08:47.279> just 00:08:47.690 --> 00:08:47.700 align:start position:0% faults and other types of faults to just 00:08:47.700 --> 00:08:49.490 align:start position:0% faults and other types of faults to just inject<00:08:48.360> chaos<00:08:48.779> into<00:08:49.140> that<00:08:49.320> running 00:08:49.490 --> 00:08:49.500 align:start position:0% inject chaos into that running 00:08:49.500 --> 00:08:50.810 align:start position:0% inject chaos into that running environment 00:08:50.810 --> 00:08:50.820 align:start position:0% environment 00:08:50.820 --> 00:08:52.310 align:start position:0% environment um obviously<00:08:51.420> it's<00:08:51.540> great<00:08:51.779> to<00:08:51.899> see<00:08:52.080> the 00:08:52.310 --> 00:08:52.320 align:start position:0% um obviously it's great to see the 00:08:52.320 --> 00:08:54.350 align:start position:0% um obviously it's great to see the software<00:08:52.620> handle<00:08:53.339> that<00:08:53.519> it's<00:08:53.820> designed<00:08:54.240> to 00:08:54.350 --> 00:08:54.360 align:start position:0% software handle that it's designed to 00:08:54.360 --> 00:08:56.449 align:start position:0% software handle that it's designed to handle<00:08:54.720> these<00:08:55.019> types<00:08:55.200> of<00:08:55.260> things<00:08:55.440> so<00:08:55.860> you<00:08:56.339> know 00:08:56.449 --> 00:08:56.459 align:start position:0% handle these types of things so you know 00:08:56.459 --> 00:08:59.630 align:start position:0% handle these types of things so you know under<00:08:56.940> duress<00:08:57.420> we<00:08:57.899> see<00:08:58.080> things<00:08:58.380> going<00:08:58.620> wrong 00:08:59.630 --> 00:08:59.640 align:start position:0% under duress we see things going wrong 00:08:59.640 --> 00:09:01.610 align:start position:0% under duress we see things going wrong um<00:08:59.700> and<00:09:00.060> we<00:09:00.180> we<00:09:00.360> basically<00:09:00.779> use<00:09:01.080> fuzzing 00:09:01.610 --> 00:09:01.620 align:start position:0% um and we we basically use fuzzing 00:09:01.620 --> 00:09:03.710 align:start position:0% um and we we basically use fuzzing technology<00:09:02.040> to<00:09:02.519> to<00:09:02.820> basically<00:09:03.180> hit<00:09:03.420> the 00:09:03.710 --> 00:09:03.720 align:start position:0% technology to to basically hit the 00:09:03.720 --> 00:09:05.269 align:start position:0% technology to to basically hit the entire<00:09:03.959> system 00:09:05.269 --> 00:09:05.279 align:start position:0% entire system 00:09:05.279 --> 00:09:07.009 align:start position:0% entire system um not<00:09:05.760> just<00:09:05.880> individual<00:09:06.420> pieces<00:09:06.839> of 00:09:07.009 --> 00:09:07.019 align:start position:0% um not just individual pieces of 00:09:07.019 --> 00:09:09.110 align:start position:0% um not just individual pieces of software<00:09:07.320> but<00:09:07.620> the<00:09:07.920> entire<00:09:08.160> system<00:09:08.459> is<00:09:08.700> fuzzed 00:09:09.110 --> 00:09:09.120 align:start position:0% software but the entire system is fuzzed 00:09:09.120 --> 00:09:12.970 align:start position:0% software but the entire system is fuzzed and<00:09:09.899> that<00:09:10.680> allows<00:09:11.100> us<00:09:11.279> so<00:09:11.880> basically<00:09:12.240> kind<00:09:12.540> of 00:09:12.970 --> 00:09:12.980 align:start position:0% and that allows us so basically kind of 00:09:12.980 --> 00:09:15.350 align:start position:0% and that allows us so basically kind of deterministically<00:09:13.980> replay<00:09:14.339> the<00:09:14.880> complete 00:09:15.350 --> 00:09:15.360 align:start position:0% deterministically replay the complete 00:09:15.360 --> 00:09:17.750 align:start position:0% deterministically replay the complete orchestration<00:09:15.899> of<00:09:16.080> a<00:09:16.560> situation<00:09:16.920> not<00:09:17.519> just 00:09:17.750 --> 00:09:17.760 align:start position:0% orchestration of a situation not just 00:09:17.760 --> 00:09:19.910 align:start position:0% orchestration of a situation not just one<00:09:18.060> particular<00:09:18.360> application<00:09:18.839> but<00:09:19.200> we<00:09:19.800> know 00:09:19.910 --> 00:09:19.920 align:start position:0% one particular application but we know 00:09:19.920 --> 00:09:21.350 align:start position:0% one particular application but we know that<00:09:20.160> in<00:09:20.459> this<00:09:20.580> combination<00:09:21.000> different 00:09:21.350 --> 00:09:21.360 align:start position:0% that in this combination different 00:09:21.360 --> 00:09:23.570 align:start position:0% that in this combination different clients<00:09:21.899> under<00:09:22.440> these<00:09:22.740> Network<00:09:22.920> conditions 00:09:23.570 --> 00:09:23.580 align:start position:0% clients under these Network conditions 00:09:23.580 --> 00:09:25.490 align:start position:0% clients under these Network conditions something<00:09:24.480> goes<00:09:24.779> wrong 00:09:25.490 --> 00:09:25.500 align:start position:0% something goes wrong 00:09:25.500 --> 00:09:28.250 align:start position:0% something goes wrong um<00:09:25.920> and<00:09:26.399> so<00:09:26.580> we<00:09:26.700> use<00:09:26.880> strategies<00:09:27.420> inside<00:09:27.959> the 00:09:28.250 --> 00:09:28.260 align:start position:0% um and so we use strategies inside the 00:09:28.260 --> 00:09:30.230 align:start position:0% um and so we use strategies inside the system<00:09:28.380> to<00:09:28.740> allow<00:09:28.920> us<00:09:29.040> to<00:09:29.220> seek<00:09:29.519> rare<00:09:29.880> events 00:09:30.230 --> 00:09:30.240 align:start position:0% system to allow us to seek rare events 00:09:30.240 --> 00:09:32.389 align:start position:0% system to allow us to seek rare events and<00:09:30.420> so<00:09:30.600> when<00:09:31.380> you<00:09:31.500> when<00:09:31.740> I<00:09:31.860> start<00:09:31.980> looking<00:09:32.160> at 00:09:32.389 --> 00:09:32.399 align:start position:0% and so when you when I start looking at 00:09:32.399 --> 00:09:33.530 align:start position:0% and so when you when I start looking at the<00:09:32.519> numbers<00:09:32.640> and<00:09:32.880> kind<00:09:33.060> of<00:09:33.180> what<00:09:33.240> we've<00:09:33.360> been 00:09:33.530 --> 00:09:33.540 align:start position:0% the numbers and kind of what we've been 00:09:33.540 --> 00:09:35.389 align:start position:0% the numbers and kind of what we've been doing<00:09:33.720> over<00:09:33.899> the<00:09:34.080> last<00:09:34.140> year<00:09:34.380> you<00:09:35.100> know<00:09:35.279> we 00:09:35.389 --> 00:09:35.399 align:start position:0% doing over the last year you know we 00:09:35.399 --> 00:09:37.190 align:start position:0% doing over the last year you know we hear<00:09:35.580> a<00:09:35.700> huge<00:09:35.940> amount<00:09:36.180> of<00:09:36.300> code<00:09:36.480> edges<00:09:36.899> like 00:09:37.190 --> 00:09:37.200 align:start position:0% hear a huge amount of code edges like 00:09:37.200 --> 00:09:40.190 align:start position:0% hear a huge amount of code edges like you<00:09:38.040> know<00:09:38.100> a<00:09:38.459> huge<00:09:38.760> amount<00:09:39.000> and<00:09:39.240> so<00:09:39.420> how<00:09:39.959> do<00:09:40.080> we 00:09:40.190 --> 00:09:40.200 align:start position:0% you know a huge amount and so how do we 00:09:40.200 --> 00:09:43.009 align:start position:0% you know a huge amount and so how do we how<00:09:40.440> do<00:09:40.620> we<00:09:40.740> find<00:09:40.980> and<00:09:41.279> allow<00:09:42.000> ourselves<00:09:42.420> to<00:09:42.779> to 00:09:43.009 --> 00:09:43.019 align:start position:0% how do we find and allow ourselves to to 00:09:43.019 --> 00:09:45.769 align:start position:0% how do we find and allow ourselves to to seek<00:09:43.440> out<00:09:43.560> those<00:09:43.980> edge<00:09:44.580> cases<00:09:45.060> that<00:09:45.420> you<00:09:45.720> know 00:09:45.769 --> 00:09:45.779 align:start position:0% seek out those edge cases that you know 00:09:45.779 --> 00:09:48.170 align:start position:0% seek out those edge cases that you know if<00:09:45.899> they<00:09:46.019> do<00:09:46.200> happen<00:09:46.380> again<00:09:46.800> it<00:09:47.519> can<00:09:47.700> be<00:09:47.820> can<00:09:48.000> be 00:09:48.170 --> 00:09:48.180 align:start position:0% if they do happen again it can be can be 00:09:48.180 --> 00:09:49.790 align:start position:0% if they do happen again it can be can be pretty<00:09:48.300> catastrophic 00:09:49.790 --> 00:09:49.800 align:start position:0% pretty catastrophic 00:09:49.800 --> 00:09:52.670 align:start position:0% pretty catastrophic um<00:09:49.860> but<00:09:50.519> you<00:09:51.300> know<00:09:51.480> get<00:09:51.839> to<00:09:51.959> them<00:09:52.140> and<00:09:52.440> and 00:09:52.670 --> 00:09:52.680 align:start position:0% um but you know get to them and and 00:09:52.680 --> 00:09:55.310 align:start position:0% um but you know get to them and and uncover<00:09:53.459> them<00:09:53.580> to<00:09:53.760> help<00:09:54.120> the<00:09:54.360> client<00:09:54.540> teams<00:09:55.200> um 00:09:55.310 --> 00:09:55.320 align:start position:0% uncover them to help the client teams um 00:09:55.320 --> 00:09:58.550 align:start position:0% uncover them to help the client teams um debug<00:09:55.740> and<00:09:55.980> fix<00:09:56.339> so<00:09:57.180> we<00:09:57.720> have<00:09:57.839> we<00:09:58.320> have<00:09:58.380> the 00:09:58.550 --> 00:09:58.560 align:start position:0% debug and fix so we have we have the 00:09:58.560 --> 00:10:00.530 align:start position:0% debug and fix so we have we have the ability<00:09:58.800> to<00:09:59.100> have<00:09:59.339> all<00:09:59.580> this<00:09:59.760> wrapped<00:10:00.180> up<00:10:00.300> in 00:10:00.530 --> 00:10:00.540 align:start position:0% ability to have all this wrapped up in 00:10:00.540 --> 00:10:03.650 align:start position:0% ability to have all this wrapped up in in<00:10:00.839> a<00:10:01.080> a<00:10:01.680> tool<00:10:02.160> set<00:10:02.760> um<00:10:02.820> that<00:10:03.000> is<00:10:03.060> available<00:10:03.180> to 00:10:03.650 --> 00:10:03.660 align:start position:0% in a a tool set um that is available to 00:10:03.660 --> 00:10:05.990 align:start position:0% in a a tool set um that is available to ourselves<00:10:04.140> and<00:10:04.380> we<00:10:04.620> share<00:10:04.980> it<00:10:05.160> to<00:10:05.399> the<00:10:05.760> rest<00:10:05.880> of 00:10:05.990 --> 00:10:06.000 align:start position:0% ourselves and we share it to the rest of 00:10:06.000 --> 00:10:08.090 align:start position:0% ourselves and we share it to the rest of the<00:10:06.060> client<00:10:06.300> teams<00:10:06.660> and<00:10:06.899> the<00:10:07.080> F<00:10:07.320> and<00:10:07.920> that's 00:10:08.090 --> 00:10:08.100 align:start position:0% the client teams and the F and that's 00:10:08.100 --> 00:10:10.610 align:start position:0% the client teams and the F and that's been<00:10:08.279> really<00:10:08.640> really<00:10:09.000> useful<00:10:09.480> I<00:10:09.779> think<00:10:09.959> if<00:10:10.500> we 00:10:10.610 --> 00:10:10.620 align:start position:0% been really really useful I think if we 00:10:10.620 --> 00:10:12.590 align:start position:0% been really really useful I think if we look<00:10:10.740> at<00:10:10.860> it<00:10:10.980> we<00:10:11.279> have<00:10:11.399> we<00:10:11.880> have<00:10:12.060> the<00:10:12.420> the 00:10:12.590 --> 00:10:12.600 align:start position:0% look at it we have we have the the 00:10:12.600 --> 00:10:14.329 align:start position:0% look at it we have we have the the individual<00:10:13.080> testing<00:10:13.440> going<00:10:13.800> on<00:10:13.980> which<00:10:14.220> is 00:10:14.329 --> 00:10:14.339 align:start position:0% individual testing going on which is 00:10:14.339 --> 00:10:16.730 align:start position:0% individual testing going on which is fantastic<00:10:14.760> we<00:10:15.480> continue<00:10:15.899> to<00:10:16.200> promote<00:10:16.560> that 00:10:16.730 --> 00:10:16.740 align:start position:0% fantastic we continue to promote that 00:10:16.740 --> 00:10:18.650 align:start position:0% fantastic we continue to promote that and<00:10:16.920> say<00:10:17.040> keep<00:10:17.279> keep<00:10:17.459> going<00:10:17.580> with<00:10:17.880> that<00:10:18.000> we 00:10:18.650 --> 00:10:18.660 align:start position:0% and say keep keep going with that we 00:10:18.660 --> 00:10:20.210 align:start position:0% and say keep keep going with that we have<00:10:18.720> the<00:10:18.899> test<00:10:19.019> Nets<00:10:19.440> and<00:10:19.500> Shadow<00:10:19.680> Forks 00:10:20.210 --> 00:10:20.220 align:start position:0% have the test Nets and Shadow Forks 00:10:20.220 --> 00:10:21.290 align:start position:0% have the test Nets and Shadow Forks again 00:10:21.290 --> 00:10:21.300 align:start position:0% again 00:10:21.300 --> 00:10:22.790 align:start position:0% again I<00:10:21.779> think<00:10:21.899> you<00:10:22.019> know<00:10:22.140> we<00:10:22.260> can<00:10:22.380> all<00:10:22.500> say<00:10:22.680> that 00:10:22.790 --> 00:10:22.800 align:start position:0% I think you know we can all say that 00:10:22.800 --> 00:10:24.290 align:start position:0% I think you know we can all say that they've<00:10:23.160> been<00:10:23.279> tremendously<00:10:23.700> successful<00:10:24.120> and 00:10:24.290 --> 00:10:24.300 align:start position:0% they've been tremendously successful and 00:10:24.300 --> 00:10:25.430 align:start position:0% they've been tremendously successful and useful 00:10:25.430 --> 00:10:25.440 align:start position:0% useful 00:10:25.440 --> 00:10:26.870 align:start position:0% useful and<00:10:25.860> then<00:10:25.920> we<00:10:26.100> have 00:10:26.870 --> 00:10:26.880 align:start position:0% and then we have 00:10:26.880 --> 00:10:28.790 align:start position:0% and then we have our<00:10:27.360> parallel<00:10:27.660> universes<00:10:28.200> we<00:10:28.560> have<00:10:28.680> the 00:10:28.790 --> 00:10:28.800 align:start position:0% our parallel universes we have the 00:10:28.800 --> 00:10:30.829 align:start position:0% our parallel universes we have the ability<00:10:29.040> to<00:10:29.399> run<00:10:29.580> not<00:10:30.000> just<00:10:30.120> one<00:10:30.300> simulation 00:10:30.829 --> 00:10:30.839 align:start position:0% ability to run not just one simulation 00:10:30.839 --> 00:10:32.509 align:start position:0% ability to run not just one simulation but<00:10:31.320> we're<00:10:31.440> running<00:10:31.560> simulations<00:10:32.040> literally 00:10:32.509 --> 00:10:32.519 align:start position:0% but we're running simulations literally 00:10:32.519 --> 00:10:35.389 align:start position:0% but we're running simulations literally every<00:10:32.700> day<00:10:33.000> that<00:10:33.720> are<00:10:33.899> generating<00:10:34.620> and<00:10:34.860> using 00:10:35.389 --> 00:10:35.399 align:start position:0% every day that are generating and using 00:10:35.399 --> 00:10:37.430 align:start position:0% every day that are generating and using you<00:10:35.580> know<00:10:35.700> exploring<00:10:36.420> the<00:10:36.720> various<00:10:37.200> search 00:10:37.430 --> 00:10:37.440 align:start position:0% you know exploring the various search 00:10:37.440 --> 00:10:40.730 align:start position:0% you know exploring the various search spaces<00:10:38.279> that<00:10:38.880> exist<00:10:39.420> across<00:10:39.899> any<00:10:40.380> number<00:10:40.560> of 00:10:40.730 --> 00:10:40.740 align:start position:0% spaces that exist across any number of 00:10:40.740 --> 00:10:43.250 align:start position:0% spaces that exist across any number of different<00:10:40.980> branches<00:10:41.880> inside<00:10:42.360> the<00:10:42.839> uh<00:10:43.019> the 00:10:43.250 --> 00:10:43.260 align:start position:0% different branches inside the uh the 00:10:43.260 --> 00:10:46.610 align:start position:0% different branches inside the uh the repositories<00:10:43.860> so 00:10:46.610 --> 00:10:46.620 align:start position:0% 00:10:46.620 --> 00:10:48.769 align:start position:0% what<00:10:47.040> does<00:10:47.160> this<00:10:47.279> mean<00:10:47.459> for<00:10:47.579> us<00:10:47.760> well<00:10:48.240> there's 00:10:48.769 --> 00:10:48.779 align:start position:0% what does this mean for us well there's 00:10:48.779 --> 00:10:50.990 align:start position:0% what does this mean for us well there's a<00:10:48.959> little<00:10:49.260> Little<00:10:49.440> Help<00:10:50.279> from<00:10:50.459> Doctor<00:10:50.640> Strange 00:10:50.990 --> 00:10:51.000 align:start position:0% a little Little Help from Doctor Strange 00:10:51.000 --> 00:10:55.310 align:start position:0% a little Little Help from Doctor Strange here 00:10:55.310 --> 00:10:55.320 align:start position:0% 00:10:55.320 --> 00:10:56.870 align:start position:0% hopefully<00:10:55.920> you've<00:10:56.040> seen<00:10:56.220> it<00:10:56.459> because<00:10:56.700> it's 00:10:56.870 --> 00:10:56.880 align:start position:0% hopefully you've seen it because it's 00:10:56.880 --> 00:11:05.930 align:start position:0% hopefully you've seen it because it's not<00:10:57.000> playing<00:10:57.180> here<00:10:57.959> we<00:10:58.140> go 00:11:05.930 --> 00:11:05.940 align:start position:0% 00:11:05.940 --> 00:11:07.370 align:start position:0% this<00:11:06.420> is<00:11:06.480> what<00:11:06.660> I<00:11:06.720> look<00:11:06.839> like<00:11:06.959> when<00:11:07.140> I'm<00:11:07.260> doing 00:11:07.370 --> 00:11:07.380 align:start position:0% this is what I look like when I'm doing 00:11:07.380 --> 00:11:09.640 align:start position:0% this is what I look like when I'm doing the<00:11:07.560> work 00:11:09.640 --> 00:11:09.650 align:start position:0% the work 00:11:09.650 --> 00:11:16.550 align:start position:0% the work [Music] 00:11:16.550 --> 00:11:16.560 align:start position:0% 00:11:16.560 --> 00:11:18.650 align:start position:0% for<00:11:16.920> it<00:11:17.279> in<00:11:17.399> time 00:11:18.650 --> 00:11:18.660 align:start position:0% for it in time 00:11:18.660 --> 00:11:21.829 align:start position:0% for it in time to<00:11:18.899> view<00:11:19.140> alternate<00:11:19.860> Futures<00:11:20.300> to<00:11:21.300> see<00:11:21.540> all<00:11:21.660> the 00:11:21.829 --> 00:11:21.839 align:start position:0% to view alternate Futures to see all the 00:11:21.839 --> 00:11:25.130 align:start position:0% to view alternate Futures to see all the possible<00:11:22.140> outcomes<00:11:22.560> of<00:11:22.740> the<00:11:22.920> coming<00:11:23.040> conflict 00:11:25.130 --> 00:11:25.140 align:start position:0% possible outcomes of the coming conflict 00:11:25.140 --> 00:11:30.590 align:start position:0% possible outcomes of the coming conflict how<00:11:25.620> many<00:11:25.740> did<00:11:25.980> you<00:11:26.160> see<00:11:26.339> 14<00:11:27.180> million<00:11:27.660> 605. 00:11:30.590 --> 00:11:30.600 align:start position:0% how many did you see 14 million 605. 00:11:30.600 --> 00:11:33.480 align:start position:0% how many did you see 14 million 605. how<00:11:31.019> many<00:11:31.140> we<00:11:31.380> win 00:11:33.480 --> 00:11:33.490 align:start position:0% how many we win 00:11:33.490 --> 00:11:36.769 align:start position:0% how many we win [Music] 00:11:36.769 --> 00:11:36.779 align:start position:0% 00:11:36.779 --> 00:11:38.509 align:start position:0% one 00:11:38.509 --> 00:11:38.519 align:start position:0% one 00:11:38.519 --> 00:11:41.389 align:start position:0% one so<00:11:38.940> so<00:11:39.000> for<00:11:39.360> us<00:11:39.480> winning<00:11:39.779> is<00:11:40.440> finding<00:11:41.100> these 00:11:41.389 --> 00:11:41.399 align:start position:0% so so for us winning is finding these 00:11:41.399 --> 00:11:43.610 align:start position:0% so so for us winning is finding these edge<00:11:41.579> cases<00:11:41.940> right<00:11:42.120> now<00:11:42.300> your<00:11:43.200> winning<00:11:43.320> isn't 00:11:43.610 --> 00:11:43.620 align:start position:0% edge cases right now your winning isn't 00:11:43.620 --> 00:11:46.490 align:start position:0% edge cases right now your winning isn't like<00:11:43.800> oh<00:11:43.980> all<00:11:44.279> tests<00:11:44.820> passed<00:11:45.120> yay<00:11:45.899> um<00:11:45.899> we<00:11:46.320> want 00:11:46.490 --> 00:11:46.500 align:start position:0% like oh all tests passed yay um we want 00:11:46.500 --> 00:11:48.470 align:start position:0% like oh all tests passed yay um we want to<00:11:46.740> find<00:11:46.920> those<00:11:47.279> those<00:11:47.760> really<00:11:48.000> intricate 00:11:48.470 --> 00:11:48.480 align:start position:0% to find those those really intricate 00:11:48.480 --> 00:11:50.030 align:start position:0% to find those those really intricate kind<00:11:48.660> of<00:11:48.779> piece<00:11:49.140> you<00:11:49.260> know<00:11:49.380> combinations<00:11:49.740> and 00:11:50.030 --> 00:11:50.040 align:start position:0% kind of piece you know combinations and 00:11:50.040 --> 00:11:51.829 align:start position:0% kind of piece you know combinations and iterations<00:11:50.459> where<00:11:50.820> we've<00:11:51.300> covered<00:11:51.600> 14 00:11:51.829 --> 00:11:51.839 align:start position:0% iterations where we've covered 14 00:11:51.839 --> 00:11:53.750 align:start position:0% iterations where we've covered 14 million<00:11:52.320> different<00:11:52.500> scenarios<00:11:52.980> and<00:11:53.519> we've 00:11:53.750 --> 00:11:53.760 align:start position:0% million different scenarios and we've 00:11:53.760 --> 00:11:55.490 align:start position:0% million different scenarios and we've got<00:11:53.940> you<00:11:54.360> know<00:11:54.540> maybe<00:11:54.600> not<00:11:54.779> more<00:11:55.019> than<00:11:55.140> one<00:11:55.320> but 00:11:55.490 --> 00:11:55.500 align:start position:0% got you know maybe not more than one but 00:11:55.500 --> 00:11:57.230 align:start position:0% got you know maybe not more than one but we<00:11:55.860> at<00:11:56.279> least<00:11:56.399> have<00:11:56.519> one<00:11:56.760> you<00:11:56.940> know<00:11:57.000> we<00:11:57.120> can 00:11:57.230 --> 00:11:57.240 align:start position:0% we at least have one you know we can 00:11:57.240 --> 00:11:59.210 align:start position:0% we at least have one you know we can actually<00:11:57.420> hold<00:11:57.839> our<00:11:58.019> hat<00:11:58.140> on<00:11:58.380> so<00:11:58.620> that's 00:11:59.210 --> 00:11:59.220 align:start position:0% actually hold our hat on so that's 00:11:59.220 --> 00:12:00.470 align:start position:0% actually hold our hat on so that's that's<00:11:59.459> an<00:11:59.640> example<00:11:59.880> of<00:12:00.000> what<00:12:00.180> we're<00:12:00.300> doing 00:12:00.470 --> 00:12:00.480 align:start position:0% that's an example of what we're doing 00:12:00.480 --> 00:12:02.810 align:start position:0% that's an example of what we're doing and<00:12:00.720> we<00:12:01.440> think<00:12:01.920> that<00:12:01.980> kind<00:12:02.160> of<00:12:02.220> represents<00:12:02.579> you 00:12:02.810 --> 00:12:02.820 align:start position:0% and we think that kind of represents you 00:12:02.820 --> 00:12:05.269 align:start position:0% and we think that kind of represents you know<00:12:03.000> pretty<00:12:03.300> pretty<00:12:03.480> good<00:12:03.839> sort<00:12:04.079> of<00:12:04.140> analogy 00:12:05.269 --> 00:12:05.279 align:start position:0% know pretty pretty good sort of analogy 00:12:05.279 --> 00:12:07.009 align:start position:0% know pretty pretty good sort of analogy um<00:12:05.339> if<00:12:05.760> we<00:12:05.940> move<00:12:06.120> forward<00:12:06.300> we've<00:12:06.720> seen<00:12:06.839> it 00:12:07.009 --> 00:12:07.019 align:start position:0% um if we move forward we've seen it 00:12:07.019 --> 00:12:07.730 align:start position:0% um if we move forward we've seen it again 00:12:07.730 --> 00:12:07.740 align:start position:0% again 00:12:07.740 --> 00:12:09.530 align:start position:0% again here<00:12:08.220> we<00:12:08.399> are<00:12:08.519> this<00:12:09.000> is<00:12:09.060> kind<00:12:09.240> of<00:12:09.360> what<00:12:09.420> it 00:12:09.530 --> 00:12:09.540 align:start position:0% here we are this is kind of what it 00:12:09.540 --> 00:12:10.970 align:start position:0% here we are this is kind of what it looks<00:12:09.720> like<00:12:09.779> in<00:12:09.959> our<00:12:10.079> world 00:12:10.970 --> 00:12:10.980 align:start position:0% looks like in our world 00:12:10.980 --> 00:12:12.829 align:start position:0% looks like in our world um<00:12:11.040> you<00:12:11.339> know<00:12:11.459> we're<00:12:11.579> looking<00:12:11.700> for<00:12:11.880> bugs 00:12:12.829 --> 00:12:12.839 align:start position:0% um you know we're looking for bugs 00:12:12.839 --> 00:12:14.810 align:start position:0% um you know we're looking for bugs um<00:12:12.959> this<00:12:13.440> this<00:12:13.680> is<00:12:13.860> an<00:12:13.980> example<00:12:14.279> of<00:12:14.459> an<00:12:14.579> output 00:12:14.810 --> 00:12:14.820 align:start position:0% um this this is an example of an output 00:12:14.820 --> 00:12:17.569 align:start position:0% um this this is an example of an output of<00:12:15.000> just<00:12:15.180> one<00:12:15.360> run<00:12:15.600> so<00:12:15.899> we<00:12:16.140> we<00:12:16.320> ran<00:12:16.620> this<00:12:17.279> um<00:12:17.339> 13 00:12:17.569 --> 00:12:17.579 align:start position:0% of just one run so we we ran this um 13 00:12:17.579 --> 00:12:19.850 align:start position:0% of just one run so we we ran this um 13 hours<00:12:17.880> worth<00:12:18.180> of<00:12:18.420> water<00:12:18.779> wall<00:12:19.440> clock<00:12:19.620> time 00:12:19.850 --> 00:12:19.860 align:start position:0% hours worth of water wall clock time 00:12:19.860 --> 00:12:21.470 align:start position:0% hours worth of water wall clock time which<00:12:20.160> is<00:12:20.279> if<00:12:20.579> you<00:12:20.760> look<00:12:20.880> at<00:12:21.000> the<00:12:21.120> wall<00:12:21.240> and 00:12:21.470 --> 00:12:21.480 align:start position:0% which is if you look at the wall and 00:12:21.480 --> 00:12:23.449 align:start position:0% which is if you look at the wall and there's<00:12:21.600> a<00:12:21.720> clock<00:12:21.839> on<00:12:22.019> it<00:12:22.560> um<00:12:22.680> it<00:12:22.920> will<00:12:23.040> last<00:12:23.220> 13 00:12:23.449 --> 00:12:23.459 align:start position:0% there's a clock on it um it will last 13 00:12:23.459 --> 00:12:24.350 align:start position:0% there's a clock on it um it will last 13 hours 00:12:24.350 --> 00:12:24.360 align:start position:0% hours 00:12:24.360 --> 00:12:26.870 align:start position:0% hours um<00:12:24.480> but<00:12:24.779> uh<00:12:25.140> it<00:12:25.620> actually<00:12:25.740> allows<00:12:26.220> us<00:12:26.339> to<00:12:26.640> to 00:12:26.870 --> 00:12:26.880 align:start position:0% um but uh it actually allows us to to 00:12:26.880 --> 00:12:30.470 align:start position:0% um but uh it actually allows us to to exhaust<00:12:27.800> 536<00:12:28.800> hours<00:12:29.040> worth<00:12:29.339> of<00:12:29.579> testing 00:12:30.470 --> 00:12:30.480 align:start position:0% exhaust 536 hours worth of testing 00:12:30.480 --> 00:12:31.850 align:start position:0% exhaust 536 hours worth of testing um<00:12:30.600> and<00:12:30.899> you<00:12:30.959> can<00:12:31.079> see<00:12:31.200> here<00:12:31.320> we<00:12:31.500> are<00:12:31.680> we're 00:12:31.850 --> 00:12:31.860 align:start position:0% um and you can see here we are we're 00:12:31.860 --> 00:12:33.470 align:start position:0% um and you can see here we are we're talking<00:12:32.040> about<00:12:32.279> an<00:12:32.579> enormous<00:12:32.880> amount<00:12:33.300> of 00:12:33.470 --> 00:12:33.480 align:start position:0% talking about an enormous amount of 00:12:33.480 --> 00:12:35.810 align:start position:0% talking about an enormous amount of edges<00:12:33.839> being<00:12:34.079> seen<00:12:34.320> here<00:12:35.040> um<00:12:35.160> the<00:12:35.459> branches 00:12:35.810 --> 00:12:35.820 align:start position:0% edges being seen here um the branches 00:12:35.820 --> 00:12:37.970 align:start position:0% edges being seen here um the branches are<00:12:36.240> kind<00:12:36.540> of<00:12:36.660> how<00:12:36.779> we<00:12:37.019> get<00:12:37.200> decision<00:12:37.500> points 00:12:37.970 --> 00:12:37.980 align:start position:0% are kind of how we get decision points 00:12:37.980 --> 00:12:40.310 align:start position:0% are kind of how we get decision points we<00:12:38.519> we<00:12:38.700> get<00:12:38.880> like<00:12:39.060> an<00:12:39.240> if<00:12:39.420> then<00:12:39.600> else<00:12:39.779> on<00:12:40.079> a<00:12:40.200> kind 00:12:40.310 --> 00:12:40.320 align:start position:0% we we get like an if then else on a kind 00:12:40.320 --> 00:12:42.410 align:start position:0% we we get like an if then else on a kind of<00:12:40.440> statement<00:12:40.740> inside<00:12:41.040> the<00:12:41.339> code<00:12:41.519> very<00:12:42.240> simple 00:12:42.410 --> 00:12:42.420 align:start position:0% of statement inside the code very simple 00:12:42.420 --> 00:12:44.810 align:start position:0% of statement inside the code very simple example<00:12:42.660> but<00:12:43.380> just<00:12:43.680> just<00:12:43.860> take<00:12:44.100> it 00:12:44.810 --> 00:12:44.820 align:start position:0% example but just just take it 00:12:44.820 --> 00:12:46.850 align:start position:0% example but just just take it um<00:12:44.940> we<00:12:45.540> can<00:12:45.660> basically<00:12:46.019> Branch<00:12:46.320> off<00:12:46.500> at<00:12:46.740> that 00:12:46.850 --> 00:12:46.860 align:start position:0% um we can basically Branch off at that 00:12:46.860 --> 00:12:49.670 align:start position:0% um we can basically Branch off at that point<00:12:47.040> and<00:12:47.399> exhaust<00:12:48.000> both<00:12:48.320> Avenues<00:12:49.320> and 00:12:49.670 --> 00:12:49.680 align:start position:0% point and exhaust both Avenues and 00:12:49.680 --> 00:12:51.050 align:start position:0% point and exhaust both Avenues and actually<00:12:49.860> see<00:12:50.160> what<00:12:50.399> happens<00:12:50.579> in<00:12:50.940> both 00:12:51.050 --> 00:12:51.060 align:start position:0% actually see what happens in both 00:12:51.060 --> 00:12:53.389 align:start position:0% actually see what happens in both situations<00:12:51.620> underneath<00:12:52.620> those<00:12:52.860> and<00:12:53.160> you<00:12:53.339> know 00:12:53.389 --> 00:12:53.399 align:start position:0% situations underneath those and you know 00:12:53.399 --> 00:12:55.250 align:start position:0% situations underneath those and you know under<00:12:53.579> those<00:12:53.880> test<00:12:54.060> conditions 00:12:55.250 --> 00:12:55.260 align:start position:0% under those test conditions 00:12:55.260 --> 00:12:56.930 align:start position:0% under those test conditions um<00:12:55.380> that's<00:12:55.620> an<00:12:55.800> example<00:12:55.980> of<00:12:56.100> a<00:12:56.279> branch<00:12:56.459> and 00:12:56.930 --> 00:12:56.940 align:start position:0% um that's an example of a branch and 00:12:56.940 --> 00:12:59.150 align:start position:0% um that's an example of a branch and obviously<00:12:57.180> the<00:12:57.300> code<00:12:57.420> The<00:12:57.779> Edge<00:12:57.959> is<00:12:58.440> seen<00:12:58.800> is 00:12:59.150 --> 00:12:59.160 align:start position:0% obviously the code The Edge is seen is 00:12:59.160 --> 00:13:00.710 align:start position:0% obviously the code The Edge is seen is we've<00:12:59.459> got<00:12:59.639> the<00:12:59.760> instrumentation<00:13:00.240> happening 00:13:00.710 --> 00:13:00.720 align:start position:0% we've got the instrumentation happening 00:13:00.720 --> 00:13:02.690 align:start position:0% we've got the instrumentation happening so<00:13:00.959> we<00:13:01.079> can<00:13:01.260> see<00:13:01.440> what<00:13:01.800> kind<00:13:01.920> of<00:13:02.040> functions<00:13:02.459> and 00:13:02.690 --> 00:13:02.700 align:start position:0% so we can see what kind of functions and 00:13:02.700 --> 00:13:04.370 align:start position:0% so we can see what kind of functions and and<00:13:02.940> pieces<00:13:03.360> of<00:13:03.540> code<00:13:03.660> are<00:13:03.959> actually<00:13:04.139> being 00:13:04.370 --> 00:13:04.380 align:start position:0% and pieces of code are actually being 00:13:04.380 --> 00:13:06.350 align:start position:0% and pieces of code are actually being executed 00:13:06.350 --> 00:13:06.360 align:start position:0% executed 00:13:06.360 --> 00:13:08.269 align:start position:0% executed pretty<00:13:06.899> pretty<00:13:07.139> insane<00:13:07.560> you<00:13:07.680> know<00:13:07.740> that's<00:13:08.100> one 00:13:08.269 --> 00:13:08.279 align:start position:0% pretty pretty insane you know that's one 00:13:08.279 --> 00:13:10.790 align:start position:0% pretty pretty insane you know that's one run<00:13:08.399> I've<00:13:08.579> got<00:13:08.760> 180<00:13:09.660> 000<00:13:09.779> edges<00:13:10.139> that<00:13:10.380> we're 00:13:10.790 --> 00:13:10.800 align:start position:0% run I've got 180 000 edges that we're 00:13:10.800 --> 00:13:12.230 align:start position:0% run I've got 180 000 edges that we're seeing<00:13:10.920> across<00:13:11.339> across<00:13:11.700> the<00:13:11.760> entire<00:13:12.000> network 00:13:12.230 --> 00:13:12.240 align:start position:0% seeing across across the entire network 00:13:12.240 --> 00:13:14.269 align:start position:0% seeing across across the entire network it's<00:13:12.899> a<00:13:13.139> busy<00:13:13.380> Network 00:13:14.269 --> 00:13:14.279 align:start position:0% it's a busy Network 00:13:14.279 --> 00:13:15.590 align:start position:0% it's a busy Network um<00:13:14.339> and<00:13:14.760> obviously<00:13:15.060> with<00:13:15.180> all<00:13:15.360> the<00:13:15.480> different 00:13:15.590 --> 00:13:15.600 align:start position:0% um and obviously with all the different 00:13:15.600 --> 00:13:17.810 align:start position:0% um and obviously with all the different clients<00:13:16.019> happening<00:13:16.440> that's<00:13:17.160> uh<00:13:17.399> there's<00:13:17.700> a 00:13:17.810 --> 00:13:17.820 align:start position:0% clients happening that's uh there's a 00:13:17.820 --> 00:13:20.629 align:start position:0% clients happening that's uh there's a lot<00:13:18.180> going<00:13:18.300> on 00:13:20.629 --> 00:13:20.639 align:start position:0% 00:13:20.639 --> 00:13:22.190 align:start position:0% so<00:13:21.000> we<00:13:21.120> see<00:13:21.240> ourselves<00:13:21.480> as<00:13:21.660> a<00:13:21.779> complimentary 00:13:22.190 --> 00:13:22.200 align:start position:0% so we see ourselves as a complimentary 00:13:22.200 --> 00:13:24.110 align:start position:0% so we see ourselves as a complimentary piece<00:13:22.440> we<00:13:22.680> you<00:13:22.800> know<00:13:22.920> we<00:13:23.040> we've<00:13:23.519> we've<00:13:24.000> been 00:13:24.110 --> 00:13:24.120 align:start position:0% piece we you know we we've we've been 00:13:24.120 --> 00:13:27.110 align:start position:0% piece we you know we we've we've been looking<00:13:24.420> at<00:13:24.660> this<00:13:25.320> um<00:13:25.440> as<00:13:25.860> a<00:13:26.040> you<00:13:26.519> know<00:13:26.639> a<00:13:27.000> great 00:13:27.110 --> 00:13:27.120 align:start position:0% looking at this um as a you know a great 00:13:27.120 --> 00:13:28.610 align:start position:0% looking at this um as a you know a great example<00:13:27.480> of<00:13:27.660> a<00:13:27.839> project<00:13:27.959> where<00:13:28.320> we<00:13:28.500> can 00:13:28.610 --> 00:13:28.620 align:start position:0% example of a project where we can 00:13:28.620 --> 00:13:30.889 align:start position:0% example of a project where we can basically<00:13:29.339> work<00:13:29.880> alongside<00:13:30.360> all<00:13:30.660> the<00:13:30.839> other 00:13:30.889 --> 00:13:30.899 align:start position:0% basically work alongside all the other 00:13:30.899 --> 00:13:33.410 align:start position:0% basically work alongside all the other pieces<00:13:31.380> that<00:13:31.620> the<00:13:31.860> EF<00:13:32.160> are<00:13:32.399> kind<00:13:32.880> of<00:13:32.940> using<00:13:33.240> and 00:13:33.410 --> 00:13:33.420 align:start position:0% pieces that the EF are kind of using and 00:13:33.420 --> 00:13:35.329 align:start position:0% pieces that the EF are kind of using and different<00:13:33.660> client<00:13:33.899> teams<00:13:34.200> are<00:13:34.260> using<00:13:35.040> um<00:13:35.160> so 00:13:35.329 --> 00:13:35.339 align:start position:0% different client teams are using um so 00:13:35.339 --> 00:13:37.310 align:start position:0% different client teams are using um so we're<00:13:35.639> just<00:13:35.820> another<00:13:36.000> layer<00:13:36.480> in<00:13:36.779> in<00:13:36.959> the 00:13:37.310 --> 00:13:37.320 align:start position:0% we're just another layer in in the 00:13:37.320 --> 00:13:39.530 align:start position:0% we're just another layer in in the growing<00:13:37.560> list<00:13:37.740> of<00:13:37.920> of<00:13:38.100> of<00:13:38.519> strategies<00:13:39.240> being 00:13:39.530 --> 00:13:39.540 align:start position:0% growing list of of of strategies being 00:13:39.540 --> 00:13:41.150 align:start position:0% growing list of of of strategies being being<00:13:39.899> used<00:13:40.139> and<00:13:40.320> I<00:13:40.500> think<00:13:40.560> that's<00:13:40.800> sort<00:13:41.040> of 00:13:41.150 --> 00:13:41.160 align:start position:0% being used and I think that's sort of 00:13:41.160 --> 00:13:43.190 align:start position:0% being used and I think that's sort of Testament<00:13:41.579> to<00:13:41.820> the<00:13:42.180> approach<00:13:42.420> that<00:13:42.660> EF<00:13:43.019> have 00:13:43.190 --> 00:13:43.200 align:start position:0% Testament to the approach that EF have 00:13:43.200 --> 00:13:44.030 align:start position:0% Testament to the approach that EF have used 00:13:44.030 --> 00:13:44.040 align:start position:0% used 00:13:44.040 --> 00:13:46.490 align:start position:0% used um<00:13:44.160> to<00:13:44.459> to<00:13:44.760> Really<00:13:45.360> hold<00:13:45.779> on<00:13:46.019> to<00:13:46.200> this 00:13:46.490 --> 00:13:46.500 align:start position:0% um to to Really hold on to this 00:13:46.500 --> 00:13:48.590 align:start position:0% um to to Really hold on to this resilience<00:13:46.980> you<00:13:47.220> know<00:13:47.339> making<00:13:47.760> sure<00:13:48.000> that<00:13:48.300> we 00:13:48.590 --> 00:13:48.600 align:start position:0% resilience you know making sure that we 00:13:48.600 --> 00:13:50.509 align:start position:0% resilience you know making sure that we take<00:13:48.959> advantage<00:13:49.380> of<00:13:49.560> every<00:13:49.740> way<00:13:49.980> we<00:13:50.220> can<00:13:50.339> we 00:13:50.509 --> 00:13:50.519 align:start position:0% take advantage of every way we can we 00:13:50.519 --> 00:13:52.250 align:start position:0% take advantage of every way we can we can<00:13:50.700> make<00:13:51.060> sure<00:13:51.240> that<00:13:51.600> you<00:13:51.899> know<00:13:51.959> nothing 00:13:52.250 --> 00:13:52.260 align:start position:0% can make sure that you know nothing 00:13:52.260 --> 00:13:54.889 align:start position:0% can make sure that you know nothing untoward<00:13:53.100> happens<00:13:53.399> in<00:13:53.940> the<00:13:54.000> future 00:13:54.889 --> 00:13:54.899 align:start position:0% untoward happens in the future 00:13:54.899 --> 00:13:56.930 align:start position:0% untoward happens in the future um<00:13:54.959> you<00:13:55.380> know<00:13:55.500> more<00:13:55.800> more<00:13:55.800> and<00:13:56.220> more<00:13:56.459> upgrades 00:13:56.930 --> 00:13:56.940 align:start position:0% um you know more more and more upgrades 00:13:56.940 --> 00:13:58.610 align:start position:0% um you know more more and more upgrades coming<00:13:57.120> I'm<00:13:57.360> sure<00:13:57.540> so<00:13:57.899> you<00:13:58.200> know<00:13:58.320> we've<00:13:58.500> only 00:13:58.610 --> 00:13:58.620 align:start position:0% coming I'm sure so you know we've only 00:13:58.620 --> 00:14:01.370 align:start position:0% coming I'm sure so you know we've only got<00:13:58.740> 4844<00:13:59.519> around<00:13:59.880> the<00:14:00.120> corner<00:14:00.899> I'll<00:14:01.200> say 00:14:01.370 --> 00:14:01.380 align:start position:0% got 4844 around the corner I'll say 00:14:01.380 --> 00:14:03.470 align:start position:0% got 4844 around the corner I'll say around<00:14:01.500> the<00:14:01.680> corner<00:14:01.920> we'll<00:14:02.339> see<00:14:02.880> um<00:14:02.940> but<00:14:03.180> uh 00:14:03.470 --> 00:14:03.480 align:start position:0% around the corner we'll see um but uh 00:14:03.480 --> 00:14:05.329 align:start position:0% around the corner we'll see um but uh it's<00:14:03.899> certainly<00:14:04.139> something<00:14:04.380> to<00:14:04.620> look<00:14:04.980> at<00:14:05.100> in 00:14:05.329 --> 00:14:05.339 align:start position:0% it's certainly something to look at in 00:14:05.339 --> 00:14:06.350 align:start position:0% it's certainly something to look at in terms<00:14:05.519> of 00:14:06.350 --> 00:14:06.360 align:start position:0% terms of 00:14:06.360 --> 00:14:08.389 align:start position:0% terms of um you<00:14:06.660> know<00:14:06.779> making<00:14:07.079> sure<00:14:07.320> that<00:14:07.680> uh<00:14:07.980> we're 00:14:08.389 --> 00:14:08.399 align:start position:0% um you know making sure that uh we're 00:14:08.399 --> 00:14:12.350 align:start position:0% um you know making sure that uh we're involved<00:14:09.360> at<00:14:09.720> every<00:14:09.839> step<00:14:10.019> of<00:14:10.139> the<00:14:10.260> way 00:14:12.350 --> 00:14:12.360 align:start position:0% involved at every step of the way 00:14:12.360 --> 00:14:14.449 align:start position:0% involved at every step of the way so<00:14:12.660> this<00:14:12.779> is<00:14:12.899> a<00:14:12.959> very<00:14:13.079> simple<00:14:13.200> sort<00:14:13.920> of<00:14:13.980> uh 00:14:14.449 --> 00:14:14.459 align:start position:0% so this is a very simple sort of uh 00:14:14.459 --> 00:14:15.590 align:start position:0% so this is a very simple sort of uh illustration<00:14:14.880> of<00:14:15.060> what<00:14:15.180> we've<00:14:15.360> been<00:14:15.420> doing 00:14:15.590 --> 00:14:15.600 align:start position:0% illustration of what we've been doing 00:14:15.600 --> 00:14:18.590 align:start position:0% illustration of what we've been doing we've<00:14:15.899> been<00:14:15.959> building<00:14:16.200> all<00:14:16.800> of<00:14:16.980> the<00:14:17.160> clients 00:14:18.590 --> 00:14:18.600 align:start position:0% we've been building all of the clients 00:14:18.600 --> 00:14:20.269 align:start position:0% we've been building all of the clients um<00:14:18.660> giving<00:14:18.959> them<00:14:19.200> in<00:14:19.380> in<00:14:19.620> place<00:14:19.860> and<00:14:20.100> actually 00:14:20.269 --> 00:14:20.279 align:start position:0% um giving them in in place and actually 00:14:20.279 --> 00:14:22.250 align:start position:0% um giving them in in place and actually establishing<00:14:21.000> Genesis<00:14:21.420> so<00:14:21.660> we<00:14:21.779> actually<00:14:22.079> have 00:14:22.250 --> 00:14:22.260 align:start position:0% establishing Genesis so we actually have 00:14:22.260 --> 00:14:24.230 align:start position:0% establishing Genesis so we actually have been<00:14:22.440> using<00:14:22.740> this<00:14:22.860> at<00:14:23.040> Genesis<00:14:23.519> block<00:14:23.760> and 00:14:24.230 --> 00:14:24.240 align:start position:0% been using this at Genesis block and 00:14:24.240 --> 00:14:26.810 align:start position:0% been using this at Genesis block and then<00:14:24.360> moving<00:14:24.660> it<00:14:24.779> forward<00:14:24.959> towards<00:14:25.920> the<00:14:26.459> merge 00:14:26.810 --> 00:14:26.820 align:start position:0% then moving it forward towards the merge 00:14:26.820 --> 00:14:28.730 align:start position:0% then moving it forward towards the merge in<00:14:27.360> our<00:14:27.480> in<00:14:27.660> our<00:14:27.839> world<00:14:27.959> we<00:14:28.260> would<00:14:28.440> have<00:14:28.620> the 00:14:28.730 --> 00:14:28.740 align:start position:0% in our in our world we would have the 00:14:28.740 --> 00:14:31.069 align:start position:0% in our in our world we would have the merge<00:14:29.100> kind<00:14:29.339> of<00:14:29.459> positioned<00:14:30.540> um<00:14:30.600> we<00:14:30.839> obviously 00:14:31.069 --> 00:14:31.079 align:start position:0% merge kind of positioned um we obviously 00:14:31.079 --> 00:14:32.690 align:start position:0% merge kind of positioned um we obviously start<00:14:31.260> fault<00:14:31.560> injection<00:14:31.920> we've<00:14:32.339> established 00:14:32.690 --> 00:14:32.700 align:start position:0% start fault injection we've established 00:14:32.700 --> 00:14:33.889 align:start position:0% start fault injection we've established a<00:14:32.820> chain<00:14:32.940> and<00:14:33.180> then<00:14:33.240> we<00:14:33.360> start<00:14:33.540> fault 00:14:33.889 --> 00:14:33.899 align:start position:0% a chain and then we start fault 00:14:33.899 --> 00:14:34.850 align:start position:0% a chain and then we start fault injection 00:14:34.850 --> 00:14:34.860 align:start position:0% injection 00:14:34.860 --> 00:14:37.009 align:start position:0% injection um<00:14:34.980> to<00:14:35.160> get<00:14:35.279> to<00:14:35.459> a<00:14:35.579> point<00:14:35.700> where<00:14:35.940> we've<00:14:36.720> got<00:14:36.779> a 00:14:37.009 --> 00:14:37.019 align:start position:0% um to get to a point where we've got a 00:14:37.019 --> 00:14:38.509 align:start position:0% um to get to a point where we've got a whole<00:14:37.139> host<00:14:37.380> of<00:14:37.560> different<00:14:37.860> faults<00:14:38.279> you<00:14:38.399> can 00:14:38.509 --> 00:14:38.519 align:start position:0% whole host of different faults you can 00:14:38.519 --> 00:14:41.030 align:start position:0% whole host of different faults you can see<00:14:38.639> them<00:14:38.700> here<00:14:38.940> labeled<00:14:39.540> below<00:14:40.260> so<00:14:40.560> anything 00:14:41.030 --> 00:14:41.040 align:start position:0% see them here labeled below so anything 00:14:41.040 --> 00:14:43.009 align:start position:0% see them here labeled below so anything from<00:14:41.519> partitioning 00:14:43.009 --> 00:14:43.019 align:start position:0% from partitioning 00:14:43.019 --> 00:14:44.509 align:start position:0% from partitioning um<00:14:43.079> that's<00:14:43.440> a<00:14:43.620> great<00:14:43.740> one<00:14:43.860> obviously<00:14:44.220> to 00:14:44.509 --> 00:14:44.519 align:start position:0% um that's a great one obviously to 00:14:44.519 --> 00:14:46.970 align:start position:0% um that's a great one obviously to encourage<00:14:45.120> forking<00:14:45.660> of<00:14:45.779> the<00:14:46.079> chains 00:14:46.970 --> 00:14:46.980 align:start position:0% encourage forking of the chains 00:14:46.980 --> 00:14:48.829 align:start position:0% encourage forking of the chains um<00:14:47.100> we've<00:14:47.459> then<00:14:47.579> also<00:14:47.880> got<00:14:48.060> you<00:14:48.300> know<00:14:48.420> delays 00:14:48.829 --> 00:14:48.839 align:start position:0% um we've then also got you know delays 00:14:48.839 --> 00:14:51.170 align:start position:0% um we've then also got you know delays happening<00:14:49.199> drops<00:14:49.860> of<00:14:49.920> packets 00:14:51.170 --> 00:14:51.180 align:start position:0% happening drops of packets 00:14:51.180 --> 00:14:53.030 align:start position:0% happening drops of packets um the<00:14:51.540> nodes<00:14:51.839> themselves 00:14:53.030 --> 00:14:53.040 align:start position:0% um the nodes themselves 00:14:53.040 --> 00:14:55.250 align:start position:0% um the nodes themselves um<00:14:53.399> we<00:14:53.940> can<00:14:54.060> stop<00:14:54.240> you<00:14:54.480> know<00:14:54.540> we<00:14:54.720> do<00:14:54.779> we<00:14:55.019> do<00:14:55.079> we 00:14:55.250 --> 00:14:55.260 align:start position:0% um we can stop you know we do we do we 00:14:55.260 --> 00:14:57.230 align:start position:0% um we can stop you know we do we do we put<00:14:55.680> this<00:14:55.800> thing<00:14:55.980> through<00:14:56.160> its<00:14:56.339> faces<00:14:56.699> we<00:14:57.060> stop 00:14:57.230 --> 00:14:57.240 align:start position:0% put this thing through its faces we stop 00:14:57.240 --> 00:14:59.150 align:start position:0% put this thing through its faces we stop things<00:14:57.480> we<00:14:57.660> pause<00:14:57.899> things<00:14:58.199> we<00:14:58.620> kill<00:14:58.740> things<00:14:58.980> we 00:14:59.150 --> 00:14:59.160 align:start position:0% things we pause things we kill things we 00:14:59.160 --> 00:15:01.069 align:start position:0% things we pause things we kill things we bring<00:14:59.339> them<00:14:59.459> back<00:14:59.639> up<00:14:59.820> I<00:15:00.480> suppose<00:15:00.660> in<00:15:00.779> some 00:15:01.069 --> 00:15:01.079 align:start position:0% bring them back up I suppose in some 00:15:01.079 --> 00:15:02.389 align:start position:0% bring them back up I suppose in some respects<00:15:01.320> it's<00:15:01.560> quite<00:15:01.740> realistic<00:15:02.040> you<00:15:02.220> know 00:15:02.389 --> 00:15:02.399 align:start position:0% respects it's quite realistic you know 00:15:02.399 --> 00:15:04.610 align:start position:0% respects it's quite realistic you know things<00:15:02.699> do<00:15:02.940> get<00:15:03.120> rebooted<00:15:03.779> and<00:15:03.899> violators 00:15:04.610 --> 00:15:04.620 align:start position:0% things do get rebooted and violators 00:15:04.620 --> 00:15:06.710 align:start position:0% things do get rebooted and violators come<00:15:04.860> back<00:15:04.980> up<00:15:05.160> again<00:15:05.279> we<00:15:05.639> we<00:15:05.820> have<00:15:06.360> all<00:15:06.540> that 00:15:06.710 --> 00:15:06.720 align:start position:0% come back up again we we have all that 00:15:06.720 --> 00:15:08.210 align:start position:0% come back up again we we have all that kind<00:15:06.839> of<00:15:06.959> like<00:15:07.260> happening<00:15:07.740> inside<00:15:07.860> the 00:15:08.210 --> 00:15:08.220 align:start position:0% kind of like happening inside the 00:15:08.220 --> 00:15:10.550 align:start position:0% kind of like happening inside the simulation<00:15:08.579> and<00:15:09.300> then<00:15:09.420> from<00:15:09.720> that<00:15:09.899> we<00:15:10.380> then 00:15:10.550 --> 00:15:10.560 align:start position:0% simulation and then from that we then 00:15:10.560 --> 00:15:12.110 align:start position:0% simulation and then from that we then have<00:15:10.800> you<00:15:11.040> know<00:15:11.160> any<00:15:11.339> number<00:15:11.639> of<00:15:11.760> threads 00:15:12.110 --> 00:15:12.120 align:start position:0% have you know any number of threads 00:15:12.120 --> 00:15:14.269 align:start position:0% have you know any number of threads being<00:15:12.300> paused<00:15:12.839> released<00:15:13.320> there's<00:15:14.279> there's 00:15:14.269 --> 00:15:14.279 align:start position:0% being paused released there's there's 00:15:14.279 --> 00:15:16.310 align:start position:0% being paused released there's there's yeah<00:15:14.820> it's<00:15:15.120> it's<00:15:15.300> busy 00:15:16.310 --> 00:15:16.320 align:start position:0% yeah it's it's busy 00:15:16.320 --> 00:15:18.769 align:start position:0% yeah it's it's busy um<00:15:16.440> every<00:15:17.399> type<00:15:17.699> of<00:15:17.940> this<00:15:18.180> sort<00:15:18.660> of 00:15:18.769 --> 00:15:18.779 align:start position:0% um every type of this sort of 00:15:18.779 --> 00:15:21.050 align:start position:0% um every type of this sort of configuration<00:15:19.320> of<00:15:19.680> faults<00:15:20.339> that<00:15:20.519> we<00:15:20.760> put<00:15:20.940> into 00:15:21.050 --> 00:15:21.060 align:start position:0% configuration of faults that we put into 00:15:21.060 --> 00:15:22.430 align:start position:0% configuration of faults that we put into a<00:15:21.360> simulation<00:15:21.720> is<00:15:21.899> complete<00:15:22.260> again 00:15:22.430 --> 00:15:22.440 align:start position:0% a simulation is complete again 00:15:22.440 --> 00:15:25.610 align:start position:0% a simulation is complete again completely<00:15:22.920> deterministic<00:15:23.760> so<00:15:24.540> if<00:15:25.199> we<00:15:25.380> know 00:15:25.610 --> 00:15:25.620 align:start position:0% completely deterministic so if we know 00:15:25.620 --> 00:15:28.430 align:start position:0% completely deterministic so if we know that<00:15:26.160> this<00:15:26.399> ended<00:15:26.880> up<00:15:26.940> with<00:15:27.060> a<00:15:27.180> segful<00:15:27.540> we<00:15:28.019> know 00:15:28.430 --> 00:15:28.440 align:start position:0% that this ended up with a segful we know 00:15:28.440 --> 00:15:29.930 align:start position:0% that this ended up with a segful we know we<00:15:28.620> can<00:15:28.740> literally<00:15:28.980> put<00:15:29.160> exactly<00:15:29.579> the<00:15:29.760> same 00:15:29.930 --> 00:15:29.940 align:start position:0% we can literally put exactly the same 00:15:29.940 --> 00:15:32.629 align:start position:0% we can literally put exactly the same into<00:15:30.779> the<00:15:31.139> into<00:15:31.440> the<00:15:31.800> environment<00:15:32.279> it's 00:15:32.629 --> 00:15:32.639 align:start position:0% into the into the environment it's 00:15:32.639 --> 00:15:34.189 align:start position:0% into the into the environment it's basically<00:15:32.940> creating<00:15:33.240> a<00:15:33.420> pure<00:15:33.660> function<00:15:33.959> of 00:15:34.189 --> 00:15:34.199 align:start position:0% basically creating a pure function of 00:15:34.199 --> 00:15:36.829 align:start position:0% basically creating a pure function of the<00:15:34.320> entire<00:15:34.740> system<00:15:35.279> and<00:15:35.940> we<00:15:36.060> know<00:15:36.180> we<00:15:36.480> can<00:15:36.600> get 00:15:36.829 --> 00:15:36.839 align:start position:0% the entire system and we know we can get 00:15:36.839 --> 00:15:39.650 align:start position:0% the entire system and we know we can get the<00:15:37.560> exact<00:15:37.800> same<00:15:38.040> output<00:15:38.399> which<00:15:39.120> I<00:15:39.240> think<00:15:39.300> is<00:15:39.480> a 00:15:39.650 --> 00:15:39.660 align:start position:0% the exact same output which I think is a 00:15:39.660 --> 00:15:42.230 align:start position:0% the exact same output which I think is a tremendous<00:15:40.019> piece<00:15:40.500> of<00:15:40.579> technology<00:15:41.579> which<00:15:42.060> we 00:15:42.230 --> 00:15:42.240 align:start position:0% tremendous piece of technology which we 00:15:42.240 --> 00:15:43.970 align:start position:0% tremendous piece of technology which we have<00:15:42.420> under<00:15:42.899> the<00:15:43.139> hood 00:15:43.970 --> 00:15:43.980 align:start position:0% have under the hood 00:15:43.980 --> 00:15:47.030 align:start position:0% have under the hood what<00:15:44.399> the<00:15:44.579> numbers<00:15:44.699> like<00:15:45.060> well<00:15:45.420> yeah<00:15:46.199> you<00:15:46.920> know 00:15:47.030 --> 00:15:47.040 align:start position:0% what the numbers like well yeah you know 00:15:47.040 --> 00:15:49.490 align:start position:0% what the numbers like well yeah you know in<00:15:47.699> one<00:15:47.820> year<00:15:48.000> we've<00:15:48.360> we've<00:15:48.660> conducted<00:15:48.959> 31 00:15:49.490 --> 00:15:49.500 align:start position:0% in one year we've we've conducted 31 00:15:49.500 --> 00:15:52.250 align:start position:0% in one year we've we've conducted 31 years<00:15:49.800> worth<00:15:50.040> of<00:15:50.220> 24<00:15:50.519> 7<00:15:50.820> non-stop<00:15:51.300> testing 00:15:52.250 --> 00:15:52.260 align:start position:0% years worth of 24 7 non-stop testing 00:15:52.260 --> 00:15:55.250 align:start position:0% years worth of 24 7 non-stop testing um<00:15:52.380> that<00:15:53.279> that<00:15:53.519> has<00:15:53.899> processed<00:15:54.899> and<00:15:55.019> and 00:15:55.250 --> 00:15:55.260 align:start position:0% um that that has processed and and 00:15:55.260 --> 00:15:58.370 align:start position:0% um that that has processed and and explored<00:15:56.040> over<00:15:56.279> 50<00:15:56.519> million<00:15:56.940> edges<00:15:57.300> of<00:15:57.420> code 00:15:58.370 --> 00:15:58.380 align:start position:0% explored over 50 million edges of code 00:15:58.380 --> 00:16:00.410 align:start position:0% explored over 50 million edges of code um<00:15:58.500> you<00:15:58.860> know<00:15:58.980> out<00:15:59.399> of<00:15:59.579> that<00:15:59.699> and<00:16:00.120> you<00:16:00.240> can<00:16:00.300> see 00:16:00.410 --> 00:16:00.420 align:start position:0% um you know out of that and you can see 00:16:00.420 --> 00:16:01.910 align:start position:0% um you know out of that and you can see there<00:16:00.600> you<00:16:00.899> know<00:16:00.959> out<00:16:01.079> of<00:16:01.199> that<00:16:01.320> we've<00:16:01.500> got<00:16:01.620> 45 00:16:01.910 --> 00:16:01.920 align:start position:0% there you know out of that we've got 45 00:16:01.920 --> 00:16:04.850 align:start position:0% there you know out of that we've got 45 validated<00:16:02.699> errors<00:16:03.120> some<00:16:04.079> of<00:16:04.260> which<00:16:04.380> were 00:16:04.850 --> 00:16:04.860 align:start position:0% validated errors some of which were 00:16:04.860 --> 00:16:06.949 align:start position:0% validated errors some of which were painted<00:16:05.459> for<00:16:05.579> but<00:16:05.820> 30<00:16:06.000> of<00:16:06.240> the<00:16:06.360> 33<00:16:06.720> of<00:16:06.839> them 00:16:06.949 --> 00:16:06.959 align:start position:0% painted for but 30 of the 33 of them 00:16:06.959 --> 00:16:08.449 align:start position:0% painted for but 30 of the 33 of them were<00:16:07.079> logged<00:16:07.440> bugs 00:16:08.449 --> 00:16:08.459 align:start position:0% were logged bugs 00:16:08.459 --> 00:16:10.850 align:start position:0% were logged bugs um<00:16:08.579> that<00:16:09.000> were<00:16:09.180> pretty<00:16:09.600> catastrophic<00:16:10.800> um 00:16:10.850 --> 00:16:10.860 align:start position:0% um that were pretty catastrophic um 00:16:10.860 --> 00:16:14.030 align:start position:0% um that were pretty catastrophic um things<00:16:11.160> that<00:16:11.579> really<00:16:12.180> would<00:16:12.959> bring<00:16:13.199> either<00:16:13.440> an 00:16:14.030 --> 00:16:14.040 align:start position:0% things that really would bring either an 00:16:14.040 --> 00:16:16.910 align:start position:0% things that really would bring either an actual<00:16:14.279> note<00:16:14.519> down<00:16:14.820> so<00:16:15.060> panics<00:16:15.600> seg<00:16:16.019> faults<00:16:16.800> um 00:16:16.910 --> 00:16:16.920 align:start position:0% actual note down so panics seg faults um 00:16:16.920 --> 00:16:18.230 align:start position:0% actual note down so panics seg faults um we'd<00:16:17.279> have<00:16:17.399> you<00:16:17.579> know<00:16:17.699> nil<00:16:17.940> pointer 00:16:18.230 --> 00:16:18.240 align:start position:0% we'd have you know nil pointer 00:16:18.240 --> 00:16:20.269 align:start position:0% we'd have you know nil pointer exceptions<00:16:18.660> we'd<00:16:19.260> have<00:16:19.380> there's<00:16:19.860> there's<00:16:20.100> one 00:16:20.269 --> 00:16:20.279 align:start position:0% exceptions we'd have there's there's one 00:16:20.279 --> 00:16:21.590 align:start position:0% exceptions we'd have there's there's one I'm<00:16:20.519> going<00:16:20.639> to<00:16:20.760> bring<00:16:20.820> up<00:16:20.880> in<00:16:21.060> a<00:16:21.120> minute<00:16:21.180> with<00:16:21.420> a 00:16:21.590 --> 00:16:21.600 align:start position:0% I'm going to bring up in a minute with a 00:16:21.600 --> 00:16:23.689 align:start position:0% I'm going to bring up in a minute with a little<00:16:21.779> little<00:16:22.139> example<00:16:22.740> but 00:16:23.689 --> 00:16:23.699 align:start position:0% little little example but 00:16:23.699 --> 00:16:25.730 align:start position:0% little little example but um<00:16:23.760> things<00:16:24.600> that<00:16:24.779> you<00:16:24.899> don't<00:16:25.079> want<00:16:25.320> to<00:16:25.440> have 00:16:25.730 --> 00:16:25.740 align:start position:0% um things that you don't want to have 00:16:25.740 --> 00:16:28.550 align:start position:0% um things that you don't want to have like<00:16:26.579> living<00:16:26.940> in<00:16:27.300> your<00:16:27.420> code<00:16:27.600> base<00:16:27.839> and<00:16:28.199> and<00:16:28.380> I 00:16:28.550 --> 00:16:28.560 align:start position:0% like living in your code base and and I 00:16:28.560 --> 00:16:29.870 align:start position:0% like living in your code base and and I think<00:16:28.740> that's<00:16:28.920> you<00:16:29.160> know<00:16:29.339> we<00:16:29.519> would<00:16:29.639> forward 00:16:29.870 --> 00:16:29.880 align:start position:0% think that's you know we would forward 00:16:29.880 --> 00:16:31.069 align:start position:0% think that's you know we would forward those<00:16:30.120> through<00:16:30.300> to<00:16:30.540> the<00:16:30.660> different<00:16:30.720> client 00:16:31.069 --> 00:16:31.079 align:start position:0% those through to the different client 00:16:31.079 --> 00:16:33.769 align:start position:0% those through to the different client teams<00:16:31.440> and<00:16:32.100> they've<00:16:32.459> been<00:16:32.639> able<00:16:32.820> to<00:16:32.940> eradicate 00:16:33.769 --> 00:16:33.779 align:start position:0% teams and they've been able to eradicate 00:16:33.779 --> 00:16:35.990 align:start position:0% teams and they've been able to eradicate them<00:16:34.019> and<00:16:34.500> uh<00:16:34.680> and<00:16:34.980> obviously<00:16:35.339> through<00:16:35.639> the 00:16:35.990 --> 00:16:36.000 align:start position:0% them and uh and obviously through the 00:16:36.000 --> 00:16:37.850 align:start position:0% them and uh and obviously through the successful<00:16:36.720> merge 00:16:37.850 --> 00:16:37.860 align:start position:0% successful merge 00:16:37.860 --> 00:16:40.670 align:start position:0% successful merge um<00:16:37.920> it's<00:16:38.220> been<00:16:38.399> great<00:16:38.699> to<00:16:38.820> see<00:16:39.060> our<00:16:39.480> efforts<00:16:40.079> uh 00:16:40.670 --> 00:16:40.680 align:start position:0% um it's been great to see our efforts uh 00:16:40.680 --> 00:16:42.889 align:start position:0% um it's been great to see our efforts uh put<00:16:40.860> to<00:16:41.100> put<00:16:41.759> to<00:16:41.940> the<00:16:42.180> test 00:16:42.889 --> 00:16:42.899 align:start position:0% put to put to the test 00:16:42.899 --> 00:16:45.470 align:start position:0% put to put to the test as<00:16:43.199> he<00:16:43.380> wants<00:16:43.620> an<00:16:43.740> example<00:16:44.040> or<00:16:44.820> I'll<00:16:45.240> give<00:16:45.360> you 00:16:45.470 --> 00:16:45.480 align:start position:0% as he wants an example or I'll give you 00:16:45.480 --> 00:16:46.670 align:start position:0% as he wants an example or I'll give you I'll<00:16:45.660> give<00:16:45.839> you<00:16:45.899> some 00:16:46.670 --> 00:16:46.680 align:start position:0% I'll give you some 00:16:46.680 --> 00:16:49.730 align:start position:0% I'll give you some um<00:16:46.740> so<00:16:47.600> here's<00:16:48.600> here's<00:16:48.839> an<00:16:48.899> output<00:16:49.139> of<00:16:49.380> our<00:16:49.500> of 00:16:49.730 --> 00:16:49.740 align:start position:0% um so here's here's an output of our of 00:16:49.740 --> 00:16:51.290 align:start position:0% um so here's here's an output of our of our<00:16:49.980> sort<00:16:50.100> of<00:16:50.220> one<00:16:50.339> of<00:16:50.459> the<00:16:50.519> runs<00:16:50.820> this<00:16:51.180> would 00:16:51.290 --> 00:16:51.300 align:start position:0% our sort of one of the runs this would 00:16:51.300 --> 00:16:53.150 align:start position:0% our sort of one of the runs this would come<00:16:51.480> through<00:16:51.660> from<00:16:51.959> an<00:16:52.139> email<00:16:52.259> and<00:16:52.800> hopefully 00:16:53.150 --> 00:16:53.160 align:start position:0% come through from an email and hopefully 00:16:53.160 --> 00:16:54.650 align:start position:0% come through from an email and hopefully you<00:16:53.220> can<00:16:53.339> see<00:16:53.399> it's<00:16:53.519> Biven<00:16:53.940> our<00:16:54.000> chart<00:16:54.240> you've 00:16:54.650 --> 00:16:54.660 align:start position:0% you can see it's Biven our chart you've 00:16:54.660 --> 00:16:55.970 align:start position:0% you can see it's Biven our chart you've seen<00:16:54.779> the<00:16:54.959> side<00:16:55.079> of<00:16:55.259> the<00:16:55.380> select<00:16:55.620> the<00:16:55.680> stuff<00:16:55.860> on 00:16:55.970 --> 00:16:55.980 align:start position:0% seen the side of the select the stuff on 00:16:55.980 --> 00:16:58.189 align:start position:0% seen the side of the select the stuff on the<00:16:56.100> right<00:16:56.220> hand<00:16:56.339> side<00:16:56.519> but<00:16:57.180> down<00:16:57.660> here<00:16:57.899> you 00:16:58.189 --> 00:16:58.199 align:start position:0% the right hand side but down here you 00:16:58.199 --> 00:16:59.749 align:start position:0% the right hand side but down here you can<00:16:58.259> see<00:16:58.440> a<00:16:58.560> whole<00:16:58.680> host<00:16:58.920> of<00:16:59.160> assertions<00:16:59.579> that 00:16:59.749 --> 00:16:59.759 align:start position:0% can see a whole host of assertions that 00:16:59.759 --> 00:17:01.730 align:start position:0% can see a whole host of assertions that we've<00:16:59.940> got<00:17:00.120> running<00:17:00.600> across<00:17:01.259> across<00:17:01.620> the 00:17:01.730 --> 00:17:01.740 align:start position:0% we've got running across across the 00:17:01.740 --> 00:17:03.110 align:start position:0% we've got running across across the entire<00:17:02.040> network 00:17:03.110 --> 00:17:03.120 align:start position:0% entire network 00:17:03.120 --> 00:17:04.909 align:start position:0% entire network um<00:17:03.180> this<00:17:03.600> this<00:17:03.779> is<00:17:03.959> actually<00:17:04.140> flagged<00:17:04.620> up<00:17:04.740> by 00:17:04.909 --> 00:17:04.919 align:start position:0% um this this is actually flagged up by 00:17:04.919 --> 00:17:06.590 align:start position:0% um this this is actually flagged up by fail<00:17:05.220> and<00:17:05.520> they've<00:17:05.760> got<00:17:05.819> a<00:17:05.939> fail<00:17:06.120> on<00:17:06.299> a<00:17:06.360> seg 00:17:06.590 --> 00:17:06.600 align:start position:0% fail and they've got a fail on a seg 00:17:06.600 --> 00:17:08.449 align:start position:0% fail and they've got a fail on a seg fault<00:17:06.839> this<00:17:07.380> is<00:17:07.500> this<00:17:07.860> is<00:17:07.980> you<00:17:08.160> know<00:17:08.280> something 00:17:08.449 --> 00:17:08.459 align:start position:0% fault this is this is you know something 00:17:08.459 --> 00:17:11.030 align:start position:0% fault this is this is you know something that<00:17:08.640> is<00:17:08.880> is<00:17:09.000> absolutely<00:17:09.600> real<00:17:09.839> zigzag<00:17:10.740> V 00:17:11.030 --> 00:17:11.040 align:start position:0% that is is absolutely real zigzag V 00:17:11.040 --> 00:17:13.669 align:start position:0% that is is absolutely real zigzag V illegal<00:17:11.819> storage<00:17:12.059> access<00:17:12.419> attempt<00:17:13.319> to<00:17:13.500> read 00:17:13.669 --> 00:17:13.679 align:start position:0% illegal storage access attempt to read 00:17:13.679 --> 00:17:15.590 align:start position:0% illegal storage access attempt to read from<00:17:13.919> nil<00:17:14.280> question<00:17:14.640> mark 00:17:15.590 --> 00:17:15.600 align:start position:0% from nil question mark 00:17:15.600 --> 00:17:17.090 align:start position:0% from nil question mark I<00:17:15.959> guess<00:17:16.140> I'm<00:17:16.260> really<00:17:16.380> interested<00:17:16.679> ones<00:17:16.919> you 00:17:17.090 --> 00:17:17.100 align:start position:0% I guess I'm really interested ones you 00:17:17.100 --> 00:17:18.710 align:start position:0% I guess I'm really interested ones you get<00:17:17.160> like<00:17:17.280> you<00:17:17.459> please<00:17:17.880> report<00:17:18.059> this<00:17:18.419> oh 00:17:18.710 --> 00:17:18.720 align:start position:0% get like you please report this oh 00:17:18.720 --> 00:17:20.630 align:start position:0% get like you please report this oh please<00:17:19.020> repeat<00:17:19.140> please<00:17:19.500> fix<00:17:19.679> this 00:17:20.630 --> 00:17:20.640 align:start position:0% please repeat please fix this 00:17:20.640 --> 00:17:22.970 align:start position:0% please repeat please fix this um so<00:17:21.179> this<00:17:21.839> is<00:17:21.900> just<00:17:22.079> an<00:17:22.260> example<00:17:22.500> here<00:17:22.740> and 00:17:22.970 --> 00:17:22.980 align:start position:0% um so this is just an example here and 00:17:22.980 --> 00:17:25.069 align:start position:0% um so this is just an example here and we're<00:17:23.160> like<00:17:23.280> What<00:17:23.459> do<00:17:23.640> we<00:17:23.699> do<00:17:23.819> now<00:17:24.059> how<00:17:24.900> do<00:17:24.959> we 00:17:25.069 --> 00:17:25.079 align:start position:0% we're like What do we do now how do we 00:17:25.079 --> 00:17:26.449 align:start position:0% we're like What do we do now how do we how<00:17:25.380> do<00:17:25.500> we<00:17:25.559> take<00:17:25.679> it<00:17:25.860> to<00:17:25.980> the<00:17:26.100> next<00:17:26.220> step 00:17:26.449 --> 00:17:26.459 align:start position:0% how do we take it to the next step 00:17:26.459 --> 00:17:27.590 align:start position:0% how do we take it to the next step because<00:17:26.640> it's<00:17:26.819> great<00:17:27.000> saying<00:17:27.240> well<00:17:27.360> you've 00:17:27.590 --> 00:17:27.600 align:start position:0% because it's great saying well you've 00:17:27.600 --> 00:17:28.549 align:start position:0% because it's great saying well you've got<00:17:27.720> a<00:17:27.839> problem 00:17:28.549 --> 00:17:28.559 align:start position:0% got a problem 00:17:28.559 --> 00:17:30.110 align:start position:0% got a problem um<00:17:28.620> this<00:17:28.799> you<00:17:28.980> can<00:17:29.100> see<00:17:29.220> here<00:17:29.400> is<00:17:29.580> actually<00:17:29.760> for 00:17:30.110 --> 00:17:30.120 align:start position:0% um this you can see here is actually for 00:17:30.120 --> 00:17:32.210 align:start position:0% um this you can see here is actually for the<00:17:30.720> node<00:17:30.900> that's<00:17:31.080> running<00:17:31.260> Nimbus<00:17:31.740> and<00:17:31.919> Geth 00:17:32.210 --> 00:17:32.220 align:start position:0% the node that's running Nimbus and Geth 00:17:32.220 --> 00:17:34.549 align:start position:0% the node that's running Nimbus and Geth so<00:17:32.700> we<00:17:33.240> know<00:17:33.419> there's<00:17:33.600> an<00:17:33.840> issue<00:17:34.080> there<00:17:34.260> so 00:17:34.549 --> 00:17:34.559 align:start position:0% so we know there's an issue there so 00:17:34.559 --> 00:17:36.049 align:start position:0% so we know there's an issue there so okay<00:17:34.740> fine<00:17:35.039> have<00:17:35.520> you<00:17:35.700> got<00:17:35.820> any<00:17:35.940> other 00:17:36.049 --> 00:17:36.059 align:start position:0% okay fine have you got any other 00:17:36.059 --> 00:17:37.850 align:start position:0% okay fine have you got any other occurrences<00:17:36.660> on<00:17:36.840> any<00:17:37.020> of<00:17:37.440> the<00:17:37.500> combinations 00:17:37.850 --> 00:17:37.860 align:start position:0% occurrences on any of the combinations 00:17:37.860 --> 00:17:39.289 align:start position:0% occurrences on any of the combinations we<00:17:38.220> do 00:17:39.289 --> 00:17:39.299 align:start position:0% we do 00:17:39.299 --> 00:17:40.789 align:start position:0% we do um<00:17:39.360> so<00:17:39.539> okay<00:17:39.660> that's<00:17:39.960> cool 00:17:40.789 --> 00:17:40.799 align:start position:0% um so okay that's cool 00:17:40.799 --> 00:17:42.830 align:start position:0% um so okay that's cool um<00:17:40.919> well<00:17:41.280> let's<00:17:41.400> let's<00:17:41.640> look<00:17:41.940> at<00:17:42.059> an<00:17:42.480> example 00:17:42.830 --> 00:17:42.840 align:start position:0% um well let's let's look at an example 00:17:42.840 --> 00:17:45.950 align:start position:0% um well let's let's look at an example uh<00:17:43.500> of<00:17:43.799> an<00:17:44.160> actual<00:17:44.460> kind<00:17:44.700> of<00:17:44.820> log<00:17:45.240> entry<00:17:45.780> that's 00:17:45.950 --> 00:17:45.960 align:start position:0% uh of an actual kind of log entry that's 00:17:45.960 --> 00:17:47.270 align:start position:0% uh of an actual kind of log entry that's coming<00:17:46.140> through<00:17:46.320> so<00:17:46.500> this<00:17:46.679> is<00:17:46.740> this<00:17:46.980> is<00:17:47.100> a 00:17:47.270 --> 00:17:47.280 align:start position:0% coming through so this is this is a 00:17:47.280 --> 00:17:50.029 align:start position:0% coming through so this is this is a unified<00:17:47.640> log<00:17:48.179> the<00:17:48.900> serialized<00:17:49.620> activity 00:17:50.029 --> 00:17:50.039 align:start position:0% unified log the serialized activity 00:17:50.039 --> 00:17:51.590 align:start position:0% unified log the serialized activity that's<00:17:50.400> occurring<00:17:50.820> across<00:17:51.179> the<00:17:51.240> entire 00:17:51.590 --> 00:17:51.600 align:start position:0% that's occurring across the entire 00:17:51.600 --> 00:17:53.450 align:start position:0% that's occurring across the entire simulated<00:17:52.440> environment 00:17:53.450 --> 00:17:53.460 align:start position:0% simulated environment 00:17:53.460 --> 00:17:56.630 align:start position:0% simulated environment bit<00:17:53.880> of<00:17:54.059> mouthful<00:17:54.360> so<00:17:55.260> you<00:17:55.860> see<00:17:56.039> you<00:17:56.460> can<00:17:56.520> see 00:17:56.630 --> 00:17:56.640 align:start position:0% bit of mouthful so you see you can see 00:17:56.640 --> 00:17:58.430 align:start position:0% bit of mouthful so you see you can see here<00:17:56.820> on<00:17:57.000> the<00:17:57.120> third<00:17:57.299> column<00:17:57.660> the<00:17:58.020> blue<00:17:58.080> column 00:17:58.430 --> 00:17:58.440 align:start position:0% here on the third column the blue column 00:17:58.440 --> 00:18:00.169 align:start position:0% here on the third column the blue column here<00:17:58.679> again<00:17:58.860> this<00:17:59.280> is<00:17:59.340> just<00:17:59.520> showing<00:17:59.820> us<00:17:59.940> all 00:18:00.169 --> 00:18:00.179 align:start position:0% here again this is just showing us all 00:18:00.179 --> 00:18:01.669 align:start position:0% here again this is just showing us all the<00:18:00.360> different<00:18:00.480> combinations<00:18:01.140> so<00:18:01.380> we've<00:18:01.620> got 00:18:01.669 --> 00:18:01.679 align:start position:0% the different combinations so we've got 00:18:01.679 --> 00:18:03.350 align:start position:0% the different combinations so we've got Cloud<00:18:01.860> we've<00:18:02.100> got<00:18:02.160> prism<00:18:02.400> client<00:18:02.820> Aragon 00:18:03.350 --> 00:18:03.360 align:start position:0% Cloud we've got prism client Aragon 00:18:03.360 --> 00:18:05.770 align:start position:0% Cloud we've got prism client Aragon we've<00:18:03.900> got<00:18:04.380> um<00:18:04.440> there's<00:18:04.799> nimbers<00:18:05.340> never<00:18:05.520> mind 00:18:05.770 --> 00:18:05.780 align:start position:0% we've got um there's nimbers never mind 00:18:05.780 --> 00:18:08.510 align:start position:0% we've got um there's nimbers never mind nimbuspessu<00:18:06.780> all<00:18:07.260> kind<00:18:07.620> of<00:18:07.679> serialized<00:18:08.460> and 00:18:08.510 --> 00:18:08.520 align:start position:0% nimbuspessu all kind of serialized and 00:18:08.520 --> 00:18:10.490 align:start position:0% nimbuspessu all kind of serialized and you<00:18:08.640> can<00:18:08.700> see<00:18:08.760> that<00:18:08.880> we've<00:18:09.299> got<00:18:09.419> a<00:18:09.660> concept<00:18:10.380> of 00:18:10.490 --> 00:18:10.500 align:start position:0% you can see that we've got a concept of 00:18:10.500 --> 00:18:13.070 align:start position:0% you can see that we've got a concept of time<00:18:10.740> running<00:18:11.039> through<00:18:11.340> so<00:18:11.640> this<00:18:12.539> blown<00:18:12.900> up 00:18:13.070 --> 00:18:13.080 align:start position:0% time running through so this blown up 00:18:13.080 --> 00:18:14.930 align:start position:0% time running through so this blown up piece<00:18:13.380> is<00:18:13.500> basically<00:18:14.039> the<00:18:14.220> stack<00:18:14.400> trace<00:18:14.760> of 00:18:14.930 --> 00:18:14.940 align:start position:0% piece is basically the stack trace of 00:18:14.940 --> 00:18:16.250 align:start position:0% piece is basically the stack trace of showing<00:18:15.240> us<00:18:15.299> kind<00:18:15.480> of<00:18:15.600> what<00:18:15.720> is<00:18:15.840> happening<00:18:16.080> and 00:18:16.250 --> 00:18:16.260 align:start position:0% showing us kind of what is happening and 00:18:16.260 --> 00:18:17.630 align:start position:0% showing us kind of what is happening and Nimbus<00:18:16.620> is<00:18:16.740> having<00:18:16.919> some<00:18:17.100> issue<00:18:17.460> it's 00:18:17.630 --> 00:18:17.640 align:start position:0% Nimbus is having some issue it's 00:18:17.640 --> 00:18:23.230 align:start position:0% Nimbus is having some issue it's receiving<00:18:18.000> some<00:18:18.179> Json<00:18:18.539> trying<00:18:19.500> to<00:18:19.620> figure<00:18:19.740> out 00:18:23.230 --> 00:18:23.240 align:start position:0% 00:18:23.240 --> 00:18:25.549 align:start position:0% not<00:18:24.240> doing<00:18:24.360> too<00:18:24.539> well<00:18:24.660> for<00:18:24.900> it<00:18:25.020> so<00:18:25.200> because<00:18:25.320> it 00:18:25.549 --> 00:18:25.559 align:start position:0% not doing too well for it so because it 00:18:25.559 --> 00:18:28.010 align:start position:0% not doing too well for it so because it basically<00:18:26.280> crashes<00:18:26.700> the<00:18:26.880> entire<00:18:27.120> node 00:18:28.010 --> 00:18:28.020 align:start position:0% basically crashes the entire node 00:18:28.020 --> 00:18:29.990 align:start position:0% basically crashes the entire node um<00:18:28.140> what<00:18:28.500> you<00:18:28.679> know<00:18:28.799> so<00:18:29.039> we<00:18:29.160> go<00:18:29.460> okay<00:18:29.580> this<00:18:29.940> is 00:18:29.990 --> 00:18:30.000 align:start position:0% um what you know so we go okay this is 00:18:30.000 --> 00:18:31.610 align:start position:0% um what you know so we go okay this is cool<00:18:30.179> this<00:18:30.480> is<00:18:30.600> this<00:18:30.960> is<00:18:31.020> where<00:18:31.140> I<00:18:31.260> kind<00:18:31.440> of<00:18:31.500> go 00:18:31.610 --> 00:18:31.620 align:start position:0% cool this is this is where I kind of go 00:18:31.620 --> 00:18:32.810 align:start position:0% cool this is this is where I kind of go yeah<00:18:31.919> you<00:18:32.220> know<00:18:32.340> there's<00:18:32.460> got<00:18:32.700> something 00:18:32.810 --> 00:18:32.820 align:start position:0% yeah you know there's got something 00:18:32.820 --> 00:18:34.549 align:start position:0% yeah you know there's got something something<00:18:33.120> of<00:18:33.360> Interest<00:18:33.480> here 00:18:34.549 --> 00:18:34.559 align:start position:0% something of Interest here 00:18:34.559 --> 00:18:35.990 align:start position:0% something of Interest here um<00:18:34.620> another<00:18:34.980> example<00:18:35.340> here<00:18:35.520> this<00:18:35.760> is<00:18:35.880> just 00:18:35.990 --> 00:18:36.000 align:start position:0% um another example here this is just 00:18:36.000 --> 00:18:37.669 align:start position:0% um another example here this is just from<00:18:36.179> from<00:18:36.360> Prism 00:18:37.669 --> 00:18:37.679 align:start position:0% from from Prism 00:18:37.679 --> 00:18:39.169 align:start position:0% from from Prism um<00:18:37.799> again 00:18:39.169 --> 00:18:39.179 align:start position:0% um again 00:18:39.179 --> 00:18:41.510 align:start position:0% um again I<00:18:39.720> don't<00:18:39.840> love<00:18:40.140> sort<00:18:40.620> of<00:18:40.799> seeing<00:18:40.980> panics<00:18:41.340> but 00:18:41.510 --> 00:18:41.520 align:start position:0% I don't love sort of seeing panics but 00:18:41.520 --> 00:18:43.310 align:start position:0% I don't love sort of seeing panics but like<00:18:41.700> you<00:18:41.820> know<00:18:41.940> it<00:18:42.059> does<00:18:42.360> it<00:18:42.600> does<00:18:42.900> show<00:18:43.080> that 00:18:43.310 --> 00:18:43.320 align:start position:0% like you know it does it does show that 00:18:43.320 --> 00:18:44.930 align:start position:0% like you know it does it does show that there's<00:18:43.500> something<00:18:43.740> like<00:18:44.100> of<00:18:44.460> value<00:18:44.700> here 00:18:44.930 --> 00:18:44.940 align:start position:0% there's something like of value here 00:18:44.940 --> 00:18:46.669 align:start position:0% there's something like of value here that<00:18:45.120> we're<00:18:45.240> really<00:18:45.539> stressing 00:18:46.669 --> 00:18:46.679 align:start position:0% that we're really stressing 00:18:46.679 --> 00:18:48.409 align:start position:0% that we're really stressing um<00:18:46.740> the<00:18:46.919> the<00:18:47.039> entire<00:18:47.400> environment<00:18:47.820> so<00:18:48.299> again 00:18:48.409 --> 00:18:48.419 align:start position:0% um the the entire environment so again 00:18:48.419 --> 00:18:50.350 align:start position:0% um the the entire environment so again invalid<00:18:48.960> memory<00:18:49.200> address 00:18:50.350 --> 00:18:50.360 align:start position:0% invalid memory address 00:18:50.360 --> 00:18:53.150 align:start position:0% invalid memory address yeah<00:18:51.360> okay<00:18:51.660> cool<00:18:51.900> what<00:18:52.080> do<00:18:52.200> we<00:18:52.260> do<00:18:52.440> now<00:18:52.559> you 00:18:53.150 --> 00:18:53.160 align:start position:0% yeah okay cool what do we do now you 00:18:53.160 --> 00:18:54.470 align:start position:0% yeah okay cool what do we do now you know<00:18:53.280> do<00:18:53.400> we<00:18:53.520> descend<00:18:53.760> it<00:18:53.880> to<00:18:54.000> the<00:18:54.120> client<00:18:54.299> team 00:18:54.470 --> 00:18:54.480 align:start position:0% know do we descend it to the client team 00:18:54.480 --> 00:18:57.289 align:start position:0% know do we descend it to the client team well<00:18:54.840> yeah<00:18:55.140> you<00:18:55.320> can<00:18:55.500> and<00:18:55.799> they<00:18:56.100> might<00:18:56.280> go<00:18:56.820> I<00:18:57.059> I 00:18:57.289 --> 00:18:57.299 align:start position:0% well yeah you can and they might go I I 00:18:57.299 --> 00:18:59.750 align:start position:0% well yeah you can and they might go I I wrote<00:18:57.660> that<00:18:57.840> code<00:18:58.080> I<00:18:58.919> can<00:18:58.980> see<00:18:59.220> what's<00:18:59.520> going 00:18:59.750 --> 00:18:59.760 align:start position:0% wrote that code I can see what's going 00:18:59.760 --> 00:19:00.950 align:start position:0% wrote that code I can see what's going on<00:18:59.940> here 00:19:00.950 --> 00:19:00.960 align:start position:0% on here 00:19:00.960 --> 00:19:02.330 align:start position:0% on here um 00:19:02.330 --> 00:19:02.340 align:start position:0% um 00:19:02.340 --> 00:19:05.630 align:start position:0% um well<00:19:02.880> she<00:19:03.360> had<00:19:03.480> to<00:19:03.600> do<00:19:03.720> it<00:19:03.780> didn't<00:19:04.020> she<00:19:04.260> yeah<00:19:04.640> if 00:19:05.630 --> 00:19:05.640 align:start position:0% well she had to do it didn't she yeah if 00:19:05.640 --> 00:19:07.370 align:start position:0% well she had to do it didn't she yeah if she<00:19:05.760> could<00:19:05.940> turn<00:19:06.120> back<00:19:06.299> time<00:19:06.419> well<00:19:06.840> the<00:19:07.260> great 00:19:07.370 --> 00:19:07.380 align:start position:0% she could turn back time well the great 00:19:07.380 --> 00:19:09.110 align:start position:0% she could turn back time well the great news<00:19:07.559> about<00:19:07.799> deterministic<00:19:08.520> environments<00:19:09.000> is 00:19:09.110 --> 00:19:09.120 align:start position:0% news about deterministic environments is 00:19:09.120 --> 00:19:11.210 align:start position:0% news about deterministic environments is you<00:19:09.299> can<00:19:09.419> turn<00:19:09.660> back<00:19:09.900> time<00:19:10.080> right<00:19:10.380> so<00:19:10.799> we're 00:19:11.210 --> 00:19:11.220 align:start position:0% you can turn back time right so we're 00:19:11.220 --> 00:19:13.250 align:start position:0% you can turn back time right so we're going<00:19:11.580> to<00:19:11.760> basically<00:19:12.000> jump<00:19:12.299> into<00:19:12.539> the<00:19:12.900> actual 00:19:13.250 --> 00:19:13.260 align:start position:0% going to basically jump into the actual 00:19:13.260 --> 00:19:14.870 align:start position:0% going to basically jump into the actual environment<00:19:13.679> and<00:19:13.980> actually<00:19:14.160> say<00:19:14.400> okay<00:19:14.580> right 00:19:14.870 --> 00:19:14.880 align:start position:0% environment and actually say okay right 00:19:14.880 --> 00:19:18.590 align:start position:0% environment and actually say okay right how<00:19:15.980> when<00:19:16.980> does<00:19:17.160> this<00:19:17.340> manifest<00:19:17.760> like<00:19:18.179> is<00:19:18.360> it 00:19:18.590 --> 00:19:18.600 align:start position:0% how when does this manifest like is it 00:19:18.600 --> 00:19:20.810 align:start position:0% how when does this manifest like is it okay<00:19:18.780> it<00:19:19.200> crashes 00:19:20.810 --> 00:19:20.820 align:start position:0% okay it crashes 00:19:20.820 --> 00:19:23.330 align:start position:0% okay it crashes was<00:19:21.419> it<00:19:21.660> a<00:19:21.840> second<00:19:22.020> ago<00:19:22.380> was<00:19:22.740> it<00:19:22.919> five<00:19:23.100> seconds 00:19:23.330 --> 00:19:23.340 align:start position:0% was it a second ago was it five seconds 00:19:23.340 --> 00:19:25.669 align:start position:0% was it a second ago was it five seconds ago<00:19:23.640> what<00:19:23.940> happened<00:19:24.600> in<00:19:24.840> the<00:19:25.020> execution<00:19:25.380> pass 00:19:25.669 --> 00:19:25.679 align:start position:0% ago what happened in the execution pass 00:19:25.679 --> 00:19:27.289 align:start position:0% ago what happened in the execution pass of<00:19:25.980> all<00:19:26.160> the<00:19:26.280> different<00:19:26.400> Opera<00:19:26.820> operating 00:19:27.289 --> 00:19:27.299 align:start position:0% of all the different Opera operating 00:19:27.299 --> 00:19:29.690 align:start position:0% of all the different Opera operating nodes<00:19:28.080> with<00:19:28.740> all<00:19:28.860> the<00:19:28.980> fall<00:19:29.100> injection<00:19:29.400> going 00:19:29.690 --> 00:19:29.700 align:start position:0% nodes with all the fall injection going 00:19:29.700 --> 00:19:31.789 align:start position:0% nodes with all the fall injection going on<00:19:29.880> or<00:19:30.360> or<00:19:30.480> was<00:19:30.900> it 00:19:31.789 --> 00:19:31.799 align:start position:0% on or or was it 00:19:31.799 --> 00:19:34.490 align:start position:0% on or or was it um<00:19:31.860> yeah<00:19:32.280> what<00:19:32.880> where<00:19:33.299> where<00:19:33.840> do<00:19:34.080> we<00:19:34.200> where<00:19:34.380> do 00:19:34.490 --> 00:19:34.500 align:start position:0% um yeah what where where do we where do 00:19:34.500 --> 00:19:36.409 align:start position:0% um yeah what where where do we where do we<00:19:34.620> see<00:19:34.740> this<00:19:34.919> like<00:19:35.340> actual<00:19:35.700> kind<00:19:36.000> of<00:19:36.120> thing 00:19:36.409 --> 00:19:36.419 align:start position:0% we see this like actual kind of thing 00:19:36.419 --> 00:19:37.549 align:start position:0% we see this like actual kind of thing manifest 00:19:37.549 --> 00:19:37.559 align:start position:0% manifest 00:19:37.559 --> 00:19:40.669 align:start position:0% manifest and<00:19:37.980> so<00:19:38.160> we<00:19:39.120> we<00:19:39.419> want<00:19:39.600> to<00:19:39.720> look<00:19:39.840> back<00:19:40.020> so<00:19:40.500> many 00:19:40.669 --> 00:19:40.679 align:start position:0% and so we we want to look back so many 00:19:40.679 --> 00:19:41.930 align:start position:0% and so we we want to look back so many seconds<00:19:40.860> we<00:19:41.160> may<00:19:41.280> want<00:19:41.400> to<00:19:41.520> turn<00:19:41.640> on<00:19:41.760> car 00:19:41.930 --> 00:19:41.940 align:start position:0% seconds we may want to turn on car 00:19:41.940 --> 00:19:44.090 align:start position:0% seconds we may want to turn on car packet<00:19:42.360> capture<00:19:42.600> pack<00:19:42.840> capture<00:19:43.260> isn't<00:19:43.620> by 00:19:44.090 --> 00:19:44.100 align:start position:0% packet capture pack capture isn't by 00:19:44.100 --> 00:19:45.770 align:start position:0% packet capture pack capture isn't by default<00:19:44.460> just<00:19:44.820> because<00:19:44.940> the<00:19:45.179> amount<00:19:45.360> of<00:19:45.480> data 00:19:45.770 --> 00:19:45.780 align:start position:0% default just because the amount of data 00:19:45.780 --> 00:19:47.570 align:start position:0% default just because the amount of data but<00:19:45.960> it<00:19:46.260> isn't<00:19:46.440> turned<00:19:46.620> on<00:19:46.679> by<00:19:46.860> default<00:19:47.400> we 00:19:47.570 --> 00:19:47.580 align:start position:0% but it isn't turned on by default we 00:19:47.580 --> 00:19:49.250 align:start position:0% but it isn't turned on by default we want<00:19:47.700> to<00:19:47.880> be<00:19:48.120> quite<00:19:48.299> selective<00:19:48.720> about<00:19:48.900> kind<00:19:49.140> of 00:19:49.250 --> 00:19:49.260 align:start position:0% want to be quite selective about kind of 00:19:49.260 --> 00:19:51.289 align:start position:0% want to be quite selective about kind of where<00:19:49.679> we<00:19:49.860> see<00:19:50.039> packet<00:19:50.700> capture<00:19:51.000> happening 00:19:51.289 --> 00:19:51.299 align:start position:0% where we see packet capture happening 00:19:51.299 --> 00:19:53.330 align:start position:0% where we see packet capture happening and<00:19:51.780> and<00:19:51.900> then<00:19:52.080> we<00:19:52.200> can<00:19:52.320> look<00:19:52.440> at<00:19:52.559> the<00:19:52.679> data<00:19:53.039> see 00:19:53.330 --> 00:19:53.340 align:start position:0% and and then we can look at the data see 00:19:53.340 --> 00:19:55.130 align:start position:0% and and then we can look at the data see if<00:19:53.460> again<00:19:53.700> we<00:19:53.880> can<00:19:54.000> rerun<00:19:54.299> it 00:19:55.130 --> 00:19:55.140 align:start position:0% if again we can rerun it 00:19:55.140 --> 00:19:57.110 align:start position:0% if again we can rerun it um<00:19:55.200> again<00:19:55.440> obviously<00:19:55.740> determinism<00:19:56.340> you're 00:19:57.110 --> 00:19:57.120 align:start position:0% um again obviously determinism you're 00:19:57.120 --> 00:19:58.430 align:start position:0% um again obviously determinism you're stressing<00:19:57.419> a<00:19:57.539> little<00:19:57.660> bit<00:19:57.780> of<00:19:57.900> kind<00:19:58.080> of<00:19:58.200> will 00:19:58.430 --> 00:19:58.440 align:start position:0% stressing a little bit of kind of will 00:19:58.440 --> 00:20:00.169 align:start position:0% stressing a little bit of kind of will it<00:19:58.620> still<00:19:58.860> be<00:19:59.039> deterministic<00:19:59.640> if<00:19:59.760> I<00:19:59.940> suddenly 00:20:00.169 --> 00:20:00.179 align:start position:0% it still be deterministic if I suddenly 00:20:00.179 --> 00:20:01.730 align:start position:0% it still be deterministic if I suddenly turn<00:20:00.299> on<00:20:00.419> packaged<00:20:00.900> at<00:20:01.140> a<00:20:01.260> moment<00:20:01.380> in<00:20:01.559> time 00:20:01.730 --> 00:20:01.740 align:start position:0% turn on packaged at a moment in time 00:20:01.740 --> 00:20:04.789 align:start position:0% turn on packaged at a moment in time let's<00:20:02.700> have<00:20:03.000> to<00:20:03.120> look<00:20:03.240> at<00:20:03.360> that<00:20:03.480> but<00:20:03.960> but<00:20:04.200> what 00:20:04.789 --> 00:20:04.799 align:start position:0% let's have to look at that but but what 00:20:04.799 --> 00:20:06.230 align:start position:0% let's have to look at that but but what we've<00:20:04.980> seen<00:20:05.160> is<00:20:05.340> actually<00:20:05.520> yeah<00:20:05.940> you 00:20:06.230 --> 00:20:06.240 align:start position:0% we've seen is actually yeah you 00:20:06.240 --> 00:20:07.970 align:start position:0% we've seen is actually yeah you generally<00:20:06.539> if<00:20:06.780> you've<00:20:06.960> seen<00:20:07.080> something<00:20:07.380> you 00:20:07.970 --> 00:20:07.980 align:start position:0% generally if you've seen something you 00:20:07.980 --> 00:20:10.070 align:start position:0% generally if you've seen something you know<00:20:08.100> manifest<00:20:08.640> then<00:20:09.000> we<00:20:09.600> can<00:20:09.660> we<00:20:09.900> can 00:20:10.070 --> 00:20:10.080 align:start position:0% know manifest then we can we can 00:20:10.080 --> 00:20:12.590 align:start position:0% know manifest then we can we can actively<00:20:10.740> kind<00:20:11.280> of<00:20:11.400> kind<00:20:11.880> of<00:20:12.000> turn<00:20:12.179> on<00:20:12.360> things 00:20:12.590 --> 00:20:12.600 align:start position:0% actively kind of kind of turn on things 00:20:12.600 --> 00:20:14.210 align:start position:0% actively kind of kind of turn on things to<00:20:12.840> help<00:20:12.960> kind<00:20:13.260> of<00:20:13.380> debug<00:20:13.679> and<00:20:13.860> work<00:20:14.039> out 00:20:14.210 --> 00:20:14.220 align:start position:0% to help kind of debug and work out 00:20:14.220 --> 00:20:16.010 align:start position:0% to help kind of debug and work out what's<00:20:14.400> going<00:20:14.580> on<00:20:15.179> there's<00:20:15.600> some<00:20:15.840> really 00:20:16.010 --> 00:20:16.020 align:start position:0% what's going on there's some really 00:20:16.020 --> 00:20:17.090 align:start position:0% what's going on there's some really interesting<00:20:16.260> stuff<00:20:16.440> coming<00:20:16.679> through<00:20:16.860> next 00:20:17.090 --> 00:20:17.100 align:start position:0% interesting stuff coming through next 00:20:17.100 --> 00:20:19.250 align:start position:0% interesting stuff coming through next year<00:20:17.220> which<00:20:17.460> I<00:20:17.700> can't<00:20:17.820> share<00:20:18.120> but<00:20:18.419> really<00:20:19.080> cool 00:20:19.250 --> 00:20:19.260 align:start position:0% year which I can't share but really cool 00:20:19.260 --> 00:20:21.409 align:start position:0% year which I can't share but really cool so<00:20:19.799> this<00:20:20.340> is<00:20:20.460> what<00:20:20.580> we<00:20:20.700> can<00:20:20.820> do<00:20:20.940> today<00:20:21.120> this<00:20:21.299> is 00:20:21.409 --> 00:20:21.419 align:start position:0% so this is what we can do today this is 00:20:21.419 --> 00:20:23.390 align:start position:0% so this is what we can do today this is what<00:20:21.539> we've<00:20:21.660> done<00:20:21.840> with<00:20:22.080> the<00:20:22.260> with<00:20:22.500> the<00:20:22.740> uh<00:20:22.919> is 00:20:23.390 --> 00:20:23.400 align:start position:0% what we've done with the with the uh is 00:20:23.400 --> 00:20:25.730 align:start position:0% what we've done with the with the uh is basically<00:20:24.000> look<00:20:24.299> at<00:20:24.480> this<00:20:25.020> mountain<00:20:25.200> of<00:20:25.500> data 00:20:25.730 --> 00:20:25.740 align:start position:0% basically look at this mountain of data 00:20:25.740 --> 00:20:27.110 align:start position:0% basically look at this mountain of data like<00:20:25.860> you<00:20:25.980> think<00:20:26.280> of<00:20:26.400> all<00:20:26.580> the<00:20:26.820> stuff<00:20:26.940> that's 00:20:27.110 --> 00:20:27.120 align:start position:0% like you think of all the stuff that's 00:20:27.120 --> 00:20:28.549 align:start position:0% like you think of all the stuff that's going<00:20:27.299> on<00:20:27.419> all<00:20:27.600> the<00:20:27.780> different<00:20:27.900> scenarios 00:20:28.549 --> 00:20:28.559 align:start position:0% going on all the different scenarios 00:20:28.559 --> 00:20:31.070 align:start position:0% going on all the different scenarios branches<00:20:29.220> Paths<00:20:30.120> of<00:20:30.179> execution<00:20:30.660> that<00:20:30.900> have 00:20:31.070 --> 00:20:31.080 align:start position:0% branches Paths of execution that have 00:20:31.080 --> 00:20:32.930 align:start position:0% branches Paths of execution that have happened<00:20:31.200> we<00:20:31.919> can<00:20:32.039> we<00:20:32.340> have<00:20:32.460> all<00:20:32.640> these 00:20:32.930 --> 00:20:32.940 align:start position:0% happened we can we have all these 00:20:32.940 --> 00:20:35.029 align:start position:0% happened we can we have all these available<00:20:33.360> in<00:20:33.720> a<00:20:33.900> big<00:20:34.020> massive<00:20:34.320> data<00:20:34.620> set<00:20:34.679> so 00:20:35.029 --> 00:20:35.039 align:start position:0% available in a big massive data set so 00:20:35.039 --> 00:20:36.770 align:start position:0% available in a big massive data set so we<00:20:35.340> can<00:20:35.460> we<00:20:35.820> can<00:20:35.940> look<00:20:36.120> at<00:20:36.299> this<00:20:36.539> kind<00:20:36.720> of 00:20:36.770 --> 00:20:36.780 align:start position:0% we can we can look at this kind of 00:20:36.780 --> 00:20:39.710 align:start position:0% we can we can look at this kind of analysis<00:20:37.320> and<00:20:37.679> look<00:20:37.799> at<00:20:37.980> the<00:20:38.220> x-axis<00:20:38.940> which<00:20:39.600> is 00:20:39.710 --> 00:20:39.720 align:start position:0% analysis and look at the x-axis which is 00:20:39.720 --> 00:20:42.350 align:start position:0% analysis and look at the x-axis which is your<00:20:39.960> time<00:20:40.200> versus<00:20:40.799> the<00:20:41.100> probability<00:20:41.520> of<00:20:42.179> the 00:20:42.350 --> 00:20:42.360 align:start position:0% your time versus the probability of the 00:20:42.360 --> 00:20:44.810 align:start position:0% your time versus the probability of the bug<00:20:42.480> occurring<00:20:43.020> on<00:20:43.140> the<00:20:43.260> y-axis<00:20:43.740> now<00:20:44.400> the<00:20:44.640> top 00:20:44.810 --> 00:20:44.820 align:start position:0% bug occurring on the y-axis now the top 00:20:44.820 --> 00:20:47.630 align:start position:0% bug occurring on the y-axis now the top right<00:20:45.000> is<00:20:45.240> where<00:20:45.419> the<00:20:45.600> bug<00:20:45.720> is<00:20:46.320> seen 00:20:47.630 --> 00:20:47.640 align:start position:0% right is where the bug is seen 00:20:47.640 --> 00:20:49.310 align:start position:0% right is where the bug is seen we<00:20:48.120> can<00:20:48.179> then<00:20:48.299> look<00:20:48.480> at<00:20:48.600> the<00:20:48.720> common<00:20:48.840> routes 00:20:49.310 --> 00:20:49.320 align:start position:0% we can then look at the common routes 00:20:49.320 --> 00:20:50.930 align:start position:0% we can then look at the common routes that<00:20:49.559> are<00:20:49.679> happening<00:20:49.919> across<00:20:50.280> all<00:20:50.460> the<00:20:50.580> data 00:20:50.930 --> 00:20:50.940 align:start position:0% that are happening across all the data 00:20:50.940 --> 00:20:53.029 align:start position:0% that are happening across all the data and<00:20:51.360> try<00:20:51.539> and<00:20:51.660> then<00:20:51.840> bring<00:20:52.080> it<00:20:52.260> together<00:20:52.440> to 00:20:53.029 --> 00:20:53.039 align:start position:0% and try and then bring it together to 00:20:53.039 --> 00:20:55.070 align:start position:0% and try and then bring it together to see<00:20:53.220> what<00:20:53.820> is<00:20:54.000> happening<00:20:54.299> you<00:20:54.780> know<00:20:54.840> where 00:20:55.070 --> 00:20:55.080 align:start position:0% see what is happening you know where 00:20:55.080 --> 00:20:57.650 align:start position:0% see what is happening you know where where<00:20:55.440> does<00:20:55.799> the<00:20:56.280> execution<00:20:56.700> occur<00:20:57.179> where 00:20:57.650 --> 00:20:57.660 align:start position:0% where does the execution occur where 00:20:57.660 --> 00:20:59.150 align:start position:0% where does the execution occur where suddenly<00:20:58.080> the<00:20:58.320> probability<00:20:58.679> of<00:20:59.039> this 00:20:59.150 --> 00:20:59.160 align:start position:0% suddenly the probability of this 00:20:59.160 --> 00:21:01.850 align:start position:0% suddenly the probability of this actually<00:20:59.400> becoming<00:21:00.000> a<00:21:00.120> bug<00:21:00.240> yeah<00:21:01.140> happen<00:21:01.500> and 00:21:01.850 --> 00:21:01.860 align:start position:0% actually becoming a bug yeah happen and 00:21:01.860 --> 00:21:04.190 align:start position:0% actually becoming a bug yeah happen and and<00:21:02.160> lo<00:21:02.640> and<00:21:02.760> behold<00:21:03.059> we<00:21:03.480> have<00:21:03.600> a<00:21:03.780> huge<00:21:04.020> jump 00:21:04.190 --> 00:21:04.200 align:start position:0% and lo and behold we have a huge jump 00:21:04.200 --> 00:21:06.610 align:start position:0% and lo and behold we have a huge jump here<00:21:04.440> from<00:21:04.860> literally 00:21:06.610 --> 00:21:06.620 align:start position:0% here from literally 00:21:06.620 --> 00:21:09.830 align:start position:0% here from literally 0.05<00:21:07.620> of<00:21:08.340> kind<00:21:08.520> of<00:21:08.640> the<00:21:08.940> the<00:21:09.240> kind<00:21:09.539> of<00:21:09.600> bug 00:21:09.830 --> 00:21:09.840 align:start position:0% 0.05 of kind of the the kind of bug 00:21:09.840 --> 00:21:12.950 align:start position:0% 0.05 of kind of the the kind of bug occurring<00:21:10.500> to<00:21:10.740> over<00:21:11.220> 50<00:21:11.520> this<00:21:12.240> jump<00:21:12.480> here<00:21:12.720> in 00:21:12.950 --> 00:21:12.960 align:start position:0% occurring to over 50 this jump here in 00:21:12.960 --> 00:21:14.990 align:start position:0% occurring to over 50 this jump here in the<00:21:13.080> middle<00:21:13.200> we<00:21:13.980> can<00:21:14.100> start<00:21:14.280> to<00:21:14.400> go<00:21:14.580> okay<00:21:14.700> right 00:21:14.990 --> 00:21:15.000 align:start position:0% the middle we can start to go okay right 00:21:15.000 --> 00:21:17.870 align:start position:0% the middle we can start to go okay right we<00:21:15.600> know<00:21:15.960> how<00:21:16.740> many<00:21:16.860> seconds<00:21:17.039> to<00:21:17.340> go<00:21:17.460> back<00:21:17.640> now 00:21:17.870 --> 00:21:17.880 align:start position:0% we know how many seconds to go back now 00:21:17.880 --> 00:21:19.970 align:start position:0% we know how many seconds to go back now we<00:21:18.240> can<00:21:18.360> actually<00:21:18.539> Replay<00:21:19.020> that<00:21:19.500> simulation 00:21:19.970 --> 00:21:19.980 align:start position:0% we can actually Replay that simulation 00:21:19.980 --> 00:21:23.090 align:start position:0% we can actually Replay that simulation and<00:21:20.640> turn<00:21:20.880> back<00:21:21.120> time<00:21:21.419> I<00:21:22.020> won't<00:21:22.200> sing<00:21:22.380> it 00:21:23.090 --> 00:21:23.100 align:start position:0% and turn back time I won't sing it 00:21:23.100 --> 00:21:25.010 align:start position:0% and turn back time I won't sing it um<00:21:23.160> and<00:21:23.520> and<00:21:23.640> and<00:21:23.700> see<00:21:24.240> what's<00:21:24.480> going<00:21:24.720> on<00:21:24.840> there 00:21:25.010 --> 00:21:25.020 align:start position:0% um and and and see what's going on there 00:21:25.020 --> 00:21:26.510 align:start position:0% um and and and see what's going on there because<00:21:25.260> otherwise<00:21:26.039> you're<00:21:26.160> looking<00:21:26.340> for<00:21:26.460> a 00:21:26.510 --> 00:21:26.520 align:start position:0% because otherwise you're looking for a 00:21:26.520 --> 00:21:28.190 align:start position:0% because otherwise you're looking for a needle<00:21:26.760> and<00:21:26.880> a<00:21:27.000> haystack<00:21:27.240> like<00:21:27.539> how<00:21:27.720> do<00:21:27.960> you<00:21:28.080> do 00:21:28.190 --> 00:21:28.200 align:start position:0% needle and a haystack like how do you do 00:21:28.200 --> 00:21:29.810 align:start position:0% needle and a haystack like how do you do that<00:21:28.380> and<00:21:28.620> that's<00:21:28.980> really<00:21:29.220> been<00:21:29.520> really 00:21:29.810 --> 00:21:29.820 align:start position:0% that and that's really been really 00:21:29.820 --> 00:21:31.130 align:start position:0% that and that's really been really valuable 00:21:31.130 --> 00:21:31.140 align:start position:0% valuable 00:21:31.140 --> 00:21:33.169 align:start position:0% valuable um in<00:21:31.500> in<00:21:31.620> our<00:21:31.799> in<00:21:31.980> our<00:21:32.159> efforts 00:21:33.169 --> 00:21:33.179 align:start position:0% um in in our in our efforts 00:21:33.179 --> 00:21:34.909 align:start position:0% um in in our in our efforts so 00:21:34.909 --> 00:21:34.919 align:start position:0% so 00:21:34.919 --> 00:21:37.130 align:start position:0% so what's<00:21:35.460> next<00:21:35.700> well 00:21:37.130 --> 00:21:37.140 align:start position:0% what's next well 00:21:37.140 --> 00:21:39.770 align:start position:0% what's next well merger's<00:21:37.919> great<00:21:38.100> love<00:21:38.580> it<00:21:38.820> we're<00:21:39.419> doing<00:21:39.600> some 00:21:39.770 --> 00:21:39.780 align:start position:0% merger's great love it we're doing some 00:21:39.780 --> 00:21:41.510 align:start position:0% merger's great love it we're doing some Pokemon<00:21:39.960> testing<00:21:40.559> on<00:21:40.679> some<00:21:40.799> stable<00:21:41.100> branches 00:21:41.510 --> 00:21:41.520 align:start position:0% Pokemon testing on some stable branches 00:21:41.520 --> 00:21:43.250 align:start position:0% Pokemon testing on some stable branches which<00:21:41.700> isn't<00:21:41.940> you<00:21:42.179> know<00:21:42.299> we've<00:21:42.659> got<00:21:42.900> you<00:21:43.140> know 00:21:43.250 --> 00:21:43.260 align:start position:0% which isn't you know we've got you know 00:21:43.260 --> 00:21:45.049 align:start position:0% which isn't you know we've got you know things<00:21:43.380> in<00:21:43.559> a<00:21:43.679> fairly<00:21:43.919> good<00:21:44.039> order<00:21:44.220> there 00:21:45.049 --> 00:21:45.059 align:start position:0% things in a fairly good order there 00:21:45.059 --> 00:21:47.570 align:start position:0% things in a fairly good order there um but<00:21:45.840> we<00:21:46.380> know<00:21:46.440> ethereum's<00:21:47.100> not<00:21:47.220> standing 00:21:47.570 --> 00:21:47.580 align:start position:0% um but we know ethereum's not standing 00:21:47.580 --> 00:21:50.810 align:start position:0% um but we know ethereum's not standing still<00:21:47.760> we've<00:21:48.419> got<00:21:48.539> obviously<00:21:48.960> EIP<00:21:49.559> 4844<00:21:50.340> just 00:21:50.810 --> 00:21:50.820 align:start position:0% still we've got obviously EIP 4844 just 00:21:50.820 --> 00:21:52.909 align:start position:0% still we've got obviously EIP 4844 just around<00:21:50.940> the<00:21:51.179> corner<00:21:51.480> I<00:21:51.840> say<00:21:51.960> again 00:21:52.909 --> 00:21:52.919 align:start position:0% around the corner I say again 00:21:52.919 --> 00:21:54.470 align:start position:0% around the corner I say again um<00:21:52.980> thanks<00:21:53.220> sharding<00:21:53.640> withdrawals<00:21:54.179> you<00:21:54.419> know 00:21:54.470 --> 00:21:54.480 align:start position:0% um thanks sharding withdrawals you know 00:21:54.480 --> 00:21:56.630 align:start position:0% um thanks sharding withdrawals you know a<00:21:54.900> whole<00:21:55.020> host<00:21:55.200> of<00:21:55.440> new<00:21:55.679> capability<00:21:56.100> which<00:21:56.460> is 00:21:56.630 --> 00:21:56.640 align:start position:0% a whole host of new capability which is 00:21:56.640 --> 00:21:58.970 align:start position:0% a whole host of new capability which is you<00:21:57.120> know<00:21:57.179> brand<00:21:57.780> new<00:21:58.020> products<00:21:58.559> brand<00:21:58.799> new 00:21:58.970 --> 00:21:58.980 align:start position:0% you know brand new products brand new 00:21:58.980 --> 00:22:01.430 align:start position:0% you know brand new products brand new code<00:21:59.280> brand<00:22:00.179> new<00:22:00.360> testing 00:22:01.430 --> 00:22:01.440 align:start position:0% code brand new testing 00:22:01.440 --> 00:22:03.350 align:start position:0% code brand new testing um<00:22:01.559> there's<00:22:01.860> other<00:22:02.400> pieces<00:22:02.760> in<00:22:02.940> there<00:22:03.059> around 00:22:03.350 --> 00:22:03.360 align:start position:0% um there's other pieces in there around 00:22:03.360 --> 00:22:05.390 align:start position:0% um there's other pieces in there around you<00:22:03.840> know<00:22:03.960> actually<00:22:04.620> the<00:22:05.100> one<00:22:05.280> that's 00:22:05.390 --> 00:22:05.400 align:start position:0% you know actually the one that's 00:22:05.400 --> 00:22:06.409 align:start position:0% you know actually the one that's interesting<00:22:05.700> is<00:22:05.820> using<00:22:06.120> things<00:22:06.240> like 00:22:06.409 --> 00:22:06.419 align:start position:0% interesting is using things like 00:22:06.419 --> 00:22:08.210 align:start position:0% interesting is using things like malicious<00:22:06.840> clients<00:22:07.320> you<00:22:07.740> know<00:22:07.860> what<00:22:07.919> about<00:22:08.039> if 00:22:08.210 --> 00:22:08.220 align:start position:0% malicious clients you know what about if 00:22:08.220 --> 00:22:10.310 align:start position:0% malicious clients you know what about if I<00:22:08.400> brought<00:22:08.580> up<00:22:08.700> an<00:22:08.880> environment<00:22:09.240> that<00:22:09.539> has<00:22:09.780> a 00:22:10.310 --> 00:22:10.320 align:start position:0% I brought up an environment that has a 00:22:10.320 --> 00:22:12.710 align:start position:0% I brought up an environment that has a client<00:22:10.559> that<00:22:10.860> is<00:22:11.039> you<00:22:11.580> know<00:22:11.640> not<00:22:12.299> doing<00:22:12.480> what 00:22:12.710 --> 00:22:12.720 align:start position:0% client that is you know not doing what 00:22:12.720 --> 00:22:13.789 align:start position:0% client that is you know not doing what it<00:22:12.840> should<00:22:12.960> be<00:22:13.080> doing 00:22:13.789 --> 00:22:13.799 align:start position:0% it should be doing 00:22:13.799 --> 00:22:15.830 align:start position:0% it should be doing um<00:22:13.919> you<00:22:14.340> know<00:22:14.460> can<00:22:14.760> that<00:22:14.940> cause<00:22:15.179> issues<00:22:15.659> you 00:22:15.830 --> 00:22:15.840 align:start position:0% um you know can that cause issues you 00:22:15.840 --> 00:22:17.149 align:start position:0% um you know can that cause issues you know<00:22:15.960> how<00:22:16.140> does<00:22:16.260> that<00:22:16.440> kind<00:22:16.620> of<00:22:16.740> part<00:22:16.860> of<00:22:17.039> the 00:22:17.149 --> 00:22:17.159 align:start position:0% know how does that kind of part of the 00:22:17.159 --> 00:22:19.250 align:start position:0% know how does that kind of part of the of<00:22:17.340> the<00:22:17.640> code<00:22:18.120> for<00:22:18.539> the<00:22:18.659> rest<00:22:18.780> of<00:22:18.900> the<00:22:19.020> the 00:22:19.250 --> 00:22:19.260 align:start position:0% of the code for the rest of the the 00:22:19.260 --> 00:22:21.770 align:start position:0% of the code for the rest of the the network<00:22:19.620> handle<00:22:20.340> handle<00:22:20.940> that<00:22:21.059> client<00:22:21.419> and 00:22:21.770 --> 00:22:21.780 align:start position:0% network handle handle that client and 00:22:21.780 --> 00:22:23.330 align:start position:0% network handle handle that client and does<00:22:21.900> it<00:22:22.020> does<00:22:22.140> it<00:22:22.260> operate<00:22:22.620> in<00:22:23.039> a<00:22:23.159> different 00:22:23.330 --> 00:22:23.340 align:start position:0% does it does it operate in a different 00:22:23.340 --> 00:22:25.310 align:start position:0% does it does it operate in a different manner<00:22:23.760> so 00:22:25.310 --> 00:22:25.320 align:start position:0% manner so 00:22:25.320 --> 00:22:27.649 align:start position:0% manner so other<00:22:25.919> pieces<00:22:26.280> here<00:22:26.520> you<00:22:27.240> merge<00:22:27.480> clothes 00:22:27.649 --> 00:22:27.659 align:start position:0% other pieces here you merge clothes 00:22:27.659 --> 00:22:30.049 align:start position:0% other pieces here you merge clothes clean<00:22:27.960> up<00:22:28.080> you<00:22:28.260> know<00:22:28.380> there's<00:22:28.500> changes<00:22:29.159> to<00:22:29.520> you 00:22:30.049 --> 00:22:30.059 align:start position:0% clean up you know there's changes to you 00:22:30.059 --> 00:22:31.549 align:start position:0% clean up you know there's changes to you know<00:22:30.120> kind<00:22:30.299> of<00:22:30.419> established<00:22:30.900> pieces<00:22:31.320> of<00:22:31.440> code 00:22:31.549 --> 00:22:31.559 align:start position:0% know kind of established pieces of code 00:22:31.559 --> 00:22:33.590 align:start position:0% know kind of established pieces of code that<00:22:31.799> are<00:22:31.980> in<00:22:32.280> in<00:22:32.520> place<00:22:32.760> now 00:22:33.590 --> 00:22:33.600 align:start position:0% that are in in place now 00:22:33.600 --> 00:22:35.810 align:start position:0% that are in in place now all<00:22:34.020> those<00:22:34.200> changes<00:22:34.620> introduce<00:22:35.280> you<00:22:35.700> know 00:22:35.810 --> 00:22:35.820 align:start position:0% all those changes introduce you know 00:22:35.820 --> 00:22:39.289 align:start position:0% all those changes introduce you know probably<00:22:36.419> good<00:22:36.900> and<00:22:37.320> it<00:22:37.559> could<00:22:37.740> appear<00:22:38.460> uh<00:22:39.179> you 00:22:39.289 --> 00:22:39.299 align:start position:0% probably good and it could appear uh you 00:22:39.299 --> 00:22:41.870 align:start position:0% probably good and it could appear uh you know<00:22:39.419> Downstream<00:22:39.960> so<00:22:40.260> pretty<00:22:41.039> cool 00:22:41.870 --> 00:22:41.880 align:start position:0% know Downstream so pretty cool 00:22:41.880 --> 00:22:44.630 align:start position:0% know Downstream so pretty cool um<00:22:42.000> we're<00:22:42.960> working<00:22:43.559> actively<00:22:44.159> with<00:22:44.460> the 00:22:44.630 --> 00:22:44.640 align:start position:0% um we're working actively with the 00:22:44.640 --> 00:22:46.370 align:start position:0% um we're working actively with the clients 00:22:46.370 --> 00:22:46.380 align:start position:0% clients 00:22:46.380 --> 00:22:48.590 align:start position:0% clients um<00:22:46.440> and<00:22:46.799> open<00:22:47.100> to<00:22:47.460> really<00:22:47.940> you<00:22:48.179> know<00:22:48.299> kind<00:22:48.539> of 00:22:48.590 --> 00:22:48.600 align:start position:0% um and open to really you know kind of 00:22:48.600 --> 00:22:50.529 align:start position:0% um and open to really you know kind of broadening<00:22:49.260> that<00:22:49.440> relationship<00:22:49.799> further<00:22:50.280> so 00:22:50.529 --> 00:22:50.539 align:start position:0% broadening that relationship further so 00:22:50.539 --> 00:22:54.710 align:start position:0% broadening that relationship further so that's<00:22:51.539> the<00:22:51.960> end<00:22:52.140> of<00:22:52.320> that<00:22:52.559> q<00:22:53.460> a 00:22:54.710 --> 00:22:54.720 align:start position:0% that's the end of that q a 00:22:54.720 --> 00:22:57.649 align:start position:0% that's the end of that q a um<00:22:54.840> any<00:22:55.140> questions<00:22:55.460> yeah<00:22:56.880> um<00:22:56.880> you<00:22:57.120> showed<00:22:57.539> us 00:22:57.649 --> 00:22:57.659 align:start position:0% um any questions yeah um you showed us 00:22:57.659 --> 00:23:00.049 align:start position:0% um any questions yeah um you showed us uh<00:22:58.380> a<00:22:58.559> slide<00:22:58.860> with<00:22:58.980> the<00:22:59.100> probability<00:22:59.460> of 00:23:00.049 --> 00:23:00.059 align:start position:0% uh a slide with the probability of 00:23:00.059 --> 00:23:02.450 align:start position:0% uh a slide with the probability of finding<00:23:00.600> a<00:23:00.840> bug<00:23:01.020> how<00:23:01.559> did<00:23:01.679> you<00:23:01.860> calculate<00:23:02.220> that 00:23:02.450 --> 00:23:02.460 align:start position:0% finding a bug how did you calculate that 00:23:02.460 --> 00:23:04.909 align:start position:0% finding a bug how did you calculate that probability<00:23:02.940> which<00:23:03.659> model<00:23:03.840> you<00:23:04.320> were<00:23:04.440> using 00:23:04.909 --> 00:23:04.919 align:start position:0% probability which model you were using 00:23:04.919 --> 00:23:07.610 align:start position:0% probability which model you were using or<00:23:05.760> how<00:23:06.179> complex<00:23:06.539> is<00:23:06.780> you<00:23:07.140> know<00:23:07.200> the 00:23:07.610 --> 00:23:07.620 align:start position:0% or how complex is you know the 00:23:07.620 --> 00:23:09.649 align:start position:0% or how complex is you know the calculations<00:23:08.159> and<00:23:08.580> that<00:23:08.760> stuff<00:23:09.000> that's<00:23:09.539> a 00:23:09.649 --> 00:23:09.659 align:start position:0% calculations and that stuff that's a 00:23:09.659 --> 00:23:11.810 align:start position:0% calculations and that stuff that's a good<00:23:09.780> question<00:23:10.020> so<00:23:10.380> the<00:23:10.860> just<00:23:11.400> because<00:23:11.580> the 00:23:11.810 --> 00:23:11.820 align:start position:0% good question so the just because the 00:23:11.820 --> 00:23:14.149 align:start position:0% good question so the just because the amounts<00:23:12.179> of<00:23:12.299> data<00:23:12.659> we've<00:23:12.900> got<00:23:13.080> available<00:23:13.740> we 00:23:14.149 --> 00:23:14.159 align:start position:0% amounts of data we've got available we 00:23:14.159 --> 00:23:16.430 align:start position:0% amounts of data we've got available we we<00:23:14.220> know<00:23:14.580> every<00:23:15.000> kind<00:23:15.360> of<00:23:15.480> path<00:23:15.900> execution 00:23:16.430 --> 00:23:16.440 align:start position:0% we know every kind of path execution 00:23:16.440 --> 00:23:18.710 align:start position:0% we know every kind of path execution that's<00:23:16.679> occurring<00:23:17.159> that<00:23:17.940> the<00:23:18.240> outcome 00:23:18.710 --> 00:23:18.720 align:start position:0% that's occurring that the outcome 00:23:18.720 --> 00:23:20.870 align:start position:0% that's occurring that the outcome doesn't<00:23:19.140> occur<00:23:19.500> with<00:23:19.679> a<00:23:19.919> bug<00:23:20.039> and<00:23:20.580> we<00:23:20.760> have 00:23:20.870 --> 00:23:20.880 align:start position:0% doesn't occur with a bug and we have 00:23:20.880 --> 00:23:21.890 align:start position:0% doesn't occur with a bug and we have then<00:23:21.059> obviously<00:23:21.419> all<00:23:21.600> the<00:23:21.720> different 00:23:21.890 --> 00:23:21.900 align:start position:0% then obviously all the different 00:23:21.900 --> 00:23:24.230 align:start position:0% then obviously all the different outcomes<00:23:22.440> that<00:23:22.679> do<00:23:23.340> translate<00:23:23.700> to<00:23:24.000> the<00:23:24.120> bug 00:23:24.230 --> 00:23:24.240 align:start position:0% outcomes that do translate to the bug 00:23:24.240 --> 00:23:25.310 align:start position:0% outcomes that do translate to the bug happening 00:23:25.310 --> 00:23:25.320 align:start position:0% happening 00:23:25.320 --> 00:23:26.570 align:start position:0% happening um<00:23:25.380> and<00:23:25.679> so 00:23:26.570 --> 00:23:26.580 align:start position:0% um and so 00:23:26.580 --> 00:23:29.210 align:start position:0% um and so where<00:23:27.299> the<00:23:27.539> ability<00:23:27.840> to<00:23:28.320> you<00:23:28.679> know<00:23:28.860> do<00:23:29.100> some 00:23:29.210 --> 00:23:29.220 align:start position:0% where the ability to you know do some 00:23:29.220 --> 00:23:31.130 align:start position:0% where the ability to you know do some simple<00:23:29.640> calculation<00:23:30.120> we<00:23:30.419> can<00:23:30.539> see<00:23:30.720> that<00:23:30.960> you 00:23:31.130 --> 00:23:31.140 align:start position:0% simple calculation we can see that you 00:23:31.140 --> 00:23:33.230 align:start position:0% simple calculation we can see that you know<00:23:31.260> the<00:23:31.440> path<00:23:31.679> the<00:23:32.280> path<00:23:32.460> that's<00:23:32.760> sort<00:23:33.179> of 00:23:33.230 --> 00:23:33.240 align:start position:0% know the path the path that's sort of 00:23:33.240 --> 00:23:35.270 align:start position:0% know the path the path that's sort of trodden<00:23:33.780> and<00:23:33.960> worn<00:23:34.320> and<00:23:34.740> you<00:23:34.860> know<00:23:34.980> this<00:23:35.159> but 00:23:35.270 --> 00:23:35.280 align:start position:0% trodden and worn and you know this but 00:23:35.280 --> 00:23:37.070 align:start position:0% trodden and worn and you know this but this<00:23:35.460> if<00:23:35.640> this<00:23:35.820> is<00:23:35.880> if<00:23:36.120> we<00:23:36.299> see<00:23:36.480> this<00:23:36.720> happening 00:23:37.070 --> 00:23:37.080 align:start position:0% this if this is if we see this happening 00:23:37.080 --> 00:23:40.070 align:start position:0% this if this is if we see this happening then<00:23:37.860> we<00:23:38.400> can<00:23:38.520> calculate<00:23:39.000> the<00:23:39.120> bug<00:23:39.360> occurring 00:23:40.070 --> 00:23:40.080 align:start position:0% then we can calculate the bug occurring 00:23:40.080 --> 00:23:42.230 align:start position:0% then we can calculate the bug occurring there<00:23:40.260> are<00:23:40.380> obviously<00:23:40.860> other<00:23:41.159> branches<00:23:41.760> down 00:23:42.230 --> 00:23:42.240 align:start position:0% there are obviously other branches down 00:23:42.240 --> 00:23:45.289 align:start position:0% there are obviously other branches down that<00:23:42.539> that<00:23:42.960> well-trodden<00:23:43.679> path<00:23:43.980> where<00:23:44.700> my 00:23:45.289 --> 00:23:45.299 align:start position:0% that that well-trodden path where my 00:23:45.299 --> 00:23:46.909 align:start position:0% that that well-trodden path where my virgin's<00:23:45.720> gonna<00:23:45.780> go<00:23:45.900> somewhere<00:23:46.140> else<00:23:46.260> and<00:23:46.799> the 00:23:46.909 --> 00:23:46.919 align:start position:0% virgin's gonna go somewhere else and the 00:23:46.919 --> 00:23:48.710 align:start position:0% virgin's gonna go somewhere else and the bug<00:23:47.220> doesn't<00:23:47.400> manifest<00:23:47.940> so<00:23:48.120> we<00:23:48.299> that's<00:23:48.539> that's 00:23:48.710 --> 00:23:48.720 align:start position:0% bug doesn't manifest so we that's that's 00:23:48.720 --> 00:23:50.690 align:start position:0% bug doesn't manifest so we that's that's how<00:23:48.960> we<00:23:49.140> at<00:23:49.320> every<00:23:49.559> point<00:23:49.860> in<00:23:50.159> that<00:23:50.220> graph<00:23:50.460> we 00:23:50.690 --> 00:23:50.700 align:start position:0% how we at every point in that graph we 00:23:50.700 --> 00:23:52.789 align:start position:0% how we at every point in that graph we can<00:23:50.820> we<00:23:51.000> can<00:23:51.179> calculate<00:23:51.720> if<00:23:52.080> you<00:23:52.320> know<00:23:52.380> if<00:23:52.620> it 00:23:52.789 --> 00:23:52.799 align:start position:0% can we can calculate if you know if it 00:23:52.799 --> 00:23:54.409 align:start position:0% can we can calculate if you know if it does<00:23:52.860> contribute<00:23:53.340> or<00:23:53.580> not<00:23:53.760> contribute<00:23:54.120> to<00:23:54.240> the 00:23:54.409 --> 00:23:54.419 align:start position:0% does contribute or not contribute to the 00:23:54.419 --> 00:23:57.230 align:start position:0% does contribute or not contribute to the bug<00:23:54.539> how<00:23:55.380> do<00:23:55.559> you<00:23:55.740> kind<00:23:56.159> of<00:23:56.280> isolate<00:23:56.820> unique 00:23:57.230 --> 00:23:57.240 align:start position:0% bug how do you kind of isolate unique 00:23:57.240 --> 00:24:00.230 align:start position:0% bug how do you kind of isolate unique bugs<00:23:57.600> so<00:23:57.840> you<00:23:58.140> know<00:23:58.260> it's<00:23:58.380> like<00:23:58.559> the<00:23:58.860> same<00:23:59.039> bug 00:24:00.230 --> 00:24:00.240 align:start position:0% bugs so you know it's like the same bug 00:24:00.240 --> 00:24:02.810 align:start position:0% bugs so you know it's like the same bug that's<00:24:00.539> a<00:24:00.720> good<00:24:00.780> question<00:24:01.020> and<00:24:01.380> so<00:24:01.559> we<00:24:01.919> we<00:24:02.580> see 00:24:02.810 --> 00:24:02.820 align:start position:0% that's a good question and so we we see 00:24:02.820 --> 00:24:05.029 align:start position:0% that's a good question and so we we see a<00:24:02.940> huge<00:24:03.240> amount<00:24:03.480> of<00:24:03.659> bugs<00:24:04.080> that<00:24:04.260> do<00:24:04.559> manifest 00:24:05.029 --> 00:24:05.039 align:start position:0% a huge amount of bugs that do manifest 00:24:05.039 --> 00:24:07.190 align:start position:0% a huge amount of bugs that do manifest and<00:24:05.280> show<00:24:05.520> us<00:24:05.760> like<00:24:06.179> you<00:24:06.659> know<00:24:06.780> duplication 00:24:07.190 --> 00:24:07.200 align:start position:0% and show us like you know duplication 00:24:07.200 --> 00:24:08.930 align:start position:0% and show us like you know duplication like<00:24:07.440> you<00:24:07.679> know<00:24:07.799> like<00:24:08.039> the<00:24:08.159> one<00:24:08.280> you<00:24:08.460> saw<00:24:08.700> with 00:24:08.930 --> 00:24:08.940 align:start position:0% like you know like the one you saw with 00:24:08.940 --> 00:24:11.270 align:start position:0% like you know like the one you saw with nimbuson<00:24:09.600> and<00:24:10.020> Geth 00:24:11.270 --> 00:24:11.280 align:start position:0% nimbuson and Geth 00:24:11.280 --> 00:24:13.190 align:start position:0% nimbuson and Geth that<00:24:11.760> we<00:24:12.000> can<00:24:12.120> we<00:24:12.299> can<00:24:12.419> run<00:24:12.480> that<00:24:12.659> literary<00:24:13.020> day 00:24:13.190 --> 00:24:13.200 align:start position:0% that we can we can run that literary day 00:24:13.200 --> 00:24:14.810 align:start position:0% that we can we can run that literary day in<00:24:13.380> there<00:24:13.559> and<00:24:13.799> then<00:24:13.919> it<00:24:14.340> will<00:24:14.460> you<00:24:14.580> know<00:24:14.700> with 00:24:14.810 --> 00:24:14.820 align:start position:0% in there and then it will you know with 00:24:14.820 --> 00:24:16.669 align:start position:0% in there and then it will you know with the<00:24:15.000> right<00:24:15.120> commit<00:24:15.600> code<00:24:15.780> which<00:24:16.080> is<00:24:16.200> in 00:24:16.669 --> 00:24:16.679 align:start position:0% the right commit code which is in 00:24:16.679 --> 00:24:18.169 align:start position:0% the right commit code which is in history<00:24:16.860> but<00:24:17.280> we<00:24:17.400> would<00:24:17.580> we<00:24:17.820> would<00:24:17.880> be<00:24:18.000> able<00:24:18.120> to 00:24:18.169 --> 00:24:18.179 align:start position:0% history but we would we would be able to 00:24:18.179 --> 00:24:20.270 align:start position:0% history but we would we would be able to see<00:24:18.419> that<00:24:18.600> and<00:24:18.780> we'd<00:24:19.020> see<00:24:19.140> we<00:24:19.380> we<00:24:19.559> have<00:24:19.740> counts 00:24:20.270 --> 00:24:20.280 align:start position:0% see that and we'd see we we have counts 00:24:20.280 --> 00:24:22.370 align:start position:0% see that and we'd see we we have counts on<00:24:20.640> that<00:24:21.000> occurrence<00:24:21.480> so<00:24:21.659> we<00:24:21.780> can<00:24:21.900> see<00:24:22.080> very 00:24:22.370 --> 00:24:22.380 align:start position:0% on that occurrence so we can see very 00:24:22.380 --> 00:24:24.950 align:start position:0% on that occurrence so we can see very quickly<00:24:22.679> this<00:24:23.640> isn't<00:24:23.880> just<00:24:24.059> like<00:24:24.419> an<00:24:24.720> edge 00:24:24.950 --> 00:24:24.960 align:start position:0% quickly this isn't just like an edge 00:24:24.960 --> 00:24:28.010 align:start position:0% quickly this isn't just like an edge case<00:24:25.200> that's<00:24:25.559> just<00:24:25.799> happened<00:24:25.980> on<00:24:26.400> one<00:24:26.960> sort<00:24:27.960> of 00:24:28.010 --> 00:24:28.020 align:start position:0% case that's just happened on one sort of 00:24:28.020 --> 00:24:31.130 align:start position:0% case that's just happened on one sort of combined<00:24:28.559> client<00:24:29.340> set<00:24:29.580> it's<00:24:30.179> it's<00:24:30.419> like<00:24:30.780> it's 00:24:31.130 --> 00:24:31.140 align:start position:0% combined client set it's it's like it's 00:24:31.140 --> 00:24:33.470 align:start position:0% combined client set it's it's like it's a<00:24:31.500> problem<00:24:31.679> across<00:24:32.100> the<00:24:32.159> board<00:24:32.280> and<00:24:32.520> so 00:24:33.470 --> 00:24:33.480 align:start position:0% a problem across the board and so 00:24:33.480 --> 00:24:35.330 align:start position:0% a problem across the board and so um<00:24:33.539> we<00:24:33.960> have<00:24:34.080> all<00:24:34.260> of<00:24:34.380> that<00:24:34.559> wrapped<00:24:34.980> up<00:24:35.100> into 00:24:35.330 --> 00:24:35.340 align:start position:0% um we have all of that wrapped up into 00:24:35.340 --> 00:24:37.789 align:start position:0% um we have all of that wrapped up into our<00:24:35.640> reporting<00:24:36.360> you<00:24:37.140> know<00:24:37.260> what<00:24:37.500> do<00:24:37.620> you<00:24:37.740> think 00:24:37.789 --> 00:24:37.799 align:start position:0% our reporting you know what do you think 00:24:37.799 --> 00:24:40.610 align:start position:0% our reporting you know what do you think about<00:24:37.980> applying<00:24:38.640> formal<00:24:39.000> verification<00:24:39.620> in 00:24:40.610 --> 00:24:40.620 align:start position:0% about applying formal verification in 00:24:40.620 --> 00:24:43.130 align:start position:0% about applying formal verification in this<00:24:41.100> huge<00:24:41.400> environment<00:24:41.760> is<00:24:42.299> it 00:24:43.130 --> 00:24:43.140 align:start position:0% this huge environment is it 00:24:43.140 --> 00:24:45.529 align:start position:0% this huge environment is it um<00:24:43.520> do<00:24:44.520> you<00:24:44.640> think 00:24:45.529 --> 00:24:45.539 align:start position:0% um do you think 00:24:45.539 --> 00:24:48.110 align:start position:0% um do you think um<00:24:45.679> possibility<00:24:46.679> or 00:24:48.110 --> 00:24:48.120 align:start position:0% um possibility or 00:24:48.120 --> 00:24:49.610 align:start position:0% um possibility or I'm<00:24:48.539> usually<00:24:48.840> not<00:24:49.020> the<00:24:49.140> best<00:24:49.260> person<00:24:49.380> to 00:24:49.610 --> 00:24:49.620 align:start position:0% I'm usually not the best person to 00:24:49.620 --> 00:24:52.130 align:start position:0% I'm usually not the best person to answer<00:24:49.740> that<00:24:50.039> question<00:24:50.539> but<00:24:51.539> bring<00:24:51.840> it<00:24:51.960> bring 00:24:52.130 --> 00:24:52.140 align:start position:0% answer that question but bring it bring 00:24:52.140 --> 00:24:53.210 align:start position:0% answer that question but bring it bring it<00:24:52.260> to<00:24:52.380> us<00:24:52.440> at<00:24:52.559> the<00:24:52.679> end<00:24:52.740> because<00:24:52.860> I've<00:24:53.039> got 00:24:53.210 --> 00:24:53.220 align:start position:0% it to us at the end because I've got 00:24:53.220 --> 00:24:54.289 align:start position:0% it to us at the end because I've got some<00:24:53.400> people<00:24:53.520> that<00:24:53.700> can<00:24:53.820> answer<00:24:53.940> us<00:24:54.179> that 00:24:54.289 --> 00:24:54.299 align:start position:0% some people that can answer us that 00:24:54.299 --> 00:24:55.370 align:start position:0% some people that can answer us that question<00:24:54.419> for<00:24:54.659> you 00:24:55.370 --> 00:24:55.380 align:start position:0% question for you 00:24:55.380 --> 00:24:57.409 align:start position:0% question for you okay 00:24:57.409 --> 00:24:57.419 align:start position:0% okay 00:24:57.419 --> 00:25:00.110 align:start position:0% okay well<00:24:58.380> please<00:24:58.679> great<00:24:59.100> chance<00:24:59.340> of<00:24:59.520> us<00:24:59.640> keep<00:24:59.820> keep 00:25:00.110 --> 00:25:00.120 align:start position:0% well please great chance of us keep keep 00:25:00.120 --> 00:25:02.149 align:start position:0% well please great chance of us keep keep you<00:25:00.480> know<00:25:00.539> keep<00:25:00.900> the<00:25:01.020> conversation<00:25:01.320> going<00:25:01.559> and 00:25:02.149 --> 00:25:02.159 align:start position:0% you know keep the conversation going and 00:25:02.159 --> 00:25:05.419 align:start position:0% you know keep the conversation going and uh<00:25:02.400> I<00:25:02.760> hope<00:25:02.820> you<00:25:02.940> enjoyed<00:25:03.179> the<00:25:03.299> talk