WEBVTT Kind: captions Language: en 00:00:00.570 --> 00:00:19.230 align:start position:0% [Music] 00:00:19.230 --> 00:00:19.240 align:start position:0% 00:00:19.240 --> 00:00:21.550 align:start position:0% good<00:00:19.400> morning<00:00:19.880> everybody<00:00:20.880> um<00:00:21.039> I'm<00:00:21.199> Stefan 00:00:21.550 --> 00:00:21.560 align:start position:0% good morning everybody um I'm Stefan 00:00:21.560 --> 00:00:24.830 align:start position:0% good morning everybody um I'm Stefan kobut<00:00:22.160> I'm<00:00:22.359> the<00:00:22.800> founder<00:00:23.800> um<00:00:24.080> of<00:00:24.240> sterium<00:00:24.680> and 00:00:24.830 --> 00:00:24.840 align:start position:0% kobut I'm the founder um of sterium and 00:00:24.840 --> 00:00:27.710 align:start position:0% kobut I'm the founder um of sterium and Ro<00:00:25.400> logic<00:00:26.400> and<00:00:26.760> we<00:00:26.880> will<00:00:27.039> do<00:00:27.160> a<00:00:27.240> workshop 00:00:27.710 --> 00:00:27.720 align:start position:0% Ro logic and we will do a workshop 00:00:27.720 --> 00:00:29.990 align:start position:0% Ro logic and we will do a workshop together<00:00:28.039> to<00:00:28.240> set<00:00:28.439> up<00:00:28.560> an<00:00:28.720> etherium<00:00:29.160> node<00:00:29.800> with 00:00:29.990 --> 00:00:30.000 align:start position:0% together to set up an etherium node with 00:00:30.000 --> 00:00:32.430 align:start position:0% together to set up an etherium node with with<00:00:30.160> different<00:00:30.439> kinds<00:00:30.679> of 00:00:32.430 --> 00:00:32.440 align:start position:0% with different kinds of 00:00:32.440 --> 00:00:35.709 align:start position:0% with different kinds of services<00:00:33.440> um<00:00:34.399> first<00:00:34.600> of<00:00:34.760> all<00:00:35.120> some<00:00:35.399> facts 00:00:35.709 --> 00:00:35.719 align:start position:0% services um first of all some facts 00:00:35.719 --> 00:00:38.750 align:start position:0% services um first of all some facts about<00:00:36.520> about<00:00:36.920> us<00:00:37.559> uh<00:00:37.680> R<00:00:37.960> logic<00:00:38.239> was<00:00:38.360> found<00:00:38.600> in 00:00:38.750 --> 00:00:38.760 align:start position:0% about about us uh R logic was found in 00:00:38.760 --> 00:00:41.190 align:start position:0% about about us uh R logic was found in 2012<00:00:39.440> not<00:00:39.640> actually<00:00:39.920> it's<00:00:40.000> a<00:00:40.680> blockchain 00:00:41.190 --> 00:00:41.200 align:start position:0% 2012 not actually it's a blockchain 00:00:41.200 --> 00:00:43.310 align:start position:0% 2012 not actually it's a blockchain company<00:00:41.600> but<00:00:41.760> an<00:00:42.039> IT<00:00:42.360> infrastructure<00:00:42.960> company 00:00:43.310 --> 00:00:43.320 align:start position:0% company but an IT infrastructure company 00:00:43.320 --> 00:00:47.790 align:start position:0% company but an IT infrastructure company devops<00:00:44.039> company<00:00:45.120> um<00:00:46.120> we<00:00:46.680> develop<00:00:47.280> sterium 00:00:47.790 --> 00:00:47.800 align:start position:0% devops company um we develop sterium 00:00:47.800 --> 00:00:48.830 align:start position:0% devops company um we develop sterium since 00:00:48.830 --> 00:00:48.840 align:start position:0% since 00:00:48.840 --> 00:00:53.189 align:start position:0% since 2020<00:00:49.840> um<00:00:50.120> so<00:00:51.120> already<00:00:51.559> before<00:00:52.199> the<00:00:52.399> Genesis<00:00:53.000> of 00:00:53.189 --> 00:00:53.199 align:start position:0% 2020 um so already before the Genesis of 00:00:53.199 --> 00:00:56.069 align:start position:0% 2020 um so already before the Genesis of proof<00:00:53.440> of<00:00:53.600> stake<00:00:53.960> of<00:00:54.440> um<00:00:54.640> steum<00:00:55.160> happened<00:00:55.840> we 00:00:56.069 --> 00:00:56.079 align:start position:0% proof of stake of um steum happened we 00:00:56.079 --> 00:00:58.670 align:start position:0% proof of stake of um steum happened we started<00:00:56.440> with<00:00:56.600> the<00:00:57.359> development<00:00:58.359> we<00:00:58.519> are 00:00:58.670 --> 00:00:58.680 align:start position:0% started with the development we are 00:00:58.680 --> 00:01:00.590 align:start position:0% started with the development we are institutional<00:00:59.320> node<00:00:59.559> operator<00:01:00.079> so<00:01:00.239> we<00:01:00.359> use 00:01:00.590 --> 00:01:00.600 align:start position:0% institutional node operator so we use 00:01:00.600 --> 00:01:03.229 align:start position:0% institutional node operator so we use theum<00:01:01.079> also<00:01:01.320> for<00:01:01.600> our<00:01:02.199> um<00:01:02.359> own 00:01:03.229 --> 00:01:03.239 align:start position:0% theum also for our um own 00:01:03.239 --> 00:01:06.630 align:start position:0% theum also for our um own operations<00:01:04.239> which<00:01:04.439> include<00:01:05.239> um<00:01:05.799> light<00:01:06.400> which 00:01:06.630 --> 00:01:06.640 align:start position:0% operations which include um light which 00:01:06.640 --> 00:01:09.830 align:start position:0% operations which include um light which include<00:01:07.040> the<00:01:07.479> uh<00:01:07.560> staking<00:01:08.000> efforts<00:01:08.320> in 00:01:09.830 --> 00:01:09.840 align:start position:0% include the uh staking efforts in 00:01:09.840 --> 00:01:13.429 align:start position:0% include the uh staking efforts in Lio<00:01:10.840> uh<00:01:11.000> we<00:01:11.360> already<00:01:11.960> performed<00:01:12.560> couple<00:01:12.840> of<00:01:13.280> uh 00:01:13.429 --> 00:01:13.439 align:start position:0% Lio uh we already performed couple of uh 00:01:13.439 --> 00:01:16.590 align:start position:0% Lio uh we already performed couple of uh security<00:01:13.840> audits<00:01:14.280> for<00:01:14.600> stum<00:01:15.600> to<00:01:15.799> Ure<00:01:16.400> that 00:01:16.590 --> 00:01:16.600 align:start position:0% security audits for stum to Ure that 00:01:16.600 --> 00:01:18.870 align:start position:0% security audits for stum to Ure that everything<00:01:16.920> is<00:01:17.040> running<00:01:17.560> fine<00:01:17.799> and<00:01:18.000> we<00:01:18.119> don't 00:01:18.870 --> 00:01:18.880 align:start position:0% everything is running fine and we don't 00:01:18.880 --> 00:01:22.670 align:start position:0% everything is running fine and we don't oversee<00:01:19.880> um<00:01:20.240> some<00:01:20.720> Overlook<00:01:21.320> some<00:01:21.799> major<00:01:22.520> uh 00:01:22.670 --> 00:01:22.680 align:start position:0% oversee um some Overlook some major uh 00:01:22.680 --> 00:01:24.190 align:start position:0% oversee um some Overlook some major uh security 00:01:24.190 --> 00:01:24.200 align:start position:0% security 00:01:24.200 --> 00:01:26.630 align:start position:0% security vulnerabilities<00:01:25.200> we<00:01:25.400> also<00:01:25.600> won<00:01:26.240> um<00:01:26.360> some 00:01:26.630 --> 00:01:26.640 align:start position:0% vulnerabilities we also won um some 00:01:26.640 --> 00:01:29.069 align:start position:0% vulnerabilities we also won um some awards<00:01:27.320> I<00:01:27.479> guess<00:01:27.720> the<00:01:27.880> most<00:01:28.240> recognizing<00:01:28.920> at 00:01:29.069 --> 00:01:29.079 align:start position:0% awards I guess the most recognizing at 00:01:29.079 --> 00:01:30.310 align:start position:0% awards I guess the most recognizing at least<00:01:29.240> in<00:01:29.360> austri<00:01:29.720> is<00:01:29.799> the<00:01:29.960> Austrian 00:01:30.310 --> 00:01:30.320 align:start position:0% least in austri is the Austrian 00:01:30.320 --> 00:01:31.990 align:start position:0% least in austri is the Austrian blockchain<00:01:30.680> award 00:01:31.990 --> 00:01:32.000 align:start position:0% blockchain award 00:01:32.000 --> 00:01:35.030 align:start position:0% blockchain award 2021<00:01:33.000> and<00:01:33.799> um<00:01:34.079> this<00:01:34.200> year<00:01:34.439> we<00:01:34.560> founded<00:01:34.920> a 00:01:35.030 --> 00:01:35.040 align:start position:0% 2021 and um this year we founded a 00:01:35.040 --> 00:01:37.670 align:start position:0% 2021 and um this year we founded a separate<00:01:35.439> company<00:01:36.000> for<00:01:36.320> this<00:01:36.479> great 00:01:37.670 --> 00:01:37.680 align:start position:0% separate company for this great 00:01:37.680 --> 00:01:42.190 align:start position:0% separate company for this great product<00:01:38.759> um<00:01:39.840> and<00:01:40.840> also<00:01:41.200> this<00:01:41.360> year<00:01:41.759> we 00:01:42.190 --> 00:01:42.200 align:start position:0% product um and also this year we 00:01:42.200 --> 00:01:45.469 align:start position:0% product um and also this year we launched<00:01:42.720> a<00:01:42.880> steum<00:01:43.360> plus<00:01:44.119> which<00:01:44.320> is<00:01:45.280> an 00:01:45.469 --> 00:01:45.479 align:start position:0% launched a steum plus which is an 00:01:45.479 --> 00:01:47.830 align:start position:0% launched a steum plus which is an addition<00:01:45.880> to<00:01:46.040> sterium<00:01:46.640> a<00:01:46.799> hosting<00:01:47.240> service 00:01:47.830 --> 00:01:47.840 align:start position:0% addition to sterium a hosting service 00:01:47.840 --> 00:01:49.190 align:start position:0% addition to sterium a hosting service that<00:01:47.960> you<00:01:48.040> don't<00:01:48.200> need<00:01:48.360> to<00:01:48.520> care<00:01:48.799> anymore 00:01:49.190 --> 00:01:49.200 align:start position:0% that you don't need to care anymore 00:01:49.200 --> 00:01:51.830 align:start position:0% that you don't need to care anymore about<00:01:49.520> where<00:01:49.719> you<00:01:50.479> uh<00:01:50.640> get<00:01:50.840> your<00:01:51.000> own<00:01:51.640> um 00:01:51.830 --> 00:01:51.840 align:start position:0% about where you uh get your own um 00:01:51.840 --> 00:01:54.030 align:start position:0% about where you uh get your own um machine<00:01:52.159> for 00:01:54.030 --> 00:01:54.040 align:start position:0% machine for 00:01:54.040 --> 00:01:56.630 align:start position:0% machine for sterium<00:01:55.040> so<00:01:55.200> some<00:01:55.399> use<00:01:55.719> cases<00:01:55.960> for<00:01:56.119> steum 00:01:56.630 --> 00:01:56.640 align:start position:0% sterium so some use cases for steum 00:01:56.640 --> 00:01:58.670 align:start position:0% sterium so some use cases for steum itself<00:01:57.119> steum<00:01:57.560> is<00:01:57.680> open<00:01:57.960> source<00:01:58.320> everybody 00:01:58.670 --> 00:01:58.680 align:start position:0% itself steum is open source everybody 00:01:58.680 --> 00:02:01.190 align:start position:0% itself steum is open source everybody can<00:01:58.840> look<00:01:59.000> at<00:01:59.119> the<00:01:59.240> source<00:01:59.520> of<00:01:59.640> course 00:02:01.190 --> 00:02:01.200 align:start position:0% can look at the source of course 00:02:01.200 --> 00:02:03.789 align:start position:0% can look at the source of course and<00:02:01.799> everybody<00:02:02.479> can<00:02:02.640> use<00:02:02.799> it<00:02:03.000> in<00:02:03.240> whatever<00:02:03.600> way 00:02:03.789 --> 00:02:03.799 align:start position:0% and everybody can use it in whatever way 00:02:03.799 --> 00:02:05.910 align:start position:0% and everybody can use it in whatever way they<00:02:03.960> want<00:02:04.119> to<00:02:04.360> it's<00:02:04.560> MIT<00:02:05.000> licensed<00:02:05.520> it<00:02:05.680> means 00:02:05.910 --> 00:02:05.920 align:start position:0% they want to it's MIT licensed it means 00:02:05.920 --> 00:02:08.510 align:start position:0% they want to it's MIT licensed it means you<00:02:06.039> can<00:02:06.200> also<00:02:06.399> Fork<00:02:06.759> it<00:02:07.280> Rebrand<00:02:07.960> it<00:02:08.239> whatever 00:02:08.510 --> 00:02:08.520 align:start position:0% you can also Fork it Rebrand it whatever 00:02:08.520 --> 00:02:10.749 align:start position:0% you can also Fork it Rebrand it whatever you<00:02:08.720> like<00:02:08.920> to<00:02:09.080> do<00:02:09.399> with<00:02:09.679> with<00:02:09.800> the<00:02:09.959> source<00:02:10.319> code 00:02:10.749 --> 00:02:10.759 align:start position:0% you like to do with with the source code 00:02:10.759 --> 00:02:14.270 align:start position:0% you like to do with with the source code it's<00:02:10.959> up<00:02:11.120> to<00:02:11.680> you<00:02:12.680> um<00:02:13.239> some<00:02:13.440> use<00:02:13.800> cases<00:02:14.160> of 00:02:14.270 --> 00:02:14.280 align:start position:0% it's up to you um some use cases of 00:02:14.280 --> 00:02:17.270 align:start position:0% it's up to you um some use cases of course<00:02:14.480> are<00:02:14.720> staking<00:02:15.360> we<00:02:15.879> as<00:02:16.080> mentioned<00:02:17.000> um 00:02:17.270 --> 00:02:17.280 align:start position:0% course are staking we as mentioned um 00:02:17.280 --> 00:02:20.550 align:start position:0% course are staking we as mentioned um use<00:02:17.560> it<00:02:18.560> uh<00:02:18.680> for<00:02:18.879> ourselves<00:02:19.879> for<00:02:20.080> our<00:02:20.280> own 00:02:20.550 --> 00:02:20.560 align:start position:0% use it uh for ourselves for our own 00:02:20.560 --> 00:02:24.309 align:start position:0% use it uh for ourselves for our own operations<00:02:21.239> with<00:02:21.440> Lio<00:02:22.360> and<00:02:22.560> other<00:02:23.319> protocols 00:02:24.309 --> 00:02:24.319 align:start position:0% operations with Lio and other protocols 00:02:24.319 --> 00:02:27.430 align:start position:0% operations with Lio and other protocols there<00:02:24.480> are<00:02:24.920> also<00:02:25.519> protocol<00:02:25.959> node 00:02:27.430 --> 00:02:27.440 align:start position:0% there are also protocol node 00:02:27.440 --> 00:02:30.430 align:start position:0% there are also protocol node operations<00:02:28.440> uh<00:02:28.680> for<00:02:28.920> Obel<00:02:29.239> and<00:02:29.440> SSV<00:02:30.080> so<00:02:30.239> it's 00:02:30.430 --> 00:02:30.440 align:start position:0% operations uh for Obel and SSV so it's 00:02:30.440 --> 00:02:34.030 align:start position:0% operations uh for Obel and SSV so it's very<00:02:30.680> easy<00:02:31.160> with<00:02:31.360> stereum<00:02:31.879> to<00:02:32.040> set<00:02:32.280> up<00:02:33.160> a<00:02:33.319> Lio 00:02:34.030 --> 00:02:34.040 align:start position:0% very easy with stereum to set up a Lio 00:02:34.040 --> 00:02:40.270 align:start position:0% very easy with stereum to set up a Lio CSM<00:02:35.040> um<00:02:35.440> operator<00:02:36.239> as<00:02:36.400> well<00:02:36.800> as<00:02:37.040> obal<00:02:37.400> or<00:02:37.640> SSV 00:02:40.270 --> 00:02:40.280 align:start position:0% CSM um operator as well as obal or SSV 00:02:40.280 --> 00:02:44.190 align:start position:0% CSM um operator as well as obal or SSV operators<00:02:41.280> then<00:02:42.200> it's<00:02:42.599> also<00:02:43.599> possible<00:02:44.080> that 00:02:44.190 --> 00:02:44.200 align:start position:0% operators then it's also possible that 00:02:44.200 --> 00:02:46.750 align:start position:0% operators then it's also possible that you<00:02:44.360> run<00:02:44.640> your<00:02:44.800> own<00:02:45.120> clusters<00:02:45.720> with<00:02:46.080> opal<00:02:46.440> and 00:02:46.750 --> 00:02:46.760 align:start position:0% you run your own clusters with opal and 00:02:46.760 --> 00:02:49.430 align:start position:0% you run your own clusters with opal and SSV<00:02:47.760> in<00:02:47.920> case<00:02:48.080> you<00:02:48.200> don't<00:02:48.400> know<00:02:48.560> Obel<00:02:48.879> and<00:02:49.040> SSV 00:02:49.430 --> 00:02:49.440 align:start position:0% SSV in case you don't know Obel and SSV 00:02:49.440 --> 00:02:52.190 align:start position:0% SSV in case you don't know Obel and SSV are<00:02:49.680> dvts<00:02:50.360> distributed<00:02:50.959> validator 00:02:52.190 --> 00:02:52.200 align:start position:0% are dvts distributed validator 00:02:52.200 --> 00:02:55.509 align:start position:0% are dvts distributed validator technologies<00:02:53.200> that<00:02:53.400> help<00:02:53.640> you<00:02:54.239> spread<00:02:54.800> one 00:02:55.509 --> 00:02:55.519 align:start position:0% technologies that help you spread one 00:02:55.519 --> 00:02:58.670 align:start position:0% technologies that help you spread one key<00:02:55.840> one<00:02:56.040> validator<00:02:56.640> key<00:02:57.400> over<00:02:58.040> multiple 00:02:58.670 --> 00:02:58.680 align:start position:0% key one validator key over multiple 00:02:58.680 --> 00:03:02.430 align:start position:0% key one validator key over multiple service<00:02:59.680> um<00:02:59.879> um<00:03:00.159> to<00:03:00.560> ensure<00:03:01.159> more<00:03:01.440> reliability 00:03:02.430 --> 00:03:02.440 align:start position:0% service um um to ensure more reliability 00:03:02.440 --> 00:03:06.350 align:start position:0% service um um to ensure more reliability more<00:03:02.760> resilience<00:03:03.400> to<00:03:03.760> technical<00:03:04.360> issues<00:03:05.360> or 00:03:06.350 --> 00:03:06.360 align:start position:0% more resilience to technical issues or 00:03:06.360 --> 00:03:09.110 align:start position:0% more resilience to technical issues or other<00:03:06.799> issues<00:03:07.159> that<00:03:07.319> you<00:03:07.440> might<00:03:08.000> face<00:03:09.000> of 00:03:09.110 --> 00:03:09.120 align:start position:0% other issues that you might face of 00:03:09.120 --> 00:03:11.350 align:start position:0% other issues that you might face of course<00:03:09.319> you<00:03:09.440> can<00:03:09.640> also<00:03:09.840> use<00:03:10.120> theum<00:03:10.920> um<00:03:11.120> as<00:03:11.200> an 00:03:11.350 --> 00:03:11.360 align:start position:0% course you can also use theum um as an 00:03:11.360 --> 00:03:12.789 align:start position:0% course you can also use theum um as an RPC 00:03:12.789 --> 00:03:12.799 align:start position:0% RPC 00:03:12.799 --> 00:03:16.550 align:start position:0% RPC node<00:03:13.799> um<00:03:14.560> maybe<00:03:14.879> some<00:03:15.040> of<00:03:15.159> you<00:03:15.400> guys<00:03:15.720> already 00:03:16.550 --> 00:03:16.560 align:start position:0% node um maybe some of you guys already 00:03:16.560 --> 00:03:20.309 align:start position:0% node um maybe some of you guys already um<00:03:16.720> use<00:03:17.040> infura<00:03:17.680> or<00:03:17.920> some<00:03:18.159> other<00:03:18.400> RPC<00:03:19.319> provider 00:03:20.309 --> 00:03:20.319 align:start position:0% um use infura or some other RPC provider 00:03:20.319 --> 00:03:21.869 align:start position:0% um use infura or some other RPC provider and<00:03:20.440> you<00:03:20.560> know<00:03:20.760> that<00:03:20.879> you're<00:03:21.120> limited<00:03:21.680> with 00:03:21.869 --> 00:03:21.879 align:start position:0% and you know that you're limited with 00:03:21.879 --> 00:03:23.350 align:start position:0% and you know that you're limited with them<00:03:22.200> but<00:03:22.360> with<00:03:22.519> your<00:03:22.640> own<00:03:22.840> node<00:03:23.120> you're 00:03:23.350 --> 00:03:23.360 align:start position:0% them but with your own node you're 00:03:23.360 --> 00:03:25.309 align:start position:0% them but with your own node you're basically<00:03:23.840> just<00:03:24.040> limited<00:03:24.440> by<00:03:24.560> the<00:03:24.760> hardware 00:03:25.309 --> 00:03:25.319 align:start position:0% basically just limited by the hardware 00:03:25.319 --> 00:03:29.149 align:start position:0% basically just limited by the hardware you're<00:03:26.040> um<00:03:26.920> putting<00:03:27.200> stereum<00:03:27.840> onto<00:03:28.840> we<00:03:29.000> have 00:03:29.149 --> 00:03:29.159 align:start position:0% you're um putting stereum onto we have 00:03:29.159 --> 00:03:31.509 align:start position:0% you're um putting stereum onto we have users<00:03:29.799> that<00:03:29.920> run<00:03:30.159> Arbitrage<00:03:30.640> bots<00:03:30.959> on<00:03:31.120> it<00:03:31.400> we 00:03:31.509 --> 00:03:31.519 align:start position:0% users that run Arbitrage bots on it we 00:03:31.519 --> 00:03:33.429 align:start position:0% users that run Arbitrage bots on it we have<00:03:31.680> users<00:03:32.120> that<00:03:32.560> um<00:03:32.920> connect<00:03:33.280> their 00:03:33.429 --> 00:03:33.439 align:start position:0% have users that um connect their 00:03:33.439 --> 00:03:35.869 align:start position:0% have users that um connect their metamask<00:03:34.040> on<00:03:34.200> it<00:03:34.720> um<00:03:35.000> that's<00:03:35.239> pretty<00:03:35.480> easy<00:03:35.720> and 00:03:35.869 --> 00:03:35.879 align:start position:0% metamask on it um that's pretty easy and 00:03:35.879 --> 00:03:39.630 align:start position:0% metamask on it um that's pretty easy and will<00:03:36.040> be<00:03:36.400> explained<00:03:37.400> also<00:03:38.080> later<00:03:39.080> um<00:03:39.519> of 00:03:39.630 --> 00:03:39.640 align:start position:0% will be explained also later um of 00:03:39.640 --> 00:03:41.509 align:start position:0% will be explained also later um of course<00:03:39.840> you<00:03:40.000> can<00:03:40.519> um<00:03:40.680> start<00:03:40.959> developing<00:03:41.400> your 00:03:41.509 --> 00:03:41.519 align:start position:0% course you can um start developing your 00:03:41.519 --> 00:03:44.030 align:start position:0% course you can um start developing your own<00:03:41.799> decentralized<00:03:42.599> app<00:03:43.200> with<00:03:43.400> theerum 00:03:44.030 --> 00:03:44.040 align:start position:0% own decentralized app with theerum 00:03:44.040 --> 00:03:46.630 align:start position:0% own decentralized app with theerum because<00:03:44.239> you<00:03:44.400> have<00:03:44.560> the<00:03:44.720> full<00:03:45.080> range<00:03:45.439> of<00:03:45.640> RPC 00:03:46.630 --> 00:03:46.640 align:start position:0% because you have the full range of RPC 00:03:46.640 --> 00:03:49.509 align:start position:0% because you have the full range of RPC uh<00:03:46.799> requests<00:03:47.360> that<00:03:47.480> you<00:03:47.599> can<00:03:47.920> use<00:03:48.920> as<00:03:49.080> well<00:03:49.360> of 00:03:49.509 --> 00:03:49.519 align:start position:0% uh requests that you can use as well of 00:03:49.519 --> 00:03:51.750 align:start position:0% uh requests that you can use as well of course<00:03:49.720> as 00:03:51.750 --> 00:03:51.760 align:start position:0% course as 00:03:51.760 --> 00:03:54.949 align:start position:0% course as websocket<00:03:52.760> um<00:03:52.959> and<00:03:53.159> of<00:03:53.319> course<00:03:53.879> um<00:03:54.000> steum<00:03:54.519> runs 00:03:54.949 --> 00:03:54.959 align:start position:0% websocket um and of course um steum runs 00:03:54.959 --> 00:03:56.509 align:start position:0% websocket um and of course um steum runs everything<00:03:55.319> you<00:03:55.480> want<00:03:55.640> to<00:03:56.079> you're<00:03:56.319> not 00:03:56.509 --> 00:03:56.519 align:start position:0% everything you want to you're not 00:03:56.519 --> 00:03:59.470 align:start position:0% everything you want to you're not limited<00:03:57.000> to<00:03:57.200> the<00:03:57.360> stuff<00:03:57.680> that<00:03:57.879> we<00:03:58.319> provide<00:03:58.680> you 00:03:59.470 --> 00:03:59.480 align:start position:0% limited to the stuff that we provide you 00:03:59.480 --> 00:04:02.750 align:start position:0% limited to the stuff that we provide you you<00:03:59.799> can<00:04:00.000> also<00:04:00.959> um<00:04:01.120> come<00:04:01.319> up<00:04:01.480> with<00:04:01.680> custom<00:04:02.599> uh 00:04:02.750 --> 00:04:02.760 align:start position:0% you can also um come up with custom uh 00:04:02.760 --> 00:04:04.830 align:start position:0% you can also um come up with custom uh services<00:04:03.519> that<00:04:03.799> you<00:04:04.000> integrate<00:04:04.599> pretty 00:04:04.830 --> 00:04:04.840 align:start position:0% services that you integrate pretty 00:04:04.840 --> 00:04:06.910 align:start position:0% services that you integrate pretty easily<00:04:05.560> that<00:04:05.680> will<00:04:05.840> be<00:04:06.040> also<00:04:06.439> explained<00:04:06.840> a 00:04:06.910 --> 00:04:06.920 align:start position:0% easily that will be also explained a 00:04:06.920 --> 00:04:09.710 align:start position:0% easily that will be also explained a little<00:04:07.079> bit<00:04:07.239> later 00:04:09.710 --> 00:04:09.720 align:start position:0% 00:04:09.720 --> 00:04:12.789 align:start position:0% on<00:04:10.720> as<00:04:10.840> you<00:04:10.959> may<00:04:11.120> know<00:04:11.439> ethereum<00:04:12.079> has<00:04:12.319> multiple 00:04:12.789 --> 00:04:12.799 align:start position:0% on as you may know ethereum has multiple 00:04:12.799 --> 00:04:14.589 align:start position:0% on as you may know ethereum has multiple clients<00:04:13.280> first<00:04:13.439> of<00:04:13.560> all<00:04:13.720> we<00:04:13.879> have<00:04:14.079> execution 00:04:14.589 --> 00:04:14.599 align:start position:0% clients first of all we have execution 00:04:14.599 --> 00:04:16.909 align:start position:0% clients first of all we have execution clients<00:04:15.040> and<00:04:15.439> and<00:04:15.640> consensus 00:04:16.909 --> 00:04:16.919 align:start position:0% clients and and consensus 00:04:16.919 --> 00:04:21.550 align:start position:0% clients and and consensus clients<00:04:18.000> um<00:04:19.000> both<00:04:19.320> clients<00:04:19.680> are<00:04:20.079> needed<00:04:21.079> to 00:04:21.550 --> 00:04:21.560 align:start position:0% clients um both clients are needed to 00:04:21.560 --> 00:04:23.790 align:start position:0% clients um both clients are needed to ensure<00:04:22.000> that<00:04:22.160> you<00:04:22.400> can<00:04:22.520> run<00:04:22.720> a<00:04:22.840> full<00:04:23.080> Noe<00:04:23.520> or<00:04:23.639> an 00:04:23.790 --> 00:04:23.800 align:start position:0% ensure that you can run a full Noe or an 00:04:23.800 --> 00:04:25.070 align:start position:0% ensure that you can run a full Noe or an archive 00:04:25.070 --> 00:04:25.080 align:start position:0% archive 00:04:25.080 --> 00:04:29.469 align:start position:0% archive note<00:04:26.080> we<00:04:26.639> support<00:04:27.639> um<00:04:28.160> most<00:04:28.400> of<00:04:28.600> the<00:04:29.160> most<00:04:29.320> of 00:04:29.469 --> 00:04:29.479 align:start position:0% note we support um most of the most of 00:04:29.479 --> 00:04:32.189 align:start position:0% note we support um most of the most of the<00:04:30.120> recent<00:04:30.520> clients<00:04:31.160> most<00:04:31.360> of<00:04:31.479> the<00:04:31.759> major 00:04:32.189 --> 00:04:32.199 align:start position:0% the recent clients most of the major 00:04:32.199 --> 00:04:35.830 align:start position:0% the recent clients most of the major clients<00:04:33.039> we<00:04:33.240> also<00:04:33.520> look<00:04:34.000> always<00:04:34.360> into<00:04:34.960> some<00:04:35.520> um 00:04:35.830 --> 00:04:35.840 align:start position:0% clients we also look always into some um 00:04:35.840 --> 00:04:38.110 align:start position:0% clients we also look always into some um smaller<00:04:36.320> clients<00:04:36.840> but<00:04:37.240> um<00:04:37.400> up<00:04:37.560> until<00:04:37.960> right 00:04:38.110 --> 00:04:38.120 align:start position:0% smaller clients but um up until right 00:04:38.120 --> 00:04:39.550 align:start position:0% smaller clients but um up until right now<00:04:38.280> they<00:04:38.400> were<00:04:38.600> a<00:04:38.680> little<00:04:38.840> bit<00:04:38.960> too<00:04:39.120> unstable 00:04:39.550 --> 00:04:39.560 align:start position:0% now they were a little bit too unstable 00:04:39.560 --> 00:04:42.950 align:start position:0% now they were a little bit too unstable to<00:04:39.880> integrate<00:04:41.039> and<00:04:42.039> we<00:04:42.160> want<00:04:42.360> to<00:04:42.560> make<00:04:42.720> sure 00:04:42.950 --> 00:04:42.960 align:start position:0% to integrate and we want to make sure 00:04:42.960 --> 00:04:45.150 align:start position:0% to integrate and we want to make sure that<00:04:43.080> the<00:04:43.199> user<00:04:43.479> has<00:04:43.600> a<00:04:43.680> seamless<00:04:44.160> experience 00:04:45.150 --> 00:04:45.160 align:start position:0% that the user has a seamless experience 00:04:45.160 --> 00:04:47.830 align:start position:0% that the user has a seamless experience um<00:04:45.560> in<00:04:45.759> running<00:04:46.039> an<00:04:46.199> ethereum 00:04:47.830 --> 00:04:47.840 align:start position:0% um in running an ethereum 00:04:47.840 --> 00:04:50.670 align:start position:0% um in running an ethereum node<00:04:48.840> so<00:04:49.039> how<00:04:49.160> do<00:04:49.280> you<00:04:49.400> run<00:04:49.600> an<00:04:49.720> ethereum<00:04:50.120> node 00:04:50.670 --> 00:04:50.680 align:start position:0% node so how do you run an ethereum node 00:04:50.680 --> 00:04:53.710 align:start position:0% node so how do you run an ethereum node first<00:04:50.880> of<00:04:51.039> all<00:04:51.320> you<00:04:51.440> can<00:04:51.600> run<00:04:51.759> it<00:04:51.880> on<00:04:52.120> cloud<00:04:52.840> or 00:04:53.710 --> 00:04:53.720 align:start position:0% first of all you can run it on cloud or 00:04:53.720 --> 00:04:57.430 align:start position:0% first of all you can run it on cloud or um<00:04:53.919> on<00:04:54.039> your<00:04:54.160> home<00:04:54.479> PC<00:04:55.479> or<00:04:56.120> um<00:04:56.880> your<00:04:57.120> office 00:04:57.430 --> 00:04:57.440 align:start position:0% um on your home PC or um your office 00:04:57.440 --> 00:05:00.909 align:start position:0% um on your home PC or um your office computer<00:04:58.039> wherever<00:04:58.440> you<00:04:58.600> want<00:04:59.919> um<00:05:00.479> of<00:05:00.639> course 00:05:00.909 --> 00:05:00.919 align:start position:0% computer wherever you want um of course 00:05:00.919 --> 00:05:05.550 align:start position:0% computer wherever you want um of course with<00:05:01.120> Cloud<00:05:01.479> you<00:05:01.600> have<00:05:01.800> AWS<00:05:02.800> gcp<00:05:04.039> hna<00:05:05.039> um<00:05:05.320> and 00:05:05.550 --> 00:05:05.560 align:start position:0% with Cloud you have AWS gcp hna um and 00:05:05.560 --> 00:05:07.990 align:start position:0% with Cloud you have AWS gcp hna um and our<00:05:05.800> new<00:05:06.000> product<00:05:06.320> serum<00:05:06.720> plus<00:05:07.000> of<00:05:07.160> course 00:05:07.990 --> 00:05:08.000 align:start position:0% our new product serum plus of course 00:05:08.000 --> 00:05:11.310 align:start position:0% our new product serum plus of course which<00:05:08.120> makes<00:05:08.360> it<00:05:08.520> very<00:05:08.759> easy<00:05:09.560> um<00:05:10.320> to<00:05:11.000> to<00:05:11.120> use 00:05:11.310 --> 00:05:11.320 align:start position:0% which makes it very easy um to to use 00:05:11.320 --> 00:05:14.749 align:start position:0% which makes it very easy um to to use with<00:05:11.800> steum<00:05:12.800> with<00:05:13.000> arm<00:05:13.639> it's<00:05:13.800> a<00:05:13.880> little<00:05:14.080> bit 00:05:14.749 --> 00:05:14.759 align:start position:0% with steum with arm it's a little bit 00:05:14.759 --> 00:05:17.430 align:start position:0% with steum with arm it's a little bit complicated<00:05:15.759> you<00:05:15.960> could<00:05:16.240> run<00:05:16.680> a<00:05:16.880> full<00:05:17.160> node 00:05:17.430 --> 00:05:17.440 align:start position:0% complicated you could run a full node 00:05:17.440 --> 00:05:19.749 align:start position:0% complicated you could run a full node with<00:05:17.639> Raspberry<00:05:18.120> Pi<00:05:18.360> 4<00:05:19.120> but<00:05:19.280> it's<00:05:19.440> a<00:05:19.560> little 00:05:19.749 --> 00:05:19.759 align:start position:0% with Raspberry Pi 4 but it's a little 00:05:19.759 --> 00:05:22.830 align:start position:0% with Raspberry Pi 4 but it's a little bit<00:05:19.960> slow<00:05:20.520> so<00:05:20.919> I<00:05:21.039> would<00:05:21.199> not<00:05:21.400> recommend<00:05:21.800> it<00:05:22.720> if 00:05:22.830 --> 00:05:22.840 align:start position:0% bit slow so I would not recommend it if 00:05:22.840 --> 00:05:24.950 align:start position:0% bit slow so I would not recommend it if you<00:05:23.039> want<00:05:23.400> to<00:05:23.680> use<00:05:23.960> Arm<00:05:24.400> I<00:05:24.479> would<00:05:24.639> really 00:05:24.950 --> 00:05:24.960 align:start position:0% you want to use Arm I would really 00:05:24.960 --> 00:05:28.430 align:start position:0% you want to use Arm I would really recommend<00:05:25.520> the<00:05:25.919> orok<00:05:26.440> P<00:05:27.080> 5B<00:05:27.759> or<00:05:27.919> the<00:05:28.039> orange 00:05:28.430 --> 00:05:28.440 align:start position:0% recommend the orok P 5B or the orange 00:05:28.440 --> 00:05:31.790 align:start position:0% recommend the orok P 5B or the orange pi5<00:05:29.080> it's<00:05:29.280> um<00:05:29.800> much<00:05:30.000> smoother<00:05:30.800> experience 00:05:31.790 --> 00:05:31.800 align:start position:0% pi5 it's um much smoother experience 00:05:31.800 --> 00:05:33.230 align:start position:0% pi5 it's um much smoother experience especially<00:05:32.199> on<00:05:32.360> Main 00:05:33.230 --> 00:05:33.240 align:start position:0% especially on Main 00:05:33.240 --> 00:05:37.710 align:start position:0% especially on Main net<00:05:34.240> with<00:05:35.199> x86<00:05:36.039> machines<00:05:36.919> generally<00:05:37.440> just 00:05:37.710 --> 00:05:37.720 align:start position:0% net with x86 machines generally just 00:05:37.720 --> 00:05:41.189 align:start position:0% net with x86 machines generally just choose<00:05:38.479> um<00:05:38.720> a<00:05:38.840> CPU<00:05:39.280> with<00:05:39.440> a<00:05:39.560> benchmark<00:05:40.000> over 00:05:41.189 --> 00:05:41.199 align:start position:0% choose um a CPU with a benchmark over 00:05:41.199 --> 00:05:44.350 align:start position:0% choose um a CPU with a benchmark over 20,000<00:05:42.199> that's<00:05:42.639> for<00:05:42.840> some<00:05:43.160> that<00:05:43.360> might<00:05:43.800> sound 00:05:44.350 --> 00:05:44.360 align:start position:0% 20,000 that's for some that might sound 00:05:44.360 --> 00:05:47.590 align:start position:0% 20,000 that's for some that might sound a<00:05:44.520> lot<00:05:45.039> but<00:05:45.319> if<00:05:45.440> there<00:05:45.680> are<00:05:46.360> um<00:05:47.199> uh<00:05:47.360> some 00:05:47.590 --> 00:05:47.600 align:start position:0% a lot but if there are um uh some 00:05:47.600 --> 00:05:50.390 align:start position:0% a lot but if there are um uh some network<00:05:48.440> issues<00:05:49.000> then<00:05:49.479> you<00:05:49.639> will<00:05:49.800> be<00:05:50.000> happy<00:05:50.240> to 00:05:50.390 --> 00:05:50.400 align:start position:0% network issues then you will be happy to 00:05:50.400 --> 00:05:53.309 align:start position:0% network issues then you will be happy to have<00:05:50.600> some<00:05:51.120> some<00:05:51.280> more<00:05:51.479> CPU<00:05:52.000> power<00:05:52.319> to<00:05:53.039> to 00:05:53.309 --> 00:05:53.319 align:start position:0% have some some more CPU power to to 00:05:53.319 --> 00:05:57.430 align:start position:0% have some some more CPU power to to actually<00:05:54.080> um<00:05:54.680> deal<00:05:55.120> with<00:05:55.360> these<00:05:55.600> issues<00:05:56.600> 60<00:05:57.000> G 00:05:57.430 --> 00:05:57.440 align:start position:0% actually um deal with these issues 60 G 00:05:57.440 --> 00:05:59.990 align:start position:0% actually um deal with these issues 60 G gabt<00:05:57.919> of<00:05:58.080> memory<00:05:58.960> are<00:05:59.160> in<00:05:59.280> my<00:05:59.400> op<00:05:59.639> opinion<00:05:59.880> a 00:05:59.990 --> 00:06:00.000 align:start position:0% gabt of memory are in my op opinion a 00:06:00.000 --> 00:06:02.390 align:start position:0% gabt of memory are in my op opinion a must<00:06:00.240> to<00:06:00.360> run<00:06:00.520> on<00:06:00.639> Main<00:06:00.919> net<00:06:01.560> everything<00:06:01.960> below 00:06:02.390 --> 00:06:02.400 align:start position:0% must to run on Main net everything below 00:06:02.400 --> 00:06:04.309 align:start position:0% must to run on Main net everything below that<00:06:02.600> it's<00:06:03.120> it's<00:06:03.280> already<00:06:03.639> a 00:06:04.309 --> 00:06:04.319 align:start position:0% that it's it's already a 00:06:04.319 --> 00:06:09.309 align:start position:0% that it's it's already a pain<00:06:05.319> uh<00:06:05.440> 2<00:06:05.680> terab<00:06:06.360> SSD<00:06:07.720> um<00:06:08.720> I<00:06:08.919> want<00:06:09.120> to 00:06:09.309 --> 00:06:09.319 align:start position:0% pain uh 2 terab SSD um I want to 00:06:09.319 --> 00:06:11.189 align:start position:0% pain uh 2 terab SSD um I want to emphasize<00:06:09.919> SSD 00:06:11.189 --> 00:06:11.199 align:start position:0% emphasize SSD 00:06:11.199 --> 00:06:14.870 align:start position:0% emphasize SSD here<00:06:12.199> um<00:06:12.560> old<00:06:12.919> hdds<00:06:13.919> they<00:06:14.039> don't<00:06:14.280> work<00:06:14.560> well 00:06:14.870 --> 00:06:14.880 align:start position:0% here um old hdds they don't work well 00:06:14.880 --> 00:06:18.350 align:start position:0% here um old hdds they don't work well with<00:06:15.199> with<00:06:15.520> with<00:06:15.720> nodes<00:06:16.199> also<00:06:16.520> not<00:06:16.840> with<00:06:17.400> um 00:06:18.350 --> 00:06:18.360 align:start position:0% with with with nodes also not with um 00:06:18.360 --> 00:06:21.589 align:start position:0% with with with nodes also not with um full<00:06:18.639> nodes<00:06:19.360> like<00:06:20.360> um<00:06:20.759> and<00:06:21.000> especially<00:06:21.440> not 00:06:21.589 --> 00:06:21.599 align:start position:0% full nodes like um and especially not 00:06:21.599 --> 00:06:24.309 align:start position:0% full nodes like um and especially not with<00:06:21.800> archive<00:06:22.199> nodes<00:06:22.840> two<00:06:23.120> terab<00:06:23.599> might<00:06:23.840> be<00:06:24.160> a 00:06:24.309 --> 00:06:24.319 align:start position:0% with archive nodes two terab might be a 00:06:24.319 --> 00:06:26.510 align:start position:0% with archive nodes two terab might be a little<00:06:24.560> bit<00:06:24.759> on<00:06:24.919> the<00:06:25.039> short<00:06:25.479> side<00:06:26.080> uh<00:06:26.199> for<00:06:26.360> the 00:06:26.510 --> 00:06:26.520 align:start position:0% little bit on the short side uh for the 00:06:26.520 --> 00:06:31.469 align:start position:0% little bit on the short side uh for the long<00:06:26.800> run<00:06:27.800> as<00:06:28.000> well<00:06:28.240> as<00:06:29.240> um<00:06:30.000> to<00:06:30.520> less<00:06:30.880> for<00:06:31.240> some 00:06:31.469 --> 00:06:31.479 align:start position:0% long run as well as um to less for some 00:06:31.479 --> 00:06:34.350 align:start position:0% long run as well as um to less for some of<00:06:31.680> the<00:06:32.120> clients<00:06:33.120> we<00:06:33.240> know<00:06:33.440> that<00:06:33.639> some<00:06:33.919> clients 00:06:34.350 --> 00:06:34.360 align:start position:0% of the clients we know that some clients 00:06:34.360 --> 00:06:38.070 align:start position:0% of the clients we know that some clients don't<00:06:34.840> prune<00:06:35.280> very<00:06:35.560> well<00:06:36.000> like<00:06:36.360> um<00:06:37.080> delete<00:06:37.639> all 00:06:38.070 --> 00:06:38.080 align:start position:0% don't prune very well like um delete all 00:06:38.080 --> 00:06:40.870 align:start position:0% don't prune very well like um delete all old<00:06:38.520> data<00:06:38.919> that<00:06:39.120> they<00:06:39.280> don't<00:06:39.960> need 00:06:40.870 --> 00:06:40.880 align:start position:0% old data that they don't need 00:06:40.880 --> 00:06:42.550 align:start position:0% old data that they don't need anymore 00:06:42.550 --> 00:06:42.560 align:start position:0% anymore 00:06:42.560 --> 00:06:46.950 align:start position:0% anymore um<00:06:43.560> we<00:06:44.400> we<00:06:44.560> would<00:06:45.360> if<00:06:45.720> if<00:06:45.840> you<00:06:45.960> want<00:06:46.160> to<00:06:46.479> be<00:06:46.759> like 00:06:46.950 --> 00:06:46.960 align:start position:0% um we we would if if you want to be like 00:06:46.960 --> 00:06:49.309 align:start position:0% um we we would if if you want to be like future<00:06:47.400> proof<00:06:47.759> then<00:06:48.080> go<00:06:48.240> for<00:06:48.560> three<00:06:48.840> or<00:06:49.039> four 00:06:49.309 --> 00:06:49.319 align:start position:0% future proof then go for three or four 00:06:49.319 --> 00:06:52.309 align:start position:0% future proof then go for three or four terabytes<00:06:50.039> that's<00:06:50.599> that's<00:06:50.800> way<00:06:51.160> better<00:06:52.160> but 00:06:52.309 --> 00:06:52.319 align:start position:0% terabytes that's that's way better but 00:06:52.319 --> 00:06:54.870 align:start position:0% terabytes that's that's way better but two<00:06:52.520> terabyt<00:06:53.000> should<00:06:53.360> at<00:06:53.560> least<00:06:53.800> give<00:06:53.919> you<00:06:54.120> a<00:06:54.759> a 00:06:54.870 --> 00:06:54.880 align:start position:0% two terabyt should at least give you a a 00:06:54.880 --> 00:06:57.309 align:start position:0% two terabyt should at least give you a a head<00:06:55.120> start<00:06:55.599> and<00:06:56.000> and<00:06:56.199> make<00:06:56.360> sure<00:06:57.000> everything 00:06:57.309 --> 00:06:57.319 align:start position:0% head start and and make sure everything 00:06:57.319 --> 00:07:08.909 align:start position:0% head start and and make sure everything runs<00:06:57.599> smoothly<00:06:58.000> in<00:06:58.120> the<00:06:58.280> beginning 00:07:08.909 --> 00:07:08.919 align:start position:0% 00:07:08.919 --> 00:07:10.550 align:start position:0% a<00:07:09.080> sorry<00:07:09.400> wrong 00:07:10.550 --> 00:07:10.560 align:start position:0% a sorry wrong 00:07:10.560 --> 00:07:14.909 align:start position:0% a sorry wrong button<00:07:11.560> okay<00:07:11.759> then<00:07:11.960> thank<00:07:12.080> you<00:07:12.240> very<00:07:12.599> much<00:07:13.919> um 00:07:14.909 --> 00:07:14.919 align:start position:0% button okay then thank you very much um 00:07:14.919 --> 00:07:16.589 align:start position:0% button okay then thank you very much um welcome<00:07:15.199> to 00:07:16.589 --> 00:07:16.599 align:start position:0% welcome to 00:07:16.599 --> 00:07:18.950 align:start position:0% welcome to David<00:07:17.599> thank<00:07:17.759> you<00:07:17.879> very<00:07:18.080> much<00:07:18.360> I'm<00:07:18.520> take<00:07:18.680> you 00:07:18.950 --> 00:07:18.960 align:start position:0% David thank you very much I'm take you 00:07:18.960 --> 00:07:22.909 align:start position:0% David thank you very much I'm take you over<00:07:19.400> thank<00:07:19.919> you<00:07:20.919> thank<00:07:21.080> you 00:07:22.909 --> 00:07:22.919 align:start position:0% over thank you thank you 00:07:22.919 --> 00:07:26.390 align:start position:0% over thank you thank you Stephanie<00:07:23.919> okay<00:07:24.599> um<00:07:25.440> as<00:07:25.639> this<00:07:25.759> is<00:07:25.879> a<00:07:26.000> beginnner 00:07:26.390 --> 00:07:26.400 align:start position:0% Stephanie okay um as this is a beginnner 00:07:26.400 --> 00:07:30.270 align:start position:0% Stephanie okay um as this is a beginnner workshop<00:07:27.280> um<00:07:27.720> we<00:07:28.120> now<00:07:28.440> want<00:07:28.639> to<00:07:28.800> go<00:07:29.160> into<00:07:29.520> to<00:07:30.120> um 00:07:30.270 --> 00:07:30.280 align:start position:0% workshop um we now want to go into to um 00:07:30.280 --> 00:07:32.950 align:start position:0% workshop um we now want to go into to um the<00:07:30.440> whole<00:07:30.680> staking<00:07:31.280> process<00:07:32.160> we<00:07:32.280> want<00:07:32.520> to 00:07:32.950 --> 00:07:32.960 align:start position:0% the whole staking process we want to 00:07:32.960 --> 00:07:35.390 align:start position:0% the whole staking process we want to walk<00:07:33.240> you<00:07:33.680> step<00:07:33.960> by<00:07:34.199> step<00:07:34.440> through<00:07:34.720> it<00:07:35.160> because 00:07:35.390 --> 00:07:35.400 align:start position:0% walk you step by step through it because 00:07:35.400 --> 00:07:39.110 align:start position:0% walk you step by step through it because we<00:07:35.560> have<00:07:35.720> enough<00:07:36.160> time<00:07:37.160> and<00:07:37.960> um<00:07:38.520> yeah<00:07:38.720> so<00:07:38.960> the 00:07:39.110 --> 00:07:39.120 align:start position:0% we have enough time and um yeah so the 00:07:39.120 --> 00:07:41.550 align:start position:0% we have enough time and um yeah so the next<00:07:39.319> point<00:07:39.520> is<00:07:39.639> taken<00:07:39.960> with<00:07:40.120> steum 00:07:41.550 --> 00:07:41.560 align:start position:0% next point is taken with steum 00:07:41.560 --> 00:07:45.749 align:start position:0% next point is taken with steum setup<00:07:42.560> so<00:07:42.800> there<00:07:42.919> are<00:07:43.879> four<00:07:44.720> overall<00:07:45.319> steps 00:07:45.749 --> 00:07:45.759 align:start position:0% setup so there are four overall steps 00:07:45.759 --> 00:07:49.390 align:start position:0% setup so there are four overall steps you<00:07:45.919> have<00:07:46.039> to<00:07:46.319> do<00:07:47.319> for<00:07:47.840> um<00:07:48.039> to<00:07:48.520> to<00:07:48.800> stake 00:07:49.390 --> 00:07:49.400 align:start position:0% you have to do for um to to stake 00:07:49.400 --> 00:07:53.830 align:start position:0% you have to do for um to to stake yourself<00:07:50.400> first<00:07:50.639> of<00:07:50.800> all<00:07:51.639> um<00:07:52.039> yeah<00:07:52.319> you<00:07:53.199> uh<00:07:53.720> you 00:07:53.830 --> 00:07:53.840 align:start position:0% yourself first of all um yeah you uh you 00:07:53.840 --> 00:07:56.350 align:start position:0% yourself first of all um yeah you uh you have<00:07:53.960> to<00:07:54.159> have<00:07:54.560> 32<00:07:55.120> e<00:07:55.440> but<00:07:55.599> that<00:07:55.720> you<00:07:55.919> already 00:07:56.350 --> 00:07:56.360 align:start position:0% have to have 32 e but that you already 00:07:56.360 --> 00:07:58.390 align:start position:0% have to have 32 e but that you already know<00:07:57.360> maybe<00:07:57.639> that<00:07:57.759> will<00:07:57.919> change<00:07:58.159> in<00:07:58.240> the 00:07:58.390 --> 00:07:58.400 align:start position:0% know maybe that will change in the 00:07:58.400 --> 00:08:01.589 align:start position:0% know maybe that will change in the future<00:07:59.080> but<00:07:59.199> at<00:07:59.319> the<00:07:59.560> moment<00:07:59.759> is<00:08:00.000> 32<00:08:01.000> then<00:08:01.360> you 00:08:01.589 --> 00:08:01.599 align:start position:0% future but at the moment is 32 then you 00:08:01.599 --> 00:08:04.110 align:start position:0% future but at the moment is 32 then you have<00:08:01.720> to<00:08:01.879> create<00:08:02.159> your<00:08:02.400> validator<00:08:02.960> keys<00:08:03.680> um 00:08:04.110 --> 00:08:04.120 align:start position:0% have to create your validator keys um 00:08:04.120 --> 00:08:06.830 align:start position:0% have to create your validator keys um with<00:08:04.440> a<00:08:04.560> c<00:08:04.840> Trace<00:08:05.520> um<00:08:05.720> we<00:08:05.840> will<00:08:06.080> show<00:08:06.280> you<00:08:06.520> this 00:08:06.830 --> 00:08:06.840 align:start position:0% with a c Trace um we will show you this 00:08:06.840 --> 00:08:11.029 align:start position:0% with a c Trace um we will show you this today<00:08:07.319> with<00:08:07.840> um<00:08:08.000> a<00:08:08.080> tool<00:08:08.319> called<00:08:09.080> Vue<00:08:10.080> um<00:08:10.599> then 00:08:11.029 --> 00:08:11.039 align:start position:0% today with um a tool called Vue um then 00:08:11.039 --> 00:08:14.510 align:start position:0% today with um a tool called Vue um then you<00:08:11.159> should<00:08:12.000> um<00:08:12.599> do<00:08:12.800> your<00:08:13.080> validator<00:08:13.720> setup<00:08:14.159> so 00:08:14.510 --> 00:08:14.520 align:start position:0% you should um do your validator setup so 00:08:14.520 --> 00:08:17.550 align:start position:0% you should um do your validator setup so a<00:08:14.639> full<00:08:14.919> node<00:08:15.720> run<00:08:16.039> with<00:08:16.199> a<00:08:16.400> validator<00:08:17.400> that 00:08:17.550 --> 00:08:17.560 align:start position:0% a full node run with a validator that 00:08:17.560 --> 00:08:19.230 align:start position:0% a full node run with a validator that you<00:08:17.639> can<00:08:17.800> do<00:08:18.000> with<00:08:18.159> steum<00:08:18.639> but<00:08:18.960> there<00:08:19.080> are 00:08:19.230 --> 00:08:19.240 align:start position:0% you can do with steum but there are 00:08:19.240 --> 00:08:22.469 align:start position:0% you can do with steum but there are other<00:08:19.440> tools<00:08:19.800> as<00:08:20.000> well<00:08:21.000> then<00:08:21.479> and<00:08:22.080> then 00:08:22.469 --> 00:08:22.479 align:start position:0% other tools as well then and then 00:08:22.479 --> 00:08:24.550 align:start position:0% other tools as well then and then afterwards<00:08:23.199> if<00:08:23.319> you<00:08:23.479> have<00:08:23.599> a<00:08:23.720> running<00:08:24.039> setup 00:08:24.550 --> 00:08:24.560 align:start position:0% afterwards if you have a running setup 00:08:24.560 --> 00:08:27.309 align:start position:0% afterwards if you have a running setup you<00:08:24.680> should<00:08:25.360> um<00:08:25.520> load<00:08:25.879> up<00:08:26.080> a<00:08:26.520> validator<00:08:27.080> key 00:08:27.309 --> 00:08:27.319 align:start position:0% you should um load up a validator key 00:08:27.319 --> 00:08:30.670 align:start position:0% you should um load up a validator key with<00:08:27.520> the<00:08:27.879> 32<00:08:28.520> e<00:08:29.280> and<00:08:29.560> and<00:08:29.879> of<00:08:30.039> course<00:08:30.360> always 00:08:30.670 --> 00:08:30.680 align:start position:0% with the 32 e and and of course always 00:08:30.680 --> 00:08:33.709 align:start position:0% with the 32 e and and of course always should<00:08:30.960> start<00:08:31.319> with<00:08:31.759> um<00:08:31.919> test<00:08:32.320> net<00:08:33.320> um<00:08:33.599> if 00:08:33.709 --> 00:08:33.719 align:start position:0% should start with um test net um if 00:08:33.719 --> 00:08:35.870 align:start position:0% should start with um test net um if you're<00:08:33.880> new<00:08:34.080> to<00:08:34.240> the<00:08:34.399> stuff<00:08:35.240> and<00:08:35.440> the<00:08:35.560> fourth 00:08:35.870 --> 00:08:35.880 align:start position:0% you're new to the stuff and the fourth 00:08:35.880 --> 00:08:39.750 align:start position:0% you're new to the stuff and the fourth step<00:08:36.200> is<00:08:36.640> then<00:08:37.000> afterwards<00:08:38.000> enjoy<00:08:39.000> the 00:08:39.750 --> 00:08:39.760 align:start position:0% step is then afterwards enjoy the 00:08:39.760 --> 00:08:41.589 align:start position:0% step is then afterwards enjoy the journey 00:08:41.589 --> 00:08:41.599 align:start position:0% journey 00:08:41.599 --> 00:08:47.430 align:start position:0% journey okay<00:08:42.640> so<00:08:43.640> um<00:08:44.000> I<00:08:44.920> try<00:08:45.240> to<00:08:46.240> um<00:08:46.720> emphasize<00:08:47.240> the 00:08:47.430 --> 00:08:47.440 align:start position:0% okay so um I try to um emphasize the 00:08:47.440 --> 00:08:53.350 align:start position:0% okay so um I try to um emphasize the whole<00:08:47.800> process<00:08:48.399> again<00:08:49.000> um<00:08:49.320> in<00:08:49.480> a<00:08:50.160> in<00:08:50.240> a<00:08:50.519> picture 00:08:53.350 --> 00:08:53.360 align:start position:0% whole process again um in a in a picture 00:08:53.360 --> 00:08:59.110 align:start position:0% whole process again um in a in a picture so<00:08:54.360> you<00:08:54.800> create<00:08:55.279> here<00:08:55.760> the<00:08:56.440> key<00:08:57.880> then<00:08:58.880> after 00:08:59.110 --> 00:08:59.120 align:start position:0% so you create here the key then after 00:08:59.120 --> 00:09:03.949 align:start position:0% so you create here the key then after you<00:08:59.480> have<00:08:59.560> a<00:08:59.680> running<00:09:00.160> setup<00:09:01.160> then<00:09:01.760> you<00:09:02.760> um<00:09:03.760> in 00:09:03.949 --> 00:09:03.959 align:start position:0% you have a running setup then you um in 00:09:03.959 --> 00:09:07.190 align:start position:0% you have a running setup then you um in this<00:09:04.560> uh<00:09:04.680> in<00:09:04.839> the<00:09:05.040> key<00:09:05.360> you<00:09:05.959> um<00:09:06.480> uh 00:09:07.190 --> 00:09:07.200 align:start position:0% this uh in the key you um uh 00:09:07.200 --> 00:09:10.389 align:start position:0% this uh in the key you um uh do<00:09:08.200> uh<00:09:08.279> you<00:09:08.480> give<00:09:09.120> the<00:09:09.360> the<00:09:09.600> withdrawal 00:09:10.389 --> 00:09:10.399 align:start position:0% do uh you give the the withdrawal 00:09:10.399 --> 00:09:14.590 align:start position:0% do uh you give the the withdrawal address<00:09:11.399> um<00:09:11.680> where<00:09:12.000> the<00:09:12.560> where<00:09:12.800> the<00:09:12.959> 42e<00:09:13.839> view 00:09:14.590 --> 00:09:14.600 align:start position:0% address um where the where the 42e view 00:09:14.600 --> 00:09:17.150 align:start position:0% address um where the where the 42e view um<00:09:14.760> will<00:09:14.880> be<00:09:15.040> sent<00:09:15.480> back<00:09:15.800> and<00:09:15.959> where<00:09:16.160> the<00:09:16.760> um 00:09:17.150 --> 00:09:17.160 align:start position:0% um will be sent back and where the um 00:09:17.160 --> 00:09:19.590 align:start position:0% um will be sent back and where the um attestation<00:09:18.120> rewards<00:09:18.600> and<00:09:18.760> the<00:09:18.880> synced 00:09:19.590 --> 00:09:19.600 align:start position:0% attestation rewards and the synced 00:09:19.600 --> 00:09:21.949 align:start position:0% attestation rewards and the synced rewards<00:09:20.399> will<00:09:20.600> also<00:09:20.839> be<00:09:20.959> sent<00:09:21.279> in<00:09:21.399> which 00:09:21.949 --> 00:09:21.959 align:start position:0% rewards will also be sent in which 00:09:21.959 --> 00:09:25.470 align:start position:0% rewards will also be sent in which wallet<00:09:22.959> um<00:09:23.200> so<00:09:23.519> it's<00:09:23.760> kind<00:09:23.959> of<00:09:24.160> safe<00:09:24.640> after<00:09:25.360> um 00:09:25.470 --> 00:09:25.480 align:start position:0% wallet um so it's kind of safe after um 00:09:25.480 --> 00:09:27.670 align:start position:0% wallet um so it's kind of safe after um you<00:09:25.600> load<00:09:25.839> it<00:09:25.959> up<00:09:26.120> with<00:09:26.279> the<00:09:26.360> 32<00:09:26.880> Eve<00:09:27.240> because 00:09:27.670 --> 00:09:27.680 align:start position:0% you load it up with the 32 Eve because 00:09:27.680 --> 00:09:29.870 align:start position:0% you load it up with the 32 Eve because if<00:09:27.760> you<00:09:27.959> ever<00:09:28.680> um<00:09:28.839> exit<00:09:29.120> your<00:09:29.360> validator<00:09:29.720> the 00:09:29.870 --> 00:09:29.880 align:start position:0% if you ever um exit your validator the 00:09:29.880 --> 00:09:33.790 align:start position:0% if you ever um exit your validator the key<00:09:30.079> it<00:09:30.160> will<00:09:30.440> only<00:09:30.800> go<00:09:31.000> to<00:09:31.680> that<00:09:31.880> wallet<00:09:32.320> so<00:09:33.320> um 00:09:33.790 --> 00:09:33.800 align:start position:0% key it will only go to that wallet so um 00:09:33.800 --> 00:09:36.990 align:start position:0% key it will only go to that wallet so um yeah<00:09:33.959> you're<00:09:34.240> safe<00:09:35.320> afterwards 00:09:36.990 --> 00:09:37.000 align:start position:0% yeah you're safe afterwards 00:09:37.000 --> 00:09:42.509 align:start position:0% yeah you're safe afterwards then<00:09:38.000> um<00:09:38.360> then<00:09:38.880> you<00:09:39.600> um<00:09:40.360> um<00:09:41.160> yeah<00:09:41.880> after<00:09:42.279> after 00:09:42.509 --> 00:09:42.519 align:start position:0% then um then you um um yeah after after 00:09:42.519 --> 00:09:45.710 align:start position:0% then um then you um um yeah after after that<00:09:42.760> process<00:09:43.320> after<00:09:43.480> you<00:09:43.959> loaded<00:09:44.360> up<00:09:44.560> the<00:09:44.760> key 00:09:45.710 --> 00:09:45.720 align:start position:0% that process after you loaded up the key 00:09:45.720 --> 00:09:49.670 align:start position:0% that process after you loaded up the key um<00:09:46.040> you<00:09:46.440> have<00:09:46.680> some<00:09:46.959> time<00:09:47.200> to<00:09:47.399> be<00:09:48.160> um<00:09:48.760> um<00:09:49.480> after 00:09:49.670 --> 00:09:49.680 align:start position:0% um you have some time to be um um after 00:09:49.680 --> 00:09:52.030 align:start position:0% um you have some time to be um um after you<00:09:49.880> deposited<00:09:50.399> the<00:09:50.519> 42<00:09:51.040> Eve<00:09:51.519> you<00:09:51.680> have<00:09:51.839> some 00:09:52.030 --> 00:09:52.040 align:start position:0% you deposited the 42 Eve you have some 00:09:52.040 --> 00:09:54.910 align:start position:0% you deposited the 42 Eve you have some time<00:09:52.240> to<00:09:52.399> be<00:09:52.839> approved<00:09:53.839> um<00:09:54.000> on<00:09:54.160> mayet<00:09:54.600> that's<00:09:54.839> I 00:09:54.910 --> 00:09:54.920 align:start position:0% time to be approved um on mayet that's I 00:09:54.920 --> 00:09:57.590 align:start position:0% time to be approved um on mayet that's I think<00:09:55.320> um<00:09:55.519> around<00:09:55.839> 7<00:09:56.240> days<00:09:57.079> and<00:09:57.320> in<00:09:57.440> the 00:09:57.590 --> 00:09:57.600 align:start position:0% think um around 7 days and in the 00:09:57.600 --> 00:10:00.430 align:start position:0% think um around 7 days and in the meantime<00:09:58.600> um<00:09:58.839> you<00:09:59.040> can<00:09:59.399> start<00:09:59.640> a<00:09:59.839> validator 00:10:00.430 --> 00:10:00.440 align:start position:0% meantime um you can start a validator 00:10:00.440 --> 00:10:03.790 align:start position:0% meantime um you can start a validator client<00:10:01.240> and<00:10:01.959> um<00:10:02.600> uh<00:10:02.720> set<00:10:02.959> the<00:10:03.079> fee<00:10:03.360> recipient 00:10:03.790 --> 00:10:03.800 align:start position:0% client and um uh set the fee recipient 00:10:03.800 --> 00:10:06.430 align:start position:0% client and um uh set the fee recipient address<00:10:04.600> so<00:10:04.839> that's<00:10:05.079> another<00:10:05.839> um<00:10:06.279> uh 00:10:06.430 --> 00:10:06.440 align:start position:0% address so that's another um uh 00:10:06.440 --> 00:10:08.590 align:start position:0% address so that's another um uh possibility<00:10:07.040> to<00:10:07.399> earn<00:10:07.760> rewards<00:10:08.200> and<00:10:08.399> there 00:10:08.590 --> 00:10:08.600 align:start position:0% possibility to earn rewards and there 00:10:08.600 --> 00:10:11.389 align:start position:0% possibility to earn rewards and there you<00:10:08.760> get<00:10:09.079> the<00:10:09.839> on<00:10:10.120> and<00:10:10.399> and<00:10:10.600> the<00:10:10.680> fee<00:10:10.959> recipient 00:10:11.389 --> 00:10:11.399 align:start position:0% you get the on and and the fee recipient 00:10:11.399 --> 00:10:13.870 align:start position:0% you get the on and and the fee recipient is<00:10:11.519> a<00:10:11.680> wallet<00:10:12.320> where<00:10:12.480> you<00:10:12.720> get<00:10:13.120> get<00:10:13.320> the<00:10:13.519> block 00:10:13.870 --> 00:10:13.880 align:start position:0% is a wallet where you get get the block 00:10:13.880 --> 00:10:15.110 align:start position:0% is a wallet where you get get the block production 00:10:15.110 --> 00:10:15.120 align:start position:0% production 00:10:15.120 --> 00:10:20.430 align:start position:0% production rewards<00:10:16.440> okay<00:10:17.440> so<00:10:18.360> how<00:10:18.720> now<00:10:19.519> um<00:10:19.680> to<00:10:20.000> create<00:10:20.279> a 00:10:20.430 --> 00:10:20.440 align:start position:0% rewards okay so how now um to create a 00:10:20.440 --> 00:10:23.710 align:start position:0% rewards okay so how now um to create a validator<00:10:21.000> key<00:10:21.320> you<00:10:21.560> might<00:10:21.760> be 00:10:23.710 --> 00:10:23.720 align:start position:0% validator key you might be 00:10:23.720 --> 00:10:26.310 align:start position:0% validator key you might be interested<00:10:24.720> um<00:10:25.000> there<00:10:25.120> are<00:10:25.320> different<00:10:25.640> tools 00:10:26.310 --> 00:10:26.320 align:start position:0% interested um there are different tools 00:10:26.320 --> 00:10:27.990 align:start position:0% interested um there are different tools we<00:10:26.440> will<00:10:26.680> use<00:10:26.959> today 00:10:27.990 --> 00:10:28.000 align:start position:0% we will use today 00:10:28.000 --> 00:10:32.550 align:start position:0% we will use today vagu<00:10:29.000> and<00:10:29.600> maybe<00:10:30.600> um<00:10:31.120> yeah<00:10:31.600> um<00:10:31.800> as<00:10:31.959> I<00:10:32.120> will<00:10:32.320> show 00:10:32.550 --> 00:10:32.560 align:start position:0% vagu and maybe um yeah um as I will show 00:10:32.560 --> 00:10:34.069 align:start position:0% vagu and maybe um yeah um as I will show you<00:10:32.720> you<00:10:32.839> shouldn't<00:10:33.200> do<00:10:33.399> it<00:10:33.680> because<00:10:33.959> you 00:10:34.069 --> 00:10:34.079 align:start position:0% you you shouldn't do it because you 00:10:34.079 --> 00:10:37.069 align:start position:0% you you shouldn't do it because you should<00:10:34.279> do<00:10:34.440> it<00:10:34.560> on<00:10:34.720> an<00:10:34.920> extra<00:10:35.320> machine<00:10:36.320> uh<00:10:36.600> best 00:10:37.069 --> 00:10:37.079 align:start position:0% should do it on an extra machine uh best 00:10:37.079 --> 00:10:40.550 align:start position:0% should do it on an extra machine uh best set<00:10:37.440> up<00:10:37.760> only<00:10:38.079> for<00:10:38.519> creating<00:10:38.959> a<00:10:39.200> key<00:10:40.079> with<00:10:40.279> no 00:10:40.550 --> 00:10:40.560 align:start position:0% set up only for creating a key with no 00:10:40.560 --> 00:10:43.750 align:start position:0% set up only for creating a key with no internet<00:10:41.000> connection<00:10:41.920> whatsoever<00:10:42.920> um<00:10:43.320> but 00:10:43.750 --> 00:10:43.760 align:start position:0% internet connection whatsoever um but 00:10:43.760 --> 00:10:47.389 align:start position:0% internet connection whatsoever um but for<00:10:43.959> today<00:10:44.720> um<00:10:45.160> um<00:10:45.399> as<00:10:45.519> we<00:10:45.639> do<00:10:45.800> it<00:10:46.240> only<00:10:46.440> for 00:10:47.389 --> 00:10:47.399 align:start position:0% for today um um as we do it only for 00:10:47.399 --> 00:10:50.550 align:start position:0% for today um um as we do it only for test<00:10:48.399> we<00:10:48.519> will<00:10:49.040> we<00:10:49.160> will<00:10:49.519> I<00:10:49.600> will<00:10:49.760> show<00:10:49.959> you<00:10:50.320> on 00:10:50.550 --> 00:10:50.560 align:start position:0% test we will we will I will show you on 00:10:50.560 --> 00:10:53.430 align:start position:0% test we will we will I will show you on that<00:10:50.800> so<00:10:51.399> um<00:10:51.839> vagu<00:10:52.279> is<00:10:52.360> an<00:10:52.519> open<00:10:52.760> source<00:10:53.000> tool<00:10:53.360> I 00:10:53.430 --> 00:10:53.440 align:start position:0% that so um vagu is an open source tool I 00:10:53.440 --> 00:10:57.430 align:start position:0% that so um vagu is an open source tool I think<00:10:53.600> you<00:10:53.720> can<00:10:54.600> easily 00:10:57.430 --> 00:10:57.440 align:start position:0% 00:10:57.440 --> 00:11:00.829 align:start position:0% find<00:10:58.440> um<00:10:59.399> as<00:10:59.519> I<00:10:59.680> said<00:11:00.320> um<00:11:00.480> if<00:11:00.600> you're<00:11:00.720> a 00:11:00.829 --> 00:11:00.839 align:start position:0% find um as I said um if you're a 00:11:00.839 --> 00:11:03.269 align:start position:0% find um as I said um if you're a beginner<00:11:01.279> you<00:11:01.399> should<00:11:02.079> um<00:11:02.279> use<00:11:02.519> the<00:11:02.720> test<00:11:03.000> nut 00:11:03.269 --> 00:11:03.279 align:start position:0% beginner you should um use the test nut 00:11:03.279 --> 00:11:06.310 align:start position:0% beginner you should um use the test nut for<00:11:03.639> staking<00:11:04.279> holeski<00:11:04.720> is<00:11:04.920> really<00:11:05.920> Pleasant 00:11:06.310 --> 00:11:06.320 align:start position:0% for staking holeski is really Pleasant 00:11:06.320 --> 00:11:07.389 align:start position:0% for staking holeski is really Pleasant to 00:11:07.389 --> 00:11:07.399 align:start position:0% to 00:11:07.399 --> 00:11:10.870 align:start position:0% to use<00:11:08.399> and<00:11:08.839> then<00:11:09.839> first<00:11:10.079> of<00:11:10.200> all<00:11:10.360> you<00:11:10.480> need<00:11:10.680> to 00:11:10.870 --> 00:11:10.880 align:start position:0% use and then first of all you need to 00:11:10.880 --> 00:11:13.150 align:start position:0% use and then first of all you need to create<00:11:11.160> a<00:11:11.279> new<00:11:11.720> recovery 00:11:13.150 --> 00:11:13.160 align:start position:0% create a new recovery 00:11:13.160 --> 00:11:16.430 align:start position:0% create a new recovery phase<00:11:14.160> and<00:11:14.440> as<00:11:14.519> you<00:11:14.639> see<00:11:14.839> the<00:11:14.959> tool<00:11:15.720> um<00:11:16.200> already 00:11:16.430 --> 00:11:16.440 align:start position:0% phase and as you see the tool um already 00:11:16.440 --> 00:11:19.269 align:start position:0% phase and as you see the tool um already Wars<00:11:16.800> me<00:11:16.959> that<00:11:17.120> the<00:11:17.240> internet<00:11:17.560> is<00:11:17.800> connected 00:11:19.269 --> 00:11:19.279 align:start position:0% Wars me that the internet is connected 00:11:19.279 --> 00:11:21.470 align:start position:0% Wars me that the internet is connected so<00:11:20.279> you<00:11:20.519> you<00:11:20.639> should 00:11:21.470 --> 00:11:21.480 align:start position:0% so you you should 00:11:21.480 --> 00:11:24.470 align:start position:0% so you you should really<00:11:22.480> emphasize<00:11:22.920> on 00:11:24.470 --> 00:11:24.480 align:start position:0% really emphasize on 00:11:24.480 --> 00:11:27.710 align:start position:0% really emphasize on that<00:11:25.480> so<00:11:25.639> you<00:11:25.760> see<00:11:26.000> it's<00:11:26.240> it's<00:11:26.480> really<00:11:26.760> easy<00:11:27.000> to 00:11:27.710 --> 00:11:27.720 align:start position:0% that so you see it's it's really easy to 00:11:27.720 --> 00:11:31.590 align:start position:0% that so you see it's it's really easy to do<00:11:28.720> just<00:11:29.320> create<00:11:29.560> a<00:11:29.680> secret<00:11:30.000> recovery<00:11:30.600> phase 00:11:31.590 --> 00:11:31.600 align:start position:0% do just create a secret recovery phase 00:11:31.600 --> 00:11:34.430 align:start position:0% do just create a secret recovery phase and<00:11:31.800> then<00:11:32.760> um<00:11:33.120> like<00:11:33.360> every<00:11:33.800> se<00:11:34.040> phas<00:11:34.360> you 00:11:34.430 --> 00:11:34.440 align:start position:0% and then um like every se phas you 00:11:34.440 --> 00:11:38.150 align:start position:0% and then um like every se phas you should<00:11:34.680> write<00:11:34.880> it<00:11:35.079> down<00:11:35.800> um<00:11:36.320> put<00:11:36.760> it<00:11:37.760> um<00:11:37.959> in 00:11:38.150 --> 00:11:38.160 align:start position:0% should write it down um put it um in 00:11:38.160 --> 00:11:41.910 align:start position:0% should write it down um put it um in steel<00:11:39.120> so<00:11:39.519> that<00:11:39.680> you<00:11:39.839> can't<00:11:40.120> lose<00:11:40.720> it<00:11:41.720> and 00:11:41.910 --> 00:11:41.920 align:start position:0% steel so that you can't lose it and 00:11:41.920 --> 00:11:43.990 align:start position:0% steel so that you can't lose it and never<00:11:42.200> ever<00:11:42.399> share<00:11:42.720> it<00:11:42.920> to<00:11:43.279> with 00:11:43.990 --> 00:11:44.000 align:start position:0% never ever share it to with 00:11:44.000 --> 00:11:52.350 align:start position:0% never ever share it to with anyone<00:11:45.000> except<00:11:45.320> to 00:11:52.350 --> 00:11:52.360 align:start position:0% 00:11:52.360 --> 00:11:53.870 align:start position:0% life 00:11:53.870 --> 00:11:53.880 align:start position:0% life 00:11:53.880 --> 00:11:57.870 align:start position:0% life okay<00:11:54.880> takes<00:11:55.200> up<00:11:55.560> to<00:11:55.800> 30<00:11:56.200> seconds<00:11:56.920> or 00:11:57.870 --> 00:11:57.880 align:start position:0% okay takes up to 30 seconds or 00:11:57.880 --> 00:12:04.590 align:start position:0% okay takes up to 30 seconds or longer<00:11:58.880> very 00:12:04.590 --> 00:12:04.600 align:start position:0% 00:12:04.600 --> 00:12:10.389 align:start position:0% yeah<00:12:05.600> okay<00:12:05.839> yeah<00:12:06.120> could<00:12:06.320> be<00:12:07.320> oh 00:12:10.389 --> 00:12:10.399 align:start position:0% 00:12:10.399 --> 00:12:13.710 align:start position:0% yeah<00:12:11.399> that's<00:12:11.639> hacker<00:12:11.920> tools<00:12:12.240> they're<00:12:12.720> only 00:12:13.710 --> 00:12:13.720 align:start position:0% yeah that's hacker tools they're only 00:12:13.720 --> 00:12:21.110 align:start position:0% yeah that's hacker tools they're only always<00:12:14.120> dark<00:12:14.399> mode 00:12:21.110 --> 00:12:21.120 align:start position:0% 00:12:21.120 --> 00:12:25.150 align:start position:0% so<00:12:22.120> but<00:12:22.320> maybe<00:12:22.600> that's<00:12:22.800> also<00:12:23.199> securing<00:12:24.160> the 00:12:25.150 --> 00:12:25.160 align:start position:0% so but maybe that's also securing the 00:12:25.160 --> 00:12:27.670 align:start position:0% so but maybe that's also securing the the<00:12:25.320> seat<00:12:26.079> race 00:12:27.670 --> 00:12:27.680 align:start position:0% the seat race 00:12:27.680 --> 00:12:33.150 align:start position:0% the seat race some<00:12:28.680> okay 00:12:33.150 --> 00:12:33.160 align:start position:0% 00:12:33.160 --> 00:12:36.110 align:start position:0% um<00:12:34.160> after<00:12:34.440> you<00:12:34.600> have<00:12:35.079> written<00:12:35.639> it<00:12:35.800> down<00:12:36.000> you 00:12:36.110 --> 00:12:36.120 align:start position:0% um after you have written it down you 00:12:36.120 --> 00:12:38.389 align:start position:0% um after you have written it down you have<00:12:36.320> also<00:12:36.519> here<00:12:36.680> the<00:12:36.959> C<00:12:37.360> the<00:12:37.560> option<00:12:37.800> to<00:12:38.079> copy 00:12:38.389 --> 00:12:38.399 align:start position:0% have also here the C the option to copy 00:12:38.399 --> 00:12:41.350 align:start position:0% have also here the C the option to copy it<00:12:38.639> into<00:12:38.839> a<00:12:39.040> file<00:12:40.040> as<00:12:40.120> I<00:12:40.320> said<00:12:40.639> I<00:12:40.720> wouldn't<00:12:41.279> I 00:12:41.350 --> 00:12:41.360 align:start position:0% it into a file as I said I wouldn't I 00:12:41.360 --> 00:12:44.470 align:start position:0% it into a file as I said I wouldn't I wouldn't<00:12:41.639> store<00:12:42.040> it<00:12:42.399> on<00:12:42.720> any<00:12:43.600> um<00:12:44.040> digital 00:12:44.470 --> 00:12:44.480 align:start position:0% wouldn't store it on any um digital 00:12:44.480 --> 00:12:47.629 align:start position:0% wouldn't store it on any um digital device<00:12:44.959> I<00:12:45.040> would<00:12:45.360> really<00:12:46.360> craft<00:12:46.680> it<00:12:46.839> in<00:12:47.040> paper 00:12:47.629 --> 00:12:47.639 align:start position:0% device I would really craft it in paper 00:12:47.639 --> 00:12:48.790 align:start position:0% device I would really craft it in paper or<00:12:47.839> in 00:12:48.790 --> 00:12:48.800 align:start position:0% or in 00:12:48.800 --> 00:12:51.870 align:start position:0% or in steel<00:12:49.800> but<00:12:50.040> I<00:12:50.120> will<00:12:50.360> copy<00:12:50.639> it<00:12:50.839> now<00:12:51.040> for<00:12:51.720> the 00:12:51.870 --> 00:12:51.880 align:start position:0% steel but I will copy it now for the 00:12:51.880 --> 00:12:55.550 align:start position:0% steel but I will copy it now for the ease<00:12:52.160> of<00:12:52.360> the 00:12:55.550 --> 00:12:55.560 align:start position:0% 00:12:55.560 --> 00:13:00.470 align:start position:0% process<00:12:56.560> thank<00:12:56.760> you<00:12:57.639> thank<00:12:57.800> you<00:12:58.720> everybody<00:12:59.600> um 00:13:00.470 --> 00:13:00.480 align:start position:0% process thank you thank you everybody um 00:13:00.480 --> 00:13:01.629 align:start position:0% process thank you thank you everybody um yeah 00:13:01.629 --> 00:13:01.639 align:start position:0% yeah 00:13:01.639 --> 00:13:04.629 align:start position:0% yeah um<00:13:02.639> I<00:13:02.800> I<00:13:03.000> I<00:13:03.079> wouldn't<00:13:03.560> now<00:13:03.760> go<00:13:04.000> back<00:13:04.240> because 00:13:04.629 --> 00:13:04.639 align:start position:0% um I I I wouldn't now go back because 00:13:04.639 --> 00:13:07.870 align:start position:0% um I I I wouldn't now go back because then<00:13:04.800> we<00:13:04.959> have<00:13:05.079> to<00:13:05.880> do<00:13:06.079> a<00:13:06.440> next<00:13:06.720> se<00:13:07.000> phas<00:13:07.279> but<00:13:07.800> I 00:13:07.870 --> 00:13:07.880 align:start position:0% then we have to do a next se phas but I 00:13:07.880 --> 00:13:10.509 align:start position:0% then we have to do a next se phas but I think<00:13:08.199> from<00:13:08.360> now<00:13:08.519> on<00:13:08.720> we're<00:13:08.959> good<00:13:09.519> okay<00:13:10.360> so 00:13:10.509 --> 00:13:10.519 align:start position:0% think from now on we're good okay so 00:13:10.519 --> 00:13:11.670 align:start position:0% think from now on we're good okay so then<00:13:10.639> you<00:13:10.760> go 00:13:11.670 --> 00:13:11.680 align:start position:0% then you go 00:13:11.680 --> 00:13:15.629 align:start position:0% then you go next<00:13:12.680> um<00:13:12.880> it<00:13:13.399> really<00:13:13.839> asks<00:13:14.160> you<00:13:14.440> again<00:13:14.959> if<00:13:15.199> you 00:13:15.629 --> 00:13:15.639 align:start position:0% next um it really asks you again if you 00:13:15.639 --> 00:13:18.629 align:start position:0% next um it really asks you again if you if<00:13:15.760> you<00:13:16.040> ped<00:13:16.320> it<00:13:16.959> up<00:13:17.959> I'm 00:13:18.629 --> 00:13:18.639 align:start position:0% if you ped it up I'm 00:13:18.639 --> 00:13:24.430 align:start position:0% if you ped it up I'm sure<00:13:19.639> that<00:13:19.800> I'm<00:13:19.959> lying<00:13:20.839> no<00:13:21.240> um<00:13:21.720> and<00:13:22.480> um<00:13:23.440> then 00:13:24.430 --> 00:13:24.440 align:start position:0% sure that I'm lying no um and um then 00:13:24.440 --> 00:13:26.189 align:start position:0% sure that I'm lying no um and um then you<00:13:24.600> have<00:13:24.760> to<00:13:24.959> confirm<00:13:25.399> that<00:13:25.519> you<00:13:25.680> have<00:13:25.839> this 00:13:26.189 --> 00:13:26.199 align:start position:0% you have to confirm that you have this 00:13:26.199 --> 00:13:29.310 align:start position:0% you have to confirm that you have this um<00:13:26.320> secret<00:13:27.000> recovery<00:13:27.480> phase<00:13:28.160> so<00:13:28.320> it<00:13:28.480> makes<00:13:29.120> so 00:13:29.310 --> 00:13:29.320 align:start position:0% um secret recovery phase so it makes so 00:13:29.320 --> 00:13:31.189 align:start position:0% um secret recovery phase so it makes so this<00:13:29.480> tool<00:13:29.680> is<00:13:29.880> really<00:13:30.079> good<00:13:30.519> it<00:13:30.680> really<00:13:30.920> makes 00:13:31.189 --> 00:13:31.199 align:start position:0% this tool is really good it really makes 00:13:31.199 --> 00:13:34.990 align:start position:0% this tool is really good it really makes sure<00:13:31.600> that<00:13:31.760> you're 00:13:34.990 --> 00:13:35.000 align:start position:0% 00:13:35.000 --> 00:13:38.310 align:start position:0% safe<00:13:36.000> now<00:13:36.480> you<00:13:36.639> can<00:13:36.800> check 00:13:38.310 --> 00:13:38.320 align:start position:0% safe now you can check 00:13:38.320 --> 00:13:42.870 align:start position:0% safe now you can check it<00:13:39.320> and<00:13:40.120> you<00:13:40.320> can<00:13:40.519> use<00:13:40.760> your<00:13:41.440> um<00:13:41.600> seat<00:13:41.959> phrase 00:13:42.870 --> 00:13:42.880 align:start position:0% it and you can use your um seat phrase 00:13:42.880 --> 00:13:47.189 align:start position:0% it and you can use your um seat phrase um<00:13:43.800> for<00:13:44.360> generating<00:13:44.920> more<00:13:45.199> than<00:13:45.360> one<00:13:45.639> key<00:13:46.639> and 00:13:47.189 --> 00:13:47.199 align:start position:0% um for generating more than one key and 00:13:47.199 --> 00:13:49.069 align:start position:0% um for generating more than one key and what's<00:13:47.399> the<00:13:47.560> cool<00:13:47.800> thing<00:13:48.120> is<00:13:48.320> you<00:13:48.480> can<00:13:48.760> also 00:13:49.069 --> 00:13:49.079 align:start position:0% what's the cool thing is you can also 00:13:49.079 --> 00:13:51.189 align:start position:0% what's the cool thing is you can also generate<00:13:49.440> it<00:13:49.600> to<00:13:50.000> generate<00:13:50.399> further<00:13:50.800> key<00:13:51.079> if 00:13:51.189 --> 00:13:51.199 align:start position:0% generate it to generate further key if 00:13:51.199 --> 00:13:54.310 align:start position:0% generate it to generate further key if you're<00:13:51.440> in<00:13:51.600> need<00:13:51.880> on<00:13:52.040> a<00:13:52.160> later<00:13:52.560> time<00:13:52.839> so<00:13:53.320> just 00:13:54.310 --> 00:13:54.320 align:start position:0% you're in need on a later time so just 00:13:54.320 --> 00:13:57.509 align:start position:0% you're in need on a later time so just um<00:13:54.959> remember<00:13:55.360> the<00:13:55.600> seat<00:13:55.920> phrase<00:13:56.920> put<00:13:57.079> it<00:13:57.279> in 00:13:57.509 --> 00:13:57.519 align:start position:0% um remember the seat phrase put it in 00:13:57.519 --> 00:14:02.350 align:start position:0% um remember the seat phrase put it in here<00:13:57.880> again<00:13:58.800> and<00:13:59.440> um<00:14:00.399> then<00:14:00.759> you<00:14:01.079> you<00:14:01.360> can 00:14:02.350 --> 00:14:02.360 align:start position:0% here again and um then you you can 00:14:02.360 --> 00:14:04.790 align:start position:0% here again and um then you you can already<00:14:02.920> you<00:14:03.040> can<00:14:03.240> say<00:14:03.720> how<00:14:03.880> much<00:14:04.320> Keys<00:14:04.600> you 00:14:04.790 --> 00:14:04.800 align:start position:0% already you can say how much Keys you 00:14:04.800 --> 00:14:08.509 align:start position:0% already you can say how much Keys you already<00:14:05.600> um<00:14:06.360> created<00:14:07.360> and<00:14:07.639> the<00:14:07.800> number<00:14:08.079> of<00:14:08.320> key 00:14:08.509 --> 00:14:08.519 align:start position:0% already um created and the number of key 00:14:08.519 --> 00:14:12.030 align:start position:0% already um created and the number of key new<00:14:08.759> keys<00:14:09.079> you<00:14:09.560> um<00:14:09.920> you<00:14:10.079> have<00:14:10.399> yeah 00:14:12.030 --> 00:14:12.040 align:start position:0% new keys you um you have yeah 00:14:12.040 --> 00:14:19.310 align:start position:0% new keys you um you have yeah it's<00:14:13.360> so<00:14:14.360> I<00:14:14.480> set<00:14:14.720> the 00:14:19.310 --> 00:14:19.320 align:start position:0% 00:14:19.320 --> 00:14:23.829 align:start position:0% password<00:14:20.320> and<00:14:20.639> in<00:14:21.120> if<00:14:21.360> you're<00:14:21.920> withdrawal 00:14:23.829 --> 00:14:23.839 align:start position:0% password and in if you're withdrawal 00:14:23.839 --> 00:14:27.150 align:start position:0% password and in if you're withdrawal address<00:14:24.839> you<00:14:25.079> might<00:14:25.519> want<00:14:25.680> to<00:14:26.440> take<00:14:26.680> your<00:14:26.880> own 00:14:27.150 --> 00:14:27.160 align:start position:0% address you might want to take your own 00:14:27.160 --> 00:14:38.590 align:start position:0% address you might want to take your own one 00:14:38.590 --> 00:14:38.600 align:start position:0% 00:14:38.600 --> 00:14:46.670 align:start position:0% a<00:14:38.839> perfect<00:14:39.839> already<00:14:40.199> Somey<00:14:40.959> Eve 00:14:46.670 --> 00:14:46.680 align:start position:0% 00:14:46.680 --> 00:14:49.110 align:start position:0% here<00:14:47.680> oh 00:14:49.110 --> 00:14:49.120 align:start position:0% here oh 00:14:49.120 --> 00:14:52.629 align:start position:0% here oh okay<00:14:50.120> take<00:14:50.320> a<00:14:50.560> password<00:14:51.079> that<00:14:51.199> is<00:14:51.399> longer<00:14:51.880> than 00:14:52.629 --> 00:14:52.639 align:start position:0% okay take a password that is longer than 00:14:52.639 --> 00:14:57.110 align:start position:0% okay take a password that is longer than eight 00:14:57.110 --> 00:14:57.120 align:start position:0% 00:14:57.120 --> 00:15:00.030 align:start position:0% characters<00:14:58.120> and<00:14:58.440> remember<00:14:59.360> better<00:14:59.639> write<00:14:59.839> it 00:15:00.030 --> 00:15:00.040 align:start position:0% characters and remember better write it 00:15:00.040 --> 00:15:07.150 align:start position:0% characters and remember better write it maybe<00:15:00.360> also 00:15:07.150 --> 00:15:07.160 align:start position:0% 00:15:07.160 --> 00:15:11.790 align:start position:0% down<00:15:08.160> so<00:15:08.600> and<00:15:09.600> then<00:15:09.759> you're<00:15:10.399> done<00:15:11.399> just<00:15:11.639> have 00:15:11.790 --> 00:15:11.800 align:start position:0% down so and then you're done just have 00:15:11.800 --> 00:15:15.910 align:start position:0% down so and then you're done just have to<00:15:12.120> say<00:15:12.480> where<00:15:12.639> to<00:15:13.160> put<00:15:14.079> um<00:15:14.240> the<00:15:14.399> files<00:15:15.000> I 00:15:15.910 --> 00:15:15.920 align:start position:0% to say where to put um the files I 00:15:15.920 --> 00:15:21.749 align:start position:0% to say where to put um the files I will<00:15:16.920> um<00:15:18.160> yeah<00:15:19.160> it 00:15:21.749 --> 00:15:21.759 align:start position:0% 00:15:21.759 --> 00:15:31.189 align:start position:0% there<00:15:23.240> and<00:15:24.240> create<00:15:24.639> them 00:15:31.189 --> 00:15:31.199 align:start position:0% 00:15:31.199 --> 00:15:34.269 align:start position:0% and<00:15:31.319> I<00:15:31.399> should<00:15:31.560> have<00:15:31.720> created 00:15:34.269 --> 00:15:34.279 align:start position:0% 00:15:34.279 --> 00:15:43.110 align:start position:0% an 00:15:43.110 --> 00:15:43.120 align:start position:0% 00:15:43.120 --> 00:15:45.870 align:start position:0% folder<00:15:44.120> okay<00:15:44.399> that<00:15:44.600> that 00:15:45.870 --> 00:15:45.880 align:start position:0% folder okay that that 00:15:45.880 --> 00:15:48.269 align:start position:0% folder okay that that might<00:15:46.880> take<00:15:47.120> some 00:15:48.269 --> 00:15:48.279 align:start position:0% might take some 00:15:48.279 --> 00:15:52.389 align:start position:0% might take some time<00:15:49.560> and<00:15:50.560> in<00:15:50.720> the 00:15:52.389 --> 00:15:52.399 align:start position:0% time and in the 00:15:52.399 --> 00:15:55.470 align:start position:0% time and in the meantime<00:15:53.399> yeah<00:15:54.199> we<00:15:54.399> we<00:15:54.560> done<00:15:54.759> the 00:15:55.470 --> 00:15:55.480 align:start position:0% meantime yeah we we done the 00:15:55.480 --> 00:15:58.189 align:start position:0% meantime yeah we we done the setup<00:15:56.480> you<00:15:56.639> can<00:15:56.880> also<00:15:57.120> see<00:15:57.319> it<00:15:57.440> in<00:15:57.519> the<00:15:57.680> slides 00:15:58.189 --> 00:15:58.199 align:start position:0% setup you can also see it in the slides 00:15:58.199 --> 00:16:01.189 align:start position:0% setup you can also see it in the slides the<00:15:58.360> qu<00:15:59.240> is<00:15:59.399> shared<00:15:59.920> I<00:16:00.040> think 00:16:01.189 --> 00:16:01.199 align:start position:0% the qu is shared I think 00:16:01.199 --> 00:16:04.269 align:start position:0% the qu is shared I think afterwards<00:16:02.199> um<00:16:02.920> so<00:16:03.600> there<00:16:03.720> is<00:16:03.920> the<00:16:04.079> whole 00:16:04.269 --> 00:16:04.279 align:start position:0% afterwards um so there is the whole 00:16:04.279 --> 00:16:07.350 align:start position:0% afterwards um so there is the whole tutorial 00:16:07.350 --> 00:16:07.360 align:start position:0% 00:16:07.360 --> 00:16:09.829 align:start position:0% again<00:16:08.360> and<00:16:08.519> we're<00:16:08.759> done<00:16:09.040> with<00:16:09.279> creating<00:16:09.680> the 00:16:09.829 --> 00:16:09.839 align:start position:0% again and we're done with creating the 00:16:09.839 --> 00:16:12.309 align:start position:0% again and we're done with creating the validator<00:16:10.360> key<00:16:10.639> so<00:16:11.040> the<00:16:11.240> next<00:16:11.519> thing<00:16:11.920> is<00:16:12.160> to 00:16:12.309 --> 00:16:12.319 align:start position:0% validator key so the next thing is to 00:16:12.319 --> 00:16:15.550 align:start position:0% validator key so the next thing is to doing<00:16:12.560> the<00:16:12.720> setup<00:16:13.399> the<00:16:13.560> validator 00:16:15.550 --> 00:16:15.560 align:start position:0% doing the setup the validator 00:16:15.560 --> 00:16:19.269 align:start position:0% doing the setup the validator setup 00:16:19.269 --> 00:16:19.279 align:start position:0% 00:16:19.279 --> 00:16:24.309 align:start position:0% okay<00:16:20.279> ah<00:16:20.759> yes 00:16:24.309 --> 00:16:24.319 align:start position:0% 00:16:24.319 --> 00:16:32.110 align:start position:0% here<00:16:25.319> no<00:16:26.000> yes<00:16:26.600> so<00:16:26.839> I'm<00:16:27.000> done 00:16:32.110 --> 00:16:32.120 align:start position:0% 00:16:32.120 --> 00:16:37.389 align:start position:0% um<00:16:32.399> yeah<00:16:32.639> you<00:16:32.880> you<00:16:33.160> get<00:16:34.160> um<00:16:34.920> two<00:16:35.319> two<00:16:36.079> files<00:16:37.079> the 00:16:37.389 --> 00:16:37.399 align:start position:0% um yeah you you get um two two files the 00:16:37.399 --> 00:16:40.309 align:start position:0% um yeah you you get um two two files the the<00:16:37.519> one<00:16:37.759> is<00:16:38.000> the<00:16:38.360> deposit<00:16:39.000> file<00:16:39.680> um<00:16:39.880> you<00:16:40.000> will 00:16:40.309 --> 00:16:40.319 align:start position:0% the one is the deposit file um you will 00:16:40.319 --> 00:16:44.870 align:start position:0% the one is the deposit file um you will you<00:16:40.440> will<00:16:40.759> use<00:16:41.079> to<00:16:41.839> um<00:16:42.759> um<00:16:43.040> to<00:16:43.360> to<00:16:43.480> load<00:16:43.800> up<00:16:44.079> the 00:16:44.870 --> 00:16:44.880 align:start position:0% you will use to um um to to load up the 00:16:44.880 --> 00:16:47.670 align:start position:0% you will use to um um to to load up the validator<00:16:45.480> key<00:16:46.240> I<00:16:46.360> will<00:16:46.519> show<00:16:46.759> you<00:16:47.040> or<00:16:47.279> I<00:16:47.519> walk 00:16:47.670 --> 00:16:47.680 align:start position:0% validator key I will show you or I walk 00:16:47.680 --> 00:16:49.670 align:start position:0% validator key I will show you or I walk you<00:16:47.800> through<00:16:48.000> the<00:16:48.160> process<00:16:48.720> as<00:16:48.880> well<00:16:49.120> as<00:16:49.440> uh 00:16:49.670 --> 00:16:49.680 align:start position:0% you through the process as well as uh 00:16:49.680 --> 00:16:51.269 align:start position:0% you through the process as well as uh there 00:16:51.269 --> 00:16:51.279 align:start position:0% there 00:16:51.279 --> 00:16:55.749 align:start position:0% there um<00:16:52.440> um<00:16:53.440> yeah<00:16:53.720> um<00:16:53.839> I<00:16:54.000> work<00:16:54.199> you<00:16:54.399> there<00:16:54.839> um<00:16:55.360> there 00:16:55.749 --> 00:16:55.759 align:start position:0% um um yeah um I work you there um there 00:16:55.759 --> 00:16:58.069 align:start position:0% um um yeah um I work you there um there um<00:16:56.040> we<00:16:56.120> will<00:16:56.319> use<00:16:56.639> Launchpad<00:16:57.240> for<00:16:57.440> that<00:16:57.920> uh 00:16:58.069 --> 00:16:58.079 align:start position:0% um we will use Launchpad for that uh 00:16:58.079 --> 00:17:00.389 align:start position:0% um we will use Launchpad for that uh later<00:16:58.440> on 00:17:00.389 --> 00:17:00.399 align:start position:0% later on 00:17:00.399 --> 00:17:04.189 align:start position:0% later on okay<00:17:00.680> lights<00:17:01.440> are<00:17:02.440> and<00:17:03.240> now<00:17:03.440> we<00:17:03.560> are<00:17:03.959> now<00:17:04.079> we 00:17:04.189 --> 00:17:04.199 align:start position:0% okay lights are and now we are now we 00:17:04.199 --> 00:17:07.429 align:start position:0% okay lights are and now we are now we are<00:17:04.439> starting<00:17:05.439> um<00:17:05.839> to<00:17:06.319> to<00:17:06.480> use<00:17:06.720> steum<00:17:07.280> and 00:17:07.429 --> 00:17:07.439 align:start position:0% are starting um to to use steum and 00:17:07.439 --> 00:17:10.549 align:start position:0% are starting um to to use steum and making<00:17:07.720> our<00:17:08.000> no<00:17:08.319> setup<00:17:08.679> so<00:17:09.439> what<00:17:09.600> you<00:17:09.720> need<00:17:10.079> is 00:17:10.549 --> 00:17:10.559 align:start position:0% making our no setup so what you need is 00:17:10.559 --> 00:17:14.189 align:start position:0% making our no setup so what you need is um<00:17:10.760> you<00:17:10.880> need<00:17:11.079> a<00:17:11.600> U<00:17:11.720> youto<00:17:12.640> server<00:17:13.039> machine<00:17:13.919> um 00:17:14.189 --> 00:17:14.199 align:start position:0% um you need a U youto server machine um 00:17:14.199 --> 00:17:17.789 align:start position:0% um you need a U youto server machine um that<00:17:14.600> that<00:17:14.720> runs<00:17:15.079> on<00:17:15.919> um<00:17:16.240> on<00:17:16.400> on<00:17:16.520> the<00:17:16.640> new<00:17:16.919> subun 00:17:17.789 --> 00:17:17.799 align:start position:0% that that runs on um on on the new subun 00:17:17.799 --> 00:17:21.590 align:start position:0% that that runs on um on on the new subun version<00:17:18.799> stable<00:17:19.520> version<00:17:20.520> um<00:17:20.720> you<00:17:20.880> might<00:17:21.280> also 00:17:21.590 --> 00:17:21.600 align:start position:0% version stable version um you might also 00:17:21.600 --> 00:17:25.110 align:start position:0% version stable version um you might also use<00:17:21.919> other<00:17:22.559> um<00:17:22.760> Linux<00:17:23.640> distributions<00:17:24.640> um<00:17:24.799> but 00:17:25.110 --> 00:17:25.120 align:start position:0% use other um Linux distributions um but 00:17:25.120 --> 00:17:28.069 align:start position:0% use other um Linux distributions um but it's<00:17:25.280> not<00:17:25.480> tested<00:17:25.919> so<00:17:26.600> um<00:17:27.160> we<00:17:27.400> can't<00:17:27.640> guarantee 00:17:28.069 --> 00:17:28.079 align:start position:0% it's not tested so um we can't guarantee 00:17:28.079 --> 00:17:29.870 align:start position:0% it's not tested so um we can't guarantee you<00:17:28.280> anything 00:17:29.870 --> 00:17:29.880 align:start position:0% you anything 00:17:29.880 --> 00:17:34.310 align:start position:0% you anything um<00:17:30.520> so<00:17:31.200> yeah<00:17:31.440> then<00:17:32.039> just<00:17:32.280> give<00:17:32.520> into<00:17:32.840> the 00:17:34.310 --> 00:17:34.320 align:start position:0% um so yeah then just give into the 00:17:34.320 --> 00:17:38.110 align:start position:0% um so yeah then just give into the credentials 00:17:38.110 --> 00:17:38.120 align:start position:0% 00:17:38.120 --> 00:17:41.430 align:start position:0% and<00:17:39.120> if<00:17:39.280> you<00:17:39.679> if<00:17:39.799> you<00:17:40.000> give<00:17:40.600> um<00:17:41.240> the 00:17:41.430 --> 00:17:41.440 align:start position:0% and if you if you give um the 00:17:41.440 --> 00:17:43.549 align:start position:0% and if you if you give um the credentials<00:17:41.960> the<00:17:42.120> first<00:17:42.440> time<00:17:43.080> there's<00:17:43.360> this 00:17:43.549 --> 00:17:43.559 align:start position:0% credentials the first time there's this 00:17:43.559 --> 00:17:46.110 align:start position:0% credentials the first time there's this option<00:17:43.919> to<00:17:44.120> save<00:17:44.440> it<00:17:44.880> with<00:17:45.039> the<00:17:45.200> plus 00:17:46.110 --> 00:17:46.120 align:start position:0% option to save it with the plus 00:17:46.120 --> 00:17:49.110 align:start position:0% option to save it with the plus sign<00:17:47.120> and<00:17:47.360> then 00:17:49.110 --> 00:17:49.120 align:start position:0% sign and then 00:17:49.120 --> 00:17:51.909 align:start position:0% sign and then connect<00:17:50.120> and<00:17:50.320> of<00:17:50.480> course<00:17:50.880> first<00:17:51.360> load<00:17:51.679> down 00:17:51.909 --> 00:17:51.919 align:start position:0% connect and of course first load down 00:17:51.919 --> 00:17:54.789 align:start position:0% connect and of course first load down the<00:17:52.280> steum<00:17:53.039> launcher<00:17:54.039> which<00:17:54.160> you<00:17:54.280> can<00:17:54.440> find<00:17:54.600> on 00:17:54.789 --> 00:17:54.799 align:start position:0% the steum launcher which you can find on 00:17:54.799 --> 00:18:11.710 align:start position:0% the steum launcher which you can find on our<00:17:55.760> website<00:17:56.280> or<00:17:56.440> in<00:17:56.559> the<00:17:56.720> GitHub 00:18:11.710 --> 00:18:11.720 align:start position:0% 00:18:11.720 --> 00:18:15.590 align:start position:0% so<00:18:11.960> let's 00:18:15.590 --> 00:18:15.600 align:start position:0% 00:18:15.600 --> 00:18:19.830 align:start position:0% see<00:18:16.600> okay<00:18:17.559> and<00:18:18.159> now<00:18:18.360> you<00:18:18.480> can<00:18:18.679> see<00:18:19.200> how<00:18:19.480> really 00:18:19.830 --> 00:18:19.840 align:start position:0% see okay and now you can see how really 00:18:19.840 --> 00:18:23.950 align:start position:0% see okay and now you can see how really really<00:18:20.159> easy<00:18:20.480> it<00:18:20.640> is<00:18:20.880> to<00:18:21.559> um<00:18:21.760> set<00:18:22.039> up<00:18:22.440> a<00:18:23.120> aerium 00:18:23.950 --> 00:18:23.960 align:start position:0% really easy it is to um set up a aerium 00:18:23.960 --> 00:18:27.549 align:start position:0% really easy it is to um set up a aerium node<00:18:24.960> um<00:18:25.919> we<00:18:26.240> because<00:18:26.480> we<00:18:26.640> have<00:18:26.840> this<00:18:27.039> oneclick 00:18:27.549 --> 00:18:27.559 align:start position:0% node um we because we have this oneclick 00:18:27.559 --> 00:18:29.950 align:start position:0% node um we because we have this oneclick installation<00:18:28.919> but<00:18:29.120> of<00:18:29.320> course<00:18:29.559> if<00:18:29.679> you<00:18:29.799> want 00:18:29.950 --> 00:18:29.960 align:start position:0% installation but of course if you want 00:18:29.960 --> 00:18:33.270 align:start position:0% installation but of course if you want to<00:18:30.120> do<00:18:30.559> something<00:18:31.120> more<00:18:31.799> um<00:18:32.360> fancier<00:18:33.000> or 00:18:33.270 --> 00:18:33.280 align:start position:0% to do something more um fancier or 00:18:33.280 --> 00:18:36.470 align:start position:0% to do something more um fancier or expert<00:18:34.240> you<00:18:34.400> can<00:18:34.600> do<00:18:34.880> your<00:18:35.240> custom 00:18:36.470 --> 00:18:36.480 align:start position:0% expert you can do your custom 00:18:36.480 --> 00:18:41.350 align:start position:0% expert you can do your custom installation<00:18:37.480> or<00:18:38.080> even<00:18:39.039> um<00:18:39.200> you<00:18:39.360> can<00:18:39.679> export<00:18:40.159> a 00:18:41.350 --> 00:18:41.360 align:start position:0% installation or even um you can export a 00:18:41.360 --> 00:18:43.430 align:start position:0% installation or even um you can export a configuration<00:18:42.360> um<00:18:42.600> after<00:18:42.799> you<00:18:42.919> have<00:18:43.080> set<00:18:43.280> up 00:18:43.430 --> 00:18:43.440 align:start position:0% configuration um after you have set up 00:18:43.440 --> 00:18:45.470 align:start position:0% configuration um after you have set up an<00:18:43.600> ethereum<00:18:44.080> note<00:18:44.320> with<00:18:44.520> sterium<00:18:45.039> and<00:18:45.240> un 00:18:45.470 --> 00:18:45.480 align:start position:0% an ethereum note with sterium and un 00:18:45.480 --> 00:18:49.390 align:start position:0% an ethereum note with sterium and un imported<00:18:46.080> there<00:18:46.280> so<00:18:47.200> you<00:18:47.679> can<00:18:48.679> but<00:18:48.799> we<00:18:48.919> will<00:18:49.159> go 00:18:49.390 --> 00:18:49.400 align:start position:0% imported there so you can but we will go 00:18:49.400 --> 00:18:51.310 align:start position:0% imported there so you can but we will go up<00:18:49.520> for<00:18:49.679> the<00:18:49.840> beginner<00:18:50.240> session<00:18:50.640> today<00:18:51.080> with 00:18:51.310 --> 00:18:51.320 align:start position:0% up for the beginner session today with 00:18:51.320 --> 00:18:54.350 align:start position:0% up for the beginner session today with the<00:18:51.440> one<00:18:51.679> click 00:18:54.350 --> 00:18:54.360 align:start position:0% 00:18:54.360 --> 00:18:57.710 align:start position:0% installation<00:18:55.360> okay<00:18:55.919> um<00:18:56.120> we<00:18:56.240> have<00:18:56.720> uh<00:18:56.919> then<00:18:57.159> you 00:18:57.710 --> 00:18:57.720 align:start position:0% installation okay um we have uh then you 00:18:57.720 --> 00:19:01.070 align:start position:0% installation okay um we have uh then you the<00:18:57.880> first<00:18:58.120> step<00:18:58.360> is<00:18:58.440> to<00:18:58.960> select<00:18:59.360> the<00:19:00.080> network 00:19:01.070 --> 00:19:01.080 align:start position:0% the first step is to select the network 00:19:01.080 --> 00:19:03.909 align:start position:0% the first step is to select the network we<00:19:01.480> support<00:19:01.880> of<00:19:02.039> course<00:19:02.240> if<00:19:02.400> few<00:19:02.679> main<00:19:03.000> net<00:19:03.520> and 00:19:03.909 --> 00:19:03.919 align:start position:0% we support of course if few main net and 00:19:03.919 --> 00:19:05.909 align:start position:0% we support of course if few main net and both<00:19:04.240> test<00:19:04.559> net<00:19:04.799> theoo<00:19:05.280> and 00:19:05.909 --> 00:19:05.919 align:start position:0% both test net theoo and 00:19:05.919 --> 00:19:10.510 align:start position:0% both test net theoo and heski<00:19:06.919> and<00:19:07.480> um<00:19:07.640> we<00:19:07.799> also<00:19:08.120> support<00:19:08.559> kosis<00:19:09.520> mayet 00:19:10.510 --> 00:19:10.520 align:start position:0% heski and um we also support kosis mayet 00:19:10.520 --> 00:19:14.470 align:start position:0% heski and um we also support kosis mayet so<00:19:10.960> you<00:19:11.159> might<00:19:11.520> want<00:19:11.720> to<00:19:12.360> um<00:19:12.520> start<00:19:13.280> um<00:19:13.559> start 00:19:14.470 --> 00:19:14.480 align:start position:0% so you might want to um start um start 00:19:14.480 --> 00:19:17.149 align:start position:0% so you might want to um start um start start<00:19:15.000> staking<00:19:15.480> with<00:19:15.679> kosis<00:19:16.280> so<00:19:16.679> it's<00:19:17.000> it 00:19:17.149 --> 00:19:17.159 align:start position:0% start staking with kosis so it's it 00:19:17.159 --> 00:19:19.430 align:start position:0% start staking with kosis so it's it gives<00:19:17.320> you<00:19:17.480> also<00:19:17.720> a<00:19:17.840> good<00:19:18.000> feeling<00:19:18.440> and<00:19:19.039> works 00:19:19.430 --> 00:19:19.440 align:start position:0% gives you also a good feeling and works 00:19:19.440 --> 00:19:22.950 align:start position:0% gives you also a good feeling and works exactly<00:19:19.880> the<00:19:20.039> same<00:19:20.880> or<00:19:21.360> very<00:19:21.880> similar<00:19:22.480> so<00:19:22.799> we 00:19:22.950 --> 00:19:22.960 align:start position:0% exactly the same or very similar so we 00:19:22.960 --> 00:19:25.750 align:start position:0% exactly the same or very similar so we are<00:19:23.159> starting<00:19:23.559> with<00:19:23.679> a<00:19:23.840> hes<00:19:24.280> test<00:19:24.520> n 00:19:25.750 --> 00:19:25.760 align:start position:0% are starting with a hes test n 00:19:25.760 --> 00:19:28.390 align:start position:0% are starting with a hes test n today<00:19:26.760> and<00:19:26.960> now<00:19:27.080> you<00:19:27.320> have<00:19:27.880> um<00:19:28.080> different 00:19:28.390 --> 00:19:28.400 align:start position:0% today and now you have um different 00:19:28.400 --> 00:19:29.950 align:start position:0% today and now you have um different options 00:19:29.950 --> 00:19:29.960 align:start position:0% options 00:19:29.960 --> 00:19:32.190 align:start position:0% options um<00:19:30.280> you<00:19:30.520> just<00:19:30.799> can<00:19:31.200> set<00:19:31.400> it<00:19:31.559> up<00:19:31.720> for<00:19:31.919> as<00:19:32.039> a 00:19:32.190 --> 00:19:32.200 align:start position:0% um you just can set it up for as a 00:19:32.200 --> 00:19:34.669 align:start position:0% um you just can set it up for as a staking<00:19:32.600> note<00:19:33.360> um<00:19:33.600> that's<00:19:33.880> the<00:19:34.280> vanilla 00:19:34.669 --> 00:19:34.679 align:start position:0% staking note um that's the vanilla 00:19:34.679 --> 00:19:37.870 align:start position:0% staking note um that's the vanilla staking<00:19:35.120> setup<00:19:35.640> everybody<00:19:36.559> is<00:19:36.799> talking<00:19:37.600> if<00:19:37.760> we 00:19:37.870 --> 00:19:37.880 align:start position:0% staking setup everybody is talking if we 00:19:37.880 --> 00:19:40.430 align:start position:0% staking setup everybody is talking if we are<00:19:38.039> talking<00:19:38.400> about<00:19:39.039> staking<00:19:40.039> um<00:19:40.159> there's 00:19:40.430 --> 00:19:40.440 align:start position:0% are talking about staking um there's 00:19:40.440 --> 00:19:43.510 align:start position:0% are talking about staking um there's also<00:19:40.720> the<00:19:40.960> option<00:19:41.640> to<00:19:42.200> um<00:19:42.520> do<00:19:42.799> a<00:19:42.960> MF<00:19:43.200> boosted 00:19:43.510 --> 00:19:43.520 align:start position:0% also the option to um do a MF boosted 00:19:43.520 --> 00:19:46.270 align:start position:0% also the option to um do a MF boosted version<00:19:43.960> so<00:19:44.159> you<00:19:44.400> have<00:19:44.919> um<00:19:45.720> a<00:19:45.960> client 00:19:46.270 --> 00:19:46.280 align:start position:0% version so you have um a client 00:19:46.280 --> 00:19:48.590 align:start position:0% version so you have um a client installed<00:19:46.840> that<00:19:47.080> helps<00:19:47.400> you<00:19:47.679> to<00:19:48.000> connect<00:19:48.320> to 00:19:48.590 --> 00:19:48.600 align:start position:0% installed that helps you to connect to 00:19:48.600 --> 00:19:52.470 align:start position:0% installed that helps you to connect to relays<00:19:49.600> that<00:19:50.080> um<00:19:50.320> will<00:19:50.600> help<00:19:50.799> you<00:19:50.960> to<00:19:51.760> um<00:19:52.159> MEF 00:19:52.470 --> 00:19:52.480 align:start position:0% relays that um will help you to um MEF 00:19:52.480 --> 00:19:55.070 align:start position:0% relays that um will help you to um MEF boost<00:19:52.799> so<00:19:52.960> that's<00:19:53.679> maximum<00:19:54.400> extractable 00:19:55.070 --> 00:19:55.080 align:start position:0% boost so that's maximum extractable 00:19:55.080 --> 00:19:58.470 align:start position:0% boost so that's maximum extractable value<00:19:56.039> so<00:19:56.600> um<00:19:56.760> the<00:19:56.880> block<00:19:57.200> building<00:19:58.080> um<00:19:58.280> is 00:19:58.470 --> 00:19:58.480 align:start position:0% value so um the block building um is 00:19:58.480 --> 00:20:00.590 align:start position:0% value so um the block building um is done<00:19:58.960> relays<00:19:59.480> and<00:19:59.640> you<00:19:59.840> get<00:20:00.120> a<00:20:00.240> little<00:20:00.440> bit 00:20:00.590 --> 00:20:00.600 align:start position:0% done relays and you get a little bit 00:20:00.600 --> 00:20:03.270 align:start position:0% done relays and you get a little bit more<00:20:00.799> of<00:20:00.960> rewards<00:20:01.559> because<00:20:02.120> yeah<00:20:02.760> a<00:20:02.919> whole 00:20:03.270 --> 00:20:03.280 align:start position:0% more of rewards because yeah a whole 00:20:03.280 --> 00:20:06.110 align:start position:0% more of rewards because yeah a whole whole<00:20:03.520> entity<00:20:04.080> is<00:20:04.200> a<00:20:04.320> little<00:20:04.480> bit<00:20:04.640> faster<00:20:05.120> than 00:20:06.110 --> 00:20:06.120 align:start position:0% whole entity is a little bit faster than 00:20:06.120 --> 00:20:09.549 align:start position:0% whole entity is a little bit faster than probably<00:20:06.600> what<00:20:06.799> how<00:20:07.000> you<00:20:07.159> set<00:20:07.440> up<00:20:07.760> the<00:20:08.559> um<00:20:09.200> the 00:20:09.549 --> 00:20:09.559 align:start position:0% probably what how you set up the um the 00:20:09.559 --> 00:20:11.029 align:start position:0% probably what how you set up the um the the<00:20:09.720> the<00:20:09.880> block 00:20:11.029 --> 00:20:11.039 align:start position:0% the the block 00:20:11.039 --> 00:20:14.669 align:start position:0% the the block yourself<00:20:12.039> then<00:20:12.480> uh<00:20:12.600> we<00:20:12.799> already<00:20:13.720> um<00:20:14.039> talked 00:20:14.669 --> 00:20:14.679 align:start position:0% yourself then uh we already um talked 00:20:14.679 --> 00:20:16.830 align:start position:0% yourself then uh we already um talked and<00:20:15.000> if<00:20:15.120> you<00:20:15.600> afterwards<00:20:16.039> have<00:20:16.280> question<00:20:16.640> to 00:20:16.830 --> 00:20:16.840 align:start position:0% and if you afterwards have question to 00:20:16.840 --> 00:20:20.990 align:start position:0% and if you afterwards have question to it<00:20:17.400> um<00:20:17.559> we<00:20:17.679> can<00:20:17.880> show<00:20:18.159> you<00:20:18.760> um<00:20:19.240> um<00:20:19.400> a<00:20:19.600> DVT<00:20:20.039> setup 00:20:20.990 --> 00:20:21.000 align:start position:0% it um we can show you um um a DVT setup 00:20:21.000 --> 00:20:23.390 align:start position:0% it um we can show you um um a DVT setup so<00:20:21.440> that's<00:20:21.679> where<00:20:21.960> the<00:20:22.159> key<00:20:22.440> is<00:20:22.679> split<00:20:23.000> into 00:20:23.390 --> 00:20:23.400 align:start position:0% so that's where the key is split into 00:20:23.400 --> 00:20:26.990 align:start position:0% so that's where the key is split into four<00:20:23.760> parts<00:20:24.240> or<00:20:24.919> more<00:20:25.159> than<00:20:25.360> four<00:20:25.720> parts<00:20:26.679> and 00:20:26.990 --> 00:20:27.000 align:start position:0% four parts or more than four parts and 00:20:27.000 --> 00:20:31.110 align:start position:0% four parts or more than four parts and every<00:20:27.760> um<00:20:27.960> entity<00:20:28.919> um<00:20:29.159> is<00:20:29.640> uh<00:20:29.760> is<00:20:29.960> taking<00:20:30.440> and 00:20:31.110 --> 00:20:31.120 align:start position:0% every um entity um is uh is taking and 00:20:31.120 --> 00:20:34.750 align:start position:0% every um entity um is uh is taking and uh<00:20:31.280> thinking<00:20:31.760> and<00:20:31.960> agreeing<00:20:32.440> on<00:20:33.000> uh<00:20:33.280> on<00:20:34.280> on<00:20:34.600> on 00:20:34.750 --> 00:20:34.760 align:start position:0% uh thinking and agreeing on uh on on on 00:20:34.760 --> 00:20:37.789 align:start position:0% uh thinking and agreeing on uh on on on on<00:20:34.919> their<00:20:35.120> work<00:20:35.600> and<00:20:36.320> and<00:20:36.520> then<00:20:36.799> it's<00:20:37.400> um<00:20:37.640> and 00:20:37.789 --> 00:20:37.799 align:start position:0% on their work and and then it's um and 00:20:37.799 --> 00:20:42.029 align:start position:0% on their work and and then it's um and then<00:20:38.600> it<00:20:38.720> is<00:20:39.679> uh<00:20:39.799> deployed<00:20:40.280> to<00:20:40.400> the<00:20:40.640> network<00:20:41.640> so 00:20:42.029 --> 00:20:42.039 align:start position:0% then it is uh deployed to the network so 00:20:42.039 --> 00:20:45.070 align:start position:0% then it is uh deployed to the network so it's<00:20:42.400> it's<00:20:42.640> kind<00:20:42.760> of<00:20:43.000> safe<00:20:43.400> and<00:20:43.880> uh<00:20:44.000> not<00:20:44.240> every 00:20:45.070 --> 00:20:45.080 align:start position:0% it's it's kind of safe and uh not every 00:20:45.080 --> 00:20:48.830 align:start position:0% it's it's kind of safe and uh not every uh<00:20:45.280> part<00:20:45.520> of<00:20:46.159> then<00:20:46.720> not<00:20:46.960> every<00:20:47.200> Noe<00:20:47.559> in<00:20:47.840> this<00:20:48.360> um 00:20:48.830 --> 00:20:48.840 align:start position:0% uh part of then not every Noe in this um 00:20:48.840 --> 00:20:50.750 align:start position:0% uh part of then not every Noe in this um have<00:20:49.000> to<00:20:49.120> be<00:20:49.480> up<00:20:49.720> all<00:20:49.880> the<00:20:50.039> time<00:20:50.200> so<00:20:50.360> they<00:20:50.440> are<00:20:50.640> a 00:20:50.750 --> 00:20:50.760 align:start position:0% have to be up all the time so they are a 00:20:50.760 --> 00:20:54.669 align:start position:0% have to be up all the time so they are a little<00:20:50.960> bit<00:20:51.400> um<00:20:52.159> risk-free<00:20:53.159> and<00:20:53.919> and<00:20:54.039> not<00:20:54.200> so 00:20:54.669 --> 00:20:54.679 align:start position:0% little bit um risk-free and and not so 00:20:54.679 --> 00:20:57.230 align:start position:0% little bit um risk-free and and not so reliant<00:20:55.159> on<00:20:55.360> the<00:20:56.000> on<00:20:56.240> on<00:20:56.320> the<00:20:56.440> up 00:20:57.230 --> 00:20:57.240 align:start position:0% reliant on the on on the up 00:20:57.240 --> 00:21:01.070 align:start position:0% reliant on the on on the up time<00:20:58.240> yeah<00:20:58.440> we<00:20:58.679> we<00:20:59.000> we<00:20:59.480> we<00:20:59.880> we<00:21:00.080> have<00:21:00.440> an<00:21:00.720> own 00:21:01.070 --> 00:21:01.080 align:start position:0% time yeah we we we we we have an own 00:21:01.080 --> 00:21:04.830 align:start position:0% time yeah we we we we we have an own setup<00:21:01.520> for<00:21:02.120> steum<00:21:02.600> on<00:21:02.840> arm<00:21:03.360> as<00:21:03.520> we<00:21:03.679> said<00:21:04.240> um<00:21:04.400> for 00:21:04.830 --> 00:21:04.840 align:start position:0% setup for steum on arm as we said um for 00:21:04.840 --> 00:21:07.789 align:start position:0% setup for steum on arm as we said um for for<00:21:05.080> Raspberry<00:21:05.640> Pi<00:21:06.000> or<00:21:06.600> a<00:21:06.720> little<00:21:06.880> bit<00:21:07.080> better 00:21:07.789 --> 00:21:07.799 align:start position:0% for Raspberry Pi or a little bit better 00:21:07.799 --> 00:21:10.510 align:start position:0% for Raspberry Pi or a little bit better machines<00:21:08.799> um<00:21:09.120> it's<00:21:09.400> it's<00:21:09.520> a<00:21:09.679> little<00:21:09.880> bit<00:21:10.120> of<00:21:10.279> an 00:21:10.510 --> 00:21:10.520 align:start position:0% machines um it's it's a little bit of an 00:21:10.520 --> 00:21:13.669 align:start position:0% machines um it's it's a little bit of an experimental<00:21:11.200> stuff<00:21:11.600> but<00:21:12.080> um<00:21:12.320> try<00:21:12.600> it<00:21:13.240> if<00:21:13.400> you 00:21:13.669 --> 00:21:13.679 align:start position:0% experimental stuff but um try it if you 00:21:13.679 --> 00:21:17.430 align:start position:0% experimental stuff but um try it if you if<00:21:13.760> you<00:21:13.880> want<00:21:14.520> to<00:21:15.520> it<00:21:15.679> it<00:21:15.799> work<00:21:16.120> quite<00:21:16.440> well 00:21:17.430 --> 00:21:17.440 align:start position:0% if you want to it it work quite well 00:21:17.440 --> 00:21:20.909 align:start position:0% if you want to it it work quite well then<00:21:17.640> you<00:21:17.799> have<00:21:17.960> the<00:21:18.159> archive<00:21:18.640> node<00:21:19.520> um<00:21:19.799> so<00:21:20.520> um 00:21:20.909 --> 00:21:20.919 align:start position:0% then you have the archive node um so um 00:21:20.919 --> 00:21:24.430 align:start position:0% then you have the archive node um so um fully<00:21:21.240> set<00:21:21.799> up<00:21:22.799> and<00:21:23.039> then<00:21:23.320> we<00:21:23.640> support 00:21:24.430 --> 00:21:24.440 align:start position:0% fully set up and then we support 00:21:24.440 --> 00:21:29.230 align:start position:0% fully set up and then we support protocols<00:21:25.840> um<00:21:26.840> like<00:21:27.120> the<00:21:27.480> Lio<00:21:27.919> DVD<00:21:28.840> um 00:21:29.230 --> 00:21:29.240 align:start position:0% protocols um like the Lio DVD um 00:21:29.240 --> 00:21:32.110 align:start position:0% protocols um like the Lio DVD um protocol<00:21:30.240> where<00:21:30.520> you<00:21:30.760> can<00:21:31.039> do<00:21:31.279> not<00:21:31.600> operations 00:21:32.110 --> 00:21:32.120 align:start position:0% protocol where you can do not operations 00:21:32.120 --> 00:21:36.750 align:start position:0% protocol where you can do not operations for<00:21:32.360> Lio<00:21:33.279> um<00:21:33.799> um<00:21:34.000> emphasizing<00:21:34.919> the<00:21:35.840> um<00:21:36.080> the<00:21:36.240> DVT 00:21:36.750 --> 00:21:36.760 align:start position:0% for Lio um um emphasizing the um the DVT 00:21:36.760 --> 00:21:40.750 align:start position:0% for Lio um um emphasizing the um the DVT protocol<00:21:37.400> so<00:21:37.960> you<00:21:38.159> get<00:21:38.480> one<00:21:38.679> share<00:21:39.520> of<00:21:39.919> um<00:21:40.440> of<00:21:40.559> a 00:21:40.750 --> 00:21:40.760 align:start position:0% protocol so you get one share of um of a 00:21:40.760 --> 00:21:43.590 align:start position:0% protocol so you get one share of um of a key<00:21:41.600> and<00:21:41.760> do<00:21:42.039> not<00:21:42.360> operation<00:21:42.880> and<00:21:43.039> securing 00:21:43.590 --> 00:21:43.600 align:start position:0% key and do not operation and securing 00:21:43.600 --> 00:21:47.190 align:start position:0% key and do not operation and securing the<00:21:44.039> and<00:21:44.240> and<00:21:44.600> and<00:21:44.720> do<00:21:44.960> staking<00:21:45.400> for<00:21:45.919> for<00:21:46.200> Lio 00:21:47.190 --> 00:21:47.200 align:start position:0% the and and and do staking for for Lio 00:21:47.200 --> 00:21:50.190 align:start position:0% the and and and do staking for for Lio and<00:21:47.600> what's<00:21:48.279> quite<00:21:48.600> new<00:21:49.159> and<00:21:49.559> starting<00:21:50.039> an 00:21:50.190 --> 00:21:50.200 align:start position:0% and what's quite new and starting an 00:21:50.200 --> 00:21:52.269 align:start position:0% and what's quite new and starting an early<00:21:50.480> adoption<00:21:50.799> phase<00:21:51.080> on<00:21:51.240> Main<00:21:51.520> it<00:21:51.679> is<00:21:51.880> the 00:21:52.269 --> 00:21:52.279 align:start position:0% early adoption phase on Main it is the 00:21:52.279 --> 00:21:55.750 align:start position:0% early adoption phase on Main it is the CSM<00:21:52.960> the<00:21:53.120> community<00:21:53.520> staking<00:21:54.159> module<00:21:55.159> where 00:21:55.750 --> 00:21:55.760 align:start position:0% CSM the community staking module where 00:21:55.760 --> 00:21:59.149 align:start position:0% CSM the community staking module where uh<00:21:55.919> there<00:21:56.080> is<00:21:56.600> some<00:21:57.080> some<00:21:57.320> kind<00:21:57.559> of<00:21:58.000> bond<00:21:58.960> um 00:21:59.149 --> 00:21:59.159 align:start position:0% uh there is some some kind of bond um 00:21:59.159 --> 00:22:03.590 align:start position:0% uh there is some some kind of bond um you<00:21:59.720> um<00:22:00.360> yeah<00:22:01.200> you<00:22:01.720> you<00:22:01.919> just<00:22:02.159> have<00:22:02.279> to<00:22:02.919> um<00:22:03.120> add 00:22:03.590 --> 00:22:03.600 align:start position:0% you um yeah you you just have to um add 00:22:03.600 --> 00:22:07.630 align:start position:0% you um yeah you you just have to um add a<00:22:03.880> bond<00:22:04.880> and<00:22:05.520> uh<00:22:05.679> create<00:22:06.039> the<00:22:06.200> keys<00:22:06.919> and<00:22:07.480> uh 00:22:07.630 --> 00:22:07.640 align:start position:0% a bond and uh create the keys and uh 00:22:07.640 --> 00:22:10.870 align:start position:0% a bond and uh create the keys and uh lier<00:22:08.080> will<00:22:08.360> load<00:22:08.840> your<00:22:09.760> will<00:22:09.960> load<00:22:10.200> your<00:22:10.440> K 00:22:10.870 --> 00:22:10.880 align:start position:0% lier will load your will load your K 00:22:10.880 --> 00:22:14.029 align:start position:0% lier will load your will load your K with<00:22:11.080> 32<00:22:11.679> eeve<00:22:12.679> and<00:22:12.919> then 00:22:14.029 --> 00:22:14.039 align:start position:0% with 32 eeve and then 00:22:14.039 --> 00:22:17.430 align:start position:0% with 32 eeve and then you<00:22:15.039> and<00:22:15.640> uh<00:22:15.799> and<00:22:15.919> then<00:22:16.080> you'll<00:22:16.400> get<00:22:17.000> uh<00:22:17.159> parts 00:22:17.430 --> 00:22:17.440 align:start position:0% you and uh and then you'll get uh parts 00:22:17.440 --> 00:22:19.630 align:start position:0% you and uh and then you'll get uh parts of<00:22:17.679> the<00:22:18.279> um<00:22:18.440> of<00:22:18.559> the<00:22:18.679> Rewards<00:22:19.000> or<00:22:19.159> shares<00:22:19.480> of 00:22:19.630 --> 00:22:19.640 align:start position:0% of the um of the Rewards or shares of 00:22:19.640 --> 00:22:21.710 align:start position:0% of the um of the Rewards or shares of the<00:22:19.760> rewards<00:22:20.640> which<00:22:20.760> is 00:22:21.710 --> 00:22:21.720 align:start position:0% the rewards which is 00:22:21.720 --> 00:22:25.630 align:start position:0% the rewards which is quite<00:22:22.720> quite<00:22:22.960> good<00:22:23.240> yeah<00:22:23.400> so<00:22:24.000> I<00:22:24.080> will<00:22:24.279> take<00:22:24.640> now 00:22:25.630 --> 00:22:25.640 align:start position:0% quite quite good yeah so I will take now 00:22:25.640 --> 00:22:27.310 align:start position:0% quite quite good yeah so I will take now the<00:22:26.000> vanilla 00:22:27.310 --> 00:22:27.320 align:start position:0% the vanilla 00:22:27.320 --> 00:22:30.590 align:start position:0% the vanilla staking<00:22:28.320> um<00:22:28.559> um<00:22:28.880> it's<00:22:29.159> always<00:22:29.559> possible<00:22:30.000> to 00:22:30.590 --> 00:22:30.600 align:start position:0% staking um um it's always possible to 00:22:30.600 --> 00:22:34.510 align:start position:0% staking um um it's always possible to add<00:22:31.400> um<00:22:32.320> yeah<00:22:32.640> stuff<00:22:32.840> in<00:22:33.000> the<00:22:33.159> expert<00:22:33.559> mode<00:22:34.000> so 00:22:34.510 --> 00:22:34.520 align:start position:0% add um yeah stuff in the expert mode so 00:22:34.520 --> 00:22:36.590 align:start position:0% add um yeah stuff in the expert mode so we<00:22:34.640> can<00:22:34.799> show<00:22:35.039> you<00:22:35.200> afterwards<00:22:35.760> if<00:22:35.880> you<00:22:36.279> if<00:22:36.480> you 00:22:36.590 --> 00:22:36.600 align:start position:0% we can show you afterwards if you if you 00:22:36.600 --> 00:22:39.269 align:start position:0% we can show you afterwards if you if you want<00:22:37.159> uh<00:22:37.240> to<00:22:37.400> go<00:22:37.559> from<00:22:37.679> staking<00:22:38.159> to<00:22:38.360> M<00:22:38.840> boosted 00:22:39.269 --> 00:22:39.279 align:start position:0% want uh to go from staking to M boosted 00:22:39.279 --> 00:22:43.310 align:start position:0% want uh to go from staking to M boosted for<00:22:39.799> example<00:22:40.799> um<00:22:41.200> we<00:22:41.480> I<00:22:41.559> will<00:22:42.000> show<00:22:42.159> you<00:22:42.279> in 00:22:43.310 --> 00:22:43.320 align:start position:0% for example um we I will show you in 00:22:43.320 --> 00:22:46.310 align:start position:0% for example um we I will show you in afterwards<00:22:44.320> so<00:22:44.840> and<00:22:45.400> uh<00:22:45.559> after<00:22:45.760> you<00:22:45.919> made<00:22:46.120> your 00:22:46.310 --> 00:22:46.320 align:start position:0% afterwards so and uh after you made your 00:22:46.320 --> 00:22:50.909 align:start position:0% afterwards so and uh after you made your decisions<00:22:46.840> you're<00:22:47.360> almost<00:22:47.960> set 00:22:50.909 --> 00:22:50.919 align:start position:0% 00:22:50.919 --> 00:22:54.549 align:start position:0% completely<00:22:51.919> um<00:22:52.320> what<00:22:52.640> you<00:22:53.000> now<00:22:53.400> as<00:22:53.600> we<00:22:54.240> before 00:22:54.549 --> 00:22:54.559 align:start position:0% completely um what you now as we before 00:22:54.559 --> 00:22:57.549 align:start position:0% completely um what you now as we before said<00:22:55.000> um<00:22:55.120> we<00:22:55.200> are<00:22:55.400> client<00:22:55.720> aers<00:22:56.240> so<00:22:57.039> their<00:22:57.400> the 00:22:57.549 --> 00:22:57.559 align:start position:0% said um we are client aers so their the 00:22:57.559 --> 00:23:01.310 align:start position:0% said um we are client aers so their the setup<00:22:57.919> is<00:22:58.039> chosen<00:22:58.720> randomly<00:22:59.720> um<00:23:00.080> I<00:23:00.159> mean<00:23:00.640> yeah 00:23:01.310 --> 00:23:01.320 align:start position:0% setup is chosen randomly um I mean yeah 00:23:01.320 --> 00:23:04.350 align:start position:0% setup is chosen randomly um I mean yeah it<00:23:01.440> chose<00:23:01.760> randomly<00:23:02.440> G<00:23:03.279> which<00:23:03.919> which<00:23:04.240> which 00:23:04.350 --> 00:23:04.360 align:start position:0% it chose randomly G which which which 00:23:04.360 --> 00:23:06.590 align:start position:0% it chose randomly G which which which you<00:23:04.480> shouldn't<00:23:04.919> use<00:23:05.240> because<00:23:05.640> I<00:23:05.799> mean<00:23:06.480> it's 00:23:06.590 --> 00:23:06.600 align:start position:0% you shouldn't use because I mean it's 00:23:06.600 --> 00:23:09.590 align:start position:0% you shouldn't use because I mean it's running<00:23:06.960> good<00:23:07.240> but<00:23:07.440> it's<00:23:08.039> um<00:23:08.919> at<00:23:09.039> the<00:23:09.200> mainly 00:23:09.590 --> 00:23:09.600 align:start position:0% running good but it's um at the mainly 00:23:09.600 --> 00:23:13.149 align:start position:0% running good but it's um at the mainly adopted<00:23:10.440> um<00:23:10.880> client<00:23:11.880> and<00:23:12.520> um<00:23:12.720> yeah<00:23:12.880> for 00:23:13.149 --> 00:23:13.159 align:start position:0% adopted um client and um yeah for 00:23:13.159 --> 00:23:15.789 align:start position:0% adopted um client and um yeah for decentralized<00:23:14.039> reasons<00:23:14.919> um<00:23:15.039> we<00:23:15.159> should<00:23:15.520> take 00:23:15.789 --> 00:23:15.799 align:start position:0% decentralized reasons um we should take 00:23:15.799 --> 00:23:17.870 align:start position:0% decentralized reasons um we should take something<00:23:16.159> else<00:23:16.400> so<00:23:16.559> you<00:23:16.720> just<00:23:16.919> click<00:23:17.159> on 00:23:17.870 --> 00:23:17.880 align:start position:0% something else so you just click on 00:23:17.880 --> 00:23:21.390 align:start position:0% something else so you just click on it<00:23:18.880> and<00:23:19.039> choose<00:23:19.360> something<00:23:19.679> else<00:23:19.960> for<00:23:20.159> example 00:23:21.390 --> 00:23:21.400 align:start position:0% it and choose something else for example 00:23:21.400 --> 00:23:24.029 align:start position:0% it and choose something else for example basil<00:23:22.400> um<00:23:22.679> and<00:23:22.799> you<00:23:22.919> can<00:23:23.120> do<00:23:23.520> the<00:23:23.679> same<00:23:23.880> thing 00:23:24.029 --> 00:23:24.039 align:start position:0% basil um and you can do the same thing 00:23:24.039 --> 00:23:27.149 align:start position:0% basil um and you can do the same thing for<00:23:24.200> the<00:23:24.360> consensus<00:23:24.880> clim<00:23:25.320> so<00:23:26.080> yeah<00:23:26.440> instead 00:23:27.149 --> 00:23:27.159 align:start position:0% for the consensus clim so yeah instead 00:23:27.159 --> 00:23:30.710 align:start position:0% for the consensus clim so yeah instead of<00:23:27.440> prism<00:23:28.039> I<00:23:28.159> can 00:23:30.710 --> 00:23:30.720 align:start position:0% 00:23:30.720 --> 00:23:34.230 align:start position:0% here's<00:23:31.600> load 00:23:34.230 --> 00:23:34.240 align:start position:0% 00:23:34.240 --> 00:23:37.269 align:start position:0% star<00:23:35.240> and<00:23:35.679> the<00:23:35.880> validator<00:23:36.360> Cent<00:23:36.679> is<00:23:36.840> set<00:23:37.120> as 00:23:37.269 --> 00:23:37.279 align:start position:0% star and the validator Cent is set as 00:23:37.279 --> 00:23:40.870 align:start position:0% star and the validator Cent is set as well<00:23:37.799> normally<00:23:38.400> you<00:23:38.960> um<00:23:39.120> you<00:23:39.279> set<00:23:39.559> up<00:23:39.799> your<00:23:40.720> uh 00:23:40.870 --> 00:23:40.880 align:start position:0% well normally you um you set up your uh 00:23:40.880 --> 00:23:43.710 align:start position:0% well normally you um you set up your uh ethereum<00:23:41.520> staking<00:23:41.919> note<00:23:42.520> um<00:23:42.760> with<00:23:43.159> consensus 00:23:43.710 --> 00:23:43.720 align:start position:0% ethereum staking note um with consensus 00:23:43.720 --> 00:23:46.310 align:start position:0% ethereum staking note um with consensus and<00:23:43.919> validator<00:23:44.679> client<00:23:45.279> um<00:23:45.440> from<00:23:45.760> the<00:23:46.120> the 00:23:46.310 --> 00:23:46.320 align:start position:0% and validator client um from the the 00:23:46.320 --> 00:23:47.950 align:start position:0% and validator client um from the the same<00:23:47.000> um 00:23:47.950 --> 00:23:47.960 align:start position:0% same um 00:23:47.960 --> 00:23:50.310 align:start position:0% same um developer<00:23:48.960> yeah<00:23:49.080> and<00:23:49.200> there<00:23:49.320> are<00:23:49.520> other<00:23:50.120> um 00:23:50.310 --> 00:23:50.320 align:start position:0% developer yeah and there are other um 00:23:50.320 --> 00:23:53.909 align:start position:0% developer yeah and there are other um Services<00:23:51.320> um<00:23:51.520> installed<00:23:52.080> as<00:23:52.240> well<00:23:53.000> that<00:23:53.559> um 00:23:53.909 --> 00:23:53.919 align:start position:0% Services um installed as well that um 00:23:53.919 --> 00:23:56.710 align:start position:0% Services um installed as well that um yeah<00:23:54.159> visualize<00:23:55.039> what<00:23:55.159> is<00:23:55.360> happening<00:23:55.880> in<00:23:56.039> your 00:23:56.710 --> 00:23:56.720 align:start position:0% yeah visualize what is happening in your 00:23:56.720 --> 00:24:00.549 align:start position:0% yeah visualize what is happening in your note<00:23:57.720> so<00:23:58.279> um<00:23:58.600> and<00:23:59.600> after 00:24:00.549 --> 00:24:00.559 align:start position:0% note so um and after 00:24:00.559 --> 00:24:04.830 align:start position:0% note so um and after you<00:24:01.559> you<00:24:02.240> you<00:24:02.400> click<00:24:02.919> next<00:24:03.919> um<00:24:04.120> you<00:24:04.360> only<00:24:04.679> have 00:24:04.830 --> 00:24:04.840 align:start position:0% you you you click next um you only have 00:24:04.840 --> 00:24:10.470 align:start position:0% you you you click next um you only have to<00:24:05.640> um<00:24:06.640> uh<00:24:07.640> choose<00:24:08.000> a<00:24:08.520> a<00:24:08.919> checkpoint<00:24:09.480> sync 00:24:10.470 --> 00:24:10.480 align:start position:0% to um uh choose a a checkpoint sync 00:24:10.480 --> 00:24:13.549 align:start position:0% to um uh choose a a checkpoint sync which<00:24:10.679> is<00:24:11.200> U<00:24:11.320> we<00:24:11.480> have<00:24:11.960> pre-selected<00:24:12.960> um 00:24:13.549 --> 00:24:13.559 align:start position:0% which is U we have pre-selected um 00:24:13.559 --> 00:24:17.070 align:start position:0% which is U we have pre-selected um sources<00:24:14.559> that<00:24:14.720> we<00:24:14.880> know<00:24:15.320> work<00:24:15.919> quite<00:24:16.240> well<00:24:16.960> but 00:24:17.070 --> 00:24:17.080 align:start position:0% sources that we know work quite well but 00:24:17.080 --> 00:24:21.269 align:start position:0% sources that we know work quite well but you're<00:24:17.400> also<00:24:17.799> able<00:24:18.400> to<00:24:19.200> um<00:24:19.960> yeah<00:24:20.480> um<00:24:20.640> sync<00:24:21.120> with 00:24:21.269 --> 00:24:21.279 align:start position:0% you're also able to um yeah um sync with 00:24:21.279 --> 00:24:24.430 align:start position:0% you're also able to um yeah um sync with your<00:24:21.559> own<00:24:22.240> checkpoint<00:24:23.240> if<00:24:23.360> you<00:24:23.520> want<00:24:23.720> to<00:24:24.159> so 00:24:24.430 --> 00:24:24.440 align:start position:0% your own checkpoint if you want to so 00:24:24.440 --> 00:24:30.350 align:start position:0% your own checkpoint if you want to so you<00:24:24.600> can<00:24:24.919> use<00:24:25.120> a<00:24:25.320> custom<00:24:25.679> source 00:24:30.350 --> 00:24:30.360 align:start position:0% 00:24:30.360 --> 00:24:32.750 align:start position:0% and<00:24:30.840> yeah<00:24:31.039> that's<00:24:31.320> only<00:24:31.600> an<00:24:31.840> overview<00:24:32.559> where 00:24:32.750 --> 00:24:32.760 align:start position:0% and yeah that's only an overview where 00:24:32.760 --> 00:24:37.870 align:start position:0% and yeah that's only an overview where the<00:24:32.880> things<00:24:33.200> are<00:24:34.200> stored<00:24:35.159> or<00:24:36.000> installed<00:24:36.559> and 00:24:37.870 --> 00:24:37.880 align:start position:0% the things are stored or installed and 00:24:37.880 --> 00:24:42.350 align:start position:0% the things are stored or installed and then<00:24:38.880> you<00:24:39.080> can<00:24:39.320> press 00:24:42.350 --> 00:24:42.360 align:start position:0% 00:24:42.360 --> 00:24:45.190 align:start position:0% next<00:24:43.360> okay<00:24:43.720> in<00:24:43.880> the<00:24:44.000> meanwhile<00:24:44.919> while 00:24:45.190 --> 00:24:45.200 align:start position:0% next okay in the meanwhile while 00:24:45.200 --> 00:24:47.830 align:start position:0% next okay in the meanwhile while everything<00:24:45.880> is<00:24:46.039> setting<00:24:46.480> up<00:24:47.000> what<00:24:47.200> would<00:24:47.360> you 00:24:47.830 --> 00:24:47.840 align:start position:0% everything is setting up what would you 00:24:47.840 --> 00:24:50.830 align:start position:0% everything is setting up what would you what<00:24:47.960> you<00:24:48.039> will<00:24:48.240> see<00:24:48.679> in<00:24:48.840> a<00:24:49.159> a<00:24:49.320> moment<00:24:50.240> I<00:24:50.360> will 00:24:50.830 --> 00:24:50.840 align:start position:0% what you will see in a a moment I will 00:24:50.840 --> 00:24:55.669 align:start position:0% what you will see in a a moment I will shortly<00:24:51.840> um<00:24:52.000> tell<00:24:52.240> you<00:24:52.399> a<00:24:52.480> little<00:24:52.679> bit<00:24:52.840> about 00:24:55.669 --> 00:24:55.679 align:start position:0% 00:24:55.679 --> 00:24:59.350 align:start position:0% launchpads<00:24:56.679> so<00:24:56.960> if<00:24:57.080> you<00:24:57.279> are<00:24:58.480> if<00:24:58.640> you<00:24:58.840> have 00:24:59.350 --> 00:24:59.360 align:start position:0% launchpads so if you are if you have 00:24:59.360 --> 00:25:02.190 align:start position:0% launchpads so if you are if you have created<00:24:59.760> your<00:24:59.919> validator<00:25:00.480> key<00:25:01.080> and<00:25:01.399> if<00:25:01.559> you 00:25:02.190 --> 00:25:02.200 align:start position:0% created your validator key and if you 00:25:02.200 --> 00:25:05.710 align:start position:0% created your validator key and if you have<00:25:02.440> your<00:25:02.720> setup<00:25:03.279> ready<00:25:04.279> then<00:25:04.480> you<00:25:04.880> want<00:25:05.200> to 00:25:05.710 --> 00:25:05.720 align:start position:0% have your setup ready then you want to 00:25:05.720 --> 00:25:08.590 align:start position:0% have your setup ready then you want to load<00:25:06.039> up<00:25:06.200> your<00:25:06.399> validator<00:25:07.159> uh<00:25:07.320> key<00:25:07.559> with<00:25:07.720> 32<00:25:08.279> e 00:25:08.590 --> 00:25:08.600 align:start position:0% load up your validator uh key with 32 e 00:25:08.600 --> 00:25:12.149 align:start position:0% load up your validator uh key with 32 e and<00:25:09.120> um<00:25:09.279> for<00:25:09.559> beginners<00:25:10.240> we<00:25:10.399> would<00:25:11.080> um<00:25:12.039> we 00:25:12.149 --> 00:25:12.159 align:start position:0% and um for beginners we would um we 00:25:12.159 --> 00:25:15.590 align:start position:0% and um for beginners we would um we would<00:25:12.679> uh<00:25:13.399> recommend<00:25:13.919> you<00:25:14.120> the<00:25:14.960> to<00:25:15.159> use<00:25:15.399> it 00:25:15.590 --> 00:25:15.600 align:start position:0% would uh recommend you the to use it 00:25:15.600 --> 00:25:17.350 align:start position:0% would uh recommend you the to use it from<00:25:15.840> the<00:25:16.120> the<00:25:16.240> E<00:25:16.559> the<00:25:16.640> launch<00:25:16.919> pad<00:25:17.120> from<00:25:17.240> the 00:25:17.350 --> 00:25:17.360 align:start position:0% from the the E the launch pad from the 00:25:17.360 --> 00:25:18.870 align:start position:0% from the the E the launch pad from the eum 00:25:18.870 --> 00:25:18.880 align:start position:0% eum 00:25:18.880 --> 00:25:22.029 align:start position:0% eum foundation<00:25:20.159> and<00:25:21.159> um<00:25:21.320> there's<00:25:21.559> a<00:25:21.760> really 00:25:22.029 --> 00:25:22.039 align:start position:0% foundation and um there's a really 00:25:22.039 --> 00:25:25.070 align:start position:0% foundation and um there's a really really<00:25:22.399> easy<00:25:22.880> setup<00:25:23.600> you<00:25:23.760> have<00:25:23.919> to<00:25:24.080> choose<00:25:24.799> um 00:25:25.070 --> 00:25:25.080 align:start position:0% really easy setup you have to choose um 00:25:25.080 --> 00:25:27.310 align:start position:0% really easy setup you have to choose um which<00:25:25.520> which<00:25:25.720> net 00:25:27.310 --> 00:25:27.320 align:start position:0% which which net 00:25:27.320 --> 00:25:31.909 align:start position:0% which which net in<00:25:28.320> in<00:25:28.399> the<00:25:28.559> first<00:25:29.279> place<00:25:30.279> so<00:25:31.080> I'm<00:25:31.279> I'm<00:25:31.399> using 00:25:31.909 --> 00:25:31.919 align:start position:0% in in the first place so I'm I'm using 00:25:31.919 --> 00:25:34.590 align:start position:0% in in the first place so I'm I'm using heski<00:25:32.919> and<00:25:33.159> then<00:25:33.360> it<00:25:33.480> will<00:25:33.760> really<00:25:34.120> walk<00:25:34.440> you 00:25:34.590 --> 00:25:34.600 align:start position:0% heski and then it will really walk you 00:25:34.600 --> 00:25:38.549 align:start position:0% heski and then it will really walk you to<00:25:34.919> everything<00:25:35.480> it<00:25:35.640> makes<00:25:35.880> a<00:25:36.039> lot<00:25:36.360> of<00:25:37.279> um<00:25:38.279> it 00:25:38.549 --> 00:25:38.559 align:start position:0% to everything it makes a lot of um it 00:25:38.559 --> 00:25:41.269 align:start position:0% to everything it makes a lot of um it explains<00:25:39.159> everything<00:25:39.760> again<00:25:40.640> um<00:25:40.799> it<00:25:40.919> makes<00:25:41.159> a 00:25:41.269 --> 00:25:41.279 align:start position:0% explains everything again um it makes a 00:25:41.279 --> 00:25:43.389 align:start position:0% explains everything again um it makes a lot<00:25:41.480> of<00:25:41.640> checks<00:25:42.159> if<00:25:42.360> everything<00:25:42.720> is<00:25:42.880> set<00:25:43.120> up 00:25:43.389 --> 00:25:43.399 align:start position:0% lot of checks if everything is set up 00:25:43.399 --> 00:25:46.149 align:start position:0% lot of checks if everything is set up correctly<00:25:44.080> it<00:25:44.279> warns<00:25:44.679> you<00:25:44.960> I<00:25:45.039> think<00:25:45.240> it's<00:25:45.880> very 00:25:46.149 --> 00:25:46.159 align:start position:0% correctly it warns you I think it's very 00:25:46.159 --> 00:25:50.029 align:start position:0% correctly it warns you I think it's very nice<00:25:46.440> way<00:25:46.760> just<00:25:46.960> to<00:25:47.960> uh<00:25:48.039> to<00:25:48.200> memorize<00:25:48.960> every<00:25:49.880> uh 00:25:50.029 --> 00:25:50.039 align:start position:0% nice way just to uh to memorize every uh 00:25:50.039 --> 00:25:53.149 align:start position:0% nice way just to uh to memorize every uh everything<00:25:50.520> again<00:25:51.279> and<00:25:52.000> uh<00:25:52.240> and<00:25:52.720> and<00:25:52.880> deep 00:25:53.149 --> 00:25:53.159 align:start position:0% everything again and uh and and deep 00:25:53.159 --> 00:25:55.389 align:start position:0% everything again and uh and and deep dive<00:25:53.520> into<00:25:53.880> staking 00:25:55.389 --> 00:25:55.399 align:start position:0% dive into staking 00:25:55.399 --> 00:25:58.950 align:start position:0% dive into staking again<00:25:56.399> but<00:25:56.640> I<00:25:57.520> you<00:25:57.679> might<00:25:57.880> as<00:25:58.000> well<00:25:58.640> click 00:25:58.950 --> 00:25:58.960 align:start position:0% again but I you might as well click 00:25:58.960 --> 00:26:01.669 align:start position:0% again but I you might as well click through<00:25:59.279> it<00:25:59.960> but<00:26:00.120> it's<00:26:00.320> really<00:26:01.039> yeah<00:26:01.320> I<00:26:01.399> would 00:26:01.669 --> 00:26:01.679 align:start position:0% through it but it's really yeah I would 00:26:01.679 --> 00:26:04.029 align:start position:0% through it but it's really yeah I would recommend<00:26:02.080> you<00:26:02.159> to<00:26:02.320> read<00:26:02.520> a<00:26:02.640> little<00:26:02.799> bit<00:26:03.000> into 00:26:04.029 --> 00:26:04.039 align:start position:0% recommend you to read a little bit into 00:26:04.039 --> 00:26:06.789 align:start position:0% recommend you to read a little bit into it<00:26:05.039> um<00:26:05.200> it<00:26:05.360> also<00:26:05.559> tells<00:26:05.799> you<00:26:06.000> about<00:26:06.200> the<00:26:06.399> risks 00:26:06.789 --> 00:26:06.799 align:start position:0% it um it also tells you about the risks 00:26:06.799 --> 00:26:09.830 align:start position:0% it um it also tells you about the risks the<00:26:06.960> early<00:26:07.279> adopter<00:26:07.760> risks<00:26:08.480> Etc<00:26:09.480> there's 00:26:09.830 --> 00:26:09.840 align:start position:0% the early adopter risks Etc there's 00:26:09.840 --> 00:26:12.149 align:start position:0% the early adopter risks Etc there's checklist<00:26:10.320> involved<00:26:10.720> so<00:26:11.640> there's<00:26:11.919> really 00:26:12.149 --> 00:26:12.159 align:start position:0% checklist involved so there's really 00:26:12.159 --> 00:26:15.669 align:start position:0% checklist involved so there's really some<00:26:12.399> cool<00:26:12.919> stuff<00:26:13.240> and<00:26:13.399> then<00:26:13.760> in<00:26:13.880> the<00:26:14.000> end<00:26:14.279> you 00:26:15.669 --> 00:26:15.679 align:start position:0% some cool stuff and then in the end you 00:26:15.679 --> 00:26:18.950 align:start position:0% some cool stuff and then in the end you confirm<00:26:16.679> um<00:26:17.360> yeah<00:26:17.720> and<00:26:17.880> then<00:26:18.039> you<00:26:18.200> can<00:26:18.600> choose 00:26:18.950 --> 00:26:18.960 align:start position:0% confirm um yeah and then you can choose 00:26:18.960 --> 00:26:21.230 align:start position:0% confirm um yeah and then you can choose your<00:26:19.200> even<00:26:19.440> your<00:26:19.679> execution<00:26:20.240> client<00:26:20.880> we<00:26:21.080> set 00:26:21.230 --> 00:26:21.240 align:start position:0% your even your execution client we set 00:26:21.240 --> 00:26:25.950 align:start position:0% your even your execution client we set up 00:26:25.950 --> 00:26:25.960 align:start position:0% 00:26:25.960 --> 00:26:29.269 align:start position:0% basil<00:26:26.960> and 00:26:29.269 --> 00:26:29.279 align:start position:0% basil and 00:26:29.279 --> 00:26:32.510 align:start position:0% basil and get<00:26:29.440> the<00:26:29.640> con 00:26:32.510 --> 00:26:32.520 align:start position:0% 00:26:32.520 --> 00:26:35.070 align:start position:0% documentation<00:26:33.520> then<00:26:33.840> we<00:26:34.039> took<00:26:34.520> consensus 00:26:35.070 --> 00:26:35.080 align:start position:0% documentation then we took consensus 00:26:35.080 --> 00:26:38.430 align:start position:0% documentation then we took consensus client<00:26:35.399> load 00:26:38.430 --> 00:26:38.440 align:start position:0% 00:26:38.440 --> 00:26:40.950 align:start position:0% store<00:26:39.440> yeah<00:26:39.720> right<00:26:39.960> it's<00:26:40.159> it's<00:26:40.399> kind<00:26:40.559> of<00:26:40.840> it's 00:26:40.950 --> 00:26:40.960 align:start position:0% store yeah right it's it's kind of it's 00:26:40.960 --> 00:26:44.230 align:start position:0% store yeah right it's it's kind of it's a<00:26:41.159> kind<00:26:41.279> of<00:26:41.799> optional<00:26:42.799> um 00:26:44.230 --> 00:26:44.240 align:start position:0% a kind of optional um 00:26:44.240 --> 00:26:46.990 align:start position:0% a kind of optional um um<00:26:45.240> what<00:26:45.399> you<00:26:45.520> chose<00:26:45.880> there<00:26:46.159> then<00:26:46.559> the<00:26:46.720> number 00:26:46.990 --> 00:26:47.000 align:start position:0% um what you chose there then the number 00:26:47.000 --> 00:26:48.230 align:start position:0% um what you chose there then the number of 00:26:48.230 --> 00:26:48.240 align:start position:0% of 00:26:48.240 --> 00:26:51.389 align:start position:0% of validators<00:26:49.240> then<00:26:49.559> you<00:26:49.760> set<00:26:50.000> the<00:26:50.200> withdrawal 00:26:51.389 --> 00:26:51.399 align:start position:0% validators then you set the withdrawal 00:26:51.399 --> 00:26:54.029 align:start position:0% validators then you set the withdrawal address<00:26:52.399> we<00:26:52.600> already<00:26:52.919> talked<00:26:53.320> to<00:26:53.679> should<00:26:53.880> be 00:26:54.029 --> 00:26:54.039 align:start position:0% address we already talked to should be 00:26:54.039 --> 00:27:03.909 align:start position:0% address we already talked to should be the<00:26:54.240> same<00:26:54.640> as<00:26:55.640> in<00:26:55.840> your<00:26:56.480> key<00:26:56.799> files 00:27:03.909 --> 00:27:03.919 align:start position:0% 00:27:03.919 --> 00:27:08.750 align:start position:0% yeah<00:27:04.279> what's<00:27:04.480> your<00:27:04.679> curent<00:27:05.200> operating 00:27:08.750 --> 00:27:08.760 align:start position:0% 00:27:08.760 --> 00:27:12.950 align:start position:0% system<00:27:09.760> yeah<00:27:10.360> then<00:27:11.240> download<00:27:11.799> the<00:27:12.039> keyan<00:27:12.600> GUI 00:27:12.950 --> 00:27:12.960 align:start position:0% system yeah then download the keyan GUI 00:27:12.960 --> 00:27:15.389 align:start position:0% system yeah then download the keyan GUI app<00:27:13.480> we<00:27:13.679> already<00:27:13.960> used<00:27:14.840> so<00:27:15.000> it's<00:27:15.159> also 00:27:15.389 --> 00:27:15.399 align:start position:0% app we already used so it's also 00:27:15.399 --> 00:27:17.549 align:start position:0% app we already used so it's also recommended<00:27:15.880> from<00:27:16.039> the 00:27:17.549 --> 00:27:17.559 align:start position:0% recommended from the 00:27:17.559 --> 00:27:21.430 align:start position:0% recommended from the etherum<00:27:18.559> no<00:27:18.720> come<00:27:18.840> on<00:27:19.720> I<00:27:19.960> D<00:27:20.240> can<00:27:20.440> find<00:27:20.640> it<00:27:20.840> also 00:27:21.430 --> 00:27:21.440 align:start position:0% etherum no come on I D can find it also 00:27:21.440 --> 00:27:24.029 align:start position:0% etherum no come on I D can find it also so<00:27:21.640> that's<00:27:22.039> probably<00:27:22.720> something 00:27:24.029 --> 00:27:24.039 align:start position:0% so that's probably something 00:27:24.039 --> 00:27:26.310 align:start position:0% so that's probably something good<00:27:25.039> yeah 00:27:26.310 --> 00:27:26.320 align:start position:0% good yeah 00:27:26.320 --> 00:27:30.430 align:start position:0% good yeah and<00:27:27.320> I'm<00:27:27.520> keeping<00:27:27.799> my<00:27:27.960> key 00:27:30.430 --> 00:27:30.440 align:start position:0% 00:27:30.440 --> 00:27:32.630 align:start position:0% save<00:27:31.440> and<00:27:31.679> now<00:27:31.919> you 00:27:32.630 --> 00:27:32.640 align:start position:0% save and now you 00:27:32.640 --> 00:27:35.510 align:start position:0% save and now you can 00:27:35.510 --> 00:27:35.520 align:start position:0% can 00:27:35.520 --> 00:27:42.909 align:start position:0% can um<00:27:36.520> get<00:27:36.720> your 00:27:42.909 --> 00:27:42.919 align:start position:0% 00:27:42.919 --> 00:27:44.590 align:start position:0% deposit 00:27:44.590 --> 00:27:44.600 align:start position:0% deposit 00:27:44.600 --> 00:27:49.470 align:start position:0% deposit file<00:27:45.840> and<00:27:46.840> keychan<00:27:47.480> is<00:27:47.919> very<00:27:48.679> user<00:27:49.080> friendly 00:27:49.470 --> 00:27:49.480 align:start position:0% file and keychan is very user friendly 00:27:49.480 --> 00:27:51.909 align:start position:0% file and keychan is very user friendly so<00:27:49.679> it<00:27:50.200> already<00:27:50.600> tells<00:27:50.960> you<00:27:51.279> which<00:27:51.519> file<00:27:51.760> to 00:27:51.909 --> 00:27:51.919 align:start position:0% so it already tells you which file to 00:27:51.919 --> 00:27:56.149 align:start position:0% so it already tells you which file to use<00:27:52.240> so<00:27:52.399> you<00:27:52.559> use<00:27:52.840> the<00:27:53.320> deposit<00:27:54.679> file<00:27:55.679> open<00:27:55.960> it 00:27:56.149 --> 00:27:56.159 align:start position:0% use so you use the deposit file open it 00:27:56.159 --> 00:27:58.669 align:start position:0% use so you use the deposit file open it up<00:27:56.600> every<00:27:57.080> information<00:27:57.600> is<00:27:57.760> started 00:27:58.669 --> 00:27:58.679 align:start position:0% up every information is started 00:27:58.679 --> 00:28:00.470 align:start position:0% up every information is started correctly<00:27:59.679> and 00:28:00.470 --> 00:28:00.480 align:start position:0% correctly and 00:28:00.480 --> 00:28:02.870 align:start position:0% correctly and continue<00:28:01.480> and<00:28:01.760> everything<00:28:02.159> you<00:28:02.320> then<00:28:02.600> have<00:28:02.720> to 00:28:02.870 --> 00:28:02.880 align:start position:0% continue and everything you then have to 00:28:02.880 --> 00:28:06.470 align:start position:0% continue and everything you then have to do<00:28:03.120> is<00:28:03.480> yeah<00:28:03.679> connect<00:28:04.120> your<00:28:04.720> your<00:28:05.320> wallet<00:28:06.320> of 00:28:06.470 --> 00:28:06.480 align:start position:0% do is yeah connect your your wallet of 00:28:06.480 --> 00:28:09.389 align:start position:0% do is yeah connect your your wallet of course<00:28:07.120> um<00:28:08.000> probably<00:28:08.480> if<00:28:08.600> you<00:28:09.200> if<00:28:09.279> you're 00:28:09.389 --> 00:28:09.399 align:start position:0% course um probably if you if you're 00:28:09.399 --> 00:28:11.230 align:start position:0% course um probably if you if you're doing<00:28:09.640> the<00:28:09.799> real<00:28:10.039> thing<00:28:10.320> you<00:28:10.440> should<00:28:10.840> connect 00:28:11.230 --> 00:28:11.240 align:start position:0% doing the real thing you should connect 00:28:11.240 --> 00:28:15.230 align:start position:0% doing the real thing you should connect with<00:28:11.399> a<00:28:11.880> hardware<00:28:12.640> wallet<00:28:13.640> um<00:28:14.360> um<00:28:14.559> but<00:28:14.760> you<00:28:15.080> as 00:28:15.230 --> 00:28:15.240 align:start position:0% with a hardware wallet um um but you as 00:28:15.240 --> 00:28:16.950 align:start position:0% with a hardware wallet um um but you as well<00:28:15.519> might<00:28:15.799> use 00:28:16.950 --> 00:28:16.960 align:start position:0% well might use 00:28:16.960 --> 00:28:20.509 align:start position:0% well might use metamask<00:28:17.960> I<00:28:18.080> don't<00:28:18.360> have<00:28:18.559> now<00:28:18.960> 32<00:28:19.679> holeski<00:28:20.240> e 00:28:20.509 --> 00:28:20.519 align:start position:0% metamask I don't have now 32 holeski e 00:28:20.519 --> 00:28:24.509 align:start position:0% metamask I don't have now 32 holeski e so<00:28:21.039> I<00:28:21.440> I<00:28:21.519> will<00:28:21.720> finish<00:28:22.159> here<00:28:22.399> but<00:28:23.159> um<00:28:23.399> you<00:28:23.720> then 00:28:24.509 --> 00:28:24.519 align:start position:0% so I I will finish here but um you then 00:28:24.519 --> 00:28:26.149 align:start position:0% so I I will finish here but um you then press<00:28:24.799> continue<00:28:25.200> and<00:28:25.360> everything<00:28:25.640> is<00:28:25.799> set<00:28:26.000> up 00:28:26.149 --> 00:28:26.159 align:start position:0% press continue and everything is set up 00:28:26.159 --> 00:28:26.830 align:start position:0% press continue and everything is set up for 00:28:26.830 --> 00:28:26.840 align:start position:0% for 00:28:26.840 --> 00:28:28.710 align:start position:0% for you<00:28:27.840> okay 00:28:28.710 --> 00:28:28.720 align:start position:0% you okay 00:28:28.720 --> 00:28:31.909 align:start position:0% you okay so<00:28:28.960> now<00:28:29.240> look<00:28:29.600> look<00:28:29.880> back<00:28:30.120> to<00:28:31.120> to<00:28:31.320> the<00:28:31.480> steum 00:28:31.909 --> 00:28:31.919 align:start position:0% so now look look back to to the steum 00:28:31.919 --> 00:28:34.430 align:start position:0% so now look look back to to the steum launcher<00:28:32.559> and<00:28:32.799> we<00:28:32.919> see<00:28:33.519> everything<00:28:34.000> has<00:28:34.159> start 00:28:34.430 --> 00:28:34.440 align:start position:0% launcher and we see everything has start 00:28:34.440 --> 00:28:37.509 align:start position:0% launcher and we see everything has start running<00:28:34.799> and<00:28:35.440> at<00:28:35.600> that<00:28:35.799> point<00:28:36.679> I<00:28:36.799> think<00:28:37.080> I<00:28:37.159> will 00:28:37.509 --> 00:28:37.519 align:start position:0% running and at that point I think I will 00:28:37.519 --> 00:28:41.850 align:start position:0% running and at that point I think I will hand<00:28:37.720> over<00:28:37.919> to 00:28:41.850 --> 00:28:41.860 align:start position:0% 00:28:41.860 --> 00:28:44.149 align:start position:0% [Applause] 00:28:44.149 --> 00:28:44.159 align:start position:0% [Applause] 00:28:44.159 --> 00:28:47.990 align:start position:0% [Applause] David<00:28:45.159> hi<00:28:45.399> hi<00:28:45.600> hi<00:28:45.919> okay<00:28:46.440> nice<00:28:47.440> uh<00:28:47.640> thank<00:28:47.799> you 00:28:47.990 --> 00:28:48.000 align:start position:0% David hi hi hi okay nice uh thank you 00:28:48.000 --> 00:28:50.149 align:start position:0% David hi hi hi okay nice uh thank you David<00:28:48.640> I'm<00:28:48.840> also<00:28:49.120> David<00:28:49.440> so<00:28:49.559> it's<00:28:49.720> pretty<00:28:49.960> easy 00:28:50.149 --> 00:28:50.159 align:start position:0% David I'm also David so it's pretty easy 00:28:50.159 --> 00:28:51.029 align:start position:0% David I'm also David so it's pretty easy to 00:28:51.029 --> 00:28:51.039 align:start position:0% to 00:28:51.039 --> 00:28:54.070 align:start position:0% to remember<00:28:52.039> um<00:28:52.720> I'm<00:28:52.840> going<00:28:52.960> to<00:28:53.080> show<00:28:53.279> you<00:28:53.480> like 00:28:54.070 --> 00:28:54.080 align:start position:0% remember um I'm going to show you like 00:28:54.080 --> 00:28:56.830 align:start position:0% remember um I'm going to show you like uh<00:28:55.039> basically<00:28:55.399> we're<00:28:55.600> going<00:28:55.799> to<00:28:56.519> I'm<00:28:56.640> going<00:28:56.720> to 00:28:56.830 --> 00:28:56.840 align:start position:0% uh basically we're going to I'm going to 00:28:56.840 --> 00:28:58.470 align:start position:0% uh basically we're going to I'm going to show<00:28:57.000> you<00:28:57.120> at<00:28:57.279> the<00:28:57.399> staking<00:28:57.760> page<00:28:58.159> works<00:28:58.399> I'm 00:28:58.470 --> 00:28:58.480 align:start position:0% show you at the staking page works I'm 00:28:58.480 --> 00:29:01.269 align:start position:0% show you at the staking page works I'm going<00:28:58.600> to<00:28:58.679> show<00:28:58.840> you<00:28:58.960> the<00:28:59.120> rest<00:28:59.320> of<00:28:59.519> the<00:29:00.440> um 00:29:01.269 --> 00:29:01.279 align:start position:0% going to show you the rest of the um 00:29:01.279 --> 00:29:02.950 align:start position:0% going to show you the rest of the um setup<00:29:01.760> itself<00:29:02.200> I'm<00:29:02.279> going<00:29:02.399> to<00:29:02.519> show<00:29:02.640> you<00:29:02.760> some 00:29:02.950 --> 00:29:02.960 align:start position:0% setup itself I'm going to show you some 00:29:02.960 --> 00:29:04.990 align:start position:0% setup itself I'm going to show you some management<00:29:03.519> options<00:29:04.360> at<00:29:04.480> the<00:29:04.559> end<00:29:04.760> I'm<00:29:04.880> going 00:29:04.990 --> 00:29:05.000 align:start position:0% management options at the end I'm going 00:29:05.000 --> 00:29:07.310 align:start position:0% management options at the end I'm going to<00:29:05.200> ask<00:29:05.480> like<00:29:05.720> Martin<00:29:06.320> to<00:29:06.519> join<00:29:06.799> me<00:29:06.919> for<00:29:07.080> some 00:29:07.310 --> 00:29:07.320 align:start position:0% to ask like Martin to join me for some 00:29:07.320 --> 00:29:09.029 align:start position:0% to ask like Martin to join me for some questions<00:29:07.720> you<00:29:07.799> can<00:29:08.000> ask<00:29:08.200> whatever<00:29:08.480> you<00:29:08.640> want 00:29:09.029 --> 00:29:09.039 align:start position:0% questions you can ask whatever you want 00:29:09.039 --> 00:29:11.149 align:start position:0% questions you can ask whatever you want about<00:29:09.279> staking<00:29:10.159> you<00:29:10.279> can<00:29:10.440> also<00:29:10.640> ask<00:29:10.799> me<00:29:10.960> like 00:29:11.149 --> 00:29:11.159 align:start position:0% about staking you can also ask me like 00:29:11.159 --> 00:29:12.509 align:start position:0% about staking you can also ask me like personal<00:29:11.600> questions<00:29:11.960> but<00:29:12.080> I<00:29:12.200> would<00:29:12.360> like 00:29:12.509 --> 00:29:12.519 align:start position:0% personal questions but I would like 00:29:12.519 --> 00:29:17.190 align:start position:0% personal questions but I would like refering<00:29:13.000> from<00:29:13.480> that<00:29:14.640> um<00:29:15.640> let's<00:29:15.919> just<00:29:16.080> see<00:29:16.720> as 00:29:17.190 --> 00:29:17.200 align:start position:0% refering from that um let's just see as 00:29:17.200 --> 00:29:19.870 align:start position:0% refering from that um let's just see as uh<00:29:17.360> David<00:29:17.679> already<00:29:18.000> explained<00:29:18.960> basically<00:29:19.440> you 00:29:19.870 --> 00:29:19.880 align:start position:0% uh David already explained basically you 00:29:19.880 --> 00:29:22.350 align:start position:0% uh David already explained basically you deposit<00:29:20.320> your<00:29:20.640> key<00:29:21.640> uh<00:29:21.760> as<00:29:21.840> soon<00:29:22.000> as<00:29:22.159> you 00:29:22.350 --> 00:29:22.360 align:start position:0% deposit your key uh as soon as you 00:29:22.360 --> 00:29:24.269 align:start position:0% deposit your key uh as soon as you deposited<00:29:22.840> your<00:29:23.000> key<00:29:23.320> this<00:29:23.519> key<00:29:23.720> goes<00:29:23.919> into 00:29:24.269 --> 00:29:24.279 align:start position:0% deposited your key this key goes into 00:29:24.279 --> 00:29:26.990 align:start position:0% deposited your key this key goes into activation<00:29:24.799> queue<00:29:25.519> usually<00:29:25.960> takes<00:29:26.559> a<00:29:26.720> few 00:29:26.990 --> 00:29:27.000 align:start position:0% activation queue usually takes a few 00:29:27.000 --> 00:29:29.430 align:start position:0% activation queue usually takes a few days<00:29:27.640> during<00:29:28.159> this<00:29:28.320> time<00:29:28.559> you<00:29:28.640> can<00:29:28.840> basically 00:29:29.430 --> 00:29:29.440 align:start position:0% days during this time you can basically 00:29:29.440 --> 00:29:32.269 align:start position:0% days during this time you can basically but<00:29:29.799> you<00:29:29.919> can<00:29:30.320> already<00:29:31.120> if<00:29:31.240> you<00:29:31.360> want<00:29:31.600> to 00:29:32.269 --> 00:29:32.279 align:start position:0% but you can already if you want to 00:29:32.279 --> 00:29:36.070 align:start position:0% but you can already if you want to import<00:29:32.799> this<00:29:33.000> key<00:29:33.279> in<00:29:33.480> the<00:29:33.960> setup<00:29:34.720> itself<00:29:35.720> so 00:29:36.070 --> 00:29:36.080 align:start position:0% import this key in the setup itself so 00:29:36.080 --> 00:29:37.830 align:start position:0% import this key in the setup itself so to<00:29:36.200> do<00:29:36.399> this<00:29:36.519> you<00:29:36.640> would<00:29:36.799> go<00:29:36.960> on<00:29:37.080> the<00:29:37.200> staking 00:29:37.830 --> 00:29:37.840 align:start position:0% to do this you would go on the staking 00:29:37.840 --> 00:29:40.190 align:start position:0% to do this you would go on the staking page<00:29:38.840> on<00:29:39.000> the<00:29:39.120> bottom<00:29:39.519> as<00:29:39.600> you<00:29:39.720> can<00:29:39.880> see 00:29:40.190 --> 00:29:40.200 align:start position:0% page on the bottom as you can see 00:29:40.200 --> 00:29:44.029 align:start position:0% page on the bottom as you can see there's<00:29:40.480> like<00:29:40.640> a<00:29:41.039> click<00:29:41.399> to<00:29:42.360> insert<00:29:42.679> the<00:29:43.039> key 00:29:44.029 --> 00:29:44.039 align:start position:0% there's like a click to insert the key 00:29:44.039 --> 00:29:46.470 align:start position:0% there's like a click to insert the key uh<00:29:44.320> as<00:29:44.399> soon<00:29:44.559> as<00:29:44.679> the<00:29:44.840> key<00:29:45.320> you<00:29:46.080> basically 00:29:46.470 --> 00:29:46.480 align:start position:0% uh as soon as the key you basically 00:29:46.480 --> 00:29:49.509 align:start position:0% uh as soon as the key you basically click<00:29:46.840> this<00:29:47.799> you<00:29:48.120> select<00:29:48.480> the<00:29:48.640> key 00:29:49.509 --> 00:29:49.519 align:start position:0% click this you select the key 00:29:49.519 --> 00:29:52.070 align:start position:0% click this you select the key itself<00:29:50.519> I<00:29:50.640> cannot<00:29:51.039> read<00:29:51.320> this<00:29:51.480> I'm<00:29:51.679> a<00:29:51.799> little 00:29:52.070 --> 00:29:52.080 align:start position:0% itself I cannot read this I'm a little 00:29:52.080 --> 00:29:53.710 align:start position:0% itself I cannot read this I'm a little blind<00:29:52.519> I'm 00:29:53.710 --> 00:29:53.720 align:start position:0% blind I'm 00:29:53.720 --> 00:29:56.310 align:start position:0% blind I'm sorry<00:29:54.720> basically<00:29:55.240> select<00:29:55.519> the<00:29:55.679> Chason<00:29:56.080> key 00:29:56.310 --> 00:29:56.320 align:start position:0% sorry basically select the Chason key 00:29:56.320 --> 00:29:58.549 align:start position:0% sorry basically select the Chason key file<00:29:56.720> you<00:29:56.960> go<00:29:57.200> into 00:29:58.549 --> 00:29:58.559 align:start position:0% file you go into 00:29:58.559 --> 00:30:01.029 align:start position:0% file you go into e<00:29:59.440> and<00:29:59.600> then<00:29:59.720> you<00:29:59.840> would<00:30:00.360> uh<00:30:00.519> basically<00:30:00.880> go 00:30:01.029 --> 00:30:01.039 align:start position:0% e and then you would uh basically go 00:30:01.039 --> 00:30:04.070 align:start position:0% e and then you would uh basically go through<00:30:01.240> the<00:30:01.360> other<00:30:01.799> steps<00:30:02.799> as<00:30:02.919> I<00:30:03.080> can<00:30:03.320> see<00:30:03.960> we 00:30:04.070 --> 00:30:04.080 align:start position:0% through the other steps as I can see we 00:30:04.080 --> 00:30:09.149 align:start position:0% through the other steps as I can see we have<00:30:04.279> like<00:30:04.440> a<00:30:04.919> little<00:30:05.159> bit<00:30:05.360> of<00:30:05.880> a<00:30:06.880> thing<00:30:07.200> here 00:30:09.149 --> 00:30:09.159 align:start position:0% have like a little bit of a thing here 00:30:09.159 --> 00:30:16.029 align:start position:0% have like a little bit of a thing here um<00:30:10.159> what<00:30:10.279> did<00:30:10.399> you<00:30:10.559> use<00:30:10.720> as 00:30:16.029 --> 00:30:16.039 align:start position:0% 00:30:16.039 --> 00:30:18.909 align:start position:0% password<00:30:17.039> okay<00:30:17.240> this<00:30:17.399> a<00:30:17.559> good<00:30:17.799> P<00:30:18.200> thank 00:30:18.909 --> 00:30:18.919 align:start position:0% password okay this a good P thank 00:30:18.919 --> 00:30:23.430 align:start position:0% password okay this a good P thank you<00:30:19.919> um<00:30:20.440> I'm<00:30:20.600> going<00:30:20.679> to<00:30:20.919> go<00:30:21.240> here 00:30:23.430 --> 00:30:23.440 align:start position:0% you um I'm going to go here 00:30:23.440 --> 00:30:25.269 align:start position:0% you um I'm going to go here Bam 00:30:25.269 --> 00:30:25.279 align:start position:0% Bam 00:30:25.279 --> 00:30:28.389 align:start position:0% Bam Bam<00:30:26.279> on<00:30:26.440> the<00:30:26.600> bottom<00:30:27.279> as<00:30:27.399> you<00:30:27.480> can<00:30:27.640> see<00:30:28.200> you're 00:30:28.389 --> 00:30:28.399 align:start position:0% Bam on the bottom as you can see you're 00:30:28.399 --> 00:30:29.990 align:start position:0% Bam on the bottom as you can see you're already<00:30:28.760> like<00:30:28.880> inserting<00:30:29.320> the<00:30:29.440> key<00:30:29.760> on<00:30:29.880> the 00:30:29.990 --> 00:30:30.000 align:start position:0% already like inserting the key on the 00:30:30.000 --> 00:30:31.789 align:start position:0% already like inserting the key on the bottom<00:30:30.279> you<00:30:30.360> can<00:30:30.600> select<00:30:31.000> which<00:30:31.200> validate<00:30:31.640> the 00:30:31.789 --> 00:30:31.799 align:start position:0% bottom you can select which validate the 00:30:31.799 --> 00:30:34.430 align:start position:0% bottom you can select which validate the client<00:30:32.120> you<00:30:32.360> want<00:30:32.519> to<00:30:32.679> import<00:30:33.039> to<00:30:33.960> uh<00:30:34.080> steering 00:30:34.430 --> 00:30:34.440 align:start position:0% client you want to import to uh steering 00:30:34.440 --> 00:30:36.029 align:start position:0% client you want to import to uh steering gives<00:30:34.640> you<00:30:34.760> the<00:30:34.880> option<00:30:35.080> to<00:30:35.200> run<00:30:35.440> multiple 00:30:36.029 --> 00:30:36.039 align:start position:0% gives you the option to run multiple 00:30:36.039 --> 00:30:38.430 align:start position:0% gives you the option to run multiple clients<00:30:36.480> at<00:30:36.600> the<00:30:36.760> same<00:30:37.120> time<00:30:38.120> uh<00:30:38.200> when<00:30:38.320> it 00:30:38.430 --> 00:30:38.440 align:start position:0% clients at the same time uh when it 00:30:38.440 --> 00:30:40.310 align:start position:0% clients at the same time uh when it comes<00:30:38.600> to<00:30:38.760> validate<00:30:39.159> the<00:30:39.320> clients<00:30:39.960> I<00:30:40.039> would 00:30:40.310 --> 00:30:40.320 align:start position:0% comes to validate the clients I would 00:30:40.320 --> 00:30:45.350 align:start position:0% comes to validate the clients I would ask<00:30:40.600> you<00:30:41.200> um<00:30:41.440> or<00:30:42.120> like<00:30:43.120> please<00:30:43.760> um<00:30:44.559> please 00:30:45.350 --> 00:30:45.360 align:start position:0% ask you um or like please um please 00:30:45.360 --> 00:30:47.070 align:start position:0% ask you um or like please um please please<00:30:45.679> please<00:30:45.960> please<00:30:46.200> please<00:30:46.480> please<00:30:46.960> if 00:30:47.070 --> 00:30:47.080 align:start position:0% please please please please please if 00:30:47.080 --> 00:30:49.470 align:start position:0% please please please please please if you<00:30:47.200> run<00:30:47.519> to<00:30:47.840> validate<00:30:48.279> the<00:30:48.440> clients<00:30:49.200> never 00:30:49.470 --> 00:30:49.480 align:start position:0% you run to validate the clients never 00:30:49.480 --> 00:30:51.029 align:start position:0% you run to validate the clients never import<00:30:49.799> the<00:30:49.919> same<00:30:50.120> key<00:30:50.320> in<00:30:50.440> both<00:30:50.640> clients 00:30:51.029 --> 00:30:51.039 align:start position:0% import the same key in both clients 00:30:51.039 --> 00:30:52.789 align:start position:0% import the same key in both clients you're<00:30:51.200> going<00:30:51.279> to<00:30:51.440> get<00:30:51.559> slashed<00:30:52.399> that's<00:30:52.600> just 00:30:52.789 --> 00:30:52.799 align:start position:0% you're going to get slashed that's just 00:30:52.799 --> 00:30:57.029 align:start position:0% you're going to get slashed that's just how<00:30:52.960> it<00:30:53.320> is<00:30:54.320> uh<00:30:54.840> slashing<00:30:55.399> is<00:30:55.880> um<00:30:56.440> especially 00:30:57.029 --> 00:30:57.039 align:start position:0% how it is uh slashing is um especially 00:30:57.039 --> 00:31:00.190 align:start position:0% how it is uh slashing is um especially here<00:30:58.240> uh<00:30:58.440> usually<00:30:58.840> not<00:30:59.320> that<00:30:59.639> much<00:30:59.840> of<00:31:00.000> a 00:31:00.190 --> 00:31:00.200 align:start position:0% here uh usually not that much of a 00:31:00.200 --> 00:31:01.669 align:start position:0% here uh usually not that much of a problem<00:31:00.480> I<00:31:00.600> know<00:31:00.720> a<00:31:00.840> lot<00:31:00.960> of<00:31:01.120> people<00:31:01.360> like<00:31:01.480> are 00:31:01.669 --> 00:31:01.679 align:start position:0% problem I know a lot of people like are 00:31:01.679 --> 00:31:04.190 align:start position:0% problem I know a lot of people like are really<00:31:02.600> uh<00:31:02.760> intimidated<00:31:03.559> by<00:31:03.679> the<00:31:03.799> idea<00:31:04.039> of 00:31:04.190 --> 00:31:04.200 align:start position:0% really uh intimidated by the idea of 00:31:04.200 --> 00:31:06.990 align:start position:0% really uh intimidated by the idea of getting<00:31:04.639> slashed<00:31:05.639> but<00:31:05.799> it's<00:31:06.080> usually<00:31:06.679> really 00:31:06.990 --> 00:31:07.000 align:start position:0% getting slashed but it's usually really 00:31:07.000 --> 00:31:10.430 align:start position:0% getting slashed but it's usually really really<00:31:07.639> rare<00:31:08.639> uh<00:31:09.080> most<00:31:09.399> people<00:31:09.679> you<00:31:09.919> see 00:31:10.430 --> 00:31:10.440 align:start position:0% really rare uh most people you see 00:31:10.440 --> 00:31:12.590 align:start position:0% really rare uh most people you see getting<00:31:10.760> slashed<00:31:11.480> or<00:31:11.720> if<00:31:11.840> you<00:31:12.000> see<00:31:12.240> someone 00:31:12.590 --> 00:31:12.600 align:start position:0% getting slashed or if you see someone 00:31:12.600 --> 00:31:14.870 align:start position:0% getting slashed or if you see someone getting<00:31:12.840> slashed<00:31:13.360> it<00:31:13.480> is<00:31:13.760> because<00:31:14.760> they 00:31:14.870 --> 00:31:14.880 align:start position:0% getting slashed it is because they 00:31:14.880 --> 00:31:16.750 align:start position:0% getting slashed it is because they thought<00:31:15.120> they<00:31:15.240> were<00:31:15.559> too<00:31:15.840> smart<00:31:16.320> who<00:31:16.480> wanted 00:31:16.750 --> 00:31:16.760 align:start position:0% thought they were too smart who wanted 00:31:16.760 --> 00:31:19.669 align:start position:0% thought they were too smart who wanted to<00:31:17.039> like<00:31:17.559> build<00:31:17.799> a<00:31:18.000> backup<00:31:18.480> system<00:31:19.039> that<00:31:19.240> got 00:31:19.669 --> 00:31:19.679 align:start position:0% to like build a backup system that got 00:31:19.679 --> 00:31:23.669 align:start position:0% to like build a backup system that got online<00:31:20.760> suddenly<00:31:21.760> or<00:31:22.360> um<00:31:22.679> tried<00:31:22.960> to<00:31:23.240> like<00:31:23.559> uh 00:31:23.669 --> 00:31:23.679 align:start position:0% online suddenly or um tried to like uh 00:31:23.679 --> 00:31:26.830 align:start position:0% online suddenly or um tried to like uh do<00:31:23.880> some<00:31:24.600> great<00:31:25.000> engineering<00:31:25.720> stuff<00:31:26.559> I<00:31:26.679> can 00:31:26.830 --> 00:31:26.840 align:start position:0% do some great engineering stuff I can 00:31:26.840 --> 00:31:28.830 align:start position:0% do some great engineering stuff I can tell<00:31:27.039> you<00:31:27.360> uh<00:31:27.440> when<00:31:27.559> you<00:31:27.639> want<00:31:27.799> to<00:31:27.960> a<00:31:28.159> stake 00:31:28.830 --> 00:31:28.840 align:start position:0% tell you uh when you want to a stake 00:31:28.840 --> 00:31:32.190 align:start position:0% tell you uh when you want to a stake keep<00:31:29.039> it<00:31:29.440> simple<00:31:30.440> uh<00:31:30.559> even<00:31:30.799> if<00:31:30.919> you<00:31:31.039> go<00:31:31.320> offline 00:31:32.190 --> 00:31:32.200 align:start position:0% keep it simple uh even if you go offline 00:31:32.200 --> 00:31:34.710 align:start position:0% keep it simple uh even if you go offline okay<00:31:32.720> um<00:31:33.279> let's<00:31:33.480> say<00:31:33.639> you<00:31:33.760> go<00:31:33.960> offline<00:31:34.320> for<00:31:34.519> 1 00:31:34.710 --> 00:31:34.720 align:start position:0% okay um let's say you go offline for 1 00:31:34.720 --> 00:31:37.110 align:start position:0% okay um let's say you go offline for 1 hour<00:31:35.279> you<00:31:35.399> will<00:31:35.639> get<00:31:36.000> back<00:31:36.240> the<00:31:36.440> rewards 00:31:37.110 --> 00:31:37.120 align:start position:0% hour you will get back the rewards 00:31:37.120 --> 00:31:39.509 align:start position:0% hour you will get back the rewards basically<00:31:37.480> you<00:31:37.679> lost<00:31:37.919> in<00:31:38.080> this<00:31:38.240> one<00:31:38.440> hour<00:31:39.240> in 00:31:39.509 --> 00:31:39.519 align:start position:0% basically you lost in this one hour in 00:31:39.519 --> 00:31:42.710 align:start position:0% basically you lost in this one hour in one<00:31:39.760> hour<00:31:40.480> so<00:31:40.880> it's<00:31:41.200> around<00:31:41.519> the<00:31:41.679> same 00:31:42.710 --> 00:31:42.720 align:start position:0% one hour so it's around the same 00:31:42.720 --> 00:31:46.629 align:start position:0% one hour so it's around the same time<00:31:43.919> um<00:31:44.919> and<00:31:45.279> if<00:31:45.399> you<00:31:45.519> get<00:31:45.679> slashed<00:31:46.360> there's 00:31:46.629 --> 00:31:46.639 align:start position:0% time um and if you get slashed there's 00:31:46.639 --> 00:31:49.190 align:start position:0% time um and if you get slashed there's no<00:31:47.279> this<00:31:47.519> happens<00:31:47.960> basically<00:31:48.320> immediately<00:31:48.919> so 00:31:49.190 --> 00:31:49.200 align:start position:0% no this happens basically immediately so 00:31:49.200 --> 00:31:51.710 align:start position:0% no this happens basically immediately so there<00:31:49.360> there's<00:31:49.840> no<00:31:50.840> uh<00:31:50.960> there's<00:31:51.159> no<00:31:51.360> good<00:31:51.639> you 00:31:51.710 --> 00:31:51.720 align:start position:0% there there's no uh there's no good you 00:31:51.720 --> 00:31:54.070 align:start position:0% there there's no uh there's no good you cannot<00:31:52.080> recover<00:31:52.519> from<00:31:52.760> this<00:31:53.120> so<00:31:53.679> keep<00:31:53.880> it 00:31:54.070 --> 00:31:54.080 align:start position:0% cannot recover from this so keep it 00:31:54.080 --> 00:31:56.950 align:start position:0% cannot recover from this so keep it simple<00:31:54.799> try<00:31:55.039> to<00:31:55.279> like<00:31:55.639> stay<00:31:55.960> with<00:31:56.200> one<00:31:56.519> client 00:31:56.950 --> 00:31:56.960 align:start position:0% simple try to like stay with one client 00:31:56.960 --> 00:31:58.870 align:start position:0% simple try to like stay with one client PA<00:31:57.279> if<00:31:57.399> you're<00:31:57.880> especially<00:31:58.240> don't<00:31:58.639> uh 00:31:58.870 --> 00:31:58.880 align:start position:0% PA if you're especially don't uh 00:31:58.880 --> 00:32:01.269 align:start position:0% PA if you're especially don't uh especially<00:31:59.240> if<00:31:59.320> you're<00:31:59.720> beginner<00:32:00.720> and<00:32:01.159> uh 00:32:01.269 --> 00:32:01.279 align:start position:0% especially if you're beginner and uh 00:32:01.279 --> 00:32:03.669 align:start position:0% especially if you're beginner and uh don't<00:32:01.559> go<00:32:01.679> for<00:32:01.880> multiple<00:32:02.279> valid<00:32:02.600> dat<00:32:02.880> clients 00:32:03.669 --> 00:32:03.679 align:start position:0% don't go for multiple valid dat clients 00:32:03.679 --> 00:32:05.750 align:start position:0% don't go for multiple valid dat clients if<00:32:03.799> you<00:32:03.919> want<00:32:04.039> to<00:32:04.440> uh<00:32:04.519> do<00:32:04.679> a<00:32:04.880> backup<00:32:05.320> system<00:32:05.639> you 00:32:05.750 --> 00:32:05.760 align:start position:0% if you want to uh do a backup system you 00:32:05.760 --> 00:32:08.430 align:start position:0% if you want to uh do a backup system you can<00:32:06.039> do<00:32:06.240> this<00:32:06.720> by<00:32:06.919> like<00:32:07.080> running<00:32:07.519> a<00:32:07.720> extra 00:32:08.430 --> 00:32:08.440 align:start position:0% can do this by like running a extra 00:32:08.440 --> 00:32:10.830 align:start position:0% can do this by like running a extra execution<00:32:09.039> and<00:32:09.279> consensus<00:32:09.799> client<00:32:10.120> pair<00:32:10.639> you 00:32:10.830 --> 00:32:10.840 align:start position:0% execution and consensus client pair you 00:32:10.840 --> 00:32:12.669 align:start position:0% execution and consensus client pair you basically<00:32:11.240> just<00:32:11.440> change<00:32:11.760> the<00:32:11.960> connections<00:32:12.600> I 00:32:12.669 --> 00:32:12.679 align:start position:0% basically just change the connections I 00:32:12.679 --> 00:32:14.470 align:start position:0% basically just change the connections I will<00:32:12.799> show<00:32:13.000> you<00:32:13.159> this<00:32:13.320> after<00:32:13.600> as<00:32:13.720> well<00:32:14.200> you<00:32:14.320> can 00:32:14.470 --> 00:32:14.480 align:start position:0% will show you this after as well you can 00:32:14.480 --> 00:32:18.230 align:start position:0% will show you this after as well you can do<00:32:14.679> this<00:32:14.919> inside<00:32:15.279> of<00:32:15.519> the<00:32:15.840> UI<00:32:16.200> as<00:32:16.760> well<00:32:17.760> so<00:32:18.039> we 00:32:18.230 --> 00:32:18.240 align:start position:0% do this inside of the UI as well so we 00:32:18.240 --> 00:32:20.669 align:start position:0% do this inside of the UI as well so we just<00:32:18.440> select<00:32:18.919> here<00:32:19.679> uh<00:32:19.880> the<00:32:20.159> client<00:32:20.440> we<00:32:20.559> want 00:32:20.669 --> 00:32:20.679 align:start position:0% just select here uh the client we want 00:32:20.679 --> 00:32:22.070 align:start position:0% just select here uh the client we want to<00:32:20.799> import 00:32:22.070 --> 00:32:22.080 align:start position:0% to import 00:32:22.080 --> 00:32:23.909 align:start position:0% to import into<00:32:23.080> this 00:32:23.909 --> 00:32:23.919 align:start position:0% into this 00:32:23.919 --> 00:32:26.870 align:start position:0% into this case<00:32:24.919> see<00:32:25.080> if<00:32:25.200> I<00:32:25.320> get<00:32:25.480> the<00:32:25.679> password<00:32:26.120> correctly 00:32:26.870 --> 00:32:26.880 align:start position:0% case see if I get the password correctly 00:32:26.880 --> 00:32:32.710 align:start position:0% case see if I get the password correctly one<00:32:27.120> second 00:32:32.710 --> 00:32:32.720 align:start position:0% 00:32:32.720 --> 00:32:35.909 align:start position:0% so<00:32:33.360> uh<00:32:33.600> put<00:32:33.799> in<00:32:33.960> the<00:32:34.200> password<00:32:35.200> you<00:32:35.320> can<00:32:35.480> see 00:32:35.909 --> 00:32:35.919 align:start position:0% so uh put in the password you can see 00:32:35.919 --> 00:32:38.990 align:start position:0% so uh put in the password you can see you<00:32:36.039> click<00:32:36.600> the<00:32:37.600> then<00:32:38.039> uh<00:32:38.120> you<00:32:38.279> have<00:32:38.480> the 00:32:38.990 --> 00:32:39.000 align:start position:0% you click the then uh you have the 00:32:39.000 --> 00:32:41.549 align:start position:0% you click the then uh you have the option<00:32:40.000> uh<00:32:40.120> to<00:32:40.320> import<00:32:40.720> with<00:32:40.840> a<00:32:41.000> slashing 00:32:41.549 --> 00:32:41.559 align:start position:0% option uh to import with a slashing 00:32:41.559 --> 00:32:44.350 align:start position:0% option uh to import with a slashing protection<00:32:42.480> database<00:32:43.480> uh<00:32:43.639> at<00:32:43.760> the<00:32:43.919> beginning 00:32:44.350 --> 00:32:44.360 align:start position:0% protection database uh at the beginning 00:32:44.360 --> 00:32:45.830 align:start position:0% protection database uh at the beginning when<00:32:44.480> you<00:32:44.600> first<00:32:44.840> set<00:32:45.039> up<00:32:45.159> you<00:32:45.320> don't<00:32:45.559> have<00:32:45.720> a 00:32:45.830 --> 00:32:45.840 align:start position:0% when you first set up you don't have a 00:32:45.840 --> 00:32:47.870 align:start position:0% when you first set up you don't have a slashing<00:32:46.279> protection<00:32:46.720> database<00:32:47.519> you<00:32:47.679> get 00:32:47.870 --> 00:32:47.880 align:start position:0% slashing protection database you get 00:32:47.880 --> 00:32:49.830 align:start position:0% slashing protection database you get this<00:32:48.039> if<00:32:48.159> you<00:32:48.320> remove<00:32:48.639> a<00:32:48.760> key<00:32:49.000> from<00:32:49.159> a<00:32:49.519> valid 00:32:49.830 --> 00:32:49.840 align:start position:0% this if you remove a key from a valid 00:32:49.840 --> 00:32:51.549 align:start position:0% this if you remove a key from a valid dat<00:32:50.120> client<00:32:50.679> you<00:32:50.840> have<00:32:50.960> the<00:32:51.120> option<00:32:51.360> to 00:32:51.549 --> 00:32:51.559 align:start position:0% dat client you have the option to 00:32:51.559 --> 00:32:53.029 align:start position:0% dat client you have the option to download<00:32:51.960> this<00:32:52.080> slashing<00:32:52.559> protection 00:32:53.029 --> 00:32:53.039 align:start position:0% download this slashing protection 00:32:53.039 --> 00:32:55.190 align:start position:0% download this slashing protection database<00:32:54.039> as<00:32:54.159> you<00:32:54.279> might<00:32:54.519> like<00:32:54.760> guess<00:32:55.039> from 00:32:55.190 --> 00:32:55.200 align:start position:0% database as you might like guess from 00:32:55.200 --> 00:32:56.870 align:start position:0% database as you might like guess from the<00:32:55.360> name<00:32:55.679> it's<00:32:55.840> supposed<00:32:56.159> to<00:32:56.240> be<00:32:56.360> an<00:32:56.519> extra 00:32:56.870 --> 00:32:56.880 align:start position:0% the name it's supposed to be an extra 00:32:56.880 --> 00:32:58.909 align:start position:0% the name it's supposed to be an extra layer<00:32:57.240> on<00:32:57.399> top<00:32:57.559> of<00:32:57.679> this 00:32:58.909 --> 00:32:58.919 align:start position:0% layer on top of this 00:32:58.919 --> 00:33:01.149 align:start position:0% layer on top of this uh<00:32:59.240> you<00:32:59.399> also<00:32:59.679> have<00:32:59.919> the<00:33:00.399> uh<00:33:00.559> double<00:33:00.919> G 00:33:01.149 --> 00:33:01.159 align:start position:0% uh you also have the uh double G 00:33:01.159 --> 00:33:03.870 align:start position:0% uh you also have the uh double G doubleganger<00:33:01.840> protection<00:33:02.240> running<00:33:03.240> um<00:33:03.720> this 00:33:03.870 --> 00:33:03.880 align:start position:0% doubleganger protection running um this 00:33:03.880 --> 00:33:06.269 align:start position:0% doubleganger protection running um this is<00:33:04.120> basically<00:33:04.960> uh<00:33:05.120> every<00:33:05.399> client<00:33:05.880> as<00:33:06.000> soon<00:33:06.159> as 00:33:06.269 --> 00:33:06.279 align:start position:0% is basically uh every client as soon as 00:33:06.279 --> 00:33:09.629 align:start position:0% is basically uh every client as soon as you<00:33:06.840> import<00:33:07.840> uh<00:33:07.919> a<00:33:08.120> key<00:33:08.720> basically<00:33:09.120> checks<00:33:09.480> the 00:33:09.629 --> 00:33:09.639 align:start position:0% you import uh a key basically checks the 00:33:09.639 --> 00:33:13.070 align:start position:0% you import uh a key basically checks the chain<00:33:10.440> if<00:33:10.679> the<00:33:11.279> uh<00:33:11.880> if<00:33:12.000> the<00:33:12.159> validator<00:33:12.760> key 00:33:13.070 --> 00:33:13.080 align:start position:0% chain if the uh if the validator key 00:33:13.080 --> 00:33:16.149 align:start position:0% chain if the uh if the validator key attested<00:33:13.639> in<00:33:13.840> the<00:33:14.000> last<00:33:14.240> two<00:33:14.559> EPO<00:33:15.559> this<00:33:15.799> can 00:33:16.149 --> 00:33:16.159 align:start position:0% attested in the last two EPO this can 00:33:16.159 --> 00:33:18.909 align:start position:0% attested in the last two EPO this can take<00:33:16.760> depending<00:33:17.120> on<00:33:17.360> client<00:33:18.200> actually<00:33:18.600> quite 00:33:18.909 --> 00:33:18.919 align:start position:0% take depending on client actually quite 00:33:18.919 --> 00:33:21.830 align:start position:0% take depending on client actually quite long<00:33:19.919> I<00:33:20.000> think<00:33:20.200> te<00:33:20.519> is<00:33:20.600> the<00:33:20.720> longest<00:33:21.360> I<00:33:21.440> think 00:33:21.830 --> 00:33:21.840 align:start position:0% long I think te is the longest I think 00:33:21.840 --> 00:33:23.990 align:start position:0% long I think te is the longest I think it<00:33:22.039> could<00:33:22.559> uh<00:33:22.840> sometimes<00:33:23.120> take<00:33:23.399> up<00:33:23.519> to<00:33:23.679> half<00:33:23.880> an 00:33:23.990 --> 00:33:24.000 align:start position:0% it could uh sometimes take up to half an 00:33:24.000 --> 00:33:26.149 align:start position:0% it could uh sometimes take up to half an hour<00:33:24.639> some<00:33:24.799> of<00:33:24.919> them<00:33:25.080> are<00:33:25.279> really<00:33:25.519> fast<00:33:25.799> doing 00:33:26.149 --> 00:33:26.159 align:start position:0% hour some of them are really fast doing 00:33:26.159 --> 00:33:29.710 align:start position:0% hour some of them are really fast doing it<00:33:27.159> uh<00:33:27.279> if<00:33:27.399> you<00:33:27.519> have<00:33:27.919> like<00:33:28.600> um<00:33:29.120> if<00:33:29.240> you're<00:33:29.440> in<00:33:29.559> a 00:33:29.710 --> 00:33:29.720 align:start position:0% it uh if you have like um if you're in a 00:33:29.720 --> 00:33:31.710 align:start position:0% it uh if you have like um if you're in a hurry<00:33:30.159> you<00:33:30.279> can<00:33:30.519> always<00:33:30.840> deactivate<00:33:31.440> this<00:33:31.639> I 00:33:31.710 --> 00:33:31.720 align:start position:0% hurry you can always deactivate this I 00:33:31.720 --> 00:33:34.430 align:start position:0% hurry you can always deactivate this I will<00:33:31.919> also<00:33:32.120> show<00:33:32.320> you<00:33:32.480> how<00:33:32.600> to<00:33:32.720> do<00:33:33.159> this<00:33:34.159> uh<00:33:34.279> in 00:33:34.430 --> 00:33:34.440 align:start position:0% will also show you how to do this uh in 00:33:34.440 --> 00:33:36.430 align:start position:0% will also show you how to do this uh in this<00:33:34.639> case<00:33:34.919> as<00:33:35.039> I<00:33:35.200> said<00:33:35.440> we<00:33:35.559> don't<00:33:35.799> have<00:33:35.960> a 00:33:36.430 --> 00:33:36.440 align:start position:0% this case as I said we don't have a 00:33:36.440 --> 00:33:38.389 align:start position:0% this case as I said we don't have a slashing<00:33:37.080> protection<00:33:37.559> database<00:33:38.080> so<00:33:38.240> we're 00:33:38.389 --> 00:33:38.399 align:start position:0% slashing protection database so we're 00:33:38.399 --> 00:33:40.909 align:start position:0% slashing protection database so we're just<00:33:38.519> going<00:33:38.639> to<00:33:38.799> import<00:33:39.120> it<00:33:39.480> here<00:33:40.480> and 00:33:40.909 --> 00:33:40.919 align:start position:0% just going to import it here and 00:33:40.919 --> 00:33:42.470 align:start position:0% just going to import it here and basically<00:33:41.320> it's<00:33:41.480> just<00:33:41.639> going<00:33:41.760> to<00:33:41.880> run<00:33:42.120> through 00:33:42.470 --> 00:33:42.480 align:start position:0% basically it's just going to run through 00:33:42.480 --> 00:33:44.669 align:start position:0% basically it's just going to run through I<00:33:42.600> hope<00:33:42.760> I<00:33:42.880> did<00:33:43.240> like<00:33:43.880> did<00:33:44.080> the<00:33:44.240> password 00:33:44.669 --> 00:33:44.679 align:start position:0% I hope I did like did the password 00:33:44.679 --> 00:33:47.350 align:start position:0% I hope I did like did the password correctly<00:33:45.679> and<00:33:45.840> as<00:33:45.960> soon<00:33:46.120> as<00:33:46.320> this<00:33:46.480> is<00:33:46.919> uh<00:33:47.240> this 00:33:47.350 --> 00:33:47.360 align:start position:0% correctly and as soon as this is uh this 00:33:47.360 --> 00:33:50.990 align:start position:0% correctly and as soon as this is uh this is<00:33:47.559> done<00:33:48.279> it's<00:33:48.440> going<00:33:48.559> to<00:33:48.799> just<00:33:49.480> uh<00:33:50.480> um<00:33:50.840> it's 00:33:50.990 --> 00:33:51.000 align:start position:0% is done it's going to just uh um it's 00:33:51.000 --> 00:33:53.870 align:start position:0% is done it's going to just uh um it's just<00:33:51.159> going<00:33:51.279> to<00:33:51.399> be<00:33:51.880> imported<00:33:52.880> the<00:33:53.360> you<00:33:53.480> can<00:33:53.679> do 00:33:53.870 --> 00:33:53.880 align:start position:0% just going to be imported the you can do 00:33:53.880 --> 00:33:57.070 align:start position:0% just going to be imported the you can do this<00:33:54.159> before<00:33:54.519> the<00:33:54.720> activation<00:33:55.320> C<00:33:55.639> Quee<00:33:56.240> runs 00:33:57.070 --> 00:33:57.080 align:start position:0% this before the activation C Quee runs 00:33:57.080 --> 00:33:58.230 align:start position:0% this before the activation C Quee runs yes 00:33:58.230 --> 00:33:58.240 align:start position:0% yes 00:33:58.240 --> 00:34:00.710 align:start position:0% yes effect<00:33:59.240> you<00:33:59.320> can<00:33:59.480> do<00:33:59.639> this<00:33:59.799> before<00:34:00.120> the<00:34:00.600> the 00:34:00.710 --> 00:34:00.720 align:start position:0% effect you can do this before the the 00:34:00.720 --> 00:34:02.110 align:start position:0% effect you can do this before the the keys<00:34:00.960> through<00:34:01.200> the<00:34:01.399> activation<00:34:01.880> queue 00:34:02.110 --> 00:34:02.120 align:start position:0% keys through the activation queue 00:34:02.120 --> 00:34:05.669 align:start position:0% keys through the activation queue meaning<00:34:03.120> as<00:34:03.320> soon<00:34:03.639> as<00:34:03.880> you<00:34:04.440> uh<00:34:04.760> as<00:34:04.880> soon<00:34:05.080> as<00:34:05.279> you 00:34:05.669 --> 00:34:05.679 align:start position:0% meaning as soon as you uh as soon as you 00:34:05.679 --> 00:34:07.830 align:start position:0% meaning as soon as you uh as soon as you uh<00:34:06.080> went<00:34:06.440> through<00:34:06.679> the<00:34:06.840> activation<00:34:07.320> queue 00:34:07.830 --> 00:34:07.840 align:start position:0% uh went through the activation queue 00:34:07.840 --> 00:34:10.349 align:start position:0% uh went through the activation queue you're<00:34:08.079> already<00:34:08.359> online<00:34:09.079> so<00:34:09.280> you<00:34:09.720> basically 00:34:10.349 --> 00:34:10.359 align:start position:0% you're already online so you basically 00:34:10.359 --> 00:34:12.750 align:start position:0% you're already online so you basically just<00:34:10.720> import<00:34:11.119> it<00:34:11.760> wait<00:34:12.200> wait<00:34:12.359> till<00:34:12.560> it's 00:34:12.750 --> 00:34:12.760 align:start position:0% just import it wait wait till it's 00:34:12.760 --> 00:34:13.950 align:start position:0% just import it wait wait till it's activated<00:34:13.280> it's<00:34:13.399> just<00:34:13.560> going<00:34:13.639> to<00:34:13.800> be 00:34:13.950 --> 00:34:13.960 align:start position:0% activated it's just going to be 00:34:13.960 --> 00:34:16.430 align:start position:0% activated it's just going to be automatically<00:34:14.520> online<00:34:15.240> and<00:34:15.399> then<00:34:15.960> uh<00:34:16.320> then 00:34:16.430 --> 00:34:16.440 align:start position:0% automatically online and then uh then 00:34:16.440 --> 00:34:18.069 align:start position:0% automatically online and then uh then you<00:34:16.520> are<00:34:16.879> basically<00:34:17.240> a 00:34:18.069 --> 00:34:18.079 align:start position:0% you are basically a 00:34:18.079 --> 00:34:20.869 align:start position:0% you are basically a testing<00:34:19.079> um<00:34:19.240> on<00:34:19.359> the<00:34:19.480> staking<00:34:19.879> page<00:34:20.119> itself<00:34:20.760> as 00:34:20.869 --> 00:34:20.879 align:start position:0% testing um on the staking page itself as 00:34:20.879 --> 00:34:23.550 align:start position:0% testing um on the staking page itself as I<00:34:21.040> said<00:34:21.399> want<00:34:21.520> to<00:34:21.760> go<00:34:21.879> through<00:34:22.079> some<00:34:22.359> like<00:34:23.359> uh 00:34:23.550 --> 00:34:23.560 align:start position:0% I said want to go through some like uh 00:34:23.560 --> 00:34:26.310 align:start position:0% I said want to go through some like uh some<00:34:24.200> other<00:34:24.480> features<00:34:24.960> like<00:34:25.079> some<00:34:25.280> management 00:34:26.310 --> 00:34:26.320 align:start position:0% some other features like some management 00:34:26.320 --> 00:34:28.950 align:start position:0% some other features like some management features<00:34:27.320> um<00:34:27.839> on<00:34:28.000> the<00:34:28.079> staking<00:34:28.440> page<00:34:28.639> itself 00:34:28.950 --> 00:34:28.960 align:start position:0% features um on the staking page itself 00:34:28.960 --> 00:34:30.430 align:start position:0% features um on the staking page itself you<00:34:29.079> have<00:34:29.240> the<00:34:29.359> option<00:34:29.599> to<00:34:29.800> like<00:34:30.000> just<00:34:30.200> open 00:34:30.430 --> 00:34:30.440 align:start position:0% you have the option to like just open 00:34:30.440 --> 00:34:33.069 align:start position:0% you have the option to like just open Pon<00:34:30.720> sh<00:34:31.040> the<00:34:31.159> end<00:34:31.679> it's<00:34:31.879> just<00:34:32.000> a<00:34:32.240> quick<00:34:32.480> link 00:34:33.069 --> 00:34:33.079 align:start position:0% Pon sh the end it's just a quick link 00:34:33.079 --> 00:34:35.510 align:start position:0% Pon sh the end it's just a quick link it's<00:34:33.280> the<00:34:33.520> most<00:34:33.919> common<00:34:34.240> used<00:34:34.520> tool<00:34:34.919> to<00:34:35.320> get 00:34:35.510 --> 00:34:35.520 align:start position:0% it's the most common used tool to get 00:34:35.520 --> 00:34:38.470 align:start position:0% it's the most common used tool to get like<00:34:35.720> a<00:34:35.919> network<00:34:36.440> view<00:34:37.320> on<00:34:37.520> your<00:34:38.040> um<00:34:38.240> on<00:34:38.359> your 00:34:38.470 --> 00:34:38.480 align:start position:0% like a network view on your um on your 00:34:38.480 --> 00:34:43.149 align:start position:0% like a network view on your um on your note<00:34:39.359> or<00:34:39.599> on<00:34:39.760> your<00:34:40.000> key<00:34:41.079> um<00:34:42.079> because<00:34:42.480> this<00:34:42.760> case 00:34:43.149 --> 00:34:43.159 align:start position:0% note or on your key um because this case 00:34:43.159 --> 00:34:45.470 align:start position:0% note or on your key um because this case um<00:34:43.720> you<00:34:43.839> have<00:34:43.960> a<00:34:44.119> note<00:34:44.599> it's<00:34:44.760> a<00:34:44.919> peer<00:34:45.119> top 00:34:45.470 --> 00:34:45.480 align:start position:0% um you have a note it's a peer top 00:34:45.480 --> 00:34:48.869 align:start position:0% um you have a note it's a peer top Network<00:34:46.159> okay<00:34:47.000> it's<00:34:47.320> it's<00:34:47.480> not<00:34:47.720> seen<00:34:48.599> uh<00:34:48.760> it's 00:34:48.869 --> 00:34:48.879 align:start position:0% Network okay it's it's not seen uh it's 00:34:48.879 --> 00:34:52.109 align:start position:0% Network okay it's it's not seen uh it's not<00:34:49.040> seen<00:34:49.599> everywhere<00:34:50.599> uh<00:34:51.040> the<00:34:51.480> P<00:34:51.839> CH 00:34:52.109 --> 00:34:52.119 align:start position:0% not seen everywhere uh the P CH 00:34:52.119 --> 00:34:54.310 align:start position:0% not seen everywhere uh the P CH basically<00:34:52.440> gives<00:34:52.599> you<00:34:52.800> like<00:34:52.919> a<00:34:53.440> good<00:34:53.720> overview 00:34:54.310 --> 00:34:54.320 align:start position:0% basically gives you like a good overview 00:34:54.320 --> 00:34:58.430 align:start position:0% basically gives you like a good overview of<00:34:54.639> how<00:34:54.919> the<00:34:55.200> network<00:34:55.800> sees<00:34:56.280> your<00:34:56.599> key<00:34:58.040> um<00:34:58.320> you 00:34:58.430 --> 00:34:58.440 align:start position:0% of how the network sees your key um you 00:34:58.440 --> 00:35:01.390 align:start position:0% of how the network sees your key um you can<00:34:58.640> also<00:34:59.079> copy<00:34:59.400> the<00:34:59.920> public<00:35:00.320> key<00:35:00.960> um 00:35:01.390 --> 00:35:01.400 align:start position:0% can also copy the public key um 00:35:01.400 --> 00:35:03.750 align:start position:0% can also copy the public key um basically<00:35:01.960> identifier<00:35:02.960> quite<00:35:03.280> common<00:35:03.640> I 00:35:03.750 --> 00:35:03.760 align:start position:0% basically identifier quite common I 00:35:03.760 --> 00:35:05.230 align:start position:0% basically identifier quite common I think<00:35:04.040> everyone<00:35:04.359> know<00:35:04.520> here<00:35:04.720> knows<00:35:04.960> what<00:35:05.079> a 00:35:05.230 --> 00:35:05.240 align:start position:0% think everyone know here knows what a 00:35:05.240 --> 00:35:08.710 align:start position:0% think everyone know here knows what a public<00:35:05.480> key<00:35:05.839> is<00:35:06.839> uh<00:35:06.960> you<00:35:07.040> can<00:35:07.240> give<00:35:07.520> the<00:35:08.240> um 00:35:08.710 --> 00:35:08.720 align:start position:0% public key is uh you can give the um 00:35:08.720 --> 00:35:11.510 align:start position:0% public key is uh you can give the um valid<00:35:09.040> data<00:35:09.280> key<00:35:09.480> a<00:35:09.760> name<00:35:10.760> uh<00:35:10.880> this<00:35:11.040> name<00:35:11.240> is<00:35:11.440> if 00:35:11.510 --> 00:35:11.520 align:start position:0% valid data key a name uh this name is if 00:35:11.520 --> 00:35:13.430 align:start position:0% valid data key a name uh this name is if you<00:35:11.640> have<00:35:11.800> multiple<00:35:12.200> Friends<00:35:12.920> u<00:35:13.040> you<00:35:13.160> all<00:35:13.320> want 00:35:13.430 --> 00:35:13.440 align:start position:0% you have multiple Friends u you all want 00:35:13.440 --> 00:35:14.750 align:start position:0% you have multiple Friends u you all want to<00:35:13.680> stay<00:35:13.880> on<00:35:14.040> one 00:35:14.750 --> 00:35:14.760 align:start position:0% to stay on one 00:35:14.760 --> 00:35:18.430 align:start position:0% to stay on one note<00:35:15.760> um<00:35:16.040> you<00:35:16.160> can<00:35:17.000> give<00:35:17.280> this<00:35:17.800> give<00:35:18.040> this<00:35:18.240> one 00:35:18.430 --> 00:35:18.440 align:start position:0% note um you can give this give this one 00:35:18.440 --> 00:35:19.790 align:start position:0% note um you can give this give this one name<00:35:18.760> let's<00:35:18.920> say<00:35:19.040> you<00:35:19.119> have<00:35:19.280> two<00:35:19.440> keys<00:35:19.680> you 00:35:19.790 --> 00:35:19.800 align:start position:0% name let's say you have two keys you 00:35:19.800 --> 00:35:23.069 align:start position:0% name let's say you have two keys you give<00:35:20.040> one<00:35:20.880> you<00:35:21.040> can<00:35:21.320> call<00:35:21.640> uh<00:35:21.960> name<00:35:22.240> one<00:35:22.640> like 00:35:23.069 --> 00:35:23.079 align:start position:0% give one you can call uh name one like 00:35:23.079 --> 00:35:24.990 align:start position:0% give one you can call uh name one like your<00:35:23.359> name<00:35:23.599> you<00:35:23.680> can<00:35:23.880> name<00:35:24.160> one<00:35:24.359> the<00:35:24.520> other 00:35:24.990 --> 00:35:25.000 align:start position:0% your name you can name one the other 00:35:25.000 --> 00:35:27.870 align:start position:0% your name you can name one the other it's<00:35:25.200> just<00:35:25.400> like<00:35:25.560> some<00:35:25.800> management<00:35:26.359> options 00:35:27.870 --> 00:35:27.880 align:start position:0% it's just like some management options 00:35:27.880 --> 00:35:30.190 align:start position:0% it's just like some management options you<00:35:28.000> can<00:35:28.160> set<00:35:28.560> a<00:35:28.880> block<00:35:29.200> fee<00:35:29.480> recipient<00:35:29.920> for 00:35:30.190 --> 00:35:30.200 align:start position:0% you can set a block fee recipient for 00:35:30.200 --> 00:35:32.990 align:start position:0% you can set a block fee recipient for individual<00:35:30.800> key<00:35:31.560> there's<00:35:31.800> also<00:35:32.079> the<00:35:32.280> opt<00:35:32.760> uh 00:35:32.990 --> 00:35:33.000 align:start position:0% individual key there's also the opt uh 00:35:33.000 --> 00:35:35.990 align:start position:0% individual key there's also the opt uh usually<00:35:33.480> what<00:35:33.599> you<00:35:33.800> do<00:35:34.040> is<00:35:34.320> um<00:35:34.520> set<00:35:34.720> up<00:35:35.000> a 00:35:35.990 --> 00:35:36.000 align:start position:0% usually what you do is um set up a 00:35:36.000 --> 00:35:40.430 align:start position:0% usually what you do is um set up a default<00:35:36.680> fee<00:35:37.520> recipient<00:35:38.599> uh<00:35:39.599> in<00:35:39.800> the<00:35:40.280> uh 00:35:40.430 --> 00:35:40.440 align:start position:0% default fee recipient uh in the uh 00:35:40.440 --> 00:35:43.990 align:start position:0% default fee recipient uh in the uh validat<00:35:41.000> node<00:35:41.280> client<00:35:42.320> settings<00:35:43.320> uh<00:35:43.480> but<00:35:43.880> if 00:35:43.990 --> 00:35:44.000 align:start position:0% validat node client settings uh but if 00:35:44.000 --> 00:35:45.790 align:start position:0% validat node client settings uh but if you<00:35:44.119> don't<00:35:44.359> want<00:35:44.520> to<00:35:44.680> use<00:35:44.920> this<00:35:45.160> as<00:35:45.240> I<00:35:45.400> said<00:35:45.720> if 00:35:45.790 --> 00:35:45.800 align:start position:0% you don't want to use this as I said if 00:35:45.800 --> 00:35:47.790 align:start position:0% you don't want to use this as I said if you<00:35:45.960> have<00:35:46.160> multiple<00:35:46.599> key<00:35:46.920> maybe<00:35:47.160> you<00:35:47.440> stti 00:35:47.790 --> 00:35:47.800 align:start position:0% you have multiple key maybe you stti 00:35:47.800 --> 00:35:49.710 align:start position:0% you have multiple key maybe you stti with<00:35:47.920> a<00:35:48.040> friend<00:35:48.280> to<00:35:48.440> get<00:35:48.599> on<00:35:48.760> one<00:35:48.920> machine<00:35:49.599> you 00:35:49.710 --> 00:35:49.720 align:start position:0% with a friend to get on one machine you 00:35:49.720 --> 00:35:53.109 align:start position:0% with a friend to get on one machine you can<00:35:49.920> like<00:35:50.079> set<00:35:50.280> it<00:35:50.440> up<00:35:50.640> in<00:35:50.760> a<00:35:50.960> way<00:35:51.760> that<00:35:52.640> uh<00:35:52.760> your 00:35:53.109 --> 00:35:53.119 align:start position:0% can like set it up in a way that uh your 00:35:53.119 --> 00:35:55.430 align:start position:0% can like set it up in a way that uh your block<00:35:53.359> fee<00:35:53.680> recipient<00:35:54.119> for<00:35:54.319> your<00:35:54.560> key<00:35:54.920> so<00:35:55.200> your 00:35:55.430 --> 00:35:55.440 align:start position:0% block fee recipient for your key so your 00:35:55.440 --> 00:35:57.630 align:start position:0% block fee recipient for your key so your block<00:35:56.079> production<00:35:56.560> reward<00:35:56.920> for<00:35:57.079> your<00:35:57.280> key 00:35:57.630 --> 00:35:57.640 align:start position:0% block production reward for your key 00:35:57.640 --> 00:36:00.510 align:start position:0% block production reward for your key sent<00:35:57.839> to<00:35:57.960> your<00:35:58.200> address<00:35:58.920> and<00:35:59.079> the<00:35:59.480> uh<00:35:59.599> block<00:35:59.880> VI 00:36:00.510 --> 00:36:00.520 align:start position:0% sent to your address and the uh block VI 00:36:00.520 --> 00:36:02.510 align:start position:0% sent to your address and the uh block VI reward<00:36:01.000> from<00:36:01.240> the<00:36:01.599> from<00:36:01.760> your<00:36:01.880> friends<00:36:02.280> keys 00:36:02.510 --> 00:36:02.520 align:start position:0% reward from the from your friends keys 00:36:02.520 --> 00:36:04.069 align:start position:0% reward from the from your friends keys to<00:36:02.640> send<00:36:02.839> to<00:36:03.040> their 00:36:04.069 --> 00:36:04.079 align:start position:0% to send to their 00:36:04.079 --> 00:36:06.630 align:start position:0% to send to their address<00:36:05.079> um<00:36:05.440> then<00:36:05.680> you<00:36:05.800> can<00:36:06.000> always<00:36:06.280> remove 00:36:06.630 --> 00:36:06.640 align:start position:0% address um then you can always remove 00:36:06.640 --> 00:36:09.309 align:start position:0% address um then you can always remove the<00:36:06.760> client<00:36:07.400> uh<00:36:07.720> validator<00:36:08.720> always<00:36:09.040> remove 00:36:09.309 --> 00:36:09.319 align:start position:0% the client uh validator always remove 00:36:09.319 --> 00:36:11.790 align:start position:0% the client uh validator always remove the<00:36:09.440> validator<00:36:10.000> key<00:36:10.680> and<00:36:10.800> you<00:36:10.920> can<00:36:11.160> also 00:36:11.790 --> 00:36:11.800 align:start position:0% the validator key and you can also 00:36:11.800 --> 00:36:13.990 align:start position:0% the validator key and you can also easily<00:36:12.160> like<00:36:12.400> accident<00:36:12.920> withdraw<00:36:13.480> just<00:36:13.720> click 00:36:13.990 --> 00:36:14.000 align:start position:0% easily like accident withdraw just click 00:36:14.000 --> 00:36:17.470 align:start position:0% easily like accident withdraw just click this<00:36:14.200> button<00:36:14.920> it<00:36:15.079> sends<00:36:15.440> a<00:36:16.440> it<00:36:16.560> creates<00:36:16.920> a<00:36:17.160> exit 00:36:17.470 --> 00:36:17.480 align:start position:0% this button it sends a it creates a exit 00:36:17.480 --> 00:36:19.990 align:start position:0% this button it sends a it creates a exit message<00:36:18.040> gives<00:36:18.240> it<00:36:18.400> to<00:36:18.599> the<00:36:19.119> consensus<00:36:19.599> client 00:36:19.990 --> 00:36:20.000 align:start position:0% message gives it to the consensus client 00:36:20.000 --> 00:36:21.589 align:start position:0% message gives it to the consensus client consensus<00:36:20.440> client<00:36:20.680> broadcasts<00:36:21.200> it<00:36:21.319> to<00:36:21.440> the 00:36:21.589 --> 00:36:21.599 align:start position:0% consensus client broadcasts it to the 00:36:21.599 --> 00:36:23.309 align:start position:0% consensus client broadcasts it to the network<00:36:21.920> and<00:36:22.040> it's<00:36:22.240> basically<00:36:22.640> it<00:36:23.119> it's 00:36:23.309 --> 00:36:23.319 align:start position:0% network and it's basically it it's 00:36:23.319 --> 00:36:25.790 align:start position:0% network and it's basically it it's already<00:36:23.880> exited<00:36:24.880> uh<00:36:24.960> you<00:36:25.119> then<00:36:25.400> go<00:36:25.560> through 00:36:25.790 --> 00:36:25.800 align:start position:0% already exited uh you then go through 00:36:25.800 --> 00:36:28.670 align:start position:0% already exited uh you then go through the<00:36:26.000> exit<00:36:26.359> queue<00:36:26.880> also<00:36:27.200> takes<00:36:27.720> while<00:36:28.000> so<00:36:28.560> if 00:36:28.670 --> 00:36:28.680 align:start position:0% the exit queue also takes while so if 00:36:28.680 --> 00:36:31.230 align:start position:0% the exit queue also takes while so if you<00:36:28.839> have<00:36:29.119> like<00:36:29.359> huge<00:36:29.680> swings<00:36:30.160> in<00:36:30.359> the<00:36:30.920> value 00:36:31.230 --> 00:36:31.240 align:start position:0% you have like huge swings in the value 00:36:31.240 --> 00:36:33.790 align:start position:0% you have like huge swings in the value or<00:36:31.520> price<00:36:31.720> of<00:36:31.960> Eve<00:36:32.520> you<00:36:32.680> might<00:36:32.880> want<00:36:33.040> to<00:36:33.440> is<00:36:33.599> is 00:36:33.790 --> 00:36:33.800 align:start position:0% or price of Eve you might want to is is 00:36:33.800 --> 00:36:37.870 align:start position:0% or price of Eve you might want to is is hard<00:36:34.040> to<00:36:34.359> like<00:36:35.040> plan<00:36:36.000> aead<00:36:36.440> in<00:36:36.560> this<00:36:36.800> case<00:36:37.200> but 00:36:37.870 --> 00:36:37.880 align:start position:0% hard to like plan aead in this case but 00:36:37.880 --> 00:36:39.550 align:start position:0% hard to like plan aead in this case but uh<00:36:37.960> you<00:36:38.079> won't<00:36:38.319> be<00:36:38.440> able<00:36:38.680> to<00:36:38.920> like<00:36:39.119> instantly 00:36:39.550 --> 00:36:39.560 align:start position:0% uh you won't be able to like instantly 00:36:39.560 --> 00:36:41.069 align:start position:0% uh you won't be able to like instantly sell<00:36:39.800> it<00:36:39.960> or<00:36:40.119> something<00:36:40.440> like<00:36:40.599> this<00:36:40.720> so<00:36:40.880> keep 00:36:41.069 --> 00:36:41.079 align:start position:0% sell it or something like this so keep 00:36:41.079 --> 00:36:43.790 align:start position:0% sell it or something like this so keep this<00:36:41.200> in<00:36:41.319> mind<00:36:41.880> please<00:36:42.880> um<00:36:43.119> you<00:36:43.280> also<00:36:43.480> have<00:36:43.640> the 00:36:43.790 --> 00:36:43.800 align:start position:0% this in mind please um you also have the 00:36:43.800 --> 00:36:45.230 align:start position:0% this in mind please um you also have the option<00:36:44.319> as<00:36:44.400> you<00:36:44.560> said<00:36:44.760> this<00:36:44.880> is<00:36:44.960> for<00:36:45.119> the 00:36:45.230 --> 00:36:45.240 align:start position:0% option as you said this is for the 00:36:45.240 --> 00:36:47.510 align:start position:0% option as you said this is for the individual<00:36:45.839> key<00:36:46.200> you<00:36:46.319> can<00:36:46.480> do<00:36:46.680> the<00:36:46.880> same<00:36:47.200> for 00:36:47.510 --> 00:36:47.520 align:start position:0% individual key you can do the same for 00:36:47.520 --> 00:36:50.790 align:start position:0% individual key you can do the same for the<00:36:47.920> uh<00:36:48.040> whole<00:36:48.400> client<00:36:49.400> so<00:36:49.560> you<00:36:49.680> can<00:36:49.839> set<00:36:50.440> uh<00:36:50.640> a 00:36:50.790 --> 00:36:50.800 align:start position:0% the uh whole client so you can set uh a 00:36:50.800 --> 00:36:53.790 align:start position:0% the uh whole client so you can set uh a blockchain<00:36:51.280> graffi<00:36:52.359> actually<00:36:53.359> uh<00:36:53.440> whenever 00:36:53.790 --> 00:36:53.800 align:start position:0% blockchain graffi actually uh whenever 00:36:53.800 --> 00:36:56.710 align:start position:0% blockchain graffi actually uh whenever your<00:36:54.599> um<00:36:55.160> whenever<00:36:55.440> your<00:36:55.599> note<00:36:56.079> produces<00:36:56.520> a 00:36:56.710 --> 00:36:56.720 align:start position:0% your um whenever your note produces a 00:36:56.720 --> 00:36:59.710 align:start position:0% your um whenever your note produces a block<00:36:57.280> you<00:36:57.640> have<00:36:57.839> the<00:36:58.560> uh<00:36:58.800> option<00:36:59.160> to<00:36:59.560> like 00:36:59.710 --> 00:36:59.720 align:start position:0% block you have the uh option to like 00:36:59.720 --> 00:37:02.030 align:start position:0% block you have the uh option to like include<00:37:00.079> a<00:37:00.200> small<00:37:00.560> M<00:37:00.839> message<00:37:01.160> in<00:37:01.400> there<00:37:01.880> this 00:37:02.030 --> 00:37:02.040 align:start position:0% include a small M message in there this 00:37:02.040 --> 00:37:05.230 align:start position:0% include a small M message in there this could<00:37:02.160> be<00:37:02.800> anything<00:37:03.800> uh<00:37:03.920> it<00:37:04.000> should<00:37:04.200> be<00:37:04.359> up<00:37:04.520> to 00:37:05.230 --> 00:37:05.240 align:start position:0% could be anything uh it should be up to 00:37:05.240 --> 00:37:10.710 align:start position:0% could be anything uh it should be up to 32<00:37:06.240> uh<00:37:06.760> 32<00:37:07.640> key<00:37:08.280> uh<00:37:08.560> 32<00:37:09.400> letters 00:37:10.710 --> 00:37:10.720 align:start position:0% 32 uh 32 key uh 32 letters 00:37:10.720 --> 00:37:13.390 align:start position:0% 32 uh 32 key uh 32 letters actually<00:37:11.720> um<00:37:12.119> in<00:37:12.280> this<00:37:12.520> case<00:37:13.000> we<00:37:13.200> what<00:37:13.280> we 00:37:13.390 --> 00:37:13.400 align:start position:0% actually um in this case we what we 00:37:13.400 --> 00:37:16.190 align:start position:0% actually um in this case we what we usually<00:37:13.760> do<00:37:13.960> is<00:37:14.319> uh<00:37:14.480> set<00:37:15.000> set<00:37:15.240> it<00:37:15.359> as<00:37:15.560> default 00:37:16.190 --> 00:37:16.200 align:start position:0% usually do is uh set set it as default 00:37:16.200 --> 00:37:18.790 align:start position:0% usually do is uh set set it as default st.net<00:37:17.200> it's<00:37:17.400> also<00:37:17.880> basically<00:37:18.319> if<00:37:18.440> you<00:37:18.560> go<00:37:18.680> on 00:37:18.790 --> 00:37:18.800 align:start position:0% st.net it's also basically if you go on 00:37:18.800 --> 00:37:21.030 align:start position:0% st.net it's also basically if you go on pcking<00:37:19.040> chart<00:37:19.240> at<00:37:19.400> the<00:37:19.520> end<00:37:20.319> and<00:37:20.440> you<00:37:20.640> put<00:37:20.800> in 00:37:21.030 --> 00:37:21.040 align:start position:0% pcking chart at the end and you put in 00:37:21.040 --> 00:37:23.710 align:start position:0% pcking chart at the end and you put in like<00:37:21.200> st.net<00:37:22.000> you<00:37:22.079> will<00:37:22.200> see<00:37:22.440> how<00:37:22.560> many<00:37:22.839> blocks 00:37:23.710 --> 00:37:23.720 align:start position:0% like st.net you will see how many blocks 00:37:23.720 --> 00:37:25.069 align:start position:0% like st.net you will see how many blocks what<00:37:23.880> were<00:37:24.079> produced<00:37:24.520> by<00:37:24.640> people<00:37:24.839> who<00:37:24.960> are 00:37:25.069 --> 00:37:25.079 align:start position:0% what were produced by people who are 00:37:25.079 --> 00:37:27.630 align:start position:0% what were produced by people who are using<00:37:25.319> steum<00:37:25.760> and<00:37:25.920> didn't<00:37:26.160> change<00:37:26.599> that<00:37:27.240> as<00:37:27.359> a 00:37:27.630 --> 00:37:27.640 align:start position:0% using steum and didn't change that as a 00:37:27.640 --> 00:37:29.109 align:start position:0% using steum and didn't change that as a said<00:37:27.880> you<00:37:27.960> can<00:37:28.119> change<00:37:28.400> this<00:37:28.560> whenever<00:37:28.839> you 00:37:29.109 --> 00:37:29.119 align:start position:0% said you can change this whenever you 00:37:29.119 --> 00:37:32.150 align:start position:0% said you can change this whenever you want<00:37:30.119> uh<00:37:30.720> it's<00:37:31.000> it's<00:37:31.200> nice<00:37:31.440> for<00:37:31.640> us<00:37:31.839> to<00:37:32.000> have 00:37:32.150 --> 00:37:32.160 align:start position:0% want uh it's it's nice for us to have 00:37:32.160 --> 00:37:34.990 align:start position:0% want uh it's it's nice for us to have like<00:37:32.319> some<00:37:32.640> numbers<00:37:33.319> but<00:37:34.160> uh<00:37:34.280> if<00:37:34.440> you<00:37:34.800> if<00:37:34.880> you 00:37:34.990 --> 00:37:35.000 align:start position:0% like some numbers but uh if you if you 00:37:35.000 --> 00:37:36.630 align:start position:0% like some numbers but uh if you if you just<00:37:35.160> want<00:37:35.319> to<00:37:35.480> like<00:37:35.680> have<00:37:35.800> a<00:37:35.920> fun<00:37:36.160> message<00:37:36.480> in 00:37:36.630 --> 00:37:36.640 align:start position:0% just want to like have a fun message in 00:37:36.640 --> 00:37:40.390 align:start position:0% just want to like have a fun message in that<00:37:36.800> is<00:37:36.960> absolutely<00:37:37.839> fine<00:37:38.839> um<00:37:39.599> also<00:37:40.119> option 00:37:40.390 --> 00:37:40.400 align:start position:0% that is absolutely fine um also option 00:37:40.400 --> 00:37:43.550 align:start position:0% that is absolutely fine um also option to<00:37:40.560> remove<00:37:41.079> for<00:37:41.359> all<00:37:42.000> the<00:37:42.480> every<00:37:42.760> single<00:37:43.359> uh 00:37:43.550 --> 00:37:43.560 align:start position:0% to remove for all the every single uh 00:37:43.560 --> 00:37:46.069 align:start position:0% to remove for all the every single uh valid<00:37:43.839> dat<00:37:44.079> key<00:37:44.319> from<00:37:44.520> the<00:37:44.680> client<00:37:45.599> option<00:37:45.839> to 00:37:46.069 --> 00:37:46.079 align:start position:0% valid dat key from the client option to 00:37:46.079 --> 00:37:48.030 align:start position:0% valid dat key from the client option to withdraw<00:37:46.640> every<00:37:46.839> single<00:37:47.119> valid<00:37:47.440> dat<00:37:47.680> key<00:37:47.880> from 00:37:48.030 --> 00:37:48.040 align:start position:0% withdraw every single valid dat key from 00:37:48.040 --> 00:37:50.190 align:start position:0% withdraw every single valid dat key from the<00:37:48.240> client<00:37:49.240> and<00:37:49.440> as<00:37:49.520> you<00:37:49.640> can<00:37:49.760> see<00:37:49.960> there's 00:37:50.190 --> 00:37:50.200 align:start position:0% the client and as you can see there's 00:37:50.200 --> 00:37:53.510 align:start position:0% the client and as you can see there's also<00:37:50.400> the<00:37:50.560> option<00:37:50.839> to<00:37:51.400> import<00:37:51.760> remote<00:37:52.400> Keys<00:37:53.400> uh 00:37:53.510 --> 00:37:53.520 align:start position:0% also the option to import remote Keys uh 00:37:53.520 --> 00:37:56.510 align:start position:0% also the option to import remote Keys uh we<00:37:53.680> support<00:37:54.119> web<00:37:54.280> free<00:37:54.599> signer<00:37:55.440> um<00:37:55.680> I<00:37:55.800> can<00:37:56.079> say 00:37:56.510 --> 00:37:56.520 align:start position:0% we support web free signer um I can say 00:37:56.520 --> 00:37:58.550 align:start position:0% we support web free signer um I can say personally<00:37:57.000> I<00:37:57.119> don't<00:37:57.560> use<00:37:57.760> it<00:37:58.119> and<00:37:58.280> I<00:37:58.400> don't 00:37:58.550 --> 00:37:58.560 align:start position:0% personally I don't use it and I don't 00:37:58.560 --> 00:38:01.150 align:start position:0% personally I don't use it and I don't think<00:37:58.760> anyone<00:37:59.079> of<00:37:59.240> us<00:37:59.440> uses<00:37:59.800> it<00:38:00.720> uh<00:38:00.880> because 00:38:01.150 --> 00:38:01.160 align:start position:0% think anyone of us uses it uh because 00:38:01.160 --> 00:38:03.150 align:start position:0% think anyone of us uses it uh because with<00:38:01.359> this<00:38:01.599> it's<00:38:02.040> uh<00:38:02.400> basically<00:38:02.880> really 00:38:03.150 --> 00:38:03.160 align:start position:0% with this it's uh basically really 00:38:03.160 --> 00:38:07.270 align:start position:0% with this it's uh basically really really<00:38:03.760> easy<00:38:04.760> uh<00:38:04.880> to<00:38:05.160> switch<00:38:05.760> the<00:38:06.560> uh<00:38:06.839> switch 00:38:07.270 --> 00:38:07.280 align:start position:0% really easy uh to switch the uh switch 00:38:07.280 --> 00:38:10.309 align:start position:0% really easy uh to switch the uh switch between<00:38:08.359> the<00:38:09.359> switch<00:38:09.680> between<00:38:09.920> the<00:38:10.040> client 00:38:10.309 --> 00:38:10.319 align:start position:0% between the switch between the client 00:38:10.319 --> 00:38:12.510 align:start position:0% between the switch between the client pairs<00:38:10.680> anyway<00:38:11.480> what<00:38:11.640> people<00:38:11.880> usually<00:38:12.160> use<00:38:12.400> the 00:38:12.510 --> 00:38:12.520 align:start position:0% pairs anyway what people usually use the 00:38:12.520 --> 00:38:14.710 align:start position:0% pairs anyway what people usually use the web<00:38:12.680> resigner<00:38:13.160> for<00:38:13.319> is<00:38:13.520> like<00:38:14.160> they<00:38:14.319> use<00:38:14.560> this 00:38:14.710 --> 00:38:14.720 align:start position:0% web resigner for is like they use this 00:38:14.720 --> 00:38:17.309 align:start position:0% web resigner for is like they use this as<00:38:14.839> a<00:38:15.200> extra<00:38:15.480> layer<00:38:15.800> so<00:38:15.960> they<00:38:16.119> can<00:38:16.319> import<00:38:17.119> uh 00:38:17.309 --> 00:38:17.319 align:start position:0% as a extra layer so they can import uh 00:38:17.319 --> 00:38:20.069 align:start position:0% as a extra layer so they can import uh switch<00:38:17.760> the<00:38:18.319> import<00:38:18.760> the<00:38:19.000> keys<00:38:19.680> into<00:38:19.920> the 00:38:20.069 --> 00:38:20.079 align:start position:0% switch the import the keys into the 00:38:20.079 --> 00:38:23.270 align:start position:0% switch the import the keys into the validator<00:38:20.599> CL<00:38:20.839> and<00:38:20.960> it's<00:38:21.160> just<00:38:21.319> switch<00:38:21.640> it<00:38:22.280> up 00:38:23.270 --> 00:38:23.280 align:start position:0% validator CL and it's just switch it up 00:38:23.280 --> 00:38:24.950 align:start position:0% validator CL and it's just switch it up uh<00:38:23.480> but<00:38:23.720> if<00:38:23.800> you<00:38:23.920> want<00:38:24.040> to<00:38:24.200> do<00:38:24.400> this<00:38:24.560> it's<00:38:24.760> just 00:38:24.950 --> 00:38:24.960 align:start position:0% uh but if you want to do this it's just 00:38:24.960 --> 00:38:28.270 align:start position:0% uh but if you want to do this it's just C<00:38:25.280> click<00:38:26.079> you<00:38:27.079> can<00:38:27.200> show 00:38:28.270 --> 00:38:28.280 align:start position:0% C click you can show 00:38:28.280 --> 00:38:31.550 align:start position:0% C click you can show of<00:38:29.280> just<00:38:29.440> a<00:38:29.640> click<00:38:30.280> you<00:38:30.400> can<00:38:30.599> do<00:38:30.800> a<00:38:31.000> local<00:38:31.319> one 00:38:31.550 --> 00:38:31.560 align:start position:0% of just a click you can do a local one 00:38:31.560 --> 00:38:33.230 align:start position:0% of just a click you can do a local one you<00:38:31.640> can<00:38:31.800> also<00:38:32.079> like<00:38:32.240> choose<00:38:32.440> an<00:38:32.640> external<00:38:33.040> one 00:38:33.230 --> 00:38:33.240 align:start position:0% you can also like choose an external one 00:38:33.240 --> 00:38:35.270 align:start position:0% you can also like choose an external one if<00:38:33.359> you<00:38:33.480> want<00:38:33.680> to<00:38:34.319> so<00:38:34.560> if<00:38:34.640> you<00:38:34.760> have<00:38:34.960> the<00:38:35.079> web 00:38:35.270 --> 00:38:35.280 align:start position:0% if you want to so if you have the web 00:38:35.280 --> 00:38:38.069 align:start position:0% if you want to so if you have the web fre<00:38:35.520> and<00:38:35.680> an<00:38:35.839> extra<00:38:36.160> machine<00:38:36.520> you<00:38:36.640> can<00:38:36.880> just<00:38:37.880> uh 00:38:38.069 --> 00:38:38.079 align:start position:0% fre and an extra machine you can just uh 00:38:38.079 --> 00:38:39.710 align:start position:0% fre and an extra machine you can just uh put<00:38:38.240> in<00:38:38.440> the<00:38:39.000> uh 00:38:39.710 --> 00:38:39.720 align:start position:0% put in the uh 00:38:39.720 --> 00:38:43.990 align:start position:0% put in the uh UL<00:38:40.720> uh<00:38:41.560> to<00:38:41.839> the<00:38:42.119> to<00:38:42.280> the<00:38:42.400> machine<00:38:42.880> itself<00:38:43.880> on 00:38:43.990 --> 00:38:44.000 align:start position:0% UL uh to the to the machine itself on 00:38:44.000 --> 00:38:46.270 align:start position:0% UL uh to the to the machine itself on the<00:38:44.200> right<00:38:44.400> side<00:38:44.640> you<00:38:44.839> see<00:38:45.040> a<00:38:45.160> little<00:38:45.400> bit<00:38:45.640> of 00:38:46.270 --> 00:38:46.280 align:start position:0% the right side you see a little bit of 00:38:46.280 --> 00:38:49.710 align:start position:0% the right side you see a little bit of uh<00:38:47.280> some<00:38:47.520> stats<00:38:48.480> as<00:38:48.599> you<00:38:48.720> can<00:38:48.920> see<00:38:49.240> you<00:38:49.319> can<00:38:49.480> see 00:38:49.710 --> 00:38:49.720 align:start position:0% uh some stats as you can see you can see 00:38:49.720 --> 00:38:53.390 align:start position:0% uh some stats as you can see you can see the<00:38:50.359> eepo<00:38:51.359> you<00:38:51.520> can<00:38:51.680> see<00:38:51.920> the<00:38:52.119> slots<00:38:53.119> uh<00:38:53.280> the 00:38:53.390 --> 00:38:53.400 align:start position:0% the eepo you can see the slots uh the 00:38:53.400 --> 00:38:56.150 align:start position:0% the eepo you can see the slots uh the curent<00:38:53.760> slots<00:38:54.720> on<00:38:54.880> the<00:38:55.040> bottom<00:38:55.560> if<00:38:55.720> you<00:38:55.880> would 00:38:56.150 --> 00:38:56.160 align:start position:0% curent slots on the bottom if you would 00:38:56.160 --> 00:38:58.109 align:start position:0% curent slots on the bottom if you would get<00:38:56.440> a<00:38:57.000> uh<00:38:57.079> if<00:38:57.160> you<00:38:57.280> would<00:38:57.440> would<00:38:57.599> be<00:38:57.800> part<00:38:58.000> of 00:38:58.109 --> 00:38:58.119 align:start position:0% get a uh if you would would be part of 00:38:58.119 --> 00:38:59.950 align:start position:0% get a uh if you would would be part of the<00:38:58.200> syc<00:38:58.560> committee<00:38:59.119> or<00:38:59.280> you<00:38:59.359> would<00:38:59.560> be<00:38:59.760> part 00:38:59.950 --> 00:38:59.960 align:start position:0% the syc committee or you would be part 00:38:59.960 --> 00:39:02.230 align:start position:0% the syc committee or you would be part of<00:39:00.200> the<00:39:00.960> or<00:39:01.240> the<00:39:01.400> blog 00:39:02.230 --> 00:39:02.240 align:start position:0% of the or the blog 00:39:02.240 --> 00:39:05.470 align:start position:0% of the or the blog production<00:39:03.240> uh<00:39:03.359> is<00:39:03.640> like<00:39:04.119> um<00:39:04.880> going<00:39:05.119> to<00:39:05.240> be 00:39:05.470 --> 00:39:05.480 align:start position:0% production uh is like um going to be 00:39:05.480 --> 00:39:07.710 align:start position:0% production uh is like um going to be soon<00:39:05.800> you<00:39:05.920> will<00:39:06.119> see<00:39:06.359> this<00:39:06.560> on<00:39:06.800> here<00:39:07.079> this<00:39:07.160> is 00:39:07.710 --> 00:39:07.720 align:start position:0% soon you will see this on here this is 00:39:07.720 --> 00:39:10.069 align:start position:0% soon you will see this on here this is basically<00:39:08.720> uh<00:39:08.920> like<00:39:09.040> an<00:39:09.200> extra<00:39:09.560> help<00:39:09.760> for<00:39:09.920> you 00:39:10.069 --> 00:39:10.079 align:start position:0% basically uh like an extra help for you 00:39:10.079 --> 00:39:12.150 align:start position:0% basically uh like an extra help for you to<00:39:10.240> know<00:39:10.480> when<00:39:10.680> you<00:39:10.920> have<00:39:11.040> to<00:39:11.160> do<00:39:11.440> updates 00:39:12.150 --> 00:39:12.160 align:start position:0% to know when you have to do updates 00:39:12.160 --> 00:39:14.750 align:start position:0% to know when you have to do updates because<00:39:13.160> uh<00:39:13.280> block<00:39:13.599> production<00:39:14.040> is<00:39:14.359> kind<00:39:14.560> of 00:39:14.750 --> 00:39:14.760 align:start position:0% because uh block production is kind of 00:39:14.760 --> 00:39:18.870 align:start position:0% because uh block production is kind of rare<00:39:15.280> it's<00:39:15.960> basically<00:39:16.960> uh<00:39:17.440> once<00:39:18.440> the<00:39:18.599> chance 00:39:18.870 --> 00:39:18.880 align:start position:0% rare it's basically uh once the chance 00:39:18.880 --> 00:39:22.990 align:start position:0% rare it's basically uh once the chance to<00:39:19.040> do<00:39:19.200> this<00:39:19.359> is<00:39:19.599> one<00:39:20.040> in<00:39:20.359> 150<00:39:21.240> days<00:39:22.240> so<00:39:22.720> uh<00:39:22.839> you 00:39:22.990 --> 00:39:23.000 align:start position:0% to do this is one in 150 days so uh you 00:39:23.000 --> 00:39:25.990 align:start position:0% to do this is one in 150 days so uh you get<00:39:23.319> it<00:39:24.040> on<00:39:24.240> average<00:39:24.640> twice<00:39:24.920> a<00:39:25.119> year<00:39:25.760> some 00:39:25.990 --> 00:39:26.000 align:start position:0% get it on average twice a year some 00:39:26.000 --> 00:39:27.670 align:start position:0% get it on average twice a year some people<00:39:26.200> are<00:39:26.359> more<00:39:26.599> lucky<00:39:27.000> some<00:39:27.359> people<00:39:27.520> are 00:39:27.670 --> 00:39:27.680 align:start position:0% people are more lucky some people are 00:39:27.680 --> 00:39:30.230 align:start position:0% people are more lucky some people are less<00:39:27.920> lucky<00:39:28.640> it's<00:39:28.880> basically<00:39:29.240> a<00:39:29.520> lottery<00:39:30.000> on 00:39:30.230 --> 00:39:30.240 align:start position:0% less lucky it's basically a lottery on 00:39:30.240 --> 00:39:32.950 align:start position:0% less lucky it's basically a lottery on top<00:39:30.400> of<00:39:30.520> the<00:39:30.680> attestation<00:39:31.240> rewards<00:39:31.640> you<00:39:31.800> get 00:39:32.950 --> 00:39:32.960 align:start position:0% top of the attestation rewards you get 00:39:32.960 --> 00:39:36.150 align:start position:0% top of the attestation rewards you get anyway<00:39:33.960> so<00:39:34.599> um<00:39:34.800> you<00:39:34.920> also<00:39:35.119> have<00:39:35.240> the<00:39:35.440> option<00:39:35.680> to 00:39:36.150 --> 00:39:36.160 align:start position:0% anyway so um you also have the option to 00:39:36.160 --> 00:39:38.230 align:start position:0% anyway so um you also have the option to uh<00:39:36.280> group<00:39:36.640> these<00:39:36.920> so<00:39:37.119> if<00:39:37.240> you<00:39:37.359> have<00:39:37.599> like<00:39:37.960> as<00:39:38.079> I 00:39:38.230 --> 00:39:38.240 align:start position:0% uh group these so if you have like as I 00:39:38.240 --> 00:39:39.630 align:start position:0% uh group these so if you have like as I said<00:39:38.440> if<00:39:38.560> you<00:39:38.640> have<00:39:38.800> friends<00:39:39.200> or<00:39:39.359> you<00:39:39.480> have 00:39:39.630 --> 00:39:39.640 align:start position:0% said if you have friends or you have 00:39:39.640 --> 00:39:41.829 align:start position:0% said if you have friends or you have multiple<00:39:40.520> or<00:39:40.640> you<00:39:40.800> do<00:39:41.000> some<00:39:41.200> staking<00:39:41.640> for 00:39:41.829 --> 00:39:41.839 align:start position:0% multiple or you do some staking for 00:39:41.839 --> 00:39:43.870 align:start position:0% multiple or you do some staking for other<00:39:42.119> people<00:39:42.520> you<00:39:42.640> can<00:39:42.839> group<00:39:43.119> their<00:39:43.400> keys<00:39:43.720> as 00:39:43.870 --> 00:39:43.880 align:start position:0% other people you can group their keys as 00:39:43.880 --> 00:39:46.309 align:start position:0% other people you can group their keys as well<00:39:44.520> it<00:39:44.640> would<00:39:44.880> basically<00:39:45.319> click<00:39:45.680> here<00:39:45.960> then 00:39:46.309 --> 00:39:46.319 align:start position:0% well it would basically click here then 00:39:46.319 --> 00:39:50.270 align:start position:0% well it would basically click here then click<00:39:47.040> here<00:39:48.040> uh<00:39:48.160> you<00:39:48.240> can<00:39:48.400> filter<00:39:48.839> the<00:39:49.280> clients 00:39:50.270 --> 00:39:50.280 align:start position:0% click here uh you can filter the clients 00:39:50.280 --> 00:39:53.230 align:start position:0% click here uh you can filter the clients uh<00:39:50.720> this<00:39:50.920> works<00:39:51.200> with<00:39:51.520> public<00:39:51.880> keys<00:39:52.160> and<00:39:52.760> uh 00:39:53.230 --> 00:39:53.240 align:start position:0% uh this works with public keys and uh 00:39:53.240 --> 00:39:55.950 align:start position:0% uh this works with public keys and uh the<00:39:53.400> names<00:39:53.680> you<00:39:53.839> can<00:39:54.000> set<00:39:54.839> and<00:39:54.960> you<00:39:55.079> can<00:39:55.319> also 00:39:55.950 --> 00:39:55.960 align:start position:0% the names you can set and you can also 00:39:55.960 --> 00:39:58.030 align:start position:0% the names you can set and you can also uh<00:39:56.119> just<00:39:56.440> switch<00:39:56.839> between<00:39:57.200> the 00:39:58.030 --> 00:39:58.040 align:start position:0% uh just switch between the 00:39:58.040 --> 00:40:02.670 align:start position:0% uh just switch between the showing<00:39:58.440> the<00:39:58.720> names<00:39:59.160> and<00:39:59.520> the<00:39:59.920> public<00:40:00.760> keys<00:40:01.760> so 00:40:02.670 --> 00:40:02.680 align:start position:0% showing the names and the public keys so 00:40:02.680 --> 00:40:04.309 align:start position:0% showing the names and the public keys so um<00:40:03.240> now<00:40:03.359> we're<00:40:03.520> going<00:40:03.599> to<00:40:03.760> go<00:40:03.920> a<00:40:04.000> little<00:40:04.160> bit 00:40:04.309 --> 00:40:04.319 align:start position:0% um now we're going to go a little bit 00:40:04.319 --> 00:40:06.150 align:start position:0% um now we're going to go a little bit into<00:40:04.520> the<00:40:04.640> note<00:40:04.920> page<00:40:05.560> it's<00:40:05.760> probably<00:40:06.079> a 00:40:06.150 --> 00:40:06.160 align:start position:0% into the note page it's probably a 00:40:06.160 --> 00:40:09.390 align:start position:0% into the note page it's probably a little<00:40:06.359> bit<00:40:06.520> more<00:40:07.040> exciting<00:40:08.040> uh<00:40:08.240> steum<00:40:09.240> uh 00:40:09.390 --> 00:40:09.400 align:start position:0% little bit more exciting uh steum uh 00:40:09.400 --> 00:40:11.910 align:start position:0% little bit more exciting uh steum uh supports<00:40:10.079> you<00:40:10.400> having<00:40:10.800> actually<00:40:11.240> multiple 00:40:11.910 --> 00:40:11.920 align:start position:0% supports you having actually multiple 00:40:11.920 --> 00:40:15.550 align:start position:0% supports you having actually multiple configs<00:40:12.440> at<00:40:12.680> once<00:40:13.520> or<00:40:13.800> how<00:40:13.960> we<00:40:14.119> call<00:40:14.319> them<00:40:14.480> is 00:40:15.550 --> 00:40:15.560 align:start position:0% configs at once or how we call them is 00:40:15.560 --> 00:40:18.390 align:start position:0% configs at once or how we call them is setups<00:40:16.560> uh<00:40:16.680> meaning<00:40:17.040> you<00:40:17.240> could<00:40:17.640> in<00:40:17.880> theory 00:40:18.390 --> 00:40:18.400 align:start position:0% setups uh meaning you could in theory 00:40:18.400 --> 00:40:21.230 align:start position:0% setups uh meaning you could in theory run<00:40:18.880> a<00:40:19.560> heski<00:40:20.040> note<00:40:20.240> and<00:40:20.319> a<00:40:20.400> main<00:40:20.800> node<00:40:21.040> on<00:40:21.119> the 00:40:21.230 --> 00:40:21.240 align:start position:0% run a heski note and a main node on the 00:40:21.240 --> 00:40:23.230 align:start position:0% run a heski note and a main node on the same<00:40:21.520> machine<00:40:22.000> given<00:40:22.520> your<00:40:22.680> machine<00:40:22.960> is 00:40:23.230 --> 00:40:23.240 align:start position:0% same machine given your machine is 00:40:23.240 --> 00:40:25.550 align:start position:0% same machine given your machine is strong<00:40:23.440> enough<00:40:24.280> they<00:40:24.640> obviously<00:40:25.040> need<00:40:25.280> still 00:40:25.550 --> 00:40:25.560 align:start position:0% strong enough they obviously need still 00:40:25.560 --> 00:40:27.990 align:start position:0% strong enough they obviously need still the<00:40:25.760> resources<00:40:26.319> they<00:40:26.480> need 00:40:27.990 --> 00:40:28.000 align:start position:0% the resources they need 00:40:28.000 --> 00:40:30.510 align:start position:0% the resources they need um<00:40:28.560> in<00:40:28.720> this<00:40:28.920> case<00:40:29.160> we<00:40:29.319> only<00:40:29.480> have<00:40:29.680> one<00:40:29.880> setup 00:40:30.510 --> 00:40:30.520 align:start position:0% um in this case we only have one setup 00:40:30.520 --> 00:40:32.990 align:start position:0% um in this case we only have one setup they<00:40:30.680> we<00:40:30.839> just<00:40:31.000> set<00:40:31.240> up<00:40:32.040> it's<00:40:32.240> basically<00:40:32.640> setup 00:40:32.990 --> 00:40:33.000 align:start position:0% they we just set up it's basically setup 00:40:33.000 --> 00:40:35.430 align:start position:0% they we just set up it's basically setup one<00:40:33.359> where<00:40:33.520> we<00:40:33.640> can<00:40:33.800> go<00:40:34.000> in<00:40:34.560> you<00:40:34.720> see<00:40:34.960> the<00:40:35.280> free 00:40:35.430 --> 00:40:35.440 align:start position:0% one where we can go in you see the free 00:40:35.440 --> 00:40:38.589 align:start position:0% one where we can go in you see the free client<00:40:35.960> pairs<00:40:36.960> uh<00:40:37.119> baso<00:40:37.440> is<00:40:37.599> already<00:40:37.880> syncing 00:40:38.589 --> 00:40:38.599 align:start position:0% client pairs uh baso is already syncing 00:40:38.599 --> 00:40:40.710 align:start position:0% client pairs uh baso is already syncing Lota<00:40:39.280> is<00:40:39.760> already<00:40:40.040> synced<00:40:40.480> with<00:40:40.599> the 00:40:40.710 --> 00:40:40.720 align:start position:0% Lota is already synced with the 00:40:40.720 --> 00:40:44.069 align:start position:0% Lota is already synced with the checkpoint<00:40:41.480> sync<00:40:42.480> um<00:40:42.720> and<00:40:42.920> you<00:40:43.319> can<00:40:43.480> see<00:40:43.760> also 00:40:44.069 --> 00:40:44.079 align:start position:0% checkpoint sync um and you can see also 00:40:44.079 --> 00:40:47.950 align:start position:0% checkpoint sync um and you can see also like<00:40:44.280> the<00:40:44.520> VC<00:40:45.000> has<00:40:45.280> here<00:40:45.680> it's<00:40:45.839> one<00:40:46.480> key<00:40:47.480> um 00:40:47.950 --> 00:40:47.960 align:start position:0% like the VC has here it's one key um 00:40:47.960 --> 00:40:50.430 align:start position:0% like the VC has here it's one key um what<00:40:48.079> you<00:40:48.280> usually<00:40:48.599> would<00:40:48.839> do<00:40:49.280> after<00:40:50.040> um<00:40:50.200> going 00:40:50.430 --> 00:40:50.440 align:start position:0% what you usually would do after um going 00:40:50.440 --> 00:40:53.069 align:start position:0% what you usually would do after um going through<00:40:50.839> the<00:40:51.839> going<00:40:52.079> through<00:40:52.280> the<00:40:52.440> setup<00:40:52.800> is 00:40:53.069 --> 00:40:53.079 align:start position:0% through the going through the setup is 00:40:53.079 --> 00:40:56.710 align:start position:0% through the going through the setup is also<00:40:53.359> set<00:40:53.599> up<00:40:54.000> a<00:40:55.000> uh<00:40:55.319> default<00:40:55.680> fee<00:40:55.960> recipient 00:40:56.710 --> 00:40:56.720 align:start position:0% also set up a uh default fee recipient 00:40:56.720 --> 00:40:58.910 align:start position:0% also set up a uh default fee recipient because<00:40:56.920> you<00:40:57.079> need<00:40:57.520> this<00:40:58.040> if<00:40:58.160> you<00:40:58.359> don't<00:40:58.640> set 00:40:58.910 --> 00:40:58.920 align:start position:0% because you need this if you don't set 00:40:58.920 --> 00:41:01.109 align:start position:0% because you need this if you don't set the<00:40:59.119> default<00:40:59.520> fee<00:40:59.880> recipient<00:41:00.839> and<00:41:00.960> you 00:41:01.109 --> 00:41:01.119 align:start position:0% the default fee recipient and you 00:41:01.119 --> 00:41:03.870 align:start position:0% the default fee recipient and you produce<00:41:01.480> a<00:41:01.880> block<00:41:02.880> uh<00:41:02.960> you're<00:41:03.079> going<00:41:03.200> to<00:41:03.520> burn 00:41:03.870 --> 00:41:03.880 align:start position:0% produce a block uh you're going to burn 00:41:03.880 --> 00:41:05.910 align:start position:0% produce a block uh you're going to burn your<00:41:04.240> block<00:41:04.520> reward<00:41:04.960> basically<00:41:05.640> which<00:41:05.800> is 00:41:05.910 --> 00:41:05.920 align:start position:0% your block reward basically which is 00:41:05.920 --> 00:41:08.790 align:start position:0% your block reward basically which is nice<00:41:06.119> for<00:41:06.319> everyone<00:41:06.760> else<00:41:07.760> like<00:41:08.200> happy<00:41:08.520> about 00:41:08.790 --> 00:41:08.800 align:start position:0% nice for everyone else like happy about 00:41:08.800 --> 00:41:11.270 align:start position:0% nice for everyone else like happy about like<00:41:08.920> losing<00:41:09.240> some<00:41:09.480> Eve<00:41:09.680> in<00:41:09.800> the<00:41:10.000> network<00:41:11.000> but 00:41:11.270 --> 00:41:11.280 align:start position:0% like losing some Eve in the network but 00:41:11.280 --> 00:41:13.430 align:start position:0% like losing some Eve in the network but uh<00:41:11.400> for<00:41:11.599> yourself<00:41:11.960> you're<00:41:12.160> going<00:41:12.280> to<00:41:12.520> like<00:41:13.200> uh 00:41:13.430 --> 00:41:13.440 align:start position:0% uh for yourself you're going to like uh 00:41:13.440 --> 00:41:15.270 align:start position:0% uh for yourself you're going to like uh bite<00:41:13.680> yourself<00:41:13.960> in<00:41:14.119> the<00:41:14.319> ass<00:41:14.720> basically 00:41:15.270 --> 00:41:15.280 align:start position:0% bite yourself in the ass basically 00:41:15.280 --> 00:41:18.069 align:start position:0% bite yourself in the ass basically because<00:41:15.640> as<00:41:15.760> I<00:41:15.880> said<00:41:16.160> one<00:41:16.319> in<00:41:16.520> 150<00:41:17.359> days 00:41:18.069 --> 00:41:18.079 align:start position:0% because as I said one in 150 days 00:41:18.079 --> 00:41:19.670 align:start position:0% because as I said one in 150 days especially<00:41:18.440> if<00:41:18.560> you<00:41:18.680> use<00:41:18.920> meth<00:41:19.240> boost<00:41:19.520> this 00:41:19.670 --> 00:41:19.680 align:start position:0% especially if you use meth boost this 00:41:19.680 --> 00:41:22.750 align:start position:0% especially if you use meth boost this could<00:41:19.920> be<00:41:20.240> quite<00:41:20.520> some<00:41:21.000> money<00:41:22.000> uh<00:41:22.440> we<00:41:22.640> we 00:41:22.750 --> 00:41:22.760 align:start position:0% could be quite some money uh we we 00:41:22.760 --> 00:41:24.829 align:start position:0% could be quite some money uh we we ourselves<00:41:23.280> like<00:41:23.480> produce<00:41:23.880> blocks<00:41:24.520> um<00:41:24.720> there 00:41:24.829 --> 00:41:24.839 align:start position:0% ourselves like produce blocks um there 00:41:24.839 --> 00:41:27.829 align:start position:0% ourselves like produce blocks um there are<00:41:25.000> like<00:41:25.359> multiple<00:41:25.960> hundreds<00:41:26.359> of<00:41:26.560> E 00:41:27.829 --> 00:41:27.839 align:start position:0% are like multiple hundreds of E 00:41:27.839 --> 00:41:30.270 align:start position:0% are like multiple hundreds of E obviously<00:41:28.839> usually<00:41:29.359> just<00:41:29.640> happens<00:41:29.960> when<00:41:30.160> we 00:41:30.270 --> 00:41:30.280 align:start position:0% obviously usually just happens when we 00:41:30.280 --> 00:41:32.430 align:start position:0% obviously usually just happens when we have<00:41:30.520> like<00:41:30.640> a<00:41:30.839> hack<00:41:31.079> on<00:41:31.200> the<00:41:31.359> network<00:41:31.839> and<00:41:32.000> some 00:41:32.430 --> 00:41:32.440 align:start position:0% have like a hack on the network and some 00:41:32.440 --> 00:41:34.950 align:start position:0% have like a hack on the network and some some<00:41:32.640> hacker<00:41:32.920> sends<00:41:33.240> it<00:41:33.480> like<00:41:33.720> as<00:41:34.280> uh<00:41:34.560> as<00:41:34.720> fast 00:41:34.950 --> 00:41:34.960 align:start position:0% some hacker sends it like as uh as fast 00:41:34.960 --> 00:41:37.030 align:start position:0% some hacker sends it like as uh as fast as<00:41:35.079> you<00:41:35.280> can<00:41:36.040> it<00:41:36.160> doesn't<00:41:36.440> care<00:41:36.680> about<00:41:36.880> the 00:41:37.030 --> 00:41:37.040 align:start position:0% as you can it doesn't care about the 00:41:37.040 --> 00:41:40.710 align:start position:0% as you can it doesn't care about the priority<00:41:37.520> Fe<00:41:37.800> at<00:41:38.079> all<00:41:39.359> um<00:41:40.359> you<00:41:40.480> would 00:41:40.710 --> 00:41:40.720 align:start position:0% priority Fe at all um you would 00:41:40.720 --> 00:41:42.589 align:start position:0% priority Fe at all um you would basically<00:41:41.160> get<00:41:41.440> this<00:41:41.680> if<00:41:41.800> you<00:41:41.920> send<00:41:42.160> it<00:41:42.359> back 00:41:42.589 --> 00:41:42.599 align:start position:0% basically get this if you send it back 00:41:42.599 --> 00:41:44.790 align:start position:0% basically get this if you send it back that's<00:41:42.880> like<00:41:43.520> I<00:41:43.680> guess<00:41:43.880> your<00:41:44.160> decision<00:41:44.640> I 00:41:44.790 --> 00:41:44.800 align:start position:0% that's like I guess your decision I 00:41:44.800 --> 00:41:47.710 align:start position:0% that's like I guess your decision I never<00:41:45.079> like<00:41:45.599> got<00:41:45.760> the<00:41:45.960> process<00:41:46.400> quite<00:41:47.280> but<00:41:47.599> uh 00:41:47.710 --> 00:41:47.720 align:start position:0% never like got the process quite but uh 00:41:47.720 --> 00:41:50.069 align:start position:0% never like got the process quite but uh what<00:41:47.839> you<00:41:47.960> would<00:41:48.119> do<00:41:48.319> is<00:41:48.480> you<00:41:48.599> would<00:41:48.800> go<00:41:48.960> in 00:41:50.069 --> 00:41:50.079 align:start position:0% what you would do is you would go in 00:41:50.079 --> 00:41:53.430 align:start position:0% what you would do is you would go in here<00:41:51.079> uh<00:41:51.319> you<00:41:51.440> see<00:41:51.839> you<00:41:52.040> see<00:41:52.280> here<00:41:52.920> uh<00:41:53.119> default 00:41:53.430 --> 00:41:53.440 align:start position:0% here uh you see you see here uh default 00:41:53.440 --> 00:41:55.349 align:start position:0% here uh you see you see here uh default fee<00:41:53.720> recipient<00:41:54.240> you<00:41:54.319> would<00:41:54.560> just<00:41:54.839> replace 00:41:55.349 --> 00:41:55.359 align:start position:0% fee recipient you would just replace 00:41:55.359 --> 00:41:59.309 align:start position:0% fee recipient you would just replace this<00:41:55.839> uh<00:41:56.280> Ox<00:41:56.680> o<00:41:57.720> address<00:41:58.720> uh<00:41:58.880> then<00:41:59.000> you<00:41:59.079> would 00:41:59.309 --> 00:41:59.319 align:start position:0% this uh Ox o address uh then you would 00:41:59.319 --> 00:42:02.270 align:start position:0% this uh Ox o address uh then you would confirm<00:41:59.680> and<00:42:00.160> restart<00:42:01.160> you<00:42:01.319> can<00:42:01.520> see<00:42:02.000> uh<00:42:02.160> we 00:42:02.270 --> 00:42:02.280 align:start position:0% confirm and restart you can see uh we 00:42:02.280 --> 00:42:04.109 align:start position:0% confirm and restart you can see uh we can<00:42:02.400> set<00:42:02.599> the<00:42:02.800> gas<00:42:03.040> limit<00:42:03.359> here<00:42:03.560> this<00:42:03.760> actually 00:42:04.109 --> 00:42:04.119 align:start position:0% can set the gas limit here this actually 00:42:04.119 --> 00:42:06.589 align:start position:0% can set the gas limit here this actually important<00:42:04.920> the<00:42:05.160> C<00:42:05.520> discussion<00:42:05.960> like<00:42:06.160> to<00:42:06.319> set 00:42:06.589 --> 00:42:06.599 align:start position:0% important the C discussion like to set 00:42:06.599 --> 00:42:10.430 align:start position:0% important the C discussion like to set this<00:42:06.839> higher<00:42:07.079> and<00:42:07.520> lower<00:42:09.000> um<00:42:10.000> then<00:42:10.160> we<00:42:10.280> have 00:42:10.430 --> 00:42:10.440 align:start position:0% this higher and lower um then we have 00:42:10.440 --> 00:42:12.750 align:start position:0% this higher and lower um then we have the<00:42:10.599> doubleganger<00:42:11.240> protection<00:42:12.040> as<00:42:12.160> I<00:42:12.359> said 00:42:12.750 --> 00:42:12.760 align:start position:0% the doubleganger protection as I said 00:42:12.760 --> 00:42:14.349 align:start position:0% the doubleganger protection as I said the<00:42:12.880> double<00:42:13.160> ganger<00:42:13.480> protection<00:42:13.800> is<00:42:13.960> supposed 00:42:14.349 --> 00:42:14.359 align:start position:0% the double ganger protection is supposed 00:42:14.359 --> 00:42:17.510 align:start position:0% the double ganger protection is supposed to<00:42:14.560> protect<00:42:14.920> you<00:42:15.160> from<00:42:16.000> slashing<00:42:16.560> yourself<00:42:17.240> as 00:42:17.510 --> 00:42:17.520 align:start position:0% to protect you from slashing yourself as 00:42:17.520 --> 00:42:19.230 align:start position:0% to protect you from slashing yourself as getting<00:42:17.839> slashed<00:42:18.280> through<00:42:18.520> the<00:42:18.680> keys<00:42:18.960> it's 00:42:19.230 --> 00:42:19.240 align:start position:0% getting slashed through the keys it's 00:42:19.240 --> 00:42:21.030 align:start position:0% getting slashed through the keys it's like<00:42:19.400> just<00:42:19.559> an<00:42:19.720> extra<00:42:20.040> layer<00:42:20.640> if<00:42:20.760> you<00:42:20.839> would 00:42:21.030 --> 00:42:21.040 align:start position:0% like just an extra layer if you would 00:42:21.040 --> 00:42:24.549 align:start position:0% like just an extra layer if you would imp<00:42:21.280> port<00:42:21.880> and<00:42:22.000> it<00:42:22.319> like<00:42:22.680> detects<00:42:23.280> that<00:42:23.559> you 00:42:24.549 --> 00:42:24.559 align:start position:0% imp port and it like detects that you 00:42:24.559 --> 00:42:26.630 align:start position:0% imp port and it like detects that you tested<00:42:24.880> in<00:42:24.960> the<00:42:25.119> last<00:42:25.319> two<00:42:25.520> eports<00:42:26.400> it<00:42:26.480> will 00:42:26.630 --> 00:42:26.640 align:start position:0% tested in the last two eports it will 00:42:26.640 --> 00:42:28.150 align:start position:0% tested in the last two eports it will basically<00:42:27.000> just<00:42:27.200> just<00:42:27.319> give<00:42:27.480> you<00:42:27.559> a<00:42:27.720> warning 00:42:28.150 --> 00:42:28.160 align:start position:0% basically just just give you a warning 00:42:28.160 --> 00:42:31.069 align:start position:0% basically just just give you a warning hey<00:42:28.880> are<00:42:29.000> you<00:42:29.079> sure<00:42:29.319> you<00:42:29.440> want<00:42:29.559> to<00:42:29.720> import<00:42:30.240> this 00:42:31.069 --> 00:42:31.079 align:start position:0% hey are you sure you want to import this 00:42:31.079 --> 00:42:33.270 align:start position:0% hey are you sure you want to import this uh<00:42:31.200> obviously<00:42:31.520> you<00:42:31.720> can<00:42:31.839> still<00:42:32.119> import<00:42:32.480> it<00:42:32.720> but 00:42:33.270 --> 00:42:33.280 align:start position:0% uh obviously you can still import it but 00:42:33.280 --> 00:42:34.710 align:start position:0% uh obviously you can still import it but uh<00:42:33.400> usually<00:42:33.640> it's<00:42:33.760> a<00:42:33.880> pretty<00:42:34.160> good<00:42:34.359> warning 00:42:34.710 --> 00:42:34.720 align:start position:0% uh usually it's a pretty good warning 00:42:34.720 --> 00:42:37.309 align:start position:0% uh usually it's a pretty good warning you<00:42:34.800> should<00:42:35.040> probably<00:42:35.480> keep<00:42:35.680> that<00:42:35.839> in<00:42:36.040> mind<00:42:37.040> uh 00:42:37.309 --> 00:42:37.319 align:start position:0% you should probably keep that in mind uh 00:42:37.319 --> 00:42:39.589 align:start position:0% you should probably keep that in mind uh if<00:42:37.440> you<00:42:37.520> don't<00:42:37.720> want<00:42:37.839> to<00:42:38.040> wait<00:42:38.839> um<00:42:39.040> also<00:42:39.359> as<00:42:39.440> I 00:42:39.589 --> 00:42:39.599 align:start position:0% if you don't want to wait um also as I 00:42:39.599 --> 00:42:42.270 align:start position:0% if you don't want to wait um also as I said<00:42:40.480> uh<00:42:40.760> some<00:42:41.000> clients<00:42:41.440> really<00:42:41.680> need<00:42:41.920> long 00:42:42.270 --> 00:42:42.280 align:start position:0% said uh some clients really need long 00:42:42.280 --> 00:42:45.470 align:start position:0% said uh some clients really need long like<00:42:42.839> uh<00:42:43.520> if<00:42:43.640> you<00:42:44.119> if<00:42:44.200> you're<00:42:44.359> in<00:42:44.480> a<00:42:44.599> hurry 00:42:45.470 --> 00:42:45.480 align:start position:0% like uh if you if you're in a hurry 00:42:45.480 --> 00:42:47.470 align:start position:0% like uh if you if you're in a hurry there<00:42:45.599> is<00:42:45.880> usually<00:42:46.200> no<00:42:46.520> real<00:42:46.800> reason<00:42:47.040> to<00:42:47.200> do<00:42:47.359> it 00:42:47.470 --> 00:42:47.480 align:start position:0% there is usually no real reason to do it 00:42:47.480 --> 00:42:49.309 align:start position:0% there is usually no real reason to do it but<00:42:47.599> if<00:42:47.680> you're<00:42:47.839> really<00:42:47.960> in<00:42:48.079> a<00:42:48.240> hurry<00:42:48.880> uh<00:42:49.079> or 00:42:49.309 --> 00:42:49.319 align:start position:0% but if you're really in a hurry uh or 00:42:49.319 --> 00:42:52.549 align:start position:0% but if you're really in a hurry uh or like<00:42:49.520> have<00:42:50.240> multiple<00:42:50.680> hundreds<00:42:51.040> of<00:42:51.480> keys<00:42:52.480> uh 00:42:52.549 --> 00:42:52.559 align:start position:0% like have multiple hundreds of keys uh 00:42:52.559 --> 00:42:55.190 align:start position:0% like have multiple hundreds of keys uh you<00:42:52.680> can<00:42:52.880> always<00:42:53.240> like<00:42:53.400> deactivate<00:42:54.160> this<00:42:54.760> also 00:42:55.190 --> 00:42:55.200 align:start position:0% you can always like deactivate this also 00:42:55.200 --> 00:42:57.230 align:start position:0% you can always like deactivate this also just<00:42:55.559> confirm<00:42:55.960> and<00:42:56.160> restart<00:42:56.640> and<00:42:56.760> then<00:42:56.920> you 00:42:57.230 --> 00:42:57.240 align:start position:0% just confirm and restart and then you 00:42:57.240 --> 00:42:58.950 align:start position:0% just confirm and restart and then you would<00:42:57.599> it<00:42:57.720> would<00:42:57.920> just<00:42:58.200> like<00:42:58.400> import<00:42:58.760> it 00:42:58.950 --> 00:42:58.960 align:start position:0% would it would just like import it 00:42:58.960 --> 00:43:01.710 align:start position:0% would it would just like import it without<00:42:59.200> doing<00:42:59.480> this<00:42:59.720> check<00:43:00.720> as<00:43:00.800> you<00:43:00.920> can<00:43:01.079> see 00:43:01.710 --> 00:43:01.720 align:start position:0% without doing this check as you can see 00:43:01.720 --> 00:43:03.390 align:start position:0% without doing this check as you can see um<00:43:02.200> also<00:43:02.559> really 00:43:03.390 --> 00:43:03.400 align:start position:0% um also really 00:43:03.400 --> 00:43:05.829 align:start position:0% um also really interesting<00:43:04.400> uh<00:43:04.680> we<00:43:04.880> built<00:43:05.200> the<00:43:05.359> whole<00:43:05.559> thing 00:43:05.829 --> 00:43:05.839 align:start position:0% interesting uh we built the whole thing 00:43:05.839 --> 00:43:08.230 align:start position:0% interesting uh we built the whole thing in<00:43:05.960> a<00:43:06.240> in<00:43:06.319> a<00:43:06.480> way<00:43:06.720> that<00:43:06.880> you're<00:43:07.280> are<00:43:07.680> capable<00:43:08.040> of 00:43:08.230 --> 00:43:08.240 align:start position:0% in a in a way that you're are capable of 00:43:08.240 --> 00:43:10.270 align:start position:0% in a in a way that you're are capable of like<00:43:08.359> seeing<00:43:08.760> what<00:43:08.920> it<00:43:09.280> does<00:43:09.760> actually<00:43:10.119> if 00:43:10.270 --> 00:43:10.280 align:start position:0% like seeing what it does actually if 00:43:10.280 --> 00:43:14.349 align:start position:0% like seeing what it does actually if there's<00:43:10.480> like<00:43:10.599> a<00:43:10.720> small<00:43:11.079> task<00:43:11.760> manager<00:43:12.760> so<00:43:13.359> um 00:43:14.349 --> 00:43:14.359 align:start position:0% there's like a small task manager so um 00:43:14.359 --> 00:43:16.349 align:start position:0% there's like a small task manager so um you<00:43:14.559> can<00:43:14.880> you<00:43:15.000> can<00:43:15.280> always<00:43:15.640> just<00:43:15.920> if<00:43:16.040> you<00:43:16.160> run 00:43:16.349 --> 00:43:16.359 align:start position:0% you can you can always just if you run 00:43:16.359 --> 00:43:19.390 align:start position:0% you can you can always just if you run into<00:43:16.720> like<00:43:16.880> any<00:43:17.079> eror<00:43:17.520> for<00:43:18.000> example<00:43:19.000> uh<00:43:19.200> could 00:43:19.390 --> 00:43:19.400 align:start position:0% into like any eror for example uh could 00:43:19.400 --> 00:43:21.309 align:start position:0% into like any eror for example uh could be<00:43:19.760> it's<00:43:19.960> it's<00:43:20.079> a<00:43:20.200> client<00:43:20.559> software<00:43:21.000> it's<00:43:21.119> in 00:43:21.309 --> 00:43:21.319 align:start position:0% be it's it's a client software it's in 00:43:21.319 --> 00:43:23.390 align:start position:0% be it's it's a client software it's in development<00:43:22.280> usually<00:43:22.720> like<00:43:23.200> sometimes 00:43:23.390 --> 00:43:23.400 align:start position:0% development usually like sometimes 00:43:23.400 --> 00:43:25.150 align:start position:0% development usually like sometimes they're<00:43:23.680> stable<00:43:24.119> One<00:43:24.359> release<00:43:24.960> sometimes 00:43:25.150 --> 00:43:25.160 align:start position:0% they're stable One release sometimes 00:43:25.160 --> 00:43:26.829 align:start position:0% they're stable One release sometimes they<00:43:25.280> gets<00:43:25.559> unstable<00:43:26.040> the<00:43:26.160> next<00:43:26.359> release<00:43:26.720> then 00:43:26.829 --> 00:43:26.839 align:start position:0% they gets unstable the next release then 00:43:26.839 --> 00:43:29.309 align:start position:0% they gets unstable the next release then they<00:43:26.960> get<00:43:27.200> stable<00:43:27.680> again<00:43:28.680> it's<00:43:28.920> nice 00:43:29.309 --> 00:43:29.319 align:start position:0% they get stable again it's nice 00:43:29.319 --> 00:43:33.069 align:start position:0% they get stable again it's nice obviously<00:43:29.839> that<00:43:30.240> they<00:43:31.119> get<00:43:31.359> still<00:43:31.800> like<00:43:32.079> this 00:43:33.069 --> 00:43:33.079 align:start position:0% obviously that they get still like this 00:43:33.079 --> 00:43:35.549 align:start position:0% obviously that they get still like this that<00:43:33.240> much<00:43:33.520> like<00:43:33.720> development<00:43:34.280> time<00:43:35.119> but<00:43:35.440> uh 00:43:35.549 --> 00:43:35.559 align:start position:0% that much like development time but uh 00:43:35.559 --> 00:43:37.710 align:start position:0% that much like development time but uh this<00:43:35.680> leads<00:43:35.960> to<00:43:36.160> some<00:43:36.760> could<00:43:37.000> lead<00:43:37.200> to<00:43:37.400> always 00:43:37.710 --> 00:43:37.720 align:start position:0% this leads to some could lead to always 00:43:37.720 --> 00:43:40.309 align:start position:0% this leads to some could lead to always like<00:43:37.880> some<00:43:38.160> problems<00:43:38.559> during<00:43:38.800> the<00:43:39.240> version<00:43:40.240> if 00:43:40.309 --> 00:43:40.319 align:start position:0% like some problems during the version if 00:43:40.319 --> 00:43:42.670 align:start position:0% like some problems during the version if you<00:43:40.440> run<00:43:40.680> into<00:43:40.920> a<00:43:41.119> problem<00:43:41.839> uh<00:43:42.240> we<00:43:42.359> usually 00:43:42.670 --> 00:43:42.680 align:start position:0% you run into a problem uh we usually 00:43:42.680 --> 00:43:45.750 align:start position:0% you run into a problem uh we usually recommend<00:43:43.240> you<00:43:43.400> to<00:43:43.680> just<00:43:44.559> uh<00:43:44.720> check<00:43:44.920> out<00:43:45.240> first 00:43:45.750 --> 00:43:45.760 align:start position:0% recommend you to just uh check out first 00:43:45.760 --> 00:43:48.309 align:start position:0% recommend you to just uh check out first if<00:43:46.040> the<00:43:46.440> uh<00:43:46.559> in<00:43:46.680> the<00:43:46.839> task<00:43:47.079> manager<00:43:47.920> you<00:43:48.040> can 00:43:48.309 --> 00:43:48.319 align:start position:0% if the uh in the task manager you can 00:43:48.319 --> 00:43:50.829 align:start position:0% if the uh in the task manager you can copy<00:43:48.680> this<00:43:48.960> data<00:43:49.880> you<00:43:50.000> can<00:43:50.200> come<00:43:50.440> on<00:43:50.640> our 00:43:50.829 --> 00:43:50.839 align:start position:0% copy this data you can come on our 00:43:50.839 --> 00:43:53.190 align:start position:0% copy this data you can come on our Discord<00:43:51.280> you<00:43:51.400> just<00:43:51.640> copy<00:43:51.880> it<00:43:52.000> in<00:43:52.160> if<00:43:52.280> it's<00:43:52.400> an 00:43:53.190 --> 00:43:53.200 align:start position:0% Discord you just copy it in if it's an 00:43:53.200 --> 00:43:57.109 align:start position:0% Discord you just copy it in if it's an error<00:43:54.200> uh<00:43:54.359> you<00:43:54.480> can<00:43:54.680> always<00:43:55.160> also<00:43:56.000> uh<00:43:56.160> go<00:43:56.359> in<00:43:56.880> uh 00:43:57.109 --> 00:43:57.119 align:start position:0% error uh you can always also uh go in uh 00:43:57.119 --> 00:43:59.309 align:start position:0% error uh you can always also uh go in uh for<00:43:57.280> the<00:43:57.359> clients<00:43:58.079> themselves<00:43:59.079> you<00:43:59.160> can 00:43:59.309 --> 00:43:59.319 align:start position:0% for the clients themselves you can 00:43:59.319 --> 00:44:01.390 align:start position:0% for the clients themselves you can always<00:43:59.599> go<00:43:59.880> into<00:44:00.079> the<00:44:00.200> loog<00:44:00.480> pages<00:44:00.960> the<00:44:01.079> loog 00:44:01.390 --> 00:44:01.400 align:start position:0% always go into the loog pages the loog 00:44:01.400 --> 00:44:04.150 align:start position:0% always go into the loog pages the loog pages<00:44:01.960> are<00:44:02.960> basically<00:44:03.359> your<00:44:03.559> bread<00:44:03.800> and 00:44:04.150 --> 00:44:04.160 align:start position:0% pages are basically your bread and 00:44:04.160 --> 00:44:06.150 align:start position:0% pages are basically your bread and butter<00:44:04.520> when<00:44:04.640> it<00:44:04.800> comes<00:44:05.079> to<00:44:05.240> maintenance 00:44:06.150 --> 00:44:06.160 align:start position:0% butter when it comes to maintenance 00:44:06.160 --> 00:44:08.190 align:start position:0% butter when it comes to maintenance whenever<00:44:06.480> you<00:44:06.599> run<00:44:06.839> into<00:44:07.200> any<00:44:07.559> problem<00:44:08.000> with 00:44:08.190 --> 00:44:08.200 align:start position:0% whenever you run into any problem with 00:44:08.200 --> 00:44:10.150 align:start position:0% whenever you run into any problem with the<00:44:08.440> clients<00:44:09.079> themselves<00:44:09.640> you<00:44:09.760> will 00:44:10.150 --> 00:44:10.160 align:start position:0% the clients themselves you will 00:44:10.160 --> 00:44:13.549 align:start position:0% the clients themselves you will basically<00:44:10.720> find<00:44:11.079> this<00:44:11.240> in<00:44:11.599> here<00:44:12.599> uh<00:44:13.200> you<00:44:13.319> can 00:44:13.549 --> 00:44:13.559 align:start position:0% basically find this in here uh you can 00:44:13.559 --> 00:44:16.349 align:start position:0% basically find this in here uh you can switch<00:44:13.880> through<00:44:14.119> the<00:44:14.280> clients<00:44:15.359> themselves 00:44:16.349 --> 00:44:16.359 align:start position:0% switch through the clients themselves 00:44:16.359 --> 00:44:19.630 align:start position:0% switch through the clients themselves this<00:44:16.599> case<00:44:17.160> you<00:44:17.280> can<00:44:17.480> see<00:44:17.920> we're<00:44:18.160> already<00:44:18.640> like 00:44:19.630 --> 00:44:19.640 align:start position:0% this case you can see we're already like 00:44:19.640 --> 00:44:22.910 align:start position:0% this case you can see we're already like uh<00:44:19.839> sinking<00:44:20.400> here<00:44:20.559> on<00:44:20.960> uh<00:44:21.680> load<00:44:22.160> here<00:44:22.359> sying<00:44:22.760> it 00:44:22.910 --> 00:44:22.920 align:start position:0% uh sinking here on uh load here sying it 00:44:22.920 --> 00:44:28.910 align:start position:0% uh sinking here on uh load here sying it just<00:44:23.119> tells<00:44:23.520> you<00:44:24.520> uh<00:44:25.319> the<00:44:25.920> the<00:44:26.640> um 00:44:28.910 --> 00:44:28.920 align:start position:0% just tells you uh the the um 00:44:28.920 --> 00:44:33.710 align:start position:0% just tells you uh the the um errors<00:44:29.640> happen<00:44:30.720> quite<00:44:31.720> uh<00:44:32.599> quite<00:44:32.839> rarely 00:44:33.710 --> 00:44:33.720 align:start position:0% errors happen quite uh quite rarely 00:44:33.720 --> 00:44:36.230 align:start position:0% errors happen quite uh quite rarely usually<00:44:34.559> this<00:44:35.000> uh<00:44:35.319> the<00:44:35.440> not<00:44:35.720> usually<00:44:36.000> only 00:44:36.230 --> 00:44:36.240 align:start position:0% usually this uh the not usually only 00:44:36.240 --> 00:44:38.549 align:start position:0% usually this uh the not usually only breaks<00:44:36.680> if<00:44:36.800> you<00:44:37.319> have<00:44:37.480> like<00:44:37.640> a<00:44:37.800> blackout<00:44:38.359> for 00:44:38.549 --> 00:44:38.559 align:start position:0% breaks if you have like a blackout for 00:44:38.559 --> 00:44:43.109 align:start position:0% breaks if you have like a blackout for example<00:44:39.520> or<00:44:39.760> you<00:44:40.200> um<00:44:40.640> run<00:44:40.920> into<00:44:41.200> any<00:44:41.640> like<00:44:42.160> uh 00:44:43.109 --> 00:44:43.119 align:start position:0% example or you um run into any like uh 00:44:43.119 --> 00:44:45.710 align:start position:0% example or you um run into any like uh syncing<00:44:43.680> problems<00:44:44.599> um<00:44:44.960> if<00:44:45.079> you<00:44:45.240> run<00:44:45.480> into 00:44:45.710 --> 00:44:45.720 align:start position:0% syncing problems um if you run into 00:44:45.720 --> 00:44:47.950 align:start position:0% syncing problems um if you run into syncing<00:44:46.200> problems<00:44:46.640> we<00:44:46.800> have<00:44:47.079> a<00:44:47.280> easy<00:44:47.599> command 00:44:47.950 --> 00:44:47.960 align:start position:0% syncing problems we have a easy command 00:44:47.960 --> 00:44:50.670 align:start position:0% syncing problems we have a easy command to<00:44:48.119> do<00:44:48.319> this<00:44:48.520> you<00:44:48.640> can<00:44:48.800> always<00:44:49.119> go<00:44:49.319> into<00:44:49.680> the<00:44:50.559> uh 00:44:50.670 --> 00:44:50.680 align:start position:0% to do this you can always go into the uh 00:44:50.680 --> 00:44:53.630 align:start position:0% to do this you can always go into the uh resync<00:44:51.200> button<00:44:51.920> is<00:44:52.520> basically<00:44:52.920> the<00:44:53.079> same<00:44:53.359> as 00:44:53.630 --> 00:44:53.640 align:start position:0% resync button is basically the same as 00:44:53.640 --> 00:44:55.670 align:start position:0% resync button is basically the same as the<00:44:54.079> thing<00:44:54.319> in<00:44:54.440> the<00:44:54.559> setup<00:44:55.119> themselves<00:44:55.520> you 00:44:55.670 --> 00:44:55.680 align:start position:0% the thing in the setup themselves you 00:44:55.680 --> 00:44:58.390 align:start position:0% the thing in the setup themselves you can<00:44:56.400> if<00:44:56.520> you<00:44:56.640> want<00:44:56.800> to<00:44:57.200> think<00:44:57.359> from<00:44:57.559> Genesis<00:44:58.200> I 00:44:58.390 --> 00:44:58.400 align:start position:0% can if you want to think from Genesis I 00:44:58.400 --> 00:45:00.230 align:start position:0% can if you want to think from Genesis I don't<00:44:58.720> recommend<00:44:59.280> this<00:44:59.559> it's<00:44:59.760> also<00:45:00.000> not 00:45:00.230 --> 00:45:00.240 align:start position:0% don't recommend this it's also not 00:45:00.240 --> 00:45:02.230 align:start position:0% don't recommend this it's also not recommended<00:45:01.119> by<00:45:01.240> the<00:45:01.359> client<00:45:01.640> teams<00:45:01.920> to<00:45:02.079> do 00:45:02.230 --> 00:45:02.240 align:start position:0% recommended by the client teams to do 00:45:02.240 --> 00:45:06.589 align:start position:0% recommended by the client teams to do that<00:45:03.000> because<00:45:03.520> a<00:45:03.839> takes<00:45:04.440> forever<00:45:05.440> and<00:45:05.920> uh<00:45:06.359> B 00:45:06.589 --> 00:45:06.599 align:start position:0% that because a takes forever and uh B 00:45:06.599 --> 00:45:09.270 align:start position:0% that because a takes forever and uh B you<00:45:06.839> just<00:45:07.319> uh<00:45:07.680> sometimes<00:45:08.000> you<00:45:08.400> could<00:45:08.680> run<00:45:08.920> into 00:45:09.270 --> 00:45:09.280 align:start position:0% you just uh sometimes you could run into 00:45:09.280 --> 00:45:11.870 align:start position:0% you just uh sometimes you could run into problems<00:45:09.720> during<00:45:10.040> the<00:45:10.200> sying<00:45:10.960> from 00:45:11.870 --> 00:45:11.880 align:start position:0% problems during the sying from 00:45:11.880 --> 00:45:15.230 align:start position:0% problems during the sying from Genesis<00:45:12.880> um<00:45:13.640> then<00:45:13.800> you<00:45:13.960> can<00:45:14.480> uh<00:45:14.920> you<00:45:15.040> would 00:45:15.230 --> 00:45:15.240 align:start position:0% Genesis um then you can uh you would 00:45:15.240 --> 00:45:17.790 align:start position:0% Genesis um then you can uh you would just<00:45:15.440> select<00:45:15.800> like<00:45:15.920> a<00:45:16.040> checkpoint<00:45:16.559> sync<00:45:17.559> uh 00:45:17.790 --> 00:45:17.800 align:start position:0% just select like a checkpoint sync uh 00:45:17.800 --> 00:45:19.710 align:start position:0% just select like a checkpoint sync uh recommended<00:45:18.359> one<00:45:18.599> you<00:45:18.800> go<00:45:19.040> with<00:45:19.240> for<00:45:19.400> example 00:45:19.710 --> 00:45:19.720 align:start position:0% recommended one you go with for example 00:45:19.720 --> 00:45:23.309 align:start position:0% recommended one you go with for example loar<00:45:20.400> or<00:45:20.599> something<00:45:20.880> like<00:45:21.160> that<00:45:22.079> and<00:45:22.680> uh<00:45:23.040> it 00:45:23.309 --> 00:45:23.319 align:start position:0% loar or something like that and uh it 00:45:23.319 --> 00:45:25.790 align:start position:0% loar or something like that and uh it basically<00:45:23.760> just<00:45:23.960> deletes<00:45:24.319> the<00:45:24.440> old<00:45:24.800> database 00:45:25.790 --> 00:45:25.800 align:start position:0% basically just deletes the old database 00:45:25.800 --> 00:45:31.150 align:start position:0% basically just deletes the old database and<00:45:26.280> uh<00:45:27.400> to<00:45:28.079> uh<00:45:28.720> attempts<00:45:29.119> to<00:45:29.680> sync<00:45:30.079> from<00:45:30.520> this 00:45:31.150 --> 00:45:31.160 align:start position:0% and uh to uh attempts to sync from this 00:45:31.160 --> 00:45:32.870 align:start position:0% and uh to uh attempts to sync from this uh<00:45:31.280> checkpoint 00:45:32.870 --> 00:45:32.880 align:start position:0% uh checkpoint 00:45:32.880 --> 00:45:35.750 align:start position:0% uh checkpoint itself<00:45:33.880> um<00:45:34.359> another<00:45:34.960> some<00:45:35.119> other<00:45:35.359> things<00:45:35.599> we 00:45:35.750 --> 00:45:35.760 align:start position:0% itself um another some other things we 00:45:35.760 --> 00:45:37.910 align:start position:0% itself um another some other things we have<00:45:35.960> we<00:45:36.040> have<00:45:36.200> like<00:45:36.440> a<00:45:36.920> uh<00:45:37.319> link<00:45:37.599> to<00:45:37.720> the 00:45:37.910 --> 00:45:37.920 align:start position:0% have we have like a uh link to the 00:45:37.920 --> 00:45:40.710 align:start position:0% have we have like a uh link to the documentation<00:45:38.640> so<00:45:38.880> if<00:45:38.960> you're<00:45:39.599> interested<00:45:40.599> uh 00:45:40.710 --> 00:45:40.720 align:start position:0% documentation so if you're interested uh 00:45:40.720 --> 00:45:42.950 align:start position:0% documentation so if you're interested uh to<00:45:41.119> like<00:45:41.599> configure<00:45:42.040> your<00:45:42.160> note<00:45:42.440> a<00:45:42.520> little<00:45:42.720> bit 00:45:42.950 --> 00:45:42.960 align:start position:0% to like configure your note a little bit 00:45:42.960 --> 00:45:44.910 align:start position:0% to like configure your note a little bit more<00:45:43.160> deeply<00:45:43.680> maybe<00:45:43.880> you<00:45:44.000> use<00:45:44.160> it<00:45:44.280> for 00:45:44.910 --> 00:45:44.920 align:start position:0% more deeply maybe you use it for 00:45:44.920 --> 00:45:47.510 align:start position:0% more deeply maybe you use it for development<00:45:45.920> uh<00:45:46.200> we<00:45:46.400> do<00:45:46.680> this<00:45:46.960> we<00:45:47.119> have<00:45:47.359> like 00:45:47.510 --> 00:45:47.520 align:start position:0% development uh we do this we have like 00:45:47.520 --> 00:45:50.430 align:start position:0% development uh we do this we have like the<00:45:47.640> option<00:45:47.960> in<00:45:48.160> steum<00:45:48.800> you<00:45:49.000> can<00:45:50.000> uh<00:45:50.119> in<00:45:50.280> the 00:45:50.430 --> 00:45:50.440 align:start position:0% the option in steum you can uh in the 00:45:50.440 --> 00:45:52.190 align:start position:0% the option in steum you can uh in the settings<00:45:50.960> themselves<00:45:51.400> you<00:45:51.520> can<00:45:51.680> go<00:45:51.839> into<00:45:52.040> the 00:45:52.190 --> 00:45:52.200 align:start position:0% settings themselves you can go into the 00:45:52.200 --> 00:45:56.510 align:start position:0% settings themselves you can go into the expert<00:45:52.599> mode<00:45:53.359> it's<00:45:53.599> basically<00:45:54.440> uh<00:45:55.440> do<00:45:56.000> compos 00:45:56.510 --> 00:45:56.520 align:start position:0% expert mode it's basically uh do compos 00:45:56.520 --> 00:45:59.549 align:start position:0% expert mode it's basically uh do compos config<00:45:57.160> a<00:45:57.240> little<00:45:57.400> bit<00:45:57.559> of<00:45:57.640> a<00:45:57.760> glorified<00:45:58.440> one 00:45:59.549 --> 00:45:59.559 align:start position:0% config a little bit of a glorified one 00:45:59.559 --> 00:46:02.190 align:start position:0% config a little bit of a glorified one um<00:46:00.559> you<00:46:00.680> can<00:46:00.839> see<00:46:01.160> you<00:46:01.280> can<00:46:01.480> like<00:46:01.640> set<00:46:01.880> up<00:46:02.079> the 00:46:02.190 --> 00:46:02.200 align:start position:0% um you can see you can like set up the 00:46:02.200 --> 00:46:03.750 align:start position:0% um you can see you can like set up the options<00:46:02.520> here<00:46:02.680> we<00:46:02.839> give<00:46:03.000> you<00:46:03.160> the<00:46:03.319> full 00:46:03.750 --> 00:46:03.760 align:start position:0% options here we give you the full 00:46:03.760 --> 00:46:06.829 align:start position:0% options here we give you the full control<00:46:04.760> uh<00:46:04.960> but<00:46:05.319> if<00:46:05.480> you<00:46:05.920> play<00:46:06.240> with<00:46:06.440> this<00:46:06.680> and 00:46:06.829 --> 00:46:06.839 align:start position:0% control uh but if you play with this and 00:46:06.839 --> 00:46:09.190 align:start position:0% control uh but if you play with this and you<00:46:06.960> break<00:46:07.200> your<00:46:07.359> notes<00:46:08.280> uh<00:46:08.400> you<00:46:08.599> basically<00:46:09.119> I 00:46:09.190 --> 00:46:09.200 align:start position:0% you break your notes uh you basically I 00:46:09.200 --> 00:46:11.430 align:start position:0% you break your notes uh you basically I think<00:46:09.440> you<00:46:09.599> know<00:46:09.880> what<00:46:10.400> uh<00:46:10.800> we<00:46:10.960> hope<00:46:11.200> that<00:46:11.319> you 00:46:11.430 --> 00:46:11.440 align:start position:0% think you know what uh we hope that you 00:46:11.440 --> 00:46:13.030 align:start position:0% think you know what uh we hope that you know<00:46:11.640> what<00:46:11.760> to<00:46:11.920> do<00:46:12.240> that's<00:46:12.400> why<00:46:12.520> we<00:46:12.680> call<00:46:12.800> it 00:46:13.030 --> 00:46:13.040 align:start position:0% know what to do that's why we call it 00:46:13.040 --> 00:46:16.710 align:start position:0% know what to do that's why we call it expert<00:46:13.640> mode<00:46:14.640> uh<00:46:14.920> you<00:46:15.079> can<00:46:15.400> like<00:46:15.680> add<00:46:16.240> from<00:46:16.480> the 00:46:16.710 --> 00:46:16.720 align:start position:0% expert mode uh you can like add from the 00:46:16.720 --> 00:46:18.670 align:start position:0% expert mode uh you can like add from the documentation<00:46:17.520> some<00:46:17.800> stuff<00:46:18.119> if<00:46:18.240> you<00:46:18.359> need 00:46:18.670 --> 00:46:18.680 align:start position:0% documentation some stuff if you need 00:46:18.680 --> 00:46:21.390 align:start position:0% documentation some stuff if you need like<00:46:18.880> for<00:46:19.200> example<00:46:20.200> uh<00:46:20.400> long<00:46:20.720> longer<00:46:21.119> block 00:46:21.390 --> 00:46:21.400 align:start position:0% like for example uh long longer block 00:46:21.400 --> 00:46:23.630 align:start position:0% like for example uh long longer block retention<00:46:22.160> you<00:46:22.280> want 00:46:23.630 --> 00:46:23.640 align:start position:0% retention you want 00:46:23.640 --> 00:46:27.069 align:start position:0% retention you want uh<00:46:24.640> uh<00:46:24.760> you<00:46:24.839> want<00:46:25.000> to<00:46:25.160> change<00:46:25.800> uh<00:46:26.000> some<00:46:26.359> like<00:46:26.760> uh 00:46:27.069 --> 00:46:27.079 align:start position:0% uh uh you want to change uh some like uh 00:46:27.079 --> 00:46:29.309 align:start position:0% uh uh you want to change uh some like uh parameters<00:46:27.920> you<00:46:28.040> need<00:46:28.559> different<00:46:28.960> name 00:46:29.309 --> 00:46:29.319 align:start position:0% parameters you need different name 00:46:29.319 --> 00:46:31.990 align:start position:0% parameters you need different name spaces<00:46:29.760> for<00:46:30.040> development<00:46:31.040> or<00:46:31.400> want<00:46:31.599> to<00:46:31.720> get 00:46:31.990 --> 00:46:32.000 align:start position:0% spaces for development or want to get 00:46:32.000 --> 00:46:34.150 align:start position:0% spaces for development or want to get different<00:46:32.400> data<00:46:32.960> you<00:46:33.079> can<00:46:33.240> do<00:46:33.480> this<00:46:33.800> basically 00:46:34.150 --> 00:46:34.160 align:start position:0% different data you can do this basically 00:46:34.160 --> 00:46:35.510 align:start position:0% different data you can do this basically set<00:46:34.400> this<00:46:34.559> up<00:46:34.680> in 00:46:35.510 --> 00:46:35.520 align:start position:0% set this up in 00:46:35.520 --> 00:46:37.109 align:start position:0% set this up in there 00:46:37.109 --> 00:46:37.119 align:start position:0% there 00:46:37.119 --> 00:46:40.870 align:start position:0% there um<00:46:38.119> then<00:46:38.920> uh<00:46:39.599> the<00:46:39.760> next<00:46:40.000> one<00:46:40.160> we<00:46:40.319> have<00:46:40.480> like<00:46:40.640> a 00:46:40.870 --> 00:46:40.880 align:start position:0% um then uh the next one we have like a 00:46:40.880 --> 00:46:44.230 align:start position:0% um then uh the next one we have like a simple<00:46:41.200> start<00:46:41.520> and<00:46:41.720> restart<00:46:42.160> button<00:46:43.240> pretty 00:46:44.230 --> 00:46:44.240 align:start position:0% simple start and restart button pretty 00:46:44.240 --> 00:46:48.309 align:start position:0% simple start and restart button pretty uh<00:46:44.440> pretty<00:46:44.760> basic<00:46:45.599> and<00:46:46.160> uh<00:46:47.040> from<00:46:47.319> this<00:46:47.720> the<00:46:48.079> is 00:46:48.309 --> 00:46:48.319 align:start position:0% uh pretty basic and uh from this the is 00:46:48.319 --> 00:46:51.270 align:start position:0% uh pretty basic and uh from this the is basically<00:46:48.760> the<00:46:48.920> note<00:46:49.680> page<00:46:50.680> uh<00:46:50.880> what<00:46:51.000> David 00:46:51.270 --> 00:46:51.280 align:start position:0% basically the note page uh what David 00:46:51.280 --> 00:46:53.270 align:start position:0% basically the note page uh what David explained<00:46:51.640> to<00:46:51.760> you<00:46:51.960> also<00:46:52.280> is<00:46:52.599> um<00:46:52.800> you<00:46:52.920> can<00:46:53.079> go 00:46:53.270 --> 00:46:53.280 align:start position:0% explained to you also is um you can go 00:46:53.280 --> 00:46:54.990 align:start position:0% explained to you also is um you can go with<00:46:53.440> a<00:46:53.599> MEF<00:46:53.800> boost<00:46:54.079> it's<00:46:54.240> really<00:46:54.440> easy<00:46:54.680> to<00:46:54.800> set 00:46:54.990 --> 00:46:55.000 align:start position:0% with a MEF boost it's really easy to set 00:46:55.000 --> 00:46:57.230 align:start position:0% with a MEF boost it's really easy to set up<00:46:55.200> so<00:46:55.440> this<00:46:55.520> is<00:46:55.640> now<00:46:55.839> a<00:46:56.040> solo<00:46:56.359> vanilla<00:46:56.920> taking 00:46:57.230 --> 00:46:57.240 align:start position:0% up so this is now a solo vanilla taking 00:46:57.240 --> 00:46:59.710 align:start position:0% up so this is now a solo vanilla taking one<00:46:57.960> if<00:46:58.079> you<00:46:58.319> let's<00:46:58.520> say<00:46:58.720> you<00:46:59.040> decide<00:46:59.440> after 00:46:59.710 --> 00:46:59.720 align:start position:0% one if you let's say you decide after 00:46:59.720 --> 00:47:02.109 align:start position:0% one if you let's say you decide after like<00:46:59.839> a<00:47:00.000> week<00:47:00.200> of<00:47:00.359> running<00:47:00.760> this<00:47:01.480> hey<00:47:01.839> actually 00:47:02.109 --> 00:47:02.119 align:start position:0% like a week of running this hey actually 00:47:02.119 --> 00:47:04.670 align:start position:0% like a week of running this hey actually I<00:47:02.200> want<00:47:02.319> to<00:47:02.440> use<00:47:02.640> meth<00:47:02.920> boost<00:47:03.839> you<00:47:04.240> you<00:47:04.440> you 00:47:04.670 --> 00:47:04.680 align:start position:0% I want to use meth boost you you you 00:47:04.680 --> 00:47:06.829 align:start position:0% I want to use meth boost you you you don't<00:47:05.000> have<00:47:05.119> to<00:47:05.240> set<00:47:05.440> up<00:47:05.599> the<00:47:05.720> whole<00:47:05.960> note 00:47:06.829 --> 00:47:06.839 align:start position:0% don't have to set up the whole note 00:47:06.839 --> 00:47:09.630 align:start position:0% don't have to set up the whole note again<00:47:07.319> you<00:47:07.559> just<00:47:07.800> go<00:47:08.000> in<00:47:08.200> here<00:47:09.200> uh<00:47:09.280> we<00:47:09.440> have 00:47:09.630 --> 00:47:09.640 align:start position:0% again you just go in here uh we have 00:47:09.640 --> 00:47:14.270 align:start position:0% again you just go in here uh we have like<00:47:09.839> a<00:47:10.480> edit<00:47:10.760> note<00:47:11.160> page<00:47:12.160> you<00:47:12.280> would<00:47:12.520> go<00:47:12.680> in 00:47:14.270 --> 00:47:14.280 align:start position:0% like a edit note page you would go in 00:47:14.280 --> 00:47:17.030 align:start position:0% like a edit note page you would go in here<00:47:15.280> as<00:47:15.400> you<00:47:15.520> can<00:47:15.640> see<00:47:15.960> this<00:47:16.119> is<00:47:16.520> uh<00:47:16.800> you<00:47:16.880> can 00:47:17.030 --> 00:47:17.040 align:start position:0% here as you can see this is uh you can 00:47:17.040 --> 00:47:18.910 align:start position:0% here as you can see this is uh you can see<00:47:17.359> the<00:47:17.520> connections<00:47:18.040> you<00:47:18.160> can<00:47:18.319> also<00:47:18.559> change 00:47:18.910 --> 00:47:18.920 align:start position:0% see the connections you can also change 00:47:18.920 --> 00:47:21.190 align:start position:0% see the connections you can also change these<00:47:19.160> connections<00:47:20.119> on<00:47:20.280> the<00:47:20.480> right<00:47:20.680> side<00:47:21.040> you 00:47:21.190 --> 00:47:21.200 align:start position:0% these connections on the right side you 00:47:21.200 --> 00:47:24.510 align:start position:0% these connections on the right side you have<00:47:21.400> the<00:47:21.559> option<00:47:21.880> to<00:47:22.160> just<00:47:22.480> add<00:47:23.040> stuff<00:47:23.520> like 00:47:24.510 --> 00:47:24.520 align:start position:0% have the option to just add stuff like 00:47:24.520 --> 00:47:35.750 align:start position:0% have the option to just add stuff like me<00:47:25.040> boost 00:47:35.750 --> 00:47:35.760 align:start position:0% 00:47:35.760 --> 00:47:38.549 align:start position:0% okay<00:47:36.760> uh<00:47:37.079> you<00:47:37.280> can<00:47:37.440> choose<00:47:37.720> the<00:47:37.880> installation 00:47:38.549 --> 00:47:38.559 align:start position:0% okay uh you can choose the installation 00:47:38.559 --> 00:47:42.190 align:start position:0% okay uh you can choose the installation path<00:47:39.200> then<00:47:39.319> you<00:47:39.480> would<00:47:39.720> go<00:47:40.520> next<00:47:41.520> uh<00:47:41.680> you 00:47:42.190 --> 00:47:42.200 align:start position:0% path then you would go next uh you 00:47:42.200 --> 00:47:43.950 align:start position:0% path then you would go next uh you choose<00:47:42.400> your<00:47:42.559> relays<00:47:43.160> these<00:47:43.280> are<00:47:43.480> obviously 00:47:43.950 --> 00:47:43.960 align:start position:0% choose your relays these are obviously 00:47:43.960 --> 00:47:46.109 align:start position:0% choose your relays these are obviously different<00:47:44.240> on<00:47:44.440> Main<00:47:44.839> and<00:47:45.520> they're<00:47:45.760> depending 00:47:46.109 --> 00:47:46.119 align:start position:0% different on Main and they're depending 00:47:46.119 --> 00:47:48.150 align:start position:0% different on Main and they're depending on<00:47:46.280> the<00:47:46.480> network<00:47:46.800> you're<00:47:46.960> currently<00:47:47.359> on<00:47:48.040> you 00:47:48.150 --> 00:47:48.160 align:start position:0% on the network you're currently on you 00:47:48.160 --> 00:47:50.190 align:start position:0% on the network you're currently on you can<00:47:48.400> take<00:47:48.640> all<00:47:48.800> of<00:47:49.000> them<00:47:49.200> there's<00:47:49.440> usually<00:47:49.839> no 00:47:50.190 --> 00:47:50.200 align:start position:0% can take all of them there's usually no 00:47:50.200 --> 00:47:52.390 align:start position:0% can take all of them there's usually no reason<00:47:50.720> to<00:47:51.000> not<00:47:51.280> take<00:47:51.520> all<00:47:51.680> of<00:47:51.880> them<00:47:52.160> because 00:47:52.390 --> 00:47:52.400 align:start position:0% reason to not take all of them because 00:47:52.400 --> 00:47:55.549 align:start position:0% reason to not take all of them because me<00:47:52.880> boost<00:47:53.520> takes<00:47:53.920> the<00:47:54.200> best<00:47:54.559> block<00:47:55.040> from<00:47:55.359> these 00:47:55.549 --> 00:47:55.559 align:start position:0% me boost takes the best block from these 00:47:55.559 --> 00:47:58.430 align:start position:0% me boost takes the best block from these relays<00:47:56.559> it's<00:47:56.680> just<00:47:56.839> just<00:47:57.319> uh<00:47:57.440> chooses<00:47:57.839> this 00:47:58.430 --> 00:47:58.440 align:start position:0% relays it's just just uh chooses this 00:47:58.440 --> 00:48:00.390 align:start position:0% relays it's just just uh chooses this automatically<00:47:59.440> if<00:47:59.559> you're<00:47:59.839> American<00:48:00.280> you 00:48:00.390 --> 00:48:00.400 align:start position:0% automatically if you're American you 00:48:00.400 --> 00:48:02.790 align:start position:0% automatically if you're American you might<00:48:00.640> want<00:48:00.760> to<00:48:01.040> go<00:48:01.400> with<00:48:01.640> the<00:48:02.200> uh<00:48:02.359> over 00:48:02.790 --> 00:48:02.800 align:start position:0% might want to go with the uh over 00:48:02.800 --> 00:48:05.950 align:start position:0% might want to go with the uh over compliant<00:48:03.400> one<00:48:04.160> um<00:48:04.400> I<00:48:04.480> don't<00:48:04.640> know<00:48:05.000> how<00:48:05.839> I'm 00:48:05.950 --> 00:48:05.960 align:start position:0% compliant one um I don't know how I'm 00:48:05.960 --> 00:48:07.430 align:start position:0% compliant one um I don't know how I'm not<00:48:06.119> an<00:48:06.359> American<00:48:06.839> I<00:48:06.920> don't<00:48:07.079> know<00:48:07.280> what 00:48:07.430 --> 00:48:07.440 align:start position:0% not an American I don't know what 00:48:07.440 --> 00:48:09.790 align:start position:0% not an American I don't know what happens<00:48:07.720> if<00:48:07.880> you<00:48:08.040> don't<00:48:08.440> I<00:48:08.520> will<00:48:08.720> be<00:48:08.880> honest 00:48:09.790 --> 00:48:09.800 align:start position:0% happens if you don't I will be honest 00:48:09.800 --> 00:48:13.349 align:start position:0% happens if you don't I will be honest but<00:48:10.480> um<00:48:11.480> just<00:48:11.680> going<00:48:11.800> to<00:48:12.040> go<00:48:12.240> with<00:48:12.440> all<00:48:12.599> of 00:48:13.349 --> 00:48:13.359 align:start position:0% but um just going to go with all of 00:48:13.359 --> 00:48:15.910 align:start position:0% but um just going to go with all of them<00:48:14.359> then<00:48:14.520> you<00:48:14.640> would<00:48:14.839> go 00:48:15.910 --> 00:48:15.920 align:start position:0% them then you would go 00:48:15.920 --> 00:48:18.589 align:start position:0% them then you would go next<00:48:16.920> you<00:48:17.200> have<00:48:17.359> to<00:48:17.520> connect<00:48:17.839> this<00:48:18.000> to<00:48:18.160> a 00:48:18.589 --> 00:48:18.599 align:start position:0% next you have to connect this to a 00:48:18.599 --> 00:48:20.790 align:start position:0% next you have to connect this to a consensus<00:48:19.160> client<00:48:19.760> you<00:48:19.880> can<00:48:20.079> only<00:48:20.359> connect 00:48:20.790 --> 00:48:20.800 align:start position:0% consensus client you can only connect 00:48:20.800 --> 00:48:23.870 align:start position:0% consensus client you can only connect the<00:48:21.119> me<00:48:21.520> boost<00:48:21.800> to<00:48:22.040> one<00:48:22.599> consensus<00:48:23.119> client<00:48:23.760> if 00:48:23.870 --> 00:48:23.880 align:start position:0% the me boost to one consensus client if 00:48:23.880 --> 00:48:25.790 align:start position:0% the me boost to one consensus client if you<00:48:24.040> want<00:48:24.319> more<00:48:24.599> M<00:48:25.160> if<00:48:25.280> you<00:48:25.359> have<00:48:25.520> more 00:48:25.790 --> 00:48:25.800 align:start position:0% you want more M if you have more 00:48:25.800 --> 00:48:27.829 align:start position:0% you want more M if you have more consensus<00:48:26.319> clients<00:48:27.000> and<00:48:27.119> you<00:48:27.319> want<00:48:27.520> you<00:48:27.680> have 00:48:27.829 --> 00:48:27.839 align:start position:0% consensus clients and you want you have 00:48:27.839 --> 00:48:29.710 align:start position:0% consensus clients and you want you have to<00:48:27.960> add<00:48:28.200> more 00:48:29.710 --> 00:48:29.720 align:start position:0% to add more 00:48:29.720 --> 00:48:32.710 align:start position:0% to add more repost<00:48:31.000> Services<00:48:32.000> uh<00:48:32.200> then<00:48:32.319> we<00:48:32.440> go<00:48:32.559> with 00:48:32.710 --> 00:48:32.720 align:start position:0% repost Services uh then we go with 00:48:32.720 --> 00:48:36.630 align:start position:0% repost Services uh then we go with loadstar<00:48:33.720> we<00:48:34.160> confirm<00:48:35.160> and<00:48:35.599> um<00:48:35.960> as<00:48:36.079> soon<00:48:36.240> as<00:48:36.400> we 00:48:36.630 --> 00:48:36.640 align:start position:0% loadstar we confirm and um as soon as we 00:48:36.640 --> 00:48:39.150 align:start position:0% loadstar we confirm and um as soon as we confirm<00:48:37.000> the<00:48:37.079> changes<00:48:37.559> here<00:48:38.440> it<00:48:38.640> basically<00:48:39.000> is 00:48:39.150 --> 00:48:39.160 align:start position:0% confirm the changes here it basically is 00:48:39.160 --> 00:48:40.990 align:start position:0% confirm the changes here it basically is going<00:48:39.359> to<00:48:39.720> install<00:48:40.240> this<00:48:40.559> it's<00:48:40.680> going<00:48:40.800> to 00:48:40.990 --> 00:48:41.000 align:start position:0% going to install this it's going to 00:48:41.000 --> 00:48:45.150 align:start position:0% going to install this it's going to connect<00:48:41.440> all<00:48:41.599> of<00:48:41.920> this<00:48:42.920> and<00:48:43.480> um<00:48:44.480> then<00:48:44.880> uh<00:48:44.960> your 00:48:45.150 --> 00:48:45.160 align:start position:0% connect all of this and um then uh your 00:48:45.160 --> 00:48:47.549 align:start position:0% connect all of this and um then uh your note<00:48:45.559> basically<00:48:45.960> chooses<00:48:46.640> or<00:48:46.880> your<00:48:47.040> consensus 00:48:47.549 --> 00:48:47.559 align:start position:0% note basically chooses or your consensus 00:48:47.559 --> 00:48:50.990 align:start position:0% note basically chooses or your consensus client<00:48:47.839> chooses<00:48:48.359> if<00:48:48.920> uh<00:48:49.240> usually<00:48:50.240> the<00:48:50.520> M 00:48:50.990 --> 00:48:51.000 align:start position:0% client chooses if uh usually the M 00:48:51.000 --> 00:48:53.109 align:start position:0% client chooses if uh usually the M boosted<00:48:51.559> block<00:48:51.960> first<00:48:52.480> the<00:48:52.599> one<00:48:52.760> that's 00:48:53.109 --> 00:48:53.119 align:start position:0% boosted block first the one that's 00:48:53.119 --> 00:48:56.150 align:start position:0% boosted block first the one that's suggested<00:48:53.680> by<00:48:53.920> me<00:48:54.319> boost<00:48:55.160> if<00:48:55.280> it's<00:48:55.480> not<00:48:55.839> fast 00:48:56.150 --> 00:48:56.160 align:start position:0% suggested by me boost if it's not fast 00:48:56.160 --> 00:48:57.950 align:start position:0% suggested by me boost if it's not fast enough<00:48:56.359> to<00:48:56.520> do<00:48:56.880> this<00:48:57.000> it<00:48:57.119> will<00:48:57.359> just<00:48:57.599> take<00:48:57.839> the 00:48:57.950 --> 00:48:57.960 align:start position:0% enough to do this it will just take the 00:48:57.960 --> 00:49:00.750 align:start position:0% enough to do this it will just take the one<00:48:58.160> that's<00:48:58.440> actually<00:48:59.079> provided<00:48:59.520> by<00:48:59.720> its<00:48:59.880> own 00:49:00.750 --> 00:49:00.760 align:start position:0% one that's actually provided by its own 00:49:00.760 --> 00:49:03.750 align:start position:0% one that's actually provided by its own uh<00:49:01.160> execution<00:49:01.920> client<00:49:02.920> as<00:49:03.040> you<00:49:03.200> see<00:49:03.480> you<00:49:03.599> have 00:49:03.750 --> 00:49:03.760 align:start position:0% uh execution client as you see you have 00:49:03.760 --> 00:49:06.870 align:start position:0% uh execution client as you see you have like<00:49:03.880> the<00:49:04.079> small<00:49:04.480> like<00:49:04.760> little<00:49:05.440> um<00:49:06.240> icon<00:49:06.640> here 00:49:06.870 --> 00:49:06.880 align:start position:0% like the small like little um icon here 00:49:06.880 --> 00:49:09.150 align:start position:0% like the small like little um icon here to<00:49:07.400> indicate<00:49:07.880> that<00:49:08.040> you<00:49:08.200> are<00:49:08.480> like<00:49:08.680> connected 00:49:09.150 --> 00:49:09.160 align:start position:0% to indicate that you are like connected 00:49:09.160 --> 00:49:11.710 align:start position:0% to indicate that you are like connected with<00:49:09.359> this<00:49:10.280> you<00:49:10.440> can<00:49:10.640> always<00:49:11.040> change<00:49:11.480> these 00:49:11.710 --> 00:49:11.720 align:start position:0% with this you can always change these 00:49:11.720 --> 00:49:14.510 align:start position:0% with this you can always change these connections<00:49:12.400> inside<00:49:12.760> of<00:49:13.000> this<00:49:13.200> so<00:49:14.160> let's<00:49:14.359> say 00:49:14.510 --> 00:49:14.520 align:start position:0% connections inside of this so let's say 00:49:14.520 --> 00:49:17.109 align:start position:0% connections inside of this so let's say if<00:49:14.640> I<00:49:14.799> wanted<00:49:15.119> to<00:49:15.880> uh<00:49:16.280> let's<00:49:16.480> say<00:49:16.640> if<00:49:16.760> I<00:49:16.880> wanted 00:49:17.109 --> 00:49:17.119 align:start position:0% if I wanted to uh let's say if I wanted 00:49:17.119 --> 00:49:22.230 align:start position:0% if I wanted to uh let's say if I wanted to<00:49:17.240> add<00:49:17.440> another<00:49:17.760> consensus<00:49:18.720> client<00:49:19.720> like 00:49:22.230 --> 00:49:22.240 align:start position:0% 00:49:22.240 --> 00:49:23.870 align:start position:0% lighthous 00:49:23.870 --> 00:49:23.880 align:start position:0% lighthous 00:49:23.880 --> 00:49:28.510 align:start position:0% lighthous okay<00:49:24.880> like<00:49:25.280> lighter 00:49:28.510 --> 00:49:28.520 align:start position:0% 00:49:28.520 --> 00:49:30.309 align:start position:0% uh<00:49:28.640> it's<00:49:28.799> the<00:49:29.000> same<00:49:29.319> path<00:49:29.760> you<00:49:29.960> choose<00:49:30.200> the 00:49:30.309 --> 00:49:30.319 align:start position:0% uh it's the same path you choose the 00:49:30.319 --> 00:49:32.430 align:start position:0% uh it's the same path you choose the installation<00:49:31.000> path<00:49:31.319> you<00:49:31.480> choose<00:49:31.799> the<00:49:31.960> sync 00:49:32.430 --> 00:49:32.440 align:start position:0% installation path you choose the sync 00:49:32.440 --> 00:49:35.190 align:start position:0% installation path you choose the sync options<00:49:33.440> in<00:49:33.640> here<00:49:33.839> we<00:49:33.960> can<00:49:34.119> also<00:49:34.359> go<00:49:34.520> for<00:49:34.960> like 00:49:35.190 --> 00:49:35.200 align:start position:0% options in here we can also go for like 00:49:35.200 --> 00:49:38.150 align:start position:0% options in here we can also go for like just<00:49:35.640> checkpoint<00:49:36.200> sync<00:49:36.720> as<00:49:36.839> I<00:49:37.040> said<00:49:37.799> I<00:49:37.880> would 00:49:38.150 --> 00:49:38.160 align:start position:0% just checkpoint sync as I said I would 00:49:38.160 --> 00:49:40.510 align:start position:0% just checkpoint sync as I said I would recommend<00:49:38.640> this<00:49:38.799> to<00:49:38.960> use<00:49:39.240> this<00:49:39.520> always<00:49:40.200> client 00:49:40.510 --> 00:49:40.520 align:start position:0% recommend this to use this always client 00:49:40.520 --> 00:49:42.470 align:start position:0% recommend this to use this always client teams<00:49:40.920> recommend<00:49:41.359> you<00:49:41.480> to<00:49:41.720> always<00:49:42.000> use<00:49:42.319> this 00:49:42.470 --> 00:49:42.480 align:start position:0% teams recommend you to always use this 00:49:42.480 --> 00:49:46.230 align:start position:0% teams recommend you to always use this if<00:49:42.680> you<00:49:42.799> don't<00:49:42.960> need<00:49:43.160> the<00:49:43.319> data<00:49:44.040> itself<00:49:45.040> you<00:49:45.200> go 00:49:46.230 --> 00:49:46.240 align:start position:0% if you don't need the data itself you go 00:49:46.240 --> 00:49:48.870 align:start position:0% if you don't need the data itself you go next<00:49:47.240> you<00:49:47.359> can<00:49:47.960> uh<00:49:48.119> connect<00:49:48.480> this<00:49:48.640> with 00:49:48.870 --> 00:49:48.880 align:start position:0% next you can uh connect this with 00:49:48.880 --> 00:49:50.390 align:start position:0% next you can uh connect this with execution<00:49:49.319> clients<00:49:49.599> if<00:49:49.680> I<00:49:49.799> had<00:49:49.920> more<00:49:50.079> than<00:49:50.200> one 00:49:50.390 --> 00:49:50.400 align:start position:0% execution clients if I had more than one 00:49:50.400 --> 00:49:52.910 align:start position:0% execution clients if I had more than one execution<00:49:50.920> client<00:49:51.240> I<00:49:51.400> could<00:49:51.799> um<00:49:52.440> basically 00:49:52.910 --> 00:49:52.920 align:start position:0% execution client I could um basically 00:49:52.920 --> 00:49:55.589 align:start position:0% execution client I could um basically choose<00:49:53.240> this<00:49:53.359> in<00:49:53.559> here<00:49:53.720> as<00:49:54.240> well<00:49:55.240> this<00:49:55.440> case 00:49:55.589 --> 00:49:55.599 align:start position:0% choose this in here as well this case 00:49:55.599 --> 00:49:57.870 align:start position:0% choose this in here as well this case I'm<00:49:55.720> going<00:49:55.799> to<00:49:56.000> just<00:49:56.160> go<00:49:56.319> with<00:49:56.480> the<00:49:56.720> Bas<00:49:57.079> one 00:49:57.870 --> 00:49:57.880 align:start position:0% I'm going to just go with the Bas one 00:49:57.880 --> 00:49:59.750 align:start position:0% I'm going to just go with the Bas one it's<00:49:58.040> the<00:49:58.280> same<00:49:58.559> thing<00:49:59.000> just<00:49:59.200> confirm<00:49:59.640> the 00:49:59.750 --> 00:49:59.760 align:start position:0% it's the same thing just confirm the 00:49:59.760 --> 00:50:02.309 align:start position:0% it's the same thing just confirm the change<00:50:00.760> and<00:50:00.960> after<00:50:01.280> this<00:50:01.839> um<00:50:02.000> I'm<00:50:02.079> going<00:50:02.200> to 00:50:02.309 --> 00:50:02.319 align:start position:0% change and after this um I'm going to 00:50:02.319 --> 00:50:05.069 align:start position:0% change and after this um I'm going to show<00:50:02.520> you<00:50:02.760> how<00:50:03.000> to<00:50:03.359> modify<00:50:03.839> the<00:50:04.240> connections 00:50:05.069 --> 00:50:05.079 align:start position:0% show you how to modify the connections 00:50:05.079 --> 00:50:07.670 align:start position:0% show you how to modify the connections meaning<00:50:05.720> let's<00:50:05.960> say<00:50:06.559> uh<00:50:06.760> let's<00:50:06.920> say<00:50:07.040> load<00:50:07.359> star 00:50:07.670 --> 00:50:07.680 align:start position:0% meaning let's say uh let's say load star 00:50:07.680 --> 00:50:09.870 align:start position:0% meaning let's say uh let's say load star would<00:50:07.880> fall<00:50:08.200> out<00:50:08.599> for<00:50:08.799> some<00:50:09.040> reason<00:50:09.559> Could 00:50:09.870 --> 00:50:09.880 align:start position:0% would fall out for some reason Could 00:50:09.880 --> 00:50:12.309 align:start position:0% would fall out for some reason Could Happen<00:50:10.880> um<00:50:11.079> then<00:50:11.240> I<00:50:11.359> could<00:50:11.640> like<00:50:12.000> pretty 00:50:12.309 --> 00:50:12.319 align:start position:0% Happen um then I could like pretty 00:50:12.319 --> 00:50:15.710 align:start position:0% Happen um then I could like pretty simply<00:50:12.920> switch<00:50:13.480> to<00:50:14.480> uh<00:50:14.559> using<00:50:14.880> lighthous<00:50:15.520> with 00:50:15.710 --> 00:50:15.720 align:start position:0% simply switch to uh using lighthous with 00:50:15.720 --> 00:50:19.309 align:start position:0% simply switch to uh using lighthous with like<00:50:15.960> two<00:50:16.200> clicks<00:50:16.480> of<00:50:16.640> a 00:50:19.309 --> 00:50:19.319 align:start position:0% 00:50:19.319 --> 00:50:22.190 align:start position:0% button<00:50:20.319> see<00:50:20.680> I'm<00:50:20.799> going<00:50:20.920> to<00:50:21.079> go<00:50:21.240> in<00:50:21.440> here<00:50:21.839> I<00:50:21.960> can 00:50:22.190 --> 00:50:22.200 align:start position:0% button see I'm going to go in here I can 00:50:22.200 --> 00:50:24.230 align:start position:0% button see I'm going to go in here I can obviously<00:50:22.599> also<00:50:22.920> delete<00:50:23.359> this<00:50:23.640> I<00:50:23.720> can<00:50:23.920> switch 00:50:24.230 --> 00:50:24.240 align:start position:0% obviously also delete this I can switch 00:50:24.240 --> 00:50:27.230 align:start position:0% obviously also delete this I can switch the<00:50:24.359> client<00:50:24.680> itself<00:50:25.240> out<00:50:26.240> uh 00:50:27.230 --> 00:50:27.240 align:start position:0% the client itself out uh 00:50:27.240 --> 00:50:28.670 align:start position:0% the client itself out uh usually<00:50:27.559> don't<00:50:27.839> recommend<00:50:28.240> doing<00:50:28.520> this 00:50:28.670 --> 00:50:28.680 align:start position:0% usually don't recommend doing this 00:50:28.680 --> 00:50:30.030 align:start position:0% usually don't recommend doing this either<00:50:28.960> because<00:50:29.160> you<00:50:29.280> have<00:50:29.400> to<00:50:29.559> do<00:50:29.720> some 00:50:30.030 --> 00:50:30.040 align:start position:0% either because you have to do some 00:50:30.040 --> 00:50:31.870 align:start position:0% either because you have to do some config<00:50:30.520> changes<00:50:31.000> as<00:50:31.160> well<00:50:31.359> so<00:50:31.520> if<00:50:31.599> you're 00:50:31.870 --> 00:50:31.880 align:start position:0% config changes as well so if you're 00:50:31.880 --> 00:50:34.309 align:start position:0% config changes as well so if you're expert<00:50:32.240> you<00:50:32.400> probably<00:50:33.200> could<00:50:33.440> use<00:50:33.760> this<00:50:34.200> if 00:50:34.309 --> 00:50:34.319 align:start position:0% expert you probably could use this if 00:50:34.319 --> 00:50:37.069 align:start position:0% expert you probably could use this if you're<00:50:34.520> beginner<00:50:35.480> delete<00:50:35.880> it<00:50:36.280> and<00:50:36.480> just<00:50:36.720> addit 00:50:37.069 --> 00:50:37.079 align:start position:0% you're beginner delete it and just addit 00:50:37.079 --> 00:50:38.950 align:start position:0% you're beginner delete it and just addit new<00:50:37.359> it's<00:50:37.559> it's<00:50:37.799> basically<00:50:38.200> the<00:50:38.359> same<00:50:38.640> time<00:50:38.839> it 00:50:38.950 --> 00:50:38.960 align:start position:0% new it's it's basically the same time it 00:50:38.960 --> 00:50:41.589 align:start position:0% new it's it's basically the same time it doesn't<00:50:39.400> like<00:50:39.599> take<00:50:39.839> any<00:50:40.280> longer<00:50:41.280> uh<00:50:41.359> you<00:50:41.440> can 00:50:41.589 --> 00:50:41.599 align:start position:0% doesn't like take any longer uh you can 00:50:41.599 --> 00:50:43.390 align:start position:0% doesn't like take any longer uh you can go<00:50:41.760> here<00:50:41.880> into<00:50:42.119> the<00:50:42.240> modification<00:50:43.079> and<00:50:43.240> this 00:50:43.390 --> 00:50:43.400 align:start position:0% go here into the modification and this 00:50:43.400 --> 00:50:44.990 align:start position:0% go here into the modification and this as<00:50:43.480> you<00:50:43.599> can<00:50:43.720> see<00:50:44.119> if<00:50:44.240> I<00:50:44.359> wanted<00:50:44.599> to<00:50:44.720> change 00:50:44.990 --> 00:50:45.000 align:start position:0% as you can see if I wanted to change 00:50:45.000 --> 00:50:48.549 align:start position:0% as you can see if I wanted to change this<00:50:45.160> I<00:50:45.280> can<00:50:45.480> just<00:50:45.680> go<00:50:45.920> here<00:50:46.599> go<00:50:46.880> here<00:50:47.359> and<00:50:48.359> now 00:50:48.549 --> 00:50:48.559 align:start position:0% this I can just go here go here and now 00:50:48.559 --> 00:50:50.390 align:start position:0% this I can just go here go here and now it's<00:50:49.040> as<00:50:49.160> soon<00:50:49.319> as<00:50:49.440> I<00:50:49.559> confirmed<00:50:49.960> the<00:50:50.040> changes 00:50:50.390 --> 00:50:50.400 align:start position:0% it's as soon as I confirmed the changes 00:50:50.400 --> 00:50:51.829 align:start position:0% it's as soon as I confirmed the changes here<00:50:50.559> it<00:50:50.680> uses<00:50:50.960> the<00:50:51.079> lighthouse<00:50:51.480> client 00:50:51.829 --> 00:50:51.839 align:start position:0% here it uses the lighthouse client 00:50:51.839 --> 00:50:53.910 align:start position:0% here it uses the lighthouse client instead<00:50:52.079> of<00:50:52.200> the<00:50:52.319> load<00:50:52.559> star<00:50:52.839> one<00:50:53.319> so<00:50:53.520> you<00:50:53.640> can 00:50:53.910 --> 00:50:53.920 align:start position:0% instead of the load star one so you can 00:50:53.920 --> 00:50:56.069 align:start position:0% instead of the load star one so you can build<00:50:54.359> multiple<00:50:54.880> client<00:50:55.240> pairs<00:50:55.640> if<00:50:55.760> you<00:50:55.880> have 00:50:56.069 --> 00:50:56.079 align:start position:0% build multiple client pairs if you have 00:50:56.079 --> 00:50:58.870 align:start position:0% build multiple client pairs if you have the<00:50:57.119> uh<00:50:57.240> storage<00:50:57.559> and<00:50:57.720> the<00:50:57.839> resources<00:50:58.280> on<00:50:58.440> the 00:50:58.870 --> 00:50:58.880 align:start position:0% the uh storage and the resources on the 00:50:58.880 --> 00:51:00.630 align:start position:0% the uh storage and the resources on the U<00:50:59.040> server<00:50:59.400> itself<00:50:59.680> you<00:50:59.760> can<00:50:59.920> build<00:51:00.200> multiple 00:51:00.630 --> 00:51:00.640 align:start position:0% U server itself you can build multiple 00:51:00.640 --> 00:51:03.190 align:start position:0% U server itself you can build multiple client<00:51:00.960> pairs<00:51:01.559> run<00:51:01.839> them<00:51:02.000> on<00:51:02.240> Parallel<00:51:03.079> and 00:51:03.190 --> 00:51:03.200 align:start position:0% client pairs run them on Parallel and 00:51:03.200 --> 00:51:05.349 align:start position:0% client pairs run them on Parallel and then<00:51:03.440> just<00:51:03.640> switch<00:51:04.040> between<00:51:04.359> them<00:51:04.839> you<00:51:04.960> can<00:51:05.160> do 00:51:05.349 --> 00:51:05.359 align:start position:0% then just switch between them you can do 00:51:05.359 --> 00:51:08.349 align:start position:0% then just switch between them you can do this<00:51:05.559> over<00:51:05.920> multiple<00:51:06.480> nodes<00:51:06.920> you<00:51:07.200> can<00:51:07.400> also<00:51:08.119> uh 00:51:08.349 --> 00:51:08.359 align:start position:0% this over multiple nodes you can also uh 00:51:08.359 --> 00:51:10.390 align:start position:0% this over multiple nodes you can also uh multiple<00:51:08.760> servers<00:51:09.559> I<00:51:09.680> can<00:51:09.799> show<00:51:10.000> you<00:51:10.160> this<00:51:10.280> in 00:51:10.390 --> 00:51:10.400 align:start position:0% multiple servers I can show you this in 00:51:10.400 --> 00:51:14.430 align:start position:0% multiple servers I can show you this in a<00:51:10.559> second<00:51:10.880> as<00:51:11.000> well<00:51:11.839> soon<00:51:12.040> as<00:51:12.200> we<00:51:12.319> have<00:51:12.480> through 00:51:14.430 --> 00:51:14.440 align:start position:0% a second as well soon as we have through 00:51:14.440 --> 00:51:16.549 align:start position:0% a second as well soon as we have through this<00:51:15.440> takes<00:51:15.680> a<00:51:15.839> little 00:51:16.549 --> 00:51:16.559 align:start position:0% this takes a little 00:51:16.559 --> 00:51:19.950 align:start position:0% this takes a little bit<00:51:17.559> uh<00:51:17.960> we<00:51:18.119> have<00:51:18.319> like<00:51:18.520> the<00:51:18.720> option<00:51:19.119> to<00:51:19.799> uh 00:51:19.950 --> 00:51:19.960 align:start position:0% bit uh we have like the option to uh 00:51:19.960 --> 00:51:23.069 align:start position:0% bit uh we have like the option to uh make<00:51:20.160> this<00:51:20.319> a<00:51:20.520> little<00:51:20.760> bit<00:51:21.000> easier<00:51:22.000> um<00:51:22.760> so<00:51:22.960> you 00:51:23.069 --> 00:51:23.079 align:start position:0% make this a little bit easier um so you 00:51:23.079 --> 00:51:25.470 align:start position:0% make this a little bit easier um so you would<00:51:23.280> go<00:51:23.440> in<00:51:23.640> here<00:51:23.880> you<00:51:24.000> can<00:51:24.200> go<00:51:24.400> here<00:51:24.559> for 00:51:25.470 --> 00:51:25.480 align:start position:0% would go in here you can go here for 00:51:25.480 --> 00:51:28.710 align:start position:0% would go in here you can go here for external 00:51:28.710 --> 00:51:28.720 align:start position:0% 00:51:28.720 --> 00:51:32.710 align:start position:0% if<00:51:28.799> you<00:51:28.960> can<00:51:29.160> write<00:51:29.880> it<00:51:30.880> external<00:51:31.880> here<00:51:32.520> uh<00:51:32.640> you 00:51:32.710 --> 00:51:32.720 align:start position:0% if you can write it external here uh you 00:51:32.720 --> 00:51:35.309 align:start position:0% if you can write it external here uh you will<00:51:32.960> set<00:51:33.160> up<00:51:33.319> our<00:51:33.559> external<00:51:34.119> Source<00:51:35.119> um 00:51:35.309 --> 00:51:35.319 align:start position:0% will set up our external Source um 00:51:35.319 --> 00:51:36.870 align:start position:0% will set up our external Source um there's<00:51:35.599> a<00:51:35.720> little<00:51:35.960> bit<00:51:36.119> of<00:51:36.240> a<00:51:36.440> difference 00:51:36.870 --> 00:51:36.880 align:start position:0% there's a little bit of a difference 00:51:36.880 --> 00:51:40.750 align:start position:0% there's a little bit of a difference between<00:51:37.160> the<00:51:37.319> clients<00:51:38.119> uh<00:51:39.119> the<00:51:40.119> all<00:51:40.319> of<00:51:40.520> them 00:51:40.750 --> 00:51:40.760 align:start position:0% between the clients uh the all of them 00:51:40.760 --> 00:51:43.349 align:start position:0% between the clients uh the all of them are<00:51:41.000> the<00:51:41.200> same<00:51:41.559> except<00:51:42.040> prism<00:51:42.640> for<00:51:42.880> prism<00:51:43.240> you 00:51:43.349 --> 00:51:43.359 align:start position:0% are the same except prism for prism you 00:51:43.359 --> 00:51:45.270 align:start position:0% are the same except prism for prism you have<00:51:43.480> to<00:51:43.599> set<00:51:43.760> the<00:51:43.960> extra<00:51:44.319> value<00:51:44.960> though<00:51:45.160> this 00:51:45.270 --> 00:51:45.280 align:start position:0% have to set the extra value though this 00:51:45.280 --> 00:51:47.990 align:start position:0% have to set the extra value though this is<00:51:45.520> going<00:51:45.640> to<00:51:45.799> change<00:51:46.119> soon<00:51:46.440> as<00:51:46.599> well<00:51:47.200> so<00:51:47.760> soon 00:51:47.990 --> 00:51:48.000 align:start position:0% is going to change soon as well so soon 00:51:48.000 --> 00:51:49.109 align:start position:0% is going to change soon as well so soon this<00:51:48.119> is<00:51:48.240> not<00:51:48.400> going<00:51:48.480> to<00:51:48.599> be<00:51:48.720> a<00:51:48.839> client 00:51:49.109 --> 00:51:49.119 align:start position:0% this is not going to be a client 00:51:49.119 --> 00:51:51.309 align:start position:0% this is not going to be a client selection<00:51:49.559> anymore<00:51:49.920> this<00:51:50.040> is<00:51:50.119> going<00:51:50.200> to<00:51:50.319> be<00:51:50.440> a 00:51:51.309 --> 00:51:51.319 align:start position:0% selection anymore this is going to be a 00:51:51.319 --> 00:51:54.030 align:start position:0% selection anymore this is going to be a gnostic<00:51:52.319> um<00:51:52.720> the<00:51:52.880> external<00:51:53.319> Source<00:51:53.680> it<00:51:53.799> would 00:51:54.030 --> 00:51:54.040 align:start position:0% gnostic um the external Source it would 00:51:54.040 --> 00:51:56.190 align:start position:0% gnostic um the external Source it would basically<00:51:54.400> set<00:51:54.599> up<00:51:54.880> a<00:51:55.119> IP<00:51:55.559> like<00:51:55.880> where<00:51:56.079> a 00:51:56.190 --> 00:51:56.200 align:start position:0% basically set up a IP like where a 00:51:56.200 --> 00:52:01.150 align:start position:0% basically set up a IP like where a server<00:51:56.880> 7p<00:51:57.599> with<00:51:57.799> the<00:51:58.559> um<00:51:59.559> uh<00:51:59.680> with<00:51:59.839> the<00:52:00.160> port 00:52:01.150 --> 00:52:01.160 align:start position:0% server 7p with the um uh with the port 00:52:01.160 --> 00:52:02.910 align:start position:0% server 7p with the um uh with the port you<00:52:01.280> could<00:52:01.520> go<00:52:01.680> in<00:52:01.880> here<00:52:02.119> just<00:52:02.319> set<00:52:02.520> it<00:52:02.640> up<00:52:02.760> I'm 00:52:02.910 --> 00:52:02.920 align:start position:0% you could go in here just set it up I'm 00:52:02.920 --> 00:52:05.589 align:start position:0% you could go in here just set it up I'm just<00:52:03.040> going<00:52:03.160> to<00:52:03.319> put<00:52:03.640> something<00:52:04.079> in 00:52:05.589 --> 00:52:05.599 align:start position:0% just going to put something in 00:52:05.599 --> 00:52:07.910 align:start position:0% just going to put something in there<00:52:06.599> matter<00:52:06.920> it's<00:52:07.200> basically<00:52:07.599> like<00:52:07.720> a 00:52:07.910 --> 00:52:07.920 align:start position:0% there matter it's basically like a 00:52:07.920 --> 00:52:09.710 align:start position:0% there matter it's basically like a placeholder<00:52:08.520> you<00:52:08.839> then<00:52:09.040> can<00:52:09.240> connect<00:52:09.559> your 00:52:09.710 --> 00:52:09.720 align:start position:0% placeholder you then can connect your 00:52:09.720 --> 00:52:11.990 align:start position:0% placeholder you then can connect your client<00:52:10.079> with<00:52:10.760> meaning<00:52:11.119> if<00:52:11.280> I<00:52:11.440> had<00:52:11.680> another 00:52:11.990 --> 00:52:12.000 align:start position:0% client with meaning if I had another 00:52:12.000 --> 00:52:15.069 align:start position:0% client with meaning if I had another machine<00:52:12.559> with<00:52:12.720> another<00:52:13.079> IP<00:52:13.720> with<00:52:13.880> another<00:52:14.480> uh 00:52:15.069 --> 00:52:15.079 align:start position:0% machine with another IP with another uh 00:52:15.079 --> 00:52:17.470 align:start position:0% machine with another IP with another uh with<00:52:15.240> a<00:52:15.400> port<00:52:15.760> to<00:52:16.200> access<00:52:16.599> the<00:52:16.960> uh<00:52:17.119> client 00:52:17.470 --> 00:52:17.480 align:start position:0% with a port to access the uh client 00:52:17.480 --> 00:52:19.470 align:start position:0% with a port to access the uh client inside<00:52:17.799> of<00:52:17.920> my<00:52:18.079> network<00:52:18.880> I<00:52:19.000> could<00:52:19.160> run 00:52:19.470 --> 00:52:19.480 align:start position:0% inside of my network I could run 00:52:19.480 --> 00:52:21.510 align:start position:0% inside of my network I could run multiple<00:52:19.960> servers<00:52:20.559> I<00:52:20.640> could<00:52:20.839> run<00:52:21.079> multiple 00:52:21.510 --> 00:52:21.520 align:start position:0% multiple servers I could run multiple 00:52:21.520 --> 00:52:23.390 align:start position:0% multiple servers I could run multiple servers<00:52:22.040> multiple<00:52:22.520> client<00:52:22.839> pairs<00:52:23.079> on<00:52:23.240> One 00:52:23.390 --> 00:52:23.400 align:start position:0% servers multiple client pairs on One 00:52:23.400 --> 00:52:25.309 align:start position:0% servers multiple client pairs on One servers<00:52:23.760> I<00:52:23.880> can<00:52:24.040> run<00:52:24.359> execution<00:52:24.880> client<00:52:25.160> on 00:52:25.309 --> 00:52:25.319 align:start position:0% servers I can run execution client on 00:52:25.319 --> 00:52:27.069 align:start position:0% servers I can run execution client on one<00:52:25.559> server<00:52:26.119> can<00:52:26.240> run 00:52:27.069 --> 00:52:27.079 align:start position:0% one server can run 00:52:27.079 --> 00:52:29.430 align:start position:0% one server can run exe<00:52:27.720> consensus<00:52:28.160> Cent<00:52:28.400> on<00:52:28.559> another<00:52:29.040> a<00:52:29.200> valid 00:52:29.430 --> 00:52:29.440 align:start position:0% exe consensus Cent on another a valid 00:52:29.440 --> 00:52:31.510 align:start position:0% exe consensus Cent on another a valid dat<00:52:30.160> client<00:52:30.440> on<00:52:30.599> another<00:52:30.880> and<00:52:31.000> just<00:52:31.160> connect 00:52:31.510 --> 00:52:31.520 align:start position:0% dat client on another and just connect 00:52:31.520 --> 00:52:33.309 align:start position:0% dat client on another and just connect them<00:52:31.640> through<00:52:31.920> this<00:52:32.359> and<00:52:32.480> then<00:52:32.680> just<00:52:32.880> switch 00:52:33.309 --> 00:52:33.319 align:start position:0% them through this and then just switch 00:52:33.319 --> 00:52:35.910 align:start position:0% them through this and then just switch depending<00:52:33.640> on<00:52:33.880> actually<00:52:34.200> my<00:52:34.319> own<00:52:35.240> uh<00:52:35.359> needs<00:52:35.720> in 00:52:35.910 --> 00:52:35.920 align:start position:0% depending on actually my own uh needs in 00:52:35.920 --> 00:52:37.589 align:start position:0% depending on actually my own uh needs in this 00:52:37.589 --> 00:52:37.599 align:start position:0% this 00:52:37.599 --> 00:52:40.789 align:start position:0% this case<00:52:38.599> also<00:52:39.240> again<00:52:39.520> takes<00:52:39.760> a<00:52:39.880> little<00:52:40.119> bit<00:52:40.640> but 00:52:40.789 --> 00:52:40.799 align:start position:0% case also again takes a little bit but 00:52:40.799 --> 00:52:43.950 align:start position:0% case also again takes a little bit but it's<00:52:41.000> quite<00:52:41.680> fast<00:52:42.680> so<00:52:42.920> if<00:52:43.040> I<00:52:43.160> wanted<00:52:43.440> to<00:52:43.640> now 00:52:43.950 --> 00:52:43.960 align:start position:0% it's quite fast so if I wanted to now 00:52:43.960 --> 00:52:46.230 align:start position:0% it's quite fast so if I wanted to now change<00:52:44.480> use<00:52:44.839> the<00:52:45.040> external<00:52:45.480> one<00:52:45.760> I<00:52:45.839> would<00:52:46.040> go 00:52:46.230 --> 00:52:46.240 align:start position:0% change use the external one I would go 00:52:46.240 --> 00:52:48.789 align:start position:0% change use the external one I would go the<00:52:46.440> same<00:52:46.720> way<00:52:47.280> go<00:52:47.480> in<00:52:47.760> here<00:52:48.280> select<00:52:48.640> the 00:52:48.789 --> 00:52:48.799 align:start position:0% the same way go in here select the 00:52:48.799 --> 00:52:52.910 align:start position:0% the same way go in here select the external<00:52:49.240> one<00:52:50.000> confirm<00:52:51.000> uh<00:52:51.200> and<00:52:51.319> then<00:52:51.520> just<00:52:51.760> go 00:52:52.910 --> 00:52:52.920 align:start position:0% external one confirm uh and then just go 00:52:52.920 --> 00:52:56.190 align:start position:0% external one confirm uh and then just go further<00:52:53.920> so<00:52:54.480> um<00:52:55.000> David<00:52:55.319> talked<00:52:55.599> a<00:52:55.720> little<00:52:55.920> bit 00:52:56.190 --> 00:52:56.200 align:start position:0% further so um David talked a little bit 00:52:56.200 --> 00:53:01.030 align:start position:0% further so um David talked a little bit about<00:52:56.839> using<00:52:57.400> the<00:52:58.160> uh<00:52:59.160> using<00:52:59.559> the<00:53:00.359> uh<00:53:00.520> note 00:53:01.030 --> 00:53:01.040 align:start position:0% about using the uh using the uh note 00:53:01.040 --> 00:53:04.309 align:start position:0% about using the uh using the uh note export<00:53:01.880> option<00:53:02.880> uh<00:53:03.000> you<00:53:03.200> can<00:53:03.599> if<00:53:03.720> you<00:53:03.839> run<00:53:04.119> the 00:53:04.309 --> 00:53:04.319 align:start position:0% export option uh you can if you run the 00:53:04.319 --> 00:53:06.309 align:start position:0% export option uh you can if you run the setup<00:53:04.760> you<00:53:04.880> would<00:53:05.119> just<00:53:05.359> click<00:53:05.680> here<00:53:05.960> it<00:53:06.079> would 00:53:06.309 --> 00:53:06.319 align:start position:0% setup you would just click here it would 00:53:06.319 --> 00:53:08.150 align:start position:0% setup you would just click here it would basically<00:53:06.720> give<00:53:06.880> you<00:53:07.040> this<00:53:07.200> one<00:53:07.440> setup<00:53:08.000> let's 00:53:08.150 --> 00:53:08.160 align:start position:0% basically give you this one setup let's 00:53:08.160 --> 00:53:09.470 align:start position:0% basically give you this one setup let's say<00:53:08.280> you<00:53:08.359> want<00:53:08.440> to<00:53:08.559> migrate<00:53:08.960> your<00:53:09.119> node<00:53:09.359> you 00:53:09.470 --> 00:53:09.480 align:start position:0% say you want to migrate your node you 00:53:09.480 --> 00:53:11.430 align:start position:0% say you want to migrate your node you have<00:53:09.559> a<00:53:09.680> new<00:53:09.839> machine<00:53:10.440> okay<00:53:11.079> and<00:53:11.200> you're<00:53:11.319> a 00:53:11.430 --> 00:53:11.440 align:start position:0% have a new machine okay and you're a 00:53:11.440 --> 00:53:14.870 align:start position:0% have a new machine okay and you're a little<00:53:11.599> bit<00:53:11.880> lazy<00:53:12.880> you<00:53:13.000> can<00:53:13.599> uh<00:53:14.160> it<00:53:14.640> also 00:53:14.870 --> 00:53:14.880 align:start position:0% little bit lazy you can uh it also 00:53:14.880 --> 00:53:16.349 align:start position:0% little bit lazy you can uh it also doesn't<00:53:15.200> take<00:53:15.480> that<00:53:15.640> much<00:53:15.839> longer<00:53:16.160> but<00:53:16.280> you 00:53:16.349 --> 00:53:16.359 align:start position:0% doesn't take that much longer but you 00:53:16.359 --> 00:53:18.150 align:start position:0% doesn't take that much longer but you could<00:53:16.559> just<00:53:16.760> click<00:53:17.040> here<00:53:17.240> you<00:53:17.359> would<00:53:17.559> download 00:53:18.150 --> 00:53:18.160 align:start position:0% could just click here you would download 00:53:18.160 --> 00:53:20.910 align:start position:0% could just click here you would download a<00:53:18.440> zip<00:53:18.799> file<00:53:19.200> with<00:53:19.359> the<00:53:19.520> configs<00:53:20.359> you<00:53:20.520> would<00:53:20.720> go 00:53:20.910 --> 00:53:20.920 align:start position:0% a zip file with the configs you would go 00:53:20.920 --> 00:53:24.069 align:start position:0% a zip file with the configs you would go into<00:53:21.240> the<00:53:21.760> setup<00:53:22.240> again<00:53:22.920> and<00:53:23.079> then<00:53:23.200> you<00:53:23.319> can<00:53:23.920> uh 00:53:24.069 --> 00:53:24.079 align:start position:0% into the setup again and then you can uh 00:53:24.079 --> 00:53:26.069 align:start position:0% into the setup again and then you can uh just<00:53:24.359> with<00:53:24.520> the<00:53:24.720> import<00:53:25.160> config<00:53:25.559> option<00:53:25.880> just 00:53:26.069 --> 00:53:26.079 align:start position:0% just with the import config option just 00:53:26.079 --> 00:53:29.589 align:start position:0% just with the import config option just import<00:53:26.799> this<00:53:27.280> uh<00:53:27.760> ZIP<00:53:28.160> file<00:53:28.960> and<00:53:29.079> then<00:53:29.200> it<00:53:29.359> just 00:53:29.589 --> 00:53:29.599 align:start position:0% import this uh ZIP file and then it just 00:53:29.599 --> 00:53:32.069 align:start position:0% import this uh ZIP file and then it just sets<00:53:29.880> up<00:53:30.079> what<00:53:30.200> you<00:53:30.359> had<00:53:30.799> before<00:53:31.799> uh<00:53:31.880> you 00:53:32.069 --> 00:53:32.079 align:start position:0% sets up what you had before uh you 00:53:32.079 --> 00:53:34.349 align:start position:0% sets up what you had before uh you obviously<00:53:32.520> have<00:53:32.640> to<00:53:33.240> import<00:53:33.599> the<00:53:33.720> key<00:53:34.040> again 00:53:34.349 --> 00:53:34.359 align:start position:0% obviously have to import the key again 00:53:34.359 --> 00:53:35.829 align:start position:0% obviously have to import the key again because<00:53:34.640> we<00:53:34.720> don't<00:53:34.920> have<00:53:35.040> your<00:53:35.319> password<00:53:35.720> we 00:53:35.829 --> 00:53:35.839 align:start position:0% because we don't have your password we 00:53:35.839 --> 00:53:38.309 align:start position:0% because we don't have your password we don't<00:53:36.079> like<00:53:36.280> store<00:53:36.680> any<00:53:37.000> data<00:53:37.599> you<00:53:37.760> don't<00:53:37.960> send 00:53:38.309 --> 00:53:38.319 align:start position:0% don't like store any data you don't send 00:53:38.319 --> 00:53:41.510 align:start position:0% don't like store any data you don't send any<00:53:38.559> data<00:53:38.839> this<00:53:39.040> like<00:53:39.359> pure<00:53:40.359> uh<00:53:40.480> your<00:53:40.760> stuff 00:53:41.510 --> 00:53:41.520 align:start position:0% any data this like pure uh your stuff 00:53:41.520 --> 00:53:43.270 align:start position:0% any data this like pure uh your stuff and<00:53:41.920> you<00:53:42.079> also<00:53:42.280> have<00:53:42.480> the<00:53:42.599> option<00:53:42.799> to<00:53:43.119> like 00:53:43.270 --> 00:53:43.280 align:start position:0% and you also have the option to like 00:53:43.280 --> 00:53:45.549 align:start position:0% and you also have the option to like import<00:53:43.680> like<00:53:43.799> a<00:53:43.960> single<00:53:44.359> config<00:53:45.160> this<00:53:45.280> would 00:53:45.549 --> 00:53:45.559 align:start position:0% import like a single config this would 00:53:45.559 --> 00:53:48.349 align:start position:0% import like a single config this would import<00:53:46.000> all<00:53:46.160> of<00:53:46.400> them<00:53:46.920> uh<00:53:47.079> export<00:53:47.480> all<00:53:47.599> of 00:53:48.349 --> 00:53:48.359 align:start position:0% import all of them uh export all of 00:53:48.359 --> 00:53:51.230 align:start position:0% import all of them uh export all of them<00:53:49.359> um<00:53:49.640> as<00:53:49.760> you<00:53:49.839> can<00:53:50.040> also<00:53:50.240> see<00:53:50.599> we<00:53:50.760> use 00:53:51.230 --> 00:53:51.240 align:start position:0% them um as you can also see we use 00:53:51.240 --> 00:53:54.870 align:start position:0% them um as you can also see we use grafana<00:53:52.079> prito<00:53:53.079> we<00:53:53.240> have<00:53:53.480> like<00:53:53.599> a<00:53:53.920> nice<00:53:54.200> little 00:53:54.870 --> 00:53:54.880 align:start position:0% grafana prito we have like a nice little 00:53:54.880 --> 00:53:57.230 align:start position:0% grafana prito we have like a nice little uh<00:53:55.000> control<00:53:55.480> page<00:53:55.839> it's<00:53:56.200> it's<00:53:56.680> basically<00:53:57.119> it 00:53:57.230 --> 00:53:57.240 align:start position:0% uh control page it's it's basically it 00:53:57.240 --> 00:53:59.990 align:start position:0% uh control page it's it's basically it just<00:53:57.440> gives<00:53:57.599> you<00:53:57.880> basic<00:53:58.359> view<00:53:59.359> uh<00:53:59.520> with<00:53:59.720> really 00:53:59.990 --> 00:54:00.000 align:start position:0% just gives you basic view uh with really 00:54:00.000 --> 00:54:02.109 align:start position:0% just gives you basic view uh with really really<00:54:00.200> simple<00:54:00.599> stats<00:54:01.400> if<00:54:01.520> you<00:54:01.599> want<00:54:01.720> to<00:54:01.920> go 00:54:02.109 --> 00:54:02.119 align:start position:0% really simple stats if you want to go 00:54:02.119 --> 00:54:03.950 align:start position:0% really simple stats if you want to go more<00:54:02.400> complicated<00:54:03.040> you<00:54:03.160> can<00:54:03.400> always<00:54:03.720> build 00:54:03.950 --> 00:54:03.960 align:start position:0% more complicated you can always build 00:54:03.960 --> 00:54:05.750 align:start position:0% more complicated you can always build your<00:54:04.079> own<00:54:04.400> grafana<00:54:04.880> dashboards<00:54:05.359> if<00:54:05.480> you<00:54:05.599> want 00:54:05.750 --> 00:54:05.760 align:start position:0% your own grafana dashboards if you want 00:54:05.760 --> 00:54:08.670 align:start position:0% your own grafana dashboards if you want to<00:54:06.240> you<00:54:06.520> we<00:54:06.799> deliver<00:54:07.200> the<00:54:07.359> client<00:54:08.200> grafana 00:54:08.670 --> 00:54:08.680 align:start position:0% to you we deliver the client grafana 00:54:08.680 --> 00:54:10.510 align:start position:0% to you we deliver the client grafana dashboards<00:54:09.160> with<00:54:09.319> them<00:54:09.559> they<00:54:09.680> are<00:54:10.079> basically 00:54:10.510 --> 00:54:10.520 align:start position:0% dashboards with them they are basically 00:54:10.520 --> 00:54:13.430 align:start position:0% dashboards with them they are basically default<00:54:11.119> and<00:54:11.480> uh<00:54:11.599> default<00:54:11.960> to<00:54:12.119> use<00:54:13.079> uh<00:54:13.200> you<00:54:13.280> can 00:54:13.430 --> 00:54:13.440 align:start position:0% default and uh default to use uh you can 00:54:13.440 --> 00:54:15.910 align:start position:0% default and uh default to use uh you can set<00:54:13.680> the<00:54:13.880> alerts<00:54:14.200> in<00:54:14.400> grafana<00:54:15.000> you<00:54:15.119> can<00:54:15.359> like 00:54:15.910 --> 00:54:15.920 align:start position:0% set the alerts in grafana you can like 00:54:15.920 --> 00:54:17.789 align:start position:0% set the alerts in grafana you can like actually<00:54:16.280> like<00:54:16.480> get<00:54:16.640> some<00:54:17.359> external 00:54:17.789 --> 00:54:17.799 align:start position:0% actually like get some external 00:54:17.799 --> 00:54:20.910 align:start position:0% actually like get some external notification<00:54:18.599> going<00:54:18.839> on<00:54:19.040> in<00:54:19.359> there 00:54:20.910 --> 00:54:20.920 align:start position:0% notification going on in there 00:54:20.920 --> 00:54:24.270 align:start position:0% notification going on in there um<00:54:21.920> you<00:54:22.079> can<00:54:22.240> see<00:54:23.040> uh<00:54:23.160> you<00:54:23.319> have<00:54:23.559> here<00:54:23.799> the<00:54:24.160> the 00:54:24.270 --> 00:54:24.280 align:start position:0% um you can see uh you have here the the 00:54:24.280 --> 00:54:28.349 align:start position:0% um you can see uh you have here the the curent<00:54:24.599> sync<00:54:25.000> status<00:54:26.000> now<00:54:26.119> it<00:54:26.680> like<00:54:26.920> the<00:54:27.520> your 00:54:28.349 --> 00:54:28.359 align:start position:0% curent sync status now it like the your 00:54:28.359 --> 00:54:31.990 align:start position:0% curent sync status now it like the your your<00:54:28.799> noes<00:54:29.280> view<00:54:29.559> on<00:54:29.720> the<00:54:30.240> network<00:54:31.240> uh<00:54:31.480> usually 00:54:31.990 --> 00:54:32.000 align:start position:0% your noes view on the network uh usually 00:54:32.000 --> 00:54:35.390 align:start position:0% your noes view on the network uh usually I<00:54:32.119> don't<00:54:32.760> uh<00:54:33.400> recommend<00:54:34.200> taking<00:54:34.599> this<00:54:34.839> as<00:54:35.040> a 00:54:35.390 --> 00:54:35.400 align:start position:0% I don't uh recommend taking this as a 00:54:35.400 --> 00:54:37.470 align:start position:0% I don't uh recommend taking this as a how<00:54:35.520> should<00:54:35.720> I<00:54:35.880> say<00:54:36.160> as<00:54:36.680> the<00:54:36.799> most<00:54:37.040> source<00:54:37.319> of 00:54:37.470 --> 00:54:37.480 align:start position:0% how should I say as the most source of 00:54:37.480 --> 00:54:39.150 align:start position:0% how should I say as the most source of Truth<00:54:37.880> when<00:54:38.000> it<00:54:38.119> comes<00:54:38.319> to<00:54:38.480> like<00:54:38.640> the<00:54:38.760> network 00:54:39.150 --> 00:54:39.160 align:start position:0% Truth when it comes to like the network 00:54:39.160 --> 00:54:41.630 align:start position:0% Truth when it comes to like the network status<00:54:39.640> because<00:54:39.839> it's<00:54:40.040> just<00:54:40.319> your<00:54:40.599> own<00:54:41.240> notes 00:54:41.630 --> 00:54:41.640 align:start position:0% status because it's just your own notes 00:54:41.640 --> 00:54:43.589 align:start position:0% status because it's just your own notes view<00:54:41.960> on<00:54:42.119> the<00:54:42.200> network<00:54:43.079> if<00:54:43.200> you<00:54:43.280> want<00:54:43.440> to 00:54:43.589 --> 00:54:43.599 align:start position:0% view on the network if you want to 00:54:43.599 --> 00:54:46.109 align:start position:0% view on the network if you want to actually<00:54:43.839> know<00:54:44.079> the<00:54:44.799> network<00:54:45.319> status<00:54:45.880> please 00:54:46.109 --> 00:54:46.119 align:start position:0% actually know the network status please 00:54:46.119 --> 00:54:48.589 align:start position:0% actually know the network status please like<00:54:46.359> visit<00:54:46.680> peon<00:54:47.000> chart<00:54:47.240> at<00:54:47.359> the<00:54:47.480> end<00:54:48.000> great 00:54:48.589 --> 00:54:48.599 align:start position:0% like visit peon chart at the end great 00:54:48.599 --> 00:54:51.309 align:start position:0% like visit peon chart at the end great Tool<00:54:49.599> uh<00:54:49.799> you<00:54:49.880> can<00:54:50.040> see<00:54:50.520> on<00:54:50.680> the<00:54:50.839> right<00:54:51.079> side 00:54:51.309 --> 00:54:51.319 align:start position:0% Tool uh you can see on the right side 00:54:51.319 --> 00:54:54.470 align:start position:0% Tool uh you can see on the right side you<00:54:51.440> can<00:54:51.640> use<00:54:52.160> uh<00:54:52.480> you<00:54:52.640> can<00:54:53.160> uh<00:54:53.559> use<00:54:53.799> your<00:54:53.960> RPC 00:54:54.470 --> 00:54:54.480 align:start position:0% you can use uh you can uh use your RPC 00:54:54.480 --> 00:54:57.589 align:start position:0% you can use uh you can uh use your RPC provider<00:54:55.480> uh<00:54:55.599> because<00:54:55.880> steer<00:54:56.400> uses<00:54:56.680> SSH<00:54:57.400> to 00:54:57.589 --> 00:54:57.599 align:start position:0% provider uh because steer uses SSH to 00:54:57.599 --> 00:54:59.670 align:start position:0% provider uh because steer uses SSH to connect<00:54:58.079> from<00:54:58.280> your<00:54:58.440> launcher<00:54:58.880> to<00:54:59.079> your 00:54:59.670 --> 00:54:59.680 align:start position:0% connect from your launcher to your 00:54:59.680 --> 00:55:02.069 align:start position:0% connect from your launcher to your server<00:55:00.680> uh<00:55:00.799> you<00:55:00.960> have<00:55:01.079> to<00:55:01.240> open<00:55:01.480> the<00:55:01.680> tunnel 00:55:02.069 --> 00:55:02.079 align:start position:0% server uh you have to open the tunnel 00:55:02.079 --> 00:55:06.309 align:start position:0% server uh you have to open the tunnel here<00:55:03.000> uh<00:55:03.240> then<00:55:03.440> you<00:55:03.559> can<00:55:03.760> copy<00:55:04.400> this<00:55:05.400> uh<00:55:05.960> copy 00:55:06.309 --> 00:55:06.319 align:start position:0% here uh then you can copy this uh copy 00:55:06.319 --> 00:55:07.109 align:start position:0% here uh then you can copy this uh copy this 00:55:07.109 --> 00:55:07.119 align:start position:0% this 00:55:07.119 --> 00:55:09.990 align:start position:0% this string<00:55:08.119> would<00:55:08.359> put<00:55:08.599> this<00:55:08.920> for<00:55:09.160> example<00:55:09.520> into 00:55:09.990 --> 00:55:10.000 align:start position:0% string would put this for example into 00:55:10.000 --> 00:55:18.309 align:start position:0% string would put this for example into metamask<00:55:11.000> um<00:55:11.520> I<00:55:11.680> could<00:55:11.960> show 00:55:18.309 --> 00:55:18.319 align:start position:0% 00:55:18.319 --> 00:55:23.270 align:start position:0% this 00:55:23.270 --> 00:55:23.280 align:start position:0% 00:55:23.280 --> 00:55:25.789 align:start position:0% just<00:55:24.280> uh<00:55:24.400> we<00:55:24.480> would<00:55:24.640> take<00:55:24.880> this<00:55:25.079> one<00:55:25.440> you<00:55:25.559> could 00:55:25.789 --> 00:55:25.799 align:start position:0% just uh we would take this one you could 00:55:25.799 --> 00:55:28.349 align:start position:0% just uh we would take this one you could go<00:55:25.960> in<00:55:26.119> here<00:55:26.440> you<00:55:26.559> have<00:55:26.760> like<00:55:27.000> the<00:55:27.359> network 00:55:28.349 --> 00:55:28.359 align:start position:0% go in here you have like the network 00:55:28.359 --> 00:55:32.349 align:start position:0% go in here you have like the network option<00:55:29.359> if<00:55:29.480> you<00:55:29.680> go<00:55:29.880> in<00:55:30.160> here<00:55:30.680> you<00:55:30.880> go<00:55:31.079> in<00:55:31.359> here 00:55:32.349 --> 00:55:32.359 align:start position:0% option if you go in here you go in here 00:55:32.359 --> 00:55:34.670 align:start position:0% option if you go in here you go in here you<00:55:32.480> can<00:55:32.720> go<00:55:32.960> in 00:55:34.670 --> 00:55:34.680 align:start position:0% you can go in 00:55:34.680 --> 00:55:43.910 align:start position:0% you can go in here<00:55:35.680> uh<00:55:36.079> you<00:55:36.400> should<00:55:37.039> go<00:55:37.720> where<00:55:37.880> is 00:55:43.910 --> 00:55:43.920 align:start position:0% 00:55:43.920 --> 00:55:46.069 align:start position:0% it<00:55:44.920> I<00:55:45.039> haven't<00:55:45.280> done<00:55:45.440> this<00:55:45.559> in<00:55:45.680> a<00:55:45.799> while<00:55:45.960> have 00:55:46.069 --> 00:55:46.079 align:start position:0% it I haven't done this in a while have 00:55:46.079 --> 00:55:48.390 align:start position:0% it I haven't done this in a while have to<00:55:46.200> be<00:55:46.359> honest<00:55:47.319> uh<00:55:47.480> you<00:55:47.559> would<00:55:47.839> basically<00:55:48.200> go 00:55:48.390 --> 00:55:48.400 align:start position:0% to be honest uh you would basically go 00:55:48.400 --> 00:55:50.990 align:start position:0% to be honest uh you would basically go into<00:55:48.720> the<00:55:49.280> uh<00:55:49.559> options 00:55:50.990 --> 00:55:51.000 align:start position:0% into the uh options 00:55:51.000 --> 00:55:53.029 align:start position:0% into the uh options themselves 00:55:53.029 --> 00:55:53.039 align:start position:0% themselves 00:55:53.039 --> 00:55:56.670 align:start position:0% themselves uh<00:55:54.039> okay 00:55:56.670 --> 00:55:56.680 align:start position:0% uh okay 00:55:56.680 --> 00:55:58.589 align:start position:0% uh okay uh<00:55:56.799> you<00:55:56.880> would<00:55:57.160> just<00:55:57.359> put<00:55:57.559> this<00:55:57.680> for<00:55:57.920> the<00:55:58.119> RPC 00:55:58.589 --> 00:55:58.599 align:start position:0% uh you would just put this for the RPC 00:55:58.599 --> 00:56:00.710 align:start position:0% uh you would just put this for the RPC connection<00:55:59.119> you<00:55:59.200> would<00:55:59.440> put<00:55:59.680> the<00:56:00.039> E<00:56:00.319> symbol 00:56:00.710 --> 00:56:00.720 align:start position:0% connection you would put the E symbol 00:56:00.720 --> 00:56:03.470 align:start position:0% connection you would put the E symbol you<00:56:00.839> would<00:56:01.280> choose<00:56:01.799> a<00:56:02.799> uh<00:56:03.000> blockchain 00:56:03.470 --> 00:56:03.480 align:start position:0% you would choose a uh blockchain 00:56:03.480 --> 00:56:07.910 align:start position:0% you would choose a uh blockchain Explorer<00:56:04.000> to<00:56:04.280> basically<00:56:04.920> uh<00:56:05.039> show<00:56:05.280> you<00:56:05.520> the<00:56:06.520> uh 00:56:07.910 --> 00:56:07.920 align:start position:0% Explorer to basically uh show you the uh 00:56:07.920 --> 00:56:10.870 align:start position:0% Explorer to basically uh show you the uh the<00:56:08.920> uh 00:56:10.870 --> 00:56:10.880 align:start position:0% the uh 00:56:10.880 --> 00:56:14.390 align:start position:0% the uh the<00:56:11.880> the<00:56:12.000> trans<00:56:12.440> actions<00:56:13.039> and<00:56:13.480> how<00:56:13.640> they<00:56:13.760> are 00:56:14.390 --> 00:56:14.400 align:start position:0% the the trans actions and how they are 00:56:14.400 --> 00:56:19.069 align:start position:0% the the trans actions and how they are used<00:56:15.400> can<00:56:15.520> you<00:56:16.240> go 00:56:19.069 --> 00:56:19.079 align:start position:0% used can you go 00:56:19.079 --> 00:56:24.390 align:start position:0% used can you go toed<00:56:20.440> yes<00:56:21.720> okay<00:56:22.720> um<00:56:23.240> then<00:56:23.400> you<00:56:23.640> obviously<00:56:24.160> also 00:56:24.390 --> 00:56:24.400 align:start position:0% toed yes okay um then you obviously also 00:56:24.400 --> 00:56:27.789 align:start position:0% toed yes okay um then you obviously also have<00:56:24.599> the<00:56:25.079> uh<00:56:25.680> web<00:56:25.920> socket<00:56:26.359> endo<00:56:27.039> and<00:56:27.240> the<00:56:27.480> data 00:56:27.789 --> 00:56:27.799 align:start position:0% have the uh web socket endo and the data 00:56:27.799 --> 00:56:30.510 align:start position:0% have the uh web socket endo and the data API<00:56:28.640> this<00:56:28.760> one<00:56:28.960> is<00:56:29.200> from<00:56:29.520> the<00:56:30.240> this<00:56:30.359> is 00:56:30.510 --> 00:56:30.520 align:start position:0% API this one is from the this is 00:56:30.520 --> 00:56:33.710 align:start position:0% API this one is from the this is provided<00:56:30.880> by<00:56:31.119> execution<00:56:31.640> client<00:56:31.960> the<00:56:32.240> RPC<00:56:33.240> the 00:56:33.710 --> 00:56:33.720 align:start position:0% provided by execution client the RPC the 00:56:33.720 --> 00:56:35.870 align:start position:0% provided by execution client the RPC the uh<00:56:33.960> web<00:56:34.280> socket<00:56:34.599> and<00:56:34.760> the<00:56:34.920> data<00:56:35.200> API<00:56:35.559> is 00:56:35.870 --> 00:56:35.880 align:start position:0% uh web socket and the data API is 00:56:35.880 --> 00:56:38.230 align:start position:0% uh web socket and the data API is provided<00:56:36.280> by<00:56:36.440> the<00:56:36.640> consensus<00:56:37.200> client<00:56:38.000> if<00:56:38.119> you 00:56:38.230 --> 00:56:38.240 align:start position:0% provided by the consensus client if you 00:56:38.240 --> 00:56:40.349 align:start position:0% provided by the consensus client if you run<00:56:38.559> multiple<00:56:39.039> ones<00:56:39.400> you<00:56:39.520> can<00:56:39.920> uh<00:56:40.039> switch 00:56:40.349 --> 00:56:40.359 align:start position:0% run multiple ones you can uh switch 00:56:40.359 --> 00:56:43.029 align:start position:0% run multiple ones you can uh switch through<00:56:40.880> them<00:56:41.880> uh<00:56:41.960> you<00:56:42.039> can<00:56:42.280> also<00:56:42.520> see<00:56:42.760> here<00:56:42.920> a 00:56:43.029 --> 00:56:43.039 align:start position:0% through them uh you can also see here a 00:56:43.039 --> 00:56:46.670 align:start position:0% through them uh you can also see here a little<00:56:43.200> bit<00:56:43.359> of<00:56:43.640> stats<00:56:44.640> um<00:56:45.119> from<00:56:45.400> the<00:56:45.880> key<00:56:46.200> cin 00:56:46.670 --> 00:56:46.680 align:start position:0% little bit of stats um from the key cin 00:56:46.680 --> 00:56:48.710 align:start position:0% little bit of stats um from the key cin themselves<00:56:47.400> some<00:56:47.599> of<00:56:47.799> these<00:56:48.000> are<00:56:48.280> currently<00:56:48.640> a 00:56:48.710 --> 00:56:48.720 align:start position:0% themselves some of these are currently a 00:56:48.720 --> 00:56:51.270 align:start position:0% themselves some of these are currently a little<00:56:48.880> bit<00:56:49.400> uh<00:56:49.520> these<00:56:49.680> are<00:56:49.960> current<00:56:50.559> wrong 00:56:51.270 --> 00:56:51.280 align:start position:0% little bit uh these are current wrong 00:56:51.280 --> 00:56:53.309 align:start position:0% little bit uh these are current wrong because<00:56:51.839> uh<00:56:52.039> your<00:56:52.359> key<00:56:52.599> obviously<00:56:53.000> didn't 00:56:53.309 --> 00:56:53.319 align:start position:0% because uh your key obviously didn't 00:56:53.319 --> 00:56:54.710 align:start position:0% because uh your key obviously didn't like<00:56:53.480> start<00:56:53.720> the<00:56:53.880> testing<00:56:54.160> and<00:56:54.280> it<00:56:54.400> didn't<00:56:54.599> go 00:56:54.710 --> 00:56:54.720 align:start position:0% like start the testing and it didn't go 00:56:54.720 --> 00:56:56.870 align:start position:0% like start the testing and it didn't go to<00:56:54.839> the<00:56:54.960> Keys<00:56:55.280> itself<00:56:55.720> to<00:56:55.839> the<00:56:55.960> Que 00:56:56.870 --> 00:56:56.880 align:start position:0% to the Keys itself to the Que 00:56:56.880 --> 00:57:00.390 align:start position:0% to the Keys itself to the Que itself<00:56:57.880> uh<00:56:58.119> when<00:56:58.240> it<00:56:58.400> comes<00:56:58.640> to<00:56:59.200> updating<00:57:00.200> uh 00:57:00.390 --> 00:57:00.400 align:start position:0% itself uh when it comes to updating uh 00:57:00.400 --> 00:57:03.430 align:start position:0% itself uh when it comes to updating uh because<00:57:00.799> you<00:57:01.200> constantly<00:57:02.200> are<00:57:02.839> having<00:57:03.039> a<00:57:03.160> node 00:57:03.430 --> 00:57:03.440 align:start position:0% because you constantly are having a node 00:57:03.440 --> 00:57:06.230 align:start position:0% because you constantly are having a node is<00:57:03.559> a<00:57:03.799> mainten<00:57:04.319> is<00:57:04.480> mainly<00:57:05.160> maintenance<00:57:06.160> uh 00:57:06.230 --> 00:57:06.240 align:start position:0% is a mainten is mainly maintenance uh 00:57:06.240 --> 00:57:08.349 align:start position:0% is a mainten is mainly maintenance uh maintenance<00:57:06.760> is<00:57:06.920> really<00:57:07.200> really<00:57:07.480> easy<00:57:08.200> with 00:57:08.349 --> 00:57:08.359 align:start position:0% maintenance is really really easy with 00:57:08.359 --> 00:57:11.349 align:start position:0% maintenance is really really easy with steum<00:57:08.880> itself<00:57:09.799> uh<00:57:10.200> you<00:57:10.359> have<00:57:10.559> two<00:57:10.799> options<00:57:11.200> to 00:57:11.349 --> 00:57:11.359 align:start position:0% steum itself uh you have two options to 00:57:11.359 --> 00:57:14.270 align:start position:0% steum itself uh you have two options to do<00:57:11.599> this<00:57:12.119> uh<00:57:12.480> you<00:57:12.720> just<00:57:13.480> as<00:57:13.599> soon<00:57:13.799> as<00:57:14.000> there's 00:57:14.270 --> 00:57:14.280 align:start position:0% do this uh you just as soon as there's 00:57:14.280 --> 00:57:16.270 align:start position:0% do this uh you just as soon as there's upcoming<00:57:14.640> hardw<00:57:15.200> for<00:57:15.359> example<00:57:15.920> you<00:57:16.039> would 00:57:16.270 --> 00:57:16.280 align:start position:0% upcoming hardw for example you would 00:57:16.280 --> 00:57:18.910 align:start position:0% upcoming hardw for example you would just<00:57:16.559> go<00:57:16.760> in<00:57:16.960> here<00:57:17.760> and<00:57:17.920> you<00:57:18.039> can<00:57:18.359> update<00:57:18.760> like 00:57:18.910 --> 00:57:18.920 align:start position:0% just go in here and you can update like 00:57:18.920 --> 00:57:20.870 align:start position:0% just go in here and you can update like your<00:57:19.119> clients<00:57:19.599> you<00:57:19.760> have<00:57:19.920> multiple<00:57:20.520> update 00:57:20.870 --> 00:57:20.880 align:start position:0% your clients you have multiple update 00:57:20.880 --> 00:57:23.750 align:start position:0% your clients you have multiple update options<00:57:21.760> you<00:57:21.880> can<00:57:22.039> go<00:57:22.240> with<00:57:22.440> your<00:57:22.680> Ser<00:57:23.160> as 00:57:23.750 --> 00:57:23.760 align:start position:0% options you can go with your Ser as 00:57:23.760 --> 00:57:26.910 align:start position:0% options you can go with your Ser as updates<00:57:24.760> uh<00:57:24.880> you<00:57:25.039> can<00:57:25.640> uh<00:57:25.839> still<00:57:26.440> consists<00:57:26.799> of 00:57:26.910 --> 00:57:26.920 align:start position:0% updates uh you can uh still consists of 00:57:26.920 --> 00:57:28.789 align:start position:0% updates uh you can uh still consists of two<00:57:27.160> parts<00:57:27.480> the<00:57:27.599> launch<00:57:27.920> and<00:57:28.039> the<00:57:28.160> Not<00:57:28.520> So<00:57:28.680> if 00:57:28.789 --> 00:57:28.799 align:start position:0% two parts the launch and the Not So if 00:57:28.799 --> 00:57:31.029 align:start position:0% two parts the launch and the Not So if there's<00:57:28.960> a<00:57:29.119> new<00:57:29.359> theerum<00:57:30.119> release<00:57:30.760> you<00:57:30.880> will 00:57:31.029 --> 00:57:31.039 align:start position:0% there's a new theerum release you will 00:57:31.039 --> 00:57:33.109 align:start position:0% there's a new theerum release you will have<00:57:31.160> a<00:57:31.280> new<00:57:31.520> launcher<00:57:32.000> version<00:57:32.599> this<00:57:32.799> usually 00:57:33.109 --> 00:57:33.119 align:start position:0% have a new launcher version this usually 00:57:33.119 --> 00:57:35.150 align:start position:0% have a new launcher version this usually happens<00:57:33.480> as<00:57:33.559> soon<00:57:33.720> as<00:57:33.839> you<00:57:33.960> open<00:57:34.359> theum<00:57:35.000> it's 00:57:35.150 --> 00:57:35.160 align:start position:0% happens as soon as you open theum it's 00:57:35.160 --> 00:57:37.029 align:start position:0% happens as soon as you open theum it's going<00:57:35.359> to<00:57:35.520> go<00:57:35.640> into<00:57:35.880> auto<00:57:36.240> update<00:57:36.520> mode<00:57:36.880> just 00:57:37.029 --> 00:57:37.039 align:start position:0% going to go into auto update mode just 00:57:37.039 --> 00:57:38.630 align:start position:0% going to go into auto update mode just downloads<00:57:37.400> the<00:57:37.520> newest<00:57:37.799> launcher<00:57:38.160> version 00:57:38.630 --> 00:57:38.640 align:start position:0% downloads the newest launcher version 00:57:38.640 --> 00:57:41.549 align:start position:0% downloads the newest launcher version automatically<00:57:39.640> you<00:57:39.760> would<00:57:40.000> then<00:57:40.400> log<00:57:40.680> in<00:57:41.400> go 00:57:41.549 --> 00:57:41.559 align:start position:0% automatically you would then log in go 00:57:41.559 --> 00:57:43.430 align:start position:0% automatically you would then log in go into<00:57:41.760> the<00:57:41.839> node<00:57:42.200> updates<00:57:43.039> could<00:57:43.240> just 00:57:43.430 --> 00:57:43.440 align:start position:0% into the node updates could just 00:57:43.440 --> 00:57:46.510 align:start position:0% into the node updates could just download<00:57:43.799> it<00:57:44.039> here<00:57:44.880> if<00:57:45.119> there<00:57:45.319> is<00:57:45.640> a<00:57:46.119> service 00:57:46.510 --> 00:57:46.520 align:start position:0% download it here if there is a service 00:57:46.520 --> 00:57:49.309 align:start position:0% download it here if there is a service update<00:57:46.880> let's<00:57:47.079> say<00:57:47.359> GAF<00:57:47.720> has<00:57:47.880> a<00:57:48.039> new<00:57:48.599> uh<00:57:49.079> new 00:57:49.309 --> 00:57:49.319 align:start position:0% update let's say GAF has a new uh new 00:57:49.319 --> 00:57:51.430 align:start position:0% update let's say GAF has a new uh new version<00:57:49.839> you<00:57:49.960> would<00:57:50.200> see<00:57:50.359> it<00:57:50.520> in<00:57:50.839> here<00:57:51.280> you 00:57:51.430 --> 00:57:51.440 align:start position:0% version you would see it in here you 00:57:51.440 --> 00:57:53.510 align:start position:0% version you would see it in here you could<00:57:51.640> just<00:57:51.880> click<00:57:52.200> it<00:57:52.440> you<00:57:52.559> can<00:57:52.760> just<00:57:53.079> also 00:57:53.510 --> 00:57:53.520 align:start position:0% could just click it you can just also 00:57:53.520 --> 00:57:57.029 align:start position:0% could just click it you can just also update<00:57:53.920> all<00:57:54.079> of<00:57:54.319> all<00:57:54.520> at<00:57:54.720> once<00:57:55.720> uh<00:57:55.880> EX<00:57:56.480> the<00:57:56.880> uh 00:57:57.029 --> 00:57:57.039 align:start position:0% update all of all at once uh EX the uh 00:57:57.039 --> 00:57:59.789 align:start position:0% update all of all at once uh EX the uh Servo<00:57:57.440> as<00:57:57.640> updates<00:57:57.960> they<00:57:58.079> on<00:57:58.160> an<00:57:58.319> extra<00:57:58.799> page 00:57:59.789 --> 00:57:59.799 align:start position:0% Servo as updates they on an extra page 00:57:59.799 --> 00:58:02.510 align:start position:0% Servo as updates they on an extra page uh<00:57:59.880> for<00:58:00.119> good<00:58:00.319> reasons<00:58:00.880> because<00:58:01.440> um<00:58:02.200> probably 00:58:02.510 --> 00:58:02.520 align:start position:0% uh for good reasons because um probably 00:58:02.520 --> 00:58:04.589 align:start position:0% uh for good reasons because um probably is<00:58:02.640> going<00:58:02.760> to<00:58:02.880> restart<00:58:03.359> your<00:58:03.839> noes<00:58:04.400> there 00:58:04.589 --> 00:58:04.599 align:start position:0% is going to restart your noes there 00:58:04.599 --> 00:58:06.670 align:start position:0% is going to restart your noes there might<00:58:04.920> a<00:58:05.000> lot<00:58:05.160> of<00:58:05.280> people<00:58:05.480> don't<00:58:05.680> want<00:58:05.799> to<00:58:05.960> do 00:58:06.670 --> 00:58:06.680 align:start position:0% might a lot of people don't want to do 00:58:06.680 --> 00:58:09.910 align:start position:0% might a lot of people don't want to do that<00:58:07.680> um<00:58:08.400> if<00:58:08.520> you<00:58:08.680> are<00:58:08.960> really<00:58:09.240> interested<00:58:09.799> we 00:58:09.910 --> 00:58:09.920 align:start position:0% that um if you are really interested we 00:58:09.920 --> 00:58:12.430 align:start position:0% that um if you are really interested we have<00:58:10.039> a<00:58:10.160> lot<00:58:10.359> of<00:58:10.559> people<00:58:10.799> who<00:58:11.039> actually<00:58:11.839> uh<00:58:12.039> Ste 00:58:12.430 --> 00:58:12.440 align:start position:0% have a lot of people who actually uh Ste 00:58:12.440 --> 00:58:14.990 align:start position:0% have a lot of people who actually uh Ste provides<00:58:12.760> you<00:58:12.880> with<00:58:13.039> the<00:58:13.240> option<00:58:13.920> inside<00:58:14.880> of 00:58:14.990 --> 00:58:15.000 align:start position:0% provides you with the option inside of 00:58:15.000 --> 00:58:17.270 align:start position:0% provides you with the option inside of the<00:58:15.119> server<00:58:15.400> management<00:58:15.960> page<00:58:16.920> uh<00:58:17.039> you<00:58:17.119> can 00:58:17.270 --> 00:58:17.280 align:start position:0% the server management page uh you can 00:58:17.280 --> 00:58:19.230 align:start position:0% the server management page uh you can switch<00:58:17.559> through<00:58:17.799> the<00:58:17.920> servers<00:58:18.319> here<00:58:18.480> as<00:58:18.640> well 00:58:19.230 --> 00:58:19.240 align:start position:0% switch through the servers here as well 00:58:19.240 --> 00:58:21.870 align:start position:0% switch through the servers here as well uh<00:58:19.400> as<00:58:19.480> you<00:58:19.559> can<00:58:19.680> see<00:58:19.839> we<00:58:19.920> have<00:58:20.160> multiple<00:58:20.880> ones 00:58:21.870 --> 00:58:21.880 align:start position:0% uh as you can see we have multiple ones 00:58:21.880 --> 00:58:23.470 align:start position:0% uh as you can see we have multiple ones uh<00:58:22.000> you<00:58:22.119> can<00:58:22.280> also<00:58:22.480> change<00:58:22.720> your<00:58:22.960> password 00:58:23.470 --> 00:58:23.480 align:start position:0% uh you can also change your password 00:58:23.480 --> 00:58:26.829 align:start position:0% uh you can also change your password here<00:58:24.160> um<00:58:24.400> you<00:58:24.520> can<00:58:24.720> set<00:58:25.000> up<00:58:25.920> uh<00:58:26.240> you<00:58:26.319> can<00:58:26.480> create 00:58:26.829 --> 00:58:26.839 align:start position:0% here um you can set up uh you can create 00:58:26.839 --> 00:58:30.990 align:start position:0% here um you can set up uh you can create SS<00:58:27.480> SSH<00:58:28.280> key<00:58:29.000> you<00:58:29.119> can<00:58:29.599> delete<00:58:30.000> SSH<00:58:30.520> Keys<00:58:30.799> here 00:58:30.990 --> 00:58:31.000 align:start position:0% SS SSH key you can delete SSH Keys here 00:58:31.000 --> 00:58:35.029 align:start position:0% SS SSH key you can delete SSH Keys here you<00:58:31.079> can<00:58:31.240> manage<00:58:31.680> these<00:58:32.160> as<00:58:32.599> well<00:58:33.599> and<00:58:34.000> um<00:58:34.920> you 00:58:35.029 --> 00:58:35.039 align:start position:0% you can manage these as well and um you 00:58:35.039 --> 00:58:37.910 align:start position:0% you can manage these as well and um you can<00:58:35.240> do<00:58:35.440> the<00:58:35.880> upun<00:58:36.440> updates<00:58:36.960> here<00:58:37.559> just<00:58:37.799> going 00:58:37.910 --> 00:58:37.920 align:start position:0% can do the upun updates here just going 00:58:37.920 --> 00:58:40.349 align:start position:0% can do the upun updates here just going to<00:58:38.720> check<00:58:38.960> for<00:58:39.240> them<00:58:39.599> if<00:58:39.720> it's<00:58:39.839> going<00:58:39.960> to<00:58:40.079> find 00:58:40.349 --> 00:58:40.359 align:start position:0% to check for them if it's going to find 00:58:40.359 --> 00:58:41.710 align:start position:0% to check for them if it's going to find some 00:58:41.710 --> 00:58:41.720 align:start position:0% some 00:58:41.720 --> 00:58:45.390 align:start position:0% some nope<00:58:42.839> um<00:58:43.839> but<00:58:44.000> with<00:58:44.160> serum<00:58:44.559> you<00:58:44.680> have<00:58:44.839> the 00:58:45.390 --> 00:58:45.400 align:start position:0% nope um but with serum you have the 00:58:45.400 --> 00:58:47.109 align:start position:0% nope um but with serum you have the option<00:58:45.640> to<00:58:45.839> always<00:58:46.160> go<00:58:46.359> with<00:58:46.520> the<00:58:46.640> automated 00:58:47.109 --> 00:58:47.119 align:start position:0% option to always go with the automated 00:58:47.119 --> 00:58:49.109 align:start position:0% option to always go with the automated Note<00:58:47.400> updates<00:58:48.079> these<00:58:48.240> are<00:58:48.440> actually<00:58:48.720> going<00:58:48.839> to 00:58:49.109 --> 00:58:49.119 align:start position:0% Note updates these are actually going to 00:58:49.119 --> 00:58:52.710 align:start position:0% Note updates these are actually going to pull<00:58:49.480> down<00:58:49.760> all<00:58:50.079> the<00:58:50.559> um<00:58:51.200> steum<00:58:51.799> Note<00:58:52.119> updates 00:58:52.710 --> 00:58:52.720 align:start position:0% pull down all the um steum Note updates 00:58:52.720 --> 00:58:54.549 align:start position:0% pull down all the um steum Note updates and<00:58:52.880> the<00:58:53.079> client<00:58:53.440> updates<00:58:53.880> we<00:58:53.960> have<00:58:54.079> a<00:58:54.200> lot<00:58:54.359> of 00:58:54.549 --> 00:58:54.559 align:start position:0% and the client updates we have a lot of 00:58:54.559 --> 00:58:56.670 align:start position:0% and the client updates we have a lot of users<00:58:55.079> who<00:58:55.359> put<00:58:55.599> this<00:58:55.760> on<00:58:56.160> and<00:58:56.280> then<00:58:56.440> never 00:58:56.670 --> 00:58:56.680 align:start position:0% users who put this on and then never 00:58:56.680 --> 00:58:59.910 align:start position:0% users who put this on and then never look<00:58:56.880> at<00:58:57.039> it<00:58:57.280> again<00:58:58.200> uh<00:58:58.440> Works<00:58:58.880> quite<00:58:59.319> fine<00:58:59.760> we 00:58:59.910 --> 00:58:59.920 align:start position:0% look at it again uh Works quite fine we 00:58:59.920 --> 00:59:01.430 align:start position:0% look at it again uh Works quite fine we also<00:59:00.160> have<00:59:00.319> like<00:59:00.520> some<00:59:00.720> nodes<00:59:01.079> we<00:59:01.200> have<00:59:01.319> we 00:59:01.430 --> 00:59:01.440 align:start position:0% also have like some nodes we have we 00:59:01.440 --> 00:59:03.630 align:start position:0% also have like some nodes we have we have<00:59:01.640> this<00:59:01.839> open<00:59:02.359> they<00:59:02.559> still<00:59:02.799> attach<00:59:03.240> to<00:59:03.400> this 00:59:03.630 --> 00:59:03.640 align:start position:0% have this open they still attach to this 00:59:03.640 --> 00:59:07.190 align:start position:0% have this open they still attach to this day<00:59:04.440> so<00:59:04.880> um<00:59:05.480> even<00:59:05.720> if<00:59:05.839> you're<00:59:06.520> on<00:59:06.680> your<00:59:06.880> way 00:59:07.190 --> 00:59:07.200 align:start position:0% day so um even if you're on your way 00:59:07.200 --> 00:59:09.309 align:start position:0% day so um even if you're on your way let's<00:59:07.400> say<00:59:07.799> you<00:59:08.079> travel<00:59:08.440> a<00:59:08.599> lot<00:59:08.920> this<00:59:09.039> is<00:59:09.200> like 00:59:09.309 --> 00:59:09.319 align:start position:0% let's say you travel a lot this is like 00:59:09.319 --> 00:59:11.309 align:start position:0% let's say you travel a lot this is like a<00:59:09.480> easy<00:59:09.799> option<00:59:10.079> to<00:59:10.319> actually<00:59:10.920> check<00:59:11.160> your 00:59:11.309 --> 00:59:11.319 align:start position:0% a easy option to actually check your 00:59:11.319 --> 00:59:14.029 align:start position:0% a easy option to actually check your noes<00:59:11.760> you<00:59:11.880> can<00:59:12.400> uh<00:59:12.720> and<00:59:13.000> automatically<00:59:13.680> update 00:59:14.029 --> 00:59:14.039 align:start position:0% noes you can uh and automatically update 00:59:14.039 --> 00:59:15.910 align:start position:0% noes you can uh and automatically update it<00:59:14.240> without<00:59:14.599> having<00:59:14.799> to<00:59:15.119> constantly<00:59:15.680> look 00:59:15.910 --> 00:59:15.920 align:start position:0% it without having to constantly look 00:59:15.920 --> 00:59:18.950 align:start position:0% it without having to constantly look into<00:59:16.319> it<00:59:17.319> uh<00:59:17.440> we<00:59:17.559> also<00:59:17.839> have<00:59:18.000> a<00:59:18.359> experimental 00:59:18.950 --> 00:59:18.960 align:start position:0% into it uh we also have a experimental 00:59:18.960 --> 00:59:22.309 align:start position:0% into it uh we also have a experimental 2fa<00:59:19.640> feature<00:59:20.640> um<00:59:20.960> to<00:59:21.160> use<00:59:21.440> this<00:59:21.720> please<00:59:22.039> do 00:59:22.309 --> 00:59:22.319 align:start position:0% 2fa feature um to use this please do 00:59:22.319 --> 00:59:24.950 align:start position:0% 2fa feature um to use this please do actually<00:59:22.760> this<00:59:23.760> there<00:59:24.039> some<00:59:24.440> still<00:59:24.680> some 00:59:24.950 --> 00:59:24.960 align:start position:0% actually this there some still some 00:59:24.960 --> 00:59:27.069 align:start position:0% actually this there some still some problems<00:59:25.400> with<00:59:25.559> it<00:59:26.240> uh<00:59:26.359> that<00:59:26.480> we're<00:59:26.680> currently 00:59:27.069 --> 00:59:27.079 align:start position:0% problems with it uh that we're currently 00:59:27.079 --> 00:59:30.109 align:start position:0% problems with it uh that we're currently working<00:59:27.839> on<00:59:28.839> um<00:59:29.200> you<00:59:29.359> also<00:59:29.559> have<00:59:29.720> the<00:59:29.880> option 00:59:30.109 --> 00:59:30.119 align:start position:0% working on um you also have the option 00:59:30.119 --> 00:59:32.069 align:start position:0% working on um you also have the option to<00:59:30.400> like<00:59:30.680> just<00:59:30.880> add<00:59:31.039> a<00:59:31.119> new<00:59:31.280> server<00:59:31.559> connection 00:59:32.069 --> 00:59:32.079 align:start position:0% to like just add a new server connection 00:59:32.079 --> 00:59:33.870 align:start position:0% to like just add a new server connection here<00:59:32.319> you<00:59:32.400> can<00:59:32.599> switch<00:59:32.920> through<00:59:33.240> them<00:59:33.640> if<00:59:33.760> you 00:59:33.870 --> 00:59:33.880 align:start position:0% here you can switch through them if you 00:59:33.880 --> 00:59:36.190 align:start position:0% here you can switch through them if you have<00:59:34.160> SSH<00:59:34.680> key<00:59:34.960> setup<00:59:35.319> you<00:59:35.440> can<00:59:35.760> actually<00:59:36.039> go 00:59:36.190 --> 00:59:36.200 align:start position:0% have SSH key setup you can actually go 00:59:36.200 --> 00:59:38.430 align:start position:0% have SSH key setup you can actually go with<00:59:36.359> a<00:59:36.520> quick<00:59:36.839> switch<00:59:37.839> which<00:59:37.960> is<00:59:38.160> really 00:59:38.430 --> 00:59:38.440 align:start position:0% with a quick switch which is really 00:59:38.440 --> 00:59:39.470 align:start position:0% with a quick switch which is really really 00:59:39.470 --> 00:59:39.480 align:start position:0% really 00:59:39.480 --> 00:59:41.990 align:start position:0% really nice<00:59:40.480> um 00:59:41.990 --> 00:59:42.000 align:start position:0% nice um 00:59:42.000 --> 00:59:46.230 align:start position:0% nice um then<00:59:43.000> uh<00:59:43.319> with<00:59:43.520> this<00:59:43.720> is<00:59:44.039> the<00:59:44.400> update<00:59:45.240> process 00:59:46.230 --> 00:59:46.240 align:start position:0% then uh with this is the update process 00:59:46.240 --> 00:59:48.109 align:start position:0% then uh with this is the update process uh<00:59:46.359> if<00:59:46.480> you<00:59:46.760> are<00:59:46.880> a<00:59:47.000> little<00:59:47.160> bit<00:59:47.280> of<00:59:47.400> an<00:59:47.599> expert 00:59:48.109 --> 00:59:48.119 align:start position:0% uh if you are a little bit of an expert 00:59:48.119 --> 00:59:50.349 align:start position:0% uh if you are a little bit of an expert we<00:59:48.240> have<00:59:48.680> uh<00:59:48.880> the<00:59:49.119> option<00:59:49.559> for<00:59:49.760> you<00:59:49.880> to<00:59:50.079> go<00:59:50.200> into 00:59:50.349 --> 00:59:50.359 align:start position:0% we have uh the option for you to go into 00:59:50.359 --> 00:59:52.710 align:start position:0% we have uh the option for you to go into a<00:59:50.480> secure<00:59:50.760> shell<00:59:51.280> so<00:59:51.400> you<00:59:51.520> can<00:59:51.720> actually<00:59:52.039> also 00:59:52.710 --> 00:59:52.720 align:start position:0% a secure shell so you can actually also 00:59:52.720 --> 00:59:54.270 align:start position:0% a secure shell so you can actually also use<00:59:52.960> this<00:59:53.160> here<00:59:53.319> you<00:59:53.400> don't<00:59:53.760> constantly<00:59:54.160> have 00:59:54.270 --> 00:59:54.280 align:start position:0% use this here you don't constantly have 00:59:54.280 --> 00:59:57.710 align:start position:0% use this here you don't constantly have to<00:59:54.400> switch<00:59:54.799> between<00:59:55.760> uh<00:59:56.039> terminal<00:59:56.480> and<00:59:57.079> uh 00:59:57.710 --> 00:59:57.720 align:start position:0% to switch between uh terminal and uh 00:59:57.720 --> 01:00:00.230 align:start position:0% to switch between uh terminal and uh terminal<00:59:58.119> and<00:59:58.280> theerum<00:59:59.039> it's<00:59:59.480> just<00:59:59.680> for<00:59:59.920> us<01:00:00.119> we 01:00:00.230 --> 01:00:00.240 align:start position:0% terminal and theerum it's just for us we 01:00:00.240 --> 01:00:01.870 align:start position:0% terminal and theerum it's just for us we build<01:00:00.480> this<01:00:00.680> especially<01:00:01.039> for<01:00:01.280> us<01:00:01.520> because 01:00:01.870 --> 01:00:01.880 align:start position:0% build this especially for us because 01:00:01.880 --> 01:00:05.349 align:start position:0% build this especially for us because gets<01:00:02.079> annoying<01:00:02.440> after<01:00:02.680> the<01:00:02.960> well<01:00:03.960> um<01:00:04.799> then<01:00:05.200> you 01:00:05.349 --> 01:00:05.359 align:start position:0% gets annoying after the well um then you 01:00:05.359 --> 01:00:08.349 align:start position:0% gets annoying after the well um then you also<01:00:05.640> have<01:00:05.799> here<01:00:05.960> on<01:00:06.200> top<01:00:07.039> uh<01:00:07.240> a<01:00:07.599> help<01:00:07.880> button 01:00:08.349 --> 01:00:08.359 align:start position:0% also have here on top uh a help button 01:00:08.359 --> 01:00:10.710 align:start position:0% also have here on top uh a help button so<01:00:08.640> if<01:00:08.760> you<01:00:08.880> need<01:00:09.079> any<01:00:09.319> help<01:00:09.839> you<01:00:09.960> can<01:00:10.160> go<01:00:10.400> from 01:00:10.710 --> 01:00:10.720 align:start position:0% so if you need any help you can go from 01:00:10.720 --> 01:00:14.029 align:start position:0% so if you need any help you can go from here<01:00:11.440> we<01:00:11.559> have<01:00:11.799> like<01:00:12.280> uh<01:00:12.559> a<01:00:12.880> GitHub<01:00:13.359> obviously 01:00:14.029 --> 01:00:14.039 align:start position:0% here we have like uh a GitHub obviously 01:00:14.039 --> 01:00:16.670 align:start position:0% here we have like uh a GitHub obviously open<01:00:14.799> GitHub<01:00:15.200> so<01:00:15.359> if<01:00:15.440> you<01:00:15.599> find<01:00:15.799> any<01:00:16.039> mistakes 01:00:16.670 --> 01:00:16.680 align:start position:0% open GitHub so if you find any mistakes 01:00:16.680 --> 01:00:19.270 align:start position:0% open GitHub so if you find any mistakes please<01:00:17.280> be<01:00:17.440> so<01:00:17.680> kind<01:00:17.920> and<01:00:18.119> just<01:00:18.319> report<01:00:18.720> them 01:00:19.270 --> 01:00:19.280 align:start position:0% please be so kind and just report them 01:00:19.280 --> 01:00:21.549 align:start position:0% please be so kind and just report them and<01:00:19.440> we<01:00:19.559> also<01:00:19.720> have<01:00:19.839> a<01:00:20.039> documentation 01:00:21.549 --> 01:00:21.559 align:start position:0% and we also have a documentation 01:00:21.559 --> 01:00:24.029 align:start position:0% and we also have a documentation itself<01:00:22.559> um<01:00:22.760> we<01:00:22.880> also<01:00:23.079> have<01:00:23.200> the<01:00:23.359> option<01:00:23.839> for 01:00:24.029 --> 01:00:24.039 align:start position:0% itself um we also have the option for 01:00:24.039 --> 01:00:26.230 align:start position:0% itself um we also have the option for the<01:00:24.280> notification<01:00:25.280> uh<01:00:25.400> we<01:00:25.559> support<01:00:26.039> two 01:00:26.230 --> 01:00:26.240 align:start position:0% the notification uh we support two 01:00:26.240 --> 01:00:28.589 align:start position:0% the notification uh we support two things<01:00:26.799> we<01:00:26.920> have<01:00:27.079> like<01:00:27.240> a<01:00:27.920> small<01:00:28.280> little 01:00:28.589 --> 01:00:28.599 align:start position:0% things we have like a small little 01:00:28.599 --> 01:00:30.829 align:start position:0% things we have like a small little mobile<01:00:29.000> app<01:00:29.240> it's<01:00:29.440> really<01:00:29.680> really<01:00:29.920> small<01:00:30.720> uh 01:00:30.829 --> 01:00:30.839 align:start position:0% mobile app it's really really small uh 01:00:30.839 --> 01:00:33.670 align:start position:0% mobile app it's really really small uh you<01:00:31.039> basically<01:00:31.400> set<01:00:31.599> up<01:00:31.720> a<01:00:31.880> grafana<01:00:32.400> alert<01:00:33.319> um 01:00:33.670 --> 01:00:33.680 align:start position:0% you basically set up a grafana alert um 01:00:33.680 --> 01:00:36.270 align:start position:0% you basically set up a grafana alert um this<01:00:34.359> uh<01:00:34.520> this<01:00:34.680> comes<01:00:34.960> over<01:00:35.599> encrypted<01:00:36.039> over 01:00:36.270 --> 01:00:36.280 align:start position:0% this uh this comes over encrypted over 01:00:36.280 --> 01:00:38.829 align:start position:0% this uh this comes over encrypted over relay<01:00:36.640> to<01:00:36.760> us<01:00:37.280> and<01:00:37.400> we<01:00:37.599> send<01:00:37.839> this<01:00:38.039> out<01:00:38.559> but<01:00:38.680> you 01:00:38.829 --> 01:00:38.839 align:start position:0% relay to us and we send this out but you 01:00:38.839 --> 01:00:41.309 align:start position:0% relay to us and we send this out but you also<01:00:39.160> have<01:00:39.400> the<01:00:39.680> option<01:00:39.960> for<01:00:40.200> the<01:00:40.319> more<01:00:40.599> common 01:00:41.309 --> 01:00:41.319 align:start position:0% also have the option for the more common 01:00:41.319 --> 01:00:43.230 align:start position:0% also have the option for the more common what<01:00:41.559> most<01:00:41.799> people<01:00:42.079> use<01:00:42.319> this<01:00:42.680> pcking<01:00:42.960> chart 01:00:43.230 --> 01:00:43.240 align:start position:0% what most people use this pcking chart 01:00:43.240 --> 01:00:45.789 align:start position:0% what most people use this pcking chart at<01:00:43.359> the<01:00:43.480> end<01:00:44.400> it's<01:00:44.520> not<01:00:44.760> hard<01:00:45.000> to<01:00:45.200> set<01:00:45.400> up<01:00:45.599> you 01:00:45.789 --> 01:00:45.799 align:start position:0% at the end it's not hard to set up you 01:00:45.799 --> 01:00:48.069 align:start position:0% at the end it's not hard to set up you basically<01:00:46.280> click<01:00:46.599> here<01:00:47.079> then<01:00:47.200> you<01:00:47.319> would<01:00:47.799> uh 01:00:48.069 --> 01:00:48.079 align:start position:0% basically click here then you would uh 01:00:48.079 --> 01:00:50.670 align:start position:0% basically click here then you would uh then<01:00:48.200> you<01:00:48.319> would<01:00:49.079> select<01:00:49.960> you<01:00:50.119> validate<01:00:50.520> the 01:00:50.670 --> 01:00:50.680 align:start position:0% then you would select you validate the 01:00:50.680 --> 01:00:53.470 align:start position:0% then you would select you validate the client<01:00:51.039> here<01:00:51.520> set<01:00:51.720> the<01:00:51.920> machine<01:00:52.480> and<01:00:52.720> API<01:00:53.160> key 01:00:53.470 --> 01:00:53.480 align:start position:0% client here set the machine and API key 01:00:53.480 --> 01:00:55.510 align:start position:0% client here set the machine and API key up<01:00:54.000> you<01:00:54.160> have<01:00:54.280> to<01:00:54.480> set<01:00:54.640> the<01:00:54.760> API<01:00:55.160> key<01:00:55.319> on<01:00:55.400> the 01:00:55.510 --> 01:00:55.520 align:start position:0% up you have to set the API key on the 01:00:55.520 --> 01:01:00.190 align:start position:0% up you have to set the API key on the PAC<01:00:56.280> to<01:00:56.839> website<01:00:57.720> itself<01:00:58.720> um<01:00:59.000> then<01:00:59.400> the<01:00:59.920> um 01:01:00.190 --> 01:01:00.200 align:start position:0% PAC to website itself um then the um 01:01:00.200 --> 01:01:01.789 align:start position:0% PAC to website itself um then the um updates<01:01:00.520> are<01:01:00.680> already 01:01:01.789 --> 01:01:01.799 align:start position:0% updates are already 01:01:01.799 --> 01:01:04.589 align:start position:0% updates are already showed<01:01:02.799> and<01:01:03.280> uh<01:01:03.440> you<01:01:03.559> have<01:01:03.720> also<01:01:04.039> the<01:01:04.200> settings 01:01:04.589 --> 01:01:04.599 align:start position:0% showed and uh you have also the settings 01:01:04.599 --> 01:01:06.750 align:start position:0% showed and uh you have also the settings you<01:01:04.720> can<01:01:04.839> change<01:01:05.119> some<01:01:05.359> languages<01:01:05.880> we<01:01:06.039> didn't 01:01:06.750 --> 01:01:06.760 align:start position:0% you can change some languages we didn't 01:01:06.760 --> 01:01:10.390 align:start position:0% you can change some languages we didn't uh<01:01:07.760> uh<01:01:08.079> we<01:01:08.240> don't<01:01:08.799> we<01:01:09.359> translate<01:01:09.960> as<01:01:10.079> much<01:01:10.280> as 01:01:10.390 --> 01:01:10.400 align:start position:0% uh uh we don't we translate as much as 01:01:10.400 --> 01:01:12.710 align:start position:0% uh uh we don't we translate as much as we<01:01:10.599> can<01:01:11.039> so<01:01:11.359> um<01:01:11.520> if<01:01:11.640> you<01:01:11.760> are<01:01:12.000> not<01:01:12.400> English 01:01:12.710 --> 01:01:12.720 align:start position:0% we can so um if you are not English 01:01:12.720 --> 01:01:14.470 align:start position:0% we can so um if you are not English speaker<01:01:13.000> and<01:01:13.119> know<01:01:13.319> someone<01:01:13.559> is<01:01:13.720> not<01:01:14.200> quite 01:01:14.470 --> 01:01:14.480 align:start position:0% speaker and know someone is not quite 01:01:14.480 --> 01:01:16.069 align:start position:0% speaker and know someone is not quite that<01:01:14.799> much<01:01:14.960> of<01:01:15.079> an<01:01:15.240> English<01:01:15.520> speaker<01:01:15.839> you<01:01:15.920> can 01:01:16.069 --> 01:01:16.079 align:start position:0% that much of an English speaker you can 01:01:16.079 --> 01:01:19.470 align:start position:0% that much of an English speaker you can also<01:01:16.319> use<01:01:17.039> this<01:01:18.039> and 01:01:19.470 --> 01:01:19.480 align:start position:0% also use this and 01:01:19.480 --> 01:01:23.150 align:start position:0% also use this and yeah<01:01:20.480> uh<01:01:21.039> the<01:01:21.240> option<01:01:21.720> maybe<01:01:22.200> if<01:01:22.319> you<01:01:22.440> run<01:01:22.680> into 01:01:23.150 --> 01:01:23.160 align:start position:0% yeah uh the option maybe if you run into 01:01:23.160 --> 01:01:25.750 align:start position:0% yeah uh the option maybe if you run into problems<01:01:23.920> uh<01:01:24.119> what<01:01:24.280> we<01:01:24.480> usually<01:01:24.839> do<01:01:25.240> or<01:01:25.440> I<01:01:25.640> at 01:01:25.750 --> 01:01:25.760 align:start position:0% problems uh what we usually do or I at 01:01:25.760 --> 01:01:28.349 align:start position:0% problems uh what we usually do or I at least<01:01:26.119> usually<01:01:26.480> do<01:01:27.480> um<01:01:27.640> if<01:01:27.799> there's<01:01:28.200> like 01:01:28.349 --> 01:01:28.359 align:start position:0% least usually do um if there's like 01:01:28.359 --> 01:01:31.270 align:start position:0% least usually do um if there's like something<01:01:28.640> breaking<01:01:29.039> my<01:01:29.240> notes<01:01:29.760> I'm<01:01:30.039> a<01:01:30.960> I'm<01:01:31.079> a 01:01:31.270 --> 01:01:31.280 align:start position:0% something breaking my notes I'm a I'm a 01:01:31.280 --> 01:01:34.109 align:start position:0% something breaking my notes I'm a I'm a All<01:01:31.520> or<01:01:31.720> Nothing<01:01:32.200> kind<01:01:32.359> of<01:01:32.680> guy<01:01:33.280> um<01:01:33.480> I<01:01:33.599> like<01:01:33.880> to 01:01:34.109 --> 01:01:34.119 align:start position:0% All or Nothing kind of guy um I like to 01:01:34.119 --> 01:01:37.109 align:start position:0% All or Nothing kind of guy um I like to just<01:01:34.319> nuke<01:01:34.680> the<01:01:34.799> notes<01:01:35.720> um<01:01:36.280> we<01:01:36.440> just<01:01:36.680> basically 01:01:37.109 --> 01:01:37.119 align:start position:0% just nuke the notes um we just basically 01:01:37.119 --> 01:01:40.150 align:start position:0% just nuke the notes um we just basically press<01:01:37.640> here<01:01:38.640> and<01:01:39.039> this<01:01:39.280> kills<01:01:39.640> the<01:01:39.799> whole 01:01:40.150 --> 01:01:40.160 align:start position:0% press here and this kills the whole 01:01:40.160 --> 01:01:41.789 align:start position:0% press here and this kills the whole thing<01:01:40.599> you<01:01:40.720> can<01:01:40.880> dump<01:01:41.119> your<01:01:41.280> locks<01:01:41.559> here<01:01:41.680> as 01:01:41.789 --> 01:01:41.799 align:start position:0% thing you can dump your locks here as 01:01:41.799 --> 01:01:44.349 align:start position:0% thing you can dump your locks here as well<01:01:42.799> and<01:01:43.039> as<01:01:43.160> soon<01:01:43.319> as<01:01:43.440> I<01:01:43.599> click<01:01:43.880> this<01:01:44.160> it's 01:01:44.349 --> 01:01:44.359 align:start position:0% well and as soon as I click this it's 01:01:44.359 --> 01:01:46.870 align:start position:0% well and as soon as I click this it's just<01:01:44.520> going<01:01:44.640> to<01:01:44.839> delete<01:01:45.240> everything<01:01:45.599> on<01:01:45.880> there 01:01:46.870 --> 01:01:46.880 align:start position:0% just going to delete everything on there 01:01:46.880 --> 01:01:49.349 align:start position:0% just going to delete everything on there it<01:01:47.000> takes<01:01:47.240> a<01:01:47.359> little<01:01:47.760> bit<01:01:48.760> uh<01:01:48.920> it's<01:01:49.079> quite<01:01:49.240> a 01:01:49.349 --> 01:01:49.359 align:start position:0% it takes a little bit uh it's quite a 01:01:49.359 --> 01:01:52.990 align:start position:0% it takes a little bit uh it's quite a nice<01:01:49.559> animation<01:01:50.319> you<01:01:50.520> can<01:01:51.000> than<01:01:51.640> that<01:01:51.880> guy<01:01:52.520> for 01:01:52.990 --> 01:01:53.000 align:start position:0% nice animation you can than that guy for 01:01:53.000 --> 01:01:56.069 align:start position:0% nice animation you can than that guy for that<01:01:54.000> um<01:01:54.799> just<01:01:55.000> takes<01:01:55.240> a<01:01:55.400> little<01:01:55.599> bit<01:01:55.960> I'm 01:01:56.069 --> 01:01:56.079 align:start position:0% that um just takes a little bit I'm 01:01:56.079 --> 01:01:57.750 align:start position:0% that um just takes a little bit I'm going<01:01:56.200> to<01:01:56.400> then<01:01:56.839> uh<01:01:56.920> show<01:01:57.119> you<01:01:57.319> some<01:01:57.480> of<01:01:57.640> the 01:01:57.750 --> 01:01:57.760 align:start position:0% going to then uh show you some of the 01:01:57.760 --> 01:01:59.630 align:start position:0% going to then uh show you some of the other<01:01:58.000> options<01:01:58.359> we<01:01:58.520> have<01:01:58.680> as<01:01:58.799> well<01:01:59.279> like<01:01:59.440> just 01:01:59.630 --> 01:01:59.640 align:start position:0% other options we have as well like just 01:01:59.640 --> 01:02:02.150 align:start position:0% other options we have as well like just go<01:01:59.799> through<01:02:00.039> them<01:02:00.200> one<01:02:00.400> by<01:02:00.559> one<01:02:00.799> and<01:02:00.960> then<01:02:01.920> uh<01:02:02.039> I 01:02:02.150 --> 01:02:02.160 align:start position:0% go through them one by one and then uh I 01:02:02.160 --> 01:02:03.870 align:start position:0% go through them one by one and then uh I guess<01:02:02.279> in<01:02:02.480> 5<01:02:02.680> minutes<01:02:03.000> if<01:02:03.079> you<01:02:03.200> have<01:02:03.440> like<01:02:03.559> some 01:02:03.870 --> 01:02:03.880 align:start position:0% guess in 5 minutes if you have like some 01:02:03.880 --> 01:02:07.349 align:start position:0% guess in 5 minutes if you have like some questions<01:02:04.240> I<01:02:04.400> would<01:02:04.559> love<01:02:05.440> to<01:02:05.839> to<01:02:06.359> answer<01:02:06.680> them 01:02:07.349 --> 01:02:07.359 align:start position:0% questions I would love to to answer them 01:02:07.359 --> 01:02:11.910 align:start position:0% questions I would love to to answer them all<01:02:08.400> so<01:02:09.400> um 01:02:11.910 --> 01:02:11.920 align:start position:0% all so um 01:02:11.920 --> 01:02:15.630 align:start position:0% all so um just<01:02:12.920> just<01:02:13.119> go<01:02:13.400> down<01:02:13.640> to<01:02:13.920> this<01:02:14.079> node<01:02:14.520> again<01:02:15.520> uh 01:02:15.630 --> 01:02:15.640 align:start position:0% just just go down to this node again uh 01:02:15.640 --> 01:02:17.150 align:start position:0% just just go down to this node again uh this<01:02:15.760> is 01:02:17.150 --> 01:02:17.160 align:start position:0% this is 01:02:17.160 --> 01:02:20.349 align:start position:0% this is now<01:02:18.160> this<01:02:18.319> is<01:02:18.440> now<01:02:18.559> a<01:02:18.680> nuke<01:02:19.000> node<01:02:19.359> meaning<01:02:20.000> if<01:02:20.160> I 01:02:20.349 --> 01:02:20.359 align:start position:0% now this is now a nuke node meaning if I 01:02:20.359 --> 01:02:22.630 align:start position:0% now this is now a nuke node meaning if I as<01:02:20.480> soon<01:02:20.640> as<01:02:20.760> I<01:02:20.880> go<01:02:21.079> in<01:02:21.240> here<01:02:21.440> I<01:02:21.599> go<01:02:22.279> basically 01:02:22.630 --> 01:02:22.640 align:start position:0% as soon as I go in here I go basically 01:02:22.640 --> 01:02:24.230 align:start position:0% as soon as I go in here I go basically through<01:02:22.839> the<01:02:22.960> whole<01:02:23.200> process<01:02:23.599> again<01:02:24.079> it's 01:02:24.230 --> 01:02:24.240 align:start position:0% through the whole process again it's 01:02:24.240 --> 01:02:26.109 align:start position:0% through the whole process again it's just<01:02:24.359> going<01:02:24.480> to<01:02:24.640> check<01:02:24.839> is<01:02:24.960> there<01:02:25.240> not 01:02:26.109 --> 01:02:26.119 align:start position:0% just going to check is there not 01:02:26.119 --> 01:02:28.069 align:start position:0% just going to check is there not installed<01:02:26.680> if<01:02:26.839> there<01:02:26.960> is<01:02:27.119> no<01:02:27.319> not<01:02:27.599> installed 01:02:28.069 --> 01:02:28.079 align:start position:0% installed if there is no not installed 01:02:28.079 --> 01:02:29.630 align:start position:0% installed if there is no not installed I'm<01:02:28.240> just<01:02:28.359> going<01:02:28.480> to<01:02:28.680> go<01:02:28.960> through<01:02:29.240> through 01:02:29.630 --> 01:02:29.640 align:start position:0% I'm just going to go through through 01:02:29.640 --> 01:02:33.549 align:start position:0% I'm just going to go through through this<01:02:29.920> page<01:02:30.599> again<01:02:31.599> uh<01:02:32.400> the<01:02:32.599> options<01:02:33.319> are 01:02:33.549 --> 01:02:33.559 align:start position:0% this page again uh the options are 01:02:33.559 --> 01:02:36.630 align:start position:0% this page again uh the options are pretty<01:02:33.920> pretty<01:02:34.720> simple<01:02:35.720> uh<01:02:36.119> this<01:02:36.319> case<01:02:36.520> I 01:02:36.630 --> 01:02:36.640 align:start position:0% pretty pretty simple uh this case I 01:02:36.640 --> 01:02:38.670 align:start position:0% pretty pretty simple uh this case I don't<01:02:36.880> have<01:02:37.119> much<01:02:37.520> time<01:02:37.880> sadly<01:02:38.279> to<01:02:38.400> show<01:02:38.559> you 01:02:38.670 --> 01:02:38.680 align:start position:0% don't have much time sadly to show you 01:02:38.680 --> 01:02:40.829 align:start position:0% don't have much time sadly to show you the<01:02:38.839> other<01:02:39.160> stuff<01:02:39.880> uh<01:02:40.000> if<01:02:40.079> you're<01:02:40.319> interested 01:02:40.829 --> 01:02:40.839 align:start position:0% the other stuff uh if you're interested 01:02:40.839 --> 01:02:43.069 align:start position:0% the other stuff uh if you're interested we<01:02:40.960> can<01:02:41.119> always<01:02:41.359> talk<01:02:41.599> about<01:02:41.880> it<01:02:42.599> uh<01:02:42.760> but<01:02:42.880> the 01:02:43.069 --> 01:02:43.079 align:start position:0% we can always talk about it uh but the 01:02:43.079 --> 01:02:45.230 align:start position:0% we can always talk about it uh but the basic<01:02:43.440> like<01:02:43.680> difference<01:02:44.079> is<01:02:44.920> uh<01:02:45.039> this 01:02:45.230 --> 01:02:45.240 align:start position:0% basic like difference is uh this 01:02:45.240 --> 01:02:48.390 align:start position:0% basic like difference is uh this installs<01:02:45.760> a<01:02:46.599> extra<01:02:47.000> valid<01:02:47.279> dat<01:02:47.520> client<01:02:47.839> SSV 01:02:48.390 --> 01:02:48.400 align:start position:0% installs a extra valid dat client SSV 01:02:48.400 --> 01:02:50.990 align:start position:0% installs a extra valid dat client SSV uses<01:02:48.960> not<01:02:49.160> the<01:02:49.400> standard<01:02:49.880> valid<01:02:50.119> dat<01:02:50.400> client 01:02:50.990 --> 01:02:51.000 align:start position:0% uses not the standard valid dat client 01:02:51.000 --> 01:02:52.630 align:start position:0% uses not the standard valid dat client they<01:02:51.119> use<01:02:51.359> their<01:02:51.520> own<01:02:51.720> valid<01:02:52.039> dat<01:02:52.240> client<01:02:52.520> to 01:02:52.630 --> 01:02:52.640 align:start position:0% they use their own valid dat client to 01:02:52.640 --> 01:02:55.549 align:start position:0% they use their own valid dat client to do<01:02:52.839> this<01:02:53.599> uh<01:02:53.720> obal<01:02:54.079> uses<01:02:54.359> an<01:02:54.559> extra<01:02:55.039> service 01:02:55.549 --> 01:02:55.559 align:start position:0% do this uh obal uses an extra service 01:02:55.559 --> 01:02:57.589 align:start position:0% do this uh obal uses an extra service that<01:02:55.680> is<01:02:55.839> is<01:02:56.039> connected<01:02:56.559> to<01:02:56.680> your<01:02:56.839> validator 01:02:57.589 --> 01:02:57.599 align:start position:0% that is is connected to your validator 01:02:57.599 --> 01:03:00.069 align:start position:0% that is is connected to your validator client<01:02:58.599> so<01:02:58.960> if<01:02:59.039> you<01:02:59.240> go<01:02:59.400> in<01:02:59.599> here<01:02:59.760> you<01:02:59.880> would 01:03:00.069 --> 01:03:00.079 align:start position:0% client so if you go in here you would 01:03:00.079 --> 01:03:00.870 align:start position:0% client so if you go in here you would like 01:03:00.870 --> 01:03:00.880 align:start position:0% like 01:03:00.880 --> 01:03:04.549 align:start position:0% like see<01:03:01.880> here<01:03:02.319> this<01:03:02.839> installs<01:03:03.200> the<01:03:03.359> OBO<01:03:03.640> Shon<01:03:04.160> Serv 01:03:04.549 --> 01:03:04.559 align:start position:0% see here this installs the OBO Shon Serv 01:03:04.559 --> 01:03:05.829 align:start position:0% see here this installs the OBO Shon Serv Shon 01:03:05.829 --> 01:03:05.839 align:start position:0% Shon 01:03:05.839 --> 01:03:10.150 align:start position:0% Shon Service<01:03:06.839> uh<01:03:07.119> then<01:03:07.720> uh<01:03:07.880> the<01:03:08.359> steum<01:03:08.960> arm<01:03:09.520> you<01:03:09.680> can 01:03:10.150 --> 01:03:10.160 align:start position:0% Service uh then uh the steum arm you can 01:03:10.160 --> 01:03:13.109 align:start position:0% Service uh then uh the steum arm you can uh<01:03:10.480> basically<01:03:11.480> uh<01:03:11.640> this<01:03:11.839> is<01:03:12.440> installing<01:03:12.960> just 01:03:13.109 --> 01:03:13.119 align:start position:0% uh basically uh this is installing just 01:03:13.119 --> 01:03:16.589 align:start position:0% uh basically uh this is installing just the<01:03:13.319> node<01:03:13.599> clients<01:03:14.240> without<01:03:15.079> uh<01:03:15.319> monitoring 01:03:16.589 --> 01:03:16.599 align:start position:0% the node clients without uh monitoring 01:03:16.599 --> 01:03:19.029 align:start position:0% the node clients without uh monitoring Services<01:03:17.599> uh<01:03:17.720> the<01:03:17.839> archive<01:03:18.319> node<01:03:18.640> usually 01:03:19.029 --> 01:03:19.039 align:start position:0% Services uh the archive node usually 01:03:19.039 --> 01:03:21.349 align:start position:0% Services uh the archive node usually just<01:03:19.240> sets<01:03:19.799> extra<01:03:20.279> stuff<01:03:20.520> in<01:03:20.680> your<01:03:20.960> expert 01:03:21.349 --> 01:03:21.359 align:start position:0% just sets extra stuff in your expert 01:03:21.359 --> 01:03:23.789 align:start position:0% just sets extra stuff in your expert mode<01:03:21.720> config<01:03:22.359> so<01:03:22.520> you<01:03:22.720> actually<01:03:23.039> retain<01:03:23.559> the 01:03:23.789 --> 01:03:23.799 align:start position:0% mode config so you actually retain the 01:03:23.799 --> 01:03:27.589 align:start position:0% mode config so you actually retain the blockchain<01:03:24.440> data<01:03:25.440> uh<01:03:25.599> and<01:03:25.799> the<01:03:25.920> LI<01:03:26.640> CS<01:03:27.279> uh<01:03:27.480> the 01:03:27.589 --> 01:03:27.599 align:start position:0% blockchain data uh and the LI CS uh the 01:03:27.599 --> 01:03:32.789 align:start position:0% blockchain data uh and the LI CS uh the LI<01:03:27.920> stvm<01:03:29.000> modules<01:03:30.000> uh<01:03:30.200> both<01:03:30.480> use<01:03:31.160> SSV<01:03:32.079> or<01:03:32.680> um 01:03:32.789 --> 01:03:32.799 align:start position:0% LI stvm modules uh both use SSV or um 01:03:32.799 --> 01:03:35.630 align:start position:0% LI stvm modules uh both use SSV or um obal<01:03:33.559> respectively<01:03:34.559> and<01:03:34.760> in<01:03:34.880> the<01:03:35.000> end<01:03:35.240> we<01:03:35.400> also 01:03:35.630 --> 01:03:35.640 align:start position:0% obal respectively and in the end we also 01:03:35.640 --> 01:03:36.950 align:start position:0% obal respectively and in the end we also have<01:03:35.880> the<01:03:36.039> LI 01:03:36.950 --> 01:03:36.960 align:start position:0% have the LI 01:03:36.960 --> 01:03:40.670 align:start position:0% have the LI CSM<01:03:37.960> uh<01:03:38.119> itself<01:03:38.880> where<01:03:39.039> we<01:03:39.200> have<01:03:39.400> like<01:03:39.680> a<01:03:40.520> uh 01:03:40.670 --> 01:03:40.680 align:start position:0% CSM uh itself where we have like a uh 01:03:40.680 --> 01:03:43.190 align:start position:0% CSM uh itself where we have like a uh the<01:03:41.119> valid<01:03:41.480> dat<01:03:41.799> check<01:03:42.079> the<01:03:42.240> lighter<01:03:42.559> users<01:03:43.079> we 01:03:43.190 --> 01:03:43.200 align:start position:0% the valid dat check the lighter users we 01:03:43.200 --> 01:03:46.230 align:start position:0% the valid dat check the lighter users we have<01:03:43.480> the<01:03:43.799> lighter<01:03:44.200> Keys<01:03:44.480> API<01:03:45.319> and<01:03:45.480> the<01:03:45.760> CSM 01:03:46.230 --> 01:03:46.240 align:start position:0% have the lighter Keys API and the CSM 01:03:46.240 --> 01:03:48.430 align:start position:0% have the lighter Keys API and the CSM monitoring<01:03:46.760> service<01:03:47.119> we<01:03:47.240> built<01:03:47.520> for<01:03:47.720> this<01:03:48.279> as 01:03:48.430 --> 01:03:48.440 align:start position:0% monitoring service we built for this as 01:03:48.440 --> 01:03:50.589 align:start position:0% monitoring service we built for this as well<01:03:48.599> as<01:03:48.760> an<01:03:49.000> ipfs<01:03:49.559> service<01:03:49.920> to<01:03:50.079> just<01:03:50.279> keep<01:03:50.480> the 01:03:50.589 --> 01:03:50.599 align:start position:0% well as an ipfs service to just keep the 01:03:50.599 --> 01:03:52.190 align:start position:0% well as an ipfs service to just keep the data 01:03:52.190 --> 01:03:52.200 align:start position:0% data 01:03:52.200 --> 01:03:54.309 align:start position:0% data forward 01:03:54.309 --> 01:03:54.319 align:start position:0% forward 01:03:54.319 --> 01:03:56.549 align:start position:0% forward so<01:03:55.319> okay 01:03:56.549 --> 01:03:56.559 align:start position:0% so okay 01:03:56.559 --> 01:03:59.230 align:start position:0% so okay okay<01:03:57.559> um<01:03:57.839> with<01:03:58.039> this<01:03:58.240> I<01:03:58.359> would<01:03:58.520> say<01:03:58.880> like<01:03:59.079> we 01:03:59.230 --> 01:03:59.240 align:start position:0% okay um with this I would say like we 01:03:59.240 --> 01:04:02.309 align:start position:0% okay um with this I would say like we have<01:03:59.400> like<01:03:59.599> 15<01:04:00.000> minutes<01:04:00.440> left<01:04:01.200> um<01:04:02.000> I<01:04:02.079> would 01:04:02.309 --> 01:04:02.319 align:start position:0% have like 15 minutes left um I would 01:04:02.319 --> 01:04:04.269 align:start position:0% have like 15 minutes left um I would love<01:04:02.799> uh<01:04:02.920> if<01:04:03.039> you<01:04:03.240> any<01:04:03.359> of<01:04:03.480> you<01:04:03.640> guys<01:04:03.880> have<01:04:04.039> any 01:04:04.269 --> 01:04:04.279 align:start position:0% love uh if you any of you guys have any 01:04:04.279 --> 01:04:06.589 align:start position:0% love uh if you any of you guys have any questions<01:04:05.160> um<01:04:05.680> we're<01:04:05.799> going<01:04:05.880> to<01:04:06.079> answer<01:04:06.400> them 01:04:06.589 --> 01:04:06.599 align:start position:0% questions um we're going to answer them 01:04:06.599 --> 01:04:09.470 align:start position:0% questions um we're going to answer them all<01:04:07.599> uh<01:04:08.240> m<01:04:08.520> is<01:04:08.640> going<01:04:08.720> to<01:04:08.839> help<01:04:09.000> me<01:04:09.119> with<01:04:09.240> more 01:04:09.470 --> 01:04:09.480 align:start position:0% all uh m is going to help me with more 01:04:09.480 --> 01:04:11.829 align:start position:0% all uh m is going to help me with more technical<01:04:10.319> questions<01:04:10.799> it's<01:04:11.000> not<01:04:11.359> quite<01:04:11.559> my 01:04:11.829 --> 01:04:11.839 align:start position:0% technical questions it's not quite my 01:04:11.839 --> 01:04:18.589 align:start position:0% technical questions it's not quite my for<01:04:12.760> so 01:04:18.589 --> 01:04:18.599 align:start position:0% 01:04:18.599 --> 01:04:23.230 align:start position:0% um<01:04:19.640> I<01:04:20.640> uh<01:04:20.839> when<01:04:20.960> you<01:04:21.160> use<01:04:21.920> uh<01:04:22.400> this<01:04:22.680> installer 01:04:23.230 --> 01:04:23.240 align:start position:0% um I uh when you use uh this installer 01:04:23.240 --> 01:04:25.910 align:start position:0% um I uh when you use uh this installer for<01:04:23.599> arm<01:04:24.000> devices<01:04:24.920> when<01:04:25.039> you<01:04:25.200> would<01:04:25.400> like<01:04:25.720> to 01:04:25.910 --> 01:04:25.920 align:start position:0% for arm devices when you would like to 01:04:25.920 --> 01:04:29.990 align:start position:0% for arm devices when you would like to deploy<01:04:26.760> an<01:04:27.400> ethereum<01:04:27.839> node<01:04:28.079> on<01:04:28.279> arm<01:04:29.000> devices 01:04:29.990 --> 01:04:30.000 align:start position:0% deploy an ethereum node on arm devices 01:04:30.000 --> 01:04:32.109 align:start position:0% deploy an ethereum node on arm devices uh<01:04:30.480> because<01:04:30.960> you<01:04:31.160> have<01:04:31.400> very<01:04:31.640> limited 01:04:32.109 --> 01:04:32.119 align:start position:0% uh because you have very limited 01:04:32.119 --> 01:04:34.349 align:start position:0% uh because you have very limited resources<01:04:32.920> resources<01:04:33.440> for<01:04:33.760> example<01:04:34.119> on 01:04:34.349 --> 01:04:34.359 align:start position:0% resources resources for example on 01:04:34.359 --> 01:04:38.549 align:start position:0% resources resources for example on Raspberry<01:04:34.839> Pi<01:04:35.480> 5<01:04:36.480> uh<01:04:37.079> I<01:04:37.279> guess<01:04:37.559> you<01:04:37.880> have 01:04:38.549 --> 01:04:38.559 align:start position:0% Raspberry Pi 5 uh I guess you have 01:04:38.559 --> 01:04:42.150 align:start position:0% Raspberry Pi 5 uh I guess you have limited<01:04:39.480> uh<01:04:39.640> options<01:04:40.480> about<01:04:41.440> execution<01:04:41.960> and 01:04:42.150 --> 01:04:42.160 align:start position:0% limited uh options about execution and 01:04:42.160 --> 01:04:45.150 align:start position:0% limited uh options about execution and consensus<01:04:42.599> clients<01:04:43.520> and<01:04:43.799> I'm<01:04:44.160> curious<01:04:45.000> which 01:04:45.150 --> 01:04:45.160 align:start position:0% consensus clients and I'm curious which 01:04:45.160 --> 01:04:46.950 align:start position:0% consensus clients and I'm curious which one<01:04:45.400> you<01:04:45.599> recommend<01:04:46.000> or<01:04:46.240> which<01:04:46.400> one<01:04:46.559> you<01:04:46.720> use 01:04:46.950 --> 01:04:46.960 align:start position:0% one you recommend or which one you use 01:04:46.960 --> 01:04:48.349 align:start position:0% one you recommend or which one you use as 01:04:48.349 --> 01:04:48.359 align:start position:0% as 01:04:48.359 --> 01:04:51.470 align:start position:0% as default 01:04:51.470 --> 01:04:51.480 align:start position:0% 01:04:51.480 --> 01:04:55.430 align:start position:0% um<01:04:52.480> so<01:04:53.079> um<01:04:53.319> I<01:04:53.480> actually<01:04:53.720> set<01:04:53.960> that<01:04:54.160> up<01:04:54.880> um<01:04:55.279> quite 01:04:55.430 --> 01:04:55.440 align:start position:0% um so um I actually set that up um quite 01:04:55.440 --> 01:04:58.910 align:start position:0% um so um I actually set that up um quite a<01:04:55.760> while<01:04:55.920> ago<01:04:56.480> it<01:04:56.599> was<01:04:56.760> back<01:04:56.920> in<01:04:57.079> girly<01:04:57.960> and<01:04:58.720> um 01:04:58.910 --> 01:04:58.920 align:start position:0% a while ago it was back in girly and um 01:04:58.920 --> 01:05:02.870 align:start position:0% a while ago it was back in girly and um what<01:04:59.079> I<01:04:59.240> used<01:04:59.799> was<01:05:00.680> G<01:05:01.400> and<01:05:01.799> Nimbus<01:05:02.319> Nimbus<01:05:02.720> is 01:05:02.870 --> 01:05:02.880 align:start position:0% what I used was G and Nimbus Nimbus is 01:05:02.880 --> 01:05:05.710 align:start position:0% what I used was G and Nimbus Nimbus is very<01:05:03.079> very<01:05:03.279> lightweight<01:05:04.279> um<01:05:05.240> and<01:05:05.400> especially 01:05:05.710 --> 01:05:05.720 align:start position:0% very very lightweight um and especially 01:05:05.720 --> 01:05:08.029 align:start position:0% very very lightweight um and especially if<01:05:05.799> you<01:05:05.880> run<01:05:06.079> on<01:05:06.240> like<01:05:06.400> these<01:05:06.520> small<01:05:07.039> devices 01:05:08.029 --> 01:05:08.039 align:start position:0% if you run on like these small devices 01:05:08.039 --> 01:05:10.069 align:start position:0% if you run on like these small devices um<01:05:08.400> running<01:05:08.680> on<01:05:08.880> arm<01:05:09.480> I<01:05:09.559> would<01:05:09.720> recommend 01:05:10.069 --> 01:05:10.079 align:start position:0% um running on arm I would recommend 01:05:10.079 --> 01:05:16.069 align:start position:0% um running on arm I would recommend nimus<01:05:10.480> for<01:05:11.000> these<01:05:11.160> kind<01:05:11.319> of<01:05:11.640> cases<01:05:12.920> um<01:05:13.920> but<01:05:15.079> um 01:05:16.069 --> 01:05:16.079 align:start position:0% nimus for these kind of cases um but um 01:05:16.079 --> 01:05:17.910 align:start position:0% nimus for these kind of cases um but um it<01:05:16.240> depends<01:05:16.839> it<01:05:17.000> it<01:05:17.160> really<01:05:17.359> depends<01:05:17.760> this 01:05:17.910 --> 01:05:17.920 align:start position:0% it depends it it really depends this 01:05:17.920 --> 01:05:20.029 align:start position:0% it depends it it really depends this machine<01:05:18.279> was<01:05:18.680> like<01:05:18.839> even<01:05:19.039> a<01:05:19.200> smaller<01:05:19.720> spe<01:05:19.920> it 01:05:20.029 --> 01:05:20.039 align:start position:0% machine was like even a smaller spe it 01:05:20.039 --> 01:05:23.230 align:start position:0% machine was like even a smaller spe it had<01:05:20.200> like<01:05:20.359> only<01:05:20.960> 4<01:05:21.400> GB<01:05:21.960> of<01:05:22.240> RAM<01:05:22.680> and<01:05:22.799> it<01:05:22.960> took 01:05:23.230 --> 01:05:23.240 align:start position:0% had like only 4 GB of RAM and it took 01:05:23.240 --> 01:05:25.789 align:start position:0% had like only 4 GB of RAM and it took like<01:05:23.440> two<01:05:23.760> months<01:05:24.200> to<01:05:24.480> say<01:05:24.880> I<01:05:25.119> two<01:05:25.279> months<01:05:25.480> to 01:05:25.789 --> 01:05:25.799 align:start position:0% like two months to say I two months to 01:05:25.799 --> 01:05:29.309 align:start position:0% like two months to say I two months to weeks<01:05:26.000> to<01:05:26.119> sy<01:05:27.240> so<01:05:28.240> probably<01:05:28.520> not<01:05:28.680> the<01:05:28.880> best<01:05:29.160> but 01:05:29.309 --> 01:05:29.319 align:start position:0% weeks to sy so probably not the best but 01:05:29.319 --> 01:05:33.069 align:start position:0% weeks to sy so probably not the best but if<01:05:29.400> you're<01:05:29.680> like<01:05:29.920> a<01:05:30.200> have<01:05:30.359> a<01:05:30.559> be<01:05:31.440> um<01:05:31.720> device<01:05:32.520> um 01:05:33.069 --> 01:05:33.079 align:start position:0% if you're like a have a be um device um 01:05:33.079 --> 01:05:35.990 align:start position:0% if you're like a have a be um device um you<01:05:33.319> can<01:05:33.480> have<01:05:33.680> like<01:05:33.839> more<01:05:34.039> options<01:05:34.440> open<01:05:35.119> um 01:05:35.990 --> 01:05:36.000 align:start position:0% you can have like more options open um 01:05:36.000 --> 01:05:38.470 align:start position:0% you can have like more options open um maybe<01:05:36.359> even<01:05:36.960> um<01:05:37.200> nether<01:05:37.599> mind<01:05:37.960> or<01:05:38.279> like 01:05:38.470 --> 01:05:38.480 align:start position:0% maybe even um nether mind or like 01:05:38.480 --> 01:05:40.990 align:start position:0% maybe even um nether mind or like depending<01:05:38.920> you<01:05:39.079> have<01:05:39.200> would<01:05:39.319> have<01:05:39.480> them<01:05:39.760> to<01:05:40.359> um 01:05:40.990 --> 01:05:41.000 align:start position:0% depending you have would have them to um 01:05:41.000 --> 01:05:43.470 align:start position:0% depending you have would have them to um experiment<01:05:41.559> with<01:05:41.760> all<01:05:41.960> with<01:05:42.119> all<01:05:42.319> the<01:05:43.279> um 01:05:43.470 --> 01:05:43.480 align:start position:0% experiment with all with all the um 01:05:43.480 --> 01:05:46.430 align:start position:0% experiment with all with all the um settings<01:05:44.119> steum<01:05:44.559> provides<01:05:44.880> you<01:05:45.559> um<01:05:45.839> or<01:05:46.240> all 01:05:46.430 --> 01:05:46.440 align:start position:0% settings steum provides you um or all 01:05:46.440 --> 01:05:48.349 align:start position:0% settings steum provides you um or all the<01:05:46.839> different<01:05:47.119> clients<01:05:47.480> nethermind<01:05:47.960> for 01:05:48.349 --> 01:05:48.359 align:start position:0% the different clients nethermind for 01:05:48.359 --> 01:05:51.190 align:start position:0% the different clients nethermind for example<01:05:49.359> um<01:05:49.920> Run's<01:05:50.279> great<01:05:50.599> but<01:05:50.799> if<01:05:50.920> it<01:05:51.039> comes 01:05:51.190 --> 01:05:51.200 align:start position:0% example um Run's great but if it comes 01:05:51.200 --> 01:05:53.829 align:start position:0% example um Run's great but if it comes to<01:05:51.319> pruning<01:05:51.760> you<01:05:51.880> will<01:05:52.400> probably<01:05:52.880> have<01:05:53.039> to<01:05:53.640> um 01:05:53.829 --> 01:05:53.839 align:start position:0% to pruning you will probably have to um 01:05:53.839 --> 01:05:56.630 align:start position:0% to pruning you will probably have to um reduce<01:05:54.240> the<01:05:54.440> used<01:05:54.760> load<01:05:55.160> while<01:05:55.359> pruning 01:05:56.630 --> 01:05:56.640 align:start position:0% reduce the used load while pruning 01:05:56.640 --> 01:05:59.390 align:start position:0% reduce the used load while pruning um<01:05:57.119> but<01:05:57.760> yeah<01:05:58.279> it<01:05:58.359> is<01:05:58.559> possible<01:05:58.960> you're 01:05:59.390 --> 01:05:59.400 align:start position:0% um but yeah it is possible you're 01:05:59.400 --> 01:06:03.069 align:start position:0% um but yeah it is possible you're limited<01:06:00.400> um<01:06:01.160> but<01:06:01.359> it's<01:06:01.520> definitely 01:06:03.069 --> 01:06:03.079 align:start position:0% limited um but it's definitely 01:06:03.079 --> 01:06:05.829 align:start position:0% limited um but it's definitely possible<01:06:04.079> one<01:06:04.200> more<01:06:04.480> question<01:06:04.880> about<01:06:05.400> path<01:06:05.680> to 01:06:05.829 --> 01:06:05.839 align:start position:0% possible one more question about path to 01:06:05.839 --> 01:06:09.230 align:start position:0% possible one more question about path to the<01:06:06.039> storage<01:06:06.680> this<01:06:06.839> two<01:06:07.000> terab<01:06:07.640> Drive<01:06:08.640> uh<01:06:09.039> when 01:06:09.230 --> 01:06:09.240 align:start position:0% the storage this two terab Drive uh when 01:06:09.240 --> 01:06:12.549 align:start position:0% the storage this two terab Drive uh when I<01:06:09.480> would<01:06:09.720> like<01:06:09.920> to<01:06:10.160> use<01:06:10.960> uh<01:06:11.760> two<01:06:11.960> drives<01:06:12.400> one 01:06:12.549 --> 01:06:12.559 align:start position:0% I would like to use uh two drives one 01:06:12.559 --> 01:06:15.069 align:start position:0% I would like to use uh two drives one for<01:06:13.400> uh<01:06:13.640> operating<01:06:14.079> system<01:06:14.440> and<01:06:14.640> the<01:06:14.799> second 01:06:15.069 --> 01:06:15.079 align:start position:0% for uh operating system and the second 01:06:15.079 --> 01:06:17.549 align:start position:0% for uh operating system and the second one<01:06:15.319> for<01:06:15.520> the<01:06:15.680> blockchain<01:06:16.119> copy<01:06:17.039> uh<01:06:17.160> can<01:06:17.319> I 01:06:17.549 --> 01:06:17.559 align:start position:0% one for the blockchain copy uh can I 01:06:17.559 --> 01:06:21.510 align:start position:0% one for the blockchain copy uh can I provide<01:06:18.559> um<01:06:19.079> a<01:06:19.279> path<01:06:19.960> where<01:06:20.319> the<01:06:20.520> blockchain 01:06:21.510 --> 01:06:21.520 align:start position:0% provide um a path where the blockchain 01:06:21.520 --> 01:06:24.230 align:start position:0% provide um a path where the blockchain uh<01:06:21.839> should<01:06:22.039> be<01:06:22.160> stored<01:06:22.880> if<01:06:23.039> the<01:06:23.240> partition<01:06:23.960> is 01:06:24.230 --> 01:06:24.240 align:start position:0% uh should be stored if the partition is 01:06:24.240 --> 01:06:26.109 align:start position:0% uh should be stored if the partition is um<01:06:24.400> correctly<01:06:24.760> mounted<01:06:25.160> this<01:06:25.279> is<01:06:25.640> definitely 01:06:26.109 --> 01:06:26.119 align:start position:0% um correctly mounted this is definitely 01:06:26.119 --> 01:06:28.230 align:start position:0% um correctly mounted this is definitely possible<01:06:26.480> steer<01:06:26.839> room<01:06:27.079> will<01:06:27.319> check<01:06:27.920> um<01:06:28.039> your 01:06:28.230 --> 01:06:28.240 align:start position:0% possible steer room will check um your 01:06:28.240 --> 01:06:31.029 align:start position:0% possible steer room will check um your petitions<01:06:28.799> and<01:06:29.000> will<01:06:29.200> use<01:06:29.559> the<01:06:29.960> biggest<01:06:30.319> one 01:06:31.029 --> 01:06:31.039 align:start position:0% petitions and will use the biggest one 01:06:31.039 --> 01:06:31.990 align:start position:0% petitions and will use the biggest one um<01:06:31.200> out<01:06:31.319> of 01:06:31.990 --> 01:06:32.000 align:start position:0% um out of 01:06:32.000 --> 01:06:34.870 align:start position:0% um out of default<01:06:33.000> um<01:06:33.559> but<01:06:33.680> you<01:06:33.799> can<01:06:34.079> change<01:06:34.359> it<01:06:34.520> up<01:06:34.760> the 01:06:34.870 --> 01:06:34.880 align:start position:0% default um but you can change it up the 01:06:34.880 --> 01:06:39.750 align:start position:0% default um but you can change it up the way<01:06:35.039> you<01:06:35.319> want<01:06:36.319> okay<01:06:36.559> thank 01:06:39.750 --> 01:06:39.760 align:start position:0% 01:06:39.760 --> 01:06:46.029 align:start position:0% you<01:06:40.760> uh<01:06:40.920> do<01:06:41.000> we<01:06:41.079> have<01:06:41.240> another 01:06:46.029 --> 01:06:46.039 align:start position:0% 01:06:46.039 --> 01:06:49.430 align:start position:0% question<01:06:47.039> okay<01:06:47.920> perfect 01:06:49.430 --> 01:06:49.440 align:start position:0% question okay perfect 01:06:49.440 --> 01:06:53.950 align:start position:0% question okay perfect so<01:06:50.440> all<01:06:50.799> so<01:06:51.359> uh<01:06:51.880> thanks<01:06:52.200> for<01:06:52.440> the<01:06:52.960> presentation 01:06:53.950 --> 01:06:53.960 align:start position:0% so all so uh thanks for the presentation 01:06:53.960 --> 01:06:56.990 align:start position:0% so all so uh thanks for the presentation um<01:06:54.279> quick<01:06:55.039> I<01:06:55.119> mean<01:06:55.359> I<01:06:55.799> if<01:06:55.960> let's<01:06:56.119> say<01:06:56.279> you<01:06:56.480> have 01:06:56.990 --> 01:06:57.000 align:start position:0% um quick I mean I if let's say you have 01:06:57.000 --> 01:06:59.309 align:start position:0% um quick I mean I if let's say you have more<01:06:57.200> than<01:06:57.359> one<01:06:57.599> validator<01:06:58.240> key<01:06:58.640> or<01:06:59.000> sorry<01:06:59.240> you 01:06:59.309 --> 01:06:59.319 align:start position:0% more than one validator key or sorry you 01:06:59.319 --> 01:07:01.029 align:start position:0% more than one validator key or sorry you want<01:06:59.440> to<01:06:59.520> run<01:06:59.720> more<01:06:59.880> than<01:07:00.039> one 01:07:01.029 --> 01:07:01.039 align:start position:0% want to run more than one 01:07:01.039 --> 01:07:04.789 align:start position:0% want to run more than one uh<01:07:02.039> uh<01:07:02.640> the<01:07:02.839> terminology<01:07:03.839> eludes<01:07:04.240> me<01:07:04.440> a<01:07:04.559> bit 01:07:04.789 --> 01:07:04.799 align:start position:0% uh uh the terminology eludes me a bit 01:07:04.799 --> 01:07:06.630 align:start position:0% uh uh the terminology eludes me a bit but<01:07:05.160> let's<01:07:05.279> say<01:07:05.400> you've<01:07:05.559> got<01:07:05.680> 64<01:07:06.160> eth<01:07:06.480> you<01:07:06.559> want 01:07:06.630 --> 01:07:06.640 align:start position:0% but let's say you've got 64 eth you want 01:07:06.640 --> 01:07:09.309 align:start position:0% but let's say you've got 64 eth you want to<01:07:06.799> run<01:07:07.160> two<01:07:07.799> validators<01:07:08.799> is<01:07:08.880> it<01:07:09.079> best 01:07:09.309 --> 01:07:09.319 align:start position:0% to run two validators is it best 01:07:09.319 --> 01:07:11.750 align:start position:0% to run two validators is it best practice<01:07:09.599> to<01:07:09.760> run<01:07:09.920> it<01:07:10.319> on<01:07:10.559> two<01:07:10.920> separate 01:07:11.750 --> 01:07:11.760 align:start position:0% practice to run it on two separate 01:07:11.760 --> 01:07:13.430 align:start position:0% practice to run it on two separate completely<01:07:12.200> separate<01:07:12.520> things<01:07:12.799> or<01:07:12.960> is<01:07:13.039> it<01:07:13.240> best 01:07:13.430 --> 01:07:13.440 align:start position:0% completely separate things or is it best 01:07:13.440 --> 01:07:15.829 align:start position:0% completely separate things or is it best practice<01:07:13.839> just<01:07:13.960> to<01:07:14.119> use<01:07:14.520> one<01:07:15.160> sort<01:07:15.359> of<01:07:15.520> setup 01:07:15.829 --> 01:07:15.839 align:start position:0% practice just to use one sort of setup 01:07:15.839 --> 01:07:19.750 align:start position:0% practice just to use one sort of setup for<01:07:16.119> both<01:07:16.960> keys<01:07:17.599> I<01:07:17.680> would<01:07:17.920> I<01:07:18.000> would<01:07:18.440> um<01:07:19.119> so<01:07:19.599> the 01:07:19.750 --> 01:07:19.760 align:start position:0% for both keys I would I would um so the 01:07:19.760 --> 01:07:23.750 align:start position:0% for both keys I would I would um so the valid<01:07:20.319> client<01:07:20.720> can<01:07:21.480> in<01:07:21.839> theory<01:07:22.480> hold<01:07:23.119> infinite 01:07:23.750 --> 01:07:23.760 align:start position:0% valid client can in theory hold infinite 01:07:23.760 --> 01:07:28.190 align:start position:0% valid client can in theory hold infinite valid<01:07:24.119> dator<01:07:24.400> Keys<01:07:25.400> uh<01:07:25.599> um<01:07:25.760> are<01:07:26.319> usually<01:07:27.319> uh 01:07:28.190 --> 01:07:28.200 align:start position:0% valid dator Keys uh um are usually uh 01:07:28.200 --> 01:07:29.990 align:start position:0% valid dator Keys uh um are usually uh the<01:07:28.359> more<01:07:28.599> validate<01:07:29.039> the<01:07:29.200> keys<01:07:29.440> you<01:07:29.599> import 01:07:29.990 --> 01:07:30.000 align:start position:0% the more validate the keys you import 01:07:30.000 --> 01:07:31.589 align:start position:0% the more validate the keys you import into<01:07:30.200> the<01:07:30.319> client<01:07:30.640> the<01:07:30.720> more<01:07:30.960> resources<01:07:31.480> it 01:07:31.589 --> 01:07:31.599 align:start position:0% into the client the more resources it 01:07:31.599 --> 01:07:34.710 align:start position:0% into the client the more resources it will<01:07:31.839> use<01:07:32.200> to<01:07:32.680> basically<01:07:33.680> sign<01:07:33.960> for<01:07:34.200> them 01:07:34.710 --> 01:07:34.720 align:start position:0% will use to basically sign for them 01:07:34.720 --> 01:07:36.029 align:start position:0% will use to basically sign for them because<01:07:34.920> it<01:07:35.119> like<01:07:35.279> has<01:07:35.440> to<01:07:35.599> sign<01:07:35.799> and<01:07:35.920> then 01:07:36.029 --> 01:07:36.039 align:start position:0% because it like has to sign and then 01:07:36.039 --> 01:07:38.069 align:start position:0% because it like has to sign and then send<01:07:36.240> this<01:07:36.359> to<01:07:36.480> the<01:07:36.599> consensus<01:07:37.079> client<01:07:37.680> but 01:07:38.069 --> 01:07:38.079 align:start position:0% send this to the consensus client but 01:07:38.079 --> 01:07:40.309 align:start position:0% send this to the consensus client but you<01:07:38.240> you<01:07:38.359> will<01:07:38.520> not<01:07:38.839> notice<01:07:39.359> this<01:07:39.920> until<01:07:40.160> you 01:07:40.309 --> 01:07:40.319 align:start position:0% you you will not notice this until you 01:07:40.319 --> 01:07:43.349 align:start position:0% you you will not notice this until you have<01:07:40.520> like<01:07:40.680> a<01:07:40.880> 100<01:07:41.319> keys<01:07:41.680> on<01:07:41.880> one<01:07:42.160> note<01:07:43.160> uh 01:07:43.349 --> 01:07:43.359 align:start position:0% have like a 100 keys on one note uh 01:07:43.359 --> 01:07:46.269 align:start position:0% have like a 100 keys on one note uh which<01:07:43.480> is<01:07:43.760> quite<01:07:44.160> rare<01:07:44.480> for<01:07:44.720> some<01:07:45.640> people<01:07:46.000> for 01:07:46.269 --> 01:07:46.279 align:start position:0% which is quite rare for some people for 01:07:46.279 --> 01:07:49.750 align:start position:0% which is quite rare for some people for obvious<01:07:46.880> reasons<01:07:47.880> um<01:07:48.440> so<01:07:48.760> I<01:07:48.880> would<01:07:49.200> recommend 01:07:49.750 --> 01:07:49.760 align:start position:0% obvious reasons um so I would recommend 01:07:49.760 --> 01:07:52.190 align:start position:0% obvious reasons um so I would recommend you<01:07:50.000> actually<01:07:50.319> to<01:07:50.559> use<01:07:50.960> one<01:07:51.440> machine<01:07:51.920> because 01:07:52.190 --> 01:07:52.200 align:start position:0% you actually to use one machine because 01:07:52.200 --> 01:07:54.950 align:start position:0% you actually to use one machine because you<01:07:52.680> run<01:07:53.160> the<01:07:53.359> problem<01:07:53.720> is<01:07:54.520> uh<01:07:54.680> the<01:07:54.799> your 01:07:54.950 --> 01:07:54.960 align:start position:0% you run the problem is uh the your 01:07:54.960 --> 01:07:57.269 align:start position:0% you run the problem is uh the your biggest<01:07:55.520> risk<01:07:55.839> is<01:07:55.960> the<01:07:56.119> slashing<01:07:56.680> risk<01:07:57.039> and<01:07:57.200> if 01:07:57.269 --> 01:07:57.279 align:start position:0% biggest risk is the slashing risk and if 01:07:57.279 --> 01:07:59.549 align:start position:0% biggest risk is the slashing risk and if you<01:07:57.480> for<01:07:57.720> example<01:07:58.079> forget<01:07:58.640> which<01:07:59.079> key<01:07:59.319> you 01:07:59.549 --> 01:07:59.559 align:start position:0% you for example forget which key you 01:07:59.559 --> 01:08:01.430 align:start position:0% you for example forget which key you import<01:08:00.000> in<01:08:00.160> which<01:08:00.359> client<01:08:00.839> you<01:08:01.039> could<01:08:01.200> always 01:08:01.430 --> 01:08:01.440 align:start position:0% import in which client you could always 01:08:01.440 --> 01:08:04.150 align:start position:0% import in which client you could always like<01:08:01.680> a<01:08:01.799> human<01:08:02.200> error<01:08:02.559> is<01:08:02.720> your<01:08:03.039> biggest<01:08:03.480> enemy 01:08:04.150 --> 01:08:04.160 align:start position:0% like a human error is your biggest enemy 01:08:04.160 --> 01:08:06.789 align:start position:0% like a human error is your biggest enemy basically<01:08:05.160> uh<01:08:05.440> so<01:08:05.760> having<01:08:06.039> them<01:08:06.200> on<01:08:06.359> the<01:08:06.520> same 01:08:06.789 --> 01:08:06.799 align:start position:0% basically uh so having them on the same 01:08:06.799 --> 01:08:09.109 align:start position:0% basically uh so having them on the same machine<01:08:07.359> is<01:08:07.599> probably<01:08:08.039> like<01:08:08.240> the<01:08:08.480> best<01:08:08.760> way<01:08:08.920> to 01:08:09.109 --> 01:08:09.119 align:start position:0% machine is probably like the best way to 01:08:09.119 --> 01:08:13.069 align:start position:0% machine is probably like the best way to go<01:08:09.559> in<01:08:09.720> this<01:08:09.960> case 01:08:13.069 --> 01:08:13.079 align:start position:0% 01:08:13.079 --> 01:08:16.990 align:start position:0% and<01:08:14.079> one<01:08:14.319> quick<01:08:14.640> followup<01:08:15.079> to<01:08:15.240> that<01:08:15.440> then<01:08:16.279> um 01:08:16.990 --> 01:08:17.000 align:start position:0% and one quick followup to that then um 01:08:17.000 --> 01:08:19.870 align:start position:0% and one quick followup to that then um by<01:08:17.159> running<01:08:17.839> two<01:08:18.560> validators<01:08:19.080> on<01:08:19.239> the<01:08:19.319> same 01:08:19.870 --> 01:08:19.880 align:start position:0% by running two validators on the same 01:08:19.880 --> 01:08:21.789 align:start position:0% by running two validators on the same client<01:08:20.239> are<01:08:20.400> you<01:08:20.600> running<01:08:20.880> a<01:08:21.080> risk<01:08:21.319> of<01:08:21.560> both 01:08:21.789 --> 01:08:21.799 align:start position:0% client are you running a risk of both 01:08:21.799 --> 01:08:24.110 align:start position:0% client are you running a risk of both being<01:08:22.040> slashed<01:08:22.520> at<01:08:22.640> the<01:08:22.759> same<01:08:23.040> time<01:08:23.679> or<01:08:23.920> would 01:08:24.110 --> 01:08:24.120 align:start position:0% being slashed at the same time or would 01:08:24.120 --> 01:08:26.430 align:start position:0% being slashed at the same time or would all<01:08:24.319> it<01:08:24.400> would<01:08:24.560> only<01:08:24.799> be<01:08:25.560> one<01:08:25.719> or<01:08:25.880> the<01:08:26.000> other<01:08:26.279> in 01:08:26.430 --> 01:08:26.440 align:start position:0% all it would only be one or the other in 01:08:26.440 --> 01:08:29.709 align:start position:0% all it would only be one or the other in most<01:08:26.719> cases<01:08:27.560> um<01:08:27.880> the<01:08:28.199> so<01:08:29.199> you<01:08:29.359> you<01:08:29.480> don't 01:08:29.709 --> 01:08:29.719 align:start position:0% most cases um the so you you don't 01:08:29.719 --> 01:08:31.510 align:start position:0% most cases um the so you you don't really<01:08:29.920> run<01:08:30.279> a<01:08:30.560> if<01:08:30.679> you<01:08:30.920> just<01:08:31.120> have<01:08:31.319> one 01:08:31.510 --> 01:08:31.520 align:start position:0% really run a if you just have one 01:08:31.520 --> 01:08:33.349 align:start position:0% really run a if you just have one validated<01:08:32.120> client<01:08:32.480> and<01:08:32.600> you<01:08:32.839> only<01:08:33.040> have<01:08:33.199> these 01:08:33.349 --> 01:08:33.359 align:start position:0% validated client and you only have these 01:08:33.359 --> 01:08:35.229 align:start position:0% validated client and you only have these two<01:08:33.560> keys<01:08:33.839> in<01:08:34.000> this<01:08:34.159> one<01:08:34.480> client<01:08:34.799> there's<01:08:35.000> no 01:08:35.229 --> 01:08:35.239 align:start position:0% two keys in this one client there's no 01:08:35.239 --> 01:08:37.189 align:start position:0% two keys in this one client there's no risk<01:08:35.440> of<01:08:35.600> getting<01:08:35.799> slashed<01:08:36.239> whatsoever<01:08:37.000> the 01:08:37.189 --> 01:08:37.199 align:start position:0% risk of getting slashed whatsoever the 01:08:37.199 --> 01:08:39.110 align:start position:0% risk of getting slashed whatsoever the risk<01:08:37.400> of<01:08:37.560> getting<01:08:37.759> slashed<01:08:38.199> is<01:08:38.319> for<01:08:38.520> example 01:08:39.110 --> 01:08:39.120 align:start position:0% risk of getting slashed is for example 01:08:39.120 --> 01:08:40.910 align:start position:0% risk of getting slashed is for example if<01:08:39.199> you<01:08:39.319> have<01:08:39.520> both<01:08:39.839> the<01:08:40.040> as<01:08:40.159> you<01:08:40.480> described 01:08:40.910 --> 01:08:40.920 align:start position:0% if you have both the as you described 01:08:40.920 --> 01:08:43.229 align:start position:0% if you have both the as you described your<01:08:41.080> scenario<01:08:41.880> if<01:08:42.000> you<01:08:42.120> have<01:08:42.319> both<01:08:42.520> of<01:08:42.759> these 01:08:43.229 --> 01:08:43.239 align:start position:0% your scenario if you have both of these 01:08:43.239 --> 01:08:45.309 align:start position:0% your scenario if you have both of these notes<01:08:43.560> running<01:08:44.040> okay<01:08:44.440> and<01:08:44.560> for<01:08:44.759> some<01:08:45.000> reason 01:08:45.309 --> 01:08:45.319 align:start position:0% notes running okay and for some reason 01:08:45.319 --> 01:08:48.149 align:start position:0% notes running okay and for some reason you<01:08:45.480> forget<01:08:46.080> which<01:08:46.359> key<01:08:46.600> you<01:08:46.719> had<01:08:46.920> on<01:08:47.159> which<01:08:47.799> uh 01:08:48.149 --> 01:08:48.159 align:start position:0% you forget which key you had on which uh 01:08:48.159 --> 01:08:50.349 align:start position:0% you forget which key you had on which uh which<01:08:48.359> client<01:08:48.880> and<01:08:49.000> you<01:08:49.199> import<01:08:49.719> this<01:08:49.960> again 01:08:50.349 --> 01:08:50.359 align:start position:0% which client and you import this again 01:08:50.359 --> 01:08:52.309 align:start position:0% which client and you import this again okay<01:08:50.960> it's<01:08:51.080> going<01:08:51.199> to<01:08:51.400> warn<01:08:51.679> you<01:08:52.000> okay<01:08:52.199> it's 01:08:52.309 --> 01:08:52.319 align:start position:0% okay it's going to warn you okay it's 01:08:52.319 --> 01:08:55.709 align:start position:0% okay it's going to warn you okay it's going<01:08:52.440> to<01:08:52.600> tell<01:08:52.759> you<01:08:53.480> hey<01:08:54.480> the<01:08:55.080> double<01:08:55.440> G<01:08:55.600> of 01:08:55.709 --> 01:08:55.719 align:start position:0% going to tell you hey the double G of 01:08:55.719 --> 01:08:57.149 align:start position:0% going to tell you hey the double G of protection<01:08:56.000> is<01:08:56.120> going<01:08:56.239> to<01:08:56.319> say<01:08:56.640> Hey<01:08:56.799> you<01:08:56.920> are 01:08:57.149 --> 01:08:57.159 align:start position:0% protection is going to say Hey you are 01:08:57.159 --> 01:09:01.030 align:start position:0% protection is going to say Hey you are like<01:08:57.600> testing<01:08:57.960> the<01:08:58.120> last<01:08:58.359> two<01:08:59.080> uh<01:08:59.400> epos<01:09:00.400> uh<01:09:00.759> but 01:09:01.030 --> 01:09:01.040 align:start position:0% like testing the last two uh epos uh but 01:09:01.040 --> 01:09:03.070 align:start position:0% like testing the last two uh epos uh but if<01:09:01.159> you<01:09:01.480> if<01:09:01.600> you<01:09:01.799> just<01:09:02.040> like<01:09:02.199> mindlessly<01:09:02.839> click 01:09:03.070 --> 01:09:03.080 align:start position:0% if you if you just like mindlessly click 01:09:03.080 --> 01:09:05.189 align:start position:0% if you if you just like mindlessly click through<01:09:03.400> this<01:09:03.759> okay<01:09:04.279> you<01:09:04.679> you're<01:09:04.839> going<01:09:05.000> to 01:09:05.189 --> 01:09:05.199 align:start position:0% through this okay you you're going to 01:09:05.199 --> 01:09:06.950 align:start position:0% through this okay you you're going to get<01:09:05.359> SL<01:09:05.719> you're<01:09:05.839> going<01:09:05.960> to<01:09:06.120> get<01:09:06.239> slashed<01:09:06.679> just 01:09:06.950 --> 01:09:06.960 align:start position:0% get SL you're going to get slashed just 01:09:06.960 --> 01:09:09.510 align:start position:0% get SL you're going to get slashed just by<01:09:07.120> having<01:09:07.400> the<01:09:07.679> key<01:09:08.120> in<01:09:08.400> two<01:09:08.839> diff<01:09:09.319> two 01:09:09.510 --> 01:09:09.520 align:start position:0% by having the key in two diff two 01:09:09.520 --> 01:09:12.110 align:start position:0% by having the key in two diff two different<01:09:09.880> validat<01:09:10.560> clients<01:09:11.440> active<01:09:11.839> at<01:09:12.000> the 01:09:12.110 --> 01:09:12.120 align:start position:0% different validat clients active at the 01:09:12.120 --> 01:09:14.470 align:start position:0% different validat clients active at the same<01:09:12.400> time<01:09:13.239> otherwise<01:09:13.719> slashing<01:09:14.239> is 01:09:14.470 --> 01:09:14.480 align:start position:0% same time otherwise slashing is 01:09:14.480 --> 01:09:16.950 align:start position:0% same time otherwise slashing is basically<01:09:15.199> it's<01:09:15.359> a<01:09:15.560> really<01:09:15.839> rare<01:09:16.199> event<01:09:16.600> and 01:09:16.950 --> 01:09:16.960 align:start position:0% basically it's a really rare event and 01:09:16.960 --> 01:09:18.829 align:start position:0% basically it's a really rare event and it's<01:09:17.159> actually<01:09:17.560> really<01:09:17.960> hard<01:09:18.319> to<01:09:18.600> like 01:09:18.829 --> 01:09:18.839 align:start position:0% it's actually really hard to like 01:09:18.839 --> 01:09:21.590 align:start position:0% it's actually really hard to like actually<01:09:19.120> run<01:09:19.480> into<01:09:20.159> if<01:09:20.279> you<01:09:20.440> don't<01:09:20.839> try<01:09:21.159> to<01:09:21.480> as 01:09:21.590 --> 01:09:21.600 align:start position:0% actually run into if you don't try to as 01:09:21.600 --> 01:09:24.110 align:start position:0% actually run into if you don't try to as I<01:09:21.759> said<01:09:22.120> be<01:09:22.319> smart<01:09:22.719> about<01:09:22.960> it<01:09:23.359> or<01:09:23.520> try<01:09:23.679> to<01:09:23.920> some 01:09:24.110 --> 01:09:24.120 align:start position:0% I said be smart about it or try to some 01:09:24.120 --> 01:09:26.149 align:start position:0% I said be smart about it or try to some backup<01:09:24.520> setups<01:09:24.920> or<01:09:25.080> something<01:09:25.480> like<01:09:25.679> that<01:09:26.000> if 01:09:26.149 --> 01:09:26.159 align:start position:0% backup setups or something like that if 01:09:26.159 --> 01:09:28.669 align:start position:0% backup setups or something like that if I<01:09:26.359> may<01:09:26.560> make<01:09:26.799> just<01:09:26.960> one<01:09:27.319> one<01:09:27.520> other<01:09:28.040> scenario 01:09:28.669 --> 01:09:28.679 align:start position:0% I may make just one one other scenario 01:09:28.679 --> 01:09:32.070 align:start position:0% I may make just one one other scenario quickly<01:09:29.679> um<01:09:30.000> so<01:09:30.480> in<01:09:31.400> certain<01:09:31.679> parts<01:09:31.880> of<01:09:31.960> the 01:09:32.070 --> 01:09:32.080 align:start position:0% quickly um so in certain parts of the 01:09:32.080 --> 01:09:33.950 align:start position:0% quickly um so in certain parts of the world<01:09:32.319> let's<01:09:32.480> say<01:09:32.719> southeast<01:09:33.199> Asia<01:09:33.719> power 01:09:33.950 --> 01:09:33.960 align:start position:0% world let's say southeast Asia power 01:09:33.960 --> 01:09:36.349 align:start position:0% world let's say southeast Asia power outages<01:09:34.480> are<01:09:34.759> somewhat<01:09:35.199> common<01:09:36.000> you<01:09:36.080> know<01:09:36.239> I'm 01:09:36.349 --> 01:09:36.359 align:start position:0% outages are somewhat common you know I'm 01:09:36.359 --> 01:09:38.749 align:start position:0% outages are somewhat common you know I'm worried<01:09:36.719> about<01:09:36.960> my<01:09:37.080> machine<01:09:37.400> running<01:09:38.120> it<01:09:38.600> uh 01:09:38.749 --> 01:09:38.759 align:start position:0% worried about my machine running it uh 01:09:38.759 --> 01:09:42.590 align:start position:0% worried about my machine running it uh we<01:09:38.880> lose<01:09:39.279> power<01:09:40.000> it<01:09:40.120> doesn't<01:09:40.640> reboot<01:09:41.600> properly 01:09:42.590 --> 01:09:42.600 align:start position:0% we lose power it doesn't reboot properly 01:09:42.600 --> 01:09:44.550 align:start position:0% we lose power it doesn't reboot properly um<01:09:43.000> you<01:09:43.120> know<01:09:43.279> in<01:09:43.440> such<01:09:43.560> a<01:09:43.759> case<01:09:44.000> if<01:09:44.120> you've<01:09:44.319> got 01:09:44.550 --> 01:09:44.560 align:start position:0% um you know in such a case if you've got 01:09:44.560 --> 01:09:46.349 align:start position:0% um you know in such a case if you've got both<01:09:44.799> of<01:09:44.920> your<01:09:45.040> keys<01:09:45.359> on<01:09:45.520> the<01:09:45.600> same<01:09:45.880> validator 01:09:46.349 --> 01:09:46.359 align:start position:0% both of your keys on the same validator 01:09:46.359 --> 01:09:47.910 align:start position:0% both of your keys on the same validator then<01:09:46.560> both<01:09:46.719> would<01:09:46.880> be<01:09:47.000> slashed<01:09:47.480> for<01:09:47.640> being 01:09:47.910 --> 01:09:47.920 align:start position:0% then both would be slashed for being 01:09:47.920 --> 01:09:50.309 align:start position:0% then both would be slashed for being offline<01:09:48.440> is<01:09:48.560> that<01:09:49.080> correct<01:09:49.480> uh<01:09:49.600> slashing<01:09:50.120> is 01:09:50.309 --> 01:09:50.319 align:start position:0% offline is that correct uh slashing is 01:09:50.319 --> 01:09:53.110 align:start position:0% offline is that correct uh slashing is never<01:09:50.560> for<01:09:50.799> offline<01:09:51.359> um<01:09:52.080> slashing<01:09:52.600> is<01:09:52.759> really 01:09:53.110 --> 01:09:53.120 align:start position:0% never for offline um slashing is really 01:09:53.120 --> 01:09:55.830 align:start position:0% never for offline um slashing is really just<01:09:53.600> the<01:09:54.159> uh<01:09:54.279> it's<01:09:54.480> just<01:09:54.640> the<01:09:54.880> penalty<01:09:55.600> you 01:09:55.830 --> 01:09:55.840 align:start position:0% just the uh it's just the penalty you 01:09:55.840 --> 01:09:58.510 align:start position:0% just the uh it's just the penalty you get<01:09:56.040> for<01:09:56.560> um<01:09:56.960> trying<01:09:57.280> to<01:09:57.600> cheat<01:09:57.960> the<01:09:58.120> network 01:09:58.510 --> 01:09:58.520 align:start position:0% get for um trying to cheat the network 01:09:58.520 --> 01:10:01.350 align:start position:0% get for um trying to cheat the network in<01:09:58.679> this<01:09:58.880> case<01:09:59.679> uh<01:09:59.760> if<01:09:59.880> you<01:10:00.120> try<01:10:00.360> to<01:10:01.080> as<01:10:01.159> I 01:10:01.350 --> 01:10:01.360 align:start position:0% in this case uh if you try to as I 01:10:01.360 --> 01:10:03.830 align:start position:0% in this case uh if you try to as I described<01:10:02.239> uh<01:10:02.360> sign<01:10:02.760> with<01:10:02.960> the<01:10:03.159> same<01:10:03.480> key<01:10:03.679> on 01:10:03.830 --> 01:10:03.840 align:start position:0% described uh sign with the same key on 01:10:03.840 --> 01:10:06.630 align:start position:0% described uh sign with the same key on two<01:10:04.040> different<01:10:04.320> valid<01:10:04.640> dat<01:10:04.880> clients<01:10:05.880> uh<01:10:06.520> what 01:10:06.630 --> 01:10:06.640 align:start position:0% two different valid dat clients uh what 01:10:06.640 --> 01:10:09.030 align:start position:0% two different valid dat clients uh what you<01:10:07.000> go<01:10:07.280> what<01:10:07.400> you<01:10:07.520> run<01:10:07.800> into<01:10:08.199> with<01:10:08.600> uh<01:10:08.719> getting 01:10:09.030 --> 01:10:09.040 align:start position:0% you go what you run into with uh getting 01:10:09.040 --> 01:10:11.870 align:start position:0% you go what you run into with uh getting offline<01:10:09.480> is<01:10:09.920> leaking<01:10:10.920> uh<01:10:11.080> which<01:10:11.239> is<01:10:11.719> uh 01:10:11.870 --> 01:10:11.880 align:start position:0% offline is leaking uh which is uh 01:10:11.880 --> 01:10:14.470 align:start position:0% offline is leaking uh which is uh basically<01:10:12.320> your<01:10:13.159> uh<01:10:13.280> note<01:10:13.560> goes<01:10:13.840> offline<01:10:14.199> for 01:10:14.470 --> 01:10:14.480 align:start position:0% basically your uh note goes offline for 01:10:14.480 --> 01:10:16.350 align:start position:0% basically your uh note goes offline for let's<01:10:14.679> say<01:10:14.840> your<01:10:15.000> note<01:10:15.239> goes<01:10:15.440> offline<01:10:15.760> for<01:10:15.920> 24 01:10:16.350 --> 01:10:16.360 align:start position:0% let's say your note goes offline for 24 01:10:16.360 --> 01:10:19.470 align:start position:0% let's say your note goes offline for 24 hours<01:10:16.719> for<01:10:16.920> example<01:10:17.199> or<01:10:17.360> 84<01:10:17.960> 48<01:10:18.520> Hours<01:10:18.840> 72 01:10:19.470 --> 01:10:19.480 align:start position:0% hours for example or 84 48 Hours 72 01:10:19.480 --> 01:10:22.750 align:start position:0% hours for example or 84 48 Hours 72 hours<01:10:20.480> um<01:10:21.159> there<01:10:21.280> is<01:10:21.440> no<01:10:21.640> real<01:10:21.960> risk<01:10:22.440> for<01:10:22.640> you 01:10:22.750 --> 01:10:22.760 align:start position:0% hours um there is no real risk for you 01:10:22.760 --> 01:10:24.990 align:start position:0% hours um there is no real risk for you to<01:10:23.000> just<01:10:23.239> like<01:10:23.440> actually<01:10:23.920> set<01:10:24.199> this<01:10:24.360> up<01:10:24.640> again 01:10:24.990 --> 01:10:25.000 align:start position:0% to just like actually set this up again 01:10:25.000 --> 01:10:26.910 align:start position:0% to just like actually set this up again if<01:10:25.120> you<01:10:25.320> you<01:10:25.440> don't<01:10:25.679> get<01:10:25.880> stressed<01:10:26.400> about<01:10:26.640> it 01:10:26.910 --> 01:10:26.920 align:start position:0% if you you don't get stressed about it 01:10:26.920 --> 01:10:29.669 align:start position:0% if you you don't get stressed about it okay<01:10:27.239> you're<01:10:27.440> going<01:10:27.600> to<01:10:28.320> the<01:10:28.600> the<01:10:28.960> if<01:10:29.199> you<01:10:29.360> lost 01:10:29.669 --> 01:10:29.679 align:start position:0% okay you're going to the the if you lost 01:10:29.679 --> 01:10:33.510 align:start position:0% okay you're going to the the if you lost in<01:10:29.840> the<01:10:30.199> 72<01:10:31.199> hours<01:10:31.880> as<01:10:32.199> penalty<01:10:32.840> you<01:10:32.960> will<01:10:33.159> get 01:10:33.510 --> 01:10:33.520 align:start position:0% in the 72 hours as penalty you will get 01:10:33.520 --> 01:10:36.390 align:start position:0% in the 72 hours as penalty you will get back<01:10:33.760> in<01:10:33.960> 72<01:10:34.560> hours<01:10:35.239> so<01:10:35.719> that<01:10:35.880> there's<01:10:36.120> really 01:10:36.390 --> 01:10:36.400 align:start position:0% back in 72 hours so that there's really 01:10:36.400 --> 01:10:39.270 align:start position:0% back in 72 hours so that there's really no<01:10:36.719> risk<01:10:37.120> as<01:10:37.560> as<01:10:37.679> long<01:10:37.840> as<01:10:37.960> you<01:10:38.080> don't<01:10:38.360> try<01:10:38.600> to 01:10:39.270 --> 01:10:39.280 align:start position:0% no risk as as long as you don't try to 01:10:39.280 --> 01:10:41.950 align:start position:0% no risk as as long as you don't try to uh<01:10:39.800> as<01:10:39.880> I<01:10:40.040> said<01:10:40.480> build<01:10:40.880> backup<01:10:41.400> system<01:10:41.800> there 01:10:41.950 --> 01:10:41.960 align:start position:0% uh as I said build backup system there 01:10:41.960 --> 01:10:43.750 align:start position:0% uh as I said build backup system there are<01:10:42.159> way<01:10:42.320> too<01:10:42.520> over<01:10:42.880> complicated<01:10:43.440> and<01:10:43.600> go 01:10:43.750 --> 01:10:43.760 align:start position:0% are way too over complicated and go 01:10:43.760 --> 01:10:46.510 align:start position:0% are way too over complicated and go online<01:10:44.120> at<01:10:44.239> the<01:10:44.400> same<01:10:44.640> time<01:10:45.199> that<01:10:46.120> you<01:10:46.400> you 01:10:46.510 --> 01:10:46.520 align:start position:0% online at the same time that you you 01:10:46.520 --> 01:10:49.790 align:start position:0% online at the same time that you you will<01:10:46.719> never<01:10:47.000> run<01:10:47.199> into<01:10:47.440> a<01:10:47.880> slashing<01:10:48.880> yeah 01:10:49.790 --> 01:10:49.800 align:start position:0% will never run into a slashing yeah 01:10:49.800 --> 01:10:52.630 align:start position:0% will never run into a slashing yeah you're 01:10:52.630 --> 01:10:52.640 align:start position:0% 01:10:52.640 --> 01:10:57.189 align:start position:0% welcome<01:10:53.640> um 01:10:57.189 --> 01:10:57.199 align:start position:0% 01:10:57.199 --> 01:10:59.350 align:start position:0% oh<01:10:58.199> what<01:10:58.320> do<01:10:58.400> you<01:10:58.520> need<01:10:58.679> when<01:10:58.840> staking<01:10:59.199> with 01:10:59.350 --> 01:10:59.360 align:start position:0% oh what do you need when staking with 01:10:59.360 --> 01:11:01.669 align:start position:0% oh what do you need when staking with ligh<01:10:59.719> CSM<01:11:00.320> yeah<01:11:00.600> uh<01:11:00.719> that's<01:11:00.880> a<01:11:01.040> good<01:11:01.239> question 01:11:01.669 --> 01:11:01.679 align:start position:0% ligh CSM yeah uh that's a good question 01:11:01.679 --> 01:11:04.750 align:start position:0% ligh CSM yeah uh that's a good question actually<01:11:02.640> uh<01:11:02.880> lier<01:11:03.280> CSM<01:11:03.960> you<01:11:04.199> basically<01:11:04.600> go 01:11:04.750 --> 01:11:04.760 align:start position:0% actually uh lier CSM you basically go 01:11:04.760 --> 01:11:06.630 align:start position:0% actually uh lier CSM you basically go through<01:11:05.000> the<01:11:05.120> same<01:11:05.440> process<01:11:06.120> David<01:11:06.400> showed 01:11:06.630 --> 01:11:06.640 align:start position:0% through the same process David showed 01:11:06.640 --> 01:11:08.830 align:start position:0% through the same process David showed you<01:11:07.360> uh<01:11:07.480> the<01:11:07.600> only<01:11:07.880> difference<01:11:08.199> is<01:11:08.400> instead<01:11:08.679> of 01:11:08.830 --> 01:11:08.840 align:start position:0% you uh the only difference is instead of 01:11:08.840 --> 01:11:10.470 align:start position:0% you uh the only difference is instead of the<01:11:09.000> ethereum<01:11:09.440> Launchpad<01:11:10.000> you<01:11:10.120> go<01:11:10.239> to<01:11:10.360> the 01:11:10.470 --> 01:11:10.480 align:start position:0% the ethereum Launchpad you go to the 01:11:10.480 --> 01:11:14.030 align:start position:0% the ethereum Launchpad you go to the lighter<01:11:10.800> CSM<01:11:11.520> Launchpad<01:11:12.520> uh<01:11:12.719> there's<01:11:13.040> like<01:11:13.199> a 01:11:14.030 --> 01:11:14.040 align:start position:0% lighter CSM Launchpad uh there's like a 01:11:14.040 --> 01:11:18.030 align:start position:0% lighter CSM Launchpad uh there's like a test<01:11:14.719> Li<01:11:15.840> CSM<01:11:16.840> I<01:11:16.960> could<01:11:17.239> probably<01:11:17.560> share<01:11:17.880> this 01:11:18.030 --> 01:11:18.040 align:start position:0% test Li CSM I could probably share this 01:11:18.040 --> 01:11:18.750 align:start position:0% test Li CSM I could probably share this with 01:11:18.750 --> 01:11:18.760 align:start position:0% with 01:11:18.760 --> 01:11:22.590 align:start position:0% with all<01:11:20.120> can<01:11:21.120> probably<01:11:21.440> can<01:11:21.560> show<01:11:21.800> this<01:11:22.000> after<01:11:22.440> or 01:11:22.590 --> 01:11:22.600 align:start position:0% all can probably can show this after or 01:11:22.600 --> 01:11:23.990 align:start position:0% all can probably can show this after or like<01:11:22.760> I'm<01:11:22.920> just<01:11:23.040> going<01:11:23.199> to<01:11:23.440> like<01:11:23.560> if<01:11:23.640> someone's 01:11:23.990 --> 01:11:24.000 align:start position:0% like I'm just going to like if someone's 01:11:24.000 --> 01:11:25.910 align:start position:0% like I'm just going to like if someone's interested<01:11:24.520> just<01:11:24.719> come<01:11:24.880> to<01:11:25.040> me<01:11:25.400> I<01:11:25.520> can<01:11:25.600> share 01:11:25.910 --> 01:11:25.920 align:start position:0% interested just come to me I can share 01:11:25.920 --> 01:11:28.590 align:start position:0% interested just come to me I can share the<01:11:26.040> link<01:11:26.320> with<01:11:26.679> you<01:11:27.520> uh<01:11:27.679> you<01:11:27.840> take<01:11:28.040> the<01:11:28.199> empty 01:11:28.590 --> 01:11:28.600 align:start position:0% the link with you uh you take the empty 01:11:28.600 --> 01:11:31.470 align:start position:0% the link with you uh you take the empty key<01:11:29.040> you<01:11:29.199> go<01:11:29.360> to<01:11:29.480> the<01:11:29.600> LI<01:11:29.800> of<01:11:29.960> CSM<01:11:30.440> page<01:11:31.239> uh<01:11:31.320> you 01:11:31.470 --> 01:11:31.480 align:start position:0% key you go to the LI of CSM page uh you 01:11:31.480 --> 01:11:32.990 align:start position:0% key you go to the LI of CSM page uh you upload<01:11:31.800> the<01:11:31.960> key<01:11:32.120> in<01:11:32.280> there<01:11:32.400> you<01:11:32.600> pay<01:11:32.800> your 01:11:32.990 --> 01:11:33.000 align:start position:0% upload the key in there you pay your 01:11:33.000 --> 01:11:34.590 align:start position:0% upload the key in there you pay your bond<01:11:33.520> and<01:11:33.640> that's<01:11:33.840> basically<01:11:34.239> this<01:11:34.400> and<01:11:34.480> then 01:11:34.590 --> 01:11:34.600 align:start position:0% bond and that's basically this and then 01:11:34.600 --> 01:11:37.350 align:start position:0% bond and that's basically this and then you<01:11:34.760> just<01:11:35.000> UT<01:11:35.360> the<01:11:35.480> key<01:11:36.120> it's<01:11:36.320> it's<01:11:36.520> the<01:11:36.679> same 01:11:37.350 --> 01:11:37.360 align:start position:0% you just UT the key it's it's the same 01:11:37.360 --> 01:11:39.750 align:start position:0% you just UT the key it's it's the same process<01:11:38.360> as<01:11:38.440> I<01:11:38.600> said<01:11:38.800> just<01:11:39.000> instead<01:11:39.360> of<01:11:39.600> the 01:11:39.750 --> 01:11:39.760 align:start position:0% process as I said just instead of the 01:11:39.760 --> 01:11:42.990 align:start position:0% process as I said just instead of the Launchpad<01:11:40.280> you<01:11:40.400> go<01:11:40.520> to<01:11:40.639> the<01:11:40.719> LI<01:11:40.920> of<01:11:41.040> CSM<01:11:42.000> stuff 01:11:42.990 --> 01:11:43.000 align:start position:0% Launchpad you go to the LI of CSM stuff 01:11:43.000 --> 01:11:46.510 align:start position:0% Launchpad you go to the LI of CSM stuff uh<01:11:43.360> how<01:11:43.520> many<01:11:43.760> people<01:11:44.040> use<01:11:44.560> theum<01:11:45.560> uh<01:11:45.800> we<01:11:45.960> are 01:11:46.510 --> 01:11:46.520 align:start position:0% uh how many people use theum uh we are 01:11:46.520 --> 01:11:48.110 align:start position:0% uh how many people use theum uh we are it's<01:11:46.719> it's<01:11:46.920> really<01:11:47.159> really<01:11:47.400> hard<01:11:47.560> to<01:11:47.719> say<01:11:48.000> we 01:11:48.110 --> 01:11:48.120 align:start position:0% it's it's really really hard to say we 01:11:48.120 --> 01:11:50.910 align:start position:0% it's it's really really hard to say we don't<01:11:48.400> collect<01:11:48.920> any<01:11:49.800> like<01:11:50.040> user<01:11:50.440> data<01:11:50.760> we<01:11:50.840> are 01:11:50.910 --> 01:11:50.920 align:start position:0% don't collect any like user data we are 01:11:50.920 --> 01:11:52.790 align:start position:0% don't collect any like user data we are not<01:11:51.199> interested<01:11:51.679> in<01:11:51.840> your<01:11:52.000> user<01:11:52.400> data<01:11:52.679> we 01:11:52.790 --> 01:11:52.800 align:start position:0% not interested in your user data we 01:11:52.800 --> 01:11:56.149 align:start position:0% not interested in your user data we don't<01:11:53.080> want<01:11:53.360> that<01:11:54.320> um<01:11:54.679> the<01:11:54.920> best<01:11:55.440> indicator<01:11:56.040> we 01:11:56.149 --> 01:11:56.159 align:start position:0% don't want that um the best indicator we 01:11:56.159 --> 01:11:58.350 align:start position:0% don't want that um the best indicator we would<01:11:56.520> have<01:11:56.920> is<01:11:57.199> actually<01:11:57.760> as<01:11:57.840> I<01:11:58.000> said<01:11:58.199> the 01:11:58.350 --> 01:11:58.360 align:start position:0% would have is actually as I said the 01:11:58.360 --> 01:12:01.390 align:start position:0% would have is actually as I said the blockchain<01:11:58.960> graffiti<01:11:59.920> you<01:12:00.120> only<01:12:00.520> set<01:12:00.960> as<01:12:01.239> you 01:12:01.390 --> 01:12:01.400 align:start position:0% blockchain graffiti you only set as you 01:12:01.400 --> 01:12:04.030 align:start position:0% blockchain graffiti you only set as you only<01:12:01.760> like<01:12:01.960> see<01:12:02.440> when<01:12:02.760> the<01:12:03.040> rid<01:12:03.400> dat<01:12:03.679> key 01:12:04.030 --> 01:12:04.040 align:start position:0% only like see when the rid dat key 01:12:04.040 --> 01:12:06.110 align:start position:0% only like see when the rid dat key actually<01:12:04.360> gets<01:12:04.639> to<01:12:04.840> produce<01:12:05.159> a<01:12:05.320> block<01:12:05.960> which 01:12:06.110 --> 01:12:06.120 align:start position:0% actually gets to produce a block which 01:12:06.120 --> 01:12:09.350 align:start position:0% actually gets to produce a block which is<01:12:06.280> one<01:12:06.600> in<01:12:06.800> 150<01:12:07.639> days<01:12:08.320> you<01:12:08.480> could<01:12:08.719> see<01:12:09.199> we 01:12:09.350 --> 01:12:09.360 align:start position:0% is one in 150 days you could see we 01:12:09.360 --> 01:12:12.229 align:start position:0% is one in 150 days you could see we could<01:12:09.480> you<01:12:09.600> could<01:12:09.960> estimate<01:12:10.639> it<01:12:11.639> um<01:12:11.880> I<01:12:11.960> would 01:12:12.229 --> 01:12:12.239 align:start position:0% could you could estimate it um I would 01:12:12.239 --> 01:12:16.550 align:start position:0% could you could estimate it um I would probably<01:12:12.639> say<01:12:12.960> around<01:12:13.600> uh<01:12:14.159> 1,000<01:12:15.320> 1,500<01:12:16.320> based 01:12:16.550 --> 01:12:16.560 align:start position:0% probably say around uh 1,000 1,500 based 01:12:16.560 --> 01:12:18.709 align:start position:0% probably say around uh 1,000 1,500 based on<01:12:16.679> the<01:12:16.840> download<01:12:17.239> numbers<01:12:18.000> but<01:12:18.159> I<01:12:18.280> also<01:12:18.520> have 01:12:18.709 --> 01:12:18.719 align:start position:0% on the download numbers but I also have 01:12:18.719 --> 01:12:21.310 align:start position:0% on the download numbers but I also have say<01:12:19.239> have<01:12:19.360> to<01:12:19.480> say<01:12:19.639> we<01:12:19.760> have<01:12:19.880> a<01:12:20.000> lot<01:12:20.159> of<01:12:20.800> uh 01:12:21.310 --> 01:12:21.320 align:start position:0% say have to say we have a lot of uh 01:12:21.320 --> 01:12:23.270 align:start position:0% say have to say we have a lot of uh because<01:12:21.600> the<01:12:21.800> tool<01:12:22.159> makes<01:12:22.360> it<01:12:22.520> a<01:12:22.679> little<01:12:22.920> bit 01:12:23.270 --> 01:12:23.280 align:start position:0% because the tool makes it a little bit 01:12:23.280 --> 01:12:25.709 align:start position:0% because the tool makes it a little bit maybe<01:12:23.679> maybe<01:12:23.880> even<01:12:24.040> too<01:12:24.320> easy<01:12:25.280> we<01:12:25.400> have<01:12:25.480> a<01:12:25.600> lot 01:12:25.709 --> 01:12:25.719 align:start position:0% maybe maybe even too easy we have a lot 01:12:25.719 --> 01:12:28.870 align:start position:0% maybe maybe even too easy we have a lot of<01:12:25.880> lazy<01:12:26.360> users<01:12:26.800> who<01:12:27.080> don't<01:12:27.880> uh<01:12:28.080> do<01:12:28.320> the 01:12:28.870 --> 01:12:28.880 align:start position:0% of lazy users who don't uh do the 01:12:28.880 --> 01:12:30.830 align:start position:0% of lazy users who don't uh do the updates<01:12:29.320> all<01:12:29.480> the<01:12:29.679> time<01:12:29.960> they<01:12:30.159> just<01:12:30.400> like<01:12:30.560> as<01:12:30.679> I 01:12:30.830 --> 01:12:30.840 align:start position:0% updates all the time they just like as I 01:12:30.840 --> 01:12:33.270 align:start position:0% updates all the time they just like as I said<01:12:31.280> put<01:12:31.480> the<01:12:31.600> auto<01:12:31.960> update<01:12:32.280> on<01:12:32.920> it's<01:12:33.159> going 01:12:33.270 --> 01:12:33.280 align:start position:0% said put the auto update on it's going 01:12:33.280 --> 01:12:36.390 align:start position:0% said put the auto update on it's going to<01:12:33.520> like<01:12:33.679> get<01:12:33.840> the<01:12:34.040> client<01:12:35.000> uh<01:12:35.280> client<01:12:35.760> down<01:12:36.199> uh 01:12:36.390 --> 01:12:36.400 align:start position:0% to like get the client uh client down uh 01:12:36.400 --> 01:12:38.350 align:start position:0% to like get the client uh client down uh updates<01:12:37.120> automatically<01:12:37.719> it's<01:12:37.840> going<01:12:37.920> to<01:12:38.159> take 01:12:38.350 --> 01:12:38.360 align:start position:0% updates automatically it's going to take 01:12:38.360 --> 01:12:41.270 align:start position:0% updates automatically it's going to take the<01:12:38.520> Note<01:12:38.840> updates<01:12:39.480> automatically<01:12:40.480> so<01:12:40.960> uh 01:12:41.270 --> 01:12:41.280 align:start position:0% the Note updates automatically so uh 01:12:41.280 --> 01:12:43.110 align:start position:0% the Note updates automatically so uh they<01:12:41.440> never<01:12:41.840> showing<01:12:42.239> our<01:12:42.600> like<01:12:42.800> actual 01:12:43.110 --> 01:12:43.120 align:start position:0% they never showing our like actual 01:12:43.120 --> 01:12:45.350 align:start position:0% they never showing our like actual download<01:12:43.560> numbers<01:12:43.920> from<01:12:44.159> GitHub<01:12:44.719> and<01:12:44.880> this<01:12:45.000> is 01:12:45.350 --> 01:12:45.360 align:start position:0% download numbers from GitHub and this is 01:12:45.360 --> 01:12:47.470 align:start position:0% download numbers from GitHub and this is really<01:12:45.600> the<01:12:45.760> only<01:12:46.080> thing<01:12:46.520> the<01:12:46.719> GitHub<01:12:47.120> numbers 01:12:47.470 --> 01:12:47.480 align:start position:0% really the only thing the GitHub numbers 01:12:47.480 --> 01:12:49.350 align:start position:0% really the only thing the GitHub numbers and<01:12:47.600> the<01:12:47.719> blockchain<01:12:48.120> graffi<01:12:48.600> we<01:12:48.719> can<01:12:48.880> use<01:12:49.159> to 01:12:49.350 --> 01:12:49.360 align:start position:0% and the blockchain graffi we can use to 01:12:49.360 --> 01:12:51.189 align:start position:0% and the blockchain graffi we can use to estimate 01:12:51.189 --> 01:12:51.199 align:start position:0% estimate 01:12:51.199 --> 01:12:53.629 align:start position:0% estimate that<01:12:52.199> are<01:12:52.440> there<01:12:52.600> guides<01:12:52.800> or<01:12:53.000> tutorials<01:12:53.480> for 01:12:53.629 --> 01:12:53.639 align:start position:0% that are there guides or tutorials for 01:12:53.639 --> 01:12:56.229 align:start position:0% that are there guides or tutorials for steum<01:12:54.320> yes<01:12:54.600> we<01:12:54.719> have<01:12:54.960> like<01:12:55.520> documentation 01:12:56.229 --> 01:12:56.239 align:start position:0% steum yes we have like documentation 01:12:56.239 --> 01:12:59.470 align:start position:0% steum yes we have like documentation page<01:12:56.600> with<01:12:56.800> like<01:12:57.120> a<01:12:57.800> uh<01:12:58.080> guides<01:12:58.920> uh<01:12:59.080> we<01:12:59.199> also 01:12:59.470 --> 01:12:59.480 align:start position:0% page with like a uh guides uh we also 01:12:59.480 --> 01:13:02.070 align:start position:0% page with like a uh guides uh we also have<01:12:59.760> like<01:13:00.080> uh<01:13:00.480> a<01:13:00.600> little<01:13:00.840> bit<01:13:01.080> old<01:13:01.440> tutorial 01:13:02.070 --> 01:13:02.080 align:start position:0% have like uh a little bit old tutorial 01:13:02.080 --> 01:13:04.149 align:start position:0% have like uh a little bit old tutorial videos<01:13:02.639> but<01:13:02.760> they<01:13:02.960> basically<01:13:03.440> still<01:13:03.679> work<01:13:04.000> the 01:13:04.149 --> 01:13:04.159 align:start position:0% videos but they basically still work the 01:13:04.159 --> 01:13:06.310 align:start position:0% videos but they basically still work the same<01:13:04.880> uh<01:13:05.000> the<01:13:05.120> UI<01:13:05.440> changed<01:13:05.760> a<01:13:05.880> little<01:13:06.120> bit 01:13:06.310 --> 01:13:06.320 align:start position:0% same uh the UI changed a little bit 01:13:06.320 --> 01:13:08.189 align:start position:0% same uh the UI changed a little bit between<01:13:06.679> this<01:13:06.920> maybe<01:13:07.280> interesting<01:13:07.800> to<01:13:07.920> see 01:13:08.189 --> 01:13:08.199 align:start position:0% between this maybe interesting to see 01:13:08.199 --> 01:13:11.229 align:start position:0% between this maybe interesting to see what<01:13:08.320> we<01:13:08.480> did<01:13:08.639> in<01:13:08.800> the<01:13:09.600> like<01:13:09.960> uh<01:13:10.080> years<01:13:10.520> we<01:13:11.080> uh 01:13:11.229 --> 01:13:11.239 align:start position:0% what we did in the like uh years we uh 01:13:11.239 --> 01:13:15.310 align:start position:0% what we did in the like uh years we uh working<01:13:11.560> on<01:13:12.040> this<01:13:13.040> uh<01:13:13.480> so<01:13:14.280> uh<01:13:14.440> you<01:13:14.639> also<01:13:15.000> can 01:13:15.310 --> 01:13:15.320 align:start position:0% working on this uh so uh you also can 01:13:15.320 --> 01:13:17.830 align:start position:0% working on this uh so uh you also can always<01:13:15.679> come<01:13:16.000> if<01:13:16.120> you<01:13:16.239> run<01:13:16.480> into<01:13:16.840> any<01:13:17.320> problems 01:13:17.830 --> 01:13:17.840 align:start position:0% always come if you run into any problems 01:13:17.840 --> 01:13:20.030 align:start position:0% always come if you run into any problems whatsoever<01:13:18.679> we<01:13:18.800> have<01:13:18.920> a<01:13:19.080> Discord<01:13:19.480> server<01:13:19.920> we 01:13:20.030 --> 01:13:20.040 align:start position:0% whatsoever we have a Discord server we 01:13:20.040 --> 01:13:24.910 align:start position:0% whatsoever we have a Discord server we are<01:13:20.440> 24/7<01:13:21.520> there<01:13:22.520> uh<01:13:23.480> basically<01:13:24.480> with<01:13:24.600> the<01:13:24.719> do 01:13:24.910 --> 01:13:24.920 align:start position:0% are 24/7 there uh basically with the do 01:13:24.920 --> 01:13:27.390 align:start position:0% are 24/7 there uh basically with the do s<01:13:25.320> most<01:13:25.480> of<01:13:25.600> us<01:13:25.719> are<01:13:25.920> Europe<01:13:26.280> based<01:13:27.000> so<01:13:27.159> if<01:13:27.280> you 01:13:27.390 --> 01:13:27.400 align:start position:0% s most of us are Europe based so if you 01:13:27.400 --> 01:13:29.430 align:start position:0% s most of us are Europe based so if you write<01:13:27.639> to<01:13:27.760> us<01:13:27.920> at<01:13:28.080> like<01:13:28.199> 3:00<01:13:28.440> a.m.<01:13:28.800> in<01:13:29.080> Europe 01:13:29.430 --> 01:13:29.440 align:start position:0% write to us at like 3:00 a.m. in Europe 01:13:29.440 --> 01:13:31.790 align:start position:0% write to us at like 3:00 a.m. in Europe time<01:13:29.679> we<01:13:29.800> might<01:13:30.040> not<01:13:30.320> like<01:13:30.520> answer<01:13:31.360> directly 01:13:31.790 --> 01:13:31.800 align:start position:0% time we might not like answer directly 01:13:31.800 --> 01:13:33.350 align:start position:0% time we might not like answer directly but<01:13:31.960> as<01:13:32.080> soon<01:13:32.239> as<01:13:32.400> we<01:13:32.560> wake<01:13:32.760> up<01:13:33.000> we're<01:13:33.159> going<01:13:33.239> to 01:13:33.350 --> 01:13:33.360 align:start position:0% but as soon as we wake up we're going to 01:13:33.360 --> 01:13:35.709 align:start position:0% but as soon as we wake up we're going to see<01:13:33.520> your<01:13:33.719> message<01:13:34.000> in<01:13:34.159> our<01:13:34.440> Discord<01:13:35.320> and<01:13:35.480> to 01:13:35.709 --> 01:13:35.719 align:start position:0% see your message in our Discord and to 01:13:35.719 --> 01:13:38.110 align:start position:0% see your message in our Discord and to just<01:13:36.159> come<01:13:36.440> and<01:13:36.679> actually<01:13:36.960> try<01:13:37.199> to<01:13:37.360> help<01:13:37.600> you 01:13:38.110 --> 01:13:38.120 align:start position:0% just come and actually try to help you 01:13:38.120 --> 01:13:40.110 align:start position:0% just come and actually try to help you there<01:13:38.280> was<01:13:38.520> never<01:13:39.080> a<01:13:39.280> problem<01:13:39.600> we<01:13:39.760> couldn't 01:13:40.110 --> 01:13:40.120 align:start position:0% there was never a problem we couldn't 01:13:40.120 --> 01:13:43.550 align:start position:0% there was never a problem we couldn't fix<01:13:40.719> really<01:13:41.719> uh<01:13:42.320> as<01:13:42.679> as<01:13:42.800> long<01:13:43.000> as<01:13:43.120> you<01:13:43.320> like 01:13:43.550 --> 01:13:43.560 align:start position:0% fix really uh as as long as you like 01:13:43.560 --> 01:13:45.510 align:start position:0% fix really uh as as long as you like actually<01:13:44.239> give<01:13:44.440> us<01:13:44.600> all<01:13:44.719> the<01:13:44.880> information<01:13:45.360> we 01:13:45.510 --> 01:13:45.520 align:start position:0% actually give us all the information we 01:13:45.520 --> 01:13:47.830 align:start position:0% actually give us all the information we ask<01:13:45.760> for<01:13:46.199> and<01:13:46.320> you<01:13:46.600> just<01:13:47.120> communicate<01:13:47.679> with 01:13:47.830 --> 01:13:47.840 align:start position:0% ask for and you just communicate with 01:13:47.840 --> 01:13:49.950 align:start position:0% ask for and you just communicate with each<01:13:48.000> other<01:13:48.520> it's<01:13:48.679> really<01:13:48.920> really<01:13:49.239> easy<01:13:49.520> to<01:13:49.760> go 01:13:49.950 --> 01:13:49.960 align:start position:0% each other it's really really easy to go 01:13:49.960 --> 01:13:54.030 align:start position:0% each other it's really really easy to go through<01:13:50.280> most<01:13:51.120> problems<01:13:52.120> and<01:13:52.400> yeah 01:13:54.030 --> 01:13:54.040 align:start position:0% through most problems and yeah 01:13:54.040 --> 01:13:57.270 align:start position:0% through most problems and yeah um<01:13:55.080> if<01:13:55.199> there's<01:13:55.639> uh<01:13:56.120> no<01:13:56.440> no<01:13:56.600> other<01:13:56.880> question<01:13:57.199> I 01:13:57.270 --> 01:13:57.280 align:start position:0% um if there's uh no no other question I 01:13:57.280 --> 01:13:58.910 align:start position:0% um if there's uh no no other question I would<01:13:57.440> like<01:13:57.639> end<01:13:57.840> it<01:13:57.960> a<01:13:58.080> little<01:13:58.280> bit<01:13:58.440> early<01:13:58.760> if 01:13:58.910 --> 01:13:58.920 align:start position:0% would like end it a little bit early if 01:13:58.920 --> 01:14:01.870 align:start position:0% would like end it a little bit early if that's<01:13:59.120> fine<01:13:59.280> for<01:13:59.440> you<01:13:59.639> guys<01:14:00.480> uh<01:14:00.679> so<01:14:01.480> anyone 01:14:01.870 --> 01:14:01.880 align:start position:0% that's fine for you guys uh so anyone 01:14:01.880 --> 01:14:04.950 align:start position:0% that's fine for you guys uh so anyone else 01:14:04.950 --> 01:14:04.960 align:start position:0% 01:14:04.960 --> 01:14:07.550 align:start position:0% anything<01:14:05.960> okay<01:14:06.280> perfectly<01:14:07.120> I<01:14:07.280> don't<01:14:07.400> know 01:14:07.550 --> 01:14:07.560 align:start position:0% anything okay perfectly I don't know 01:14:07.560 --> 01:14:09.790 align:start position:0% anything okay perfectly I don't know thank<01:14:07.719> you<01:14:07.880> everyone<01:14:08.600> for<01:14:08.800> listening<01:14:09.639> um 01:14:09.790 --> 01:14:09.800 align:start position:0% thank you everyone for listening um 01:14:09.800 --> 01:14:11.510 align:start position:0% thank you everyone for listening um thank<01:14:09.960> you<01:14:10.080> for<01:14:10.239> your<01:14:10.400> attention<01:14:11.159> if<01:14:11.239> you<01:14:11.360> have 01:14:11.510 --> 01:14:11.520 align:start position:0% thank you for your attention if you have 01:14:11.520 --> 01:14:13.350 align:start position:0% thank you for your attention if you have other<01:14:11.840> questions<01:14:12.360> like<01:14:12.600> personal<01:14:13.040> question 01:14:13.350 --> 01:14:13.360 align:start position:0% other questions like personal question 01:14:13.360 --> 01:14:16.189 align:start position:0% other questions like personal question or<01:14:13.560> like<01:14:14.280> specific<01:14:14.719> question<01:14:15.080> to<01:14:15.400> like<01:14:15.560> setup 01:14:16.189 --> 01:14:16.199 align:start position:0% or like specific question to like setup 01:14:16.199 --> 01:14:18.629 align:start position:0% or like specific question to like setup you<01:14:16.679> can<01:14:16.880> just<01:14:17.080> find<01:14:17.360> us<01:14:18.040> uh<01:14:18.159> we<01:14:18.280> also<01:14:18.480> have 01:14:18.629 --> 01:14:18.639 align:start position:0% you can just find us uh we also have 01:14:18.639 --> 01:14:22.030 align:start position:0% you can just find us uh we also have like<01:14:18.760> a<01:14:18.880> boo<01:14:19.360> on<01:14:19.840> uh<01:14:20.159> thur<01:14:20.520> day<01:14:20.679> and<01:14:20.960> Friday<01:14:21.960> uh 01:14:22.030 --> 01:14:22.040 align:start position:0% like a boo on uh thur day and Friday uh 01:14:22.040 --> 01:14:23.750 align:start position:0% like a boo on uh thur day and Friday uh you<01:14:22.120> can<01:14:22.320> try<01:14:22.480> it<01:14:22.600> out<01:14:22.960> yourself<01:14:23.400> if<01:14:23.480> you<01:14:23.600> want 01:14:23.750 --> 01:14:23.760 align:start position:0% you can try it out yourself if you want 01:14:23.760 --> 01:14:25.390 align:start position:0% you can try it out yourself if you want to<01:14:24.000> we<01:14:24.080> have<01:14:24.239> like<01:14:24.360> machines<01:14:24.719> here<01:14:25.159> actually 01:14:25.390 --> 01:14:25.400 align:start position:0% to we have like machines here actually 01:14:25.400 --> 01:14:28.030 align:start position:0% to we have like machines here actually try<01:14:25.639> it<01:14:25.760> out<01:14:26.320> also<01:14:26.480> have<01:14:26.600> some<01:14:26.800> nice<01:14:27.480> like 01:14:28.030 --> 01:14:28.040 align:start position:0% try it out also have some nice like 01:14:28.040 --> 01:14:31.189 align:start position:0% try it out also have some nice like merch<01:14:28.400> if<01:14:28.480> you<01:14:28.600> want<01:14:28.760> to<01:14:29.280> come<01:14:29.600> here<01:14:30.600> um<01:14:30.960> and 01:14:31.189 --> 01:14:31.199 align:start position:0% merch if you want to come here um and 01:14:31.199 --> 01:14:33.590 align:start position:0% merch if you want to come here um and yeah<01:14:31.480> thank<01:14:31.639> you<01:14:31.840> very<01:14:32.080> much<01:14:32.679> and<01:14:33.199> I<01:14:33.320> hope<01:14:33.480> you 01:14:33.590 --> 01:14:33.600 align:start position:0% yeah thank you very much and I hope you 01:14:33.600 --> 01:14:37.920 align:start position:0% yeah thank you very much and I hope you all<01:14:33.920> guys<01:14:34.199> all<01:14:34.400> have<01:14:34.560> a<01:14:34.679> nice<01:14:34.920> day