WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:14.709 align:start position:0% [Music] 00:00:14.709 --> 00:00:14.719 align:start position:0% 00:00:14.719 --> 00:00:17.810 align:start position:0% well<00:00:15.719> a<00:00:16.020> note<00:00:16.260> is<00:00:16.500> uh<00:00:17.160> software<00:00:17.580> that 00:00:17.810 --> 00:00:17.820 align:start position:0% well a note is uh software that 00:00:17.820 --> 00:00:20.290 align:start position:0% well a note is uh software that downloads<00:00:18.240> a<00:00:18.359> copy<00:00:18.600> of<00:00:18.720> the<00:00:18.840> blockchain 00:00:20.290 --> 00:00:20.300 align:start position:0% downloads a copy of the blockchain 00:00:20.300 --> 00:00:22.670 align:start position:0% downloads a copy of the blockchain all<00:00:21.300> the<00:00:21.420> history<00:00:21.600> all<00:00:21.960> the<00:00:22.140> state<00:00:22.320> all<00:00:22.560> the 00:00:22.670 --> 00:00:22.680 align:start position:0% all the history all the state all the 00:00:22.680 --> 00:00:25.790 align:start position:0% all the history all the state all the accounts<00:00:23.100> transactions<00:00:23.880> and<00:00:24.660> it<00:00:24.840> keeps<00:00:25.199> that 00:00:25.790 --> 00:00:25.800 align:start position:0% accounts transactions and it keeps that 00:00:25.800 --> 00:00:28.970 align:start position:0% accounts transactions and it keeps that up<00:00:26.039> to<00:00:26.160> date<00:00:26.779> as<00:00:27.779> blocks<00:00:28.380> and<00:00:28.500> transactions 00:00:28.970 --> 00:00:28.980 align:start position:0% up to date as blocks and transactions 00:00:28.980 --> 00:00:32.269 align:start position:0% up to date as blocks and transactions take<00:00:29.279> place<00:00:29.519> and<00:00:30.240> it<00:00:30.420> also<00:00:30.660> helps<00:00:30.960> others<00:00:31.380> run 00:00:32.269 --> 00:00:32.279 align:start position:0% take place and it also helps others run 00:00:32.279 --> 00:00:34.670 align:start position:0% take place and it also helps others run a<00:00:32.460> node<00:00:32.700> so<00:00:33.180> when<00:00:33.780> you<00:00:33.899> start<00:00:34.020> up<00:00:34.200> a<00:00:34.320> node<00:00:34.500> you 00:00:34.670 --> 00:00:34.680 align:start position:0% a node so when you start up a node you 00:00:34.680 --> 00:00:37.130 align:start position:0% a node so when you start up a node you ask<00:00:34.860> all<00:00:35.100> the<00:00:35.219> others<00:00:35.579> for<00:00:36.360> the<00:00:36.719> history<00:00:36.840> of 00:00:37.130 --> 00:00:37.140 align:start position:0% ask all the others for the history of 00:00:37.140 --> 00:00:39.290 align:start position:0% ask all the others for the history of the<00:00:37.260> blockchain 00:00:39.290 --> 00:00:39.300 align:start position:0% the blockchain 00:00:39.300 --> 00:00:41.590 align:start position:0% the blockchain um<00:00:39.360> and<00:00:39.780> this<00:00:39.960> is<00:00:40.020> really<00:00:40.200> important<00:00:40.620> because 00:00:41.590 --> 00:00:41.600 align:start position:0% um and this is really important because 00:00:41.600 --> 00:00:45.470 align:start position:0% um and this is really important because the<00:00:42.600> foundation<00:00:43.460> of<00:00:44.460> ethereum<00:00:44.940> is<00:00:45.239> really 00:00:45.470 --> 00:00:45.480 align:start position:0% the foundation of ethereum is really 00:00:45.480 --> 00:00:47.750 align:start position:0% the foundation of ethereum is really like<00:00:46.020> a<00:00:46.200> network<00:00:46.320> of<00:00:46.680> decentralized<00:00:47.340> nodes 00:00:47.750 --> 00:00:47.760 align:start position:0% like a network of decentralized nodes 00:00:47.760 --> 00:00:50.869 align:start position:0% like a network of decentralized nodes and<00:00:48.800> without<00:00:49.800> those 00:00:50.869 --> 00:00:50.879 align:start position:0% and without those 00:00:50.879 --> 00:00:55.130 align:start position:0% and without those You<00:00:51.420> Know<00:00:51.860> It<00:00:52.860> uh<00:00:53.219> you<00:00:53.820> know<00:00:53.940> why<00:00:54.719> are<00:00:54.840> we<00:00:54.960> here 00:00:55.130 --> 00:00:55.140 align:start position:0% You Know It uh you know why are we here 00:00:55.140 --> 00:00:56.930 align:start position:0% You Know It uh you know why are we here I<00:00:55.500> guess<00:00:55.860> we<00:00:56.340> could<00:00:56.460> just<00:00:56.579> build<00:00:56.760> a 00:00:56.930 --> 00:00:56.940 align:start position:0% I guess we could just build a 00:00:56.940 --> 00:00:59.389 align:start position:0% I guess we could just build a centralized<00:00:57.360> solution<00:00:57.780> and 00:00:59.389 --> 00:00:59.399 align:start position:0% centralized solution and 00:00:59.399 --> 00:01:02.450 align:start position:0% centralized solution and um have<00:01:00.059> something<00:01:00.360> quicker<00:01:00.840> and 00:01:02.450 --> 00:01:02.460 align:start position:0% um have something quicker and 00:01:02.460 --> 00:01:04.210 align:start position:0% um have something quicker and yeah 00:01:04.210 --> 00:01:04.220 align:start position:0% yeah 00:01:04.220 --> 00:01:07.789 align:start position:0% yeah so<00:01:05.220> we'll<00:01:05.460> go<00:01:05.640> over<00:01:05.700> four<00:01:06.240> four<00:01:06.659> of<00:01:06.960> like<00:01:07.500> the 00:01:07.789 --> 00:01:07.799 align:start position:0% so we'll go over four four of like the 00:01:07.799 --> 00:01:09.010 align:start position:0% so we'll go over four four of like the main 00:01:09.010 --> 00:01:09.020 align:start position:0% main 00:01:09.020 --> 00:01:11.870 align:start position:0% main reasons<00:01:10.020> why<00:01:10.320> I<00:01:10.799> tell<00:01:11.100> people<00:01:11.280> like<00:01:11.520> hey<00:01:11.640> you 00:01:11.870 --> 00:01:11.880 align:start position:0% reasons why I tell people like hey you 00:01:11.880 --> 00:01:13.090 align:start position:0% reasons why I tell people like hey you should<00:01:12.000> run<00:01:12.119> a<00:01:12.240> node 00:01:13.090 --> 00:01:13.100 align:start position:0% should run a node 00:01:13.100 --> 00:01:16.310 align:start position:0% should run a node so<00:01:14.100> uh<00:01:14.640> again<00:01:14.820> supporting<00:01:15.299> the<00:01:15.420> network<00:01:15.540> it's 00:01:16.310 --> 00:01:16.320 align:start position:0% so uh again supporting the network it's 00:01:16.320 --> 00:01:18.469 align:start position:0% so uh again supporting the network it's each<00:01:16.799> additional<00:01:17.159> node<00:01:17.460> that<00:01:17.640> joins<00:01:17.939> is 00:01:18.469 --> 00:01:18.479 align:start position:0% each additional node that joins is 00:01:18.479 --> 00:01:20.929 align:start position:0% each additional node that joins is additional<00:01:18.960> capacity<00:01:19.380> to<00:01:19.619> the<00:01:19.740> network<00:01:19.939> it 00:01:20.929 --> 00:01:20.939 align:start position:0% additional capacity to the network it 00:01:20.939 --> 00:01:23.270 align:start position:0% additional capacity to the network it makes<00:01:21.119> the<00:01:21.240> network<00:01:21.420> more<00:01:21.720> robust<00:01:22.280> more 00:01:23.270 --> 00:01:23.280 align:start position:0% makes the network more robust more 00:01:23.280 --> 00:01:26.990 align:start position:0% makes the network more robust more secure<00:01:24.140> again<00:01:25.140> more<00:01:25.619> note<00:01:25.979> like<00:01:26.159> easier<00:01:26.700> for<00:01:26.880> a 00:01:26.990 --> 00:01:27.000 align:start position:0% secure again more note like easier for a 00:01:27.000 --> 00:01:28.910 align:start position:0% secure again more note like easier for a new<00:01:27.119> node<00:01:27.299> to<00:01:27.479> start<00:01:27.600> up<00:01:27.720> has<00:01:28.020> more<00:01:28.259> nodes<00:01:28.560> to 00:01:28.910 --> 00:01:28.920 align:start position:0% new node to start up has more nodes to 00:01:28.920 --> 00:01:31.429 align:start position:0% new node to start up has more nodes to to<00:01:29.159> get<00:01:29.400> the<00:01:29.939> history<00:01:30.479> from 00:01:31.429 --> 00:01:31.439 align:start position:0% to get the history from 00:01:31.439 --> 00:01:32.870 align:start position:0% to get the history from also 00:01:32.870 --> 00:01:32.880 align:start position:0% also 00:01:32.880 --> 00:01:34.070 align:start position:0% also it's<00:01:33.180> really<00:01:33.299> important<00:01:33.600> that<00:01:33.840> we<00:01:33.960> have 00:01:34.070 --> 00:01:34.080 align:start position:0% it's really important that we have 00:01:34.080 --> 00:01:35.410 align:start position:0% it's really important that we have people<00:01:34.380> running 00:01:35.410 --> 00:01:35.420 align:start position:0% people running 00:01:35.420 --> 00:01:38.030 align:start position:0% people running nodes<00:01:36.420> that<00:01:36.780> are<00:01:37.079> from<00:01:37.259> different<00:01:37.500> clients 00:01:38.030 --> 00:01:38.040 align:start position:0% nodes that are from different clients 00:01:38.040 --> 00:01:40.310 align:start position:0% nodes that are from different clients meaning<00:01:38.460> different<00:01:38.820> node<00:01:39.600> teams<00:01:40.020> different 00:01:40.310 --> 00:01:40.320 align:start position:0% meaning different node teams different 00:01:40.320 --> 00:01:42.050 align:start position:0% meaning different node teams different client<00:01:40.680> teams 00:01:42.050 --> 00:01:42.060 align:start position:0% client teams 00:01:42.060 --> 00:01:44.510 align:start position:0% client teams um<00:01:42.600> right<00:01:43.020> now<00:01:43.200> it's<00:01:43.259> kind<00:01:43.500> of<00:01:43.560> a<00:01:43.619> big<00:01:43.740> problem 00:01:44.510 --> 00:01:44.520 align:start position:0% um right now it's kind of a big problem 00:01:44.520 --> 00:01:45.230 align:start position:0% um right now it's kind of a big problem um 00:01:45.230 --> 00:01:45.240 align:start position:0% um 00:01:45.240 --> 00:01:47.510 align:start position:0% um if<00:01:45.659> you've<00:01:45.900> heard<00:01:46.020> of<00:01:46.200> Geth<00:01:46.439> or<00:01:46.619> Goa<00:01:46.920> Theory<00:01:47.220> go 00:01:47.510 --> 00:01:47.520 align:start position:0% if you've heard of Geth or Goa Theory go 00:01:47.520 --> 00:01:50.870 align:start position:0% if you've heard of Geth or Goa Theory go ethereum<00:01:48.060> right<00:01:48.659> now<00:01:48.840> about<00:01:49.020> 80<00:01:49.320> of<00:01:49.920> nodes<00:01:50.280> are 00:01:50.870 --> 00:01:50.880 align:start position:0% ethereum right now about 80 of nodes are 00:01:50.880 --> 00:01:54.410 align:start position:0% ethereum right now about 80 of nodes are Geth<00:01:51.439> and<00:01:52.439> if<00:01:52.920> there<00:01:53.100> were<00:01:53.220> to<00:01:53.460> be<00:01:53.579> a<00:01:53.759> bug<00:01:53.880> in 00:01:54.410 --> 00:01:54.420 align:start position:0% Geth and if there were to be a bug in 00:01:54.420 --> 00:01:56.749 align:start position:0% Geth and if there were to be a bug in Geth<00:01:54.920> that<00:01:55.920> would<00:01:56.040> cause<00:01:56.220> quite<00:01:56.460> a<00:01:56.579> problem 00:01:56.749 --> 00:01:56.759 align:start position:0% Geth that would cause quite a problem 00:01:56.759 --> 00:01:58.609 align:start position:0% Geth that would cause quite a problem for<00:01:57.240> the<00:01:57.540> network 00:01:58.609 --> 00:01:58.619 align:start position:0% for the network 00:01:58.619 --> 00:02:02.090 align:start position:0% for the network so<00:01:59.460> we'd<00:01:59.700> much<00:01:59.939> like<00:02:00.840> to<00:02:01.020> have<00:02:01.200> users<00:02:01.619> run<00:02:01.860> like 00:02:02.090 --> 00:02:02.100 align:start position:0% so we'd much like to have users run like 00:02:02.100 --> 00:02:04.969 align:start position:0% so we'd much like to have users run like Basu<00:02:02.759> or<00:02:03.180> another<00:02:03.299> mind 00:02:04.969 --> 00:02:04.979 align:start position:0% Basu or another mind 00:02:04.979 --> 00:02:05.630 align:start position:0% Basu or another mind um 00:02:05.630 --> 00:02:05.640 align:start position:0% um 00:02:05.640 --> 00:02:08.029 align:start position:0% um and<00:02:06.420> uh<00:02:06.659> yeah<00:02:06.840> this<00:02:07.020> makes<00:02:07.200> ethereum<00:02:07.860> much 00:02:08.029 --> 00:02:08.039 align:start position:0% and uh yeah this makes ethereum much 00:02:08.039 --> 00:02:09.469 align:start position:0% and uh yeah this makes ethereum much more<00:02:08.160> resistant 00:02:09.469 --> 00:02:09.479 align:start position:0% more resistant 00:02:09.479 --> 00:02:11.809 align:start position:0% more resistant and<00:02:09.840> I'm<00:02:09.959> sure<00:02:10.140> it<00:02:10.259> helps<00:02:10.500> the<00:02:10.739> get<00:02:11.280> developers 00:02:11.809 --> 00:02:11.819 align:start position:0% and I'm sure it helps the get developers 00:02:11.819 --> 00:02:15.050 align:start position:0% and I'm sure it helps the get developers sleep<00:02:12.120> at<00:02:12.360> night<00:02:12.480> as<00:02:12.840> well 00:02:15.050 --> 00:02:15.060 align:start position:0% 00:02:15.060 --> 00:02:17.030 align:start position:0% okay<00:02:15.540> another<00:02:15.780> big<00:02:16.080> reason<00:02:16.260> is<00:02:16.560> to<00:02:16.800> avoid 00:02:17.030 --> 00:02:17.040 align:start position:0% okay another big reason is to avoid 00:02:17.040 --> 00:02:18.589 align:start position:0% okay another big reason is to avoid lock-in 00:02:18.589 --> 00:02:18.599 align:start position:0% lock-in 00:02:18.599 --> 00:02:20.690 align:start position:0% lock-in um this<00:02:18.900> has<00:02:19.080> to<00:02:19.200> do<00:02:19.319> with<00:02:19.440> like<00:02:19.680> the<00:02:20.340> problems 00:02:20.690 --> 00:02:20.700 align:start position:0% um this has to do with like the problems 00:02:20.700 --> 00:02:22.369 align:start position:0% um this has to do with like the problems of<00:02:20.879> kind<00:02:21.000> of<00:02:21.120> the<00:02:21.180> web<00:02:21.300> 2<00:02:21.599> that<00:02:21.900> we<00:02:22.080> talk<00:02:22.260> about 00:02:22.369 --> 00:02:22.379 align:start position:0% of kind of the web 2 that we talk about 00:02:22.379 --> 00:02:24.589 align:start position:0% of kind of the web 2 that we talk about a<00:02:22.620> lot<00:02:22.680> centralization 00:02:24.589 --> 00:02:24.599 align:start position:0% a lot centralization 00:02:24.599 --> 00:02:27.229 align:start position:0% a lot centralization um<00:02:24.660> so<00:02:25.440> uh<00:02:26.160> having<00:02:26.400> a<00:02:26.580> decentralized<00:02:27.000> network 00:02:27.229 --> 00:02:27.239 align:start position:0% um so uh having a decentralized network 00:02:27.239 --> 00:02:30.350 align:start position:0% um so uh having a decentralized network of<00:02:27.540> nodes<00:02:27.840> both<00:02:28.500> helps<00:02:29.099> ethereum<00:02:29.819> from<00:02:30.060> being 00:02:30.350 --> 00:02:30.360 align:start position:0% of nodes both helps ethereum from being 00:02:30.360 --> 00:02:32.690 align:start position:0% of nodes both helps ethereum from being uh<00:02:31.200> kind<00:02:31.739> of<00:02:31.860> like 00:02:32.690 --> 00:02:32.700 align:start position:0% uh kind of like 00:02:32.700 --> 00:02:34.970 align:start position:0% uh kind of like uh<00:02:33.300> locked<00:02:33.599> into<00:02:33.720> maybe<00:02:34.200> a<00:02:34.379> small<00:02:34.560> group<00:02:34.800> of 00:02:34.970 --> 00:02:34.980 align:start position:0% uh locked into maybe a small group of 00:02:34.980 --> 00:02:39.350 align:start position:0% uh locked into maybe a small group of developers<00:02:35.520> or<00:02:35.700> teams<00:02:36.120> and<00:02:37.020> it<00:02:37.140> also 00:02:39.350 --> 00:02:39.360 align:start position:0% developers or teams and it also 00:02:39.360 --> 00:02:42.290 align:start position:0% developers or teams and it also it<00:02:39.720> enables<00:02:40.140> like<00:02:40.700> additional<00:02:41.700> systems<00:02:42.120> to<00:02:42.239> be 00:02:42.290 --> 00:02:42.300 align:start position:0% it enables like additional systems to be 00:02:42.300 --> 00:02:45.110 align:start position:0% it enables like additional systems to be built<00:02:42.599> on<00:02:42.720> top<00:02:42.840> of<00:02:43.019> ethereum<00:02:43.500> and<00:02:44.760> um<00:02:44.760> have 00:02:45.110 --> 00:02:45.120 align:start position:0% built on top of ethereum and um have 00:02:45.120 --> 00:02:47.930 align:start position:0% built on top of ethereum and um have these<00:02:45.420> properties<00:02:45.720> so<00:02:46.200> uh<00:02:47.160> if<00:02:47.519> you<00:02:47.580> you<00:02:47.760> can 00:02:47.930 --> 00:02:47.940 align:start position:0% these properties so uh if you you can 00:02:47.940 --> 00:02:51.050 align:start position:0% these properties so uh if you you can build<00:02:48.060> a<00:02:48.180> system<00:02:48.300> on<00:02:48.540> top<00:02:48.720> of<00:02:48.780> ethereum<00:02:49.260> and<00:02:49.860> uh 00:02:51.050 --> 00:02:51.060 align:start position:0% build a system on top of ethereum and uh 00:02:51.060 --> 00:02:54.350 align:start position:0% build a system on top of ethereum and uh if<00:02:51.599> designed<00:02:51.959> in<00:02:52.080> the<00:02:52.200> right<00:02:52.319> way<00:02:52.760> a<00:02:53.760> property 00:02:54.350 --> 00:02:54.360 align:start position:0% if designed in the right way a property 00:02:54.360 --> 00:02:57.530 align:start position:0% if designed in the right way a property can<00:02:55.080> only<00:02:55.260> really<00:02:55.440> be<00:02:55.620> changed<00:02:56.099> if<00:02:56.640> all<00:02:57.420> the 00:02:57.530 --> 00:02:57.540 align:start position:0% can only really be changed if all the 00:02:57.540 --> 00:03:00.110 align:start position:0% can only really be changed if all the all<00:02:57.900> the<00:02:58.080> users<00:02:58.440> and<00:02:58.920> participants<00:02:59.519> want<00:03:00.000> that 00:03:00.110 --> 00:03:00.120 align:start position:0% all the users and participants want that 00:03:00.120 --> 00:03:02.509 align:start position:0% all the users and participants want that property<00:03:00.480> to<00:03:00.540> be<00:03:00.660> changed<00:03:01.280> when<00:03:02.280> we<00:03:02.400> talk 00:03:02.509 --> 00:03:02.519 align:start position:0% property to be changed when we talk 00:03:02.519 --> 00:03:09.650 align:start position:0% property to be changed when we talk about<00:03:02.640> forkability<00:03:03.239> this<00:03:03.599> is<00:03:03.660> what<00:03:03.840> we<00:03:03.959> mean 00:03:09.650 --> 00:03:09.660 align:start position:0% 00:03:09.660 --> 00:03:11.930 align:start position:0% uh<00:03:10.080> one<00:03:10.260> other<00:03:10.379> cool<00:03:10.560> thing<00:03:10.739> is<00:03:11.040> kind<00:03:11.819> of 00:03:11.930 --> 00:03:11.940 align:start position:0% uh one other cool thing is kind of 00:03:11.940 --> 00:03:14.149 align:start position:0% uh one other cool thing is kind of relates<00:03:12.180> to<00:03:12.300> the<00:03:12.420> last<00:03:12.540> slide<00:03:12.900> is<00:03:13.379> you<00:03:13.920> get<00:03:14.040> to 00:03:14.149 --> 00:03:14.159 align:start position:0% relates to the last slide is you get to 00:03:14.159 --> 00:03:16.309 align:start position:0% relates to the last slide is you get to vote<00:03:14.340> on<00:03:14.580> changes<00:03:15.239> to<00:03:15.360> ethereum<00:03:15.720> if<00:03:15.900> you<00:03:16.019> run<00:03:16.140> a 00:03:16.309 --> 00:03:16.319 align:start position:0% vote on changes to ethereum if you run a 00:03:16.319 --> 00:03:17.210 align:start position:0% vote on changes to ethereum if you run a node 00:03:17.210 --> 00:03:17.220 align:start position:0% node 00:03:17.220 --> 00:03:19.430 align:start position:0% node so<00:03:17.700> let's<00:03:17.940> say<00:03:18.120> vitalik<00:03:18.780> and<00:03:18.959> some<00:03:19.200> of<00:03:19.319> his 00:03:19.430 --> 00:03:19.440 align:start position:0% so let's say vitalik and some of his 00:03:19.440 --> 00:03:21.589 align:start position:0% so let's say vitalik and some of his friends<00:03:19.620> create<00:03:20.099> an<00:03:20.340> update<00:03:20.580> to<00:03:20.760> Geth<00:03:21.060> and<00:03:21.360> say 00:03:21.589 --> 00:03:21.599 align:start position:0% friends create an update to Geth and say 00:03:21.599 --> 00:03:24.110 align:start position:0% friends create an update to Geth and say we<00:03:22.440> want<00:03:22.620> one<00:03:22.739> to<00:03:22.860> eat<00:03:23.040> every<00:03:23.159> block<00:03:23.400> and<00:03:24.000> we're 00:03:24.110 --> 00:03:24.120 align:start position:0% we want one to eat every block and we're 00:03:24.120 --> 00:03:26.290 align:start position:0% we want one to eat every block and we're going<00:03:24.239> to<00:03:24.300> send<00:03:24.420> it<00:03:24.540> to<00:03:24.659> devs.the<00:03:25.260> devs.eth 00:03:26.290 --> 00:03:26.300 align:start position:0% going to send it to devs.the devs.eth 00:03:26.300 --> 00:03:29.809 align:start position:0% going to send it to devs.the devs.eth and<00:03:27.300> they<00:03:27.480> all<00:03:27.599> update<00:03:27.900> their<00:03:28.019> nodes<00:03:28.700> you<00:03:29.700> can 00:03:29.809 --> 00:03:29.819 align:start position:0% and they all update their nodes you can 00:03:29.819 --> 00:03:33.350 align:start position:0% and they all update their nodes you can choose<00:03:30.180> to<00:03:30.720> support<00:03:31.319> them<00:03:31.940> by<00:03:32.940> taking<00:03:33.120> that 00:03:33.350 --> 00:03:33.360 align:start position:0% choose to support them by taking that 00:03:33.360 --> 00:03:36.350 align:start position:0% choose to support them by taking that update<00:03:33.720> essentially<00:03:34.319> voting<00:03:34.800> uh<00:03:35.580> with<00:03:36.180> their 00:03:36.350 --> 00:03:36.360 align:start position:0% update essentially voting uh with their 00:03:36.360 --> 00:03:40.190 align:start position:0% update essentially voting uh with their change<00:03:36.599> or<00:03:37.500> you<00:03:37.860> can<00:03:38.099> decide<00:03:38.519> not<00:03:38.700> to<00:03:38.959> and<00:03:39.959> you 00:03:40.190 --> 00:03:40.200 align:start position:0% change or you can decide not to and you 00:03:40.200 --> 00:03:41.809 align:start position:0% change or you can decide not to and you can<00:03:40.319> not<00:03:40.560> take<00:03:40.799> that<00:03:40.980> update<00:03:41.280> and<00:03:41.459> just<00:03:41.640> run 00:03:41.809 --> 00:03:41.819 align:start position:0% can not take that update and just run 00:03:41.819 --> 00:03:45.229 align:start position:0% can not take that update and just run the<00:03:42.360> current<00:03:42.780> version<00:03:43.019> that<00:03:43.260> you're<00:03:43.379> running 00:03:45.229 --> 00:03:45.239 align:start position:0% the current version that you're running 00:03:45.239 --> 00:03:47.690 align:start position:0% the current version that you're running um<00:03:45.299> so<00:03:45.599> if<00:03:46.019> a<00:03:46.440> lot<00:03:46.560> of<00:03:46.680> users<00:03:46.980> don't<00:03:47.400> update 00:03:47.690 --> 00:03:47.700 align:start position:0% um so if a lot of users don't update 00:03:47.700 --> 00:03:51.770 align:start position:0% um so if a lot of users don't update their<00:03:47.940> nodes<00:03:48.379> if<00:03:49.379> uh<00:03:50.040> the<00:03:50.819> like<00:03:51.239> centralized 00:03:51.770 --> 00:03:51.780 align:start position:0% their nodes if uh the like centralized 00:03:51.780 --> 00:03:53.630 align:start position:0% their nodes if uh the like centralized exchanges<00:03:52.140> and<00:03:52.379> your<00:03:52.500> wallet<00:03:52.799> providers<00:03:53.220> like 00:03:53.630 --> 00:03:53.640 align:start position:0% exchanges and your wallet providers like 00:03:53.640 --> 00:03:55.009 align:start position:0% exchanges and your wallet providers like they<00:03:53.879> don't<00:03:54.000> update<00:03:54.420> their<00:03:54.540> update<00:03:54.900> their 00:03:55.009 --> 00:03:55.019 align:start position:0% they don't update their update their 00:03:55.019 --> 00:03:56.330 align:start position:0% they don't update their update their nodes<00:03:55.260> then<00:03:55.500> this<00:03:55.680> update<00:03:55.980> doesn't<00:03:56.159> take 00:03:56.330 --> 00:03:56.340 align:start position:0% nodes then this update doesn't take 00:03:56.340 --> 00:03:57.170 align:start position:0% nodes then this update doesn't take place 00:03:57.170 --> 00:03:57.180 align:start position:0% place 00:03:57.180 --> 00:03:59.330 align:start position:0% place but<00:03:57.780> let's<00:03:57.959> say<00:03:58.080> like<00:03:58.379> all<00:03:58.560> of<00:03:58.680> those<00:03:58.920> actors 00:03:59.330 --> 00:03:59.340 align:start position:0% but let's say like all of those actors 00:03:59.340 --> 00:04:01.130 align:start position:0% but let's say like all of those actors do<00:03:59.580> update 00:04:01.130 --> 00:04:01.140 align:start position:0% do update 00:04:01.140 --> 00:04:02.570 align:start position:0% do update um then<00:04:01.620> it's<00:04:01.799> most<00:04:02.040> likely<00:04:02.280> that<00:04:02.400> this 00:04:02.570 --> 00:04:02.580 align:start position:0% um then it's most likely that this 00:04:02.580 --> 00:04:03.949 align:start position:0% um then it's most likely that this update<00:04:02.879> goes<00:04:03.180> through<00:04:03.239> and<00:04:03.599> if<00:04:03.720> you<00:04:03.840> don't 00:04:03.949 --> 00:04:03.959 align:start position:0% update goes through and if you don't 00:04:03.959 --> 00:04:05.270 align:start position:0% update goes through and if you don't have<00:04:04.080> a<00:04:04.260> node<00:04:04.379> then<00:04:04.560> you<00:04:04.739> don't<00:04:04.860> really<00:04:04.980> have<00:04:05.159> a 00:04:05.270 --> 00:04:05.280 align:start position:0% have a node then you don't really have a 00:04:05.280 --> 00:04:07.009 align:start position:0% have a node then you don't really have a choice<00:04:05.400> you<00:04:05.700> don't<00:04:05.819> have<00:04:05.940> a<00:04:06.060> vote<00:04:06.299> you<00:04:06.900> don't 00:04:07.009 --> 00:04:07.019 align:start position:0% choice you don't have a vote you don't 00:04:07.019 --> 00:04:10.670 align:start position:0% choice you don't have a vote you don't have<00:04:07.140> a<00:04:07.260> voice 00:04:10.670 --> 00:04:10.680 align:start position:0% 00:04:10.680 --> 00:04:14.390 align:start position:0% okay<00:04:11.580> and<00:04:12.360> uh<00:04:12.659> this<00:04:12.959> is<00:04:13.080> a<00:04:13.379> picture<00:04:13.620> from<00:04:14.159> one 00:04:14.390 --> 00:04:14.400 align:start position:0% okay and uh this is a picture from one 00:04:14.400 --> 00:04:17.270 align:start position:0% okay and uh this is a picture from one of<00:04:14.459> italics<00:04:14.939> blogs<00:04:15.360> uh 00:04:17.270 --> 00:04:17.280 align:start position:0% of italics blogs uh 00:04:17.280 --> 00:04:20.830 align:start position:0% of italics blogs uh again<00:04:17.820> talking<00:04:18.120> about<00:04:18.359> uh 00:04:20.830 --> 00:04:20.840 align:start position:0% again talking about uh 00:04:20.840 --> 00:04:24.050 align:start position:0% again talking about uh yeah<00:04:21.840> so<00:04:22.680> um<00:04:22.740> if<00:04:22.979> there<00:04:23.280> were<00:04:23.460> to<00:04:23.520> be<00:04:23.699> some<00:04:23.880> sort 00:04:24.050 --> 00:04:24.060 align:start position:0% yeah so um if there were to be some sort 00:04:24.060 --> 00:04:27.170 align:start position:0% yeah so um if there were to be some sort of<00:04:24.120> attack<00:04:24.300> on<00:04:24.660> the<00:04:24.780> on<00:04:25.139> the<00:04:25.259> uh<00:04:26.400> ethereum 00:04:27.170 --> 00:04:27.180 align:start position:0% of attack on the on the uh ethereum 00:04:27.180 --> 00:04:29.990 align:start position:0% of attack on the on the uh ethereum through<00:04:27.479> this<00:04:27.780> uh<00:04:28.680> like<00:04:28.919> a<00:04:29.160> new<00:04:29.280> update<00:04:29.639> comes 00:04:29.990 --> 00:04:30.000 align:start position:0% through this uh like a new update comes 00:04:30.000 --> 00:04:32.210 align:start position:0% through this uh like a new update comes in<00:04:30.120> and<00:04:30.300> it's<00:04:30.600> does<00:04:31.080> something<00:04:31.320> bad<00:04:31.620> it<00:04:31.979> takes 00:04:32.210 --> 00:04:32.220 align:start position:0% in and it's does something bad it takes 00:04:32.220 --> 00:04:33.770 align:start position:0% in and it's does something bad it takes funds 00:04:33.770 --> 00:04:33.780 align:start position:0% funds 00:04:33.780 --> 00:04:35.749 align:start position:0% funds um<00:04:33.840> that<00:04:34.320> would<00:04:34.440> be<00:04:34.620> considered<00:04:35.040> uh<00:04:35.280> like<00:04:35.520> the 00:04:35.749 --> 00:04:35.759 align:start position:0% um that would be considered uh like the 00:04:35.759 --> 00:04:38.930 align:start position:0% um that would be considered uh like the attack<00:04:35.880> we're<00:04:36.120> talking<00:04:36.300> about<00:04:36.419> here<00:04:36.740> and<00:04:37.940> uh 00:04:38.930 --> 00:04:38.940 align:start position:0% attack we're talking about here and uh 00:04:38.940 --> 00:04:40.790 align:start position:0% attack we're talking about here and uh all<00:04:39.300> the<00:04:39.479> users<00:04:39.780> all<00:04:40.139> the<00:04:40.259> node<00:04:40.380> operators 00:04:40.790 --> 00:04:40.800 align:start position:0% all the users all the node operators 00:04:40.800 --> 00:04:43.189 align:start position:0% all the users all the node operators that<00:04:40.979> decide<00:04:41.280> to<00:04:41.400> take<00:04:41.580> that<00:04:42.000> uh<00:04:42.720> contentious 00:04:43.189 --> 00:04:43.199 align:start position:0% that decide to take that uh contentious 00:04:43.199 --> 00:04:46.129 align:start position:0% that decide to take that uh contentious update<00:04:43.560> there<00:04:44.520> they<00:04:44.940> may<00:04:45.060> end<00:04:45.360> up<00:04:45.479> on<00:04:45.600> one<00:04:45.780> fork 00:04:46.129 --> 00:04:46.139 align:start position:0% update there they may end up on one fork 00:04:46.139 --> 00:04:47.810 align:start position:0% update there they may end up on one fork and<00:04:46.380> all<00:04:46.560> the<00:04:46.680> other 00:04:47.810 --> 00:04:47.820 align:start position:0% and all the other 00:04:47.820 --> 00:04:48.650 align:start position:0% and all the other um 00:04:48.650 --> 00:04:48.660 align:start position:0% um 00:04:48.660 --> 00:04:50.570 align:start position:0% um users<00:04:49.320> and<00:04:49.500> node<00:04:49.620> operators<00:04:49.979> might<00:04:50.220> end<00:04:50.340> up<00:04:50.460> on 00:04:50.570 --> 00:04:50.580 align:start position:0% users and node operators might end up on 00:04:50.580 --> 00:04:52.129 align:start position:0% users and node operators might end up on another<00:04:50.759> Fork 00:04:52.129 --> 00:04:52.139 align:start position:0% another Fork 00:04:52.139 --> 00:04:55.670 align:start position:0% another Fork and<00:04:53.100> he<00:04:53.460> talks<00:04:53.759> about<00:04:54.080> uh<00:04:55.080> these<00:04:55.320> are<00:04:55.440> kind<00:04:55.620> of 00:04:55.670 --> 00:04:55.680 align:start position:0% and he talks about uh these are kind of 00:04:55.680 --> 00:04:56.930 align:start position:0% and he talks about uh these are kind of like<00:04:55.800> the<00:04:55.919> three<00:04:56.100> scenarios<00:04:56.580> that<00:04:56.820> would 00:04:56.930 --> 00:04:56.940 align:start position:0% like the three scenarios that would 00:04:56.940 --> 00:04:58.730 align:start position:0% like the three scenarios that would happen<00:04:57.120> in<00:04:57.419> this<00:04:57.479> case 00:04:58.730 --> 00:04:58.740 align:start position:0% happen in this case 00:04:58.740 --> 00:05:02.930 align:start position:0% happen in this case and<00:04:59.580> uh<00:05:00.180> so<00:05:00.900> we<00:05:01.680> prefer<00:05:02.040> the<00:05:02.400> options<00:05:02.699> like 00:05:02.930 --> 00:05:02.940 align:start position:0% and uh so we prefer the options like 00:05:02.940 --> 00:05:04.670 align:start position:0% and uh so we prefer the options like toward<00:05:03.240> the<00:05:03.360> left<00:05:03.540> so<00:05:03.780> we<00:05:04.020> would<00:05:04.500> want 00:05:04.670 --> 00:05:04.680 align:start position:0% toward the left so we would want 00:05:04.680 --> 00:05:06.710 align:start position:0% toward the left so we would want something<00:05:04.919> like<00:05:05.220> this<00:05:05.400> to<00:05:05.699> fail 00:05:06.710 --> 00:05:06.720 align:start position:0% something like this to fail 00:05:06.720 --> 00:05:10.490 align:start position:0% something like this to fail obviously<00:05:07.440> and<00:05:08.160> uh<00:05:08.940> however 00:05:10.490 --> 00:05:10.500 align:start position:0% obviously and uh however 00:05:10.500 --> 00:05:13.129 align:start position:0% obviously and uh however uh<00:05:11.100> even<00:05:11.340> if<00:05:11.580> it<00:05:11.820> just<00:05:12.240> ends<00:05:12.540> up<00:05:12.600> in<00:05:12.780> chaos 00:05:13.129 --> 00:05:13.139 align:start position:0% uh even if it just ends up in chaos 00:05:13.139 --> 00:05:16.070 align:start position:0% uh even if it just ends up in chaos meaning<00:05:13.440> like<00:05:14.000> uh<00:05:15.000> you<00:05:15.479> know<00:05:15.540> maybe<00:05:15.660> half<00:05:15.900> the 00:05:16.070 --> 00:05:16.080 align:start position:0% meaning like uh you know maybe half the 00:05:16.080 --> 00:05:17.450 align:start position:0% meaning like uh you know maybe half the exchanges 00:05:17.450 --> 00:05:17.460 align:start position:0% exchanges 00:05:17.460 --> 00:05:20.150 align:start position:0% exchanges show<00:05:18.060> one<00:05:18.419> state<00:05:18.660> of<00:05:18.900> the<00:05:19.020> ethereum<00:05:19.620> and<00:05:19.919> maybe 00:05:20.150 --> 00:05:20.160 align:start position:0% show one state of the ethereum and maybe 00:05:20.160 --> 00:05:21.770 align:start position:0% show one state of the ethereum and maybe half<00:05:20.460> the<00:05:20.639> you<00:05:20.940> know<00:05:21.060> exchangers<00:05:21.419> and<00:05:21.540> wallets 00:05:21.770 --> 00:05:21.780 align:start position:0% half the you know exchangers and wallets 00:05:21.780 --> 00:05:23.570 align:start position:0% half the you know exchangers and wallets show<00:05:21.960> another<00:05:22.139> state<00:05:22.680> of<00:05:22.860> ethereum<00:05:23.220> that's 00:05:23.570 --> 00:05:23.580 align:start position:0% show another state of ethereum that's 00:05:23.580 --> 00:05:25.850 align:start position:0% show another state of ethereum that's still<00:05:23.820> like<00:05:24.000> much<00:05:24.240> better<00:05:24.479> than<00:05:24.960> uh<00:05:25.680> the 00:05:25.850 --> 00:05:25.860 align:start position:0% still like much better than uh the 00:05:25.860 --> 00:05:27.170 align:start position:0% still like much better than uh the attackers 00:05:27.170 --> 00:05:27.180 align:start position:0% attackers 00:05:27.180 --> 00:05:30.110 align:start position:0% attackers becoming<00:05:27.720> Victorious 00:05:30.110 --> 00:05:30.120 align:start position:0% becoming Victorious 00:05:30.120 --> 00:05:32.510 align:start position:0% becoming Victorious it<00:05:30.660> kind<00:05:30.780> of<00:05:30.900> makes<00:05:31.100> the<00:05:32.100> attack<00:05:32.220> like 00:05:32.510 --> 00:05:32.520 align:start position:0% it kind of makes the attack like 00:05:32.520 --> 00:05:34.370 align:start position:0% it kind of makes the attack like extremely<00:05:32.940> expensive<00:05:33.360> even<00:05:33.660> if<00:05:33.960> the<00:05:34.259> attack 00:05:34.370 --> 00:05:34.380 align:start position:0% extremely expensive even if the attack 00:05:34.380 --> 00:05:37.610 align:start position:0% extremely expensive even if the attack doesn't<00:05:34.800> uh<00:05:35.759> you<00:05:36.000> know<00:05:36.120> isn't<00:05:36.360> Victorious<00:05:36.780> or 00:05:37.610 --> 00:05:37.620 align:start position:0% doesn't uh you know isn't Victorious or 00:05:37.620 --> 00:05:39.650 align:start position:0% doesn't uh you know isn't Victorious or it<00:05:37.740> doesn't<00:05:38.100> fail<00:05:38.340> I<00:05:38.580> should<00:05:38.699> say<00:05:38.820> it's<00:05:39.479> still 00:05:39.650 --> 00:05:39.660 align:start position:0% it doesn't fail I should say it's still 00:05:39.660 --> 00:05:46.670 align:start position:0% it doesn't fail I should say it's still extremely<00:05:40.080> costly 00:05:46.670 --> 00:05:46.680 align:start position:0% 00:05:46.680 --> 00:05:48.230 align:start position:0% and<00:05:47.039> then<00:05:47.220> an<00:05:47.520> important<00:05:47.820> question<00:05:47.940> everyone 00:05:48.230 --> 00:05:48.240 align:start position:0% and then an important question everyone 00:05:48.240 --> 00:05:50.810 align:start position:0% and then an important question everyone wants<00:05:48.539> to<00:05:48.600> know<00:05:48.720> is<00:05:48.780> can<00:05:48.960> I<00:05:49.139> run<00:05:49.259> a<00:05:49.380> full<00:05:49.500> node 00:05:50.810 --> 00:05:50.820 align:start position:0% wants to know is can I run a full node 00:05:50.820 --> 00:05:53.210 align:start position:0% wants to know is can I run a full node um<00:05:50.940> a<00:05:51.300> lot<00:05:51.419> of<00:05:51.539> people<00:05:51.660> I<00:05:52.199> I<00:05:52.440> talk<00:05:52.680> to<00:05:52.800> they<00:05:53.100> want 00:05:53.210 --> 00:05:53.220 align:start position:0% um a lot of people I I talk to they want 00:05:53.220 --> 00:05:54.469 align:start position:0% um a lot of people I I talk to they want to<00:05:53.340> run<00:05:53.460> a<00:05:53.580> node<00:05:53.759> but<00:05:53.880> they<00:05:54.060> don't<00:05:54.180> know<00:05:54.300> if 00:05:54.469 --> 00:05:54.479 align:start position:0% to run a node but they don't know if 00:05:54.479 --> 00:05:56.450 align:start position:0% to run a node but they don't know if they<00:05:54.600> can 00:05:56.450 --> 00:05:56.460 align:start position:0% they can 00:05:56.460 --> 00:05:58.790 align:start position:0% they can so<00:05:56.820> here<00:05:57.000> are<00:05:57.120> some<00:05:57.240> of<00:05:57.360> the<00:05:57.360> requirements 00:05:58.790 --> 00:05:58.800 align:start position:0% so here are some of the requirements 00:05:58.800 --> 00:06:00.950 align:start position:0% so here are some of the requirements um<00:05:58.860> your<00:05:59.340> computer<00:05:59.460> needs<00:05:59.940> 8<00:06:00.120> to<00:06:00.240> 16<00:06:00.419> gigabytes 00:06:00.950 --> 00:06:00.960 align:start position:0% um your computer needs 8 to 16 gigabytes 00:06:00.960 --> 00:06:03.890 align:start position:0% um your computer needs 8 to 16 gigabytes of<00:06:01.080> memory<00:06:01.380> two<00:06:02.280> terabytes<00:06:02.759> of<00:06:02.940> fast<00:06:03.120> SSD 00:06:03.890 --> 00:06:03.900 align:start position:0% of memory two terabytes of fast SSD 00:06:03.900 --> 00:06:05.650 align:start position:0% of memory two terabytes of fast SSD storage<00:06:04.199> that's 00:06:05.650 --> 00:06:05.660 align:start position:0% storage that's 00:06:05.660 --> 00:06:08.210 align:start position:0% storage that's this<00:06:06.660> is<00:06:06.840> kind<00:06:07.020> of<00:06:07.139> the<00:06:07.259> biggest<00:06:07.380> problem<00:06:07.740> for 00:06:08.210 --> 00:06:08.220 align:start position:0% this is kind of the biggest problem for 00:06:08.220 --> 00:06:12.050 align:start position:0% this is kind of the biggest problem for people<00:06:08.580> is<00:06:09.000> is<00:06:09.300> this<00:06:09.660> fast<00:06:09.840> SSD<00:06:10.500> storage 00:06:12.050 --> 00:06:12.060 align:start position:0% people is is this fast SSD storage 00:06:12.060 --> 00:06:13.790 align:start position:0% people is is this fast SSD storage um 00:06:13.790 --> 00:06:13.800 align:start position:0% um 00:06:13.800 --> 00:06:15.650 align:start position:0% um even<00:06:14.340> some<00:06:14.639> of<00:06:14.759> like<00:06:14.940> what<00:06:15.300> you<00:06:15.419> might<00:06:15.539> think 00:06:15.650 --> 00:06:15.660 align:start position:0% even some of like what you might think 00:06:15.660 --> 00:06:17.390 align:start position:0% even some of like what you might think is<00:06:15.840> like<00:06:16.020> a<00:06:16.199> really<00:06:16.320> fast<00:06:16.560> external<00:06:17.100> storage 00:06:17.390 --> 00:06:17.400 align:start position:0% is like a really fast external storage 00:06:17.400 --> 00:06:20.210 align:start position:0% is like a really fast external storage drive<00:06:17.820> like<00:06:18.360> uh<00:06:18.840> you<00:06:19.020> know<00:06:19.139> it's<00:06:19.560> super<00:06:19.860> highly 00:06:20.210 --> 00:06:20.220 align:start position:0% drive like uh you know it's super highly 00:06:20.220 --> 00:06:22.189 align:start position:0% drive like uh you know it's super highly rated<00:06:20.460> for<00:06:20.639> like<00:06:20.820> moving<00:06:21.060> videos<00:06:21.240> and<00:06:21.720> in 00:06:22.189 --> 00:06:22.199 align:start position:0% rated for like moving videos and in 00:06:22.199 --> 00:06:24.529 align:start position:0% rated for like moving videos and in photos<00:06:22.440> it<00:06:23.280> might<00:06:23.460> not<00:06:23.580> be<00:06:23.759> fast<00:06:24.000> enough<00:06:24.240> for 00:06:24.529 --> 00:06:24.539 align:start position:0% photos it might not be fast enough for 00:06:24.539 --> 00:06:26.150 align:start position:0% photos it might not be fast enough for syncing<00:06:25.080> a<00:06:25.199> node 00:06:26.150 --> 00:06:26.160 align:start position:0% syncing a node 00:06:26.160 --> 00:06:30.110 align:start position:0% syncing a node um 00:06:30.110 --> 00:06:30.120 align:start position:0% 00:06:30.120 --> 00:06:33.170 align:start position:0% uh<00:06:30.660> right<00:06:30.780> now<00:06:30.960> only<00:06:31.319> one<00:06:31.680> terabyte<00:06:32.340> is<00:06:32.940> used 00:06:33.170 --> 00:06:33.180 align:start position:0% uh right now only one terabyte is used 00:06:33.180 --> 00:06:35.090 align:start position:0% uh right now only one terabyte is used by<00:06:33.419> nodes<00:06:33.660> to<00:06:33.900> store<00:06:34.139> the<00:06:34.319> state 00:06:35.090 --> 00:06:35.100 align:start position:0% by nodes to store the state 00:06:35.100 --> 00:06:36.590 align:start position:0% by nodes to store the state um<00:06:35.160> this<00:06:35.280> is<00:06:35.460> growing<00:06:35.699> about<00:06:35.819> 10<00:06:36.060> gigabytes 00:06:36.590 --> 00:06:36.600 align:start position:0% um this is growing about 10 gigabytes 00:06:36.600 --> 00:06:37.570 align:start position:0% um this is growing about 10 gigabytes per<00:06:36.780> week 00:06:37.570 --> 00:06:37.580 align:start position:0% per week 00:06:37.580 --> 00:06:40.969 align:start position:0% per week some<00:06:38.580> nodes<00:06:38.880> have<00:06:39.180> options<00:06:39.539> to<00:06:39.720> use<00:06:39.900> less<00:06:40.199> uh 00:06:40.969 --> 00:06:40.979 align:start position:0% some nodes have options to use less uh 00:06:40.979 --> 00:06:42.770 align:start position:0% some nodes have options to use less uh they're<00:06:41.160> kind<00:06:41.340> of 00:06:42.770 --> 00:06:42.780 align:start position:0% they're kind of 00:06:42.780 --> 00:06:44.029 align:start position:0% they're kind of they're<00:06:43.319> just<00:06:43.500> beyond<00:06:43.740> like<00:06:43.860> the 00:06:44.029 --> 00:06:44.039 align:start position:0% they're just beyond like the 00:06:44.039 --> 00:06:46.370 align:start position:0% they're just beyond like the experimental<00:06:44.520> phase<00:06:44.819> they're<00:06:45.539> like<00:06:46.080> they're 00:06:46.370 --> 00:06:46.380 align:start position:0% experimental phase they're like they're 00:06:46.380 --> 00:06:47.749 align:start position:0% experimental phase they're like they're solid<00:06:46.680> options<00:06:46.919> but<00:06:47.280> they<00:06:47.460> have<00:06:47.580> their 00:06:47.749 --> 00:06:47.759 align:start position:0% solid options but they have their 00:06:47.759 --> 00:06:49.430 align:start position:0% solid options but they have their limitations 00:06:49.430 --> 00:06:49.440 align:start position:0% limitations 00:06:49.440 --> 00:06:52.029 align:start position:0% limitations um<00:06:49.500> and<00:06:49.979> don't<00:06:50.160> quite<00:06:50.460> maybe<00:06:50.699> meet<00:06:51.060> all<00:06:51.419> of<00:06:51.539> the 00:06:52.029 --> 00:06:52.039 align:start position:0% um and don't quite maybe meet all of the 00:06:52.039 --> 00:06:54.950 align:start position:0% um and don't quite maybe meet all of the uh<00:06:53.039> use<00:06:53.460> cases<00:06:53.699> that<00:06:53.880> people<00:06:54.000> need<00:06:54.300> and<00:06:54.840> then 00:06:54.950 --> 00:06:54.960 align:start position:0% uh use cases that people need and then 00:06:54.960 --> 00:06:57.890 align:start position:0% uh use cases that people need and then the<00:06:55.259> CPU<00:06:55.620> is<00:06:55.800> not<00:06:55.979> usually<00:06:56.220> a<00:06:56.280> bottleneck<00:06:56.639> so 00:06:57.890 --> 00:06:57.900 align:start position:0% the CPU is not usually a bottleneck so 00:06:57.900 --> 00:07:00.469 align:start position:0% the CPU is not usually a bottleneck so um<00:06:58.440> most<00:06:59.039> laptops<00:06:59.580> that<00:06:59.759> are<00:06:59.880> within<00:07:00.240> like 00:07:00.469 --> 00:07:00.479 align:start position:0% um most laptops that are within like 00:07:00.479 --> 00:07:09.290 align:start position:0% um most laptops that are within like five<00:07:00.840> years<00:07:01.080> old<00:07:01.259> should<00:07:01.620> should<00:07:01.620> do<00:07:02.100> fine 00:07:09.290 --> 00:07:09.300 align:start position:0% 00:07:09.300 --> 00:07:11.330 align:start position:0% internet<00:07:09.660> can<00:07:10.139> be<00:07:10.319> a<00:07:10.620> little<00:07:10.680> bit<00:07:10.800> of<00:07:10.919> an<00:07:10.979> issue 00:07:11.330 --> 00:07:11.340 align:start position:0% internet can be a little bit of an issue 00:07:11.340 --> 00:07:13.610 align:start position:0% internet can be a little bit of an issue so<00:07:11.520> you<00:07:11.699> need<00:07:11.819> about<00:07:12.000> 10<00:07:12.360> megabits<00:07:13.139> upload 00:07:13.610 --> 00:07:13.620 align:start position:0% so you need about 10 megabits upload 00:07:13.620 --> 00:07:15.469 align:start position:0% so you need about 10 megabits upload download<00:07:13.800> and<00:07:14.340> it<00:07:14.520> needs<00:07:14.819> to<00:07:14.880> be<00:07:15.000> lower 00:07:15.469 --> 00:07:15.479 align:start position:0% download and it needs to be lower 00:07:15.479 --> 00:07:18.350 align:start position:0% download and it needs to be lower latency<00:07:16.020> connection 00:07:18.350 --> 00:07:18.360 align:start position:0% latency connection 00:07:18.360 --> 00:07:20.629 align:start position:0% latency connection um the<00:07:18.600> data<00:07:18.900> cap<00:07:19.020> is<00:07:19.560> can<00:07:19.979> be<00:07:20.160> a<00:07:20.280> problem<00:07:20.400> in 00:07:20.629 --> 00:07:20.639 align:start position:0% um the data cap is can be a problem in 00:07:20.639 --> 00:07:23.150 align:start position:0% um the data cap is can be a problem in the<00:07:20.759> U.S<00:07:21.060> a<00:07:21.720> lot<00:07:21.960> of<00:07:22.139> Internet<00:07:22.380> providers<00:07:22.919> have 00:07:23.150 --> 00:07:23.160 align:start position:0% the U.S a lot of Internet providers have 00:07:23.160 --> 00:07:26.089 align:start position:0% the U.S a lot of Internet providers have a<00:07:23.280> one<00:07:23.400> terabyte<00:07:24.000> per<00:07:24.539> month<00:07:24.720> cap<00:07:25.139> I've<00:07:25.800> talked 00:07:26.089 --> 00:07:26.099 align:start position:0% a one terabyte per month cap I've talked 00:07:26.099 --> 00:07:28.129 align:start position:0% a one terabyte per month cap I've talked to<00:07:26.160> some<00:07:26.400> people<00:07:26.580> uh<00:07:27.419> here<00:07:27.660> in<00:07:27.780> South<00:07:27.960> America 00:07:28.129 --> 00:07:28.139 align:start position:0% to some people uh here in South America 00:07:28.139 --> 00:07:29.629 align:start position:0% to some people uh here in South America and<00:07:28.500> they<00:07:28.740> don't<00:07:28.800> seem<00:07:29.039> to<00:07:29.160> have<00:07:29.280> that<00:07:29.460> problem 00:07:29.629 --> 00:07:29.639 align:start position:0% and they don't seem to have that problem 00:07:29.639 --> 00:07:32.150 align:start position:0% and they don't seem to have that problem or<00:07:30.180> at<00:07:30.360> least<00:07:30.479> they're<00:07:30.780> not<00:07:30.900> aware<00:07:31.139> of<00:07:31.259> it<00:07:31.380> and 00:07:32.150 --> 00:07:32.160 align:start position:0% or at least they're not aware of it and 00:07:32.160 --> 00:07:34.070 align:start position:0% or at least they're not aware of it and then<00:07:32.400> definitely<00:07:33.060> can't<00:07:33.360> really<00:07:33.539> run<00:07:33.720> it<00:07:33.900> on 00:07:34.070 --> 00:07:34.080 align:start position:0% then definitely can't really run it on 00:07:34.080 --> 00:07:40.010 align:start position:0% then definitely can't really run it on like<00:07:34.259> a<00:07:34.440> slow<00:07:34.620> cellular<00:07:35.160> or<00:07:35.580> Wi-Fi<00:07:36.000> connection 00:07:40.010 --> 00:07:40.020 align:start position:0% 00:07:40.020 --> 00:07:41.809 align:start position:0% okay<00:07:40.440> I'm<00:07:40.860> gonna<00:07:40.979> quickly<00:07:41.280> talk<00:07:41.400> about<00:07:41.580> like 00:07:41.809 --> 00:07:41.819 align:start position:0% okay I'm gonna quickly talk about like 00:07:41.819 --> 00:07:43.670 align:start position:0% okay I'm gonna quickly talk about like the<00:07:41.940> SSD<00:07:42.419> types 00:07:43.670 --> 00:07:43.680 align:start position:0% the SSD types 00:07:43.680 --> 00:07:45.170 align:start position:0% the SSD types um<00:07:43.740> kind<00:07:44.220> of<00:07:44.340> the<00:07:44.460> number<00:07:44.639> that<00:07:44.880> you<00:07:45.000> want<00:07:45.060> to 00:07:45.170 --> 00:07:45.180 align:start position:0% um kind of the number that you want to 00:07:45.180 --> 00:07:48.529 align:start position:0% um kind of the number that you want to know<00:07:45.300> is<00:07:45.479> this<00:07:45.780> like<00:07:46.020> 10<00:07:46.440> 10K<00:07:47.180> input<00:07:48.180> output 00:07:48.529 --> 00:07:48.539 align:start position:0% know is this like 10 10K input output 00:07:48.539 --> 00:07:51.170 align:start position:0% know is this like 10 10K input output operations<00:07:49.199> per<00:07:49.500> second 00:07:51.170 --> 00:07:51.180 align:start position:0% operations per second 00:07:51.180 --> 00:07:52.070 align:start position:0% operations per second um 00:07:52.070 --> 00:07:52.080 align:start position:0% um 00:07:52.080 --> 00:07:55.670 align:start position:0% um so<00:07:52.740> yeah<00:07:53.120> nodes<00:07:54.120> they<00:07:55.080> are<00:07:55.380> essentially 00:07:55.670 --> 00:07:55.680 align:start position:0% so yeah nodes they are essentially 00:07:55.680 --> 00:07:57.350 align:start position:0% so yeah nodes they are essentially writing<00:07:55.979> like<00:07:56.160> tons<00:07:56.340> of<00:07:56.520> like<00:07:56.639> small<00:07:56.880> files 00:07:57.350 --> 00:07:57.360 align:start position:0% writing like tons of like small files 00:07:57.360 --> 00:07:59.510 align:start position:0% writing like tons of like small files back<00:07:57.599> and<00:07:57.720> forth<00:07:58.020> reading<00:07:58.680> and<00:07:58.800> writing<00:07:59.099> to 00:07:59.510 --> 00:07:59.520 align:start position:0% back and forth reading and writing to 00:07:59.520 --> 00:08:02.390 align:start position:0% back and forth reading and writing to have<00:08:00.120> SSD<00:08:00.780> and 00:08:02.390 --> 00:08:02.400 align:start position:0% have SSD and 00:08:02.400 --> 00:08:04.189 align:start position:0% have SSD and um this<00:08:02.819> is<00:08:02.940> kind<00:08:03.120> of<00:08:03.180> like<00:08:03.360> not<00:08:03.720> really<00:08:03.960> a 00:08:04.189 --> 00:08:04.199 align:start position:0% um this is kind of like not really a 00:08:04.199 --> 00:08:07.550 align:start position:0% um this is kind of like not really a common<00:08:04.380> rating<00:08:04.800> that<00:08:05.479> uh<00:08:06.479> SSD<00:08:07.020> companies<00:08:07.319> tell 00:08:07.550 --> 00:08:07.560 align:start position:0% common rating that uh SSD companies tell 00:08:07.560 --> 00:08:08.629 align:start position:0% common rating that uh SSD companies tell consumers 00:08:08.629 --> 00:08:08.639 align:start position:0% consumers 00:08:08.639 --> 00:08:11.029 align:start position:0% consumers because<00:08:09.300> it's<00:08:09.479> not<00:08:09.720> quite<00:08:09.960> applicable<00:08:10.740> to 00:08:11.029 --> 00:08:11.039 align:start position:0% because it's not quite applicable to 00:08:11.039 --> 00:08:12.409 align:start position:0% because it's not quite applicable to what<00:08:11.220> most<00:08:11.400> consumers<00:08:11.759> are<00:08:11.940> doing<00:08:12.060> with<00:08:12.300> their 00:08:12.409 --> 00:08:12.419 align:start position:0% what most consumers are doing with their 00:08:12.419 --> 00:08:13.909 align:start position:0% what most consumers are doing with their SSD 00:08:13.909 --> 00:08:13.919 align:start position:0% SSD 00:08:13.919 --> 00:08:16.129 align:start position:0% SSD most<00:08:14.460> consumers<00:08:14.880> are<00:08:15.060> just<00:08:15.240> yeah<00:08:15.479> like<00:08:15.720> moving 00:08:16.129 --> 00:08:16.139 align:start position:0% most consumers are just yeah like moving 00:08:16.139 --> 00:08:22.010 align:start position:0% most consumers are just yeah like moving at<00:08:16.259> large<00:08:16.500> video<00:08:16.740> files<00:08:17.160> storing<00:08:17.580> photos 00:08:22.010 --> 00:08:22.020 align:start position:0% 00:08:22.020 --> 00:08:23.210 align:start position:0% okay 00:08:23.210 --> 00:08:23.220 align:start position:0% okay 00:08:23.220 --> 00:08:26.689 align:start position:0% okay um internal<00:08:23.759> ssds<00:08:24.360> M2<00:08:24.720> and<00:08:24.960> vme<00:08:25.460> uh<00:08:26.460> that's 00:08:26.689 --> 00:08:26.699 align:start position:0% um internal ssds M2 and vme uh that's 00:08:26.699 --> 00:08:29.510 align:start position:0% um internal ssds M2 and vme uh that's like<00:08:27.060> very<00:08:28.020> popular<00:08:28.199> now 00:08:29.510 --> 00:08:29.520 align:start position:0% like very popular now 00:08:29.520 --> 00:08:30.170 align:start position:0% like very popular now um 00:08:30.170 --> 00:08:30.180 align:start position:0% um 00:08:30.180 --> 00:08:33.310 align:start position:0% um within<00:08:30.960> the<00:08:31.139> like<00:08:31.259> 200<00:08:31.620> range<00:08:32.279> you<00:08:32.760> can<00:08:32.940> get 00:08:33.310 --> 00:08:33.320 align:start position:0% within the like 200 range you can get 00:08:33.320 --> 00:08:35.570 align:start position:0% within the like 200 range you can get for<00:08:34.320> this 00:08:35.570 --> 00:08:35.580 align:start position:0% for this 00:08:35.580 --> 00:08:37.850 align:start position:0% for this um and<00:08:36.539> then<00:08:36.719> yeah<00:08:37.140> you<00:08:37.440> probably<00:08:37.560> just<00:08:37.740> want 00:08:37.850 --> 00:08:37.860 align:start position:0% um and then yeah you probably just want 00:08:37.860 --> 00:08:39.290 align:start position:0% um and then yeah you probably just want to<00:08:37.979> stick<00:08:38.099> with<00:08:38.279> that<00:08:38.399> the<00:08:38.700> other<00:08:38.820> options<00:08:39.120> if 00:08:39.290 --> 00:08:39.300 align:start position:0% to stick with that the other options if 00:08:39.300 --> 00:08:40.730 align:start position:0% to stick with that the other options if you<00:08:39.419> have<00:08:39.539> them<00:08:39.659> like<00:08:39.839> lying<00:08:40.140> around<00:08:40.260> those 00:08:40.730 --> 00:08:40.740 align:start position:0% you have them like lying around those 00:08:40.740 --> 00:08:43.310 align:start position:0% you have them like lying around those might<00:08:40.979> work<00:08:41.279> that's<00:08:42.120> not<00:08:42.300> going<00:08:42.479> to<00:08:42.599> work 00:08:43.310 --> 00:08:43.320 align:start position:0% might work that's not going to work 00:08:43.320 --> 00:08:46.730 align:start position:0% might work that's not going to work uh<00:08:43.919> external<00:08:44.399> ssds<00:08:45.180> uh<00:08:45.839> the<00:08:45.959> reason<00:08:46.080> why<00:08:46.380> like 00:08:46.730 --> 00:08:46.740 align:start position:0% uh external ssds uh the reason why like 00:08:46.740 --> 00:08:49.730 align:start position:0% uh external ssds uh the reason why like I<00:08:46.980> I<00:08:47.700> want<00:08:48.180> to<00:08:48.240> emphasize<00:08:48.540> this<00:08:48.779> is<00:08:49.019> because<00:08:49.260> I 00:08:49.730 --> 00:08:49.740 align:start position:0% I I want to emphasize this is because I 00:08:49.740 --> 00:08:51.829 align:start position:0% I I want to emphasize this is because I think<00:08:49.860> there's<00:08:50.580> a<00:08:51.060> lot<00:08:51.180> of<00:08:51.240> people<00:08:51.360> out<00:08:51.660> there 00:08:51.829 --> 00:08:51.839 align:start position:0% think there's a lot of people out there 00:08:51.839 --> 00:08:54.650 align:start position:0% think there's a lot of people out there with<00:08:52.140> laptops<00:08:52.880> and<00:08:53.880> don't<00:08:54.060> have<00:08:54.240> like<00:08:54.480> a 00:08:54.650 --> 00:08:54.660 align:start position:0% with laptops and don't have like a 00:08:54.660 --> 00:08:57.290 align:start position:0% with laptops and don't have like a dedicated<00:08:55.100> desktop<00:08:56.100> or<00:08:56.399> a<00:08:56.580> computer<00:08:56.700> just<00:08:57.120> for 00:08:57.290 --> 00:08:57.300 align:start position:0% dedicated desktop or a computer just for 00:08:57.300 --> 00:09:00.050 align:start position:0% dedicated desktop or a computer just for running<00:08:57.540> a<00:08:57.720> full<00:08:57.839> note<00:08:58.019> and<00:08:58.800> so 00:09:00.050 --> 00:09:00.060 align:start position:0% running a full note and so 00:09:00.060 --> 00:09:01.310 align:start position:0% running a full note and so um I<00:09:00.420> want<00:09:00.480> people<00:09:00.600> to<00:09:00.779> be<00:09:00.899> able<00:09:00.959> to<00:09:01.080> run<00:09:01.200> a 00:09:01.310 --> 00:09:01.320 align:start position:0% um I want people to be able to run a 00:09:01.320 --> 00:09:03.350 align:start position:0% um I want people to be able to run a full<00:09:01.440> node<00:09:01.680> on<00:09:01.920> their<00:09:02.040> laptop<00:09:02.399> maybe<00:09:03.120> like 00:09:03.350 --> 00:09:03.360 align:start position:0% full node on their laptop maybe like 00:09:03.360 --> 00:09:04.910 align:start position:0% full node on their laptop maybe like while<00:09:03.540> they're<00:09:03.660> not<00:09:03.839> using<00:09:04.140> it<00:09:04.260> or<00:09:04.560> if<00:09:04.800> they 00:09:04.910 --> 00:09:04.920 align:start position:0% while they're not using it or if they 00:09:04.920 --> 00:09:06.650 align:start position:0% while they're not using it or if they have<00:09:05.040> an<00:09:05.160> extra<00:09:05.339> one 00:09:06.650 --> 00:09:06.660 align:start position:0% have an extra one 00:09:06.660 --> 00:09:09.290 align:start position:0% have an extra one um<00:09:07.200> so<00:09:07.920> check<00:09:08.220> to<00:09:08.399> see<00:09:08.519> if<00:09:08.640> your<00:09:08.760> laptop<00:09:09.060> has 00:09:09.290 --> 00:09:09.300 align:start position:0% um so check to see if your laptop has 00:09:09.300 --> 00:09:12.110 align:start position:0% um so check to see if your laptop has like<00:09:09.540> one<00:09:09.779> of<00:09:09.959> these<00:09:10.380> connections 00:09:12.110 --> 00:09:12.120 align:start position:0% like one of these connections 00:09:12.120 --> 00:09:21.050 align:start position:0% like one of these connections either<00:09:12.660> Thunderbolt<00:09:13.320> 403<00:09:13.800> or<00:09:13.980> USB<00:09:14.580> 3.2 00:09:21.050 --> 00:09:21.060 align:start position:0% 00:09:21.060 --> 00:09:22.490 align:start position:0% okay<00:09:21.480> now<00:09:21.660> this<00:09:21.839> is<00:09:21.959> the<00:09:22.080> interesting<00:09:22.380> part 00:09:22.490 --> 00:09:22.500 align:start position:0% okay now this is the interesting part 00:09:22.500 --> 00:09:24.889 align:start position:0% okay now this is the interesting part because<00:09:22.940> these<00:09:23.940> are<00:09:24.060> some<00:09:24.360> of<00:09:24.480> the<00:09:24.540> upgrades 00:09:24.889 --> 00:09:24.899 align:start position:0% because these are some of the upgrades 00:09:24.899 --> 00:09:26.810 align:start position:0% because these are some of the upgrades or<00:09:25.260> potential<00:09:25.680> upgrades<00:09:25.980> coming<00:09:26.160> to<00:09:26.339> ethereum 00:09:26.810 --> 00:09:26.820 align:start position:0% or potential upgrades coming to ethereum 00:09:26.820 --> 00:09:32.389 align:start position:0% or potential upgrades coming to ethereum in<00:09:27.240> the<00:09:27.420> near<00:09:27.600> future<00:09:27.779> here 00:09:32.389 --> 00:09:32.399 align:start position:0% 00:09:32.399 --> 00:09:34.490 align:start position:0% so<00:09:33.120> when<00:09:33.300> you<00:09:33.420> hear<00:09:33.540> proto-dang<00:09:34.140> sharding 00:09:34.490 --> 00:09:34.500 align:start position:0% so when you hear proto-dang sharding 00:09:34.500 --> 00:09:37.910 align:start position:0% so when you hear proto-dang sharding that's<00:09:34.940> eip4488<00:09:36.200> and<00:09:37.200> actually<00:09:37.380> in<00:09:37.560> the<00:09:37.740> worst 00:09:37.910 --> 00:09:37.920 align:start position:0% that's eip4488 and actually in the worst 00:09:37.920 --> 00:09:40.490 align:start position:0% that's eip4488 and actually in the worst case<00:09:38.100> scenario<00:09:38.700> this<00:09:39.000> would<00:09:39.180> add<00:09:39.480> two<00:09:40.260> and<00:09:40.440> a 00:09:40.490 --> 00:09:40.500 align:start position:0% case scenario this would add two and a 00:09:40.500 --> 00:09:43.009 align:start position:0% case scenario this would add two and a half<00:09:40.560> gigabyte<00:09:41.040> terabytes<00:09:41.880> per<00:09:42.300> year<00:09:42.540> for 00:09:43.009 --> 00:09:43.019 align:start position:0% half gigabyte terabytes per year for 00:09:43.019 --> 00:09:44.870 align:start position:0% half gigabyte terabytes per year for node<00:09:43.260> operators<00:09:43.680> which<00:09:43.980> is<00:09:44.100> just<00:09:44.399> not<00:09:44.640> really 00:09:44.870 --> 00:09:44.880 align:start position:0% node operators which is just not really 00:09:44.880 --> 00:09:48.650 align:start position:0% node operators which is just not really an<00:09:45.120> option<00:09:45.420> for<00:09:45.779> at<00:09:46.140> home<00:09:46.800> node<00:09:47.100> operators 00:09:48.650 --> 00:09:48.660 align:start position:0% an option for at home node operators 00:09:48.660 --> 00:09:51.889 align:start position:0% an option for at home node operators so<00:09:49.500> in<00:09:50.100> one<00:09:50.279> of<00:09:50.399> italics<00:09:50.760> write-ups<00:09:51.300> he<00:09:51.720> said 00:09:51.889 --> 00:09:51.899 align:start position:0% so in one of italics write-ups he said 00:09:51.899 --> 00:09:53.930 align:start position:0% so in one of italics write-ups he said that<00:09:52.080> like<00:09:52.560> uh 00:09:53.930 --> 00:09:53.940 align:start position:0% that like uh 00:09:53.940 --> 00:09:56.090 align:start position:0% that like uh when<00:09:54.540> like<00:09:54.839> if<00:09:55.019> Proto<00:09:55.380> dang<00:09:55.560> sharding<00:09:55.920> goes 00:09:56.090 --> 00:09:56.100 align:start position:0% when like if Proto dang sharding goes 00:09:56.100 --> 00:09:58.850 align:start position:0% when like if Proto dang sharding goes through<00:09:56.220> like<00:09:56.580> we<00:09:56.940> also<00:09:57.420> need<00:09:57.600> EIP 00:09:58.850 --> 00:09:58.860 align:start position:0% through like we also need EIP 00:09:58.860 --> 00:10:01.430 align:start position:0% through like we also need EIP all<00:09:59.220> the<00:09:59.339> fours<00:09:59.760> and<00:10:00.600> uh<00:10:00.779> what<00:10:01.019> that<00:10:01.140> does<00:10:01.260> is 00:10:01.430 --> 00:10:01.440 align:start position:0% all the fours and uh what that does is 00:10:01.440 --> 00:10:04.009 align:start position:0% all the fours and uh what that does is eliminate<00:10:02.160> historical<00:10:03.060> data<00:10:03.540> requirement 00:10:04.009 --> 00:10:04.019 align:start position:0% eliminate historical data requirement 00:10:04.019 --> 00:10:06.110 align:start position:0% eliminate historical data requirement from<00:10:04.620> the<00:10:04.800> nodes<00:10:04.980> which<00:10:05.220> would<00:10:05.399> save<00:10:05.580> like<00:10:05.760> 500 00:10:06.110 --> 00:10:06.120 align:start position:0% from the nodes which would save like 500 00:10:06.120 --> 00:10:08.210 align:start position:0% from the nodes which would save like 500 gigabytes<00:10:06.660> and 00:10:08.210 --> 00:10:08.220 align:start position:0% gigabytes and 00:10:08.220 --> 00:10:11.690 align:start position:0% gigabytes and um 00:10:11.690 --> 00:10:11.700 align:start position:0% 00:10:11.700 --> 00:10:13.670 align:start position:0% and<00:10:12.180> kind<00:10:12.480> of<00:10:12.540> like<00:10:12.779> cut<00:10:13.260> down<00:10:13.440> the 00:10:13.670 --> 00:10:13.680 align:start position:0% and kind of like cut down the 00:10:13.680 --> 00:10:16.070 align:start position:0% and kind of like cut down the requirement<00:10:14.100> on<00:10:14.519> nodes<00:10:14.880> having<00:10:15.360> a<00:10:15.600> store<00:10:15.779> like 00:10:16.070 --> 00:10:16.080 align:start position:0% requirement on nodes having a store like 00:10:16.080 --> 00:10:20.090 align:start position:0% requirement on nodes having a store like all<00:10:16.440> of<00:10:16.560> this<00:10:16.920> data<00:10:17.660> State<00:10:18.660> expiry<00:10:19.320> is<00:10:19.740> one 00:10:20.090 --> 00:10:20.100 align:start position:0% all of this data State expiry is one 00:10:20.100 --> 00:10:21.110 align:start position:0% all of this data State expiry is one that 00:10:21.110 --> 00:10:21.120 align:start position:0% that 00:10:21.120 --> 00:10:24.110 align:start position:0% that uh<00:10:21.779> is<00:10:21.959> is<00:10:22.260> contentious<00:10:22.800> again<00:10:23.040> what<00:10:23.820> it<00:10:23.940> does 00:10:24.110 --> 00:10:24.120 align:start position:0% uh is is contentious again what it does 00:10:24.120 --> 00:10:25.490 align:start position:0% uh is is contentious again what it does is<00:10:24.360> essentially<00:10:24.720> eliminates<00:10:25.320> the 00:10:25.490 --> 00:10:25.500 align:start position:0% is essentially eliminates the 00:10:25.500 --> 00:10:28.370 align:start position:0% is essentially eliminates the requirement<00:10:25.800> for<00:10:26.100> nodes<00:10:26.459> to<00:10:26.760> like<00:10:27.000> uh<00:10:27.899> keep<00:10:28.200> on 00:10:28.370 --> 00:10:28.380 align:start position:0% requirement for nodes to like uh keep on 00:10:28.380 --> 00:10:31.970 align:start position:0% requirement for nodes to like uh keep on to<00:10:28.560> certain<00:10:28.800> to<00:10:29.580> store<00:10:29.940> certain<00:10:30.180> transactions 00:10:31.970 --> 00:10:31.980 align:start position:0% to certain to store certain transactions 00:10:31.980 --> 00:10:33.769 align:start position:0% to certain to store certain transactions um<00:10:32.040> let's<00:10:32.700> say<00:10:32.820> like 00:10:33.769 --> 00:10:33.779 align:start position:0% um let's say like 00:10:33.779 --> 00:10:37.130 align:start position:0% um let's say like before<00:10:34.080> a<00:10:34.440> year<00:10:34.620> or<00:10:34.860> so<00:10:35.040> and<00:10:35.940> um<00:10:36.000> unless<00:10:36.959> that 00:10:37.130 --> 00:10:37.140 align:start position:0% before a year or so and um unless that 00:10:37.140 --> 00:10:38.690 align:start position:0% before a year or so and um unless that state<00:10:37.320> is<00:10:37.560> updated 00:10:38.690 --> 00:10:38.700 align:start position:0% state is updated 00:10:38.700 --> 00:10:40.910 align:start position:0% state is updated so<00:10:39.480> uh<00:10:40.019> I 00:10:40.910 --> 00:10:40.920 align:start position:0% so uh I 00:10:40.920 --> 00:10:43.009 align:start position:0% so uh I I have<00:10:41.399> a<00:10:41.519> feeling<00:10:41.700> this<00:10:42.240> probably<00:10:42.480> won't<00:10:42.779> go 00:10:43.009 --> 00:10:43.019 align:start position:0% I have a feeling this probably won't go 00:10:43.019 --> 00:10:44.269 align:start position:0% I have a feeling this probably won't go through 00:10:44.269 --> 00:10:44.279 align:start position:0% through 00:10:44.279 --> 00:10:45.889 align:start position:0% through um 00:10:45.889 --> 00:10:45.899 align:start position:0% um 00:10:45.899 --> 00:10:48.170 align:start position:0% um so<00:10:46.380> don't<00:10:46.620> count<00:10:46.800> on<00:10:46.980> that<00:10:47.180> stateless 00:10:48.170 --> 00:10:48.180 align:start position:0% so don't count on that stateless 00:10:48.180 --> 00:10:51.170 align:start position:0% so don't count on that stateless ethereum<00:10:48.660> is<00:10:49.140> is<00:10:49.380> a<00:10:49.620> really<00:10:49.680> cool<00:10:49.920> change<00:10:50.279> and 00:10:51.170 --> 00:10:51.180 align:start position:0% ethereum is is a really cool change and 00:10:51.180 --> 00:10:53.210 align:start position:0% ethereum is is a really cool change and no<00:10:51.839> storage<00:10:52.140> would<00:10:52.500> be<00:10:52.620> required<00:10:52.920> for<00:10:53.100> the 00:10:53.210 --> 00:10:53.220 align:start position:0% no storage would be required for the 00:10:53.220 --> 00:10:55.130 align:start position:0% no storage would be required for the node<00:10:53.399> so<00:10:53.640> it<00:10:53.760> pretty<00:10:54.000> much<00:10:54.120> eliminate<00:10:54.779> that 00:10:55.130 --> 00:10:55.140 align:start position:0% node so it pretty much eliminate that 00:10:55.140 --> 00:10:57.889 align:start position:0% node so it pretty much eliminate that two<00:10:55.620> terabyte<00:10:56.100> SSD<00:10:56.579> requirement 00:10:57.889 --> 00:10:57.899 align:start position:0% two terabyte SSD requirement 00:10:57.899 --> 00:11:00.110 align:start position:0% two terabyte SSD requirement um 00:11:00.110 --> 00:11:00.120 align:start position:0% 00:11:00.120 --> 00:11:02.269 align:start position:0% it<00:11:00.660> would<00:11:00.839> still<00:11:00.959> be<00:11:01.140> good<00:11:01.260> for<00:11:01.500> no<00:11:01.680> for<00:11:02.100> like 00:11:02.269 --> 00:11:02.279 align:start position:0% it would still be good for no for like 00:11:02.279 --> 00:11:04.970 align:start position:0% it would still be good for no for like some<00:11:02.519> nodes<00:11:02.820> some<00:11:03.120> users<00:11:03.480> to<00:11:03.899> have<00:11:04.560> that<00:11:04.800> block 00:11:04.970 --> 00:11:04.980 align:start position:0% some nodes some users to have that block 00:11:04.980 --> 00:11:06.470 align:start position:0% some nodes some users to have that block that<00:11:05.399> history 00:11:06.470 --> 00:11:06.480 align:start position:0% that history 00:11:06.480 --> 00:11:08.030 align:start position:0% that history but<00:11:06.899> it<00:11:06.959> wouldn't<00:11:07.140> be<00:11:07.320> a<00:11:07.440> requirement<00:11:07.740> so<00:11:07.920> you 00:11:08.030 --> 00:11:08.040 align:start position:0% but it wouldn't be a requirement so you 00:11:08.040 --> 00:11:09.829 align:start position:0% but it wouldn't be a requirement so you could<00:11:08.100> run<00:11:08.220> a<00:11:08.399> node<00:11:08.519> and<00:11:08.700> still<00:11:08.880> validate<00:11:09.300> all 00:11:09.829 --> 00:11:09.839 align:start position:0% could run a node and still validate all 00:11:09.839 --> 00:11:11.630 align:start position:0% could run a node and still validate all the<00:11:09.959> blocks<00:11:10.320> and<00:11:10.380> transactions<00:11:11.040> and<00:11:11.399> and 00:11:11.630 --> 00:11:11.640 align:start position:0% the blocks and transactions and and 00:11:11.640 --> 00:11:12.590 align:start position:0% the blocks and transactions and and really 00:11:12.590 --> 00:11:12.600 align:start position:0% really 00:11:12.600 --> 00:11:14.810 align:start position:0% really um<00:11:12.800> participate<00:11:13.800> in<00:11:13.980> all<00:11:14.160> those<00:11:14.279> benefits<00:11:14.700> I 00:11:14.810 --> 00:11:14.820 align:start position:0% um participate in all those benefits I 00:11:14.820 --> 00:11:16.490 align:start position:0% um participate in all those benefits I mentioned<00:11:15.120> earlier<00:11:15.420> without<00:11:15.959> the<00:11:16.260> storage 00:11:16.490 --> 00:11:16.500 align:start position:0% mentioned earlier without the storage 00:11:16.500 --> 00:11:18.410 align:start position:0% mentioned earlier without the storage but<00:11:16.920> again<00:11:17.339> this<00:11:17.579> requires<00:11:17.940> like<00:11:18.060> vertical 00:11:18.410 --> 00:11:18.420 align:start position:0% but again this requires like vertical 00:11:18.420 --> 00:11:20.090 align:start position:0% but again this requires like vertical trees<00:11:18.899> and<00:11:19.140> it's<00:11:19.560> a<00:11:19.740> pretty<00:11:19.860> difficult 00:11:20.090 --> 00:11:20.100 align:start position:0% trees and it's a pretty difficult 00:11:20.100 --> 00:11:23.990 align:start position:0% trees and it's a pretty difficult upgrade<00:11:20.640> so<00:11:21.120> don't<00:11:22.019> quite<00:11:22.320> count<00:11:22.500> on<00:11:22.740> that 00:11:23.990 --> 00:11:24.000 align:start position:0% upgrade so don't quite count on that 00:11:24.000 --> 00:11:26.509 align:start position:0% upgrade so don't quite count on that uh<00:11:24.540> ethereum<00:11:24.959> portal<00:11:25.260> network<00:11:25.500> is<00:11:26.040> a<00:11:26.339> really 00:11:26.509 --> 00:11:26.519 align:start position:0% uh ethereum portal network is a really 00:11:26.519 --> 00:11:28.910 align:start position:0% uh ethereum portal network is a really cool<00:11:26.899> uh<00:11:27.899> actually<00:11:28.079> like<00:11:28.380> separate<00:11:28.740> Network 00:11:28.910 --> 00:11:28.920 align:start position:0% cool uh actually like separate Network 00:11:28.920 --> 00:11:30.650 align:start position:0% cool uh actually like separate Network separate<00:11:29.640> Network<00:11:29.760> built<00:11:30.240> on<00:11:30.420> top<00:11:30.540> of 00:11:30.650 --> 00:11:30.660 align:start position:0% separate Network built on top of 00:11:30.660 --> 00:11:33.110 align:start position:0% separate Network built on top of ethereum<00:11:31.079> or<00:11:31.380> to<00:11:31.500> the<00:11:31.680> side<00:11:31.800> of<00:11:31.920> ethereum<00:11:32.339> it 00:11:33.110 --> 00:11:33.120 align:start position:0% ethereum or to the side of ethereum it 00:11:33.120 --> 00:11:35.949 align:start position:0% ethereum or to the side of ethereum it leverages<00:11:33.480> like<00:11:33.899> BitTorrent<00:11:34.880> architecture 00:11:35.949 --> 00:11:35.959 align:start position:0% leverages like BitTorrent architecture 00:11:35.959 --> 00:11:38.990 align:start position:0% leverages like BitTorrent architecture and<00:11:36.959> would<00:11:37.500> kind<00:11:37.680> of<00:11:37.800> enable<00:11:38.040> everyone<00:11:38.519> to<00:11:38.880> run 00:11:38.990 --> 00:11:39.000 align:start position:0% and would kind of enable everyone to run 00:11:39.000 --> 00:11:41.269 align:start position:0% and would kind of enable everyone to run a<00:11:39.120> light<00:11:39.240> node<00:11:39.600> actually<00:11:40.320> like<00:11:40.620> embedded<00:11:41.160> in 00:11:41.269 --> 00:11:41.279 align:start position:0% a light node actually like embedded in 00:11:41.279 --> 00:11:42.710 align:start position:0% a light node actually like embedded in their<00:11:41.459> wallet 00:11:42.710 --> 00:11:42.720 align:start position:0% their wallet 00:11:42.720 --> 00:11:44.690 align:start position:0% their wallet um<00:11:42.779> so<00:11:43.079> like<00:11:43.260> most<00:11:43.740> of<00:11:43.860> our<00:11:43.980> wallets<00:11:44.279> right<00:11:44.519> now 00:11:44.690 --> 00:11:44.700 align:start position:0% um so like most of our wallets right now 00:11:44.700 --> 00:11:48.590 align:start position:0% um so like most of our wallets right now they<00:11:45.240> talk<00:11:45.779> to<00:11:45.959> like<00:11:46.140> infuria<00:11:46.800> or<00:11:46.980> Alchemy<00:11:47.600> to 00:11:48.590 --> 00:11:48.600 align:start position:0% they talk to like infuria or Alchemy to 00:11:48.600 --> 00:11:50.690 align:start position:0% they talk to like infuria or Alchemy to get<00:11:48.779> transit<00:11:49.320> to<00:11:49.560> get<00:11:49.800> transactions<00:11:50.399> and<00:11:50.519> send 00:11:50.690 --> 00:11:50.700 align:start position:0% get transit to get transactions and send 00:11:50.700 --> 00:11:53.350 align:start position:0% get transit to get transactions and send a<00:11:50.820> transaction<00:11:51.240> uh<00:11:52.019> this<00:11:52.320> would<00:11:52.500> essentially 00:11:53.350 --> 00:11:53.360 align:start position:0% a transaction uh this would essentially 00:11:53.360 --> 00:11:56.710 align:start position:0% a transaction uh this would essentially eliminate<00:11:54.360> that<00:11:54.740> point<00:11:55.740> of<00:11:55.920> centralization 00:11:56.710 --> 00:11:56.720 align:start position:0% eliminate that point of centralization 00:11:56.720 --> 00:11:59.090 align:start position:0% eliminate that point of centralization and<00:11:57.720> your<00:11:58.140> light<00:11:58.320> node<00:11:58.560> would<00:11:58.740> actually<00:11:58.860> talk 00:11:59.090 --> 00:11:59.100 align:start position:0% and your light node would actually talk 00:11:59.100 --> 00:12:02.990 align:start position:0% and your light node would actually talk to<00:11:59.279> other<00:11:59.399> light<00:11:59.640> nodes<00:12:00.060> which<00:12:00.959> would<00:12:01.380> uh<00:12:02.459> talk 00:12:02.990 --> 00:12:03.000 align:start position:0% to other light nodes which would uh talk 00:12:03.000 --> 00:12:04.370 align:start position:0% to other light nodes which would uh talk to<00:12:03.180> full<00:12:03.360> nodes<00:12:03.660> whenever<00:12:03.959> you<00:12:04.140> send<00:12:04.260> a 00:12:04.370 --> 00:12:04.380 align:start position:0% to full nodes whenever you send a 00:12:04.380 --> 00:12:07.310 align:start position:0% to full nodes whenever you send a transaction<00:12:04.800> so<00:12:05.220> we<00:12:05.519> really<00:12:06.360> promising<00:12:06.899> but 00:12:07.310 --> 00:12:07.320 align:start position:0% transaction so we really promising but 00:12:07.320 --> 00:12:10.970 align:start position:0% transaction so we really promising but uh<00:12:08.160> quite<00:12:08.519> a<00:12:08.640> bit<00:12:08.700> of<00:12:08.820> work<00:12:09.000> there 00:12:10.970 --> 00:12:10.980 align:start position:0% uh quite a bit of work there 00:12:10.980 --> 00:12:13.550 align:start position:0% uh quite a bit of work there I<00:12:11.339> think<00:12:11.519> they<00:12:11.700> want<00:12:11.880> to<00:12:12.060> have 00:12:13.550 --> 00:12:13.560 align:start position:0% I think they want to have 00:12:13.560 --> 00:12:15.110 align:start position:0% I think they want to have just<00:12:13.920> for<00:12:14.100> a<00:12:14.220> Time<00:12:14.399> reference<00:12:14.760> I<00:12:14.940> think<00:12:15.000> they 00:12:15.110 --> 00:12:15.120 align:start position:0% just for a Time reference I think they 00:12:15.120 --> 00:12:17.569 align:start position:0% just for a Time reference I think they want<00:12:15.240> to<00:12:15.360> have<00:12:15.480> something<00:12:15.779> out<00:12:16.260> by<00:12:17.100> like<00:12:17.339> the 00:12:17.569 --> 00:12:17.579 align:start position:0% want to have something out by like the 00:12:17.579 --> 00:12:19.550 align:start position:0% want to have something out by like the end<00:12:17.760> of<00:12:17.940> next<00:12:18.180> year 00:12:19.550 --> 00:12:19.560 align:start position:0% end of next year 00:12:19.560 --> 00:12:23.569 align:start position:0% end of next year um 00:12:23.569 --> 00:12:23.579 align:start position:0% 00:12:23.579 --> 00:12:28.790 align:start position:0% all<00:12:23.880> right<00:12:24.060> the<00:12:24.600> fun<00:12:24.779> part<00:12:25.019> how<00:12:25.560> to<00:12:25.680> run<00:12:25.920> node 00:12:28.790 --> 00:12:28.800 align:start position:0% 00:12:28.800 --> 00:12:31.130 align:start position:0% okay<00:12:29.279> uh 00:12:31.130 --> 00:12:31.140 align:start position:0% okay uh 00:12:31.140 --> 00:12:33.350 align:start position:0% okay uh could<00:12:31.620> I<00:12:31.800> get<00:12:31.920> a<00:12:32.100> quick<00:12:32.279> hands<00:12:32.940> like<00:12:33.060> if<00:12:33.240> you've 00:12:33.350 --> 00:12:33.360 align:start position:0% could I get a quick hands like if you've 00:12:33.360 --> 00:12:36.009 align:start position:0% could I get a quick hands like if you've heard<00:12:33.540> of<00:12:33.660> dap<00:12:34.019> node<00:12:34.380> or 00:12:36.009 --> 00:12:36.019 align:start position:0% heard of dap node or 00:12:36.019 --> 00:12:41.569 align:start position:0% heard of dap node or ethereum<00:12:37.019> on<00:12:37.200> arm<00:12:37.380> I<00:12:37.800> guess 00:12:41.569 --> 00:12:41.579 align:start position:0% 00:12:41.579 --> 00:12:44.150 align:start position:0% maybe<00:12:42.060> a<00:12:42.300> quarter<00:12:42.540> of<00:12:42.600> the<00:12:42.660> people<00:12:42.779> in<00:12:42.959> here 00:12:44.150 --> 00:12:44.160 align:start position:0% maybe a quarter of the people in here 00:12:44.160 --> 00:12:47.090 align:start position:0% maybe a quarter of the people in here okay<00:12:44.639> so<00:12:44.940> yeah<00:12:45.120> they're<00:12:45.420> great<00:12:45.660> the<00:12:46.200> only 00:12:47.090 --> 00:12:47.100 align:start position:0% okay so yeah they're great the only 00:12:47.100 --> 00:12:49.069 align:start position:0% okay so yeah they're great the only um difficulty<00:12:47.700> with<00:12:48.000> running<00:12:48.420> a<00:12:48.779> node<00:12:48.899> with 00:12:49.069 --> 00:12:49.079 align:start position:0% um difficulty with running a node with 00:12:49.079 --> 00:12:51.110 align:start position:0% um difficulty with running a node with dab<00:12:49.320> node<00:12:49.560> is<00:12:49.740> you<00:12:50.040> pretty<00:12:50.579> much<00:12:50.700> need<00:12:50.940> a 00:12:51.110 --> 00:12:51.120 align:start position:0% dab node is you pretty much need a 00:12:51.120 --> 00:12:53.509 align:start position:0% dab node is you pretty much need a separate<00:12:51.480> computer 00:12:53.509 --> 00:12:53.519 align:start position:0% separate computer 00:12:53.519 --> 00:12:55.910 align:start position:0% separate computer um it<00:12:54.420> installs<00:12:54.779> an<00:12:54.959> entire<00:12:55.260> new<00:12:55.560> operating 00:12:55.910 --> 00:12:55.920 align:start position:0% um it installs an entire new operating 00:12:55.920 --> 00:13:00.110 align:start position:0% um it installs an entire new operating system<00:12:56.220> which<00:12:57.180> is<00:12:57.360> also<00:12:58.339> can<00:12:59.339> be<00:12:59.519> a<00:12:59.639> hurdle<00:12:59.940> for 00:13:00.110 --> 00:13:00.120 align:start position:0% system which is also can be a hurdle for 00:13:00.120 --> 00:13:02.329 align:start position:0% system which is also can be a hurdle for people<00:13:00.300> that<00:13:00.720> haven't<00:13:01.260> installed<00:13:01.680> a<00:13:01.860> new<00:13:01.980> new 00:13:02.329 --> 00:13:02.339 align:start position:0% people that haven't installed a new new 00:13:02.339 --> 00:13:04.730 align:start position:0% people that haven't installed a new new operating<00:13:02.639> system<00:13:02.940> on<00:13:03.180> a<00:13:03.360> computer 00:13:04.730 --> 00:13:04.740 align:start position:0% operating system on a computer 00:13:04.740 --> 00:13:06.050 align:start position:0% operating system on a computer um but<00:13:05.220> they're<00:13:05.339> great<00:13:05.519> they've<00:13:05.760> been<00:13:05.880> around 00:13:06.050 --> 00:13:06.060 align:start position:0% um but they're great they've been around 00:13:06.060 --> 00:13:09.769 align:start position:0% um but they're great they've been around been<00:13:06.779> around<00:13:06.959> for<00:13:07.260> a<00:13:07.380> while<00:13:07.500> and<00:13:08.940> um<00:13:09.000> I<00:13:09.720> would 00:13:09.769 --> 00:13:09.779 align:start position:0% been around for a while and um I would 00:13:09.779 --> 00:13:14.870 align:start position:0% been around for a while and um I would say<00:13:09.959> like<00:13:10.320> are<00:13:11.100> pretty<00:13:11.279> battle<00:13:11.519> tested 00:13:14.870 --> 00:13:14.880 align:start position:0% 00:13:14.880 --> 00:13:18.170 align:start position:0% option<00:13:15.600> two<00:13:15.899> is<00:13:16.200> the<00:13:16.380> command<00:13:16.680> line<00:13:16.860> which<00:13:17.579> is 00:13:18.170 --> 00:13:18.180 align:start position:0% option two is the command line which is 00:13:18.180 --> 00:13:22.790 align:start position:0% option two is the command line which is for<00:13:18.540> you<00:13:19.380> know<00:13:19.500> super<00:13:19.860> technical<00:13:20.279> users 00:13:22.790 --> 00:13:22.800 align:start position:0% for you know super technical users 00:13:22.800 --> 00:13:25.190 align:start position:0% for you know super technical users uh<00:13:23.519> and<00:13:23.639> yeah<00:13:24.060> technical<00:13:24.480> users<00:13:24.839> who<00:13:25.079> are 00:13:25.190 --> 00:13:25.200 align:start position:0% uh and yeah technical users who are 00:13:25.200 --> 00:13:27.350 align:start position:0% uh and yeah technical users who are familiar<00:13:25.380> with<00:13:25.560> the<00:13:25.680> command<00:13:25.980> line<00:13:26.160> and<00:13:27.360> um 00:13:27.350 --> 00:13:27.360 align:start position:0% familiar with the command line and um 00:13:27.360 --> 00:13:29.690 align:start position:0% familiar with the command line and um yeah<00:13:27.899> don't<00:13:28.200> mind<00:13:28.440> monitoring<00:13:29.220> their<00:13:29.459> node 00:13:29.690 --> 00:13:29.700 align:start position:0% yeah don't mind monitoring their node 00:13:29.700 --> 00:13:33.470 align:start position:0% yeah don't mind monitoring their node from<00:13:30.060> a<00:13:30.480> flurry<00:13:30.899> of<00:13:31.079> like<00:13:31.320> command<00:13:31.980> logs 00:13:33.470 --> 00:13:33.480 align:start position:0% from a flurry of like command logs 00:13:33.480 --> 00:13:35.090 align:start position:0% from a flurry of like command logs um<00:13:33.540> and<00:13:34.200> then<00:13:34.260> this<00:13:34.620> is<00:13:34.680> this<00:13:34.980> is<00:13:35.040> actually 00:13:35.090 --> 00:13:35.100 align:start position:0% um and then this is this is actually 00:13:35.100 --> 00:13:38.389 align:start position:0% um and then this is this is actually from<00:13:35.339> ethereum.org's<00:13:36.300> website 00:13:38.389 --> 00:13:38.399 align:start position:0% from ethereum.org's website 00:13:38.399 --> 00:13:39.530 align:start position:0% from ethereum.org's website um 00:13:39.530 --> 00:13:39.540 align:start position:0% um 00:13:39.540 --> 00:13:41.810 align:start position:0% um and<00:13:39.959> actually<00:13:40.139> photoshopped<00:13:40.980> nice<00:13:41.279> node<00:13:41.639> here 00:13:41.810 --> 00:13:41.820 align:start position:0% and actually photoshopped nice node here 00:13:41.820 --> 00:13:43.790 align:start position:0% and actually photoshopped nice node here not<00:13:42.540> photoshopped<00:13:43.019> but<00:13:43.139> like<00:13:43.320> edited<00:13:43.620> the 00:13:43.790 --> 00:13:43.800 align:start position:0% not photoshopped but like edited the 00:13:43.800 --> 00:13:45.949 align:start position:0% not photoshopped but like edited the HTML<00:13:44.279> so<00:13:44.579> this<00:13:44.700> was<00:13:44.880> kind<00:13:45.120> of<00:13:45.180> like 00:13:45.949 --> 00:13:45.959 align:start position:0% HTML so this was kind of like 00:13:45.959 --> 00:13:48.530 align:start position:0% HTML so this was kind of like uh<00:13:46.560> the<00:13:46.680> vision<00:13:46.860> for<00:13:47.100> a<00:13:47.220> nice<00:13:47.339> node 00:13:48.530 --> 00:13:48.540 align:start position:0% uh the vision for a nice node 00:13:48.540 --> 00:13:49.190 align:start position:0% uh the vision for a nice node um 00:13:49.190 --> 00:13:49.200 align:start position:0% um 00:13:49.200 --> 00:13:51.230 align:start position:0% um was<00:13:49.920> like<00:13:50.160> hey<00:13:50.339> we<00:13:50.519> I<00:13:50.639> think<00:13:50.760> we<00:13:50.880> need<00:13:51.000> a<00:13:51.120> third 00:13:51.230 --> 00:13:51.240 align:start position:0% was like hey we I think we need a third 00:13:51.240 --> 00:13:55.190 align:start position:0% was like hey we I think we need a third option<00:13:51.600> one<00:13:52.079> that<00:13:52.760> is<00:13:53.760> uh<00:13:54.360> for<00:13:54.600> like<00:13:54.899> the 00:13:55.190 --> 00:13:55.200 align:start position:0% option one that is uh for like the 00:13:55.200 --> 00:13:56.930 align:start position:0% option one that is uh for like the non-technical<00:13:55.740> user<00:13:56.220> there's<00:13:56.579> tons<00:13:56.820> of 00:13:56.930 --> 00:13:56.940 align:start position:0% non-technical user there's tons of 00:13:56.940 --> 00:13:58.310 align:start position:0% non-technical user there's tons of people<00:13:57.120> bashing<00:13:57.600> it<00:13:57.720> in<00:13:57.899> the<00:13:58.019> ethereum 00:13:58.310 --> 00:13:58.320 align:start position:0% people bashing it in the ethereum 00:13:58.320 --> 00:14:00.650 align:start position:0% people bashing it in the ethereum community<00:13:58.579> uh<00:13:59.579> who<00:13:59.760> want<00:13:59.880> to<00:14:00.000> run<00:14:00.060> a<00:14:00.240> full<00:14:00.360> node 00:14:00.650 --> 00:14:00.660 align:start position:0% community uh who want to run a full node 00:14:00.660 --> 00:14:02.569 align:start position:0% community uh who want to run a full node but<00:14:01.019> don't<00:14:01.500> want<00:14:01.680> to<00:14:01.800> hit<00:14:01.920> the<00:14:02.040> command<00:14:02.279> line 00:14:02.569 --> 00:14:02.579 align:start position:0% but don't want to hit the command line 00:14:02.579 --> 00:14:05.949 align:start position:0% but don't want to hit the command line don't<00:14:03.360> want<00:14:03.540> to<00:14:03.720> buy<00:14:04.019> another<00:14:04.139> computer 00:14:05.949 --> 00:14:05.959 align:start position:0% don't want to buy another computer 00:14:05.959 --> 00:14:08.389 align:start position:0% don't want to buy another computer technically<00:14:06.959> it's<00:14:07.680> possible<00:14:08.040> to<00:14:08.279> just 00:14:08.389 --> 00:14:08.399 align:start position:0% technically it's possible to just 00:14:08.399 --> 00:14:10.490 align:start position:0% technically it's possible to just download<00:14:08.639> an<00:14:08.940> app<00:14:09.120> on<00:14:09.300> your<00:14:09.480> laptop 00:14:10.490 --> 00:14:10.500 align:start position:0% download an app on your laptop 00:14:10.500 --> 00:14:12.230 align:start position:0% download an app on your laptop and<00:14:10.800> run<00:14:10.980> a<00:14:11.160> full<00:14:11.220> node<00:14:11.459> so<00:14:11.639> why<00:14:11.820> don't<00:14:11.940> we<00:14:12.060> have 00:14:12.230 --> 00:14:12.240 align:start position:0% and run a full node so why don't we have 00:14:12.240 --> 00:14:13.310 align:start position:0% and run a full node so why don't we have it 00:14:13.310 --> 00:14:13.320 align:start position:0% it 00:14:13.320 --> 00:14:17.629 align:start position:0% it uh<00:14:14.220> so<00:14:15.060> I'm<00:14:15.240> hoping<00:14:15.540> someday<00:14:15.899> uh<00:14:16.620> when<00:14:17.459> this 00:14:17.629 --> 00:14:17.639 align:start position:0% uh so I'm hoping someday uh when this 00:14:17.639 --> 00:14:19.970 align:start position:0% uh so I'm hoping someday uh when this gets<00:14:17.880> to<00:14:17.940> a<00:14:18.300> more<00:14:18.899> stable<00:14:19.139> version<00:14:19.440> that 00:14:19.970 --> 00:14:19.980 align:start position:0% gets to a more stable version that 00:14:19.980 --> 00:14:21.889 align:start position:0% gets to a more stable version that they'll<00:14:20.279> include<00:14:20.579> me<00:14:20.700> on<00:14:20.880> on<00:14:21.060> ethereum.org 00:14:21.889 --> 00:14:21.899 align:start position:0% they'll include me on on ethereum.org 00:14:21.899 --> 00:14:25.370 align:start position:0% they'll include me on on ethereum.org but<00:14:22.079> uh<00:14:22.620> we<00:14:22.980> gotta<00:14:23.220> approve<00:14:23.519> it<00:14:23.579> until<00:14:23.700> then<00:14:24.060> so 00:14:25.370 --> 00:14:25.380 align:start position:0% but uh we gotta approve it until then so 00:14:25.380 --> 00:14:27.290 align:start position:0% but uh we gotta approve it until then so I'm<00:14:25.860> going<00:14:26.040> to<00:14:26.100> talk<00:14:26.279> about<00:14:26.399> a<00:14:26.639> nice<00:14:27.000> node 00:14:27.290 --> 00:14:27.300 align:start position:0% I'm going to talk about a nice node 00:14:27.300 --> 00:14:30.710 align:start position:0% I'm going to talk about a nice node which<00:14:27.660> I<00:14:28.620> am<00:14:28.740> working<00:14:28.980> on<00:14:29.220> and<00:14:29.940> so<00:14:30.360> this<00:14:30.600> is 00:14:30.710 --> 00:14:30.720 align:start position:0% which I am working on and so this is 00:14:30.720 --> 00:14:32.690 align:start position:0% which I am working on and so this is what<00:14:31.139> the<00:14:31.200> current<00:14:31.320> version<00:14:31.560> looks<00:14:31.980> like 00:14:32.690 --> 00:14:32.700 align:start position:0% what the current version looks like 00:14:32.700 --> 00:14:35.930 align:start position:0% what the current version looks like this<00:14:33.240> is<00:14:33.420> our<00:14:33.779> Alpha<00:14:34.139> release<00:14:34.320> version<00:14:34.740> zero 00:14:35.930 --> 00:14:35.940 align:start position:0% this is our Alpha release version zero 00:14:35.940 --> 00:14:38.569 align:start position:0% this is our Alpha release version zero and<00:14:36.540> you<00:14:36.660> can<00:14:36.839> see<00:14:36.899> this<00:14:37.260> is<00:14:37.380> just<00:14:37.680> like<00:14:38.100> an<00:14:38.459> app 00:14:38.569 --> 00:14:38.579 align:start position:0% and you can see this is just like an app 00:14:38.579 --> 00:14:42.050 align:start position:0% and you can see this is just like an app running<00:14:38.880> on<00:14:39.540> I<00:14:40.019> think<00:14:40.139> this<00:14:40.260> is<00:14:40.380> Windows 00:14:42.050 --> 00:14:42.060 align:start position:0% running on I think this is Windows 00:14:42.060 --> 00:14:44.870 align:start position:0% running on I think this is Windows um<00:14:42.120> and<00:14:42.660> you've<00:14:42.899> got<00:14:43.079> both<00:14:43.500> your<00:14:43.880> execution 00:14:44.870 --> 00:14:44.880 align:start position:0% um and you've got both your execution 00:14:44.880 --> 00:14:46.990 align:start position:0% um and you've got both your execution consensus<00:14:45.540> clients<00:14:46.019> here 00:14:46.990 --> 00:14:47.000 align:start position:0% consensus clients here 00:14:47.000 --> 00:14:53.350 align:start position:0% consensus clients here super<00:14:48.000> simple<00:14:48.300> stop<00:14:48.839> start<00:14:49.380> remove 00:14:53.350 --> 00:14:53.360 align:start position:0% 00:14:53.360 --> 00:14:55.610 align:start position:0% you<00:14:54.360> can<00:14:54.420> kind<00:14:54.720> of<00:14:54.839> see<00:14:54.959> like<00:14:55.139> what<00:14:55.380> is<00:14:55.500> it 00:14:55.610 --> 00:14:55.620 align:start position:0% you can kind of see like what is it 00:14:55.620 --> 00:14:57.650 align:start position:0% you can kind of see like what is it doing<00:14:55.740> here<00:14:55.920> at<00:14:56.040> the<00:14:56.160> top<00:14:56.279> like<00:14:56.699> okay<00:14:57.360> awesome 00:14:57.650 --> 00:14:57.660 align:start position:0% doing here at the top like okay awesome 00:14:57.660 --> 00:14:59.810 align:start position:0% doing here at the top like okay awesome I<00:14:57.959> know<00:14:58.079> how<00:14:58.260> much<00:14:58.380> storage<00:14:58.620> it's<00:14:58.860> taking<00:14:59.160> up<00:14:59.399> I 00:14:59.810 --> 00:14:59.820 align:start position:0% I know how much storage it's taking up I 00:14:59.820 --> 00:15:01.250 align:start position:0% I know how much storage it's taking up I can<00:14:59.940> see<00:15:00.060> like<00:15:00.300> what's<00:15:00.540> the<00:15:00.779> latest<00:15:00.899> Block 00:15:01.250 --> 00:15:01.260 align:start position:0% can see like what's the latest Block 00:15:01.260 --> 00:15:04.670 align:start position:0% can see like what's the latest Block it's<00:15:01.680> at<00:15:01.860> at<00:15:02.160> it's<00:15:02.579> at<00:15:02.820> uh<00:15:03.420> how<00:15:03.600> many<00:15:03.660> peers<00:15:04.380> is 00:15:04.670 --> 00:15:04.680 align:start position:0% it's at at it's at uh how many peers is 00:15:04.680 --> 00:15:06.470 align:start position:0% it's at at it's at uh how many peers is my<00:15:04.920> node<00:15:05.339> connected<00:15:05.760> to 00:15:06.470 --> 00:15:06.480 align:start position:0% my node connected to 00:15:06.480 --> 00:15:10.670 align:start position:0% my node connected to and<00:15:07.079> then<00:15:07.260> kind<00:15:08.220> of<00:15:08.339> in<00:15:09.180> line<00:15:09.360> with<00:15:09.660> this<00:15:10.260> idea 00:15:10.670 --> 00:15:10.680 align:start position:0% and then kind of in line with this idea 00:15:10.680 --> 00:15:12.230 align:start position:0% and then kind of in line with this idea that<00:15:10.860> like<00:15:11.040> I<00:15:11.279> want<00:15:11.399> everyone<00:15:11.699> to<00:15:12.000> be<00:15:12.060> able<00:15:12.180> to 00:15:12.230 --> 00:15:12.240 align:start position:0% that like I want everyone to be able to 00:15:12.240 --> 00:15:13.850 align:start position:0% that like I want everyone to be able to run<00:15:12.360> a<00:15:12.480> node<00:15:12.660> I<00:15:12.839> also<00:15:13.079> want<00:15:13.260> everyone<00:15:13.440> to<00:15:13.740> be 00:15:13.850 --> 00:15:13.860 align:start position:0% run a node I also want everyone to be 00:15:13.860 --> 00:15:15.110 align:start position:0% run a node I also want everyone to be able<00:15:13.980> to<00:15:14.100> like 00:15:15.110 --> 00:15:15.120 align:start position:0% able to like 00:15:15.120 --> 00:15:16.730 align:start position:0% able to like you<00:15:15.600> know<00:15:15.660> no<00:15:15.959> matter<00:15:16.079> what<00:15:16.320> language<00:15:16.500> you 00:15:16.730 --> 00:15:16.740 align:start position:0% you know no matter what language you 00:15:16.740 --> 00:15:19.250 align:start position:0% you know no matter what language you speak<00:15:16.980> uh<00:15:17.940> we'll<00:15:18.240> have<00:15:18.420> a<00:15:18.540> translation<00:15:18.959> for 00:15:19.250 --> 00:15:19.260 align:start position:0% speak uh we'll have a translation for 00:15:19.260 --> 00:15:20.810 align:start position:0% speak uh we'll have a translation for that<00:15:19.380> language 00:15:20.810 --> 00:15:20.820 align:start position:0% that language 00:15:20.820 --> 00:15:23.150 align:start position:0% that language um<00:15:20.940> and<00:15:21.180> all<00:15:21.360> of<00:15:21.480> these<00:15:21.600> languages<00:15:21.959> uh<00:15:22.920> were 00:15:23.150 --> 00:15:23.160 align:start position:0% um and all of these languages uh were 00:15:23.160 --> 00:15:26.750 align:start position:0% um and all of these languages uh were translated<00:15:23.579> by<00:15:24.180> contributors<00:15:25.079> just<00:15:25.680> people 00:15:26.750 --> 00:15:26.760 align:start position:0% translated by contributors just people 00:15:26.760 --> 00:15:28.370 align:start position:0% translated by contributors just people with<00:15:27.180> a<00:15:27.240> good<00:15:27.360> heart<00:15:27.540> who<00:15:27.779> came<00:15:27.899> out<00:15:28.019> and<00:15:28.199> said 00:15:28.370 --> 00:15:28.380 align:start position:0% with a good heart who came out and said 00:15:28.380 --> 00:15:31.069 align:start position:0% with a good heart who came out and said yeah<00:15:28.800> I'll<00:15:29.100> be<00:15:29.459> glad<00:15:29.699> to<00:15:29.880> translate<00:15:30.120> like 00:15:31.069 --> 00:15:31.079 align:start position:0% yeah I'll be glad to translate like 00:15:31.079 --> 00:15:33.170 align:start position:0% yeah I'll be glad to translate like whatever<00:15:31.500> we<00:15:31.860> can<00:15:32.040> and<00:15:32.459> into<00:15:32.880> another 00:15:33.170 --> 00:15:33.180 align:start position:0% whatever we can and into another 00:15:33.180 --> 00:15:35.210 align:start position:0% whatever we can and into another language<00:15:33.480> so 00:15:35.210 --> 00:15:35.220 align:start position:0% language so 00:15:35.220 --> 00:15:36.769 align:start position:0% language so a<00:15:35.760> nice<00:15:36.000> note 00:15:36.769 --> 00:15:36.779 align:start position:0% a nice note 00:15:36.779 --> 00:15:38.689 align:start position:0% a nice note essentially<00:15:37.380> Sports<00:15:37.620> translations<00:15:38.220> we<00:15:38.579> just 00:15:38.689 --> 00:15:38.699 align:start position:0% essentially Sports translations we just 00:15:38.699 --> 00:15:40.189 align:start position:0% essentially Sports translations we just need<00:15:38.880> people<00:15:39.120> who<00:15:39.420> speak<00:15:39.720> all<00:15:39.899> of<00:15:40.019> the<00:15:40.079> other 00:15:40.189 --> 00:15:40.199 align:start position:0% need people who speak all of the other 00:15:40.199 --> 00:15:46.550 align:start position:0% need people who speak all of the other languages<00:15:40.560> to<00:15:40.800> help<00:15:40.920> out 00:15:46.550 --> 00:15:46.560 align:start position:0% 00:15:46.560 --> 00:15:48.470 align:start position:0% okay<00:15:46.800> hopefully<00:15:47.100> this<00:15:47.279> loads<00:15:47.639> so<00:15:48.000> this<00:15:48.180> is<00:15:48.300> a 00:15:48.470 --> 00:15:48.480 align:start position:0% okay hopefully this loads so this is a 00:15:48.480 --> 00:15:50.689 align:start position:0% okay hopefully this loads so this is a design<00:15:48.660> for<00:15:49.019> our<00:15:49.139> next<00:15:49.320> version<00:15:49.620> much<00:15:50.519> like 00:15:50.689 --> 00:15:50.699 align:start position:0% design for our next version much like 00:15:50.699 --> 00:15:54.230 align:start position:0% design for our next version much like cleaner<00:15:51.180> UI 00:15:54.230 --> 00:15:54.240 align:start position:0% 00:15:54.240 --> 00:15:56.210 align:start position:0% at<00:15:54.720> first<00:15:54.839> only<00:15:55.079> the<00:15:55.260> ethereum<00:15:55.620> node<00:15:55.860> will<00:15:56.100> be 00:15:56.210 --> 00:15:56.220 align:start position:0% at first only the ethereum node will be 00:15:56.220 --> 00:15:57.530 align:start position:0% at first only the ethereum node will be available<00:15:56.399> but<00:15:56.760> I'm<00:15:56.880> designing<00:15:57.240> it<00:15:57.360> to<00:15:57.480> be 00:15:57.530 --> 00:15:57.540 align:start position:0% available but I'm designing it to be 00:15:57.540 --> 00:16:00.110 align:start position:0% available but I'm designing it to be General<00:15:57.779> so<00:15:58.260> that<00:15:58.500> you<00:15:59.160> can<00:15:59.220> run<00:15:59.399> other<00:15:59.760> nodes 00:16:00.110 --> 00:16:00.120 align:start position:0% General so that you can run other nodes 00:16:00.120 --> 00:16:03.350 align:start position:0% General so that you can run other nodes I'll<00:16:00.720> talk<00:16:01.139> more<00:16:01.320> on<00:16:01.500> that<00:16:02.120> so<00:16:03.120> you<00:16:03.240> pick 00:16:03.350 --> 00:16:03.360 align:start position:0% I'll talk more on that so you pick 00:16:03.360 --> 00:16:05.629 align:start position:0% I'll talk more on that so you pick ethereum<00:16:03.779> node<00:16:04.019> then<00:16:04.199> you<00:16:04.380> pick<00:16:04.620> which<00:16:05.399> client 00:16:05.629 --> 00:16:05.639 align:start position:0% ethereum node then you pick which client 00:16:05.639 --> 00:16:08.090 align:start position:0% ethereum node then you pick which client you<00:16:05.820> want<00:16:06.000> to<00:16:06.120> run<00:16:06.240> we<00:16:07.079> conveniently<00:16:07.740> show<00:16:07.980> you 00:16:08.090 --> 00:16:08.100 align:start position:0% you want to run we conveniently show you 00:16:08.100 --> 00:16:11.210 align:start position:0% you want to run we conveniently show you which<00:16:08.459> clients<00:16:08.820> are<00:16:08.940> minority<00:16:09.360> clients<00:16:10.220> you 00:16:11.210 --> 00:16:11.220 align:start position:0% which clients are minority clients you 00:16:11.220 --> 00:16:13.550 align:start position:0% which clients are minority clients you can<00:16:11.459> select<00:16:12.420> a<00:16:12.540> few<00:16:12.660> options<00:16:12.959> select<00:16:13.380> where 00:16:13.550 --> 00:16:13.560 align:start position:0% can select a few options select where 00:16:13.560 --> 00:16:15.710 align:start position:0% can select a few options select where you<00:16:13.680> want<00:16:13.800> to<00:16:13.920> store<00:16:14.160> the<00:16:14.459> data<00:16:14.760> at 00:16:15.710 --> 00:16:15.720 align:start position:0% you want to store the data at 00:16:15.720 --> 00:16:17.210 align:start position:0% you want to store the data at again<00:16:16.139> these<00:16:16.440> are<00:16:16.500> all<00:16:16.620> things<00:16:16.800> you'd<00:16:17.040> have<00:16:17.160> to 00:16:17.210 --> 00:16:17.220 align:start position:0% again these are all things you'd have to 00:16:17.220 --> 00:16:20.509 align:start position:0% again these are all things you'd have to do<00:16:17.339> from<00:16:17.579> the<00:16:17.760> command<00:16:18.000> line 00:16:20.509 --> 00:16:20.519 align:start position:0% 00:16:20.519 --> 00:16:23.449 align:start position:0% and<00:16:21.060> then<00:16:21.240> this<00:16:21.600> will<00:16:22.500> actually<00:16:22.680> take<00:16:23.040> the 00:16:23.449 --> 00:16:23.459 align:start position:0% and then this will actually take the 00:16:23.459 --> 00:16:25.310 align:start position:0% and then this will actually take the screen<00:16:24.060> um<00:16:24.060> I<00:16:24.240> think<00:16:24.600> I'll<00:16:24.720> show<00:16:24.899> it<00:16:25.019> to<00:16:25.139> you 00:16:25.310 --> 00:16:25.320 align:start position:0% screen um I think I'll show it to you 00:16:25.320 --> 00:16:26.329 align:start position:0% screen um I think I'll show it to you later 00:16:26.329 --> 00:16:26.339 align:start position:0% later 00:16:26.339 --> 00:16:31.750 align:start position:0% later um 00:16:31.750 --> 00:16:31.760 align:start position:0% 00:16:31.760 --> 00:16:34.310 align:start position:0% and<00:16:32.760> then<00:16:33.000> we<00:16:33.600> have<00:16:33.779> to<00:16:33.839> install<00:16:33.959> some 00:16:34.310 --> 00:16:34.320 align:start position:0% and then we have to install some 00:16:34.320 --> 00:16:37.670 align:start position:0% and then we have to install some dependencies<00:16:35.160> here<00:16:35.399> and 00:16:37.670 --> 00:16:37.680 align:start position:0% dependencies here and 00:16:37.680 --> 00:16:41.389 align:start position:0% dependencies here and we<00:16:38.279> just<00:16:38.519> hit<00:16:38.699> start<00:16:39.139> and<00:16:40.139> uh 00:16:41.389 --> 00:16:41.399 align:start position:0% we just hit start and uh 00:16:41.399 --> 00:16:44.090 align:start position:0% we just hit start and uh our<00:16:41.759> node<00:16:42.000> is<00:16:42.120> syncing<00:16:42.540> and<00:16:42.779> running<00:16:42.959> and<00:16:43.620> we 00:16:44.090 --> 00:16:44.100 align:start position:0% our node is syncing and running and we 00:16:44.100 --> 00:16:45.710 align:start position:0% our node is syncing and running and we have<00:16:44.220> this<00:16:44.399> beautiful<00:16:44.579> UI<00:16:45.000> to<00:16:45.240> see<00:16:45.360> our<00:16:45.480> node 00:16:45.710 --> 00:16:45.720 align:start position:0% have this beautiful UI to see our node 00:16:45.720 --> 00:16:50.030 align:start position:0% have this beautiful UI to see our node in<00:16:46.019> everything<00:16:46.980> is<00:16:47.339> great 00:16:50.030 --> 00:16:50.040 align:start position:0% 00:16:50.040 --> 00:16:53.449 align:start position:0% okay<00:16:50.579> so<00:16:51.180> this<00:16:51.300> was<00:16:51.540> this<00:16:51.899> is<00:16:51.959> kind<00:16:52.139> of<00:16:52.259> a<00:16:52.440> key 00:16:53.449 --> 00:16:53.459 align:start position:0% okay so this was this is kind of a key 00:16:53.459 --> 00:16:54.769 align:start position:0% okay so this was this is kind of a key um piece<00:16:53.940> of<00:16:54.000> information<00:16:54.180> for<00:16:54.540> a<00:16:54.660> lot<00:16:54.720> of 00:16:54.769 --> 00:16:54.779 align:start position:0% um piece of information for a lot of 00:16:54.779 --> 00:16:56.749 align:start position:0% um piece of information for a lot of people<00:16:54.899> is<00:16:55.079> like<00:16:55.320> can<00:16:55.980> my<00:16:56.160> computer<00:16:56.279> run<00:16:56.579> this 00:16:56.749 --> 00:16:56.759 align:start position:0% people is like can my computer run this 00:16:56.759 --> 00:16:57.769 align:start position:0% people is like can my computer run this node 00:16:57.769 --> 00:16:57.779 align:start position:0% node 00:16:57.779 --> 00:16:59.629 align:start position:0% node um<00:16:57.899> no<00:16:58.259> you<00:16:58.560> don't<00:16:58.680> have<00:16:58.740> to<00:16:58.860> go<00:16:59.100> to<00:16:59.399> like 00:16:59.629 --> 00:16:59.639 align:start position:0% um no you don't have to go to like 00:16:59.639 --> 00:17:01.069 align:start position:0% um no you don't have to go to like guides<00:17:00.000> or<00:17:00.120> websites<00:17:00.540> to<00:17:00.720> read<00:17:00.899> through 00:17:01.069 --> 00:17:01.079 align:start position:0% guides or websites to read through 00:17:01.079 --> 00:17:04.909 align:start position:0% guides or websites to read through things<00:17:01.380> it's<00:17:02.100> in<00:17:02.279> the<00:17:02.459> app<00:17:02.579> uh<00:17:03.480> the<00:17:03.660> app 00:17:04.909 --> 00:17:04.919 align:start position:0% things it's in the app uh the app 00:17:04.919 --> 00:17:07.189 align:start position:0% things it's in the app uh the app yeah<00:17:05.280> we<00:17:05.579> can<00:17:05.699> see<00:17:05.880> like<00:17:06.120> hey<00:17:06.360> is<00:17:06.600> your<00:17:06.780> CPU 00:17:07.189 --> 00:17:07.199 align:start position:0% yeah we can see like hey is your CPU 00:17:07.199 --> 00:17:09.650 align:start position:0% yeah we can see like hey is your CPU fast<00:17:07.439> enough<00:17:07.620> how<00:17:07.980> much<00:17:08.100> memory<00:17:08.459> do<00:17:08.640> you<00:17:08.760> have 00:17:09.650 --> 00:17:09.660 align:start position:0% fast enough how much memory do you have 00:17:09.660 --> 00:17:11.689 align:start position:0% fast enough how much memory do you have do<00:17:09.959> you<00:17:10.140> have<00:17:10.199> an<00:17:10.319> SSD<00:17:10.740> does<00:17:11.339> it<00:17:11.459> have<00:17:11.579> enough 00:17:11.689 --> 00:17:11.699 align:start position:0% do you have an SSD does it have enough 00:17:11.699 --> 00:17:13.669 align:start position:0% do you have an SSD does it have enough space<00:17:12.000> all<00:17:12.600> that<00:17:12.839> stuff 00:17:13.669 --> 00:17:13.679 align:start position:0% space all that stuff 00:17:13.679 --> 00:17:14.449 align:start position:0% space all that stuff um 00:17:14.449 --> 00:17:14.459 align:start position:0% um 00:17:14.459 --> 00:17:21.110 align:start position:0% um we<00:17:14.939> can<00:17:15.059> do<00:17:15.179> so<00:17:15.600> we<00:17:15.900> do<00:17:16.020> it<00:17:16.140> for<00:17:16.319> you 00:17:21.110 --> 00:17:21.120 align:start position:0% 00:17:21.120 --> 00:17:25.130 align:start position:0% and<00:17:21.900> this<00:17:22.439> may<00:17:22.620> differ<00:17:22.860> by<00:17:23.459> client<00:17:23.939> and<00:17:24.839> in<00:17:25.020> the 00:17:25.130 --> 00:17:25.140 align:start position:0% and this may differ by client and in the 00:17:25.140 --> 00:17:27.409 align:start position:0% and this may differ by client and in the future<00:17:25.260> this<00:17:25.620> may<00:17:25.799> differ<00:17:26.040> by<00:17:26.880> node<00:17:27.120> type 00:17:27.409 --> 00:17:27.419 align:start position:0% future this may differ by node type 00:17:27.419 --> 00:17:29.690 align:start position:0% future this may differ by node type meaning<00:17:28.319> the<00:17:28.559> hardware<00:17:28.740> requirements<00:17:29.460> May 00:17:29.690 --> 00:17:29.700 align:start position:0% meaning the hardware requirements May 00:17:29.700 --> 00:17:32.450 align:start position:0% meaning the hardware requirements May differ<00:17:29.880> some<00:17:30.840> nodes<00:17:31.140> maybe<00:17:31.440> use<00:17:32.040> a<00:17:32.280> small 00:17:32.450 --> 00:17:32.460 align:start position:0% differ some nodes maybe use a small 00:17:32.460 --> 00:17:33.770 align:start position:0% differ some nodes maybe use a small amount<00:17:32.640> of<00:17:32.820> RAM 00:17:33.770 --> 00:17:33.780 align:start position:0% amount of RAM 00:17:33.780 --> 00:17:36.770 align:start position:0% amount of RAM others<00:17:34.500> you<00:17:34.620> might<00:17:34.740> use<00:17:34.860> more<00:17:35.100> storage<00:17:35.780> so 00:17:36.770 --> 00:17:36.780 align:start position:0% others you might use more storage so 00:17:36.780 --> 00:17:38.510 align:start position:0% others you might use more storage so we'll<00:17:37.260> give<00:17:37.500> you<00:17:37.620> that<00:17:37.740> green<00:17:37.919> check<00:17:38.100> mark<00:17:38.340> if 00:17:38.510 --> 00:17:38.520 align:start position:0% we'll give you that green check mark if 00:17:38.520 --> 00:17:44.090 align:start position:0% we'll give you that green check mark if you're<00:17:38.640> good<00:17:38.820> to<00:17:38.940> go<00:17:39.059> based<00:17:39.720> on<00:17:39.780> the<00:17:39.900> Note<00:17:40.020> type 00:17:44.090 --> 00:17:44.100 align:start position:0% 00:17:44.100 --> 00:17:46.130 align:start position:0% a<00:17:44.220> few<00:17:44.460> more<00:17:44.640> screenshots<00:17:45.059> here 00:17:46.130 --> 00:17:46.140 align:start position:0% a few more screenshots here 00:17:46.140 --> 00:17:47.570 align:start position:0% a few more screenshots here um 00:17:47.570 --> 00:17:47.580 align:start position:0% um 00:17:47.580 --> 00:17:49.130 align:start position:0% um yeah<00:17:48.000> just<00:17:48.179> wanted<00:17:48.360> to<00:17:48.539> leave<00:17:48.660> these<00:17:48.780> up<00:17:48.960> here 00:17:49.130 --> 00:17:49.140 align:start position:0% yeah just wanted to leave these up here 00:17:49.140 --> 00:17:51.830 align:start position:0% yeah just wanted to leave these up here so<00:17:49.320> you<00:17:49.620> could<00:17:49.860> see<00:17:50.039> them<00:17:50.160> without<00:17:50.400> the<00:17:50.700> video 00:17:51.830 --> 00:17:51.840 align:start position:0% so you could see them without the video 00:17:51.840 --> 00:17:54.350 align:start position:0% so you could see them without the video um this<00:17:52.559> is<00:17:52.620> this<00:17:53.100> is<00:17:53.280> really<00:17:53.520> like<00:17:53.880> important 00:17:54.350 --> 00:17:54.360 align:start position:0% um this is this is really like important 00:17:54.360 --> 00:17:56.270 align:start position:0% um this is this is really like important to<00:17:54.539> me<00:17:55.200> um<00:17:55.200> being<00:17:55.440> able<00:17:55.620> to<00:17:55.740> change<00:17:55.980> the 00:17:56.270 --> 00:17:56.280 align:start position:0% to me um being able to change the 00:17:56.280 --> 00:17:58.190 align:start position:0% to me um being able to change the settings<00:17:56.400> on<00:17:56.760> your<00:17:56.880> node<00:17:57.059> through<00:17:57.539> the<00:17:57.840> UI 00:17:58.190 --> 00:17:58.200 align:start position:0% settings on your node through the UI 00:17:58.200 --> 00:18:02.090 align:start position:0% settings on your node through the UI again<00:17:58.880> to<00:17:59.880> do<00:18:00.000> this<00:18:00.179> now<00:18:00.419> you<00:18:01.380> have<00:18:01.500> to<00:18:01.620> go<00:18:01.860> to 00:18:02.090 --> 00:18:02.100 align:start position:0% again to do this now you have to go to 00:18:02.100 --> 00:18:05.570 align:start position:0% again to do this now you have to go to the<00:18:02.280> docs<00:18:02.700> of<00:18:02.940> the<00:18:03.539> client<00:18:03.780> team<00:18:04.220> uh<00:18:05.220> try<00:18:05.460> to 00:18:05.570 --> 00:18:05.580 align:start position:0% the docs of the client team uh try to 00:18:05.580 --> 00:18:07.250 align:start position:0% the docs of the client team uh try to find<00:18:05.700> like<00:18:05.940> the<00:18:06.120> right<00:18:06.240> flag<00:18:06.480> with<00:18:06.780> like<00:18:07.020> the 00:18:07.250 --> 00:18:07.260 align:start position:0% find like the right flag with like the 00:18:07.260 --> 00:18:10.970 align:start position:0% find like the right flag with like the dash<00:18:07.440> dash<00:18:07.860> uh<00:18:08.940> whatever<00:18:09.600> and<00:18:10.320> hopefully<00:18:10.799> you 00:18:10.970 --> 00:18:10.980 align:start position:0% dash dash uh whatever and hopefully you 00:18:10.980 --> 00:18:12.289 align:start position:0% dash dash uh whatever and hopefully you format<00:18:11.340> it<00:18:11.460> rightly<00:18:11.700> I<00:18:11.880> don't<00:18:12.000> know<00:18:12.059> if<00:18:12.179> it 00:18:12.289 --> 00:18:12.299 align:start position:0% format it rightly I don't know if it 00:18:12.299 --> 00:18:14.390 align:start position:0% format it rightly I don't know if it needs<00:18:12.539> quotes<00:18:12.780> uh<00:18:13.620> it<00:18:13.740> doesn't<00:18:13.799> need<00:18:14.039> a<00:18:14.160> comma 00:18:14.390 --> 00:18:14.400 align:start position:0% needs quotes uh it doesn't need a comma 00:18:14.400 --> 00:18:15.770 align:start position:0% needs quotes uh it doesn't need a comma in<00:18:14.520> between<00:18:14.640> our<00:18:14.940> space<00:18:15.179> you<00:18:15.419> don't<00:18:15.539> have<00:18:15.660> to 00:18:15.770 --> 00:18:15.780 align:start position:0% in between our space you don't have to 00:18:15.780 --> 00:18:16.909 align:start position:0% in between our space you don't have to do<00:18:15.900> that 00:18:16.909 --> 00:18:16.919 align:start position:0% do that 00:18:16.919 --> 00:18:26.450 align:start position:0% do that with<00:18:17.220> a<00:18:17.460> nice<00:18:17.520> node<00:18:17.820> it's<00:18:18.179> here 00:18:26.450 --> 00:18:26.460 align:start position:0% 00:18:26.460 --> 00:18:29.150 align:start position:0% okay<00:18:26.880> nice<00:18:27.240> node<00:18:27.600> is<00:18:28.039> cross-platform<00:18:29.039> meaning 00:18:29.150 --> 00:18:29.160 align:start position:0% okay nice node is cross-platform meaning 00:18:29.160 --> 00:18:32.330 align:start position:0% okay nice node is cross-platform meaning it<00:18:29.400> works<00:18:29.640> with<00:18:29.760> Windows<00:18:30.240> Mac<00:18:30.480> Linux 00:18:32.330 --> 00:18:32.340 align:start position:0% it works with Windows Mac Linux 00:18:32.340 --> 00:18:40.450 align:start position:0% it works with Windows Mac Linux um<00:18:32.460> this<00:18:32.580> is<00:18:32.760> screenshot<00:18:33.059> of<00:18:33.240> windows 00:18:40.450 --> 00:18:40.460 align:start position:0% 00:18:40.460 --> 00:18:43.370 align:start position:0% looks<00:18:41.460> like<00:18:41.520> it's<00:18:41.640> not<00:18:41.820> going<00:18:41.940> to<00:18:42.059> play 00:18:43.370 --> 00:18:43.380 align:start position:0% looks like it's not going to play 00:18:43.380 --> 00:18:46.310 align:start position:0% looks like it's not going to play um so<00:18:44.100> yeah<00:18:44.760> again<00:18:44.940> I<00:18:45.240> designed<00:18:45.660> nice<00:18:45.840> node<00:18:46.140> to 00:18:46.310 --> 00:18:46.320 align:start position:0% um so yeah again I designed nice node to 00:18:46.320 --> 00:18:49.909 align:start position:0% um so yeah again I designed nice node to be<00:18:46.440> as<00:18:46.740> general<00:18:46.919> as<00:18:47.220> possible<00:18:47.520> meaning<00:18:48.260> as<00:18:49.260> l2s 00:18:49.909 --> 00:18:49.919 align:start position:0% be as general as possible meaning as l2s 00:18:49.919 --> 00:18:52.909 align:start position:0% be as general as possible meaning as l2s start<00:18:50.100> to<00:18:50.280> decentralize<00:18:50.940> and<00:18:51.360> provide<00:18:51.780> nodes 00:18:52.909 --> 00:18:52.919 align:start position:0% start to decentralize and provide nodes 00:18:52.919 --> 00:18:55.210 align:start position:0% start to decentralize and provide nodes um<00:18:52.980> maybe<00:18:53.400> sync<00:18:53.820> with<00:18:53.940> sequencers 00:18:55.210 --> 00:18:55.220 align:start position:0% um maybe sync with sequencers 00:18:55.220 --> 00:18:58.010 align:start position:0% um maybe sync with sequencers nice<00:18:56.220> node 00:18:58.010 --> 00:18:58.020 align:start position:0% nice node 00:18:58.020 --> 00:18:59.810 align:start position:0% nice node there<00:18:58.500> should<00:18:58.679> be<00:18:58.799> very<00:18:58.919> minimal<00:18:59.280> changes<00:18:59.640> to 00:18:59.810 --> 00:18:59.820 align:start position:0% there should be very minimal changes to 00:18:59.820 --> 00:19:02.750 align:start position:0% there should be very minimal changes to support<00:19:00.000> those<00:19:00.299> new<00:19:00.419> node<00:19:00.660> types 00:19:02.750 --> 00:19:02.760 align:start position:0% support those new node types 00:19:02.760 --> 00:19:05.210 align:start position:0% support those new node types and<00:19:03.539> uh<00:19:03.900> and<00:19:04.260> actually<00:19:04.380> like<00:19:04.620> users<00:19:05.039> could 00:19:05.210 --> 00:19:05.220 align:start position:0% and uh and actually like users could 00:19:05.220 --> 00:19:07.070 align:start position:0% and uh and actually like users could open<00:19:05.400> a<00:19:05.580> pull<00:19:05.700> request<00:19:06.059> to<00:19:06.240> nice<00:19:06.419> nodes<00:19:06.720> GitHub 00:19:07.070 --> 00:19:07.080 align:start position:0% open a pull request to nice nodes GitHub 00:19:07.080 --> 00:19:09.650 align:start position:0% open a pull request to nice nodes GitHub and<00:19:07.440> and<00:19:07.740> those<00:19:07.980> new<00:19:08.160> nodes<00:19:08.460> would<00:19:08.700> be<00:19:08.880> in<00:19:09.419> in 00:19:09.650 --> 00:19:09.660 align:start position:0% and and those new nodes would be in in 00:19:09.660 --> 00:19:12.650 align:start position:0% and and those new nodes would be in in nice<00:19:09.840> node<00:19:10.140> in<00:19:10.260> the<00:19:10.380> next<00:19:10.500> release 00:19:12.650 --> 00:19:12.660 align:start position:0% nice node in the next release 00:19:12.660 --> 00:19:15.049 align:start position:0% nice node in the next release um<00:19:12.780> so<00:19:13.200> for<00:19:13.860> the<00:19:13.980> technical<00:19:14.220> folks<00:19:14.580> nice<00:19:14.760> note 00:19:15.049 --> 00:19:15.059 align:start position:0% um so for the technical folks nice note 00:19:15.059 --> 00:19:17.330 align:start position:0% um so for the technical folks nice note is<00:19:15.299> sort<00:19:15.480> of<00:19:15.600> a<00:19:15.780> UI<00:19:16.559> wrapper<00:19:16.919> around<00:19:17.100> like 00:19:17.330 --> 00:19:17.340 align:start position:0% is sort of a UI wrapper around like 00:19:17.340 --> 00:19:18.830 align:start position:0% is sort of a UI wrapper around like Docker<00:19:17.820> containers 00:19:18.830 --> 00:19:18.840 align:start position:0% Docker containers 00:19:18.840 --> 00:19:20.690 align:start position:0% Docker containers um<00:19:18.960> so<00:19:19.320> any<00:19:19.500> any<00:19:19.740> node<00:19:20.100> type<00:19:20.280> that<00:19:20.460> has<00:19:20.580> a 00:19:20.690 --> 00:19:20.700 align:start position:0% um so any any node type that has a 00:19:20.700 --> 00:19:22.130 align:start position:0% um so any any node type that has a Docker<00:19:21.000> image<00:19:21.240> will<00:19:21.419> be<00:19:21.600> like<00:19:21.780> really<00:19:21.960> quick 00:19:22.130 --> 00:19:22.140 align:start position:0% Docker image will be like really quick 00:19:22.140 --> 00:19:25.669 align:start position:0% Docker image will be like really quick really<00:19:22.500> easy<00:19:22.740> to<00:19:23.039> add<00:19:23.220> to<00:19:23.400> nice<00:19:23.640> note 00:19:25.669 --> 00:19:25.679 align:start position:0% really easy to add to nice note 00:19:25.679 --> 00:19:28.250 align:start position:0% really easy to add to nice note um<00:19:25.799> and<00:19:26.580> uh<00:19:26.940> yeah<00:19:27.120> eventually<00:19:27.480> we<00:19:27.720> want<00:19:27.960> to<00:19:28.140> add 00:19:28.250 --> 00:19:28.260 align:start position:0% um and uh yeah eventually we want to add 00:19:28.260 --> 00:19:30.710 align:start position:0% um and uh yeah eventually we want to add things<00:19:28.860> like<00:19:29.039> staking<00:19:29.400> as<00:19:29.640> well 00:19:30.710 --> 00:19:30.720 align:start position:0% things like staking as well 00:19:30.720 --> 00:19:33.110 align:start position:0% things like staking as well um<00:19:31.140> so<00:19:31.679> this<00:19:31.860> is<00:19:31.980> a<00:19:32.160> UI<00:19:32.460> screenshot<00:19:32.820> of<00:19:32.940> like 00:19:33.110 --> 00:19:33.120 align:start position:0% um so this is a UI screenshot of like 00:19:33.120 --> 00:19:34.370 align:start position:0% um so this is a UI screenshot of like what<00:19:33.240> it<00:19:33.360> would<00:19:33.480> look<00:19:33.600> like<00:19:33.720> if<00:19:33.960> you<00:19:34.080> were<00:19:34.260> to 00:19:34.370 --> 00:19:34.380 align:start position:0% what it would look like if you were to 00:19:34.380 --> 00:19:38.029 align:start position:0% what it would look like if you were to add<00:19:34.799> validators 00:19:38.029 --> 00:19:38.039 align:start position:0% 00:19:38.039 --> 00:19:41.210 align:start position:0% and<00:19:38.580> then<00:19:38.640> you<00:19:38.880> can<00:19:39.000> just<00:19:39.179> kind<00:19:39.299> of<00:19:39.419> see<00:19:39.539> like 00:19:41.210 --> 00:19:41.220 align:start position:0% and then you can just kind of see like 00:19:41.220 --> 00:19:44.150 align:start position:0% and then you can just kind of see like yeah<00:19:41.760> uh<00:19:42.539> arbitrome<00:19:43.260> does<00:19:43.440> have<00:19:43.559> a<00:19:43.679> have<00:19:43.919> a<00:19:44.039> no 00:19:44.150 --> 00:19:44.160 align:start position:0% yeah uh arbitrome does have a have a no 00:19:44.160 --> 00:19:48.049 align:start position:0% yeah uh arbitrome does have a have a no doubt<00:19:44.580> I<00:19:45.480> don't<00:19:45.660> know<00:19:46.260> if<00:19:46.919> um 00:19:48.049 --> 00:19:48.059 align:start position:0% doubt I don't know if um 00:19:48.059 --> 00:19:50.210 align:start position:0% doubt I don't know if um I<00:19:48.419> don't<00:19:48.539> know<00:19:48.660> how<00:19:48.900> involved<00:19:49.260> it<00:19:49.380> is<00:19:49.559> in<00:19:49.980> their 00:19:50.210 --> 00:19:50.220 align:start position:0% I don't know how involved it is in their 00:19:50.220 --> 00:19:51.830 align:start position:0% I don't know how involved it is in their their<00:19:50.460> Layer<00:19:50.820> Two<00:19:51.000> yet<00:19:51.179> I<00:19:51.419> think<00:19:51.539> it<00:19:51.720> might 00:19:51.830 --> 00:19:51.840 align:start position:0% their Layer Two yet I think it might 00:19:51.840 --> 00:19:54.350 align:start position:0% their Layer Two yet I think it might kind<00:19:52.020> of<00:19:52.080> just<00:19:52.260> be<00:19:52.440> like<00:19:52.740> a<00:19:53.039> replica<00:19:53.400> node<00:19:53.880> and 00:19:54.350 --> 00:19:54.360 align:start position:0% kind of just be like a replica node and 00:19:54.360 --> 00:19:58.310 align:start position:0% kind of just be like a replica node and not<00:19:54.600> quite<00:19:54.780> uh<00:19:55.679> the<00:19:55.919> same<00:19:56.039> priority<00:19:56.520> as<00:19:56.880> as 00:19:58.310 --> 00:19:58.320 align:start position:0% not quite uh the same priority as as 00:19:58.320 --> 00:19:59.210 align:start position:0% not quite uh the same priority as as um 00:19:59.210 --> 00:19:59.220 align:start position:0% um 00:19:59.220 --> 00:20:02.270 align:start position:0% um they're<00:19:59.760> kind<00:20:00.000> of<00:20:00.059> like<00:20:00.179> their<00:20:01.080> own 00:20:02.270 --> 00:20:02.280 align:start position:0% they're kind of like their own 00:20:02.280 --> 00:20:03.890 align:start position:0% they're kind of like their own and<00:20:02.940> then 00:20:03.890 --> 00:20:03.900 align:start position:0% and then 00:20:03.900 --> 00:20:06.529 align:start position:0% and then The<00:20:04.559> Ant<00:20:04.679> and<00:20:04.980> Beyond<00:20:05.280> here<00:20:05.520> is 00:20:06.529 --> 00:20:06.539 align:start position:0% The Ant and Beyond here is 00:20:06.539 --> 00:20:08.810 align:start position:0% The Ant and Beyond here is okay<00:20:07.020> if<00:20:07.260> our<00:20:07.380> if<00:20:07.559> our<00:20:07.740> like<00:20:07.919> web<00:20:08.100> three<00:20:08.400> dreams 00:20:08.810 --> 00:20:08.820 align:start position:0% okay if our if our like web three dreams 00:20:08.820 --> 00:20:11.570 align:start position:0% okay if our if our like web three dreams take<00:20:09.059> off<00:20:09.240> and<00:20:09.660> web<00:20:10.140> 3<00:20:10.440> infrastructure<00:20:11.100> is 00:20:11.570 --> 00:20:11.580 align:start position:0% take off and web 3 infrastructure is 00:20:11.580 --> 00:20:13.850 align:start position:0% take off and web 3 infrastructure is really<00:20:11.880> where<00:20:12.299> we<00:20:12.419> go<00:20:12.600> to<00:20:12.720> and<00:20:13.260> the<00:20:13.559> users 00:20:13.850 --> 00:20:13.860 align:start position:0% really where we go to and the users 00:20:13.860 --> 00:20:15.830 align:start position:0% really where we go to and the users control<00:20:14.280> we<00:20:14.700> control<00:20:14.940> the<00:20:15.299> platform<00:20:15.600> and 00:20:15.830 --> 00:20:15.840 align:start position:0% control we control the platform and 00:20:15.840 --> 00:20:17.630 align:start position:0% control we control the platform and control<00:20:16.020> the<00:20:16.260> data<00:20:16.559> then<00:20:17.220> we're<00:20:17.400> going<00:20:17.520> to 00:20:17.630 --> 00:20:17.640 align:start position:0% control the data then we're going to 00:20:17.640 --> 00:20:20.570 align:start position:0% control the data then we're going to want<00:20:17.760> users<00:20:18.120> to<00:20:18.360> run<00:20:18.799> uh<00:20:19.799> some<00:20:19.980> of<00:20:20.100> these<00:20:20.220> web3 00:20:20.570 --> 00:20:20.580 align:start position:0% want users to run uh some of these web3 00:20:20.580 --> 00:20:23.390 align:start position:0% want users to run uh some of these web3 infrastructure<00:20:21.120> nodes<00:20:21.419> so<00:20:22.260> for<00:20:22.799> example<00:20:23.039> like 00:20:23.390 --> 00:20:23.400 align:start position:0% infrastructure nodes so for example like 00:20:23.400 --> 00:20:25.549 align:start position:0% infrastructure nodes so for example like this<00:20:23.580> video<00:20:23.820> is<00:20:24.660> being<00:20:24.900> live<00:20:25.140> streamed<00:20:25.440> over 00:20:25.549 --> 00:20:25.559 align:start position:0% this video is being live streamed over 00:20:25.559 --> 00:20:27.650 align:start position:0% this video is being live streamed over live<00:20:25.799> peer<00:20:26.220> and 00:20:27.650 --> 00:20:27.660 align:start position:0% live peer and 00:20:27.660 --> 00:20:29.870 align:start position:0% live peer and uh<00:20:28.320> they<00:20:28.559> have<00:20:28.740> a 00:20:29.870 --> 00:20:29.880 align:start position:0% uh they have a 00:20:29.880 --> 00:20:34.370 align:start position:0% uh they have a network<00:20:30.780> of<00:20:31.500> video<00:20:32.100> trans<00:20:32.580> transcoders 00:20:34.370 --> 00:20:34.380 align:start position:0% network of video trans transcoders 00:20:34.380 --> 00:20:35.029 align:start position:0% network of video trans transcoders um 00:20:35.029 --> 00:20:35.039 align:start position:0% um 00:20:35.039 --> 00:20:37.909 align:start position:0% um and<00:20:35.820> then<00:20:36.179> so<00:20:36.900> they<00:20:37.080> transcode<00:20:37.500> this<00:20:37.740> video 00:20:37.909 --> 00:20:37.919 align:start position:0% and then so they transcode this video 00:20:37.919 --> 00:20:41.270 align:start position:0% and then so they transcode this video and<00:20:38.520> that's<00:20:39.000> that<00:20:39.419> any<00:20:39.960> any<00:20:40.200> one<00:20:40.440> of<00:20:40.559> us<00:20:40.620> if<00:20:41.039> you 00:20:41.270 --> 00:20:41.280 align:start position:0% and that's that any any one of us if you 00:20:41.280 --> 00:20:43.370 align:start position:0% and that's that any any one of us if you have<00:20:41.400> a<00:20:41.520> graphics<00:20:41.820> card<00:20:42.000> can<00:20:42.419> join<00:20:42.780> that<00:20:43.200> live 00:20:43.370 --> 00:20:43.380 align:start position:0% have a graphics card can join that live 00:20:43.380 --> 00:20:45.650 align:start position:0% have a graphics card can join that live peer<00:20:43.740> Network<00:20:43.919> and 00:20:45.650 --> 00:20:45.660 align:start position:0% peer Network and 00:20:45.660 --> 00:20:46.310 align:start position:0% peer Network and um 00:20:46.310 --> 00:20:46.320 align:start position:0% um 00:20:46.320 --> 00:20:48.350 align:start position:0% um we<00:20:46.980> can<00:20:47.039> use<00:20:47.160> our<00:20:47.340> graphics<00:20:47.640> card<00:20:47.760> to<00:20:48.059> right 00:20:48.350 --> 00:20:48.360 align:start position:0% we can use our graphics card to right 00:20:48.360 --> 00:20:50.090 align:start position:0% we can use our graphics card to right transcode<00:20:48.840> that<00:20:49.080> video 00:20:50.090 --> 00:20:50.100 align:start position:0% transcode that video 00:20:50.100 --> 00:20:52.789 align:start position:0% transcode that video um<00:20:50.160> so<00:20:50.400> this<00:20:50.520> is<00:20:50.640> just<00:20:50.760> one<00:20:50.940> example<00:20:51.299> of 00:20:52.789 --> 00:20:52.799 align:start position:0% um so this is just one example of 00:20:52.799 --> 00:20:56.870 align:start position:0% um so this is just one example of yeah<00:20:53.280> like<00:20:53.760> a<00:20:54.000> web<00:20:54.179> 3<00:20:54.980> infrastructure<00:20:55.980> that 00:20:56.870 --> 00:20:56.880 align:start position:0% yeah like a web 3 infrastructure that 00:20:56.880 --> 00:21:00.110 align:start position:0% yeah like a web 3 infrastructure that users<00:20:57.240> can<00:20:57.419> participate<00:20:57.960> in<00:20:58.140> and<00:20:58.320> uh 00:21:00.110 --> 00:21:00.120 align:start position:0% users can participate in and uh 00:21:00.120 --> 00:21:02.029 align:start position:0% users can participate in and uh and<00:21:00.299> have<00:21:00.660> more<00:21:00.780> of<00:21:00.900> a<00:21:01.020> say<00:21:01.140> in<00:21:01.260> and<00:21:01.559> it's 00:21:02.029 --> 00:21:02.039 align:start position:0% and have more of a say in and it's 00:21:02.039 --> 00:21:04.130 align:start position:0% and have more of a say in and it's something<00:21:02.280> that<00:21:02.820> uh 00:21:04.130 --> 00:21:04.140 align:start position:0% something that uh 00:21:04.140 --> 00:21:06.830 align:start position:0% something that uh I<00:21:04.559> think<00:21:04.679> we<00:21:04.860> can<00:21:05.039> support<00:21:05.220> and<00:21:06.179> uh<00:21:06.360> so<00:21:06.539> we<00:21:06.660> show 00:21:06.830 --> 00:21:06.840 align:start position:0% I think we can support and uh so we show 00:21:06.840 --> 00:21:12.289 align:start position:0% I think we can support and uh so we show it<00:21:06.960> here 00:21:12.289 --> 00:21:12.299 align:start position:0% 00:21:12.299 --> 00:21:17.570 align:start position:0% okay<00:21:12.960> and<00:21:13.260> this 00:21:17.570 --> 00:21:17.580 align:start position:0% 00:21:17.580 --> 00:21:26.810 align:start position:0% I<00:21:18.000> think<00:21:18.120> this<00:21:18.299> might<00:21:18.419> be<00:21:18.539> the<00:21:18.720> same<00:21:18.840> video 00:21:26.810 --> 00:21:26.820 align:start position:0% 00:21:26.820 --> 00:21:28.610 align:start position:0% okay<00:21:27.419> and<00:21:27.780> that<00:21:27.960> looks<00:21:28.200> like<00:21:28.260> the<00:21:28.440> same 00:21:28.610 --> 00:21:28.620 align:start position:0% okay and that looks like the same 00:21:28.620 --> 00:21:32.149 align:start position:0% okay and that looks like the same screenshot<00:21:29.039> maybe<00:21:29.280> I<00:21:29.460> hit<00:21:29.640> it<00:21:29.760> back<00:21:29.880> last<00:21:30.120> time 00:21:32.149 --> 00:21:32.159 align:start position:0% screenshot maybe I hit it back last time 00:21:32.159 --> 00:21:34.669 align:start position:0% screenshot maybe I hit it back last time okay<00:21:32.640> a<00:21:32.940> little<00:21:33.059> bit<00:21:33.179> for<00:21:33.480> our<00:21:33.600> road<00:21:33.780> map 00:21:34.669 --> 00:21:34.679 align:start position:0% okay a little bit for our road map 00:21:34.679 --> 00:21:37.310 align:start position:0% okay a little bit for our road map um so<00:21:34.980> really<00:21:35.220> close<00:21:35.400> to<00:21:35.580> releasing<00:21:36.179> uh<00:21:37.140> the 00:21:37.310 --> 00:21:37.320 align:start position:0% um so really close to releasing uh the 00:21:37.320 --> 00:21:39.010 align:start position:0% um so really close to releasing uh the redesigned<00:21:37.740> UI<00:21:38.039> ux 00:21:39.010 --> 00:21:39.020 align:start position:0% redesigned UI ux 00:21:39.020 --> 00:21:41.330 align:start position:0% redesigned UI ux uh<00:21:40.020> and<00:21:40.200> the<00:21:40.380> super<00:21:40.500> simple<00:21:40.679> onboarding 00:21:41.330 --> 00:21:41.340 align:start position:0% uh and the super simple onboarding 00:21:41.340 --> 00:21:43.010 align:start position:0% uh and the super simple onboarding walking<00:21:42.000> you<00:21:42.299> through<00:21:42.480> like<00:21:42.780> the<00:21:42.900> hardware 00:21:43.010 --> 00:21:43.020 align:start position:0% walking you through like the hardware 00:21:43.020 --> 00:21:45.169 align:start position:0% walking you through like the hardware requirements<00:21:43.559> other<00:21:43.679> things<00:21:43.919> like<00:21:44.100> that 00:21:45.169 --> 00:21:45.179 align:start position:0% requirements other things like that 00:21:45.179 --> 00:21:47.630 align:start position:0% requirements other things like that um I<00:21:45.360> want<00:21:45.480> to<00:21:45.600> get<00:21:45.720> more<00:21:45.840> translations 00:21:47.630 --> 00:21:47.640 align:start position:0% um I want to get more translations 00:21:47.640 --> 00:21:49.669 align:start position:0% um I want to get more translations um<00:21:48.059> we're 00:21:49.669 --> 00:21:49.679 align:start position:0% um we're 00:21:49.679 --> 00:21:51.230 align:start position:0% um we're um<00:21:49.740> we're<00:21:50.039> gonna<00:21:50.159> work<00:21:50.340> on<00:21:50.460> that<00:21:50.580> hard<00:21:50.760> push<00:21:51.059> on 00:21:51.230 --> 00:21:51.240 align:start position:0% um we're gonna work on that hard push on 00:21:51.240 --> 00:21:52.610 align:start position:0% um we're gonna work on that hard push on that<00:21:51.360> hard<00:21:51.539> hopefully<00:21:52.020> by<00:21:52.200> the<00:21:52.380> end<00:21:52.500> of 00:21:52.610 --> 00:21:52.620 align:start position:0% that hard hopefully by the end of 00:21:52.620 --> 00:21:54.470 align:start position:0% that hard hopefully by the end of October<00:21:52.980> here 00:21:54.470 --> 00:21:54.480 align:start position:0% October here 00:21:54.480 --> 00:21:56.690 align:start position:0% October here um<00:21:55.080> after<00:21:55.559> that<00:21:55.799> there's<00:21:56.159> some<00:21:56.340> internal 00:21:56.690 --> 00:21:56.700 align:start position:0% um after that there's some internal 00:21:56.700 --> 00:21:58.130 align:start position:0% um after that there's some internal changes<00:21:57.059> that<00:21:57.360> we<00:21:57.480> need<00:21:57.600> to<00:21:57.659> make<00:21:57.840> to<00:21:58.020> support 00:21:58.130 --> 00:21:58.140 align:start position:0% changes that we need to make to support 00:21:58.140 --> 00:22:00.470 align:start position:0% changes that we need to make to support more<00:21:58.380> node<00:21:58.740> types<00:21:59.159> for<00:21:59.340> the<00:21:59.520> future 00:22:00.470 --> 00:22:00.480 align:start position:0% more node types for the future 00:22:00.480 --> 00:22:03.409 align:start position:0% more node types for the future um<00:22:00.960> for<00:22:01.320> the<00:22:01.559> technical<00:22:02.460> folks<00:22:02.760> that's<00:22:03.059> uh 00:22:03.409 --> 00:22:03.419 align:start position:0% um for the technical folks that's uh 00:22:03.419 --> 00:22:05.690 align:start position:0% um for the technical folks that's uh Docker<00:22:03.840> compose<00:22:04.200> that<00:22:04.919> means<00:22:05.220> kind<00:22:05.520> of<00:22:05.580> like 00:22:05.690 --> 00:22:05.700 align:start position:0% Docker compose that means kind of like 00:22:05.700 --> 00:22:07.730 align:start position:0% Docker compose that means kind of like there<00:22:06.120> are<00:22:06.240> nodes<00:22:06.480> that<00:22:06.780> have<00:22:07.020> contained 00:22:07.730 --> 00:22:07.740 align:start position:0% there are nodes that have contained 00:22:07.740 --> 00:22:10.310 align:start position:0% there are nodes that have contained multiple<00:22:08.100> services<00:22:08.600> and<00:22:09.600> so<00:22:09.780> that<00:22:09.900> that<00:22:10.140> will 00:22:10.310 --> 00:22:10.320 align:start position:0% multiple services and so that that will 00:22:10.320 --> 00:22:12.529 align:start position:0% multiple services and so that that will help<00:22:10.500> those<00:22:10.679> node<00:22:10.980> types 00:22:12.529 --> 00:22:12.539 align:start position:0% help those node types 00:22:12.539 --> 00:22:13.190 align:start position:0% help those node types um 00:22:13.190 --> 00:22:13.200 align:start position:0% um 00:22:13.200 --> 00:22:16.190 align:start position:0% um and<00:22:13.980> then<00:22:14.039> additional<00:22:14.400> features<00:22:14.880> I<00:22:15.600> think<00:22:16.080> I 00:22:16.190 --> 00:22:16.200 align:start position:0% and then additional features I think I 00:22:16.200 --> 00:22:18.169 align:start position:0% and then additional features I think I can<00:22:16.320> show<00:22:16.440> you<00:22:16.559> these<00:22:16.799> after 00:22:18.169 --> 00:22:18.179 align:start position:0% can show you these after 00:22:18.179 --> 00:22:19.549 align:start position:0% can show you these after um 00:22:19.549 --> 00:22:19.559 align:start position:0% um 00:22:19.559 --> 00:22:22.490 align:start position:0% um so<00:22:20.220> yeah<00:22:20.580> no<00:22:20.880> notifications<00:22:21.539> if<00:22:22.140> your<00:22:22.320> node 00:22:22.490 --> 00:22:22.500 align:start position:0% so yeah no notifications if your node 00:22:22.500 --> 00:22:25.130 align:start position:0% so yeah no notifications if your node has<00:22:22.679> an<00:22:22.799> error<00:22:23.159> log<00:22:23.280> like<00:22:23.820> we'll<00:22:24.179> we'll<00:22:24.659> show 00:22:25.130 --> 00:22:25.140 align:start position:0% has an error log like we'll we'll show 00:22:25.140 --> 00:22:26.870 align:start position:0% has an error log like we'll we'll show you<00:22:25.320> a<00:22:25.440> notification<00:22:25.860> that<00:22:26.159> error<00:22:26.520> log<00:22:26.580> won't 00:22:26.870 --> 00:22:26.880 align:start position:0% you a notification that error log won't 00:22:26.880 --> 00:22:28.789 align:start position:0% you a notification that error log won't get<00:22:27.179> like<00:22:27.360> lost<00:22:27.659> in<00:22:27.960> your 00:22:28.789 --> 00:22:28.799 align:start position:0% get like lost in your 00:22:28.799 --> 00:22:31.430 align:start position:0% get like lost in your terminal<00:22:29.400> and<00:22:29.640> you'll<00:22:29.820> never<00:22:29.940> know<00:22:30.120> about<00:22:30.299> it 00:22:31.430 --> 00:22:31.440 align:start position:0% terminal and you'll never know about it 00:22:31.440 --> 00:22:32.330 align:start position:0% terminal and you'll never know about it um 00:22:32.330 --> 00:22:32.340 align:start position:0% um 00:22:32.340 --> 00:22:35.330 align:start position:0% um and<00:22:32.700> then<00:22:32.820> you<00:22:33.059> can<00:22:33.120> like<00:22:33.419> search<00:22:33.900> logs<00:22:34.500> maybe 00:22:35.330 --> 00:22:35.340 align:start position:0% and then you can like search logs maybe 00:22:35.340 --> 00:22:36.950 align:start position:0% and then you can like search logs maybe if<00:22:35.520> your<00:22:35.580> internet<00:22:35.760> goes<00:22:36.179> down<00:22:36.240> we'll<00:22:36.480> notify 00:22:36.950 --> 00:22:36.960 align:start position:0% if your internet goes down we'll notify 00:22:36.960 --> 00:22:38.090 align:start position:0% if your internet goes down we'll notify you 00:22:38.090 --> 00:22:38.100 align:start position:0% you 00:22:38.100 --> 00:22:39.409 align:start position:0% you um<00:22:38.159> that<00:22:38.460> your<00:22:38.580> internet<00:22:38.700> was<00:22:39.000> down<00:22:39.179> for<00:22:39.360> a 00:22:39.409 --> 00:22:39.419 align:start position:0% um that your internet was down for a 00:22:39.419 --> 00:22:42.890 align:start position:0% um that your internet was down for a brief<00:22:39.659> time 00:22:42.890 --> 00:22:42.900 align:start position:0% 00:22:42.900 --> 00:22:46.010 align:start position:0% and<00:22:43.799> then<00:22:44.039> after<00:22:44.400> that<00:22:44.760> yeah<00:22:45.120> by<00:22:45.299> February<00:22:45.780> of 00:22:46.010 --> 00:22:46.020 align:start position:0% and then after that yeah by February of 00:22:46.020 --> 00:22:48.409 align:start position:0% and then after that yeah by February of next<00:22:46.260> year<00:22:46.440> we'd<00:22:46.860> like<00:22:47.039> to<00:22:47.280> add<00:22:47.460> Layer<00:22:48.299> Two 00:22:48.409 --> 00:22:48.419 align:start position:0% next year we'd like to add Layer Two 00:22:48.419 --> 00:22:50.029 align:start position:0% next year we'd like to add Layer Two nodes<00:22:48.780> and<00:22:49.020> more<00:22:49.200> web<00:22:49.320> 3<00:22:49.559> infrastructure 00:22:50.029 --> 00:22:50.039 align:start position:0% nodes and more web 3 infrastructure 00:22:50.039 --> 00:22:55.789 align:start position:0% nodes and more web 3 infrastructure nodes 00:22:55.789 --> 00:22:55.799 align:start position:0% 00:22:55.799 --> 00:22:58.549 align:start position:0% all<00:22:56.340> right<00:22:56.580> so<00:22:57.120> it's<00:22:57.480> it<00:22:57.840> is<00:22:58.020> critical<00:22:58.320> to 00:22:58.549 --> 00:22:58.559 align:start position:0% all right so it's it is critical to 00:22:58.559 --> 00:23:00.350 align:start position:0% all right so it's it is critical to ethereum's<00:22:59.159> Mission<00:22:59.340> of<00:22:59.640> decentralization 00:23:00.350 --> 00:23:00.360 align:start position:0% ethereum's Mission of decentralization 00:23:00.360 --> 00:23:02.990 align:start position:0% ethereum's Mission of decentralization censorship<00:23:01.080> resistance<00:23:01.679> and<00:23:02.039> resiliency<00:23:02.520> for 00:23:02.990 --> 00:23:03.000 align:start position:0% censorship resistance and resiliency for 00:23:03.000 --> 00:23:06.409 align:start position:0% censorship resistance and resiliency for users<00:23:03.299> to<00:23:03.539> be<00:23:03.659> able<00:23:03.659> to<00:23:03.840> run<00:23:03.960> nodes<00:23:04.380> and 00:23:06.409 --> 00:23:06.419 align:start position:0% users to be able to run nodes and 00:23:06.419 --> 00:23:07.190 align:start position:0% users to be able to run nodes and um 00:23:07.190 --> 00:23:07.200 align:start position:0% um 00:23:07.200 --> 00:23:08.930 align:start position:0% um this<00:23:07.740> is<00:23:07.799> this<00:23:08.100> is<00:23:08.280> extremely<00:23:08.580> important<00:23:08.820> to 00:23:08.930 --> 00:23:08.940 align:start position:0% this is this is extremely important to 00:23:08.940 --> 00:23:10.490 align:start position:0% this is this is extremely important to me<00:23:09.059> because<00:23:09.299> like<00:23:09.720> all<00:23:10.020> of<00:23:10.080> the<00:23:10.200> other<00:23:10.320> good 00:23:10.490 --> 00:23:10.500 align:start position:0% me because like all of the other good 00:23:10.500 --> 00:23:12.830 align:start position:0% me because like all of the other good things<00:23:10.679> we<00:23:10.980> talk<00:23:11.100> about<00:23:11.220> here 00:23:12.830 --> 00:23:12.840 align:start position:0% things we talk about here 00:23:12.840 --> 00:23:14.630 align:start position:0% things we talk about here um<00:23:12.960> you<00:23:13.200> know<00:23:13.320> will<00:23:13.559> only<00:23:13.799> last<00:23:14.100> will<00:23:14.400> only 00:23:14.630 --> 00:23:14.640 align:start position:0% um you know will only last will only 00:23:14.640 --> 00:23:17.510 align:start position:0% um you know will only last will only exist<00:23:15.000> will<00:23:15.240> only<00:23:15.480> really<00:23:15.600> be<00:23:15.840> possible<00:23:16.200> if<00:23:16.799> we 00:23:17.510 --> 00:23:17.520 align:start position:0% exist will only really be possible if we 00:23:17.520 --> 00:23:20.870 align:start position:0% exist will only really be possible if we have<00:23:17.760> a<00:23:18.000> truly<00:23:18.360> like<00:23:18.840> user-led 00:23:20.870 --> 00:23:20.880 align:start position:0% have a truly like user-led 00:23:20.880 --> 00:23:21.529 align:start position:0% have a truly like user-led um 00:23:21.529 --> 00:23:21.539 align:start position:0% um 00:23:21.539 --> 00:23:24.890 align:start position:0% um a<00:23:22.080> culture<00:23:22.440> of<00:23:22.559> like<00:23:22.679> running<00:23:22.860> nodes<00:23:23.280> and<00:23:24.240> if 00:23:24.890 --> 00:23:24.900 align:start position:0% a culture of like running nodes and if 00:23:24.900 --> 00:23:27.409 align:start position:0% a culture of like running nodes and if the<00:23:25.559> core<00:23:25.679> devs<00:23:26.159> continue<00:23:26.280> to<00:23:26.700> make<00:23:27.240> it 00:23:27.409 --> 00:23:27.419 align:start position:0% the core devs continue to make it 00:23:27.419 --> 00:23:30.289 align:start position:0% the core devs continue to make it possible<00:23:27.659> for<00:23:27.900> users<00:23:28.200> to<00:23:28.380> run<00:23:28.500> nodes<00:23:28.860> so<00:23:29.760> yeah 00:23:30.289 --> 00:23:30.299 align:start position:0% possible for users to run nodes so yeah 00:23:30.299 --> 00:23:32.750 align:start position:0% possible for users to run nodes so yeah for<00:23:30.539> like<00:23:30.840> if<00:23:31.320> we<00:23:31.440> want<00:23:31.620> this<00:23:31.919> dream<00:23:32.220> of<00:23:32.460> like 00:23:32.750 --> 00:23:32.760 align:start position:0% for like if we want this dream of like 00:23:32.760 --> 00:23:35.270 align:start position:0% for like if we want this dream of like open<00:23:33.299> Global<00:23:33.900> infrastructure<00:23:34.679> super<00:23:34.980> low 00:23:35.270 --> 00:23:35.280 align:start position:0% open Global infrastructure super low 00:23:35.280 --> 00:23:37.190 align:start position:0% open Global infrastructure super low transaction<00:23:35.760> fees<00:23:36.120> for<00:23:36.299> the<00:23:36.480> world<00:23:36.600> like<00:23:37.080> open 00:23:37.190 --> 00:23:37.200 align:start position:0% transaction fees for the world like open 00:23:37.200 --> 00:23:39.230 align:start position:0% transaction fees for the world like open Financial<00:23:37.559> system 00:23:39.230 --> 00:23:39.240 align:start position:0% Financial system 00:23:39.240 --> 00:23:40.750 align:start position:0% Financial system um 00:23:40.750 --> 00:23:40.760 align:start position:0% um 00:23:40.760 --> 00:23:44.149 align:start position:0% um ethereum<00:23:41.760> for<00:23:41.940> everyone<00:23:42.120> we<00:23:42.659> need<00:23:42.980> users<00:23:43.980> to 00:23:44.149 --> 00:23:44.159 align:start position:0% ethereum for everyone we need users to 00:23:44.159 --> 00:23:48.470 align:start position:0% ethereum for everyone we need users to continue<00:23:44.280> to<00:23:44.580> run<00:23:44.700> nodes 00:23:48.470 --> 00:23:48.480 align:start position:0% 00:23:48.480 --> 00:23:50.270 align:start position:0% and<00:23:49.080> nice<00:23:49.320> to<00:23:49.500> know<00:23:49.559> the<00:23:49.679> mission<00:23:49.860> is<00:23:50.100> to 00:23:50.270 --> 00:23:50.280 align:start position:0% and nice to know the mission is to 00:23:50.280 --> 00:23:53.210 align:start position:0% and nice to know the mission is to simplify<00:23:50.580> node<00:23:50.940> running 00:23:53.210 --> 00:23:53.220 align:start position:0% 00:23:53.220 --> 00:23:56.280 align:start position:0% and<00:23:53.940> thank<00:23:54.240> you<00:23:54.360> gracias<00:23:55.260> artoros 00:23:56.280 --> 00:23:56.290 align:start position:0% and thank you gracias artoros 00:23:56.290 --> 00:24:01.070 align:start position:0% and thank you gracias artoros [Applause] 00:24:01.070 --> 00:24:01.080 align:start position:0% 00:24:01.080 --> 00:24:03.409 align:start position:0% so<00:24:01.740> yeah<00:24:02.100> I<00:24:02.280> want<00:24:02.400> to<00:24:02.520> open<00:24:02.640> it<00:24:02.820> for<00:24:03.059> questions 00:24:03.409 --> 00:24:03.419 align:start position:0% so yeah I want to open it for questions 00:24:03.419 --> 00:24:05.750 align:start position:0% so yeah I want to open it for questions and<00:24:04.860> um 00:24:05.750 --> 00:24:05.760 align:start position:0% and um 00:24:05.760 --> 00:24:08.270 align:start position:0% and um uh<00:24:06.299> let's<00:24:06.539> see<00:24:06.780> I<00:24:07.559> just<00:24:07.740> want<00:24:07.860> to<00:24:07.980> move<00:24:08.039> it<00:24:08.159> to 00:24:08.270 --> 00:24:08.280 align:start position:0% uh let's see I just want to move it to 00:24:08.280 --> 00:24:10.430 align:start position:0% uh let's see I just want to move it to this<00:24:08.400> slide<00:24:08.640> uh<00:24:09.240> so<00:24:09.419> yeah<00:24:09.780> real<00:24:10.020> quick<00:24:10.140> if<00:24:10.320> you 00:24:10.430 --> 00:24:10.440 align:start position:0% this slide uh so yeah real quick if you 00:24:10.440 --> 00:24:13.010 align:start position:0% this slide uh so yeah real quick if you want<00:24:10.559> to<00:24:10.679> help<00:24:10.799> uh<00:24:11.520> we<00:24:11.700> need<00:24:11.820> everybody 00:24:13.010 --> 00:24:13.020 align:start position:0% want to help uh we need everybody 00:24:13.020 --> 00:24:13.789 align:start position:0% want to help uh we need everybody um 00:24:13.789 --> 00:24:13.799 align:start position:0% um 00:24:13.799 --> 00:24:16.730 align:start position:0% um join<00:24:14.280> our<00:24:14.340> Discord<00:24:14.640> reach<00:24:15.059> out<00:24:15.120> on<00:24:15.299> Twitter 00:24:16.730 --> 00:24:16.740 align:start position:0% join our Discord reach out on Twitter 00:24:16.740 --> 00:24:18.230 align:start position:0% join our Discord reach out on Twitter um there's<00:24:17.340> a<00:24:17.520> website<00:24:17.760> here<00:24:18.000> you<00:24:18.120> can 00:24:18.230 --> 00:24:18.240 align:start position:0% um there's a website here you can 00:24:18.240 --> 00:24:20.990 align:start position:0% um there's a website here you can translate<00:24:18.419> on<00:24:18.780> uh<00:24:19.620> which<00:24:20.100> I'll<00:24:20.520> get<00:24:20.700> notified 00:24:20.990 --> 00:24:21.000 align:start position:0% translate on uh which I'll get notified 00:24:21.000 --> 00:24:23.090 align:start position:0% translate on uh which I'll get notified as<00:24:21.299> soon<00:24:21.419> as<00:24:21.539> someone<00:24:21.659> translates 00:24:23.090 --> 00:24:23.100 align:start position:0% as soon as someone translates 00:24:23.100 --> 00:24:24.770 align:start position:0% as soon as someone translates um<00:24:23.159> so<00:24:23.520> that's<00:24:23.640> cool<00:24:23.880> too 00:24:24.770 --> 00:24:24.780 align:start position:0% um so that's cool too 00:24:24.780 --> 00:24:28.010 align:start position:0% um so that's cool too and<00:24:25.260> yeah<00:24:25.440> question<00:24:25.860> time 00:24:28.010 --> 00:24:28.020 align:start position:0% and yeah question time 00:24:28.020 --> 00:24:29.590 align:start position:0% and yeah question time thank<00:24:28.500> you<00:24:28.559> for<00:24:28.679> your<00:24:28.860> time 00:24:29.590 --> 00:24:29.600 align:start position:0% thank you for your time 00:24:29.600 --> 00:24:31.549 align:start position:0% thank you for your time I've<00:24:30.600> got<00:24:30.720> this<00:24:30.900> core<00:24:31.080> philosophical 00:24:31.549 --> 00:24:31.559 align:start position:0% I've got this core philosophical 00:24:31.559 --> 00:24:32.990 align:start position:0% I've got this core philosophical question<00:24:31.919> that<00:24:32.159> I've<00:24:32.280> had<00:24:32.400> for<00:24:32.580> a<00:24:32.700> long<00:24:32.820> time 00:24:32.990 --> 00:24:33.000 align:start position:0% question that I've had for a long time 00:24:33.000 --> 00:24:35.870 align:start position:0% question that I've had for a long time which<00:24:33.840> is<00:24:34.020> I<00:24:34.620> feel<00:24:34.799> and<00:24:35.100> maybe<00:24:35.280> this<00:24:35.460> is<00:24:35.580> a<00:24:35.700> lack 00:24:35.870 --> 00:24:35.880 align:start position:0% which is I feel and maybe this is a lack 00:24:35.880 --> 00:24:37.850 align:start position:0% which is I feel and maybe this is a lack of<00:24:36.000> understanding<00:24:36.480> that<00:24:36.860> full 00:24:37.850 --> 00:24:37.860 align:start position:0% of understanding that full 00:24:37.860 --> 00:24:41.330 align:start position:0% of understanding that full non-validating<00:24:38.760> notes<00:24:39.240> are<00:24:39.480> overvaluable 00:24:41.330 --> 00:24:41.340 align:start position:0% non-validating notes are overvaluable 00:24:41.340 --> 00:24:43.250 align:start position:0% non-validating notes are overvaluable because<00:24:41.580> in<00:24:42.000> the<00:24:42.179> end<00:24:42.240> the<00:24:42.539> state<00:24:42.840> is<00:24:43.080> only 00:24:43.250 --> 00:24:43.260 align:start position:0% because in the end the state is only 00:24:43.260 --> 00:24:46.130 align:start position:0% because in the end the state is only managed<00:24:43.679> by<00:24:43.919> full<00:24:44.760> value 00:24:46.130 --> 00:24:46.140 align:start position:0% managed by full value 00:24:46.140 --> 00:24:47.649 align:start position:0% managed by full value so 00:24:47.649 --> 00:24:47.659 align:start position:0% so 00:24:47.659 --> 00:24:49.850 align:start position:0% so why<00:24:48.659> does<00:24:48.780> it<00:24:48.960> really<00:24:49.140> matter<00:24:49.320> that<00:24:49.679> they're 00:24:49.850 --> 00:24:49.860 align:start position:0% why does it really matter that they're 00:24:49.860 --> 00:24:53.610 align:start position:0% why does it really matter that they're more<00:24:50.100> and<00:24:50.280> more 00:24:53.610 --> 00:24:53.620 align:start position:0% 00:24:53.620 --> 00:24:58.810 align:start position:0% [Music] 00:24:58.810 --> 00:24:58.820 align:start position:0% 00:24:58.820 --> 00:25:02.090 align:start position:0% to<00:24:59.820> just<00:25:00.240> deploy<00:25:00.659> thousands<00:25:01.260> of<00:25:01.320> full 00:25:02.090 --> 00:25:02.100 align:start position:0% to just deploy thousands of full 00:25:02.100 --> 00:25:04.190 align:start position:0% to just deploy thousands of full non-validating<00:25:02.820> nodes<00:25:03.179> which<00:25:03.720> don't<00:25:03.960> make 00:25:04.190 --> 00:25:04.200 align:start position:0% non-validating nodes which don't make 00:25:04.200 --> 00:25:05.810 align:start position:0% non-validating nodes which don't make mistake 00:25:05.810 --> 00:25:05.820 align:start position:0% mistake 00:25:05.820 --> 00:25:09.549 align:start position:0% mistake to<00:25:06.299> overpower<00:25:06.780> to<00:25:07.559> kind<00:25:07.860> of<00:25:07.919> cycle<00:25:08.159> attack 00:25:09.549 --> 00:25:09.559 align:start position:0% to overpower to kind of cycle attack 00:25:09.559 --> 00:25:11.570 align:start position:0% to overpower to kind of cycle attack non-validating<00:25:10.559> Network 00:25:11.570 --> 00:25:11.580 align:start position:0% non-validating Network 00:25:11.580 --> 00:25:12.950 align:start position:0% non-validating Network okay<00:25:12.000> so 00:25:12.950 --> 00:25:12.960 align:start position:0% okay so 00:25:12.960 --> 00:25:14.390 align:start position:0% okay so um<00:25:13.080> tell<00:25:13.500> me<00:25:13.620> if<00:25:13.679> I<00:25:13.799> understood<00:25:14.100> your<00:25:14.280> question 00:25:14.390 --> 00:25:14.400 align:start position:0% um tell me if I understood your question 00:25:14.400 --> 00:25:16.610 align:start position:0% um tell me if I understood your question right<00:25:14.580> so<00:25:14.940> your<00:25:15.179> question<00:25:15.299> is<00:25:15.539> what's<00:25:16.440> the 00:25:16.610 --> 00:25:16.620 align:start position:0% right so your question is what's the 00:25:16.620 --> 00:25:20.390 align:start position:0% right so your question is what's the importance<00:25:17.039> of<00:25:17.640> uh<00:25:18.500> non-valid<00:25:19.500> non-staking 00:25:20.390 --> 00:25:20.400 align:start position:0% importance of uh non-valid non-staking 00:25:20.400 --> 00:25:23.029 align:start position:0% importance of uh non-valid non-staking non-validator<00:25:21.179> nodes<00:25:21.539> like<00:25:21.780> without<00:25:21.960> eth 00:25:23.029 --> 00:25:23.039 align:start position:0% non-validator nodes like without eth 00:25:23.039 --> 00:25:25.310 align:start position:0% non-validator nodes like without eth um<00:25:23.100> what's<00:25:23.700> what's<00:25:23.760> their<00:25:24.240> importance 00:25:25.310 --> 00:25:25.320 align:start position:0% um what's what's their importance 00:25:25.320 --> 00:25:35.570 align:start position:0% um what's what's their importance um 00:25:35.570 --> 00:25:35.580 align:start position:0% 00:25:35.580 --> 00:25:38.390 align:start position:0% yeah<00:25:35.820> yeah<00:25:36.320> so<00:25:37.320> uh<00:25:37.679> it's<00:25:37.799> a<00:25:37.980> great<00:25:38.100> question 00:25:38.390 --> 00:25:38.400 align:start position:0% yeah yeah so uh it's a great question 00:25:38.400 --> 00:25:41.930 align:start position:0% yeah yeah so uh it's a great question and<00:25:39.140> what<00:25:40.140> it<00:25:40.260> does<00:25:40.440> is<00:25:40.860> uh<00:25:41.279> the<00:25:41.580> non-eth 00:25:41.930 --> 00:25:41.940 align:start position:0% and what it does is uh the non-eth 00:25:41.940 --> 00:25:44.149 align:start position:0% and what it does is uh the non-eth non-staking<00:25:42.539> nodes<00:25:42.960> actually<00:25:43.320> keep<00:25:43.799> the 00:25:44.149 --> 00:25:44.159 align:start position:0% non-staking nodes actually keep the 00:25:44.159 --> 00:25:47.210 align:start position:0% non-staking nodes actually keep the validators<00:25:44.820> it<00:25:45.419> keeps<00:25:45.779> the<00:25:46.140> e-stick<00:25:46.919> nodes 00:25:47.210 --> 00:25:47.220 align:start position:0% validators it keeps the e-stick nodes 00:25:47.220 --> 00:25:48.230 align:start position:0% validators it keeps the e-stick nodes honest 00:25:48.230 --> 00:25:48.240 align:start position:0% honest 00:25:48.240 --> 00:25:50.529 align:start position:0% honest so<00:25:48.840> yeah<00:25:49.020> if<00:25:49.320> let's<00:25:49.679> say 00:25:50.529 --> 00:25:50.539 align:start position:0% so yeah if let's say 00:25:50.539 --> 00:25:53.570 align:start position:0% so yeah if let's say some<00:25:51.539> centralized<00:25:52.140> staking<00:25:52.500> service<00:25:52.799> gets 00:25:53.570 --> 00:25:53.580 align:start position:0% some centralized staking service gets 00:25:53.580 --> 00:25:56.810 align:start position:0% some centralized staking service gets yeah<00:25:54.059> 75<00:25:54.539> of<00:25:55.020> the<00:25:55.080> validators 00:25:56.810 --> 00:25:56.820 align:start position:0% yeah 75 of the validators 00:25:56.820 --> 00:25:58.490 align:start position:0% yeah 75 of the validators um<00:25:56.880> and<00:25:57.360> they<00:25:57.539> want<00:25:57.720> to<00:25:57.779> push<00:25:57.960> through<00:25:58.140> a<00:25:58.380> block 00:25:58.490 --> 00:25:58.500 align:start position:0% um and they want to push through a block 00:25:58.500 --> 00:26:01.850 align:start position:0% um and they want to push through a block that<00:25:58.919> sends<00:25:59.279> all<00:25:59.460> the<00:25:59.580> youth<00:25:59.880> to<00:26:00.059> them<00:26:00.440> uh<00:26:01.440> the 00:26:01.850 --> 00:26:01.860 align:start position:0% that sends all the youth to them uh the 00:26:01.860 --> 00:26:04.730 align:start position:0% that sends all the youth to them uh the non-eth<00:26:02.460> uh<00:26:03.240> nodes<00:26:03.659> will<00:26:04.020> say<00:26:04.200> hey<00:26:04.380> that's 00:26:04.730 --> 00:26:04.740 align:start position:0% non-eth uh nodes will say hey that's 00:26:04.740 --> 00:26:06.769 align:start position:0% non-eth uh nodes will say hey that's like<00:26:05.159> that's<00:26:05.580> a<00:26:05.760> funky<00:26:06.059> block<00:26:06.240> that<00:26:06.600> doesn't 00:26:06.769 --> 00:26:06.779 align:start position:0% like that's a funky block that doesn't 00:26:06.779 --> 00:26:08.990 align:start position:0% like that's a funky block that doesn't apply<00:26:07.320> that<00:26:07.620> doesn't<00:26:07.799> uh<00:26:08.220> follow<00:26:08.460> the<00:26:08.760> rules 00:26:08.990 --> 00:26:09.000 align:start position:0% apply that doesn't uh follow the rules 00:26:09.000 --> 00:26:10.610 align:start position:0% apply that doesn't uh follow the rules of<00:26:09.240> ethereum<00:26:09.779> that's<00:26:10.020> you're<00:26:10.320> trying<00:26:10.500> to 00:26:10.610 --> 00:26:10.620 align:start position:0% of ethereum that's you're trying to 00:26:10.620 --> 00:26:12.230 align:start position:0% of ethereum that's you're trying to steal<00:26:10.860> someone's<00:26:11.100> money<00:26:11.279> reject<00:26:11.880> that<00:26:12.059> block 00:26:12.230 --> 00:26:12.240 align:start position:0% steal someone's money reject that block 00:26:12.240 --> 00:26:14.870 align:start position:0% steal someone's money reject that block I'm<00:26:12.539> not<00:26:12.720> like<00:26:13.080> I'm<00:26:13.679> not<00:26:13.860> gonna<00:26:14.039> I'm<00:26:14.640> not<00:26:14.760> gonna 00:26:14.870 --> 00:26:14.880 align:start position:0% I'm not like I'm not gonna I'm not gonna 00:26:14.880 --> 00:26:17.269 align:start position:0% I'm not like I'm not gonna I'm not gonna take<00:26:15.120> that<00:26:15.419> transaction<00:26:15.960> and<00:26:16.919> share<00:26:17.100> it<00:26:17.159> with 00:26:17.269 --> 00:26:17.279 align:start position:0% take that transaction and share it with 00:26:17.279 --> 00:26:18.769 align:start position:0% take that transaction and share it with anyone<00:26:17.520> else<00:26:17.640> I'm<00:26:17.820> going<00:26:17.940> to<00:26:18.000> drop<00:26:18.179> it<00:26:18.419> and<00:26:18.659> say 00:26:18.769 --> 00:26:18.779 align:start position:0% anyone else I'm going to drop it and say 00:26:18.779 --> 00:26:21.230 align:start position:0% anyone else I'm going to drop it and say that's<00:26:18.960> invalid<00:26:19.559> so<00:26:20.340> it<00:26:20.580> essentially<00:26:20.880> keeps 00:26:21.230 --> 00:26:21.240 align:start position:0% that's invalid so it essentially keeps 00:26:21.240 --> 00:26:22.669 align:start position:0% that's invalid so it essentially keeps them<00:26:21.299> honest 00:26:22.669 --> 00:26:22.679 align:start position:0% them honest 00:26:22.679 --> 00:26:26.070 align:start position:0% them honest foreign 00:26:26.070 --> 00:26:26.080 align:start position:0% 00:26:26.080 --> 00:26:34.120 align:start position:0% [Music] 00:26:34.120 --> 00:26:34.130 align:start position:0% 00:26:34.130 --> 00:26:36.409 align:start position:0% [Music] 00:26:36.409 --> 00:26:36.419 align:start position:0% [Music] 00:26:36.419 --> 00:26:39.049 align:start position:0% [Music] to<00:26:36.900> push<00:26:37.080> another<00:26:37.440> 10<00:26:37.980> 000<00:26:38.039> into<00:26:38.640> the<00:26:38.940> network 00:26:39.049 --> 00:26:39.059 align:start position:0% to push another 10 000 into the network 00:26:39.059 --> 00:26:41.210 align:start position:0% to push another 10 000 into the network is<00:26:39.419> very<00:26:39.720> easy 00:26:41.210 --> 00:26:41.220 align:start position:0% is very easy 00:26:41.220 --> 00:26:45.169 align:start position:0% is very easy so<00:26:41.580> how<00:26:42.059> how<00:26:42.179> strong<00:26:43.080> it<00:26:43.380> really<00:26:43.620> is<00:26:43.860> the<00:26:44.279> is 00:26:45.169 --> 00:26:45.179 align:start position:0% so how how strong it really is the is 00:26:45.179 --> 00:26:46.669 align:start position:0% so how how strong it really is the is the<00:26:45.419> defense<00:26:45.600> mechanism 00:26:46.669 --> 00:26:46.679 align:start position:0% the defense mechanism 00:26:46.679 --> 00:26:48.350 align:start position:0% the defense mechanism yeah<00:26:47.159> that's<00:26:47.340> that's<00:26:47.580> a<00:26:47.760> good<00:26:47.880> question<00:26:48.000> so 00:26:48.350 --> 00:26:48.360 align:start position:0% yeah that's that's a good question so 00:26:48.360 --> 00:26:50.990 align:start position:0% yeah that's that's a good question so like<00:26:48.600> if<00:26:48.779> someone<00:26:48.960> were<00:26:49.260> to<00:26:49.500> on<00:26:50.279> a<00:26:50.520> some<00:26:50.820> cloud 00:26:50.990 --> 00:26:51.000 align:start position:0% like if someone were to on a some cloud 00:26:51.000 --> 00:26:52.549 align:start position:0% like if someone were to on a some cloud service<00:26:51.240> just<00:26:51.659> spin<00:26:51.840> up<00:26:51.960> like<00:26:52.140> a<00:26:52.320> ton<00:26:52.440> of 00:26:52.549 --> 00:26:52.559 align:start position:0% service just spin up like a ton of 00:26:52.559 --> 00:26:55.909 align:start position:0% service just spin up like a ton of non-eth<00:26:52.980> nodes<00:26:53.820> um 00:26:55.909 --> 00:26:55.919 align:start position:0% 00:26:55.919 --> 00:26:57.409 align:start position:0% I<00:26:56.460> think<00:26:56.520> it<00:26:56.700> would<00:26:56.820> be<00:26:56.880> I<00:26:57.059> think<00:26:57.179> it<00:26:57.299> would 00:26:57.409 --> 00:26:57.419 align:start position:0% I think it would be I think it would 00:26:57.419 --> 00:26:59.810 align:start position:0% I think it would be I think it would probably<00:26:57.600> be<00:26:57.779> more<00:26:58.140> costly<00:26:58.500> than 00:26:59.810 --> 00:26:59.820 align:start position:0% probably be more costly than 00:26:59.820 --> 00:27:01.669 align:start position:0% probably be more costly than um<00:26:59.880> it<00:27:00.600> would<00:27:00.659> be<00:27:00.779> I<00:27:00.960> think<00:27:01.080> it<00:27:01.200> still<00:27:01.380> would<00:27:01.559> be 00:27:01.669 --> 00:27:01.679 align:start position:0% um it would be I think it still would be 00:27:01.679 --> 00:27:02.930 align:start position:0% um it would be I think it still would be pretty<00:27:01.799> costly 00:27:02.930 --> 00:27:02.940 align:start position:0% pretty costly 00:27:02.940 --> 00:27:04.250 align:start position:0% pretty costly um and 00:27:04.250 --> 00:27:04.260 align:start position:0% um and 00:27:04.260 --> 00:27:06.590 align:start position:0% um and I<00:27:04.740> think<00:27:04.860> even<00:27:05.159> if<00:27:05.580> let's<00:27:05.880> say<00:27:06.059> they<00:27:06.360> have 00:27:06.590 --> 00:27:06.600 align:start position:0% I think even if let's say they have 00:27:06.600 --> 00:27:08.870 align:start position:0% I think even if let's say they have triple<00:27:07.260> quadruple<00:27:08.039> the<00:27:08.220> number<00:27:08.400> of<00:27:08.640> like 00:27:08.870 --> 00:27:08.880 align:start position:0% triple quadruple the number of like 00:27:08.880 --> 00:27:13.610 align:start position:0% triple quadruple the number of like honest<00:27:09.360> nice<00:27:10.260> nodes<00:27:11.059> uh<00:27:12.059> then 00:27:13.610 --> 00:27:13.620 align:start position:0% honest nice nodes uh then 00:27:13.620 --> 00:27:15.769 align:start position:0% honest nice nodes uh then I<00:27:14.220> think<00:27:14.340> the<00:27:14.460> attack<00:27:14.520> would<00:27:14.880> still<00:27:15.120> fail<00:27:15.299> or 00:27:15.769 --> 00:27:15.779 align:start position:0% I think the attack would still fail or 00:27:15.779 --> 00:27:19.250 align:start position:0% I think the attack would still fail or it<00:27:16.140> may<00:27:16.740> in<00:27:17.159> this<00:27:17.279> case<00:27:17.460> uh<00:27:18.179> default<00:27:18.779> to<00:27:18.900> chaos 00:27:19.250 --> 00:27:19.260 align:start position:0% it may in this case uh default to chaos 00:27:19.260 --> 00:27:20.510 align:start position:0% it may in this case uh default to chaos so<00:27:19.440> I<00:27:19.620> think 00:27:20.510 --> 00:27:20.520 align:start position:0% so I think 00:27:20.520 --> 00:27:21.950 align:start position:0% so I think I'm<00:27:20.940> probably<00:27:21.120> not<00:27:21.299> the<00:27:21.419> best<00:27:21.539> person<00:27:21.720> to 00:27:21.950 --> 00:27:21.960 align:start position:0% I'm probably not the best person to 00:27:21.960 --> 00:27:24.049 align:start position:0% I'm probably not the best person to speak<00:27:22.080> in<00:27:22.260> terms<00:27:22.500> of<00:27:22.559> like<00:27:22.740> hey<00:27:22.919> we<00:27:23.159> need<00:27:23.340> X 00:27:24.049 --> 00:27:24.059 align:start position:0% speak in terms of like hey we need X 00:27:24.059 --> 00:27:27.590 align:start position:0% speak in terms of like hey we need X number<00:27:24.360> of<00:27:24.600> honest<00:27:25.440> nodes<00:27:25.740> but<00:27:26.220> I<00:27:26.340> think 00:27:27.590 --> 00:27:27.600 align:start position:0% number of honest nodes but I think 00:27:27.600 --> 00:27:29.990 align:start position:0% number of honest nodes but I think um<00:27:27.740> sufficiently<00:27:28.740> so<00:27:29.159> so<00:27:29.220> right<00:27:29.640> now<00:27:29.760> I<00:27:29.880> think 00:27:29.990 --> 00:27:30.000 align:start position:0% um sufficiently so so right now I think 00:27:30.000 --> 00:27:34.669 align:start position:0% um sufficiently so so right now I think it's<00:27:30.120> it's<00:27:30.360> at<00:27:30.600> about<00:27:30.779> like<00:27:31.080> 8<00:27:31.620> 000<00:27:31.740> and<00:27:33.120> um 00:27:34.669 --> 00:27:34.679 align:start position:0% it's it's at about like 8 000 and um 00:27:34.679 --> 00:27:35.990 align:start position:0% it's it's at about like 8 000 and um yeah<00:27:35.100> I<00:27:35.279> don't<00:27:35.400> know<00:27:35.460> what<00:27:35.580> that<00:27:35.700> right<00:27:35.820> number 00:27:35.990 --> 00:27:36.000 align:start position:0% yeah I don't know what that right number 00:27:36.000 --> 00:27:38.450 align:start position:0% yeah I don't know what that right number is<00:27:36.240> I<00:27:36.539> I<00:27:36.779> was<00:27:37.320> reading<00:27:37.620> one<00:27:37.740> of<00:27:37.799> italics<00:27:38.159> blog 00:27:38.450 --> 00:27:38.460 align:start position:0% is I I was reading one of italics blog 00:27:38.460 --> 00:27:40.549 align:start position:0% is I I was reading one of italics blog and<00:27:38.640> I<00:27:38.760> think<00:27:38.880> he<00:27:39.059> even<00:27:39.179> said 00:27:40.549 --> 00:27:40.559 align:start position:0% and I think he even said 00:27:40.559 --> 00:27:42.710 align:start position:0% and I think he even said I'm<00:27:41.100> not<00:27:41.220> sure<00:27:41.340> how<00:27:41.520> many<00:27:41.700> it<00:27:42.059> is<00:27:42.240> it's 00:27:42.710 --> 00:27:42.720 align:start position:0% I'm not sure how many it is it's 00:27:42.720 --> 00:27:44.390 align:start position:0% I'm not sure how many it is it's probably<00:27:43.080> more<00:27:43.380> than<00:27:43.620> like<00:27:43.919> a<00:27:44.100> few<00:27:44.220> hundred 00:27:44.390 --> 00:27:44.400 align:start position:0% probably more than like a few hundred 00:27:44.400 --> 00:27:48.230 align:start position:0% probably more than like a few hundred but<00:27:44.880> I<00:27:45.299> don't<00:27:45.419> know<00:27:45.539> yeah 00:27:48.230 --> 00:27:48.240 align:start position:0% 00:27:48.240 --> 00:27:50.930 align:start position:0% yeah I<00:27:49.080> I<00:27:49.380> yeah<00:27:49.980> I'm<00:27:50.159> not<00:27:50.279> the<00:27:50.400> best<00:27:50.520> person<00:27:50.700> I 00:27:50.930 --> 00:27:50.940 align:start position:0% yeah I I yeah I'm not the best person I 00:27:50.940 --> 00:27:53.690 align:start position:0% yeah I I yeah I'm not the best person I hope<00:27:51.059> the<00:27:51.240> courthouse<00:27:51.720> thought<00:27:51.960> about<00:27:52.080> that 00:27:53.690 --> 00:27:53.700 align:start position:0% hope the courthouse thought about that 00:27:53.700 --> 00:27:57.490 align:start position:0% hope the courthouse thought about that okay 00:27:57.490 --> 00:27:57.500 align:start position:0% 00:27:57.500 --> 00:27:59.090 align:start position:0% yeah 00:27:59.090 --> 00:27:59.100 align:start position:0% yeah 00:27:59.100 --> 00:28:05.350 align:start position:0% yeah um 00:28:05.350 --> 00:28:05.360 align:start position:0% 00:28:05.360 --> 00:28:07.490 align:start position:0% my<00:28:06.360> father<00:28:06.480> could<00:28:06.659> run<00:28:06.779> it<00:28:06.960> my<00:28:07.140> mother<00:28:07.260> could 00:28:07.490 --> 00:28:07.500 align:start position:0% my father could run it my mother could 00:28:07.500 --> 00:28:08.990 align:start position:0% my father could run it my mother could run<00:28:07.679> it<00:28:07.799> in<00:28:07.860> their<00:28:07.980> home 00:28:08.990 --> 00:28:09.000 align:start position:0% run it in their home 00:28:09.000 --> 00:28:10.610 align:start position:0% run it in their home attack 00:28:10.610 --> 00:28:10.620 align:start position:0% attack 00:28:10.620 --> 00:28:13.909 align:start position:0% attack um<00:28:10.740> so<00:28:11.340> if<00:28:11.700> they<00:28:11.880> get<00:28:12.059> all<00:28:12.240> this<00:28:12.419> set<00:28:12.600> up<00:28:12.779> and<00:28:13.260> I 00:28:13.909 --> 00:28:13.919 align:start position:0% um so if they get all this set up and I 00:28:13.919 --> 00:28:15.710 align:start position:0% um so if they get all this set up and I show<00:28:14.279> them<00:28:14.400> what<00:28:14.580> ethereum<00:28:14.940> is<00:28:15.120> and<00:28:15.360> they<00:28:15.539> put 00:28:15.710 --> 00:28:15.720 align:start position:0% show them what ethereum is and they put 00:28:15.720 --> 00:28:17.210 align:start position:0% show them what ethereum is and they put all<00:28:15.840> this<00:28:16.020> money<00:28:16.140> into<00:28:16.380> it<00:28:16.559> now<00:28:16.799> they<00:28:16.980> have 00:28:17.210 --> 00:28:17.220 align:start position:0% all this money into it now they have 00:28:17.220 --> 00:28:18.649 align:start position:0% all this money into it now they have this<00:28:17.460> money<00:28:17.640> running<00:28:17.880> on<00:28:18.179> this<00:28:18.299> Windows 00:28:18.649 --> 00:28:18.659 align:start position:0% this money running on this Windows 00:28:18.659 --> 00:28:21.590 align:start position:0% this money running on this Windows computer<00:28:18.840> there<00:28:19.340> and<00:28:20.340> it<00:28:20.880> has<00:28:21.059> no<00:28:21.360> battery 00:28:21.590 --> 00:28:21.600 align:start position:0% computer there and it has no battery 00:28:21.600 --> 00:28:24.470 align:start position:0% computer there and it has no battery backup<00:28:22.200> it<00:28:22.559> has<00:28:22.860> no<00:28:23.700> um<00:28:23.760> they<00:28:24.000> just<00:28:24.179> shut<00:28:24.299> it 00:28:24.470 --> 00:28:24.480 align:start position:0% backup it has no um they just shut it 00:28:24.480 --> 00:28:26.210 align:start position:0% backup it has no um they just shut it down<00:28:24.600> because<00:28:24.900> they<00:28:25.260> they<00:28:25.679> don't<00:28:25.919> want<00:28:26.100> it 00:28:26.210 --> 00:28:26.220 align:start position:0% down because they they don't want it 00:28:26.220 --> 00:28:27.950 align:start position:0% down because they they don't want it running<00:28:26.400> all<00:28:26.700> night<00:28:26.880> well<00:28:27.360> obviously<00:28:27.840> now 00:28:27.950 --> 00:28:27.960 align:start position:0% running all night well obviously now 00:28:27.960 --> 00:28:29.810 align:start position:0% running all night well obviously now they're<00:28:28.200> getting<00:28:28.380> slashed<00:28:29.100> and<00:28:29.279> so<00:28:29.460> you<00:28:29.640> have 00:28:29.810 --> 00:28:29.820 align:start position:0% they're getting slashed and so you have 00:28:29.820 --> 00:28:30.830 align:start position:0% they're getting slashed and so you have a<00:28:29.880> lot<00:28:29.940> of<00:28:30.059> these<00:28:30.240> people<00:28:30.360> who<00:28:30.480> don't<00:28:30.659> know 00:28:30.830 --> 00:28:30.840 align:start position:0% a lot of these people who don't know 00:28:30.840 --> 00:28:32.570 align:start position:0% a lot of these people who don't know about<00:28:30.960> these<00:28:31.320> things<00:28:31.440> you<00:28:31.860> know<00:28:32.159> how<00:28:32.279> to<00:28:32.400> set 00:28:32.570 --> 00:28:32.580 align:start position:0% about these things you know how to set 00:28:32.580 --> 00:28:34.250 align:start position:0% about these things you know how to set up<00:28:32.760> a<00:28:33.000> hardware<00:28:33.419> aren't<00:28:33.840> you<00:28:33.960> kind<00:28:34.140> of 00:28:34.250 --> 00:28:34.260 align:start position:0% up a hardware aren't you kind of 00:28:34.260 --> 00:28:36.350 align:start position:0% up a hardware aren't you kind of concerned<00:28:34.740> about<00:28:34.860> that<00:28:35.279> or<00:28:35.760> maybe<00:28:35.940> they<00:28:36.179> think 00:28:36.350 --> 00:28:36.360 align:start position:0% concerned about that or maybe they think 00:28:36.360 --> 00:28:38.269 align:start position:0% concerned about that or maybe they think I<00:28:36.600> want<00:28:36.779> to<00:28:36.900> set<00:28:36.960> up<00:28:37.140> two<00:28:37.380> they<00:28:37.679> use<00:28:37.860> the<00:28:38.039> same 00:28:38.269 --> 00:28:38.279 align:start position:0% I want to set up two they use the same 00:28:38.279 --> 00:28:41.210 align:start position:0% I want to set up two they use the same contract<00:28:38.820> addresses<00:28:39.299> and<00:28:39.840> two<00:28:40.440> and<00:28:40.740> boom<00:28:41.039> boom 00:28:41.210 --> 00:28:41.220 align:start position:0% contract addresses and two and boom boom 00:28:41.220 --> 00:28:42.649 align:start position:0% contract addresses and two and boom boom boom<00:28:41.400> they<00:28:41.520> start<00:28:41.700> getting<00:28:41.820> slashed<00:28:42.600> if<00:28:42.600> you 00:28:42.649 --> 00:28:42.659 align:start position:0% boom they start getting slashed if you 00:28:42.659 --> 00:28:44.390 align:start position:0% boom they start getting slashed if you can<00:28:42.840> too 00:28:44.390 --> 00:28:44.400 align:start position:0% can too 00:28:44.400 --> 00:28:48.409 align:start position:0% can too have<00:28:44.940> you<00:28:45.120> thought<00:28:45.299> of<00:28:45.600> uh<00:28:45.900> like 00:28:48.409 --> 00:28:48.419 align:start position:0% 00:28:48.419 --> 00:28:50.149 align:start position:0% yeah<00:28:48.840> that's<00:28:49.320> a<00:28:49.440> good<00:28:49.500> question<00:28:49.679> is<00:28:49.860> like<00:28:49.980> if 00:28:50.149 --> 00:28:50.159 align:start position:0% yeah that's a good question is like if 00:28:50.159 --> 00:28:52.190 align:start position:0% yeah that's a good question is like if we<00:28:50.279> do<00:28:50.340> make<00:28:50.520> it<00:28:50.640> easy<00:28:50.820> to<00:28:51.120> use<00:28:51.299> like<00:28:51.600> we<00:28:52.020> need 00:28:52.190 --> 00:28:52.200 align:start position:0% we do make it easy to use like we need 00:28:52.200 --> 00:28:53.690 align:start position:0% we do make it easy to use like we need to 00:28:53.690 --> 00:28:53.700 align:start position:0% to 00:28:53.700 --> 00:28:56.269 align:start position:0% to um also<00:28:54.539> make<00:28:54.840> make<00:28:55.200> it<00:28:55.500> very<00:28:55.679> clear<00:28:55.919> like 00:28:56.269 --> 00:28:56.279 align:start position:0% um also make make it very clear like 00:28:56.279 --> 00:28:58.909 align:start position:0% um also make make it very clear like what<00:28:56.580> they<00:28:56.820> need<00:28:57.000> to<00:28:57.120> do<00:28:57.360> and 00:28:58.909 --> 00:28:58.919 align:start position:0% what they need to do and 00:28:58.919 --> 00:29:02.149 align:start position:0% what they need to do and um<00:28:58.980> and<00:28:59.760> then<00:28:59.940> probably<00:29:00.480> also<00:29:01.020> make<00:29:01.380> it<00:29:01.919> very 00:29:02.149 --> 00:29:02.159 align:start position:0% um and then probably also make it very 00:29:02.159 --> 00:29:04.430 align:start position:0% um and then probably also make it very easy<00:29:02.400> for<00:29:02.700> them<00:29:02.940> to 00:29:04.430 --> 00:29:04.440 align:start position:0% easy for them to 00:29:04.440 --> 00:29:09.049 align:start position:0% easy for them to uh<00:29:05.279> like<00:29:05.520> stop<00:29:05.940> it<00:29:06.120> or<00:29:06.360> withdraw<00:29:06.960> or 00:29:09.049 --> 00:29:09.059 align:start position:0% uh like stop it or withdraw or 00:29:09.059 --> 00:29:11.870 align:start position:0% uh like stop it or withdraw or um<00:29:09.419> note<00:29:09.960> of<00:29:10.200> notify<00:29:10.679> them 00:29:11.870 --> 00:29:11.880 align:start position:0% um note of notify them 00:29:11.880 --> 00:29:12.950 align:start position:0% um note of notify them um<00:29:11.940> so<00:29:12.240> yeah<00:29:12.360> if<00:29:12.480> we're<00:29:12.600> going<00:29:12.720> to<00:29:12.779> make<00:29:12.900> it 00:29:12.950 --> 00:29:12.960 align:start position:0% um so yeah if we're going to make it 00:29:12.960 --> 00:29:14.510 align:start position:0% um so yeah if we're going to make it easy<00:29:13.140> for<00:29:13.320> people<00:29:13.500> to<00:29:13.679> onboard<00:29:13.919> we<00:29:14.159> also<00:29:14.340> need 00:29:14.510 --> 00:29:14.520 align:start position:0% easy for people to onboard we also need 00:29:14.520 --> 00:29:16.490 align:start position:0% easy for people to onboard we also need it<00:29:14.760> that's<00:29:15.299> a<00:29:15.539> great<00:29:15.720> point<00:29:15.900> we<00:29:16.140> need<00:29:16.260> to<00:29:16.380> make 00:29:16.490 --> 00:29:16.500 align:start position:0% it that's a great point we need to make 00:29:16.500 --> 00:29:18.590 align:start position:0% it that's a great point we need to make it<00:29:16.620> easy<00:29:16.740> for<00:29:16.980> them<00:29:17.100> to<00:29:17.460> kind<00:29:17.640> of<00:29:17.700> get<00:29:18.120> off<00:29:18.299> or 00:29:18.590 --> 00:29:18.600 align:start position:0% it easy for them to kind of get off or 00:29:18.600 --> 00:29:23.650 align:start position:0% it easy for them to kind of get off or help<00:29:18.779> them<00:29:18.960> get<00:29:19.140> off 00:29:23.650 --> 00:29:23.660 align:start position:0% 00:29:23.660 --> 00:29:41.810 align:start position:0% [Music] 00:29:41.810 --> 00:29:41.820 align:start position:0% 00:29:41.820 --> 00:29:44.090 align:start position:0% yeah<00:29:42.120> I<00:29:42.179> think<00:29:42.299> the<00:29:42.419> quick<00:29:42.600> answer<00:29:42.840> is<00:29:43.080> I<00:29:43.380> would 00:29:44.090 --> 00:29:44.100 align:start position:0% yeah I think the quick answer is I would 00:29:44.100 --> 00:29:45.649 align:start position:0% yeah I think the quick answer is I would um<00:29:44.460> in<00:29:44.820> the<00:29:44.940> app<00:29:45.000> we're<00:29:45.179> going<00:29:45.360> to<00:29:45.419> just<00:29:45.539> make 00:29:45.649 --> 00:29:45.659 align:start position:0% um in the app we're going to just make 00:29:45.659 --> 00:29:47.930 align:start position:0% um in the app we're going to just make it<00:29:45.840> like<00:29:46.020> super<00:29:46.620> obvious<00:29:47.039> like<00:29:47.640> lots<00:29:47.880> of 00:29:47.930 --> 00:29:47.940 align:start position:0% it like super obvious like lots of 00:29:47.940 --> 00:29:49.789 align:start position:0% it like super obvious like lots of warnings<00:29:48.240> like<00:29:48.419> hey<00:29:48.600> this<00:29:48.840> need<00:29:49.080> you<00:29:49.380> need<00:29:49.679> to 00:29:49.789 --> 00:29:49.799 align:start position:0% warnings like hey this need you need to 00:29:49.799 --> 00:29:51.049 align:start position:0% warnings like hey this need you need to have<00:29:49.919> you're<00:29:50.100> an<00:29:50.220> entered<00:29:50.520> on<00:29:50.640> you<00:29:50.880> need<00:29:50.940> to 00:29:51.049 --> 00:29:51.059 align:start position:0% have you're an entered on you need to 00:29:51.059 --> 00:29:52.789 align:start position:0% have you're an entered on you need to have<00:29:51.179> this<00:29:51.360> computer<00:29:51.539> up 00:29:52.789 --> 00:29:52.799 align:start position:0% have this computer up 00:29:52.799 --> 00:29:53.649 align:start position:0% have this computer up um 00:29:53.649 --> 00:29:53.659 align:start position:0% um 00:29:53.659 --> 00:29:56.690 align:start position:0% um and<00:29:54.659> yeah<00:29:54.960> hopefully<00:29:55.380> it's<00:29:55.620> our<00:29:56.220> solution's<00:29:56.640> a 00:29:56.690 --> 00:29:56.700 align:start position:0% and yeah hopefully it's our solution's a 00:29:56.700 --> 00:29:57.950 align:start position:0% and yeah hopefully it's our solution's a lot<00:29:56.760> better<00:29:56.880> than<00:29:57.059> the<00:29:57.240> Alternatives<00:29:57.600> like 00:29:57.950 --> 00:29:57.960 align:start position:0% lot better than the Alternatives like 00:29:57.960 --> 00:29:59.690 align:start position:0% lot better than the Alternatives like hopefully<00:29:58.380> we're<00:29:58.559> way<00:29:58.740> better<00:29:58.919> at<00:29:59.159> notifying 00:29:59.690 --> 00:29:59.700 align:start position:0% hopefully we're way better at notifying 00:29:59.700 --> 00:30:00.889 align:start position:0% hopefully we're way better at notifying people 00:30:00.889 --> 00:30:00.899 align:start position:0% people 00:30:00.899 --> 00:30:02.990 align:start position:0% people um<00:30:00.960> when<00:30:01.620> their<00:30:01.919> node<00:30:02.100> does<00:30:02.340> go<00:30:02.520> down<00:30:02.700> things 00:30:02.990 --> 00:30:03.000 align:start position:0% um when their node does go down things 00:30:03.000 --> 00:30:09.169 align:start position:0% um when their node does go down things like<00:30:03.179> that 00:30:09.169 --> 00:30:09.179 align:start position:0% 00:30:09.179 --> 00:30:12.289 align:start position:0% yeah<00:30:09.299> no<00:30:09.840> no<00:30:09.919> incentives<00:30:10.919> right<00:30:11.159> now 00:30:12.289 --> 00:30:12.299 align:start position:0% yeah no no incentives right now 00:30:12.299 --> 00:30:14.570 align:start position:0% yeah no no incentives right now for<00:30:12.659> for<00:30:12.720> a<00:30:13.080> non-eth<00:30:13.500> non-validator<00:30:14.279> note 00:30:14.570 --> 00:30:14.580 align:start position:0% for for a non-eth non-validator note 00:30:14.580 --> 00:30:16.250 align:start position:0% for for a non-eth non-validator note yeah 00:30:16.250 --> 00:30:16.260 align:start position:0% yeah 00:30:16.260 --> 00:30:20.149 align:start position:0% yeah so<00:30:16.740> and<00:30:17.399> that's<00:30:17.700> a<00:30:17.880> great<00:30:18.000> Point<00:30:18.120> like<00:30:18.360> if 00:30:20.149 --> 00:30:20.159 align:start position:0% so and that's a great Point like if 00:30:20.159 --> 00:30:21.169 align:start position:0% so and that's a great Point like if um 00:30:21.169 --> 00:30:21.179 align:start position:0% um 00:30:21.179 --> 00:30:23.330 align:start position:0% um if<00:30:21.539> you're<00:30:21.659> someone<00:30:21.899> who 00:30:23.330 --> 00:30:23.340 align:start position:0% if you're someone who 00:30:23.340 --> 00:30:26.210 align:start position:0% if you're someone who um<00:30:23.399> like<00:30:23.820> the<00:30:24.419> SSD<00:30:24.960> is<00:30:25.260> like<00:30:25.440> a<00:30:25.620> big<00:30:25.799> uh 00:30:26.210 --> 00:30:26.220 align:start position:0% um like the SSD is like a big uh 00:30:26.220 --> 00:30:28.570 align:start position:0% um like the SSD is like a big uh commitment<00:30:26.580> for<00:30:27.179> you<00:30:27.360> or<00:30:27.600> purchase<00:30:28.020> like 00:30:28.570 --> 00:30:28.580 align:start position:0% commitment for you or purchase like 00:30:28.580 --> 00:30:30.950 align:start position:0% commitment for you or purchase like maybe<00:30:29.580> running<00:30:29.880> a<00:30:30.120> full<00:30:30.360> node<00:30:30.600> I<00:30:30.720> don't<00:30:30.840> want 00:30:30.950 --> 00:30:30.960 align:start position:0% maybe running a full node I don't want 00:30:30.960 --> 00:30:32.269 align:start position:0% maybe running a full node I don't want to<00:30:31.020> discourage<00:30:31.320> you<00:30:31.440> but<00:30:31.559> maybe<00:30:31.740> it's<00:30:31.919> not<00:30:32.100> the 00:30:32.269 --> 00:30:32.279 align:start position:0% to discourage you but maybe it's not the 00:30:32.279 --> 00:30:34.610 align:start position:0% to discourage you but maybe it's not the best<00:30:32.520> use<00:30:32.820> of<00:30:33.059> of<00:30:33.480> like<00:30:34.020> your<00:30:34.260> money<00:30:34.440> or 00:30:34.610 --> 00:30:34.620 align:start position:0% best use of of like your money or 00:30:34.620 --> 00:30:36.950 align:start position:0% best use of of like your money or resources<00:30:35.039> like<00:30:35.340> the<00:30:35.640> there<00:30:36.120> are<00:30:36.299> there<00:30:36.539> is<00:30:36.659> no 00:30:36.950 --> 00:30:36.960 align:start position:0% resources like the there are there is no 00:30:36.960 --> 00:30:38.930 align:start position:0% resources like the there are there is no like<00:30:37.200> direct<00:30:37.520> incentive<00:30:38.520> at<00:30:38.700> the<00:30:38.820> moment 00:30:38.930 --> 00:30:38.940 align:start position:0% like direct incentive at the moment 00:30:38.940 --> 00:30:41.330 align:start position:0% like direct incentive at the moment other<00:30:39.240> than<00:30:39.480> obviously<00:30:40.380> like<00:30:40.740> making<00:30:41.159> sure 00:30:41.330 --> 00:30:41.340 align:start position:0% other than obviously like making sure 00:30:41.340 --> 00:30:42.529 align:start position:0% other than obviously like making sure ethereum 00:30:42.529 --> 00:30:42.539 align:start position:0% ethereum 00:30:42.539 --> 00:30:45.830 align:start position:0% ethereum um<00:30:42.659> works<00:30:43.440> and<00:30:43.559> stays<00:30:43.919> up<00:30:44.039> so 00:30:45.830 --> 00:30:45.840 align:start position:0% um works and stays up so 00:30:45.840 --> 00:30:48.169 align:start position:0% um works and stays up so um<00:30:45.899> it<00:30:46.380> is<00:30:46.500> yeah<00:30:47.159> that's<00:30:47.460> a<00:30:47.640> that's<00:30:47.880> a<00:30:48.000> great 00:30:48.169 --> 00:30:48.179 align:start position:0% um it is yeah that's a that's a great 00:30:48.179 --> 00:30:50.510 align:start position:0% um it is yeah that's a that's a great point 00:30:50.510 --> 00:30:50.520 align:start position:0% point 00:30:50.520 --> 00:30:53.750 align:start position:0% point yep 00:30:53.750 --> 00:30:53.760 align:start position:0% 00:30:53.760 --> 00:30:55.029 align:start position:0% [Music] 00:30:55.029 --> 00:30:55.039 align:start position:0% [Music] 00:30:55.039 --> 00:30:57.470 align:start position:0% [Music] it's<00:30:56.039> from<00:30:56.220> personal<00:30:56.460> experience<00:30:56.940> like<00:30:57.179> when 00:30:57.470 --> 00:30:57.480 align:start position:0% it's from personal experience like when 00:30:57.480 --> 00:30:59.630 align:start position:0% it's from personal experience like when the<00:30:57.659> defense<00:30:58.080> just<00:30:58.440> launched<00:30:58.740> it<00:30:59.220> was<00:30:59.460> also 00:30:59.630 --> 00:30:59.640 align:start position:0% the defense just launched it was also 00:30:59.640 --> 00:31:03.960 align:start position:0% the defense just launched it was also one<00:30:59.880> of<00:31:00.059> the<00:31:00.120> first<00:31:00.720> uh 00:31:03.960 --> 00:31:03.970 align:start position:0% 00:31:03.970 --> 00:31:07.190 align:start position:0% [Music] 00:31:07.190 --> 00:31:07.200 align:start position:0% [Music] 00:31:07.200 --> 00:31:08.220 align:start position:0% [Music] um 00:31:08.220 --> 00:31:08.230 align:start position:0% um 00:31:08.230 --> 00:31:26.889 align:start position:0% um [Music] 00:31:26.889 --> 00:31:26.899 align:start position:0% 00:31:26.899 --> 00:31:29.330 align:start position:0% I<00:31:27.899> think<00:31:28.020> it's<00:31:28.140> more<00:31:28.380> of<00:31:28.500> a<00:31:28.559> challenge<00:31:28.740> but<00:31:29.100> how 00:31:29.330 --> 00:31:29.340 align:start position:0% I think it's more of a challenge but how 00:31:29.340 --> 00:31:31.490 align:start position:0% I think it's more of a challenge but how do<00:31:29.520> you<00:31:29.640> build<00:31:29.880> a 00:31:31.490 --> 00:31:31.500 align:start position:0% do you build a 00:31:31.500 --> 00:31:32.430 align:start position:0% do you build a one<00:31:31.980> of<00:31:32.220> you 00:31:32.430 --> 00:31:32.440 align:start position:0% one of you 00:31:32.440 --> 00:31:35.630 align:start position:0% one of you [Music] 00:31:35.630 --> 00:31:35.640 align:start position:0% 00:31:35.640 --> 00:31:39.169 align:start position:0% know 00:31:39.169 --> 00:31:39.179 align:start position:0% 00:31:39.179 --> 00:31:55.909 align:start position:0% uh 00:31:55.909 --> 00:31:55.919 align:start position:0% 00:31:55.919 --> 00:31:57.710 align:start position:0% whatever<00:31:56.220> it<00:31:56.460> is 00:31:57.710 --> 00:31:57.720 align:start position:0% whatever it is 00:31:57.720 --> 00:32:00.110 align:start position:0% whatever it is yeah<00:31:58.260> I<00:31:58.440> mean<00:31:58.679> certainly<00:31:59.399> we<00:31:59.640> want<00:31:59.820> to<00:31:59.940> make<00:32:00.000> it 00:32:00.110 --> 00:32:00.120 align:start position:0% yeah I mean certainly we want to make it 00:32:00.120 --> 00:32:02.570 align:start position:0% yeah I mean certainly we want to make it as<00:32:00.240> user-friendly<00:32:00.779> as<00:32:00.899> possible<00:32:01.260> and<00:32:01.679> we<00:32:02.340> know 00:32:02.570 --> 00:32:02.580 align:start position:0% as user-friendly as possible and we know 00:32:02.580 --> 00:32:04.850 align:start position:0% as user-friendly as possible and we know one<00:32:02.760> thing<00:32:02.880> we<00:32:03.299> have<00:32:03.659> thought<00:32:04.380> about<00:32:04.440> is<00:32:04.679> like 00:32:04.850 --> 00:32:04.860 align:start position:0% one thing we have thought about is like 00:32:04.860 --> 00:32:06.710 align:start position:0% one thing we have thought about is like letting<00:32:05.159> users<00:32:05.399> opt<00:32:05.640> into<00:32:05.820> automatic<00:32:06.419> updates 00:32:06.710 --> 00:32:06.720 align:start position:0% letting users opt into automatic updates 00:32:06.720 --> 00:32:09.470 align:start position:0% letting users opt into automatic updates for<00:32:06.899> their<00:32:07.080> nodes<00:32:07.320> so<00:32:08.000> wherever<00:32:09.000> possible 00:32:09.470 --> 00:32:09.480 align:start position:0% for their nodes so wherever possible 00:32:09.480 --> 00:32:12.289 align:start position:0% for their nodes so wherever possible they<00:32:09.779> don't<00:32:09.960> need<00:32:10.200> to<00:32:10.380> need<00:32:10.799> to<00:32:10.919> do<00:32:11.039> anything 00:32:12.289 --> 00:32:12.299 align:start position:0% they don't need to need to do anything 00:32:12.299 --> 00:32:13.610 align:start position:0% they don't need to need to do anything um 00:32:13.610 --> 00:32:13.620 align:start position:0% um 00:32:13.620 --> 00:32:15.529 align:start position:0% um and<00:32:14.340> I<00:32:14.580> think<00:32:14.700> that<00:32:14.820> yeah<00:32:15.000> that's<00:32:15.299> that's 00:32:15.529 --> 00:32:15.539 align:start position:0% and I think that yeah that's that's 00:32:15.539 --> 00:32:17.269 align:start position:0% and I think that yeah that's that's probably<00:32:15.840> a<00:32:16.140> big<00:32:16.200> part<00:32:16.440> of<00:32:16.620> of<00:32:16.860> running<00:32:17.039> your 00:32:17.269 --> 00:32:17.279 align:start position:0% probably a big part of of running your 00:32:17.279 --> 00:32:18.830 align:start position:0% probably a big part of of running your Note<00:32:17.460> is<00:32:17.700> yeah<00:32:17.940> just<00:32:18.299> doing<00:32:18.419> those<00:32:18.600> updates 00:32:18.830 --> 00:32:18.840 align:start position:0% Note is yeah just doing those updates 00:32:18.840 --> 00:32:20.090 align:start position:0% Note is yeah just doing those updates and<00:32:19.080> then<00:32:19.200> having<00:32:19.440> some<00:32:19.740> sort<00:32:19.860> of<00:32:19.980> like 00:32:20.090 --> 00:32:20.100 align:start position:0% and then having some sort of like 00:32:20.100 --> 00:32:21.409 align:start position:0% and then having some sort of like alerting 00:32:21.409 --> 00:32:21.419 align:start position:0% alerting 00:32:21.419 --> 00:32:22.190 align:start position:0% alerting um 00:32:22.190 --> 00:32:22.200 align:start position:0% um 00:32:22.200 --> 00:32:24.230 align:start position:0% um in<00:32:22.799> terms<00:32:23.039> of<00:32:23.159> like<00:32:23.460> if<00:32:23.760> some<00:32:23.940> some<00:32:24.120> other 00:32:24.230 --> 00:32:24.240 align:start position:0% in terms of like if some some other 00:32:24.240 --> 00:32:26.029 align:start position:0% in terms of like if some some other problem<00:32:24.480> were<00:32:24.720> to<00:32:24.840> happen<00:32:25.020> like<00:32:25.679> we<00:32:25.799> would<00:32:25.919> try 00:32:26.029 --> 00:32:26.039 align:start position:0% problem were to happen like we would try 00:32:26.039 --> 00:32:28.310 align:start position:0% problem were to happen like we would try to<00:32:26.159> diagnose<00:32:26.520> it<00:32:26.640> as<00:32:26.760> best<00:32:26.940> we<00:32:27.059> can<00:32:27.240> but 00:32:28.310 --> 00:32:28.320 align:start position:0% to diagnose it as best we can but 00:32:28.320 --> 00:32:29.690 align:start position:0% to diagnose it as best we can but um 00:32:29.690 --> 00:32:29.700 align:start position:0% um 00:32:29.700 --> 00:32:32.149 align:start position:0% um I<00:32:30.120> suppose<00:32:30.419> that<00:32:30.720> I<00:32:31.020> like 00:32:32.149 --> 00:32:32.159 align:start position:0% I suppose that I like 00:32:32.159 --> 00:32:34.549 align:start position:0% I suppose that I like for<00:32:32.399> an<00:32:32.640> issue<00:32:32.880> we<00:32:33.059> can't<00:32:33.179> diagnose<00:32:33.659> I<00:32:34.020> yeah<00:32:34.320> I 00:32:34.549 --> 00:32:34.559 align:start position:0% for an issue we can't diagnose I yeah I 00:32:34.559 --> 00:32:36.169 align:start position:0% for an issue we can't diagnose I yeah I don't<00:32:34.620> have<00:32:34.740> an<00:32:34.860> answer<00:32:34.980> but<00:32:35.580> it's<00:32:35.880> it's 00:32:36.169 --> 00:32:36.179 align:start position:0% don't have an answer but it's it's 00:32:36.179 --> 00:32:38.149 align:start position:0% don't have an answer but it's it's something<00:32:36.360> I'll<00:32:36.659> definitely<00:32:37.320> um<00:32:37.380> uh<00:32:37.860> keep<00:32:38.039> in 00:32:38.149 --> 00:32:38.159 align:start position:0% something I'll definitely um uh keep in 00:32:38.159 --> 00:32:42.470 align:start position:0% something I'll definitely um uh keep in mind 00:32:42.470 --> 00:32:42.480 align:start position:0% 00:32:42.480 --> 00:32:49.810 align:start position:0% [Music] 00:32:49.810 --> 00:32:49.820 align:start position:0% 00:32:49.820 --> 00:32:52.149 align:start position:0% [Music] 00:32:52.149 --> 00:32:52.159 align:start position:0% [Music] 00:32:52.159 --> 00:32:54.710 align:start position:0% [Music] yeah<00:32:53.159> yeah<00:32:53.220> the<00:32:53.820> other<00:32:53.880> thing<00:32:54.299> I<00:32:54.360> do<00:32:54.480> want<00:32:54.600> to 00:32:54.710 --> 00:32:54.720 align:start position:0% yeah yeah the other thing I do want to 00:32:54.720 --> 00:32:57.590 align:start position:0% yeah yeah the other thing I do want to have<00:32:54.779> is<00:32:54.899> like<00:32:55.260> if<00:32:55.980> uh<00:32:56.640> I'll<00:32:56.880> like<00:32:57.179> show<00:32:57.419> the 00:32:57.590 --> 00:32:57.600 align:start position:0% have is like if uh I'll like show the 00:32:57.600 --> 00:32:59.149 align:start position:0% have is like if uh I'll like show the command<00:32:57.899> that<00:32:58.080> nice<00:32:58.200> node<00:32:58.500> used<00:32:58.679> to<00:32:58.860> start<00:32:58.980> the 00:32:59.149 --> 00:32:59.159 align:start position:0% command that nice node used to start the 00:32:59.159 --> 00:33:00.470 align:start position:0% command that nice node used to start the node<00:32:59.340> so<00:32:59.460> you<00:32:59.580> can<00:32:59.700> just<00:32:59.760> copy<00:33:00.059> and<00:33:00.120> paste<00:33:00.419> that 00:33:00.470 --> 00:33:00.480 align:start position:0% node so you can just copy and paste that 00:33:00.480 --> 00:33:02.210 align:start position:0% node so you can just copy and paste that command<00:33:00.840> and<00:33:01.020> like<00:33:01.200> leave<00:33:01.500> the<00:33:01.740> app<00:33:01.860> if<00:33:02.100> you 00:33:02.210 --> 00:33:02.220 align:start position:0% command and like leave the app if you 00:33:02.220 --> 00:33:03.470 align:start position:0% command and like leave the app if you want<00:33:02.340> and<00:33:02.460> then<00:33:02.640> you<00:33:02.760> can<00:33:02.880> just<00:33:03.000> go<00:33:03.299> to<00:33:03.419> the 00:33:03.470 --> 00:33:03.480 align:start position:0% want and then you can just go to the 00:33:03.480 --> 00:33:05.450 align:start position:0% want and then you can just go to the command<00:33:03.779> line<00:33:03.960> and<00:33:04.260> yeah<00:33:04.860> that's<00:33:05.279> that's 00:33:05.450 --> 00:33:05.460 align:start position:0% command line and yeah that's that's 00:33:05.460 --> 00:33:06.850 align:start position:0% command line and yeah that's that's something<00:33:05.640> I<00:33:05.880> want<00:33:05.940> to<00:33:06.000> do<00:33:06.120> too<00:33:06.240> right<00:33:06.600> here 00:33:06.850 --> 00:33:06.860 align:start position:0% something I want to do too right here 00:33:06.860 --> 00:33:07.669 align:start position:0% something I want to do too right here [Music] 00:33:07.669 --> 00:33:07.679 align:start position:0% [Music] 00:33:07.679 --> 00:33:12.789 align:start position:0% [Music] um 00:33:12.789 --> 00:33:12.799 align:start position:0% 00:33:12.799 --> 00:33:16.160 align:start position:0% thank<00:33:13.799> you<00:33:13.860> so<00:33:13.980> much 00:33:16.160 --> 00:33:16.170 align:start position:0% 00:33:16.170 --> 00:33:29.840 align:start position:0% [Music] 00:33:29.840 --> 00:33:29.850 align:start position:0% 00:33:29.850 --> 00:33:37.690 align:start position:0% [Music] 00:33:37.690 --> 00:33:37.700 align:start position:0% 00:33:37.700 --> 00:33:40.430 align:start position:0% my<00:33:38.700> question<00:33:38.820> is<00:33:39.120> uh 00:33:40.430 --> 00:33:40.440 align:start position:0% my question is uh 00:33:40.440 --> 00:33:43.190 align:start position:0% my question is uh when<00:33:41.159> when<00:33:41.519> your<00:33:41.820> team<00:33:42.000> like<00:33:42.179> a<00:33:42.360> build<00:33:42.539> is<00:33:42.840> it's 00:33:43.190 --> 00:33:43.200 align:start position:0% when when your team like a build is it's 00:33:43.200 --> 00:33:45.169 align:start position:0% when when your team like a build is it's it's<00:33:43.260> based<00:33:43.980> on<00:33:43.980> like<00:33:44.159> uh<00:33:44.460> there<00:33:44.880> is<00:33:45.000> a 00:33:45.169 --> 00:33:45.179 align:start position:0% it's based on like uh there is a 00:33:45.179 --> 00:33:48.350 align:start position:0% it's based on like uh there is a reachers<00:33:45.659> behind<00:33:46.140> like<00:33:46.919> uh<00:33:47.159> for 00:33:48.350 --> 00:33:48.360 align:start position:0% reachers behind like uh for 00:33:48.360 --> 00:33:51.830 align:start position:0% reachers behind like uh for what<00:33:48.960> kind<00:33:49.140> of<00:33:49.260> age<00:33:49.620> or<00:33:50.039> or<00:33:50.279> what<00:33:50.519> what<00:33:50.640> is<00:33:51.000> uh 00:33:51.830 --> 00:33:51.840 align:start position:0% what kind of age or or what what is uh 00:33:51.840 --> 00:33:53.509 align:start position:0% what kind of age or or what what is uh um<00:33:51.960> this<00:33:52.200> kind<00:33:52.320> of<00:33:52.440> people<00:33:52.559> that<00:33:52.919> can't<00:33:53.159> afford 00:33:53.509 --> 00:33:53.519 align:start position:0% um this kind of people that can't afford 00:33:53.519 --> 00:33:55.070 align:start position:0% um this kind of people that can't afford like<00:33:53.700> that<00:33:53.880> this<00:33:54.179> is<00:33:54.299> easy<00:33:54.480> to<00:33:54.659> use<00:33:54.779> because 00:33:55.070 --> 00:33:55.080 align:start position:0% like that this is easy to use because 00:33:55.080 --> 00:33:58.190 align:start position:0% like that this is easy to use because even<00:33:55.500> if<00:33:55.860> this<00:33:56.039> is<00:33:56.159> easy<00:33:56.340> to<00:33:56.519> use<00:33:56.760> for<00:33:57.120> us<00:33:57.360> maybe 00:33:58.190 --> 00:33:58.200 align:start position:0% even if this is easy to use for us maybe 00:33:58.200 --> 00:34:00.950 align:start position:0% even if this is easy to use for us maybe that<00:33:59.100> kind<00:33:59.340> of<00:33:59.460> a<00:33:59.640> stance<00:33:59.880> and<00:34:00.240> it<00:34:00.360> selects<00:34:00.779> oh 00:34:00.950 --> 00:34:00.960 align:start position:0% that kind of a stance and it selects oh 00:34:00.960 --> 00:34:03.110 align:start position:0% that kind of a stance and it selects oh it's<00:34:01.140> like<00:34:01.320> option<00:34:01.740> all<00:34:01.919> the<00:34:02.100> stuff<00:34:02.279> that<00:34:02.880> we 00:34:03.110 --> 00:34:03.120 align:start position:0% it's like option all the stuff that we 00:34:03.120 --> 00:34:06.409 align:start position:0% it's like option all the stuff that we talk<00:34:03.539> for<00:34:03.840> uh<00:34:04.140> an<00:34:04.559> algorithm<00:34:04.980> or<00:34:05.640> even<00:34:05.880> our<00:34:06.179> job 00:34:06.409 --> 00:34:06.419 align:start position:0% talk for uh an algorithm or even our job 00:34:06.419 --> 00:34:07.549 align:start position:0% talk for uh an algorithm or even our job people 00:34:07.549 --> 00:34:07.559 align:start position:0% people 00:34:07.559 --> 00:34:11.149 align:start position:0% people t-shirt<00:34:08.099> behind<00:34:08.639> that<00:34:08.820> like<00:34:09.599> uh<00:34:09.960> this<00:34:10.679> is<00:34:10.859> like 00:34:11.149 --> 00:34:11.159 align:start position:0% t-shirt behind that like uh this is like 00:34:11.159 --> 00:34:13.310 align:start position:0% t-shirt behind that like uh this is like a<00:34:11.399> accurate<00:34:11.879> with<00:34:12.119> this 00:34:13.310 --> 00:34:13.320 align:start position:0% a accurate with this 00:34:13.320 --> 00:34:15.409 align:start position:0% a accurate with this um age<00:34:13.800> people<00:34:14.159> or<00:34:14.580> not<00:34:14.879> telling<00:34:15.179> the<00:34:15.300> people 00:34:15.409 --> 00:34:15.419 align:start position:0% um age people or not telling the people 00:34:15.419 --> 00:34:16.430 align:start position:0% um age people or not telling the people whatever 00:34:16.430 --> 00:34:16.440 align:start position:0% whatever 00:34:16.440 --> 00:34:19.430 align:start position:0% whatever okay<00:34:16.980> so<00:34:18.000> um<00:34:18.060> just<00:34:18.240> to<00:34:18.359> repeat<00:34:18.480> uh<00:34:19.020> for<00:34:19.260> the 00:34:19.430 --> 00:34:19.440 align:start position:0% okay so um just to repeat uh for the 00:34:19.440 --> 00:34:21.649 align:start position:0% okay so um just to repeat uh for the stream<00:34:20.399> um<00:34:20.460> it<00:34:21.240> sounds<00:34:21.359> like<00:34:21.540> there's 00:34:21.649 --> 00:34:21.659 align:start position:0% stream um it sounds like there's 00:34:21.659 --> 00:34:24.109 align:start position:0% stream um it sounds like there's concerns<00:34:22.200> that<00:34:22.500> uh<00:34:23.280> we<00:34:23.580> need<00:34:23.700> to<00:34:23.760> make<00:34:23.940> sure 00:34:24.109 --> 00:34:24.119 align:start position:0% concerns that uh we need to make sure 00:34:24.119 --> 00:34:26.930 align:start position:0% concerns that uh we need to make sure that<00:34:24.599> uh<00:34:25.139> if<00:34:25.379> it<00:34:25.500> is<00:34:25.619> super<00:34:25.740> easy<00:34:25.980> to<00:34:26.280> get<00:34:26.399> in<00:34:26.520> to 00:34:26.930 --> 00:34:26.940 align:start position:0% that uh if it is super easy to get in to 00:34:26.940 --> 00:34:30.649 align:start position:0% that uh if it is super easy to get in to get<00:34:27.419> started<00:34:27.720> that<00:34:28.200> uh<00:34:29.159> we<00:34:29.520> make 00:34:30.649 --> 00:34:30.659 align:start position:0% get started that uh we make 00:34:30.659 --> 00:34:33.530 align:start position:0% get started that uh we make either<00:34:30.960> some<00:34:31.260> guide<00:34:31.500> rails<00:34:31.919> or<00:34:32.159> some<00:34:32.399> some 00:34:33.530 --> 00:34:33.540 align:start position:0% either some guide rails or some some 00:34:33.540 --> 00:34:34.190 align:start position:0% either some guide rails or some some um 00:34:34.190 --> 00:34:34.200 align:start position:0% um 00:34:34.200 --> 00:34:36.290 align:start position:0% um just<00:34:34.440> make<00:34:34.560> it<00:34:34.800> the<00:34:35.040> user<00:34:35.520> aware<00:34:35.760> that<00:34:36.060> what 00:34:36.290 --> 00:34:36.300 align:start position:0% just make it the user aware that what 00:34:36.300 --> 00:34:38.570 align:start position:0% just make it the user aware that what they're<00:34:36.419> getting<00:34:36.599> into<00:34:36.839> and 00:34:38.570 --> 00:34:38.580 align:start position:0% they're getting into and 00:34:38.580 --> 00:34:39.470 align:start position:0% they're getting into and um 00:34:39.470 --> 00:34:39.480 align:start position:0% um 00:34:39.480 --> 00:34:41.270 align:start position:0% um so<00:34:39.960> yeah<00:34:40.139> I<00:34:40.379> mean<00:34:40.500> what<00:34:40.619> I'd<00:34:40.980> have<00:34:41.099> to<00:34:41.159> say 00:34:41.270 --> 00:34:41.280 align:start position:0% so yeah I mean what I'd have to say 00:34:41.280 --> 00:34:43.550 align:start position:0% so yeah I mean what I'd have to say those<00:34:41.460> concerns<00:34:41.879> is 00:34:43.550 --> 00:34:43.560 align:start position:0% those concerns is 00:34:43.560 --> 00:34:45.589 align:start position:0% those concerns is um<00:34:43.740> I<00:34:44.040> think<00:34:44.159> we<00:34:44.399> we<00:34:44.580> could<00:34:44.820> do<00:34:45.179> something 00:34:45.589 --> 00:34:45.599 align:start position:0% um I think we we could do something 00:34:45.599 --> 00:34:46.730 align:start position:0% um I think we we could do something where 00:34:46.730 --> 00:34:46.740 align:start position:0% where 00:34:46.740 --> 00:34:49.010 align:start position:0% where um<00:34:46.800> instead<00:34:47.639> of<00:34:47.700> letting<00:34:48.060> like<00:34:48.179> the<00:34:48.359> user<00:34:48.720> it's 00:34:49.010 --> 00:34:49.020 align:start position:0% um instead of letting like the user it's 00:34:49.020 --> 00:34:50.389 align:start position:0% um instead of letting like the user it's just<00:34:49.320> something<00:34:49.500> I<00:34:49.679> thought<00:34:49.800> of<00:34:49.919> now<00:34:50.099> like 00:34:50.389 --> 00:34:50.399 align:start position:0% just something I thought of now like 00:34:50.399 --> 00:34:52.730 align:start position:0% just something I thought of now like click<00:34:50.879> like<00:34:51.179> yes<00:34:51.480> yes<00:34:51.659> yes<00:34:51.720> yes<00:34:51.899> yes<00:34:52.139> and<00:34:52.619> then 00:34:52.730 --> 00:34:52.740 align:start position:0% click like yes yes yes yes yes and then 00:34:52.740 --> 00:34:54.829 align:start position:0% click like yes yes yes yes yes and then they're<00:34:52.859> good<00:34:53.040> to<00:34:53.159> go<00:34:53.220> like<00:34:53.399> deposit<00:34:54.359> maybe 00:34:54.829 --> 00:34:54.839 align:start position:0% they're good to go like deposit maybe 00:34:54.839 --> 00:34:56.930 align:start position:0% they're good to go like deposit maybe having<00:34:55.200> some<00:34:55.560> kind<00:34:55.740> of<00:34:55.859> like 00:34:56.930 --> 00:34:56.940 align:start position:0% having some kind of like 00:34:56.940 --> 00:34:58.849 align:start position:0% having some kind of like um<00:34:57.000> speed<00:34:57.599> bump<00:34:57.839> that<00:34:58.320> kind<00:34:58.440> of<00:34:58.619> thing<00:34:58.680> where 00:34:58.849 --> 00:34:58.859 align:start position:0% um speed bump that kind of thing where 00:34:58.859 --> 00:35:00.410 align:start position:0% um speed bump that kind of thing where like<00:34:59.040> they<00:34:59.220> have<00:34:59.339> to<00:34:59.580> either<00:34:59.880> like 00:35:00.410 --> 00:35:00.420 align:start position:0% like they have to either like 00:35:00.420 --> 00:35:03.950 align:start position:0% like they have to either like demonstrate<00:35:01.260> some<00:35:01.560> technical<00:35:02.040> uh 00:35:03.950 --> 00:35:03.960 align:start position:0% demonstrate some technical uh 00:35:03.960 --> 00:35:05.870 align:start position:0% demonstrate some technical uh um<00:35:04.080> knowledge<00:35:04.980> of<00:35:05.160> like<00:35:05.460> what<00:35:05.760> they're 00:35:05.870 --> 00:35:05.880 align:start position:0% um knowledge of like what they're 00:35:05.880 --> 00:35:08.030 align:start position:0% um knowledge of like what they're getting<00:35:06.060> and<00:35:06.300> then<00:35:06.480> getting<00:35:06.720> into<00:35:07.080> just<00:35:07.800> sort 00:35:08.030 --> 00:35:08.040 align:start position:0% getting and then getting into just sort 00:35:08.040 --> 00:35:10.430 align:start position:0% getting and then getting into just sort of<00:35:08.220> sort<00:35:08.460> of<00:35:08.520> like<00:35:08.640> maybe<00:35:08.820> basic<00:35:09.359> quiz<00:35:10.200> or 00:35:10.430 --> 00:35:10.440 align:start position:0% of sort of like maybe basic quiz or 00:35:10.440 --> 00:35:12.050 align:start position:0% of sort of like maybe basic quiz or something<00:35:10.619> like<00:35:10.920> that 00:35:12.050 --> 00:35:12.060 align:start position:0% something like that 00:35:12.060 --> 00:35:15.410 align:start position:0% something like that um<00:35:12.540> but<00:35:12.960> other<00:35:13.079> than<00:35:13.380> that<00:35:13.619> I<00:35:14.040> mean 00:35:15.410 --> 00:35:15.420 align:start position:0% um but other than that I mean 00:35:15.420 --> 00:35:18.950 align:start position:0% um but other than that I mean um<00:35:15.599> yeah<00:35:15.960> did<00:35:16.260> I<00:35:16.740> did<00:35:17.220> I<00:35:17.760> um<00:35:17.820> address<00:35:18.180> your 00:35:18.950 --> 00:35:18.960 align:start position:0% um yeah did I did I um address your 00:35:18.960 --> 00:35:21.109 align:start position:0% um yeah did I did I um address your concerns<00:35:19.260> was<00:35:19.680> there<00:35:19.800> anything<00:35:19.980> else<00:35:20.280> or<00:35:20.820> um 00:35:21.109 --> 00:35:21.119 align:start position:0% concerns was there anything else or um 00:35:21.119 --> 00:35:22.910 align:start position:0% concerns was there anything else or um okay<00:35:21.660> yeah<00:35:22.020> I<00:35:22.140> think<00:35:22.260> maybe<00:35:22.440> some<00:35:22.680> sort<00:35:22.800> of 00:35:22.910 --> 00:35:22.920 align:start position:0% okay yeah I think maybe some sort of 00:35:22.920 --> 00:35:24.050 align:start position:0% okay yeah I think maybe some sort of speed<00:35:23.040> bump<00:35:23.220> just<00:35:23.460> so<00:35:23.520> they<00:35:23.700> can't<00:35:23.760> click 00:35:24.050 --> 00:35:24.060 align:start position:0% speed bump just so they can't click 00:35:24.060 --> 00:35:25.790 align:start position:0% speed bump just so they can't click through<00:35:24.240> like<00:35:24.540> super<00:35:24.720> fast<00:35:25.020> and<00:35:25.440> get 00:35:25.790 --> 00:35:25.800 align:start position:0% through like super fast and get 00:35:25.800 --> 00:35:27.890 align:start position:0% through like super fast and get themselves<00:35:26.099> into<00:35:26.339> something<00:35:26.579> they<00:35:26.880> didn't<00:35:27.060> uh 00:35:27.890 --> 00:35:27.900 align:start position:0% themselves into something they didn't uh 00:35:27.900 --> 00:35:29.870 align:start position:0% themselves into something they didn't uh know<00:35:28.079> and<00:35:28.380> now<00:35:28.560> this<00:35:28.920> program<00:35:29.160> is<00:35:29.460> taking<00:35:29.640> up 00:35:29.870 --> 00:35:29.880 align:start position:0% know and now this program is taking up 00:35:29.880 --> 00:35:32.390 align:start position:0% know and now this program is taking up all<00:35:30.000> their<00:35:30.180> SSD<00:35:30.540> space<00:35:30.780> in<00:35:30.960> the<00:35:31.140> background 00:35:32.390 --> 00:35:32.400 align:start position:0% all their SSD space in the background 00:35:32.400 --> 00:35:33.230 align:start position:0% all their SSD space in the background um 00:35:33.230 --> 00:35:33.240 align:start position:0% um 00:35:33.240 --> 00:35:35.990 align:start position:0% um yeah<00:35:33.839> absolutely 00:35:35.990 --> 00:35:36.000 align:start position:0% yeah absolutely 00:35:36.000 --> 00:35:38.089 align:start position:0% yeah absolutely right<00:35:36.480> there<00:35:36.599> in<00:35:36.839> the<00:35:37.020> White 00:35:38.089 --> 00:35:38.099 align:start position:0% right there in the White 00:35:38.099 --> 00:35:40.370 align:start position:0% right there in the White uh<00:35:38.640> sweater<00:35:39.060> or<00:35:39.480> yeah<00:35:39.780> I<00:35:39.960> think<00:35:40.079> you<00:35:40.200> were 00:35:40.370 --> 00:35:40.380 align:start position:0% uh sweater or yeah I think you were 00:35:40.380 --> 00:35:50.270 align:start position:0% uh sweater or yeah I think you were first<00:35:40.560> but<00:35:40.800> blue<00:35:41.400> shirt 00:35:50.270 --> 00:35:50.280 align:start position:0% 00:35:50.280 --> 00:35:52.730 align:start position:0% um<00:35:50.339> so<00:35:50.880> if 00:35:52.730 --> 00:35:52.740 align:start position:0% um so if 00:35:52.740 --> 00:35:56.030 align:start position:0% um so if um<00:35:52.920> if<00:35:53.640> you<00:35:53.940> don't<00:35:54.060> have<00:35:54.180> any<00:35:54.740> and<00:35:55.740> you're<00:35:55.920> not 00:35:56.030 --> 00:35:56.040 align:start position:0% um if you don't have any and you're not 00:35:56.040 --> 00:35:58.790 align:start position:0% um if you don't have any and you're not staking<00:35:56.400> no<00:35:56.700> slashing<00:35:57.720> um<00:35:57.839> if<00:35:58.079> if<00:35:58.380> you're 00:35:58.790 --> 00:35:58.800 align:start position:0% staking no slashing um if if you're 00:35:58.800 --> 00:36:01.790 align:start position:0% staking no slashing um if if you're staking<00:35:59.160> with<00:35:59.520> nice<00:35:59.700> node<00:36:00.060> and<00:36:00.780> uh<00:36:01.500> your<00:36:01.619> node 00:36:01.790 --> 00:36:01.800 align:start position:0% staking with nice node and uh your node 00:36:01.800 --> 00:36:03.410 align:start position:0% staking with nice node and uh your node were<00:36:02.040> to<00:36:02.160> go<00:36:02.220> down<00:36:02.339> it<00:36:02.520> would<00:36:02.640> be<00:36:02.760> slash<00:36:03.119> just 00:36:03.410 --> 00:36:03.420 align:start position:0% were to go down it would be slash just 00:36:03.420 --> 00:36:13.310 align:start position:0% were to go down it would be slash just like<00:36:03.660> any<00:36:04.320> other<00:36:04.440> note 00:36:13.310 --> 00:36:13.320 align:start position:0% 00:36:13.320 --> 00:36:15.050 align:start position:0% that's<00:36:13.800> that's<00:36:13.859> a<00:36:14.220> great<00:36:14.280> question 00:36:15.050 --> 00:36:15.060 align:start position:0% that's that's a great question 00:36:15.060 --> 00:36:16.849 align:start position:0% that's that's a great question um his<00:36:15.240> question<00:36:15.480> was<00:36:15.780> could<00:36:16.260> this<00:36:16.440> be<00:36:16.560> a<00:36:16.740> web 00:36:16.849 --> 00:36:16.859 align:start position:0% um his question was could this be a web 00:36:16.859 --> 00:36:20.270 align:start position:0% um his question was could this be a web app<00:36:17.040> and 00:36:20.270 --> 00:36:20.280 align:start position:0% 00:36:20.280 --> 00:36:23.750 align:start position:0% um<00:36:20.400> and<00:36:20.880> I<00:36:21.540> I<00:36:21.839> don't<00:36:22.380> think<00:36:22.500> so<00:36:22.680> as<00:36:22.980> of<00:36:23.099> now<00:36:23.339> I 00:36:23.750 --> 00:36:23.760 align:start position:0% um and I I don't think so as of now I 00:36:23.760 --> 00:36:25.790 align:start position:0% um and I I don't think so as of now I think<00:36:23.880> uh 00:36:25.790 --> 00:36:25.800 align:start position:0% think uh 00:36:25.800 --> 00:36:28.370 align:start position:0% think uh uh<00:36:26.160> I<00:36:26.700> think<00:36:26.820> there<00:36:27.540> are<00:36:27.660> limitations<00:36:28.020> on<00:36:28.260> the 00:36:28.370 --> 00:36:28.380 align:start position:0% uh I think there are limitations on the 00:36:28.380 --> 00:36:30.950 align:start position:0% uh I think there are limitations on the browser<00:36:28.800> which<00:36:29.160> you<00:36:29.880> can't<00:36:30.060> basically<00:36:30.540> run<00:36:30.780> a 00:36:30.950 --> 00:36:30.960 align:start position:0% browser which you can't basically run a 00:36:30.960 --> 00:36:33.530 align:start position:0% browser which you can't basically run a command<00:36:31.260> a<00:36:32.220> web<00:36:32.460> page<00:36:32.640> can't<00:36:32.940> just<00:36:33.180> like<00:36:33.359> run 00:36:33.530 --> 00:36:33.540 align:start position:0% command a web page can't just like run 00:36:33.540 --> 00:36:35.510 align:start position:0% command a web page can't just like run an<00:36:33.780> arbitrary<00:36:34.140> command<00:36:34.500> on<00:36:34.740> your<00:36:34.980> your 00:36:35.510 --> 00:36:35.520 align:start position:0% an arbitrary command on your your 00:36:35.520 --> 00:36:37.310 align:start position:0% an arbitrary command on your your computer<00:36:35.820> but<00:36:36.420> like<00:36:36.780> an<00:36:36.960> installed 00:36:37.310 --> 00:36:37.320 align:start position:0% computer but like an installed 00:36:37.320 --> 00:36:39.349 align:start position:0% computer but like an installed application<00:36:37.800> can 00:36:39.349 --> 00:36:39.359 align:start position:0% application can 00:36:39.359 --> 00:36:41.390 align:start position:0% application can um<00:36:39.440> so 00:36:41.390 --> 00:36:41.400 align:start position:0% um so 00:36:41.400 --> 00:36:42.410 align:start position:0% um so um 00:36:42.410 --> 00:36:42.420 align:start position:0% um 00:36:42.420 --> 00:36:45.230 align:start position:0% um now<00:36:43.260> the<00:36:43.680> front<00:36:43.859> end<00:36:44.040> part<00:36:44.280> of<00:36:44.460> a<00:36:44.520> nice<00:36:44.640> node<00:36:44.940> we 00:36:45.230 --> 00:36:45.240 align:start position:0% now the front end part of a nice node we 00:36:45.240 --> 00:36:46.730 align:start position:0% now the front end part of a nice node we could<00:36:45.300> separate<00:36:45.660> that<00:36:45.839> out<00:36:46.020> and<00:36:46.260> put<00:36:46.440> that<00:36:46.560> as 00:36:46.730 --> 00:36:46.740 align:start position:0% could separate that out and put that as 00:36:46.740 --> 00:36:48.109 align:start position:0% could separate that out and put that as a<00:36:46.920> web<00:36:47.040> page 00:36:48.109 --> 00:36:48.119 align:start position:0% a web page 00:36:48.119 --> 00:36:51.710 align:start position:0% a web page um it's<00:36:49.079> actually<00:36:49.260> uh<00:36:50.520> it's<00:36:51.000> actually<00:36:51.180> like 00:36:51.710 --> 00:36:51.720 align:start position:0% um it's actually uh it's actually like 00:36:51.720 --> 00:36:53.990 align:start position:0% um it's actually uh it's actually like mostly<00:36:52.680> the<00:36:53.040> front<00:36:53.220> end<00:36:53.339> is<00:36:53.520> basically<00:36:53.760> a<00:36:53.940> web 00:36:53.990 --> 00:36:54.000 align:start position:0% mostly the front end is basically a web 00:36:54.000 --> 00:36:56.210 align:start position:0% mostly the front end is basically a web page<00:36:54.180> it's<00:36:54.480> basically<00:36:54.780> running<00:36:55.020> in 00:36:56.210 --> 00:36:56.220 align:start position:0% page it's basically running in 00:36:56.220 --> 00:36:58.609 align:start position:0% page it's basically running in um<00:36:56.280> chromium<00:36:57.060> there's<00:36:57.480> the<00:36:58.260> underlying 00:36:58.609 --> 00:36:58.619 align:start position:0% um chromium there's the underlying 00:36:58.619 --> 00:37:00.050 align:start position:0% um chromium there's the underlying architecture<00:36:58.980> for<00:36:59.099> a<00:36:59.339> nice<00:36:59.520> node<00:36:59.760> is<00:36:59.880> called 00:37:00.050 --> 00:37:00.060 align:start position:0% architecture for a nice node is called 00:37:00.060 --> 00:37:01.970 align:start position:0% architecture for a nice node is called electron<00:37:00.540> and<00:37:01.079> it<00:37:01.260> basically<00:37:01.500> downloads 00:37:01.970 --> 00:37:01.980 align:start position:0% electron and it basically downloads 00:37:01.980 --> 00:37:04.130 align:start position:0% electron and it basically downloads chromium<00:37:02.520> and<00:37:02.940> so<00:37:03.119> it's<00:37:03.300> it's<00:37:03.599> like<00:37:03.839> its<00:37:04.079> own 00:37:04.130 --> 00:37:04.140 align:start position:0% chromium and so it's it's like its own 00:37:04.140 --> 00:37:05.990 align:start position:0% chromium and so it's it's like its own little<00:37:04.260> web<00:37:04.500> browser<00:37:04.859> there<00:37:05.040> with<00:37:05.640> extra 00:37:05.990 --> 00:37:06.000 align:start position:0% little web browser there with extra 00:37:06.000 --> 00:37:08.750 align:start position:0% little web browser there with extra permissions<00:37:06.660> to<00:37:07.220> interface<00:37:08.220> with<00:37:08.339> operating 00:37:08.750 --> 00:37:08.760 align:start position:0% permissions to interface with operating 00:37:08.760 --> 00:37:11.329 align:start position:0% permissions to interface with operating system 00:37:11.329 --> 00:37:11.339 align:start position:0% 00:37:11.339 --> 00:37:13.609 align:start position:0% yeah 00:37:13.609 --> 00:37:13.619 align:start position:0% yeah 00:37:13.619 --> 00:37:17.810 align:start position:0% yeah any<00:37:14.220> other<00:37:14.640> questions 00:37:17.810 --> 00:37:17.820 align:start position:0% 00:37:17.820 --> 00:37:22.010 align:start position:0% here<00:37:18.240> again 00:37:22.010 --> 00:37:22.020 align:start position:0% 00:37:22.020 --> 00:37:24.890 align:start position:0% uh<00:37:22.680> right<00:37:22.859> now<00:37:23.040> uh<00:37:23.579> no<00:37:23.760> plans<00:37:24.060> I<00:37:24.599> want<00:37:24.720> to<00:37:24.780> stay 00:37:24.890 --> 00:37:24.900 align:start position:0% uh right now uh no plans I want to stay 00:37:24.900 --> 00:37:27.890 align:start position:0% uh right now uh no plans I want to stay open<00:37:25.020> sources<00:37:25.500> as<00:37:25.980> long<00:37:26.160> as<00:37:26.280> possible<00:37:26.720> we<00:37:27.720> have 00:37:27.890 --> 00:37:27.900 align:start position:0% open sources as long as possible we have 00:37:27.900 --> 00:37:31.550 align:start position:0% open sources as long as possible we have been<00:37:28.020> supported<00:37:28.500> by<00:37:29.119> first<00:37:30.119> East<00:37:30.420> acre<00:37:30.900> in<00:37:31.380> a 00:37:31.550 --> 00:37:31.560 align:start position:0% been supported by first East acre in a 00:37:31.560 --> 00:37:35.990 align:start position:0% been supported by first East acre in a Sierra<00:37:31.859> CLR<00:37:32.579> fund<00:37:32.940> and<00:37:33.839> then<00:37:34.020> get<00:37:34.320> coin<00:37:35.000> two 00:37:35.990 --> 00:37:36.000 align:start position:0% Sierra CLR fund and then get coin two 00:37:36.000 --> 00:37:39.170 align:start position:0% Sierra CLR fund and then get coin two rounds<00:37:36.359> of<00:37:36.540> get<00:37:36.960> coin<00:37:37.380> and<00:37:38.220> then<00:37:38.400> we<00:37:38.880> we 00:37:39.170 --> 00:37:39.180 align:start position:0% rounds of get coin and then we we 00:37:39.180 --> 00:37:42.410 align:start position:0% rounds of get coin and then we we recently<00:37:39.599> got<00:37:39.900> a<00:37:40.500> grant<00:37:40.740> from<00:37:41.040> City<00:37:41.280> Dao<00:37:41.820> which 00:37:42.410 --> 00:37:42.420 align:start position:0% recently got a grant from City Dao which 00:37:42.420 --> 00:37:44.810 align:start position:0% recently got a grant from City Dao which funded<00:37:42.839> the<00:37:43.320> like<00:37:43.680> improved<00:37:44.220> onboarding 00:37:44.810 --> 00:37:44.820 align:start position:0% funded the like improved onboarding 00:37:44.820 --> 00:37:47.510 align:start position:0% funded the like improved onboarding experience<00:37:45.180> that<00:37:45.780> I<00:37:45.960> showed<00:37:46.200> you<00:37:46.260> all<00:37:46.380> today 00:37:47.510 --> 00:37:47.520 align:start position:0% experience that I showed you all today 00:37:47.520 --> 00:37:48.530 align:start position:0% experience that I showed you all today um 00:37:48.530 --> 00:37:48.540 align:start position:0% um 00:37:48.540 --> 00:37:51.410 align:start position:0% um and<00:37:49.320> then<00:37:49.560> hopefully<00:37:50.400> we'll<00:37:50.820> get<00:37:51.000> more<00:37:51.119> grants 00:37:51.410 --> 00:37:51.420 align:start position:0% and then hopefully we'll get more grants 00:37:51.420 --> 00:37:55.370 align:start position:0% and then hopefully we'll get more grants and<00:37:51.599> stay<00:37:51.780> open<00:37:51.960> source 00:37:55.370 --> 00:37:55.380 align:start position:0% 00:37:55.380 --> 00:38:02.870 align:start position:0% yep 00:38:02.870 --> 00:38:02.880 align:start position:0% 00:38:02.880 --> 00:38:06.050 align:start position:0% I've<00:38:03.780> seen<00:38:04.200> people<00:38:04.560> ask<00:38:04.859> that 00:38:06.050 --> 00:38:06.060 align:start position:0% I've seen people ask that 00:38:06.060 --> 00:38:07.250 align:start position:0% I've seen people ask that um 00:38:07.250 --> 00:38:07.260 align:start position:0% um 00:38:07.260 --> 00:38:10.730 align:start position:0% um I<00:38:07.680> think<00:38:07.800> if<00:38:08.400> there<00:38:09.240> there<00:38:09.839> could<00:38:10.079> be<00:38:10.200> in<00:38:10.680> the 00:38:10.730 --> 00:38:10.740 align:start position:0% I think if there there could be in the 00:38:10.740 --> 00:38:13.790 align:start position:0% I think if there there could be in the future<00:38:10.920> and<00:38:11.280> I<00:38:11.460> I<00:38:12.000> think<00:38:12.240> absolutely<00:38:12.720> I<00:38:13.619> think 00:38:13.790 --> 00:38:13.800 align:start position:0% future and I I think absolutely I think 00:38:13.800 --> 00:38:15.950 align:start position:0% future and I I think absolutely I think there<00:38:14.339> are<00:38:14.460> lots<00:38:14.880> of 00:38:15.950 --> 00:38:15.960 align:start position:0% there are lots of 00:38:15.960 --> 00:38:18.349 align:start position:0% there are lots of um<00:38:16.020> groups<00:38:16.740> or<00:38:16.859> foundations 00:38:18.349 --> 00:38:18.359 align:start position:0% um groups or foundations 00:38:18.359 --> 00:38:19.670 align:start position:0% um groups or foundations um 00:38:19.670 --> 00:38:19.680 align:start position:0% um 00:38:19.680 --> 00:38:21.710 align:start position:0% um maybe<00:38:20.220> like<00:38:20.520> eat<00:38:20.700> steak<00:38:20.940> or<00:38:21.180> the<00:38:21.420> ethereum 00:38:21.710 --> 00:38:21.720 align:start position:0% maybe like eat steak or the ethereum 00:38:21.720 --> 00:38:23.150 align:start position:0% maybe like eat steak or the ethereum foundation<00:38:22.079> who<00:38:22.380> would 00:38:23.150 --> 00:38:23.160 align:start position:0% foundation who would 00:38:23.160 --> 00:38:26.150 align:start position:0% foundation who would provide<00:38:24.119> some<00:38:24.359> incentive<00:38:24.780> I<00:38:25.200> think 00:38:26.150 --> 00:38:26.160 align:start position:0% provide some incentive I think 00:38:26.160 --> 00:38:28.550 align:start position:0% provide some incentive I think the<00:38:26.640> limitation<00:38:27.060> here<00:38:27.240> is<00:38:27.420> probably<00:38:27.660> like<00:38:28.079> you 00:38:28.550 --> 00:38:28.560 align:start position:0% the limitation here is probably like you 00:38:28.560 --> 00:38:29.990 align:start position:0% the limitation here is probably like you need<00:38:28.680> to<00:38:28.859> prove<00:38:29.220> that<00:38:29.400> the<00:38:29.640> person<00:38:29.700> running 00:38:29.990 --> 00:38:30.000 align:start position:0% need to prove that the person running 00:38:30.000 --> 00:38:31.849 align:start position:0% need to prove that the person running the<00:38:30.240> node<00:38:30.420> is<00:38:30.599> a<00:38:30.780> human<00:38:30.900> or<00:38:31.380> that<00:38:31.680> perfect 00:38:31.849 --> 00:38:31.859 align:start position:0% the node is a human or that perfect 00:38:31.859 --> 00:38:35.210 align:start position:0% the node is a human or that perfect Humanity<00:38:32.400> civil<00:38:33.180> resistance<00:38:33.599> problem<00:38:33.780> so 00:38:35.210 --> 00:38:35.220 align:start position:0% Humanity civil resistance problem so 00:38:35.220 --> 00:38:36.589 align:start position:0% Humanity civil resistance problem so um 00:38:36.589 --> 00:38:36.599 align:start position:0% um 00:38:36.599 --> 00:38:38.329 align:start position:0% um I<00:38:36.900> haven't<00:38:37.079> thought<00:38:37.320> through<00:38:37.500> the<00:38:37.800> whole<00:38:38.040> like 00:38:38.329 --> 00:38:38.339 align:start position:0% I haven't thought through the whole like 00:38:38.339 --> 00:38:41.030 align:start position:0% I haven't thought through the whole like consequences<00:38:39.300> of<00:38:39.540> tying<00:38:39.900> your 00:38:41.030 --> 00:38:41.040 align:start position:0% consequences of tying your 00:38:41.040 --> 00:38:43.970 align:start position:0% consequences of tying your Humanity<00:38:41.880> ID<00:38:42.060> to<00:38:42.359> your<00:38:42.480> node<00:38:42.599> but<00:38:43.020> I<00:38:43.740> think 00:38:43.970 --> 00:38:43.980 align:start position:0% Humanity ID to your node but I think 00:38:43.980 --> 00:38:45.710 align:start position:0% Humanity ID to your node but I think with<00:38:44.640> that<00:38:44.880> people<00:38:45.240> would<00:38:45.480> give<00:38:45.599> out 00:38:45.710 --> 00:38:45.720 align:start position:0% with that people would give out 00:38:45.720 --> 00:38:47.270 align:start position:0% with that people would give out incentives 00:38:47.270 --> 00:38:47.280 align:start position:0% incentives 00:38:47.280 --> 00:38:48.410 align:start position:0% incentives um 00:38:48.410 --> 00:38:48.420 align:start position:0% um 00:38:48.420 --> 00:38:50.569 align:start position:0% um other<00:38:48.900> than<00:38:49.140> that<00:38:49.260> I<00:38:49.500> don't<00:38:49.560> know<00:38:49.740> uh<00:38:50.280> I<00:38:50.520> don't 00:38:50.569 --> 00:38:50.579 align:start position:0% other than that I don't know uh I don't 00:38:50.579 --> 00:38:51.770 align:start position:0% other than that I don't know uh I don't know<00:38:50.700> how<00:38:50.820> they<00:38:50.940> would<00:38:51.060> do<00:38:51.180> it<00:38:51.240> without<00:38:51.359> civil 00:38:51.770 --> 00:38:51.780 align:start position:0% know how they would do it without civil 00:38:51.780 --> 00:38:59.390 align:start position:0% know how they would do it without civil resistance<00:38:52.140> yeah 00:38:59.390 --> 00:38:59.400 align:start position:0% 00:38:59.400 --> 00:39:01.490 align:start position:0% uh<00:39:00.060> if<00:39:00.300> you're<00:39:00.480> not<00:39:00.660> staking<00:39:01.020> or<00:39:01.320> not 00:39:01.490 --> 00:39:01.500 align:start position:0% uh if you're not staking or not 00:39:01.500 --> 00:39:04.370 align:start position:0% uh if you're not staking or not validating<00:39:01.920> there<00:39:02.400> are<00:39:02.520> no<00:39:02.820> no<00:39:03.359> incentives<00:39:04.020> no 00:39:04.370 --> 00:39:04.380 align:start position:0% validating there are no no incentives no 00:39:04.380 --> 00:39:08.700 align:start position:0% validating there are no no incentives no yeah<00:39:04.859> no<00:39:05.220> monetary<00:39:05.760> Rewards 00:39:08.700 --> 00:39:08.710 align:start position:0% 00:39:08.710 --> 00:39:22.320 align:start position:0% [Music] 00:39:22.320 --> 00:39:22.330 align:start position:0% 00:39:22.330 --> 00:39:28.089 align:start position:0% [Music] 00:39:28.089 --> 00:39:28.099 align:start position:0% 00:39:28.099 --> 00:39:30.470 align:start position:0% yeah<00:39:29.099> yeah<00:39:29.099> I<00:39:29.460> mean<00:39:29.579> that's<00:39:29.760> something<00:39:30.060> I've 00:39:30.470 --> 00:39:30.480 align:start position:0% yeah yeah I mean that's something I've 00:39:30.480 --> 00:39:32.150 align:start position:0% yeah yeah I mean that's something I've thought<00:39:30.660> about<00:39:30.780> I<00:39:31.320> haven't<00:39:31.619> like<00:39:31.920> quite 00:39:32.150 --> 00:39:32.160 align:start position:0% thought about I haven't like quite 00:39:32.160 --> 00:39:34.730 align:start position:0% thought about I haven't like quite worked<00:39:32.400> on<00:39:32.520> now<00:39:32.700> but<00:39:33.119> uh<00:39:33.839> the<00:39:33.960> operating<00:39:34.320> like 00:39:34.730 --> 00:39:34.740 align:start position:0% worked on now but uh the operating like 00:39:34.740 --> 00:39:37.250 align:start position:0% worked on now but uh the operating like the<00:39:35.579> Apple<00:39:35.700> can<00:39:36.060> know<00:39:36.300> whether<00:39:36.780> you're<00:39:37.079> on 00:39:37.250 --> 00:39:37.260 align:start position:0% the Apple can know whether you're on 00:39:37.260 --> 00:39:39.349 align:start position:0% the Apple can know whether you're on battery<00:39:37.440> whether<00:39:37.920> you're<00:39:38.099> on<00:39:38.280> power<00:39:38.520> whether 00:39:39.349 --> 00:39:39.359 align:start position:0% battery whether you're on power whether 00:39:39.359 --> 00:39:41.810 align:start position:0% battery whether you're on power whether you're<00:39:39.480> on<00:39:39.660> Wi-Fi<00:39:39.960> ethernet 00:39:41.810 --> 00:39:41.820 align:start position:0% you're on Wi-Fi ethernet 00:39:41.820 --> 00:39:44.150 align:start position:0% you're on Wi-Fi ethernet um<00:39:42.300> uh<00:39:43.020> right<00:39:43.200> now<00:39:43.320> we<00:39:43.500> don't<00:39:43.619> have<00:39:43.740> like<00:39:43.920> any 00:39:44.150 --> 00:39:44.160 align:start position:0% um uh right now we don't have like any 00:39:44.160 --> 00:39:45.349 align:start position:0% um uh right now we don't have like any internet<00:39:44.339> speed<00:39:44.700> check<00:39:45.000> but<00:39:45.240> that's 00:39:45.349 --> 00:39:45.359 align:start position:0% internet speed check but that's 00:39:45.359 --> 00:39:47.210 align:start position:0% internet speed check but that's something<00:39:45.599> we<00:39:45.839> could<00:39:45.900> definitely<00:39:46.200> add<00:39:46.440> so<00:39:46.859> I 00:39:47.210 --> 00:39:47.220 align:start position:0% something we could definitely add so I 00:39:47.220 --> 00:39:48.890 align:start position:0% something we could definitely add so I want<00:39:47.339> to<00:39:47.520> I<00:39:47.700> I<00:39:47.880> do<00:39:48.180> in<00:39:48.359> the<00:39:48.420> long<00:39:48.480> term<00:39:48.599> I<00:39:48.780> do 00:39:48.890 --> 00:39:48.900 align:start position:0% want to I I do in the long term I do 00:39:48.900 --> 00:39:50.510 align:start position:0% want to I I do in the long term I do want<00:39:49.079> to<00:39:49.200> make<00:39:49.320> it<00:39:49.440> so<00:39:49.619> that<00:39:49.800> yeah<00:39:49.980> you<00:39:50.400> can 00:39:50.510 --> 00:39:50.520 align:start position:0% want to make it so that yeah you can 00:39:50.520 --> 00:39:52.970 align:start position:0% want to make it so that yeah you can close<00:39:51.180> your<00:39:51.420> laptop<00:39:51.660> a<00:39:51.900> bit<00:39:52.140> the<00:39:52.380> node<00:39:52.560> stops 00:39:52.970 --> 00:39:52.980 align:start position:0% close your laptop a bit the node stops 00:39:52.980 --> 00:39:55.370 align:start position:0% close your laptop a bit the node stops peacefully<00:39:53.520> wherever<00:39:54.480> you<00:39:54.660> go<00:39:54.780> next<00:39:54.960> you<00:39:55.200> open 00:39:55.370 --> 00:39:55.380 align:start position:0% peacefully wherever you go next you open 00:39:55.380 --> 00:39:57.170 align:start position:0% peacefully wherever you go next you open your<00:39:55.619> laptop<00:39:55.920> maybe<00:39:56.400> just<00:39:56.579> plug<00:39:56.760> it<00:39:56.880> in<00:39:57.000> you 00:39:57.170 --> 00:39:57.180 align:start position:0% your laptop maybe just plug it in you 00:39:57.180 --> 00:39:59.569 align:start position:0% your laptop maybe just plug it in you eat<00:39:57.359> dinner<00:39:57.540> and<00:39:57.780> it's<00:39:57.900> it's<00:39:58.260> sinking<00:39:58.740> like 00:39:59.569 --> 00:39:59.579 align:start position:0% eat dinner and it's it's sinking like 00:39:59.579 --> 00:40:00.829 align:start position:0% eat dinner and it's it's sinking like while<00:39:59.940> you're 00:40:00.829 --> 00:40:00.839 align:start position:0% while you're 00:40:00.839 --> 00:40:03.770 align:start position:0% while you're uh<00:40:01.619> yeah<00:40:01.920> and<00:40:02.400> then<00:40:02.520> we'll<00:40:02.760> also<00:40:03.359> potentially 00:40:03.770 --> 00:40:03.780 align:start position:0% uh yeah and then we'll also potentially 00:40:03.780 --> 00:40:05.150 align:start position:0% uh yeah and then we'll also potentially like<00:40:04.079> you<00:40:04.320> get<00:40:04.440> we<00:40:04.680> could<00:40:04.740> have<00:40:04.859> a<00:40:04.980> setting 00:40:05.150 --> 00:40:05.160 align:start position:0% like you get we could have a setting 00:40:05.160 --> 00:40:07.190 align:start position:0% like you get we could have a setting like<00:40:05.280> while<00:40:05.460> you're<00:40:05.640> while<00:40:05.880> I'm<00:40:06.060> working 00:40:07.190 --> 00:40:07.200 align:start position:0% like while you're while I'm working 00:40:07.200 --> 00:40:09.410 align:start position:0% like while you're while I'm working don't<00:40:07.800> use<00:40:08.040> resources<00:40:08.579> like<00:40:08.820> just<00:40:09.000> run<00:40:09.180> in<00:40:09.359> the 00:40:09.410 --> 00:40:09.420 align:start position:0% don't use resources like just run in the 00:40:09.420 --> 00:40:11.510 align:start position:0% don't use resources like just run in the background<00:40:09.660> or<00:40:09.960> like<00:40:10.320> just<00:40:10.560> pause<00:40:10.920> while<00:40:11.280> I'm 00:40:11.510 --> 00:40:11.520 align:start position:0% background or like just pause while I'm 00:40:11.520 --> 00:40:14.569 align:start position:0% background or like just pause while I'm working<00:40:11.700> maybe<00:40:12.300> from<00:40:12.599> my<00:40:12.780> typical<00:40:13.020> work<00:40:13.260> hours 00:40:14.569 --> 00:40:14.579 align:start position:0% working maybe from my typical work hours 00:40:14.579 --> 00:40:22.849 align:start position:0% working maybe from my typical work hours um<00:40:14.640> yeah 00:40:22.849 --> 00:40:22.859 align:start position:0% 00:40:22.859 --> 00:40:29.450 align:start position:0% okay<00:40:23.520> all<00:40:24.060> right<00:40:24.560> anyone<00:40:25.560> else 00:40:29.450 --> 00:40:29.460 align:start position:0% 00:40:29.460 --> 00:40:31.670 align:start position:0% okay<00:40:29.940> I<00:40:30.119> think<00:40:30.240> that's<00:40:30.359> it<00:40:30.599> I<00:40:30.900> posted<00:40:31.320> the 00:40:31.670 --> 00:40:31.680 align:start position:0% okay I think that's it I posted the 00:40:31.680 --> 00:40:34.790 align:start position:0% okay I think that's it I posted the slides<00:40:32.099> on<00:40:32.579> the<00:40:32.940> nice<00:40:33.240> note<00:40:33.480> Twitter 00:40:34.790 --> 00:40:34.800 align:start position:0% slides on the nice note Twitter 00:40:34.800 --> 00:40:37.010 align:start position:0% slides on the nice note Twitter um<00:40:34.859> there's<00:40:35.040> tons<00:40:35.220> of<00:40:35.400> links<00:40:35.640> in<00:40:35.760> here 00:40:37.010 --> 00:40:37.020 align:start position:0% um there's tons of links in here 00:40:37.020 --> 00:40:37.790 align:start position:0% um there's tons of links in here um 00:40:37.790 --> 00:40:37.800 align:start position:0% um 00:40:37.800 --> 00:40:42.530 align:start position:0% um so<00:40:38.280> uh<00:40:39.060> you<00:40:39.180> can<00:40:39.300> check<00:40:39.359> out<00:40:39.480> the<00:40:39.660> slides<00:40:39.960> there 00:40:42.530 --> 00:40:42.540 align:start position:0% 00:40:42.540 --> 00:40:44.660 align:start position:0% awesome<00:40:42.960> thanks<00:40:43.260> everyone 00:40:44.660 --> 00:40:44.670 align:start position:0% awesome thanks everyone 00:40:44.670 --> 00:40:48.860 align:start position:0% awesome thanks everyone [Applause] 00:40:48.860 --> 00:40:48.870 align:start position:0% [Applause] 00:40:48.870 --> 00:40:58.569 align:start position:0% [Applause] [Music] 00:40:58.569 --> 00:40:58.579 align:start position:0% 00:40:58.579 --> 00:41:00.290 align:start position:0% uh 00:41:00.290 --> 00:41:00.300 align:start position:0% uh 00:41:00.300 --> 00:41:03.920 align:start position:0% uh okay<00:41:00.960> that's<00:41:01.260> it 00:41:03.920 --> 00:41:03.930 align:start position:0% 00:41:03.930 --> 00:41:07.430 align:start position:0% [Applause]