WEBVTT Kind: captions Language: en 00:00:00.570 --> 00:00:22.230 align:start position:0% [Music] 00:00:22.230 --> 00:00:22.240 align:start position:0% 00:00:22.240 --> 00:00:25.070 align:start position:0% hello<00:00:23.240> hello<00:00:23.519> everyone<00:00:24.519> uh<00:00:24.640> my<00:00:24.760> name<00:00:24.920> is 00:00:25.070 --> 00:00:25.080 align:start position:0% hello hello everyone uh my name is 00:00:25.080 --> 00:00:27.790 align:start position:0% hello hello everyone uh my name is Fernando<00:00:25.680> he's<00:00:26.000> my<00:00:26.359> colleague<00:00:26.720> Diego<00:00:27.560> uh<00:00:27.679> we 00:00:27.790 --> 00:00:27.800 align:start position:0% Fernando he's my colleague Diego uh we 00:00:27.800 --> 00:00:31.109 align:start position:0% Fernando he's my colleague Diego uh we are<00:00:27.880> from<00:00:28.560> arm<00:00:29.160> U<00:00:29.359> we<00:00:29.439> are<00:00:29.640> trying<00:00:30.080> to<00:00:30.359> show 00:00:31.109 --> 00:00:31.119 align:start position:0% are from arm U we are trying to show 00:00:31.119 --> 00:00:34.830 align:start position:0% are from arm U we are trying to show today<00:00:31.880> how<00:00:32.079> to<00:00:32.880> uh<00:00:33.160> build<00:00:34.120> I<00:00:34.239> think<00:00:34.480> that<00:00:34.680> we 00:00:34.830 --> 00:00:34.840 align:start position:0% today how to uh build I think that we 00:00:34.840 --> 00:00:38.430 align:start position:0% today how to uh build I think that we call<00:00:35.360> Super<00:00:35.960> node<00:00:36.960> uh<00:00:37.160> in<00:00:37.280> a<00:00:37.440> very<00:00:37.640> easy<00:00:37.879> way<00:00:38.200> in 00:00:38.430 --> 00:00:38.440 align:start position:0% call Super node uh in a very easy way in 00:00:38.440 --> 00:00:41.750 align:start position:0% call Super node uh in a very easy way in a<00:00:38.680> low<00:00:39.040> power<00:00:39.360> device<00:00:39.840> Hardware<00:00:40.480> this<00:00:40.600> is<00:00:40.760> a 00:00:41.750 --> 00:00:41.760 align:start position:0% a low power device Hardware this is a 00:00:41.760 --> 00:00:43.709 align:start position:0% a low power device Hardware this is a hardware<00:00:42.120> demonstration<00:00:42.800> and<00:00:43.079> I<00:00:43.280> encourage 00:00:43.709 --> 00:00:43.719 align:start position:0% hardware demonstration and I encourage 00:00:43.719 --> 00:00:46.150 align:start position:0% hardware demonstration and I encourage you<00:00:43.840> to<00:00:44.280> come<00:00:44.480> closer<00:00:45.280> if<00:00:45.399> you<00:00:45.520> want<00:00:45.680> to<00:00:45.800> see 00:00:46.150 --> 00:00:46.160 align:start position:0% you to come closer if you want to see 00:00:46.160 --> 00:00:48.029 align:start position:0% you to come closer if you want to see how<00:00:46.360> we<00:00:46.520> are<00:00:46.760> going<00:00:46.960> to<00:00:47.199> build<00:00:47.640> the<00:00:47.879> the 00:00:48.029 --> 00:00:48.039 align:start position:0% how we are going to build the the 00:00:48.039 --> 00:00:51.150 align:start position:0% how we are going to build the the machine<00:00:48.480> and<00:00:49.000> we<00:00:49.120> are<00:00:49.280> going<00:00:49.680> to<00:00:50.680> uh<00:00:50.800> do 00:00:51.150 --> 00:00:51.160 align:start position:0% machine and we are going to uh do 00:00:51.160 --> 00:00:53.950 align:start position:0% machine and we are going to uh do everything<00:00:51.559> in<00:00:51.719> life<00:00:52.120> here<00:00:52.800> we<00:00:52.960> hope<00:00:53.280> this<00:00:53.680> is 00:00:53.950 --> 00:00:53.960 align:start position:0% everything in life here we hope this is 00:00:53.960 --> 00:00:56.869 align:start position:0% everything in life here we hope this is going<00:00:54.120> to<00:00:54.320> work<00:00:54.800> because<00:00:55.800> it's<00:00:56.280> a<00:00:56.399> live<00:00:56.600> demo 00:00:56.869 --> 00:00:56.879 align:start position:0% going to work because it's a live demo 00:00:56.879 --> 00:01:00.349 align:start position:0% going to work because it's a live demo and<00:00:57.160> always<00:00:57.559> is<00:00:57.800> is<00:00:58.000> hard<00:00:58.199> to<00:00:58.559> to<00:00:58.840> to<00:00:59.039> tell<00:00:59.719> but 00:01:00.349 --> 00:01:00.359 align:start position:0% and always is is hard to to to tell but 00:01:00.359 --> 00:01:02.389 align:start position:0% and always is is hard to to to tell but if<00:01:00.440> you<00:01:00.559> want<00:01:00.719> to<00:01:00.879> see<00:01:01.359> the<00:01:01.800> the<00:01:02.000> the<00:01:02.120> ARM 00:01:02.389 --> 00:01:02.399 align:start position:0% if you want to see the the the ARM 00:01:02.399 --> 00:01:04.390 align:start position:0% if you want to see the the the ARM device<00:01:02.920> and<00:01:03.239> all<00:01:03.600> the<00:01:03.719> things<00:01:03.920> that<00:01:04.040> you<00:01:04.199> need 00:01:04.390 --> 00:01:04.400 align:start position:0% device and all the things that you need 00:01:04.400 --> 00:01:07.390 align:start position:0% device and all the things that you need to<00:01:04.600> create<00:01:04.879> your<00:01:05.040> own<00:01:05.239> no<00:01:05.519> at<00:01:05.760> home<00:01:06.760> uh<00:01:07.240> I 00:01:07.390 --> 00:01:07.400 align:start position:0% to create your own no at home uh I 00:01:07.400 --> 00:01:09.469 align:start position:0% to create your own no at home uh I encourage<00:01:07.759> you<00:01:07.840> to<00:01:08.000> go<00:01:08.200> closer<00:01:08.600> in<00:01:08.840> order<00:01:09.159> to 00:01:09.469 --> 00:01:09.479 align:start position:0% encourage you to go closer in order to 00:01:09.479 --> 00:01:11.030 align:start position:0% encourage you to go closer in order to to<00:01:09.640> see<00:01:09.920> all<00:01:10.159> the<00:01:10.360> the<00:01:10.479> things<00:01:10.640> that<00:01:10.799> we<00:01:10.920> are 00:01:11.030 --> 00:01:11.040 align:start position:0% to see all the the things that we are 00:01:11.040 --> 00:01:13.749 align:start position:0% to see all the the things that we are going<00:01:11.200> to<00:01:11.360> do<00:01:12.000> outside<00:01:12.520> the<00:01:12.799> the<00:01:12.920> camera<00:01:13.479> here 00:01:13.749 --> 00:01:13.759 align:start position:0% going to do outside the the camera here 00:01:13.759 --> 00:01:16.109 align:start position:0% going to do outside the the camera here in<00:01:14.040> in<00:01:14.159> our<00:01:14.759> this<00:01:15.040> small 00:01:16.109 --> 00:01:16.119 align:start position:0% in in our this small 00:01:16.119 --> 00:01:26.749 align:start position:0% in in our this small lab 00:01:26.749 --> 00:01:26.759 align:start position:0% 00:01:26.759 --> 00:01:42.350 align:start position:0% uh<00:01:27.799> uh<00:01:28.799> where<00:01:29.119> the 00:01:42.350 --> 00:01:42.360 align:start position:0% 00:01:42.360 --> 00:01:54.469 align:start position:0% help<00:01:43.360> uh<00:01:43.600> here<00:01:44.000> it's<00:01:44.280> here<00:01:44.680> H 00:01:54.469 --> 00:01:54.479 align:start position:0% 00:01:54.479 --> 00:01:58.310 align:start position:0% yeah<00:01:55.479> so<00:01:55.840> this<00:01:56.000> is<00:01:56.439> this<00:01:56.719> are<00:01:56.920> not<00:01:57.200> the<00:01:57.520> best<00:01:57.960> uh 00:01:58.310 --> 00:01:58.320 align:start position:0% yeah so this is this are not the best uh 00:01:58.320 --> 00:02:00.709 align:start position:0% yeah so this is this are not the best uh conditions<00:01:59.119> uh<00:01:59.280> especially<00:02:00.039> work<00:02:00.320> conditions 00:02:00.709 --> 00:02:00.719 align:start position:0% conditions uh especially work conditions 00:02:00.719 --> 00:02:03.870 align:start position:0% conditions uh especially work conditions because<00:02:01.439> well<00:02:01.640> we<00:02:01.719> are<00:02:01.880> in<00:02:02.439> a<00:02:03.439> close 00:02:03.870 --> 00:02:03.880 align:start position:0% because well we are in a close 00:02:03.880 --> 00:02:08.070 align:start position:0% because well we are in a close environment<00:02:04.880> so<00:02:06.000> um<00:02:07.000> what<00:02:07.200> we're<00:02:07.439> going<00:02:07.600> to<00:02:07.719> do 00:02:08.070 --> 00:02:08.080 align:start position:0% environment so um what we're going to do 00:02:08.080 --> 00:02:11.790 align:start position:0% environment so um what we're going to do is<00:02:08.479> uh<00:02:08.640> to<00:02:08.800> launch<00:02:09.200> a<00:02:09.399> script<00:02:10.360> that<00:02:10.920> uh<00:02:11.400> is<00:02:11.599> the 00:02:11.790 --> 00:02:11.800 align:start position:0% is uh to launch a script that uh is the 00:02:11.800 --> 00:02:14.350 align:start position:0% is uh to launch a script that uh is the script<00:02:12.200> that<00:02:12.520> installs<00:02:13.280> everything<00:02:14.000> from 00:02:14.350 --> 00:02:14.360 align:start position:0% script that installs everything from 00:02:14.360 --> 00:02:18.350 align:start position:0% script that installs everything from from<00:02:14.519> the<00:02:14.879> beginning<00:02:15.920> so<00:02:16.920> you<00:02:17.120> can<00:02:17.400> see<00:02:18.200> what 00:02:18.350 --> 00:02:18.360 align:start position:0% from the beginning so you can see what 00:02:18.360 --> 00:02:20.550 align:start position:0% from the beginning so you can see what is<00:02:18.519> going<00:02:18.760> on<00:02:18.920> in<00:02:19.040> the<00:02:19.200> background<00:02:19.720> this<00:02:19.840> is 00:02:20.550 --> 00:02:20.560 align:start position:0% is going on in the background this is 00:02:20.560 --> 00:02:23.229 align:start position:0% is going on in the background this is this<00:02:21.319> uh<00:02:21.640> when<00:02:21.760> you<00:02:21.920> install<00:02:22.319> our<00:02:22.519> our<00:02:22.800> image 00:02:23.229 --> 00:02:23.239 align:start position:0% this uh when you install our our image 00:02:23.239 --> 00:02:25.790 align:start position:0% this uh when you install our our image this<00:02:23.360> is<00:02:23.480> not<00:02:23.680> something<00:02:24.040> that<00:02:24.200> you<00:02:24.440> see<00:02:25.440> uh 00:02:25.790 --> 00:02:25.800 align:start position:0% this is not something that you see uh 00:02:25.800 --> 00:02:30.670 align:start position:0% this is not something that you see uh but<00:02:26.319> uh<00:02:26.599> we<00:02:26.720> want<00:02:26.920> to<00:02:27.519> we<00:02:27.640> want<00:02:27.840> you<00:02:27.959> to<00:02:28.120> see<00:02:29.080> um 00:02:30.670 --> 00:02:30.680 align:start position:0% but uh we want to we want you to see um 00:02:30.680 --> 00:02:34.990 align:start position:0% but uh we want to we want you to see um this<00:02:31.239> uh<00:02:31.560> tasks<00:02:32.440> that<00:02:33.080> uh<00:02:33.760> installs<00:02:34.760> pretty 00:02:34.990 --> 00:02:35.000 align:start position:0% this uh tasks that uh installs pretty 00:02:35.000 --> 00:02:39.270 align:start position:0% this uh tasks that uh installs pretty much<00:02:35.239> everything<00:02:36.360> from<00:02:37.480> uh<00:02:38.480> partitioning<00:02:39.040> the 00:02:39.270 --> 00:02:39.280 align:start position:0% much everything from uh partitioning the 00:02:39.280 --> 00:02:43.430 align:start position:0% much everything from uh partitioning the disk<00:02:39.800> and<00:02:40.560> user<00:02:41.000> creation<00:02:42.000> and<00:02:42.560> uh<00:02:42.720> software 00:02:43.430 --> 00:02:43.440 align:start position:0% disk and user creation and uh software 00:02:43.440 --> 00:02:48.390 align:start position:0% disk and user creation and uh software install<00:02:44.440> uh<00:02:44.640> so<00:02:44.879> you<00:02:45.080> can<00:02:46.120> uh<00:02:47.120> make<00:02:47.360> an<00:02:47.599> idea<00:02:48.040> of 00:02:48.390 --> 00:02:48.400 align:start position:0% install uh so you can uh make an idea of 00:02:48.400 --> 00:03:01.509 align:start position:0% install uh so you can uh make an idea of what's<00:02:48.640> going<00:02:48.840> on<00:02:49.120> there 00:03:01.509 --> 00:03:01.519 align:start position:0% 00:03:01.519 --> 00:03:04.470 align:start position:0% it's 00:03:04.470 --> 00:03:04.480 align:start position:0% 00:03:04.480 --> 00:03:19.149 align:start position:0% cool 00:03:19.149 --> 00:03:19.159 align:start position:0% 00:03:19.159 --> 00:03:23.229 align:start position:0% okay<00:03:20.159> someone<00:03:20.680> here<00:03:20.840> is<00:03:20.959> running 00:03:23.229 --> 00:03:23.239 align:start position:0% okay someone here is running 00:03:23.239 --> 00:03:27.710 align:start position:0% okay someone here is running notes<00:03:24.239> yeah<00:03:25.080> with<00:03:25.519> these<00:03:25.840> devices<00:03:26.400> or<00:03:26.879> or<00:03:27.280> more 00:03:27.710 --> 00:03:27.720 align:start position:0% notes yeah with these devices or or more 00:03:27.720 --> 00:03:52.270 align:start position:0% notes yeah with these devices or or more uh<00:03:28.720> yeah 00:03:52.270 --> 00:03:52.280 align:start position:0% 00:03:52.280 --> 00:04:12.069 align:start position:0% now<00:03:53.280> it's<00:03:53.560> okay 00:04:12.069 --> 00:04:12.079 align:start position:0% 00:04:12.079 --> 00:04:17.030 align:start position:0% yeah<00:04:13.079> so<00:04:14.079> uh<00:04:14.879> this<00:04:15.000> is<00:04:15.760> really<00:04:16.120> what<00:04:16.759> what<00:04:16.880> we 00:04:17.030 --> 00:04:17.040 align:start position:0% yeah so uh this is really what what we 00:04:17.040 --> 00:04:19.909 align:start position:0% yeah so uh this is really what what we do<00:04:17.400> we<00:04:17.600> help<00:04:17.919> users<00:04:18.320> to<00:04:18.519> run<00:04:19.000> etherum<00:04:19.440> nodes<00:04:19.720> in 00:04:19.909 --> 00:04:19.919 align:start position:0% do we help users to run etherum nodes in 00:04:19.919 --> 00:04:24.189 align:start position:0% do we help users to run etherum nodes in low<00:04:20.280> power<00:04:21.040> devices<00:04:22.040> uh<00:04:22.759> like<00:04:23.479> this<00:04:23.800> one<00:04:24.080> this 00:04:24.189 --> 00:04:24.199 align:start position:0% low power devices uh like this one this 00:04:24.199 --> 00:04:28.110 align:start position:0% low power devices uh like this one this is<00:04:24.360> a<00:04:24.720> rock<00:04:25.000> 5B<00:04:25.720> but<00:04:26.120> uh<00:04:26.280> there<00:04:26.440> are<00:04:26.960> also<00:04:27.960> uh 00:04:28.110 --> 00:04:28.120 align:start position:0% is a rock 5B but uh there are also uh 00:04:28.120 --> 00:04:30.310 align:start position:0% is a rock 5B but uh there are also uh the<00:04:28.240> orange<00:04:28.600> Pi<00:04:28.880> 5<00:04:29.160> plus<00:04:29.560> and<00:04:29.720> and<00:04:29.840> the<00:04:29.919> nanop 00:04:30.310 --> 00:04:30.320 align:start position:0% the orange Pi 5 plus and and the nanop 00:04:30.320 --> 00:04:34.390 align:start position:0% the orange Pi 5 plus and and the nanop bc6<00:04:31.320> there<00:04:31.479> are<00:04:31.759> very<00:04:31.960> similar<00:04:32.639> devices<00:04:33.639> uh 00:04:34.390 --> 00:04:34.400 align:start position:0% bc6 there are very similar devices uh 00:04:34.400 --> 00:04:35.270 align:start position:0% bc6 there are very similar devices uh they 00:04:35.270 --> 00:04:35.280 align:start position:0% they 00:04:35.280 --> 00:04:42.430 align:start position:0% they uh<00:04:36.280> they<00:04:36.560> have<00:04:37.039> an<00:04:37.720> AR<00:04:38.120> arm<00:04:38.639> 64<00:04:39.639> core<00:04:40.639> and<00:04:41.240> um<00:04:42.000> 16 00:04:42.430 --> 00:04:42.440 align:start position:0% uh they have an AR arm 64 core and um 16 00:04:42.440 --> 00:04:46.029 align:start position:0% uh they have an AR arm 64 core and um 16 gab<00:04:42.880> of<00:04:43.039> RAM<00:04:43.600> and<00:04:44.039> Native<00:04:44.639> uh<00:04:44.800> di<00:04:45.080> support<00:04:45.680> so 00:04:46.029 --> 00:04:46.039 align:start position:0% gab of RAM and Native uh di support so 00:04:46.039 --> 00:04:50.189 align:start position:0% gab of RAM and Native uh di support so pretty<00:04:46.320> much<00:04:46.720> they<00:04:47.080> they<00:04:47.199> are<00:04:47.440> the<00:04:47.919> same 00:04:50.189 --> 00:04:50.199 align:start position:0% pretty much they they are the same 00:04:50.199 --> 00:04:54.270 align:start position:0% pretty much they they are the same um<00:04:51.199> yeah<00:04:51.560> what<00:04:51.720> we<00:04:51.919> do<00:04:52.199> is<00:04:52.800> uh<00:04:53.000> as<00:04:53.120> I<00:04:53.320> was<00:04:53.960> uh 00:04:54.270 --> 00:04:54.280 align:start position:0% um yeah what we do is uh as I was uh 00:04:54.280 --> 00:04:58.350 align:start position:0% um yeah what we do is uh as I was uh saying<00:04:55.039> uh<00:04:55.400> earlier<00:04:55.880> is<00:04:56.680> uh<00:04:57.680> we<00:04:57.880> provide<00:04:58.199> an 00:04:58.350 --> 00:04:58.360 align:start position:0% saying uh earlier is uh we provide an 00:04:58.360 --> 00:05:02.990 align:start position:0% saying uh earlier is uh we provide an image<00:04:58.800> based<00:04:59.080> on<00:04:59.360> on<00:04:59.919> Aran<00:05:00.600> s<00:05:00.960> OS<00:05:01.960> that<00:05:02.360> what<00:05:02.759> uh 00:05:02.990 --> 00:05:03.000 align:start position:0% image based on on Aran s OS that what uh 00:05:03.000 --> 00:05:05.310 align:start position:0% image based on on Aran s OS that what uh what<00:05:03.320> does<00:05:03.680> is<00:05:03.880> to 00:05:05.310 --> 00:05:05.320 align:start position:0% what does is to 00:05:05.320 --> 00:05:08.469 align:start position:0% what does is to um<00:05:06.320> installs<00:05:07.000> everything<00:05:07.320> on<00:05:07.520> first<00:05:07.800> boot<00:05:08.280> it 00:05:08.469 --> 00:05:08.479 align:start position:0% um installs everything on first boot it 00:05:08.479 --> 00:05:11.270 align:start position:0% um installs everything on first boot it runs<00:05:08.880> a<00:05:09.199> a<00:05:09.320> scet<00:05:09.759> on<00:05:09.960> on<00:05:10.120> first<00:05:10.440> boot<00:05:10.759> that<00:05:11.039> we 00:05:11.270 --> 00:05:11.280 align:start position:0% runs a a scet on on first boot that we 00:05:11.280 --> 00:05:14.350 align:start position:0% runs a a scet on on first boot that we going<00:05:11.479> to<00:05:11.639> run<00:05:12.240> here<00:05:12.560> live<00:05:13.520> uh<00:05:13.639> for<00:05:13.800> you<00:05:13.919> to<00:05:14.080> see 00:05:14.350 --> 00:05:14.360 align:start position:0% going to run here live uh for you to see 00:05:14.360 --> 00:05:17.590 align:start position:0% going to run here live uh for you to see what<00:05:14.600> what's<00:05:14.800> going<00:05:15.000> on<00:05:15.280> there<00:05:16.039> and<00:05:16.600> installs 00:05:17.590 --> 00:05:17.600 align:start position:0% what what's going on there and installs 00:05:17.600 --> 00:05:21.990 align:start position:0% what what's going on there and installs uh<00:05:18.560> everything<00:05:19.560> uh<00:05:19.720> from<00:05:20.440> uh<00:05:20.880> partitioning<00:05:21.880> uh 00:05:21.990 --> 00:05:22.000 align:start position:0% uh everything uh from uh partitioning uh 00:05:22.000 --> 00:05:26.469 align:start position:0% uh everything uh from uh partitioning uh user<00:05:22.840> creation<00:05:23.880> swap<00:05:24.880> uh<00:05:25.520> and<00:05:25.880> of<00:05:26.039> course<00:05:26.319> the 00:05:26.469 --> 00:05:26.479 align:start position:0% user creation swap uh and of course the 00:05:26.479 --> 00:05:30.510 align:start position:0% user creation swap uh and of course the ethereum<00:05:26.880> clients<00:05:27.479> that<00:05:28.039> uh<00:05:28.600> you<00:05:29.319> uh 00:05:30.510 --> 00:05:30.520 align:start position:0% ethereum clients that uh you uh 00:05:30.520 --> 00:05:32.950 align:start position:0% ethereum clients that uh you uh once<00:05:30.840> installed<00:05:31.360> you<00:05:31.520> only<00:05:31.759> need<00:05:32.039> to<00:05:32.400> to<00:05:32.560> stop 00:05:32.950 --> 00:05:32.960 align:start position:0% once installed you only need to to stop 00:05:32.960 --> 00:05:35.670 align:start position:0% once installed you only need to to stop two<00:05:33.319> system<00:05:34.160> devices<00:05:34.680> for<00:05:35.000> for<00:05:35.199> running<00:05:35.520> the 00:05:35.670 --> 00:05:35.680 align:start position:0% two system devices for for running the 00:05:35.680 --> 00:05:39.749 align:start position:0% two system devices for for running the nodes<00:05:36.479> so<00:05:37.240> it's<00:05:37.440> veryy 00:05:39.749 --> 00:05:39.759 align:start position:0% 00:05:39.759 --> 00:05:45.469 align:start position:0% convenient<00:05:41.240> um<00:05:42.360> yeah<00:05:43.400> um<00:05:44.400> we've<00:05:44.639> been<00:05:45.240> uh 00:05:45.469 --> 00:05:45.479 align:start position:0% convenient um yeah um we've been uh 00:05:45.479 --> 00:05:49.110 align:start position:0% convenient um yeah um we've been uh doing<00:05:45.880> this<00:05:46.400> uh<00:05:46.720> for<00:05:46.919> a<00:05:47.039> long<00:05:47.280> time<00:05:47.800> since<00:05:48.400> uh 00:05:49.110 --> 00:05:49.120 align:start position:0% doing this uh for a long time since uh 00:05:49.120 --> 00:05:52.950 align:start position:0% doing this uh for a long time since uh 2016<00:05:50.120> and<00:05:50.880> we<00:05:51.039> do<00:05:51.199> it<00:05:51.440> because<00:05:52.240> uh<00:05:52.479> we<00:05:52.639> think 00:05:52.950 --> 00:05:52.960 align:start position:0% 2016 and we do it because uh we think 00:05:52.960 --> 00:05:57.230 align:start position:0% 2016 and we do it because uh we think that<00:05:53.560> um<00:05:54.560> ethereum<00:05:55.160> must<00:05:55.720> uh<00:05:55.919> be 00:05:57.230 --> 00:05:57.240 align:start position:0% that um ethereum must uh be 00:05:57.240 --> 00:06:00.990 align:start position:0% that um ethereum must uh be accessible<00:05:58.240> you<00:05:58.680> people<00:05:59.240> uh<00:05:59.360> need<00:05:59.680> to<00:06:00.039> to<00:06:00.479> run 00:06:00.990 --> 00:06:01.000 align:start position:0% accessible you people uh need to to run 00:06:01.000 --> 00:06:04.070 align:start position:0% accessible you people uh need to to run notes<00:06:02.000> uh<00:06:02.199> on<00:06:02.759> convenient<00:06:03.319> devices<00:06:03.759> on 00:06:04.070 --> 00:06:04.080 align:start position:0% notes uh on convenient devices on 00:06:04.080 --> 00:06:05.589 align:start position:0% notes uh on convenient devices on commodity 00:06:05.589 --> 00:06:05.599 align:start position:0% commodity 00:06:05.599 --> 00:06:09.350 align:start position:0% commodity hardware<00:06:06.599> and<00:06:07.000> uh<00:06:07.199> this<00:06:07.319> is<00:06:07.639> our<00:06:08.120> our<00:06:08.840> vision 00:06:09.350 --> 00:06:09.360 align:start position:0% hardware and uh this is our our vision 00:06:09.360 --> 00:06:14.670 align:start position:0% hardware and uh this is our our vision of<00:06:09.759> of<00:06:10.080> e<00:06:10.720> nodes<00:06:11.720> uh<00:06:12.039> these<00:06:12.240> are<00:06:12.680> the<00:06:13.520> the<00:06:14.520> uh 00:06:14.670 --> 00:06:14.680 align:start position:0% of of e nodes uh these are the the uh 00:06:14.680 --> 00:06:17.990 align:start position:0% of of e nodes uh these are the the uh features<00:06:15.440> of<00:06:16.120> of<00:06:16.680> these<00:06:16.919> devices<00:06:17.360> low<00:06:17.680> power 00:06:17.990 --> 00:06:18.000 align:start position:0% features of of these devices low power 00:06:18.000 --> 00:06:20.589 align:start position:0% features of of these devices low power consumption<00:06:18.919> affordable<00:06:19.919> uh<00:06:20.039> these<00:06:20.240> devices 00:06:20.589 --> 00:06:20.599 align:start position:0% consumption affordable uh these devices 00:06:20.599 --> 00:06:22.309 align:start position:0% consumption affordable uh these devices are<00:06:20.919> less<00:06:21.120> than 00:06:22.309 --> 00:06:22.319 align:start position:0% are less than 00:06:22.319 --> 00:06:26.309 align:start position:0% are less than $200<00:06:23.639> um<00:06:24.639> great<00:06:24.919> for<00:06:25.120> lightweight<00:06:25.599> nodes<00:06:26.080> and 00:06:26.309 --> 00:06:26.319 align:start position:0% $200 um great for lightweight nodes and 00:06:26.319 --> 00:06:29.189 align:start position:0% $200 um great for lightweight nodes and testing<00:06:27.039> environments<00:06:28.039> uh<00:06:28.680> and<00:06:28.880> growing 00:06:29.189 --> 00:06:29.199 align:start position:0% testing environments uh and growing 00:06:29.199 --> 00:06:31.110 align:start position:0% testing environments uh and growing support<00:06:29.680> Community<00:06:30.080> Resources<00:06:30.599> we<00:06:30.759> have<00:06:30.919> a 00:06:31.110 --> 00:06:31.120 align:start position:0% support Community Resources we have a 00:06:31.120 --> 00:06:34.230 align:start position:0% support Community Resources we have a Discord<00:06:31.520> channel<00:06:32.440> uh<00:06:32.599> we<00:06:32.759> have<00:06:33.000> a<00:06:33.319> extensive 00:06:34.230 --> 00:06:34.240 align:start position:0% Discord channel uh we have a extensive 00:06:34.240 --> 00:06:37.110 align:start position:0% Discord channel uh we have a extensive uh<00:06:34.440> documentation<00:06:35.120> page<00:06:35.479> where<00:06:35.759> you<00:06:35.960> can<00:06:36.599> uh 00:06:37.110 --> 00:06:37.120 align:start position:0% uh documentation page where you can uh 00:06:37.120 --> 00:06:39.870 align:start position:0% uh documentation page where you can uh see<00:06:37.919> uh<00:06:38.680> pretty<00:06:38.919> much<00:06:39.160> everything<00:06:39.639> what<00:06:39.759> you 00:06:39.870 --> 00:06:39.880 align:start position:0% see uh pretty much everything what you 00:06:39.880 --> 00:06:42.870 align:start position:0% see uh pretty much everything what you need<00:06:40.160> to<00:06:40.479> to<00:06:40.680> fire<00:06:40.960> up<00:06:41.160> a<00:06:41.280> note<00:06:42.000> and<00:06:42.240> if<00:06:42.440> you 00:06:42.870 --> 00:06:42.880 align:start position:0% need to to fire up a note and if you 00:06:42.880 --> 00:06:45.909 align:start position:0% need to to fire up a note and if you don't<00:06:43.199> know<00:06:44.120> how<00:06:44.440> or<00:06:44.639> you<00:06:44.880> have<00:06:45.319> uh<00:06:45.599> some 00:06:45.909 --> 00:06:45.919 align:start position:0% don't know how or you have uh some 00:06:45.919 --> 00:06:48.870 align:start position:0% don't know how or you have uh some question<00:06:46.280> you<00:06:46.440> can<00:06:47.000> also<00:06:47.440> come<00:06:47.759> to<00:06:48.440> to<00:06:48.639> our 00:06:48.870 --> 00:06:48.880 align:start position:0% question you can also come to to our 00:06:48.880 --> 00:06:52.589 align:start position:0% question you can also come to to our Discord<00:06:49.240> Channel<00:06:49.599> and<00:06:49.880> we<00:06:50.199> we<00:06:50.360> can<00:06:50.520> help<00:06:50.759> you 00:06:52.589 --> 00:06:52.599 align:start position:0% Discord Channel and we we can help you 00:06:52.599 --> 00:06:57.230 align:start position:0% Discord Channel and we we can help you there<00:06:53.599> so<00:06:53.759> a<00:06:53.919> super<00:06:54.479> node<00:06:55.479> is<00:06:55.720> basically 00:06:57.230 --> 00:06:57.240 align:start position:0% there so a super node is basically 00:06:57.240 --> 00:07:01.029 align:start position:0% there so a super node is basically um<00:06:58.240> a<00:06:58.400> ler<00:06:58.759> one<00:06:59.000> Noe<00:06:59.720> a<00:06:59.960> a<00:07:00.080> layer<00:07:00.400> one<00:07:00.680> client 00:07:01.029 --> 00:07:01.039 align:start position:0% um a ler one Noe a a layer one client 00:07:01.039 --> 00:07:04.110 align:start position:0% um a ler one Noe a a layer one client and<00:07:01.240> a<00:07:01.400> layer<00:07:02.080> uh<00:07:02.240> two<00:07:02.520> client<00:07:02.879> running<00:07:03.240> along 00:07:04.110 --> 00:07:04.120 align:start position:0% and a layer uh two client running along 00:07:04.120 --> 00:07:08.749 align:start position:0% and a layer uh two client running along in<00:07:04.240> the<00:07:04.360> same<00:07:05.000> device<00:07:06.000> uh<00:07:06.199> so<00:07:06.720> usually<00:07:07.160> you<00:07:07.879> uh 00:07:08.749 --> 00:07:08.759 align:start position:0% in the same device uh so usually you uh 00:07:08.759 --> 00:07:11.950 align:start position:0% in the same device uh so usually you uh you<00:07:09.319> uh<00:07:09.440> run<00:07:09.840> them<00:07:10.199> separately<00:07:11.160> but<00:07:11.599> uh<00:07:11.800> what 00:07:11.950 --> 00:07:11.960 align:start position:0% you uh run them separately but uh what 00:07:11.960 --> 00:07:13.990 align:start position:0% you uh run them separately but uh what we<00:07:12.080> wanted<00:07:12.360> to<00:07:12.520> do<00:07:12.800> here<00:07:13.039> is<00:07:13.680> uh<00:07:13.800> to 00:07:13.990 --> 00:07:14.000 align:start position:0% we wanted to do here is uh to 00:07:14.000 --> 00:07:15.950 align:start position:0% we wanted to do here is uh to demonstrate<00:07:14.599> that<00:07:14.879> how<00:07:15.120> powerful<00:07:15.680> these 00:07:15.950 --> 00:07:15.960 align:start position:0% demonstrate that how powerful these 00:07:15.960 --> 00:07:20.350 align:start position:0% demonstrate that how powerful these devices<00:07:16.400> are<00:07:17.759> and<00:07:18.759> the<00:07:18.919> only<00:07:19.199> thing<00:07:19.919> uh<00:07:20.199> that 00:07:20.350 --> 00:07:20.360 align:start position:0% devices are and the only thing uh that 00:07:20.360 --> 00:07:23.990 align:start position:0% devices are and the only thing uh that you<00:07:20.520> need<00:07:21.319> uh<00:07:22.319> especially<00:07:22.800> for<00:07:23.080> for<00:07:23.319> this<00:07:23.800> uh 00:07:23.990 --> 00:07:24.000 align:start position:0% you need uh especially for for this uh 00:07:24.000 --> 00:07:28.589 align:start position:0% you need uh especially for for this uh setup<00:07:24.440> is<00:07:25.199> uh<00:07:25.319> a<00:07:25.520> device<00:07:25.919> with<00:07:26.240> 32<00:07:26.840> GB<00:07:27.360> of<00:07:27.599> RAM 00:07:28.589 --> 00:07:28.599 align:start position:0% setup is uh a device with 32 GB of RAM 00:07:28.599 --> 00:07:33.150 align:start position:0% setup is uh a device with 32 GB of RAM so<00:07:29.360> uh<00:07:29.720> uh<00:07:30.120> pretty<00:07:30.360> much<00:07:30.840> the<00:07:31.160> the<00:07:31.879> the 00:07:33.150 --> 00:07:33.160 align:start position:0% so uh uh pretty much the the the 00:07:33.160 --> 00:07:35.869 align:start position:0% so uh uh pretty much the the the um<00:07:34.160> the<00:07:34.280> operation<00:07:34.720> is<00:07:34.919> the<00:07:35.039> same<00:07:35.440> you<00:07:35.720> you 00:07:35.869 --> 00:07:35.879 align:start position:0% um the operation is the same you you 00:07:35.879 --> 00:07:39.749 align:start position:0% um the operation is the same you you need<00:07:36.080> to<00:07:36.319> start<00:07:37.199> uh<00:07:38.199> uh<00:07:38.560> two<00:07:38.840> system<00:07:39.199> Dev<00:07:39.560> two 00:07:39.749 --> 00:07:39.759 align:start position:0% need to start uh uh two system Dev two 00:07:39.759 --> 00:07:42.230 align:start position:0% need to start uh uh two system Dev two system<00:07:40.120> services<00:07:40.599> for<00:07:40.960> the<00:07:41.240> L1<00:07:41.720> client<00:07:42.120> and 00:07:42.230 --> 00:07:42.240 align:start position:0% system services for the L1 client and 00:07:42.240 --> 00:07:44.629 align:start position:0% system services for the L1 client and two<00:07:42.520> system<00:07:42.800> service<00:07:43.160> for<00:07:43.280> the<00:07:43.400> L2<00:07:43.759> client<00:07:44.440> and 00:07:44.629 --> 00:07:44.639 align:start position:0% two system service for the L2 client and 00:07:44.639 --> 00:07:48.990 align:start position:0% two system service for the L2 client and once<00:07:44.840> you<00:07:45.039> do<00:07:45.560> that<00:07:46.560> uh<00:07:47.280> you<00:07:47.639> have<00:07:48.159> a<00:07:48.360> supern 00:07:48.990 --> 00:07:49.000 align:start position:0% once you do that uh you have a supern 00:07:49.000 --> 00:07:52.550 align:start position:0% once you do that uh you have a supern running<00:07:50.000> uh<00:07:50.560> an<00:07:50.759> L1<00:07:51.479> client<00:07:51.800> running<00:07:52.120> and<00:07:52.280> an 00:07:52.550 --> 00:07:52.560 align:start position:0% running uh an L1 client running and an 00:07:52.560 --> 00:07:57.189 align:start position:0% running uh an L1 client running and an L2 00:07:57.189 --> 00:07:57.199 align:start position:0% 00:07:57.199 --> 00:08:00.990 align:start position:0% run<00:07:58.199> yeah<00:07:58.960> as<00:07:59.080> you<00:07:59.199> know<00:07:59.879> um<00:08:00.280> in<00:08:00.479> the<00:08:00.720> in<00:08:00.840> the 00:08:00.990 --> 00:08:01.000 align:start position:0% run yeah as you know um in the in the 00:08:01.000 --> 00:08:04.189 align:start position:0% run yeah as you know um in the in the last<00:08:01.280> years<00:08:02.039> uh<00:08:02.280> ethereum<00:08:02.879> it's<00:08:03.080> been<00:08:03.879> uh 00:08:04.189 --> 00:08:04.199 align:start position:0% last years uh ethereum it's been uh 00:08:04.199 --> 00:08:07.510 align:start position:0% last years uh ethereum it's been uh struggling<00:08:04.919> with<00:08:05.440> scalability<00:08:06.440> and<00:08:06.879> and<00:08:07.120> L2 00:08:07.510 --> 00:08:07.520 align:start position:0% struggling with scalability and and L2 00:08:07.520 --> 00:08:10.149 align:start position:0% struggling with scalability and and L2 nodes<00:08:07.800> are<00:08:08.039> very<00:08:08.280> important<00:08:09.080> and<00:08:09.800> uh<00:08:10.000> we 00:08:10.149 --> 00:08:10.159 align:start position:0% nodes are very important and uh we 00:08:10.159 --> 00:08:13.110 align:start position:0% nodes are very important and uh we wanted<00:08:10.680> to<00:08:11.319> give<00:08:11.599> users<00:08:12.120> the<00:08:12.319> ability<00:08:12.680> to<00:08:12.840> run 00:08:13.110 --> 00:08:13.120 align:start position:0% wanted to give users the ability to run 00:08:13.120 --> 00:08:15.950 align:start position:0% wanted to give users the ability to run these<00:08:13.319> kinds<00:08:13.520> of<00:08:13.680> nodes<00:08:14.280> because<00:08:15.280> uh<00:08:15.479> we<00:08:15.639> think 00:08:15.950 --> 00:08:15.960 align:start position:0% these kinds of nodes because uh we think 00:08:15.960 --> 00:08:19.830 align:start position:0% these kinds of nodes because uh we think that<00:08:17.000> uh<00:08:18.000> as<00:08:18.199> well<00:08:18.400> as<00:08:18.599> you<00:08:18.759> can<00:08:19.280> verify<00:08:19.720> the 00:08:19.830 --> 00:08:19.840 align:start position:0% that uh as well as you can verify the 00:08:19.840 --> 00:08:23.029 align:start position:0% that uh as well as you can verify the chain<00:08:20.639> with<00:08:20.800> the<00:08:21.080> L1<00:08:21.520> nodes<00:08:22.240> it's<00:08:22.479> important 00:08:23.029 --> 00:08:23.039 align:start position:0% chain with the L1 nodes it's important 00:08:23.039 --> 00:08:25.350 align:start position:0% chain with the L1 nodes it's important that<00:08:23.240> you<00:08:23.520> can<00:08:23.800> interact<00:08:24.280> directly<00:08:24.879> with<00:08:25.159> with 00:08:25.350 --> 00:08:25.360 align:start position:0% that you can interact directly with with 00:08:25.360 --> 00:08:26.950 align:start position:0% that you can interact directly with with L2<00:08:25.759> notes<00:08:26.120> as 00:08:26.950 --> 00:08:26.960 align:start position:0% L2 notes as 00:08:26.960 --> 00:08:31.350 align:start position:0% L2 notes as well<00:08:27.960> so<00:08:28.520> the<00:08:28.680> boards<00:08:29.159> as<00:08:29.520> I<00:08:29.639> was<00:08:29.759> saying<00:08:30.400> um 00:08:31.350 --> 00:08:31.360 align:start position:0% well so the boards as I was saying um 00:08:31.360 --> 00:08:33.750 align:start position:0% well so the boards as I was saying um these<00:08:31.520> are<00:08:31.919> the<00:08:32.360> the<00:08:32.839> devices<00:08:33.360> that<00:08:33.560> we 00:08:33.750 --> 00:08:33.760 align:start position:0% these are the the devices that we 00:08:33.760 --> 00:08:38.190 align:start position:0% these are the the devices that we support<00:08:34.560> uh<00:08:34.680> orange<00:08:35.080> Pi<00:08:35.399> P<00:08:35.919> orange<00:08:36.320> Pi<00:08:36.719> 5<00:08:37.440> um<00:08:38.080> is 00:08:38.190 --> 00:08:38.200 align:start position:0% support uh orange Pi P orange Pi 5 um is 00:08:38.200 --> 00:08:40.190 align:start position:0% support uh orange Pi P orange Pi 5 um is a<00:08:38.320> little<00:08:38.599> discontinued<00:08:39.320> because<00:08:39.599> it<00:08:39.760> doesn't 00:08:40.190 --> 00:08:40.200 align:start position:0% a little discontinued because it doesn't 00:08:40.200 --> 00:08:44.269 align:start position:0% a little discontinued because it doesn't have<00:08:40.839> uh<00:08:41.120> a<00:08:41.320> good<00:08:41.919> uh<00:08:42.279> this<00:08:42.640> support<00:08:43.159> but<00:08:43.919> uh<00:08:44.080> it 00:08:44.269 --> 00:08:44.279 align:start position:0% have uh a good uh this support but uh it 00:08:44.279 --> 00:08:46.670 align:start position:0% have uh a good uh this support but uh it still<00:08:44.560> works<00:08:45.399> and<00:08:45.640> for<00:08:45.839> the<00:08:45.959> super<00:08:46.240> nodes<00:08:46.560> you 00:08:46.670 --> 00:08:46.680 align:start position:0% still works and for the super nodes you 00:08:46.680 --> 00:08:50.430 align:start position:0% still works and for the super nodes you need<00:08:47.240> uh<00:08:47.560> 32<00:08:48.080> GB<00:08:48.519> of<00:08:48.680> RAM<00:08:49.360> that's<00:08:49.800> the<00:08:49.959> only 00:08:50.430 --> 00:08:50.440 align:start position:0% need uh 32 GB of RAM that's the only 00:08:50.440 --> 00:08:55.350 align:start position:0% need uh 32 GB of RAM that's the only difference<00:08:50.959> with<00:08:51.360> uh<00:08:51.680> with<00:08:51.800> a<00:08:51.959> normal<00:08:52.279> node 00:08:55.350 --> 00:08:55.360 align:start position:0% 00:08:55.360 --> 00:08:59.590 align:start position:0% okay<00:08:56.360> uh<00:08:56.600> yeah 00:08:59.590 --> 00:08:59.600 align:start position:0% okay uh yeah 00:08:59.600 --> 00:09:02.509 align:start position:0% okay uh yeah it's<00:08:59.720> somewhat<00:09:00.040> the<00:09:00.120> same<00:09:00.360> here<00:09:00.640> it's<00:09:01.320> uh<00:09:02.320> what 00:09:02.509 --> 00:09:02.519 align:start position:0% it's somewhat the same here it's uh what 00:09:02.519 --> 00:09:04.790 align:start position:0% it's somewhat the same here it's uh what would<00:09:02.680> you<00:09:02.800> need<00:09:03.360> apart<00:09:03.640> from<00:09:03.959> the<00:09:04.399> the<00:09:04.640> the 00:09:04.790 --> 00:09:04.800 align:start position:0% would you need apart from the the the 00:09:04.800 --> 00:09:07.509 align:start position:0% would you need apart from the the the the<00:09:04.880> small<00:09:05.160> device<00:09:05.640> the<00:09:06.279> The<00:09:06.680> Rock<00:09:06.959> five<00:09:07.240> like 00:09:07.509 --> 00:09:07.519 align:start position:0% the small device the The Rock five like 00:09:07.519 --> 00:09:11.389 align:start position:0% the small device the The Rock five like here<00:09:08.000> you<00:09:08.160> need<00:09:08.399> a<00:09:08.720> mbme<00:09:09.519> dis<00:09:10.519> okay<00:09:10.880> again<00:09:11.240> here 00:09:11.389 --> 00:09:11.399 align:start position:0% here you need a mbme dis okay again here 00:09:11.399 --> 00:09:14.710 align:start position:0% here you need a mbme dis okay again here will<00:09:11.600> depends<00:09:12.519> uh<00:09:13.480> if<00:09:13.600> you<00:09:13.760> want<00:09:13.959> to<00:09:14.079> be<00:09:14.240> futter 00:09:14.710 --> 00:09:14.720 align:start position:0% will depends uh if you want to be futter 00:09:14.720 --> 00:09:18.389 align:start position:0% will depends uh if you want to be futter proof<00:09:15.480> of<00:09:15.800> if<00:09:16.440> you<00:09:16.600> want<00:09:16.760> to<00:09:17.480> build<00:09:17.760> an<00:09:18.000> arive 00:09:18.389 --> 00:09:18.399 align:start position:0% proof of if you want to build an arive 00:09:18.399 --> 00:09:21.150 align:start position:0% proof of if you want to build an arive note<00:09:19.120> you<00:09:19.320> even<00:09:19.640> can<00:09:19.920> build<00:09:20.200> an<00:09:20.440> archive<00:09:20.839> note 00:09:21.150 --> 00:09:21.160 align:start position:0% note you even can build an archive note 00:09:21.160 --> 00:09:24.110 align:start position:0% note you even can build an archive note here<00:09:21.440> with<00:09:21.760> with<00:09:21.920> these<00:09:22.399> uh<00:09:22.800> devices<00:09:23.800> but<00:09:24.000> you 00:09:24.110 --> 00:09:24.120 align:start position:0% here with with these uh devices but you 00:09:24.120 --> 00:09:26.710 align:start position:0% here with with these uh devices but you will<00:09:24.279> you<00:09:24.480> need<00:09:24.959> at<00:09:25.120> least<00:09:25.720> 4<00:09:26.000> tabt<00:09:26.480> for<00:09:26.600> an 00:09:26.710 --> 00:09:26.720 align:start position:0% will you need at least 4 tabt for an 00:09:26.720 --> 00:09:29.389 align:start position:0% will you need at least 4 tabt for an archive<00:09:27.079> node<00:09:27.480> and<00:09:27.720> 2<00:09:27.959> tabt<00:09:28.440> for<00:09:28.640> a<00:09:29.000> for<00:09:29.160> an 00:09:29.389 --> 00:09:29.399 align:start position:0% archive node and 2 tabt for a for an 00:09:29.399 --> 00:09:32.590 align:start position:0% archive node and 2 tabt for a for an normal<00:09:29.640> note<00:09:29.800> for<00:09:29.920> a<00:09:30.040> full<00:09:30.600> Noe<00:09:31.600> uh<00:09:31.800> you<00:09:31.959> need 00:09:32.590 --> 00:09:32.600 align:start position:0% normal note for a full Noe uh you need 00:09:32.600 --> 00:09:35.949 align:start position:0% normal note for a full Noe uh you need uh<00:09:32.920> an<00:09:33.120> SD<00:09:33.480> car<00:09:34.200> uh<00:09:34.399> here<00:09:34.680> please<00:09:35.200> buy<00:09:35.560> the<00:09:35.720> best 00:09:35.949 --> 00:09:35.959 align:start position:0% uh an SD car uh here please buy the best 00:09:35.959 --> 00:09:38.430 align:start position:0% uh an SD car uh here please buy the best SD<00:09:36.240> card<00:09:36.480> that<00:09:36.640> you<00:09:37.160> you<00:09:37.360> can<00:09:37.560> afford<00:09:37.880> because 00:09:38.430 --> 00:09:38.440 align:start position:0% SD card that you you can afford because 00:09:38.440 --> 00:09:40.230 align:start position:0% SD card that you you can afford because important<00:09:38.800> it's<00:09:38.959> very<00:09:39.160> important<00:09:39.760> the<00:09:40.120> the 00:09:40.230 --> 00:09:40.240 align:start position:0% important it's very important the the 00:09:40.240 --> 00:09:42.790 align:start position:0% important it's very important the the throughput<00:09:40.720> of<00:09:41.040> the<00:09:41.399> thisd<00:09:41.800> car<00:09:42.000> and<00:09:42.279> the<00:09:42.560> and 00:09:42.790 --> 00:09:42.800 align:start position:0% throughput of the thisd car and the and 00:09:42.800 --> 00:09:44.269 align:start position:0% throughput of the thisd car and the and the 00:09:44.269 --> 00:09:44.279 align:start position:0% the 00:09:44.279 --> 00:09:47.710 align:start position:0% the quality<00:09:45.320> um<00:09:46.320> of<00:09:46.440> course<00:09:46.720> an<00:09:46.959> ethernet<00:09:47.399> cable 00:09:47.710 --> 00:09:47.720 align:start position:0% quality um of course an ethernet cable 00:09:47.720 --> 00:09:50.389 align:start position:0% quality um of course an ethernet cable if<00:09:47.839> you<00:09:48.000> want<00:09:48.240> to<00:09:48.600> to<00:09:48.800> have<00:09:49.000> the<00:09:49.160> best<00:09:49.920> uh 00:09:50.389 --> 00:09:50.399 align:start position:0% if you want to to have the best uh 00:09:50.399 --> 00:09:53.150 align:start position:0% if you want to to have the best uh internet<00:09:50.800> connection<00:09:51.360> the<00:09:51.680> the<00:09:51.839> L 00:09:53.150 --> 00:09:53.160 align:start position:0% internet connection the the L 00:09:53.160 --> 00:09:55.790 align:start position:0% internet connection the the L uh<00:09:54.160> uh<00:09:54.480> the<00:09:54.600> less<00:09:54.800> problems<00:09:55.120> with<00:09:55.240> the<00:09:55.320> network 00:09:55.790 --> 00:09:55.800 align:start position:0% uh uh the less problems with the network 00:09:55.800 --> 00:09:57.710 align:start position:0% uh uh the less problems with the network but<00:09:56.240> they're<00:09:56.480> very<00:09:56.680> sensible<00:09:57.079> to<00:09:57.279> the<00:09:57.480> to<00:09:57.600> the 00:09:57.710 --> 00:09:57.720 align:start position:0% but they're very sensible to the to the 00:09:57.720 --> 00:10:00.030 align:start position:0% but they're very sensible to the to the network<00:09:58.079> and<00:09:58.279> know<00:09:58.839> you<00:09:59.040> want<00:09:59.519> you<00:09:59.720> don't<00:09:59.920> want 00:10:00.030 --> 00:10:00.040 align:start position:0% network and know you want you don't want 00:10:00.040 --> 00:10:01.829 align:start position:0% network and know you want you don't want to<00:10:00.160> lose<00:10:00.360> any<00:10:00.839> station<00:10:01.160> if<00:10:01.279> you<00:10:01.360> are<00:10:01.519> going<00:10:01.680> to 00:10:01.829 --> 00:10:01.839 align:start position:0% to lose any station if you are going to 00:10:01.839 --> 00:10:04.630 align:start position:0% to lose any station if you are going to validate<00:10:02.240> with<00:10:02.399> these<00:10:03.079> devices<00:10:04.079> uh<00:10:04.440> we 00:10:04.630 --> 00:10:04.640 align:start position:0% validate with these devices uh we 00:10:04.640 --> 00:10:06.310 align:start position:0% validate with these devices uh we recommend<00:10:05.079> to<00:10:05.279> use 00:10:06.310 --> 00:10:06.320 align:start position:0% recommend to use 00:10:06.320 --> 00:10:08.949 align:start position:0% recommend to use the<00:10:07.320> the<00:10:07.760> connection<00:10:08.079> of<00:10:08.240> the 00:10:08.949 --> 00:10:08.959 align:start position:0% the the connection of the 00:10:08.959 --> 00:10:13.069 align:start position:0% the the connection of the device<00:10:09.959> and<00:10:10.680> these<00:10:11.040> devices<00:10:11.680> are<00:10:12.640> uh 00:10:13.069 --> 00:10:13.079 align:start position:0% device and these devices are uh 00:10:13.079 --> 00:10:15.550 align:start position:0% device and these devices are uh especially<00:10:13.519> when<00:10:13.720> you<00:10:13.839> are<00:10:14.480> uh<00:10:14.600> sinking<00:10:15.440> the 00:10:15.550 --> 00:10:15.560 align:start position:0% especially when you are uh sinking the 00:10:15.560 --> 00:10:18.430 align:start position:0% especially when you are uh sinking the first<00:10:15.800> time<00:10:16.160> are<00:10:16.440> very<00:10:16.680> hot<00:10:17.360> and<00:10:17.880> the<00:10:18.120> the<00:10:18.240> best 00:10:18.430 --> 00:10:18.440 align:start position:0% first time are very hot and the the best 00:10:18.440 --> 00:10:20.910 align:start position:0% first time are very hot and the the best thing<00:10:18.680> to<00:10:19.000> to<00:10:19.200> get<00:10:19.440> a 00:10:20.910 --> 00:10:20.920 align:start position:0% thing to to get a 00:10:20.920 --> 00:10:25.069 align:start position:0% thing to to get a uh<00:10:21.920> uh<00:10:22.200> a<00:10:22.399> very<00:10:22.880> quiet<00:10:23.240> device<00:10:23.680> is<00:10:24.320> buy<00:10:24.560> a<00:10:24.760> case 00:10:25.069 --> 00:10:25.079 align:start position:0% uh uh a very quiet device is buy a case 00:10:25.079 --> 00:10:33.230 align:start position:0% uh uh a very quiet device is buy a case like<00:10:25.320> this<00:10:25.600> with<00:10:26.160> uh<00:10:26.560> a<00:10:26.760> passive<00:10:27.160> head<00:10:27.399> scene 00:10:33.230 --> 00:10:33.240 align:start position:0% 00:10:33.240 --> 00:10:36.910 align:start position:0% uh<00:10:34.240> the<00:10:35.079> another<00:10:35.440> very<00:10:35.639> very<00:10:35.839> important<00:10:36.560> thing 00:10:36.910 --> 00:10:36.920 align:start position:0% uh the another very very important thing 00:10:36.920 --> 00:10:41.150 align:start position:0% uh the another very very important thing is<00:10:37.360> to<00:10:37.519> choose<00:10:38.279> a<00:10:38.600> very<00:10:39.279> good<00:10:39.519> a<00:10:39.680> high-end<00:10:40.399> mbmm 00:10:41.150 --> 00:10:41.160 align:start position:0% is to choose a very good a high-end mbmm 00:10:41.160 --> 00:10:44.110 align:start position:0% is to choose a very good a high-end mbmm disc<00:10:41.680> because<00:10:42.480> we<00:10:42.680> move<00:10:43.200> from<00:10:43.399> the<00:10:43.560> image<00:10:43.920> from 00:10:44.110 --> 00:10:44.120 align:start position:0% disc because we move from the image from 00:10:44.120 --> 00:10:45.509 align:start position:0% disc because we move from the image from the<00:10:44.240> standard<00:10:44.600> Linux<00:10:44.920> installation 00:10:45.509 --> 00:10:45.519 align:start position:0% the standard Linux installation 00:10:45.519 --> 00:10:48.150 align:start position:0% the standard Linux installation everything<00:10:45.959> that<00:10:46.440> uh<00:10:46.880> usually<00:10:47.399> right<00:10:47.600> to<00:10:47.760> disk 00:10:48.150 --> 00:10:48.160 align:start position:0% everything that uh usually right to disk 00:10:48.160 --> 00:10:52.710 align:start position:0% everything that uh usually right to disk to<00:10:48.399> the<00:10:48.880> mbme<00:10:49.639> disc<00:10:50.320> in<00:10:50.440> order<00:10:50.760> to<00:10:51.040> keep<00:10:51.399> the<00:10:51.880> SD 00:10:52.710 --> 00:10:52.720 align:start position:0% to the mbme disc in order to keep the SD 00:10:52.720 --> 00:10:58.350 align:start position:0% to the mbme disc in order to keep the SD carard<00:10:53.920> uh<00:10:54.920> safe<00:10:55.360> and<00:10:55.680> health<00:10:56.519> we<00:10:56.760> moove<00:10:57.360> uh 00:10:58.350 --> 00:10:58.360 align:start position:0% carard uh safe and health we moove uh 00:10:58.360 --> 00:11:01.990 align:start position:0% carard uh safe and health we moove uh all<00:10:58.639> the<00:10:58.800> things<00:10:59.079> like<00:10:59.440> the<00:10:59.560> logs<00:11:00.200> or<00:11:00.600> the<00:11:01.600> swap 00:11:01.990 --> 00:11:02.000 align:start position:0% all the things like the logs or the swap 00:11:02.000 --> 00:11:07.590 align:start position:0% all the things like the logs or the swap partition<00:11:02.519> to<00:11:02.800> the<00:11:03.320> to<00:11:03.600> the<00:11:04.880> mbn<00:11:05.880> dis<00:11:06.600> because 00:11:07.590 --> 00:11:07.600 align:start position:0% partition to the to the mbn dis because 00:11:07.600 --> 00:11:09.670 align:start position:0% partition to the to the mbn dis because is<00:11:07.839> built<00:11:08.200> for<00:11:08.519> for<00:11:08.720> brighting<00:11:09.079> and<00:11:09.279> the<00:11:09.360> SD 00:11:09.670 --> 00:11:09.680 align:start position:0% is built for for brighting and the SD 00:11:09.680 --> 00:11:11.990 align:start position:0% is built for for brighting and the SD car<00:11:10.120> is 00:11:11.990 --> 00:11:12.000 align:start position:0% car is 00:11:12.000 --> 00:11:16.350 align:start position:0% car is slower<00:11:13.000> uh<00:11:13.760> we<00:11:13.920> have<00:11:14.120> a<00:11:14.440> list<00:11:14.760> in<00:11:14.880> our<00:11:15.360> doation 00:11:16.350 --> 00:11:16.360 align:start position:0% slower uh we have a list in our doation 00:11:16.360 --> 00:11:20.430 align:start position:0% slower uh we have a list in our doation that<00:11:17.279> uh<00:11:17.920> with<00:11:18.120> some<00:11:19.120> dis<00:11:19.480> that<00:11:19.720> we<00:11:20.120> thought 00:11:20.430 --> 00:11:20.440 align:start position:0% that uh with some dis that we thought 00:11:20.440 --> 00:11:23.509 align:start position:0% that uh with some dis that we thought that<00:11:20.639> are<00:11:20.880> the<00:11:21.040> best<00:11:21.720> but<00:11:22.079> at<00:11:22.200> the<00:11:22.320> end<00:11:22.680> is<00:11:23.360> for 00:11:23.509 --> 00:11:23.519 align:start position:0% that are the best but at the end is for 00:11:23.519 --> 00:11:24.949 align:start position:0% that are the best but at the end is for us<00:11:23.680> is<00:11:23.839> very<00:11:24.000> important<00:11:24.320> we<00:11:24.440> have<00:11:24.680> B 00:11:24.949 --> 00:11:24.959 align:start position:0% us is very important we have B 00:11:24.959 --> 00:11:29.790 align:start position:0% us is very important we have B experience<00:11:25.480> with<00:11:26.160> uh<00:11:27.160> uh<00:11:27.720> bath<00:11:28.079> MBM<00:11:28.760> disc<00:11:29.360> that 00:11:29.790 --> 00:11:29.800 align:start position:0% experience with uh uh bath MBM disc that 00:11:29.800 --> 00:11:32.710 align:start position:0% experience with uh uh bath MBM disc that we<00:11:30.040> don't<00:11:30.480> uh<00:11:30.880> don't<00:11:31.079> suggest<00:11:31.440> to 00:11:32.710 --> 00:11:32.720 align:start position:0% we don't uh don't suggest to 00:11:32.720 --> 00:11:37.430 align:start position:0% we don't uh don't suggest to buy<00:11:34.120> uh<00:11:35.120> I<00:11:35.200> think<00:11:35.560> the<00:11:35.800> the<00:11:36.200> the<00:11:36.399> hard<00:11:36.760> thing 00:11:37.430 --> 00:11:37.440 align:start position:0% buy uh I think the the the hard thing 00:11:37.440 --> 00:11:39.949 align:start position:0% buy uh I think the the the hard thing here<00:11:37.680> is<00:11:38.160> uh<00:11:38.480> enable<00:11:38.959> port<00:11:39.200> forwarding<00:11:39.760> with 00:11:39.949 --> 00:11:39.959 align:start position:0% here is uh enable port forwarding with 00:11:39.959 --> 00:11:42.629 align:start position:0% here is uh enable port forwarding with your<00:11:40.440> if<00:11:40.560> you<00:11:40.680> are<00:11:40.959> doing<00:11:41.240> sing<00:11:41.639> at<00:11:41.839> home<00:11:42.440> with 00:11:42.629 --> 00:11:42.639 align:start position:0% your if you are doing sing at home with 00:11:42.639 --> 00:11:46.509 align:start position:0% your if you are doing sing at home with your<00:11:43.000> locally<00:11:43.560> ISP<00:11:44.160> you<00:11:44.320> need<00:11:44.519> to<00:11:45.120> open<00:11:46.120> uh<00:11:46.360> at 00:11:46.509 --> 00:11:46.519 align:start position:0% your locally ISP you need to open uh at 00:11:46.519 --> 00:11:48.030 align:start position:0% your locally ISP you need to open uh at least<00:11:46.720> two 00:11:48.030 --> 00:11:48.040 align:start position:0% least two 00:11:48.040 --> 00:11:50.949 align:start position:0% least two ports<00:11:49.040> yeah<00:11:49.279> and<00:11:49.560> and<00:11:49.760> network<00:11:50.320> as<00:11:50.480> well 00:11:50.949 --> 00:11:50.959 align:start position:0% ports yeah and and network as well 00:11:50.959 --> 00:11:53.110 align:start position:0% ports yeah and and network as well because<00:11:51.360> we<00:11:51.519> we've<00:11:51.720> seen<00:11:52.079> a<00:11:52.240> lot<00:11:52.399> of<00:11:52.639> problems 00:11:53.110 --> 00:11:53.120 align:start position:0% because we we've seen a lot of problems 00:11:53.120 --> 00:11:55.870 align:start position:0% because we we've seen a lot of problems that<00:11:53.399> comes<00:11:53.680> from<00:11:54.279> from<00:11:54.560> network<00:11:55.360> uh<00:11:55.680> for 00:11:55.870 --> 00:11:55.880 align:start position:0% that comes from from network uh for 00:11:55.880 --> 00:11:58.430 align:start position:0% that comes from from network uh for example<00:11:56.440> in<00:11:56.639> Spain<00:11:57.079> uh<00:11:57.240> bandwidth<00:11:57.760> is<00:11:58.160> quite 00:11:58.430 --> 00:11:58.440 align:start position:0% example in Spain uh bandwidth is quite 00:11:58.440 --> 00:12:03.269 align:start position:0% example in Spain uh bandwidth is quite good<00:11:59.320> it's<00:11:59.600> really<00:11:59.959> quite<00:12:00.240> good<00:12:01.000> uh<00:12:02.000> fiber<00:12:02.959> uh 00:12:03.269 --> 00:12:03.279 align:start position:0% good it's really quite good uh fiber uh 00:12:03.279 --> 00:12:07.190 align:start position:0% good it's really quite good uh fiber uh connections<00:12:04.279> uh<00:12:04.639> you<00:12:04.839> can<00:12:05.440> uh<00:12:05.600> syn<00:12:06.279> all 00:12:07.190 --> 00:12:07.200 align:start position:0% connections uh you can uh syn all 00:12:07.200 --> 00:12:10.710 align:start position:0% connections uh you can uh syn all flawlessly<00:12:08.200> uh<00:12:08.399> it<00:12:08.720> it<00:12:08.959> work<00:12:09.440> works<00:12:09.800> great<00:12:10.519> but 00:12:10.710 --> 00:12:10.720 align:start position:0% flawlessly uh it it work works great but 00:12:10.720 --> 00:12:14.350 align:start position:0% flawlessly uh it it work works great but we've<00:12:10.920> seen<00:12:11.279> other<00:12:11.959> uh<00:12:12.240> countries<00:12:12.920> and<00:12:13.800> from 00:12:14.350 --> 00:12:14.360 align:start position:0% we've seen other uh countries and from 00:12:14.360 --> 00:12:16.990 align:start position:0% we've seen other uh countries and from from<00:12:14.880> from<00:12:15.120> Europe<00:12:15.680> that<00:12:16.240> um<00:12:16.560> they<00:12:16.760> have 00:12:16.990 --> 00:12:17.000 align:start position:0% from from Europe that um they have 00:12:17.000 --> 00:12:19.790 align:start position:0% from from Europe that um they have problems<00:12:17.360> with<00:12:17.600> this<00:12:18.480> so<00:12:19.079> yeah<00:12:19.480> this<00:12:19.600> is 00:12:19.790 --> 00:12:19.800 align:start position:0% problems with this so yeah this is 00:12:19.800 --> 00:12:22.350 align:start position:0% problems with this so yeah this is another<00:12:20.480> um<00:12:21.160> another<00:12:21.639> uh<00:12:21.800> problem<00:12:22.120> that<00:12:22.240> we 00:12:22.350 --> 00:12:22.360 align:start position:0% another um another uh problem that we 00:12:22.360 --> 00:12:27.189 align:start position:0% another um another uh problem that we are<00:12:22.959> uh<00:12:23.959> uh<00:12:24.160> seeing<00:12:24.959> with<00:12:25.279> with<00:12:25.480> users<00:12:26.440> a<00:12:26.600> small 00:12:27.189 --> 00:12:27.199 align:start position:0% are uh uh seeing with with users a small 00:12:27.199 --> 00:12:30.550 align:start position:0% are uh uh seeing with with users a small real<00:12:27.519> life<00:12:27.760> example<00:12:28.120> for<00:12:28.399> this<00:12:28.600> is<00:12:28.839> the<00:12:29.480> ntp 00:12:30.550 --> 00:12:30.560 align:start position:0% real life example for this is the ntp 00:12:30.560 --> 00:12:33.550 align:start position:0% real life example for this is the ntp protocol<00:12:31.560> uh<00:12:32.120> in<00:12:32.279> order<00:12:32.560> to<00:12:32.800> not<00:12:33.000> to<00:12:33.120> lose<00:12:33.320> any 00:12:33.550 --> 00:12:33.560 align:start position:0% protocol uh in order to not to lose any 00:12:33.560 --> 00:12:35.389 align:start position:0% protocol uh in order to not to lose any attestations<00:12:34.320> it's<00:12:34.560> very<00:12:34.760> very<00:12:34.959> important 00:12:35.389 --> 00:12:35.399 align:start position:0% attestations it's very very important 00:12:35.399 --> 00:12:39.189 align:start position:0% attestations it's very very important that<00:12:35.639> you<00:12:36.279> your<00:12:36.560> device<00:12:36.880> is<00:12:37.800> on<00:12:38.040> time<00:12:38.639> but<00:12:39.000> to 00:12:39.189 --> 00:12:39.199 align:start position:0% that you your device is on time but to 00:12:39.199 --> 00:12:41.430 align:start position:0% that you your device is on time but to the<00:12:39.639> second<00:12:40.639> so<00:12:40.839> we<00:12:41.000> change<00:12:41.320> the 00:12:41.430 --> 00:12:41.440 align:start position:0% the second so we change the 00:12:41.440 --> 00:12:43.910 align:start position:0% the second so we change the configuration<00:12:41.959> of<00:12:42.120> the<00:12:42.240> ntp<00:12:42.920> client<00:12:43.399> here<00:12:43.760> in 00:12:43.910 --> 00:12:43.920 align:start position:0% configuration of the ntp client here in 00:12:43.920 --> 00:12:46.990 align:start position:0% configuration of the ntp client here in order<00:12:44.160> to<00:12:44.279> be<00:12:44.399> more<00:12:44.839> aggressive<00:12:45.839> and<00:12:46.800> uh 00:12:46.990 --> 00:12:47.000 align:start position:0% order to be more aggressive and uh 00:12:47.000 --> 00:12:49.910 align:start position:0% order to be more aggressive and uh trying<00:12:47.320> to<00:12:47.760> to<00:12:47.959> get<00:12:48.120> in<00:12:48.360> time<00:12:49.279> in<00:12:49.360> a<00:12:49.519> very<00:12:49.720> very 00:12:49.910 --> 00:12:49.920 align:start position:0% trying to to get in time in a very very 00:12:49.920 --> 00:12:51.550 align:start position:0% trying to to get in time in a very very aggressive<00:12:50.360> way<00:12:50.680> the<00:12:50.839> the<00:12:50.959> most<00:12:51.160> aggressive 00:12:51.550 --> 00:12:51.560 align:start position:0% aggressive way the the most aggressive 00:12:51.560 --> 00:12:53.230 align:start position:0% aggressive way the the most aggressive way<00:12:51.720> that<00:12:51.839> is<00:12:52.000> allow<00:12:52.320> with<00:12:52.480> for<00:12:52.680> most<00:12:52.880> of<00:12:53.079> the 00:12:53.230 --> 00:12:53.240 align:start position:0% way that is allow with for most of the 00:12:53.240 --> 00:12:56.750 align:start position:0% way that is allow with for most of the ntp<00:12:54.000> servers<00:12:55.000> in<00:12:55.160> order<00:12:55.360> to<00:12:55.680> not<00:12:55.880> lose<00:12:56.279> any<00:12:56.560> a 00:12:56.750 --> 00:12:56.760 align:start position:0% ntp servers in order to not lose any a 00:12:56.760 --> 00:12:58.470 align:start position:0% ntp servers in order to not lose any a second<00:12:57.079> because<00:12:57.760> sometimes<00:12:57.959> when<00:12:58.120> you<00:12:58.240> lose 00:12:58.470 --> 00:12:58.480 align:start position:0% second because sometimes when you lose 00:12:58.480 --> 00:13:00.910 align:start position:0% second because sometimes when you lose one<00:12:58.639> second<00:12:58.880> or<00:12:59.240> seconds<00:12:59.560> and<00:13:00.040> maybe<00:13:00.560> it's<00:13:00.720> not 00:13:00.910 --> 00:13:00.920 align:start position:0% one second or seconds and maybe it's not 00:13:00.920 --> 00:13:03.189 align:start position:0% one second or seconds and maybe it's not important<00:13:01.320> in<00:13:01.519> any<00:13:01.760> other<00:13:02.000> computer<00:13:02.480> here<00:13:02.680> you 00:13:03.189 --> 00:13:03.199 align:start position:0% important in any other computer here you 00:13:03.199 --> 00:13:04.870 align:start position:0% important in any other computer here you can<00:13:03.360> lose<00:13:03.560> an<00:13:03.800> attestation<00:13:04.440> because<00:13:04.600> of<00:13:04.720> the 00:13:04.870 --> 00:13:04.880 align:start position:0% can lose an attestation because of the 00:13:04.880 --> 00:13:09.790 align:start position:0% can lose an attestation because of the protocol<00:13:05.800> so<00:13:06.720> uh<00:13:07.199> having<00:13:08.000> uh<00:13:08.360> low<00:13:08.600> latency<00:13:09.040> in 00:13:09.790 --> 00:13:09.800 align:start position:0% protocol so uh having uh low latency in 00:13:09.800 --> 00:13:12.310 align:start position:0% protocol so uh having uh low latency in your<00:13:10.800> a<00:13:10.959> good<00:13:11.160> internet<00:13:11.519> connection<00:13:11.839> at<00:13:12.040> home 00:13:12.310 --> 00:13:12.320 align:start position:0% your a good internet connection at home 00:13:12.320 --> 00:13:14.189 align:start position:0% your a good internet connection at home is<00:13:12.519> is<00:13:13.040> quite<00:13:13.279> quite 00:13:14.189 --> 00:13:14.199 align:start position:0% is is quite quite 00:13:14.199 --> 00:13:17.670 align:start position:0% is is quite quite important<00:13:15.199> and<00:13:15.720> we<00:13:15.839> are<00:13:16.120> going<00:13:16.399> to<00:13:16.600> start<00:13:17.079> a<00:13:17.519> a 00:13:17.670 --> 00:13:17.680 align:start position:0% important and we are going to start a a 00:13:17.680 --> 00:13:19.829 align:start position:0% important and we are going to start a a live<00:13:17.920> demo<00:13:18.160> using<00:13:18.440> our<00:13:18.680> image<00:13:18.959> and<00:13:19.279> a<00:13:19.399> real 00:13:19.829 --> 00:13:19.839 align:start position:0% live demo using our image and a real 00:13:19.839 --> 00:13:22.430 align:start position:0% live demo using our image and a real Hardware<00:13:20.320> here<00:13:20.600> in<00:13:20.760> order<00:13:21.000> to<00:13:21.199> create<00:13:22.040> uh<00:13:22.320> a 00:13:22.430 --> 00:13:22.440 align:start position:0% Hardware here in order to create uh a 00:13:22.440 --> 00:13:25.269 align:start position:0% Hardware here in order to create uh a full<00:13:22.680> node<00:13:23.399> left<00:13:23.760> here 00:13:25.269 --> 00:13:25.279 align:start position:0% full node left here 00:13:25.279 --> 00:13:29.310 align:start position:0% full node left here um<00:13:26.279> yeah<00:13:27.279> we're<00:13:27.480> going<00:13:27.639> to<00:13:27.880> flash<00:13:28.440> the<00:13:28.920> as<00:13:29.199> the 00:13:29.310 --> 00:13:29.320 align:start position:0% um yeah we're going to flash the as the 00:13:29.320 --> 00:13:30.150 align:start position:0% um yeah we're going to flash the as the card 00:13:30.150 --> 00:13:30.160 align:start position:0% card 00:13:30.160 --> 00:13:35.310 align:start position:0% card with<00:13:31.160> uh<00:13:32.120> in<00:13:32.279> this<00:13:32.519> case<00:13:32.800> with<00:13:33.160> a<00:13:33.880> stock<00:13:34.880> image 00:13:35.310 --> 00:13:35.320 align:start position:0% with uh in this case with a stock image 00:13:35.320 --> 00:13:38.230 align:start position:0% with uh in this case with a stock image from<00:13:35.800> from<00:13:36.000> Aram<00:13:37.000> because<00:13:37.360> we<00:13:37.480> want<00:13:37.680> you<00:13:37.839> to 00:13:38.230 --> 00:13:38.240 align:start position:0% from from Aram because we want you to 00:13:38.240 --> 00:13:42.030 align:start position:0% from from Aram because we want you to see<00:13:39.120> uh<00:13:39.720> we<00:13:39.839> are<00:13:40.000> going<00:13:40.320> to<00:13:41.320> to<00:13:41.519> launch<00:13:41.839> the 00:13:42.030 --> 00:13:42.040 align:start position:0% see uh we are going to to launch the 00:13:42.040 --> 00:13:43.949 align:start position:0% see uh we are going to to launch the script<00:13:42.480> manually<00:13:42.959> because<00:13:43.160> we<00:13:43.279> wanted<00:13:43.600> to<00:13:43.800> you 00:13:43.949 --> 00:13:43.959 align:start position:0% script manually because we wanted to you 00:13:43.959 --> 00:13:46.750 align:start position:0% script manually because we wanted to you to<00:13:44.120> see<00:13:44.880> uh<00:13:45.079> what's<00:13:45.320> going<00:13:45.560> on<00:13:45.839> there<00:13:46.440> uh<00:13:46.600> what 00:13:46.750 --> 00:13:46.760 align:start position:0% to see uh what's going on there uh what 00:13:46.760 --> 00:13:49.790 align:start position:0% to see uh what's going on there uh what the<00:13:46.880> script<00:13:47.279> does<00:13:47.720> and<00:13:48.160> and<00:13:48.680> all<00:13:49.000> the<00:13:49.320> logs 00:13:49.790 --> 00:13:49.800 align:start position:0% the script does and and all the logs 00:13:49.800 --> 00:13:54.030 align:start position:0% the script does and and all the logs that<00:13:50.199> the<00:13:50.920> uh<00:13:51.519> is<00:13:52.040> uh<00:13:52.560> writing<00:13:53.560> along<00:13:53.839> with 00:13:54.030 --> 00:13:54.040 align:start position:0% that the uh is uh writing along with 00:13:54.040 --> 00:13:59.150 align:start position:0% that the uh is uh writing along with installation 00:13:59.150 --> 00:13:59.160 align:start position:0% 00:13:59.160 --> 00:14:00.150 align:start position:0% we 00:14:00.150 --> 00:14:00.160 align:start position:0% we 00:14:00.160 --> 00:14:03.110 align:start position:0% we are<00:14:01.160> here<00:14:01.519> we<00:14:01.639> are<00:14:01.800> going<00:14:01.959> to<00:14:02.160> use<00:14:02.399> our 00:14:03.110 --> 00:14:03.120 align:start position:0% are here we are going to use our 00:14:03.120 --> 00:14:04.550 align:start position:0% are here we are going to use our official<00:14:03.480> documentation<00:14:04.040> in<00:14:04.120> order<00:14:04.399> to 00:14:04.550 --> 00:14:04.560 align:start position:0% official documentation in order to 00:14:04.560 --> 00:14:06.189 align:start position:0% official documentation in order to follow<00:14:04.920> the<00:14:05.120> same<00:14:05.360> instructions<00:14:05.880> that<00:14:06.079> you 00:14:06.189 --> 00:14:06.199 align:start position:0% follow the same instructions that you 00:14:06.199 --> 00:14:09.550 align:start position:0% follow the same instructions that you will<00:14:06.399> follow<00:14:07.120> in<00:14:07.199> order<00:14:07.440> to<00:14:07.600> create<00:14:08.040> this<00:14:08.880> uh 00:14:09.550 --> 00:14:09.560 align:start position:0% will follow in order to create this uh 00:14:09.560 --> 00:14:11.350 align:start position:0% will follow in order to create this uh this<00:14:09.759> installation<00:14:10.279> but<00:14:10.519> we<00:14:10.600> are<00:14:10.800> going<00:14:11.000> to 00:14:11.350 --> 00:14:11.360 align:start position:0% this installation but we are going to 00:14:11.360 --> 00:14:14.509 align:start position:0% this installation but we are going to step<00:14:11.639> some<00:14:12.480> skip<00:14:12.759> some<00:14:13.000> steps<00:14:13.959> because<00:14:14.279> we<00:14:14.360> are 00:14:14.509 --> 00:14:14.519 align:start position:0% step some skip some steps because we are 00:14:14.519 --> 00:14:16.949 align:start position:0% step some skip some steps because we are going<00:14:14.680> to<00:14:14.839> not<00:14:15.199> here<00:14:15.480> waiting<00:14:15.800> for<00:14:16.440> download 00:14:16.949 --> 00:14:16.959 align:start position:0% going to not here waiting for download 00:14:16.959 --> 00:14:19.829 align:start position:0% going to not here waiting for download an<00:14:17.160> image<00:14:17.399> or<00:14:17.519> something<00:14:17.800> like<00:14:17.959> this<00:14:18.759> okay<00:14:19.639> uh 00:14:19.829 --> 00:14:19.839 align:start position:0% an image or something like this okay uh 00:14:19.839 --> 00:14:22.749 align:start position:0% an image or something like this okay uh this<00:14:19.959> is<00:14:20.199> our<00:14:21.079> our<00:14:21.360> public<00:14:21.680> recomendation<00:14:22.639> you 00:14:22.749 --> 00:14:22.759 align:start position:0% this is our our public recomendation you 00:14:22.759 --> 00:14:25.030 align:start position:0% this is our our public recomendation you can<00:14:23.079> find<00:14:23.240> it<00:14:23.399> in<00:14:23.560> Google<00:14:23.839> or<00:14:24.079> in<00:14:24.360> our<00:14:24.680> Twitter 00:14:25.030 --> 00:14:25.040 align:start position:0% can find it in Google or in our Twitter 00:14:25.040 --> 00:14:27.030 align:start position:0% can find it in Google or in our Twitter account<00:14:25.680> it's<00:14:25.920> very<00:14:26.120> easy<00:14:26.320> to<00:14:26.440> find<00:14:26.680> but<00:14:26.800> it's 00:14:27.030 --> 00:14:27.040 align:start position:0% account it's very easy to find but it's 00:14:27.040 --> 00:14:29.829 align:start position:0% account it's very easy to find but it's in<00:14:27.279> R<00:14:27.560> the<00:14:27.720> do 00:14:29.829 --> 00:14:29.839 align:start position:0% in R the do 00:14:29.839 --> 00:14:31.990 align:start position:0% in R the do uh<00:14:30.320> have<00:14:30.639> the<00:14:30.800> same<00:14:31.040> things<00:14:31.279> that<00:14:31.480> you<00:14:31.600> see<00:14:31.800> the 00:14:31.990 --> 00:14:32.000 align:start position:0% uh have the same things that you see the 00:14:32.000 --> 00:14:34.350 align:start position:0% uh have the same things that you see the recommended<00:14:32.519> Hardware<00:14:33.079> you<00:14:33.240> could<00:14:33.480> see<00:14:33.920> here 00:14:34.350 --> 00:14:34.360 align:start position:0% recommended Hardware you could see here 00:14:34.360 --> 00:14:38.509 align:start position:0% recommended Hardware you could see here we<00:14:34.560> have<00:14:34.920> a<00:14:35.440> small<00:14:36.440> um<00:14:37.440> specs<00:14:37.800> of<00:14:38.000> all<00:14:38.240> the 00:14:38.509 --> 00:14:38.519 align:start position:0% we have a small um specs of all the 00:14:38.519 --> 00:14:40.550 align:start position:0% we have a small um specs of all the supported<00:14:39.399> uh 00:14:40.550 --> 00:14:40.560 align:start position:0% supported uh 00:14:40.560 --> 00:14:44.030 align:start position:0% supported uh devices<00:14:41.560> um<00:14:42.560> the<00:14:42.720> first<00:14:42.959> thing<00:14:43.199> that<00:14:43.399> you<00:14:43.800> want 00:14:44.030 --> 00:14:44.040 align:start position:0% devices um the first thing that you want 00:14:44.040 --> 00:14:46.590 align:start position:0% devices um the first thing that you want to<00:14:44.240> have<00:14:44.720> uh<00:14:44.880> apart<00:14:45.279> from<00:14:45.560> building<00:14:46.000> your 00:14:46.590 --> 00:14:46.600 align:start position:0% to have uh apart from building your 00:14:46.600 --> 00:14:49.269 align:start position:0% to have uh apart from building your device<00:14:47.480> putting<00:14:47.839> in<00:14:48.040> the<00:14:48.199> box<00:14:48.600> and<00:14:48.959> something 00:14:49.269 --> 00:14:49.279 align:start position:0% device putting in the box and something 00:14:49.279 --> 00:14:51.829 align:start position:0% device putting in the box and something like<00:14:49.440> this<00:14:49.639> is<00:14:49.920> to<00:14:50.120> download<00:14:50.680> the<00:14:51.079> image<00:14:51.680> you 00:14:51.829 --> 00:14:51.839 align:start position:0% like this is to download the image you 00:14:51.839 --> 00:14:53.790 align:start position:0% like this is to download the image you have<00:14:52.000> to<00:14:52.160> choose<00:14:52.680> the<00:14:52.839> right<00:14:53.120> image<00:14:53.360> for<00:14:53.560> your 00:14:53.790 --> 00:14:53.800 align:start position:0% have to choose the right image for your 00:14:53.800 --> 00:14:56.550 align:start position:0% have to choose the right image for your device<00:14:54.160> you<00:14:54.279> can<00:14:54.440> buy<00:14:54.800> an<00:14:54.920> NC<00:14:55.480> a<00:14:55.639> rock<00:14:55.880> five<00:14:56.279> or 00:14:56.550 --> 00:14:56.560 align:start position:0% device you can buy an NC a rock five or 00:14:56.560 --> 00:14:59.389 align:start position:0% device you can buy an NC a rock five or orang<00:14:56.920> P<00:14:57.600> you<00:14:57.720> can<00:14:57.959> donad<00:14:58.519> or<00:14:58.720> all<00:14:59.120> much<00:14:59.279> I 00:14:59.389 --> 00:14:59.399 align:start position:0% orang P you can donad or all much I 00:14:59.399 --> 00:15:01.310 align:start position:0% orang P you can donad or all much I already<00:14:59.680> download<00:15:00.120> it<00:15:00.560> I'm<00:15:00.720> just<00:15:01.040> going<00:15:01.160> to 00:15:01.310 --> 00:15:01.320 align:start position:0% already download it I'm just going to 00:15:01.320 --> 00:15:07.030 align:start position:0% already download it I'm just going to see<00:15:01.519> it<00:15:02.199> but<00:15:03.000> uh<00:15:03.360> it's<00:15:03.600> quite<00:15:03.920> E<00:15:04.959> uh<00:15:05.959> let's<00:15:06.279> see 00:15:07.030 --> 00:15:07.040 align:start position:0% see it but uh it's quite E uh let's see 00:15:07.040 --> 00:15:08.749 align:start position:0% see it but uh it's quite E uh let's see we<00:15:07.160> are<00:15:07.279> going<00:15:07.480> to<00:15:07.800> do<00:15:07.959> a<00:15:08.120> life<00:15:08.320> installation 00:15:08.749 --> 00:15:08.759 align:start position:0% we are going to do a life installation 00:15:08.759 --> 00:15:14.269 align:start position:0% we are going to do a life installation with<00:15:08.880> a<00:15:09.000> rock<00:15:09.240> five<00:15:09.519> we<00:15:09.639> are<00:15:09.800> going<00:15:10.000> to<00:15:10.759> come 00:15:14.269 --> 00:15:14.279 align:start position:0% 00:15:14.279 --> 00:15:16.350 align:start position:0% here 00:15:16.350 --> 00:15:16.360 align:start position:0% here 00:15:16.360 --> 00:15:20.430 align:start position:0% here umage<00:15:17.600> okay<00:15:18.600> rock<00:15:18.920> five<00:15:19.519> and<00:15:19.720> you<00:15:19.839> can<00:15:20.040> do<00:15:20.199> that 00:15:20.430 --> 00:15:20.440 align:start position:0% umage okay rock five and you can do that 00:15:20.440 --> 00:15:26.189 align:start position:0% umage okay rock five and you can do that here<00:15:21.279> the<00:15:22.279> even<00:15:23.040> the<00:15:24.040> the<00:15:24.759> Dage<00:15:25.519> I<00:15:25.839> already 00:15:26.189 --> 00:15:26.199 align:start position:0% here the even the the Dage I already 00:15:26.199 --> 00:15:29.629 align:start position:0% here the even the the Dage I already done<00:15:26.440> it<00:15:26.680> so<00:15:27.040> then<00:15:27.279> going<00:15:27.440> to<00:15:27.959> do<00:15:29.040> once<00:15:29.240> you 00:15:29.629 --> 00:15:29.639 align:start position:0% done it so then going to do once you 00:15:29.639 --> 00:15:31.230 align:start position:0% done it so then going to do once you download<00:15:30.000> your<00:15:30.120> image<00:15:30.480> you<00:15:30.600> could<00:15:30.839> verify 00:15:31.230 --> 00:15:31.240 align:start position:0% download your image you could verify 00:15:31.240 --> 00:15:33.269 align:start position:0% download your image you could verify that<00:15:31.440> this<00:15:31.680> everything<00:15:31.959> is<00:15:32.160> okay<00:15:32.519> we<00:15:32.720> provide 00:15:33.269 --> 00:15:33.279 align:start position:0% that this everything is okay we provide 00:15:33.279 --> 00:15:38.870 align:start position:0% that this everything is okay we provide the<00:15:34.000> the<00:15:34.839> sh<00:15:35.839> 256<00:15:36.839> uh 00:15:38.870 --> 00:15:38.880 align:start position:0% the the sh 256 uh 00:15:38.880 --> 00:15:42.350 align:start position:0% the the sh 256 uh um<00:15:39.880> hash<00:15:40.600> or<00:15:40.800> than<00:15:40.920> to<00:15:41.680> that<00:15:41.880> everything<00:15:42.160> is 00:15:42.350 --> 00:15:42.360 align:start position:0% um hash or than to that everything is 00:15:42.360 --> 00:15:47.069 align:start position:0% um hash or than to that everything is okay<00:15:42.680> is<00:15:43.079> our<00:15:43.560> official<00:15:44.079> image<00:15:45.079> and<00:15:45.959> the<00:15:46.959> the 00:15:47.069 --> 00:15:47.079 align:start position:0% okay is our official image and the the 00:15:47.079 --> 00:15:49.189 align:start position:0% okay is our official image and the the next<00:15:47.319> thing<00:15:47.560> is<00:15:47.720> to<00:15:48.160> write<00:15:48.399> the<00:15:48.519> iMat<00:15:48.880> to<00:15:49.040> the 00:15:49.189 --> 00:15:49.199 align:start position:0% next thing is to write the iMat to the 00:15:49.199 --> 00:15:51.949 align:start position:0% next thing is to write the iMat to the SD 00:15:51.949 --> 00:15:51.959 align:start position:0% 00:15:51.959 --> 00:15:54.990 align:start position:0% car<00:15:52.959> by<00:15:53.079> the<00:15:53.199> way<00:15:53.480> if<00:15:53.959> someone<00:15:54.440> has<00:15:54.720> any 00:15:54.990 --> 00:15:55.000 align:start position:0% car by the way if someone has any 00:15:55.000 --> 00:15:57.949 align:start position:0% car by the way if someone has any question<00:15:55.519> or<00:15:55.880> any<00:15:56.160> doubt<00:15:56.880> uh<00:15:57.079> please 00:15:57.949 --> 00:15:57.959 align:start position:0% question or any doubt uh please 00:15:57.959 --> 00:16:07.269 align:start position:0% question or any doubt uh please interrupt<00:15:58.600> and<00:15:59.199> and<00:16:00.040> whatever<00:16:00.880> I 00:16:07.269 --> 00:16:07.279 align:start position:0% 00:16:07.279 --> 00:16:11.189 align:start position:0% mean<00:16:08.279> those<00:16:08.959> uh<00:16:09.480> computers<00:16:10.240> are<00:16:10.720> those 00:16:11.189 --> 00:16:11.199 align:start position:0% mean those uh computers are those 00:16:11.199 --> 00:16:12.910 align:start position:0% mean those uh computers are those computers<00:16:11.839> are 00:16:12.910 --> 00:16:12.920 align:start position:0% computers are 00:16:12.920 --> 00:16:16.230 align:start position:0% computers are $180<00:16:13.920> yeah<00:16:14.800> cost<00:16:15.560> I've<00:16:15.680> seen<00:16:15.959> that<00:16:16.079> for 00:16:16.230 --> 00:16:16.240 align:start position:0% $180 yeah cost I've seen that for 00:16:16.240 --> 00:16:18.829 align:start position:0% $180 yeah cost I've seen that for example<00:16:17.120> right<00:16:17.360> now<00:16:17.920> int 00:16:18.829 --> 00:16:18.839 align:start position:0% example right now int 00:16:18.839 --> 00:16:21.749 align:start position:0% example right now int Compu<00:16:20.000> Compu 00:16:21.749 --> 00:16:21.759 align:start position:0% Compu Compu 00:16:21.759 --> 00:16:24.990 align:start position:0% Compu Compu just<00:16:22.759> for<00:16:22.920> example<00:16:23.279> are<00:16:23.519> buying<00:16:24.000> for 00:16:24.990 --> 00:16:25.000 align:start position:0% just for example are buying for 00:16:25.000 --> 00:16:27.110 align:start position:0% just for example are buying for $600<00:16:26.000> which<00:16:26.079> is<00:16:26.240> more<00:16:26.360> or<00:16:26.519> less<00:16:26.759> what<00:16:26.880> will 00:16:27.110 --> 00:16:27.120 align:start position:0% $600 which is more or less what will 00:16:27.120 --> 00:16:29.749 align:start position:0% $600 which is more or less what will cost<00:16:27.399> this<00:16:27.600> with<00:16:27.720> the 00:16:29.749 --> 00:16:29.759 align:start position:0% cost this with the 00:16:29.759 --> 00:16:32.670 align:start position:0% cost this with the well<00:16:30.759> it's<00:16:30.920> a<00:16:31.000> little<00:16:31.199> more<00:16:31.440> expensive<00:16:31.920> but<00:16:32.440> uh 00:16:32.670 --> 00:16:32.680 align:start position:0% well it's a little more expensive but uh 00:16:32.680 --> 00:16:35.350 align:start position:0% well it's a little more expensive but uh yeah<00:16:32.880> it's<00:16:33.199> it's<00:16:33.800> uh<00:16:34.079> it's<00:16:34.199> a<00:16:34.360> good<00:16:34.639> question 00:16:35.350 --> 00:16:35.360 align:start position:0% yeah it's it's uh it's a good question 00:16:35.360 --> 00:16:39.829 align:start position:0% yeah it's it's uh it's a good question um<00:16:36.000> yeah<00:16:36.279> but<00:16:37.079> uh<00:16:37.880> for<00:16:38.079> example<00:16:38.880> the<00:16:39.319> uh<00:16:39.519> power 00:16:39.829 --> 00:16:39.839 align:start position:0% um yeah but uh for example the uh power 00:16:39.839 --> 00:16:44.629 align:start position:0% um yeah but uh for example the uh power user<00:16:40.319> of<00:16:40.680> of<00:16:40.880> this<00:16:41.079> device<00:16:41.399> is<00:16:41.560> 10<00:16:41.839> BTS<00:16:43.240> and<00:16:44.240> you 00:16:44.629 --> 00:16:44.639 align:start position:0% user of of this device is 10 BTS and you 00:16:44.639 --> 00:16:47.990 align:start position:0% user of of this device is 10 BTS and you you<00:16:45.040> know<00:16:45.279> that<00:16:45.800> uh<00:16:46.480> you<00:16:46.680> have<00:16:46.880> to<00:16:47.440> run<00:16:47.759> this 00:16:47.990 --> 00:16:48.000 align:start position:0% you know that uh you have to run this 00:16:48.000 --> 00:16:51.949 align:start position:0% you know that uh you have to run this 24/7<00:16:49.000> so<00:16:49.720> it's<00:16:49.920> a<00:16:50.319> big<00:16:50.600> difference<00:16:51.079> with<00:16:51.680> other 00:16:51.949 --> 00:16:51.959 align:start position:0% 24/7 so it's a big difference with other 00:16:51.959 --> 00:16:53.670 align:start position:0% 24/7 so it's a big difference with other devices<00:16:52.399> that's<00:16:52.560> for<00:16:52.680> example<00:16:53.160> and<00:16:53.319> there<00:16:53.480> are 00:16:53.670 --> 00:16:53.680 align:start position:0% devices that's for example and there are 00:16:53.680 --> 00:16:57.949 align:start position:0% devices that's for example and there are more<00:16:54.639> uh<00:16:55.639> uh<00:16:56.319> convenience<00:16:56.920> a<00:16:57.079> small<00:16:57.399> factor 00:16:57.949 --> 00:16:57.959 align:start position:0% more uh uh convenience a small factor 00:16:57.959 --> 00:17:00.990 align:start position:0% more uh uh convenience a small factor you<00:16:58.079> can<00:16:58.279> put<00:16:58.440> it<00:16:58.560> in<00:16:58.920> any<00:16:59.120> corner<00:16:59.519> of<00:16:59.959> of<00:17:00.360> the 00:17:00.990 --> 00:17:01.000 align:start position:0% you can put it in any corner of of the 00:17:01.000 --> 00:17:04.710 align:start position:0% you can put it in any corner of of the of<00:17:01.279> the<00:17:01.480> of<00:17:01.600> your<00:17:01.880> house<00:17:02.240> or<00:17:02.519> the<00:17:02.920> roor<00:17:03.920> there<00:17:04.600> I 00:17:04.710 --> 00:17:04.720 align:start position:0% of the of your house or the roor there I 00:17:04.720 --> 00:17:05.549 align:start position:0% of the of your house or the roor there I think 00:17:05.549 --> 00:17:05.559 align:start position:0% think 00:17:05.559 --> 00:17:09.429 align:start position:0% think that<00:17:06.559> ER<00:17:07.319> any<00:17:07.600> device<00:17:07.959> is<00:17:08.280> is<00:17:08.480> fine<00:17:08.799> to<00:17:09.079> to<00:17:09.240> run 00:17:09.429 --> 00:17:09.439 align:start position:0% that ER any device is is fine to to run 00:17:09.439 --> 00:17:12.110 align:start position:0% that ER any device is is fine to to run a<00:17:09.600> node<00:17:09.880> I<00:17:09.919> mean<00:17:10.280> we<00:17:10.400> are<00:17:10.520> not<00:17:10.720> competing<00:17:11.520> uh 00:17:12.110 --> 00:17:12.120 align:start position:0% a node I mean we are not competing uh 00:17:12.120 --> 00:17:14.590 align:start position:0% a node I mean we are not competing uh because<00:17:12.720> we<00:17:12.880> are<00:17:13.160> there<00:17:13.439> with<00:17:13.760> that<00:17:14.039> node<00:17:14.400> that 00:17:14.590 --> 00:17:14.600 align:start position:0% because we are there with that node that 00:17:14.600 --> 00:17:17.470 align:start position:0% because we are there with that node that are<00:17:15.480> an<00:17:15.679> amazing<00:17:16.439> option<00:17:16.839> for<00:17:17.039> for<00:17:17.199> running 00:17:17.470 --> 00:17:17.480 align:start position:0% are an amazing option for for running 00:17:17.480 --> 00:17:21.669 align:start position:0% are an amazing option for for running noes<00:17:18.480> but<00:17:19.120> uh<00:17:19.919> choices<00:17:20.280> are<00:17:20.559> good<00:17:21.000> I<00:17:21.120> mean<00:17:21.520> you 00:17:21.669 --> 00:17:21.679 align:start position:0% noes but uh choices are good I mean you 00:17:21.679 --> 00:17:23.750 align:start position:0% noes but uh choices are good I mean you know<00:17:22.640> and<00:17:22.880> another<00:17:23.280> I<00:17:23.360> think<00:17:23.520> another 00:17:23.750 --> 00:17:23.760 align:start position:0% know and another I think another 00:17:23.760 --> 00:17:26.470 align:start position:0% know and another I think another important<00:17:24.120> thing<00:17:24.319> is<00:17:24.439> is<00:17:24.600> to<00:17:24.959> add<00:17:25.600> the<00:17:26.240> add 00:17:26.470 --> 00:17:26.480 align:start position:0% important thing is is to add the add 00:17:26.480 --> 00:17:28.590 align:start position:0% important thing is is to add the add diversity<00:17:26.959> to<00:17:27.160> the<00:17:27.520> to<00:17:27.640> the<00:17:27.799> network<00:17:28.319> if<00:17:28.439> you 00:17:28.590 --> 00:17:28.600 align:start position:0% diversity to the to the network if you 00:17:28.600 --> 00:17:32.070 align:start position:0% diversity to the to the network if you only<00:17:29.039> around<00:17:29.600> empty<00:17:30.559> compatible<00:17:31.080> processors 00:17:32.070 --> 00:17:32.080 align:start position:0% only around empty compatible processors 00:17:32.080 --> 00:17:34.870 align:start position:0% only around empty compatible processors and<00:17:32.240> you<00:17:32.400> have<00:17:33.200> a<00:17:33.360> bag<00:17:33.720> like<00:17:34.080> a<00:17:34.160> few<00:17:34.360> years<00:17:34.600> ago 00:17:34.870 --> 00:17:34.880 align:start position:0% and you have a bag like a few years ago 00:17:34.880 --> 00:17:37.630 align:start position:0% and you have a bag like a few years ago like<00:17:35.039> it<00:17:35.120> was<00:17:35.559> Spectre<00:17:36.559> this<00:17:36.760> B<00:17:37.120> who<00:17:37.320> affects 00:17:37.630 --> 00:17:37.640 align:start position:0% like it was Spectre this B who affects 00:17:37.640 --> 00:17:39.230 align:start position:0% like it was Spectre this B who affects the<00:17:37.760> hardware<00:17:38.120> D<00:17:38.520> the<00:17:38.640> hardware<00:17:38.960> for<00:17:39.120> the 00:17:39.230 --> 00:17:39.240 align:start position:0% the hardware D the hardware for the 00:17:39.240 --> 00:17:41.029 align:start position:0% the hardware D the hardware for the processors<00:17:39.679> the<00:17:39.799> inter<00:17:40.120> processors<00:17:40.600> mostly 00:17:41.029 --> 00:17:41.039 align:start position:0% processors the inter processors mostly 00:17:41.039 --> 00:17:45.350 align:start position:0% processors the inter processors mostly but<00:17:41.320> some<00:17:42.000> kind<00:17:42.280> of<00:17:42.559> of<00:17:42.919> problem<00:17:43.320> with<00:17:43.559> the<00:17:44.360> uh 00:17:45.350 --> 00:17:45.360 align:start position:0% but some kind of of problem with the uh 00:17:45.360 --> 00:17:49.110 align:start position:0% but some kind of of problem with the uh MD<00:17:45.799> processors<00:17:46.280> also<00:17:47.280> at<00:17:47.440> the<00:17:47.520> end<00:17:48.000> you<00:17:48.640> could 00:17:49.110 --> 00:17:49.120 align:start position:0% MD processors also at the end you could 00:17:49.120 --> 00:17:51.470 align:start position:0% MD processors also at the end you could have<00:17:49.280> a<00:17:49.440> problem<00:17:49.760> and<00:17:50.039> adding<00:17:50.640> armed<00:17:51.000> devices 00:17:51.470 --> 00:17:51.480 align:start position:0% have a problem and adding armed devices 00:17:51.480 --> 00:17:53.630 align:start position:0% have a problem and adding armed devices with<00:17:51.760> another<00:17:52.200> architecture<00:17:52.799> and<00:17:53.080> other<00:17:53.400> kind 00:17:53.630 --> 00:17:53.640 align:start position:0% with another architecture and other kind 00:17:53.640 --> 00:17:56.470 align:start position:0% with another architecture and other kind of<00:17:54.480> CPU<00:17:54.840> processs<00:17:55.360> is<00:17:55.520> good<00:17:55.960> for<00:17:56.120> the<00:17:56.240> health 00:17:56.470 --> 00:17:56.480 align:start position:0% of CPU processs is good for the health 00:17:56.480 --> 00:17:59.070 align:start position:0% of CPU processs is good for the health of<00:17:56.600> the<00:17:57.000> network<00:17:58.000> it's<00:17:58.080> a<00:17:58.280> divers<00:17:58.840> we<00:17:58.960> are 00:17:59.070 --> 00:17:59.080 align:start position:0% of the network it's a divers we are 00:17:59.080 --> 00:18:02.510 align:start position:0% of the network it's a divers we are looking<00:17:59.360> into<00:17:59.600> RIS<00:17:59.960> five<00:18:00.280> as<00:18:00.440> well<00:18:00.960> yeah<00:18:01.559> we<00:18:02.159> SN 00:18:02.510 --> 00:18:02.520 align:start position:0% looking into RIS five as well yeah we SN 00:18:02.520 --> 00:18:06.149 align:start position:0% looking into RIS five as well yeah we SN it<00:18:02.640> a<00:18:02.799> note<00:18:03.240> with<00:18:03.480> a<00:18:04.240> a<00:18:04.400> note<00:18:04.919> not<00:18:05.080> a<00:18:05.200> note<00:18:05.559> a<00:18:05.760> get 00:18:06.149 --> 00:18:06.159 align:start position:0% it a note with a a note not a note a get 00:18:06.159 --> 00:18:08.830 align:start position:0% it a note with a a note not a note a get a<00:18:06.360> get<00:18:06.559> note<00:18:06.960> a<00:18:07.159> GU<00:18:07.360> client<00:18:07.760> with<00:18:08.000> a<00:18:08.240> risk<00:18:08.600> five 00:18:08.830 --> 00:18:08.840 align:start position:0% a get note a GU client with a risk five 00:18:08.840 --> 00:18:11.029 align:start position:0% a get note a GU client with a risk five board<00:18:09.720> and<00:18:09.960> yeah<00:18:10.280> I<00:18:10.360> think<00:18:10.720> it's<00:18:10.880> very 00:18:11.029 --> 00:18:11.039 align:start position:0% board and yeah I think it's very 00:18:11.039 --> 00:18:12.870 align:start position:0% board and yeah I think it's very interesting<00:18:11.440> that<00:18:11.640> people<00:18:11.880> can<00:18:12.080> choose<00:18:12.679> not 00:18:12.870 --> 00:18:12.880 align:start position:0% interesting that people can choose not 00:18:12.880 --> 00:18:17.310 align:start position:0% interesting that people can choose not only<00:18:13.280> a<00:18:13.679> device<00:18:14.480> but<00:18:15.080> architecture<00:18:16.039> and<00:18:16.840> and 00:18:17.310 --> 00:18:17.320 align:start position:0% only a device but architecture and and 00:18:17.320 --> 00:18:20.070 align:start position:0% only a device but architecture and and have<00:18:17.880> a<00:18:18.039> lot<00:18:18.200> of<00:18:18.480> a<00:18:18.600> lot<00:18:18.720> of<00:18:18.919> choices<00:18:19.360> to<00:18:19.720> to<00:18:19.960> to 00:18:20.070 --> 00:18:20.080 align:start position:0% have a lot of a lot of choices to to to 00:18:20.080 --> 00:18:24.510 align:start position:0% have a lot of a lot of choices to to to choose<00:18:20.360> from<00:18:21.360> okay<00:18:22.080> I<00:18:22.200> can<00:18:22.360> agree<00:18:22.640> with 00:18:24.510 --> 00:18:24.520 align:start position:0% choose from okay I can agree with 00:18:24.520 --> 00:18:26.430 align:start position:0% choose from okay I can agree with that<00:18:25.520> you 00:18:26.430 --> 00:18:26.440 align:start position:0% that you 00:18:26.440 --> 00:18:29.870 align:start position:0% that you mention<00:18:27.440> TV<00:18:27.799> settings<00:18:28.880> to<00:18:29.039> keep<00:18:29.200> the<00:18:29.320> server 00:18:29.870 --> 00:18:29.880 align:start position:0% mention TV settings to keep the server 00:18:29.880 --> 00:18:32.510 align:start position:0% mention TV settings to keep the server on<00:18:30.360> time<00:18:31.360> you<00:18:31.520> mentioned<00:18:31.840> like<00:18:32.000> you<00:18:32.120> have<00:18:32.280> some 00:18:32.510 --> 00:18:32.520 align:start position:0% on time you mentioned like you have some 00:18:32.520 --> 00:18:34.909 align:start position:0% on time you mentioned like you have some specific<00:18:32.960> settings<00:18:33.320> for<00:18:33.760> um<00:18:34.400> the<00:18:34.679> time 00:18:34.909 --> 00:18:34.919 align:start position:0% specific settings for um the time 00:18:34.919 --> 00:18:36.909 align:start position:0% specific settings for um the time servers<00:18:35.720> they<00:18:35.919> pretty<00:18:36.200> aggressive<00:18:36.640> can<00:18:36.799> you 00:18:36.909 --> 00:18:36.919 align:start position:0% servers they pretty aggressive can you 00:18:36.919 --> 00:19:22.990 align:start position:0% servers they pretty aggressive can you share<00:18:37.200> these<00:18:37.320> settings<00:18:37.679> later 00:19:22.990 --> 00:19:23.000 align:start position:0% 00:19:23.000 --> 00:19:40.029 align:start position:0% I<00:19:23.400> I'm<00:19:23.600> looking<00:19:23.799> for<00:19:24.000> it<00:19:24.840> one<00:19:25.080> off<00:19:25.799> this<00:19:26.679> conf 00:19:40.029 --> 00:19:40.039 align:start position:0% 00:19:40.039 --> 00:19:43.710 align:start position:0% foree 00:19:43.710 --> 00:19:43.720 align:start position:0% 00:19:43.720 --> 00:19:47.909 align:start position:0% spee 00:19:47.909 --> 00:19:47.919 align:start position:0% 00:19:47.919 --> 00:19:56.110 align:start position:0% speee 00:19:56.110 --> 00:19:56.120 align:start position:0% 00:19:56.120 --> 00:19:59.270 align:start position:0% speeech<00:19:57.120> no 00:19:59.270 --> 00:19:59.280 align:start position:0% speeech no 00:19:59.280 --> 00:20:00.630 align:start position:0% speeech no I<00:19:59.400> have<00:19:59.520> to<00:19:59.679> find<00:19:59.880> it<00:20:00.080> because<00:20:00.320> I<00:20:00.440> don't 00:20:00.630 --> 00:20:00.640 align:start position:0% I have to find it because I don't 00:20:00.640 --> 00:20:03.149 align:start position:0% I have to find it because I don't remember<00:20:00.960> in<00:20:01.200> which<00:20:01.520> package<00:20:02.120> I<00:20:02.240> build<00:20:02.520> it<00:20:02.720> but 00:20:03.149 --> 00:20:03.159 align:start position:0% remember in which package I build it but 00:20:03.159 --> 00:20:09.070 align:start position:0% remember in which package I build it but let<00:20:03.320> me<00:20:04.039> we<00:20:04.120> will<00:20:04.600> SE<00:20:05.600> this<00:20:06.520> later<00:20:07.520> okay<00:20:07.799> let<00:20:08.080> me 00:20:09.070 --> 00:20:09.080 align:start position:0% let me we will SE this later okay let me 00:20:09.080 --> 00:20:11.950 align:start position:0% let me we will SE this later okay let me yeah<00:20:09.440> yeah<00:20:09.919> uh<00:20:10.120> thanks<00:20:11.039> uh<00:20:11.200> this<00:20:11.320> might<00:20:11.559> be 00:20:11.950 --> 00:20:11.960 align:start position:0% yeah yeah uh thanks uh this might be 00:20:11.960 --> 00:20:15.029 align:start position:0% yeah yeah uh thanks uh this might be maybe<00:20:12.240> a<00:20:12.320> silly<00:20:12.679> question<00:20:13.000> but<00:20:13.360> running<00:20:14.320> the 00:20:15.029 --> 00:20:15.039 align:start position:0% maybe a silly question but running the 00:20:15.039 --> 00:20:17.310 align:start position:0% maybe a silly question but running the uh<00:20:15.200> this<00:20:15.440> on<00:20:15.600> the<00:20:15.799> cloud<00:20:16.280> like<00:20:16.440> on<00:20:16.760> ec2 00:20:17.310 --> 00:20:17.320 align:start position:0% uh this on the cloud like on ec2 00:20:17.320 --> 00:20:20.830 align:start position:0% uh this on the cloud like on ec2 instance<00:20:18.080> is<00:20:18.240> this<00:20:19.159> not<00:20:19.400> recommended<00:20:20.280> or 00:20:20.830 --> 00:20:20.840 align:start position:0% instance is this not recommended or 00:20:20.840 --> 00:20:23.149 align:start position:0% instance is this not recommended or running<00:20:21.120> out<00:20:21.360> nothing<00:20:21.760> in<00:20:21.880> the<00:20:22.000> cloud<00:20:23.000> yeah 00:20:23.149 --> 00:20:23.159 align:start position:0% running out nothing in the cloud yeah 00:20:23.159 --> 00:20:25.750 align:start position:0% running out nothing in the cloud yeah like<00:20:23.320> in<00:20:23.480> an<00:20:23.760> E2<00:20:24.280> instance<00:20:24.799> sure<00:20:25.039> it's<00:20:25.320> easier 00:20:25.750 --> 00:20:25.760 align:start position:0% like in an E2 instance sure it's easier 00:20:25.760 --> 00:20:27.870 align:start position:0% like in an E2 instance sure it's easier but<00:20:25.919> it's<00:20:26.039> more<00:20:26.280> expensive<00:20:26.880> as<00:20:27.039> well<00:20:27.440> yeah 00:20:27.870 --> 00:20:27.880 align:start position:0% but it's more expensive as well yeah 00:20:27.880 --> 00:20:32.029 align:start position:0% but it's more expensive as well yeah yeah<00:20:28.280> and<00:20:29.120> and<00:20:29.760> you<00:20:29.919> know<00:20:30.679> the<00:20:31.000> objective<00:20:31.799> of 00:20:32.029 --> 00:20:32.039 align:start position:0% yeah and and you know the objective of 00:20:32.039 --> 00:20:34.110 align:start position:0% yeah and and you know the objective of of<00:20:32.159> the<00:20:32.400> problem<00:20:33.039> of<00:20:33.159> the<00:20:33.320> project<00:20:33.799> the<00:20:33.919> goal 00:20:34.110 --> 00:20:34.120 align:start position:0% of the problem of the project the goal 00:20:34.120 --> 00:20:36.789 align:start position:0% of the problem of the project the goal of<00:20:34.280> the<00:20:34.440> project<00:20:34.720> is<00:20:34.880> that<00:20:35.440> individuals<00:20:36.440> are 00:20:36.789 --> 00:20:36.799 align:start position:0% of the project is that individuals are 00:20:36.799 --> 00:20:40.430 align:start position:0% of the project is that individuals are run<00:20:37.120> notes<00:20:37.880> at<00:20:38.120> home<00:20:38.559> this<00:20:38.760> is<00:20:39.039> the<00:20:39.840> but<00:20:40.280> of 00:20:40.430 --> 00:20:40.440 align:start position:0% run notes at home this is the but of 00:20:40.440 --> 00:20:42.350 align:start position:0% run notes at home this is the but of course<00:20:40.799> uh<00:20:41.000> running<00:20:41.559> in<00:20:41.679> the<00:20:41.840> cloud<00:20:42.159> is 00:20:42.350 --> 00:20:42.360 align:start position:0% course uh running in the cloud is 00:20:42.360 --> 00:20:44.950 align:start position:0% course uh running in the cloud is another<00:20:42.799> option<00:20:43.200> and<00:20:43.720> a<00:20:43.840> lot<00:20:44.000> of<00:20:44.240> people<00:20:44.760> be<00:20:44.840> a 00:20:44.950 --> 00:20:44.960 align:start position:0% another option and a lot of people be a 00:20:44.960 --> 00:20:46.990 align:start position:0% another option and a lot of people be a would<00:20:45.159> be<00:20:45.320> more<00:20:45.520> expensive<00:20:46.120> but<00:20:46.640> at<00:20:46.720> the<00:20:46.840> same 00:20:46.990 --> 00:20:47.000 align:start position:0% would be more expensive but at the same 00:20:47.000 --> 00:20:49.830 align:start position:0% would be more expensive but at the same time<00:20:47.919> you<00:20:48.039> can<00:20:48.240> have<00:20:48.400> it<00:20:48.679> like<00:20:49.120> Auto<00:20:49.520> healing 00:20:49.830 --> 00:20:49.840 align:start position:0% time you can have it like Auto healing 00:20:49.840 --> 00:20:53.149 align:start position:0% time you can have it like Auto healing and<00:20:49.960> things<00:20:50.080> like<00:20:50.240> that<00:20:50.840> okay<00:20:51.840> it's<00:20:52.280> not<00:20:52.520> not 00:20:53.149 --> 00:20:53.159 align:start position:0% and things like that okay it's not not 00:20:53.159 --> 00:20:55.070 align:start position:0% and things like that okay it's not not more<00:20:53.440> expensive<00:20:54.120> and<00:20:54.360> at<00:20:54.480> the<00:20:54.600> end<00:20:54.799> you<00:20:54.919> will 00:20:55.070 --> 00:20:55.080 align:start position:0% more expensive and at the end you will 00:20:55.080 --> 00:20:58.230 align:start position:0% more expensive and at the end you will depend<00:20:55.400> in<00:20:55.640> a<00:20:56.159> in<00:20:56.280> a<00:20:56.480> company<00:20:57.039> and<00:20:57.760> if<00:20:57.919> you<00:20:58.080> want 00:20:58.230 --> 00:20:58.240 align:start position:0% depend in a in a company and if you want 00:20:58.240 --> 00:20:59.669 align:start position:0% depend in a in a company and if you want to 00:20:59.669 --> 00:20:59.679 align:start position:0% to 00:20:59.679 --> 00:21:03.270 align:start position:0% to to<00:21:00.679> for<00:21:00.880> example<00:21:01.159> not<00:21:01.360> depend<00:21:01.720> from<00:21:02.559> five<00:21:02.880> six 00:21:03.270 --> 00:21:03.280 align:start position:0% to for example not depend from five six 00:21:03.280 --> 00:21:05.190 align:start position:0% to for example not depend from five six seven<00:21:03.960> big<00:21:04.200> companies<00:21:04.559> around<00:21:04.799> the<00:21:04.919> world 00:21:05.190 --> 00:21:05.200 align:start position:0% seven big companies around the world 00:21:05.200 --> 00:21:07.750 align:start position:0% seven big companies around the world that<00:21:05.360> could<00:21:05.640> have<00:21:06.000> a<00:21:06.799> big<00:21:07.080> problem<00:21:07.559> at<00:21:07.679> the 00:21:07.750 --> 00:21:07.760 align:start position:0% that could have a big problem at the 00:21:07.760 --> 00:21:10.909 align:start position:0% that could have a big problem at the same<00:21:08.039> time<00:21:08.600> uh<00:21:09.000> I<00:21:09.080> don't<00:21:09.280> know<00:21:09.960> right<00:21:10.159> now<00:21:10.440> but 00:21:10.909 --> 00:21:10.919 align:start position:0% same time uh I don't know right now but 00:21:10.919 --> 00:21:13.470 align:start position:0% same time uh I don't know right now but a<00:21:11.000> few<00:21:11.200> years<00:21:11.440> ago<00:21:11.880> if<00:21:12.600> uh<00:21:12.880> Amazon<00:21:13.279> web 00:21:13.470 --> 00:21:13.480 align:start position:0% a few years ago if uh Amazon web 00:21:13.480 --> 00:21:16.630 align:start position:0% a few years ago if uh Amazon web services<00:21:13.919> have<00:21:14.200> a<00:21:14.559> big<00:21:14.840> strong<00:21:15.520> problem<00:21:16.520> uh 00:21:16.630 --> 00:21:16.640 align:start position:0% services have a big strong problem uh 00:21:16.640 --> 00:21:19.870 align:start position:0% services have a big strong problem uh most<00:21:16.840> of<00:21:17.120> the<00:21:17.960> of<00:21:18.080> the<00:21:18.200> nodes<00:21:18.520> are<00:21:18.679> running<00:21:19.159> in 00:21:19.870 --> 00:21:19.880 align:start position:0% most of the of the nodes are running in 00:21:19.880 --> 00:21:22.669 align:start position:0% most of the of the nodes are running in in<00:21:20.559> the<00:21:21.200> in<00:21:21.360> Amazon<00:21:21.720> in<00:21:21.840> Amazon<00:21:22.120> we<00:21:22.279> services 00:21:22.669 --> 00:21:22.679 align:start position:0% in the in Amazon in Amazon we services 00:21:22.679 --> 00:21:26.470 align:start position:0% in the in Amazon in Amazon we services so<00:21:22.840> at<00:21:22.960> the<00:21:23.080> end<00:21:23.840> you<00:21:24.120> probably<00:21:24.679> would<00:21:24.919> have<00:21:25.240> a 00:21:26.470 --> 00:21:26.480 align:start position:0% so at the end you probably would have a 00:21:26.480 --> 00:21:29.310 align:start position:0% so at the end you probably would have a uh<00:21:27.480> half<00:21:27.720> of<00:21:27.960> the<00:21:28.200> of<00:21:28.320> the<00:21:28.640> validators<00:21:29.080> shut 00:21:29.310 --> 00:21:29.320 align:start position:0% uh half of the of the validators shut 00:21:29.320 --> 00:21:31.430 align:start position:0% uh half of the of the validators shut down<00:21:29.640> because<00:21:30.000> Amazon<00:21:30.360> has<00:21:30.480> a<00:21:30.640> big<00:21:30.840> problem 00:21:31.430 --> 00:21:31.440 align:start position:0% down because Amazon has a big problem 00:21:31.440 --> 00:21:33.149 align:start position:0% down because Amazon has a big problem usually<00:21:31.919> they<00:21:32.039> don't<00:21:32.240> have<00:21:32.360> a<00:21:32.559> big<00:21:32.720> problem<00:21:33.000> of 00:21:33.149 --> 00:21:33.159 align:start position:0% usually they don't have a big problem of 00:21:33.159 --> 00:21:35.630 align:start position:0% usually they don't have a big problem of course<00:21:33.480> but<00:21:34.080> you<00:21:34.200> know<00:21:34.480> the<00:21:34.760> the<00:21:34.880> main<00:21:35.200> purpose 00:21:35.630 --> 00:21:35.640 align:start position:0% course but you know the the main purpose 00:21:35.640 --> 00:21:37.230 align:start position:0% course but you know the the main purpose of<00:21:35.919> of<00:21:36.080> the<00:21:36.200> blockchain<00:21:36.600> is<00:21:36.720> to<00:21:36.840> verify 00:21:37.230 --> 00:21:37.240 align:start position:0% of of the blockchain is to verify 00:21:37.240 --> 00:21:41.029 align:start position:0% of of the blockchain is to verify yourself<00:21:37.799> so<00:21:38.559> it's<00:21:38.799> good<00:21:39.039> to<00:21:39.440> to<00:21:40.120> uh<00:21:40.480> can<00:21:40.760> do 00:21:41.029 --> 00:21:41.039 align:start position:0% yourself so it's good to to uh can do 00:21:41.039 --> 00:21:44.190 align:start position:0% yourself so it's good to to uh can do that<00:21:41.960> at<00:21:42.159> home<00:21:42.480> or<00:21:42.679> or<00:21:42.919> with<00:21:43.159> your<00:21:43.400> device<00:21:44.039> no 00:21:44.190 --> 00:21:44.200 align:start position:0% that at home or or with your device no 00:21:44.200 --> 00:21:52.750 align:start position:0% that at home or or with your device no no<00:21:44.760> I<00:21:44.919> get<00:21:45.000> it<00:21:45.200> thank 00:21:52.750 --> 00:21:52.760 align:start position:0% 00:21:52.760 --> 00:21:56.350 align:start position:0% you<00:21:53.760> hey<00:21:54.279> sorry<00:21:54.799> uh<00:21:54.960> another<00:21:55.440> non<00:21:55.960> another 00:21:56.350 --> 00:21:56.360 align:start position:0% you hey sorry uh another non another 00:21:56.360 --> 00:21:59.510 align:start position:0% you hey sorry uh another non another nonrelated<00:21:57.120> question<00:21:57.840> uh<00:21:58.679> from<00:21:58.919> where<00:21:59.120> I<00:21:59.240> come 00:21:59.510 --> 00:21:59.520 align:start position:0% nonrelated question uh from where I come 00:21:59.520 --> 00:22:01.430 align:start position:0% nonrelated question uh from where I come I<00:21:59.600> come<00:21:59.799> from<00:22:00.000> Latin<00:22:00.320> America<00:22:00.840> where<00:22:01.120> we<00:22:01.279> have 00:22:01.430 --> 00:22:01.440 align:start position:0% I come from Latin America where we have 00:22:01.440 --> 00:22:03.750 align:start position:0% I come from Latin America where we have a<00:22:01.559> lot<00:22:01.720> of<00:22:01.919> problems<00:22:02.240> with<00:22:02.440> electricity<00:22:03.279> and 00:22:03.750 --> 00:22:03.760 align:start position:0% a lot of problems with electricity and 00:22:03.760 --> 00:22:06.950 align:start position:0% a lot of problems with electricity and and<00:22:03.960> public<00:22:04.240> services<00:22:04.799> and<00:22:05.200> sometimes<00:22:05.960> the 00:22:06.950 --> 00:22:06.960 align:start position:0% and public services and sometimes the 00:22:06.960 --> 00:22:08.990 align:start position:0% and public services and sometimes the light<00:22:07.200> goes<00:22:07.440> off<00:22:07.720> like<00:22:07.880> for<00:22:08.000> example<00:22:08.360> Cuba<00:22:08.760> had 00:22:08.990 --> 00:22:09.000 align:start position:0% light goes off like for example Cuba had 00:22:09.000 --> 00:22:10.710 align:start position:0% light goes off like for example Cuba had had<00:22:09.279> for<00:22:09.480> examp<00:22:09.840> one<00:22:10.000> week<00:22:10.240> without 00:22:10.710 --> 00:22:10.720 align:start position:0% had for examp one week without 00:22:10.720 --> 00:22:16.070 align:start position:0% had for examp one week without electricity<00:22:11.720> so<00:22:12.679> uh<00:22:13.679> my<00:22:13.880> question<00:22:14.360> is<00:22:15.039> uh 00:22:16.070 --> 00:22:16.080 align:start position:0% electricity so uh my question is uh 00:22:16.080 --> 00:22:19.070 align:start position:0% electricity so uh my question is uh how<00:22:17.080> how<00:22:17.240> can<00:22:17.400> I<00:22:17.600> be<00:22:17.760> safe<00:22:18.200> that<00:22:18.480> that<00:22:18.679> the<00:22:18.880> for 00:22:19.070 --> 00:22:19.080 align:start position:0% how how can I be safe that that the for 00:22:19.080 --> 00:22:22.110 align:start position:0% how how can I be safe that that the for example<00:22:19.559> that<00:22:19.760> the<00:22:20.600> that<00:22:21.080> if<00:22:21.320> the<00:22:21.440> electricity 00:22:22.110 --> 00:22:22.120 align:start position:0% example that the that if the electricity 00:22:22.120 --> 00:22:26.390 align:start position:0% example that the that if the electricity Falls<00:22:23.120> uh<00:22:23.480> the<00:22:24.039> the<00:22:24.559> the<00:22:24.799> money<00:22:25.480> I<00:22:25.600> have<00:22:25.919> staked 00:22:26.390 --> 00:22:26.400 align:start position:0% Falls uh the the the money I have staked 00:22:26.400 --> 00:22:28.710 align:start position:0% Falls uh the the the money I have staked on<00:22:26.600> the<00:22:26.760> on<00:22:27.400> on<00:22:27.600> this<00:22:27.799> notes<00:22:28.159> are<00:22:28.360> not<00:22:28.559> not 00:22:28.710 --> 00:22:28.720 align:start position:0% on the on on this notes are not not 00:22:28.720 --> 00:22:30.830 align:start position:0% on the on on this notes are not not going<00:22:28.880> to<00:22:29.039> be<00:22:29.640> are<00:22:29.760> not<00:22:29.919> going<00:22:30.080> to<00:22:30.200> be<00:22:30.320> slashed 00:22:30.830 --> 00:22:30.840 align:start position:0% going to be are not going to be slashed 00:22:30.840 --> 00:22:33.230 align:start position:0% going to be are not going to be slashed for<00:22:31.039> example<00:22:31.559> if<00:22:31.799> if<00:22:31.919> electricity<00:22:32.480> Falls<00:22:33.000> if 00:22:33.230 --> 00:22:33.240 align:start position:0% for example if if electricity Falls if 00:22:33.240 --> 00:22:35.710 align:start position:0% for example if if electricity Falls if if<00:22:33.400> I<00:22:33.679> I'm<00:22:33.799> running<00:22:34.279> no<00:22:34.600> on<00:22:34.760> not<00:22:35.000> internet<00:22:35.559> your 00:22:35.710 --> 00:22:35.720 align:start position:0% if I I'm running no on not internet your 00:22:35.720 --> 00:22:39.350 align:start position:0% if I I'm running no on not internet your meaning<00:22:36.360> validators<00:22:37.440> slash<00:22:38.440> yeah<00:22:38.919> no 00:22:39.350 --> 00:22:39.360 align:start position:0% meaning validators slash yeah no 00:22:39.360 --> 00:22:41.630 align:start position:0% meaning validators slash yeah no validator<00:22:39.880> are<00:22:40.039> not<00:22:40.320> slash<00:22:40.799> because<00:22:41.080> of<00:22:41.240> a<00:22:41.559> of 00:22:41.630 --> 00:22:41.640 align:start position:0% validator are not slash because of a of 00:22:41.640 --> 00:22:45.630 align:start position:0% validator are not slash because of a of a<00:22:41.960> blackout<00:22:42.960> you<00:22:43.200> just<00:22:43.480> are<00:22:44.240> penalized<00:22:45.240> uh<00:22:45.520> if 00:22:45.630 --> 00:22:45.640 align:start position:0% a blackout you just are penalized uh if 00:22:45.640 --> 00:22:47.870 align:start position:0% a blackout you just are penalized uh if you<00:22:45.760> are<00:22:45.880> offline<00:22:46.279> you<00:22:46.400> are<00:22:46.559> penalized<00:22:47.200> but<00:22:47.600> uh 00:22:47.870 --> 00:22:47.880 align:start position:0% you are offline you are penalized but uh 00:22:47.880 --> 00:22:50.909 align:start position:0% you are offline you are penalized but uh you<00:22:48.039> never<00:22:48.480> get<00:22:48.640> this<00:22:49.039> get<00:22:49.279> lash<00:22:49.880> yeah<00:22:50.559> okay 00:22:50.909 --> 00:22:50.919 align:start position:0% you never get this get lash yeah okay 00:22:50.919 --> 00:22:52.310 align:start position:0% you never get this get lash yeah okay yeah<00:22:51.080> I<00:22:51.159> think<00:22:51.320> I<00:22:51.440> used<00:22:51.640> the<00:22:51.799> wrong<00:22:52.000> term<00:22:52.200> it 00:22:52.310 --> 00:22:52.320 align:start position:0% yeah I think I used the wrong term it 00:22:52.320 --> 00:22:53.350 align:start position:0% yeah I think I used the wrong term it was 00:22:53.350 --> 00:22:53.360 align:start position:0% was 00:22:53.360 --> 00:22:56.269 align:start position:0% was penalized<00:22:54.360> if<00:22:54.640> if<00:22:54.760> I'm<00:22:55.000> offline<00:22:55.559> then<00:22:55.799> I<00:22:55.880> am<00:22:56.159> I 00:22:56.269 --> 00:22:56.279 align:start position:0% penalized if if I'm offline then I am I 00:22:56.279 --> 00:22:58.990 align:start position:0% penalized if if I'm offline then I am I going<00:22:56.440> to<00:22:56.559> get<00:22:56.720> penalized<00:22:57.279> right<00:22:57.799> y<00:22:58.279> yeah<00:22:58.640> yeah 00:22:58.990 --> 00:22:59.000 align:start position:0% going to get penalized right y yeah yeah 00:22:59.000 --> 00:23:02.070 align:start position:0% going to get penalized right y yeah yeah but<00:22:59.320> you<00:22:59.440> can<00:22:59.640> run<00:22:59.919> a<00:23:00.840> a<00:23:01.120> device<00:23:01.480> for<00:23:01.720> keeping 00:23:02.070 --> 00:23:02.080 align:start position:0% but you can run a a device for keeping 00:23:02.080 --> 00:23:05.590 align:start position:0% but you can run a a device for keeping the<00:23:02.320> the<00:23:02.799> electricity<00:23:03.799> at<00:23:03.960> least<00:23:04.640> some<00:23:04.960> hours 00:23:05.590 --> 00:23:05.600 align:start position:0% the the electricity at least some hours 00:23:05.600 --> 00:23:07.510 align:start position:0% the the electricity at least some hours because<00:23:06.120> you<00:23:06.240> know<00:23:06.480> you<00:23:06.559> know<00:23:06.799> this<00:23:06.919> is<00:23:07.279> uh 00:23:07.510 --> 00:23:07.520 align:start position:0% because you know you know this is uh 00:23:07.520 --> 00:23:11.029 align:start position:0% because you know you know this is uh very<00:23:07.720> low<00:23:08.039> power<00:23:08.760> so<00:23:09.159> you<00:23:09.279> would<00:23:09.480> need<00:23:10.039> maybe 00:23:11.029 --> 00:23:11.039 align:start position:0% very low power so you would need maybe 00:23:11.039 --> 00:23:15.789 align:start position:0% very low power so you would need maybe with<00:23:11.360> small<00:23:11.679> side<00:23:12.400> yeah<00:23:13.400> an<00:23:13.720> UPS<00:23:14.720> yes<00:23:15.559> and<00:23:15.679> for 00:23:15.789 --> 00:23:15.799 align:start position:0% with small side yeah an UPS yes and for 00:23:15.799 --> 00:23:18.630 align:start position:0% with small side yeah an UPS yes and for the<00:23:16.279> internet<00:23:17.279> that's<00:23:17.480> the<00:23:17.679> problem<00:23:18.279> okay<00:23:18.480> if 00:23:18.630 --> 00:23:18.640 align:start position:0% the internet that's the problem okay if 00:23:18.640 --> 00:23:22.230 align:start position:0% the internet that's the problem okay if you<00:23:18.880> have<00:23:19.600> another<00:23:20.080> source<00:23:20.400> of<00:23:20.600> Internet<00:23:21.159> is<00:23:22.159> I 00:23:22.230 --> 00:23:22.240 align:start position:0% you have another source of Internet is I 00:23:22.240 --> 00:23:22.870 align:start position:0% you have another source of Internet is I don't 00:23:22.870 --> 00:23:22.880 align:start position:0% don't 00:23:22.880 --> 00:23:27.070 align:start position:0% don't know<00:23:23.880> that's<00:23:24.320> so<00:23:24.559> yeah<00:23:24.720> that's<00:23:24.880> an<00:23:25.799> yeah<00:23:26.360> these 00:23:27.070 --> 00:23:27.080 align:start position:0% know that's so yeah that's an yeah these 00:23:27.080 --> 00:23:28.990 align:start position:0% know that's so yeah that's an yeah these These<00:23:27.200> are<00:23:27.400> problems<00:23:27.799> that<00:23:28.000> are<00:23:28.679> hardly 00:23:28.990 --> 00:23:29.000 align:start position:0% These are problems that are hardly 00:23:29.000 --> 00:23:32.630 align:start position:0% These are problems that are hardly solvable<00:23:29.919> because<00:23:30.520> you<00:23:30.640> know<00:23:31.039> the<00:23:31.960> it's 00:23:32.630 --> 00:23:32.640 align:start position:0% solvable because you know the it's 00:23:32.640 --> 00:23:36.070 align:start position:0% solvable because you know the it's infrastructure<00:23:33.640> internet<00:23:34.520> uh 00:23:36.070 --> 00:23:36.080 align:start position:0% infrastructure internet uh 00:23:36.080 --> 00:23:40.909 align:start position:0% infrastructure internet uh Power<00:23:37.080> with<00:23:37.200> an<00:23:37.360> UPS<00:23:37.960> I<00:23:38.039> can<00:23:38.200> room<00:23:38.880> my<00:23:39.679> uh<00:23:40.400> my<00:23:40.760> I 00:23:40.909 --> 00:23:40.919 align:start position:0% Power with an UPS I can room my uh my I 00:23:40.919 --> 00:23:43.070 align:start position:0% Power with an UPS I can room my uh my I have<00:23:41.120> four<00:23:41.360> or<00:23:41.559> five 00:23:43.070 --> 00:23:43.080 align:start position:0% have four or five 00:23:43.080 --> 00:23:45.630 align:start position:0% have four or five devices<00:23:44.080> I<00:23:44.200> have<00:23:44.480> four<00:23:44.600> or<00:23:44.760> five<00:23:44.960> devices<00:23:45.320> like 00:23:45.630 --> 00:23:45.640 align:start position:0% devices I have four or five devices like 00:23:45.640 --> 00:23:47.950 align:start position:0% devices I have four or five devices like they<00:23:45.880> this<00:23:46.039> at<00:23:46.240> home<00:23:46.799> and<00:23:47.000> with<00:23:47.279> my<00:23:47.440> I<00:23:47.600> have 00:23:47.950 --> 00:23:47.960 align:start position:0% they this at home and with my I have 00:23:47.960 --> 00:23:50.830 align:start position:0% they this at home and with my I have very<00:23:48.159> small<00:23:48.480> ups<00:23:49.440> and<00:23:49.600> with<00:23:49.760> the<00:23:49.880> small<00:23:50.120> ups 00:23:50.830 --> 00:23:50.840 align:start position:0% very small ups and with the small ups 00:23:50.840 --> 00:23:54.230 align:start position:0% very small ups and with the small ups and<00:23:51.600> plus<00:23:52.039> or<00:23:52.279> my<00:23:52.480> home<00:23:52.840> router<00:23:53.840> uh<00:23:53.960> you<00:23:54.080> can 00:23:54.230 --> 00:23:54.240 align:start position:0% and plus or my home router uh you can 00:23:54.240 --> 00:23:58.070 align:start position:0% and plus or my home router uh you can run<00:23:54.720> it<00:23:55.240> uh<00:23:55.559> for<00:23:55.960> I<00:23:56.120> think<00:23:56.559> six<00:23:56.840> or<00:23:57.000> seven<00:23:57.279> hours 00:23:58.070 --> 00:23:58.080 align:start position:0% run it uh for I think six or seven hours 00:23:58.080 --> 00:24:00.990 align:start position:0% run it uh for I think six or seven hours yeah<00:23:58.279> so<00:23:58.559> right<00:23:59.240> but<00:23:59.799> uh<00:23:59.960> of<00:24:00.120> course<00:24:00.440> if<00:24:00.880> I 00:24:00.990 --> 00:24:01.000 align:start position:0% yeah so right but uh of course if I 00:24:01.000 --> 00:24:03.470 align:start position:0% yeah so right but uh of course if I don't<00:24:01.240> have<00:24:01.520> also<00:24:02.120> connection<00:24:02.679> internet 00:24:03.470 --> 00:24:03.480 align:start position:0% don't have also connection internet 00:24:03.480 --> 00:24:07.230 align:start position:0% don't have also connection internet connection<00:24:04.480> I<00:24:04.640> get<00:24:05.600> also<00:24:06.279> so<00:24:06.480> the<00:24:06.559> same<00:24:06.799> time 00:24:07.230 --> 00:24:07.240 align:start position:0% connection I get also so the same time 00:24:07.240 --> 00:24:09.310 align:start position:0% connection I get also so the same time so<00:24:07.559> it's<00:24:07.760> not<00:24:08.000> safe<00:24:08.279> for<00:24:08.480> example<00:24:08.760> for<00:24:08.919> a<00:24:09.039> Black 00:24:09.310 --> 00:24:09.320 align:start position:0% so it's not safe for example for a Black 00:24:09.320 --> 00:24:12.029 align:start position:0% so it's not safe for example for a Black Swan<00:24:09.600> event<00:24:10.039> like<00:24:10.480> uh<00:24:10.679> Cuba<00:24:11.039> having<00:24:11.640> one<00:24:11.840> week 00:24:12.029 --> 00:24:12.039 align:start position:0% Swan event like uh Cuba having one week 00:24:12.039 --> 00:24:13.830 align:start position:0% Swan event like uh Cuba having one week without 00:24:13.830 --> 00:24:13.840 align:start position:0% without 00:24:13.840 --> 00:24:20.230 align:start position:0% without electricity<00:24:14.840> yeah<00:24:15.080> thank 00:24:20.230 --> 00:24:20.240 align:start position:0% 00:24:20.240 --> 00:24:26.190 align:start position:0% you<00:24:21.679> stlink<00:24:22.679> yeah<00:24:23.520> yeah<00:24:23.840> but<00:24:24.440> but<00:24:25.440> over<00:24:26.039> at 00:24:26.190 --> 00:24:26.200 align:start position:0% you stlink yeah yeah but but over at 00:24:26.200 --> 00:24:28.909 align:start position:0% you stlink yeah yeah but but over at that<00:24:26.399> point<00:24:27.399> more 00:24:28.909 --> 00:24:28.919 align:start position:0% that point more 00:24:28.919 --> 00:24:31.710 align:start position:0% that point more yeah<00:24:29.720> what<00:24:29.880> what's<00:24:30.039> the<00:24:30.240> cost<00:24:30.520> of<00:24:30.799> Starling<00:24:31.600> I 00:24:31.710 --> 00:24:31.720 align:start position:0% yeah what what's the cost of Starling I 00:24:31.720 --> 00:24:38.870 align:start position:0% yeah what what's the cost of Starling I don't<00:24:31.880> I<00:24:31.919> don't<00:24:32.080> know<00:24:32.679> I'm<00:24:32.840> just 00:24:38.870 --> 00:24:38.880 align:start position:0% 00:24:38.880 --> 00:24:40.750 align:start position:0% asking<00:24:39.880> yeah<00:24:40.080> yeah 00:24:40.750 --> 00:24:40.760 align:start position:0% asking yeah yeah 00:24:40.760 --> 00:24:46.149 align:start position:0% asking yeah yeah yeah<00:24:41.760> in<00:24:41.960> Spain<00:24:42.279> is<00:24:42.559> $100<00:24:43.480> per 00:24:46.149 --> 00:24:46.159 align:start position:0% 00:24:46.159 --> 00:24:50.190 align:start position:0% month<00:24:47.159> yeah<00:24:47.880> the<00:24:48.240> the<00:24:48.640> monthly<00:24:49.640> monthly<00:24:49.960> cost 00:24:50.190 --> 00:24:50.200 align:start position:0% month yeah the the monthly monthly cost 00:24:50.200 --> 00:24:54.269 align:start position:0% month yeah the the monthly monthly cost in<00:24:50.399> Spain<00:24:50.679> for<00:24:50.880> sink<00:24:51.360> is<00:24:51.520> $100<00:24:52.520> per<00:24:52.760> month<00:24:53.760> 100 00:24:54.269 --> 00:24:54.279 align:start position:0% in Spain for sink is $100 per month 100 00:24:54.279 --> 00:24:55.630 align:start position:0% in Spain for sink is $100 per month 100 per<00:24:54.440> month<00:24:54.880> so 00:24:55.630 --> 00:24:55.640 align:start position:0% per month so 00:24:55.640 --> 00:25:05.950 align:start position:0% per month so it's<00:24:56.640> but<00:24:56.960> also<00:24:57.240> you<00:24:57.600> need<00:24:57.840> a<00:24:58.000> bigger 00:25:05.950 --> 00:25:05.960 align:start position:0% 00:25:05.960 --> 00:25:08.470 align:start position:0% EPS 00:25:08.470 --> 00:25:08.480 align:start position:0% EPS 00:25:08.480 --> 00:25:12.430 align:start position:0% EPS escalating<00:25:09.480> we<00:25:09.640> started<00:25:09.960> on 00:25:12.430 --> 00:25:12.440 align:start position:0% 00:25:12.440 --> 00:25:15.389 align:start position:0% $150<00:25:13.440> something<00:25:13.720> like 00:25:15.389 --> 00:25:15.399 align:start position:0% $150 something like 00:25:15.399 --> 00:25:26.909 align:start position:0% $150 something like $2,000<00:25:16.399> yeah's<00:25:16.640> go<00:25:16.760> to<00:25:16.880> the 00:25:26.909 --> 00:25:26.919 align:start position:0% 00:25:26.919 --> 00:25:31.029 align:start position:0% cloud<00:25:27.919> sorry<00:25:28.559> so<00:25:29.080> withing<00:25:30.080> yeah<00:25:30.640> you<00:25:30.760> have<00:25:30.880> to 00:25:31.029 --> 00:25:31.039 align:start position:0% cloud sorry so withing yeah you have to 00:25:31.039 --> 00:25:35.510 align:start position:0% cloud sorry so withing yeah you have to make<00:25:31.159> a<00:25:31.760> minimum<00:25:32.200> of<00:25:32.679> 32<00:25:33.679> well<00:25:34.200> uh<00:25:34.399> actually<00:25:35.200> uh 00:25:35.510 --> 00:25:35.520 align:start position:0% make a minimum of 32 well uh actually uh 00:25:35.520 --> 00:25:38.870 align:start position:0% make a minimum of 32 well uh actually uh this<00:25:35.799> past<00:25:36.080> week<00:25:36.799> uh<00:25:37.000> we<00:25:37.120> are<00:25:37.279> staking<00:25:37.960> with<00:25:38.720> uh 00:25:38.870 --> 00:25:38.880 align:start position:0% this past week uh we are staking with uh 00:25:38.880 --> 00:25:44.269 align:start position:0% this past week uh we are staking with uh one<00:25:39.240> to<00:25:39.720> 5<00:25:40.120> f<00:25:40.679> with<00:25:41.279> uh<00:25:41.679> the<00:25:41.880> CSM<00:25:42.880> uh<00:25:43.120> from<00:25:43.360> Lio 00:25:44.269 --> 00:25:44.279 align:start position:0% one to 5 f with uh the CSM uh from Lio 00:25:44.279 --> 00:25:46.190 align:start position:0% one to 5 f with uh the CSM uh from Lio that<00:25:44.520> they<00:25:44.760> released<00:25:45.520> I 00:25:46.190 --> 00:25:46.200 align:start position:0% that they released I 00:25:46.200 --> 00:25:49.789 align:start position:0% that they released I think<00:25:47.200> two<00:25:47.600> or<00:25:47.919> or<00:25:48.320> three<00:25:48.559> weeks<00:25:48.880> ago<00:25:49.520> and<00:25:49.679> it 00:25:49.789 --> 00:25:49.799 align:start position:0% think two or or three weeks ago and it 00:25:49.799 --> 00:25:53.230 align:start position:0% think two or or three weeks ago and it was<00:25:50.200> great<00:25:51.200> uh<00:25:51.399> we<00:25:51.679> didn't<00:25:51.960> release<00:25:52.720> this<00:25:53.039> this 00:25:53.230 --> 00:25:53.240 align:start position:0% was great uh we didn't release this this 00:25:53.240 --> 00:25:55.070 align:start position:0% was great uh we didn't release this this configuration<00:25:53.919> yet<00:25:54.159> because<00:25:54.399> we<00:25:54.520> are<00:25:54.679> testing 00:25:55.070 --> 00:25:55.080 align:start position:0% configuration yet because we are testing 00:25:55.080 --> 00:25:58.990 align:start position:0% configuration yet because we are testing in<00:25:55.480> in<00:25:56.120> we<00:25:56.200> are<00:25:56.720> sticking<00:25:57.399> in<00:25:57.559> main<00:25:57.880> net 00:25:58.990 --> 00:25:59.000 align:start position:0% in in we are sticking in main net 00:25:59.000 --> 00:26:02.590 align:start position:0% in in we are sticking in main net uh<00:25:59.919> I<00:26:00.039> think<00:26:00.279> on<00:26:00.480> this<00:26:00.679> device<00:26:01.640> and<00:26:01.799> it's<00:26:02.039> going 00:26:02.590 --> 00:26:02.600 align:start position:0% uh I think on this device and it's going 00:26:02.600 --> 00:26:07.070 align:start position:0% uh I think on this device and it's going quite<00:26:02.799> well<00:26:03.320> but<00:26:03.600> yeah<00:26:04.159> uh<00:26:04.440> you<00:26:04.640> can<00:26:05.480> use<00:26:06.200> uh 00:26:07.070 --> 00:26:07.080 align:start position:0% quite well but yeah uh you can use uh 00:26:07.080 --> 00:26:09.630 align:start position:0% quite well but yeah uh you can use uh Lio<00:26:08.080> uh<00:26:08.399> we<00:26:08.559> are<00:26:08.679> looking<00:26:09.000> into<00:26:09.399> other 00:26:09.630 --> 00:26:09.640 align:start position:0% Lio uh we are looking into other 00:26:09.640 --> 00:26:12.909 align:start position:0% Lio uh we are looking into other solutions<00:26:10.080> to<00:26:10.279> lower<00:26:10.720> this<00:26:11.039> this<00:26:11.200> barrier<00:26:11.960> yes 00:26:12.909 --> 00:26:12.919 align:start position:0% solutions to lower this this barrier yes 00:26:12.919 --> 00:26:16.789 align:start position:0% solutions to lower this this barrier yes uh<00:26:13.120> we<00:26:13.320> have<00:26:13.559> validators<00:26:14.399> with<00:26:15.120> the<00:26:15.799> vanila 00:26:16.789 --> 00:26:16.799 align:start position:0% uh we have validators with the vanila 00:26:16.799 --> 00:26:19.350 align:start position:0% uh we have validators with the vanila contract<00:26:17.360> with<00:26:17.679> 32<00:26:18.399> e 00:26:19.350 --> 00:26:19.360 align:start position:0% contract with 32 e 00:26:19.360 --> 00:26:22.190 align:start position:0% contract with 32 e but<00:26:20.360> we<00:26:20.480> know<00:26:20.720> every<00:26:21.000> everyone<00:26:21.600> can<00:26:22.000> can 00:26:22.190 --> 00:26:22.200 align:start position:0% but we know every everyone can can 00:26:22.200 --> 00:26:27.230 align:start position:0% but we know every everyone can can validate<00:26:22.720> with<00:26:23.200> uh<00:26:24.000> uh<00:26:25.000> uh<00:26:25.399> 32<00:26:26.399> is<00:26:26.720> is<00:26:27.000> very 00:26:27.230 --> 00:26:27.240 align:start position:0% validate with uh uh uh 32 is is very 00:26:27.240 --> 00:26:29.669 align:start position:0% validate with uh uh uh 32 is is very expensive<00:26:28.039> so<00:26:28.440> yeah<00:26:28.679> we<00:26:28.840> we<00:26:28.919> are<00:26:29.039> looking<00:26:29.320> into 00:26:29.669 --> 00:26:29.679 align:start position:0% expensive so yeah we we are looking into 00:26:29.679 --> 00:26:32.510 align:start position:0% expensive so yeah we we are looking into into<00:26:29.919> Alternatives<00:26:30.720> yes<00:26:31.360> this<00:26:31.480> is<00:26:31.679> a<00:26:32.039> priority 00:26:32.510 --> 00:26:32.520 align:start position:0% into Alternatives yes this is a priority 00:26:32.520 --> 00:26:33.230 align:start position:0% into Alternatives yes this is a priority for 00:26:33.230 --> 00:26:33.240 align:start position:0% for 00:26:33.240 --> 00:26:36.950 align:start position:0% for us<00:26:34.240> yes<00:26:34.520> uh<00:26:34.720> 32<00:26:35.520> right<00:26:35.640> now<00:26:35.919> is<00:26:36.399> a<00:26:36.559> good<00:26:36.720> amount 00:26:36.950 --> 00:26:36.960 align:start position:0% us yes uh 32 right now is a good amount 00:26:36.960 --> 00:26:39.590 align:start position:0% us yes uh 32 right now is a good amount of<00:26:37.159> money<00:26:38.120> if<00:26:38.200> you<00:26:38.320> want<00:26:38.480> to<00:26:38.600> start<00:26:38.880> to<00:26:39.120> to 00:26:39.590 --> 00:26:39.600 align:start position:0% of money if you want to start to to 00:26:39.600 --> 00:26:43.870 align:start position:0% of money if you want to start to to rating<00:26:40.600> like<00:26:41.039> vital<00:26:41.600> said<00:26:41.960> yesterday<00:26:42.679> is<00:26:43.679> much 00:26:43.870 --> 00:26:43.880 align:start position:0% rating like vital said yesterday is much 00:26:43.880 --> 00:26:46.789 align:start position:0% rating like vital said yesterday is much more<00:26:44.120> than<00:26:44.679> two<00:26:44.880> or<00:26:45.039> three<00:26:45.240> weeks<00:26:45.520> ago<00:26:46.159> so<00:26:46.679> the 00:26:46.789 --> 00:26:46.799 align:start position:0% more than two or three weeks ago so the 00:26:46.799 --> 00:26:49.789 align:start position:0% more than two or three weeks ago so the the<00:26:46.919> barrier<00:26:47.440> is<00:26:47.600> increasing<00:26:48.520> but<00:26:49.159> like<00:26:49.480> dieo 00:26:49.789 --> 00:26:49.799 align:start position:0% the barrier is increasing but like dieo 00:26:49.799 --> 00:26:53.110 align:start position:0% the barrier is increasing but like dieo said<00:26:50.039> with<00:26:50.399> some<00:26:51.320> like<00:26:51.520> Lio<00:26:52.440> Solutions<00:26:52.919> you 00:26:53.110 --> 00:26:53.120 align:start position:0% said with some like Lio Solutions you 00:26:53.120 --> 00:26:59.870 align:start position:0% said with some like Lio Solutions you can<00:26:53.600> put<00:26:53.880> start<00:26:54.200> with<00:26:54.520> one<00:26:55.320> 1.5<00:26:56.320> or<00:26:56.520> 1<00:26:57.320> 1.5<00:26:58.520> 5<00:26:59.240> uh 00:26:59.870 --> 00:26:59.880 align:start position:0% can put start with one 1.5 or 1 1.5 5 uh 00:26:59.880 --> 00:27:02.230 align:start position:0% can put start with one 1.5 or 1 1.5 5 uh but<00:27:00.200> I<00:27:00.360> think<00:27:00.559> it<00:27:00.720> will<00:27:00.880> be<00:27:01.320> this<00:27:01.399> is<00:27:01.520> for<00:27:01.840> Early 00:27:02.230 --> 00:27:02.240 align:start position:0% but I think it will be this is for Early 00:27:02.240 --> 00:27:06.190 align:start position:0% but I think it will be this is for Early Access<00:27:02.640> I<00:27:02.720> think<00:27:02.919> it<00:27:03.080> will<00:27:03.279> be<00:27:04.120> 2.3<00:27:04.880> or<00:27:05.080> 2.5<00:27:05.960> I 00:27:06.190 --> 00:27:06.200 align:start position:0% Access I think it will be 2.3 or 2.5 I 00:27:06.200 --> 00:27:09.789 align:start position:0% Access I think it will be 2.3 or 2.5 I don't<00:27:06.399> remember<00:27:06.880> that's<00:27:07.880> it's<00:27:08.080> less<00:27:08.399> but<00:27:08.880> uh<00:27:09.559> I 00:27:09.789 --> 00:27:09.799 align:start position:0% don't remember that's it's less but uh I 00:27:09.799 --> 00:27:11.710 align:start position:0% don't remember that's it's less but uh I they<00:27:09.960> think<00:27:10.399> at<00:27:10.520> the<00:27:10.640> L<00:27:10.840> it's<00:27:11.039> going<00:27:11.200> to<00:27:11.559> if 00:27:11.710 --> 00:27:11.720 align:start position:0% they think at the L it's going to if 00:27:11.720 --> 00:27:14.389 align:start position:0% they think at the L it's going to if you're<00:27:12.000> if<00:27:12.080> you're<00:27:12.480> soloer<00:27:13.480> already<00:27:13.840> you<00:27:13.960> can 00:27:14.389 --> 00:27:14.399 align:start position:0% you're if you're soloer already you can 00:27:14.399 --> 00:27:19.269 align:start position:0% you're if you're soloer already you can up<00:27:15.039> up<00:27:15.279> to<00:27:16.039> to<00:27:16.240> the<00:27:16.360> 12<00:27:16.559> 125<00:27:17.559> staking<00:27:18.000> now<00:27:18.919> yeah 00:27:19.269 --> 00:27:19.279 align:start position:0% up up to to the 12 125 staking now yeah 00:27:19.279 --> 00:27:20.430 align:start position:0% up up to to the 12 125 staking now yeah with<00:27:19.559> with 00:27:20.430 --> 00:27:20.440 align:start position:0% with with 00:27:20.440 --> 00:27:25.029 align:start position:0% with with Lio<00:27:21.440> Lio<00:27:21.960> Lio<00:27:22.520> community<00:27:23.399> community<00:27:24.159> staking 00:27:25.029 --> 00:27:25.039 align:start position:0% Lio Lio Lio community community staking 00:27:25.039 --> 00:27:29.230 align:start position:0% Lio Lio Lio community community staking module<00:27:26.039> you<00:27:26.159> can<00:27:26.399> search<00:27:26.720> for<00:27:26.960> it<00:27:27.760> it's<00:27:28.480> uh 00:27:29.230 --> 00:27:29.240 align:start position:0% module you can search for it it's uh 00:27:29.240 --> 00:27:31.750 align:start position:0% module you can search for it it's uh it's<00:27:29.520> easy<00:27:29.799> to<00:27:29.960> set<00:27:30.200> up<00:27:30.440> if<00:27:30.600> you<00:27:30.799> have<00:27:31.240> uh<00:27:31.440> some 00:27:31.750 --> 00:27:31.760 align:start position:0% it's easy to set up if you have uh some 00:27:31.760 --> 00:27:33.149 align:start position:0% it's easy to set up if you have uh some experience 00:27:33.149 --> 00:27:33.159 align:start position:0% experience 00:27:33.159 --> 00:27:36.590 align:start position:0% experience validating<00:27:34.320> uh<00:27:35.320> it's<00:27:35.760> uh<00:27:35.919> pretty<00:27:36.200> much<00:27:36.440> the 00:27:36.590 --> 00:27:36.600 align:start position:0% validating uh it's uh pretty much the 00:27:36.600 --> 00:27:38.549 align:start position:0% validating uh it's uh pretty much the same<00:27:36.919> but<00:27:37.120> you<00:27:37.320> have<00:27:37.480> to<00:27:37.720> deposit<00:27:38.200> on<00:27:38.399> the 00:27:38.549 --> 00:27:38.559 align:start position:0% same but you have to deposit on the 00:27:38.559 --> 00:27:40.909 align:start position:0% same but you have to deposit on the lightos<00:27:39.080> contract<00:27:39.559> instead<00:27:39.919> of<00:27:40.159> the<00:27:40.760> uh 00:27:40.909 --> 00:27:40.919 align:start position:0% lightos contract instead of the uh 00:27:40.919 --> 00:27:43.909 align:start position:0% lightos contract instead of the uh ethereum<00:27:41.480> Foundation<00:27:42.039> one<00:27:43.039> and<00:27:43.399> the<00:27:43.600> other 00:27:43.909 --> 00:27:43.919 align:start position:0% ethereum Foundation one and the other 00:27:43.919 --> 00:27:47.110 align:start position:0% ethereum Foundation one and the other thing<00:27:44.880> are<00:27:45.279> two<00:27:45.519> or<00:27:45.760> three<00:27:46.320> uh<00:27:46.480> configuration 00:27:47.110 --> 00:27:47.120 align:start position:0% thing are two or three uh configuration 00:27:47.120 --> 00:27:50.149 align:start position:0% thing are two or three uh configuration parameters<00:27:47.760> but<00:27:48.240> it's<00:27:48.600> it's<00:27:48.840> easy<00:27:49.440> it's<00:27:49.640> easy 00:27:50.149 --> 00:27:50.159 align:start position:0% parameters but it's it's easy it's easy 00:27:50.159 --> 00:27:53.230 align:start position:0% parameters but it's it's easy it's easy the<00:27:50.279> keys<00:27:50.519> are<00:27:50.760> the<00:27:50.960> same<00:27:51.600> uh<00:27:51.799> you<00:27:52.600> you<00:27:53.080> the 00:27:53.230 --> 00:27:53.240 align:start position:0% the keys are the same uh you you the 00:27:53.240 --> 00:27:56.590 align:start position:0% the keys are the same uh you you the kids<00:27:53.960> uh<00:27:54.440> the<00:27:54.600> same<00:27:55.039> and<00:27:55.559> and<00:27:55.799> yes<00:27:56.159> it's<00:27:56.399> it's 00:27:56.590 --> 00:27:56.600 align:start position:0% kids uh the same and and yes it's it's 00:27:56.600 --> 00:27:59.549 align:start position:0% kids uh the same and and yes it's it's easy<00:27:57.080> and<00:27:57.200> you<00:27:57.320> have<00:27:57.480> a<00:27:57.640> panel<00:27:58.240> with<00:27:58.399> all<00:27:58.640> the 00:27:59.549 --> 00:27:59.559 align:start position:0% easy and you have a panel with all the 00:27:59.559 --> 00:28:02.870 align:start position:0% easy and you have a panel with all the uh<00:27:59.840> data<00:28:00.399> and<00:28:00.640> keys<00:28:01.159> and<00:28:01.600> and<00:28:01.960> uh<00:28:02.200> R<00:28:02.480> worlds 00:28:02.870 --> 00:28:02.880 align:start position:0% uh data and keys and and uh R worlds 00:28:02.880 --> 00:28:05.430 align:start position:0% uh data and keys and and uh R worlds it's<00:28:03.159> it's 00:28:05.430 --> 00:28:05.440 align:start position:0% it's it's 00:28:05.440 --> 00:28:10.149 align:start position:0% it's it's nice<00:28:06.440> okay<00:28:07.240> U<00:28:08.039> and<00:28:08.159> meanwhile<00:28:08.640> I<00:28:08.799> was<00:28:09.679> uh 00:28:10.149 --> 00:28:10.159 align:start position:0% nice okay U and meanwhile I was uh 00:28:10.159 --> 00:28:12.789 align:start position:0% nice okay U and meanwhile I was uh writing<00:28:10.600> the<00:28:10.760> SD<00:28:11.039> card<00:28:11.440> with<00:28:11.600> our<00:28:12.120> image<00:28:12.600> with 00:28:12.789 --> 00:28:12.799 align:start position:0% writing the SD card with our image with 00:28:12.799 --> 00:28:14.909 align:start position:0% writing the SD card with our image with an<00:28:13.039> RBM<00:28:13.559> image<00:28:13.919> and<00:28:14.360> we<00:28:14.480> are<00:28:14.600> going<00:28:14.760> to 00:28:14.909 --> 00:28:14.919 align:start position:0% an RBM image and we are going to 00:28:14.919 --> 00:28:17.630 align:start position:0% an RBM image and we are going to transform<00:28:15.440> this<00:28:15.720> Arman<00:28:16.240> image<00:28:16.480> in<00:28:16.640> our<00:28:16.840> image 00:28:17.630 --> 00:28:17.640 align:start position:0% transform this Arman image in our image 00:28:17.640 --> 00:28:20.669 align:start position:0% transform this Arman image in our image with<00:28:17.840> running<00:28:18.240> our<00:28:18.679> init<00:28:19.080> script<00:28:19.760> live<00:28:20.159> here 00:28:20.669 --> 00:28:20.679 align:start position:0% with running our init script live here 00:28:20.679 --> 00:28:22.909 align:start position:0% with running our init script live here we<00:28:20.799> hope<00:28:21.120> is<00:28:21.360> everything<00:28:21.600> is<00:28:21.720> going<00:28:21.960> to<00:28:22.360> to<00:28:22.640> go 00:28:22.909 --> 00:28:22.919 align:start position:0% we hope is everything is going to to go 00:28:22.919 --> 00:28:26.230 align:start position:0% we hope is everything is going to to go well<00:28:23.600> at<00:28:23.720> the<00:28:23.799> end<00:28:24.120> you<00:28:24.240> could<00:28:24.799> use<00:28:25.799> a<00:28:25.919> lot<00:28:26.080> of 00:28:26.230 --> 00:28:26.240 align:start position:0% well at the end you could use a lot of 00:28:26.240 --> 00:28:29.110 align:start position:0% well at the end you could use a lot of different<00:28:26.519> tools<00:28:26.799> to<00:28:27.000> write<00:28:27.360> and<00:28:28.000> uh<00:28:28.559> image<00:28:28.919> on 00:28:29.110 --> 00:28:29.120 align:start position:0% different tools to write and uh image on 00:28:29.120 --> 00:28:32.389 align:start position:0% different tools to write and uh image on SD<00:28:29.399> card<00:28:29.960> here<00:28:30.440> the<00:28:30.960> the<00:28:31.120> easy<00:28:31.519> way<00:28:31.720> in<00:28:32.000> Linux 00:28:32.389 --> 00:28:32.399 align:start position:0% SD card here the the easy way in Linux 00:28:32.399 --> 00:28:34.990 align:start position:0% SD card here the the easy way in Linux in<00:28:32.559> my<00:28:32.720> opinion<00:28:33.039> is<00:28:33.240> using<00:28:33.640> DD<00:28:34.080> but<00:28:34.720> there's 00:28:34.990 --> 00:28:35.000 align:start position:0% in my opinion is using DD but there's 00:28:35.000 --> 00:28:39.630 align:start position:0% in my opinion is using DD but there's some<00:28:35.840> graphical<00:28:36.840> uh<00:28:37.519> here<00:28:38.279> some<00:28:39.080> uh<00:28:39.240> graphical 00:28:39.630 --> 00:28:39.640 align:start position:0% some graphical uh here some uh graphical 00:28:39.640 --> 00:28:42.990 align:start position:0% some graphical uh here some uh graphical tools<00:28:40.000> that<00:28:40.240> going<00:28:40.600> same<00:28:40.960> like<00:28:41.440> uh<00:28:42.200> dis<00:28:42.600> image 00:28:42.990 --> 00:28:43.000 align:start position:0% tools that going same like uh dis image 00:28:43.000 --> 00:28:45.830 align:start position:0% tools that going same like uh dis image writer<00:28:43.519> and<00:28:43.919> balena<00:28:44.399> exer<00:28:44.840> for<00:28:45.080> Windows<00:28:45.640> and 00:28:45.830 --> 00:28:45.840 align:start position:0% writer and balena exer for Windows and 00:28:45.840 --> 00:28:49.310 align:start position:0% writer and balena exer for Windows and even<00:28:46.039> for<00:28:46.279> Mac<00:28:46.600> is<00:28:46.799> also<00:28:47.159> Valena<00:28:48.039> so<00:28:48.480> there's<00:28:48.760> a 00:28:49.310 --> 00:28:49.320 align:start position:0% even for Mac is also Valena so there's a 00:28:49.320 --> 00:28:52.669 align:start position:0% even for Mac is also Valena so there's a lot<00:28:49.519> of<00:28:49.760> different<00:28:50.640> uh<00:28:51.240> ways<00:28:51.480> to<00:28:51.679> to<00:28:51.799> write<00:28:52.080> an 00:28:52.669 --> 00:28:52.679 align:start position:0% lot of different uh ways to to write an 00:28:52.679 --> 00:28:55.830 align:start position:0% lot of different uh ways to to write an SD<00:28:52.960> card<00:28:53.640> and<00:28:53.840> when<00:28:54.000> you<00:28:54.240> have<00:28:55.039> your<00:28:55.279> SD<00:28:55.559> card 00:28:55.830 --> 00:28:55.840 align:start position:0% SD card and when you have your SD card 00:28:55.840 --> 00:29:05.350 align:start position:0% SD card and when you have your SD card done<00:28:56.200> is<00:28:56.640> like<00:28:56.799> you<00:28:56.919> see<00:28:57.720> me<00:28:58.159> amount 00:29:05.350 --> 00:29:05.360 align:start position:0% 00:29:05.360 --> 00:29:08.350 align:start position:0% it<00:29:06.360> it's<00:29:06.840> I<00:29:07.039> this<00:29:07.200> it<00:29:07.320> like<00:29:07.640> put<00:29:07.799> the<00:29:07.880> SD<00:29:08.159> carard 00:29:08.350 --> 00:29:08.360 align:start position:0% it it's I this it like put the SD carard 00:29:08.360 --> 00:29:13.430 align:start position:0% it it's I this it like put the SD carard in<00:29:08.519> the<00:29:08.720> device<00:29:09.559> that's<00:29:09.840> not<00:29:10.080> not<00:29:10.240> so 00:29:13.430 --> 00:29:13.440 align:start position:0% 00:29:13.440 --> 00:29:17.549 align:start position:0% hard<00:29:14.440> and<00:29:14.760> if<00:29:14.880> you<00:29:15.000> want 00:29:17.549 --> 00:29:17.559 align:start position:0% 00:29:17.559 --> 00:29:20.269 align:start position:0% to<00:29:18.559> uh<00:29:18.960> plug 00:29:20.269 --> 00:29:20.279 align:start position:0% to uh plug 00:29:20.279 --> 00:29:22.950 align:start position:0% to uh plug the<00:29:21.279> the<00:29:21.480> device<00:29:21.919> and<00:29:22.120> if<00:29:22.240> you<00:29:22.320> want<00:29:22.480> to<00:29:22.640> come 00:29:22.950 --> 00:29:22.960 align:start position:0% the the device and if you want to come 00:29:22.960 --> 00:29:25.990 align:start position:0% the the device and if you want to come closer<00:29:23.559> and<00:29:24.559> let's<00:29:24.880> hope<00:29:25.200> that<00:29:25.399> everything<00:29:25.720> is 00:29:25.990 --> 00:29:26.000 align:start position:0% closer and let's hope that everything is 00:29:26.000 --> 00:29:28.470 align:start position:0% closer and let's hope that everything is okay 00:29:28.470 --> 00:29:28.480 align:start position:0% okay 00:29:28.480 --> 00:29:34.630 align:start position:0% okay no 00:29:34.630 --> 00:29:34.640 align:start position:0% 00:29:34.640 --> 00:29:42.149 align:start position:0% okay<00:29:35.640> something<00:29:36.080> will<00:29:36.279> start<00:29:36.760> here<00:29:37.760> let's 00:29:42.149 --> 00:29:42.159 align:start position:0% 00:29:42.159 --> 00:29:47.549 align:start position:0% see<00:29:43.159> uh<00:29:43.399> demo<00:29:43.720> effect<00:29:44.279> life 00:29:47.549 --> 00:29:47.559 align:start position:0% 00:29:47.559 --> 00:29:49.750 align:start position:0% themo 00:29:49.750 --> 00:29:49.760 align:start position:0% themo 00:29:49.760 --> 00:29:59.590 align:start position:0% themo yes<00:29:50.760> let<00:29:51.000> me 00:29:59.590 --> 00:29:59.600 align:start position:0% 00:29:59.600 --> 00:30:01.549 align:start position:0% so<00:29:59.880> again<00:30:00.120> now<00:30:00.320> we<00:30:00.440> are<00:30:00.559> going<00:30:00.720> to<00:30:00.919> connect<00:30:01.440> uh 00:30:01.549 --> 00:30:01.559 align:start position:0% so again now we are going to connect uh 00:30:01.559 --> 00:30:02.710 align:start position:0% so again now we are going to connect uh through 00:30:02.710 --> 00:30:02.720 align:start position:0% through 00:30:02.720 --> 00:30:04.830 align:start position:0% through SSH<00:30:03.720> and 00:30:04.830 --> 00:30:04.840 align:start position:0% SSH and 00:30:04.840 --> 00:30:08.110 align:start position:0% SSH and um<00:30:05.840> H<00:30:06.000> launch<00:30:06.399> the<00:30:06.559> script<00:30:07.320> that<00:30:07.760> we<00:30:07.880> were 00:30:08.110 --> 00:30:08.120 align:start position:0% um H launch the script that we were 00:30:08.120 --> 00:30:12.830 align:start position:0% um H launch the script that we were talking<00:30:08.600> about<00:30:09.600> and<00:30:10.399> we<00:30:10.519> will<00:30:10.760> see<00:30:11.279> how<00:30:12.159> uh 00:30:12.830 --> 00:30:12.840 align:start position:0% talking about and we will see how uh 00:30:12.840 --> 00:30:25.950 align:start position:0% talking about and we will see how uh this<00:30:13.159> image<00:30:13.679> is<00:30:14.679> turned<00:30:15.240> into<00:30:15.679> a<00:30:15.919> an<00:30:16.559> Noe<00:30:17.440> uh 00:30:25.950 --> 00:30:25.960 align:start position:0% 00:30:25.960 --> 00:30:40.669 align:start position:0% automatically<00:30:26.960> there's<00:30:27.200> no<00:30:28.120> work 00:30:40.669 --> 00:30:40.679 align:start position:0% 00:30:40.679 --> 00:30:44.990 align:start position:0% maybe<00:30:41.679> we<00:30:41.799> need<00:30:41.960> to<00:30:42.080> find<00:30:42.399> the 00:30:44.990 --> 00:30:45.000 align:start position:0% 00:30:45.000 --> 00:30:47.470 align:start position:0% IP 00:30:47.470 --> 00:30:47.480 align:start position:0% IP 00:30:47.480 --> 00:30:49.870 align:start position:0% IP so<00:30:48.480> in<00:30:48.640> order<00:30:48.880> to<00:30:49.039> create<00:30:49.279> the<00:30:49.399> demo<00:30:49.640> you<00:30:49.720> have 00:30:49.870 --> 00:30:49.880 align:start position:0% so in order to create the demo you have 00:30:49.880 --> 00:30:53.350 align:start position:0% so in order to create the demo you have to<00:30:50.159> to<00:30:50.320> start<00:30:50.799> uh<00:30:51.120> dhtp<00:30:51.880> the<00:30:52.080> server<00:30:52.440> in<00:30:52.640> my<00:30:53.200> my 00:30:53.350 --> 00:30:53.360 align:start position:0% to to start uh dhtp the server in my my 00:30:53.360 --> 00:30:54.990 align:start position:0% to to start uh dhtp the server in my my computer<00:30:53.720> in<00:30:53.840> order<00:30:54.080> to<00:30:54.320> simulate<00:30:54.840> my 00:30:54.990 --> 00:30:55.000 align:start position:0% computer in order to simulate my 00:30:55.000 --> 00:30:58.149 align:start position:0% computer in order to simulate my computer<00:30:55.320> as<00:30:55.399> a<00:30:55.559> router<00:30:55.960> here<00:30:56.200> but<00:30:56.600> uh<00:30:58.039> not 00:30:58.149 --> 00:30:58.159 align:start position:0% computer as a router here but uh not 00:30:58.159 --> 00:31:00.310 align:start position:0% computer as a router here but uh not needed<00:30:58.679> home<00:30:59.440> probably<00:30:59.799> your<00:30:59.960> your<00:31:00.120> home 00:31:00.310 --> 00:31:00.320 align:start position:0% needed home probably your your home 00:31:00.320 --> 00:31:03.149 align:start position:0% needed home probably your your home router<00:31:00.840> is<00:31:01.000> going<00:31:01.159> to<00:31:01.440> give<00:31:01.720> an<00:31:02.120> an<00:31:02.399> IP<00:31:02.799> to<00:31:02.960> the 00:31:03.149 --> 00:31:03.159 align:start position:0% router is going to give an an IP to the 00:31:03.159 --> 00:31:24.029 align:start position:0% router is going to give an an IP to the device<00:31:03.559> in<00:31:03.840> in<00:31:03.960> an<00:31:04.120> automatic 00:31:24.029 --> 00:31:24.039 align:start position:0% 00:31:24.039 --> 00:31:28.669 align:start position:0% way<00:31:25.039> now<00:31:25.279> we<00:31:25.440> are<00:31:26.039> entering<00:31:27.039> you<00:31:27.240> can<00:31:27.600> see 00:31:28.669 --> 00:31:28.679 align:start position:0% way now we are entering you can see 00:31:28.679 --> 00:31:30.950 align:start position:0% way now we are entering you can see this<00:31:29.399> this<00:31:29.559> is<00:31:29.760> the<00:31:29.960> standard<00:31:30.559> this<00:31:30.679> is<00:31:30.799> the 00:31:30.950 --> 00:31:30.960 align:start position:0% this this is the standard this is the 00:31:30.960 --> 00:31:34.350 align:start position:0% this this is the standard this is the standard<00:31:31.320> image<00:31:31.679> from<00:31:31.960> from<00:31:32.559> RBM<00:31:33.559> for<00:31:34.240> the 00:31:34.350 --> 00:31:34.360 align:start position:0% standard image from from RBM for the 00:31:34.360 --> 00:31:35.669 align:start position:0% standard image from from RBM for the rock 00:31:35.669 --> 00:31:35.679 align:start position:0% rock 00:31:35.679 --> 00:31:38.830 align:start position:0% rock five<00:31:36.679> and<00:31:36.960> now<00:31:37.200> we<00:31:37.320> are<00:31:37.440> going<00:31:37.679> to<00:31:38.399> to<00:31:38.559> launch 00:31:38.830 --> 00:31:38.840 align:start position:0% five and now we are going to to launch 00:31:38.840 --> 00:31:41.909 align:start position:0% five and now we are going to to launch the 00:31:41.909 --> 00:31:41.919 align:start position:0% 00:31:41.919 --> 00:31:45.629 align:start position:0% script<00:31:42.919> we<00:31:43.080> have<00:31:43.200> to<00:31:43.360> change<00:31:44.080> the 00:31:45.629 --> 00:31:45.639 align:start position:0% script we have to change the 00:31:45.639 --> 00:31:49.750 align:start position:0% script we have to change the the<00:31:46.639> the<00:31:46.760> mirrors<00:31:47.480> the<00:31:47.600> mirrors<00:31:48.440> yes<00:31:49.039> uh<00:31:49.600> we 00:31:49.750 --> 00:31:49.760 align:start position:0% the the mirrors the mirrors yes uh we 00:31:49.760 --> 00:31:52.310 align:start position:0% the the mirrors the mirrors yes uh we found<00:31:50.120> that<00:31:50.399> the<00:31:50.639> default<00:31:51.320> un<00:31:51.639> to<00:31:51.760> mirrors 00:31:52.310 --> 00:31:52.320 align:start position:0% found that the default un to mirrors 00:31:52.320 --> 00:31:56.629 align:start position:0% found that the default un to mirrors here<00:31:52.559> in<00:31:53.000> in<00:31:53.320> Thailand<00:31:54.320> are<00:31:55.279> so<00:31:55.559> slow<00:31:56.120> that<00:31:56.480> it 00:31:56.629 --> 00:31:56.639 align:start position:0% here in in Thailand are so slow that it 00:31:56.639 --> 00:31:58.470 align:start position:0% here in in Thailand are so slow that it makes<00:31:57.000> almost<00:31:57.320> impossible<00:31:57.679> to<00:31:57.919> created<00:31:58.320> this 00:31:58.470 --> 00:31:58.480 align:start position:0% makes almost impossible to created this 00:31:58.480 --> 00:32:01.149 align:start position:0% makes almost impossible to created this demo<00:31:58.840> here<00:31:59.200> at<00:31:59.360> least<00:31:59.519> in<00:31:59.679> our<00:31:59.919> hotel<00:32:00.919> because 00:32:01.149 --> 00:32:01.159 align:start position:0% demo here at least in our hotel because 00:32:01.159 --> 00:32:03.950 align:start position:0% demo here at least in our hotel because it's<00:32:01.360> so<00:32:01.559> extremely<00:32:01.960> slow<00:32:02.320> that<00:32:02.519> at<00:32:02.639> the<00:32:02.960> end 00:32:03.950 --> 00:32:03.960 align:start position:0% it's so extremely slow that at the end 00:32:03.960 --> 00:32:07.430 align:start position:0% it's so extremely slow that at the end simple<00:32:04.639> a<00:32:05.279> update<00:32:05.919> it<00:32:06.120> last<00:32:06.399> for<00:32:06.679> 15<00:32:07.000> minutes 00:32:07.430 --> 00:32:07.440 align:start position:0% simple a update it last for 15 minutes 00:32:07.440 --> 00:32:10.870 align:start position:0% simple a update it last for 15 minutes so<00:32:08.159> we<00:32:08.320> are<00:32:08.720> we<00:32:08.880> found<00:32:09.200> some<00:32:09.480> mirrors<00:32:10.039> closer 00:32:10.870 --> 00:32:10.880 align:start position:0% so we are we found some mirrors closer 00:32:10.880 --> 00:32:14.110 align:start position:0% so we are we found some mirrors closer we<00:32:11.039> hope<00:32:11.360> that<00:32:11.760> it<00:32:12.000> is<00:32:12.320> going<00:32:12.559> going<00:32:12.799> well<00:32:13.120> here 00:32:14.110 --> 00:32:14.120 align:start position:0% we hope that it is going going well here 00:32:14.120 --> 00:32:16.909 align:start position:0% we hope that it is going going well here let 00:32:16.909 --> 00:32:16.919 align:start position:0% 00:32:16.919 --> 00:32:19.710 align:start position:0% me<00:32:17.919> it's<00:32:18.080> not<00:32:18.240> a<00:32:18.399> big<00:32:18.559> deal<00:32:18.799> only<00:32:19.080> change<00:32:19.519> the 00:32:19.710 --> 00:32:19.720 align:start position:0% me it's not a big deal only change the 00:32:19.720 --> 00:32:24.350 align:start position:0% me it's not a big deal only change the the<00:32:19.840> sources<00:32:20.399> of<00:32:21.000> the<00:32:22.000> of<00:32:22.200> the<00:32:22.519> armian<00:32:23.519> um 00:32:24.350 --> 00:32:24.360 align:start position:0% the sources of the of the armian um 00:32:24.360 --> 00:32:56.430 align:start position:0% the sources of the of the armian um packages<00:32:24.960> and<00:32:25.559> let's<00:32:25.799> start 00:32:56.430 --> 00:32:56.440 align:start position:0% 00:32:56.440 --> 00:32:59.269 align:start position:0% this<00:32:56.600> is<00:32:56.840> the<00:32:57.679> uh<00:32:57.919> uh<00:32:58.080> script<00:32:58.519> for<00:32:58.919> for<00:32:59.120> the 00:32:59.269 --> 00:32:59.279 align:start position:0% this is the uh uh script for for the 00:32:59.279 --> 00:33:02.110 align:start position:0% this is the uh uh script for for the rock<00:32:59.519> five<00:32:59.760> you<00:32:59.880> can<00:33:00.080> find<00:33:00.320> it<00:33:00.480> in<00:33:01.039> our 00:33:02.110 --> 00:33:02.120 align:start position:0% rock five you can find it in our 00:33:02.120 --> 00:33:09.230 align:start position:0% rock five you can find it in our GitHub<00:33:03.120> so<00:33:03.399> you<00:33:03.519> can<00:33:03.679> take<00:33:03.799> a 00:33:09.230 --> 00:33:09.240 align:start position:0% 00:33:09.240 --> 00:33:13.029 align:start position:0% look<00:33:10.240> for<00:33:10.679> is<00:33:10.840> tring<00:33:11.200> with<00:33:11.720> Nano<00:33:12.720> because<00:33:12.919> he 00:33:13.029 --> 00:33:13.039 align:start position:0% look for is tring with Nano because he 00:33:13.039 --> 00:33:24.149 align:start position:0% look for is tring with Nano because he don't<00:33:13.279> want 00:33:24.149 --> 00:33:24.159 align:start position:0% 00:33:24.159 --> 00:33:28.710 align:start position:0% it<00:33:25.159> right 00:33:28.710 --> 00:33:28.720 align:start position:0% 00:33:28.720 --> 00:33:31.669 align:start position:0% okay<00:33:28.960> I<00:33:29.200> I<00:33:29.360> usually<00:33:29.679> don't<00:33:29.919> use<00:33:30.120> Nano<00:33:30.679> so<00:33:31.279> but 00:33:31.669 --> 00:33:31.679 align:start position:0% okay I I usually don't use Nano so but 00:33:31.679 --> 00:33:35.909 align:start position:0% okay I I usually don't use Nano so but theault<00:33:32.320> arm<00:33:33.120> don't<00:33:33.440> include<00:33:34.039> beam<00:33:34.799> so<00:33:35.480> I 00:33:35.909 --> 00:33:35.919 align:start position:0% theault arm don't include beam so I 00:33:35.919 --> 00:33:38.029 align:start position:0% theault arm don't include beam so I getting<00:33:36.360> little<00:33:36.639> stuck<00:33:36.960> here<00:33:37.200> but<00:33:37.840> we<00:33:37.919> are 00:33:38.029 --> 00:33:38.039 align:start position:0% getting little stuck here but we are 00:33:38.039 --> 00:33:41.070 align:start position:0% getting little stuck here but we are going<00:33:38.240> to<00:33:38.440> start<00:33:39.320> uh<00:33:39.919> the<00:33:40.240> the<00:33:40.440> the<00:33:40.559> magic<00:33:40.880> of 00:33:41.070 --> 00:33:41.080 align:start position:0% going to start uh the the the magic of 00:33:41.080 --> 00:33:43.389 align:start position:0% going to start uh the the the magic of the<00:33:41.360> bre<00:33:41.760> here<00:33:41.880> is<00:33:42.159> the<00:33:42.440> this<00:33:42.720> small<00:33:43.080> script 00:33:43.389 --> 00:33:43.399 align:start position:0% the bre here is the this small script 00:33:43.399 --> 00:33:46.110 align:start position:0% the bre here is the this small script that<00:33:43.760> transform<00:33:44.320> the<00:33:44.919> default<00:33:45.320> image<00:33:45.960> you 00:33:46.110 --> 00:33:46.120 align:start position:0% that transform the default image you 00:33:46.120 --> 00:33:47.909 align:start position:0% that transform the default image you have<00:33:46.360> you<00:33:46.440> don't<00:33:46.639> have<00:33:46.760> to<00:33:46.880> trust<00:33:47.240> us<00:33:47.519> you<00:33:47.760> can 00:33:47.909 --> 00:33:47.919 align:start position:0% have you don't have to trust us you can 00:33:47.919 --> 00:33:49.870 align:start position:0% have you don't have to trust us you can do<00:33:48.360> this<00:33:48.519> at<00:33:48.720> home<00:33:49.200> you<00:33:49.399> don't<00:33:49.600> know<00:33:49.760> the 00:33:49.870 --> 00:33:49.880 align:start position:0% do this at home you don't know the 00:33:49.880 --> 00:33:52.990 align:start position:0% do this at home you don't know the offici<00:33:50.240> AR<00:33:50.559> image<00:33:51.000> and<00:33:51.760> only<00:33:52.000> wrong<00:33:52.480> this<00:33:52.760> Skip 00:33:52.990 --> 00:33:53.000 align:start position:0% offici AR image and only wrong this Skip 00:33:53.000 --> 00:33:57.470 align:start position:0% offici AR image and only wrong this Skip and<00:33:53.120> will<00:33:53.279> transform<00:33:53.679> it<00:33:53.919> in<00:33:55.240> uh<00:33:56.240> uh<00:33:56.440> full<00:33:57.279> arm 00:33:57.470 --> 00:33:57.480 align:start position:0% and will transform it in uh uh full arm 00:33:57.480 --> 00:34:00.870 align:start position:0% and will transform it in uh uh full arm Noe 00:34:00.870 --> 00:34:00.880 align:start position:0% 00:34:00.880 --> 00:34:03.710 align:start position:0% okay<00:34:01.679> uh<00:34:01.960> if<00:34:02.080> you<00:34:02.240> download<00:34:02.600> the<00:34:02.760> rematch<00:34:03.440> that 00:34:03.710 --> 00:34:03.720 align:start position:0% okay uh if you download the rematch that 00:34:03.720 --> 00:34:05.990 align:start position:0% okay uh if you download the rematch that will<00:34:04.000> happen<00:34:04.840> uh<00:34:05.000> automatically<00:34:05.639> the<00:34:05.799> first 00:34:05.990 --> 00:34:06.000 align:start position:0% will happen uh automatically the first 00:34:06.000 --> 00:34:09.109 align:start position:0% will happen uh automatically the first run<00:34:06.679> the<00:34:06.799> first<00:34:07.039> time<00:34:07.240> that<00:34:07.360> you<00:34:07.480> run<00:34:07.960> the<00:34:08.960> the 00:34:09.109 --> 00:34:09.119 align:start position:0% run the first time that you run the the 00:34:09.119 --> 00:34:11.750 align:start position:0% run the first time that you run the the script<00:34:09.560> it<00:34:09.679> will<00:34:10.000> transform<00:34:10.480> it<00:34:10.760> and<00:34:11.200> do<00:34:11.520> all 00:34:11.750 --> 00:34:11.760 align:start position:0% script it will transform it and do all 00:34:11.760 --> 00:34:15.389 align:start position:0% script it will transform it and do all the<00:34:12.480> needed<00:34:12.839> changes<00:34:13.520> to<00:34:13.760> create<00:34:14.320> uh<00:34:15.040> this 00:34:15.389 --> 00:34:15.399 align:start position:0% the needed changes to create uh this 00:34:15.399 --> 00:34:17.310 align:start position:0% the needed changes to create uh this configuration<00:34:16.399> let's 00:34:17.310 --> 00:34:17.320 align:start position:0% configuration let's 00:34:17.320 --> 00:34:18.829 align:start position:0% configuration let's see 00:34:18.829 --> 00:34:18.839 align:start position:0% see 00:34:18.839 --> 00:34:22.270 align:start position:0% see have<00:34:19.839> a<00:34:20.000> sleep<00:34:20.560> waiting<00:34:20.879> for<00:34:21.119> your<00:34:21.919> router 00:34:22.270 --> 00:34:22.280 align:start position:0% have a sleep waiting for your router 00:34:22.280 --> 00:34:25.629 align:start position:0% have a sleep waiting for your router home<00:34:22.520> router<00:34:23.000> giving<00:34:23.280> you<00:34:23.440> an 00:34:25.629 --> 00:34:25.639 align:start position:0% home router giving you an 00:34:25.639 --> 00:34:28.550 align:start position:0% home router giving you an IP<00:34:26.639> and<00:34:26.800> let's<00:34:27.040> hope<00:34:27.320> that<00:34:27.919> uh<00:34:28.240> these<00:34:28.399> new 00:34:28.550 --> 00:34:28.560 align:start position:0% IP and let's hope that uh these new 00:34:28.560 --> 00:34:34.030 align:start position:0% IP and let's hope that uh these new mirrors<00:34:29.119> works<00:34:29.480> well<00:34:30.079> here<00:34:31.079> that's<00:34:31.720> 2<00:34:31.919> minutes 00:34:34.030 --> 00:34:34.040 align:start position:0% mirrors works well here that's 2 minutes 00:34:34.040 --> 00:34:36.470 align:start position:0% mirrors works well here that's 2 minutes okay<00:34:35.040> yeah<00:34:35.240> these<00:34:35.399> ones<00:34:35.679> are<00:34:35.919> the<00:34:36.079> the<00:34:36.200> fast 00:34:36.470 --> 00:34:36.480 align:start position:0% okay yeah these ones are the the fast 00:34:36.480 --> 00:34:37.629 align:start position:0% okay yeah these ones are the the fast ones 00:34:37.629 --> 00:34:37.639 align:start position:0% ones 00:34:37.639 --> 00:34:43.069 align:start position:0% ones so<00:34:38.639> so 00:34:43.069 --> 00:34:43.079 align:start position:0% 00:34:43.079 --> 00:34:47.349 align:start position:0% uh<00:34:44.079> how<00:34:44.200> much<00:34:44.440> time<00:34:45.119> uh<00:34:45.520> did<00:34:45.679> it<00:34:45.919> take<00:34:46.240> in<00:34:47.159> in 00:34:47.349 --> 00:34:47.359 align:start position:0% uh how much time uh did it take in in 00:34:47.359 --> 00:34:52.149 align:start position:0% uh how much time uh did it take in in our<00:34:47.919> demo<00:34:48.399> at<00:34:49.480> the<00:34:50.480> uh<00:34:50.639> 20<00:34:50.960> minutes<00:34:51.399> 2025 00:34:52.149 --> 00:34:52.159 align:start position:0% our demo at the uh 20 minutes 2025 00:34:52.159 --> 00:34:56.270 align:start position:0% our demo at the uh 20 minutes 2025 minutes<00:34:52.639> with<00:34:53.000> uh<00:34:53.839> official<00:34:54.839> ports<00:34:55.599> or<00:34:55.879> W 00:34:56.270 --> 00:34:56.280 align:start position:0% minutes with uh official ports or W 00:34:56.280 --> 00:34:59.829 align:start position:0% minutes with uh official ports or W ports<00:34:56.639> repositor<00:34:58.000> uh<00:34:58.320> here<00:34:58.640> from<00:34:58.920> Thailand<00:34:59.440> is 00:34:59.829 --> 00:34:59.839 align:start position:0% ports repositor uh here from Thailand is 00:34:59.839 --> 00:35:02.190 align:start position:0% ports repositor uh here from Thailand is last<00:35:00.200> for<00:35:00.560> 20<00:35:00.880> minutes<00:35:01.359> here<00:35:01.599> is<00:35:01.800> the<00:35:01.960> best 00:35:02.190 --> 00:35:02.200 align:start position:0% last for 20 minutes here is the best 00:35:02.200 --> 00:35:25.030 align:start position:0% last for 20 minutes here is the best that<00:35:02.480> we<00:35:02.599> could<00:35:02.880> find 00:35:25.030 --> 00:35:25.040 align:start position:0% 00:35:25.040 --> 00:35:28.270 align:start position:0% no<00:35:26.040> okay<00:35:26.400> we<00:35:26.520> know<00:35:26.720> this<00:35:26.839> is<00:35:26.920> a<00:35:27.040> little<00:35:27.240> B 00:35:28.270 --> 00:35:28.280 align:start position:0% no okay we know this is a little B 00:35:28.280 --> 00:35:30.710 align:start position:0% no okay we know this is a little B but<00:35:29.240> the<00:35:29.480> the<00:35:29.680> the<00:35:29.800> first<00:35:30.000> thing<00:35:30.240> that<00:35:30.520> is 00:35:30.710 --> 00:35:30.720 align:start position:0% but the the the first thing that is 00:35:30.720 --> 00:35:36.630 align:start position:0% but the the the first thing that is going<00:35:30.880> to<00:35:31.040> do<00:35:31.400> the<00:35:32.119> the<00:35:32.640> the<00:35:33.119> script<00:35:34.119> is 00:35:36.630 --> 00:35:36.640 align:start position:0% going to do the the the script is 00:35:36.640 --> 00:35:40.190 align:start position:0% going to do the the the script is uh<00:35:37.640> test<00:35:38.079> if<00:35:38.280> you<00:35:38.839> have<00:35:39.079> already<00:35:39.640> done<00:35:39.960> some 00:35:40.190 --> 00:35:40.200 align:start position:0% uh test if you have already done some 00:35:40.200 --> 00:35:41.950 align:start position:0% uh test if you have already done some installation<00:35:40.680> in<00:35:40.800> your<00:35:41.000> dis<00:35:41.320> because<00:35:41.800> uh 00:35:41.950 --> 00:35:41.960 align:start position:0% installation in your dis because uh 00:35:41.960 --> 00:35:44.390 align:start position:0% installation in your dis because uh probably<00:35:42.320> you<00:35:42.920> have<00:35:43.160> some<00:35:43.400> problems<00:35:43.880> with<00:35:44.119> SD 00:35:44.390 --> 00:35:44.400 align:start position:0% probably you have some problems with SD 00:35:44.400 --> 00:35:46.550 align:start position:0% probably you have some problems with SD car<00:35:44.640> of<00:35:44.839> the<00:35:45.079> device<00:35:45.440> so<00:35:45.760> you<00:35:45.920> have<00:35:46.079> to<00:35:46.200> change 00:35:46.550 --> 00:35:46.560 align:start position:0% car of the device so you have to change 00:35:46.560 --> 00:35:49.470 align:start position:0% car of the device so you have to change but<00:35:47.480> uh<00:35:47.760> the<00:35:48.040> initial<00:35:48.440> skip<00:35:48.800> takes<00:35:49.079> care<00:35:49.359> is 00:35:49.470 --> 00:35:49.480 align:start position:0% but uh the initial skip takes care is 00:35:49.480 --> 00:35:51.349 align:start position:0% but uh the initial skip takes care is you<00:35:49.680> have 00:35:51.349 --> 00:35:51.359 align:start position:0% you have 00:35:51.359 --> 00:35:54.109 align:start position:0% you have um<00:35:52.359> a<00:35:52.520> previous<00:35:52.880> installation<00:35:53.359> for<00:35:53.680> the 00:35:54.109 --> 00:35:54.119 align:start position:0% um a previous installation for the 00:35:54.119 --> 00:35:59.309 align:start position:0% um a previous installation for the ethereum<00:35:54.640> arm<00:35:55.359> uh<00:35:56.040> image<00:35:57.040> uh<00:35:57.359> it<00:35:57.920> not<00:35:58.240> will<00:35:58.480> be 00:35:59.309 --> 00:35:59.319 align:start position:0% ethereum arm uh image uh it not will be 00:35:59.319 --> 00:36:02.710 align:start position:0% ethereum arm uh image uh it not will be deleted<00:35:59.880> deleted<00:36:00.560> you<00:36:00.800> have<00:36:00.960> to<00:36:01.240> you<00:36:01.520> want<00:36:02.520> to 00:36:02.710 --> 00:36:02.720 align:start position:0% deleted deleted you have to you want to 00:36:02.720 --> 00:36:03.550 align:start position:0% deleted deleted you have to you want to keep<00:36:02.880> your 00:36:03.550 --> 00:36:03.560 align:start position:0% keep your 00:36:03.560 --> 00:36:16.430 align:start position:0% keep your configuration<00:36:04.760> and 00:36:16.430 --> 00:36:16.440 align:start position:0% 00:36:16.440 --> 00:36:19.750 align:start position:0% anything<00:36:17.560> uh<00:36:18.560> usually<00:36:18.880> it<00:36:19.000> takes<00:36:19.280> 10<00:36:19.520> 10 00:36:19.750 --> 00:36:19.760 align:start position:0% anything uh usually it takes 10 10 00:36:19.760 --> 00:36:22.589 align:start position:0% anything uh usually it takes 10 10 minutes<00:36:20.760> once<00:36:21.000> we<00:36:21.200> putot<00:36:21.599> your<00:36:22.000> your<00:36:22.200> device 00:36:22.589 --> 00:36:22.599 align:start position:0% minutes once we putot your your device 00:36:22.599 --> 00:36:25.270 align:start position:0% minutes once we putot your your device with<00:36:22.800> a<00:36:23.040> with<00:36:23.160> a<00:36:23.280> new<00:36:23.480> image<00:36:24.480> uh<00:36:24.720> it<00:36:24.839> takes<00:36:25.079> 10 00:36:25.270 --> 00:36:25.280 align:start position:0% with a with a new image uh it takes 10 00:36:25.280 --> 00:36:27.750 align:start position:0% with a with a new image uh it takes 10 minutes<00:36:25.800> yes<00:36:26.200> the<00:36:26.280> first<00:36:26.520> putot<00:36:26.760> is<00:36:27.079> alone 00:36:27.750 --> 00:36:27.760 align:start position:0% minutes yes the first putot is alone 00:36:27.760 --> 00:36:29.630 align:start position:0% minutes yes the first putot is alone it's<00:36:28.160> quite<00:36:28.400> long<00:36:28.599> it's<00:36:28.760> about<00:36:28.960> 10<00:36:29.119> minutes 00:36:29.630 --> 00:36:29.640 align:start position:0% it's quite long it's about 10 minutes 00:36:29.640 --> 00:36:32.069 align:start position:0% it's quite long it's about 10 minutes but<00:36:29.880> here<00:36:30.680> the<00:36:30.839> thing<00:36:31.000> is<00:36:31.480> getting<00:36:31.839> really 00:36:32.069 --> 00:36:32.079 align:start position:0% but here the thing is getting really 00:36:32.079 --> 00:36:35.829 align:start position:0% but here the thing is getting really slow<00:36:33.079> uh<00:36:33.200> you<00:36:33.359> have<00:36:33.480> to<00:36:33.599> sync<00:36:34.280> all<00:36:34.560> the<00:36:35.440> uh 00:36:35.829 --> 00:36:35.839 align:start position:0% slow uh you have to sync all the uh 00:36:35.839 --> 00:36:38.829 align:start position:0% slow uh you have to sync all the uh information<00:36:36.319> for<00:36:36.920> the<00:36:37.760> package<00:36:38.079> mirrors<00:36:38.480> from 00:36:38.829 --> 00:36:38.839 align:start position:0% information for the package mirrors from 00:36:38.839 --> 00:36:43.870 align:start position:0% information for the package mirrors from the<00:36:39.480> the<00:36:40.040> this<00:36:41.000> to<00:36:41.119> basic<00:36:41.760> distribution<00:36:42.880> but 00:36:43.870 --> 00:36:43.880 align:start position:0% the the this to basic distribution but 00:36:43.880 --> 00:36:45.190 align:start position:0% the the this to basic distribution but here<00:36:44.079> will<00:36:44.319> depend<00:36:44.599> of<00:36:44.760> the<00:36:44.880> internet 00:36:45.190 --> 00:36:45.200 align:start position:0% here will depend of the internet 00:36:45.200 --> 00:36:48.069 align:start position:0% here will depend of the internet connection<00:36:45.640> here<00:36:46.480> yeah<00:36:46.760> and<00:36:47.200> uh<00:36:47.560> if<00:36:47.760> it's 00:36:48.069 --> 00:36:48.079 align:start position:0% connection here yeah and uh if it's 00:36:48.079 --> 00:36:50.990 align:start position:0% connection here yeah and uh if it's close<00:36:48.440> or<00:36:49.040> not<00:36:49.280> very<00:36:49.480> close<00:36:49.760> from<00:36:49.960> the<00:36:50.079> sources 00:36:50.990 --> 00:36:51.000 align:start position:0% close or not very close from the sources 00:36:51.000 --> 00:36:54.470 align:start position:0% close or not very close from the sources and<00:36:51.359> the<00:36:52.240> one<00:36:52.599> official<00:36:53.079> repositories<00:36:53.680> are<00:36:53.920> in 00:36:54.470 --> 00:36:54.480 align:start position:0% and the one official repositories are in 00:36:54.480 --> 00:36:58.550 align:start position:0% and the one official repositories are in in<00:36:54.760> us<00:36:55.760> so<00:36:56.240> are<00:36:56.560> quite<00:36:56.800> far<00:36:57.079> and 00:36:58.550 --> 00:36:58.560 align:start position:0% in us so are quite far and 00:36:58.560 --> 00:37:01.030 align:start position:0% in us so are quite far and yeah<00:36:59.200> definitely<00:37:00.000> not<00:37:00.200> the<00:37:00.319> best<00:37:00.680> condition 00:37:01.030 --> 00:37:01.040 align:start position:0% yeah definitely not the best condition 00:37:01.040 --> 00:37:03.150 align:start position:0% yeah definitely not the best condition here 00:37:03.150 --> 00:37:03.160 align:start position:0% here 00:37:03.160 --> 00:37:10.309 align:start position:0% here because<00:37:04.160> networking<00:37:04.800> is<00:37:05.000> not<00:37:05.319> the<00:37:06.079> the<00:37:06.240> best 00:37:10.309 --> 00:37:10.319 align:start position:0% 00:37:10.319 --> 00:37:13.589 align:start position:0% here<00:37:11.319> no<00:37:11.560> it's<00:37:11.880> it's<00:37:12.280> it's<00:37:12.440> updating<00:37:13.119> the<00:37:13.400> the 00:37:13.589 --> 00:37:13.599 align:start position:0% here no it's it's it's updating the the 00:37:13.599 --> 00:37:16.950 align:start position:0% here no it's it's it's updating the the AP<00:37:14.119> repositories<00:37:15.079> just<00:37:15.359> no<00:37:15.520> the<00:37:15.960> the<00:37:16.160> first 00:37:16.950 --> 00:37:16.960 align:start position:0% AP repositories just no the the first 00:37:16.960 --> 00:37:19.190 align:start position:0% AP repositories just no the the first first<00:37:17.440> thing<00:37:17.680> that<00:37:17.839> you<00:37:17.960> should<00:37:18.240> do<00:37:18.920> when<00:37:19.079> you 00:37:19.190 --> 00:37:19.200 align:start position:0% first thing that you should do when you 00:37:19.200 --> 00:37:22.309 align:start position:0% first thing that you should do when you are<00:37:19.520> going<00:37:19.720> to<00:37:19.880> install<00:37:20.240> anything<00:37:20.560> in<00:37:20.839> a<00:37:21.480> wtu 00:37:22.309 --> 00:37:22.319 align:start position:0% are going to install anything in a wtu 00:37:22.319 --> 00:37:25.510 align:start position:0% are going to install anything in a wtu deing<00:37:23.000> distribution<00:37:23.560> is<00:37:23.800> to<00:37:23.960> syn<00:37:24.400> your<00:37:25.280> your 00:37:25.510 --> 00:37:25.520 align:start position:0% deing distribution is to syn your your 00:37:25.520 --> 00:37:28.150 align:start position:0% deing distribution is to syn your your computer<00:37:26.000> with<00:37:26.319> the<00:37:26.760> the<00:37:27.040> last<00:37:27.280> lat<00:37:27.800> versions 00:37:28.150 --> 00:37:28.160 align:start position:0% computer with the the last lat versions 00:37:28.160 --> 00:37:30.990 align:start position:0% computer with the the last lat versions of<00:37:28.400> the<00:37:28.640> packages<00:37:29.200> and<00:37:29.319> you<00:37:29.480> have<00:37:29.640> to<00:37:30.319> it<00:37:30.480> it 00:37:30.990 --> 00:37:31.000 align:start position:0% of the packages and you have to it it 00:37:31.000 --> 00:37:33.750 align:start position:0% of the packages and you have to it it needs<00:37:31.359> to<00:37:31.720> to<00:37:31.880> install<00:37:32.200> some<00:37:32.440> packages<00:37:33.119> and<00:37:33.560> to 00:37:33.750 --> 00:37:33.760 align:start position:0% needs to to install some packages and to 00:37:33.760 --> 00:37:36.390 align:start position:0% needs to to install some packages and to make<00:37:33.960> sure<00:37:34.319> that<00:37:35.000> everything<00:37:35.480> is<00:37:35.880> okay<00:37:36.200> you 00:37:36.390 --> 00:37:36.400 align:start position:0% make sure that everything is okay you 00:37:36.400 --> 00:37:38.710 align:start position:0% make sure that everything is okay you need<00:37:36.599> to<00:37:37.000> to<00:37:37.119> make<00:37:37.280> an<00:37:37.440> update<00:37:37.920> in<00:37:38.000> the<00:37:38.200> last 00:37:38.710 --> 00:37:38.720 align:start position:0% need to to make an update in the last 00:37:38.720 --> 00:37:41.069 align:start position:0% need to to make an update in the last latest<00:37:39.079> version<00:37:39.680> available<00:37:40.200> so<00:37:40.680> you<00:37:40.839> have<00:37:40.960> to 00:37:41.069 --> 00:37:41.079 align:start position:0% latest version available so you have to 00:37:41.079 --> 00:37:43.750 align:start position:0% latest version available so you have to do<00:37:41.280> it<00:37:41.760> it's<00:37:42.480> it's<00:37:42.680> now<00:37:43.040> it's<00:37:43.160> now<00:37:43.319> installing 00:37:43.750 --> 00:37:43.760 align:start position:0% do it it's it's now it's now installing 00:37:43.760 --> 00:37:47.630 align:start position:0% do it it's it's now it's now installing some<00:37:44.680> some<00:37:44.960> packages<00:37:45.920> yes<00:37:46.599> uh<00:37:47.160> after<00:37:47.480> the 00:37:47.630 --> 00:37:47.640 align:start position:0% some some packages yes uh after the 00:37:47.640 --> 00:37:49.950 align:start position:0% some some packages yes uh after the first<00:37:47.920> Sy<00:37:48.400> which<00:37:48.800> the<00:37:49.280> the<00:37:49.520> the<00:37:49.599> only<00:37:49.839> the 00:37:49.950 --> 00:37:49.960 align:start position:0% first Sy which the the the only the 00:37:49.960 --> 00:37:52.150 align:start position:0% first Sy which the the the only the slowest<00:37:50.319> one<00:37:50.760> later<00:37:51.160> you<00:37:51.319> have<00:37:51.680> already<00:37:52.000> the 00:37:52.150 --> 00:37:52.160 align:start position:0% slowest one later you have already the 00:37:52.160 --> 00:37:55.589 align:start position:0% slowest one later you have already the latest<00:37:52.520> version<00:37:52.880> and<00:37:53.119> it<00:37:53.440> will<00:37:53.680> go<00:37:54.000> very<00:37:54.599> fast 00:37:55.589 --> 00:37:55.599 align:start position:0% latest version and it will go very fast 00:37:55.599 --> 00:37:59.349 align:start position:0% latest version and it will go very fast uh<00:37:55.839> you<00:37:56.640> uh<00:37:56.960> have<00:37:57.119> to<00:37:57.200> see<00:37:57.359> the<00:37:57.560> some<00:37:58.560> we<00:37:58.800> think 00:37:59.349 --> 00:37:59.359 align:start position:0% uh you uh have to see the some we think 00:37:59.359 --> 00:38:02.910 align:start position:0% uh you uh have to see the some we think uh<00:37:59.560> essential<00:38:00.000> Tools<00:38:00.440> in<00:38:00.599> order<00:38:00.920> to<00:38:01.920> uh<00:38:02.640> create 00:38:02.910 --> 00:38:02.920 align:start position:0% uh essential Tools in order to uh create 00:38:02.920 --> 00:38:06.870 align:start position:0% uh essential Tools in order to uh create your<00:38:03.240> image<00:38:04.240> some<00:38:04.680> tools<00:38:05.119> like<00:38:05.560> uh<00:38:06.040> beam<00:38:06.720> of 00:38:06.870 --> 00:38:06.880 align:start position:0% your image some tools like uh beam of 00:38:06.880 --> 00:38:10.069 align:start position:0% your image some tools like uh beam of course<00:38:07.200> and<00:38:07.640> tet<00:38:08.480> for<00:38:08.680> sinking<00:38:09.119> or 00:38:10.069 --> 00:38:10.079 align:start position:0% course and tet for sinking or 00:38:10.079 --> 00:38:16.109 align:start position:0% course and tet for sinking or seeing<00:38:11.079> uh<00:38:11.960> a<00:38:12.400> better<00:38:12.680> S<00:38:13.040> loog<00:38:13.359> here 00:38:16.109 --> 00:38:16.119 align:start position:0% seeing uh a better S loog here 00:38:16.119 --> 00:38:18.910 align:start position:0% seeing uh a better S loog here uh<00:38:17.119> and<00:38:17.640> at<00:38:17.760> the<00:38:17.880> end<00:38:18.240> the<00:38:18.359> most<00:38:18.560> important 00:38:18.910 --> 00:38:18.920 align:start position:0% uh and at the end the most important 00:38:18.920 --> 00:38:22.990 align:start position:0% uh and at the end the most important thing<00:38:19.160> here<00:38:19.400> is<00:38:20.319> uh<00:38:21.319> where<00:38:21.520> is 00:38:22.990 --> 00:38:23.000 align:start position:0% thing here is uh where is 00:38:23.000 --> 00:38:27.950 align:start position:0% thing here is uh where is the<00:38:24.000> uh<00:38:24.680> a<00:38:24.880> j<00:38:25.160> disk<00:38:25.520> in<00:38:25.680> order<00:38:26.000> to 00:38:27.950 --> 00:38:27.960 align:start position:0% the uh a j disk in order to 00:38:27.960 --> 00:38:31.309 align:start position:0% the uh a j disk in order to create<00:38:28.359> a<00:38:29.160> partition<00:38:30.160> partition<00:38:30.599> in<00:38:30.839> the<00:38:31.160> the 00:38:31.309 --> 00:38:31.319 align:start position:0% create a partition partition in the the 00:38:31.319 --> 00:38:33.670 align:start position:0% create a partition partition in the the MBM<00:38:31.880> disc<00:38:32.200> for<00:38:32.440> the<00:38:32.520> first<00:38:32.760> time<00:38:33.119> probably<00:38:33.440> you 00:38:33.670 --> 00:38:33.680 align:start position:0% MBM disc for the first time probably you 00:38:33.680 --> 00:38:35.829 align:start position:0% MBM disc for the first time probably you don't<00:38:33.920> have<00:38:34.160> anything<00:38:34.440> in<00:38:34.640> your<00:38:35.160> disc<00:38:35.599> and<00:38:35.720> you 00:38:35.829 --> 00:38:35.839 align:start position:0% don't have anything in your disc and you 00:38:35.839 --> 00:38:38.990 align:start position:0% don't have anything in your disc and you have<00:38:36.000> to<00:38:36.160> create<00:38:36.400> a<00:38:36.560> partition<00:38:37.040> in<00:38:37.599> a<00:38:38.599> custom 00:38:38.990 --> 00:38:39.000 align:start position:0% have to create a partition in a custom 00:38:39.000 --> 00:38:42.510 align:start position:0% have to create a partition in a custom way<00:38:39.480> in<00:38:39.599> order<00:38:39.880> to<00:38:40.119> have<00:38:40.480> your 00:38:42.510 --> 00:38:42.520 align:start position:0% way in order to have your 00:38:42.520 --> 00:38:44.430 align:start position:0% way in order to have your um<00:38:43.520> swap 00:38:44.430 --> 00:38:44.440 align:start position:0% um swap 00:38:44.440 --> 00:38:48.150 align:start position:0% um swap partition<00:38:45.440> and<00:38:45.880> use<00:38:46.240> all<00:38:46.560> the<00:38:47.319> uh<00:38:47.599> available 00:38:48.150 --> 00:38:48.160 align:start position:0% partition and use all the uh available 00:38:48.160 --> 00:38:51.910 align:start position:0% partition and use all the uh available space<00:38:48.680> in<00:38:48.800> order<00:38:49.160> to<00:38:49.599> have<00:38:50.160> the<00:38:51.160> uh<00:38:51.520> sync 00:38:51.910 --> 00:38:51.920 align:start position:0% space in order to have the uh sync 00:38:51.920 --> 00:38:54.790 align:start position:0% space in order to have the uh sync database<00:38:52.359> of<00:38:52.520> the<00:38:53.040> clients<00:38:54.040> at<00:38:54.160> the<00:38:54.280> end<00:38:54.560> you 00:38:54.790 --> 00:38:54.800 align:start position:0% database of the clients at the end you 00:38:54.800 --> 00:38:57.950 align:start position:0% database of the clients at the end you will<00:38:54.960> need<00:38:55.160> a<00:38:55.280> lot<00:38:55.440> of<00:38:55.599> space<00:38:55.880> to<00:38:56.000> sync<00:38:56.400> a<00:38:56.920> uh<00:38:57.800> to 00:38:57.950 --> 00:38:57.960 align:start position:0% will need a lot of space to sync a uh to 00:38:57.960 --> 00:39:04.030 align:start position:0% will need a lot of space to sync a uh to sync<00:38:58.200> the 00:39:04.030 --> 00:39:04.040 align:start position:0% 00:39:04.040 --> 00:39:06.550 align:start position:0% blockchain<00:39:05.040> h<00:39:05.200> no<00:39:05.839> it<00:39:05.920> doesn't<00:39:06.200> start<00:39:06.440> to 00:39:06.550 --> 00:39:06.560 align:start position:0% blockchain h no it doesn't start to 00:39:06.560 --> 00:39:09.230 align:start position:0% blockchain h no it doesn't start to think<00:39:06.920> already<00:39:07.560> uh<00:39:07.720> to<00:39:07.839> syn<00:39:08.119> already<00:39:08.680> uh<00:39:08.920> here 00:39:09.230 --> 00:39:09.240 align:start position:0% think already uh to syn already uh here 00:39:09.240 --> 00:39:11.829 align:start position:0% think already uh to syn already uh here is<00:39:09.440> only<00:39:09.680> preparing<00:39:10.160> the<00:39:10.359> operating<00:39:10.880> system 00:39:11.829 --> 00:39:11.839 align:start position:0% is only preparing the operating system 00:39:11.839 --> 00:39:16.069 align:start position:0% is only preparing the operating system to<00:39:12.359> you<00:39:12.440> mean<00:39:12.839> the<00:39:12.920> e<00:39:13.520> no<00:39:14.400> no<00:39:14.640> no<00:39:14.800> no<00:39:15.000> no<00:39:16.000> the 00:39:16.069 --> 00:39:16.079 align:start position:0% to you mean the e no no no no no the 00:39:16.079 --> 00:39:18.870 align:start position:0% to you mean the e no no no no no the clients<00:39:16.480> the<00:39:16.920> clients<00:39:17.240> are<00:39:17.560> even<00:39:17.800> not 00:39:18.870 --> 00:39:18.880 align:start position:0% clients the clients are even not 00:39:18.880 --> 00:39:25.470 align:start position:0% clients the clients are even not installed<00:39:19.920> yeah<00:39:21.000> okay<00:39:22.000> uh<00:39:22.960> let's<00:39:23.480> so<00:39:23.880> this<00:39:24.480> is 00:39:25.470 --> 00:39:25.480 align:start position:0% installed yeah okay uh let's so this is 00:39:25.480 --> 00:39:27.829 align:start position:0% installed yeah okay uh let's so this is maybe<00:39:25.839> probably<00:39:26.440> a<00:39:26.560> little<00:39:26.920> low<00:39:27.119> level<00:39:27.480> but<00:39:27.720> at 00:39:27.829 --> 00:39:27.839 align:start position:0% maybe probably a little low level but at 00:39:27.839 --> 00:39:29.349 align:start position:0% maybe probably a little low level but at the<00:39:27.920> end<00:39:28.119> you<00:39:28.200> are<00:39:28.359> going<00:39:28.560> to 00:39:29.349 --> 00:39:29.359 align:start position:0% the end you are going to 00:39:29.359 --> 00:39:33.270 align:start position:0% the end you are going to format<00:39:30.359> uh<00:39:30.560> your<00:39:31.319> mbme 00:39:33.270 --> 00:39:33.280 align:start position:0% format uh your mbme 00:39:33.280 --> 00:39:36.829 align:start position:0% format uh your mbme dis<00:39:34.280> uh<00:39:34.520> is<00:39:34.839> take<00:39:35.520> automatically<00:39:36.440> you<00:39:36.599> will 00:39:36.829 --> 00:39:36.839 align:start position:0% dis uh is take automatically you will 00:39:36.839 --> 00:39:39.550 align:start position:0% dis uh is take automatically you will create<00:39:37.119> a<00:39:37.240> partition<00:39:37.760> format<00:39:38.200> it<00:39:38.680> use<00:39:38.960> all<00:39:39.200> the 00:39:39.550 --> 00:39:39.560 align:start position:0% create a partition format it use all the 00:39:39.560 --> 00:39:41.510 align:start position:0% create a partition format it use all the Ava<00:39:39.960> available<00:39:40.400> space<00:39:40.680> in<00:39:40.800> the 00:39:41.510 --> 00:39:41.520 align:start position:0% Ava available space in the 00:39:41.520 --> 00:39:45.670 align:start position:0% Ava available space in the disk<00:39:42.520> uh<00:39:42.720> we<00:39:42.839> use<00:39:43.520> uh<00:39:43.640> X4<00:39:44.119> file<00:39:44.359> system<00:39:45.119> you<00:39:45.359> are 00:39:45.670 --> 00:39:45.680 align:start position:0% disk uh we use uh X4 file system you are 00:39:45.680 --> 00:39:49.109 align:start position:0% disk uh we use uh X4 file system you are into<00:39:46.119> Linux<00:39:46.560> you<00:39:46.720> will<00:39:46.920> know<00:39:47.200> that<00:39:47.839> there<00:39:48.839> are 00:39:49.109 --> 00:39:49.119 align:start position:0% into Linux you will know that there are 00:39:49.119 --> 00:39:51.550 align:start position:0% into Linux you will know that there are a<00:39:49.359> lot<00:39:49.520> of<00:39:49.720> different<00:39:50.119> f<00:39:50.520> file<00:39:50.760> systems<00:39:51.200> we<00:39:51.400> are 00:39:51.550 --> 00:39:51.560 align:start position:0% a lot of different f file systems we are 00:39:51.560 --> 00:39:52.870 align:start position:0% a lot of different f file systems we are going<00:39:52.040> here 00:39:52.870 --> 00:39:52.880 align:start position:0% going here 00:39:52.880 --> 00:39:55.910 align:start position:0% going here to<00:39:53.880> in<00:39:54.000> our<00:39:54.240> opinion<00:39:54.560> the<00:39:54.680> most<00:39:55.000> stable 00:39:55.910 --> 00:39:55.920 align:start position:0% to in our opinion the most stable 00:39:55.920 --> 00:40:01.349 align:start position:0% to in our opinion the most stable because<00:39:56.640> this<00:39:56.760> is<00:39:56.920> r<00:39:57.400> 2<00:39:57.640> from<00:39:57.920> Ser 00:40:01.349 --> 00:40:01.359 align:start position:0% 00:40:01.359 --> 00:40:06.630 align:start position:0% always<00:40:02.839> uh<00:40:03.839> we<00:40:03.960> are<00:40:04.160> going<00:40:04.480> to<00:40:05.359> to<00:40:05.560> create<00:40:06.000> two 00:40:06.630 --> 00:40:06.640 align:start position:0% always uh we are going to to create two 00:40:06.640 --> 00:40:09.030 align:start position:0% always uh we are going to to create two partitions<00:40:07.640> a<00:40:07.760> home<00:40:08.040> partition<00:40:08.400> a<00:40:08.560> very<00:40:08.800> big 00:40:09.030 --> 00:40:09.040 align:start position:0% partitions a home partition a very big 00:40:09.040 --> 00:40:12.109 align:start position:0% partitions a home partition a very big home<00:40:09.280> partition<00:40:09.920> and<00:40:10.280> another<00:40:10.920> partition<00:40:11.440> to 00:40:12.109 --> 00:40:12.119 align:start position:0% home partition and another partition to 00:40:12.119 --> 00:40:16.630 align:start position:0% home partition and another partition to uh<00:40:12.319> swap<00:40:12.800> space<00:40:13.079> and<00:40:13.560> TMP<00:40:14.720> U<00:40:15.720> and<00:40:16.119> temporary 00:40:16.630 --> 00:40:16.640 align:start position:0% uh swap space and TMP U and temporary 00:40:16.640 --> 00:40:19.550 align:start position:0% uh swap space and TMP U and temporary files<00:40:17.640> like<00:40:18.040> logs<00:40:18.400> or<00:40:18.599> something<00:40:18.880> like<00:40:19.079> this 00:40:19.550 --> 00:40:19.560 align:start position:0% files like logs or something like this 00:40:19.560 --> 00:40:21.950 align:start position:0% files like logs or something like this in<00:40:19.720> order<00:40:20.000> to<00:40:20.319> avoid<00:40:20.599> to<00:40:20.800> Bright<00:40:21.200> in<00:40:21.359> the<00:40:21.640> SD 00:40:21.950 --> 00:40:21.960 align:start position:0% in order to avoid to Bright in the SD 00:40:21.960 --> 00:40:25.670 align:start position:0% in order to avoid to Bright in the SD car<00:40:22.680> anything<00:40:23.680> we<00:40:23.800> are<00:40:24.440> trying<00:40:24.800> to<00:40:25.319> make<00:40:25.560> the 00:40:25.670 --> 00:40:25.680 align:start position:0% car anything we are trying to make the 00:40:25.680 --> 00:40:28.270 align:start position:0% car anything we are trying to make the SD<00:40:26.000> car<00:40:26.319> as<00:40:26.520> readonly<00:40:27.000> as<00:40:27.079> possible<00:40:27.319> I<00:40:27.839> because 00:40:28.270 --> 00:40:28.280 align:start position:0% SD car as readonly as possible I because 00:40:28.280 --> 00:40:30.309 align:start position:0% SD car as readonly as possible I because at<00:40:28.400> the<00:40:28.520> end<00:40:28.720> is<00:40:29.040> the<00:40:29.319> bottleneck<00:40:29.880> in<00:40:30.040> this 00:40:30.309 --> 00:40:30.319 align:start position:0% at the end is the bottleneck in this 00:40:30.319 --> 00:40:31.990 align:start position:0% at the end is the bottleneck in this kind<00:40:30.520> of 00:40:31.990 --> 00:40:32.000 align:start position:0% kind of 00:40:32.000 --> 00:40:34.910 align:start position:0% kind of installations<00:40:33.000> we<00:40:33.200> create<00:40:33.720> an<00:40:33.960> ethereum<00:40:34.400> user 00:40:34.910 --> 00:40:34.920 align:start position:0% installations we create an ethereum user 00:40:34.920 --> 00:40:38.510 align:start position:0% installations we create an ethereum user is<00:40:35.560> a<00:40:36.560> decision<00:40:37.040> that<00:40:37.240> we<00:40:37.359> made<00:40:37.920> H<00:40:38.200> everything 00:40:38.510 --> 00:40:38.520 align:start position:0% is a decision that we made H everything 00:40:38.520 --> 00:40:40.990 align:start position:0% is a decision that we made H everything is<00:40:38.640> running<00:40:39.160> under<00:40:39.480> a<00:40:39.720> etherum<00:40:40.200> user<00:40:40.520> in<00:40:40.760> the 00:40:40.990 --> 00:40:41.000 align:start position:0% is running under a etherum user in the 00:40:41.000 --> 00:40:43.150 align:start position:0% is running under a etherum user in the in<00:40:41.079> the<00:40:41.240> computer<00:40:42.160> all<00:40:42.319> the<00:40:42.480> clients<00:40:42.800> running 00:40:43.150 --> 00:40:43.160 align:start position:0% in the computer all the clients running 00:40:43.160 --> 00:40:44.829 align:start position:0% in the computer all the clients running with<00:40:43.319> the<00:40:43.440> same<00:40:43.680> user<00:40:44.079> ethereum<00:40:44.560> all<00:40:44.680> the 00:40:44.829 --> 00:40:44.839 align:start position:0% with the same user ethereum all the 00:40:44.839 --> 00:40:47.870 align:start position:0% with the same user ethereum all the configuration<00:40:45.440> is<00:40:45.599> in<00:40:45.960> ETC<00:40:46.880> SL 00:40:47.870 --> 00:40:47.880 align:start position:0% configuration is in ETC SL 00:40:47.880 --> 00:40:51.510 align:start position:0% configuration is in ETC SL ethereum<00:40:48.880> uh<00:40:49.319> we<00:40:50.000> wanted<00:40:50.480> to<00:40:50.640> do<00:40:50.839> it<00:40:51.040> because 00:40:51.510 --> 00:40:51.520 align:start position:0% ethereum uh we wanted to do it because 00:40:51.520 --> 00:40:53.829 align:start position:0% ethereum uh we wanted to do it because we<00:40:51.680> think<00:40:52.359> it's<00:40:52.560> the<00:40:52.720> easy<00:40:53.040> way<00:40:53.560> you<00:40:53.680> are 00:40:53.829 --> 00:40:53.839 align:start position:0% we think it's the easy way you are 00:40:53.839 --> 00:40:55.870 align:start position:0% we think it's the easy way you are running<00:40:54.359> ethereum<00:40:54.800> software<00:40:55.440> everything<00:40:55.720> is 00:40:55.870 --> 00:40:55.880 align:start position:0% running ethereum software everything is 00:40:55.880 --> 00:40:57.430 align:start position:0% running ethereum software everything is under<00:40:56.160> the<00:40:56.280> ethereum<00:40:56.640> user<00:40:56.920> and<00:40:57.040> the<00:40:57.319> the 00:40:57.430 --> 00:40:57.440 align:start position:0% under the ethereum user and the the 00:40:57.440 --> 00:40:59.470 align:start position:0% under the ethereum user and the the ethereum<00:40:57.880> configuration<00:40:58.359> repository<00:40:59.280> all 00:40:59.470 --> 00:40:59.480 align:start position:0% ethereum configuration repository all 00:40:59.480 --> 00:41:02.109 align:start position:0% ethereum configuration repository all the<00:40:59.640> clients<00:41:00.160> all<00:41:00.480> the<00:41:01.119> layer<00:41:01.400> one<00:41:01.599> layer<00:41:01.880> two 00:41:02.109 --> 00:41:02.119 align:start position:0% the clients all the layer one layer two 00:41:02.119 --> 00:41:04.430 align:start position:0% the clients all the layer one layer two consens<00:41:02.599> execution<00:41:03.040> clients<00:41:03.440> have<00:41:04.240> the 00:41:04.430 --> 00:41:04.440 align:start position:0% consens execution clients have the 00:41:04.440 --> 00:41:06.470 align:start position:0% consens execution clients have the configuration<00:41:04.960> on<00:41:05.200> the<00:41:05.400> the<00:41:05.520> same<00:41:05.760> directory 00:41:06.470 --> 00:41:06.480 align:start position:0% configuration on the the same directory 00:41:06.480 --> 00:41:10.230 align:start position:0% configuration on the the same directory so<00:41:06.839> yeah<00:41:07.359> and<00:41:07.839> if<00:41:08.280> if<00:41:08.760> something<00:41:09.119> goes<00:41:09.400> wrong 00:41:10.230 --> 00:41:10.240 align:start position:0% so yeah and if if something goes wrong 00:41:10.240 --> 00:41:13.390 align:start position:0% so yeah and if if something goes wrong uh<00:41:10.440> with<00:41:10.640> the<00:41:10.920> OS<00:41:11.680> you<00:41:11.839> just<00:41:12.079> need<00:41:12.280> to<00:41:12.760> flash 00:41:13.390 --> 00:41:13.400 align:start position:0% uh with the OS you just need to flash 00:41:13.400 --> 00:41:17.069 align:start position:0% uh with the OS you just need to flash the<00:41:13.560> SD<00:41:13.960> again<00:41:14.960> and<00:41:15.160> you<00:41:15.440> put<00:41:15.800> a<00:41:16.040> new<00:41:16.520> SD<00:41:16.920> and 00:41:17.069 --> 00:41:17.079 align:start position:0% the SD again and you put a new SD and 00:41:17.079 --> 00:41:19.550 align:start position:0% the SD again and you put a new SD and you<00:41:17.359> have<00:41:17.680> exactly<00:41:18.119> the<00:41:18.280> same<00:41:18.839> uh<00:41:19.079> system<00:41:19.440> that 00:41:19.550 --> 00:41:19.560 align:start position:0% you have exactly the same uh system that 00:41:19.560 --> 00:41:22.270 align:start position:0% you have exactly the same uh system that you<00:41:19.720> have<00:41:20.079> previously<00:41:21.079> and<00:41:21.400> for<00:41:21.839> for<00:41:22.000> example 00:41:22.270 --> 00:41:22.280 align:start position:0% you have previously and for for example 00:41:22.280 --> 00:41:25.750 align:start position:0% you have previously and for for example for<00:41:22.480> upgrading<00:41:23.079> to<00:41:23.319> a<00:41:23.520> new<00:41:23.960> untu<00:41:24.480> version<00:41:25.040> same 00:41:25.750 --> 00:41:25.760 align:start position:0% for upgrading to a new untu version same 00:41:25.760 --> 00:41:30.309 align:start position:0% for upgrading to a new untu version same you<00:41:26.040> put<00:41:26.240> out<00:41:26.520> the<00:41:27.319> micro<00:41:27.640> SD<00:41:28.200> you<00:41:28.880> flash<00:41:29.240> a<00:41:29.400> new 00:41:30.309 --> 00:41:30.319 align:start position:0% you put out the micro SD you flash a new 00:41:30.319 --> 00:41:33.270 align:start position:0% you put out the micro SD you flash a new uh<00:41:30.680> image<00:41:31.680> and<00:41:31.800> you<00:41:32.040> have<00:41:32.359> everything<00:41:32.760> updated 00:41:33.270 --> 00:41:33.280 align:start position:0% uh image and you have everything updated 00:41:33.280 --> 00:41:37.670 align:start position:0% uh image and you have everything updated including<00:41:34.079> clients<00:41:35.079> uh<00:41:35.839> and<00:41:36.680> maybe<00:41:37.200> uh<00:41:37.400> it's 00:41:37.670 --> 00:41:37.680 align:start position:0% including clients uh and maybe uh it's 00:41:37.680 --> 00:41:40.510 align:start position:0% including clients uh and maybe uh it's question<00:41:38.040> of<00:41:38.800> five<00:41:39.160> 10<00:41:39.359> minutes<00:41:39.960> yes<00:41:40.400> you 00:41:40.510 --> 00:41:40.520 align:start position:0% question of five 10 minutes yes you 00:41:40.520 --> 00:41:43.829 align:start position:0% question of five 10 minutes yes you don't<00:41:40.760> have<00:41:40.920> to<00:41:41.160> do<00:41:41.400> an<00:41:41.640> up<00:41:42.599> this<00:41:42.839> upgrade<00:41:43.560> and 00:41:43.829 --> 00:41:43.839 align:start position:0% don't have to do an up this upgrade and 00:41:43.839 --> 00:41:46.349 align:start position:0% don't have to do an up this upgrade and all<00:41:44.319> this<00:41:44.839> the<00:41:44.960> main<00:41:45.119> idea<00:41:45.400> is<00:41:45.640> the<00:41:45.839> operating 00:41:46.349 --> 00:41:46.359 align:start position:0% all this the main idea is the operating 00:41:46.359 --> 00:41:48.990 align:start position:0% all this the main idea is the operating system<00:41:46.720> is<00:41:46.839> in<00:41:47.000> the<00:41:47.160> SD<00:41:47.440> card<00:41:48.240> and<00:41:48.680> you<00:41:48.839> can 00:41:48.990 --> 00:41:49.000 align:start position:0% system is in the SD card and you can 00:41:49.000 --> 00:41:50.990 align:start position:0% system is in the SD card and you can change<00:41:49.280> it<00:41:49.680> whenever<00:41:50.040> you<00:41:50.160> can<00:41:50.560> but<00:41:50.720> all<00:41:50.839> the 00:41:50.990 --> 00:41:51.000 align:start position:0% change it whenever you can but all the 00:41:51.000 --> 00:41:53.190 align:start position:0% change it whenever you can but all the configuration<00:41:51.640> is<00:41:51.760> in<00:41:52.000> the<00:41:52.520> in<00:41:52.640> the<00:41:52.800> internal 00:41:53.190 --> 00:41:53.200 align:start position:0% configuration is in the in the internal 00:41:53.200 --> 00:41:55.510 align:start position:0% configuration is in the in the internal dis<00:41:53.560> the<00:41:53.680> MBM<00:41:54.280> dis<00:41:54.800> all<00:41:54.960> the<00:41:55.079> configuration 00:41:55.510 --> 00:41:55.520 align:start position:0% dis the MBM dis all the configuration 00:41:55.520 --> 00:41:59.150 align:start position:0% dis the MBM dis all the configuration need<00:41:55.760> is<00:41:56.000> here<00:41:56.280> so<00:41:56.960> you<00:41:57.720> you<00:41:58.440> you<00:41:58.720> are<00:41:58.920> not 00:41:59.150 --> 00:41:59.160 align:start position:0% need is here so you you you are not 00:41:59.160 --> 00:42:00.790 align:start position:0% need is here so you you you are not going<00:41:59.319> to<00:41:59.480> lose<00:41:59.760> anything<00:42:00.200> if<00:42:00.319> you<00:42:00.520> change 00:42:00.790 --> 00:42:00.800 align:start position:0% going to lose anything if you change 00:42:00.800 --> 00:42:02.190 align:start position:0% going to lose anything if you change your<00:42:00.960> operating<00:42:01.359> system<00:42:01.640> you<00:42:01.720> could<00:42:01.920> try 00:42:02.190 --> 00:42:02.200 align:start position:0% your operating system you could try 00:42:02.200 --> 00:42:05.710 align:start position:0% your operating system you could try another<00:42:02.560> one<00:42:03.359> you<00:42:03.640> could<00:42:04.640> upgrade<00:42:05.040> it<00:42:05.359> or 00:42:05.710 --> 00:42:05.720 align:start position:0% another one you could upgrade it or 00:42:05.720 --> 00:42:08.069 align:start position:0% another one you could upgrade it or downgrade<00:42:06.160> it<00:42:06.359> on<00:42:06.920> maybe<00:42:07.240> you<00:42:07.480> have<00:42:07.640> a<00:42:07.800> problem 00:42:08.069 --> 00:42:08.079 align:start position:0% downgrade it on maybe you have a problem 00:42:08.079 --> 00:42:10.470 align:start position:0% downgrade it on maybe you have a problem with<00:42:08.200> the<00:42:08.280> SD<00:42:08.560> card<00:42:09.280> if<00:42:09.400> the<00:42:09.520> SD<00:42:09.760> card<00:42:09.960> is<00:42:10.119> not 00:42:10.470 --> 00:42:10.480 align:start position:0% with the SD card if the SD card is not 00:42:10.480 --> 00:42:12.550 align:start position:0% with the SD card if the SD card is not good<00:42:11.160> usually<00:42:11.480> you<00:42:11.680> have<00:42:11.880> problems<00:42:12.240> writing 00:42:12.550 --> 00:42:12.560 align:start position:0% good usually you have problems writing 00:42:12.560 --> 00:42:15.829 align:start position:0% good usually you have problems writing the<00:42:12.640> SD<00:42:12.880> card<00:42:13.079> you<00:42:13.280> will<00:42:13.480> see<00:42:14.040> in<00:42:14.160> your<00:42:14.839> logs 00:42:15.829 --> 00:42:15.839 align:start position:0% the SD card you will see in your logs 00:42:15.839 --> 00:42:18.190 align:start position:0% the SD card you will see in your logs the<00:42:16.119> the<00:42:16.640> system<00:42:17.000> try<00:42:17.319> to<00:42:17.480> writing<00:42:17.880> the<00:42:17.960> SD 00:42:18.190 --> 00:42:18.200 align:start position:0% the the system try to writing the SD 00:42:18.200 --> 00:42:21.150 align:start position:0% the the system try to writing the SD card<00:42:18.480> some<00:42:19.079> small<00:42:19.359> FES<00:42:19.720> and<00:42:19.880> you<00:42:20.040> have<00:42:20.720> some 00:42:21.150 --> 00:42:21.160 align:start position:0% card some small FES and you have some 00:42:21.160 --> 00:42:22.870 align:start position:0% card some small FES and you have some briting<00:42:21.480> problems<00:42:22.000> prob<00:42:22.240> the<00:42:22.359> SD<00:42:22.599> card<00:42:22.760> is 00:42:22.870 --> 00:42:22.880 align:start position:0% briting problems prob the SD card is 00:42:22.880 --> 00:42:25.309 align:start position:0% briting problems prob the SD card is wrong<00:42:23.160> or<00:42:24.160> something<00:42:24.440> happens<00:42:24.720> to<00:42:24.800> me<00:42:25.040> that<00:42:25.200> I 00:42:25.309 --> 00:42:25.319 align:start position:0% wrong or something happens to me that I 00:42:25.319 --> 00:42:29.470 align:start position:0% wrong or something happens to me that I put<00:42:25.520> the<00:42:25.599> SD<00:42:25.839> card<00:42:26.079> in<00:42:26.240> the<00:42:26.359> wrong<00:42:26.559> side<00:42:26.800> and 00:42:29.470 --> 00:42:29.480 align:start position:0% 00:42:29.480 --> 00:42:32.030 align:start position:0% scratch<00:42:29.880> it<00:42:30.119> and<00:42:30.319> at<00:42:30.480> the<00:42:30.599> end<00:42:31.000> is<00:42:31.319> not<00:42:31.760> not 00:42:32.030 --> 00:42:32.040 align:start position:0% scratch it and at the end is not not 00:42:32.040 --> 00:42:33.950 align:start position:0% scratch it and at the end is not not working<00:42:32.599> okay<00:42:32.960> that<00:42:33.160> at<00:42:33.240> the<00:42:33.359> end<00:42:33.480> you<00:42:33.599> only<00:42:33.839> to 00:42:33.950 --> 00:42:33.960 align:start position:0% working okay that at the end you only to 00:42:33.960 --> 00:42:36.589 align:start position:0% working okay that at the end you only to have<00:42:34.079> to<00:42:34.240> break<00:42:34.559> the<00:42:34.760> iMat<00:42:35.200> again<00:42:36.079> put<00:42:36.280> it<00:42:36.440> in 00:42:36.589 --> 00:42:36.599 align:start position:0% have to break the iMat again put it in 00:42:36.599 --> 00:42:39.030 align:start position:0% have to break the iMat again put it in the<00:42:36.880> device<00:42:37.200> and<00:42:37.359> you<00:42:37.480> are<00:42:37.680> going<00:42:37.880> good<00:42:38.119> go 00:42:39.030 --> 00:42:39.040 align:start position:0% the device and you are going good go 00:42:39.040 --> 00:42:42.270 align:start position:0% the device and you are going good go restart<00:42:39.640> and<00:42:40.040> it's<00:42:40.319> okay<00:42:41.280> it's<00:42:41.480> now<00:42:41.800> right<00:42:42.079> in 00:42:42.270 --> 00:42:42.280 align:start position:0% restart and it's okay it's now right in 00:42:42.280 --> 00:42:46.950 align:start position:0% restart and it's okay it's now right in the<00:42:42.880> swap<00:42:43.880> yeah<00:42:44.640> uh<00:42:45.160> it<00:42:45.319> takes<00:42:45.559> some<00:42:45.800> time<00:42:46.319> uh<00:42:46.480> s 00:42:46.950 --> 00:42:46.960 align:start position:0% the swap yeah uh it takes some time uh s 00:42:46.960 --> 00:42:49.750 align:start position:0% the swap yeah uh it takes some time uh s partition<00:42:47.960> uh<00:42:48.280> on<00:42:48.640> on<00:42:48.839> on<00:42:49.000> this<00:42:49.200> very<00:42:49.480> device 00:42:49.750 --> 00:42:49.760 align:start position:0% partition uh on on on this very device 00:42:49.760 --> 00:42:52.549 align:start position:0% partition uh on on on this very device is<00:42:49.920> the<00:42:50.200> 32<00:42:50.680> gigs<00:42:51.160> version<00:42:52.160> uh<00:42:52.319> you're 00:42:52.549 --> 00:42:52.559 align:start position:0% is the 32 gigs version uh you're 00:42:52.559 --> 00:42:55.589 align:start position:0% is the 32 gigs version uh you're probably<00:42:53.240> you're<00:42:53.480> not<00:42:53.680> going<00:42:53.839> to<00:42:54.040> use<00:42:54.599> swap 00:42:55.589 --> 00:42:55.599 align:start position:0% probably you're not going to use swap 00:42:55.599 --> 00:43:00.829 align:start position:0% probably you're not going to use swap unless<00:42:56.440> you<00:42:56.880> are<00:42:57.280> using<00:42:58.079> teu<00:42:59.280> because<00:43:00.280> Bas 00:43:00.829 --> 00:43:00.839 align:start position:0% unless you are using teu because Bas 00:43:00.839 --> 00:43:04.470 align:start position:0% unless you are using teu because Bas maybe<00:43:01.079> Aron<00:43:01.520> and<00:43:01.960> may<00:43:02.640> yeah<00:43:03.000> because<00:43:04.000> most<00:43:04.200> of 00:43:04.470 --> 00:43:04.480 align:start position:0% maybe Aron and may yeah because most of 00:43:04.480 --> 00:43:07.270 align:start position:0% maybe Aron and may yeah because most of the<00:43:04.680> the<00:43:04.760> other<00:43:04.960> clients<00:43:05.359> are<00:43:05.800> less<00:43:06.559> uh<00:43:06.680> run 00:43:07.270 --> 00:43:07.280 align:start position:0% the the other clients are less uh run 00:43:07.280 --> 00:43:11.190 align:start position:0% the the other clients are less uh run hungry<00:43:08.280> but<00:43:08.960> uh<00:43:09.960> we<00:43:10.119> are<00:43:10.400> at<00:43:10.520> the<00:43:10.640> end<00:43:10.880> we<00:43:11.040> are 00:43:11.190 --> 00:43:11.200 align:start position:0% hungry but uh we are at the end we are 00:43:11.200 --> 00:43:15.309 align:start position:0% hungry but uh we are at the end we are using<00:43:11.520> that<00:43:11.760> we<00:43:11.880> use<00:43:12.240> a<00:43:12.880> a<00:43:13.599> demon<00:43:14.079> Lake<00:43:14.760> name<00:43:15.000> it 00:43:15.309 --> 00:43:15.319 align:start position:0% using that we use a a demon Lake name it 00:43:15.319 --> 00:43:21.710 align:start position:0% using that we use a a demon Lake name it d<00:43:15.839> p<00:43:16.240> h<00:43:16.880> Ys<00:43:17.880> that<00:43:18.040> is<00:43:18.680> a<00:43:19.680> uh<00:43:20.480> a<00:43:20.599> Linux<00:43:21.000> demon<00:43:21.480> that 00:43:21.710 --> 00:43:21.720 align:start position:0% d p h Ys that is a uh a Linux demon that 00:43:21.720 --> 00:43:23.390 align:start position:0% d p h Ys that is a uh a Linux demon that creates<00:43:22.280> swap<00:43:22.680> on 00:43:23.390 --> 00:43:23.400 align:start position:0% creates swap on 00:43:23.400 --> 00:43:27.430 align:start position:0% creates swap on demand<00:43:24.400> so<00:43:25.240> uh<00:43:25.599> uh<00:43:26.359> if<00:43:26.520> you<00:43:26.680> have<00:43:26.880> SP<00:43:27.119> space<00:43:27.319> in 00:43:27.430 --> 00:43:27.440 align:start position:0% demand so uh uh if you have SP space in 00:43:27.440 --> 00:43:29.710 align:start position:0% demand so uh uh if you have SP space in the<00:43:27.559> dis<00:43:28.440> you<00:43:28.559> will<00:43:28.800> creating<00:43:29.240> more<00:43:29.400> and<00:43:29.559> more 00:43:29.710 --> 00:43:29.720 align:start position:0% the dis you will creating more and more 00:43:29.720 --> 00:43:31.910 align:start position:0% the dis you will creating more and more swap<00:43:30.079> in<00:43:30.200> demand<00:43:30.559> and<00:43:30.720> you<00:43:30.839> are<00:43:31.079> Avy<00:43:31.440> to<00:43:31.680> own 00:43:31.910 --> 00:43:31.920 align:start position:0% swap in demand and you are Avy to own 00:43:31.920 --> 00:43:34.870 align:start position:0% swap in demand and you are Avy to own Killers<00:43:32.520> the<00:43:32.680> process<00:43:33.319> that's<00:43:33.880> uh<00:43:34.559> I<00:43:34.680> think 00:43:34.870 --> 00:43:34.880 align:start position:0% Killers the process that's uh I think 00:43:34.880 --> 00:43:37.710 align:start position:0% Killers the process that's uh I think it's<00:43:35.079> a<00:43:35.240> good<00:43:36.040> good<00:43:36.240> idea<00:43:36.559> in<00:43:36.760> this<00:43:37.400> these 00:43:37.710 --> 00:43:37.720 align:start position:0% it's a good good idea in this these 00:43:37.720 --> 00:43:41.030 align:start position:0% it's a good good idea in this these devices<00:43:38.200> that<00:43:38.400> they're<00:43:39.200> uh<00:43:39.559> small 00:43:41.030 --> 00:43:41.040 align:start position:0% devices that they're uh small 00:43:41.040 --> 00:43:43.470 align:start position:0% devices that they're uh small and<00:43:42.040> they<00:43:42.119> are<00:43:42.280> powerful<00:43:42.680> but<00:43:42.960> they<00:43:43.040> are<00:43:43.200> small 00:43:43.470 --> 00:43:43.480 align:start position:0% and they are powerful but they are small 00:43:43.480 --> 00:43:46.150 align:start position:0% and they are powerful but they are small and<00:43:44.040> you<00:43:44.280> probably<00:43:44.559> will<00:43:44.760> need<00:43:45.319> uh<00:43:45.520> more<00:43:45.760> Swap 00:43:46.150 --> 00:43:46.160 align:start position:0% and you probably will need uh more Swap 00:43:46.160 --> 00:43:49.150 align:start position:0% and you probably will need uh more Swap and<00:43:46.520> you<00:43:46.640> are<00:43:47.079> this<00:43:47.200> is<00:43:47.400> dynamic<00:43:47.800> swap<00:43:48.240> so<00:43:48.720> it's 00:43:49.150 --> 00:43:49.160 align:start position:0% and you are this is dynamic swap so it's 00:43:49.160 --> 00:43:52.030 align:start position:0% and you are this is dynamic swap so it's I<00:43:49.280> think<00:43:49.559> we<00:43:49.880> we<00:43:50.040> think<00:43:50.240> it's<00:43:50.359> a<00:43:50.520> good 00:43:52.030 --> 00:43:52.040 align:start position:0% I think we we think it's a good 00:43:52.040 --> 00:43:55.190 align:start position:0% I think we we think it's a good idea<00:43:53.040> um<00:43:53.599> now<00:43:53.800> this<00:43:54.079> the<00:43:54.200> process<00:43:54.480> to<00:43:54.640> G<00:43:54.880> swap 00:43:55.190 --> 00:43:55.200 align:start position:0% idea um now this the process to G swap 00:43:55.200 --> 00:43:59.750 align:start position:0% idea um now this the process to G swap we<00:43:55.400> changed<00:43:56.000> the<00:43:57.480> some<00:43:58.240> kernel<00:43:59.040> variable 00:43:59.750 --> 00:43:59.760 align:start position:0% we changed the some kernel variable 00:43:59.760 --> 00:44:02.030 align:start position:0% we changed the some kernel variable variables<00:44:00.240> to<00:44:00.520> the<00:44:01.119> for<00:44:01.280> the<00:44:01.400> swappiness<00:44:01.920> in 00:44:02.030 --> 00:44:02.040 align:start position:0% variables to the for the swappiness in 00:44:02.040 --> 00:44:05.589 align:start position:0% variables to the for the swappiness in order<00:44:02.319> to<00:44:02.920> to<00:44:03.119> tell<00:44:03.359> the<00:44:03.760> kernel<00:44:04.760> uh<00:44:04.960> that<00:44:05.240> use 00:44:05.589 --> 00:44:05.599 align:start position:0% order to to tell the kernel uh that use 00:44:05.599 --> 00:44:09.190 align:start position:0% order to to tell the kernel uh that use swap<00:44:06.160> in<00:44:06.319> a<00:44:06.559> less<00:44:06.800> aggressive<00:44:07.720> way<00:44:08.720> we<00:44:08.880> are 00:44:09.190 --> 00:44:09.200 align:start position:0% swap in a less aggressive way we are 00:44:09.200 --> 00:44:10.950 align:start position:0% swap in a less aggressive way we are trying<00:44:09.480> to<00:44:09.640> avoid<00:44:10.040> write<00:44:10.359> anything<00:44:10.640> to<00:44:10.839> the 00:44:10.950 --> 00:44:10.960 align:start position:0% trying to avoid write anything to the 00:44:10.960 --> 00:44:13.670 align:start position:0% trying to avoid write anything to the dis<00:44:11.359> so<00:44:11.720> we're<00:44:12.079> trying<00:44:12.359> to<00:44:12.760> to<00:44:12.880> use<00:44:13.160> swap<00:44:13.480> in 00:44:13.670 --> 00:44:13.680 align:start position:0% dis so we're trying to to use swap in 00:44:13.680 --> 00:44:16.829 align:start position:0% dis so we're trying to to use swap in the<00:44:14.119> in<00:44:14.200> a<00:44:14.359> less<00:44:14.559> aggressive<00:44:14.960> way<00:44:15.680> and<00:44:15.920> we 00:44:16.829 --> 00:44:16.839 align:start position:0% the in a less aggressive way and we 00:44:16.839 --> 00:44:20.030 align:start position:0% the in a less aggressive way and we install<00:44:17.839> uh<00:44:18.119> our<00:44:18.480> repository<00:44:19.280> we<00:44:19.480> maintain<00:44:19.839> of 00:44:20.030 --> 00:44:20.040 align:start position:0% install uh our repository we maintain of 00:44:20.040 --> 00:44:22.150 align:start position:0% install uh our repository we maintain of the<00:44:20.160> software<00:44:20.680> all<00:44:20.920> the<00:44:21.480> the<00:44:21.640> ethereum 00:44:22.150 --> 00:44:22.160 align:start position:0% the software all the the ethereum 00:44:22.160 --> 00:44:23.630 align:start position:0% the software all the the ethereum clients<00:44:22.520> all<00:44:22.680> the<00:44:22.760> ethereum<00:44:23.119> level<00:44:23.319> one<00:44:23.520> and 00:44:23.630 --> 00:44:23.640 align:start position:0% clients all the ethereum level one and 00:44:23.640 --> 00:44:27.750 align:start position:0% clients all the ethereum level one and level<00:44:23.839> two<00:44:24.040> clients<00:44:25.040> in<00:44:25.240> our<00:44:25.640> main<00:44:26.160> or<00:44:26.880> uh 00:44:27.750 --> 00:44:27.760 align:start position:0% level two clients in our main or uh 00:44:27.760 --> 00:44:30.790 align:start position:0% level two clients in our main or uh devian<00:44:28.200> repository<00:44:28.880> this<00:44:29.160> AP<00:44:29.800> eum 00:44:30.790 --> 00:44:30.800 align:start position:0% devian repository this AP eum 00:44:30.800 --> 00:44:34.109 align:start position:0% devian repository this AP eum arm.com<00:44:31.800> it's<00:44:32.160> Public<00:44:32.559> Access<00:44:32.960> you<00:44:33.119> can 00:44:34.109 --> 00:44:34.119 align:start position:0% arm.com it's Public Access you can 00:44:34.119 --> 00:44:35.950 align:start position:0% arm.com it's Public Access you can clients<00:44:34.720> there<00:44:34.800> are<00:44:34.960> deian<00:44:35.319> clients<00:44:35.760> you're 00:44:35.950 --> 00:44:35.960 align:start position:0% clients there are deian clients you're 00:44:35.960 --> 00:44:40.990 align:start position:0% clients there are deian clients you're going<00:44:36.119> to<00:44:36.280> St<00:44:37.280> all<00:44:37.599> the<00:44:38.160> all<00:44:38.359> the<00:44:39.119> devices<00:44:40.119> but 00:44:40.990 --> 00:44:41.000 align:start position:0% going to St all the all the devices but 00:44:41.000 --> 00:44:44.990 align:start position:0% going to St all the all the devices but uh<00:44:41.800> we<00:44:42.040> provideing<00:44:42.599> our<00:44:42.880> gab<00:44:43.720> the<00:44:43.880> tools<00:44:44.880> that 00:44:44.990 --> 00:44:45.000 align:start position:0% uh we provideing our gab the tools that 00:44:45.000 --> 00:44:46.750 align:start position:0% uh we provideing our gab the tools that you<00:44:45.119> need<00:44:45.359> to<00:44:45.559> write<00:44:45.800> it<00:44:46.079> because<00:44:46.400> you<00:44:46.520> don't 00:44:46.750 --> 00:44:46.760 align:start position:0% you need to write it because you don't 00:44:46.760 --> 00:44:48.309 align:start position:0% you need to write it because you don't have<00:44:46.880> to<00:44:47.040> trust 00:44:48.309 --> 00:44:48.319 align:start position:0% have to trust 00:44:48.319 --> 00:44:52.190 align:start position:0% have to trust us<00:44:49.319> as<00:44:49.440> you<00:44:49.559> can<00:44:49.760> see<00:44:50.480> uh<00:44:51.079> we<00:44:51.280> use<00:44:51.520> the<00:44:51.640> binaries 00:44:52.190 --> 00:44:52.200 align:start position:0% us as you can see uh we use the binaries 00:44:52.200 --> 00:44:55.390 align:start position:0% us as you can see uh we use the binaries provided<00:44:52.640> by<00:44:53.040> the<00:44:53.359> teams<00:44:54.240> the<00:44:54.400> client<00:44:54.720> teams 00:44:55.390 --> 00:44:55.400 align:start position:0% provided by the teams the client teams 00:44:55.400 --> 00:44:57.549 align:start position:0% provided by the teams the client teams directly<00:44:56.079> if<00:44:56.160> you<00:44:56.280> CL<00:44:56.480> our<00:44:56.640> Repository<00:44:57.440> there 00:44:57.549 --> 00:44:57.559 align:start position:0% directly if you CL our Repository there 00:44:57.559 --> 00:44:58.470 align:start position:0% directly if you CL our Repository there is 00:44:58.470 --> 00:44:58.480 align:start position:0% is 00:44:58.480 --> 00:45:01.790 align:start position:0% is a<00:44:59.480> a<00:45:00.280> vagrant 00:45:01.790 --> 00:45:01.800 align:start position:0% a a vagrant 00:45:01.800 --> 00:45:04.309 align:start position:0% a a vagrant machine<00:45:02.800> prepared<00:45:03.240> to<00:45:03.599> compile<00:45:03.960> of<00:45:04.160> the 00:45:04.309 --> 00:45:04.319 align:start position:0% machine prepared to compile of the 00:45:04.319 --> 00:45:07.309 align:start position:0% machine prepared to compile of the clients<00:45:05.040> it's<00:45:05.200> a<00:45:05.319> make<00:45:05.599> file<00:45:05.960> that<00:45:06.119> you<00:45:06.880> don't 00:45:07.309 --> 00:45:07.319 align:start position:0% clients it's a make file that you don't 00:45:07.319 --> 00:45:08.430 align:start position:0% clients it's a make file that you don't the 00:45:08.430 --> 00:45:08.440 align:start position:0% the 00:45:08.440 --> 00:45:11.030 align:start position:0% the repository<00:45:09.440> uh<00:45:09.680> run<00:45:10.000> into<00:45:10.280> a<00:45:10.559> directory 00:45:11.030 --> 00:45:11.040 align:start position:0% repository uh run into a directory 00:45:11.040 --> 00:45:15.390 align:start position:0% repository uh run into a directory called<00:45:11.359> ethereum<00:45:11.880> arm<00:45:12.880> and<00:45:13.880> uh<00:45:14.240> make<00:45:14.960> and<00:45:15.119> will 00:45:15.390 --> 00:45:15.400 align:start position:0% called ethereum arm and uh make and will 00:45:15.400 --> 00:45:17.069 align:start position:0% called ethereum arm and uh make and will compile<00:45:15.800> all<00:45:15.960> the<00:45:16.119> clients<00:45:16.400> for<00:45:16.559> you<00:45:16.760> they 00:45:17.069 --> 00:45:17.079 align:start position:0% compile all the clients for you they 00:45:17.079 --> 00:45:19.270 align:start position:0% compile all the clients for you they compile<00:45:17.480> or<00:45:17.680> create<00:45:18.319> all<00:45:18.599> the<00:45:18.839> the<00:45:18.960> clients 00:45:19.270 --> 00:45:19.280 align:start position:0% compile or create all the the clients 00:45:19.280 --> 00:45:22.069 align:start position:0% compile or create all the the clients for<00:45:19.440> you<00:45:19.839> and<00:45:20.000> you<00:45:20.240> don't<00:45:20.480> have<00:45:20.599> to<00:45:20.760> trust<00:45:21.200> us 00:45:22.069 --> 00:45:22.079 align:start position:0% for you and you don't have to trust us 00:45:22.079 --> 00:45:24.910 align:start position:0% for you and you don't have to trust us uh<00:45:22.359> you<00:45:23.040> could<00:45:23.319> use<00:45:23.640> or<00:45:23.920> Dean<00:45:24.240> repository<00:45:24.760> but 00:45:24.910 --> 00:45:24.920 align:start position:0% uh you could use or Dean repository but 00:45:24.920 --> 00:45:27.549 align:start position:0% uh you could use or Dean repository but if<00:45:25.040> you<00:45:25.200> don't<00:45:25.400> want<00:45:25.720> because<00:45:26.359> okay<00:45:27.040> I<00:45:27.160> want<00:45:27.359> to 00:45:27.549 --> 00:45:27.559 align:start position:0% if you don't want because okay I want to 00:45:27.559 --> 00:45:29.549 align:start position:0% if you don't want because okay I want to create<00:45:27.880> my<00:45:28.040> own<00:45:28.280> packages<00:45:28.760> we<00:45:29.079> provide<00:45:29.400> all 00:45:29.549 --> 00:45:29.559 align:start position:0% create my own packages we provide all 00:45:29.559 --> 00:45:31.589 align:start position:0% create my own packages we provide all the<00:45:29.680> tools<00:45:30.119> for<00:45:30.359> create<00:45:30.720> your<00:45:31.040> your<00:45:31.200> deant 00:45:31.589 --> 00:45:31.599 align:start position:0% the tools for create your your deant 00:45:31.599 --> 00:45:35.069 align:start position:0% the tools for create your your deant packages<00:45:32.400> and<00:45:33.400> uh<00:45:34.280> probably<00:45:34.599> it's<00:45:34.680> a<00:45:34.880> good 00:45:35.069 --> 00:45:35.079 align:start position:0% packages and uh probably it's a good 00:45:35.079 --> 00:45:38.190 align:start position:0% packages and uh probably it's a good idea<00:45:35.359> to<00:45:35.880> to<00:45:36.040> do<00:45:36.480> like<00:45:36.680> this<00:45:36.920> it's<00:45:37.520> harder<00:45:38.000> you 00:45:38.190 --> 00:45:38.200 align:start position:0% idea to to do like this it's harder you 00:45:38.200 --> 00:45:41.670 align:start position:0% idea to to do like this it's harder you have<00:45:38.319> to<00:45:38.480> know<00:45:38.800> a<00:45:39.200> bit<00:45:39.480> more<00:45:40.160> about<00:45:40.960> Linux<00:45:41.400> and 00:45:41.670 --> 00:45:41.680 align:start position:0% have to know a bit more about Linux and 00:45:41.680 --> 00:45:43.670 align:start position:0% have to know a bit more about Linux and devian<00:45:42.000> system<00:45:42.280> but<00:45:42.400> it's<00:45:42.559> not<00:45:42.760> so<00:45:43.000> hard<00:45:43.240> is 00:45:43.670 --> 00:45:43.680 align:start position:0% devian system but it's not so hard is 00:45:43.680 --> 00:45:45.710 align:start position:0% devian system but it's not so hard is only<00:45:43.960> it's<00:45:44.079> a<00:45:44.240> make<00:45:44.480> file<00:45:44.760> that<00:45:44.960> takes<00:45:45.280> care<00:45:45.520> of 00:45:45.710 --> 00:45:45.720 align:start position:0% only it's a make file that takes care of 00:45:45.720 --> 00:45:47.589 align:start position:0% only it's a make file that takes care of everything<00:45:46.200> and<00:45:46.359> you<00:45:46.599> could<00:45:46.800> look<00:45:47.319> of<00:45:47.480> the 00:45:47.589 --> 00:45:47.599 align:start position:0% everything and you could look of the 00:45:47.599 --> 00:45:51.870 align:start position:0% everything and you could look of the code<00:45:47.839> is<00:45:48.160> nothing<00:45:48.599> very<00:45:49.200> very<00:45:50.319> um<00:45:51.319> uh<00:45:51.480> hard<00:45:51.720> to 00:45:51.870 --> 00:45:51.880 align:start position:0% code is nothing very very um uh hard to 00:45:51.880 --> 00:45:54.030 align:start position:0% code is nothing very very um uh hard to do<00:45:52.200> this<00:45:52.440> it's<00:45:52.680> quite 00:45:54.030 --> 00:45:54.040 align:start position:0% do this it's quite 00:45:54.040 --> 00:45:56.670 align:start position:0% do this it's quite easy<00:45:55.040> well<00:45:55.280> and<00:45:55.480> now<00:45:55.839> is<00:45:56.079> we<00:45:56.160> are<00:45:56.319> going<00:45:56.480> to 00:45:56.670 --> 00:45:56.680 align:start position:0% easy well and now is we are going to 00:45:56.680 --> 00:45:58.710 align:start position:0% easy well and now is we are going to start<00:45:57.359> all 00:45:58.710 --> 00:45:58.720 align:start position:0% start all 00:45:58.720 --> 00:46:01.630 align:start position:0% start all the<00:45:59.720> the<00:46:00.079> e<00:46:00.520> software<00:46:00.880> that<00:46:01.000> we<00:46:01.119> support<00:46:01.520> you 00:46:01.630 --> 00:46:01.640 align:start position:0% the the e software that we support you 00:46:01.640 --> 00:46:04.549 align:start position:0% the the e software that we support you could<00:46:01.800> see<00:46:02.119> here<00:46:02.440> B<00:46:02.920> Aron 00:46:04.549 --> 00:46:04.559 align:start position:0% could see here B Aron 00:46:04.559 --> 00:46:07.510 align:start position:0% could see here B Aron G<00:46:05.559> all<00:46:05.720> the<00:46:05.880> dependencies<00:46:06.599> around<00:46:07.079> nether 00:46:07.510 --> 00:46:07.520 align:start position:0% G all the dependencies around nether 00:46:07.520 --> 00:46:10.790 align:start position:0% G all the dependencies around nether mind<00:46:08.079> all<00:46:08.559> all<00:46:09.160> the<00:46:10.160> the<00:46:10.280> software<00:46:10.640> that<00:46:10.720> you 00:46:10.790 --> 00:46:10.800 align:start position:0% mind all all the the software that you 00:46:10.800 --> 00:46:12.670 align:start position:0% mind all all the the software that you will<00:46:10.960> need<00:46:11.160> to<00:46:11.319> create<00:46:11.520> an<00:46:11.640> not<00:46:11.880> that<00:46:12.040> home<00:46:12.520> is 00:46:12.670 --> 00:46:12.680 align:start position:0% will need to create an not that home is 00:46:12.680 --> 00:46:15.190 align:start position:0% will need to create an not that home is going<00:46:12.960> to<00:46:13.079> start<00:46:13.400> here<00:46:13.559> in<00:46:13.760> the<00:46:14.079> proess<00:46:14.880> and 00:46:15.190 --> 00:46:15.200 align:start position:0% going to start here in the proess and 00:46:15.200 --> 00:46:18.990 align:start position:0% going to start here in the proess and when<00:46:15.400> you<00:46:15.640> start<00:46:16.079> an<00:46:16.880> image<00:46:17.520> you<00:46:17.680> could<00:46:18.000> choose 00:46:18.990 --> 00:46:19.000 align:start position:0% when you start an image you could choose 00:46:19.000 --> 00:46:21.390 align:start position:0% when you start an image you could choose whatever<00:46:19.440> your<00:46:19.599> client<00:46:20.040> you<00:46:20.280> you<00:46:20.400> want<00:46:20.520> to<00:46:20.680> use 00:46:21.390 --> 00:46:21.400 align:start position:0% whatever your client you you want to use 00:46:21.400 --> 00:46:25.030 align:start position:0% whatever your client you you want to use so<00:46:21.599> at<00:46:21.760> the<00:46:21.880> end<00:46:22.440> it's<00:46:22.720> quite<00:46:22.960> easy<00:46:23.920> uh<00:46:24.079> you 00:46:25.030 --> 00:46:25.040 align:start position:0% so at the end it's quite easy uh you 00:46:25.040 --> 00:46:28.829 align:start position:0% so at the end it's quite easy uh you Runway<00:46:25.480> we<00:46:25.720> choose<00:46:26.000> to<00:46:26.280> random<00:46:27.000> clients<00:46:28.000> it's 00:46:28.829 --> 00:46:28.839 align:start position:0% Runway we choose to random clients it's 00:46:28.839 --> 00:46:32.390 align:start position:0% Runway we choose to random clients it's still<00:46:29.640> stalling<00:46:30.640> uh<00:46:31.000> te<00:46:31.440> right<00:46:31.599> now<00:46:31.960> that's 00:46:32.390 --> 00:46:32.400 align:start position:0% still stalling uh te right now that's 00:46:32.400 --> 00:46:34.870 align:start position:0% still stalling uh te right now that's the<00:46:32.680> one<00:46:32.839> of<00:46:32.960> the<00:46:33.079> heaviest 00:46:34.870 --> 00:46:34.880 align:start position:0% the one of the heaviest 00:46:34.880 --> 00:46:37.150 align:start position:0% the one of the heaviest clients<00:46:35.880> and<00:46:36.079> at<00:46:36.200> the<00:46:36.280> end<00:46:36.480> of<00:46:36.599> the<00:46:36.720> script<00:46:37.079> it 00:46:37.150 --> 00:46:37.160 align:start position:0% clients and at the end of the script it 00:46:37.160 --> 00:46:41.069 align:start position:0% clients and at the end of the script it will<00:46:37.359> reboot<00:46:38.040> and<00:46:38.880> hopefully<00:46:39.880> it<00:46:40.040> will<00:46:40.520> start 00:46:41.069 --> 00:46:41.079 align:start position:0% will reboot and hopefully it will start 00:46:41.079 --> 00:46:43.470 align:start position:0% will reboot and hopefully it will start and<00:46:41.359> here<00:46:41.599> on<00:46:41.720> our<00:46:41.960> note<00:46:42.440> and<00:46:43.040> we<00:46:43.240> could 00:46:43.470 --> 00:46:43.480 align:start position:0% and here on our note and we could 00:46:43.480 --> 00:46:46.829 align:start position:0% and here on our note and we could starting<00:46:43.960> to<00:46:44.559> to<00:46:44.800> syn<00:46:45.800> uh<00:46:46.319> I<00:46:46.400> don't<00:46:46.559> know<00:46:46.760> we 00:46:46.829 --> 00:46:46.839 align:start position:0% starting to to syn uh I don't know we 00:46:46.839 --> 00:46:49.790 align:start position:0% starting to to syn uh I don't know we are<00:46:46.960> going<00:46:47.119> to<00:46:47.280> choose<00:46:47.680> G<00:46:48.480> Nimbus<00:46:49.480> whatever 00:46:49.790 --> 00:46:49.800 align:start position:0% are going to choose G Nimbus whatever 00:46:49.800 --> 00:46:52.589 align:start position:0% are going to choose G Nimbus whatever you<00:46:49.960> want<00:46:50.440> whatever<00:46:50.720> you<00:46:50.800> want<00:46:51.200> you<00:46:51.440> you<00:46:52.440> the 00:46:52.589 --> 00:46:52.599 align:start position:0% you want whatever you want you you the 00:46:52.599 --> 00:46:54.790 align:start position:0% you want whatever you want you you the idea<00:46:53.000> here<00:46:53.200> is<00:46:53.359> that<00:46:53.559> you<00:46:53.680> can<00:46:53.880> choose<00:46:54.520> any 00:46:54.790 --> 00:46:54.800 align:start position:0% idea here is that you can choose any 00:46:54.800 --> 00:46:57.910 align:start position:0% idea here is that you can choose any client<00:46:55.680> any<00:46:55.880> client<00:46:56.200> you<00:46:56.319> want<00:46:57.079> you<00:46:57.319> choose<00:46:57.640> a 00:46:57.910 --> 00:46:57.920 align:start position:0% client any client you want you choose a 00:46:57.920 --> 00:47:02.109 align:start position:0% client any client you want you choose a consensus<00:46:58.480> client<00:46:59.040> you<00:46:59.319> choose<00:47:00.319> a<00:47:00.920> execution 00:47:02.109 --> 00:47:02.119 align:start position:0% consensus client you choose a execution 00:47:02.119 --> 00:47:06.109 align:start position:0% consensus client you choose a execution client<00:47:03.119> uh<00:47:03.359> start<00:47:03.800> the<00:47:04.079> consensus<00:47:05.119> service 00:47:06.109 --> 00:47:06.119 align:start position:0% client uh start the consensus service 00:47:06.119 --> 00:47:09.910 align:start position:0% client uh start the consensus service and<00:47:06.280> start<00:47:06.680> the<00:47:07.520> um<00:47:08.400> execution<00:47:08.920> service<00:47:09.760> and 00:47:09.910 --> 00:47:09.920 align:start position:0% and start the um execution service and 00:47:09.920 --> 00:47:13.150 align:start position:0% and start the um execution service and you're<00:47:10.200> done<00:47:10.599> that's<00:47:10.880> the<00:47:11.119> that's<00:47:11.319> the 00:47:13.150 --> 00:47:13.160 align:start position:0% you're done that's the that's the 00:47:13.160 --> 00:47:16.990 align:start position:0% you're done that's the that's the idea<00:47:14.160> we<00:47:14.319> want<00:47:14.640> to<00:47:15.640> this<00:47:15.760> is<00:47:15.839> for<00:47:16.040> layer<00:47:16.359> one<00:47:16.760> of 00:47:16.990 --> 00:47:17.000 align:start position:0% idea we want to this is for layer one of 00:47:17.000 --> 00:47:19.950 align:start position:0% idea we want to this is for layer one of course<00:47:18.000> H<00:47:18.119> Layer<00:47:18.440> Two<00:47:18.680> is<00:47:19.079> basically<00:47:19.520> the<00:47:19.680> same 00:47:19.950 --> 00:47:19.960 align:start position:0% course H Layer Two is basically the same 00:47:19.960 --> 00:47:22.910 align:start position:0% course H Layer Two is basically the same but<00:47:20.200> you<00:47:20.440> need<00:47:20.960> first<00:47:21.480> uh<00:47:21.599> to<00:47:21.839> have<00:47:22.000> a<00:47:22.160> ler<00:47:22.440> one 00:47:22.910 --> 00:47:22.920 align:start position:0% but you need first uh to have a ler one 00:47:22.920 --> 00:47:23.870 align:start position:0% but you need first uh to have a ler one uh 00:47:23.870 --> 00:47:23.880 align:start position:0% uh 00:47:23.880 --> 00:47:26.630 align:start position:0% uh running<00:47:24.880> uh<00:47:25.200> as<00:47:25.319> you<00:47:25.440> know<00:47:25.839> the<00:47:26.040> the<00:47:26.240> consensus 00:47:26.630 --> 00:47:26.640 align:start position:0% running uh as you know the the consensus 00:47:26.640 --> 00:47:30.109 align:start position:0% running uh as you know the the consensus CL<00:47:26.920> Cent<00:47:27.520> uh<00:47:27.800> SNS<00:47:28.280> with<00:47:28.720> checkpoint<00:47:29.200> sync<00:47:29.920> so 00:47:30.109 --> 00:47:30.119 align:start position:0% CL Cent uh SNS with checkpoint sync so 00:47:30.119 --> 00:47:32.670 align:start position:0% CL Cent uh SNS with checkpoint sync so you<00:47:30.280> need<00:47:30.480> a<00:47:30.599> little<00:47:30.920> time<00:47:31.160> to<00:47:31.760> to<00:47:31.960> get<00:47:32.280> the<00:47:32.480> the 00:47:32.670 --> 00:47:32.680 align:start position:0% you need a little time to to get the the 00:47:32.680 --> 00:47:33.630 align:start position:0% you need a little time to to get the the client 00:47:33.630 --> 00:47:33.640 align:start position:0% client 00:47:33.640 --> 00:47:39.230 align:start position:0% client sync<00:47:34.640> uh<00:47:35.640> and<00:47:36.640> the<00:47:36.880> execution<00:47:37.559> client<00:47:38.559> ER<00:47:39.000> last 00:47:39.230 --> 00:47:39.240 align:start position:0% sync uh and the execution client ER last 00:47:39.240 --> 00:47:42.630 align:start position:0% sync uh and the execution client ER last time<00:47:39.520> we<00:47:40.040> we<00:47:40.200> tried<00:47:40.640> G<00:47:41.400> uh<00:47:41.720> I<00:47:41.880> think<00:47:42.200> it<00:47:42.359> was 00:47:42.630 --> 00:47:42.640 align:start position:0% time we we tried G uh I think it was 00:47:42.640 --> 00:47:44.109 align:start position:0% time we we tried G uh I think it was like<00:47:43.200> 12 00:47:44.109 --> 00:47:44.119 align:start position:0% like 12 00:47:44.119 --> 00:47:47.470 align:start position:0% like 12 hours<00:47:45.119> uh<00:47:45.599> but<00:47:45.800> never<00:47:46.119> mind<00:47:46.440> is<00:47:47.119> a<00:47:47.200> little 00:47:47.470 --> 00:47:47.480 align:start position:0% hours uh but never mind is a little 00:47:47.480 --> 00:47:50.230 align:start position:0% hours uh but never mind is a little faster<00:47:47.880> because<00:47:48.599> uh<00:47:48.839> once<00:47:49.200> they<00:47:49.480> keep<00:47:49.760> up<00:47:50.079> with 00:47:50.230 --> 00:47:50.240 align:start position:0% faster because uh once they keep up with 00:47:50.240 --> 00:47:53.349 align:start position:0% faster because uh once they keep up with the<00:47:50.359> change<00:47:51.079> uh<00:47:51.800> the<00:47:52.000> state<00:47:52.359> is<00:47:52.839> sinking<00:47:53.240> in 00:47:53.349 --> 00:47:53.359 align:start position:0% the change uh the state is sinking in 00:47:53.359 --> 00:47:56.630 align:start position:0% the change uh the state is sinking in the<00:47:53.520> background<00:47:54.400> so<00:47:54.640> you<00:47:54.800> can<00:47:55.640> you<00:47:55.760> can<00:47:56.040> have<00:47:56.319> a 00:47:56.630 --> 00:47:56.640 align:start position:0% the background so you can you can have a 00:47:56.640 --> 00:48:00.549 align:start position:0% the background so you can you can have a a<00:47:57.000> h<00:47:57.760> a<00:47:57.960> usable<00:47:58.400> note<00:47:58.760> in<00:47:59.079> maybe<00:47:59.359> four<00:48:00.280> five 00:48:00.549 --> 00:48:00.559 align:start position:0% a h a usable note in maybe four five 00:48:00.559 --> 00:48:03.190 align:start position:0% a h a usable note in maybe four five hours<00:48:01.520> it's<00:48:01.839> very 00:48:03.190 --> 00:48:03.200 align:start position:0% hours it's very 00:48:03.200 --> 00:48:06.750 align:start position:0% hours it's very fast<00:48:04.200> yeah<00:48:04.359> just<00:48:04.559> today<00:48:04.960> we<00:48:05.119> sink<00:48:05.559> here<00:48:06.119> in<00:48:06.440> 4 00:48:06.750 --> 00:48:06.760 align:start position:0% fast yeah just today we sink here in 4 00:48:06.760 --> 00:48:10.390 align:start position:0% fast yeah just today we sink here in 4 hours<00:48:07.760> yeah<00:48:08.040> four<00:48:08.599> four<00:48:08.760> hours<00:48:09.280> here<00:48:09.400> in<00:48:10.319> in 00:48:10.390 --> 00:48:10.400 align:start position:0% hours yeah four four hours here in in 00:48:10.400 --> 00:48:13.829 align:start position:0% hours yeah four four hours here in in the<00:48:10.559> boot<00:48:10.960> of<00:48:11.680> stick<00:48:11.960> at<00:48:12.119> home<00:48:12.319> boot<00:48:13.240> we<00:48:13.599> no 00:48:13.829 --> 00:48:13.839 align:start position:0% the boot of stick at home boot we no 00:48:13.839 --> 00:48:15.670 align:start position:0% the boot of stick at home boot we no port<00:48:14.079> forwarding<00:48:14.680> nothing<00:48:14.960> no<00:48:15.079> P<00:48:15.240> forwarding 00:48:15.670 --> 00:48:15.680 align:start position:0% port forwarding nothing no P forwarding 00:48:15.680 --> 00:48:17.750 align:start position:0% port forwarding nothing no P forwarding not<00:48:15.920> everything<00:48:16.280> is<00:48:16.599> slower<00:48:17.160> that<00:48:17.520> you<00:48:17.640> could 00:48:17.750 --> 00:48:17.760 align:start position:0% not everything is slower that you could 00:48:17.760 --> 00:48:20.790 align:start position:0% not everything is slower that you could do<00:48:18.000> at<00:48:18.119> home<00:48:18.319> but<00:48:18.440> in<00:48:18.559> 4<00:48:18.760> hours<00:48:19.359> we<00:48:19.520> have<00:48:19.839> a 00:48:20.790 --> 00:48:20.800 align:start position:0% do at home but in 4 hours we have a 00:48:20.800 --> 00:48:24.430 align:start position:0% do at home but in 4 hours we have a nether<00:48:21.000> M<00:48:21.160> syn<00:48:21.839> was<00:48:22.119> prison<00:48:22.680> plus<00:48:23.440> NE<00:48:23.960> I<00:48:24.079> think 00:48:24.430 --> 00:48:24.440 align:start position:0% nether M syn was prison plus NE I think 00:48:24.440 --> 00:48:26.910 align:start position:0% nether M syn was prison plus NE I think yeah<00:48:25.160> but<00:48:25.359> again<00:48:25.559> you<00:48:25.640> can<00:48:25.839> choose<00:48:26.200> any<00:48:26.480> Cent 00:48:26.910 --> 00:48:26.920 align:start position:0% yeah but again you can choose any Cent 00:48:26.920 --> 00:48:31.349 align:start position:0% yeah but again you can choose any Cent you<00:48:27.040> want<00:48:28.000> te<00:48:28.400> you<00:48:29.319> uh<00:48:29.839> nimbos<00:48:30.839> nimos 00:48:31.349 --> 00:48:31.359 align:start position:0% you want te you uh nimbos nimos 00:48:31.359 --> 00:48:33.390 align:start position:0% you want te you uh nimbos nimos especially<00:48:31.960> are<00:48:32.200> good<00:48:32.400> for<00:48:32.640> these<00:48:32.839> kinds<00:48:33.119> of 00:48:33.390 --> 00:48:33.400 align:start position:0% especially are good for these kinds of 00:48:33.400 --> 00:48:38.069 align:start position:0% especially are good for these kinds of of<00:48:33.559> devices<00:48:34.040> because<00:48:34.319> it's<00:48:34.520> very<00:48:35.079> light<00:48:36.160> uh<00:48:37.160> it 00:48:38.069 --> 00:48:38.079 align:start position:0% of devices because it's very light uh it 00:48:38.079 --> 00:48:40.990 align:start position:0% of devices because it's very light uh it I<00:48:38.200> think<00:48:38.359> it<00:48:38.520> takes<00:48:39.480> less<00:48:39.720> than<00:48:39.880> 1<00:48:40.119> gab<00:48:40.559> of<00:48:40.720> ram 00:48:40.990 --> 00:48:41.000 align:start position:0% I think it takes less than 1 gab of ram 00:48:41.000 --> 00:48:45.870 align:start position:0% I think it takes less than 1 gab of ram it's<00:48:41.520> amazing<00:48:42.520> and<00:48:43.359> uh<00:48:44.000> yeah<00:48:44.520> prism<00:48:45.200> and<00:48:45.559> and 00:48:45.870 --> 00:48:45.880 align:start position:0% it's amazing and uh yeah prism and and 00:48:45.880 --> 00:48:48.069 align:start position:0% it's amazing and uh yeah prism and and Lighthouse<00:48:46.880> grandine<00:48:47.440> I<00:48:47.520> think<00:48:47.760> that<00:48:47.920> we 00:48:48.069 --> 00:48:48.079 align:start position:0% Lighthouse grandine I think that we 00:48:48.079 --> 00:48:51.710 align:start position:0% Lighthouse grandine I think that we support<00:48:48.440> as<00:48:48.640> well<00:48:49.079> and<00:48:49.520> lar<00:48:50.520> granding<00:48:51.000> and<00:48:51.200> ler 00:48:51.710 --> 00:48:51.720 align:start position:0% support as well and lar granding and ler 00:48:51.720 --> 00:48:57.230 align:start position:0% support as well and lar granding and ler yeah<00:48:52.000> and<00:48:53.240> and<00:48:54.240> for<00:48:54.480> the<00:48:54.680> execution<00:48:55.280> side<00:48:55.960> uh<00:48:56.920> G 00:48:57.230 --> 00:48:57.240 align:start position:0% yeah and and for the execution side uh G 00:48:57.240 --> 00:49:03.990 align:start position:0% yeah and and for the execution side uh G NE<00:48:57.599> mine<00:48:58.720> B<00:48:59.720> uh<00:49:00.400> re<00:49:00.880> and 00:49:03.990 --> 00:49:04.000 align:start position:0% 00:49:04.000 --> 00:49:10.390 align:start position:0% Aron<00:49:05.240> uh<00:49:06.240> yeah<00:49:06.480> yeah<00:49:07.319> right<00:49:07.480> now<00:49:08.200> uh 00:49:10.390 --> 00:49:10.400 align:start position:0% Aron uh yeah yeah right now uh 00:49:10.400 --> 00:49:13.549 align:start position:0% Aron uh yeah yeah right now uh the<00:49:11.400> the<00:49:11.559> station<00:49:11.920> of<00:49:12.200> all<00:49:12.480> the<00:49:12.839> the<00:49:13.040> the<00:49:13.280> over 00:49:13.549 --> 00:49:13.559 align:start position:0% the the station of all the the the over 00:49:13.559 --> 00:49:17.390 align:start position:0% the the station of all the the the over ended<00:49:14.079> here<00:49:14.960> with<00:49:15.200> the<00:49:15.359> layers<00:49:15.760> two<00:49:16.599> that<00:49:17.240> uh 00:49:17.390 --> 00:49:17.400 align:start position:0% ended here with the layers two that uh 00:49:17.400 --> 00:49:19.630 align:start position:0% ended here with the layers two that uh there<00:49:17.520> are<00:49:17.839> the<00:49:18.200> the<00:49:18.799> the<00:49:18.920> layer<00:49:19.160> two<00:49:19.400> that<00:49:19.480> we 00:49:19.630 --> 00:49:19.640 align:start position:0% there are the the the layer two that we 00:49:19.640 --> 00:49:22.309 align:start position:0% there are the the the layer two that we support<00:49:20.000> right<00:49:20.160> now<00:49:20.920> and<00:49:21.200> started<00:49:21.640> to<00:49:22.119> to 00:49:22.309 --> 00:49:22.319 align:start position:0% support right now and started to to 00:49:22.319 --> 00:49:25.430 align:start position:0% support right now and started to to start<00:49:23.160> uh<00:49:23.359> promethus<00:49:24.000> and<00:49:24.240> and<00:49:24.440> grafana<00:49:25.280> you 00:49:25.430 --> 00:49:25.440 align:start position:0% start uh promethus and and grafana you 00:49:25.440 --> 00:49:29.710 align:start position:0% start uh promethus and and grafana you will<00:49:25.680> have<00:49:26.119> uh<00:49:27.119> um<00:49:28.000> our<00:49:28.240> F<00:49:28.599> server<00:49:28.880> running<00:49:29.319> in 00:49:29.710 --> 00:49:29.720 align:start position:0% will have uh um our F server running in 00:49:29.720 --> 00:49:32.270 align:start position:0% will have uh um our F server running in in<00:49:29.880> your<00:49:30.119> device<00:49:30.440> and<00:49:30.599> you<00:49:30.720> will<00:49:31.000> see<00:49:31.359> all<00:49:31.680> the 00:49:32.270 --> 00:49:32.280 align:start position:0% in your device and you will see all the 00:49:32.280 --> 00:49:33.950 align:start position:0% in your device and you will see all the right<00:49:32.440> now<00:49:32.760> the<00:49:33.000> the<00:49:33.079> official<00:49:33.480> that's<00:49:33.720> works 00:49:33.950 --> 00:49:33.960 align:start position:0% right now the the official that's works 00:49:33.960 --> 00:49:37.470 align:start position:0% right now the the official that's works of<00:49:34.079> for<00:49:34.720> clients<00:49:35.720> and<00:49:36.319> it<00:49:36.480> will<00:49:36.720> depends<00:49:37.079> on 00:49:37.470 --> 00:49:37.480 align:start position:0% of for clients and it will depends on 00:49:37.480 --> 00:49:39.030 align:start position:0% of for clients and it will depends on what<00:49:37.640> client<00:49:37.960> are<00:49:38.119> you're<00:49:38.240> running<00:49:38.720> you<00:49:38.839> will 00:49:39.030 --> 00:49:39.040 align:start position:0% what client are you're running you will 00:49:39.040 --> 00:49:41.349 align:start position:0% what client are you're running you will see<00:49:39.359> the<00:49:39.599> statistics<00:49:40.440> of<00:49:40.559> the<00:49:40.720> node<00:49:41.040> and<00:49:41.200> the 00:49:41.349 --> 00:49:41.359 align:start position:0% see the statistics of the node and the 00:49:41.359 --> 00:49:42.829 align:start position:0% see the statistics of the node and the statistics<00:49:41.960> of 00:49:42.829 --> 00:49:42.839 align:start position:0% statistics of 00:49:42.839 --> 00:49:46.150 align:start position:0% statistics of the<00:49:43.839> all<00:49:43.960> the<00:49:44.079> s<00:49:44.440> the<00:49:44.599> get<00:49:44.880> statistics<00:49:45.599> or 00:49:46.150 --> 00:49:46.160 align:start position:0% the all the s the get statistics or 00:49:46.160 --> 00:49:48.630 align:start position:0% the all the s the get statistics or nimus<00:49:46.680> statistics<00:49:47.319> all<00:49:47.559> the<00:49:47.720> with<00:49:47.880> the 00:49:48.630 --> 00:49:48.640 align:start position:0% nimus statistics all the with the 00:49:48.640 --> 00:49:53.510 align:start position:0% nimus statistics all the with the officials<00:49:50.079> um<00:49:51.079> uh<00:49:51.280> dashboard<00:49:52.119> and<00:49:53.119> at<00:49:53.240> the<00:49:53.319> end 00:49:53.510 --> 00:49:53.520 align:start position:0% officials um uh dashboard and at the end 00:49:53.520 --> 00:49:56.789 align:start position:0% officials um uh dashboard and at the end you<00:49:53.640> will<00:49:54.280> see<00:49:54.680> if<00:49:54.880> you<00:49:55.720> graan<00:49:56.040> is<00:49:56.160> very<00:49:56.280> useful 00:49:56.789 --> 00:49:56.799 align:start position:0% you will see if you graan is very useful 00:49:56.799 --> 00:50:00.549 align:start position:0% you will see if you graan is very useful to<00:49:57.599> to<00:49:57.799> see<00:49:58.599> problems<00:49:59.599> at<00:49:59.720> the<00:49:59.880> end<00:50:00.240> you<00:50:00.359> will 00:50:00.549 --> 00:50:00.559 align:start position:0% to to see problems at the end you will 00:50:00.559 --> 00:50:03.230 align:start position:0% to to see problems at the end you will see<00:50:00.960> all<00:50:01.240> the<00:50:01.799> hardware<00:50:02.280> stats<00:50:02.720> of<00:50:02.960> your 00:50:03.230 --> 00:50:03.240 align:start position:0% see all the hardware stats of your 00:50:03.240 --> 00:50:07.109 align:start position:0% see all the hardware stats of your device<00:50:03.640> if<00:50:03.880> this<00:50:04.240> low<00:50:05.240> CPUs<00:50:06.040> low<00:50:06.480> networks<00:50:06.960> you 00:50:07.109 --> 00:50:07.119 align:start position:0% device if this low CPUs low networks you 00:50:07.119 --> 00:50:10.309 align:start position:0% device if this low CPUs low networks you have<00:50:07.280> problems<00:50:07.640> you<00:50:07.760> have<00:50:08.400> you<00:50:08.680> know<00:50:09.680> uh<00:50:09.920> for 00:50:10.309 --> 00:50:10.319 align:start position:0% have problems you have you know uh for 00:50:10.319 --> 00:50:12.390 align:start position:0% have problems you have you know uh for people<00:50:10.680> like<00:50:10.960> doing<00:50:11.640> banama<00:50:12.000> if<00:50:12.119> you<00:50:12.240> have 00:50:12.390 --> 00:50:12.400 align:start position:0% people like doing banama if you have 00:50:12.400 --> 00:50:13.670 align:start position:0% people like doing banama if you have problems<00:50:12.760> with<00:50:12.880> your<00:50:13.000> internet<00:50:13.319> connection 00:50:13.670 --> 00:50:13.680 align:start position:0% problems with your internet connection 00:50:13.680 --> 00:50:14.990 align:start position:0% problems with your internet connection you<00:50:13.760> will<00:50:13.920> see<00:50:14.119> the<00:50:14.240> drops<00:50:14.520> in<00:50:14.680> internet 00:50:14.990 --> 00:50:15.000 align:start position:0% you will see the drops in internet 00:50:15.000 --> 00:50:16.470 align:start position:0% you will see the drops in internet connection<00:50:15.319> when<00:50:15.400> you<00:50:15.520> are<00:50:15.960> home<00:50:16.200> and<00:50:16.400> you 00:50:16.470 --> 00:50:16.480 align:start position:0% connection when you are home and you 00:50:16.480 --> 00:50:20.150 align:start position:0% connection when you are home and you could<00:50:16.640> see<00:50:17.280> via<00:50:17.599> your<00:50:18.079> local<00:50:18.359> network<00:50:19.200> all<00:50:19.480> the 00:50:20.150 --> 00:50:20.160 align:start position:0% could see via your local network all the 00:50:20.160 --> 00:50:22.390 align:start position:0% could see via your local network all the all<00:50:20.319> the<00:50:20.440> stats<00:50:20.839> of<00:50:21.000> your 00:50:22.390 --> 00:50:22.400 align:start position:0% all the stats of your 00:50:22.400 --> 00:50:24.510 align:start position:0% all the stats of your note 00:50:24.510 --> 00:50:24.520 align:start position:0% note 00:50:24.520 --> 00:50:29.430 align:start position:0% note um<00:50:25.520> of<00:50:25.680> course<00:50:25.880> this<00:50:26.680> automatic<00:50:27.760> and<00:50:28.760> now<00:50:29.119> it's 00:50:29.430 --> 00:50:29.440 align:start position:0% um of course this automatic and now it's 00:50:29.440 --> 00:50:32.390 align:start position:0% um of course this automatic and now it's ending<00:50:30.000> with<00:50:30.200> all<00:50:30.359> the 00:50:32.390 --> 00:50:32.400 align:start position:0% ending with all the 00:50:32.400 --> 00:50:35.710 align:start position:0% ending with all the dependencies<00:50:33.400> is<00:50:33.559> in<00:50:34.280> gra<00:50:34.960> gfan<00:50:35.319> is<00:50:35.440> already 00:50:35.710 --> 00:50:35.720 align:start position:0% dependencies is in gra gfan is already 00:50:35.720 --> 00:50:38.349 align:start position:0% dependencies is in gra gfan is already started<00:50:36.200> yeah<00:50:36.960> but<00:50:37.200> we<00:50:37.359> have<00:50:37.480> to<00:50:37.680> restart<00:50:38.040> the 00:50:38.349 --> 00:50:38.359 align:start position:0% started yeah but we have to restart the 00:50:38.359 --> 00:50:41.470 align:start position:0% started yeah but we have to restart the note<00:50:39.359> uh<00:50:39.599> this<00:50:39.720> is 00:50:41.470 --> 00:50:41.480 align:start position:0% note uh this is 00:50:41.480 --> 00:50:45.030 align:start position:0% note uh this is the 00:50:45.030 --> 00:50:45.040 align:start position:0% 00:50:45.040 --> 00:50:48.950 align:start position:0% set 00:50:48.950 --> 00:50:48.960 align:start position:0% 00:50:48.960 --> 00:50:52.549 align:start position:0% heard<00:50:49.960> uh<00:50:50.079> four<00:50:50.319> terab<00:50:50.720> for<00:50:50.880> an<00:50:51.240> archive<00:50:51.599> node 00:50:52.549 --> 00:50:52.559 align:start position:0% heard uh four terab for an archive node 00:50:52.559 --> 00:50:55.710 align:start position:0% heard uh four terab for an archive node no<00:50:53.319> um<00:50:54.319> the<00:50:54.440> problem<00:50:54.680> is<00:50:55.040> that<00:50:55.200> the<00:50:55.319> state<00:50:55.520> is 00:50:55.710 --> 00:50:55.720 align:start position:0% no um the problem is that the state is 00:50:55.720 --> 00:50:58.589 align:start position:0% no um the problem is that the state is gring<00:50:56.440> uh<00:50:56.760> um<00:50:57.119> I<00:50:57.240> think<00:50:57.520> that<00:50:57.720> now<00:50:58.000> maybe<00:50:58.400> a 00:50:58.589 --> 00:50:58.599 align:start position:0% gring uh um I think that now maybe a 00:50:58.599 --> 00:51:01.710 align:start position:0% gring uh um I think that now maybe a fresh<00:50:58.920> ink<00:50:59.240> is<00:50:59.440> about<00:51:00.119> 1.1 00:51:01.710 --> 00:51:01.720 align:start position:0% fresh ink is about 1.1 00:51:01.720 --> 00:51:08.789 align:start position:0% fresh ink is about 1.1 1.2<00:51:02.720> uh<00:51:02.920> yeah<00:51:03.200> it<00:51:03.920> uh<00:51:04.160> grows<00:51:05.400> um<00:51:06.680> fast<00:51:07.680> uh<00:51:08.440> maybe 00:51:08.789 --> 00:51:08.799 align:start position:0% 1.2 uh yeah it uh grows um fast uh maybe 00:51:08.799 --> 00:51:12.109 align:start position:0% 1.2 uh yeah it uh grows um fast uh maybe it<00:51:09.040> will<00:51:09.319> be<00:51:09.920> uh<00:51:10.200> okay<00:51:10.440> for<00:51:11.440> maybe<00:51:11.720> several 00:51:12.109 --> 00:51:12.119 align:start position:0% it will be uh okay for maybe several 00:51:12.119 --> 00:51:15.589 align:start position:0% it will be uh okay for maybe several months<00:51:13.119> but<00:51:13.640> uh<00:51:13.880> now<00:51:14.480> uh<00:51:14.599> if<00:51:14.720> you<00:51:14.880> can<00:51:15.160> afford 00:51:15.589 --> 00:51:15.599 align:start position:0% months but uh now uh if you can afford 00:51:15.599 --> 00:51:17.829 align:start position:0% months but uh now uh if you can afford four<00:51:15.880> terabytes<00:51:16.440> go<00:51:16.640> for<00:51:16.799> four<00:51:17.000> terabytes<00:51:17.720> but 00:51:17.829 --> 00:51:17.839 align:start position:0% four terabytes go for four terabytes but 00:51:17.839 --> 00:51:21.589 align:start position:0% four terabytes go for four terabytes but you<00:51:18.000> can<00:51:18.280> run<00:51:18.559> a<00:51:18.720> not<00:51:18.960> with<00:51:19.520> two<00:51:20.520> yet<00:51:21.319> it<00:51:21.480> it 00:51:21.589 --> 00:51:21.599 align:start position:0% you can run a not with two yet it it 00:51:21.599 --> 00:51:25.190 align:start position:0% you can run a not with two yet it it will<00:51:22.200> grow<00:51:23.200> network<00:51:23.760> will<00:51:23.960> grow<00:51:24.960> all<00:51:25.079> the 00:51:25.190 --> 00:51:25.200 align:start position:0% will grow network will grow all the 00:51:25.200 --> 00:51:27.549 align:start position:0% will grow network will grow all the blockchain<00:51:25.599> will<00:51:25.760> grow<00:51:26.280> is<00:51:26.839> in<00:51:27.040> Daily<00:51:27.400> in 00:51:27.549 --> 00:51:27.559 align:start position:0% blockchain will grow is in Daily in 00:51:27.559 --> 00:51:29.549 align:start position:0% blockchain will grow is in Daily in daily<00:51:27.839> basis<00:51:28.160> so<00:51:28.400> at<00:51:28.480> the<00:51:28.559> end<00:51:28.760> 2<00:51:28.920> tabes<00:51:29.359> is 00:51:29.549 --> 00:51:29.559 align:start position:0% daily basis so at the end 2 tabes is 00:51:29.559 --> 00:51:32.510 align:start position:0% daily basis so at the end 2 tabes is okay<00:51:29.760> for<00:51:30.079> for<00:51:30.200> now<00:51:30.880> clients<00:51:31.359> has<00:51:31.920> uh<00:51:32.079> clients 00:51:32.510 --> 00:51:32.520 align:start position:0% okay for for now clients has uh clients 00:51:32.520 --> 00:51:36.910 align:start position:0% okay for for now clients has uh clients have<00:51:32.920> um<00:51:33.880> uh<00:51:34.319> online<00:51:34.799> pruning<00:51:35.280> as<00:51:35.440> well<00:51:35.960> now<00:51:36.520> uh 00:51:36.910 --> 00:51:36.920 align:start position:0% have um uh online pruning as well now uh 00:51:36.920 --> 00:51:40.190 align:start position:0% have um uh online pruning as well now uh from<00:51:37.920> just<00:51:38.200> one<00:51:38.440> or<00:51:38.599> two<00:51:38.760> months<00:51:39.040> ago<00:51:39.720> so<00:51:40.000> it 00:51:40.190 --> 00:51:40.200 align:start position:0% from just one or two months ago so it 00:51:40.200 --> 00:51:43.829 align:start position:0% from just one or two months ago so it helps<00:51:40.880> to<00:51:41.359> to<00:51:41.599> keep<00:51:41.920> the<00:51:42.160> the<00:51:42.319> size<00:51:42.799> uh<00:51:43.000> low 00:51:43.829 --> 00:51:43.839 align:start position:0% helps to to keep the the size uh low 00:51:43.839 --> 00:51:46.870 align:start position:0% helps to to keep the the size uh low yeah<00:51:44.839> it's<00:51:45.119> it's<00:51:45.359> nice<00:51:46.000> you<00:51:46.160> Lo<00:51:46.480> everything 00:51:46.870 --> 00:51:46.880 align:start position:0% yeah it's it's nice you Lo everything 00:51:46.880 --> 00:51:47.990 align:start position:0% yeah it's it's nice you Lo everything right 00:51:47.990 --> 00:51:48.000 align:start position:0% right 00:51:48.000 --> 00:51:49.549 align:start position:0% right now 00:51:49.549 --> 00:51:49.559 align:start position:0% now 00:51:49.559 --> 00:51:52.150 align:start position:0% now how<00:51:50.559> terab<00:51:51.240> right 00:51:52.150 --> 00:51:52.160 align:start position:0% how terab right 00:51:52.160 --> 00:51:57.030 align:start position:0% how terab right now.<00:51:53.160> or<00:51:53.280> is<00:51:53.400> it<00:51:54.119> 1.99<00:51:55.400> already<00:51:56.400> yeah 00:51:57.030 --> 00:51:57.040 align:start position:0% now. or is it 1.99 already yeah 00:51:57.040 --> 00:51:59.589 align:start position:0% now. or is it 1.99 already yeah it's<00:51:57.280> hard<00:51:57.480> to<00:51:57.640> say<00:51:58.119> uh<00:51:58.240> it's<00:51:58.359> hard<00:51:58.559> to<00:51:58.680> say<00:51:59.079> but 00:51:59.589 --> 00:51:59.599 align:start position:0% it's hard to say uh it's hard to say but 00:51:59.599 --> 00:52:02.670 align:start position:0% it's hard to say uh it's hard to say but uh<00:51:59.920> with<00:52:00.440> uh<00:52:00.799> two<00:52:01.040> terabytes<00:52:01.839> I<00:52:01.960> think<00:52:02.480> uh 00:52:02.670 --> 00:52:02.680 align:start position:0% uh with uh two terabytes I think uh 00:52:02.680 --> 00:52:05.789 align:start position:0% uh with uh two terabytes I think uh maybe<00:52:02.960> six<00:52:03.200> seven<00:52:03.480> months<00:52:03.760> you<00:52:03.920> can 00:52:05.789 --> 00:52:05.799 align:start position:0% maybe six seven months you can 00:52:05.799 --> 00:52:08.390 align:start position:0% maybe six seven months you can run<00:52:06.799> it's<00:52:07.040> almost<00:52:07.319> impossible<00:52:07.760> to<00:52:07.960> to<00:52:08.079> tell 00:52:08.390 --> 00:52:08.400 align:start position:0% run it's almost impossible to to tell 00:52:08.400 --> 00:52:10.190 align:start position:0% run it's almost impossible to to tell but<00:52:08.720> I<00:52:08.920> don't<00:52:09.160> think<00:52:09.440> that<00:52:09.559> you<00:52:09.720> will<00:52:09.920> last 00:52:10.190 --> 00:52:10.200 align:start position:0% but I don't think that you will last 00:52:10.200 --> 00:52:12.829 align:start position:0% but I don't think that you will last more<00:52:10.400> than<00:52:10.559> a<00:52:10.880> year<00:52:11.880> with<00:52:12.079> two<00:52:12.240> terab<00:52:12.720> right 00:52:12.829 --> 00:52:12.839 align:start position:0% more than a year with two terab right 00:52:12.839 --> 00:52:15.630 align:start position:0% more than a year with two terab right now<00:52:13.480> you<00:52:13.720> probably<00:52:14.040> will<00:52:14.160> need<00:52:14.359> a<00:52:14.520> 4<00:52:14.760> terabytes 00:52:15.630 --> 00:52:15.640 align:start position:0% now you probably will need a 4 terabytes 00:52:15.640 --> 00:52:18.589 align:start position:0% now you probably will need a 4 terabytes for<00:52:15.839> sure<00:52:16.520> or<00:52:16.760> or<00:52:17.040> or<00:52:17.160> even<00:52:17.400> bigger<00:52:17.880> in<00:52:18.400> in<00:52:18.520> the 00:52:18.589 --> 00:52:18.599 align:start position:0% for sure or or or even bigger in in the 00:52:18.599 --> 00:52:21.309 align:start position:0% for sure or or or even bigger in in the few<00:52:18.920> years<00:52:19.400> but<00:52:19.839> I<00:52:19.920> think<00:52:20.079> we<00:52:20.160> are<00:52:20.280> in<00:52:20.400> the<00:52:20.559> B<00:52:20.960> of 00:52:21.309 --> 00:52:21.319 align:start position:0% few years but I think we are in the B of 00:52:21.319 --> 00:52:24.789 align:start position:0% few years but I think we are in the B of of<00:52:21.640> asking<00:52:22.000> for<00:52:22.440> for<00:52:22.720> for<00:52:23.040> terabytes<00:52:23.599> yes<00:52:24.359> yes 00:52:24.789 --> 00:52:24.799 align:start position:0% of asking for for for terabytes yes yes 00:52:24.799 --> 00:52:27.109 align:start position:0% of asking for for for terabytes yes yes for<00:52:25.319> for<00:52:25.640> be<00:52:25.960> for<00:52:26.160> be 00:52:27.109 --> 00:52:27.119 align:start position:0% for for be for be 00:52:27.119 --> 00:52:29.309 align:start position:0% for for be for be for<00:52:27.359> for<00:52:27.599> me<00:52:28.000> okay<00:52:28.359> he<00:52:28.520> you<00:52:28.680> want<00:52:29.040> you<00:52:29.119> are 00:52:29.309 --> 00:52:29.319 align:start position:0% for for me okay he you want you are 00:52:29.319 --> 00:52:31.589 align:start position:0% for for me okay he you want you are going<00:52:29.480> to<00:52:29.640> buy<00:52:30.000> something<00:52:30.359> right<00:52:30.520> now<00:52:31.440> okay 00:52:31.589 --> 00:52:31.599 align:start position:0% going to buy something right now okay 00:52:31.599 --> 00:52:33.829 align:start position:0% going to buy something right now okay spend<00:52:31.880> a<00:52:32.000> little<00:52:32.280> more<00:52:32.760> buy<00:52:33.040> 4<00:52:33.280> terabytes<00:52:33.720> and 00:52:33.829 --> 00:52:33.839 align:start position:0% spend a little more buy 4 terabytes and 00:52:33.839 --> 00:52:37.670 align:start position:0% spend a little more buy 4 terabytes and you<00:52:33.920> are<00:52:34.040> good<00:52:34.200> to<00:52:34.319> go<00:52:34.520> probably<00:52:34.760> for<00:52:35.160> years 00:52:37.670 --> 00:52:37.680 align:start position:0% you are good to go probably for years 00:52:37.680 --> 00:52:41.430 align:start position:0% you are good to go probably for years yes<00:52:38.680> okay<00:52:39.119> uh<00:52:40.079> meanwhile<00:52:40.839> it's<00:52:41.119> still 00:52:41.430 --> 00:52:41.440 align:start position:0% yes okay uh meanwhile it's still 00:52:41.440 --> 00:52:44.190 align:start position:0% yes okay uh meanwhile it's still standing<00:52:41.920> there<00:52:42.680> this<00:52:42.799> is<00:52:43.040> the<00:52:43.839> uh<00:52:43.960> if<00:52:44.079> you 00:52:44.190 --> 00:52:44.200 align:start position:0% standing there this is the uh if you 00:52:44.200 --> 00:52:47.510 align:start position:0% standing there this is the uh if you want<00:52:44.440> to<00:52:44.960> to<00:52:45.680> to<00:52:45.839> create<00:52:46.240> your<00:52:46.880> your<00:52:47.119> packages 00:52:47.510 --> 00:52:47.520 align:start position:0% want to to to create your your packages 00:52:47.520 --> 00:52:49.549 align:start position:0% want to to to create your your packages at<00:52:47.720> home<00:52:47.960> and<00:52:48.119> don't<00:52:48.319> trust<00:52:48.640> a 00:52:49.549 --> 00:52:49.559 align:start position:0% at home and don't trust a 00:52:49.559 --> 00:52:53.190 align:start position:0% at home and don't trust a repository<00:52:50.559> uh<00:52:50.680> we<00:52:50.880> provide<00:52:51.280> this<00:52:51.520> make<00:52:52.200> files 00:52:53.190 --> 00:52:53.200 align:start position:0% repository uh we provide this make files 00:52:53.200 --> 00:52:56.950 align:start position:0% repository uh we provide this make files it's<00:52:53.559> uh<00:52:53.720> we<00:52:53.880> use<00:52:54.280> fpm<00:52:55.000> it's<00:52:55.200> a<00:52:55.599> ruby<00:52:55.960> tool<00:52:56.720> to 00:52:56.950 --> 00:52:56.960 align:start position:0% it's uh we use fpm it's a ruby tool to 00:52:56.960 --> 00:53:02.589 align:start position:0% it's uh we use fpm it's a ruby tool to create<00:52:57.920> uh<00:52:58.200> AP<00:52:58.960> RPM<00:52:59.720> or<00:52:59.920> any<00:53:00.160> other<00:53:00.440> kind<00:53:00.720> of<00:53:01.599> uh 00:53:02.589 --> 00:53:02.599 align:start position:0% create uh AP RPM or any other kind of uh 00:53:02.599 --> 00:53:06.910 align:start position:0% create uh AP RPM or any other kind of uh Dean<00:53:03.400> or<00:53:04.359> or<00:53:05.200> red<00:53:05.520> hat<00:53:05.720> packages<00:53:06.480> in<00:53:06.599> a<00:53:06.760> very 00:53:06.910 --> 00:53:06.920 align:start position:0% Dean or or red hat packages in a very 00:53:06.920 --> 00:53:10.430 align:start position:0% Dean or or red hat packages in a very easy<00:53:07.200> way<00:53:08.040> it's<00:53:08.720> quite<00:53:08.960> easy<00:53:09.240> to<00:53:09.400> use<00:53:10.040> at<00:53:10.200> the 00:53:10.430 --> 00:53:10.440 align:start position:0% easy way it's quite easy to use at the 00:53:10.440 --> 00:53:14.750 align:start position:0% easy way it's quite easy to use at the end<00:53:11.440> uh<00:53:11.760> you<00:53:11.920> only<00:53:12.160> have<00:53:12.280> to<00:53:13.040> pass<00:53:13.359> to<00:53:13.680> the<00:53:14.559> uh 00:53:14.750 --> 00:53:14.760 align:start position:0% end uh you only have to pass to the uh 00:53:14.760 --> 00:53:17.750 align:start position:0% end uh you only have to pass to the uh to<00:53:14.920> the<00:53:15.079> tool<00:53:15.799> some<00:53:16.079> kind<00:53:16.280> of<00:53:16.480> variables<00:53:17.040> and 00:53:17.750 --> 00:53:17.760 align:start position:0% to the tool some kind of variables and 00:53:17.760 --> 00:53:20.470 align:start position:0% to the tool some kind of variables and you<00:53:18.000> will<00:53:18.440> will<00:53:18.680> tell<00:53:18.880> in<00:53:19.200> where<00:53:19.359> is<00:53:19.640> the<00:53:20.240> the 00:53:20.470 --> 00:53:20.480 align:start position:0% you will will tell in where is the the 00:53:20.480 --> 00:53:22.030 align:start position:0% you will will tell in where is the the binaries<00:53:20.880> where<00:53:21.040> is<00:53:21.160> the<00:53:21.280> configuration 00:53:22.030 --> 00:53:22.040 align:start position:0% binaries where is the configuration 00:53:22.040 --> 00:53:24.910 align:start position:0% binaries where is the configuration files<00:53:23.040> uh<00:53:23.280> with<00:53:23.640> which<00:53:23.760> is<00:53:24.040> the<00:53:24.720> the 00:53:24.910 --> 00:53:24.920 align:start position:0% files uh with which is the the 00:53:24.920 --> 00:53:27.030 align:start position:0% files uh with which is the the maintainer<00:53:25.640> which<00:53:25.799> is<00:53:26.000> the<00:53:26.520> name<00:53:26.720> of<00:53:26.839> the 00:53:27.030 --> 00:53:27.040 align:start position:0% maintainer which is the name of the 00:53:27.040 --> 00:53:29.230 align:start position:0% maintainer which is the name of the package<00:53:27.520> at<00:53:27.680> the<00:53:27.799> end<00:53:28.000> is<00:53:28.359> quite<00:53:28.599> easy<00:53:28.920> and<00:53:29.079> we 00:53:29.230 --> 00:53:29.240 align:start position:0% package at the end is quite easy and we 00:53:29.240 --> 00:53:34.309 align:start position:0% package at the end is quite easy and we will<00:53:29.520> create<00:53:30.160> adbm<00:53:30.920> or<00:53:32.240> orpm<00:53:33.240> package<00:53:33.520> for<00:53:33.720> you 00:53:34.309 --> 00:53:34.319 align:start position:0% will create adbm or orpm package for you 00:53:34.319 --> 00:53:37.109 align:start position:0% will create adbm or orpm package for you so<00:53:34.640> you<00:53:34.760> could<00:53:35.359> use<00:53:36.000> these<00:53:36.280> scripts<00:53:36.640> to<00:53:36.799> create 00:53:37.109 --> 00:53:37.119 align:start position:0% so you could use these scripts to create 00:53:37.119 --> 00:53:39.670 align:start position:0% so you could use these scripts to create your<00:53:37.359> own<00:53:38.200> uh<00:53:38.400> packages<00:53:38.880> at<00:53:39.000> the<00:53:39.079> end<00:53:39.319> it's 00:53:39.670 --> 00:53:39.680 align:start position:0% your own uh packages at the end it's 00:53:39.680 --> 00:53:42.069 align:start position:0% your own uh packages at the end it's quite<00:53:39.920> easy<00:53:40.200> to<00:53:40.400> you<00:53:40.640> clone<00:53:40.960> the<00:53:41.119> repository 00:53:42.069 --> 00:53:42.079 align:start position:0% quite easy to you clone the repository 00:53:42.079 --> 00:53:45.549 align:start position:0% quite easy to you clone the repository go<00:53:42.280> to<00:53:42.520> the<00:53:43.280> uh<00:53:43.520> folder<00:53:44.000> of<00:53:44.240> any<00:53:44.520> of<00:53:44.760> the 00:53:45.549 --> 00:53:45.559 align:start position:0% go to the uh folder of any of the 00:53:45.559 --> 00:53:47.109 align:start position:0% go to the uh folder of any of the clients<00:53:46.079> and<00:53:46.280> write 00:53:47.109 --> 00:53:47.119 align:start position:0% clients and write 00:53:47.119 --> 00:53:51.789 align:start position:0% clients and write make<00:53:48.119> and<00:53:48.520> we<00:53:48.839> will<00:53:49.680> uh<00:53:49.920> use<00:53:50.480> make<00:53:50.680> file<00:53:50.960> to<00:53:51.520> and 00:53:51.789 --> 00:53:51.799 align:start position:0% make and we will uh use make file to and 00:53:51.799 --> 00:53:54.630 align:start position:0% make and we will uh use make file to and with<00:53:52.319> the<00:53:52.799> at<00:53:52.920> the<00:53:53.040> end<00:53:53.200> of<00:53:53.440> the<00:53:53.839> make<00:53:54.160> process 00:53:54.630 --> 00:53:54.640 align:start position:0% with the at the end of the make process 00:53:54.640 --> 00:53:58.270 align:start position:0% with the at the end of the make process you<00:53:54.720> will<00:53:55.000> have<00:53:55.319> a<00:53:55.880> a<00:53:56.079> DE<00:53:56.559> packages<00:53:57.000> orpm 00:53:58.270 --> 00:53:58.280 align:start position:0% you will have a a DE packages orpm 00:53:58.280 --> 00:54:01.190 align:start position:0% you will have a a DE packages orpm package<00:53:59.280> and<00:53:59.480> it's<00:53:59.680> it's<00:53:59.880> quite<00:54:00.079> easy<00:54:00.319> to<00:54:00.520> do 00:54:01.190 --> 00:54:01.200 align:start position:0% package and it's it's quite easy to do 00:54:01.200 --> 00:54:03.670 align:start position:0% package and it's it's quite easy to do we<00:54:01.319> think<00:54:01.559> is<00:54:02.160> very<00:54:02.520> well<00:54:02.760> and<00:54:03.000> it<00:54:03.119> will<00:54:03.319> take 00:54:03.670 --> 00:54:03.680 align:start position:0% we think is very well and it will take 00:54:03.680 --> 00:54:07.349 align:start position:0% we think is very well and it will take care<00:54:04.240> of<00:54:04.480> the<00:54:04.680> P<00:54:04.880> we<00:54:05.119> go<00:54:05.280> to<00:54:05.720> the<00:54:06.720> uh<00:54:06.960> official 00:54:07.349 --> 00:54:07.359 align:start position:0% care of the P we go to the uh official 00:54:07.359 --> 00:54:09.510 align:start position:0% care of the P we go to the uh official repository<00:54:08.240> get<00:54:08.440> the<00:54:08.559> latest 00:54:09.510 --> 00:54:09.520 align:start position:0% repository get the latest 00:54:09.520 --> 00:54:12.470 align:start position:0% repository get the latest version<00:54:10.520> uh<00:54:10.720> get<00:54:10.880> the<00:54:11.079> latest<00:54:11.520> binary<00:54:12.160> and 00:54:12.470 --> 00:54:12.480 align:start position:0% version uh get the latest binary and 00:54:12.480 --> 00:54:14.990 align:start position:0% version uh get the latest binary and compress<00:54:12.839> it<00:54:13.400> and<00:54:13.599> create<00:54:14.040> the<00:54:14.480> the<00:54:14.640> dean 00:54:14.990 --> 00:54:15.000 align:start position:0% compress it and create the the dean 00:54:15.000 --> 00:54:18.910 align:start position:0% compress it and create the the dean package<00:54:15.400> for<00:54:15.599> you<00:54:16.240> we<00:54:16.359> are<00:54:16.599> not<00:54:17.559> we<00:54:18.119> use 00:54:18.910 --> 00:54:18.920 align:start position:0% package for you we are not we use 00:54:18.920 --> 00:54:21.069 align:start position:0% package for you we are not we use usually<00:54:19.280> don't<00:54:19.520> touch<00:54:19.839> anything<00:54:20.400> in<00:54:20.680> the<00:54:20.960> in 00:54:21.069 --> 00:54:21.079 align:start position:0% usually don't touch anything in the in 00:54:21.079 --> 00:54:23.910 align:start position:0% usually don't touch anything in the in the<00:54:21.200> clients<00:54:22.160> sometimes<00:54:22.440> you<00:54:22.680> have<00:54:22.880> to<00:54:23.680> to 00:54:23.910 --> 00:54:23.920 align:start position:0% the clients sometimes you have to to 00:54:23.920 --> 00:54:26.109 align:start position:0% the clients sometimes you have to to compile<00:54:24.319> it<00:54:24.720> and<00:54:24.960> it's<00:54:25.240> always<00:54:25.599> in<00:54:25.760> the<00:54:25.960> in<00:54:26.040> the 00:54:26.109 --> 00:54:26.119 align:start position:0% compile it and it's always in the in the 00:54:26.119 --> 00:54:29.349 align:start position:0% compile it and it's always in the in the make<00:54:26.440> file<00:54:27.000> because<00:54:27.440> the<00:54:27.920> the 00:54:29.349 --> 00:54:29.359 align:start position:0% make file because the the 00:54:29.359 --> 00:54:32.150 align:start position:0% make file because the the the<00:54:30.359> the<00:54:30.480> maintainers<00:54:31.040> of<00:54:31.200> the<00:54:31.359> client<00:54:31.760> don't 00:54:32.150 --> 00:54:32.160 align:start position:0% the the maintainers of the client don't 00:54:32.160 --> 00:54:35.510 align:start position:0% the the maintainers of the client don't don't<00:54:32.480> doesn't<00:54:32.839> provide<00:54:33.319> an<00:54:33.920> an<00:54:34.119> arm<00:54:35.000> binary 00:54:35.510 --> 00:54:35.520 align:start position:0% don't doesn't provide an an arm binary 00:54:35.520 --> 00:54:37.670 align:start position:0% don't doesn't provide an an arm binary for<00:54:35.760> you<00:54:36.000> so<00:54:36.359> we<00:54:36.520> have<00:54:36.680> to<00:54:36.839> compile<00:54:37.160> it<00:54:37.280> for<00:54:37.480> you 00:54:37.670 --> 00:54:37.680 align:start position:0% for you so we have to compile it for you 00:54:37.680 --> 00:54:41.030 align:start position:0% for you so we have to compile it for you but<00:54:37.880> at<00:54:38.040> the<00:54:38.400> end<00:54:39.400> uh<00:54:39.880> let<00:54:40.040> me<00:54:40.240> see<00:54:40.520> if<00:54:40.720> it<00:54:40.839> will 00:54:41.030 --> 00:54:41.040 align:start position:0% but at the end uh let me see if it will 00:54:41.040 --> 00:54:46.430 align:start position:0% but at the end uh let me see if it will end<00:54:42.240> yes<00:54:43.240> uh<00:54:44.160> the<00:54:45.160> the<00:54:45.559> the<00:54:45.720> station<00:54:46.119> script 00:54:46.430 --> 00:54:46.440 align:start position:0% end yes uh the the the station script 00:54:46.440 --> 00:54:49.430 align:start position:0% end yes uh the the the station script ended<00:54:47.319> and<00:54:47.720> seems<00:54:48.040> to<00:54:48.359> to<00:54:48.559> end<00:54:48.799> way<00:54:49.040> at<00:54:49.160> the<00:54:49.240> end 00:54:49.430 --> 00:54:49.440 align:start position:0% ended and seems to to end way at the end 00:54:49.440 --> 00:54:53.910 align:start position:0% ended and seems to to end way at the end we<00:54:49.640> be<00:54:49.839> change<00:54:50.480> the<00:54:51.480> the<00:54:51.680> password<00:54:52.040> for<00:54:52.240> you<00:54:53.119> um 00:54:53.910 --> 00:54:53.920 align:start position:0% we be change the the password for you um 00:54:53.920 --> 00:54:57.109 align:start position:0% we be change the the password for you um we<00:54:54.400> create<00:54:55.400> uh<00:54:55.920> ethere 00:54:57.109 --> 00:54:57.119 align:start position:0% we create uh ethere 00:54:57.119 --> 00:54:59.950 align:start position:0% we create uh ethere user<00:54:57.760> with<00:54:58.079> an<00:54:58.240> ethereum<00:54:58.880> ethereum 00:54:59.950 --> 00:54:59.960 align:start position:0% user with an ethereum ethereum 00:54:59.960 --> 00:55:02.430 align:start position:0% user with an ethereum ethereum password<00:55:00.960> uh<00:55:01.079> we'll<00:55:01.280> force<00:55:01.559> you<00:55:01.760> to<00:55:02.000> to<00:55:02.160> change 00:55:02.430 --> 00:55:02.440 align:start position:0% password uh we'll force you to to change 00:55:02.440 --> 00:55:04.470 align:start position:0% password uh we'll force you to to change it<00:55:02.720> and<00:55:03.000> we<00:55:03.079> will<00:55:03.319> reboot<00:55:03.839> and<00:55:03.960> we<00:55:04.040> will<00:55:04.160> use 00:55:04.470 --> 00:55:04.480 align:start position:0% it and we will reboot and we will use 00:55:04.480 --> 00:55:06.589 align:start position:0% it and we will reboot and we will use see<00:55:04.799> you<00:55:05.000> have<00:55:05.440> uh<00:55:05.720> right<00:55:05.880> now<00:55:06.040> a<00:55:06.119> full<00:55:06.319> note<00:55:06.520> we 00:55:06.589 --> 00:55:06.599 align:start position:0% see you have uh right now a full note we 00:55:06.599 --> 00:55:18.950 align:start position:0% see you have uh right now a full note we you<00:55:06.720> going<00:55:06.880> to 00:55:18.950 --> 00:55:18.960 align:start position:0% 00:55:18.960 --> 00:55:21.789 align:start position:0% connect 00:55:21.789 --> 00:55:21.799 align:start position:0% connect 00:55:21.799 --> 00:55:27.430 align:start position:0% connect after<00:55:22.799> okay<00:55:23.240> let's<00:55:23.520> say<00:55:24.240> I<00:55:24.920> finish<00:55:25.280> sing<00:55:26.720> note 00:55:27.430 --> 00:55:27.440 align:start position:0% after okay let's say I finish sing note 00:55:27.440 --> 00:55:30.270 align:start position:0% after okay let's say I finish sing note via<00:55:27.680> normal<00:55:28.160> internet<00:55:29.160> after<00:55:29.680> thinking<00:55:30.119> the 00:55:30.270 --> 00:55:30.280 align:start position:0% via normal internet after thinking the 00:55:30.280 --> 00:55:34.510 align:start position:0% via normal internet after thinking the note<00:55:31.039> is<00:55:31.119> it<00:55:31.400> possible<00:55:31.760> to<00:55:31.960> run<00:55:32.280> this<00:55:33.039> via<00:55:34.039> uh 00:55:34.510 --> 00:55:34.520 align:start position:0% note is it possible to run this via uh 00:55:34.520 --> 00:55:37.349 align:start position:0% note is it possible to run this via uh via<00:55:35.119> VIA 00:55:37.349 --> 00:55:37.359 align:start position:0% via VIA 00:55:37.359 --> 00:55:39.750 align:start position:0% via VIA 5G<00:55:38.359> via 00:55:39.750 --> 00:55:39.760 align:start position:0% 5G via 00:55:39.760 --> 00:55:43.910 align:start position:0% 5G via 5G<00:55:40.760> possibly<00:55:41.640> but<00:55:41.880> I<00:55:42.000> cannot<00:55:42.400> say<00:55:43.280> uh<00:55:43.440> I<00:55:43.559> didn't 00:55:43.910 --> 00:55:43.920 align:start position:0% 5G possibly but I cannot say uh I didn't 00:55:43.920 --> 00:55:48.270 align:start position:0% 5G possibly but I cannot say uh I didn't try<00:55:45.039> uh<00:55:46.039> it's<00:55:46.319> possible<00:55:46.680> because<00:55:46.960> one<00:55:47.280> thing 00:55:48.270 --> 00:55:48.280 align:start position:0% try uh it's possible because one thing 00:55:48.280 --> 00:55:49.510 align:start position:0% try uh it's possible because one thing uh 00:55:49.510 --> 00:55:49.520 align:start position:0% uh 00:55:49.520 --> 00:55:53.870 align:start position:0% uh the<00:55:50.520> band<00:55:50.920> with<00:55:51.160> needed<00:55:51.760> is<00:55:52.760> much<00:55:52.960> more<00:55:53.240> less 00:55:53.870 --> 00:55:53.880 align:start position:0% the band with needed is much more less 00:55:53.880 --> 00:55:59.910 align:start position:0% the band with needed is much more less so<00:55:54.680> yeah<00:55:55.200> I<00:55:55.359> I<00:55:55.480> don't<00:55:55.680> know<00:55:56.599> is<00:55:56.720> the<00:55:56.920> 5G<00:55:57.880> yeah<00:55:58.520> in 00:55:59.910 --> 00:55:59.920 align:start position:0% so yeah I I don't know is the 5G yeah in 00:55:59.920 --> 00:56:08.870 align:start position:0% so yeah I I don't know is the 5G yeah in area<00:56:00.920> where<00:56:01.119> I<00:56:01.359> live<00:56:01.920> I<00:56:02.079> have<00:56:02.400> a<00:56:02.720> 5G 00:56:08.870 --> 00:56:08.880 align:start position:0% 00:56:08.880 --> 00:56:11.430 align:start position:0% connection<00:56:09.880> and<00:56:10.119> at<00:56:10.240> the<00:56:10.359> end<00:56:10.599> is<00:56:10.920> going 00:56:11.430 --> 00:56:11.440 align:start position:0% connection and at the end is going 00:56:11.440 --> 00:56:15.150 align:start position:0% connection and at the end is going around<00:56:12.079> 50<00:56:13.079> Max<00:56:13.440> per<00:56:13.640> second<00:56:14.039> so<00:56:14.599> at<00:56:14.760> the<00:56:14.880> end 00:56:15.150 --> 00:56:15.160 align:start position:0% around 50 Max per second so at the end 00:56:15.160 --> 00:56:17.069 align:start position:0% around 50 Max per second so at the end this<00:56:15.760> will<00:56:15.920> be 00:56:17.069 --> 00:56:17.079 align:start position:0% this will be 00:56:17.079 --> 00:56:18.670 align:start position:0% this will be enough 00:56:18.670 --> 00:56:18.680 align:start position:0% enough 00:56:18.680 --> 00:56:21.870 align:start position:0% enough when<00:56:19.680> to<00:56:19.799> keep<00:56:20.000> the<00:56:20.280> track<00:56:21.280> whenever<00:56:21.559> it<00:56:21.680> comes 00:56:21.870 --> 00:56:21.880 align:start position:0% when to keep the track whenever it comes 00:56:21.880 --> 00:56:24.549 align:start position:0% when to keep the track whenever it comes to<00:56:22.119> networks<00:56:22.839> it's<00:56:23.160> it's<00:56:23.440> hard<00:56:23.640> to<00:56:23.799> say<00:56:24.359> it's 00:56:24.549 --> 00:56:24.559 align:start position:0% to networks it's it's hard to say it's 00:56:24.559 --> 00:56:28.309 align:start position:0% to networks it's it's hard to say it's hard<00:56:24.760> to<00:56:24.920> say<00:56:26.359> so<00:56:26.920> have<00:56:27.119> anybody<00:56:27.599> in<00:56:27.920> in<00:56:28.119> the 00:56:28.309 --> 00:56:28.319 align:start position:0% hard to say so have anybody in in the 00:56:28.319 --> 00:56:31.309 align:start position:0% hard to say so have anybody in in the community<00:56:28.880> tried<00:56:29.400> running<00:56:30.000> it<00:56:30.520> for<00:56:30.680> a<00:56:30.880> while 00:56:31.309 --> 00:56:31.319 align:start position:0% community tried running it for a while 00:56:31.319 --> 00:56:35.589 align:start position:0% community tried running it for a while in<00:56:32.200> in<00:56:32.319> a<00:56:32.599> mobile<00:56:32.960> network<00:56:33.920> yeah<00:56:34.480> thank<00:56:34.640> you 00:56:35.589 --> 00:56:35.599 align:start position:0% in in a mobile network yeah thank you 00:56:35.599 --> 00:56:37.789 align:start position:0% in in a mobile network yeah thank you has<00:56:35.839> anybody<00:56:36.400> in<00:56:36.559> the<00:56:37.039> in<00:56:37.160> the<00:56:37.319> AR<00:56:37.599> in<00:56:37.680> the 00:56:37.789 --> 00:56:37.799 align:start position:0% has anybody in the in the AR in the 00:56:37.799 --> 00:56:40.710 align:start position:0% has anybody in the in the AR in the ethereum<00:56:38.200> and<00:56:38.319> arm<00:56:38.599> Community<00:56:39.520> or<00:56:39.880> in<00:56:40.079> the 00:56:40.710 --> 00:56:40.720 align:start position:0% ethereum and arm Community or in the 00:56:40.720 --> 00:56:44.109 align:start position:0% ethereum and arm Community or in the other<00:56:40.960> in<00:56:41.079> the<00:56:41.200> ethereum<00:56:41.760> small<00:56:42.760> uh<00:56:43.400> M<00:56:43.760> server 00:56:44.109 --> 00:56:44.119 align:start position:0% other in the ethereum small uh M server 00:56:44.119 --> 00:56:46.470 align:start position:0% other in the ethereum small uh M server Community<00:56:44.520> tried<00:56:44.839> running<00:56:45.400> this<00:56:45.640> for<00:56:45.839> a<00:56:46.079> while 00:56:46.470 --> 00:56:46.480 align:start position:0% Community tried running this for a while 00:56:46.480 --> 00:56:49.829 align:start position:0% Community tried running this for a while on<00:56:47.200> on<00:56:47.440> mobile<00:56:47.799> network<00:56:48.520> since<00:56:49.520> well 00:56:49.829 --> 00:56:49.839 align:start position:0% on on mobile network since well 00:56:49.839 --> 00:56:52.630 align:start position:0% on on mobile network since well especially<00:56:50.480> here<00:56:51.240> especially<00:56:51.799> in<00:56:52.119> in<00:56:52.359> in<00:56:52.480> our 00:56:52.630 --> 00:56:52.640 align:start position:0% especially here especially in in in our 00:56:52.640 --> 00:56:53.589 align:start position:0% especially here especially in in in our second 00:56:53.589 --> 00:56:53.599 align:start position:0% second 00:56:53.599 --> 00:56:56.470 align:start position:0% second world<00:56:54.599> mobile<00:56:54.880> networks<00:56:55.240> are<00:56:55.599> sometimes<00:56:55.799> more 00:56:56.470 --> 00:56:56.480 align:start position:0% world mobile networks are sometimes more 00:56:56.480 --> 00:57:01.430 align:start position:0% world mobile networks are sometimes more relable<00:56:57.799> it<00:56:58.799> it's<00:56:59.000> unable<00:56:59.680> though<00:57:00.599> it's<00:57:00.960> like 00:57:01.430 --> 00:57:01.440 align:start position:0% relable it it's unable though it's like 00:57:01.440 --> 00:57:03.349 align:start position:0% relable it it's unable though it's like the<00:57:01.559> mobile<00:57:01.880> network<00:57:02.599> is<00:57:02.799> not<00:57:03.079> really 00:57:03.349 --> 00:57:03.359 align:start position:0% the mobile network is not really 00:57:03.359 --> 00:57:05.190 align:start position:0% the mobile network is not really reliable<00:57:03.880> usually<00:57:04.240> the<00:57:04.319> one<00:57:04.520> at<00:57:04.640> least<00:57:04.920> I<00:57:05.079> I 00:57:05.190 --> 00:57:05.200 align:start position:0% reliable usually the one at least I I 00:57:05.200 --> 00:57:07.710 align:start position:0% reliable usually the one at least I I did<00:57:05.440> which<00:57:05.559> is<00:57:05.640> in<00:57:06.000> London<00:57:07.000> you<00:57:07.119> can<00:57:07.319> use<00:57:07.480> it 00:57:07.710 --> 00:57:07.720 align:start position:0% did which is in London you can use it 00:57:07.720 --> 00:57:11.190 align:start position:0% did which is in London you can use it it's<00:57:07.920> actually<00:57:08.240> quite<00:57:08.520> fast<00:57:09.400> but<00:57:09.520> it's 00:57:11.190 --> 00:57:11.200 align:start position:0% it's actually quite fast but it's 00:57:11.200 --> 00:57:13.390 align:start position:0% it's actually quite fast but it's unpredictable<00:57:12.200> and<00:57:12.680> you<00:57:12.799> are<00:57:12.920> running<00:57:13.240> the 00:57:13.390 --> 00:57:13.400 align:start position:0% unpredictable and you are running the 00:57:13.400 --> 00:57:17.069 align:start position:0% unpredictable and you are running the node<00:57:13.799> still<00:57:14.119> or<00:57:14.400> or<00:57:15.359> you<00:57:15.559> give<00:57:15.720> up<00:57:16.240> give<00:57:16.440> up<00:57:16.640> or 00:57:17.069 --> 00:57:17.079 align:start position:0% node still or or you give up give up or 00:57:17.079 --> 00:57:19.109 align:start position:0% node still or or you give up give up or I<00:57:17.200> did<00:57:17.400> for<00:57:17.520> it<00:57:17.640> some<00:57:17.880> time<00:57:18.119> I<00:57:18.280> did<00:57:18.680> okay 00:57:19.109 --> 00:57:19.119 align:start position:0% I did for it some time I did okay 00:57:19.119 --> 00:57:20.190 align:start position:0% I did for it some time I did okay because<00:57:19.280> it<00:57:19.400> was 00:57:20.190 --> 00:57:20.200 align:start position:0% because it was 00:57:20.200 --> 00:57:24.190 align:start position:0% because it was stabilized<00:57:21.200> so<00:57:21.400> it<00:57:21.559> stop<00:57:21.839> syn<00:57:22.200> it<00:57:22.599> it<00:57:23.119> uh<00:57:23.960> uh 00:57:24.190 --> 00:57:24.200 align:start position:0% stabilized so it stop syn it it uh uh 00:57:24.200 --> 00:57:26.750 align:start position:0% stabilized so it stop syn it it uh uh gets<00:57:24.480> out<00:57:24.880> Gets<00:57:25.119> behind<00:57:25.400> the<00:57:25.559> chain<00:57:25.960> and<00:57:26.440> keeps 00:57:26.750 --> 00:57:26.760 align:start position:0% gets out Gets behind the chain and keeps 00:57:26.760 --> 00:57:30.470 align:start position:0% gets out Gets behind the chain and keeps up<00:57:27.280> behind<00:57:28.119> Okay<00:57:28.440> exact<00:57:28.839> so<00:57:29.440> you<00:57:29.559> know<00:57:30.240> I<00:57:30.400> I 00:57:30.470 --> 00:57:30.480 align:start position:0% up behind Okay exact so you know I I 00:57:30.480 --> 00:57:32.589 align:start position:0% up behind Okay exact so you know I I don't<00:57:30.599> know<00:57:30.799> what<00:57:31.680> what<00:57:31.839> was<00:57:32.079> exactly<00:57:32.480> the 00:57:32.589 --> 00:57:32.599 align:start position:0% don't know what what was exactly the 00:57:32.599 --> 00:57:34.510 align:start position:0% don't know what what was exactly the source<00:57:32.880> of<00:57:33.039> the<00:57:33.280> problem<00:57:33.720> but<00:57:34.000> you<00:57:34.119> know<00:57:34.319> from 00:57:34.510 --> 00:57:34.520 align:start position:0% source of the problem but you know from 00:57:34.520 --> 00:57:37.270 align:start position:0% source of the problem but you know from time<00:57:34.720> to<00:57:35.000> time<00:57:36.000> it<00:57:36.079> would<00:57:36.319> just<00:57:36.599> like<00:57:36.960> you<00:57:37.079> know 00:57:37.270 --> 00:57:37.280 align:start position:0% time to time it would just like you know 00:57:37.280 --> 00:57:39.710 align:start position:0% time to time it would just like you know either<00:57:37.480> be<00:57:37.680> very<00:57:37.839> slow<00:57:38.559> probably<00:57:39.160> or<00:57:39.319> I<00:57:39.440> needed 00:57:39.710 --> 00:57:39.720 align:start position:0% either be very slow probably or I needed 00:57:39.720 --> 00:57:43.230 align:start position:0% either be very slow probably or I needed to<00:57:39.960> reset<00:57:40.559> the<00:57:41.000> the<00:57:41.200> 5G<00:57:41.680> router<00:57:42.559> so<00:57:42.720> I<00:57:43.039> had<00:57:43.160> to 00:57:43.230 --> 00:57:43.240 align:start position:0% to reset the the 5G router so I had to 00:57:43.240 --> 00:57:46.750 align:start position:0% to reset the the 5G router so I had to create<00:57:43.559> a<00:57:44.319> a<00:57:44.480> script<00:57:44.880> that<00:57:45.280> you<00:57:45.400> know<00:57:46.200> detected 00:57:46.750 --> 00:57:46.760 align:start position:0% create a a script that you know detected 00:57:46.760 --> 00:57:49.109 align:start position:0% create a a script that you know detected it<00:57:47.200> turn<00:57:47.480> off<00:57:47.640> the<00:57:47.839> plug<00:57:48.119> and<00:57:48.280> turn<00:57:48.480> it<00:57:48.640> back<00:57:48.799> on 00:57:49.109 --> 00:57:49.119 align:start position:0% it turn off the plug and turn it back on 00:57:49.119 --> 00:57:51.109 align:start position:0% it turn off the plug and turn it back on to<00:57:49.359> another<00:57:49.680> Wi-Fi<00:57:50.240> so<00:57:50.400> it<00:57:50.480> was<00:57:50.680> like<00:57:50.799> a<00:57:50.920> little 00:57:51.109 --> 00:57:51.119 align:start position:0% to another Wi-Fi so it was like a little 00:57:51.119 --> 00:57:53.190 align:start position:0% to another Wi-Fi so it was like a little bit<00:57:51.520> n<00:57:51.720> that's<00:57:51.920> impossible<00:57:52.440> yeah<00:57:52.839> yeah<00:57:53.000> so<00:57:53.119> I 00:57:53.190 --> 00:57:53.200 align:start position:0% bit n that's impossible yeah yeah so I 00:57:53.200 --> 00:57:55.430 align:start position:0% bit n that's impossible yeah yeah so I was<00:57:53.359> like<00:57:53.559> this<00:57:53.680> is<00:57:53.880> not<00:57:54.440> like<00:57:54.920> stable<00:57:55.280> and 00:57:55.430 --> 00:57:55.440 align:start position:0% was like this is not like stable and 00:57:55.440 --> 00:57:58.510 align:start position:0% was like this is not like stable and reliable<00:57:55.920> so<00:57:56.200> so<00:57:56.319> I<00:57:56.480> kind<00:57:56.599> of<00:57:56.760> gave<00:57:57.079> up<00:57:58.079> but<00:57:58.319> for 00:57:58.510 --> 00:57:58.520 align:start position:0% reliable so so I kind of gave up but for 00:57:58.520 --> 00:58:00.430 align:start position:0% reliable so so I kind of gave up but for a<00:57:58.680> moment<00:57:59.079> it<00:57:59.200> felt<00:57:59.440> like<00:57:59.599> it<00:57:59.720> was<00:57:59.920> really<00:58:00.160> good 00:58:00.430 --> 00:58:00.440 align:start position:0% a moment it felt like it was really good 00:58:00.440 --> 00:58:03.150 align:start position:0% a moment it felt like it was really good cuz<00:58:00.680> getting<00:58:01.079> 200<00:58:01.319> megabits<00:58:02.240> per<00:58:02.480> second<00:58:03.000> you 00:58:03.150 --> 00:58:03.160 align:start position:0% cuz getting 200 megabits per second you 00:58:03.160 --> 00:58:05.150 align:start position:0% cuz getting 200 megabits per second you know<00:58:03.680> syncing<00:58:04.160> and<00:58:04.359> download<00:58:04.760> which<00:58:04.880> is<00:58:05.000> more 00:58:05.150 --> 00:58:05.160 align:start position:0% know syncing and download which is more 00:58:05.160 --> 00:58:07.910 align:start position:0% know syncing and download which is more than<00:58:05.400> enough<00:58:05.640> for<00:58:05.839> for<00:58:06.000> it<00:58:06.119> to<00:58:06.760> operate<00:58:07.760> thank 00:58:07.910 --> 00:58:07.920 align:start position:0% than enough for for it to operate thank 00:58:07.920 --> 00:58:12.270 align:start position:0% than enough for for it to operate thank you<00:58:08.039> for 00:58:12.270 --> 00:58:12.280 align:start position:0% 00:58:12.280 --> 00:58:16.870 align:start position:0% speaking<00:58:13.280> speed<00:58:13.920> you<00:58:15.240> reli 00:58:16.870 --> 00:58:16.880 align:start position:0% speaking speed you reli 00:58:16.880 --> 00:58:19.670 align:start position:0% speaking speed you reli uh<00:58:17.880> we<00:58:18.079> recommend<00:58:18.480> fiber<00:58:18.920> but<00:58:19.079> we're<00:58:19.319> aware 00:58:19.670 --> 00:58:19.680 align:start position:0% uh we recommend fiber but we're aware 00:58:19.680 --> 00:58:22.270 align:start position:0% uh we recommend fiber but we're aware that<00:58:20.079> uh<00:58:20.520> it's<00:58:20.720> not<00:58:20.960> available<00:58:21.720> in<00:58:22.000> all 00:58:22.270 --> 00:58:22.280 align:start position:0% that uh it's not available in all 00:58:22.280 --> 00:58:24.910 align:start position:0% that uh it's not available in all countries<00:58:22.960> but<00:58:23.319> uh<00:58:23.599> yeah 00:58:24.910 --> 00:58:24.920 align:start position:0% countries but uh yeah 00:58:24.920 --> 00:58:27.789 align:start position:0% countries but uh yeah uh<00:58:25.920> again<00:58:26.160> again<00:58:26.520> with<00:58:26.760> Network<00:58:27.200> have<00:58:27.400> to<00:58:27.520> say 00:58:27.789 --> 00:58:27.799 align:start position:0% uh again again with Network have to say 00:58:27.799 --> 00:58:32.589 align:start position:0% uh again again with Network have to say because<00:58:28.960> uh<00:58:29.960> uh<00:58:30.280> what<00:58:30.480> in<00:58:30.760> Spain<00:58:31.200> is<00:58:31.760> uh<00:58:32.200> slow 00:58:32.589 --> 00:58:32.599 align:start position:0% because uh uh what in Spain is uh slow 00:58:32.599 --> 00:58:34.589 align:start position:0% because uh uh what in Spain is uh slow Network<00:58:33.160> or<00:58:33.520> fast<00:58:33.760> Network<00:58:34.160> in<00:58:34.319> other 00:58:34.589 --> 00:58:34.599 align:start position:0% Network or fast Network in other 00:58:34.599 --> 00:58:39.029 align:start position:0% Network or fast Network in other countries<00:58:35.520> uh<00:58:36.079> I<00:58:36.359> I<00:58:37.200> we<00:58:37.400> we<00:58:37.520> were<00:58:38.200> uh<00:58:38.440> surprised 00:58:39.029 --> 00:58:39.039 align:start position:0% countries uh I I we we were uh surprised 00:58:39.039 --> 00:58:41.470 align:start position:0% countries uh I I we we were uh surprised because<00:58:39.480> uh<00:58:39.599> we<00:58:39.760> met<00:58:40.280> uh<00:58:40.520> afy<00:58:40.960> from<00:58:41.240> from 00:58:41.470 --> 00:58:41.480 align:start position:0% because uh we met uh afy from from 00:58:41.480 --> 00:58:44.630 align:start position:0% because uh we met uh afy from from Germany<00:58:42.359> and<00:58:43.119> he<00:58:43.319> told<00:58:43.599> us<00:58:43.880> that<00:58:44.280> uh<00:58:44.440> in 00:58:44.630 --> 00:58:44.640 align:start position:0% Germany and he told us that uh in 00:58:44.640 --> 00:58:48.270 align:start position:0% Germany and he told us that uh in Germany<00:58:45.039> is<00:58:45.359> awful<00:58:46.119> the<00:58:46.799> in<00:58:47.039> in<00:58:47.400> general<00:58:47.960> the 00:58:48.270 --> 00:58:48.280 align:start position:0% Germany is awful the in in general the 00:58:48.280 --> 00:58:50.589 align:start position:0% Germany is awful the in in general the the<00:58:48.760> the<00:58:48.920> internet<00:58:49.319> connections<00:58:49.960> and<00:58:50.240> it<00:58:50.359> was 00:58:50.589 --> 00:58:50.599 align:start position:0% the the internet connections and it was 00:58:50.599 --> 00:58:54.829 align:start position:0% the the internet connections and it was like<00:58:50.760> a<00:58:50.880> shock<00:58:51.319> because<00:58:52.319> you<00:58:53.119> don't<00:58:53.680> expect<00:58:54.079> to 00:58:54.829 --> 00:58:54.839 align:start position:0% like a shock because you don't expect to 00:58:54.839 --> 00:58:58.069 align:start position:0% like a shock because you don't expect to a<00:58:54.960> country<00:58:55.319> like<00:58:55.520> that<00:58:55.760> can<00:58:56.240> have<00:58:56.640> uh<00:58:57.480> uh<00:58:57.839> bad 00:58:58.069 --> 00:58:58.079 align:start position:0% a country like that can have uh uh bad 00:58:58.079 --> 00:59:00.270 align:start position:0% a country like that can have uh uh bad connections<00:58:58.520> to<00:58:58.680> the<00:58:58.839> Internet<00:58:59.359> so<00:59:00.000> yeah<00:59:00.119> it 00:59:00.270 --> 00:59:00.280 align:start position:0% connections to the Internet so yeah it 00:59:00.280 --> 00:59:03.349 align:start position:0% connections to the Internet so yeah it depends<00:59:00.599> a<00:59:00.760> lot<00:59:01.079> it<00:59:01.240> depends<00:59:01.520> a<00:59:01.640> lot<00:59:02.440> and<00:59:02.760> it's 00:59:03.349 --> 00:59:03.359 align:start position:0% depends a lot it depends a lot and it's 00:59:03.359 --> 00:59:06.029 align:start position:0% depends a lot it depends a lot and it's it's<00:59:03.680> it's<00:59:03.880> a<00:59:04.440> it's<00:59:04.559> not<00:59:04.720> only<00:59:05.400> it's<00:59:05.640> not<00:59:05.839> only 00:59:06.029 --> 00:59:06.039 align:start position:0% it's it's a it's not only it's not only 00:59:06.039 --> 00:59:10.230 align:start position:0% it's it's a it's not only it's not only speed<00:59:06.400> it's<00:59:06.559> latency<00:59:07.680> also<00:59:08.680> because<00:59:09.359> uh<00:59:10.000> I 00:59:10.230 --> 00:59:10.240 align:start position:0% speed it's latency also because uh I 00:59:10.240 --> 00:59:14.390 align:start position:0% speed it's latency also because uh I usually<00:59:10.720> have<00:59:11.200> uh<00:59:11.799> 100<00:59:12.240> megabits<00:59:12.960> at<00:59:13.400> home 00:59:14.390 --> 00:59:14.400 align:start position:0% usually have uh 100 megabits at home 00:59:14.400 --> 00:59:16.829 align:start position:0% usually have uh 100 megabits at home it's<00:59:14.680> the<00:59:14.920> lowest<00:59:15.400> speed<00:59:15.720> that<00:59:15.880> you<00:59:16.119> could 00:59:16.829 --> 00:59:16.839 align:start position:0% it's the lowest speed that you could 00:59:16.839 --> 00:59:21.150 align:start position:0% it's the lowest speed that you could could<00:59:17.839> H<00:59:18.799> with<00:59:19.039> fiber<00:59:19.440> in<00:59:19.599> Spain<00:59:20.599> 100<00:59:20.920> is<00:59:21.039> the 00:59:21.150 --> 00:59:21.160 align:start position:0% could H with fiber in Spain 100 is the 00:59:21.160 --> 00:59:23.950 align:start position:0% could H with fiber in Spain 100 is the lowest<00:59:21.680> and<00:59:22.039> I<00:59:22.160> used<00:59:22.400> to<00:59:22.599> have<00:59:22.760> it<00:59:23.000> because 00:59:23.950 --> 00:59:23.960 align:start position:0% lowest and I used to have it because 00:59:23.960 --> 00:59:25.589 align:start position:0% lowest and I used to have it because usually<00:59:24.319> in<00:59:24.440> my<00:59:24.640> daily<00:59:24.920> basis<00:59:25.160> I<00:59:25.280> don't<00:59:25.440> need 00:59:25.589 --> 00:59:25.599 align:start position:0% usually in my daily basis I don't need 00:59:25.599 --> 00:59:26.870 align:start position:0% usually in my daily basis I don't need more 00:59:26.870 --> 00:59:26.880 align:start position:0% more 00:59:26.880 --> 00:59:29.829 align:start position:0% more uh<00:59:27.079> but<00:59:27.640> when<00:59:27.799> I<00:59:28.039> started<00:59:28.480> to<00:59:29.160> to<00:59:29.359> work<00:59:29.640> with 00:59:29.829 --> 00:59:29.839 align:start position:0% uh but when I started to to work with 00:59:29.839 --> 00:59:34.549 align:start position:0% uh but when I started to to work with the<00:59:29.960> a<00:59:30.520> here<00:59:31.520> uh<00:59:31.720> at<00:59:31.839> the<00:59:32.039> end<00:59:33.039> 100<00:59:33.559> megabytes 00:59:34.549 --> 00:59:34.559 align:start position:0% the a here uh at the end 100 megabytes 00:59:34.559 --> 00:59:36.349 align:start position:0% the a here uh at the end 100 megabytes come<00:59:34.760> closer<00:59:35.160> if<00:59:35.319> you<00:59:35.400> are<00:59:35.520> running<00:59:36.000> more<00:59:36.200> than 00:59:36.349 --> 00:59:36.359 align:start position:0% come closer if you are running more than 00:59:36.359 --> 00:59:39.069 align:start position:0% come closer if you are running more than one<00:59:36.640> note<00:59:37.640> with<00:59:37.839> one<00:59:38.000> note<00:59:38.240> you<00:59:38.319> are<00:59:38.559> okay<00:59:38.880> no 00:59:39.069 --> 00:59:39.079 align:start position:0% one note with one note you are okay no 00:59:39.079 --> 00:59:42.109 align:start position:0% one note with one note you are okay no problem<00:59:39.599> you<00:59:39.720> will<00:59:39.880> s<00:59:40.839> maybe<00:59:41.119> you<00:59:41.240> will<00:59:41.480> last<00:59:41.839> a 00:59:42.109 --> 00:59:42.119 align:start position:0% problem you will s maybe you will last a 00:59:42.119 --> 00:59:44.230 align:start position:0% problem you will s maybe you will last a little<00:59:42.400> longer<00:59:42.799> but<00:59:42.960> it<00:59:43.079> will<00:59:43.280> sink<00:59:44.000> at<00:59:44.119> the 00:59:44.230 --> 00:59:44.240 align:start position:0% little longer but it will sink at the 00:59:44.240 --> 00:59:47.190 align:start position:0% little longer but it will sink at the end<00:59:44.520> it<00:59:44.640> will<00:59:44.839> works<00:59:45.760> but<00:59:46.039> when<00:59:46.319> you<00:59:46.480> start<00:59:46.799> to 00:59:47.190 --> 00:59:47.200 align:start position:0% end it will works but when you start to 00:59:47.200 --> 00:59:49.829 align:start position:0% end it will works but when you start to to<00:59:47.400> play<00:59:47.640> with<00:59:48.200> two<00:59:48.559> three<00:59:48.839> four<00:59:49.160> five<00:59:49.400> notes 00:59:49.829 --> 00:59:49.839 align:start position:0% to play with two three four five notes 00:59:49.839 --> 00:59:54.430 align:start position:0% to play with two three four five notes it's<00:59:50.400> not<00:59:50.640> not<00:59:51.079> enough<00:59:52.079> okay 00:59:54.430 --> 00:59:54.440 align:start position:0% 00:59:54.440 --> 00:59:56.789 align:start position:0% uh<00:59:55.440> uh 00:59:56.789 --> 00:59:56.799 align:start position:0% uh uh 00:59:56.799 --> 00:59:58.789 align:start position:0% uh uh I<00:59:56.920> don't<00:59:57.079> know<00:59:57.400> five<00:59:57.799> six<00:59:58.280> something<00:59:58.599> like 00:59:58.789 --> 00:59:58.799 align:start position:0% I don't know five six something like 00:59:58.799 --> 01:00:00.789 align:start position:0% I don't know five six something like this<00:59:59.079> but 01:00:00.789 --> 01:00:00.799 align:start position:0% this but 01:00:00.799 --> 01:00:05.789 align:start position:0% this but uh<01:00:01.799> yes<01:00:02.039> notes<01:00:03.039> Notes<01:00:03.440> too<01:00:03.839> oh<01:00:04.079> I<01:00:04.280> run<01:00:05.280> maybe<01:00:05.480> 7 01:00:05.789 --> 01:00:05.799 align:start position:0% uh yes notes Notes too oh I run maybe 7 01:00:05.799 --> 01:00:08.510 align:start position:0% uh yes notes Notes too oh I run maybe 7 eight<01:00:06.240> at<01:00:06.480> home<01:00:06.760> I<01:00:06.920> have<01:00:07.160> 300 01:00:08.510 --> 01:00:08.520 align:start position:0% eight at home I have 300 01:00:08.520 --> 01:00:11.230 align:start position:0% eight at home I have 300 megabits<01:00:09.520> I<01:00:09.680> have<01:00:09.920> 1<01:00:10.160> terabyte<01:00:10.760> right<01:00:10.880> now<01:00:11.079> at 01:00:11.230 --> 01:00:11.240 align:start position:0% megabits I have 1 terabyte right now at 01:00:11.240 --> 01:00:14.270 align:start position:0% megabits I have 1 terabyte right now at home<01:00:11.760> and<01:00:12.119> the<01:00:12.280> difference<01:00:12.680> is<01:00:12.920> huge<01:00:13.359> in<01:00:13.599> times 01:00:14.270 --> 01:00:14.280 align:start position:0% home and the difference is huge in times 01:00:14.280 --> 01:00:16.430 align:start position:0% home and the difference is huge in times and<01:00:14.400> you<01:00:14.520> know<01:00:14.880> you<01:00:15.079> have<01:00:15.319> in<01:00:15.480> your<01:00:16.119> you<01:00:16.280> have 01:00:16.430 --> 01:00:16.440 align:start position:0% and you know you have in your you have 01:00:16.440 --> 01:00:19.150 align:start position:0% and you know you have in your you have at<01:00:16.640> home<01:00:16.880> Netflix<01:00:17.400> Ando<01:00:18.319> and<01:00:18.640> you<01:00:18.760> are 01:00:19.150 --> 01:00:19.160 align:start position:0% at home Netflix Ando and you are 01:00:19.160 --> 01:00:23.390 align:start position:0% at home Netflix Ando and you are watching<01:00:19.640> shows<01:00:20.160> and<01:00:21.079> it<01:00:21.400> it<01:00:21.559> runs<01:00:22.000> well<01:00:22.440> so 01:00:23.390 --> 01:00:23.400 align:start position:0% watching shows and it it runs well so 01:00:23.400 --> 01:00:27.230 align:start position:0% watching shows and it it runs well so yeah<01:00:24.240> I<01:00:24.319> think 01:00:27.230 --> 01:00:27.240 align:start position:0% yeah I think 01:00:27.240 --> 01:00:30.670 align:start position:0% yeah I think sorry<01:00:28.240> can<01:00:28.359> you<01:00:28.480> use<01:00:28.799> with<01:00:29.039> VPN<01:00:30.039> VPN 01:00:30.670 --> 01:00:30.680 align:start position:0% sorry can you use with VPN VPN 01:00:30.680 --> 01:00:32.230 align:start position:0% sorry can you use with VPN VPN externally<01:00:31.200> to<01:00:31.400> the 01:00:32.230 --> 01:00:32.240 align:start position:0% externally to the 01:00:32.240 --> 01:00:35.390 align:start position:0% externally to the device<01:00:33.240> you<01:00:33.400> can<01:00:33.680> but<01:00:33.960> uh<01:00:34.240> it's<01:00:34.480> not<01:00:35.039> uh<01:00:35.240> it's 01:00:35.390 --> 01:00:35.400 align:start position:0% device you can but uh it's not uh it's 01:00:35.400 --> 01:00:41.630 align:start position:0% device you can but uh it's not uh it's not<01:00:35.680> necessary<01:00:36.640> to 01:00:41.630 --> 01:00:41.640 align:start position:0% 01:00:41.640 --> 01:00:47.390 align:start position:0% use<01:00:42.640> yeah<01:00:42.920> no<01:00:43.359> it's<01:00:44.039> uh<01:00:44.960> I<01:00:45.200> I<01:00:45.319> don't<01:00:45.760> I<01:00:45.880> don't<01:00:46.440> um 01:00:47.390 --> 01:00:47.400 align:start position:0% use yeah no it's uh I I don't I don't um 01:00:47.400 --> 01:00:51.309 align:start position:0% use yeah no it's uh I I don't I don't um I<01:00:47.480> don't<01:00:48.400> uh<01:00:49.119> um<01:00:49.400> do<01:00:49.640> anything<01:00:50.400> uh<01:00:50.640> particular 01:00:51.309 --> 01:00:51.319 align:start position:0% I don't uh um do anything uh particular 01:00:51.319 --> 01:00:58.990 align:start position:0% I don't uh um do anything uh particular I<01:00:51.440> mean<01:00:52.440> it's<01:00:53.440> the<01:00:54.079> stock<01:00:55.079> stock<01:00:55.319> one 01:00:58.990 --> 01:00:59.000 align:start position:0% 01:00:59.000 --> 01:01:01.870 align:start position:0% okay<01:00:59.599> uh<01:01:00.240> the<01:01:00.319> only<01:01:00.520> thing<01:01:00.799> I<01:01:00.960> I<01:01:01.039> don't<01:01:01.280> hear<01:01:01.520> is 01:01:01.870 --> 01:01:01.880 align:start position:0% okay uh the only thing I I don't hear is 01:01:01.880 --> 01:01:05.270 align:start position:0% okay uh the only thing I I don't hear is start<01:01:02.280> two<01:01:02.520> Services<01:01:03.359> get<01:01:04.359> uh 01:01:05.270 --> 01:01:05.280 align:start position:0% start two Services get uh 01:01:05.280 --> 01:01:08.990 align:start position:0% start two Services get uh nimus<01:01:06.280> the<01:01:06.440> nimus<01:01:06.799> Lo<01:01:07.079> so<01:01:08.079> can<01:01:08.200> you<01:01:08.319> show<01:01:08.720> the 01:01:08.990 --> 01:01:09.000 align:start position:0% nimus the nimus Lo so can you show the 01:01:09.000 --> 01:01:13.589 align:start position:0% nimus the nimus Lo so can you show the the<01:01:09.720> both<01:01:10.319> uh<01:01:11.079> commands 01:01:13.589 --> 01:01:13.599 align:start position:0% the both uh commands 01:01:13.599 --> 01:01:19.109 align:start position:0% the both uh commands yes<01:01:14.599> uh<01:01:14.960> start<01:01:16.160> consensus<01:01:17.160> c<01:01:17.880> um<01:01:18.440> I<01:01:18.599> think<01:01:18.920> we 01:01:19.109 --> 01:01:19.119 align:start position:0% yes uh start consensus c um I think we 01:01:19.119 --> 01:01:23.390 align:start position:0% yes uh start consensus c um I think we are<01:01:19.880> no<01:01:20.079> I<01:01:20.200> started<01:01:20.680> nether<01:01:21.160> M<01:01:22.160> okay<01:01:22.440> nether<01:01:22.799> M 01:01:23.390 --> 01:01:23.400 align:start position:0% are no I started nether M okay nether M 01:01:23.400 --> 01:01:27.349 align:start position:0% are no I started nether M okay nether M and<01:01:24.000> anus<01:01:24.920> and<01:01:26.079> is<01:01:26.319> starting<01:01:26.640> to<01:01:26.760> sync<01:01:27.119> right 01:01:27.349 --> 01:01:27.359 align:start position:0% and anus and is starting to sync right 01:01:27.359 --> 01:01:30.829 align:start position:0% and anus and is starting to sync right now<01:01:28.359> so<01:01:28.520> you<01:01:28.680> once<01:01:29.000> boot<01:01:29.599> with<01:01:29.839> the<01:01:30.160> with<01:01:30.280> a<01:01:30.440> new 01:01:30.829 --> 01:01:30.839 align:start position:0% now so you once boot with the with a new 01:01:30.839 --> 01:01:33.309 align:start position:0% now so you once boot with the with a new node<01:01:31.359> uh<01:01:31.480> you<01:01:31.640> just<01:01:32.160> have<01:01:32.319> to<01:01:32.480> start<01:01:33.079> two 01:01:33.309 --> 01:01:33.319 align:start position:0% node uh you just have to start two 01:01:33.319 --> 01:01:35.630 align:start position:0% node uh you just have to start two services<01:01:33.960> and<01:01:34.359> you<01:01:34.559> have 01:01:35.630 --> 01:01:35.640 align:start position:0% services and you have 01:01:35.640 --> 01:01:39.309 align:start position:0% services and you have a<01:01:36.640> h<01:01:36.760> you<01:01:36.880> will<01:01:37.079> have<01:01:37.240> a<01:01:37.359> Noe<01:01:37.680> in<01:01:38.039> several<01:01:38.480> hours 01:01:39.309 --> 01:01:39.319 align:start position:0% a h you will have a Noe in several hours 01:01:39.319 --> 01:01:42.630 align:start position:0% a h you will have a Noe in several hours depends<01:01:39.760> on<01:01:40.319> on<01:01:40.839> network<01:01:41.480> conditions<01:01:42.200> this 01:01:42.630 --> 01:01:42.640 align:start position:0% depends on on network conditions this 01:01:42.640 --> 01:01:45.109 align:start position:0% depends on on network conditions this this<01:01:43.280> wi-fi<01:01:43.680> is<01:01:44.039> quite<01:01:44.280> fast<01:01:44.559> it's<01:01:44.720> faster 01:01:45.109 --> 01:01:45.119 align:start position:0% this wi-fi is quite fast it's faster 01:01:45.119 --> 01:01:47.710 align:start position:0% this wi-fi is quite fast it's faster than<01:01:45.520> the<01:01:46.520> the<01:01:46.760> the<01:01:46.920> public<01:01:47.280> the<01:01:47.400> General 01:01:47.710 --> 01:01:47.720 align:start position:0% than the the the public the General 01:01:47.720 --> 01:01:50.109 align:start position:0% than the the the public the General Public<01:01:48.000> Access<01:01:48.319> so<01:01:48.559> probably<01:01:48.920> here<01:01:49.160> in<01:01:49.880> four 01:01:50.109 --> 01:01:50.119 align:start position:0% Public Access so probably here in four 01:01:50.119 --> 01:01:53.349 align:start position:0% Public Access so probably here in four five<01:01:50.319> hours<01:01:50.680> you're<01:01:50.920> good<01:01:51.079> to<01:01:51.559> go<01:01:52.559> so<01:01:53.039> at<01:01:53.200> the 01:01:53.349 --> 01:01:53.359 align:start position:0% five hours you're good to go so at the 01:01:53.359 --> 01:01:59.750 align:start position:0% five hours you're good to go so at the end<01:01:53.599> of<01:01:53.799> this<01:01:54.400> uh<01:01:54.839> when<01:01:56.160> consensus<01:01:57.559> uh<01:01:58.760> when 01:01:59.750 --> 01:01:59.760 align:start position:0% end of this uh when consensus uh when 01:01:59.760 --> 01:02:02.789 align:start position:0% end of this uh when consensus uh when nether<01:02:00.119> mind<01:02:00.520> and<01:02:01.119> and<01:02:01.559> thinking<01:02:02.559> uh<01:02:02.680> you 01:02:02.789 --> 01:02:02.799 align:start position:0% nether mind and and thinking uh you 01:02:02.799 --> 01:02:05.470 align:start position:0% nether mind and and thinking uh you could<01:02:03.039> start<01:02:03.960> what<01:02:04.079> we<01:02:04.240> call<01:02:04.400> a<01:02:04.559> super<01:02:04.799> note<01:02:05.160> we 01:02:05.470 --> 01:02:05.480 align:start position:0% could start what we call a super note we 01:02:05.480 --> 01:02:07.029 align:start position:0% could start what we call a super note we are<01:02:05.720> going<01:02:05.880> to<01:02:06.079> start 01:02:07.029 --> 01:02:07.039 align:start position:0% are going to start 01:02:07.039 --> 01:02:09.630 align:start position:0% are going to start op<01:02:08.039> yeah<01:02:08.240> we<01:02:08.359> will<01:02:08.559> start<01:02:08.799> a<01:02:08.920> super<01:02:09.200> note<01:02:09.480> it 01:02:09.630 --> 01:02:09.640 align:start position:0% op yeah we will start a super note it 01:02:09.640 --> 01:02:13.910 align:start position:0% op yeah we will start a super note it won't<01:02:09.960> work<01:02:10.440> because<01:02:11.440> you<01:02:11.640> need<01:02:11.880> an<01:02:12.079> L1<01:02:12.920> synet 01:02:13.910 --> 01:02:13.920 align:start position:0% won't work because you need an L1 synet 01:02:13.920 --> 01:02:16.630 align:start position:0% won't work because you need an L1 synet which<01:02:14.440> uh<01:02:14.599> is<01:02:14.720> not<01:02:14.960> happening<01:02:15.359> now<01:02:16.279> uh<01:02:16.400> but<01:02:16.520> we 01:02:16.630 --> 01:02:16.640 align:start position:0% which uh is not happening now uh but we 01:02:16.640 --> 01:02:18.269 align:start position:0% which uh is not happening now uh but we will<01:02:16.760> show<01:02:17.079> the<01:02:17.240> configuration<01:02:17.880> files 01:02:18.269 --> 01:02:18.279 align:start position:0% will show the configuration files 01:02:18.279 --> 01:02:20.910 align:start position:0% will show the configuration files because<01:02:18.520> we<01:02:18.640> need<01:02:18.880> to<01:02:19.440> to<01:02:19.640> change<01:02:20.359> a<01:02:20.480> couple<01:02:20.720> of 01:02:20.910 --> 01:02:20.920 align:start position:0% because we need to to change a couple of 01:02:20.920 --> 01:02:23.910 align:start position:0% because we need to to change a couple of parameters<01:02:21.599> it's<01:02:22.240> everything<01:02:22.559> it's<01:02:22.839> in<01:02:23.039> our 01:02:23.910 --> 01:02:23.920 align:start position:0% parameters it's everything it's in our 01:02:23.920 --> 01:02:26.589 align:start position:0% parameters it's everything it's in our uh<01:02:24.440> in<01:02:24.559> our<01:02:24.799> documentation<01:02:25.440> page 01:02:26.589 --> 01:02:26.599 align:start position:0% uh in our documentation page 01:02:26.599 --> 01:02:29.470 align:start position:0% uh in our documentation page so<01:02:27.599> I<01:02:27.680> have<01:02:27.799> a<01:02:28.039> question<01:02:28.319> there<01:02:28.480> about<01:02:28.799> updates 01:02:29.470 --> 01:02:29.480 align:start position:0% so I have a question there about updates 01:02:29.480 --> 01:02:31.670 align:start position:0% so I have a question there about updates so<01:02:29.799> when<01:02:30.400> there's<01:02:30.599> a<01:02:30.760> new<01:02:31.000> chain<01:02:31.279> Fork 01:02:31.670 --> 01:02:31.680 align:start position:0% so when there's a new chain Fork 01:02:31.680 --> 01:02:33.710 align:start position:0% so when there's a new chain Fork happening<01:02:32.279> and<01:02:32.440> you<01:02:32.559> need<01:02:32.680> to<01:02:32.920> update<01:02:33.359> before 01:02:33.710 --> 01:02:33.720 align:start position:0% happening and you need to update before 01:02:33.720 --> 01:02:35.990 align:start position:0% happening and you need to update before that<01:02:34.119> like<01:02:34.839> is<01:02:34.960> that<01:02:35.359> is<01:02:35.480> some<01:02:35.640> of<01:02:35.799> that 01:02:35.990 --> 01:02:36.000 align:start position:0% that like is that is some of that 01:02:36.000 --> 01:02:38.109 align:start position:0% that like is that is some of that automated<01:02:36.559> because<01:02:36.760> it's<01:02:36.960> dbn<01:02:37.440> packages<01:02:38.000> is 01:02:38.109 --> 01:02:38.119 align:start position:0% automated because it's dbn packages is 01:02:38.119 --> 01:02:39.870 align:start position:0% automated because it's dbn packages is there<01:02:38.319> like<01:02:38.440> a<01:02:38.559> crown<01:02:38.960> tab<01:02:39.240> that<01:02:39.359> you<01:02:39.680> have 01:02:39.870 --> 01:02:39.880 align:start position:0% there like a crown tab that you have 01:02:39.880 --> 01:02:41.910 align:start position:0% there like a crown tab that you have already<01:02:40.200> in<01:02:40.359> your<01:02:40.640> recommendations<01:02:41.400> or<01:02:41.640> like 01:02:41.910 --> 01:02:41.920 align:start position:0% already in your recommendations or like 01:02:41.920 --> 01:02:43.269 align:start position:0% already in your recommendations or like maybe<01:02:42.079> you<01:02:42.200> can<01:02:42.319> talk<01:02:42.520> about<01:02:42.839> how<01:02:42.960> long<01:02:43.160> does 01:02:43.269 --> 01:02:43.279 align:start position:0% maybe you can talk about how long does 01:02:43.279 --> 01:02:45.630 align:start position:0% maybe you can talk about how long does it<01:02:43.400> need<01:02:43.520> to<01:02:43.640> be<01:02:43.839> down<01:02:44.240> should<01:02:44.440> I<01:02:44.720> check<01:02:45.160> weekly 01:02:45.630 --> 01:02:45.640 align:start position:0% it need to be down should I check weekly 01:02:45.640 --> 01:02:47.190 align:start position:0% it need to be down should I check weekly or<01:02:45.799> like<01:02:46.319> some<01:02:46.480> of 01:02:47.190 --> 01:02:47.200 align:start position:0% or like some of 01:02:47.200 --> 01:02:51.549 align:start position:0% or like some of that<01:02:48.200> J<01:02:49.039> use<01:02:49.359> the<01:02:49.520> dean<01:02:49.920> automatic<01:02:50.799> updates 01:02:51.549 --> 01:02:51.559 align:start position:0% that J use the dean automatic updates 01:02:51.559 --> 01:02:53.670 align:start position:0% that J use the dean automatic updates but<01:02:51.760> we<01:02:51.920> don't<01:02:52.279> start<01:02:52.520> it<01:02:52.720> by<01:02:52.880> default<01:02:53.559> we 01:02:53.670 --> 01:02:53.680 align:start position:0% but we don't start it by default we 01:02:53.680 --> 01:02:57.589 align:start position:0% but we don't start it by default we don't<01:02:53.920> want<01:02:54.599> uh<01:02:54.720> to<01:02:56.160> uh<01:02:56.279> forc<01:02:56.640> you<01:02:56.799> to<01:02:57.319> to 01:02:57.589 --> 01:02:57.599 align:start position:0% don't want uh to uh forc you to to 01:02:57.599 --> 01:02:59.750 align:start position:0% don't want uh to uh forc you to to upgrade<01:02:58.079> anything<01:02:58.520> because<01:02:58.839> you<01:02:59.200> could<01:02:59.480> be 01:02:59.750 --> 01:02:59.760 align:start position:0% upgrade anything because you could be 01:02:59.760 --> 01:03:02.470 align:start position:0% upgrade anything because you could be start<01:03:00.039> working<01:03:00.559> in<01:03:01.039> in<01:03:01.200> a<01:03:01.440> version<01:03:01.799> for<01:03:02.119> some 01:03:02.470 --> 01:03:02.480 align:start position:0% start working in in a version for some 01:03:02.480 --> 01:03:04.829 align:start position:0% start working in in a version for some several<01:03:02.920> reasons<01:03:03.279> so<01:03:03.599> at<01:03:03.799> the<01:03:03.920> end<01:03:04.520> most<01:03:04.720> of 01:03:04.829 --> 01:03:04.839 align:start position:0% several reasons so at the end most of 01:03:04.839 --> 01:03:06.230 align:start position:0% several reasons so at the end most of the 01:03:06.230 --> 01:03:06.240 align:start position:0% the 01:03:06.240 --> 01:03:09.950 align:start position:0% the people<01:03:07.240> uh<01:03:07.520> tends<01:03:07.880> to<01:03:08.119> wait<01:03:08.599> one<01:03:09.200> or<01:03:09.440> two 01:03:09.950 --> 01:03:09.960 align:start position:0% people uh tends to wait one or two 01:03:09.960 --> 01:03:12.069 align:start position:0% people uh tends to wait one or two versions<01:03:10.559> behind<01:03:11.079> not<01:03:11.319> in<01:03:11.480> the<01:03:11.640> top<01:03:11.839> of<01:03:11.960> the 01:03:12.069 --> 01:03:12.079 align:start position:0% versions behind not in the top of the 01:03:12.079 --> 01:03:13.910 align:start position:0% versions behind not in the top of the edge<01:03:12.319> version<01:03:12.680> because<01:03:13.319> sometimes<01:03:13.599> the<01:03:13.720> new 01:03:13.910 --> 01:03:13.920 align:start position:0% edge version because sometimes the new 01:03:13.920 --> 01:03:17.269 align:start position:0% edge version because sometimes the new versions<01:03:14.240> include<01:03:14.559> new<01:03:14.680> books<01:03:15.640> new<01:03:15.839> boxs<01:03:16.359> um 01:03:17.269 --> 01:03:17.279 align:start position:0% versions include new books new boxs um 01:03:17.279 --> 01:03:20.109 align:start position:0% versions include new books new boxs um and<01:03:17.559> we<01:03:17.680> are<01:03:18.000> not<01:03:18.880> we<01:03:19.000> think<01:03:19.240> that<01:03:19.480> it's<01:03:19.680> not 01:03:20.109 --> 01:03:20.119 align:start position:0% and we are not we think that it's not 01:03:20.119 --> 01:03:23.029 align:start position:0% and we are not we think that it's not very<01:03:20.559> polite<01:03:21.240> to<01:03:21.400> force<01:03:21.720> you<01:03:21.880> to<01:03:22.359> to<01:03:22.640> update 01:03:23.029 --> 01:03:23.039 align:start position:0% very polite to force you to to update 01:03:23.039 --> 01:03:26.269 align:start position:0% very polite to force you to to update your<01:03:23.480> packages<01:03:24.480> but<01:03:24.799> you<01:03:24.960> could<01:03:25.279> use<01:03:25.559> the<01:03:26.039> the 01:03:26.269 --> 01:03:26.279 align:start position:0% your packages but you could use the the 01:03:26.279 --> 01:03:28.589 align:start position:0% your packages but you could use the the deian<01:03:27.279> um<01:03:27.839> the 01:03:28.589 --> 01:03:28.599 align:start position:0% deian um the 01:03:28.599 --> 01:03:31.390 align:start position:0% deian um the deian<01:03:29.599> demon<01:03:30.119> to<01:03:30.760> to<01:03:30.920> upgrade<01:03:31.279> your 01:03:31.390 --> 01:03:31.400 align:start position:0% deian demon to to upgrade your 01:03:31.400 --> 01:03:34.950 align:start position:0% deian demon to to upgrade your packageing<01:03:31.760> in<01:03:31.920> automatic<01:03:32.440> way<01:03:32.960> we<01:03:33.319> will<01:03:34.319> uh 01:03:34.950 --> 01:03:34.960 align:start position:0% packageing in automatic way we will uh 01:03:34.960 --> 01:03:38.430 align:start position:0% packageing in automatic way we will uh we<01:03:35.680> usually<01:03:36.680> uh<01:03:36.839> update<01:03:37.160> the<01:03:37.319> repository<01:03:38.319> the 01:03:38.430 --> 01:03:38.440 align:start position:0% we usually uh update the repository the 01:03:38.440 --> 01:03:41.109 align:start position:0% we usually uh update the repository the same<01:03:38.799> day<01:03:39.039> or<01:03:39.400> the<01:03:39.920> one<01:03:40.119> or<01:03:40.240> two<01:03:40.480> days<01:03:40.720> that<01:03:40.960> the 01:03:41.109 --> 01:03:41.119 align:start position:0% same day or the one or two days that the 01:03:41.119 --> 01:03:43.430 align:start position:0% same day or the one or two days that the new<01:03:41.319> version<01:03:41.880> arrives<01:03:42.440> so<01:03:42.799> you<01:03:42.920> will<01:03:43.160> have 01:03:43.430 --> 01:03:43.440 align:start position:0% new version arrives so you will have 01:03:43.440 --> 01:03:46.549 align:start position:0% new version arrives so you will have always<01:03:43.839> the<01:03:44.039> the<01:03:44.200> latest<01:03:44.559> version<01:03:45.240> yeah<01:03:45.839> we 01:03:46.549 --> 01:03:46.559 align:start position:0% always the the latest version yeah we 01:03:46.559 --> 01:03:48.910 align:start position:0% always the the latest version yeah we usually<01:03:47.000> announce<01:03:47.359> the<01:03:47.760> the<01:03:47.920> releases<01:03:48.440> of<01:03:48.760> of 01:03:48.910 --> 01:03:48.920 align:start position:0% usually announce the the releases of of 01:03:48.920 --> 01:03:51.670 align:start position:0% usually announce the the releases of of new<01:03:49.119> packages<01:03:49.559> on<01:03:49.880> on<01:03:50.079> our<01:03:50.319> t<01:03:50.760> account<01:03:51.279> so<01:03:51.559> you 01:03:51.670 --> 01:03:51.680 align:start position:0% new packages on on our t account so you 01:03:51.680 --> 01:03:56.990 align:start position:0% new packages on on our t account so you can<01:03:51.839> see<01:03:52.119> that<01:03:53.160> there<01:03:54.160> so<01:03:54.799> um 01:03:56.990 --> 01:03:57.000 align:start position:0% can see that there so um 01:03:57.000 --> 01:03:59.190 align:start position:0% can see that there so um we<01:03:57.200> just<01:03:57.359> need<01:03:57.799> because<01:03:58.079> we<01:03:58.200> are<01:03:58.359> running<01:03:59.000> uh 01:03:59.190 --> 01:03:59.200 align:start position:0% we just need because we are running uh 01:03:59.200 --> 01:04:03.029 align:start position:0% we just need because we are running uh both<01:03:59.880> uh<01:04:00.000> L1<01:04:00.440> and<01:04:00.599> L2<01:04:01.000> in<01:04:01.160> the<01:04:01.319> same<01:04:01.960> um<01:04:02.720> in<01:04:02.880> the 01:04:03.029 --> 01:04:03.039 align:start position:0% both uh L1 and L2 in the same um in the 01:04:03.039 --> 01:04:06.230 align:start position:0% both uh L1 and L2 in the same um in the same<01:04:03.440> uh<01:04:03.599> device<01:04:04.440> we<01:04:04.599> just<01:04:04.960> going<01:04:05.119> to<01:04:05.279> put<01:04:05.520> Here 01:04:06.230 --> 01:04:06.240 align:start position:0% same uh device we just going to put Here 01:04:06.240 --> 01:04:07.349 align:start position:0% same uh device we just going to put Here Local 01:04:07.349 --> 01:04:07.359 align:start position:0% Local 01:04:07.359 --> 01:04:10.349 align:start position:0% Local Host<01:04:08.359> yeah<01:04:08.720> he<01:04:08.920> he<01:04:09.119> can<01:04:09.319> use<01:04:09.559> Local<01:04:09.920> Host 01:04:10.349 --> 01:04:10.359 align:start position:0% Host yeah he he can use Local Host 01:04:10.359 --> 01:04:11.910 align:start position:0% Host yeah he he can use Local Host because<01:04:10.720> one<01:04:10.920> of<01:04:11.079> the<01:04:11.200> software<01:04:11.599> that<01:04:11.760> we 01:04:11.910 --> 01:04:11.920 align:start position:0% because one of the software that we 01:04:11.920 --> 01:04:15.190 align:start position:0% because one of the software that we provide<01:04:12.200> here<01:04:12.359> is<01:04:12.480> an<01:04:12.640> N<01:04:13.440> server<01:04:14.440> Runing<01:04:14.839> as<01:04:15.000> a 01:04:15.190 --> 01:04:15.200 align:start position:0% provide here is an N server Runing as a 01:04:15.200 --> 01:04:17.470 align:start position:0% provide here is an N server Runing as a proxy<01:04:15.960> because<01:04:16.319> most<01:04:16.480> of<01:04:16.680> the<01:04:16.920> time<01:04:17.240> that 01:04:17.470 --> 01:04:17.480 align:start position:0% proxy because most of the time that 01:04:17.480 --> 01:04:19.950 align:start position:0% proxy because most of the time that people<01:04:18.240> that<01:04:18.400> run<01:04:18.720> not<01:04:18.920> a<01:04:19.119> home<01:04:19.400> they<01:04:19.520> want<01:04:19.760> to 01:04:19.950 --> 01:04:19.960 align:start position:0% people that run not a home they want to 01:04:19.960 --> 01:04:22.670 align:start position:0% people that run not a home they want to access<01:04:20.200> to<01:04:20.359> the<01:04:20.559> API<01:04:21.559> of<01:04:21.720> the<01:04:21.880> client<01:04:22.240> in<01:04:22.359> order 01:04:22.670 --> 01:04:22.680 align:start position:0% access to the API of the client in order 01:04:22.680 --> 01:04:26.190 align:start position:0% access to the API of the client in order to<01:04:23.400> do<01:04:23.760> the<01:04:24.039> work<01:04:24.400> or 01:04:26.190 --> 01:04:26.200 align:start position:0% to do the work or 01:04:26.200 --> 01:04:28.549 align:start position:0% to do the work or check<01:04:26.640> anything<01:04:27.079> in<01:04:27.319> the<01:04:27.640> in<01:04:27.880> the<01:04:28.319> in<01:04:28.440> the 01:04:28.549 --> 01:04:28.559 align:start position:0% check anything in the in the in the 01:04:28.559 --> 01:04:31.670 align:start position:0% check anything in the in the in the blockchain<01:04:29.319> so<01:04:29.559> at<01:04:29.680> the<01:04:29.760> end<01:04:30.000> it's<01:04:30.319> easy<01:04:30.680> to<01:04:31.359> to 01:04:31.670 --> 01:04:31.680 align:start position:0% blockchain so at the end it's easy to to 01:04:31.680 --> 01:04:35.390 align:start position:0% blockchain so at the end it's easy to to only<01:04:32.440> uh<01:04:32.640> use<01:04:32.920> the<01:04:33.119> IP<01:04:33.760> of<01:04:33.920> the<01:04:34.079> device<01:04:34.480> to<01:04:35.160> to 01:04:35.390 --> 01:04:35.400 align:start position:0% only uh use the IP of the device to to 01:04:35.400 --> 01:04:38.269 align:start position:0% only uh use the IP of the device to to get<01:04:35.680> information<01:04:36.279> at<01:04:36.440> at<01:04:36.559> the<01:04:36.680> end<01:04:37.319> it's<01:04:37.559> an<01:04:37.839> NG 01:04:38.269 --> 01:04:38.279 align:start position:0% get information at at the end it's an NG 01:04:38.279 --> 01:04:42.589 align:start position:0% get information at at the end it's an NG server<01:04:39.200> running<01:04:39.720> here<01:04:40.720> uh<01:04:41.400> like<01:04:41.520> a<01:04:42.160> reverse 01:04:42.589 --> 01:04:42.599 align:start position:0% server running here uh like a reverse 01:04:42.599 --> 01:04:46.589 align:start position:0% server running here uh like a reverse proxy<01:04:43.319> for<01:04:43.680> for<01:04:43.880> all<01:04:44.160> the<01:04:44.400> the 01:04:46.589 --> 01:04:46.599 align:start position:0% 01:04:46.599 --> 01:04:50.190 align:start position:0% clients<01:04:47.599> and<01:04:48.279> if<01:04:48.400> you<01:04:48.520> are<01:04:48.720> going<01:04:48.920> to<01:04:49.160> use<01:04:50.039> uh 01:04:50.190 --> 01:04:50.200 align:start position:0% clients and if you are going to use uh 01:04:50.200 --> 01:04:53.269 align:start position:0% clients and if you are going to use uh metam<01:04:50.559> mask<01:04:51.400> against<01:04:51.680> your<01:04:51.839> own<01:04:52.119> node<01:04:53.119> there 01:04:53.269 --> 01:04:53.279 align:start position:0% metam mask against your own node there 01:04:53.279 --> 01:04:56.990 align:start position:0% metam mask against your own node there is<01:04:53.520> a<01:04:53.839> you<01:04:54.000> have<01:04:54.119> to<01:04:54.319> install<01:04:54.920> there<01:04:55.039> is<01:04:55.240> a 01:04:56.990 --> 01:04:57.000 align:start position:0% is a you have to install there is a 01:04:57.000 --> 01:05:01.510 align:start position:0% is a you have to install there is a um<01:04:57.799> and<01:04:58.000> Jinx<01:04:58.319> is<01:04:59.240> running<01:04:59.760> with<01:05:00.039> um<01:05:00.720> SSL 01:05:01.510 --> 01:05:01.520 align:start position:0% um and Jinx is running with um SSL 01:05:01.520 --> 01:05:03.349 align:start position:0% um and Jinx is running with um SSL certification<01:05:02.319> that<01:05:02.480> you<01:05:02.599> will<01:05:03.039> have<01:05:03.200> to 01:05:03.349 --> 01:05:03.359 align:start position:0% certification that you will have to 01:05:03.359 --> 01:05:05.390 align:start position:0% certification that you will have to install<01:05:03.720> in<01:05:03.839> your<01:05:04.039> computer<01:05:04.760> in<01:05:04.920> order<01:05:05.240> to 01:05:05.390 --> 01:05:05.400 align:start position:0% install in your computer in order to 01:05:05.400 --> 01:05:08.269 align:start position:0% install in your computer in order to trust<01:05:05.720> it<01:05:06.359> or<01:05:06.880> if<01:05:07.000> you<01:05:07.240> have<01:05:07.480> your 01:05:08.269 --> 01:05:08.279 align:start position:0% trust it or if you have your 01:05:08.279 --> 01:05:13.470 align:start position:0% trust it or if you have your own<01:05:09.279> uh<01:05:09.839> domain<01:05:10.279> you<01:05:10.400> could<01:05:10.599> use 01:05:13.470 --> 01:05:13.480 align:start position:0% 01:05:13.480 --> 01:05:18.670 align:start position:0% it 01:05:18.670 --> 01:05:18.680 align:start position:0% 01:05:18.680 --> 01:05:22.109 align:start position:0% yeah<01:05:19.680> so<01:05:20.640> uh 01:05:22.109 --> 01:05:22.119 align:start position:0% yeah so uh 01:05:22.119 --> 01:05:26.549 align:start position:0% yeah so uh for<01:05:23.119> for<01:05:23.680> uh<01:05:24.480> starting<01:05:24.960> Del<01:05:25.319> to<01:05:25.960> we<01:05:26.160> just<01:05:26.319> need 01:05:26.549 --> 01:05:26.559 align:start position:0% for for uh starting Del to we just need 01:05:26.559 --> 01:05:29.670 align:start position:0% for for uh starting Del to we just need to<01:05:27.119> start<01:05:27.720> uh<01:05:27.920> this<01:05:28.240> these<01:05:28.440> are 01:05:29.670 --> 01:05:29.680 align:start position:0% to start uh this these are 01:05:29.680 --> 01:05:31.829 align:start position:0% to start uh this these are uh 01:05:31.829 --> 01:05:31.839 align:start position:0% uh 01:05:31.839 --> 01:05:35.750 align:start position:0% uh um<01:05:32.839> uh<01:05:33.119> first<01:05:33.359> you<01:05:33.559> need<01:05:33.760> to<01:05:34.200> to<01:05:34.440> run<01:05:34.760> up<01:05:35.079> gu<01:05:35.480> and 01:05:35.750 --> 01:05:35.760 align:start position:0% um uh first you need to to run up gu and 01:05:35.760 --> 01:05:40.269 align:start position:0% um uh first you need to to run up gu and later<01:05:36.160> up<01:05:36.400> no<01:05:37.000> that's<01:05:37.960> uh<01:05:38.839> all<01:05:39.039> you<01:05:39.160> have<01:05:39.319> to<01:05:39.480> do 01:05:40.269 --> 01:05:40.279 align:start position:0% later up no that's uh all you have to do 01:05:40.279 --> 01:05:44.069 align:start position:0% later up no that's uh all you have to do and<01:05:41.039> here<01:05:41.880> and<01:05:42.599> in<01:05:42.880> the<01:05:43.359> in<01:05:43.480> the<01:05:43.640> upnote 01:05:44.069 --> 01:05:44.079 align:start position:0% and here and in the in the upnote 01:05:44.079 --> 01:05:48.510 align:start position:0% and here and in the in the upnote configuration<01:05:44.680> you<01:05:44.839> need<01:05:45.039> to<01:05:46.200> um<01:05:47.279> put<01:05:48.279> where 01:05:48.510 --> 01:05:48.520 align:start position:0% configuration you need to um put where 01:05:48.520 --> 01:05:51.829 align:start position:0% configuration you need to um put where your<01:05:48.960> l<01:05:49.440> l<01:05:49.760> one<01:05:50.039> is<01:05:50.839> H<01:05:50.960> in<01:05:51.079> this<01:05:51.240> case<01:05:51.400> is<01:05:51.559> Local 01:05:51.829 --> 01:05:51.839 align:start position:0% your l l one is H in this case is Local 01:05:51.839 --> 01:05:55.309 align:start position:0% your l l one is H in this case is Local Host<01:05:52.520> you<01:05:52.920> you<01:05:53.160> we<01:05:53.359> put<01:05:53.559> Local<01:05:53.960> Host<01:05:54.760> in<01:05:55.119> in 01:05:55.309 --> 01:05:55.319 align:start position:0% Host you you we put Local Host in in 01:05:55.319 --> 01:05:57.230 align:start position:0% Host you you we put Local Host in in case<01:05:55.480> you<01:05:55.680> you<01:05:55.799> have<01:05:56.000> it<01:05:56.240> in<01:05:56.440> another<01:05:56.799> node<01:05:57.079> you 01:05:57.230 --> 01:05:57.240 align:start position:0% case you you have it in another node you 01:05:57.240 --> 01:06:34.549 align:start position:0% case you you have it in another node you put<01:05:57.480> here<01:05:57.960> uh<01:05:58.240> the<01:05:58.440> IP<01:05:59.400> and<01:06:00.039> and<01:06:00.160> you're<01:06:00.440> done 01:06:34.549 --> 01:06:34.559 align:start position:0% 01:06:34.559 --> 01:06:36.430 align:start position:0% oh 01:06:36.430 --> 01:06:36.440 align:start position:0% oh 01:06:36.440 --> 01:06:44.029 align:start position:0% oh happen<01:06:37.440> oh<01:06:38.000> okay<01:06:38.599> but<01:06:38.799> no<01:06:39.559> no<01:06:40.559> no<01:06:41.319> layer<01:06:41.640> one<01:06:41.839> is 01:06:44.029 --> 01:06:44.039 align:start position:0% happen oh okay but no no no layer one is 01:06:44.039 --> 01:06:50.589 align:start position:0% happen oh okay but no no no layer one is not 01:06:50.589 --> 01:06:50.599 align:start position:0% 01:06:50.599 --> 01:06:53.870 align:start position:0% the<01:06:51.599> uh<01:06:51.880> it's<01:06:52.319> an<01:06:52.520> example<01:06:53.039> everything<01:06:53.720> is 01:06:53.870 --> 01:06:53.880 align:start position:0% the uh it's an example everything is 01:06:53.880 --> 01:06:58.470 align:start position:0% the uh it's an example everything is under<01:06:54.279> the<01:06:54.559> ethereum<01:06:55.839> uh<01:06:56.720> ITC<01:06:57.359> ethereum<01:06:58.319> uh 01:06:58.470 --> 01:06:58.480 align:start position:0% under the ethereum uh ITC ethereum uh 01:06:58.480 --> 01:07:13.349 align:start position:0% under the ethereum uh ITC ethereum uh folder<01:06:59.480> all<01:06:59.680> the<01:06:59.839> configuration<01:07:00.400> is 01:07:13.349 --> 01:07:13.359 align:start position:0% 01:07:13.359 --> 01:07:16.510 align:start position:0% there<01:07:14.359> now<01:07:14.520> we<01:07:14.640> need<01:07:14.839> to<01:07:15.480> specify<01:07:16.119> another 01:07:16.510 --> 01:07:16.520 align:start position:0% there now we need to specify another 01:07:16.520 --> 01:07:20.789 align:start position:0% there now we need to specify another port<01:07:16.880> for<01:07:17.559> uh<01:07:18.559> for<01:07:18.799> upgate<01:07:19.319> because<01:07:19.720> G<01:07:20.079> is<01:07:20.640> uh 01:07:20.789 --> 01:07:20.799 align:start position:0% port for uh for upgate because G is uh 01:07:20.799 --> 01:07:23.750 align:start position:0% port for uh for upgate because G is uh running<01:07:21.240> on<01:07:22.000> on 01:07:23.750 --> 01:07:23.760 align:start position:0% running on on 01:07:23.760 --> 01:07:50.870 align:start position:0% running on on 30303<01:07:24.760> so<01:07:25.119> we<01:07:25.240> need 01:07:50.870 --> 01:07:50.880 align:start position:0% 01:07:50.880 --> 01:07:54.470 align:start position:0% now<01:07:51.880> um<01:07:52.599> once<01:07:52.760> you<01:07:52.960> have<01:07:53.119> a<01:07:53.400> upath<01:07:54.160> all<01:07:54.319> you 01:07:54.470 --> 01:07:54.480 align:start position:0% now um once you have a upath all you 01:07:54.480 --> 01:07:58.309 align:start position:0% now um once you have a upath all you have<01:07:54.640> to<01:07:54.799> do<01:07:55.039> is<01:07:55.799> uh<01:07:56.160> again<01:07:57.079> put<01:07:57.400> your<01:07:58.160> uh 01:07:58.309 --> 01:07:58.319 align:start position:0% have to do is uh again put your uh 01:07:58.319 --> 01:08:01.870 align:start position:0% have to do is uh again put your uh modify<01:07:58.799> your<01:07:59.000> configuration<01:07:59.559> in<01:07:59.920> up<01:08:00.200> node<01:08:00.880> and 01:08:01.870 --> 01:08:01.880 align:start position:0% modify your configuration in up node and 01:08:01.880 --> 01:08:07.470 align:start position:0% modify your configuration in up node and and<01:08:02.760> well<01:08:03.799> uh<01:08:04.799> um<01:08:05.279> we<01:08:05.440> are<01:08:06.000> using<01:08:06.359> optimism<01:08:07.240> as 01:08:07.470 --> 01:08:07.480 align:start position:0% and well uh um we are using optimism as 01:08:07.480 --> 01:08:10.589 align:start position:0% and well uh um we are using optimism as a<01:08:08.240> as<01:08:08.359> an<01:08:08.599> example<01:08:09.119> but<01:08:09.400> uh<01:08:09.520> you<01:08:09.680> can<01:08:10.279> run 01:08:10.589 --> 01:08:10.599 align:start position:0% a as an example but uh you can run 01:08:10.599 --> 01:08:14.829 align:start position:0% a as an example but uh you can run Arbitron<01:08:11.319> or<01:08:11.680> nosis<01:08:12.559> or<01:08:12.880> base<01:08:13.599> so<01:08:14.200> it's<01:08:14.440> all<01:08:14.680> in 01:08:14.829 --> 01:08:14.839 align:start position:0% Arbitron or nosis or base so it's all in 01:08:14.839 --> 01:08:17.709 align:start position:0% Arbitron or nosis or base so it's all in our<01:08:15.160> configuration<01:08:16.080> uh<01:08:16.319> page<01:08:17.080> so<01:08:17.319> it's<01:08:17.480> not 01:08:17.709 --> 01:08:17.719 align:start position:0% our configuration uh page so it's not 01:08:17.719 --> 01:08:21.030 align:start position:0% our configuration uh page so it's not the<01:08:17.839> only<01:08:18.120> option 01:08:21.030 --> 01:08:21.040 align:start position:0% 01:08:21.040 --> 01:08:23.950 align:start position:0% optimism<01:08:22.040> can<01:08:22.159> you<01:08:22.400> run<01:08:23.000> uh<01:08:23.199> layer<01:08:23.520> one<01:08:23.719> and 01:08:23.950 --> 01:08:23.960 align:start position:0% optimism can you run uh layer one and 01:08:23.960 --> 01:08:26.349 align:start position:0% optimism can you run uh layer one and Layer<01:08:24.239> Two<01:08:24.480> in<01:08:24.640> the<01:08:24.799> same 01:08:26.349 --> 01:08:26.359 align:start position:0% Layer Two in the same 01:08:26.359 --> 01:08:28.190 align:start position:0% Layer Two in the same it<01:08:26.640> it's<01:08:26.920> the<01:08:27.400> super 01:08:28.190 --> 01:08:28.200 align:start position:0% it it's the super 01:08:28.200 --> 01:08:34.269 align:start position:0% it it's the super [Music] 01:08:34.269 --> 01:08:34.279 align:start position:0% 01:08:34.279 --> 01:08:37.390 align:start position:0% node<01:08:35.279> okay<01:08:35.480> up<01:08:35.719> node<01:08:35.960> is<01:08:36.120> not<01:08:36.400> is<01:08:36.600> not<01:08:36.799> going<01:08:37.040> to 01:08:37.390 --> 01:08:37.400 align:start position:0% node okay up node is not is not going to 01:08:37.400 --> 01:08:40.269 align:start position:0% node okay up node is not is not going to to<01:08:37.600> work<01:08:38.000> because<01:08:38.600> uh<01:08:38.719> we<01:08:38.799> don't<01:08:39.080> have<01:08:39.480> a<01:08:40.080> a 01:08:40.269 --> 01:08:40.279 align:start position:0% to work because uh we don't have a a 01:08:40.279 --> 01:08:42.030 align:start position:0% to work because uh we don't have a a layer<01:08:40.640> one<01:08:40.880> sync 01:08:42.030 --> 01:08:42.040 align:start position:0% layer one sync 01:08:42.040 --> 01:08:45.269 align:start position:0% layer one sync okay<01:08:43.080> see<01:08:44.080> it's<01:08:44.279> going 01:08:45.269 --> 01:08:45.279 align:start position:0% okay see it's going 01:08:45.279 --> 01:08:47.630 align:start position:0% okay see it's going to<01:08:46.279> to 01:08:47.630 --> 01:08:47.640 align:start position:0% to to 01:08:47.640 --> 01:08:51.349 align:start position:0% to to break<01:08:48.640> but<01:08:49.239> uh<01:08:50.000> yeah<01:08:50.279> this<01:08:50.400> is<01:08:50.640> pretty<01:08:50.920> much 01:08:51.349 --> 01:08:51.359 align:start position:0% break but uh yeah this is pretty much 01:08:51.359 --> 01:08:54.030 align:start position:0% break but uh yeah this is pretty much every<01:08:51.920> all<01:08:52.080> you<01:08:52.319> can<01:08:52.560> you<01:08:52.719> have<01:08:52.880> to<01:08:53.040> do<01:08:53.319> to<01:08:53.880> to 01:08:54.030 --> 01:08:54.040 align:start position:0% every all you can you have to do to to 01:08:54.040 --> 01:08:56.590 align:start position:0% every all you can you have to do to to run<01:08:54.319> two<01:08:54.560> notes<01:08:55.560> two<01:08:55.799> layer 01:08:56.590 --> 01:08:56.600 align:start position:0% run two notes two layer 01:08:56.600 --> 01:09:01.189 align:start position:0% run two notes two layer nodes<01:08:57.600> ER<01:08:57.920> in<01:08:58.120> the<01:08:58.279> same<01:08:58.480> device 01:09:01.189 --> 01:09:01.199 align:start position:0% 01:09:01.199 --> 01:09:05.030 align:start position:0% T<01:09:02.199> but<01:09:02.759> uh<01:09:03.279> yeah<01:09:04.000> just<01:09:04.159> to<01:09:04.319> come<01:09:04.600> back<01:09:04.719> to<01:09:04.880> that 01:09:05.030 --> 01:09:05.040 align:start position:0% T but uh yeah just to come back to that 01:09:05.040 --> 01:09:07.630 align:start position:0% T but uh yeah just to come back to that earli<01:09:05.359> question<01:09:05.640> about<01:09:05.960> the<01:09:06.440> storage<01:09:06.920> size 01:09:07.630 --> 01:09:07.640 align:start position:0% earli question about the storage size 01:09:07.640 --> 01:09:10.950 align:start position:0% earli question about the storage size now<01:09:07.880> if<01:09:08.000> you<01:09:08.359> run<01:09:08.600> two<01:09:09.560> oh<01:09:09.839> yeah<01:09:10.040> yeah<01:09:10.239> no<01:09:10.719> four 01:09:10.950 --> 01:09:10.960 align:start position:0% now if you run two oh yeah yeah no four 01:09:10.960 --> 01:09:13.950 align:start position:0% now if you run two oh yeah yeah no four four<01:09:11.159> tabes<01:09:11.759> here<01:09:12.520> yes<01:09:13.279> so<01:09:13.400> how<01:09:13.560> big<01:09:13.719> is 01:09:13.950 --> 01:09:13.960 align:start position:0% four tabes here yes so how big is 01:09:13.960 --> 01:09:15.870 align:start position:0% four tabes here yes so how big is optimism<01:09:14.480> for<01:09:14.679> example<01:09:15.120> right<01:09:15.239> now<01:09:15.480> like<01:09:15.759> how 01:09:15.870 --> 01:09:15.880 align:start position:0% optimism for example right now like how 01:09:15.880 --> 01:09:17.470 align:start position:0% optimism for example right now like how much<01:09:16.080> do<01:09:16.199> I<01:09:16.359> need<01:09:16.560> for<01:09:16.719> that<01:09:16.960> because<01:09:17.120> I<01:09:17.239> always 01:09:17.470 --> 01:09:17.480 align:start position:0% much do I need for that because I always 01:09:17.480 --> 01:09:19.870 align:start position:0% much do I need for that because I always think<01:09:17.839> they're<01:09:18.080> so<01:09:18.359> fast<01:09:18.640> add<01:09:18.960> so<01:09:19.080> much<01:09:19.359> space 01:09:19.870 --> 01:09:19.880 align:start position:0% think they're so fast add so much space 01:09:19.880 --> 01:09:23.149 align:start position:0% think they're so fast add so much space yeah<01:09:20.319> I<01:09:20.520> I<01:09:20.759> would<01:09:21.000> say<01:09:21.440> about<01:09:21.679> two<01:09:22.159> terabytes 01:09:23.149 --> 01:09:23.159 align:start position:0% yeah I I would say about two terabytes 01:09:23.159 --> 01:09:26.510 align:start position:0% yeah I I would say about two terabytes op<01:09:23.400> not<01:09:23.799> just<01:09:24.080> optimism<01:09:24.600> alone<01:09:25.080> y<01:09:25.600> yeah<01:09:26.239> and 01:09:26.510 --> 01:09:26.520 align:start position:0% op not just optimism alone y yeah and 01:09:26.520 --> 01:09:29.749 align:start position:0% op not just optimism alone y yeah and and<01:09:27.159> uh<01:09:27.480> several<01:09:27.839> months<01:09:28.199> ago<01:09:28.960> uh<01:09:29.239> you<01:09:29.400> needed 01:09:29.749 --> 01:09:29.759 align:start position:0% and uh several months ago uh you needed 01:09:29.759 --> 01:09:34.149 align:start position:0% and uh several months ago uh you needed to<01:09:30.759> uh<01:09:30.960> download<01:09:31.480> the<01:09:31.679> snapshot<01:09:32.400> it<01:09:32.679> was<01:09:33.679> very 01:09:34.149 --> 01:09:34.159 align:start position:0% to uh download the snapshot it was very 01:09:34.159 --> 01:09:38.030 align:start position:0% to uh download the snapshot it was very difficult<01:09:34.359> to<01:09:35.120> to<01:09:35.480> De<01:09:35.719> compress<01:09:36.480> because<01:09:37.279> H<01:09:37.839> it 01:09:38.030 --> 01:09:38.040 align:start position:0% difficult to to De compress because H it 01:09:38.040 --> 01:09:41.510 align:start position:0% difficult to to De compress because H it was<01:09:38.359> already<01:09:39.279> uh<01:09:39.640> the<01:09:39.799> snapshot<01:09:40.440> it<01:09:40.600> was<01:09:41.120> uh 01:09:41.510 --> 01:09:41.520 align:start position:0% was already uh the snapshot it was uh 01:09:41.520 --> 01:09:43.110 align:start position:0% was already uh the snapshot it was uh huge<01:09:41.920> and<01:09:42.120> you 01:09:43.110 --> 01:09:43.120 align:start position:0% huge and you 01:09:43.120 --> 01:09:46.990 align:start position:0% huge and you need<01:09:44.120> like<01:09:44.719> six<01:09:45.080> or<01:09:45.319> seven<01:09:45.640> terabytes<01:09:46.239> for 01:09:46.990 --> 01:09:47.000 align:start position:0% need like six or seven terabytes for 01:09:47.000 --> 01:09:50.149 align:start position:0% need like six or seven terabytes for storing<01:09:47.600> the<01:09:48.000> the<01:09:48.359> compressed<01:09:48.799> file<01:09:49.080> in<01:09:49.600> and 01:09:50.149 --> 01:09:50.159 align:start position:0% storing the the compressed file in and 01:09:50.159 --> 01:09:52.789 align:start position:0% storing the the compressed file in and and<01:09:50.359> the<01:09:50.560> compress<01:09:50.960> it<01:09:51.520> but<01:09:51.719> now<01:09:52.239> it<01:09:52.400> supports 01:09:52.789 --> 01:09:52.799 align:start position:0% and the compress it but now it supports 01:09:52.799 --> 01:09:55.830 align:start position:0% and the compress it but now it supports a<01:09:52.920> snap<01:09:53.239> syn<01:09:53.719> and<01:09:54.040> and<01:09:54.400> and<01:09:54.760> it<01:09:54.960> works<01:09:55.520> was 01:09:55.830 --> 01:09:55.840 align:start position:0% a snap syn and and and it works was 01:09:55.840 --> 01:09:58.709 align:start position:0% a snap syn and and and it works was great<01:09:56.440> yeah<01:09:56.640> it's<01:09:56.880> very<01:09:57.080> easy<01:09:57.360> to<01:09:57.640> to<01:09:57.800> run<01:09:58.520> an 01:09:58.709 --> 01:09:58.719 align:start position:0% great yeah it's very easy to to run an 01:09:58.719 --> 01:09:59.790 align:start position:0% great yeah it's very easy to to run an optimism 01:09:59.790 --> 01:09:59.800 align:start position:0% optimism 01:09:59.800 --> 01:10:03.990 align:start position:0% optimism node<01:10:00.800> yeah<01:10:01.159> we<01:10:01.320> have<01:10:01.640> really<01:10:02.400> at<01:10:02.600> home<01:10:03.600> running 01:10:03.990 --> 01:10:04.000 align:start position:0% node yeah we have really at home running 01:10:04.000 --> 01:10:06.790 align:start position:0% node yeah we have really at home running a<01:10:04.400> super<01:10:04.719> node<01:10:05.120> because<01:10:05.560> if<01:10:05.719> everything<01:10:06.120> fails 01:10:06.790 --> 01:10:06.800 align:start position:0% a super node because if everything fails 01:10:06.800 --> 01:10:09.310 align:start position:0% a super node because if everything fails we<01:10:06.960> have<01:10:07.120> our<01:10:08.040> no<01:10:08.280> is<01:10:08.400> not<01:10:08.560> running<01:10:08.920> because<01:10:09.120> it 01:10:09.310 --> 01:10:09.320 align:start position:0% we have our no is not running because it 01:10:09.320 --> 01:10:13.350 align:start position:0% we have our no is not running because it fails<01:10:09.679> but<01:10:10.080> uh<01:10:10.400> but<01:10:10.800> uh<01:10:11.239> yeah<01:10:11.800> it's<01:10:12.800> here<01:10:12.920> it's 01:10:13.350 --> 01:10:13.360 align:start position:0% fails but uh but uh yeah it's here it's 01:10:13.360 --> 01:10:15.709 align:start position:0% fails but uh but uh yeah it's here it's home<01:10:13.640> it's<01:10:13.760> ours<01:10:14.280> uh<01:10:14.760> okay<01:10:15.239> this<01:10:15.480> this<01:10:15.600> is 01:10:15.709 --> 01:10:15.719 align:start position:0% home it's ours uh okay this this is 01:10:15.719 --> 01:10:19.470 align:start position:0% home it's ours uh okay this this is running<01:10:16.000> at<01:10:16.120> my<01:10:16.360> home<01:10:16.840> okay<01:10:17.840> uh<01:10:18.159> this<01:10:18.320> one<01:10:19.040> and 01:10:19.470 --> 01:10:19.480 align:start position:0% running at my home okay uh this one and 01:10:19.480 --> 01:10:23.149 align:start position:0% running at my home okay uh this one and you<01:10:19.679> you<01:10:19.760> can<01:10:19.920> see<01:10:20.600> uh<01:10:21.440> um<01:10:22.120> the<01:10:22.280> average<01:10:22.679> load 01:10:23.149 --> 01:10:23.159 align:start position:0% you you can see uh um the average load 01:10:23.159 --> 01:10:26.189 align:start position:0% you you can see uh um the average load and<01:10:23.520> it's<01:10:23.840> running<01:10:24.600> flawlessly 01:10:26.189 --> 01:10:26.199 align:start position:0% and it's running flawlessly 01:10:26.199 --> 01:10:29.709 align:start position:0% and it's running flawlessly uh<01:10:26.920> it's<01:10:27.159> the<01:10:27.360> same<01:10:28.080> I<01:10:28.159> don't<01:10:28.440> know<01:10:28.760> is<01:10:29.120> if<01:10:29.560> this 01:10:29.709 --> 01:10:29.719 align:start position:0% uh it's the same I don't know is if this 01:10:29.719 --> 01:10:32.390 align:start position:0% uh it's the same I don't know is if this is<01:10:29.880> the<01:10:30.040> same<01:10:30.400> device<01:10:31.400> no<01:10:31.640> it's 01:10:32.390 --> 01:10:32.400 align:start position:0% is the same device no it's 01:10:32.400 --> 01:10:38.110 align:start position:0% is the same device no it's another<01:10:33.400> orange<01:10:33.840> p<01:10:34.840> p<01:10:35.480> FL<01:10:36.480> and<01:10:37.080> um<01:10:37.679> yeah<01:10:37.880> it's 01:10:38.110 --> 01:10:38.120 align:start position:0% another orange p p FL and um yeah it's 01:10:38.120 --> 01:10:40.310 align:start position:0% another orange p p FL and um yeah it's pretty<01:10:38.320> much<01:10:38.480> the<01:10:38.600> same<01:10:38.840> device<01:10:39.280> but<01:10:39.719> uh<01:10:40.199> you 01:10:40.310 --> 01:10:40.320 align:start position:0% pretty much the same device but uh you 01:10:40.320 --> 01:10:43.910 align:start position:0% pretty much the same device but uh you can<01:10:40.480> see<01:10:40.760> that<01:10:41.280> it's<01:10:41.400> running<01:10:41.920> great<01:10:42.920> uh<01:10:43.719> in 01:10:43.910 --> 01:10:43.920 align:start position:0% can see that it's running great uh in 01:10:43.920 --> 01:10:47.669 align:start position:0% can see that it's running great uh in sync 01:10:47.669 --> 01:10:47.679 align:start position:0% 01:10:47.679 --> 01:10:55.870 align:start position:0% and<01:10:48.679> what<01:10:49.000> what<01:10:50.000> one 01:10:55.870 --> 01:10:55.880 align:start position:0% 01:10:55.880 --> 01:10:58.430 align:start position:0% yes<01:10:56.600> lo 01:10:58.430 --> 01:10:58.440 align:start position:0% yes lo 01:10:58.440 --> 01:11:01.149 align:start position:0% yes lo lo<01:10:59.440> uh 01:11:01.149 --> 01:11:01.159 align:start position:0% lo uh 01:11:01.159 --> 01:11:07.910 align:start position:0% lo uh uh<01:11:02.159> wait<01:11:02.320> a<01:11:02.480> minute 01:11:07.910 --> 01:11:07.920 align:start position:0% 01:11:07.920 --> 01:11:15.030 align:start position:0% please 01:11:15.030 --> 01:11:15.040 align:start position:0% 01:11:15.040 --> 01:11:19.910 align:start position:0% what<01:11:16.040> it's<01:11:16.360> easy<01:11:16.640> to<01:11:16.760> see<01:11:17.320> nice<01:11:18.280> this<01:11:18.400> is<01:11:18.920> nice 01:11:19.910 --> 01:11:19.920 align:start position:0% what it's easy to see nice this is nice 01:11:19.920 --> 01:11:23.750 align:start position:0% what it's easy to see nice this is nice okay<01:11:20.400> as<01:11:20.560> you<01:11:20.679> can<01:11:20.840> see<01:11:21.120> here<01:11:21.520> the<01:11:21.760> all<01:11:22.440> the<01:11:23.440> a<01:11:23.640> a 01:11:23.750 --> 01:11:23.760 align:start position:0% okay as you can see here the all the a a 01:11:23.760 --> 01:11:27.709 align:start position:0% okay as you can see here the all the a a very<01:11:23.920> easy<01:11:24.199> way<01:11:24.360> to<01:11:24.480> see<01:11:24.840> how<01:11:25.040> is<01:11:25.400> your<01:11:26.520> uh<01:11:27.520> your 01:11:27.709 --> 01:11:27.719 align:start position:0% very easy way to see how is your uh your 01:11:27.719 --> 01:11:31.110 align:start position:0% very easy way to see how is your uh your node<01:11:28.400> going<01:11:28.920> you<01:11:29.120> have<01:11:29.600> the<01:11:30.600> all<01:11:30.840> the 01:11:31.110 --> 01:11:31.120 align:start position:0% node going you have the all the 01:11:31.120 --> 01:11:33.270 align:start position:0% node going you have the all the processes<01:11:31.880> all<01:11:32.040> the<01:11:32.199> processes<01:11:32.679> running<01:11:33.040> is 01:11:33.270 --> 01:11:33.280 align:start position:0% processes all the processes running is 01:11:33.280 --> 01:11:37.110 align:start position:0% processes all the processes running is up<01:11:33.880> G<01:11:34.159> nimus<01:11:35.120> um<01:11:35.520> up<01:11:35.800> node<01:11:36.400> all<01:11:36.640> in<01:11:36.760> the<01:11:36.920> same 01:11:37.110 --> 01:11:37.120 align:start position:0% up G nimus um up node all in the same 01:11:37.120 --> 01:11:39.709 align:start position:0% up G nimus um up node all in the same node<01:11:37.600> it's<01:11:37.800> an<01:11:38.040> orang<01:11:38.400> orange<01:11:38.719> Pine<01:11:39.040> is<01:11:39.400> most 01:11:39.709 --> 01:11:39.719 align:start position:0% node it's an orang orange Pine is most 01:11:39.719 --> 01:11:41.830 align:start position:0% node it's an orang orange Pine is most more<01:11:39.880> or<01:11:40.040> less<01:11:40.199> the<01:11:40.360> same<01:11:40.760> device<01:11:41.480> the<01:11:41.639> same 01:11:41.830 --> 01:11:41.840 align:start position:0% more or less the same device the same 01:11:41.840 --> 01:11:45.910 align:start position:0% more or less the same device the same powerful<01:11:42.239> the<01:11:42.360> same<01:11:42.920> memory<01:11:43.920> um<01:11:44.440> you<01:11:44.600> see<01:11:44.920> it's 01:11:45.910 --> 01:11:45.920 align:start position:0% powerful the same memory um you see it's 01:11:45.920 --> 01:11:49.590 align:start position:0% powerful the same memory um you see it's uh<01:11:46.239> it's<01:11:46.440> not<01:11:46.679> cing<01:11:47.040> the<01:11:47.320> the<01:11:47.440> CPU<01:11:47.800> is<01:11:48.000> 70<01:11:48.760> 70% 01:11:49.590 --> 01:11:49.600 align:start position:0% uh it's not cing the the CPU is 70 70% 01:11:49.600 --> 01:11:52.430 align:start position:0% uh it's not cing the the CPU is 70 70% of<01:11:49.920> CPU<01:11:50.400> using<01:11:51.080> memory<01:11:51.520> are 01:11:52.430 --> 01:11:52.440 align:start position:0% of CPU using memory are 01:11:52.440 --> 01:11:56.550 align:start position:0% of CPU using memory are 60%<01:11:53.440> uh<01:11:53.760> swapping<01:11:54.280> is<01:11:54.560> 50<01:11:54.920> 50<01:11:55.239> %<01:11:55.639> right<01:11:55.880> here<01:11:56.040> is 01:11:56.550 --> 01:11:56.560 align:start position:0% 60% uh swapping is 50 50 % right here is 01:11:56.560 --> 01:11:58.830 align:start position:0% 60% uh swapping is 50 50 % right here is is<01:11:57.560> it's<01:11:57.719> doing 01:11:58.830 --> 01:11:58.840 align:start position:0% is it's doing 01:11:58.840 --> 01:12:03.030 align:start position:0% is it's doing well<01:11:59.840> not<01:12:00.040> is<01:12:00.199> not<01:12:00.400> even<01:12:01.360> very<01:12:01.639> very<01:12:02.000> high<01:12:02.440> low 01:12:03.030 --> 01:12:03.040 align:start position:0% well not is not even very very high low 01:12:03.040 --> 01:12:05.950 align:start position:0% well not is not even very very high low here<01:12:03.520> so<01:12:04.320> you<01:12:04.440> can<01:12:04.600> see<01:12:04.880> this<01:12:05.040> is<01:12:05.480> more<01:12:05.719> than 01:12:05.950 --> 01:12:05.960 align:start position:0% here so you can see this is more than 01:12:05.960 --> 01:12:09.350 align:start position:0% here so you can see this is more than enough<01:12:06.719> small<01:12:07.000> device<01:12:07.400> like<01:12:07.560> this<01:12:07.679> to<01:12:07.880> run 01:12:09.350 --> 01:12:09.360 align:start position:0% enough small device like this to run 01:12:09.360 --> 01:12:15.310 align:start position:0% enough small device like this to run super 01:12:15.310 --> 01:12:15.320 align:start position:0% 01:12:15.320 --> 01:12:17.030 align:start position:0% yes 01:12:17.030 --> 01:12:17.040 align:start position:0% yes 01:12:17.040 --> 01:12:20.189 align:start position:0% yes sorry<01:12:18.040> why<01:12:18.159> we<01:12:18.320> use<01:12:18.480> swap<01:12:19.400> just<01:12:19.800> some 01:12:20.189 --> 01:12:20.199 align:start position:0% sorry why we use swap just some 01:12:20.199 --> 01:12:22.790 align:start position:0% sorry why we use swap just some sometimes<01:12:20.480> most<01:12:20.639> of<01:12:20.800> the<01:12:20.960> times<01:12:21.239> during<01:12:21.800> sync 01:12:22.790 --> 01:12:22.800 align:start position:0% sometimes most of the times during sync 01:12:22.800 --> 01:12:24.709 align:start position:0% sometimes most of the times during sync uh<01:12:22.920> you<01:12:23.040> will<01:12:23.199> need<01:12:23.440> more<01:12:23.880> memory<01:12:24.239> that<01:12:24.480> you 01:12:24.709 --> 01:12:24.719 align:start position:0% uh you will need more memory that you 01:12:24.719 --> 01:12:26.030 align:start position:0% uh you will need more memory that you have 01:12:26.030 --> 01:12:26.040 align:start position:0% have 01:12:26.040 --> 01:12:28.750 align:start position:0% have sorry<01:12:26.520> this<01:12:26.679> is<01:12:27.520> more<01:12:27.679> than<01:12:27.800> the<01:12:27.920> 72<01:12:28.440> with<01:12:28.600> a 01:12:28.750 --> 01:12:28.760 align:start position:0% sorry this is more than the 72 with a 01:12:28.760 --> 01:12:31.950 align:start position:0% sorry this is more than the 72 with a super<01:12:29.040> note<01:12:29.360> yes<01:12:30.320> with<01:12:30.560> all<01:12:30.880> the<01:12:31.280> this<01:12:31.679> one 01:12:31.950 --> 01:12:31.960 align:start position:0% super note yes with all the this one 01:12:31.960 --> 01:12:35.149 align:start position:0% super note yes with all the this one four<01:12:32.320> five<01:12:32.560> six<01:12:32.800> seven<01:12:33.520> uh<01:12:33.679> service<01:12:34.159> running 01:12:35.149 --> 01:12:35.159 align:start position:0% four five six seven uh service running 01:12:35.159 --> 01:12:37.629 align:start position:0% four five six seven uh service running sometimes<01:12:35.600> in<01:12:35.760> during<01:12:36.040> syn<01:12:36.440> it<01:12:36.960> will<01:12:37.239> requires 01:12:37.629 --> 01:12:37.639 align:start position:0% sometimes in during syn it will requires 01:12:37.639 --> 01:12:41.310 align:start position:0% sometimes in during syn it will requires more<01:12:37.800> than<01:12:37.960> 72<01:12:38.440> and<01:12:38.639> we<01:12:39.159> you<01:12:39.280> will<01:12:39.520> have<01:12:39.800> an<01:12:40.440> uh 01:12:41.310 --> 01:12:41.320 align:start position:0% more than 72 and we you will have an uh 01:12:41.320 --> 01:12:45.350 align:start position:0% more than 72 and we you will have an uh on<01:12:42.000> killer<01:12:43.000> out<01:12:43.199> of<01:12:43.360> memory<01:12:43.639> killer<01:12:44.159> with<01:12:45.000> the 01:12:45.350 --> 01:12:45.360 align:start position:0% on killer out of memory killer with the 01:12:45.360 --> 01:12:47.950 align:start position:0% on killer out of memory killer with the heaviest<01:12:46.280> uh<01:12:46.760> proc<01:12:47.280> the<01:12:47.360> heav<01:12:47.679> process 01:12:47.950 --> 01:12:47.960 align:start position:0% heaviest uh proc the heav process 01:12:47.960 --> 01:12:50.149 align:start position:0% heaviest uh proc the heav process running<01:12:48.360> it's<01:12:48.480> a<01:12:48.600> safe<01:12:48.840> measure<01:12:49.239> I<01:12:49.400> think<01:12:49.880> that 01:12:50.149 --> 01:12:50.159 align:start position:0% running it's a safe measure I think that 01:12:50.159 --> 01:12:53.390 align:start position:0% running it's a safe measure I think that it's<01:12:50.600> is<01:12:50.760> not<01:12:51.000> using<01:12:51.360> it<01:12:51.960> Prett<01:12:52.800> pretty<01:12:53.000> much 01:12:53.390 --> 01:12:53.400 align:start position:0% it's is not using it Prett pretty much 01:12:53.400 --> 01:12:54.750 align:start position:0% it's is not using it Prett pretty much it's<01:12:53.520> not<01:12:53.639> going<01:12:53.800> be<01:12:53.880> using<01:12:54.199> swap<01:12:54.560> but<01:12:54.679> the 01:12:54.750 --> 01:12:54.760 align:start position:0% it's not going be using swap but the 01:12:54.760 --> 01:12:57.229 align:start position:0% it's not going be using swap but the swap<01:12:55.239> is<01:12:55.320> in<01:12:55.440> the<01:12:55.600> MBM<01:12:56.080> dis<01:12:56.520> so<01:12:56.719> it's<01:12:57.040> quite 01:12:57.229 --> 01:12:57.239 align:start position:0% swap is in the MBM dis so it's quite 01:12:57.239 --> 01:13:01.270 align:start position:0% swap is in the MBM dis so it's quite fast<01:12:57.480> to<01:12:57.639> access<01:12:58.320> this<01:12:58.800> and<01:12:59.760> I<01:12:59.880> was<01:13:00.120> at<01:13:00.600> uh<01:13:01.040> this 01:13:01.270 --> 01:13:01.280 align:start position:0% fast to access this and I was at uh this 01:13:01.280 --> 01:13:04.430 align:start position:0% fast to access this and I was at uh this a<01:13:01.600> very<01:13:01.760> funny<01:13:02.280> web<01:13:02.440> page<01:13:02.719> as<01:13:02.920> Linux<01:13:03.639> maram<01:13:04.239> so 01:13:04.430 --> 01:13:04.440 align:start position:0% a very funny web page as Linux maram so 01:13:04.440 --> 01:13:06.470 align:start position:0% a very funny web page as Linux maram so at<01:13:04.560> the<01:13:04.639> end<01:13:05.000> you<01:13:05.159> have<01:13:05.360> swap<01:13:05.960> because<01:13:06.199> is<01:13:06.360> the 01:13:06.470 --> 01:13:06.480 align:start position:0% at the end you have swap because is the 01:13:06.480 --> 01:13:08.629 align:start position:0% at the end you have swap because is the system<01:13:06.840> is<01:13:07.040> is<01:13:07.199> going<01:13:07.360> to<01:13:07.520> need<01:13:07.880> right<01:13:08.040> now 01:13:08.629 --> 01:13:08.639 align:start position:0% system is is going to need right now 01:13:08.639 --> 01:13:15.629 align:start position:0% system is is going to need right now it's<01:13:09.880> 50%<01:13:10.880> uh<01:13:11.480> us<01:13:11.719> it<01:13:12.440> not<01:13:12.920> probably<01:13:13.560> let<01:13:13.719> me 01:13:15.629 --> 01:13:15.639 align:start position:0% it's 50% uh us it not probably let me 01:13:15.639 --> 01:13:18.510 align:start position:0% it's 50% uh us it not probably let me see<01:13:16.639> no<01:13:16.960> no<01:13:17.280> there's<01:13:17.480> no<01:13:17.760> process<01:13:18.080> using<01:13:18.360> in 01:13:18.510 --> 01:13:18.520 align:start position:0% see no no there's no process using in 01:13:18.520 --> 01:13:22.110 align:start position:0% see no no there's no process using in swap<01:13:18.880> right<01:13:19.000> now<01:13:19.320> but<01:13:19.880> uh<01:13:20.320> during<01:13:20.679> sync<01:13:21.080> we<01:13:21.280> saw 01:13:22.110 --> 01:13:22.120 align:start position:0% swap right now but uh during sync we saw 01:13:22.120 --> 01:13:24.470 align:start position:0% swap right now but uh during sync we saw several<01:13:22.480> on<01:13:22.719> Killers<01:13:23.400> we<01:13:23.560> have<01:13:23.800> all<01:13:24.280> the 01:13:24.470 --> 01:13:24.480 align:start position:0% several on Killers we have all the 01:13:24.480 --> 01:13:25.709 align:start position:0% several on Killers we have all the devices<01:13:24.880> so 01:13:25.709 --> 01:13:25.719 align:start position:0% devices so 01:13:25.719 --> 01:13:28.750 align:start position:0% devices so we<01:13:26.000> will<01:13:26.199> need<01:13:26.440> swap<01:13:26.960> at<01:13:27.080> the<01:13:27.199> end<01:13:28.199> um<01:13:28.480> if<01:13:28.639> you 01:13:28.750 --> 01:13:28.760 align:start position:0% we will need swap at the end um if you 01:13:28.760 --> 01:13:31.510 align:start position:0% we will need swap at the end um if you using<01:13:29.120> the<01:13:29.320> 16<01:13:30.000> gigs<01:13:30.280> of<01:13:30.480> RAM<01:13:30.719> version<01:13:31.280> will 01:13:31.510 --> 01:13:31.520 align:start position:0% using the 16 gigs of RAM version will 01:13:31.520 --> 01:13:32.750 align:start position:0% using the 16 gigs of RAM version will use 01:13:32.750 --> 01:13:32.760 align:start position:0% use 01:13:32.760 --> 01:13:35.189 align:start position:0% use round<01:13:33.760> also 01:13:35.189 --> 01:13:35.199 align:start position:0% round also 01:13:35.199 --> 01:13:39.229 align:start position:0% round also but<01:13:36.199> uh<01:13:36.840> when<01:13:37.280> everything<01:13:37.639> is<01:13:37.880> syn<01:13:38.280> and<01:13:38.719> Runing 01:13:39.229 --> 01:13:39.239 align:start position:0% but uh when everything is syn and Runing 01:13:39.239 --> 01:13:42.550 align:start position:0% but uh when everything is syn and Runing is<01:13:39.440> not<01:13:40.000> so<01:13:40.320> heavily<01:13:40.639> us<01:13:40.840> it<01:13:41.199> the<01:13:41.520> the<01:13:42.159> the 01:13:42.550 --> 01:13:42.560 align:start position:0% is not so heavily us it the the the 01:13:42.560 --> 01:13:44.910 align:start position:0% is not so heavily us it the the the service<01:13:43.360> of<01:13:43.520> course<01:13:43.840> I<01:13:44.000> I<01:13:44.199> don't<01:13:44.440> remember<01:13:44.800> you 01:13:44.910 --> 01:13:44.920 align:start position:0% service of course I I don't remember you 01:13:44.920 --> 01:13:46.709 align:start position:0% service of course I I don't remember you will<01:13:45.080> have<01:13:45.320> always<01:13:45.760> a<01:13:45.920> promethus<01:13:46.400> server 01:13:46.709 --> 01:13:46.719 align:start position:0% will have always a promethus server 01:13:46.719 --> 01:13:50.390 align:start position:0% will have always a promethus server running<01:13:47.120> in<01:13:47.560> behind<01:13:48.560> storing<01:13:49.280> studing<01:13:50.280> the 01:13:50.390 --> 01:13:50.400 align:start position:0% running in behind storing studing the 01:13:50.400 --> 01:13:53.470 align:start position:0% running in behind storing studing the statistics<01:13:50.880> of<01:13:51.000> your<01:13:51.159> note<01:13:52.000> so<01:13:52.520> it's<01:13:53.159> always 01:13:53.470 --> 01:13:53.480 align:start position:0% statistics of your note so it's always 01:13:53.480 --> 01:13:56.189 align:start position:0% statistics of your note so it's always running<01:13:53.920> per<01:13:54.400> server<01:13:55.120> and<01:13:55.400> grafana<01:13:55.840> server 01:13:56.189 --> 01:13:56.199 align:start position:0% running per server and grafana server 01:13:56.199 --> 01:13:58.990 align:start position:0% running per server and grafana server over<01:13:56.440> the<01:13:56.600> promethus<01:13:57.239> so<01:13:57.520> at<01:13:57.639> the<01:13:57.760> end<01:13:58.000> is 01:13:58.990 --> 01:13:59.000 align:start position:0% over the promethus so at the end is 01:13:59.000 --> 01:14:02.430 align:start position:0% over the promethus so at the end is another<01:14:00.000> quite<01:14:00.320> heavy<01:14:01.159> uh<01:14:01.880> uh<01:14:02.080> process 01:14:02.430 --> 01:14:02.440 align:start position:0% another quite heavy uh uh process 01:14:02.440 --> 01:14:04.510 align:start position:0% another quite heavy uh uh process running<01:14:02.760> so<01:14:02.920> at<01:14:03.040> the<01:14:03.159> end<01:14:03.280> you<01:14:03.360> will<01:14:03.560> need<01:14:04.360> a 01:14:04.510 --> 01:14:04.520 align:start position:0% running so at the end you will need a 01:14:04.520 --> 01:14:07.750 align:start position:0% running so at the end you will need a bit<01:14:04.679> of<01:14:05.080> swap<01:14:06.080> but<01:14:06.280> it's<01:14:06.520> not<01:14:06.719> a<01:14:06.960> big<01:14:07.159> deal 01:14:07.750 --> 01:14:07.760 align:start position:0% bit of swap but it's not a big deal 01:14:07.760 --> 01:14:10.790 align:start position:0% bit of swap but it's not a big deal because<01:14:07.960> the<01:14:08.080> swap<01:14:08.400> is<01:14:08.480> in<01:14:08.719> the<01:14:09.440> the<01:14:09.960> MBM<01:14:10.400> disc 01:14:10.790 --> 01:14:10.800 align:start position:0% because the swap is in the the MBM disc 01:14:10.800 --> 01:14:14.030 align:start position:0% because the swap is in the the MBM disc the<01:14:11.080> S<01:14:11.360> dis<01:14:11.880> is<01:14:12.239> quite 01:14:14.030 --> 01:14:14.040 align:start position:0% the S dis is quite 01:14:14.040 --> 01:14:16.870 align:start position:0% the S dis is quite fast<01:14:15.040> I'm<01:14:15.280> lot<01:14:15.520> faster<01:14:15.920> than<01:14:16.080> the<01:14:16.280> SD<01:14:16.560> card 01:14:16.870 --> 01:14:16.880 align:start position:0% fast I'm lot faster than the SD card 01:14:16.880 --> 01:14:19.110 align:start position:0% fast I'm lot faster than the SD card that<01:14:17.719> the<01:14:17.920> main<01:14:18.080> idea<01:14:18.320> of<01:14:18.480> this<01:14:18.639> is<01:14:18.800> all<01:14:18.960> the 01:14:19.110 --> 01:14:19.120 align:start position:0% that the main idea of this is all the 01:14:19.120 --> 01:14:22.070 align:start position:0% that the main idea of this is all the Twix<01:14:19.760> for<01:14:20.000> not<01:14:20.199> using<01:14:20.600> the<01:14:20.719> SD 01:14:22.070 --> 01:14:22.080 align:start position:0% Twix for not using the SD 01:14:22.080 --> 01:14:26.030 align:start position:0% Twix for not using the SD car<01:14:23.080> okay<01:14:23.560> I<01:14:23.719> think<01:14:24.719> that's<01:14:24.880> it<01:14:25.320> yeah<01:14:25.800> that's 01:14:26.030 --> 01:14:26.040 align:start position:0% car okay I think that's it yeah that's 01:14:26.040 --> 01:14:28.629 align:start position:0% car okay I think that's it yeah that's it<01:14:26.840> that's<01:14:27.000> the<01:14:27.159> end<01:14:27.440> is<01:14:27.760> the<01:14:28.000> the<01:14:28.199> a<01:14:28.320> way<01:14:28.520> to 01:14:28.629 --> 01:14:28.639 align:start position:0% it that's the end is the the a way to 01:14:28.639 --> 01:14:30.709 align:start position:0% it that's the end is the the a way to create<01:14:28.920> your<01:14:29.199> not<01:14:29.639> home<01:14:29.880> I<01:14:30.000> don't<01:14:30.120> know<01:14:30.320> if 01:14:30.709 --> 01:14:30.719 align:start position:0% create your not home I don't know if 01:14:30.719 --> 01:14:33.669 align:start position:0% create your not home I don't know if there<01:14:30.800> is<01:14:31.000> any<01:14:31.239> other<01:14:31.520> question<01:14:32.080> over<01:14:32.679> here 01:14:33.669 --> 01:14:33.679 align:start position:0% there is any other question over here 01:14:33.679 --> 01:14:37.310 align:start position:0% there is any other question over here yep<01:14:34.600> how<01:14:35.600> how<01:14:35.760> are<01:14:35.840> you<01:14:36.040> running<01:14:36.360> this<01:14:37.120> how 01:14:37.310 --> 01:14:37.320 align:start position:0% yep how how are you running this how 01:14:37.320 --> 01:14:40.030 align:start position:0% yep how how are you running this how does<01:14:37.440> it<01:14:37.639> look<01:14:37.840> in<01:14:37.960> your<01:14:38.360> home<01:14:39.360> exactly<01:14:39.920> the 01:14:40.030 --> 01:14:40.040 align:start position:0% does it look in your home exactly the 01:14:40.040 --> 01:14:43.830 align:start position:0% does it look in your home exactly the same<01:14:40.760> exactly<01:14:41.199> the<01:14:41.360> same<01:14:42.000> I<01:14:42.199> have<01:14:42.560> uh<01:14:42.960> well<01:14:43.520> not 01:14:43.830 --> 01:14:43.840 align:start position:0% same exactly the same I have uh well not 01:14:43.840 --> 01:14:48.030 align:start position:0% same exactly the same I have uh well not exactly<01:14:44.400> I<01:14:44.600> we<01:14:44.760> have<01:14:44.960> a<01:14:45.199> little<01:14:45.719> rack<01:14:46.719> uh<01:14:47.600> but 01:14:48.030 --> 01:14:48.040 align:start position:0% exactly I we have a little rack uh but 01:14:48.040 --> 01:14:50.070 align:start position:0% exactly I we have a little rack uh but uh<01:14:48.239> you<01:14:48.400> can<01:14:48.639> put<01:14:48.840> this<01:14:49.080> in<01:14:49.360> any<01:14:49.600> Corner 01:14:50.070 --> 01:14:50.080 align:start position:0% uh you can put this in any Corner 01:14:50.080 --> 01:14:53.149 align:start position:0% uh you can put this in any Corner because<01:14:50.920> uh<01:14:51.159> if<01:14:51.280> you<01:14:51.440> want<01:14:51.719> only<01:14:52.040> one<01:14:52.280> note<01:14:53.000> I 01:14:53.149 --> 01:14:53.159 align:start position:0% because uh if you want only one note I 01:14:53.159 --> 01:14:57.350 align:start position:0% because uh if you want only one note I have<01:14:53.639> maybe<01:14:53.920> six<01:14:54.239> seven<01:14:54.760> I<01:14:55.280> if 01:14:57.350 --> 01:14:57.360 align:start position:0% have maybe six seven I if 01:14:57.360 --> 01:15:00.189 align:start position:0% have maybe six seven I if you<01:14:58.360> a<01:14:58.520> w 01:15:00.189 --> 01:15:00.199 align:start position:0% you a w 01:15:00.199 --> 01:15:04.110 align:start position:0% you a w yes<01:15:01.199> this<01:15:01.360> one<01:15:01.920> have<01:15:02.480> a<01:15:02.719> w<01:15:03.080> in<01:15:03.199> my<01:15:03.360> case<01:15:03.639> because 01:15:04.110 --> 01:15:04.120 align:start position:0% yes this one have a w in my case because 01:15:04.120 --> 01:15:07.830 align:start position:0% yes this one have a w in my case because there<01:15:04.239> is<01:15:04.360> no<01:15:04.600> noise<01:15:05.600> so<01:15:06.000> at<01:15:06.120> the<01:15:06.239> end<01:15:06.840> you 01:15:07.830 --> 01:15:07.840 align:start position:0% there is no noise so at the end you 01:15:07.840 --> 01:15:10.430 align:start position:0% there is no noise so at the end you right<01:15:08.000> now<01:15:08.199> I<01:15:08.320> have<01:15:08.560> another<01:15:08.880> rack<01:15:09.199> and<01:15:09.400> I<01:15:09.560> have 01:15:10.430 --> 01:15:10.440 align:start position:0% right now I have another rack and I have 01:15:10.440 --> 01:15:13.070 align:start position:0% right now I have another rack and I have a<01:15:10.560> little<01:15:11.080> room<01:15:11.320> for<01:15:11.560> myself<01:15:12.000> for<01:15:12.239> work<01:15:12.880> at 01:15:13.070 --> 01:15:13.080 align:start position:0% a little room for myself for work at 01:15:13.080 --> 01:15:16.149 align:start position:0% a little room for myself for work at home<01:15:13.480> but<01:15:14.480> uh<01:15:15.000> at<01:15:15.120> the<01:15:15.239> first<01:15:15.480> time<01:15:15.719> when<01:15:15.960> I 01:15:16.149 --> 01:15:16.159 align:start position:0% home but uh at the first time when I 01:15:16.159 --> 01:15:18.990 align:start position:0% home but uh at the first time when I start<01:15:16.520> running<01:15:16.840> it<01:15:17.000> I<01:15:17.120> have<01:15:17.320> it<01:15:18.000> uh<01:15:18.400> in<01:15:18.679> in<01:15:18.800> the 01:15:18.990 --> 01:15:19.000 align:start position:0% start running it I have it uh in in the 01:15:19.000 --> 01:15:22.270 align:start position:0% start running it I have it uh in in the left<01:15:19.199> side<01:15:19.360> of<01:15:19.560> the<01:15:19.719> my<01:15:19.880> home<01:15:20.400> router<01:15:21.400> a<01:15:21.639> small 01:15:22.270 --> 01:15:22.280 align:start position:0% left side of the my home router a small 01:15:22.280 --> 01:15:24.510 align:start position:0% left side of the my home router a small I<01:15:22.440> bought<01:15:22.719> a<01:15:23.080> very<01:15:23.320> very<01:15:23.560> small<01:15:24.040> ethernet 01:15:24.510 --> 01:15:24.520 align:start position:0% I bought a very very small ethernet 01:15:24.520 --> 01:15:25.590 align:start position:0% I bought a very very small ethernet cable 01:15:25.590 --> 01:15:25.600 align:start position:0% cable 01:15:25.600 --> 01:15:30.310 align:start position:0% cable and<01:15:26.320> I<01:15:26.480> only<01:15:26.719> need<01:15:27.040> one<01:15:28.280> um<01:15:29.280> uh<01:15:29.880> I<01:15:29.960> don't<01:15:30.159> need 01:15:30.310 --> 01:15:30.320 align:start position:0% and I only need one um uh I don't need 01:15:30.320 --> 01:15:34.189 align:start position:0% and I only need one um uh I don't need the<01:15:30.480> screen<01:15:31.239> I<01:15:31.360> only<01:15:31.600> need<01:15:32.000> the<01:15:32.800> P<01:15:33.320> adapter<01:15:33.880> and 01:15:34.189 --> 01:15:34.199 align:start position:0% the screen I only need the P adapter and 01:15:34.199 --> 01:15:38.110 align:start position:0% the screen I only need the P adapter and the<01:15:34.719> small<01:15:35.480> so<01:15:35.600> at<01:15:35.719> the<01:15:35.800> end<01:15:36.000> it's<01:15:36.159> no<01:15:36.800> noise<01:15:37.800> a 01:15:38.110 --> 01:15:38.120 align:start position:0% the small so at the end it's no noise a 01:15:38.120 --> 01:15:41.110 align:start position:0% the small so at the end it's no noise a little<01:15:38.520> bit<01:15:39.120> hot<01:15:39.480> but<01:15:39.760> it's<01:15:39.920> not<01:15:40.159> noise<01:15:40.719> so<01:15:41.000> at 01:15:41.110 --> 01:15:41.120 align:start position:0% little bit hot but it's not noise so at 01:15:41.120 --> 01:15:44.669 align:start position:0% little bit hot but it's not noise so at the<01:15:41.199> end<01:15:41.520> is<01:15:42.199> is<01:15:42.400> have<01:15:42.600> a<01:15:42.800> very<01:15:42.960> good<01:15:43.520> W<01:15:44.520> very 01:15:44.669 --> 01:15:44.679 align:start position:0% the end is is have a very good W very 01:15:44.679 --> 01:15:49.229 align:start position:0% the end is is have a very good W very very<01:15:44.880> good<01:15:45.520> and<01:15:46.120> only<01:15:47.120> yes<01:15:47.520> and<01:15:47.840> I<01:15:48.760> I<01:15:48.960> bought 01:15:49.229 --> 01:15:49.239 align:start position:0% very good and only yes and I I bought 01:15:49.239 --> 01:15:52.510 align:start position:0% very good and only yes and I I bought this<01:15:49.520> small<01:15:50.000> keyboard<01:15:51.000> it's<01:15:51.560> quite<01:15:51.800> useful<01:15:52.320> to 01:15:52.510 --> 01:15:52.520 align:start position:0% this small keyboard it's quite useful to 01:15:52.520 --> 01:15:54.590 align:start position:0% this small keyboard it's quite useful to to<01:15:52.679> run<01:15:52.960> this<01:15:53.280> these<01:15:53.600> devices<01:15:54.040> you<01:15:54.159> have<01:15:54.360> a 01:15:54.590 --> 01:15:54.600 align:start position:0% to run this these devices you have a 01:15:54.600 --> 01:15:57.750 align:start position:0% to run this these devices you have a mouse<01:15:55.080> on<01:15:55.280> a<01:15:55.440> keyboard<01:15:55.960> here<01:15:56.920> and<01:15:57.280> at<01:15:57.400> the<01:15:57.520> end 01:15:57.750 --> 01:15:57.760 align:start position:0% mouse on a keyboard here and at the end 01:15:57.760 --> 01:16:00.550 align:start position:0% mouse on a keyboard here and at the end is<01:15:57.960> is<01:15:58.199> quite<01:15:58.400> easy<01:15:58.679> to<01:15:59.080> to<01:15:59.320> to<01:15:59.480> work<01:15:59.840> but<01:16:00.280> only 01:16:00.550 --> 01:16:00.560 align:start position:0% is is quite easy to to to work but only 01:16:00.560 --> 01:16:03.070 align:start position:0% is is quite easy to to to work but only if<01:16:00.679> you<01:16:00.920> need<01:16:01.440> to<01:16:01.760> to<01:16:02.040> put<01:16:02.239> the<01:16:02.480> screen<01:16:02.800> or 01:16:03.070 --> 01:16:03.080 align:start position:0% if you need to to put the screen or 01:16:03.080 --> 01:16:04.510 align:start position:0% if you need to to put the screen or working<01:16:03.400> Bri<01:16:03.679> this 01:16:04.510 --> 01:16:04.520 align:start position:0% working Bri this 01:16:04.520 --> 01:16:07.910 align:start position:0% working Bri this but<01:16:05.800> yeah<01:16:06.800> I<01:16:06.920> don't<01:16:07.120> think<01:16:07.280> you<01:16:07.400> will<01:16:07.639> have<01:16:07.760> a 01:16:07.910 --> 01:16:07.920 align:start position:0% but yeah I don't think you will have a 01:16:07.920 --> 01:16:11.830 align:start position:0% but yeah I don't think you will have a problem<01:16:08.320> with<01:16:08.719> with<01:16:09.360> it's<01:16:09.520> not<01:16:09.760> so<01:16:10.440> ugly<01:16:11.440> and 01:16:11.830 --> 01:16:11.840 align:start position:0% problem with with it's not so ugly and 01:16:11.840 --> 01:16:14.990 align:start position:0% problem with with it's not so ugly and makes<01:16:12.120> no<01:16:12.320> noise<01:16:12.960> you<01:16:13.320> you<01:16:13.520> can<01:16:14.520> actually 01:16:14.990 --> 01:16:15.000 align:start position:0% makes no noise you you can actually 01:16:15.000 --> 01:16:16.470 align:start position:0% makes no noise you you can actually that's<01:16:15.159> the<01:16:15.280> idea<01:16:15.600> that<01:16:15.679> you<01:16:15.800> can<01:16:16.000> put<01:16:16.159> it<01:16:16.280> in 01:16:16.470 --> 01:16:16.480 align:start position:0% that's the idea that you can put it in 01:16:16.480 --> 01:16:19.709 align:start position:0% that's the idea that you can put it in any<01:16:16.679> corner 01:16:19.709 --> 01:16:19.719 align:start position:0% 01:16:19.719 --> 01:16:23.669 align:start position:0% so<01:16:20.719> maybe<01:16:20.960> a<01:16:21.080> little<01:16:21.400> but<01:16:21.800> uh<01:16:22.080> I<01:16:22.199> think<01:16:22.520> that<01:16:23.000> uh 01:16:23.669 --> 01:16:23.679 align:start position:0% so maybe a little but uh I think that uh 01:16:23.679 --> 01:16:28.310 align:start position:0% so maybe a little but uh I think that uh even<01:16:24.520> in<01:16:24.920> sink<01:16:25.520> because<01:16:26.239> uh<01:16:26.400> one<01:16:26.639> sink<01:16:27.080> is<01:16:27.880> uh 01:16:28.310 --> 01:16:28.320 align:start position:0% even in sink because uh one sink is uh 01:16:28.320 --> 01:16:31.669 align:start position:0% even in sink because uh one sink is uh you<01:16:28.760> you<01:16:28.880> can<01:16:29.000> see<01:16:29.199> the<01:16:29.320> lot<01:16:29.639> aage<01:16:30.440> uh<01:16:31.360> after 01:16:31.669 --> 01:16:31.679 align:start position:0% you you can see the lot aage uh after 01:16:31.679 --> 01:16:36.350 align:start position:0% you you can see the lot aage uh after the<01:16:31.880> sink<01:16:32.440> uh<01:16:32.639> it's<01:16:33.239> uh<01:16:34.040> it's<01:16:34.320> maybe<01:16:34.639> at<01:16:35.080> 50 01:16:36.350 --> 01:16:36.360 align:start position:0% the sink uh it's uh it's maybe at 50 01:16:36.360 --> 01:16:40.110 align:start position:0% the sink uh it's uh it's maybe at 50 50°<01:16:37.400> uh<01:16:38.400> maybe<01:16:38.760> uh<01:16:38.880> at<01:16:39.040> home<01:16:39.239> in<01:16:39.360> my<01:16:39.560> home<01:16:39.800> is 01:16:40.110 --> 01:16:40.120 align:start position:0% 50° uh maybe uh at home in my home is 01:16:40.120 --> 01:16:41.470 align:start position:0% 50° uh maybe uh at home in my home is around 01:16:41.470 --> 01:16:41.480 align:start position:0% around 01:16:41.480 --> 01:16:46.270 align:start position:0% around 60°<01:16:42.480> yeah<01:16:43.239> I<01:16:43.639> always<01:16:44.159> wasn't<01:16:44.480> in<01:16:45.000> place<01:16:45.280> I<01:16:45.440> was 01:16:46.270 --> 01:16:46.280 align:start position:0% 60° yeah I always wasn't in place I was 01:16:46.280 --> 01:16:51.790 align:start position:0% 60° yeah I always wasn't in place I was at<01:16:47.280> yes<01:16:47.719> uh<01:16:48.719> I<01:16:48.920> have<01:16:49.159> it<01:16:49.719> in<01:16:50.120> in<01:16:50.280> a<01:16:50.639> small<01:16:51.000> rack 01:16:51.790 --> 01:16:51.800 align:start position:0% at yes uh I have it in in a small rack 01:16:51.800 --> 01:16:54.189 align:start position:0% at yes uh I have it in in a small rack closed<01:16:52.360> small<01:16:52.600> rack<01:16:52.880> no<01:16:53.080> ventilation<01:16:53.600> at<01:16:53.719> all 01:16:54.189 --> 01:16:54.199 align:start position:0% closed small rack no ventilation at all 01:16:54.199 --> 01:16:57.310 align:start position:0% closed small rack no ventilation at all no<01:16:54.639> no<01:16:55.320> no<01:16:55.480> fun<01:16:55.880> no<01:16:56.040> noise<01:16:56.840> everything<01:16:57.120> is 01:16:57.310 --> 01:16:57.320 align:start position:0% no no no fun no noise everything is 01:16:57.320 --> 01:17:00.870 align:start position:0% no no no fun no noise everything is quiet<01:16:57.760> and<01:16:58.000> it's<01:16:58.280> around<01:16:58.880> 60°<01:16:59.880> always<01:17:00.639> if<01:17:00.719> you 01:17:00.870 --> 01:17:00.880 align:start position:0% quiet and it's around 60° always if you 01:17:00.880 --> 01:17:03.550 align:start position:0% quiet and it's around 60° always if you touch<01:17:01.120> it<01:17:01.320> you<01:17:01.520> will<01:17:02.520> notice<01:17:03.080> that<01:17:03.239> is<01:17:03.400> a 01:17:03.550 --> 01:17:03.560 align:start position:0% touch it you will notice that is a 01:17:03.560 --> 01:17:05.910 align:start position:0% touch it you will notice that is a little 01:17:05.910 --> 01:17:05.920 align:start position:0% 01:17:05.920 --> 01:17:09.390 align:start position:0% hot<01:17:06.920> yeah<01:17:07.080> yeah<01:17:07.199> you<01:17:07.360> you<01:17:07.480> could<01:17:07.760> run<01:17:08.040> it<01:17:09.000> in<01:17:09.159> a 01:17:09.390 --> 01:17:09.400 align:start position:0% hot yeah yeah you you could run it in a 01:17:09.400 --> 01:17:11.229 align:start position:0% hot yeah yeah you you could run it in a very<01:17:09.600> close<01:17:09.960> space<01:17:10.199> and<01:17:10.520> you<01:17:10.719> will<01:17:11.000> have 01:17:11.229 --> 01:17:11.239 align:start position:0% very close space and you will have 01:17:11.239 --> 01:17:14.229 align:start position:0% very close space and you will have problems<01:17:12.120> I<01:17:12.320> don't<01:17:12.480> know<01:17:13.360> it<01:17:13.520> will<01:17:13.679> depends<01:17:13.960> on 01:17:14.229 --> 01:17:14.239 align:start position:0% problems I don't know it will depends on 01:17:14.239 --> 01:17:18.110 align:start position:0% problems I don't know it will depends on your<01:17:14.679> WEA<01:17:15.159> around<01:17:15.920> you<01:17:16.080> are<01:17:16.800> probably<01:17:17.360> 40<01:17:17.719> or 01:17:18.110 --> 01:17:18.120 align:start position:0% your WEA around you are probably 40 or 01:17:18.120 --> 01:17:21.550 align:start position:0% your WEA around you are probably 40 or 50°<01:17:18.880> outside<01:17:19.639> I<01:17:19.760> don't<01:17:19.920> know<01:17:20.199> I<01:17:20.480> I<01:17:21.280> I<01:17:21.360> don't 01:17:21.550 --> 01:17:21.560 align:start position:0% 50° outside I don't know I I I don't 01:17:21.560 --> 01:17:24.110 align:start position:0% 50° outside I don't know I I I don't really<01:17:21.719> know<01:17:22.120> but<01:17:23.120> I<01:17:23.239> think<01:17:23.400> you<01:17:23.560> can<01:17:23.719> run<01:17:23.960> it 01:17:24.110 --> 01:17:24.120 align:start position:0% really know but I think you can run it 01:17:24.120 --> 01:17:25.550 align:start position:0% really know but I think you can run it it<01:17:24.480> inside 01:17:25.550 --> 01:17:25.560 align:start position:0% it inside 01:17:25.560 --> 01:17:28.149 align:start position:0% it inside if<01:17:25.679> you 01:17:28.149 --> 01:17:28.159 align:start position:0% 01:17:28.159 --> 01:17:32.310 align:start position:0% want<01:17:29.159> yes<01:17:29.679> yeah<01:17:29.920> there<01:17:30.120> yes<01:17:30.480> yeah<01:17:30.679> no<01:17:30.880> no 01:17:32.310 --> 01:17:32.320 align:start position:0% want yes yeah there yes yeah no no 01:17:32.320 --> 01:17:37.149 align:start position:0% want yes yeah there yes yeah no no problem<01:17:33.440> okay<01:17:34.440> if<01:17:34.760> any<01:17:35.000> other 01:17:37.149 --> 01:17:37.159 align:start position:0% problem okay if any other 01:17:37.159 --> 01:17:42.360 align:start position:0% problem okay if any other question<01:17:38.159> thank<01:17:38.360> you<01:17:38.760> thank<01:17:38.920> you<01:17:39.199> thank<01:17:39.360> you