WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.450 align:start position:0% foreign 00:00:04.450 --> 00:00:04.460 align:start position:0% 00:00:04.460 --> 00:00:13.270 align:start position:0% [Music] 00:00:13.270 --> 00:00:13.280 align:start position:0% 00:00:13.280 --> 00:00:14.470 align:start position:0% [Music] 00:00:14.470 --> 00:00:14.480 align:start position:0% [Music] 00:00:14.480 --> 00:00:16.790 align:start position:0% [Music] systems<00:00:15.480> thank<00:00:15.719> you<00:00:15.839> I'm<00:00:16.139> also<00:00:16.440> one<00:00:16.619> of<00:00:16.740> the 00:00:16.790 --> 00:00:16.800 align:start position:0% systems thank you I'm also one of the 00:00:16.800 --> 00:00:19.849 align:start position:0% systems thank you I'm also one of the co-organizers<00:00:17.340> of<00:00:17.520> East<00:00:17.699> Berlin<00:00:18.119> and<00:00:18.960> I<00:00:19.740> used 00:00:19.849 --> 00:00:19.859 align:start position:0% co-organizers of East Berlin and I used 00:00:19.859 --> 00:00:23.810 align:start position:0% co-organizers of East Berlin and I used to<00:00:20.100> work<00:00:20.580> on<00:00:21.060> various<00:00:21.680> EF<00:00:22.680> and<00:00:22.859> ESP<00:00:23.039> grants<00:00:23.640> in 00:00:23.810 --> 00:00:23.820 align:start position:0% to work on various EF and ESP grants in 00:00:23.820 --> 00:00:25.609 align:start position:0% to work on various EF and ESP grants in the<00:00:23.939> past<00:00:24.060> for<00:00:24.300> both<00:00:24.539> execution<00:00:25.080> layer<00:00:25.439> and 00:00:25.609 --> 00:00:25.619 align:start position:0% the past for both execution layer and 00:00:25.619 --> 00:00:27.650 align:start position:0% the past for both execution layer and consensus<00:00:26.160> layer<00:00:26.460> clients<00:00:26.760> and<00:00:27.119> among<00:00:27.420> others 00:00:27.650 --> 00:00:27.660 align:start position:0% consensus layer clients and among others 00:00:27.660 --> 00:00:29.810 align:start position:0% consensus layer clients and among others as<00:00:28.140> Francis<00:00:28.380> already<00:00:28.680> mentioned<00:00:29.220> I<00:00:29.580> launched 00:00:29.810 --> 00:00:29.820 align:start position:0% as Francis already mentioned I launched 00:00:29.820 --> 00:00:32.030 align:start position:0% as Francis already mentioned I launched the<00:00:29.939> early<00:00:30.240> testnet<00:00:30.779> with<00:00:31.199> a<00:00:31.439> bunch<00:00:31.679> of<00:00:31.800> cool 00:00:32.030 --> 00:00:32.040 align:start position:0% the early testnet with a bunch of cool 00:00:32.040 --> 00:00:33.650 align:start position:0% the early testnet with a bunch of cool people<00:00:32.340> that<00:00:32.640> are<00:00:32.759> also<00:00:33.059> sitting<00:00:33.300> here<00:00:33.420> in<00:00:33.540> the 00:00:33.650 --> 00:00:33.660 align:start position:0% people that are also sitting here in the 00:00:33.660 --> 00:00:36.830 align:start position:0% people that are also sitting here in the room<00:00:33.780> in<00:00:34.620> 2019<00:00:34.980> so<00:00:35.880> what<00:00:36.300> I'm<00:00:36.480> going<00:00:36.600> to<00:00:36.719> cover 00:00:36.830 --> 00:00:36.840 align:start position:0% room in 2019 so what I'm going to cover 00:00:36.840 --> 00:00:40.010 align:start position:0% room in 2019 so what I'm going to cover today<00:00:37.200> is<00:00:37.680> I<00:00:38.219> want<00:00:38.340> to<00:00:38.460> briefly<00:00:39.000> dive<00:00:39.540> into<00:00:39.719> the 00:00:40.010 --> 00:00:40.020 align:start position:0% today is I want to briefly dive into the 00:00:40.020 --> 00:00:42.110 align:start position:0% today is I want to briefly dive into the ethereum<00:00:40.500> protocol<00:00:40.860> history<00:00:41.100> prior<00:00:41.879> to<00:00:42.000> the 00:00:42.110 --> 00:00:42.120 align:start position:0% ethereum protocol history prior to the 00:00:42.120 --> 00:00:44.150 align:start position:0% ethereum protocol history prior to the merge 00:00:44.150 --> 00:00:44.160 align:start position:0% merge 00:00:44.160 --> 00:00:46.130 align:start position:0% merge um<00:00:44.219> and<00:00:44.760> then<00:00:44.879> specifically<00:00:45.420> take<00:00:45.780> a<00:00:45.960> close 00:00:46.130 --> 00:00:46.140 align:start position:0% um and then specifically take a close 00:00:46.140 --> 00:00:48.709 align:start position:0% um and then specifically take a close look<00:00:46.320> at<00:00:46.559> the<00:00:46.680> implications<00:00:47.100> of<00:00:47.820> the<00:00:48.059> merge<00:00:48.420> on 00:00:48.709 --> 00:00:48.719 align:start position:0% look at the implications of the merge on 00:00:48.719 --> 00:00:51.290 align:start position:0% look at the implications of the merge on the<00:00:48.899> test<00:00:49.020> Nets<00:00:49.500> and<00:00:50.100> finally<00:00:50.700> give<00:00:51.000> a<00:00:51.180> quick 00:00:51.290 --> 00:00:51.300 align:start position:0% the test Nets and finally give a quick 00:00:51.300 --> 00:00:53.150 align:start position:0% the test Nets and finally give a quick guide<00:00:51.539> to<00:00:51.780> selecting<00:00:52.200> a<00:00:52.379> test<00:00:52.500> net<00:00:52.680> for<00:00:52.980> your 00:00:53.150 --> 00:00:53.160 align:start position:0% guide to selecting a test net for your 00:00:53.160 --> 00:00:56.090 align:start position:0% guide to selecting a test net for your project<00:00:54.120> so<00:00:55.020> yeah<00:00:55.199> let's<00:00:55.440> dive<00:00:55.680> right<00:00:55.920> into 00:00:56.090 --> 00:00:56.100 align:start position:0% project so yeah let's dive right into 00:00:56.100 --> 00:00:58.250 align:start position:0% project so yeah let's dive right into the<00:00:56.399> protocol<00:00:56.699> history<00:00:57.000> everything<00:00:57.780> started 00:00:58.250 --> 00:00:58.260 align:start position:0% the protocol history everything started 00:00:58.260 --> 00:00:59.510 align:start position:0% the protocol history everything started with<00:00:58.379> a<00:00:58.559> test<00:00:58.680> net 00:00:59.510 --> 00:00:59.520 align:start position:0% with a test net 00:00:59.520 --> 00:01:01.729 align:start position:0% with a test net does<00:01:00.239> anyone<00:01:00.539> here<00:01:00.719> know<00:01:00.960> what's<00:01:01.379> the<00:01:01.620> meaning 00:01:01.729 --> 00:01:01.739 align:start position:0% does anyone here know what's the meaning 00:01:01.739 --> 00:01:03.470 align:start position:0% does anyone here know what's the meaning of<00:01:01.980> the<00:01:02.100> ethereum 00:01:03.470 --> 00:01:03.480 align:start position:0% of the ethereum 00:01:03.480 --> 00:01:06.410 align:start position:0% of the ethereum Genesis<00:01:04.140> extra<00:01:04.500> data<00:01:04.979> is<00:01:05.100> you<00:01:05.880> might<00:01:06.000> know<00:01:06.180> the 00:01:06.410 --> 00:01:06.420 align:start position:0% Genesis extra data is you might know the 00:01:06.420 --> 00:01:09.170 align:start position:0% Genesis extra data is you might know the Bitcoin<00:01:06.900> extra<00:01:07.080> data<00:01:07.560> or<00:01:07.880> against<00:01:08.880> this 00:01:09.170 --> 00:01:09.180 align:start position:0% Bitcoin extra data or against this 00:01:09.180 --> 00:01:11.030 align:start position:0% Bitcoin extra data or against this accelerator<00:01:09.540> contains<00:01:10.140> a<00:01:10.380> news<00:01:10.680> headline 00:01:11.030 --> 00:01:11.040 align:start position:0% accelerator contains a news headline 00:01:11.040 --> 00:01:12.950 align:start position:0% accelerator contains a news headline does<00:01:11.340> anyone<00:01:11.580> know<00:01:11.760> what<00:01:12.000> the<00:01:12.180> meaning<00:01:12.540> of<00:01:12.780> the 00:01:12.950 --> 00:01:12.960 align:start position:0% does anyone know what the meaning of the 00:01:12.960 --> 00:01:16.250 align:start position:0% does anyone know what the meaning of the ethereum<00:01:13.799> accelerators<00:01:14.400> it's<00:01:15.360> actually<00:01:15.600> a 00:01:16.250 --> 00:01:16.260 align:start position:0% ethereum accelerators it's actually a 00:01:16.260 --> 00:01:19.550 align:start position:0% ethereum accelerators it's actually a block<00:01:16.439> hash<00:01:16.799> from<00:01:17.159> a<00:01:17.340> test<00:01:17.520> net 00:01:19.550 --> 00:01:19.560 align:start position:0% block hash from a test net 00:01:19.560 --> 00:01:22.910 align:start position:0% block hash from a test net um ethereum<00:01:20.220> was<00:01:20.939> uh<00:01:21.659> publicly<00:01:22.380> fairly 00:01:22.910 --> 00:01:22.920 align:start position:0% um ethereum was uh publicly fairly 00:01:22.920 --> 00:01:25.969 align:start position:0% um ethereum was uh publicly fairly launched<00:01:23.340> by<00:01:23.759> announcing<00:01:24.360> a<00:01:24.780> block<00:01:25.259> number<00:01:25.500> on 00:01:25.969 --> 00:01:25.979 align:start position:0% launched by announcing a block number on 00:01:25.979 --> 00:01:28.630 align:start position:0% launched by announcing a block number on a<00:01:26.159> Olympic<00:01:26.820> test<00:01:26.939> net<00:01:27.180> that<00:01:27.780> was 00:01:28.630 --> 00:01:28.640 align:start position:0% a Olympic test net that was 00:01:28.640 --> 00:01:33.410 align:start position:0% a Olympic test net that was 128<00:01:29.640> 201<00:01:30.860> and<00:01:31.860> once<00:01:32.159> this<00:01:32.280> test<00:01:32.640> net<00:01:32.880> was<00:01:33.119> mined 00:01:33.410 --> 00:01:33.420 align:start position:0% 128 201 and once this test net was mined 00:01:33.420 --> 00:01:36.410 align:start position:0% 128 201 and once this test net was mined on<00:01:33.540> the<00:01:33.840> uh<00:01:34.680> test<00:01:35.100> once<00:01:35.759> this<00:01:35.820> block<00:01:35.939> was<00:01:36.180> mined 00:01:36.410 --> 00:01:36.420 align:start position:0% on the uh test once this block was mined 00:01:36.420 --> 00:01:38.569 align:start position:0% on the uh test once this block was mined on<00:01:36.540> the<00:01:36.659> test<00:01:36.780> net<00:01:36.960> this<00:01:37.560> hash<00:01:37.920> could<00:01:38.340> be 00:01:38.569 --> 00:01:38.579 align:start position:0% on the test net this hash could be 00:01:38.579 --> 00:01:41.870 align:start position:0% on the test net this hash could be inserted<00:01:39.420> into<00:01:39.780> the<00:01:40.680> ethereum<00:01:41.100> Genesis<00:01:41.460> and 00:01:41.870 --> 00:01:41.880 align:start position:0% inserted into the ethereum Genesis and 00:01:41.880 --> 00:01:43.850 align:start position:0% inserted into the ethereum Genesis and the<00:01:42.299> public<00:01:42.479> mining<00:01:42.900> on<00:01:43.020> ethereum<00:01:43.439> mainnet 00:01:43.850 --> 00:01:43.860 align:start position:0% the public mining on ethereum mainnet 00:01:43.860 --> 00:01:45.649 align:start position:0% the public mining on ethereum mainnet could<00:01:44.159> start 00:01:45.649 --> 00:01:45.659 align:start position:0% could start 00:01:45.659 --> 00:01:47.749 align:start position:0% could start Olympic<00:01:46.320> was<00:01:46.500> the<00:01:46.680> last<00:01:46.860> pre-release<00:01:47.340> testnet 00:01:47.749 --> 00:01:47.759 align:start position:0% Olympic was the last pre-release testnet 00:01:47.759 --> 00:01:50.330 align:start position:0% Olympic was the last pre-release testnet before<00:01:47.880> the<00:01:48.180> issue<00:01:48.600> mainnet<00:01:49.020> was<00:01:49.200> launched 00:01:50.330 --> 00:01:50.340 align:start position:0% before the issue mainnet was launched 00:01:50.340 --> 00:01:53.149 align:start position:0% before the issue mainnet was launched and<00:01:51.060> the<00:01:51.299> first<00:01:51.600> public<00:01:52.259> assumed<00:01:52.740> testnet 00:01:53.149 --> 00:01:53.159 align:start position:0% and the first public assumed testnet 00:01:53.159 --> 00:01:55.190 align:start position:0% and the first public assumed testnet after<00:01:53.520> the<00:01:53.700> launch<00:01:53.939> was<00:01:54.180> more 00:01:55.190 --> 00:01:55.200 align:start position:0% after the launch was more 00:01:55.200 --> 00:01:56.870 align:start position:0% after the launch was more than<00:01:55.740> was<00:01:55.920> a<00:01:56.040> proof<00:01:56.220> of<00:01:56.220> work<00:01:56.340> testing<00:01:56.759> it 00:01:56.870 --> 00:01:56.880 align:start position:0% than was a proof of work testing it 00:01:56.880 --> 00:01:59.870 align:start position:0% than was a proof of work testing it using<00:01:57.060> the<00:01:57.180> same<00:01:57.299> algorithm<00:01:58.200> as<00:01:58.380> mainnet<00:01:58.880> and 00:01:59.870 --> 00:01:59.880 align:start position:0% using the same algorithm as mainnet and 00:01:59.880 --> 00:02:01.910 align:start position:0% using the same algorithm as mainnet and interestingly<00:02:00.479> it<00:02:00.720> had<00:02:00.899> a<00:02:01.020> custom<00:02:01.200> starting 00:02:01.910 --> 00:02:01.920 align:start position:0% interestingly it had a custom starting 00:02:01.920 --> 00:02:05.450 align:start position:0% interestingly it had a custom starting launch<00:02:02.659> of<00:02:03.659> 2<00:02:03.899> to<00:02:04.079> the<00:02:04.259> power<00:02:04.380> of<00:02:04.560> 20<00:02:04.799> to 00:02:05.450 --> 00:02:05.460 align:start position:0% launch of 2 to the power of 20 to 00:02:05.460 --> 00:02:08.510 align:start position:0% launch of 2 to the power of 20 to prevent<00:02:06.119> transaction<00:02:06.719> replays<00:02:07.439> on<00:02:07.799> mainnet 00:02:08.510 --> 00:02:08.520 align:start position:0% prevent transaction replays on mainnet 00:02:08.520 --> 00:02:10.249 align:start position:0% prevent transaction replays on mainnet most<00:02:09.119> of<00:02:09.300> us<00:02:09.360> probably<00:02:09.660> remember<00:02:09.899> the 00:02:10.249 --> 00:02:10.259 align:start position:0% most of us probably remember the 00:02:10.259 --> 00:02:13.190 align:start position:0% most of us probably remember the Shanghai<00:02:10.679> attacks<00:02:11.099> during<00:02:11.220> Defcon<00:02:11.760> 2<00:02:12.000> in<00:02:12.480> 2016 00:02:13.190 --> 00:02:13.200 align:start position:0% Shanghai attacks during Defcon 2 in 2016 00:02:13.200 --> 00:02:16.190 align:start position:0% Shanghai attacks during Defcon 2 in 2016 an<00:02:14.160> attacker<00:02:14.580> exploited<00:02:15.239> the<00:02:15.480> long<00:02:15.660> discrete 00:02:16.190 --> 00:02:16.200 align:start position:0% an attacker exploited the long discrete 00:02:16.200 --> 00:02:20.030 align:start position:0% an attacker exploited the long discrete time<00:02:16.440> of<00:02:16.920> the<00:02:17.099> X<00:02:17.280> code<00:02:17.580> size<00:02:17.879> op<00:02:18.420> code<00:02:18.860> in<00:02:19.860> one 00:02:20.030 --> 00:02:20.040 align:start position:0% time of the X code size op code in one 00:02:20.040 --> 00:02:21.830 align:start position:0% time of the X code size op code in one of<00:02:20.160> the<00:02:20.280> client<00:02:20.400> implementations<00:02:21.060> which 00:02:21.830 --> 00:02:21.840 align:start position:0% of the client implementations which 00:02:21.840 --> 00:02:23.510 align:start position:0% of the client implementations which caused<00:02:22.200> the<00:02:22.260> denial<00:02:22.620> of<00:02:22.739> service<00:02:22.920> of<00:02:23.340> the 00:02:23.510 --> 00:02:23.520 align:start position:0% caused the denial of service of the 00:02:23.520 --> 00:02:25.490 align:start position:0% caused the denial of service of the issue<00:02:23.940> main<00:02:24.120> net<00:02:24.300> here's<00:02:24.780> a<00:02:24.840> photo<00:02:24.959> of<00:02:25.200> the 00:02:25.490 --> 00:02:25.500 align:start position:0% issue main net here's a photo of the 00:02:25.500 --> 00:02:28.729 align:start position:0% issue main net here's a photo of the amazing<00:02:26.459> guest<00:02:26.700> team<00:02:27.020> investigating<00:02:28.020> the 00:02:28.729 --> 00:02:28.739 align:start position:0% amazing guest team investigating the 00:02:28.739 --> 00:02:30.830 align:start position:0% amazing guest team investigating the issues<00:02:29.099> and<00:02:29.340> coming<00:02:29.580> up<00:02:29.760> with<00:02:29.940> a<00:02:30.120> solution<00:02:30.420> to 00:02:30.830 --> 00:02:30.840 align:start position:0% issues and coming up with a solution to 00:02:30.840 --> 00:02:32.390 align:start position:0% issues and coming up with a solution to address<00:02:30.959> this<00:02:31.200> issue<00:02:31.500> two<00:02:31.739> subsequent<00:02:32.160> hard 00:02:32.390 --> 00:02:32.400 align:start position:0% address this issue two subsequent hard 00:02:32.400 --> 00:02:34.309 align:start position:0% address this issue two subsequent hard Forks<00:02:32.700> were<00:02:32.819> scheduled<00:02:33.239> for<00:02:33.360> ethereum<00:02:33.900> the 00:02:34.309 --> 00:02:34.319 align:start position:0% Forks were scheduled for ethereum the 00:02:34.319 --> 00:02:36.949 align:start position:0% Forks were scheduled for ethereum the tanguine<00:02:34.739> whistle<00:02:35.160> Fork<00:02:35.459> to<00:02:35.819> fix<00:02:36.180> the<00:02:36.780> attack 00:02:36.949 --> 00:02:36.959 align:start position:0% tanguine whistle Fork to fix the attack 00:02:36.959 --> 00:02:39.530 align:start position:0% tanguine whistle Fork to fix the attack vector<00:02:37.560> and<00:02:37.920> dispers<00:02:38.340> dragon 00:02:39.530 --> 00:02:39.540 align:start position:0% vector and dispers dragon 00:02:39.540 --> 00:02:41.690 align:start position:0% vector and dispers dragon Fork<00:02:40.379> to<00:02:40.500> allow<00:02:40.860> cleaning<00:02:41.220> up<00:02:41.340> the<00:02:41.459> state 00:02:41.690 --> 00:02:41.700 align:start position:0% Fork to allow cleaning up the state 00:02:41.700 --> 00:02:45.110 align:start position:0% Fork to allow cleaning up the state afterwards<00:02:42.300> however<00:02:43.019> this<00:02:43.560> protocol<00:02:43.920> change 00:02:45.110 --> 00:02:45.120 align:start position:0% afterwards however this protocol change 00:02:45.120 --> 00:02:48.170 align:start position:0% afterwards however this protocol change caused<00:02:45.840> a<00:02:45.959> consensus<00:02:46.379> failure<00:02:46.800> on<00:02:46.980> Modern 00:02:48.170 --> 00:02:48.180 align:start position:0% caused a consensus failure on Modern 00:02:48.180 --> 00:02:50.150 align:start position:0% caused a consensus failure on Modern this<00:02:48.599> was<00:02:48.780> specifically<00:02:49.200> caused<00:02:49.620> by<00:02:49.920> the 00:02:50.150 --> 00:02:50.160 align:start position:0% this was specifically caused by the 00:02:50.160 --> 00:02:52.790 align:start position:0% this was specifically caused by the different<00:02:50.840> ways<00:02:51.840> how<00:02:52.019> the<00:02:52.200> clients<00:02:52.440> handled 00:02:52.790 --> 00:02:52.800 align:start position:0% different ways how the clients handled 00:02:52.800 --> 00:02:55.009 align:start position:0% different ways how the clients handled this<00:02:52.980> custom<00:02:53.220> starting<00:02:53.580> loans<00:02:54.120> and<00:02:54.599> it<00:02:54.900> was 00:02:55.009 --> 00:02:55.019 align:start position:0% this custom starting loans and it was 00:02:55.019 --> 00:02:57.410 align:start position:0% this custom starting loans and it was then<00:02:55.200> decided<00:02:55.620> it's<00:02:55.800> not<00:02:56.099> not<00:02:56.700> a<00:02:56.879> good<00:02:57.000> idea<00:02:57.239> to 00:02:57.410 --> 00:02:57.420 align:start position:0% then decided it's not not a good idea to 00:02:57.420 --> 00:02:59.330 align:start position:0% then decided it's not not a good idea to have<00:02:57.540> a<00:02:57.720> custom<00:02:57.840> protocol<00:02:58.260> on<00:02:58.560> a<00:02:58.680> test<00:02:58.739> net<00:02:58.920> and 00:02:59.330 --> 00:02:59.340 align:start position:0% have a custom protocol on a test net and 00:02:59.340 --> 00:03:02.449 align:start position:0% have a custom protocol on a test net and therefore<00:02:59.760> modern<00:03:00.480> was<00:03:01.160> discontinued<00:03:02.160> and 00:03:02.449 --> 00:03:02.459 align:start position:0% therefore modern was discontinued and 00:03:02.459 --> 00:03:05.330 align:start position:0% therefore modern was discontinued and replaced<00:03:03.060> by<00:03:03.480> a<00:03:03.959> new<00:03:04.440> testnet<00:03:05.099> called 00:03:05.330 --> 00:03:05.340 align:start position:0% replaced by a new testnet called 00:03:05.340 --> 00:03:07.369 align:start position:0% replaced by a new testnet called ribstone<00:03:05.819> groups<00:03:06.420> was<00:03:06.599> the<00:03:06.720> first<00:03:06.840> tester<00:03:07.200> to 00:03:07.369 --> 00:03:07.379 align:start position:0% ribstone groups was the first tester to 00:03:07.379 --> 00:03:10.210 align:start position:0% ribstone groups was the first tester to launch<00:03:07.560> with<00:03:08.120> shine<00:03:09.120> ID<00:03:09.300> right<00:03:09.599> from<00:03:09.720> Genesis 00:03:10.210 --> 00:03:10.220 align:start position:0% launch with shine ID right from Genesis 00:03:10.220 --> 00:03:13.369 align:start position:0% launch with shine ID right from Genesis the<00:03:11.220> chain<00:03:11.400> ID<00:03:11.700> served<00:03:12.480> the<00:03:12.540> purpose<00:03:12.900> of<00:03:13.200> a 00:03:13.369 --> 00:03:13.379 align:start position:0% the chain ID served the purpose of a 00:03:13.379 --> 00:03:15.830 align:start position:0% the chain ID served the purpose of a simple<00:03:13.500> replay<00:03:13.800> protection<00:03:14.599> according<00:03:15.599> to 00:03:15.830 --> 00:03:15.840 align:start position:0% simple replay protection according to 00:03:15.840 --> 00:03:18.290 align:start position:0% simple replay protection according to EIP<00:03:16.440> 155 00:03:18.290 --> 00:03:18.300 align:start position:0% EIP 155 00:03:18.300 --> 00:03:20.509 align:start position:0% EIP 155 so<00:03:18.720> the<00:03:18.900> roof's<00:03:19.260> intestine<00:03:19.620> was<00:03:19.980> also<00:03:20.220> powered 00:03:20.509 --> 00:03:20.519 align:start position:0% so the roof's intestine was also powered 00:03:20.519 --> 00:03:23.149 align:start position:0% so the roof's intestine was also powered by<00:03:20.640> the<00:03:20.879> isage<00:03:21.239> proof<00:03:21.540> of<00:03:21.599> work<00:03:21.780> engine<00:03:22.500> we<00:03:22.980> all 00:03:23.149 --> 00:03:23.159 align:start position:0% by the isage proof of work engine we all 00:03:23.159 --> 00:03:24.410 align:start position:0% by the isage proof of work engine we all know<00:03:23.280> proof<00:03:23.640> of<00:03:23.700> work<00:03:23.819> is<00:03:24.120> fairly 00:03:24.410 --> 00:03:24.420 align:start position:0% know proof of work is fairly 00:03:24.420 --> 00:03:25.670 align:start position:0% know proof of work is fairly permissionless 00:03:25.670 --> 00:03:25.680 align:start position:0% permissionless 00:03:25.680 --> 00:03:27.890 align:start position:0% permissionless so<00:03:26.099> there<00:03:26.340> is<00:03:26.519> no<00:03:26.700> good<00:03:26.940> incentive<00:03:27.360> to<00:03:27.599> secure 00:03:27.890 --> 00:03:27.900 align:start position:0% so there is no good incentive to secure 00:03:27.900 --> 00:03:30.589 align:start position:0% so there is no good incentive to secure a<00:03:28.080> zero<00:03:28.560> value<00:03:28.680> proof<00:03:29.159> of<00:03:29.220> work<00:03:29.400> test<00:03:29.640> bet<00:03:30.360> so 00:03:30.589 --> 00:03:30.599 align:start position:0% a zero value proof of work test bet so 00:03:30.599 --> 00:03:35.210 align:start position:0% a zero value proof of work test bet so attackers<00:03:31.260> moved<00:03:31.680> to<00:03:32.540> DOS<00:03:33.540> rubstone 00:03:35.210 --> 00:03:35.220 align:start position:0% attackers moved to DOS rubstone 00:03:35.220 --> 00:03:37.790 align:start position:0% attackers moved to DOS rubstone and<00:03:35.580> the<00:03:35.700> test<00:03:35.879> net<00:03:36.060> was<00:03:36.360> unusable<00:03:36.900> for<00:03:37.319> weeks 00:03:37.790 --> 00:03:37.800 align:start position:0% and the test net was unusable for weeks 00:03:37.800 --> 00:03:40.550 align:start position:0% and the test net was unusable for weeks in<00:03:38.400> response<00:03:38.940> parity<00:03:39.840> launched<00:03:40.140> the<00:03:40.260> coven 00:03:40.550 --> 00:03:40.560 align:start position:0% in response parity launched the coven 00:03:40.560 --> 00:03:43.070 align:start position:0% in response parity launched the coven proof<00:03:40.860> of<00:03:40.920> authority<00:03:41.280> test<00:03:41.580> net<00:03:41.760> and<00:03:42.540> guests 00:03:43.070 --> 00:03:43.080 align:start position:0% proof of authority test net and guests 00:03:43.080 --> 00:03:44.270 align:start position:0% proof of authority test net and guests launched<00:03:43.440> during<00:03:43.560> the<00:03:43.799> approval<00:03:44.220> for 00:03:44.270 --> 00:03:44.280 align:start position:0% launched during the approval for 00:03:44.280 --> 00:03:46.490 align:start position:0% launched during the approval for Authority<00:03:44.640> test<00:03:44.879> net<00:03:45.120> for<00:03:45.900> the<00:03:46.200> first<00:03:46.319> time 00:03:46.490 --> 00:03:46.500 align:start position:0% Authority test net for the first time 00:03:46.500 --> 00:03:48.770 align:start position:0% Authority test net for the first time ethereum<00:03:47.099> had<00:03:47.340> a 00:03:48.770 --> 00:03:48.780 align:start position:0% ethereum had a 00:03:48.780 --> 00:03:52.490 align:start position:0% ethereum had a way<00:03:49.560> to<00:03:50.360> have<00:03:51.360> a<00:03:51.540> more<00:03:51.720> stable<00:03:51.959> test<00:03:52.260> net 00:03:52.490 --> 00:03:52.500 align:start position:0% way to have a more stable test net 00:03:52.500 --> 00:03:54.949 align:start position:0% way to have a more stable test net environment<00:03:53.099> however<00:03:53.819> coven<00:03:54.299> used<00:03:54.599> the 00:03:54.949 --> 00:03:54.959 align:start position:0% environment however coven used the 00:03:54.959 --> 00:03:57.470 align:start position:0% environment however coven used the parity<00:03:55.319> Aura<00:03:55.799> consensus<00:03:56.220> engine<00:03:56.459> and<00:03:57.239> drink 00:03:57.470 --> 00:03:57.480 align:start position:0% parity Aura consensus engine and drink 00:03:57.480 --> 00:03:59.570 align:start position:0% parity Aura consensus engine and drink be<00:03:57.780> used<00:03:57.959> to<00:03:58.140> guess<00:03:58.440> click<00:03:58.799> consensus<00:03:59.280> engine 00:03:59.570 --> 00:03:59.580 align:start position:0% be used to guess click consensus engine 00:03:59.580 --> 00:04:02.649 align:start position:0% be used to guess click consensus engine and<00:04:00.239> they<00:04:00.360> were<00:04:00.540> not<00:04:00.720> con<00:04:01.140> compatible 00:04:02.649 --> 00:04:02.659 align:start position:0% and they were not con compatible 00:04:02.659 --> 00:04:05.270 align:start position:0% and they were not con compatible coven<00:04:03.659> was<00:04:04.019> therefore<00:04:04.440> only<00:04:04.620> accessible 00:04:05.270 --> 00:04:05.280 align:start position:0% coven was therefore only accessible 00:04:05.280 --> 00:04:08.210 align:start position:0% coven was therefore only accessible through<00:04:05.819> the<00:04:06.120> parity<00:04:06.480> serum<00:04:06.900> stack 00:04:08.210 --> 00:04:08.220 align:start position:0% through the parity serum stack 00:04:08.220 --> 00:04:11.089 align:start position:0% through the parity serum stack whereas<00:04:08.819> ring<00:04:09.060> B<00:04:09.239> was<00:04:09.540> only<00:04:09.720> accessible<00:04:10.439> by 00:04:11.089 --> 00:04:11.099 align:start position:0% whereas ring B was only accessible by 00:04:11.099 --> 00:04:13.850 align:start position:0% whereas ring B was only accessible by gas<00:04:11.340> or<00:04:11.879> tooling<00:04:12.780> that<00:04:13.080> relied<00:04:13.439> on<00:04:13.620> the<00:04:13.739> gas 00:04:13.850 --> 00:04:13.860 align:start position:0% gas or tooling that relied on the gas 00:04:13.860 --> 00:04:15.410 align:start position:0% gas or tooling that relied on the gas stack 00:04:15.410 --> 00:04:15.420 align:start position:0% stack 00:04:15.420 --> 00:04:18.590 align:start position:0% stack so<00:04:16.079> in<00:04:16.620> 2018<00:04:16.859> the<00:04:17.459> girl<00:04:17.579> initiative<00:04:18.120> attempted 00:04:18.590 --> 00:04:18.600 align:start position:0% so in 2018 the girl initiative attempted 00:04:18.600 --> 00:04:21.890 align:start position:0% so in 2018 the girl initiative attempted to<00:04:18.720> address<00:04:18.900> this<00:04:19.760> by<00:04:20.760> ideating<00:04:21.180> a 00:04:21.890 --> 00:04:21.900 align:start position:0% to address this by ideating a 00:04:21.900 --> 00:04:25.490 align:start position:0% to address this by ideating a cross-client<00:04:22.560> proof<00:04:22.860> of<00:04:22.919> authority<00:04:23.479> test<00:04:24.479> net 00:04:25.490 --> 00:04:25.500 align:start position:0% cross-client proof of authority test net 00:04:25.500 --> 00:04:27.290 align:start position:0% cross-client proof of authority test net in<00:04:25.919> the<00:04:26.100> end<00:04:26.220> the<00:04:26.460> initiative<00:04:26.759> managed<00:04:27.180> to 00:04:27.290 --> 00:04:27.300 align:start position:0% in the end the initiative managed to 00:04:27.300 --> 00:04:28.909 align:start position:0% in the end the initiative managed to implement<00:04:27.540> click<00:04:27.900> and<00:04:28.020> parity 00:04:28.909 --> 00:04:28.919 align:start position:0% implement click and parity 00:04:28.919 --> 00:04:32.210 align:start position:0% implement click and parity and<00:04:29.699> subsequently<00:04:30.540> in<00:04:30.780> 2019<00:04:31.259> the<00:04:31.800> early 00:04:32.210 --> 00:04:32.220 align:start position:0% and subsequently in 2019 the early 00:04:32.220 --> 00:04:33.770 align:start position:0% and subsequently in 2019 the early Testament<00:04:32.699> was<00:04:33.000> launched<00:04:33.300> as<00:04:33.479> a<00:04:33.660> first 00:04:33.770 --> 00:04:33.780 align:start position:0% Testament was launched as a first 00:04:33.780 --> 00:04:35.629 align:start position:0% Testament was launched as a first cross-client<00:04:34.440> proof<00:04:34.919> of<00:04:34.979> authority<00:04:35.460> test 00:04:35.629 --> 00:04:35.639 align:start position:0% cross-client proof of authority test 00:04:35.639 --> 00:04:38.810 align:start position:0% cross-client proof of authority test mode<00:04:35.940> with<00:04:36.540> validators<00:04:37.139> from<00:04:37.380> both<00:04:37.820> guests 00:04:38.810 --> 00:04:38.820 align:start position:0% mode with validators from both guests 00:04:38.820 --> 00:04:40.730 align:start position:0% mode with validators from both guests and<00:04:38.940> parity<00:04:39.360> ethereum 00:04:40.730 --> 00:04:40.740 align:start position:0% and parity ethereum 00:04:40.740 --> 00:04:43.189 align:start position:0% and parity ethereum at<00:04:41.100> the<00:04:41.280> same<00:04:41.400> time<00:04:41.580> coincidentally<00:04:42.419> after 00:04:43.189 --> 00:04:43.199 align:start position:0% at the same time coincidentally after 00:04:43.199 --> 00:04:46.010 align:start position:0% at the same time coincidentally after Defcon<00:04:43.800> I<00:04:44.639> believe<00:04:44.759> the<00:04:45.120> pantheon<00:04:45.540> client<00:04:45.840> was 00:04:46.010 --> 00:04:46.020 align:start position:0% Defcon I believe the pantheon client was 00:04:46.020 --> 00:04:48.710 align:start position:0% Defcon I believe the pantheon client was released<00:04:46.380> so<00:04:47.040> there<00:04:47.400> was<00:04:47.580> a<00:04:48.000> even<00:04:48.360> a<00:04:48.600> third 00:04:48.710 --> 00:04:48.720 align:start position:0% released so there was a even a third 00:04:48.720 --> 00:04:51.770 align:start position:0% released so there was a even a third client<00:04:49.139> available<00:04:49.979> for<00:04:50.699> running<00:04:51.180> validators 00:04:51.770 --> 00:04:51.780 align:start position:0% client available for running validators 00:04:51.780 --> 00:04:54.409 align:start position:0% client available for running validators on<00:04:51.960> this<00:04:52.080> test<00:04:52.259> net<00:04:52.440> and<00:04:52.919> soon<00:04:53.639> after<00:04:53.880> also 00:04:54.409 --> 00:04:54.419 align:start position:0% on this test net and soon after also 00:04:54.419 --> 00:04:57.350 align:start position:0% on this test net and soon after also nazamine<00:04:55.199> joined<00:04:55.560> the<00:04:55.800> validator<00:04:56.340> set 00:04:57.350 --> 00:04:57.360 align:start position:0% nazamine joined the validator set 00:04:57.360 --> 00:04:59.270 align:start position:0% nazamine joined the validator set you<00:04:57.840> know<00:04:57.960> later<00:04:58.139> the<00:04:58.440> same<00:04:58.740> year<00:04:58.919> parity 00:04:59.270 --> 00:04:59.280 align:start position:0% you know later the same year parity 00:04:59.280 --> 00:05:02.270 align:start position:0% you know later the same year parity except<00:04:59.699> uh<00:05:00.240> ethereum<00:05:00.720> and<00:05:01.620> um 00:05:02.270 --> 00:05:02.280 align:start position:0% except uh ethereum and um 00:05:02.280 --> 00:05:05.749 align:start position:0% except uh ethereum and um leaving<00:05:02.699> coven<00:05:03.300> fairly<00:05:04.080> unmaintained 00:05:05.749 --> 00:05:05.759 align:start position:0% leaving coven fairly unmaintained 00:05:05.759 --> 00:05:09.290 align:start position:0% leaving coven fairly unmaintained unfortunately 00:05:09.290 --> 00:05:09.300 align:start position:0% 00:05:09.300 --> 00:05:12.110 align:start position:0% now<00:05:09.840> going<00:05:10.500> fast<00:05:10.680> forward<00:05:10.919> in<00:05:11.220> time 00:05:12.110 --> 00:05:12.120 align:start position:0% now going fast forward in time 00:05:12.120 --> 00:05:14.689 align:start position:0% now going fast forward in time just<00:05:12.780> earlier<00:05:13.080> this<00:05:13.259> year<00:05:13.440> to<00:05:14.040> prepare<00:05:14.400> for 00:05:14.689 --> 00:05:14.699 align:start position:0% just earlier this year to prepare for 00:05:14.699 --> 00:05:16.670 align:start position:0% just earlier this year to prepare for the<00:05:14.820> merge<00:05:15.120> some<00:05:15.479> of<00:05:15.660> the<00:05:15.780> older<00:05:16.080> testnets<00:05:16.560> had 00:05:16.670 --> 00:05:16.680 align:start position:0% the merge some of the older testnets had 00:05:16.680 --> 00:05:18.830 align:start position:0% the merge some of the older testnets had to<00:05:16.800> be<00:05:16.919> deprecated<00:05:17.400> the<00:05:18.060> protocol<00:05:18.360> support 00:05:18.830 --> 00:05:18.840 align:start position:0% to be deprecated the protocol support 00:05:18.840 --> 00:05:21.530 align:start position:0% to be deprecated the protocol support team<00:05:19.560> announced<00:05:20.400> the<00:05:20.580> end<00:05:20.759> of<00:05:20.820> life<00:05:21.060> for 00:05:21.530 --> 00:05:21.540 align:start position:0% team announced the end of life for 00:05:21.540 --> 00:05:24.310 align:start position:0% team announced the end of life for Robson<00:05:22.500> and<00:05:22.740> Rigby<00:05:23.100> on 00:05:24.310 --> 00:05:24.320 align:start position:0% Robson and Rigby on 00:05:24.320 --> 00:05:29.029 align:start position:0% Robson and Rigby on the<00:05:25.320> amazing<00:05:25.740> ethereum<00:05:26.340> Foundation<00:05:27.300> block 00:05:29.029 --> 00:05:29.039 align:start position:0% the amazing ethereum Foundation block 00:05:29.039 --> 00:05:31.129 align:start position:0% the amazing ethereum Foundation block they<00:05:29.520> argued<00:05:29.940> the<00:05:30.180> older<00:05:30.600> test<00:05:30.720> Nets<00:05:31.080> are 00:05:31.129 --> 00:05:31.139 align:start position:0% they argued the older test Nets are 00:05:31.139 --> 00:05:32.749 align:start position:0% they argued the older test Nets are harder<00:05:31.380> to<00:05:31.500> maintain<00:05:31.860> due<00:05:32.400> to<00:05:32.520> Growing 00:05:32.749 --> 00:05:32.759 align:start position:0% harder to maintain due to Growing 00:05:32.759 --> 00:05:34.909 align:start position:0% harder to maintain due to Growing history<00:05:32.940> and<00:05:33.180> state<00:05:33.440> and<00:05:34.440> the<00:05:34.560> growing 00:05:34.909 --> 00:05:34.919 align:start position:0% history and state and the growing 00:05:34.919 --> 00:05:38.090 align:start position:0% history and state and the growing complexity<00:05:35.400> to<00:05:35.759> run<00:05:35.940> the<00:05:36.120> test<00:05:36.300> net<00:05:36.479> setup 00:05:38.090 --> 00:05:38.100 align:start position:0% complexity to run the test net setup 00:05:38.100 --> 00:05:39.969 align:start position:0% complexity to run the test net setup so<00:05:38.580> in<00:05:38.820> foresight 00:05:39.969 --> 00:05:39.979 align:start position:0% so in foresight 00:05:39.979 --> 00:05:42.909 align:start position:0% so in foresight however<00:05:40.979> new<00:05:41.280> test<00:05:41.460> net<00:05:41.699> was<00:05:42.000> launched 00:05:42.909 --> 00:05:42.919 align:start position:0% however new test net was launched 00:05:42.919 --> 00:05:46.249 align:start position:0% however new test net was launched sipolia<00:05:43.919> interestingly<00:05:44.880> sepolia 00:05:46.249 --> 00:05:46.259 align:start position:0% sipolia interestingly sepolia 00:05:46.259 --> 00:05:49.010 align:start position:0% sipolia interestingly sepolia that<00:05:47.100> was<00:05:47.280> just<00:05:47.460> launched<00:05:48.000> not<00:05:48.600> even<00:05:48.720> a<00:05:48.900> year 00:05:49.010 --> 00:05:49.020 align:start position:0% that was just launched not even a year 00:05:49.020 --> 00:05:53.770 align:start position:0% that was just launched not even a year ago<00:05:49.320> it<00:05:50.100> was<00:05:50.340> launched<00:05:51.060> as<00:05:51.300> a<00:05:51.479> proof<00:05:51.840> of<00:05:51.900> work 00:05:53.770 --> 00:05:53.780 align:start position:0% ago it was launched as a proof of work 00:05:53.780 --> 00:05:56.990 align:start position:0% ago it was launched as a proof of work test<00:05:54.780> net<00:05:55.020> using<00:05:55.440> the<00:05:55.620> same<00:05:55.759> algorithm<00:05:56.759> as 00:05:56.990 --> 00:05:57.000 align:start position:0% test net using the same algorithm as 00:05:57.000 --> 00:05:58.969 align:start position:0% test net using the same algorithm as main<00:05:57.180> net<00:05:57.419> back<00:05:57.780> in<00:05:57.900> the<00:05:57.960> day 00:05:58.969 --> 00:05:58.979 align:start position:0% main net back in the day 00:05:58.979 --> 00:06:00.830 align:start position:0% main net back in the day there<00:05:59.460> was<00:05:59.639> a<00:05:59.699> first<00:05:59.820> time<00:06:00.000> since<00:06:00.360> uh<00:06:00.660> the 00:06:00.830 --> 00:06:00.840 align:start position:0% there was a first time since uh the 00:06:00.840 --> 00:06:03.050 align:start position:0% there was a first time since uh the Robson<00:06:01.259> launched<00:06:01.560> in<00:06:01.680> 2017<00:06:02.039> that<00:06:02.699> we<00:06:02.880> actually 00:06:03.050 --> 00:06:03.060 align:start position:0% Robson launched in 2017 that we actually 00:06:03.060 --> 00:06:07.129 align:start position:0% Robson launched in 2017 that we actually launched<00:06:03.479> a<00:06:03.720> new<00:06:03.840> proof<00:06:04.199> of<00:06:04.259> work<00:06:04.500> test<00:06:04.740> net 00:06:07.129 --> 00:06:07.139 align:start position:0% 00:06:07.139 --> 00:06:09.290 align:start position:0% the<00:06:07.860> reason<00:06:08.039> was<00:06:08.520> potentially<00:06:09.000> to<00:06:09.180> have 00:06:09.290 --> 00:06:09.300 align:start position:0% the reason was potentially to have 00:06:09.300 --> 00:06:11.270 align:start position:0% the reason was potentially to have another<00:06:09.419> test<00:06:09.660> net<00:06:09.900> similar<00:06:10.259> to<00:06:10.380> mainnet<00:06:10.800> to 00:06:11.270 --> 00:06:11.280 align:start position:0% another test net similar to mainnet to 00:06:11.280 --> 00:06:14.749 align:start position:0% another test net similar to mainnet to allow<00:06:12.060> for<00:06:12.300> once<00:06:12.840> again<00:06:12.960> testing<00:06:13.380> the<00:06:13.560> merge 00:06:14.749 --> 00:06:14.759 align:start position:0% allow for once again testing the merge 00:06:14.759 --> 00:06:17.150 align:start position:0% allow for once again testing the merge and<00:06:15.120> now<00:06:15.300> mainnet<00:06:15.660> conditions 00:06:17.150 --> 00:06:17.160 align:start position:0% and now mainnet conditions 00:06:17.160 --> 00:06:18.950 align:start position:0% and now mainnet conditions okay<00:06:17.639> so<00:06:18.060> let's 00:06:18.950 --> 00:06:18.960 align:start position:0% okay so let's 00:06:18.960 --> 00:06:20.689 align:start position:0% okay so let's um<00:06:19.020> recap<00:06:19.620> the<00:06:19.740> test<00:06:19.919> Nets<00:06:20.280> prior<00:06:20.460> to<00:06:20.580> the 00:06:20.689 --> 00:06:20.699 align:start position:0% um recap the test Nets prior to the 00:06:20.699 --> 00:06:23.570 align:start position:0% um recap the test Nets prior to the merge<00:06:21.060> modern<00:06:21.960> is<00:06:22.680> fairly<00:06:23.100> dead<00:06:23.220> it<00:06:23.460> was 00:06:23.570 --> 00:06:23.580 align:start position:0% merge modern is fairly dead it was 00:06:23.580 --> 00:06:26.830 align:start position:0% merge modern is fairly dead it was replaced<00:06:24.000> by<00:06:24.120> Robson<00:06:24.660> in<00:06:25.020> 2017. 00:06:26.830 --> 00:06:26.840 align:start position:0% replaced by Robson in 2017. 00:06:26.840 --> 00:06:29.689 align:start position:0% replaced by Robson in 2017. was<00:06:27.840> just<00:06:28.080> deprecated<00:06:28.979> a<00:06:29.160> couple<00:06:29.280> of<00:06:29.400> weeks 00:06:29.689 --> 00:06:29.699 align:start position:0% was just deprecated a couple of weeks 00:06:29.699 --> 00:06:32.270 align:start position:0% was just deprecated a couple of weeks ago 00:06:32.270 --> 00:06:32.280 align:start position:0% 00:06:32.280 --> 00:06:33.770 align:start position:0% um coven<00:06:32.699> diet<00:06:32.940> was<00:06:33.180> poverty<00:06:33.600> leaving 00:06:33.770 --> 00:06:33.780 align:start position:0% um coven diet was poverty leaving 00:06:33.780 --> 00:06:34.909 align:start position:0% um coven diet was poverty leaving ethereum 00:06:34.909 --> 00:06:34.919 align:start position:0% ethereum 00:06:34.919 --> 00:06:37.150 align:start position:0% ethereum Rigby<00:06:35.639> was<00:06:35.940> also 00:06:37.150 --> 00:06:37.160 align:start position:0% Rigby was also 00:06:37.160 --> 00:06:39.230 align:start position:0% Rigby was also deprecated<00:06:38.160> just 00:06:39.230 --> 00:06:39.240 align:start position:0% deprecated just 00:06:39.240 --> 00:06:42.290 align:start position:0% deprecated just a<00:06:39.479> couple<00:06:39.720> of<00:06:39.960> months<00:06:40.560> ago<00:06:40.800> and<00:06:41.400> that<00:06:42.000> leaves 00:06:42.290 --> 00:06:42.300 align:start position:0% a couple of months ago and that leaves 00:06:42.300 --> 00:06:43.790 align:start position:0% a couple of months ago and that leaves us<00:06:42.360> with<00:06:42.539> scurry<00:06:43.020> and<00:06:43.080> sympolia<00:06:43.560> as<00:06:43.680> the 00:06:43.790 --> 00:06:43.800 align:start position:0% us with scurry and sympolia as the 00:06:43.800 --> 00:06:46.370 align:start position:0% us with scurry and sympolia as the latest<00:06:43.919> test<00:06:44.220> nets<00:06:44.639> for<00:06:44.699> ethereum 00:06:46.370 --> 00:06:46.380 align:start position:0% latest test nets for ethereum 00:06:46.380 --> 00:06:48.469 align:start position:0% latest test nets for ethereum and<00:06:46.680> now<00:06:46.860> let's<00:06:46.979> just<00:06:47.280> uh<00:06:47.699> take<00:06:48.000> a<00:06:48.060> look<00:06:48.180> at 00:06:48.469 --> 00:06:48.479 align:start position:0% and now let's just uh take a look at 00:06:48.479 --> 00:06:51.409 align:start position:0% and now let's just uh take a look at what<00:06:48.840> it<00:06:49.020> actually<00:06:49.199> means<00:06:49.620> to<00:06:50.039> merge 00:06:51.409 --> 00:06:51.419 align:start position:0% what it actually means to merge 00:06:51.419 --> 00:06:54.469 align:start position:0% what it actually means to merge uh<00:06:51.960> yeah<00:06:52.080> I<00:06:52.199> took<00:06:52.440> a<00:06:52.560> lot<00:06:52.680> of<00:06:52.800> time<00:06:53.340> to<00:06:53.639> build 00:06:54.469 --> 00:06:54.479 align:start position:0% uh yeah I took a lot of time to build 00:06:54.479 --> 00:06:57.290 align:start position:0% uh yeah I took a lot of time to build these<00:06:54.720> slides<00:06:55.020> so<00:06:55.680> in<00:06:55.979> ethereum<00:06:56.520> this<00:06:56.699> the 00:06:57.290 --> 00:06:57.300 align:start position:0% these slides so in ethereum this the 00:06:57.300 --> 00:06:59.450 align:start position:0% these slides so in ethereum this the merch<00:06:57.660> stands<00:06:57.960> for<00:06:58.020> an<00:06:58.199> event<00:06:58.380> where<00:06:59.220> two 00:06:59.450 --> 00:06:59.460 align:start position:0% merch stands for an event where two 00:06:59.460 --> 00:07:02.689 align:start position:0% merch stands for an event where two blockchains<00:07:00.120> are<00:07:00.479> literally<00:07:00.840> glued<00:07:01.259> together 00:07:02.689 --> 00:07:02.699 align:start position:0% blockchains are literally glued together 00:07:02.699 --> 00:07:05.150 align:start position:0% blockchains are literally glued together you<00:07:03.240> need<00:07:03.600> a<00:07:03.900> consensus<00:07:04.380> layer<00:07:04.680> Beacon<00:07:04.979> chain 00:07:05.150 --> 00:07:05.160 align:start position:0% you need a consensus layer Beacon chain 00:07:05.160 --> 00:07:07.909 align:start position:0% you need a consensus layer Beacon chain that<00:07:05.940> takes<00:07:06.120> over<00:07:06.419> finality<00:07:07.139> and<00:07:07.380> Fork<00:07:07.740> Choice 00:07:07.909 --> 00:07:07.919 align:start position:0% that takes over finality and Fork Choice 00:07:07.919 --> 00:07:09.950 align:start position:0% that takes over finality and Fork Choice considerations 00:07:09.950 --> 00:07:09.960 align:start position:0% considerations 00:07:09.960 --> 00:07:13.070 align:start position:0% considerations here<00:07:10.500> shown<00:07:10.800> in<00:07:10.979> blue 00:07:13.070 --> 00:07:13.080 align:start position:0% here shown in blue 00:07:13.080 --> 00:07:15.409 align:start position:0% here shown in blue um<00:07:13.139> and<00:07:13.380> this<00:07:13.620> consensus<00:07:14.160> layer<00:07:14.520> Beacon<00:07:15.300> chain 00:07:15.409 --> 00:07:15.419 align:start position:0% um and this consensus layer Beacon chain 00:07:15.419 --> 00:07:17.029 align:start position:0% um and this consensus layer Beacon chain replaces<00:07:16.020> the<00:07:16.199> Legacy<00:07:16.500> proof<00:07:16.800> of<00:07:16.860> work 00:07:17.029 --> 00:07:17.039 align:start position:0% replaces the Legacy proof of work 00:07:17.039 --> 00:07:19.790 align:start position:0% replaces the Legacy proof of work consensus<00:07:17.580> or<00:07:18.120> the<00:07:18.419> other<00:07:18.600> consensus<00:07:19.139> uh 00:07:19.790 --> 00:07:19.800 align:start position:0% consensus or the other consensus uh 00:07:19.800 --> 00:07:21.170 align:start position:0% consensus or the other consensus uh mechanisms 00:07:21.170 --> 00:07:21.180 align:start position:0% mechanisms 00:07:21.180 --> 00:07:24.469 align:start position:0% mechanisms on<00:07:21.599> the<00:07:21.840> execution<00:07:22.380> layer<00:07:22.880> here<00:07:23.880> depicted<00:07:24.360> in 00:07:24.469 --> 00:07:24.479 align:start position:0% on the execution layer here depicted in 00:07:24.479 --> 00:07:26.749 align:start position:0% on the execution layer here depicted in red 00:07:26.749 --> 00:07:26.759 align:start position:0% 00:07:26.759 --> 00:07:28.969 align:start position:0% so<00:07:27.120> the<00:07:27.300> slide<00:07:27.660> shows<00:07:28.139> the<00:07:28.319> timeline<00:07:28.680> of<00:07:28.860> the 00:07:28.969 --> 00:07:28.979 align:start position:0% so the slide shows the timeline of the 00:07:28.979 --> 00:07:31.309 align:start position:0% so the slide shows the timeline of the test<00:07:29.099> net<00:07:29.340> mergers 00:07:31.309 --> 00:07:31.319 align:start position:0% test net mergers 00:07:31.319 --> 00:07:34.670 align:start position:0% test net mergers and<00:07:32.220> I<00:07:33.180> added<00:07:33.360> a<00:07:33.419> lot<00:07:33.539> of<00:07:33.660> details<00:07:34.139> here<00:07:34.440> I'm 00:07:34.670 --> 00:07:34.680 align:start position:0% and I added a lot of details here I'm 00:07:34.680 --> 00:07:36.350 align:start position:0% and I added a lot of details here I'm standing<00:07:35.099> in<00:07:35.220> front<00:07:35.400> of<00:07:35.520> it<00:07:35.699> I<00:07:35.940> had<00:07:36.120> a<00:07:36.240> lot<00:07:36.300> of 00:07:36.350 --> 00:07:36.360 align:start position:0% standing in front of it I had a lot of 00:07:36.360 --> 00:07:38.510 align:start position:0% standing in front of it I had a lot of details<00:07:36.720> here<00:07:36.840> but<00:07:37.080> let's<00:07:37.800> revisit<00:07:38.340> this 00:07:38.510 --> 00:07:38.520 align:start position:0% details here but let's revisit this 00:07:38.520 --> 00:07:39.589 align:start position:0% details here but let's revisit this slide 00:07:39.589 --> 00:07:39.599 align:start position:0% slide 00:07:39.599 --> 00:07:40.909 align:start position:0% slide in<00:07:40.080> a<00:07:40.319> bit 00:07:40.909 --> 00:07:40.919 align:start position:0% in a bit 00:07:40.919 --> 00:07:43.550 align:start position:0% in a bit after<00:07:41.639> talking<00:07:42.360> a<00:07:42.660> bit<00:07:42.780> about<00:07:43.080> the 00:07:43.550 --> 00:07:43.560 align:start position:0% after talking a bit about the 00:07:43.560 --> 00:07:45.350 align:start position:0% after talking a bit about the implications 00:07:45.350 --> 00:07:45.360 align:start position:0% implications 00:07:45.360 --> 00:07:47.330 align:start position:0% implications so<00:07:46.440> um 00:07:47.330 --> 00:07:47.340 align:start position:0% so um 00:07:47.340 --> 00:07:49.309 align:start position:0% so um just<00:07:47.759> to<00:07:47.880> recap<00:07:48.120> a<00:07:48.300> proof<00:07:48.599> of<00:07:48.660> work<00:07:48.780> consensus 00:07:49.309 --> 00:07:49.319 align:start position:0% just to recap a proof of work consensus 00:07:49.319 --> 00:07:51.890 align:start position:0% just to recap a proof of work consensus mechanism<00:07:49.740> is<00:07:50.220> permissionless<00:07:51.060> as<00:07:51.419> parental 00:07:51.890 --> 00:07:51.900 align:start position:0% mechanism is permissionless as parental 00:07:51.900 --> 00:07:53.330 align:start position:0% mechanism is permissionless as parental motor<00:07:52.139> consensus 00:07:53.330 --> 00:07:53.340 align:start position:0% motor consensus 00:07:53.340 --> 00:07:55.430 align:start position:0% motor consensus so<00:07:53.759> you<00:07:54.000> can<00:07:54.060> just<00:07:54.180> turn<00:07:54.360> on<00:07:54.599> your<00:07:54.720> CPU<00:07:55.080> Miner 00:07:55.430 --> 00:07:55.440 align:start position:0% so you can just turn on your CPU Miner 00:07:55.440 --> 00:07:57.110 align:start position:0% so you can just turn on your CPU Miner and<00:07:55.560> hope<00:07:55.800> for<00:07:55.979> a<00:07:56.160> block 00:07:57.110 --> 00:07:57.120 align:start position:0% and hope for a block 00:07:57.120 --> 00:07:59.809 align:start position:0% and hope for a block in<00:07:57.300> theory 00:07:59.809 --> 00:07:59.819 align:start position:0% 00:07:59.819 --> 00:08:01.550 align:start position:0% on<00:08:00.180> the<00:08:00.300> other<00:08:00.360> hand<00:08:00.479> a<00:08:00.720> proof<00:08:01.080> of<00:08:01.139> authority 00:08:01.550 --> 00:08:01.560 align:start position:0% on the other hand a proof of authority 00:08:01.560 --> 00:08:03.950 align:start position:0% on the other hand a proof of authority is<00:08:01.860> permissioned<00:08:02.520> obviously<00:08:03.419> only 00:08:03.950 --> 00:08:03.960 align:start position:0% is permissioned obviously only 00:08:03.960 --> 00:08:06.050 align:start position:0% is permissioned obviously only authorized<00:08:04.800> accounts<00:08:05.280> may<00:08:05.460> take<00:08:05.639> part<00:08:05.880> in 00:08:06.050 --> 00:08:06.060 align:start position:0% authorized accounts may take part in 00:08:06.060 --> 00:08:07.249 align:start position:0% authorized accounts may take part in consensus 00:08:07.249 --> 00:08:07.259 align:start position:0% consensus 00:08:07.259 --> 00:08:09.350 align:start position:0% consensus and<00:08:07.860> then<00:08:07.979> again<00:08:08.099> proof<00:08:08.520> of<00:08:08.580> stake<00:08:08.819> is<00:08:09.000> fairly 00:08:09.350 --> 00:08:09.360 align:start position:0% and then again proof of stake is fairly 00:08:09.360 --> 00:08:10.610 align:start position:0% and then again proof of stake is fairly permissionless 00:08:10.610 --> 00:08:10.620 align:start position:0% permissionless 00:08:10.620 --> 00:08:13.730 align:start position:0% permissionless you<00:08:11.160> have<00:08:11.340> a<00:08:11.580> token<00:08:12.240> and<00:08:12.419> you<00:08:12.539> can<00:08:12.660> stake<00:08:12.900> it<00:08:13.080> to 00:08:13.730 --> 00:08:13.740 align:start position:0% you have a token and you can stake it to 00:08:13.740 --> 00:08:15.770 align:start position:0% you have a token and you can stake it to take<00:08:14.280> part<00:08:14.460> in<00:08:14.639> consensus 00:08:15.770 --> 00:08:15.780 align:start position:0% take part in consensus 00:08:15.780 --> 00:08:18.890 align:start position:0% take part in consensus so<00:08:16.319> what<00:08:16.740> does<00:08:16.860> it<00:08:16.979> mean<00:08:17.099> for<00:08:17.340> SEO<00:08:17.699> mainnet<00:08:18.180> the 00:08:18.890 --> 00:08:18.900 align:start position:0% so what does it mean for SEO mainnet the 00:08:18.900 --> 00:08:21.350 align:start position:0% so what does it mean for SEO mainnet the merge<00:08:19.259> obviously<00:08:19.699> moving<00:08:20.699> from<00:08:20.879> proof<00:08:21.240> of 00:08:21.350 --> 00:08:21.360 align:start position:0% merge obviously moving from proof of 00:08:21.360 --> 00:08:23.570 align:start position:0% merge obviously moving from proof of work<00:08:21.539> to<00:08:22.199> proof<00:08:22.500> of<00:08:22.560> stake 00:08:23.570 --> 00:08:23.580 align:start position:0% work to proof of stake 00:08:23.580 --> 00:08:24.290 align:start position:0% work to proof of stake um 00:08:24.290 --> 00:08:24.300 align:start position:0% um 00:08:24.300 --> 00:08:25.909 align:start position:0% um just<00:08:24.780> does<00:08:24.900> not<00:08:25.080> change<00:08:25.259> much<00:08:25.560> in<00:08:25.740> this 00:08:25.909 --> 00:08:25.919 align:start position:0% just does not change much in this 00:08:25.919 --> 00:08:27.710 align:start position:0% just does not change much in this perspective<00:08:26.280> it<00:08:26.580> was<00:08:26.759> permissionless<00:08:27.360> before 00:08:27.710 --> 00:08:27.720 align:start position:0% perspective it was permissionless before 00:08:27.720 --> 00:08:30.589 align:start position:0% perspective it was permissionless before the<00:08:28.199> merge<00:08:28.560> is<00:08:28.919> still<00:08:29.759> permissionless<00:08:30.360> after 00:08:30.589 --> 00:08:30.599 align:start position:0% the merge is still permissionless after 00:08:30.599 --> 00:08:32.209 align:start position:0% the merge is still permissionless after the<00:08:30.840> merge 00:08:32.209 --> 00:08:32.219 align:start position:0% the merge 00:08:32.219 --> 00:08:34.550 align:start position:0% the merge but<00:08:32.580> how<00:08:32.820> does<00:08:32.940> it<00:08:33.120> look<00:08:33.240> like<00:08:33.479> for<00:08:33.899> the<00:08:34.140> test 00:08:34.550 --> 00:08:34.560 align:start position:0% but how does it look like for the test 00:08:34.560 --> 00:08:35.930 align:start position:0% but how does it look like for the test Nets 00:08:35.930 --> 00:08:35.940 align:start position:0% Nets 00:08:35.940 --> 00:08:39.769 align:start position:0% Nets so<00:08:36.300> girly<00:08:36.899> was<00:08:37.459> merged<00:08:38.459> with<00:08:38.640> a<00:08:38.820> beacon<00:08:39.659> chain 00:08:39.769 --> 00:08:39.779 align:start position:0% so girly was merged with a beacon chain 00:08:39.779 --> 00:08:41.029 align:start position:0% so girly was merged with a beacon chain test<00:08:40.020> net 00:08:41.029 --> 00:08:41.039 align:start position:0% test net 00:08:41.039 --> 00:08:43.070 align:start position:0% test net and<00:08:42.419> um 00:08:43.070 --> 00:08:43.080 align:start position:0% and um 00:08:43.080 --> 00:08:46.250 align:start position:0% and um to<00:08:43.620> access 00:08:46.250 --> 00:08:46.260 align:start position:0% 00:08:46.260 --> 00:08:48.410 align:start position:0% to<00:08:46.740> get<00:08:46.800> access<00:08:46.980> to<00:08:47.279> the<00:08:47.519> consensus<00:08:48.000> on<00:08:48.300> the 00:08:48.410 --> 00:08:48.420 align:start position:0% to get access to the consensus on the 00:08:48.420 --> 00:08:51.410 align:start position:0% to get access to the consensus on the growly<00:08:48.779> test<00:08:48.959> net<00:08:49.200> prior<00:08:49.800> to<00:08:49.920> the<00:08:50.040> merge<00:08:50.459> uh 00:08:51.410 --> 00:08:51.420 align:start position:0% growly test net prior to the merge uh 00:08:51.420 --> 00:08:54.590 align:start position:0% growly test net prior to the merge uh was<00:08:51.600> con<00:08:51.959> was<00:08:52.680> permissioned<00:08:53.279> so<00:08:53.760> girly<00:08:54.240> was 00:08:54.590 --> 00:08:54.600 align:start position:0% was con was permissioned so girly was 00:08:54.600 --> 00:08:56.630 align:start position:0% was con was permissioned so girly was running<00:08:55.080> a<00:08:55.500> community<00:08:55.680> maintained<00:08:56.459> Valley 00:08:56.630 --> 00:08:56.640 align:start position:0% running a community maintained Valley 00:08:56.640 --> 00:08:58.009 align:start position:0% running a community maintained Valley data<00:08:57.060> set 00:08:58.009 --> 00:08:58.019 align:start position:0% data set 00:08:58.019 --> 00:09:01.430 align:start position:0% data set however<00:08:58.980> after<00:08:59.700> the<00:08:59.940> merge<00:09:00.360> it<00:09:00.660> transitioned 00:09:01.430 --> 00:09:01.440 align:start position:0% however after the merge it transitioned 00:09:01.440 --> 00:09:02.930 align:start position:0% however after the merge it transitioned to<00:09:01.680> a<00:09:01.800> proof<00:09:02.040> of<00:09:02.160> stake<00:09:02.399> consensus 00:09:02.930 --> 00:09:02.940 align:start position:0% to a proof of stake consensus 00:09:02.940 --> 00:09:06.710 align:start position:0% to a proof of stake consensus interestingly<00:09:03.720> and<00:09:03.959> suddenly<00:09:04.320> everyone<00:09:05.100> can 00:09:06.710 --> 00:09:06.720 align:start position:0% interestingly and suddenly everyone can 00:09:06.720 --> 00:09:10.190 align:start position:0% interestingly and suddenly everyone can participate<00:09:07.680> in<00:09:08.459> consensus 00:09:10.190 --> 00:09:10.200 align:start position:0% participate in consensus 00:09:10.200 --> 00:09:14.269 align:start position:0% participate in consensus given<00:09:10.860> you<00:09:11.160> have<00:09:11.339> access<00:09:11.519> to<00:09:11.820> girlies 00:09:14.269 --> 00:09:14.279 align:start position:0% given you have access to girlies 00:09:14.279 --> 00:09:17.509 align:start position:0% given you have access to girlies so<00:09:15.080> girly<00:09:16.080> used<00:09:16.380> to<00:09:16.500> be<00:09:16.620> permissioned<00:09:17.160> is<00:09:17.339> now 00:09:17.509 --> 00:09:17.519 align:start position:0% so girly used to be permissioned is now 00:09:17.519 --> 00:09:20.509 align:start position:0% so girly used to be permissioned is now permissionless 00:09:20.509 --> 00:09:20.519 align:start position:0% 00:09:20.519 --> 00:09:22.910 align:start position:0% but<00:09:20.940> what<00:09:21.060> about<00:09:21.240> zipolia 00:09:22.910 --> 00:09:22.920 align:start position:0% but what about zipolia 00:09:22.920 --> 00:09:24.949 align:start position:0% but what about zipolia um<00:09:22.980> as<00:09:23.279> I<00:09:23.399> mentioned<00:09:23.640> prior<00:09:24.180> to<00:09:24.300> the<00:09:24.420> merge<00:09:24.720> it 00:09:24.949 --> 00:09:24.959 align:start position:0% um as I mentioned prior to the merge it 00:09:24.959 --> 00:09:27.710 align:start position:0% um as I mentioned prior to the merge it was<00:09:25.140> powered<00:09:25.560> by<00:09:25.920> the<00:09:26.820> permissionless<00:09:27.300> esash 00:09:27.710 --> 00:09:27.720 align:start position:0% was powered by the permissionless esash 00:09:27.720 --> 00:09:29.930 align:start position:0% was powered by the permissionless esash a<00:09:27.899> proof<00:09:28.080> of<00:09:28.200> work<00:09:28.320> algorithm<00:09:29.279> here<00:09:29.700> you<00:09:29.760> can 00:09:29.930 --> 00:09:29.940 align:start position:0% a proof of work algorithm here you can 00:09:29.940 --> 00:09:32.389 align:start position:0% a proof of work algorithm here you can see<00:09:30.060> my<00:09:30.360> sepolia<00:09:31.019> Miner<00:09:31.380> I<00:09:31.740> was<00:09:31.860> happy<00:09:31.980> that<00:09:32.220> I 00:09:32.389 --> 00:09:32.399 align:start position:0% see my sepolia Miner I was happy that I 00:09:32.399 --> 00:09:35.870 align:start position:0% see my sepolia Miner I was happy that I once<00:09:32.700> again<00:09:32.760> can<00:09:33.180> mine<00:09:34.019> a<00:09:34.200> test<00:09:34.320> net 00:09:35.870 --> 00:09:35.880 align:start position:0% once again can mine a test net 00:09:35.880 --> 00:09:37.970 align:start position:0% once again can mine a test net um<00:09:36.000> and<00:09:36.540> yeah<00:09:36.720> I<00:09:36.899> did<00:09:37.019> not<00:09:37.140> ask<00:09:37.440> for<00:09:37.620> permission 00:09:37.970 --> 00:09:37.980 align:start position:0% um and yeah I did not ask for permission 00:09:37.980 --> 00:09:40.550 align:start position:0% um and yeah I did not ask for permission I<00:09:38.279> can<00:09:38.399> just<00:09:38.580> I<00:09:39.000> was<00:09:39.240> just<00:09:39.600> able<00:09:39.959> to<00:09:40.080> mine<00:09:40.380> the 00:09:40.550 --> 00:09:40.560 align:start position:0% I can just I was just able to mine the 00:09:40.560 --> 00:09:44.389 align:start position:0% I can just I was just able to mine the blocks<00:09:40.920> I<00:09:41.100> got<00:09:41.279> a<00:09:41.580> lot<00:09:41.700> of<00:09:41.820> zipolia<00:09:42.480> either 00:09:44.389 --> 00:09:44.399 align:start position:0% blocks I got a lot of zipolia either 00:09:44.399 --> 00:09:46.370 align:start position:0% blocks I got a lot of zipolia either um 00:09:46.370 --> 00:09:46.380 align:start position:0% um 00:09:46.380 --> 00:09:49.490 align:start position:0% um but<00:09:47.100> now<00:09:47.220> there's<00:09:47.519> something<00:09:47.820> unique<00:09:48.360> about 00:09:49.490 --> 00:09:49.500 align:start position:0% but now there's something unique about 00:09:49.500 --> 00:09:52.970 align:start position:0% but now there's something unique about um the<00:09:50.220> C<00:09:50.339> polier<00:09:50.760> Beacon<00:09:51.120> chain 00:09:52.970 --> 00:09:52.980 align:start position:0% um the C polier Beacon chain 00:09:52.980 --> 00:09:56.690 align:start position:0% um the C polier Beacon chain um<00:09:53.100> since<00:09:53.640> it<00:09:53.940> was<00:09:54.260> apparent<00:09:55.260> that<00:09:55.500> girly<00:09:55.980> will 00:09:56.690 --> 00:09:56.700 align:start position:0% um since it was apparent that girly will 00:09:56.700 --> 00:09:59.810 align:start position:0% um since it was apparent that girly will no<00:09:57.240> longer<00:09:57.540> be<00:09:58.019> permissioned<00:09:58.980> there<00:09:59.580> was 00:09:59.810 --> 00:09:59.820 align:start position:0% no longer be permissioned there was 00:09:59.820 --> 00:10:03.290 align:start position:0% no longer be permissioned there was actually<00:10:00.680> the<00:10:01.680> the<00:10:02.459> Quest<00:10:02.760> for<00:10:03.060> having 00:10:03.290 --> 00:10:03.300 align:start position:0% actually the the Quest for having 00:10:03.300 --> 00:10:04.630 align:start position:0% actually the the Quest for having another 00:10:04.630 --> 00:10:04.640 align:start position:0% another 00:10:04.640 --> 00:10:09.050 align:start position:0% another permission<00:10:05.640> test<00:10:06.240> net<00:10:06.480> to<00:10:07.019> have<00:10:07.700> a<00:10:08.700> certain 00:10:09.050 --> 00:10:09.060 align:start position:0% permission test net to have a certain 00:10:09.060 --> 00:10:10.790 align:start position:0% permission test net to have a certain stability<00:10:09.480> guarantees 00:10:10.790 --> 00:10:10.800 align:start position:0% stability guarantees 00:10:10.800 --> 00:10:14.570 align:start position:0% stability guarantees so<00:10:11.880> it<00:10:12.660> was<00:10:12.839> decided<00:10:13.380> that<00:10:13.560> the<00:10:13.740> polio<00:10:14.220> gets<00:10:14.519> a 00:10:14.570 --> 00:10:14.580 align:start position:0% so it was decided that the polio gets a 00:10:14.580 --> 00:10:16.850 align:start position:0% so it was decided that the polio gets a beacon<00:10:14.880> chain<00:10:15.060> with<00:10:15.480> a<00:10:15.899> modified<00:10:16.260> deposit 00:10:16.850 --> 00:10:16.860 align:start position:0% beacon chain with a modified deposit 00:10:16.860 --> 00:10:18.829 align:start position:0% beacon chain with a modified deposit contract<00:10:17.220> that<00:10:17.399> does<00:10:17.700> not<00:10:17.880> accept<00:10:18.120> regular 00:10:18.829 --> 00:10:18.839 align:start position:0% contract that does not accept regular 00:10:18.839 --> 00:10:21.470 align:start position:0% contract that does not accept regular ether<00:10:19.440> deposits 00:10:21.470 --> 00:10:21.480 align:start position:0% ether deposits 00:10:21.480 --> 00:10:24.530 align:start position:0% ether deposits instead<00:10:22.260> attracts<00:10:22.800> the<00:10:23.760> valid<00:10:24.060> data<00:10:24.300> sets 00:10:24.530 --> 00:10:24.540 align:start position:0% instead attracts the valid data sets 00:10:24.540 --> 00:10:27.170 align:start position:0% instead attracts the valid data sets through<00:10:24.660> an<00:10:24.779> erc20<00:10:25.260> token 00:10:27.170 --> 00:10:27.180 align:start position:0% through an erc20 token 00:10:27.180 --> 00:10:29.990 align:start position:0% through an erc20 token so<00:10:27.660> in<00:10:27.959> that<00:10:28.080> case<00:10:28.320> zipolia<00:10:29.220> is<00:10:29.459> a<00:10:29.640> proof<00:10:29.940> of 00:10:29.990 --> 00:10:30.000 align:start position:0% so in that case zipolia is a proof of 00:10:30.000 --> 00:10:32.630 align:start position:0% so in that case zipolia is a proof of authority<00:10:30.540> version<00:10:30.839> of<00:10:31.440> The<00:10:32.100> Beacon<00:10:32.459> chain 00:10:32.630 --> 00:10:32.640 align:start position:0% authority version of The Beacon chain 00:10:32.640 --> 00:10:35.870 align:start position:0% authority version of The Beacon chain and<00:10:33.240> therefore<00:10:33.600> the<00:10:34.080> access<00:10:34.260> to<00:10:34.860> the<00:10:35.459> polio 00:10:35.870 --> 00:10:35.880 align:start position:0% and therefore the access to the polio 00:10:35.880 --> 00:10:38.269 align:start position:0% and therefore the access to the polio consensus<00:10:36.300> is<00:10:36.480> permissioned 00:10:38.269 --> 00:10:38.279 align:start position:0% consensus is permissioned 00:10:38.279 --> 00:10:40.070 align:start position:0% consensus is permissioned so<00:10:38.640> let's<00:10:38.820> take<00:10:39.180> a<00:10:39.300> look<00:10:39.420> at<00:10:39.540> this<00:10:39.720> overview 00:10:40.070 --> 00:10:40.080 align:start position:0% so let's take a look at this overview 00:10:40.080 --> 00:10:41.030 align:start position:0% so let's take a look at this overview again 00:10:41.030 --> 00:10:41.040 align:start position:0% again 00:10:41.040 --> 00:10:42.110 align:start position:0% again um 00:10:42.110 --> 00:10:42.120 align:start position:0% um 00:10:42.120 --> 00:10:43.730 align:start position:0% um this<00:10:42.540> is<00:10:42.600> a<00:10:42.779> timeline<00:10:43.080> actually<00:10:43.320> on<00:10:43.560> the 00:10:43.730 --> 00:10:43.740 align:start position:0% this is a timeline actually on the 00:10:43.740 --> 00:10:45.310 align:start position:0% this is a timeline actually on the x-axis<00:10:44.160> axis 00:10:45.310 --> 00:10:45.320 align:start position:0% x-axis axis 00:10:45.320 --> 00:10:49.449 align:start position:0% x-axis axis the<00:10:46.320> first<00:10:46.500> test<00:10:46.860> net<00:10:47.100> to<00:10:47.399> merge<00:10:47.640> was<00:10:47.760> rubson 00:10:49.449 --> 00:10:49.459 align:start position:0% the first test net to merge was rubson 00:10:49.459 --> 00:10:52.550 align:start position:0% the first test net to merge was rubson was<00:10:50.459> fairly<00:10:51.000> similar<00:10:51.300> to<00:10:51.420> mainnet<00:10:51.839> it<00:10:52.380> was 00:10:52.550 --> 00:10:52.560 align:start position:0% was fairly similar to mainnet it was 00:10:52.560 --> 00:10:54.290 align:start position:0% was fairly similar to mainnet it was proof<00:10:52.920> of<00:10:52.980> work 00:10:54.290 --> 00:10:54.300 align:start position:0% proof of work 00:10:54.300 --> 00:10:56.269 align:start position:0% proof of work and<00:10:54.839> after<00:10:54.959> the<00:10:55.200> merge<00:10:55.500> it<00:10:55.620> was<00:10:55.800> proof<00:10:56.160> of 00:10:56.269 --> 00:10:56.279 align:start position:0% and after the merge it was proof of 00:10:56.279 --> 00:10:58.970 align:start position:0% and after the merge it was proof of stake<00:10:56.579> right<00:10:56.880> so<00:10:57.420> permission<00:10:57.980> less 00:10:58.970 --> 00:10:58.980 align:start position:0% stake right so permission less 00:10:58.980 --> 00:11:01.430 align:start position:0% stake right so permission less permission<00:10:59.579> less 00:11:01.430 --> 00:11:01.440 align:start position:0% permission less 00:11:01.440 --> 00:11:04.910 align:start position:0% permission less then<00:11:02.339> zipolia<00:11:03.000> transitioned 00:11:04.910 --> 00:11:04.920 align:start position:0% then zipolia transitioned 00:11:04.920 --> 00:11:08.990 align:start position:0% then zipolia transitioned with<00:11:05.579> this<00:11:06.000> modified<00:11:06.920> Beacon<00:11:07.920> chain 00:11:08.990 --> 00:11:09.000 align:start position:0% with this modified Beacon chain 00:11:09.000 --> 00:11:10.610 align:start position:0% with this modified Beacon chain so<00:11:09.360> technically<00:11:09.660> the<00:11:09.839> consensus<00:11:10.260> algorithm 00:11:10.610 --> 00:11:10.620 align:start position:0% so technically the consensus algorithm 00:11:10.620 --> 00:11:12.410 align:start position:0% so technically the consensus algorithm is<00:11:10.800> still<00:11:10.920> proof<00:11:11.220> of<00:11:11.279> stake<00:11:11.519> but<00:11:11.820> through<00:11:12.120> this 00:11:12.410 --> 00:11:12.420 align:start position:0% is still proof of stake but through this 00:11:12.420 --> 00:11:14.509 align:start position:0% is still proof of stake but through this permission 00:11:14.509 --> 00:11:14.519 align:start position:0% permission 00:11:14.519 --> 00:11:16.130 align:start position:0% permission um 00:11:16.130 --> 00:11:16.140 align:start position:0% um 00:11:16.140 --> 00:11:18.350 align:start position:0% um esc20<00:11:16.920> token<00:11:17.279> that<00:11:17.399> you<00:11:17.579> require<00:11:17.760> to<00:11:18.180> take 00:11:18.350 --> 00:11:18.360 align:start position:0% esc20 token that you require to take 00:11:18.360 --> 00:11:20.930 align:start position:0% esc20 token that you require to take part<00:11:18.540> in<00:11:18.839> consensus<00:11:19.440> I<00:11:20.160> call<00:11:20.279> it<00:11:20.519> for 00:11:20.930 --> 00:11:20.940 align:start position:0% part in consensus I call it for 00:11:20.940 --> 00:11:22.690 align:start position:0% part in consensus I call it for Simplicity<00:11:21.480> proof<00:11:21.899> of<00:11:21.899> authority<00:11:22.320> here 00:11:22.690 --> 00:11:22.700 align:start position:0% Simplicity proof of authority here 00:11:22.700 --> 00:11:25.670 align:start position:0% Simplicity proof of authority here because<00:11:23.700> access<00:11:24.300> to<00:11:24.600> this<00:11:24.839> consensus<00:11:25.380> is 00:11:25.670 --> 00:11:25.680 align:start position:0% because access to this consensus is 00:11:25.680 --> 00:11:28.370 align:start position:0% because access to this consensus is actually<00:11:25.860> permissioned 00:11:28.370 --> 00:11:28.380 align:start position:0% actually permissioned 00:11:28.380 --> 00:11:29.269 align:start position:0% actually permissioned um 00:11:29.269 --> 00:11:29.279 align:start position:0% um 00:11:29.279 --> 00:11:30.889 align:start position:0% um and<00:11:29.940> then 00:11:30.889 --> 00:11:30.899 align:start position:0% and then 00:11:30.899 --> 00:11:33.470 align:start position:0% and then girly<00:11:31.620> merge<00:11:32.160> was<00:11:32.279> Prada<00:11:32.640> and<00:11:32.880> test<00:11:33.060> net<00:11:33.240> were 00:11:33.470 --> 00:11:33.480 align:start position:0% girly merge was Prada and test net were 00:11:33.480 --> 00:11:35.870 align:start position:0% girly merge was Prada and test net were exactly<00:11:33.839> the<00:11:33.959> opposite<00:11:34.260> happened<00:11:34.500> uh 00:11:35.870 --> 00:11:35.880 align:start position:0% exactly the opposite happened uh 00:11:35.880 --> 00:11:38.210 align:start position:0% exactly the opposite happened uh the<00:11:36.420> proof<00:11:36.720> of<00:11:36.779> authority<00:11:37.320> test<00:11:37.860> and<00:11:38.040> it 00:11:38.210 --> 00:11:38.220 align:start position:0% the proof of authority test and it 00:11:38.220 --> 00:11:40.550 align:start position:0% the proof of authority test and it became<00:11:38.459> a<00:11:38.640> proof<00:11:38.880> of<00:11:38.940> stake<00:11:39.300> girly<00:11:40.140> test<00:11:40.380> net 00:11:40.550 --> 00:11:40.560 align:start position:0% became a proof of stake girly test net 00:11:40.560 --> 00:11:42.590 align:start position:0% became a proof of stake girly test net after<00:11:41.279> the<00:11:41.579> merge 00:11:42.590 --> 00:11:42.600 align:start position:0% after the merge 00:11:42.600 --> 00:11:45.050 align:start position:0% after the merge and<00:11:42.959> then<00:11:43.079> yeah<00:11:43.200> we<00:11:43.740> are<00:11:43.860> here<00:11:44.060> eventually 00:11:45.050 --> 00:11:45.060 align:start position:0% and then yeah we are here eventually 00:11:45.060 --> 00:11:46.910 align:start position:0% and then yeah we are here eventually just<00:11:45.360> a<00:11:45.540> couple<00:11:45.660> of<00:11:45.720> weeks<00:11:46.019> ago<00:11:46.200> the<00:11:46.380> mainnet 00:11:46.910 --> 00:11:46.920 align:start position:0% just a couple of weeks ago the mainnet 00:11:46.920 --> 00:11:50.509 align:start position:0% just a couple of weeks ago the mainnet merge<00:11:47.339> occurred<00:11:48.240> so<00:11:48.540> yeah<00:11:48.660> just<00:11:49.339> take<00:11:50.339> a<00:11:50.399> look 00:11:50.509 --> 00:11:50.519 align:start position:0% merge occurred so yeah just take a look 00:11:50.519 --> 00:11:53.389 align:start position:0% merge occurred so yeah just take a look at<00:11:50.640> the<00:11:50.820> post<00:11:51.120> merge<00:11:51.839> test<00:11:52.019> net<00:11:52.260> landscape<00:11:52.800> I 00:11:53.389 --> 00:11:53.399 align:start position:0% at the post merge test net landscape I 00:11:53.399 --> 00:11:56.630 align:start position:0% at the post merge test net landscape I showed<00:11:53.700> you<00:11:53.820> that<00:11:54.000> groups<00:11:54.660> merged<00:11:55.560> however<00:11:56.399> it 00:11:56.630 --> 00:11:56.640 align:start position:0% showed you that groups merged however it 00:11:56.640 --> 00:11:58.850 align:start position:0% showed you that groups merged however it has<00:11:56.820> been<00:11:56.940> deprecated<00:11:57.480> by<00:11:58.079> the<00:11:58.260> ethereum 00:11:58.850 --> 00:11:58.860 align:start position:0% has been deprecated by the ethereum 00:11:58.860 --> 00:12:02.810 align:start position:0% has been deprecated by the ethereum foundations<00:11:59.220> a<00:11:59.579> protocol<00:11:59.820> support<00:12:00.120> team 00:12:02.810 --> 00:12:02.820 align:start position:0% 00:12:02.820 --> 00:12:06.170 align:start position:0% and<00:12:03.720> it<00:12:03.959> leaves<00:12:04.260> us<00:12:04.440> with<00:12:04.980> uh<00:12:05.700> girly<00:12:06.060> and 00:12:06.170 --> 00:12:06.180 align:start position:0% and it leaves us with uh girly and 00:12:06.180 --> 00:12:08.509 align:start position:0% and it leaves us with uh girly and simpleia<00:12:06.660> is<00:12:06.899> the<00:12:07.079> only<00:12:07.200> long-standing 00:12:08.509 --> 00:12:08.519 align:start position:0% simpleia is the only long-standing 00:12:08.519 --> 00:12:13.610 align:start position:0% simpleia is the only long-standing public<00:12:09.060> post<00:12:09.600> merge<00:12:10.140> test<00:12:10.320> Nets 00:12:13.610 --> 00:12:13.620 align:start position:0% 00:12:13.620 --> 00:12:16.009 align:start position:0% so<00:12:14.220> I<00:12:14.519> will<00:12:14.700> conclude<00:12:15.000> my<00:12:15.240> presentation<00:12:15.660> with 00:12:16.009 --> 00:12:16.019 align:start position:0% so I will conclude my presentation with 00:12:16.019 --> 00:12:17.509 align:start position:0% so I will conclude my presentation with the 00:12:17.509 --> 00:12:17.519 align:start position:0% the 00:12:17.519 --> 00:12:19.790 align:start position:0% the test<00:12:17.940> net<00:12:18.180> selection<00:12:18.660> guide 00:12:19.790 --> 00:12:19.800 align:start position:0% test net selection guide 00:12:19.800 --> 00:12:21.590 align:start position:0% test net selection guide I<00:12:20.160> mean<00:12:20.279> it's<00:12:20.339> only<00:12:20.579> two<00:12:20.700> testers<00:12:21.060> how<00:12:21.300> hard 00:12:21.590 --> 00:12:21.600 align:start position:0% I mean it's only two testers how hard 00:12:21.600 --> 00:12:24.710 align:start position:0% I mean it's only two testers how hard can<00:12:21.779> it<00:12:21.959> be 00:12:24.710 --> 00:12:24.720 align:start position:0% 00:12:24.720 --> 00:12:26.389 align:start position:0% I<00:12:25.620> um 00:12:26.389 --> 00:12:26.399 align:start position:0% I um 00:12:26.399 --> 00:12:28.430 align:start position:0% I um I<00:12:26.820> mentioned<00:12:27.060> how<00:12:27.240> amazing<00:12:27.540> Museum<00:12:27.779> block<00:12:28.200> is 00:12:28.430 --> 00:12:28.440 align:start position:0% I mentioned how amazing Museum block is 00:12:28.440 --> 00:12:30.889 align:start position:0% I mentioned how amazing Museum block is it's<00:12:29.339> just<00:12:29.700> a 00:12:30.889 --> 00:12:30.899 align:start position:0% it's just a 00:12:30.899 --> 00:12:33.410 align:start position:0% it's just a great<00:12:31.320> resource<00:12:31.680> I<00:12:31.920> found<00:12:32.100> this<00:12:32.339> slide<00:12:32.700> on<00:12:33.060> on 00:12:33.410 --> 00:12:33.420 align:start position:0% great resource I found this slide on on 00:12:33.420 --> 00:12:35.750 align:start position:0% great resource I found this slide on on the<00:12:33.660> ethereum<00:12:34.079> Block 00:12:35.750 --> 00:12:35.760 align:start position:0% the ethereum Block 00:12:35.760 --> 00:12:36.769 align:start position:0% the ethereum Block um 00:12:36.769 --> 00:12:36.779 align:start position:0% um 00:12:36.779 --> 00:12:39.170 align:start position:0% um basically<00:12:37.500> just<00:12:37.620> Recaps<00:12:38.100> what<00:12:38.220> I<00:12:38.399> just<00:12:38.519> said 00:12:39.170 --> 00:12:39.180 align:start position:0% basically just Recaps what I just said 00:12:39.180 --> 00:12:41.030 align:start position:0% basically just Recaps what I just said um 00:12:41.030 --> 00:12:41.040 align:start position:0% um 00:12:41.040 --> 00:12:43.490 align:start position:0% um the<00:12:41.640> open<00:12:41.760> value<00:12:42.000> data<00:12:42.360> set<00:12:42.420> for<00:12:42.600> girly<00:12:42.959> on<00:12:43.380> the 00:12:43.490 --> 00:12:43.500 align:start position:0% the open value data set for girly on the 00:12:43.500 --> 00:12:45.170 align:start position:0% the open value data set for girly on the one<00:12:43.620> hand<00:12:43.740> the<00:12:44.160> closed<00:12:44.459> value<00:12:44.579> data<00:12:44.940> set<00:12:45.000> for 00:12:45.170 --> 00:12:45.180 align:start position:0% one hand the closed value data set for 00:12:45.180 --> 00:12:47.449 align:start position:0% one hand the closed value data set for zipolia<00:12:45.660> on<00:12:45.839> the<00:12:45.959> other<00:12:46.019> hand 00:12:47.449 --> 00:12:47.459 align:start position:0% zipolia on the other hand 00:12:47.459 --> 00:12:49.730 align:start position:0% zipolia on the other hand um obviously<00:12:48.300> since<00:12:48.540> Gurley<00:12:49.019> is<00:12:49.200> much<00:12:49.380> older 00:12:49.730 --> 00:12:49.740 align:start position:0% um obviously since Gurley is much older 00:12:49.740 --> 00:12:52.449 align:start position:0% um obviously since Gurley is much older it<00:12:49.920> has<00:12:50.040> a<00:12:50.160> large<00:12:50.279> state 00:12:52.449 --> 00:12:52.459 align:start position:0% it has a large state 00:12:52.459 --> 00:12:56.629 align:start position:0% it has a large state that<00:12:53.459> gives<00:12:54.360> some<00:12:55.260> better<00:12:55.620> Network<00:12:55.980> effect<00:12:56.339> so 00:12:56.629 --> 00:12:56.639 align:start position:0% that gives some better Network effect so 00:12:56.639 --> 00:12:58.129 align:start position:0% that gives some better Network effect so if<00:12:56.820> you<00:12:56.940> have<00:12:57.060> an<00:12:57.300> application<00:12:57.660> that<00:12:57.899> you<00:12:58.019> want 00:12:58.129 --> 00:12:58.139 align:start position:0% if you have an application that you want 00:12:58.139 --> 00:12:59.930 align:start position:0% if you have an application that you want to<00:12:58.260> deploy<00:12:58.620> Deploy<00:12:59.220> on<00:12:59.279> girly<00:12:59.639> and<00:12:59.820> you 00:12:59.930 --> 00:12:59.940 align:start position:0% to deploy Deploy on girly and you 00:12:59.940 --> 00:13:02.150 align:start position:0% to deploy Deploy on girly and you require<00:13:00.180> other<00:13:00.660> applications<00:13:01.139> or<00:13:01.440> interfaces 00:13:02.150 --> 00:13:02.160 align:start position:0% require other applications or interfaces 00:13:02.160 --> 00:13:05.569 align:start position:0% require other applications or interfaces you<00:13:02.940> might<00:13:03.120> find<00:13:03.420> some<00:13:03.600> on<00:13:04.139> the<00:13:04.320> polio<00:13:04.680> girly 00:13:05.569 --> 00:13:05.579 align:start position:0% you might find some on the polio girly 00:13:05.579 --> 00:13:07.430 align:start position:0% you might find some on the polio girly but<00:13:05.700> not<00:13:05.820> on<00:13:05.940> the<00:13:06.120> polio<00:13:06.480> because<00:13:06.660> the<00:13:07.079> polio 00:13:07.430 --> 00:13:07.440 align:start position:0% but not on the polio because the polio 00:13:07.440 --> 00:13:08.810 align:start position:0% but not on the polio because the polio is<00:13:07.560> fairly<00:13:07.800> new<00:13:07.920> and<00:13:08.100> not<00:13:08.220> many<00:13:08.399> applications 00:13:08.810 --> 00:13:08.820 align:start position:0% is fairly new and not many applications 00:13:08.820 --> 00:13:11.690 align:start position:0% is fairly new and not many applications and<00:13:09.360> libraries<00:13:09.660> are<00:13:09.839> deployed<00:13:10.260> yet 00:13:11.690 --> 00:13:11.700 align:start position:0% and libraries are deployed yet 00:13:11.700 --> 00:13:14.150 align:start position:0% and libraries are deployed yet however<00:13:12.360> it's<00:13:12.540> also<00:13:12.839> longer<00:13:13.260> to<00:13:13.380> sink<00:13:13.560> and 00:13:14.150 --> 00:13:14.160 align:start position:0% however it's also longer to sink and 00:13:14.160 --> 00:13:16.009 align:start position:0% however it's also longer to sink and more<00:13:14.339> involved<00:13:14.760> to<00:13:14.880> run<00:13:15.060> girly 00:13:16.009 --> 00:13:16.019 align:start position:0% more involved to run girly 00:13:16.019 --> 00:13:18.530 align:start position:0% more involved to run girly infrastructure 00:13:18.530 --> 00:13:18.540 align:start position:0% infrastructure 00:13:18.540 --> 00:13:21.829 align:start position:0% infrastructure so<00:13:19.260> to<00:13:19.980> summarize<00:13:20.339> this 00:13:21.829 --> 00:13:21.839 align:start position:0% so to summarize this 00:13:21.839 --> 00:13:24.769 align:start position:0% so to summarize this please<00:13:22.200> do<00:13:22.500> use<00:13:22.680> girly<00:13:23.220> test<00:13:23.880> net<00:13:24.060> as<00:13:24.420> it<00:13:24.600> is 00:13:24.769 --> 00:13:24.779 align:start position:0% please do use girly test net as it is 00:13:24.779 --> 00:13:29.990 align:start position:0% please do use girly test net as it is most<00:13:25.079> similar<00:13:25.680> to<00:13:26.040> the<00:13:26.399> ethium<00:13:26.940> mainnet 00:13:29.990 --> 00:13:30.000 align:start position:0% 00:13:30.000 --> 00:13:31.970 align:start position:0% girly<00:13:30.540> is<00:13:30.839> especially<00:13:31.380> interesting<00:13:31.740> for<00:13:31.920> you 00:13:31.970 --> 00:13:31.980 align:start position:0% girly is especially interesting for you 00:13:31.980 --> 00:13:34.129 align:start position:0% girly is especially interesting for you if<00:13:32.160> you<00:13:32.339> plan<00:13:32.579> to<00:13:32.820> test<00:13:33.480> a<00:13:33.660> beacon<00:13:34.019> chain 00:13:34.129 --> 00:13:34.139 align:start position:0% if you plan to test a beacon chain 00:13:34.139 --> 00:13:37.190 align:start position:0% if you plan to test a beacon chain validator<00:13:34.680> if<00:13:35.399> you<00:13:35.519> want<00:13:35.760> to<00:13:35.880> test<00:13:36.300> your<00:13:36.839> setup 00:13:37.190 --> 00:13:37.200 align:start position:0% validator if you want to test your setup 00:13:37.200 --> 00:13:39.650 align:start position:0% validator if you want to test your setup if<00:13:37.500> you<00:13:37.620> want<00:13:37.800> to<00:13:37.980> test<00:13:38.279> upgrading<00:13:39.180> client 00:13:39.650 --> 00:13:39.660 align:start position:0% if you want to test upgrading client 00:13:39.660 --> 00:13:42.769 align:start position:0% if you want to test upgrading client versions<00:13:40.079> if<00:13:40.320> you<00:13:40.440> want<00:13:40.620> to<00:13:40.740> test 00:13:42.769 --> 00:13:42.779 align:start position:0% versions if you want to test 00:13:42.779 --> 00:13:46.490 align:start position:0% versions if you want to test going<00:13:43.320> through<00:13:43.560> protocol<00:13:43.860> upgrades<00:13:44.940> girly<00:13:45.660> is 00:13:46.490 --> 00:13:46.500 align:start position:0% going through protocol upgrades girly is 00:13:46.500 --> 00:13:49.190 align:start position:0% going through protocol upgrades girly is potentially<00:13:47.220> the<00:13:47.519> best<00:13:47.639> uh<00:13:48.180> or<00:13:48.480> if<00:13:48.779> not<00:13:48.959> even 00:13:49.190 --> 00:13:49.200 align:start position:0% potentially the best uh or if not even 00:13:49.200 --> 00:13:50.629 align:start position:0% potentially the best uh or if not even the<00:13:49.380> only<00:13:49.500> test<00:13:49.740> Network<00:13:49.980> you<00:13:50.339> can<00:13:50.399> actually 00:13:50.629 --> 00:13:50.639 align:start position:0% the only test Network you can actually 00:13:50.639 --> 00:13:53.150 align:start position:0% the only test Network you can actually conduct<00:13:51.060> this 00:13:53.150 --> 00:13:53.160 align:start position:0% conduct this 00:13:53.160 --> 00:13:53.930 align:start position:0% conduct this um 00:13:53.930 --> 00:13:53.940 align:start position:0% um 00:13:53.940 --> 00:13:55.910 align:start position:0% um yes<00:13:54.360> please<00:13:54.600> also<00:13:54.839> do<00:13:54.959> use<00:13:55.200> the<00:13:55.380> sepolia 00:13:55.910 --> 00:13:55.920 align:start position:0% yes please also do use the sepolia 00:13:55.920 --> 00:13:58.009 align:start position:0% yes please also do use the sepolia testnet<00:13:56.760> um 00:13:58.009 --> 00:13:58.019 align:start position:0% testnet um 00:13:58.019 --> 00:14:00.230 align:start position:0% testnet um sepolia<00:13:58.800> comes<00:13:59.040> with<00:13:59.220> the<00:13:59.519> best<00:13:59.880> stability 00:14:00.230 --> 00:14:00.240 align:start position:0% sepolia comes with the best stability 00:14:00.240 --> 00:14:01.970 align:start position:0% sepolia comes with the best stability guarantees<00:14:00.779> due<00:14:01.019> to<00:14:01.200> the<00:14:01.440> permissioned 00:14:01.970 --> 00:14:01.980 align:start position:0% guarantees due to the permissioned 00:14:01.980 --> 00:14:04.069 align:start position:0% guarantees due to the permissioned validator<00:14:02.459> set 00:14:04.069 --> 00:14:04.079 align:start position:0% validator set 00:14:04.079 --> 00:14:06.290 align:start position:0% validator set since<00:14:04.800> it's<00:14:04.980> fairly<00:14:05.279> new<00:14:05.399> it<00:14:05.579> is<00:14:05.760> fastest<00:14:06.120> to 00:14:06.290 --> 00:14:06.300 align:start position:0% since it's fairly new it is fastest to 00:14:06.300 --> 00:14:08.870 align:start position:0% since it's fairly new it is fastest to sync<00:14:06.600> and<00:14:07.019> also<00:14:07.440> it<00:14:07.860> has<00:14:08.040> the<00:14:08.160> best<00:14:08.339> long-term 00:14:08.870 --> 00:14:08.880 align:start position:0% sync and also it has the best long-term 00:14:08.880 --> 00:14:11.329 align:start position:0% sync and also it has the best long-term guarantees<00:14:09.360> so<00:14:10.079> I<00:14:10.260> would<00:14:10.380> lean<00:14:10.740> towards<00:14:11.100> a 00:14:11.329 --> 00:14:11.339 align:start position:0% guarantees so I would lean towards a 00:14:11.339 --> 00:14:13.069 align:start position:0% guarantees so I would lean towards a recommending<00:14:12.000> uh 00:14:13.069 --> 00:14:13.079 align:start position:0% recommending uh 00:14:13.079 --> 00:14:14.569 align:start position:0% recommending uh to<00:14:13.440> test<00:14:13.560> your<00:14:13.800> applications<00:14:14.160> or<00:14:14.399> even 00:14:14.569 --> 00:14:14.579 align:start position:0% to test your applications or even 00:14:14.579 --> 00:14:17.810 align:start position:0% to test your applications or even migrate<00:14:15.180> your<00:14:15.360> applications 00:14:17.810 --> 00:14:17.820 align:start position:0% 00:14:17.820 --> 00:14:20.810 align:start position:0% to<00:14:18.800> sepolia<00:14:19.800> instead<00:14:20.040> of<00:14:20.100> Gurley<00:14:20.519> at<00:14:20.700> this 00:14:20.810 --> 00:14:20.820 align:start position:0% to sepolia instead of Gurley at this 00:14:20.820 --> 00:14:22.910 align:start position:0% to sepolia instead of Gurley at this point 00:14:22.910 --> 00:14:22.920 align:start position:0% point 00:14:22.920 --> 00:14:26.930 align:start position:0% point yeah<00:14:23.279> do<00:14:23.519> not<00:14:23.700> use<00:14:24.300> groups<00:14:24.839> and<00:14:24.959> obviously<00:14:25.860> um 00:14:26.930 --> 00:14:26.940 align:start position:0% yeah do not use groups and obviously um 00:14:26.940 --> 00:14:29.990 align:start position:0% yeah do not use groups and obviously um I<00:14:27.720> when<00:14:28.560> when<00:14:29.040> I<00:14:29.220> prepared<00:14:29.459> my<00:14:29.639> slides<00:14:29.880> I 00:14:29.990 --> 00:14:30.000 align:start position:0% I when when I prepared my slides I 00:14:30.000 --> 00:14:31.490 align:start position:0% I when when I prepared my slides I realized<00:14:30.300> that<00:14:30.480> we<00:14:30.779> are<00:14:30.959> just<00:14:31.139> in<00:14:31.320> this 00:14:31.490 --> 00:14:31.500 align:start position:0% realized that we are just in this 00:14:31.500 --> 00:14:33.170 align:start position:0% realized that we are just in this transition<00:14:31.860> phase<00:14:32.220> where<00:14:32.459> big<00:14:32.940> service 00:14:33.170 --> 00:14:33.180 align:start position:0% transition phase where big service 00:14:33.180 --> 00:14:35.090 align:start position:0% transition phase where big service providers<00:14:33.779> already<00:14:34.200> start<00:14:34.500> shutting<00:14:34.980> down 00:14:35.090 --> 00:14:35.100 align:start position:0% providers already start shutting down 00:14:35.100 --> 00:14:37.730 align:start position:0% providers already start shutting down infrastructure<00:14:35.820> so<00:14:36.120> you<00:14:37.019> have<00:14:37.200> to<00:14:37.440> expect 00:14:37.730 --> 00:14:37.740 align:start position:0% infrastructure so you have to expect 00:14:37.740 --> 00:14:40.910 align:start position:0% infrastructure so you have to expect interruptions<00:14:38.700> and<00:14:38.940> downtime 00:14:40.910 --> 00:14:40.920 align:start position:0% interruptions and downtime 00:14:40.920 --> 00:14:44.210 align:start position:0% interruptions and downtime don't<00:14:41.459> use<00:14:41.699> coven<00:14:42.120> for<00:14:42.480> obvious<00:14:42.720> reasons 00:14:44.210 --> 00:14:44.220 align:start position:0% don't use coven for obvious reasons 00:14:44.220 --> 00:14:47.870 align:start position:0% don't use coven for obvious reasons and<00:14:45.000> yes<00:14:45.300> also<00:14:45.959> I<00:14:46.680> would<00:14:46.860> not<00:14:47.040> recommend<00:14:47.399> using 00:14:47.870 --> 00:14:47.880 align:start position:0% and yes also I would not recommend using 00:14:47.880 --> 00:14:49.790 align:start position:0% and yes also I would not recommend using Rigby<00:14:48.300> even<00:14:48.540> though<00:14:48.720> there<00:14:49.139> is<00:14:49.320> some 00:14:49.790 --> 00:14:49.800 align:start position:0% Rigby even though there is some 00:14:49.800 --> 00:14:52.310 align:start position:0% Rigby even though there is some long-term<00:14:50.399> support<00:14:50.579> planned<00:14:51.180> for<00:14:51.360> rink<00:14:51.660> B<00:14:51.839> for 00:14:52.310 --> 00:14:52.320 align:start position:0% long-term support planned for rink B for 00:14:52.320 --> 00:14:54.710 align:start position:0% long-term support planned for rink B for almost<00:14:52.680> another<00:14:52.980> year<00:14:53.339> but<00:14:53.699> you<00:14:54.480> will 00:14:54.710 --> 00:14:54.720 align:start position:0% almost another year but you will 00:14:54.720 --> 00:14:56.689 align:start position:0% almost another year but you will potentially<00:14:55.199> not<00:14:55.440> get<00:14:55.800> more<00:14:56.279> protocol 00:14:56.689 --> 00:14:56.699 align:start position:0% potentially not get more protocol 00:14:56.699 --> 00:14:58.490 align:start position:0% potentially not get more protocol upgrades<00:14:57.240> on<00:14:57.360> that<00:14:57.540> Network<00:14:57.720> so<00:14:57.959> I<00:14:58.139> would<00:14:58.260> also 00:14:58.490 --> 00:14:58.500 align:start position:0% upgrades on that Network so I would also 00:14:58.500 --> 00:15:00.590 align:start position:0% upgrades on that Network so I would also not<00:14:58.620> recommend<00:14:58.980> using<00:14:59.579> ring<00:15:00.120> B<00:15:00.240> and<00:15:00.420> that 00:15:00.590 --> 00:15:00.600 align:start position:0% not recommend using ring B and that 00:15:00.600 --> 00:15:03.829 align:start position:0% not recommend using ring B and that regard<00:15:01.440> yeah<00:15:01.860> right<00:15:02.100> there<00:15:03.000> are<00:15:03.120> some<00:15:03.240> caveats 00:15:03.829 --> 00:15:03.839 align:start position:0% regard yeah right there are some caveats 00:15:03.839 --> 00:15:06.710 align:start position:0% regard yeah right there are some caveats so<00:15:03.959> as<00:15:04.320> I<00:15:04.500> mentioned<00:15:04.800> the<00:15:05.399> girly<00:15:05.760> test<00:15:06.180> net<00:15:06.420> has 00:15:06.710 --> 00:15:06.720 align:start position:0% so as I mentioned the girly test net has 00:15:06.720 --> 00:15:08.930 align:start position:0% so as I mentioned the girly test net has Esa<00:15:07.620> supply<00:15:07.740> issues<00:15:08.160> due<00:15:08.459> to<00:15:08.579> the<00:15:08.639> sheer 00:15:08.930 --> 00:15:08.940 align:start position:0% Esa supply issues due to the sheer 00:15:08.940 --> 00:15:10.250 align:start position:0% Esa supply issues due to the sheer amount<00:15:09.120> of<00:15:09.240> users<00:15:09.540> trying<00:15:09.779> to<00:15:09.959> test<00:15:10.079> their 00:15:10.250 --> 00:15:10.260 align:start position:0% amount of users trying to test their 00:15:10.260 --> 00:15:11.810 align:start position:0% amount of users trying to test their validator<00:15:10.740> set<00:15:11.040> up 00:15:11.810 --> 00:15:11.820 align:start position:0% validator set up 00:15:11.820 --> 00:15:16.250 align:start position:0% validator set up each<00:15:12.300> validator<00:15:12.779> requires<00:15:13.680> 32<00:15:14.459> is<00:15:14.959> and<00:15:15.959> if<00:15:16.139> you 00:15:16.250 --> 00:15:16.260 align:start position:0% each validator requires 32 is and if you 00:15:16.260 --> 00:15:17.810 align:start position:0% each validator requires 32 is and if you want<00:15:16.380> to<00:15:16.500> have<00:15:16.620> a<00:15:16.860> more<00:15:16.920> involved<00:15:17.339> setup<00:15:17.639> with 00:15:17.810 --> 00:15:17.820 align:start position:0% want to have a more involved setup with 00:15:17.820 --> 00:15:20.750 align:start position:0% want to have a more involved setup with I<00:15:18.120> don't<00:15:18.300> know<00:15:18.360> 1000<00:15:19.260> validators<00:15:19.980> it<00:15:20.279> quickly 00:15:20.750 --> 00:15:20.760 align:start position:0% I don't know 1000 validators it quickly 00:15:20.760 --> 00:15:23.810 align:start position:0% I don't know 1000 validators it quickly becomes<00:15:21.240> a<00:15:21.540> huge<00:15:21.899> burden<00:15:22.339> huge<00:15:23.339> problem<00:15:23.519> to 00:15:23.810 --> 00:15:23.820 align:start position:0% becomes a huge burden huge problem to 00:15:23.820 --> 00:15:26.090 align:start position:0% becomes a huge burden huge problem to access<00:15:24.000> these<00:15:24.660> uh<00:15:24.959> required<00:15:25.440> test<00:15:25.560> net<00:15:25.740> tokens 00:15:26.090 --> 00:15:26.100 align:start position:0% access these uh required test net tokens 00:15:26.100 --> 00:15:27.530 align:start position:0% access these uh required test net tokens this<00:15:26.579> is<00:15:26.699> something<00:15:26.880> we<00:15:27.120> still<00:15:27.240> need<00:15:27.420> to 00:15:27.530 --> 00:15:27.540 align:start position:0% this is something we still need to 00:15:27.540 --> 00:15:29.329 align:start position:0% this is something we still need to figure<00:15:27.660> out<00:15:27.839> going<00:15:28.380> forward<00:15:28.620> so<00:15:28.920> if<00:15:29.100> you<00:15:29.220> have 00:15:29.329 --> 00:15:29.339 align:start position:0% figure out going forward so if you have 00:15:29.339 --> 00:15:31.490 align:start position:0% figure out going forward so if you have an<00:15:29.459> idea<00:15:29.699> please<00:15:29.880> hit<00:15:30.120> me<00:15:30.240> up<00:15:30.420> yeah<00:15:30.959> and<00:15:31.320> in 00:15:31.490 --> 00:15:31.500 align:start position:0% an idea please hit me up yeah and in 00:15:31.500 --> 00:15:33.710 align:start position:0% an idea please hit me up yeah and in terms<00:15:31.740> of<00:15:31.800> testnet<00:15:32.279> age<00:15:32.459> Gurley<00:15:33.300> is<00:15:33.480> also 00:15:33.710 --> 00:15:33.720 align:start position:0% terms of testnet age Gurley is also 00:15:33.720 --> 00:15:38.210 align:start position:0% terms of testnet age Gurley is also fairly<00:15:34.139> old<00:15:34.800> so<00:15:35.399> it<00:15:35.699> has<00:15:35.940> it<00:15:36.240> comes<00:15:36.540> with<00:15:36.660> a 00:15:38.210 --> 00:15:38.220 align:start position:0% fairly old so it has it comes with a 00:15:38.220 --> 00:15:43.550 align:start position:0% fairly old so it has it comes with a Felipe<00:15:39.440> or<00:15:40.440> a<00:15:40.560> rich<00:15:40.920> history<00:15:41.339> and<00:15:41.699> State 00:15:43.550 --> 00:15:43.560 align:start position:0% Felipe or a rich history and State 00:15:43.560 --> 00:15:45.590 align:start position:0% Felipe or a rich history and State and<00:15:44.220> is<00:15:44.459> therefore<00:15:44.820> more<00:15:45.000> difficult<00:15:45.360> to 00:15:45.590 --> 00:15:45.600 align:start position:0% and is therefore more difficult to 00:15:45.600 --> 00:15:47.449 align:start position:0% and is therefore more difficult to synchronize 00:15:47.449 --> 00:15:47.459 align:start position:0% synchronize 00:15:47.459 --> 00:15:49.490 align:start position:0% synchronize especially<00:15:48.180> now<00:15:48.480> that<00:15:48.839> it's<00:15:49.019> merged<00:15:49.380> with 00:15:49.490 --> 00:15:49.500 align:start position:0% especially now that it's merged with 00:15:49.500 --> 00:15:51.769 align:start position:0% especially now that it's merged with prata<00:15:49.980> which<00:15:50.220> also<00:15:50.579> comes<00:15:51.120> with<00:15:51.240> a<00:15:51.420> fairly<00:15:51.660> old 00:15:51.769 --> 00:15:51.779 align:start position:0% prata which also comes with a fairly old 00:15:51.779 --> 00:15:56.329 align:start position:0% prata which also comes with a fairly old Beacon<00:15:52.320> chain<00:15:52.760> in<00:15:53.760> in<00:15:53.880> combination 00:15:56.329 --> 00:15:56.339 align:start position:0% 00:15:56.339 --> 00:15:59.150 align:start position:0% and<00:15:56.519> yes<00:15:56.699> the<00:15:57.000> polio<00:15:57.420> is<00:15:57.839> uh 00:15:59.150 --> 00:15:59.160 align:start position:0% and yes the polio is uh 00:15:59.160 --> 00:16:01.610 align:start position:0% and yes the polio is uh uh<00:15:59.339> relatively<00:15:59.820> new<00:16:00.000> as<00:16:00.240> I<00:16:00.360> mentioned<00:16:00.600> it 00:16:01.610 --> 00:16:01.620 align:start position:0% uh relatively new as I mentioned it 00:16:01.620 --> 00:16:03.530 align:start position:0% uh relatively new as I mentioned it I<00:16:02.040> wrote<00:16:02.160> down<00:16:02.399> lack<00:16:02.699> of<00:16:02.880> infrastructure<00:16:03.360> I 00:16:03.530 --> 00:16:03.540 align:start position:0% I wrote down lack of infrastructure I 00:16:03.540 --> 00:16:05.030 align:start position:0% I wrote down lack of infrastructure I put<00:16:03.660> it<00:16:03.779> in<00:16:03.899> Brackets<00:16:04.199> because<00:16:04.380> it's<00:16:04.620> changing 00:16:05.030 --> 00:16:05.040 align:start position:0% put it in Brackets because it's changing 00:16:05.040 --> 00:16:07.790 align:start position:0% put it in Brackets because it's changing really<00:16:05.279> rapidly<00:16:05.820> right<00:16:06.000> now<00:16:06.260> I<00:16:07.260> just<00:16:07.380> noticed 00:16:07.790 --> 00:16:07.800 align:start position:0% really rapidly right now I just noticed 00:16:07.800 --> 00:16:11.509 align:start position:0% really rapidly right now I just noticed while<00:16:07.980> preparing<00:16:08.399> my<00:16:08.519> slides<00:16:08.880> that<00:16:09.000> uh<00:16:09.480> even 00:16:11.509 --> 00:16:11.519 align:start position:0% while preparing my slides that uh even 00:16:11.519 --> 00:16:15.410 align:start position:0% while preparing my slides that uh even metamask<00:16:12.420> has<00:16:13.019> a<00:16:13.320> sepolier 00:16:15.410 --> 00:16:15.420 align:start position:0% metamask has a sepolier 00:16:15.420 --> 00:16:19.009 align:start position:0% metamask has a sepolier test<00:16:15.959> Nets<00:16:16.380> which<00:16:16.500> now<00:16:16.740> so<00:16:17.519> um<00:16:17.579> it's<00:16:18.180> happening 00:16:19.009 --> 00:16:19.019 align:start position:0% test Nets which now so um it's happening 00:16:19.019 --> 00:16:20.689 align:start position:0% test Nets which now so um it's happening I'm<00:16:19.440> really<00:16:19.620> happy<00:16:19.800> that<00:16:20.040> we<00:16:20.220> get<00:16:20.339> all<00:16:20.519> these 00:16:20.689 --> 00:16:20.699 align:start position:0% I'm really happy that we get all these 00:16:20.699 --> 00:16:22.310 align:start position:0% I'm really happy that we get all these Integrations<00:16:21.060> now 00:16:22.310 --> 00:16:22.320 align:start position:0% Integrations now 00:16:22.320 --> 00:16:24.350 align:start position:0% Integrations now oh<00:16:22.680> yeah 00:16:24.350 --> 00:16:24.360 align:start position:0% oh yeah 00:16:24.360 --> 00:16:25.730 align:start position:0% oh yeah okay 00:16:25.730 --> 00:16:25.740 align:start position:0% okay 00:16:25.740 --> 00:16:28.790 align:start position:0% okay um this<00:16:26.459> is<00:16:26.579> my<00:16:26.940> subjective<00:16:27.899> recommendation 00:16:28.790 --> 00:16:28.800 align:start position:0% um this is my subjective recommendation 00:16:28.800 --> 00:16:31.490 align:start position:0% um this is my subjective recommendation if<00:16:29.459> you<00:16:29.579> want<00:16:29.820> to<00:16:29.940> test<00:16:30.320> infrastructure<00:16:31.320> if 00:16:31.490 --> 00:16:31.500 align:start position:0% if you want to test infrastructure if 00:16:31.500 --> 00:16:33.889 align:start position:0% if you want to test infrastructure if you<00:16:31.620> want<00:16:31.740> to<00:16:31.800> test<00:16:32.040> your<00:16:32.399> validators<00:16:32.880> I<00:16:33.779> would 00:16:33.889 --> 00:16:33.899 align:start position:0% you want to test your validators I would 00:16:33.899 --> 00:16:36.650 align:start position:0% you want to test your validators I would recommend<00:16:34.260> you<00:16:34.500> to<00:16:34.740> run<00:16:34.920> them<00:16:35.160> on<00:16:35.339> girly 00:16:36.650 --> 00:16:36.660 align:start position:0% recommend you to run them on girly 00:16:36.660 --> 00:16:39.710 align:start position:0% recommend you to run them on girly if<00:16:37.139> you<00:16:37.259> want<00:16:37.500> to<00:16:37.620> test<00:16:38.339> your<00:16:38.579> applications<00:16:39.000> I 00:16:39.710 --> 00:16:39.720 align:start position:0% if you want to test your applications I 00:16:39.720 --> 00:16:42.769 align:start position:0% if you want to test your applications I would<00:16:39.839> even<00:16:40.139> encourage<00:16:40.680> you<00:16:40.800> to<00:16:41.540> skip<00:16:42.540> early 00:16:42.769 --> 00:16:42.779 align:start position:0% would even encourage you to skip early 00:16:42.779 --> 00:16:46.370 align:start position:0% would even encourage you to skip early and<00:16:43.079> go<00:16:43.259> straight<00:16:43.500> to<00:16:43.880> run<00:16:44.880> your<00:16:45.540> stack<00:16:46.019> on 00:16:46.370 --> 00:16:46.380 align:start position:0% and go straight to run your stack on 00:16:46.380 --> 00:16:51.710 align:start position:0% and go straight to run your stack on sepolia 00:16:51.710 --> 00:16:51.720 align:start position:0% 00:16:51.720 --> 00:16:53.749 align:start position:0% okay<00:16:52.199> this<00:16:52.500> was<00:16:52.680> my<00:16:52.860> talk 00:16:53.749 --> 00:16:53.759 align:start position:0% okay this was my talk 00:16:53.759 --> 00:16:55.670 align:start position:0% okay this was my talk um<00:16:53.880> please<00:16:54.120> use<00:16:54.360> girly<00:16:54.779> or<00:16:54.959> sepolia<00:16:55.500> going 00:16:55.670 --> 00:16:55.680 align:start position:0% um please use girly or sepolia going 00:16:55.680 --> 00:16:57.050 align:start position:0% um please use girly or sepolia going forward 00:16:57.050 --> 00:16:57.060 align:start position:0% forward 00:16:57.060 --> 00:16:58.189 align:start position:0% forward um find<00:16:57.480> me 00:16:58.189 --> 00:16:58.199 align:start position:0% um find me 00:16:58.199 --> 00:17:00.170 align:start position:0% um find me for<00:16:58.680> some<00:16:58.860> spare<00:16:59.220> Visa<00:16:59.699> cards<00:16:59.940> from<00:17:00.060> East 00:17:00.170 --> 00:17:00.180 align:start position:0% for some spare Visa cards from East 00:17:00.180 --> 00:17:02.269 align:start position:0% for some spare Visa cards from East Berlin<00:17:00.600> they<00:17:01.019> are<00:17:01.139> pre-loaded<00:17:01.740> with<00:17:01.860> girly 00:17:02.269 --> 00:17:02.279 align:start position:0% Berlin they are pre-loaded with girly 00:17:02.279 --> 00:17:05.150 align:start position:0% Berlin they are pre-loaded with girly and<00:17:02.459> sipolia<00:17:03.000> Isa<00:17:03.420> so<00:17:03.600> if<00:17:03.720> you<00:17:03.899> want<00:17:04.140> some<00:17:04.439> I 00:17:05.150 --> 00:17:05.160 align:start position:0% and sipolia Isa so if you want some I 00:17:05.160 --> 00:17:07.130 align:start position:0% and sipolia Isa so if you want some I will<00:17:05.280> not<00:17:05.400> throw<00:17:05.579> them<00:17:05.880> into<00:17:06.240> the<00:17:06.419> audience<00:17:06.720> if 00:17:07.130 --> 00:17:07.140 align:start position:0% will not throw them into the audience if 00:17:07.140 --> 00:17:08.929 align:start position:0% will not throw them into the audience if I<00:17:07.380> just<00:17:07.500> fight<00:17:07.620> me<00:17:07.860> after<00:17:07.980> the<00:17:08.280> talk 00:17:08.929 --> 00:17:08.939 align:start position:0% I just fight me after the talk 00:17:08.939 --> 00:17:10.610 align:start position:0% I just fight me after the talk um 00:17:10.610 --> 00:17:10.620 align:start position:0% um 00:17:10.620 --> 00:17:12.409 align:start position:0% um and<00:17:11.280> yes<00:17:11.520> since<00:17:11.760> we<00:17:11.880> have<00:17:12.000> a<00:17:12.179> couple<00:17:12.240> of 00:17:12.409 --> 00:17:12.419 align:start position:0% and yes since we have a couple of 00:17:12.419 --> 00:17:15.530 align:start position:0% and yes since we have a couple of minutes<00:17:12.660> left<00:17:12.839> please<00:17:13.140> ask<00:17:13.439> questions 00:17:15.530 --> 00:17:15.540 align:start position:0% minutes left please ask questions 00:17:15.540 --> 00:17:18.770 align:start position:0% minutes left please ask questions thanks<00:17:16.140> for<00:17:16.380> the<00:17:16.620> presentation<00:17:17.419> is<00:17:18.419> there<00:17:18.600> any 00:17:18.770 --> 00:17:18.780 align:start position:0% thanks for the presentation is there any 00:17:18.780 --> 00:17:22.789 align:start position:0% thanks for the presentation is there any tutorial<00:17:19.500> or<00:17:19.860> manual<00:17:20.400> how<00:17:21.120> to<00:17:21.299> be<00:17:21.780> a<00:17:22.140> validator 00:17:22.789 --> 00:17:22.799 align:start position:0% tutorial or manual how to be a validator 00:17:22.799 --> 00:17:25.010 align:start position:0% tutorial or manual how to be a validator in<00:17:23.339> sepolio 00:17:25.010 --> 00:17:25.020 align:start position:0% in sepolio 00:17:25.020 --> 00:17:26.630 align:start position:0% in sepolio ought to<00:17:25.260> be<00:17:25.380> to<00:17:26.100> help<00:17:26.280> in<00:17:26.520> the 00:17:26.630 --> 00:17:26.640 align:start position:0% ought to be to help in the 00:17:26.640 --> 00:17:29.049 align:start position:0% ought to be to help in the infrastructure 00:17:29.049 --> 00:17:29.059 align:start position:0% infrastructure 00:17:29.059 --> 00:17:32.210 align:start position:0% infrastructure short<00:17:30.059> answer<00:17:30.299> is<00:17:30.600> you<00:17:30.780> can't 00:17:32.210 --> 00:17:32.220 align:start position:0% short answer is you can't 00:17:32.220 --> 00:17:35.330 align:start position:0% short answer is you can't because<00:17:33.000> as<00:17:33.840> I<00:17:34.020> mentioned<00:17:34.320> even<00:17:35.039> though<00:17:35.160> it's 00:17:35.330 --> 00:17:35.340 align:start position:0% because as I mentioned even though it's 00:17:35.340 --> 00:17:38.930 align:start position:0% because as I mentioned even though it's proof<00:17:35.640> of<00:17:35.700> stake<00:17:36.000> you<00:17:36.419> need<00:17:36.799> a<00:17:37.799> special<00:17:38.220> erc20 00:17:38.930 --> 00:17:38.940 align:start position:0% proof of stake you need a special erc20 00:17:38.940 --> 00:17:40.730 align:start position:0% proof of stake you need a special erc20 token<00:17:39.360> to<00:17:39.539> get<00:17:39.720> access<00:17:39.840> to<00:17:40.080> this<00:17:40.200> value<00:17:40.380> data 00:17:40.730 --> 00:17:40.740 align:start position:0% token to get access to this value data 00:17:40.740 --> 00:17:42.590 align:start position:0% token to get access to this value data set<00:17:40.860> and<00:17:41.400> you<00:17:41.520> would<00:17:41.700> basically<00:17:42.059> have<00:17:42.299> to 00:17:42.590 --> 00:17:42.600 align:start position:0% set and you would basically have to 00:17:42.600 --> 00:17:44.870 align:start position:0% set and you would basically have to Google<00:17:43.380> support<00:17:43.919> your 00:17:44.870 --> 00:17:44.880 align:start position:0% Google support your 00:17:44.880 --> 00:17:47.390 align:start position:0% Google support your GitHub<00:17:45.539> repository<00:17:46.140> and<00:17:46.440> there<00:17:46.919> is<00:17:47.039> an<00:17:47.160> issue 00:17:47.390 --> 00:17:47.400 align:start position:0% GitHub repository and there is an issue 00:17:47.400 --> 00:17:48.950 align:start position:0% GitHub repository and there is an issue where<00:17:47.640> you<00:17:47.760> can<00:17:47.880> request<00:17:48.179> to<00:17:48.419> be<00:17:48.600> added<00:17:48.840> to 00:17:48.950 --> 00:17:48.960 align:start position:0% where you can request to be added to 00:17:48.960 --> 00:17:50.330 align:start position:0% where you can request to be added to this<00:17:49.080> value<00:17:49.260> data<00:17:49.679> set 00:17:50.330 --> 00:17:50.340 align:start position:0% this value data set 00:17:50.340 --> 00:17:53.990 align:start position:0% this value data set but<00:17:51.000> in<00:17:51.720> general<00:17:52.100> not<00:17:53.100> many<00:17:53.280> teams<00:17:53.700> will<00:17:53.880> be 00:17:53.990 --> 00:17:54.000 align:start position:0% but in general not many teams will be 00:17:54.000 --> 00:17:56.630 align:start position:0% but in general not many teams will be accepted<00:17:54.480> just<00:17:54.780> to<00:17:55.140> keep<00:17:55.260> it<00:17:55.500> really 00:17:56.630 --> 00:17:56.640 align:start position:0% accepted just to keep it really 00:17:56.640 --> 00:17:59.510 align:start position:0% accepted just to keep it really a<00:17:57.240> small<00:17:57.660> value<00:17:57.960> data<00:17:58.380> set 00:17:59.510 --> 00:17:59.520 align:start position:0% a small value data set 00:17:59.520 --> 00:18:01.970 align:start position:0% a small value data set maybe<00:18:00.299> two<00:18:00.600> questions<00:18:00.840> here 00:18:01.970 --> 00:18:01.980 align:start position:0% maybe two questions here 00:18:01.980 --> 00:18:03.850 align:start position:0% maybe two questions here um one<00:18:02.460> when 00:18:03.850 --> 00:18:03.860 align:start position:0% um one when 00:18:03.860 --> 00:18:07.130 align:start position:0% um one when eip1559<00:18:04.860> came<00:18:05.220> around<00:18:05.460> it<00:18:06.419> was<00:18:06.539> very<00:18:06.720> hard<00:18:06.960> to 00:18:07.130 --> 00:18:07.140 align:start position:0% eip1559 came around it was very hard to 00:18:07.140 --> 00:18:08.510 align:start position:0% eip1559 came around it was very hard to test<00:18:07.320> that<00:18:07.559> in<00:18:07.679> advance<00:18:07.860> because<00:18:08.220> you<00:18:08.400> have 00:18:08.510 --> 00:18:08.520 align:start position:0% test that in advance because you have 00:18:08.520 --> 00:18:10.430 align:start position:0% test that in advance because you have these<00:18:08.700> proof<00:18:08.940> of<00:18:09.000> authority<00:18:09.299> networks<00:18:09.720> that 00:18:10.430 --> 00:18:10.440 align:start position:0% these proof of authority networks that 00:18:10.440 --> 00:18:12.169 align:start position:0% these proof of authority networks that had<00:18:10.620> no<00:18:10.740> fee<00:18:11.039> market<00:18:11.160> and<00:18:11.760> then<00:18:11.880> you<00:18:12.059> have 00:18:12.169 --> 00:18:12.179 align:start position:0% had no fee market and then you have 00:18:12.179 --> 00:18:14.390 align:start position:0% had no fee market and then you have these<00:18:12.360> proof<00:18:12.660> of<00:18:12.780> work<00:18:13.440> networks<00:18:13.980> that<00:18:14.160> had 00:18:14.390 --> 00:18:14.400 align:start position:0% these proof of work networks that had 00:18:14.400 --> 00:18:16.190 align:start position:0% these proof of work networks that had like<00:18:14.640> kind<00:18:14.880> of<00:18:15.000> a<00:18:15.120> fee<00:18:15.360> Market<00:18:15.480> you<00:18:15.840> could<00:18:15.960> kind 00:18:16.190 --> 00:18:16.200 align:start position:0% like kind of a fee Market you could kind 00:18:16.200 --> 00:18:18.289 align:start position:0% like kind of a fee Market you could kind of<00:18:16.320> Reason<00:18:16.500> about<00:18:16.860> sort<00:18:17.760> of<00:18:17.820> what<00:18:18.000> that<00:18:18.120> change 00:18:18.289 --> 00:18:18.299 align:start position:0% of Reason about sort of what that change 00:18:18.299 --> 00:18:19.610 align:start position:0% of Reason about sort of what that change would<00:18:18.660> do 00:18:19.610 --> 00:18:19.620 align:start position:0% would do 00:18:19.620 --> 00:18:21.350 align:start position:0% would do sorry<00:18:19.860> I<00:18:20.340> am<00:18:20.520> leading<00:18:20.760> into<00:18:20.880> questionnaire 00:18:21.350 --> 00:18:21.360 align:start position:0% sorry I am leading into questionnaire 00:18:21.360 --> 00:18:23.450 align:start position:0% sorry I am leading into questionnaire I'm<00:18:21.480> just<00:18:21.660> giving<00:18:21.840> some<00:18:22.080> background<00:18:22.400> and<00:18:23.400> then 00:18:23.450 --> 00:18:23.460 align:start position:0% I'm just giving some background and then 00:18:23.460 --> 00:18:25.250 align:start position:0% I'm just giving some background and then coven<00:18:23.880> if<00:18:24.299> I<00:18:24.480> seem<00:18:24.660> to<00:18:24.780> remember<00:18:24.840> right<00:18:25.080> was 00:18:25.250 --> 00:18:25.260 align:start position:0% coven if I seem to remember right was 00:18:25.260 --> 00:18:27.169 align:start position:0% coven if I seem to remember right was like<00:18:25.380> parody<00:18:25.740> Technologies<00:18:26.280> maintained<00:18:27.059> it 00:18:27.169 --> 00:18:27.179 align:start position:0% like parody Technologies maintained it 00:18:27.179 --> 00:18:30.409 align:start position:0% like parody Technologies maintained it for<00:18:27.539> the<00:18:28.200> old<00:18:28.260> open<00:18:28.500> ethereum<00:18:29.160> parity<00:18:30.000> climb 00:18:30.409 --> 00:18:30.419 align:start position:0% for the old open ethereum parity climb 00:18:30.419 --> 00:18:31.850 align:start position:0% for the old open ethereum parity climb sort<00:18:30.600> of<00:18:30.780> the<00:18:30.840> idea 00:18:31.850 --> 00:18:31.860 align:start position:0% sort of the idea 00:18:31.860 --> 00:18:34.610 align:start position:0% sort of the idea and<00:18:32.700> I<00:18:33.179> think<00:18:33.240> like<00:18:33.480> now<00:18:33.720> the<00:18:33.900> execution<00:18:34.320> layer 00:18:34.610 --> 00:18:34.620 align:start position:0% and I think like now the execution layer 00:18:34.620 --> 00:18:35.750 align:start position:0% and I think like now the execution layer is<00:18:34.740> a<00:18:34.860> spec 00:18:35.750 --> 00:18:35.760 align:start position:0% is a spec 00:18:35.760 --> 00:18:38.450 align:start position:0% is a spec there's<00:18:36.240> some<00:18:36.419> value<00:18:36.660> behind 00:18:38.450 --> 00:18:38.460 align:start position:0% there's some value behind 00:18:38.460 --> 00:18:39.049 align:start position:0% there's some value behind um 00:18:39.049 --> 00:18:39.059 align:start position:0% um 00:18:39.059 --> 00:18:41.990 align:start position:0% um you<00:18:39.539> know<00:18:39.600> testing<00:18:40.020> clients<00:18:40.620> so<00:18:41.340> I<00:18:41.520> so<00:18:41.760> I<00:18:41.940> guess 00:18:41.990 --> 00:18:42.000 align:start position:0% you know testing clients so I so I guess 00:18:42.000 --> 00:18:43.490 align:start position:0% you know testing clients so I so I guess Mike<00:18:42.240> just<00:18:42.600> to<00:18:42.660> sum<00:18:42.780> it<00:18:42.960> up<00:18:43.080> to<00:18:43.200> a<00:18:43.320> question 00:18:43.490 --> 00:18:43.500 align:start position:0% Mike just to sum it up to a question 00:18:43.500 --> 00:18:46.549 align:start position:0% Mike just to sum it up to a question both<00:18:44.400> testing<00:18:44.820> features<00:18:45.360> an<00:18:45.780> execution<00:18:46.140> layer 00:18:46.549 --> 00:18:46.559 align:start position:0% both testing features an execution layer 00:18:46.559 --> 00:18:49.510 align:start position:0% both testing features an execution layer specs<00:18:47.039> is<00:18:47.760> there<00:18:47.880> any<00:18:48.059> thought<00:18:48.299> in<00:18:48.660> behind 00:18:49.510 --> 00:18:49.520 align:start position:0% specs is there any thought in behind 00:18:49.520 --> 00:18:51.770 align:start position:0% specs is there any thought in behind testing<00:18:50.520> those<00:18:50.760> kind<00:18:51.000> of<00:18:51.120> things<00:18:51.240> moving 00:18:51.770 --> 00:18:51.780 align:start position:0% testing those kind of things moving 00:18:51.780 --> 00:18:54.169 align:start position:0% testing those kind of things moving forward<00:18:51.960> spinning<00:18:52.380> up<00:18:52.679> test<00:18:53.340> Nets<00:18:53.760> or<00:18:53.820> Forks 00:18:54.169 --> 00:18:54.179 align:start position:0% forward spinning up test Nets or Forks 00:18:54.179 --> 00:18:55.789 align:start position:0% forward spinning up test Nets or Forks of<00:18:54.240> test<00:18:54.419> Nets<00:18:54.840> to<00:18:54.960> do<00:18:55.080> that 00:18:55.789 --> 00:18:55.799 align:start position:0% of test Nets to do that 00:18:55.799 --> 00:18:59.090 align:start position:0% of test Nets to do that so 00:18:59.090 --> 00:18:59.100 align:start position:0% 00:18:59.100 --> 00:19:00.770 align:start position:0% I'm<00:18:59.520> sorry<00:18:59.700> I<00:18:59.880> don't<00:19:00.179> think<00:19:00.360> I<00:19:00.539> got<00:19:00.660> the 00:19:00.770 --> 00:19:00.780 align:start position:0% I'm sorry I don't think I got the 00:19:00.780 --> 00:19:02.930 align:start position:0% I'm sorry I don't think I got the question<00:19:01.020> it's<00:19:01.380> also<00:19:01.860> I<00:19:02.580> don't<00:19:02.640> have<00:19:02.760> the 00:19:02.930 --> 00:19:02.940 align:start position:0% question it's also I don't have the 00:19:02.940 --> 00:19:05.090 align:start position:0% question it's also I don't have the speakers<00:19:03.120> if<00:19:03.900> you<00:19:04.080> could<00:19:04.260> just<00:19:04.380> try<00:19:04.620> to<00:19:04.740> speak 00:19:05.090 --> 00:19:05.100 align:start position:0% speakers if you could just try to speak 00:19:05.100 --> 00:19:07.370 align:start position:0% speakers if you could just try to speak up<00:19:05.280> a<00:19:05.460> bit<00:19:05.520> or<00:19:05.820> so<00:19:06.120> so<00:19:06.360> specific<00:19:06.840> testing 00:19:07.370 --> 00:19:07.380 align:start position:0% up a bit or so so specific testing 00:19:07.380 --> 00:19:09.830 align:start position:0% up a bit or so so specific testing specific<00:19:07.799> features<00:19:08.340> of<00:19:08.700> ethereum<00:19:09.179> forks<00:19:09.660> like 00:19:09.830 --> 00:19:09.840 align:start position:0% specific features of ethereum forks like 00:19:09.840 --> 00:19:13.789 align:start position:0% specific features of ethereum forks like a<00:19:10.020> fee<00:19:10.320> Market<00:19:10.440> changes<00:19:11.100> or<00:19:11.880> testing<00:19:12.780> the<00:19:13.620> or 00:19:13.789 --> 00:19:13.799 align:start position:0% a fee Market changes or testing the or 00:19:13.799 --> 00:19:16.789 align:start position:0% a fee Market changes or testing the or validating<00:19:14.400> the<00:19:15.000> the<00:19:15.240> execution 00:19:16.789 --> 00:19:16.799 align:start position:0% validating the the execution 00:19:16.799 --> 00:19:19.310 align:start position:0% validating the the execution spec<00:19:17.480> was<00:19:18.480> sort<00:19:18.660> of<00:19:18.780> the<00:19:18.840> goal<00:19:19.080> because<00:19:19.200> like 00:19:19.310 --> 00:19:19.320 align:start position:0% spec was sort of the goal because like 00:19:19.320 --> 00:19:20.750 align:start position:0% spec was sort of the goal because like you<00:19:19.440> had<00:19:19.559> like<00:19:19.740> you<00:19:19.919> know<00:19:19.980> open<00:19:20.100> ethereum<00:19:20.640> or 00:19:20.750 --> 00:19:20.760 align:start position:0% you had like you know open ethereum or 00:19:20.760 --> 00:19:23.510 align:start position:0% you had like you know open ethereum or parity<00:19:21.179> and<00:19:21.480> Geth<00:19:21.780> and<00:19:22.500> whether<00:19:22.740> they<00:19:23.039> synced 00:19:23.510 --> 00:19:23.520 align:start position:0% parity and Geth and whether they synced 00:19:23.520 --> 00:19:25.190 align:start position:0% parity and Geth and whether they synced up<00:19:23.640> or<00:19:23.820> not<00:19:23.940> in<00:19:24.240> terms<00:19:24.419> of<00:19:24.539> where<00:19:25.020> they're 00:19:25.190 --> 00:19:25.200 align:start position:0% up or not in terms of where they're 00:19:25.200 --> 00:19:27.890 align:start position:0% up or not in terms of where they're executing<00:19:25.799> uh<00:19:26.640> you<00:19:26.760> know<00:19:26.880> evm<00:19:27.419> basically 00:19:27.890 --> 00:19:27.900 align:start position:0% executing uh you know evm basically 00:19:27.900 --> 00:19:31.010 align:start position:0% executing uh you know evm basically correctly<00:19:28.860> was<00:19:29.100> always<00:19:29.280> a<00:19:29.520> question<00:19:29.820> right<00:19:30.179> if 00:19:31.010 --> 00:19:31.020 align:start position:0% correctly was always a question right if 00:19:31.020 --> 00:19:33.470 align:start position:0% correctly was always a question right if they<00:19:31.140> ever<00:19:31.260> split<00:19:31.679> so<00:19:32.039> so<00:19:32.340> I<00:19:32.640> that's<00:19:33.240> that's 00:19:33.470 --> 00:19:33.480 align:start position:0% they ever split so so I that's that's 00:19:33.480 --> 00:19:35.210 align:start position:0% they ever split so so I that's that's what<00:19:33.720> I'm<00:19:33.840> asking<00:19:34.080> where<00:19:34.559> are<00:19:34.740> the<00:19:34.860> where<00:19:35.100> is 00:19:35.210 --> 00:19:35.220 align:start position:0% what I'm asking where are the where is 00:19:35.220 --> 00:19:36.830 align:start position:0% what I'm asking where are the where is the<00:19:35.340> test<00:19:35.460> net<00:19:35.700> infrastructure<00:19:36.480> sort<00:19:36.780> of 00:19:36.830 --> 00:19:36.840 align:start position:0% the test net infrastructure sort of 00:19:36.840 --> 00:19:38.450 align:start position:0% the test net infrastructure sort of going<00:19:37.020> in<00:19:37.380> terms<00:19:37.559> of<00:19:37.679> forks<00:19:38.160> and<00:19:38.280> things 00:19:38.450 --> 00:19:38.460 align:start position:0% going in terms of forks and things 00:19:38.460 --> 00:19:40.310 align:start position:0% going in terms of forks and things they're<00:19:38.640> just<00:19:38.880> gonna<00:19:39.059> spin<00:19:39.720> it<00:19:39.840> up<00:19:39.960> whenever 00:19:40.310 --> 00:19:40.320 align:start position:0% they're just gonna spin it up whenever 00:19:40.320 --> 00:19:44.930 align:start position:0% they're just gonna spin it up whenever or<00:19:40.679> whatever<00:19:41.039> I<00:19:41.340> want<00:19:41.460> to<00:19:41.580> beat<00:19:42.000> this<00:19:42.179> to<00:19:42.419> death 00:19:44.930 --> 00:19:44.940 align:start position:0% 00:19:44.940 --> 00:19:46.310 align:start position:0% um<00:19:45.059> yeah<00:19:45.240> I<00:19:45.360> hope<00:19:45.480> I<00:19:45.600> understand<00:19:45.780> the<00:19:46.200> question 00:19:46.310 --> 00:19:46.320 align:start position:0% um yeah I hope I understand the question 00:19:46.320 --> 00:19:48.529 align:start position:0% um yeah I hope I understand the question uh<00:19:47.160> correctly 00:19:48.529 --> 00:19:48.539 align:start position:0% uh correctly 00:19:48.539 --> 00:19:50.930 align:start position:0% uh correctly um<00:19:49.020> so<00:19:49.500> I<00:19:49.740> was<00:19:49.799> talking<00:19:50.039> about<00:19:50.280> public<00:19:50.640> test 00:19:50.930 --> 00:19:50.940 align:start position:0% um so I was talking about public test 00:19:50.940 --> 00:19:52.970 align:start position:0% um so I was talking about public test Nets<00:19:51.299> today<00:19:51.419> and<00:19:51.960> public<00:19:52.140> testness<00:19:52.559> is<00:19:52.799> always 00:19:52.970 --> 00:19:52.980 align:start position:0% Nets today and public testness is always 00:19:52.980 --> 00:19:55.190 align:start position:0% Nets today and public testness is always a<00:19:53.340> really<00:19:53.640> final<00:19:53.940> stage<00:19:54.600> of<00:19:54.840> testing 00:19:55.190 --> 00:19:55.200 align:start position:0% a really final stage of testing 00:19:55.200 --> 00:19:56.810 align:start position:0% a really final stage of testing everything<00:19:55.440> so<00:19:55.799> if<00:19:56.220> we<00:19:56.400> want<00:19:56.520> to<00:19:56.640> test 00:19:56.810 --> 00:19:56.820 align:start position:0% everything so if we want to test 00:19:56.820 --> 00:19:59.150 align:start position:0% everything so if we want to test execution<00:19:57.419> layer<00:19:57.840> changes<00:19:58.500> the<00:19:58.740> content 00:19:59.150 --> 00:19:59.160 align:start position:0% execution layer changes the content 00:19:59.160 --> 00:20:01.549 align:start position:0% execution layer changes the content layer<00:19:59.520> changes<00:20:00.240> and<00:20:00.600> whatnot<00:20:00.900> you<00:20:01.080> usually<00:20:01.320> go 00:20:01.549 --> 00:20:01.559 align:start position:0% layer changes and whatnot you usually go 00:20:01.559 --> 00:20:05.930 align:start position:0% layer changes and whatnot you usually go from<00:20:01.919> from<00:20:02.280> like<00:20:02.700> a<00:20:02.940> local<00:20:03.480> simulations<00:20:04.020> to<00:20:04.440> to 00:20:05.930 --> 00:20:05.940 align:start position:0% from from like a local simulations to to 00:20:05.940 --> 00:20:08.510 align:start position:0% from from like a local simulations to to permissioned<00:20:06.780> deafness<00:20:07.200> to 00:20:08.510 --> 00:20:08.520 align:start position:0% permissioned deafness to 00:20:08.520 --> 00:20:10.970 align:start position:0% permissioned deafness to um through<00:20:08.820> like<00:20:09.059> a<00:20:09.240> lot<00:20:09.419> of<00:20:09.600> hurls<00:20:10.559> until<00:20:10.740> you 00:20:10.970 --> 00:20:10.980 align:start position:0% um through like a lot of hurls until you 00:20:10.980 --> 00:20:12.710 align:start position:0% um through like a lot of hurls until you actually<00:20:11.160> get<00:20:11.460> to<00:20:11.580> a<00:20:11.760> public<00:20:11.880> test<00:20:12.179> net<00:20:12.419> and 00:20:12.710 --> 00:20:12.720 align:start position:0% actually get to a public test net and 00:20:12.720 --> 00:20:14.450 align:start position:0% actually get to a public test net and these<00:20:13.260> test<00:20:13.440> Nets<00:20:13.799> like<00:20:13.919> when<00:20:14.039> I<00:20:14.220> recommend 00:20:14.450 --> 00:20:14.460 align:start position:0% these test Nets like when I recommend 00:20:14.460 --> 00:20:16.909 align:start position:0% these test Nets like when I recommend Gurley<00:20:14.880> or<00:20:15.059> sepolier<00:20:15.600> they<00:20:16.200> will<00:20:16.440> only<00:20:16.679> get 00:20:16.909 --> 00:20:16.919 align:start position:0% Gurley or sepolier they will only get 00:20:16.919 --> 00:20:19.150 align:start position:0% Gurley or sepolier they will only get protocol<00:20:17.220> upgrades<00:20:17.760> that<00:20:17.880> have<00:20:18.179> been 00:20:19.150 --> 00:20:19.160 align:start position:0% protocol upgrades that have been 00:20:19.160 --> 00:20:22.130 align:start position:0% protocol upgrades that have been sufficiently<00:20:20.160> tested<00:20:20.460> before 00:20:22.130 --> 00:20:22.140 align:start position:0% sufficiently tested before 00:20:22.140 --> 00:20:23.810 align:start position:0% sufficiently tested before um 00:20:23.810 --> 00:20:23.820 align:start position:0% um 00:20:23.820 --> 00:20:25.190 align:start position:0% um I<00:20:24.240> don't<00:20:24.360> know<00:20:24.539> if<00:20:24.600> this<00:20:24.780> answers<00:20:25.020> your 00:20:25.190 --> 00:20:25.200 align:start position:0% I don't know if this answers your 00:20:25.200 --> 00:20:31.310 align:start position:0% I don't know if this answers your question<00:20:25.380> okay 00:20:31.310 --> 00:20:31.320 align:start position:0% 00:20:31.320 --> 00:20:32.150 align:start position:0% um 00:20:32.150 --> 00:20:32.160 align:start position:0% um 00:20:32.160 --> 00:20:34.070 align:start position:0% um do<00:20:32.580> you<00:20:32.640> know<00:20:32.760> why<00:20:33.000> did<00:20:33.419> the<00:20:33.539> mergers<00:20:33.840> happen 00:20:34.070 --> 00:20:34.080 align:start position:0% do you know why did the mergers happen 00:20:34.080 --> 00:20:36.230 align:start position:0% do you know why did the mergers happen the<00:20:34.320> way<00:20:34.440> around<00:20:34.559> they<00:20:34.919> did<00:20:35.100> could<00:20:35.940> wouldn't 00:20:36.230 --> 00:20:36.240 align:start position:0% the way around they did could wouldn't 00:20:36.240 --> 00:20:38.390 align:start position:0% the way around they did could wouldn't it<00:20:36.480> have<00:20:36.600> been<00:20:36.720> more<00:20:36.900> logical<00:20:37.260> for<00:20:37.620> for<00:20:37.860> goalie 00:20:38.390 --> 00:20:38.400 align:start position:0% it have been more logical for for goalie 00:20:38.400 --> 00:20:39.950 align:start position:0% it have been more logical for for goalie to<00:20:38.700> continue<00:20:38.760> as<00:20:39.120> a<00:20:39.240> proof<00:20:39.480> of<00:20:39.539> authority 00:20:39.950 --> 00:20:39.960 align:start position:0% to continue as a proof of authority 00:20:39.960 --> 00:20:44.690 align:start position:0% to continue as a proof of authority sorry<00:20:40.200> I<00:20:40.380> think<00:20:40.500> I<00:20:40.559> have<00:20:40.679> to<00:20:40.799> come<00:20:40.919> down 00:20:44.690 --> 00:20:44.700 align:start position:0% 00:20:44.700 --> 00:20:46.669 align:start position:0% I'm<00:20:45.179> just<00:20:45.299> wondering<00:20:45.660> why<00:20:46.080> the<00:20:46.260> merges 00:20:46.669 --> 00:20:46.679 align:start position:0% I'm just wondering why the merges 00:20:46.679 --> 00:20:49.130 align:start position:0% I'm just wondering why the merges happened<00:20:46.919> the<00:20:47.160> way<00:20:47.340> around<00:20:47.460> that<00:20:47.820> they<00:20:48.059> did<00:20:48.240> as 00:20:49.130 --> 00:20:49.140 align:start position:0% happened the way around that they did as 00:20:49.140 --> 00:20:51.830 align:start position:0% happened the way around that they did as opposed<00:20:49.620> to<00:20:49.820> gawley<00:20:50.820> continuing<00:20:51.299> as<00:20:51.480> a<00:20:51.600> proof 00:20:51.830 --> 00:20:51.840 align:start position:0% opposed to gawley continuing as a proof 00:20:51.840 --> 00:20:56.210 align:start position:0% opposed to gawley continuing as a proof of<00:20:51.900> authority<00:20:52.440> in<00:20:53.000> sepolia<00:20:54.000> uh<00:20:54.660> transitioning 00:20:56.210 --> 00:20:56.220 align:start position:0% of authority in sepolia uh transitioning 00:20:56.220 --> 00:20:57.830 align:start position:0% of authority in sepolia uh transitioning yeah<00:20:56.640> I<00:20:56.820> think<00:20:56.940> that's<00:20:57.179> a<00:20:57.360> very<00:20:57.480> good<00:20:57.600> question 00:20:57.830 --> 00:20:57.840 align:start position:0% yeah I think that's a very good question 00:20:57.840 --> 00:20:59.870 align:start position:0% yeah I think that's a very good question the<00:20:58.559> reason<00:20:58.679> is<00:20:58.919> that<00:20:59.100> it<00:20:59.280> merged<00:20:59.640> with<00:20:59.760> the 00:20:59.870 --> 00:20:59.880 align:start position:0% the reason is that it merged with the 00:20:59.880 --> 00:21:01.789 align:start position:0% the reason is that it merged with the product<00:21:00.059> test<00:21:00.360> net<00:21:00.539> which<00:21:00.840> you<00:21:01.080> used<00:21:01.320> to<00:21:01.500> be<00:21:01.620> a 00:21:01.789 --> 00:21:01.799 align:start position:0% product test net which you used to be a 00:21:01.799 --> 00:21:03.650 align:start position:0% product test net which you used to be a consensus<00:21:02.400> layer<00:21:02.700> testment<00:21:03.179> for<00:21:03.299> a<00:21:03.419> very<00:21:03.480> long 00:21:03.650 --> 00:21:03.660 align:start position:0% consensus layer testment for a very long 00:21:03.660 --> 00:21:07.130 align:start position:0% consensus layer testment for a very long time<00:21:03.840> where<00:21:04.679> many<00:21:04.980> teams<00:21:05.340> already<00:21:05.520> tested 00:21:07.130 --> 00:21:07.140 align:start position:0% time where many teams already tested 00:21:07.140 --> 00:21:07.909 align:start position:0% time where many teams already tested um 00:21:07.909 --> 00:21:07.919 align:start position:0% um 00:21:07.919 --> 00:21:10.370 align:start position:0% um running<00:21:08.280> validators<00:21:08.940> for<00:21:09.360> more<00:21:09.900> than<00:21:10.080> a<00:21:10.200> year 00:21:10.370 --> 00:21:10.380 align:start position:0% running validators for more than a year 00:21:10.380 --> 00:21:13.070 align:start position:0% running validators for more than a year or<00:21:10.620> one<00:21:11.160> and<00:21:11.280> a<00:21:11.400> half<00:21:11.460> year<00:21:11.700> so<00:21:12.299> it<00:21:12.419> was<00:21:12.600> already 00:21:13.070 --> 00:21:13.080 align:start position:0% or one and a half year so it was already 00:21:13.080 --> 00:21:14.570 align:start position:0% or one and a half year so it was already this<00:21:13.500> proof<00:21:13.860> of 00:21:14.570 --> 00:21:14.580 align:start position:0% this proof of 00:21:14.580 --> 00:21:18.169 align:start position:0% this proof of um<00:21:14.640> stake<00:21:15.419> test<00:21:15.720> net<00:21:15.960> available<00:21:16.280> and<00:21:17.280> it<00:21:18.059> was 00:21:18.169 --> 00:21:18.179 align:start position:0% um stake test net available and it was 00:21:18.179 --> 00:21:19.909 align:start position:0% um stake test net available and it was decided<00:21:18.660> not<00:21:18.960> to 00:21:19.909 --> 00:21:19.919 align:start position:0% decided not to 00:21:19.919 --> 00:21:20.890 align:start position:0% decided not to um 00:21:20.890 --> 00:21:20.900 align:start position:0% um 00:21:20.900 --> 00:21:24.529 align:start position:0% um launch<00:21:21.900> a<00:21:22.080> new<00:21:22.260> test<00:21:22.980> Beacon<00:21:23.520> chain<00:21:23.700> test<00:21:24.000> net 00:21:24.529 --> 00:21:24.539 align:start position:0% launch a new test Beacon chain test net 00:21:24.539 --> 00:21:25.250 align:start position:0% launch a new test Beacon chain test net um 00:21:25.250 --> 00:21:25.260 align:start position:0% um 00:21:25.260 --> 00:21:28.190 align:start position:0% um for<00:21:25.919> currently<00:21:26.640> specifically 00:21:28.190 --> 00:21:28.200 align:start position:0% for currently specifically 00:21:28.200 --> 00:21:31.010 align:start position:0% for currently specifically and<00:21:28.740> just<00:21:28.980> use<00:21:29.100> the<00:21:29.340> existing<00:21:29.760> one<00:21:29.940> so<00:21:30.659> this<00:21:30.900> is 00:21:31.010 --> 00:21:31.020 align:start position:0% and just use the existing one so this is 00:21:31.020 --> 00:21:32.450 align:start position:0% and just use the existing one so this is that's<00:21:31.380> why<00:21:31.500> we<00:21:31.620> had<00:21:31.740> this<00:21:31.860> flip<00:21:32.159> that<00:21:32.280> was 00:21:32.450 --> 00:21:32.460 align:start position:0% that's why we had this flip that was 00:21:32.460 --> 00:21:34.490 align:start position:0% that's why we had this flip that was also<00:21:32.700> discussed<00:21:33.059> so<00:21:33.179> maybe<00:21:33.360> have<00:21:33.659> a<00:21:33.840> new<00:21:34.020> uh 00:21:34.490 --> 00:21:34.500 align:start position:0% also discussed so maybe have a new uh 00:21:34.500 --> 00:21:36.470 align:start position:0% also discussed so maybe have a new uh deposit<00:21:34.919> contract<00:21:35.159> on<00:21:35.340> Gurley<00:21:35.700> but<00:21:35.940> in<00:21:36.360> the 00:21:36.470 --> 00:21:36.480 align:start position:0% deposit contract on Gurley but in the 00:21:36.480 --> 00:21:38.390 align:start position:0% deposit contract on Gurley but in the end<00:21:36.600> they<00:21:36.720> decided<00:21:37.140> it's<00:21:37.679> actually<00:21:37.860> worse<00:21:38.280> for 00:21:38.390 --> 00:21:38.400 align:start position:0% end they decided it's actually worse for 00:21:38.400 --> 00:21:40.490 align:start position:0% end they decided it's actually worse for testing<00:21:38.700> the<00:21:38.820> merge<00:21:39.120> to<00:21:39.659> do<00:21:39.840> the<00:21:40.020> big<00:21:40.260> big 00:21:40.490 --> 00:21:40.500 align:start position:0% testing the merge to do the big big 00:21:40.500 --> 00:21:43.070 align:start position:0% testing the merge to do the big big merge<00:21:41.460> because<00:21:41.880> product<00:21:42.179> was<00:21:42.600> also<00:21:42.780> the<00:21:42.900> only 00:21:43.070 --> 00:21:43.080 align:start position:0% merge because product was also the only 00:21:43.080 --> 00:21:46.850 align:start position:0% merge because product was also the only uh<00:21:43.620> consensus<00:21:44.159> layer<00:21:44.400> test<00:21:44.580> method<00:21:45.000> had 00:21:46.850 --> 00:21:46.860 align:start position:0% uh consensus layer test method had 00:21:46.860 --> 00:21:49.370 align:start position:0% uh consensus layer test method had about<00:21:47.400> approximately<00:21:48.179> the<00:21:48.539> same<00:21:48.780> amount<00:21:49.020> of 00:21:49.370 --> 00:21:49.380 align:start position:0% about approximately the same amount of 00:21:49.380 --> 00:21:54.350 align:start position:0% about approximately the same amount of uh<00:21:49.679> values<00:21:50.159> and<00:21:50.340> mainnet<00:21:50.820> as<00:21:51.299> mainly 00:21:54.350 --> 00:21:54.360 align:start position:0% 00:21:54.360 --> 00:21:58.789 align:start position:0% yes<00:21:54.960> and<00:21:55.799> it<00:21:55.980> was<00:21:56.100> very<00:21:56.340> very<00:21:56.880> valuable<00:21:57.360> for<00:21:58.020> a 00:21:58.789 --> 00:21:58.799 align:start position:0% yes and it was very very valuable for a 00:21:58.799 --> 00:22:00.529 align:start position:0% yes and it was very very valuable for a specifically<00:21:59.280> the<00:21:59.460> consensus<00:21:59.880> player<00:22:00.179> teams 00:22:00.529 --> 00:22:00.539 align:start position:0% specifically the consensus player teams 00:22:00.539 --> 00:22:02.210 align:start position:0% specifically the consensus player teams to<00:22:00.840> have 00:22:02.210 --> 00:22:02.220 align:start position:0% to have 00:22:02.220 --> 00:22:03.289 align:start position:0% to have um 00:22:03.289 --> 00:22:03.299 align:start position:0% um 00:22:03.299 --> 00:22:06.529 align:start position:0% um to<00:22:03.840> let<00:22:04.020> to<00:22:04.380> not<00:22:04.559> sunset<00:22:05.159> this<00:22:05.580> prata<00:22:06.240> test<00:22:06.360> net 00:22:06.529 --> 00:22:06.539 align:start position:0% to let to not sunset this prata test net 00:22:06.539 --> 00:22:08.690 align:start position:0% to let to not sunset this prata test net and<00:22:06.960> you<00:22:07.140> cannot<00:22:07.380> have<00:22:07.620> you<00:22:08.039> cannot<00:22:08.280> move<00:22:08.460> this 00:22:08.690 --> 00:22:08.700 align:start position:0% and you cannot have you cannot move this 00:22:08.700 --> 00:22:10.730 align:start position:0% and you cannot have you cannot move this product<00:22:08.880> testing<00:22:09.360> it<00:22:09.480> to<00:22:09.600> another<00:22:09.780> execution 00:22:10.730 --> 00:22:10.740 align:start position:0% product testing it to another execution 00:22:10.740 --> 00:22:14.230 align:start position:0% product testing it to another execution layer<00:22:11.100> because<00:22:11.280> it's<00:22:11.640> all<00:22:11.880> linked<00:22:12.299> to<00:22:12.360> the<00:22:12.600> uh 00:22:14.230 --> 00:22:14.240 align:start position:0% layer because it's all linked to the uh 00:22:14.240 --> 00:22:16.730 align:start position:0% layer because it's all linked to the uh deposit<00:22:15.240> contract 00:22:16.730 --> 00:22:16.740 align:start position:0% deposit contract 00:22:16.740 --> 00:22:19.250 align:start position:0% deposit contract to<00:22:17.159> have<00:22:17.640> validators<00:22:18.240> or<00:22:18.539> the<00:22:18.840> external 00:22:19.250 --> 00:22:19.260 align:start position:0% to have validators or the external 00:22:19.260 --> 00:22:21.830 align:start position:0% to have validators or the external participants<00:22:19.919> on<00:22:20.400> these<00:22:20.640> test<00:22:20.820> Nets<00:22:21.299> and<00:22:21.659> you 00:22:21.830 --> 00:22:21.840 align:start position:0% participants on these test Nets and you 00:22:21.840 --> 00:22:25.850 align:start position:0% participants on these test Nets and you need<00:22:22.020> to<00:22:22.440> do<00:22:23.280> a<00:22:23.400> bug<00:22:23.520> fix 00:22:25.850 --> 00:22:25.860 align:start position:0% need to do a bug fix 00:22:25.860 --> 00:22:28.730 align:start position:0% need to do a bug fix when<00:22:26.640> you<00:22:26.760> need<00:22:26.880> to<00:22:27.000> do<00:22:27.120> a<00:22:27.299> bug<00:22:27.480> fix<00:22:27.780> on<00:22:28.559> the 00:22:28.730 --> 00:22:28.740 align:start position:0% when you need to do a bug fix on the 00:22:28.740 --> 00:22:30.770 align:start position:0% when you need to do a bug fix on the test<00:22:28.919> net<00:22:29.220> code<00:22:29.520> are<00:22:30.000> the<00:22:30.240> external 00:22:30.770 --> 00:22:30.780 align:start position:0% test net code are the external 00:22:30.780 --> 00:22:33.169 align:start position:0% test net code are the external participants<00:22:31.380> such<00:22:31.799> as<00:22:31.980> validators<00:22:32.640> having 00:22:33.169 --> 00:22:33.179 align:start position:0% participants such as validators having 00:22:33.179 --> 00:22:34.270 align:start position:0% participants such as validators having to 00:22:34.270 --> 00:22:34.280 align:start position:0% to 00:22:34.280 --> 00:22:37.750 align:start position:0% to rebuild<00:22:35.280> their<00:22:36.000> their<00:22:36.360> validators<00:22:36.960> on<00:22:37.320> a<00:22:37.440> new 00:22:37.750 --> 00:22:37.760 align:start position:0% rebuild their their validators on a new 00:22:37.760 --> 00:22:40.250 align:start position:0% rebuild their their validators on a new machine<00:22:38.760> image<00:22:39.360> or<00:22:39.539> a<00:22:39.659> new<00:22:39.780> version<00:22:39.960> of<00:22:40.200> the 00:22:40.250 --> 00:22:40.260 align:start position:0% machine image or a new version of the 00:22:40.260 --> 00:22:41.390 align:start position:0% machine image or a new version of the code<00:22:40.440> base 00:22:41.390 --> 00:22:41.400 align:start position:0% code base 00:22:41.400 --> 00:22:43.430 align:start position:0% code base and<00:22:42.000> how<00:22:42.240> often<00:22:42.539> does<00:22:42.659> that<00:22:42.840> happen<00:22:43.020> during 00:22:43.430 --> 00:22:43.440 align:start position:0% and how often does that happen during 00:22:43.440 --> 00:22:46.610 align:start position:0% and how often does that happen during the<00:22:43.980> test<00:22:44.280> net<00:22:44.520> phases 00:22:46.610 --> 00:22:46.620 align:start position:0% the test net phases 00:22:46.620 --> 00:22:49.430 align:start position:0% the test net phases what's<00:22:47.340> the<00:22:47.580> question<00:22:47.760> uh<00:22:48.539> if<00:22:49.020> there's<00:22:49.140> a<00:22:49.320> bug 00:22:49.430 --> 00:22:49.440 align:start position:0% what's the question uh if there's a bug 00:22:49.440 --> 00:22:51.289 align:start position:0% what's the question uh if there's a bug fix<00:22:49.679> on<00:22:49.919> a<00:22:50.039> test<00:22:50.159> net<00:22:50.400> how<00:22:50.820> often<00:22:51.059> do<00:22:51.120> you<00:22:51.240> have 00:22:51.289 --> 00:22:51.299 align:start position:0% fix on a test net how often do you have 00:22:51.299 --> 00:22:53.029 align:start position:0% fix on a test net how often do you have to<00:22:51.419> rebuild<00:22:51.780> your<00:22:51.900> clients 00:22:53.029 --> 00:22:53.039 align:start position:0% to rebuild your clients 00:22:53.039 --> 00:22:56.570 align:start position:0% to rebuild your clients yeah<00:22:53.640> what's<00:22:54.179> the<00:22:54.480> workflow<00:22:55.200> when<00:22:56.159> there<00:22:56.460> is 00:22:56.570 --> 00:22:56.580 align:start position:0% yeah what's the workflow when there is 00:22:56.580 --> 00:22:59.450 align:start position:0% yeah what's the workflow when there is bug<00:22:56.820> fixes<00:22:57.299> applied<00:22:57.659> to<00:22:57.840> the<00:22:58.080> test<00:22:58.260> Nets<00:22:58.860> if 00:22:59.450 --> 00:22:59.460 align:start position:0% bug fixes applied to the test Nets if 00:22:59.460 --> 00:23:01.430 align:start position:0% bug fixes applied to the test Nets if you<00:22:59.640> are<00:22:59.760> a<00:22:59.880> validator<00:23:00.360> there<00:23:00.960> might<00:23:01.140> be<00:23:01.200> a 00:23:01.430 --> 00:23:01.440 align:start position:0% you are a validator there might be a 00:23:01.440 --> 00:23:03.230 align:start position:0% you are a validator there might be a protocol<00:23:02.100> bug 00:23:03.230 --> 00:23:03.240 align:start position:0% protocol bug 00:23:03.240 --> 00:23:06.289 align:start position:0% protocol bug so<00:23:03.659> does<00:23:03.900> the<00:23:04.080> validators<00:23:04.679> get<00:23:05.640> coordinated 00:23:06.289 --> 00:23:06.299 align:start position:0% so does the validators get coordinated 00:23:06.299 --> 00:23:10.130 align:start position:0% so does the validators get coordinated and<00:23:06.840> they<00:23:07.140> redeploy<00:23:07.980> their<00:23:08.520> nodes<00:23:09.240> multiple 00:23:10.130 --> 00:23:10.140 align:start position:0% and they redeploy their nodes multiple 00:23:10.140 --> 00:23:13.610 align:start position:0% and they redeploy their nodes multiple times<00:23:10.380> during<00:23:10.799> the<00:23:11.039> test<00:23:11.220> net<00:23:11.400> rollout 00:23:13.610 --> 00:23:13.620 align:start position:0% times during the test net rollout 00:23:13.620 --> 00:23:17.390 align:start position:0% times during the test net rollout uh<00:23:14.400> yes<00:23:14.700> this<00:23:15.059> is<00:23:15.179> basically<00:23:15.919> uh<00:23:16.919> yeah<00:23:17.100> the 00:23:17.390 --> 00:23:17.400 align:start position:0% uh yes this is basically uh yeah the 00:23:17.400 --> 00:23:19.669 align:start position:0% uh yes this is basically uh yeah the answer<00:23:17.460> is<00:23:17.700> yes<00:23:17.820> but<00:23:18.840> um 00:23:19.669 --> 00:23:19.679 align:start position:0% answer is yes but um 00:23:19.679 --> 00:23:21.830 align:start position:0% answer is yes but um this<00:23:20.340> happens<00:23:20.580> very<00:23:20.940> rarely<00:23:21.240> because<00:23:21.539> most 00:23:21.830 --> 00:23:21.840 align:start position:0% this happens very rarely because most 00:23:21.840 --> 00:23:24.770 align:start position:0% this happens very rarely because most bugs<00:23:22.320> are<00:23:22.679> usually<00:23:23.340> not<00:23:23.580> caught<00:23:23.880> on<00:23:24.179> test<00:23:24.360> Nets 00:23:24.770 --> 00:23:24.780 align:start position:0% bugs are usually not caught on test Nets 00:23:24.780 --> 00:23:29.299 align:start position:0% bugs are usually not caught on test Nets but<00:23:25.380> much<00:23:25.620> much<00:23:25.860> earlier<00:23:26.280> thank<00:23:27.000> you<00:23:27.120> everyone