WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:14.169 align:start position:0% [Music] 00:00:14.169 --> 00:00:14.179 align:start position:0% 00:00:14.179 --> 00:00:16.609 align:start position:0% options<00:00:15.179> if<00:00:15.540> you<00:00:15.660> would<00:00:15.839> like<00:00:15.960> to<00:00:16.139> launch<00:00:16.440> your 00:00:16.609 --> 00:00:16.619 align:start position:0% options if you would like to launch your 00:00:16.619 --> 00:00:19.010 align:start position:0% options if you would like to launch your own<00:00:16.740> validator<00:00:17.220> node<00:00:17.640> and<00:00:17.880> talk<00:00:18.060> about<00:00:18.240> what 00:00:19.010 --> 00:00:19.020 align:start position:0% own validator node and talk about what 00:00:19.020 --> 00:00:20.689 align:start position:0% own validator node and talk about what the<00:00:19.140> node<00:00:19.320> infrastructure<00:00:19.920> landscape<00:00:20.400> looks 00:00:20.689 --> 00:00:20.699 align:start position:0% the node infrastructure landscape looks 00:00:20.699 --> 00:00:22.910 align:start position:0% the node infrastructure landscape looks like<00:00:20.760> in<00:00:20.939> ethereum<00:00:21.359> currently<00:00:21.720> and<00:00:22.560> you<00:00:22.800> know 00:00:22.910 --> 00:00:22.920 align:start position:0% like in ethereum currently and you know 00:00:22.920 --> 00:00:26.029 align:start position:0% like in ethereum currently and you know why<00:00:23.160> it's<00:00:23.400> important<00:00:23.820> that<00:00:24.300> if<00:00:24.960> you<00:00:25.140> can<00:00:25.380> you 00:00:26.029 --> 00:00:26.039 align:start position:0% why it's important that if you can you 00:00:26.039 --> 00:00:28.070 align:start position:0% why it's important that if you can you consider<00:00:26.519> running<00:00:26.880> your<00:00:27.119> own<00:00:27.300> node<00:00:27.599> so<00:00:27.960> my 00:00:28.070 --> 00:00:28.080 align:start position:0% consider running your own node so my 00:00:28.080 --> 00:00:29.990 align:start position:0% consider running your own node so my name<00:00:28.199> is<00:00:28.260> Maggie<00:00:28.680> love 00:00:29.990 --> 00:00:30.000 align:start position:0% name is Maggie love 00:00:30.000 --> 00:00:31.669 align:start position:0% name is Maggie love um<00:00:30.119> I<00:00:30.359> guess<00:00:30.539> next<00:00:30.779> slide 00:00:31.669 --> 00:00:31.679 align:start position:0% um I guess next slide 00:00:31.679 --> 00:00:34.910 align:start position:0% um I guess next slide Clicker<00:00:32.820> cool<00:00:33.480> so<00:00:34.079> my<00:00:34.260> name<00:00:34.380> is<00:00:34.440> Maggie<00:00:34.800> love 00:00:34.910 --> 00:00:34.920 align:start position:0% Clicker cool so my name is Maggie love 00:00:34.920 --> 00:00:36.410 align:start position:0% Clicker cool so my name is Maggie love I'm<00:00:35.219> one<00:00:35.399> of<00:00:35.520> the<00:00:35.579> co-founders<00:00:36.000> and<00:00:36.239> director 00:00:36.410 --> 00:00:36.420 align:start position:0% I'm one of the co-founders and director 00:00:36.420 --> 00:00:38.690 align:start position:0% I'm one of the co-founders and director of<00:00:36.600> ecosystem<00:00:37.079> and<00:00:37.500> Partnerships<00:00:37.980> for<00:00:38.280> web3 00:00:38.690 --> 00:00:38.700 align:start position:0% of ecosystem and Partnerships for web3 00:00:38.700 --> 00:00:42.410 align:start position:0% of ecosystem and Partnerships for web3 cloud<00:00:39.000> I'm<00:00:39.660> also<00:00:39.960> the<00:00:40.140> founder<00:00:40.379> of<00:00:40.500> shifai<00:00:41.420> and 00:00:42.410 --> 00:00:42.420 align:start position:0% cloud I'm also the founder of shifai and 00:00:42.420 --> 00:00:46.250 align:start position:0% cloud I'm also the founder of shifai and that's<00:00:42.899> me<00:00:43.140> on<00:00:43.320> Twitter<00:00:43.500> and<00:00:43.800> this<00:00:43.920> is<00:00:44.100> Shane 00:00:46.250 --> 00:00:46.260 align:start position:0% that's me on Twitter and this is Shane 00:00:46.260 --> 00:00:47.810 align:start position:0% that's me on Twitter and this is Shane so<00:00:46.620> Shane<00:00:47.040> is<00:00:47.219> the<00:00:47.340> co-founder<00:00:47.700> of 00:00:47.810 --> 00:00:47.820 align:start position:0% so Shane is the co-founder of 00:00:47.820 --> 00:00:49.970 align:start position:0% so Shane is the co-founder of decentralized<00:00:48.239> authority<00:00:48.780> and<00:00:49.140> our<00:00:49.620> teams 00:00:49.970 --> 00:00:49.980 align:start position:0% decentralized authority and our teams 00:00:49.980 --> 00:00:52.250 align:start position:0% decentralized authority and our teams are<00:00:50.100> working<00:00:50.280> together<00:00:50.600> on<00:00:51.600> some<00:00:51.840> different 00:00:52.250 --> 00:00:52.260 align:start position:0% are working together on some different 00:00:52.260 --> 00:00:54.950 align:start position:0% are working together on some different plays<00:00:52.680> in<00:00:52.739> the<00:00:52.860> node<00:00:53.039> infrastructure<00:00:53.640> space 00:00:54.950 --> 00:00:54.960 align:start position:0% plays in the node infrastructure space 00:00:54.960 --> 00:00:57.950 align:start position:0% plays in the node infrastructure space and<00:00:55.559> uh<00:00:55.739> just<00:00:55.980> a<00:00:56.100> bit<00:00:56.160> about<00:00:56.280> web3<00:00:56.760> Cloud<00:00:57.000> so<00:00:57.719> we 00:00:57.950 --> 00:00:57.960 align:start position:0% and uh just a bit about web3 Cloud so we 00:00:57.960 --> 00:00:59.930 align:start position:0% and uh just a bit about web3 Cloud so we are<00:00:58.199> a<00:00:58.440> compute<00:00:58.920> and<00:00:59.039> storage<00:00:59.340> Hardware 00:00:59.930 --> 00:00:59.940 align:start position:0% are a compute and storage Hardware 00:00:59.940 --> 00:01:02.029 align:start position:0% are a compute and storage Hardware infrastructure<00:01:00.719> provider<00:01:01.140> powering<00:01:01.559> web<00:01:01.800> 3 00:01:02.029 --> 00:01:02.039 align:start position:0% infrastructure provider powering web 3 00:01:02.039 --> 00:01:04.009 align:start position:0% infrastructure provider powering web 3 and<00:01:02.760> we're<00:01:02.879> also<00:01:03.180> a<00:01:03.300> joint<00:01:03.539> venture<00:01:03.899> between 00:01:04.009 --> 00:01:04.019 align:start position:0% and we're also a joint venture between 00:01:04.019 --> 00:01:06.710 align:start position:0% and we're also a joint venture between consensus<00:01:04.680> in<00:01:04.920> Advanced<00:01:05.280> Micro<00:01:05.460> Devices<00:01:05.880> and 00:01:06.710 --> 00:01:06.720 align:start position:0% consensus in Advanced Micro Devices and 00:01:06.720 --> 00:01:09.250 align:start position:0% consensus in Advanced Micro Devices and really<00:01:06.900> our<00:01:07.200> goal<00:01:07.439> is<00:01:07.680> to<00:01:07.979> provide<00:01:08.400> the 00:01:09.250 --> 00:01:09.260 align:start position:0% really our goal is to provide the 00:01:09.260 --> 00:01:12.410 align:start position:0% really our goal is to provide the infrastructure<00:01:10.260> for<00:01:10.860> many<00:01:11.400> web3<00:01:11.880> protocols 00:01:12.410 --> 00:01:12.420 align:start position:0% infrastructure for many web3 protocols 00:01:12.420 --> 00:01:14.090 align:start position:0% infrastructure for many web3 protocols so<00:01:12.659> the<00:01:12.840> protocols<00:01:13.320> on<00:01:13.500> the<00:01:13.619> software<00:01:13.920> side 00:01:14.090 --> 00:01:14.100 align:start position:0% so the protocols on the software side 00:01:14.100 --> 00:01:16.730 align:start position:0% so the protocols on the software side can<00:01:14.400> just<00:01:14.520> focus<00:01:14.760> on<00:01:14.939> scaling<00:01:15.420> and<00:01:16.200> building 00:01:16.730 --> 00:01:16.740 align:start position:0% can just focus on scaling and building 00:01:16.740 --> 00:01:19.429 align:start position:0% can just focus on scaling and building it<00:01:17.220> web3<00:01:17.939> natively<00:01:18.420> so<00:01:18.900> building 00:01:19.429 --> 00:01:19.439 align:start position:0% it web3 natively so building 00:01:19.439 --> 00:01:23.630 align:start position:0% it web3 natively so building infrastructure<00:01:20.100> that's<00:01:20.280> web<00:01:20.520> 3<00:01:20.759> native 00:01:23.630 --> 00:01:23.640 align:start position:0% 00:01:23.640 --> 00:01:27.469 align:start position:0% okay<00:01:24.540> so<00:01:25.100> uh<00:01:26.100> why<00:01:26.340> is<00:01:26.460> validating<00:01:26.939> important 00:01:27.469 --> 00:01:27.479 align:start position:0% okay so uh why is validating important 00:01:27.479 --> 00:01:30.050 align:start position:0% okay so uh why is validating important right<00:01:27.900> so<00:01:28.500> ethereum<00:01:29.400> believes<00:01:29.759> that 00:01:30.050 --> 00:01:30.060 align:start position:0% right so ethereum believes that 00:01:30.060 --> 00:01:31.969 align:start position:0% right so ethereum believes that validators<00:01:30.540> will<00:01:30.780> play<00:01:30.960> an<00:01:31.200> active<00:01:31.500> part<00:01:31.740> in 00:01:31.969 --> 00:01:31.979 align:start position:0% validators will play an active part in 00:01:31.979 --> 00:01:34.130 align:start position:0% validators will play an active part in ethereum's<00:01:32.640> future<00:01:32.759> and<00:01:33.479> that<00:01:33.659> they<00:01:33.840> are<00:01:34.020> key 00:01:34.130 --> 00:01:34.140 align:start position:0% ethereum's future and that they are key 00:01:34.140 --> 00:01:36.230 align:start position:0% ethereum's future and that they are key to<00:01:34.320> more<00:01:34.560> secure<00:01:34.920> scalable<00:01:35.460> and<00:01:35.759> sustainable 00:01:36.230 --> 00:01:36.240 align:start position:0% to more secure scalable and sustainable 00:01:36.240 --> 00:01:37.730 align:start position:0% to more secure scalable and sustainable ethereum 00:01:37.730 --> 00:01:37.740 align:start position:0% ethereum 00:01:37.740 --> 00:01:40.010 align:start position:0% ethereum um<00:01:37.860> I<00:01:38.040> got<00:01:38.159> this<00:01:38.280> quote<00:01:38.520> from<00:01:38.640> an<00:01:38.820> article<00:01:39.299> I<00:01:39.720> I 00:01:40.010 --> 00:01:40.020 align:start position:0% um I got this quote from an article I I 00:01:40.020 --> 00:01:42.530 align:start position:0% um I got this quote from an article I I post<00:01:40.259> all<00:01:40.500> the<00:01:40.799> things<00:01:41.340> I<00:01:41.520> take<00:01:41.759> from<00:01:41.939> and 00:01:42.530 --> 00:01:42.540 align:start position:0% post all the things I take from and 00:01:42.540 --> 00:01:44.270 align:start position:0% post all the things I take from and really<00:01:42.780> this<00:01:43.079> is<00:01:43.200> uh<00:01:43.380> the<00:01:43.619> validators<00:01:44.040> are 00:01:44.270 --> 00:01:44.280 align:start position:0% really this is uh the validators are 00:01:44.280 --> 00:01:46.130 align:start position:0% really this is uh the validators are really<00:01:44.460> important<00:01:44.759> to<00:01:45.000> ethereum<00:01:45.479> if<00:01:46.020> you 00:01:46.130 --> 00:01:46.140 align:start position:0% really important to ethereum if you 00:01:46.140 --> 00:01:48.590 align:start position:0% really important to ethereum if you heard<00:01:46.320> Danny<00:01:46.740> Ryan's<00:01:47.220> opening<00:01:47.700> talk<00:01:47.880> a 00:01:48.590 --> 00:01:48.600 align:start position:0% heard Danny Ryan's opening talk a 00:01:48.600 --> 00:01:50.690 align:start position:0% heard Danny Ryan's opening talk a resiliency<00:01:49.140> is<00:01:49.740> incredibly<00:01:50.159> important<00:01:50.520> in 00:01:50.690 --> 00:01:50.700 align:start position:0% resiliency is incredibly important in 00:01:50.700 --> 00:01:52.609 align:start position:0% resiliency is incredibly important in this<00:01:50.880> space<00:01:51.119> and<00:01:51.780> we're<00:01:51.960> going<00:01:52.140> to<00:01:52.259> touch<00:01:52.439> on 00:01:52.609 --> 00:01:52.619 align:start position:0% this space and we're going to touch on 00:01:52.619 --> 00:01:58.609 align:start position:0% this space and we're going to touch on that<00:01:52.740> again<00:01:52.920> today<00:01:53.220> in<00:01:53.579> this<00:01:53.759> presentation 00:01:58.609 --> 00:01:58.619 align:start position:0% 00:01:58.619 --> 00:02:02.270 align:start position:0% okay<00:01:59.280> so<00:01:59.820> I<00:02:00.420> had<00:02:00.659> a<00:02:00.780> spicy<00:02:01.200> tweet<00:02:01.560> uh<00:02:01.920> earlier 00:02:02.270 --> 00:02:02.280 align:start position:0% okay so I had a spicy tweet uh earlier 00:02:02.280 --> 00:02:04.609 align:start position:0% okay so I had a spicy tweet uh earlier this<00:02:02.520> year<00:02:02.700> and<00:02:03.240> it<00:02:03.540> kind<00:02:03.840> of<00:02:03.899> sparked<00:02:04.380> me<00:02:04.500> to 00:02:04.609 --> 00:02:04.619 align:start position:0% this year and it kind of sparked me to 00:02:04.619 --> 00:02:06.590 align:start position:0% this year and it kind of sparked me to go<00:02:04.740> further<00:02:05.100> down<00:02:05.280> this<00:02:05.460> rabbit<00:02:05.880> hole<00:02:06.000> and 00:02:06.590 --> 00:02:06.600 align:start position:0% go further down this rabbit hole and 00:02:06.600 --> 00:02:08.809 align:start position:0% go further down this rabbit hole and sort<00:02:06.780> of<00:02:06.960> why<00:02:07.079> I'm<00:02:07.259> here<00:02:07.439> today<00:02:07.619> it<00:02:08.280> got<00:02:08.520> a<00:02:08.700> lot 00:02:08.809 --> 00:02:08.819 align:start position:0% sort of why I'm here today it got a lot 00:02:08.819 --> 00:02:10.309 align:start position:0% sort of why I'm here today it got a lot of<00:02:09.060> airplane<00:02:09.300> and<00:02:09.660> they<00:02:09.840> spent<00:02:09.959> like<00:02:10.140> two 00:02:10.309 --> 00:02:10.319 align:start position:0% of airplane and they spent like two 00:02:10.319 --> 00:02:11.930 align:start position:0% of airplane and they spent like two minutes<00:02:10.440> on<00:02:10.739> it<00:02:10.860> so<00:02:10.979> I<00:02:11.160> was<00:02:11.220> really<00:02:11.400> surprised 00:02:11.930 --> 00:02:11.940 align:start position:0% minutes on it so I was really surprised 00:02:11.940 --> 00:02:13.970 align:start position:0% minutes on it so I was really surprised all<00:02:12.780> right<00:02:12.900> so 00:02:13.970 --> 00:02:13.980 align:start position:0% all right so 00:02:13.980 --> 00:02:15.770 align:start position:0% all right so uh<00:02:14.520> you<00:02:14.700> know<00:02:14.819> what<00:02:14.940> does<00:02:15.120> it<00:02:15.300> mean<00:02:15.420> to<00:02:15.599> be 00:02:15.770 --> 00:02:15.780 align:start position:0% uh you know what does it mean to be 00:02:15.780 --> 00:02:18.470 align:start position:0% uh you know what does it mean to be decentralized<00:02:16.560> and<00:02:16.800> should<00:02:17.099> uh<00:02:17.760> protocols 00:02:18.470 --> 00:02:18.480 align:start position:0% decentralized and should uh protocols 00:02:18.480 --> 00:02:20.990 align:start position:0% decentralized and should uh protocols like<00:02:18.540> ethereum<00:02:19.080> and<00:02:19.440> others<00:02:19.739> be<00:02:19.980> concerned<00:02:20.459> if 00:02:20.990 --> 00:02:21.000 align:start position:0% like ethereum and others be concerned if 00:02:21.000 --> 00:02:23.030 align:start position:0% like ethereum and others be concerned if more<00:02:21.360> than<00:02:21.480> you<00:02:21.720> know<00:02:21.840> 50<00:02:22.020> of<00:02:22.500> their<00:02:22.620> nodes<00:02:22.860> are 00:02:23.030 --> 00:02:23.040 align:start position:0% more than you know 50 of their nodes are 00:02:23.040 --> 00:02:25.430 align:start position:0% more than you know 50 of their nodes are running<00:02:23.220> on<00:02:23.459> one<00:02:23.700> hosting<00:02:24.540> provider<00:02:25.020> what<00:02:25.260> are 00:02:25.430 --> 00:02:25.440 align:start position:0% running on one hosting provider what are 00:02:25.440 --> 00:02:26.809 align:start position:0% running on one hosting provider what are some<00:02:25.560> of<00:02:25.680> the<00:02:25.739> things<00:02:25.920> we<00:02:26.099> have<00:02:26.220> to<00:02:26.400> consider 00:02:26.809 --> 00:02:26.819 align:start position:0% some of the things we have to consider 00:02:26.819 --> 00:02:29.869 align:start position:0% some of the things we have to consider uh<00:02:27.720> you<00:02:27.840> know<00:02:27.959> decentralization<00:02:28.800> is<00:02:29.160> a<00:02:29.459> key 00:02:29.869 --> 00:02:29.879 align:start position:0% uh you know decentralization is a key 00:02:29.879 --> 00:02:31.729 align:start position:0% uh you know decentralization is a key tenant<00:02:30.180> at<00:02:30.420> least<00:02:30.599> the<00:02:30.780> ethereum<00:02:31.200> ecosystem 00:02:31.729 --> 00:02:31.739 align:start position:0% tenant at least the ethereum ecosystem 00:02:31.739 --> 00:02:34.490 align:start position:0% tenant at least the ethereum ecosystem not<00:02:32.459> every<00:02:32.640> ecosystem<00:02:33.239> and<00:02:33.840> so<00:02:34.020> I<00:02:34.140> wanted<00:02:34.260> to 00:02:34.490 --> 00:02:34.500 align:start position:0% not every ecosystem and so I wanted to 00:02:34.500 --> 00:02:36.470 align:start position:0% not every ecosystem and so I wanted to challenge<00:02:34.860> that<00:02:35.459> notion<00:02:35.819> that<00:02:36.060> if<00:02:36.180> we<00:02:36.360> say 00:02:36.470 --> 00:02:36.480 align:start position:0% challenge that notion that if we say 00:02:36.480 --> 00:02:38.949 align:start position:0% challenge that notion that if we say this<00:02:36.660> is<00:02:36.780> important<00:02:37.200> uh<00:02:37.920> are<00:02:38.220> we<00:02:38.459> actually 00:02:38.949 --> 00:02:38.959 align:start position:0% this is important uh are we actually 00:02:38.959 --> 00:02:42.229 align:start position:0% this is important uh are we actually decentralized<00:02:39.959> and<00:02:41.099> um 00:02:42.229 --> 00:02:42.239 align:start position:0% decentralized and um 00:02:42.239 --> 00:02:44.930 align:start position:0% decentralized and um because<00:02:42.959> of<00:02:43.319> this<00:02:43.440> tweet<00:02:43.860> hurts<00:02:44.400> nurse<00:02:44.700> so<00:02:44.819> you 00:02:44.930 --> 00:02:44.940 align:start position:0% because of this tweet hurts nurse so you 00:02:44.940 --> 00:02:47.990 align:start position:0% because of this tweet hurts nurse so you can<00:02:45.000> see<00:02:45.120> her<00:02:45.300> 16.9<00:02:46.019> of<00:02:46.680> the<00:02:46.860> ecosystem<00:02:47.280> I'll 00:02:47.990 --> 00:02:48.000 align:start position:0% can see her 16.9 of the ecosystem I'll 00:02:48.000 --> 00:02:49.610 align:start position:0% can see her 16.9 of the ecosystem I'll responded<00:02:48.540> to<00:02:48.660> my<00:02:48.780> tweet<00:02:49.080> saying<00:02:49.379> they<00:02:49.500> were 00:02:49.610 --> 00:02:49.620 align:start position:0% responded to my tweet saying they were 00:02:49.620 --> 00:02:51.890 align:start position:0% responded to my tweet saying they were Banning<00:02:50.099> a<00:02:50.580> running<00:02:50.760> ethereum<00:02:51.300> notes<00:02:51.720> on 00:02:51.890 --> 00:02:51.900 align:start position:0% Banning a running ethereum notes on 00:02:51.900 --> 00:02:54.170 align:start position:0% Banning a running ethereum notes on their<00:02:52.019> infrastructure<00:02:52.680> so<00:02:53.400> they're<00:02:53.700> a<00:02:53.940> data 00:02:54.170 --> 00:02:54.180 align:start position:0% their infrastructure so they're a data 00:02:54.180 --> 00:02:56.150 align:start position:0% their infrastructure so they're a data center<00:02:54.300> within<00:02:54.720> Germany<00:02:55.080> uh<00:02:55.500> that<00:02:55.620> a<00:02:55.860> lot<00:02:55.980> of 00:02:56.150 --> 00:02:56.160 align:start position:0% center within Germany uh that a lot of 00:02:56.160 --> 00:02:58.970 align:start position:0% center within Germany uh that a lot of nodes<00:02:56.819> are<00:02:57.000> running<00:02:57.180> on<00:02:57.420> so<00:02:57.840> we<00:02:58.440> can<00:02:58.560> start<00:02:58.800> to 00:02:58.970 --> 00:02:58.980 align:start position:0% nodes are running on so we can start to 00:02:58.980 --> 00:03:01.130 align:start position:0% nodes are running on so we can start to see<00:02:59.099> the<00:02:59.340> issues<00:02:59.700> here<00:02:59.940> uh<00:03:00.720> if<00:03:00.840> we're<00:03:01.019> not 00:03:01.130 --> 00:03:01.140 align:start position:0% see the issues here uh if we're not 00:03:01.140 --> 00:03:02.930 align:start position:0% see the issues here uh if we're not thinking<00:03:01.440> about<00:03:01.620> how<00:03:01.920> to<00:03:02.099> decentralize<00:03:02.640> the 00:03:02.930 --> 00:03:02.940 align:start position:0% thinking about how to decentralize the 00:03:02.940 --> 00:03:04.729 align:start position:0% thinking about how to decentralize the cost<00:03:03.120> hosting<00:03:03.599> providers<00:03:04.019> uh<00:03:04.500> because 00:03:04.729 --> 00:03:04.739 align:start position:0% cost hosting providers uh because 00:03:04.739 --> 00:03:06.050 align:start position:0% cost hosting providers uh because Searcher<00:03:05.220> did<00:03:05.340> it<00:03:05.459> they're<00:03:05.640> smaller<00:03:05.940> but 00:03:06.050 --> 00:03:06.060 align:start position:0% Searcher did it they're smaller but 00:03:06.060 --> 00:03:08.210 align:start position:0% Searcher did it they're smaller but potentially<00:03:06.599> Amazon<00:03:06.840> could<00:03:07.319> do<00:03:07.440> it 00:03:08.210 --> 00:03:08.220 align:start position:0% potentially Amazon could do it 00:03:08.220 --> 00:03:10.550 align:start position:0% potentially Amazon could do it um<00:03:08.340> and<00:03:08.519> one<00:03:08.700> of<00:03:08.879> the<00:03:08.940> ethereum<00:03:09.660> uh<00:03:10.140> Foundation 00:03:10.550 --> 00:03:10.560 align:start position:0% um and one of the ethereum uh Foundation 00:03:10.560 --> 00:03:13.309 align:start position:0% um and one of the ethereum uh Foundation members<00:03:10.980> Peter<00:03:11.459> uh<00:03:12.239> right<00:03:12.420> kind<00:03:12.720> of<00:03:12.840> commented 00:03:13.309 --> 00:03:13.319 align:start position:0% members Peter uh right kind of commented 00:03:13.319 --> 00:03:16.729 align:start position:0% members Peter uh right kind of commented on<00:03:13.440> that<00:03:13.860> you<00:03:14.580> know<00:03:14.700> it's<00:03:15.599> important<00:03:16.019> to 00:03:16.729 --> 00:03:16.739 align:start position:0% on that you know it's important to 00:03:16.739 --> 00:03:19.729 align:start position:0% on that you know it's important to update<00:03:17.340> the<00:03:17.580> validator<00:03:18.060> ecosystem<00:03:19.019> so<00:03:19.440> more 00:03:19.729 --> 00:03:19.739 align:start position:0% update the validator ecosystem so more 00:03:19.739 --> 00:03:21.470 align:start position:0% update the validator ecosystem so more people<00:03:19.920> can<00:03:20.220> run<00:03:20.400> it<00:03:20.519> at<00:03:20.700> home<00:03:20.819> update<00:03:21.300> the 00:03:21.470 --> 00:03:21.480 align:start position:0% people can run it at home update the 00:03:21.480 --> 00:03:24.229 align:start position:0% people can run it at home update the protocol<00:03:21.780> itself<00:03:22.260> and<00:03:23.099> you<00:03:23.280> know<00:03:23.400> if<00:03:24.000> that's 00:03:24.229 --> 00:03:24.239 align:start position:0% protocol itself and you know if that's 00:03:24.239 --> 00:03:25.850 align:start position:0% protocol itself and you know if that's not<00:03:24.480> happening<00:03:24.780> then<00:03:25.080> people<00:03:25.319> are<00:03:25.500> gonna<00:03:25.680> go 00:03:25.850 --> 00:03:25.860 align:start position:0% not happening then people are gonna go 00:03:25.860 --> 00:03:28.130 align:start position:0% not happening then people are gonna go with<00:03:26.040> the<00:03:26.220> easy<00:03:26.400> hosting<00:03:27.360> providers<00:03:27.780> they<00:03:27.959> may 00:03:28.130 --> 00:03:28.140 align:start position:0% with the easy hosting providers they may 00:03:28.140 --> 00:03:30.050 align:start position:0% with the easy hosting providers they may not<00:03:28.260> be<00:03:28.379> aware<00:03:28.680> of<00:03:28.800> some<00:03:29.340> of<00:03:29.519> the<00:03:29.580> risks<00:03:29.940> that 00:03:30.050 --> 00:03:30.060 align:start position:0% not be aware of some of the risks that 00:03:30.060 --> 00:03:32.089 align:start position:0% not be aware of some of the risks that could<00:03:30.239> happen<00:03:30.420> so 00:03:32.089 --> 00:03:32.099 align:start position:0% could happen so 00:03:32.099 --> 00:03:34.910 align:start position:0% could happen so um<00:03:32.159> that<00:03:32.580> was<00:03:32.700> a<00:03:32.879> fun<00:03:33.239> fun<00:03:33.540> week<00:03:33.840> or<00:03:34.140> so<00:03:34.319> of 00:03:34.910 --> 00:03:34.920 align:start position:0% um that was a fun fun week or so of 00:03:34.920 --> 00:03:37.190 align:start position:0% um that was a fun fun week or so of notifications<00:03:35.580> and<00:03:36.300> so<00:03:36.480> really<00:03:36.720> quickly<00:03:37.019> I 00:03:37.190 --> 00:03:37.200 align:start position:0% notifications and so really quickly I 00:03:37.200 --> 00:03:38.869 align:start position:0% notifications and so really quickly I just<00:03:37.319> wanted<00:03:37.440> to<00:03:37.620> do<00:03:37.739> a<00:03:37.860> poll<00:03:38.040> uh<00:03:38.400> because<00:03:38.580> this 00:03:38.869 --> 00:03:38.879 align:start position:0% just wanted to do a poll uh because this 00:03:38.879 --> 00:03:41.330 align:start position:0% just wanted to do a poll uh because this was<00:03:39.000> a<00:03:39.239> big<00:03:39.360> part<00:03:39.840> of<00:03:40.080> the<00:03:40.200> debate<00:03:40.500> on<00:03:40.920> on<00:03:41.159> the 00:03:41.330 --> 00:03:41.340 align:start position:0% was a big part of the debate on on the 00:03:41.340 --> 00:03:43.190 align:start position:0% was a big part of the debate on on the Twitter<00:03:41.459> thread<00:03:41.879> how<00:03:42.060> many<00:03:42.180> many<00:03:42.720> of<00:03:43.019> you 00:03:43.190 --> 00:03:43.200 align:start position:0% Twitter thread how many many of you 00:03:43.200 --> 00:03:44.690 align:start position:0% Twitter thread how many many of you think<00:03:43.500> a<00:03:43.799> centralization<00:03:44.400> about 00:03:44.690 --> 00:03:44.700 align:start position:0% think a centralization about 00:03:44.700 --> 00:03:48.890 align:start position:0% think a centralization about infrastructure<00:03:45.480> is<00:03:45.840> a<00:03:46.019> concern<00:03:46.319> for<00:03:46.560> ethereum 00:03:48.890 --> 00:03:48.900 align:start position:0% infrastructure is a concern for ethereum 00:03:48.900 --> 00:03:51.890 align:start position:0% infrastructure is a concern for ethereum okay<00:03:49.379> great<00:03:49.680> so<00:03:50.400> all<00:03:51.120> of<00:03:51.299> us<00:03:51.360> are<00:03:51.540> here<00:03:51.659> because 00:03:51.890 --> 00:03:51.900 align:start position:0% okay great so all of us are here because 00:03:51.900 --> 00:03:53.210 align:start position:0% okay great so all of us are here because we're<00:03:52.140> probably<00:03:52.379> curious<00:03:52.920> about 00:03:53.210 --> 00:03:53.220 align:start position:0% we're probably curious about 00:03:53.220 --> 00:03:55.430 align:start position:0% we're probably curious about decentralization<00:03:54.000> and<00:03:54.480> believe<00:03:54.720> it's 00:03:55.430 --> 00:03:55.440 align:start position:0% decentralization and believe it's 00:03:55.440 --> 00:03:58.009 align:start position:0% decentralization and believe it's important<00:03:55.860> through<00:03:56.159> for<00:03:56.459> a<00:03:56.700> resilient<00:03:57.299> uh 00:03:58.009 --> 00:03:58.019 align:start position:0% important through for a resilient uh 00:03:58.019 --> 00:03:59.869 align:start position:0% important through for a resilient uh vertical 00:03:59.869 --> 00:03:59.879 align:start position:0% vertical 00:03:59.879 --> 00:04:01.910 align:start position:0% vertical and<00:04:00.239> so<00:04:00.360> then<00:04:00.540> the<00:04:00.720> goal<00:04:01.019> of<00:04:01.140> this<00:04:01.319> Workshop 00:04:01.910 --> 00:04:01.920 align:start position:0% and so then the goal of this Workshop 00:04:01.920 --> 00:04:04.070 align:start position:0% and so then the goal of this Workshop today<00:04:02.220> is<00:04:03.060> to<00:04:03.299> teach<00:04:03.480> you<00:04:03.599> about<00:04:03.780> the 00:04:04.070 --> 00:04:04.080 align:start position:0% today is to teach you about the 00:04:04.080 --> 00:04:06.350 align:start position:0% today is to teach you about the importance<00:04:04.440> of<00:04:04.620> running<00:04:04.799> your<00:04:05.099> own<00:04:05.340> note<00:04:05.640> to 00:04:06.350 --> 00:04:06.360 align:start position:0% importance of running your own note to 00:04:06.360 --> 00:04:07.670 align:start position:0% importance of running your own note to contribute<00:04:06.720> to<00:04:06.900> the<00:04:07.019> resilience<00:04:07.440> into 00:04:07.670 --> 00:04:07.680 align:start position:0% contribute to the resilience into 00:04:07.680 --> 00:04:10.190 align:start position:0% contribute to the resilience into centralization<00:04:08.280> of<00:04:08.640> the<00:04:08.819> network<00:04:08.940> and<00:04:09.900> also 00:04:10.190 --> 00:04:10.200 align:start position:0% centralization of the network and also 00:04:10.200 --> 00:04:12.530 align:start position:0% centralization of the network and also to<00:04:10.439> protect<00:04:10.739> yourself<00:04:10.920> from<00:04:11.400> penalties<00:04:12.000> so 00:04:12.530 --> 00:04:12.540 align:start position:0% to protect yourself from penalties so 00:04:12.540 --> 00:04:14.210 align:start position:0% to protect yourself from penalties so what<00:04:12.659> we'll<00:04:12.840> go<00:04:12.959> over<00:04:13.080> today<00:04:13.439> actually<00:04:13.860> the 00:04:14.210 --> 00:04:14.220 align:start position:0% what we'll go over today actually the 00:04:14.220 --> 00:04:17.689 align:start position:0% what we'll go over today actually the ethereum<00:04:14.760> uh<00:04:15.599> protocol<00:04:15.979> incentivizes<00:04:16.979> you<00:04:17.160> to 00:04:17.689 --> 00:04:17.699 align:start position:0% ethereum uh protocol incentivizes you to 00:04:17.699 --> 00:04:19.610 align:start position:0% ethereum uh protocol incentivizes you to be<00:04:17.820> running<00:04:18.000> your<00:04:18.299> own<00:04:18.479> node<00:04:18.780> and<00:04:19.019> not<00:04:19.260> to<00:04:19.380> be 00:04:19.610 --> 00:04:19.620 align:start position:0% be running your own node and not to be 00:04:19.620 --> 00:04:22.550 align:start position:0% be running your own node and not to be aggregated<00:04:20.579> in<00:04:20.820> a<00:04:21.000> majority<00:04:21.299> of<00:04:21.660> any<00:04:21.900> kind<00:04:22.199> and 00:04:22.550 --> 00:04:22.560 align:start position:0% aggregated in a majority of any kind and 00:04:22.560 --> 00:04:26.030 align:start position:0% aggregated in a majority of any kind and so<00:04:22.740> we'll<00:04:22.919> get<00:04:23.100> a<00:04:23.220> bit<00:04:23.340> more<00:04:23.460> into<00:04:23.639> that 00:04:26.030 --> 00:04:26.040 align:start position:0% 00:04:26.040 --> 00:04:28.730 align:start position:0% so<00:04:26.520> really<00:04:26.759> quickly<00:04:27.060> the<00:04:27.240> agenda<00:04:27.720> uh<00:04:28.440> why<00:04:28.560> did 00:04:28.730 --> 00:04:28.740 align:start position:0% so really quickly the agenda uh why did 00:04:28.740 --> 00:04:30.650 align:start position:0% so really quickly the agenda uh why did ethereum<00:04:29.160> move<00:04:29.340> to<00:04:29.460> proof<00:04:29.699> of<00:04:29.820> stake 00:04:30.650 --> 00:04:30.660 align:start position:0% ethereum move to proof of stake 00:04:30.660 --> 00:04:33.469 align:start position:0% ethereum move to proof of stake node<00:04:31.440> infrastructure<00:04:32.220> landscape<00:04:32.759> and 00:04:33.469 --> 00:04:33.479 align:start position:0% node infrastructure landscape and 00:04:33.479 --> 00:04:35.810 align:start position:0% node infrastructure landscape and examining<00:04:33.960> decentralization<00:04:34.620> across<00:04:35.400> layers 00:04:35.810 --> 00:04:35.820 align:start position:0% examining decentralization across layers 00:04:35.820 --> 00:04:38.450 align:start position:0% examining decentralization across layers in<00:04:36.060> that<00:04:36.240> landscape<00:04:36.780> and<00:04:37.560> then<00:04:37.740> node<00:04:38.040> Runner 00:04:38.450 --> 00:04:38.460 align:start position:0% in that landscape and then node Runner 00:04:38.460 --> 00:04:40.670 align:start position:0% in that landscape and then node Runner options<00:04:38.759> and<00:04:39.060> so<00:04:39.240> Shane<00:04:39.479> will<00:04:39.660> get<00:04:39.780> up<00:04:39.960> here<00:04:40.139> uh 00:04:40.670 --> 00:04:40.680 align:start position:0% options and so Shane will get up here uh 00:04:40.680 --> 00:04:42.469 align:start position:0% options and so Shane will get up here uh to<00:04:40.919> run<00:04:41.100> you<00:04:41.220> through<00:04:41.400> different<00:04:41.639> node<00:04:42.060> Runner 00:04:42.469 --> 00:04:42.479 align:start position:0% to run you through different node Runner 00:04:42.479 --> 00:04:45.350 align:start position:0% to run you through different node Runner options<00:04:42.780> at<00:04:43.020> the<00:04:43.199> end 00:04:45.350 --> 00:04:45.360 align:start position:0% 00:04:45.360 --> 00:04:47.870 align:start position:0% okay<00:04:45.900> so<00:04:46.139> proof<00:04:46.440> of<00:04:46.560> stake<00:04:46.860> and<00:04:47.040> solo<00:04:47.400> sticky 00:04:47.870 --> 00:04:47.880 align:start position:0% okay so proof of stake and solo sticky 00:04:47.880 --> 00:04:51.110 align:start position:0% okay so proof of stake and solo sticky 101<00:04:48.300> so<00:04:48.900> she<00:04:49.139> buys<00:04:49.560> an<00:04:49.740> educational<00:04:50.100> shift<00:04:50.699> at 00:04:51.110 --> 00:04:51.120 align:start position:0% 101 so she buys an educational shift at 00:04:51.120 --> 00:04:53.749 align:start position:0% 101 so she buys an educational shift at onward<00:04:51.600> women<00:04:51.960> and<00:04:52.680> non-binary<00:04:53.280> folks<00:04:53.580> in<00:04:53.639> the 00:04:53.749 --> 00:04:53.759 align:start position:0% onward women and non-binary folks in the 00:04:53.759 --> 00:04:56.270 align:start position:0% onward women and non-binary folks in the crypto<00:04:54.060> ecosystem<00:04:54.479> so<00:04:54.840> I<00:04:55.020> am<00:04:55.139> a<00:04:55.320> teacher<00:04:55.620> a 00:04:56.270 --> 00:04:56.280 align:start position:0% crypto ecosystem so I am a teacher a 00:04:56.280 --> 00:04:58.070 align:start position:0% crypto ecosystem so I am a teacher a part<00:04:56.400> of<00:04:56.520> my<00:04:56.639> time<00:04:56.759> in<00:04:56.940> the<00:04:57.120> space<00:04:57.240> so<00:04:57.660> some<00:04:57.900> of 00:04:58.070 --> 00:04:58.080 align:start position:0% part of my time in the space so some of 00:04:58.080 --> 00:04:59.990 align:start position:0% part of my time in the space so some of this<00:04:58.139> is<00:04:58.320> familiar<00:04:58.800> to<00:04:58.979> you 00:04:59.990 --> 00:05:00.000 align:start position:0% this is familiar to you 00:05:00.000 --> 00:05:02.210 align:start position:0% this is familiar to you um<00:05:00.120> I<00:05:00.720> like<00:05:00.960> to<00:05:01.139> make<00:05:01.380> sure<00:05:01.500> everyone's<00:05:01.979> on<00:05:02.100> the 00:05:02.210 --> 00:05:02.220 align:start position:0% um I like to make sure everyone's on the 00:05:02.220 --> 00:05:04.610 align:start position:0% um I like to make sure everyone's on the same<00:05:02.400> page<00:05:02.639> by<00:05:03.240> explaining<00:05:03.780> things<00:05:03.960> before<00:05:04.259> we 00:05:04.610 --> 00:05:04.620 align:start position:0% same page by explaining things before we 00:05:04.620 --> 00:05:06.590 align:start position:0% same page by explaining things before we dive<00:05:04.740> in<00:05:05.040> so<00:05:05.639> a<00:05:05.880> quick<00:05:06.060> proof<00:05:06.419> of<00:05:06.540> State 00:05:06.590 --> 00:05:06.600 align:start position:0% dive in so a quick proof of State 00:05:06.600 --> 00:05:08.210 align:start position:0% dive in so a quick proof of State glossary<00:05:07.080> for<00:05:07.380> those<00:05:07.500> of<00:05:07.620> you<00:05:07.740> who<00:05:07.919> may<00:05:08.100> be 00:05:08.210 --> 00:05:08.220 align:start position:0% glossary for those of you who may be 00:05:08.220 --> 00:05:10.850 align:start position:0% glossary for those of you who may be unfamiliar<00:05:08.820> uh<00:05:09.660> so<00:05:09.780> proof<00:05:10.199> of<00:05:10.199> stake<00:05:10.500> is<00:05:10.680> a 00:05:10.850 --> 00:05:10.860 align:start position:0% unfamiliar uh so proof of stake is a 00:05:10.860 --> 00:05:13.189 align:start position:0% unfamiliar uh so proof of stake is a consensus<00:05:11.280> mechanism<00:05:11.699> where<00:05:12.300> evaluators<00:05:12.960> put 00:05:13.189 --> 00:05:13.199 align:start position:0% consensus mechanism where evaluators put 00:05:13.199 --> 00:05:15.469 align:start position:0% consensus mechanism where evaluators put Capital<00:05:13.380> At<00:05:13.800> Risk<00:05:14.100> by<00:05:14.460> staking<00:05:14.820> it<00:05:15.060> to 00:05:15.469 --> 00:05:15.479 align:start position:0% Capital At Risk by staking it to 00:05:15.479 --> 00:05:17.210 align:start position:0% Capital At Risk by staking it to validate<00:05:15.900> blocks<00:05:16.259> of<00:05:16.380> transactions<00:05:17.040> and 00:05:17.210 --> 00:05:17.220 align:start position:0% validate blocks of transactions and 00:05:17.220 --> 00:05:18.650 align:start position:0% validate blocks of transactions and secure<00:05:17.520> the<00:05:17.759> network 00:05:18.650 --> 00:05:18.660 align:start position:0% secure the network 00:05:18.660 --> 00:05:21.350 align:start position:0% secure the network a<00:05:19.259> consensus<00:05:19.800> mechanisms<00:05:20.340> are<00:05:20.460> just<00:05:20.699> how<00:05:21.120> a 00:05:21.350 --> 00:05:21.360 align:start position:0% a consensus mechanisms are just how a 00:05:21.360 --> 00:05:23.510 align:start position:0% a consensus mechanisms are just how a blockchain<00:05:21.780> protocol<00:05:22.259> or<00:05:22.860> a<00:05:22.979> group<00:05:23.100> of<00:05:23.280> any 00:05:23.510 --> 00:05:23.520 align:start position:0% blockchain protocol or a group of any 00:05:23.520 --> 00:05:26.270 align:start position:0% blockchain protocol or a group of any time<00:05:23.759> any<00:05:24.300> kind<00:05:24.539> really<00:05:24.960> uh<00:05:25.620> comes<00:05:25.979> to<00:05:26.160> the 00:05:26.270 --> 00:05:26.280 align:start position:0% time any kind really uh comes to the 00:05:26.280 --> 00:05:28.790 align:start position:0% time any kind really uh comes to the source<00:05:27.060> of<00:05:27.180> truth<00:05:27.479> about<00:05:27.720> something<00:05:28.080> and<00:05:28.680> it's 00:05:28.790 --> 00:05:28.800 align:start position:0% source of truth about something and it's 00:05:28.800 --> 00:05:30.469 align:start position:0% source of truth about something and it's really<00:05:29.039> important<00:05:29.340> in<00:05:29.520> blockchain<00:05:29.880> protocols 00:05:30.469 --> 00:05:30.479 align:start position:0% really important in blockchain protocols 00:05:30.479 --> 00:05:32.029 align:start position:0% really important in blockchain protocols especially<00:05:30.780> ethereum<00:05:31.380> that<00:05:31.560> we<00:05:31.680> have<00:05:31.800> one 00:05:32.029 --> 00:05:32.039 align:start position:0% especially ethereum that we have one 00:05:32.039 --> 00:05:34.129 align:start position:0% especially ethereum that we have one single<00:05:32.340> source<00:05:32.699> of<00:05:32.820> Truth<00:05:33.060> in<00:05:33.539> order<00:05:33.720> for<00:05:33.900> it 00:05:34.129 --> 00:05:34.139 align:start position:0% single source of Truth in order for it 00:05:34.139 --> 00:05:36.590 align:start position:0% single source of Truth in order for it to<00:05:34.259> function<00:05:34.560> properly 00:05:36.590 --> 00:05:36.600 align:start position:0% to function properly 00:05:36.600 --> 00:05:38.510 align:start position:0% to function properly a<00:05:37.080> staking<00:05:37.440> is<00:05:37.620> just<00:05:37.740> the<00:05:37.800> act<00:05:37.979> of<00:05:38.100> locking<00:05:38.400> up 00:05:38.510 --> 00:05:38.520 align:start position:0% a staking is just the act of locking up 00:05:38.520 --> 00:05:40.610 align:start position:0% a staking is just the act of locking up or<00:05:38.699> depositing<00:05:39.240> crypto 00:05:40.610 --> 00:05:40.620 align:start position:0% or depositing crypto 00:05:40.620 --> 00:05:42.590 align:start position:0% or depositing crypto an<00:05:41.039> a<00:05:41.280> validator<00:05:41.580> note<00:05:41.880> so<00:05:42.120> really<00:05:42.240> what<00:05:42.479> we're 00:05:42.590 --> 00:05:42.600 align:start position:0% an a validator note so really what we're 00:05:42.600 --> 00:05:44.450 align:start position:0% an a validator note so really what we're focusing<00:05:42.960> on<00:05:43.080> today<00:05:43.320> is<00:05:43.919> a<00:05:44.100> note<00:05:44.220> that 00:05:44.450 --> 00:05:44.460 align:start position:0% focusing on today is a note that 00:05:44.460 --> 00:05:47.870 align:start position:0% focusing on today is a note that processes<00:05:44.940> transaction<00:05:45.479> uh<00:05:46.440> sorry<00:05:47.039> adds<00:05:47.759> new 00:05:47.870 --> 00:05:47.880 align:start position:0% processes transaction uh sorry adds new 00:05:47.880 --> 00:05:50.570 align:start position:0% processes transaction uh sorry adds new box<00:05:48.120> to<00:05:48.419> the<00:05:48.539> blockchain<00:05:48.900> and<00:05:49.199> stores<00:05:49.380> data<00:05:49.979> a 00:05:50.570 --> 00:05:50.580 align:start position:0% box to the blockchain and stores data a 00:05:50.580 --> 00:05:52.550 align:start position:0% box to the blockchain and stores data a little<00:05:50.880> misspelling<00:05:51.419> there<00:05:51.539> and<00:05:52.199> so<00:05:52.320> they're 00:05:52.550 --> 00:05:52.560 align:start position:0% little misspelling there and so they're 00:05:52.560 --> 00:05:54.350 align:start position:0% little misspelling there and so they're responsible<00:05:52.919> for<00:05:53.160> proposing<00:05:53.759> blocks<00:05:54.300> of 00:05:54.350 --> 00:05:54.360 align:start position:0% responsible for proposing blocks of 00:05:54.360 --> 00:05:57.170 align:start position:0% responsible for proposing blocks of transactions<00:05:55.080> and<00:05:55.979> attesting<00:05:56.639> uh<00:05:57.000> the 00:05:57.170 --> 00:05:57.180 align:start position:0% transactions and attesting uh the 00:05:57.180 --> 00:05:59.210 align:start position:0% transactions and attesting uh the transactions<00:05:57.720> and<00:05:57.900> blocks<00:05:58.259> are<00:05:58.380> true<00:05:58.560> so<00:05:59.160> if 00:05:59.210 --> 00:05:59.220 align:start position:0% transactions and blocks are true so if 00:05:59.220 --> 00:06:00.710 align:start position:0% transactions and blocks are true so if you're<00:05:59.400> running<00:05:59.520> a<00:05:59.759> validator<00:06:00.060> node<00:06:00.419> there 00:06:00.710 --> 00:06:00.720 align:start position:0% you're running a validator node there 00:06:00.720 --> 00:06:02.510 align:start position:0% you're running a validator node there were<00:06:00.900> sometimes<00:06:01.440> responsible<00:06:01.860> for<00:06:02.039> proposing 00:06:02.510 --> 00:06:02.520 align:start position:0% were sometimes responsible for proposing 00:06:02.520 --> 00:06:04.850 align:start position:0% were sometimes responsible for proposing the<00:06:02.639> block<00:06:02.820> transactions<00:06:03.660> and<00:06:04.259> sometimes<00:06:04.620> for 00:06:04.850 --> 00:06:04.860 align:start position:0% the block transactions and sometimes for 00:06:04.860 --> 00:06:06.770 align:start position:0% the block transactions and sometimes for a<00:06:05.160> testing<00:06:05.460> at<00:06:05.580> the<00:06:05.759> transactions<00:06:06.360> a 00:06:06.770 --> 00:06:06.780 align:start position:0% a testing at the transactions a 00:06:06.780 --> 00:06:08.749 align:start position:0% a testing at the transactions a different<00:06:06.900> block<00:06:07.139> proposer<00:06:07.800> is<00:06:08.220> proposing 00:06:08.749 --> 00:06:08.759 align:start position:0% different block proposer is proposing 00:06:08.759 --> 00:06:11.330 align:start position:0% different block proposer is proposing our<00:06:09.000> true<00:06:09.240> so<00:06:10.139> that's<00:06:10.320> your<00:06:10.500> quick<00:06:10.740> glossary 00:06:11.330 --> 00:06:11.340 align:start position:0% our true so that's your quick glossary 00:06:11.340 --> 00:06:13.670 align:start position:0% our true so that's your quick glossary for<00:06:11.639> those<00:06:11.759> of<00:06:11.880> you<00:06:12.000> who<00:06:12.120> are<00:06:12.240> familiar<00:06:12.720> and<00:06:13.440> so 00:06:13.670 --> 00:06:13.680 align:start position:0% for those of you who are familiar and so 00:06:13.680 --> 00:06:15.409 align:start position:0% for those of you who are familiar and so why<00:06:13.860> did<00:06:13.979> ethereum<00:06:14.400> move<00:06:14.580> to<00:06:14.759> prove<00:06:15.060> a<00:06:15.120> stake 00:06:15.409 --> 00:06:15.419 align:start position:0% why did ethereum move to prove a stake 00:06:15.419 --> 00:06:17.689 align:start position:0% why did ethereum move to prove a stake of<00:06:16.080> reducing<00:06:16.500> barriers<00:06:16.919> to<00:06:17.100> entry<00:06:17.460> through 00:06:17.689 --> 00:06:17.699 align:start position:0% of reducing barriers to entry through 00:06:17.699 --> 00:06:19.969 align:start position:0% of reducing barriers to entry through Network<00:06:18.000> participants<00:06:18.600> so<00:06:19.199> more<00:06:19.500> people<00:06:19.680> have 00:06:19.969 --> 00:06:19.979 align:start position:0% Network participants so more people have 00:06:19.979 --> 00:06:22.370 align:start position:0% Network participants so more people have Capital<00:06:20.220> to<00:06:20.639> stake<00:06:20.940> uh<00:06:21.479> that<00:06:21.720> improve<00:06:22.080> of<00:06:22.199> work 00:06:22.370 --> 00:06:22.380 align:start position:0% Capital to stake uh that improve of work 00:06:22.380 --> 00:06:24.950 align:start position:0% Capital to stake uh that improve of work where<00:06:22.620> you<00:06:22.740> would<00:06:22.860> need<00:06:23.039> uh<00:06:23.699> gpus<00:06:24.240> electricity 00:06:24.950 --> 00:06:24.960 align:start position:0% where you would need uh gpus electricity 00:06:24.960 --> 00:06:27.350 align:start position:0% where you would need uh gpus electricity power<00:06:25.319> a<00:06:25.680> lot<00:06:25.860> of<00:06:25.979> capital<00:06:26.160> in<00:06:26.940> order<00:06:27.060> to 00:06:27.350 --> 00:06:27.360 align:start position:0% power a lot of capital in order to 00:06:27.360 --> 00:06:29.029 align:start position:0% power a lot of capital in order to validate<00:06:27.780> transactions<00:06:28.440> and<00:06:28.620> secure<00:06:28.860> the 00:06:29.029 --> 00:06:29.039 align:start position:0% validate transactions and secure the 00:06:29.039 --> 00:06:31.490 align:start position:0% validate transactions and secure the network<00:06:29.240> uh<00:06:30.240> reduce<00:06:30.479> ethereum's<00:06:31.199> carbon 00:06:31.490 --> 00:06:31.500 align:start position:0% network uh reduce ethereum's carbon 00:06:31.500 --> 00:06:34.790 align:start position:0% network uh reduce ethereum's carbon footprint<00:06:31.979> by<00:06:32.160> 99.5<00:06:33.139> that's<00:06:34.139> really<00:06:34.440> exciting 00:06:34.790 --> 00:06:34.800 align:start position:0% footprint by 99.5 that's really exciting 00:06:34.800 --> 00:06:36.230 align:start position:0% footprint by 99.5 that's really exciting for<00:06:34.979> the<00:06:35.100> ecosystem<00:06:35.460> especially<00:06:36.060> when<00:06:36.120> we're 00:06:36.230 --> 00:06:36.240 align:start position:0% for the ecosystem especially when we're 00:06:36.240 --> 00:06:37.909 align:start position:0% for the ecosystem especially when we're thinking<00:06:36.479> about<00:06:36.720> attracting<00:06:37.620> new 00:06:37.909 --> 00:06:37.919 align:start position:0% thinking about attracting new 00:06:37.919 --> 00:06:40.550 align:start position:0% thinking about attracting new applications<00:06:38.520> and<00:06:38.940> users<00:06:39.360> who<00:06:39.660> are<00:06:39.840> extremely 00:06:40.550 --> 00:06:40.560 align:start position:0% applications and users who are extremely 00:06:40.560 --> 00:06:47.230 align:start position:0% applications and users who are extremely work 00:06:47.230 --> 00:06:47.240 align:start position:0% 00:06:47.240 --> 00:06:54.290 align:start position:0% [Music] 00:06:54.290 --> 00:06:54.300 align:start position:0% [Music] 00:06:54.300 --> 00:06:57.050 align:start position:0% [Music] and<00:06:54.960> so<00:06:55.139> also<00:06:55.680> means<00:06:56.039> that<00:06:56.160> we<00:06:56.280> need<00:06:56.400> to<00:06:56.639> issue 00:06:57.050 --> 00:06:57.060 align:start position:0% and so also means that we need to issue 00:06:57.060 --> 00:06:59.689 align:start position:0% and so also means that we need to issue to<00:06:57.720> incentivize<00:06:58.319> validators<00:06:58.919> to<00:06:59.220> secure<00:06:59.460> the 00:06:59.689 --> 00:06:59.699 align:start position:0% to incentivize validators to secure the 00:06:59.699 --> 00:07:01.550 align:start position:0% to incentivize validators to secure the network 00:07:01.550 --> 00:07:01.560 align:start position:0% network 00:07:01.560 --> 00:07:05.570 align:start position:0% network and<00:07:02.039> so<00:07:02.280> 51<00:07:03.020> attacks<00:07:04.020> are<00:07:04.500> more<00:07:04.740> costly<00:07:05.280> and 00:07:05.570 --> 00:07:05.580 align:start position:0% and so 51 attacks are more costly and 00:07:05.580 --> 00:07:07.490 align:start position:0% and so 51 attacks are more costly and difficult<00:07:05.880> to<00:07:06.120> do<00:07:06.240> than<00:07:06.479> they<00:07:06.720> were<00:07:06.900> in<00:07:07.080> proof 00:07:07.490 --> 00:07:07.500 align:start position:0% difficult to do than they were in proof 00:07:07.500 --> 00:07:09.469 align:start position:0% difficult to do than they were in proof of<00:07:07.560> work 00:07:09.469 --> 00:07:09.479 align:start position:0% of work 00:07:09.479 --> 00:07:11.510 align:start position:0% of work and<00:07:09.960> it's<00:07:10.139> easier<00:07:10.500> to<00:07:10.740> have<00:07:10.979> a<00:07:11.340> social 00:07:11.510 --> 00:07:11.520 align:start position:0% and it's easier to have a social 00:07:11.520 --> 00:07:14.090 align:start position:0% and it's easier to have a social recovery<00:07:12.240> if<00:07:12.780> something<00:07:13.080> happened<00:07:13.440> uh 00:07:14.090 --> 00:07:14.100 align:start position:0% recovery if something happened uh 00:07:14.100 --> 00:07:37.270 align:start position:0% recovery if something happened uh negative<00:07:14.460> happens 00:07:37.270 --> 00:07:37.280 align:start position:0% 00:07:37.280 --> 00:07:54.430 align:start position:0% having<00:07:38.280> uh<00:07:39.060> a<00:07:39.720> lot<00:07:39.840> of<00:07:40.020> power 00:07:54.430 --> 00:07:54.440 align:start position:0% 00:07:54.440 --> 00:07:58.189 align:start position:0% you<00:07:55.440> must<00:07:55.620> commit<00:07:56.039> some<00:07:56.340> type<00:07:56.580> of<00:07:56.699> capital 00:07:58.189 --> 00:07:58.199 align:start position:0% you must commit some type of capital 00:07:58.199 --> 00:08:42.490 align:start position:0% you must commit some type of capital foreign 00:08:42.490 --> 00:08:42.500 align:start position:0% 00:08:42.500 --> 00:08:44.269 align:start position:0% for<00:08:43.500> you 00:08:44.269 --> 00:08:44.279 align:start position:0% for you 00:08:44.279 --> 00:08:47.570 align:start position:0% for you and<00:08:44.760> so<00:08:45.000> going<00:08:45.360> to<00:08:45.600> take<00:08:45.839> about<00:08:46.020> 25<00:08:46.440> cut<00:08:47.399> of 00:08:47.570 --> 00:08:47.580 align:start position:0% and so going to take about 25 cut of 00:08:47.580 --> 00:08:50.030 align:start position:0% and so going to take about 25 cut of earnings<00:08:47.940> from<00:08:48.180> stickers 00:08:50.030 --> 00:08:50.040 align:start position:0% earnings from stickers 00:08:50.040 --> 00:08:52.610 align:start position:0% earnings from stickers uh<00:08:50.459> your<00:08:50.760> keys<00:08:51.120> in<00:08:51.240> your<00:08:51.360> crypto<00:08:51.779> so<00:08:52.320> when 00:08:52.610 --> 00:08:52.620 align:start position:0% uh your keys in your crypto so when 00:08:52.620 --> 00:08:54.350 align:start position:0% uh your keys in your crypto so when you're<00:08:52.740> speaking<00:08:53.100> with<00:08:53.220> other<00:08:53.339> entities<00:08:53.820> they 00:08:54.350 --> 00:08:54.360 align:start position:0% you're speaking with other entities they 00:08:54.360 --> 00:08:56.870 align:start position:0% you're speaking with other entities they ultimately<00:08:54.779> have<00:08:55.080> your<00:08:55.320> private<00:08:55.680> keys<00:08:56.100> and<00:08:56.580> so 00:08:56.870 --> 00:08:56.880 align:start position:0% ultimately have your private keys and so 00:08:56.880 --> 00:08:58.490 align:start position:0% ultimately have your private keys and so you<00:08:57.060> ultimately<00:08:57.420> do<00:08:57.660> not<00:08:57.839> have<00:08:57.959> final<00:08:58.200> access 00:08:58.490 --> 00:08:58.500 align:start position:0% you ultimately do not have final access 00:08:58.500 --> 00:09:08.230 align:start position:0% you ultimately do not have final access to<00:08:58.800> your<00:08:58.980> crypto<00:08:59.339> which<00:08:59.820> is<00:08:59.940> not<00:09:00.120> the<00:09:00.300> case 00:09:08.230 --> 00:09:08.240 align:start position:0% 00:09:08.240 --> 00:09:11.690 align:start position:0% Hardware<00:09:09.240> setups<00:09:09.959> but<00:09:10.080> you<00:09:10.380> know<00:09:10.440> you<00:09:10.680> can<00:09:10.920> uh 00:09:11.690 --> 00:09:11.700 align:start position:0% Hardware setups but you know you can uh 00:09:11.700 --> 00:09:14.210 align:start position:0% Hardware setups but you know you can uh you're<00:09:12.300> not<00:09:12.420> locked<00:09:12.779> into<00:09:12.899> one<00:09:13.140> type<00:09:13.320> of<00:09:13.440> setup 00:09:14.210 --> 00:09:14.220 align:start position:0% you're not locked into one type of setup 00:09:14.220 --> 00:09:16.550 align:start position:0% you're not locked into one type of setup and<00:09:14.640> reduce<00:09:15.000> the<00:09:15.360> risk<00:09:15.660> of<00:09:15.779> large<00:09:16.019> events 00:09:16.550 --> 00:09:16.560 align:start position:0% and reduce the risk of large events 00:09:16.560 --> 00:09:17.930 align:start position:0% and reduce the risk of large events flashing<00:09:16.920> so<00:09:17.160> we're<00:09:17.279> going<00:09:17.399> to<00:09:17.459> go<00:09:17.580> over<00:09:17.700> this 00:09:17.930 --> 00:09:17.940 align:start position:0% flashing so we're going to go over this 00:09:17.940 --> 00:09:20.210 align:start position:0% flashing so we're going to go over this a<00:09:18.060> bit<00:09:18.180> more<00:09:18.300> but<00:09:18.959> if<00:09:19.140> you're<00:09:19.320> joining<00:09:19.800> a<00:09:19.980> large 00:09:20.210 --> 00:09:20.220 align:start position:0% a bit more but if you're joining a large 00:09:20.220 --> 00:09:22.970 align:start position:0% a bit more but if you're joining a large pool<00:09:20.580> that<00:09:21.120> has<00:09:21.779> um<00:09:21.839> majority<00:09:22.560> of<00:09:22.680> the<00:09:22.800> network 00:09:22.970 --> 00:09:22.980 align:start position:0% pool that has um majority of the network 00:09:22.980 --> 00:09:24.889 align:start position:0% pool that has um majority of the network and<00:09:23.399> if<00:09:23.640> something<00:09:23.880> happens<00:09:24.180> to<00:09:24.480> that<00:09:24.660> pool 00:09:24.889 --> 00:09:24.899 align:start position:0% and if something happens to that pool 00:09:24.899 --> 00:09:27.710 align:start position:0% and if something happens to that pool they<00:09:25.740> go<00:09:25.920> offline<00:09:26.220> and<00:09:26.399> have<00:09:26.640> trouble 00:09:27.710 --> 00:09:27.720 align:start position:0% they go offline and have trouble 00:09:27.720 --> 00:09:29.750 align:start position:0% they go offline and have trouble um<00:09:27.779> accessing<00:09:28.320> the<00:09:28.440> network<00:09:28.620> you're<00:09:29.399> going<00:09:29.640> to 00:09:29.750 --> 00:09:29.760 align:start position:0% um accessing the network you're going to 00:09:29.760 --> 00:09:31.310 align:start position:0% um accessing the network you're going to get<00:09:29.880> flashed<00:09:30.360> as<00:09:30.480> part<00:09:30.660> of<00:09:30.779> that<00:09:30.899> but<00:09:31.200> if 00:09:31.310 --> 00:09:31.320 align:start position:0% get flashed as part of that but if 00:09:31.320 --> 00:09:33.110 align:start position:0% get flashed as part of that but if you're<00:09:31.440> a<00:09:31.620> solo<00:09:31.920> speaker<00:09:32.160> you're<00:09:32.760> not<00:09:32.940> going 00:09:33.110 --> 00:09:33.120 align:start position:0% you're a solo speaker you're not going 00:09:33.120 --> 00:09:53.410 align:start position:0% you're a solo speaker you're not going to<00:09:33.180> run<00:09:33.360> into<00:09:33.480> that<00:09:33.660> risk 00:09:53.410 --> 00:09:53.420 align:start position:0% 00:09:53.420 --> 00:09:56.210 align:start position:0% is<00:09:54.420> true 00:09:56.210 --> 00:09:56.220 align:start position:0% is true 00:09:56.220 --> 00:10:06.889 align:start position:0% is true protocol 00:10:06.889 --> 00:10:06.899 align:start position:0% 00:10:06.899 --> 00:10:08.870 align:start position:0% however<00:10:07.620> there<00:10:07.740> are<00:10:07.860> some<00:10:08.040> challenges<00:10:08.519> with 00:10:08.870 --> 00:10:08.880 align:start position:0% however there are some challenges with 00:10:08.880 --> 00:10:11.750 align:start position:0% however there are some challenges with solo<00:10:09.300> validating<00:10:09.720> and<00:10:10.440> so<00:10:10.680> uh<00:10:11.160> this<00:10:11.519> morning 00:10:11.750 --> 00:10:11.760 align:start position:0% solo validating and so uh this morning 00:10:11.760 --> 00:10:14.690 align:start position:0% solo validating and so uh this morning this<00:10:12.240> was<00:10:12.480> the<00:10:12.660> price<00:10:12.779> of<00:10:12.959> 32<00:10:13.440> East<00:10:13.740> which<00:10:14.519> is 00:10:14.690 --> 00:10:14.700 align:start position:0% this was the price of 32 East which is 00:10:14.700 --> 00:10:16.370 align:start position:0% this was the price of 32 East which is not<00:10:14.820> acceptable<00:10:15.240> to<00:10:15.420> many<00:10:15.600> who<00:10:15.839> want<00:10:16.019> to<00:10:16.140> take 00:10:16.370 --> 00:10:16.380 align:start position:0% not acceptable to many who want to take 00:10:16.380 --> 00:10:18.110 align:start position:0% not acceptable to many who want to take it<00:10:16.560> home<00:10:16.740> even<00:10:17.220> if<00:10:17.459> we<00:10:17.580> think<00:10:17.760> about<00:10:17.820> how 00:10:18.110 --> 00:10:18.120 align:start position:0% it home even if we think about how 00:10:18.120 --> 00:10:20.870 align:start position:0% it home even if we think about how large.com<00:10:18.839> is<00:10:19.320> right<00:10:19.560> now<00:10:19.680> it<00:10:20.339> was<00:10:20.519> not<00:10:20.640> this 00:10:20.870 --> 00:10:20.880 align:start position:0% large.com is right now it was not this 00:10:20.880 --> 00:10:24.650 align:start position:0% large.com is right now it was not this large<00:10:21.180> for<00:10:21.720> the<00:10:21.959> past<00:10:22.700> and<00:10:23.700> so<00:10:23.940> we're<00:10:24.240> having<00:10:24.480> a 00:10:24.650 --> 00:10:24.660 align:start position:0% large for the past and so we're having a 00:10:24.660 --> 00:10:26.030 align:start position:0% large for the past and so we're having a lot<00:10:24.779> of<00:10:24.899> new<00:10:25.019> participants<00:10:25.500> joining<00:10:25.920> our 00:10:26.030 --> 00:10:26.040 align:start position:0% lot of new participants joining our 00:10:26.040 --> 00:10:27.829 align:start position:0% lot of new participants joining our ecosystem<00:10:26.519> and<00:10:27.120> it's<00:10:27.180> really<00:10:27.480> hard<00:10:27.660> to 00:10:27.829 --> 00:10:27.839 align:start position:0% ecosystem and it's really hard to 00:10:27.839 --> 00:10:29.870 align:start position:0% ecosystem and it's really hard to accumulate<00:10:28.320> 32<00:10:28.800> each 00:10:29.870 --> 00:10:29.880 align:start position:0% accumulate 32 each 00:10:29.880 --> 00:10:32.150 align:start position:0% accumulate 32 each uh<00:10:30.600> so<00:10:30.839> there<00:10:31.080> is<00:10:31.260> still<00:10:31.380> a<00:10:31.560> cost<00:10:31.740> of<00:10:31.980> Hardware 00:10:32.150 --> 00:10:32.160 align:start position:0% uh so there is still a cost of Hardware 00:10:32.160 --> 00:10:34.430 align:start position:0% uh so there is still a cost of Hardware electricity<00:10:32.940> ongoing<00:10:33.600> maintenance<00:10:33.959> of<00:10:34.200> these 00:10:34.430 --> 00:10:34.440 align:start position:0% electricity ongoing maintenance of these 00:10:34.440 --> 00:10:36.530 align:start position:0% electricity ongoing maintenance of these notes<00:10:34.740> it's<00:10:35.160> not<00:10:35.399> set<00:10:35.640> it<00:10:35.820> and<00:10:35.940> forget<00:10:36.120> it<00:10:36.360> in 00:10:36.530 --> 00:10:36.540 align:start position:0% notes it's not set it and forget it in 00:10:36.540 --> 00:10:38.210 align:start position:0% notes it's not set it and forget it in your<00:10:36.660> home 00:10:38.210 --> 00:10:38.220 align:start position:0% your home 00:10:38.220 --> 00:10:40.070 align:start position:0% your home you<00:10:38.760> have<00:10:38.880> to<00:10:39.000> technical<00:10:39.420> know-how<00:10:39.959> to 00:10:40.070 --> 00:10:40.080 align:start position:0% you have to technical know-how to 00:10:40.080 --> 00:10:41.630 align:start position:0% you have to technical know-how to develop<00:10:40.380> and<00:10:40.560> operate<00:10:40.980> an<00:10:41.160> ethereum 00:10:41.630 --> 00:10:41.640 align:start position:0% develop and operate an ethereum 00:10:41.640 --> 00:10:43.670 align:start position:0% develop and operate an ethereum validator<00:10:42.120> so<00:10:42.540> there's<00:10:42.720> lots<00:10:43.080> of<00:10:43.140> tutorials 00:10:43.670 --> 00:10:43.680 align:start position:0% validator so there's lots of tutorials 00:10:43.680 --> 00:10:46.009 align:start position:0% validator so there's lots of tutorials but<00:10:44.160> if<00:10:44.279> you're<00:10:44.459> not<00:10:44.579> very<00:10:44.820> technical<00:10:45.120> it<00:10:45.899> will 00:10:46.009 --> 00:10:46.019 align:start position:0% but if you're not very technical it will 00:10:46.019 --> 00:10:48.710 align:start position:0% but if you're not very technical it will be<00:10:46.140> difficult<00:10:46.459> a<00:10:47.459> secure<00:10:47.820> Key<00:10:48.060> Management<00:10:48.300> so 00:10:48.710 --> 00:10:48.720 align:start position:0% be difficult a secure Key Management so 00:10:48.720 --> 00:10:50.210 align:start position:0% be difficult a secure Key Management so whenever<00:10:49.019> you're<00:10:49.200> managing<00:10:49.560> your<00:10:49.740> own<00:10:49.860> Keys 00:10:50.210 --> 00:10:50.220 align:start position:0% whenever you're managing your own Keys 00:10:50.220 --> 00:10:52.069 align:start position:0% whenever you're managing your own Keys you<00:10:50.459> have<00:10:50.579> to<00:10:50.700> have<00:10:50.880> very<00:10:51.480> good<00:10:51.660> practices 00:10:52.069 --> 00:10:52.079 align:start position:0% you have to have very good practices 00:10:52.079 --> 00:10:54.590 align:start position:0% you have to have very good practices around<00:10:52.560> keeping<00:10:53.100> it<00:10:53.279> secure<00:10:53.640> if<00:10:54.300> you<00:10:54.480> lose 00:10:54.590 --> 00:10:54.600 align:start position:0% around keeping it secure if you lose 00:10:54.600 --> 00:10:56.870 align:start position:0% around keeping it secure if you lose your<00:10:54.839> keys<00:10:55.200> it's<00:10:55.560> not<00:10:55.860> a<00:10:56.040> good<00:10:56.160> situation<00:10:56.519> for 00:10:56.870 --> 00:10:56.880 align:start position:0% your keys it's not a good situation for 00:10:56.880 --> 00:11:03.730 align:start position:0% your keys it's not a good situation for you 00:11:03.730 --> 00:11:03.740 align:start position:0% 00:11:03.740 --> 00:11:33.590 align:start position:0% and<00:11:04.740> it<00:11:04.920> maximizes<00:11:05.579> rewards 00:11:33.590 --> 00:11:33.600 align:start position:0% 00:11:33.600 --> 00:11:35.090 align:start position:0% um it's<00:11:33.839> locked<00:11:34.140> up<00:11:34.260> until<00:11:34.560> this<00:11:34.920> next 00:11:35.090 --> 00:11:35.100 align:start position:0% um it's locked up until this next 00:11:35.100 --> 00:12:09.310 align:start position:0% um it's locked up until this next upgrade 00:12:09.310 --> 00:12:09.320 align:start position:0% 00:12:09.320 --> 00:12:12.949 align:start position:0% from<00:12:10.320> this<00:12:10.860> not<00:12:11.579> to<00:12:11.820> you<00:12:12.300> know<00:12:12.420> say<00:12:12.779> anything 00:12:12.949 --> 00:12:12.959 align:start position:0% from this not to you know say anything 00:12:12.959 --> 00:12:15.110 align:start position:0% from this not to you know say anything bad<00:12:13.260> about<00:12:13.440> water 00:12:15.110 --> 00:12:15.120 align:start position:0% bad about water 00:12:15.120 --> 00:12:17.150 align:start position:0% bad about water so<00:12:15.660> then<00:12:15.779> what<00:12:16.019> is<00:12:16.140> the<00:12:16.260> validator<00:12:16.620> landscape 00:12:17.150 --> 00:12:17.160 align:start position:0% so then what is the validator landscape 00:12:17.160 --> 00:12:18.769 align:start position:0% so then what is the validator landscape reality<00:12:17.519> taking<00:12:17.880> into<00:12:18.180> account<00:12:18.480> the 00:12:18.769 --> 00:12:18.779 align:start position:0% reality taking into account the 00:12:18.779 --> 00:12:20.630 align:start position:0% reality taking into account the requirements<00:12:19.200> and<00:12:19.380> challenges 00:12:20.630 --> 00:12:20.640 align:start position:0% requirements and challenges 00:12:20.640 --> 00:12:22.090 align:start position:0% requirements and challenges um 00:12:22.090 --> 00:12:22.100 align:start position:0% um 00:12:22.100 --> 00:12:23.930 align:start position:0% um what<00:12:23.100> if<00:12:23.279> they<00:12:23.339> don't<00:12:23.459> have<00:12:23.579> the<00:12:23.640> technical 00:12:23.930 --> 00:12:23.940 align:start position:0% what if they don't have the technical 00:12:23.940 --> 00:12:25.430 align:start position:0% what if they don't have the technical know-how<00:12:24.420> what<00:12:24.720> if<00:12:24.899> they<00:12:25.019> don't<00:12:25.140> have<00:12:25.260> the 00:12:25.430 --> 00:12:25.440 align:start position:0% know-how what if they don't have the 00:12:25.440 --> 00:12:28.130 align:start position:0% know-how what if they don't have the time<00:12:25.680> uh<00:12:26.339> inability<00:12:27.000> to<00:12:27.300> continue<00:12:27.480> managing 00:12:28.130 --> 00:12:28.140 align:start position:0% time uh inability to continue managing 00:12:28.140 --> 00:12:32.870 align:start position:0% time uh inability to continue managing after<00:12:28.380> setup<00:12:28.920> uh<00:12:29.820> so<00:12:30.420> um<00:12:30.920> via<00:12:31.920> a<00:12:32.160> service<00:12:32.459> a 00:12:32.870 --> 00:12:32.880 align:start position:0% after setup uh so um via a service a 00:12:32.880 --> 00:12:35.210 align:start position:0% after setup uh so um via a service a pool<00:12:33.060> or<00:12:33.360> an<00:12:33.480> exchange 00:12:35.210 --> 00:12:35.220 align:start position:0% pool or an exchange 00:12:35.220 --> 00:12:37.130 align:start position:0% pool or an exchange and<00:12:35.700> these<00:12:36.000> options<00:12:36.240> are<00:12:36.540> wonderful<00:12:36.899> because 00:12:37.130 --> 00:12:37.140 align:start position:0% and these options are wonderful because 00:12:37.140 --> 00:12:39.350 align:start position:0% and these options are wonderful because we<00:12:37.440> increase<00:12:37.620> the<00:12:37.920> participation<00:12:38.459> of 00:12:39.350 --> 00:12:39.360 align:start position:0% we increase the participation of 00:12:39.360 --> 00:12:41.569 align:start position:0% we increase the participation of individuals<00:12:40.079> staking<00:12:40.620> in<00:12:40.860> the<00:12:40.980> ethereum<00:12:41.339> at 00:12:41.569 --> 00:12:41.579 align:start position:0% individuals staking in the ethereum at 00:12:41.579 --> 00:12:42.290 align:start position:0% individuals staking in the ethereum at work 00:12:42.290 --> 00:12:42.300 align:start position:0% work 00:12:42.300 --> 00:12:44.509 align:start position:0% work uh<00:12:42.899> but<00:12:43.079> they<00:12:43.260> aren't<00:12:43.380> a<00:12:43.620> deal<00:12:43.800> for<00:12:44.100> resilience 00:12:44.509 --> 00:12:44.519 align:start position:0% uh but they aren't a deal for resilience 00:12:44.519 --> 00:12:47.030 align:start position:0% uh but they aren't a deal for resilience robustness<00:12:45.180> security<00:12:45.779> and<00:12:46.500> all<00:12:46.620> those<00:12:46.860> things 00:12:47.030 --> 00:12:47.040 align:start position:0% robustness security and all those things 00:12:47.040 --> 00:12:50.509 align:start position:0% robustness security and all those things we<00:12:47.339> want<00:12:47.519> uh<00:12:48.300> for<00:12:48.480> the<00:12:48.720> ethereum<00:12:49.079> protocol<00:12:49.920> and 00:12:50.509 --> 00:12:50.519 align:start position:0% we want uh for the ethereum protocol and 00:12:50.519 --> 00:12:52.430 align:start position:0% we want uh for the ethereum protocol and so<00:12:50.700> then<00:12:50.940> knowing<00:12:51.839> this<00:12:51.959> knowing<00:12:52.320> that 00:12:52.430 --> 00:12:52.440 align:start position:0% so then knowing this knowing that 00:12:52.440 --> 00:12:53.930 align:start position:0% so then knowing this knowing that there's<00:12:52.620> more<00:12:52.800> options<00:12:53.040> what<00:12:53.459> is<00:12:53.639> the<00:12:53.760> actual 00:12:53.930 --> 00:12:53.940 align:start position:0% there's more options what is the actual 00:12:53.940 --> 00:12:58.490 align:start position:0% there's more options what is the actual state<00:12:54.240> of<00:12:54.660> the<00:12:54.779> validator<00:12:55.260> landscape<00:12:55.740> today 00:12:58.490 --> 00:12:58.500 align:start position:0% 00:12:58.500 --> 00:13:01.150 align:start position:0% so<00:12:59.459> really<00:12:59.700> quickly<00:13:00.120> uh 00:13:01.150 --> 00:13:01.160 align:start position:0% so really quickly uh 00:13:01.160 --> 00:13:04.550 align:start position:0% so really quickly uh landscape<00:13:02.160> has<00:13:02.519> many<00:13:02.760> players<00:13:03.360> and<00:13:04.079> so<00:13:04.320> we 00:13:04.550 --> 00:13:04.560 align:start position:0% landscape has many players and so we 00:13:04.560 --> 00:13:06.710 align:start position:0% landscape has many players and so we have<00:13:04.740> a<00:13:04.920> smart<00:13:05.100> contract<00:13:05.579> platforms<00:13:06.180> so<00:13:06.420> there 00:13:06.710 --> 00:13:06.720 align:start position:0% have a smart contract platforms so there 00:13:06.720 --> 00:13:09.310 align:start position:0% have a smart contract platforms so there was<00:13:06.959> like<00:13:07.200> ethereum<00:13:07.680> we<00:13:08.279> have<00:13:08.399> software 00:13:09.310 --> 00:13:09.320 align:start position:0% was like ethereum we have software 00:13:09.320 --> 00:13:11.509 align:start position:0% was like ethereum we have software infrastructure<00:13:10.320> providers<00:13:10.740> we<00:13:11.399> have 00:13:11.509 --> 00:13:11.519 align:start position:0% infrastructure providers we have 00:13:11.519 --> 00:13:13.670 align:start position:0% infrastructure providers we have Hardware<00:13:11.839> infrastructure<00:13:12.839> providers<00:13:13.380> as 00:13:13.670 --> 00:13:13.680 align:start position:0% Hardware infrastructure providers as 00:13:13.680 --> 00:13:16.790 align:start position:0% Hardware infrastructure providers as well<00:13:13.920> uh<00:13:14.880> they<00:13:15.120> have<00:13:15.360> solo<00:13:15.839> stickers<00:13:16.260> we<00:13:16.680> have 00:13:16.790 --> 00:13:16.800 align:start position:0% well uh they have solo stickers we have 00:13:16.800 --> 00:13:19.730 align:start position:0% well uh they have solo stickers we have liquid<00:13:17.220> staking<00:13:17.579> protocols<00:13:18.360> we<00:13:19.019> have<00:13:19.200> seeking 00:13:19.730 --> 00:13:19.740 align:start position:0% liquid staking protocols we have seeking 00:13:19.740 --> 00:13:22.129 align:start position:0% liquid staking protocols we have seeking service<00:13:19.980> businesses<00:13:20.700> liquid<00:13:21.420> stickers<00:13:21.899> and 00:13:22.129 --> 00:13:22.139 align:start position:0% service businesses liquid stickers and 00:13:22.139 --> 00:13:23.870 align:start position:0% service businesses liquid stickers and we<00:13:22.260> have<00:13:22.440> investors<00:13:22.980> so<00:13:23.459> there's<00:13:23.700> actually 00:13:23.870 --> 00:13:23.880 align:start position:0% we have investors so there's actually 00:13:23.880 --> 00:13:26.810 align:start position:0% we have investors so there's actually many<00:13:24.120> players<00:13:24.600> that<00:13:24.779> contribute<00:13:25.380> to<00:13:25.740> the<00:13:26.339> uh 00:13:26.810 --> 00:13:26.820 align:start position:0% many players that contribute to the uh 00:13:26.820 --> 00:13:29.810 align:start position:0% many players that contribute to the uh staking<00:13:27.360> landscape 00:13:29.810 --> 00:13:29.820 align:start position:0% staking landscape 00:13:29.820 --> 00:13:31.850 align:start position:0% staking landscape um so<00:13:30.120> today<00:13:30.480> uh<00:13:31.079> for<00:13:31.260> the<00:13:31.440> rest<00:13:31.560> of<00:13:31.740> this 00:13:31.850 --> 00:13:31.860 align:start position:0% um so today uh for the rest of this 00:13:31.860 --> 00:13:33.590 align:start position:0% um so today uh for the rest of this presentation<00:13:32.399> before<00:13:32.760> we<00:13:33.000> get<00:13:33.120> into<00:13:33.240> the<00:13:33.420> no 00:13:33.590 --> 00:13:33.600 align:start position:0% presentation before we get into the no 00:13:33.600 --> 00:13:35.389 align:start position:0% presentation before we get into the no running<00:13:33.839> options<00:13:34.200> we're<00:13:34.800> going<00:13:34.980> to<00:13:35.100> look<00:13:35.220> at 00:13:35.389 --> 00:13:35.399 align:start position:0% running options we're going to look at 00:13:35.399 --> 00:13:37.009 align:start position:0% running options we're going to look at the<00:13:35.760> decentralization<00:13:36.300> of<00:13:36.720> the<00:13:36.899> different 00:13:37.009 --> 00:13:37.019 align:start position:0% the decentralization of the different 00:13:37.019 --> 00:13:40.250 align:start position:0% the decentralization of the different layers<00:13:37.500> of<00:13:37.680> the<00:13:37.980> node<00:13:38.160> landscape<00:13:38.760> so<00:13:39.660> hosting 00:13:40.250 --> 00:13:40.260 align:start position:0% layers of the node landscape so hosting 00:13:40.260 --> 00:13:43.550 align:start position:0% layers of the node landscape so hosting providers<00:13:40.740> uh<00:13:41.459> 65<00:13:41.940> of<00:13:42.540> ethereum<00:13:43.019> notes<00:13:43.440> are 00:13:43.550 --> 00:13:43.560 align:start position:0% providers uh 65 of ethereum notes are 00:13:43.560 --> 00:13:49.210 align:start position:0% providers uh 65 of ethereum notes are hosted<00:13:43.920> on<00:13:44.100> centralized<00:13:44.880> services 00:13:49.210 --> 00:13:49.220 align:start position:0% 00:13:49.220 --> 00:13:52.009 align:start position:0% so<00:13:50.220> you<00:13:50.459> know<00:13:50.519> the<00:13:50.700> different<00:13:50.940> rules<00:13:51.420> and<00:13:51.720> how 00:13:52.009 --> 00:13:52.019 align:start position:0% so you know the different rules and how 00:13:52.019 --> 00:13:53.230 align:start position:0% so you know the different rules and how much 00:13:53.230 --> 00:13:53.240 align:start position:0% much 00:13:53.240 --> 00:13:56.150 align:start position:0% much dominance<00:13:54.240> they<00:13:54.480> have<00:13:54.660> a<00:13:55.200> lot<00:13:55.560> of<00:13:55.740> coinbase 00:13:56.150 --> 00:13:56.160 align:start position:0% dominance they have a lot of coinbase 00:13:56.160 --> 00:14:00.170 align:start position:0% dominance they have a lot of coinbase cracking<00:13:56.639> binance<00:13:57.660> Etc<00:13:57.860> uh<00:13:58.860> no<00:13:59.040> client<00:13:59.519> uh 00:14:00.170 --> 00:14:00.180 align:start position:0% cracking binance Etc uh no client uh 00:14:00.180 --> 00:14:02.509 align:start position:0% cracking binance Etc uh no client uh diversity<00:14:00.839> so<00:14:01.320> it's<00:14:01.560> really<00:14:01.800> important<00:14:02.160> that 00:14:02.509 --> 00:14:02.519 align:start position:0% diversity so it's really important that 00:14:02.519 --> 00:14:03.889 align:start position:0% diversity so it's really important that we're<00:14:02.700> not<00:14:02.880> all<00:14:03.000> running<00:14:03.240> the<00:14:03.480> same<00:14:03.600> no 00:14:03.889 --> 00:14:03.899 align:start position:0% we're not all running the same no 00:14:03.899 --> 00:14:06.590 align:start position:0% we're not all running the same no clients<00:14:04.320> so<00:14:04.500> we're<00:14:04.620> going<00:14:04.740> to<00:14:04.860> examine<00:14:05.279> that 00:14:06.590 --> 00:14:06.600 align:start position:0% clients so we're going to examine that 00:14:06.600 --> 00:14:08.690 align:start position:0% clients so we're going to examine that and<00:14:07.139> then<00:14:07.380> Geographic<00:14:07.980> no<00:14:08.220> distribution 00:14:08.690 --> 00:14:08.700 align:start position:0% and then Geographic no distribution 00:14:08.700 --> 00:14:10.250 align:start position:0% and then Geographic no distribution right<00:14:09.120> we<00:14:09.300> don't<00:14:09.480> want<00:14:09.660> to<00:14:09.779> all<00:14:09.839> be<00:14:10.019> running 00:14:10.250 --> 00:14:10.260 align:start position:0% right we don't want to all be running 00:14:10.260 --> 00:14:12.949 align:start position:0% right we don't want to all be running our<00:14:10.920> nodes<00:14:11.220> out<00:14:11.519> of<00:14:11.700> the<00:14:11.820> U.S<00:14:12.240> Virginia<00:14:12.480> East 00:14:12.949 --> 00:14:12.959 align:start position:0% our nodes out of the U.S Virginia East 00:14:12.959 --> 00:14:15.710 align:start position:0% our nodes out of the U.S Virginia East the<00:14:13.440> big<00:14:13.560> amazon<00:14:13.860> Data<00:14:14.399> Center 00:14:15.710 --> 00:14:15.720 align:start position:0% the big amazon Data Center 00:14:15.720 --> 00:14:17.509 align:start position:0% the big amazon Data Center and<00:14:16.139> then<00:14:16.320> coin<00:14:16.740> ownership<00:14:16.980> distribution 00:14:17.509 --> 00:14:17.519 align:start position:0% and then coin ownership distribution 00:14:17.519 --> 00:14:20.449 align:start position:0% and then coin ownership distribution right<00:14:17.820> so<00:14:18.180> uh<00:14:18.839> depending<00:14:19.260> on<00:14:19.320> how<00:14:19.740> much<00:14:19.860> uh<00:14:20.220> you 00:14:20.449 --> 00:14:20.459 align:start position:0% right so uh depending on how much uh you 00:14:20.459 --> 00:14:22.490 align:start position:0% right so uh depending on how much uh you know<00:14:20.579> power<00:14:21.120> and<00:14:21.360> staked<00:14:21.779> Capital<00:14:21.959> you<00:14:22.320> have 00:14:22.490 --> 00:14:22.500 align:start position:0% know power and staked Capital you have 00:14:22.500 --> 00:14:24.230 align:start position:0% know power and staked Capital you have on<00:14:22.680> the<00:14:22.860> network<00:14:23.040> especially<00:14:23.579> these<00:14:23.820> schools 00:14:24.230 --> 00:14:24.240 align:start position:0% on the network especially these schools 00:14:24.240 --> 00:14:25.910 align:start position:0% on the network especially these schools you're<00:14:24.660> going<00:14:24.779> to<00:14:24.899> have<00:14:25.019> more<00:14:25.200> coins<00:14:25.620> and<00:14:25.740> more 00:14:25.910 --> 00:14:25.920 align:start position:0% you're going to have more coins and more 00:14:25.920 --> 00:14:28.430 align:start position:0% you're going to have more coins and more rewards<00:14:26.339> and<00:14:27.120> uh<00:14:27.360> you<00:14:27.660> know<00:14:27.720> more<00:14:27.899> potential 00:14:28.430 --> 00:14:28.440 align:start position:0% rewards and uh you know more potential 00:14:28.440 --> 00:14:29.629 align:start position:0% rewards and uh you know more potential political<00:14:28.800> say 00:14:29.629 --> 00:14:29.639 align:start position:0% political say 00:14:29.639 --> 00:14:31.910 align:start position:0% political say so<00:14:29.959> first<00:14:30.959> we're<00:14:31.200> going<00:14:31.320> to<00:14:31.380> look<00:14:31.500> at<00:14:31.620> the<00:14:31.680> new 00:14:31.910 --> 00:14:31.920 align:start position:0% so first we're going to look at the new 00:14:31.920 --> 00:14:33.590 align:start position:0% so first we're going to look at the new distribution<00:14:32.399> so<00:14:32.760> this<00:14:32.940> doesn't<00:14:33.120> break<00:14:33.420> down 00:14:33.590 --> 00:14:33.600 align:start position:0% distribution so this doesn't break down 00:14:33.600 --> 00:14:36.650 align:start position:0% distribution so this doesn't break down by<00:14:33.779> hosting<00:14:34.200> providers<00:14:34.680> but<00:14:35.459> you<00:14:35.639> can<00:14:35.760> see<00:14:36.000> uh 00:14:36.650 --> 00:14:36.660 align:start position:0% by hosting providers but you can see uh 00:14:36.660 --> 00:14:40.069 align:start position:0% by hosting providers but you can see uh hosting<00:14:37.079> is<00:14:37.740> 63.9 00:14:40.069 --> 00:14:40.079 align:start position:0% hosting is 63.9 00:14:40.079 --> 00:14:42.170 align:start position:0% hosting is 63.9 um<00:14:40.199> this<00:14:40.320> is<00:14:40.500> taken<00:14:40.800> from<00:14:41.120> ethernet.org<00:14:42.120> you 00:14:42.170 --> 00:14:42.180 align:start position:0% um this is taken from ethernet.org you 00:14:42.180 --> 00:14:43.550 align:start position:0% um this is taken from ethernet.org you can<00:14:42.360> go<00:14:42.540> there<00:14:42.660> right<00:14:42.899> now<00:14:43.019> and<00:14:43.199> you<00:14:43.320> can<00:14:43.440> look 00:14:43.550 --> 00:14:43.560 align:start position:0% can go there right now and you can look 00:14:43.560 --> 00:14:46.550 align:start position:0% can go there right now and you can look up<00:14:43.680> these<00:14:43.860> charts<00:14:44.160> in<00:14:44.220> real<00:14:44.399> time<00:14:44.699> and<00:14:45.600> so<00:14:45.839> uh 00:14:46.550 --> 00:14:46.560 align:start position:0% up these charts in real time and so uh 00:14:46.560 --> 00:14:48.470 align:start position:0% up these charts in real time and so uh right<00:14:46.920> now<00:14:47.040> most<00:14:47.459> people<00:14:47.639> aren't<00:14:48.060> solo 00:14:48.470 --> 00:14:48.480 align:start position:0% right now most people aren't solo 00:14:48.480 --> 00:14:50.449 align:start position:0% right now most people aren't solo speaking<00:14:48.839> most<00:14:49.380> people<00:14:49.560> are<00:14:49.800> speaking<00:14:50.279> with 00:14:50.449 --> 00:14:50.459 align:start position:0% speaking most people are speaking with 00:14:50.459 --> 00:14:52.550 align:start position:0% speaking most people are speaking with some<00:14:50.639> type<00:14:50.880> of<00:14:51.060> Provider<00:14:51.480> that's<00:14:52.079> sticking 00:14:52.550 --> 00:14:52.560 align:start position:0% some type of Provider that's sticking 00:14:52.560 --> 00:14:55.370 align:start position:0% some type of Provider that's sticking with<00:14:52.740> a<00:14:53.100> hosting<00:14:53.579> provider 00:14:55.370 --> 00:14:55.380 align:start position:0% with a hosting provider 00:14:55.380 --> 00:16:06.000 align:start position:0% with a hosting provider itself 00:16:06.000 --> 00:16:06.010 align:start position:0% 00:16:06.010 --> 00:16:09.069 align:start position:0% [Music] 00:16:09.069 --> 00:16:09.079 align:start position:0% [Music] 00:16:09.079 --> 00:16:11.030 align:start position:0% [Music] and<00:16:10.079> you<00:16:10.320> know 00:16:11.030 --> 00:16:11.040 align:start position:0% and you know 00:16:11.040 --> 00:16:13.310 align:start position:0% and you know um that<00:16:11.399> has<00:16:11.519> many<00:16:11.760> other<00:16:12.000> implications 00:16:13.310 --> 00:16:13.320 align:start position:0% um that has many other implications 00:16:13.320 --> 00:16:16.730 align:start position:0% um that has many other implications oh<00:16:13.800> I<00:16:14.100> went<00:16:14.339> back 00:16:16.730 --> 00:16:16.740 align:start position:0% 00:16:16.740 --> 00:16:20.449 align:start position:0% and<00:16:17.220> so<00:16:17.519> uh<00:16:18.360> in<00:16:18.540> September<00:16:19.019> uh<00:16:19.560> you<00:16:19.740> know<00:16:19.800> 13.5 00:16:20.449 --> 00:16:20.459 align:start position:0% and so uh in September uh you know 13.5 00:16:20.459 --> 00:16:23.810 align:start position:0% and so uh in September uh you know 13.5 million<00:16:21.000> East<00:16:21.300> uh<00:16:22.079> we're<00:16:22.260> staked<00:16:22.740> so<00:16:23.220> a<00:16:23.519> lot<00:16:23.699> of 00:16:23.810 --> 00:16:23.820 align:start position:0% million East uh we're staked so a lot of 00:16:23.820 --> 00:16:26.090 align:start position:0% million East uh we're staked so a lot of money<00:16:24.060> and<00:16:24.480> more<00:16:24.779> than<00:16:24.959> 60<00:16:25.139> of<00:16:25.620> the<00:16:25.680> youth<00:16:25.980> was 00:16:26.090 --> 00:16:26.100 align:start position:0% money and more than 60 of the youth was 00:16:26.100 --> 00:16:28.129 align:start position:0% money and more than 60 of the youth was sitting<00:16:26.339> with<00:16:26.519> Lido<00:16:27.000> coinbase<00:16:27.480> Kraken<00:16:27.959> and 00:16:28.129 --> 00:16:28.139 align:start position:0% sitting with Lido coinbase Kraken and 00:16:28.139 --> 00:16:31.550 align:start position:0% sitting with Lido coinbase Kraken and finance<00:16:29.040> uh<00:16:29.639> so<00:16:30.000> all<00:16:30.480> of<00:16:30.660> these<00:16:30.839> entities<00:16:31.139> have 00:16:31.550 --> 00:16:31.560 align:start position:0% finance uh so all of these entities have 00:16:31.560 --> 00:16:33.910 align:start position:0% finance uh so all of these entities have a<00:16:31.800> much<00:16:31.980> higher<00:16:32.459> likelihood<00:16:32.940> of<00:16:33.540> being 00:16:33.910 --> 00:16:33.920 align:start position:0% a much higher likelihood of being 00:16:33.920 --> 00:16:35.930 align:start position:0% a much higher likelihood of being assigned<00:16:34.920> to<00:16:34.980> produce<00:16:35.279> blocks<00:16:35.820> of 00:16:35.930 --> 00:16:35.940 align:start position:0% assigned to produce blocks of 00:16:35.940 --> 00:16:37.670 align:start position:0% assigned to produce blocks of transactions<00:16:36.540> because<00:16:37.019> they<00:16:37.259> have<00:16:37.440> more 00:16:37.670 --> 00:16:37.680 align:start position:0% transactions because they have more 00:16:37.680 --> 00:16:39.590 align:start position:0% transactions because they have more stake<00:16:38.100> teeth 00:16:39.590 --> 00:16:39.600 align:start position:0% stake teeth 00:16:39.600 --> 00:16:41.449 align:start position:0% stake teeth and<00:16:40.019> so<00:16:40.199> some<00:16:40.440> of<00:16:40.560> the<00:16:40.680> concerns<00:16:41.100> that<00:16:41.339> were 00:16:41.449 --> 00:16:41.459 align:start position:0% and so some of the concerns that were 00:16:41.459 --> 00:16:42.949 align:start position:0% and so some of the concerns that were brought<00:16:41.639> up<00:16:41.820> when<00:16:42.000> this<00:16:42.180> happened<00:16:42.360> or<00:16:42.720> when 00:16:42.949 --> 00:16:42.959 align:start position:0% brought up when this happened or when 00:16:42.959 --> 00:16:45.290 align:start position:0% brought up when this happened or when this<00:16:43.139> was<00:16:43.320> realized<00:16:43.800> as<00:16:44.759> um<00:16:44.759> obviously 00:16:45.290 --> 00:16:45.300 align:start position:0% this was realized as um obviously 00:16:45.300 --> 00:16:46.850 align:start position:0% this was realized as um obviously they're<00:16:45.480> getting<00:16:45.720> more<00:16:45.959> of<00:16:46.199> the<00:16:46.380> rewards 00:16:46.850 --> 00:16:46.860 align:start position:0% they're getting more of the rewards 00:16:46.860 --> 00:16:48.350 align:start position:0% they're getting more of the rewards they're<00:16:47.100> earning<00:16:47.519> most<00:16:47.639> of<00:16:47.759> the<00:16:47.880> money<00:16:48.060> coming 00:16:48.350 --> 00:16:48.360 align:start position:0% they're earning most of the money coming 00:16:48.360 --> 00:16:50.269 align:start position:0% they're earning most of the money coming from<00:16:48.600> the<00:16:48.779> network 00:16:50.269 --> 00:16:50.279 align:start position:0% from the network 00:16:50.279 --> 00:16:52.430 align:start position:0% from the network uh<00:16:50.880> and<00:16:51.060> there's<00:16:51.360> a<00:16:51.660> lot<00:16:51.779> of<00:16:51.899> discussion 00:16:52.430 --> 00:16:52.440 align:start position:0% uh and there's a lot of discussion 00:16:52.440 --> 00:16:54.290 align:start position:0% uh and there's a lot of discussion around<00:16:52.680> censoring<00:16:53.339> transactions<00:16:53.880> around<00:16:54.060> the 00:16:54.290 --> 00:16:54.300 align:start position:0% around censoring transactions around the 00:16:54.300 --> 00:16:57.850 align:start position:0% around censoring transactions around the network<00:16:54.480> a<00:16:54.839> lot<00:16:54.959> of<00:16:55.079> them<00:16:55.139> use<00:16:55.380> IBD<00:16:56.040> boost 00:16:57.850 --> 00:16:57.860 align:start position:0% network a lot of them use IBD boost 00:16:57.860 --> 00:17:01.129 align:start position:0% network a lot of them use IBD boost of<00:16:58.860> sanctions<00:16:59.399> and<00:16:59.579> tornado<00:17:00.000> cash 00:17:01.129 --> 00:17:01.139 align:start position:0% of sanctions and tornado cash 00:17:01.139 --> 00:17:02.569 align:start position:0% of sanctions and tornado cash um<00:17:01.199> these<00:17:01.620> uh 00:17:02.569 --> 00:17:02.579 align:start position:0% um these uh 00:17:02.579 --> 00:17:15.829 align:start position:0% um these uh Network 00:17:15.829 --> 00:17:15.839 align:start position:0% 00:17:15.839 --> 00:17:18.169 align:start position:0% and<00:17:16.439> so<00:17:16.620> uh<00:17:17.160> more<00:17:17.400> importantly<00:17:17.699> this<00:17:18.059> is 00:17:18.169 --> 00:17:18.179 align:start position:0% and so uh more importantly this is 00:17:18.179 --> 00:17:19.789 align:start position:0% and so uh more importantly this is happening<00:17:18.540> right<00:17:18.780> now<00:17:18.959> you<00:17:19.260> can<00:17:19.439> see<00:17:19.620> what's 00:17:19.789 --> 00:17:19.799 align:start position:0% happening right now you can see what's 00:17:19.799 --> 00:17:22.069 align:start position:0% happening right now you can see what's going<00:17:20.040> on<00:17:20.160> between<00:17:20.459> Lego<00:17:20.819> and<00:17:21.120> others<00:17:21.480> is<00:17:21.900> that 00:17:22.069 --> 00:17:22.079 align:start position:0% going on between Lego and others is that 00:17:22.079 --> 00:17:23.449 align:start position:0% going on between Lego and others is that they're<00:17:22.260> defining<00:17:22.679> the<00:17:22.799> rules<00:17:22.980> of<00:17:23.160> law 00:17:23.449 --> 00:17:23.459 align:start position:0% they're defining the rules of law 00:17:23.459 --> 00:17:25.370 align:start position:0% they're defining the rules of law formation<00:17:23.880> and<00:17:24.299> what<00:17:24.540> type<00:17:24.720> of<00:17:24.839> blocks<00:17:25.260> get 00:17:25.370 --> 00:17:25.380 align:start position:0% formation and what type of blocks get 00:17:25.380 --> 00:17:27.590 align:start position:0% formation and what type of blocks get created<00:17:25.799> once<00:17:26.640> again<00:17:26.699> so<00:17:27.000> they<00:17:27.179> can<00:17:27.299> say<00:17:27.419> like 00:17:27.590 --> 00:17:27.600 align:start position:0% created once again so they can say like 00:17:27.600 --> 00:17:29.030 align:start position:0% created once again so they can say like these<00:17:27.900> type<00:17:28.020> of<00:17:28.140> transactions<00:17:28.679> can<00:17:28.860> be 00:17:29.030 --> 00:17:29.040 align:start position:0% these type of transactions can be 00:17:29.040 --> 00:17:30.950 align:start position:0% these type of transactions can be included<00:17:29.340> in<00:17:29.460> blocks<00:17:29.880> of<00:17:30.419> these<00:17:30.720> types<00:17:30.900> of 00:17:30.950 --> 00:17:30.960 align:start position:0% included in blocks of these types of 00:17:30.960 --> 00:17:32.450 align:start position:0% included in blocks of these types of transactions<00:17:31.500> should<00:17:31.679> not<00:17:31.860> be<00:17:31.980> included<00:17:32.280> in 00:17:32.450 --> 00:17:32.460 align:start position:0% transactions should not be included in 00:17:32.460 --> 00:17:34.010 align:start position:0% transactions should not be included in blocks<00:17:32.820> so<00:17:33.179> they're<00:17:33.360> gonna<00:17:33.480> be<00:17:33.540> able<00:17:33.660> to<00:17:33.780> set 00:17:34.010 --> 00:17:34.020 align:start position:0% blocks so they're gonna be able to set 00:17:34.020 --> 00:17:37.310 align:start position:0% blocks so they're gonna be able to set the<00:17:34.440> rules<00:17:35.340> of<00:17:35.640> how<00:17:35.880> things<00:17:36.059> work<00:17:36.360> in<00:17:36.780> a<00:17:37.020> theory 00:17:37.310 --> 00:17:37.320 align:start position:0% the rules of how things work in a theory 00:17:37.320 --> 00:17:40.370 align:start position:0% the rules of how things work in a theory improved<00:17:37.740> stake<00:17:38.039> and<00:17:38.640> then<00:17:38.880> others<00:17:39.419> entities 00:17:40.370 --> 00:17:40.380 align:start position:0% improved stake and then others entities 00:17:40.380 --> 00:17:41.930 align:start position:0% improved stake and then others entities that<00:17:40.740> they<00:17:40.860> don't<00:17:40.919> follow<00:17:41.100> these<00:17:41.400> rules<00:17:41.640> could 00:17:41.930 --> 00:17:41.940 align:start position:0% that they don't follow these rules could 00:17:41.940 --> 00:17:44.630 align:start position:0% that they don't follow these rules could be<00:17:42.120> penalized<00:17:42.840> so<00:17:43.620> it's<00:17:44.100> really<00:17:44.280> important 00:17:44.630 --> 00:17:44.640 align:start position:0% be penalized so it's really important 00:17:44.640 --> 00:17:47.510 align:start position:0% be penalized so it's really important that<00:17:44.940> not<00:17:45.120> you<00:17:45.360> know<00:17:45.539> one<00:17:46.260> group<00:17:46.500> of<00:17:47.039> uh 00:17:47.510 --> 00:17:47.520 align:start position:0% that not you know one group of uh 00:17:47.520 --> 00:17:51.770 align:start position:0% that not you know one group of uh entities<00:17:48.080> uh<00:17:49.100> producing<00:17:50.100> blocks<00:17:50.520> uh<00:17:51.240> are 00:17:51.770 --> 00:17:51.780 align:start position:0% entities uh producing blocks uh are 00:17:51.780 --> 00:17:53.450 align:start position:0% entities uh producing blocks uh are creating<00:17:52.559> the<00:17:52.740> rules<00:17:52.919> for<00:17:53.160> the<00:17:53.280> entire 00:17:53.450 --> 00:17:53.460 align:start position:0% creating the rules for the entire 00:17:53.460 --> 00:18:15.610 align:start position:0% creating the rules for the entire network 00:18:15.610 --> 00:18:15.620 align:start position:0% 00:18:15.620 --> 00:18:19.669 align:start position:0% are<00:18:16.620> producing<00:18:17.100> all<00:18:17.340> the<00:18:17.460> blocks 00:18:19.669 --> 00:18:19.679 align:start position:0% are producing all the blocks 00:18:19.679 --> 00:18:23.090 align:start position:0% are producing all the blocks and<00:18:20.340> so<00:18:21.000> um<00:18:21.000> another<00:18:21.360> uh<00:18:22.200> type<00:18:22.500> of<00:18:22.799> you<00:18:23.039> know 00:18:23.090 --> 00:18:23.100 align:start position:0% and so um another uh type of you know 00:18:23.100 --> 00:18:24.950 align:start position:0% and so um another uh type of you know decentralization<00:18:23.760> or<00:18:24.360> in<00:18:24.600> this<00:18:24.780> case 00:18:24.950 --> 00:18:24.960 align:start position:0% decentralization or in this case 00:18:24.960 --> 00:18:28.090 align:start position:0% decentralization or in this case diversity<00:18:25.559> that's<00:18:26.220> really<00:18:26.520> important 00:18:28.090 --> 00:18:28.100 align:start position:0% diversity that's really important 00:18:28.100 --> 00:18:31.190 align:start position:0% diversity that's really important diversity<00:18:29.100> and<00:18:29.820> so<00:18:30.059> right<00:18:30.539> now<00:18:30.720> you<00:18:30.900> can<00:18:31.020> see 00:18:31.190 --> 00:18:31.200 align:start position:0% diversity and so right now you can see 00:18:31.200 --> 00:18:35.990 align:start position:0% diversity and so right now you can see death<00:18:31.559> is<00:18:31.740> 77<00:18:32.299> of<00:18:33.299> the<00:18:33.720> uh<00:18:34.679> consensus<00:18:35.460> clients 00:18:35.990 --> 00:18:36.000 align:start position:0% death is 77 of the uh consensus clients 00:18:36.000 --> 00:18:38.930 align:start position:0% death is 77 of the uh consensus clients so<00:18:36.240> what<00:18:36.480> people<00:18:36.720> are<00:18:36.960> writing<00:18:37.440> and<00:18:38.160> so<00:18:38.400> once 00:18:38.930 --> 00:18:38.940 align:start position:0% so what people are writing and so once 00:18:38.940 --> 00:18:41.150 align:start position:0% so what people are writing and so once again<00:18:39.000> Peter<00:18:39.480> he's<00:18:39.960> another<00:18:40.260> good<00:18:40.620> person<00:18:40.919> to 00:18:41.150 --> 00:18:41.160 align:start position:0% again Peter he's another good person to 00:18:41.160 --> 00:18:42.529 align:start position:0% again Peter he's another good person to follow<00:18:41.340> if<00:18:41.580> you're<00:18:41.760> more<00:18:42.059> curious<00:18:42.419> about 00:18:42.529 --> 00:18:42.539 align:start position:0% follow if you're more curious about 00:18:42.539 --> 00:18:43.909 align:start position:0% follow if you're more curious about what's<00:18:42.780> happening 00:18:43.909 --> 00:18:43.919 align:start position:0% what's happening 00:18:43.919 --> 00:18:46.909 align:start position:0% what's happening um<00:18:44.039> you<00:18:44.340> know<00:18:44.400> it<00:18:45.240> is<00:18:45.360> uh<00:18:45.900> similar<00:18:46.320> to<00:18:46.559> all<00:18:46.799> the 00:18:46.909 --> 00:18:46.919 align:start position:0% um you know it is uh similar to all the 00:18:46.919 --> 00:18:48.890 align:start position:0% um you know it is uh similar to all the nodes<00:18:47.220> are<00:18:47.460> being<00:18:47.640> hosted<00:18:48.120> in<00:18:48.240> one<00:18:48.419> place<00:18:48.660> or 00:18:48.890 --> 00:18:48.900 align:start position:0% nodes are being hosted in one place or 00:18:48.900 --> 00:18:51.110 align:start position:0% nodes are being hosted in one place or all<00:18:49.140> there's<00:18:49.380> a<00:18:49.620> lot<00:18:49.679> in<00:18:49.860> a<00:18:50.039> pool<00:18:50.160> if<00:18:50.820> something 00:18:51.110 --> 00:18:51.120 align:start position:0% all there's a lot in a pool if something 00:18:51.120 --> 00:18:53.890 align:start position:0% all there's a lot in a pool if something happens 00:18:53.890 --> 00:18:53.900 align:start position:0% 00:18:53.900 --> 00:18:56.690 align:start position:0% to<00:18:54.900> be<00:18:54.960> running<00:18:55.140> that<00:18:55.500> same<00:18:55.679> consensus<00:18:56.220> client 00:18:56.690 --> 00:18:56.700 align:start position:0% to be running that same consensus client 00:18:56.700 --> 00:18:58.250 align:start position:0% to be running that same consensus client and<00:18:57.480> so 00:18:58.250 --> 00:18:58.260 align:start position:0% and so 00:18:58.260 --> 00:19:00.350 align:start position:0% and so um<00:18:58.380> you<00:18:58.620> know<00:18:58.679> I<00:18:58.799> read<00:18:58.980> an<00:18:59.160> article<00:18:59.460> that<00:18:59.880> it's 00:19:00.350 --> 00:19:00.360 align:start position:0% um you know I read an article that it's 00:19:00.360 --> 00:19:01.970 align:start position:0% um you know I read an article that it's not<00:19:00.660> great<00:19:00.840> to<00:19:01.020> have<00:19:01.140> one<00:19:01.320> because<00:19:01.559> as<00:19:01.860> a 00:19:01.970 --> 00:19:01.980 align:start position:0% not great to have one because as a 00:19:01.980 --> 00:19:04.310 align:start position:0% not great to have one because as a client<00:19:02.220> it's<00:19:02.460> better<00:19:02.700> to<00:19:02.880> have<00:19:03.120> a<00:19:03.600> majority<00:19:04.020> in 00:19:04.310 --> 00:19:04.320 align:start position:0% client it's better to have a majority in 00:19:04.320 --> 00:19:07.190 align:start position:0% client it's better to have a majority in an<00:19:04.440> ethereum<00:19:04.799> uh<00:19:05.160> purposely<00:19:05.640> oh<00:19:06.480> sorry<00:19:06.840> A 00:19:07.190 --> 00:19:07.200 align:start position:0% an ethereum uh purposely oh sorry A 00:19:07.200 --> 00:19:09.350 align:start position:0% an ethereum uh purposely oh sorry A diversity<00:19:07.740> I've<00:19:08.340> had<00:19:08.580> multiple<00:19:08.820> clients 00:19:09.350 --> 00:19:09.360 align:start position:0% diversity I've had multiple clients 00:19:09.360 --> 00:19:10.730 align:start position:0% diversity I've had multiple clients running<00:19:09.539> but<00:19:09.840> it<00:19:10.020> actually<00:19:10.260> worked<00:19:10.679> at 00:19:10.730 --> 00:19:10.740 align:start position:0% running but it actually worked at 00:19:10.740 --> 00:19:12.289 align:start position:0% running but it actually worked at multiple<00:19:11.100> clients<00:19:11.520> and<00:19:11.700> wanted<00:19:11.940> a<00:19:12.179> super 00:19:12.289 --> 00:19:12.299 align:start position:0% multiple clients and wanted a super 00:19:12.299 --> 00:19:13.909 align:start position:0% multiple clients and wanted a super majority<00:19:12.840> than<00:19:13.260> it<00:19:13.380> is<00:19:13.500> to<00:19:13.679> have<00:19:13.799> one 00:19:13.909 --> 00:19:13.919 align:start position:0% majority than it is to have one 00:19:13.919 --> 00:19:16.130 align:start position:0% majority than it is to have one consensus<00:19:14.460> client<00:19:14.880> so<00:19:15.720> it<00:19:15.900> is<00:19:16.020> something 00:19:16.130 --> 00:19:16.140 align:start position:0% consensus client so it is something 00:19:16.140 --> 00:19:17.810 align:start position:0% consensus client so it is something people<00:19:16.440> are<00:19:16.679> working<00:19:16.919> on<00:19:17.160> and<00:19:17.400> there<00:19:17.700> are 00:19:17.810 --> 00:19:17.820 align:start position:0% people are working on and there are 00:19:17.820 --> 00:19:21.040 align:start position:0% people are working on and there are other<00:19:17.940> clients<00:19:18.480> that<00:19:18.720> you<00:19:18.840> can<00:19:18.960> run 00:19:21.040 --> 00:19:21.050 align:start position:0% other clients that you can run 00:19:21.050 --> 00:19:49.450 align:start position:0% other clients that you can run [Music] 00:19:49.450 --> 00:19:49.460 align:start position:0% 00:19:49.460 --> 00:19:52.070 align:start position:0% the<00:19:50.460> network<00:19:50.580> will<00:19:50.940> start<00:19:51.179> slashing<00:19:51.900> that 00:19:52.070 --> 00:19:52.080 align:start position:0% the network will start slashing that 00:19:52.080 --> 00:20:37.870 align:start position:0% the network will start slashing that group<00:19:52.320> so<00:19:52.679> anybody<00:19:53.160> that's<00:19:53.340> in<00:19:53.580> that<00:19:53.700> group 00:20:37.870 --> 00:20:37.880 align:start position:0% 00:20:37.880 --> 00:20:40.970 align:start position:0% right<00:20:38.880> now<00:20:39.539> uh<00:20:40.080> these<00:20:40.320> nodes<00:20:40.440> will<00:20:40.679> all<00:20:40.799> start 00:20:40.970 --> 00:20:40.980 align:start position:0% right now uh these nodes will all start 00:20:40.980 --> 00:20:42.770 align:start position:0% right now uh these nodes will all start getting<00:20:41.160> flashed<00:20:41.700> until<00:20:41.940> the<00:20:42.120> value<00:20:42.360> is<00:20:42.539> less 00:20:42.770 --> 00:20:42.780 align:start position:0% getting flashed until the value is less 00:20:42.780 --> 00:20:45.230 align:start position:0% getting flashed until the value is less than<00:20:42.900> one-third<00:20:43.500> and<00:20:44.220> so<00:20:44.460> you're<00:20:44.760> going<00:20:45.000> from 00:20:45.230 --> 00:20:45.240 align:start position:0% than one-third and so you're going from 00:20:45.240 --> 00:20:48.950 align:start position:0% than one-third and so you're going from 53<00:20:45.860> below<00:20:46.860> to<00:20:47.100> 32<00:20:47.460> before<00:20:48.059> the<00:20:48.360> slashing<00:20:48.780> would 00:20:48.950 --> 00:20:48.960 align:start position:0% 53 below to 32 before the slashing would 00:20:48.960 --> 00:20:51.770 align:start position:0% 53 below to 32 before the slashing would end<00:20:49.140> so<00:20:49.799> anyone<00:20:50.280> posted<00:20:50.880> on<00:20:51.059> Amazon<00:20:51.299> would 00:20:51.770 --> 00:20:51.780 align:start position:0% end so anyone posted on Amazon would 00:20:51.780 --> 00:20:54.350 align:start position:0% end so anyone posted on Amazon would suffer<00:20:52.260> as<00:20:52.740> a<00:20:52.860> part<00:20:52.980> of<00:20:53.100> that 00:20:54.350 --> 00:20:54.360 align:start position:0% suffer as a part of that 00:20:54.360 --> 00:20:56.690 align:start position:0% suffer as a part of that and<00:20:54.840> so<00:20:55.080> you<00:20:55.440> as<00:20:55.740> an<00:20:55.860> individual<00:20:56.160> don't<00:20:56.460> have 00:20:56.690 --> 00:20:56.700 align:start position:0% and so you as an individual don't have 00:20:56.700 --> 00:20:58.130 align:start position:0% and so you as an individual don't have control<00:20:56.880> because<00:20:57.240> you're<00:20:57.539> a<00:20:57.660> part<00:20:57.780> of<00:20:57.960> this 00:20:58.130 --> 00:20:58.140 align:start position:0% control because you're a part of this 00:20:58.140 --> 00:21:00.409 align:start position:0% control because you're a part of this potential<00:20:58.500> slashing<00:20:59.039> group<00:20:59.220> and<00:20:59.760> also<00:21:00.059> as<00:21:00.240> I 00:21:00.409 --> 00:21:00.419 align:start position:0% potential slashing group and also as I 00:21:00.419 --> 00:21:02.570 align:start position:0% potential slashing group and also as I imagine<00:21:00.539> you<00:21:00.780> may<00:21:00.960> have<00:21:01.080> no<00:21:01.260> idea<00:21:01.500> uh<00:21:02.280> where 00:21:02.570 --> 00:21:02.580 align:start position:0% imagine you may have no idea uh where 00:21:02.580 --> 00:21:04.010 align:start position:0% imagine you may have no idea uh where your<00:21:02.700> nodes<00:21:02.880> are<00:21:03.059> be<00:21:03.240> hosted<00:21:03.600> if<00:21:03.720> you're<00:21:03.900> going 00:21:04.010 --> 00:21:04.020 align:start position:0% your nodes are be hosted if you're going 00:21:04.020 --> 00:21:05.270 align:start position:0% your nodes are be hosted if you're going through<00:21:04.200> some<00:21:04.500> other<00:21:04.740> type<00:21:04.980> of<00:21:05.039> service 00:21:05.270 --> 00:21:05.280 align:start position:0% through some other type of service 00:21:05.280 --> 00:21:33.430 align:start position:0% through some other type of service provider 00:21:33.430 --> 00:21:33.440 align:start position:0% 00:21:33.440 --> 00:21:44.029 align:start position:0% is<00:21:34.440> impacted 00:21:44.029 --> 00:21:44.039 align:start position:0% 00:21:44.039 --> 00:21:47.029 align:start position:0% so<00:21:44.940> whether<00:21:45.600> it's<00:21:45.960> posting<00:21:46.440> whether<00:21:46.860> it's 00:21:47.029 --> 00:21:47.039 align:start position:0% so whether it's posting whether it's 00:21:47.039 --> 00:21:49.010 align:start position:0% so whether it's posting whether it's pool<00:21:47.280> because<00:21:47.580> the<00:21:47.880> pool<00:21:48.120> is<00:21:48.360> hosting<00:21:48.840> there 00:21:49.010 --> 00:21:49.020 align:start position:0% pool because the pool is hosting there 00:21:49.020 --> 00:21:51.110 align:start position:0% pool because the pool is hosting there or<00:21:49.559> the<00:21:49.679> pool<00:21:49.919> in<00:21:50.159> general<00:21:50.400> or<00:21:50.760> whether<00:21:50.940> it's 00:21:51.110 --> 00:21:51.120 align:start position:0% or the pool in general or whether it's 00:21:51.120 --> 00:21:53.750 align:start position:0% or the pool in general or whether it's at<00:21:51.299> the<00:21:51.480> client<00:21:51.659> consensus<00:21:52.200> level 00:21:53.750 --> 00:21:53.760 align:start position:0% at the client consensus level 00:21:53.760 --> 00:21:54.890 align:start position:0% at the client consensus level um<00:21:53.880> there's<00:21:54.179> a<00:21:54.299> lot<00:21:54.419> of<00:21:54.480> risk<00:21:54.780> of 00:21:54.890 --> 00:21:54.900 align:start position:0% um there's a lot of risk of 00:21:54.900 --> 00:21:57.169 align:start position:0% um there's a lot of risk of essentialization<00:21:55.500> and<00:21:56.039> you<00:21:56.340> being<00:21:56.520> penalized 00:21:57.169 --> 00:21:57.179 align:start position:0% essentialization and you being penalized 00:21:57.179 --> 00:21:59.330 align:start position:0% essentialization and you being penalized as<00:21:57.360> a<00:21:57.600> validator 00:21:59.330 --> 00:21:59.340 align:start position:0% as a validator 00:21:59.340 --> 00:22:01.549 align:start position:0% as a validator um<00:21:59.360> what<00:22:00.360> degree<00:22:00.600> does<00:22:00.780> decentralization 00:22:01.549 --> 00:22:01.559 align:start position:0% um what degree does decentralization 00:22:01.559 --> 00:22:03.230 align:start position:0% um what degree does decentralization matter<00:22:01.860> these<00:22:02.280> networks<00:22:02.580> there's<00:22:02.820> like<00:22:03.000> a<00:22:03.179> big 00:22:03.230 --> 00:22:03.240 align:start position:0% matter these networks there's like a big 00:22:03.240 --> 00:22:05.450 align:start position:0% matter these networks there's like a big debate<00:22:03.600> on<00:22:03.780> that<00:22:04.020> and<00:22:04.500> like<00:22:04.799> every<00:22:04.980> blockchain 00:22:05.450 --> 00:22:05.460 align:start position:0% debate on that and like every blockchain 00:22:05.460 --> 00:22:07.850 align:start position:0% debate on that and like every blockchain protocol<00:22:05.820> has<00:22:06.120> their<00:22:06.299> own<00:22:06.480> version<00:22:07.320> of<00:22:07.500> how 00:22:07.850 --> 00:22:07.860 align:start position:0% protocol has their own version of how 00:22:07.860 --> 00:22:10.070 align:start position:0% protocol has their own version of how decentralized<00:22:08.460> they<00:22:08.760> want<00:22:08.940> to<00:22:09.059> be 00:22:10.070 --> 00:22:10.080 align:start position:0% decentralized they want to be 00:22:10.080 --> 00:22:13.149 align:start position:0% decentralized they want to be um<00:22:10.200> and<00:22:10.380> there<00:22:10.799> was<00:22:10.980> a<00:22:11.100> talk<00:22:11.280> uh 00:22:13.149 --> 00:22:13.159 align:start position:0% um and there was a talk uh 00:22:13.159 --> 00:22:16.090 align:start position:0% um and there was a talk uh he<00:22:14.159> was<00:22:14.340> mentioning<00:22:14.640> that<00:22:14.940> is 00:22:16.090 --> 00:22:16.100 align:start position:0% he was mentioning that is 00:22:16.100 --> 00:22:18.770 align:start position:0% he was mentioning that is not<00:22:17.100> works<00:22:17.460> and<00:22:17.820> that<00:22:18.000> there<00:22:18.240> tends<00:22:18.480> to<00:22:18.539> be<00:22:18.659> a 00:22:18.770 --> 00:22:18.780 align:start position:0% not works and that there tends to be a 00:22:18.780 --> 00:22:20.990 align:start position:0% not works and that there tends to be a bit<00:22:18.900> of<00:22:19.020> a<00:22:19.080> tragedy<00:22:19.559> of<00:22:19.740> the<00:22:19.860> commons<00:22:20.220> when<00:22:20.760> it 00:22:20.990 --> 00:22:21.000 align:start position:0% bit of a tragedy of the commons when it 00:22:21.000 --> 00:22:23.029 align:start position:0% bit of a tragedy of the commons when it comes<00:22:21.179> to<00:22:21.299> decentralization<00:22:21.900> or<00:22:22.559> it's<00:22:22.799> like 00:22:23.029 --> 00:22:23.039 align:start position:0% comes to decentralization or it's like 00:22:23.039 --> 00:22:25.970 align:start position:0% comes to decentralization or it's like this<00:22:23.220> uh<00:22:23.880> creeping<00:22:24.720> phenomenon<00:22:25.260> where<00:22:25.740> people 00:22:25.970 --> 00:22:25.980 align:start position:0% this uh creeping phenomenon where people 00:22:25.980 --> 00:22:27.710 align:start position:0% this uh creeping phenomenon where people don't<00:22:26.220> actually<00:22:26.460> care<00:22:26.760> about<00:22:26.940> it<00:22:27.120> until<00:22:27.360> it's 00:22:27.710 --> 00:22:27.720 align:start position:0% don't actually care about it until it's 00:22:27.720 --> 00:22:30.049 align:start position:0% don't actually care about it until it's too<00:22:28.020> late<00:22:28.140> so<00:22:28.620> until<00:22:28.860> this<00:22:29.640> large<00:22:29.880> group 00:22:30.049 --> 00:22:30.059 align:start position:0% too late so until this large group 00:22:30.059 --> 00:22:32.570 align:start position:0% too late so until this large group starts<00:22:30.419> getting<00:22:30.600> slashed<00:22:31.200> so<00:22:31.559> not<00:22:32.280> something 00:22:32.570 --> 00:22:32.580 align:start position:0% starts getting slashed so not something 00:22:32.580 --> 00:22:34.430 align:start position:0% starts getting slashed so not something that<00:22:33.000> matters<00:22:33.299> because<00:22:33.600> the<00:22:33.840> performance<00:22:34.200> of 00:22:34.430 --> 00:22:34.440 align:start position:0% that matters because the performance of 00:22:34.440 --> 00:22:36.770 align:start position:0% that matters because the performance of the<00:22:34.559> network<00:22:34.679> is<00:22:34.980> running<00:22:35.220> fine<00:22:35.580> and<00:22:36.419> most 00:22:36.770 --> 00:22:36.780 align:start position:0% the network is running fine and most 00:22:36.780 --> 00:22:38.690 align:start position:0% the network is running fine and most users<00:22:37.380> probably<00:22:37.679> especially<00:22:38.159> when<00:22:38.340> it's<00:22:38.520> not 00:22:38.690 --> 00:22:38.700 align:start position:0% users probably especially when it's not 00:22:38.700 --> 00:22:41.149 align:start position:0% users probably especially when it's not at<00:22:39.240> a<00:22:39.360> technical<00:22:39.600> developer<00:22:40.200> conference<00:22:40.620> are 00:22:41.149 --> 00:22:41.159 align:start position:0% at a technical developer conference are 00:22:41.159 --> 00:22:42.529 align:start position:0% at a technical developer conference are not<00:22:41.400> that<00:22:41.520> worried<00:22:41.820> about<00:22:41.880> decentralization 00:22:42.529 --> 00:22:42.539 align:start position:0% not that worried about decentralization 00:22:42.539 --> 00:22:44.330 align:start position:0% not that worried about decentralization they're<00:22:43.020> worried<00:22:43.320> about<00:22:43.440> you<00:22:43.919> know<00:22:44.039> being 00:22:44.330 --> 00:22:44.340 align:start position:0% they're worried about you know being 00:22:44.340 --> 00:22:47.149 align:start position:0% they're worried about you know being able<00:22:44.640> to<00:22:44.700> successfully<00:22:45.299> use<00:22:45.539> their<00:22:45.780> app 00:22:47.149 --> 00:22:47.159 align:start position:0% able to successfully use their app 00:22:47.159 --> 00:22:49.310 align:start position:0% able to successfully use their app and<00:22:47.640> write<00:22:47.820> the<00:22:48.000> ethereum<00:22:48.419> network<00:22:48.659> goal<00:22:49.200> is 00:22:49.310 --> 00:22:49.320 align:start position:0% and write the ethereum network goal is 00:22:49.320 --> 00:22:53.029 align:start position:0% and write the ethereum network goal is to<00:22:49.500> be<00:22:49.620> incredibly<00:22:50.100> uh<00:22:51.200> neutral<00:22:52.200> resilient 00:22:53.029 --> 00:22:53.039 align:start position:0% to be incredibly uh neutral resilient 00:22:53.039 --> 00:23:01.750 align:start position:0% to be incredibly uh neutral resilient scalable<00:22:53.460> and<00:22:53.700> global<00:22:54.059> settlement<00:22:54.419> layer 00:23:01.750 --> 00:23:01.760 align:start position:0% 00:23:01.760 --> 00:23:04.909 align:start position:0% earn<00:23:02.760> rewards<00:23:03.179> and<00:23:03.360> avoid<00:23:03.720> penalties 00:23:04.909 --> 00:23:04.919 align:start position:0% earn rewards and avoid penalties 00:23:04.919 --> 00:23:07.430 align:start position:0% earn rewards and avoid penalties and<00:23:05.460> so<00:23:05.640> right<00:23:05.940> as<00:23:06.240> we've<00:23:06.419> been<00:23:06.900> um<00:23:06.900> as<00:23:07.320> I 00:23:07.430 --> 00:23:07.440 align:start position:0% and so right as we've been um as I 00:23:07.440 --> 00:23:08.870 align:start position:0% and so right as we've been um as I mentioned<00:23:07.679> today<00:23:07.919> the<00:23:08.280> ethereum<00:23:08.700> network 00:23:08.870 --> 00:23:08.880 align:start position:0% mentioned today the ethereum network 00:23:08.880 --> 00:23:11.570 align:start position:0% mentioned today the ethereum network actually<00:23:09.299> encourages<00:23:09.780> decentralization<00:23:10.580> uh 00:23:11.570 --> 00:23:11.580 align:start position:0% actually encourages decentralization uh 00:23:11.580 --> 00:23:13.610 align:start position:0% actually encourages decentralization uh less<00:23:11.880> penalties<00:23:12.360> to<00:23:12.539> run<00:23:12.720> your<00:23:12.960> own<00:23:13.080> validator 00:23:13.610 --> 00:23:13.620 align:start position:0% less penalties to run your own validator 00:23:13.620 --> 00:23:15.230 align:start position:0% less penalties to run your own validator note<00:23:13.919> for<00:23:14.220> one<00:23:14.400> of<00:23:14.520> your<00:23:14.580> own<00:23:14.760> individual 00:23:15.230 --> 00:23:15.240 align:start position:0% note for one of your own individual 00:23:15.240 --> 00:23:17.930 align:start position:0% note for one of your own individual client<00:23:15.600> uh<00:23:16.320> for<00:23:16.500> not<00:23:16.620> hosting<00:23:17.159> or<00:23:17.460> going 00:23:17.930 --> 00:23:17.940 align:start position:0% client uh for not hosting or going 00:23:17.940 --> 00:23:20.210 align:start position:0% client uh for not hosting or going through<00:23:18.179> a<00:23:18.360> pool 00:23:20.210 --> 00:23:20.220 align:start position:0% through a pool 00:23:20.220 --> 00:23:22.850 align:start position:0% through a pool in<00:23:20.580> general<00:23:21.299> um<00:23:21.299> the<00:23:21.539> ethereum<00:23:22.020> community<00:23:22.380> is 00:23:22.850 --> 00:23:22.860 align:start position:0% in general um the ethereum community is 00:23:22.860 --> 00:23:25.130 align:start position:0% in general um the ethereum community is working<00:23:23.220> uh<00:23:23.820> across<00:23:24.240> all<00:23:24.480> these<00:23:24.659> points<00:23:24.960> of 00:23:25.130 --> 00:23:25.140 align:start position:0% working uh across all these points of 00:23:25.140 --> 00:23:27.409 align:start position:0% working uh across all these points of centralization<00:23:25.799> uh<00:23:26.700> two<00:23:26.940> ways<00:23:27.299> to 00:23:27.409 --> 00:23:27.419 align:start position:0% centralization uh two ways to 00:23:27.419 --> 00:23:29.930 align:start position:0% centralization uh two ways to decentralize<00:23:28.200> these<00:23:28.740> uh<00:23:29.100> different<00:23:29.340> aspects 00:23:29.930 --> 00:23:29.940 align:start position:0% decentralize these uh different aspects 00:23:29.940 --> 00:23:32.330 align:start position:0% decentralize these uh different aspects so<00:23:30.600> the<00:23:30.840> node<00:23:31.140> infrastructure<00:23:31.679> layer<00:23:32.039> the 00:23:32.330 --> 00:23:32.340 align:start position:0% so the node infrastructure layer the 00:23:32.340 --> 00:23:35.330 align:start position:0% so the node infrastructure layer the pools<00:23:32.940> the<00:23:33.539> client<00:23:33.780> diversity<00:23:34.440> uh<00:23:35.159> the 00:23:35.330 --> 00:23:35.340 align:start position:0% pools the client diversity uh the 00:23:35.340 --> 00:23:37.549 align:start position:0% pools the client diversity uh the geographic<00:23:35.820> distribution<00:23:36.320> and<00:23:37.320> block 00:23:37.549 --> 00:23:37.559 align:start position:0% geographic distribution and block 00:23:37.559 --> 00:23:40.310 align:start position:0% geographic distribution and block construction<00:23:37.980> so<00:23:38.880> these<00:23:39.659> are<00:23:39.720> things<00:23:39.960> and 00:23:40.310 --> 00:23:40.320 align:start position:0% construction so these are things and 00:23:40.320 --> 00:23:42.770 align:start position:0% construction so these are things and coin<00:23:40.620> distribution<00:23:40.919> uh<00:23:41.820> this<00:23:42.120> is<00:23:42.299> not<00:23:42.480> a 00:23:42.770 --> 00:23:42.780 align:start position:0% coin distribution uh this is not a 00:23:42.780 --> 00:23:43.810 align:start position:0% coin distribution uh this is not a presentation 00:23:43.810 --> 00:23:43.820 align:start position:0% presentation 00:23:43.820 --> 00:23:46.370 align:start position:0% presentation ecosystem<00:23:44.820> is<00:23:45.120> like<00:23:45.480> for<00:23:45.960> the<00:23:46.080> first<00:23:46.200> time 00:23:46.370 --> 00:23:46.380 align:start position:0% ecosystem is like for the first time 00:23:46.380 --> 00:23:48.289 align:start position:0% ecosystem is like for the first time hearing<00:23:46.799> the<00:23:47.220> very<00:23:47.400> aware<00:23:47.760> of<00:23:47.940> all<00:23:48.059> these 00:23:48.289 --> 00:23:48.299 align:start position:0% hearing the very aware of all these 00:23:48.299 --> 00:23:51.169 align:start position:0% hearing the very aware of all these things<00:23:48.419> and<00:23:48.840> working<00:23:49.140> uh<00:23:49.860> very<00:23:50.100> hard<00:23:50.340> to 00:23:51.169 --> 00:23:51.179 align:start position:0% things and working uh very hard to 00:23:51.179 --> 00:23:52.850 align:start position:0% things and working uh very hard to improve<00:23:51.419> the<00:23:51.539> resilience<00:23:51.900> to<00:23:52.260> sexualization 00:23:52.850 --> 00:23:52.860 align:start position:0% improve the resilience to sexualization 00:23:52.860 --> 00:23:55.310 align:start position:0% improve the resilience to sexualization and<00:23:53.820> uh<00:23:54.059> even<00:23:54.240> the<00:23:54.480> different<00:23:54.600> safety 00:23:55.310 --> 00:23:55.320 align:start position:0% and uh even the different safety 00:23:55.320 --> 00:23:56.810 align:start position:0% and uh even the different safety providers<00:23:55.679> are<00:23:55.860> trying<00:23:56.100> to<00:23:56.280> you<00:23:56.760> know 00:23:56.810 --> 00:23:56.820 align:start position:0% providers are trying to you know 00:23:56.820 --> 00:24:00.110 align:start position:0% providers are trying to you know distribute<00:23:57.360> where<00:23:57.720> they<00:23:57.900> uh<00:23:58.260> run<00:23:58.500> their<00:23:58.740> notes 00:24:00.110 --> 00:24:00.120 align:start position:0% distribute where they uh run their notes 00:24:00.120 --> 00:24:08.210 align:start position:0% distribute where they uh run their notes options 00:24:08.210 --> 00:24:08.220 align:start position:0% 00:24:08.220 --> 00:24:10.549 align:start position:0% right 00:24:10.549 --> 00:24:10.559 align:start position:0% right 00:24:10.559 --> 00:24:13.549 align:start position:0% right so<00:24:10.919> having<00:24:11.880> an<00:24:12.120> understanding<00:24:12.480> now<00:24:12.720> of<00:24:13.260> kind 00:24:13.549 --> 00:24:13.559 align:start position:0% so having an understanding now of kind 00:24:13.559 --> 00:24:17.090 align:start position:0% so having an understanding now of kind of<00:24:13.679> the<00:24:13.799> the<00:24:14.220> the<00:24:14.600> landscape<00:24:15.600> uh<00:24:16.500> within 00:24:17.090 --> 00:24:17.100 align:start position:0% of the the the landscape uh within 00:24:17.100 --> 00:24:19.549 align:start position:0% of the the the landscape uh within ethereum<00:24:17.580> and<00:24:18.059> the<00:24:18.240> requirements<00:24:18.840> for<00:24:19.320> being 00:24:19.549 --> 00:24:19.559 align:start position:0% ethereum and the requirements for being 00:24:19.559 --> 00:24:22.190 align:start position:0% ethereum and the requirements for being a<00:24:19.740> runner<00:24:20.220> what<00:24:20.640> options<00:24:21.059> are<00:24:21.480> there<00:24:21.600> for 00:24:22.190 --> 00:24:22.200 align:start position:0% a runner what options are there for 00:24:22.200 --> 00:24:24.470 align:start position:0% a runner what options are there for actually<00:24:22.679> running<00:24:23.039> your<00:24:23.340> own<00:24:23.460> notes<00:24:23.880> so 00:24:24.470 --> 00:24:24.480 align:start position:0% actually running your own notes so 00:24:24.480 --> 00:24:27.110 align:start position:0% actually running your own notes so actually<00:24:24.720> let<00:24:25.020> me<00:24:25.140> get<00:24:25.380> the<00:24:25.500> clicker<00:24:25.860> from<00:24:25.980> you 00:24:27.110 --> 00:24:27.120 align:start position:0% actually let me get the clicker from you 00:24:27.120 --> 00:24:30.409 align:start position:0% actually let me get the clicker from you okay 00:24:30.409 --> 00:24:30.419 align:start position:0% 00:24:30.419 --> 00:24:46.990 align:start position:0% oh<00:24:31.080> uh<00:24:31.620> let's<00:24:31.740> see<00:24:31.919> here 00:24:46.990 --> 00:24:47.000 align:start position:0% 00:24:47.000 --> 00:24:49.549 align:start position:0% Administration<00:24:48.000> you<00:24:48.480> understand<00:24:48.659> networking 00:24:49.549 --> 00:24:49.559 align:start position:0% Administration you understand networking 00:24:49.559 --> 00:24:53.330 align:start position:0% Administration you understand networking uh<00:24:50.520> scripting<00:24:51.080> Docker<00:24:52.080> these<00:24:52.620> are<00:24:52.740> all<00:24:52.860> skills 00:24:53.330 --> 00:24:53.340 align:start position:0% uh scripting Docker these are all skills 00:24:53.340 --> 00:24:56.090 align:start position:0% uh scripting Docker these are all skills that<00:24:53.400> you<00:24:53.580> have<00:24:53.820> and<00:24:54.299> so<00:24:54.539> because<00:24:54.900> of<00:24:55.200> that<00:24:55.380> uh 00:24:56.090 --> 00:24:56.100 align:start position:0% that you have and so because of that uh 00:24:56.100 --> 00:24:58.430 align:start position:0% that you have and so because of that uh you<00:24:56.280> have<00:24:56.400> numerous<00:24:56.880> resources<00:24:57.659> for<00:24:57.900> learning 00:24:58.430 --> 00:24:58.440 align:start position:0% you have numerous resources for learning 00:24:58.440 --> 00:25:01.190 align:start position:0% you have numerous resources for learning about<00:24:58.740> uh<00:24:59.580> which<00:25:00.120> nodes<00:25:00.539> you<00:25:00.780> want<00:25:00.960> to<00:25:01.080> run 00:25:01.190 --> 00:25:01.200 align:start position:0% about uh which nodes you want to run 00:25:01.200 --> 00:25:02.870 align:start position:0% about uh which nodes you want to run which<00:25:01.559> clients<00:25:01.980> you<00:25:02.100> want<00:25:02.220> to<00:25:02.340> run<00:25:02.460> and<00:25:02.640> how 00:25:02.870 --> 00:25:02.880 align:start position:0% which clients you want to run and how 00:25:02.880 --> 00:25:04.669 align:start position:0% which clients you want to run and how you<00:25:02.940> want<00:25:03.120> to<00:25:03.179> run<00:25:03.360> them<00:25:03.539> there's<00:25:04.320> a<00:25:04.440> lot<00:25:04.559> of 00:25:04.669 --> 00:25:04.679 align:start position:0% you want to run them there's a lot of 00:25:04.679 --> 00:25:06.110 align:start position:0% you want to run them there's a lot of documentation<00:25:05.100> with<00:25:05.340> every<00:25:05.520> single<00:25:05.760> client 00:25:06.110 --> 00:25:06.120 align:start position:0% documentation with every single client 00:25:06.120 --> 00:25:08.690 align:start position:0% documentation with every single client about<00:25:06.840> uh<00:25:07.380> becoming<00:25:07.799> an<00:25:07.919> ethereum<00:25:08.340> validator 00:25:08.690 --> 00:25:08.700 align:start position:0% about uh becoming an ethereum validator 00:25:08.700 --> 00:25:11.210 align:start position:0% about uh becoming an ethereum validator with<00:25:09.000> them<00:25:09.120> uh<00:25:10.080> there's<00:25:10.260> no<00:25:10.440> limitation<00:25:10.860> on 00:25:11.210 --> 00:25:11.220 align:start position:0% with them uh there's no limitation on 00:25:11.220 --> 00:25:13.430 align:start position:0% with them uh there's no limitation on the<00:25:11.340> location<00:25:11.520> of<00:25:12.419> where<00:25:12.659> you<00:25:12.780> want<00:25:12.960> to<00:25:13.140> host 00:25:13.430 --> 00:25:13.440 align:start position:0% the location of where you want to host 00:25:13.440 --> 00:25:15.710 align:start position:0% the location of where you want to host your<00:25:13.679> notes<00:25:14.039> and<00:25:14.280> there's<00:25:14.520> no<00:25:14.760> limitation<00:25:15.179> on 00:25:15.710 --> 00:25:15.720 align:start position:0% your notes and there's no limitation on 00:25:15.720 --> 00:25:18.470 align:start position:0% your notes and there's no limitation on the<00:25:15.960> client<00:25:16.440> choice<00:25:16.799> because<00:25:17.100> you<00:25:17.940> can<00:25:18.179> take 00:25:18.470 --> 00:25:18.480 align:start position:0% the client choice because you can take 00:25:18.480 --> 00:25:20.210 align:start position:0% the client choice because you can take anything<00:25:18.780> and<00:25:19.140> run<00:25:19.500> with<00:25:19.679> it<00:25:19.799> because<00:25:19.919> you 00:25:20.210 --> 00:25:20.220 align:start position:0% anything and run with it because you 00:25:20.220 --> 00:25:33.730 align:start position:0% anything and run with it because you have<00:25:20.400> the<00:25:20.520> skills<00:25:20.940> to<00:25:21.480> be<00:25:21.600> able<00:25:21.780> to<00:25:21.900> do<00:25:22.080> that 00:25:33.730 --> 00:25:33.740 align:start position:0% 00:25:33.740 --> 00:25:36.289 align:start position:0% things<00:25:34.740> of<00:25:34.919> that<00:25:35.039> nature<00:25:35.279> so<00:25:35.520> if<00:25:36.000> you're<00:25:36.120> an 00:25:36.289 --> 00:25:36.299 align:start position:0% things of that nature so if you're an 00:25:36.299 --> 00:25:38.090 align:start position:0% things of that nature so if you're an advanced<00:25:36.600> user<00:25:36.960> there's<00:25:37.440> a<00:25:37.679> lot<00:25:37.740> of<00:25:37.860> options 00:25:38.090 --> 00:25:38.100 align:start position:0% advanced user there's a lot of options 00:25:38.100 --> 00:25:39.409 align:start position:0% advanced user there's a lot of options for<00:25:38.340> you<00:25:38.520> out<00:25:38.700> there 00:25:39.409 --> 00:25:39.419 align:start position:0% for you out there 00:25:39.419 --> 00:25:42.230 align:start position:0% for you out there now<00:25:39.840> the<00:25:40.080> entry<00:25:40.500> level<00:25:40.679> users<00:25:41.220> uh<00:25:41.880> so<00:25:42.000> these 00:25:42.230 --> 00:25:42.240 align:start position:0% now the entry level users uh so these 00:25:42.240 --> 00:25:44.149 align:start position:0% now the entry level users uh so these are<00:25:42.299> the<00:25:42.419> folks<00:25:42.659> that<00:25:42.779> don't<00:25:42.960> have<00:25:43.260> all<00:25:43.919> of<00:25:44.039> the 00:25:44.149 --> 00:25:44.159 align:start position:0% are the folks that don't have all of the 00:25:44.159 --> 00:25:48.289 align:start position:0% are the folks that don't have all of the uh<00:25:44.880> all<00:25:45.059> skills<00:25:45.620> uh<00:25:46.620> mentioned<00:25:47.100> above<00:25:47.820> well 00:25:48.289 --> 00:25:48.299 align:start position:0% uh all skills uh mentioned above well 00:25:48.299 --> 00:25:50.269 align:start position:0% uh all skills uh mentioned above well good<00:25:48.720> news<00:25:48.900> is<00:25:49.080> there<00:25:49.559> are<00:25:49.679> three<00:25:49.980> different 00:25:50.269 --> 00:25:50.279 align:start position:0% good news is there are three different 00:25:50.279 --> 00:25:54.730 align:start position:0% good news is there are three different uh<00:25:50.880> GUI<00:25:51.299> based<00:25:51.779> uh<00:25:52.200> software<00:25:52.559> options<00:25:52.980> so<00:25:53.460> this 00:25:54.730 --> 00:25:54.740 align:start position:0% uh GUI based uh software options so this 00:25:54.740 --> 00:25:57.470 align:start position:0% uh GUI based uh software options so this significantly<00:25:55.740> streamlines<00:25:56.460> the<00:25:57.000> the<00:25:57.240> level 00:25:57.470 --> 00:25:57.480 align:start position:0% significantly streamlines the the level 00:25:57.480 --> 00:25:59.510 align:start position:0% significantly streamlines the the level of<00:25:57.840> skill<00:25:58.140> that<00:25:58.380> you<00:25:58.500> need<00:25:58.620> in<00:25:58.919> order<00:25:59.100> to<00:25:59.220> run<00:25:59.340> a 00:25:59.510 --> 00:25:59.520 align:start position:0% of skill that you need in order to run a 00:25:59.520 --> 00:26:00.830 align:start position:0% of skill that you need in order to run a validator 00:26:00.830 --> 00:26:00.840 align:start position:0% validator 00:26:00.840 --> 00:26:03.289 align:start position:0% validator um<00:26:00.960> you<00:26:01.500> might<00:26:01.679> be<00:26:01.860> limited<00:26:02.340> on<00:26:02.940> the<00:26:03.059> location 00:26:03.289 --> 00:26:03.299 align:start position:0% um you might be limited on the location 00:26:03.299 --> 00:26:06.909 align:start position:0% um you might be limited on the location of<00:26:03.900> where<00:26:04.140> you<00:26:04.440> can<00:26:04.620> uh<00:26:05.460> host<00:26:05.760> that<00:26:06.059> validator 00:26:06.909 --> 00:26:06.919 align:start position:0% of where you can uh host that validator 00:26:06.919 --> 00:26:10.250 align:start position:0% of where you can uh host that validator uh<00:26:07.919> we'll<00:26:08.460> we'll<00:26:08.640> get<00:26:09.000> into<00:26:09.179> some<00:26:09.600> of<00:26:09.779> that<00:26:09.900> but 00:26:10.250 --> 00:26:10.260 align:start position:0% uh we'll we'll get into some of that but 00:26:10.260 --> 00:26:13.610 align:start position:0% uh we'll we'll get into some of that but uh<00:26:10.559> with<00:26:10.980> with<00:26:11.460> an<00:26:11.760> entry<00:26:12.120> node<00:26:12.600> uh<00:26:13.140> with<00:26:13.440> an 00:26:13.610 --> 00:26:13.620 align:start position:0% uh with with an entry node uh with an 00:26:13.620 --> 00:26:15.529 align:start position:0% uh with with an entry node uh with an entry<00:26:13.860> level<00:26:13.980> user<00:26:14.400> you're<00:26:14.820> much<00:26:15.059> more<00:26:15.240> likely 00:26:15.529 --> 00:26:15.539 align:start position:0% entry level user you're much more likely 00:26:15.539 --> 00:26:17.269 align:start position:0% entry level user you're much more likely to<00:26:15.659> probably<00:26:15.840> want<00:26:16.020> to<00:26:16.140> run<00:26:16.260> it<00:26:16.440> at<00:26:16.559> home 00:26:17.269 --> 00:26:17.279 align:start position:0% to probably want to run it at home 00:26:17.279 --> 00:26:19.669 align:start position:0% to probably want to run it at home uh<00:26:18.000> you<00:26:18.179> all<00:26:18.360> might<00:26:18.600> be<00:26:18.720> limited<00:26:19.020> on<00:26:19.440> the 00:26:19.669 --> 00:26:19.679 align:start position:0% uh you all might be limited on the 00:26:19.679 --> 00:26:22.669 align:start position:0% uh you all might be limited on the client<00:26:20.039> Choice<00:26:20.460> uh<00:26:21.419> because<00:26:21.659> if<00:26:22.200> you're<00:26:22.320> using 00:26:22.669 --> 00:26:22.679 align:start position:0% client Choice uh because if you're using 00:26:22.679 --> 00:26:23.990 align:start position:0% client Choice uh because if you're using a<00:26:22.740> software<00:26:23.039> platform<00:26:23.340> you're<00:26:23.640> limited<00:26:23.940> to 00:26:23.990 --> 00:26:24.000 align:start position:0% a software platform you're limited to 00:26:24.000 --> 00:26:26.210 align:start position:0% a software platform you're limited to whatever<00:26:24.179> software<00:26:24.900> or<00:26:25.260> whatever<00:26:25.559> clients 00:26:26.210 --> 00:26:26.220 align:start position:0% whatever software or whatever clients 00:26:26.220 --> 00:27:01.570 align:start position:0% whatever software or whatever clients that<00:26:26.580> software<00:26:27.059> has<00:26:27.900> available<00:26:28.140> to<00:26:28.500> you 00:27:01.570 --> 00:27:01.580 align:start position:0% 00:27:01.580 --> 00:27:06.049 align:start position:0% so<00:27:02.580> Windows<00:27:03.480> Mac<00:27:03.779> Linux<00:27:04.380> you<00:27:04.980> install<00:27:05.220> it<00:27:05.580> on 00:27:06.049 --> 00:27:06.059 align:start position:0% so Windows Mac Linux you install it on 00:27:06.059 --> 00:27:08.690 align:start position:0% so Windows Mac Linux you install it on your<00:27:06.240> uh<00:27:07.020> on<00:27:07.260> your<00:27:07.559> computer<00:27:07.740> and<00:27:08.340> then<00:27:08.520> you 00:27:08.690 --> 00:27:08.700 align:start position:0% your uh on your computer and then you 00:27:08.700 --> 00:27:10.669 align:start position:0% your uh on your computer and then you can<00:27:08.880> connect<00:27:09.059> it<00:27:09.299> to<00:27:09.480> a<00:27:09.659> remote<00:27:09.840> server<00:27:10.320> and 00:27:10.669 --> 00:27:10.679 align:start position:0% can connect it to a remote server and 00:27:10.679 --> 00:27:12.289 align:start position:0% can connect it to a remote server and they<00:27:10.919> have<00:27:11.039> a<00:27:11.159> very<00:27:11.279> simple<00:27:11.460> tutorial<00:27:11.880> on<00:27:12.120> like 00:27:12.289 --> 00:27:12.299 align:start position:0% they have a very simple tutorial on like 00:27:12.299 --> 00:27:13.970 align:start position:0% they have a very simple tutorial on like setting<00:27:12.600> up<00:27:12.720> a<00:27:12.840> remote<00:27:13.200> server<00:27:13.679> with 00:27:13.970 --> 00:27:13.980 align:start position:0% setting up a remote server with 00:27:13.980 --> 00:27:16.370 align:start position:0% setting up a remote server with different<00:27:14.159> Cloud<00:27:14.400> providers<00:27:15.000> uh<00:27:15.840> but<00:27:16.020> really 00:27:16.370 --> 00:27:16.380 align:start position:0% different Cloud providers uh but really 00:27:16.380 --> 00:27:19.010 align:start position:0% different Cloud providers uh but really what<00:27:16.679> happens<00:27:16.919> is<00:27:17.159> after<00:27:17.520> you<00:27:17.820> just<00:27:18.120> sign<00:27:18.779> up 00:27:19.010 --> 00:27:19.020 align:start position:0% what happens is after you just sign up 00:27:19.020 --> 00:27:20.750 align:start position:0% what happens is after you just sign up for<00:27:19.260> a<00:27:19.320> server<00:27:19.620> you<00:27:20.220> can<00:27:20.279> actually<00:27:20.400> Point 00:27:20.750 --> 00:27:20.760 align:start position:0% for a server you can actually Point 00:27:20.760 --> 00:27:23.450 align:start position:0% for a server you can actually Point their<00:27:21.120> application<00:27:21.659> to<00:27:22.440> that<00:27:22.679> server<00:27:23.039> and 00:27:23.450 --> 00:27:23.460 align:start position:0% their application to that server and 00:27:23.460 --> 00:27:25.190 align:start position:0% their application to that server and then<00:27:23.640> the<00:27:23.820> application<00:27:24.299> takes<00:27:24.779> care<00:27:25.020> of 00:27:25.190 --> 00:27:25.200 align:start position:0% then the application takes care of 00:27:25.200 --> 00:27:27.289 align:start position:0% then the application takes care of everything<00:27:25.500> uh<00:27:26.460> and<00:27:26.580> it<00:27:26.760> actually<00:27:26.940> does<00:27:27.179> it 00:27:27.289 --> 00:27:27.299 align:start position:0% everything uh and it actually does it 00:27:27.299 --> 00:27:28.549 align:start position:0% everything uh and it actually does it through<00:27:27.419> a<00:27:27.600> really<00:27:27.720> cool<00:27:27.840> technology<00:27:28.260> called 00:27:28.549 --> 00:27:28.559 align:start position:0% through a really cool technology called 00:27:28.559 --> 00:27:33.049 align:start position:0% through a really cool technology called Ansel<00:27:29.100> so<00:27:29.640> basically<00:27:30.299> send<00:27:31.260> uh<00:27:31.919> send<00:27:32.340> commands 00:27:33.049 --> 00:27:33.059 align:start position:0% Ansel so basically send uh send commands 00:27:33.059 --> 00:27:35.750 align:start position:0% Ansel so basically send uh send commands to<00:27:33.360> the<00:27:33.480> server<00:27:33.840> to<00:27:34.200> set<00:27:34.500> it<00:27:34.679> up<00:27:34.860> perfectly<00:27:35.460> for 00:27:35.750 --> 00:27:35.760 align:start position:0% to the server to set it up perfectly for 00:27:35.760 --> 00:27:38.930 align:start position:0% to the server to set it up perfectly for you<00:27:35.960> uh<00:27:36.960> the<00:27:37.380> good<00:27:37.559> and<00:27:37.860> so<00:27:38.100> with<00:27:38.460> this<00:27:38.640> kind<00:27:38.820> of 00:27:38.930 --> 00:27:38.940 align:start position:0% you uh the good and so with this kind of 00:27:38.940 --> 00:27:42.049 align:start position:0% you uh the good and so with this kind of setup<00:27:39.240> entry<00:27:40.200> or<00:27:40.559> uh<00:27:40.799> skill-wise<00:27:41.400> you<00:27:41.820> could 00:27:42.049 --> 00:27:42.059 align:start position:0% setup entry or uh skill-wise you could 00:27:42.059 --> 00:27:43.730 align:start position:0% setup entry or uh skill-wise you could be<00:27:42.179> an<00:27:42.360> artist<00:27:42.539> uh<00:27:43.200> they<00:27:43.440> have<00:27:43.559> great 00:27:43.730 --> 00:27:43.740 align:start position:0% be an artist uh they have great 00:27:43.740 --> 00:27:45.830 align:start position:0% be an artist uh they have great tutorials<00:27:44.220> very<00:27:44.640> simple 00:27:45.830 --> 00:27:45.840 align:start position:0% tutorials very simple 00:27:45.840 --> 00:27:47.570 align:start position:0% tutorials very simple time<00:27:46.200> wise<00:27:46.559> you're<00:27:46.740> looking<00:27:46.919> at<00:27:47.039> maybe<00:27:47.340> about 00:27:47.570 --> 00:27:47.580 align:start position:0% time wise you're looking at maybe about 00:27:47.580 --> 00:27:50.510 align:start position:0% time wise you're looking at maybe about an<00:27:47.940> hour<00:27:48.179> uh<00:27:48.779> or<00:27:49.080> less<00:27:49.260> if<00:27:49.799> if<00:27:50.220> you're 00:27:50.510 --> 00:27:50.520 align:start position:0% an hour uh or less if if you're 00:27:50.520 --> 00:27:52.490 align:start position:0% an hour uh or less if if you're following<00:27:50.880> their<00:27:51.059> tutorials<00:27:51.600> it<00:27:52.080> can<00:27:52.200> be<00:27:52.320> done 00:27:52.490 --> 00:27:52.500 align:start position:0% following their tutorials it can be done 00:27:52.500 --> 00:27:53.870 align:start position:0% following their tutorials it can be done very<00:27:52.799> efficiently 00:27:53.870 --> 00:27:53.880 align:start position:0% very efficiently 00:27:53.880 --> 00:28:09.970 align:start position:0% very efficiently notable<00:27:54.480> features<00:27:55.100> uh 00:28:09.970 --> 00:28:09.980 align:start position:0% 00:28:09.980 --> 00:28:13.909 align:start position:0% uh<00:28:10.980> controller<00:28:11.700> you<00:28:12.419> can<00:28:12.600> host<00:28:13.440> your<00:28:13.740> note 00:28:13.909 --> 00:28:13.919 align:start position:0% uh controller you can host your note 00:28:13.919 --> 00:28:16.190 align:start position:0% uh controller you can host your note really<00:28:14.279> anywhere<00:28:14.820> on<00:28:15.240> any<00:28:15.419> kind<00:28:15.600> of<00:28:15.720> Provider 00:28:16.190 --> 00:28:16.200 align:start position:0% really anywhere on any kind of Provider 00:28:16.200 --> 00:28:18.230 align:start position:0% really anywhere on any kind of Provider uh<00:28:17.100> and<00:28:17.220> so<00:28:17.460> you<00:28:17.580> really<00:28:17.760> have<00:28:17.940> a<00:28:18.059> lot<00:28:18.120> of 00:28:18.230 --> 00:28:18.240 align:start position:0% uh and so you really have a lot of 00:28:18.240 --> 00:28:21.649 align:start position:0% uh and so you really have a lot of location<00:28:18.360> Freedom<00:28:19.220> uh<00:28:20.220> you<00:28:20.760> have<00:28:20.880> extensive 00:28:21.649 --> 00:28:21.659 align:start position:0% location Freedom uh you have extensive 00:28:21.659 --> 00:28:24.110 align:start position:0% location Freedom uh you have extensive client<00:28:21.960> options<00:28:22.440> they<00:28:22.980> do<00:28:23.159> a<00:28:23.400> great<00:28:23.580> job<00:28:23.880> of 00:28:24.110 --> 00:28:24.120 align:start position:0% client options they do a great job of 00:28:24.120 --> 00:28:25.430 align:start position:0% client options they do a great job of giving<00:28:24.299> you<00:28:24.480> tons<00:28:24.779> of<00:28:24.900> different<00:28:25.080> client 00:28:25.430 --> 00:28:25.440 align:start position:0% giving you tons of different client 00:28:25.440 --> 00:28:28.010 align:start position:0% giving you tons of different client options<00:28:25.860> so<00:28:26.700> you<00:28:27.120> could<00:28:27.240> actually<00:28:27.480> take<00:28:27.960> a 00:28:28.010 --> 00:28:28.020 align:start position:0% options so you could actually take a 00:28:28.020 --> 00:28:30.250 align:start position:0% options so you could actually take a look<00:28:28.140> at<00:28:28.320> uh<00:28:28.980> those<00:28:29.220> charts 00:28:30.250 --> 00:28:30.260 align:start position:0% look at uh those charts 00:28:30.260 --> 00:28:34.490 align:start position:0% look at uh those charts okay<00:28:31.260> which<00:28:31.559> ones<00:28:31.860> are<00:28:31.980> over<00:28:32.159> at<00:28:32.400> 33<00:28:33.320> uh<00:28:34.320> and 00:28:34.490 --> 00:28:34.500 align:start position:0% okay which ones are over at 33 uh and 00:28:34.500 --> 00:28:36.289 align:start position:0% okay which ones are over at 33 uh and you<00:28:34.799> most<00:28:35.039> likely<00:28:35.220> don't<00:28:35.520> want<00:28:35.700> to<00:28:35.880> be<00:28:36.000> in<00:28:36.120> that 00:28:36.289 --> 00:28:36.299 align:start position:0% you most likely don't want to be in that 00:28:36.299 --> 00:28:37.970 align:start position:0% you most likely don't want to be in that group<00:28:36.539> because<00:28:36.840> if<00:28:37.080> something<00:28:37.320> happens<00:28:37.620> so 00:28:37.970 --> 00:28:37.980 align:start position:0% group because if something happens so 00:28:37.980 --> 00:28:40.130 align:start position:0% group because if something happens so say<00:28:38.279> you're<00:28:38.520> with<00:28:38.760> prism<00:28:39.120> and<00:28:39.779> something 00:28:40.130 --> 00:28:40.140 align:start position:0% say you're with prism and something 00:28:40.140 --> 00:28:44.750 align:start position:0% say you're with prism and something happens<00:28:40.440> to<00:28:41.039> uh<00:28:41.960> there's<00:28:42.960> a<00:28:43.140> mistake<00:28:43.500> uh<00:28:44.340> in<00:28:44.580> an 00:28:44.750 --> 00:28:44.760 align:start position:0% happens to uh there's a mistake uh in an 00:28:44.760 --> 00:28:48.049 align:start position:0% happens to uh there's a mistake uh in an update<00:28:45.120> what<00:28:45.539> have<00:28:45.840> you<00:28:46.020> what<00:28:46.799> happens<00:28:46.980> is<00:28:47.520> if 00:28:48.049 --> 00:28:48.059 align:start position:0% update what have you what happens is if 00:28:48.059 --> 00:28:49.669 align:start position:0% update what have you what happens is if there<00:28:48.360> are<00:28:48.539> over<00:28:48.659> one<00:28:48.960> third<00:28:49.260> that<00:28:49.559> whole 00:28:49.669 --> 00:28:49.679 align:start position:0% there are over one third that whole 00:28:49.679 --> 00:28:51.230 align:start position:0% there are over one third that whole group<00:28:49.860> is<00:28:50.039> going<00:28:50.220> to<00:28:50.340> start<00:28:50.460> getting<00:28:50.640> slashed 00:28:51.230 --> 00:28:51.240 align:start position:0% group is going to start getting slashed 00:28:51.240 --> 00:28:53.990 align:start position:0% group is going to start getting slashed so<00:28:51.779> you<00:28:52.200> want<00:28:52.500> to<00:28:52.620> be<00:28:52.679> a<00:28:52.919> smaller<00:28:53.279> client<00:28:53.700> group 00:28:53.990 --> 00:28:54.000 align:start position:0% so you want to be a smaller client group 00:28:54.000 --> 00:28:56.510 align:start position:0% so you want to be a smaller client group and<00:28:54.240> that's<00:28:54.419> actually<00:28:54.659> what's<00:28:55.260> brilliant 00:28:56.510 --> 00:28:56.520 align:start position:0% and that's actually what's brilliant 00:28:56.520 --> 00:28:59.330 align:start position:0% and that's actually what's brilliant designed<00:28:57.360> is<00:28:57.720> a<00:28:58.020> one-client<00:28:58.559> diversity<00:28:59.039> so 00:28:59.330 --> 00:28:59.340 align:start position:0% designed is a one-client diversity so 00:28:59.340 --> 00:29:01.789 align:start position:0% designed is a one-client diversity so that<00:28:59.580> you<00:28:59.880> don't<00:29:00.059> have<00:29:00.539> the<00:29:01.380> whole<00:29:01.559> network 00:29:01.789 --> 00:29:01.799 align:start position:0% that you don't have the whole network 00:29:01.799 --> 00:29:05.330 align:start position:0% that you don't have the whole network hinging<00:29:02.520> on<00:29:02.880> one<00:29:03.059> client 00:29:05.330 --> 00:29:05.340 align:start position:0% hinging on one client 00:29:05.340 --> 00:29:08.870 align:start position:0% hinging on one client another<00:29:05.880> platform<00:29:06.419> uh<00:29:07.460> this<00:29:08.460> is<00:29:08.580> a<00:29:08.640> really 00:29:08.870 --> 00:29:08.880 align:start position:0% another platform uh this is a really 00:29:08.880 --> 00:29:10.909 align:start position:0% another platform uh this is a really cool<00:29:09.059> platform<00:29:09.539> uh<00:29:10.140> it's<00:29:10.320> different<00:29:10.559> than<00:29:10.740> the 00:29:10.909 --> 00:29:10.919 align:start position:0% cool platform uh it's different than the 00:29:10.919 --> 00:29:11.930 align:start position:0% cool platform uh it's different than the other<00:29:10.980> one<00:29:11.159> because<00:29:11.279> this<00:29:11.520> is<00:29:11.640> a<00:29:11.700> hardware 00:29:11.930 --> 00:29:11.940 align:start position:0% other one because this is a hardware 00:29:11.940 --> 00:29:14.450 align:start position:0% other one because this is a hardware platform<00:29:12.419> so<00:29:12.659> this<00:29:12.900> is<00:29:13.020> something<00:29:13.320> where<00:29:13.740> you 00:29:14.450 --> 00:29:14.460 align:start position:0% platform so this is something where you 00:29:14.460 --> 00:29:16.490 align:start position:0% platform so this is something where you have<00:29:14.580> to<00:29:14.700> actually<00:29:14.880> buy<00:29:15.299> their<00:29:15.539> Hardware<00:29:15.779> in 00:29:16.490 --> 00:29:16.500 align:start position:0% have to actually buy their Hardware in 00:29:16.500 --> 00:29:20.149 align:start position:0% have to actually buy their Hardware in order<00:29:16.740> to<00:29:17.059> uh<00:29:18.059> use<00:29:18.419> their<00:29:18.659> software<00:29:19.080> so<00:29:19.799> it's 00:29:20.149 --> 00:29:20.159 align:start position:0% order to uh use their software so it's 00:29:20.159 --> 00:29:21.950 align:start position:0% order to uh use their software so it's kind<00:29:20.399> of<00:29:20.520> like<00:29:20.580> that<00:29:20.880> complete<00:29:21.360> package<00:29:21.720> which 00:29:21.950 --> 00:29:21.960 align:start position:0% kind of like that complete package which 00:29:21.960 --> 00:29:23.810 align:start position:0% kind of like that complete package which is<00:29:22.140> great<00:29:22.380> for<00:29:22.620> some<00:29:22.740> users<00:29:23.100> where<00:29:23.399> they<00:29:23.640> just 00:29:23.810 --> 00:29:23.820 align:start position:0% is great for some users where they just 00:29:23.820 --> 00:29:27.110 align:start position:0% is great for some users where they just want<00:29:24.000> to<00:29:24.120> buy<00:29:24.480> it<00:29:24.720> and<00:29:25.440> have<00:29:25.860> a<00:29:26.100> real<00:29:26.279> easy<00:29:26.640> kind 00:29:27.110 --> 00:29:27.120 align:start position:0% want to buy it and have a real easy kind 00:29:27.120 --> 00:29:30.470 align:start position:0% want to buy it and have a real easy kind of<00:29:27.240> uh<00:29:27.960> point-and-click<00:29:28.620> setup<00:29:29.000> but<00:29:30.000> you<00:29:30.360> know 00:29:30.470 --> 00:29:30.480 align:start position:0% of uh point-and-click setup but you know 00:29:30.480 --> 00:29:32.630 align:start position:0% of uh point-and-click setup but you know you<00:29:30.779> do<00:29:31.140> need<00:29:31.320> to<00:29:31.440> buy<00:29:31.559> their<00:29:31.740> Hardware<00:29:31.919> uh<00:29:32.399> you 00:29:32.630 --> 00:29:32.640 align:start position:0% you do need to buy their Hardware uh you 00:29:32.640 --> 00:29:33.830 align:start position:0% you do need to buy their Hardware uh you can't<00:29:32.760> just<00:29:32.880> use<00:29:33.059> it<00:29:33.240> on<00:29:33.299> your<00:29:33.480> own<00:29:33.539> hardware 00:29:33.830 --> 00:29:33.840 align:start position:0% can't just use it on your own hardware 00:29:33.840 --> 00:29:35.950 align:start position:0% can't just use it on your own hardware and<00:29:34.679> you<00:29:34.799> also<00:29:34.980> don't<00:29:35.100> have<00:29:35.279> Hardware<00:29:35.520> Choice 00:29:35.950 --> 00:29:35.960 align:start position:0% and you also don't have Hardware Choice 00:29:35.960 --> 00:29:40.310 align:start position:0% and you also don't have Hardware Choice uh<00:29:36.960> but<00:29:37.380> skill<00:29:38.159> level<00:29:38.340> wise<00:29:38.760> novice<00:29:39.480> very<00:29:40.140> easy 00:29:40.310 --> 00:29:40.320 align:start position:0% uh but skill level wise novice very easy 00:29:40.320 --> 00:29:43.010 align:start position:0% uh but skill level wise novice very easy to<00:29:40.559> use<00:29:40.679> uh<00:29:41.279> we're<00:29:41.460> talking<00:29:41.580> an<00:29:42.120> hour<00:29:42.299> maybe<00:29:42.720> a 00:29:43.010 --> 00:29:43.020 align:start position:0% to use uh we're talking an hour maybe a 00:29:43.020 --> 00:29:44.269 align:start position:0% to use uh we're talking an hour maybe a little<00:29:43.080> bit<00:29:43.260> more<00:29:43.380> of<00:29:43.559> a<00:29:43.679> setup<00:29:43.860> it's<00:29:44.100> a<00:29:44.220> little 00:29:44.269 --> 00:29:44.279 align:start position:0% little bit more of a setup it's a little 00:29:44.279 --> 00:29:46.789 align:start position:0% little bit more of a setup it's a little bit<00:29:44.460> uh<00:29:45.299> there's<00:29:45.600> a<00:29:45.960> few<00:29:46.080> more<00:29:46.200> steps<00:29:46.559> in<00:29:46.679> it 00:29:46.789 --> 00:29:46.799 align:start position:0% bit uh there's a few more steps in it 00:29:46.799 --> 00:29:48.230 align:start position:0% bit uh there's a few more steps in it but<00:29:46.919> it's<00:29:47.039> still<00:29:47.279> a<00:29:47.460> great<00:29:47.640> user<00:29:48.059> experience 00:29:48.230 --> 00:29:48.240 align:start position:0% but it's still a great user experience 00:29:48.240 --> 00:29:50.750 align:start position:0% but it's still a great user experience some<00:29:48.960> notable<00:29:49.320> features<00:29:49.679> is<00:29:49.919> there's<00:29:50.159> no<00:29:50.340> OS 00:29:50.750 --> 00:29:50.760 align:start position:0% some notable features is there's no OS 00:29:50.760 --> 00:29:52.730 align:start position:0% some notable features is there's no OS configuration<00:29:51.360> because<00:29:51.659> you're<00:29:51.960> buying<00:29:52.380> the 00:29:52.730 --> 00:29:52.740 align:start position:0% configuration because you're buying the 00:29:52.740 --> 00:29:55.130 align:start position:0% configuration because you're buying the uh<00:29:53.520> Hardware<00:29:53.820> you<00:29:54.419> don't<00:29:54.539> have<00:29:54.659> to<00:29:54.720> set<00:29:54.899> up<00:29:55.020> the 00:29:55.130 --> 00:29:55.140 align:start position:0% uh Hardware you don't have to set up the 00:29:55.140 --> 00:29:58.070 align:start position:0% uh Hardware you don't have to set up the OS<00:29:55.440> it's<00:29:55.980> a<00:29:56.220> full<00:29:56.460> package<00:29:56.820> in<00:29:57.000> that<00:29:57.179> way<00:29:57.299> they 00:29:58.070 --> 00:29:58.080 align:start position:0% OS it's a full package in that way they 00:29:58.080 --> 00:29:59.630 align:start position:0% OS it's a full package in that way they also<00:29:58.320> have<00:29:58.380> a<00:29:58.559> really<00:29:58.679> impressive<00:29:59.100> app<00:29:59.460> store 00:29:59.630 --> 00:29:59.640 align:start position:0% also have a really impressive app store 00:29:59.640 --> 00:30:02.149 align:start position:0% also have a really impressive app store where<00:30:00.000> you<00:30:00.179> can<00:30:00.360> uh<00:30:01.020> deploy<00:30:01.440> notes<00:30:01.740> from<00:30:01.919> other 00:30:02.149 --> 00:30:02.159 align:start position:0% where you can uh deploy notes from other 00:30:02.159 --> 00:30:04.789 align:start position:0% where you can uh deploy notes from other blockchains<00:30:03.000> or<00:30:03.299> uh<00:30:03.779> other<00:30:03.960> clients<00:30:04.380> and<00:30:04.679> it's 00:30:04.789 --> 00:30:04.799 align:start position:0% blockchains or uh other clients and it's 00:30:04.799 --> 00:30:14.940 align:start position:0% blockchains or uh other clients and it's really<00:30:04.980> cool<00:30:05.220> foreign 00:30:14.940 --> 00:30:14.950 align:start position:0% 00:30:14.950 --> 00:30:38.810 align:start position:0% [Music] 00:30:38.810 --> 00:30:38.820 align:start position:0% 00:30:38.820 --> 00:30:41.149 align:start position:0% skill<00:30:39.419> level<00:30:39.600> wise<00:30:39.960> I<00:30:40.200> give<00:30:40.440> this<00:30:40.620> a<00:30:40.799> moderate 00:30:41.149 --> 00:30:41.159 align:start position:0% skill level wise I give this a moderate 00:30:41.159 --> 00:30:42.590 align:start position:0% skill level wise I give this a moderate and<00:30:41.340> the<00:30:41.460> reason<00:30:41.580> I<00:30:41.820> give<00:30:41.940> it<00:30:42.059> a<00:30:42.120> moderate<00:30:42.419> is 00:30:42.590 --> 00:30:42.600 align:start position:0% and the reason I give it a moderate is 00:30:42.600 --> 00:30:45.350 align:start position:0% and the reason I give it a moderate is because<00:30:42.779> there's<00:30:43.020> a<00:30:43.320> lot<00:30:43.500> of<00:30:43.799> options<00:30:44.220> so<00:30:45.000> for 00:30:45.350 --> 00:30:45.360 align:start position:0% because there's a lot of options so for 00:30:45.360 --> 00:30:47.870 align:start position:0% because there's a lot of options so for some<00:30:45.600> users<00:30:45.960> having<00:30:46.320> that<00:30:46.679> that<00:30:47.220> amount<00:30:47.700> of 00:30:47.870 --> 00:30:47.880 align:start position:0% some users having that that amount of 00:30:47.880 --> 00:30:49.730 align:start position:0% some users having that that amount of options<00:30:48.240> could<00:30:48.539> actually<00:30:48.720> be<00:30:48.960> something<00:30:49.260> that 00:30:49.730 --> 00:30:49.740 align:start position:0% options could actually be something that 00:30:49.740 --> 00:30:53.690 align:start position:0% options could actually be something that is<00:30:49.980> very<00:30:50.520> uh<00:30:51.120> intimidating<00:30:51.600> and<00:30:52.260> so<00:30:52.740> uh<00:30:53.399> but 00:30:53.690 --> 00:30:53.700 align:start position:0% is very uh intimidating and so uh but 00:30:53.700 --> 00:30:55.310 align:start position:0% is very uh intimidating and so uh but there<00:30:54.000> are<00:30:54.179> some<00:30:54.360> great<00:30:54.480> tutorials<00:30:55.020> that<00:30:55.200> you 00:30:55.310 --> 00:30:55.320 align:start position:0% there are some great tutorials that you 00:30:55.320 --> 00:30:57.110 align:start position:0% there are some great tutorials that you know<00:30:55.440> can<00:30:55.620> take<00:30:55.799> people<00:30:55.980> through<00:30:56.340> you<00:30:57.059> know 00:30:57.110 --> 00:30:57.120 align:start position:0% know can take people through you know 00:30:57.120 --> 00:30:58.970 align:start position:0% know can take people through you know setting<00:30:57.600> setting<00:30:58.020> everything<00:30:58.140> up<00:30:58.440> for<00:30:58.620> a<00:30:58.740> DOT 00:30:58.970 --> 00:30:58.980 align:start position:0% setting setting everything up for a DOT 00:30:58.980 --> 00:31:01.250 align:start position:0% setting setting everything up for a DOT node<00:30:59.279> uh<00:31:00.120> it<00:31:00.299> takes<00:31:00.480> a<00:31:00.659> little<00:31:00.779> bit<00:31:00.899> more<00:31:01.020> time 00:31:01.250 --> 00:31:01.260 align:start position:0% node uh it takes a little bit more time 00:31:01.260 --> 00:31:02.870 align:start position:0% node uh it takes a little bit more time because<00:31:01.440> there<00:31:01.679> are<00:31:01.799> more<00:31:01.980> options<00:31:02.399> there's<00:31:02.640> a 00:31:02.870 --> 00:31:02.880 align:start position:0% because there are more options there's a 00:31:02.880 --> 00:31:05.029 align:start position:0% because there are more options there's a few<00:31:03.120> more<00:31:03.299> things<00:31:03.480> you<00:31:03.659> need<00:31:03.779> to<00:31:03.899> set<00:31:04.080> up 00:31:05.029 --> 00:31:05.039 align:start position:0% few more things you need to set up 00:31:05.039 --> 00:31:07.610 align:start position:0% few more things you need to set up um<00:31:05.159> but<00:31:05.399> their<00:31:06.000> approach<00:31:06.419> is<00:31:06.539> really<00:31:06.720> cool<00:31:06.960> uh 00:31:07.610 --> 00:31:07.620 align:start position:0% um but their approach is really cool uh 00:31:07.620 --> 00:31:09.950 align:start position:0% um but their approach is really cool uh it's<00:31:07.740> a<00:31:07.919> notable<00:31:08.220> future<00:31:08.460> wise<00:31:09.000> they<00:31:09.720> they 00:31:09.950 --> 00:31:09.960 align:start position:0% it's a notable future wise they they 00:31:09.960 --> 00:31:12.409 align:start position:0% it's a notable future wise they they have<00:31:10.140> this<00:31:10.380> modular<00:31:10.740> approach<00:31:11.279> so<00:31:11.700> you<00:31:12.240> can 00:31:12.409 --> 00:31:12.419 align:start position:0% have this modular approach so you can 00:31:12.419 --> 00:31:14.870 align:start position:0% have this modular approach so you can choose<00:31:12.960> you<00:31:13.260> know<00:31:13.320> different<00:31:13.880> monitoring 00:31:14.870 --> 00:31:14.880 align:start position:0% choose you know different monitoring 00:31:14.880 --> 00:31:17.450 align:start position:0% choose you know different monitoring tools<00:31:15.240> that<00:31:15.539> you<00:31:15.659> want<00:31:15.779> to<00:31:15.899> use<00:31:16.140> with<00:31:16.559> your<00:31:17.039> uh 00:31:17.450 --> 00:31:17.460 align:start position:0% tools that you want to use with your uh 00:31:17.460 --> 00:31:19.130 align:start position:0% tools that you want to use with your uh with<00:31:17.820> your<00:31:17.940> node<00:31:18.299> and<00:31:18.539> they<00:31:18.659> have<00:31:18.899> a<00:31:19.020> really 00:31:19.130 --> 00:31:19.140 align:start position:0% with your node and they have a really 00:31:19.140 --> 00:31:20.690 align:start position:0% with your node and they have a really cool<00:31:19.380> way<00:31:19.620> of<00:31:19.799> just<00:31:19.919> being<00:31:20.100> able<00:31:20.279> to<00:31:20.399> kind<00:31:20.580> of 00:31:20.690 --> 00:31:20.700 align:start position:0% cool way of just being able to kind of 00:31:20.700 --> 00:31:22.909 align:start position:0% cool way of just being able to kind of create<00:31:20.880> this<00:31:21.360> uh<00:31:22.140> this<00:31:22.440> way<00:31:22.559> of<00:31:22.799> just 00:31:22.909 --> 00:31:22.919 align:start position:0% create this uh this way of just 00:31:22.919 --> 00:31:25.789 align:start position:0% create this uh this way of just deploying<00:31:23.640> different<00:31:24.179> uh<00:31:25.020> packages<00:31:25.380> as<00:31:25.679> they 00:31:25.789 --> 00:31:25.799 align:start position:0% deploying different uh packages as they 00:31:25.799 --> 00:31:27.350 align:start position:0% deploying different uh packages as they call<00:31:25.980> them<00:31:26.159> deploying<00:31:26.820> different<00:31:26.940> packages 00:31:27.350 --> 00:31:27.360 align:start position:0% call them deploying different packages 00:31:27.360 --> 00:31:30.529 align:start position:0% call them deploying different packages that<00:31:28.140> are<00:31:28.380> kind<00:31:28.500> of<00:31:28.679> part<00:31:28.799> of<00:31:28.980> your<00:31:29.539> valuator 00:31:30.529 --> 00:31:30.539 align:start position:0% that are kind of part of your valuator 00:31:30.539 --> 00:31:32.510 align:start position:0% that are kind of part of your valuator Suite<00:31:30.960> if<00:31:31.200> you<00:31:31.320> will<00:31:31.500> so<00:31:31.980> there's<00:31:32.100> a<00:31:32.279> lot<00:31:32.399> of 00:31:32.510 --> 00:31:32.520 align:start position:0% Suite if you will so there's a lot of 00:31:32.520 --> 00:31:34.610 align:start position:0% Suite if you will so there's a lot of customization<00:31:33.059> there<00:31:33.840> um 00:31:34.610 --> 00:31:34.620 align:start position:0% customization there um 00:31:34.620 --> 00:31:38.029 align:start position:0% customization there um uh<00:31:35.580> they<00:31:36.480> have<00:31:36.600> a<00:31:36.779> very<00:31:36.899> simplified<00:31:37.320> OS 00:31:38.029 --> 00:31:38.039 align:start position:0% uh they have a very simplified OS 00:31:38.039 --> 00:31:40.549 align:start position:0% uh they have a very simplified OS installer<00:31:38.580> so<00:31:38.700> you<00:31:38.880> can<00:31:38.940> actually<00:31:39.200> install<00:31:40.200> it 00:31:40.549 --> 00:31:40.559 align:start position:0% installer so you can actually install it 00:31:40.559 --> 00:31:42.710 align:start position:0% installer so you can actually install it from<00:31:40.980> a<00:31:41.340> Ubuntu<00:31:41.820> image<00:31:42.059> that<00:31:42.240> they<00:31:42.360> provide 00:31:42.710 --> 00:31:42.720 align:start position:0% from a Ubuntu image that they provide 00:31:42.720 --> 00:31:44.029 align:start position:0% from a Ubuntu image that they provide and<00:31:43.020> it<00:31:43.140> just<00:31:43.320> streamlines<00:31:43.679> the<00:31:43.860> whole 00:31:44.029 --> 00:31:44.039 align:start position:0% and it just streamlines the whole 00:31:44.039 --> 00:31:45.769 align:start position:0% and it just streamlines the whole process<00:31:44.279> so<00:31:44.640> there's<00:31:44.820> less<00:31:45.120> that<00:31:45.419> people<00:31:45.600> have 00:31:45.769 --> 00:31:45.779 align:start position:0% process so there's less that people have 00:31:45.779 --> 00:31:48.350 align:start position:0% process so there's less that people have to<00:31:45.899> do<00:31:46.080> uh<00:31:46.919> they<00:31:47.340> have<00:31:47.520> a<00:31:47.640> very<00:31:47.760> impressive<00:31:48.000> App 00:31:48.350 --> 00:31:48.360 align:start position:0% to do uh they have a very impressive App 00:31:48.360 --> 00:31:51.169 align:start position:0% to do uh they have a very impressive App Store<00:31:48.539> as<00:31:48.779> well<00:31:49.039> uh<00:31:50.039> far<00:31:50.520> beyond<00:31:50.880> actually 00:31:51.169 --> 00:31:51.179 align:start position:0% Store as well uh far beyond actually 00:31:51.179 --> 00:31:53.630 align:start position:0% Store as well uh far beyond actually nodes<00:31:51.659> they<00:31:51.899> also<00:31:52.200> allow<00:31:52.380> you<00:31:52.500> to<00:31:52.740> uh<00:31:53.399> host 00:31:53.630 --> 00:31:53.640 align:start position:0% nodes they also allow you to uh host 00:31:53.640 --> 00:31:55.610 align:start position:0% nodes they also allow you to uh host your<00:31:53.880> own<00:31:54.000> dapps<00:31:54.539> and<00:31:54.659> things<00:31:54.840> of<00:31:55.080> that<00:31:55.260> nature 00:31:55.610 --> 00:31:55.620 align:start position:0% your own dapps and things of that nature 00:31:55.620 --> 00:31:57.649 align:start position:0% your own dapps and things of that nature so<00:31:55.980> there's<00:31:56.220> a<00:31:56.399> lot<00:31:56.520> of<00:31:56.640> options<00:31:56.940> especially 00:31:57.649 --> 00:31:57.659 align:start position:0% so there's a lot of options especially 00:31:57.659 --> 00:32:00.230 align:start position:0% so there's a lot of options especially or<00:31:58.500> individ<00:31:58.980> Theory<00:31:59.220> ecosystem<00:31:59.640> there's<00:32:00.000> a 00:32:00.230 --> 00:32:00.240 align:start position:0% or individ Theory ecosystem there's a 00:32:00.240 --> 00:32:01.850 align:start position:0% or individ Theory ecosystem there's a lot<00:32:00.360> of<00:32:00.480> options<00:32:00.659> that<00:32:01.260> you<00:32:01.320> can<00:32:01.440> do<00:32:01.559> with<00:32:01.679> that 00:32:01.850 --> 00:32:01.860 align:start position:0% lot of options that you can do with that 00:32:01.860 --> 00:32:04.070 align:start position:0% lot of options that you can do with that it's<00:32:02.220> a<00:32:02.340> very<00:32:02.460> impressive<00:32:02.760> platform 00:32:04.070 --> 00:32:04.080 align:start position:0% it's a very impressive platform 00:32:04.080 --> 00:32:06.409 align:start position:0% it's a very impressive platform and<00:32:04.620> it's<00:32:04.919> Advanced<00:32:05.279> user<00:32:05.700> friendly<00:32:06.000> so 00:32:06.409 --> 00:32:06.419 align:start position:0% and it's Advanced user friendly so 00:32:06.419 --> 00:32:08.750 align:start position:0% and it's Advanced user friendly so Advanced<00:32:06.960> users<00:32:07.320> can<00:32:07.559> actually<00:32:07.799> do<00:32:08.279> a<00:32:08.460> lot<00:32:08.580> of 00:32:08.750 --> 00:32:08.760 align:start position:0% Advanced users can actually do a lot of 00:32:08.760 --> 00:32:12.169 align:start position:0% Advanced users can actually do a lot of modifying<00:32:09.419> uh<00:32:10.200> there's<00:32:10.440> a<00:32:10.620> lot<00:32:10.740> of<00:32:10.919> kind<00:32:11.220> of<00:32:11.399> uh 00:32:12.169 --> 00:32:12.179 align:start position:0% modifying uh there's a lot of kind of uh 00:32:12.179 --> 00:32:15.409 align:start position:0% modifying uh there's a lot of kind of uh um<00:32:12.299> there's<00:32:12.840> kind<00:32:13.260> of<00:32:13.380> this<00:32:13.500> like<00:32:13.799> uh<00:32:14.700> uh 00:32:15.409 --> 00:32:15.419 align:start position:0% um there's kind of this like uh uh 00:32:15.419 --> 00:32:17.389 align:start position:0% um there's kind of this like uh uh tweaking<00:32:15.720> Community<00:32:16.080> inside<00:32:16.740> of<00:32:17.039> that<00:32:17.159> note 00:32:17.389 --> 00:32:17.399 align:start position:0% tweaking Community inside of that note 00:32:17.399 --> 00:32:19.610 align:start position:0% tweaking Community inside of that note where<00:32:17.760> people<00:32:18.000> are<00:32:18.179> able<00:32:18.419> to<00:32:18.539> set<00:32:19.260> things<00:32:19.440> up 00:32:19.610 --> 00:32:19.620 align:start position:0% where people are able to set things up 00:32:19.620 --> 00:32:21.889 align:start position:0% where people are able to set things up in<00:32:19.799> a<00:32:19.980> certain<00:32:20.100> way<00:32:20.279> uh<00:32:20.880> you<00:32:21.419> know<00:32:21.539> achieve 00:32:21.889 --> 00:32:21.899 align:start position:0% in a certain way uh you know achieve 00:32:21.899 --> 00:32:23.570 align:start position:0% in a certain way uh you know achieve certain<00:32:22.080> goals<00:32:22.440> and<00:32:22.559> so<00:32:22.740> that's<00:32:23.279> a<00:32:23.460> really 00:32:23.570 --> 00:32:23.580 align:start position:0% certain goals and so that's a really 00:32:23.580 --> 00:32:26.930 align:start position:0% certain goals and so that's a really cool<00:32:23.880> advantage<00:32:24.779> to<00:32:25.020> being<00:32:25.260> kind<00:32:25.679> of<00:32:25.860> uh<00:32:26.520> this 00:32:26.930 --> 00:32:26.940 align:start position:0% cool advantage to being kind of uh this 00:32:26.940 --> 00:32:29.750 align:start position:0% cool advantage to being kind of uh this platform<00:32:27.600> is<00:32:28.140> there's<00:32:28.620> places<00:32:29.039> you<00:32:29.399> can<00:32:29.520> go 00:32:29.750 --> 00:32:29.760 align:start position:0% platform is there's places you can go 00:32:29.760 --> 00:32:35.090 align:start position:0% platform is there's places you can go far<00:32:30.299> beyond<00:32:30.659> whatever<00:32:30.960> yourself 00:32:35.090 --> 00:32:35.100 align:start position:0% 00:32:35.100 --> 00:32:39.830 align:start position:0% so<00:32:35.960> uh<00:32:36.960> no<00:32:37.140> software<00:32:37.740> is<00:32:38.580> the<00:32:38.820> best<00:32:39.000> way<00:32:39.299> to 00:32:39.830 --> 00:32:39.840 align:start position:0% so uh no software is the best way to 00:32:39.840 --> 00:32:42.350 align:start position:0% so uh no software is the best way to decentralized<00:32:40.559> and<00:32:40.919> that<00:32:41.039> is<00:32:41.220> my<00:32:41.399> argument<00:32:41.700> uh 00:32:42.350 --> 00:32:42.360 align:start position:0% decentralized and that is my argument uh 00:32:42.360 --> 00:32:43.610 align:start position:0% decentralized and that is my argument uh and<00:32:42.539> the<00:32:42.659> reason<00:32:42.779> I'm<00:32:43.020> saying<00:32:43.260> that<00:32:43.380> is 00:32:43.610 --> 00:32:43.620 align:start position:0% and the reason I'm saying that is 00:32:43.620 --> 00:32:46.370 align:start position:0% and the reason I'm saying that is because<00:32:43.919> no<00:32:44.460> software<00:32:44.880> can<00:32:45.120> encourage<00:32:45.899> anyone 00:32:46.370 --> 00:32:46.380 align:start position:0% because no software can encourage anyone 00:32:46.380 --> 00:32:48.710 align:start position:0% because no software can encourage anyone to<00:32:46.620> run<00:32:46.799> validators<00:32:47.340> from<00:32:47.640> home<00:32:47.820> you<00:32:48.539> don't 00:32:48.710 --> 00:32:48.720 align:start position:0% to run validators from home you don't 00:32:48.720 --> 00:32:51.830 align:start position:0% to run validators from home you don't have<00:32:48.960> to<00:32:49.200> use<00:32:49.620> a<00:32:50.220> cloud<00:32:50.460> platform<00:32:51.000> if<00:32:51.419> you<00:32:51.600> can 00:32:51.830 --> 00:32:51.840 align:start position:0% have to use a cloud platform if you can 00:32:51.840 --> 00:32:53.930 align:start position:0% have to use a cloud platform if you can easily<00:32:52.380> and<00:32:52.559> simply<00:32:52.919> run 00:32:53.930 --> 00:32:53.940 align:start position:0% easily and simply run 00:32:53.940 --> 00:32:57.110 align:start position:0% easily and simply run validate<00:32:54.840> your<00:32:54.960> notes<00:32:55.260> at<00:32:55.799> home<00:32:55.980> uh<00:32:56.940> it 00:32:57.110 --> 00:32:57.120 align:start position:0% validate your notes at home uh it 00:32:57.120 --> 00:32:58.789 align:start position:0% validate your notes at home uh it ensures<00:32:57.419> that<00:32:57.600> updates<00:32:58.020> and<00:32:58.200> best<00:32:58.440> practices 00:32:58.789 --> 00:32:58.799 align:start position:0% ensures that updates and best practices 00:32:58.799 --> 00:33:01.789 align:start position:0% ensures that updates and best practices are<00:32:59.220> being<00:32:59.399> applied<00:32:59.820> so<00:33:00.480> if<00:33:00.720> it<00:33:01.380> says<00:33:01.679> someone 00:33:01.789 --> 00:33:01.799 align:start position:0% are being applied so if it says someone 00:33:01.799 --> 00:33:13.080 align:start position:0% are being applied so if it says someone wants<00:33:02.100> to<00:33:02.159> run<00:33:02.399> a<00:33:03.240> uh 00:33:13.080 --> 00:33:13.090 align:start position:0% 00:33:13.090 --> 00:33:15.009 align:start position:0% [Music] 00:33:15.009 --> 00:33:15.019 align:start position:0% [Music] 00:33:15.019 --> 00:33:18.110 align:start position:0% [Music] into<00:33:16.019> you<00:33:16.679> know<00:33:16.740> terminal<00:33:17.159> in<00:33:17.460> order<00:33:17.700> to<00:33:17.940> try 00:33:18.110 --> 00:33:18.120 align:start position:0% into you know terminal in order to try 00:33:18.120 --> 00:33:20.090 align:start position:0% into you know terminal in order to try to<00:33:18.240> get<00:33:18.419> it<00:33:18.539> all<00:33:18.659> working<00:33:18.960> but<00:33:19.380> they<00:33:19.980> don't 00:33:20.090 --> 00:33:20.100 align:start position:0% to get it all working but they don't 00:33:20.100 --> 00:33:21.950 align:start position:0% to get it all working but they don't know<00:33:20.399> exactly<00:33:20.940> if<00:33:21.240> everything's<00:33:21.720> working 00:33:21.950 --> 00:33:21.960 align:start position:0% know exactly if everything's working 00:33:21.960 --> 00:33:23.389 align:start position:0% know exactly if everything's working properly<00:33:22.559> they<00:33:22.799> don't<00:33:22.980> really<00:33:23.159> understand 00:33:23.389 --> 00:33:23.399 align:start position:0% properly they don't really understand 00:33:23.399 --> 00:33:25.490 align:start position:0% properly they don't really understand how<00:33:23.820> everything's<00:33:24.240> working<00:33:24.419> that's<00:33:25.260> actually 00:33:25.490 --> 00:33:25.500 align:start position:0% how everything's working that's actually 00:33:25.500 --> 00:33:27.950 align:start position:0% how everything's working that's actually where<00:33:25.980> no<00:33:26.340> software<00:33:26.880> can<00:33:27.120> come<00:33:27.299> in<00:33:27.419> because<00:33:27.659> it 00:33:27.950 --> 00:33:27.960 align:start position:0% where no software can come in because it 00:33:27.960 --> 00:33:30.470 align:start position:0% where no software can come in because it can<00:33:28.140> standardize<00:33:28.620> how<00:33:28.919> things<00:33:29.100> operate<00:33:29.580> uh 00:33:30.470 --> 00:33:30.480 align:start position:0% can standardize how things operate uh 00:33:30.480 --> 00:33:32.090 align:start position:0% can standardize how things operate uh and<00:33:30.659> ensure<00:33:30.960> that<00:33:31.140> best<00:33:31.380> practices<00:33:31.620> are<00:33:31.919> being 00:33:32.090 --> 00:33:32.100 align:start position:0% and ensure that best practices are being 00:33:32.100 --> 00:33:34.430 align:start position:0% and ensure that best practices are being deployed<00:33:32.519> when<00:33:32.700> you<00:33:32.820> deployed<00:33:33.179> a<00:33:33.299> node<00:33:33.480> uh 00:33:34.430 --> 00:33:34.440 align:start position:0% deployed when you deployed a node uh 00:33:34.440 --> 00:33:36.710 align:start position:0% deployed when you deployed a node uh when<00:33:34.740> you<00:33:34.919> deploy<00:33:35.220> a<00:33:35.279> validator<00:33:35.640> uh<00:33:36.240> it<00:33:36.480> also 00:33:36.710 --> 00:33:36.720 align:start position:0% when you deploy a validator uh it also 00:33:36.720 --> 00:33:39.769 align:start position:0% when you deploy a validator uh it also simplifies<00:33:37.220> uh<00:33:38.220> client<00:33:38.760> adoption<00:33:39.179> you<00:33:39.720> know 00:33:39.769 --> 00:33:39.779 align:start position:0% simplifies uh client adoption you know 00:33:39.779 --> 00:33:41.570 align:start position:0% simplifies uh client adoption you know ultimately<00:33:40.200> if<00:33:40.500> you<00:33:40.620> have<00:33:40.799> options<00:33:41.220> inside 00:33:41.570 --> 00:33:41.580 align:start position:0% ultimately if you have options inside 00:33:41.580 --> 00:33:43.730 align:start position:0% ultimately if you have options inside this<00:33:42.000> uh<00:33:42.480> software<00:33:42.840> platforms<00:33:43.320> you<00:33:43.620> can 00:33:43.730 --> 00:33:43.740 align:start position:0% this uh software platforms you can 00:33:43.740 --> 00:33:45.710 align:start position:0% this uh software platforms you can choose<00:33:44.039> you<00:33:44.640> know<00:33:44.700> which<00:33:45.000> clients<00:33:45.419> you<00:33:45.539> want 00:33:45.710 --> 00:33:45.720 align:start position:0% choose you know which clients you want 00:33:45.720 --> 00:33:48.230 align:start position:0% choose you know which clients you want to<00:33:45.840> use<00:33:46.039> uh<00:33:47.039> ultimately<00:33:47.399> that's<00:33:47.820> where 00:33:48.230 --> 00:33:48.240 align:start position:0% to use uh ultimately that's where 00:33:48.240 --> 00:33:51.409 align:start position:0% to use uh ultimately that's where software<00:33:49.200> can<00:33:49.440> go<00:33:49.740> and<00:33:50.399> software<00:33:50.940> can<00:33:51.120> make<00:33:51.299> it 00:33:51.409 --> 00:33:51.419 align:start position:0% software can go and software can make it 00:33:51.419 --> 00:33:53.810 align:start position:0% software can go and software can make it just<00:33:51.539> really<00:33:51.720> easy<00:33:51.899> for<00:33:52.080> people<00:33:52.320> to<00:33:52.679> uh<00:33:53.519> pick 00:33:53.810 --> 00:33:53.820 align:start position:0% just really easy for people to uh pick 00:33:53.820 --> 00:33:55.549 align:start position:0% just really easy for people to uh pick their<00:33:54.059> clients<00:33:54.419> and<00:33:54.720> pick<00:33:54.960> the<00:33:55.140> small<00:33:55.320> ones 00:33:55.549 --> 00:33:55.559 align:start position:0% their clients and pick the small ones 00:33:55.559 --> 00:33:59.330 align:start position:0% their clients and pick the small ones and<00:33:55.740> the<00:33:55.919> unused<00:33:56.279> ones<00:33:57.000> so<00:33:57.659> uh<00:33:58.559> so<00:33:58.860> what<00:33:59.159> are 00:33:59.330 --> 00:33:59.340 align:start position:0% and the unused ones so uh so what are 00:33:59.340 --> 00:34:01.370 align:start position:0% and the unused ones so uh so what are some<00:33:59.460> challenges<00:33:59.880> to<00:34:00.360> developing<00:34:00.960> no 00:34:01.370 --> 00:34:01.380 align:start position:0% some challenges to developing no 00:34:01.380 --> 00:34:03.169 align:start position:0% some challenges to developing no software<00:34:01.860> if<00:34:02.159> that's<00:34:02.279> kind<00:34:02.580> of<00:34:02.640> one<00:34:02.880> of<00:34:03.059> the 00:34:03.169 --> 00:34:03.179 align:start position:0% software if that's kind of one of the 00:34:03.179 --> 00:34:05.029 align:start position:0% software if that's kind of one of the key<00:34:03.720> ways<00:34:04.080> that<00:34:04.200> we<00:34:04.380> can<00:34:04.500> really<00:34:04.679> encourage 00:34:05.029 --> 00:34:05.039 align:start position:0% key ways that we can really encourage 00:34:05.039 --> 00:34:06.350 align:start position:0% key ways that we can really encourage people<00:34:05.279> to<00:34:05.460> run<00:34:05.580> at<00:34:05.760> home<00:34:05.880> what<00:34:06.059> are<00:34:06.179> some<00:34:06.299> of 00:34:06.350 --> 00:34:06.360 align:start position:0% people to run at home what are some of 00:34:06.360 --> 00:34:08.210 align:start position:0% people to run at home what are some of the<00:34:06.480> challenges<00:34:06.779> well<00:34:07.440> it<00:34:07.679> requires<00:34:08.040> full 00:34:08.210 --> 00:34:08.220 align:start position:0% the challenges well it requires full 00:34:08.220 --> 00:34:10.070 align:start position:0% the challenges well it requires full stack<00:34:08.520> development<00:34:09.000> skills<00:34:09.480> so<00:34:09.780> we're 00:34:10.070 --> 00:34:10.080 align:start position:0% stack development skills so we're 00:34:10.080 --> 00:34:11.629 align:start position:0% stack development skills so we're talking<00:34:10.260> back<00:34:10.500> in<00:34:10.679> the<00:34:10.800> front<00:34:10.859> so<00:34:11.220> you<00:34:11.339> have<00:34:11.520> to 00:34:11.629 --> 00:34:11.639 align:start position:0% talking back in the front so you have to 00:34:11.639 --> 00:34:13.250 align:start position:0% talking back in the front so you have to be<00:34:11.760> really<00:34:12.060> familiar<00:34:12.540> with<00:34:13.020> the<00:34:13.139> whole 00:34:13.250 --> 00:34:13.260 align:start position:0% be really familiar with the whole 00:34:13.260 --> 00:34:14.570 align:start position:0% be really familiar with the whole backing<00:34:13.619> you<00:34:13.800> have<00:34:13.919> to<00:34:13.980> be<00:34:14.040> able<00:34:14.159> to<00:34:14.220> deploy 00:34:14.570 --> 00:34:14.580 align:start position:0% backing you have to be able to deploy 00:34:14.580 --> 00:34:18.589 align:start position:0% backing you have to be able to deploy notes<00:34:15.080> uh<00:34:16.080> understand<00:34:16.379> Docker<00:34:17.220> or<00:34:17.700> uh<00:34:18.359> if 00:34:18.589 --> 00:34:18.599 align:start position:0% notes uh understand Docker or uh if 00:34:18.599 --> 00:34:19.849 align:start position:0% notes uh understand Docker or uh if you're<00:34:18.659> if<00:34:18.839> you're<00:34:19.020> disappointed<00:34:19.440> directly 00:34:19.849 --> 00:34:19.859 align:start position:0% you're if you're disappointed directly 00:34:19.859 --> 00:34:21.470 align:start position:0% you're if you're disappointed directly onto<00:34:20.159> the<00:34:20.339> OS<00:34:20.580> there's<00:34:20.879> a<00:34:21.060> lot<00:34:21.119> that<00:34:21.300> you<00:34:21.419> have 00:34:21.470 --> 00:34:21.480 align:start position:0% onto the OS there's a lot that you have 00:34:21.480 --> 00:34:23.510 align:start position:0% onto the OS there's a lot that you have to<00:34:21.599> figure<00:34:21.720> out<00:34:21.899> on<00:34:22.560> that<00:34:22.679> side<00:34:22.859> plus<00:34:23.159> you<00:34:23.339> have 00:34:23.510 --> 00:34:23.520 align:start position:0% to figure out on that side plus you have 00:34:23.520 --> 00:34:25.369 align:start position:0% to figure out on that side plus you have to<00:34:23.639> worry<00:34:23.879> about<00:34:24.060> the<00:34:24.300> front<00:34:24.419> end<00:34:24.659> so<00:34:25.020> you 00:34:25.369 --> 00:34:25.379 align:start position:0% to worry about the front end so you 00:34:25.379 --> 00:34:28.250 align:start position:0% to worry about the front end so you really<00:34:25.500> it<00:34:26.099> the<00:34:26.639> software<00:34:27.000> has<00:34:27.119> to<00:34:27.300> be<00:34:27.419> uh 00:34:28.250 --> 00:34:28.260 align:start position:0% really it the software has to be uh 00:34:28.260 --> 00:34:31.250 align:start position:0% really it the software has to be uh really<00:34:28.440> a<00:34:28.679> full<00:34:28.859> sack<00:34:29.220> software<00:34:30.000> uh<00:34:30.899> in<00:34:31.080> order 00:34:31.250 --> 00:34:31.260 align:start position:0% really a full sack software uh in order 00:34:31.260 --> 00:34:33.050 align:start position:0% really a full sack software uh in order to<00:34:31.560> really<00:34:31.919> be<00:34:32.159> able<00:34:32.280> to<00:34:32.460> meet<00:34:32.700> all<00:34:32.879> the 00:34:33.050 --> 00:34:33.060 align:start position:0% to really be able to meet all the 00:34:33.060 --> 00:34:35.510 align:start position:0% to really be able to meet all the requirements<00:34:33.480> to<00:34:34.020> be<00:34:34.379> a<00:34:34.800> good<00:34:34.919> running<00:34:35.159> those 00:34:35.510 --> 00:34:35.520 align:start position:0% requirements to be a good running those 00:34:35.520 --> 00:34:37.129 align:start position:0% requirements to be a good running those software<00:34:35.879> we're<00:34:36.300> also<00:34:36.540> talking<00:34:36.720> about<00:34:36.839> you 00:34:37.129 --> 00:34:37.139 align:start position:0% software we're also talking about you 00:34:37.139 --> 00:34:38.510 align:start position:0% software we're also talking about you have<00:34:37.320> to<00:34:37.379> have<00:34:37.560> a<00:34:37.619> deep<00:34:37.800> understanding<00:34:38.280> of<00:34:38.339> no 00:34:38.510 --> 00:34:38.520 align:start position:0% have to have a deep understanding of no 00:34:38.520 --> 00:34:39.649 align:start position:0% have to have a deep understanding of no running<00:34:38.760> itself<00:34:39.119> you<00:34:39.359> have<00:34:39.480> to<00:34:39.540> understand 00:34:39.649 --> 00:34:39.659 align:start position:0% running itself you have to understand 00:34:39.659 --> 00:34:41.149 align:start position:0% running itself you have to understand the<00:34:39.960> best<00:34:40.139> practices<00:34:40.440> you<00:34:40.859> have<00:34:41.040> to 00:34:41.149 --> 00:34:41.159 align:start position:0% the best practices you have to 00:34:41.159 --> 00:34:43.250 align:start position:0% the best practices you have to understand<00:34:41.359> what<00:34:42.359> your<00:34:42.540> software<00:34:42.899> needs<00:34:43.200> to 00:34:43.250 --> 00:34:43.260 align:start position:0% understand what your software needs to 00:34:43.260 --> 00:34:46.970 align:start position:0% understand what your software needs to look<00:34:43.379> for<00:34:43.619> XYZ<00:34:44.659> uh<00:34:45.659> while<00:34:46.080> also<00:34:46.560> you<00:34:46.919> know 00:34:46.970 --> 00:34:46.980 align:start position:0% look for XYZ uh while also you know 00:34:46.980 --> 00:34:49.010 align:start position:0% look for XYZ uh while also you know right<00:34:47.220> brain<00:34:47.639> you<00:34:48.179> also<00:34:48.419> have<00:34:48.480> to<00:34:48.659> think<00:34:48.899> about 00:34:49.010 --> 00:34:49.020 align:start position:0% right brain you also have to think about 00:34:49.020 --> 00:34:51.109 align:start position:0% right brain you also have to think about the<00:34:49.260> user<00:34:49.560> the<00:34:49.740> creative<00:34:50.040> side<00:34:50.280> of<00:34:50.520> figuring 00:34:51.109 --> 00:34:51.119 align:start position:0% the user the creative side of figuring 00:34:51.119 --> 00:34:52.669 align:start position:0% the user the creative side of figuring out<00:34:51.179> user<00:34:51.599> experience<00:34:51.899> what<00:34:52.200> will<00:34:52.379> engage 00:34:52.669 --> 00:34:52.679 align:start position:0% out user experience what will engage 00:34:52.679 --> 00:34:54.050 align:start position:0% out user experience what will engage users<00:34:53.099> what<00:34:53.280> will<00:34:53.399> make<00:34:53.520> them<00:34:53.639> want<00:34:53.820> to<00:34:53.940> use 00:34:54.050 --> 00:34:54.060 align:start position:0% users what will make them want to use 00:34:54.060 --> 00:34:56.389 align:start position:0% users what will make them want to use your<00:34:54.240> software<00:34:54.540> so<00:34:55.379> you<00:34:55.919> really<00:34:56.040> have<00:34:56.220> to<00:34:56.339> have 00:34:56.389 --> 00:34:56.399 align:start position:0% your software so you really have to have 00:34:56.399 --> 00:35:31.130 align:start position:0% your software so you really have to have a<00:34:56.520> deep<00:34:56.639> understanding<00:34:56.940> uh 00:35:31.130 --> 00:35:31.140 align:start position:0% 00:35:31.140 --> 00:35:34.310 align:start position:0% but<00:35:32.040> uh<00:35:33.000> I<00:35:33.660> didn't<00:35:33.839> really<00:35:34.020> give<00:35:34.200> an 00:35:34.310 --> 00:35:34.320 align:start position:0% but uh I didn't really give an 00:35:34.320 --> 00:35:35.810 align:start position:0% but uh I didn't really give an introduction<00:35:34.680> to<00:35:34.859> decentralized<00:35:35.520> Authority 00:35:35.810 --> 00:35:35.820 align:start position:0% introduction to decentralized Authority 00:35:35.820 --> 00:35:38.329 align:start position:0% introduction to decentralized Authority what<00:35:36.359> we're<00:35:36.660> doing<00:35:36.900> is<00:35:37.440> we're<00:35:37.740> developing 00:35:38.329 --> 00:35:38.339 align:start position:0% what we're doing is we're developing 00:35:38.339 --> 00:35:40.430 align:start position:0% what we're doing is we're developing software<00:35:38.760> uh<00:35:39.300> and<00:35:39.420> specifically<00:35:39.839> no<00:35:40.079> software 00:35:40.430 --> 00:35:40.440 align:start position:0% software uh and specifically no software 00:35:40.440 --> 00:35:44.450 align:start position:0% software uh and specifically no software and<00:35:40.980> so<00:35:41.220> uh<00:35:41.880> I<00:35:42.119> wanted<00:35:42.240> to<00:35:42.740> uh<00:35:43.740> talk<00:35:44.099> a<00:35:44.339> little 00:35:44.450 --> 00:35:44.460 align:start position:0% and so uh I wanted to uh talk a little 00:35:44.460 --> 00:35:46.490 align:start position:0% and so uh I wanted to uh talk a little bit<00:35:44.579> about<00:35:44.940> how<00:35:45.420> we<00:35:45.540> can<00:35:45.720> see<00:35:45.900> the<00:35:46.140> no 00:35:46.490 --> 00:35:46.500 align:start position:0% bit about how we can see the no 00:35:46.500 --> 00:35:48.770 align:start position:0% bit about how we can see the no landscape<00:35:47.099> changing<00:35:47.880> with<00:35:48.060> the<00:35:48.359> software 00:35:48.770 --> 00:35:48.780 align:start position:0% landscape changing with the software 00:35:48.780 --> 00:35:52.010 align:start position:0% landscape changing with the software with<00:35:49.500> tools<00:35:50.099> like<00:35:50.520> node<00:35:50.880> launcher<00:35:51.300> which<00:35:51.720> is<00:35:51.839> a 00:35:52.010 --> 00:35:52.020 align:start position:0% with tools like node launcher which is a 00:35:52.020 --> 00:35:55.730 align:start position:0% with tools like node launcher which is a typescript<00:35:52.500> uh<00:35:53.220> no<00:35:53.400> deployment<00:35:54.000> engine<00:35:54.240> so<00:35:54.960> no 00:35:55.730 --> 00:35:55.740 align:start position:0% typescript uh no deployment engine so no 00:35:55.740 --> 00:35:58.250 align:start position:0% typescript uh no deployment engine so no launcher<00:35:56.339> is<00:35:56.579> an<00:35:56.820> open<00:35:57.000> source<00:35:57.480> no<00:35:57.720> deployment 00:35:58.250 --> 00:35:58.260 align:start position:0% launcher is an open source no deployment 00:35:58.260 --> 00:36:01.010 align:start position:0% launcher is an open source no deployment engine<00:35:58.560> written<00:35:59.339> in<00:35:59.640> typescript<00:36:00.119> that 00:36:01.010 --> 00:36:01.020 align:start position:0% engine written in typescript that 00:36:01.020 --> 00:36:03.650 align:start position:0% engine written in typescript that enables<00:36:01.619> the<00:36:02.099> easy<00:36:02.400> creation<00:36:02.940> of<00:36:03.480> no 00:36:03.650 --> 00:36:03.660 align:start position:0% enables the easy creation of no 00:36:03.660 --> 00:36:06.109 align:start position:0% enables the easy creation of no development<00:36:04.140> applications<00:36:04.800> so<00:36:05.700> if<00:36:05.940> someone 00:36:06.109 --> 00:36:06.119 align:start position:0% development applications so if someone 00:36:06.119 --> 00:36:09.829 align:start position:0% development applications so if someone wants<00:36:06.480> to<00:36:06.540> create<00:36:07.040> a<00:36:08.040> application<00:36:08.700> uh<00:36:09.540> that<00:36:09.660> is 00:36:09.829 --> 00:36:09.839 align:start position:0% wants to create a application uh that is 00:36:09.839 --> 00:36:11.990 align:start position:0% wants to create a application uh that is for<00:36:10.079> running<00:36:10.260> those<00:36:10.680> what<00:36:11.280> no<00:36:11.460> launcher<00:36:11.880> does 00:36:11.990 --> 00:36:12.000 align:start position:0% for running those what no launcher does 00:36:12.000 --> 00:36:14.450 align:start position:0% for running those what no launcher does is<00:36:12.359> it<00:36:12.660> allows<00:36:13.079> them<00:36:13.320> to<00:36:13.560> start<00:36:13.740> developing<00:36:14.339> an 00:36:14.450 --> 00:36:14.460 align:start position:0% is it allows them to start developing an 00:36:14.460 --> 00:36:15.829 align:start position:0% is it allows them to start developing an application<00:36:14.880> without<00:36:15.300> needing<00:36:15.780> to 00:36:15.829 --> 00:36:15.839 align:start position:0% application without needing to 00:36:15.839 --> 00:36:17.630 align:start position:0% application without needing to understand<00:36:15.960> the<00:36:16.320> back<00:36:16.560> end<00:36:16.740> because<00:36:17.220> it's<00:36:17.460> a 00:36:17.630 --> 00:36:17.640 align:start position:0% understand the back end because it's a 00:36:17.640 --> 00:36:19.849 align:start position:0% understand the back end because it's a full<00:36:17.760> deployment<00:36:18.180> engine<00:36:18.480> it<00:36:19.200> will<00:36:19.320> deploy 00:36:19.849 --> 00:36:19.859 align:start position:0% full deployment engine it will deploy 00:36:19.859 --> 00:36:23.089 align:start position:0% full deployment engine it will deploy the<00:36:20.339> nodes<00:36:20.579> in<00:36:20.880> the<00:36:21.000> proper<00:36:21.300> way<00:36:21.560> uh<00:36:22.560> using 00:36:23.089 --> 00:36:23.099 align:start position:0% the nodes in the proper way uh using 00:36:23.099 --> 00:36:26.390 align:start position:0% the nodes in the proper way uh using apis<00:36:23.940> the<00:36:24.660> features<00:36:25.020> those<00:36:25.619> can<00:36:25.859> be<00:36:25.980> deployed 00:36:26.390 --> 00:36:26.400 align:start position:0% apis the features those can be deployed 00:36:26.400 --> 00:36:28.790 align:start position:0% apis the features those can be deployed and<00:36:26.640> controlled<00:36:27.240> through<00:36:27.540> standard<00:36:27.960> apis<00:36:28.440> you 00:36:28.790 --> 00:36:28.800 align:start position:0% and controlled through standard apis you 00:36:28.800 --> 00:36:31.069 align:start position:0% and controlled through standard apis you don't<00:36:28.920> have<00:36:29.099> to<00:36:29.280> know<00:36:29.400> how<00:36:29.880> to<00:36:30.180> uh<00:36:30.660> deploy 00:36:31.069 --> 00:36:31.079 align:start position:0% don't have to know how to uh deploy 00:36:31.079 --> 00:36:33.230 align:start position:0% don't have to know how to uh deploy something<00:36:31.560> Docker<00:36:32.220> all<00:36:32.400> the<00:36:32.579> proper<00:36:32.820> Docker 00:36:33.230 --> 00:36:33.240 align:start position:0% something Docker all the proper Docker 00:36:33.240 --> 00:36:35.870 align:start position:0% something Docker all the proper Docker configs<00:36:33.780> all<00:36:34.500> this<00:36:34.619> stuff<00:36:34.859> you<00:36:35.460> just<00:36:35.579> simply 00:36:35.870 --> 00:36:35.880 align:start position:0% configs all this stuff you just simply 00:36:35.880 --> 00:36:38.150 align:start position:0% configs all this stuff you just simply need<00:36:36.240> to<00:36:36.359> be<00:36:36.480> able<00:36:36.720> to<00:36:36.839> understand<00:36:37.680> a 00:36:38.150 --> 00:36:38.160 align:start position:0% need to be able to understand a 00:36:38.160 --> 00:36:41.390 align:start position:0% need to be able to understand a typescript<00:36:38.640> API<00:36:39.119> which<00:36:39.599> typescript<00:36:40.260> is<00:36:40.980> you 00:36:41.390 --> 00:36:41.400 align:start position:0% typescript API which typescript is you 00:36:41.400 --> 00:36:43.550 align:start position:0% typescript API which typescript is you know<00:36:41.460> amazing<00:36:41.880> for<00:36:42.540> uh<00:36:43.200> application 00:36:43.550 --> 00:36:43.560 align:start position:0% know amazing for uh application 00:36:43.560 --> 00:36:46.010 align:start position:0% know amazing for uh application development<00:36:44.099> and<00:36:45.060> you<00:36:45.359> can<00:36:45.480> be<00:36:45.599> Off<00:36:45.780> to<00:36:45.960> the 00:36:46.010 --> 00:36:46.020 align:start position:0% development and you can be Off to the 00:36:46.020 --> 00:36:49.069 align:start position:0% development and you can be Off to the Races<00:36:46.380> to<00:36:46.560> develop<00:36:46.920> your<00:36:47.160> own<00:36:47.280> software<00:36:48.079> uh 00:36:49.069 --> 00:36:49.079 align:start position:0% Races to develop your own software uh 00:36:49.079 --> 00:36:52.310 align:start position:0% Races to develop your own software uh you<00:36:49.740> are<00:36:49.920> able<00:36:50.220> to<00:36:50.540> programmatically<00:36:51.540> deploy 00:36:52.310 --> 00:36:52.320 align:start position:0% you are able to programmatically deploy 00:36:52.320 --> 00:36:54.829 align:start position:0% you are able to programmatically deploy those<00:36:52.619> and<00:36:53.099> upgrade<00:36:53.520> them<00:36:53.700> to<00:36:53.940> validators<00:36:54.359> so 00:36:54.829 --> 00:36:54.839 align:start position:0% those and upgrade them to validators so 00:36:54.839 --> 00:36:56.089 align:start position:0% those and upgrade them to validators so one<00:36:55.260> of<00:36:55.380> the<00:36:55.440> and<00:36:55.740> what<00:36:55.920> does 00:36:56.089 --> 00:36:56.099 align:start position:0% one of the and what does 00:36:56.099 --> 00:36:59.150 align:start position:0% one of the and what does programmatically<00:36:56.760> mean<00:36:57.359> here<00:36:57.720> in<00:36:58.560> this<00:36:58.859> case 00:36:59.150 --> 00:36:59.160 align:start position:0% programmatically mean here in this case 00:36:59.160 --> 00:37:01.430 align:start position:0% programmatically mean here in this case uh<00:36:59.940> like<00:37:00.060> with<00:37:00.300> the<00:37:00.480> other<00:37:00.599> platforms<00:37:01.140> that<00:37:01.320> we 00:37:01.430 --> 00:37:01.440 align:start position:0% uh like with the other platforms that we 00:37:01.440 --> 00:37:04.430 align:start position:0% uh like with the other platforms that we showed<00:37:02.280> there's<00:37:03.000> there's<00:37:03.359> there's<00:37:03.480> manual 00:37:04.430 --> 00:37:04.440 align:start position:0% showed there's there's there's manual 00:37:04.440 --> 00:37:06.650 align:start position:0% showed there's there's there's manual steps<00:37:04.800> that<00:37:04.980> you<00:37:05.099> have<00:37:05.220> to<00:37:05.339> take<00:37:05.460> in<00:37:05.880> the<00:37:06.060> uh<00:37:06.480> in 00:37:06.650 --> 00:37:06.660 align:start position:0% steps that you have to take in the uh in 00:37:06.660 --> 00:37:08.270 align:start position:0% steps that you have to take in the uh in the<00:37:06.780> process<00:37:07.020> you<00:37:07.260> either<00:37:07.440> have<00:37:07.680> to<00:37:07.800> copy<00:37:08.099> a 00:37:08.270 --> 00:37:08.280 align:start position:0% the process you either have to copy a 00:37:08.280 --> 00:37:11.930 align:start position:0% the process you either have to copy a file<00:37:08.460> over<00:37:08.700> here<00:37:09.000> you<00:37:09.420> have<00:37:09.599> to<00:37:09.960> uh<00:37:10.920> you<00:37:11.760> have 00:37:11.930 --> 00:37:11.940 align:start position:0% file over here you have to uh you have 00:37:11.940 --> 00:37:13.609 align:start position:0% file over here you have to uh you have to<00:37:12.060> say<00:37:12.180> this<00:37:12.480> you<00:37:12.720> have<00:37:12.839> to<00:37:12.960> do<00:37:13.079> you<00:37:13.380> know<00:37:13.440> so 00:37:13.609 --> 00:37:13.619 align:start position:0% to say this you have to do you know so 00:37:13.619 --> 00:37:16.010 align:start position:0% to say this you have to do you know so there's<00:37:13.859> uh<00:37:14.460> in<00:37:14.700> the<00:37:14.820> process<00:37:15.240> of<00:37:15.599> deploying<00:37:15.960> a 00:37:16.010 --> 00:37:16.020 align:start position:0% there's uh in the process of deploying a 00:37:16.020 --> 00:37:17.630 align:start position:0% there's uh in the process of deploying a node<00:37:16.200> with<00:37:16.380> those<00:37:16.560> other<00:37:16.740> software<00:37:17.160> platforms 00:37:17.630 --> 00:37:17.640 align:start position:0% node with those other software platforms 00:37:17.640 --> 00:37:19.550 align:start position:0% node with those other software platforms there's<00:37:18.180> certain<00:37:18.420> processes<00:37:19.079> that<00:37:19.320> require 00:37:19.550 --> 00:37:19.560 align:start position:0% there's certain processes that require 00:37:19.560 --> 00:37:21.770 align:start position:0% there's certain processes that require human<00:37:19.920> intervention<00:37:20.780> programmatically 00:37:21.770 --> 00:37:21.780 align:start position:0% human intervention programmatically 00:37:21.780 --> 00:37:23.690 align:start position:0% human intervention programmatically means<00:37:22.380> you're<00:37:22.500> able<00:37:22.800> to<00:37:22.859> do<00:37:23.040> this<00:37:23.220> entirely 00:37:23.690 --> 00:37:23.700 align:start position:0% means you're able to do this entirely 00:37:23.700 --> 00:37:25.370 align:start position:0% means you're able to do this entirely through<00:37:24.119> programs<00:37:24.660> so<00:37:24.900> you<00:37:25.140> can<00:37:25.200> actually 00:37:25.370 --> 00:37:25.380 align:start position:0% through programs so you can actually 00:37:25.380 --> 00:37:27.170 align:start position:0% through programs so you can actually have<00:37:25.740> all<00:37:26.040> the<00:37:26.160> elements<00:37:26.520> that<00:37:26.700> would<00:37:26.940> require 00:37:27.170 --> 00:37:27.180 align:start position:0% have all the elements that would require 00:37:27.180 --> 00:37:30.589 align:start position:0% have all the elements that would require you<00:37:28.140> know<00:37:28.260> a<00:37:28.619> human<00:37:28.920> to<00:37:29.160> copy<00:37:30.060> this<00:37:30.180> over<00:37:30.359> here 00:37:30.589 --> 00:37:30.599 align:start position:0% you know a human to copy this over here 00:37:30.599 --> 00:37:32.569 align:start position:0% you know a human to copy this over here to<00:37:30.900> do<00:37:31.020> this<00:37:31.200> over<00:37:31.380> here<00:37:31.619> you<00:37:32.040> can<00:37:32.160> have<00:37:32.339> that 00:37:32.569 --> 00:37:32.579 align:start position:0% to do this over here you can have that 00:37:32.579 --> 00:37:35.390 align:start position:0% to do this over here you can have that all<00:37:32.820> done<00:37:33.060> in<00:37:33.480> a<00:37:33.599> programmatic<00:37:34.200> way<00:37:34.320> so<00:37:34.920> it 00:37:35.390 --> 00:37:35.400 align:start position:0% all done in a programmatic way so it 00:37:35.400 --> 00:37:38.150 align:start position:0% all done in a programmatic way so it creates<00:37:35.640> a<00:37:35.820> much<00:37:36.180> more<00:37:36.480> seamless<00:37:37.020> uh<00:37:37.740> user 00:37:38.150 --> 00:37:38.160 align:start position:0% creates a much more seamless uh user 00:37:38.160 --> 00:37:39.650 align:start position:0% creates a much more seamless uh user experience<00:37:38.460> and<00:37:38.820> you<00:37:39.000> have<00:37:39.180> way<00:37:39.300> more<00:37:39.480> control 00:37:39.650 --> 00:37:39.660 align:start position:0% experience and you have way more control 00:37:39.660 --> 00:37:40.970 align:start position:0% experience and you have way more control over<00:37:39.960> the<00:37:40.200> nodes<00:37:40.440> and<00:37:40.680> how<00:37:40.859> they're 00:37:40.970 --> 00:37:40.980 align:start position:0% over the nodes and how they're 00:37:40.980 --> 00:37:42.349 align:start position:0% over the nodes and how they're configured<00:37:41.460> because<00:37:41.880> it's<00:37:42.180> all 00:37:42.349 --> 00:37:42.359 align:start position:0% configured because it's all 00:37:42.359 --> 00:37:44.390 align:start position:0% configured because it's all programmatically<00:37:43.079> designed<00:37:43.619> you<00:37:44.280> have 00:37:44.390 --> 00:37:44.400 align:start position:0% programmatically designed you have 00:37:44.400 --> 00:37:47.089 align:start position:0% programmatically designed you have seamless<00:37:44.760> client<00:37:45.000> updates<00:37:45.500> uh<00:37:46.500> with<00:37:46.859> no 00:37:47.089 --> 00:37:47.099 align:start position:0% seamless client updates uh with no 00:37:47.099 --> 00:37:50.810 align:start position:0% seamless client updates uh with no launcher<00:37:47.640> if<00:37:48.240> there's<00:37:48.660> a<00:37:48.839> new<00:37:49.020> client<00:37:49.320> we<00:37:50.280> uh 00:37:50.810 --> 00:37:50.820 align:start position:0% launcher if there's a new client we uh 00:37:50.820 --> 00:37:52.609 align:start position:0% launcher if there's a new client we uh uh<00:37:51.060> and<00:37:51.240> it's<00:37:51.480> actually<00:37:51.599> ties<00:37:52.020> in<00:37:52.200> with<00:37:52.440> this 00:37:52.609 --> 00:37:52.619 align:start position:0% uh and it's actually ties in with this 00:37:52.619 --> 00:37:54.410 align:start position:0% uh and it's actually ties in with this point<00:37:52.920> down<00:37:53.160> here<00:37:53.400> we<00:37:53.700> have<00:37:53.880> a<00:37:53.940> client<00:37:54.180> test 00:37:54.410 --> 00:37:54.420 align:start position:0% point down here we have a client test 00:37:54.420 --> 00:37:57.470 align:start position:0% point down here we have a client test Suite<00:37:54.780> so<00:37:54.960> I'll<00:37:55.200> kind<00:37:55.500> of<00:37:55.560> tackle<00:37:56.400> these<00:37:56.640> in<00:37:57.300> a 00:37:57.470 --> 00:37:57.480 align:start position:0% Suite so I'll kind of tackle these in a 00:37:57.480 --> 00:37:59.450 align:start position:0% Suite so I'll kind of tackle these in a scenario<00:37:58.140> that's<00:37:58.380> happened<00:37:58.560> recently<00:37:59.040> where 00:37:59.450 --> 00:37:59.460 align:start position:0% scenario that's happened recently where 00:37:59.460 --> 00:38:01.670 align:start position:0% scenario that's happened recently where we<00:37:59.880> have<00:38:00.000> a<00:38:00.180> client<00:38:00.420> test<00:38:00.720> Suite<00:38:01.079> where<00:38:01.320> when<00:38:01.560> a 00:38:01.670 --> 00:38:01.680 align:start position:0% we have a client test Suite where when a 00:38:01.680 --> 00:38:03.650 align:start position:0% we have a client test Suite where when a new<00:38:01.800> client<00:38:01.920> comes<00:38:02.220> out<00:38:02.640> we're<00:38:03.000> able<00:38:03.300> to<00:38:03.420> test 00:38:03.650 --> 00:38:03.660 align:start position:0% new client comes out we're able to test 00:38:03.660 --> 00:38:06.290 align:start position:0% new client comes out we're able to test it<00:38:03.900> uh<00:38:04.859> against<00:38:05.099> this<00:38:05.339> library<00:38:05.640> to<00:38:05.940> make<00:38:06.180> sure 00:38:06.290 --> 00:38:06.300 align:start position:0% it uh against this library to make sure 00:38:06.300 --> 00:38:08.329 align:start position:0% it uh against this library to make sure that<00:38:06.720> nothing<00:38:07.079> breaks<00:38:07.560> inside<00:38:07.920> of<00:38:08.220> this 00:38:08.329 --> 00:38:08.339 align:start position:0% that nothing breaks inside of this 00:38:08.339 --> 00:38:12.109 align:start position:0% that nothing breaks inside of this Library<00:38:08.780> uh<00:38:09.780> which<00:38:10.320> no<00:38:10.800> applications<00:38:11.640> can<00:38:11.940> use 00:38:12.109 --> 00:38:12.119 align:start position:0% Library uh which no applications can use 00:38:12.119 --> 00:38:16.190 align:start position:0% Library uh which no applications can use well<00:38:12.780> uh<00:38:13.440> earlier<00:38:13.859> this<00:38:14.099> year<00:38:14.480> uh<00:38:15.480> the<00:38:15.720> gaffe 00:38:16.190 --> 00:38:16.200 align:start position:0% well uh earlier this year uh the gaffe 00:38:16.200 --> 00:38:19.010 align:start position:0% well uh earlier this year uh the gaffe uh<00:38:16.680> death<00:38:16.920> notes<00:38:17.400> came<00:38:17.640> out<00:38:17.820> with<00:38:18.180> uh<00:38:18.720> a<00:38:18.900> new 00:38:19.010 --> 00:38:19.020 align:start position:0% uh death notes came out with uh a new 00:38:19.020 --> 00:38:22.430 align:start position:0% uh death notes came out with uh a new version<00:38:19.200> that<00:38:20.040> actually<00:38:20.280> Sunset<00:38:21.060> a<00:38:21.900> uh<00:38:22.260> a 00:38:22.430 --> 00:38:22.440 align:start position:0% version that actually Sunset a uh a 00:38:22.440 --> 00:38:24.950 align:start position:0% version that actually Sunset a uh a configuration<00:38:22.940> uh<00:38:23.940> and<00:38:24.240> it<00:38:24.420> wasn't<00:38:24.660> like 00:38:24.950 --> 00:38:24.960 align:start position:0% configuration uh and it wasn't like 00:38:24.960 --> 00:38:26.690 align:start position:0% configuration uh and it wasn't like widely<00:38:25.440> used<00:38:25.619> but<00:38:25.800> it<00:38:25.980> was<00:38:26.099> a<00:38:26.220> configuration 00:38:26.690 --> 00:38:26.700 align:start position:0% widely used but it was a configuration 00:38:26.700 --> 00:38:28.730 align:start position:0% widely used but it was a configuration in<00:38:27.000> there<00:38:27.119> but<00:38:27.300> it<00:38:27.480> wasn't<00:38:27.660> in<00:38:27.839> the<00:38:28.020> recent<00:38:28.380> so 00:38:28.730 --> 00:38:28.740 align:start position:0% in there but it wasn't in the recent so 00:38:28.740 --> 00:38:31.069 align:start position:0% in there but it wasn't in the recent so we<00:38:28.920> actually<00:38:29.099> put<00:38:29.520> it<00:38:29.640> through<00:38:29.880> our<00:38:30.180> testing 00:38:31.069 --> 00:38:31.079 align:start position:0% we actually put it through our testing 00:38:31.079 --> 00:38:33.650 align:start position:0% we actually put it through our testing or<00:38:31.440> our<00:38:31.619> test<00:38:32.040> suite<00:38:32.400> and<00:38:32.940> we<00:38:33.119> realized<00:38:33.420> we 00:38:33.650 --> 00:38:33.660 align:start position:0% or our test suite and we realized we 00:38:33.660 --> 00:38:35.450 align:start position:0% or our test suite and we realized we were<00:38:33.780> getting<00:38:33.900> all<00:38:34.020> these<00:38:34.200> flags<00:38:34.740> we<00:38:35.099> reached 00:38:35.450 --> 00:38:35.460 align:start position:0% were getting all these flags we reached 00:38:35.460 --> 00:38:37.190 align:start position:0% were getting all these flags we reached out<00:38:35.520> to<00:38:35.640> them<00:38:35.700> like<00:38:35.880> oh<00:38:36.000> yeah<00:38:36.180> they<00:38:36.540> uh<00:38:36.900> uh 00:38:37.190 --> 00:38:37.200 align:start position:0% out to them like oh yeah they uh uh 00:38:37.200 --> 00:38:38.930 align:start position:0% out to them like oh yeah they uh uh we're<00:38:37.440> you<00:38:37.740> know<00:38:37.859> sunsetting<00:38:38.400> this<00:38:38.520> you<00:38:38.820> know 00:38:38.930 --> 00:38:38.940 align:start position:0% we're you know sunsetting this you know 00:38:38.940 --> 00:38:40.430 align:start position:0% we're you know sunsetting this you know but<00:38:39.060> it<00:38:39.240> wasn't<00:38:39.359> in<00:38:39.599> the<00:38:39.720> release<00:38:39.839> though<00:38:40.079> so 00:38:40.430 --> 00:38:40.440 align:start position:0% but it wasn't in the release though so 00:38:40.440 --> 00:38:42.650 align:start position:0% but it wasn't in the release though so there's<00:38:40.859> there's<00:38:41.040> elements<00:38:41.940> to<00:38:42.180> where<00:38:42.359> you 00:38:42.650 --> 00:38:42.660 align:start position:0% there's there's elements to where you 00:38:42.660 --> 00:38:44.450 align:start position:0% there's there's elements to where you know<00:38:42.720> even<00:38:42.960> on<00:38:43.260> the<00:38:43.440> client<00:38:43.680> side<00:38:43.920> they<00:38:44.280> can 00:38:44.450 --> 00:38:44.460 align:start position:0% know even on the client side they can 00:38:44.460 --> 00:38:46.550 align:start position:0% know even on the client side they can just<00:38:44.579> make<00:38:44.820> an<00:38:45.060> update<00:38:45.359> to<00:38:45.660> something<00:38:45.900> not 00:38:46.550 --> 00:38:46.560 align:start position:0% just make an update to something not 00:38:46.560 --> 00:38:48.829 align:start position:0% just make an update to something not realizing<00:38:47.280> that<00:38:47.940> other<00:38:48.180> people<00:38:48.420> might<00:38:48.660> be 00:38:48.829 --> 00:38:48.839 align:start position:0% realizing that other people might be 00:38:48.839 --> 00:38:50.870 align:start position:0% realizing that other people might be using<00:38:49.200> different<00:38:49.440> configurations<00:38:50.099> that 00:38:50.870 --> 00:38:50.880 align:start position:0% using different configurations that 00:38:50.880 --> 00:38:52.609 align:start position:0% using different configurations that would<00:38:51.119> affect<00:38:51.480> that<00:38:51.660> this<00:38:52.079> is<00:38:52.200> where<00:38:52.380> no 00:38:52.609 --> 00:38:52.619 align:start position:0% would affect that this is where no 00:38:52.619 --> 00:38:55.069 align:start position:0% would affect that this is where no launcher<00:38:53.099> comes<00:38:53.460> in<00:38:53.520> by<00:38:54.000> uh<00:38:54.599> this<00:38:54.839> can 00:38:55.069 --> 00:38:55.079 align:start position:0% launcher comes in by uh this can 00:38:55.079 --> 00:38:58.069 align:start position:0% launcher comes in by uh this can actually<00:38:55.200> eliminate<00:38:55.920> so<00:38:56.400> uh<00:38:57.119> eliminate<00:38:57.780> that 00:38:58.069 --> 00:38:58.079 align:start position:0% actually eliminate so uh eliminate that 00:38:58.079 --> 00:39:00.829 align:start position:0% actually eliminate so uh eliminate that attack<00:38:58.800> vector<00:38:59.280> or<00:38:59.820> not<00:39:00.240> necessarily<00:39:00.480> tactic 00:39:00.829 --> 00:39:00.839 align:start position:0% attack vector or not necessarily tactic 00:39:00.839 --> 00:39:02.870 align:start position:0% attack vector or not necessarily tactic but<00:39:01.079> that<00:39:01.260> slash<00:39:01.619> event<00:39:01.800> where<00:39:02.160> where<00:39:02.640> if 00:39:02.870 --> 00:39:02.880 align:start position:0% but that slash event where where if 00:39:02.880 --> 00:39:04.490 align:start position:0% but that slash event where where if there's<00:39:03.060> a<00:39:03.300> problem<00:39:03.480> with<00:39:03.720> death<00:39:03.960> and<00:39:04.320> there's 00:39:04.490 --> 00:39:04.500 align:start position:0% there's a problem with death and there's 00:39:04.500 --> 00:39:06.770 align:start position:0% there's a problem with death and there's a<00:39:04.859> uh<00:39:05.160> a<00:39:05.400> feature<00:39:05.820> that<00:39:05.940> people<00:39:06.060> are<00:39:06.300> requiring 00:39:06.770 --> 00:39:06.780 align:start position:0% a uh a feature that people are requiring 00:39:06.780 --> 00:39:09.050 align:start position:0% a uh a feature that people are requiring and<00:39:07.380> that's<00:39:07.619> suddenly<00:39:08.040> taken<00:39:08.339> away<00:39:08.520> and<00:39:08.820> it's 00:39:09.050 --> 00:39:09.060 align:start position:0% and that's suddenly taken away and it's 00:39:09.060 --> 00:39:11.870 align:start position:0% and that's suddenly taken away and it's not<00:39:09.240> realized<00:39:09.599> how<00:39:09.900> widely<00:39:10.260> it's<00:39:10.500> used<00:39:10.740> uh<00:39:11.700> no 00:39:11.870 --> 00:39:11.880 align:start position:0% not realized how widely it's used uh no 00:39:11.880 --> 00:39:13.790 align:start position:0% not realized how widely it's used uh no one<00:39:12.060> should<00:39:12.240> catch<00:39:12.720> that<00:39:12.839> before<00:39:13.200> the<00:39:13.440> upgrade 00:39:13.790 --> 00:39:13.800 align:start position:0% one should catch that before the upgrade 00:39:13.800 --> 00:39:16.910 align:start position:0% one should catch that before the upgrade happens<00:39:14.040> so<00:39:14.640> that's<00:39:14.940> the<00:39:15.240> advantage<00:39:15.660> of<00:39:16.200> uh 00:39:16.910 --> 00:39:16.920 align:start position:0% happens so that's the advantage of uh 00:39:16.920 --> 00:39:20.210 align:start position:0% happens so that's the advantage of uh some<00:39:17.339> of<00:39:17.700> thinking<00:39:18.440> thinking<00:39:19.440> uh 00:39:20.210 --> 00:39:20.220 align:start position:0% some of thinking thinking uh 00:39:20.220 --> 00:39:22.790 align:start position:0% some of thinking thinking uh holistically<00:39:20.820> about<00:39:21.359> the<00:39:21.720> back<00:39:21.960> end<00:39:22.140> of 00:39:22.790 --> 00:39:22.800 align:start position:0% holistically about the back end of 00:39:22.800 --> 00:39:24.410 align:start position:0% holistically about the back end of running<00:39:23.099> notes 00:39:24.410 --> 00:39:24.420 align:start position:0% running notes 00:39:24.420 --> 00:39:26.990 align:start position:0% running notes so<00:39:24.660> this<00:39:25.020> is<00:39:25.200> an<00:39:25.320> example<00:39:25.619> of<00:39:25.980> what<00:39:26.400> a<00:39:26.700> simple 00:39:26.990 --> 00:39:27.000 align:start position:0% so this is an example of what a simple 00:39:27.000 --> 00:39:28.910 align:start position:0% so this is an example of what a simple API<00:39:27.420> could<00:39:27.660> look<00:39:27.839> like<00:39:27.960> so<00:39:28.140> for<00:39:28.380> for 00:39:28.910 --> 00:39:28.920 align:start position:0% API could look like so for for 00:39:28.920 --> 00:39:31.190 align:start position:0% API could look like so for for application<00:39:29.640> developers<00:39:30.180> this<00:39:30.780> is<00:39:30.839> what<00:39:31.079> you 00:39:31.190 --> 00:39:31.200 align:start position:0% application developers this is what you 00:39:31.200 --> 00:39:35.329 align:start position:0% application developers this is what you need<00:39:31.520> to<00:39:32.520> allow<00:39:33.240> your<00:39:33.720> application<00:39:34.200> to<00:39:34.859> deploy 00:39:35.329 --> 00:39:35.339 align:start position:0% need to allow your application to deploy 00:39:35.339 --> 00:39:37.609 align:start position:0% need to allow your application to deploy a<00:39:36.119> ethereum<00:39:36.660> evaluator 00:39:37.609 --> 00:39:37.619 align:start position:0% a ethereum evaluator 00:39:37.619 --> 00:39:39.829 align:start position:0% a ethereum evaluator for<00:39:38.099> the<00:39:38.339> developers<00:39:38.700> out<00:39:38.880> there<00:39:39.060> this<00:39:39.720> is 00:39:39.829 --> 00:39:39.839 align:start position:0% for the developers out there this is 00:39:39.839 --> 00:39:42.290 align:start position:0% for the developers out there this is simple<00:39:40.079> this<00:39:40.920> is<00:39:41.099> super<00:39:41.460> simple<00:39:41.700> you're<00:39:42.180> not 00:39:42.290 --> 00:39:42.300 align:start position:0% simple this is super simple you're not 00:39:42.300 --> 00:39:43.910 align:start position:0% simple this is super simple you're not having<00:39:42.480> to<00:39:42.599> touch<00:39:42.780> Docker<00:39:43.320> you're<00:39:43.619> not<00:39:43.740> having 00:39:43.910 --> 00:39:43.920 align:start position:0% having to touch Docker you're not having 00:39:43.920 --> 00:39:46.430 align:start position:0% having to touch Docker you're not having to<00:39:44.099> touch<00:39:44.280> anything<00:39:44.640> on<00:39:45.000> the<00:39:45.119> system<00:39:45.440> the 00:39:46.430 --> 00:39:46.440 align:start position:0% to touch anything on the system the 00:39:46.440 --> 00:39:48.589 align:start position:0% to touch anything on the system the library<00:39:46.740> itself<00:39:47.280> is<00:39:47.520> doing<00:39:47.760> everything<00:39:48.300> for 00:39:48.589 --> 00:39:48.599 align:start position:0% library itself is doing everything for 00:39:48.599 --> 00:39:50.630 align:start position:0% library itself is doing everything for you<00:39:48.720> in<00:39:48.839> the<00:39:49.020> back<00:39:49.140> end<00:39:49.260> with<00:39:49.980> best<00:39:50.280> practices 00:39:50.630 --> 00:39:50.640 align:start position:0% you in the back end with best practices 00:39:50.640 --> 00:39:52.250 align:start position:0% you in the back end with best practices and<00:39:51.060> this<00:39:51.300> is<00:39:51.420> all<00:39:51.540> you<00:39:51.660> have<00:39:51.780> to<00:39:51.900> add<00:39:51.960> to<00:39:52.140> your 00:39:52.250 --> 00:39:52.260 align:start position:0% and this is all you have to add to your 00:39:52.260 --> 00:39:54.650 align:start position:0% and this is all you have to add to your application 00:39:54.650 --> 00:39:54.660 align:start position:0% 00:39:54.660 --> 00:39:58.490 align:start position:0% so<00:39:55.200> no<00:39:55.800> launcher<00:39:56.400> is<00:39:56.820> it<00:39:57.119> in<00:39:57.240> use<00:39:57.420> yes<00:39:57.900> it<00:39:58.140> is<00:39:58.260> no 00:39:58.490 --> 00:39:58.500 align:start position:0% so no launcher is it in use yes it is no 00:39:58.500 --> 00:40:00.829 align:start position:0% so no launcher is it in use yes it is no launcher's<00:39:59.160> been<00:39:59.280> in<00:39:59.460> uh<00:39:59.880> well<00:40:00.060> battle<00:40:00.300> tested 00:40:00.829 --> 00:40:00.839 align:start position:0% launcher's been in uh well battle tested 00:40:00.839 --> 00:40:04.250 align:start position:0% launcher's been in uh well battle tested through<00:40:01.200> node<00:40:01.560> pilot<00:40:01.980> no<00:40:02.160> pilot<00:40:02.760> is<00:40:03.420> a<00:40:03.900> uh 00:40:04.250 --> 00:40:04.260 align:start position:0% through node pilot no pilot is a uh 00:40:04.260 --> 00:40:07.370 align:start position:0% through node pilot no pilot is a uh consumer-facing<00:40:05.300> node<00:40:06.300> management<00:40:06.660> software 00:40:07.370 --> 00:40:07.380 align:start position:0% consumer-facing node management software 00:40:07.380 --> 00:40:09.829 align:start position:0% consumer-facing node management software that<00:40:08.339> uh<00:40:08.640> we've<00:40:08.880> been<00:40:09.000> developing<00:40:09.480> we're 00:40:09.829 --> 00:40:09.839 align:start position:0% that uh we've been developing we're 00:40:09.839 --> 00:40:11.270 align:start position:0% that uh we've been developing we're currently<00:40:10.140> in<00:40:10.320> beta<00:40:10.680> we're<00:40:10.859> hoping<00:40:11.040> to<00:40:11.160> come 00:40:11.270 --> 00:40:11.280 align:start position:0% currently in beta we're hoping to come 00:40:11.280 --> 00:40:14.750 align:start position:0% currently in beta we're hoping to come out<00:40:11.460> with<00:40:11.579> version<00:40:11.760> one<00:40:12.320> uh<00:40:13.320> q1<00:40:14.040> the<00:40:14.339> next<00:40:14.460> year 00:40:14.750 --> 00:40:14.760 align:start position:0% out with version one uh q1 the next year 00:40:14.760 --> 00:40:17.870 align:start position:0% out with version one uh q1 the next year uh<00:40:15.480> and<00:40:15.599> make<00:40:15.780> it<00:40:15.900> fully<00:40:16.140> open<00:40:16.260> source<00:40:16.740> uh<00:40:17.520> so 00:40:17.870 --> 00:40:17.880 align:start position:0% uh and make it fully open source uh so 00:40:17.880 --> 00:40:19.730 align:start position:0% uh and make it fully open source uh so far<00:40:18.060> thousands<00:40:18.540> of<00:40:18.660> notes<00:40:19.020> and<00:40:19.260> validators 00:40:19.730 --> 00:40:19.740 align:start position:0% far thousands of notes and validators 00:40:19.740 --> 00:40:21.710 align:start position:0% far thousands of notes and validators have<00:40:19.980> been<00:40:20.160> actually<00:40:20.400> launched<00:40:20.880> through<00:40:21.300> node 00:40:21.710 --> 00:40:21.720 align:start position:0% have been actually launched through node 00:40:21.720 --> 00:40:24.710 align:start position:0% have been actually launched through node pilot<00:40:22.079> so<00:40:22.619> it's<00:40:22.740> been<00:40:23.040> heavily<00:40:23.579> used 00:40:24.710 --> 00:40:24.720 align:start position:0% pilot so it's been heavily used 00:40:24.720 --> 00:40:27.349 align:start position:0% pilot so it's been heavily used um<00:40:24.780> uh<00:40:25.740> it<00:40:25.980> started<00:40:26.520> off<00:40:26.640> primarily<00:40:27.119> in 00:40:27.349 --> 00:40:27.359 align:start position:0% um uh it started off primarily in 00:40:27.359 --> 00:40:29.750 align:start position:0% um uh it started off primarily in another<00:40:27.480> network<00:40:27.900> uh<00:40:28.500> pocket<00:40:28.859> network<00:40:28.980> uh 00:40:29.750 --> 00:40:29.760 align:start position:0% another network uh pocket network uh 00:40:29.760 --> 00:40:33.349 align:start position:0% another network uh pocket network uh which<00:40:30.000> actually<00:40:30.180> serves<00:40:30.720> uh<00:40:31.619> RPC<00:40:32.220> calls<00:40:33.000> to 00:40:33.349 --> 00:40:33.359 align:start position:0% which actually serves uh RPC calls to 00:40:33.359 --> 00:40:35.270 align:start position:0% which actually serves uh RPC calls to ethereum<00:40:33.960> application<00:40:34.440> so<00:40:34.740> it's<00:40:34.859> really<00:40:35.099> cool 00:40:35.270 --> 00:40:35.280 align:start position:0% ethereum application so it's really cool 00:40:35.280 --> 00:40:48.550 align:start position:0% ethereum application so it's really cool uh<00:40:35.880> it's<00:40:36.060> really<00:40:36.300> cool<00:40:36.540> Synergy<00:40:37.200> there<00:40:37.440> but<00:40:38.040> uh 00:40:48.550 --> 00:40:48.560 align:start position:0% 00:40:48.560 --> 00:40:50.750 align:start position:0% so<00:40:49.560> we're<00:40:49.740> talking<00:40:49.980> about<00:40:50.099> like<00:40:50.400> a<00:40:50.579> web 00:40:50.750 --> 00:40:50.760 align:start position:0% so we're talking about like a web 00:40:50.760 --> 00:40:52.910 align:start position:0% so we're talking about like a web application<00:40:51.300> but<00:40:51.960> again<00:40:52.140> it's<00:40:52.320> able<00:40:52.619> to<00:40:52.740> run 00:40:52.910 --> 00:40:52.920 align:start position:0% application but again it's able to run 00:40:52.920 --> 00:40:55.550 align:start position:0% application but again it's able to run and<00:40:53.400> then<00:40:53.579> deploy<00:40:53.940> nodes<00:40:54.599> and<00:40:54.839> create<00:40:55.020> a<00:40:55.200> user 00:40:55.550 --> 00:40:55.560 align:start position:0% and then deploy nodes and create a user 00:40:55.560 --> 00:40:57.770 align:start position:0% and then deploy nodes and create a user interface<00:40:55.980> and<00:40:56.220> a<00:40:56.400> user<00:40:56.700> experience<00:40:57.060> that 00:40:57.770 --> 00:40:57.780 align:start position:0% interface and a user experience that 00:40:57.780 --> 00:41:00.530 align:start position:0% interface and a user experience that allows<00:40:58.260> more<00:40:58.859> people<00:40:59.099> to<00:40:59.400> have<00:40:59.520> access<00:40:59.760> to 00:41:00.530 --> 00:41:00.540 align:start position:0% allows more people to have access to 00:41:00.540 --> 00:41:02.210 align:start position:0% allows more people to have access to note<00:41:00.900> running<00:41:01.140> and<00:41:01.619> it's<00:41:01.800> just<00:41:01.920> a<00:41:02.040> simple 00:41:02.210 --> 00:41:02.220 align:start position:0% note running and it's just a simple 00:41:02.220 --> 00:41:04.910 align:start position:0% note running and it's just a simple application<00:41:02.960> ultimately<00:41:03.960> with<00:41:04.619> node 00:41:04.910 --> 00:41:04.920 align:start position:0% application ultimately with node 00:41:04.920 --> 00:41:06.470 align:start position:0% application ultimately with node launcher<00:41:05.280> any<00:41:05.579> developer<00:41:06.060> can<00:41:06.240> start 00:41:06.470 --> 00:41:06.480 align:start position:0% launcher any developer can start 00:41:06.480 --> 00:41:09.050 align:start position:0% launcher any developer can start creating<00:41:06.900> no<00:41:07.260> deployment<00:41:07.740> applications<00:41:08.339> like 00:41:09.050 --> 00:41:09.060 align:start position:0% creating no deployment applications like 00:41:09.060 --> 00:41:12.650 align:start position:0% creating no deployment applications like node<00:41:09.540> pilot<00:41:10.380> we<00:41:11.040> want<00:41:11.220> to<00:41:11.400> open<00:41:11.700> up<00:41:12.119> this<00:41:12.359> space 00:41:12.650 --> 00:41:12.660 align:start position:0% node pilot we want to open up this space 00:41:12.660 --> 00:41:15.170 align:start position:0% node pilot we want to open up this space so<00:41:13.320> that<00:41:13.680> there's<00:41:13.920> Innovation<00:41:14.400> happening<00:41:14.880> on 00:41:15.170 --> 00:41:15.180 align:start position:0% so that there's Innovation happening on 00:41:15.180 --> 00:41:18.770 align:start position:0% so that there's Innovation happening on the<00:41:15.359> user<00:41:15.780> side<00:41:16.020> of<00:41:16.740> node<00:41:17.300> uh<00:41:18.300> software 00:41:18.770 --> 00:41:18.780 align:start position:0% the user side of node uh software 00:41:18.780 --> 00:41:20.930 align:start position:0% the user side of node uh software because<00:41:19.380> we<00:41:19.859> want<00:41:19.980> more<00:41:20.160> and<00:41:20.339> more<00:41:20.520> users<00:41:20.820> to 00:41:20.930 --> 00:41:20.940 align:start position:0% because we want more and more users to 00:41:20.940 --> 00:41:23.030 align:start position:0% because we want more and more users to be<00:41:21.060> attracted<00:41:21.420> to<00:41:21.599> the<00:41:21.720> space<00:41:21.900> and<00:41:22.500> more<00:41:22.740> users 00:41:23.030 --> 00:41:23.040 align:start position:0% be attracted to the space and more users 00:41:23.040 --> 00:41:25.069 align:start position:0% be attracted to the space and more users can<00:41:23.220> be<00:41:23.339> attracted<00:41:23.700> to<00:41:23.820> the<00:41:23.940> space<00:41:24.180> when<00:41:24.900> we 00:41:25.069 --> 00:41:25.079 align:start position:0% can be attracted to the space when we 00:41:25.079 --> 00:41:27.470 align:start position:0% can be attracted to the space when we have<00:41:25.260> these<00:41:25.619> kind<00:41:25.859> of<00:41:26.040> uh<00:41:26.700> uh<00:41:26.760> when<00:41:27.119> we<00:41:27.300> have 00:41:27.470 --> 00:41:27.480 align:start position:0% have these kind of uh uh when we have 00:41:27.480 --> 00:41:29.030 align:start position:0% have these kind of uh uh when we have these<00:41:27.720> kind<00:41:27.839> of<00:41:27.960> software<00:41:28.320> that<00:41:28.859> meet 00:41:29.030 --> 00:41:29.040 align:start position:0% these kind of software that meet 00:41:29.040 --> 00:41:30.770 align:start position:0% these kind of software that meet different<00:41:29.339> users<00:41:29.760> with<00:41:30.000> where<00:41:30.240> they're<00:41:30.359> at<00:41:30.540> or 00:41:30.770 --> 00:41:30.780 align:start position:0% different users with where they're at or 00:41:30.780 --> 00:41:32.510 align:start position:0% different users with where they're at or the<00:41:31.020> features<00:41:31.320> that<00:41:31.440> they're<00:41:31.560> looking<00:41:31.800> for<00:41:31.920> we 00:41:32.510 --> 00:41:32.520 align:start position:0% the features that they're looking for we 00:41:32.520 --> 00:41:34.790 align:start position:0% the features that they're looking for we can<00:41:32.640> see<00:41:33.060> that<00:41:33.300> Innovation<00:41:33.780> start<00:41:34.380> to<00:41:34.560> grow 00:41:34.790 --> 00:41:34.800 align:start position:0% can see that Innovation start to grow 00:41:34.800 --> 00:41:46.930 align:start position:0% can see that Innovation start to grow with<00:41:35.400> tools<00:41:35.940> like<00:41:36.180> no<00:41:36.480> launcher 00:41:46.930 --> 00:41:46.940 align:start position:0% 00:41:46.940 --> 00:41:50.930 align:start position:0% using<00:41:47.940> entirely<00:41:48.480> uh<00:41:49.079> only<00:41:49.380> node<00:41:50.099> launcher<00:41:50.460> so 00:41:50.930 --> 00:41:50.940 align:start position:0% using entirely uh only node launcher so 00:41:50.940 --> 00:41:52.790 align:start position:0% using entirely uh only node launcher so we're<00:41:51.060> very<00:41:51.240> excited<00:41:51.540> about<00:41:51.660> that 00:41:52.790 --> 00:41:52.800 align:start position:0% we're very excited about that 00:41:52.800 --> 00:41:53.890 align:start position:0% we're very excited about that um 00:41:53.890 --> 00:41:53.900 align:start position:0% um 00:41:53.900 --> 00:41:56.030 align:start position:0% um we<00:41:54.900> were<00:41:55.020> in<00:41:55.140> the<00:41:55.260> middle<00:41:55.320> of<00:41:55.440> refactoring<00:41:55.920> I 00:41:56.030 --> 00:41:56.040 align:start position:0% we were in the middle of refactoring I 00:41:56.040 --> 00:41:57.770 align:start position:0% we were in the middle of refactoring I was<00:41:56.160> talking<00:41:56.280> to<00:41:56.400> the<00:41:56.520> dev<00:41:56.640> yesterday<00:41:56.940> uh<00:41:57.660> he's 00:41:57.770 --> 00:41:57.780 align:start position:0% was talking to the dev yesterday uh he's 00:41:57.780 --> 00:42:00.050 align:start position:0% was talking to the dev yesterday uh he's like<00:41:57.960> well<00:41:58.140> yeah<00:41:58.800> well<00:41:59.160> the<00:41:59.400> first<00:41:59.520> right<00:41:59.880> now 00:42:00.050 --> 00:42:00.060 align:start position:0% like well yeah well the first right now 00:42:00.060 --> 00:42:02.270 align:start position:0% like well yeah well the first right now uh<00:42:00.540> has<00:42:00.720> some<00:42:00.839> bugs<00:42:01.260> because<00:42:01.440> of<00:42:01.680> refactoring 00:42:02.270 --> 00:42:02.280 align:start position:0% uh has some bugs because of refactoring 00:42:02.280 --> 00:42:03.950 align:start position:0% uh has some bugs because of refactoring and<00:42:02.400> broken<00:42:02.579> so<00:42:02.940> right<00:42:03.480> now<00:42:03.599> what<00:42:03.780> we 00:42:03.950 --> 00:42:03.960 align:start position:0% and broken so right now what we 00:42:03.960 --> 00:42:05.450 align:start position:0% and broken so right now what we currently<00:42:04.260> have<00:42:04.320> on<00:42:04.440> our<00:42:04.619> GitHub<00:42:04.859> is<00:42:05.160> broken 00:42:05.450 --> 00:42:05.460 align:start position:0% currently have on our GitHub is broken 00:42:05.460 --> 00:42:07.550 align:start position:0% currently have on our GitHub is broken but<00:42:06.060> that's<00:42:06.780> the<00:42:06.960> beauty<00:42:07.079> of<00:42:07.260> what<00:42:07.440> we're 00:42:07.550 --> 00:42:07.560 align:start position:0% but that's the beauty of what we're 00:42:07.560 --> 00:42:09.950 align:start position:0% but that's the beauty of what we're doing<00:42:07.680> is<00:42:07.859> we're<00:42:08.220> we're<00:42:08.400> building<00:42:09.000> it<00:42:09.180> out<00:42:09.359> uh 00:42:09.950 --> 00:42:09.960 align:start position:0% doing is we're we're building it out uh 00:42:09.960 --> 00:42:11.810 align:start position:0% doing is we're we're building it out uh and<00:42:10.140> we're<00:42:10.500> uh<00:42:11.040> and<00:42:11.220> then<00:42:11.339> once<00:42:11.579> we're<00:42:11.700> ready 00:42:11.810 --> 00:42:11.820 align:start position:0% and we're uh and then once we're ready 00:42:11.820 --> 00:42:13.790 align:start position:0% and we're uh and then once we're ready to<00:42:11.940> make<00:42:12.119> a<00:42:12.240> production<00:42:12.480> ready<00:42:12.780> it's<00:42:13.140> in<00:42:13.380> a<00:42:13.560> uh 00:42:13.790 --> 00:42:13.800 align:start position:0% to make a production ready it's in a uh 00:42:13.800 --> 00:42:15.170 align:start position:0% to make a production ready it's in a uh right<00:42:14.220> now<00:42:14.339> it's<00:42:14.460> in<00:42:14.579> its<00:42:14.760> own<00:42:14.820> dedicated 00:42:15.170 --> 00:42:15.180 align:start position:0% right now it's in its own dedicated 00:42:15.180 --> 00:42:16.550 align:start position:0% right now it's in its own dedicated Branch 00:42:16.550 --> 00:42:16.560 align:start position:0% Branch 00:42:16.560 --> 00:42:18.710 align:start position:0% Branch um<00:42:16.680> but<00:42:16.920> once<00:42:17.220> you<00:42:17.339> push<00:42:17.520> the<00:42:17.700> master<00:42:17.880> then 00:42:18.710 --> 00:42:18.720 align:start position:0% um but once you push the master then 00:42:18.720 --> 00:42:21.109 align:start position:0% um but once you push the master then anyone<00:42:19.320> could<00:42:19.859> actually<00:42:20.099> use<00:42:20.400> node<00:42:20.700> launcher 00:42:21.109 --> 00:42:21.119 align:start position:0% anyone could actually use node launcher 00:42:21.119 --> 00:42:24.530 align:start position:0% anyone could actually use node launcher to<00:42:21.240> create<00:42:21.420> a<00:42:22.079> validators<00:42:22.740> for<00:42:22.980> ethereum<00:42:23.540> uh 00:42:24.530 --> 00:42:24.540 align:start position:0% to create a validators for ethereum uh 00:42:24.540 --> 00:42:26.390 align:start position:0% to create a validators for ethereum uh where<00:42:24.960> you<00:42:25.140> want<00:42:25.260> to<00:42:25.380> add<00:42:25.500> multiple<00:42:25.859> clients 00:42:26.390 --> 00:42:26.400 align:start position:0% where you want to add multiple clients 00:42:26.400 --> 00:42:28.910 align:start position:0% where you want to add multiple clients uh<00:42:27.119> by<00:42:27.300> the<00:42:27.420> end<00:42:27.540> of<00:42:27.660> the<00:42:27.780> year<00:42:27.900> uh<00:42:28.500> development 00:42:28.910 --> 00:42:28.920 align:start position:0% uh by the end of the year uh development 00:42:28.920 --> 00:42:31.490 align:start position:0% uh by the end of the year uh development progress<00:42:29.339> can<00:42:29.940> be<00:42:30.119> followed<00:42:30.480> on<00:42:30.900> our<00:42:31.140> GitHub 00:42:31.490 --> 00:42:31.500 align:start position:0% progress can be followed on our GitHub 00:42:31.500 --> 00:42:35.710 align:start position:0% progress can be followed on our GitHub which<00:42:31.740> is<00:42:31.859> no<00:42:31.980> launcher<00:42:32.460> uh<00:42:33.000> decentralized 00:42:35.710 --> 00:42:35.720 align:start position:0% which is no launcher uh decentralized 00:42:35.720 --> 00:42:38.690 align:start position:0% which is no launcher uh decentralized and<00:42:36.720> we<00:42:36.900> hope<00:42:37.020> to<00:42:37.200> see<00:42:37.320> developers<00:42:37.740> use<00:42:38.040> this 00:42:38.690 --> 00:42:38.700 align:start position:0% and we hope to see developers use this 00:42:38.700 --> 00:42:41.750 align:start position:0% and we hope to see developers use this tool<00:42:39.180> or<00:42:39.720> use<00:42:39.960> tools<00:42:40.320> like<00:42:40.380> node<00:42:40.619> launcher<00:42:41.040> to 00:42:41.750 --> 00:42:41.760 align:start position:0% tool or use tools like node launcher to 00:42:41.760 --> 00:42:44.210 align:start position:0% tool or use tools like node launcher to create<00:42:41.940> next<00:42:42.420> generation<00:42:42.960> of<00:42:43.440> software<00:42:43.800> where 00:42:44.210 --> 00:42:44.220 align:start position:0% create next generation of software where 00:42:44.220 --> 00:42:47.990 align:start position:0% create next generation of software where it's<00:42:44.460> super<00:42:44.640> user<00:42:45.060> focused<00:42:45.480> super<00:42:46.079> uh<00:42:47.040> uh 00:42:47.990 --> 00:42:48.000 align:start position:0% it's super user focused super uh uh 00:42:48.000 --> 00:42:50.810 align:start position:0% it's super user focused super uh uh super<00:42:48.599> feature<00:42:49.260> Rich<00:42:49.500> so<00:42:50.220> that<00:42:50.400> it<00:42:50.640> can 00:42:50.810 --> 00:42:50.820 align:start position:0% super feature Rich so that it can 00:42:50.820 --> 00:42:52.609 align:start position:0% super feature Rich so that it can attract<00:42:51.060> more<00:42:51.300> people<00:42:51.540> that<00:42:51.780> wanna<00:42:52.079> you<00:42:52.560> know 00:42:52.609 --> 00:42:52.619 align:start position:0% attract more people that wanna you know 00:42:52.619 --> 00:42:54.170 align:start position:0% attract more people that wanna you know if<00:42:52.740> they're<00:42:52.920> considering<00:42:53.339> hey<00:42:53.520> should<00:42:53.820> I<00:42:54.000> put 00:42:54.170 --> 00:42:54.180 align:start position:0% if they're considering hey should I put 00:42:54.180 --> 00:42:56.870 align:start position:0% if they're considering hey should I put my<00:42:54.540> uh<00:42:55.320> should<00:42:55.440> I<00:42:55.619> put<00:42:55.740> my<00:42:55.859> stake<00:42:56.220> in<00:42:56.400> a<00:42:56.520> staking 00:42:56.870 --> 00:42:56.880 align:start position:0% my uh should I put my stake in a staking 00:42:56.880 --> 00:42:59.210 align:start position:0% my uh should I put my stake in a staking service<00:42:57.180> which<00:42:57.660> I<00:42:57.839> run<00:42:57.960> on<00:42:58.200> my<00:42:58.319> own<00:42:58.440> it's<00:42:58.980> just 00:42:59.210 --> 00:42:59.220 align:start position:0% service which I run on my own it's just 00:42:59.220 --> 00:43:00.950 align:start position:0% service which I run on my own it's just so<00:42:59.520> simple<00:42:59.640> to<00:42:59.880> run<00:43:00.000> on<00:43:00.180> your<00:43:00.300> own<00:43:00.420> and<00:43:00.780> there's 00:43:00.950 --> 00:43:00.960 align:start position:0% so simple to run on your own and there's 00:43:00.960 --> 00:43:02.690 align:start position:0% so simple to run on your own and there's so<00:43:01.140> many<00:43:01.260> options<00:43:01.680> for<00:43:01.980> writing<00:43:02.280> on<00:43:02.400> your<00:43:02.579> own 00:43:02.690 --> 00:43:02.700 align:start position:0% so many options for writing on your own 00:43:02.700 --> 00:43:04.609 align:start position:0% so many options for writing on your own that<00:43:03.300> you<00:43:03.540> don't<00:43:03.660> even<00:43:03.839> need<00:43:04.079> to<00:43:04.200> consider 00:43:04.609 --> 00:43:04.619 align:start position:0% that you don't even need to consider 00:43:04.619 --> 00:43:07.250 align:start position:0% that you don't even need to consider giving<00:43:05.220> your<00:43:05.460> keys<00:43:05.880> and<00:43:06.540> uh<00:43:06.839> putting<00:43:07.079> your 00:43:07.250 --> 00:43:07.260 align:start position:0% giving your keys and uh putting your 00:43:07.260 --> 00:43:09.170 align:start position:0% giving your keys and uh putting your trust<00:43:07.500> in<00:43:07.680> someone<00:43:07.859> else 00:43:09.170 --> 00:43:09.180 align:start position:0% trust in someone else 00:43:09.180 --> 00:43:10.630 align:start position:0% trust in someone else foreign 00:43:10.630 --> 00:43:10.640 align:start position:0% foreign 00:43:10.640 --> 00:43:13.670 align:start position:0% foreign conclusion<00:43:11.640> then<00:43:11.819> with<00:43:12.300> everything<00:43:12.660> that<00:43:13.140> uh 00:43:13.670 --> 00:43:13.680 align:start position:0% conclusion then with everything that uh 00:43:13.680 --> 00:43:16.430 align:start position:0% conclusion then with everything that uh Maggie<00:43:14.160> uh<00:43:15.000> talked<00:43:15.420> about<00:43:15.420> and<00:43:15.900> then<00:43:16.020> what<00:43:16.260> I'm 00:43:16.430 --> 00:43:16.440 align:start position:0% Maggie uh talked about and then what I'm 00:43:16.440 --> 00:43:18.710 align:start position:0% Maggie uh talked about and then what I'm kind<00:43:16.619> of<00:43:16.740> closing<00:43:17.099> here<00:43:17.280> with<00:43:17.540> uh<00:43:18.540> in 00:43:18.710 --> 00:43:18.720 align:start position:0% kind of closing here with uh in 00:43:18.720 --> 00:43:20.870 align:start position:0% kind of closing here with uh in conclusion<00:43:19.200> ethereum<00:43:19.859> is<00:43:19.980> designed<00:43:20.460> for 00:43:20.870 --> 00:43:20.880 align:start position:0% conclusion ethereum is designed for 00:43:20.880 --> 00:43:23.210 align:start position:0% conclusion ethereum is designed for optimal<00:43:21.540> decentralization<00:43:22.319> it's<00:43:22.920> really 00:43:23.210 --> 00:43:23.220 align:start position:0% optimal decentralization it's really 00:43:23.220 --> 00:43:25.430 align:start position:0% optimal decentralization it's really designed<00:43:23.760> to<00:43:24.180> push 00:43:25.430 --> 00:43:25.440 align:start position:0% designed to push 00:43:25.440 --> 00:43:28.670 align:start position:0% designed to push folks<00:43:26.220> to<00:43:26.579> decentralization<00:43:27.359> by<00:43:28.319> having 00:43:28.670 --> 00:43:28.680 align:start position:0% folks to decentralization by having 00:43:28.680 --> 00:43:30.470 align:start position:0% folks to decentralization by having those<00:43:28.980> large<00:43:29.160> slashing<00:43:29.700> events<00:43:30.060> where<00:43:30.240> if 00:43:30.470 --> 00:43:30.480 align:start position:0% those large slashing events where if 00:43:30.480 --> 00:43:32.510 align:start position:0% those large slashing events where if you're<00:43:30.599> part<00:43:31.020> of<00:43:31.319> too<00:43:31.500> large<00:43:31.680> of<00:43:31.920> a<00:43:32.040> group<00:43:32.220> you 00:43:32.510 --> 00:43:32.520 align:start position:0% you're part of too large of a group you 00:43:32.520 --> 00:43:34.130 align:start position:0% you're part of too large of a group you know<00:43:32.640> using<00:43:33.000> a<00:43:33.119> certain<00:43:33.240> client<00:43:33.599> or<00:43:33.780> on<00:43:34.020> a 00:43:34.130 --> 00:43:34.140 align:start position:0% know using a certain client or on a 00:43:34.140 --> 00:43:35.930 align:start position:0% know using a certain client or on a certain<00:43:34.260> cloud<00:43:34.560> provider<00:43:35.160> you'll<00:43:35.760> start 00:43:35.930 --> 00:43:35.940 align:start position:0% certain cloud provider you'll start 00:43:35.940 --> 00:43:37.490 align:start position:0% certain cloud provider you'll start getting<00:43:36.119> slashed<00:43:36.660> there's<00:43:36.839> an<00:43:37.020> issue<00:43:37.319> there 00:43:37.490 --> 00:43:37.500 align:start position:0% getting slashed there's an issue there 00:43:37.500 --> 00:43:40.510 align:start position:0% getting slashed there's an issue there it<00:43:38.099> really<00:43:38.400> incentivizes<00:43:39.300> the<00:43:39.780> run<00:43:39.960> at<00:43:40.200> home 00:43:40.510 --> 00:43:40.520 align:start position:0% it really incentivizes the run at home 00:43:40.520 --> 00:43:43.370 align:start position:0% it really incentivizes the run at home decentralized<00:43:41.520> kind<00:43:41.819> of<00:43:42.000> ecosystem<00:43:42.480> uh 00:43:43.370 --> 00:43:43.380 align:start position:0% decentralized kind of ecosystem uh 00:43:43.380 --> 00:43:45.050 align:start position:0% decentralized kind of ecosystem uh evaluators<00:43:43.920> can<00:43:44.099> protect<00:43:44.280> themselves<00:43:44.700> by 00:43:45.050 --> 00:43:45.060 align:start position:0% evaluators can protect themselves by 00:43:45.060 --> 00:43:46.970 align:start position:0% evaluators can protect themselves by potentially<00:43:45.420> uh<00:43:45.780> from<00:43:46.140> potentially<00:43:46.560> large 00:43:46.970 --> 00:43:46.980 align:start position:0% potentially uh from potentially large 00:43:46.980 --> 00:43:49.730 align:start position:0% potentially uh from potentially large losses<00:43:47.520> by<00:43:47.819> avoiding<00:43:48.300> uh<00:43:48.960> oversaturated 00:43:49.730 --> 00:43:49.740 align:start position:0% losses by avoiding uh oversaturated 00:43:49.740 --> 00:43:53.750 align:start position:0% losses by avoiding uh oversaturated Cloud<00:43:50.040> providers<00:43:50.520> AWS<00:43:51.359> 53<00:43:52.339> it's<00:43:53.339> starting<00:43:53.579> to 00:43:53.750 --> 00:43:53.760 align:start position:0% Cloud providers AWS 53 it's starting to 00:43:53.760 --> 00:43:55.730 align:start position:0% Cloud providers AWS 53 it's starting to get<00:43:53.940> to<00:43:54.060> a<00:43:54.180> point<00:43:54.300> where<00:43:54.420> it's<00:43:54.599> at<00:43:54.720> risk<00:43:55.079> if<00:43:55.619> you 00:43:55.730 --> 00:43:55.740 align:start position:0% get to a point where it's at risk if you 00:43:55.740 --> 00:43:57.589 align:start position:0% get to a point where it's at risk if you Deploy<00:43:56.099> on<00:43:56.400> AWS<00:43:56.940> simply<00:43:57.240> because<00:43:57.359> if 00:43:57.589 --> 00:43:57.599 align:start position:0% Deploy on AWS simply because if 00:43:57.599 --> 00:43:59.270 align:start position:0% Deploy on AWS simply because if something<00:43:57.780> happens<00:43:58.020> there<00:43:58.319> even<00:43:58.740> if<00:43:58.980> it<00:43:59.099> just 00:43:59.270 --> 00:43:59.280 align:start position:0% something happens there even if it just 00:43:59.280 --> 00:44:01.309 align:start position:0% something happens there even if it just goes<00:43:59.579> offline<00:43:59.880> they<00:44:00.119> have<00:44:00.240> a<00:44:00.359> DNS<00:44:00.720> error<00:44:01.079> you 00:44:01.309 --> 00:44:01.319 align:start position:0% goes offline they have a DNS error you 00:44:01.319 --> 00:44:02.690 align:start position:0% goes offline they have a DNS error you know<00:44:01.380> and<00:44:01.619> something<00:44:01.859> goes<00:44:02.160> offline<00:44:02.460> which 00:44:02.690 --> 00:44:02.700 align:start position:0% know and something goes offline which 00:44:02.700 --> 00:44:04.490 align:start position:0% know and something goes offline which happened<00:44:02.880> last<00:44:03.180> year<00:44:03.300> they<00:44:03.599> had<00:44:03.839> entire<00:44:04.079> data 00:44:04.490 --> 00:44:04.500 align:start position:0% happened last year they had entire data 00:44:04.500 --> 00:44:07.130 align:start position:0% happened last year they had entire data centers<00:44:04.800> going<00:44:05.040> down<00:44:05.220> because<00:44:05.540> uh<00:44:06.540> an<00:44:06.720> admin 00:44:07.130 --> 00:44:07.140 align:start position:0% centers going down because uh an admin 00:44:07.140 --> 00:44:09.710 align:start position:0% centers going down because uh an admin accidentally<00:44:07.740> pushed<00:44:08.160> a<00:44:08.400> patch<00:44:08.940> to<00:44:09.119> their<00:44:09.359> DNS 00:44:09.710 --> 00:44:09.720 align:start position:0% accidentally pushed a patch to their DNS 00:44:09.720 --> 00:44:11.270 align:start position:0% accidentally pushed a patch to their DNS that<00:44:09.960> broke<00:44:10.200> everything 00:44:11.270 --> 00:44:11.280 align:start position:0% that broke everything 00:44:11.280 --> 00:44:12.109 align:start position:0% that broke everything um 00:44:12.109 --> 00:44:12.119 align:start position:0% um 00:44:12.119 --> 00:44:14.270 align:start position:0% um that<00:44:12.780> you<00:44:12.960> know<00:44:13.079> those<00:44:13.260> kind<00:44:13.560> of<00:44:13.680> those<00:44:14.099> kind 00:44:14.270 --> 00:44:14.280 align:start position:0% that you know those kind of those kind 00:44:14.280 --> 00:44:16.609 align:start position:0% that you know those kind of those kind of<00:44:14.400> simple<00:44:14.760> things<00:44:15.660> could<00:44:16.079> actually<00:44:16.260> affect 00:44:16.609 --> 00:44:16.619 align:start position:0% of simple things could actually affect 00:44:16.619 --> 00:44:18.410 align:start position:0% of simple things could actually affect the<00:44:16.800> entire<00:44:16.980> network<00:44:17.220> so<00:44:17.520> it's<00:44:17.880> becoming<00:44:18.300> a 00:44:18.410 --> 00:44:18.420 align:start position:0% the entire network so it's becoming a 00:44:18.420 --> 00:44:20.930 align:start position:0% the entire network so it's becoming a risk<00:44:18.720> to<00:44:18.839> be<00:44:18.960> on<00:44:19.079> these<00:44:19.200> large<00:44:19.380> platforms<00:44:20.099> uh 00:44:20.930 --> 00:44:20.940 align:start position:0% risk to be on these large platforms uh 00:44:20.940 --> 00:44:22.910 align:start position:0% risk to be on these large platforms uh and<00:44:21.180> then<00:44:21.420> use<00:44:21.900> clients<00:44:22.380> with<00:44:22.619> less 00:44:22.910 --> 00:44:22.920 align:start position:0% and then use clients with less 00:44:22.920 --> 00:44:25.010 align:start position:0% and then use clients with less utilization<00:44:23.579> in<00:44:24.060> the<00:44:24.180> network<00:44:24.300> itself<00:44:24.780> right 00:44:25.010 --> 00:44:25.020 align:start position:0% utilization in the network itself right 00:44:25.020 --> 00:44:26.390 align:start position:0% utilization in the network itself right now<00:44:25.200> if<00:44:25.319> you're<00:44:25.380> using<00:44:25.560> prison<00:44:25.800> or<00:44:26.040> Lighthouse 00:44:26.390 --> 00:44:26.400 align:start position:0% now if you're using prison or Lighthouse 00:44:26.400 --> 00:44:29.569 align:start position:0% now if you're using prison or Lighthouse you're<00:44:27.060> in<00:44:27.240> that<00:44:27.480> 40<00:44:27.720> range<00:44:28.500> uh<00:44:29.220> so<00:44:29.339> if 00:44:29.569 --> 00:44:29.579 align:start position:0% you're in that 40 range uh so if 00:44:29.579 --> 00:44:30.589 align:start position:0% you're in that 40 range uh so if something<00:44:29.700> were<00:44:29.880> to<00:44:30.060> happen<00:44:30.180> to<00:44:30.300> either<00:44:30.420> of 00:44:30.589 --> 00:44:30.599 align:start position:0% something were to happen to either of 00:44:30.599 --> 00:44:33.050 align:start position:0% something were to happen to either of those<00:44:30.720> clients<00:44:31.140> you<00:44:31.920> could<00:44:32.040> potentially<00:44:32.640> see 00:44:33.050 --> 00:44:33.060 align:start position:0% those clients you could potentially see 00:44:33.060 --> 00:44:36.589 align:start position:0% those clients you could potentially see uh<00:44:33.839> large<00:44:34.079> losses<00:44:34.560> uh<00:44:35.400> but<00:44:35.819> the<00:44:36.060> good<00:44:36.240> news<00:44:36.420> is 00:44:36.589 --> 00:44:36.599 align:start position:0% uh large losses uh but the good news is 00:44:36.599 --> 00:44:38.390 align:start position:0% uh large losses uh but the good news is there<00:44:36.960> are<00:44:37.140> great<00:44:37.319> options<00:44:37.619> for<00:44:37.859> entry-level 00:44:38.390 --> 00:44:38.400 align:start position:0% there are great options for entry-level 00:44:38.400 --> 00:44:40.069 align:start position:0% there are great options for entry-level users<00:44:38.760> to<00:44:38.880> participate<00:44:39.300> in<00:44:39.480> the<00:44:39.660> ethereum 00:44:40.069 --> 00:44:40.079 align:start position:0% users to participate in the ethereum 00:44:40.079 --> 00:44:42.230 align:start position:0% users to participate in the ethereum validation<00:44:40.560> I<00:44:41.099> definitely<00:44:41.579> encourage<00:44:41.940> you<00:44:42.060> to 00:44:42.230 --> 00:44:42.240 align:start position:0% validation I definitely encourage you to 00:44:42.240 --> 00:44:44.390 align:start position:0% validation I definitely encourage you to go<00:44:42.420> look<00:44:42.660> at<00:44:43.079> those<00:44:43.260> options<00:44:43.619> that<00:44:43.859> are<00:44:44.040> listed 00:44:44.390 --> 00:44:44.400 align:start position:0% go look at those options that are listed 00:44:44.400 --> 00:44:49.309 align:start position:0% go look at those options that are listed on<00:44:44.780> ethereum.org<00:44:45.780> uh<00:44:46.740> when<00:44:46.980> it<00:44:47.160> says<00:44:47.579> uh 00:44:49.309 --> 00:44:49.319 align:start position:0% on ethereum.org uh when it says uh 00:44:49.319 --> 00:44:51.470 align:start position:0% on ethereum.org uh when it says uh uh<00:44:49.980> say<00:44:50.220> ethereum<00:44:50.760> and<00:44:51.060> they<00:44:51.240> talk<00:44:51.420> about 00:44:51.470 --> 00:44:51.480 align:start position:0% uh say ethereum and they talk about 00:44:51.480 --> 00:44:53.329 align:start position:0% uh say ethereum and they talk about different<00:44:51.720> options<00:44:52.079> all<00:44:52.680> these<00:44:52.859> options<00:44:53.099> are 00:44:53.329 --> 00:44:53.339 align:start position:0% different options all these options are 00:44:53.339 --> 00:44:54.770 align:start position:0% different options all these options are there<00:44:53.520> because<00:44:53.760> they<00:44:54.000> were<00:44:54.119> open<00:44:54.300> source<00:44:54.660> all 00:44:54.770 --> 00:44:54.780 align:start position:0% there because they were open source all 00:44:54.780 --> 00:44:56.450 align:start position:0% there because they were open source all three<00:44:54.960> that<00:44:55.200> I<00:44:55.319> mentioned<00:44:55.680> they're<00:44:56.220> really 00:44:56.450 --> 00:44:56.460 align:start position:0% three that I mentioned they're really 00:44:56.460 --> 00:44:58.309 align:start position:0% three that I mentioned they're really great<00:44:56.640> options<00:44:56.940> there's<00:44:57.240> no<00:44:57.540> reason<00:44:57.660> to<00:44:57.900> not 00:44:58.309 --> 00:44:58.319 align:start position:0% great options there's no reason to not 00:44:58.319 --> 00:45:01.190 align:start position:0% great options there's no reason to not run<00:44:58.800> your<00:44:59.040> own<00:44:59.160> theory<00:44:59.579> note<00:44:59.819> today<00:45:00.119> uh<00:45:01.020> but 00:45:01.190 --> 00:45:01.200 align:start position:0% run your own theory note today uh but 00:45:01.200 --> 00:45:03.349 align:start position:0% run your own theory note today uh but then<00:45:01.319> kind<00:45:01.560> of<00:45:01.619> looking<00:45:01.800> to<00:45:02.339> the<00:45:02.579> future<00:45:02.760> we 00:45:03.349 --> 00:45:03.359 align:start position:0% then kind of looking to the future we 00:45:03.359 --> 00:45:05.270 align:start position:0% then kind of looking to the future we are<00:45:03.480> very<00:45:03.720> excited<00:45:04.020> we're<00:45:04.200> very<00:45:04.440> bullish<00:45:04.859> on 00:45:05.270 --> 00:45:05.280 align:start position:0% are very excited we're very bullish on 00:45:05.280 --> 00:45:08.870 align:start position:0% are very excited we're very bullish on where<00:45:05.640> no<00:45:06.180> software<00:45:06.660> can<00:45:07.079> go<00:45:07.400> uh<00:45:08.400> and<00:45:08.579> the<00:45:08.700> kind 00:45:08.870 --> 00:45:08.880 align:start position:0% where no software can go uh and the kind 00:45:08.880 --> 00:45:10.970 align:start position:0% where no software can go uh and the kind of<00:45:09.060> user<00:45:09.359> experience<00:45:09.780> that<00:45:10.440> could<00:45:10.619> become 00:45:10.970 --> 00:45:10.980 align:start position:0% of user experience that could become 00:45:10.980 --> 00:45:14.089 align:start position:0% of user experience that could become standard<00:45:11.520> for<00:45:11.880> node<00:45:12.359> software<00:45:12.720> uh<00:45:13.619> and<00:45:13.920> you 00:45:14.089 --> 00:45:14.099 align:start position:0% standard for node software uh and you 00:45:14.099 --> 00:45:15.470 align:start position:0% standard for node software uh and you know<00:45:14.160> we're<00:45:14.339> excited<00:45:14.700> to<00:45:14.819> be<00:45:14.880> working<00:45:15.119> on<00:45:15.359> our 00:45:15.470 --> 00:45:15.480 align:start position:0% know we're excited to be working on our 00:45:15.480 --> 00:45:17.990 align:start position:0% know we're excited to be working on our side<00:45:15.839> on<00:45:16.319> the<00:45:16.560> uh<00:45:16.800> tooling<00:45:17.280> side<00:45:17.520> whether 00:45:17.990 --> 00:45:18.000 align:start position:0% side on the uh tooling side whether 00:45:18.000 --> 00:45:20.390 align:start position:0% side on the uh tooling side whether Cloud's<00:45:18.599> working<00:45:18.720> on<00:45:18.960> the<00:45:19.319> uh<00:45:19.740> infrastructure 00:45:20.390 --> 00:45:20.400 align:start position:0% Cloud's working on the uh infrastructure 00:45:20.400 --> 00:45:22.849 align:start position:0% Cloud's working on the uh infrastructure and<00:45:20.760> Hardware<00:45:20.940> side<00:45:21.359> so<00:45:21.720> really<00:45:22.380> the<00:45:22.619> future 00:45:22.849 --> 00:45:22.859 align:start position:0% and Hardware side so really the future 00:45:22.859 --> 00:45:24.890 align:start position:0% and Hardware side so really the future is<00:45:23.099> super<00:45:23.280> bright<00:45:23.520> with<00:45:24.000> ethereum<00:45:24.540> validation 00:45:24.890 --> 00:45:24.900 align:start position:0% is super bright with ethereum validation 00:45:24.900 --> 00:45:26.450 align:start position:0% is super bright with ethereum validation we<00:45:25.140> want<00:45:25.260> to<00:45:25.319> encourage<00:45:25.560> everyone<00:45:25.800> to<00:45:26.160> run 00:45:26.450 --> 00:45:26.460 align:start position:0% we want to encourage everyone to run 00:45:26.460 --> 00:45:29.210 align:start position:0% we want to encourage everyone to run their<00:45:26.700> own<00:45:26.819> ethereum<00:45:27.300> nodes<00:45:27.680> uh<00:45:28.680> on<00:45:28.920> their<00:45:29.040> own 00:45:29.210 --> 00:45:29.220 align:start position:0% their own ethereum nodes uh on their own 00:45:29.220 --> 00:45:32.510 align:start position:0% their own ethereum nodes uh on their own so<00:45:29.880> that's<00:45:30.300> uh<00:45:30.660> thanks<00:45:31.079> for<00:45:31.380> joining<00:45:31.859> us<00:45:32.040> I 00:45:32.510 --> 00:45:32.520 align:start position:0% so that's uh thanks for joining us I 00:45:32.520 --> 00:45:35.270 align:start position:0% so that's uh thanks for joining us I think<00:45:32.640> uh<00:45:33.060> are<00:45:33.180> we<00:45:33.300> doing<00:45:33.420> like<00:45:33.660> a<00:45:33.900> q<00:45:34.200> a<00:45:34.380> uh 00:45:35.270 --> 00:45:35.280 align:start position:0% think uh are we doing like a q a uh 00:45:35.280 --> 00:45:37.190 align:start position:0% think uh are we doing like a q a uh because<00:45:35.400> we<00:45:35.640> have<00:45:35.819> like<00:45:36.119> 12<00:45:36.540> minutes<00:45:36.780> do<00:45:37.079> we 00:45:37.190 --> 00:45:37.200 align:start position:0% because we have like 12 minutes do we 00:45:37.200 --> 00:45:39.470 align:start position:0% because we have like 12 minutes do we have<00:45:37.319> 12<00:45:37.500> minutes 00:45:39.470 --> 00:45:39.480 align:start position:0% have 12 minutes 00:45:39.480 --> 00:45:40.609 align:start position:0% have 12 minutes amazing 00:45:40.609 --> 00:45:40.619 align:start position:0% amazing 00:45:40.619 --> 00:45:43.550 align:start position:0% amazing okay<00:45:41.160> yeah<00:45:42.000> if<00:45:42.480> folks<00:45:43.020> have<00:45:43.140> any<00:45:43.319> questions 00:45:43.550 --> 00:45:43.560 align:start position:0% okay yeah if folks have any questions 00:45:43.560 --> 00:45:53.150 align:start position:0% okay yeah if folks have any questions about<00:45:43.920> any<00:45:44.400> of<00:45:44.520> this<00:45:44.700> let<00:45:45.000> us<00:45:45.180> know<00:45:45.300> yes 00:45:53.150 --> 00:45:53.160 align:start position:0% 00:45:53.160 --> 00:45:58.190 align:start position:0% yep 00:45:58.190 --> 00:45:58.200 align:start position:0% 00:45:58.200 --> 00:46:00.410 align:start position:0% yeah 00:46:00.410 --> 00:46:00.420 align:start position:0% yeah 00:46:00.420 --> 00:46:03.290 align:start position:0% yeah so<00:46:01.079> uh<00:46:01.680> so<00:46:01.920> specifically<00:46:02.579> so<00:46:02.760> I'm<00:46:03.000> not<00:46:03.119> a 00:46:03.290 --> 00:46:03.300 align:start position:0% so uh so specifically so I'm not a 00:46:03.300 --> 00:46:06.470 align:start position:0% so uh so specifically so I'm not a developer<00:46:03.720> so<00:46:04.020> how<00:46:04.440> exactly<00:46:04.920> no<00:46:05.220> launchers<00:46:05.700> uh 00:46:06.470 --> 00:46:06.480 align:start position:0% developer so how exactly no launchers uh 00:46:06.480 --> 00:46:08.510 align:start position:0% developer so how exactly no launchers uh or<00:46:06.780> yeah<00:46:07.200> no<00:46:07.440> launcher<00:46:07.920> is<00:46:08.040> dealing<00:46:08.400> with 00:46:08.510 --> 00:46:08.520 align:start position:0% or yeah no launcher is dealing with 00:46:08.520 --> 00:46:11.990 align:start position:0% or yeah no launcher is dealing with Secrets<00:46:08.940> uh<00:46:09.839> yes<00:46:10.140> what<00:46:10.740> we<00:46:10.920> what<00:46:11.280> we<00:46:11.460> do<00:46:11.700> have 00:46:11.990 --> 00:46:12.000 align:start position:0% Secrets uh yes what we what we do have 00:46:12.000 --> 00:46:15.829 align:start position:0% Secrets uh yes what we what we do have is<00:46:12.480> the<00:46:12.839> uh<00:46:13.200> RPC<00:46:13.800> password<00:46:14.460> for<00:46:15.000> those<00:46:15.420> nodes 00:46:15.829 --> 00:46:15.839 align:start position:0% is the uh RPC password for those nodes 00:46:15.839 --> 00:46:18.530 align:start position:0% is the uh RPC password for those nodes are<00:46:16.380> actually<00:46:16.560> being<00:46:16.920> stored<00:46:17.460> in<00:46:17.760> memory<00:46:18.119> so 00:46:18.530 --> 00:46:18.540 align:start position:0% are actually being stored in memory so 00:46:18.540 --> 00:46:20.390 align:start position:0% are actually being stored in memory so there<00:46:18.900> are<00:46:19.079> elements<00:46:19.500> that<00:46:19.619> are<00:46:19.859> being<00:46:19.980> stored 00:46:20.390 --> 00:46:20.400 align:start position:0% there are elements that are being stored 00:46:20.400 --> 00:46:22.910 align:start position:0% there are elements that are being stored in<00:46:20.700> memory<00:46:21.060> uh<00:46:21.780> with<00:46:21.960> node<00:46:22.260> launcher<00:46:22.619> so 00:46:22.910 --> 00:46:22.920 align:start position:0% in memory uh with node launcher so 00:46:22.920 --> 00:46:25.309 align:start position:0% in memory uh with node launcher so they're<00:46:23.099> not<00:46:23.220> in<00:46:23.400> playing<00:46:23.520> text<00:46:23.819> uh<00:46:24.780> now<00:46:25.020> we're 00:46:25.309 --> 00:46:25.319 align:start position:0% they're not in playing text uh now we're 00:46:25.319 --> 00:46:27.290 align:start position:0% they're not in playing text uh now we're still<00:46:25.560> developing<00:46:26.220> ethereum<00:46:26.819> and<00:46:27.000> figuring 00:46:27.290 --> 00:46:27.300 align:start position:0% still developing ethereum and figuring 00:46:27.300 --> 00:46:28.970 align:start position:0% still developing ethereum and figuring out<00:46:27.359> how<00:46:27.660> are<00:46:27.780> we<00:46:27.900> going<00:46:28.020> to<00:46:28.079> handle<00:46:28.440> all<00:46:28.800> the 00:46:28.970 --> 00:46:28.980 align:start position:0% out how are we going to handle all the 00:46:28.980 --> 00:46:31.190 align:start position:0% out how are we going to handle all the you<00:46:29.339> know<00:46:29.460> handle<00:46:30.119> everything<00:46:30.420> handle<00:46:31.020> all 00:46:31.190 --> 00:46:31.200 align:start position:0% you know handle everything handle all 00:46:31.200 --> 00:46:33.230 align:start position:0% you know handle everything handle all the<00:46:31.380> secrets<00:46:31.800> but<00:46:32.160> we're<00:46:32.339> building<00:46:32.579> into<00:46:32.880> node 00:46:33.230 --> 00:46:33.240 align:start position:0% the secrets but we're building into node 00:46:33.240 --> 00:46:37.550 align:start position:0% the secrets but we're building into node launcher<00:46:33.720> ways<00:46:34.560> to<00:46:34.859> protect<00:46:35.400> uh<00:46:36.240> from<00:46:36.540> having 00:46:37.550 --> 00:46:37.560 align:start position:0% launcher ways to protect uh from having 00:46:37.560 --> 00:46:41.270 align:start position:0% launcher ways to protect uh from having um<00:46:37.680> uh<00:46:38.640> from<00:46:38.940> having<00:46:39.119> you<00:46:39.660> know<00:46:39.720> plain<00:46:40.079> text<00:46:40.319> uh 00:46:41.270 --> 00:46:41.280 align:start position:0% um uh from having you know plain text uh 00:46:41.280 --> 00:46:44.210 align:start position:0% um uh from having you know plain text uh anything<00:46:41.660> on<00:46:42.660> your<00:46:43.200> server<00:46:43.560> because<00:46:43.740> we<00:46:43.920> feel 00:46:44.210 --> 00:46:44.220 align:start position:0% anything on your server because we feel 00:46:44.220 --> 00:46:46.370 align:start position:0% anything on your server because we feel like<00:46:44.339> that<00:46:44.520> that's<00:46:44.819> where<00:46:45.119> no<00:46:45.660> software 00:46:46.370 --> 00:46:46.380 align:start position:0% like that that's where no software 00:46:46.380 --> 00:46:48.589 align:start position:0% like that that's where no software should<00:46:46.619> go<00:46:46.800> to<00:46:47.040> where<00:46:47.220> uh<00:46:47.880> there's<00:46:48.240> a<00:46:48.420> lot<00:46:48.480> of 00:46:48.589 --> 00:46:48.599 align:start position:0% should go to where uh there's a lot of 00:46:48.599 --> 00:46:51.050 align:start position:0% should go to where uh there's a lot of security<00:46:48.780> around<00:46:49.260> how<00:46:49.680> your<00:46:50.040> uh<00:46:50.520> what's<00:46:50.819> being 00:46:51.050 --> 00:46:51.060 align:start position:0% security around how your uh what's being 00:46:51.060 --> 00:46:52.609 align:start position:0% security around how your uh what's being stored<00:46:51.420> on<00:46:51.540> your<00:46:51.720> server<00:46:51.960> and<00:46:52.140> how<00:46:52.319> it's<00:46:52.440> being 00:46:52.609 --> 00:46:52.619 align:start position:0% stored on your server and how it's being 00:46:52.619 --> 00:46:53.630 align:start position:0% stored on your server and how it's being stored 00:46:53.630 --> 00:46:53.640 align:start position:0% stored 00:46:53.640 --> 00:46:55.430 align:start position:0% stored um<00:46:53.700> and<00:46:53.940> so<00:46:54.180> usually<00:46:54.720> utilizing<00:46:55.260> something 00:46:55.430 --> 00:46:55.440 align:start position:0% um and so usually utilizing something 00:46:55.440 --> 00:46:58.250 align:start position:0% um and so usually utilizing something like<00:46:55.680> memory<00:46:56.099> is<00:46:56.400> one<00:46:56.700> way<00:46:56.880> that<00:46:57.359> you<00:46:57.660> can<00:46:57.780> put 00:46:58.250 --> 00:46:58.260 align:start position:0% like memory is one way that you can put 00:46:58.260 --> 00:47:21.550 align:start position:0% like memory is one way that you can put the<00:46:58.560> uh<00:46:58.859> password<00:46:59.640> inside 00:47:21.550 --> 00:47:21.560 align:start position:0% 00:47:21.560 --> 00:47:23.569 align:start position:0% thank<00:47:22.560> you<00:47:22.680> very<00:47:22.740> much 00:47:23.569 --> 00:47:23.579 align:start position:0% thank you very much 00:47:23.579 --> 00:47:26.630 align:start position:0% thank you very much this<00:47:24.119> was<00:47:24.300> really<00:47:24.540> useful<00:47:25.099> uh<00:47:26.099> so<00:47:26.339> two 00:47:26.630 --> 00:47:26.640 align:start position:0% this was really useful uh so two 00:47:26.640 --> 00:47:30.050 align:start position:0% this was really useful uh so two questions<00:47:27.079> one<00:47:28.079> uh<00:47:28.859> the<00:47:29.099> only<00:47:29.220> thing<00:47:29.520> stopping 00:47:30.050 --> 00:47:30.060 align:start position:0% questions one uh the only thing stopping 00:47:30.060 --> 00:47:32.750 align:start position:0% questions one uh the only thing stopping me<00:47:30.180> from<00:47:30.420> running<00:47:30.720> a<00:47:31.020> note<00:47:31.200> at<00:47:31.440> home<00:47:31.740> I<00:47:32.579> mean 00:47:32.750 --> 00:47:32.760 align:start position:0% me from running a note at home I mean 00:47:32.760 --> 00:47:35.270 align:start position:0% me from running a note at home I mean like<00:47:33.000> locally<00:47:33.420> is<00:47:34.140> that<00:47:34.319> I<00:47:34.440> don't<00:47:34.619> have<00:47:34.859> a<00:47:35.040> good 00:47:35.270 --> 00:47:35.280 align:start position:0% like locally is that I don't have a good 00:47:35.280 --> 00:47:37.809 align:start position:0% like locally is that I don't have a good connection<00:47:35.460> I<00:47:36.000> live<00:47:36.540> in<00:47:36.660> a<00:47:36.839> very<00:47:37.020> remote<00:47:37.260> area 00:47:37.809 --> 00:47:37.819 align:start position:0% connection I live in a very remote area 00:47:37.819 --> 00:47:43.069 align:start position:0% connection I live in a very remote area so<00:47:39.140> uh<00:47:40.140> perhaps<00:47:40.760> I<00:47:41.760> don't<00:47:41.819> know<00:47:41.880> update<00:47:42.480> on<00:47:42.720> the 00:47:43.069 --> 00:47:43.079 align:start position:0% so uh perhaps I don't know update on the 00:47:43.079 --> 00:47:46.250 align:start position:0% so uh perhaps I don't know update on the best<00:47:43.440> like<00:47:44.460> uh 00:47:46.250 --> 00:47:46.260 align:start position:0% best like uh 00:47:46.260 --> 00:47:48.170 align:start position:0% best like uh set<00:47:46.800> up<00:47:46.980> for<00:47:47.099> that<00:47:47.280> and<00:47:47.700> the<00:47:47.819> second<00:47:47.940> question 00:47:48.170 --> 00:47:48.180 align:start position:0% set up for that and the second question 00:47:48.180 --> 00:47:50.030 align:start position:0% set up for that and the second question is<00:47:48.420> if 00:47:50.030 --> 00:47:50.040 align:start position:0% is if 00:47:50.040 --> 00:47:52.490 align:start position:0% is if I<00:47:50.520> don't<00:47:50.640> have<00:47:50.880> 32<00:47:51.540> years 00:47:52.490 --> 00:47:52.500 align:start position:0% I don't have 32 years 00:47:52.500 --> 00:47:55.069 align:start position:0% I don't have 32 years and<00:47:52.920> I<00:47:53.099> want<00:47:53.280> to<00:47:53.460> own<00:47:53.760> something<00:47:54.300> at<00:47:54.599> home<00:47:54.780> is 00:47:55.069 --> 00:47:55.079 align:start position:0% and I want to own something at home is 00:47:55.079 --> 00:47:56.569 align:start position:0% and I want to own something at home is there<00:47:55.260> an<00:47:55.380> option 00:47:56.569 --> 00:47:56.579 align:start position:0% there an option 00:47:56.579 --> 00:48:00.050 align:start position:0% there an option so<00:47:57.240> uh<00:47:58.020> so<00:47:58.440> first<00:47:59.099> one<00:47:59.579> if<00:47:59.760> you<00:47:59.819> have<00:47:59.940> bad 00:48:00.050 --> 00:48:00.060 align:start position:0% so uh so first one if you have bad 00:48:00.060 --> 00:48:02.210 align:start position:0% so uh so first one if you have bad internet<00:48:00.300> so<00:48:00.839> how<00:48:01.200> penalties<00:48:01.740> work<00:48:01.980> in 00:48:02.210 --> 00:48:02.220 align:start position:0% internet so how penalties work in 00:48:02.220 --> 00:48:04.849 align:start position:0% internet so how penalties work in ethereal<00:48:02.760> for<00:48:03.119> being<00:48:03.540> lazy<00:48:04.079> right<00:48:04.319> this<00:48:04.680> is 00:48:04.849 --> 00:48:04.859 align:start position:0% ethereal for being lazy right this is 00:48:04.859 --> 00:48:07.550 align:start position:0% ethereal for being lazy right this is either<00:48:05.040> you're<00:48:05.700> offline<00:48:06.240> or<00:48:07.079> you're<00:48:07.260> not 00:48:07.550 --> 00:48:07.560 align:start position:0% either you're offline or you're not 00:48:07.560 --> 00:48:09.170 align:start position:0% either you're offline or you're not keeping<00:48:07.920> up<00:48:08.040> or<00:48:08.339> something<00:48:08.460> of<00:48:08.700> that<00:48:08.819> nature 00:48:09.170 --> 00:48:09.180 align:start position:0% keeping up or something of that nature 00:48:09.180 --> 00:48:11.930 align:start position:0% keeping up or something of that nature the<00:48:10.020> uh<00:48:10.500> that's<00:48:10.740> considered<00:48:11.160> a<00:48:11.220> penalty<00:48:11.640> so 00:48:11.930 --> 00:48:11.940 align:start position:0% the uh that's considered a penalty so 00:48:11.940 --> 00:48:13.730 align:start position:0% the uh that's considered a penalty so what<00:48:12.359> a<00:48:12.540> penalty<00:48:12.839> can<00:48:13.079> be<00:48:13.140> is<00:48:13.319> it<00:48:13.500> can<00:48:13.680> either 00:48:13.730 --> 00:48:13.740 align:start position:0% what a penalty can be is it can either 00:48:13.740 --> 00:48:15.349 align:start position:0% what a penalty can be is it can either be<00:48:13.980> a<00:48:14.099> reduced<00:48:14.460> in<00:48:14.520> rewards<00:48:14.940> that<00:48:15.060> you<00:48:15.180> receive 00:48:15.349 --> 00:48:15.359 align:start position:0% be a reduced in rewards that you receive 00:48:15.359 --> 00:48:18.589 align:start position:0% be a reduced in rewards that you receive or<00:48:15.599> it<00:48:15.780> could<00:48:15.900> actually<00:48:16.079> be<00:48:16.640> uh<00:48:17.640> where<00:48:18.359> what 00:48:18.589 --> 00:48:18.599 align:start position:0% or it could actually be uh where what 00:48:18.599 --> 00:48:21.230 align:start position:0% or it could actually be uh where what you<00:48:18.839> would<00:48:19.079> have<00:48:19.200> gotten<00:48:19.560> if<00:48:19.980> you<00:48:20.160> were<00:48:20.400> uh 00:48:21.230 --> 00:48:21.240 align:start position:0% you would have gotten if you were uh 00:48:21.240 --> 00:48:24.410 align:start position:0% you would have gotten if you were uh operating<00:48:21.720> optimally<00:48:22.339> is<00:48:23.339> deducted<00:48:24.119> so 00:48:24.410 --> 00:48:24.420 align:start position:0% operating optimally is deducted so 00:48:24.420 --> 00:48:26.569 align:start position:0% operating optimally is deducted so you're<00:48:24.660> slashed<00:48:25.200> very<00:48:25.560> small<00:48:25.800> amounts<00:48:26.160> so<00:48:26.400> say 00:48:26.569 --> 00:48:26.579 align:start position:0% you're slashed very small amounts so say 00:48:26.579 --> 00:48:30.050 align:start position:0% you're slashed very small amounts so say you're<00:48:27.180> uh<00:48:27.780> so<00:48:28.079> in<00:48:28.980> a<00:48:29.160> day<00:48:29.280> you<00:48:29.819> know<00:48:29.880> maybe 00:48:30.050 --> 00:48:30.060 align:start position:0% you're uh so in a day you know maybe 00:48:30.060 --> 00:48:32.390 align:start position:0% you're uh so in a day you know maybe your<00:48:30.359> internet<00:48:30.660> goes<00:48:31.140> out<00:48:31.260> for<00:48:31.500> 30<00:48:31.859> minutes<00:48:32.099> or 00:48:32.390 --> 00:48:32.400 align:start position:0% your internet goes out for 30 minutes or 00:48:32.400 --> 00:48:35.510 align:start position:0% your internet goes out for 30 minutes or something<00:48:32.640> like<00:48:32.940> that<00:48:33.260> you're<00:48:34.260> deducted<00:48:34.980> what 00:48:35.510 --> 00:48:35.520 align:start position:0% something like that you're deducted what 00:48:35.520 --> 00:48:37.370 align:start position:0% something like that you're deducted what profit<00:48:36.060> you<00:48:36.300> would<00:48:36.420> have<00:48:36.540> made<00:48:36.660> in<00:48:36.960> that<00:48:37.140> 30 00:48:37.370 --> 00:48:37.380 align:start position:0% profit you would have made in that 30 00:48:37.380 --> 00:48:40.430 align:start position:0% profit you would have made in that 30 minutes<00:48:37.680> so<00:48:38.520> you<00:48:38.880> lose<00:48:39.119> out<00:48:39.359> on<00:48:39.780> that<00:48:39.960> those<00:48:40.260> 30 00:48:40.430 --> 00:48:40.440 align:start position:0% minutes so you lose out on that those 30 00:48:40.440 --> 00:48:42.710 align:start position:0% minutes so you lose out on that those 30 minutes<00:48:40.680> of<00:48:40.920> reward<00:48:41.220> but<00:48:41.579> then<00:48:41.880> it 00:48:42.710 --> 00:48:42.720 align:start position:0% minutes of reward but then it 00:48:42.720 --> 00:48:44.329 align:start position:0% minutes of reward but then it essentially<00:48:43.079> is<00:48:43.260> almost<00:48:43.500> like<00:48:43.680> you<00:48:43.859> lost<00:48:43.980> an 00:48:44.329 --> 00:48:44.339 align:start position:0% essentially is almost like you lost an 00:48:44.339 --> 00:48:46.670 align:start position:0% essentially is almost like you lost an hour<00:48:44.579> right<00:48:45.000> other<00:48:45.540> words<00:48:45.780> because<00:48:46.020> it's<00:48:46.319> you 00:48:46.670 --> 00:48:46.680 align:start position:0% hour right other words because it's you 00:48:46.680 --> 00:48:49.430 align:start position:0% hour right other words because it's you know<00:48:46.740> it's<00:48:46.920> deducted<00:48:47.400> right<00:48:47.700> so 00:48:49.430 --> 00:48:49.440 align:start position:0% know it's deducted right so 00:48:49.440 --> 00:48:51.950 align:start position:0% know it's deducted right so so<00:48:50.160> that's<00:48:50.579> where<00:48:50.880> you<00:48:51.240> can<00:48:51.300> kind<00:48:51.480> of<00:48:51.599> gauge 00:48:51.950 --> 00:48:51.960 align:start position:0% so that's where you can kind of gauge 00:48:51.960 --> 00:48:53.750 align:start position:0% so that's where you can kind of gauge you<00:48:52.319> know<00:48:52.380> you<00:48:52.680> might<00:48:52.800> not<00:48:52.980> be<00:48:53.160> as<00:48:53.339> profitable 00:48:53.750 --> 00:48:53.760 align:start position:0% you know you might not be as profitable 00:48:53.760 --> 00:48:57.349 align:start position:0% you know you might not be as profitable even<00:48:54.180> if<00:48:54.420> you're<00:48:54.599> in<00:48:54.780> a<00:48:55.020> a<00:48:55.260> an<00:48:55.980> area<00:48:56.220> where<00:48:57.000> your 00:48:57.349 --> 00:48:57.359 align:start position:0% even if you're in a a an area where your 00:48:57.359 --> 00:48:58.670 align:start position:0% even if you're in a a an area where your internet<00:48:57.480> kind<00:48:57.839> of<00:48:57.960> cuts<00:48:58.200> in<00:48:58.260> and<00:48:58.380> out<00:48:58.500> or 00:48:58.670 --> 00:48:58.680 align:start position:0% internet kind of cuts in and out or 00:48:58.680 --> 00:48:59.990 align:start position:0% internet kind of cuts in and out or something<00:48:58.800> like<00:48:58.980> that<00:48:59.160> you<00:48:59.579> just<00:48:59.700> need<00:48:59.880> to 00:48:59.990 --> 00:49:00.000 align:start position:0% something like that you just need to 00:49:00.000 --> 00:49:01.609 align:start position:0% something like that you just need to kind<00:49:00.180> of<00:49:00.240> gauge<00:49:00.480> what<00:49:00.780> that<00:49:01.020> might<00:49:01.319> look<00:49:01.500> like 00:49:01.609 --> 00:49:01.619 align:start position:0% kind of gauge what that might look like 00:49:01.619 --> 00:49:04.130 align:start position:0% kind of gauge what that might look like and<00:49:01.920> maybe<00:49:02.339> it's<00:49:02.520> worth<00:49:02.700> running<00:49:02.940> a<00:49:03.300> validator 00:49:04.130 --> 00:49:04.140 align:start position:0% and maybe it's worth running a validator 00:49:04.140 --> 00:49:07.190 align:start position:0% and maybe it's worth running a validator on<00:49:04.619> uh<00:49:05.099> one<00:49:05.520> of<00:49:05.579> the<00:49:05.640> test<00:49:05.760> networks<00:49:06.300> to<00:49:06.960> kind 00:49:07.190 --> 00:49:07.200 align:start position:0% on uh one of the test networks to kind 00:49:07.200 --> 00:49:09.170 align:start position:0% on uh one of the test networks to kind of<00:49:07.319> see<00:49:07.560> what<00:49:07.920> the<00:49:08.099> performance<00:49:08.460> is<00:49:08.700> like<00:49:08.880> to 00:49:09.170 --> 00:49:09.180 align:start position:0% of see what the performance is like to 00:49:09.180 --> 00:49:10.730 align:start position:0% of see what the performance is like to see<00:49:09.300> okay<00:49:09.540> would<00:49:09.780> this<00:49:09.960> be<00:49:10.079> profitable<00:49:10.500> would 00:49:10.730 --> 00:49:10.740 align:start position:0% see okay would this be profitable would 00:49:10.740 --> 00:49:12.950 align:start position:0% see okay would this be profitable would this<00:49:10.980> be<00:49:11.160> worth<00:49:11.339> going 00:49:12.950 --> 00:49:12.960 align:start position:0% this be worth going 00:49:12.960 --> 00:49:14.930 align:start position:0% this be worth going um<00:49:13.079> but<00:49:13.380> then<00:49:13.619> uh<00:49:14.040> there<00:49:14.400> are<00:49:14.520> you<00:49:14.819> know 00:49:14.930 --> 00:49:14.940 align:start position:0% um but then uh there are you know 00:49:14.940 --> 00:49:18.170 align:start position:0% um but then uh there are you know Solutions<00:49:15.359> and<00:49:15.720> uh<00:49:16.200> I'll<00:49:17.099> mentioned<00:49:17.579> through 00:49:18.170 --> 00:49:18.180 align:start position:0% Solutions and uh I'll mentioned through 00:49:18.180 --> 00:49:21.230 align:start position:0% Solutions and uh I'll mentioned through Cloud<00:49:18.420> that<00:49:19.140> are<00:49:19.440> putting<00:49:19.980> uh<00:49:20.640> putting<00:49:21.060> a<00:49:21.180> lot 00:49:21.230 --> 00:49:21.240 align:start position:0% Cloud that are putting uh putting a lot 00:49:21.240 --> 00:49:24.170 align:start position:0% Cloud that are putting uh putting a lot of<00:49:21.359> work<00:49:21.540> into<00:49:21.960> getting<00:49:22.859> servers<00:49:23.640> and<00:49:23.940> getting 00:49:24.170 --> 00:49:24.180 align:start position:0% of work into getting servers and getting 00:49:24.180 --> 00:49:26.390 align:start position:0% of work into getting servers and getting Hardware<00:49:24.540> into<00:49:25.500> different<00:49:25.920> parts<00:49:26.160> of<00:49:26.339> the 00:49:26.390 --> 00:49:26.400 align:start position:0% Hardware into different parts of the 00:49:26.400 --> 00:49:29.089 align:start position:0% Hardware into different parts of the world<00:49:26.579> into<00:49:26.940> different<00:49:27.359> regions<00:49:27.740> uh<00:49:28.740> that<00:49:28.980> are 00:49:29.089 --> 00:49:29.099 align:start position:0% world into different regions uh that are 00:49:29.099 --> 00:49:31.309 align:start position:0% world into different regions uh that are kind<00:49:29.339> of<00:49:29.400> outside<00:49:29.760> of<00:49:30.180> the<00:49:30.480> you<00:49:30.780> know<00:49:30.900> Cloud 00:49:31.309 --> 00:49:31.319 align:start position:0% kind of outside of the you know Cloud 00:49:31.319 --> 00:49:33.410 align:start position:0% kind of outside of the you know Cloud gigs<00:49:32.220> so<00:49:32.400> that<00:49:32.520> if<00:49:32.640> you<00:49:32.760> really<00:49:32.880> do<00:49:33.060> have<00:49:33.240> bad 00:49:33.410 --> 00:49:33.420 align:start position:0% gigs so that if you really do have bad 00:49:33.420 --> 00:49:35.870 align:start position:0% gigs so that if you really do have bad internet<00:49:33.680> there<00:49:34.680> there<00:49:35.099> will<00:49:35.339> be<00:49:35.520> options 00:49:35.870 --> 00:49:35.880 align:start position:0% internet there there will be options 00:49:35.880 --> 00:49:39.170 align:start position:0% internet there there will be options where<00:49:36.660> you<00:49:36.839> can<00:49:36.900> deploy<00:49:37.319> you<00:49:37.859> know<00:49:37.920> to<00:49:38.460> uh<00:49:39.000> to 00:49:39.170 --> 00:49:39.180 align:start position:0% where you can deploy you know to uh to 00:49:39.180 --> 00:49:41.329 align:start position:0% where you can deploy you know to uh to Hardware<00:49:39.480> providers<00:49:40.200> that<00:49:40.740> aren't<00:49:40.920> tied<00:49:41.160> to 00:49:41.329 --> 00:49:41.339 align:start position:0% Hardware providers that aren't tied to 00:49:41.339 --> 00:49:43.910 align:start position:0% Hardware providers that aren't tied to that<00:49:41.579> same<00:49:41.760> like<00:49:41.940> Cloud<00:49:42.599> cluster<00:49:43.260> that<00:49:43.800> we 00:49:43.910 --> 00:49:43.920 align:start position:0% that same like Cloud cluster that we 00:49:43.920 --> 00:49:48.130 align:start position:0% that same like Cloud cluster that we were<00:49:44.099> talking<00:49:44.280> about<00:49:44.460> earlier 00:49:48.130 --> 00:49:48.140 align:start position:0% 00:49:48.140 --> 00:49:50.210 align:start position:0% your<00:49:49.140> questions 00:49:50.210 --> 00:49:50.220 align:start position:0% your questions 00:49:50.220 --> 00:49:52.490 align:start position:0% your questions oh<00:49:50.760> and<00:49:50.880> if<00:49:51.000> you<00:49:51.119> don't<00:49:51.240> have<00:49:51.359> 32<00:49:51.780> weeks<00:49:52.140> so<00:49:52.380> if 00:49:52.490 --> 00:49:52.500 align:start position:0% oh and if you don't have 32 weeks so if 00:49:52.500 --> 00:49:54.290 align:start position:0% oh and if you don't have 32 weeks so if you<00:49:52.560> don't<00:49:52.680> have<00:49:52.800> your<00:49:52.920> 32<00:49:53.220> 8<00:49:53.460> that's<00:49:53.700> uh<00:49:54.119> you 00:49:54.290 --> 00:49:54.300 align:start position:0% you don't have your 32 8 that's uh you 00:49:54.300 --> 00:49:56.270 align:start position:0% you don't have your 32 8 that's uh you are<00:49:54.480> you<00:49:54.839> can<00:49:55.020> still<00:49:55.140> run<00:49:55.319> notes<00:49:55.740> you<00:49:56.099> can 00:49:56.270 --> 00:49:56.280 align:start position:0% are you can still run notes you can 00:49:56.280 --> 00:49:57.530 align:start position:0% are you can still run notes you can still<00:49:56.400> run<00:49:56.640> notes<00:49:57.000> you<00:49:57.119> won't<00:49:57.359> get<00:49:57.480> any 00:49:57.530 --> 00:49:57.540 align:start position:0% still run notes you won't get any 00:49:57.540 --> 00:49:59.030 align:start position:0% still run notes you won't get any rewards<00:49:58.020> for<00:49:58.140> them 00:49:59.030 --> 00:49:59.040 align:start position:0% rewards for them 00:49:59.040 --> 00:50:02.569 align:start position:0% rewards for them um<00:49:59.520> but<00:50:00.119> uh<00:50:00.660> uh<00:50:01.079> you<00:50:01.319> you<00:50:01.680> can<00:50:02.040> you<00:50:02.339> know<00:50:02.460> there 00:50:02.569 --> 00:50:02.579 align:start position:0% um but uh uh you you can you know there 00:50:02.579 --> 00:50:05.450 align:start position:0% um but uh uh you you can you know there are<00:50:02.760> other<00:50:03.000> staking<00:50:03.839> uh<00:50:04.740> cooling<00:50:05.160> options 00:50:05.450 --> 00:50:05.460 align:start position:0% are other staking uh cooling options 00:50:05.460 --> 00:50:08.690 align:start position:0% are other staking uh cooling options like<00:50:05.819> rocket<00:50:06.359> pool<00:50:06.540> is<00:50:06.960> a<00:50:07.200> good<00:50:07.859> one 00:50:08.690 --> 00:50:08.700 align:start position:0% like rocket pool is a good one 00:50:08.700 --> 00:50:10.730 align:start position:0% like rocket pool is a good one also<00:50:09.240> if<00:50:09.480> you<00:50:09.599> have<00:50:09.720> friends<00:50:09.900> that<00:50:10.140> trust<00:50:10.560> you 00:50:10.730 --> 00:50:10.740 align:start position:0% also if you have friends that trust you 00:50:10.740 --> 00:50:13.370 align:start position:0% also if you have friends that trust you then<00:50:11.400> maybe<00:50:11.700> you<00:50:11.880> can<00:50:12.060> aggregate<00:50:12.599> some<00:50:12.900> people 00:50:13.370 --> 00:50:13.380 align:start position:0% then maybe you can aggregate some people 00:50:13.380 --> 00:50:15.829 align:start position:0% then maybe you can aggregate some people do<00:50:13.680> aggregate<00:50:14.160> amongst<00:50:14.880> uh<00:50:15.300> groups<00:50:15.720> of 00:50:15.829 --> 00:50:15.839 align:start position:0% do aggregate amongst uh groups of 00:50:15.839 --> 00:50:18.410 align:start position:0% do aggregate amongst uh groups of friends<00:50:16.020> who<00:50:16.380> may<00:50:16.619> not<00:50:16.740> have<00:50:16.980> uh<00:50:17.819> enough<00:50:17.940> eth 00:50:18.410 --> 00:50:18.420 align:start position:0% friends who may not have uh enough eth 00:50:18.420 --> 00:50:19.609 align:start position:0% friends who may not have uh enough eth and<00:50:18.660> then<00:50:18.780> you<00:50:18.960> know 00:50:19.609 --> 00:50:19.619 align:start position:0% and then you know 00:50:19.619 --> 00:50:21.770 align:start position:0% and then you know add<00:50:20.160> a<00:50:20.339> little<00:50:20.400> point<00:50:20.640> of<00:50:20.819> trust<00:50:21.060> but<00:50:21.300> it's<00:50:21.660> a 00:50:21.770 --> 00:50:21.780 align:start position:0% add a little point of trust but it's a 00:50:21.780 --> 00:50:24.950 align:start position:0% add a little point of trust but it's a it's<00:50:22.020> an<00:50:22.140> option 00:50:24.950 --> 00:50:24.960 align:start position:0% 00:50:24.960 --> 00:50:56.450 align:start position:0% uh<00:50:25.500> yes<00:50:25.680> sir 00:50:56.450 --> 00:50:56.460 align:start position:0% 00:50:56.460 --> 00:51:00.290 align:start position:0% that<00:50:57.359> would<00:50:57.540> be<00:50:57.660> the<00:50:57.839> case<00:50:58.079> I<00:50:58.740> would<00:50:58.859> say<00:50:59.040> if<00:50:59.940> if 00:51:00.290 --> 00:51:00.300 align:start position:0% that would be the case I would say if if 00:51:00.300 --> 00:51:02.870 align:start position:0% that would be the case I would say if if no<00:51:00.599> software<00:51:01.079> was<00:51:01.200> maintained<00:51:01.740> seriously<00:51:02.339> so 00:51:02.870 --> 00:51:02.880 align:start position:0% no software was maintained seriously so 00:51:02.880 --> 00:51:05.210 align:start position:0% no software was maintained seriously so with<00:51:03.240> no<00:51:03.480> software<00:51:03.900> people<00:51:04.319> could 00:51:05.210 --> 00:51:05.220 align:start position:0% with no software people could 00:51:05.220 --> 00:51:09.710 align:start position:0% with no software people could minimize<00:51:06.000> a<00:51:06.300> lot<00:51:06.420> of<00:51:06.780> uh<00:51:07.140> cost<00:51:07.579> uh<00:51:08.579> and<00:51:09.180> and 00:51:09.710 --> 00:51:09.720 align:start position:0% minimize a lot of uh cost uh and and 00:51:09.720 --> 00:51:11.450 align:start position:0% minimize a lot of uh cost uh and and also<00:51:10.140> minimize<00:51:10.500> certain<00:51:10.740> risks<00:51:11.099> by<00:51:11.339> just 00:51:11.450 --> 00:51:11.460 align:start position:0% also minimize certain risks by just 00:51:11.460 --> 00:51:14.210 align:start position:0% also minimize certain risks by just running<00:51:11.640> it<00:51:11.819> at<00:51:11.940> home<00:51:12.059> so<00:51:12.839> while<00:51:13.200> yes<00:51:13.619> you<00:51:14.099> know 00:51:14.210 --> 00:51:14.220 align:start position:0% running it at home so while yes you know 00:51:14.220 --> 00:51:17.150 align:start position:0% running it at home so while yes you know you<00:51:14.940> could<00:51:15.119> have<00:51:15.420> you<00:51:16.260> know<00:51:16.319> large<00:51:16.680> providers 00:51:17.150 --> 00:51:17.160 align:start position:0% you could have you know large providers 00:51:17.160 --> 00:51:19.490 align:start position:0% you could have you know large providers like<00:51:17.339> AWS<00:51:17.819> you<00:51:18.420> know<00:51:18.480> it<00:51:18.960> really<00:51:19.020> comes<00:51:19.380> down 00:51:19.490 --> 00:51:19.500 align:start position:0% like AWS you know it really comes down 00:51:19.500 --> 00:51:21.530 align:start position:0% like AWS you know it really comes down to<00:51:19.800> you<00:51:20.099> know<00:51:20.160> six<00:51:20.460> providers<00:51:21.059> as<00:51:21.359> you 00:51:21.530 --> 00:51:21.540 align:start position:0% to you know six providers as you 00:51:21.540 --> 00:51:23.510 align:start position:0% to you know six providers as you mentioned<00:51:21.720> right<00:51:21.900> six<00:51:22.200> providers 00:51:23.510 --> 00:51:23.520 align:start position:0% mentioned right six providers 00:51:23.520 --> 00:51:24.290 align:start position:0% mentioned right six providers um 00:51:24.290 --> 00:51:24.300 align:start position:0% um 00:51:24.300 --> 00:51:26.809 align:start position:0% um sure<00:51:24.839> you<00:51:25.200> can<00:51:25.260> go<00:51:25.380> that<00:51:25.619> way<00:51:25.740> and<00:51:26.339> send<00:51:26.579> money 00:51:26.809 --> 00:51:26.819 align:start position:0% sure you can go that way and send money 00:51:26.819 --> 00:51:29.630 align:start position:0% sure you can go that way and send money each<00:51:27.119> month<00:51:27.300> or<00:51:27.839> you<00:51:28.079> can<00:51:28.140> have<00:51:28.440> an<00:51:29.040> old<00:51:29.280> laptop 00:51:29.630 --> 00:51:29.640 align:start position:0% each month or you can have an old laptop 00:51:29.640 --> 00:51:32.150 align:start position:0% each month or you can have an old laptop running<00:51:30.420> uh<00:51:31.319> where<00:51:31.500> you're<00:51:31.680> keeping<00:51:31.920> all<00:51:32.040> the 00:51:32.150 --> 00:51:32.160 align:start position:0% running uh where you're keeping all the 00:51:32.160 --> 00:51:33.650 align:start position:0% running uh where you're keeping all the rewards<00:51:32.520> and<00:51:32.700> you<00:51:32.880> don't<00:51:33.000> have<00:51:33.180> that<00:51:33.420> that 00:51:33.650 --> 00:51:33.660 align:start position:0% rewards and you don't have that that 00:51:33.660 --> 00:51:37.849 align:start position:0% rewards and you don't have that that overhead<00:51:34.140> and<00:51:34.440> it's<00:51:34.619> that<00:51:34.980> simple<00:51:35.220> to<00:51:35.819> run<00:51:36.059> uh 00:51:37.849 --> 00:51:37.859 align:start position:0% overhead and it's that simple to run uh 00:51:37.859 --> 00:51:41.030 align:start position:0% overhead and it's that simple to run uh that<00:51:38.520> so<00:51:39.359> I<00:51:39.660> think<00:51:39.960> you're<00:51:40.140> right<00:51:40.440> in<00:51:40.740> terms<00:51:40.920> of 00:51:41.030 --> 00:51:41.040 align:start position:0% that so I think you're right in terms of 00:51:41.040 --> 00:51:42.829 align:start position:0% that so I think you're right in terms of just<00:51:41.280> what<00:51:41.520> tends<00:51:41.880> to<00:51:41.940> happen<00:51:42.240> in<00:51:42.540> these<00:51:42.660> kind 00:51:42.829 --> 00:51:42.839 align:start position:0% just what tends to happen in these kind 00:51:42.839 --> 00:51:45.770 align:start position:0% just what tends to happen in these kind of<00:51:42.900> ecosystems<00:51:43.619> but<00:51:44.339> uh<00:51:44.940> but<00:51:45.240> I<00:51:45.359> think<00:51:45.480> because 00:51:45.770 --> 00:51:45.780 align:start position:0% of ecosystems but uh but I think because 00:51:45.780 --> 00:51:48.109 align:start position:0% of ecosystems but uh but I think because of<00:51:46.140> the<00:51:46.260> way<00:51:46.440> that<00:51:47.160> that<00:51:47.579> theory<00:51:48.000> is 00:51:48.109 --> 00:51:48.119 align:start position:0% of the way that that theory is 00:51:48.119 --> 00:51:50.150 align:start position:0% of the way that that theory is approach's<00:51:48.839> sake<00:51:49.020> where<00:51:49.440> they<00:51:49.680> intentionally 00:51:50.150 --> 00:51:50.160 align:start position:0% approach's sake where they intentionally 00:51:50.160 --> 00:51:52.970 align:start position:0% approach's sake where they intentionally put<00:51:50.520> in<00:51:50.760> mechanisms<00:51:51.420> to<00:51:51.599> incentivize<00:51:52.200> more 00:51:52.970 --> 00:51:52.980 align:start position:0% put in mechanisms to incentivize more 00:51:52.980 --> 00:51:54.710 align:start position:0% put in mechanisms to incentivize more and<00:51:53.099> more<00:51:53.280> decentralization<00:51:53.940> I<00:51:54.420> think<00:51:54.599> the 00:51:54.710 --> 00:51:54.720 align:start position:0% and more decentralization I think the 00:51:54.720 --> 00:51:56.030 align:start position:0% and more decentralization I think the market<00:51:54.900> will 00:51:56.030 --> 00:51:56.040 align:start position:0% market will 00:51:56.040 --> 00:51:56.809 align:start position:0% market will um 00:51:56.809 --> 00:51:56.819 align:start position:0% um 00:51:56.819 --> 00:51:59.510 align:start position:0% um uh<00:51:57.599> will<00:51:57.900> will<00:51:58.140> match<00:51:58.380> that<00:51:58.680> right<00:51:59.040> and<00:51:59.400> I 00:51:59.510 --> 00:51:59.520 align:start position:0% uh will will match that right and I 00:51:59.520 --> 00:52:01.069 align:start position:0% uh will will match that right and I believe<00:51:59.700> there<00:52:00.119> are<00:52:00.240> going<00:52:00.359> to<00:52:00.480> be<00:52:00.599> a<00:52:00.839> lot<00:52:00.960> of 00:52:01.069 --> 00:52:01.079 align:start position:0% believe there are going to be a lot of 00:52:01.079 --> 00:52:03.290 align:start position:0% believe there are going to be a lot of options<00:52:01.380> for<00:52:01.859> node<00:52:02.280> software<00:52:02.640> in<00:52:03.059> the<00:52:03.180> future 00:52:03.290 --> 00:52:03.300 align:start position:0% options for node software in the future 00:52:03.300 --> 00:52:05.150 align:start position:0% options for node software in the future uh<00:52:03.900> there's<00:52:04.140> already<00:52:04.260> three<00:52:04.559> great<00:52:04.740> ones<00:52:04.980> out 00:52:05.150 --> 00:52:05.160 align:start position:0% uh there's already three great ones out 00:52:05.160 --> 00:52:06.589 align:start position:0% uh there's already three great ones out there<00:52:05.280> uh<00:52:05.760> we're<00:52:05.880> building<00:52:06.059> one<00:52:06.240> ourselves 00:52:06.589 --> 00:52:06.599 align:start position:0% there uh we're building one ourselves 00:52:06.599 --> 00:52:08.030 align:start position:0% there uh we're building one ourselves and<00:52:06.839> we're<00:52:06.960> building<00:52:07.079> tools<00:52:07.500> that<00:52:07.559> allow<00:52:07.859> more 00:52:08.030 --> 00:52:08.040 align:start position:0% and we're building tools that allow more 00:52:08.040 --> 00:52:09.530 align:start position:0% and we're building tools that allow more people<00:52:08.160> to<00:52:08.339> build<00:52:08.460> them<00:52:08.640> so<00:52:08.880> I<00:52:09.300> think<00:52:09.420> the 00:52:09.530 --> 00:52:09.540 align:start position:0% people to build them so I think the 00:52:09.540 --> 00:52:11.270 align:start position:0% people to build them so I think the future<00:52:09.720> is<00:52:09.900> really<00:52:10.020> bright<00:52:10.260> with<00:52:10.500> that 00:52:11.270 --> 00:52:11.280 align:start position:0% future is really bright with that 00:52:11.280 --> 00:52:13.430 align:start position:0% future is really bright with that um<00:52:11.400> so<00:52:11.700> that's<00:52:12.119> my<00:52:12.359> thought 00:52:13.430 --> 00:52:13.440 align:start position:0% um so that's my thought 00:52:13.440 --> 00:52:18.290 align:start position:0% um so that's my thought um<00:52:13.640> may<00:52:14.640> I<00:52:14.760> ask<00:52:14.940> if<00:52:15.420> uh<00:52:15.900> no<00:52:16.260> uh<00:52:17.180> launcher<00:52:18.180> is 00:52:18.290 --> 00:52:18.300 align:start position:0% um may I ask if uh no uh launcher is 00:52:18.300 --> 00:52:22.670 align:start position:0% um may I ask if uh no uh launcher is capable<00:52:19.020> to<00:52:19.500> integrate<00:52:20.280> the<00:52:21.180> DVD<00:52:21.720> no 00:52:22.670 --> 00:52:22.680 align:start position:0% capable to integrate the DVD no 00:52:22.680 --> 00:52:25.190 align:start position:0% capable to integrate the DVD no deployment 00:52:25.190 --> 00:52:25.200 align:start position:0% deployment 00:52:25.200 --> 00:52:29.630 align:start position:0% deployment DVD 00:52:29.630 --> 00:52:29.640 align:start position:0% 00:52:29.640 --> 00:52:58.220 align:start position:0% foreign 00:52:58.220 --> 00:52:58.230 align:start position:0% 00:52:58.230 --> 00:53:27.010 align:start position:0% [Music] 00:53:27.010 --> 00:53:27.020 align:start position:0% 00:53:27.020 --> 00:53:30.170 align:start position:0% so<00:53:28.020> it's<00:53:28.319> very<00:53:28.680> adaptable<00:53:29.280> it<00:53:29.520> can<00:53:29.700> apply<00:53:30.000> to 00:53:30.170 --> 00:53:30.180 align:start position:0% so it's very adaptable it can apply to 00:53:30.180 --> 00:53:32.450 align:start position:0% so it's very adaptable it can apply to any<00:53:30.540> parts<00:53:30.780> of<00:53:30.960> the<00:53:31.079> node<00:53:31.260> any<00:53:31.859> parts<00:53:32.160> of<00:53:32.339> any 00:53:32.450 --> 00:53:32.460 align:start position:0% any parts of the node any parts of any 00:53:32.460 --> 00:53:33.829 align:start position:0% any parts of the node any parts of any container<00:53:32.940> one<00:53:33.240> of<00:53:33.420> the<00:53:33.480> things<00:53:33.660> we're 00:53:33.829 --> 00:53:33.839 align:start position:0% container one of the things we're 00:53:33.839 --> 00:53:35.210 align:start position:0% container one of the things we're building<00:53:34.020> right<00:53:34.260> now<00:53:34.440> is<00:53:34.559> the<00:53:34.740> ability<00:53:34.980> to 00:53:35.210 --> 00:53:35.220 align:start position:0% building right now is the ability to 00:53:35.220 --> 00:53:36.829 align:start position:0% building right now is the ability to deploy<00:53:35.579> multiple<00:53:36.000> containers<00:53:36.480> so<00:53:36.720> there's 00:53:36.829 --> 00:53:36.839 align:start position:0% deploy multiple containers so there's 00:53:36.839 --> 00:53:39.829 align:start position:0% deploy multiple containers so there's some<00:53:37.079> like<00:53:37.559> polygon<00:53:38.220> that<00:53:39.000> uh<00:53:39.480> require 00:53:39.829 --> 00:53:39.839 align:start position:0% some like polygon that uh require 00:53:39.839 --> 00:53:41.870 align:start position:0% some like polygon that uh require multiple<00:53:40.440> containers<00:53:40.920> right<00:53:41.280> in<00:53:41.520> order<00:53:41.700> to 00:53:41.870 --> 00:53:41.880 align:start position:0% multiple containers right in order to 00:53:41.880 --> 00:53:43.910 align:start position:0% multiple containers right in order to run<00:53:42.059> their<00:53:42.300> node<00:53:42.720> it's<00:53:43.200> actually<00:53:43.440> multiple 00:53:43.910 --> 00:53:43.920 align:start position:0% run their node it's actually multiple 00:53:43.920 --> 00:53:45.890 align:start position:0% run their node it's actually multiple notes<00:53:44.220> uh<00:53:44.880> so<00:53:45.119> we're<00:53:45.240> building<00:53:45.420> in<00:53:45.720> that 00:53:45.890 --> 00:53:45.900 align:start position:0% notes uh so we're building in that 00:53:45.900 --> 00:53:47.930 align:start position:0% notes uh so we're building in that ability<00:53:46.380> to<00:53:46.619> have<00:53:46.800> all<00:53:47.220> those<00:53:47.339> nodes<00:53:47.640> all 00:53:47.930 --> 00:53:47.940 align:start position:0% ability to have all those nodes all 00:53:47.940 --> 00:53:50.210 align:start position:0% ability to have all those nodes all orchestrated<00:53:48.480> and<00:53:48.660> working<00:53:48.900> together<00:53:49.220> uh 00:53:50.210 --> 00:53:50.220 align:start position:0% orchestrated and working together uh 00:53:50.220 --> 00:53:52.010 align:start position:0% orchestrated and working together uh without<00:53:50.579> needing<00:53:51.240> to<00:53:51.300> do<00:53:51.420> it<00:53:51.599> manually 00:53:52.010 --> 00:53:52.020 align:start position:0% without needing to do it manually 00:53:52.020 --> 00:53:53.630 align:start position:0% without needing to do it manually because<00:53:52.319> it's<00:53:52.559> all<00:53:52.740> handled<00:53:53.160> through<00:53:53.400> the 00:53:53.630 --> 00:53:53.640 align:start position:0% because it's all handled through the 00:53:53.640 --> 00:53:55.569 align:start position:0% because it's all handled through the engine<00:53:54.000> itself 00:53:55.569 --> 00:53:55.579 align:start position:0% engine itself 00:53:55.579 --> 00:54:03.349 align:start position:0% engine itself thank<00:53:56.579> you 00:54:03.349 --> 00:54:03.359 align:start position:0% 00:54:03.359 --> 00:54:06.829 align:start position:0% so<00:54:04.020> uh<00:54:04.680> there<00:54:05.160> are<00:54:05.400> uh<00:54:05.940> so 00:54:06.829 --> 00:54:06.839 align:start position:0% so uh there are uh so 00:54:06.839 --> 00:54:09.290 align:start position:0% so uh there are uh so on<00:54:07.280> ethereum.org<00:54:08.280> there's<00:54:08.700> all<00:54:09.119> that 00:54:09.290 --> 00:54:09.300 align:start position:0% on ethereum.org there's all that 00:54:09.300 --> 00:54:10.849 align:start position:0% on ethereum.org there's all that information<00:54:09.540> so<00:54:09.960> I<00:54:10.140> definitely<00:54:10.380> check<00:54:10.619> it<00:54:10.740> out 00:54:10.849 --> 00:54:10.859 align:start position:0% information so I definitely check it out 00:54:10.859 --> 00:54:13.130 align:start position:0% information so I definitely check it out there<00:54:11.040> uh<00:54:12.000> from<00:54:12.240> what<00:54:12.420> I<00:54:12.540> remember<00:54:12.720> from 00:54:13.130 --> 00:54:13.140 align:start position:0% there uh from what I remember from 00:54:13.140 --> 00:54:15.770 align:start position:0% there uh from what I remember from looking<00:54:13.380> at<00:54:13.559> it<00:54:13.680> last<00:54:13.859> night<00:54:14.040> is<00:54:14.940> uh<00:54:15.480> they 00:54:15.770 --> 00:54:15.780 align:start position:0% looking at it last night is uh they 00:54:15.780 --> 00:54:18.770 align:start position:0% looking at it last night is uh they recommend<00:54:16.319> uh<00:54:17.040> kind<00:54:17.220> of<00:54:17.339> on<00:54:17.520> the<00:54:17.760> low<00:54:18.119> side<00:54:18.420> or 00:54:18.770 --> 00:54:18.780 align:start position:0% recommend uh kind of on the low side or 00:54:18.780 --> 00:54:24.250 align:start position:0% recommend uh kind of on the low side or on<00:54:19.260> the<00:54:19.440> recommended<00:54:20.280> side<00:54:20.520> was<00:54:21.480> a<00:54:21.960> uh<00:54:22.680> i7 00:54:24.250 --> 00:54:24.260 align:start position:0% on the recommended side was a uh i7 00:54:24.260 --> 00:54:27.530 align:start position:0% on the recommended side was a uh i7 4470<00:54:25.260> which<00:54:25.680> is<00:54:25.800> like<00:54:26.700> a<00:54:26.880> 15<00:54:27.059> year<00:54:27.359> old 00:54:27.530 --> 00:54:27.540 align:start position:0% 4470 which is like a 15 year old 00:54:27.540 --> 00:54:30.950 align:start position:0% 4470 which is like a 15 year old processor<00:54:28.079> so<00:54:28.579> so<00:54:29.579> yeah<00:54:30.119> and<00:54:30.300> I<00:54:30.540> said<00:54:30.660> it<00:54:30.839> for 00:54:30.950 --> 00:54:30.960 align:start position:0% processor so so yeah and I said it for 00:54:30.960 --> 00:54:32.210 align:start position:0% processor so so yeah and I said it for like<00:54:31.079> 15<00:54:31.200> years<00:54:31.440> ago<00:54:31.680> or<00:54:31.859> something<00:54:31.980> so 00:54:32.210 --> 00:54:32.220 align:start position:0% like 15 years ago or something so 00:54:32.220 --> 00:54:34.910 align:start position:0% like 15 years ago or something so anyways<00:54:33.059> yeah<00:54:33.540> ethereum<00:54:34.319> is<00:54:34.500> very<00:54:34.740> well 00:54:34.910 --> 00:54:34.920 align:start position:0% anyways yeah ethereum is very well 00:54:34.920 --> 00:54:38.569 align:start position:0% anyways yeah ethereum is very well equipped<00:54:35.359> for<00:54:36.359> uh<00:54:36.960> minimal<00:54:37.500> uh<00:54:38.280> Hardware 00:54:38.569 --> 00:54:38.579 align:start position:0% equipped for uh minimal uh Hardware 00:54:38.579 --> 00:54:40.670 align:start position:0% equipped for uh minimal uh Hardware requirements<00:54:39.240> unlike<00:54:40.079> a<00:54:40.319> lot<00:54:40.440> of<00:54:40.559> other 00:54:40.670 --> 00:54:40.680 align:start position:0% requirements unlike a lot of other 00:54:40.680 --> 00:54:47.510 align:start position:0% requirements unlike a lot of other networks<00:54:41.400> out<00:54:41.579> there 00:54:47.510 --> 00:54:47.520 align:start position:0% 00:54:47.520 --> 00:54:49.670 align:start position:0% no<00:54:48.059> you're<00:54:48.359> just<00:54:48.480> on<00:54:48.780> the<00:54:48.900> server<00:54:49.260> itself 00:54:49.670 --> 00:54:49.680 align:start position:0% no you're just on the server itself 00:54:49.680 --> 00:54:52.309 align:start position:0% no you're just on the server itself needs<00:54:50.400> to<00:54:50.460> have<00:54:50.700> those<00:54:51.000> requirements 00:54:52.309 --> 00:54:52.319 align:start position:0% needs to have those requirements 00:54:52.319 --> 00:54:54.530 align:start position:0% needs to have those requirements um which<00:54:52.859> are<00:54:53.040> very<00:54:53.220> minimal<00:54:53.579> uh<00:54:54.180> and<00:54:54.420> then 00:54:54.530 --> 00:54:54.540 align:start position:0% um which are very minimal uh and then 00:54:54.540 --> 00:54:55.970 align:start position:0% um which are very minimal uh and then their<00:54:54.780> application<00:54:55.260> I<00:54:55.500> believe<00:54:55.619> you<00:54:55.740> can<00:54:55.859> just 00:54:55.970 --> 00:54:55.980 align:start position:0% their application I believe you can just 00:54:55.980 --> 00:54:58.010 align:start position:0% their application I believe you can just run<00:54:56.099> on<00:54:56.339> any<00:54:56.640> computer<00:54:57.300> that's<00:54:57.780> running 00:54:58.010 --> 00:54:58.020 align:start position:0% run on any computer that's running 00:54:58.020 --> 00:55:01.490 align:start position:0% run on any computer that's running either<00:54:58.380> Windows<00:54:58.920> Linux<00:54:59.280> or<00:54:59.700> uh<00:55:00.059> uh 00:55:01.490 --> 00:55:01.500 align:start position:0% either Windows Linux or uh uh 00:55:01.500 --> 00:55:05.870 align:start position:0% either Windows Linux or uh uh uh<00:55:01.680> apple<00:55:02.099> or<00:55:02.640> Mac<00:55:03.059> so 00:55:05.870 --> 00:55:05.880 align:start position:0% 00:55:05.880 --> 00:55:12.000 align:start position:0% got<00:55:06.240> two<00:55:06.540> minutes<00:55:06.660> yeah 00:55:12.000 --> 00:55:12.010 align:start position:0% 00:55:12.010 --> 00:55:15.170 align:start position:0% [Music] 00:55:15.170 --> 00:55:15.180 align:start position:0% 00:55:15.180 --> 00:55:19.130 align:start position:0% increase<00:55:15.720> your<00:55:16.260> profit<00:55:17.160> on<00:55:17.520> YouTube<00:55:18.140> by 00:55:19.130 --> 00:55:19.140 align:start position:0% increase your profit on YouTube by 00:55:19.140 --> 00:55:21.740 align:start position:0% increase your profit on YouTube by earning<00:55:19.740> like<00:55:19.980> the<00:55:20.280> big<00:55:20.579> clients 00:55:21.740 --> 00:55:21.750 align:start position:0% earning like the big clients 00:55:21.750 --> 00:55:29.089 align:start position:0% earning like the big clients [Music] 00:55:29.089 --> 00:55:29.099 align:start position:0% 00:55:29.099 --> 00:55:31.670 align:start position:0% absolutely<00:55:29.880> like<00:55:30.420> so<00:55:30.900> we<00:55:31.319> don't<00:55:31.440> have<00:55:31.559> to 00:55:31.670 --> 00:55:31.680 align:start position:0% absolutely like so we don't have to 00:55:31.680 --> 00:55:32.990 align:start position:0% absolutely like so we don't have to integrate<00:55:32.040> right<00:55:32.280> now<00:55:32.400> I<00:55:32.579> was<00:55:32.700> actually<00:55:32.819> just 00:55:32.990 --> 00:55:33.000 align:start position:0% integrate right now I was actually just 00:55:33.000 --> 00:55:34.970 align:start position:0% integrate right now I was actually just talking<00:55:33.119> about<00:55:33.359> yesterday<00:55:33.839> about<00:55:34.140> it<00:55:34.740> um<00:55:34.800> we 00:55:34.970 --> 00:55:34.980 align:start position:0% talking about yesterday about it um we 00:55:34.980 --> 00:55:36.589 align:start position:0% talking about yesterday about it um we don't<00:55:35.099> have<00:55:35.220> it<00:55:35.400> integrated<00:55:35.700> now<00:55:35.940> but<00:55:36.359> it's 00:55:36.589 --> 00:55:36.599 align:start position:0% don't have it integrated now but it's 00:55:36.599 --> 00:55:38.750 align:start position:0% don't have it integrated now but it's literally<00:55:36.960> service<00:55:37.319> that<00:55:37.619> you<00:55:37.740> run<00:55:37.980> alongside 00:55:38.750 --> 00:55:38.760 align:start position:0% literally service that you run alongside 00:55:38.760 --> 00:55:40.970 align:start position:0% literally service that you run alongside your<00:55:39.119> ethereum<00:55:39.480> validation<00:55:39.900> so<00:55:40.440> it's<00:55:40.740> a 00:55:40.970 --> 00:55:40.980 align:start position:0% your ethereum validation so it's a 00:55:40.980 --> 00:55:43.790 align:start position:0% your ethereum validation so it's a container<00:55:41.400> yes<00:55:41.940> we<00:55:42.359> can<00:55:42.540> absolutely<00:55:42.960> and<00:55:43.680> then 00:55:43.790 --> 00:55:43.800 align:start position:0% container yes we can absolutely and then 00:55:43.800 --> 00:55:45.109 align:start position:0% container yes we can absolutely and then that's<00:55:43.980> what<00:55:44.040> no<00:55:44.280> launcher<00:55:44.579> does<00:55:44.760> makes 00:55:45.109 --> 00:55:45.119 align:start position:0% that's what no launcher does makes 00:55:45.119 --> 00:55:47.990 align:start position:0% that's what no launcher does makes running<00:55:45.359> containers<00:55:45.960> super<00:55:46.800> easy<00:55:47.099> and<00:55:47.700> able 00:55:47.990 --> 00:55:48.000 align:start position:0% running containers super easy and able 00:55:48.000 --> 00:55:49.609 align:start position:0% running containers super easy and able to<00:55:48.059> do<00:55:48.180> it<00:55:48.240> in<00:55:48.359> a<00:55:48.420> programmatic<00:55:48.900> way<00:55:49.020> to<00:55:49.440> where 00:55:49.609 --> 00:55:49.619 align:start position:0% to do it in a programmatic way to where 00:55:49.619 --> 00:55:51.410 align:start position:0% to do it in a programmatic way to where it<00:55:49.740> all<00:55:50.040> automatically<00:55:50.579> connects<00:55:51.000> so<00:55:51.240> yes 00:55:51.410 --> 00:55:51.420 align:start position:0% it all automatically connects so yes 00:55:51.420 --> 00:55:58.670 align:start position:0% it all automatically connects so yes absolutely<00:55:52.380> possible 00:55:58.670 --> 00:55:58.680 align:start position:0% 00:55:58.680 --> 00:55:59.630 align:start position:0% um 00:55:59.630 --> 00:55:59.640 align:start position:0% um 00:55:59.640 --> 00:56:01.520 align:start position:0% um [Laughter] 00:56:01.520 --> 00:56:01.530 align:start position:0% [Laughter] 00:56:01.530 --> 00:56:04.790 align:start position:0% [Laughter] [Applause] 00:56:04.790 --> 00:56:04.800 align:start position:0% [Applause] 00:56:04.800 --> 00:56:07.309 align:start position:0% [Applause] um<00:56:05.040> I've<00:56:05.400> been<00:56:05.640> uh<00:56:06.119> running<00:56:06.359> with<00:56:06.839> my<00:56:07.079> own 00:56:07.309 --> 00:56:07.319 align:start position:0% um I've been uh running with my own 00:56:07.319 --> 00:56:08.329 align:start position:0% um I've been uh running with my own Hardware 00:56:08.329 --> 00:56:08.339 align:start position:0% Hardware 00:56:08.339 --> 00:56:10.130 align:start position:0% Hardware um<00:56:08.460> I<00:56:08.640> wanted<00:56:08.819> to<00:56:09.059> get<00:56:09.180> like<00:56:09.359> a<00:56:09.599> recommendation 00:56:10.130 --> 00:56:10.140 align:start position:0% um I wanted to get like a recommendation 00:56:10.140 --> 00:56:12.130 align:start position:0% um I wanted to get like a recommendation on<00:56:10.800> like<00:56:11.040> uh 00:56:12.130 --> 00:56:12.140 align:start position:0% on like uh 00:56:12.140 --> 00:56:15.530 align:start position:0% on like uh pretty<00:56:13.140> complicated<00:56:13.559> like<00:56:14.280> uh<00:56:15.000> you<00:56:15.300> mentioned 00:56:15.530 --> 00:56:15.540 align:start position:0% pretty complicated like uh you mentioned 00:56:15.540 --> 00:56:16.970 align:start position:0% pretty complicated like uh you mentioned like<00:56:15.720> the<00:56:15.960> resources<00:56:16.380> from<00:56:16.559> the<00:56:16.680> ethereum 00:56:16.970 --> 00:56:16.980 align:start position:0% like the resources from the ethereum 00:56:16.980 --> 00:56:18.950 align:start position:0% like the resources from the ethereum foundation<00:56:17.339> then<00:56:17.760> they<00:56:18.000> they<00:56:18.300> point<00:56:18.599> to<00:56:18.780> our 00:56:18.950 --> 00:56:18.960 align:start position:0% foundation then they they point to our 00:56:18.960 --> 00:56:21.950 align:start position:0% foundation then they they point to our random<00:56:19.260> guys<00:56:19.559> uh<00:56:20.160> medium<00:56:20.460> post<00:56:20.760> and<00:56:21.540> another 00:56:21.950 --> 00:56:21.960 align:start position:0% random guys uh medium post and another 00:56:21.960 --> 00:56:24.170 align:start position:0% random guys uh medium post and another random<00:56:22.440> guys<00:56:22.559> medium<00:56:22.920> post<00:56:23.160> which<00:56:23.460> is<00:56:23.640> uh<00:56:24.000> not 00:56:24.170 --> 00:56:24.180 align:start position:0% random guys medium post which is uh not 00:56:24.180 --> 00:56:26.450 align:start position:0% random guys medium post which is uh not updated<00:56:24.540> or<00:56:25.079> how<00:56:25.319> do<00:56:25.559> I<00:56:25.680> know<00:56:25.800> if<00:56:25.980> it's<00:56:26.099> update 00:56:26.450 --> 00:56:26.460 align:start position:0% updated or how do I know if it's update 00:56:26.460 --> 00:56:27.650 align:start position:0% updated or how do I know if it's update or<00:56:26.640> not 00:56:27.650 --> 00:56:27.660 align:start position:0% or not 00:56:27.660 --> 00:56:28.490 align:start position:0% or not um 00:56:28.490 --> 00:56:28.500 align:start position:0% um 00:56:28.500 --> 00:56:31.849 align:start position:0% um and<00:56:29.460> good<00:56:30.180> luck<00:56:30.359> if<00:56:30.660> you<00:56:30.839> want<00:56:30.960> to<00:56:31.140> run<00:56:31.319> any 00:56:31.849 --> 00:56:31.859 align:start position:0% and good luck if you want to run any 00:56:31.859 --> 00:56:34.730 align:start position:0% and good luck if you want to run any that<00:56:32.520> are<00:56:32.700> not<00:56:32.880> like<00:56:33.180> gas<00:56:33.480> and<00:56:34.079> like<00:56:34.380> a<00:56:34.500> typical 00:56:34.730 --> 00:56:34.740 align:start position:0% that are not like gas and like a typical 00:56:34.740 --> 00:56:37.130 align:start position:0% that are not like gas and like a typical condition<00:56:35.160> of<00:56:35.520> prisoners<00:56:36.059> right<00:56:36.780> like<00:56:36.960> the 00:56:37.130 --> 00:56:37.140 align:start position:0% condition of prisoners right like the 00:56:37.140 --> 00:56:38.990 align:start position:0% condition of prisoners right like the recommendation<00:56:37.559> for<00:56:37.859> anything<00:56:38.280> that's<00:56:38.819> not 00:56:38.990 --> 00:56:39.000 align:start position:0% recommendation for anything that's not 00:56:39.000 --> 00:56:42.170 align:start position:0% recommendation for anything that's not like<00:56:39.180> the<00:56:39.420> main<00:56:39.599> ones<00:56:39.900> are<00:56:40.140> existent<00:56:40.740> so 00:56:42.170 --> 00:56:42.180 align:start position:0% like the main ones are existent so 00:56:42.180 --> 00:56:45.290 align:start position:0% like the main ones are existent so um<00:56:42.300> first<00:56:43.079> question<00:56:43.319> is<00:56:43.680> there<00:56:44.339> a<00:56:44.700> source<00:56:45.240> of 00:56:45.290 --> 00:56:45.300 align:start position:0% um first question is there a source of 00:56:45.300 --> 00:56:47.089 align:start position:0% um first question is there a source of Truth<00:56:45.599> in<00:56:45.900> documentation<00:56:46.440> which<00:56:46.800> I<00:56:46.980> can 00:56:47.089 --> 00:56:47.099 align:start position:0% Truth in documentation which I can 00:56:47.099 --> 00:56:49.609 align:start position:0% Truth in documentation which I can follow<00:56:47.280> like<00:56:47.700> uh<00:56:48.240> to<00:56:48.660> set<00:56:48.839> up<00:56:49.020> my<00:56:49.200> own<00:56:49.319> Hardware 00:56:49.609 --> 00:56:49.619 align:start position:0% follow like uh to set up my own Hardware 00:56:49.619 --> 00:56:51.950 align:start position:0% follow like uh to set up my own Hardware we<00:56:50.040> do<00:56:50.160> Bluetooth<00:56:50.400> server<00:56:50.880> and<00:56:51.540> like<00:56:51.720> go 00:56:51.950 --> 00:56:51.960 align:start position:0% we do Bluetooth server and like go 00:56:51.960 --> 00:56:53.990 align:start position:0% we do Bluetooth server and like go through<00:56:52.079> it<00:56:52.260> I<00:56:52.619> mean<00:56:52.740> I'm<00:56:52.920> no<00:56:53.160> not<00:56:53.400> no<00:56:53.819> machine 00:56:53.990 --> 00:56:54.000 align:start position:0% through it I mean I'm no not no machine 00:56:54.000 --> 00:56:58.390 align:start position:0% through it I mean I'm no not no machine or<00:56:54.480> anything<00:56:54.660> but<00:56:55.140> like<00:56:55.619> I<00:56:55.859> can<00:56:55.980> yeah 00:56:58.390 --> 00:56:58.400 align:start position:0% or anything but like I can yeah 00:56:58.400 --> 00:57:01.910 align:start position:0% or anything but like I can yeah is<00:56:59.400> uh<00:57:00.119> it<00:57:00.420> is<00:57:00.599> the<00:57:00.839> best<00:57:01.020> place<00:57:01.319> to<00:57:01.559> uh 00:57:01.910 --> 00:57:01.920 align:start position:0% is uh it is the best place to uh 00:57:01.920 --> 00:57:03.950 align:start position:0% is uh it is the best place to uh official<00:57:02.280> ethereum<00:57:02.880> documentation<00:57:03.480> from<00:57:03.839> the 00:57:03.950 --> 00:57:03.960 align:start position:0% official ethereum documentation from the 00:57:03.960 --> 00:57:06.230 align:start position:0% official ethereum documentation from the ethereum<00:57:04.440> foundation<00:57:04.859> is<00:57:05.460> the<00:57:05.760> probably<00:57:06.000> the 00:57:06.230 --> 00:57:06.240 align:start position:0% ethereum foundation is the probably the 00:57:06.240 --> 00:57:08.630 align:start position:0% ethereum foundation is the probably the best<00:57:06.420> uh<00:57:07.319> but<00:57:07.559> also<00:57:07.859> it<00:57:07.980> also<00:57:08.220> depends<00:57:08.460> on<00:57:08.520> the 00:57:08.630 --> 00:57:08.640 align:start position:0% best uh but also it also depends on the 00:57:08.640 --> 00:57:10.010 align:start position:0% best uh but also it also depends on the client<00:57:08.819> that<00:57:09.059> you're<00:57:09.180> using<00:57:09.480> so<00:57:09.720> different 00:57:10.010 --> 00:57:10.020 align:start position:0% client that you're using so different 00:57:10.020 --> 00:57:11.390 align:start position:0% client that you're using so different clients<00:57:10.500> do<00:57:10.680> have<00:57:10.920> different<00:57:11.160> Hardware 00:57:11.390 --> 00:57:11.400 align:start position:0% clients do have different Hardware 00:57:11.400 --> 00:57:13.309 align:start position:0% clients do have different Hardware requirements<00:57:12.059> from<00:57:12.300> my<00:57:12.540> understanding<00:57:13.020> each 00:57:13.309 --> 00:57:13.319 align:start position:0% requirements from my understanding each 00:57:13.319 --> 00:57:15.370 align:start position:0% requirements from my understanding each client<00:57:13.680> uh<00:57:14.280> in<00:57:14.579> their<00:57:14.700> documentations 00:57:15.370 --> 00:57:15.380 align:start position:0% client uh in their documentations 00:57:15.380 --> 00:57:17.150 align:start position:0% client uh in their documentations specifically<00:57:16.380> State<00:57:16.619> what<00:57:16.800> their<00:57:16.980> Hardware 00:57:17.150 --> 00:57:17.160 align:start position:0% specifically State what their Hardware 00:57:17.160 --> 00:57:19.790 align:start position:0% specifically State what their Hardware requirements<00:57:17.819> are<00:57:17.940> so<00:57:18.780> I<00:57:19.319> would<00:57:19.440> actually 00:57:19.790 --> 00:57:19.800 align:start position:0% requirements are so I would actually 00:57:19.800 --> 00:57:22.010 align:start position:0% requirements are so I would actually look<00:57:20.099> at<00:57:20.220> the<00:57:20.460> documentation<00:57:21.000> for<00:57:21.480> the<00:57:21.660> client 00:57:22.010 --> 00:57:22.020 align:start position:0% look at the documentation for the client 00:57:22.020 --> 00:57:24.170 align:start position:0% look at the documentation for the client and<00:57:22.559> see<00:57:22.740> what<00:57:22.920> the<00:57:23.099> requirements<00:57:23.579> are<00:57:23.760> for 00:57:24.170 --> 00:57:24.180 align:start position:0% and see what the requirements are for 00:57:24.180 --> 00:57:27.410 align:start position:0% and see what the requirements are for that<00:57:24.420> uh<00:57:25.140> for<00:57:25.319> that<00:57:25.619> now<00:57:25.740> the<00:57:26.520> one<00:57:27.180> thing<00:57:27.240> you 00:57:27.410 --> 00:57:27.420 align:start position:0% that uh for that now the one thing you 00:57:27.420 --> 00:57:29.210 align:start position:0% that uh for that now the one thing you do<00:57:27.540> need<00:57:27.660> to<00:57:27.720> be<00:57:27.780> aware<00:57:27.960> of<00:57:28.079> is<00:57:28.440> Maggie 00:57:29.210 --> 00:57:29.220 align:start position:0% do need to be aware of is Maggie 00:57:29.220 --> 00:57:31.790 align:start position:0% do need to be aware of is Maggie mentioned<00:57:29.700> you<00:57:30.180> have<00:57:30.300> to<00:57:30.480> run<00:57:30.660> a<00:57:31.200> execution 00:57:31.790 --> 00:57:31.800 align:start position:0% mentioned you have to run a execution 00:57:31.800 --> 00:57:34.490 align:start position:0% mentioned you have to run a execution client<00:57:32.520> you<00:57:32.760> have<00:57:32.940> to<00:57:33.059> run<00:57:33.300> a<00:57:33.720> beacon<00:57:34.140> client 00:57:34.490 --> 00:57:34.500 align:start position:0% client you have to run a beacon client 00:57:34.500 --> 00:57:37.730 align:start position:0% client you have to run a beacon client uh<00:57:35.359> and<00:57:36.359> you<00:57:36.540> have<00:57:36.660> to<00:57:36.780> run<00:57:36.900> a<00:57:37.020> validator<00:57:37.500> which 00:57:37.730 --> 00:57:37.740 align:start position:0% uh and you have to run a validator which 00:57:37.740 --> 00:57:40.430 align:start position:0% uh and you have to run a validator which is<00:57:37.859> really<00:57:38.040> just<00:57:38.400> a<00:57:38.880> consensus<00:57:39.420> client<00:57:39.720> that's 00:57:40.430 --> 00:57:40.440 align:start position:0% is really just a consensus client that's 00:57:40.440 --> 00:57:42.829 align:start position:0% is really just a consensus client that's only<00:57:40.740> job<00:57:41.040> is<00:57:41.339> to<00:57:41.460> be<00:57:41.579> a<00:57:41.700> validator<00:57:42.059> so<00:57:42.359> you 00:57:42.829 --> 00:57:42.839 align:start position:0% only job is to be a validator so you 00:57:42.839 --> 00:57:46.250 align:start position:0% only job is to be a validator so you have<00:57:42.960> to<00:57:43.079> run<00:57:43.260> three<00:57:43.559> different<00:57:43.800> clients<00:57:44.339> uh 00:57:46.250 --> 00:57:46.260 align:start position:0% have to run three different clients uh 00:57:46.260 --> 00:57:49.490 align:start position:0% have to run three different clients uh so<00:57:46.559> even<00:57:47.460> though<00:57:47.760> maybe<00:57:48.300> the 00:57:49.490 --> 00:57:49.500 align:start position:0% so even though maybe the 00:57:49.500 --> 00:57:52.309 align:start position:0% so even though maybe the um<00:57:49.559> the<00:57:50.460> the<00:57:50.460> one<00:57:51.240> client<00:57:51.599> has<00:57:52.140> certain 00:57:52.309 --> 00:57:52.319 align:start position:0% um the the one client has certain 00:57:52.319 --> 00:57:54.109 align:start position:0% um the the one client has certain Hardware<00:57:52.559> requirements<00:57:53.280> you<00:57:53.579> have<00:57:53.760> to<00:57:53.880> also 00:57:54.109 --> 00:57:54.119 align:start position:0% Hardware requirements you have to also 00:57:54.119 --> 00:57:55.309 align:start position:0% Hardware requirements you have to also look<00:57:54.180> at<00:57:54.300> what<00:57:54.480> other<00:57:54.660> clients<00:57:55.020> are<00:57:55.140> going<00:57:55.260> to 00:57:55.309 --> 00:57:55.319 align:start position:0% look at what other clients are going to 00:57:55.319 --> 00:57:57.650 align:start position:0% look at what other clients are going to be<00:57:55.440> using<00:57:55.740> and<00:57:56.339> then<00:57:56.460> you<00:57:56.760> have<00:57:56.880> to<00:57:57.180> you<00:57:57.599> know 00:57:57.650 --> 00:57:57.660 align:start position:0% be using and then you have to you know 00:57:57.660 --> 00:57:59.569 align:start position:0% be using and then you have to you know bring<00:57:58.319> it<00:57:58.440> all<00:57:58.619> together<00:57:58.740> so<00:57:59.040> I<00:57:59.160> would<00:57:59.280> say<00:57:59.400> go 00:57:59.569 --> 00:57:59.579 align:start position:0% bring it all together so I would say go 00:57:59.579 --> 00:58:01.790 align:start position:0% bring it all together so I would say go to<00:57:59.640> the<00:57:59.760> client's<00:58:00.180> documentation<00:58:01.079> figure<00:58:01.559> out 00:58:01.790 --> 00:58:01.800 align:start position:0% to the client's documentation figure out 00:58:01.800 --> 00:58:03.589 align:start position:0% to the client's documentation figure out which<00:58:02.040> each<00:58:02.339> one<00:58:02.460> is<00:58:02.640> after<00:58:02.940> you<00:58:03.180> decide<00:58:03.420> what 00:58:03.589 --> 00:58:03.599 align:start position:0% which each one is after you decide what 00:58:03.599 --> 00:58:05.510 align:start position:0% which each one is after you decide what you<00:58:03.660> want<00:58:03.780> your<00:58:03.960> makeup<00:58:04.260> to<00:58:04.440> be<00:58:04.559> and<00:58:05.220> you<00:58:05.400> know 00:58:05.510 --> 00:58:05.520 align:start position:0% you want your makeup to be and you know 00:58:05.520 --> 00:58:07.069 align:start position:0% you want your makeup to be and you know use<00:58:05.700> the<00:58:05.880> information<00:58:06.059> that<00:58:06.359> Maggie<00:58:06.780> gave<00:58:06.960> you 00:58:07.069 --> 00:58:07.079 align:start position:0% use the information that Maggie gave you 00:58:07.079 --> 00:58:10.790 align:start position:0% use the information that Maggie gave you in<00:58:07.440> terms<00:58:07.680> of<00:58:07.740> uh<00:58:08.460> the<00:58:08.700> usage<00:58:09.059> on<00:58:09.599> where<00:58:09.900> uh<00:58:10.500> how 00:58:10.790 --> 00:58:10.800 align:start position:0% in terms of uh the usage on where uh how 00:58:10.800 --> 00:58:12.530 align:start position:0% in terms of uh the usage on where uh how how<00:58:10.980> utilized<00:58:11.640> certain<00:58:11.760> clients<00:58:12.059> are<00:58:12.180> to<00:58:12.359> make 00:58:12.530 --> 00:58:12.540 align:start position:0% how utilized certain clients are to make 00:58:12.540 --> 00:58:16.069 align:start position:0% how utilized certain clients are to make your<00:58:12.660> decision<00:58:12.900> cool<00:58:13.380> and<00:58:14.040> uh<00:58:14.760> just<00:58:15.420> one<00:58:15.780> I 00:58:16.069 --> 00:58:16.079 align:start position:0% your decision cool and uh just one I 00:58:16.079 --> 00:58:17.329 align:start position:0% your decision cool and uh just one I don't<00:58:16.200> want<00:58:16.319> to<00:58:16.440> put<00:58:16.559> you<00:58:16.680> in<00:58:16.800> an<00:58:16.920> adult<00:58:17.040> spot 00:58:17.329 --> 00:58:17.339 align:start position:0% don't want to put you in an adult spot 00:58:17.339 --> 00:58:19.490 align:start position:0% don't want to put you in an adult spot right<00:58:17.640> but<00:58:18.359> um<00:58:18.480> for<00:58:19.020> the<00:58:19.260> sake<00:58:19.380> of 00:58:19.490 --> 00:58:19.500 align:start position:0% right but um for the sake of 00:58:19.500 --> 00:58:21.770 align:start position:0% right but um for the sake of decentralization<00:58:20.220> easy 00:58:21.770 --> 00:58:21.780 align:start position:0% decentralization easy 00:58:21.780 --> 00:58:24.109 align:start position:0% decentralization easy um<00:58:21.839> I'm<00:58:22.020> better<00:58:22.440> off<00:58:22.619> like<00:58:23.160> uh<00:58:23.579> going<00:58:23.819> into 00:58:24.109 --> 00:58:24.119 align:start position:0% um I'm better off like uh going into 00:58:24.119 --> 00:58:26.630 align:start position:0% um I'm better off like uh going into well<00:58:24.599> I<00:58:25.079> don't<00:58:25.140> think<00:58:25.319> I<00:58:25.559> could<00:58:25.680> go<00:58:25.859> to<00:58:26.040> Dominos 00:58:26.630 --> 00:58:26.640 align:start position:0% well I don't think I could go to Dominos 00:58:26.640 --> 00:58:28.670 align:start position:0% well I don't think I could go to Dominos because<00:58:27.240> I'm<00:58:27.480> running<00:58:27.660> my<00:58:27.900> own<00:58:28.020> Hardware<00:58:28.260> but 00:58:28.670 --> 00:58:28.680 align:start position:0% because I'm running my own Hardware but 00:58:28.680 --> 00:58:31.490 align:start position:0% because I'm running my own Hardware but like<00:58:29.040> uh<00:58:29.220> using<00:58:29.640> something<00:58:29.819> like<00:58:30.059> ethereum<00:58:30.660> or 00:58:31.490 --> 00:58:31.500 align:start position:0% like uh using something like ethereum or 00:58:31.500 --> 00:58:53.170 align:start position:0% like uh using something like ethereum or uh 00:58:53.170 --> 00:58:53.180 align:start position:0% 00:58:53.180 --> 00:58:56.030 align:start position:0% ethereum.org<00:58:54.180> they<00:58:54.359> actually<00:58:54.540> do<00:58:54.839> give<00:58:55.200> uh<00:58:55.799> in 00:58:56.030 --> 00:58:56.040 align:start position:0% ethereum.org they actually do give uh in 00:58:56.040 --> 00:58:57.710 align:start position:0% ethereum.org they actually do give uh in talking<00:58:56.460> about<00:58:56.700> these<00:58:57.059> different<00:58:57.240> options 00:58:57.710 --> 00:58:57.720 align:start position:0% talking about these different options 00:58:57.720 --> 00:59:00.829 align:start position:0% talking about these different options they<00:58:58.380> do<00:58:58.619> list<00:58:59.040> out<00:58:59.339> uh<00:59:00.119> different<00:59:00.359> features 00:59:00.829 --> 00:59:00.839 align:start position:0% they do list out uh different features 00:59:00.839 --> 00:59:02.390 align:start position:0% they do list out uh different features or<00:59:01.020> different<00:59:01.260> elements<00:59:01.559> to<00:59:01.740> them<00:59:01.980> where<00:59:02.160> like 00:59:02.390 --> 00:59:02.400 align:start position:0% or different elements to them where like 00:59:02.400 --> 00:59:03.890 align:start position:0% or different elements to them where like some<00:59:02.640> of<00:59:02.700> them<00:59:02.819> have<00:59:02.940> been<00:59:03.119> audited<00:59:03.480> right 00:59:03.890 --> 00:59:03.900 align:start position:0% some of them have been audited right 00:59:03.900 --> 00:59:06.289 align:start position:0% some of them have been audited right some<00:59:04.319> haven't<00:59:04.559> right<00:59:05.099> so<00:59:05.460> you<00:59:05.940> could<00:59:06.059> actually 00:59:06.289 --> 00:59:06.299 align:start position:0% some haven't right so you could actually 00:59:06.299 --> 00:59:09.049 align:start position:0% some haven't right so you could actually potentially<00:59:07.079> use<00:59:07.319> that<00:59:07.500> as<00:59:07.680> a<00:59:07.799> way<00:59:07.980> to<00:59:08.160> gauge 00:59:09.049 --> 00:59:09.059 align:start position:0% potentially use that as a way to gauge 00:59:09.059 --> 00:59:10.190 align:start position:0% potentially use that as a way to gauge but 00:59:10.190 --> 00:59:10.200 align:start position:0% but 00:59:10.200 --> 00:59:11.809 align:start position:0% but um<00:59:10.319> you<00:59:10.740> know<00:59:10.799> most<00:59:11.099> of<00:59:11.220> the<00:59:11.339> time<00:59:11.460> with 00:59:11.809 --> 00:59:11.819 align:start position:0% um you know most of the time with 00:59:11.819 --> 00:59:13.970 align:start position:0% um you know most of the time with something<00:59:12.359> like<00:59:12.660> uh 00:59:13.970 --> 00:59:13.980 align:start position:0% something like uh 00:59:13.980 --> 00:59:18.589 align:start position:0% something like uh yeah<00:59:14.900> you<00:59:15.900> know<00:59:15.960> with<00:59:16.380> stuff<00:59:16.799> like<00:59:17.099> uh<00:59:17.599> both 00:59:18.589 --> 00:59:18.599 align:start position:0% yeah you know with stuff like uh both 00:59:18.599 --> 00:59:22.370 align:start position:0% yeah you know with stuff like uh both that<00:59:18.839> node<00:59:19.140> and<00:59:19.680> uh<00:59:19.980> cerium<00:59:20.460> you<00:59:21.119> know<00:59:21.180> their 00:59:22.370 --> 00:59:22.380 align:start position:0% that node and uh cerium you know their 00:59:22.380 --> 00:59:24.049 align:start position:0% that node and uh cerium you know their your<00:59:22.920> those<00:59:23.339> aren't<00:59:23.520> things<00:59:23.819> that<00:59:24.000> are 00:59:24.049 --> 00:59:24.059 align:start position:0% your those aren't things that are 00:59:24.059 --> 00:59:25.789 align:start position:0% your those aren't things that are exposed<00:59:24.540> to<00:59:24.599> the<00:59:24.720> public<00:59:24.900> right<00:59:25.380> so<00:59:25.559> the 00:59:25.789 --> 00:59:25.799 align:start position:0% exposed to the public right so the 00:59:25.799 --> 00:59:28.549 align:start position:0% exposed to the public right so the application<00:59:26.280> is<00:59:26.460> just<00:59:26.760> sitting<00:59:27.119> on<00:59:27.960> your 00:59:28.549 --> 00:59:28.559 align:start position:0% application is just sitting on your 00:59:28.559 --> 00:59:31.010 align:start position:0% application is just sitting on your computer<00:59:29.059> so<00:59:30.059> if<00:59:30.240> your<00:59:30.359> computer<00:59:30.540> would<00:59:30.839> be 00:59:31.010 --> 00:59:31.020 align:start position:0% computer so if your computer would be 00:59:31.020 --> 00:59:37.309 align:start position:0% computer so if your computer would be hacked<00:59:31.380> this<00:59:31.740> is<00:59:31.859> how<00:59:32.040> serious<00:59:32.460> so 00:59:37.309 --> 00:59:37.319 align:start position:0% 00:59:37.319 --> 00:59:38.870 align:start position:0% there's<00:59:37.859> going<00:59:38.040> to<00:59:38.040> be<00:59:38.160> risk<00:59:38.460> no<00:59:38.579> matter<00:59:38.700> what 00:59:38.870 --> 00:59:38.880 align:start position:0% there's going to be risk no matter what 00:59:38.880 --> 00:59:41.809 align:start position:0% there's going to be risk no matter what options<00:59:39.540> you<00:59:40.020> use<00:59:40.260> but<00:59:40.859> uh<00:59:41.040> yeah<00:59:41.280> there<00:59:41.640> is 00:59:41.809 --> 00:59:41.819 align:start position:0% options you use but uh yeah there is 00:59:41.819 --> 00:59:43.609 align:start position:0% options you use but uh yeah there is some<00:59:42.180> information<00:59:42.540> on<00:59:42.900> the<00:59:43.020> ethereum<00:59:43.440> network 00:59:43.609 --> 00:59:43.619 align:start position:0% some information on the ethereum network 00:59:43.619 --> 00:59:46.030 align:start position:0% some information on the ethereum network uh 00:59:46.030 --> 00:59:46.040 align:start position:0% uh 00:59:46.040 --> 00:59:49.190 align:start position:0% uh thank<00:59:47.040> you<00:59:47.160> so<00:59:47.280> much 00:59:49.190 --> 00:59:49.200 align:start position:0% thank you so much 00:59:49.200 --> 00:59:51.049 align:start position:0% thank you so much um<00:59:49.319> thank<00:59:49.740> you<00:59:49.799> everyone<00:59:50.040> for<00:59:50.460> being<00:59:50.640> here<00:59:50.819> so 00:59:51.049 --> 00:59:51.059 align:start position:0% um thank you everyone for being here so 00:59:51.059 --> 00:59:52.670 align:start position:0% um thank you everyone for being here so early<00:59:51.240> in<00:59:51.420> the<00:59:51.480> morning<00:59:51.599> as<00:59:51.960> I<00:59:52.140> mentioned<00:59:52.440> on 00:59:52.670 --> 00:59:52.680 align:start position:0% early in the morning as I mentioned on 00:59:52.680 --> 00:59:55.370 align:start position:0% early in the morning as I mentioned on lastded.com<00:59:53.460> you<00:59:54.180> can<00:59:54.299> follow<00:59:54.540> us<00:59:54.720> to<00:59:54.960> stay<00:59:55.140> up 00:59:55.370 --> 00:59:55.380 align:start position:0% lastded.com you can follow us to stay up 00:59:55.380 --> 00:59:56.690 align:start position:0% lastded.com you can follow us to stay up to<00:59:55.500> date<00:59:55.619> on<00:59:55.799> what's<00:59:55.980> going<00:59:56.160> on<00:59:56.280> with<00:59:56.520> no 00:59:56.690 --> 00:59:56.700 align:start position:0% to date on what's going on with no 00:59:56.700 --> 00:59:58.970 align:start position:0% to date on what's going on with no launcher<00:59:57.119> and<00:59:57.599> if<00:59:57.720> you're<00:59:57.839> a<00:59:58.020> protocol<00:59:58.319> uh 00:59:58.970 --> 00:59:58.980 align:start position:0% launcher and if you're a protocol uh 00:59:58.980 --> 01:00:01.970 align:start position:0% launcher and if you're a protocol uh looking<00:59:59.220> for<00:59:59.660> uh<01:00:00.660> no<01:00:01.020> software<01:00:01.500> or<01:00:01.799> even 01:00:01.970 --> 01:00:01.980 align:start position:0% looking for uh no software or even 01:00:01.980 --> 01:00:03.650 align:start position:0% looking for uh no software or even Hardware<01:00:02.400> infrastructure<01:00:03.180> want<01:00:03.480> to 01:00:03.650 --> 01:00:03.660 align:start position:0% Hardware infrastructure want to 01:00:03.660 --> 01:00:05.510 align:start position:0% Hardware infrastructure want to decentralize<01:00:04.319> you<01:00:04.859> should<01:00:04.980> contact<01:00:05.220> us 01:00:05.510 --> 01:00:05.520 align:start position:0% decentralize you should contact us 01:00:05.520 --> 01:00:07.430 align:start position:0% decentralize you should contact us because<01:00:05.819> that's<01:00:06.059> what<01:00:06.359> we<01:00:06.540> care<01:00:07.079> about<01:00:07.200> what 01:00:07.430 --> 01:00:07.440 align:start position:0% because that's what we care about what 01:00:07.440 --> 01:00:09.440 align:start position:0% because that's what we care about what we<01:00:07.559> like<01:00:07.680> to<01:00:07.859> do<01:00:07.980> so<01:00:08.220> thank<01:00:08.460> you<01:00:08.520> so<01:00:08.700> much 01:00:09.440 --> 01:00:09.450 align:start position:0% we like to do so thank you so much 01:00:09.450 --> 01:00:13.510 align:start position:0% we like to do so thank you so much [Applause]