WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:15.490 align:start position:0% [Music] 00:00:15.490 --> 00:00:15.500 align:start position:0% 00:00:15.500 --> 00:00:19.130 align:start position:0% like<00:00:16.500> what<00:00:17.279> happened<00:00:17.580> before<00:00:18.060> as<00:00:18.539> this<00:00:18.779> one<00:00:18.960> is 00:00:19.130 --> 00:00:19.140 align:start position:0% like what happened before as this one is 00:00:19.140 --> 00:00:21.529 align:start position:0% like what happened before as this one is basically<00:00:19.440> just<00:00:19.740> like<00:00:19.980> a<00:00:20.699> continuing<00:00:21.180> session 00:00:21.529 --> 00:00:21.539 align:start position:0% basically just like a continuing session 00:00:21.539 --> 00:00:24.050 align:start position:0% basically just like a continuing session to<00:00:21.840> what<00:00:22.080> happened<00:00:22.260> in<00:00:22.500> Osaka<00:00:23.100> where<00:00:23.460> we 00:00:24.050 --> 00:00:24.060 align:start position:0% to what happened in Osaka where we 00:00:24.060 --> 00:00:25.730 align:start position:0% to what happened in Osaka where we thought<00:00:24.240> that<00:00:24.420> we<00:00:24.600> will<00:00:24.779> almost<00:00:25.019> die<00:00:25.380> after 00:00:25.730 --> 00:00:25.740 align:start position:0% thought that we will almost die after 00:00:25.740 --> 00:00:27.410 align:start position:0% thought that we will almost die after typhoon 00:00:27.410 --> 00:00:27.420 align:start position:0% typhoon 00:00:27.420 --> 00:00:29.570 align:start position:0% typhoon um so<00:00:28.080> basically<00:00:28.439> that<00:00:28.680> was<00:00:28.920> like<00:00:29.099> proof<00:00:29.460> of 00:00:29.570 --> 00:00:29.580 align:start position:0% um so basically that was like proof of 00:00:29.580 --> 00:00:31.250 align:start position:0% um so basically that was like proof of work<00:00:29.760> to<00:00:30.000> prove<00:00:30.300> of<00:00:30.420> stakes<00:00:30.720> or<00:00:31.019> like 00:00:31.250 --> 00:00:31.260 align:start position:0% work to prove of stakes or like 00:00:31.260 --> 00:00:33.770 align:start position:0% work to prove of stakes or like transition<00:00:31.740> session<00:00:32.220> uh<00:00:33.120> where<00:00:33.300> we<00:00:33.480> hosted 00:00:33.770 --> 00:00:33.780 align:start position:0% transition session uh where we hosted 00:00:33.780 --> 00:00:36.410 align:start position:0% transition session uh where we hosted like<00:00:34.020> some<00:00:34.380> Community<00:00:34.620> sessions<00:00:35.219> as<00:00:35.460> well<00:00:35.579> uh 00:00:36.410 --> 00:00:36.420 align:start position:0% like some Community sessions as well uh 00:00:36.420 --> 00:00:39.110 align:start position:0% like some Community sessions as well uh alongside<00:00:36.899> the<00:00:37.200> Eid<00:00:37.440> one<00:00:37.620> in<00:00:38.040> each<00:00:38.340> One<00:00:38.640> X<00:00:38.880> to 00:00:39.110 --> 00:00:39.120 align:start position:0% alongside the Eid one in each One X to 00:00:39.120 --> 00:00:41.630 align:start position:0% alongside the Eid one in each One X to E2<00:00:39.540> and<00:00:40.079> these<00:00:40.320> two<00:00:40.440> sessions 00:00:41.630 --> 00:00:41.640 align:start position:0% E2 and these two sessions 00:00:41.640 --> 00:00:44.090 align:start position:0% E2 and these two sessions um<00:00:41.760> it<00:00:41.940> was<00:00:42.180> kind<00:00:42.480> of<00:00:42.600> successful<00:00:43.260> in<00:00:43.680> a<00:00:43.860> huge 00:00:44.090 --> 00:00:44.100 align:start position:0% um it was kind of successful in a huge 00:00:44.100 --> 00:00:47.869 align:start position:0% um it was kind of successful in a huge room<00:00:44.280> where<00:00:44.760> vitalik<00:00:45.719> went<00:00:45.960> on<00:00:46.379> like<00:00:46.559> a<00:00:46.980> huge 00:00:47.869 --> 00:00:47.879 align:start position:0% room where vitalik went on like a huge 00:00:47.879 --> 00:00:49.610 align:start position:0% room where vitalik went on like a huge session<00:00:48.239> and<00:00:48.539> brought<00:00:48.780> like<00:00:49.079> so<00:00:49.500> many 00:00:49.610 --> 00:00:49.620 align:start position:0% session and brought like so many 00:00:49.620 --> 00:00:53.270 align:start position:0% session and brought like so many research<00:00:50.340> posts<00:00:50.820> of<00:00:51.239> like<00:00:51.600> that<00:00:52.379> inspired<00:00:53.100> the 00:00:53.270 --> 00:00:53.280 align:start position:0% research posts of like that inspired the 00:00:53.280 --> 00:00:55.549 align:start position:0% research posts of like that inspired the discussions<00:00:53.640> that<00:00:53.940> happen<00:00:54.180> uh<00:00:55.079> during<00:00:55.320> the 00:00:55.549 --> 00:00:55.559 align:start position:0% discussions that happen uh during the 00:00:55.559 --> 00:00:56.990 align:start position:0% discussions that happen uh during the session 00:00:56.990 --> 00:00:57.000 align:start position:0% session 00:00:57.000 --> 00:00:58.430 align:start position:0% session um<00:00:57.059> and<00:00:57.539> then 00:00:58.430 --> 00:00:58.440 align:start position:0% um and then 00:00:58.440 --> 00:01:00.650 align:start position:0% um and then um<00:00:58.559> just<00:00:58.800> to<00:00:58.980> give<00:00:59.100> you<00:00:59.219> a<00:00:59.340> quick<00:00:59.520> overview<00:01:00.000> of 00:01:00.650 --> 00:01:00.660 align:start position:0% um just to give you a quick overview of 00:01:00.660 --> 00:01:02.090 align:start position:0% um just to give you a quick overview of the 00:01:02.090 --> 00:01:02.100 align:start position:0% the 00:01:02.100 --> 00:01:03.950 align:start position:0% the um<00:01:02.160> the<00:01:02.579> roadmap<00:01:02.940> of<00:01:03.300> what<00:01:03.539> we've<00:01:03.780> been 00:01:03.950 --> 00:01:03.960 align:start position:0% um the roadmap of what we've been 00:01:03.960 --> 00:01:07.910 align:start position:0% um the roadmap of what we've been discussing<00:01:04.440> uh<00:01:05.220> like<00:01:05.880> just<00:01:06.720> a<00:01:06.840> few<00:01:07.020> points<00:01:07.439> uh 00:01:07.910 --> 00:01:07.920 align:start position:0% discussing uh like just a few points uh 00:01:07.920 --> 00:01:10.429 align:start position:0% discussing uh like just a few points uh mainly<00:01:08.280> we've<00:01:08.640> been<00:01:08.700> discussing<00:01:09.119> the<00:01:09.299> IP<00:01:09.600> 1559 00:01:10.429 --> 00:01:10.439 align:start position:0% mainly we've been discussing the IP 1559 00:01:10.439 --> 00:01:14.030 align:start position:0% mainly we've been discussing the IP 1559 the<00:01:10.680> fee<00:01:11.040> Market<00:01:11.159> change<00:01:11.939> for<00:01:12.600> ethereum<00:01:13.200> uh 00:01:14.030 --> 00:01:14.040 align:start position:0% the fee Market change for ethereum uh 00:01:14.040 --> 00:01:17.570 align:start position:0% the fee Market change for ethereum uh which<00:01:14.340> was<00:01:14.640> a<00:01:15.119> very<00:01:15.720> hot<00:01:16.320> discussion<00:01:16.920> and<00:01:17.400> also 00:01:17.570 --> 00:01:17.580 align:start position:0% which was a very hot discussion and also 00:01:17.580 --> 00:01:21.289 align:start position:0% which was a very hot discussion and also the<00:01:17.820> prak<00:01:18.180> Pao<00:01:18.479> which<00:01:18.840> we<00:01:19.080> agreed<00:01:19.500> uh<00:01:19.860> uh<00:01:20.820> that 00:01:21.289 --> 00:01:21.299 align:start position:0% the prak Pao which we agreed uh uh that 00:01:21.299 --> 00:01:23.570 align:start position:0% the prak Pao which we agreed uh uh that sort<00:01:21.479> of<00:01:21.659> conspiracy<00:01:22.320> driven<00:01:22.619> AIP<00:01:23.040> and<00:01:23.340> we 00:01:23.570 --> 00:01:23.580 align:start position:0% sort of conspiracy driven AIP and we 00:01:23.580 --> 00:01:25.730 align:start position:0% sort of conspiracy driven AIP and we should<00:01:23.759> not<00:01:23.939> keep<00:01:24.180> much<00:01:24.540> of<00:01:24.659> a<00:01:24.840> like<00:01:25.140> we<00:01:25.439> should 00:01:25.730 --> 00:01:25.740 align:start position:0% should not keep much of a like we should 00:01:25.740 --> 00:01:28.850 align:start position:0% should not keep much of a like we should not<00:01:25.920> like<00:01:26.360> pay<00:01:27.360> much<00:01:27.659> of<00:01:27.900> attention<00:01:28.320> to<00:01:28.680> that 00:01:28.850 --> 00:01:28.860 align:start position:0% not like pay much of attention to that 00:01:28.860 --> 00:01:31.670 align:start position:0% not like pay much of attention to that as<00:01:29.100> that's<00:01:29.400> very<00:01:29.759> conspiracy<00:01:30.479> agreement 00:01:31.670 --> 00:01:31.680 align:start position:0% as that's very conspiracy agreement 00:01:31.680 --> 00:01:33.469 align:start position:0% as that's very conspiracy agreement um<00:01:31.799> then<00:01:32.040> we<00:01:32.280> also<00:01:32.520> started<00:01:32.880> discussing<00:01:33.299> about 00:01:33.469 --> 00:01:33.479 align:start position:0% um then we also started discussing about 00:01:33.479 --> 00:01:34.609 align:start position:0% um then we also started discussing about State<00:01:33.720> rent 00:01:34.609 --> 00:01:34.619 align:start position:0% State rent 00:01:34.619 --> 00:01:35.770 align:start position:0% State rent um<00:01:34.680> as 00:01:35.770 --> 00:01:35.780 align:start position:0% um as 00:01:35.780 --> 00:01:38.270 align:start position:0% um as we<00:01:36.780> realized<00:01:37.079> that<00:01:37.380> many<00:01:37.560> people<00:01:37.740> are<00:01:37.979> using 00:01:38.270 --> 00:01:38.280 align:start position:0% we realized that many people are using 00:01:38.280 --> 00:01:40.850 align:start position:0% we realized that many people are using blockchain<00:01:38.759> as<00:01:39.180> a<00:01:39.479> storage 00:01:40.850 --> 00:01:40.860 align:start position:0% blockchain as a storage 00:01:40.860 --> 00:01:42.890 align:start position:0% blockchain as a storage um<00:01:40.920> so<00:01:41.100> we<00:01:41.340> were<00:01:41.520> discussing<00:01:42.119> that<00:01:42.720> there 00:01:42.890 --> 00:01:42.900 align:start position:0% um so we were discussing that there 00:01:42.900 --> 00:01:45.770 align:start position:0% um so we were discussing that there should<00:01:43.140> be<00:01:43.259> uh<00:01:43.680> rent<00:01:44.040> free<00:01:44.340> that<00:01:45.299> there<00:01:45.600> should 00:01:45.770 --> 00:01:45.780 align:start position:0% should be uh rent free that there should 00:01:45.780 --> 00:01:50.510 align:start position:0% should be uh rent free that there should be<00:01:45.900> some<00:01:46.140> rent<00:01:46.500> fee<00:01:47.100> for<00:01:47.400> the<00:01:48.180> providers<00:01:49.520> it 00:01:50.510 --> 00:01:50.520 align:start position:0% be some rent fee for the providers it 00:01:50.520 --> 00:01:53.210 align:start position:0% be some rent fee for the providers it also<00:01:50.939> kick<00:01:51.479> off<00:01:51.659> the<00:01:52.140> ideas<00:01:52.320> for<00:01:52.740> stateless 00:01:53.210 --> 00:01:53.220 align:start position:0% also kick off the ideas for stateless 00:01:53.220 --> 00:01:56.810 align:start position:0% also kick off the ideas for stateless Clan<00:01:53.720> with<00:01:54.720> Alex<00:01:54.960> and<00:01:55.200> Piper<00:01:55.680> I'm<00:01:56.159> not<00:01:56.340> sure<00:01:56.579> if 00:01:56.810 --> 00:01:56.820 align:start position:0% Clan with Alex and Piper I'm not sure if 00:01:56.820 --> 00:01:59.510 align:start position:0% Clan with Alex and Piper I'm not sure if they<00:01:57.000> are<00:01:57.180> there<00:01:57.360> but<00:01:58.020> um<00:01:58.020> they<00:01:58.320> started 00:01:59.510 --> 00:01:59.520 align:start position:0% they are there but um they started 00:01:59.520 --> 00:02:01.429 align:start position:0% they are there but um they started um<00:01:59.579> pretty<00:01:59.759> much<00:02:00.000> discussing<00:02:00.659> how<00:02:01.079> we<00:02:01.320> make 00:02:01.429 --> 00:02:01.439 align:start position:0% um pretty much discussing how we make 00:02:01.439 --> 00:02:03.710 align:start position:0% um pretty much discussing how we make ethereum<00:02:01.979> stateless<00:02:02.340> and<00:02:03.119> then<00:02:03.240> they<00:02:03.540> follow 00:02:03.710 --> 00:02:03.720 align:start position:0% ethereum stateless and then they follow 00:02:03.720 --> 00:02:06.830 align:start position:0% ethereum stateless and then they follow up<00:02:03.960> the<00:02:04.259> session<00:02:04.560> in<00:02:05.100> Paris<00:02:05.460> after<00:02:05.759> ECC<00:02:06.360> in 00:02:06.830 --> 00:02:06.840 align:start position:0% up the session in Paris after ECC in 00:02:06.840 --> 00:02:10.150 align:start position:0% up the session in Paris after ECC in 2020<00:02:07.500> which<00:02:08.280> was<00:02:08.520> the<00:02:08.819> covet<00:02:09.360> session<00:02:09.599> as<00:02:09.840> well 00:02:10.150 --> 00:02:10.160 align:start position:0% 2020 which was the covet session as well 00:02:10.160 --> 00:02:13.250 align:start position:0% 2020 which was the covet session as well and<00:02:11.160> then<00:02:11.340> we<00:02:11.760> were<00:02:12.480> discussing<00:02:12.959> Also 00:02:13.250 --> 00:02:13.260 align:start position:0% and then we were discussing Also 00:02:13.260 --> 00:02:17.150 align:start position:0% and then we were discussing Also regarding<00:02:13.800> uh<00:02:14.640> like<00:02:14.819> how<00:02:15.060> ethereum<00:02:15.660> can<00:02:16.140> like 00:02:17.150 --> 00:02:17.160 align:start position:0% regarding uh like how ethereum can like 00:02:17.160 --> 00:02:19.670 align:start position:0% regarding uh like how ethereum can like um<00:02:17.220> how<00:02:17.580> like<00:02:17.819> hearts<00:02:18.900> um<00:02:18.959> like<00:02:19.260> The<00:02:19.440> Shard 00:02:19.670 --> 00:02:19.680 align:start position:0% um how like hearts um like The Shard 00:02:19.680 --> 00:02:22.369 align:start position:0% um how like hearts um like The Shard design<00:02:19.920> basically<00:02:20.459> uh<00:02:21.360> and<00:02:21.599> then<00:02:21.720> the<00:02:21.959> ACM 00:02:22.369 --> 00:02:22.379 align:start position:0% design basically uh and then the ACM 00:02:22.379 --> 00:02:25.550 align:start position:0% design basically uh and then the ACM transaction<00:02:23.220> history<00:02:23.640> archive<00:02:24.440> which<00:02:25.440> is 00:02:25.550 --> 00:02:25.560 align:start position:0% transaction history archive which is 00:02:25.560 --> 00:02:28.610 align:start position:0% transaction history archive which is basically<00:02:25.920> about<00:02:26.160> how<00:02:27.120> we<00:02:27.360> can<00:02:27.540> keep<00:02:27.900> the<00:02:28.319> full 00:02:28.610 --> 00:02:28.620 align:start position:0% basically about how we can keep the full 00:02:28.620 --> 00:02:32.390 align:start position:0% basically about how we can keep the full state<00:02:29.040> of<00:02:30.140> all<00:02:31.140> transactions<00:02:31.980> and<00:02:32.220> like 00:02:32.390 --> 00:02:32.400 align:start position:0% state of all transactions and like 00:02:32.400 --> 00:02:34.910 align:start position:0% state of all transactions and like archive<00:02:32.819> notes<00:02:33.239> and<00:02:33.420> all<00:02:33.599> that 00:02:34.910 --> 00:02:34.920 align:start position:0% archive notes and all that 00:02:34.920 --> 00:02:35.750 align:start position:0% archive notes and all that um 00:02:35.750 --> 00:02:35.760 align:start position:0% um 00:02:35.760 --> 00:02:37.130 align:start position:0% um so 00:02:37.130 --> 00:02:37.140 align:start position:0% so 00:02:37.140 --> 00:02:39.050 align:start position:0% so um<00:02:37.200> you<00:02:37.620> guys<00:02:37.800> may<00:02:37.920> be<00:02:38.099> wondering<00:02:38.459> why 00:02:39.050 --> 00:02:39.060 align:start position:0% um you guys may be wondering why 00:02:39.060 --> 00:02:40.970 align:start position:0% um you guys may be wondering why everybody<00:02:39.360> is<00:02:39.720> sitting<00:02:40.020> down<00:02:40.200> even<00:02:40.500> I'm<00:02:40.739> like 00:02:40.970 --> 00:02:40.980 align:start position:0% everybody is sitting down even I'm like 00:02:40.980 --> 00:02:42.170 align:start position:0% everybody is sitting down even I'm like sitting<00:02:41.280> down<00:02:41.400> because<00:02:41.580> I<00:02:41.760> don't<00:02:41.879> want<00:02:42.000> to<00:02:42.060> be 00:02:42.170 --> 00:02:42.180 align:start position:0% sitting down because I don't want to be 00:02:42.180 --> 00:02:44.270 align:start position:0% sitting down because I don't want to be like<00:02:42.360> too<00:02:42.599> much<00:02:42.720> like<00:02:42.959> oh<00:02:43.440> I'm<00:02:43.620> like<00:02:43.800> important 00:02:44.270 --> 00:02:44.280 align:start position:0% like too much like oh I'm like important 00:02:44.280 --> 00:02:46.250 align:start position:0% like too much like oh I'm like important and<00:02:44.459> you<00:02:44.580> guys<00:02:44.700> are<00:02:44.879> not<00:02:45.060> uh<00:02:45.780> but<00:02:45.959> basically 00:02:46.250 --> 00:02:46.260 align:start position:0% and you guys are not uh but basically 00:02:46.260 --> 00:02:48.110 align:start position:0% and you guys are not uh but basically three<00:02:46.620> magician<00:02:47.040> sessions<00:02:47.400> are<00:02:47.640> always<00:02:47.879> like 00:02:48.110 --> 00:02:48.120 align:start position:0% three magician sessions are always like 00:02:48.120 --> 00:02:51.170 align:start position:0% three magician sessions are always like everybody's<00:02:48.780> sort<00:02:49.019> of<00:02:49.200> like<00:02:49.319> on<00:02:49.620> the<00:02:49.800> same 00:02:51.170 --> 00:02:51.180 align:start position:0% everybody's sort of like on the same 00:02:51.180 --> 00:02:54.170 align:start position:0% everybody's sort of like on the same um<00:02:51.239> same<00:02:51.900> like<00:02:52.379> line<00:02:53.099> or<00:02:53.400> something<00:02:53.519> that<00:02:53.879> like 00:02:54.170 --> 00:02:54.180 align:start position:0% um same like line or something that like 00:02:54.180 --> 00:02:56.089 align:start position:0% um same like line or something that like there<00:02:54.300> is<00:02:54.480> no<00:02:54.599> such<00:02:54.780> thing<00:02:54.959> as<00:02:55.140> like<00:02:55.440> oh<00:02:55.800> these 00:02:56.089 --> 00:02:56.099 align:start position:0% there is no such thing as like oh these 00:02:56.099 --> 00:02:57.770 align:start position:0% there is no such thing as like oh these are<00:02:56.220> the<00:02:56.340> cardiffs<00:02:56.940> or<00:02:57.060> like<00:02:57.239> oh<00:02:57.360> these<00:02:57.660> are 00:02:57.770 --> 00:02:57.780 align:start position:0% are the cardiffs or like oh these are 00:02:57.780 --> 00:02:59.270 align:start position:0% are the cardiffs or like oh these are the<00:02:57.900> speakers<00:02:58.080> and<00:02:58.440> they're<00:02:58.560> important<00:02:59.040> like 00:02:59.270 --> 00:02:59.280 align:start position:0% the speakers and they're important like 00:02:59.280 --> 00:03:01.550 align:start position:0% the speakers and they're important like no<00:02:59.519> like<00:02:59.819> everybody<00:03:00.300> is<00:03:00.720> equal<00:03:00.959> and<00:03:01.379> everybody 00:03:01.550 --> 00:03:01.560 align:start position:0% no like everybody is equal and everybody 00:03:01.560 --> 00:03:03.050 align:start position:0% no like everybody is equal and everybody is 00:03:03.050 --> 00:03:03.060 align:start position:0% is 00:03:03.060 --> 00:03:05.150 align:start position:0% is um<00:03:03.120> as<00:03:03.480> important<00:03:03.900> as<00:03:04.379> whether<00:03:04.800> you're<00:03:04.980> a 00:03:05.150 --> 00:03:05.160 align:start position:0% um as important as whether you're a 00:03:05.160 --> 00:03:06.949 align:start position:0% um as important as whether you're a speaker<00:03:05.340> or<00:03:05.819> you<00:03:06.180> are<00:03:06.360> sitting<00:03:06.780> in<00:03:06.840> the 00:03:06.949 --> 00:03:06.959 align:start position:0% speaker or you are sitting in the 00:03:06.959 --> 00:03:09.650 align:start position:0% speaker or you are sitting in the audience<00:03:07.319> uh<00:03:08.220> and<00:03:08.400> I<00:03:08.519> highly<00:03:08.940> encourage<00:03:09.480> you 00:03:09.650 --> 00:03:09.660 align:start position:0% audience uh and I highly encourage you 00:03:09.660 --> 00:03:13.190 align:start position:0% audience uh and I highly encourage you to<00:03:10.140> join<00:03:10.680> us<00:03:10.980> anytime<00:03:11.519> in<00:03:11.760> this<00:03:11.940> like<00:03:12.200> how 00:03:13.190 --> 00:03:13.200 align:start position:0% to join us anytime in this like how 00:03:13.200 --> 00:03:15.050 align:start position:0% to join us anytime in this like how Circle 00:03:15.050 --> 00:03:15.060 align:start position:0% Circle 00:03:15.060 --> 00:03:17.089 align:start position:0% Circle um<00:03:15.120> so<00:03:15.300> if<00:03:15.599> you<00:03:15.720> have<00:03:16.080> like<00:03:16.319> something<00:03:16.500> to<00:03:16.860> say 00:03:17.089 --> 00:03:17.099 align:start position:0% um so if you have like something to say 00:03:17.099 --> 00:03:19.430 align:start position:0% um so if you have like something to say to<00:03:17.459> this<00:03:17.760> session<00:03:18.239> or<00:03:18.540> like<00:03:18.780> to<00:03:18.959> the<00:03:19.140> topic 00:03:19.430 --> 00:03:19.440 align:start position:0% to this session or like to the topic 00:03:19.440 --> 00:03:21.170 align:start position:0% to this session or like to the topic that<00:03:19.620> is<00:03:19.739> being<00:03:19.860> discussed<00:03:20.400> feel<00:03:20.879> free<00:03:21.060> to 00:03:21.170 --> 00:03:21.180 align:start position:0% that is being discussed feel free to 00:03:21.180 --> 00:03:24.350 align:start position:0% that is being discussed feel free to anytime<00:03:21.780> uh<00:03:22.500> switch<00:03:22.800> like<00:03:23.459> anybody<00:03:23.819> just<00:03:24.180> like 00:03:24.350 --> 00:03:24.360 align:start position:0% anytime uh switch like anybody just like 00:03:24.360 --> 00:03:26.149 align:start position:0% anytime uh switch like anybody just like take<00:03:24.540> their<00:03:24.840> seat<00:03:25.080> and<00:03:25.260> be<00:03:25.440> like<00:03:25.560> hey<00:03:25.739> like<00:03:26.040> I 00:03:26.149 --> 00:03:26.159 align:start position:0% take their seat and be like hey like I 00:03:26.159 --> 00:03:28.130 align:start position:0% take their seat and be like hey like I want<00:03:26.340> to<00:03:26.459> like<00:03:26.519> say<00:03:26.760> something<00:03:26.940> to<00:03:27.180> this<00:03:27.360> uh 00:03:28.130 --> 00:03:28.140 align:start position:0% want to like say something to this uh 00:03:28.140 --> 00:03:30.110 align:start position:0% want to like say something to this uh and<00:03:28.260> even<00:03:28.440> grab<00:03:28.739> a<00:03:28.920> mic 00:03:30.110 --> 00:03:30.120 align:start position:0% and even grab a mic 00:03:30.120 --> 00:03:32.390 align:start position:0% and even grab a mic um<00:03:30.239> and<00:03:30.840> I<00:03:31.080> also<00:03:31.440> encourage<00:03:31.800> you<00:03:31.920> to<00:03:32.040> take<00:03:32.220> some 00:03:32.390 --> 00:03:32.400 align:start position:0% um and I also encourage you to take some 00:03:32.400 --> 00:03:34.369 align:start position:0% um and I also encourage you to take some notes<00:03:32.700> or<00:03:32.879> some<00:03:33.120> like<00:03:33.300> ideas<00:03:33.540> that<00:03:34.019> you<00:03:34.200> have 00:03:34.369 --> 00:03:34.379 align:start position:0% notes or some like ideas that you have 00:03:34.379 --> 00:03:36.830 align:start position:0% notes or some like ideas that you have we<00:03:34.860> also<00:03:35.159> have<00:03:35.280> a<00:03:35.400> marker<00:03:35.879> would<00:03:36.480> just<00:03:36.720> like 00:03:36.830 --> 00:03:36.840 align:start position:0% we also have a marker would just like 00:03:36.840 --> 00:03:39.350 align:start position:0% we also have a marker would just like thank<00:03:37.560> you<00:03:37.739> so<00:03:37.860> much<00:03:37.980> who's<00:03:38.280> gonna<00:03:38.640> take<00:03:39.180> a 00:03:39.350 --> 00:03:39.360 align:start position:0% thank you so much who's gonna take a 00:03:39.360 --> 00:03:42.589 align:start position:0% thank you so much who's gonna take a note<00:03:39.540> from<00:03:39.780> this<00:03:39.959> session<00:03:40.200> and<00:03:41.040> then<00:03:41.280> also<00:03:42.000> I 00:03:42.589 --> 00:03:42.599 align:start position:0% note from this session and then also I 00:03:42.599 --> 00:03:45.229 align:start position:0% note from this session and then also I forgot<00:03:42.959> your<00:03:43.200> name<00:03:43.379> uh<00:03:44.220> but<00:03:44.459> uh<00:03:44.760> there<00:03:45.000> is<00:03:45.120> a 00:03:45.229 --> 00:03:45.239 align:start position:0% forgot your name uh but uh there is a 00:03:45.239 --> 00:03:47.089 align:start position:0% forgot your name uh but uh there is a guy<00:03:45.360> who<00:03:45.599> is<00:03:45.720> going<00:03:45.840> to<00:03:45.959> take<00:03:46.260> a<00:03:46.500> note<00:03:46.799> in 00:03:47.089 --> 00:03:47.099 align:start position:0% guy who is going to take a note in 00:03:47.099 --> 00:03:48.949 align:start position:0% guy who is going to take a note in Spanish<00:03:47.400> so<00:03:48.000> we<00:03:48.180> are<00:03:48.360> going<00:03:48.480> to<00:03:48.599> have<00:03:48.780> a 00:03:48.949 --> 00:03:48.959 align:start position:0% Spanish so we are going to have a 00:03:48.959 --> 00:03:51.589 align:start position:0% Spanish so we are going to have a translated<00:03:49.440> notes<00:03:50.400> uh<00:03:50.640> from<00:03:50.879> this<00:03:51.060> session<00:03:51.239> as 00:03:51.589 --> 00:03:51.599 align:start position:0% translated notes uh from this session as 00:03:51.599 --> 00:03:53.930 align:start position:0% translated notes uh from this session as well<00:03:51.780> uh<00:03:52.500> and<00:03:52.680> make<00:03:52.860> sure<00:03:52.980> to<00:03:53.159> publish<00:03:53.459> them<00:03:53.700> on 00:03:53.930 --> 00:03:53.940 align:start position:0% well uh and make sure to publish them on 00:03:53.940 --> 00:03:56.270 align:start position:0% well uh and make sure to publish them on ethereum<00:03:54.480> magician's<00:03:54.959> Farm 00:03:56.270 --> 00:03:56.280 align:start position:0% ethereum magician's Farm 00:03:56.280 --> 00:03:58.789 align:start position:0% ethereum magician's Farm um and<00:03:56.640> then<00:03:56.760> I<00:03:57.659> just<00:03:57.959> figured<00:03:58.319> out<00:03:58.440> that<00:03:58.620> this 00:03:58.789 --> 00:03:58.799 align:start position:0% um and then I just figured out that this 00:03:58.799 --> 00:04:00.530 align:start position:0% um and then I just figured out that this would<00:03:58.980> be<00:03:59.099> a<00:03:59.280> cool<00:03:59.400> quote 00:04:00.530 --> 00:04:00.540 align:start position:0% would be a cool quote 00:04:00.540 --> 00:04:03.110 align:start position:0% would be a cool quote um<00:04:00.659> to<00:04:01.200> my<00:04:01.739> kick<00:04:02.040> up<00:04:02.220> this<00:04:02.340> session<00:04:02.580> to<00:04:03.000> like 00:04:03.110 --> 00:04:03.120 align:start position:0% um to my kick up this session to like 00:04:03.120 --> 00:04:05.809 align:start position:0% um to my kick up this session to like make<00:04:03.480> ethereum<00:04:03.959> more<00:04:04.200> Diversified 00:04:05.809 --> 00:04:05.819 align:start position:0% make ethereum more Diversified 00:04:05.819 --> 00:04:09.289 align:start position:0% make ethereum more Diversified um<00:04:05.879> as<00:04:06.239> I<00:04:06.540> feel<00:04:06.720> like<00:04:06.840> we<00:04:07.080> need<00:04:07.260> more<00:04:07.560> clients 00:04:09.289 --> 00:04:09.299 align:start position:0% um as I feel like we need more clients 00:04:09.299 --> 00:04:11.869 align:start position:0% um as I feel like we need more clients um<00:04:09.420> to<00:04:10.080> be<00:04:10.260> run<00:04:10.560> in<00:04:10.980> the<00:04:11.099> ethereum<00:04:11.580> ecosystem 00:04:11.869 --> 00:04:11.879 align:start position:0% um to be run in the ethereum ecosystem 00:04:11.879 --> 00:04:14.270 align:start position:0% um to be run in the ethereum ecosystem and<00:04:12.239> we<00:04:12.599> should<00:04:12.840> not<00:04:13.019> be 00:04:14.270 --> 00:04:14.280 align:start position:0% and we should not be 00:04:14.280 --> 00:04:16.430 align:start position:0% and we should not be um<00:04:14.340> just<00:04:14.640> focusing<00:04:15.120> ourselves<00:04:15.540> or<00:04:15.780> on<00:04:16.199> the 00:04:16.430 --> 00:04:16.440 align:start position:0% um just focusing ourselves or on the 00:04:16.440 --> 00:04:19.610 align:start position:0% um just focusing ourselves or on the main<00:04:16.620> two<00:04:17.299> clients<00:04:18.299> and<00:04:18.660> by<00:04:18.840> the<00:04:18.959> way<00:04:19.019> the<00:04:19.260> QR 00:04:19.610 --> 00:04:19.620 align:start position:0% main two clients and by the way the QR 00:04:19.620 --> 00:04:22.009 align:start position:0% main two clients and by the way the QR code<00:04:19.799> weird<00:04:20.519> until<00:04:20.940> let<00:04:21.239> the<00:04:21.359> QR<00:04:21.600> code<00:04:21.780> be 00:04:22.009 --> 00:04:22.019 align:start position:0% code weird until let the QR code be 00:04:22.019 --> 00:04:23.570 align:start position:0% code weird until let the QR code be there<00:04:22.199> and<00:04:22.560> that's<00:04:22.740> where<00:04:22.979> you<00:04:23.160> can<00:04:23.280> find<00:04:23.400> the 00:04:23.570 --> 00:04:23.580 align:start position:0% there and that's where you can find the 00:04:23.580 --> 00:04:26.150 align:start position:0% there and that's where you can find the slides<00:04:24.000> and<00:04:24.900> in<00:04:25.380> the<00:04:25.500> slides<00:04:25.800> there<00:04:25.919> are<00:04:26.040> many 00:04:26.150 --> 00:04:26.160 align:start position:0% slides and in the slides there are many 00:04:26.160 --> 00:04:27.890 align:start position:0% slides and in the slides there are many links<00:04:26.520> that<00:04:26.639> what<00:04:27.120> I've<00:04:27.419> been<00:04:27.660> just 00:04:27.890 --> 00:04:27.900 align:start position:0% links that what I've been just 00:04:27.900 --> 00:04:31.370 align:start position:0% links that what I've been just mentioning<00:04:28.440> during<00:04:29.400> my<00:04:29.880> introduction<00:04:30.780> speech 00:04:31.370 --> 00:04:31.380 align:start position:0% mentioning during my introduction speech 00:04:31.380 --> 00:04:33.530 align:start position:0% mentioning during my introduction speech and<00:04:31.860> that's<00:04:32.400> pretty<00:04:32.639> much<00:04:32.820> it<00:04:33.000> from<00:04:33.240> my<00:04:33.419> side 00:04:33.530 --> 00:04:33.540 align:start position:0% and that's pretty much it from my side 00:04:33.540 --> 00:04:35.390 align:start position:0% and that's pretty much it from my side I'm<00:04:33.840> just<00:04:34.020> going<00:04:34.199> to<00:04:34.380> try<00:04:34.680> to<00:04:34.860> encourage<00:04:35.220> you 00:04:35.390 --> 00:04:35.400 align:start position:0% I'm just going to try to encourage you 00:04:35.400 --> 00:04:36.230 align:start position:0% I'm just going to try to encourage you all<00:04:35.520> to 00:04:36.230 --> 00:04:36.240 align:start position:0% all to 00:04:36.240 --> 00:04:39.350 align:start position:0% all to week<00:04:36.660> up<00:04:36.960> uh<00:04:37.919> and<00:04:38.100> like<00:04:38.280> don't<00:04:38.639> be<00:04:38.880> scared<00:04:39.180> even 00:04:39.350 --> 00:04:39.360 align:start position:0% week up uh and like don't be scared even 00:04:39.360 --> 00:04:41.990 align:start position:0% week up uh and like don't be scared even the<00:04:39.660> mic<00:04:39.840> it<00:04:40.500> doesn't<00:04:40.680> bite<00:04:40.979> you<00:04:41.220> and<00:04:41.699> it's 00:04:41.990 --> 00:04:42.000 align:start position:0% the mic it doesn't bite you and it's 00:04:42.000 --> 00:04:44.629 align:start position:0% the mic it doesn't bite you and it's just<00:04:42.360> like<00:04:42.780> our<00:04:43.020> friend<00:04:43.320> and 00:04:44.629 --> 00:04:44.639 align:start position:0% just like our friend and 00:04:44.639 --> 00:04:46.790 align:start position:0% just like our friend and um if<00:04:44.940> you<00:04:45.120> will<00:04:45.300> try<00:04:45.840> to<00:04:46.020> if<00:04:46.380> you<00:04:46.500> want<00:04:46.620> to 00:04:46.790 --> 00:04:46.800 align:start position:0% um if you will try to if you want to 00:04:46.800 --> 00:04:49.850 align:start position:0% um if you will try to if you want to like<00:04:46.979> speak<00:04:47.160> up<00:04:47.340> about<00:04:47.580> something<00:04:47.940> uh<00:04:48.840> we<00:04:49.560> want 00:04:49.850 --> 00:04:49.860 align:start position:0% like speak up about something uh we want 00:04:49.860 --> 00:04:52.129 align:start position:0% like speak up about something uh we want you<00:04:50.100> to<00:04:50.280> like<00:04:50.520> make<00:04:51.000> sure<00:04:51.180> that 00:04:52.129 --> 00:04:52.139 align:start position:0% you to like make sure that 00:04:52.139 --> 00:04:54.890 align:start position:0% you to like make sure that um everybody<00:04:52.800> will<00:04:53.220> hear<00:04:53.460> you<00:04:53.639> basically<00:04:54.180> and 00:04:54.890 --> 00:04:54.900 align:start position:0% um everybody will hear you basically and 00:04:54.900 --> 00:04:56.629 align:start position:0% um everybody will hear you basically and that's<00:04:55.440> pretty<00:04:55.620> much<00:04:55.800> it 00:04:56.629 --> 00:04:56.639 align:start position:0% that's pretty much it 00:04:56.639 --> 00:04:59.270 align:start position:0% that's pretty much it um<00:04:56.699> I'm<00:04:56.880> excited<00:04:57.240> for<00:04:57.540> this<00:04:57.720> I'm<00:04:58.500> just<00:04:58.919> giving 00:04:59.270 --> 00:04:59.280 align:start position:0% um I'm excited for this I'm just giving 00:04:59.280 --> 00:05:01.550 align:start position:0% um I'm excited for this I'm just giving the<00:04:59.699> words<00:04:59.880> to<00:05:00.240> Tim<00:05:00.479> and<00:05:00.900> let's<00:05:01.080> kick<00:05:01.440> off 00:05:01.550 --> 00:05:01.560 align:start position:0% the words to Tim and let's kick off 00:05:01.560 --> 00:05:02.930 align:start position:0% the words to Tim and let's kick off sweet 00:05:02.930 --> 00:05:02.940 align:start position:0% sweet 00:05:02.940 --> 00:05:05.510 align:start position:0% sweet um<00:05:03.000> yeah<00:05:03.360> thanks<00:05:03.540> a<00:05:03.780> lot<00:05:03.900> for<00:05:04.139> the<00:05:04.380> intro 00:05:05.510 --> 00:05:05.520 align:start position:0% um yeah thanks a lot for the intro 00:05:05.520 --> 00:05:07.070 align:start position:0% um yeah thanks a lot for the intro um<00:05:05.699> yeah<00:05:06.000> so<00:05:06.180> I<00:05:06.360> guess<00:05:06.479> on<00:05:06.720> the<00:05:06.840> point<00:05:06.960> of 00:05:07.070 --> 00:05:07.080 align:start position:0% um yeah so I guess on the point of 00:05:07.080 --> 00:05:08.629 align:start position:0% um yeah so I guess on the point of people<00:05:07.320> asking<00:05:07.680> questions<00:05:07.860> and<00:05:08.100> contributing 00:05:08.629 --> 00:05:08.639 align:start position:0% people asking questions and contributing 00:05:08.639 --> 00:05:11.390 align:start position:0% people asking questions and contributing I<00:05:09.120> do<00:05:09.360> not<00:05:09.540> have<00:05:09.780> near<00:05:10.199> three<00:05:10.560> hours<00:05:10.800> of<00:05:11.220> like 00:05:11.390 --> 00:05:11.400 align:start position:0% I do not have near three hours of like 00:05:11.400 --> 00:05:14.150 align:start position:0% I do not have near three hours of like contents<00:05:11.940> here<00:05:12.060> right<00:05:12.300> like<00:05:12.540> so<00:05:12.960> like<00:05:13.160> you 00:05:14.150 --> 00:05:14.160 align:start position:0% contents here right like so like you 00:05:14.160 --> 00:05:15.950 align:start position:0% contents here right like so like you know<00:05:14.280> I<00:05:14.520> have<00:05:14.880> a<00:05:15.060> couple<00:05:15.180> questions<00:05:15.419> to<00:05:15.720> kick 00:05:15.950 --> 00:05:15.960 align:start position:0% know I have a couple questions to kick 00:05:15.960 --> 00:05:18.050 align:start position:0% know I have a couple questions to kick things<00:05:16.139> off<00:05:16.380> but<00:05:16.740> like<00:05:16.979> this<00:05:17.400> is<00:05:17.520> very<00:05:17.699> much<00:05:17.820> on 00:05:18.050 --> 00:05:18.060 align:start position:0% things off but like this is very much on 00:05:18.060 --> 00:05:20.090 align:start position:0% things off but like this is very much on you<00:05:18.240> if<00:05:18.780> uh<00:05:19.139> you<00:05:19.380> will<00:05:19.500> have<00:05:19.620> stuff<00:05:19.800> you<00:05:19.979> want 00:05:20.090 --> 00:05:20.100 align:start position:0% you if uh you will have stuff you want 00:05:20.100 --> 00:05:22.070 align:start position:0% you if uh you will have stuff you want to<00:05:20.220> discuss<00:05:20.460> this<00:05:20.759> is<00:05:20.820> the<00:05:21.000> place<00:05:21.120> for<00:05:21.360> it 00:05:22.070 --> 00:05:22.080 align:start position:0% to discuss this is the place for it 00:05:22.080 --> 00:05:24.350 align:start position:0% to discuss this is the place for it um<00:05:22.199> or<00:05:22.380> we'll<00:05:22.620> be<00:05:22.800> out<00:05:22.919> of<00:05:22.979> here<00:05:23.100> in<00:05:23.220> 50<00:05:23.340> minutes 00:05:24.350 --> 00:05:24.360 align:start position:0% um or we'll be out of here in 50 minutes 00:05:24.360 --> 00:05:26.390 align:start position:0% um or we'll be out of here in 50 minutes um<00:05:24.720> but<00:05:25.259> I<00:05:25.440> guess<00:05:25.560> yeah<00:05:25.740> there's<00:05:26.039> like<00:05:26.280> three 00:05:26.390 --> 00:05:26.400 align:start position:0% um but I guess yeah there's like three 00:05:26.400 --> 00:05:28.670 align:start position:0% um but I guess yeah there's like three things<00:05:26.580> on<00:05:26.820> the<00:05:26.880> slides<00:05:27.180> I<00:05:27.360> think<00:05:27.539> uh<00:05:27.960> or<00:05:28.080> needs 00:05:28.670 --> 00:05:28.680 align:start position:0% things on the slides I think uh or needs 00:05:28.680 --> 00:05:30.409 align:start position:0% things on the slides I think uh or needs to<00:05:28.740> discuss<00:05:28.919> with<00:05:29.160> the<00:05:29.280> people<00:05:29.580> here<00:05:30.180> um<00:05:30.240> first 00:05:30.409 --> 00:05:30.419 align:start position:0% to discuss with the people here um first 00:05:30.419 --> 00:05:32.810 align:start position:0% to discuss with the people here um first is<00:05:30.539> just<00:05:30.720> like<00:05:30.780> how<00:05:30.960> the<00:05:31.080> merge<00:05:31.380> went<00:05:31.560> it<00:05:31.860> was<00:05:31.979> a 00:05:32.810 --> 00:05:32.820 align:start position:0% is just like how the merge went it was a 00:05:32.820 --> 00:05:34.550 align:start position:0% is just like how the merge went it was a pretty<00:05:33.180> big<00:05:33.360> piece<00:05:33.720> of<00:05:33.780> work 00:05:34.550 --> 00:05:34.560 align:start position:0% pretty big piece of work 00:05:34.560 --> 00:05:36.529 align:start position:0% pretty big piece of work um<00:05:34.680> not<00:05:35.160> only<00:05:35.340> technically<00:05:35.759> but<00:05:36.000> just<00:05:36.240> like 00:05:36.529 --> 00:05:36.539 align:start position:0% um not only technically but just like 00:05:36.539 --> 00:05:38.570 align:start position:0% um not only technically but just like making<00:05:37.440> it<00:05:37.680> happen<00:05:37.800> from<00:05:38.100> like<00:05:38.280> a<00:05:38.460> human 00:05:38.570 --> 00:05:38.580 align:start position:0% making it happen from like a human 00:05:38.580 --> 00:05:40.129 align:start position:0% making it happen from like a human perspective<00:05:39.060> we<00:05:39.479> have<00:05:39.660> all<00:05:39.780> these<00:05:39.960> teams 00:05:40.129 --> 00:05:40.139 align:start position:0% perspective we have all these teams 00:05:40.139 --> 00:05:41.810 align:start position:0% perspective we have all these teams working<00:05:40.320> together<00:05:40.620> so 00:05:41.810 --> 00:05:41.820 align:start position:0% working together so 00:05:41.820 --> 00:05:44.029 align:start position:0% working together so um<00:05:41.880> yeah<00:05:42.300> I'm<00:05:42.780> personally<00:05:43.440> curious<00:05:43.800> to<00:05:43.919> hear 00:05:44.029 --> 00:05:44.039 align:start position:0% um yeah I'm personally curious to hear 00:05:44.039 --> 00:05:45.230 align:start position:0% um yeah I'm personally curious to hear just<00:05:44.220> from<00:05:44.340> the<00:05:44.460> different<00:05:44.580> client<00:05:44.880> teams<00:05:45.120> and 00:05:45.230 --> 00:05:45.240 align:start position:0% just from the different client teams and 00:05:45.240 --> 00:05:46.670 align:start position:0% just from the different client teams and folks<00:05:45.479> involved<00:05:45.780> like<00:05:45.960> how<00:05:46.199> that<00:05:46.500> whole 00:05:46.670 --> 00:05:46.680 align:start position:0% folks involved like how that whole 00:05:46.680 --> 00:05:48.170 align:start position:0% folks involved like how that whole process<00:05:46.919> went<00:05:47.160> is<00:05:47.520> there<00:05:47.639> things<00:05:47.820> we<00:05:47.940> can<00:05:48.060> do 00:05:48.170 --> 00:05:48.180 align:start position:0% process went is there things we can do 00:05:48.180 --> 00:05:49.969 align:start position:0% process went is there things we can do better<00:05:48.300> for<00:05:48.660> like<00:05:48.840> the<00:05:49.080> next<00:05:49.199> one 00:05:49.969 --> 00:05:49.979 align:start position:0% better for like the next one 00:05:49.979 --> 00:05:51.170 align:start position:0% better for like the next one um<00:05:50.039> or<00:05:50.220> things<00:05:50.340> we<00:05:50.460> did<00:05:50.639> well<00:05:50.699> that<00:05:50.880> we<00:05:51.060> didn't 00:05:51.170 --> 00:05:51.180 align:start position:0% um or things we did well that we didn't 00:05:51.180 --> 00:05:52.670 align:start position:0% um or things we did well that we didn't expect<00:05:51.300> to<00:05:51.479> do<00:05:51.600> so<00:05:51.780> well 00:05:52.670 --> 00:05:52.680 align:start position:0% expect to do so well 00:05:52.680 --> 00:05:54.770 align:start position:0% expect to do so well um<00:05:52.800> after<00:05:53.280> that<00:05:53.580> like<00:05:53.880> we<00:05:54.180> keep<00:05:54.360> talking<00:05:54.539> about 00:05:54.770 --> 00:05:54.780 align:start position:0% um after that like we keep talking about 00:05:54.780 --> 00:05:56.990 align:start position:0% um after that like we keep talking about like<00:05:55.020> The<00:05:55.259> Surge<00:05:55.500> Verge<00:05:55.800> Purge<00:05:56.220> Splurge<00:05:56.699> all 00:05:56.990 --> 00:05:57.000 align:start position:0% like The Surge Verge Purge Splurge all 00:05:57.000 --> 00:05:57.890 align:start position:0% like The Surge Verge Purge Splurge all that<00:05:57.180> stuff 00:05:57.890 --> 00:05:57.900 align:start position:0% that stuff 00:05:57.900 --> 00:05:59.689 align:start position:0% that stuff um<00:05:58.020> I<00:05:58.380> think<00:05:58.500> I<00:05:58.919> just<00:05:59.100> want<00:05:59.280> to<00:05:59.400> make<00:05:59.460> sure<00:05:59.580> we 00:05:59.689 --> 00:05:59.699 align:start position:0% um I think I just want to make sure we 00:05:59.699 --> 00:06:01.010 align:start position:0% um I think I just want to make sure we have<00:05:59.820> space<00:06:00.060> you<00:06:00.479> know<00:06:00.539> to<00:06:00.720> hear<00:06:00.840> from 00:06:01.010 --> 00:06:01.020 align:start position:0% have space you know to hear from 00:06:01.020 --> 00:06:03.050 align:start position:0% have space you know to hear from different<00:06:01.199> kind<00:06:01.440> teams<00:06:01.800> about<00:06:01.919> like<00:06:02.160> how<00:06:02.880> they 00:06:03.050 --> 00:06:03.060 align:start position:0% different kind teams about like how they 00:06:03.060 --> 00:06:04.790 align:start position:0% different kind teams about like how they see<00:06:03.240> priorities<00:06:03.660> there<00:06:04.020> what<00:06:04.380> they<00:06:04.500> think<00:06:04.620> is 00:06:04.790 --> 00:06:04.800 align:start position:0% see priorities there what they think is 00:06:04.800 --> 00:06:06.469 align:start position:0% see priorities there what they think is important<00:06:05.220> where<00:06:05.580> things<00:06:05.820> are<00:06:06.000> generally<00:06:06.240> at 00:06:06.469 --> 00:06:06.479 align:start position:0% important where things are generally at 00:06:06.479 --> 00:06:07.969 align:start position:0% important where things are generally at and<00:06:06.960> then<00:06:07.080> answer<00:06:07.199> all<00:06:07.440> the<00:06:07.560> questions<00:06:07.680> from 00:06:07.969 --> 00:06:07.979 align:start position:0% and then answer all the questions from 00:06:07.979 --> 00:06:11.330 align:start position:0% and then answer all the questions from you<00:06:08.160> guys<00:06:08.280> because<00:06:08.580> I<00:06:09.060> think<00:06:09.180> it's<00:06:09.660> uh<00:06:10.500> easy<00:06:11.039> to 00:06:11.330 --> 00:06:11.340 align:start position:0% you guys because I think it's uh easy to 00:06:11.340 --> 00:06:13.550 align:start position:0% you guys because I think it's uh easy to like<00:06:11.520> look<00:06:11.639> at<00:06:11.759> the<00:06:11.940> four<00:06:12.060> acronyms<00:06:12.780> or<00:06:13.080> like 00:06:13.550 --> 00:06:13.560 align:start position:0% like look at the four acronyms or like 00:06:13.560 --> 00:06:15.710 align:start position:0% like look at the four acronyms or like meme<00:06:13.800> names<00:06:14.039> and<00:06:14.520> then<00:06:14.639> when<00:06:15.240> you<00:06:15.360> get<00:06:15.479> it<00:06:15.600> to 00:06:15.710 --> 00:06:15.720 align:start position:0% meme names and then when you get it to 00:06:15.720 --> 00:06:17.510 align:start position:0% meme names and then when you get it to the<00:06:15.900> details<00:06:16.259> there's<00:06:16.440> like<00:06:16.680> many<00:06:17.100> more<00:06:17.340> open 00:06:17.510 --> 00:06:17.520 align:start position:0% the details there's like many more open 00:06:17.520 --> 00:06:18.950 align:start position:0% the details there's like many more open questions<00:06:17.880> so<00:06:18.180> hopefully<00:06:18.479> we<00:06:18.600> could<00:06:18.720> get<00:06:18.900> into 00:06:18.950 --> 00:06:18.960 align:start position:0% questions so hopefully we could get into 00:06:18.960 --> 00:06:20.689 align:start position:0% questions so hopefully we could get into some<00:06:19.139> of<00:06:19.259> those 00:06:20.689 --> 00:06:20.699 align:start position:0% some of those 00:06:20.699 --> 00:06:22.129 align:start position:0% some of those um and<00:06:21.060> then<00:06:21.180> yeah<00:06:21.300> we'll<00:06:21.479> try<00:06:21.660> and<00:06:21.780> keep<00:06:21.900> time 00:06:22.129 --> 00:06:22.139 align:start position:0% um and then yeah we'll try and keep time 00:06:22.139 --> 00:06:23.150 align:start position:0% um and then yeah we'll try and keep time at<00:06:22.319> the<00:06:22.440> end 00:06:23.150 --> 00:06:23.160 align:start position:0% at the end 00:06:23.160 --> 00:06:24.469 align:start position:0% at the end um<00:06:23.220> or<00:06:23.400> actually<00:06:23.520> we<00:06:23.819> will<00:06:23.940> keep<00:06:24.120> coming<00:06:24.300> no 00:06:24.469 --> 00:06:24.479 align:start position:0% um or actually we will keep coming no 00:06:24.479 --> 00:06:25.670 align:start position:0% um or actually we will keep coming no matter<00:06:24.600> what<00:06:24.780> at<00:06:24.960> the<00:06:25.080> end 00:06:25.670 --> 00:06:25.680 align:start position:0% matter what at the end 00:06:25.680 --> 00:06:27.409 align:start position:0% matter what at the end um<00:06:25.800> to<00:06:25.979> just<00:06:26.280> discuss<00:06:26.460> like<00:06:26.639> specific<00:06:26.819> eip's 00:06:27.409 --> 00:06:27.419 align:start position:0% um to just discuss like specific eip's 00:06:27.419 --> 00:06:28.610 align:start position:0% um to just discuss like specific eip's like<00:06:27.539> there's<00:06:27.660> a<00:06:27.720> bunch<00:06:27.840> of<00:06:27.900> VIP<00:06:28.139> Champions 00:06:28.610 --> 00:06:28.620 align:start position:0% like there's a bunch of VIP Champions 00:06:28.620 --> 00:06:30.350 align:start position:0% like there's a bunch of VIP Champions shanghai's<00:06:29.520> planning's<00:06:30.060> been<00:06:30.180> a<00:06:30.300> bit 00:06:30.350 --> 00:06:30.360 align:start position:0% shanghai's planning's been a bit 00:06:30.360 --> 00:06:32.029 align:start position:0% shanghai's planning's been a bit different<00:06:30.479> because<00:06:30.840> we<00:06:31.319> we<00:06:31.500> canceled<00:06:31.800> the 00:06:32.029 --> 00:06:32.039 align:start position:0% different because we we canceled the 00:06:32.039 --> 00:06:33.770 align:start position:0% different because we we canceled the calls<00:06:32.460> after<00:06:32.580> it<00:06:32.880> emerges<00:06:33.240> to<00:06:33.360> give<00:06:33.479> people<00:06:33.600> a 00:06:33.770 --> 00:06:33.780 align:start position:0% calls after it emerges to give people a 00:06:33.780 --> 00:06:35.990 align:start position:0% calls after it emerges to give people a break<00:06:33.960> uh<00:06:34.500> so<00:06:34.620> everyone<00:06:34.740> has<00:06:35.160> like<00:06:35.340> eaps<00:06:35.880> that 00:06:35.990 --> 00:06:36.000 align:start position:0% break uh so everyone has like eaps that 00:06:36.000 --> 00:06:37.249 align:start position:0% break uh so everyone has like eaps that they<00:06:36.120> want<00:06:36.240> to<00:06:36.360> put<00:06:36.419> in 00:06:37.249 --> 00:06:37.259 align:start position:0% they want to put in 00:06:37.259 --> 00:06:38.629 align:start position:0% they want to put in um<00:06:37.380> not<00:06:37.560> other<00:06:37.800> places<00:06:38.039> to<00:06:38.280> discuss<00:06:38.460> them 00:06:38.629 --> 00:06:38.639 align:start position:0% um not other places to discuss them 00:06:38.639 --> 00:06:40.309 align:start position:0% um not other places to discuss them right<00:06:38.819> now<00:06:38.940> so<00:06:39.180> we'll<00:06:39.300> use<00:06:39.479> this<00:06:39.660> as<00:06:39.840> a<00:06:40.020> sort<00:06:40.139> of 00:06:40.309 --> 00:06:40.319 align:start position:0% right now so we'll use this as a sort of 00:06:40.319 --> 00:06:42.230 align:start position:0% right now so we'll use this as a sort of pressure<00:06:40.860> valve<00:06:41.400> for<00:06:41.819> some<00:06:42.000> of<00:06:42.120> those 00:06:42.230 --> 00:06:42.240 align:start position:0% pressure valve for some of those 00:06:42.240 --> 00:06:43.670 align:start position:0% pressure valve for some of those discussions 00:06:43.670 --> 00:06:43.680 align:start position:0% discussions 00:06:43.680 --> 00:06:44.629 align:start position:0% discussions um<00:06:43.740> yeah 00:06:44.629 --> 00:06:44.639 align:start position:0% um yeah 00:06:44.639 --> 00:06:46.670 align:start position:0% um yeah but<00:06:45.360> again<00:06:45.539> yeah<00:06:45.900> please<00:06:46.080> ask<00:06:46.380> questions 00:06:46.670 --> 00:06:46.680 align:start position:0% but again yeah please ask questions 00:06:46.680 --> 00:06:49.490 align:start position:0% but again yeah please ask questions throughout<00:06:48.060> um<00:06:48.120> otherwise<00:06:48.840> this<00:06:49.199> is<00:06:49.319> going<00:06:49.440> to 00:06:49.490 --> 00:06:49.500 align:start position:0% throughout um otherwise this is going to 00:06:49.500 --> 00:06:50.930 align:start position:0% throughout um otherwise this is going to be<00:06:49.560> over<00:06:49.620> pretty<00:06:49.860> quick 00:06:50.930 --> 00:06:50.940 align:start position:0% be over pretty quick 00:06:50.940 --> 00:06:53.870 align:start position:0% be over pretty quick um<00:06:51.000> but<00:06:51.539> yeah<00:06:51.600> to<00:06:52.259> kick<00:06:52.440> it<00:06:52.560> off<00:06:52.979> um<00:06:53.100> I<00:06:53.400> I<00:06:53.699> just 00:06:53.870 --> 00:06:53.880 align:start position:0% um but yeah to kick it off um I I just 00:06:53.880 --> 00:06:55.070 align:start position:0% um but yeah to kick it off um I I just was<00:06:54.000> curious<00:06:54.360> to<00:06:54.479> hear<00:06:54.600> from<00:06:54.720> like<00:06:54.900> different 00:06:55.070 --> 00:06:55.080 align:start position:0% was curious to hear from like different 00:06:55.080 --> 00:06:56.150 align:start position:0% was curious to hear from like different folks<00:06:55.319> on<00:06:55.440> kite<00:06:55.680> teams<00:06:55.919> like<00:06:56.039> their 00:06:56.150 --> 00:06:56.160 align:start position:0% folks on kite teams like their 00:06:56.160 --> 00:06:58.010 align:start position:0% folks on kite teams like their perspective<00:06:56.520> I'm<00:06:56.759> like<00:06:56.940> not<00:06:57.660> like 00:06:58.010 --> 00:06:58.020 align:start position:0% perspective I'm like not like 00:06:58.020 --> 00:06:59.809 align:start position:0% perspective I'm like not like technically<00:06:58.620> how<00:06:58.919> the<00:06:59.100> merge<00:06:59.400> went<00:06:59.460> like<00:06:59.699> I 00:06:59.809 --> 00:06:59.819 align:start position:0% technically how the merge went like I 00:06:59.819 --> 00:07:01.189 align:start position:0% technically how the merge went like I think<00:06:59.940> we've<00:07:00.120> covered<00:07:00.600> that<00:07:00.780> a<00:07:00.900> lot<00:07:01.020> already 00:07:01.189 --> 00:07:01.199 align:start position:0% think we've covered that a lot already 00:07:01.199 --> 00:07:03.409 align:start position:0% think we've covered that a lot already but<00:07:01.560> just<00:07:01.740> how<00:07:02.280> they<00:07:02.460> felt<00:07:02.759> during<00:07:03.060> the 00:07:03.409 --> 00:07:03.419 align:start position:0% but just how they felt during the 00:07:03.419 --> 00:07:05.510 align:start position:0% but just how they felt during the process<00:07:03.720> and<00:07:04.199> like<00:07:04.380> you<00:07:04.919> know<00:07:04.979> now<00:07:05.160> that<00:07:05.340> it's 00:07:05.510 --> 00:07:05.520 align:start position:0% process and like you know now that it's 00:07:05.520 --> 00:07:07.370 align:start position:0% process and like you know now that it's over<00:07:05.699> and<00:07:06.000> and<00:07:06.240> we<00:07:06.660> have<00:07:06.780> a<00:07:06.900> bit<00:07:07.020> more<00:07:07.139> distance 00:07:07.370 --> 00:07:07.380 align:start position:0% over and and we have a bit more distance 00:07:07.380 --> 00:07:09.830 align:start position:0% over and and we have a bit more distance like<00:07:07.800> looking<00:07:08.580> back<00:07:08.880> how<00:07:09.300> do<00:07:09.419> you<00:07:09.539> feel<00:07:09.660> it 00:07:09.830 --> 00:07:09.840 align:start position:0% like looking back how do you feel it 00:07:09.840 --> 00:07:11.570 align:start position:0% like looking back how do you feel it went<00:07:10.259> and<00:07:10.500> other<00:07:11.039> things<00:07:11.280> that<00:07:11.340> could<00:07:11.460> have 00:07:11.570 --> 00:07:11.580 align:start position:0% went and other things that could have 00:07:11.580 --> 00:07:16.850 align:start position:0% went and other things that could have been<00:07:11.699> better<00:07:11.819> oh<00:07:12.720> yeah 00:07:16.850 --> 00:07:16.860 align:start position:0% 00:07:16.860 --> 00:07:19.430 align:start position:0% I<00:07:17.280> made<00:07:17.400> the<00:07:17.520> mistake<00:07:17.759> of<00:07:17.819> sitting<00:07:18.060> beside<00:07:18.300> Tim 00:07:19.430 --> 00:07:19.440 align:start position:0% I made the mistake of sitting beside Tim 00:07:19.440 --> 00:07:20.110 align:start position:0% I made the mistake of sitting beside Tim um 00:07:20.110 --> 00:07:20.120 align:start position:0% um 00:07:20.120 --> 00:07:23.570 align:start position:0% um uh<00:07:21.120> it<00:07:21.900> was<00:07:21.960> stressful<00:07:22.380> it<00:07:23.039> was<00:07:23.160> really<00:07:23.400> really 00:07:23.570 --> 00:07:23.580 align:start position:0% uh it was stressful it was really really 00:07:23.580 --> 00:07:25.249 align:start position:0% uh it was stressful it was really really stressful<00:07:24.060> and<00:07:24.300> really<00:07:24.479> drawn<00:07:24.780> out<00:07:24.900> for<00:07:25.139> a 00:07:25.249 --> 00:07:25.259 align:start position:0% stressful and really drawn out for a 00:07:25.259 --> 00:07:27.890 align:start position:0% stressful and really drawn out for a long<00:07:25.380> time<00:07:25.560> and<00:07:25.979> I<00:07:26.099> think<00:07:26.280> as<00:07:26.759> quarters<00:07:27.180> we've 00:07:27.890 --> 00:07:27.900 align:start position:0% long time and I think as quarters we've 00:07:27.900 --> 00:07:29.990 align:start position:0% long time and I think as quarters we've all<00:07:28.020> felt<00:07:28.319> that<00:07:28.440> real<00:07:28.620> pressure 00:07:29.990 --> 00:07:30.000 align:start position:0% all felt that real pressure 00:07:30.000 --> 00:07:31.370 align:start position:0% all felt that real pressure um<00:07:30.120> so<00:07:30.539> that's<00:07:30.660> that's<00:07:30.840> kind<00:07:31.080> of<00:07:31.199> the<00:07:31.259> personal 00:07:31.370 --> 00:07:31.380 align:start position:0% um so that's that's kind of the personal 00:07:31.380 --> 00:07:33.350 align:start position:0% um so that's that's kind of the personal view<00:07:31.680> of<00:07:31.860> it<00:07:32.039> I<00:07:32.580> don't<00:07:32.819> know<00:07:32.940> how<00:07:33.060> you<00:07:33.240> change 00:07:33.350 --> 00:07:33.360 align:start position:0% view of it I don't know how you change 00:07:33.360 --> 00:07:34.850 align:start position:0% view of it I don't know how you change that<00:07:33.599> I'm<00:07:33.780> not<00:07:33.960> sure<00:07:34.080> we<00:07:34.199> should<00:07:34.380> because<00:07:34.560> we 00:07:34.850 --> 00:07:34.860 align:start position:0% that I'm not sure we should because we 00:07:34.860 --> 00:07:36.469 align:start position:0% that I'm not sure we should because we should<00:07:34.979> have<00:07:35.099> been<00:07:35.220> under<00:07:35.400> pressure<00:07:35.639> to<00:07:35.880> ship 00:07:36.469 --> 00:07:36.479 align:start position:0% should have been under pressure to ship 00:07:36.479 --> 00:07:37.850 align:start position:0% should have been under pressure to ship and<00:07:36.720> we<00:07:36.840> were 00:07:37.850 --> 00:07:37.860 align:start position:0% and we were 00:07:37.860 --> 00:07:40.430 align:start position:0% and we were um<00:07:37.979> but<00:07:38.400> you<00:07:38.520> know<00:07:38.639> I<00:07:39.240> guess<00:07:39.539> I'd<00:07:39.720> say<00:07:39.900> never<00:07:40.259> be 00:07:40.430 --> 00:07:40.440 align:start position:0% um but you know I guess I'd say never be 00:07:40.440 --> 00:07:41.689 align:start position:0% um but you know I guess I'd say never be in<00:07:40.560> doubt<00:07:40.800> that<00:07:40.919> core<00:07:41.099> devs<00:07:41.460> feel<00:07:41.580> the 00:07:41.689 --> 00:07:41.699 align:start position:0% in doubt that core devs feel the 00:07:41.699 --> 00:07:43.070 align:start position:0% in doubt that core devs feel the pressure<00:07:41.819> to<00:07:42.060> ship 00:07:43.070 --> 00:07:43.080 align:start position:0% pressure to ship 00:07:43.080 --> 00:07:46.129 align:start position:0% pressure to ship um<00:07:43.139> we<00:07:43.560> really<00:07:43.740> do<00:07:44.039> uh 00:07:46.129 --> 00:07:46.139 align:start position:0% um we really do uh 00:07:46.139 --> 00:07:49.070 align:start position:0% um we really do uh yeah<00:07:46.740> I<00:07:46.919> think<00:07:47.099> there<00:07:47.520> were<00:07:47.759> a<00:07:48.720> lot<00:07:48.840> of<00:07:48.960> really 00:07:49.070 --> 00:07:49.080 align:start position:0% yeah I think there were a lot of really 00:07:49.080 --> 00:07:51.469 align:start position:0% yeah I think there were a lot of really good<00:07:49.319> things<00:07:49.500> we<00:07:49.740> did<00:07:49.860> the<00:07:50.099> testing<00:07:50.520> that<00:07:51.300> we 00:07:51.469 --> 00:07:51.479 align:start position:0% good things we did the testing that we 00:07:51.479 --> 00:07:54.290 align:start position:0% good things we did the testing that we we<00:07:51.720> managed<00:07:52.080> to<00:07:52.259> do<00:07:52.440> was<00:07:52.979> phenomenal 00:07:54.290 --> 00:07:54.300 align:start position:0% we managed to do was phenomenal 00:07:54.300 --> 00:07:55.670 align:start position:0% we managed to do was phenomenal um<00:07:54.360> and<00:07:54.599> it<00:07:54.720> was<00:07:54.840> a<00:07:55.020> kind<00:07:55.199> of<00:07:55.259> another<00:07:55.380> couple 00:07:55.670 --> 00:07:55.680 align:start position:0% um and it was a kind of another couple 00:07:55.680 --> 00:07:57.110 align:start position:0% um and it was a kind of another couple of<00:07:55.860> steps<00:07:56.220> up<00:07:56.280> on<00:07:56.460> anything<00:07:56.639> we've<00:07:57.000> done 00:07:57.110 --> 00:07:57.120 align:start position:0% of steps up on anything we've done 00:07:57.120 --> 00:07:59.210 align:start position:0% of steps up on anything we've done before<00:07:57.300> for<00:07:57.660> hard<00:07:57.780> forks<00:07:58.319> and<00:07:58.800> that<00:07:58.979> kind<00:07:59.099> of 00:07:59.210 --> 00:07:59.220 align:start position:0% before for hard forks and that kind of 00:07:59.220 --> 00:08:01.550 align:start position:0% before for hard forks and that kind of coordination<00:07:59.639> and<00:08:00.419> and<00:08:00.780> work<00:08:01.020> that<00:08:01.199> went<00:08:01.380> into 00:08:01.550 --> 00:08:01.560 align:start position:0% coordination and and work that went into 00:08:01.560 --> 00:08:04.070 align:start position:0% coordination and and work that went into that<00:08:01.740> was<00:08:01.979> absolutely<00:08:02.520> fantastic 00:08:04.070 --> 00:08:04.080 align:start position:0% that was absolutely fantastic 00:08:04.080 --> 00:08:04.670 align:start position:0% that was absolutely fantastic um 00:08:04.670 --> 00:08:04.680 align:start position:0% um 00:08:04.680 --> 00:08:05.990 align:start position:0% um starting<00:08:04.979> with<00:08:05.220> the<00:08:05.340> client<00:08:05.460> teams<00:08:05.759> testing 00:08:05.990 --> 00:08:06.000 align:start position:0% starting with the client teams testing 00:08:06.000 --> 00:08:07.490 align:start position:0% starting with the client teams testing their<00:08:06.120> releases<00:08:06.479> but<00:08:06.720> then<00:08:06.840> the<00:08:07.080> EF<00:08:07.319> support 00:08:07.490 --> 00:08:07.500 align:start position:0% their releases but then the EF support 00:08:07.500 --> 00:08:09.230 align:start position:0% their releases but then the EF support was<00:08:07.680> spinning<00:08:07.919> up<00:08:08.160> the<00:08:08.400> shadow<00:08:08.580> test<00:08:08.819> Nets 00:08:09.230 --> 00:08:09.240 align:start position:0% was spinning up the shadow test Nets 00:08:09.240 --> 00:08:11.029 align:start position:0% was spinning up the shadow test Nets were<00:08:09.419> a<00:08:09.539> brilliant<00:08:10.020> idea 00:08:11.029 --> 00:08:11.039 align:start position:0% were a brilliant idea 00:08:11.039 --> 00:08:13.610 align:start position:0% were a brilliant idea um<00:08:11.160> and<00:08:11.580> uh<00:08:12.000> Mario<00:08:12.240> and<00:08:12.660> and<00:08:12.960> other<00:08:13.500> people 00:08:13.610 --> 00:08:13.620 align:start position:0% um and uh Mario and and other people 00:08:13.620 --> 00:08:15.469 align:start position:0% um and uh Mario and and other people contributing<00:08:14.160> to<00:08:14.400> the 00:08:15.469 --> 00:08:15.479 align:start position:0% contributing to the 00:08:15.479 --> 00:08:17.930 align:start position:0% contributing to the um test<00:08:15.780> Suites<00:08:16.259> uh<00:08:16.860> And<00:08:17.039> Hive<00:08:17.280> tests<00:08:17.699> and 00:08:17.930 --> 00:08:17.940 align:start position:0% um test Suites uh And Hive tests and 00:08:17.940 --> 00:08:19.309 align:start position:0% um test Suites uh And Hive tests and that<00:08:18.120> kind<00:08:18.240> of<00:08:18.360> thing<00:08:18.479> really<00:08:19.139> really 00:08:19.309 --> 00:08:19.319 align:start position:0% that kind of thing really really 00:08:19.319 --> 00:08:22.909 align:start position:0% that kind of thing really really valuable<00:08:19.740> I<00:08:20.580> don't<00:08:20.759> think<00:08:21.060> we<00:08:21.660> started<00:08:22.620> those 00:08:22.909 --> 00:08:22.919 align:start position:0% valuable I don't think we started those 00:08:22.919 --> 00:08:25.610 align:start position:0% valuable I don't think we started those Hive<00:08:23.160> tests<00:08:23.580> in<00:08:23.699> particular<00:08:24.000> early<00:08:24.360> enough 00:08:25.610 --> 00:08:25.620 align:start position:0% Hive tests in particular early enough 00:08:25.620 --> 00:08:26.930 align:start position:0% Hive tests in particular early enough um<00:08:25.740> and<00:08:25.979> I<00:08:26.039> think<00:08:26.160> that<00:08:26.460> probably<00:08:26.580> is<00:08:26.819> a 00:08:26.930 --> 00:08:26.940 align:start position:0% um and I think that probably is a 00:08:26.940 --> 00:08:27.830 align:start position:0% um and I think that probably is a knock-on<00:08:27.180> effect<00:08:27.360> and<00:08:27.599> we<00:08:27.720> didn't 00:08:27.830 --> 00:08:27.840 align:start position:0% knock-on effect and we didn't 00:08:27.840 --> 00:08:28.969 align:start position:0% knock-on effect and we didn't necessarily<00:08:28.199> include<00:08:28.440> the<00:08:28.560> execution 00:08:28.969 --> 00:08:28.979 align:start position:0% necessarily include the execution 00:08:28.979 --> 00:08:31.369 align:start position:0% necessarily include the execution clients<00:08:29.520> early<00:08:29.819> enough<00:08:30.120> uh<00:08:30.960> which<00:08:31.139> might<00:08:31.259> have 00:08:31.369 --> 00:08:31.379 align:start position:0% clients early enough uh which might have 00:08:31.379 --> 00:08:32.329 align:start position:0% clients early enough uh which might have been<00:08:31.500> because<00:08:31.620> they<00:08:31.800> were<00:08:31.919> busy<00:08:32.099> with<00:08:32.219> you 00:08:32.329 --> 00:08:32.339 align:start position:0% been because they were busy with you 00:08:32.339 --> 00:08:34.610 align:start position:0% been because they were busy with you know<00:08:32.459> 1559<00:08:33.060> or<00:08:33.240> something<00:08:33.360> giant 00:08:34.610 --> 00:08:34.620 align:start position:0% know 1559 or something giant 00:08:34.620 --> 00:08:36.110 align:start position:0% know 1559 or something giant um<00:08:34.680> so<00:08:35.099> I'm<00:08:35.219> not<00:08:35.339> sure<00:08:35.459> what<00:08:35.640> the<00:08:35.820> timelines 00:08:36.110 --> 00:08:36.120 align:start position:0% um so I'm not sure what the timelines 00:08:36.120 --> 00:08:38.149 align:start position:0% um so I'm not sure what the timelines there<00:08:36.360> exactly<00:08:36.719> were<00:08:36.839> but<00:08:37.080> it<00:08:37.320> it<00:08:37.620> felt<00:08:38.039> like 00:08:38.149 --> 00:08:38.159 align:start position:0% there exactly were but it it felt like 00:08:38.159 --> 00:08:41.209 align:start position:0% there exactly were but it it felt like consensus<00:08:38.880> side<00:08:39.180> almost<00:08:39.539> felt<00:08:40.320> confident<00:08:40.979> and 00:08:41.209 --> 00:08:41.219 align:start position:0% consensus side almost felt confident and 00:08:41.219 --> 00:08:42.829 align:start position:0% consensus side almost felt confident and ready<00:08:41.339> and<00:08:41.640> execution<00:08:42.000> was<00:08:42.180> kind<00:08:42.360> of<00:08:42.479> like<00:08:42.479> oh 00:08:42.829 --> 00:08:42.839 align:start position:0% ready and execution was kind of like oh 00:08:42.839 --> 00:08:44.149 align:start position:0% ready and execution was kind of like oh yeah<00:08:43.020> emerge<00:08:43.440> the<00:08:43.560> merge<00:08:43.740> is<00:08:43.800> the<00:08:43.919> next<00:08:44.039> thing 00:08:44.149 --> 00:08:44.159 align:start position:0% yeah emerge the merge is the next thing 00:08:44.159 --> 00:08:46.250 align:start position:0% yeah emerge the merge is the next thing we've<00:08:44.399> got<00:08:44.640> time<00:08:44.820> now<00:08:45.000> we<00:08:45.180> can<00:08:45.300> look<00:08:45.420> and<00:08:46.080> it 00:08:46.250 --> 00:08:46.260 align:start position:0% we've got time now we can look and it 00:08:46.260 --> 00:08:47.870 align:start position:0% we've got time now we can look and it wasn't<00:08:46.440> wasn't<00:08:46.980> a<00:08:47.220> surprise<00:08:47.459> to<00:08:47.580> them<00:08:47.700> don't 00:08:47.870 --> 00:08:47.880 align:start position:0% wasn't wasn't a surprise to them don't 00:08:47.880 --> 00:08:49.490 align:start position:0% wasn't wasn't a surprise to them don't don't<00:08:48.120> get<00:08:48.360> me<00:08:48.480> wrong<00:08:48.600> but<00:08:48.779> I<00:08:49.080> think<00:08:49.200> that<00:08:49.380> was 00:08:49.490 --> 00:08:49.500 align:start position:0% don't get me wrong but I think that was 00:08:49.500 --> 00:08:52.009 align:start position:0% don't get me wrong but I think that was a<00:08:49.680> big<00:08:49.800> deal<00:08:49.980> that<00:08:50.399> that<00:08:50.820> would<00:08:51.060> have<00:08:51.180> helped 00:08:52.009 --> 00:08:52.019 align:start position:0% a big deal that that would have helped 00:08:52.019 --> 00:08:54.110 align:start position:0% a big deal that that would have helped to<00:08:52.320> bring<00:08:52.440> that<00:08:52.680> forward<00:08:52.920> and<00:08:53.459> then<00:08:53.580> have<00:08:53.820> more 00:08:54.110 --> 00:08:54.120 align:start position:0% to bring that forward and then have more 00:08:54.120 --> 00:08:56.630 align:start position:0% to bring that forward and then have more time<00:08:54.360> on<00:08:54.720> things<00:08:55.380> like<00:08:55.680> being<00:08:56.160> able<00:08:56.339> to<00:08:56.459> pay 00:08:56.630 --> 00:08:56.640 align:start position:0% time on things like being able to pay 00:08:56.640 --> 00:08:58.190 align:start position:0% time on things like being able to pay real<00:08:56.820> attention<00:08:57.180> to<00:08:57.360> the<00:08:57.480> hive<00:08:57.600> test<00:08:57.839> we<00:08:58.080> were 00:08:58.190 --> 00:08:58.200 align:start position:0% real attention to the hive test we were 00:08:58.200 --> 00:08:59.750 align:start position:0% real attention to the hive test we were struggling<00:08:58.500> as<00:08:58.680> client<00:08:58.980> developers<00:08:59.459> to<00:08:59.640> keep 00:08:59.750 --> 00:08:59.760 align:start position:0% struggling as client developers to keep 00:08:59.760 --> 00:09:00.949 align:start position:0% struggling as client developers to keep up<00:08:59.940> with<00:09:00.120> the<00:09:00.300> sport<00:09:00.420> and<00:09:00.660> the<00:09:00.779> last<00:09:00.839> minute 00:09:00.949 --> 00:09:00.959 align:start position:0% up with the sport and the last minute 00:09:00.959 --> 00:09:03.710 align:start position:0% up with the sport and the last minute things<00:09:01.260> we<00:09:01.380> knew<00:09:01.620> about<00:09:01.880> and<00:09:02.880> dealing<00:09:03.600> with 00:09:03.710 --> 00:09:03.720 align:start position:0% things we knew about and dealing with 00:09:03.720 --> 00:09:05.449 align:start position:0% things we knew about and dealing with these<00:09:03.959> Hive<00:09:04.140> test<00:09:04.380> reports<00:09:04.860> that<00:09:04.980> are<00:09:05.160> in<00:09:05.279> a 00:09:05.449 --> 00:09:05.459 align:start position:0% these Hive test reports that are in a 00:09:05.459 --> 00:09:06.710 align:start position:0% these Hive test reports that are in a format<00:09:05.880> that<00:09:06.060> particularly<00:09:06.360> for<00:09:06.480> the<00:09:06.600> cancer 00:09:06.710 --> 00:09:06.720 align:start position:0% format that particularly for the cancer 00:09:06.720 --> 00:09:08.269 align:start position:0% format that particularly for the cancer consensus<00:09:07.320> side<00:09:07.440> we<00:09:07.680> weren't<00:09:07.800> particularly 00:09:08.269 --> 00:09:08.279 align:start position:0% consensus side we weren't particularly 00:09:08.279 --> 00:09:13.090 align:start position:0% consensus side we weren't particularly familiar<00:09:08.640> with 00:09:13.090 --> 00:09:13.100 align:start position:0% 00:09:13.100 --> 00:09:16.070 align:start position:0% thank<00:09:14.100> you<00:09:14.300> made<00:09:15.300> a<00:09:15.420> mistake<00:09:15.660> of<00:09:15.779> sitting<00:09:15.959> too 00:09:16.070 --> 00:09:16.080 align:start position:0% thank you made a mistake of sitting too 00:09:16.080 --> 00:09:19.190 align:start position:0% thank you made a mistake of sitting too close<00:09:16.200> to<00:09:16.380> age 00:09:19.190 --> 00:09:19.200 align:start position:0% 00:09:19.200 --> 00:09:20.750 align:start position:0% um<00:09:19.320> yeah<00:09:19.680> I<00:09:19.860> I<00:09:19.980> agree<00:09:20.339> it<00:09:20.519> was<00:09:20.640> really 00:09:20.750 --> 00:09:20.760 align:start position:0% um yeah I I agree it was really 00:09:20.760 --> 00:09:23.570 align:start position:0% um yeah I I agree it was really stressful<00:09:21.120> very<00:09:21.600> very<00:09:21.720> stressful<00:09:22.200> four<00:09:22.620> years 00:09:23.570 --> 00:09:23.580 align:start position:0% stressful very very stressful four years 00:09:23.580 --> 00:09:24.769 align:start position:0% stressful very very stressful four years um<00:09:23.640> I<00:09:23.760> think<00:09:23.880> a<00:09:24.060> large<00:09:24.180> part<00:09:24.420> of<00:09:24.540> it<00:09:24.660> was 00:09:24.769 --> 00:09:24.779 align:start position:0% um I think a large part of it was 00:09:24.779 --> 00:09:26.090 align:start position:0% um I think a large part of it was figuring<00:09:25.320> out<00:09:25.380> how<00:09:25.500> to<00:09:25.620> deal<00:09:25.740> with<00:09:25.860> that<00:09:25.980> and 00:09:26.090 --> 00:09:26.100 align:start position:0% figuring out how to deal with that and 00:09:26.100 --> 00:09:28.670 align:start position:0% figuring out how to deal with that and how<00:09:26.279> to<00:09:26.600> keep<00:09:27.600> performing<00:09:28.080> and<00:09:28.440> keep 00:09:28.670 --> 00:09:28.680 align:start position:0% how to keep performing and keep 00:09:28.680 --> 00:09:31.670 align:start position:0% how to keep performing and keep delivering<00:09:29.220> good<00:09:29.459> code<00:09:29.720> uh<00:09:30.720> not<00:09:31.200> sure<00:09:31.380> what<00:09:31.560> to 00:09:31.670 --> 00:09:31.680 align:start position:0% delivering good code uh not sure what to 00:09:31.680 --> 00:09:33.110 align:start position:0% delivering good code uh not sure what to do<00:09:31.860> about<00:09:31.980> that 00:09:33.110 --> 00:09:33.120 align:start position:0% do about that 00:09:33.120 --> 00:09:35.329 align:start position:0% do about that um perhaps<00:09:33.540> having<00:09:33.839> gone<00:09:34.140> through<00:09:34.380> it<00:09:34.620> once 00:09:35.329 --> 00:09:35.339 align:start position:0% um perhaps having gone through it once 00:09:35.339 --> 00:09:37.190 align:start position:0% um perhaps having gone through it once then<00:09:35.760> these<00:09:36.300> group<00:09:36.480> of<00:09:36.660> clients<00:09:36.959> will<00:09:37.080> be 00:09:37.190 --> 00:09:37.200 align:start position:0% then these group of clients will be 00:09:37.200 --> 00:09:39.590 align:start position:0% then these group of clients will be better<00:09:37.320> at<00:09:37.500> doing<00:09:37.680> it<00:09:37.860> again 00:09:39.590 --> 00:09:39.600 align:start position:0% better at doing it again 00:09:39.600 --> 00:09:42.170 align:start position:0% better at doing it again um<00:09:39.660> I<00:09:40.140> think<00:09:40.260> it<00:09:40.380> was<00:09:40.500> interesting<00:09:40.980> to<00:09:41.459> see<00:09:41.640> how 00:09:42.170 --> 00:09:42.180 align:start position:0% um I think it was interesting to see how 00:09:42.180 --> 00:09:44.810 align:start position:0% um I think it was interesting to see how they<00:09:42.720> were<00:09:42.899> kind<00:09:43.140> of<00:09:43.680> um<00:09:43.740> like<00:09:44.220> a<00:09:44.399> few<00:09:44.580> little 00:09:44.810 --> 00:09:44.820 align:start position:0% they were kind of um like a few little 00:09:44.820 --> 00:09:46.430 align:start position:0% they were kind of um like a few little efforts<00:09:45.300> or<00:09:45.420> a<00:09:45.600> few<00:09:45.660> people<00:09:45.839> that<00:09:46.140> kind<00:09:46.320> of 00:09:46.430 --> 00:09:46.440 align:start position:0% efforts or a few people that kind of 00:09:46.440 --> 00:09:48.769 align:start position:0% efforts or a few people that kind of poked<00:09:46.800> up<00:09:46.860> and<00:09:47.160> really<00:09:47.339> pushed<00:09:47.640> things<00:09:47.760> along 00:09:48.769 --> 00:09:48.779 align:start position:0% poked up and really pushed things along 00:09:48.779 --> 00:09:51.050 align:start position:0% poked up and really pushed things along um<00:09:48.839> I<00:09:48.959> think<00:09:49.080> Parry<00:09:49.500> was<00:09:49.680> really<00:09:49.860> helpful 00:09:51.050 --> 00:09:51.060 align:start position:0% um I think Parry was really helpful 00:09:51.060 --> 00:09:55.009 align:start position:0% um I think Parry was really helpful um uh<00:09:51.959> I<00:09:52.140> think<00:09:52.320> uh<00:09:52.860> Marius<00:09:53.279> also<00:09:53.899> managed<00:09:54.899> to 00:09:55.009 --> 00:09:55.019 align:start position:0% um uh I think uh Marius also managed to 00:09:55.019 --> 00:09:56.870 align:start position:0% um uh I think uh Marius also managed to create<00:09:55.140> a<00:09:55.320> lot<00:09:55.380> of<00:09:55.560> momentum<00:09:55.980> so<00:09:56.580> I<00:09:56.700> think 00:09:56.870 --> 00:09:56.880 align:start position:0% create a lot of momentum so I think 00:09:56.880 --> 00:09:59.150 align:start position:0% create a lot of momentum so I think there's<00:09:57.000> a<00:09:57.180> lot<00:09:57.240> to<00:09:57.360> be<00:09:57.540> said<00:09:57.660> about 00:09:59.150 --> 00:09:59.160 align:start position:0% there's a lot to be said about 00:09:59.160 --> 00:10:01.250 align:start position:0% there's a lot to be said about um<00:09:59.279> yeah<00:09:59.820> just<00:10:00.060> I<00:10:00.420> think<00:10:00.540> the<00:10:00.720> right<00:10:00.839> person<00:10:01.019> at 00:10:01.250 --> 00:10:01.260 align:start position:0% um yeah just I think the right person at 00:10:01.260 --> 00:10:02.449 align:start position:0% um yeah just I think the right person at the<00:10:01.380> right<00:10:01.500> time<00:10:01.620> relieving<00:10:02.160> the<00:10:02.279> right 00:10:02.449 --> 00:10:02.459 align:start position:0% the right time relieving the right 00:10:02.459 --> 00:10:04.250 align:start position:0% the right time relieving the right pressure<00:10:02.820> point<00:10:03.120> so 00:10:04.250 --> 00:10:04.260 align:start position:0% pressure point so 00:10:04.260 --> 00:10:05.990 align:start position:0% pressure point so I<00:10:04.680> don't<00:10:04.800> know<00:10:04.920> what<00:10:05.040> we<00:10:05.160> can<00:10:05.279> do<00:10:05.399> to<00:10:05.640> to<00:10:05.640> make 00:10:05.990 --> 00:10:06.000 align:start position:0% I don't know what we can do to to make 00:10:06.000 --> 00:10:07.490 align:start position:0% I don't know what we can do to to make that<00:10:06.120> happen<00:10:06.300> more<00:10:06.540> in<00:10:06.720> the<00:10:06.839> future<00:10:06.899> but<00:10:07.200> those 00:10:07.490 --> 00:10:07.500 align:start position:0% that happen more in the future but those 00:10:07.500 --> 00:10:09.350 align:start position:0% that happen more in the future but those yeah<00:10:08.040> those<00:10:08.339> individuals<00:10:08.760> should<00:10:08.940> be<00:10:09.000> enabled 00:10:09.350 --> 00:10:09.360 align:start position:0% yeah those individuals should be enabled 00:10:09.360 --> 00:10:10.490 align:start position:0% yeah those individuals should be enabled when<00:10:09.480> they<00:10:09.600> want<00:10:09.720> to<00:10:09.839> when<00:10:09.959> they<00:10:10.140> want<00:10:10.200> to<00:10:10.320> do 00:10:10.490 --> 00:10:10.500 align:start position:0% when they want to when they want to do 00:10:10.500 --> 00:10:11.810 align:start position:0% when they want to when they want to do something 00:10:11.810 --> 00:10:11.820 align:start position:0% something 00:10:11.820 --> 00:10:13.730 align:start position:0% something um<00:10:11.940> I<00:10:12.240> think<00:10:12.360> it<00:10:12.480> went<00:10:12.600> really<00:10:12.779> well 00:10:13.730 --> 00:10:13.740 align:start position:0% um I think it went really well 00:10:13.740 --> 00:10:15.829 align:start position:0% um I think it went really well um<00:10:13.800> I<00:10:13.980> have<00:10:14.160> been<00:10:14.399> quite<00:10:15.000> disappointed<00:10:15.480> with 00:10:15.829 --> 00:10:15.839 align:start position:0% um I have been quite disappointed with 00:10:15.839 --> 00:10:17.990 align:start position:0% um I have been quite disappointed with Mev<00:10:16.620> since 00:10:17.990 --> 00:10:18.000 align:start position:0% Mev since 00:10:18.000 --> 00:10:19.430 align:start position:0% Mev since um<00:10:18.060> since<00:10:18.360> it's<00:10:18.540> launched<00:10:18.899> I<00:10:19.080> know<00:10:19.200> there's 00:10:19.430 --> 00:10:19.440 align:start position:0% um since it's launched I know there's 00:10:19.440 --> 00:10:21.650 align:start position:0% um since it's launched I know there's been<00:10:19.680> with<00:10:20.040> some<00:10:20.279> of<00:10:20.459> the<00:10:20.820> implementations 00:10:21.650 --> 00:10:21.660 align:start position:0% been with some of the implementations 00:10:21.660 --> 00:10:23.030 align:start position:0% been with some of the implementations there<00:10:21.959> there's<00:10:22.140> been<00:10:22.260> some<00:10:22.440> bugs<00:10:22.740> that<00:10:22.860> we 00:10:23.030 --> 00:10:23.040 align:start position:0% there there's been some bugs that we 00:10:23.040 --> 00:10:25.370 align:start position:0% there there's been some bugs that we that<00:10:23.399> with<00:10:23.880> like<00:10:24.000> Json<00:10:24.300> encoding<00:10:24.839> that<00:10:25.019> really 00:10:25.370 --> 00:10:25.380 align:start position:0% that with like Json encoding that really 00:10:25.380 --> 00:10:28.009 align:start position:0% that with like Json encoding that really really<00:10:25.920> shouldn't<00:10:26.399> have<00:10:26.519> hit<00:10:26.700> us<00:10:26.880> on<00:10:27.060> mainnet 00:10:28.009 --> 00:10:28.019 align:start position:0% really shouldn't have hit us on mainnet 00:10:28.019 --> 00:10:29.090 align:start position:0% really shouldn't have hit us on mainnet um 00:10:29.090 --> 00:10:29.100 align:start position:0% um 00:10:29.100 --> 00:10:33.410 align:start position:0% um I<00:10:29.760> think<00:10:29.940> it's<00:10:30.779> probably<00:10:30.959> because<00:10:31.260> Mev 00:10:33.410 --> 00:10:33.420 align:start position:0% I think it's probably because Mev 00:10:33.420 --> 00:10:34.970 align:start position:0% I think it's probably because Mev um<00:10:33.600> like<00:10:34.080> we<00:10:34.200> all<00:10:34.380> kind<00:10:34.500> of<00:10:34.620> realize<00:10:34.860> that 00:10:34.970 --> 00:10:34.980 align:start position:0% um like we all kind of realize that 00:10:34.980 --> 00:10:37.009 align:start position:0% um like we all kind of realize that that's<00:10:35.160> a<00:10:35.339> thing<00:10:35.459> is<00:10:35.640> happening<00:10:36.060> quite<00:10:36.779> close 00:10:37.009 --> 00:10:37.019 align:start position:0% that's a thing is happening quite close 00:10:37.019 --> 00:10:38.329 align:start position:0% that's a thing is happening quite close to<00:10:37.200> the<00:10:37.320> merge<00:10:37.620> didn't<00:10:37.860> quite<00:10:37.980> get<00:10:38.160> enough 00:10:38.329 --> 00:10:38.339 align:start position:0% to the merge didn't quite get enough 00:10:38.339 --> 00:10:40.670 align:start position:0% to the merge didn't quite get enough time<00:10:38.580> to<00:10:38.880> run<00:10:39.000> with<00:10:39.180> it<00:10:39.300> didn't<00:10:39.540> get<00:10:39.839> enough 00:10:40.670 --> 00:10:40.680 align:start position:0% time to run with it didn't get enough 00:10:40.680 --> 00:10:42.530 align:start position:0% time to run with it didn't get enough time<00:10:40.980> for<00:10:41.160> it<00:10:41.279> to<00:10:41.459> be<00:10:41.640> integrated<00:10:42.120> into<00:10:42.300> our 00:10:42.530 --> 00:10:42.540 align:start position:0% time for it to be integrated into our 00:10:42.540 --> 00:10:44.030 align:start position:0% time for it to be integrated into our setups 00:10:44.030 --> 00:10:44.040 align:start position:0% setups 00:10:44.040 --> 00:10:44.750 align:start position:0% setups um 00:10:44.750 --> 00:10:44.760 align:start position:0% um 00:10:44.760 --> 00:10:47.990 align:start position:0% um I<00:10:45.360> think<00:10:45.480> there's<00:10:46.260> also<00:10:46.740> some<00:10:47.399> catching<00:10:47.940> up 00:10:47.990 --> 00:10:48.000 align:start position:0% I think there's also some catching up 00:10:48.000 --> 00:10:50.150 align:start position:0% I think there's also some catching up that<00:10:48.180> those<00:10:48.300> teams<00:10:48.540> need<00:10:48.720> to<00:10:48.839> do<00:10:48.959> in<00:10:49.140> terms<00:10:49.440> of 00:10:50.150 --> 00:10:50.160 align:start position:0% that those teams need to do in terms of 00:10:50.160 --> 00:10:51.829 align:start position:0% that those teams need to do in terms of um<00:10:50.220> announcements<00:10:50.940> and<00:10:51.060> cons<00:10:51.240> so<00:10:51.600> if<00:10:51.720> they 00:10:51.829 --> 00:10:51.839 align:start position:0% um announcements and cons so if they 00:10:51.839 --> 00:10:53.509 align:start position:0% um announcements and cons so if they have<00:10:52.019> failures 00:10:53.509 --> 00:10:53.519 align:start position:0% have failures 00:10:53.519 --> 00:10:55.370 align:start position:0% have failures um<00:10:53.579> with<00:10:54.360> their<00:10:54.540> software<00:10:54.839> they<00:10:55.079> need<00:10:55.260> to 00:10:55.370 --> 00:10:55.380 align:start position:0% um with their software they need to 00:10:55.380 --> 00:10:56.630 align:start position:0% um with their software they need to announce<00:10:55.680> it<00:10:55.860> they<00:10:55.980> need<00:10:56.160> to<00:10:56.220> tell<00:10:56.399> people 00:10:56.630 --> 00:10:56.640 align:start position:0% announce it they need to tell people 00:10:56.640 --> 00:10:58.490 align:start position:0% announce it they need to tell people instantly<00:10:57.360> that<00:10:57.660> there<00:10:57.899> is<00:10:58.019> a<00:10:58.200> problem<00:10:58.320> and 00:10:58.490 --> 00:10:58.500 align:start position:0% instantly that there is a problem and 00:10:58.500 --> 00:11:00.350 align:start position:0% instantly that there is a problem and it's<00:10:58.680> being<00:10:58.800> looked<00:10:59.040> into<00:10:59.160> not<00:10:59.519> sit<00:10:59.940> on<00:11:00.120> it<00:11:00.240> for 00:11:00.350 --> 00:11:00.360 align:start position:0% it's being looked into not sit on it for 00:11:00.360 --> 00:11:02.329 align:start position:0% it's being looked into not sit on it for some<00:11:00.540> time<00:11:00.720> and<00:11:00.959> then<00:11:01.140> and<00:11:01.800> then<00:11:01.980> and<00:11:02.100> then 00:11:02.329 --> 00:11:02.339 align:start position:0% some time and then and then and then 00:11:02.339 --> 00:11:05.090 align:start position:0% some time and then and then and then publish<00:11:02.700> it<00:11:02.880> do<00:11:03.540> I<00:11:03.779> was<00:11:04.320> really<00:11:04.560> happy<00:11:04.800> to 00:11:05.090 --> 00:11:05.100 align:start position:0% publish it do I was really happy to 00:11:05.100 --> 00:11:06.650 align:start position:0% publish it do I was really happy to actually<00:11:05.279> we<00:11:05.700> we<00:11:05.880> almost<00:11:06.180> launched<00:11:06.540> in 00:11:06.650 --> 00:11:06.660 align:start position:0% actually we we almost launched in 00:11:06.660 --> 00:11:09.650 align:start position:0% actually we we almost launched in October<00:11:07.140> so<00:11:07.500> just<00:11:08.100> the<00:11:08.279> next<00:11:08.459> year 00:11:09.650 --> 00:11:09.660 align:start position:0% October so just the next year 00:11:09.660 --> 00:11:11.389 align:start position:0% October so just the next year um 00:11:11.389 --> 00:11:11.399 align:start position:0% um 00:11:11.399 --> 00:11:14.090 align:start position:0% um so<00:11:12.060> but<00:11:12.480> then<00:11:12.660> I<00:11:12.839> came<00:11:12.959> back<00:11:13.200> to<00:11:13.440> the<00:11:13.680> like 00:11:14.090 --> 00:11:14.100 align:start position:0% so but then I came back to the like 00:11:14.100 --> 00:11:16.190 align:start position:0% so but then I came back to the like after<00:11:14.339> I<00:11:14.579> said<00:11:14.700> that<00:11:14.880> I<00:11:15.060> was<00:11:15.180> like<00:11:15.300> yeah<00:11:15.899> maybe 00:11:16.190 --> 00:11:16.200 align:start position:0% after I said that I was like yeah maybe 00:11:16.200 --> 00:11:18.170 align:start position:0% after I said that I was like yeah maybe maybe<00:11:16.440> it<00:11:16.680> was<00:11:16.860> not<00:11:17.040> really<00:11:17.339> the<00:11:18.000> common 00:11:18.170 --> 00:11:18.180 align:start position:0% maybe it was not really the common 00:11:18.180 --> 00:11:20.449 align:start position:0% maybe it was not really the common agreement<00:11:18.600> the<00:11:18.839> common<00:11:18.959> sense<00:11:19.320> and<00:11:20.160> I<00:11:20.279> came 00:11:20.449 --> 00:11:20.459 align:start position:0% agreement the common sense and I came 00:11:20.459 --> 00:11:22.190 align:start position:0% agreement the common sense and I came back<00:11:20.640> today<00:11:20.940> to<00:11:21.420> the<00:11:21.540> Netherlands<00:11:22.019> team 00:11:22.190 --> 00:11:22.200 align:start position:0% back today to the Netherlands team 00:11:22.200 --> 00:11:24.050 align:start position:0% back today to the Netherlands team asking<00:11:22.620> everyone<00:11:22.800> hey<00:11:23.399> do<00:11:23.640> you<00:11:23.640> think<00:11:23.760> I<00:11:23.940> can 00:11:24.050 --> 00:11:24.060 align:start position:0% asking everyone hey do you think I can 00:11:24.060 --> 00:11:25.790 align:start position:0% asking everyone hey do you think I can do<00:11:24.180> that<00:11:24.300> for<00:11:24.480> October<00:11:24.899> like<00:11:25.200> you<00:11:25.440> think<00:11:25.620> it's 00:11:25.790 --> 00:11:25.800 align:start position:0% do that for October like you think it's 00:11:25.800 --> 00:11:28.310 align:start position:0% do that for October like you think it's possible<00:11:26.100> at<00:11:26.279> least<00:11:26.339> do<00:11:26.640> I<00:11:26.820> have<00:11:26.940> to<00:11:27.060> go<00:11:28.019> and 00:11:28.310 --> 00:11:28.320 align:start position:0% possible at least do I have to go and 00:11:28.320 --> 00:11:30.530 align:start position:0% possible at least do I have to go and just<00:11:28.560> like<00:11:28.800> tell<00:11:29.459> everyone<00:11:29.640> hey<00:11:30.000> I<00:11:30.180> was<00:11:30.300> wrong 00:11:30.530 --> 00:11:30.540 align:start position:0% just like tell everyone hey I was wrong 00:11:30.540 --> 00:11:33.190 align:start position:0% just like tell everyone hey I was wrong and<00:11:31.200> they<00:11:31.320> said<00:11:31.500> no<00:11:31.680> we<00:11:31.920> think<00:11:32.220> it's<00:11:32.459> possible 00:11:33.190 --> 00:11:33.200 align:start position:0% and they said no we think it's possible 00:11:33.200 --> 00:11:37.430 align:start position:0% and they said no we think it's possible so<00:11:34.200> I<00:11:34.500> thought<00:11:34.680> okay<00:11:35.160> yeah<00:11:35.579> and<00:11:36.240> well<00:11:37.079> there 00:11:37.430 --> 00:11:37.440 align:start position:0% so I thought okay yeah and well there 00:11:37.440 --> 00:11:39.110 align:start position:0% so I thought okay yeah and well there was<00:11:37.620> there<00:11:37.980> was<00:11:38.160> a<00:11:38.279> lot<00:11:38.339> of<00:11:38.459> work<00:11:38.579> but<00:11:38.880> at<00:11:39.000> the 00:11:39.110 --> 00:11:39.120 align:start position:0% was there was a lot of work but at the 00:11:39.120 --> 00:11:40.490 align:start position:0% was there was a lot of work but at the same<00:11:39.180> time<00:11:39.360> I<00:11:39.480> remember<00:11:39.660> thinking<00:11:40.140> on<00:11:40.320> the 00:11:40.490 --> 00:11:40.500 align:start position:0% same time I remember thinking on the 00:11:40.500 --> 00:11:42.769 align:start position:0% same time I remember thinking on the same<00:11:40.620> day<00:11:40.800> I<00:11:41.579> think<00:11:41.640> it<00:11:41.820> was<00:11:41.940> good<00:11:42.180> to<00:11:42.420> say<00:11:42.540> it 00:11:42.769 --> 00:11:42.779 align:start position:0% same day I think it was good to say it 00:11:42.779 --> 00:11:44.930 align:start position:0% same day I think it was good to say it because<00:11:43.079> suddenly<00:11:43.920> all<00:11:44.220> the<00:11:44.399> infrastructure 00:11:44.930 --> 00:11:44.940 align:start position:0% because suddenly all the infrastructure 00:11:44.940 --> 00:11:46.910 align:start position:0% because suddenly all the infrastructure teams<00:11:45.420> started<00:11:46.019> calling<00:11:46.440> everyone<00:11:46.620> and 00:11:46.910 --> 00:11:46.920 align:start position:0% teams started calling everyone and 00:11:46.920 --> 00:11:48.350 align:start position:0% teams started calling everyone and saying<00:11:47.220> hey<00:11:47.339> like<00:11:47.579> we're<00:11:47.940> launching<00:11:48.300> in 00:11:48.350 --> 00:11:48.360 align:start position:0% saying hey like we're launching in 00:11:48.360 --> 00:11:49.910 align:start position:0% saying hey like we're launching in October<00:11:48.660> we<00:11:48.899> are<00:11:49.019> totally<00:11:49.200> unprepared<00:11:49.800> we 00:11:49.910 --> 00:11:49.920 align:start position:0% October we are totally unprepared we 00:11:49.920 --> 00:11:51.769 align:start position:0% October we are totally unprepared we have<00:11:50.040> to<00:11:50.160> start<00:11:50.339> preparing<00:11:50.940> and<00:11:51.480> it<00:11:51.660> was 00:11:51.769 --> 00:11:51.779 align:start position:0% have to start preparing and it was 00:11:51.779 --> 00:11:53.090 align:start position:0% have to start preparing and it was needed<00:11:52.079> like<00:11:52.260> because<00:11:52.440> we<00:11:52.620> needed<00:11:52.860> node 00:11:53.090 --> 00:11:53.100 align:start position:0% needed like because we needed node 00:11:53.100 --> 00:11:54.710 align:start position:0% needed like because we needed node operators<00:11:53.579> to<00:11:53.820> start<00:11:53.940> looking<00:11:54.180> at<00:11:54.480> this<00:11:54.600> we 00:11:54.710 --> 00:11:54.720 align:start position:0% operators to start looking at this we 00:11:54.720 --> 00:11:56.269 align:start position:0% operators to start looking at this we needed<00:11:55.079> a<00:11:55.260> community<00:11:55.380> to<00:11:55.680> say<00:11:55.860> okay<00:11:56.040> there's 00:11:56.269 --> 00:11:56.279 align:start position:0% needed a community to say okay there's 00:11:56.279 --> 00:11:58.730 align:start position:0% needed a community to say okay there's some<00:11:56.459> date<00:11:56.640> for<00:11:56.940> the<00:11:57.060> first<00:11:57.180> time<00:11:57.420> uh<00:11:58.380> so<00:11:58.560> I 00:11:58.730 --> 00:11:58.740 align:start position:0% some date for the first time uh so I 00:11:58.740 --> 00:12:01.430 align:start position:0% some date for the first time uh so I miss<00:11:58.920> it<00:11:59.040> by<00:11:59.160> a<00:11:59.339> lot<00:11:59.399> but<00:11:59.640> and<00:12:00.300> then<00:12:00.420> in<00:12:00.839> Emporia 00:12:01.430 --> 00:12:01.440 align:start position:0% miss it by a lot but and then in Emporia 00:12:01.440 --> 00:12:03.370 align:start position:0% miss it by a lot but and then in Emporia yes<00:12:01.620> I<00:12:01.860> was<00:12:02.040> still<00:12:02.160> still<00:12:02.399> very<00:12:02.640> confident 00:12:03.370 --> 00:12:03.380 align:start position:0% yes I was still still very confident 00:12:03.380 --> 00:12:05.569 align:start position:0% yes I was still still very confident because<00:12:04.380> I<00:12:04.800> I've<00:12:05.160> seen<00:12:05.339> the<00:12:05.459> things 00:12:05.569 --> 00:12:05.579 align:start position:0% because I I've seen the things 00:12:05.579 --> 00:12:07.430 align:start position:0% because I I've seen the things progressing<00:12:06.060> I've<00:12:06.360> seen<00:12:06.540> the<00:12:06.720> the<00:12:06.899> Ryan<00:12:07.140> is 00:12:07.430 --> 00:12:07.440 align:start position:0% progressing I've seen the the Ryan is 00:12:07.440 --> 00:12:09.470 align:start position:0% progressing I've seen the the Ryan is hitting<00:12:08.220> very<00:12:08.399> fast<00:12:08.579> but<00:12:08.880> it<00:12:08.940> was<00:12:09.120> like<00:12:09.240> all 00:12:09.470 --> 00:12:09.480 align:start position:0% hitting very fast but it was like all 00:12:09.480 --> 00:12:11.329 align:start position:0% hitting very fast but it was like all those<00:12:09.720> small<00:12:10.320> things<00:12:10.620> that<00:12:10.920> take<00:12:11.100> so<00:12:11.279> much 00:12:11.329 --> 00:12:11.339 align:start position:0% those small things that take so much 00:12:11.339 --> 00:12:13.850 align:start position:0% those small things that take so much much<00:12:11.760> time<00:12:12.060> really<00:12:12.720> in<00:12:13.019> the<00:12:13.200> testing<00:12:13.500> and<00:12:13.680> the 00:12:13.850 --> 00:12:13.860 align:start position:0% much time really in the testing and the 00:12:13.860 --> 00:12:15.790 align:start position:0% much time really in the testing and the proper<00:12:14.100> testing<00:12:14.399> and<00:12:14.579> the<00:12:14.760> confidence 00:12:15.790 --> 00:12:15.800 align:start position:0% proper testing and the confidence 00:12:15.800 --> 00:12:19.009 align:start position:0% proper testing and the confidence and<00:12:16.800> I<00:12:16.980> think<00:12:17.160> when<00:12:17.579> I<00:12:17.760> was<00:12:17.880> a<00:12:18.120> bit<00:12:18.240> pessimistic 00:12:19.009 --> 00:12:19.019 align:start position:0% and I think when I was a bit pessimistic 00:12:19.019 --> 00:12:22.370 align:start position:0% and I think when I was a bit pessimistic was<00:12:19.200> around<00:12:19.440> April<00:12:19.860> this<00:12:20.100> year<00:12:20.480> when<00:12:21.480> I 00:12:22.370 --> 00:12:22.380 align:start position:0% was around April this year when I 00:12:22.380 --> 00:12:24.530 align:start position:0% was around April this year when I when<00:12:22.860> we<00:12:23.100> were<00:12:23.279> thinking<00:12:23.700> about<00:12:23.820> Mev<00:12:24.300> boost 00:12:24.530 --> 00:12:24.540 align:start position:0% when we were thinking about Mev boost 00:12:24.540 --> 00:12:26.389 align:start position:0% when we were thinking about Mev boost and<00:12:24.839> how<00:12:25.079> ready<00:12:25.200> a<00:12:25.440> movie<00:12:25.560> boost<00:12:25.800> is<00:12:26.100> and<00:12:26.220> how 00:12:26.389 --> 00:12:26.399 align:start position:0% and how ready a movie boost is and how 00:12:26.399 --> 00:12:28.550 align:start position:0% and how ready a movie boost is and how much<00:12:26.579> everybody<00:12:27.180> was<00:12:27.600> prepared<00:12:27.959> for<00:12:28.140> Mev 00:12:28.550 --> 00:12:28.560 align:start position:0% much everybody was prepared for Mev 00:12:28.560 --> 00:12:31.490 align:start position:0% much everybody was prepared for Mev burst<00:12:28.980> and<00:12:29.399> it<00:12:29.820> was<00:12:30.060> more<00:12:30.300> stressed<00:12:31.200> at<00:12:31.320> the 00:12:31.490 --> 00:12:31.500 align:start position:0% burst and it was more stressed at the 00:12:31.500 --> 00:12:33.769 align:start position:0% burst and it was more stressed at the time<00:12:31.620> about<00:12:31.920> will<00:12:32.640> we<00:12:32.880> have<00:12:33.000> a<00:12:33.060> movie<00:12:33.240> burst<00:12:33.660> on 00:12:33.769 --> 00:12:33.779 align:start position:0% time about will we have a movie burst on 00:12:33.779 --> 00:12:35.269 align:start position:0% time about will we have a movie burst on time<00:12:33.959> or<00:12:34.260> will<00:12:34.440> we<00:12:34.620> have<00:12:34.740> to<00:12:34.800> launch<00:12:35.040> without 00:12:35.269 --> 00:12:35.279 align:start position:0% time or will we have to launch without 00:12:35.279 --> 00:12:37.130 align:start position:0% time or will we have to launch without any<00:12:35.579> Rebus<00:12:35.940> because<00:12:36.180> at<00:12:36.540> the<00:12:36.720> time<00:12:36.839> we<00:12:36.959> were 00:12:37.130 --> 00:12:37.140 align:start position:0% any Rebus because at the time we were 00:12:37.140 --> 00:12:40.250 align:start position:0% any Rebus because at the time we were thinking<00:12:37.440> of<00:12:37.800> June<00:12:38.760> or<00:12:38.880> May<00:12:39.120> as<00:12:39.420> a<00:12:39.600> launch<00:12:40.079> date 00:12:40.250 --> 00:12:40.260 align:start position:0% thinking of June or May as a launch date 00:12:40.260 --> 00:12:43.370 align:start position:0% thinking of June or May as a launch date for<00:12:40.560> a<00:12:40.680> movie<00:12:40.860> a<00:12:41.519> for<00:12:41.820> for<00:12:42.000> the<00:12:42.180> merge<00:12:42.540> so 00:12:43.370 --> 00:12:43.380 align:start position:0% for a movie a for for the merge so 00:12:43.380 --> 00:12:45.290 align:start position:0% for a movie a for for the merge so everything<00:12:43.920> came<00:12:44.220> together<00:12:44.459> around 00:12:45.290 --> 00:12:45.300 align:start position:0% everything came together around 00:12:45.300 --> 00:12:47.870 align:start position:0% everything came together around September<00:12:46.279> I<00:12:47.279> definitely<00:12:47.519> didn't<00:12:47.639> want 00:12:47.870 --> 00:12:47.880 align:start position:0% September I definitely didn't want 00:12:47.880 --> 00:12:49.190 align:start position:0% September I definitely didn't want people<00:12:48.120> to 00:12:49.190 --> 00:12:49.200 align:start position:0% people to 00:12:49.200 --> 00:12:52.009 align:start position:0% people to does<00:12:49.860> it<00:12:50.100> say<00:12:50.279> to<00:12:50.760> use<00:12:50.880> this<00:12:51.120> difficulty<00:12:51.720> bomb 00:12:52.009 --> 00:12:52.019 align:start position:0% does it say to use this difficulty bomb 00:12:52.019 --> 00:12:54.590 align:start position:0% does it say to use this difficulty bomb thing<00:12:52.380> as<00:12:52.800> a<00:12:53.100> as<00:12:53.760> something<00:12:54.000> that<00:12:54.240> would<00:12:54.360> drive 00:12:54.590 --> 00:12:54.600 align:start position:0% thing as a as something that would drive 00:12:54.600 --> 00:12:58.490 align:start position:0% thing as a as something that would drive the<00:12:54.839> dates<00:12:55.079> uh<00:12:56.040> talking<00:12:56.760> to<00:12:57.000> developers<00:12:57.600> to 00:12:58.490 --> 00:12:58.500 align:start position:0% the dates uh talking to developers to 00:12:58.500 --> 00:13:01.069 align:start position:0% the dates uh talking to developers to our<00:12:58.800> team<00:12:59.100> I<00:12:59.760> feel<00:12:59.880> like<00:13:00.060> there's<00:13:00.480> really<00:13:00.720> no 00:13:01.069 --> 00:13:01.079 align:start position:0% our team I feel like there's really no 00:13:01.079 --> 00:13:02.990 align:start position:0% our team I feel like there's really no more<00:13:01.260> motivation<00:13:01.740> you<00:13:02.100> can<00:13:02.220> get<00:13:02.399> or<00:13:02.700> no<00:13:02.880> more 00:13:02.990 --> 00:13:03.000 align:start position:0% more motivation you can get or no more 00:13:03.000 --> 00:13:05.389 align:start position:0% more motivation you can get or no more pushing<00:13:03.420> or<00:13:03.660> or<00:13:04.019> shouting<00:13:04.620> or<00:13:04.800> asking<00:13:05.220> that 00:13:05.389 --> 00:13:05.399 align:start position:0% pushing or or shouting or asking that 00:13:05.399 --> 00:13:07.129 align:start position:0% pushing or or shouting or asking that you<00:13:05.519> could<00:13:05.700> get<00:13:05.820> for<00:13:06.060> delivery<00:13:06.420> on<00:13:06.540> time<00:13:06.720> so 00:13:07.129 --> 00:13:07.139 align:start position:0% you could get for delivery on time so 00:13:07.139 --> 00:13:08.569 align:start position:0% you could get for delivery on time so there's<00:13:07.320> absolutely<00:13:07.680> no<00:13:07.860> sense<00:13:08.040> to<00:13:08.220> introduce 00:13:08.569 --> 00:13:08.579 align:start position:0% there's absolutely no sense to introduce 00:13:08.579 --> 00:13:11.030 align:start position:0% there's absolutely no sense to introduce any<00:13:08.760> other<00:13:08.940> stressor<00:13:09.540> so<00:13:09.839> so<00:13:10.260> the<00:13:10.560> difficulty 00:13:11.030 --> 00:13:11.040 align:start position:0% any other stressor so so the difficulty 00:13:11.040 --> 00:13:13.730 align:start position:0% any other stressor so so the difficulty bombing<00:13:11.459> moved<00:13:11.880> slightly<00:13:12.200> uh<00:13:13.200> I<00:13:13.380> hoped<00:13:13.620> it 00:13:13.730 --> 00:13:13.740 align:start position:0% bombing moved slightly uh I hoped it 00:13:13.740 --> 00:13:16.250 align:start position:0% bombing moved slightly uh I hoped it won't<00:13:13.860> move<00:13:14.100> the<00:13:14.339> merge<00:13:14.700> date<00:13:14.899> and<00:13:15.899> we<00:13:16.079> didn't 00:13:16.250 --> 00:13:16.260 align:start position:0% won't move the merge date and we didn't 00:13:16.260 --> 00:13:18.350 align:start position:0% won't move the merge date and we didn't so<00:13:16.980> actually<00:13:17.220> the<00:13:17.399> merge<00:13:17.700> it<00:13:17.820> wasn't<00:13:17.940> moved 00:13:18.350 --> 00:13:18.360 align:start position:0% so actually the merge it wasn't moved 00:13:18.360 --> 00:13:20.269 align:start position:0% so actually the merge it wasn't moved and<00:13:18.660> nobody<00:13:18.959> was<00:13:19.500> talking<00:13:19.680> about<00:13:19.920> the<00:13:20.160> block 00:13:20.269 --> 00:13:20.279 align:start position:0% and nobody was talking about the block 00:13:20.279 --> 00:13:22.310 align:start position:0% and nobody was talking about the block times<00:13:20.579> but<00:13:21.180> we<00:13:21.360> would<00:13:21.600> talk<00:13:21.779> about<00:13:21.959> the<00:13:22.200> block 00:13:22.310 --> 00:13:22.320 align:start position:0% times but we would talk about the block 00:13:22.320 --> 00:13:24.829 align:start position:0% times but we would talk about the block times<00:13:22.620> if<00:13:22.920> it<00:13:23.100> didn't<00:13:23.220> happens 00:13:24.829 --> 00:13:24.839 align:start position:0% times if it didn't happens 00:13:24.839 --> 00:13:26.150 align:start position:0% times if it didn't happens nice 00:13:26.150 --> 00:13:26.160 align:start position:0% nice 00:13:26.160 --> 00:13:28.190 align:start position:0% nice um<00:13:26.220> yeah<00:13:26.459> we're<00:13:26.700> focus<00:13:27.120> on<00:13:27.240> another<00:13:27.540> side<00:13:28.079> of 00:13:28.190 --> 00:13:28.200 align:start position:0% um yeah we're focus on another side of 00:13:28.200 --> 00:13:36.110 align:start position:0% um yeah we're focus on another side of the<00:13:28.320> room 00:13:36.110 --> 00:13:36.120 align:start position:0% 00:13:36.120 --> 00:13:38.389 align:start position:0% we<00:13:36.480> are<00:13:36.660> like<00:13:36.899> one<00:13:37.079> of<00:13:37.139> the<00:13:37.200> minor<00:13:37.560> clients<00:13:38.160> uh 00:13:38.389 --> 00:13:38.399 align:start position:0% we are like one of the minor clients uh 00:13:38.399 --> 00:13:40.430 align:start position:0% we are like one of the minor clients uh bezel<00:13:38.940> team<00:13:39.120> and 00:13:40.430 --> 00:13:40.440 align:start position:0% bezel team and 00:13:40.440 --> 00:13:41.269 align:start position:0% bezel team and um one<00:13:40.620> thing<00:13:40.740> I<00:13:40.860> would<00:13:40.980> have<00:13:41.100> done 00:13:41.269 --> 00:13:41.279 align:start position:0% um one thing I would have done 00:13:41.279 --> 00:13:43.069 align:start position:0% um one thing I would have done differently<00:13:41.820> was 00:13:43.069 --> 00:13:43.079 align:start position:0% differently was 00:13:43.079 --> 00:13:45.470 align:start position:0% differently was um<00:13:43.139> preparing<00:13:43.680> for<00:13:43.980> people<00:13:44.399> choosing<00:13:45.240> client 00:13:45.470 --> 00:13:45.480 align:start position:0% um preparing for people choosing client 00:13:45.480 --> 00:13:47.449 align:start position:0% um preparing for people choosing client diversity<00:13:45.959> uh<00:13:46.560> getting<00:13:46.740> ready<00:13:46.980> for<00:13:47.279> them 00:13:47.449 --> 00:13:47.459 align:start position:0% diversity uh getting ready for them 00:13:47.459 --> 00:13:49.310 align:start position:0% diversity uh getting ready for them didn't<00:13:48.000> realize<00:13:48.420> I<00:13:48.600> guess<00:13:48.720> I<00:13:49.019> think<00:13:49.079> it<00:13:49.200> was 00:13:49.310 --> 00:13:49.320 align:start position:0% didn't realize I guess I think it was 00:13:49.320 --> 00:13:51.590 align:start position:0% didn't realize I guess I think it was around<00:13:49.740> like<00:13:49.980> two<00:13:50.160> three<00:13:50.459> weeks<00:13:50.820> before<00:13:51.180> the 00:13:51.590 --> 00:13:51.600 align:start position:0% around like two three weeks before the 00:13:51.600 --> 00:13:54.350 align:start position:0% around like two three weeks before the merge<00:13:51.959> timeline<00:13:52.320> we<00:13:53.100> saw<00:13:53.279> a<00:13:53.700> huge<00:13:53.940> amount<00:13:54.240> of 00:13:54.350 --> 00:13:54.360 align:start position:0% merge timeline we saw a huge amount of 00:13:54.360 --> 00:13:57.110 align:start position:0% merge timeline we saw a huge amount of people<00:13:54.540> thanks<00:13:55.079> to<00:13:55.380> a<00:13:55.620> lot<00:13:55.800> of<00:13:55.920> solo<00:13:56.760> stickers 00:13:57.110 --> 00:13:57.120 align:start position:0% people thanks to a lot of solo stickers 00:13:57.120 --> 00:13:59.569 align:start position:0% people thanks to a lot of solo stickers coming<00:13:57.300> through<00:13:57.600> Discord<00:13:58.260> asking<00:13:59.100> tons<00:13:59.399> of 00:13:59.569 --> 00:13:59.579 align:start position:0% coming through Discord asking tons of 00:13:59.579 --> 00:14:01.910 align:start position:0% coming through Discord asking tons of questions<00:14:00.060> and<00:14:00.779> I<00:14:01.200> think<00:14:01.260> the<00:14:01.440> maintainers 00:14:01.910 --> 00:14:01.920 align:start position:0% questions and I think the maintainers 00:14:01.920 --> 00:14:04.190 align:start position:0% questions and I think the maintainers were<00:14:02.100> super<00:14:02.399> busy<00:14:02.820> with<00:14:03.360> uh<00:14:03.720> you<00:14:03.899> know<00:14:03.959> trying 00:14:04.190 --> 00:14:04.200 align:start position:0% were super busy with uh you know trying 00:14:04.200 --> 00:14:06.590 align:start position:0% were super busy with uh you know trying to<00:14:04.320> get<00:14:04.500> the<00:14:04.680> final<00:14:04.920> release<00:14:05.220> out<00:14:05.639> uh<00:14:06.360> didn't 00:14:06.590 --> 00:14:06.600 align:start position:0% to get the final release out uh didn't 00:14:06.600 --> 00:14:08.629 align:start position:0% to get the final release out uh didn't get<00:14:06.839> to<00:14:07.019> really<00:14:07.200> respond<00:14:07.620> to<00:14:07.800> a<00:14:08.160> lot<00:14:08.279> of<00:14:08.399> them 00:14:08.629 --> 00:14:08.639 align:start position:0% get to really respond to a lot of them 00:14:08.639 --> 00:14:11.030 align:start position:0% get to really respond to a lot of them so<00:14:09.360> I<00:14:09.480> think<00:14:09.600> that's<00:14:09.720> something<00:14:09.959> that<00:14:10.380> if<00:14:10.920> we 00:14:11.030 --> 00:14:11.040 align:start position:0% so I think that's something that if we 00:14:11.040 --> 00:14:13.190 align:start position:0% so I think that's something that if we had<00:14:11.160> to<00:14:11.220> go<00:14:11.339> through<00:14:11.459> the<00:14:11.639> merge<00:14:11.940> not<00:14:12.540> really 00:14:13.190 --> 00:14:13.200 align:start position:0% had to go through the merge not really 00:14:13.200 --> 00:14:14.389 align:start position:0% had to go through the merge not really um<00:14:13.260> but<00:14:13.440> if<00:14:13.500> we<00:14:13.620> had<00:14:13.740> to<00:14:13.860> go<00:14:13.920> through<00:14:14.100> it<00:14:14.220> again 00:14:14.389 --> 00:14:14.399 align:start position:0% um but if we had to go through it again 00:14:14.399 --> 00:14:17.030 align:start position:0% um but if we had to go through it again that<00:14:14.820> we<00:14:15.000> would<00:14:15.180> do<00:14:15.300> that<00:14:15.480> differently<00:14:15.959> to<00:14:16.500> be 00:14:17.030 --> 00:14:17.040 align:start position:0% that we would do that differently to be 00:14:17.040 --> 00:14:19.730 align:start position:0% that we would do that differently to be ready<00:14:17.339> for<00:14:17.880> Community<00:14:18.600> Support<00:14:19.019> how<00:14:19.440> do<00:14:19.560> we 00:14:19.730 --> 00:14:19.740 align:start position:0% ready for Community Support how do we 00:14:19.740 --> 00:14:22.129 align:start position:0% ready for Community Support how do we get<00:14:19.920> this<00:14:20.279> uh<00:14:20.700> new<00:14:21.420> users<00:14:21.720> coming<00:14:21.899> through 00:14:22.129 --> 00:14:22.139 align:start position:0% get this uh new users coming through 00:14:22.139 --> 00:14:23.569 align:start position:0% get this uh new users coming through this<00:14:22.380> ecosystem<00:14:22.740> like<00:14:23.040> how<00:14:23.160> can<00:14:23.279> we<00:14:23.399> support 00:14:23.569 --> 00:14:23.579 align:start position:0% this ecosystem like how can we support 00:14:23.579 --> 00:14:24.769 align:start position:0% this ecosystem like how can we support that<00:14:23.760> better 00:14:24.769 --> 00:14:24.779 align:start position:0% that better 00:14:24.779 --> 00:14:26.629 align:start position:0% that better um<00:14:24.839> and<00:14:25.200> but<00:14:25.560> honestly<00:14:25.920> it's<00:14:25.980> definitely<00:14:26.339> a 00:14:26.629 --> 00:14:26.639 align:start position:0% um and but honestly it's definitely a 00:14:26.639 --> 00:14:29.210 align:start position:0% um and but honestly it's definitely a hard<00:14:26.820> challenge<00:14:27.720> because<00:14:28.200> as<00:14:28.620> maintainers 00:14:29.210 --> 00:14:29.220 align:start position:0% hard challenge because as maintainers 00:14:29.220 --> 00:14:31.250 align:start position:0% hard challenge because as maintainers like<00:14:29.579> you're<00:14:30.180> really<00:14:30.420> deep<00:14:30.600> in<00:14:30.720> the<00:14:30.839> weeds<00:14:31.139> of 00:14:31.250 --> 00:14:31.260 align:start position:0% like you're really deep in the weeds of 00:14:31.260 --> 00:14:34.090 align:start position:0% like you're really deep in the weeds of like<00:14:31.560> really<00:14:31.800> trying<00:14:32.459> to<00:14:32.639> get<00:14:32.820> the<00:14:33.060> code<00:14:33.300> out 00:14:34.090 --> 00:14:34.100 align:start position:0% like really trying to get the code out 00:14:34.100 --> 00:14:37.550 align:start position:0% like really trying to get the code out on<00:14:35.100> top<00:14:35.279> of<00:14:35.459> that<00:14:35.700> trying<00:14:36.060> to<00:14:36.300> support<00:14:36.660> tons<00:14:37.440> of 00:14:37.550 --> 00:14:37.560 align:start position:0% on top of that trying to support tons of 00:14:37.560 --> 00:14:39.470 align:start position:0% on top of that trying to support tons of users<00:14:37.860> coming<00:14:38.100> through<00:14:38.339> is<00:14:38.760> uh<00:14:39.120> it's<00:14:39.360> it's 00:14:39.470 --> 00:14:39.480 align:start position:0% users coming through is uh it's it's 00:14:39.480 --> 00:14:41.629 align:start position:0% users coming through is uh it's it's really<00:14:39.779> challenging<00:14:40.199> but<00:14:40.620> thanks<00:14:41.100> to<00:14:41.339> a<00:14:41.519> lot 00:14:41.629 --> 00:14:41.639 align:start position:0% really challenging but thanks to a lot 00:14:41.639 --> 00:14:44.210 align:start position:0% really challenging but thanks to a lot of<00:14:41.760> the<00:14:42.079> contributors<00:14:43.079> who<00:14:43.320> also<00:14:43.680> chimed<00:14:44.160> in 00:14:44.210 --> 00:14:44.220 align:start position:0% of the contributors who also chimed in 00:14:44.220 --> 00:14:46.129 align:start position:0% of the contributors who also chimed in and<00:14:44.579> asked<00:14:44.940> answering<00:14:45.600> a<00:14:45.720> lot<00:14:45.839> of<00:14:45.899> other 00:14:46.129 --> 00:14:46.139 align:start position:0% and asked answering a lot of other 00:14:46.139 --> 00:14:47.990 align:start position:0% and asked answering a lot of other people's<00:14:46.860> questions<00:14:47.100> on<00:14:47.459> how<00:14:47.639> to<00:14:47.760> set<00:14:47.880> up 00:14:47.990 --> 00:14:48.000 align:start position:0% people's questions on how to set up 00:14:48.000 --> 00:14:50.389 align:start position:0% people's questions on how to set up their<00:14:48.180> validators<00:14:48.660> and<00:14:48.839> all<00:14:49.019> that<00:14:49.680> um<00:14:49.680> so<00:14:49.920> yeah 00:14:50.389 --> 00:14:50.399 align:start position:0% their validators and all that um so yeah 00:14:50.399 --> 00:14:52.310 align:start position:0% their validators and all that um so yeah it's<00:14:50.579> definitely<00:14:50.880> a<00:14:51.420> community<00:14:51.600> effort<00:14:52.139> it's 00:14:52.310 --> 00:14:52.320 align:start position:0% it's definitely a community effort it's 00:14:52.320 --> 00:14:54.710 align:start position:0% it's definitely a community effort it's not<00:14:52.500> just<00:14:52.740> the<00:14:53.040> maintainers<00:14:53.820> all<00:14:54.060> core<00:14:54.300> devs 00:14:54.710 --> 00:14:54.720 align:start position:0% not just the maintainers all core devs 00:14:54.720 --> 00:14:56.629 align:start position:0% not just the maintainers all core devs so<00:14:55.079> thank<00:14:55.260> you<00:14:55.380> for<00:14:55.560> those<00:14:55.800> uh<00:14:56.040> solo<00:14:56.339> stickers 00:14:56.629 --> 00:14:56.639 align:start position:0% so thank you for those uh solo stickers 00:14:56.639 --> 00:14:58.250 align:start position:0% so thank you for those uh solo stickers coming<00:14:56.820> in<00:14:57.000> and<00:14:57.240> asking<00:14:57.600> questions<00:14:57.779> and 00:14:58.250 --> 00:14:58.260 align:start position:0% coming in and asking questions and 00:14:58.260 --> 00:15:00.050 align:start position:0% coming in and asking questions and really<00:14:58.620> improving<00:14:59.100> the<00:14:59.279> client<00:14:59.579> diversity 00:15:00.050 --> 00:15:00.060 align:start position:0% really improving the client diversity 00:15:00.060 --> 00:15:02.509 align:start position:0% really improving the client diversity and<00:15:00.420> also<00:15:00.779> other<00:15:01.019> contributors<00:15:01.620> supporting 00:15:02.509 --> 00:15:02.519 align:start position:0% and also other contributors supporting 00:15:02.519 --> 00:15:05.750 align:start position:0% and also other contributors supporting each<00:15:02.639> other<00:15:02.760> so<00:15:03.240> yeah<00:15:04.199> thank<00:15:04.560> you<00:15:04.680> for<00:15:05.040> that 00:15:05.750 --> 00:15:05.760 align:start position:0% each other so yeah thank you for that 00:15:05.760 --> 00:15:07.670 align:start position:0% each other so yeah thank you for that um I<00:15:06.120> guess<00:15:06.240> one<00:15:06.420> less<00:15:06.600> common<00:15:06.899> is<00:15:07.199> please 00:15:07.670 --> 00:15:07.680 align:start position:0% um I guess one less common is please 00:15:07.680 --> 00:15:10.569 align:start position:0% um I guess one less common is please don't<00:15:07.920> threat<00:15:08.339> threaten<00:15:08.940> us 00:15:10.569 --> 00:15:10.579 align:start position:0% don't threat threaten us 00:15:10.579 --> 00:15:13.189 align:start position:0% don't threat threaten us minority<00:15:11.579> clients<00:15:12.240> by<00:15:12.480> saying<00:15:12.839> oh<00:15:12.959> we're 00:15:13.189 --> 00:15:13.199 align:start position:0% minority clients by saying oh we're 00:15:13.199 --> 00:15:16.129 align:start position:0% minority clients by saying oh we're gonna<00:15:13.380> go<00:15:13.620> together<00:15:13.940> I<00:15:14.940> think<00:15:15.060> that's<00:15:15.420> like<00:15:15.779> a 00:15:16.129 --> 00:15:16.139 align:start position:0% gonna go together I think that's like a 00:15:16.139 --> 00:15:19.310 align:start position:0% gonna go together I think that's like a step<00:15:16.740> in<00:15:17.100> your<00:15:17.279> like<00:15:17.699> heart<00:15:18.360> and<00:15:18.600> twisting<00:15:19.139> it 00:15:19.310 --> 00:15:19.320 align:start position:0% step in your like heart and twisting it 00:15:19.320 --> 00:15:22.910 align:start position:0% step in your like heart and twisting it so<00:15:20.040> yeah<00:15:20.639> thank<00:15:21.240> you 00:15:22.910 --> 00:15:22.920 align:start position:0% so yeah thank you 00:15:22.920 --> 00:15:26.329 align:start position:0% so yeah thank you hello<00:15:23.639> okay<00:15:24.180> so<00:15:24.600> I<00:15:25.199> wanna<00:15:25.500> double<00:15:25.860> down<00:15:26.100> on 00:15:26.329 --> 00:15:26.339 align:start position:0% hello okay so I wanna double down on 00:15:26.339 --> 00:15:29.750 align:start position:0% hello okay so I wanna double down on Paul<00:15:26.579> so<00:15:26.880> I'm<00:15:27.180> from<00:15:27.420> prison<00:15:27.779> and<00:15:28.860> um<00:15:28.860> so<00:15:29.459> from 00:15:29.750 --> 00:15:29.760 align:start position:0% Paul so I'm from prison and um so from 00:15:29.760 --> 00:15:32.870 align:start position:0% Paul so I'm from prison and um so from my<00:15:30.000> team's<00:15:30.480> perspective<00:15:31.399> merge<00:15:32.399> has<00:15:32.639> always 00:15:32.870 --> 00:15:32.880 align:start position:0% my team's perspective merge has always 00:15:32.880 --> 00:15:35.449 align:start position:0% my team's perspective merge has always just<00:15:33.180> been<00:15:33.360> consensus<00:15:34.139> execution<00:15:34.920> and<00:15:35.339> engine 00:15:35.449 --> 00:15:35.459 align:start position:0% just been consensus execution and engine 00:15:35.459 --> 00:15:39.170 align:start position:0% just been consensus execution and engine API<00:15:36.060> and<00:15:36.540> boom<00:15:36.899> done<00:15:37.139> right<00:15:37.560> and<00:15:38.279> then<00:15:38.459> like<00:15:38.880> I 00:15:39.170 --> 00:15:39.180 align:start position:0% API and boom done right and then like I 00:15:39.180 --> 00:15:41.210 align:start position:0% API and boom done right and then like I guess<00:15:39.360> like<00:15:39.660> just<00:15:40.019> a<00:15:40.199> month<00:15:40.380> before<00:15:40.620> the<00:15:40.860> merch 00:15:41.210 --> 00:15:41.220 align:start position:0% guess like just a month before the merch 00:15:41.220 --> 00:15:43.129 align:start position:0% guess like just a month before the merch we<00:15:41.459> learned<00:15:41.699> okay<00:15:41.820> there's<00:15:42.180> this<00:15:42.360> Mev<00:15:42.899> stuff 00:15:43.129 --> 00:15:43.139 align:start position:0% we learned okay there's this Mev stuff 00:15:43.139 --> 00:15:45.290 align:start position:0% we learned okay there's this Mev stuff we<00:15:43.440> have<00:15:43.560> to<00:15:43.680> work<00:15:43.920> out<00:15:44.160> now<00:15:44.339> and<00:15:45.000> then<00:15:45.120> there's 00:15:45.290 --> 00:15:45.300 align:start position:0% we have to work out now and then there's 00:15:45.300 --> 00:15:47.210 align:start position:0% we have to work out now and then there's this<00:15:45.480> Mev<00:15:45.899> booths<00:15:46.320> and<00:15:46.440> there's<00:15:46.560> this<00:15:46.680> relayer 00:15:47.210 --> 00:15:47.220 align:start position:0% this Mev booths and there's this relayer 00:15:47.220 --> 00:15:49.670 align:start position:0% this Mev booths and there's this relayer this<00:15:47.399> Builder<00:15:47.880> so<00:15:48.060> we<00:15:48.240> just<00:15:48.420> keep<00:15:48.540> adding<00:15:49.019> more 00:15:49.670 --> 00:15:49.680 align:start position:0% this Builder so we just keep adding more 00:15:49.680 --> 00:15:52.370 align:start position:0% this Builder so we just keep adding more and<00:15:49.860> more<00:15:50.160> actors<00:15:50.699> to<00:15:51.000> the<00:15:51.120> picture<00:15:51.300> and<00:15:52.260> then 00:15:52.370 --> 00:15:52.380 align:start position:0% and more actors to the picture and then 00:15:52.380 --> 00:15:54.710 align:start position:0% and more actors to the picture and then even<00:15:52.620> a<00:15:52.800> few<00:15:52.920> weeks<00:15:53.160> before<00:15:53.459> the<00:15:54.120> merge<00:15:54.540> right 00:15:54.710 --> 00:15:54.720 align:start position:0% even a few weeks before the merge right 00:15:54.720 --> 00:15:56.750 align:start position:0% even a few weeks before the merge right there<00:15:54.959> there<00:15:55.320> was<00:15:55.560> this<00:15:55.860> tornado<00:15:56.279> or<00:15:56.519> cash 00:15:56.750 --> 00:15:56.760 align:start position:0% there there was this tornado or cash 00:15:56.760 --> 00:15:58.910 align:start position:0% there there was this tornado or cash they<00:15:57.240> say<00:15:57.420> all<00:15:57.660> fetch<00:15:58.019> stuff<00:15:58.199> and<00:15:58.800> then 00:15:58.910 --> 00:15:58.920 align:start position:0% they say all fetch stuff and then 00:15:58.920 --> 00:16:01.610 align:start position:0% they say all fetch stuff and then flashbots<00:15:59.579> would<00:15:59.760> only<00:16:00.000> relayer<00:16:00.660> so<00:16:01.199> our<00:16:01.380> team 00:16:01.610 --> 00:16:01.620 align:start position:0% flashbots would only relayer so our team 00:16:01.620 --> 00:16:03.470 align:start position:0% flashbots would only relayer so our team had<00:16:01.980> this<00:16:02.279> big<00:16:02.459> internal<00:16:02.820> discussion<00:16:03.180> it's 00:16:03.470 --> 00:16:03.480 align:start position:0% had this big internal discussion it's 00:16:03.480 --> 00:16:04.910 align:start position:0% had this big internal discussion it's okay<00:16:03.600> should<00:16:03.839> we<00:16:04.019> drop<00:16:04.139> the<00:16:04.320> support<00:16:04.500> right 00:16:04.910 --> 00:16:04.920 align:start position:0% okay should we drop the support right 00:16:04.920 --> 00:16:07.790 align:start position:0% okay should we drop the support right now<00:16:05.100> like<00:16:05.519> like<00:16:05.880> what<00:16:06.240> should<00:16:06.420> we<00:16:06.600> do<00:16:06.899> if 00:16:07.790 --> 00:16:07.800 align:start position:0% now like like what should we do if 00:16:07.800 --> 00:16:10.910 align:start position:0% now like like what should we do if flashbart<00:16:08.579> was<00:16:08.880> the<00:16:09.120> only<00:16:09.240> relayer<00:16:09.899> and<00:16:10.440> they 00:16:10.910 --> 00:16:10.920 align:start position:0% flashbart was the only relayer and they 00:16:10.920 --> 00:16:12.829 align:start position:0% flashbart was the only relayer and they are<00:16:11.100> sensory<00:16:11.519> transaction<00:16:12.000> right<00:16:12.480> even 00:16:12.829 --> 00:16:12.839 align:start position:0% are sensory transaction right even 00:16:12.839 --> 00:16:15.650 align:start position:0% are sensory transaction right even though<00:16:13.079> and<00:16:13.980> maybe<00:16:14.639> boost<00:16:14.880> is<00:16:15.240> a<00:16:15.360> neutral 00:16:15.650 --> 00:16:15.660 align:start position:0% though and maybe boost is a neutral 00:16:15.660 --> 00:16:17.930 align:start position:0% though and maybe boost is a neutral piece<00:16:15.959> of<00:16:16.019> software<00:16:16.440> above<00:16:16.980> flash<00:16:17.220> about<00:16:17.399> is 00:16:17.930 --> 00:16:17.940 align:start position:0% piece of software above flash about is 00:16:17.940 --> 00:16:19.790 align:start position:0% piece of software above flash about is the<00:16:18.120> only<00:16:18.240> relayer<00:16:18.779> then<00:16:19.019> as<00:16:19.260> a<00:16:19.380> client<00:16:19.620> team 00:16:19.790 --> 00:16:19.800 align:start position:0% the only relayer then as a client team 00:16:19.800 --> 00:16:22.370 align:start position:0% the only relayer then as a client team we<00:16:20.100> are<00:16:20.279> indirectly<00:16:21.000> supporting<00:16:21.899> censorship 00:16:22.370 --> 00:16:22.380 align:start position:0% we are indirectly supporting censorship 00:16:22.380 --> 00:16:24.410 align:start position:0% we are indirectly supporting censorship and<00:16:22.620> of<00:16:22.740> course<00:16:23.160> I'm<00:16:23.760> not<00:16:23.880> happy<00:16:24.060> with<00:16:24.240> that 00:16:24.410 --> 00:16:24.420 align:start position:0% and of course I'm not happy with that 00:16:24.420 --> 00:16:26.269 align:start position:0% and of course I'm not happy with that this<00:16:24.600> this<00:16:24.779> is<00:16:24.959> now<00:16:25.199> why<00:16:25.680> we're<00:16:25.860> here<00:16:26.100> for 00:16:26.269 --> 00:16:26.279 align:start position:0% this this is now why we're here for 00:16:26.279 --> 00:16:29.509 align:start position:0% this this is now why we're here for right<00:16:26.519> so<00:16:26.940> I<00:16:27.600> think<00:16:27.720> like<00:16:28.500> we've<00:16:29.160> learned<00:16:29.279> a 00:16:29.509 --> 00:16:29.519 align:start position:0% right so I think like we've learned a 00:16:29.519 --> 00:16:31.370 align:start position:0% right so I think like we've learned a lot<00:16:29.639> I<00:16:29.820> learned<00:16:30.060> a<00:16:30.240> lot<00:16:30.360> it's<00:16:30.600> just<00:16:30.839> like<00:16:31.019> if 00:16:31.370 --> 00:16:31.380 align:start position:0% lot I learned a lot it's just like if 00:16:31.380 --> 00:16:34.009 align:start position:0% lot I learned a lot it's just like if today<00:16:31.620> relays<00:16:32.399> are<00:16:32.519> producing<00:16:32.940> 50<00:16:33.180> of<00:16:33.720> the 00:16:34.009 --> 00:16:34.019 align:start position:0% today relays are producing 50 of the 00:16:34.019 --> 00:16:35.629 align:start position:0% today relays are producing 50 of the blocks<00:16:34.500> on<00:16:34.560> the<00:16:34.680> main<00:16:34.800> net<00:16:35.040> are<00:16:35.519> they 00:16:35.629 --> 00:16:35.639 align:start position:0% blocks on the main net are they 00:16:35.639 --> 00:16:37.730 align:start position:0% blocks on the main net are they considered<00:16:36.060> as<00:16:36.180> layer<00:16:36.540> one<00:16:36.720> right<00:16:37.019> and<00:16:37.560> I'm 00:16:37.730 --> 00:16:37.740 align:start position:0% considered as layer one right and I'm 00:16:37.740 --> 00:16:40.009 align:start position:0% considered as layer one right and I'm I'm<00:16:38.040> I'm<00:16:38.160> really<00:16:38.820> happy<00:16:39.120> to<00:16:39.300> see<00:16:39.540> this<00:16:39.779> more 00:16:40.009 --> 00:16:40.019 align:start position:0% I'm I'm really happy to see this more 00:16:40.019 --> 00:16:41.810 align:start position:0% I'm I'm really happy to see this more and<00:16:40.139> more<00:16:40.380> like<00:16:40.560> relayers<00:16:41.160> flash<00:16:41.339> balls 00:16:41.810 --> 00:16:41.820 align:start position:0% and more like relayers flash balls 00:16:41.820 --> 00:16:43.850 align:start position:0% and more like relayers flash balls they're<00:16:42.060> joining<00:16:42.540> the<00:16:42.720> Oracle<00:16:43.139> Depot<00:16:43.380> they're 00:16:43.850 --> 00:16:43.860 align:start position:0% they're joining the Oracle Depot they're 00:16:43.860 --> 00:16:46.249 align:start position:0% they're joining the Oracle Depot they're starting<00:16:44.100> to<00:16:44.759> participate<00:16:45.420> more<00:16:45.779> on<00:16:46.079> just 00:16:46.249 --> 00:16:46.259 align:start position:0% starting to participate more on just 00:16:46.259 --> 00:16:48.230 align:start position:0% starting to participate more on just layer<00:16:46.560> one<00:16:46.680> roadmap<00:16:47.160> like<00:16:47.459> architecture<00:16:48.120> and 00:16:48.230 --> 00:16:48.240 align:start position:0% layer one roadmap like architecture and 00:16:48.240 --> 00:16:50.870 align:start position:0% layer one roadmap like architecture and stuff<00:16:48.420> like<00:16:48.600> that<00:16:48.720> so<00:16:48.959> I<00:16:49.139> do<00:16:49.259> think<00:16:49.440> like<00:16:49.740> we<00:16:50.699> do 00:16:50.870 --> 00:16:50.880 align:start position:0% stuff like that so I do think like we do 00:16:50.880 --> 00:16:52.610 align:start position:0% stuff like that so I do think like we do have<00:16:51.360> to<00:16:51.540> work<00:16:51.660> with<00:16:51.839> them<00:16:51.959> and<00:16:52.139> they<00:16:52.380> have<00:16:52.560> to 00:16:52.610 --> 00:16:52.620 align:start position:0% have to work with them and they have to 00:16:52.620 --> 00:16:54.470 align:start position:0% have to work with them and they have to work<00:16:52.740> with<00:16:52.920> us<00:16:53.100> together<00:16:53.399> to<00:16:53.880> basically<00:16:54.240> push 00:16:54.470 --> 00:16:54.480 align:start position:0% work with us together to basically push 00:16:54.480 --> 00:16:57.650 align:start position:0% work with us together to basically push the<00:16:54.720> space<00:16:54.899> forward 00:16:57.650 --> 00:16:57.660 align:start position:0% 00:16:57.660 --> 00:16:59.629 align:start position:0% okay 00:16:59.629 --> 00:16:59.639 align:start position:0% okay 00:16:59.639 --> 00:17:02.030 align:start position:0% okay yeah<00:17:00.060> good<00:17:00.600> points<00:17:00.839> by<00:17:01.259> um<00:17:01.259> by<00:17:01.560> Terrence<00:17:01.920> I 00:17:02.030 --> 00:17:02.040 align:start position:0% yeah good points by um by Terrence I 00:17:02.040 --> 00:17:03.290 align:start position:0% yeah good points by um by Terrence I think<00:17:02.160> it's<00:17:02.279> worth<00:17:02.459> saying<00:17:02.759> as<00:17:02.880> well<00:17:02.940> that<00:17:03.060> I 00:17:03.290 --> 00:17:03.300 align:start position:0% think it's worth saying as well that I 00:17:03.300 --> 00:17:04.669 align:start position:0% think it's worth saying as well that I think<00:17:03.360> even<00:17:03.959> though<00:17:04.079> we<00:17:04.260> did<00:17:04.380> have<00:17:04.500> some 00:17:04.669 --> 00:17:04.679 align:start position:0% think even though we did have some 00:17:04.679 --> 00:17:06.350 align:start position:0% think even though we did have some problems<00:17:04.919> with<00:17:05.100> Mev<00:17:05.579> and<00:17:05.760> I<00:17:05.880> was<00:17:05.939> pretty<00:17:06.120> harsh 00:17:06.350 --> 00:17:06.360 align:start position:0% problems with Mev and I was pretty harsh 00:17:06.360 --> 00:17:07.970 align:start position:0% problems with Mev and I was pretty harsh on<00:17:06.480> them<00:17:06.600> before<00:17:06.780> I<00:17:07.199> think<00:17:07.319> we<00:17:07.500> did<00:17:07.620> come<00:17:07.799> out 00:17:07.970 --> 00:17:07.980 align:start position:0% on them before I think we did come out 00:17:07.980 --> 00:17:09.949 align:start position:0% on them before I think we did come out of<00:17:08.160> it<00:17:08.579> um<00:17:08.640> in<00:17:08.939> a<00:17:09.059> better<00:17:09.179> spot<00:17:09.480> than<00:17:09.660> we<00:17:09.780> were 00:17:09.949 --> 00:17:09.959 align:start position:0% of it um in a better spot than we were 00:17:09.959 --> 00:17:13.309 align:start position:0% of it um in a better spot than we were before<00:17:10.199> uh<00:17:10.799> there's<00:17:10.980> no<00:17:11.160> like<00:17:11.640> Mev<00:17:12.120> guests<00:17:12.480> now 00:17:13.309 --> 00:17:13.319 align:start position:0% before uh there's no like Mev guests now 00:17:13.319 --> 00:17:14.449 align:start position:0% before uh there's no like Mev guests now um<00:17:13.380> and<00:17:13.500> Flash<00:17:13.679> Sports<00:17:13.919> we're<00:17:14.160> really<00:17:14.280> happy 00:17:14.449 --> 00:17:14.459 align:start position:0% um and Flash Sports we're really happy 00:17:14.459 --> 00:17:16.669 align:start position:0% um and Flash Sports we're really happy to<00:17:14.699> to<00:17:15.000> relinquish<00:17:15.600> that<00:17:15.839> that<00:17:16.079> control<00:17:16.319> which 00:17:16.669 --> 00:17:16.679 align:start position:0% to to relinquish that that control which 00:17:16.679 --> 00:17:17.929 align:start position:0% to to relinquish that that control which was<00:17:16.799> really<00:17:17.040> cool 00:17:17.929 --> 00:17:17.939 align:start position:0% was really cool 00:17:17.939 --> 00:17:20.030 align:start position:0% was really cool um an<00:17:18.179> mbb<00:17:18.600> boost 00:17:20.030 --> 00:17:20.040 align:start position:0% um an mbb boost 00:17:20.040 --> 00:17:22.130 align:start position:0% um an mbb boost um is<00:17:20.640> something<00:17:21.360> that<00:17:21.540> can<00:17:21.660> be<00:17:21.780> implemented 00:17:22.130 --> 00:17:22.140 align:start position:0% um is something that can be implemented 00:17:22.140 --> 00:17:23.390 align:start position:0% um is something that can be implemented by<00:17:22.380> other<00:17:22.559> people 00:17:23.390 --> 00:17:23.400 align:start position:0% by other people 00:17:23.400 --> 00:17:25.069 align:start position:0% by other people um<00:17:23.520> and<00:17:23.819> even<00:17:24.000> as<00:17:24.179> it<00:17:24.360> stands<00:17:24.660> it<00:17:24.780> works<00:17:25.020> with 00:17:25.069 --> 00:17:25.079 align:start position:0% um and even as it stands it works with 00:17:25.079 --> 00:17:27.169 align:start position:0% um and even as it stands it works with other<00:17:25.319> relays<00:17:26.339> um<00:17:26.400> so<00:17:26.579> I<00:17:26.760> think<00:17:26.819> we<00:17:27.000> really 00:17:27.169 --> 00:17:27.179 align:start position:0% other relays um so I think we really 00:17:27.179 --> 00:17:29.090 align:start position:0% other relays um so I think we really opened<00:17:27.480> up<00:17:27.540> the<00:17:27.720> world<00:17:27.839> to<00:17:28.140> Mev<00:17:28.620> and<00:17:28.799> although 00:17:29.090 --> 00:17:29.100 align:start position:0% opened up the world to Mev and although 00:17:29.100 --> 00:17:30.350 align:start position:0% opened up the world to Mev and although we<00:17:29.220> didn't<00:17:29.340> solve<00:17:29.640> it<00:17:29.700> and<00:17:29.880> we're<00:17:30.059> still<00:17:30.240> not 00:17:30.350 --> 00:17:30.360 align:start position:0% we didn't solve it and we're still not 00:17:30.360 --> 00:17:32.270 align:start position:0% we didn't solve it and we're still not in<00:17:30.540> a<00:17:30.660> great<00:17:30.780> spot<00:17:30.960> I<00:17:31.380> think<00:17:31.500> we<00:17:31.679> ended<00:17:31.919> up<00:17:31.980> in<00:17:32.160> a 00:17:32.270 --> 00:17:32.280 align:start position:0% in a great spot I think we ended up in a 00:17:32.280 --> 00:17:34.310 align:start position:0% in a great spot I think we ended up in a better<00:17:32.400> spot<00:17:33.120> um<00:17:33.179> and<00:17:33.419> I<00:17:33.540> think<00:17:33.660> flashbots 00:17:34.310 --> 00:17:34.320 align:start position:0% better spot um and I think flashbots 00:17:34.320 --> 00:17:35.750 align:start position:0% better spot um and I think flashbots have<00:17:34.500> done<00:17:34.620> some<00:17:34.740> good<00:17:34.860> stuff<00:17:35.340> um<00:17:35.340> towards 00:17:35.750 --> 00:17:35.760 align:start position:0% have done some good stuff um towards 00:17:35.760 --> 00:17:37.070 align:start position:0% have done some good stuff um towards that<00:17:35.880> as<00:17:36.000> well 00:17:37.070 --> 00:17:37.080 align:start position:0% that as well 00:17:37.080 --> 00:17:38.630 align:start position:0% that as well yeah<00:17:37.559> the<00:17:37.740> circuit<00:17:38.039> breaker's<00:17:38.400> good<00:17:38.460> as<00:17:38.580> well 00:17:38.630 --> 00:17:38.640 align:start position:0% yeah the circuit breaker's good as well 00:17:38.640 --> 00:17:41.570 align:start position:0% yeah the circuit breaker's good as well yeah<00:17:38.820> so<00:17:39.000> now<00:17:39.419> there's<00:17:40.020> um<00:17:40.100> the<00:17:41.100> consensus 00:17:41.570 --> 00:17:41.580 align:start position:0% yeah so now there's um the consensus 00:17:41.580 --> 00:17:43.310 align:start position:0% yeah so now there's um the consensus clients<00:17:42.000> can<00:17:42.240> detect<00:17:42.480> when<00:17:42.780> the<00:17:42.960> chain<00:17:43.140> is 00:17:43.310 --> 00:17:43.320 align:start position:0% clients can detect when the chain is 00:17:43.320 --> 00:17:45.710 align:start position:0% clients can detect when the chain is unhealthy<00:17:43.799> and<00:17:43.980> then<00:17:44.100> just<00:17:44.280> disable<00:17:44.520> Mev 00:17:45.710 --> 00:17:45.720 align:start position:0% unhealthy and then just disable Mev 00:17:45.720 --> 00:17:46.730 align:start position:0% unhealthy and then just disable Mev um<00:17:45.840> so<00:17:45.960> that's<00:17:46.080> something<00:17:46.260> that<00:17:46.500> we<00:17:46.620> couldn't 00:17:46.730 --> 00:17:46.740 align:start position:0% um so that's something that we couldn't 00:17:46.740 --> 00:17:49.130 align:start position:0% um so that's something that we couldn't really<00:17:46.919> do<00:17:47.100> before<00:17:47.280> in<00:17:47.580> Mev<00:17:48.000> Geth 00:17:49.130 --> 00:17:49.140 align:start position:0% really do before in Mev Geth 00:17:49.140 --> 00:17:51.230 align:start position:0% really do before in Mev Geth um<00:17:49.200> with<00:17:49.620> the<00:17:49.799> like<00:17:49.919> Mev<00:17:50.340> boot<00:17:50.640> flash<00:17:51.000> plus 00:17:51.230 --> 00:17:51.240 align:start position:0% um with the like Mev boot flash plus 00:17:51.240 --> 00:17:53.029 align:start position:0% um with the like Mev boot flash plus could<00:17:51.480> have<00:17:51.539> implemented<00:17:51.960> it<00:17:52.080> but 00:17:53.029 --> 00:17:53.039 align:start position:0% could have implemented it but 00:17:53.039 --> 00:17:55.010 align:start position:0% could have implemented it but um<00:17:53.100> you<00:17:53.220> know<00:17:53.280> it's<00:17:53.340> a<00:17:53.520> lot<00:17:53.580> of<00:17:53.700> work<00:17:53.820> for<00:17:53.940> them 00:17:55.010 --> 00:17:55.020 align:start position:0% um you know it's a lot of work for them 00:17:55.020 --> 00:17:56.750 align:start position:0% um you know it's a lot of work for them um<00:17:55.140> so<00:17:55.679> yeah<00:17:55.860> now<00:17:56.039> there's<00:17:56.400> a<00:17:56.580> lot<00:17:56.640> more 00:17:56.750 --> 00:17:56.760 align:start position:0% um so yeah now there's a lot more 00:17:56.760 --> 00:17:58.250 align:start position:0% um so yeah now there's a lot more control<00:17:56.940> from<00:17:57.299> the<00:17:57.419> consensus<00:17:57.840> clients<00:17:58.140> at 00:17:58.250 --> 00:17:58.260 align:start position:0% control from the consensus clients at 00:17:58.260 --> 00:18:00.230 align:start position:0% control from the consensus clients at least<00:17:58.919> um<00:17:58.980> into<00:17:59.160> what's<00:17:59.400> going<00:17:59.580> on<00:17:59.700> with<00:17:59.820> Mev 00:18:00.230 --> 00:18:00.240 align:start position:0% least um into what's going on with Mev 00:18:00.240 --> 00:18:01.430 align:start position:0% least um into what's going on with Mev and<00:18:00.419> I<00:18:00.539> think<00:18:00.600> that's<00:18:00.780> that's<00:18:01.020> a<00:18:01.260> really<00:18:01.320> good 00:18:01.430 --> 00:18:01.440 align:start position:0% and I think that's that's a really good 00:18:01.440 --> 00:18:02.870 align:start position:0% and I think that's that's a really good place<00:18:01.620> to<00:18:01.740> be<00:18:01.860> in 00:18:02.870 --> 00:18:02.880 align:start position:0% place to be in 00:18:02.880 --> 00:18:05.630 align:start position:0% place to be in do<00:18:03.480> they<00:18:03.900> still<00:18:04.140> run<00:18:04.500> nav<00:18:04.860> Geth<00:18:05.280> if<00:18:05.400> you<00:18:05.520> did 00:18:05.630 --> 00:18:05.640 align:start position:0% do they still run nav Geth if you did 00:18:05.640 --> 00:18:07.430 align:start position:0% do they still run nav Geth if you did the<00:18:05.760> theory<00:18:06.000> layers 00:18:07.430 --> 00:18:07.440 align:start position:0% the theory layers 00:18:07.440 --> 00:18:08.810 align:start position:0% the theory layers I<00:18:07.980> don't<00:18:08.039> know<00:18:08.160> actually<00:18:08.400> it's<00:18:08.580> a<00:18:08.760> good 00:18:08.810 --> 00:18:08.820 align:start position:0% I don't know actually it's a good 00:18:08.820 --> 00:18:10.909 align:start position:0% I don't know actually it's a good question<00:18:09.000> I<00:18:09.299> kind<00:18:09.480> of<00:18:09.840> um<00:18:09.840> wasn't<00:18:10.559> thinking 00:18:10.909 --> 00:18:10.919 align:start position:0% question I kind of um wasn't thinking 00:18:10.919 --> 00:18:12.650 align:start position:0% question I kind of um wasn't thinking about<00:18:11.039> that<00:18:11.340> but<00:18:11.580> yeah<00:18:12.000> because<00:18:12.120> I<00:18:12.360> think<00:18:12.480> like 00:18:12.650 --> 00:18:12.660 align:start position:0% about that but yeah because I think like 00:18:12.660 --> 00:18:14.150 align:start position:0% about that but yeah because I think like you<00:18:12.900> know<00:18:13.020> for<00:18:13.140> the<00:18:13.320> most<00:18:13.440> part<00:18:13.500> most<00:18:13.919> people 00:18:14.150 --> 00:18:14.160 align:start position:0% you know for the most part most people 00:18:14.160 --> 00:18:15.529 align:start position:0% you know for the most part most people who<00:18:14.340> are<00:18:14.400> running<00:18:14.580> validators<00:18:15.120> they're<00:18:15.360> just 00:18:15.529 --> 00:18:15.539 align:start position:0% who are running validators they're just 00:18:15.539 --> 00:18:17.810 align:start position:0% who are running validators they're just getting<00:18:15.780> blocks<00:18:16.500> from<00:18:16.799> the<00:18:16.980> either<00:18:17.640> the 00:18:17.810 --> 00:18:17.820 align:start position:0% getting blocks from the either the 00:18:17.820 --> 00:18:19.490 align:start position:0% getting blocks from the either the Builder<00:18:18.120> the<00:18:18.299> relay<00:18:18.539> somebody<00:18:18.840> has<00:18:19.080> to<00:18:19.200> run 00:18:19.490 --> 00:18:19.500 align:start position:0% Builder the relay somebody has to run 00:18:19.500 --> 00:18:21.710 align:start position:0% Builder the relay somebody has to run something<00:18:20.400> that<00:18:20.700> looks<00:18:21.000> like<00:18:21.059> Geth<00:18:21.480> that's 00:18:21.710 --> 00:18:21.720 align:start position:0% something that looks like Geth that's 00:18:21.720 --> 00:18:23.870 align:start position:0% something that looks like Geth that's taking<00:18:21.900> the<00:18:22.200> Searcher<00:18:22.559> bundles<00:18:22.980> together<00:18:23.400> and 00:18:23.870 --> 00:18:23.880 align:start position:0% taking the Searcher bundles together and 00:18:23.880 --> 00:18:26.210 align:start position:0% taking the Searcher bundles together and putting<00:18:24.419> them<00:18:24.539> into<00:18:24.720> a<00:18:24.960> block<00:18:25.080> format<00:18:25.559> yeah<00:18:26.039> I 00:18:26.210 --> 00:18:26.220 align:start position:0% putting them into a block format yeah I 00:18:26.220 --> 00:18:28.070 align:start position:0% putting them into a block format yeah I guess<00:18:26.400> what's<00:18:26.580> up<00:18:26.760> if<00:18:27.240> that<00:18:27.419> that's<00:18:27.660> still<00:18:27.840> the 00:18:28.070 --> 00:18:28.080 align:start position:0% guess what's up if that that's still the 00:18:28.080 --> 00:18:29.510 align:start position:0% guess what's up if that that's still the case<00:18:28.200> it's<00:18:28.380> not<00:18:28.559> it's<00:18:28.679> not<00:18:28.860> ideal<00:18:29.100> but<00:18:29.280> I<00:18:29.460> guess 00:18:29.510 --> 00:18:29.520 align:start position:0% case it's not it's not ideal but I guess 00:18:29.520 --> 00:18:31.130 align:start position:0% case it's not it's not ideal but I guess what's<00:18:29.700> better<00:18:29.940> now<00:18:30.179> is<00:18:30.360> that<00:18:30.660> every<00:18:30.840> one<00:18:31.020> of 00:18:31.130 --> 00:18:31.140 align:start position:0% what's better now is that every one of 00:18:31.140 --> 00:18:34.669 align:start position:0% what's better now is that every one of those<00:18:31.260> gets<00:18:31.620> produced<00:18:32.039> is<00:18:32.580> now<00:18:32.760> verified<00:18:33.240> by 00:18:34.669 --> 00:18:34.679 align:start position:0% those gets produced is now verified by 00:18:34.679 --> 00:18:36.950 align:start position:0% those gets produced is now verified by um<00:18:34.740> not<00:18:35.340> that<00:18:35.580> thing<00:18:35.820> before<00:18:36.299> it's<00:18:36.539> published 00:18:36.950 --> 00:18:36.960 align:start position:0% um not that thing before it's published 00:18:36.960 --> 00:18:38.570 align:start position:0% um not that thing before it's published on<00:18:37.080> the<00:18:37.200> network<00:18:37.320> right 00:18:38.570 --> 00:18:38.580 align:start position:0% on the network right 00:18:38.580 --> 00:18:40.310 align:start position:0% on the network right yeah<00:18:39.120> and<00:18:39.299> I<00:18:39.419> guess<00:18:39.539> like<00:18:39.720> from<00:18:40.020> my 00:18:40.310 --> 00:18:40.320 align:start position:0% yeah and I guess like from my 00:18:40.320 --> 00:18:42.650 align:start position:0% yeah and I guess like from my perspective<00:18:40.679> the<00:18:41.280> the<00:18:41.340> whole<00:18:41.940> situation<00:18:42.419> with 00:18:42.650 --> 00:18:42.660 align:start position:0% perspective the the whole situation with 00:18:42.660 --> 00:18:45.529 align:start position:0% perspective the the whole situation with Mev<00:18:42.960> was<00:18:43.140> very<00:18:43.320> interesting<00:18:43.740> because<00:18:44.419> Mev<00:18:45.419> has 00:18:45.529 --> 00:18:45.539 align:start position:0% Mev was very interesting because Mev has 00:18:45.539 --> 00:18:47.990 align:start position:0% Mev was very interesting because Mev has been<00:18:45.660> around<00:18:45.840> for<00:18:46.440> several<00:18:47.160> years<00:18:47.340> now<00:18:47.640> and 00:18:47.990 --> 00:18:48.000 align:start position:0% been around for several years now and 00:18:48.000 --> 00:18:49.669 align:start position:0% been around for several years now and you<00:18:48.360> know<00:18:48.480> we've<00:18:48.900> kind<00:18:49.020> of<00:18:49.140> seen<00:18:49.320> through<00:18:49.500> the 00:18:49.669 --> 00:18:49.679 align:start position:0% you know we've kind of seen through the 00:18:49.679 --> 00:18:52.430 align:start position:0% you know we've kind of seen through the defy<00:18:50.160> Summer<00:18:50.340> and<00:18:50.580> the<00:18:50.760> nft<00:18:51.000> summer<00:18:51.440> these 00:18:52.430 --> 00:18:52.440 align:start position:0% defy Summer and the nft summer these 00:18:52.440 --> 00:18:54.230 align:start position:0% defy Summer and the nft summer these crazy<00:18:52.559> numbers<00:18:52.799> about<00:18:53.100> how<00:18:53.340> much<00:18:53.460> Mev<00:18:54.000> there 00:18:54.230 --> 00:18:54.240 align:start position:0% crazy numbers about how much Mev there 00:18:54.240 --> 00:18:56.570 align:start position:0% crazy numbers about how much Mev there is<00:18:54.360> in<00:18:54.539> blocks<00:18:55.020> and<00:18:55.200> you<00:18:55.919> know<00:18:55.980> for<00:18:56.220> my 00:18:56.570 --> 00:18:56.580 align:start position:0% is in blocks and you know for my 00:18:56.580 --> 00:18:57.590 align:start position:0% is in blocks and you know for my perspective<00:18:56.880> was<00:18:57.059> I<00:18:57.179> was<00:18:57.299> thinking<00:18:57.360> you<00:18:57.480> know 00:18:57.590 --> 00:18:57.600 align:start position:0% perspective was I was thinking you know 00:18:57.600 --> 00:18:59.029 align:start position:0% perspective was I was thinking you know there's<00:18:57.780> so<00:18:57.960> much<00:18:58.080> money<00:18:58.260> in<00:18:58.500> this<00:18:58.679> industry 00:18:59.029 --> 00:18:59.039 align:start position:0% there's so much money in this industry 00:18:59.039 --> 00:19:00.710 align:start position:0% there's so much money in this industry like<00:18:59.340> the<00:18:59.700> solutions<00:19:00.120> are<00:19:00.299> just<00:19:00.480> going<00:19:00.600> to 00:19:00.710 --> 00:19:00.720 align:start position:0% like the solutions are just going to 00:19:00.720 --> 00:19:01.789 align:start position:0% like the solutions are just going to appear<00:19:01.020> and<00:19:01.260> they're<00:19:01.380> going<00:19:01.500> to<00:19:01.559> be<00:19:01.620> really 00:19:01.789 --> 00:19:01.799 align:start position:0% appear and they're going to be really 00:19:01.799 --> 00:19:03.970 align:start position:0% appear and they're going to be really robust<00:19:02.280> and<00:19:02.820> they're<00:19:03.000> going<00:19:03.120> to<00:19:03.299> work 00:19:03.970 --> 00:19:03.980 align:start position:0% robust and they're going to work 00:19:03.980 --> 00:19:06.590 align:start position:0% robust and they're going to work and<00:19:04.980> then<00:19:05.100> you<00:19:05.400> know<00:19:05.520> it<00:19:05.640> turns<00:19:05.940> out<00:19:06.059> that<00:19:06.419> it's 00:19:06.590 --> 00:19:06.600 align:start position:0% and then you know it turns out that it's 00:19:06.600 --> 00:19:08.630 align:start position:0% and then you know it turns out that it's six<00:19:06.840> seven<00:19:07.140> months<00:19:07.500> before<00:19:07.740> we<00:19:08.280> were<00:19:08.460> really 00:19:08.630 --> 00:19:08.640 align:start position:0% six seven months before we were really 00:19:08.640 --> 00:19:10.610 align:start position:0% six seven months before we were really projecting<00:19:09.059> for<00:19:09.240> the<00:19:09.360> merch<00:19:09.660> to<00:19:09.840> happen<00:19:10.020> we're 00:19:10.610 --> 00:19:10.620 align:start position:0% projecting for the merch to happen we're 00:19:10.620 --> 00:19:12.529 align:start position:0% projecting for the merch to happen we're starting<00:19:10.860> to<00:19:11.039> realize<00:19:11.400> that<00:19:11.880> the<00:19:12.179> solutions 00:19:12.529 --> 00:19:12.539 align:start position:0% starting to realize that the solutions 00:19:12.539 --> 00:19:14.930 align:start position:0% starting to realize that the solutions that<00:19:12.960> we<00:19:13.380> as<00:19:13.500> core<00:19:13.740> developers<00:19:14.220> feel<00:19:14.460> need<00:19:14.820> to 00:19:14.930 --> 00:19:14.940 align:start position:0% that we as core developers feel need to 00:19:14.940 --> 00:19:17.270 align:start position:0% that we as core developers feel need to exist<00:19:15.240> weren't<00:19:15.840> in<00:19:16.559> the<00:19:16.620> place<00:19:16.740> that<00:19:16.919> we<00:19:17.039> felt 00:19:17.270 --> 00:19:17.280 align:start position:0% exist weren't in the place that we felt 00:19:17.280 --> 00:19:18.650 align:start position:0% exist weren't in the place that we felt that<00:19:17.340> they<00:19:17.520> needed<00:19:17.700> to<00:19:17.760> be<00:19:17.880> and<00:19:18.120> so<00:19:18.240> we<00:19:18.360> started 00:19:18.650 --> 00:19:18.660 align:start position:0% that they needed to be and so we started 00:19:18.660 --> 00:19:21.230 align:start position:0% that they needed to be and so we started trying<00:19:18.840> to<00:19:18.960> like<00:19:19.080> help<00:19:19.320> help<00:19:19.799> accelerate 00:19:21.230 --> 00:19:21.240 align:start position:0% trying to like help help accelerate 00:19:21.240 --> 00:19:22.789 align:start position:0% trying to like help help accelerate um that<00:19:22.020> path 00:19:22.789 --> 00:19:22.799 align:start position:0% um that path 00:19:22.799 --> 00:19:25.669 align:start position:0% um that path and<00:19:23.700> the<00:19:24.660> way<00:19:24.780> that<00:19:24.900> it<00:19:25.020> turned<00:19:25.320> out<00:19:25.380> I<00:19:25.559> think 00:19:25.669 --> 00:19:25.679 align:start position:0% and the way that it turned out I think 00:19:25.679 --> 00:19:27.250 align:start position:0% and the way that it turned out I think like<00:19:25.799> it's<00:19:26.160> better<00:19:26.400> than<00:19:26.640> it<00:19:26.820> could<00:19:26.880> have<00:19:27.000> been 00:19:27.250 --> 00:19:27.260 align:start position:0% like it's better than it could have been 00:19:27.260 --> 00:19:29.570 align:start position:0% like it's better than it could have been I<00:19:28.260> would<00:19:28.500> have<00:19:28.620> been<00:19:28.740> very<00:19:28.980> curious<00:19:29.280> to<00:19:29.460> see 00:19:29.570 --> 00:19:29.580 align:start position:0% I would have been very curious to see 00:19:29.580 --> 00:19:31.610 align:start position:0% I would have been very curious to see like<00:19:29.820> what<00:19:30.299> in<00:19:30.480> you<00:19:30.720> know<00:19:30.840> institutions<00:19:31.320> would 00:19:31.610 --> 00:19:31.620 align:start position:0% like what in you know institutions would 00:19:31.620 --> 00:19:34.310 align:start position:0% like what in you know institutions would have<00:19:31.740> created<00:19:32.039> their<00:19:32.460> own<00:19:32.580> Mev<00:19:33.120> boost<00:19:33.360> had 00:19:34.310 --> 00:19:34.320 align:start position:0% have created their own Mev boost had 00:19:34.320 --> 00:19:37.250 align:start position:0% have created their own Mev boost had this<00:19:34.860> like<00:19:35.039> open<00:19:35.340> source<00:19:36.000> public<00:19:36.299> thing<00:19:36.900> not 00:19:37.250 --> 00:19:37.260 align:start position:0% this like open source public thing not 00:19:37.260 --> 00:19:39.169 align:start position:0% this like open source public thing not existed<00:19:37.740> because<00:19:38.400> I<00:19:38.640> think<00:19:38.760> that<00:19:38.880> there<00:19:39.059> is 00:19:39.169 --> 00:19:39.179 align:start position:0% existed because I think that there is 00:19:39.179 --> 00:19:40.970 align:start position:0% existed because I think that there is enough<00:19:39.299> money<00:19:39.539> in<00:19:39.780> this<00:19:39.900> industry<00:19:40.200> that<00:19:40.620> some 00:19:40.970 --> 00:19:40.980 align:start position:0% enough money in this industry that some 00:19:40.980 --> 00:19:41.990 align:start position:0% enough money in this industry that some of<00:19:41.100> these<00:19:41.220> big<00:19:41.340> stickers<00:19:41.700> would<00:19:41.880> have 00:19:41.990 --> 00:19:42.000 align:start position:0% of these big stickers would have 00:19:42.000 --> 00:19:43.310 align:start position:0% of these big stickers would have realized<00:19:42.240> you<00:19:42.419> know<00:19:42.480> there's<00:19:42.720> no<00:19:42.900> way<00:19:43.020> for<00:19:43.140> us 00:19:43.310 --> 00:19:43.320 align:start position:0% realized you know there's no way for us 00:19:43.320 --> 00:19:44.870 align:start position:0% realized you know there's no way for us to<00:19:43.380> extract<00:19:43.679> the<00:19:43.799> movie<00:19:43.919> anymore<00:19:44.220> let's 00:19:44.870 --> 00:19:44.880 align:start position:0% to extract the movie anymore let's 00:19:44.880 --> 00:19:46.909 align:start position:0% to extract the movie anymore let's create<00:19:45.240> some<00:19:45.660> centralized<00:19:46.260> endpoint<00:19:46.679> for 00:19:46.909 --> 00:19:46.919 align:start position:0% create some centralized endpoint for 00:19:46.919 --> 00:19:48.830 align:start position:0% create some centralized endpoint for people<00:19:47.100> to<00:19:47.280> send<00:19:47.460> bundles<00:19:47.820> to<00:19:48.000> and<00:19:48.240> we'll<00:19:48.660> just 00:19:48.830 --> 00:19:48.840 align:start position:0% people to send bundles to and we'll just 00:19:48.840 --> 00:19:51.529 align:start position:0% people to send bundles to and we'll just extract<00:19:49.140> it<00:19:49.320> for<00:19:49.500> our<00:19:49.679> customers<00:19:50.100> and<00:19:50.820> you 00:19:51.529 --> 00:19:51.539 align:start position:0% extract it for our customers and you 00:19:51.539 --> 00:19:53.450 align:start position:0% extract it for our customers and you know<00:19:51.600> Screw<00:19:52.440> all<00:19:52.559> the<00:19:52.740> rest<00:19:52.860> of<00:19:52.980> the<00:19:53.039> stakers 00:19:53.450 --> 00:19:53.460 align:start position:0% know Screw all the rest of the stakers 00:19:53.460 --> 00:19:55.370 align:start position:0% know Screw all the rest of the stakers they<00:19:53.700> can<00:19:53.880> figure<00:19:54.120> out<00:19:54.299> their<00:19:54.480> own<00:19:54.600> ways<00:19:54.900> so 00:19:55.370 --> 00:19:55.380 align:start position:0% they can figure out their own ways so 00:19:55.380 --> 00:19:57.350 align:start position:0% they can figure out their own ways so it's<00:19:55.919> not<00:19:56.039> where<00:19:56.220> we<00:19:56.340> want<00:19:56.520> it<00:19:56.640> to<00:19:56.700> be<00:19:56.820> today<00:19:57.000> we 00:19:57.350 --> 00:19:57.360 align:start position:0% it's not where we want it to be today we 00:19:57.360 --> 00:19:58.970 align:start position:0% it's not where we want it to be today we want<00:19:57.480> to<00:19:57.600> improve<00:19:57.900> boost<00:19:58.380> and<00:19:58.620> make<00:19:58.740> it<00:19:58.860> better 00:19:58.970 --> 00:19:58.980 align:start position:0% want to improve boost and make it better 00:19:58.980 --> 00:20:01.370 align:start position:0% want to improve boost and make it better and<00:19:59.880> we<00:20:00.059> eventually<00:20:00.360> want<00:20:00.539> to<00:20:00.660> move<00:20:00.780> to<00:20:00.960> PBS 00:20:01.370 --> 00:20:01.380 align:start position:0% and we eventually want to move to PBS 00:20:01.380 --> 00:20:04.010 align:start position:0% and we eventually want to move to PBS where<00:20:01.679> it's<00:20:01.799> part<00:20:02.100> of<00:20:02.220> the<00:20:02.340> protocol<00:20:02.840> uh<00:20:03.840> and 00:20:04.010 --> 00:20:04.020 align:start position:0% where it's part of the protocol uh and 00:20:04.020 --> 00:20:05.510 align:start position:0% where it's part of the protocol uh and so<00:20:04.140> we're<00:20:04.260> just<00:20:04.440> working<00:20:04.559> towards<00:20:04.980> that<00:20:05.100> but 00:20:05.510 --> 00:20:05.520 align:start position:0% so we're just working towards that but 00:20:05.520 --> 00:20:07.490 align:start position:0% so we're just working towards that but and<00:20:05.760> I<00:20:05.940> think<00:20:06.059> like<00:20:06.240> also<00:20:06.720> you<00:20:07.260> know<00:20:07.320> with 00:20:07.490 --> 00:20:07.500 align:start position:0% and I think like also you know with 00:20:07.500 --> 00:20:10.010 align:start position:0% and I think like also you know with respect<00:20:07.799> to<00:20:08.179> thinking<00:20:09.179> that<00:20:09.299> the<00:20:09.600> Mev 00:20:10.010 --> 00:20:10.020 align:start position:0% respect to thinking that the Mev 00:20:10.020 --> 00:20:11.390 align:start position:0% respect to thinking that the Mev industry<00:20:10.380> was<00:20:10.620> going<00:20:10.740> to<00:20:10.799> build<00:20:10.980> all<00:20:11.220> this 00:20:11.390 --> 00:20:11.400 align:start position:0% industry was going to build all this 00:20:11.400 --> 00:20:13.549 align:start position:0% industry was going to build all this stuff<00:20:11.640> the<00:20:12.480> core<00:20:12.600> development<00:20:13.140> Community<00:20:13.380> is 00:20:13.549 --> 00:20:13.559 align:start position:0% stuff the core development Community is 00:20:13.559 --> 00:20:15.950 align:start position:0% stuff the core development Community is also<00:20:13.860> like<00:20:13.919> a<00:20:14.100> very<00:20:14.660> anti-finalization<00:20:15.660> of<00:20:15.840> a 00:20:15.950 --> 00:20:15.960 align:start position:0% also like a very anti-finalization of a 00:20:15.960 --> 00:20:18.830 align:start position:0% also like a very anti-finalization of a lot<00:20:16.080> of<00:20:16.200> things<00:20:16.380> and<00:20:17.100> so<00:20:17.400> to<00:20:18.000> a<00:20:18.240> degree<00:20:18.480> it<00:20:18.600> felt 00:20:18.830 --> 00:20:18.840 align:start position:0% lot of things and so to a degree it felt 00:20:18.840 --> 00:20:20.270 align:start position:0% lot of things and so to a degree it felt like<00:20:18.900> we<00:20:19.140> didn't<00:20:19.320> want<00:20:19.620> to<00:20:19.740> think<00:20:19.860> about<00:20:19.980> it<00:20:20.160> it 00:20:20.270 --> 00:20:20.280 align:start position:0% like we didn't want to think about it it 00:20:20.280 --> 00:20:22.250 align:start position:0% like we didn't want to think about it it felt<00:20:20.580> wrong<00:20:20.760> for<00:20:21.000> us<00:20:21.120> to<00:20:21.240> think<00:20:21.360> about<00:20:21.539> Mev<00:20:22.080> in 00:20:22.250 --> 00:20:22.260 align:start position:0% felt wrong for us to think about Mev in 00:20:22.260 --> 00:20:23.210 align:start position:0% felt wrong for us to think about Mev in a<00:20:22.380> lot<00:20:22.440> of<00:20:22.500> cases 00:20:23.210 --> 00:20:23.220 align:start position:0% a lot of cases 00:20:23.220 --> 00:20:25.490 align:start position:0% a lot of cases and<00:20:23.880> it<00:20:24.059> was<00:20:24.179> only<00:20:24.419> later<00:20:24.840> on<00:20:25.080> where<00:20:25.320> we 00:20:25.490 --> 00:20:25.500 align:start position:0% and it was only later on where we 00:20:25.500 --> 00:20:27.169 align:start position:0% and it was only later on where we realized<00:20:25.860> how<00:20:26.220> much<00:20:26.340> interplay<00:20:26.760> there<00:20:27.000> was 00:20:27.169 --> 00:20:27.179 align:start position:0% realized how much interplay there was 00:20:27.179 --> 00:20:29.630 align:start position:0% realized how much interplay there was between<00:20:27.480> censorship<00:20:28.260> and<00:20:28.799> Mev<00:20:29.220> and<00:20:29.460> the 00:20:29.630 --> 00:20:29.640 align:start position:0% between censorship and Mev and the 00:20:29.640 --> 00:20:31.250 align:start position:0% between censorship and Mev and the ability<00:20:29.820> to<00:20:30.059> produce<00:20:30.299> blocks<00:20:30.720> and<00:20:30.840> it<00:20:31.020> started 00:20:31.250 --> 00:20:31.260 align:start position:0% ability to produce blocks and it started 00:20:31.260 --> 00:20:32.870 align:start position:0% ability to produce blocks and it started to<00:20:31.320> just<00:20:31.380> unfold<00:20:31.799> very<00:20:32.100> naturally<00:20:32.460> over<00:20:32.700> the 00:20:32.870 --> 00:20:32.880 align:start position:0% to just unfold very naturally over the 00:20:32.880 --> 00:20:34.549 align:start position:0% to just unfold very naturally over the last<00:20:33.059> six<00:20:33.240> to<00:20:33.360> eight<00:20:33.539> months<00:20:33.840> and<00:20:34.320> I<00:20:34.440> think 00:20:34.549 --> 00:20:34.559 align:start position:0% last six to eight months and I think 00:20:34.559 --> 00:20:35.810 align:start position:0% last six to eight months and I think like<00:20:34.679> looking<00:20:34.980> back<00:20:35.220> if<00:20:35.460> we<00:20:35.580> would<00:20:35.700> have 00:20:35.810 --> 00:20:35.820 align:start position:0% like looking back if we would have 00:20:35.820 --> 00:20:38.150 align:start position:0% like looking back if we would have understood<00:20:36.179> those<00:20:36.480> things<00:20:36.600> two<00:20:36.840> years<00:20:37.020> ago<00:20:37.380> we 00:20:38.150 --> 00:20:38.160 align:start position:0% understood those things two years ago we 00:20:38.160 --> 00:20:40.130 align:start position:0% understood those things two years ago we probably<00:20:38.520> would<00:20:38.760> have<00:20:38.940> thought<00:20:39.179> a<00:20:39.480> lot<00:20:39.840> harder 00:20:40.130 --> 00:20:40.140 align:start position:0% probably would have thought a lot harder 00:20:40.140 --> 00:20:41.930 align:start position:0% probably would have thought a lot harder about<00:20:40.320> how<00:20:40.679> to<00:20:40.919> think<00:20:41.280> about<00:20:41.460> this<00:20:41.700> with 00:20:41.930 --> 00:20:41.940 align:start position:0% about how to think about this with 00:20:41.940 --> 00:20:43.549 align:start position:0% about how to think about this with respect<00:20:42.240> to<00:20:42.360> the<00:20:42.539> merge<00:20:42.840> and<00:20:42.960> maybe<00:20:43.260> how<00:20:43.440> to 00:20:43.549 --> 00:20:43.559 align:start position:0% respect to the merge and maybe how to 00:20:43.559 --> 00:20:44.870 align:start position:0% respect to the merge and maybe how to integrate<00:20:43.980> some<00:20:44.160> of<00:20:44.280> this<00:20:44.400> stuff<00:20:44.580> a<00:20:44.760> little 00:20:44.870 --> 00:20:44.880 align:start position:0% integrate some of this stuff a little 00:20:44.880 --> 00:20:51.289 align:start position:0% integrate some of this stuff a little bit<00:20:44.940> more<00:20:45.120> natively<00:20:45.539> uh<00:20:46.140> into<00:20:46.500> clients 00:20:51.289 --> 00:20:51.299 align:start position:0% 00:20:51.299 --> 00:20:53.510 align:start position:0% yeah<00:20:52.020> and<00:20:52.320> I<00:20:52.380> guess<00:20:52.919> um 00:20:53.510 --> 00:20:53.520 align:start position:0% yeah and I guess um 00:20:53.520 --> 00:20:56.210 align:start position:0% yeah and I guess um yes<00:20:54.179> talking<00:20:54.539> about<00:20:54.840> like<00:20:55.140> the<00:20:55.620> design<00:20:55.799> of<00:20:56.039> the 00:20:56.210 --> 00:20:56.220 align:start position:0% yes talking about like the design of the 00:20:56.220 --> 00:20:57.650 align:start position:0% yes talking about like the design of the whole<00:20:56.400> thing<00:20:56.640> I'm<00:20:56.940> curious<00:20:57.240> to<00:20:57.299> hear<00:20:57.419> like 00:20:57.650 --> 00:20:57.660 align:start position:0% whole thing I'm curious to hear like 00:20:57.660 --> 00:20:59.750 align:start position:0% whole thing I'm curious to hear like Proto<00:20:58.260> Macau<00:20:58.679> you<00:20:58.919> both<00:20:59.160> spend<00:20:59.400> a<00:20:59.520> bunch<00:20:59.700> of 00:20:59.750 --> 00:20:59.760 align:start position:0% Proto Macau you both spend a bunch of 00:20:59.760 --> 00:21:01.669 align:start position:0% Proto Macau you both spend a bunch of time<00:20:59.940> like<00:21:00.179> early<00:21:00.539> on<00:21:00.900> with<00:21:01.260> like<00:21:01.440> the<00:21:01.559> engine 00:21:01.669 --> 00:21:01.679 align:start position:0% time like early on with like the engine 00:21:01.679 --> 00:21:04.789 align:start position:0% time like early on with like the engine API<00:21:02.280> and<00:21:02.640> and<00:21:02.940> specking<00:21:03.419> out<00:21:03.539> of<00:21:03.660> that<00:21:03.780> but 00:21:04.789 --> 00:21:04.799 align:start position:0% API and and specking out of that but 00:21:04.799 --> 00:21:06.529 align:start position:0% API and and specking out of that but um<00:21:04.860> yeah<00:21:05.280> Miguel<00:21:05.700> do<00:21:06.000> you<00:21:06.120> want<00:21:06.179> to<00:21:06.299> just<00:21:06.419> like 00:21:06.529 --> 00:21:06.539 align:start position:0% um yeah Miguel do you want to just like 00:21:06.539 --> 00:21:08.029 align:start position:0% um yeah Miguel do you want to just like walk<00:21:06.720> us<00:21:06.900> through<00:21:07.140> like 00:21:08.029 --> 00:21:08.039 align:start position:0% walk us through like 00:21:08.039 --> 00:21:10.310 align:start position:0% walk us through like how<00:21:08.340> do<00:21:08.520> we<00:21:08.640> come<00:21:08.880> up<00:21:09.000> with<00:21:09.240> the<00:21:09.360> merge<00:21:09.780> like 00:21:10.310 --> 00:21:10.320 align:start position:0% how do we come up with the merge like 00:21:10.320 --> 00:21:13.310 align:start position:0% how do we come up with the merge like how<00:21:10.559> do<00:21:10.799> we<00:21:10.919> how<00:21:11.160> do<00:21:11.340> we<00:21:11.460> get<00:21:11.640> here 00:21:13.310 --> 00:21:13.320 align:start position:0% how do we how do we get here 00:21:13.320 --> 00:21:18.350 align:start position:0% how do we how do we get here yeah<00:21:13.640> hey<00:21:14.640> ah<00:21:15.240> okay<00:21:16.200> so<00:21:16.559> sorry<00:21:17.460> like<00:21:17.880> for<00:21:18.179> me 00:21:18.350 --> 00:21:18.360 align:start position:0% yeah hey ah okay so sorry like for me 00:21:18.360 --> 00:21:19.970 align:start position:0% yeah hey ah okay so sorry like for me the<00:21:18.660> merge<00:21:18.960> started 00:21:19.970 --> 00:21:19.980 align:start position:0% the merge started 00:21:19.980 --> 00:21:23.390 align:start position:0% the merge started two<00:21:20.460> and<00:21:20.580> a<00:21:20.700> half<00:21:20.700> years<00:21:21.000> ago<00:21:21.419> like<00:21:22.140> roughly<00:21:22.679> at 00:21:23.390 --> 00:21:23.400 align:start position:0% two and a half years ago like roughly at 00:21:23.400 --> 00:21:26.750 align:start position:0% two and a half years ago like roughly at this<00:21:23.700> moment<00:21:24.000> in<00:21:24.179> time<00:21:24.440> and<00:21:25.440> uh<00:21:25.799> yeah<00:21:26.100> by<00:21:26.520> that 00:21:26.750 --> 00:21:26.760 align:start position:0% this moment in time and uh yeah by that 00:21:26.760 --> 00:21:29.450 align:start position:0% this moment in time and uh yeah by that time<00:21:26.940> it<00:21:27.240> was<00:21:27.419> like<00:21:27.720> an<00:21:27.960> idea<00:21:28.260> of<00:21:28.500> the<00:21:29.039> two-way 00:21:29.450 --> 00:21:29.460 align:start position:0% time it was like an idea of the two-way 00:21:29.460 --> 00:21:32.330 align:start position:0% time it was like an idea of the two-way Bridge<00:21:29.700> of<00:21:30.179> bringing<00:21:30.600> the<00:21:31.080> um<00:21:31.080> Casper<00:21:31.860> F<00:21:32.039> of<00:21:32.159> G 00:21:32.330 --> 00:21:32.340 align:start position:0% Bridge of bringing the um Casper F of G 00:21:32.340 --> 00:21:34.010 align:start position:0% Bridge of bringing the um Casper F of G as<00:21:32.580> a<00:21:32.760> frame<00:21:32.880> analysis<00:21:33.360> Gadget<00:21:33.720> from<00:21:33.900> the 00:21:34.010 --> 00:21:34.020 align:start position:0% as a frame analysis Gadget from the 00:21:34.020 --> 00:21:36.590 align:start position:0% as a frame analysis Gadget from the beacon<00:21:34.440> chain<00:21:34.620> to<00:21:34.919> the<00:21:35.400> um<00:21:35.400> the<00:21:36.059> proof<00:21:36.419> work 00:21:36.590 --> 00:21:36.600 align:start position:0% beacon chain to the um the proof work 00:21:36.600 --> 00:21:38.029 align:start position:0% beacon chain to the um the proof work chain 00:21:38.029 --> 00:21:38.039 align:start position:0% chain 00:21:38.039 --> 00:21:40.490 align:start position:0% chain um<00:21:38.100> that<00:21:38.580> was<00:21:39.360> the<00:21:39.539> Australian<00:21:39.900> point<00:21:40.140> and 00:21:40.490 --> 00:21:40.500 align:start position:0% um that was the Australian point and 00:21:40.500 --> 00:21:42.710 align:start position:0% um that was the Australian point and there<00:21:40.620> was<00:21:40.740> an<00:21:40.919> idea<00:21:41.159> of<00:21:41.340> like<00:21:41.520> actually 00:21:42.710 --> 00:21:42.720 align:start position:0% there was an idea of like actually 00:21:42.720 --> 00:21:43.810 align:start position:0% there was an idea of like actually um 00:21:43.810 --> 00:21:43.820 align:start position:0% um 00:21:43.820 --> 00:21:46.669 align:start position:0% um uh<00:21:44.820> transition<00:21:45.539> in<00:21:45.780> the<00:21:45.960> proof<00:21:46.200> of<00:21:46.260> work<00:21:46.440> chain 00:21:46.669 --> 00:21:46.679 align:start position:0% uh transition in the proof of work chain 00:21:46.679 --> 00:21:49.430 align:start position:0% uh transition in the proof of work chain eventually<00:21:47.159> to<00:21:47.460> the<00:21:47.700> one<00:21:48.059> of<00:21:48.179> the<00:21:48.299> shards<00:21:48.780> that 00:21:49.430 --> 00:21:49.440 align:start position:0% eventually to the one of the shards that 00:21:49.440 --> 00:21:54.409 align:start position:0% eventually to the one of the shards that was<00:21:50.120> not<00:21:51.120> yet<00:21:51.360> designed<00:21:52.140> by<00:21:52.620> that<00:21:52.799> time<00:21:53.120> and<00:21:54.120> uh 00:21:54.409 --> 00:21:54.419 align:start position:0% was not yet designed by that time and uh 00:21:54.419 --> 00:21:56.990 align:start position:0% was not yet designed by that time and uh yeah<00:21:54.960> it<00:21:55.260> was<00:21:55.440> like<00:21:55.679> a<00:21:55.860> long<00:21:55.980> journey<00:21:56.400> I<00:21:56.700> can't 00:21:56.990 --> 00:21:57.000 align:start position:0% yeah it was like a long journey I can't 00:21:57.000 --> 00:22:00.230 align:start position:0% yeah it was like a long journey I can't recall<00:21:57.539> everything<00:21:58.020> that<00:21:58.559> has<00:21:58.799> happened<00:21:59.240> uh 00:22:00.230 --> 00:22:00.240 align:start position:0% recall everything that has happened uh 00:22:00.240 --> 00:22:03.470 align:start position:0% recall everything that has happened uh like<00:22:01.080> during<00:22:01.980> this<00:22:02.400> more<00:22:02.940> than<00:22:03.120> two<00:22:03.299> years 00:22:03.470 --> 00:22:03.480 align:start position:0% like during this more than two years 00:22:03.480 --> 00:22:06.710 align:start position:0% like during this more than two years period<00:22:04.020> of<00:22:04.679> time<00:22:04.919> but<00:22:05.700> one<00:22:06.179> thing<00:22:06.299> that<00:22:06.539> I 00:22:06.710 --> 00:22:06.720 align:start position:0% period of time but one thing that I 00:22:06.720 --> 00:22:10.070 align:start position:0% period of time but one thing that I would<00:22:06.900> just<00:22:07.080> like<00:22:07.320> to<00:22:07.860> mention<00:22:08.640> here<00:22:09.059> like<00:22:09.539> my 00:22:10.070 --> 00:22:10.080 align:start position:0% would just like to mention here like my 00:22:10.080 --> 00:22:11.930 align:start position:0% would just like to mention here like my key<00:22:10.320> takeaway<00:22:10.740> one<00:22:11.100> of<00:22:11.220> the<00:22:11.340> key<00:22:11.460> takeaways 00:22:11.930 --> 00:22:11.940 align:start position:0% key takeaway one of the key takeaways 00:22:11.940 --> 00:22:14.930 align:start position:0% key takeaway one of the key takeaways from<00:22:12.240> the<00:22:12.480> working<00:22:13.020> on<00:22:13.260> the<00:22:13.380> merge<00:22:13.799> project<00:22:14.039> is 00:22:14.930 --> 00:22:14.940 align:start position:0% from the working on the merge project is 00:22:14.940 --> 00:22:17.810 align:start position:0% from the working on the merge project is that<00:22:15.299> retrospectively 00:22:17.810 --> 00:22:17.820 align:start position:0% that retrospectively 00:22:17.820 --> 00:22:21.049 align:start position:0% that retrospectively um<00:22:17.880> what<00:22:18.419> what<00:22:18.600> I<00:22:18.960> can<00:22:19.679> um<00:22:19.740> yeah<00:22:20.100> recall<00:22:20.640> like 00:22:21.049 --> 00:22:21.059 align:start position:0% um what what I can um yeah recall like 00:22:21.059 --> 00:22:24.350 align:start position:0% um what what I can um yeah recall like the<00:22:21.299> first<00:22:21.740> collaboration<00:22:22.740> with<00:22:23.340> other<00:22:23.700> some 00:22:24.350 --> 00:22:24.360 align:start position:0% the first collaboration with other some 00:22:24.360 --> 00:22:26.029 align:start position:0% the first collaboration with other some somebody<00:22:24.659> else<00:22:24.960> working<00:22:25.260> on<00:22:25.559> the<00:22:25.679> same<00:22:25.860> space 00:22:26.029 --> 00:22:26.039 align:start position:0% somebody else working on the same space 00:22:26.039 --> 00:22:28.669 align:start position:0% somebody else working on the same space was<00:22:26.460> uh<00:22:26.940> collaborating<00:22:27.720> with<00:22:28.020> Guillaume 00:22:28.669 --> 00:22:28.679 align:start position:0% was uh collaborating with Guillaume 00:22:28.679 --> 00:22:31.549 align:start position:0% was uh collaborating with Guillaume guillaum<00:22:29.580> prototype<00:22:30.539> did<00:22:30.900> basically<00:22:31.320> the 00:22:31.549 --> 00:22:31.559 align:start position:0% guillaum prototype did basically the 00:22:31.559 --> 00:22:33.890 align:start position:0% guillaum prototype did basically the first<00:22:31.740> execution<00:22:32.220> layer<00:22:32.640> client<00:22:32.880> was<00:22:33.659> not 00:22:33.890 --> 00:22:33.900 align:start position:0% first execution layer client was not 00:22:33.900 --> 00:22:37.250 align:start position:0% first execution layer client was not called<00:22:34.140> that<00:22:34.620> by<00:22:35.340> that<00:22:35.460> time<00:22:35.700> but<00:22:35.940> anyway<00:22:36.260> it 00:22:37.250 --> 00:22:37.260 align:start position:0% called that by that time but anyway it 00:22:37.260 --> 00:22:40.090 align:start position:0% called that by that time but anyway it like<00:22:37.440> made<00:22:37.799> me<00:22:38.039> much<00:22:38.460> easier<00:22:38.880> to<00:22:39.299> like 00:22:40.090 --> 00:22:40.100 align:start position:0% like made me much easier to like 00:22:40.100 --> 00:22:42.289 align:start position:0% like made me much easier to like prototype<00:22:41.100> the<00:22:41.280> whole<00:22:41.460> thing<00:22:41.700> like<00:22:42.059> the 00:22:42.289 --> 00:22:42.299 align:start position:0% prototype the whole thing like the 00:22:42.299 --> 00:22:44.630 align:start position:0% prototype the whole thing like the consensus<00:22:42.780> interact<00:22:43.500> with<00:22:44.100> the<00:22:44.220> execution 00:22:44.630 --> 00:22:44.640 align:start position:0% consensus interact with the execution 00:22:44.640 --> 00:22:48.470 align:start position:0% consensus interact with the execution layer<00:22:45.500> it<00:22:46.500> was<00:22:46.620> not<00:22:46.799> done<00:22:47.100> by<00:22:47.340> engine<00:22:47.760> API<00:22:48.299> by 00:22:48.470 --> 00:22:48.480 align:start position:0% layer it was not done by engine API by 00:22:48.480 --> 00:22:51.289 align:start position:0% layer it was not done by engine API by that<00:22:48.659> time<00:22:48.840> but<00:22:49.140> anyway<00:22:49.500> it<00:22:50.280> was<00:22:50.460> like<00:22:50.760> yeah 00:22:51.289 --> 00:22:51.299 align:start position:0% that time but anyway it was like yeah 00:22:51.299 --> 00:22:53.570 align:start position:0% that time but anyway it was like yeah the<00:22:51.600> old<00:22:51.780> idea<00:22:52.260> of<00:22:52.380> like<00:22:52.559> putting<00:22:52.980> it<00:22:53.159> in<00:22:53.400> a 00:22:53.570 --> 00:22:53.580 align:start position:0% the old idea of like putting it in a 00:22:53.580 --> 00:22:56.570 align:start position:0% the old idea of like putting it in a chart<00:22:53.760> and<00:22:54.360> make<00:22:54.600> it<00:22:54.840> work<00:22:55.020> somehow<00:22:55.679> so<00:22:56.280> we<00:22:56.400> did 00:22:56.570 --> 00:22:56.580 align:start position:0% chart and make it work somehow so we did 00:22:56.580 --> 00:22:59.810 align:start position:0% chart and make it work somehow so we did this<00:22:56.820> prototype<00:22:57.480> then<00:22:58.380> yeah<00:22:59.039> after<00:22:59.400> some 00:22:59.810 --> 00:22:59.820 align:start position:0% this prototype then yeah after some 00:22:59.820 --> 00:23:01.549 align:start position:0% this prototype then yeah after some progress<00:23:00.179> on<00:23:00.419> the<00:23:00.539> merge<00:23:00.840> specs<00:23:01.260> and<00:23:01.320> the 00:23:01.549 --> 00:23:01.559 align:start position:0% progress on the merge specs and the 00:23:01.559 --> 00:23:04.310 align:start position:0% progress on the merge specs and the ideas<00:23:01.860> then<00:23:02.340> protopied<00:23:03.179> with<00:23:03.539> like<00:23:03.659> rheanism 00:23:04.310 --> 00:23:04.320 align:start position:0% ideas then protopied with like rheanism 00:23:04.320 --> 00:23:07.549 align:start position:0% ideas then protopied with like rheanism project<00:23:04.620> so<00:23:05.520> just<00:23:05.820> you<00:23:06.120> know<00:23:06.240> forced<00:23:07.140> us<00:23:07.320> to 00:23:07.549 --> 00:23:07.559 align:start position:0% project so just you know forced us to 00:23:07.559 --> 00:23:11.090 align:start position:0% project so just you know forced us to make<00:23:08.520> the<00:23:08.760> first<00:23:08.940> version<00:23:09.299> of<00:23:09.720> engine<00:23:09.960> API<00:23:10.620> for 00:23:11.090 --> 00:23:11.100 align:start position:0% make the first version of engine API for 00:23:11.100 --> 00:23:12.710 align:start position:0% make the first version of engine API for the<00:23:11.340> do<00:23:11.460> you<00:23:11.640> remember<00:23:11.700> all<00:23:12.059> this<00:23:12.299> enormous 00:23:12.710 --> 00:23:12.720 align:start position:0% the do you remember all this enormous 00:23:12.720 --> 00:23:14.270 align:start position:0% the do you remember all this enormous amount<00:23:13.020> of<00:23:13.200> hours<00:23:13.500> you've<00:23:13.860> spent<00:23:14.039> the 00:23:14.270 --> 00:23:14.280 align:start position:0% amount of hours you've spent the 00:23:14.280 --> 00:23:16.010 align:start position:0% amount of hours you've spent the managing<00:23:14.760> this<00:23:14.880> project<00:23:15.120> and<00:23:15.419> driving<00:23:15.659> it 00:23:16.010 --> 00:23:16.020 align:start position:0% managing this project and driving it 00:23:16.020 --> 00:23:18.590 align:start position:0% managing this project and driving it through<00:23:16.260> it's<00:23:16.919> like<00:23:17.280> I<00:23:17.880> mean<00:23:18.000> I<00:23:18.240> can<00:23:18.360> talk 00:23:18.590 --> 00:23:18.600 align:start position:0% through it's like I mean I can talk 00:23:18.600 --> 00:23:21.490 align:start position:0% through it's like I mean I can talk about<00:23:18.720> that<00:23:19.080> I<00:23:19.679> would<00:23:20.039> want<00:23:20.220> to<00:23:20.400> First 00:23:21.490 --> 00:23:21.500 align:start position:0% about that I would want to First 00:23:21.500 --> 00:23:25.250 align:start position:0% about that I would want to First reiterate<00:23:22.500> over<00:23:23.059> the<00:23:24.059> first<00:23:24.299> moment<00:23:24.960> in<00:23:25.080> time 00:23:25.250 --> 00:23:25.260 align:start position:0% reiterate over the first moment in time 00:23:25.260 --> 00:23:27.289 align:start position:0% reiterate over the first moment in time most<00:23:25.500> that<00:23:25.740> we<00:23:25.919> developed<00:23:26.280> the<00:23:26.460> merge 00:23:27.289 --> 00:23:27.299 align:start position:0% most that we developed the merge 00:23:27.299 --> 00:23:30.230 align:start position:0% most that we developed the merge I<00:23:27.960> think<00:23:28.559> it<00:23:29.280> was 00:23:30.230 --> 00:23:30.240 align:start position:0% I think it was 00:23:30.240 --> 00:23:32.029 align:start position:0% I think it was um<00:23:30.299> before<00:23:30.659> coffee<00:23:31.080> before<00:23:31.679> the<00:23:31.919> whole 00:23:32.029 --> 00:23:32.039 align:start position:0% um before coffee before the whole 00:23:32.039 --> 00:23:35.690 align:start position:0% um before coffee before the whole pandemic<00:23:33.000> I<00:23:33.600> think<00:23:33.720> in<00:23:34.080> like<00:23:34.620> SBC<00:23:35.100> there<00:23:35.520> were 00:23:35.690 --> 00:23:35.700 align:start position:0% pandemic I think in like SBC there were 00:23:35.700 --> 00:23:38.270 align:start position:0% pandemic I think in like SBC there were still<00:23:35.880> discussions<00:23:36.299> about<00:23:36.480> ewasum<00:23:37.200> but<00:23:38.039> then 00:23:38.270 --> 00:23:38.280 align:start position:0% still discussions about ewasum but then 00:23:38.280 --> 00:23:40.190 align:start position:0% still discussions about ewasum but then less<00:23:38.460> than<00:23:38.580> a<00:23:38.760> month<00:23:38.880> later<00:23:39.120> in<00:23:39.720> Paris<00:23:40.020> during 00:23:40.190 --> 00:23:40.200 align:start position:0% less than a month later in Paris during 00:23:40.200 --> 00:23:41.390 align:start position:0% less than a month later in Paris during Evon<00:23:40.679> X 00:23:41.390 --> 00:23:41.400 align:start position:0% Evon X 00:23:41.400 --> 00:23:43.370 align:start position:0% Evon X discussions<00:23:41.880> afterwards 00:23:43.370 --> 00:23:43.380 align:start position:0% discussions afterwards 00:23:43.380 --> 00:23:46.730 align:start position:0% discussions afterwards eosm<00:23:44.280> or<00:23:44.580> like<00:23:44.700> the<00:23:44.880> ID<00:23:45.059> of<00:23:45.600> execution<00:23:46.200> starts 00:23:46.730 --> 00:23:46.740 align:start position:0% eosm or like the ID of execution starts 00:23:46.740 --> 00:23:49.610 align:start position:0% eosm or like the ID of execution starts was<00:23:46.919> basically<00:23:47.280> over<00:23:47.520> and<00:23:47.880> don't<00:23:48.120> forget<00:23:48.840> and 00:23:49.610 --> 00:23:49.620 align:start position:0% was basically over and don't forget and 00:23:49.620 --> 00:23:52.430 align:start position:0% was basically over and don't forget and these<00:23:50.340> discussions<00:23:50.700> between<00:23:51.179> you<00:23:51.720> and 00:23:52.430 --> 00:23:52.440 align:start position:0% these discussions between you and 00:23:52.440 --> 00:23:56.649 align:start position:0% these discussions between you and Guillaume<00:23:53.179> Danny<00:23:54.200> me<00:23:55.200> others<00:23:55.860> Brandon<00:23:56.280> also 00:23:56.649 --> 00:23:56.659 align:start position:0% Guillaume Danny me others Brandon also 00:23:56.659 --> 00:24:01.669 align:start position:0% Guillaume Danny me others Brandon also started<00:23:57.659> where<00:23:58.200> hey<00:23:58.799> maybe<00:23:59.240> we<00:24:00.240> can<00:24:00.679> prototype 00:24:01.669 --> 00:24:01.679 align:start position:0% started where hey maybe we can prototype 00:24:01.679 --> 00:24:05.029 align:start position:0% started where hey maybe we can prototype the<00:24:02.159> Catalyst<00:24:02.700> thing<00:24:03.000> with<00:24:03.600> the<00:24:04.080> evm<00:24:04.500> applied 00:24:05.029 --> 00:24:05.039 align:start position:0% the Catalyst thing with the evm applied 00:24:05.039 --> 00:24:06.230 align:start position:0% the Catalyst thing with the evm applied to<00:24:05.100> techu 00:24:06.230 --> 00:24:06.240 align:start position:0% to techu 00:24:06.240 --> 00:24:09.049 align:start position:0% to techu and<00:24:07.080> uh<00:24:07.320> yeah<00:24:07.620> like 00:24:09.049 --> 00:24:09.059 align:start position:0% and uh yeah like 00:24:09.059 --> 00:24:11.630 align:start position:0% and uh yeah like that's<00:24:09.539> kind<00:24:09.840> of<00:24:09.960> cool<00:24:10.080> but<00:24:10.620> I<00:24:10.799> took<00:24:11.039> that's 00:24:11.630 --> 00:24:11.640 align:start position:0% that's kind of cool but I took that's 00:24:11.640 --> 00:24:14.690 align:start position:0% that's kind of cool but I took that's two<00:24:12.059> thousand<00:24:12.780> twenty<00:24:13.440> it<00:24:13.620> took<00:24:13.799> a<00:24:13.980> year<00:24:14.159> more 00:24:14.690 --> 00:24:14.700 align:start position:0% two thousand twenty it took a year more 00:24:14.700 --> 00:24:16.909 align:start position:0% two thousand twenty it took a year more than<00:24:14.940> a<00:24:15.000> year<00:24:15.120> till<00:24:15.360> we<00:24:15.539> got<00:24:15.720> to<00:24:15.960> to<00:24:16.320> rayonism 00:24:16.909 --> 00:24:16.919 align:start position:0% than a year till we got to to rayonism 00:24:16.919 --> 00:24:20.149 align:start position:0% than a year till we got to to rayonism so<00:24:17.640> it's<00:24:17.760> a<00:24:17.940> huge<00:24:18.240> leap<00:24:18.600> already<00:24:19.200> where<00:24:19.799> things 00:24:20.149 --> 00:24:20.159 align:start position:0% so it's a huge leap already where things 00:24:20.159 --> 00:24:21.350 align:start position:0% so it's a huge leap already where things happened 00:24:21.350 --> 00:24:21.360 align:start position:0% happened 00:24:21.360 --> 00:24:24.350 align:start position:0% happened and<00:24:21.900> then<00:24:22.159> in<00:24:23.159> realism<00:24:23.580> where<00:24:23.820> in<00:24:24.240> this 00:24:24.350 --> 00:24:24.360 align:start position:0% and then in realism where in this 00:24:24.360 --> 00:24:26.810 align:start position:0% and then in realism where in this awkward<00:24:24.659> spots<00:24:25.200> where<00:24:25.799> alter<00:24:26.159> was<00:24:26.460> still<00:24:26.640> not 00:24:26.810 --> 00:24:26.820 align:start position:0% awkward spots where alter was still not 00:24:26.820 --> 00:24:29.990 align:start position:0% awkward spots where alter was still not shipped<00:24:27.240> and<00:24:27.900> London<00:24:28.260> was<00:24:28.500> still<00:24:28.679> not<00:24:28.799> chapped 00:24:29.990 --> 00:24:30.000 align:start position:0% shipped and London was still not chapped 00:24:30.000 --> 00:24:32.750 align:start position:0% shipped and London was still not chapped and<00:24:30.780> we<00:24:31.200> were<00:24:31.380> just<00:24:31.620> like<00:24:31.860> moment<00:24:32.460> in<00:24:32.640> time 00:24:32.750 --> 00:24:32.760 align:start position:0% and we were just like moment in time 00:24:32.760 --> 00:24:34.190 align:start position:0% and we were just like moment in time where<00:24:33.000> there's<00:24:33.240> this<00:24:33.480> stack<00:24:33.659> development 00:24:34.190 --> 00:24:34.200 align:start position:0% where there's this stack development 00:24:34.200 --> 00:24:36.890 align:start position:0% where there's this stack development where<00:24:35.039> you<00:24:35.159> have<00:24:35.280> to<00:24:35.400> convince<00:24:35.820> people 00:24:36.890 --> 00:24:36.900 align:start position:0% where you have to convince people 00:24:36.900 --> 00:24:39.590 align:start position:0% where you have to convince people that<00:24:37.620> they<00:24:37.860> need<00:24:38.100> to<00:24:38.280> dedicate<00:24:38.640> resources<00:24:39.240> on 00:24:39.590 --> 00:24:39.600 align:start position:0% that they need to dedicate resources on 00:24:39.600 --> 00:24:42.169 align:start position:0% that they need to dedicate resources on something<00:24:39.780> that's<00:24:40.080> not<00:24:40.320> the<00:24:40.500> main<00:24:40.679> hard<00:24:41.039> work 00:24:42.169 --> 00:24:42.179 align:start position:0% something that's not the main hard work 00:24:42.179 --> 00:24:44.570 align:start position:0% something that's not the main hard work to<00:24:42.840> make<00:24:43.080> some<00:24:43.260> kind<00:24:43.380> of<00:24:43.500> progress 00:24:44.570 --> 00:24:44.580 align:start position:0% to make some kind of progress 00:24:44.580 --> 00:24:47.630 align:start position:0% to make some kind of progress definitely<00:24:45.179> like<00:24:45.840> there<00:24:46.740> there<00:24:46.799> were<00:24:47.280> moments 00:24:47.630 --> 00:24:47.640 align:start position:0% definitely like there there were moments 00:24:47.640 --> 00:24:51.409 align:start position:0% definitely like there there were moments in<00:24:47.760> time<00:24:47.940> where<00:24:48.240> I<00:24:48.480> was<00:24:48.799> slightly<00:24:49.799> like 00:24:51.409 --> 00:24:51.419 align:start position:0% in time where I was slightly like 00:24:51.419 --> 00:24:54.890 align:start position:0% in time where I was slightly like yeah<00:24:51.840> out<00:24:52.679> of<00:24:52.860> my<00:24:53.039> humor<00:24:53.400> because<00:24:53.760> of<00:24:54.120> the<00:24:54.419> the 00:24:54.890 --> 00:24:54.900 align:start position:0% yeah out of my humor because of the the 00:24:54.900 --> 00:24:58.490 align:start position:0% yeah out of my humor because of the the way<00:24:55.140> the<00:24:56.100> the<00:24:56.480> these<00:24:57.480> calls<00:24:57.720> would<00:24:57.900> go<00:24:58.080> like 00:24:58.490 --> 00:24:58.500 align:start position:0% way the the these calls would go like 00:24:58.500 --> 00:24:59.990 align:start position:0% way the the these calls would go like for<00:24:58.679> a<00:24:58.799> month<00:24:58.919> we<00:24:59.100> were<00:24:59.340> thinking<00:24:59.640> of<00:24:59.760> it<00:24:59.880> like 00:24:59.990 --> 00:25:00.000 align:start position:0% for a month we were thinking of it like 00:25:00.000 --> 00:25:02.510 align:start position:0% for a month we were thinking of it like a<00:25:00.179> hackathon<00:25:00.600> where<00:25:00.960> okay<00:25:01.320> we<00:25:01.620> just<00:25:01.799> do<00:25:02.280> the 00:25:02.510 --> 00:25:02.520 align:start position:0% a hackathon where okay we just do the 00:25:02.520 --> 00:25:04.789 align:start position:0% a hackathon where okay we just do the Prototype<00:25:03.059> with<00:25:03.240> more<00:25:03.480> than<00:25:03.659> one<00:25:03.780> client 00:25:04.789 --> 00:25:04.799 align:start position:0% Prototype with more than one client 00:25:04.799 --> 00:25:07.549 align:start position:0% Prototype with more than one client and<00:25:05.700> Martin<00:25:06.120> often<00:25:06.659> it's<00:25:06.780> just<00:25:07.020> meant<00:25:07.260> that 00:25:07.549 --> 00:25:07.559 align:start position:0% and Martin often it's just meant that 00:25:07.559 --> 00:25:10.370 align:start position:0% and Martin often it's just meant that some<00:25:07.799> clients<00:25:08.159> would<00:25:08.400> not<00:25:08.640> go<00:25:09.240> and<00:25:09.780> join<00:25:10.080> these 00:25:10.370 --> 00:25:10.380 align:start position:0% some clients would not go and join these 00:25:10.380 --> 00:25:14.090 align:start position:0% some clients would not go and join these cars<00:25:10.740> to<00:25:11.039> even<00:25:11.220> just<00:25:11.460> get<00:25:11.580> a<00:25:12.059> glimpse<00:25:12.900> of<00:25:13.200> what 00:25:14.090 --> 00:25:14.100 align:start position:0% cars to even just get a glimpse of what 00:25:14.100 --> 00:25:16.610 align:start position:0% cars to even just get a glimpse of what we<00:25:14.340> were<00:25:14.520> trying<00:25:14.700> to<00:25:14.880> do<00:25:15.059> after<00:25:15.419> alter<00:25:16.380> and 00:25:16.610 --> 00:25:16.620 align:start position:0% we were trying to do after alter and 00:25:16.620 --> 00:25:18.649 align:start position:0% we were trying to do after alter and after<00:25:16.799> London<00:25:17.340> and<00:25:18.059> I<00:25:18.120> think<00:25:18.240> like<00:25:18.419> this 00:25:18.649 --> 00:25:18.659 align:start position:0% after London and I think like this 00:25:18.659 --> 00:25:21.649 align:start position:0% after London and I think like this disco-free<00:25:19.380> process<00:25:19.740> for<00:25:20.039> future<00:25:20.280> Forks<00:25:20.940> we 00:25:21.649 --> 00:25:21.659 align:start position:0% disco-free process for future Forks we 00:25:21.659 --> 00:25:23.270 align:start position:0% disco-free process for future Forks we can<00:25:21.840> improve<00:25:22.260> where 00:25:23.270 --> 00:25:23.280 align:start position:0% can improve where 00:25:23.280 --> 00:25:25.370 align:start position:0% can improve where that's<00:25:23.880> the<00:25:24.120> time<00:25:24.299> and<00:25:24.659> if<00:25:24.960> we<00:25:25.080> had<00:25:25.260> more 00:25:25.370 --> 00:25:25.380 align:start position:0% that's the time and if we had more 00:25:25.380 --> 00:25:26.690 align:start position:0% that's the time and if we had more people 00:25:26.690 --> 00:25:26.700 align:start position:0% people 00:25:26.700 --> 00:25:28.549 align:start position:0% people think<00:25:27.120> about<00:25:27.299> the<00:25:27.539> merge<00:25:27.960> we<00:25:28.200> could<00:25:28.380> have 00:25:28.549 --> 00:25:28.559 align:start position:0% think about the merge we could have 00:25:28.559 --> 00:25:31.250 align:start position:0% think about the merge we could have realized<00:25:29.100> that<00:25:29.400> hey<00:25:30.059> we<00:25:30.360> need<00:25:30.539> to<00:25:30.659> make<00:25:30.960> these 00:25:31.250 --> 00:25:31.260 align:start position:0% realized that hey we need to make these 00:25:31.260 --> 00:25:33.409 align:start position:0% realized that hey we need to make these communication<00:25:31.740> Channels<00:25:32.400> with<00:25:33.000> things<00:25:33.240> like 00:25:33.409 --> 00:25:33.419 align:start position:0% communication Channels with things like 00:25:33.419 --> 00:25:35.510 align:start position:0% communication Channels with things like flashbots<00:25:34.080> and<00:25:34.380> MFE 00:25:35.510 --> 00:25:35.520 align:start position:0% flashbots and MFE 00:25:35.520 --> 00:25:37.490 align:start position:0% flashbots and MFE verages<00:25:36.179> very<00:25:36.419> soon 00:25:37.490 --> 00:25:37.500 align:start position:0% verages very soon 00:25:37.500 --> 00:25:39.590 align:start position:0% verages very soon all<00:25:38.159> the<00:25:38.340> rest<00:25:38.460> it's<00:25:38.640> very<00:25:38.760> late<00:25:39.000> then<00:25:39.360> you've 00:25:39.590 --> 00:25:39.600 align:start position:0% all the rest it's very late then you've 00:25:39.600 --> 00:25:42.769 align:start position:0% all the rest it's very late then you've got<00:25:39.720> the<00:25:39.840> new<00:25:40.020> situations 00:25:42.769 --> 00:25:42.779 align:start position:0% 00:25:42.779 --> 00:25:45.289 align:start position:0% yeah<00:25:43.260> and<00:25:43.500> by<00:25:43.679> the<00:25:43.799> way<00:25:43.860> and<00:25:44.220> maybe<00:25:44.460> people<00:25:44.820> are 00:25:45.289 --> 00:25:45.299 align:start position:0% yeah and by the way and maybe people are 00:25:45.299 --> 00:25:47.570 align:start position:0% yeah and by the way and maybe people are going<00:25:45.600> to<00:25:45.779> join<00:25:46.140> us<00:25:46.260> for<00:25:46.620> the<00:25:46.799> last<00:25:46.919> session<00:25:47.220> so 00:25:47.570 --> 00:25:47.580 align:start position:0% going to join us for the last session so 00:25:47.580 --> 00:25:50.330 align:start position:0% going to join us for the last session so we<00:25:47.880> can<00:25:48.059> discuss<00:25:48.419> more<00:25:48.720> that<00:25:48.960> later<00:25:49.740> because 00:25:50.330 --> 00:25:50.340 align:start position:0% we can discuss more that later because 00:25:50.340 --> 00:25:52.610 align:start position:0% we can discuss more that later because Alex<00:25:50.820> he<00:25:51.419> just<00:25:51.600> text<00:25:51.779> me<00:25:52.020> that<00:25:52.140> he's<00:25:52.380> coming 00:25:52.610 --> 00:25:52.620 align:start position:0% Alex he just text me that he's coming 00:25:52.620 --> 00:25:55.370 align:start position:0% Alex he just text me that he's coming for<00:25:53.159> the<00:25:53.460> last<00:25:53.580> session<00:25:54.020> unfortunately<00:25:55.020> he 00:25:55.370 --> 00:25:55.380 align:start position:0% for the last session unfortunately he 00:25:55.380 --> 00:25:57.169 align:start position:0% for the last session unfortunately he did<00:25:55.559> not<00:25:55.740> make<00:25:55.919> it<00:25:56.039> here 00:25:57.169 --> 00:25:57.179 align:start position:0% did not make it here 00:25:57.179 --> 00:25:59.690 align:start position:0% did not make it here can<00:25:57.900> I<00:25:58.020> continue<00:25:58.200> on<00:25:58.559> that<00:25:58.740> yeah<00:25:59.039> it's<00:25:59.340> just<00:25:59.520> a 00:25:59.690 --> 00:25:59.700 align:start position:0% can I continue on that yeah it's just a 00:25:59.700 --> 00:26:02.810 align:start position:0% can I continue on that yeah it's just a few<00:25:59.820> few<00:26:00.140> sentences<00:26:01.140> left<00:26:01.380> from<00:26:01.919> my<00:26:02.100> end<00:26:02.220> okay 00:26:02.810 --> 00:26:02.820 align:start position:0% few few sentences left from my end okay 00:26:02.820 --> 00:26:05.090 align:start position:0% few few sentences left from my end okay so<00:26:03.120> after<00:26:03.360> any<00:26:03.720> this<00:26:04.320> is<00:26:04.380> the<00:26:04.559> first<00:26:04.679> time<00:26:04.919> we 00:26:05.090 --> 00:26:05.100 align:start position:0% so after any this is the first time we 00:26:05.100 --> 00:26:07.549 align:start position:0% so after any this is the first time we had<00:26:05.340> like<00:26:05.640> engaged<00:26:06.419> more<00:26:06.659> client<00:26:07.020> developers 00:26:07.549 --> 00:26:07.559 align:start position:0% had like engaged more client developers 00:26:07.559 --> 00:26:09.230 align:start position:0% had like engaged more client developers and<00:26:07.740> client<00:26:07.980> development<00:26:08.400> teams<00:26:08.760> into<00:26:09.000> that 00:26:09.230 --> 00:26:09.240 align:start position:0% and client development teams into that 00:26:09.240 --> 00:26:11.630 align:start position:0% and client development teams into that we<00:26:09.900> had<00:26:10.140> to<00:26:10.260> written<00:26:10.559> to<00:26:10.980> write<00:26:11.100> us<00:26:11.279> back<00:26:11.460> of 00:26:11.630 --> 00:26:11.640 align:start position:0% we had to written to write us back of 00:26:11.640 --> 00:26:14.149 align:start position:0% we had to written to write us back of the<00:26:11.820> engine<00:26:11.940> API<00:26:12.480> like<00:26:12.720> to<00:26:12.960> make<00:26:13.140> this<00:26:13.500> you 00:26:14.149 --> 00:26:14.159 align:start position:0% the engine API like to make this you 00:26:14.159 --> 00:26:15.890 align:start position:0% the engine API like to make this you know<00:26:14.279> some<00:26:14.760> kind<00:26:14.940> of<00:26:15.059> standardized<00:26:15.659> or 00:26:15.890 --> 00:26:15.900 align:start position:0% know some kind of standardized or 00:26:15.900 --> 00:26:18.950 align:start position:0% know some kind of standardized or whatever<00:26:16.340> it<00:26:17.340> was<00:26:17.460> even<00:26:17.700> before<00:26:18.000> Emperor<00:26:18.659> it 00:26:18.950 --> 00:26:18.960 align:start position:0% whatever it was even before Emperor it 00:26:18.960 --> 00:26:21.769 align:start position:0% whatever it was even before Emperor it was<00:26:19.080> like<00:26:19.320> uh<00:26:19.919> like<00:26:20.220> more<00:26:20.580> than<00:26:20.880> one<00:26:21.240> year<00:26:21.419> ago 00:26:21.769 --> 00:26:21.779 align:start position:0% was like uh like more than one year ago 00:26:21.779 --> 00:26:23.690 align:start position:0% was like uh like more than one year ago like<00:26:22.380> yeah 00:26:23.690 --> 00:26:23.700 align:start position:0% like yeah 00:26:23.700 --> 00:26:26.210 align:start position:0% like yeah yeah<00:26:24.179> April<00:26:24.900> and<00:26:25.020> May<00:26:25.260> what<00:26:25.679> do<00:26:25.860> you<00:26:25.860> mean<00:26:25.980> one 00:26:26.210 --> 00:26:26.220 align:start position:0% yeah April and May what do you mean one 00:26:26.220 --> 00:26:30.049 align:start position:0% yeah April and May what do you mean one yeah<00:26:26.520> it<00:26:26.940> was<00:26:27.120> great<00:26:27.320> so<00:26:28.320> then<00:26:28.559> Emperor<00:26:29.460> then 00:26:30.049 --> 00:26:30.059 align:start position:0% yeah it was great so then Emperor then 00:26:30.059 --> 00:26:32.930 align:start position:0% yeah it was great so then Emperor then uh<00:26:30.419> yeah<00:26:30.720> all<00:26:30.960> this<00:26:31.320> of<00:26:31.620> chain<00:26:31.740> events<00:26:32.340> uh<00:26:32.700> off 00:26:32.930 --> 00:26:32.940 align:start position:0% uh yeah all this of chain events uh off 00:26:32.940 --> 00:26:36.649 align:start position:0% uh yeah all this of chain events uh off chains<00:26:33.419> sorry<00:26:33.600> of<00:26:33.900> sites<00:26:34.799> of<00:26:35.520> of<00:26:35.659> offline 00:26:36.649 --> 00:26:36.659 align:start position:0% chains sorry of sites of of offline 00:26:36.659 --> 00:26:40.730 align:start position:0% chains sorry of sites of of offline events<00:26:37.260> it's<00:26:37.740> a<00:26:38.400> really<00:26:38.820> huge 00:26:40.730 --> 00:26:40.740 align:start position:0% events it's a really huge 00:26:40.740 --> 00:26:44.750 align:start position:0% events it's a really huge um<00:26:40.860> facility<00:26:41.520> of<00:26:42.000> the<00:26:42.179> progress<00:26:42.679> and<00:26:43.679> all<00:26:43.980> the 00:26:44.750 --> 00:26:44.760 align:start position:0% um facility of the progress and all the 00:26:44.760 --> 00:26:47.630 align:start position:0% um facility of the progress and all the um developers<00:26:45.419> in<00:26:46.020> one<00:26:46.500> place<00:26:46.860> talking<00:26:47.400> to 00:26:47.630 --> 00:26:47.640 align:start position:0% um developers in one place talking to 00:26:47.640 --> 00:26:50.269 align:start position:0% um developers in one place talking to each<00:26:47.880> other<00:26:48.000> in<00:26:48.299> person<00:26:48.539> I<00:26:49.380> think<00:26:49.500> it's<00:26:49.860> really 00:26:50.269 --> 00:26:50.279 align:start position:0% each other in person I think it's really 00:26:50.279 --> 00:26:53.149 align:start position:0% each other in person I think it's really helps<00:26:50.760> to<00:26:51.179> collaborate<00:26:51.840> on<00:26:52.080> the<00:26:52.200> things<00:26:52.380> even 00:26:53.149 --> 00:26:53.159 align:start position:0% helps to collaborate on the things even 00:26:53.159 --> 00:26:56.210 align:start position:0% helps to collaborate on the things even after<00:26:53.520> the<00:26:53.760> event<00:26:54.059> and<00:26:54.659> when<00:26:54.960> we<00:26:55.140> were<00:26:55.320> like<00:26:55.980> on 00:26:56.210 --> 00:26:56.220 align:start position:0% after the event and when we were like on 00:26:56.220 --> 00:26:57.769 align:start position:0% after the event and when we were like on the<00:26:56.279> internet 00:26:57.769 --> 00:26:57.779 align:start position:0% the internet 00:26:57.779 --> 00:26:59.090 align:start position:0% the internet um back<00:26:58.020> to<00:26:58.200> work 00:26:59.090 --> 00:26:59.100 align:start position:0% um back to work 00:26:59.100 --> 00:27:01.250 align:start position:0% um back to work yeah<00:26:59.760> and 00:27:01.250 --> 00:27:01.260 align:start position:0% yeah and 00:27:01.260 --> 00:27:03.710 align:start position:0% yeah and as<00:27:01.860> has<00:27:02.400> been<00:27:02.520> mentioned<00:27:02.820> tests<00:27:03.299> and<00:27:03.360> efforts 00:27:03.710 --> 00:27:03.720 align:start position:0% as has been mentioned tests and efforts 00:27:03.720 --> 00:27:05.169 align:start position:0% as has been mentioned tests and efforts client<00:27:04.080> developers 00:27:05.169 --> 00:27:05.179 align:start position:0% client developers 00:27:05.179 --> 00:27:07.430 align:start position:0% client developers gave<00:27:06.179> a<00:27:06.360> lot<00:27:06.480> of<00:27:06.600> feedback<00:27:06.900> and<00:27:07.200> all<00:27:07.320> this 00:27:07.430 --> 00:27:07.440 align:start position:0% gave a lot of feedback and all this 00:27:07.440 --> 00:27:10.370 align:start position:0% gave a lot of feedback and all this stuff<00:27:07.679> I<00:27:08.340> was<00:27:08.520> just<00:27:08.640> and<00:27:08.880> the<00:27:09.120> key<00:27:09.299> takeaway<00:27:09.659> uh 00:27:10.370 --> 00:27:10.380 align:start position:0% stuff I was just and the key takeaway uh 00:27:10.380 --> 00:27:13.250 align:start position:0% stuff I was just and the key takeaway uh for<00:27:10.559> from<00:27:10.799> from<00:27:11.159> what<00:27:11.640> has<00:27:11.880> been<00:27:12.059> said 00:27:13.250 --> 00:27:13.260 align:start position:0% for from from what has been said 00:27:13.260 --> 00:27:16.010 align:start position:0% for from from what has been said um<00:27:13.380> yeah<00:27:13.679> the<00:27:14.279> right<00:27:14.760> people<00:27:15.120> at<00:27:15.720> the<00:27:15.840> right 00:27:16.010 --> 00:27:16.020 align:start position:0% um yeah the right people at the right 00:27:16.020 --> 00:27:17.390 align:start position:0% um yeah the right people at the right moment<00:27:16.320> in<00:27:16.500> time 00:27:17.390 --> 00:27:17.400 align:start position:0% moment in time 00:27:17.400 --> 00:27:19.870 align:start position:0% moment in time make<00:27:17.880> the<00:27:18.059> things<00:27:18.240> happen<00:27:18.679> so 00:27:19.870 --> 00:27:19.880 align:start position:0% make the things happen so 00:27:19.880 --> 00:27:22.010 align:start position:0% make the things happen so retrospectively<00:27:20.880> this<00:27:21.480> is<00:27:21.600> what<00:27:21.840> has 00:27:22.010 --> 00:27:22.020 align:start position:0% retrospectively this is what has 00:27:22.020 --> 00:27:23.990 align:start position:0% retrospectively this is what has happened<00:27:22.200> with<00:27:22.559> the<00:27:22.679> merge 00:27:23.990 --> 00:27:24.000 align:start position:0% happened with the merge 00:27:24.000 --> 00:27:27.590 align:start position:0% happened with the merge um<00:27:24.059> and<00:27:24.419> I<00:27:24.720> think<00:27:24.840> that<00:27:25.520> uh<00:27:26.520> this<00:27:27.120> may<00:27:27.419> only 00:27:27.590 --> 00:27:27.600 align:start position:0% um and I think that uh this may only 00:27:27.600 --> 00:27:30.049 align:start position:0% um and I think that uh this may only happen<00:27:28.020> uh<00:27:28.860> this<00:27:29.100> kind<00:27:29.220> of<00:27:29.340> like<00:27:29.520> thing<00:27:29.760> right 00:27:30.049 --> 00:27:30.059 align:start position:0% happen uh this kind of like thing right 00:27:30.059 --> 00:27:32.330 align:start position:0% happen uh this kind of like thing right people<00:27:30.299> at<00:27:30.539> the<00:27:30.720> right<00:27:31.039> moment<00:27:32.039> in<00:27:32.159> time 00:27:32.330 --> 00:27:32.340 align:start position:0% people at the right moment in time 00:27:32.340 --> 00:27:34.789 align:start position:0% people at the right moment in time appear<00:27:32.820> like<00:27:33.000> in<00:27:33.179> a<00:27:33.360> healthy<00:27:33.659> Community<00:27:33.840> which 00:27:34.789 --> 00:27:34.799 align:start position:0% appear like in a healthy Community which 00:27:34.799 --> 00:27:37.130 align:start position:0% appear like in a healthy Community which we<00:27:35.340> have<00:27:35.520> currently<00:27:36.120> the<00:27:36.600> healthy<00:27:36.960> community 00:27:37.130 --> 00:27:37.140 align:start position:0% we have currently the healthy community 00:27:37.140 --> 00:27:40.730 align:start position:0% we have currently the healthy community of<00:27:37.559> researchers<00:27:38.400> and<00:27:38.580> developers<00:27:39.320> and<00:27:40.320> uh 00:27:40.730 --> 00:27:40.740 align:start position:0% of researchers and developers and uh 00:27:40.740 --> 00:27:43.010 align:start position:0% of researchers and developers and uh yeah<00:27:41.039> and<00:27:41.700> this<00:27:42.059> like 00:27:43.010 --> 00:27:43.020 align:start position:0% yeah and this like 00:27:43.020 --> 00:27:46.610 align:start position:0% yeah and this like uh<00:27:43.740> prove<00:27:44.279> the<00:27:44.940> merge<00:27:45.299> is<00:27:45.480> like<00:27:45.659> as<00:27:46.020> for<00:27:46.320> me<00:27:46.440> is 00:27:46.610 --> 00:27:46.620 align:start position:0% uh prove the merge is like as for me is 00:27:46.620 --> 00:27:48.769 align:start position:0% uh prove the merge is like as for me is proof<00:27:47.039> of<00:27:47.100> like<00:27:47.340> these 00:27:48.769 --> 00:27:48.779 align:start position:0% proof of like these 00:27:48.779 --> 00:27:50.930 align:start position:0% proof of like these um<00:27:48.840> that<00:27:49.380> the<00:27:49.559> this<00:27:49.980> community<00:27:50.279> of<00:27:50.580> research 00:27:50.930 --> 00:27:50.940 align:start position:0% um that the this community of research 00:27:50.940 --> 00:27:53.149 align:start position:0% um that the this community of research and<00:27:51.360> developers<00:27:51.840> that<00:27:52.140> we<00:27:52.260> have<00:27:52.380> in<00:27:52.620> ethereum 00:27:53.149 --> 00:27:53.159 align:start position:0% and developers that we have in ethereum 00:27:53.159 --> 00:27:56.570 align:start position:0% and developers that we have in ethereum ecosystem<00:27:53.760> can<00:27:54.659> like<00:27:55.020> capable<00:27:55.559> of<00:27:55.679> delivering 00:27:56.570 --> 00:27:56.580 align:start position:0% ecosystem can like capable of delivering 00:27:56.580 --> 00:27:59.630 align:start position:0% ecosystem can like capable of delivering like<00:27:56.760> huge<00:27:57.299> big<00:27:57.779> sophisticated<00:27:58.320> projects<00:27:59.039> and 00:27:59.630 --> 00:27:59.640 align:start position:0% like huge big sophisticated projects and 00:27:59.640 --> 00:28:01.130 align:start position:0% like huge big sophisticated projects and like<00:27:59.820> the<00:28:00.000> merge<00:28:00.299> is<00:28:00.419> like<00:28:00.600> the<00:28:00.779> first<00:28:00.900> one 00:28:01.130 --> 00:28:01.140 align:start position:0% like the merge is like the first one 00:28:01.140 --> 00:28:03.350 align:start position:0% like the merge is like the first one right<00:28:01.799> so<00:28:02.100> next<00:28:02.460> is 00:28:03.350 --> 00:28:03.360 align:start position:0% right so next is 00:28:03.360 --> 00:28:07.010 align:start position:0% right so next is uh<00:28:03.960> dank<00:28:04.200> charging<00:28:04.740> and<00:28:05.340> other<00:28:05.760> things<00:28:06.120> uh 00:28:07.010 --> 00:28:07.020 align:start position:0% uh dank charging and other things uh 00:28:07.020 --> 00:28:10.010 align:start position:0% uh dank charging and other things uh local<00:28:07.500> trees<00:28:08.039> so<00:28:08.400> it's<00:28:09.000> not<00:28:09.240> that<00:28:09.480> I'm<00:28:09.840> not 00:28:10.010 --> 00:28:10.020 align:start position:0% local trees so it's not that I'm not 00:28:10.020 --> 00:28:11.810 align:start position:0% local trees so it's not that I'm not that<00:28:10.200> scared<00:28:10.500> about<00:28:10.679> it<00:28:10.919> after<00:28:11.159> we<00:28:11.640> deliver 00:28:11.810 --> 00:28:11.820 align:start position:0% that scared about it after we deliver 00:28:11.820 --> 00:28:14.390 align:start position:0% that scared about it after we deliver the<00:28:12.179> merge<00:28:12.480> with<00:28:13.080> this<00:28:13.440> huge<00:28:13.740> success<00:28:14.039> so 00:28:14.390 --> 00:28:14.400 align:start position:0% the merge with this huge success so 00:28:14.400 --> 00:28:17.029 align:start position:0% the merge with this huge success so thank<00:28:15.059> you<00:28:15.179> very<00:28:15.600> much<00:28:15.720> everyone 00:28:17.029 --> 00:28:17.039 align:start position:0% thank you very much everyone 00:28:17.039 --> 00:28:21.490 align:start position:0% thank you very much everyone who<00:28:17.640> made<00:28:18.059> it 00:28:21.490 --> 00:28:21.500 align:start position:0% 00:28:21.500 --> 00:28:23.750 align:start position:0% I<00:28:22.500> guess<00:28:22.559> on<00:28:22.919> the<00:28:23.220> note<00:28:23.340> of<00:28:23.520> the<00:28:23.580> community 00:28:23.750 --> 00:28:23.760 align:start position:0% I guess on the note of the community 00:28:23.760 --> 00:28:25.850 align:start position:0% I guess on the note of the community it's<00:28:24.120> been<00:28:24.299> like<00:28:24.419> 35<00:28:24.659> minutes<00:28:25.080> that's<00:28:25.380> just<00:28:25.620> us 00:28:25.850 --> 00:28:25.860 align:start position:0% it's been like 35 minutes that's just us 00:28:25.860 --> 00:28:26.870 align:start position:0% it's been like 35 minutes that's just us talking 00:28:26.870 --> 00:28:26.880 align:start position:0% talking 00:28:26.880 --> 00:28:30.049 align:start position:0% talking um<00:28:27.000> Team<00:28:27.600> don't<00:28:27.960> want<00:28:28.140> to<00:28:28.200> give<00:28:28.380> a<00:28:28.679> lot<00:28:28.860> star 00:28:30.049 --> 00:28:30.059 align:start position:0% um Team don't want to give a lot star 00:28:30.059 --> 00:28:33.529 align:start position:0% um Team don't want to give a lot star um<00:28:30.120> to<00:28:30.419> like<00:28:30.600> tell<00:28:31.260> us<00:28:31.559> more<00:28:31.880> but<00:28:32.880> after<00:28:33.240> that 00:28:33.529 --> 00:28:33.539 align:start position:0% um to like tell us more but after that 00:28:33.539 --> 00:28:37.190 align:start position:0% um to like tell us more but after that start<00:28:34.380> asking<00:28:34.799> questions<00:28:35.100> so<00:28:35.640> we<00:28:35.820> can<00:28:35.940> like 00:28:37.190 --> 00:28:37.200 align:start position:0% start asking questions so we can like 00:28:37.200 --> 00:28:39.529 align:start position:0% start asking questions so we can like open<00:28:37.559> this<00:28:37.860> up<00:28:38.039> hey<00:28:38.580> thank<00:28:38.820> you<00:28:39.000> sorry<00:28:39.299> for 00:28:39.529 --> 00:28:39.539 align:start position:0% open this up hey thank you sorry for 00:28:39.539 --> 00:28:40.930 align:start position:0% open this up hey thank you sorry for being<00:28:39.720> late 00:28:40.930 --> 00:28:40.940 align:start position:0% being late 00:28:40.940 --> 00:28:44.870 align:start position:0% being late as<00:28:41.940> we<00:28:42.120> are<00:28:42.299> most<00:28:42.960> of<00:28:43.140> the<00:28:43.200> time<00:28:43.380> uh<00:28:44.220> we're<00:28:44.460> we 00:28:44.870 --> 00:28:44.880 align:start position:0% as we are most of the time uh we're we 00:28:44.880 --> 00:28:47.149 align:start position:0% as we are most of the time uh we're we are<00:28:45.059> the<00:28:45.240> fifth<00:28:45.600> the<00:28:46.140> fifth<00:28:46.500> uh<00:28:46.679> consensus 00:28:47.149 --> 00:28:47.159 align:start position:0% are the fifth the fifth uh consensus 00:28:47.159 --> 00:28:49.370 align:start position:0% are the fifth the fifth uh consensus client<00:28:47.460> so<00:28:47.700> yeah<00:28:47.940> we<00:28:48.299> we<00:28:48.659> actually<00:28:48.900> produced 00:28:49.370 --> 00:28:49.380 align:start position:0% client so yeah we we actually produced 00:28:49.380 --> 00:28:50.990 align:start position:0% client so yeah we we actually produced our<00:28:49.500> first<00:28:49.620> block<00:28:49.860> on<00:28:50.100> mainnet<00:28:50.460> in<00:28:50.700> November 00:28:50.990 --> 00:28:51.000 align:start position:0% our first block on mainnet in November 00:28:51.000 --> 00:28:53.330 align:start position:0% our first block on mainnet in November of<00:28:51.120> last<00:28:51.360> year<00:28:51.539> but<00:28:52.200> it<00:28:52.320> was<00:28:52.500> actually<00:28:52.679> fun<00:28:53.039> to 00:28:53.330 --> 00:28:53.340 align:start position:0% of last year but it was actually fun to 00:28:53.340 --> 00:28:56.149 align:start position:0% of last year but it was actually fun to basically<00:28:53.640> Sprint<00:28:54.000> up<00:28:54.299> to<00:28:54.779> uh<00:28:55.260> to<00:28:55.799> with 00:28:56.149 --> 00:28:56.159 align:start position:0% basically Sprint up to uh to with 00:28:56.159 --> 00:28:59.149 align:start position:0% basically Sprint up to uh to with everyone<00:28:56.400> else<00:28:56.640> and<00:28:56.880> basically<00:28:57.299> caught<00:28:57.900> up 00:28:59.149 --> 00:28:59.159 align:start position:0% everyone else and basically caught up 00:28:59.159 --> 00:29:01.250 align:start position:0% everyone else and basically caught up um<00:28:59.279> so<00:28:59.520> that<00:28:59.700> sort<00:28:59.940> of<00:29:00.059> retrospective<00:29:00.659> was<00:29:01.020> uh 00:29:01.250 --> 00:29:01.260 align:start position:0% um so that sort of retrospective was uh 00:29:01.260 --> 00:29:03.950 align:start position:0% um so that sort of retrospective was uh was<00:29:01.620> amazing<00:29:02.039> to<00:29:02.279> see<00:29:02.460> the<00:29:02.640> kind<00:29:02.820> of<00:29:02.880> feat<00:29:03.299> that 00:29:03.950 --> 00:29:03.960 align:start position:0% was amazing to see the kind of feat that 00:29:03.960 --> 00:29:05.570 align:start position:0% was amazing to see the kind of feat that we<00:29:04.080> can<00:29:04.200> get<00:29:04.380> there<00:29:04.559> and<00:29:04.860> of<00:29:05.100> course<00:29:05.220> with<00:29:05.460> the 00:29:05.570 --> 00:29:05.580 align:start position:0% we can get there and of course with the 00:29:05.580 --> 00:29:08.210 align:start position:0% we can get there and of course with the help<00:29:05.700> of<00:29:05.940> all<00:29:06.120> the<00:29:06.240> other<00:29:06.419> client<00:29:06.900> teams 00:29:08.210 --> 00:29:08.220 align:start position:0% help of all the other client teams 00:29:08.220 --> 00:29:10.010 align:start position:0% help of all the other client teams um<00:29:08.279> as<00:29:08.460> well<00:29:08.640> we<00:29:08.880> were<00:29:09.059> able<00:29:09.299> to<00:29:09.480> pull<00:29:09.779> through 00:29:10.010 --> 00:29:10.020 align:start position:0% um as well we were able to pull through 00:29:10.020 --> 00:29:12.529 align:start position:0% um as well we were able to pull through so<00:29:10.860> basically<00:29:11.340> goes<00:29:11.640> to<00:29:11.700> show<00:29:11.880> that<00:29:12.179> what 00:29:12.529 --> 00:29:12.539 align:start position:0% so basically goes to show that what 00:29:12.539 --> 00:29:13.909 align:start position:0% so basically goes to show that what we're<00:29:12.659> capable<00:29:13.080> of<00:29:13.260> when<00:29:13.440> we<00:29:13.620> all<00:29:13.740> work 00:29:13.909 --> 00:29:13.919 align:start position:0% we're capable of when we all work 00:29:13.919 --> 00:29:15.230 align:start position:0% we're capable of when we all work together<00:29:14.159> especially<00:29:14.760> when<00:29:14.940> we're<00:29:15.059> all 00:29:15.230 --> 00:29:15.240 align:start position:0% together especially when we're all 00:29:15.240 --> 00:29:18.230 align:start position:0% together especially when we're all focused<00:29:15.720> on<00:29:16.020> that<00:29:16.919> one<00:29:17.220> thing<00:29:17.400> and<00:29:17.760> it<00:29:17.880> was<00:29:18.000> to 00:29:18.230 --> 00:29:18.240 align:start position:0% focused on that one thing and it was to 00:29:18.240 --> 00:29:21.350 align:start position:0% focused on that one thing and it was to achieve<00:29:18.659> a<00:29:19.380> successful<00:29:19.740> merge<00:29:20.220> so 00:29:21.350 --> 00:29:21.360 align:start position:0% achieve a successful merge so 00:29:21.360 --> 00:29:23.269 align:start position:0% achieve a successful merge so um it<00:29:21.600> was<00:29:21.720> really<00:29:21.899> great<00:29:22.200> to<00:29:22.500> for<00:29:22.919> all<00:29:23.159> you 00:29:23.269 --> 00:29:23.279 align:start position:0% um it was really great to for all you 00:29:23.279 --> 00:29:26.870 align:start position:0% um it was really great to for all you guys<00:29:23.399> to<00:29:23.580> help<00:29:23.820> us<00:29:24.059> basically<00:29:24.779> pull<00:29:25.740> us<00:29:25.980> up<00:29:26.640> to 00:29:26.870 --> 00:29:26.880 align:start position:0% guys to help us basically pull us up to 00:29:26.880 --> 00:29:29.450 align:start position:0% guys to help us basically pull us up to where<00:29:27.539> you<00:29:27.659> guys<00:29:27.779> are 00:29:29.450 --> 00:29:29.460 align:start position:0% where you guys are 00:29:29.460 --> 00:29:30.950 align:start position:0% where you guys are um I<00:29:29.880> guess<00:29:30.000> one<00:29:30.179> of<00:29:30.360> the<00:29:30.419> hardest<00:29:30.720> things 00:29:30.950 --> 00:29:30.960 align:start position:0% um I guess one of the hardest things 00:29:30.960 --> 00:29:33.649 align:start position:0% um I guess one of the hardest things that<00:29:31.500> we<00:29:31.860> had<00:29:32.039> to<00:29:32.159> deal<00:29:32.279> with<00:29:32.460> with<00:29:32.700> being<00:29:33.059> a 00:29:33.649 --> 00:29:33.659 align:start position:0% that we had to deal with with being a 00:29:33.659 --> 00:29:36.110 align:start position:0% that we had to deal with with being a more<00:29:33.779> later<00:29:34.020> client<00:29:34.500> uh<00:29:35.100> to<00:29:35.279> be<00:29:35.399> ready<00:29:35.580> for 00:29:36.110 --> 00:29:36.120 align:start position:0% more later client uh to be ready for 00:29:36.120 --> 00:29:39.230 align:start position:0% more later client uh to be ready for mainnet<00:29:36.720> is<00:29:37.559> really<00:29:37.799> just<00:29:38.100> the<00:29:38.820> fact<00:29:38.940> that 00:29:39.230 --> 00:29:39.240 align:start position:0% mainnet is really just the fact that 00:29:39.240 --> 00:29:41.810 align:start position:0% mainnet is really just the fact that client<00:29:39.659> stickiness<00:29:40.260> is<00:29:40.559> really<00:29:40.860> really<00:29:41.399> huge 00:29:41.810 --> 00:29:41.820 align:start position:0% client stickiness is really really huge 00:29:41.820 --> 00:29:44.269 align:start position:0% client stickiness is really really huge issue<00:29:42.179> and<00:29:42.480> we<00:29:42.960> definitely<00:29:43.260> noticed<00:29:43.799> it<00:29:43.980> as 00:29:44.269 --> 00:29:44.279 align:start position:0% issue and we definitely noticed it as 00:29:44.279 --> 00:29:47.389 align:start position:0% issue and we definitely noticed it as we're<00:29:44.700> going<00:29:44.880> towards<00:29:45.240> merch<00:29:46.140> people 00:29:47.389 --> 00:29:47.399 align:start position:0% we're going towards merch people 00:29:47.399 --> 00:29:50.029 align:start position:0% we're going towards merch people tended<00:29:47.940> to<00:29:48.240> not<00:29:48.419> necessarily<00:29:49.320> want<00:29:49.860> to 00:29:50.029 --> 00:29:50.039 align:start position:0% tended to not necessarily want to 00:29:50.039 --> 00:29:53.510 align:start position:0% tended to not necessarily want to experiment<00:29:50.760> with<00:29:51.539> a<00:29:51.960> new<00:29:52.140> client<00:29:52.440> going<00:29:53.220> up<00:29:53.399> to 00:29:53.510 --> 00:29:53.520 align:start position:0% experiment with a new client going up to 00:29:53.520 --> 00:29:55.130 align:start position:0% experiment with a new client going up to something<00:29:53.700> as<00:29:53.940> critical<00:29:54.240> as<00:29:54.419> the<00:29:54.539> merge<00:29:54.840> so<00:29:55.020> we 00:29:55.130 --> 00:29:55.140 align:start position:0% something as critical as the merge so we 00:29:55.140 --> 00:29:57.710 align:start position:0% something as critical as the merge so we found<00:29:55.320> that<00:29:55.500> to<00:29:55.679> be<00:29:56.220> quite<00:29:56.760> difficult<00:29:57.059> even 00:29:57.710 --> 00:29:57.720 align:start position:0% found that to be quite difficult even 00:29:57.720 --> 00:29:59.930 align:start position:0% found that to be quite difficult even though<00:29:58.020> we<00:29:58.500> you<00:29:58.799> know<00:29:58.919> tried<00:29:59.220> our<00:29:59.399> best<00:29:59.580> to 00:29:59.930 --> 00:29:59.940 align:start position:0% though we you know tried our best to 00:29:59.940 --> 00:30:01.549 align:start position:0% though we you know tried our best to sort<00:30:00.120> of<00:30:00.179> make<00:30:00.360> it<00:30:00.480> easier<00:30:00.779> for<00:30:01.020> people<00:30:01.140> you 00:30:01.549 --> 00:30:01.559 align:start position:0% sort of make it easier for people you 00:30:01.559 --> 00:30:04.490 align:start position:0% sort of make it easier for people you know<00:30:01.820> like<00:30:02.820> one<00:30:03.120> of<00:30:03.240> the<00:30:03.720> best<00:30:03.840> examples<00:30:04.260> would 00:30:04.490 --> 00:30:04.500 align:start position:0% know like one of the best examples would 00:30:04.500 --> 00:30:07.130 align:start position:0% know like one of the best examples would have<00:30:04.679> been<00:30:04.799> our<00:30:05.419> lodestar<00:30:06.419> quick<00:30:06.659> scripts 00:30:07.130 --> 00:30:07.140 align:start position:0% have been our lodestar quick scripts 00:30:07.140 --> 00:30:09.830 align:start position:0% have been our lodestar quick scripts that<00:30:07.620> we<00:30:07.740> use<00:30:07.919> which<00:30:08.760> is<00:30:09.120> basically<00:30:09.419> like<00:30:09.720> a 00:30:09.830 --> 00:30:09.840 align:start position:0% that we use which is basically like a 00:30:09.840 --> 00:30:11.330 align:start position:0% that we use which is basically like a one-line<00:30:10.140> command<00:30:10.500> for<00:30:10.679> people<00:30:10.799> to<00:30:10.980> start<00:30:11.159> up 00:30:11.330 --> 00:30:11.340 align:start position:0% one-line command for people to start up 00:30:11.340 --> 00:30:15.529 align:start position:0% one-line command for people to start up load<00:30:12.120> star<00:30:12.240> with<00:30:12.659> any<00:30:13.200> of<00:30:13.620> the<00:30:13.740> El<00:30:13.919> clients 00:30:15.529 --> 00:30:15.539 align:start position:0% load star with any of the El clients 00:30:15.539 --> 00:30:17.510 align:start position:0% load star with any of the El clients um<00:30:15.659> but<00:30:16.020> you<00:30:16.380> know<00:30:16.500> didn't<00:30:16.980> see<00:30:17.220> as<00:30:17.340> much 00:30:17.510 --> 00:30:17.520 align:start position:0% um but you know didn't see as much 00:30:17.520 --> 00:30:20.389 align:start position:0% um but you know didn't see as much traction<00:30:17.820> with<00:30:18.000> as<00:30:18.299> we'd<00:30:18.600> like<00:30:18.659> to<00:30:18.840> but 00:30:20.389 --> 00:30:20.399 align:start position:0% traction with as we'd like to but 00:30:20.399 --> 00:30:21.830 align:start position:0% traction with as we'd like to but um now<00:30:20.760> that<00:30:20.880> we're<00:30:21.059> pretty<00:30:21.299> much<00:30:21.419> caught<00:30:21.659> up 00:30:21.830 --> 00:30:21.840 align:start position:0% um now that we're pretty much caught up 00:30:21.840 --> 00:30:24.549 align:start position:0% um now that we're pretty much caught up going<00:30:22.679> into<00:30:22.919> withdrawals<00:30:23.880> Shanghai 00:30:24.549 --> 00:30:24.559 align:start position:0% going into withdrawals Shanghai 00:30:24.559 --> 00:30:26.930 align:start position:0% going into withdrawals Shanghai dangsharding<00:30:25.559> hoping<00:30:26.340> to<00:30:26.399> see<00:30:26.580> much<00:30:26.760> more 00:30:26.930 --> 00:30:26.940 align:start position:0% dangsharding hoping to see much more 00:30:26.940 --> 00:30:29.630 align:start position:0% dangsharding hoping to see much more adoption<00:30:27.360> with<00:30:27.600> that<00:30:27.840> and<00:30:28.679> um<00:30:28.679> yeah<00:30:29.399> we 00:30:29.630 --> 00:30:29.640 align:start position:0% adoption with that and um yeah we 00:30:29.640 --> 00:30:31.430 align:start position:0% adoption with that and um yeah we definitely<00:30:30.179> can't<00:30:30.360> do<00:30:30.539> it<00:30:30.659> without<00:30:30.899> the<00:30:31.320> help 00:30:31.430 --> 00:30:31.440 align:start position:0% definitely can't do it without the help 00:30:31.440 --> 00:30:33.110 align:start position:0% definitely can't do it without the help of<00:30:31.679> all<00:30:31.860> of<00:30:31.980> our<00:30:32.159> Collective<00:30:32.580> Minds<00:30:32.940> together 00:30:33.110 --> 00:30:33.120 align:start position:0% of all of our Collective Minds together 00:30:33.120 --> 00:30:37.010 align:start position:0% of all of our Collective Minds together so<00:30:33.840> really<00:30:34.559> our<00:30:34.799> retrospective<00:30:35.520> is<00:30:36.179> um<00:30:36.240> if<00:30:36.779> you 00:30:37.010 --> 00:30:37.020 align:start position:0% so really our retrospective is um if you 00:30:37.020 --> 00:30:39.230 align:start position:0% so really our retrospective is um if you are<00:30:37.140> an<00:30:37.320> up-and-coming<00:30:37.980> client 00:30:39.230 --> 00:30:39.240 align:start position:0% are an up-and-coming client 00:30:39.240 --> 00:30:41.389 align:start position:0% are an up-and-coming client um<00:30:39.299> we're<00:30:39.659> all<00:30:39.779> here<00:30:39.960> to<00:30:40.140> help<00:30:40.260> you 00:30:41.389 --> 00:30:41.399 align:start position:0% um we're all here to help you 00:30:41.399 --> 00:30:44.029 align:start position:0% um we're all here to help you nice 00:30:44.029 --> 00:30:44.039 align:start position:0% 00:30:44.039 --> 00:30:45.010 align:start position:0% yeah 00:30:45.010 --> 00:30:45.020 align:start position:0% yeah 00:30:45.020 --> 00:30:48.049 align:start position:0% yeah so<00:30:46.020> we<00:30:46.320> we've<00:30:46.860> just<00:30:46.980> shared<00:30:47.279> kind<00:30:47.460> of<00:30:47.520> mostly 00:30:48.049 --> 00:30:48.059 align:start position:0% so we we've just shared kind of mostly 00:30:48.059 --> 00:30:49.730 align:start position:0% so we we've just shared kind of mostly core<00:30:48.240> devs<00:30:48.600> and<00:30:48.659> researchers<00:30:49.140> you<00:30:49.500> know<00:30:49.559> our 00:30:49.730 --> 00:30:49.740 align:start position:0% core devs and researchers you know our 00:30:49.740 --> 00:30:51.049 align:start position:0% core devs and researchers you know our retrospectors<00:30:50.279> on<00:30:50.460> the<00:30:50.520> merge<00:30:50.760> so<00:30:50.880> my 00:30:51.049 --> 00:30:51.059 align:start position:0% retrospectors on the merge so my 00:30:51.059 --> 00:30:52.430 align:start position:0% retrospectors on the merge so my question<00:30:51.179> to<00:30:51.480> everyone<00:30:51.840> out<00:30:52.140> in<00:30:52.260> the 00:30:52.430 --> 00:30:52.440 align:start position:0% question to everyone out in the 00:30:52.440 --> 00:30:54.769 align:start position:0% question to everyone out in the community<00:30:52.559> is<00:30:52.919> what's<00:30:53.760> it<00:30:54.059> been<00:30:54.240> like<00:30:54.480> like 00:30:54.769 --> 00:30:54.779 align:start position:0% community is what's it been like like 00:30:54.779 --> 00:30:56.570 align:start position:0% community is what's it been like like what's<00:30:55.080> your<00:30:55.380> retrospective<00:30:55.980> on<00:30:56.220> how<00:30:56.460> the 00:30:56.570 --> 00:30:56.580 align:start position:0% what's your retrospective on how the 00:30:56.580 --> 00:30:58.130 align:start position:0% what's your retrospective on how the merge<00:30:56.880> has<00:30:57.000> gone<00:30:57.179> how's<00:30:57.480> it<00:30:57.659> been<00:30:57.779> as<00:30:57.960> a 00:30:58.130 --> 00:30:58.140 align:start position:0% merge has gone how's it been as a 00:30:58.140 --> 00:31:00.470 align:start position:0% merge has gone how's it been as a validator<00:30:58.440> how's<00:30:58.740> it<00:30:58.919> been<00:30:59.100> as<00:30:59.460> a<00:31:00.179> dab 00:31:00.470 --> 00:31:00.480 align:start position:0% validator how's it been as a dab 00:31:00.480 --> 00:31:04.250 align:start position:0% validator how's it been as a dab developer<00:31:01.020> and<00:31:01.200> those<00:31:01.380> kinds<00:31:01.620> of<00:31:01.679> things 00:31:04.250 --> 00:31:04.260 align:start position:0% 00:31:04.260 --> 00:31:05.450 align:start position:0% someone's<00:31:04.740> got<00:31:04.860> to<00:31:04.919> start<00:31:05.039> just<00:31:05.159> give<00:31:05.279> someone 00:31:05.450 --> 00:31:05.460 align:start position:0% someone's got to start just give someone 00:31:05.460 --> 00:31:06.350 align:start position:0% someone's got to start just give someone a<00:31:05.700> mic<00:31:05.820> yeah 00:31:06.350 --> 00:31:06.360 align:start position:0% a mic yeah 00:31:06.360 --> 00:31:07.510 align:start position:0% a mic yeah [Music] 00:31:07.510 --> 00:31:07.520 align:start position:0% [Music] 00:31:07.520 --> 00:31:10.250 align:start position:0% [Music] hi<00:31:08.520> I'm<00:31:08.940> not<00:31:09.179> there 00:31:10.250 --> 00:31:10.260 align:start position:0% hi I'm not there 00:31:10.260 --> 00:31:13.909 align:start position:0% hi I'm not there it<00:31:10.980> was<00:31:11.159> crazy<00:31:11.460> because<00:31:12.440> in<00:31:13.440> Mexico<00:31:13.620> I'm 00:31:13.909 --> 00:31:13.919 align:start position:0% it was crazy because in Mexico I'm 00:31:13.919 --> 00:31:15.350 align:start position:0% it was crazy because in Mexico I'm trying<00:31:14.100> to<00:31:14.279> teach<00:31:14.399> people<00:31:14.640> what<00:31:15.000> this<00:31:15.179> video 00:31:15.350 --> 00:31:15.360 align:start position:0% trying to teach people what this video 00:31:15.360 --> 00:31:17.990 align:start position:0% trying to teach people what this video needs<00:31:15.720> to<00:31:15.779> make<00:31:16.140> in<00:31:16.320> while<00:31:16.980> people<00:31:17.700> like<00:31:17.880> you 00:31:17.990 --> 00:31:18.000 align:start position:0% needs to make in while people like you 00:31:18.000 --> 00:31:20.570 align:start position:0% needs to make in while people like you are<00:31:18.240> building<00:31:18.419> are<00:31:19.020> creating 00:31:20.570 --> 00:31:20.580 align:start position:0% are building are creating 00:31:20.580 --> 00:31:22.789 align:start position:0% are building are creating I<00:31:21.059> need<00:31:21.240> scar<00:31:21.480> record<00:31:21.779> all<00:31:22.260> the<00:31:22.380> terminology 00:31:22.789 --> 00:31:22.799 align:start position:0% I need scar record all the terminology 00:31:22.799 --> 00:31:27.710 align:start position:0% I need scar record all the terminology is<00:31:23.279> very<00:31:23.940> hard<00:31:24.179> to<00:31:24.299> understand<00:31:24.480> and<00:31:25.580> that<00:31:26.720> they 00:31:27.710 --> 00:31:27.720 align:start position:0% is very hard to understand and that they 00:31:27.720 --> 00:31:30.610 align:start position:0% is very hard to understand and that they don't<00:31:28.559> teach<00:31:28.919> people<00:31:29.220> what<00:31:30.120> you<00:31:30.240> are<00:31:30.419> doing 00:31:30.610 --> 00:31:30.620 align:start position:0% don't teach people what you are doing 00:31:30.620 --> 00:31:33.889 align:start position:0% don't teach people what you are doing and<00:31:31.620> guys<00:31:31.860> like<00:31:32.100> me<00:31:32.340> that<00:31:32.700> are<00:31:32.940> nerds<00:31:33.720> ready 00:31:33.889 --> 00:31:33.899 align:start position:0% and guys like me that are nerds ready 00:31:33.899 --> 00:31:35.930 align:start position:0% and guys like me that are nerds ready and<00:31:34.260> all<00:31:34.559> the<00:31:34.740> stuff 00:31:35.930 --> 00:31:35.940 align:start position:0% and all the stuff 00:31:35.940 --> 00:31:41.269 align:start position:0% and all the stuff it's<00:31:36.419> very<00:31:36.840> hard<00:31:37.320> to<00:31:37.919> to<00:31:38.159> keep<00:31:38.460> a<00:31:38.700> good<00:31:39.000> Channel 00:31:41.269 --> 00:31:41.279 align:start position:0% it's very hard to to keep a good Channel 00:31:41.279 --> 00:31:43.370 align:start position:0% it's very hard to to keep a good Channel so<00:31:41.820> I<00:31:42.240> think 00:31:43.370 --> 00:31:43.380 align:start position:0% so I think 00:31:43.380 --> 00:31:45.289 align:start position:0% so I think it's 00:31:45.289 --> 00:31:45.299 align:start position:0% it's 00:31:45.299 --> 00:31:47.510 align:start position:0% it's day<00:31:45.659> to<00:31:45.840> day<00:31:46.020> it's<00:31:46.260> improving<00:31:46.740> life<00:31:46.919> for 00:31:47.510 --> 00:31:47.520 align:start position:0% day to day it's improving life for 00:31:47.520 --> 00:31:49.730 align:start position:0% day to day it's improving life for example<00:31:47.700> when<00:31:48.000> I<00:31:48.360> start<00:31:48.480> to<00:31:48.779> make<00:31:49.260> the<00:31:49.380> threats 00:31:49.730 --> 00:31:49.740 align:start position:0% example when I start to make the threats 00:31:49.740 --> 00:31:51.549 align:start position:0% example when I start to make the threats about<00:31:49.860> all<00:31:50.159> quartets<00:31:50.520> in<00:31:50.700> Spanish 00:31:51.549 --> 00:31:51.559 align:start position:0% about all quartets in Spanish 00:31:51.559 --> 00:31:55.370 align:start position:0% about all quartets in Spanish Skylar<00:31:52.559> came<00:31:52.740> to<00:31:52.860> me<00:31:53.039> and<00:31:53.220> said<00:31:53.520> a<00:31:53.940> guy<00:31:54.179> a<00:31:55.020> nice 00:31:55.370 --> 00:31:55.380 align:start position:0% Skylar came to me and said a guy a nice 00:31:55.380 --> 00:31:58.130 align:start position:0% Skylar came to me and said a guy a nice what<00:31:55.980> you<00:31:56.100> are<00:31:56.279> what<00:31:56.640> you<00:31:56.700> are<00:31:56.880> doing<00:31:57.000> they<00:31:57.899> and 00:31:58.130 --> 00:31:58.140 align:start position:0% what you are what you are doing they and 00:31:58.140 --> 00:32:00.830 align:start position:0% what you are what you are doing they and team<00:31:58.320> Baker<00:31:58.740> start<00:31:59.100> to<00:31:59.279> to<00:31:59.640> share<00:32:00.000> my<00:32:00.179> post<00:32:00.360> so 00:32:00.830 --> 00:32:00.840 align:start position:0% team Baker start to to share my post so 00:32:00.840 --> 00:32:03.769 align:start position:0% team Baker start to to share my post so thank<00:32:01.140> you<00:32:01.260> to<00:32:01.500> everyone<00:32:01.679> for<00:32:02.220> all<00:32:02.520> this 00:32:03.769 --> 00:32:03.779 align:start position:0% thank you to everyone for all this 00:32:03.779 --> 00:32:06.110 align:start position:0% thank you to everyone for all this I<00:32:04.440> don't<00:32:04.559> know<00:32:04.679> I<00:32:04.919> feel<00:32:05.220> like<00:32:05.399> very<00:32:05.760> nervous 00:32:06.110 --> 00:32:06.120 align:start position:0% I don't know I feel like very nervous 00:32:06.120 --> 00:32:08.570 align:start position:0% I don't know I feel like very nervous because<00:32:06.419> I<00:32:06.840> think<00:32:07.020> that<00:32:07.440> I<00:32:07.620> am<00:32:07.740> with<00:32:08.039> a<00:32:08.340> very 00:32:08.570 --> 00:32:08.580 align:start position:0% because I think that I am with a very 00:32:08.580 --> 00:32:11.090 align:start position:0% because I think that I am with a very very<00:32:08.760> smart<00:32:09.059> guys<00:32:09.360> people<00:32:09.899> and<00:32:10.380> it's<00:32:10.860> like 00:32:11.090 --> 00:32:11.100 align:start position:0% very smart guys people and it's like 00:32:11.100 --> 00:32:12.529 align:start position:0% very smart guys people and it's like crazy<00:32:11.399> but 00:32:12.529 --> 00:32:12.539 align:start position:0% crazy but 00:32:12.539 --> 00:32:16.070 align:start position:0% crazy but that<00:32:13.020> day<00:32:13.260> that<00:32:13.620> night<00:32:13.860> where<00:32:14.419> I<00:32:15.419> was<00:32:15.539> with<00:32:15.899> the 00:32:16.070 --> 00:32:16.080 align:start position:0% that day that night where I was with the 00:32:16.080 --> 00:32:18.409 align:start position:0% that day that night where I was with the East<00:32:16.500> Latin<00:32:16.919> Community<00:32:17.120> speaking<00:32:18.120> about<00:32:18.240> the 00:32:18.409 --> 00:32:18.419 align:start position:0% East Latin Community speaking about the 00:32:18.419 --> 00:32:20.810 align:start position:0% East Latin Community speaking about the marriage<00:32:18.720> what<00:32:18.899> he's<00:32:19.200> going<00:32:19.500> to<00:32:19.740> do 00:32:20.810 --> 00:32:20.820 align:start position:0% marriage what he's going to do 00:32:20.820 --> 00:32:23.210 align:start position:0% marriage what he's going to do everybody<00:32:21.240> was<00:32:21.779> very<00:32:22.080> very<00:32:22.260> hyped<00:32:22.740> then<00:32:22.860> we 00:32:23.210 --> 00:32:23.220 align:start position:0% everybody was very very hyped then we 00:32:23.220 --> 00:32:25.850 align:start position:0% everybody was very very hyped then we saw<00:32:23.399> the<00:32:23.640> panda<00:32:23.880> and<00:32:24.480> was<00:32:24.720> okay<00:32:25.200> it's<00:32:25.620> done 00:32:25.850 --> 00:32:25.860 align:start position:0% saw the panda and was okay it's done 00:32:25.860 --> 00:32:28.850 align:start position:0% saw the panda and was okay it's done let's<00:32:26.159> go<00:32:26.340> to<00:32:26.460> sleep 00:32:28.850 --> 00:32:28.860 align:start position:0% 00:32:28.860 --> 00:32:32.389 align:start position:0% so<00:32:29.700> great<00:32:30.059> job<00:32:30.240> guys<00:32:30.480> great<00:32:30.960> job 00:32:32.389 --> 00:32:32.399 align:start position:0% so great job guys great job 00:32:32.399 --> 00:32:34.370 align:start position:0% so great job guys great job and<00:32:33.120> I<00:32:33.539> think 00:32:34.370 --> 00:32:34.380 align:start position:0% and I think 00:32:34.380 --> 00:32:36.110 align:start position:0% and I think thank<00:32:34.860> you<00:32:34.980> to<00:32:35.100> everyone<00:32:35.279> who's<00:32:35.640> doing<00:32:35.820> those 00:32:36.110 --> 00:32:36.120 align:start position:0% thank you to everyone who's doing those 00:32:36.120 --> 00:32:37.430 align:start position:0% thank you to everyone who's doing those translations<00:32:36.539> and<00:32:36.840> helping<00:32:37.140> with<00:32:37.260> that 00:32:37.430 --> 00:32:37.440 align:start position:0% translations and helping with that 00:32:37.440 --> 00:32:38.630 align:start position:0% translations and helping with that education 00:32:38.630 --> 00:32:38.640 align:start position:0% education 00:32:38.640 --> 00:32:40.610 align:start position:0% education we<00:32:39.120> can't<00:32:39.240> keep<00:32:39.419> up<00:32:39.539> with<00:32:39.659> all<00:32:39.840> of<00:32:39.960> it<00:32:40.080> and<00:32:40.380> it 00:32:40.610 --> 00:32:40.620 align:start position:0% we can't keep up with all of it and it 00:32:40.620 --> 00:32:42.289 align:start position:0% we can't keep up with all of it and it is<00:32:40.860> a<00:32:41.039> community<00:32:41.159> effort<00:32:41.640> it's<00:32:41.820> it's<00:32:41.940> really 00:32:42.289 --> 00:32:42.299 align:start position:0% is a community effort it's it's really 00:32:42.299 --> 00:32:45.169 align:start position:0% is a community effort it's it's really brilliant<00:32:43.140> uh<00:32:43.679> this<00:32:44.159> might<00:32:44.340> be<00:32:44.520> like<00:32:44.760> a<00:32:44.940> random 00:32:45.169 --> 00:32:45.179 align:start position:0% brilliant uh this might be like a random 00:32:45.179 --> 00:32:46.490 align:start position:0% brilliant uh this might be like a random question<00:32:45.419> but<00:32:45.720> can<00:32:46.020> we<00:32:46.140> have<00:32:46.320> more 00:32:46.490 --> 00:32:46.500 align:start position:0% question but can we have more 00:32:46.500 --> 00:32:49.250 align:start position:0% question but can we have more documentation<00:32:47.159> resources<00:32:47.820> for<00:32:48.659> future<00:32:49.020> core 00:32:49.250 --> 00:32:49.260 align:start position:0% documentation resources for future core 00:32:49.260 --> 00:32:50.930 align:start position:0% documentation resources for future core developers 00:32:50.930 --> 00:32:50.940 align:start position:0% developers 00:32:50.940 --> 00:32:52.370 align:start position:0% developers um because<00:32:51.179> I've<00:32:51.539> looked<00:32:51.840> around<00:32:51.960> and<00:32:52.260> it's 00:32:52.370 --> 00:32:52.380 align:start position:0% um because I've looked around and it's 00:32:52.380 --> 00:32:54.529 align:start position:0% um because I've looked around and it's very<00:32:52.559> hard<00:32:52.740> to<00:32:52.919> find<00:32:53.159> and<00:32:53.880> I<00:32:54.120> myself<00:32:54.240> would 00:32:54.529 --> 00:32:54.539 align:start position:0% very hard to find and I myself would 00:32:54.539 --> 00:32:56.690 align:start position:0% very hard to find and I myself would like<00:32:54.659> to<00:32:54.779> volunteer<00:32:55.260> to<00:32:55.559> take<00:32:55.799> that<00:32:55.980> task<00:32:56.279> and 00:32:56.690 --> 00:32:56.700 align:start position:0% like to volunteer to take that task and 00:32:56.700 --> 00:32:58.490 align:start position:0% like to volunteer to take that task and would<00:32:57.000> love<00:32:57.179> to<00:32:57.360> create<00:32:57.600> a<00:32:57.840> documentation<00:32:58.320> of 00:32:58.490 --> 00:32:58.500 align:start position:0% would love to create a documentation of 00:32:58.500 --> 00:33:01.130 align:start position:0% would love to create a documentation of tutorials<00:32:58.980> and<00:32:59.159> road<00:32:59.340> maps<00:32:59.760> because<00:33:00.419> I<00:33:01.020> really 00:33:01.130 --> 00:33:01.140 align:start position:0% tutorials and road maps because I really 00:33:01.140 --> 00:33:03.350 align:start position:0% tutorials and road maps because I really want<00:33:01.320> to<00:33:01.440> work<00:33:01.679> on<00:33:01.919> that<00:33:02.100> but<00:33:02.820> it's<00:33:02.940> very<00:33:03.120> hard 00:33:03.350 --> 00:33:03.360 align:start position:0% want to work on that but it's very hard 00:33:03.360 --> 00:33:05.630 align:start position:0% want to work on that but it's very hard to<00:33:03.539> find<00:33:03.720> like<00:33:03.899> a<00:33:04.080> clear<00:33:04.200> path<00:33:04.559> to<00:33:04.860> become<00:33:05.399> a 00:33:05.630 --> 00:33:05.640 align:start position:0% to find like a clear path to become a 00:33:05.640 --> 00:33:09.830 align:start position:0% to find like a clear path to become a core<00:33:05.820> developer<00:33:06.600> okay<00:33:07.080> this<00:33:07.799> is<00:33:07.919> a<00:33:08.220> great<00:33:08.840> time 00:33:09.830 --> 00:33:09.840 align:start position:0% core developer okay this is a great time 00:33:09.840 --> 00:33:11.570 align:start position:0% core developer okay this is a great time to<00:33:10.140> give<00:33:10.260> a<00:33:10.440> shout<00:33:10.620> out<00:33:10.740> because<00:33:10.860> Mario<00:33:11.220> just 00:33:11.570 --> 00:33:11.580 align:start position:0% to give a shout out because Mario just 00:33:11.580 --> 00:33:14.450 align:start position:0% to give a shout out because Mario just came<00:33:11.760> and<00:33:12.059> he<00:33:12.480> is<00:33:12.740> actually<00:33:13.740> one<00:33:14.159> of<00:33:14.279> the 00:33:14.450 --> 00:33:14.460 align:start position:0% came and he is actually one of the 00:33:14.460 --> 00:33:16.370 align:start position:0% came and he is actually one of the people<00:33:14.640> who<00:33:15.120> leads<00:33:15.480> the<00:33:15.600> fellowship<00:33:16.080> program 00:33:16.370 --> 00:33:16.380 align:start position:0% people who leads the fellowship program 00:33:16.380 --> 00:33:18.950 align:start position:0% people who leads the fellowship program for<00:33:16.980> cardiffs 00:33:18.950 --> 00:33:18.960 align:start position:0% for cardiffs 00:33:18.960 --> 00:33:20.590 align:start position:0% for cardiffs um<00:33:19.019> like<00:33:19.679> um 00:33:20.590 --> 00:33:20.600 align:start position:0% um like um 00:33:20.600 --> 00:33:22.370 align:start position:0% um like um thank<00:33:21.600> you 00:33:22.370 --> 00:33:22.380 align:start position:0% thank you 00:33:22.380 --> 00:33:23.690 align:start position:0% thank you um have<00:33:22.620> you<00:33:22.740> heard<00:33:22.860> about<00:33:23.039> a<00:33:23.340> protocol 00:33:23.690 --> 00:33:23.700 align:start position:0% um have you heard about a protocol 00:33:23.700 --> 00:33:26.870 align:start position:0% um have you heard about a protocol Fellowship<00:33:24.320> uh<00:33:25.320> it's<00:33:25.980> exactly<00:33:26.399> answer<00:33:26.580> to 00:33:26.870 --> 00:33:26.880 align:start position:0% Fellowship uh it's exactly answer to 00:33:26.880 --> 00:33:29.090 align:start position:0% Fellowship uh it's exactly answer to your<00:33:27.059> question<00:33:27.299> oh<00:33:28.200> you<00:33:28.440> were<00:33:28.559> I'm<00:33:28.919> sorry 00:33:29.090 --> 00:33:29.100 align:start position:0% your question oh you were I'm sorry 00:33:29.100 --> 00:33:30.769 align:start position:0% your question oh you were I'm sorry about<00:33:29.279> that<00:33:29.700> but<00:33:30.000> you<00:33:30.240> can<00:33:30.299> still<00:33:30.419> participate 00:33:30.769 --> 00:33:30.779 align:start position:0% about that but you can still participate 00:33:30.779 --> 00:33:33.169 align:start position:0% about that but you can still participate so<00:33:30.899> this<00:33:31.080> is<00:33:31.140> the<00:33:31.260> thing<00:33:31.380> so<00:33:31.559> like<00:33:32.100> um<00:33:32.159> so<00:33:32.519> uh<00:33:32.940> if 00:33:33.169 --> 00:33:33.179 align:start position:0% so this is the thing so like um so uh if 00:33:33.179 --> 00:33:35.570 align:start position:0% so this is the thing so like um so uh if you<00:33:33.360> didn't<00:33:33.419> protocol<00:33:34.140> Fellowship<00:33:34.620> is<00:33:35.039> a<00:33:35.279> kind 00:33:35.570 --> 00:33:35.580 align:start position:0% you didn't protocol Fellowship is a kind 00:33:35.580 --> 00:33:37.850 align:start position:0% you didn't protocol Fellowship is a kind of<00:33:35.760> an<00:33:35.880> internship<00:33:36.179> program<00:33:36.480> where 00:33:37.850 --> 00:33:37.860 align:start position:0% of an internship program where 00:33:37.860 --> 00:33:41.149 align:start position:0% of an internship program where um<00:33:37.919> uh<00:33:38.880> anybody<00:33:39.299> can<00:33:39.659> come<00:33:40.140> and<00:33:40.620> work<00:33:40.860> start 00:33:41.149 --> 00:33:41.159 align:start position:0% um uh anybody can come and work start 00:33:41.159 --> 00:33:44.090 align:start position:0% um uh anybody can come and work start working<00:33:41.399> on<00:33:41.640> a<00:33:41.760> project<00:33:41.940> and<00:33:42.659> in<00:33:43.440> a<00:33:43.620> way<00:33:43.740> that 00:33:44.090 --> 00:33:44.100 align:start position:0% working on a project and in a way that 00:33:44.100 --> 00:33:47.029 align:start position:0% working on a project and in a way that we<00:33:45.179> it<00:33:45.960> provides 00:33:47.029 --> 00:33:47.039 align:start position:0% we it provides 00:33:47.039 --> 00:33:49.430 align:start position:0% we it provides um certain<00:33:47.519> mentorship<00:33:48.059> from<00:33:48.539> many<00:33:48.840> of<00:33:49.080> folks 00:33:49.430 --> 00:33:49.440 align:start position:0% um certain mentorship from many of folks 00:33:49.440 --> 00:33:51.529 align:start position:0% um certain mentorship from many of folks who<00:33:49.620> are<00:33:49.740> sitting<00:33:50.100> here<00:33:50.220> and<00:33:50.460> other<00:33:50.880> core<00:33:51.120> devs 00:33:51.529 --> 00:33:51.539 align:start position:0% who are sitting here and other core devs 00:33:51.539 --> 00:33:54.350 align:start position:0% who are sitting here and other core devs and<00:33:52.200> there<00:33:52.559> are<00:33:52.679> also<00:33:52.860> resources<00:33:53.279> so<00:33:53.700> if<00:33:54.000> uh 00:33:54.350 --> 00:33:54.360 align:start position:0% and there are also resources so if uh 00:33:54.360 --> 00:33:56.389 align:start position:0% and there are also resources so if uh with<00:33:54.659> the<00:33:54.779> uh<00:33:55.200> the<00:33:55.620> whole<00:33:55.740> uh<00:33:56.100> later 00:33:56.389 --> 00:33:56.399 align:start position:0% with the uh the whole uh later 00:33:56.399 --> 00:33:58.850 align:start position:0% with the uh the whole uh later Fellowship<00:33:57.059> is<00:33:57.299> coordinated<00:33:57.720> via<00:33:58.140> repository 00:33:58.850 --> 00:33:58.860 align:start position:0% Fellowship is coordinated via repository 00:33:58.860 --> 00:34:02.090 align:start position:0% Fellowship is coordinated via repository on<00:33:59.640> GitHub<00:34:00.000> where<00:34:00.419> there<00:34:01.019> is<00:34:01.200> also<00:34:01.500> suggested 00:34:02.090 --> 00:34:02.100 align:start position:0% on GitHub where there is also suggested 00:34:02.100 --> 00:34:04.490 align:start position:0% on GitHub where there is also suggested reading<00:34:02.460> uh<00:34:03.240> there<00:34:03.539> are<00:34:03.840> a<00:34:04.080> few<00:34:04.140> things<00:34:04.320> they 00:34:04.490 --> 00:34:04.500 align:start position:0% reading uh there are a few things they 00:34:04.500 --> 00:34:06.110 align:start position:0% reading uh there are a few things they put<00:34:04.679> together<00:34:04.860> but<00:34:05.220> I<00:34:05.399> agree<00:34:05.580> it's<00:34:05.760> not<00:34:05.940> easy 00:34:06.110 --> 00:34:06.120 align:start position:0% put together but I agree it's not easy 00:34:06.120 --> 00:34:08.149 align:start position:0% put together but I agree it's not easy that's<00:34:06.539> it's<00:34:06.899> a<00:34:07.140> high<00:34:07.260> wall<00:34:07.440> that<00:34:07.740> you<00:34:07.799> have<00:34:07.919> to 00:34:08.149 --> 00:34:08.159 align:start position:0% that's it's a high wall that you have to 00:34:08.159 --> 00:34:10.490 align:start position:0% that's it's a high wall that you have to go<00:34:08.580> through<00:34:08.760> but<00:34:09.060> so<00:34:09.599> we<00:34:09.780> are<00:34:09.899> I<00:34:10.139> believe<00:34:10.320> that 00:34:10.490 --> 00:34:10.500 align:start position:0% go through but so we are I believe that 00:34:10.500 --> 00:34:13.250 align:start position:0% go through but so we are I believe that this<00:34:10.679> might<00:34:10.980> make<00:34:11.159> it<00:34:11.580> easier<00:34:11.879> so<00:34:12.179> there<00:34:12.419> is<00:34:12.599> uh 00:34:13.250 --> 00:34:13.260 align:start position:0% this might make it easier so there is uh 00:34:13.260 --> 00:34:14.510 align:start position:0% this might make it easier so there is uh there<00:34:13.500> is<00:34:13.560> a<00:34:13.679> lot<00:34:13.679> of<00:34:13.800> things<00:34:13.919> to<00:34:14.099> dive<00:34:14.339> into 00:34:14.510 --> 00:34:14.520 align:start position:0% there is a lot of things to dive into 00:34:14.520 --> 00:34:17.329 align:start position:0% there is a lot of things to dive into and<00:34:15.119> uh<00:34:15.480> the<00:34:15.899> the<00:34:16.200> reading<00:34:16.560> in<00:34:16.679> the<00:34:16.859> repo<00:34:17.159> can 00:34:17.329 --> 00:34:17.339 align:start position:0% and uh the the reading in the repo can 00:34:17.339 --> 00:34:20.089 align:start position:0% and uh the the reading in the repo can help<00:34:17.520> you<00:34:17.700> to<00:34:18.060> look<00:34:18.480> into<00:34:18.659> what<00:34:19.020> what<00:34:19.379> uh<00:34:19.859> makes 00:34:20.089 --> 00:34:20.099 align:start position:0% help you to look into what what uh makes 00:34:20.099 --> 00:34:22.790 align:start position:0% help you to look into what what uh makes you<00:34:20.280> uh<00:34:20.700> what<00:34:21.599> you're<00:34:21.720> interested<00:34:22.020> in<00:34:22.139> and 00:34:22.790 --> 00:34:22.800 align:start position:0% you uh what you're interested in and 00:34:22.800 --> 00:34:25.790 align:start position:0% you uh what you're interested in and then<00:34:23.099> uh<00:34:23.820> you<00:34:24.119> can<00:34:24.240> just<00:34:24.599> start<00:34:24.899> contributing 00:34:25.790 --> 00:34:25.800 align:start position:0% then uh you can just start contributing 00:34:25.800 --> 00:34:28.490 align:start position:0% then uh you can just start contributing because<00:34:26.399> so<00:34:26.820> the<00:34:27.060> the<00:34:27.599> calls<00:34:28.139> and<00:34:28.320> everything 00:34:28.490 --> 00:34:28.500 align:start position:0% because so the the calls and everything 00:34:28.500 --> 00:34:30.530 align:start position:0% because so the the calls and everything in<00:34:28.919> the<00:34:29.040> even<00:34:29.220> if<00:34:29.460> you<00:34:29.580> were<00:34:29.700> accepted<00:34:30.240> it's 00:34:30.530 --> 00:34:30.540 align:start position:0% in the even if you were accepted it's 00:34:30.540 --> 00:34:32.869 align:start position:0% in the even if you were accepted it's still<00:34:30.720> open<00:34:30.899> you<00:34:31.320> can<00:34:31.440> join<00:34:32.040> uh<00:34:32.580> if<00:34:32.700> you<00:34:32.820> are 00:34:32.869 --> 00:34:32.879 align:start position:0% still open you can join uh if you are 00:34:32.879 --> 00:34:34.250 align:start position:0% still open you can join uh if you are not<00:34:33.060> accepted<00:34:33.419> you<00:34:33.540> just<00:34:33.720> don't<00:34:33.899> get<00:34:34.139> a 00:34:34.250 --> 00:34:34.260 align:start position:0% not accepted you just don't get a 00:34:34.260 --> 00:34:36.349 align:start position:0% not accepted you just don't get a stipend<00:34:34.619> uh<00:34:35.280> but<00:34:35.460> you<00:34:35.639> can<00:34:35.700> still<00:34:35.879> come<00:34:36.179> and 00:34:36.349 --> 00:34:36.359 align:start position:0% stipend uh but you can still come and 00:34:36.359 --> 00:34:38.270 align:start position:0% stipend uh but you can still come and and<00:34:36.540> if<00:34:36.780> you<00:34:36.899> work<00:34:37.080> on<00:34:37.200> a<00:34:37.440> project<00:34:37.560> and<00:34:37.980> over<00:34:38.099> a 00:34:38.270 --> 00:34:38.280 align:start position:0% and if you work on a project and over a 00:34:38.280 --> 00:34:39.889 align:start position:0% and if you work on a project and over a few<00:34:38.339> weeks<00:34:38.580> we<00:34:38.760> see<00:34:38.940> that<00:34:39.119> you<00:34:39.300> have<00:34:39.419> valuable 00:34:39.889 --> 00:34:39.899 align:start position:0% few weeks we see that you have valuable 00:34:39.899 --> 00:34:42.530 align:start position:0% few weeks we see that you have valuable out<00:34:40.200> output<00:34:40.679> uh<00:34:41.280> we<00:34:41.580> can<00:34:41.700> still<00:34:41.879> uh<00:34:42.240> give<00:34:42.419> you 00:34:42.530 --> 00:34:42.540 align:start position:0% out output uh we can still uh give you 00:34:42.540 --> 00:34:45.109 align:start position:0% out output uh we can still uh give you this<00:34:42.659> type<00:34:42.780> and<00:34:43.020> as<00:34:43.200> well<00:34:43.320> uh<00:34:44.159> but<00:34:44.460> it's<00:34:44.820> fully 00:34:45.109 --> 00:34:45.119 align:start position:0% this type and as well uh but it's fully 00:34:45.119 --> 00:34:47.450 align:start position:0% this type and as well uh but it's fully a<00:34:45.480> permissionless<00:34:45.960> you<00:34:46.260> can<00:34:46.440> come<00:34:47.159> to<00:34:47.339> the 00:34:47.450 --> 00:34:47.460 align:start position:0% a permissionless you can come to the 00:34:47.460 --> 00:34:50.109 align:start position:0% a permissionless you can come to the calls<00:34:47.820> propose<00:34:48.359> idea<00:34:48.780> that<00:34:48.960> you<00:34:49.080> want<00:34:49.200> there 00:34:50.109 --> 00:34:50.119 align:start position:0% calls propose idea that you want there 00:34:50.119 --> 00:34:52.849 align:start position:0% calls propose idea that you want there there<00:34:51.119> are<00:34:51.419> calls<00:34:52.200> where<00:34:52.320> you<00:34:52.440> can<00:34:52.500> propose 00:34:52.849 --> 00:34:52.859 align:start position:0% there are calls where you can propose 00:34:52.859 --> 00:34:55.909 align:start position:0% there are calls where you can propose idea<00:34:53.280> in<00:34:53.520> an<00:34:53.639> issue<00:34:53.879> similar<00:34:54.240> to<00:34:54.359> ACD<00:34:54.839> uh<00:34:55.619> that 00:34:55.909 --> 00:34:55.919 align:start position:0% idea in an issue similar to ACD uh that 00:34:55.919 --> 00:34:58.250 align:start position:0% idea in an issue similar to ACD uh that I<00:34:56.099> would<00:34:56.159> like<00:34:56.280> to<00:34:56.399> discuss<00:34:56.700> this<00:34:56.940> and<00:34:57.900> uh 00:34:58.250 --> 00:34:58.260 align:start position:0% I would like to discuss this and uh 00:34:58.260 --> 00:35:00.230 align:start position:0% I would like to discuss this and uh we'll<00:34:58.500> invite<00:34:58.800> some<00:34:59.040> of<00:34:59.220> the<00:34:59.400> mentors<00:34:59.700> to<00:34:59.940> help 00:35:00.230 --> 00:35:00.240 align:start position:0% we'll invite some of the mentors to help 00:35:00.240 --> 00:35:02.089 align:start position:0% we'll invite some of the mentors to help you<00:35:00.359> with<00:35:00.540> that<00:35:00.720> give<00:35:01.020> you<00:35:01.200> some<00:35:01.380> guidance<00:35:01.740> so 00:35:02.089 --> 00:35:02.099 align:start position:0% you with that give you some guidance so 00:35:02.099 --> 00:35:04.010 align:start position:0% you with that give you some guidance so yeah<00:35:02.460> hopefully<00:35:02.880> it<00:35:03.000> can<00:35:03.119> help<00:35:03.240> and<00:35:03.660> if<00:35:03.780> not 00:35:04.010 --> 00:35:04.020 align:start position:0% yeah hopefully it can help and if not 00:35:04.020 --> 00:35:09.050 align:start position:0% yeah hopefully it can help and if not that 00:35:09.050 --> 00:35:09.060 align:start position:0% 00:35:09.060 --> 00:35:12.410 align:start position:0% well<00:35:09.359> and<00:35:10.200> uh<00:35:10.980> we<00:35:11.460> have<00:35:11.640> like<00:35:11.880> one<00:35:12.119> of<00:35:12.240> our 00:35:12.410 --> 00:35:12.420 align:start position:0% well and uh we have like one of our 00:35:12.420 --> 00:35:14.630 align:start position:0% well and uh we have like one of our projects<00:35:12.960> is<00:35:13.200> also<00:35:13.619> card<00:35:13.800> development<00:35:14.339> as 00:35:14.630 --> 00:35:14.640 align:start position:0% projects is also card development as 00:35:14.640 --> 00:35:17.210 align:start position:0% projects is also card development as well<00:35:14.760> where<00:35:15.540> we<00:35:15.839> we<00:35:16.200> are<00:35:16.440> very<00:35:16.619> happy<00:35:16.859> to<00:35:17.040> guide 00:35:17.210 --> 00:35:17.220 align:start position:0% well where we we are very happy to guide 00:35:17.220 --> 00:35:19.550 align:start position:0% well where we we are very happy to guide you<00:35:17.460> over<00:35:17.700> as<00:35:18.060> well 00:35:19.550 --> 00:35:19.560 align:start position:0% you over as well 00:35:19.560 --> 00:35:22.490 align:start position:0% you over as well um<00:35:19.680> yeah<00:35:19.980> we<00:35:20.280> are<00:35:20.460> always<00:35:20.700> hiring<00:35:21.300> new<00:35:21.780> interns 00:35:22.490 --> 00:35:22.500 align:start position:0% um yeah we are always hiring new interns 00:35:22.500 --> 00:35:24.890 align:start position:0% um yeah we are always hiring new interns so 00:35:24.890 --> 00:35:24.900 align:start position:0% so 00:35:24.900 --> 00:35:26.930 align:start position:0% so I<00:35:25.320> don't<00:35:25.440> know<00:35:25.560> yeah<00:35:25.859> so<00:35:26.160> this<00:35:26.400> is<00:35:26.520> like<00:35:26.700> sort 00:35:26.930 --> 00:35:26.940 align:start position:0% I don't know yeah so this is like sort 00:35:26.940 --> 00:35:29.150 align:start position:0% I don't know yeah so this is like sort of<00:35:27.060> like<00:35:27.240> should<00:35:27.660> be<00:35:27.900> your<00:35:28.140> base<00:35:28.440> layer<00:35:28.859> for 00:35:29.150 --> 00:35:29.160 align:start position:0% of like should be your base layer for 00:35:29.160 --> 00:35:31.790 align:start position:0% of like should be your base layer for where<00:35:29.579> to<00:35:29.700> find<00:35:29.880> more<00:35:30.240> cardiffs<00:35:31.140> related<00:35:31.500> or 00:35:31.790 --> 00:35:31.800 align:start position:0% where to find more cardiffs related or 00:35:31.800 --> 00:35:34.130 align:start position:0% where to find more cardiffs related or like<00:35:31.980> how<00:35:32.160> to<00:35:32.280> be<00:35:32.460> according 00:35:34.130 --> 00:35:34.140 align:start position:0% like how to be according 00:35:34.140 --> 00:35:35.750 align:start position:0% like how to be according um although<00:35:35.099> that<00:35:35.280> was<00:35:35.460> kind<00:35:35.700> of 00:35:35.750 --> 00:35:35.760 align:start position:0% um although that was kind of 00:35:35.760 --> 00:35:38.990 align:start position:0% um although that was kind of controversial<00:35:36.359> where<00:35:37.619> um<00:35:37.619> I<00:35:37.800> think<00:35:37.980> lane<00:35:38.339> or<00:35:38.700> I 00:35:38.990 --> 00:35:39.000 align:start position:0% controversial where um I think lane or I 00:35:39.000 --> 00:35:39.829 align:start position:0% controversial where um I think lane or I mean 00:35:39.829 --> 00:35:39.839 align:start position:0% mean 00:35:39.839 --> 00:35:42.650 align:start position:0% mean yeah I<00:35:40.440> mean<00:35:40.619> it<00:35:40.740> was<00:35:40.920> like<00:35:41.339> oh<00:35:42.000> he's<00:35:42.240> a<00:35:42.300> cardos 00:35:42.650 --> 00:35:42.660 align:start position:0% yeah I mean it was like oh he's a cardos 00:35:42.660 --> 00:35:46.790 align:start position:0% yeah I mean it was like oh he's a cardos can<00:35:42.960> I<00:35:43.079> be<00:35:43.200> a<00:35:43.260> quarterback 00:35:46.790 --> 00:35:46.800 align:start position:0% 00:35:46.800 --> 00:35:51.710 align:start position:0% um<00:35:46.980> yeah<00:35:47.339> who<00:35:47.640> else 00:35:51.710 --> 00:35:51.720 align:start position:0% 00:35:51.720 --> 00:35:54.230 align:start position:0% ever<00:35:52.200> be<00:35:52.440> a<00:35:52.619> hackathon<00:35:53.160> for<00:35:53.880> this<00:35:54.000> sort<00:35:54.180> of 00:35:54.230 --> 00:35:54.240 align:start position:0% ever be a hackathon for this sort of 00:35:54.240 --> 00:35:55.970 align:start position:0% ever be a hackathon for this sort of thing<00:35:54.359> uh<00:35:54.960> maybe<00:35:55.020> like<00:35:55.260> a<00:35:55.440> three-day<00:35:55.740> thing 00:35:55.970 --> 00:35:55.980 align:start position:0% thing uh maybe like a three-day thing 00:35:55.980 --> 00:35:58.609 align:start position:0% thing uh maybe like a three-day thing event<00:35:56.700> where<00:35:57.060> people<00:35:57.240> can<00:35:57.540> work<00:35:58.079> on<00:35:58.320> funny 00:35:58.609 --> 00:35:58.619 align:start position:0% event where people can work on funny 00:35:58.619 --> 00:35:59.510 align:start position:0% event where people can work on funny stuff 00:35:59.510 --> 00:35:59.520 align:start position:0% stuff 00:35:59.520 --> 00:36:01.670 align:start position:0% stuff we<00:35:59.940> should<00:36:00.119> do<00:36:00.300> that<00:36:00.480> because<00:36:01.079> Kristoff 00:36:01.670 --> 00:36:01.680 align:start position:0% we should do that because Kristoff 00:36:01.680 --> 00:36:04.250 align:start position:0% we should do that because Kristoff wanted<00:36:02.280> to<00:36:02.579> do<00:36:02.820> one<00:36:03.180> in<00:36:03.540> like<00:36:03.720> never<00:36:04.020> mind 00:36:04.250 --> 00:36:04.260 align:start position:0% wanted to do one in like never mind 00:36:04.260 --> 00:36:07.130 align:start position:0% wanted to do one in like never mind hackathon<00:36:05.099> uh<00:36:06.060> but<00:36:06.240> it<00:36:06.359> was<00:36:06.540> like<00:36:06.720> it<00:36:06.960> was 00:36:07.130 --> 00:36:07.140 align:start position:0% hackathon uh but it was like it was 00:36:07.140 --> 00:36:08.630 align:start position:0% hackathon uh but it was like it was supposed<00:36:07.320> to<00:36:07.440> be<00:36:07.619> internal<00:36:08.040> but<00:36:08.339> I'm<00:36:08.460> very 00:36:08.630 --> 00:36:08.640 align:start position:0% supposed to be internal but I'm very 00:36:08.640 --> 00:36:10.970 align:start position:0% supposed to be internal but I'm very happy<00:36:08.820> to<00:36:09.000> take<00:36:09.180> this<00:36:09.359> over<00:36:09.599> and 00:36:10.970 --> 00:36:10.980 align:start position:0% happy to take this over and 00:36:10.980 --> 00:36:13.130 align:start position:0% happy to take this over and um<00:36:11.040> do<00:36:11.280> sort<00:36:11.520> of<00:36:11.640> like<00:36:11.700> a<00:36:11.940> chord<00:36:12.180> of<00:36:12.480> uh 00:36:13.130 --> 00:36:13.140 align:start position:0% um do sort of like a chord of uh 00:36:13.140 --> 00:36:16.069 align:start position:0% um do sort of like a chord of uh hackathon<00:36:13.680> and<00:36:14.099> I<00:36:14.820> mean<00:36:15.000> Mario<00:36:15.480> should 00:36:16.069 --> 00:36:16.079 align:start position:0% hackathon and I mean Mario should 00:36:16.079 --> 00:36:19.069 align:start position:0% hackathon and I mean Mario should definitely<00:36:16.440> collaborate<00:36:17.099> on<00:36:17.339> that 00:36:19.069 --> 00:36:19.079 align:start position:0% definitely collaborate on that 00:36:19.079 --> 00:36:20.870 align:start position:0% definitely collaborate on that Thomas<00:36:19.500> is<00:36:19.859> okay<00:36:19.980> with<00:36:20.220> that<00:36:20.400> because<00:36:20.640> he's 00:36:20.870 --> 00:36:20.880 align:start position:0% Thomas is okay with that because he's 00:36:20.880 --> 00:36:22.910 align:start position:0% Thomas is okay with that because he's like<00:36:21.119> my<00:36:21.240> boss<00:36:21.480> right<00:36:21.720> now<00:36:21.900> because<00:36:22.680> I'm 00:36:22.910 --> 00:36:22.920 align:start position:0% like my boss right now because I'm 00:36:22.920 --> 00:36:25.690 align:start position:0% like my boss right now because I'm leading<00:36:23.220> the<00:36:23.339> internship<00:36:23.640> program<00:36:23.940> so 00:36:25.690 --> 00:36:25.700 align:start position:0% leading the internship program so 00:36:25.700 --> 00:36:28.190 align:start position:0% leading the internship program so just<00:36:26.700> quickly<00:36:27.000> I<00:36:27.180> was<00:36:27.300> going<00:36:27.420> to<00:36:27.540> say 00:36:28.190 --> 00:36:28.200 align:start position:0% just quickly I was going to say 00:36:28.200 --> 00:36:30.650 align:start position:0% just quickly I was going to say um<00:36:28.260> it's<00:36:28.859> a<00:36:28.980> lot<00:36:29.160> of<00:36:29.339> the<00:36:29.760> open<00:36:29.940> source<00:36:30.300> repos 00:36:30.650 --> 00:36:30.660 align:start position:0% um it's a lot of the open source repos 00:36:30.660 --> 00:36:32.810 align:start position:0% um it's a lot of the open source repos also<00:36:31.079> have<00:36:31.200> tickets<00:36:31.440> that<00:36:31.800> are<00:36:31.980> marked<00:36:32.280> good 00:36:32.810 --> 00:36:32.820 align:start position:0% also have tickets that are marked good 00:36:32.820 --> 00:36:35.990 align:start position:0% also have tickets that are marked good to<00:36:32.940> start<00:36:33.060> development<00:36:33.480> on<00:36:34.200> so<00:36:35.040> that's 00:36:35.990 --> 00:36:36.000 align:start position:0% to start development on so that's 00:36:36.000 --> 00:36:38.270 align:start position:0% to start development on so that's another<00:36:36.180> Avenue<00:36:36.480> it<00:36:37.200> does<00:36:37.320> get<00:36:37.500> taken<00:36:37.800> up<00:36:37.980> by 00:36:38.270 --> 00:36:38.280 align:start position:0% another Avenue it does get taken up by 00:36:38.280 --> 00:36:41.270 align:start position:0% another Avenue it does get taken up by contributors<00:36:39.020> and<00:36:40.020> we<00:36:40.619> review<00:36:40.800> and<00:36:41.099> give 00:36:41.270 --> 00:36:41.280 align:start position:0% contributors and we review and give 00:36:41.280 --> 00:36:43.370 align:start position:0% contributors and we review and give feedback<00:36:41.579> and<00:36:41.820> help<00:36:42.060> and 00:36:43.370 --> 00:36:43.380 align:start position:0% feedback and help and 00:36:43.380 --> 00:36:45.770 align:start position:0% feedback and help and so<00:36:43.740> there<00:36:44.460> are<00:36:44.579> a<00:36:44.640> few<00:36:44.700> averages<00:36:45.060> but<00:36:45.359> it<00:36:45.480> is<00:36:45.599> a 00:36:45.770 --> 00:36:45.780 align:start position:0% so there are a few averages but it is a 00:36:45.780 --> 00:36:52.430 align:start position:0% so there are a few averages but it is a big<00:36:46.380> it's<00:36:46.920> a<00:36:47.099> learning<00:36:47.579> curve 00:36:52.430 --> 00:36:52.440 align:start position:0% 00:36:52.440 --> 00:36:55.310 align:start position:0% um<00:36:52.560> so<00:36:53.160> we<00:36:54.119> were<00:36:54.300> working<00:36:54.480> this<00:36:54.780> weekend<00:36:55.020> on 00:36:55.310 --> 00:36:55.320 align:start position:0% um so we were working this weekend on 00:36:55.320 --> 00:36:57.710 align:start position:0% um so we were working this weekend on the<00:36:55.440> eth<00:36:55.680> Bogota<00:36:56.339> on<00:36:56.640> some<00:36:56.880> hypothesis 00:36:57.710 --> 00:36:57.720 align:start position:0% the eth Bogota on some hypothesis 00:36:57.720 --> 00:37:00.950 align:start position:0% the eth Bogota on some hypothesis regarding<00:36:58.440> the<00:36:58.859> new<00:36:59.460> proof<00:36:59.940> of<00:37:00.000> approval 00:37:00.950 --> 00:37:00.960 align:start position:0% regarding the new proof of approval 00:37:00.960 --> 00:37:04.130 align:start position:0% regarding the new proof of approval stake<00:37:01.260> system<00:37:01.700> and<00:37:02.700> one<00:37:03.000> question<00:37:03.240> we<00:37:03.720> written 00:37:04.130 --> 00:37:04.140 align:start position:0% stake system and one question we written 00:37:04.140 --> 00:37:07.010 align:start position:0% stake system and one question we written couldn't<00:37:04.440> get<00:37:04.800> answered<00:37:05.339> was<00:37:05.640> now<00:37:06.599> with<00:37:06.900> the 00:37:07.010 --> 00:37:07.020 align:start position:0% couldn't get answered was now with the 00:37:07.020 --> 00:37:09.589 align:start position:0% couldn't get answered was now with the new<00:37:07.140> approval<00:37:07.560> stake<00:37:07.920> system<00:37:08.160> is<00:37:08.700> how<00:37:09.119> the<00:37:09.359> Box 00:37:09.589 --> 00:37:09.599 align:start position:0% new approval stake system is how the Box 00:37:09.599 --> 00:37:12.770 align:start position:0% new approval stake system is how the Box the<00:37:10.140> blocks<00:37:10.680> get<00:37:10.859> built<00:37:11.339> is<00:37:12.000> it<00:37:12.180> still<00:37:12.420> purely 00:37:12.770 --> 00:37:12.780 align:start position:0% the blocks get built is it still purely 00:37:12.780 --> 00:37:15.230 align:start position:0% the blocks get built is it still purely an<00:37:13.020> economical<00:37:13.500> incentive<00:37:14.099> as<00:37:14.760> where<00:37:15.060> they 00:37:15.230 --> 00:37:15.240 align:start position:0% an economical incentive as where they 00:37:15.240 --> 00:37:17.270 align:start position:0% an economical incentive as where they choose<00:37:15.599> the<00:37:15.720> highest<00:37:16.020> fees<00:37:16.380> for<00:37:16.619> the<00:37:16.800> or<00:37:17.099> the 00:37:17.270 --> 00:37:17.280 align:start position:0% choose the highest fees for the or the 00:37:17.280 --> 00:37:19.190 align:start position:0% choose the highest fees for the or the highest<00:37:17.520> prices<00:37:17.760> to<00:37:18.180> include<00:37:18.420> in<00:37:18.660> the<00:37:18.839> blocks 00:37:19.190 --> 00:37:19.200 align:start position:0% highest prices to include in the blocks 00:37:19.200 --> 00:37:22.130 align:start position:0% highest prices to include in the blocks or<00:37:20.040> are<00:37:20.280> there<00:37:20.460> other<00:37:20.940> incentives<00:37:21.599> include 00:37:22.130 --> 00:37:22.140 align:start position:0% or are there other incentives include 00:37:22.140 --> 00:37:24.530 align:start position:0% or are there other incentives include included<00:37:23.099> as<00:37:23.339> there's<00:37:23.520> an<00:37:23.760> increased<00:37:24.119> risk<00:37:24.420> of 00:37:24.530 --> 00:37:24.540 align:start position:0% included as there's an increased risk of 00:37:24.540 --> 00:37:29.210 align:start position:0% included as there's an increased risk of slashing 00:37:29.210 --> 00:37:29.220 align:start position:0% 00:37:29.220 --> 00:37:32.510 align:start position:0% so<00:37:29.760> they<00:37:30.240> the<00:37:30.960> blog<00:37:31.260> building<00:37:31.500> doesn't<00:37:32.280> really 00:37:32.510 --> 00:37:32.520 align:start position:0% so they the blog building doesn't really 00:37:32.520 --> 00:37:34.370 align:start position:0% so they the blog building doesn't really lead<00:37:32.880> to<00:37:33.119> the<00:37:33.300> slash<00:37:33.599> increase<00:37:33.780> slash 00:37:34.370 --> 00:37:34.380 align:start position:0% lead to the slash increase slash 00:37:34.380 --> 00:37:35.829 align:start position:0% lead to the slash increase slash increases<00:37:34.859> are<00:37:35.040> only 00:37:35.829 --> 00:37:35.839 align:start position:0% increases are only 00:37:35.839 --> 00:37:39.170 align:start position:0% increases are only related<00:37:36.839> to<00:37:37.140> the<00:37:37.680> double<00:37:38.339> signing<00:37:38.940> like 00:37:39.170 --> 00:37:39.180 align:start position:0% related to the double signing like 00:37:39.180 --> 00:37:41.329 align:start position:0% related to the double signing like signing<00:37:39.720> two<00:37:40.200> different<00:37:40.440> blocks<00:37:40.920> or 00:37:41.329 --> 00:37:41.339 align:start position:0% signing two different blocks or 00:37:41.339 --> 00:37:43.370 align:start position:0% signing two different blocks or attaching<00:37:42.300> to<00:37:42.480> two<00:37:42.660> different<00:37:42.780> blocks<00:37:43.200> of 00:37:43.370 --> 00:37:43.380 align:start position:0% attaching to two different blocks of 00:37:43.380 --> 00:37:45.349 align:start position:0% attaching to two different blocks of proposing<00:37:43.859> to<00:37:44.339> conflicting<00:37:44.940> blocks<00:37:45.240> or 00:37:45.349 --> 00:37:45.359 align:start position:0% proposing to conflicting blocks or 00:37:45.359 --> 00:37:48.470 align:start position:0% proposing to conflicting blocks or attesting<00:37:45.839> to<00:37:45.960> conflicting<00:37:46.619> blocks<00:37:47.400> so<00:37:48.119> they 00:37:48.470 --> 00:37:48.480 align:start position:0% attesting to conflicting blocks so they 00:37:48.480 --> 00:37:50.990 align:start position:0% attesting to conflicting blocks so they yeah<00:37:49.200> it's<00:37:49.680> it<00:37:49.980> should<00:37:50.339> be<00:37:50.460> economical 00:37:50.990 --> 00:37:51.000 align:start position:0% yeah it's it should be economical 00:37:51.000 --> 00:37:52.550 align:start position:0% yeah it's it should be economical incentive<00:37:51.480> it<00:37:51.660> should<00:37:51.839> be 00:37:52.550 --> 00:37:52.560 align:start position:0% incentive it should be 00:37:52.560 --> 00:37:54.410 align:start position:0% incentive it should be a<00:37:52.800> line<00:37:53.099> incentive<00:37:53.640> something<00:37:53.880> that<00:37:54.119> is<00:37:54.240> very 00:37:54.410 --> 00:37:54.420 align:start position:0% a line incentive something that is very 00:37:54.420 --> 00:37:55.910 align:start position:0% a line incentive something that is very natural<00:37:54.599> so<00:37:54.960> the<00:37:55.079> blood<00:37:55.200> Builder<00:37:55.619> is<00:37:55.740> looking 00:37:55.910 --> 00:37:55.920 align:start position:0% natural so the blood Builder is looking 00:37:55.920 --> 00:37:58.150 align:start position:0% natural so the blood Builder is looking for<00:37:56.160> the<00:37:56.280> payout<00:37:56.700> and 00:37:58.150 --> 00:37:58.160 align:start position:0% for the payout and 00:37:58.160 --> 00:38:00.410 align:start position:0% for the payout and collects<00:37:59.160> the<00:37:59.460> transactions<00:38:00.119> that<00:38:00.300> are 00:38:00.410 --> 00:38:00.420 align:start position:0% collects the transactions that are 00:38:00.420 --> 00:38:02.810 align:start position:0% collects the transactions that are paying<00:38:00.720> the<00:38:00.839> most<00:38:01.020> uh<00:38:01.800> plus<00:38:02.099> there<00:38:02.520> might<00:38:02.700> be 00:38:02.810 --> 00:38:02.820 align:start position:0% paying the most uh plus there might be 00:38:02.820 --> 00:38:04.010 align:start position:0% paying the most uh plus there might be any 00:38:04.010 --> 00:38:04.020 align:start position:0% any 00:38:04.020 --> 00:38:07.609 align:start position:0% any not<00:38:04.920> clearly<00:38:05.700> economical<00:38:06.359> not<00:38:06.660> Financial<00:38:06.900> but 00:38:07.609 --> 00:38:07.619 align:start position:0% not clearly economical not Financial but 00:38:07.619 --> 00:38:10.730 align:start position:0% not clearly economical not Financial but still<00:38:07.859> quantifiable<00:38:08.579> benefits 00:38:10.730 --> 00:38:10.740 align:start position:0% still quantifiable benefits 00:38:10.740 --> 00:38:13.930 align:start position:0% still quantifiable benefits right<00:38:11.400> so<00:38:11.880> Thomas<00:38:12.359> is<00:38:12.720> right<00:38:12.960> about<00:38:13.140> slashing 00:38:13.930 --> 00:38:13.940 align:start position:0% right so Thomas is right about slashing 00:38:13.940 --> 00:38:16.609 align:start position:0% right so Thomas is right about slashing there<00:38:14.940> are<00:38:15.119> inactivity<00:38:15.660> penalties<00:38:16.200> which<00:38:16.440> are 00:38:16.609 --> 00:38:16.619 align:start position:0% there are inactivity penalties which are 00:38:16.619 --> 00:38:19.550 align:start position:0% there are inactivity penalties which are often<00:38:16.859> confused<00:38:17.280> with<00:38:17.460> slashings<00:38:18.140> which<00:38:19.140> you 00:38:19.550 --> 00:38:19.560 align:start position:0% often confused with slashings which you 00:38:19.560 --> 00:38:24.230 align:start position:0% often confused with slashings which you can<00:38:19.619> incur<00:38:20.300> if<00:38:21.300> you<00:38:21.839> miss<00:38:22.200> your<00:38:22.619> proposal<00:38:23.240> and 00:38:24.230 --> 00:38:24.240 align:start position:0% can incur if you miss your proposal and 00:38:24.240 --> 00:38:27.290 align:start position:0% can incur if you miss your proposal and for<00:38:25.079> example<00:38:25.380> if<00:38:26.099> that<00:38:26.280> latency<00:38:26.700> is<00:38:26.940> very<00:38:27.060> high 00:38:27.290 --> 00:38:27.300 align:start position:0% for example if that latency is very high 00:38:27.300 --> 00:38:28.730 align:start position:0% for example if that latency is very high because<00:38:27.540> they're<00:38:27.780> using<00:38:28.079> an<00:38:28.200> external<00:38:28.560> block 00:38:28.730 --> 00:38:28.740 align:start position:0% because they're using an external block 00:38:28.740 --> 00:38:31.130 align:start position:0% because they're using an external block Builder<00:38:29.160> surface 00:38:31.130 --> 00:38:31.140 align:start position:0% Builder surface 00:38:31.140 --> 00:38:33.829 align:start position:0% Builder surface um so<00:38:32.040> that's<00:38:32.640> one 00:38:33.829 --> 00:38:33.839 align:start position:0% um so that's one 00:38:33.839 --> 00:38:36.710 align:start position:0% um so that's one incentive<00:38:34.800> for<00:38:35.040> people<00:38:35.820> to<00:38:36.180> use<00:38:36.420> lower 00:38:36.710 --> 00:38:36.720 align:start position:0% incentive for people to use lower 00:38:36.720 --> 00:38:39.170 align:start position:0% incentive for people to use lower latency<00:38:37.140> Services<00:38:37.579> it<00:38:38.579> should<00:38:38.760> just<00:38:38.940> be<00:38:39.000> your 00:38:39.170 --> 00:38:39.180 align:start position:0% latency Services it should just be your 00:38:39.180 --> 00:38:40.370 align:start position:0% latency Services it should just be your or<00:38:39.420> not 00:38:40.370 --> 00:38:40.380 align:start position:0% or not 00:38:40.380 --> 00:38:42.290 align:start position:0% or not but<00:38:40.800> I<00:38:40.980> do<00:38:41.040> think<00:38:41.280> that's 00:38:42.290 --> 00:38:42.300 align:start position:0% but I do think that's 00:38:42.300 --> 00:38:44.390 align:start position:0% but I do think that's part<00:38:42.720> of<00:38:42.839> the<00:38:42.960> whole<00:38:43.079> MEP<00:38:43.560> discussion<00:38:43.980> and<00:38:44.160> how 00:38:44.390 --> 00:38:44.400 align:start position:0% part of the whole MEP discussion and how 00:38:44.400 --> 00:38:48.050 align:start position:0% part of the whole MEP discussion and how we<00:38:44.579> make<00:38:45.800> homesteakers<00:38:46.800> as<00:38:47.099> competitive<00:38:47.640> with 00:38:48.050 --> 00:38:48.060 align:start position:0% we make homesteakers as competitive with 00:38:48.060 --> 00:38:50.530 align:start position:0% we make homesteakers as competitive with regular<00:38:48.359> stakers<00:38:48.900> when<00:38:49.680> it<00:38:49.859> comes<00:38:50.160> to 00:38:50.530 --> 00:38:50.540 align:start position:0% regular stakers when it comes to 00:38:50.540 --> 00:38:53.270 align:start position:0% regular stakers when it comes to publishing<00:38:51.540> blocks<00:38:52.200> so<00:38:52.440> that<00:38:52.619> they<00:38:52.859> get 00:38:53.270 --> 00:38:53.280 align:start position:0% publishing blocks so that they get 00:38:53.280 --> 00:38:56.210 align:start position:0% publishing blocks so that they get adjusted<00:38:53.760> timely<00:38:54.060> and<00:38:54.300> they're<00:38:54.420> not<00:38:54.599> missed 00:38:56.210 --> 00:38:56.220 align:start position:0% adjusted timely and they're not missed 00:38:56.220 --> 00:38:58.370 align:start position:0% adjusted timely and they're not missed and<00:38:56.760> larger<00:38:57.119> blocks<00:38:57.540> obviously<00:38:57.960> and<00:38:58.200> they 00:38:58.370 --> 00:38:58.380 align:start position:0% and larger blocks obviously and they 00:38:58.380 --> 00:39:00.410 align:start position:0% and larger blocks obviously and they they<00:38:58.980> are<00:38:59.220> they<00:38:59.339> cost<00:38:59.520> more<00:38:59.700> expensive<00:39:00.119> they 00:39:00.410 --> 00:39:00.420 align:start position:0% they are they cost more expensive they 00:39:00.420 --> 00:39:03.290 align:start position:0% they are they cost more expensive they cost<00:39:00.660> more<00:39:00.960> time<00:39:01.200> to<00:39:01.440> propagate<00:39:02.060> so<00:39:03.060> that 00:39:03.290 --> 00:39:03.300 align:start position:0% cost more time to propagate so that 00:39:03.300 --> 00:39:06.290 align:start position:0% cost more time to propagate so that might<00:39:03.599> play<00:39:03.780> a<00:39:03.960> role 00:39:06.290 --> 00:39:06.300 align:start position:0% 00:39:06.300 --> 00:39:09.950 align:start position:0% thank<00:39:06.900> you 00:39:09.950 --> 00:39:09.960 align:start position:0% 00:39:09.960 --> 00:39:13.069 align:start position:0% I<00:39:10.440> just<00:39:10.560> wanted<00:39:10.680> this 00:39:13.069 --> 00:39:13.079 align:start position:0% 00:39:13.079 --> 00:39:14.930 align:start position:0% I<00:39:13.560> was<00:39:13.800> just<00:39:13.920> going<00:39:14.040> to<00:39:14.160> circle<00:39:14.400> back<00:39:14.700> very 00:39:14.930 --> 00:39:14.940 align:start position:0% I was just going to circle back very 00:39:14.940 --> 00:39:16.970 align:start position:0% I was just going to circle back very quickly<00:39:15.240> to<00:39:15.720> the<00:39:16.200> question<00:39:16.380> about<00:39:16.560> how<00:39:16.800> to<00:39:16.920> be 00:39:16.970 --> 00:39:16.980 align:start position:0% quickly to the question about how to be 00:39:16.980 --> 00:39:18.530 align:start position:0% quickly to the question about how to be a<00:39:17.160> core<00:39:17.400> developer<00:39:17.820> and<00:39:18.000> I<00:39:18.119> wanted<00:39:18.300> to<00:39:18.420> say 00:39:18.530 --> 00:39:18.540 align:start position:0% a core developer and I wanted to say 00:39:18.540 --> 00:39:20.569 align:start position:0% a core developer and I wanted to say that<00:39:18.720> there's<00:39:18.900> I<00:39:19.079> think<00:39:19.200> there's<00:39:19.440> two<00:39:19.920> things 00:39:20.569 --> 00:39:20.579 align:start position:0% that there's I think there's two things 00:39:20.579 --> 00:39:23.569 align:start position:0% that there's I think there's two things to<00:39:20.820> consider<00:39:21.180> the<00:39:21.839> first<00:39:22.020> is<00:39:22.320> just<00:39:23.040> follow<00:39:23.280> all 00:39:23.569 --> 00:39:23.579 align:start position:0% to consider the first is just follow all 00:39:23.579 --> 00:39:25.970 align:start position:0% to consider the first is just follow all core<00:39:23.820> devs<00:39:24.359> the<00:39:24.660> best<00:39:24.839> of<00:39:24.960> your<00:39:25.140> ability<00:39:25.380> I 00:39:25.970 --> 00:39:25.980 align:start position:0% core devs the best of your ability I 00:39:25.980 --> 00:39:28.130 align:start position:0% core devs the best of your ability I think<00:39:26.099> orienting<00:39:26.760> oneself<00:39:27.540> around<00:39:27.839> like 00:39:28.130 --> 00:39:28.140 align:start position:0% think orienting oneself around like 00:39:28.140 --> 00:39:29.150 align:start position:0% think orienting oneself around like what's<00:39:28.320> actually<00:39:28.560> happening<00:39:28.920> in<00:39:29.040> the 00:39:29.150 --> 00:39:29.160 align:start position:0% what's actually happening in the 00:39:29.160 --> 00:39:31.490 align:start position:0% what's actually happening in the protocol<00:39:29.480> starts<00:39:30.480> to<00:39:30.599> make<00:39:30.839> it<00:39:30.960> a<00:39:31.079> lot<00:39:31.200> clearer 00:39:31.490 --> 00:39:31.500 align:start position:0% protocol starts to make it a lot clearer 00:39:31.500 --> 00:39:32.990 align:start position:0% protocol starts to make it a lot clearer like<00:39:31.680> where<00:39:32.040> are<00:39:32.220> places<00:39:32.400> that<00:39:32.640> you<00:39:32.820> can 00:39:32.990 --> 00:39:33.000 align:start position:0% like where are places that you can 00:39:33.000 --> 00:39:35.390 align:start position:0% like where are places that you can contribute<00:39:33.359> to<00:39:33.599> so<00:39:34.260> doing<00:39:34.500> that<00:39:34.800> and<00:39:35.040> then<00:39:35.160> I 00:39:35.390 --> 00:39:35.400 align:start position:0% contribute to so doing that and then I 00:39:35.400 --> 00:39:37.010 align:start position:0% contribute to so doing that and then I haven't<00:39:35.520> talked<00:39:35.880> to<00:39:35.940> a<00:39:36.119> core<00:39:36.300> developer<00:39:36.720> in<00:39:36.900> a 00:39:37.010 --> 00:39:37.020 align:start position:0% haven't talked to a core developer in a 00:39:37.020 --> 00:39:38.210 align:start position:0% haven't talked to a core developer in a long<00:39:37.140> time<00:39:37.260> who<00:39:37.500> doesn't<00:39:37.680> have<00:39:37.859> a<00:39:38.099> long 00:39:38.210 --> 00:39:38.220 align:start position:0% long time who doesn't have a long 00:39:38.220 --> 00:39:39.589 align:start position:0% long time who doesn't have a long laundry<00:39:38.460> list<00:39:38.820> of<00:39:39.000> things<00:39:39.180> that<00:39:39.359> they<00:39:39.480> would 00:39:39.589 --> 00:39:39.599 align:start position:0% laundry list of things that they would 00:39:39.599 --> 00:39:40.849 align:start position:0% laundry list of things that they would love<00:39:39.720> to<00:39:39.900> happen<00:39:40.079> that<00:39:40.380> they<00:39:40.560> just<00:39:40.680> simply 00:39:40.849 --> 00:39:40.859 align:start position:0% love to happen that they just simply 00:39:40.859 --> 00:39:42.230 align:start position:0% love to happen that they just simply don't<00:39:40.980> have<00:39:41.099> enough<00:39:41.220> hours<00:39:41.400> in<00:39:41.640> the<00:39:41.760> day<00:39:41.880> to<00:39:42.060> do 00:39:42.230 --> 00:39:42.240 align:start position:0% don't have enough hours in the day to do 00:39:42.240 --> 00:39:44.810 align:start position:0% don't have enough hours in the day to do so<00:39:43.140> maybe<00:39:43.380> once<00:39:43.920> you're<00:39:44.099> feeling<00:39:44.460> more 00:39:44.810 --> 00:39:44.820 align:start position:0% so maybe once you're feeling more 00:39:44.820 --> 00:39:46.310 align:start position:0% so maybe once you're feeling more oriented<00:39:45.240> with<00:39:45.420> the<00:39:45.720> direction<00:39:45.900> of<00:39:46.200> the 00:39:46.310 --> 00:39:46.320 align:start position:0% oriented with the direction of the 00:39:46.320 --> 00:39:47.870 align:start position:0% oriented with the direction of the protocol<00:39:46.560> to<00:39:46.920> try<00:39:47.099> and<00:39:47.160> just<00:39:47.280> reach<00:39:47.520> out<00:39:47.579> to<00:39:47.760> a 00:39:47.870 --> 00:39:47.880 align:start position:0% protocol to try and just reach out to a 00:39:47.880 --> 00:39:49.609 align:start position:0% protocol to try and just reach out to a core<00:39:48.000> developer<00:39:48.420> and<00:39:48.540> say<00:39:48.720> hey 00:39:49.609 --> 00:39:49.619 align:start position:0% core developer and say hey 00:39:49.619 --> 00:39:51.170 align:start position:0% core developer and say hey you<00:39:49.980> know<00:39:50.099> this<00:39:50.280> is<00:39:50.400> my<00:39:50.520> skill<00:39:50.700> set<00:39:50.880> this<00:39:51.060> is 00:39:51.170 --> 00:39:51.180 align:start position:0% you know this is my skill set this is 00:39:51.180 --> 00:39:53.150 align:start position:0% you know this is my skill set this is where<00:39:51.300> I'm<00:39:51.420> coming<00:39:51.540> from<00:39:51.780> you<00:39:52.680> know<00:39:52.800> do<00:39:53.040> you 00:39:53.150 --> 00:39:53.160 align:start position:0% where I'm coming from you know do you 00:39:53.160 --> 00:39:54.530 align:start position:0% where I'm coming from you know do you have<00:39:53.220> a<00:39:53.339> project<00:39:53.460> in<00:39:53.760> mind<00:39:54.000> that<00:39:54.119> I<00:39:54.300> might<00:39:54.420> be 00:39:54.530 --> 00:39:54.540 align:start position:0% have a project in mind that I might be 00:39:54.540 --> 00:39:56.030 align:start position:0% have a project in mind that I might be able<00:39:54.599> to<00:39:54.720> help<00:39:54.839> with<00:39:55.020> and<00:39:55.320> I<00:39:55.440> think<00:39:55.560> like<00:39:55.680> once 00:39:56.030 --> 00:39:56.040 align:start position:0% able to help with and I think like once 00:39:56.040 --> 00:39:57.470 align:start position:0% able to help with and I think like once you<00:39:56.099> start<00:39:56.280> doing<00:39:56.700> a<00:39:56.880> little<00:39:57.000> bit<00:39:57.060> of<00:39:57.180> that<00:39:57.300> and 00:39:57.470 --> 00:39:57.480 align:start position:0% you start doing a little bit of that and 00:39:57.480 --> 00:39:59.030 align:start position:0% you start doing a little bit of that and showing<00:39:57.839> that<00:39:58.140> there's<00:39:58.500> like<00:39:58.920> you're 00:39:59.030 --> 00:39:59.040 align:start position:0% showing that there's like you're 00:39:59.040 --> 00:40:01.490 align:start position:0% showing that there's like you're creating<00:39:59.339> value<00:39:59.640> then<00:40:00.300> core<00:40:00.660> teams<00:40:01.260> love 00:40:01.490 --> 00:40:01.500 align:start position:0% creating value then core teams love 00:40:01.500 --> 00:40:04.910 align:start position:0% creating value then core teams love hiring<00:40:01.980> people<00:40:02.280> so<00:40:03.240> this<00:40:03.540> is<00:40:03.780> uh<00:40:04.079> this<00:40:04.740> is<00:40:04.859> what 00:40:04.910 --> 00:40:04.920 align:start position:0% hiring people so this is uh this is what 00:40:04.920 --> 00:40:07.430 align:start position:0% hiring people so this is uh this is what I<00:40:05.099> would<00:40:05.160> recommend<00:40:05.460> all<00:40:06.300> the<00:40:06.540> tiny<00:40:07.079> note<00:40:07.200> on 00:40:07.430 --> 00:40:07.440 align:start position:0% I would recommend all the tiny note on 00:40:07.440 --> 00:40:10.190 align:start position:0% I would recommend all the tiny note on that<00:40:07.619> about<00:40:07.980> like<00:40:08.339> following<00:40:08.700> your<00:40:08.940> devs 00:40:10.190 --> 00:40:10.200 align:start position:0% that about like following your devs 00:40:10.200 --> 00:40:12.710 align:start position:0% that about like following your devs um as<00:40:10.560> the<00:40:10.800> guy<00:40:10.980> who<00:40:11.160> runs<00:40:11.640> it<00:40:11.760> the<00:40:12.300> first<00:40:12.420> like 00:40:12.710 --> 00:40:12.720 align:start position:0% um as the guy who runs it the first like 00:40:12.720 --> 00:40:15.530 align:start position:0% um as the guy who runs it the first like six<00:40:13.079> months<00:40:13.500> or<00:40:13.800> so<00:40:14.040> it<00:40:14.579> was<00:40:14.700> my<00:40:14.880> job<00:40:15.060> to<00:40:15.240> attend 00:40:15.530 --> 00:40:15.540 align:start position:0% six months or so it was my job to attend 00:40:15.540 --> 00:40:16.849 align:start position:0% six months or so it was my job to attend all<00:40:15.720> core<00:40:15.900> devs<00:40:16.260> I<00:40:16.320> just<00:40:16.440> like<00:40:16.619> didn't 00:40:16.849 --> 00:40:16.859 align:start position:0% all core devs I just like didn't 00:40:16.859 --> 00:40:18.349 align:start position:0% all core devs I just like didn't understand<00:40:17.160> anything<00:40:17.579> that<00:40:17.880> was<00:40:18.060> happening 00:40:18.349 --> 00:40:18.359 align:start position:0% understand anything that was happening 00:40:18.359 --> 00:40:20.089 align:start position:0% understand anything that was happening and<00:40:18.900> like<00:40:19.020> it<00:40:19.260> was<00:40:19.440> literally<00:40:19.740> like<00:40:19.920> too 00:40:20.089 --> 00:40:20.099 align:start position:0% and like it was literally like too 00:40:20.099 --> 00:40:22.069 align:start position:0% and like it was literally like too intimidated<00:40:20.640> to<00:40:20.940> like<00:40:21.060> speak<00:40:21.240> up<00:40:21.420> so<00:40:21.660> like<00:40:21.839> if 00:40:22.069 --> 00:40:22.079 align:start position:0% intimidated to like speak up so like if 00:40:22.079 --> 00:40:23.450 align:start position:0% intimidated to like speak up so like if that's<00:40:22.200> your<00:40:22.440> feeling 00:40:23.450 --> 00:40:23.460 align:start position:0% that's your feeling 00:40:23.460 --> 00:40:25.430 align:start position:0% that's your feeling um<00:40:23.520> that's<00:40:23.760> normal<00:40:24.000> and<00:40:24.780> if<00:40:25.020> you're<00:40:25.140> smarter 00:40:25.430 --> 00:40:25.440 align:start position:0% um that's normal and if you're smarter 00:40:25.440 --> 00:40:26.630 align:start position:0% um that's normal and if you're smarter than<00:40:25.500> me<00:40:25.619> it'll<00:40:25.800> probably<00:40:25.920> not<00:40:26.160> last<00:40:26.339> six 00:40:26.630 --> 00:40:26.640 align:start position:0% than me it'll probably not last six 00:40:26.640 --> 00:40:29.450 align:start position:0% than me it'll probably not last six months<00:40:26.940> but<00:40:27.240> like<00:40:27.480> it<00:40:28.440> there's<00:40:28.859> a<00:40:28.980> lot<00:40:29.160> of<00:40:29.280> just 00:40:29.450 --> 00:40:29.460 align:start position:0% months but like it there's a lot of just 00:40:29.460 --> 00:40:32.150 align:start position:0% months but like it there's a lot of just like<00:40:29.820> implied<00:40:30.420> context<00:40:30.900> that<00:40:31.440> I<00:40:31.980> don't<00:40:32.040> know 00:40:32.150 --> 00:40:32.160 align:start position:0% like implied context that I don't know 00:40:32.160 --> 00:40:33.770 align:start position:0% like implied context that I don't know it's<00:40:32.280> really<00:40:32.460> hard<00:40:32.700> and<00:40:33.119> I<00:40:33.240> felt<00:40:33.480> really<00:40:33.660> good 00:40:33.770 --> 00:40:33.780 align:start position:0% it's really hard and I felt really good 00:40:33.780 --> 00:40:35.750 align:start position:0% it's really hard and I felt really good about<00:40:33.900> myself<00:40:34.200> when<00:40:34.560> Danny<00:40:34.920> Ryan<00:40:35.099> told<00:40:35.460> me<00:40:35.579> the 00:40:35.750 --> 00:40:35.760 align:start position:0% about myself when Danny Ryan told me the 00:40:35.760 --> 00:40:37.550 align:start position:0% about myself when Danny Ryan told me the same<00:40:35.880> thing<00:40:36.060> when<00:40:36.599> he<00:40:36.780> started<00:40:37.140> I<00:40:37.440> think 00:40:37.550 --> 00:40:37.560 align:start position:0% same thing when he started I think 00:40:37.560 --> 00:40:39.230 align:start position:0% same thing when he started I think before<00:40:37.740> he<00:40:37.980> started<00:40:38.280> the<00:40:38.460> EF<00:40:38.700> he<00:40:38.880> would<00:40:39.000> attend 00:40:39.230 --> 00:40:39.240 align:start position:0% before he started the EF he would attend 00:40:39.240 --> 00:40:41.569 align:start position:0% before he started the EF he would attend the<00:40:39.359> Casper<00:40:39.780> CBC<00:40:40.320> calls<00:40:40.740> and<00:40:41.099> he<00:40:41.280> would<00:40:41.400> just 00:40:41.569 --> 00:40:41.579 align:start position:0% the Casper CBC calls and he would just 00:40:41.579 --> 00:40:43.490 align:start position:0% the Casper CBC calls and he would just share<00:40:41.820> links<00:40:42.180> in<00:40:42.359> the<00:40:42.480> zoom<00:40:42.780> chat<00:40:43.020> he<00:40:43.320> was 00:40:43.490 --> 00:40:43.500 align:start position:0% share links in the zoom chat he was 00:40:43.500 --> 00:40:45.050 align:start position:0% share links in the zoom chat he was telling<00:40:43.800> me<00:40:43.859> like<00:40:44.280> you<00:40:44.640> know<00:40:44.700> when<00:40:44.880> somebody 00:40:45.050 --> 00:40:45.060 align:start position:0% telling me like you know when somebody 00:40:45.060 --> 00:40:47.089 align:start position:0% telling me like you know when somebody was<00:40:45.359> like<00:40:45.480> oh<00:40:45.720> like<00:40:46.020> this<00:40:46.260> paper<00:40:46.440> came<00:40:46.740> out<00:40:46.859> he 00:40:47.089 --> 00:40:47.099 align:start position:0% was like oh like this paper came out he 00:40:47.099 --> 00:40:48.589 align:start position:0% was like oh like this paper came out he would<00:40:47.220> just<00:40:47.339> like<00:40:47.400> Google<00:40:47.579> it<00:40:47.820> to<00:40:48.060> be<00:40:48.420> the 00:40:48.589 --> 00:40:48.599 align:start position:0% would just like Google it to be the 00:40:48.599 --> 00:40:50.329 align:start position:0% would just like Google it to be the first<00:40:48.660> guy<00:40:48.839> to<00:40:49.020> share<00:40:49.140> the<00:40:49.260> link<00:40:49.380> in<00:40:49.560> Zoom<00:40:50.099> chat 00:40:50.329 --> 00:40:50.339 align:start position:0% first guy to share the link in Zoom chat 00:40:50.339 --> 00:40:53.750 align:start position:0% first guy to share the link in Zoom chat so<00:40:50.760> like<00:40:51.079> yeah<00:40:52.079> the<00:40:52.320> calls<00:40:52.980> are<00:40:53.040> like 00:40:53.750 --> 00:40:53.760 align:start position:0% so like yeah the calls are like 00:40:53.760 --> 00:40:55.970 align:start position:0% so like yeah the calls are like hard<00:40:54.359> to<00:40:54.540> it's<00:40:54.960> not<00:40:55.140> like<00:40:55.320> a<00:40:55.440> good<00:40:55.560> way<00:40:55.680> to<00:40:55.859> dive 00:40:55.970 --> 00:40:55.980 align:start position:0% hard to it's not like a good way to dive 00:40:55.980 --> 00:40:57.650 align:start position:0% hard to it's not like a good way to dive into<00:40:56.160> it<00:40:56.339> I<00:40:56.520> haven't<00:40:56.640> found<00:40:56.880> somebody 00:40:57.650 --> 00:40:57.660 align:start position:0% into it I haven't found somebody 00:40:57.660 --> 00:40:59.329 align:start position:0% into it I haven't found somebody um<00:40:57.720> so<00:40:57.839> if<00:40:58.020> you're<00:40:58.140> like<00:40:58.380> if<00:40:58.740> it<00:40:58.920> feels<00:40:59.160> weird 00:40:59.329 --> 00:40:59.339 align:start position:0% um so if you're like if it feels weird 00:40:59.339 --> 00:41:01.790 align:start position:0% um so if you're like if it feels weird for<00:40:59.700> a<00:40:59.940> while<00:41:00.060> uh<00:41:00.839> that's<00:41:01.200> that's<00:41:01.260> kind<00:41:01.740> of 00:41:01.790 --> 00:41:01.800 align:start position:0% for a while uh that's that's kind of 00:41:01.800 --> 00:41:03.650 align:start position:0% for a while uh that's that's kind of normal 00:41:03.650 --> 00:41:03.660 align:start position:0% normal 00:41:03.660 --> 00:41:04.430 align:start position:0% normal um 00:41:04.430 --> 00:41:04.440 align:start position:0% um 00:41:04.440 --> 00:41:06.650 align:start position:0% um I<00:41:04.859> have<00:41:05.040> I<00:41:05.520> when<00:41:06.000> people<00:41:06.119> ask<00:41:06.359> me<00:41:06.480> any 00:41:06.650 --> 00:41:06.660 align:start position:0% I have I when people ask me any 00:41:06.660 --> 00:41:08.150 align:start position:0% I have I when people ask me any questions<00:41:06.900> I<00:41:07.260> always<00:41:07.380> throw<00:41:07.619> in<00:41:07.800> these<00:41:08.040> at 00:41:08.150 --> 00:41:08.160 align:start position:0% questions I always throw in these at 00:41:08.160 --> 00:41:10.069 align:start position:0% questions I always throw in these at random<00:41:08.460> ideas<00:41:08.640> I<00:41:09.119> think<00:41:09.240> this<00:41:09.359> is<00:41:09.480> a<00:41:09.599> good<00:41:09.780> idea 00:41:10.069 --> 00:41:10.079 align:start position:0% random ideas I think this is a good idea 00:41:10.079 --> 00:41:13.310 align:start position:0% random ideas I think this is a good idea just<00:41:10.440> be<00:41:10.760> extremely<00:41:11.760> obsessed<00:41:12.480> with<00:41:12.900> like<00:41:13.079> eat 00:41:13.310 --> 00:41:13.320 align:start position:0% just be extremely obsessed with like eat 00:41:13.320 --> 00:41:16.190 align:start position:0% just be extremely obsessed with like eat Research<00:41:13.920> Forum<00:41:14.400> and<00:41:15.000> to<00:41:15.119> a<00:41:15.300> point<00:41:15.480> where<00:41:15.839> that 00:41:16.190 --> 00:41:16.200 align:start position:0% Research Forum and to a point where that 00:41:16.200 --> 00:41:17.930 align:start position:0% Research Forum and to a point where that you<00:41:16.380> read<00:41:16.560> The<00:41:16.740> Forum<00:41:17.040> one<00:41:17.220> two<00:41:17.520> three<00:41:17.760> times 00:41:17.930 --> 00:41:17.940 align:start position:0% you read The Forum one two three times 00:41:17.940 --> 00:41:20.270 align:start position:0% you read The Forum one two three times and<00:41:18.359> then<00:41:18.480> take<00:41:18.720> notes<00:41:19.140> to<00:41:19.380> like<00:41:19.859> like 00:41:20.270 --> 00:41:20.280 align:start position:0% and then take notes to like like 00:41:20.280 --> 00:41:22.069 align:start position:0% and then take notes to like like basically<00:41:20.700> where<00:41:21.119> the<00:41:21.420> notes<00:41:21.660> that<00:41:21.839> you<00:41:21.960> can 00:41:22.069 --> 00:41:22.079 align:start position:0% basically where the notes that you can 00:41:22.079 --> 00:41:23.990 align:start position:0% basically where the notes that you can understand<00:41:22.260> then<00:41:22.980> you<00:41:23.160> can<00:41:23.280> transfer<00:41:23.640> notes 00:41:23.990 --> 00:41:24.000 align:start position:0% understand then you can transfer notes 00:41:24.000 --> 00:41:25.670 align:start position:0% understand then you can transfer notes into<00:41:24.180> blog<00:41:24.599> posts<00:41:24.900> and<00:41:25.200> then<00:41:25.320> you<00:41:25.440> can<00:41:25.500> share 00:41:25.670 --> 00:41:25.680 align:start position:0% into blog posts and then you can share 00:41:25.680 --> 00:41:27.950 align:start position:0% into blog posts and then you can share the<00:41:25.800> blog<00:41:26.040> post<00:41:26.160> to<00:41:26.400> people<00:41:26.520> and<00:41:27.300> then<00:41:27.420> but<00:41:27.720> but 00:41:27.950 --> 00:41:27.960 align:start position:0% the blog post to people and then but but 00:41:27.960 --> 00:41:30.829 align:start position:0% the blog post to people and then but but when<00:41:28.260> you're<00:41:28.440> able<00:41:28.680> to<00:41:28.800> do<00:41:28.980> that<00:41:29.160> you<00:41:29.579> you<00:41:30.300> like 00:41:30.829 --> 00:41:30.839 align:start position:0% when you're able to do that you you like 00:41:30.839 --> 00:41:32.930 align:start position:0% when you're able to do that you you like you<00:41:31.079> can<00:41:31.200> actually<00:41:31.380> be<00:41:31.680> fairly<00:41:32.160> you<00:41:32.760> can't 00:41:32.930 --> 00:41:32.940 align:start position:0% you can actually be fairly you can't 00:41:32.940 --> 00:41:34.609 align:start position:0% you can actually be fairly you can't actually<00:41:33.180> be<00:41:33.480> very<00:41:33.720> knowledgeable<00:41:34.200> at<00:41:34.500> that 00:41:34.609 --> 00:41:34.619 align:start position:0% actually be very knowledgeable at that 00:41:34.619 --> 00:41:37.370 align:start position:0% actually be very knowledgeable at that topic<00:41:34.980> already<00:41:35.220> which<00:41:36.060> yeah<00:41:36.720> and<00:41:36.960> then<00:41:37.140> other 00:41:37.370 --> 00:41:37.380 align:start position:0% topic already which yeah and then other 00:41:37.380 --> 00:41:38.870 align:start position:0% topic already which yeah and then other things<00:41:37.560> like<00:41:37.859> just<00:41:38.040> just<00:41:38.160> podcasts<00:41:38.760> in 00:41:38.870 --> 00:41:38.880 align:start position:0% things like just just podcasts in 00:41:38.880 --> 00:41:40.970 align:start position:0% things like just just podcasts in general<00:41:39.060> like<00:41:39.480> just<00:41:40.079> like<00:41:40.260> pay<00:41:40.440> attention<00:41:40.740> to 00:41:40.970 --> 00:41:40.980 align:start position:0% general like just like pay attention to 00:41:40.980 --> 00:41:43.370 align:start position:0% general like just like pay attention to like<00:41:41.099> quartet<00:41:41.640> podcast<00:41:41.880> and<00:41:42.660> then<00:41:42.780> take<00:41:43.020> notes 00:41:43.370 --> 00:41:43.380 align:start position:0% like quartet podcast and then take notes 00:41:43.380 --> 00:41:45.589 align:start position:0% like quartet podcast and then take notes on<00:41:43.500> that<00:41:43.740> and<00:41:44.220> then<00:41:44.460> also<00:41:44.880> share<00:41:45.180> your<00:41:45.300> notes 00:41:45.589 --> 00:41:45.599 align:start position:0% on that and then also share your notes 00:41:45.599 --> 00:41:47.450 align:start position:0% on that and then also share your notes because<00:41:45.720> people<00:41:46.079> will<00:41:46.680> actually<00:41:46.800> appreciate 00:41:47.450 --> 00:41:47.460 align:start position:0% because people will actually appreciate 00:41:47.460 --> 00:41:50.030 align:start position:0% because people will actually appreciate that<00:41:47.700> because<00:41:48.180> not<00:41:48.720> because<00:41:49.200> not<00:41:49.680> a<00:41:49.800> lot<00:41:49.980> of 00:41:50.030 --> 00:41:50.040 align:start position:0% that because not because not a lot of 00:41:50.040 --> 00:41:51.470 align:start position:0% that because not because not a lot of people<00:41:50.160> have<00:41:50.400> come<00:41:50.640> to<00:41:50.880> watch<00:41:50.940> like<00:41:51.240> YouTube 00:41:51.470 --> 00:41:51.480 align:start position:0% people have come to watch like YouTube 00:41:51.480 --> 00:41:53.210 align:start position:0% people have come to watch like YouTube videos<00:41:51.839> and<00:41:52.200> listen<00:41:52.320> to<00:41:52.560> podcasts<00:41:52.980> and<00:41:53.099> stuff 00:41:53.210 --> 00:41:53.220 align:start position:0% videos and listen to podcasts and stuff 00:41:53.220 --> 00:41:56.210 align:start position:0% videos and listen to podcasts and stuff people<00:41:53.820> will<00:41:54.359> prefer<00:41:54.780> to<00:41:54.900> read<00:41:55.020> notes 00:41:56.210 --> 00:41:56.220 align:start position:0% people will prefer to read notes 00:41:56.220 --> 00:41:58.970 align:start position:0% people will prefer to read notes and<00:41:57.000> just<00:41:57.420> make<00:41:57.720> sure<00:41:57.839> to<00:41:58.079> share<00:41:58.380> everything 00:41:58.970 --> 00:41:58.980 align:start position:0% and just make sure to share everything 00:41:58.980 --> 00:42:02.390 align:start position:0% and just make sure to share everything on<00:41:59.280> Twitter<00:41:59.520> that's<00:42:00.300> where<00:42:00.980> that's<00:42:01.980> where<00:42:02.220> the 00:42:02.390 --> 00:42:02.400 align:start position:0% on Twitter that's where that's where the 00:42:02.400 --> 00:42:04.730 align:start position:0% on Twitter that's where that's where the hype<00:42:02.820> is<00:42:02.940> and<00:42:03.240> that's<00:42:03.420> like<00:42:03.660> how<00:42:04.020> you<00:42:04.200> can<00:42:04.320> get 00:42:04.730 --> 00:42:04.740 align:start position:0% hype is and that's like how you can get 00:42:04.740 --> 00:42:07.370 align:start position:0% hype is and that's like how you can get involved<00:42:05.220> and<00:42:05.760> go<00:42:05.940> to<00:42:06.060> events<00:42:06.599> and<00:42:06.960> just<00:42:07.140> like 00:42:07.370 --> 00:42:07.380 align:start position:0% involved and go to events and just like 00:42:07.380 --> 00:42:09.589 align:start position:0% involved and go to events and just like speak<00:42:07.619> up<00:42:07.859> or<00:42:08.220> even<00:42:08.280> take<00:42:08.579> notes<00:42:08.940> and<00:42:09.119> then 00:42:09.589 --> 00:42:09.599 align:start position:0% speak up or even take notes and then 00:42:09.599 --> 00:42:11.390 align:start position:0% speak up or even take notes and then like<00:42:09.839> even<00:42:10.020> DM<00:42:10.380> to<00:42:10.500> people<00:42:10.740> that's<00:42:10.980> like<00:42:11.220> how 00:42:11.390 --> 00:42:11.400 align:start position:0% like even DM to people that's like how 00:42:11.400 --> 00:42:13.970 align:start position:0% like even DM to people that's like how you<00:42:11.640> can<00:42:11.880> basically<00:42:12.420> get<00:42:12.720> started<00:42:13.140> also<00:42:13.800> great 00:42:13.970 --> 00:42:13.980 align:start position:0% you can basically get started also great 00:42:13.980 --> 00:42:16.490 align:start position:0% you can basically get started also great way<00:42:14.220> how<00:42:14.520> to<00:42:14.640> get<00:42:14.880> even<00:42:15.359> closer<00:42:15.960> to<00:42:16.140> the<00:42:16.320> people 00:42:16.490 --> 00:42:16.500 align:start position:0% way how to get even closer to the people 00:42:16.500 --> 00:42:18.710 align:start position:0% way how to get even closer to the people in<00:42:16.740> the<00:42:16.859> ethereum<00:42:17.280> it's<00:42:17.820> just<00:42:18.000> volunteer<00:42:18.420> on<00:42:18.599> a 00:42:18.710 --> 00:42:18.720 align:start position:0% in the ethereum it's just volunteer on a 00:42:18.720 --> 00:42:20.990 align:start position:0% in the ethereum it's just volunteer on a conference<00:42:19.079> that's<00:42:19.500> basically<00:42:19.920> how<00:42:20.760> many 00:42:20.990 --> 00:42:21.000 align:start position:0% conference that's basically how many 00:42:21.000 --> 00:42:23.030 align:start position:0% conference that's basically how many people<00:42:21.240> in<00:42:21.720> the<00:42:21.839> ecosystem<00:42:22.200> including<00:42:22.859> me 00:42:23.030 --> 00:42:23.040 align:start position:0% people in the ecosystem including me 00:42:23.040 --> 00:42:25.130 align:start position:0% people in the ecosystem including me started<00:42:23.520> and<00:42:23.880> I<00:42:24.000> feel<00:42:24.119> like<00:42:24.300> that's<00:42:24.660> the<00:42:25.020> way 00:42:25.130 --> 00:42:25.140 align:start position:0% started and I feel like that's the way 00:42:25.140 --> 00:42:27.290 align:start position:0% started and I feel like that's the way how<00:42:25.440> you<00:42:25.619> can<00:42:25.740> get<00:42:25.920> even<00:42:26.099> closer<00:42:26.700> and<00:42:27.180> whether 00:42:27.290 --> 00:42:27.300 align:start position:0% how you can get even closer and whether 00:42:27.300 --> 00:42:28.490 align:start position:0% how you can get even closer and whether that's<00:42:27.599> like<00:42:27.839> volunteering<00:42:28.260> on<00:42:28.380> the 00:42:28.490 --> 00:42:28.500 align:start position:0% that's like volunteering on the 00:42:28.500 --> 00:42:30.290 align:start position:0% that's like volunteering on the conference<00:42:28.859> itself<00:42:29.160> or<00:42:29.760> you<00:42:29.880> can<00:42:30.000> just<00:42:30.119> even 00:42:30.290 --> 00:42:30.300 align:start position:0% conference itself or you can just even 00:42:30.300 --> 00:42:32.030 align:start position:0% conference itself or you can just even volunteer<00:42:30.900> on<00:42:31.020> a<00:42:31.200> calls<00:42:31.440> and<00:42:31.619> you<00:42:31.740> can<00:42:31.859> like 00:42:32.030 --> 00:42:32.040 align:start position:0% volunteer on a calls and you can like 00:42:32.040 --> 00:42:34.730 align:start position:0% volunteer on a calls and you can like find<00:42:32.640> like<00:42:32.940> a<00:42:33.240> client<00:42:33.660> calls<00:42:34.260> and<00:42:34.380> then<00:42:34.560> just 00:42:34.730 --> 00:42:34.740 align:start position:0% find like a client calls and then just 00:42:34.740 --> 00:42:36.650 align:start position:0% find like a client calls and then just like<00:42:34.859> hey<00:42:35.099> like<00:42:35.339> I<00:42:35.640> want<00:42:35.760> to<00:42:35.880> take<00:42:36.000> a<00:42:36.180> note<00:42:36.359> or 00:42:36.650 --> 00:42:36.660 align:start position:0% like hey like I want to take a note or 00:42:36.660 --> 00:42:38.990 align:start position:0% like hey like I want to take a note or like<00:42:36.900> this<00:42:37.500> is<00:42:37.619> my<00:42:37.859> skill<00:42:38.099> set<00:42:38.280> and<00:42:38.460> like<00:42:38.700> this 00:42:38.990 --> 00:42:39.000 align:start position:0% like this is my skill set and like this 00:42:39.000 --> 00:42:40.790 align:start position:0% like this is my skill set and like this is<00:42:39.119> how<00:42:39.359> I<00:42:39.540> want<00:42:39.780> to<00:42:39.960> help<00:42:40.079> you<00:42:40.260> or<00:42:40.380> like<00:42:40.619> I 00:42:40.790 --> 00:42:40.800 align:start position:0% is how I want to help you or like I 00:42:40.800 --> 00:42:43.370 align:start position:0% is how I want to help you or like I found<00:42:40.980> a<00:42:41.160> Bunty<00:42:41.640> uh<00:42:42.240> like<00:42:42.480> I<00:42:42.660> found<00:42:42.780> a<00:42:42.960> bug<00:42:43.140> in 00:42:43.370 --> 00:42:43.380 align:start position:0% found a Bunty uh like I found a bug in 00:42:43.380 --> 00:42:45.230 align:start position:0% found a Bunty uh like I found a bug in your<00:42:43.560> code<00:42:43.859> or<00:42:44.160> something<00:42:44.400> or<00:42:44.760> just<00:42:44.940> like<00:42:45.060> get 00:42:45.230 --> 00:42:45.240 align:start position:0% your code or something or just like get 00:42:45.240 --> 00:42:49.730 align:start position:0% your code or something or just like get involved<00:42:45.660> with<00:42:45.780> the<00:42:45.960> GitHub<00:42:46.260> repos 00:42:49.730 --> 00:42:49.740 align:start position:0% 00:42:49.740 --> 00:42:53.569 align:start position:0% yeah<00:42:50.339> I'd<00:42:50.880> 100<00:42:51.180> agree<00:42:52.020> hi<00:42:52.380> I'm<00:42:52.619> Christine<00:42:53.520> um 00:42:53.569 --> 00:42:53.579 align:start position:0% yeah I'd 100 agree hi I'm Christine um 00:42:53.579 --> 00:42:55.550 align:start position:0% yeah I'd 100 agree hi I'm Christine um I'm<00:42:53.760> a<00:42:53.880> researcher<00:42:54.240> at<00:42:54.420> Galaxy<00:42:54.599> but<00:42:55.140> on<00:42:55.440> the 00:42:55.550 --> 00:42:55.560 align:start position:0% I'm a researcher at Galaxy but on the 00:42:55.560 --> 00:42:57.950 align:start position:0% I'm a researcher at Galaxy but on the topic<00:42:55.740> of<00:42:55.859> Youth<00:42:56.160> core<00:42:56.280> Dev<00:42:56.520> calls<00:42:57.000> I<00:42:57.660> too 00:42:57.950 --> 00:42:57.960 align:start position:0% topic of Youth core Dev calls I too 00:42:57.960 --> 00:42:59.569 align:start position:0% topic of Youth core Dev calls I too definitely<00:42:58.440> did<00:42:58.740> not<00:42:58.920> understand<00:42:59.099> anything 00:42:59.569 --> 00:42:59.579 align:start position:0% definitely did not understand anything 00:42:59.579 --> 00:43:01.910 align:start position:0% definitely did not understand anything for<00:43:00.119> like<00:43:00.300> the<00:43:00.480> first<00:43:00.599> couple<00:43:00.900> years<00:43:01.260> of<00:43:01.680> my 00:43:01.910 --> 00:43:01.920 align:start position:0% for like the first couple years of my 00:43:01.920 --> 00:43:04.069 align:start position:0% for like the first couple years of my time<00:43:02.280> covering<00:43:03.000> these<00:43:03.240> calls<00:43:03.480> but<00:43:03.599> it<00:43:03.780> takes<00:43:03.900> a 00:43:04.069 --> 00:43:04.079 align:start position:0% time covering these calls but it takes a 00:43:04.079 --> 00:43:05.089 align:start position:0% time covering these calls but it takes a while 00:43:05.089 --> 00:43:05.099 align:start position:0% while 00:43:05.099 --> 00:43:06.890 align:start position:0% while um<00:43:05.220> I<00:43:05.400> think<00:43:05.579> one<00:43:05.880> thing<00:43:06.060> that<00:43:06.480> I<00:43:06.599> thought<00:43:06.720> was 00:43:06.890 --> 00:43:06.900 align:start position:0% um I think one thing that I thought was 00:43:06.900 --> 00:43:09.050 align:start position:0% um I think one thing that I thought was really<00:43:07.200> interesting<00:43:07.680> about<00:43:08.220> covering<00:43:08.819> the 00:43:09.050 --> 00:43:09.060 align:start position:0% really interesting about covering the 00:43:09.060 --> 00:43:11.329 align:start position:0% really interesting about covering the merge<00:43:09.420> and<00:43:09.720> being<00:43:09.960> on<00:43:10.319> these<00:43:10.560> like<00:43:10.920> watching 00:43:11.329 --> 00:43:11.339 align:start position:0% merge and being on these like watching 00:43:11.339 --> 00:43:13.849 align:start position:0% merge and being on these like watching through<00:43:11.520> live<00:43:11.760> stream<00:43:12.000> over<00:43:12.480> the<00:43:12.900> years<00:43:13.560> that 00:43:13.849 --> 00:43:13.859 align:start position:0% through live stream over the years that 00:43:13.859 --> 00:43:15.410 align:start position:0% through live stream over the years that it<00:43:13.920> took<00:43:14.160> to<00:43:14.339> kind<00:43:14.520> of<00:43:14.579> like<00:43:14.700> get<00:43:14.940> the<00:43:15.119> merge 00:43:15.410 --> 00:43:15.420 align:start position:0% it took to kind of like get the merge 00:43:15.420 --> 00:43:18.349 align:start position:0% it took to kind of like get the merge going<00:43:15.660> is<00:43:16.560> how<00:43:16.859> over<00:43:17.160> time 00:43:18.349 --> 00:43:18.359 align:start position:0% going is how over time 00:43:18.359 --> 00:43:20.870 align:start position:0% going is how over time like<00:43:18.900> the<00:43:19.200> process<00:43:19.560> for<00:43:20.040> figuring<00:43:20.460> out<00:43:20.640> what 00:43:20.870 --> 00:43:20.880 align:start position:0% like the process for figuring out what 00:43:20.880 --> 00:43:22.730 align:start position:0% like the process for figuring out what goes<00:43:21.180> into<00:43:21.240> the<00:43:21.540> merge<00:43:21.839> and<00:43:22.079> who<00:43:22.319> gets<00:43:22.619> to 00:43:22.730 --> 00:43:22.740 align:start position:0% goes into the merge and who gets to 00:43:22.740 --> 00:43:25.370 align:start position:0% goes into the merge and who gets to build<00:43:23.040> clients<00:43:23.579> for<00:43:23.819> the<00:43:24.060> merge<00:43:24.380> increasingly 00:43:25.370 --> 00:43:25.380 align:start position:0% build clients for the merge increasingly 00:43:25.380 --> 00:43:28.430 align:start position:0% build clients for the merge increasingly become<00:43:25.980> like<00:43:26.339> a<00:43:26.880> smaller<00:43:27.300> and<00:43:27.660> smaller<00:43:28.079> and 00:43:28.430 --> 00:43:28.440 align:start position:0% become like a smaller and smaller and 00:43:28.440 --> 00:43:30.349 align:start position:0% become like a smaller and smaller and smaller<00:43:28.920> team 00:43:30.349 --> 00:43:30.359 align:start position:0% smaller team 00:43:30.359 --> 00:43:31.550 align:start position:0% smaller team um so<00:43:30.540> like<00:43:30.660> in<00:43:30.839> the<00:43:30.960> beginning<00:43:31.020> there<00:43:31.380> was 00:43:31.550 --> 00:43:31.560 align:start position:0% um so like in the beginning there was 00:43:31.560 --> 00:43:33.650 align:start position:0% um so like in the beginning there was like<00:43:31.800> probably<00:43:32.339> there<00:43:32.940> was<00:43:33.060> like<00:43:33.300> there's 00:43:33.650 --> 00:43:33.660 align:start position:0% like probably there was like there's 00:43:33.660 --> 00:43:35.930 align:start position:0% like probably there was like there's this<00:43:33.960> article<00:43:34.319> on<00:43:34.500> coindesk<00:43:35.099> talking<00:43:35.760> about 00:43:35.930 --> 00:43:35.940 align:start position:0% this article on coindesk talking about 00:43:35.940 --> 00:43:37.790 align:start position:0% this article on coindesk talking about like<00:43:36.180> how<00:43:36.359> there's<00:43:36.660> like<00:43:36.900> eight<00:43:37.200> or<00:43:37.500> nine 00:43:37.790 --> 00:43:37.800 align:start position:0% like how there's like eight or nine 00:43:37.800 --> 00:43:39.530 align:start position:0% like how there's like eight or nine different<00:43:38.040> client<00:43:38.460> teams<00:43:38.819> like<00:43:39.060> trying<00:43:39.300> to 00:43:39.530 --> 00:43:39.540 align:start position:0% different client teams like trying to 00:43:39.540 --> 00:43:41.690 align:start position:0% different client teams like trying to build<00:43:39.780> for<00:43:40.380> the<00:43:40.680> merge<00:43:40.980> but<00:43:41.220> a<00:43:41.400> lot<00:43:41.460> of<00:43:41.579> them 00:43:41.690 --> 00:43:41.700 align:start position:0% build for the merge but a lot of them 00:43:41.700 --> 00:43:44.270 align:start position:0% build for the merge but a lot of them dropped<00:43:42.119> off<00:43:42.240> once<00:43:42.780> like<00:43:43.020> I<00:43:43.859> think<00:43:43.980> there<00:43:44.160> was 00:43:44.270 --> 00:43:44.280 align:start position:0% dropped off once like I think there was 00:43:44.280 --> 00:43:46.670 align:start position:0% dropped off once like I think there was a<00:43:44.400> point<00:43:44.579> in<00:43:44.819> which<00:43:45.000> like<00:43:45.359> the<00:43:45.599> the<00:43:45.780> repo<00:43:46.319> for 00:43:46.670 --> 00:43:46.680 align:start position:0% a point in which like the the repo for 00:43:46.680 --> 00:43:49.130 align:start position:0% a point in which like the the repo for how<00:43:47.579> ethereum's<00:43:48.240> consensus<00:43:48.720> was<00:43:48.960> going<00:43:49.140> to 00:43:49.130 --> 00:43:49.140 align:start position:0% how ethereum's consensus was going to 00:43:49.140 --> 00:43:50.690 align:start position:0% how ethereum's consensus was going to happen<00:43:49.319> got<00:43:49.560> like<00:43:49.740> to<00:43:49.920> totally<00:43:50.160> overturned 00:43:50.690 --> 00:43:50.700 align:start position:0% happen got like to totally overturned 00:43:50.700 --> 00:43:52.190 align:start position:0% happen got like to totally overturned and<00:43:50.819> that<00:43:50.940> made<00:43:51.060> a<00:43:51.240> lot<00:43:51.300> of<00:43:51.359> playing<00:43:51.599> teams<00:43:52.020> mad 00:43:52.190 --> 00:43:52.200 align:start position:0% and that made a lot of playing teams mad 00:43:52.200 --> 00:43:53.930 align:start position:0% and that made a lot of playing teams mad and<00:43:52.440> so<00:43:52.560> then<00:43:52.740> it<00:43:52.920> like<00:43:53.099> shranked<00:43:53.640> down<00:43:53.760> to 00:43:53.930 --> 00:43:53.940 align:start position:0% and so then it like shranked down to 00:43:53.940 --> 00:43:56.630 align:start position:0% and so then it like shranked down to four<00:43:54.180> and<00:43:54.780> I<00:43:54.900> think<00:43:54.960> the<00:43:55.200> closer<00:43:55.680> like<00:43:56.460> the 00:43:56.630 --> 00:43:56.640 align:start position:0% four and I think the closer like the 00:43:56.640 --> 00:44:00.050 align:start position:0% four and I think the closer like the client<00:43:56.819> teams<00:43:57.180> got<00:43:57.420> to<00:43:57.720> to<00:43:58.440> the<00:43:58.980> merge 00:44:00.050 --> 00:44:00.060 align:start position:0% client teams got to to the merge 00:44:00.060 --> 00:44:04.849 align:start position:0% client teams got to to the merge it<00:44:00.599> was<00:44:00.839> very<00:44:01.140> it<00:44:01.859> was<00:44:02.040> very<00:44:02.400> clear<00:44:02.819> that<00:44:03.240> like 00:44:04.849 --> 00:44:04.859 align:start position:0% it was very it was very clear that like 00:44:04.859 --> 00:44:07.730 align:start position:0% it was very it was very clear that like there<00:44:05.400> there<00:44:05.400> wasn't<00:44:05.880> like<00:44:06.300> really<00:44:07.200> much<00:44:07.500> more 00:44:07.730 --> 00:44:07.740 align:start position:0% there there wasn't like really much more 00:44:07.740 --> 00:44:09.950 align:start position:0% there there wasn't like really much more discussion<00:44:08.220> to<00:44:08.460> be<00:44:08.579> had<00:44:08.880> from<00:44:09.359> like<00:44:09.660> just 00:44:09.950 --> 00:44:09.960 align:start position:0% discussion to be had from like just 00:44:09.960 --> 00:44:13.430 align:start position:0% discussion to be had from like just anybody<00:44:10.380> so<00:44:11.160> like<00:44:11.480> when<00:44:12.480> the<00:44:12.839> Discord<00:44:13.079> channel 00:44:13.430 --> 00:44:13.440 align:start position:0% anybody so like when the Discord channel 00:44:13.440 --> 00:44:15.410 align:start position:0% anybody so like when the Discord channel was<00:44:13.920> like<00:44:14.160> privatized<00:44:14.880> like<00:44:15.060> basically<00:44:15.300> like 00:44:15.410 --> 00:44:15.420 align:start position:0% was like privatized like basically like 00:44:15.420 --> 00:44:17.390 align:start position:0% was like privatized like basically like no<00:44:15.660> one<00:44:15.839> talked<00:44:16.560> because<00:44:16.740> we<00:44:16.980> really<00:44:17.099> have<00:44:17.280> to 00:44:17.390 --> 00:44:17.400 align:start position:0% no one talked because we really have to 00:44:17.400 --> 00:44:20.089 align:start position:0% no one talked because we really have to focus<00:44:17.579> on<00:44:17.760> the<00:44:17.880> merge<00:44:18.180> right<00:44:18.359> now<00:44:18.540> and<00:44:19.440> when 00:44:20.089 --> 00:44:20.099 align:start position:0% focus on the merge right now and when 00:44:20.099 --> 00:44:21.530 align:start position:0% focus on the merge right now and when they<00:44:20.280> started<00:44:20.579> to<00:44:20.700> become<00:44:20.880> like<00:44:21.000> differences 00:44:21.530 --> 00:44:21.540 align:start position:0% they started to become like differences 00:44:21.540 --> 00:44:23.990 align:start position:0% they started to become like differences of<00:44:21.900> like<00:44:22.140> client<00:44:22.560> teams<00:44:22.980> Readiness<00:44:23.520> for<00:44:23.819> the 00:44:23.990 --> 00:44:24.000 align:start position:0% of like client teams Readiness for the 00:44:24.000 --> 00:44:26.510 align:start position:0% of like client teams Readiness for the merge<00:44:24.359> so<00:44:24.960> like<00:44:25.140> some<00:44:25.319> Clan<00:44:25.619> teams<00:44:25.980> were<00:44:26.280> more 00:44:26.510 --> 00:44:26.520 align:start position:0% merge so like some Clan teams were more 00:44:26.520 --> 00:44:28.250 align:start position:0% merge so like some Clan teams were more ready<00:44:26.700> than<00:44:27.000> others<00:44:27.300> had<00:44:27.599> more<00:44:27.900> features 00:44:28.250 --> 00:44:28.260 align:start position:0% ready than others had more features 00:44:28.260 --> 00:44:30.530 align:start position:0% ready than others had more features ready<00:44:28.500> than<00:44:28.740> others<00:44:29.099> I<00:44:29.760> think<00:44:29.880> they're<00:44:30.180> the 00:44:30.530 --> 00:44:30.540 align:start position:0% ready than others I think they're the 00:44:30.540 --> 00:44:32.569 align:start position:0% ready than others I think they're the differences<00:44:31.020> between<00:44:31.380> like<00:44:31.680> preparation<00:44:32.220> and 00:44:32.569 --> 00:44:32.579 align:start position:0% differences between like preparation and 00:44:32.579 --> 00:44:34.790 align:start position:0% differences between like preparation and resources<00:44:33.000> for<00:44:33.300> each<00:44:33.480> client<00:44:33.780> teams<00:44:34.200> got<00:44:34.560> a 00:44:34.790 --> 00:44:34.800 align:start position:0% resources for each client teams got a 00:44:34.800 --> 00:44:37.010 align:start position:0% resources for each client teams got a lot<00:44:34.980> clearer<00:44:35.579> like<00:44:36.119> the<00:44:36.240> closer<00:44:36.599> it<00:44:36.720> came<00:44:36.900> to 00:44:37.010 --> 00:44:37.020 align:start position:0% lot clearer like the closer it came to 00:44:37.020 --> 00:44:38.270 align:start position:0% lot clearer like the closer it came to the<00:44:37.200> merge 00:44:38.270 --> 00:44:38.280 align:start position:0% the merge 00:44:38.280 --> 00:44:39.770 align:start position:0% the merge um<00:44:38.339> so<00:44:38.520> I<00:44:38.640> think<00:44:38.700> like<00:44:38.880> moving<00:44:39.240> forward<00:44:39.480> and 00:44:39.770 --> 00:44:39.780 align:start position:0% um so I think like moving forward and 00:44:39.780 --> 00:44:41.030 align:start position:0% um so I think like moving forward and looking<00:44:39.960> ahead<00:44:40.319> to<00:44:40.500> some<00:44:40.619> of<00:44:40.800> the<00:44:40.859> other 00:44:41.030 --> 00:44:41.040 align:start position:0% looking ahead to some of the other 00:44:41.040 --> 00:44:43.010 align:start position:0% looking ahead to some of the other bigger<00:44:41.460> upgrades 00:44:43.010 --> 00:44:43.020 align:start position:0% bigger upgrades 00:44:43.020 --> 00:44:45.109 align:start position:0% bigger upgrades um<00:44:43.079> I<00:44:43.680> guess<00:44:43.800> like<00:44:44.040> I<00:44:44.339> wanted<00:44:44.460> to<00:44:44.760> know<00:44:44.880> your 00:44:45.109 --> 00:44:45.119 align:start position:0% um I guess like I wanted to know your 00:44:45.119 --> 00:44:46.809 align:start position:0% um I guess like I wanted to know your guys's<00:44:45.480> thoughts<00:44:45.839> on 00:44:46.809 --> 00:44:46.819 align:start position:0% guys's thoughts on 00:44:46.819 --> 00:44:49.010 align:start position:0% guys's thoughts on how<00:44:47.819> to<00:44:48.180> like 00:44:49.010 --> 00:44:49.020 align:start position:0% how to like 00:44:49.020 --> 00:44:50.809 align:start position:0% how to like on<00:44:49.440> basically<00:44:49.740> what<00:44:50.040> the<00:44:50.220> new<00:44:50.339> process<00:44:50.640> is 00:44:50.809 --> 00:44:50.819 align:start position:0% on basically what the new process is 00:44:50.819 --> 00:44:52.670 align:start position:0% on basically what the new process is going<00:44:51.060> to<00:44:51.180> be<00:44:51.240> for<00:44:51.420> eips<00:44:51.780> and<00:44:52.200> stuff<00:44:52.380> because 00:44:52.670 --> 00:44:52.680 align:start position:0% going to be for eips and stuff because 00:44:52.680 --> 00:44:54.770 align:start position:0% going to be for eips and stuff because like<00:44:52.980> for<00:44:53.220> the<00:44:53.400> eth<00:44:53.640> core<00:44:53.760> Dev<00:44:53.940> calls<00:44:54.420> for<00:44:54.599> the 00:44:54.770 --> 00:44:54.780 align:start position:0% like for the eth core Dev calls for the 00:44:54.780 --> 00:44:56.150 align:start position:0% like for the eth core Dev calls for the last<00:44:54.900> couple<00:44:55.079> months<00:44:55.380> it's<00:44:55.560> been<00:44:55.740> clear<00:44:55.920> that 00:44:56.150 --> 00:44:56.160 align:start position:0% last couple months it's been clear that 00:44:56.160 --> 00:44:59.150 align:start position:0% last couple months it's been clear that it's<00:44:56.339> just<00:44:56.579> the<00:44:56.760> merge<00:44:57.180> but<00:44:57.900> now<00:44:58.200> like<00:44:58.619> there's 00:44:59.150 --> 00:44:59.160 align:start position:0% it's just the merge but now like there's 00:44:59.160 --> 00:45:00.770 align:start position:0% it's just the merge but now like there's going<00:44:59.339> to<00:44:59.400> be<00:44:59.520> so<00:44:59.760> much<00:44:59.940> to<00:45:00.180> discuss<00:45:00.420> so<00:45:00.660> much 00:45:00.770 --> 00:45:00.780 align:start position:0% going to be so much to discuss so much 00:45:00.780 --> 00:45:02.870 align:start position:0% going to be so much to discuss so much about<00:45:00.900> ethereum's<00:45:01.440> roadmap 00:45:02.870 --> 00:45:02.880 align:start position:0% about ethereum's roadmap 00:45:02.880 --> 00:45:03.530 align:start position:0% about ethereum's roadmap um 00:45:03.530 --> 00:45:03.540 align:start position:0% um 00:45:03.540 --> 00:45:05.690 align:start position:0% um so<00:45:04.020> I<00:45:04.319> thought<00:45:04.440> that<00:45:04.619> it<00:45:04.800> was<00:45:04.980> like<00:45:05.220> really 00:45:05.690 --> 00:45:05.700 align:start position:0% so I thought that it was like really 00:45:05.700 --> 00:45:08.450 align:start position:0% so I thought that it was like really like<00:45:06.180> part<00:45:06.599> of<00:45:06.900> the<00:45:07.200> the<00:45:07.440> whole<00:45:07.920> topic<00:45:08.280> around 00:45:08.450 --> 00:45:08.460 align:start position:0% like part of the the whole topic around 00:45:08.460 --> 00:45:10.370 align:start position:0% like part of the the whole topic around like<00:45:08.700> ossification<00:45:09.359> like<00:45:09.839> the<00:45:10.200> more 00:45:10.370 --> 00:45:10.380 align:start position:0% like ossification like the more 00:45:10.380 --> 00:45:12.530 align:start position:0% like ossification like the more decentralized<00:45:11.099> this<00:45:11.339> process<00:45:11.640> is<00:45:11.940> the<00:45:12.240> harder 00:45:12.530 --> 00:45:12.540 align:start position:0% decentralized this process is the harder 00:45:12.540 --> 00:45:14.870 align:start position:0% decentralized this process is the harder it<00:45:12.599> is<00:45:12.780> to<00:45:12.960> make<00:45:13.079> changes 00:45:14.870 --> 00:45:14.880 align:start position:0% it is to make changes 00:45:14.880 --> 00:45:17.150 align:start position:0% it is to make changes um but<00:45:15.660> clearly<00:45:16.140> there's<00:45:16.440> like<00:45:16.680> some<00:45:16.859> amount 00:45:17.150 --> 00:45:17.160 align:start position:0% um but clearly there's like some amount 00:45:17.160 --> 00:45:18.950 align:start position:0% um but clearly there's like some amount of<00:45:17.280> centralization<00:45:17.819> that's<00:45:18.240> needed<00:45:18.599> and<00:45:18.780> that 00:45:18.950 --> 00:45:18.960 align:start position:0% of centralization that's needed and that 00:45:18.960 --> 00:45:20.450 align:start position:0% of centralization that's needed and that we've<00:45:19.140> already<00:45:19.319> seen<00:45:19.619> to<00:45:19.859> make<00:45:19.980> the<00:45:20.160> merge 00:45:20.450 --> 00:45:20.460 align:start position:0% we've already seen to make the merge 00:45:20.460 --> 00:45:22.069 align:start position:0% we've already seen to make the merge possible<00:45:20.880> and<00:45:21.180> so<00:45:21.359> now<00:45:21.480> there's<00:45:21.660> Shanghai 00:45:22.069 --> 00:45:22.079 align:start position:0% possible and so now there's Shanghai 00:45:22.079 --> 00:45:24.290 align:start position:0% possible and so now there's Shanghai coming<00:45:22.380> up<00:45:22.619> so<00:45:23.160> like<00:45:23.339> will<00:45:23.520> it<00:45:23.640> still<00:45:23.819> be<00:45:24.000> like 00:45:24.290 --> 00:45:24.300 align:start position:0% coming up so like will it still be like 00:45:24.300 --> 00:45:26.510 align:start position:0% coming up so like will it still be like consensus<00:45:25.079> layer<00:45:25.380> execution<00:45:25.740> layer<00:45:26.160> like 00:45:26.510 --> 00:45:26.520 align:start position:0% consensus layer execution layer like 00:45:26.520 --> 00:45:28.550 align:start position:0% consensus layer execution layer like calls<00:45:27.240> or<00:45:27.480> how<00:45:27.839> are<00:45:27.960> we<00:45:28.079> thinking<00:45:28.380> about 00:45:28.550 --> 00:45:28.560 align:start position:0% calls or how are we thinking about 00:45:28.560 --> 00:45:32.150 align:start position:0% calls or how are we thinking about governance<00:45:29.220> I<00:45:29.579> guess<00:45:29.640> moving<00:45:30.060> forward<00:45:30.300> to<00:45:30.780> to 00:45:32.150 --> 00:45:32.160 align:start position:0% governance I guess moving forward to to 00:45:32.160 --> 00:45:34.250 align:start position:0% governance I guess moving forward to to to<00:45:32.760> start<00:45:32.940> to<00:45:33.300> like 00:45:34.250 --> 00:45:34.260 align:start position:0% to start to like 00:45:34.260 --> 00:45:36.710 align:start position:0% to start to like um<00:45:34.319> yeah<00:45:34.740> pull<00:45:35.040> off<00:45:35.220> some<00:45:35.460> of<00:45:35.579> the<00:45:35.700> other<00:45:35.819> big 00:45:36.710 --> 00:45:36.720 align:start position:0% um yeah pull off some of the other big 00:45:36.720 --> 00:45:40.670 align:start position:0% um yeah pull off some of the other big big<00:45:37.220> road<00:45:38.220> map<00:45:38.460> items 00:45:40.670 --> 00:45:40.680 align:start position:0% big road map items 00:45:40.680 --> 00:45:43.010 align:start position:0% big road map items wow<00:45:41.220> there's<00:45:41.460> a<00:45:41.640> lot<00:45:41.760> to<00:45:41.880> unpack<00:45:42.180> in<00:45:42.359> there 00:45:43.010 --> 00:45:43.020 align:start position:0% wow there's a lot to unpack in there 00:45:43.020 --> 00:45:45.710 align:start position:0% wow there's a lot to unpack in there um<00:45:43.440> I<00:45:43.920> think<00:45:44.040> High<00:45:44.700> short<00:45:45.180> really<00:45:45.480> short 00:45:45.710 --> 00:45:45.720 align:start position:0% um I think High short really short 00:45:45.720 --> 00:45:48.050 align:start position:0% um I think High short really short answer<00:45:45.960> is<00:45:46.200> like<00:45:46.619> slowly<00:45:47.400> iterating<00:45:47.819> from 00:45:48.050 --> 00:45:48.060 align:start position:0% answer is like slowly iterating from 00:45:48.060 --> 00:45:50.569 align:start position:0% answer is like slowly iterating from what<00:45:48.240> we<00:45:48.420> have<00:45:48.660> like<00:45:49.140> I<00:45:49.380> think<00:45:49.500> just<00:45:49.800> like<00:45:50.099> the 00:45:50.569 --> 00:45:50.579 align:start position:0% what we have like I think just like the 00:45:50.579 --> 00:45:53.990 align:start position:0% what we have like I think just like the merge<00:45:51.000> itself<00:45:51.599> was<00:45:52.260> kind<00:45:52.560> of<00:45:52.680> a<00:45:52.980> feat<00:45:53.880> of 00:45:53.990 --> 00:45:54.000 align:start position:0% merge itself was kind of a feat of 00:45:54.000 --> 00:45:55.609 align:start position:0% merge itself was kind of a feat of governance<00:45:54.420> to<00:45:54.599> some<00:45:54.780> extent<00:45:55.079> to<00:45:55.260> get<00:45:55.440> like 00:45:55.609 --> 00:45:55.619 align:start position:0% governance to some extent to get like 00:45:55.619 --> 00:45:58.130 align:start position:0% governance to some extent to get like mine<00:45:55.980> kind<00:45:56.160> teams<00:45:56.579> to<00:45:56.700> work<00:45:56.880> together 00:45:58.130 --> 00:45:58.140 align:start position:0% mine kind teams to work together 00:45:58.140 --> 00:46:01.309 align:start position:0% mine kind teams to work together um<00:45:58.260> and<00:45:58.560> agree<00:45:58.859> on<00:45:59.099> like<00:45:59.520> uh<00:46:00.480> like<00:46:00.780> agreeing<00:46:01.200> on 00:46:01.309 --> 00:46:01.319 align:start position:0% um and agree on like uh like agreeing on 00:46:01.319 --> 00:46:02.990 align:start position:0% um and agree on like uh like agreeing on the<00:46:01.440> big<00:46:01.560> stuff<00:46:01.740> was<00:46:01.920> easy<00:46:02.160> for<00:46:02.400> the<00:46:02.579> merch<00:46:02.880> I 00:46:02.990 --> 00:46:03.000 align:start position:0% the big stuff was easy for the merch I 00:46:03.000 --> 00:46:04.730 align:start position:0% the big stuff was easy for the merch I think<00:46:03.119> everybody<00:46:03.240> wanted<00:46:03.599> to<00:46:03.839> do<00:46:03.960> it 00:46:04.730 --> 00:46:04.740 align:start position:0% think everybody wanted to do it 00:46:04.740 --> 00:46:05.410 align:start position:0% think everybody wanted to do it um 00:46:05.410 --> 00:46:05.420 align:start position:0% um 00:46:05.420 --> 00:46:08.030 align:start position:0% um like<00:46:06.420> all<00:46:06.900> the<00:46:07.020> tiny<00:46:07.380> things<00:46:07.500> I<00:46:07.740> don't<00:46:07.859> know<00:46:07.920> I 00:46:08.030 --> 00:46:08.040 align:start position:0% like all the tiny things I don't know I 00:46:08.040 --> 00:46:10.370 align:start position:0% like all the tiny things I don't know I have<00:46:08.160> latest<00:46:08.400> valid<00:46:08.819> hash<00:46:09.060> like<00:46:09.660> burnt<00:46:10.260> into 00:46:10.370 --> 00:46:10.380 align:start position:0% have latest valid hash like burnt into 00:46:10.380 --> 00:46:12.230 align:start position:0% have latest valid hash like burnt into my<00:46:10.680> head<00:46:10.800> from<00:46:11.099> typing<00:46:11.460> in<00:46:11.640> the<00:46:11.819> El<00:46:11.940> Cortez 00:46:12.230 --> 00:46:12.240 align:start position:0% my head from typing in the El Cortez 00:46:12.240 --> 00:46:14.390 align:start position:0% my head from typing in the El Cortez agenda<00:46:13.200> um<00:46:13.319> like<00:46:13.619> it's<00:46:13.800> just<00:46:14.040> like<00:46:14.220> this 00:46:14.390 --> 00:46:14.400 align:start position:0% agenda um like it's just like this 00:46:14.400 --> 00:46:16.550 align:start position:0% agenda um like it's just like this thousand<00:46:14.819> tiny<00:46:15.240> things<00:46:15.300> where<00:46:15.599> it's<00:46:15.839> like<00:46:16.380> the 00:46:16.550 --> 00:46:16.560 align:start position:0% thousand tiny things where it's like the 00:46:16.560 --> 00:46:18.650 align:start position:0% thousand tiny things where it's like the coordinations<00:46:16.980> was<00:46:17.460> really<00:46:17.700> hard 00:46:18.650 --> 00:46:18.660 align:start position:0% coordinations was really hard 00:46:18.660 --> 00:46:21.530 align:start position:0% coordinations was really hard um<00:46:18.720> I<00:46:19.079> think<00:46:19.200> the<00:46:19.740> other<00:46:19.859> thing<00:46:20.040> is<00:46:20.220> like<00:46:20.540> and 00:46:21.530 --> 00:46:21.540 align:start position:0% um I think the other thing is like and 00:46:21.540 --> 00:46:23.030 align:start position:0% um I think the other thing is like and and<00:46:21.660> we're<00:46:21.960> about<00:46:22.079> to<00:46:22.319> get<00:46:22.380> into<00:46:22.500> seconds<00:46:22.800> it's 00:46:23.030 --> 00:46:23.040 align:start position:0% and we're about to get into seconds it's 00:46:23.040 --> 00:46:26.569 align:start position:0% and we're about to get into seconds it's like<00:46:23.280> balancing<00:46:23.819> like<00:46:24.660> large<00:46:25.579> protocol 00:46:26.569 --> 00:46:26.579 align:start position:0% like balancing like large protocol 00:46:26.579 --> 00:46:28.190 align:start position:0% like balancing like large protocol changes<00:46:27.119> so<00:46:27.300> something<00:46:27.540> like<00:46:27.780> the<00:46:27.900> merge 00:46:28.190 --> 00:46:28.200 align:start position:0% changes so something like the merge 00:46:28.200 --> 00:46:29.630 align:start position:0% changes so something like the merge something<00:46:28.380> like<00:46:28.740> sharding<00:46:29.220> something<00:46:29.460> like 00:46:29.630 --> 00:46:29.640 align:start position:0% something like sharding something like 00:46:29.640 --> 00:46:32.930 align:start position:0% something like sharding something like stateless<00:46:30.060> with<00:46:30.839> like<00:46:31.200> smaller<00:46:32.160> things<00:46:32.460> that 00:46:32.930 --> 00:46:32.940 align:start position:0% stateless with like smaller things that 00:46:32.940 --> 00:46:35.750 align:start position:0% stateless with like smaller things that like<00:46:33.180> bring<00:46:33.420> it<00:46:33.660> out<00:46:33.839> of<00:46:33.960> value<00:46:34.079> as<00:46:34.319> well<00:46:34.500> I<00:46:35.400> I 00:46:35.750 --> 00:46:35.760 align:start position:0% like bring it out of value as well I I 00:46:35.760 --> 00:46:38.089 align:start position:0% like bring it out of value as well I I think<00:46:36.000> this<00:46:36.300> is<00:46:36.480> where<00:46:36.780> most<00:46:37.380> of<00:46:37.560> the<00:46:37.680> tension 00:46:38.089 --> 00:46:38.099 align:start position:0% think this is where most of the tension 00:46:38.099 --> 00:46:40.250 align:start position:0% think this is where most of the tension probably<00:46:38.579> arises<00:46:39.180> like<00:46:39.660> different 00:46:40.250 --> 00:46:40.260 align:start position:0% probably arises like different 00:46:40.260 --> 00:46:42.589 align:start position:0% probably arises like different prioritizations<00:46:41.040> there<00:46:41.460> I<00:46:41.940> think<00:46:42.060> so<00:46:42.480> I'm 00:46:42.589 --> 00:46:42.599 align:start position:0% prioritizations there I think so I'm 00:46:42.599 --> 00:46:43.790 align:start position:0% prioritizations there I think so I'm curious<00:46:42.780> to<00:46:42.839> hear<00:46:42.960> from<00:46:43.020> Dan<00:46:43.140> crowd<00:46:43.380> then 00:46:43.790 --> 00:46:43.800 align:start position:0% curious to hear from Dan crowd then 00:46:43.800 --> 00:46:45.410 align:start position:0% curious to hear from Dan crowd then crowd<00:46:44.160> you<00:46:44.280> have<00:46:44.400> like<00:46:44.640> some<00:46:45.060> like<00:46:45.300> more 00:46:45.410 --> 00:46:45.420 align:start position:0% crowd you have like some like more 00:46:45.420 --> 00:46:47.030 align:start position:0% crowd you have like some like more radical<00:46:45.780> views<00:46:46.079> about<00:46:46.200> the<00:46:46.380> process<00:46:46.619> than<00:46:46.859> me 00:46:47.030 --> 00:46:47.040 align:start position:0% radical views about the process than me 00:46:47.040 --> 00:46:49.010 align:start position:0% radical views about the process than me so<00:46:47.220> yeah<00:46:47.819> and<00:46:48.060> you<00:46:48.180> haven't<00:46:48.300> spoken<00:46:48.660> so<00:46:48.780> far<00:46:48.900> so 00:46:49.010 --> 00:46:49.020 align:start position:0% so yeah and you haven't spoken so far so 00:46:49.020 --> 00:46:50.569 align:start position:0% so yeah and you haven't spoken so far so I<00:46:49.140> think<00:46:49.260> it's<00:46:49.380> a<00:46:49.500> good<00:46:49.680> it's<00:46:49.920> a<00:46:50.099> good<00:46:50.220> cue<00:46:50.400> for 00:46:50.569 --> 00:46:50.579 align:start position:0% I think it's a good it's a good cue for 00:46:50.579 --> 00:46:53.450 align:start position:0% I think it's a good it's a good cue for you 00:46:53.450 --> 00:46:53.460 align:start position:0% 00:46:53.460 --> 00:46:54.170 align:start position:0% um 00:46:54.170 --> 00:46:54.180 align:start position:0% um 00:46:54.180 --> 00:46:59.930 align:start position:0% um I<00:46:54.660> mean<00:46:54.839> that's<00:46:54.960> a<00:46:55.079> big<00:46:55.260> jump<00:46:55.440> but<00:46:55.680> yeah<00:46:56.160> um 00:46:59.930 --> 00:46:59.940 align:start position:0% 00:46:59.940 --> 00:47:02.150 align:start position:0% um<00:47:00.119> I<00:47:00.420> mean<00:47:00.540> my<00:47:00.720> view<00:47:01.140> on<00:47:01.319> all<00:47:01.440> core<00:47:01.619> devs<00:47:02.040> I 00:47:02.150 --> 00:47:02.160 align:start position:0% um I mean my view on all core devs I 00:47:02.160 --> 00:47:04.670 align:start position:0% um I mean my view on all core devs I mean<00:47:02.280> like<00:47:02.460> I<00:47:02.700> mean<00:47:02.819> uh<00:47:03.480> I<00:47:03.960> think<00:47:04.380> the<00:47:04.500> big 00:47:04.670 --> 00:47:04.680 align:start position:0% mean like I mean uh I think the big 00:47:04.680 --> 00:47:07.190 align:start position:0% mean like I mean uh I think the big thing<00:47:04.920> that<00:47:05.280> I<00:47:05.700> I<00:47:06.119> feel<00:47:06.359> is<00:47:06.540> missing<00:47:06.900> and<00:47:07.079> that 00:47:07.190 --> 00:47:07.200 align:start position:0% thing that I I feel is missing and that 00:47:07.200 --> 00:47:08.930 align:start position:0% thing that I I feel is missing and that I<00:47:07.380> want<00:47:07.560> to<00:47:07.680> see<00:47:07.800> is 00:47:08.930 --> 00:47:08.940 align:start position:0% I want to see is 00:47:08.940 --> 00:47:10.970 align:start position:0% I want to see is um<00:47:09.000> representation<00:47:09.660> of<00:47:10.020> like<00:47:10.260> ethereum's 00:47:10.970 --> 00:47:10.980 align:start position:0% um representation of like ethereum's 00:47:10.980 --> 00:47:12.589 align:start position:0% um representation of like ethereum's users<00:47:11.280> and<00:47:11.520> the<00:47:11.700> whole<00:47:11.880> Community<00:47:12.060> rather 00:47:12.589 --> 00:47:12.599 align:start position:0% users and the whole Community rather 00:47:12.599 --> 00:47:15.170 align:start position:0% users and the whole Community rather than<00:47:12.720> it<00:47:13.319> mostly<00:47:13.680> being<00:47:13.859> focused<00:47:14.400> around<00:47:14.640> one 00:47:15.170 --> 00:47:15.180 align:start position:0% than it mostly being focused around one 00:47:15.180 --> 00:47:18.109 align:start position:0% than it mostly being focused around one side<00:47:15.420> of<00:47:15.839> the<00:47:16.079> of<00:47:16.380> the<00:47:17.220> um<00:47:17.280> of<00:47:17.520> ethereum<00:47:17.940> which 00:47:18.109 --> 00:47:18.119 align:start position:0% side of the of the um of ethereum which 00:47:18.119 --> 00:47:19.609 align:start position:0% side of the of the um of ethereum which is<00:47:18.240> the<00:47:18.420> development 00:47:19.609 --> 00:47:19.619 align:start position:0% is the development 00:47:19.619 --> 00:47:21.230 align:start position:0% is the development um<00:47:19.680> and<00:47:19.859> I<00:47:19.920> think<00:47:20.099> that's<00:47:20.400> uh<00:47:20.700> that's<00:47:21.060> a<00:47:21.180> big 00:47:21.230 --> 00:47:21.240 align:start position:0% um and I think that's uh that's a big 00:47:21.240 --> 00:47:23.990 align:start position:0% um and I think that's uh that's a big thing<00:47:21.420> and<00:47:21.660> we<00:47:21.839> would<00:47:22.020> see<00:47:22.859> very<00:47:23.400> interesting 00:47:23.990 --> 00:47:24.000 align:start position:0% thing and we would see very interesting 00:47:24.000 --> 00:47:26.390 align:start position:0% thing and we would see very interesting and<00:47:24.300> different<00:47:24.480> proposals<00:47:25.200> if<00:47:25.440> we<00:47:25.680> had<00:47:26.160> more 00:47:26.390 --> 00:47:26.400 align:start position:0% and different proposals if we had more 00:47:26.400 --> 00:47:28.250 align:start position:0% and different proposals if we had more voices<00:47:26.700> like<00:47:26.940> that<00:47:27.060> on<00:47:27.240> the<00:47:27.420> call<00:47:27.599> also<00:47:28.200> the 00:47:28.250 --> 00:47:28.260 align:start position:0% voices like that on the call also the 00:47:28.260 --> 00:47:31.430 align:start position:0% voices like that on the call also the app<00:47:28.440> process<00:47:29.220> is<00:47:29.400> being<00:47:29.700> like<00:47:30.599> it's<00:47:31.200> being 00:47:31.430 --> 00:47:31.440 align:start position:0% app process is being like it's being 00:47:31.440 --> 00:47:34.550 align:start position:0% app process is being like it's being improved<00:47:32.099> over<00:47:33.060> time<00:47:33.300> and<00:47:33.599> right<00:47:33.839> now<00:47:34.020> what 00:47:34.550 --> 00:47:34.560 align:start position:0% improved over time and right now what 00:47:34.560 --> 00:47:37.730 align:start position:0% improved over time and right now what like<00:47:35.040> not<00:47:35.520> like<00:47:35.880> we<00:47:36.180> but<00:47:36.480> the<00:47:36.599> ipip<00:47:37.200> group<00:47:37.500> is 00:47:37.730 --> 00:47:37.740 align:start position:0% like not like we but the ipip group is 00:47:37.740 --> 00:47:40.309 align:start position:0% like not like we but the ipip group is working<00:47:37.980> on<00:47:38.220> and<00:47:38.520> uh<00:47:38.819> alongside<00:47:39.599> with<00:47:39.960> uh 00:47:40.309 --> 00:47:40.319 align:start position:0% working on and uh alongside with uh 00:47:40.319 --> 00:47:42.829 align:start position:0% working on and uh alongside with uh ethereum<00:47:40.740> cat<00:47:40.980> holders<00:47:41.400> uh<00:47:42.300> it's<00:47:42.480> pretty<00:47:42.660> much 00:47:42.829 --> 00:47:42.839 align:start position:0% ethereum cat holders uh it's pretty much 00:47:42.839 --> 00:47:45.950 align:start position:0% ethereum cat holders uh it's pretty much that<00:47:43.200> they<00:47:43.619> are<00:47:44.099> going<00:47:44.280> to<00:47:44.460> like<00:47:44.760> sort<00:47:45.060> of<00:47:45.300> fork 00:47:45.950 --> 00:47:45.960 align:start position:0% that they are going to like sort of fork 00:47:45.960 --> 00:47:48.290 align:start position:0% that they are going to like sort of fork or<00:47:46.200> like<00:47:46.440> separate<00:47:46.859> the<00:47:47.099> core<00:47:47.280> eyepiece<00:47:47.940> from 00:47:48.290 --> 00:47:48.300 align:start position:0% or like separate the core eyepiece from 00:47:48.300 --> 00:47:51.470 align:start position:0% or like separate the core eyepiece from the<00:47:48.599> other<00:47:49.200> year<00:47:50.040> season<00:47:50.400> like<00:47:50.700> are<00:47:51.000> different 00:47:51.470 --> 00:47:51.480 align:start position:0% the other year season like are different 00:47:51.480 --> 00:47:59.770 align:start position:0% the other year season like are different aips<00:47:51.920> and<00:47:52.920> then<00:47:53.099> eventually 00:47:59.770 --> 00:47:59.780 align:start position:0% 00:47:59.780 --> 00:48:02.390 align:start position:0% yeah<00:48:00.780> but<00:48:01.140> like<00:48:01.319> I<00:48:01.560> remember<00:48:01.740> like<00:48:02.040> we've<00:48:02.220> been 00:48:02.390 --> 00:48:02.400 align:start position:0% yeah but like I remember like we've been 00:48:02.400 --> 00:48:04.309 align:start position:0% yeah but like I remember like we've been talking<00:48:02.640> with<00:48:02.940> like<00:48:03.240> team<00:48:03.599> and<00:48:03.960> some<00:48:04.140> other 00:48:04.309 --> 00:48:04.319 align:start position:0% talking with like team and some other 00:48:04.319 --> 00:48:06.230 align:start position:0% talking with like team and some other even<00:48:04.619> like<00:48:04.800> Hudson<00:48:05.099> I<00:48:05.280> think<00:48:05.400> you<00:48:05.640> were<00:48:05.940> there 00:48:06.230 --> 00:48:06.240 align:start position:0% even like Hudson I think you were there 00:48:06.240 --> 00:48:08.630 align:start position:0% even like Hudson I think you were there in<00:48:06.420> the<00:48:06.540> group<00:48:06.720> where<00:48:07.560> we<00:48:07.800> wanted<00:48:07.980> to<00:48:08.220> separate 00:48:08.630 --> 00:48:08.640 align:start position:0% in the group where we wanted to separate 00:48:08.640 --> 00:48:13.550 align:start position:0% in the group where we wanted to separate e<00:48:09.500> uh<00:48:10.500> erc's<00:48:11.339> from<00:48:11.760> the<00:48:12.000> eaps 00:48:13.550 --> 00:48:13.560 align:start position:0% e uh erc's from the eaps 00:48:13.560 --> 00:48:14.870 align:start position:0% e uh erc's from the eaps um 00:48:14.870 --> 00:48:14.880 align:start position:0% um 00:48:14.880 --> 00:48:19.550 align:start position:0% um oh<00:48:15.740> Jesus<00:48:16.740> I<00:48:17.099> mean<00:48:17.220> also<00:48:17.880> happen<00:48:18.060> we<00:48:18.660> we<00:48:19.260> did 00:48:19.550 --> 00:48:19.560 align:start position:0% oh Jesus I mean also happen we we did 00:48:19.560 --> 00:48:21.050 align:start position:0% oh Jesus I mean also happen we we did not<00:48:19.740> use<00:48:20.160> the 00:48:21.050 --> 00:48:21.060 align:start position:0% not use the 00:48:21.060 --> 00:48:23.089 align:start position:0% not use the stage<00:48:21.599> because<00:48:21.960> we<00:48:22.319> went<00:48:22.440> to<00:48:22.619> like<00:48:22.800> be 00:48:23.089 --> 00:48:23.099 align:start position:0% stage because we went to like be 00:48:23.099 --> 00:48:24.610 align:start position:0% stage because we went to like be everybody<00:48:23.460> on<00:48:24.060> the<00:48:24.300> same 00:48:24.610 --> 00:48:24.620 align:start position:0% everybody on the same 00:48:24.620 --> 00:48:27.890 align:start position:0% everybody on the same [Laughter] 00:48:27.890 --> 00:48:27.900 align:start position:0% [Laughter] 00:48:27.900 --> 00:48:29.450 align:start position:0% [Laughter] okay 00:48:29.450 --> 00:48:29.460 align:start position:0% okay 00:48:29.460 --> 00:48:30.829 align:start position:0% okay thank<00:48:29.880> you 00:48:30.829 --> 00:48:30.839 align:start position:0% thank you 00:48:30.839 --> 00:48:32.089 align:start position:0% thank you um 00:48:32.089 --> 00:48:32.099 align:start position:0% um 00:48:32.099 --> 00:48:33.950 align:start position:0% um so<00:48:32.460> pretty<00:48:32.700> much<00:48:32.880> we<00:48:33.119> wanted<00:48:33.240> to<00:48:33.480> separate 00:48:33.950 --> 00:48:33.960 align:start position:0% so pretty much we wanted to separate 00:48:33.960 --> 00:48:36.829 align:start position:0% so pretty much we wanted to separate erc's<00:48:34.619> from<00:48:34.859> uh<00:48:35.040> eaps<00:48:35.700> but<00:48:35.940> then<00:48:36.060> it<00:48:36.420> ended<00:48:36.720> up 00:48:36.829 --> 00:48:36.839 align:start position:0% erc's from uh eaps but then it ended up 00:48:36.839 --> 00:48:39.290 align:start position:0% erc's from uh eaps but then it ended up what<00:48:37.020> ended<00:48:37.380> up<00:48:37.440> happening<00:48:37.859> is<00:48:38.099> that<00:48:38.280> we<00:48:38.460> ended 00:48:39.290 --> 00:48:39.300 align:start position:0% what ended up happening is that we ended 00:48:39.300 --> 00:48:42.170 align:start position:0% what ended up happening is that we ended up<00:48:39.359> sort<00:48:39.960> of<00:48:40.140> separating<00:48:40.500> core<00:48:40.740> IPS<00:48:41.220> from<00:48:41.579> the 00:48:42.170 --> 00:48:42.180 align:start position:0% up sort of separating core IPS from the 00:48:42.180 --> 00:48:44.630 align:start position:0% up sort of separating core IPS from the rest<00:48:42.300> of<00:48:42.540> the<00:48:42.900> eaps<00:48:43.680> that's<00:48:44.099> exactly<00:48:44.460> right 00:48:44.630 --> 00:48:44.640 align:start position:0% rest of the eaps that's exactly right 00:48:44.640 --> 00:48:47.630 align:start position:0% rest of the eaps that's exactly right and<00:48:45.540> um<00:48:45.540> there's<00:48:46.260> been<00:48:46.500> there's<00:48:47.040> been<00:48:47.280> years 00:48:47.630 --> 00:48:47.640 align:start position:0% and um there's been there's been years 00:48:47.640 --> 00:48:49.609 align:start position:0% and um there's been there's been years and<00:48:48.000> years<00:48:48.359> of<00:48:48.660> debate<00:48:48.960> over<00:48:49.140> whether<00:48:49.319> to 00:48:49.609 --> 00:48:49.619 align:start position:0% and years of debate over whether to 00:48:49.619 --> 00:48:53.329 align:start position:0% and years of debate over whether to separate<00:48:49.800> eips<00:48:50.160> from<00:48:50.400> erc's<00:48:51.020> and<00:48:52.020> a<00:48:52.260> lot<00:48:52.380> of<00:48:52.500> it 00:48:53.329 --> 00:48:53.339 align:start position:0% separate eips from erc's and a lot of it 00:48:53.339 --> 00:48:54.890 align:start position:0% separate eips from erc's and a lot of it the<00:48:53.760> biggest<00:48:53.940> problem<00:48:54.180> I'm<00:48:54.359> finding<00:48:54.720> looking 00:48:54.890 --> 00:48:54.900 align:start position:0% the biggest problem I'm finding looking 00:48:54.900 --> 00:48:57.650 align:start position:0% the biggest problem I'm finding looking back<00:48:55.200> is<00:48:55.740> that<00:48:55.920> there<00:48:56.220> wasn't<00:48:56.400> a<00:48:56.819> steward<00:48:57.060> to 00:48:57.650 --> 00:48:57.660 align:start position:0% back is that there wasn't a steward to 00:48:57.660 --> 00:49:00.230 align:start position:0% back is that there wasn't a steward to be<00:48:57.780> an<00:48:57.960> ERC<00:48:58.380> editor<00:48:58.800> I<00:48:59.400> mean<00:48:59.520> there<00:48:59.819> are<00:49:00.060> also 00:49:00.230 --> 00:49:00.240 align:start position:0% be an ERC editor I mean there are also 00:49:00.240 --> 00:49:02.990 align:start position:0% be an ERC editor I mean there are also EIP<00:49:00.599> editors<00:49:01.260> already<00:49:01.560> but<00:49:02.040> there<00:49:02.280> are<00:49:02.579> like 00:49:02.990 --> 00:49:03.000 align:start position:0% EIP editors already but there are like 00:49:03.000 --> 00:49:05.569 align:start position:0% EIP editors already but there are like two<00:49:03.780> or<00:49:03.960> three<00:49:04.200> people<00:49:04.500> at<00:49:05.040> this<00:49:05.220> point<00:49:05.400> and 00:49:05.569 --> 00:49:05.579 align:start position:0% two or three people at this point and 00:49:05.579 --> 00:49:06.950 align:start position:0% two or three people at this point and Micah<00:49:06.000> doesn't<00:49:06.119> want<00:49:06.240> to<00:49:06.300> do<00:49:06.359> erc's<00:49:06.839> anymore 00:49:06.950 --> 00:49:06.960 align:start position:0% Micah doesn't want to do erc's anymore 00:49:06.960 --> 00:49:08.809 align:start position:0% Micah doesn't want to do erc's anymore like<00:49:07.260> he's<00:49:07.380> been<00:49:07.560> open<00:49:07.680> about<00:49:07.920> that<00:49:08.220> I<00:49:08.700> mean 00:49:08.809 --> 00:49:08.819 align:start position:0% like he's been open about that I mean 00:49:08.819 --> 00:49:10.790 align:start position:0% like he's been open about that I mean yeah<00:49:09.119> there<00:49:09.480> was<00:49:09.660> like<00:49:09.960> many<00:49:10.260> people<00:49:10.500> that 00:49:10.790 --> 00:49:10.800 align:start position:0% yeah there was like many people that 00:49:10.800 --> 00:49:12.710 align:start position:0% yeah there was like many people that wanted<00:49:11.040> to<00:49:11.280> sort<00:49:11.460> of<00:49:11.640> do<00:49:11.760> it<00:49:11.880> I<00:49:12.000> was<00:49:12.240> even<00:49:12.359> like 00:49:12.710 --> 00:49:12.720 align:start position:0% wanted to sort of do it I was even like 00:49:12.720 --> 00:49:14.930 align:start position:0% wanted to sort of do it I was even like one<00:49:13.440> of<00:49:13.560> the<00:49:13.680> people<00:49:13.800> that<00:49:14.099> wanted<00:49:14.339> to<00:49:14.520> like<00:49:14.700> do 00:49:14.930 --> 00:49:14.940 align:start position:0% one of the people that wanted to like do 00:49:14.940 --> 00:49:16.970 align:start position:0% one of the people that wanted to like do it<00:49:15.060> myself<00:49:15.300> on<00:49:15.780> behalf<00:49:16.140> of<00:49:16.200> magicians<00:49:16.800> but 00:49:16.970 --> 00:49:16.980 align:start position:0% it myself on behalf of magicians but 00:49:16.980 --> 00:49:19.370 align:start position:0% it myself on behalf of magicians but then<00:49:17.160> like<00:49:17.420> it<00:49:18.420> kind<00:49:18.599> of<00:49:18.660> fizzled<00:49:18.960> yeah<00:49:19.140> there 00:49:19.370 --> 00:49:19.380 align:start position:0% then like it kind of fizzled yeah there 00:49:19.380 --> 00:49:21.170 align:start position:0% then like it kind of fizzled yeah there was<00:49:19.500> there<00:49:19.740> was<00:49:19.920> like<00:49:20.180> miscommunication 00:49:21.170 --> 00:49:21.180 align:start position:0% was there was like miscommunication 00:49:21.180 --> 00:49:22.069 align:start position:0% was there was like miscommunication there<00:49:21.540> was<00:49:21.660> like<00:49:21.720> a<00:49:21.839> lot<00:49:21.900> of<00:49:21.960> different 00:49:22.069 --> 00:49:22.079 align:start position:0% there was like a lot of different 00:49:22.079 --> 00:49:23.210 align:start position:0% there was like a lot of different problems<00:49:22.380> but<00:49:22.560> either<00:49:22.619> way<00:49:22.800> I'm<00:49:22.980> glad<00:49:23.099> that 00:49:23.210 --> 00:49:23.220 align:start position:0% problems but either way I'm glad that 00:49:23.220 --> 00:49:25.309 align:start position:0% problems but either way I'm glad that it's<00:49:23.339> getting<00:49:23.460> separated<00:49:23.880> now<00:49:24.240> that's<00:49:25.079> gonna 00:49:25.309 --> 00:49:25.319 align:start position:0% it's getting separated now that's gonna 00:49:25.319 --> 00:49:26.510 align:start position:0% it's getting separated now that's gonna make<00:49:25.500> things<00:49:25.619> less<00:49:25.800> confusing<00:49:26.160> when<00:49:26.339> people 00:49:26.510 --> 00:49:26.520 align:start position:0% make things less confusing when people 00:49:26.520 --> 00:49:30.290 align:start position:0% make things less confusing when people talk<00:49:26.700> about<00:49:26.819> eips<00:49:27.240> and<00:49:27.660> especially<00:49:28.079> is<00:49:28.440> POS<00:49:29.300> uh 00:49:30.290 --> 00:49:30.300 align:start position:0% talk about eips and especially is POS uh 00:49:30.300 --> 00:49:32.690 align:start position:0% talk about eips and especially is POS uh because<00:49:30.599> back<00:49:31.020> in<00:49:31.200> like<00:49:31.380> I<00:49:31.859> think<00:49:31.980> we<00:49:32.400> had<00:49:32.520> this 00:49:32.690 --> 00:49:32.700 align:start position:0% because back in like I think we had this 00:49:32.700 --> 00:49:34.910 align:start position:0% because back in like I think we had this discussion<00:49:33.119> and<00:49:33.540> uh<00:49:33.839> like<00:49:34.140> with<00:49:34.380> Mario's 00:49:34.910 --> 00:49:34.920 align:start position:0% discussion and uh like with Mario's 00:49:34.920 --> 00:49:37.130 align:start position:0% discussion and uh like with Mario's right<00:49:34.980> at<00:49:35.400> the<00:49:35.579> Amsterdam<00:49:36.119> where<00:49:36.599> we<00:49:36.780> started 00:49:37.130 --> 00:49:37.140 align:start position:0% right at the Amsterdam where we started 00:49:37.140 --> 00:49:40.309 align:start position:0% right at the Amsterdam where we started talking<00:49:37.380> about<00:49:37.859> how<00:49:38.579> the<00:49:39.000> EI<00:49:39.359> process<00:49:40.079> will 00:49:40.309 --> 00:49:40.319 align:start position:0% talking about how the EI process will 00:49:40.319 --> 00:49:42.470 align:start position:0% talking about how the EI process will gonna<00:49:40.560> look<00:49:40.800> like<00:49:40.980> and<00:49:41.400> that<00:49:41.700> was<00:49:41.880> like<00:49:42.060> April 00:49:42.470 --> 00:49:42.480 align:start position:0% gonna look like and that was like April 00:49:42.480 --> 00:49:43.670 align:start position:0% gonna look like and that was like April this<00:49:42.720> year 00:49:43.670 --> 00:49:43.680 align:start position:0% this year 00:49:43.680 --> 00:49:46.130 align:start position:0% this year um<00:49:43.800> and<00:49:44.099> only<00:49:44.339> basically<00:49:45.119> pretty<00:49:45.359> much<00:49:45.540> got<00:49:45.780> as 00:49:46.130 --> 00:49:46.140 align:start position:0% um and only basically pretty much got as 00:49:46.140 --> 00:49:48.950 align:start position:0% um and only basically pretty much got as answer<00:49:46.440> was<00:49:46.920> that<00:49:47.160> it<00:49:47.339> will<00:49:47.520> be<00:49:48.119> consensus 00:49:48.950 --> 00:49:48.960 align:start position:0% answer was that it will be consensus 00:49:48.960 --> 00:49:53.030 align:start position:0% answer was that it will be consensus driven<00:49:49.579> so<00:49:50.579> not<00:49:50.940> not<00:49:51.300> AIP<00:49:51.780> process<00:49:52.200> as<00:49:52.560> we<00:49:52.859> are 00:49:53.030 --> 00:49:53.040 align:start position:0% driven so not not AIP process as we are 00:49:53.040 --> 00:49:55.190 align:start position:0% driven so not not AIP process as we are used<00:49:53.280> to<00:49:53.400> right<00:49:54.119> now<00:49:54.240> which<00:49:54.599> is<00:49:54.780> by<00:49:55.020> the<00:49:55.140> way 00:49:55.190 --> 00:49:55.200 align:start position:0% used to right now which is by the way 00:49:55.200 --> 00:49:57.050 align:start position:0% used to right now which is by the way described<00:49:55.680> in<00:49:55.859> the<00:49:56.040> IAP<00:49:56.280> one<00:49:56.520> which<00:49:56.700> you<00:49:56.880> guys 00:49:57.050 --> 00:49:57.060 align:start position:0% described in the IAP one which you guys 00:49:57.060 --> 00:50:01.069 align:start position:0% described in the IAP one which you guys can<00:49:57.240> find<00:49:57.480> on<00:49:57.839> uh<00:49:58.440> eip.etherium.org 00:50:01.069 --> 00:50:01.079 align:start position:0% can find on uh eip.etherium.org 00:50:01.079 --> 00:50:04.069 align:start position:0% can find on uh eip.etherium.org um<00:50:01.140> yeah<00:50:02.099> can<00:50:02.700> I<00:50:02.819> say<00:50:02.940> one<00:50:03.480> more<00:50:03.660> quick<00:50:03.900> thing 00:50:04.069 --> 00:50:04.079 align:start position:0% um yeah can I say one more quick thing 00:50:04.079 --> 00:50:06.109 align:start position:0% um yeah can I say one more quick thing on<00:50:04.319> the<00:50:04.440> eip's<00:50:04.980> I<00:50:05.220> I<00:50:05.400> guess<00:50:05.579> it's<00:50:05.700> like<00:50:05.880> worth 00:50:06.109 --> 00:50:06.119 align:start position:0% on the eip's I I guess it's like worth 00:50:06.119 --> 00:50:07.670 align:start position:0% on the eip's I I guess it's like worth separating<00:50:06.540> like<00:50:06.780> the<00:50:07.020> tools<00:50:07.319> from<00:50:07.500> the 00:50:07.670 --> 00:50:07.680 align:start position:0% separating like the tools from the 00:50:07.680 --> 00:50:09.109 align:start position:0% separating like the tools from the process<00:50:07.920> like<00:50:08.220> sure<00:50:08.339> you<00:50:08.520> know<00:50:08.640> like<00:50:08.819> we<00:50:09.000> can 00:50:09.109 --> 00:50:09.119 align:start position:0% process like sure you know like we can 00:50:09.119 --> 00:50:11.569 align:start position:0% process like sure you know like we can split<00:50:09.420> out<00:50:09.480> the<00:50:09.660> RCs<00:50:10.140> and<00:50:10.380> I'm<00:50:10.920> very<00:50:11.220> bullish 00:50:11.569 --> 00:50:11.579 align:start position:0% split out the RCs and I'm very bullish 00:50:11.579 --> 00:50:13.970 align:start position:0% split out the RCs and I'm very bullish on<00:50:11.760> my<00:50:11.940> executable<00:50:12.540> specs<00:50:13.020> for<00:50:13.200> for<00:50:13.440> the 00:50:13.970 --> 00:50:13.980 align:start position:0% on my executable specs for for the 00:50:13.980 --> 00:50:15.890 align:start position:0% on my executable specs for for the Executioner<00:50:14.760> like<00:50:15.060> there's<00:50:15.240> a<00:50:15.420> bunch<00:50:15.540> of<00:50:15.660> like 00:50:15.890 --> 00:50:15.900 align:start position:0% Executioner like there's a bunch of like 00:50:15.900 --> 00:50:17.750 align:start position:0% Executioner like there's a bunch of like mechanical<00:50:16.619> changes<00:50:17.040> we<00:50:17.220> can<00:50:17.339> do<00:50:17.460> to<00:50:17.579> the 00:50:17.750 --> 00:50:17.760 align:start position:0% mechanical changes we can do to the 00:50:17.760 --> 00:50:19.130 align:start position:0% mechanical changes we can do to the process<00:50:18.000> and<00:50:18.300> I<00:50:18.599> think<00:50:18.720> they'll<00:50:18.900> be<00:50:19.020> better 00:50:19.130 --> 00:50:19.140 align:start position:0% process and I think they'll be better 00:50:19.140 --> 00:50:21.170 align:start position:0% process and I think they'll be better but<00:50:19.380> that's<00:50:19.560> different<00:50:19.740> from<00:50:20.040> like<00:50:20.220> how<00:50:20.880> do<00:50:21.000> we 00:50:21.170 --> 00:50:21.180 align:start position:0% but that's different from like how do we 00:50:21.180 --> 00:50:22.609 align:start position:0% but that's different from like how do we actually<00:50:21.300> come<00:50:21.540> to<00:50:21.720> consensus<00:50:22.200> on<00:50:22.380> the<00:50:22.500> thing 00:50:22.609 --> 00:50:22.619 align:start position:0% actually come to consensus on the thing 00:50:22.619 --> 00:50:23.990 align:start position:0% actually come to consensus on the thing like<00:50:22.740> whether<00:50:23.040> it's<00:50:23.220> an<00:50:23.339> EIP<00:50:23.579> or<00:50:23.819> the<00:50:23.880> yellow 00:50:23.990 --> 00:50:24.000 align:start position:0% like whether it's an EIP or the yellow 00:50:24.000 --> 00:50:26.450 align:start position:0% like whether it's an EIP or the yellow paper<00:50:24.240> like<00:50:24.540> a<00:50:24.720> consensus<00:50:25.140> spec<00:50:25.319> PR 00:50:26.450 --> 00:50:26.460 align:start position:0% paper like a consensus spec PR 00:50:26.460 --> 00:50:27.530 align:start position:0% paper like a consensus spec PR um you<00:50:26.700> know<00:50:26.760> that's<00:50:26.880> like<00:50:27.119> a<00:50:27.240> marginal 00:50:27.530 --> 00:50:27.540 align:start position:0% um you know that's like a marginal 00:50:27.540 --> 00:50:29.630 align:start position:0% um you know that's like a marginal difference<00:50:27.780> I<00:50:28.319> think<00:50:28.440> that 00:50:29.630 --> 00:50:29.640 align:start position:0% difference I think that 00:50:29.640 --> 00:50:31.069 align:start position:0% difference I think that so<00:50:30.119> one<00:50:30.359> thing<00:50:30.480> I<00:50:30.599> actually<00:50:30.720> really<00:50:30.900> don't 00:50:31.069 --> 00:50:31.079 align:start position:0% so one thing I actually really don't 00:50:31.079 --> 00:50:33.290 align:start position:0% so one thing I actually really don't like<00:50:31.200> about<00:50:31.380> Cortez<00:50:31.800> is<00:50:31.980> that<00:50:32.160> it's<00:50:32.280> calls 00:50:33.290 --> 00:50:33.300 align:start position:0% like about Cortez is that it's calls 00:50:33.300 --> 00:50:35.630 align:start position:0% like about Cortez is that it's calls um like<00:50:34.079> my<00:50:34.260> like<00:50:34.680> and<00:50:34.859> the<00:50:35.099> reason<00:50:35.280> for<00:50:35.520> that 00:50:35.630 --> 00:50:35.640 align:start position:0% um like my like and the reason for that 00:50:35.640 --> 00:50:36.650 align:start position:0% um like my like and the reason for that is<00:50:35.940> like 00:50:36.650 --> 00:50:36.660 align:start position:0% is like 00:50:36.660 --> 00:50:38.510 align:start position:0% is like um calls<00:50:37.140> are<00:50:37.200> hard<00:50:37.380> because<00:50:37.740> for<00:50:38.280> they 00:50:38.510 --> 00:50:38.520 align:start position:0% um calls are hard because for they 00:50:38.520 --> 00:50:39.890 align:start position:0% um calls are hard because for they optimize<00:50:38.880> for<00:50:39.060> a<00:50:39.119> bunch<00:50:39.240> of<00:50:39.359> weird<00:50:39.540> things<00:50:39.720> so 00:50:39.890 --> 00:50:39.900 align:start position:0% optimize for a bunch of weird things so 00:50:39.900 --> 00:50:40.970 align:start position:0% optimize for a bunch of weird things so like<00:50:40.079> the<00:50:40.200> optimize<00:50:40.500> for<00:50:40.619> people<00:50:40.740> who<00:50:40.859> are 00:50:40.970 --> 00:50:40.980 align:start position:0% like the optimize for people who are 00:50:40.980 --> 00:50:43.609 align:start position:0% like the optimize for people who are awake<00:50:41.220> at<00:50:41.400> the<00:50:41.520> time<00:50:41.700> who<00:50:42.180> are<00:50:42.359> like<00:50:42.540> uh<00:50:43.319> good 00:50:43.609 --> 00:50:43.619 align:start position:0% awake at the time who are like uh good 00:50:43.619 --> 00:50:45.829 align:start position:0% awake at the time who are like uh good English<00:50:43.800> speakers<00:50:44.099> who<00:50:44.700> like<00:50:44.940> are<00:50:45.420> very<00:50:45.599> like 00:50:45.829 --> 00:50:45.839 align:start position:0% English speakers who like are very like 00:50:45.839 --> 00:50:47.569 align:start position:0% English speakers who like are very like eloquent<00:50:46.319> and<00:50:46.619> like<00:50:46.740> can<00:50:46.920> like<00:50:47.160> think<00:50:47.339> on 00:50:47.569 --> 00:50:47.579 align:start position:0% eloquent and like can like think on 00:50:47.579 --> 00:50:49.910 align:start position:0% eloquent and like can like think on their<00:50:47.760> feet<00:50:47.940> and<00:50:48.180> and<00:50:48.540> like<00:50:48.839> respond<00:50:49.380> live 00:50:49.910 --> 00:50:49.920 align:start position:0% their feet and and like respond live 00:50:49.920 --> 00:50:51.290 align:start position:0% their feet and and like respond live during<00:50:50.160> the<00:50:50.460> call 00:50:51.290 --> 00:50:51.300 align:start position:0% during the call 00:50:51.300 --> 00:50:52.609 align:start position:0% during the call um<00:50:51.420> I<00:50:51.599> think<00:50:51.780> this<00:50:51.839> and<00:50:52.079> also<00:50:52.380> they're<00:50:52.440> like 00:50:52.609 --> 00:50:52.619 align:start position:0% um I think this and also they're like 00:50:52.619 --> 00:50:54.049 align:start position:0% um I think this and also they're like not<00:50:52.800> very<00:50:52.920> scalable<00:50:53.280> we<00:50:53.460> can't<00:50:53.579> have<00:50:53.700> like<00:50:53.880> 90 00:50:54.049 --> 00:50:54.059 align:start position:0% not very scalable we can't have like 90 00:50:54.059 --> 00:50:56.510 align:start position:0% not very scalable we can't have like 90 people<00:50:54.300> on<00:50:54.480> a<00:50:54.720> call<00:50:55.319> um<00:50:55.440> and<00:50:55.800> so<00:50:55.920> like<00:50:56.280> to<00:50:56.400> your 00:50:56.510 --> 00:50:56.520 align:start position:0% people on a call um and so like to your 00:50:56.520 --> 00:50:57.829 align:start position:0% people on a call um and so like to your point<00:50:56.700> about<00:50:56.819> like<00:50:57.000> having<00:50:57.180> more<00:50:57.420> more<00:50:57.660> of 00:50:57.829 --> 00:50:57.839 align:start position:0% point about like having more more of 00:50:57.839 --> 00:51:00.109 align:start position:0% point about like having more more of like<00:50:57.960> the<00:50:58.200> community<00:50:58.380> involved<00:50:58.920> it's<00:50:59.040> like 00:51:00.109 --> 00:51:00.119 align:start position:0% like the community involved it's like 00:51:00.119 --> 00:51:02.809 align:start position:0% like the community involved it's like that's<00:51:00.780> something<00:51:01.020> where<00:51:01.319> like<00:51:01.559> moving<00:51:02.400> the 00:51:02.809 --> 00:51:02.819 align:start position:0% that's something where like moving the 00:51:02.819 --> 00:51:03.950 align:start position:0% that's something where like moving the calls<00:51:03.119> are<00:51:03.180> good<00:51:03.359> because<00:51:03.480> they<00:51:03.599> give<00:51:03.720> like<00:51:03.839> a 00:51:03.950 --> 00:51:03.960 align:start position:0% calls are good because they give like a 00:51:03.960 --> 00:51:05.390 align:start position:0% calls are good because they give like a forcing<00:51:04.319> function<00:51:04.559> and<00:51:04.740> like<00:51:04.859> some<00:51:04.980> rhythms 00:51:05.390 --> 00:51:05.400 align:start position:0% forcing function and like some rhythms 00:51:05.400 --> 00:51:06.170 align:start position:0% forcing function and like some rhythms like<00:51:05.460> I<00:51:05.640> wouldn't<00:51:05.700> take<00:51:05.880> them<00:51:06.059> away 00:51:06.170 --> 00:51:06.180 align:start position:0% like I wouldn't take them away 00:51:06.180 --> 00:51:08.150 align:start position:0% like I wouldn't take them away completely<00:51:06.599> but<00:51:07.079> moving<00:51:07.440> to<00:51:07.559> be<00:51:07.740> like<00:51:07.920> more 00:51:08.150 --> 00:51:08.160 align:start position:0% completely but moving to be like more 00:51:08.160 --> 00:51:10.849 align:start position:0% completely but moving to be like more async<00:51:08.760> is<00:51:09.000> something<00:51:09.180> I've<00:51:09.599> like<00:51:09.900> I<00:51:10.619> try<00:51:10.740> to 00:51:10.849 --> 00:51:10.859 align:start position:0% async is something I've like I try to 00:51:10.859 --> 00:51:12.410 align:start position:0% async is something I've like I try to think<00:51:10.980> a<00:51:11.160> lot<00:51:11.280> about<00:51:11.400> and<00:51:11.880> you<00:51:12.059> know<00:51:12.119> so<00:51:12.240> for 00:51:12.410 --> 00:51:12.420 align:start position:0% think a lot about and you know so for 00:51:12.420 --> 00:51:14.569 align:start position:0% think a lot about and you know so for Shanghai<00:51:12.780> we<00:51:13.020> have<00:51:13.140> like<00:51:13.319> this<00:51:13.619> uh<00:51:13.800> tag<00:51:14.099> on<00:51:14.280> on 00:51:14.569 --> 00:51:14.579 align:start position:0% Shanghai we have like this uh tag on on 00:51:14.579 --> 00:51:16.910 align:start position:0% Shanghai we have like this uh tag on on these<00:51:14.940> magicians<00:51:15.420> and<00:51:15.660> like<00:51:15.839> you<00:51:16.440> know<00:51:16.500> anyone 00:51:16.910 --> 00:51:16.920 align:start position:0% these magicians and like you know anyone 00:51:16.920 --> 00:51:18.829 align:start position:0% these magicians and like you know anyone can<00:51:17.099> tag<00:51:17.280> their<00:51:17.460> eat<00:51:17.640> there<00:51:17.880> Klein<00:51:18.420> devs<00:51:18.720> can 00:51:18.829 --> 00:51:18.839 align:start position:0% can tag their eat there Klein devs can 00:51:18.839 --> 00:51:20.809 align:start position:0% can tag their eat there Klein devs can review<00:51:18.960> it<00:51:19.200> like<00:51:19.559> I<00:51:19.740> can't<00:51:19.859> force<00:51:20.220> Klein<00:51:20.520> devs 00:51:20.809 --> 00:51:20.819 align:start position:0% review it like I can't force Klein devs 00:51:20.819 --> 00:51:22.069 align:start position:0% review it like I can't force Klein devs to<00:51:20.880> like<00:51:21.000> look<00:51:21.119> at<00:51:21.240> your<00:51:21.359> VIP<00:51:21.599> if<00:51:21.839> they<00:51:21.900> don't 00:51:22.069 --> 00:51:22.079 align:start position:0% to like look at your VIP if they don't 00:51:22.079 --> 00:51:25.010 align:start position:0% to like look at your VIP if they don't want<00:51:22.200> to<00:51:22.319> like<00:51:22.859> you<00:51:23.400> know<00:51:23.480> no<00:51:24.480> one<00:51:24.599> can<00:51:24.780> do<00:51:24.900> that 00:51:25.010 --> 00:51:25.020 align:start position:0% want to like you know no one can do that 00:51:25.020 --> 00:51:26.569 align:start position:0% want to like you know no one can do that but<00:51:25.200> it's<00:51:25.319> like<00:51:25.500> at<00:51:25.920> least<00:51:26.040> there's<00:51:26.280> a<00:51:26.460> list 00:51:26.569 --> 00:51:26.579 align:start position:0% but it's like at least there's a list 00:51:26.579 --> 00:51:28.309 align:start position:0% but it's like at least there's a list and<00:51:26.880> they<00:51:27.059> can<00:51:27.240> scroll<00:51:27.480> through<00:51:27.660> it<00:51:27.900> and<00:51:28.200> like 00:51:28.309 --> 00:51:28.319 align:start position:0% and they can scroll through it and like 00:51:28.319 --> 00:51:29.990 align:start position:0% and they can scroll through it and like if<00:51:28.500> it<00:51:28.619> sounds<00:51:28.740> good<00:51:28.920> to<00:51:29.099> them<00:51:29.220> it<00:51:29.760> might<00:51:29.880> be 00:51:29.990 --> 00:51:30.000 align:start position:0% if it sounds good to them it might be 00:51:30.000 --> 00:51:32.210 align:start position:0% if it sounds good to them it might be like<00:51:30.240> more<00:51:30.660> accessible<00:51:31.260> and<00:51:31.680> maybe<00:51:31.859> you<00:51:32.040> wrote 00:51:32.210 --> 00:51:32.220 align:start position:0% like more accessible and maybe you wrote 00:51:32.220 --> 00:51:34.370 align:start position:0% like more accessible and maybe you wrote it<00:51:32.400> you<00:51:32.520> know<00:51:32.640> at<00:51:32.700> 9am<00:51:33.000> Vietnam<00:51:33.480> time<00:51:33.780> rather 00:51:34.370 --> 00:51:34.380 align:start position:0% it you know at 9am Vietnam time rather 00:51:34.380 --> 00:51:36.710 align:start position:0% it you know at 9am Vietnam time rather than<00:51:34.559> like<00:51:34.800> 4<00:51:35.040> a.m<00:51:35.400> during<00:51:35.579> yakodev<00:51:36.359> awkward 00:51:36.710 --> 00:51:36.720 align:start position:0% than like 4 a.m during yakodev awkward 00:51:36.720 --> 00:51:39.710 align:start position:0% than like 4 a.m during yakodev awkward devs<00:51:37.140> so<00:51:37.559> yeah<00:51:37.680> I<00:51:37.859> think<00:51:38.160> more<00:51:38.760> async<00:51:39.300> is<00:51:39.480> like 00:51:39.710 --> 00:51:39.720 align:start position:0% devs so yeah I think more async is like 00:51:39.720 --> 00:51:42.410 align:start position:0% devs so yeah I think more async is like one<00:51:40.260> actual<00:51:40.740> tick<00:51:41.040> like<00:51:41.400> thing<00:51:41.880> we<00:51:42.119> can<00:51:42.240> do<00:51:42.300> to 00:51:42.410 --> 00:51:42.420 align:start position:0% one actual tick like thing we can do to 00:51:42.420 --> 00:51:44.390 align:start position:0% one actual tick like thing we can do to make<00:51:42.540> the<00:51:42.660> process<00:51:42.900> more<00:51:43.319> open 00:51:44.390 --> 00:51:44.400 align:start position:0% make the process more open 00:51:44.400 --> 00:51:50.530 align:start position:0% make the process more open um<00:51:44.460> yeah 00:51:50.530 --> 00:51:50.540 align:start position:0% 00:51:50.540 --> 00:51:56.510 align:start position:0% into<00:51:51.540> it<00:51:51.720> you<00:51:51.839> don't<00:51:51.960> have<00:51:52.079> to<00:51:52.140> like<00:51:52.260> okay<00:51:52.680> okay 00:51:56.510 --> 00:51:56.520 align:start position:0% 00:51:56.520 --> 00:51:59.270 align:start position:0% what<00:51:56.940> what's<00:51:57.119> the<00:51:57.420> next<00:51:57.540> topic<00:51:58.260> Serge<00:51:58.859> Verge 00:51:59.270 --> 00:51:59.280 align:start position:0% what what's the next topic Serge Verge 00:51:59.280 --> 00:52:02.450 align:start position:0% what what's the next topic Serge Verge Verge<00:51:59.880> all<00:52:00.300> the<00:52:00.420> big<00:52:00.540> stuff<00:52:00.780> so<00:52:01.079> so<00:52:01.440> so<00:52:01.619> so<00:52:01.859> now 00:52:02.450 --> 00:52:02.460 align:start position:0% Verge all the big stuff so so so so now 00:52:02.460 --> 00:52:05.270 align:start position:0% Verge all the big stuff so so so so now that<00:52:02.760> we've<00:52:03.119> talked<00:52:03.780> about<00:52:03.900> how<00:52:04.559> we<00:52:04.859> are<00:52:05.040> going 00:52:05.270 --> 00:52:05.280 align:start position:0% that we've talked about how we are going 00:52:05.280 --> 00:52:09.349 align:start position:0% that we've talked about how we are going to<00:52:05.839> uh<00:52:06.839> to<00:52:07.559> come<00:52:07.680> to<00:52:07.920> consensus<00:52:08.520> on<00:52:08.880> these<00:52:09.180> new 00:52:09.349 --> 00:52:09.359 align:start position:0% to uh to come to consensus on these new 00:52:09.359 --> 00:52:11.270 align:start position:0% to uh to come to consensus on these new upgrades<00:52:09.960> and<00:52:10.200> new<00:52:10.440> things<00:52:10.619> we<00:52:10.980> could<00:52:11.099> maybe 00:52:11.270 --> 00:52:11.280 align:start position:0% upgrades and new things we could maybe 00:52:11.280 --> 00:52:13.670 align:start position:0% upgrades and new things we could maybe talk<00:52:11.640> about<00:52:11.819> the<00:52:12.359> new<00:52:12.900> upgrades<00:52:13.380> and<00:52:13.559> new 00:52:13.670 --> 00:52:13.680 align:start position:0% talk about the new upgrades and new 00:52:13.680 --> 00:52:15.410 align:start position:0% talk about the new upgrades and new things<00:52:13.920> what's<00:52:14.460> your<00:52:14.700> favorite<00:52:14.880> new<00:52:15.059> upgrade 00:52:15.410 --> 00:52:15.420 align:start position:0% things what's your favorite new upgrade 00:52:15.420 --> 00:52:17.710 align:start position:0% things what's your favorite new upgrade it's<00:52:15.780> enough<00:52:15.960> segue<00:52:16.380> for<00:52:16.559> you<00:52:16.680> yeah<00:52:17.099> sure 00:52:17.710 --> 00:52:17.720 align:start position:0% it's enough segue for you yeah sure 00:52:17.720 --> 00:52:19.549 align:start position:0% it's enough segue for you yeah sure hilarious<00:52:18.720> what's<00:52:18.960> your<00:52:19.140> favorite<00:52:19.260> new 00:52:19.549 --> 00:52:19.559 align:start position:0% hilarious what's your favorite new 00:52:19.559 --> 00:52:20.930 align:start position:0% hilarious what's your favorite new upgrade 00:52:20.930 --> 00:52:20.940 align:start position:0% upgrade 00:52:20.940 --> 00:52:33.349 align:start position:0% upgrade um 00:52:33.349 --> 00:52:33.359 align:start position:0% 00:52:33.359 --> 00:52:42.170 align:start position:0% um that<00:52:34.020> that's<00:52:34.380> that's<00:52:34.619> pretty<00:52:34.980> nice 00:52:42.170 --> 00:52:42.180 align:start position:0% 00:52:42.180 --> 00:52:44.569 align:start position:0% I'm<00:52:42.540> okay<00:52:42.839> maybe<00:52:43.079> okay<00:52:43.380> a<00:52:43.680> better<00:52:43.859> question<00:52:44.160> on 00:52:44.569 --> 00:52:44.579 align:start position:0% I'm okay maybe okay a better question on 00:52:44.579 --> 00:52:46.130 align:start position:0% I'm okay maybe okay a better question on like<00:52:44.760> the<00:52:44.940> new<00:52:45.119> upgrades 00:52:46.130 --> 00:52:46.140 align:start position:0% like the new upgrades 00:52:46.140 --> 00:52:48.410 align:start position:0% like the new upgrades um<00:52:46.200> I<00:52:46.319> guess<00:52:46.440> I'm<00:52:46.619> curious<00:52:46.920> like<00:52:47.099> Yeah<00:52:48.059> from 00:52:48.410 --> 00:52:48.420 align:start position:0% um I guess I'm curious like Yeah from 00:52:48.420 --> 00:52:50.990 align:start position:0% um I guess I'm curious like Yeah from from<00:52:49.020> client<00:52:49.440> team's<00:52:49.740> perspective<00:52:50.040> like<00:52:50.400> how 00:52:50.990 --> 00:52:51.000 align:start position:0% from client team's perspective like how 00:52:51.000 --> 00:52:52.490 align:start position:0% from client team's perspective like how much<00:52:51.119> have<00:52:51.300> you<00:52:51.480> been<00:52:51.599> thinking<00:52:51.960> about<00:52:52.200> new 00:52:52.490 --> 00:52:52.500 align:start position:0% much have you been thinking about new 00:52:52.500 --> 00:52:53.990 align:start position:0% much have you been thinking about new upgrades<00:52:52.980> because<00:52:53.160> like<00:52:53.400> everyone<00:52:53.760> on 00:52:53.990 --> 00:52:54.000 align:start position:0% upgrades because like everyone on 00:52:54.000 --> 00:52:55.790 align:start position:0% upgrades because like everyone on Twitter<00:52:54.119> obviously<00:52:54.599> talks<00:52:54.839> about<00:52:54.900> 4844<00:52:55.559> a 00:52:55.790 --> 00:52:55.800 align:start position:0% Twitter obviously talks about 4844 a 00:52:55.800 --> 00:52:57.290 align:start position:0% Twitter obviously talks about 4844 a bunch<00:52:55.920> of<00:52:56.040> people<00:52:56.099> not<00:52:56.400> in<00:52:56.579> fine<00:52:56.760> teams<00:52:57.180> have 00:52:57.290 --> 00:52:57.300 align:start position:0% bunch of people not in fine teams have 00:52:57.300 --> 00:52:58.790 align:start position:0% bunch of people not in fine teams have been<00:52:57.359> contributing<00:52:57.839> a<00:52:58.020> couple<00:52:58.079> incline<00:52:58.500> teams 00:52:58.790 --> 00:52:58.800 align:start position:0% been contributing a couple incline teams 00:52:58.800 --> 00:53:00.230 align:start position:0% been contributing a couple incline teams have<00:52:58.859> as<00:52:59.040> well<00:52:59.160> but<00:52:59.280> like<00:52:59.460> you<00:52:59.819> know<00:52:59.880> mostly 00:53:00.230 --> 00:53:00.240 align:start position:0% have as well but like you know mostly 00:53:00.240 --> 00:53:02.510 align:start position:0% have as well but like you know mostly like<00:53:00.599> we<00:53:00.720> shipped<00:53:00.960> the<00:53:01.079> merge<00:53:01.260> a<00:53:01.380> month<00:53:01.500> ago 00:53:02.510 --> 00:53:02.520 align:start position:0% like we shipped the merge a month ago 00:53:02.520 --> 00:53:05.690 align:start position:0% like we shipped the merge a month ago um<00:53:02.640> you<00:53:02.819> know<00:53:02.940> like<00:53:03.720> it's<00:53:04.200> not<00:53:04.380> a<00:53:04.500> lot<00:53:04.619> of<00:53:04.740> time 00:53:05.690 --> 00:53:05.700 align:start position:0% um you know like it's not a lot of time 00:53:05.700 --> 00:53:07.250 align:start position:0% um you know like it's not a lot of time um<00:53:05.880> so<00:53:06.180> yeah<00:53:06.300> how<00:53:06.480> are<00:53:06.599> y'all<00:53:06.780> thinking<00:53:07.079> about 00:53:07.250 --> 00:53:07.260 align:start position:0% um so yeah how are y'all thinking about 00:53:07.260 --> 00:53:09.109 align:start position:0% um so yeah how are y'all thinking about like<00:53:07.559> what's<00:53:07.740> next<00:53:07.980> or<00:53:08.280> are<00:53:08.520> you<00:53:08.760> trying<00:53:08.940> to 00:53:09.109 --> 00:53:09.119 align:start position:0% like what's next or are you trying to 00:53:09.119 --> 00:53:10.549 align:start position:0% like what's next or are you trying to not<00:53:09.359> think<00:53:09.540> about<00:53:09.660> it<00:53:09.839> as<00:53:09.960> much<00:53:10.140> as<00:53:10.260> possible 00:53:10.549 --> 00:53:10.559 align:start position:0% not think about it as much as possible 00:53:10.559 --> 00:53:13.910 align:start position:0% not think about it as much as possible and<00:53:11.339> you<00:53:12.000> know<00:53:12.079> decompress<00:53:13.079> with<00:53:13.200> emerge<00:53:13.619> yeah 00:53:13.910 --> 00:53:13.920 align:start position:0% and you know decompress with emerge yeah 00:53:13.920 --> 00:53:15.170 align:start position:0% and you know decompress with emerge yeah so<00:53:14.160> I 00:53:15.170 --> 00:53:15.180 align:start position:0% so I 00:53:15.180 --> 00:53:17.809 align:start position:0% so I I<00:53:15.780> kind<00:53:15.900> of<00:53:16.020> think<00:53:16.200> our<00:53:16.619> main<00:53:17.160> responsibility 00:53:17.809 --> 00:53:17.819 align:start position:0% I kind of think our main responsibility 00:53:17.819 --> 00:53:22.730 align:start position:0% I kind of think our main responsibility is<00:53:18.180> our<00:53:18.359> users<00:53:18.720> right<00:53:18.960> now<00:53:19.339> and<00:53:20.339> uh<00:53:20.819> so<00:53:21.180> uh 00:53:22.730 --> 00:53:22.740 align:start position:0% is our users right now and uh so uh 00:53:22.740 --> 00:53:24.890 align:start position:0% is our users right now and uh so uh we<00:53:23.280> have<00:53:23.400> a<00:53:23.579> bunch<00:53:23.760> of<00:53:23.880> upgrades<00:53:24.359> coming<00:53:24.599> up 00:53:24.890 --> 00:53:24.900 align:start position:0% we have a bunch of upgrades coming up 00:53:24.900 --> 00:53:29.390 align:start position:0% we have a bunch of upgrades coming up that<00:53:25.800> oh<00:53:26.220> yeah<00:53:26.400> okay<00:53:26.760> hi 00:53:29.390 --> 00:53:29.400 align:start position:0% that oh yeah okay hi 00:53:29.400 --> 00:53:30.589 align:start position:0% that oh yeah okay hi um 00:53:30.589 --> 00:53:30.599 align:start position:0% um 00:53:30.599 --> 00:53:32.750 align:start position:0% um uh<00:53:31.079> we<00:53:31.200> have<00:53:31.319> a<00:53:31.440> we<00:53:31.680> have<00:53:31.800> a 00:53:32.750 --> 00:53:32.760 align:start position:0% uh we have a we have a 00:53:32.760 --> 00:53:35.990 align:start position:0% uh we have a we have a so<00:53:33.359> forget<00:53:34.160> at<00:53:35.160> least<00:53:35.280> from<00:53:35.460> my<00:53:35.700> perspective 00:53:35.990 --> 00:53:36.000 align:start position:0% so forget at least from my perspective 00:53:36.000 --> 00:53:38.750 align:start position:0% so forget at least from my perspective forget<00:53:36.300> it's<00:53:37.260> the<00:53:37.920> most<00:53:38.099> important<00:53:38.400> thing<00:53:38.579> is 00:53:38.750 --> 00:53:38.760 align:start position:0% forget it's the most important thing is 00:53:38.760 --> 00:53:40.010 align:start position:0% forget it's the most important thing is the<00:53:38.940> current<00:53:39.059> Network 00:53:40.010 --> 00:53:40.020 align:start position:0% the current Network 00:53:40.020 --> 00:53:43.010 align:start position:0% the current Network and<00:53:40.619> it's<00:53:40.859> not<00:53:41.099> the<00:53:41.460> it's<00:53:42.000> not<00:53:42.180> the<00:53:42.359> future<00:53:42.599> and 00:53:43.010 --> 00:53:43.020 align:start position:0% and it's not the it's not the future and 00:53:43.020 --> 00:53:46.730 align:start position:0% and it's not the it's not the future and it's<00:53:43.200> not<00:53:43.500> uh<00:53:43.920> this<00:53:44.220> it<00:53:44.760> wasn't<00:53:45.000> the<00:53:45.300> merge<00:53:45.720> and 00:53:46.730 --> 00:53:46.740 align:start position:0% it's not uh this it wasn't the merge and 00:53:46.740 --> 00:53:47.630 align:start position:0% it's not uh this it wasn't the merge and um 00:53:47.630 --> 00:53:47.640 align:start position:0% um 00:53:47.640 --> 00:53:50.329 align:start position:0% um we<00:53:48.180> want<00:53:48.420> to<00:53:48.540> make<00:53:48.660> sure<00:53:48.900> that<00:53:49.260> the<00:53:50.099> current 00:53:50.329 --> 00:53:50.339 align:start position:0% we want to make sure that the current 00:53:50.339 --> 00:53:52.309 align:start position:0% we want to make sure that the current network<00:53:50.579> runs<00:53:51.119> and<00:53:51.720> the<00:53:51.960> current<00:53:52.079> network 00:53:52.309 --> 00:53:52.319 align:start position:0% network runs and the current network 00:53:52.319 --> 00:53:54.410 align:start position:0% network runs and the current network doesn't<00:53:52.680> go<00:53:52.859> down<00:53:53.040> and<00:53:53.400> it's<00:53:53.520> secure<00:53:53.880> and<00:53:54.180> it's 00:53:54.410 --> 00:53:54.420 align:start position:0% doesn't go down and it's secure and it's 00:53:54.420 --> 00:53:58.069 align:start position:0% doesn't go down and it's secure and it's usable<00:53:55.140> and<00:53:55.619> it's<00:53:55.859> uh<00:53:56.579> decentralized<00:53:57.540> and<00:53:57.960> you 00:53:58.069 --> 00:53:58.079 align:start position:0% usable and it's uh decentralized and you 00:53:58.079 --> 00:54:00.170 align:start position:0% usable and it's uh decentralized and you can<00:53:58.200> run<00:53:58.319> your<00:53:58.559> own<00:53:58.680> node 00:54:00.170 --> 00:54:00.180 align:start position:0% can run your own node 00:54:00.180 --> 00:54:01.130 align:start position:0% can run your own node um 00:54:01.130 --> 00:54:01.140 align:start position:0% um 00:54:01.140 --> 00:54:05.089 align:start position:0% um so<00:54:02.099> uh<00:54:02.700> we<00:54:02.940> have<00:54:03.059> a<00:54:03.240> bunch<00:54:03.420> of<00:54:03.599> uh<00:54:04.440> other<00:54:04.859> things 00:54:05.089 --> 00:54:05.099 align:start position:0% so uh we have a bunch of uh other things 00:54:05.099 --> 00:54:08.030 align:start position:0% so uh we have a bunch of uh other things coming<00:54:05.400> up<00:54:05.579> to<00:54:05.880> improve<00:54:06.559> uh<00:54:07.559> things<00:54:07.740> about 00:54:08.030 --> 00:54:08.040 align:start position:0% coming up to improve uh things about 00:54:08.040 --> 00:54:11.230 align:start position:0% coming up to improve uh things about around<00:54:08.520> the<00:54:08.819> database<00:54:09.180> in<00:54:09.420> gath<00:54:09.780> the<00:54:10.559> the 00:54:11.230 --> 00:54:11.240 align:start position:0% around the database in gath the the 00:54:11.240 --> 00:54:16.130 align:start position:0% around the database in gath the the state<00:54:12.240> the<00:54:13.200> way<00:54:13.500> we<00:54:13.740> store<00:54:14.040> the<00:54:14.280> state<00:54:14.520> and 00:54:16.130 --> 00:54:16.140 align:start position:0% state the way we store the state and 00:54:16.140 --> 00:54:19.250 align:start position:0% state the way we store the state and um<00:54:16.200> so<00:54:17.040> yeah<00:54:17.400> I'm<00:54:17.700> really<00:54:18.660> excited<00:54:19.020> about 00:54:19.250 --> 00:54:19.260 align:start position:0% um so yeah I'm really excited about 00:54:19.260 --> 00:54:21.650 align:start position:0% um so yeah I'm really excited about those<00:54:19.619> and<00:54:20.460> because<00:54:20.760> we've<00:54:21.119> been<00:54:21.300> focusing 00:54:21.650 --> 00:54:21.660 align:start position:0% those and because we've been focusing 00:54:21.660 --> 00:54:23.750 align:start position:0% those and because we've been focusing kind<00:54:21.960> of<00:54:22.079> focusing<00:54:22.440> on<00:54:22.619> those<00:54:22.800> we<00:54:23.579> haven't 00:54:23.750 --> 00:54:23.760 align:start position:0% kind of focusing on those we haven't 00:54:23.760 --> 00:54:27.109 align:start position:0% kind of focusing on those we haven't focused<00:54:24.180> too<00:54:24.359> much<00:54:24.540> on<00:54:24.839> the<00:54:25.020> upcoming<00:54:25.440> eaps 00:54:27.109 --> 00:54:27.119 align:start position:0% focused too much on the upcoming eaps 00:54:27.119 --> 00:54:30.069 align:start position:0% focused too much on the upcoming eaps um 00:54:30.069 --> 00:54:30.079 align:start position:0% 00:54:30.079 --> 00:54:34.609 align:start position:0% okay<00:54:31.079> okay<00:54:31.520> like<00:54:32.520> in<00:54:32.760> general<00:54:32.880> the<00:54:33.180> team<00:54:33.359> uh<00:54:34.020> I 00:54:34.609 --> 00:54:34.619 align:start position:0% okay okay like in general the team uh I 00:54:34.619 --> 00:54:37.790 align:start position:0% okay okay like in general the team uh I I<00:54:34.859> personally<00:54:35.520> also<00:54:36.000> like<00:54:36.480> I<00:54:36.780> I<00:54:37.079> started 00:54:37.790 --> 00:54:37.800 align:start position:0% I personally also like I I started 00:54:37.800 --> 00:54:43.630 align:start position:0% I personally also like I I started implementing<00:54:38.599> 4844<00:54:39.599> in<00:54:39.839> Lighthouse 00:54:43.630 --> 00:54:43.640 align:start position:0% 00:54:43.640 --> 00:54:47.089 align:start position:0% wrong<00:54:44.640> client<00:54:44.940> uh<00:54:45.420> but<00:54:45.720> uh<00:54:46.079> it<00:54:46.319> was<00:54:46.500> it<00:54:46.800> was<00:54:46.980> a 00:54:47.089 --> 00:54:47.099 align:start position:0% wrong client uh but uh it was it was a 00:54:47.099 --> 00:54:49.190 align:start position:0% wrong client uh but uh it was it was a learning<00:54:47.400> experience<00:54:47.760> and<00:54:48.240> I<00:54:48.420> I<00:54:48.660> also<00:54:48.960> worked 00:54:49.190 --> 00:54:49.200 align:start position:0% learning experience and I I also worked 00:54:49.200 --> 00:54:50.569 align:start position:0% learning experience and I I also worked a<00:54:49.260> bit<00:54:49.380> on<00:54:49.500> the<00:54:49.559> Casey<00:54:49.920> Jesus<00:54:50.160> ceremony 00:54:50.569 --> 00:54:50.579 align:start position:0% a bit on the Casey Jesus ceremony 00:54:50.579 --> 00:54:53.809 align:start position:0% a bit on the Casey Jesus ceremony because<00:54:50.819> that<00:54:51.300> was<00:54:51.540> just<00:54:51.780> interesting<00:54:52.260> to<00:54:52.440> me 00:54:53.809 --> 00:54:53.819 align:start position:0% because that was just interesting to me 00:54:53.819 --> 00:54:55.210 align:start position:0% because that was just interesting to me um 00:54:55.210 --> 00:54:55.220 align:start position:0% um 00:54:55.220 --> 00:54:58.130 align:start position:0% um we<00:54:56.220> I<00:54:56.760> think<00:54:56.880> get<00:54:57.119> this<00:54:57.359> in<00:54:57.599> a<00:54:57.720> fortunate 00:54:58.130 --> 00:54:58.140 align:start position:0% we I think get this in a fortunate 00:54:58.140 --> 00:54:59.630 align:start position:0% we I think get this in a fortunate position<00:54:58.319> that<00:54:58.740> we<00:54:58.920> have<00:54:59.040> a<00:54:59.220> lot<00:54:59.280> of<00:54:59.460> outside 00:54:59.630 --> 00:54:59.640 align:start position:0% position that we have a lot of outside 00:54:59.640 --> 00:55:02.569 align:start position:0% position that we have a lot of outside contributions<00:55:00.420> uh<00:55:01.319> so<00:55:01.500> people<00:55:01.740> actually<00:55:02.220> if 00:55:02.569 --> 00:55:02.579 align:start position:0% contributions uh so people actually if 00:55:02.579 --> 00:55:06.230 align:start position:0% contributions uh so people actually if they<00:55:02.760> if<00:55:03.240> they<00:55:03.540> propose<00:55:04.260> an<00:55:04.380> EIP<00:55:04.880> they<00:55:05.880> usually 00:55:06.230 --> 00:55:06.240 align:start position:0% they if they propose an EIP they usually 00:55:06.240 --> 00:55:09.829 align:start position:0% they if they propose an EIP they usually implement<00:55:06.660> it<00:55:06.839> in<00:55:06.960> Geth<00:55:07.319> and<00:55:07.920> so<00:55:08.420> when<00:55:09.420> when 00:55:09.829 --> 00:55:09.839 align:start position:0% implement it in Geth and so when when 00:55:09.839 --> 00:55:12.950 align:start position:0% implement it in Geth and so when when like<00:55:10.559> the<00:55:11.520> time<00:55:11.760> rolls<00:55:12.359> around<00:55:12.480> and<00:55:12.780> we 00:55:12.950 --> 00:55:12.960 align:start position:0% like the time rolls around and we 00:55:12.960 --> 00:55:16.730 align:start position:0% like the time rolls around and we have<00:55:13.140> to<00:55:13.500> uh<00:55:14.280> uh<00:55:15.079> have<00:55:16.079> the<00:55:16.260> implementations 00:55:16.730 --> 00:55:16.740 align:start position:0% have to uh uh have the implementations 00:55:16.740 --> 00:55:19.430 align:start position:0% have to uh uh have the implementations for<00:55:17.040> the<00:55:17.160> eaps<00:55:17.760> we<00:55:18.660> have<00:55:18.780> something<00:55:18.960> to<00:55:19.319> build 00:55:19.430 --> 00:55:19.440 align:start position:0% for the eaps we have something to build 00:55:19.440 --> 00:55:21.410 align:start position:0% for the eaps we have something to build on<00:55:19.619> and 00:55:21.410 --> 00:55:21.420 align:start position:0% on and 00:55:21.420 --> 00:55:23.690 align:start position:0% on and um we're<00:55:22.200> in<00:55:22.440> a<00:55:22.680> very<00:55:22.800> good<00:55:22.980> position<00:55:23.220> there 00:55:23.690 --> 00:55:23.700 align:start position:0% um we're in a very good position there 00:55:23.700 --> 00:55:26.930 align:start position:0% um we're in a very good position there compared<00:55:24.180> to<00:55:24.300> other<00:55:24.480> client<00:55:24.839> teams<00:55:25.200> and<00:55:26.040> so<00:55:26.640> we 00:55:26.930 --> 00:55:26.940 align:start position:0% compared to other client teams and so we 00:55:26.940 --> 00:55:29.950 align:start position:0% compared to other client teams and so we can<00:55:27.119> kind<00:55:27.420> of<00:55:27.540> focus<00:55:27.960> a<00:55:28.380> bit<00:55:28.500> more<00:55:28.740> on 00:55:29.950 --> 00:55:29.960 align:start position:0% can kind of focus a bit more on 00:55:29.960 --> 00:55:33.049 align:start position:0% can kind of focus a bit more on testing<00:55:31.040> making<00:55:32.040> sure<00:55:32.280> that<00:55:32.460> the<00:55:32.579> spec<00:55:32.819> is 00:55:33.049 --> 00:55:33.059 align:start position:0% testing making sure that the spec is 00:55:33.059 --> 00:55:36.589 align:start position:0% testing making sure that the spec is correct<00:55:33.359> all<00:55:34.020> of<00:55:34.200> these<00:55:34.500> things 00:55:36.589 --> 00:55:36.599 align:start position:0% correct all of these things 00:55:36.599 --> 00:55:38.829 align:start position:0% correct all of these things I<00:55:37.140> I<00:55:37.319> think<00:55:37.680> I<00:55:37.859> drifted 00:55:38.829 --> 00:55:38.839 align:start position:0% I I think I drifted 00:55:38.839 --> 00:55:43.010 align:start position:0% I I think I drifted very<00:55:39.839> far<00:55:39.960> from<00:55:40.200> the<00:55:40.380> question<00:55:40.940> yeah<00:55:41.940> cool 00:55:43.010 --> 00:55:43.020 align:start position:0% very far from the question yeah cool 00:55:43.020 --> 00:55:45.170 align:start position:0% very far from the question yeah cool um<00:55:43.079> how<00:55:43.380> we<00:55:43.559> feel<00:55:43.740> about<00:55:43.859> upgrades 00:55:45.170 --> 00:55:45.180 align:start position:0% um how we feel about upgrades 00:55:45.180 --> 00:55:46.730 align:start position:0% um how we feel about upgrades um<00:55:45.300> I<00:55:45.480> think<00:55:45.599> we're<00:55:45.720> generally<00:55:46.020> Keen<00:55:46.319> I<00:55:46.619> think 00:55:46.730 --> 00:55:46.740 align:start position:0% um I think we're generally Keen I think 00:55:46.740 --> 00:55:49.910 align:start position:0% um I think we're generally Keen I think uh<00:55:47.700> definitely<00:55:48.059> Keen<00:55:48.480> for<00:55:49.020> withdrawals<00:55:49.680> which 00:55:49.910 --> 00:55:49.920 align:start position:0% uh definitely Keen for withdrawals which 00:55:49.920 --> 00:55:51.710 align:start position:0% uh definitely Keen for withdrawals which uh<00:55:50.160> Mark<00:55:50.339> is<00:55:50.579> working<00:55:50.760> on 00:55:51.710 --> 00:55:51.720 align:start position:0% uh Mark is working on 00:55:51.720 --> 00:55:54.230 align:start position:0% uh Mark is working on um<00:55:51.900> I<00:55:52.140> I<00:55:52.500> kind<00:55:52.859> of<00:55:52.980> feel<00:55:53.160> like<00:55:53.520> the<00:55:53.760> merge<00:55:54.119> is 00:55:54.230 --> 00:55:54.240 align:start position:0% um I I kind of feel like the merge is 00:55:54.240 --> 00:55:55.490 align:start position:0% um I I kind of feel like the merge is not<00:55:54.420> really<00:55:54.480> finished<00:55:54.720> until<00:55:54.960> we<00:55:55.260> have<00:55:55.380> them 00:55:55.490 --> 00:55:55.500 align:start position:0% not really finished until we have them 00:55:55.500 --> 00:55:56.750 align:start position:0% not really finished until we have them in<00:55:55.680> we<00:55:55.920> kind<00:55:56.040> of<00:55:56.099> have<00:55:56.220> a<00:55:56.400> bit<00:55:56.460> of<00:55:56.579> an 00:55:56.750 --> 00:55:56.760 align:start position:0% in we kind of have a bit of an 00:55:56.760 --> 00:55:58.309 align:start position:0% in we kind of have a bit of an outstanding<00:55:57.240> promise<00:55:57.599> that<00:55:57.780> we're<00:55:57.960> yet<00:55:58.140> to 00:55:58.309 --> 00:55:58.319 align:start position:0% outstanding promise that we're yet to 00:55:58.319 --> 00:56:00.710 align:start position:0% outstanding promise that we're yet to fulfill<00:55:58.680> to<00:55:58.859> the<00:55:59.400> stakers 00:56:00.710 --> 00:56:00.720 align:start position:0% fulfill to the stakers 00:56:00.720 --> 00:56:03.530 align:start position:0% fulfill to the stakers um so<00:56:01.440> definitely<00:56:02.040> Keen<00:56:02.220> to<00:56:02.400> get<00:56:02.520> that<00:56:02.700> one<00:56:02.819> in 00:56:03.530 --> 00:56:03.540 align:start position:0% um so definitely Keen to get that one in 00:56:03.540 --> 00:56:05.510 align:start position:0% um so definitely Keen to get that one in um<00:56:03.599> without<00:56:03.839> even<00:56:04.260> saying<00:56:04.740> like 00:56:05.510 --> 00:56:05.520 align:start position:0% um without even saying like 00:56:05.520 --> 00:56:07.250 align:start position:0% um without even saying like you<00:56:06.059> know<00:56:06.119> what<00:56:06.540> do<00:56:06.660> you<00:56:06.720> want<00:56:06.839> to<00:56:06.960> do<00:56:07.079> after 00:56:07.250 --> 00:56:07.260 align:start position:0% you know what do you want to do after 00:56:07.260 --> 00:56:08.510 align:start position:0% you know what do you want to do after the<00:56:07.500> merge<00:56:07.800> because<00:56:07.920> it's<00:56:08.040> not<00:56:08.220> really<00:56:08.339> after 00:56:08.510 --> 00:56:08.520 align:start position:0% the merge because it's not really after 00:56:08.520 --> 00:56:10.609 align:start position:0% the merge because it's not really after the<00:56:08.760> merge<00:56:09.000> for<00:56:09.059> me<00:56:09.180> until<00:56:09.300> we've<00:56:09.599> done<00:56:09.720> that 00:56:10.609 --> 00:56:10.619 align:start position:0% the merge for me until we've done that 00:56:10.619 --> 00:56:12.770 align:start position:0% the merge for me until we've done that um<00:56:11.160> yeah<00:56:11.579> so<00:56:11.760> Keen<00:56:12.000> to<00:56:12.119> work<00:56:12.180> on<00:56:12.300> that<00:56:12.420> Keen<00:56:12.660> to 00:56:12.770 --> 00:56:12.780 align:start position:0% um yeah so Keen to work on that Keen to 00:56:12.780 --> 00:56:14.089 align:start position:0% um yeah so Keen to work on that Keen to get<00:56:12.839> that<00:56:12.960> in<00:56:13.140> soon<00:56:13.319> definitely<00:56:13.680> Keen<00:56:13.859> to<00:56:14.040> get 00:56:14.089 --> 00:56:14.099 align:start position:0% get that in soon definitely Keen to get 00:56:14.099 --> 00:56:16.730 align:start position:0% get that in soon definitely Keen to get 4844<00:56:14.640> and<00:56:14.940> I<00:56:15.059> think<00:56:15.119> that<00:56:15.240> looks<00:56:15.420> really<00:56:15.540> cool 00:56:16.730 --> 00:56:16.740 align:start position:0% 4844 and I think that looks really cool 00:56:16.740 --> 00:56:19.069 align:start position:0% 4844 and I think that looks really cool um personally<00:56:17.460> not<00:56:17.760> super<00:56:17.940> Keen<00:56:18.359> to<00:56:18.660> rush<00:56:18.900> it 00:56:19.069 --> 00:56:19.079 align:start position:0% um personally not super Keen to rush it 00:56:19.079 --> 00:56:21.890 align:start position:0% um personally not super Keen to rush it I<00:56:19.500> think<00:56:19.559> it'd<00:56:19.980> be<00:56:20.099> nice<00:56:20.280> to<00:56:20.520> have<00:56:20.760> a<00:56:21.480> bit<00:56:21.780> of 00:56:21.890 --> 00:56:21.900 align:start position:0% I think it'd be nice to have a bit of 00:56:21.900 --> 00:56:23.329 align:start position:0% I think it'd be nice to have a bit of time<00:56:22.020> like<00:56:22.319> Maris<00:56:22.740> was<00:56:22.859> saying<00:56:23.040> to<00:56:23.160> kind<00:56:23.280> of 00:56:23.329 --> 00:56:23.339 align:start position:0% time like Maris was saying to kind of 00:56:23.339 --> 00:56:25.069 align:start position:0% time like Maris was saying to kind of watch<00:56:23.460> the<00:56:23.640> network 00:56:25.069 --> 00:56:25.079 align:start position:0% watch the network 00:56:25.079 --> 00:56:27.230 align:start position:0% watch the network um<00:56:25.140> breathe 00:56:27.230 --> 00:56:27.240 align:start position:0% um breathe 00:56:27.240 --> 00:56:30.109 align:start position:0% um breathe um<00:56:27.359> yeah<00:56:28.020> so<00:56:28.680> definitely<00:56:29.400> Keen<00:56:29.640> for<00:56:29.760> upgrades 00:56:30.109 --> 00:56:30.119 align:start position:0% um yeah so definitely Keen for upgrades 00:56:30.119 --> 00:56:35.150 align:start position:0% um yeah so definitely Keen for upgrades sorry 00:56:35.150 --> 00:56:35.160 align:start position:0% 00:56:35.160 --> 00:56:37.790 align:start position:0% yeah<00:56:35.700> yeah<00:56:35.760> that's<00:56:36.180> right 00:56:37.790 --> 00:56:37.800 align:start position:0% yeah yeah that's right 00:56:37.800 --> 00:56:40.069 align:start position:0% yeah yeah that's right um<00:56:37.859> yeah<00:56:38.579> we<00:56:38.760> we<00:56:38.940> have<00:56:39.480> um<00:56:39.480> like<00:56:39.599> Sean's<00:56:39.960> been 00:56:40.069 --> 00:56:40.079 align:start position:0% um yeah we we have um like Sean's been 00:56:40.079 --> 00:56:41.930 align:start position:0% um yeah we we have um like Sean's been working<00:56:40.260> on<00:56:40.500> it<00:56:41.040> um<00:56:41.160> Maris<00:56:41.520> has<00:56:41.700> been<00:56:41.819> working 00:56:41.930 --> 00:56:41.940 align:start position:0% working on it um Maris has been working 00:56:41.940 --> 00:56:43.490 align:start position:0% working on it um Maris has been working on<00:56:42.119> it<00:56:42.180> for<00:56:42.300> Lighthouse 00:56:43.490 --> 00:56:43.500 align:start position:0% on it for Lighthouse 00:56:43.500 --> 00:56:46.430 align:start position:0% on it for Lighthouse um<00:56:43.700> yeah<00:56:44.900> you're<00:56:45.900> gonna<00:56:46.020> put<00:56:46.140> in<00:56:46.260> your<00:56:46.380> time 00:56:46.430 --> 00:56:46.440 align:start position:0% um yeah you're gonna put in your time 00:56:46.440 --> 00:56:48.410 align:start position:0% um yeah you're gonna put in your time sheet<00:56:46.740> man 00:56:48.410 --> 00:56:48.420 align:start position:0% sheet man 00:56:48.420 --> 00:56:50.930 align:start position:0% sheet man um<00:56:48.480> yeah<00:56:48.780> so<00:56:48.960> we're<00:56:49.140> keen<00:56:49.380> I'll<00:56:49.740> uh<00:56:49.980> pass<00:56:50.460> it<00:56:50.819> to 00:56:50.930 --> 00:56:50.940 align:start position:0% um yeah so we're keen I'll uh pass it to 00:56:50.940 --> 00:56:53.170 align:start position:0% um yeah so we're keen I'll uh pass it to the<00:56:51.059> techu 00:56:53.170 --> 00:56:53.180 align:start position:0% the techu 00:56:53.180 --> 00:56:55.849 align:start position:0% the techu yeah<00:56:54.180> I<00:56:54.420> think 00:56:55.849 --> 00:56:55.859 align:start position:0% yeah I think 00:56:55.859 --> 00:56:58.549 align:start position:0% yeah I think I<00:56:56.400> really<00:56:56.579> support<00:56:56.819> Paul's<00:56:57.240> point<00:56:57.420> on<00:56:57.900> the<00:56:58.440> the 00:56:58.549 --> 00:56:58.559 align:start position:0% I really support Paul's point on the the 00:56:58.559 --> 00:57:00.230 align:start position:0% I really support Paul's point on the the next<00:56:58.800> thing<00:56:58.920> we<00:56:59.040> do<00:56:59.160> is<00:56:59.220> withdrawals<00:56:59.760> like 00:57:00.230 --> 00:57:00.240 align:start position:0% next thing we do is withdrawals like 00:57:00.240 --> 00:57:02.630 align:start position:0% next thing we do is withdrawals like it's<00:57:00.780> got<00:57:00.960> to<00:57:01.079> be<00:57:01.200> done<00:57:01.319> I<00:57:01.980> I<00:57:02.160> don't<00:57:02.400> think<00:57:02.520> it's 00:57:02.630 --> 00:57:02.640 align:start position:0% it's got to be done I I don't think it's 00:57:02.640 --> 00:57:04.730 align:start position:0% it's got to be done I I don't think it's reasonable<00:57:03.059> to<00:57:03.240> put<00:57:03.420> in<00:57:03.599> bigger<00:57:04.260> things<00:57:04.440> that 00:57:04.730 --> 00:57:04.740 align:start position:0% reasonable to put in bigger things that 00:57:04.740 --> 00:57:05.750 align:start position:0% reasonable to put in bigger things that are<00:57:04.859> then<00:57:04.980> going<00:57:05.160> to<00:57:05.280> delay<00:57:05.520> getting 00:57:05.750 --> 00:57:05.760 align:start position:0% are then going to delay getting 00:57:05.760 --> 00:57:08.030 align:start position:0% are then going to delay getting withdrawals<00:57:06.300> out<00:57:06.480> we<00:57:06.900> made<00:57:07.020> a<00:57:07.200> promise<00:57:07.440> we 00:57:08.030 --> 00:57:08.040 align:start position:0% withdrawals out we made a promise we 00:57:08.040 --> 00:57:09.710 align:start position:0% withdrawals out we made a promise we shirked<00:57:08.460> on<00:57:08.520> the<00:57:08.640> promise<00:57:08.880> a<00:57:09.119> bit<00:57:09.240> and<00:57:09.599> you 00:57:09.710 --> 00:57:09.720 align:start position:0% shirked on the promise a bit and you 00:57:09.720 --> 00:57:10.910 align:start position:0% shirked on the promise a bit and you were<00:57:09.839> all<00:57:09.960> very<00:57:10.079> forgiving<00:57:10.380> because<00:57:10.619> we<00:57:10.800> got 00:57:10.910 --> 00:57:10.920 align:start position:0% were all very forgiving because we got 00:57:10.920 --> 00:57:12.650 align:start position:0% were all very forgiving because we got the<00:57:11.040> merge<00:57:11.339> sooner<00:57:11.700> and<00:57:12.240> now<00:57:12.359> we're<00:57:12.480> going<00:57:12.599> to 00:57:12.650 --> 00:57:12.660 align:start position:0% the merge sooner and now we're going to 00:57:12.660 --> 00:57:14.089 align:start position:0% the merge sooner and now we're going to deliver<00:57:12.780> the<00:57:13.020> promise<00:57:13.260> we've<00:57:13.680> got<00:57:13.859> to<00:57:13.980> come 00:57:14.089 --> 00:57:14.099 align:start position:0% deliver the promise we've got to come 00:57:14.099 --> 00:57:15.290 align:start position:0% deliver the promise we've got to come through<00:57:14.220> on<00:57:14.400> that 00:57:15.290 --> 00:57:15.300 align:start position:0% through on that 00:57:15.300 --> 00:57:16.549 align:start position:0% through on that um<00:57:15.420> but<00:57:15.660> I<00:57:15.720> think<00:57:15.839> the<00:57:15.960> thing<00:57:16.140> that<00:57:16.319> really 00:57:16.549 --> 00:57:16.559 align:start position:0% um but I think the thing that really 00:57:16.559 --> 00:57:18.049 align:start position:0% um but I think the thing that really comes<00:57:16.859> after<00:57:16.920> the<00:57:17.160> merge<00:57:17.460> is<00:57:17.579> the<00:57:17.700> use<00:57:17.880> of 00:57:18.049 --> 00:57:18.059 align:start position:0% comes after the merge is the use of 00:57:18.059 --> 00:57:19.730 align:start position:0% comes after the merge is the use of support<00:57:18.180> for<00:57:18.599> the<00:57:18.720> merge<00:57:19.020> and<00:57:19.559> the 00:57:19.730 --> 00:57:19.740 align:start position:0% support for the merge and the 00:57:19.740 --> 00:57:21.290 align:start position:0% support for the merge and the optimization<00:57:20.280> and<00:57:20.579> the<00:57:20.700> cleanup<00:57:21.000> and<00:57:21.180> the 00:57:21.290 --> 00:57:21.300 align:start position:0% optimization and the cleanup and the 00:57:21.300 --> 00:57:22.730 align:start position:0% optimization and the cleanup and the learning<00:57:21.540> now<00:57:21.720> that<00:57:21.900> we're<00:57:22.020> actually<00:57:22.260> seeing 00:57:22.730 --> 00:57:22.740 align:start position:0% learning now that we're actually seeing 00:57:22.740 --> 00:57:25.130 align:start position:0% learning now that we're actually seeing it<00:57:22.920> in<00:57:23.220> the<00:57:23.339> real<00:57:23.460> world<00:57:23.640> for<00:57:24.119> real<00:57:24.300> there's<00:57:24.900> a 00:57:25.130 --> 00:57:25.140 align:start position:0% it in the real world for real there's a 00:57:25.140 --> 00:57:26.809 align:start position:0% it in the real world for real there's a whole<00:57:25.260> heap<00:57:25.619> of<00:57:25.680> stuff<00:57:25.859> that<00:57:26.220> we<00:57:26.339> can<00:57:26.460> now<00:57:26.579> go 00:57:26.809 --> 00:57:26.819 align:start position:0% whole heap of stuff that we can now go 00:57:26.819 --> 00:57:29.030 align:start position:0% whole heap of stuff that we can now go oh<00:57:27.359> we<00:57:28.079> should<00:57:28.260> make<00:57:28.380> this<00:57:28.559> better<00:57:28.680> and<00:57:28.920> it's 00:57:29.030 --> 00:57:29.040 align:start position:0% oh we should make this better and it's 00:57:29.040 --> 00:57:30.410 align:start position:0% oh we should make this better and it's not<00:57:29.220> going<00:57:29.339> to<00:57:29.460> be<00:57:29.460> protocol<00:57:29.819> upgrades<00:57:30.240> it's 00:57:30.410 --> 00:57:30.420 align:start position:0% not going to be protocol upgrades it's 00:57:30.420 --> 00:57:32.089 align:start position:0% not going to be protocol upgrades it's just<00:57:30.599> client<00:57:30.900> Improvement<00:57:31.260> and<00:57:31.440> so<00:57:31.619> on<00:57:31.740> so 00:57:32.089 --> 00:57:32.099 align:start position:0% just client Improvement and so on so 00:57:32.099 --> 00:57:33.109 align:start position:0% just client Improvement and so on so that's<00:57:32.220> going<00:57:32.400> to<00:57:32.460> take<00:57:32.579> a<00:57:32.640> good<00:57:32.760> chunk<00:57:32.940> of 00:57:33.109 --> 00:57:33.119 align:start position:0% that's going to take a good chunk of 00:57:33.119 --> 00:57:36.109 align:start position:0% that's going to take a good chunk of time<00:57:33.300> but<00:57:34.020> I<00:57:34.200> think<00:57:34.319> we<00:57:34.559> can 00:57:36.109 --> 00:57:36.119 align:start position:0% time but I think we can 00:57:36.119 --> 00:57:37.790 align:start position:0% time but I think we can um<00:57:36.180> start<00:57:36.480> looking<00:57:36.780> at<00:57:37.079> a<00:57:37.440> bunch<00:57:37.559> of<00:57:37.680> other 00:57:37.790 --> 00:57:37.800 align:start position:0% um start looking at a bunch of other 00:57:37.800 --> 00:57:39.710 align:start position:0% um start looking at a bunch of other things<00:57:38.040> as<00:57:38.220> well<00:57:38.339> and<00:57:38.520> so<00:57:38.640> I<00:57:38.760> think<00:57:38.819> 4844<00:57:39.420> is 00:57:39.710 --> 00:57:39.720 align:start position:0% things as well and so I think 4844 is 00:57:39.720 --> 00:57:42.230 align:start position:0% things as well and so I think 4844 is probably<00:57:39.900> getting<00:57:40.200> the<00:57:40.920> The<00:57:41.220> Lion's<00:57:41.880> Share<00:57:42.119> of 00:57:42.230 --> 00:57:42.240 align:start position:0% probably getting the The Lion's Share of 00:57:42.240 --> 00:57:43.790 align:start position:0% probably getting the The Lion's Share of attention<00:57:42.540> of<00:57:42.960> the<00:57:43.200> next<00:57:43.260> big<00:57:43.500> thing<00:57:43.619> after 00:57:43.790 --> 00:57:43.800 align:start position:0% attention of the next big thing after 00:57:43.800 --> 00:57:46.370 align:start position:0% attention of the next big thing after withdrawals 00:57:46.370 --> 00:57:46.380 align:start position:0% withdrawals 00:57:46.380 --> 00:57:48.410 align:start position:0% withdrawals yeah<00:57:46.859> I<00:57:47.220> think<00:57:47.400> that<00:57:47.579> withdrawals<00:57:48.180> are 00:57:48.410 --> 00:57:48.420 align:start position:0% yeah I think that withdrawals are 00:57:48.420 --> 00:57:50.630 align:start position:0% yeah I think that withdrawals are absolutely<00:57:48.900> must<00:57:49.319> and<00:57:49.800> absolutely<00:57:50.280> the<00:57:50.460> most 00:57:50.630 --> 00:57:50.640 align:start position:0% absolutely must and absolutely the most 00:57:50.640 --> 00:57:52.190 align:start position:0% absolutely must and absolutely the most important<00:57:51.000> thing<00:57:51.180> to<00:57:51.359> deliver<00:57:51.540> at<00:57:51.960> the<00:57:52.079> same 00:57:52.190 --> 00:57:52.200 align:start position:0% important thing to deliver at the same 00:57:52.200 --> 00:57:55.250 align:start position:0% important thing to deliver at the same time<00:57:52.380> 4844<00:57:53.059> sounds<00:57:54.059> so<00:57:54.420> interesting<00:57:54.839> that<00:57:55.079> it 00:57:55.250 --> 00:57:55.260 align:start position:0% time 4844 sounds so interesting that it 00:57:55.260 --> 00:57:57.650 align:start position:0% time 4844 sounds so interesting that it starts<00:57:55.619> distill<00:57:56.040> the<00:57:56.220> Thunder<00:57:56.400> and<00:57:57.000> and<00:57:57.480> I 00:57:57.650 --> 00:57:57.660 align:start position:0% starts distill the Thunder and and I 00:57:57.660 --> 00:57:59.750 align:start position:0% starts distill the Thunder and and I think<00:57:57.780> this<00:57:57.900> may<00:57:58.200> be<00:57:58.319> even<00:57:58.859> it's<00:57:59.160> it's<00:57:59.400> a<00:57:59.640> bit 00:57:59.750 --> 00:57:59.760 align:start position:0% think this may be even it's it's a bit 00:57:59.760 --> 00:58:06.290 align:start position:0% think this may be even it's it's a bit dangerous<00:58:00.180> we<00:58:00.900> should 00:58:06.290 --> 00:58:06.300 align:start position:0% 00:58:06.300 --> 00:58:07.910 align:start position:0% very<00:58:06.900> brave<00:58:07.140> man<00:58:07.319> sitting<00:58:07.619> between<00:58:07.680> photos 00:58:07.910 --> 00:58:07.920 align:start position:0% very brave man sitting between photos 00:58:07.920 --> 00:58:12.829 align:start position:0% very brave man sitting between photos yeah<00:58:08.819> exactly<00:58:10.040> uh<00:58:11.040> so<00:58:11.940> so<00:58:12.300> yeah<00:58:12.480> that's<00:58:12.660> that's 00:58:12.829 --> 00:58:12.839 align:start position:0% yeah exactly uh so so yeah that's that's 00:58:12.839 --> 00:58:14.690 align:start position:0% yeah exactly uh so so yeah that's that's why<00:58:13.020> it's<00:58:13.200> so<00:58:13.440> interesting<00:58:13.859> because<00:58:14.220> there's 00:58:14.690 --> 00:58:14.700 align:start position:0% why it's so interesting because there's 00:58:14.700 --> 00:58:17.870 align:start position:0% why it's so interesting because there's people<00:58:15.319> are<00:58:16.319> so<00:58:16.500> convincing<00:58:17.099> in<00:58:17.400> delivering 00:58:17.870 --> 00:58:17.880 align:start position:0% people are so convincing in delivering 00:58:17.880 --> 00:58:19.730 align:start position:0% people are so convincing in delivering those<00:58:18.119> Visions<00:58:18.540> uh 00:58:19.730 --> 00:58:19.740 align:start position:0% those Visions uh 00:58:19.740 --> 00:58:22.309 align:start position:0% those Visions uh yeah<00:58:20.400> I<00:58:20.579> think<00:58:20.760> that's<00:58:21.000> uh<00:58:21.480> coming<00:58:21.900> back<00:58:22.079> to 00:58:22.309 --> 00:58:22.319 align:start position:0% yeah I think that's uh coming back to 00:58:22.319 --> 00:58:24.410 align:start position:0% yeah I think that's uh coming back to her<00:58:22.500> Netherlands<00:58:23.280> team<00:58:23.460> thinks<00:58:23.940> about<00:58:24.119> the 00:58:24.410 --> 00:58:24.420 align:start position:0% her Netherlands team thinks about the 00:58:24.420 --> 00:58:26.809 align:start position:0% her Netherlands team thinks about the next<00:58:24.660> delivery<00:58:25.140> I<00:58:25.500> almost<00:58:25.680> would<00:58:25.980> like<00:58:26.160> to<00:58:26.339> to 00:58:26.809 --> 00:58:26.819 align:start position:0% next delivery I almost would like to to 00:58:26.819 --> 00:58:28.970 align:start position:0% next delivery I almost would like to to activate<00:58:27.180> Daniel<00:58:27.599> here<00:58:27.960> to<00:58:28.200> tell<00:58:28.380> about<00:58:28.619> his 00:58:28.970 --> 00:58:28.980 align:start position:0% activate Daniel here to tell about his 00:58:28.980 --> 00:58:33.049 align:start position:0% activate Daniel here to tell about his like<00:58:29.280> plan<00:58:29.520> of<00:58:29.819> of<00:58:30.240> delivering<00:58:30.780> them 00:58:33.049 --> 00:58:33.059 align:start position:0% 00:58:33.059 --> 00:58:35.809 align:start position:0% so<00:58:33.720> I<00:58:34.020> think<00:58:34.200> it's<00:58:34.440> uh<00:58:34.800> in<00:58:35.099> our<00:58:35.220> case<00:58:35.460> very 00:58:35.809 --> 00:58:35.819 align:start position:0% so I think it's uh in our case very 00:58:35.819 --> 00:58:37.970 align:start position:0% so I think it's uh in our case very similar<00:58:36.180> what<00:58:36.660> I<00:58:37.200> just<00:58:37.380> heard<00:58:37.559> from<00:58:37.799> other 00:58:37.970 --> 00:58:37.980 align:start position:0% similar what I just heard from other 00:58:37.980 --> 00:58:40.250 align:start position:0% similar what I just heard from other teams<00:58:38.400> so<00:58:38.819> you<00:58:39.359> right<00:58:39.599> now<00:58:39.720> I<00:58:39.839> would<00:58:39.900> like<00:58:40.079> to 00:58:40.250 --> 00:58:40.260 align:start position:0% teams so you right now I would like to 00:58:40.260 --> 00:58:42.470 align:start position:0% teams so you right now I would like to relax<00:58:41.099> a<00:58:41.400> little<00:58:41.520> bit<00:58:41.640> and<00:58:41.880> focus<00:58:42.240> on 00:58:42.470 --> 00:58:42.480 align:start position:0% relax a little bit and focus on 00:58:42.480 --> 00:58:44.990 align:start position:0% relax a little bit and focus on improving<00:58:43.440> our<00:58:43.619> client<00:58:43.980> yeah<00:58:44.280> so<00:58:44.819> the 00:58:44.990 --> 00:58:45.000 align:start position:0% improving our client yeah so the 00:58:45.000 --> 00:58:47.030 align:start position:0% improving our client yeah so the marriage<00:58:45.299> was<00:58:45.599> extremely<00:58:46.200> stressful<00:58:46.680> to<00:58:46.859> be 00:58:47.030 --> 00:58:47.040 align:start position:0% marriage was extremely stressful to be 00:58:47.040 --> 00:58:48.430 align:start position:0% marriage was extremely stressful to be honest<00:58:47.220> for<00:58:47.400> the<00:58:47.579> whole<00:58:47.700> team 00:58:48.430 --> 00:58:48.440 align:start position:0% honest for the whole team 00:58:48.440 --> 00:58:53.390 align:start position:0% honest for the whole team and<00:58:49.440> now<00:58:50.220> people<00:58:50.579> want<00:58:51.180> to<00:58:51.359> do<00:58:51.839> things<00:58:52.740> that 00:58:53.390 --> 00:58:53.400 align:start position:0% and now people want to do things that 00:58:53.400 --> 00:58:56.450 align:start position:0% and now people want to do things that you<00:58:53.700> know<00:58:53.760> you<00:58:54.119> know<00:58:54.299> let's<00:58:55.020> say<00:58:55.200> slower<00:58:56.160> a 00:58:56.450 --> 00:58:56.460 align:start position:0% you know you know let's say slower a 00:58:56.460 --> 00:58:59.150 align:start position:0% you know you know let's say slower a slower<00:58:56.819> Pace<00:58:57.059> yeah<00:58:57.359> and<00:58:58.319> additionally<00:58:58.799> we 00:58:59.150 --> 00:58:59.160 align:start position:0% slower Pace yeah and additionally we 00:58:59.160 --> 00:59:00.589 align:start position:0% slower Pace yeah and additionally we would<00:58:59.339> like<00:58:59.460> to<00:58:59.579> clean<00:58:59.760> up<00:59:00.000> a<00:59:00.180> little<00:59:00.240> bit<00:59:00.420> Yeah 00:59:00.589 --> 00:59:00.599 align:start position:0% would like to clean up a little bit Yeah 00:59:00.599 --> 00:59:02.809 align:start position:0% would like to clean up a little bit Yeah because<00:59:00.839> there<00:59:01.079> was<00:59:01.200> no<00:59:01.440> time 00:59:02.809 --> 00:59:02.819 align:start position:0% because there was no time 00:59:02.819 --> 00:59:04.370 align:start position:0% because there was no time um I<00:59:03.299> know<00:59:03.420> I<00:59:03.599> don't<00:59:03.780> know<00:59:03.900> if<00:59:03.960> you<00:59:04.079> are<00:59:04.200> aware 00:59:04.370 --> 00:59:04.380 align:start position:0% um I know I don't know if you are aware 00:59:04.380 --> 00:59:06.049 align:start position:0% um I know I don't know if you are aware but<00:59:04.619> like<00:59:04.799> never<00:59:05.040> mind<00:59:05.280> a<00:59:05.400> few<00:59:05.460> months<00:59:05.700> ago<00:59:05.819> it 00:59:06.049 --> 00:59:06.059 align:start position:0% but like never mind a few months ago it 00:59:06.059 --> 00:59:08.870 align:start position:0% but like never mind a few months ago it was<00:59:06.180> completely<00:59:06.480> different<00:59:06.799> uh<00:59:07.799> Team<00:59:08.220> it<00:59:08.640> was 00:59:08.870 --> 00:59:08.880 align:start position:0% was completely different uh Team it was 00:59:08.880 --> 00:59:11.690 align:start position:0% was completely different uh Team it was undersized<00:59:09.839> very<00:59:10.200> small<00:59:10.440> at<00:59:11.400> some<00:59:11.579> point 00:59:11.690 --> 00:59:11.700 align:start position:0% undersized very small at some point 00:59:11.700 --> 00:59:13.789 align:start position:0% undersized very small at some point there<00:59:12.000> was<00:59:12.119> only<00:59:12.240> one<00:59:12.480> guy<00:59:12.660> Marek<00:59:13.260> working<00:59:13.559> on 00:59:13.789 --> 00:59:13.799 align:start position:0% there was only one guy Marek working on 00:59:13.799 --> 00:59:16.730 align:start position:0% there was only one guy Marek working on the<00:59:13.980> merge<00:59:14.280> which<00:59:14.760> was<00:59:14.940> crazy<00:59:15.299> and<00:59:16.140> you<00:59:16.440> know<00:59:16.559> I 00:59:16.730 --> 00:59:16.740 align:start position:0% the merge which was crazy and you know I 00:59:16.740 --> 00:59:18.710 align:start position:0% the merge which was crazy and you know I was<00:59:16.859> really<00:59:17.040> sorry<00:59:17.280> when<00:59:17.520> I<00:59:17.700> joined<00:59:17.940> and<00:59:18.059> I<00:59:18.240> you 00:59:18.710 --> 00:59:18.720 align:start position:0% was really sorry when I joined and I you 00:59:18.720 --> 00:59:21.650 align:start position:0% was really sorry when I joined and I you know<00:59:18.839> uh<00:59:19.680> met<00:59:20.280> my<00:59:20.460> recognized<00:59:21.000> okay<00:59:21.180> we<00:59:21.540> have 00:59:21.650 --> 00:59:21.660 align:start position:0% know uh met my recognized okay we have 00:59:21.660 --> 00:59:23.809 align:start position:0% know uh met my recognized okay we have to<00:59:21.780> do<00:59:21.900> something<00:59:22.079> with<00:59:22.380> that<00:59:22.559> and<00:59:23.400> yeah<00:59:23.640> now 00:59:23.809 --> 00:59:23.819 align:start position:0% to do something with that and yeah now 00:59:23.819 --> 00:59:25.309 align:start position:0% to do something with that and yeah now it's<00:59:24.059> we<00:59:24.420> are<00:59:24.599> in<00:59:24.720> a<00:59:24.839> completely<00:59:25.079> different 00:59:25.309 --> 00:59:25.319 align:start position:0% it's we are in a completely different 00:59:25.319 --> 00:59:28.250 align:start position:0% it's we are in a completely different State<00:59:25.619> uh<00:59:26.520> we<00:59:26.700> can<00:59:27.000> you<00:59:27.420> know<00:59:27.540> improve<00:59:28.020> our 00:59:28.250 --> 00:59:28.260 align:start position:0% State uh we can you know improve our 00:59:28.260 --> 00:59:29.990 align:start position:0% State uh we can you know improve our client<00:59:28.500> a<00:59:28.740> lot<00:59:28.859> we<00:59:29.339> have<00:59:29.520> a<00:59:29.640> lot<00:59:29.760> of<00:59:29.819> things 00:59:29.990 --> 00:59:30.000 align:start position:0% client a lot we have a lot of things 00:59:30.000 --> 00:59:32.089 align:start position:0% client a lot we have a lot of things that<00:59:30.240> actually<00:59:30.420> we<00:59:30.660> are<00:59:30.900> excited<00:59:31.319> about<00:59:31.500> and 00:59:32.089 --> 00:59:32.099 align:start position:0% that actually we are excited about and 00:59:32.099 --> 00:59:34.130 align:start position:0% that actually we are excited about and they<00:59:32.280> are<00:59:32.400> not<00:59:32.520> enough<00:59:33.240> I<00:59:33.780> would<00:59:33.960> say 00:59:34.130 --> 00:59:34.140 align:start position:0% they are not enough I would say 00:59:34.140 --> 00:59:36.650 align:start position:0% they are not enough I would say one-to-one<00:59:34.980> related<00:59:35.280> to<00:59:35.520> to<00:59:35.700> Shanghai<00:59:36.180> these 00:59:36.650 --> 00:59:36.660 align:start position:0% one-to-one related to to Shanghai these 00:59:36.660 --> 00:59:38.270 align:start position:0% one-to-one related to to Shanghai these are<00:59:36.780> the<00:59:36.900> things<00:59:37.020> like<00:59:37.319> human<00:59:37.500> yeah<00:59:38.040> like 00:59:38.270 --> 00:59:38.280 align:start position:0% are the things like human yeah like 00:59:38.280 --> 00:59:40.190 align:start position:0% are the things like human yeah like database<00:59:38.640> Improvement<00:59:39.059> our<00:59:39.720> sync 00:59:40.190 --> 00:59:40.200 align:start position:0% database Improvement our sync 00:59:40.200 --> 00:59:42.890 align:start position:0% database Improvement our sync Improvement<00:59:40.559> you<00:59:40.859> know<00:59:40.980> our<00:59:41.880> robustness<00:59:42.660> of 00:59:42.890 --> 00:59:42.900 align:start position:0% Improvement you know our robustness of 00:59:42.900 --> 00:59:44.750 align:start position:0% Improvement you know our robustness of the<00:59:43.020> clients<00:59:43.380> these<00:59:43.859> are<00:59:43.920> the<00:59:44.040> things<00:59:44.280> that 00:59:44.750 --> 00:59:44.760 align:start position:0% the clients these are the things that 00:59:44.760 --> 00:59:47.270 align:start position:0% the clients these are the things that maybe<00:59:44.940> are<00:59:45.420> not<00:59:45.599> so<00:59:45.839> excited<00:59:46.380> exciting<00:59:47.040> for 00:59:47.270 --> 00:59:47.280 align:start position:0% maybe are not so excited exciting for 00:59:47.280 --> 00:59:49.190 align:start position:0% maybe are not so excited exciting for the<00:59:47.460> community<00:59:47.579> but<00:59:48.420> they're<00:59:48.599> exciting<00:59:49.020> for 00:59:49.190 --> 00:59:49.200 align:start position:0% the community but they're exciting for 00:59:49.200 --> 00:59:51.890 align:start position:0% the community but they're exciting for us<00:59:49.440> and<00:59:50.400> that's<00:59:50.640> we<00:59:51.059> are<00:59:51.240> mostly<00:59:51.599> are<00:59:51.780> talking 00:59:51.890 --> 00:59:51.900 align:start position:0% us and that's we are mostly are talking 00:59:51.900 --> 00:59:53.329 align:start position:0% us and that's we are mostly are talking about<00:59:52.079> right<00:59:52.380> now<00:59:52.619> and<00:59:52.980> there<00:59:53.099> are<00:59:53.160> also 00:59:53.329 --> 00:59:53.339 align:start position:0% about right now and there are also 00:59:53.339 --> 00:59:55.730 align:start position:0% about right now and there are also things<00:59:53.520> like<00:59:53.700> you<00:59:53.940> know<00:59:54.000> documentation<00:59:54.740> uh 00:59:55.730 --> 00:59:55.740 align:start position:0% things like you know documentation uh 00:59:55.740 --> 00:59:58.069 align:start position:0% things like you know documentation uh Community<00:59:56.640> Support<00:59:56.940> user<00:59:57.480> support<00:59:57.599> these<00:59:57.960> are 00:59:58.069 --> 00:59:58.079 align:start position:0% Community Support user support these are 00:59:58.079 --> 01:00:00.049 align:start position:0% Community Support user support these are things<00:59:58.200> that<00:59:58.500> didn't<00:59:58.740> work<00:59:59.099> well<00:59:59.460> in<00:59:59.819> the<00:59:59.940> past 01:00:00.049 --> 01:00:00.059 align:start position:0% things that didn't work well in the past 01:00:00.059 --> 01:00:02.270 align:start position:0% things that didn't work well in the past and<01:00:00.780> I<01:00:01.020> think<01:00:01.140> in<01:00:01.319> general<01:00:01.440> it<01:00:01.980> should<01:00:02.160> be 01:00:02.270 --> 01:00:02.280 align:start position:0% and I think in general it should be 01:00:02.280 --> 01:00:05.089 align:start position:0% and I think in general it should be improved<01:00:02.700> not<01:00:03.359> only<01:00:03.480> in<01:00:03.839> nethermine<01:00:04.440> but<01:00:04.740> in 01:00:05.089 --> 01:00:05.099 align:start position:0% improved not only in nethermine but in 01:00:05.099 --> 01:00:07.490 align:start position:0% improved not only in nethermine but in the<01:00:05.280> whole<01:00:05.400> Community<01:00:05.640> yeah<01:00:06.059> so<01:00:06.839> this<01:00:07.020> is<01:00:07.200> what 01:00:07.490 --> 01:00:07.500 align:start position:0% the whole Community yeah so this is what 01:00:07.500 --> 01:00:10.130 align:start position:0% the whole Community yeah so this is what actually<01:00:07.799> excites<01:00:08.339> us<01:00:08.460> right<01:00:09.119> now<01:00:09.299> and<01:00:09.960> in 01:00:10.130 --> 01:00:10.140 align:start position:0% actually excites us right now and in 01:00:10.140 --> 01:00:12.230 align:start position:0% actually excites us right now and in terms<01:00:10.380> of<01:00:10.440> particular<01:00:11.040> eips<01:00:11.460> we<01:00:12.059> already 01:00:12.230 --> 01:00:12.240 align:start position:0% terms of particular eips we already 01:00:12.240 --> 01:00:14.690 align:start position:0% terms of particular eips we already started<01:00:12.660> you<01:00:12.839> know<01:00:12.960> investigations<01:00:13.500> but<01:00:13.980> you 01:00:14.690 --> 01:00:14.700 align:start position:0% started you know investigations but you 01:00:14.700 --> 01:00:17.750 align:start position:0% started you know investigations but you know<01:00:15.240> taking<01:00:15.780> it<01:00:16.020> slowly<01:00:16.500> you<01:00:17.220> know<01:00:17.339> have<01:00:17.579> fun 01:00:17.750 --> 01:00:17.760 align:start position:0% know taking it slowly you know have fun 01:00:17.760 --> 01:00:20.990 align:start position:0% know taking it slowly you know have fun with<01:00:18.000> it<01:00:18.180> like<01:00:18.720> four<01:00:19.020> eight<01:00:19.380> four<01:00:19.559> four<01:00:19.799> is<01:00:20.579> you 01:00:20.990 --> 01:00:21.000 align:start position:0% with it like four eight four four is you 01:00:21.000 --> 01:00:22.609 align:start position:0% with it like four eight four four is you know<01:00:21.119> there<01:00:21.240> is<01:00:21.420> one<01:00:21.720> guy<01:00:21.839> working<01:00:22.140> from<01:00:22.440> our 01:00:22.609 --> 01:00:22.619 align:start position:0% know there is one guy working from our 01:00:22.619 --> 01:00:24.289 align:start position:0% know there is one guy working from our team<01:00:22.859> that's<01:00:23.160> I<01:00:23.520> see<01:00:23.700> that<01:00:23.880> he's<01:00:24.059> really 01:00:24.289 --> 01:00:24.299 align:start position:0% team that's I see that he's really 01:00:24.299 --> 01:00:27.170 align:start position:0% team that's I see that he's really excited<01:00:24.720> about<01:00:24.900> it<01:00:25.140> that's<01:00:25.799> cool<01:00:26.099> there<01:00:26.760> is<01:00:26.940> we 01:00:27.170 --> 01:00:27.180 align:start position:0% excited about it that's cool there is we 01:00:27.180 --> 01:00:28.849 align:start position:0% excited about it that's cool there is we already<01:00:27.299> started<01:00:27.720> with<01:00:27.960> travels<01:00:28.619> we<01:00:28.740> have 01:00:28.849 --> 01:00:28.859 align:start position:0% already started with travels we have 01:00:28.859 --> 01:00:31.309 align:start position:0% already started with travels we have some<01:00:29.099> kind<01:00:29.220> of<01:00:29.339> draft<01:00:29.700> implementation<01:00:30.480> and<01:00:31.020> we 01:00:31.309 --> 01:00:31.319 align:start position:0% some kind of draft implementation and we 01:00:31.319 --> 01:00:33.710 align:start position:0% some kind of draft implementation and we know<01:00:31.440> that<01:00:31.680> maybe<01:00:32.040> it's<01:00:32.220> gonna<01:00:32.400> change<01:00:32.760> but 01:00:33.710 --> 01:00:33.720 align:start position:0% know that maybe it's gonna change but 01:00:33.720 --> 01:00:36.349 align:start position:0% know that maybe it's gonna change but yeah<01:00:34.079> why<01:00:34.319> not<01:00:34.500> to<01:00:34.680> start<01:00:34.859> playing<01:00:35.460> with<01:00:35.700> it<01:00:35.880> so 01:00:36.349 --> 01:00:36.359 align:start position:0% yeah why not to start playing with it so 01:00:36.359 --> 01:00:38.270 align:start position:0% yeah why not to start playing with it so yeah<01:00:36.599> in<01:00:36.839> general<01:00:36.960> yeah<01:00:37.319> we<01:00:37.559> are<01:00:37.740> in<01:00:37.980> much 01:00:38.270 --> 01:00:38.280 align:start position:0% yeah in general yeah we are in much 01:00:38.280 --> 01:00:40.970 align:start position:0% yeah in general yeah we are in much better<01:00:38.460> State<01:00:38.819> than<01:00:39.180> we<01:00:39.480> used<01:00:39.599> to<01:00:39.780> be<01:00:39.839> and<01:00:40.680> yeah 01:00:40.970 --> 01:00:40.980 align:start position:0% better State than we used to be and yeah 01:00:40.980 --> 01:00:45.069 align:start position:0% better State than we used to be and yeah this<01:00:41.460> is<01:00:41.520> what<01:00:41.700> we<01:00:41.760> are<01:00:41.940> doing<01:00:42.059> right<01:00:42.240> now 01:00:45.069 --> 01:00:45.079 align:start position:0% 01:00:45.079 --> 01:00:47.650 align:start position:0% so<01:00:46.079> uh 01:00:47.650 --> 01:00:47.660 align:start position:0% so uh 01:00:47.660 --> 01:00:50.510 align:start position:0% so uh yeah<01:00:48.660> I<01:00:48.900> can<01:00:48.960> give<01:00:49.140> you<01:00:49.319> uh<01:00:49.920> an<01:00:50.160> additional 01:00:50.510 --> 01:00:50.520 align:start position:0% yeah I can give you uh an additional 01:00:50.520 --> 01:00:52.970 align:start position:0% yeah I can give you uh an additional perspective<01:00:50.940> from<01:00:51.480> Minority<01:00:52.440> client<01:00:52.799> like 01:00:52.970 --> 01:00:52.980 align:start position:0% perspective from Minority client like 01:00:52.980 --> 01:00:54.890 align:start position:0% perspective from Minority client like lodestar<01:00:53.579> we're<01:00:54.119> pretty<01:00:54.359> much<01:00:54.480> in<01:00:54.660> the<01:00:54.780> same 01:00:54.890 --> 01:00:54.900 align:start position:0% lodestar we're pretty much in the same 01:00:54.900 --> 01:00:58.190 align:start position:0% lodestar we're pretty much in the same boat<01:00:55.079> I<01:00:55.559> guess<01:00:55.740> with<01:00:56.220> like<01:00:56.520> nethermind<01:00:57.119> where 01:00:58.190 --> 01:00:58.200 align:start position:0% boat I guess with like nethermind where 01:00:58.200 --> 01:01:01.010 align:start position:0% boat I guess with like nethermind where before<01:00:58.799> like<01:00:59.280> at<01:00:59.640> a<01:00:59.760> point<01:00:59.880> where<01:01:00.240> we<01:01:00.900> haven't 01:01:01.010 --> 01:01:01.020 align:start position:0% before like at a point where we haven't 01:01:01.020 --> 01:01:03.170 align:start position:0% before like at a point where we haven't even<01:01:01.319> hired<01:01:01.740> the<01:01:01.859> people<01:01:02.040> that<01:01:02.339> you<01:01:02.460> guys<01:01:02.640> have 01:01:03.170 --> 01:01:03.180 align:start position:0% even hired the people that you guys have 01:01:03.180 --> 01:01:06.170 align:start position:0% even hired the people that you guys have at<01:01:03.420> this<01:01:03.599> point<01:01:03.780> so<01:01:04.680> in<01:01:05.040> terms<01:01:05.280> of<01:01:05.400> time<01:01:05.700> we 01:01:06.170 --> 01:01:06.180 align:start position:0% at this point so in terms of time we 01:01:06.180 --> 01:01:08.569 align:start position:0% at this point so in terms of time we really<01:01:06.359> haven't<01:01:06.660> had<01:01:07.079> as<01:01:07.500> much<01:01:07.680> time<01:01:08.280> to 01:01:08.569 --> 01:01:08.579 align:start position:0% really haven't had as much time to 01:01:08.579 --> 01:01:10.609 align:start position:0% really haven't had as much time to really<01:01:08.760> think<01:01:09.059> too<01:01:09.420> too<01:01:09.660> far<01:01:09.839> ahead<01:01:10.200> we're 01:01:10.609 --> 01:01:10.619 align:start position:0% really think too too far ahead we're 01:01:10.619 --> 01:01:12.530 align:start position:0% really think too too far ahead we're getting<01:01:10.859> most<01:01:11.220> of<01:01:11.400> the<01:01:11.520> stuff<01:01:11.880> from<01:01:12.119> you<01:01:12.420> know 01:01:12.530 --> 01:01:12.540 align:start position:0% getting most of the stuff from you know 01:01:12.540 --> 01:01:14.510 align:start position:0% getting most of the stuff from you know you<01:01:13.020> guys<01:01:13.200> in<01:01:13.440> in<01:01:13.619> the<01:01:13.859> community<01:01:13.980> and<01:01:14.339> such 01:01:14.510 --> 01:01:14.520 align:start position:0% you guys in in the community and such 01:01:14.520 --> 01:01:17.210 align:start position:0% you guys in in the community and such but<01:01:15.420> uh<01:01:15.660> technical<01:01:16.260> debt<01:01:16.619> is<01:01:16.799> definitely<01:01:17.040> a 01:01:17.210 --> 01:01:17.220 align:start position:0% but uh technical debt is definitely a 01:01:17.220 --> 01:01:20.030 align:start position:0% but uh technical debt is definitely a huge<01:01:17.460> thing<01:01:17.640> for<01:01:18.000> us<01:01:18.119> as<01:01:18.299> well<01:01:18.480> we<01:01:19.319> have<01:01:19.559> a<01:01:19.980> lot 01:01:20.030 --> 01:01:20.040 align:start position:0% huge thing for us as well we have a lot 01:01:20.040 --> 01:01:22.430 align:start position:0% huge thing for us as well we have a lot of<01:01:20.160> documentation<01:01:20.760> we<01:01:21.000> need<01:01:21.180> to<01:01:21.299> update<01:01:21.599> stuff 01:01:22.430 --> 01:01:22.440 align:start position:0% of documentation we need to update stuff 01:01:22.440 --> 01:01:25.309 align:start position:0% of documentation we need to update stuff like<01:01:22.680> this<01:01:22.920> which<01:01:23.940> um<01:01:24.059> you<01:01:24.299> know<01:01:24.420> it<01:01:25.079> would<01:01:25.140> be 01:01:25.309 --> 01:01:25.319 align:start position:0% like this which um you know it would be 01:01:25.319 --> 01:01:27.530 align:start position:0% like this which um you know it would be nice<01:01:25.500> to<01:01:25.680> have<01:01:25.920> a<01:01:26.160> Sprint<01:01:26.520> that's<01:01:26.880> just<01:01:27.180> you 01:01:27.530 --> 01:01:27.540 align:start position:0% nice to have a Sprint that's just you 01:01:27.540 --> 01:01:29.750 align:start position:0% nice to have a Sprint that's just you know<01:01:27.599> for<01:01:27.839> technical<01:01:28.200> debt<01:01:28.559> and<01:01:29.400> and<01:01:29.640> and 01:01:29.750 --> 01:01:29.760 align:start position:0% know for technical debt and and and 01:01:29.760 --> 01:01:32.630 align:start position:0% know for technical debt and and and getting<01:01:30.299> our<01:01:30.480> client<01:01:30.720> up<01:01:31.020> uh<01:01:31.440> to<01:01:31.740> to<01:01:32.160> par<01:01:32.400> in 01:01:32.630 --> 01:01:32.640 align:start position:0% getting our client up uh to to par in 01:01:32.640 --> 01:01:33.890 align:start position:0% getting our client up uh to to par in that<01:01:32.760> sense 01:01:33.890 --> 01:01:33.900 align:start position:0% that sense 01:01:33.900 --> 01:01:35.569 align:start position:0% that sense um<01:01:33.960> but<01:01:34.200> that's<01:01:34.500> you<01:01:34.980> know<01:01:35.040> we're<01:01:35.339> really 01:01:35.569 --> 01:01:35.579 align:start position:0% um but that's you know we're really 01:01:35.579 --> 01:01:37.370 align:start position:0% um but that's you know we're really excited<01:01:35.940> of<01:01:36.180> course<01:01:36.299> to<01:01:36.599> implement<01:01:36.900> all<01:01:37.140> the 01:01:37.370 --> 01:01:37.380 align:start position:0% excited of course to implement all the 01:01:37.380 --> 01:01:38.870 align:start position:0% excited of course to implement all the upcoming<01:01:37.859> stuff 01:01:38.870 --> 01:01:38.880 align:start position:0% upcoming stuff 01:01:38.880 --> 01:01:40.730 align:start position:0% upcoming stuff um<01:01:38.940> in<01:01:39.420> the<01:01:39.540> roadmap 01:01:40.730 --> 01:01:40.740 align:start position:0% um in the roadmap 01:01:40.740 --> 01:01:43.670 align:start position:0% um in the roadmap um<01:01:40.859> like<01:01:41.099> this<01:01:41.760> was<01:01:41.940> great<01:01:42.180> for<01:01:42.420> me<01:01:42.540> because<01:01:42.900> I 01:01:43.670 --> 01:01:43.680 align:start position:0% um like this was great for me because I 01:01:43.680 --> 01:01:45.710 align:start position:0% um like this was great for me because I haven't<01:01:43.799> even<01:01:43.920> specked<01:01:44.460> up<01:01:44.520> 48<01:01:44.880> 44<01:01:45.240> as<01:01:45.480> much<01:01:45.599> as 01:01:45.710 --> 01:01:45.720 align:start position:0% haven't even specked up 48 44 as much as 01:01:45.720 --> 01:01:48.530 align:start position:0% haven't even specked up 48 44 as much as I<01:01:45.900> should<01:01:46.140> yet<01:01:46.680> so<01:01:47.040> that's<01:01:47.280> you<01:01:47.700> know 01:01:48.530 --> 01:01:48.540 align:start position:0% I should yet so that's you know 01:01:48.540 --> 01:01:51.410 align:start position:0% I should yet so that's you know where<01:01:49.140> we're<01:01:49.260> at<01:01:49.440> basically 01:01:51.410 --> 01:01:51.420 align:start position:0% where we're at basically 01:01:51.420 --> 01:01:54.470 align:start position:0% where we're at basically so<01:01:52.020> on<01:01:52.260> the<01:01:52.380> Nimbus<01:01:52.799> side<01:01:53.180> there<01:01:54.180> is<01:01:54.359> a 01:01:54.470 --> 01:01:54.480 align:start position:0% so on the Nimbus side there is a 01:01:54.480 --> 01:01:57.289 align:start position:0% so on the Nimbus side there is a delicate<01:01:54.960> balance<01:01:55.319> between<01:01:56.059> implementing<01:01:57.059> a 01:01:57.289 --> 01:01:57.299 align:start position:0% delicate balance between implementing a 01:01:57.299 --> 01:01:59.630 align:start position:0% delicate balance between implementing a new<01:01:57.480> thing<01:01:57.720> that<01:01:58.079> are<01:01:58.260> still<01:01:58.500> moving<01:01:59.160> targets 01:01:59.630 --> 01:01:59.640 align:start position:0% new thing that are still moving targets 01:01:59.640 --> 01:02:03.109 align:start position:0% new thing that are still moving targets and<01:02:00.859> doing<01:02:01.859> things<01:02:02.280> that<01:02:02.520> are<01:02:02.640> expecting<01:02:02.940> from 01:02:03.109 --> 01:02:03.119 align:start position:0% and doing things that are expecting from 01:02:03.119 --> 01:02:05.690 align:start position:0% and doing things that are expecting from client<01:02:03.480> teams<01:02:03.780> like<01:02:03.900> testing<01:02:04.440> and<01:02:05.099> trying<01:02:05.400> not 01:02:05.690 --> 01:02:05.700 align:start position:0% client teams like testing and trying not 01:02:05.700 --> 01:02:07.910 align:start position:0% client teams like testing and trying not to<01:02:05.880> introduce<01:02:06.180> regressions<01:02:06.839> uh<01:02:07.380> like<01:02:07.559> we<01:02:07.740> had 01:02:07.910 --> 01:02:07.920 align:start position:0% to introduce regressions uh like we had 01:02:07.920 --> 01:02:09.230 align:start position:0% to introduce regressions uh like we had a<01:02:08.099> lot<01:02:08.220> of 01:02:09.230 --> 01:02:09.240 align:start position:0% a lot of 01:02:09.240 --> 01:02:09.950 align:start position:0% a lot of um 01:02:09.950 --> 01:02:09.960 align:start position:0% um 01:02:09.960 --> 01:02:12.829 align:start position:0% um Point<01:02:10.440> release<01:02:10.740> in<01:02:11.400> the<01:02:11.579> past<01:02:12.299> three<01:02:12.540> weeks 01:02:12.829 --> 01:02:12.839 align:start position:0% Point release in the past three weeks 01:02:12.839 --> 01:02:15.530 align:start position:0% Point release in the past three weeks before<01:02:12.960> the<01:02:13.260> match<01:02:13.500> and<01:02:14.339> that<01:02:14.760> took<01:02:15.000> like<01:02:15.299> all 01:02:15.530 --> 01:02:15.540 align:start position:0% before the match and that took like all 01:02:15.540 --> 01:02:18.829 align:start position:0% before the match and that took like all of<01:02:15.660> our<01:02:15.839> Focus<01:02:16.079> but<01:02:16.799> we<01:02:17.160> do<01:02:17.339> like 01:02:18.829 --> 01:02:18.839 align:start position:0% of our Focus but we do like 01:02:18.839 --> 01:02:21.170 align:start position:0% of our Focus but we do like um<01:02:18.859> implementing<01:02:19.859> new<01:02:20.220> things<01:02:20.400> as<01:02:20.700> well<01:02:20.819> for 01:02:21.170 --> 01:02:21.180 align:start position:0% um implementing new things as well for 01:02:21.180 --> 01:02:23.930 align:start position:0% um implementing new things as well for example<01:02:21.420> we<01:02:22.140> took<01:02:22.980> the<01:02:23.099> lead<01:02:23.220> with<01:02:23.400> load<01:02:23.760> star 01:02:23.930 --> 01:02:23.940 align:start position:0% example we took the lead with load star 01:02:23.940 --> 01:02:25.910 align:start position:0% example we took the lead with load star on<01:02:24.240> the<01:02:24.359> light<01:02:24.540> client<01:02:24.900> thing<01:02:25.200> so<01:02:25.619> this<01:02:25.799> is 01:02:25.910 --> 01:02:25.920 align:start position:0% on the light client thing so this is 01:02:25.920 --> 01:02:27.890 align:start position:0% on the light client thing so this is something<01:02:26.099> that<01:02:26.339> we<01:02:26.460> will<01:02:26.579> continue<01:02:26.819> but<01:02:27.660> we 01:02:27.890 --> 01:02:27.900 align:start position:0% something that we will continue but we 01:02:27.900 --> 01:02:29.690 align:start position:0% something that we will continue but we didn't<01:02:28.020> start<01:02:28.319> at<01:02:28.500> all<01:02:28.680> on<01:02:28.980> anything<01:02:29.160> related 01:02:29.690 --> 01:02:29.700 align:start position:0% didn't start at all on anything related 01:02:29.700 --> 01:02:32.690 align:start position:0% didn't start at all on anything related to<01:02:30.059> the<01:02:30.540> search<01:02:30.720> The<01:02:31.140> Verge<01:02:31.500> The<01:02:32.400> Purge 01:02:32.690 --> 01:02:32.700 align:start position:0% to the search The Verge The Purge 01:02:32.700 --> 01:02:36.170 align:start position:0% to the search The Verge The Purge endless<01:02:33.000> Branch<01:02:33.359> well<01:02:33.780> we<01:02:34.740> did<01:02:34.920> try<01:02:35.280> to<01:02:35.460> look 01:02:36.170 --> 01:02:36.180 align:start position:0% endless Branch well we did try to look 01:02:36.180 --> 01:02:39.109 align:start position:0% endless Branch well we did try to look into<01:02:36.359> kcg<01:02:37.020> commitment<01:02:37.440> but<01:02:37.980> they<01:02:38.400> changed<01:02:38.760> a 01:02:39.109 --> 01:02:39.119 align:start position:0% into kcg commitment but they changed a 01:02:39.119 --> 01:02:40.490 align:start position:0% into kcg commitment but they changed a lot<01:02:39.240> in<01:02:39.480> the<01:02:39.599> past<01:02:39.720> two<01:02:39.900> years<01:02:40.020> so<01:02:40.260> everything 01:02:40.490 --> 01:02:40.500 align:start position:0% lot in the past two years so everything 01:02:40.500 --> 01:02:45.230 align:start position:0% lot in the past two years so everything has<01:02:40.799> to<01:02:40.920> be<01:02:41.040> thrown<01:02:41.400> out<01:02:41.520> and<01:02:42.000> recorded 01:02:45.230 --> 01:02:45.240 align:start position:0% 01:02:45.240 --> 01:02:49.069 align:start position:0% um I<01:02:45.660> I<01:02:45.839> also<01:02:46.319> think<01:02:46.740> it's<01:02:47.040> fine<01:02:47.579> for<01:02:48.119> uh<01:02:48.839> these 01:02:49.069 --> 01:02:49.079 align:start position:0% um I I also think it's fine for uh these 01:02:49.079 --> 01:02:51.289 align:start position:0% um I I also think it's fine for uh these smaller<01:02:49.380> clients<01:02:49.740> to<01:02:49.920> not<01:02:50.099> be<01:02:50.400> on<01:02:50.700> the<01:02:50.940> like 01:02:51.289 --> 01:02:51.299 align:start position:0% smaller clients to not be on the like 01:02:51.299 --> 01:02:53.450 align:start position:0% smaller clients to not be on the like brink<01:02:51.839> of<01:02:52.020> research 01:02:53.450 --> 01:02:53.460 align:start position:0% brink of research 01:02:53.460 --> 01:02:55.190 align:start position:0% brink of research um because<01:02:53.760> the 01:02:55.190 --> 01:02:55.200 align:start position:0% um because the 01:02:55.200 --> 01:02:57.170 align:start position:0% um because the especially<01:02:55.740> with<01:02:56.099> these<01:02:56.400> uh<01:02:56.640> with<01:02:57.000> these 01:02:57.170 --> 01:02:57.180 align:start position:0% especially with these uh with these 01:02:57.180 --> 01:02:59.750 align:start position:0% especially with these uh with these upgrades<01:02:57.480> like<01:02:57.720> like<01:02:57.960> 4844<01:02:58.619> right<01:02:58.920> now<01:02:59.040> the 01:02:59.750 --> 01:02:59.760 align:start position:0% upgrades like like 4844 right now the 01:02:59.760 --> 01:03:04.430 align:start position:0% upgrades like like 4844 right now the spec<01:02:59.940> will<01:03:00.240> change<01:03:00.540> uh<01:03:01.380> a<01:03:01.740> lot<01:03:02.180> and<01:03:03.180> uh<01:03:03.599> it<01:03:04.200> I 01:03:04.430 --> 01:03:04.440 align:start position:0% spec will change uh a lot and uh it I 01:03:04.440 --> 01:03:06.230 align:start position:0% spec will change uh a lot and uh it I think<01:03:04.500> it<01:03:04.680> just<01:03:04.859> doesn't<01:03:05.040> make<01:03:05.339> sense<01:03:05.579> for<01:03:05.940> for 01:03:06.230 --> 01:03:06.240 align:start position:0% think it just doesn't make sense for for 01:03:06.240 --> 01:03:08.089 align:start position:0% think it just doesn't make sense for for smaller<01:03:06.720> client<01:03:07.020> teams 01:03:08.089 --> 01:03:08.099 align:start position:0% smaller client teams 01:03:08.099 --> 01:03:11.809 align:start position:0% smaller client teams um<01:03:08.220> that<01:03:08.579> have<01:03:08.819> that<01:03:09.740> need<01:03:10.740> to<01:03:10.920> focus<01:03:11.160> on<01:03:11.460> like 01:03:11.809 --> 01:03:11.819 align:start position:0% um that have that need to focus on like 01:03:11.819 --> 01:03:14.270 align:start position:0% um that have that need to focus on like getting<01:03:12.119> their<01:03:12.359> client<01:03:12.660> up<01:03:12.839> to<01:03:13.020> speed 01:03:14.270 --> 01:03:14.280 align:start position:0% getting their client up to speed 01:03:14.280 --> 01:03:18.710 align:start position:0% getting their client up to speed um<01:03:14.339> to<01:03:14.819> also<01:03:15.920> uh<01:03:16.920> think<01:03:17.220> about<01:03:17.400> the<01:03:18.240> research 01:03:18.710 --> 01:03:18.720 align:start position:0% um to also uh think about the research 01:03:18.720 --> 01:03:21.230 align:start position:0% um to also uh think about the research and<01:03:19.200> and<01:03:19.500> the<01:03:19.799> iteration<01:03:20.160> on<01:03:20.400> the<01:03:20.520> spec<01:03:20.700> so<01:03:21.000> I 01:03:21.230 --> 01:03:21.240 align:start position:0% and and the iteration on the spec so I 01:03:21.240 --> 01:03:22.510 align:start position:0% and and the iteration on the spec so I think<01:03:21.299> that's<01:03:21.480> something<01:03:21.720> that<01:03:21.960> we<01:03:22.140> did<01:03:22.260> with 01:03:22.510 --> 01:03:22.520 align:start position:0% think that's something that we did with 01:03:22.520 --> 01:03:25.309 align:start position:0% think that's something that we did with uh<01:03:23.520> with<01:03:23.760> the<01:03:23.819> merge<01:03:24.180> pretty<01:03:24.359> pretty<01:03:24.660> well<01:03:25.079> is 01:03:25.309 --> 01:03:25.319 align:start position:0% uh with the merge pretty pretty well is 01:03:25.319 --> 01:03:28.010 align:start position:0% uh with the merge pretty pretty well is there<01:03:25.980> was<01:03:26.220> like<01:03:26.700> the<01:03:27.000> bigger<01:03:27.240> client<01:03:27.540> teams 01:03:28.010 --> 01:03:28.020 align:start position:0% there was like the bigger client teams 01:03:28.020 --> 01:03:30.890 align:start position:0% there was like the bigger client teams uh<01:03:28.260> gas<01:03:28.559> Lighthouse<01:03:29.040> prism 01:03:30.890 --> 01:03:30.900 align:start position:0% uh gas Lighthouse prism 01:03:30.900 --> 01:03:31.630 align:start position:0% uh gas Lighthouse prism um 01:03:31.630 --> 01:03:31.640 align:start position:0% um 01:03:31.640 --> 01:03:35.210 align:start position:0% um uh<01:03:32.640> never<01:03:33.000> mind<01:03:33.299> be<01:03:33.720> so<01:03:34.020> iterating<01:03:34.619> on<01:03:34.980> the 01:03:35.210 --> 01:03:35.220 align:start position:0% uh never mind be so iterating on the 01:03:35.220 --> 01:03:37.789 align:start position:0% uh never mind be so iterating on the iterating<01:03:35.819> on<01:03:36.059> the<01:03:36.240> spec<01:03:36.420> and<01:03:37.079> the<01:03:37.319> the<01:03:37.500> other 01:03:37.789 --> 01:03:37.799 align:start position:0% iterating on the spec and the the other 01:03:37.799 --> 01:03:38.990 align:start position:0% iterating on the spec and the the other client's 01:03:38.990 --> 01:03:39.000 align:start position:0% client's 01:03:39.000 --> 01:03:41.809 align:start position:0% client's um kind<01:03:39.420> of<01:03:39.540> uh<01:03:40.079> like<01:03:40.319> like<01:03:40.680> like<01:03:40.799> following<01:03:41.640> a 01:03:41.809 --> 01:03:41.819 align:start position:0% um kind of uh like like like following a 01:03:41.819 --> 01:03:46.130 align:start position:0% um kind of uh like like like following a bit<01:03:41.940> and<01:03:43.319> um<01:03:43.380> I<01:03:43.859> think<01:03:43.920> that's<01:03:44.220> a<01:03:44.520> good<01:03:44.760> way<01:03:45.140> for 01:03:46.130 --> 01:03:46.140 align:start position:0% bit and um I think that's a good way for 01:03:46.140 --> 01:03:48.770 align:start position:0% bit and um I think that's a good way for the<01:03:46.500> teams<01:03:46.980> that<01:03:47.220> have<01:03:47.460> more<01:03:47.940> funding<01:03:48.420> more 01:03:48.770 --> 01:03:48.780 align:start position:0% the teams that have more funding more 01:03:48.780 --> 01:03:50.329 align:start position:0% the teams that have more funding more people 01:03:50.329 --> 01:03:50.339 align:start position:0% people 01:03:50.339 --> 01:03:52.609 align:start position:0% people um<01:03:50.460> to<01:03:51.240> take<01:03:51.540> some<01:03:51.720> of<01:03:51.839> the<01:03:51.960> load<01:03:52.260> away<01:03:52.380> from 01:03:52.609 --> 01:03:52.619 align:start position:0% um to take some of the load away from 01:03:52.619 --> 01:03:55.130 align:start position:0% um to take some of the load away from the<01:03:52.799> other<01:03:52.859> teams<01:03:53.339> and<01:03:54.000> also<01:03:54.299> that's<01:03:54.660> also 01:03:55.130 --> 01:03:55.140 align:start position:0% the other teams and also that's also 01:03:55.140 --> 01:03:56.750 align:start position:0% the other teams and also that's also what<01:03:55.260> we're<01:03:55.380> trying<01:03:55.619> with<01:03:55.859> uh<01:03:56.220> with<01:03:56.520> uh 01:03:56.750 --> 01:03:56.760 align:start position:0% what we're trying with uh with uh 01:03:56.760 --> 01:03:59.450 align:start position:0% what we're trying with uh with uh testing<01:03:57.240> uh<01:03:58.140> and<01:03:58.319> and<01:03:58.500> the<01:03:58.980> ethereum 01:03:59.450 --> 01:03:59.460 align:start position:0% testing uh and and the ethereum 01:03:59.460 --> 01:04:02.089 align:start position:0% testing uh and and the ethereum foundation<01:03:59.819> testing<01:04:00.240> team<01:04:00.559> uh<01:04:01.559> where<01:04:01.920> we're 01:04:02.089 --> 01:04:02.099 align:start position:0% foundation testing team uh where we're 01:04:02.099 --> 01:04:03.890 align:start position:0% foundation testing team uh where we're currently<01:04:02.460> looking<01:04:02.700> for<01:04:02.940> new<01:04:03.180> people<01:04:03.420> so<01:04:03.780> if 01:04:03.890 --> 01:04:03.900 align:start position:0% currently looking for new people so if 01:04:03.900 --> 01:04:06.589 align:start position:0% currently looking for new people so if you're<01:04:04.020> interested<01:04:04.380> in<01:04:04.619> testing<01:04:05.059> uh<01:04:06.059> come 01:04:06.589 --> 01:04:06.599 align:start position:0% you're interested in testing uh come 01:04:06.599 --> 01:04:10.549 align:start position:0% you're interested in testing uh come talk<01:04:06.839> to<01:04:07.079> me<01:04:07.500> or<01:04:08.040> Mario<01:04:08.400> Vega 01:04:10.549 --> 01:04:10.559 align:start position:0% talk to me or Mario Vega 01:04:10.559 --> 01:04:13.390 align:start position:0% talk to me or Mario Vega um 01:04:13.390 --> 01:04:13.400 align:start position:0% 01:04:13.400 --> 01:04:17.089 align:start position:0% yes<01:04:14.400> so<01:04:14.760> we<01:04:15.059> we<01:04:15.119> want<01:04:15.660> to<01:04:15.780> completely<01:04:16.500> revamp 01:04:17.089 --> 01:04:17.099 align:start position:0% yes so we we want to completely revamp 01:04:17.099 --> 01:04:20.089 align:start position:0% yes so we we want to completely revamp the<01:04:17.760> way<01:04:17.940> we<01:04:18.119> do<01:04:18.299> state<01:04:18.540> tests 01:04:20.089 --> 01:04:20.099 align:start position:0% the way we do state tests 01:04:20.099 --> 01:04:22.609 align:start position:0% the way we do state tests um<01:04:20.160> to<01:04:20.520> make<01:04:20.640> it<01:04:20.940> really<01:04:21.180> really<01:04:21.359> easy<01:04:21.720> for<01:04:22.140> for 01:04:22.609 --> 01:04:22.619 align:start position:0% um to make it really really easy for for 01:04:22.619 --> 01:04:26.270 align:start position:0% um to make it really really easy for for people<01:04:23.460> to<01:04:23.880> to<01:04:24.119> implement<01:04:24.599> State<01:04:24.900> tests<01:04:25.319> and 01:04:26.270 --> 01:04:26.280 align:start position:0% people to to implement State tests and 01:04:26.280 --> 01:04:30.530 align:start position:0% people to to implement State tests and uh<01:04:27.020> to<01:04:28.020> take<01:04:28.200> some<01:04:28.380> load<01:04:28.740> of<01:04:28.859> of<01:04:29.160> the<01:04:29.940> the 01:04:30.530 --> 01:04:30.540 align:start position:0% uh to take some load of of the the 01:04:30.540 --> 01:04:32.630 align:start position:0% uh to take some load of of the the client<01:04:30.900> teams 01:04:32.630 --> 01:04:32.640 align:start position:0% client teams 01:04:32.640 --> 01:04:34.730 align:start position:0% client teams I<01:04:33.180> just<01:04:33.299> wanted<01:04:33.540> to<01:04:33.780> share<01:04:34.020> from<01:04:34.380> a<01:04:34.559> small 01:04:34.730 --> 01:04:34.740 align:start position:0% I just wanted to share from a small 01:04:34.740 --> 01:04:37.670 align:start position:0% I just wanted to share from a small client<01:04:35.099> perspective<01:04:35.520> so<01:04:36.000> for<01:04:36.359> Basu<01:04:37.020> honestly 01:04:37.670 --> 01:04:37.680 align:start position:0% client perspective so for Basu honestly 01:04:37.680 --> 01:04:40.789 align:start position:0% client perspective so for Basu honestly past<01:04:38.099> month<01:04:38.400> has<01:04:38.700> been<01:04:38.940> as<01:04:39.599> equally<01:04:39.900> hectic<01:04:40.440> as 01:04:40.789 --> 01:04:40.799 align:start position:0% past month has been as equally hectic as 01:04:40.799 --> 01:04:43.190 align:start position:0% past month has been as equally hectic as preparing<01:04:41.460> for<01:04:41.640> the<01:04:41.760> merge 01:04:43.190 --> 01:04:43.200 align:start position:0% preparing for the merge 01:04:43.200 --> 01:04:46.549 align:start position:0% preparing for the merge um with<01:04:43.680> a<01:04:43.799> bunch<01:04:43.980> of<01:04:44.160> major<01:04:44.880> fixes<01:04:45.660> for<01:04:46.319> bug 01:04:46.549 --> 01:04:46.559 align:start position:0% um with a bunch of major fixes for bug 01:04:46.559 --> 01:04:49.069 align:start position:0% um with a bunch of major fixes for bug fixes<01:04:47.040> so<01:04:48.000> honestly<01:04:48.540> we<01:04:48.660> haven't<01:04:48.839> even 01:04:49.069 --> 01:04:49.079 align:start position:0% fixes so honestly we haven't even 01:04:49.079 --> 01:04:52.069 align:start position:0% fixes so honestly we haven't even thought<01:04:49.440> of<01:04:49.740> a<01:04:49.980> future<01:04:50.240> eips<01:04:51.240> honestly<01:04:51.839> I 01:04:52.069 --> 01:04:52.079 align:start position:0% thought of a future eips honestly I 01:04:52.079 --> 01:04:54.530 align:start position:0% thought of a future eips honestly I think<01:04:52.260> we<01:04:52.920> even<01:04:53.099> haven't<01:04:53.520> gotten<01:04:53.940> a<01:04:54.059> chance<01:04:54.180> to 01:04:54.530 --> 01:04:54.540 align:start position:0% think we even haven't gotten a chance to 01:04:54.540 --> 01:04:57.049 align:start position:0% think we even haven't gotten a chance to rest<01:04:55.099> and<01:04:56.099> a<01:04:56.280> lot<01:04:56.339> of<01:04:56.460> the<01:04:56.579> maintainers 01:04:57.049 --> 01:04:57.059 align:start position:0% rest and a lot of the maintainers 01:04:57.059 --> 01:04:58.549 align:start position:0% rest and a lot of the maintainers couldn't<01:04:57.359> make<01:04:57.660> it<01:04:57.780> because<01:04:57.960> they're<01:04:58.319> still 01:04:58.549 --> 01:04:58.559 align:start position:0% couldn't make it because they're still 01:04:58.559 --> 01:05:00.770 align:start position:0% couldn't make it because they're still working<01:04:58.799> really<01:04:59.099> hard<01:04:59.400> working<01:05:00.059> on<01:05:00.240> the<01:05:00.359> fixes 01:05:00.770 --> 01:05:00.780 align:start position:0% working really hard working on the fixes 01:05:00.780 --> 01:05:02.870 align:start position:0% working really hard working on the fixes some<01:05:01.500> even<01:05:01.740> donated<01:05:02.400> some<01:05:02.640> of<01:05:02.760> their 01:05:02.870 --> 01:05:02.880 align:start position:0% some even donated some of their 01:05:02.880 --> 01:05:05.809 align:start position:0% some even donated some of their opportunity<01:05:03.359> leave<01:05:03.599> to<01:05:03.960> work<01:05:04.260> on<01:05:04.559> the<01:05:04.920> fixes 01:05:05.809 --> 01:05:05.819 align:start position:0% opportunity leave to work on the fixes 01:05:05.819 --> 01:05:09.230 align:start position:0% opportunity leave to work on the fixes um so<01:05:06.180> quite<01:05:06.900> quite<01:05:07.260> intense<01:05:08.000> but<01:05:09.000> I<01:05:09.119> think 01:05:09.230 --> 01:05:09.240 align:start position:0% um so quite quite intense but I think 01:05:09.240 --> 01:05:10.670 align:start position:0% um so quite quite intense but I think afterwards<01:05:09.780> we'll 01:05:10.670 --> 01:05:10.680 align:start position:0% afterwards we'll 01:05:10.680 --> 01:05:12.589 align:start position:0% afterwards we'll um hopefully<01:05:11.099> get<01:05:11.460> some<01:05:11.579> time<01:05:11.760> to<01:05:12.000> rest<01:05:12.180> and 01:05:12.589 --> 01:05:12.599 align:start position:0% um hopefully get some time to rest and 01:05:12.599 --> 01:05:14.750 align:start position:0% um hopefully get some time to rest and get<01:05:12.720> all<01:05:12.900> the<01:05:13.020> maintainers<01:05:13.500> together<01:05:13.760> talk 01:05:14.750 --> 01:05:14.760 align:start position:0% get all the maintainers together talk 01:05:14.760 --> 01:05:16.970 align:start position:0% get all the maintainers together talk through<01:05:15.059> what's<01:05:15.420> going<01:05:15.599> to<01:05:15.720> be<01:05:15.780> the<01:05:16.079> future 01:05:16.970 --> 01:05:16.980 align:start position:0% through what's going to be the future 01:05:16.980 --> 01:05:19.430 align:start position:0% through what's going to be the future um you<01:05:17.220> know<01:05:17.599> works<01:05:18.599> that<01:05:18.720> we<01:05:18.900> want<01:05:19.020> to<01:05:19.140> work 01:05:19.430 --> 01:05:19.440 align:start position:0% um you know works that we want to work 01:05:19.440 --> 01:05:21.950 align:start position:0% um you know works that we want to work on<01:05:19.619> what<01:05:20.520> really<01:05:20.640> resonated<01:05:21.180> me<01:05:21.420> personally 01:05:21.950 --> 01:05:21.960 align:start position:0% on what really resonated me personally 01:05:21.960 --> 01:05:24.049 align:start position:0% on what really resonated me personally with<01:05:22.319> the<01:05:22.500> earlier<01:05:22.859> Talks<01:05:23.160> by<01:05:23.339> iOS<01:05:23.760> the 01:05:24.049 --> 01:05:24.059 align:start position:0% with the earlier Talks by iOS the 01:05:24.059 --> 01:05:26.870 align:start position:0% with the earlier Talks by iOS the subtraction<01:05:24.540> part<01:05:25.079> so<01:05:25.799> I'm<01:05:26.220> hoping<01:05:26.520> that<01:05:26.700> as 01:05:26.870 --> 01:05:26.880 align:start position:0% subtraction part so I'm hoping that as 01:05:26.880 --> 01:05:29.210 align:start position:0% subtraction part so I'm hoping that as maintainers<01:05:27.359> we<01:05:27.480> got<01:05:27.660> to<01:05:27.839> see<01:05:28.020> which<01:05:28.799> part<01:05:29.040> of 01:05:29.210 --> 01:05:29.220 align:start position:0% maintainers we got to see which part of 01:05:29.220 --> 01:05:31.250 align:start position:0% maintainers we got to see which part of our<01:05:29.339> code<01:05:29.579> base<01:05:29.819> could<01:05:30.119> we<01:05:30.359> actually<01:05:30.660> subtract 01:05:31.250 --> 01:05:31.260 align:start position:0% our code base could we actually subtract 01:05:31.260 --> 01:05:32.990 align:start position:0% our code base could we actually subtract I<01:05:31.619> think<01:05:31.740> we're<01:05:31.980> still<01:05:32.220> talking<01:05:32.400> about<01:05:32.579> about 01:05:32.990 --> 01:05:33.000 align:start position:0% I think we're still talking about about 01:05:33.000 --> 01:05:35.150 align:start position:0% I think we're still talking about about what<01:05:33.599> eips<01:05:33.900> are<01:05:34.200> we<01:05:34.319> going<01:05:34.440> to<01:05:34.500> add<01:05:34.740> and<01:05:34.980> add 01:05:35.150 --> 01:05:35.160 align:start position:0% what eips are we going to add and add 01:05:35.160 --> 01:05:36.950 align:start position:0% what eips are we going to add and add and<01:05:35.339> add<01:05:35.460> to<01:05:35.640> our<01:05:35.819> code<01:05:36.000> base<01:05:36.180> but<01:05:36.720> I<01:05:36.839> think 01:05:36.950 --> 01:05:36.960 align:start position:0% and add to our code base but I think 01:05:36.960 --> 01:05:38.630 align:start position:0% and add to our code base but I think there's<01:05:37.260> going<01:05:37.619> to<01:05:37.799> be<01:05:37.920> some<01:05:38.160> like<01:05:38.400> future 01:05:38.630 --> 01:05:38.640 align:start position:0% there's going to be some like future 01:05:38.640 --> 01:05:41.329 align:start position:0% there's going to be some like future like<01:05:39.359> you<01:05:39.660> know<01:05:39.780> Tech<01:05:40.200> not<01:05:40.680> future<01:05:40.859> like<01:05:41.160> Tech 01:05:41.329 --> 01:05:41.339 align:start position:0% like you know Tech not future like Tech 01:05:41.339 --> 01:05:43.849 align:start position:0% like you know Tech not future like Tech debt<01:05:41.700> from<01:05:41.880> the<01:05:42.059> past<01:05:42.240> to<01:05:42.900> clear<01:05:43.200> out<01:05:43.440> to 01:05:43.849 --> 01:05:43.859 align:start position:0% debt from the past to clear out to 01:05:43.859 --> 01:05:45.650 align:start position:0% debt from the past to clear out to modularize 01:05:45.650 --> 01:05:45.660 align:start position:0% modularize 01:05:45.660 --> 01:05:48.349 align:start position:0% modularize um the<01:05:46.140> the<01:05:46.380> product<01:05:46.680> itself<01:05:47.160> and<01:05:47.520> so<01:05:48.059> looking 01:05:48.349 --> 01:05:48.359 align:start position:0% um the the product itself and so looking 01:05:48.359 --> 01:05:50.390 align:start position:0% um the the product itself and so looking into<01:05:48.599> a<01:05:48.839> lot<01:05:48.960> of<01:05:49.500> um<01:05:49.559> I<01:05:49.799> would<01:05:49.920> say<01:05:50.040> client 01:05:50.390 --> 01:05:50.400 align:start position:0% into a lot of um I would say client 01:05:50.400 --> 01:05:52.549 align:start position:0% into a lot of um I would say client Improvement<01:05:50.819> is<01:05:51.299> currently<01:05:52.020> where<01:05:52.200> I<01:05:52.380> see 01:05:52.549 --> 01:05:52.559 align:start position:0% Improvement is currently where I see 01:05:52.559 --> 01:05:54.410 align:start position:0% Improvement is currently where I see maintainers<01:05:53.160> are<01:05:53.400> talking<01:05:53.579> a<01:05:53.819> lot<01:05:53.940> about<01:05:54.059> but 01:05:54.410 --> 01:05:54.420 align:start position:0% maintainers are talking a lot about but 01:05:54.420 --> 01:05:56.270 align:start position:0% maintainers are talking a lot about but yeah<01:05:54.720> definitely<01:05:55.079> would 01:05:56.270 --> 01:05:56.280 align:start position:0% yeah definitely would 01:05:56.280 --> 01:05:58.069 align:start position:0% yeah definitely would um would<01:05:56.520> have<01:05:56.640> to<01:05:56.819> come<01:05:57.059> talk<01:05:57.420> about<01:05:57.599> eips 01:05:58.069 --> 01:05:58.079 align:start position:0% um would have to come talk about eips 01:05:58.079 --> 01:06:00.410 align:start position:0% um would have to come talk about eips yeah 01:06:00.410 --> 01:06:00.420 align:start position:0% yeah 01:06:00.420 --> 01:06:04.250 align:start position:0% yeah um<01:06:00.599> so<01:06:01.140> I'm<01:06:01.500> prism<01:06:02.099> and<01:06:02.640> I<01:06:03.180> think<01:06:03.359> withdrawals 01:06:04.250 --> 01:06:04.260 align:start position:0% um so I'm prism and I think withdrawals 01:06:04.260 --> 01:06:06.589 align:start position:0% um so I'm prism and I think withdrawals is<01:06:04.619> important<01:06:05.040> but<01:06:05.280> it's<01:06:05.400> also<01:06:05.700> on<01:06:06.119> the<01:06:06.240> easier 01:06:06.589 --> 01:06:06.599 align:start position:0% is important but it's also on the easier 01:06:06.599 --> 01:06:09.670 align:start position:0% is important but it's also on the easier side<01:06:06.839> and<01:06:07.140> on<01:06:07.319> the<01:06:07.440> eip44<01:06:08.339> we<01:06:08.940> have<01:06:09.119> been<01:06:09.299> lucky 01:06:09.670 --> 01:06:09.680 align:start position:0% side and on the eip44 we have been lucky 01:06:09.680 --> 01:06:12.710 align:start position:0% side and on the eip44 we have been lucky and<01:06:10.680> optimism<01:06:11.220> and<01:06:11.640> then<01:06:11.760> coinbase<01:06:12.299> have<01:06:12.599> been 01:06:12.710 --> 01:06:12.720 align:start position:0% and optimism and then coinbase have been 01:06:12.720 --> 01:06:14.690 align:start position:0% and optimism and then coinbase have been contributing<01:06:13.319> to<01:06:13.440> our<01:06:13.559> code<01:06:13.799> base<01:06:14.040> so<01:06:14.400> thank 01:06:14.690 --> 01:06:14.700 align:start position:0% contributing to our code base so thank 01:06:14.700 --> 01:06:17.329 align:start position:0% contributing to our code base so thank you<01:06:14.819> for<01:06:15.240> that<01:06:15.420> but<01:06:15.900> I<01:06:16.079> do<01:06:16.140> want<01:06:16.380> to<01:06:16.559> throw<01:06:16.740> like 01:06:17.329 --> 01:06:17.339 align:start position:0% you for that but I do want to throw like 01:06:17.339 --> 01:06:20.450 align:start position:0% you for that but I do want to throw like a<01:06:17.460> curveball<01:06:17.880> I<01:06:18.660> think<01:06:18.780> like<01:06:19.460> censorship 01:06:20.450 --> 01:06:20.460 align:start position:0% a curveball I think like censorship 01:06:20.460 --> 01:06:23.030 align:start position:0% a curveball I think like censorship resistance<01:06:21.180> is<01:06:21.480> equally<01:06:21.900> as<01:06:22.260> important<01:06:22.740> as 01:06:23.030 --> 01:06:23.040 align:start position:0% resistance is equally as important as 01:06:23.040 --> 01:06:25.910 align:start position:0% resistance is equally as important as 444<01:06:23.819> and<01:06:24.000> withdraw<01:06:24.420> I<01:06:24.900> just<01:06:25.020> look<01:06:25.260> at<01:06:25.440> Mev 01:06:25.910 --> 01:06:25.920 align:start position:0% 444 and withdraw I just look at Mev 01:06:25.920 --> 01:06:29.870 align:start position:0% 444 and withdraw I just look at Mev watch<01:06:26.160> info<01:06:26.640> at<01:06:27.000> 47<01:06:27.900> of<01:06:28.500> the<01:06:28.680> blogs<01:06:29.099> are<01:06:29.520> on<01:06:29.760> the 01:06:29.870 --> 01:06:29.880 align:start position:0% watch info at 47 of the blogs are on the 01:06:29.880 --> 01:06:32.569 align:start position:0% watch info at 47 of the blogs are on the offback<01:06:30.299> compliance<01:06:30.780> right<01:06:30.900> now<01:06:31.079> so<01:06:31.619> 47<01:06:32.160> of 01:06:32.569 --> 01:06:32.579 align:start position:0% offback compliance right now so 47 of 01:06:32.579 --> 01:06:34.789 align:start position:0% offback compliance right now so 47 of the<01:06:32.700> Bloods<01:06:33.059> or<01:06:33.240> main<01:06:33.480> net<01:06:33.660> or<01:06:34.260> have<01:06:34.440> some<01:06:34.619> sort 01:06:34.789 --> 01:06:34.799 align:start position:0% the Bloods or main net or have some sort 01:06:34.799 --> 01:06:36.829 align:start position:0% the Bloods or main net or have some sort of<01:06:34.920> censorship<01:06:35.400> resistance<01:06:35.880> yielded<01:06:36.480> to<01:06:36.720> it 01:06:36.829 --> 01:06:36.839 align:start position:0% of censorship resistance yielded to it 01:06:36.839 --> 01:06:38.150 align:start position:0% of censorship resistance yielded to it right<01:06:37.020> so<01:06:37.440> I<01:06:37.559> do<01:06:37.619> think<01:06:37.799> like<01:06:37.980> there's 01:06:38.150 --> 01:06:38.160 align:start position:0% right so I do think like there's 01:06:38.160 --> 01:06:40.250 align:start position:0% right so I do think like there's something<01:06:38.400> like<01:06:38.640> before<01:06:38.819> full<01:06:39.180> PBS<01:06:39.720> there's 01:06:40.250 --> 01:06:40.260 align:start position:0% something like before full PBS there's 01:06:40.260 --> 01:06:41.569 align:start position:0% something like before full PBS there's definitely<01:06:40.619> something<01:06:40.859> that<01:06:41.099> we<01:06:41.220> can<01:06:41.280> do<01:06:41.400> to 01:06:41.569 --> 01:06:41.579 align:start position:0% definitely something that we can do to 01:06:41.579 --> 01:06:43.730 align:start position:0% definitely something that we can do to make<01:06:41.700> it<01:06:41.880> better<01:06:42.059> we<01:06:42.780> do<01:06:42.900> have<01:06:43.140> some<01:06:43.380> hybrid 01:06:43.730 --> 01:06:43.740 align:start position:0% make it better we do have some hybrid 01:06:43.740 --> 01:06:46.370 align:start position:0% make it better we do have some hybrid PBS<01:06:44.280> we<01:06:44.520> can<01:06:44.640> do<01:06:44.760> we<01:06:45.119> can<01:06:45.299> leverage<01:06:46.140> the 01:06:46.370 --> 01:06:46.380 align:start position:0% PBS we can do we can leverage the 01:06:46.380 --> 01:06:49.730 align:start position:0% PBS we can do we can leverage the Builder<01:06:46.799> API<01:06:47.160> we<01:06:47.700> can<01:06:47.819> iterate<01:06:48.480> very<01:06:48.780> fast<01:06:49.020> we 01:06:49.730 --> 01:06:49.740 align:start position:0% Builder API we can iterate very fast we 01:06:49.740 --> 01:06:52.130 align:start position:0% Builder API we can iterate very fast we can<01:06:49.920> have<01:06:50.039> some<01:06:50.339> map<01:06:50.640> boosts<01:06:51.180> CR<01:06:51.420> this<01:06:51.780> type<01:06:52.079> of 01:06:52.130 --> 01:06:52.140 align:start position:0% can have some map boosts CR this type of 01:06:52.140 --> 01:06:53.630 align:start position:0% can have some map boosts CR this type of thing<01:06:52.319> and<01:06:52.799> we<01:06:53.039> thought<01:06:53.220> this<01:06:53.400> latest 01:06:53.630 --> 01:06:53.640 align:start position:0% thing and we thought this latest 01:06:53.640 --> 01:06:55.789 align:start position:0% thing and we thought this latest research<01:06:54.059> post<01:06:54.299> does<01:06:54.660> point<01:06:54.900> us<01:06:55.140> to<01:06:55.319> some<01:06:55.500> nice 01:06:55.789 --> 01:06:55.799 align:start position:0% research post does point us to some nice 01:06:55.799 --> 01:06:58.190 align:start position:0% research post does point us to some nice Direction<01:06:56.460> and<01:06:57.059> point<01:06:57.240> out<01:06:57.480> B<01:06:57.599> also<01:06:57.900> has<01:06:58.020> a 01:06:58.190 --> 01:06:58.200 align:start position:0% Direction and point out B also has a 01:06:58.200 --> 01:06:59.990 align:start position:0% Direction and point out B also has a nice<01:06:58.319> research<01:06:58.619> post<01:06:58.799> as<01:06:59.039> well<01:06:59.160> so<01:06:59.400> I'm<01:06:59.819> very 01:06:59.990 --> 01:07:00.000 align:start position:0% nice research post as well so I'm very 01:07:00.000 --> 01:07:01.609 align:start position:0% nice research post as well so I'm very excited<01:07:00.420> for<01:07:00.539> that<01:07:00.660> and<01:07:01.020> I<01:07:01.200> definitely 01:07:01.609 --> 01:07:01.619 align:start position:0% excited for that and I definitely 01:07:01.619 --> 01:07:05.750 align:start position:0% excited for that and I definitely definitely<01:07:02.460> want<01:07:02.640> to<01:07:02.819> prioritize<01:07:03.299> right<01:07:04.260> now 01:07:05.750 --> 01:07:05.760 align:start position:0% definitely want to prioritize right now 01:07:05.760 --> 01:07:09.710 align:start position:0% definitely want to prioritize right now uh<01:07:06.539> I'm<01:07:06.839> very<01:07:07.500> sympathetic<01:07:08.099> to<01:07:08.460> teams<01:07:09.420> who 01:07:09.710 --> 01:07:09.720 align:start position:0% uh I'm very sympathetic to teams who 01:07:09.720 --> 01:07:13.069 align:start position:0% uh I'm very sympathetic to teams who talk<01:07:10.200> about<01:07:10.319> wanting<01:07:10.740> time<01:07:10.920> to<01:07:11.220> uh<01:07:11.700> to<01:07:12.359> work<01:07:12.900> on 01:07:13.069 --> 01:07:13.079 align:start position:0% talk about wanting time to uh to work on 01:07:13.079 --> 01:07:14.690 align:start position:0% talk about wanting time to uh to work on their<01:07:13.260> client<01:07:13.440> and<01:07:13.619> handle<01:07:14.099> their<01:07:14.339> Technical 01:07:14.690 --> 01:07:14.700 align:start position:0% their client and handle their Technical 01:07:14.700 --> 01:07:18.109 align:start position:0% their client and handle their Technical backload<01:07:15.420> and<01:07:15.720> I<01:07:16.200> thought<01:07:16.319> that<01:07:16.819> 4844<01:07:17.819> and 01:07:18.109 --> 01:07:18.119 align:start position:0% backload and I thought that 4844 and 01:07:18.119 --> 01:07:20.089 align:start position:0% backload and I thought that 4844 and withdrawals<01:07:18.720> was<01:07:18.900> a<01:07:19.079> really<01:07:19.140> good<01:07:19.319> example<01:07:19.799> of 01:07:20.089 --> 01:07:20.099 align:start position:0% withdrawals was a really good example of 01:07:20.099 --> 01:07:21.950 align:start position:0% withdrawals was a really good example of they<01:07:20.460> both<01:07:20.640> kind<01:07:20.880> of<01:07:20.940> individually<01:07:21.359> look<01:07:21.660> like 01:07:21.950 --> 01:07:21.960 align:start position:0% they both kind of individually look like 01:07:21.960 --> 01:07:23.569 align:start position:0% they both kind of individually look like okay<01:07:22.200> we've<01:07:22.559> got<01:07:22.680> kind<01:07:22.920> of<01:07:23.039> an<01:07:23.160> idea<01:07:23.339> of<01:07:23.460> how 01:07:23.569 --> 01:07:23.579 align:start position:0% okay we've got kind of an idea of how 01:07:23.579 --> 01:07:25.370 align:start position:0% okay we've got kind of an idea of how these<01:07:23.880> two<01:07:24.000> things<01:07:24.180> are<01:07:24.359> going<01:07:24.480> to<01:07:24.599> work 01:07:25.370 --> 01:07:25.380 align:start position:0% these two things are going to work 01:07:25.380 --> 01:07:27.230 align:start position:0% these two things are going to work but<01:07:25.859> and<01:07:26.099> then<01:07:26.280> putting<01:07:26.579> them<01:07:26.640> in<01:07:26.940> the<01:07:27.059> same 01:07:27.230 --> 01:07:27.240 align:start position:0% but and then putting them in the same 01:07:27.240 --> 01:07:29.870 align:start position:0% but and then putting them in the same Fork<01:07:27.660> actually<01:07:28.319> does<01:07:28.799> increase<01:07:29.099> complexity 01:07:29.870 --> 01:07:29.880 align:start position:0% Fork actually does increase complexity 01:07:29.880 --> 01:07:32.750 align:start position:0% Fork actually does increase complexity uh<01:07:30.780> for<01:07:31.079> you<01:07:31.440> know<01:07:31.500> minor<01:07:32.039> technical<01:07:32.339> reasons 01:07:32.750 --> 01:07:32.760 align:start position:0% uh for you know minor technical reasons 01:07:32.760 --> 01:07:34.450 align:start position:0% uh for you know minor technical reasons I<01:07:32.880> I<01:07:33.059> guess<01:07:33.240> you<01:07:33.660> know<01:07:33.720> we're<01:07:33.839> talking<01:07:34.079> about 01:07:34.450 --> 01:07:34.460 align:start position:0% I I guess you know we're talking about 01:07:34.460 --> 01:07:38.390 align:start position:0% I I guess you know we're talking about uh<01:07:35.460> switching<01:07:36.299> the<01:07:36.599> forking<01:07:37.140> based<01:07:37.619> on<01:07:38.039> a 01:07:38.390 --> 01:07:38.400 align:start position:0% uh switching the forking based on a 01:07:38.400 --> 01:07:41.809 align:start position:0% uh switching the forking based on a block<01:07:38.579> number<01:07:38.819> two<01:07:39.059> based<01:07:39.539> on<01:07:39.780> timestamp<01:07:40.819> and 01:07:41.809 --> 01:07:41.819 align:start position:0% block number two based on timestamp and 01:07:41.819 --> 01:07:44.809 align:start position:0% block number two based on timestamp and you<01:07:42.119> know<01:07:42.240> the<01:07:42.720> the<01:07:42.900> more<01:07:43.319> uh<01:07:43.980> places<01:07:44.280> that<01:07:44.640> you 01:07:44.809 --> 01:07:44.819 align:start position:0% you know the the more uh places that you 01:07:44.819 --> 01:07:48.470 align:start position:0% you know the the more uh places that you have<01:07:44.940> to<01:07:45.299> change<01:07:45.780> in<01:07:46.020> the<01:07:46.140> code<01:07:46.260> base<01:07:46.559> uh 01:07:48.470 --> 01:07:48.480 align:start position:0% have to change in the code base uh 01:07:48.480 --> 01:07:50.510 align:start position:0% have to change in the code base uh the<01:07:49.319> the<01:07:49.500> more<01:07:49.740> work<01:07:49.920> that's<01:07:50.099> going<01:07:50.339> to<01:07:50.460> be 01:07:50.510 --> 01:07:50.520 align:start position:0% the the more work that's going to be 01:07:50.520 --> 01:07:52.670 align:start position:0% the the more work that's going to be right<01:07:50.819> so<01:07:51.119> 4844<01:07:51.900> introduces<01:07:52.380> a<01:07:52.559> new 01:07:52.670 --> 01:07:52.680 align:start position:0% right so 4844 introduces a new 01:07:52.680 --> 01:07:55.190 align:start position:0% right so 4844 introduces a new transaction<01:07:53.400> type<01:07:53.700> which<01:07:54.420> means<01:07:54.780> you<01:07:55.140> know 01:07:55.190 --> 01:07:55.200 align:start position:0% transaction type which means you know 01:07:55.200 --> 01:07:57.410 align:start position:0% transaction type which means you know more<01:07:55.380> places<01:07:55.559> that<01:07:56.039> this<01:07:56.339> forking<01:07:57.059> based<01:07:57.299> on 01:07:57.410 --> 01:07:57.420 align:start position:0% more places that this forking based on 01:07:57.420 --> 01:07:59.569 align:start position:0% more places that this forking based on timestamp<01:07:57.839> has<01:07:58.140> to<01:07:58.380> has<01:07:58.920> to<01:07:59.039> happen<01:07:59.160> for 01:07:59.569 --> 01:07:59.579 align:start position:0% timestamp has to has to happen for 01:07:59.579 --> 01:08:00.829 align:start position:0% timestamp has to has to happen for example<01:07:59.819> so 01:08:00.829 --> 01:08:00.839 align:start position:0% example so 01:08:00.839 --> 01:08:03.230 align:start position:0% example so just<01:08:01.260> an<01:08:01.440> interesting<01:08:01.740> place<01:08:02.039> of<01:08:02.460> seeing<01:08:02.819> why 01:08:03.230 --> 01:08:03.240 align:start position:0% just an interesting place of seeing why 01:08:03.240 --> 01:08:06.230 align:start position:0% just an interesting place of seeing why you<01:08:03.960> might<01:08:04.140> get<01:08:04.440> pushback<01:08:04.859> on<01:08:05.400> hey<01:08:05.760> let's<01:08:06.000> only 01:08:06.230 --> 01:08:06.240 align:start position:0% you might get pushback on hey let's only 01:08:06.240 --> 01:08:09.109 align:start position:0% you might get pushback on hey let's only do<01:08:06.539> one<01:08:07.380> major<01:08:07.619> thing<01:08:07.859> in<01:08:08.160> this<01:08:08.339> next<01:08:08.579> you<01:08:09.000> know 01:08:09.109 --> 01:08:09.119 align:start position:0% do one major thing in this next you know 01:08:09.119 --> 01:08:10.730 align:start position:0% do one major thing in this next you know Fork<01:08:09.480> instead<01:08:09.780> of<01:08:09.839> two<01:08:09.960> and<01:08:10.200> and<01:08:10.319> leave<01:08:10.559> room 01:08:10.730 --> 01:08:10.740 align:start position:0% Fork instead of two and and leave room 01:08:10.740 --> 01:08:11.990 align:start position:0% Fork instead of two and and leave room for<01:08:10.980> maintenance 01:08:11.990 --> 01:08:12.000 align:start position:0% for maintenance 01:08:12.000 --> 01:08:14.809 align:start position:0% for maintenance so<01:08:12.059> so<01:08:12.299> just<01:08:12.960> as<01:08:13.200> an<01:08:13.619> example<01:08:13.859> for<01:08:14.160> this<01:08:14.400> I 01:08:14.809 --> 01:08:14.819 align:start position:0% so so just as an example for this I 01:08:14.819 --> 01:08:16.970 align:start position:0% so so just as an example for this I actually<01:08:15.180> implemented<01:08:15.839> the<01:08:16.140> forking<01:08:16.739> based 01:08:16.970 --> 01:08:16.980 align:start position:0% actually implemented the forking based 01:08:16.980 --> 01:08:19.430 align:start position:0% actually implemented the forking based on<01:08:17.040> timestamps<01:08:17.699> for<01:08:17.940> Shanghai<01:08:18.420> which<01:08:19.199> was 01:08:19.430 --> 01:08:19.440 align:start position:0% on timestamps for Shanghai which was 01:08:19.440 --> 01:08:24.530 align:start position:0% on timestamps for Shanghai which was like<01:08:19.920> uh<01:08:20.640> a<01:08:20.940> 20<01:08:21.179> line<01:08:21.540> change<01:08:22.279> and<01:08:23.279> I<01:08:24.239> looked 01:08:24.530 --> 01:08:24.540 align:start position:0% like uh a 20 line change and I looked 01:08:24.540 --> 01:08:28.490 align:start position:0% like uh a 20 line change and I looked into<01:08:25.219> uh<01:08:26.219> doing<01:08:26.640> the<01:08:26.819> same<01:08:27.000> thing<01:08:27.179> for<01:08:27.839> uh 01:08:28.490 --> 01:08:28.500 align:start position:0% into uh doing the same thing for uh 01:08:28.500 --> 01:08:30.289 align:start position:0% into uh doing the same thing for uh sorry<01:08:28.679> for<01:08:28.980> for<01:08:29.160> withdrawals<01:08:30.000> not<01:08:30.120> for 01:08:30.289 --> 01:08:30.299 align:start position:0% sorry for for withdrawals not for 01:08:30.299 --> 01:08:31.490 align:start position:0% sorry for for withdrawals not for Shanghai 01:08:31.490 --> 01:08:31.500 align:start position:0% Shanghai 01:08:31.500 --> 01:08:34.309 align:start position:0% Shanghai um<01:08:31.759> and<01:08:32.759> I<01:08:33.060> looked<01:08:33.359> into<01:08:33.480> doing<01:08:33.779> the<01:08:34.140> same 01:08:34.309 --> 01:08:34.319 align:start position:0% um and I looked into doing the same 01:08:34.319 --> 01:08:36.530 align:start position:0% um and I looked into doing the same thing<01:08:34.560> for<01:08:34.920> four<01:08:35.160> eight<01:08:35.339> four<01:08:35.580> four<01:08:35.759> and<01:08:36.299> it 01:08:36.530 --> 01:08:36.540 align:start position:0% thing for four eight four four and it 01:08:36.540 --> 01:08:39.590 align:start position:0% thing for four eight four four and it would<01:08:36.660> be<01:08:36.839> like<01:08:37.199> 70<01:08:38.160> different<01:08:38.580> files<01:08:39.179> that<01:08:39.420> I 01:08:39.590 --> 01:08:39.600 align:start position:0% would be like 70 different files that I 01:08:39.600 --> 01:08:41.870 align:start position:0% would be like 70 different files that I would<01:08:40.020> need<01:08:40.140> to<01:08:40.319> touch<01:08:40.500> just<01:08:40.980> for<01:08:41.279> changing 01:08:41.870 --> 01:08:41.880 align:start position:0% would need to touch just for changing 01:08:41.880 --> 01:08:46.130 align:start position:0% would need to touch just for changing the<01:08:42.500> uh<01:08:43.500> changing<01:08:44.279> the<01:08:44.520> way<01:08:44.699> we<01:08:45.000> we<01:08:45.540> verify<01:08:46.020> the 01:08:46.130 --> 01:08:46.140 align:start position:0% the uh changing the way we we verify the 01:08:46.140 --> 01:08:48.769 align:start position:0% the uh changing the way we we verify the signatures<01:08:46.620> and<01:08:46.920> the<01:08:47.219> sign<01:08:47.339> up<01:08:47.580> so 01:08:48.769 --> 01:08:48.779 align:start position:0% signatures and the sign up so 01:08:48.779 --> 01:08:49.550 align:start position:0% signatures and the sign up so um 01:08:49.550 --> 01:08:49.560 align:start position:0% um 01:08:49.560 --> 01:08:51.470 align:start position:0% um it's 01:08:51.470 --> 01:08:51.480 align:start position:0% it's 01:08:51.480 --> 01:08:53.930 align:start position:0% it's individually<01:08:52.319> it's<01:08:52.739> it's<01:08:52.920> okay<01:08:53.400> but<01:08:53.699> together 01:08:53.930 --> 01:08:53.940 align:start position:0% individually it's it's okay but together 01:08:53.940 --> 01:09:01.130 align:start position:0% individually it's it's okay but together it<01:08:54.359> creates<01:08:54.900> uh<01:08:55.440> even<01:08:55.799> more<01:08:55.980> complexity 01:09:01.130 --> 01:09:01.140 align:start position:0% 01:09:01.140 --> 01:09:03.650 align:start position:0% I<01:09:01.440> feel<01:09:01.859> like<01:09:01.980> we've<01:09:02.640> heard<01:09:02.759> a<01:09:02.940> lot<01:09:03.060> of<01:09:03.179> clients 01:09:03.650 --> 01:09:03.660 align:start position:0% I feel like we've heard a lot of clients 01:09:03.660 --> 01:09:07.010 align:start position:0% I feel like we've heard a lot of clients say<01:09:03.960> that<01:09:04.500> they<01:09:04.920> feel<01:09:05.520> that<01:09:06.000> they<01:09:06.719> could<01:09:06.839> spend 01:09:07.010 --> 01:09:07.020 align:start position:0% say that they feel that they could spend 01:09:07.020 --> 01:09:08.630 align:start position:0% say that they feel that they could spend some<01:09:07.199> time<01:09:07.440> cleaning<01:09:08.040> things<01:09:08.219> up<01:09:08.400> in<01:09:08.520> their 01:09:08.630 --> 01:09:08.640 align:start position:0% some time cleaning things up in their 01:09:08.640 --> 01:09:10.910 align:start position:0% some time cleaning things up in their code<01:09:08.819> base<01:09:09.380> improving<01:09:10.380> in<01:09:10.620> you<01:09:10.859> know 01:09:10.910 --> 01:09:10.920 align:start position:0% code base improving in you know 01:09:10.920 --> 01:09:13.249 align:start position:0% code base improving in you know improving<01:09:11.460> things<01:09:11.640> in<01:09:11.819> their<01:09:11.940> code<01:09:12.120> base<01:09:12.359> I'm 01:09:13.249 --> 01:09:13.259 align:start position:0% improving things in their code base I'm 01:09:13.259 --> 01:09:15.829 align:start position:0% improving things in their code base I'm just<01:09:13.500> curious<01:09:13.859> to<01:09:14.040> hear<01:09:14.279> from<01:09:14.819> Tim<01:09:15.359> and<01:09:15.600> from 01:09:15.829 --> 01:09:15.839 align:start position:0% just curious to hear from Tim and from 01:09:15.839 --> 01:09:17.749 align:start position:0% just curious to hear from Tim and from other<01:09:15.960> clients<01:09:16.380> like<01:09:16.560> how<01:09:17.219> should<01:09:17.460> we<01:09:17.640> think 01:09:17.749 --> 01:09:17.759 align:start position:0% other clients like how should we think 01:09:17.759 --> 01:09:20.630 align:start position:0% other clients like how should we think about<01:09:18.000> this<01:09:18.480> in<01:09:19.080> respect<01:09:19.380> to<01:09:19.560> the<01:09:19.859> roadmap<01:09:20.339> and 01:09:20.630 --> 01:09:20.640 align:start position:0% about this in respect to the roadmap and 01:09:20.640 --> 01:09:22.550 align:start position:0% about this in respect to the roadmap and all<01:09:21.120> the<01:09:21.239> things<01:09:21.359> we<01:09:21.540> want<01:09:21.719> to<01:09:21.839> do<01:09:21.960> because<01:09:22.259> it 01:09:22.550 --> 01:09:22.560 align:start position:0% all the things we want to do because it 01:09:22.560 --> 01:09:24.650 align:start position:0% all the things we want to do because it seems<01:09:23.040> like<01:09:23.100> we're<01:09:23.339> consistently<01:09:23.880> saying<01:09:24.299> we 01:09:24.650 --> 01:09:24.660 align:start position:0% seems like we're consistently saying we 01:09:24.660 --> 01:09:26.450 align:start position:0% seems like we're consistently saying we need<01:09:24.779> to<01:09:24.900> ship<01:09:25.080> withdrawals<01:09:25.799> yesterday<01:09:26.100> we 01:09:26.450 --> 01:09:26.460 align:start position:0% need to ship withdrawals yesterday we 01:09:26.460 --> 01:09:27.769 align:start position:0% need to ship withdrawals yesterday we need<01:09:26.580> to<01:09:26.640> ship<01:09:26.819> four<01:09:27.120> eight<01:09:27.239> four<01:09:27.420> four<01:09:27.480> three 01:09:27.769 --> 01:09:27.779 align:start position:0% need to ship four eight four four three 01:09:27.779 --> 01:09:29.090 align:start position:0% need to ship four eight four four three months<01:09:28.080> ago 01:09:29.090 --> 01:09:29.100 align:start position:0% months ago 01:09:29.100 --> 01:09:31.849 align:start position:0% months ago vertical<01:09:29.759> trees<01:09:30.239> all<01:09:30.540> these<01:09:30.779> things<01:09:31.020> and<01:09:31.500> it's 01:09:31.849 --> 01:09:31.859 align:start position:0% vertical trees all these things and it's 01:09:31.859 --> 01:09:34.249 align:start position:0% vertical trees all these things and it's not<01:09:32.040> clear<01:09:32.219> to<01:09:32.520> me<01:09:32.640> how<01:09:33.480> to<01:09:33.600> do<01:09:33.779> that<01:09:33.960> and 01:09:34.249 --> 01:09:34.259 align:start position:0% not clear to me how to do that and 01:09:34.259 --> 01:09:36.590 align:start position:0% not clear to me how to do that and balance<01:09:34.679> and<01:09:35.040> you<01:09:35.339> know<01:09:35.460> maintaining<01:09:36.239> clients 01:09:36.590 --> 01:09:36.600 align:start position:0% balance and you know maintaining clients 01:09:36.600 --> 01:09:40.370 align:start position:0% balance and you know maintaining clients for<01:09:36.839> the<01:09:36.960> long<01:09:37.080> term 01:09:40.370 --> 01:09:40.380 align:start position:0% 01:09:40.380 --> 01:09:42.890 align:start position:0% so<01:09:40.859> well<01:09:41.520> while<01:09:41.819> we<01:09:42.000> say<01:09:42.120> that<01:09:42.299> we<01:09:42.600> want<01:09:42.779> to 01:09:42.890 --> 01:09:42.900 align:start position:0% so well while we say that we want to 01:09:42.900 --> 01:09:44.450 align:start position:0% so well while we say that we want to slow<01:09:43.259> down<01:09:43.500> at<01:09:43.679> the<01:09:43.859> same<01:09:43.920> time<01:09:44.040> I'm<01:09:44.160> thinking 01:09:44.450 --> 01:09:44.460 align:start position:0% slow down at the same time I'm thinking 01:09:44.460 --> 01:09:47.749 align:start position:0% slow down at the same time I'm thinking that<01:09:44.719> nevermind<01:09:45.719> is<01:09:45.900> ready<01:09:46.080> to<01:09:46.440> to<01:09:46.980> think<01:09:47.400> like 01:09:47.749 --> 01:09:47.759 align:start position:0% that nevermind is ready to to think like 01:09:47.759 --> 01:09:50.809 align:start position:0% that nevermind is ready to to think like a<01:09:47.940> big<01:09:48.179> client<01:09:48.480> like<01:09:48.839> the<01:09:48.960> one<01:09:49.140> that<01:09:49.380> is<01:09:49.819> that 01:09:50.809 --> 01:09:50.819 align:start position:0% a big client like the one that is that 01:09:50.819 --> 01:09:53.450 align:start position:0% a big client like the one that is that is<01:09:51.000> leading<01:09:51.480> the<01:09:51.600> effort<01:09:51.960> on<01:09:52.259> the<01:09:52.560> exploration 01:09:53.450 --> 01:09:53.460 align:start position:0% is leading the effort on the exploration 01:09:53.460 --> 01:09:55.189 align:start position:0% is leading the effort on the exploration so<01:09:53.759> so<01:09:54.000> by<01:09:54.179> the<01:09:54.299> fact<01:09:54.420> that<01:09:54.540> we<01:09:54.719> have<01:09:54.840> the<01:09:55.080> large 01:09:55.189 --> 01:09:55.199 align:start position:0% so so by the fact that we have the large 01:09:55.199 --> 01:09:58.010 align:start position:0% so so by the fact that we have the large team<01:09:55.560> uh<01:09:56.219> we<01:09:56.460> can<01:09:56.640> both<01:09:57.000> keep<01:09:57.480> cleaning<01:09:57.900> the 01:09:58.010 --> 01:09:58.020 align:start position:0% team uh we can both keep cleaning the 01:09:58.020 --> 01:09:59.750 align:start position:0% team uh we can both keep cleaning the technical<01:09:58.320> lab<01:09:58.560> but<01:09:58.860> also<01:09:59.160> participate<01:09:59.580> in 01:09:59.750 --> 01:09:59.760 align:start position:0% technical lab but also participate in 01:09:59.760 --> 01:10:02.330 align:start position:0% technical lab but also participate in the<01:09:59.880> research<01:10:00.120> and<01:10:00.300> prototyping<01:10:00.920> uh<01:10:01.920> so<01:10:02.100> so 01:10:02.330 --> 01:10:02.340 align:start position:0% the research and prototyping uh so so 01:10:02.340 --> 01:10:04.370 align:start position:0% the research and prototyping uh so so we've<01:10:02.760> we've<01:10:03.239> seen<01:10:03.420> we've<01:10:03.780> heard<01:10:03.900> that<01:10:04.080> from 01:10:04.370 --> 01:10:04.380 align:start position:0% we've we've seen we've heard that from 01:10:04.380 --> 01:10:07.370 align:start position:0% we've we've seen we've heard that from Mikhail<01:10:05.040> talking<01:10:05.880> about<01:10:06.120> has<01:10:06.960> been<01:10:07.199> guys 01:10:07.370 --> 01:10:07.380 align:start position:0% Mikhail talking about has been guys 01:10:07.380 --> 01:10:09.950 align:start position:0% Mikhail talking about has been guys still<01:10:07.560> there<01:10:07.800> no<01:10:08.040> no<01:10:08.219> okay 01:10:09.950 --> 01:10:09.960 align:start position:0% still there no no okay 01:10:09.960 --> 01:10:11.990 align:start position:0% still there no no okay um<01:10:10.020> so<01:10:10.320> so<01:10:10.560> he<01:10:10.739> was<01:10:10.800> thinking<01:10:11.040> how<01:10:11.219> much<01:10:11.520> it<01:10:11.699> was 01:10:11.990 --> 01:10:12.000 align:start position:0% um so so he was thinking how much it was 01:10:12.000 --> 01:10:13.850 align:start position:0% um so so he was thinking how much it was helpful<01:10:12.480> to<01:10:12.719> have<01:10:12.900> the<01:10:13.199> Prototype<01:10:13.739> from 01:10:13.850 --> 01:10:13.860 align:start position:0% helpful to have the Prototype from 01:10:13.860 --> 01:10:15.650 align:start position:0% helpful to have the Prototype from Guillaume<01:10:14.400> right<01:10:14.580> and<01:10:15.000> and<01:10:15.179> how<01:10:15.480> much 01:10:15.650 --> 01:10:15.660 align:start position:0% Guillaume right and and how much 01:10:15.660 --> 01:10:18.410 align:start position:0% Guillaume right and and how much Maurice's<01:10:16.560> experimentations<01:10:17.400> were<01:10:17.820> pushing 01:10:18.410 --> 01:10:18.420 align:start position:0% Maurice's experimentations were pushing 01:10:18.420 --> 01:10:20.390 align:start position:0% Maurice's experimentations were pushing things<01:10:18.840> forward 01:10:20.390 --> 01:10:20.400 align:start position:0% things forward 01:10:20.400 --> 01:10:22.669 align:start position:0% things forward um so<01:10:20.640> we<01:10:20.880> have<01:10:21.000> those<01:10:21.360> excited<01:10:22.140> people<01:10:22.440> like 01:10:22.669 --> 01:10:22.679 align:start position:0% um so we have those excited people like 01:10:22.679 --> 01:10:25.610 align:start position:0% um so we have those excited people like Alexa<01:10:22.920> you<01:10:23.340> know<01:10:23.460> and<01:10:23.640> that<01:10:23.880> in<01:10:24.060> mind<01:10:24.179> and<01:10:24.780> they 01:10:25.610 --> 01:10:25.620 align:start position:0% Alexa you know and that in mind and they 01:10:25.620 --> 01:10:26.930 align:start position:0% Alexa you know and that in mind and they they<01:10:25.860> want<01:10:26.040> to<01:10:26.159> explore<01:10:26.460> they<01:10:26.699> want<01:10:26.820> to 01:10:26.930 --> 01:10:26.940 align:start position:0% they want to explore they want to 01:10:26.940 --> 01:10:28.430 align:start position:0% they want to explore they want to experiment<01:10:27.300> and<01:10:27.719> this<01:10:27.840> should<01:10:28.020> help<01:10:28.199> everyone 01:10:28.430 --> 01:10:28.440 align:start position:0% experiment and this should help everyone 01:10:28.440 --> 01:10:30.649 align:start position:0% experiment and this should help everyone to<01:10:28.800> to<01:10:28.980> push<01:10:29.159> things<01:10:29.400> forward<01:10:29.699> and<01:10:30.060> and<01:10:30.420> these 01:10:30.649 --> 01:10:30.659 align:start position:0% to to push things forward and and these 01:10:30.659 --> 01:10:32.030 align:start position:0% to to push things forward and and these deliveries<01:10:31.020> are<01:10:31.199> critical<01:10:31.560> and<01:10:31.860> they're 01:10:32.030 --> 01:10:32.040 align:start position:0% deliveries are critical and they're 01:10:32.040 --> 01:10:34.189 align:start position:0% deliveries are critical and they're still<01:10:32.219> time<01:10:32.520> critical<01:10:32.940> I'll<01:10:33.719> be<01:10:33.900> doing<01:10:34.020> that 01:10:34.189 --> 01:10:34.199 align:start position:0% still time critical I'll be doing that 01:10:34.199 --> 01:10:36.590 align:start position:0% still time critical I'll be doing that in<01:10:34.380> parallel<01:10:34.679> even<01:10:34.920> if<01:10:35.159> the<01:10:35.280> field<01:10:35.460> will<01:10:35.760> be 01:10:36.590 --> 01:10:36.600 align:start position:0% in parallel even if the field will be 01:10:36.600 --> 01:10:40.189 align:start position:0% in parallel even if the field will be we<01:10:37.140> change<01:10:37.679> this<01:10:38.040> style<01:10:38.540> uh<01:10:39.540> that's<01:10:39.780> that<01:10:40.080> we 01:10:40.189 --> 01:10:40.199 align:start position:0% we change this style uh that's that we 01:10:40.199 --> 01:10:41.870 align:start position:0% we change this style uh that's that we do<01:10:40.380> that<01:10:40.500> a<01:10:40.679> bit<01:10:40.739> more<01:10:40.860> mature<01:10:41.340> way<01:10:41.520> I<01:10:41.760> think 01:10:41.870 --> 01:10:41.880 align:start position:0% do that a bit more mature way I think 01:10:41.880 --> 01:10:43.430 align:start position:0% do that a bit more mature way I think that<01:10:42.000> maturity<01:10:42.480> will<01:10:42.659> come<01:10:42.840> also<01:10:43.080> from<01:10:43.320> the 01:10:43.430 --> 01:10:43.440 align:start position:0% that maturity will come also from the 01:10:43.440 --> 01:10:44.750 align:start position:0% that maturity will come also from the learning<01:10:43.679> from<01:10:43.920> the<01:10:44.040> merge<01:10:44.340> and<01:10:44.460> from<01:10:44.580> the 01:10:44.750 --> 01:10:44.760 align:start position:0% learning from the merge and from the 01:10:44.760 --> 01:10:47.570 align:start position:0% learning from the merge and from the team<01:10:44.880> being<01:10:45.120> larger<01:10:45.600> so 01:10:47.570 --> 01:10:47.580 align:start position:0% team being larger so 01:10:47.580 --> 01:10:49.490 align:start position:0% team being larger so I<01:10:48.060> think<01:10:48.239> on<01:10:48.420> average<01:10:48.600> the<01:10:48.900> teams<01:10:49.140> grew<01:10:49.380> about 01:10:49.490 --> 01:10:49.500 align:start position:0% I think on average the teams grew about 01:10:49.500 --> 01:10:51.770 align:start position:0% I think on average the teams grew about like<01:10:49.800> two<01:10:49.920> to<01:10:50.100> three<01:10:50.280> times<01:10:50.460> in<01:10:51.300> the<01:10:51.420> last<01:10:51.540> two 01:10:51.770 --> 01:10:51.780 align:start position:0% like two to three times in the last two 01:10:51.780 --> 01:10:54.950 align:start position:0% like two to three times in the last two years<01:10:51.960> on<01:10:52.440> many<01:10:52.620> of<01:10:52.800> the<01:10:53.040> clients<01:10:53.820> teams<01:10:54.239> which 01:10:54.950 --> 01:10:54.960 align:start position:0% years on many of the clients teams which 01:10:54.960 --> 01:10:57.649 align:start position:0% years on many of the clients teams which means<01:10:55.320> that<01:10:56.040> we<01:10:56.699> should<01:10:56.880> be<01:10:57.000> able<01:10:57.239> to<01:10:57.360> ship 01:10:57.649 --> 01:10:57.659 align:start position:0% means that we should be able to ship 01:10:57.659 --> 01:10:58.610 align:start position:0% means that we should be able to ship faster 01:10:58.610 --> 01:10:58.620 align:start position:0% faster 01:10:58.620 --> 01:11:01.010 align:start position:0% faster than<01:10:59.580> in<01:10:59.760> the<01:10:59.880> past<01:11:00.000> and<01:11:00.300> when<01:11:00.480> we<01:11:00.600> look<01:11:00.719> at<01:11:00.840> the 01:11:01.010 --> 01:11:01.020 align:start position:0% than in the past and when we look at the 01:11:01.020 --> 01:11:05.270 align:start position:0% than in the past and when we look at the last<01:11:01.199> two<01:11:01.380> years<01:11:01.620> comparing<01:11:02.280> to<01:11:02.520> the<01:11:02.880> 2018-19 01:11:05.270 --> 01:11:05.280 align:start position:0% last two years comparing to the 2018-19 01:11:05.280 --> 01:11:07.370 align:start position:0% last two years comparing to the 2018-19 uh<01:11:06.000> we've<01:11:06.239> seen<01:11:06.360> that<01:11:06.540> we've<01:11:06.719> seen<01:11:06.900> that<01:11:07.080> pace 01:11:07.370 --> 01:11:07.380 align:start position:0% uh we've seen that we've seen that pace 01:11:07.380 --> 01:11:09.709 align:start position:0% uh we've seen that we've seen that pace and<01:11:08.219> there<01:11:08.460> is<01:11:08.640> much<01:11:08.760> more<01:11:09.000> experience<01:11:09.360> with 01:11:09.709 --> 01:11:09.719 align:start position:0% and there is much more experience with 01:11:09.719 --> 01:11:11.750 align:start position:0% and there is much more experience with the<01:11:09.900> teams<01:11:10.260> people<01:11:10.860> delivered<01:11:11.340> so<01:11:11.580> much 01:11:11.750 --> 01:11:11.760 align:start position:0% the teams people delivered so much 01:11:11.760 --> 01:11:13.550 align:start position:0% the teams people delivered so much during<01:11:12.000> the<01:11:12.179> merch<01:11:12.480> and<01:11:12.719> they<01:11:12.960> they<01:11:13.320> are 01:11:13.550 --> 01:11:13.560 align:start position:0% during the merch and they they are 01:11:13.560 --> 01:11:15.590 align:start position:0% during the merch and they they are interested<01:11:13.920> in<01:11:14.159> now<01:11:14.460> delivering<01:11:15.300> the<01:11:15.420> things 01:11:15.590 --> 01:11:15.600 align:start position:0% interested in now delivering the things 01:11:15.600 --> 01:11:17.149 align:start position:0% interested in now delivering the things that<01:11:15.840> they<01:11:15.960> wanted<01:11:16.140> to<01:11:16.380> work<01:11:16.500> on<01:11:16.679> the<01:11:16.860> side<01:11:16.980> and 01:11:17.149 --> 01:11:17.159 align:start position:0% that they wanted to work on the side and 01:11:17.159 --> 01:11:18.470 align:start position:0% that they wanted to work on the side and many<01:11:17.340> of<01:11:17.460> those<01:11:17.640> things<01:11:17.820> that<01:11:18.000> they<01:11:18.179> wanted<01:11:18.300> to 01:11:18.470 --> 01:11:18.480 align:start position:0% many of those things that they wanted to 01:11:18.480 --> 01:11:20.149 align:start position:0% many of those things that they wanted to work<01:11:18.600> on<01:11:18.780> the<01:11:18.900> side<01:11:19.020> are<01:11:19.260> the<01:11:19.380> EIP<01:11:19.679> is<01:11:19.980> already 01:11:20.149 --> 01:11:20.159 align:start position:0% work on the side are the EIP is already 01:11:20.159 --> 01:11:22.729 align:start position:0% work on the side are the EIP is already are<01:11:20.820> the<01:11:21.000> items<01:11:21.360> that<01:11:21.600> are<01:11:21.840> interesting<01:11:22.560> like 01:11:22.729 --> 01:11:22.739 align:start position:0% are the items that are interesting like 01:11:22.739 --> 01:11:26.750 align:start position:0% are the items that are interesting like 4844<01:11:23.460> right<01:11:24.199> so<01:11:25.199> this<01:11:25.739> will<01:11:25.920> happen<01:11:26.100> I<01:11:26.520> think 01:11:26.750 --> 01:11:26.760 align:start position:0% 4844 right so this will happen I think 01:11:26.760 --> 01:11:30.350 align:start position:0% 4844 right so this will happen I think this<01:11:26.880> will<01:11:27.060> happen 01:11:30.350 --> 01:11:30.360 align:start position:0% 01:11:30.360 --> 01:11:32.689 align:start position:0% but<01:11:31.199> it's<01:11:31.380> also<01:11:31.739> another<01:11:31.920> factor<01:11:32.400> that<01:11:32.520> we 01:11:32.689 --> 01:11:32.699 align:start position:0% but it's also another factor that we 01:11:32.699 --> 01:11:34.550 align:start position:0% but it's also another factor that we need<01:11:32.760> to<01:11:32.880> consider<01:11:33.239> yeah<01:11:33.420> but<01:11:33.719> like<01:11:33.960> changing 01:11:34.550 --> 01:11:34.560 align:start position:0% need to consider yeah but like changing 01:11:34.560 --> 01:11:37.669 align:start position:0% need to consider yeah but like changing let's<01:11:34.980> say<01:11:35.100> 10<01:11:35.400> lines<01:11:35.699> of<01:11:35.940> code<01:11:36.120> or<01:11:36.540> 17<01:11:36.960> files 01:11:37.669 --> 01:11:37.679 align:start position:0% let's say 10 lines of code or 17 files 01:11:37.679 --> 01:11:40.070 align:start position:0% let's say 10 lines of code or 17 files two<01:11:38.219> years<01:11:38.400> ago<01:11:38.699> was<01:11:39.480> completely<01:11:39.840> different 01:11:40.070 --> 01:11:40.080 align:start position:0% two years ago was completely different 01:11:40.080 --> 01:11:42.350 align:start position:0% two years ago was completely different than<01:11:40.679> changing<01:11:41.159> the<01:11:41.280> same<01:11:41.520> amount<01:11:41.760> of<01:11:41.940> files 01:11:42.350 --> 01:11:42.360 align:start position:0% than changing the same amount of files 01:11:42.360 --> 01:11:44.630 align:start position:0% than changing the same amount of files right<01:11:42.719> now<01:11:42.900> the<01:11:43.560> code<01:11:43.679> base<01:11:43.920> is<01:11:44.159> much<01:11:44.340> bigger 01:11:44.630 --> 01:11:44.640 align:start position:0% right now the code base is much bigger 01:11:44.640 --> 01:11:47.870 align:start position:0% right now the code base is much bigger the<01:11:45.000> complexity<01:11:45.480> is<01:11:45.659> much<01:11:45.980> uh<01:11:46.980> bigger<01:11:47.340> and<01:11:47.640> you 01:11:47.870 --> 01:11:47.880 align:start position:0% the complexity is much uh bigger and you 01:11:47.880 --> 01:11:49.930 align:start position:0% the complexity is much uh bigger and you know<01:11:48.000> sometimes<01:11:48.719> you<01:11:48.900> know<01:11:49.020> Small<01:11:49.320> Change 01:11:49.930 --> 01:11:49.940 align:start position:0% know sometimes you know Small Change 01:11:49.940 --> 01:11:53.450 align:start position:0% know sometimes you know Small Change requires<01:11:50.940> you<01:11:51.300> know<01:11:51.420> days<01:11:51.840> or<01:11:52.199> maybe<01:11:52.320> weeks<01:11:52.860> of 01:11:53.450 --> 01:11:53.460 align:start position:0% requires you know days or maybe weeks of 01:11:53.460 --> 01:11:55.370 align:start position:0% requires you know days or maybe weeks of you<01:11:53.699> know<01:11:53.760> research<01:11:54.179> yeah<01:11:54.360> and<01:11:54.600> testing<01:11:55.140> and 01:11:55.370 --> 01:11:55.380 align:start position:0% you know research yeah and testing and 01:11:55.380 --> 01:11:56.870 align:start position:0% you know research yeah and testing and testing<01:11:55.679> especially<01:11:56.100> testing<01:11:56.520> here<01:11:56.640> it's 01:11:56.870 --> 01:11:56.880 align:start position:0% testing especially testing here it's 01:11:56.880 --> 01:12:00.350 align:start position:0% testing especially testing here it's something<01:11:57.060> that<01:11:57.500> we<01:11:58.500> need<01:11:58.620> to<01:11:58.739> improve<01:11:59.159> and<01:12:00.060> so 01:12:00.350 --> 01:12:00.360 align:start position:0% something that we need to improve and so 01:12:00.360 --> 01:12:02.689 align:start position:0% something that we need to improve and so yeah<01:12:00.600> the<01:12:00.840> teams<01:12:01.140> grow<01:12:01.380> grew<01:12:01.980> but<01:12:02.219> at<01:12:02.460> the<01:12:02.580> same 01:12:02.689 --> 01:12:02.699 align:start position:0% yeah the teams grow grew but at the same 01:12:02.699 --> 01:12:04.910 align:start position:0% yeah the teams grow grew but at the same time<01:12:02.940> it<01:12:03.540> takes<01:12:03.659> much<01:12:03.960> I<01:12:04.320> think<01:12:04.440> it's<01:12:04.679> going<01:12:04.860> to 01:12:04.910 --> 01:12:04.920 align:start position:0% time it takes much I think it's going to 01:12:04.920 --> 01:12:07.310 align:start position:0% time it takes much I think it's going to take<01:12:05.040> much<01:12:05.280> much<01:12:05.520> time<01:12:05.820> to<01:12:06.120> deliver<01:12:06.320> similar 01:12:07.310 --> 01:12:07.320 align:start position:0% take much much time to deliver similar 01:12:07.320 --> 01:12:11.810 align:start position:0% take much much time to deliver similar change<01:12:07.500> as<01:12:08.340> the<01:12:08.880> ones<01:12:09.120> in<01:12:09.300> the<01:12:09.420> past 01:12:11.810 --> 01:12:11.820 align:start position:0% 01:12:11.820 --> 01:12:13.370 align:start position:0% um if<01:12:12.060> I<01:12:12.239> can<01:12:12.360> add<01:12:12.480> something<01:12:12.659> else<01:12:12.900> and<01:12:13.199> on 01:12:13.370 --> 01:12:13.380 align:start position:0% um if I can add something else and on 01:12:13.380 --> 01:12:15.430 align:start position:0% um if I can add something else and on clients 01:12:15.430 --> 01:12:15.440 align:start position:0% clients 01:12:15.440 --> 01:12:20.570 align:start position:0% clients the<01:12:16.440> right<01:12:17.219> now<01:12:17.659> testing<01:12:18.659> is<01:12:19.380> not<01:12:19.560> much 01:12:20.570 --> 01:12:20.580 align:start position:0% the right now testing is not much 01:12:20.580 --> 01:12:22.910 align:start position:0% the right now testing is not much like<01:12:21.000> the<01:12:21.239> experienced<01:12:21.719> with<01:12:22.199> testing<01:12:22.679> is<01:12:22.800> not 01:12:22.910 --> 01:12:22.920 align:start position:0% like the experienced with testing is not 01:12:22.920 --> 01:12:24.169 align:start position:0% like the experienced with testing is not much<01:12:23.040> better<01:12:23.280> than<01:12:23.580> the<01:12:23.820> experience 01:12:24.169 --> 01:12:24.179 align:start position:0% much better than the experience 01:12:24.179 --> 01:12:28.669 align:start position:0% much better than the experience introducing<01:12:24.840> an<01:12:25.080> EIP<01:12:25.520> I<01:12:26.520> think<01:12:26.640> we<01:12:27.060> need<01:12:27.239> a<01:12:27.960> a 01:12:28.669 --> 01:12:28.679 align:start position:0% introducing an EIP I think we need a a 01:12:28.679 --> 01:12:30.470 align:start position:0% introducing an EIP I think we need a a better<01:12:28.860> platform<01:12:29.340> to<01:12:29.760> discuss<01:12:30.000> like<01:12:30.300> the 01:12:30.470 --> 01:12:30.480 align:start position:0% better platform to discuss like the 01:12:30.480 --> 01:12:33.590 align:start position:0% better platform to discuss like the bottlenecks<01:12:31.080> of<01:12:31.140> ethereum<01:12:31.620> to<01:12:32.219> understand<01:12:32.600> it 01:12:33.590 --> 01:12:33.600 align:start position:0% bottlenecks of ethereum to understand it 01:12:33.600 --> 01:12:36.890 align:start position:0% bottlenecks of ethereum to understand it like<01:12:33.900> the<01:12:34.199> complexity<01:12:34.800> of<01:12:35.239> syncing<01:12:36.239> of<01:12:36.600> disk 01:12:36.890 --> 01:12:36.900 align:start position:0% like the complexity of syncing of disk 01:12:36.900 --> 01:12:39.530 align:start position:0% like the complexity of syncing of disk IO<01:12:37.199> and<01:12:37.440> so<01:12:37.560> on<01:12:38.159> and 01:12:39.530 --> 01:12:39.540 align:start position:0% IO and so on and 01:12:39.540 --> 01:12:42.770 align:start position:0% IO and so on and tools<01:12:40.320> like<01:12:40.500> Hive<01:12:40.739> they<01:12:41.699> are<01:12:41.820> just<01:12:42.060> a<01:12:42.239> stagnant 01:12:42.770 --> 01:12:42.780 align:start position:0% tools like Hive they are just a stagnant 01:12:42.780 --> 01:12:45.649 align:start position:0% tools like Hive they are just a stagnant sometimes<01:12:43.620> as<01:12:44.340> the<01:12:44.580> clients<01:12:44.880> themselves<01:12:45.239> when 01:12:45.649 --> 01:12:45.659 align:start position:0% sometimes as the clients themselves when 01:12:45.659 --> 01:12:47.090 align:start position:0% sometimes as the clients themselves when it<01:12:45.840> comes<01:12:46.020> to<01:12:46.080> making<01:12:46.260> changes<01:12:46.739> or 01:12:47.090 --> 01:12:47.100 align:start position:0% it comes to making changes or 01:12:47.100 --> 01:12:49.250 align:start position:0% it comes to making changes or improvements 01:12:49.250 --> 01:12:49.260 align:start position:0% improvements 01:12:49.260 --> 01:12:51.430 align:start position:0% improvements um maybe<01:12:49.739> we're<01:12:50.159> talking<01:12:50.460> about<01:12:50.640> awkward<01:12:51.120> off 01:12:51.430 --> 01:12:51.440 align:start position:0% um maybe we're talking about awkward off 01:12:51.440 --> 01:12:53.990 align:start position:0% um maybe we're talking about awkward off changes<01:12:52.440> maybe<01:12:52.620> you<01:12:52.860> should<01:12:52.980> have<01:12:53.159> like<01:12:53.400> a 01:12:53.990 --> 01:12:54.000 align:start position:0% changes maybe you should have like a 01:12:54.000 --> 01:12:56.810 align:start position:0% changes maybe you should have like a regular<01:12:54.360> breakout<01:12:54.960> for<01:12:55.199> testing<01:12:55.980> maybe<01:12:56.460> we 01:12:56.810 --> 01:12:56.820 align:start position:0% regular breakout for testing maybe we 01:12:56.820 --> 01:12:58.550 align:start position:0% regular breakout for testing maybe we should<01:12:56.940> have<01:12:57.120> more<01:12:57.540> of<01:12:57.719> this<01:12:57.840> platform<01:12:58.199> to 01:12:58.550 --> 01:12:58.560 align:start position:0% should have more of this platform to 01:12:58.560 --> 01:13:01.850 align:start position:0% should have more of this platform to discuss<01:12:59.060> how<01:13:00.060> we<01:13:00.239> get<01:13:00.420> out<01:13:00.780> of<01:13:00.960> this 01:13:01.850 --> 01:13:01.860 align:start position:0% discuss how we get out of this 01:13:01.860 --> 01:13:04.669 align:start position:0% discuss how we get out of this this<01:13:02.280> stacked<01:13:02.699> up<01:13:02.820> into<01:13:03.600> a<01:13:03.960> place<01:13:04.080> where<01:13:04.440> we 01:13:04.669 --> 01:13:04.679 align:start position:0% this stacked up into a place where we 01:13:04.679 --> 01:13:08.270 align:start position:0% this stacked up into a place where we can<01:13:04.800> be<01:13:05.219> excited<01:13:05.640> about<01:13:05.820> new<01:13:06.060> eips<01:13:06.800> so<01:13:07.800> so<01:13:07.980> one 01:13:08.270 --> 01:13:08.280 align:start position:0% can be excited about new eips so so one 01:13:08.280 --> 01:13:10.370 align:start position:0% can be excited about new eips so so one thing<01:13:08.400> about<01:13:08.640> Hive<01:13:09.360> is<01:13:09.659> that<01:13:09.840> it's<01:13:10.080> currently 01:13:10.370 --> 01:13:10.380 align:start position:0% thing about Hive is that it's currently 01:13:10.380 --> 01:13:13.550 align:start position:0% thing about Hive is that it's currently maintained<01:13:10.800> by<01:13:10.980> the<01:13:11.100> guest<01:13:11.340> team<01:13:11.840> and<01:13:12.840> we're 01:13:13.550 --> 01:13:13.560 align:start position:0% maintained by the guest team and we're 01:13:13.560 --> 01:13:15.830 align:start position:0% maintained by the guest team and we're slowly<01:13:14.159> transitioning<01:13:14.820> this<01:13:15.060> over<01:13:15.300> to<01:13:15.659> the 01:13:15.830 --> 01:13:15.840 align:start position:0% slowly transitioning this over to the 01:13:15.840 --> 01:13:18.830 align:start position:0% slowly transitioning this over to the testing<01:13:16.199> team<01:13:16.440> so<01:13:17.219> Mario<01:13:17.580> wrote<01:13:18.179> a<01:13:18.600> lot<01:13:18.719> of 01:13:18.830 --> 01:13:18.840 align:start position:0% testing team so Mario wrote a lot of 01:13:18.840 --> 01:13:20.570 align:start position:0% testing team so Mario wrote a lot of Hive<01:13:19.140> tests<01:13:19.560> for<01:13:19.679> the<01:13:19.800> merch<01:13:20.100> basically<01:13:20.340> all 01:13:20.570 --> 01:13:20.580 align:start position:0% Hive tests for the merch basically all 01:13:20.580 --> 01:13:24.050 align:start position:0% Hive tests for the merch basically all of<01:13:21.000> the<01:13:21.120> hive<01:13:21.360> tabs<01:13:21.719> tests<01:13:22.440> for<01:13:22.560> the<01:13:22.679> merge<01:13:23.060> and 01:13:24.050 --> 01:13:24.060 align:start position:0% of the hive tabs tests for the merge and 01:13:24.060 --> 01:13:25.790 align:start position:0% of the hive tabs tests for the merge and so 01:13:25.790 --> 01:13:25.800 align:start position:0% so 01:13:25.800 --> 01:13:28.790 align:start position:0% so as<01:13:26.280> I<01:13:26.460> said<01:13:26.580> we're<01:13:26.880> trying<01:13:27.120> to<01:13:27.540> increase<01:13:27.840> uh 01:13:28.790 --> 01:13:28.800 align:start position:0% as I said we're trying to increase uh 01:13:28.800 --> 01:13:30.770 align:start position:0% as I said we're trying to increase uh we're<01:13:29.159> trying<01:13:29.580> to<01:13:29.760> ramp<01:13:29.940> up<01:13:30.120> the<01:13:30.360> size<01:13:30.480> of<01:13:30.659> the 01:13:30.770 --> 01:13:30.780 align:start position:0% we're trying to ramp up the size of the 01:13:30.780 --> 01:13:32.510 align:start position:0% we're trying to ramp up the size of the testing<01:13:31.080> team<01:13:31.260> within<01:13:31.739> the<01:13:31.800> ECM<01:13:32.219> foundation 01:13:32.510 --> 01:13:32.520 align:start position:0% testing team within the ECM foundation 01:13:32.520 --> 01:13:35.450 align:start position:0% testing team within the ECM foundation and<01:13:32.760> that<01:13:33.060> should<01:13:33.239> take<01:13:33.540> some<01:13:33.900> local<01:13:34.199> hey<01:13:34.560> I'd 01:13:35.450 --> 01:13:35.460 align:start position:0% and that should take some local hey I'd 01:13:35.460 --> 01:13:37.490 align:start position:0% and that should take some local hey I'd like<01:13:35.699> that<01:13:35.940> if<01:13:36.420> your<01:13:36.480> information<01:13:36.659> is<01:13:37.080> helping 01:13:37.490 --> 01:13:37.500 align:start position:0% like that if your information is helping 01:13:37.500 --> 01:13:39.709 align:start position:0% like that if your information is helping but<01:13:38.100> I<01:13:38.280> don't<01:13:38.460> think<01:13:38.699> the<01:13:38.940> right<01:13:39.060> solution<01:13:39.420> is 01:13:39.709 --> 01:13:39.719 align:start position:0% but I don't think the right solution is 01:13:39.719 --> 01:13:43.010 align:start position:0% but I don't think the right solution is to<01:13:39.900> limit<01:13:40.080> it<01:13:40.320> to<01:13:40.500> one<01:13:40.679> team<01:13:40.980> no<01:13:41.699> I<01:13:42.300> agree<01:13:42.480> so<01:13:42.900> I 01:13:43.010 --> 01:13:43.020 align:start position:0% to limit it to one team no I agree so I 01:13:43.020 --> 01:13:46.130 align:start position:0% to limit it to one team no I agree so I think<01:13:43.199> as<01:13:43.980> like<01:13:44.340> an<01:13:44.520> open<01:13:44.640> call<01:13:44.940> to<01:13:45.179> anybody<01:13:45.540> if 01:13:46.130 --> 01:13:46.140 align:start position:0% think as like an open call to anybody if 01:13:46.140 --> 01:13:48.709 align:start position:0% think as like an open call to anybody if you<01:13:46.380> are<01:13:46.500> a<01:13:46.800> testing<01:13:47.159> team<01:13:47.400> and<01:13:48.179> like<01:13:48.360> you<01:13:48.600> want 01:13:48.709 --> 01:13:48.719 align:start position:0% you are a testing team and like you want 01:13:48.719 --> 01:13:50.930 align:start position:0% you are a testing team and like you want to<01:13:48.840> work<01:13:49.020> on<01:13:49.199> this<01:13:49.380> stuff<01:13:49.560> ping<01:13:50.280> Danny<01:13:50.760> Ryan 01:13:50.930 --> 01:13:50.940 align:start position:0% to work on this stuff ping Danny Ryan 01:13:50.940 --> 01:13:54.050 align:start position:0% to work on this stuff ping Danny Ryan and<01:13:51.659> he<01:13:51.780> will<01:13:51.960> answer<01:13:52.199> you<01:13:52.500> any<01:13:52.920> hour<01:13:53.460> or<01:13:53.820> day 01:13:54.050 --> 01:13:54.060 align:start position:0% and he will answer you any hour or day 01:13:54.060 --> 01:13:56.450 align:start position:0% and he will answer you any hour or day any<01:13:54.659> minute<01:13:55.020> of<01:13:55.500> any<01:13:55.739> hour<01:13:55.920> of<01:13:56.100> every<01:13:56.280> day 01:13:56.450 --> 01:13:56.460 align:start position:0% any minute of any hour of every day 01:13:56.460 --> 01:13:58.850 align:start position:0% any minute of any hour of every day about<01:13:57.060> improved<01:13:57.600> testing<01:13:57.960> capacity<01:13:58.380> and<01:13:58.800> I 01:13:58.850 --> 01:13:58.860 align:start position:0% about improved testing capacity and I 01:13:58.860 --> 01:14:00.770 align:start position:0% about improved testing capacity and I think<01:13:59.280> like<01:13:59.760> I<01:13:59.940> agree<01:14:00.120> it's<01:14:00.300> like<01:14:00.420> a<01:14:00.540> huge<01:14:00.600> ball 01:14:00.770 --> 01:14:00.780 align:start position:0% think like I agree it's like a huge ball 01:14:00.780 --> 01:14:03.050 align:start position:0% think like I agree it's like a huge ball deck<01:14:01.080> to<01:14:01.440> be<01:14:01.500> fair<01:14:01.620> I<01:14:01.800> feel<01:14:01.920> like<01:14:02.040> the<01:14:02.159> merge<01:14:02.520> we 01:14:03.050 --> 01:14:03.060 align:start position:0% deck to be fair I feel like the merge we 01:14:03.060 --> 01:14:04.910 align:start position:0% deck to be fair I feel like the merge we did<01:14:03.300> like<01:14:03.540> an<01:14:03.719> amazing<01:14:04.080> job<01:14:04.380> there<01:14:04.560> like 01:14:04.910 --> 01:14:04.920 align:start position:0% did like an amazing job there like 01:14:04.920 --> 01:14:06.590 align:start position:0% did like an amazing job there like relative<01:14:05.219> to<01:14:05.400> what<01:14:05.520> it<01:14:05.699> was<01:14:05.760> before<01:14:05.940> like<01:14:06.420> when 01:14:06.590 --> 01:14:06.600 align:start position:0% relative to what it was before like when 01:14:06.600 --> 01:14:08.450 align:start position:0% relative to what it was before like when we<01:14:06.780> shipped<01:14:06.960> 1559<01:14:07.560> I<01:14:07.679> was<01:14:07.800> like 01:14:08.450 --> 01:14:08.460 align:start position:0% we shipped 1559 I was like 01:14:08.460 --> 01:14:12.290 align:start position:0% we shipped 1559 I was like not<01:14:09.239> 100<01:14:09.780> confident<01:14:10.739> I<01:14:11.340> was<01:14:11.520> like<01:14:11.580> and<01:14:12.179> then 01:14:12.290 --> 01:14:12.300 align:start position:0% not 100 confident I was like and then 01:14:12.300 --> 01:14:15.110 align:start position:0% not 100 confident I was like and then when<01:14:13.199> the<01:14:13.380> merge<01:14:13.620> went<01:14:13.800> live<01:14:13.980> uh<01:14:14.640> you<01:14:15.000> know 01:14:15.110 --> 01:14:15.120 align:start position:0% when the merge went live uh you know 01:14:15.120 --> 01:14:16.970 align:start position:0% when the merge went live uh you know like<01:14:15.300> I<01:14:15.540> was<01:14:15.659> expecting<01:14:16.080> some<01:14:16.320> operator<01:14:16.679> to 01:14:16.970 --> 01:14:16.980 align:start position:0% like I was expecting some operator to 01:14:16.980 --> 01:14:19.130 align:start position:0% like I was expecting some operator to mess<01:14:17.159> it<01:14:17.280> up<01:14:17.460> but<01:14:17.699> not<01:14:17.940> like<01:14:18.239> the<01:14:18.659> network<01:14:18.780> to 01:14:19.130 --> 01:14:19.140 align:start position:0% mess it up but not like the network to 01:14:19.140 --> 01:14:21.050 align:start position:0% mess it up but not like the network to break<01:14:19.320> like<01:14:19.560> it<01:14:19.800> felt<01:14:20.159> like<01:14:20.219> the<01:14:20.400> testing<01:14:20.760> was 01:14:21.050 --> 01:14:21.060 align:start position:0% break like it felt like the testing was 01:14:21.060 --> 01:14:22.610 align:start position:0% break like it felt like the testing was like<01:14:21.179> super<01:14:21.420> robust 01:14:22.610 --> 01:14:22.620 align:start position:0% like super robust 01:14:22.620 --> 01:14:26.030 align:start position:0% like super robust um<01:14:22.739> and<01:14:23.640> and<01:14:24.120> and<01:14:24.120> the<01:14:24.480> challenge<01:14:25.040> the 01:14:26.030 --> 01:14:26.040 align:start position:0% um and and and the challenge the 01:14:26.040 --> 01:14:27.470 align:start position:0% um and and and the challenge the challenge<01:14:26.219> I<01:14:26.460> think<01:14:26.580> with<01:14:26.760> shipping<01:14:27.179> I'll 01:14:27.470 --> 01:14:27.480 align:start position:0% challenge I think with shipping I'll 01:14:27.480 --> 01:14:29.630 align:start position:0% challenge I think with shipping I'll live<01:14:27.659> like<01:14:27.900> this<01:14:28.080> complicated<01:14:28.679> stuff<01:14:29.040> is 01:14:29.630 --> 01:14:29.640 align:start position:0% live like this complicated stuff is 01:14:29.640 --> 01:14:31.610 align:start position:0% live like this complicated stuff is often<01:14:29.940> not<01:14:30.179> like<01:14:30.480> not<01:14:31.020> just<01:14:31.140> that<01:14:31.320> it's<01:14:31.500> hard 01:14:31.610 --> 01:14:31.620 align:start position:0% often not like not just that it's hard 01:14:31.620 --> 01:14:33.590 align:start position:0% often not like not just that it's hard but<01:14:31.800> it's<01:14:31.920> like<01:14:32.040> it<01:14:32.219> changes<01:14:32.580> the<01:14:32.820> shape<01:14:33.120> of 01:14:33.590 --> 01:14:33.600 align:start position:0% but it's like it changes the shape of 01:14:33.600 --> 01:14:35.510 align:start position:0% but it's like it changes the shape of the<01:14:33.719> network<01:14:33.900> like<01:14:34.500> it's<01:14:34.679> easy<01:14:34.920> to<01:14:35.219> add<01:14:35.340> the 01:14:35.510 --> 01:14:35.520 align:start position:0% the network like it's easy to add the 01:14:35.520 --> 01:14:37.130 align:start position:0% the network like it's easy to add the new<01:14:35.699> OP<01:14:35.880> code<01:14:36.060> right<01:14:36.300> and<01:14:36.480> write<01:14:36.719> test<01:14:36.840> for<01:14:37.080> it 01:14:37.130 --> 01:14:37.140 align:start position:0% new OP code right and write test for it 01:14:37.140 --> 01:14:38.689 align:start position:0% new OP code right and write test for it like<01:14:37.260> we<01:14:37.380> have<01:14:37.440> framework<01:14:37.800> for<01:14:37.980> that<01:14:38.159> and<01:14:38.580> now 01:14:38.689 --> 01:14:38.699 align:start position:0% like we have framework for that and now 01:14:38.699 --> 01:14:40.550 align:start position:0% like we have framework for that and now we<01:14:38.880> have<01:14:39.000> and<01:14:39.360> and<01:14:39.600> like<01:14:39.960> if<01:14:40.140> you<01:14:40.260> want<01:14:40.380> to<01:14:40.440> do 01:14:40.550 --> 01:14:40.560 align:start position:0% we have and and like if you want to do 01:14:40.560 --> 01:14:42.410 align:start position:0% we have and and like if you want to do something<01:14:40.860> like<01:14:41.159> blobs 01:14:42.410 --> 01:14:42.420 align:start position:0% something like blobs 01:14:42.420 --> 01:14:45.649 align:start position:0% something like blobs um<01:14:42.540> we<01:14:42.840> don't<01:14:43.199> have<01:14:43.380> like<01:14:43.820> blob<01:14:44.820> testing<01:14:45.300> right 01:14:45.649 --> 01:14:45.659 align:start position:0% um we don't have like blob testing right 01:14:45.659 --> 01:14:46.910 align:start position:0% um we don't have like blob testing right and<01:14:45.960> so<01:14:46.080> we're<01:14:46.199> gonna<01:14:46.320> need<01:14:46.500> to<01:14:46.620> build<01:14:46.739> all 01:14:46.910 --> 01:14:46.920 align:start position:0% and so we're gonna need to build all 01:14:46.920 --> 01:14:47.750 align:start position:0% and so we're gonna need to build all that 01:14:47.750 --> 01:14:47.760 align:start position:0% that 01:14:47.760 --> 01:14:49.370 align:start position:0% that um and<01:14:47.940> then<01:14:48.060> then<01:14:48.480> we'll<01:14:48.659> have<01:14:48.840> it<01:14:48.960> and<01:14:49.199> it'll 01:14:49.370 --> 01:14:49.380 align:start position:0% um and then then we'll have it and it'll 01:14:49.380 --> 01:14:51.229 align:start position:0% um and then then we'll have it and it'll be<01:14:49.560> easier<01:14:49.920> to<01:14:50.280> like<01:14:50.400> you<01:14:50.580> know<01:14:50.640> grow<01:14:50.880> the<01:14:51.120> size 01:14:51.229 --> 01:14:51.239 align:start position:0% be easier to like you know grow the size 01:14:51.239 --> 01:14:52.669 align:start position:0% be easier to like you know grow the size of<01:14:51.360> blobs<01:14:51.719> or<01:14:51.840> something<01:14:51.960> but<01:14:52.380> then<01:14:52.500> when 01:14:52.669 --> 01:14:52.679 align:start position:0% of blobs or something but then when 01:14:52.679 --> 01:14:54.110 align:start position:0% of blobs or something but then when we're<01:14:52.800> gonna<01:14:52.980> we<01:14:53.580> want<01:14:53.699> to<01:14:53.760> do<01:14:53.880> I<01:14:54.000> don't<01:14:54.060> know 01:14:54.110 --> 01:14:54.120 align:start position:0% we're gonna we want to do I don't know 01:14:54.120 --> 01:14:56.090 align:start position:0% we're gonna we want to do I don't know like<01:14:54.239> daily<01:14:54.420> availability<01:14:54.840> sampling<01:14:55.500> we<01:14:55.920> need 01:14:56.090 --> 01:14:56.100 align:start position:0% like daily availability sampling we need 01:14:56.100 --> 01:14:58.550 align:start position:0% like daily availability sampling we need like<01:14:56.460> you<01:14:56.820> need<01:14:57.000> like<01:14:57.300> always<01:14:57.840> to<01:14:58.140> build<01:14:58.320> the 01:14:58.550 --> 01:14:58.560 align:start position:0% like you need like always to build the 01:14:58.560 --> 01:15:00.350 align:start position:0% like you need like always to build the new<01:14:58.739> testing<01:14:59.100> stuff 01:15:00.350 --> 01:15:00.360 align:start position:0% new testing stuff 01:15:00.360 --> 01:15:01.669 align:start position:0% new testing stuff um and<01:15:00.719> it's<01:15:00.840> kind<01:15:01.020> of<01:15:01.080> hard<01:15:01.199> because<01:15:01.380> like 01:15:01.669 --> 01:15:01.679 align:start position:0% um and it's kind of hard because like 01:15:01.679 --> 01:15:03.530 align:start position:0% um and it's kind of hard because like you<01:15:01.800> can't<01:15:01.920> build<01:15:02.280> it<01:15:02.460> in<01:15:02.940> advance<01:15:03.120> because 01:15:03.530 --> 01:15:03.540 align:start position:0% you can't build it in advance because 01:15:03.540 --> 01:15:05.930 align:start position:0% you can't build it in advance because you<01:15:03.780> need<01:15:03.900> you<01:15:04.560> need<01:15:04.679> to<01:15:04.800> test<01:15:04.920> something 01:15:05.930 --> 01:15:05.940 align:start position:0% you need you need to test something 01:15:05.940 --> 01:15:07.310 align:start position:0% you need you need to test something um<01:15:06.000> so<01:15:06.179> there's<01:15:06.360> this<01:15:06.600> weird<01:15:06.780> like<01:15:07.140> chicken 01:15:07.310 --> 01:15:07.320 align:start position:0% um so there's this weird like chicken 01:15:07.320 --> 01:15:09.050 align:start position:0% um so there's this weird like chicken and<01:15:07.560> egg<01:15:07.679> but<01:15:07.800> do<01:15:07.980> you<01:15:08.100> think<01:15:08.159> like 01:15:09.050 --> 01:15:09.060 align:start position:0% and egg but do you think like 01:15:09.060 --> 01:15:10.250 align:start position:0% and egg but do you think like like<01:15:09.540> we<01:15:09.659> were<01:15:09.780> having<01:15:09.960> the<01:15:10.140> same 01:15:10.250 --> 01:15:10.260 align:start position:0% like we were having the same 01:15:10.260 --> 01:15:13.010 align:start position:0% like we were having the same conversation<01:15:10.679> in<01:15:10.980> 2018<01:15:11.100> in<01:15:11.699> Osaka<01:15:12.239> and<01:15:12.719> like 01:15:13.010 --> 01:15:13.020 align:start position:0% conversation in 2018 in Osaka and like 01:15:13.020 --> 01:15:15.590 align:start position:0% conversation in 2018 in Osaka and like our<01:15:13.199> capacity<01:15:13.620> was<01:15:13.920> like<01:15:14.159> 25<01:15:14.400> probably<01:15:15.300> of 01:15:15.590 --> 01:15:15.600 align:start position:0% our capacity was like 25 probably of 01:15:15.600 --> 01:15:19.010 align:start position:0% our capacity was like 25 probably of this<01:15:15.780> so<01:15:16.320> it's<01:15:16.440> like<01:15:17.179> I<01:15:18.179> feel<01:15:18.300> we've<01:15:18.719> we<01:15:18.840> have 01:15:19.010 --> 01:15:19.020 align:start position:0% this so it's like I feel we've we have 01:15:19.020 --> 01:15:20.750 align:start position:0% this so it's like I feel we've we have gotten<01:15:19.380> better<01:15:19.500> I<01:15:20.159> don't<01:15:20.280> know<01:15:20.400> that<01:15:20.580> it's 01:15:20.750 --> 01:15:20.760 align:start position:0% gotten better I don't know that it's 01:15:20.760 --> 01:15:22.669 align:start position:0% gotten better I don't know that it's ever<01:15:20.940> going<01:15:21.239> to<01:15:21.420> feel<01:15:21.719> better<01:15:21.960> doing<01:15:22.260> the<01:15:22.500> work 01:15:22.669 --> 01:15:22.679 align:start position:0% ever going to feel better doing the work 01:15:22.679 --> 01:15:24.169 align:start position:0% ever going to feel better doing the work which<01:15:23.040> is<01:15:23.159> maybe<01:15:23.280> my<01:15:23.520> thing<01:15:23.640> just<01:15:23.820> like<01:15:23.940> we 01:15:24.169 --> 01:15:24.179 align:start position:0% which is maybe my thing just like we 01:15:24.179 --> 01:15:27.050 align:start position:0% which is maybe my thing just like we just<01:15:24.300> do<01:15:24.540> more<01:15:24.719> or<01:15:25.440> better<01:15:25.800> at<01:15:26.219> it<01:15:26.460> but<01:15:26.880> it 01:15:27.050 --> 01:15:27.060 align:start position:0% just do more or better at it but it 01:15:27.060 --> 01:15:28.370 align:start position:0% just do more or better at it but it still<01:15:27.239> feels<01:15:27.480> like<01:15:27.540> we're<01:15:27.719> kind<01:15:27.960> of<01:15:28.020> pushing 01:15:28.370 --> 01:15:28.380 align:start position:0% still feels like we're kind of pushing 01:15:28.380 --> 01:15:30.770 align:start position:0% still feels like we're kind of pushing ourselves<01:15:28.739> because<01:15:29.640> like<01:15:30.060> it's<01:15:30.420> just<01:15:30.540> hard 01:15:30.770 --> 01:15:30.780 align:start position:0% ourselves because like it's just hard 01:15:30.780 --> 01:15:33.169 align:start position:0% ourselves because like it's just hard stuff<01:15:31.080> and<01:15:31.500> you<01:15:31.679> need<01:15:31.800> to<01:15:32.159> build<01:15:32.280> it 01:15:33.169 --> 01:15:33.179 align:start position:0% stuff and you need to build it 01:15:33.179 --> 01:15:34.550 align:start position:0% stuff and you need to build it um<01:15:33.239> and<01:15:33.540> yeah<01:15:33.659> like<01:15:33.840> I<01:15:34.020> mean<01:15:34.140> you<01:15:34.260> know<01:15:34.380> the 01:15:34.550 --> 01:15:34.560 align:start position:0% um and yeah like I mean you know the 01:15:34.560 --> 01:15:37.189 align:start position:0% um and yeah like I mean you know the touch<01:15:34.800> on<01:15:35.040> 444<01:15:35.400> obviously<01:15:36.120> client<01:15:36.480> teams<01:15:36.780> kind 01:15:37.189 --> 01:15:37.199 align:start position:0% touch on 444 obviously client teams kind 01:15:37.199 --> 01:15:38.870 align:start position:0% touch on 444 obviously client teams kind of<01:15:37.320> tired<01:15:37.679> you<01:15:38.159> know<01:15:38.219> want<01:15:38.400> to<01:15:38.580> take<01:15:38.640> a<01:15:38.760> break 01:15:38.870 --> 01:15:38.880 align:start position:0% of tired you know want to take a break 01:15:38.880 --> 01:15:40.490 align:start position:0% of tired you know want to take a break want<01:15:39.120> to<01:15:39.300> focus<01:15:39.360> on<01:15:39.480> withdrawals<01:15:40.020> but<01:15:40.260> like 01:15:40.490 --> 01:15:40.500 align:start position:0% want to focus on withdrawals but like 01:15:40.500 --> 01:15:42.709 align:start position:0% want to focus on withdrawals but like having<01:15:40.739> optimism<01:15:41.280> had<01:15:41.580> step<01:15:41.820> up<01:15:42.000> having<01:15:42.300> coin 01:15:42.709 --> 01:15:42.719 align:start position:0% having optimism had step up having coin 01:15:42.719 --> 01:15:44.570 align:start position:0% having optimism had step up having coin Rays<01:15:43.080> step<01:15:43.260> up<01:15:43.440> like<01:15:43.800> we<01:15:44.159> wouldn't<01:15:44.280> even<01:15:44.460> be 01:15:44.570 --> 01:15:44.580 align:start position:0% Rays step up like we wouldn't even be 01:15:44.580 --> 01:15:46.130 align:start position:0% Rays step up like we wouldn't even be talking<01:15:44.760> about<01:15:44.940> 444<01:15:45.480> if<01:15:45.659> this<01:15:45.840> hadn't 01:15:46.130 --> 01:15:46.140 align:start position:0% talking about 444 if this hadn't 01:15:46.140 --> 01:15:47.990 align:start position:0% talking about 444 if this hadn't happened<01:15:46.320> and<01:15:46.920> I'm<01:15:47.100> not<01:15:47.280> convinced<01:15:47.640> that<01:15:47.760> like 01:15:47.990 --> 01:15:48.000 align:start position:0% happened and I'm not convinced that like 01:15:48.000 --> 01:15:49.669 align:start position:0% happened and I'm not convinced that like four<01:15:48.659> years<01:15:48.900> ago<01:15:49.199> it<01:15:49.380> would<01:15:49.500> have<01:15:49.620> been 01:15:49.669 --> 01:15:49.679 align:start position:0% four years ago it would have been 01:15:49.679 --> 01:15:51.169 align:start position:0% four years ago it would have been possible<01:15:49.980> for<01:15:50.280> like 01:15:51.169 --> 01:15:51.179 align:start position:0% possible for like 01:15:51.179 --> 01:15:53.330 align:start position:0% possible for like there<01:15:51.719> were<01:15:51.840> no<01:15:51.960> L2<01:15:52.320> teams<01:15:52.620> but<01:15:52.800> like<01:15:52.980> you<01:15:53.219> know 01:15:53.330 --> 01:15:53.340 align:start position:0% there were no L2 teams but like you know 01:15:53.340 --> 01:15:55.850 align:start position:0% there were no L2 teams but like you know for<01:15:53.640> like<01:15:53.880> the<01:15:54.000> Plasma<01:15:54.300> Team<01:15:54.540> to<01:15:55.020> like<01:15:55.260> ship 01:15:55.850 --> 01:15:55.860 align:start position:0% for like the Plasma Team to like ship 01:15:55.860 --> 01:15:57.709 align:start position:0% for like the Plasma Team to like ship something<01:15:56.100> like<01:15:56.580> that<01:15:56.820> so 01:15:57.709 --> 01:15:57.719 align:start position:0% something like that so 01:15:57.719 --> 01:15:59.270 align:start position:0% something like that so yeah<01:15:57.960> I<01:15:58.260> think<01:15:58.380> we're<01:15:58.500> making<01:15:58.679> progress<01:15:59.040> I 01:15:59.270 --> 01:15:59.280 align:start position:0% yeah I think we're making progress I 01:15:59.280 --> 01:16:00.110 align:start position:0% yeah I think we're making progress I don't<01:15:59.340> know<01:15:59.460> that's<01:15:59.580> ever<01:15:59.760> going<01:15:59.940> to<01:16:00.000> feel 01:16:00.110 --> 01:16:00.120 align:start position:0% don't know that's ever going to feel 01:16:00.120 --> 01:16:08.030 align:start position:0% don't know that's ever going to feel better<01:16:00.300> is<01:16:00.780> by<01:16:00.960> rough<01:16:01.199> feeling 01:16:08.030 --> 01:16:08.040 align:start position:0% 01:16:08.040 --> 01:16:10.189 align:start position:0% so<01:16:08.880> I<01:16:09.120> drained<01:16:09.360> from<01:16:09.480> taking<01:16:09.659> I<01:16:09.960> just<01:16:10.080> moved 01:16:10.189 --> 01:16:10.199 align:start position:0% so I drained from taking I just moved 01:16:10.199 --> 01:16:11.209 align:start position:0% so I drained from taking I just moved from<01:16:10.260> over<01:16:10.440> there 01:16:11.209 --> 01:16:11.219 align:start position:0% from over there 01:16:11.219 --> 01:16:13.370 align:start position:0% from over there um<01:16:11.340> so<01:16:12.000> the<01:16:12.420> context 01:16:13.370 --> 01:16:13.380 align:start position:0% um so the context 01:16:13.380 --> 01:16:14.630 align:start position:0% um so the context um<01:16:13.440> so<01:16:13.620> I<01:16:13.739> think<01:16:13.860> the<01:16:13.980> other<01:16:14.100> Factor<01:16:14.460> that's 01:16:14.630 --> 01:16:14.640 align:start position:0% um so I think the other Factor that's 01:16:14.640 --> 01:16:15.950 align:start position:0% um so I think the other Factor that's slightly<01:16:15.120> interesting<01:16:15.480> is<01:16:15.600> there's<01:16:15.780> this 01:16:15.950 --> 01:16:15.960 align:start position:0% slightly interesting is there's this 01:16:15.960 --> 01:16:19.070 align:start position:0% slightly interesting is there's this real<01:16:16.140> cycle<01:16:16.440> to<01:16:17.040> Doing<01:16:17.460> Hard<01:16:17.760> Forks<01:16:18.300> in<01:16:18.840> that 01:16:19.070 --> 01:16:19.080 align:start position:0% real cycle to Doing Hard Forks in that 01:16:19.080 --> 01:16:22.669 align:start position:0% real cycle to Doing Hard Forks in that client<01:16:19.620> teams<01:16:19.920> in<01:16:20.040> particular<01:16:20.400> get<01:16:20.760> swamped 01:16:22.669 --> 01:16:22.679 align:start position:0% client teams in particular get swamped 01:16:22.679 --> 01:16:24.110 align:start position:0% client teams in particular get swamped it's<01:16:23.040> not<01:16:23.219> really<01:16:23.340> early<01:16:23.520> on<01:16:23.699> the<01:16:23.880> research 01:16:24.110 --> 01:16:24.120 align:start position:0% it's not really early on the research 01:16:24.120 --> 01:16:25.430 align:start position:0% it's not really early on the research team<01:16:24.300> probably<01:16:24.480> gets<01:16:24.780> one<01:16:24.840> first<01:16:25.080> then<01:16:25.320> the 01:16:25.430 --> 01:16:25.440 align:start position:0% team probably gets one first then the 01:16:25.440 --> 01:16:26.990 align:start position:0% team probably gets one first then the client<01:16:25.560> teams<01:16:25.860> get<01:16:25.980> swamped<01:16:26.340> and<01:16:26.699> then<01:16:26.820> our 01:16:26.990 --> 01:16:27.000 align:start position:0% client teams get swamped and then our 01:16:27.000 --> 01:16:28.790 align:start position:0% client teams get swamped and then our work<01:16:27.179> is<01:16:27.360> done<01:16:27.600> and<01:16:28.199> we're<01:16:28.260> kind<01:16:28.440> of<01:16:28.560> waiting 01:16:28.790 --> 01:16:28.800 align:start position:0% work is done and we're kind of waiting 01:16:28.800 --> 01:16:30.470 align:start position:0% work is done and we're kind of waiting on<01:16:28.860> coordination<01:16:29.280> and<01:16:29.699> there's<01:16:29.820> this<01:16:30.060> lull 01:16:30.470 --> 01:16:30.480 align:start position:0% on coordination and there's this lull 01:16:30.480 --> 01:16:32.870 align:start position:0% on coordination and there's this lull and<01:16:31.020> that<01:16:31.080> lull<01:16:31.440> is<01:16:31.739> where<01:16:31.920> we<01:16:32.040> get<01:16:32.159> all<01:16:32.580> of<01:16:32.699> our 01:16:32.870 --> 01:16:32.880 align:start position:0% and that lull is where we get all of our 01:16:32.880 --> 01:16:34.850 align:start position:0% and that lull is where we get all of our client<01:16:33.300> optimizations<01:16:33.960> and<01:16:34.380> all<01:16:34.560> the<01:16:34.739> other 01:16:34.850 --> 01:16:34.860 align:start position:0% client optimizations and all the other 01:16:34.860 --> 01:16:36.709 align:start position:0% client optimizations and all the other stuff<01:16:35.040> kind<01:16:35.280> of<01:16:35.400> done 01:16:36.709 --> 01:16:36.719 align:start position:0% stuff kind of done 01:16:36.719 --> 01:16:39.110 align:start position:0% stuff kind of done um<01:16:36.920> and<01:16:37.920> uh 01:16:39.110 --> 01:16:39.120 align:start position:0% um and uh 01:16:39.120 --> 01:16:41.570 align:start position:0% um and uh yeah so<01:16:39.659> that's<01:16:39.840> real<01:16:40.080> opportunity<01:16:40.860> and<01:16:41.280> and 01:16:41.570 --> 01:16:41.580 align:start position:0% yeah so that's real opportunity and and 01:16:41.580 --> 01:16:42.950 align:start position:0% yeah so that's real opportunity and and a<01:16:41.760> lot<01:16:41.880> of<01:16:42.000> the<01:16:42.120> community<01:16:42.360> coordination 01:16:42.950 --> 01:16:42.960 align:start position:0% a lot of the community coordination 01:16:42.960 --> 01:16:45.050 align:start position:0% a lot of the community coordination happens<01:16:43.260> there<01:16:43.620> there's<01:16:44.100> there's<01:16:44.400> a<01:16:44.699> lot<01:16:44.880> of 01:16:45.050 --> 01:16:45.060 align:start position:0% happens there there's there's a lot of 01:16:45.060 --> 01:16:47.689 align:start position:0% happens there there's there's a lot of time<01:16:45.480> it<01:16:45.960> takes<01:16:46.140> to<01:16:46.380> go<01:16:46.560> from<01:16:46.860> the<01:16:47.280> code<01:16:47.400> is 01:16:47.689 --> 01:16:47.699 align:start position:0% time it takes to go from the code is 01:16:47.699 --> 01:16:51.229 align:start position:0% time it takes to go from the code is ready<01:16:47.940> and<01:16:48.239> done<01:16:48.480> to<01:16:49.260> the<01:16:49.620> code<01:16:49.800> is<01:16:50.100> tested<01:16:51.000> in 01:16:51.229 --> 01:16:51.239 align:start position:0% ready and done to the code is tested in 01:16:51.239 --> 01:16:53.510 align:start position:0% ready and done to the code is tested in every<01:16:51.480> possible<01:16:51.840> situation<01:16:52.380> and<01:16:53.040> we've 01:16:53.510 --> 01:16:53.520 align:start position:0% every possible situation and we've 01:16:53.520 --> 01:16:54.950 align:start position:0% every possible situation and we've automated<01:16:53.820> all<01:16:54.060> of<01:16:54.179> that<01:16:54.300> in<01:16:54.480> terms<01:16:54.659> of<01:16:54.719> the 01:16:54.950 --> 01:16:54.960 align:start position:0% automated all of that in terms of the 01:16:54.960 --> 01:16:57.169 align:start position:0% automated all of that in terms of the cross-client<01:16:55.620> stuff<01:16:55.920> and<01:16:56.159> and<01:16:56.340> the 01:16:57.169 --> 01:16:57.179 align:start position:0% cross-client stuff and and the 01:16:57.179 --> 01:16:59.450 align:start position:0% cross-client stuff and and the the<01:16:57.780> level<01:16:57.960> of<01:16:58.199> detail<01:16:58.500> we<01:16:58.679> want<01:16:58.800> for<01:16:58.980> ethereum 01:16:59.450 --> 01:16:59.460 align:start position:0% the level of detail we want for ethereum 01:16:59.460 --> 01:17:02.870 align:start position:0% the level of detail we want for ethereum and<01:17:00.239> then<01:17:00.420> the<01:17:01.080> code<01:17:01.199> is<01:17:01.440> actually<01:17:01.679> ready<01:17:02.460> from 01:17:02.870 --> 01:17:02.880 align:start position:0% and then the code is actually ready from 01:17:02.880 --> 01:17:04.250 align:start position:0% and then the code is actually ready from the<01:17:03.179> community's<01:17:03.540> perspective<01:17:03.840> and<01:17:04.020> all<01:17:04.140> the 01:17:04.250 --> 01:17:04.260 align:start position:0% the community's perspective and all the 01:17:04.260 --> 01:17:05.570 align:start position:0% the community's perspective and all the tools<01:17:04.440> of<01:17:04.560> updated<01:17:04.800> and<01:17:04.980> so<01:17:05.100> on<01:17:05.159> and<01:17:05.340> all<01:17:05.460> of 01:17:05.570 --> 01:17:05.580 align:start position:0% tools of updated and so on and all of 01:17:05.580 --> 01:17:06.530 align:start position:0% tools of updated and so on and all of those<01:17:05.699> kind<01:17:05.820> of<01:17:05.940> happen<01:17:06.000> to<01:17:06.179> happen<01:17:06.300> in 01:17:06.530 --> 01:17:06.540 align:start position:0% those kind of happen to happen in 01:17:06.540 --> 01:17:09.890 align:start position:0% those kind of happen to happen in sequence<01:17:06.900> so<01:17:07.620> as<01:17:08.400> long<01:17:08.520> as<01:17:08.640> we<01:17:08.880> don't<01:17:09.120> shoot 01:17:09.890 --> 01:17:09.900 align:start position:0% sequence so as long as we don't shoot 01:17:09.900 --> 01:17:14.209 align:start position:0% sequence so as long as we don't shoot for<01:17:10.320> a<01:17:10.860> massive<01:17:11.219> hard<01:17:11.580> Fork<01:17:12.060> we<01:17:12.840> can<01:17:13.020> get<01:17:13.320> a<01:17:13.800> you 01:17:14.209 --> 01:17:14.219 align:start position:0% for a massive hard Fork we can get a you 01:17:14.219 --> 01:17:15.470 align:start position:0% for a massive hard Fork we can get a you know<01:17:14.340> a<01:17:14.460> little<01:17:14.520> hump<01:17:14.699> of<01:17:14.940> we<01:17:15.120> can<01:17:15.239> get<01:17:15.360> you 01:17:15.470 --> 01:17:15.480 align:start position:0% know a little hump of we can get you 01:17:15.480 --> 01:17:16.490 align:start position:0% know a little hump of we can get you know<01:17:15.600> say<01:17:15.719> withdrawals<01:17:16.199> done<01:17:16.320> because 01:17:16.490 --> 01:17:16.500 align:start position:0% know say withdrawals done because 01:17:16.500 --> 01:17:18.410 align:start position:0% know say withdrawals done because they're<01:17:16.679> relatively<01:17:17.159> simple 01:17:18.410 --> 01:17:18.420 align:start position:0% they're relatively simple 01:17:18.420 --> 01:17:20.930 align:start position:0% they're relatively simple pick<01:17:18.719> up<01:17:18.900> a<01:17:19.080> lull<01:17:19.260> and<01:17:19.739> then<01:17:19.800> be<01:17:19.980> ready<01:17:20.159> to<01:17:20.460> to 01:17:20.930 --> 01:17:20.940 align:start position:0% pick up a lull and then be ready to to 01:17:20.940 --> 01:17:22.910 align:start position:0% pick up a lull and then be ready to to pick<01:17:21.179> up<01:17:21.360> something<01:17:21.540> big<01:17:21.840> again 01:17:22.910 --> 01:17:22.920 align:start position:0% pick up something big again 01:17:22.920 --> 01:17:26.030 align:start position:0% pick up something big again um<01:17:22.980> so<01:17:23.520> it's<01:17:23.640> not<01:17:23.940> a<01:17:24.179> case<01:17:24.360> of<01:17:24.659> stop<01:17:25.500> the<01:17:25.800> world 01:17:26.030 --> 01:17:26.040 align:start position:0% um so it's not a case of stop the world 01:17:26.040 --> 01:17:29.870 align:start position:0% um so it's not a case of stop the world it's<01:17:26.880> just<01:17:27.179> managing<01:17:28.020> those<01:17:28.260> cycles<01:17:28.880> and 01:17:29.870 --> 01:17:29.880 align:start position:0% it's just managing those cycles and 01:17:29.880 --> 01:17:32.209 align:start position:0% it's just managing those cycles and probably<01:17:30.000> the<01:17:30.179> other<01:17:30.300> factor<01:17:30.719> is<01:17:30.900> that<01:17:31.260> teams 01:17:32.209 --> 01:17:32.219 align:start position:0% probably the other factor is that teams 01:17:32.219 --> 01:17:34.250 align:start position:0% probably the other factor is that teams go<01:17:32.460> through<01:17:32.699> that<01:17:33.360> kind<01:17:33.480> of<01:17:33.600> cycle<01:17:33.840> as<01:17:34.080> well 01:17:34.250 --> 01:17:34.260 align:start position:0% go through that kind of cycle as well 01:17:34.260 --> 01:17:36.350 align:start position:0% go through that kind of cycle as well that<01:17:35.040> you'll<01:17:35.340> have<01:17:35.520> a<01:17:35.699> great<01:17:35.820> team<01:17:36.000> and<01:17:36.239> you're 01:17:36.350 --> 01:17:36.360 align:start position:0% that you'll have a great team and you're 01:17:36.360 --> 01:17:37.490 align:start position:0% that you'll have a great team and you're going<01:17:36.480> well<01:17:36.659> and<01:17:36.840> then<01:17:36.960> someone<01:17:37.080> will<01:17:37.260> get<01:17:37.380> a 01:17:37.490 --> 01:17:37.500 align:start position:0% going well and then someone will get a 01:17:37.500 --> 01:17:39.050 align:start position:0% going well and then someone will get a better<01:17:37.560> job<01:17:37.739> offer<01:17:38.100> somewhere<01:17:38.460> and<01:17:38.880> you're 01:17:39.050 --> 01:17:39.060 align:start position:0% better job offer somewhere and you're 01:17:39.060 --> 01:17:40.669 align:start position:0% better job offer somewhere and you're kind<01:17:39.300> of<01:17:39.420> suddenly<01:17:39.960> you've<01:17:40.140> got<01:17:40.260> fewer<01:17:40.560> people 01:17:40.669 --> 01:17:40.679 align:start position:0% kind of suddenly you've got fewer people 01:17:40.679 --> 01:17:42.229 align:start position:0% kind of suddenly you've got fewer people on<01:17:40.920> your<01:17:41.040> team<01:17:41.219> and<01:17:41.520> you're<01:17:41.640> rebuilding<01:17:42.120> with 01:17:42.229 --> 01:17:42.239 align:start position:0% on your team and you're rebuilding with 01:17:42.239 --> 01:17:43.850 align:start position:0% on your team and you're rebuilding with some<01:17:42.360> new<01:17:42.540> people<01:17:42.719> again<01:17:42.960> and<01:17:43.320> yeah<01:17:43.560> all<01:17:43.739> the 01:17:43.850 --> 01:17:43.860 align:start position:0% some new people again and yeah all the 01:17:43.860 --> 01:17:45.470 align:start position:0% some new people again and yeah all the client<01:17:43.980> teams<01:17:44.280> are<01:17:44.340> nodding<01:17:44.699> we've<01:17:45.120> all<01:17:45.300> done 01:17:45.470 --> 01:17:45.480 align:start position:0% client teams are nodding we've all done 01:17:45.480 --> 01:17:47.149 align:start position:0% client teams are nodding we've all done it<01:17:45.600> it<01:17:45.780> happens<01:17:45.960> on<01:17:46.199> every<01:17:46.380> team<01:17:46.560> from<01:17:46.860> time<01:17:46.980> to 01:17:47.149 --> 01:17:47.159 align:start position:0% it it happens on every team from time to 01:17:47.159 --> 01:17:48.709 align:start position:0% it it happens on every team from time to time<01:17:47.340> it<01:17:47.880> just<01:17:47.940> depends<01:17:48.179> where<01:17:48.360> you<01:17:48.480> are<01:17:48.600> in 01:17:48.709 --> 01:17:48.719 align:start position:0% time it just depends where you are in 01:17:48.719 --> 01:17:51.110 align:start position:0% time it just depends where you are in that<01:17:48.840> cycle<01:17:49.020> as<01:17:49.320> to<01:17:49.500> how<01:17:50.460> freaking<01:17:50.699> out<01:17:50.880> you 01:17:51.110 --> 01:17:51.120 align:start position:0% that cycle as to how freaking out you 01:17:51.120 --> 01:17:58.250 align:start position:0% that cycle as to how freaking out you are<01:17:51.239> about<01:17:51.420> the<01:17:51.659> next<01:17:51.780> hard<01:17:51.960> book<01:17:52.199> as<01:17:52.440> well 01:17:58.250 --> 01:17:58.260 align:start position:0% 01:17:58.260 --> 01:18:01.310 align:start position:0% I<01:17:58.860> don't<01:17:58.980> know 01:18:01.310 --> 01:18:01.320 align:start position:0% 01:18:01.320 --> 01:18:03.470 align:start position:0% um<01:18:01.500> I<01:18:02.040> was<01:18:02.159> expecting<01:18:02.580> to<01:18:02.880> come<01:18:03.060> and<01:18:03.179> try<01:18:03.360> and 01:18:03.470 --> 01:18:03.480 align:start position:0% um I was expecting to come and try and 01:18:03.480 --> 01:18:05.689 align:start position:0% um I was expecting to come and try and like<01:18:03.600> make<01:18:03.780> a<01:18:03.900> pitch<01:18:04.260> for<01:18:04.500> why<01:18:04.739> it's<01:18:05.219> crazy<01:18:05.400> to 01:18:05.689 --> 01:18:05.699 align:start position:0% like make a pitch for why it's crazy to 01:18:05.699 --> 01:18:07.610 align:start position:0% like make a pitch for why it's crazy to do<01:18:05.880> more<01:18:06.060> than<01:18:06.179> just<01:18:06.300> withdrawals<01:18:07.020> is<01:18:07.140> a<01:18:07.500> big 01:18:07.610 --> 01:18:07.620 align:start position:0% do more than just withdrawals is a big 01:18:07.620 --> 01:18:09.229 align:start position:0% do more than just withdrawals is a big thing<01:18:07.739> in<01:18:07.980> in<01:18:08.159> the<01:18:08.400> first<01:18:08.520> half<01:18:08.699> Fork<01:18:09.120> after 01:18:09.229 --> 01:18:09.239 align:start position:0% thing in in the first half Fork after 01:18:09.239 --> 01:18:10.850 align:start position:0% thing in in the first half Fork after the<01:18:09.420> merge<01:18:09.719> but<01:18:10.080> actually<01:18:10.199> I've<01:18:10.380> not<01:18:10.560> had<01:18:10.679> a 01:18:10.850 --> 01:18:10.860 align:start position:0% the merge but actually I've not had a 01:18:10.860 --> 01:18:13.070 align:start position:0% the merge but actually I've not had a single<01:18:11.159> core<01:18:11.699> Dev<01:18:11.820> advocate<01:18:12.300> for<01:18:12.480> that<01:18:12.600> so<01:18:12.900> far 01:18:13.070 --> 01:18:13.080 align:start position:0% single core Dev advocate for that so far 01:18:13.080 --> 01:18:15.610 align:start position:0% single core Dev advocate for that so far so<01:18:13.260> oh<01:18:13.920> but<01:18:14.159> maybe<01:18:14.280> Danka 01:18:15.610 --> 01:18:15.620 align:start position:0% so oh but maybe Danka 01:18:15.620 --> 01:18:18.050 align:start position:0% so oh but maybe Danka oh<01:18:16.620> no<01:18:16.739> I<01:18:16.920> moved<01:18:17.219> within<01:18:17.400> arm<01:18:17.580> reach<01:18:17.880> of<01:18:18.000> the 01:18:18.050 --> 01:18:18.060 align:start position:0% oh no I moved within arm reach of the 01:18:18.060 --> 01:18:20.149 align:start position:0% oh no I moved within arm reach of the office<01:18:18.179> that's<01:18:19.020> the<01:18:19.140> question<01:18:19.320> anyway 01:18:20.149 --> 01:18:20.159 align:start position:0% office that's the question anyway 01:18:20.159 --> 01:18:22.189 align:start position:0% office that's the question anyway um<01:18:20.280> but<01:18:20.520> I<01:18:20.640> did<01:18:20.760> I<01:18:20.940> did<01:18:21.060> want<01:18:21.239> to<01:18:21.360> ask<01:18:21.480> two<01:18:22.140> um 01:18:22.189 --> 01:18:22.199 align:start position:0% um but I did I did want to ask two um 01:18:22.199 --> 01:18:24.229 align:start position:0% um but I did I did want to ask two um points<01:18:22.500> about<01:18:22.560> withdrawals<01:18:23.640> um<01:18:23.760> like<01:18:23.940> mostly 01:18:24.229 --> 01:18:24.239 align:start position:0% points about withdrawals um like mostly 01:18:24.239 --> 01:18:25.970 align:start position:0% points about withdrawals um like mostly to<01:18:24.360> consensus<01:18:24.840> clients<01:18:25.440> um<01:18:25.440> so<01:18:25.620> the<01:18:25.860> first 01:18:25.970 --> 01:18:25.980 align:start position:0% to consensus clients um so the first 01:18:25.980 --> 01:18:27.229 align:start position:0% to consensus clients um so the first point<01:18:26.159> is 01:18:27.229 --> 01:18:27.239 align:start position:0% point is 01:18:27.239 --> 01:18:28.550 align:start position:0% point is um<01:18:27.300> a<01:18:27.480> few<01:18:27.540> people<01:18:27.659> have<01:18:27.900> said<01:18:28.020> things<01:18:28.199> like<01:18:28.380> oh 01:18:28.550 --> 01:18:28.560 align:start position:0% um a few people have said things like oh 01:18:28.560 --> 01:18:30.950 align:start position:0% um a few people have said things like oh it's<01:18:28.800> a<01:18:28.920> relatively<01:18:29.219> small<01:18:29.400> change<01:18:29.699> and<01:18:30.420> so<01:18:30.780> my 01:18:30.950 --> 01:18:30.960 align:start position:0% it's a relatively small change and so my 01:18:30.960 --> 01:18:34.189 align:start position:0% it's a relatively small change and so my I<01:18:31.500> wanted<01:18:31.620> to<01:18:31.860> just<01:18:32.040> check<01:18:32.400> like<01:18:32.699> is<01:18:32.940> it<01:18:33.120> so<01:18:34.140> um 01:18:34.189 --> 01:18:34.199 align:start position:0% I wanted to just check like is it so um 01:18:34.199 --> 01:18:36.950 align:start position:0% I wanted to just check like is it so um uh<01:18:34.980> so<01:18:35.640> one<01:18:36.120> of<01:18:36.239> the<01:18:36.300> other<01:18:36.420> sessions<01:18:36.659> recently 01:18:36.950 --> 01:18:36.960 align:start position:0% uh so one of the other sessions recently 01:18:36.960 --> 01:18:39.050 align:start position:0% uh so one of the other sessions recently one<01:18:37.199> of<01:18:37.320> the<01:18:37.320> points<01:18:37.560> that<01:18:37.620> was<01:18:37.800> made<01:18:37.980> uh<01:18:38.820> was 01:18:39.050 --> 01:18:39.060 align:start position:0% one of the points that was made uh was 01:18:39.060 --> 01:18:40.070 align:start position:0% one of the points that was made uh was that 01:18:40.070 --> 01:18:40.080 align:start position:0% that 01:18:40.080 --> 01:18:42.350 align:start position:0% that um<01:18:40.199> you<01:18:40.500> know<01:18:40.560> at<01:18:40.739> the<01:18:40.860> at<01:18:41.040> the<01:18:41.219> time<01:18:41.340> that<01:18:41.580> the 01:18:42.350 --> 01:18:42.360 align:start position:0% um you know at the at the time that the 01:18:42.360 --> 01:18:44.630 align:start position:0% um you know at the at the time that the um<01:18:42.480> withdrawals<01:18:43.260> become<01:18:43.440> enabled<01:18:43.739> also<01:18:44.580> um 01:18:44.630 --> 01:18:44.640 align:start position:0% um withdrawals become enabled also um 01:18:44.640 --> 01:18:46.430 align:start position:0% um withdrawals become enabled also um withdraw<01:18:45.120> key<01:18:45.360> rotation<01:18:45.780> becomes<01:18:46.260> available 01:18:46.430 --> 01:18:46.440 align:start position:0% withdraw key rotation becomes available 01:18:46.440 --> 01:18:48.470 align:start position:0% withdraw key rotation becomes available so<01:18:46.980> there's<01:18:47.340> going<01:18:47.520> to<01:18:47.580> be<01:18:47.699> an<01:18:47.820> enormous<01:18:48.120> queue 01:18:48.470 --> 01:18:48.480 align:start position:0% so there's going to be an enormous queue 01:18:48.480 --> 01:18:50.030 align:start position:0% so there's going to be an enormous queue of<01:18:48.600> people<01:18:48.719> wanting<01:18:49.080> to<01:18:49.199> do<01:18:49.380> key<01:18:49.560> rotation 01:18:50.030 --> 01:18:50.040 align:start position:0% of people wanting to do key rotation 01:18:50.040 --> 01:18:51.830 align:start position:0% of people wanting to do key rotation there's<01:18:50.520> gonna<01:18:50.699> be<01:18:50.880> massive<01:18:51.120> Mev<01:18:51.480> from<01:18:51.719> those 01:18:51.830 --> 01:18:51.840 align:start position:0% there's gonna be massive Mev from those 01:18:51.840 --> 01:18:55.430 align:start position:0% there's gonna be massive Mev from those validators<01:18:52.800> who<01:18:53.159> are<01:18:53.340> trying<01:18:53.520> to<01:18:53.699> exit<01:18:54.000> before 01:18:55.430 --> 01:18:55.440 align:start position:0% validators who are trying to exit before 01:18:55.440 --> 01:18:56.870 align:start position:0% validators who are trying to exit before um<01:18:55.500> they<01:18:55.800> get<01:18:56.040> hacked<01:18:56.340> because<01:18:56.460> their<01:18:56.640> key's 01:18:56.870 --> 01:18:56.880 align:start position:0% um they get hacked because their key's 01:18:56.880 --> 01:18:58.070 align:start position:0% um they get hacked because their key's been<01:18:57.000> compromised<01:18:57.360> over<01:18:57.480> the<01:18:57.659> last<01:18:57.780> two<01:18:57.960> years 01:18:58.070 --> 01:18:58.080 align:start position:0% been compromised over the last two years 01:18:58.080 --> 01:19:00.169 align:start position:0% been compromised over the last two years all<01:18:58.679> kinds<01:18:58.920> of<01:18:58.980> other<01:18:59.100> sort<01:18:59.340> of<01:18:59.400> maybe<01:18:59.760> things 01:19:00.169 --> 01:19:00.179 align:start position:0% all kinds of other sort of maybe things 01:19:00.179 --> 01:19:02.930 align:start position:0% all kinds of other sort of maybe things you<01:19:00.360> haven't<01:19:00.540> about<01:19:00.960> very<01:19:01.260> much<01:19:01.440> so<01:19:02.100> do<01:19:02.699> those 01:19:02.930 --> 01:19:02.940 align:start position:0% you haven't about very much so do those 01:19:02.940 --> 01:19:05.630 align:start position:0% you haven't about very much so do those worry<01:19:03.120> people<01:19:03.360> at<01:19:03.540> all<01:19:03.659> or<01:19:03.960> not<01:19:04.260> at<01:19:04.440> all<01:19:04.920> um<01:19:05.280> and 01:19:05.630 --> 01:19:05.640 align:start position:0% worry people at all or not at all um and 01:19:05.640 --> 01:19:06.649 align:start position:0% worry people at all or not at all um and the<01:19:05.760> second<01:19:05.940> point<01:19:06.060> I<01:19:06.179> wanted<01:19:06.300> to<01:19:06.420> raise<01:19:06.540> about 01:19:06.649 --> 01:19:06.659 align:start position:0% the second point I wanted to raise about 01:19:06.659 --> 01:19:09.649 align:start position:0% the second point I wanted to raise about withdrawals<01:19:07.260> was<01:19:07.620> around<01:19:07.860> whether<01:19:08.820> uh<01:19:09.540> it 01:19:09.649 --> 01:19:09.659 align:start position:0% withdrawals was around whether uh it 01:19:09.659 --> 01:19:10.910 align:start position:0% withdrawals was around whether uh it kind<01:19:09.780> of<01:19:09.900> links<01:19:10.080> the<01:19:10.199> text<01:19:10.320> out<01:19:10.560> point<01:19:10.739> that 01:19:10.910 --> 01:19:10.920 align:start position:0% kind of links the text out point that 01:19:10.920 --> 01:19:12.590 align:start position:0% kind of links the text out point that two<01:19:11.040> people<01:19:11.159> have<01:19:11.340> mentioned<01:19:11.580> is<01:19:11.760> uh<01:19:12.239> is<01:19:12.480> there 01:19:12.590 --> 01:19:12.600 align:start position:0% two people have mentioned is uh is there 01:19:12.600 --> 01:19:14.330 align:start position:0% two people have mentioned is uh is there is<01:19:12.780> there<01:19:13.080> a<01:19:13.199> kind<01:19:13.560> of<01:19:13.679> significant<01:19:14.340> um 01:19:14.330 --> 01:19:14.340 align:start position:0% is there a kind of significant um 01:19:14.340 --> 01:19:16.070 align:start position:0% is there a kind of significant um quantity<01:19:14.640> of<01:19:14.820> tech<01:19:14.940> get<01:19:15.120> around<01:19:15.360> the<01:19:15.600> deposit 01:19:16.070 --> 01:19:16.080 align:start position:0% quantity of tech get around the deposit 01:19:16.080 --> 01:19:19.850 align:start position:0% quantity of tech get around the deposit process<01:19:16.560> so<01:19:17.460> so<01:19:18.060> as<01:19:18.659> as<01:19:18.900> withdrawals<01:19:19.739> The 01:19:19.850 --> 01:19:19.860 align:start position:0% process so so as as withdrawals The 01:19:19.860 --> 01:19:21.830 align:start position:0% process so so as as withdrawals The Proposal<01:19:20.340> exists<01:19:20.760> is<01:19:21.000> to<01:19:21.179> create<01:19:21.360> a<01:19:21.719> new 01:19:21.830 --> 01:19:21.840 align:start position:0% Proposal exists is to create a new 01:19:21.840 --> 01:19:24.110 align:start position:0% Proposal exists is to create a new operation<01:19:22.620> for<01:19:22.920> withdrawals<01:19:23.460> it's<01:19:23.640> not<01:19:23.940> a 01:19:24.110 --> 01:19:24.120 align:start position:0% operation for withdrawals it's not a 01:19:24.120 --> 01:19:25.550 align:start position:0% operation for withdrawals it's not a transaction<01:19:24.360> it's<01:19:24.600> a<01:19:24.960> completely<01:19:25.199> separate 01:19:25.550 --> 01:19:25.560 align:start position:0% transaction it's a completely separate 01:19:25.560 --> 01:19:27.410 align:start position:0% transaction it's a completely separate type<01:19:25.739> of<01:19:25.920> thing 01:19:27.410 --> 01:19:27.420 align:start position:0% type of thing 01:19:27.420 --> 01:19:28.850 align:start position:0% type of thing um<01:19:27.480> it<01:19:27.840> seems<01:19:28.020> quite<01:19:28.140> natural<01:19:28.320> you<01:19:28.620> might<01:19:28.739> want 01:19:28.850 --> 01:19:28.860 align:start position:0% um it seems quite natural you might want 01:19:28.860 --> 01:19:30.290 align:start position:0% um it seems quite natural you might want to<01:19:28.980> just<01:19:29.100> have<01:19:29.159> a<01:19:29.340> corresponding<01:19:29.760> deposit 01:19:30.290 --> 01:19:30.300 align:start position:0% to just have a corresponding deposit 01:19:30.300 --> 01:19:32.090 align:start position:0% to just have a corresponding deposit operation<01:19:30.659> clean<01:19:31.199> up<01:19:31.320> the<01:19:31.440> deposit<01:19:31.800> contract 01:19:32.090 --> 01:19:32.100 align:start position:0% operation clean up the deposit contract 01:19:32.100 --> 01:19:34.490 align:start position:0% operation clean up the deposit contract deal<01:19:32.400> with<01:19:32.520> the<01:19:32.640> issues<01:19:32.880> like<01:19:33.120> kind<01:19:33.659> of<01:19:33.780> you 01:19:34.490 --> 01:19:34.500 align:start position:0% deal with the issues like kind of you 01:19:34.500 --> 01:19:35.930 align:start position:0% deal with the issues like kind of you know<01:19:34.620> double<01:19:34.920> counting<01:19:35.340> issue<01:19:35.580> it's<01:19:35.699> all<01:19:35.820> this 01:19:35.930 --> 01:19:35.940 align:start position:0% know double counting issue it's all this 01:19:35.940 --> 01:19:37.550 align:start position:0% know double counting issue it's all this kind<01:19:36.120> of<01:19:36.239> stuff<01:19:36.360> that<01:19:37.199> would<01:19:37.320> make<01:19:37.440> the 01:19:37.550 --> 01:19:37.560 align:start position:0% kind of stuff that would make the 01:19:37.560 --> 01:19:38.870 align:start position:0% kind of stuff that would make the protocol<01:19:37.800> more<01:19:38.100> understandable<01:19:38.520> for<01:19:38.699> future 01:19:38.870 --> 01:19:38.880 align:start position:0% protocol more understandable for future 01:19:38.880 --> 01:19:41.270 align:start position:0% protocol more understandable for future Generations<01:19:39.360> is<01:19:40.020> anyone<01:19:40.500> interested<01:19:41.040> in<01:19:41.159> that 01:19:41.270 --> 01:19:41.280 align:start position:0% Generations is anyone interested in that 01:19:41.280 --> 01:19:44.090 align:start position:0% Generations is anyone interested in that or<01:19:41.520> is<01:19:41.880> that<01:19:42.120> for<01:19:42.540> later<01:19:42.719> I<01:19:43.560> heard<01:19:43.739> some<01:19:43.920> good 01:19:44.090 --> 01:19:44.100 align:start position:0% or is that for later I heard some good 01:19:44.100 --> 01:19:47.270 align:start position:0% or is that for later I heard some good arguments<01:19:44.820> about<01:19:45.500> cleaning<01:19:46.500> up<01:19:46.620> the<01:19:46.800> deposit 01:19:47.270 --> 01:19:47.280 align:start position:0% arguments about cleaning up the deposit 01:19:47.280 --> 01:19:51.110 align:start position:0% arguments about cleaning up the deposit contracts<01:19:47.880> to<01:19:48.659> keep<01:19:49.100> the<01:19:50.100> supply<01:19:50.400> in<01:19:51.000> the 01:19:51.110 --> 01:19:51.120 align:start position:0% contracts to keep the supply in the 01:19:51.120 --> 01:19:53.450 align:start position:0% contracts to keep the supply in the balances<01:19:51.540> actually<01:19:52.380> matching<01:19:52.980> all<01:19:53.280> the 01:19:53.450 --> 01:19:53.460 align:start position:0% balances actually matching all the 01:19:53.460 --> 01:19:56.810 align:start position:0% balances actually matching all the expectations<01:19:53.940> rather<01:19:54.840> than<01:19:55.020> looking<01:19:55.320> up<01:19:55.820> or 01:19:56.810 --> 01:19:56.820 align:start position:0% expectations rather than looking up or 01:19:56.820 --> 01:19:59.870 align:start position:0% expectations rather than looking up or like<01:19:57.300> burning<01:19:57.780> the<01:19:58.199> the<01:19:58.739> deposits<01:19:59.520> and<01:19:59.699> then 01:19:59.870 --> 01:19:59.880 align:start position:0% like burning the the deposits and then 01:19:59.880 --> 01:20:02.330 align:start position:0% like burning the the deposits and then minting<01:20:00.360> through<01:20:00.900> withdrawals<01:20:01.500> so<01:20:02.219> that's 01:20:02.330 --> 01:20:02.340 align:start position:0% minting through withdrawals so that's 01:20:02.340 --> 01:20:04.669 align:start position:0% minting through withdrawals so that's fair<01:20:02.640> I<01:20:03.300> do<01:20:03.420> think<01:20:03.600> deposits<01:20:04.260> are<01:20:04.320> user 01:20:04.669 --> 01:20:04.679 align:start position:0% fair I do think deposits are user 01:20:04.679 --> 01:20:06.470 align:start position:0% fair I do think deposits are user initiated<01:20:05.219> and<01:20:05.699> withdrawals<01:20:06.179> are<01:20:06.300> system 01:20:06.470 --> 01:20:06.480 align:start position:0% initiated and withdrawals are system 01:20:06.480 --> 01:20:08.630 align:start position:0% initiated and withdrawals are system initiated<01:20:07.080> so<01:20:07.860> they're<01:20:08.100> fundamentally 01:20:08.630 --> 01:20:08.640 align:start position:0% initiated so they're fundamentally 01:20:08.640 --> 01:20:12.830 align:start position:0% initiated so they're fundamentally different 01:20:12.830 --> 01:20:12.840 align:start position:0% 01:20:12.840 --> 01:20:14.570 align:start position:0% but<01:20:13.320> yes<01:20:13.440> there's<01:20:13.679> a<01:20:13.800> lot<01:20:13.860> of<01:20:13.980> tech<01:20:14.100> debt<01:20:14.340> there 01:20:14.570 --> 01:20:14.580 align:start position:0% but yes there's a lot of tech debt there 01:20:14.580 --> 01:20:17.330 align:start position:0% but yes there's a lot of tech debt there and<01:20:14.760> yes<01:20:15.000> we<01:20:15.239> will<01:20:15.420> fix<01:20:15.960> it<01:20:16.199> in<01:20:16.440> a<01:20:16.560> hard<01:20:16.920> Fork<01:20:17.219> at 01:20:17.330 --> 01:20:17.340 align:start position:0% and yes we will fix it in a hard Fork at 01:20:17.340 --> 01:20:18.229 align:start position:0% and yes we will fix it in a hard Fork at some<01:20:17.460> point 01:20:18.229 --> 01:20:18.239 align:start position:0% some point 01:20:18.239 --> 01:20:20.750 align:start position:0% some point um just<01:20:18.900> to<01:20:19.260> simplify<01:20:19.679> like<01:20:20.159> it's<01:20:20.520> it's 01:20:20.750 --> 01:20:20.760 align:start position:0% um just to simplify like it's it's 01:20:20.760 --> 01:20:22.729 align:start position:0% um just to simplify like it's it's ridiculous<01:20:21.300> the<01:20:21.659> beacon<01:20:22.080> chain<01:20:22.260> is<01:20:22.560> still 01:20:22.729 --> 01:20:22.739 align:start position:0% ridiculous the beacon chain is still 01:20:22.739 --> 01:20:25.850 align:start position:0% ridiculous the beacon chain is still voting<01:20:23.100> on<01:20:23.280> what<01:20:23.460> it<01:20:23.580> sees<01:20:23.880> as<01:20:24.060> the<01:20:24.239> Ethan<01:20:24.659> head 01:20:25.850 --> 01:20:25.860 align:start position:0% voting on what it sees as the Ethan head 01:20:25.860 --> 01:20:27.770 align:start position:0% voting on what it sees as the Ethan head after<01:20:26.340> the<01:20:26.640> merge 01:20:27.770 --> 01:20:27.780 align:start position:0% after the merge 01:20:27.780 --> 01:20:30.310 align:start position:0% after the merge and<01:20:28.080> it's<01:20:28.260> 8<01:20:28.679> 000<01:20:28.739> blocks<01:20:29.159> behind 01:20:30.310 --> 01:20:30.320 align:start position:0% and it's 8 000 blocks behind 01:20:30.320 --> 01:20:32.810 align:start position:0% and it's 8 000 blocks behind but<01:20:31.320> hey<01:20:31.500> it<01:20:31.739> works<01:20:31.980> right<01:20:32.340> and<01:20:32.580> we<01:20:32.699> didn't 01:20:32.810 --> 01:20:32.820 align:start position:0% but hey it works right and we didn't 01:20:32.820 --> 01:20:34.250 align:start position:0% but hey it works right and we didn't have<01:20:33.000> to<01:20:33.120> touch<01:20:33.179> it<01:20:33.360> and<01:20:33.480> that<01:20:33.600> was<01:20:33.719> good<01:20:33.840> but 01:20:34.250 --> 01:20:34.260 align:start position:0% have to touch it and that was good but 01:20:34.260 --> 01:20:37.970 align:start position:0% have to touch it and that was good but we<01:20:34.380> will<01:20:34.560> have<01:20:34.679> to<01:20:34.739> fix<01:20:34.860> that 01:20:37.970 --> 01:20:37.980 align:start position:0% 01:20:37.980 --> 01:20:43.189 align:start position:0% I'm<01:20:38.520> curious<01:20:38.760> to<01:20:38.880> hear<01:20:39.000> from<01:20:39.179> the<01:20:39.300> 4844<01:20:39.900> Maxis 01:20:43.189 --> 01:20:43.199 align:start position:0% 01:20:43.199 --> 01:20:47.030 align:start position:0% the<01:20:43.380> thing<01:20:43.860> about<01:20:44.040> fart<01:20:44.400> for<01:20:44.699> four<01:20:44.940> is<01:20:45.320> is<01:20:46.320> it's 01:20:47.030 --> 01:20:47.040 align:start position:0% the thing about fart for four is is it's 01:20:47.040 --> 01:20:50.209 align:start position:0% the thing about fart for four is is it's this<01:20:47.640> complement<01:20:48.360> to<01:20:48.840> proof<01:20:49.260> of<01:20:49.320> stake<01:20:49.679> in<01:20:49.980> the 01:20:50.209 --> 01:20:50.219 align:start position:0% this complement to proof of stake in the 01:20:50.219 --> 01:20:53.090 align:start position:0% this complement to proof of stake in the whole<01:20:50.880> dream<01:20:51.179> of<01:20:51.360> Serenity<01:20:51.800> so<01:20:52.800> we're<01:20:52.920> very 01:20:53.090 --> 01:20:53.100 align:start position:0% whole dream of Serenity so we're very 01:20:53.100 --> 01:20:55.790 align:start position:0% whole dream of Serenity so we're very motivated<01:20:53.520> to<01:20:53.760> Shepherds<01:20:54.360> at<01:20:55.199> the<01:20:55.380> same<01:20:55.500> time 01:20:55.790 --> 01:20:55.800 align:start position:0% motivated to Shepherds at the same time 01:20:55.800 --> 01:20:59.030 align:start position:0% motivated to Shepherds at the same time I<01:20:56.760> think<01:20:56.940> there<01:20:57.179> are<01:20:57.420> goal<01:20:57.960> posts<01:20:58.320> and<01:20:58.739> like 01:20:59.030 --> 01:20:59.040 align:start position:0% I think there are goal posts and like 01:20:59.040 --> 01:21:00.950 align:start position:0% I think there are goal posts and like the<01:20:59.280> communication<01:20:59.880> about<01:21:00.239> the<01:21:00.600> state<01:21:00.780> of 01:21:00.950 --> 01:21:00.960 align:start position:0% the communication about the state of 01:21:00.960 --> 01:21:04.970 align:start position:0% the communication about the state of ethereum<01:21:01.380> are<01:21:02.100> not<01:21:02.280> that<01:21:02.460> clear<01:21:02.780> and<01:21:03.780> so<01:21:04.140> I'd 01:21:04.970 --> 01:21:04.980 align:start position:0% ethereum are not that clear and so I'd 01:21:04.980 --> 01:21:07.310 align:start position:0% ethereum are not that clear and so I'd like<01:21:05.219> a<01:21:05.400> better<01:21:05.520> platform<01:21:05.940> for<01:21:06.179> testing<01:21:06.659> I'd 01:21:07.310 --> 01:21:07.320 align:start position:0% like a better platform for testing I'd 01:21:07.320 --> 01:21:10.070 align:start position:0% like a better platform for testing I'd like<01:21:07.560> testing<01:21:08.159> to<01:21:08.340> be<01:21:08.460> less<01:21:08.699> stagnant<01:21:09.239> I'd 01:21:10.070 --> 01:21:10.080 align:start position:0% like testing to be less stagnant I'd 01:21:10.080 --> 01:21:13.310 align:start position:0% like testing to be less stagnant I'd like<01:21:10.320> to<01:21:10.500> contribute<01:21:10.860> to<01:21:11.040> testing<01:21:11.600> and<01:21:12.600> often 01:21:13.310 --> 01:21:13.320 align:start position:0% like to contribute to testing and often 01:21:13.320 --> 01:21:16.370 align:start position:0% like to contribute to testing and often I<01:21:13.739> see<01:21:13.920> that<01:21:14.400> some<01:21:14.760> of<01:21:14.940> the<01:21:15.060> test<01:21:15.239> tooling<01:21:15.719> are 01:21:16.370 --> 01:21:16.380 align:start position:0% I see that some of the test tooling are 01:21:16.380 --> 01:21:19.010 align:start position:0% I see that some of the test tooling are locked<01:21:16.739> into<01:21:17.100> either<01:21:17.880> a<01:21:18.120> research<01:21:18.420> team<01:21:18.659> or 01:21:19.010 --> 01:21:19.020 align:start position:0% locked into either a research team or 01:21:19.020 --> 01:21:21.590 align:start position:0% locked into either a research team or the<01:21:19.140> guest<01:21:19.380> team<01:21:19.560> of<01:21:19.800> hives<01:21:20.060> and<01:21:21.060> if<01:21:21.239> we<01:21:21.420> open 01:21:21.590 --> 01:21:21.600 align:start position:0% the guest team of hives and if we open 01:21:21.600 --> 01:21:23.990 align:start position:0% the guest team of hives and if we open these<01:21:21.960> things<01:21:22.080> more<01:21:22.380> like<01:21:22.739> up<01:21:23.040> and<01:21:23.880> we 01:21:23.990 --> 01:21:24.000 align:start position:0% these things more like up and we 01:21:24.000 --> 01:21:25.669 align:start position:0% these things more like up and we communicate<01:21:24.540> it<01:21:24.659> and<01:21:24.900> that's<01:21:25.199> caused<01:21:25.620> about 01:21:25.669 --> 01:21:25.679 align:start position:0% communicate it and that's caused about 01:21:25.679 --> 01:21:28.189 align:start position:0% communicate it and that's caused about these<01:21:26.040> things<01:21:26.159> if<01:21:26.760> we<01:21:27.120> I<01:21:27.480> think<01:21:27.540> we<01:21:27.780> can<01:21:27.900> make<01:21:28.020> a 01:21:28.189 --> 01:21:28.199 align:start position:0% these things if we I think we can make a 01:21:28.199 --> 01:21:31.490 align:start position:0% these things if we I think we can make a lot<01:21:28.380> more<01:21:29.159> of<01:21:29.400> these<01:21:29.699> quick<01:21:29.820> programs<01:21:30.540> towards 01:21:31.490 --> 01:21:31.500 align:start position:0% lot more of these quick programs towards 01:21:31.500 --> 01:21:34.250 align:start position:0% lot more of these quick programs towards the<01:21:31.620> states<01:21:31.860> we're<01:21:32.699> very<01:21:33.000> happy<01:21:33.179> to<01:21:33.480> to<01:21:33.900> work 01:21:34.250 --> 01:21:34.260 align:start position:0% the states we're very happy to to work 01:21:34.260 --> 01:21:40.910 align:start position:0% the states we're very happy to to work on<01:21:34.440> Forex<01:21:34.800> refer<01:21:35.159> other<01:21:35.460> complex<01:21:35.880> upgrades 01:21:40.910 --> 01:21:40.920 align:start position:0% 01:21:40.920 --> 01:21:42.649 align:start position:0% um yeah<01:21:41.219> I<01:21:41.520> want<01:21:41.640> to<01:21:41.760> share<01:21:41.880> my<01:21:42.120> perspective 01:21:42.649 --> 01:21:42.659 align:start position:0% um yeah I want to share my perspective 01:21:42.659 --> 01:21:44.870 align:start position:0% um yeah I want to share my perspective on<01:21:42.840> as<01:21:43.080> well<01:21:43.199> I<01:21:43.380> think<01:21:43.560> like<01:21:43.739> we<01:21:44.340> have<01:21:44.460> heard<01:21:44.699> a 01:21:44.870 --> 01:21:44.880 align:start position:0% on as well I think like we have heard a 01:21:44.880 --> 01:21:46.490 align:start position:0% on as well I think like we have heard a lot<01:21:44.940> about<01:21:45.120> tech<01:21:45.360> debt<01:21:45.780> this<01:21:45.960> is<01:21:46.080> which<01:21:46.320> is 01:21:46.490 --> 01:21:46.500 align:start position:0% lot about tech debt this is which is 01:21:46.500 --> 01:21:49.550 align:start position:0% lot about tech debt this is which is like<01:21:46.679> Fair<01:21:46.920> these<01:21:47.580> the<01:21:48.120> the<01:21:48.420> devs<01:21:49.140> here<01:21:49.320> like 01:21:49.550 --> 01:21:49.560 align:start position:0% like Fair these the the devs here like 01:21:49.560 --> 01:21:51.709 align:start position:0% like Fair these the the devs here like they<01:21:49.860> have<01:21:49.980> the<01:21:50.340> best<01:21:50.760> overview<01:21:51.120> of<01:21:51.360> that<01:21:51.480> and 01:21:51.709 --> 01:21:51.719 align:start position:0% they have the best overview of that and 01:21:51.719 --> 01:21:53.990 align:start position:0% they have the best overview of that and that<01:21:51.900> is<01:21:52.080> like<01:21:52.320> uh<01:21:53.100> a<01:21:53.340> very<01:21:53.460> important<01:21:53.820> point 01:21:53.990 --> 01:21:54.000 align:start position:0% that is like uh a very important point 01:21:54.000 --> 01:21:55.430 align:start position:0% that is like uh a very important point of<01:21:54.360> course 01:21:55.430 --> 01:21:55.440 align:start position:0% of course 01:21:55.440 --> 01:21:57.350 align:start position:0% of course um<01:21:55.560> but<01:21:55.980> I<01:21:56.280> think<01:21:56.400> we<01:21:56.699> also<01:21:56.940> have<01:21:57.120> a<01:21:57.300> different 01:21:57.350 --> 01:21:57.360 align:start position:0% um but I think we also have a different 01:21:57.360 --> 01:21:59.990 align:start position:0% um but I think we also have a different kind<01:21:57.600> of<01:21:57.719> debt<01:21:58.020> which<01:21:58.320> is<01:21:58.500> like<01:21:58.800> right<01:21:59.340> now<01:21:59.520> we 01:21:59.990 --> 01:22:00.000 align:start position:0% kind of debt which is like right now we 01:22:00.000 --> 01:22:02.390 align:start position:0% kind of debt which is like right now we cannot<01:22:00.360> serve<01:22:00.780> the<01:22:00.960> vast<01:22:01.260> majority<01:22:01.739> of<01:22:02.159> people 01:22:02.390 --> 01:22:02.400 align:start position:0% cannot serve the vast majority of people 01:22:02.400 --> 01:22:05.149 align:start position:0% cannot serve the vast majority of people who<01:22:02.940> might<01:22:03.060> want<01:22:03.239> to<01:22:03.360> use<01:22:03.480> ethereum<01:22:04.080> so<01:22:04.679> like<01:22:04.860> I 01:22:05.149 --> 01:22:05.159 align:start position:0% who might want to use ethereum so like I 01:22:05.159 --> 01:22:07.430 align:start position:0% who might want to use ethereum so like I think<01:22:05.219> like<01:22:05.520> it<01:22:06.000> illustrates<01:22:06.840> my<01:22:07.020> point<01:22:07.199> from 01:22:07.430 --> 01:22:07.440 align:start position:0% think like it illustrates my point from 01:22:07.440 --> 01:22:08.750 align:start position:0% think like it illustrates my point from earlier<01:22:07.800> that 01:22:08.750 --> 01:22:08.760 align:start position:0% earlier that 01:22:08.760 --> 01:22:10.490 align:start position:0% earlier that um we<01:22:08.940> are<01:22:09.060> having<01:22:09.239> these<01:22:09.540> discussions<01:22:09.960> among 01:22:10.490 --> 01:22:10.500 align:start position:0% um we are having these discussions among 01:22:10.500 --> 01:22:12.110 align:start position:0% um we are having these discussions among core<01:22:10.679> deaths<01:22:11.219> and<01:22:11.460> they<01:22:11.699> are<01:22:11.820> good<01:22:11.940> and 01:22:12.110 --> 01:22:12.120 align:start position:0% core deaths and they are good and 01:22:12.120 --> 01:22:14.810 align:start position:0% core deaths and they are good and they're<01:22:12.300> important<01:22:12.719> but<01:22:13.320> somehow<01:22:13.800> uh<01:22:14.640> they 01:22:14.810 --> 01:22:14.820 align:start position:0% they're important but somehow uh they 01:22:14.820 --> 01:22:16.310 align:start position:0% they're important but somehow uh they can't<01:22:15.000> be<01:22:15.239> the<01:22:15.420> only<01:22:15.540> input<01:22:15.840> into<01:22:16.080> the 01:22:16.310 --> 01:22:16.320 align:start position:0% can't be the only input into the 01:22:16.320 --> 01:22:17.810 align:start position:0% can't be the only input into the decision<01:22:16.560> making 01:22:17.810 --> 01:22:17.820 align:start position:0% decision making 01:22:17.820 --> 01:22:19.610 align:start position:0% decision making um so<01:22:18.000> I<01:22:18.179> don't<01:22:18.239> want<01:22:18.420> to<01:22:18.600> Clearly<01:22:18.960> say<01:22:19.080> like<01:22:19.320> I 01:22:19.610 --> 01:22:19.620 align:start position:0% um so I don't want to Clearly say like I 01:22:19.620 --> 01:22:22.250 align:start position:0% um so I don't want to Clearly say like I can't<01:22:19.739> say<01:22:19.980> like<01:22:20.280> we<01:22:20.820> have<01:22:21.000> to<01:22:21.179> do<01:22:21.300> 4844<01:22:22.020> as 01:22:22.250 --> 01:22:22.260 align:start position:0% can't say like we have to do 4844 as 01:22:22.260 --> 01:22:25.550 align:start position:0% can't say like we have to do 4844 as part<01:22:22.500> of<01:22:22.679> Shanghai<01:22:23.400> uh<01:22:24.360> but<01:22:24.960> personally<01:22:25.320> I 01:22:25.550 --> 01:22:25.560 align:start position:0% part of Shanghai uh but personally I 01:22:25.560 --> 01:22:27.530 align:start position:0% part of Shanghai uh but personally I would<01:22:25.679> love<01:22:25.800> to<01:22:25.980> see<01:22:26.159> it<01:22:26.340> and<01:22:26.760> I<01:22:27.239> think<01:22:27.360> there 01:22:27.530 --> 01:22:27.540 align:start position:0% would love to see it and I think there 01:22:27.540 --> 01:22:29.090 align:start position:0% would love to see it and I think there are<01:22:27.659> very<01:22:27.780> good<01:22:27.960> reasons<01:22:28.320> to<01:22:28.440> try<01:22:28.620> to<01:22:28.800> do<01:22:28.920> it 01:22:29.090 --> 01:22:29.100 align:start position:0% are very good reasons to try to do it 01:22:29.100 --> 01:22:32.209 align:start position:0% are very good reasons to try to do it and<01:22:30.120> um<01:22:30.239> and<01:22:30.540> I<01:22:30.659> think<01:22:30.780> like<01:22:31.080> only<01:22:31.620> looking<01:22:31.920> at 01:22:32.209 --> 01:22:32.219 align:start position:0% and um and I think like only looking at 01:22:32.219 --> 01:22:34.010 align:start position:0% and um and I think like only looking at the<01:22:32.400> tech<01:22:32.520> depth<01:22:33.000> and<01:22:33.120> saying<01:22:33.420> like<01:22:33.600> we<01:22:33.900> can't 01:22:34.010 --> 01:22:34.020 align:start position:0% the tech depth and saying like we can't 01:22:34.020 --> 01:22:35.810 align:start position:0% the tech depth and saying like we can't do<01:22:34.260> it<01:22:34.380> because<01:22:34.560> of<01:22:34.800> this<01:22:34.980> and<01:22:35.219> we<01:22:35.400> need<01:22:35.520> to<01:22:35.640> do 01:22:35.810 --> 01:22:35.820 align:start position:0% do it because of this and we need to do 01:22:35.820 --> 01:22:37.550 align:start position:0% do it because of this and we need to do everything<01:22:36.060> in<01:22:36.360> sequence 01:22:37.550 --> 01:22:37.560 align:start position:0% everything in sequence 01:22:37.560 --> 01:22:39.649 align:start position:0% everything in sequence um<01:22:37.620> is<01:22:37.860> is<01:22:38.100> not<01:22:38.340> enough<01:22:38.520> in<01:22:38.820> my<01:22:38.940> opinion<01:22:39.239> in 01:22:39.649 --> 01:22:39.659 align:start position:0% um is is not enough in my opinion in 01:22:39.659 --> 01:22:42.229 align:start position:0% um is is not enough in my opinion in arguing<01:22:40.080> against<01:22:40.199> it<01:22:40.500> like<01:22:40.920> it's<01:22:41.520> um<01:22:41.580> it's<01:22:42.060> uh 01:22:42.229 --> 01:22:42.239 align:start position:0% arguing against it like it's um it's uh 01:22:42.239 --> 01:22:44.990 align:start position:0% arguing against it like it's um it's uh we<01:22:42.659> we<01:22:42.840> have<01:22:43.140> to<01:22:43.380> like<01:22:43.679> at<01:22:44.280> some<01:22:44.400> point<01:22:44.520> also 01:22:44.990 --> 01:22:45.000 align:start position:0% we we have to like at some point also 01:22:45.000 --> 01:22:47.090 align:start position:0% we we have to like at some point also start<01:22:45.239> seeing<01:22:45.659> the<01:22:45.900> other<01:22:46.020> side<01:22:46.199> like<01:22:46.500> okay<01:22:46.739> so 01:22:47.090 --> 01:22:47.100 align:start position:0% start seeing the other side like okay so 01:22:47.100 --> 01:22:49.490 align:start position:0% start seeing the other side like okay so what<01:22:47.699> what<01:22:47.880> is<01:22:48.120> the<01:22:48.540> consequence<01:22:49.020> of<01:22:49.260> not 01:22:49.490 --> 01:22:49.500 align:start position:0% what what is the consequence of not 01:22:49.500 --> 01:22:51.649 align:start position:0% what what is the consequence of not doing<01:22:49.679> it<01:22:49.920> like<01:22:50.280> my<01:22:50.520> fear<01:22:50.880> like<01:22:51.300> of<01:22:51.480> course 01:22:51.649 --> 01:22:51.659 align:start position:0% doing it like my fear like of course 01:22:51.659 --> 01:22:54.890 align:start position:0% doing it like my fear like of course like<01:22:51.840> if<01:22:52.080> we<01:22:52.260> have<01:22:52.440> say<01:22:52.739> Shanghai 01:22:54.890 --> 01:22:54.900 align:start position:0% like if we have say Shanghai 01:22:54.900 --> 01:22:57.770 align:start position:0% like if we have say Shanghai for<01:22:55.620> we<01:22:55.980> managed<01:22:56.280> to<01:22:56.340> do<01:22:56.580> it<01:22:56.699> in<01:22:57.000> February<01:22:57.420> and 01:22:57.770 --> 01:22:57.780 align:start position:0% for we managed to do it in February and 01:22:57.780 --> 01:22:59.990 align:start position:0% for we managed to do it in February and then<01:22:57.900> we<01:22:58.140> can<01:22:58.320> do<01:22:58.500> like<01:22:58.739> uh<01:22:59.219> for<01:22:59.460> it<01:22:59.640> for<01:22:59.820> free 01:22:59.990 --> 01:23:00.000 align:start position:0% then we can do like uh for it for free 01:23:00.000 --> 01:23:01.610 align:start position:0% then we can do like uh for it for free for<01:23:00.360> a<01:23:00.480> few<01:23:00.540> months<01:23:00.780> later<01:23:00.900> okay<01:23:01.260> like 01:23:01.610 --> 01:23:01.620 align:start position:0% for a few months later okay like 01:23:01.620 --> 01:23:03.950 align:start position:0% for a few months later okay like everyone's<01:23:02.340> happy<01:23:02.460> with<01:23:02.699> that<01:23:02.880> but<01:23:03.300> like<01:23:03.540> what 01:23:03.950 --> 01:23:03.960 align:start position:0% everyone's happy with that but like what 01:23:03.960 --> 01:23:05.750 align:start position:0% everyone's happy with that but like what happens<01:23:04.199> if<01:23:04.679> actually<01:23:04.860> Shanghai<01:23:05.400> does<01:23:05.640> not 01:23:05.750 --> 01:23:05.760 align:start position:0% happens if actually Shanghai does not 01:23:05.760 --> 01:23:08.209 align:start position:0% happens if actually Shanghai does not happen<01:23:05.940> in<01:23:06.300> February<01:23:06.600> it<01:23:06.780> happens<01:23:07.020> in<01:23:07.500> June<01:23:08.100> it 01:23:08.209 --> 01:23:08.219 align:start position:0% happen in February it happens in June it 01:23:08.219 --> 01:23:10.430 align:start position:0% happen in February it happens in June it happens<01:23:08.400> in<01:23:08.760> September<01:23:09.300> or<01:23:09.540> something<01:23:09.719> when 01:23:10.430 --> 01:23:10.440 align:start position:0% happens in September or something when 01:23:10.440 --> 01:23:13.729 align:start position:0% happens in September or something when 4844<01:23:11.280> slips<01:23:11.640> into<01:23:11.820> 2024<01:23:12.719> I<01:23:13.080> think<01:23:13.199> I<01:23:13.440> mean<01:23:13.500> I 01:23:13.729 --> 01:23:13.739 align:start position:0% 4844 slips into 2024 I think I mean I 01:23:13.739 --> 01:23:15.169 align:start position:0% 4844 slips into 2024 I think I mean I would<01:23:13.860> be<01:23:13.980> fairly<01:23:14.340> unhappy<01:23:14.699> with<01:23:14.820> that<01:23:15.000> so 01:23:15.169 --> 01:23:15.179 align:start position:0% would be fairly unhappy with that so 01:23:15.179 --> 01:23:17.090 align:start position:0% would be fairly unhappy with that so like<01:23:15.360> we<01:23:15.600> should<01:23:15.719> consider<01:23:16.260> these<01:23:16.679> scenarios 01:23:17.090 --> 01:23:17.100 align:start position:0% like we should consider these scenarios 01:23:17.100 --> 01:23:18.649 align:start position:0% like we should consider these scenarios and<01:23:17.460> we<01:23:17.640> should<01:23:17.760> also<01:23:18.000> think<01:23:18.120> about<01:23:18.300> what<01:23:18.540> it 01:23:18.649 --> 01:23:18.659 align:start position:0% and we should also think about what it 01:23:18.659 --> 01:23:20.570 align:start position:0% and we should also think about what it means<01:23:18.840> to<01:23:18.960> ethereum<01:23:19.380> yes<01:23:19.560> it's<01:23:19.739> like<01:23:19.980> it's<01:23:20.400> a 01:23:20.570 --> 01:23:20.580 align:start position:0% means to ethereum yes it's like it's a 01:23:20.580 --> 01:23:22.610 align:start position:0% means to ethereum yes it's like it's a bear<01:23:20.760> market<01:23:21.060> now<01:23:21.420> so<01:23:21.719> maybe<01:23:21.840> we<01:23:22.199> don't<01:23:22.320> have 01:23:22.610 --> 01:23:22.620 align:start position:0% bear market now so maybe we don't have 01:23:22.620 --> 01:23:25.550 align:start position:0% bear market now so maybe we don't have these<01:23:23.100> high<01:23:23.580> fees<01:23:24.000> as<01:23:24.300> pressure<01:23:24.659> pressing<01:23:25.380> an 01:23:25.550 --> 01:23:25.560 align:start position:0% these high fees as pressure pressing an 01:23:25.560 --> 01:23:27.709 align:start position:0% these high fees as pressure pressing an issue<01:23:25.860> anymore<01:23:26.159> but<01:23:26.820> I<01:23:27.000> think<01:23:27.120> they<01:23:27.360> are<01:23:27.480> still 01:23:27.709 --> 01:23:27.719 align:start position:0% issue anymore but I think they are still 01:23:27.719 --> 01:23:29.630 align:start position:0% issue anymore but I think they are still actually<01:23:27.900> a<01:23:28.140> pressing<01:23:28.380> issue<01:23:28.739> because<01:23:28.920> right 01:23:29.630 --> 01:23:29.640 align:start position:0% actually a pressing issue because right 01:23:29.640 --> 01:23:32.270 align:start position:0% actually a pressing issue because right now<01:23:29.820> maybe<01:23:30.239> like<01:23:30.659> we<01:23:30.900> don't<01:23:31.080> feel<01:23:31.440> the<01:23:31.679> pain<01:23:31.860> as 01:23:32.270 --> 01:23:32.280 align:start position:0% now maybe like we don't feel the pain as 01:23:32.280 --> 01:23:34.970 align:start position:0% now maybe like we don't feel the pain as much<01:23:32.520> because<01:23:32.940> our<01:23:33.840> the<01:23:34.260> things<01:23:34.440> that<01:23:34.679> we<01:23:34.860> have 01:23:34.970 --> 01:23:34.980 align:start position:0% much because our the things that we have 01:23:34.980 --> 01:23:37.850 align:start position:0% much because our the things that we have been<01:23:35.159> doing<01:23:35.400> are<01:23:35.880> fine<01:23:36.120> but<01:23:36.840> still<01:23:37.140> a<01:23:37.620> lot<01:23:37.739> of 01:23:37.850 --> 01:23:37.860 align:start position:0% been doing are fine but still a lot of 01:23:37.860 --> 01:23:39.830 align:start position:0% been doing are fine but still a lot of applications<01:23:38.340> are<01:23:38.820> not<01:23:39.000> being<01:23:39.300> built<01:23:39.659> because 01:23:39.830 --> 01:23:39.840 align:start position:0% applications are not being built because 01:23:39.840 --> 01:23:41.750 align:start position:0% applications are not being built because the<01:23:40.140> fees<01:23:40.380> are<01:23:40.560> too<01:23:40.739> high<01:23:40.860> and<01:23:41.159> because<01:23:41.340> they 01:23:41.750 --> 01:23:41.760 align:start position:0% the fees are too high and because they 01:23:41.760 --> 01:23:43.850 align:start position:0% the fees are too high and because they can't<01:23:41.940> like<01:23:42.360> the<01:23:42.840> experimentation<01:23:43.500> can't 01:23:43.850 --> 01:23:43.860 align:start position:0% can't like the experimentation can't 01:23:43.860 --> 01:23:46.070 align:start position:0% can't like the experimentation can't happen<01:23:44.100> because<01:23:44.400> I<01:23:44.820> can't<01:23:44.940> like<01:23:45.239> do<01:23:45.659> some<01:23:45.900> fun 01:23:46.070 --> 01:23:46.080 align:start position:0% happen because I can't like do some fun 01:23:46.080 --> 01:23:47.930 align:start position:0% happen because I can't like do some fun stuff<01:23:46.260> if<01:23:46.500> things<01:23:46.679> costs<01:23:47.159> one<01:23:47.520> dollar<01:23:47.699> per 01:23:47.930 --> 01:23:47.940 align:start position:0% stuff if things costs one dollar per 01:23:47.940 --> 01:23:49.910 align:start position:0% stuff if things costs one dollar per transaction<01:23:48.420> which<01:23:48.960> I<01:23:49.140> could<01:23:49.260> do<01:23:49.380> if<01:23:49.560> it's<01:23:49.739> one 01:23:49.910 --> 01:23:49.920 align:start position:0% transaction which I could do if it's one 01:23:49.920 --> 01:23:51.649 align:start position:0% transaction which I could do if it's one cent<01:23:50.100> per<01:23:50.280> transaction<01:23:50.699> so<01:23:51.060> I<01:23:51.179> think<01:23:51.300> like<01:23:51.480> we 01:23:51.649 --> 01:23:51.659 align:start position:0% cent per transaction so I think like we 01:23:51.659 --> 01:23:54.649 align:start position:0% cent per transaction so I think like we should<01:23:51.840> like<01:23:52.560> be<01:23:53.340> more<01:23:53.580> willing<01:23:54.179> to<01:23:54.300> like 01:23:54.649 --> 01:23:54.659 align:start position:0% should like be more willing to like 01:23:54.659 --> 01:23:56.810 align:start position:0% should like be more willing to like think<01:23:55.380> about<01:23:55.560> this<01:23:55.860> part<01:23:56.100> as<01:23:56.280> well<01:23:56.460> and<01:23:56.640> I 01:23:56.810 --> 01:23:56.820 align:start position:0% think about this part as well and I 01:23:56.820 --> 01:23:58.610 align:start position:0% think about this part as well and I would<01:23:56.940> love<01:23:57.179> to<01:23:57.360> like<01:23:57.600> understand<01:23:57.960> how<01:23:58.320> we<01:23:58.500> can 01:23:58.610 --> 01:23:58.620 align:start position:0% would love to like understand how we can 01:23:58.620 --> 01:24:00.890 align:start position:0% would love to like understand how we can also<01:23:59.100> like<01:23:59.280> get<01:23:59.699> that<01:23:59.880> in<01:24:00.120> that<01:24:00.360> thinking<01:24:00.719> into 01:24:00.890 --> 01:24:00.900 align:start position:0% also like get that in that thinking into 01:24:00.900 --> 01:24:04.370 align:start position:0% also like get that in that thinking into our<01:24:01.140> governance<01:24:01.620> Pro<01:24:01.860> process<01:24:02.580> as<01:24:02.820> well 01:24:04.370 --> 01:24:04.380 align:start position:0% our governance Pro process as well 01:24:04.380 --> 01:24:06.050 align:start position:0% our governance Pro process as well so<01:24:04.860> uh 01:24:06.050 --> 01:24:06.060 align:start position:0% so uh 01:24:06.060 --> 01:24:08.810 align:start position:0% so uh currently<01:24:06.719> we're<01:24:07.020> releasing<01:24:07.500> artworks<01:24:08.400> uh 01:24:08.810 --> 01:24:08.820 align:start position:0% currently we're releasing artworks uh 01:24:08.820 --> 01:24:10.490 align:start position:0% currently we're releasing artworks uh basically<01:24:09.179> when<01:24:09.540> it's<01:24:09.719> ready 01:24:10.490 --> 01:24:10.500 align:start position:0% basically when it's ready 01:24:10.500 --> 01:24:13.729 align:start position:0% basically when it's ready so<01:24:11.100> the<01:24:11.460> more<01:24:11.640> things<01:24:11.880> we<01:24:12.060> put<01:24:12.300> inside<01:24:12.560> uh<01:24:13.560> the 01:24:13.729 --> 01:24:13.739 align:start position:0% so the more things we put inside uh the 01:24:13.739 --> 01:24:16.370 align:start position:0% so the more things we put inside uh the longer<01:24:14.100> it<01:24:14.219> takes<01:24:14.880> to<01:24:15.120> be<01:24:15.239> ready<01:24:15.360> because<01:24:15.719> of 01:24:16.370 --> 01:24:16.380 align:start position:0% longer it takes to be ready because of 01:24:16.380 --> 01:24:19.370 align:start position:0% longer it takes to be ready because of uh<01:24:16.800> testing<01:24:17.280> for<01:24:17.460> example<01:24:17.760> so 01:24:19.370 --> 01:24:19.380 align:start position:0% uh testing for example so 01:24:19.380 --> 01:24:22.370 align:start position:0% uh testing for example so if<01:24:20.040> we<01:24:20.159> actually<01:24:20.400> do<01:24:20.760> withdrawals<01:24:21.540> uh<01:24:22.080> which 01:24:22.370 --> 01:24:22.380 align:start position:0% if we actually do withdrawals uh which 01:24:22.380 --> 01:24:24.709 align:start position:0% if we actually do withdrawals uh which are<01:24:22.560> supposedly<01:24:22.980> simple<01:24:23.340> for<01:24:23.940> uh<01:24:24.360> the<01:24:24.540> talk 01:24:24.709 --> 01:24:24.719 align:start position:0% are supposedly simple for uh the talk 01:24:24.719 --> 01:24:28.490 align:start position:0% are supposedly simple for uh the talk from<01:24:24.960> yesterday<01:24:25.320> uh<01:24:26.360> was<01:24:27.360> less<01:24:27.840> reassuring 01:24:28.490 --> 01:24:28.500 align:start position:0% from yesterday uh was less reassuring 01:24:28.500 --> 01:24:30.290 align:start position:0% from yesterday uh was less reassuring regarding<01:24:28.920> that 01:24:30.290 --> 01:24:30.300 align:start position:0% regarding that 01:24:30.300 --> 01:24:30.950 align:start position:0% regarding that um 01:24:30.950 --> 01:24:30.960 align:start position:0% um 01:24:30.960 --> 01:24:33.350 align:start position:0% um we<01:24:31.620> can<01:24:31.800> yeah<01:24:32.219> maybe<01:24:32.400> in<01:24:32.640> February<01:24:33.000> we<01:24:33.179> can 01:24:33.350 --> 01:24:33.360 align:start position:0% we can yeah maybe in February we can 01:24:33.360 --> 01:24:36.110 align:start position:0% we can yeah maybe in February we can have<01:24:33.540> withdrawals<01:24:34.199> and<01:24:34.500> then<01:24:34.739> uh<01:24:35.100> for<01:24:35.219> 804<01:24:35.760> uh 01:24:36.110 --> 01:24:36.120 align:start position:0% have withdrawals and then uh for 804 uh 01:24:36.120 --> 01:24:37.610 align:start position:0% have withdrawals and then uh for 804 uh for<01:24:36.360> the<01:24:36.480> next<01:24:36.719> one<01:24:36.840> but<01:24:36.960> if<01:24:37.140> we<01:24:37.260> put<01:24:37.440> both 01:24:37.610 --> 01:24:37.620 align:start position:0% for the next one but if we put both 01:24:37.620 --> 01:24:39.709 align:start position:0% for the next one but if we put both together<01:24:37.920> uh<01:24:38.760> maybe<01:24:38.940> it<01:24:39.179> will<01:24:39.300> be<01:24:39.420> only<01:24:39.540> in 01:24:39.709 --> 01:24:39.719 align:start position:0% together uh maybe it will be only in 01:24:39.719 --> 01:24:41.270 align:start position:0% together uh maybe it will be only in June 01:24:41.270 --> 01:24:41.280 align:start position:0% June 01:24:41.280 --> 01:24:44.090 align:start position:0% June um<01:24:41.460> so<01:24:42.000> there<01:24:42.659> is<01:24:42.780> a<01:24:42.900> balance<01:24:43.140> there<01:24:43.320> so<01:24:43.920> I 01:24:44.090 --> 01:24:44.100 align:start position:0% um so there is a balance there so I 01:24:44.100 --> 01:24:45.590 align:start position:0% um so there is a balance there so I guess<01:24:44.219> one<01:24:44.460> question<01:24:44.699> there<01:24:45.000> is<01:24:45.179> like<01:24:45.300> do<01:24:45.480> you 01:24:45.590 --> 01:24:45.600 align:start position:0% guess one question there is like do you 01:24:45.600 --> 01:24:48.050 align:start position:0% guess one question there is like do you think<01:24:45.719> it's<01:24:45.840> impossible<01:24:46.440> to<01:24:46.739> have<01:24:46.980> a<01:24:47.159> yeah<01:24:47.460> one 01:24:48.050 --> 01:24:48.060 align:start position:0% think it's impossible to have a yeah one 01:24:48.060 --> 01:24:49.850 align:start position:0% think it's impossible to have a yeah one fork<01:24:48.480> in<01:24:48.659> February<01:24:49.140> and<01:24:49.320> then<01:24:49.440> another<01:24:49.620> one 01:24:49.850 --> 01:24:49.860 align:start position:0% fork in February and then another one 01:24:49.860 --> 01:24:50.990 align:start position:0% fork in February and then another one like<01:24:50.040> literally<01:24:50.400> three<01:24:50.580> or<01:24:50.699> four<01:24:50.820> months 01:24:50.990 --> 01:24:51.000 align:start position:0% like literally three or four months 01:24:51.000 --> 01:24:56.090 align:start position:0% like literally three or four months later 01:24:56.090 --> 01:24:56.100 align:start position:0% 01:24:56.100 --> 01:24:57.430 align:start position:0% in London 01:24:57.430 --> 01:24:57.440 align:start position:0% in London 01:24:57.440 --> 01:25:00.590 align:start position:0% in London okay<01:24:58.440> well<01:24:58.620> that's<01:24:58.860> uh<01:24:59.040> I<01:24:59.219> mean<01:24:59.340> one<01:25:00.179> I<01:25:00.480> mean 01:25:00.590 --> 01:25:00.600 align:start position:0% okay well that's uh I mean one I mean 01:25:00.600 --> 01:25:02.209 align:start position:0% okay well that's uh I mean one I mean this<01:25:00.840> is<01:25:00.960> like<01:25:01.140> a<01:25:01.320> discussion<01:25:01.679> but<01:25:01.860> just<01:25:02.040> like 01:25:02.209 --> 01:25:02.219 align:start position:0% this is like a discussion but just like 01:25:02.219 --> 01:25:03.709 align:start position:0% this is like a discussion but just like one<01:25:02.400> other<01:25:02.520> thing<01:25:02.760> I<01:25:02.940> wanted<01:25:03.060> to<01:25:03.300> add<01:25:03.420> just 01:25:03.709 --> 01:25:03.719 align:start position:0% one other thing I wanted to add just 01:25:03.719 --> 01:25:05.510 align:start position:0% one other thing I wanted to add just like<01:25:03.900> to<01:25:04.140> what<01:25:04.320> Dan<01:25:04.560> grad<01:25:04.860> said<01:25:05.040> is<01:25:05.280> like 01:25:05.510 --> 01:25:05.520 align:start position:0% like to what Dan grad said is like 01:25:05.520 --> 01:25:07.189 align:start position:0% like to what Dan grad said is like thinking<01:25:06.120> about<01:25:06.239> it<01:25:06.480> from<01:25:06.719> the<01:25:06.840> perspective 01:25:07.189 --> 01:25:07.199 align:start position:0% thinking about it from the perspective 01:25:07.199 --> 01:25:09.590 align:start position:0% thinking about it from the perspective of<01:25:07.500> tech<01:25:07.739> debt<01:25:08.159> of<01:25:08.340> layer<01:25:08.640> 2<01:25:08.820> protocols<01:25:09.300> and<01:25:09.420> of 01:25:09.590 --> 01:25:09.600 align:start position:0% of tech debt of layer 2 protocols and of 01:25:09.600 --> 01:25:12.110 align:start position:0% of tech debt of layer 2 protocols and of Roll-Ups<01:25:10.140> right<01:25:10.199> like<01:25:10.440> the<01:25:10.679> yeah<01:25:10.980> one<01:25:11.880> of<01:25:12.000> the 01:25:12.110 --> 01:25:12.120 align:start position:0% Roll-Ups right like the yeah one of the 01:25:12.120 --> 01:25:15.350 align:start position:0% Roll-Ups right like the yeah one of the kind<01:25:12.480> of<01:25:12.620> philosophical<01:25:13.620> goals<01:25:14.219> of<01:25:14.340> 4844<01:25:15.060> I 01:25:15.350 --> 01:25:15.360 align:start position:0% kind of philosophical goals of 4844 I 01:25:15.360 --> 01:25:18.530 align:start position:0% kind of philosophical goals of 4844 I think<01:25:15.540> was<01:25:15.840> to<01:25:16.140> kind<01:25:16.380> of<01:25:16.440> be<01:25:16.800> a<01:25:17.040> like<01:25:18.000> the 01:25:18.530 --> 01:25:18.540 align:start position:0% think was to kind of be a like the 01:25:18.540 --> 01:25:20.630 align:start position:0% think was to kind of be a like the changed<01:25:18.960> the<01:25:19.500> change<01:25:19.679> to<01:25:19.860> end<01:25:20.040> all<01:25:20.219> changes 01:25:20.630 --> 01:25:20.640 align:start position:0% changed the change to end all changes 01:25:20.640 --> 01:25:23.330 align:start position:0% changed the change to end all changes sort<01:25:21.179> of<01:25:21.300> for<01:25:21.600> uh<01:25:22.080> specifically<01:25:22.739> for<01:25:22.920> warrior 01:25:23.330 --> 01:25:23.340 align:start position:0% sort of for uh specifically for warrior 01:25:23.340 --> 01:25:26.930 align:start position:0% sort of for uh specifically for warrior twos<01:25:23.580> in<01:25:24.300> the<01:25:24.420> sense<01:25:24.659> that<01:25:25.280> 4844<01:25:26.280> introduces 01:25:26.930 --> 01:25:26.940 align:start position:0% twos in the sense that 4844 introduces 01:25:26.940 --> 01:25:29.209 align:start position:0% twos in the sense that 4844 introduces stuff<01:25:27.300> like<01:25:27.540> the<01:25:27.900> point<01:25:28.080> evaluation<01:25:28.620> breaking 01:25:29.209 --> 01:25:29.219 align:start position:0% stuff like the point evaluation breaking 01:25:29.219 --> 01:25:31.910 align:start position:0% stuff like the point evaluation breaking pile<01:25:29.400> and<01:25:29.640> the<01:25:29.880> concept<01:25:30.060> of<01:25:30.239> blobs<01:25:30.719> and<01:25:31.560> if 01:25:31.910 --> 01:25:31.920 align:start position:0% pile and the concept of blobs and if 01:25:31.920 --> 01:25:34.430 align:start position:0% pile and the concept of blobs and if that<01:25:32.219> allows<01:25:32.520> way<01:25:32.880> or<01:25:33.120> two<01:25:33.239> is<01:25:33.480> to<01:25:33.600> kind<01:25:33.900> of<01:25:34.020> set 01:25:34.430 --> 01:25:34.440 align:start position:0% that allows way or two is to kind of set 01:25:34.440 --> 01:25:35.990 align:start position:0% that allows way or two is to kind of set their<01:25:34.679> code<01:25:34.860> once<01:25:35.280> and<01:25:35.400> they<01:25:35.580> can<01:25:35.760> literally 01:25:35.990 --> 01:25:36.000 align:start position:0% their code once and they can literally 01:25:36.000 --> 01:25:37.610 align:start position:0% their code once and they can literally write<01:25:36.239> their<01:25:36.420> code<01:25:36.540> and<01:25:36.780> launch<01:25:36.960> it<01:25:37.199> and<01:25:37.440> then 01:25:37.610 --> 01:25:37.620 align:start position:0% write their code and launch it and then 01:25:37.620 --> 01:25:39.950 align:start position:0% write their code and launch it and then you<01:25:38.100> know<01:25:38.159> no<01:25:38.460> matter<01:25:38.640> how<01:25:39.120> much<01:25:39.239> we<01:25:39.540> screw 01:25:39.950 --> 01:25:39.960 align:start position:0% you know no matter how much we screw 01:25:39.960 --> 01:25:41.689 align:start position:0% you know no matter how much we screw around<01:25:40.140> with<01:25:40.560> the<01:25:40.800> yeah<01:25:41.159> sharding<01:25:41.580> design 01:25:41.689 --> 01:25:41.699 align:start position:0% around with the yeah sharding design 01:25:41.699 --> 01:25:43.250 align:start position:0% around with the yeah sharding design later<01:25:42.000> as<01:25:42.300> long<01:25:42.420> as<01:25:42.540> we<01:25:42.719> kind<01:25:42.840> of<01:25:42.960> screw<01:25:43.140> around 01:25:43.250 --> 01:25:43.260 align:start position:0% later as long as we kind of screw around 01:25:43.260 --> 01:25:45.530 align:start position:0% later as long as we kind of screw around within<01:25:43.679> certain<01:25:43.860> parameters<01:25:44.360> Roll-Ups<01:25:45.360> will 01:25:45.530 --> 01:25:45.540 align:start position:0% within certain parameters Roll-Ups will 01:25:45.540 --> 01:25:47.689 align:start position:0% within certain parameters Roll-Ups will be<01:25:45.659> able<01:25:45.840> to<01:25:45.960> kind<01:25:46.440> of<01:25:46.620> you<01:25:47.040> know<01:25:47.219> breathe<01:25:47.520> easy 01:25:47.689 --> 01:25:47.699 align:start position:0% be able to kind of you know breathe easy 01:25:47.699 --> 01:25:49.310 align:start position:0% be able to kind of you know breathe easy and<01:25:48.060> know<01:25:48.239> that<01:25:48.480> you<01:25:48.600> know<01:25:48.719> they<01:25:49.020> don't<01:25:49.199> have 01:25:49.310 --> 01:25:49.320 align:start position:0% and know that you know they don't have 01:25:49.320 --> 01:25:50.750 align:start position:0% and know that you know they don't have to<01:25:49.440> make<01:25:49.620> like<01:25:49.860> that<01:25:50.100> kind<01:25:50.219> of<01:25:50.340> re-architect 01:25:50.750 --> 01:25:50.760 align:start position:0% to make like that kind of re-architect 01:25:50.760 --> 01:25:52.729 align:start position:0% to make like that kind of re-architect thing<01:25:51.060> again<01:25:51.239> right<01:25:51.540> so<01:25:51.780> I<01:25:51.900> think<01:25:52.080> there's<01:25:52.440> uh 01:25:52.729 --> 01:25:52.739 align:start position:0% thing again right so I think there's uh 01:25:52.739 --> 01:25:55.490 align:start position:0% thing again right so I think there's uh you<01:25:53.340> know<01:25:53.460> there's<01:25:53.880> also<01:25:54.239> a<01:25:54.360> value<01:25:54.540> in<01:25:55.080> trying 01:25:55.490 --> 01:25:55.500 align:start position:0% you know there's also a value in trying 01:25:55.500 --> 01:25:58.070 align:start position:0% you know there's also a value in trying to<01:25:55.679> like<01:25:56.400> get<01:25:57.060> that<01:25:57.239> phase<01:25:57.480> done<01:25:57.719> earlier 01:25:58.070 --> 01:25:58.080 align:start position:0% to like get that phase done earlier 01:25:58.080 --> 01:25:59.570 align:start position:0% to like get that phase done earlier because<01:25:58.320> you<01:25:58.560> know<01:25:58.679> the<01:25:58.800> earlier<01:25:59.100> they<01:25:59.340> yeah 01:25:59.570 --> 01:25:59.580 align:start position:0% because you know the earlier they yeah 01:25:59.580 --> 01:26:01.910 align:start position:0% because you know the earlier they yeah they<01:26:00.060> can<01:26:00.179> do<01:26:00.360> those<01:26:00.719> uh<01:26:00.960> those<01:26:01.620> kinds<01:26:01.860> of 01:26:01.910 --> 01:26:01.920 align:start position:0% they can do those uh those kinds of 01:26:01.920 --> 01:26:03.709 align:start position:0% they can do those uh those kinds of changes<01:26:02.280> that<01:26:02.580> you<01:26:02.820> know<01:26:02.880> the<01:26:03.300> more<01:26:03.420> they<01:26:03.600> can 01:26:03.709 --> 01:26:03.719 align:start position:0% changes that you know the more they can 01:26:03.719 --> 01:26:05.450 align:start position:0% changes that you know the more they can get<01:26:03.840> to<01:26:03.960> the<01:26:04.139> phase<01:26:04.260> where<01:26:04.500> like<01:26:04.800> you<01:26:05.400> know 01:26:05.450 --> 01:26:05.460 align:start position:0% get to the phase where like you know 01:26:05.460 --> 01:26:07.490 align:start position:0% get to the phase where like you know they<01:26:06.060> can<01:26:06.239> start<01:26:06.480> clearing<01:26:06.900> instead<01:26:07.260> of<01:26:07.320> they 01:26:07.490 --> 01:26:07.500 align:start position:0% they can start clearing instead of they 01:26:07.500 --> 01:26:08.750 align:start position:0% they can start clearing instead of they have<01:26:07.679> to<01:26:07.800> know<01:26:07.980> that<01:26:08.159> like<01:26:08.340> they<01:26:08.580> have<01:26:08.639> to 01:26:08.750 --> 01:26:08.760 align:start position:0% have to know that like they have to 01:26:08.760 --> 01:26:11.689 align:start position:0% have to know that like they have to clear<01:26:08.880> eventually<01:26:09.300> let's<01:26:09.659> just<01:26:09.900> it's<01:26:10.860> so 01:26:11.689 --> 01:26:11.699 align:start position:0% clear eventually let's just it's so 01:26:11.699 --> 01:26:13.370 align:start position:0% clear eventually let's just it's so worth<01:26:11.940> talking<01:26:12.239> to<01:26:12.420> layer<01:26:12.780> two<01:26:12.900> teams<01:26:13.199> about 01:26:13.370 --> 01:26:13.380 align:start position:0% worth talking to layer two teams about 01:26:13.380 --> 01:26:14.450 align:start position:0% worth talking to layer two teams about that<01:26:13.560> too<01:26:13.679> I<01:26:13.860> mean<01:26:13.920> I'm<01:26:14.040> sure<01:26:14.159> they'll<01:26:14.280> have 01:26:14.450 --> 01:26:14.460 align:start position:0% that too I mean I'm sure they'll have 01:26:14.460 --> 01:26:16.550 align:start position:0% that too I mean I'm sure they'll have their<01:26:14.580> own<01:26:14.760> perspectives 01:26:16.550 --> 01:26:16.560 align:start position:0% their own perspectives 01:26:16.560 --> 01:26:19.490 align:start position:0% their own perspectives so<01:26:17.100> I<01:26:17.400> guess<01:26:17.520> we<01:26:18.000> various<01:26:18.719> kind<01:26:18.900> of<01:26:19.020> consensus 01:26:19.490 --> 01:26:19.500 align:start position:0% so I guess we various kind of consensus 01:26:19.500 --> 01:26:21.890 align:start position:0% so I guess we various kind of consensus that<01:26:19.739> we<01:26:19.980> want<01:26:20.159> for<01:26:20.460> 844<01:26:21.000> and<01:26:21.179> withdrawals 01:26:21.890 --> 01:26:21.900 align:start position:0% that we want for 844 and withdrawals 01:26:21.900 --> 01:26:24.050 align:start position:0% that we want for 844 and withdrawals within<01:26:22.320> the<01:26:22.500> next<01:26:22.679> nine<01:26:23.219> months<01:26:23.520> is<01:26:23.639> let's<01:26:23.820> say 01:26:24.050 --> 01:26:24.060 align:start position:0% within the next nine months is let's say 01:26:24.060 --> 01:26:27.590 align:start position:0% within the next nine months is let's say so<01:26:24.480> the<01:26:24.780> question<01:26:24.960> becomes<01:26:25.500> both<01:26:26.040> together<01:26:26.340> or 01:26:27.590 --> 01:26:27.600 align:start position:0% so the question becomes both together or 01:26:27.600 --> 01:26:30.770 align:start position:0% so the question becomes both together or uh<01:26:28.199> withdrawal<01:26:28.800> first<01:26:28.980> and<01:26:29.400> then<01:26:29.580> fight<01:26:29.880> over 01:26:30.770 --> 01:26:30.780 align:start position:0% uh withdrawal first and then fight over 01:26:30.780 --> 01:26:35.030 align:start position:0% uh withdrawal first and then fight over and<01:26:31.440> so<01:26:32.000> planning<01:26:33.000> team<01:26:33.179> I<01:26:34.139> I<01:26:34.440> will<01:26:34.620> say<01:26:34.739> one<01:26:34.920> of 01:26:35.030 --> 01:26:35.040 align:start position:0% and so planning team I I will say one of 01:26:35.040 --> 01:26:36.590 align:start position:0% and so planning team I I will say one of the<01:26:35.100> added<01:26:35.400> challenges<01:26:35.760> that<01:26:36.000> the<01:26:36.179> specs<01:26:36.480> for 01:26:36.590 --> 01:26:36.600 align:start position:0% the added challenges that the specs for 01:26:36.600 --> 01:26:39.950 align:start position:0% the added challenges that the specs for 4844<01:26:37.320> and<01:26:37.560> capella<01:26:38.100> are<01:26:38.219> not<01:26:38.400> unified<01:26:38.820> so<01:26:39.540> like 01:26:39.950 --> 01:26:39.960 align:start position:0% 4844 and capella are not unified so like 01:26:39.960 --> 01:26:42.169 align:start position:0% 4844 and capella are not unified so like he's<01:26:40.560> working<01:26:40.800> on<01:26:41.040> 4844<01:26:41.520> I'm<01:26:41.820> working<01:26:42.000> on 01:26:42.169 --> 01:26:42.179 align:start position:0% he's working on 4844 I'm working on 01:26:42.179 --> 01:26:44.689 align:start position:0% he's working on 4844 I'm working on capella<01:26:42.719> and<01:26:43.139> that's<01:26:43.560> gonna<01:26:44.040> be<01:26:44.280> a<01:26:44.400> hell<01:26:44.460> of<01:26:44.580> a 01:26:44.689 --> 01:26:44.699 align:start position:0% capella and that's gonna be a hell of a 01:26:44.699 --> 01:26:47.030 align:start position:0% capella and that's gonna be a hell of a pull<01:26:44.820> request<01:26:45.179> to<01:26:46.139> try<01:26:46.260> to<01:26:46.380> merge<01:26:46.739> these 01:26:47.030 --> 01:26:47.040 align:start position:0% pull request to try to merge these 01:26:47.040 --> 01:26:48.770 align:start position:0% pull request to try to merge these things<01:26:47.159> and<01:26:47.699> test<01:26:47.940> them 01:26:48.770 --> 01:26:48.780 align:start position:0% things and test them 01:26:48.780 --> 01:26:50.450 align:start position:0% things and test them so<01:26:49.500> they're<01:26:49.620> kind<01:26:49.800> of<01:26:49.920> already<01:26:50.040> written<01:26:50.280> like 01:26:50.450 --> 01:26:50.460 align:start position:0% so they're kind of already written like 01:26:50.460 --> 01:26:51.530 align:start position:0% so they're kind of already written like they're<01:26:50.639> separate 01:26:51.530 --> 01:26:51.540 align:start position:0% they're separate 01:26:51.540 --> 01:26:52.750 align:start position:0% they're separate just 01:26:52.750 --> 01:26:52.760 align:start position:0% just 01:26:52.760 --> 01:26:56.090 align:start position:0% just sure<01:26:54.120> so<01:26:54.840> one<01:26:55.199> thing<01:26:55.320> I<01:26:55.500> would<01:26:55.679> add<01:26:55.860> with 01:26:56.090 --> 01:26:56.100 align:start position:0% sure so one thing I would add with 01:26:56.100 --> 01:26:58.610 align:start position:0% sure so one thing I would add with regard<01:26:56.460> to<01:26:56.639> hard<01:26:56.940> Forks<01:26:57.360> one<01:26:57.480> versus<01:26:57.600> two<01:26:57.900> is 01:26:58.610 --> 01:26:58.620 align:start position:0% regard to hard Forks one versus two is 01:26:58.620 --> 01:27:00.430 align:start position:0% regard to hard Forks one versus two is that<01:26:58.800> you<01:26:58.980> generally<01:26:59.219> with<01:26:59.400> the<01:26:59.580> hard<01:26:59.699> Forks 01:27:00.430 --> 01:27:00.440 align:start position:0% that you generally with the hard Forks 01:27:00.440 --> 01:27:03.350 align:start position:0% that you generally with the hard Forks implementing<01:27:01.440> something<01:27:01.980> takes<01:27:02.820> usually 01:27:03.350 --> 01:27:03.360 align:start position:0% implementing something takes usually 01:27:03.360 --> 01:27:05.450 align:start position:0% implementing something takes usually less<01:27:03.600> time<01:27:03.840> than<01:27:04.080> rolling<01:27:04.560> it<01:27:04.679> out 01:27:05.450 --> 01:27:05.460 align:start position:0% less time than rolling it out 01:27:05.460 --> 01:27:08.689 align:start position:0% less time than rolling it out so<01:27:06.239> uh<01:27:06.659> implementing<01:27:07.620> both<01:27:07.800> withdrawals<01:27:08.460> and 01:27:08.689 --> 01:27:08.699 align:start position:0% so uh implementing both withdrawals and 01:27:08.699 --> 01:27:10.729 align:start position:0% so uh implementing both withdrawals and 4844<01:27:09.420> in<01:27:09.659> the<01:27:09.840> same<01:27:09.900> artwork<01:27:10.320> definitely 01:27:10.729 --> 01:27:10.739 align:start position:0% 4844 in the same artwork definitely 01:27:10.739 --> 01:27:13.310 align:start position:0% 4844 in the same artwork definitely makes<01:27:11.460> it<01:27:11.639> longer<01:27:12.060> but<01:27:12.360> I<01:27:12.540> think<01:27:12.659> overall<01:27:13.139> it 01:27:13.310 --> 01:27:13.320 align:start position:0% makes it longer but I think overall it 01:27:13.320 --> 01:27:14.990 align:start position:0% makes it longer but I think overall it would<01:27:13.560> still<01:27:13.860> be<01:27:14.040> shorter<01:27:14.400> than<01:27:14.580> doing<01:27:14.760> two 01:27:14.990 --> 01:27:15.000 align:start position:0% would still be shorter than doing two 01:27:15.000 --> 01:27:19.070 align:start position:0% would still be shorter than doing two hard<01:27:15.179> works<01:27:15.600> because<01:27:16.080> you<01:27:16.500> have<01:27:16.679> a 01:27:19.070 --> 01:27:19.080 align:start position:0% 01:27:19.080 --> 01:27:21.850 align:start position:0% um yeah 01:27:21.850 --> 01:27:21.860 align:start position:0% 01:27:21.860 --> 01:27:26.209 align:start position:0% sorry<01:27:22.860> so 01:27:26.209 --> 01:27:26.219 align:start position:0% 01:27:26.219 --> 01:27:29.209 align:start position:0% so<01:27:26.639> essentially<01:27:27.440> I<01:27:28.440> think<01:27:28.500> rolling<01:27:28.980> out<01:27:29.100> the 01:27:29.209 --> 01:27:29.219 align:start position:0% so essentially I think rolling out the 01:27:29.219 --> 01:27:30.950 align:start position:0% so essentially I think rolling out the hard<01:27:29.400> work<01:27:29.580> always<01:27:29.940> takes<01:27:30.300> two<01:27:30.600> to<01:27:30.780> three 01:27:30.950 --> 01:27:30.960 align:start position:0% hard work always takes two to three 01:27:30.960 --> 01:27:33.530 align:start position:0% hard work always takes two to three months<01:27:31.260> of<01:27:31.440> just<01:27:31.739> while<01:27:32.219> every<01:27:33.060> client<01:27:33.360> is 01:27:33.530 --> 01:27:33.540 align:start position:0% months of just while every client is 01:27:33.540 --> 01:27:35.870 align:start position:0% months of just while every client is yeah<01:27:33.780> I'm<01:27:33.960> not<01:27:34.199> done<01:27:34.500> yet<01:27:34.800> let's<01:27:35.219> test<01:27:35.580> it 01:27:35.870 --> 01:27:35.880 align:start position:0% yeah I'm not done yet let's test it 01:27:35.880 --> 01:27:38.450 align:start position:0% yeah I'm not done yet let's test it tests<01:27:36.300> are<01:27:36.360> not<01:27:36.540> done<01:27:36.780> yet<01:27:37.020> okay<01:27:37.320> let's<01:27:37.679> do<01:27:38.219> a 01:27:38.450 --> 01:27:38.460 align:start position:0% tests are not done yet okay let's do a 01:27:38.460 --> 01:27:40.910 align:start position:0% tests are not done yet okay let's do a hard<01:27:39.239> work<01:27:39.480> this<01:27:39.840> that's<01:27:40.020> not<01:27:40.320> hard<01:27:40.500> Fork 01:27:40.910 --> 01:27:40.920 align:start position:0% hard work this that's not hard Fork 01:27:40.920 --> 01:27:43.370 align:start position:0% hard work this that's not hard Fork that's<01:27:41.159> that<01:27:41.340> that<01:27:41.639> that's<01:27:41.880> not<01:27:42.060> so<01:27:42.300> we<01:27:43.199> kind 01:27:43.370 --> 01:27:43.380 align:start position:0% that's that that that's not so we kind 01:27:43.380 --> 01:27:45.890 align:start position:0% that's that that that's not so we kind of<01:27:43.980> I<01:27:44.580> don't<01:27:44.760> necessarily<01:27:45.360> want<01:27:45.480> to<01:27:45.600> say<01:27:45.719> we 01:27:45.890 --> 01:27:45.900 align:start position:0% of I don't necessarily want to say we 01:27:45.900 --> 01:27:48.290 align:start position:0% of I don't necessarily want to say we suck<01:27:46.080> at<01:27:46.260> rolling<01:27:46.620> out<01:27:46.739> things<01:27:46.980> but<01:27:47.699> we<01:27:48.060> don't 01:27:48.290 --> 01:27:48.300 align:start position:0% suck at rolling out things but we don't 01:27:48.300 --> 01:27:50.990 align:start position:0% suck at rolling out things but we don't really<01:27:48.600> push<01:27:48.960> very<01:27:49.260> hard<01:27:49.560> so<01:27:50.520> if<01:27:50.639> we<01:27:50.760> want<01:27:50.940> to 01:27:50.990 --> 01:27:51.000 align:start position:0% really push very hard so if we want to 01:27:51.000 --> 01:27:52.610 align:start position:0% really push very hard so if we want to roll<01:27:51.179> out<01:27:51.360> two<01:27:51.540> hard<01:27:51.719> Forks<01:27:52.139> then<01:27:52.260> you<01:27:52.500> have 01:27:52.610 --> 01:27:52.620 align:start position:0% roll out two hard Forks then you have 01:27:52.620 --> 01:27:55.370 align:start position:0% roll out two hard Forks then you have this<01:27:52.860> boilerplate<01:27:53.580> time<01:27:53.880> that<01:27:54.300> will<01:27:54.659> eat<01:27:55.139> up 01:27:55.370 --> 01:27:55.380 align:start position:0% this boilerplate time that will eat up 01:27:55.380 --> 01:27:57.770 align:start position:0% this boilerplate time that will eat up both<01:27:55.620> up<01:27:55.800> from<01:27:56.100> both<01:27:56.219> of<01:27:56.400> them<01:27:56.580> so<01:27:57.420> that's<01:27:57.540> the 01:27:57.770 --> 01:27:57.780 align:start position:0% both up from both of them so that's the 01:27:57.780 --> 01:27:58.790 align:start position:0% both up from both of them so that's the extra 01:27:58.790 --> 01:27:58.800 align:start position:0% extra 01:27:58.800 --> 01:28:01.129 align:start position:0% extra I<01:27:59.280> I<01:27:59.520> just<01:27:59.760> want<01:27:59.880> to<01:28:00.000> chime<01:28:00.239> in<01:28:00.360> on<01:28:00.540> dunkrat's 01:28:01.129 --> 01:28:01.139 align:start position:0% I I just want to chime in on dunkrat's 01:28:01.139 --> 01:28:02.629 align:start position:0% I I just want to chime in on dunkrat's point<01:28:01.320> from<01:28:01.620> the<01:28:01.800> coinbase<01:28:02.280> perspective 01:28:02.629 --> 01:28:02.639 align:start position:0% point from the coinbase perspective 01:28:02.639 --> 01:28:04.070 align:start position:0% point from the coinbase perspective that's<01:28:02.820> what<01:28:03.000> I<01:28:03.120> represent<01:28:03.420> and<01:28:03.659> I<01:28:03.840> know<01:28:03.960> that 01:28:04.070 --> 01:28:04.080 align:start position:0% that's what I represent and I know that 01:28:04.080 --> 01:28:05.990 align:start position:0% that's what I represent and I know that we're<01:28:04.320> still<01:28:04.500> here<01:28:04.739> kind<01:28:05.040> of<01:28:05.159> building<01:28:05.400> trust 01:28:05.990 --> 01:28:06.000 align:start position:0% we're still here kind of building trust 01:28:06.000 --> 01:28:08.450 align:start position:0% we're still here kind of building trust you<01:28:06.780> know<01:28:06.900> convincing<01:28:07.260> it<01:28:07.440> like<01:28:07.800> I<01:28:07.980> get<01:28:08.100> it<01:28:08.219> I 01:28:08.450 --> 01:28:08.460 align:start position:0% you know convincing it like I get it I 01:28:08.460 --> 01:28:09.709 align:start position:0% you know convincing it like I get it I get<01:28:08.520> it<01:28:08.699> like<01:28:08.940> it's<01:28:09.179> the<01:28:09.300> first<01:28:09.420> time<01:28:09.540> you've 01:28:09.709 --> 01:28:09.719 align:start position:0% get it like it's the first time you've 01:28:09.719 --> 01:28:11.090 align:start position:0% get it like it's the first time you've had<01:28:09.840> me<01:28:09.960> in<01:28:10.139> this<01:28:10.260> room 01:28:11.090 --> 01:28:11.100 align:start position:0% had me in this room 01:28:11.100 --> 01:28:12.350 align:start position:0% had me in this room um<01:28:11.159> but<01:28:11.400> you<01:28:11.580> know<01:28:11.699> we've<01:28:11.760> been<01:28:11.940> we've<01:28:12.179> been 01:28:12.350 --> 01:28:12.360 align:start position:0% um but you know we've been we've been 01:28:12.360 --> 01:28:13.729 align:start position:0% um but you know we've been we've been working<01:28:12.480> with<01:28:12.719> Proto<01:28:13.139> for<01:28:13.320> the<01:28:13.440> last<01:28:13.560> five 01:28:13.729 --> 01:28:13.739 align:start position:0% working with Proto for the last five 01:28:13.739 --> 01:28:15.830 align:start position:0% working with Proto for the last five months<01:28:14.040> on<01:28:14.219> eip4844<01:28:15.179> implementing<01:28:15.780> an 01:28:15.830 --> 01:28:15.840 align:start position:0% months on eip4844 implementing an 01:28:15.840 --> 01:28:19.010 align:start position:0% months on eip4844 implementing an imprisonment<01:28:16.199> spec<01:28:16.560> uh<01:28:17.219> prism<01:28:17.460> in<01:28:17.760> Geth<01:28:18.060> and<01:28:18.840> I 01:28:19.010 --> 01:28:19.020 align:start position:0% imprisonment spec uh prism in Geth and I 01:28:19.020 --> 01:28:20.870 align:start position:0% imprisonment spec uh prism in Geth and I think<01:28:19.139> to<01:28:19.560> doncrat's<01:28:20.219> point<01:28:20.400> the<01:28:20.699> difference 01:28:20.870 --> 01:28:20.880 align:start position:0% think to doncrat's point the difference 01:28:20.880 --> 01:28:23.390 align:start position:0% think to doncrat's point the difference between<01:28:21.360> like<01:28:22.020> each<01:28:22.440> one<01:28:22.679> of<01:28:22.800> next<01:28:23.040> year<01:28:23.219> and 01:28:23.390 --> 01:28:23.400 align:start position:0% between like each one of next year and 01:28:23.400 --> 01:28:25.610 align:start position:0% between like each one of next year and 2024<01:28:24.000> for<01:28:24.300> a<01:28:24.480> business<01:28:24.600> like<01:28:24.900> coinbase<01:28:25.440> is 01:28:25.610 --> 01:28:25.620 align:start position:0% 2024 for a business like coinbase is 01:28:25.620 --> 01:28:27.229 align:start position:0% 2024 for a business like coinbase is massive<01:28:26.040> and<01:28:26.340> I<01:28:26.520> think<01:28:26.580> the<01:28:26.699> way<01:28:26.820> that<01:28:27.000> shows 01:28:27.229 --> 01:28:27.239 align:start position:0% massive and I think the way that shows 01:28:27.239 --> 01:28:29.810 align:start position:0% massive and I think the way that shows up<01:28:27.360> is<01:28:27.540> we<01:28:27.719> have<01:28:27.960> products<01:28:28.560> that<01:28:29.159> we've<01:28:29.460> built 01:28:29.810 --> 01:28:29.820 align:start position:0% up is we have products that we've built 01:28:29.820 --> 01:28:32.090 align:start position:0% up is we have products that we've built on<01:28:30.179> chain<01:28:30.480> smart<01:28:30.900> contracts<01:28:31.380> that<01:28:31.560> we<01:28:31.800> want<01:28:31.920> to 01:28:32.090 --> 01:28:32.100 align:start position:0% on chain smart contracts that we want to 01:28:32.100 --> 01:28:33.770 align:start position:0% on chain smart contracts that we want to be<01:28:32.219> launching<01:28:32.639> like<01:28:33.060> literally<01:28:33.360> we<01:28:33.600> want<01:28:33.659> to 01:28:33.770 --> 01:28:33.780 align:start position:0% be launching like literally we want to 01:28:33.780 --> 01:28:35.990 align:start position:0% be launching like literally we want to be<01:28:33.900> launching<01:28:34.199> in<01:28:34.320> Q4<01:28:34.739> in<01:28:35.219> q1<01:28:35.520> of<01:28:35.699> next<01:28:35.880> year 01:28:35.990 --> 01:28:36.000 align:start position:0% be launching in Q4 in q1 of next year 01:28:36.000 --> 01:28:37.790 align:start position:0% be launching in Q4 in q1 of next year and<01:28:36.120> we<01:28:36.300> can't<01:28:36.420> right<01:28:36.659> now<01:28:36.840> and<01:28:37.500> that<01:28:37.620> is 01:28:37.790 --> 01:28:37.800 align:start position:0% and we can't right now and that is 01:28:37.800 --> 01:28:39.050 align:start position:0% and we can't right now and that is because<01:28:37.920> at<01:28:38.340> the<01:28:38.460> scale<01:28:38.699> that<01:28:38.880> we're 01:28:39.050 --> 01:28:39.060 align:start position:0% because at the scale that we're 01:28:39.060 --> 01:28:40.370 align:start position:0% because at the scale that we're operating<01:28:39.360> at<01:28:39.540> where<01:28:39.780> we're<01:28:39.960> talking<01:28:40.139> about 01:28:40.370 --> 01:28:40.380 align:start position:0% operating at where we're talking about 01:28:40.380 --> 01:28:41.930 align:start position:0% operating at where we're talking about bringing<01:28:40.800> millions<01:28:41.159> or<01:28:41.280> tens<01:28:41.520> of<01:28:41.639> millions 01:28:41.930 --> 01:28:41.940 align:start position:0% bringing millions or tens of millions 01:28:41.940 --> 01:28:44.030 align:start position:0% bringing millions or tens of millions customers<01:28:42.420> into<01:28:43.020> those<01:28:43.320> contracts<01:28:43.739> in<01:28:43.920> our 01:28:44.030 --> 01:28:44.040 align:start position:0% customers into those contracts in our 01:28:44.040 --> 01:28:45.709 align:start position:0% customers into those contracts in our wallet<01:28:44.340> products<01:28:44.580> fully<01:28:45.000> non-custodially 01:28:45.709 --> 01:28:45.719 align:start position:0% wallet products fully non-custodially 01:28:45.719 --> 01:28:48.290 align:start position:0% wallet products fully non-custodially it's<01:28:46.380> just<01:28:46.560> too<01:28:46.739> too<01:28:47.040> expensive<01:28:47.520> most<01:28:48.060> of<01:28:48.239> our 01:28:48.290 --> 01:28:48.300 align:start position:0% it's just too too expensive most of our 01:28:48.300 --> 01:28:49.610 align:start position:0% it's just too too expensive most of our customers<01:28:48.600> who<01:28:48.780> are<01:28:48.900> not<01:28:49.020> in<01:28:49.139> the<01:28:49.199> US<01:28:49.320> can't 01:28:49.610 --> 01:28:49.620 align:start position:0% customers who are not in the US can't 01:28:49.620 --> 01:28:51.229 align:start position:0% customers who are not in the US can't pay<01:28:49.860> for<01:28:50.040> it<01:28:50.159> and<01:28:50.580> we<01:28:50.760> as<01:28:50.940> a<01:28:51.120> business 01:28:51.229 --> 01:28:51.239 align:start position:0% pay for it and we as a business 01:28:51.239 --> 01:28:52.790 align:start position:0% pay for it and we as a business especially<01:28:51.719> in<01:28:51.900> the<01:28:52.020> bear<01:28:52.080> Market<01:28:52.320> can't 01:28:52.790 --> 01:28:52.800 align:start position:0% especially in the bear Market can't 01:28:52.800 --> 01:28:54.950 align:start position:0% especially in the bear Market can't subsidize<01:28:53.400> the<01:28:53.639> cost<01:28:53.760> for<01:28:54.060> them<01:28:54.239> and<01:28:54.659> so<01:28:54.780> what 01:28:54.950 --> 01:28:54.960 align:start position:0% subsidize the cost for them and so what 01:28:54.960 --> 01:28:57.169 align:start position:0% subsidize the cost for them and so what that<01:28:55.080> means<01:28:55.380> is<01:28:55.560> that<01:28:55.800> in<01:28:56.580> the<01:28:56.699> context<01:28:57.000> of 01:28:57.169 --> 01:28:57.179 align:start position:0% that means is that in the context of 01:28:57.179 --> 01:28:58.610 align:start position:0% that means is that in the context of these<01:28:57.360> conversations<01:28:57.840> the<01:28:58.260> people<01:28:58.380> who<01:28:58.500> may 01:28:58.610 --> 01:28:58.620 align:start position:0% these conversations the people who may 01:28:58.620 --> 01:28:59.990 align:start position:0% these conversations the people who may be<01:28:58.739> don't<01:28:59.159> understand<01:28:59.340> the<01:28:59.760> technology 01:28:59.990 --> 01:29:00.000 align:start position:0% be don't understand the technology 01:29:00.000 --> 01:29:01.790 align:start position:0% be don't understand the technology benefits<01:29:00.540> of<01:29:00.719> decentralization<01:29:01.260> or<01:29:01.620> security 01:29:01.790 --> 01:29:01.800 align:start position:0% benefits of decentralization or security 01:29:01.800 --> 01:29:03.830 align:start position:0% benefits of decentralization or security they<01:29:02.219> then<01:29:02.400> go<01:29:02.580> and<01:29:02.760> say<01:29:02.940> hey<01:29:03.120> there's<01:29:03.719> all 01:29:03.830 --> 01:29:03.840 align:start position:0% they then go and say hey there's all 01:29:03.840 --> 01:29:07.070 align:start position:0% they then go and say hey there's all these<01:29:04.020> other<01:29:04.139> evm<01:29:04.679> chains<01:29:05.219> they<01:29:05.760> have<01:29:06.060> sub<01:29:06.840> one 01:29:07.070 --> 01:29:07.080 align:start position:0% these other evm chains they have sub one 01:29:07.080 --> 01:29:08.990 align:start position:0% these other evm chains they have sub one cent<01:29:07.320> fees<01:29:07.800> can<01:29:08.040> we<01:29:08.159> just<01:29:08.280> deploy<01:29:08.639> this<01:29:08.820> thing 01:29:08.990 --> 01:29:09.000 align:start position:0% cent fees can we just deploy this thing 01:29:09.000 --> 01:29:11.510 align:start position:0% cent fees can we just deploy this thing on<01:29:09.239> that<01:29:09.420> like<01:29:10.139> would<01:29:10.440> that<01:29:10.620> be<01:29:10.739> a<01:29:10.920> faster<01:29:11.100> can 01:29:11.510 --> 01:29:11.520 align:start position:0% on that like would that be a faster can 01:29:11.520 --> 01:29:13.070 align:start position:0% on that like would that be a faster can get<01:29:11.760> can<01:29:12.000> that<01:29:12.239> get<01:29:12.360> this<01:29:12.540> thing<01:29:12.659> shipped<01:29:12.960> in 01:29:13.070 --> 01:29:13.080 align:start position:0% get can that get this thing shipped in 01:29:13.080 --> 01:29:16.490 align:start position:0% get can that get this thing shipped in q1<01:29:13.440> and<01:29:14.219> it's<01:29:14.400> up<01:29:14.580> to<01:29:14.760> the<01:29:15.179> people<01:29:15.380> like<01:29:16.380> me 01:29:16.490 --> 01:29:16.500 align:start position:0% q1 and it's up to the people like me 01:29:16.500 --> 01:29:18.169 align:start position:0% q1 and it's up to the people like me maybe<01:29:16.739> or<01:29:16.920> others<01:29:17.159> the<01:29:17.340> company<01:29:17.520> who<01:29:18.000> who 01:29:18.169 --> 01:29:18.179 align:start position:0% maybe or others the company who who 01:29:18.179 --> 01:29:19.550 align:start position:0% maybe or others the company who who understand<01:29:18.420> the<01:29:18.840> whole<01:29:18.960> process<01:29:19.199> and<01:29:19.380> why 01:29:19.550 --> 01:29:19.560 align:start position:0% understand the whole process and why 01:29:19.560 --> 01:29:20.810 align:start position:0% understand the whole process and why we're<01:29:19.679> doing<01:29:19.860> Roll-Ups<01:29:20.340> and<01:29:20.460> why<01:29:20.580> this<01:29:20.760> is 01:29:20.810 --> 01:29:20.820 align:start position:0% we're doing Roll-Ups and why this is 01:29:20.820 --> 01:29:22.129 align:start position:0% we're doing Roll-Ups and why this is such<01:29:21.000> an<01:29:21.120> important<01:29:21.360> investment<01:29:21.659> from<01:29:21.960> a 01:29:22.129 --> 01:29:22.139 align:start position:0% such an important investment from a 01:29:22.139 --> 01:29:23.629 align:start position:0% such an important investment from a decentralization<01:29:22.920> security<01:29:23.159> perspective 01:29:23.629 --> 01:29:23.639 align:start position:0% decentralization security perspective 01:29:23.639 --> 01:29:25.669 align:start position:0% decentralization security perspective say<01:29:23.880> no<01:29:24.120> like<01:29:24.540> we<01:29:24.719> need<01:29:24.840> to<01:29:24.960> wait<01:29:25.139> we<01:29:25.440> need<01:29:25.560> to 01:29:25.669 --> 01:29:25.679 align:start position:0% say no like we need to wait we need to 01:29:25.679 --> 01:29:27.590 align:start position:0% say no like we need to wait we need to wait<01:29:25.800> for<01:29:26.100> this<01:29:26.219> to<01:29:26.460> have<01:29:26.699> the<01:29:26.940> right<01:29:27.120> solution 01:29:27.590 --> 01:29:27.600 align:start position:0% wait for this to have the right solution 01:29:27.600 --> 01:29:29.810 align:start position:0% wait for this to have the right solution and<01:29:27.960> so<01:29:28.199> I<01:29:28.500> think<01:29:28.620> waiting<01:29:29.159> until<01:29:29.340> the 01:29:29.810 --> 01:29:29.820 align:start position:0% and so I think waiting until the 01:29:29.820 --> 01:29:31.370 align:start position:0% and so I think waiting until the beginning<01:29:30.060> of<01:29:30.300> next<01:29:30.540> year<01:29:30.719> you<01:29:31.080> know<01:29:31.199> first 01:29:31.370 --> 01:29:31.380 align:start position:0% beginning of next year you know first 01:29:31.380 --> 01:29:32.870 align:start position:0% beginning of next year you know first half<01:29:31.560> of<01:29:31.739> next<01:29:31.920> year<01:29:32.159> I<01:29:32.520> feel<01:29:32.639> like<01:29:32.760> that's 01:29:32.870 --> 01:29:32.880 align:start position:0% half of next year I feel like that's 01:29:32.880 --> 01:29:34.910 align:start position:0% half of next year I feel like that's like<01:29:33.120> a<01:29:33.239> thing<01:29:33.540> we<01:29:33.780> can<01:29:33.960> hold<01:29:34.260> we<01:29:34.500> can<01:29:34.620> make<01:29:34.800> it 01:29:34.910 --> 01:29:34.920 align:start position:0% like a thing we can hold we can make it 01:29:34.920 --> 01:29:37.970 align:start position:0% like a thing we can hold we can make it happen<01:29:35.159> waiting<01:29:35.940> until<01:29:36.060> 2024<01:29:36.780> is<01:29:37.500> really<01:29:37.800> hard 01:29:37.970 --> 01:29:37.980 align:start position:0% happen waiting until 2024 is really hard 01:29:37.980 --> 01:29:39.770 align:start position:0% happen waiting until 2024 is really hard that's<01:29:38.460> going<01:29:38.639> to<01:29:38.760> be<01:29:38.880> a<01:29:39.000> real<01:29:39.179> challenge<01:29:39.480> for 01:29:39.770 --> 01:29:39.780 align:start position:0% that's going to be a real challenge for 01:29:39.780 --> 01:29:41.990 align:start position:0% that's going to be a real challenge for us<01:29:39.900> and<01:29:40.080> so<01:29:40.260> I<01:29:40.620> think<01:29:40.739> I<01:29:41.100> think<01:29:41.219> from<01:29:42.000> from 01:29:41.990 --> 01:29:42.000 align:start position:0% us and so I think I think from from 01:29:42.000 --> 01:29:43.550 align:start position:0% us and so I think I think from from where<01:29:42.480> I<01:29:42.719> sit 01:29:43.550 --> 01:29:43.560 align:start position:0% where I sit 01:29:43.560 --> 01:29:45.229 align:start position:0% where I sit um<01:29:43.620> our<01:29:43.860> feeling<01:29:44.040> is<01:29:44.280> like<01:29:44.460> let's<01:29:44.760> make<01:29:45.000> the 01:29:45.229 --> 01:29:45.239 align:start position:0% um our feeling is like let's make the 01:29:45.239 --> 01:29:46.850 align:start position:0% um our feeling is like let's make the list<01:29:45.360> of<01:29:45.600> all<01:29:45.780> of<01:29:45.900> the<01:29:46.080> things<01:29:46.260> that<01:29:46.620> all<01:29:46.800> of 01:29:46.850 --> 01:29:46.860 align:start position:0% list of all of the things that all of 01:29:46.860 --> 01:29:48.590 align:start position:0% list of all of the things that all of the<01:29:46.980> people<01:29:47.159> in<01:29:47.280> this<01:29:47.460> room<01:29:47.580> feel<01:29:47.880> like<01:29:48.060> we 01:29:48.590 --> 01:29:48.600 align:start position:0% the people in this room feel like we 01:29:48.600 --> 01:29:50.390 align:start position:0% the people in this room feel like we need<01:29:48.780> in<01:29:49.020> order<01:29:49.139> to<01:29:49.260> feel<01:29:49.440> comfortable<01:29:49.800> and<01:29:50.280> if 01:29:50.390 --> 01:29:50.400 align:start position:0% need in order to feel comfortable and if 01:29:50.400 --> 01:29:51.709 align:start position:0% need in order to feel comfortable and if that's<01:29:50.580> better<01:29:50.820> monitoring<01:29:51.300> of<01:29:51.480> the<01:29:51.600> network 01:29:51.709 --> 01:29:51.719 align:start position:0% that's better monitoring of the network 01:29:51.719 --> 01:29:53.450 align:start position:0% that's better monitoring of the network so<01:29:52.020> we<01:29:52.139> can<01:29:52.199> understand<01:29:52.320> bandwidth<01:29:53.100> if<01:29:53.280> that's 01:29:53.450 --> 01:29:53.460 align:start position:0% so we can understand bandwidth if that's 01:29:53.460 --> 01:29:55.250 align:start position:0% so we can understand bandwidth if that's better<01:29:53.699> testing<01:29:54.179> so<01:29:54.420> we<01:29:54.600> can<01:29:54.719> feel<01:29:55.020> more 01:29:55.250 --> 01:29:55.260 align:start position:0% better testing so we can feel more 01:29:55.260 --> 01:29:56.270 align:start position:0% better testing so we can feel more confident<01:29:55.560> in<01:29:55.679> the<01:29:55.800> change<01:29:55.920> that<01:29:56.159> we're 01:29:56.270 --> 01:29:56.280 align:start position:0% confident in the change that we're 01:29:56.280 --> 01:29:59.209 align:start position:0% confident in the change that we're making<01:29:56.460> uh<01:29:57.300> whatever<01:29:57.600> it<01:29:57.900> is<01:29:58.020> like<01:29:58.320> give<01:29:58.679> us 01:29:59.209 --> 01:29:59.219 align:start position:0% making uh whatever it is like give us 01:29:59.219 --> 01:30:02.030 align:start position:0% making uh whatever it is like give us the<01:29:59.580> list<01:29:59.760> give<01:30:00.360> optimism<01:30:00.900> the<01:30:01.139> list<01:30:01.380> and 01:30:02.030 --> 01:30:02.040 align:start position:0% the list give optimism the list and 01:30:02.040 --> 01:30:03.830 align:start position:0% the list give optimism the list and we're<01:30:02.159> ready<01:30:02.400> to<01:30:02.639> throw<01:30:02.820> resources<01:30:03.420> at<01:30:03.659> this 01:30:03.830 --> 01:30:03.840 align:start position:0% we're ready to throw resources at this 01:30:03.840 --> 01:30:06.290 align:start position:0% we're ready to throw resources at this and<01:30:04.080> support<01:30:04.320> this<01:30:04.679> and<01:30:05.159> I<01:30:05.280> know<01:30:05.460> that<01:30:05.760> again 01:30:06.290 --> 01:30:06.300 align:start position:0% and support this and I know that again 01:30:06.300 --> 01:30:08.330 align:start position:0% and support this and I know that again we<01:30:06.659> have<01:30:06.719> a<01:30:06.840> lot<01:30:06.900> of<01:30:07.020> trust<01:30:07.260> to<01:30:07.380> build<01:30:07.560> that 01:30:08.330 --> 01:30:08.340 align:start position:0% we have a lot of trust to build that 01:30:08.340 --> 01:30:10.070 align:start position:0% we have a lot of trust to build that will<01:30:08.400> come<01:30:08.580> through<01:30:08.760> in<01:30:08.880> its<01:30:09.120> work<01:30:09.239> a<01:30:09.900> year 01:30:10.070 --> 01:30:10.080 align:start position:0% will come through in its work a year 01:30:10.080 --> 01:30:11.510 align:start position:0% will come through in its work a year from<01:30:10.260> now<01:30:10.380> I<01:30:10.500> hope<01:30:10.679> that<01:30:10.860> there's<01:30:11.100> a<01:30:11.280> lot<01:30:11.340> more 01:30:11.510 --> 01:30:11.520 align:start position:0% from now I hope that there's a lot more 01:30:11.520 --> 01:30:13.430 align:start position:0% from now I hope that there's a lot more trust<01:30:11.820> here<01:30:12.000> but<01:30:12.360> I<01:30:12.659> do<01:30:12.780> want<01:30:12.900> a<01:30:13.080> voice<01:30:13.199> like 01:30:13.430 --> 01:30:13.440 align:start position:0% trust here but I do want a voice like 01:30:13.440 --> 01:30:15.350 align:start position:0% trust here but I do want a voice like that's<01:30:13.679> the<01:30:13.920> impact<01:30:14.340> for<01:30:14.820> for<01:30:15.000> a<01:30:15.239> business 01:30:15.350 --> 01:30:15.360 align:start position:0% that's the impact for for a business 01:30:15.360 --> 01:30:17.689 align:start position:0% that's the impact for for a business like<01:30:15.659> us<01:30:15.900> and<01:30:16.500> we're<01:30:16.800> ready<01:30:16.980> to<01:30:17.280> come<01:30:17.400> to<01:30:17.580> the 01:30:17.689 --> 01:30:17.699 align:start position:0% like us and we're ready to come to the 01:30:17.699 --> 01:30:19.189 align:start position:0% like us and we're ready to come to the table<01:30:17.820> with<01:30:18.120> you<01:30:18.239> all<01:30:18.360> and<01:30:18.480> work<01:30:18.659> together<01:30:18.840> to 01:30:19.189 --> 01:30:19.199 align:start position:0% table with you all and work together to 01:30:19.199 --> 01:30:21.229 align:start position:0% table with you all and work together to figure<01:30:19.320> out<01:30:19.500> how<01:30:19.980> do<01:30:20.040> we<01:30:20.100> make<01:30:20.280> it<01:30:20.460> so<01:30:20.639> the<01:30:21.120> end 01:30:21.229 --> 01:30:21.239 align:start position:0% figure out how do we make it so the end 01:30:21.239 --> 01:30:23.629 align:start position:0% figure out how do we make it so the end result<01:30:21.480> is<01:30:22.199> tens<01:30:22.679> of<01:30:22.860> millions<01:30:23.100> or<01:30:23.280> hundreds 01:30:23.629 --> 01:30:23.639 align:start position:0% result is tens of millions or hundreds 01:30:23.639 --> 01:30:25.189 align:start position:0% result is tens of millions or hundreds of<01:30:23.760> millions<01:30:24.000> of<01:30:24.120> more<01:30:24.239> users<01:30:24.600> are<01:30:24.780> using 01:30:25.189 --> 01:30:25.199 align:start position:0% of millions of more users are using 01:30:25.199 --> 01:30:26.990 align:start position:0% of millions of more users are using ethereum<01:30:25.920> by<01:30:26.219> the<01:30:26.340> middle<01:30:26.460> of<01:30:26.639> the<01:30:26.699> end<01:30:26.880> of 01:30:26.990 --> 01:30:27.000 align:start position:0% ethereum by the middle of the end of 01:30:27.000 --> 01:30:28.910 align:start position:0% ethereum by the middle of the end of next<01:30:27.179> year 01:30:28.910 --> 01:30:28.920 align:start position:0% next year 01:30:28.920 --> 01:30:30.169 align:start position:0% next year so 01:30:30.169 --> 01:30:30.179 align:start position:0% so 01:30:30.179 --> 01:30:31.160 align:start position:0% so excuse<01:30:30.719> me 01:30:31.160 --> 01:30:31.170 align:start position:0% excuse me 01:30:31.170 --> 01:30:33.890 align:start position:0% excuse me [Applause] 01:30:33.890 --> 01:30:33.900 align:start position:0% [Applause] 01:30:33.900 --> 01:30:36.830 align:start position:0% [Applause] I<01:30:34.560> I<01:30:34.739> have<01:30:34.980> I<01:30:35.280> have 01:30:36.830 --> 01:30:36.840 align:start position:0% I I have I have 01:30:36.840 --> 01:30:40.970 align:start position:0% I I have I have two<01:30:37.800> rebuttals<01:30:38.520> to<01:30:38.940> uh<01:30:39.300> to<01:30:39.840> to<01:30:39.840> putting<01:30:40.500> uh<01:30:40.800> for 01:30:40.970 --> 01:30:40.980 align:start position:0% two rebuttals to uh to to putting uh for 01:30:40.980 --> 01:30:43.490 align:start position:0% two rebuttals to uh to to putting uh for it<01:30:41.159> for<01:30:41.280> four<01:30:41.460> in<01:30:41.699> into<01:30:41.880> Shanghai 01:30:43.490 --> 01:30:43.500 align:start position:0% it for four in into Shanghai 01:30:43.500 --> 01:30:45.169 align:start position:0% it for four in into Shanghai um 01:30:45.169 --> 01:30:45.179 align:start position:0% um 01:30:45.179 --> 01:30:48.350 align:start position:0% um one<01:30:45.659> of<01:30:45.780> them<01:30:45.900> is<01:30:46.320> uh 01:30:48.350 --> 01:30:48.360 align:start position:0% one of them is uh 01:30:48.360 --> 01:30:51.590 align:start position:0% one of them is uh I<01:30:48.840> don't<01:30:48.960> I<01:30:49.380> don't<01:30:49.620> I<01:30:49.860> don't<01:30:50.219> see<01:30:50.820> any<01:30:51.000> Roll-Ups 01:30:51.590 --> 01:30:51.600 align:start position:0% I don't I don't I don't see any Roll-Ups 01:30:51.600 --> 01:30:54.169 align:start position:0% I don't I don't I don't see any Roll-Ups that<01:30:51.719> are<01:30:51.840> trustless<01:30:52.199> right<01:30:52.560> now<01:30:52.820> uh<01:30:53.820> most<01:30:54.000> of 01:30:54.169 --> 01:30:54.179 align:start position:0% that are trustless right now uh most of 01:30:54.179 --> 01:30:55.970 align:start position:0% that are trustless right now uh most of them<01:30:54.239> don't<01:30:54.540> implement<01:30:55.080> the<01:30:55.320> the<01:30:55.560> fraud 01:30:55.970 --> 01:30:55.980 align:start position:0% them don't implement the the fraud 01:30:55.980 --> 01:30:58.729 align:start position:0% them don't implement the the fraud proofs<01:30:56.340> uh<01:30:56.880> they're<01:30:57.120> putting<01:30:57.420> the<01:30:57.540> data 01:30:58.729 --> 01:30:58.739 align:start position:0% proofs uh they're putting the data 01:30:58.739 --> 01:31:00.950 align:start position:0% proofs uh they're putting the data on<01:30:59.219> chain<01:30:59.400> but<01:30:59.699> the<01:30:59.880> data<01:31:00.120> is<01:31:00.239> not<01:31:00.420> really<01:31:00.600> used 01:31:00.950 --> 01:31:00.960 align:start position:0% on chain but the data is not really used 01:31:00.960 --> 01:31:03.770 align:start position:0% on chain but the data is not really used for<01:31:01.320> anything<01:31:01.500> so<01:31:02.400> uh<01:31:02.880> like<01:31:03.179> you<01:31:03.360> cannot<01:31:03.600> use 01:31:03.770 --> 01:31:03.780 align:start position:0% for anything so uh like you cannot use 01:31:03.780 --> 01:31:06.470 align:start position:0% for anything so uh like you cannot use it<01:31:03.960> to<01:31:04.139> to<01:31:04.380> prove<01:31:04.860> that<01:31:05.100> the<01:31:05.340> that<01:31:05.820> the<01:31:06.120> that 01:31:06.470 --> 01:31:06.480 align:start position:0% it to to prove that the that the that 01:31:06.480 --> 01:31:07.790 align:start position:0% it to to prove that the that the that the<01:31:06.600> Roll<01:31:06.719> Up<01:31:06.960> is<01:31:07.139> wrong 01:31:07.790 --> 01:31:07.800 align:start position:0% the Roll Up is wrong 01:31:07.800 --> 01:31:12.649 align:start position:0% the Roll Up is wrong and<01:31:08.760> so<01:31:09.239> if<01:31:09.780> we<01:31:09.900> Implement<01:31:10.320> Bank<01:31:11.219> sharding 01:31:12.649 --> 01:31:12.659 align:start position:0% and so if we Implement Bank sharding 01:31:12.659 --> 01:31:15.350 align:start position:0% and so if we Implement Bank sharding we<01:31:13.320> basically<01:31:13.679> say<01:31:14.100> to<01:31:14.520> the<01:31:14.699> community<01:31:14.880> use 01:31:15.350 --> 01:31:15.360 align:start position:0% we basically say to the community use 01:31:15.360 --> 01:31:17.510 align:start position:0% we basically say to the community use these<01:31:15.600> Roll-Ups<01:31:16.139> but<01:31:16.739> the<01:31:16.860> Roll-Ups<01:31:17.340> are<01:31:17.400> not 01:31:17.510 --> 01:31:17.520 align:start position:0% these Roll-Ups but the Roll-Ups are not 01:31:17.520 --> 01:31:19.310 align:start position:0% these Roll-Ups but the Roll-Ups are not secure 01:31:19.310 --> 01:31:19.320 align:start position:0% secure 01:31:19.320 --> 01:31:20.270 align:start position:0% secure um 01:31:20.270 --> 01:31:20.280 align:start position:0% um 01:31:20.280 --> 01:31:23.930 align:start position:0% um I<01:31:20.820> think<01:31:20.940> that's<01:31:21.120> kind<01:31:21.420> of<01:31:21.480> a 01:31:23.930 --> 01:31:23.940 align:start position:0% 01:31:23.940 --> 01:31:26.629 align:start position:0% it's<01:31:24.120> a<01:31:24.300> minor<01:31:24.600> problem<01:31:24.840> it's<01:31:25.260> it's<01:31:25.560> uh<01:31:26.100> the 01:31:26.629 --> 01:31:26.639 align:start position:0% it's a minor problem it's it's uh the 01:31:26.639 --> 01:31:28.129 align:start position:0% it's a minor problem it's it's uh the other<01:31:26.760> thing 01:31:28.129 --> 01:31:28.139 align:start position:0% other thing 01:31:28.139 --> 01:31:31.729 align:start position:0% other thing the<01:31:28.620> bigger<01:31:28.920> problem<01:31:29.100> I<01:31:29.460> I<01:31:29.699> see<01:31:29.940> is<01:31:30.120> that<01:31:30.960> from 01:31:31.729 --> 01:31:31.739 align:start position:0% the bigger problem I I see is that from 01:31:31.739 --> 01:31:34.550 align:start position:0% the bigger problem I I see is that from yesterday's<01:31:32.280> conversation<01:31:33.080> just<01:31:34.080> doesn't 01:31:34.550 --> 01:31:34.560 align:start position:0% yesterday's conversation just doesn't 01:31:34.560 --> 01:31:38.629 align:start position:0% yesterday's conversation just doesn't seem<01:31:35.219> ready<01:31:35.820> yet<01:31:36.120> so<01:31:36.900> withdrawals 01:31:38.629 --> 01:31:38.639 align:start position:0% seem ready yet so withdrawals 01:31:38.639 --> 01:31:41.870 align:start position:0% seem ready yet so withdrawals the<01:31:39.360> way<01:31:39.540> I<01:31:39.840> see<01:31:40.080> it<01:31:40.260> are<01:31:41.159> basically<01:31:41.520> done 01:31:41.870 --> 01:31:41.880 align:start position:0% the way I see it are basically done 01:31:41.880 --> 01:31:45.229 align:start position:0% the way I see it are basically done they're<01:31:42.840> like<01:31:43.320> they<01:31:43.860> are<01:31:43.980> implemented<01:31:44.639> in 01:31:45.229 --> 01:31:45.239 align:start position:0% they're like they are implemented in 01:31:45.239 --> 01:31:47.750 align:start position:0% they're like they are implemented in some<01:31:45.480> of<01:31:45.600> the<01:31:45.719> clients<01:31:46.139> already 01:31:47.750 --> 01:31:47.760 align:start position:0% some of the clients already 01:31:47.760 --> 01:31:49.750 align:start position:0% some of the clients already um<01:31:47.820> the<01:31:48.060> specs<01:31:48.480> seems<01:31:48.659> to<01:31:48.780> be<01:31:48.900> pretty<01:31:49.139> stable 01:31:49.750 --> 01:31:49.760 align:start position:0% um the specs seems to be pretty stable 01:31:49.760 --> 01:31:53.209 align:start position:0% um the specs seems to be pretty stable and<01:31:50.760> with<01:31:51.239> Deng<01:31:51.780> sharding<01:31:52.080> we<01:31:52.260> recently<01:31:52.679> had<01:31:52.920> a 01:31:53.209 --> 01:31:53.219 align:start position:0% and with Deng sharding we recently had a 01:31:53.219 --> 01:31:57.110 align:start position:0% and with Deng sharding we recently had a new<01:31:53.340> fee<01:31:53.760> Market<01:31:54.020> change<01:31:55.020> that 01:31:57.110 --> 01:31:57.120 align:start position:0% new fee Market change that 01:31:57.120 --> 01:31:59.450 align:start position:0% new fee Market change that I<01:31:57.540> don't<01:31:57.659> know<01:31:57.780> how<01:31:58.020> much<01:31:58.199> thought<01:31:58.920> has<01:31:59.280> has 01:31:59.450 --> 01:31:59.460 align:start position:0% I don't know how much thought has has 01:31:59.460 --> 01:32:02.450 align:start position:0% I don't know how much thought has has been<01:31:59.699> put<01:31:59.880> into<01:32:00.060> it<01:32:00.659> from<01:32:01.620> from<01:32:01.620> my<01:32:02.100> point<01:32:02.280> of 01:32:02.450 --> 01:32:02.460 align:start position:0% been put into it from from my point of 01:32:02.460 --> 01:32:03.890 align:start position:0% been put into it from from my point of view<01:32:02.580> it 01:32:03.890 --> 01:32:03.900 align:start position:0% view it 01:32:03.900 --> 01:32:06.590 align:start position:0% view it it<01:32:03.960> like<01:32:04.800> the<01:32:05.280> the<01:32:05.400> fee<01:32:05.760> Market<01:32:05.820> change<01:32:06.120> at 01:32:06.590 --> 01:32:06.600 align:start position:0% it like the the fee Market change at 01:32:06.600 --> 01:32:08.649 align:start position:0% it like the the fee Market change at some<01:32:06.780> some<01:32:07.020> 1559 01:32:08.649 --> 01:32:08.659 align:start position:0% some some 1559 01:32:08.659 --> 01:32:12.649 align:start position:0% some some 1559 like<01:32:09.659> uh<01:32:10.560> thing<01:32:10.800> and<01:32:11.760> from<01:32:12.120> my<01:32:12.300> point<01:32:12.420> of<01:32:12.540> view 01:32:12.649 --> 01:32:12.659 align:start position:0% like uh thing and from my point of view 01:32:12.659 --> 01:32:16.310 align:start position:0% like uh thing and from my point of view it<01:32:12.900> looks<01:32:13.440> like<01:32:13.679> we<01:32:14.520> have<01:32:14.699> a<01:32:14.820> hammer<01:32:15.239> the<01:32:15.659> 1559 01:32:16.310 --> 01:32:16.320 align:start position:0% it looks like we have a hammer the 1559 01:32:16.320 --> 01:32:18.350 align:start position:0% it looks like we have a hammer the 1559 hammer<01:32:16.800> and<01:32:17.159> now<01:32:17.340> every<01:32:17.520> everything<01:32:17.880> looks 01:32:18.350 --> 01:32:18.360 align:start position:0% hammer and now every everything looks 01:32:18.360 --> 01:32:21.950 align:start position:0% hammer and now every everything looks like<01:32:18.480> a<01:32:18.659> nail<01:32:18.840> and<01:32:20.100> um<01:32:20.159> so<01:32:20.760> I<01:32:21.120> think<01:32:21.239> there<01:32:21.780> has 01:32:21.950 --> 01:32:21.960 align:start position:0% like a nail and um so I think there has 01:32:21.960 --> 01:32:26.390 align:start position:0% like a nail and um so I think there has to<01:32:22.139> be<01:32:22.260> more 01:32:26.390 --> 01:32:26.400 align:start position:0% 01:32:26.400 --> 01:32:30.169 align:start position:0% oh<01:32:26.820> oh<01:32:26.820> yeah<01:32:27.360> yeah<01:32:27.600> so<01:32:27.960> sorry<01:32:28.080> sorry<01:32:28.639> yeah<01:32:29.639> okay 01:32:30.169 --> 01:32:30.179 align:start position:0% oh oh yeah yeah so sorry sorry yeah okay 01:32:30.179 --> 01:32:32.570 align:start position:0% oh oh yeah yeah so sorry sorry yeah okay you<01:32:30.600> know 01:32:32.570 --> 01:32:32.580 align:start position:0% you know 01:32:32.580 --> 01:32:34.010 align:start position:0% you know we<01:32:32.820> want<01:32:32.940> to<01:32:33.000> do<01:32:33.120> this 01:32:34.010 --> 01:32:34.020 align:start position:0% we want to do this 01:32:34.020 --> 01:32:35.990 align:start position:0% we want to do this like<01:32:34.440> this<01:32:34.739> change<01:32:34.860> was<01:32:35.219> like<01:32:35.580> in<01:32:35.880> the 01:32:35.990 --> 01:32:36.000 align:start position:0% like this change was like in the 01:32:36.000 --> 01:32:37.850 align:start position:0% like this change was like in the pipeline<01:32:36.360> for<01:32:36.540> like<01:32:36.780> months<01:32:37.380> I<01:32:37.560> think<01:32:37.679> it 01:32:37.850 --> 01:32:37.860 align:start position:0% pipeline for like months I think it 01:32:37.860 --> 01:32:39.649 align:start position:0% pipeline for like months I think it wasn't<01:32:37.980> like<01:32:38.219> something<01:32:38.460> we<01:32:38.820> suddenly<01:32:39.420> came 01:32:39.649 --> 01:32:39.659 align:start position:0% wasn't like something we suddenly came 01:32:39.659 --> 01:32:41.149 align:start position:0% wasn't like something we suddenly came up<01:32:39.780> with<01:32:39.900> this<01:32:40.020> was<01:32:40.260> clear<01:32:40.440> we<01:32:40.679> wanted<01:32:40.800> to<01:32:40.980> do 01:32:41.149 --> 01:32:41.159 align:start position:0% up with this was clear we wanted to do 01:32:41.159 --> 01:32:42.770 align:start position:0% up with this was clear we wanted to do this<01:32:41.219> and<01:32:41.520> we<01:32:41.760> do<01:32:41.820> have<01:32:41.940> the<01:32:42.120> change<01:32:42.300> in<01:32:42.540> when 01:32:42.770 --> 01:32:42.780 align:start position:0% this and we do have the change in when 01:32:42.780 --> 01:32:44.149 align:start position:0% this and we do have the change in when they<01:32:42.960> didn't<01:32:43.020> get<01:32:43.199> in<01:32:43.380> prison<01:32:43.620> in<01:32:43.860> a<01:32:43.980> live 01:32:44.149 --> 01:32:44.159 align:start position:0% they didn't get in prison in a live 01:32:44.159 --> 01:32:47.330 align:start position:0% they didn't get in prison in a live devnet<01:32:44.699> okay<01:32:45.060> yeah<01:32:45.480> yeah<01:32:45.719> so<01:32:46.020> but<01:32:46.800> those<01:32:47.219> are 01:32:47.330 --> 01:32:47.340 align:start position:0% devnet okay yeah yeah so but those are 01:32:47.340 --> 01:32:48.470 align:start position:0% devnet okay yeah yeah so but those are the<01:32:47.460> things<01:32:47.580> that 01:32:48.470 --> 01:32:48.480 align:start position:0% the things that 01:32:48.480 --> 01:32:51.050 align:start position:0% the things that those<01:32:49.199> those<01:32:49.380> are<01:32:49.860> things<01:32:50.040> that<01:32:50.219> are<01:32:50.400> uh<01:32:50.760> that 01:32:51.050 --> 01:32:51.060 align:start position:0% those those are things that are uh that 01:32:51.060 --> 01:32:53.810 align:start position:0% those those are things that are uh that we're<01:32:51.239> not<01:32:51.420> not<01:32:51.840> quite<01:32:52.139> clear<01:32:52.320> to<01:32:52.500> me<01:32:52.679> and<01:32:53.760> um 01:32:53.810 --> 01:32:53.820 align:start position:0% we're not not quite clear to me and um 01:32:53.820 --> 01:32:55.490 align:start position:0% we're not not quite clear to me and um so<01:32:54.179> from<01:32:54.300> my<01:32:54.540> point<01:32:54.659> of<01:32:54.840> view 01:32:55.490 --> 01:32:55.500 align:start position:0% so from my point of view 01:32:55.500 --> 01:32:59.330 align:start position:0% so from my point of view we<01:32:56.159> could<01:32:56.340> ship<01:32:56.880> with<01:32:57.420> uh<01:32:57.960> withdrawals 01:32:59.330 --> 01:32:59.340 align:start position:0% we could ship with uh withdrawals 01:32:59.340 --> 01:33:04.250 align:start position:0% we could ship with uh withdrawals easily<01:33:00.120> January<01:33:00.739> uh<01:33:02.159> especially<01:33:02.940> if<01:33:03.300> we<01:33:03.480> if<01:33:03.900> we 01:33:04.250 --> 01:33:04.260 align:start position:0% easily January uh especially if we if we 01:33:04.260 --> 01:33:12.649 align:start position:0% easily January uh especially if we if we uh<01:33:04.679> like<01:33:04.980> kick<01:33:05.340> out<01:33:05.520> some<01:33:05.699> of<01:33:05.820> them 01:33:12.649 --> 01:33:12.659 align:start position:0% 01:33:12.659 --> 01:33:13.910 align:start position:0% yes 01:33:13.910 --> 01:33:13.920 align:start position:0% yes 01:33:13.920 --> 01:33:20.709 align:start position:0% yes now<01:33:14.580> yeah 01:33:20.709 --> 01:33:20.719 align:start position:0% 01:33:20.719 --> 01:33:24.590 align:start position:0% okay<01:33:22.159> it's<01:33:23.159> probably<01:33:23.760> a<01:33:24.000> bigger<01:33:24.239> change<01:33:24.360> for 01:33:24.590 --> 01:33:24.600 align:start position:0% okay it's probably a bigger change for 01:33:24.600 --> 01:33:26.149 align:start position:0% okay it's probably a bigger change for the<01:33:24.719> for<01:33:24.900> the<01:33:25.080> consensus<01:33:25.500> layer<01:33:25.800> I<01:33:25.920> think<01:33:26.040> for 01:33:26.149 --> 01:33:26.159 align:start position:0% the for the consensus layer I think for 01:33:26.159 --> 01:33:28.850 align:start position:0% the for the consensus layer I think for the<01:33:26.340> execution<01:33:26.699> layer<01:33:27.120> it's<01:33:27.300> it's<01:33:27.659> pretty<01:33:28.199> uh 01:33:28.850 --> 01:33:28.860 align:start position:0% the execution layer it's it's pretty uh 01:33:28.860 --> 01:33:31.550 align:start position:0% the execution layer it's it's pretty uh pretty<01:33:29.100> much<01:33:29.280> done<01:33:29.520> and 01:33:31.550 --> 01:33:31.560 align:start position:0% pretty much done and 01:33:31.560 --> 01:33:35.030 align:start position:0% pretty much done and um<01:33:31.699> okay<01:33:32.699> okay<01:33:33.540> okay<01:33:33.600> maybe<01:33:34.260> I'm<01:33:34.440> I'm<01:33:34.679> totally 01:33:35.030 --> 01:33:35.040 align:start position:0% um okay okay okay maybe I'm I'm totally 01:33:35.040 --> 01:33:36.410 align:start position:0% um okay okay okay maybe I'm I'm totally wrong<01:33:35.219> here 01:33:36.410 --> 01:33:36.420 align:start position:0% wrong here 01:33:36.420 --> 01:33:37.729 align:start position:0% wrong here um 01:33:37.729 --> 01:33:37.739 align:start position:0% um 01:33:37.739 --> 01:33:40.850 align:start position:0% um but<01:33:38.219> I<01:33:38.400> I<01:33:38.639> agree<01:33:38.880> with<01:33:39.120> the<01:33:39.300> argument<01:33:39.659> that 01:33:40.850 --> 01:33:40.860 align:start position:0% but I I agree with the argument that 01:33:40.860 --> 01:33:44.770 align:start position:0% but I I agree with the argument that so<01:33:41.580> even<01:33:42.239> if<01:33:42.540> we<01:33:42.659> were<01:33:42.840> to<01:33:42.960> ship<01:33:43.760> uh 01:33:44.770 --> 01:33:44.780 align:start position:0% so even if we were to ship uh 01:33:44.780 --> 01:33:48.649 align:start position:0% so even if we were to ship uh withdrawals<01:33:45.780> in<01:33:46.020> January 01:33:48.649 --> 01:33:48.659 align:start position:0% 01:33:48.659 --> 01:33:51.470 align:start position:0% um<01:33:48.780> I<01:33:49.260> think<01:33:49.380> we<01:33:49.620> could<01:33:49.800> own<01:33:50.040> the<01:33:50.280> ship<01:33:50.460> uh<01:33:51.300> tank 01:33:51.470 --> 01:33:51.480 align:start position:0% um I think we could own the ship uh tank 01:33:51.480 --> 01:33:54.470 align:start position:0% um I think we could own the ship uh tank sharding 01:33:54.470 --> 01:33:54.480 align:start position:0% 01:33:54.480 --> 01:33:59.209 align:start position:0% um<01:33:54.500> September<01:33:55.520> of<01:33:56.520> of<01:33:57.179> 2023 01:33:59.209 --> 01:33:59.219 align:start position:0% um September of of 2023 01:33:59.219 --> 01:34:01.910 align:start position:0% um September of of 2023 if<01:33:59.520> we<01:33:59.639> were<01:33:59.760> to<01:33:59.880> do<01:34:00.060> both<01:34:00.380> we<01:34:01.380> can<01:34:01.620> probably 01:34:01.910 --> 01:34:01.920 align:start position:0% if we were to do both we can probably 01:34:01.920 --> 01:34:05.570 align:start position:0% if we were to do both we can probably ship<01:34:02.580> it<01:34:02.760> somewhere<01:34:03.540> in<01:34:03.719> the<01:34:03.840> middle<01:34:03.980> and<01:34:04.980> so 01:34:05.570 --> 01:34:05.580 align:start position:0% ship it somewhere in the middle and so 01:34:05.580 --> 01:34:08.990 align:start position:0% ship it somewhere in the middle and so actually<01:34:06.360> would<01:34:07.380> if<01:34:07.679> I<01:34:07.800> if<01:34:07.980> I<01:34:08.280> really<01:34:08.460> have<01:34:08.699> if 01:34:08.990 --> 01:34:09.000 align:start position:0% actually would if I if I really have if 01:34:09.000 --> 01:34:10.610 align:start position:0% actually would if I if I really have if I<01:34:09.239> really<01:34:09.420> think<01:34:09.659> about<01:34:09.840> it<01:34:10.080> it<01:34:10.320> would 01:34:10.610 --> 01:34:10.620 align:start position:0% I really think about it it would 01:34:10.620 --> 01:34:13.850 align:start position:0% I really think about it it would probably<01:34:11.159> cut<01:34:11.460> to<01:34:11.699> two<01:34:11.940> months<01:34:12.300> uh<01:34:13.080> to<01:34:13.260> to<01:34:13.440> both 01:34:13.850 --> 01:34:13.860 align:start position:0% probably cut to two months uh to to both 01:34:13.860 --> 01:34:16.010 align:start position:0% probably cut to two months uh to to both of<01:34:14.040> it<01:34:14.159> even<01:34:14.580> even<01:34:14.880> though<01:34:15.120> I<01:34:15.360> don't<01:34:15.480> like<01:34:15.780> it 01:34:16.010 --> 01:34:16.020 align:start position:0% of it even even though I don't like it 01:34:16.020 --> 01:34:19.010 align:start position:0% of it even even though I don't like it and<01:34:16.380> even<01:34:16.560> though<01:34:16.800> I<01:34:17.280> don't<01:34:17.340> like<01:34:17.520> to<01:34:17.699> admit<01:34:18.060> it 01:34:19.010 --> 01:34:19.020 align:start position:0% and even though I don't like to admit it 01:34:19.020 --> 01:34:21.110 align:start position:0% and even though I don't like to admit it um<01:34:19.080> but<01:34:19.500> I<01:34:19.679> think<01:34:19.860> it<01:34:20.280> might<01:34:20.520> be<01:34:20.760> the<01:34:21.000> right 01:34:21.110 --> 01:34:21.120 align:start position:0% um but I think it might be the right 01:34:21.120 --> 01:34:24.610 align:start position:0% um but I think it might be the right thing<01:34:21.360> to<01:34:21.540> do 01:34:24.610 --> 01:34:24.620 align:start position:0% 01:34:24.620 --> 01:34:27.169 align:start position:0% you<01:34:25.620> have<01:34:25.739> is<01:34:25.920> probably<01:34:26.100> that<01:34:26.460> it<01:34:26.639> is<01:34:26.820> a<01:34:27.060> bit 01:34:27.169 --> 01:34:27.179 align:start position:0% you have is probably that it is a bit 01:34:27.179 --> 01:34:28.910 align:start position:0% you have is probably that it is a bit more<01:34:27.420> risky<01:34:27.840> to<01:34:28.020> do<01:34:28.139> both<01:34:28.320> at<01:34:28.500> the<01:34:28.620> same<01:34:28.800> time 01:34:28.910 --> 01:34:28.920 align:start position:0% more risky to do both at the same time 01:34:28.920 --> 01:34:30.890 align:start position:0% more risky to do both at the same time and<01:34:29.639> I<01:34:29.820> think<01:34:29.940> like<01:34:30.179> most<01:34:30.420> people<01:34:30.600> would 01:34:30.890 --> 01:34:30.900 align:start position:0% and I think like most people would 01:34:30.900 --> 01:34:32.270 align:start position:0% and I think like most people would probably<01:34:31.139> agree<01:34:31.440> with<01:34:31.620> that<01:34:31.739> like<01:34:32.040> that 01:34:32.270 --> 01:34:32.280 align:start position:0% probably agree with that like that 01:34:32.280 --> 01:34:35.030 align:start position:0% probably agree with that like that making<01:34:32.520> a<01:34:32.820> bigger<01:34:33.060> change<01:34:33.239> definitely<01:34:34.040> adds 01:34:35.030 --> 01:34:35.040 align:start position:0% making a bigger change definitely adds 01:34:35.040 --> 01:34:37.430 align:start position:0% making a bigger change definitely adds to<01:34:35.159> the<01:34:35.340> risk<01:34:35.580> of<01:34:35.760> the<01:34:36.000> hard<01:34:36.060> Fork<01:34:36.480> itself 01:34:37.430 --> 01:34:37.440 align:start position:0% to the risk of the hard Fork itself 01:34:37.440 --> 01:34:39.110 align:start position:0% to the risk of the hard Fork itself um<01:34:37.560> and<01:34:37.739> I<01:34:37.860> think<01:34:38.040> we<01:34:38.400> also<01:34:38.639> should<01:34:38.760> have<01:34:38.940> an 01:34:39.110 --> 01:34:39.120 align:start position:0% um and I think we also should have an 01:34:39.120 --> 01:34:42.050 align:start position:0% um and I think we also should have an honest<01:34:39.360> conversation<01:34:39.780> on<01:34:40.199> in<01:34:40.500> which<01:34:40.739> cases<01:34:41.219> we 01:34:42.050 --> 01:34:42.060 align:start position:0% honest conversation on in which cases we 01:34:42.060 --> 01:34:43.910 align:start position:0% honest conversation on in which cases we are<01:34:42.300> willing<01:34:42.659> to<01:34:42.840> accept<01:34:43.020> those<01:34:43.500> risks 01:34:43.910 --> 01:34:43.920 align:start position:0% are willing to accept those risks 01:34:43.920 --> 01:34:45.470 align:start position:0% are willing to accept those risks because<01:34:44.100> what<01:34:44.460> we're<01:34:44.580> doing<01:34:44.760> is<01:34:44.940> just<01:34:45.179> so 01:34:45.470 --> 01:34:45.480 align:start position:0% because what we're doing is just so 01:34:45.480 --> 01:34:48.110 align:start position:0% because what we're doing is just so important<01:34:45.840> that<01:34:46.260> maybe<01:34:46.800> like<01:34:47.219> some<01:34:47.639> risks 01:34:48.110 --> 01:34:48.120 align:start position:0% important that maybe like some risks 01:34:48.120 --> 01:34:51.490 align:start position:0% important that maybe like some risks have<01:34:48.300> to<01:34:48.420> be<01:34:48.600> accepted<01:34:49.020> as<01:34:49.199> part<01:34:49.440> of<01:34:49.560> doing<01:34:49.679> it 01:34:51.490 --> 01:34:51.500 align:start position:0% have to be accepted as part of doing it 01:34:51.500 --> 01:34:54.950 align:start position:0% have to be accepted as part of doing it yeah<01:34:52.500> Paul<01:34:52.739> from<01:34:52.980> techu<01:34:53.400> Team<01:34:53.580> just<01:34:53.940> on<01:34:54.179> that<01:34:54.360> I 01:34:54.950 --> 01:34:54.960 align:start position:0% yeah Paul from techu Team just on that I 01:34:54.960 --> 01:34:56.330 align:start position:0% yeah Paul from techu Team just on that I mean<01:34:55.080> there's<01:34:55.260> a<01:34:55.380> couple<01:34:55.500> of<01:34:55.620> aspects<01:34:56.100> maybe 01:34:56.330 --> 01:34:56.340 align:start position:0% mean there's a couple of aspects maybe 01:34:56.340 --> 01:34:58.189 align:start position:0% mean there's a couple of aspects maybe we<01:34:56.639> need<01:34:56.820> to<01:34:56.940> get<01:34:57.060> better<01:34:57.300> at<01:34:57.719> doing<01:34:57.960> hard 01:34:58.189 --> 01:34:58.199 align:start position:0% we need to get better at doing hard 01:34:58.199 --> 01:35:00.770 align:start position:0% we need to get better at doing hard forks<01:34:58.739> and<01:34:58.980> releasing<01:34:59.340> them<01:34:59.520> honestly<01:35:00.239> it's<01:35:00.600> a 01:35:00.770 --> 01:35:00.780 align:start position:0% forks and releasing them honestly it's a 01:35:00.780 --> 01:35:03.110 align:start position:0% forks and releasing them honestly it's a long<01:35:00.900> time<01:35:01.080> between<01:35:01.380> code<01:35:01.739> completion<01:35:02.280> and 01:35:03.110 --> 01:35:03.120 align:start position:0% long time between code completion and 01:35:03.120 --> 01:35:05.870 align:start position:0% long time between code completion and getting<01:35:03.360> to<01:35:03.659> getting<01:35:04.139> to<01:35:04.380> that<01:35:04.560> gate<01:35:04.800> that<01:35:05.699> may 01:35:05.870 --> 01:35:05.880 align:start position:0% getting to getting to that gate that may 01:35:05.880 --> 01:35:07.970 align:start position:0% getting to getting to that gate that may be<01:35:06.000> a<01:35:06.179> thing<01:35:06.300> we<01:35:06.480> need<01:35:06.659> to<01:35:06.840> address<01:35:07.199> but<01:35:07.800> the 01:35:07.970 --> 01:35:07.980 align:start position:0% be a thing we need to address but the 01:35:07.980 --> 01:35:09.290 align:start position:0% be a thing we need to address but the other<01:35:08.100> side<01:35:08.280> of<01:35:08.460> it<01:35:08.580> Playing<01:35:08.820> devil's 01:35:09.290 --> 01:35:09.300 align:start position:0% other side of it Playing devil's 01:35:09.300 --> 01:35:11.030 align:start position:0% other side of it Playing devil's advocate 01:35:11.030 --> 01:35:11.040 align:start position:0% advocate 01:35:11.040 --> 01:35:13.490 align:start position:0% advocate I<01:35:11.520> understand<01:35:11.699> that<01:35:12.420> 4844<01:35:13.080> might<01:35:13.320> be 01:35:13.490 --> 01:35:13.500 align:start position:0% I understand that 4844 might be 01:35:13.500 --> 01:35:15.229 align:start position:0% I understand that 4844 might be important<01:35:13.800> and<01:35:13.980> if<01:35:14.159> it's<01:35:14.340> relatively<01:35:14.880> well 01:35:15.229 --> 01:35:15.239 align:start position:0% important and if it's relatively well 01:35:15.239 --> 01:35:16.430 align:start position:0% important and if it's relatively well defined 01:35:16.430 --> 01:35:16.440 align:start position:0% defined 01:35:16.440 --> 01:35:18.290 align:start position:0% defined there's<01:35:16.980> nothing<01:35:17.219> physically<01:35:17.699> stopping<01:35:18.179> us 01:35:18.290 --> 01:35:18.300 align:start position:0% there's nothing physically stopping us 01:35:18.300 --> 01:35:20.270 align:start position:0% there's nothing physically stopping us from<01:35:18.540> doing<01:35:18.780> that<01:35:19.020> first 01:35:20.270 --> 01:35:20.280 align:start position:0% from doing that first 01:35:20.280 --> 01:35:23.149 align:start position:0% from doing that first and<01:35:20.940> just<01:35:21.360> delivering<01:35:21.719> 4844<01:35:22.320> and<01:35:22.920> not 01:35:23.149 --> 01:35:23.159 align:start position:0% and just delivering 4844 and not 01:35:23.159 --> 01:35:25.490 align:start position:0% and just delivering 4844 and not delivering<01:35:23.520> withdrawals<01:35:24.060> I<01:35:24.360> mean<01:35:24.480> it's<01:35:24.659> a<01:35:24.900> it 01:35:25.490 --> 01:35:25.500 align:start position:0% delivering withdrawals I mean it's a it 01:35:25.500 --> 01:35:28.430 align:start position:0% delivering withdrawals I mean it's a it is<01:35:25.679> it<01:35:26.040> is<01:35:26.219> an<01:35:26.460> actual<01:35:26.699> option<01:35:27.060> that<01:35:27.300> we<01:35:27.480> have 01:35:28.430 --> 01:35:28.440 align:start position:0% is it is an actual option that we have 01:35:28.440 --> 01:35:30.649 align:start position:0% is it is an actual option that we have no<01:35:29.040> I'm<01:35:29.400> playing<01:35:29.580> Devil's<01:35:30.000> Advocate<01:35:30.360> sure 01:35:30.649 --> 01:35:30.659 align:start position:0% no I'm playing Devil's Advocate sure 01:35:30.659 --> 01:35:32.090 align:start position:0% no I'm playing Devil's Advocate sure Paul<01:35:30.900> is<01:35:31.080> not<01:35:31.260> representing<01:35:31.679> the<01:35:31.800> views<01:35:31.980> of 01:35:32.090 --> 01:35:32.100 align:start position:0% Paul is not representing the views of 01:35:32.100 --> 01:35:33.709 align:start position:0% Paul is not representing the views of the<01:35:32.219> teku<01:35:32.580> team 01:35:33.709 --> 01:35:33.719 align:start position:0% the teku team 01:35:33.719 --> 01:35:35.930 align:start position:0% the teku team this<01:35:34.260> is<01:35:34.320> no<01:35:34.500> but<01:35:34.679> it's<01:35:34.800> a<01:35:34.920> fair<01:35:35.040> comment<01:35:35.280> this 01:35:35.930 --> 01:35:35.940 align:start position:0% this is no but it's a fair comment this 01:35:35.940 --> 01:35:38.510 align:start position:0% this is no but it's a fair comment this is<01:35:36.060> purely<01:35:36.300> my<01:35:36.540> view<01:35:36.719> but<01:35:37.080> in<01:35:37.500> reality<01:35:37.800> if<01:35:38.219> two 01:35:38.510 --> 01:35:38.520 align:start position:0% is purely my view but in reality if two 01:35:38.520 --> 01:35:41.149 align:start position:0% is purely my view but in reality if two is<01:35:38.940> too<01:35:39.239> hard<01:35:39.420> and<01:35:40.080> we<01:35:40.260> want<01:35:40.440> to<01:35:40.560> deliver<01:35:40.679> this 01:35:41.149 --> 01:35:41.159 align:start position:0% is too hard and we want to deliver this 01:35:41.159 --> 01:35:43.610 align:start position:0% is too hard and we want to deliver this early<01:35:41.400> in<01:35:41.820> a<01:35:41.940> timely<01:35:42.179> manner<01:35:42.540> to<01:35:42.780> not<01:35:43.020> stuff 01:35:43.610 --> 01:35:43.620 align:start position:0% early in a timely manner to not stuff 01:35:43.620 --> 01:35:45.890 align:start position:0% early in a timely manner to not stuff over<01:35:43.800> businesses<01:35:44.460> that<01:35:45.179> is<01:35:45.300> an<01:35:45.420> option<01:35:45.719> that 01:35:45.890 --> 01:35:45.900 align:start position:0% over businesses that is an option that 01:35:45.900 --> 01:35:47.510 align:start position:0% over businesses that is an option that we<01:35:46.080> do<01:35:46.199> have 01:35:47.510 --> 01:35:47.520 align:start position:0% we do have 01:35:47.520 --> 01:35:49.189 align:start position:0% we do have yeah<01:35:47.580> we<01:35:48.060> should<01:35:48.179> absolutely<01:35:48.480> focus<01:35:48.840> on<01:35:49.020> doing 01:35:49.189 --> 01:35:49.199 align:start position:0% yeah we should absolutely focus on doing 01:35:49.199 --> 01:35:52.250 align:start position:0% yeah we should absolutely focus on doing the<01:35:49.440> most<01:35:49.560> important<01:35:49.920> thing<01:35:50.100> first<01:35:50.340> always 01:35:52.250 --> 01:35:52.260 align:start position:0% the most important thing first always 01:35:52.260 --> 01:35:54.290 align:start position:0% the most important thing first always um<01:35:52.320> I<01:35:52.739> think<01:35:52.860> the<01:35:53.400> point<01:35:53.699> that's<01:35:53.880> come<01:35:54.060> up<01:35:54.120> a 01:35:54.290 --> 01:35:54.300 align:start position:0% um I think the point that's come up a 01:35:54.300 --> 01:35:56.169 align:start position:0% um I think the point that's come up a couple<01:35:54.420> of<01:35:54.540> times<01:35:54.719> is<01:35:55.020> you<01:35:55.260> know<01:35:55.320> when<01:35:55.620> we<01:35:55.800> ship 01:35:56.169 --> 01:35:56.179 align:start position:0% couple of times is you know when we ship 01:35:56.179 --> 01:35:58.129 align:start position:0% couple of times is you know when we ship withdrawals<01:35:57.179> and<01:35:57.540> it's<01:35:57.659> actually<01:35:57.780> when<01:35:57.960> we 01:35:58.129 --> 01:35:58.139 align:start position:0% withdrawals and it's actually when we 01:35:58.139 --> 01:36:00.290 align:start position:0% withdrawals and it's actually when we finish<01:35:58.260> code<01:35:58.560> completion<01:35:59.100> because<01:35:59.820> running 01:36:00.290 --> 01:36:00.300 align:start position:0% finish code completion because running 01:36:00.300 --> 01:36:01.729 align:start position:0% finish code completion because running through<01:36:00.540> test<01:36:00.719> Nets<01:36:01.080> doesn't<01:36:01.199> take<01:36:01.380> quarter 01:36:01.729 --> 01:36:01.739 align:start position:0% through test Nets doesn't take quarter 01:36:01.739 --> 01:36:03.470 align:start position:0% through test Nets doesn't take quarter of<01:36:01.860> time<01:36:01.980> we<01:36:02.280> put<01:36:02.400> out<01:36:02.580> a<01:36:02.699> release<01:36:02.820> it<01:36:03.120> should 01:36:03.470 --> 01:36:03.480 align:start position:0% of time we put out a release it should 01:36:03.480 --> 01:36:05.450 align:start position:0% of time we put out a release it should be<01:36:03.600> pretty<01:36:03.719> quick<01:36:03.900> and<01:36:04.080> easy<01:36:04.340> there<01:36:05.340> is 01:36:05.450 --> 01:36:05.460 align:start position:0% be pretty quick and easy there is 01:36:05.460 --> 01:36:07.370 align:start position:0% be pretty quick and easy there is coordination<01:36:05.880> cost<01:36:06.179> and<01:36:06.659> it<01:36:06.840> consumes<01:36:07.260> all 01:36:07.370 --> 01:36:07.380 align:start position:0% coordination cost and it consumes all 01:36:07.380 --> 01:36:09.169 align:start position:0% coordination cost and it consumes all core<01:36:07.500> devs<01:36:07.800> for<01:36:07.920> a<01:36:07.980> while<01:36:08.040> so<01:36:08.340> you've<01:36:08.940> got<01:36:09.060> to 01:36:09.169 --> 01:36:09.179 align:start position:0% core devs for a while so you've got to 01:36:09.179 --> 01:36:10.370 align:start position:0% core devs for a while so you've got to know<01:36:09.360> what's<01:36:09.540> coming<01:36:09.719> next<01:36:09.960> if<01:36:10.199> you're<01:36:10.320> going 01:36:10.370 --> 01:36:10.380 align:start position:0% know what's coming next if you're going 01:36:10.380 --> 01:36:12.229 align:start position:0% know what's coming next if you're going to<01:36:10.500> paralyze<01:36:10.920> it<01:36:11.040> but<01:36:11.400> it's<01:36:11.639> code<01:36:11.820> completion 01:36:12.229 --> 01:36:12.239 align:start position:0% to paralyze it but it's code completion 01:36:12.239 --> 01:36:13.910 align:start position:0% to paralyze it but it's code completion that's<01:36:12.480> the<01:36:12.659> big<01:36:12.780> thing<01:36:12.960> I'll<01:36:13.500> give<01:36:13.679> it<01:36:13.800> to 01:36:13.910 --> 01:36:13.920 align:start position:0% that's the big thing I'll give it to 01:36:13.920 --> 01:36:14.689 align:start position:0% that's the big thing I'll give it to them 01:36:14.689 --> 01:36:14.699 align:start position:0% them 01:36:14.699 --> 01:36:18.050 align:start position:0% them uh<01:36:15.480> in<01:36:15.659> between<01:36:15.840> I<01:36:16.199> just<01:36:16.440> pop<01:36:16.920> in 01:36:18.050 --> 01:36:18.060 align:start position:0% uh in between I just pop in 01:36:18.060 --> 01:36:19.970 align:start position:0% uh in between I just pop in um so<01:36:18.540> in<01:36:18.659> my<01:36:18.780> opinion<01:36:18.960> withdrawals<01:36:19.679> are<01:36:19.800> kind 01:36:19.970 --> 01:36:19.980 align:start position:0% um so in my opinion withdrawals are kind 01:36:19.980 --> 01:36:22.070 align:start position:0% um so in my opinion withdrawals are kind of<01:36:20.100> specked<01:36:20.639> out<01:36:20.760> so<01:36:21.060> it<01:36:21.239> I<01:36:21.600> mean<01:36:21.719> there<01:36:21.960> are 01:36:22.070 --> 01:36:22.080 align:start position:0% of specked out so it I mean there are 01:36:22.080 --> 01:36:24.470 align:start position:0% of specked out so it I mean there are variations<01:36:22.560> but<01:36:23.040> it's<01:36:23.340> simple<01:36:23.760> it's<01:36:24.300> really 01:36:24.470 --> 01:36:24.480 align:start position:0% variations but it's simple it's really 01:36:24.480 --> 01:36:28.250 align:start position:0% variations but it's simple it's really really<01:36:24.659> simple<01:36:25.020> whereas<01:36:25.980> with<01:36:26.280> the<01:36:26.840> 4844<01:36:27.840> that 01:36:28.250 --> 01:36:28.260 align:start position:0% really simple whereas with the 4844 that 01:36:28.260 --> 01:36:30.709 align:start position:0% really simple whereas with the 4844 that will<01:36:28.500> most<01:36:28.920> definitely<01:36:29.280> take<01:36:29.520> a<01:36:30.420> lot<01:36:30.480> more 01:36:30.709 --> 01:36:30.719 align:start position:0% will most definitely take a lot more 01:36:30.719 --> 01:36:32.950 align:start position:0% will most definitely take a lot more time<01:36:30.900> to<01:36:31.080> spec<01:36:31.320> out<01:36:31.560> and<01:36:31.739> it<01:36:31.980> has<01:36:32.159> a<01:36:32.340> lot<01:36:32.400> more 01:36:32.950 --> 01:36:32.960 align:start position:0% time to spec out and it has a lot more 01:36:32.960 --> 01:36:35.330 align:start position:0% time to spec out and it has a lot more potential<01:36:33.960> problems<01:36:34.500> with<01:36:34.739> denial<01:36:35.159> of 01:36:35.330 --> 01:36:35.340 align:start position:0% potential problems with denial of 01:36:35.340 --> 01:36:36.950 align:start position:0% potential problems with denial of service<01:36:35.520> and<01:36:35.820> everything<01:36:35.940> it<01:36:36.239> affects 01:36:36.950 --> 01:36:36.960 align:start position:0% service and everything it affects 01:36:36.960 --> 01:36:39.110 align:start position:0% service and everything it affects Network<01:36:37.139> so<01:36:37.620> withdrawals<01:36:38.460> that's<01:36:38.699> just<01:36:39.000> a 01:36:39.110 --> 01:36:39.120 align:start position:0% Network so withdrawals that's just a 01:36:39.120 --> 01:36:40.729 align:start position:0% Network so withdrawals that's just a tiny<01:36:39.420> consensus<01:36:39.840> change<01:36:40.080> you<01:36:40.260> know<01:36:40.380> tweak<01:36:40.620> a 01:36:40.729 --> 01:36:40.739 align:start position:0% tiny consensus change you know tweak a 01:36:40.739 --> 01:36:43.310 align:start position:0% tiny consensus change you know tweak a bit<01:36:40.800> the<01:36:40.980> data<01:36:41.280> structures<01:36:41.580> and<01:36:41.760> done<01:36:42.000> with<01:36:42.900> uh 01:36:43.310 --> 01:36:43.320 align:start position:0% bit the data structures and done with uh 01:36:43.320 --> 01:36:45.770 align:start position:0% bit the data structures and done with uh with<01:36:43.800> 4844<01:36:44.340> that<01:36:44.820> has<01:36:45.060> a<01:36:45.300> much<01:36:45.420> deeper 01:36:45.770 --> 01:36:45.780 align:start position:0% with 4844 that has a much deeper 01:36:45.780 --> 01:36:47.570 align:start position:0% with 4844 that has a much deeper implication<01:36:46.199> so<01:36:46.500> I<01:36:46.679> think<01:36:46.800> it<01:36:47.100> it<01:36:47.340> will 01:36:47.570 --> 01:36:47.580 align:start position:0% implication so I think it it will 01:36:47.580 --> 01:36:49.370 align:start position:0% implication so I think it it will require<01:36:47.760> a<01:36:48.120> lot<01:36:48.179> more<01:36:48.360> work 01:36:49.370 --> 01:36:49.380 align:start position:0% require a lot more work 01:36:49.380 --> 01:36:51.950 align:start position:0% require a lot more work and<01:36:49.980> in<01:36:50.219> my<01:36:50.340> opinion<01:36:50.699> it<01:36:51.360> would<01:36:51.480> be<01:36:51.659> much 01:36:51.950 --> 01:36:51.960 align:start position:0% and in my opinion it would be much 01:36:51.960 --> 01:36:55.189 align:start position:0% and in my opinion it would be much simpler<01:36:52.440> to<01:36:52.860> say<01:36:53.639> that<01:36:53.820> okay<01:36:54.000> for<01:36:54.360> withdrawals 01:36:55.189 --> 01:36:55.199 align:start position:0% simpler to say that okay for withdrawals 01:36:55.199 --> 01:36:57.890 align:start position:0% simpler to say that okay for withdrawals are<01:36:55.380> definitely<01:36:55.679> going<01:36:56.040> in<01:36:56.340> and<01:36:57.000> maybe<01:36:57.179> give<01:36:57.719> a 01:36:57.890 --> 01:36:57.900 align:start position:0% are definitely going in and maybe give a 01:36:57.900 --> 01:37:01.370 align:start position:0% are definitely going in and maybe give a cut<01:36:58.080> off<01:36:58.320> that<01:36:59.159> if<01:36:59.460> we<01:36:59.820> for<01:37:00.179> some<01:37:00.360> reason<01:37:00.540> 4844 01:37:01.370 --> 01:37:01.380 align:start position:0% cut off that if we for some reason 4844 01:37:01.380 --> 01:37:03.169 align:start position:0% cut off that if we for some reason 4844 gets<01:37:01.800> complicated<01:37:02.159> and<01:37:02.400> we<01:37:02.520> cannot<01:37:02.760> finish<01:37:02.940> it 01:37:03.169 --> 01:37:03.179 align:start position:0% gets complicated and we cannot finish it 01:37:03.179 --> 01:37:04.070 align:start position:0% gets complicated and we cannot finish it by 01:37:04.070 --> 01:37:04.080 align:start position:0% by 01:37:04.080 --> 01:37:06.649 align:start position:0% by month<01:37:04.560> X<01:37:04.920> then<01:37:05.280> just<01:37:05.520> say<01:37:05.760> okay<01:37:05.940> we're<01:37:06.300> rolling 01:37:06.649 --> 01:37:06.659 align:start position:0% month X then just say okay we're rolling 01:37:06.659 --> 01:37:09.169 align:start position:0% month X then just say okay we're rolling with<01:37:06.900> the<01:37:07.020> withdrawals<01:37:07.679> first<01:37:07.920> and<01:37:08.159> then 01:37:09.169 --> 01:37:09.179 align:start position:0% with the withdrawals first and then 01:37:09.179 --> 01:37:12.290 align:start position:0% with the withdrawals first and then whatever<01:37:09.719> whatever<01:37:10.199> the<01:37:10.620> other<01:37:10.800> is<01:37:11.100> ready 01:37:12.290 --> 01:37:12.300 align:start position:0% whatever whatever the other is ready 01:37:12.300 --> 01:37:14.629 align:start position:0% whatever whatever the other is ready so<01:37:12.840> quick<01:37:13.139> question<01:37:13.440> from<01:37:13.800> me<01:37:13.980> because<01:37:14.280> I 01:37:14.629 --> 01:37:14.639 align:start position:0% so quick question from me because I 01:37:14.639 --> 01:37:16.430 align:start position:0% so quick question from me because I heard<01:37:14.880> the<01:37:15.239> term<01:37:15.420> a<01:37:15.659> few<01:37:15.780> times<01:37:15.960> like<01:37:16.260> about 01:37:16.430 --> 01:37:16.440 align:start position:0% heard the term a few times like about 01:37:16.440 --> 01:37:19.970 align:start position:0% heard the term a few times like about code<01:37:17.159> completion<01:37:18.000> and<01:37:18.900> then<01:37:19.080> rolling<01:37:19.620> the<01:37:19.800> the 01:37:19.970 --> 01:37:19.980 align:start position:0% code completion and then rolling the the 01:37:19.980 --> 01:37:23.570 align:start position:0% code completion and then rolling the the change<01:37:20.480> and<01:37:21.480> that<01:37:21.960> we<01:37:22.199> are<01:37:22.440> very<01:37:23.100> slow<01:37:23.280> in<01:37:23.460> the 01:37:23.570 --> 01:37:23.580 align:start position:0% change and that we are very slow in the 01:37:23.580 --> 01:37:25.250 align:start position:0% change and that we are very slow in the second<01:37:23.760> part<01:37:23.940> but<01:37:24.239> you<01:37:24.420> know<01:37:24.540> I<01:37:24.719> I<01:37:24.840> joined 01:37:25.250 --> 01:37:25.260 align:start position:0% second part but you know I I joined 01:37:25.260 --> 01:37:28.070 align:start position:0% second part but you know I I joined right<01:37:25.500> yeah<01:37:25.739> I'm<01:37:25.920> I'm<01:37:26.219> a<01:37:26.699> new<01:37:26.820> guy<01:37:27.060> but<01:37:27.659> what<01:37:27.960> I 01:37:28.070 --> 01:37:28.080 align:start position:0% right yeah I'm I'm a new guy but what I 01:37:28.080 --> 01:37:31.450 align:start position:0% right yeah I'm I'm a new guy but what I observed<01:37:28.440> with<01:37:28.560> the<01:37:28.739> merge<01:37:29.159> we<01:37:29.600> we<01:37:30.600> shift 01:37:31.450 --> 01:37:31.460 align:start position:0% observed with the merge we we shift 01:37:31.460 --> 01:37:35.209 align:start position:0% observed with the merge we we shift shift<01:37:32.460> in<01:37:32.880> middle<01:37:33.480> of<01:37:33.719> September<01:37:34.199> but<01:37:34.860> what<01:37:35.100> I 01:37:35.209 --> 01:37:35.219 align:start position:0% shift in middle of September but what I 01:37:35.219 --> 01:37:36.229 align:start position:0% shift in middle of September but what I observed 01:37:36.229 --> 01:37:36.239 align:start position:0% observed 01:37:36.239 --> 01:37:39.169 align:start position:0% observed flag<01:37:36.900> from<01:37:37.320> my<01:37:37.500> the<01:37:37.800> definition<01:37:37.980> I<01:37:38.460> know<01:37:38.639> the 01:37:39.169 --> 01:37:39.179 align:start position:0% flag from my the definition I know the 01:37:39.179 --> 01:37:42.229 align:start position:0% flag from my the definition I know the code<01:37:39.360> was<01:37:39.659> not<01:37:39.840> completed<01:37:40.260> in<01:37:40.800> August<01:37:41.460> and 01:37:42.229 --> 01:37:42.239 align:start position:0% code was not completed in August and 01:37:42.239 --> 01:37:43.729 align:start position:0% code was not completed in August and some<01:37:42.420> teams<01:37:42.719> were<01:37:42.840> like 01:37:43.729 --> 01:37:43.739 align:start position:0% some teams were like 01:37:43.739 --> 01:37:46.430 align:start position:0% some teams were like pushing<01:37:44.460> the<01:37:44.639> changes<01:37:45.000> at<01:37:45.239> the<01:37:45.360> very<01:37:45.480> end<01:37:45.719> and 01:37:46.430 --> 01:37:46.440 align:start position:0% pushing the changes at the very end and 01:37:46.440 --> 01:37:48.649 align:start position:0% pushing the changes at the very end and for<01:37:46.679> me<01:37:46.860> like<01:37:47.219> when<01:37:47.699> you<01:37:47.820> say<01:37:47.940> that<01:37:48.120> code<01:37:48.420> is 01:37:48.649 --> 01:37:48.659 align:start position:0% for me like when you say that code is 01:37:48.659 --> 01:37:50.689 align:start position:0% for me like when you say that code is completed<01:37:49.020> you<01:37:49.620> know<01:37:49.800> you 01:37:50.689 --> 01:37:50.699 align:start position:0% completed you know you 01:37:50.699 --> 01:37:53.030 align:start position:0% completed you know you you've<01:37:51.300> been<01:37:51.480> testing<01:37:51.960> you<01:37:52.500> start<01:37:52.620> testing 01:37:53.030 --> 01:37:53.040 align:start position:0% you've been testing you start testing 01:37:53.040 --> 01:37:55.070 align:start position:0% you've been testing you start testing and<01:37:53.340> you<01:37:53.520> don't<01:37:53.760> introduce<01:37:54.179> new<01:37:54.420> changes<01:37:54.900> yeah 01:37:55.070 --> 01:37:55.080 align:start position:0% and you don't introduce new changes yeah 01:37:55.080 --> 01:37:57.709 align:start position:0% and you don't introduce new changes yeah so<01:37:55.500> the<01:37:55.679> code<01:37:55.800> is<01:37:56.040> stable<01:37:56.340> so 01:37:57.709 --> 01:37:57.719 align:start position:0% so the code is stable so 01:37:57.719 --> 01:37:59.209 align:start position:0% so the code is stable so it<01:37:58.139> looked<01:37:58.320> a<01:37:58.380> bit<01:37:58.500> different<01:37:58.679> from<01:37:59.040> my 01:37:59.209 --> 01:37:59.219 align:start position:0% it looked a bit different from my 01:37:59.219 --> 01:38:01.430 align:start position:0% it looked a bit different from my perspective<01:37:59.699> yeah<01:38:00.179> I<01:38:00.480> agree<01:38:00.659> the<01:38:00.900> merge<01:38:01.260> was 01:38:01.430 --> 01:38:01.440 align:start position:0% perspective yeah I agree the merge was 01:38:01.440 --> 01:38:03.169 align:start position:0% perspective yeah I agree the merge was not<01:38:01.620> a<01:38:01.800> case<01:38:01.920> where<01:38:02.159> we<01:38:02.280> were<01:38:02.460> called<01:38:02.639> complete 01:38:03.169 --> 01:38:03.179 align:start position:0% not a case where we were called complete 01:38:03.179 --> 01:38:04.910 align:start position:0% not a case where we were called complete three<01:38:03.360> months<01:38:03.659> before 01:38:04.910 --> 01:38:04.920 align:start position:0% three months before 01:38:04.920 --> 01:38:06.950 align:start position:0% three months before um<01:38:05.040> so<01:38:05.400> yeah<01:38:05.699> but<01:38:06.000> but<01:38:06.179> we<01:38:06.600> have<01:38:06.659> done<01:38:06.840> that 01:38:06.950 --> 01:38:06.960 align:start position:0% um so yeah but but we have done that 01:38:06.960 --> 01:38:08.750 align:start position:0% um so yeah but but we have done that before<01:38:07.139> right<01:38:07.440> like<01:38:07.620> and<01:38:07.920> and<01:38:08.100> you<01:38:08.400> know<01:38:08.460> again 01:38:08.750 --> 01:38:08.760 align:start position:0% before right like and and you know again 01:38:08.760 --> 01:38:10.250 align:start position:0% before right like and and you know again I<01:38:09.000> think<01:38:09.120> burden<01:38:09.420> London<01:38:09.780> was<01:38:09.960> like<01:38:10.080> a<01:38:10.199> good 01:38:10.250 --> 01:38:10.260 align:start position:0% I think burden London was like a good 01:38:10.260 --> 01:38:11.750 align:start position:0% I think burden London was like a good example<01:38:10.560> as<01:38:10.860> soon<01:38:11.040> as<01:38:11.100> we<01:38:11.280> were<01:38:11.400> kind<01:38:11.580> of<01:38:11.639> code 01:38:11.750 --> 01:38:11.760 align:start position:0% example as soon as we were kind of code 01:38:11.760 --> 01:38:13.729 align:start position:0% example as soon as we were kind of code complete<01:38:12.179> on<01:38:12.300> burden<01:38:12.659> we<01:38:13.080> started<01:38:13.380> working<01:38:13.500> on 01:38:13.729 --> 01:38:13.739 align:start position:0% complete on burden we started working on 01:38:13.739 --> 01:38:15.770 align:start position:0% complete on burden we started working on London<01:38:14.159> before<01:38:14.340> like<01:38:14.699> it<01:38:14.880> shipped<01:38:15.239> and<01:38:15.659> part 01:38:15.770 --> 01:38:15.780 align:start position:0% London before like it shipped and part 01:38:15.780 --> 01:38:17.390 align:start position:0% London before like it shipped and part of<01:38:15.960> the<01:38:16.020> reason<01:38:16.199> for<01:38:16.560> that<01:38:16.679> three-month<01:38:17.219> delay 01:38:17.390 --> 01:38:17.400 align:start position:0% of the reason for that three-month delay 01:38:17.400 --> 01:38:18.890 align:start position:0% of the reason for that three-month delay is<01:38:17.760> not<01:38:17.940> like<01:38:18.060> for<01:38:18.239> the<01:38:18.360> client<01:38:18.540> teams<01:38:18.780> it's 01:38:18.890 --> 01:38:18.900 align:start position:0% is not like for the client teams it's 01:38:18.900 --> 01:38:20.209 align:start position:0% is not like for the client teams it's for<01:38:19.020> like<01:38:19.139> everyone<01:38:19.320> running<01:38:19.620> your<01:38:19.860> node<01:38:20.040> like 01:38:20.209 --> 01:38:20.219 align:start position:0% for like everyone running your node like 01:38:20.219 --> 01:38:22.010 align:start position:0% for like everyone running your node like folks<01:38:20.460> like<01:38:20.580> coinbase<01:38:21.000> because<01:38:21.420> usually<01:38:21.780> like 01:38:22.010 --> 01:38:22.020 align:start position:0% folks like coinbase because usually like 01:38:22.020 --> 01:38:24.530 align:start position:0% folks like coinbase because usually like people<01:38:22.280> like<01:38:23.280> and<01:38:23.520> not<01:38:23.760> the<01:38:23.880> coinbase<01:38:24.420> here 01:38:24.530 --> 01:38:24.540 align:start position:0% people like and not the coinbase here 01:38:24.540 --> 01:38:26.450 align:start position:0% people like and not the coinbase here like<01:38:24.900> people<01:38:25.139> just<01:38:25.500> don't<01:38:25.739> care<01:38:25.920> about<01:38:26.280> the 01:38:26.450 --> 01:38:26.460 align:start position:0% like people just don't care about the 01:38:26.460 --> 01:38:28.010 align:start position:0% like people just don't care about the hard<01:38:26.580> Forks<01:38:27.000> until<01:38:27.179> they're<01:38:27.540> like<01:38:27.659> announced 01:38:28.010 --> 01:38:28.020 align:start position:0% hard Forks until they're like announced 01:38:28.020 --> 01:38:30.830 align:start position:0% hard Forks until they're like announced on<01:38:28.139> a<01:38:28.320> blog<01:38:28.560> post<01:38:28.620> on<01:38:28.920> blog.etherium.org 01:38:30.830 --> 01:38:30.840 align:start position:0% on a blog post on blog.etherium.org 01:38:30.840 --> 01:38:32.270 align:start position:0% on a blog post on blog.etherium.org um and<01:38:31.080> then<01:38:31.139> they're<01:38:31.260> like<01:38:31.380> holy<01:38:31.860> and 01:38:32.270 --> 01:38:32.280 align:start position:0% um and then they're like holy and 01:38:32.280 --> 01:38:33.530 align:start position:0% um and then they're like holy and then<01:38:32.400> they<01:38:32.639> like<01:38:32.880> message<01:38:33.060> me<01:38:33.300> and<01:38:33.420> they're 01:38:33.530 --> 01:38:33.540 align:start position:0% then they like message me and they're 01:38:33.540 --> 01:38:34.910 align:start position:0% then they like message me and they're like<01:38:33.659> oh<01:38:33.780> my<01:38:33.840> God<01:38:33.960> we<01:38:34.199> need<01:38:34.380> to<01:38:34.440> like<01:38:34.620> upgrade 01:38:34.910 --> 01:38:34.920 align:start position:0% like oh my God we need to like upgrade 01:38:34.920 --> 01:38:37.010 align:start position:0% like oh my God we need to like upgrade all<01:38:35.100> our<01:38:35.280> infrastructure<01:38:35.820> and<01:38:36.060> you<01:38:36.420> know<01:38:36.480> and 01:38:37.010 --> 01:38:37.020 align:start position:0% all our infrastructure and you know and 01:38:37.020 --> 01:38:38.750 align:start position:0% all our infrastructure and you know and especially<01:38:37.380> so<01:38:37.679> if<01:38:37.920> like<01:38:38.100> it's<01:38:38.280> a<01:38:38.460> complicated 01:38:38.750 --> 01:38:38.760 align:start position:0% especially so if like it's a complicated 01:38:38.760 --> 01:38:40.189 align:start position:0% especially so if like it's a complicated hard<01:38:39.000> Fork<01:38:39.300> if<01:38:39.420> it's<01:38:39.540> just<01:38:39.659> like<01:38:39.780> introducing 01:38:40.189 --> 01:38:40.199 align:start position:0% hard Fork if it's just like introducing 01:38:40.199 --> 01:38:41.629 align:start position:0% hard Fork if it's just like introducing a<01:38:40.380> new<01:38:40.500> OP<01:38:40.620> code 01:38:41.629 --> 01:38:41.639 align:start position:0% a new OP code 01:38:41.639 --> 01:38:42.890 align:start position:0% a new OP code um<01:38:41.699> they<01:38:41.880> need<01:38:42.060> to<01:38:42.120> upgrade<01:38:42.360> their<01:38:42.480> notes<01:38:42.780> and 01:38:42.890 --> 01:38:42.900 align:start position:0% um they need to upgrade their notes and 01:38:42.900 --> 01:38:44.330 align:start position:0% um they need to upgrade their notes and still<01:38:43.080> sometimes<01:38:43.440> you<01:38:43.679> know<01:38:43.800> they're<01:38:44.040> like<01:38:44.159> oh 01:38:44.330 --> 01:38:44.340 align:start position:0% still sometimes you know they're like oh 01:38:44.340 --> 01:38:45.649 align:start position:0% still sometimes you know they're like oh we<01:38:44.520> need<01:38:44.639> like<01:38:44.760> two<01:38:44.880> months<01:38:45.060> to<01:38:45.179> do<01:38:45.300> that<01:38:45.420> or 01:38:45.649 --> 01:38:45.659 align:start position:0% we need like two months to do that or 01:38:45.659 --> 01:38:48.229 align:start position:0% we need like two months to do that or something<01:38:45.780> so<01:38:46.440> it's<01:38:46.980> it's<01:38:47.219> worth<01:38:47.460> noting<01:38:47.940> like 01:38:48.229 --> 01:38:48.239 align:start position:0% something so it's it's worth noting like 01:38:48.239 --> 01:38:51.110 align:start position:0% something so it's it's worth noting like we<01:38:49.020> can<01:38:49.260> set<01:38:49.980> our<01:38:50.219> schedules<01:38:50.639> somewhat 01:38:51.110 --> 01:38:51.120 align:start position:0% we can set our schedules somewhat 01:38:51.120 --> 01:38:52.910 align:start position:0% we can set our schedules somewhat independently<01:38:51.960> of<01:38:52.380> like<01:38:52.560> the<01:38:52.739> release 01:38:52.910 --> 01:38:52.920 align:start position:0% independently of like the release 01:38:52.920 --> 01:38:54.050 align:start position:0% independently of like the release schedule 01:38:54.050 --> 01:38:54.060 align:start position:0% schedule 01:38:54.060 --> 01:38:55.550 align:start position:0% schedule um<01:38:54.120> but<01:38:54.360> that<01:38:54.540> doesn't<01:38:54.719> necessarily<01:38:55.199> mean<01:38:55.380> you 01:38:55.550 --> 01:38:55.560 align:start position:0% um but that doesn't necessarily mean you 01:38:55.560 --> 01:38:57.410 align:start position:0% um but that doesn't necessarily mean you want<01:38:55.739> to<01:38:55.860> like<01:38:55.980> do<01:38:56.520> cold<01:38:56.820> complete<01:38:57.179> and<01:38:57.239> ship 01:38:57.410 --> 01:38:57.420 align:start position:0% want to like do cold complete and ship 01:38:57.420 --> 01:38:59.510 align:start position:0% want to like do cold complete and ship two<01:38:57.540> weeks<01:38:57.659> later<01:38:58.139> because<01:38:58.620> there's<01:38:59.340> still 01:38:59.510 --> 01:38:59.520 align:start position:0% two weeks later because there's still 01:38:59.520 --> 01:39:01.189 align:start position:0% two weeks later because there's still value<01:38:59.699> in<01:38:59.940> giving<01:39:00.120> people<01:39:00.360> time<01:39:00.659> to<01:39:00.840> upgrade 01:39:01.189 --> 01:39:01.199 align:start position:0% value in giving people time to upgrade 01:39:01.199 --> 01:39:03.229 align:start position:0% value in giving people time to upgrade and<01:39:01.739> I<01:39:01.920> I<01:39:02.100> would<01:39:02.280> also<01:39:02.460> argue<01:39:02.699> the<01:39:02.820> merge<01:39:03.060> was 01:39:03.229 --> 01:39:03.239 align:start position:0% and I I would also argue the merge was 01:39:03.239 --> 01:39:04.910 align:start position:0% and I I would also argue the merge was like<01:39:03.300> cutting<01:39:03.600> it<01:39:03.780> close<01:39:03.960> and 01:39:04.910 --> 01:39:04.920 align:start position:0% like cutting it close and 01:39:04.920 --> 01:39:05.629 align:start position:0% like cutting it close and um 01:39:05.629 --> 01:39:05.639 align:start position:0% um 01:39:05.639 --> 01:39:07.310 align:start position:0% um I<01:39:06.000> think<01:39:06.120> you<01:39:06.300> know<01:39:06.360> the<01:39:06.600> merger's<01:39:07.020> like<01:39:07.080> a<01:39:07.199> big 01:39:07.310 --> 01:39:07.320 align:start position:0% I think you know the merger's like a big 01:39:07.320 --> 01:39:08.930 align:start position:0% I think you know the merger's like a big change<01:39:07.440> the<01:39:07.739> environment<01:39:08.100> bits<01:39:08.520> the<01:39:08.760> like 01:39:08.930 --> 01:39:08.940 align:start position:0% change the environment bits the like 01:39:08.940 --> 01:39:10.910 align:start position:0% change the environment bits the like proof<01:39:09.480> of<01:39:09.540> statements<01:39:09.960> so<01:39:10.080> I<01:39:10.199> think<01:39:10.380> there<01:39:10.739> was 01:39:10.910 --> 01:39:10.920 align:start position:0% proof of statements so I think there was 01:39:10.920 --> 01:39:13.250 align:start position:0% proof of statements so I think there was a<01:39:11.340> bunch<01:39:11.460> of<01:39:11.580> variables<01:39:12.000> in<01:39:12.120> that<01:39:12.300> one 01:39:13.250 --> 01:39:13.260 align:start position:0% a bunch of variables in that one 01:39:13.260 --> 01:39:14.810 align:start position:0% a bunch of variables in that one um<01:39:13.440> but<01:39:13.620> if<01:39:13.800> you<01:39:13.920> do<01:39:14.040> historically<01:39:14.460> we've<01:39:14.760> been 01:39:14.810 --> 01:39:14.820 align:start position:0% um but if you do historically we've been 01:39:14.820 --> 01:39:16.129 align:start position:0% um but if you do historically we've been like<01:39:15.000> kind<01:39:15.179> of<01:39:15.300> slow<01:39:15.420> but<01:39:15.659> I<01:39:15.780> think<01:39:15.900> that's 01:39:16.129 --> 01:39:16.139 align:start position:0% like kind of slow but I think that's 01:39:16.139 --> 01:39:18.950 align:start position:0% like kind of slow but I think that's that's<01:39:16.500> like<01:39:16.739> healthy<01:39:17.159> for<01:39:17.520> people<01:39:17.880> like<01:39:18.600> peop 01:39:18.950 --> 01:39:18.960 align:start position:0% that's like healthy for people like peop 01:39:18.960 --> 01:39:20.870 align:start position:0% that's like healthy for people like peop people<01:39:19.260> who<01:39:19.620> like<01:39:19.800> are<01:39:19.980> not<01:39:20.100> core<01:39:20.400> developers 01:39:20.870 --> 01:39:20.880 align:start position:0% people who like are not core developers 01:39:20.880 --> 01:39:22.010 align:start position:0% people who like are not core developers should<01:39:21.060> not<01:39:21.179> have<01:39:21.360> to<01:39:21.480> look<01:39:21.600> at<01:39:21.719> this<01:39:21.840> stuff 01:39:22.010 --> 01:39:22.020 align:start position:0% should not have to look at this stuff 01:39:22.020 --> 01:39:23.990 align:start position:0% should not have to look at this stuff every<01:39:22.320> day<01:39:22.560> to<01:39:22.980> know<01:39:23.159> like<01:39:23.400> is<01:39:23.580> there<01:39:23.699> a<01:39:23.820> hard 01:39:23.990 --> 01:39:24.000 align:start position:0% every day to know like is there a hard 01:39:24.000 --> 01:39:26.810 align:start position:0% every day to know like is there a hard fork<01:39:24.300> in<01:39:24.420> 10<01:39:24.600> days<01:39:24.840> right 01:39:26.810 --> 01:39:26.820 align:start position:0% fork in 10 days right 01:39:26.820 --> 01:39:30.050 align:start position:0% fork in 10 days right uh<01:39:27.420> diano<01:39:27.719> basal<01:39:28.199> maintainer<01:39:29.040> um<01:39:29.159> one<01:39:29.880> of<01:39:30.000> the 01:39:30.050 --> 01:39:30.060 align:start position:0% uh diano basal maintainer um one of the 01:39:30.060 --> 01:39:32.149 align:start position:0% uh diano basal maintainer um one of the ideas<01:39:30.179> that<01:39:30.540> you<01:39:30.659> you<01:39:30.900> sent<01:39:31.139> me<01:39:31.320> once<01:39:31.739> uh<01:39:32.040> Tim 01:39:32.149 --> 01:39:32.159 align:start position:0% ideas that you you sent me once uh Tim 01:39:32.159 --> 01:39:33.229 align:start position:0% ideas that you you sent me once uh Tim that<01:39:32.400> might<01:39:32.520> help<01:39:32.699> because<01:39:32.820> I'm<01:39:32.940> hearing<01:39:33.179> a 01:39:33.229 --> 01:39:33.239 align:start position:0% that might help because I'm hearing a 01:39:33.239 --> 01:39:34.910 align:start position:0% that might help because I'm hearing a lot<01:39:33.360> of<01:39:33.420> just<01:39:33.600> talk<01:39:33.840> about 01:39:34.910 --> 01:39:34.920 align:start position:0% lot of just talk about 01:39:34.920 --> 01:39:37.430 align:start position:0% lot of just talk about um<01:39:34.980> lots<01:39:35.699> of<01:39:35.760> bandwidth<01:39:36.300> Lots<01:39:36.719> needed<01:39:37.139> in<01:39:37.260> in 01:39:37.430 --> 01:39:37.440 align:start position:0% um lots of bandwidth Lots needed in in 01:39:37.440 --> 01:39:38.689 align:start position:0% um lots of bandwidth Lots needed in in the<01:39:37.620> layer<01:39:37.860> one 01:39:38.689 --> 01:39:38.699 align:start position:0% the layer one 01:39:38.699 --> 01:39:40.430 align:start position:0% the layer one um<01:39:38.760> what<01:39:38.940> if<01:39:39.060> we<01:39:39.300> prototype<01:39:40.020> some<01:39:40.199> of<01:39:40.320> our 01:39:40.430 --> 01:39:40.440 align:start position:0% um what if we prototype some of our 01:39:40.440 --> 01:39:42.770 align:start position:0% um what if we prototype some of our ideas<01:39:40.620> relating<01:39:41.580> to<01:39:41.760> things<01:39:41.940> like<01:39:42.120> evm<01:39:42.659> and 01:39:42.770 --> 01:39:42.780 align:start position:0% ideas relating to things like evm and 01:39:42.780 --> 01:39:45.110 align:start position:0% ideas relating to things like evm and transaction<01:39:43.080> formats<01:39:43.679> on<01:39:43.800> a<01:39:43.980> layer<01:39:44.219> two<01:39:44.400> and 01:39:45.110 --> 01:39:45.120 align:start position:0% transaction formats on a layer two and 01:39:45.120 --> 01:39:46.910 align:start position:0% transaction formats on a layer two and that<01:39:45.300> way<01:39:45.420> the<01:39:45.719> libraries<01:39:46.199> and<01:39:46.440> the<01:39:46.560> tooling 01:39:46.910 --> 01:39:46.920 align:start position:0% that way the libraries and the tooling 01:39:46.920 --> 01:39:48.830 align:start position:0% that way the libraries and the tooling could<01:39:47.400> adopt<01:39:47.699> to<01:39:47.820> that<01:39:47.940> on<01:39:48.060> the<01:39:48.179> layer<01:39:48.420> 2<01:39:48.540> stuff 01:39:48.830 --> 01:39:48.840 align:start position:0% could adopt to that on the layer 2 stuff 01:39:48.840 --> 01:39:51.350 align:start position:0% could adopt to that on the layer 2 stuff and<01:39:49.679> then<01:39:49.800> all<01:39:50.460> the<01:39:50.580> downstream<01:39:51.060> stuff<01:39:51.239> is 01:39:51.350 --> 01:39:51.360 align:start position:0% and then all the downstream stuff is 01:39:51.360 --> 01:39:53.330 align:start position:0% and then all the downstream stuff is ready<01:39:51.600> and<01:39:52.139> then<01:39:52.260> layer<01:39:52.620> one<01:39:52.739> can<01:39:52.980> implement 01:39:53.330 --> 01:39:53.340 align:start position:0% ready and then layer one can implement 01:39:53.340 --> 01:39:55.430 align:start position:0% ready and then layer one can implement it<01:39:53.520> when<01:39:53.760> they<01:39:53.940> have<01:39:54.060> the<01:39:54.239> bandwidth<01:39:55.260> um<01:39:55.260> and 01:39:55.430 --> 01:39:55.440 align:start position:0% it when they have the bandwidth um and 01:39:55.440 --> 01:39:56.930 align:start position:0% it when they have the bandwidth um and not<01:39:55.620> having<01:39:55.739> to<01:39:55.980> rush<01:39:56.219> in<01:39:56.340> and<01:39:56.460> get<01:39:56.580> those<01:39:56.699> in 01:39:56.930 --> 01:39:56.940 align:start position:0% not having to rush in and get those in 01:39:56.940 --> 01:39:59.270 align:start position:0% not having to rush in and get those in so<01:39:57.179> you<01:39:57.300> can<01:39:57.420> get<01:39:57.659> cool<01:39:58.260> things<01:39:58.440> like<01:39:58.679> BLS 01:39:59.270 --> 01:39:59.280 align:start position:0% so you can get cool things like BLS 01:39:59.280 --> 01:40:01.610 align:start position:0% so you can get cool things like BLS transaction<01:39:59.699> formats<01:40:00.360> sooner<01:40:00.659> rather<01:40:01.380> than 01:40:01.610 --> 01:40:01.620 align:start position:0% transaction formats sooner rather than 01:40:01.620 --> 01:40:05.590 align:start position:0% transaction formats sooner rather than in<01:40:01.800> 2024<01:40:02.400> or<01:40:02.580> 2025. 01:40:05.590 --> 01:40:05.600 align:start position:0% 01:40:05.600 --> 01:40:09.530 align:start position:0% I<01:40:06.600> really<01:40:07.440> do<01:40:07.800> like<01:40:08.040> the<01:40:08.219> idea<01:40:08.580> at<01:40:09.239> the<01:40:09.360> same 01:40:09.530 --> 01:40:09.540 align:start position:0% I really do like the idea at the same 01:40:09.540 --> 01:40:12.709 align:start position:0% I really do like the idea at the same time<01:40:09.860> via<01:40:10.860> Slayer<01:40:11.219> 2<01:40:11.340> optimism<01:40:11.880> especially 01:40:12.709 --> 01:40:12.719 align:start position:0% time via Slayer 2 optimism especially 01:40:12.719 --> 01:40:15.470 align:start position:0% time via Slayer 2 optimism especially we're<01:40:13.679> trying<01:40:13.980> not<01:40:14.400> to<01:40:14.699> stray<01:40:15.060> away<01:40:15.179> from 01:40:15.470 --> 01:40:15.480 align:start position:0% we're trying not to stray away from 01:40:15.480 --> 01:40:17.750 align:start position:0% we're trying not to stray away from layer<01:40:15.780> 1<01:40:15.900> where<01:40:16.560> we<01:40:16.679> create<01:40:16.860> conflicts<01:40:17.580> in 01:40:17.750 --> 01:40:17.760 align:start position:0% layer 1 where we create conflicts in 01:40:17.760 --> 01:40:20.570 align:start position:0% layer 1 where we create conflicts in development<01:40:18.380> we<01:40:19.380> are<01:40:19.560> literally<01:40:19.860> just<01:40:20.219> trying 01:40:20.570 --> 01:40:20.580 align:start position:0% development we are literally just trying 01:40:20.580 --> 01:40:23.450 align:start position:0% development we are literally just trying to<01:40:20.820> if<01:40:21.239> we<01:40:21.420> could<01:40:21.600> we<01:40:22.260> would<01:40:22.440> run<01:40:22.679> GAF<01:40:23.040> without 01:40:23.450 --> 01:40:23.460 align:start position:0% to if we could we would run GAF without 01:40:23.460 --> 01:40:25.729 align:start position:0% to if we could we would run GAF without modifications<01:40:24.239> we<01:40:25.020> don't<01:40:25.199> want<01:40:25.320> to<01:40:25.620> be 01:40:25.729 --> 01:40:25.739 align:start position:0% modifications we don't want to be 01:40:25.739 --> 01:40:26.510 align:start position:0% modifications we don't want to be different 01:40:26.510 --> 01:40:26.520 align:start position:0% different 01:40:26.520 --> 01:40:30.709 align:start position:0% different and<01:40:27.380> often<01:40:28.380> I<01:40:28.860> just<01:40:29.100> like<01:40:29.460> client<01:40:30.360> teams 01:40:30.709 --> 01:40:30.719 align:start position:0% and often I just like client teams 01:40:30.719 --> 01:40:32.689 align:start position:0% and often I just like client teams they're<01:40:30.900> one<01:40:31.139> developers<01:40:31.679> to<01:40:32.400> be<01:40:32.520> more 01:40:32.689 --> 01:40:32.699 align:start position:0% they're one developers to be more 01:40:32.699 --> 01:40:35.810 align:start position:0% they're one developers to be more receptive<01:40:33.239> towards<01:40:33.920> changes<01:40:34.920> but<01:40:35.520> also 01:40:35.810 --> 01:40:35.820 align:start position:0% receptive towards changes but also 01:40:35.820 --> 01:40:38.149 align:start position:0% receptive towards changes but also testing<01:40:36.179> and<01:40:36.360> like<01:40:36.600> creating<01:40:37.080> confidence<01:40:37.560> in 01:40:38.149 --> 01:40:38.159 align:start position:0% testing and like creating confidence in 01:40:38.159 --> 01:40:40.010 align:start position:0% testing and like creating confidence in these<01:40:38.400> changes 01:40:40.010 --> 01:40:40.020 align:start position:0% these changes 01:40:40.020 --> 01:40:42.530 align:start position:0% these changes as<01:40:40.679> there<01:40:41.040> to<01:40:41.280> authorize 01:40:42.530 --> 01:40:42.540 align:start position:0% as there to authorize 01:40:42.540 --> 01:40:44.629 align:start position:0% as there to authorize you<01:40:43.020> get<01:40:43.139> this<01:40:43.260> conflict<01:40:43.560> of<01:40:43.739> interest<01:40:43.920> where 01:40:44.629 --> 01:40:44.639 align:start position:0% you get this conflict of interest where 01:40:44.639 --> 01:40:46.370 align:start position:0% you get this conflict of interest where okay<01:40:45.120> you<01:40:45.360> want<01:40:45.480> to<01:40:45.600> make<01:40:45.659> the<01:40:45.840> change<01:40:46.020> to<01:40:46.199> be 01:40:46.370 --> 01:40:46.380 align:start position:0% okay you want to make the change to be 01:40:46.380 --> 01:40:48.490 align:start position:0% okay you want to make the change to be special<01:40:46.560> on<01:40:46.920> new<01:40:47.159> and<01:40:47.520> exciting<01:40:48.060> and<01:40:48.300> cheap 01:40:48.490 --> 01:40:48.500 align:start position:0% special on new and exciting and cheap 01:40:48.500 --> 01:40:52.370 align:start position:0% special on new and exciting and cheap but<01:40:49.500> you<01:40:49.800> you're<01:40:50.280> not<01:40:50.639> shipping<01:40:51.300> the<01:40:52.020> ethereum 01:40:52.370 --> 01:40:52.380 align:start position:0% but you you're not shipping the ethereum 01:40:52.380 --> 01:40:54.290 align:start position:0% but you you're not shipping the ethereum dream 01:40:54.290 --> 01:40:54.300 align:start position:0% dream 01:40:54.300 --> 01:40:56.870 align:start position:0% dream yes 01:40:56.870 --> 01:40:56.880 align:start position:0% yes 01:40:56.880 --> 01:40:59.149 align:start position:0% yes like<01:40:57.420> and<01:40:58.020> especially<01:40:58.320> data<01:40:58.800> availability 01:40:59.149 --> 01:40:59.159 align:start position:0% like and especially data availability 01:40:59.159 --> 01:41:02.090 align:start position:0% like and especially data availability like<01:40:59.460> foreign<01:41:00.260> we<01:41:01.260> can't<01:41:01.380> even<01:41:01.560> ship<01:41:01.860> it<01:41:01.980> on 01:41:02.090 --> 01:41:02.100 align:start position:0% like foreign we can't even ship it on 01:41:02.100 --> 01:41:04.729 align:start position:0% like foreign we can't even ship it on Layer<01:41:02.400> Two<01:41:02.520> every<01:41:02.880> like<01:41:03.360> we<01:41:03.600> created<01:41:04.139> layer 01:41:04.729 --> 01:41:04.739 align:start position:0% Layer Two every like we created layer 01:41:04.739 --> 01:41:06.890 align:start position:0% Layer Two every like we created layer three<01:41:04.860> situation<01:41:05.400> with<01:41:06.060> a<01:41:06.300> much<01:41:06.420> much<01:41:06.600> smaller 01:41:06.890 --> 01:41:06.900 align:start position:0% three situation with a much much smaller 01:41:06.900 --> 01:41:11.930 align:start position:0% three situation with a much much smaller validator<01:41:07.380> sound 01:41:11.930 --> 01:41:11.940 align:start position:0% 01:41:11.940 --> 01:41:13.970 align:start position:0% when<01:41:12.420> we<01:41:12.540> go<01:41:12.659> through<01:41:12.840> that<01:41:13.020> big<01:41:13.199> list<01:41:13.440> of<01:41:13.739> uh 01:41:13.970 --> 01:41:13.980 align:start position:0% when we go through that big list of uh 01:41:13.980 --> 01:41:15.770 align:start position:0% when we go through that big list of uh proposed<01:41:14.400> EIP<01:41:14.699> stuff<01:41:15.060> that's<01:41:15.239> coming<01:41:15.420> up<01:41:15.600> in 01:41:15.770 --> 01:41:15.780 align:start position:0% proposed EIP stuff that's coming up in 01:41:15.780 --> 01:41:17.750 align:start position:0% proposed EIP stuff that's coming up in the<01:41:15.960> next<01:41:16.080> thing<01:41:16.380> like<01:41:17.040> half<01:41:17.340> of<01:41:17.520> them<01:41:17.639> are 01:41:17.750 --> 01:41:17.760 align:start position:0% the next thing like half of them are 01:41:17.760 --> 01:41:20.090 align:start position:0% the next thing like half of them are just<01:41:17.940> evm<01:41:18.420> stuff<01:41:18.659> and<01:41:19.260> that<01:41:19.380> stuff<01:41:19.560> is<01:41:19.739> easy<01:41:19.920> to 01:41:20.090 --> 01:41:20.100 align:start position:0% just evm stuff and that stuff is easy to 01:41:20.100 --> 01:41:21.110 align:start position:0% just evm stuff and that stuff is easy to push<01:41:20.219> through<01:41:20.340> but<01:41:20.520> then<01:41:20.580> you<01:41:20.699> get<01:41:20.820> into<01:41:20.940> the 01:41:21.110 --> 01:41:21.120 align:start position:0% push through but then you get into the 01:41:21.120 --> 01:41:23.330 align:start position:0% push through but then you get into the situation<01:41:21.480> like<01:41:22.260> we<01:41:22.440> had<01:41:22.560> with<01:41:22.800> subroutines 01:41:23.330 --> 01:41:23.340 align:start position:0% situation like we had with subroutines 01:41:23.340 --> 01:41:25.010 align:start position:0% situation like we had with subroutines where<01:41:23.880> it<01:41:24.060> was<01:41:24.120> implemented<01:41:24.540> it<01:41:24.659> was<01:41:24.780> ready 01:41:25.010 --> 01:41:25.020 align:start position:0% where it was implemented it was ready 01:41:25.020 --> 01:41:27.290 align:start position:0% where it was implemented it was ready and<01:41:25.739> then<01:41:25.860> the<01:41:26.100> week<01:41:26.280> before<01:41:26.460> the<01:41:26.940> first<01:41:27.060> test 01:41:27.290 --> 01:41:27.300 align:start position:0% and then the week before the first test 01:41:27.300 --> 01:41:29.689 align:start position:0% and then the week before the first test net<01:41:27.540> all<01:41:27.780> of<01:41:27.900> a<01:41:27.960> sudden<01:41:28.020> it<01:41:28.139> gets<01:41:28.380> ripped<01:41:28.739> out<01:41:28.860> I 01:41:29.689 --> 01:41:29.699 align:start position:0% net all of a sudden it gets ripped out I 01:41:29.699 --> 01:41:31.729 align:start position:0% net all of a sudden it gets ripped out I mean<01:41:29.820> I<01:41:30.239> I<01:41:30.360> like<01:41:30.540> the<01:41:30.719> idea<01:41:30.960> but<01:41:31.139> your<01:41:31.380> voice<01:41:31.560> in 01:41:31.729 --> 01:41:31.739 align:start position:0% mean I I like the idea but your voice in 01:41:31.739 --> 01:41:33.110 align:start position:0% mean I I like the idea but your voice in the<01:41:31.800> exact<01:41:31.980> concern<01:41:32.280> how<01:41:32.699> do<01:41:32.820> we<01:41:32.940> get<01:41:33.000> the 01:41:33.110 --> 01:41:33.120 align:start position:0% the exact concern how do we get the 01:41:33.120 --> 01:41:34.430 align:start position:0% the exact concern how do we get the commitment<01:41:33.420> that<01:41:33.600> if<01:41:33.719> it's<01:41:33.840> done<01:41:34.080> it<01:41:34.320> will 01:41:34.430 --> 01:41:34.440 align:start position:0% commitment that if it's done it will 01:41:34.440 --> 01:41:36.590 align:start position:0% commitment that if it's done it will ship<01:41:34.679> on<01:41:34.860> layer<01:41:35.219> one<01:41:35.340> without<01:41:35.880> substantial 01:41:36.590 --> 01:41:36.600 align:start position:0% ship on layer one without substantial 01:41:36.600 --> 01:41:38.270 align:start position:0% ship on layer one without substantial change<01:41:36.780> because<01:41:37.020> then<01:41:37.380> if<01:41:37.860> you<01:41:37.980> have<01:41:38.100> these 01:41:38.270 --> 01:41:38.280 align:start position:0% change because then if you have these 01:41:38.280 --> 01:41:39.950 align:start position:0% change because then if you have these changes<01:41:38.580> on<01:41:38.760> Layer<01:41:39.000> Two<01:41:39.179> and<01:41:39.659> they<01:41:39.840> change 01:41:39.950 --> 01:41:39.960 align:start position:0% changes on Layer Two and they change 01:41:39.960 --> 01:41:41.810 align:start position:0% changes on Layer Two and they change substantially<01:41:40.560> then<01:41:41.100> it's<01:41:41.280> a<01:41:41.400> burden<01:41:41.580> on<01:41:41.699> the 01:41:41.810 --> 01:41:41.820 align:start position:0% substantially then it's a burden on the 01:41:41.820 --> 01:41:43.609 align:start position:0% substantially then it's a burden on the layer<01:41:42.060> 2<01:41:42.119> Chain<01:41:42.360> if<01:41:42.540> they<01:41:42.659> put<01:41:42.780> it<01:41:42.900> on<01:41:43.080> on<01:41:43.380> one 01:41:43.609 --> 01:41:43.619 align:start position:0% layer 2 Chain if they put it on on one 01:41:43.619 --> 01:41:45.109 align:start position:0% layer 2 Chain if they put it on on one of<01:41:43.739> their<01:41:43.860> Premier<01:41:44.219> chains<01:41:44.639> rather<01:41:44.880> than<01:41:45.000> on 01:41:45.109 --> 01:41:45.119 align:start position:0% of their Premier chains rather than on 01:41:45.119 --> 01:41:47.570 align:start position:0% of their Premier chains rather than on testnet 01:41:47.570 --> 01:41:47.580 align:start position:0% testnet 01:41:47.580 --> 01:41:50.209 align:start position:0% testnet so<01:41:48.300> one<01:41:48.600> thing<01:41:48.900> to<01:41:49.320> answer<01:41:49.500> here<01:41:49.800> is<01:41:49.980> that<01:41:50.100> I 01:41:50.209 --> 01:41:50.219 align:start position:0% so one thing to answer here is that I 01:41:50.219 --> 01:41:51.590 align:start position:0% so one thing to answer here is that I think<01:41:50.340> it's<01:41:50.580> very 01:41:51.590 --> 01:41:51.600 align:start position:0% think it's very 01:41:51.600 --> 01:41:54.169 align:start position:0% think it's very from<01:41:52.080> the<01:41:52.260> outside<01:41:52.380> it<01:41:53.400> it's<01:41:53.639> a<01:41:53.880> bit<01:41:53.940> strange 01:41:54.169 --> 01:41:54.179 align:start position:0% from the outside it it's a bit strange 01:41:54.179 --> 01:41:55.970 align:start position:0% from the outside it it's a bit strange because<01:41:54.480> it<01:41:54.840> kind<01:41:54.960> of<01:41:55.080> looks<01:41:55.380> like<01:41:55.500> there<01:41:55.800> is 01:41:55.970 --> 01:41:55.980 align:start position:0% because it kind of looks like there is 01:41:55.980 --> 01:41:58.189 align:start position:0% because it kind of looks like there is commitment<01:41:56.400> to<01:41:56.639> go<01:41:56.760> with<01:41:56.880> an<01:41:57.060> EIP<01:41:57.360> and<01:41:58.020> in 01:41:58.189 --> 01:41:58.199 align:start position:0% commitment to go with an EIP and in 01:41:58.199 --> 01:41:59.510 align:start position:0% commitment to go with an EIP and in reality<01:41:58.560> what<01:41:58.800> at<01:41:59.040> least<01:41:59.159> what<01:41:59.340> I've 01:41:59.510 --> 01:41:59.520 align:start position:0% reality what at least what I've 01:41:59.520 --> 01:42:01.910 align:start position:0% reality what at least what I've experienced<01:42:00.000> is<01:42:00.360> that<01:42:00.659> most<01:42:01.260> layer<01:42:01.619> one<01:42:01.739> most 01:42:01.910 --> 01:42:01.920 align:start position:0% experienced is that most layer one most 01:42:01.920 --> 01:42:04.129 align:start position:0% experienced is that most layer one most execution<01:42:02.400> clients<01:42:02.940> won't<01:42:03.420> even<01:42:03.659> touch<01:42:03.960> any 01:42:04.129 --> 01:42:04.139 align:start position:0% execution clients won't even touch any 01:42:04.139 --> 01:42:05.570 align:start position:0% execution clients won't even touch any IP<01:42:04.560> until<01:42:04.739> somebody<01:42:05.100> else<01:42:05.340> actually 01:42:05.570 --> 01:42:05.580 align:start position:0% IP until somebody else actually 01:42:05.580 --> 01:42:07.609 align:start position:0% IP until somebody else actually implements<01:42:06.239> it<01:42:06.360> and<01:42:06.840> verifies<01:42:07.320> that<01:42:07.500> it's 01:42:07.609 --> 01:42:07.619 align:start position:0% implements it and verifies that it's 01:42:07.619 --> 01:42:10.729 align:start position:0% implements it and verifies that it's correct<01:42:08.460> so<01:42:08.880> usually<01:42:09.239> you<01:42:10.199> have<01:42:10.320> the<01:42:10.440> EIP 01:42:10.729 --> 01:42:10.739 align:start position:0% correct so usually you have the EIP 01:42:10.739 --> 01:42:12.890 align:start position:0% correct so usually you have the EIP authors<01:42:11.280> which<01:42:11.520> kind<01:42:11.760> of<01:42:11.880> has<01:42:12.119> to<01:42:12.239> beg<01:42:12.659> one<01:42:12.780> of 01:42:12.890 --> 01:42:12.900 align:start position:0% authors which kind of has to beg one of 01:42:12.900 --> 01:42:15.590 align:start position:0% authors which kind of has to beg one of the<01:42:13.020> clients<01:42:13.380> to<01:42:13.679> please<01:42:13.860> implement<01:42:14.400> it<01:42:14.639> and 01:42:15.590 --> 01:42:15.600 align:start position:0% the clients to please implement it and 01:42:15.600 --> 01:42:17.870 align:start position:0% the clients to please implement it and and<01:42:15.960> everybody<01:42:16.739> is<01:42:17.100> just<01:42:17.280> waiting<01:42:17.580> for<01:42:17.760> that 01:42:17.870 --> 01:42:17.880 align:start position:0% and everybody is just waiting for that 01:42:17.880 --> 01:42:19.550 align:start position:0% and everybody is just waiting for that client<01:42:18.179> to<01:42:18.360> implement<01:42:18.659> and<01:42:18.900> find<01:42:19.080> all<01:42:19.380> the 01:42:19.550 --> 01:42:19.560 align:start position:0% client to implement and find all the 01:42:19.560 --> 01:42:22.550 align:start position:0% client to implement and find all the corner<01:42:19.860> cases<01:42:20.100> and<01:42:20.280> when<01:42:20.520> when<01:42:21.300> the<01:42:21.659> code<01:42:22.139> apps 01:42:22.550 --> 01:42:22.560 align:start position:0% corner cases and when when the code apps 01:42:22.560 --> 01:42:24.770 align:start position:0% corner cases and when when the code apps say<01:42:22.679> that<01:42:22.860> okay<01:42:23.040> we<01:42:23.639> are<01:42:23.820> releasing<01:42:24.239> this<01:42:24.420> EIP 01:42:24.770 --> 01:42:24.780 align:start position:0% say that okay we are releasing this EIP 01:42:24.780 --> 01:42:26.450 align:start position:0% say that okay we are releasing this EIP in<01:42:25.139> three<01:42:25.320> months<01:42:25.500> and<01:42:25.679> everybody<01:42:25.860> goes<01:42:26.340> into 01:42:26.450 --> 01:42:26.460 align:start position:0% in three months and everybody goes into 01:42:26.460 --> 01:42:28.550 align:start position:0% in three months and everybody goes into this<01:42:26.699> holy<01:42:27.179> mode<01:42:27.360> and<01:42:27.540> okay<01:42:27.780> let's 01:42:28.550 --> 01:42:28.560 align:start position:0% this holy mode and okay let's 01:42:28.560 --> 01:42:31.550 align:start position:0% this holy mode and okay let's quickly<01:42:29.280> implement<01:42:29.639> it<01:42:29.880> and<01:42:30.719> then<01:42:30.900> we<01:42:31.139> kind<01:42:31.380> of 01:42:31.550 --> 01:42:31.560 align:start position:0% quickly implement it and then we kind of 01:42:31.560 --> 01:42:34.850 align:start position:0% quickly implement it and then we kind of like<01:42:31.800> pursue<01:42:32.340> this<01:42:32.520> dream<01:42:32.880> of<01:42:33.840> Roll-Ups<01:42:34.619> I<01:42:34.739> was 01:42:34.850 --> 01:42:34.860 align:start position:0% like pursue this dream of Roll-Ups I was 01:42:34.860 --> 01:42:35.870 align:start position:0% like pursue this dream of Roll-Ups I was like 01:42:35.870 --> 01:42:35.880 align:start position:0% like 01:42:35.880 --> 01:42:39.229 align:start position:0% like like<01:42:36.300> comparative<01:42:37.159> execution<01:42:38.159> layers<01:42:38.639> on<01:42:39.119> top 01:42:39.229 --> 01:42:39.239 align:start position:0% like comparative execution layers on top 01:42:39.239 --> 01:42:41.330 align:start position:0% like comparative execution layers on top of<01:42:39.420> a<01:42:39.600> secure<01:42:39.960> data<01:42:40.380> layer<01:42:40.619> that's<01:42:40.800> minimal 01:42:41.330 --> 01:42:41.340 align:start position:0% of a secure data layer that's minimal 01:42:41.340 --> 01:42:44.810 align:start position:0% of a secure data layer that's minimal and<01:42:41.699> like<01:42:42.480> widely<01:42:43.199> decentralized 01:42:44.810 --> 01:42:44.820 align:start position:0% and like widely decentralized 01:42:44.820 --> 01:42:47.270 align:start position:0% and like widely decentralized but<01:42:45.179> right<01:42:45.360> now<01:42:45.540> just<01:42:45.719> we<01:42:46.199> don't<01:42:46.320> have<01:42:46.679> a<01:42:46.980> layer 01:42:47.270 --> 01:42:47.280 align:start position:0% but right now just we don't have a layer 01:42:47.280 --> 01:42:50.270 align:start position:0% but right now just we don't have a layer 2<01:42:47.400> evm<01:42:47.880> standards<01:42:48.900> but<01:42:49.320> I<01:42:49.500> mean<01:42:49.619> what<01:42:49.860> if<01:42:50.040> you 01:42:50.270 --> 01:42:50.280 align:start position:0% 2 evm standards but I mean what if you 01:42:50.280 --> 01:42:51.830 align:start position:0% 2 evm standards but I mean what if you wind<01:42:50.400> up<01:42:50.580> in<01:42:50.699> a<01:42:50.820> situation<01:42:51.060> like<01:42:51.239> coven<01:42:51.600> where 01:42:51.830 --> 01:42:51.840 align:start position:0% wind up in a situation like coven where 01:42:51.840 --> 01:42:53.629 align:start position:0% wind up in a situation like coven where you<01:42:52.020> had<01:42:52.139> a<01:42:52.679> part<01:42:52.860> of<01:42:52.980> the<01:42:53.100> chain<01:42:53.219> that<01:42:53.460> ran 01:42:53.629 --> 01:42:53.639 align:start position:0% you had a part of the chain that ran 01:42:53.639 --> 01:42:54.830 align:start position:0% you had a part of the chain that ran with<01:42:53.820> wasm<01:42:54.239> and<01:42:54.360> then<01:42:54.480> all<01:42:54.600> of<01:42:54.719> a<01:42:54.780> sudden 01:42:54.830 --> 01:42:54.840 align:start position:0% with wasm and then all of a sudden 01:42:54.840 --> 01:42:56.689 align:start position:0% with wasm and then all of a sudden wasm's<01:42:55.440> gone<01:42:55.619> then<01:42:56.159> all<01:42:56.280> of<01:42:56.400> a<01:42:56.400> sudden<01:42:56.460> one 01:42:56.689 --> 01:42:56.699 align:start position:0% wasm's gone then all of a sudden one 01:42:56.699 --> 01:42:58.970 align:start position:0% wasm's gone then all of a sudden one client<01:42:56.880> they<01:42:57.060> can<01:42:57.179> run<01:42:57.300> Watson's<01:42:57.780> gone<01:42:57.980> and 01:42:58.970 --> 01:42:58.980 align:start position:0% client they can run Watson's gone and 01:42:58.980 --> 01:43:00.950 align:start position:0% client they can run Watson's gone and you<01:42:59.159> can't<01:42:59.280> run<01:42:59.460> the<01:42:59.639> chain<01:42:59.820> from<01:43:00.060> zero<01:43:00.420> is 01:43:00.950 --> 01:43:00.960 align:start position:0% you can't run the chain from zero is 01:43:00.960 --> 01:43:03.470 align:start position:0% you can't run the chain from zero is that<01:43:01.080> a<01:43:01.260> bad<01:43:01.380> thing<01:43:01.560> is<01:43:01.739> it<01:43:01.920> an<01:43:02.040> okay<01:43:02.219> thing 01:43:03.470 --> 01:43:03.480 align:start position:0% that a bad thing is it an okay thing 01:43:03.480 --> 01:43:06.050 align:start position:0% that a bad thing is it an okay thing I<01:43:04.139> would<01:43:04.380> say<01:43:04.560> it's<01:43:04.800> pretty<01:43:05.280> pretty<01:43:05.520> bad<01:43:05.820> so 01:43:06.050 --> 01:43:06.060 align:start position:0% I would say it's pretty pretty bad so 01:43:06.060 --> 01:43:08.390 align:start position:0% I would say it's pretty pretty bad so it's<01:43:06.239> it's<01:43:06.420> basically<01:43:07.260> just<01:43:07.500> shoving<01:43:07.980> teched 01:43:08.390 --> 01:43:08.400 align:start position:0% it's it's basically just shoving teched 01:43:08.400 --> 01:43:11.270 align:start position:0% it's it's basically just shoving teched up<01:43:08.460> to<01:43:08.639> layer<01:43:08.940> twos<01:43:09.300> and<01:43:10.020> then<01:43:10.199> the<01:43:10.920> cost<01:43:11.040> is 01:43:11.270 --> 01:43:11.280 align:start position:0% up to layer twos and then the cost is 01:43:11.280 --> 01:43:14.270 align:start position:0% up to layer twos and then the cost is incurred<01:43:11.699> by<01:43:11.880> users<01:43:12.300> being<01:43:12.900> confused<01:43:13.619> by 01:43:14.270 --> 01:43:14.280 align:start position:0% incurred by users being confused by 01:43:14.280 --> 01:43:16.550 align:start position:0% incurred by users being confused by their<01:43:14.639> smart<01:43:15.000> contract<01:43:15.360> works<01:43:15.840> on<01:43:15.960> 110<01:43:16.260> not 01:43:16.550 --> 01:43:16.560 align:start position:0% their smart contract works on 110 not 01:43:16.560 --> 01:43:21.890 align:start position:0% their smart contract works on 110 not the<01:43:16.739> other<01:43:16.800> 10.<01:43:17.639> right 01:43:21.890 --> 01:43:21.900 align:start position:0% 01:43:21.900 --> 01:43:23.930 align:start position:0% oh<01:43:22.260> just<01:43:22.679> yeah<01:43:22.860> we<01:43:23.100> can<01:43:23.340> wrap<01:43:23.460> up<01:43:23.639> here<01:43:23.760> we're 01:43:23.930 --> 01:43:23.940 align:start position:0% oh just yeah we can wrap up here we're 01:43:23.940 --> 01:43:26.870 align:start position:0% oh just yeah we can wrap up here we're like<01:43:24.060> yeah<01:43:24.560> yeah<01:43:25.560> we<01:43:25.860> can<01:43:26.040> I<01:43:26.460> mean<01:43:26.580> if<01:43:26.699> there's 01:43:26.870 --> 01:43:26.880 align:start position:0% like yeah yeah we can I mean if there's 01:43:26.880 --> 01:43:28.430 align:start position:0% like yeah yeah we can I mean if there's final<01:43:27.060> comments<01:43:27.420> we<01:43:27.480> can<01:43:27.600> do<01:43:27.719> that<01:43:27.840> then<01:43:28.139> maybe 01:43:28.430 --> 01:43:28.440 align:start position:0% final comments we can do that then maybe 01:43:28.440 --> 01:43:29.689 align:start position:0% final comments we can do that then maybe we<01:43:28.619> should<01:43:28.739> take<01:43:28.860> a<01:43:28.980> short<01:43:29.100> break<01:43:29.280> but<01:43:29.460> just 01:43:29.689 --> 01:43:29.699 align:start position:0% we should take a short break but just 01:43:29.699 --> 01:43:30.830 align:start position:0% we should take a short break but just want<01:43:29.820> to<01:43:29.940> make<01:43:30.000> sure<01:43:30.060> we<01:43:30.239> wanted<01:43:30.300> to<01:43:30.540> keep<01:43:30.659> the 01:43:30.830 --> 01:43:30.840 align:start position:0% want to make sure we wanted to keep the 01:43:30.840 --> 01:43:34.010 align:start position:0% want to make sure we wanted to keep the last<01:43:30.960> hour<01:43:31.199> to<01:43:31.920> discuss<01:43:32.219> actual<01:43:32.580> eips 01:43:34.010 --> 01:43:34.020 align:start position:0% last hour to discuss actual eips 01:43:34.020 --> 01:43:35.629 align:start position:0% last hour to discuss actual eips um because<01:43:34.199> we<01:43:34.440> we<01:43:34.739> don't<01:43:34.980> usually<01:43:35.280> have<01:43:35.400> like 01:43:35.629 --> 01:43:35.639 align:start position:0% um because we we don't usually have like 01:43:35.639 --> 01:43:37.250 align:start position:0% um because we we don't usually have like forums<01:43:36.000> to<01:43:36.179> do<01:43:36.300> that<01:43:36.480> with<01:43:36.719> all<01:43:36.900> the<01:43:37.020> client 01:43:37.250 --> 01:43:37.260 align:start position:0% forums to do that with all the client 01:43:37.260 --> 01:43:38.450 align:start position:0% forums to do that with all the client teams<01:43:37.560> so 01:43:38.450 --> 01:43:38.460 align:start position:0% teams so 01:43:38.460 --> 01:43:40.129 align:start position:0% teams so um if<01:43:38.940> people<01:43:39.060> want<01:43:39.360> to<01:43:39.480> have<01:43:39.540> less<01:43:39.659> comments 01:43:40.129 --> 01:43:40.139 align:start position:0% um if people want to have less comments 01:43:40.139 --> 01:43:41.750 align:start position:0% um if people want to have less comments or<01:43:40.500> take<01:43:40.800> a<01:43:40.920> short<01:43:41.040> break<01:43:41.219> you<01:43:41.400> can<01:43:41.520> do<01:43:41.639> that 01:43:41.750 --> 01:43:41.760 align:start position:0% or take a short break you can do that 01:43:41.760 --> 01:43:44.330 align:start position:0% or take a short break you can do that but<01:43:41.940> let's<01:43:42.540> take<01:43:43.020> a<01:43:43.199> break<01:43:43.380> for<01:43:43.800> like<01:43:43.980> five 01:43:44.330 --> 01:43:44.340 align:start position:0% but let's take a break for like five 01:43:44.340 --> 01:43:47.209 align:start position:0% but let's take a break for like five minutes<01:43:44.639> and<01:43:45.060> then<01:43:45.179> let's<01:43:45.480> have<01:43:45.900> the<01:43:46.219> Shanghai 01:43:47.209 --> 01:43:47.219 align:start position:0% minutes and then let's have the Shanghai 01:43:47.219 --> 01:43:50.990 align:start position:0% minutes and then let's have the Shanghai AAP<01:43:47.639> outers<01:43:48.239> lineup<01:43:49.139> or<01:43:49.860> switch<01:43:50.219> the<01:43:50.580> spots 01:43:50.990 --> 01:43:51.000 align:start position:0% AAP outers lineup or switch the spots 01:43:51.000 --> 01:43:54.189 align:start position:0% AAP outers lineup or switch the spots with<01:43:51.239> the<01:43:51.420> yeah 01:43:54.189 --> 01:43:54.199 align:start position:0% 01:43:54.199 --> 01:43:57.430 align:start position:0% thank<01:43:55.199> you<01:43:55.520> okay<01:43:56.520> go<01:43:56.940> to<01:43:57.060> the<01:43:57.239> bathroom 01:43:57.430 --> 01:43:57.440 align:start position:0% thank you okay go to the bathroom 01:43:57.440 --> 01:44:05.500 align:start position:0% thank you okay go to the bathroom [Applause]