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:12.789 align:start position:0% [Music] 00:00:12.789 --> 00:00:12.799 align:start position:0% 00:00:12.799 --> 00:00:15.589 align:start position:0% welcome<00:00:13.799> here<00:00:14.219> in<00:00:14.400> Bogota<00:00:14.759> and<00:00:15.179> thank<00:00:15.299> you<00:00:15.420> for 00:00:15.589 --> 00:00:15.599 align:start position:0% welcome here in Bogota and thank you for 00:00:15.599 --> 00:00:18.470 align:start position:0% welcome here in Bogota and thank you for coming<00:00:15.780> I'm<00:00:16.619> Attila<00:00:17.279> and<00:00:17.640> I'm<00:00:17.880> From<00:00:18.119> The<00:00:18.240> Storm 00:00:18.470 --> 00:00:18.480 align:start position:0% coming I'm Attila and I'm From The Storm 00:00:18.480 --> 00:00:21.109 align:start position:0% coming I'm Attila and I'm From The Storm foundation<00:00:19.100> and<00:00:20.100> today<00:00:20.340> I'm<00:00:20.580> going<00:00:20.760> to<00:00:20.939> talk 00:00:21.109 --> 00:00:21.119 align:start position:0% foundation and today I'm going to talk 00:00:21.119 --> 00:00:24.470 align:start position:0% foundation and today I'm going to talk about<00:00:21.359> this<00:00:22.320> Farm<00:00:22.560> the<00:00:23.520> where<00:00:23.820> the<00:00:24.000> project<00:00:24.180> is 00:00:24.470 --> 00:00:24.480 align:start position:0% about this Farm the where the project is 00:00:24.480 --> 00:00:27.529 align:start position:0% about this Farm the where the project is at<00:00:24.660> the<00:00:24.840> moment<00:00:25.080> how<00:00:25.800> you<00:00:25.980> can<00:00:26.160> run<00:00:26.640> a<00:00:27.300> light 00:00:27.529 --> 00:00:27.539 align:start position:0% at the moment how you can run a light 00:00:27.539 --> 00:00:29.990 align:start position:0% at the moment how you can run a light node<00:00:27.840> how<00:00:28.019> you<00:00:28.199> can<00:00:28.320> run<00:00:28.439> full<00:00:28.740> node<00:00:29.099> and<00:00:29.699> talk 00:00:29.990 --> 00:00:30.000 align:start position:0% node how you can run full node and talk 00:00:30.000 --> 00:00:32.810 align:start position:0% node how you can run full node and talk a<00:00:30.180> bit<00:00:30.300> about<00:00:30.599> future<00:00:31.199> plans<00:00:31.679> as<00:00:31.920> well 00:00:32.810 --> 00:00:32.820 align:start position:0% a bit about future plans as well 00:00:32.820 --> 00:00:35.209 align:start position:0% a bit about future plans as well so<00:00:33.660> I<00:00:34.140> don't<00:00:34.260> know<00:00:34.320> how<00:00:34.500> many<00:00:34.680> of<00:00:34.860> you<00:00:34.980> are 00:00:35.209 --> 00:00:35.219 align:start position:0% so I don't know how many of you are 00:00:35.219 --> 00:00:38.030 align:start position:0% so I don't know how many of you are familiar<00:00:35.520> with<00:00:35.760> swarm<00:00:36.600> but<00:00:37.260> basically<00:00:37.620> swarm 00:00:38.030 --> 00:00:38.040 align:start position:0% familiar with swarm but basically swarm 00:00:38.040 --> 00:00:40.190 align:start position:0% familiar with swarm but basically swarm is<00:00:38.160> decentralized<00:00:38.760> data<00:00:39.239> storage<00:00:39.480> and 00:00:40.190 --> 00:00:40.200 align:start position:0% is decentralized data storage and 00:00:40.200 --> 00:00:42.170 align:start position:0% is decentralized data storage and distribution<00:00:40.620> technology 00:00:42.170 --> 00:00:42.180 align:start position:0% distribution technology 00:00:42.180 --> 00:00:45.350 align:start position:0% distribution technology so<00:00:42.920> also<00:00:43.920> I'm<00:00:44.100> not<00:00:44.340> sure<00:00:44.520> how<00:00:44.879> much<00:00:45.000> of<00:00:45.180> your 00:00:45.350 --> 00:00:45.360 align:start position:0% so also I'm not sure how much of your 00:00:45.360 --> 00:00:47.590 align:start position:0% so also I'm not sure how much of your family<00:00:45.660> are<00:00:45.899> with<00:00:46.079> this<00:00:46.320> original<00:00:46.500> idea<00:00:47.100> of 00:00:47.590 --> 00:00:47.600 align:start position:0% family are with this original idea of 00:00:47.600 --> 00:00:51.229 align:start position:0% family are with this original idea of ethereum<00:00:48.600> being<00:00:48.960> the<00:00:49.260> word<00:00:49.440> CPU<00:00:50.039> but<00:00:50.700> at<00:00:51.059> that 00:00:51.229 --> 00:00:51.239 align:start position:0% ethereum being the word CPU but at that 00:00:51.239 --> 00:00:53.450 align:start position:0% ethereum being the word CPU but at that the<00:00:51.719> Swarm<00:00:52.079> Origins<00:00:52.500> coming<00:00:52.739> from<00:00:52.980> the<00:00:53.219> same 00:00:53.450 --> 00:00:53.460 align:start position:0% the Swarm Origins coming from the same 00:00:53.460 --> 00:00:56.029 align:start position:0% the Swarm Origins coming from the same time<00:00:53.700> and<00:00:54.059> then<00:00:54.239> at<00:00:55.020> that<00:00:55.199> time<00:00:55.379> there<00:00:55.920> was 00:00:56.029 --> 00:00:56.039 align:start position:0% time and then at that time there was 00:00:56.039 --> 00:00:58.790 align:start position:0% time and then at that time there was this<00:00:56.280> idea<00:00:56.579> of<00:00:56.820> this<00:00:57.180> Holy<00:00:57.840> Trinity<00:00:58.079> where 00:00:58.790 --> 00:00:58.800 align:start position:0% this idea of this Holy Trinity where 00:00:58.800 --> 00:01:01.130 align:start position:0% this idea of this Holy Trinity where ethereum<00:00:59.280> is<00:00:59.460> the<00:00:59.579> word<00:00:59.699> CPU<00:01:00.239> swarm<00:01:00.840> would<00:01:00.960> be 00:01:01.130 --> 00:01:01.140 align:start position:0% ethereum is the word CPU swarm would be 00:01:01.140 --> 00:01:02.869 align:start position:0% ethereum is the word CPU swarm would be the<00:01:01.260> the<00:01:01.500> words<00:01:01.800> hard<00:01:02.219> drive<00:01:02.399> and<00:01:02.699> then 00:01:02.869 --> 00:01:02.879 align:start position:0% the the words hard drive and then 00:01:02.879 --> 00:01:05.450 align:start position:0% the the words hard drive and then whisper<00:01:03.300> would<00:01:03.539> have<00:01:03.719> been<00:01:03.840> the<00:01:04.460> messaging 00:01:05.450 --> 00:01:05.460 align:start position:0% whisper would have been the messaging 00:01:05.460 --> 00:01:06.649 align:start position:0% whisper would have been the messaging system 00:01:06.649 --> 00:01:06.659 align:start position:0% system 00:01:06.659 --> 00:01:09.469 align:start position:0% system and<00:01:07.560> like<00:01:08.040> things<00:01:08.640> turned<00:01:09.119> out<00:01:09.180> to<00:01:09.360> be 00:01:09.469 --> 00:01:09.479 align:start position:0% and like things turned out to be 00:01:09.479 --> 00:01:12.170 align:start position:0% and like things turned out to be differently<00:01:09.960> but<00:01:10.380> still<00:01:10.619> the<00:01:10.920> the<00:01:11.100> idea<00:01:11.520> and 00:01:12.170 --> 00:01:12.180 align:start position:0% differently but still the the idea and 00:01:12.180 --> 00:01:14.210 align:start position:0% differently but still the the idea and the<00:01:12.420> roots<00:01:12.659> of<00:01:12.900> swarm<00:01:13.380> is<00:01:13.560> coming<00:01:13.680> from<00:01:13.979> that 00:01:14.210 --> 00:01:14.220 align:start position:0% the roots of swarm is coming from that 00:01:14.220 --> 00:01:17.810 align:start position:0% the roots of swarm is coming from that so<00:01:14.580> you<00:01:15.180> can<00:01:15.299> think<00:01:15.659> of<00:01:15.840> swarm<00:01:16.320> as<00:01:16.500> being<00:01:16.740> the<00:01:17.520> a 00:01:17.810 --> 00:01:17.820 align:start position:0% so you can think of swarm as being the a 00:01:17.820 --> 00:01:20.450 align:start position:0% so you can think of swarm as being the a huge<00:01:18.659> hard<00:01:19.080> drive<00:01:19.260> based<00:01:19.740> on<00:01:19.799> peer-to-peer 00:01:20.450 --> 00:01:20.460 align:start position:0% huge hard drive based on peer-to-peer 00:01:20.460 --> 00:01:23.030 align:start position:0% huge hard drive based on peer-to-peer technology<00:01:20.820> and<00:01:21.780> then<00:01:21.960> when<00:01:22.320> I'm<00:01:22.860> talking 00:01:23.030 --> 00:01:23.040 align:start position:0% technology and then when I'm talking 00:01:23.040 --> 00:01:25.249 align:start position:0% technology and then when I'm talking about<00:01:23.340> swarm<00:01:24.000> people<00:01:24.240> usually<00:01:24.659> ask<00:01:24.840> me<00:01:25.020> okay 00:01:25.249 --> 00:01:25.259 align:start position:0% about swarm people usually ask me okay 00:01:25.259 --> 00:01:27.350 align:start position:0% about swarm people usually ask me okay so<00:01:25.500> how<00:01:25.799> is<00:01:25.920> it<00:01:26.040> different<00:01:26.159> from<00:01:26.400> ipfs<00:01:27.119> like 00:01:27.350 --> 00:01:27.360 align:start position:0% so how is it different from ipfs like 00:01:27.360 --> 00:01:29.210 align:start position:0% so how is it different from ipfs like this<00:01:27.479> is<00:01:27.600> the<00:01:27.780> question<00:01:28.020> that<00:01:28.439> everyone<00:01:28.920> is 00:01:29.210 --> 00:01:29.220 align:start position:0% this is the question that everyone is 00:01:29.220 --> 00:01:32.270 align:start position:0% this is the question that everyone is interested<00:01:29.700> in<00:01:29.939> and<00:01:30.900> then 00:01:32.270 --> 00:01:32.280 align:start position:0% interested in and then 00:01:32.280 --> 00:01:36.050 align:start position:0% interested in and then um<00:01:32.340> it's<00:01:33.299> quite<00:01:33.540> different<00:01:33.860> but<00:01:34.860> since<00:01:35.460> the 00:01:36.050 --> 00:01:36.060 align:start position:0% um it's quite different but since the 00:01:36.060 --> 00:01:38.690 align:start position:0% um it's quite different but since the the<00:01:36.900> goals<00:01:37.320> of<00:01:37.439> the<00:01:37.619> projects<00:01:37.979> are<00:01:38.220> similar 00:01:38.690 --> 00:01:38.700 align:start position:0% the goals of the projects are similar 00:01:38.700 --> 00:01:41.270 align:start position:0% the goals of the projects are similar then<00:01:39.119> I<00:01:39.659> think<00:01:39.840> it's<00:01:40.140> worth<00:01:40.439> mentioning<00:01:40.920> like 00:01:41.270 --> 00:01:41.280 align:start position:0% then I think it's worth mentioning like 00:01:41.280 --> 00:01:43.730 align:start position:0% then I think it's worth mentioning like what<00:01:41.579> are<00:01:41.820> the<00:01:42.060> there's<00:01:42.840> some<00:01:43.200> kind<00:01:43.380> of<00:01:43.500> core 00:01:43.730 --> 00:01:43.740 align:start position:0% what are the there's some kind of core 00:01:43.740 --> 00:01:45.410 align:start position:0% what are the there's some kind of core ideas<00:01:44.280> that 00:01:45.410 --> 00:01:45.420 align:start position:0% ideas that 00:01:45.420 --> 00:01:47.090 align:start position:0% ideas that are<00:01:45.900> built<00:01:46.259> into<00:01:46.320> swarm<00:01:46.799> and<00:01:46.920> maybe 00:01:47.090 --> 00:01:47.100 align:start position:0% are built into swarm and maybe 00:01:47.100 --> 00:01:49.429 align:start position:0% are built into swarm and maybe differentiating<00:01:47.759> with<00:01:48.060> different<00:01:48.299> uh<00:01:49.140> or 00:01:49.429 --> 00:01:49.439 align:start position:0% differentiating with different uh or 00:01:49.439 --> 00:01:52.069 align:start position:0% differentiating with different uh or alternative<00:01:50.299> decentralized<00:01:51.299> storage<00:01:51.600> system 00:01:52.069 --> 00:01:52.079 align:start position:0% alternative decentralized storage system 00:01:52.079 --> 00:01:56.630 align:start position:0% alternative decentralized storage system so<00:01:53.119> one<00:01:54.119> thing<00:01:54.299> is<00:01:54.659> that<00:01:54.960> uh<00:01:55.320> swarm<00:01:56.040> has<00:01:56.220> a<00:01:56.460> very 00:01:56.630 --> 00:01:56.640 align:start position:0% so one thing is that uh swarm has a very 00:01:56.640 --> 00:01:59.710 align:start position:0% so one thing is that uh swarm has a very strong<00:01:57.060> focus<00:01:57.540> and<00:01:57.899> privacy<00:01:58.340> preserving<00:01:59.340> and 00:01:59.710 --> 00:01:59.720 align:start position:0% strong focus and privacy preserving and 00:01:59.720 --> 00:02:03.289 align:start position:0% strong focus and privacy preserving and uh<00:02:00.720> being<00:02:01.380> permissionless<00:02:02.100> so<00:02:02.520> it<00:02:02.700> means<00:02:03.000> that 00:02:03.289 --> 00:02:03.299 align:start position:0% uh being permissionless so it means that 00:02:03.299 --> 00:02:07.130 align:start position:0% uh being permissionless so it means that you<00:02:04.140> in<00:02:04.439> order<00:02:04.619> to<00:02:05.040> upload<00:02:05.759> to<00:02:06.000> the<00:02:06.180> Swarm<00:02:06.899> to 00:02:07.130 --> 00:02:07.140 align:start position:0% you in order to upload to the Swarm to 00:02:07.140 --> 00:02:09.650 align:start position:0% you in order to upload to the Swarm to the<00:02:07.200> this<00:02:07.560> world<00:02:07.740> hard<00:02:08.340> disk<00:02:08.759> you<00:02:09.239> don't<00:02:09.420> have 00:02:09.650 --> 00:02:09.660 align:start position:0% the this world hard disk you don't have 00:02:09.660 --> 00:02:11.330 align:start position:0% the this world hard disk you don't have to<00:02:09.899> have<00:02:10.080> a<00:02:10.259> node<00:02:10.500> so<00:02:10.800> that's<00:02:10.979> a<00:02:11.160> different 00:02:11.330 --> 00:02:11.340 align:start position:0% to have a node so that's a different 00:02:11.340 --> 00:02:14.630 align:start position:0% to have a node so that's a different from<00:02:11.700> ipfs<00:02:12.360> you<00:02:12.599> have<00:02:12.720> to<00:02:12.840> have<00:02:13.020> your<00:02:13.200> node<00:02:13.640> and 00:02:14.630 --> 00:02:14.640 align:start position:0% from ipfs you have to have your node and 00:02:14.640 --> 00:02:17.089 align:start position:0% from ipfs you have to have your node and I<00:02:15.120> will<00:02:15.239> talk<00:02:15.480> about<00:02:15.599> later<00:02:15.959> like<00:02:16.440> a<00:02:16.739> bit<00:02:16.920> more 00:02:17.089 --> 00:02:17.099 align:start position:0% I will talk about later like a bit more 00:02:17.099 --> 00:02:20.210 align:start position:0% I will talk about later like a bit more the<00:02:17.640> the<00:02:18.239> differences<00:02:19.020> in<00:02:19.319> like<00:02:19.440> how<00:02:19.739> the<00:02:19.920> data 00:02:20.210 --> 00:02:20.220 align:start position:0% the the differences in like how the data 00:02:20.220 --> 00:02:23.210 align:start position:0% the the differences in like how the data is<00:02:20.400> handled<00:02:20.760> but<00:02:21.480> then<00:02:21.720> again<00:02:21.980> going<00:02:22.980> forward 00:02:23.210 --> 00:02:23.220 align:start position:0% is handled but then again going forward 00:02:23.220 --> 00:02:24.970 align:start position:0% is handled but then again going forward on<00:02:23.580> this<00:02:23.760> list<00:02:23.940> like 00:02:24.970 --> 00:02:24.980 align:start position:0% on this list like 00:02:24.980 --> 00:02:27.890 align:start position:0% on this list like swarming<00:02:25.980> interim<00:02:26.459> native<00:02:26.700> which<00:02:27.060> means<00:02:27.599> that 00:02:27.890 --> 00:02:27.900 align:start position:0% swarming interim native which means that 00:02:27.900 --> 00:02:30.170 align:start position:0% swarming interim native which means that it<00:02:28.680> uses<00:02:28.920> a<00:02:29.099> lot<00:02:29.160> of<00:02:29.220> Primitives<00:02:29.700> like<00:02:29.879> crypto 00:02:30.170 --> 00:02:30.180 align:start position:0% it uses a lot of Primitives like crypto 00:02:30.180 --> 00:02:32.510 align:start position:0% it uses a lot of Primitives like crypto Primitives<00:02:30.720> that<00:02:31.200> are<00:02:31.560> used<00:02:31.800> in<00:02:31.980> each<00:02:32.160> room 00:02:32.510 --> 00:02:32.520 align:start position:0% Primitives that are used in each room 00:02:32.520 --> 00:02:35.990 align:start position:0% Primitives that are used in each room and<00:02:33.300> also<00:02:33.660> the<00:02:33.959> smart<00:02:34.140> contracts<00:02:34.680> it<00:02:34.860> uses<00:02:35.220> are 00:02:35.990 --> 00:02:36.000 align:start position:0% and also the smart contracts it uses are 00:02:36.000 --> 00:02:39.589 align:start position:0% and also the smart contracts it uses are running<00:02:36.180> on<00:02:36.620> evm<00:02:37.620> so<00:02:37.980> it<00:02:38.160> doesn't<00:02:38.580> invent<00:02:39.180> its 00:02:39.589 --> 00:02:39.599 align:start position:0% running on evm so it doesn't invent its 00:02:39.599 --> 00:02:41.930 align:start position:0% running on evm so it doesn't invent its own<00:02:39.720> blockchain<00:02:40.680> and<00:02:41.040> it<00:02:41.220> does<00:02:41.400> not<00:02:41.580> try<00:02:41.760> to 00:02:41.930 --> 00:02:41.940 align:start position:0% own blockchain and it does not try to 00:02:41.940 --> 00:02:43.850 align:start position:0% own blockchain and it does not try to create<00:02:42.180> that<00:02:42.780> problem<00:02:43.080> because<00:02:43.440> that<00:02:43.739> is 00:02:43.850 --> 00:02:43.860 align:start position:0% create that problem because that is 00:02:43.860 --> 00:02:45.770 align:start position:0% create that problem because that is solved<00:02:44.220> by<00:02:44.400> others<00:02:44.819> and<00:02:45.000> it's 00:02:45.770 --> 00:02:45.780 align:start position:0% solved by others and it's 00:02:45.780 --> 00:02:48.430 align:start position:0% solved by others and it's not<00:02:46.440> the<00:02:46.680> area<00:02:46.920> of<00:02:47.160> focus 00:02:48.430 --> 00:02:48.440 align:start position:0% not the area of focus 00:02:48.440 --> 00:02:51.589 align:start position:0% not the area of focus it<00:02:49.440> has<00:02:49.680> robo's<00:02:50.340> defenses<00:02:50.700> against<00:02:51.000> blocking 00:02:51.589 --> 00:02:51.599 align:start position:0% it has robo's defenses against blocking 00:02:51.599 --> 00:02:54.070 align:start position:0% it has robo's defenses against blocking or<00:02:51.840> changing<00:02:52.260> access<00:02:52.500> so<00:02:53.099> that 00:02:54.070 --> 00:02:54.080 align:start position:0% or changing access so that 00:02:54.080 --> 00:02:56.449 align:start position:0% or changing access so that this<00:02:55.080> is<00:02:55.260> kind<00:02:55.500> of<00:02:55.620> the<00:02:55.860> thing<00:02:55.980> that<00:02:56.220> we<00:02:56.340> call 00:02:56.449 --> 00:02:56.459 align:start position:0% this is kind of the thing that we call 00:02:56.459 --> 00:02:58.670 align:start position:0% this is kind of the thing that we call censorship<00:02:57.060> resistance<00:02:57.660> so<00:02:57.900> once<00:02:58.260> data<00:02:58.560> is 00:02:58.670 --> 00:02:58.680 align:start position:0% censorship resistance so once data is 00:02:58.680 --> 00:03:01.130 align:start position:0% censorship resistance so once data is uploaded<00:02:59.099> to<00:02:59.280> the<00:02:59.400> network<00:02:59.580> as<00:03:00.480> long<00:03:00.660> as<00:03:00.840> there 00:03:01.130 --> 00:03:01.140 align:start position:0% uploaded to the network as long as there 00:03:01.140 --> 00:03:02.869 align:start position:0% uploaded to the network as long as there is<00:03:01.260> someone<00:03:01.440> who<00:03:01.860> wants<00:03:02.099> to<00:03:02.160> keep<00:03:02.340> it<00:03:02.519> on<00:03:02.760> the 00:03:02.869 --> 00:03:02.879 align:start position:0% is someone who wants to keep it on the 00:03:02.879 --> 00:03:05.869 align:start position:0% is someone who wants to keep it on the network<00:03:03.060> then<00:03:04.019> nobody<00:03:04.800> else<00:03:05.099> can<00:03:05.400> take<00:03:05.640> it 00:03:05.869 --> 00:03:05.879 align:start position:0% network then nobody else can take it 00:03:05.879 --> 00:03:07.970 align:start position:0% network then nobody else can take it down<00:03:06.239> from<00:03:06.480> the<00:03:06.660> network<00:03:06.780> or<00:03:07.140> that's<00:03:07.379> the<00:03:07.620> idea 00:03:07.970 --> 00:03:07.980 align:start position:0% down from the network or that's the idea 00:03:07.980 --> 00:03:10.670 align:start position:0% down from the network or that's the idea and<00:03:08.220> then<00:03:08.459> I<00:03:09.239> will<00:03:09.420> talk<00:03:09.599> about<00:03:09.720> later<00:03:10.319> where 00:03:10.670 --> 00:03:10.680 align:start position:0% and then I will talk about later where 00:03:10.680 --> 00:03:12.250 align:start position:0% and then I will talk about later where we<00:03:10.860> are<00:03:10.980> with<00:03:11.220> that 00:03:12.250 --> 00:03:12.260 align:start position:0% we are with that 00:03:12.260 --> 00:03:15.410 align:start position:0% we are with that there<00:03:13.260> is<00:03:13.379> also<00:03:13.739> a<00:03:14.159> feature<00:03:14.640> which<00:03:15.120> is<00:03:15.239> like 00:03:15.410 --> 00:03:15.420 align:start position:0% there is also a feature which is like 00:03:15.420 --> 00:03:18.350 align:start position:0% there is also a feature which is like Auto<00:03:15.659> scaling<00:03:16.200> so<00:03:16.500> the<00:03:16.680> the<00:03:17.000> because<00:03:18.000> this<00:03:18.239> is 00:03:18.350 --> 00:03:18.360 align:start position:0% Auto scaling so the the because this is 00:03:18.360 --> 00:03:20.089 align:start position:0% Auto scaling so the the because this is our<00:03:18.659> country<00:03:18.900> this<00:03:19.500> is<00:03:19.560> a<00:03:19.680> distribution 00:03:20.089 --> 00:03:20.099 align:start position:0% our country this is a distribution 00:03:20.099 --> 00:03:25.729 align:start position:0% our country this is a distribution Network<00:03:20.400> as<00:03:20.819> well<00:03:21.440> the<00:03:22.440> data<00:03:22.800> is<00:03:22.980> uh 00:03:25.729 --> 00:03:25.739 align:start position:0% 00:03:25.739 --> 00:03:27.649 align:start position:0% um you<00:03:26.459> know<00:03:26.519> when<00:03:26.760> when<00:03:27.000> the<00:03:27.239> data<00:03:27.540> is 00:03:27.649 --> 00:03:27.659 align:start position:0% um you know when when the data is 00:03:27.659 --> 00:03:30.890 align:start position:0% um you know when when the data is downloaded<00:03:28.140> then<00:03:28.980> the<00:03:29.280> copies<00:03:29.819> are<00:03:30.360> stored<00:03:30.720> on 00:03:30.890 --> 00:03:30.900 align:start position:0% downloaded then the copies are stored on 00:03:30.900 --> 00:03:34.190 align:start position:0% downloaded then the copies are stored on nodes<00:03:31.200> and<00:03:31.620> therefore<00:03:31.980> uh<00:03:32.940> it's<00:03:33.720> it's 00:03:34.190 --> 00:03:34.200 align:start position:0% nodes and therefore uh it's it's 00:03:34.200 --> 00:03:37.250 align:start position:0% nodes and therefore uh it's it's available<00:03:34.560> on<00:03:35.400> more<00:03:35.580> nodes<00:03:36.000> so<00:03:36.239> that<00:03:36.540> it<00:03:36.959> has 00:03:37.250 --> 00:03:37.260 align:start position:0% available on more nodes so that it has 00:03:37.260 --> 00:03:39.949 align:start position:0% available on more nodes so that it has this<00:03:37.500> other<00:03:37.739> this<00:03:38.459> uh<00:03:38.700> property<00:03:39.480> that<00:03:39.720> like 00:03:39.949 --> 00:03:39.959 align:start position:0% this other this uh property that like 00:03:39.959 --> 00:03:42.289 align:start position:0% this other this uh property that like more<00:03:40.500> people<00:03:40.680> you<00:03:41.099> sharing<00:03:41.640> the<00:03:41.819> same<00:03:42.000> kind<00:03:42.180> of 00:03:42.289 --> 00:03:42.299 align:start position:0% more people you sharing the same kind of 00:03:42.299 --> 00:03:44.690 align:start position:0% more people you sharing the same kind of data<00:03:42.780> sets<00:03:43.080> the<00:03:43.260> more<00:03:43.440> it<00:03:43.860> copies<00:03:44.280> there<00:03:44.519> are 00:03:44.690 --> 00:03:44.700 align:start position:0% data sets the more it copies there are 00:03:44.700 --> 00:03:46.789 align:start position:0% data sets the more it copies there are on<00:03:44.819> the<00:03:44.940> network<00:03:45.060> and<00:03:45.480> that<00:03:45.780> can<00:03:45.959> help<00:03:46.200> with 00:03:46.789 --> 00:03:46.799 align:start position:0% on the network and that can help with 00:03:46.799 --> 00:03:50.030 align:start position:0% on the network and that can help with like<00:03:47.099> CDN<00:03:47.940> type<00:03:48.360> of<00:03:48.540> functionalities<00:03:49.200> there's 00:03:50.030 --> 00:03:50.040 align:start position:0% like CDN type of functionalities there's 00:03:50.040 --> 00:03:51.949 align:start position:0% like CDN type of functionalities there's Integrity<00:03:50.580> protection<00:03:51.060> with<00:03:51.540> content 00:03:51.949 --> 00:03:51.959 align:start position:0% Integrity protection with content 00:03:51.959 --> 00:03:54.649 align:start position:0% Integrity protection with content addressing<00:03:52.680> but<00:03:53.400> also<00:03:53.700> there<00:03:54.000> is<00:03:54.180> mutable 00:03:54.649 --> 00:03:54.659 align:start position:0% addressing but also there is mutable 00:03:54.659 --> 00:03:58.490 align:start position:0% addressing but also there is mutable updates<00:03:55.200> with<00:03:55.739> sign<00:03:56.040> chunks<00:03:56.580> so<00:03:56.879> you<00:03:57.360> can<00:03:57.540> have 00:03:58.490 --> 00:03:58.500 align:start position:0% updates with sign chunks so you can have 00:03:58.500 --> 00:04:00.890 align:start position:0% updates with sign chunks so you can have both<00:03:59.040> of<00:03:59.280> these<00:03:59.580> things<00:03:59.700> together<00:04:00.120> and<00:04:00.659> with 00:04:00.890 --> 00:04:00.900 align:start position:0% both of these things together and with 00:04:00.900 --> 00:04:04.550 align:start position:0% both of these things together and with that<00:04:01.140> you<00:04:01.680> can<00:04:01.860> think<00:04:02.519> of<00:04:02.700> also<00:04:03.060> like<00:04:03.239> as<00:04:03.720> a<00:04:04.019> not 00:04:04.550 --> 00:04:04.560 align:start position:0% that you can think of also like as a not 00:04:04.560 --> 00:04:07.130 align:start position:0% that you can think of also like as a not only<00:04:04.680> just<00:04:05.040> storing<00:04:05.640> like<00:04:06.000> static<00:04:06.480> data<00:04:06.900> sets 00:04:07.130 --> 00:04:07.140 align:start position:0% only just storing like static data sets 00:04:07.140 --> 00:04:09.890 align:start position:0% only just storing like static data sets but<00:04:07.440> like<00:04:07.680> have<00:04:08.159> data<00:04:09.000> structures<00:04:09.360> that<00:04:09.720> can 00:04:09.890 --> 00:04:09.900 align:start position:0% but like have data structures that can 00:04:09.900 --> 00:04:12.289 align:start position:0% but like have data structures that can be<00:04:10.080> updated<00:04:10.700> and<00:04:11.700> can<00:04:11.879> be<00:04:12.000> used<00:04:12.120> for 00:04:12.289 --> 00:04:12.299 align:start position:0% be updated and can be used for 00:04:12.299 --> 00:04:13.809 align:start position:0% be updated and can be used for application<00:04:12.780> layers 00:04:13.809 --> 00:04:13.819 align:start position:0% application layers 00:04:13.819 --> 00:04:17.569 align:start position:0% application layers and<00:04:14.819> eventually<00:04:15.599> it<00:04:16.079> forgets<00:04:16.620> data<00:04:17.100> or 00:04:17.569 --> 00:04:17.579 align:start position:0% and eventually it forgets data or 00:04:17.579 --> 00:04:19.670 align:start position:0% and eventually it forgets data or content<00:04:18.000> that<00:04:18.359> is<00:04:18.540> no<00:04:18.720> longer<00:04:18.959> relevant<00:04:19.500> to 00:04:19.670 --> 00:04:19.680 align:start position:0% content that is no longer relevant to 00:04:19.680 --> 00:04:22.969 align:start position:0% content that is no longer relevant to preserve<00:04:20.160> so<00:04:20.600> as<00:04:21.600> I<00:04:21.900> will<00:04:22.139> explain<00:04:22.380> like<00:04:22.800> you 00:04:22.969 --> 00:04:22.979 align:start position:0% preserve so as I will explain like you 00:04:22.979 --> 00:04:25.850 align:start position:0% preserve so as I will explain like you have<00:04:23.160> to<00:04:23.340> pay<00:04:23.639> in<00:04:24.300> order<00:04:24.419> to<00:04:24.600> get<00:04:25.020> the<00:04:25.440> data<00:04:25.740> on 00:04:25.850 --> 00:04:25.860 align:start position:0% have to pay in order to get the data on 00:04:25.860 --> 00:04:28.969 align:start position:0% have to pay in order to get the data on the<00:04:25.979> network<00:04:26.300> and<00:04:27.300> if<00:04:28.020> nobody<00:04:28.440> is<00:04:28.620> paying<00:04:28.860> for 00:04:28.969 --> 00:04:28.979 align:start position:0% the network and if nobody is paying for 00:04:28.979 --> 00:04:31.070 align:start position:0% the network and if nobody is paying for the<00:04:29.160> data<00:04:29.460> then<00:04:29.699> it<00:04:29.820> means<00:04:30.120> that<00:04:30.419> it's<00:04:30.900> no 00:04:31.070 --> 00:04:31.080 align:start position:0% the data then it means that it's no 00:04:31.080 --> 00:04:33.890 align:start position:0% the data then it means that it's no longer<00:04:31.320> relevant<00:04:31.680> so<00:04:31.919> it<00:04:32.100> will<00:04:32.220> be<00:04:32.400> deleted<00:04:33.300> so 00:04:33.890 --> 00:04:33.900 align:start position:0% longer relevant so it will be deleted so 00:04:33.900 --> 00:04:36.530 align:start position:0% longer relevant so it will be deleted so these<00:04:34.500> are<00:04:34.620> like<00:04:34.860> from<00:04:35.460> this<00:04:35.639> you<00:04:36.000> may<00:04:36.180> get<00:04:36.360> an 00:04:36.530 --> 00:04:36.540 align:start position:0% these are like from this you may get an 00:04:36.540 --> 00:04:40.629 align:start position:0% these are like from this you may get an initial<00:04:36.840> impression<00:04:37.400> and<00:04:38.400> I<00:04:38.820> will<00:04:38.940> go<00:04:39.120> to<00:04:39.380> some 00:04:40.629 --> 00:04:40.639 align:start position:0% initial impression and I will go to some 00:04:40.639 --> 00:04:43.070 align:start position:0% initial impression and I will go to some details<00:04:41.639> but<00:04:41.880> not<00:04:42.120> in<00:04:42.419> a<00:04:42.540> very<00:04:42.660> deep<00:04:42.840> level 00:04:43.070 --> 00:04:43.080 align:start position:0% details but not in a very deep level 00:04:43.080 --> 00:04:45.189 align:start position:0% details but not in a very deep level because<00:04:43.440> that's<00:04:43.800> not<00:04:43.979> the<00:04:44.220> focus<00:04:44.460> of<00:04:44.699> this 00:04:45.189 --> 00:04:45.199 align:start position:0% because that's not the focus of this 00:04:45.199 --> 00:04:47.749 align:start position:0% because that's not the focus of this Workshop<00:04:46.199> it's<00:04:46.440> more<00:04:46.680> it's<00:04:47.340> going<00:04:47.520> to<00:04:47.580> be 00:04:47.749 --> 00:04:47.759 align:start position:0% Workshop it's more it's going to be 00:04:47.759 --> 00:04:49.909 align:start position:0% Workshop it's more it's going to be Hands-On<00:04:48.180> so<00:04:48.360> don't<00:04:48.540> worry<00:04:48.720> just<00:04:49.080> I<00:04:49.500> just<00:04:49.740> give 00:04:49.909 --> 00:04:49.919 align:start position:0% Hands-On so don't worry just I just give 00:04:49.919 --> 00:04:52.550 align:start position:0% Hands-On so don't worry just I just give a<00:04:50.160> small<00:04:50.580> introduction<00:04:51.180> so<00:04:51.600> that<00:04:51.780> everyone<00:04:52.199> is 00:04:52.550 --> 00:04:52.560 align:start position:0% a small introduction so that everyone is 00:04:52.560 --> 00:04:55.670 align:start position:0% a small introduction so that everyone is on<00:04:52.800> the<00:04:52.919> same<00:04:53.100> page<00:04:53.660> so<00:04:54.660> basically<00:04:55.199> when<00:04:55.500> you 00:04:55.670 --> 00:04:55.680 align:start position:0% on the same page so basically when you 00:04:55.680 --> 00:04:58.249 align:start position:0% on the same page so basically when you upload<00:04:56.040> data<00:04:56.520> to<00:04:56.759> the<00:04:56.940> Swarm<00:04:57.360> what<00:04:57.780> happens<00:04:57.960> is 00:04:58.249 --> 00:04:58.259 align:start position:0% upload data to the Swarm what happens is 00:04:58.259 --> 00:05:00.950 align:start position:0% upload data to the Swarm what happens is that<00:04:58.560> swarm<00:04:59.220> takes<00:04:59.460> the<00:04:59.639> data<00:05:00.000> splits<00:05:00.660> it<00:05:00.840> into 00:05:00.950 --> 00:05:00.960 align:start position:0% that swarm takes the data splits it into 00:05:00.960 --> 00:05:05.689 align:start position:0% that swarm takes the data splits it into 4K<00:05:01.500> chunks<00:05:02.040> and<00:05:02.940> then<00:05:03.180> assigns<00:05:04.080> the<00:05:04.500> the<00:05:04.919> I<00:05:05.400> am 00:05:05.689 --> 00:05:05.699 align:start position:0% 4K chunks and then assigns the the I am 00:05:05.699 --> 00:05:06.469 align:start position:0% 4K chunks and then assigns the the I am done 00:05:06.469 --> 00:05:06.479 align:start position:0% done 00:05:06.479 --> 00:05:08.810 align:start position:0% done optionally<00:05:07.320> currently<00:05:07.860> it's<00:05:08.160> optional<00:05:08.639> and 00:05:08.810 --> 00:05:08.820 align:start position:0% optionally currently it's optional and 00:05:08.820 --> 00:05:12.110 align:start position:0% optionally currently it's optional and encrypt<00:05:09.300> the<00:05:09.479> chunks<00:05:09.900> and<00:05:10.680> then<00:05:10.919> based<00:05:11.699> on<00:05:11.820> the 00:05:12.110 --> 00:05:12.120 align:start position:0% encrypt the chunks and then based on the 00:05:12.120 --> 00:05:14.590 align:start position:0% encrypt the chunks and then based on the chunks<00:05:12.660> content<00:05:13.139> address<00:05:13.380> finds<00:05:14.160> the<00:05:14.340> nodes 00:05:14.590 --> 00:05:14.600 align:start position:0% chunks content address finds the nodes 00:05:14.600 --> 00:05:17.210 align:start position:0% chunks content address finds the nodes that<00:05:15.600> should<00:05:15.960> be<00:05:16.139> storing<00:05:16.620> it<00:05:16.740> on<00:05:16.919> the<00:05:17.040> network 00:05:17.210 --> 00:05:17.220 align:start position:0% that should be storing it on the network 00:05:17.220 --> 00:05:19.490 align:start position:0% that should be storing it on the network and<00:05:17.639> that<00:05:18.000> means<00:05:18.419> that<00:05:18.600> the<00:05:18.780> data<00:05:19.139> is<00:05:19.259> spread 00:05:19.490 --> 00:05:19.500 align:start position:0% and that means that the data is spread 00:05:19.500 --> 00:05:22.490 align:start position:0% and that means that the data is spread on<00:05:19.620> the<00:05:19.800> network<00:05:20.120> so<00:05:21.120> then<00:05:21.960> you<00:05:22.199> want<00:05:22.320> to 00:05:22.490 --> 00:05:22.500 align:start position:0% on the network so then you want to 00:05:22.500 --> 00:05:24.189 align:start position:0% on the network so then you want to upload<00:05:22.979> uh 00:05:24.189 --> 00:05:24.199 align:start position:0% upload uh 00:05:24.199 --> 00:05:27.950 align:start position:0% upload uh a<00:05:25.199> data<00:05:25.560> any<00:05:26.400> data<00:05:26.820> onto<00:05:27.240> the<00:05:27.360> network<00:05:27.539> then 00:05:27.950 --> 00:05:27.960 align:start position:0% a data any data onto the network then 00:05:27.960 --> 00:05:30.350 align:start position:0% a data any data onto the network then when<00:05:28.560> you<00:05:28.800> have<00:05:28.919> a<00:05:29.039> node<00:05:29.280> then<00:05:29.580> it<00:05:29.759> will<00:05:29.940> find 00:05:30.350 --> 00:05:30.360 align:start position:0% when you have a node then it will find 00:05:30.360 --> 00:05:33.110 align:start position:0% when you have a node then it will find the<00:05:31.020> nearest<00:05:31.199> nodes<00:05:31.860> that<00:05:32.220> matches<00:05:32.639> the 00:05:33.110 --> 00:05:33.120 align:start position:0% the nearest nodes that matches the 00:05:33.120 --> 00:05:36.409 align:start position:0% the nearest nodes that matches the content<00:05:33.660> address<00:05:34.020> of<00:05:34.979> the<00:05:35.340> of<00:05:35.699> the<00:05:36.000> data<00:05:36.300> of 00:05:36.409 --> 00:05:36.419 align:start position:0% content address of the of the data of 00:05:36.419 --> 00:05:39.830 align:start position:0% content address of the of the data of the<00:05:36.600> data<00:05:36.960> chunk<00:05:37.199> and<00:05:38.100> send<00:05:38.520> it<00:05:38.759> there<00:05:39.000> and 00:05:39.830 --> 00:05:39.840 align:start position:0% the data chunk and send it there and 00:05:39.840 --> 00:05:42.110 align:start position:0% the data chunk and send it there and then<00:05:40.080> when<00:05:40.560> you<00:05:40.740> try<00:05:40.979> to<00:05:41.220> download<00:05:41.460> the<00:05:41.820> data 00:05:42.110 --> 00:05:42.120 align:start position:0% then when you try to download the data 00:05:42.120 --> 00:05:44.749 align:start position:0% then when you try to download the data the<00:05:42.300> same<00:05:42.479> logic<00:05:42.900> happens<00:05:43.080> so<00:05:43.680> then<00:05:43.919> basically 00:05:44.749 --> 00:05:44.759 align:start position:0% the same logic happens so then basically 00:05:44.759 --> 00:05:47.090 align:start position:0% the same logic happens so then basically you<00:05:45.180> access<00:05:45.479> any<00:05:45.900> nodes<00:05:46.259> and<00:05:46.680> then<00:05:46.800> it<00:05:46.979> will 00:05:47.090 --> 00:05:47.100 align:start position:0% you access any nodes and then it will 00:05:47.100 --> 00:05:48.950 align:start position:0% you access any nodes and then it will find<00:05:47.340> the<00:05:47.520> route<00:05:47.699> on<00:05:47.940> the<00:05:48.120> network<00:05:48.240> and<00:05:48.780> then 00:05:48.950 --> 00:05:48.960 align:start position:0% find the route on the network and then 00:05:48.960 --> 00:05:52.850 align:start position:0% find the route on the network and then get<00:05:49.620> back<00:05:49.800> the<00:05:50.100> chunks<00:05:50.660> from<00:05:51.660> the<00:05:52.380> the<00:05:52.560> nodes 00:05:52.850 --> 00:05:52.860 align:start position:0% get back the chunks from the the nodes 00:05:52.860 --> 00:05:55.610 align:start position:0% get back the chunks from the the nodes that<00:05:53.580> has<00:05:53.820> the<00:05:54.120> address<00:05:54.419> closest<00:05:54.960> to<00:05:55.380> the 00:05:55.610 --> 00:05:55.620 align:start position:0% that has the address closest to the 00:05:55.620 --> 00:05:57.710 align:start position:0% that has the address closest to the chunks<00:05:56.340> address 00:05:57.710 --> 00:05:57.720 align:start position:0% chunks address 00:05:57.720 --> 00:06:01.550 align:start position:0% chunks address and<00:05:58.500> so<00:05:58.940> that's<00:05:59.940> the<00:06:00.240> basics<00:06:00.600> of<00:06:00.840> like<00:06:01.080> the 00:06:01.550 --> 00:06:01.560 align:start position:0% and so that's the basics of like the 00:06:01.560 --> 00:06:04.730 align:start position:0% and so that's the basics of like the storing<00:06:02.460> data<00:06:02.880> on<00:06:03.300> Swarm<00:06:03.720> and<00:06:04.139> the<00:06:04.320> main 00:06:04.730 --> 00:06:04.740 align:start position:0% storing data on Swarm and the main 00:06:04.740 --> 00:06:08.210 align:start position:0% storing data on Swarm and the main concept<00:06:05.479> and<00:06:06.479> uh<00:06:06.900> also 00:06:08.210 --> 00:06:08.220 align:start position:0% concept and uh also 00:06:08.220 --> 00:06:10.730 align:start position:0% concept and uh also there<00:06:08.820> are<00:06:08.940> different<00:06:09.120> kind<00:06:09.479> of<00:06:09.600> nodes<00:06:09.900> so<00:06:10.199> as 00:06:10.730 --> 00:06:10.740 align:start position:0% there are different kind of nodes so as 00:06:10.740 --> 00:06:13.550 align:start position:0% there are different kind of nodes so as as<00:06:10.800> Farm<00:06:11.400> evolved<00:06:11.940> we<00:06:12.180> realized<00:06:12.600> that<00:06:12.900> one 00:06:13.550 --> 00:06:13.560 align:start position:0% as Farm evolved we realized that one 00:06:13.560 --> 00:06:17.150 align:start position:0% as Farm evolved we realized that one size<00:06:13.800> does<00:06:14.160> not<00:06:14.340> fit<00:06:14.639> all<00:06:14.820> and<00:06:15.419> and<00:06:16.020> then<00:06:16.440> at 00:06:17.150 --> 00:06:17.160 align:start position:0% size does not fit all and and then at 00:06:17.160 --> 00:06:19.510 align:start position:0% size does not fit all and and then at the<00:06:17.280> beginning<00:06:17.400> we<00:06:17.880> only<00:06:18.120> had<00:06:18.419> this<00:06:18.840> full<00:06:19.139> node 00:06:19.510 --> 00:06:19.520 align:start position:0% the beginning we only had this full node 00:06:19.520 --> 00:06:21.950 align:start position:0% the beginning we only had this full node functionality<00:06:20.520> where<00:06:20.940> like<00:06:21.240> the<00:06:21.539> nodes<00:06:21.720> were 00:06:21.950 --> 00:06:21.960 align:start position:0% functionality where like the nodes were 00:06:21.960 --> 00:06:24.129 align:start position:0% functionality where like the nodes were storing<00:06:22.319> data<00:06:22.740> it<00:06:23.039> was<00:06:23.160> also<00:06:23.400> used<00:06:23.639> for 00:06:24.129 --> 00:06:24.139 align:start position:0% storing data it was also used for 00:06:24.139 --> 00:06:28.010 align:start position:0% storing data it was also used for accessing<00:06:25.139> the<00:06:25.319> network<00:06:25.560> and<00:06:26.460> uh<00:06:27.419> like 00:06:28.010 --> 00:06:28.020 align:start position:0% accessing the network and uh like 00:06:28.020 --> 00:06:29.809 align:start position:0% accessing the network and uh like basically<00:06:28.380> all<00:06:28.620> the<00:06:28.800> functionality<00:06:29.280> were<00:06:29.580> in 00:06:29.809 --> 00:06:29.819 align:start position:0% basically all the functionality were in 00:06:29.819 --> 00:06:31.730 align:start position:0% basically all the functionality were in the<00:06:29.940> full<00:06:30.060> nodes<00:06:30.479> but<00:06:31.020> eventually<00:06:31.500> we 00:06:31.730 --> 00:06:31.740 align:start position:0% the full nodes but eventually we 00:06:31.740 --> 00:06:34.249 align:start position:0% the full nodes but eventually we realized<00:06:32.220> that<00:06:33.000> most<00:06:33.660> people<00:06:33.840> won't 00:06:34.249 --> 00:06:34.259 align:start position:0% realized that most people won't 00:06:34.259 --> 00:06:36.110 align:start position:0% realized that most people won't necessarily<00:06:34.740> need<00:06:35.039> a<00:06:35.520> full<00:06:35.759> node 00:06:36.110 --> 00:06:36.120 align:start position:0% necessarily need a full node 00:06:36.120 --> 00:06:39.590 align:start position:0% necessarily need a full node functionality<00:06:36.660> so<00:06:37.560> we<00:06:38.220> separated<00:06:38.819> like<00:06:39.240> into 00:06:39.590 --> 00:06:39.600 align:start position:0% functionality so we separated like into 00:06:39.600 --> 00:06:42.590 align:start position:0% functionality so we separated like into different<00:06:40.080> ways<00:06:40.800> how<00:06:41.039> you<00:06:41.220> can<00:06:41.340> access<00:06:41.600> the 00:06:42.590 --> 00:06:42.600 align:start position:0% different ways how you can access the 00:06:42.600 --> 00:06:45.830 align:start position:0% different ways how you can access the the<00:06:42.660> data<00:06:43.259> on<00:06:43.560> the<00:06:43.620> Swarm<00:06:43.979> Network<00:06:44.539> there<00:06:45.539> is<00:06:45.720> a 00:06:45.830 --> 00:06:45.840 align:start position:0% the data on the Swarm Network there is a 00:06:45.840 --> 00:06:49.610 align:start position:0% the data on the Swarm Network there is a gateway<00:06:46.199> that<00:06:46.560> we<00:06:46.740> provide<00:06:47.360> as<00:06:48.360> a<00:06:48.660> as<00:06:49.259> a<00:06:49.500> free 00:06:49.610 --> 00:06:49.620 align:start position:0% gateway that we provide as a as a free 00:06:49.620 --> 00:06:51.950 align:start position:0% gateway that we provide as a as a free trial<00:06:49.979> version<00:06:50.280> so<00:06:51.120> to<00:06:51.300> speak<00:06:51.479> there's<00:06:51.720> an 00:06:51.950 --> 00:06:51.960 align:start position:0% trial version so to speak there's an 00:06:51.960 --> 00:06:54.170 align:start position:0% trial version so to speak there's an ultra<00:06:52.319> light<00:06:52.440> node<00:06:52.860> which<00:06:53.580> you<00:06:53.819> can<00:06:54.000> install 00:06:54.170 --> 00:06:54.180 align:start position:0% ultra light node which you can install 00:06:54.180 --> 00:06:56.570 align:start position:0% ultra light node which you can install on<00:06:54.600> your<00:06:54.780> laptop<00:06:55.139> and<00:06:55.740> then<00:06:55.919> it<00:06:56.100> doesn't<00:06:56.280> use 00:06:56.570 --> 00:06:56.580 align:start position:0% on your laptop and then it doesn't use 00:06:56.580 --> 00:06:59.029 align:start position:0% on your laptop and then it doesn't use too<00:06:56.940> much<00:06:57.180> resources<00:06:57.780> but<00:06:58.259> then<00:06:58.500> with<00:06:58.800> that 00:06:59.029 --> 00:06:59.039 align:start position:0% too much resources but then with that 00:06:59.039 --> 00:07:01.490 align:start position:0% too much resources but then with that you<00:06:59.639> cannot<00:06:59.940> upload<00:07:00.539> to<00:07:00.720> the<00:07:00.900> network<00:07:01.020> because 00:07:01.490 --> 00:07:01.500 align:start position:0% you cannot upload to the network because 00:07:01.500 --> 00:07:03.290 align:start position:0% you cannot upload to the network because in<00:07:01.800> order<00:07:01.919> to<00:07:02.160> upload<00:07:02.520> to<00:07:02.639> the<00:07:02.819> network<00:07:02.940> you 00:07:03.290 --> 00:07:03.300 align:start position:0% in order to upload to the network you 00:07:03.300 --> 00:07:05.450 align:start position:0% in order to upload to the network you will<00:07:03.539> have<00:07:03.720> to<00:07:03.900> pay<00:07:04.080> for<00:07:04.380> the<00:07:04.740> data<00:07:05.100> for 00:07:05.450 --> 00:07:05.460 align:start position:0% will have to pay for the data for 00:07:05.460 --> 00:07:09.529 align:start position:0% will have to pay for the data for someone<00:07:06.000> to<00:07:06.539> store<00:07:06.960> it<00:07:07.199> for<00:07:07.380> you<00:07:07.580> and<00:07:08.580> that's 00:07:09.529 --> 00:07:09.539 align:start position:0% someone to store it for you and that's 00:07:09.539 --> 00:07:11.090 align:start position:0% someone to store it for you and that's something<00:07:09.840> that<00:07:10.199> you<00:07:10.319> can<00:07:10.440> do<00:07:10.560> with<00:07:10.740> a<00:07:10.919> light 00:07:11.090 --> 00:07:11.100 align:start position:0% something that you can do with a light 00:07:11.100 --> 00:07:13.850 align:start position:0% something that you can do with a light node<00:07:11.460> and<00:07:12.060> I<00:07:12.300> will 00:07:13.850 --> 00:07:13.860 align:start position:0% node and I will 00:07:13.860 --> 00:07:16.249 align:start position:0% node and I will um I<00:07:14.100> will<00:07:14.340> install<00:07:14.580> this<00:07:15.479> on<00:07:15.840> my<00:07:16.080> computer 00:07:16.249 --> 00:07:16.259 align:start position:0% um I will install this on my computer 00:07:16.259 --> 00:07:18.170 align:start position:0% um I will install this on my computer like<00:07:16.800> we<00:07:17.160> will<00:07:17.340> see<00:07:17.520> like<00:07:17.699> how<00:07:17.940> the<00:07:18.060> internet 00:07:18.170 --> 00:07:18.180 align:start position:0% like we will see like how the internet 00:07:18.180 --> 00:07:21.909 align:start position:0% like we will see like how the internet works<00:07:18.780> so<00:07:19.440> far<00:07:19.620> it<00:07:19.860> was<00:07:20.099> not<00:07:20.400> always<00:07:20.759> great<00:07:21.180> but 00:07:21.909 --> 00:07:21.919 align:start position:0% works so far it was not always great but 00:07:21.919 --> 00:07:26.450 align:start position:0% works so far it was not always great but let's<00:07:22.919> uh<00:07:23.880> I<00:07:24.360> hope<00:07:24.479> someone<00:07:24.900> like<00:07:25.740> sacrificed 00:07:26.450 --> 00:07:26.460 align:start position:0% let's uh I hope someone like sacrificed 00:07:26.460 --> 00:07:28.730 align:start position:0% let's uh I hope someone like sacrificed some<00:07:26.639> goals<00:07:27.060> to<00:07:27.180> the<00:07:27.360> demo<00:07:27.599> Gods<00:07:27.960> today<00:07:28.259> so 00:07:28.730 --> 00:07:28.740 align:start position:0% some goals to the demo Gods today so 00:07:28.740 --> 00:07:32.450 align:start position:0% some goals to the demo Gods today so that<00:07:28.919> we<00:07:29.220> can<00:07:29.400> have<00:07:30.120> some<00:07:30.360> luck<00:07:30.539> with<00:07:30.780> that 00:07:32.450 --> 00:07:32.460 align:start position:0% that we can have some luck with that 00:07:32.460 --> 00:07:35.089 align:start position:0% that we can have some luck with that um and<00:07:33.300> yeah<00:07:33.419> so<00:07:33.599> we<00:07:33.840> we<00:07:34.139> basically<00:07:34.500> realized 00:07:35.089 --> 00:07:35.099 align:start position:0% um and yeah so we we basically realized 00:07:35.099 --> 00:07:38.390 align:start position:0% um and yeah so we we basically realized that<00:07:35.660> if<00:07:36.660> you<00:07:36.780> want<00:07:36.960> to<00:07:37.080> see<00:07:37.259> like<00:07:37.500> a<00:07:37.800> web<00:07:37.979> 2 00:07:38.390 --> 00:07:38.400 align:start position:0% that if you want to see like a web 2 00:07:38.400 --> 00:07:41.390 align:start position:0% that if you want to see like a web 2 kind<00:07:38.819> of<00:07:38.940> view<00:07:39.180> of<00:07:39.479> like<00:07:39.720> these<00:07:40.259> uh<00:07:41.039> different 00:07:41.390 --> 00:07:41.400 align:start position:0% kind of view of like these uh different 00:07:41.400 --> 00:07:45.170 align:start position:0% kind of view of like these uh different products<00:07:42.300> packaging<00:07:43.259> then<00:07:43.800> I<00:07:44.460> can<00:07:44.580> show<00:07:45.000> you 00:07:45.170 --> 00:07:45.180 align:start position:0% products packaging then I can show you 00:07:45.180 --> 00:07:46.749 align:start position:0% products packaging then I can show you this<00:07:45.360> that<00:07:45.720> basically 00:07:46.749 --> 00:07:46.759 align:start position:0% this that basically 00:07:46.759 --> 00:07:49.490 align:start position:0% this that basically there<00:07:47.759> is<00:07:47.880> a<00:07:48.000> free<00:07:48.120> trial<00:07:48.539> on<00:07:48.960> the<00:07:49.139> Gateway 00:07:49.490 --> 00:07:49.500 align:start position:0% there is a free trial on the Gateway 00:07:49.500 --> 00:07:51.230 align:start position:0% there is a free trial on the Gateway that<00:07:49.860> you<00:07:49.919> can<00:07:50.039> access<00:07:50.220> from<00:07:50.580> the<00:07:50.699> browser<00:07:51.060> you 00:07:51.230 --> 00:07:51.240 align:start position:0% that you can access from the browser you 00:07:51.240 --> 00:07:52.850 align:start position:0% that you can access from the browser you don't<00:07:51.419> need<00:07:51.599> to<00:07:51.780> install<00:07:51.900> anything<00:07:52.259> you<00:07:52.800> can 00:07:52.850 --> 00:07:52.860 align:start position:0% don't need to install anything you can 00:07:52.860 --> 00:07:55.129 align:start position:0% don't need to install anything you can just<00:07:53.039> go<00:07:53.220> to<00:07:53.400> this<00:07:53.580> website<00:07:54.360> you<00:07:54.660> can<00:07:54.780> upload 00:07:55.129 --> 00:07:55.139 align:start position:0% just go to this website you can upload 00:07:55.139 --> 00:07:57.529 align:start position:0% just go to this website you can upload it<00:07:55.380> or<00:07:55.620> download<00:07:55.860> data<00:07:56.340> but<00:07:56.580> it's<00:07:56.759> limited<00:07:57.180> to 00:07:57.529 --> 00:07:57.539 align:start position:0% it or download data but it's limited to 00:07:57.539 --> 00:08:00.710 align:start position:0% it or download data but it's limited to certain<00:07:58.139> size<00:07:58.500> and<00:07:58.800> then<00:07:58.979> also<00:07:59.340> that<00:07:59.639> is<00:08:00.479> the 00:08:00.710 --> 00:08:00.720 align:start position:0% certain size and then also that is the 00:08:00.720 --> 00:08:02.689 align:start position:0% certain size and then also that is the nature<00:08:00.960> of<00:08:01.080> the<00:08:01.259> gateways<00:08:01.740> is<00:08:01.860> the<00:08:02.039> Gateway 00:08:02.689 --> 00:08:02.699 align:start position:0% nature of the gateways is the Gateway 00:08:02.699 --> 00:08:06.529 align:start position:0% nature of the gateways is the Gateway operators<00:08:03.300> must<00:08:04.139> uh<00:08:04.800> you<00:08:05.400> know<00:08:05.460> comply<00:08:06.419> with 00:08:06.529 --> 00:08:06.539 align:start position:0% operators must uh you know comply with 00:08:06.539 --> 00:08:08.629 align:start position:0% operators must uh you know comply with the<00:08:06.780> low<00:08:06.900> and<00:08:07.199> then<00:08:07.440> remove<00:08:07.680> some<00:08:08.099> data<00:08:08.520> and 00:08:08.629 --> 00:08:08.639 align:start position:0% the low and then remove some data and 00:08:08.639 --> 00:08:10.730 align:start position:0% the low and then remove some data and then<00:08:08.880> at<00:08:09.479> that<00:08:09.660> point<00:08:09.840> like<00:08:10.139> censorship 00:08:10.730 --> 00:08:10.740 align:start position:0% then at that point like censorship 00:08:10.740 --> 00:08:12.710 align:start position:0% then at that point like censorship resistance<00:08:11.340> cannot<00:08:11.759> be<00:08:12.060> maintained 00:08:12.710 --> 00:08:12.720 align:start position:0% resistance cannot be maintained 00:08:12.720 --> 00:08:13.610 align:start position:0% resistance cannot be maintained organized 00:08:13.610 --> 00:08:13.620 align:start position:0% organized 00:08:13.620 --> 00:08:16.010 align:start position:0% organized if<00:08:14.280> you<00:08:14.460> want<00:08:14.699> to<00:08:14.819> access<00:08:15.180> directly<00:08:15.780> the 00:08:16.010 --> 00:08:16.020 align:start position:0% if you want to access directly the 00:08:16.020 --> 00:08:18.350 align:start position:0% if you want to access directly the network<00:08:16.199> then<00:08:16.740> the<00:08:17.099> the<00:08:17.160> recommended<00:08:17.940> way<00:08:18.120> to 00:08:18.350 --> 00:08:18.360 align:start position:0% network then the the recommended way to 00:08:18.360 --> 00:08:20.990 align:start position:0% network then the the recommended way to do<00:08:18.479> that<00:08:18.660> is<00:08:18.840> by<00:08:19.199> using<00:08:19.620> either<00:08:20.340> the<00:08:20.639> Swarm 00:08:20.990 --> 00:08:21.000 align:start position:0% do that is by using either the Swarm 00:08:21.000 --> 00:08:22.850 align:start position:0% do that is by using either the Swarm desktop<00:08:21.300> app<00:08:21.539> which<00:08:21.780> is<00:08:21.960> like<00:08:22.199> easy<00:08:22.500> to 00:08:22.850 --> 00:08:22.860 align:start position:0% desktop app which is like easy to 00:08:22.860 --> 00:08:25.309 align:start position:0% desktop app which is like easy to install<00:08:23.039> and<00:08:23.520> you<00:08:24.360> can<00:08:24.419> install<00:08:24.599> it<00:08:24.900> on<00:08:25.080> your 00:08:25.309 --> 00:08:25.319 align:start position:0% install and you can install it on your 00:08:25.319 --> 00:08:28.070 align:start position:0% install and you can install it on your laptop<00:08:25.740> or<00:08:26.460> desktop<00:08:26.819> computers<00:08:27.360> and<00:08:27.900> then 00:08:28.070 --> 00:08:28.080 align:start position:0% laptop or desktop computers and then 00:08:28.080 --> 00:08:30.230 align:start position:0% laptop or desktop computers and then most<00:08:28.319> we<00:08:28.680> recommend<00:08:29.340> this<00:08:29.460> to<00:08:29.699> most<00:08:29.940> people 00:08:30.230 --> 00:08:30.240 align:start position:0% most we recommend this to most people 00:08:30.240 --> 00:08:33.050 align:start position:0% most we recommend this to most people that<00:08:30.780> want<00:08:31.139> to<00:08:31.319> create<00:08:31.700> data<00:08:32.700> and<00:08:32.820> store 00:08:33.050 --> 00:08:33.060 align:start position:0% that want to create data and store 00:08:33.060 --> 00:08:35.209 align:start position:0% that want to create data and store Network<00:08:33.419> or<00:08:34.020> just<00:08:34.260> want<00:08:34.380> to<00:08:34.560> Simply<00:08:34.919> access 00:08:35.209 --> 00:08:35.219 align:start position:0% Network or just want to Simply access 00:08:35.219 --> 00:08:37.550 align:start position:0% Network or just want to Simply access the<00:08:35.580> data<00:08:35.880> on<00:08:36.000> the<00:08:36.180> network 00:08:37.550 --> 00:08:37.560 align:start position:0% the data on the network 00:08:37.560 --> 00:08:40.550 align:start position:0% the data on the network and<00:08:38.159> it<00:08:38.459> comes<00:08:39.120> into<00:08:39.300> varieties<00:08:40.140> like<00:08:40.440> this 00:08:40.550 --> 00:08:40.560 align:start position:0% and it comes into varieties like this 00:08:40.560 --> 00:08:44.329 align:start position:0% and it comes into varieties like this ultra<00:08:40.979> light<00:08:41.159> node<00:08:41.520> which<00:08:42.360> does<00:08:43.080> not<00:08:43.339> require 00:08:44.329 --> 00:08:44.339 align:start position:0% ultra light node which does not require 00:08:44.339 --> 00:08:46.250 align:start position:0% ultra light node which does not require you<00:08:44.700> to<00:08:44.880> do<00:08:45.060> any<00:08:45.240> kind<00:08:45.420> of<00:08:45.540> transactions<00:08:46.080> on 00:08:46.250 --> 00:08:46.260 align:start position:0% you to do any kind of transactions on 00:08:46.260 --> 00:08:48.170 align:start position:0% you to do any kind of transactions on the<00:08:46.380> blockchain<00:08:46.740> but<00:08:47.220> that's<00:08:47.459> limited<00:08:48.000> so 00:08:48.170 --> 00:08:48.180 align:start position:0% the blockchain but that's limited so 00:08:48.180 --> 00:08:50.269 align:start position:0% the blockchain but that's limited so then<00:08:48.360> you<00:08:48.540> can<00:08:48.660> only<00:08:48.839> access<00:08:49.440> data<00:08:49.980> but<00:08:50.100> not 00:08:50.269 --> 00:08:50.279 align:start position:0% then you can only access data but not 00:08:50.279 --> 00:08:52.310 align:start position:0% then you can only access data but not upload<00:08:50.700> if<00:08:51.180> you<00:08:51.300> want<00:08:51.480> to<00:08:51.600> upload<00:08:51.899> you<00:08:52.200> will 00:08:52.310 --> 00:08:52.320 align:start position:0% upload if you want to upload you will 00:08:52.320 --> 00:08:55.310 align:start position:0% upload if you want to upload you will have<00:08:52.500> to<00:08:52.740> buy<00:08:52.920> the<00:08:53.399> the<00:08:54.000> Swarm<00:08:54.480> native<00:08:54.779> token 00:08:55.310 --> 00:08:55.320 align:start position:0% have to buy the the Swarm native token 00:08:55.320 --> 00:08:57.769 align:start position:0% have to buy the the Swarm native token which<00:08:55.680> is<00:08:55.800> called<00:08:55.920> Bzz<00:08:56.580> and<00:08:57.180> then<00:08:57.360> with<00:08:57.600> that 00:08:57.769 --> 00:08:57.779 align:start position:0% which is called Bzz and then with that 00:08:57.779 --> 00:08:59.230 align:start position:0% which is called Bzz and then with that you<00:08:58.140> can<00:08:58.260> buy 00:08:59.230 --> 00:08:59.240 align:start position:0% you can buy 00:08:59.240 --> 00:09:01.970 align:start position:0% you can buy capacity<00:09:00.240> on<00:09:00.540> the<00:09:00.660> network<00:09:00.779> so<00:09:01.320> that<00:09:01.560> you<00:09:01.920> can 00:09:01.970 --> 00:09:01.980 align:start position:0% capacity on the network so that you can 00:09:01.980 --> 00:09:03.769 align:start position:0% capacity on the network so that you can store<00:09:02.220> your<00:09:02.459> data<00:09:02.820> and<00:09:02.940> with<00:09:03.120> the<00:09:03.300> full<00:09:03.420> node 00:09:03.769 --> 00:09:03.779 align:start position:0% store your data and with the full node 00:09:03.779 --> 00:09:05.570 align:start position:0% store your data and with the full node you<00:09:04.620> can 00:09:05.570 --> 00:09:05.580 align:start position:0% you can 00:09:05.580 --> 00:09:08.990 align:start position:0% you can it<00:09:06.120> has<00:09:06.300> the<00:09:06.540> full<00:09:06.720> functionality<00:09:07.580> but<00:09:08.580> it 00:09:08.990 --> 00:09:09.000 align:start position:0% it has the full functionality but it 00:09:09.000 --> 00:09:11.930 align:start position:0% it has the full functionality but it also<00:09:09.300> means<00:09:09.600> that<00:09:09.899> you<00:09:10.200> need<00:09:10.440> to<00:09:10.680> run<00:09:10.920> this<00:09:11.279> on 00:09:11.930 --> 00:09:11.940 align:start position:0% also means that you need to run this on 00:09:11.940 --> 00:09:14.710 align:start position:0% also means that you need to run this on a<00:09:12.420> more<00:09:12.720> like<00:09:12.959> more<00:09:13.260> slightly<00:09:13.500> on<00:09:13.680> a<00:09:13.800> separate 00:09:14.710 --> 00:09:14.720 align:start position:0% a more like more slightly on a separate 00:09:14.720 --> 00:09:17.570 align:start position:0% a more like more slightly on a separate server<00:09:15.720> because<00:09:16.200> like<00:09:16.560> if<00:09:16.860> you<00:09:16.980> run<00:09:17.160> the<00:09:17.399> full 00:09:17.570 --> 00:09:17.580 align:start position:0% server because like if you run the full 00:09:17.580 --> 00:09:19.550 align:start position:0% server because like if you run the full node<00:09:17.940> on<00:09:18.120> your<00:09:18.300> laptop<00:09:18.660> machine<00:09:18.899> for<00:09:19.320> example 00:09:19.550 --> 00:09:19.560 align:start position:0% node on your laptop machine for example 00:09:19.560 --> 00:09:21.230 align:start position:0% node on your laptop machine for example it<00:09:19.980> uses 00:09:21.230 --> 00:09:21.240 align:start position:0% it uses 00:09:21.240 --> 00:09:24.170 align:start position:0% it uses it may<00:09:21.839> use<00:09:22.200> your<00:09:22.980> network<00:09:23.160> connection<00:09:23.580> in 00:09:24.170 --> 00:09:24.180 align:start position:0% it may use your network connection in 00:09:24.180 --> 00:09:25.850 align:start position:0% it may use your network connection in times<00:09:24.300> that<00:09:24.600> you<00:09:24.779> don't<00:09:24.959> want<00:09:25.140> to<00:09:25.320> it<00:09:25.500> has<00:09:25.680> to 00:09:25.850 --> 00:09:25.860 align:start position:0% times that you don't want to it has to 00:09:25.860 --> 00:09:28.850 align:start position:0% times that you don't want to it has to be<00:09:25.980> around<00:09:26.160> 24<00:09:26.580> 7<00:09:27.120> because<00:09:28.019> then<00:09:28.440> that 00:09:28.850 --> 00:09:28.860 align:start position:0% be around 24 7 because then that 00:09:28.860 --> 00:09:30.650 align:start position:0% be around 24 7 because then that provides<00:09:29.220> the<00:09:29.459> availability<00:09:29.820> for<00:09:30.240> the<00:09:30.360> data 00:09:30.650 --> 00:09:30.660 align:start position:0% provides the availability for the data 00:09:30.660 --> 00:09:32.449 align:start position:0% provides the availability for the data for<00:09:30.899> others<00:09:31.200> on<00:09:31.380> the<00:09:31.500> network<00:09:31.680> so<00:09:32.040> if<00:09:32.279> you 00:09:32.449 --> 00:09:32.459 align:start position:0% for others on the network so if you 00:09:32.459 --> 00:09:35.269 align:start position:0% for others on the network so if you close<00:09:32.640> your<00:09:32.880> laptop<00:09:33.240> then<00:09:33.860> I<00:09:34.860> will<00:09:34.980> talk<00:09:35.160> about 00:09:35.269 --> 00:09:35.279 align:start position:0% close your laptop then I will talk about 00:09:35.279 --> 00:09:37.910 align:start position:0% close your laptop then I will talk about later<00:09:35.640> like<00:09:36.060> you<00:09:36.839> wouldn't<00:09:37.019> be<00:09:37.560> able<00:09:37.740> to 00:09:37.910 --> 00:09:37.920 align:start position:0% later like you wouldn't be able to 00:09:37.920 --> 00:09:42.050 align:start position:0% later like you wouldn't be able to participate<00:09:38.580> in<00:09:38.880> the<00:09:39.180> in<00:09:39.899> the<00:09:40.339> earning<00:09:41.339> part 00:09:42.050 --> 00:09:42.060 align:start position:0% participate in the in the earning part 00:09:42.060 --> 00:09:43.490 align:start position:0% participate in the in the earning part of<00:09:42.360> the 00:09:43.490 --> 00:09:43.500 align:start position:0% of the 00:09:43.500 --> 00:09:46.670 align:start position:0% of the thing<00:09:44.100> so<00:09:44.820> like<00:09:45.000> how<00:09:45.180> you<00:09:45.600> can<00:09:45.720> earn<00:09:46.019> money<00:09:46.260> by 00:09:46.670 --> 00:09:46.680 align:start position:0% thing so like how you can earn money by 00:09:46.680 --> 00:09:49.670 align:start position:0% thing so like how you can earn money by uh<00:09:47.459> by<00:09:47.760> storing<00:09:48.120> data<00:09:48.420> for<00:09:48.540> other<00:09:48.720> people 00:09:49.670 --> 00:09:49.680 align:start position:0% uh by storing data for other people 00:09:49.680 --> 00:09:53.030 align:start position:0% uh by storing data for other people and<00:09:50.820> um<00:09:50.820> so<00:09:51.540> yeah<00:09:51.660> like<00:09:51.899> we<00:09:52.200> realized<00:09:52.560> that<00:09:52.800> the 00:09:53.030 --> 00:09:53.040 align:start position:0% and um so yeah like we realized that the 00:09:53.040 --> 00:09:55.910 align:start position:0% and um so yeah like we realized that the the<00:09:53.279> full<00:09:53.519> node<00:09:53.880> is<00:09:54.120> not<00:09:54.360> a<00:09:55.140> very<00:09:55.440> good<00:09:55.680> choice 00:09:55.910 --> 00:09:55.920 align:start position:0% the full node is not a very good choice 00:09:55.920 --> 00:09:58.190 align:start position:0% the full node is not a very good choice for<00:09:56.279> most<00:09:56.459> people<00:09:56.820> having<00:09:57.420> running<00:09:57.779> it<00:09:58.019> on 00:09:58.190 --> 00:09:58.200 align:start position:0% for most people having running it on 00:09:58.200 --> 00:10:01.070 align:start position:0% for most people having running it on their<00:09:58.380> laptops<00:09:58.860> and<00:09:58.980> stuff<00:09:59.220> so<00:09:59.459> for<00:09:59.880> that<00:10:00.120> we 00:10:01.070 --> 00:10:01.080 align:start position:0% their laptops and stuff so for that we 00:10:01.080 --> 00:10:03.710 align:start position:0% their laptops and stuff so for that we recommend<00:10:01.620> the<00:10:01.920> desktop<00:10:02.459> app<00:10:02.700> and<00:10:02.940> the<00:10:03.180> full 00:10:03.710 --> 00:10:03.720 align:start position:0% recommend the desktop app and the full 00:10:03.720 --> 00:10:06.050 align:start position:0% recommend the desktop app and the full node<00:10:04.019> we<00:10:04.260> recommend<00:10:04.620> people<00:10:04.860> who<00:10:05.339> are<00:10:05.519> more 00:10:06.050 --> 00:10:06.060 align:start position:0% node we recommend people who are more 00:10:06.060 --> 00:10:09.290 align:start position:0% node we recommend people who are more seriously<00:10:06.480> want<00:10:06.720> to<00:10:07.459> store<00:10:08.459> data<00:10:09.000> for<00:10:09.120> other 00:10:09.290 --> 00:10:09.300 align:start position:0% seriously want to store data for other 00:10:09.300 --> 00:10:12.949 align:start position:0% seriously want to store data for other people<00:10:09.800> and<00:10:10.800> then<00:10:10.980> so<00:10:11.519> maybe<00:10:12.060> to<00:10:12.360> recap<00:10:12.660> like 00:10:12.949 --> 00:10:12.959 align:start position:0% people and then so maybe to recap like 00:10:12.959 --> 00:10:14.810 align:start position:0% people and then so maybe to recap like this<00:10:13.140> like<00:10:13.380> the<00:10:13.620> light<00:10:13.800> node<00:10:14.160> considerations 00:10:14.810 --> 00:10:14.820 align:start position:0% this like the light node considerations 00:10:14.820 --> 00:10:17.389 align:start position:0% this like the light node considerations is<00:10:15.240> lightweight<00:10:15.899> use<00:10:16.320> only<00:10:16.500> resources<00:10:17.100> if<00:10:17.279> you 00:10:17.389 --> 00:10:17.399 align:start position:0% is lightweight use only resources if you 00:10:17.399 --> 00:10:19.610 align:start position:0% is lightweight use only resources if you request<00:10:17.700> them<00:10:17.940> on<00:10:18.660> demand<00:10:19.019> so<00:10:19.320> it<00:10:19.500> doesn't 00:10:19.610 --> 00:10:19.620 align:start position:0% request them on demand so it doesn't 00:10:19.620 --> 00:10:22.250 align:start position:0% request them on demand so it doesn't have<00:10:19.800> to<00:10:19.980> be<00:10:20.100> running<00:10:20.279> 24<00:10:20.580> 7<00:10:21.060> and<00:10:21.959> you<00:10:22.140> can 00:10:22.250 --> 00:10:22.260 align:start position:0% have to be running 24 7 and you can 00:10:22.260 --> 00:10:24.590 align:start position:0% have to be running 24 7 and you can start<00:10:22.380> without<00:10:22.680> a<00:10:22.980> penny<00:10:23.279> so<00:10:23.880> that<00:10:24.060> means<00:10:24.360> that 00:10:24.590 --> 00:10:24.600 align:start position:0% start without a penny so that means that 00:10:24.600 --> 00:10:26.690 align:start position:0% start without a penny so that means that you<00:10:24.839> don't<00:10:24.959> need<00:10:25.260> to<00:10:25.560> make<00:10:25.800> any<00:10:26.040> transactions 00:10:26.690 --> 00:10:26.700 align:start position:0% you don't need to make any transactions 00:10:26.700 --> 00:10:30.050 align:start position:0% you don't need to make any transactions to<00:10:27.000> start<00:10:27.180> using<00:10:27.600> it<00:10:27.720> but<00:10:29.040> um<00:10:29.040> later<00:10:29.459> you<00:10:29.820> can 00:10:30.050 --> 00:10:30.060 align:start position:0% to start using it but um later you can 00:10:30.060 --> 00:10:32.870 align:start position:0% to start using it but um later you can unlock<00:10:30.600> it<00:10:30.899> with<00:10:31.080> more<00:10:31.320> functionality<00:10:31.980> and 00:10:32.870 --> 00:10:32.880 align:start position:0% unlock it with more functionality and 00:10:32.880 --> 00:10:35.150 align:start position:0% unlock it with more functionality and the<00:10:33.120> full<00:10:33.480> node<00:10:33.899> has<00:10:34.260> different<00:10:34.560> Hardware 00:10:35.150 --> 00:10:35.160 align:start position:0% the full node has different Hardware 00:10:35.160 --> 00:10:38.090 align:start position:0% the full node has different Hardware requirements<00:10:36.000> so<00:10:36.360> like<00:10:36.720> currently<00:10:37.560> we 00:10:38.090 --> 00:10:38.100 align:start position:0% requirements so like currently we 00:10:38.100 --> 00:10:40.190 align:start position:0% requirements so like currently we recommend<00:10:38.760> that<00:10:38.940> you<00:10:39.120> can<00:10:39.300> start<00:10:39.540> running<00:10:39.839> at 00:10:40.190 --> 00:10:40.200 align:start position:0% recommend that you can start running at 00:10:40.200 --> 00:10:44.509 align:start position:0% recommend that you can start running at an<00:10:40.440> Raspberry<00:10:40.800> Pi<00:10:41.100> with<00:10:41.399> like<00:10:41.760> 4G<00:10:42.360> Ram<00:10:42.860> 70<00:10:43.860> gigs 00:10:44.509 --> 00:10:44.519 align:start position:0% an Raspberry Pi with like 4G Ram 70 gigs 00:10:44.519 --> 00:10:47.150 align:start position:0% an Raspberry Pi with like 4G Ram 70 gigs of<00:10:44.700> disk<00:10:45.480> space<00:10:45.660> it<00:10:45.959> has<00:10:46.140> to<00:10:46.260> be<00:10:46.320> an<00:10:46.440> SSD<00:10:46.920> so 00:10:47.150 --> 00:10:47.160 align:start position:0% of disk space it has to be an SSD so 00:10:47.160 --> 00:10:48.350 align:start position:0% of disk space it has to be an SSD so most<00:10:47.399> likely<00:10:47.579> if<00:10:47.760> you<00:10:47.880> want<00:10:48.000> to<00:10:48.120> use<00:10:48.240> a 00:10:48.350 --> 00:10:48.360 align:start position:0% most likely if you want to use a 00:10:48.360 --> 00:10:50.690 align:start position:0% most likely if you want to use a Raspberry<00:10:48.720> Pi<00:10:48.959> you<00:10:49.140> have<00:10:49.260> to<00:10:49.740> connect<00:10:50.279> your 00:10:50.690 --> 00:10:50.700 align:start position:0% Raspberry Pi you have to connect your 00:10:50.700 --> 00:10:53.210 align:start position:0% Raspberry Pi you have to connect your external<00:10:51.300> SSD<00:10:51.839> to<00:10:52.079> that<00:10:52.260> because<00:10:52.620> it's<00:10:52.980> quite 00:10:53.210 --> 00:10:53.220 align:start position:0% external SSD to that because it's quite 00:10:53.220 --> 00:10:55.009 align:start position:0% external SSD to that because it's quite demanding<00:10:53.760> on<00:10:54.000> the<00:10:54.180> disk 00:10:55.009 --> 00:10:55.019 align:start position:0% demanding on the disk 00:10:55.019 --> 00:10:58.310 align:start position:0% demanding on the disk storage<00:10:55.500> system<00:10:56.040> should<00:10:56.519> be<00:10:56.720> it's<00:10:57.720> always<00:10:57.899> on 00:10:58.310 --> 00:10:58.320 align:start position:0% storage system should be it's always on 00:10:58.320 --> 00:11:02.509 align:start position:0% storage system should be it's always on so<00:10:58.560> it's<00:10:58.860> supposed<00:10:59.279> to<00:10:59.459> be<00:10:59.700> run<00:10:59.940> 24<00:11:00.360> 7<00:11:00.980> and<00:11:01.980> you 00:11:02.509 --> 00:11:02.519 align:start position:0% so it's supposed to be run 24 7 and you 00:11:02.519 --> 00:11:04.670 align:start position:0% so it's supposed to be run 24 7 and you have<00:11:02.760> to<00:11:02.880> do<00:11:03.060> one<00:11:03.300> transaction<00:11:03.779> in<00:11:04.320> order<00:11:04.440> to 00:11:04.670 --> 00:11:04.680 align:start position:0% have to do one transaction in order to 00:11:04.680 --> 00:11:08.389 align:start position:0% have to do one transaction in order to participate<00:11:05.279> in<00:11:05.579> the<00:11:06.140> uh<00:11:07.140> in<00:11:07.560> being<00:11:08.040> a<00:11:08.220> full 00:11:08.389 --> 00:11:08.399 align:start position:0% participate in the uh in being a full 00:11:08.399 --> 00:11:11.509 align:start position:0% participate in the uh in being a full node<00:11:08.760> basically<00:11:09.600> you<00:11:09.899> have<00:11:10.019> to<00:11:10.279> deploy<00:11:11.279> a 00:11:11.509 --> 00:11:11.519 align:start position:0% node basically you have to deploy a 00:11:11.519 --> 00:11:14.530 align:start position:0% node basically you have to deploy a checkbook<00:11:11.880> contract<00:11:12.360> so<00:11:12.720> that<00:11:12.959> you<00:11:13.380> can 00:11:14.530 --> 00:11:14.540 align:start position:0% checkbook contract so that you can 00:11:14.540 --> 00:11:16.910 align:start position:0% checkbook contract so that you can participate<00:11:15.540> in<00:11:15.899> something<00:11:16.140> that<00:11:16.500> we<00:11:16.680> call 00:11:16.910 --> 00:11:16.920 align:start position:0% participate in something that we call 00:11:16.920 --> 00:11:20.569 align:start position:0% participate in something that we call the<00:11:17.300> bandwidth<00:11:18.300> incentives<00:11:18.899> so<00:11:19.620> let<00:11:20.220> me<00:11:20.339> just 00:11:20.569 --> 00:11:20.579 align:start position:0% the bandwidth incentives so let me just 00:11:20.579 --> 00:11:22.970 align:start position:0% the bandwidth incentives so let me just talk<00:11:20.760> a<00:11:20.940> bit<00:11:21.120> about<00:11:21.300> that<00:11:21.720> so<00:11:22.380> basically<00:11:22.740> there 00:11:22.970 --> 00:11:22.980 align:start position:0% talk a bit about that so basically there 00:11:22.980 --> 00:11:24.710 align:start position:0% talk a bit about that so basically there are<00:11:23.100> two<00:11:23.220> kind<00:11:23.399> of<00:11:23.579> incentives<00:11:24.240> there<00:11:24.540> is 00:11:24.710 --> 00:11:24.720 align:start position:0% are two kind of incentives there is 00:11:24.720 --> 00:11:27.490 align:start position:0% are two kind of incentives there is bandwidth<00:11:25.320> incentives<00:11:25.860> that<00:11:26.820> is<00:11:26.940> like 00:11:27.490 --> 00:11:27.500 align:start position:0% bandwidth incentives that is like 00:11:27.500 --> 00:11:29.930 align:start position:0% bandwidth incentives that is like incentives<00:11:28.500> like<00:11:29.040> money<00:11:29.279> that<00:11:29.579> you<00:11:29.700> can<00:11:29.820> earn 00:11:29.930 --> 00:11:29.940 align:start position:0% incentives like money that you can earn 00:11:29.940 --> 00:11:32.690 align:start position:0% incentives like money that you can earn for<00:11:30.420> sharing<00:11:30.959> data<00:11:31.320> on<00:11:31.440> the<00:11:31.560> network<00:11:31.740> and<00:11:32.579> then 00:11:32.690 --> 00:11:32.700 align:start position:0% for sharing data on the network and then 00:11:32.700 --> 00:11:34.550 align:start position:0% for sharing data on the network and then there's<00:11:32.940> storage<00:11:33.180> incentives<00:11:33.839> that<00:11:34.140> is<00:11:34.320> like 00:11:34.550 --> 00:11:34.560 align:start position:0% there's storage incentives that is like 00:11:34.560 --> 00:11:38.569 align:start position:0% there's storage incentives that is like you<00:11:35.459> can<00:11:35.640> earn<00:11:35.940> by<00:11:36.240> storing<00:11:37.220> data<00:11:38.220> for<00:11:38.399> other 00:11:38.569 --> 00:11:38.579 align:start position:0% you can earn by storing data for other 00:11:38.579 --> 00:11:41.210 align:start position:0% you can earn by storing data for other people<00:11:38.940> and 00:11:41.210 --> 00:11:41.220 align:start position:0% people and 00:11:41.220 --> 00:11:44.990 align:start position:0% people and so<00:11:42.120> like<00:11:43.079> everyone<00:11:43.740> maybe<00:11:44.160> I<00:11:44.459> don't<00:11:44.640> have<00:11:44.820> to 00:11:44.990 --> 00:11:45.000 align:start position:0% so like everyone maybe I don't have to 00:11:45.000 --> 00:11:47.750 align:start position:0% so like everyone maybe I don't have to explain<00:11:45.300> here<00:11:45.779> the<00:11:46.320> importance<00:11:47.100> of<00:11:47.279> instances 00:11:47.750 --> 00:11:47.760 align:start position:0% explain here the importance of instances 00:11:47.760 --> 00:11:51.290 align:start position:0% explain here the importance of instances incentives<00:11:48.480> here<00:11:48.779> but<00:11:49.079> like<00:11:49.500> maybe<00:11:50.300> what's 00:11:51.290 --> 00:11:51.300 align:start position:0% incentives here but like maybe what's 00:11:51.300 --> 00:11:53.509 align:start position:0% incentives here but like maybe what's relevant<00:11:51.720> here<00:11:51.959> is<00:11:52.140> that<00:11:52.380> like<00:11:52.680> these<00:11:53.339> two 00:11:53.509 --> 00:11:53.519 align:start position:0% relevant here is that like these two 00:11:53.519 --> 00:11:56.389 align:start position:0% relevant here is that like these two things<00:11:54.000> are<00:11:54.240> separate<00:11:54.600> and<00:11:54.779> currently 00:11:56.389 --> 00:11:56.399 align:start position:0% things are separate and currently 00:11:56.399 --> 00:11:59.509 align:start position:0% things are separate and currently um<00:11:56.519> only<00:11:56.940> the<00:11:57.480> the<00:11:57.779> bandwidth<00:11:58.320> incentives<00:11:58.800> are 00:11:59.509 --> 00:11:59.519 align:start position:0% um only the the bandwidth incentives are 00:11:59.519 --> 00:12:02.509 align:start position:0% um only the the bandwidth incentives are uh<00:12:00.240> running<00:12:00.540> on<00:12:01.019> the<00:12:01.200> on<00:12:01.440> the<00:12:01.560> main<00:12:01.680> net<00:12:01.920> So 00:12:02.509 --> 00:12:02.519 align:start position:0% uh running on the on the main net So 00:12:02.519 --> 00:12:06.230 align:start position:0% uh running on the on the main net So currently<00:12:02.880> you<00:12:03.180> cannot<00:12:03.420> really<00:12:03.600> earn 00:12:06.230 --> 00:12:06.240 align:start position:0% 00:12:06.240 --> 00:12:09.110 align:start position:0% by<00:12:06.720> storing<00:12:07.140> data<00:12:07.920> for<00:12:08.040> other<00:12:08.220> people<00:12:08.519> this<00:12:09.000> is 00:12:09.110 --> 00:12:09.120 align:start position:0% by storing data for other people this is 00:12:09.120 --> 00:12:10.310 align:start position:0% by storing data for other people this is something<00:12:09.360> that<00:12:09.660> we<00:12:09.779> are<00:12:09.899> working<00:12:10.079> on 00:12:10.310 --> 00:12:10.320 align:start position:0% something that we are working on 00:12:10.320 --> 00:12:12.769 align:start position:0% something that we are working on currently<00:12:10.740> and<00:12:10.980> this<00:12:11.100> is<00:12:11.220> on<00:12:11.399> testnet<00:12:12.000> so<00:12:12.360> we 00:12:12.769 --> 00:12:12.779 align:start position:0% currently and this is on testnet so we 00:12:12.779 --> 00:12:14.990 align:start position:0% currently and this is on testnet so we are<00:12:12.899> planning<00:12:13.200> to<00:12:13.320> Rolling<00:12:13.740> it<00:12:13.920> out<00:12:14.100> like<00:12:14.519> soon 00:12:14.990 --> 00:12:15.000 align:start position:0% are planning to Rolling it out like soon 00:12:15.000 --> 00:12:17.710 align:start position:0% are planning to Rolling it out like soon once<00:12:15.779> the<00:12:15.959> testing<00:12:16.320> is<00:12:16.500> done 00:12:17.710 --> 00:12:17.720 align:start position:0% once the testing is done 00:12:17.720 --> 00:12:18.230 align:start position:0% once the testing is done [Music] 00:12:18.230 --> 00:12:18.240 align:start position:0% [Music] 00:12:18.240 --> 00:12:19.430 align:start position:0% [Music] um 00:12:19.430 --> 00:12:19.440 align:start position:0% um 00:12:19.440 --> 00:12:23.889 align:start position:0% um and<00:12:20.399> yeah<00:12:21.240> so<00:12:21.720> maybe 00:12:23.889 --> 00:12:23.899 align:start position:0% and yeah so maybe 00:12:23.899 --> 00:12:27.230 align:start position:0% and yeah so maybe just<00:12:24.899> to<00:12:25.320> show<00:12:25.500> you<00:12:25.680> like<00:12:25.980> the<00:12:26.279> the<00:12:26.459> the<00:12:26.579> data 00:12:27.230 --> 00:12:27.240 align:start position:0% just to show you like the the the data 00:12:27.240 --> 00:12:29.690 align:start position:0% just to show you like the the the data economy<00:12:27.660> in<00:12:27.839> the<00:12:28.019> network<00:12:28.140> is<00:12:28.620> that<00:12:28.980> what<00:12:29.519> we 00:12:29.690 --> 00:12:29.700 align:start position:0% economy in the network is that what we 00:12:29.700 --> 00:12:31.069 align:start position:0% economy in the network is that what we see<00:12:29.820> is<00:12:30.000> that 00:12:31.069 --> 00:12:31.079 align:start position:0% see is that 00:12:31.079 --> 00:12:32.870 align:start position:0% see is that um what<00:12:31.440> is<00:12:31.560> interesting<00:12:31.920> in<00:12:32.100> swarm<00:12:32.519> is<00:12:32.640> that 00:12:32.870 --> 00:12:32.880 align:start position:0% um what is interesting in swarm is that 00:12:32.880 --> 00:12:35.509 align:start position:0% um what is interesting in swarm is that consumers<00:12:33.480> who<00:12:34.260> are<00:12:34.440> downloading<00:12:34.980> data<00:12:35.339> from 00:12:35.509 --> 00:12:35.519 align:start position:0% consumers who are downloading data from 00:12:35.519 --> 00:12:36.829 align:start position:0% consumers who are downloading data from the<00:12:35.700> network 00:12:36.829 --> 00:12:36.839 align:start position:0% the network 00:12:36.839 --> 00:12:39.530 align:start position:0% the network are<00:12:37.380> actually<00:12:37.620> paying<00:12:38.100> for<00:12:38.399> uh<00:12:38.940> downloading 00:12:39.530 --> 00:12:39.540 align:start position:0% are actually paying for uh downloading 00:12:39.540 --> 00:12:42.230 align:start position:0% are actually paying for uh downloading data<00:12:40.200> uh<00:12:41.100> so 00:12:42.230 --> 00:12:42.240 align:start position:0% data uh so 00:12:42.240 --> 00:12:45.889 align:start position:0% data uh so um<00:12:42.300> there<00:12:42.959> is<00:12:43.079> a<00:12:43.260> way<00:12:43.800> to<00:12:44.100> to<00:12:44.459> use<00:12:44.820> it<00:12:45.060> without 00:12:45.889 --> 00:12:45.899 align:start position:0% um there is a way to to use it without 00:12:45.899 --> 00:12:50.629 align:start position:0% um there is a way to to use it without paying<00:12:46.639> but<00:12:47.639> that<00:12:48.120> means<00:12:48.480> that<00:12:48.779> your<00:12:49.160> uh<00:12:50.160> your 00:12:50.629 --> 00:12:50.639 align:start position:0% paying but that means that your uh your 00:12:50.639 --> 00:12:52.670 align:start position:0% paying but that means that your uh your speed<00:12:50.820> is<00:12:51.060> limited<00:12:51.480> so<00:12:51.959> that<00:12:52.200> you<00:12:52.440> don't 00:12:52.670 --> 00:12:52.680 align:start position:0% speed is limited so that you don't 00:12:52.680 --> 00:12:55.129 align:start position:0% speed is limited so that you don't basically<00:12:53.519> the<00:12:53.820> the<00:12:54.000> nodes<00:12:54.300> are<00:12:54.480> prioritizing 00:12:55.129 --> 00:12:55.139 align:start position:0% basically the the nodes are prioritizing 00:12:55.139 --> 00:12:56.449 align:start position:0% basically the the nodes are prioritizing paying<00:12:55.560> nodes 00:12:56.449 --> 00:12:56.459 align:start position:0% paying nodes 00:12:56.459 --> 00:13:00.250 align:start position:0% paying nodes who<00:12:56.880> are<00:12:57.120> paying<00:12:57.240> for<00:12:57.540> downloading<00:12:58.519> content 00:13:00.250 --> 00:13:00.260 align:start position:0% who are paying for downloading content 00:13:00.260 --> 00:13:04.250 align:start position:0% who are paying for downloading content and<00:13:01.260> so<00:13:01.560> the<00:13:02.160> the<00:13:02.339> interesting<00:13:02.760> thing<00:13:03.000> here<00:13:03.839> is 00:13:04.250 --> 00:13:04.260 align:start position:0% and so the the interesting thing here is 00:13:04.260 --> 00:13:07.610 align:start position:0% and so the the interesting thing here is that<00:13:04.620> uh<00:13:05.360> this<00:13:06.360> enables<00:13:07.019> a<00:13:07.200> new<00:13:07.320> kind<00:13:07.500> of 00:13:07.610 --> 00:13:07.620 align:start position:0% that uh this enables a new kind of 00:13:07.620 --> 00:13:09.470 align:start position:0% that uh this enables a new kind of economy<00:13:08.160> so 00:13:09.470 --> 00:13:09.480 align:start position:0% economy so 00:13:09.480 --> 00:13:11.750 align:start position:0% economy so uh<00:13:09.540> like<00:13:10.079> the<00:13:10.560> currently<00:13:10.980> the<00:13:11.160> internet<00:13:11.339> has 00:13:11.750 --> 00:13:11.760 align:start position:0% uh like the currently the internet has 00:13:11.760 --> 00:13:15.410 align:start position:0% uh like the currently the internet has this<00:13:11.940> problem<00:13:12.180> that<00:13:12.720> by<00:13:13.620> storing<00:13:13.980> data<00:13:14.459> can<00:13:15.240> be 00:13:15.410 --> 00:13:15.420 align:start position:0% this problem that by storing data can be 00:13:15.420 --> 00:13:17.810 align:start position:0% this problem that by storing data can be quite<00:13:15.660> cheap<00:13:16.019> but<00:13:16.800> the<00:13:17.100> problem<00:13:17.220> is<00:13:17.459> that<00:13:17.639> if 00:13:17.810 --> 00:13:17.820 align:start position:0% quite cheap but the problem is that if 00:13:17.820 --> 00:13:20.509 align:start position:0% quite cheap but the problem is that if you<00:13:18.000> try<00:13:18.300> to<00:13:18.420> store<00:13:18.839> a<00:13:19.440> large<00:13:19.560> amount<00:13:19.920> of<00:13:20.040> data 00:13:20.509 --> 00:13:20.519 align:start position:0% you try to store a large amount of data 00:13:20.519 --> 00:13:22.730 align:start position:0% you try to store a large amount of data and<00:13:20.700> it<00:13:20.880> gets<00:13:21.240> your<00:13:21.600> project<00:13:21.779> yet<00:13:22.200> successful 00:13:22.730 --> 00:13:22.740 align:start position:0% and it gets your project yet successful 00:13:22.740 --> 00:13:25.370 align:start position:0% and it gets your project yet successful and<00:13:23.399> people<00:13:23.639> start<00:13:24.000> downloading<00:13:24.600> data<00:13:25.079> from 00:13:25.370 --> 00:13:25.380 align:start position:0% and people start downloading data from 00:13:25.380 --> 00:13:28.550 align:start position:0% and people start downloading data from you<00:13:25.560> then<00:13:26.399> suddenly<00:13:26.880> your<00:13:27.240> costs<00:13:27.660> are<00:13:28.200> not<00:13:28.380> on 00:13:28.550 --> 00:13:28.560 align:start position:0% you then suddenly your costs are not on 00:13:28.560 --> 00:13:30.290 align:start position:0% you then suddenly your costs are not on the<00:13:28.680> storage<00:13:28.860> side<00:13:29.220> but<00:13:29.639> actually<00:13:29.880> on<00:13:30.120> the 00:13:30.290 --> 00:13:30.300 align:start position:0% the storage side but actually on the 00:13:30.300 --> 00:13:31.790 align:start position:0% the storage side but actually on the bandwidth<00:13:30.720> side<00:13:30.899> so<00:13:31.079> if<00:13:31.200> you're<00:13:31.320> using<00:13:31.620> Amazon 00:13:31.790 --> 00:13:31.800 align:start position:0% bandwidth side so if you're using Amazon 00:13:31.800 --> 00:13:33.590 align:start position:0% bandwidth side so if you're using Amazon or<00:13:32.279> something<00:13:32.519> like<00:13:32.820> that 00:13:33.590 --> 00:13:33.600 align:start position:0% or something like that 00:13:33.600 --> 00:13:35.870 align:start position:0% or something like that then<00:13:34.260> you<00:13:34.500> will<00:13:34.620> have<00:13:34.800> to<00:13:34.920> pay<00:13:35.100> a<00:13:35.339> lot<00:13:35.459> for<00:13:35.760> the 00:13:35.870 --> 00:13:35.880 align:start position:0% then you will have to pay a lot for the 00:13:35.880 --> 00:13:38.810 align:start position:0% then you will have to pay a lot for the the<00:13:36.060> bandwidth<00:13:36.600> and<00:13:37.320> that<00:13:37.620> can<00:13:37.860> be<00:13:38.040> for<00:13:38.579> small 00:13:38.810 --> 00:13:38.820 align:start position:0% the bandwidth and that can be for small 00:13:38.820 --> 00:13:40.730 align:start position:0% the bandwidth and that can be for small project<00:13:39.120> that<00:13:39.600> can<00:13:39.720> be<00:13:39.899> like<00:13:40.079> prohibitively 00:13:40.730 --> 00:13:40.740 align:start position:0% project that can be like prohibitively 00:13:40.740 --> 00:13:42.889 align:start position:0% project that can be like prohibitively expensive<00:13:41.399> so 00:13:42.889 --> 00:13:42.899 align:start position:0% expensive so 00:13:42.899 --> 00:13:46.009 align:start position:0% expensive so um<00:13:42.959> like<00:13:43.920> storing<00:13:44.459> like<00:13:44.820> I<00:13:45.180> know<00:13:45.300> I<00:13:45.720> had<00:13:45.839> this 00:13:46.009 --> 00:13:46.019 align:start position:0% um like storing like I know I had this 00:13:46.019 --> 00:13:48.530 align:start position:0% um like storing like I know I had this example<00:13:46.380> that's<00:13:46.620> storing<00:13:47.100> like<00:13:47.399> 40<00:13:47.880> gigabytes 00:13:48.530 --> 00:13:48.540 align:start position:0% example that's storing like 40 gigabytes 00:13:48.540 --> 00:13:51.170 align:start position:0% example that's storing like 40 gigabytes for<00:13:48.779> a<00:13:48.959> year<00:13:49.139> is<00:13:49.260> like<00:13:49.620> a<00:13:50.100> few<00:13:50.220> dollars<00:13:50.639> maximum 00:13:51.170 --> 00:13:51.180 align:start position:0% for a year is like a few dollars maximum 00:13:51.180 --> 00:13:53.690 align:start position:0% for a year is like a few dollars maximum but<00:13:51.779> like<00:13:52.019> if<00:13:52.380> there<00:13:52.680> are<00:13:52.800> like<00:13:52.920> 10<00:13:53.339> 000<00:13:53.399> people 00:13:53.690 --> 00:13:53.700 align:start position:0% but like if there are like 10 000 people 00:13:53.700 --> 00:13:56.150 align:start position:0% but like if there are like 10 000 people downloading<00:13:54.360> that<00:13:54.600> from<00:13:54.839> you<00:13:55.019> you<00:13:55.740> can<00:13:55.920> start 00:13:56.150 --> 00:13:56.160 align:start position:0% downloading that from you you can start 00:13:56.160 --> 00:13:57.790 align:start position:0% downloading that from you you can start paying<00:13:56.639> like 00:13:57.790 --> 00:13:57.800 align:start position:0% paying like 00:13:57.800 --> 00:14:00.410 align:start position:0% paying like money<00:13:58.800> in<00:13:59.040> the<00:13:59.160> ten<00:13:59.399> thousand<00:13:59.700> dollars<00:13:59.940> range 00:14:00.410 --> 00:14:00.420 align:start position:0% money in the ten thousand dollars range 00:14:00.420 --> 00:14:02.750 align:start position:0% money in the ten thousand dollars range and<00:14:00.660> then<00:14:00.899> small<00:14:01.440> projects<00:14:01.980> may<00:14:02.220> not<00:14:02.399> be<00:14:02.579> able 00:14:02.750 --> 00:14:02.760 align:start position:0% and then small projects may not be able 00:14:02.760 --> 00:14:06.769 align:start position:0% and then small projects may not be able to<00:14:03.000> afford<00:14:03.420> that<00:14:03.660> and<00:14:04.620> by<00:14:05.399> changing<00:14:05.820> this<00:14:06.300> kind 00:14:06.769 --> 00:14:06.779 align:start position:0% to afford that and by changing this kind 00:14:06.779 --> 00:14:09.110 align:start position:0% to afford that and by changing this kind of<00:14:06.959> Dynamics<00:14:07.560> on<00:14:07.920> making<00:14:08.279> the<00:14:08.579> downloaders 00:14:09.110 --> 00:14:09.120 align:start position:0% of Dynamics on making the downloaders 00:14:09.120 --> 00:14:11.509 align:start position:0% of Dynamics on making the downloaders pay<00:14:09.420> can<00:14:10.019> enable<00:14:10.380> new<00:14:10.680> kind<00:14:10.860> of<00:14:10.980> applications 00:14:11.509 --> 00:14:11.519 align:start position:0% pay can enable new kind of applications 00:14:11.519 --> 00:14:13.730 align:start position:0% pay can enable new kind of applications where<00:14:12.060> even<00:14:12.300> like<00:14:12.660> small<00:14:12.899> projects<00:14:13.500> can 00:14:13.730 --> 00:14:13.740 align:start position:0% where even like small projects can 00:14:13.740 --> 00:14:16.910 align:start position:0% where even like small projects can afford<00:14:14.100> to<00:14:14.339> to<00:14:14.700> host<00:14:15.000> big<00:14:15.360> data<00:14:15.839> sets<00:14:16.139> and<00:14:16.380> also 00:14:16.910 --> 00:14:16.920 align:start position:0% afford to to host big data sets and also 00:14:16.920 --> 00:14:20.690 align:start position:0% afford to to host big data sets and also this<00:14:17.100> enables<00:14:18.180> hosting<00:14:19.019> public<00:14:19.380> data<00:14:20.339> sets<00:14:20.639> or 00:14:20.690 --> 00:14:20.700 align:start position:0% this enables hosting public data sets or 00:14:20.700 --> 00:14:23.090 align:start position:0% this enables hosting public data sets or common<00:14:20.940> good<00:14:21.240> data<00:14:21.720> sets<00:14:22.019> that<00:14:22.620> we<00:14:22.800> consider 00:14:23.090 --> 00:14:23.100 align:start position:0% common good data sets that we consider 00:14:23.100 --> 00:14:26.210 align:start position:0% common good data sets that we consider like<00:14:23.339> for<00:14:23.639> example<00:14:23.880> Wikipedia<00:14:24.600> data<00:14:25.200> or<00:14:25.500> or 00:14:26.210 --> 00:14:26.220 align:start position:0% like for example Wikipedia data or or 00:14:26.220 --> 00:14:29.810 align:start position:0% like for example Wikipedia data or or open<00:14:26.760> street<00:14:27.060> maps<00:14:27.540> data<00:14:28.019> or<00:14:28.200> like<00:14:29.160> it<00:14:29.459> would 00:14:29.810 --> 00:14:29.820 align:start position:0% open street maps data or like it would 00:14:29.820 --> 00:14:31.490 align:start position:0% open street maps data or like it would be<00:14:29.940> good<00:14:30.060> to<00:14:30.180> see<00:14:30.300> like<00:14:30.540> blockchain<00:14:30.899> data<00:14:31.320> it 00:14:31.490 --> 00:14:31.500 align:start position:0% be good to see like blockchain data it 00:14:31.500 --> 00:14:33.170 align:start position:0% be good to see like blockchain data it doesn't<00:14:31.680> really<00:14:31.920> make<00:14:32.160> sense<00:14:32.339> to<00:14:32.700> blockchain 00:14:33.170 --> 00:14:33.180 align:start position:0% doesn't really make sense to blockchain 00:14:33.180 --> 00:14:36.530 align:start position:0% doesn't really make sense to blockchain it<00:14:33.420> to<00:14:33.600> be<00:14:33.779> stored<00:14:34.200> on<00:14:34.320> all<00:14:35.100> the<00:14:35.339> the<00:14:35.639> nodes<00:14:36.000> it 00:14:36.530 --> 00:14:36.540 align:start position:0% it to be stored on all the the nodes it 00:14:36.540 --> 00:14:38.810 align:start position:0% it to be stored on all the the nodes it would<00:14:36.779> make<00:14:36.959> sense<00:14:37.139> to<00:14:37.440> have<00:14:37.560> like<00:14:37.860> one<00:14:38.160> common 00:14:38.810 --> 00:14:38.820 align:start position:0% would make sense to have like one common 00:14:38.820 --> 00:14:41.269 align:start position:0% would make sense to have like one common good<00:14:39.360> space<00:14:39.660> where<00:14:40.019> everyone<00:14:40.260> could<00:14:40.740> uh 00:14:41.269 --> 00:14:41.279 align:start position:0% good space where everyone could uh 00:14:41.279 --> 00:14:43.430 align:start position:0% good space where everyone could uh finance<00:14:41.820> and<00:14:42.120> and<00:14:42.420> maintain<00:14:42.959> as<00:14:43.139> a<00:14:43.320> common 00:14:43.430 --> 00:14:43.440 align:start position:0% finance and and maintain as a common 00:14:43.440 --> 00:14:46.310 align:start position:0% finance and and maintain as a common goods<00:14:43.920> and<00:14:44.699> there<00:14:45.060> are<00:14:45.180> many<00:14:45.480> other<00:14:45.720> use<00:14:46.019> cases 00:14:46.310 --> 00:14:46.320 align:start position:0% goods and there are many other use cases 00:14:46.320 --> 00:14:49.670 align:start position:0% goods and there are many other use cases that<00:14:46.740> this<00:14:46.860> can<00:14:47.160> enable<00:14:48.000> and 00:14:49.670 --> 00:14:49.680 align:start position:0% that this can enable and 00:14:49.680 --> 00:14:51.949 align:start position:0% that this can enable and what<00:14:50.279> I<00:14:50.519> see<00:14:50.639> here<00:14:50.820> is<00:14:51.000> that<00:14:51.240> this<00:14:51.480> can<00:14:51.720> create 00:14:51.949 --> 00:14:51.959 align:start position:0% what I see here is that this can create 00:14:51.959 --> 00:14:54.410 align:start position:0% what I see here is that this can create this<00:14:52.320> kind<00:14:52.500> of<00:14:52.680> new<00:14:53.160> kind<00:14:53.820> of<00:14:53.940> applications 00:14:54.410 --> 00:14:54.420 align:start position:0% this kind of new kind of applications 00:14:54.420 --> 00:14:57.350 align:start position:0% this kind of new kind of applications where<00:14:54.779> business<00:14:55.519> opportunities<00:14:56.519> can<00:14:57.060> rise 00:14:57.350 --> 00:14:57.360 align:start position:0% where business opportunities can rise 00:14:57.360 --> 00:15:00.590 align:start position:0% where business opportunities can rise when<00:14:57.899> data<00:14:58.620> creators<00:14:58.980> can<00:14:59.339> create<00:14:59.600> they 00:15:00.590 --> 00:15:00.600 align:start position:0% when data creators can create they 00:15:00.600 --> 00:15:03.410 align:start position:0% when data creators can create they create<00:15:01.139> something<00:15:01.740> that<00:15:02.279> is<00:15:02.399> stored<00:15:02.820> on<00:15:02.940> Swarm 00:15:03.410 --> 00:15:03.420 align:start position:0% create something that is stored on Swarm 00:15:03.420 --> 00:15:06.050 align:start position:0% create something that is stored on Swarm and<00:15:04.019> then<00:15:04.199> that<00:15:05.040> can<00:15:05.279> be<00:15:05.459> shared<00:15:05.880> with 00:15:06.050 --> 00:15:06.060 align:start position:0% and then that can be shared with 00:15:06.060 --> 00:15:08.509 align:start position:0% and then that can be shared with consumers<00:15:06.660> and<00:15:07.139> then<00:15:07.320> here<00:15:07.980> you<00:15:08.160> can<00:15:08.339> figure 00:15:08.509 --> 00:15:08.519 align:start position:0% consumers and then here you can figure 00:15:08.519 --> 00:15:09.590 align:start position:0% consumers and then here you can figure out<00:15:08.760> like 00:15:09.590 --> 00:15:09.600 align:start position:0% out like 00:15:09.600 --> 00:15:11.870 align:start position:0% out like you<00:15:10.139> upload<00:15:10.440> data<00:15:10.980> you<00:15:11.339> get<00:15:11.519> back<00:15:11.699> the 00:15:11.870 --> 00:15:11.880 align:start position:0% you upload data you get back the 00:15:11.880 --> 00:15:14.569 align:start position:0% you upload data you get back the reference<00:15:12.300> and<00:15:12.779> then<00:15:13.019> giving<00:15:13.620> access<00:15:13.980> to<00:15:14.399> that 00:15:14.569 --> 00:15:14.579 align:start position:0% reference and then giving access to that 00:15:14.579 --> 00:15:17.689 align:start position:0% reference and then giving access to that data<00:15:14.940> can<00:15:15.420> be<00:15:16.320> turned<00:15:16.680> into<00:15:16.860> business 00:15:17.689 --> 00:15:17.699 align:start position:0% data can be turned into business 00:15:17.699 --> 00:15:20.509 align:start position:0% data can be turned into business opportunities<00:15:18.420> so<00:15:18.959> that<00:15:19.740> is<00:15:19.860> also<00:15:20.220> something 00:15:20.509 --> 00:15:20.519 align:start position:0% opportunities so that is also something 00:15:20.519 --> 00:15:22.670 align:start position:0% opportunities so that is also something that<00:15:20.940> we<00:15:21.180> considered 00:15:22.670 --> 00:15:22.680 align:start position:0% that we considered 00:15:22.680 --> 00:15:27.170 align:start position:0% that we considered sort<00:15:23.279> of<00:15:23.519> problem<00:15:23.899> and<00:15:24.899> now<00:15:25.079> I'm<00:15:26.040> going<00:15:26.579> to<00:15:26.940> the 00:15:27.170 --> 00:15:27.180 align:start position:0% sort of problem and now I'm going to the 00:15:27.180 --> 00:15:29.930 align:start position:0% sort of problem and now I'm going to the the<00:15:27.480> more<00:15:28.320> Hands-On<00:15:28.800> part<00:15:29.399> of<00:15:29.579> the<00:15:29.760> the 00:15:29.930 --> 00:15:29.940 align:start position:0% the more Hands-On part of the the 00:15:29.940 --> 00:15:32.870 align:start position:0% the more Hands-On part of the the workshop<00:15:30.420> so<00:15:30.839> I<00:15:31.680> will<00:15:31.800> go<00:15:32.100> to<00:15:32.220> the<00:15:32.459> terminal 00:15:32.870 --> 00:15:32.880 align:start position:0% workshop so I will go to the terminal 00:15:32.880 --> 00:15:35.210 align:start position:0% workshop so I will go to the terminal and<00:15:33.600> do<00:15:33.779> some<00:15:33.959> stuff<00:15:34.199> that<00:15:34.620> people<00:15:34.800> does 00:15:35.210 --> 00:15:35.220 align:start position:0% and do some stuff that people does 00:15:35.220 --> 00:15:38.269 align:start position:0% and do some stuff that people does usually<00:15:35.579> in<00:15:35.699> the<00:15:35.820> terminal<00:15:36.120> and<00:15:37.019> so<00:15:37.260> the<00:15:38.100> first 00:15:38.269 --> 00:15:38.279 align:start position:0% usually in the terminal and so the first 00:15:38.279 --> 00:15:40.550 align:start position:0% usually in the terminal and so the first thing<00:15:38.459> I<00:15:38.760> would<00:15:38.880> like<00:15:39.060> to<00:15:39.180> talk<00:15:39.360> about<00:15:39.540> is<00:15:39.899> that 00:15:40.550 --> 00:15:40.560 align:start position:0% thing I would like to talk about is that 00:15:40.560 --> 00:15:41.210 align:start position:0% thing I would like to talk about is that um 00:15:41.210 --> 00:15:41.220 align:start position:0% um 00:15:41.220 --> 00:15:44.990 align:start position:0% um so<00:15:41.820> the<00:15:42.120> the<00:15:42.300> Swarm<00:15:43.279> currently<00:15:44.279> has<00:15:44.519> an 00:15:44.990 --> 00:15:45.000 align:start position:0% so the the Swarm currently has an 00:15:45.000 --> 00:15:48.470 align:start position:0% so the the Swarm currently has an implementation<00:15:45.480> called<00:15:45.899> B<00:15:46.279> and<00:15:47.279> uh<00:15:47.760> you<00:15:48.300> can 00:15:48.470 --> 00:15:48.480 align:start position:0% implementation called B and uh you can 00:15:48.480 --> 00:15:51.170 align:start position:0% implementation called B and uh you can download<00:15:48.720> B<00:15:49.500> from<00:15:50.160> the<00:15:50.279> website<00:15:50.639> and<00:15:50.880> you<00:15:51.060> can 00:15:51.170 --> 00:15:51.180 align:start position:0% download B from the website and you can 00:15:51.180 --> 00:15:52.970 align:start position:0% download B from the website and you can install<00:15:51.360> it<00:15:51.600> on<00:15:51.720> your<00:15:51.899> computer<00:15:52.079> and<00:15:52.500> then<00:15:52.680> you 00:15:52.970 --> 00:15:52.980 align:start position:0% install it on your computer and then you 00:15:52.980 --> 00:15:55.750 align:start position:0% install it on your computer and then you can<00:15:53.360> configure<00:15:54.360> it<00:15:54.480> and<00:15:54.839> start 00:15:55.750 --> 00:15:55.760 align:start position:0% can configure it and start 00:15:55.760 --> 00:15:57.949 align:start position:0% can configure it and start interacting<00:15:56.760> with<00:15:57.000> that 00:15:57.949 --> 00:15:57.959 align:start position:0% interacting with that 00:15:57.959 --> 00:16:02.329 align:start position:0% interacting with that and<00:15:58.860> uh<00:15:59.360> so<00:16:00.360> there<00:16:00.959> is<00:16:01.139> a<00:16:01.260> Dev<00:16:01.380> mode<00:16:01.740> for<00:16:02.100> this 00:16:02.329 --> 00:16:02.339 align:start position:0% and uh so there is a Dev mode for this 00:16:02.339 --> 00:16:04.310 align:start position:0% and uh so there is a Dev mode for this like<00:16:02.639> I<00:16:03.000> wanted<00:16:03.120> to<00:16:03.480> show<00:16:03.720> this<00:16:03.959> to<00:16:04.199> you 00:16:04.310 --> 00:16:04.320 align:start position:0% like I wanted to show this to you 00:16:04.320 --> 00:16:06.949 align:start position:0% like I wanted to show this to you because<00:16:04.560> that's<00:16:04.980> quite<00:16:05.339> easy<00:16:06.000> to<00:16:06.420> use<00:16:06.600> and 00:16:06.949 --> 00:16:06.959 align:start position:0% because that's quite easy to use and 00:16:06.959 --> 00:16:11.090 align:start position:0% because that's quite easy to use and it's<00:16:07.260> quite<00:16:07.760> uh<00:16:08.760> handy<00:16:09.660> when<00:16:10.079> you<00:16:10.380> when<00:16:10.860> you 00:16:11.090 --> 00:16:11.100 align:start position:0% it's quite uh handy when you when you 00:16:11.100 --> 00:16:13.370 align:start position:0% it's quite uh handy when you when you are<00:16:11.279> not<00:16:11.399> sure<00:16:11.579> if<00:16:11.760> you<00:16:11.940> want<00:16:12.180> to<00:16:12.300> be<00:16:12.899> invested 00:16:13.370 --> 00:16:13.380 align:start position:0% are not sure if you want to be invested 00:16:13.380 --> 00:16:15.710 align:start position:0% are not sure if you want to be invested in<00:16:13.620> this<00:16:13.920> and<00:16:14.160> you<00:16:14.399> don't<00:16:14.579> want<00:16:14.820> to<00:16:14.940> spend<00:16:15.240> too 00:16:15.710 --> 00:16:15.720 align:start position:0% in this and you don't want to spend too 00:16:15.720 --> 00:16:17.870 align:start position:0% in this and you don't want to spend too much<00:16:15.899> time<00:16:16.139> on<00:16:16.320> that<00:16:16.500> so<00:16:16.860> basically<00:16:17.279> once<00:16:17.760> you 00:16:17.870 --> 00:16:17.880 align:start position:0% much time on that so basically once you 00:16:17.880 --> 00:16:20.090 align:start position:0% much time on that so basically once you have<00:16:18.000> the<00:16:18.120> B<00:16:18.300> binary<00:16:18.839> installed<00:16:19.800> on<00:16:19.920> your 00:16:20.090 --> 00:16:20.100 align:start position:0% have the B binary installed on your 00:16:20.100 --> 00:16:22.670 align:start position:0% have the B binary installed on your machine<00:16:20.420> which<00:16:21.420> is<00:16:21.540> called<00:16:21.720> B<00:16:21.959> then<00:16:22.260> this<00:16:22.500> Dev 00:16:22.670 --> 00:16:22.680 align:start position:0% machine which is called B then this Dev 00:16:22.680 --> 00:16:24.769 align:start position:0% machine which is called B then this Dev mode<00:16:22.920> can<00:16:23.160> be<00:16:23.339> just<00:16:23.459> invoked<00:16:23.940> with<00:16:24.120> this<00:16:24.240> B<00:16:24.480> Dev 00:16:24.769 --> 00:16:24.779 align:start position:0% mode can be just invoked with this B Dev 00:16:24.779 --> 00:16:27.829 align:start position:0% mode can be just invoked with this B Dev it<00:16:25.620> starts<00:16:25.920> up<00:16:26.040> and<00:16:26.579> then<00:16:26.820> it's<00:16:27.360> ready<00:16:27.540> to 00:16:27.829 --> 00:16:27.839 align:start position:0% it starts up and then it's ready to 00:16:27.839 --> 00:16:32.329 align:start position:0% it starts up and then it's ready to serve<00:16:28.199> requests<00:16:29.160> so<00:16:30.060> you<00:16:30.660> can<00:16:30.839> access<00:16:31.260> the<00:16:32.100> the 00:16:32.329 --> 00:16:32.339 align:start position:0% serve requests so you can access the the 00:16:32.339 --> 00:16:37.310 align:start position:0% serve requests so you can access the the B<00:16:32.579> API<00:16:33.180> on<00:16:33.480> the<00:16:33.600> port<00:16:33.920> 1633<00:16:34.940> and<00:16:35.940> it<00:16:36.540> also<00:16:36.899> has 00:16:37.310 --> 00:16:37.320 align:start position:0% B API on the port 1633 and it also has 00:16:37.320 --> 00:16:41.350 align:start position:0% B API on the port 1633 and it also has some<00:16:37.860> other<00:16:38.339> functionality<00:16:39.180> Imports<00:16:40.339> 1635 00:16:41.350 --> 00:16:41.360 align:start position:0% some other functionality Imports 1635 00:16:41.360 --> 00:16:45.590 align:start position:0% some other functionality Imports 1635 like<00:16:42.360> it's<00:16:43.339> currently<00:16:44.339> that<00:16:44.639> like<00:16:44.940> data 00:16:45.590 --> 00:16:45.600 align:start position:0% like it's currently that like data 00:16:45.600 --> 00:16:47.689 align:start position:0% like it's currently that like data related<00:16:45.899> functionality<00:16:46.500> can<00:16:46.860> be<00:16:46.980> accessed<00:16:47.519> on 00:16:47.689 --> 00:16:47.699 align:start position:0% related functionality can be accessed on 00:16:47.699 --> 00:16:49.850 align:start position:0% related functionality can be accessed on the<00:16:47.880> 33<00:16:48.300> port<00:16:48.600> and<00:16:48.899> then<00:16:49.079> administrative 00:16:49.850 --> 00:16:49.860 align:start position:0% the 33 port and then administrative 00:16:49.860 --> 00:16:54.350 align:start position:0% the 33 port and then administrative functions<00:16:50.519> can<00:16:50.880> be<00:16:51.060> accessed<00:16:51.839> on<00:16:52.019> the<00:16:52.259> 35<00:16:53.360> and 00:16:54.350 --> 00:16:54.360 align:start position:0% functions can be accessed on the 35 and 00:16:54.360 --> 00:16:58.850 align:start position:0% functions can be accessed on the 35 and maybe<00:16:55.019> I<00:16:55.680> can<00:16:55.860> show<00:16:56.220> you<00:16:56.399> like<00:16:56.820> the 00:16:58.850 --> 00:16:58.860 align:start position:0% maybe I can show you like the 00:16:58.860 --> 00:17:02.210 align:start position:0% maybe I can show you like the um<00:16:59.339> the<00:17:00.000> documentation<00:17:00.660> for<00:17:01.259> this<00:17:01.440> so<00:17:01.740> like<00:17:01.920> we 00:17:02.210 --> 00:17:02.220 align:start position:0% um the documentation for this so like we 00:17:02.220 --> 00:17:05.090 align:start position:0% um the documentation for this so like we have<00:17:02.399> a<00:17:02.759> quite<00:17:03.060> complete<00:17:03.480> documentation<00:17:04.100> so 00:17:05.090 --> 00:17:05.100 align:start position:0% have a quite complete documentation so 00:17:05.100 --> 00:17:08.210 align:start position:0% have a quite complete documentation so how<00:17:05.400> the<00:17:05.579> API<00:17:06.000> works<00:17:06.540> and<00:17:06.839> then 00:17:08.210 --> 00:17:08.220 align:start position:0% how the API works and then 00:17:08.220 --> 00:17:10.569 align:start position:0% how the API works and then maybe<00:17:08.819> I<00:17:09.059> will<00:17:09.179> do<00:17:09.419> this<00:17:09.540> at<00:17:09.720> the<00:17:09.900> end<00:17:10.020> like 00:17:10.569 --> 00:17:10.579 align:start position:0% maybe I will do this at the end like 00:17:10.579 --> 00:17:14.809 align:start position:0% maybe I will do this at the end like once<00:17:11.579> I<00:17:11.760> went<00:17:12.000> through<00:17:12.360> all<00:17:12.780> the<00:17:13.020> things<00:17:13.199> so<00:17:13.819> I 00:17:14.809 --> 00:17:14.819 align:start position:0% once I went through all the things so I 00:17:14.819 --> 00:17:16.309 align:start position:0% once I went through all the things so I just<00:17:14.880> wanted<00:17:15.059> to<00:17:15.299> show<00:17:15.419> you<00:17:15.600> that<00:17:15.839> basically 00:17:16.309 --> 00:17:16.319 align:start position:0% just wanted to show you that basically 00:17:16.319 --> 00:17:19.069 align:start position:0% just wanted to show you that basically like<00:17:16.679> trying<00:17:17.100> it<00:17:17.339> in<00:17:17.520> Dev<00:17:17.760> mode<00:17:18.059> can<00:17:18.600> be<00:17:18.780> quite 00:17:19.069 --> 00:17:19.079 align:start position:0% like trying it in Dev mode can be quite 00:17:19.079 --> 00:17:21.829 align:start position:0% like trying it in Dev mode can be quite easy<00:17:19.380> and<00:17:20.220> it<00:17:20.699> does<00:17:20.939> not<00:17:21.059> take<00:17:21.299> you<00:17:21.480> a<00:17:21.600> lot<00:17:21.720> of 00:17:21.829 --> 00:17:21.839 align:start position:0% easy and it does not take you a lot of 00:17:21.839 --> 00:17:25.069 align:start position:0% easy and it does not take you a lot of time<00:17:22.079> if<00:17:22.620> you<00:17:22.799> just<00:17:22.919> want<00:17:23.100> to<00:17:23.220> try<00:17:23.459> to 00:17:25.069 --> 00:17:25.079 align:start position:0% time if you just want to try to 00:17:25.079 --> 00:17:28.250 align:start position:0% time if you just want to try to um<00:17:25.500> upload<00:17:26.339> data<00:17:26.640> download<00:17:26.939> it<00:17:27.419> check<00:17:28.079> out 00:17:28.250 --> 00:17:28.260 align:start position:0% um upload data download it check out 00:17:28.260 --> 00:17:31.070 align:start position:0% um upload data download it check out filter<00:17:28.620> API<00:17:29.280> then<00:17:29.580> and<00:17:29.940> I<00:17:30.360> this<00:17:30.840> is<00:17:30.960> the 00:17:31.070 --> 00:17:31.080 align:start position:0% filter API then and I this is the 00:17:31.080 --> 00:17:34.190 align:start position:0% filter API then and I this is the recommended<00:17:31.620> way<00:17:31.799> to<00:17:32.040> do<00:17:32.240> and<00:17:33.240> then 00:17:34.190 --> 00:17:34.200 align:start position:0% recommended way to do and then 00:17:34.200 --> 00:17:36.950 align:start position:0% recommended way to do and then uh<00:17:34.919> there<00:17:35.220> is<00:17:35.340> a 00:17:36.950 --> 00:17:36.960 align:start position:0% uh there is a 00:17:36.960 --> 00:17:41.570 align:start position:0% uh there is a desktop<00:17:37.679> app<00:17:38.340> so<00:17:39.000> for<00:17:39.240> that<00:17:39.480> I<00:17:39.960> will<00:17:40.080> need<00:17:40.380> to<00:17:40.620> I 00:17:41.570 --> 00:17:41.580 align:start position:0% desktop app so for that I will need to I 00:17:41.580 --> 00:17:43.789 align:start position:0% desktop app so for that I will need to I forgot<00:17:42.059> to<00:17:42.299> do<00:17:42.480> this<00:17:42.660> but<00:17:42.900> I<00:17:43.140> will<00:17:43.260> do<00:17:43.559> some 00:17:43.789 --> 00:17:43.799 align:start position:0% forgot to do this but I will do some 00:17:43.799 --> 00:17:48.409 align:start position:0% forgot to do this but I will do some quick<00:17:44.640> uh<00:17:45.679> housekeeping<00:17:46.679> so 00:17:48.409 --> 00:17:48.419 align:start position:0% quick uh housekeeping so 00:17:48.419 --> 00:17:50.090 align:start position:0% quick uh housekeeping so social<00:17:48.720> support 00:17:50.090 --> 00:17:50.100 align:start position:0% social support 00:17:50.100 --> 00:17:52.010 align:start position:0% social support so<00:17:50.460> I<00:17:50.580> already<00:17:50.700> have<00:17:51.000> it<00:17:51.179> installed<00:17:51.720> on<00:17:51.840> my 00:17:52.010 --> 00:17:52.020 align:start position:0% so I already have it installed on my 00:17:52.020 --> 00:17:55.490 align:start position:0% so I already have it installed on my machine<00:17:52.260> so<00:17:52.740> I<00:17:52.980> need<00:17:53.160> to<00:17:53.520> basically 00:17:55.490 --> 00:17:55.500 align:start position:0% machine so I need to basically 00:17:55.500 --> 00:17:57.770 align:start position:0% machine so I need to basically um 00:17:57.770 --> 00:17:57.780 align:start position:0% 00:17:57.780 --> 00:18:03.049 align:start position:0% sorry<00:17:58.140> about<00:17:58.380> this 00:18:03.049 --> 00:18:03.059 align:start position:0% 00:18:03.059 --> 00:18:07.010 align:start position:0% so<00:18:03.600> I<00:18:04.380> just<00:18:04.559> moved<00:18:04.919> the<00:18:05.039> folder<00:18:05.580> so<00:18:05.880> it<00:18:06.539> forgets 00:18:07.010 --> 00:18:07.020 align:start position:0% so I just moved the folder so it forgets 00:18:07.020 --> 00:18:09.830 align:start position:0% so I just moved the folder so it forgets everything<00:18:07.220> so<00:18:08.220> you<00:18:08.520> have<00:18:08.700> you<00:18:08.940> can<00:18:09.059> go<00:18:09.480> to<00:18:09.600> the 00:18:09.830 --> 00:18:09.840 align:start position:0% everything so you have you can go to the 00:18:09.840 --> 00:18:13.250 align:start position:0% everything so you have you can go to the website<00:18:10.260> and<00:18:11.220> then<00:18:11.340> on<00:18:11.520> the<00:18:11.700> website<00:18:12.059> you<00:18:12.419> can 00:18:13.250 --> 00:18:13.260 align:start position:0% website and then on the website you can 00:18:13.260 --> 00:18:16.090 align:start position:0% website and then on the website you can yeah<00:18:13.799> it's<00:18:14.160> later<00:18:14.460> this<00:18:15.120> is<00:18:15.299> going<00:18:15.539> to<00:18:15.660> be 00:18:16.090 --> 00:18:16.100 align:start position:0% yeah it's later this is going to be 00:18:16.100 --> 00:18:18.650 align:start position:0% yeah it's later this is going to be handy<00:18:17.100> so<00:18:17.340> on<00:18:17.520> the<00:18:17.700> website<00:18:18.000> you<00:18:18.299> can<00:18:18.360> download 00:18:18.650 --> 00:18:18.660 align:start position:0% handy so on the website you can download 00:18:18.660 --> 00:18:21.710 align:start position:0% handy so on the website you can download it<00:18:19.500> and<00:18:20.039> I<00:18:20.280> already<00:18:20.400> downloaded<00:18:21.000> it<00:18:21.240> so<00:18:21.480> that 00:18:21.710 --> 00:18:21.720 align:start position:0% it and I already downloaded it so that 00:18:21.720 --> 00:18:23.930 align:start position:0% it and I already downloaded it so that it's<00:18:22.260> on<00:18:22.500> my<00:18:22.740> machine<00:18:22.919> and<00:18:23.280> I<00:18:23.460> don't<00:18:23.580> have<00:18:23.760> to 00:18:23.930 --> 00:18:23.940 align:start position:0% it's on my machine and I don't have to 00:18:23.940 --> 00:18:25.430 align:start position:0% it's on my machine and I don't have to rely<00:18:24.179> on<00:18:24.299> the<00:18:24.419> network<00:18:24.539> however<00:18:25.080> like 00:18:25.430 --> 00:18:25.440 align:start position:0% rely on the network however like 00:18:25.440 --> 00:18:27.230 align:start position:0% rely on the network however like installing<00:18:25.919> this<00:18:26.220> like<00:18:26.460> this<00:18:26.820> is<00:18:26.940> a 00:18:27.230 --> 00:18:27.240 align:start position:0% installing this like this is a 00:18:27.240 --> 00:18:30.529 align:start position:0% installing this like this is a completely<00:18:27.780> networked<00:18:28.380> software<00:18:28.740> so<00:18:29.539> in 00:18:30.529 --> 00:18:30.539 align:start position:0% completely networked software so in 00:18:30.539 --> 00:18:33.110 align:start position:0% completely networked software so in order<00:18:30.720> to<00:18:31.080> demonstrate<00:18:31.799> this<00:18:32.100> I<00:18:32.400> I<00:18:32.640> will<00:18:32.820> need 00:18:33.110 --> 00:18:33.120 align:start position:0% order to demonstrate this I I will need 00:18:33.120 --> 00:18:37.490 align:start position:0% order to demonstrate this I I will need also<00:18:33.539> network<00:18:34.080> connection<00:18:34.559> to<00:18:34.980> be<00:18:35.100> working 00:18:37.490 --> 00:18:37.500 align:start position:0% 00:18:37.500 --> 00:18:39.529 align:start position:0% but<00:18:37.919> the<00:18:38.100> point<00:18:38.220> is<00:18:38.400> that<00:18:39.000> um 00:18:39.529 --> 00:18:39.539 align:start position:0% but the point is that um 00:18:39.539 --> 00:18:41.450 align:start position:0% but the point is that um so<00:18:39.960> there's<00:18:40.080> a<00:18:40.320> desktop<00:18:40.620> app<00:18:40.860> it's<00:18:41.280> an 00:18:41.450 --> 00:18:41.460 align:start position:0% so there's a desktop app it's an 00:18:41.460 --> 00:18:43.669 align:start position:0% so there's a desktop app it's an electron<00:18:41.820> app<00:18:42.059> so<00:18:42.299> it's<00:18:42.539> available<00:18:42.780> on<00:18:43.500> all 00:18:43.669 --> 00:18:43.679 align:start position:0% electron app so it's available on all 00:18:43.679 --> 00:18:48.830 align:start position:0% electron app so it's available on all major<00:18:43.980> platforms<00:18:44.820> Mac<00:18:45.360> Linux<00:18:45.900> windows<00:18:46.760> and<00:18:47.760> uh 00:18:48.830 --> 00:18:48.840 align:start position:0% major platforms Mac Linux windows and uh 00:18:48.840 --> 00:18:52.070 align:start position:0% major platforms Mac Linux windows and uh it<00:18:49.559> has<00:18:49.860> different<00:18:50.539> versions<00:18:51.539> that<00:18:51.840> you<00:18:51.960> can 00:18:52.070 --> 00:18:52.080 align:start position:0% it has different versions that you can 00:18:52.080 --> 00:18:55.190 align:start position:0% it has different versions that you can download<00:18:52.760> so<00:18:53.760> if<00:18:53.880> you<00:18:54.000> this<00:18:54.360> is<00:18:54.480> the<00:18:54.660> GitHub 00:18:55.190 --> 00:18:55.200 align:start position:0% download so if you this is the GitHub 00:18:55.200 --> 00:18:57.230 align:start position:0% download so if you this is the GitHub page<00:18:55.500> but<00:18:56.039> you<00:18:56.160> can<00:18:56.280> also<00:18:56.520> download<00:18:56.700> it<00:18:57.059> from 00:18:57.230 --> 00:18:57.240 align:start position:0% page but you can also download it from 00:18:57.240 --> 00:19:00.130 align:start position:0% page but you can also download it from the<00:18:57.360> website<00:18:57.780> and<00:18:58.440> once<00:18:58.679> you<00:18:58.799> have<00:18:58.919> this<00:18:59.220> file 00:19:00.130 --> 00:19:00.140 align:start position:0% the website and once you have this file 00:19:00.140 --> 00:19:01.670 align:start position:0% the website and once you have this file on<00:19:01.140> your<00:19:01.320> machine 00:19:01.670 --> 00:19:01.680 align:start position:0% on your machine 00:19:01.680 --> 00:19:02.750 align:start position:0% on your machine [Music] 00:19:02.750 --> 00:19:02.760 align:start position:0% [Music] 00:19:02.760 --> 00:19:06.470 align:start position:0% [Music] okay<00:19:03.500> right<00:19:04.500> let<00:19:04.860> me<00:19:04.980> just<00:19:05.220> find<00:19:05.520> this 00:19:06.470 --> 00:19:06.480 align:start position:0% okay right let me just find this 00:19:06.480 --> 00:19:14.150 align:start position:0% okay right let me just find this like<00:19:07.140> here<00:19:07.500> download<00:19:08.240> swarm<00:19:09.240> desktop 00:19:14.150 --> 00:19:14.160 align:start position:0% 00:19:14.160 --> 00:19:16.669 align:start position:0% me<00:19:14.580> sorry<00:19:15.299> about<00:19:15.539> this 00:19:16.669 --> 00:19:16.679 align:start position:0% me sorry about this 00:19:16.679 --> 00:19:19.909 align:start position:0% me sorry about this um 00:19:19.909 --> 00:19:19.919 align:start position:0% 00:19:19.919 --> 00:19:22.789 align:start position:0% zero 00:19:22.789 --> 00:19:22.799 align:start position:0% 00:19:22.799 --> 00:19:25.430 align:start position:0% okay<00:19:23.340> so<00:19:23.700> then<00:19:23.940> let's<00:19:24.120> do<00:19:24.419> like<00:19:24.780> how<00:19:25.020> would<00:19:25.260> you 00:19:25.430 --> 00:19:25.440 align:start position:0% okay so then let's do like how would you 00:19:25.440 --> 00:19:29.510 align:start position:0% okay so then let's do like how would you do<00:19:25.559> it<00:19:26.220> so<00:19:26.760> I<00:19:26.880> download<00:19:27.179> the<00:19:27.559> x64<00:19:28.559> DMG<00:19:29.280> version 00:19:29.510 --> 00:19:29.520 align:start position:0% do it so I download the x64 DMG version 00:19:29.520 --> 00:19:31.970 align:start position:0% do it so I download the x64 DMG version because<00:19:29.820> I<00:19:30.240> have<00:19:30.360> the 00:19:31.970 --> 00:19:31.980 align:start position:0% because I have the 00:19:31.980 --> 00:19:34.370 align:start position:0% because I have the okay<00:19:32.280> maybe<00:19:32.580> I<00:19:32.880> don't<00:19:33.000> do<00:19:33.360> that 00:19:34.370 --> 00:19:34.380 align:start position:0% okay maybe I don't do that 00:19:34.380 --> 00:19:38.150 align:start position:0% okay maybe I don't do that okay<00:19:34.799> sorry<00:19:35.179> uh<00:19:36.179> I<00:19:36.419> will<00:19:36.539> just<00:19:36.780> open<00:19:36.960> the 00:19:38.150 --> 00:19:38.160 align:start position:0% okay sorry uh I will just open the 00:19:38.160 --> 00:19:49.010 align:start position:0% okay sorry uh I will just open the downloaded<00:19:39.059> version 00:19:49.010 --> 00:19:49.020 align:start position:0% 00:19:49.020 --> 00:19:51.529 align:start position:0% so<00:19:49.559> you<00:19:49.740> yeah<00:19:50.160> okay<00:19:50.400> I<00:19:50.640> already<00:19:50.820> installed<00:19:51.360> it 00:19:51.529 --> 00:19:51.539 align:start position:0% so you yeah okay I already installed it 00:19:51.539 --> 00:19:53.990 align:start position:0% so you yeah okay I already installed it so<00:19:51.900> I<00:19:52.080> just<00:19:52.200> need<00:19:52.380> to<00:19:52.559> start<00:19:52.919> it<00:19:53.220> like<00:19:53.760> you 00:19:53.990 --> 00:19:54.000 align:start position:0% so I just need to start it like you 00:19:54.000 --> 00:19:56.150 align:start position:0% so I just need to start it like you install<00:19:54.299> it<00:19:54.539> as<00:19:54.720> a<00:19:54.900> Mac<00:19:55.020> app<00:19:55.260> you<00:19:55.559> put<00:19:55.860> this<00:19:56.039> in 00:19:56.150 --> 00:19:56.160 align:start position:0% install it as a Mac app you put this in 00:19:56.160 --> 00:19:58.850 align:start position:0% install it as a Mac app you put this in the<00:19:56.340> application<00:19:57.260> folder<00:19:58.260> and<00:19:58.559> then<00:19:58.679> you 00:19:58.850 --> 00:19:58.860 align:start position:0% the application folder and then you 00:19:58.860 --> 00:20:00.110 align:start position:0% the application folder and then you start<00:19:59.100> it 00:20:00.110 --> 00:20:00.120 align:start position:0% start it 00:20:00.120 --> 00:20:03.770 align:start position:0% start it and<00:20:00.780> uh 00:20:03.770 --> 00:20:03.780 align:start position:0% 00:20:03.780 --> 00:20:09.230 align:start position:0% yeah<00:20:04.260> it<00:20:05.100> starts<00:20:05.580> with<00:20:05.880> uh<00:20:06.919> downloading<00:20:07.919> B<00:20:08.400> So 00:20:09.230 --> 00:20:09.240 align:start position:0% yeah it starts with uh downloading B So 00:20:09.240 --> 00:20:12.590 align:start position:0% yeah it starts with uh downloading B So currently<00:20:09.660> it's<00:20:09.960> uh<00:20:10.799> it<00:20:11.520> just<00:20:11.640> uh 00:20:12.590 --> 00:20:12.600 align:start position:0% currently it's uh it just uh 00:20:12.600 --> 00:20:16.070 align:start position:0% currently it's uh it just uh yeah<00:20:13.320> it's<00:20:14.160> again<00:20:14.400> I<00:20:15.299> didn't<00:20:15.360> think<00:20:15.600> of<00:20:15.780> this 00:20:16.070 --> 00:20:16.080 align:start position:0% yeah it's again I didn't think of this 00:20:16.080 --> 00:20:18.470 align:start position:0% yeah it's again I didn't think of this because<00:20:16.500> on<00:20:17.100> a<00:20:17.220> normal<00:20:17.340> Network<00:20:17.640> this<00:20:18.059> doesn't 00:20:18.470 --> 00:20:18.480 align:start position:0% because on a normal Network this doesn't 00:20:18.480 --> 00:20:20.810 align:start position:0% because on a normal Network this doesn't take<00:20:18.720> too<00:20:18.900> long<00:20:19.080> and<00:20:19.860> this<00:20:20.100> is<00:20:20.160> only<00:20:20.340> needed 00:20:20.810 --> 00:20:20.820 align:start position:0% take too long and this is only needed 00:20:20.820 --> 00:20:25.010 align:start position:0% take too long and this is only needed because<00:20:21.320> we<00:20:22.320> support<00:20:22.880> M1<00:20:23.880> Max<00:20:24.120> so<00:20:24.539> it<00:20:24.720> has<00:20:24.840> a 00:20:25.010 --> 00:20:25.020 align:start position:0% because we support M1 Max so it has a 00:20:25.020 --> 00:20:26.690 align:start position:0% because we support M1 Max so it has a different<00:20:25.080> version<00:20:25.500> and<00:20:25.919> it<00:20:26.039> has<00:20:26.220> different<00:20:26.400> B 00:20:26.690 --> 00:20:26.700 align:start position:0% different version and it has different B 00:20:26.700 --> 00:20:29.630 align:start position:0% different version and it has different B versions<00:20:27.120> so<00:20:27.360> it<00:20:27.480> downloads<00:20:27.900> the<00:20:28.080> M1<00:20:28.919> macv 00:20:29.630 --> 00:20:29.640 align:start position:0% versions so it downloads the M1 macv 00:20:29.640 --> 00:20:31.430 align:start position:0% versions so it downloads the M1 macv version<00:20:29.880> if<00:20:30.179> you<00:20:30.240> have<00:20:30.299> a<00:20:30.480> number<00:20:30.539> MAC<00:20:30.960> or<00:20:31.200> M 00:20:31.430 --> 00:20:31.440 align:start position:0% version if you have a number MAC or M 00:20:31.440 --> 00:20:34.430 align:start position:0% version if you have a number MAC or M like<00:20:31.799> apple<00:20:31.980> silicone<00:20:32.520> version<00:20:32.820> and<00:20:33.360> then<00:20:33.539> it 00:20:34.430 --> 00:20:34.440 align:start position:0% like apple silicone version and then it 00:20:34.440 --> 00:20:36.950 align:start position:0% like apple silicone version and then it for<00:20:34.740> me<00:20:34.860> it's<00:20:35.039> an<00:20:35.400> old<00:20:35.700> Intel<00:20:36.179> Mac<00:20:36.539> so<00:20:36.780> it 00:20:36.950 --> 00:20:36.960 align:start position:0% for me it's an old Intel Mac so it 00:20:36.960 --> 00:20:42.010 align:start position:0% for me it's an old Intel Mac so it downloads<00:20:37.380> that<00:20:37.559> one 00:20:42.010 --> 00:20:42.020 align:start position:0% 00:20:42.020 --> 00:20:44.870 align:start position:0% and<00:20:43.020> yeah<00:20:43.140> after<00:20:43.440> that<00:20:43.799> so<00:20:44.220> as<00:20:44.400> you<00:20:44.640> can<00:20:44.760> see 00:20:44.870 --> 00:20:44.880 align:start position:0% and yeah after that so as you can see 00:20:44.880 --> 00:20:48.830 align:start position:0% and yeah after that so as you can see like<00:20:45.179> this<00:20:45.419> is<00:20:45.600> a<00:20:46.160> desktop<00:20:47.160> app<00:20:47.520> you 00:20:48.830 --> 00:20:48.840 align:start position:0% like this is a desktop app you 00:20:48.840 --> 00:20:52.850 align:start position:0% like this is a desktop app you have<00:20:49.500> to<00:20:49.799> go<00:20:50.400> through<00:20:50.580> the<00:20:50.880> installer 00:20:52.850 --> 00:20:52.860 align:start position:0% have to go through the installer 00:20:52.860 --> 00:21:06.909 align:start position:0% have to go through the installer uh<00:20:52.919> let<00:20:53.460> me<00:20:53.640> check<00:20:53.760> like<00:20:54.059> where<00:20:54.360> it<00:20:54.480> is<00:20:54.660> so 00:21:06.909 --> 00:21:06.919 align:start position:0% 00:21:06.919 --> 00:21:10.150 align:start position:0% so<00:21:07.919> it<00:21:08.280> already<00:21:08.460> created<00:21:09.000> the<00:21:09.299> things<00:21:09.539> but 00:21:10.150 --> 00:21:10.160 align:start position:0% so it already created the things but 00:21:10.160 --> 00:21:12.470 align:start position:0% so it already created the things but downloading<00:21:11.160> B 00:21:12.470 --> 00:21:12.480 align:start position:0% downloading B 00:21:12.480 --> 00:21:16.010 align:start position:0% downloading B mm-hmm 00:21:16.010 --> 00:21:16.020 align:start position:0% 00:21:16.020 --> 00:21:18.230 align:start position:0% so<00:21:16.679> you<00:21:16.799> don't<00:21:17.039> have<00:21:17.160> to<00:21:17.400> wait<00:21:17.580> for<00:21:17.880> this 00:21:18.230 --> 00:21:18.240 align:start position:0% so you don't have to wait for this 00:21:18.240 --> 00:21:23.029 align:start position:0% so you don't have to wait for this normally<00:21:19.200> it's<00:21:19.500> like<00:21:19.740> this<00:21:20.600> uh<00:21:21.620> if<00:21:22.620> if<00:21:22.740> this 00:21:23.029 --> 00:21:23.039 align:start position:0% normally it's like this uh if if this 00:21:23.039 --> 00:21:25.850 align:start position:0% normally it's like this uh if if this doesn't<00:21:23.280> work<00:21:23.580> out<00:21:23.760> then<00:21:24.299> I<00:21:24.720> can<00:21:24.900> I<00:21:25.559> can<00:21:25.679> show 00:21:25.850 --> 00:21:25.860 align:start position:0% doesn't work out then I can I can show 00:21:25.860 --> 00:21:28.090 align:start position:0% doesn't work out then I can I can show you<00:21:26.100> the<00:21:26.460> an<00:21:26.880> already<00:21:27.059> downloaded<00:21:27.720> version 00:21:28.090 --> 00:21:28.100 align:start position:0% you the an already downloaded version 00:21:28.100 --> 00:21:31.130 align:start position:0% you the an already downloaded version and<00:21:29.100> installed<00:21:29.940> the<00:21:30.240> only<00:21:30.360> problem<00:21:30.600> with<00:21:30.960> that 00:21:31.130 --> 00:21:31.140 align:start position:0% and installed the only problem with that 00:21:31.140 --> 00:21:33.289 align:start position:0% and installed the only problem with that is<00:21:31.440> that<00:21:31.740> there<00:21:32.039> is<00:21:32.159> a<00:21:32.340> step<00:21:32.520> like<00:21:32.820> when<00:21:33.120> you 00:21:33.289 --> 00:21:33.299 align:start position:0% is that there is a step like when you 00:21:33.299 --> 00:21:35.690 align:start position:0% is that there is a step like when you download<00:21:33.600> the<00:21:33.960> app<00:21:34.140> first<00:21:34.799> it<00:21:35.039> starts<00:21:35.460> in<00:21:35.520> a 00:21:35.690 --> 00:21:35.700 align:start position:0% download the app first it starts in a 00:21:35.700 --> 00:21:37.370 align:start position:0% download the app first it starts in a mode<00:21:35.880> where 00:21:37.370 --> 00:21:37.380 align:start position:0% mode where 00:21:37.380 --> 00:21:38.149 align:start position:0% mode where um 00:21:38.149 --> 00:21:38.159 align:start position:0% um 00:21:38.159 --> 00:21:40.490 align:start position:0% um like<00:21:38.700> it's<00:21:38.820> a<00:21:39.000> it's<00:21:39.240> a<00:21:39.360> this<00:21:39.659> like<00:21:39.840> ultra<00:21:40.320> light 00:21:40.490 --> 00:21:40.500 align:start position:0% like it's a it's a this like ultra light 00:21:40.500 --> 00:21:43.490 align:start position:0% like it's a it's a this like ultra light mode<00:21:40.799> so<00:21:41.340> it's<00:21:41.460> it's<00:21:41.640> a<00:21:41.880> limited<00:21:42.299> version<00:21:42.600> you 00:21:43.490 --> 00:21:43.500 align:start position:0% mode so it's it's a limited version you 00:21:43.500 --> 00:21:45.590 align:start position:0% mode so it's it's a limited version you can<00:21:43.620> only<00:21:43.860> access<00:21:44.280> data<00:21:44.880> but<00:21:45.179> you<00:21:45.360> cannot 00:21:45.590 --> 00:21:45.600 align:start position:0% can only access data but you cannot 00:21:45.600 --> 00:21:48.010 align:start position:0% can only access data but you cannot upload<00:21:46.020> and<00:21:46.620> in<00:21:46.860> order<00:21:46.980> to 00:21:48.010 --> 00:21:48.020 align:start position:0% upload and in order to 00:21:48.020 --> 00:21:51.289 align:start position:0% upload and in order to unlock<00:21:49.020> this<00:21:49.559> upload<00:21:49.980> functionality<00:21:50.640> you 00:21:51.289 --> 00:21:51.299 align:start position:0% unlock this upload functionality you 00:21:51.299 --> 00:21:52.909 align:start position:0% unlock this upload functionality you have<00:21:51.419> to<00:21:51.600> do<00:21:51.840> the<00:21:52.020> thing<00:21:52.260> what<00:21:52.500> we<00:21:52.620> call<00:21:52.740> the 00:21:52.909 --> 00:21:52.919 align:start position:0% have to do the thing what we call the 00:21:52.919 --> 00:21:55.850 align:start position:0% have to do the thing what we call the cryptoboarding<00:21:53.880> and<00:21:54.659> that<00:21:54.900> is<00:21:55.080> basically<00:21:55.620> you 00:21:55.850 --> 00:21:55.860 align:start position:0% cryptoboarding and that is basically you 00:21:55.860 --> 00:21:58.310 align:start position:0% cryptoboarding and that is basically you have<00:21:56.039> to<00:21:56.220> fund<00:21:56.520> your<00:21:56.640> node<00:21:57.059> so<00:21:57.360> swarm<00:21:57.960> the 00:21:58.310 --> 00:21:58.320 align:start position:0% have to fund your node so swarm the 00:21:58.320 --> 00:22:00.529 align:start position:0% have to fund your node so swarm the swarming<00:21:58.740> that<00:21:59.100> uses<00:21:59.520> the<00:21:59.820> diagnosis 00:22:00.529 --> 00:22:00.539 align:start position:0% swarming that uses the diagnosis 00:22:00.539 --> 00:22:01.669 align:start position:0% swarming that uses the diagnosis blockchain 00:22:01.669 --> 00:22:01.679 align:start position:0% blockchain 00:22:01.679 --> 00:22:04.010 align:start position:0% blockchain and<00:22:02.460> that<00:22:02.760> means<00:22:03.000> that<00:22:03.179> you<00:22:03.360> will<00:22:03.539> need<00:22:03.780> to 00:22:04.010 --> 00:22:04.020 align:start position:0% and that means that you will need to 00:22:04.020 --> 00:22:07.010 align:start position:0% and that means that you will need to have<00:22:04.320> some<00:22:04.919> X<00:22:05.220> die<00:22:05.520> so<00:22:06.000> that<00:22:06.179> it<00:22:06.480> can<00:22:06.600> make<00:22:06.780> the 00:22:07.010 --> 00:22:07.020 align:start position:0% have some X die so that it can make the 00:22:07.020 --> 00:22:08.990 align:start position:0% have some X die so that it can make the transactions<00:22:07.559> for<00:22:07.799> you 00:22:08.990 --> 00:22:09.000 align:start position:0% transactions for you 00:22:09.000 --> 00:22:12.350 align:start position:0% transactions for you and<00:22:09.780> also<00:22:10.380> for<00:22:10.740> uploading<00:22:11.460> data<00:22:12.059> to<00:22:12.179> the 00:22:12.350 --> 00:22:12.360 align:start position:0% and also for uploading data to the 00:22:12.360 --> 00:22:14.390 align:start position:0% and also for uploading data to the network<00:22:12.480> you<00:22:12.900> will<00:22:13.080> need<00:22:13.260> the<00:22:13.440> busy<00:22:13.799> Z<00:22:13.919> token 00:22:14.390 --> 00:22:14.400 align:start position:0% network you will need the busy Z token 00:22:14.400 --> 00:22:17.810 align:start position:0% network you will need the busy Z token so<00:22:15.179> my<00:22:15.780> I<00:22:16.080> will<00:22:16.260> cancel<00:22:16.500> this<00:22:16.860> because<00:22:17.220> like 00:22:17.810 --> 00:22:17.820 align:start position:0% so my I will cancel this because like 00:22:17.820 --> 00:22:20.330 align:start position:0% so my I will cancel this because like it's<00:22:18.059> not<00:22:18.600> it's<00:22:18.600> not<00:22:18.840> working<00:22:19.020> very<00:22:19.500> well 00:22:20.330 --> 00:22:20.340 align:start position:0% it's not it's not working very well 00:22:20.340 --> 00:22:23.570 align:start position:0% it's not it's not working very well and<00:22:21.000> that's<00:22:21.780> not<00:22:22.020> good<00:22:22.260> but 00:22:23.570 --> 00:22:23.580 align:start position:0% and that's not good but 00:22:23.580 --> 00:22:26.630 align:start position:0% and that's not good but I<00:22:24.000> will<00:22:24.120> show<00:22:24.419> you<00:22:24.600> the<00:22:24.840> the<00:22:25.020> network<00:22:25.320> anyhow 00:22:26.630 --> 00:22:26.640 align:start position:0% I will show you the the network anyhow 00:22:26.640 --> 00:22:29.149 align:start position:0% I will show you the the network anyhow or<00:22:27.240> the<00:22:27.539> the<00:22:27.720> version<00:22:27.960> that<00:22:28.380> I<00:22:28.500> installed<00:22:28.740> that 00:22:29.149 --> 00:22:29.159 align:start position:0% or the the version that I installed that 00:22:29.159 --> 00:22:32.750 align:start position:0% or the the version that I installed that I<00:22:29.280> had<00:22:29.460> on<00:22:29.640> my<00:22:30.059> machine<00:22:30.299> installed<00:22:30.960> already 00:22:32.750 --> 00:22:32.760 align:start position:0% I had on my machine installed already 00:22:32.760 --> 00:22:35.330 align:start position:0% I had on my machine installed already so<00:22:33.360> I<00:22:33.720> will<00:22:33.960> just<00:22:34.200> need<00:22:34.380> to 00:22:35.330 --> 00:22:35.340 align:start position:0% so I will just need to 00:22:35.340 --> 00:22:38.270 align:start position:0% so I will just need to put<00:22:36.000> this<00:22:36.179> thing<00:22:36.360> back 00:22:38.270 --> 00:22:38.280 align:start position:0% put this thing back 00:22:38.280 --> 00:22:46.250 align:start position:0% put this thing back the<00:22:38.640> library<00:22:38.880> application<00:22:39.659> support 00:22:46.250 --> 00:22:46.260 align:start position:0% 00:22:46.260 --> 00:22:50.690 align:start position:0% and<00:22:46.799> if<00:22:47.100> you<00:22:47.400> have<00:22:47.940> that<00:22:48.559> then<00:22:49.559> when<00:22:50.159> you<00:22:50.460> start 00:22:50.690 --> 00:22:50.700 align:start position:0% and if you have that then when you start 00:22:50.700 --> 00:22:52.490 align:start position:0% and if you have that then when you start the 00:22:52.490 --> 00:22:52.500 align:start position:0% the 00:22:52.500 --> 00:22:54.409 align:start position:0% the app<00:22:52.919> like<00:22:53.280> that 00:22:54.409 --> 00:22:54.419 align:start position:0% app like that 00:22:54.419 --> 00:22:57.169 align:start position:0% app like that no 00:22:57.169 --> 00:22:57.179 align:start position:0% 00:22:57.179 --> 00:22:58.789 align:start position:0% Fargo 00:22:58.789 --> 00:22:58.799 align:start position:0% Fargo 00:22:58.799 --> 00:23:01.070 align:start position:0% Fargo yeah<00:22:59.340> okay 00:23:01.070 --> 00:23:01.080 align:start position:0% yeah okay 00:23:01.080 --> 00:23:04.610 align:start position:0% yeah okay me 00:23:04.610 --> 00:23:04.620 align:start position:0% 00:23:04.620 --> 00:23:07.490 align:start position:0% that's<00:23:05.400> the<00:23:05.700> demo<00:23:06.059> effect 00:23:07.490 --> 00:23:07.500 align:start position:0% that's the demo effect 00:23:07.500 --> 00:23:08.870 align:start position:0% that's the demo effect and<00:23:08.039> then 00:23:08.870 --> 00:23:08.880 align:start position:0% and then 00:23:08.880 --> 00:23:12.890 align:start position:0% and then the<00:23:08.940> network 00:23:12.890 --> 00:23:12.900 align:start position:0% 00:23:12.900 --> 00:23:17.870 align:start position:0% um<00:23:13.080> yeah<00:23:13.679> maybe<00:23:14.220> uh 00:23:17.870 --> 00:23:17.880 align:start position:0% 00:23:17.880 --> 00:23:21.789 align:start position:0% so<00:23:18.720> I'm 00:23:21.789 --> 00:23:21.799 align:start position:0% 00:23:21.799 --> 00:23:25.310 align:start position:0% yeah<00:23:22.799> so<00:23:23.159> I<00:23:23.520> did<00:23:23.640> some<00:23:23.820> testing<00:23:24.299> and<00:23:24.659> they<00:23:25.020> did 00:23:25.310 --> 00:23:25.320 align:start position:0% yeah so I did some testing and they did 00:23:25.320 --> 00:23:27.350 align:start position:0% yeah so I did some testing and they did not<00:23:25.440> really<00:23:25.679> work<00:23:26.039> well<00:23:26.340> so<00:23:26.700> this<00:23:26.820> is<00:23:27.000> why<00:23:27.120> I 00:23:27.350 --> 00:23:27.360 align:start position:0% not really work well so this is why I 00:23:27.360 --> 00:23:29.149 align:start position:0% not really work well so this is why I might<00:23:27.659> try<00:23:27.840> to<00:23:28.020> do<00:23:28.260> my 00:23:29.149 --> 00:23:29.159 align:start position:0% might try to do my 00:23:29.159 --> 00:23:32.270 align:start position:0% might try to do my network<00:23:30.120> connection<00:23:30.600> and<00:23:31.200> yeah<00:23:31.380> I<00:23:31.679> managed<00:23:32.159> to 00:23:32.270 --> 00:23:32.280 align:start position:0% network connection and yeah I managed to 00:23:32.280 --> 00:23:37.909 align:start position:0% network connection and yeah I managed to overwrite<00:23:32.880> this<00:23:33.720> for<00:23:34.320> some<00:23:34.740> reason 00:23:37.909 --> 00:23:37.919 align:start position:0% 00:23:37.919 --> 00:23:47.870 align:start position:0% that's<00:23:38.880> not<00:23:39.120> good<00:23:39.419> but<00:23:39.900> we<00:23:40.140> will 00:23:47.870 --> 00:23:47.880 align:start position:0% 00:23:47.880 --> 00:23:52.669 align:start position:0% oh<00:23:48.480> yeah<00:23:48.659> that's<00:23:49.380> true<00:23:49.679> okay<00:23:50.360> thanks<00:23:51.360> for<00:23:51.720> like 00:23:52.669 --> 00:23:52.679 align:start position:0% oh yeah that's true okay thanks for like 00:23:52.679 --> 00:23:54.230 align:start position:0% oh yeah that's true okay thanks for like in<00:23:52.860> the<00:23:53.039> in<00:23:53.220> the<00:23:53.340> when<00:23:53.520> you're<00:23:53.760> sharing<00:23:54.120> your 00:23:54.230 --> 00:23:54.240 align:start position:0% in the in the when you're sharing your 00:23:54.240 --> 00:23:56.690 align:start position:0% in the in the when you're sharing your screen<00:23:54.480> it's<00:23:54.840> not<00:23:55.020> necessarily<00:23:55.559> the<00:23:55.860> you<00:23:56.460> see 00:23:56.690 --> 00:23:56.700 align:start position:0% screen it's not necessarily the you see 00:23:56.700 --> 00:24:01.070 align:start position:0% screen it's not necessarily the you see on<00:23:57.120> these<00:23:57.480> things<00:23:57.600> I<00:23:58.559> put<00:23:58.919> it<00:23:59.100> inside<00:23:59.340> okay 00:24:01.070 --> 00:24:01.080 align:start position:0% on these things I put it inside okay 00:24:01.080 --> 00:24:03.049 align:start position:0% on these things I put it inside okay so<00:24:01.500> that's<00:24:01.620> good 00:24:03.049 --> 00:24:03.059 align:start position:0% so that's good 00:24:03.059 --> 00:24:09.470 align:start position:0% so that's good so<00:24:03.480> we<00:24:04.140> will<00:24:04.320> need<00:24:04.559> to<00:24:04.740> do<00:24:04.980> some 00:24:09.470 --> 00:24:09.480 align:start position:0% 00:24:09.480 --> 00:24:11.870 align:start position:0% yeah 00:24:11.870 --> 00:24:11.880 align:start position:0% yeah 00:24:11.880 --> 00:24:14.510 align:start position:0% yeah okay<00:24:12.480> and<00:24:12.720> we'll<00:24:12.960> just<00:24:13.140> put<00:24:13.320> back<00:24:13.559> the<00:24:13.919> here 00:24:14.510 --> 00:24:14.520 align:start position:0% okay and we'll just put back the here 00:24:14.520 --> 00:24:19.330 align:start position:0% okay and we'll just put back the here remove<00:24:15.480> the 00:24:19.330 --> 00:24:19.340 align:start position:0% 00:24:19.340 --> 00:24:22.070 align:start position:0% supports<00:24:20.340> from<00:24:20.580> desktop 00:24:22.070 --> 00:24:22.080 align:start position:0% supports from desktop 00:24:22.080 --> 00:24:24.230 align:start position:0% supports from desktop so<00:24:22.440> it<00:24:22.559> means<00:24:22.740> someone<00:24:22.919> is<00:24:23.280> listening<00:24:23.880> to<00:24:24.059> the 00:24:24.230 --> 00:24:24.240 align:start position:0% so it means someone is listening to the 00:24:24.240 --> 00:24:27.649 align:start position:0% so it means someone is listening to the while<00:24:24.419> I'm<00:24:24.600> attacking<00:24:24.780> and<00:24:25.260> that's<00:24:25.500> good<00:24:25.740> news 00:24:27.649 --> 00:24:27.659 align:start position:0% while I'm attacking and that's good news 00:24:27.659 --> 00:24:28.650 align:start position:0% while I'm attacking and that's good news um 00:24:28.650 --> 00:24:28.660 align:start position:0% um 00:24:28.660 --> 00:24:29.930 align:start position:0% um [Music] 00:24:29.930 --> 00:24:29.940 align:start position:0% [Music] 00:24:29.940 --> 00:24:32.750 align:start position:0% [Music] all<00:24:30.299> right 00:24:32.750 --> 00:24:32.760 align:start position:0% 00:24:32.760 --> 00:24:34.370 align:start position:0% okay 00:24:34.370 --> 00:24:34.380 align:start position:0% okay 00:24:34.380 --> 00:24:36.950 align:start position:0% okay let<00:24:34.620> me<00:24:34.799> check 00:24:36.950 --> 00:24:36.960 align:start position:0% let me check 00:24:36.960 --> 00:24:39.590 align:start position:0% let me check yeah<00:24:37.380> so<00:24:38.280> now<00:24:38.460> you<00:24:38.700> have<00:24:38.880> all<00:24:39.059> the<00:24:39.240> files 00:24:39.590 --> 00:24:39.600 align:start position:0% yeah so now you have all the files 00:24:39.600 --> 00:24:41.330 align:start position:0% yeah so now you have all the files downloaded<00:24:40.020> and<00:24:40.260> it's<00:24:40.440> already<00:24:40.620> set<00:24:40.980> up<00:24:41.159> and 00:24:41.330 --> 00:24:41.340 align:start position:0% downloaded and it's already set up and 00:24:41.340 --> 00:24:43.490 align:start position:0% downloaded and it's already set up and for<00:24:42.120> running<00:24:42.299> yeah<00:24:42.659> we<00:24:42.900> just<00:24:42.960> need<00:24:43.140> to<00:24:43.320> start 00:24:43.490 --> 00:24:43.500 align:start position:0% for running yeah we just need to start 00:24:43.500 --> 00:24:47.390 align:start position:0% for running yeah we just need to start it<00:24:44.059> so<00:24:45.059> in<00:24:45.659> this<00:24:45.840> case<00:24:46.020> it<00:24:46.440> just<00:24:46.620> starts<00:24:47.039> up<00:24:47.159> as 00:24:47.390 --> 00:24:47.400 align:start position:0% it so in this case it just starts up as 00:24:47.400 --> 00:24:50.450 align:start position:0% it so in this case it just starts up as this<00:24:47.700> one<00:24:47.960> small<00:24:48.960> icon 00:24:50.450 --> 00:24:50.460 align:start position:0% this one small icon 00:24:50.460 --> 00:24:53.510 align:start position:0% this one small icon and<00:24:51.120> then<00:24:51.299> it<00:24:51.539> opens<00:24:51.960> the<00:24:52.260> UI<00:24:52.679> in<00:24:52.919> the<00:24:53.100> browser 00:24:53.510 --> 00:24:53.520 align:start position:0% and then it opens the UI in the browser 00:24:53.520 --> 00:24:55.549 align:start position:0% and then it opens the UI in the browser oh 00:24:55.549 --> 00:24:55.559 align:start position:0% oh 00:24:55.559 --> 00:24:57.770 align:start position:0% oh and 00:24:57.770 --> 00:24:57.780 align:start position:0% and 00:24:57.780 --> 00:25:00.710 align:start position:0% and something<00:24:58.380> is<00:24:58.919> happening 00:25:00.710 --> 00:25:00.720 align:start position:0% something is happening 00:25:00.720 --> 00:25:02.330 align:start position:0% something is happening but 00:25:02.330 --> 00:25:02.340 align:start position:0% but 00:25:02.340 --> 00:25:07.070 align:start position:0% but this<00:25:02.820> is<00:25:03.000> not<00:25:03.240> what<00:25:03.780> I<00:25:03.900> expected<00:25:04.440> but 00:25:07.070 --> 00:25:07.080 align:start position:0% this is not what I expected but 00:25:07.080 --> 00:25:09.590 align:start position:0% this is not what I expected but anyhow<00:25:07.740> the<00:25:08.039> the<00:25:08.220> point<00:25:08.460> is<00:25:08.700> that<00:25:09.000> like<00:25:09.179> if<00:25:09.419> you 00:25:09.590 --> 00:25:09.600 align:start position:0% anyhow the the point is that like if you 00:25:09.600 --> 00:25:12.590 align:start position:0% anyhow the the point is that like if you have<00:25:09.720> a<00:25:09.780> working<00:25:09.960> internet<00:25:10.380> connection<00:25:10.799> like 00:25:12.590 --> 00:25:12.600 align:start position:0% have a working internet connection like 00:25:12.600 --> 00:25:16.970 align:start position:0% have a working internet connection like then<00:25:13.140> this<00:25:13.500> is<00:25:13.679> this<00:25:14.340> is<00:25:14.520> working<00:25:14.840> so<00:25:15.840> and<00:25:16.799> then 00:25:16.970 --> 00:25:16.980 align:start position:0% then this is this is working so and then 00:25:16.980 --> 00:25:23.690 align:start position:0% then this is this is working so and then you<00:25:17.220> can<00:25:17.340> do<00:25:17.580> this<00:25:17.880> so<00:25:18.360> yes 00:25:23.690 --> 00:25:23.700 align:start position:0% 00:25:23.700 --> 00:25:26.930 align:start position:0% I<00:25:24.240> can<00:25:24.360> use<00:25:24.539> your<00:25:24.779> computer 00:25:26.930 --> 00:25:26.940 align:start position:0% I can use your computer 00:25:26.940 --> 00:25:37.909 align:start position:0% I can use your computer uh<00:25:27.720> you<00:25:27.960> have<00:25:28.080> HDMI 00:25:37.909 --> 00:25:37.919 align:start position:0% 00:25:37.919 --> 00:25:41.690 align:start position:0% Defcon<00:25:38.640> Workshop<00:25:39.059> Wi-Fi<00:25:39.480> all<00:25:40.260> right<00:25:40.500> oops<00:25:41.400> not 00:25:41.690 --> 00:25:41.700 align:start position:0% Defcon Workshop Wi-Fi all right oops not 00:25:41.700 --> 00:25:48.590 align:start position:0% Defcon Workshop Wi-Fi all right oops not that<00:25:42.539> one<00:25:42.720> that<00:25:43.020> one 00:25:48.590 --> 00:25:48.600 align:start position:0% 00:25:48.600 --> 00:25:50.090 align:start position:0% so<00:25:49.260> wait 00:25:50.090 --> 00:25:50.100 align:start position:0% so wait 00:25:50.100 --> 00:25:54.769 align:start position:0% so wait um something<00:25:50.460> is<00:25:50.760> working<00:25:50.940> actually<00:25:51.360> so<00:25:51.900> we 00:25:54.769 --> 00:25:54.779 align:start position:0% um something is working actually so we 00:25:54.779 --> 00:25:57.230 align:start position:0% um something is working actually so we sorry<00:25:55.020> what<00:25:55.320> is<00:25:55.440> the<00:25:55.620> password 00:25:57.230 --> 00:25:57.240 align:start position:0% sorry what is the password 00:25:57.240 --> 00:25:58.370 align:start position:0% sorry what is the password that 00:25:58.370 --> 00:25:58.380 align:start position:0% that 00:25:58.380 --> 00:26:05.450 align:start position:0% that okay 00:26:05.450 --> 00:26:05.460 align:start position:0% 00:26:05.460 --> 00:26:07.130 align:start position:0% okay<00:26:05.580> thanks 00:26:07.130 --> 00:26:07.140 align:start position:0% okay thanks 00:26:07.140 --> 00:26:11.890 align:start position:0% okay thanks thanks<00:26:07.559> everyone 00:26:11.890 --> 00:26:11.900 align:start position:0% 00:26:11.900 --> 00:26:15.230 align:start position:0% all<00:26:12.900> right<00:26:13.080> let<00:26:13.860> me<00:26:14.039> see<00:26:14.159> if<00:26:14.400> it<00:26:14.640> works<00:26:15.000> better 00:26:15.230 --> 00:26:15.240 align:start position:0% all right let me see if it works better 00:26:15.240 --> 00:26:26.510 align:start position:0% all right let me see if it works better or<00:26:15.659> not 00:26:26.510 --> 00:26:26.520 align:start position:0% 00:26:26.520 --> 00:26:29.930 align:start position:0% okay<00:26:27.240> so<00:26:27.600> it's<00:26:28.260> somewhat<00:26:28.559> working<00:26:28.860> like<00:26:29.700> it's 00:26:29.930 --> 00:26:29.940 align:start position:0% okay so it's somewhat working like it's 00:26:29.940 --> 00:26:32.090 align:start position:0% okay so it's somewhat working like it's I<00:26:30.600> can<00:26:30.720> show<00:26:30.900> you<00:26:31.080> the<00:26:31.440> the<00:26:31.620> most 00:26:32.090 --> 00:26:32.100 align:start position:0% I can show you the the most 00:26:32.100 --> 00:26:34.970 align:start position:0% I can show you the the most functionality<00:26:32.760> of<00:26:33.000> this<00:26:33.240> thing 00:26:34.970 --> 00:26:34.980 align:start position:0% functionality of this thing 00:26:34.980 --> 00:26:38.029 align:start position:0% functionality of this thing so 00:26:38.029 --> 00:26:38.039 align:start position:0% 00:26:38.039 --> 00:26:41.149 align:start position:0% so<00:26:38.220> yeah<00:26:38.580> there<00:26:38.760> is<00:26:38.880> one<00:26:39.059> warning<00:26:39.679> which<00:26:40.679> might 00:26:41.149 --> 00:26:41.159 align:start position:0% so yeah there is one warning which might 00:26:41.159 --> 00:26:43.850 align:start position:0% so yeah there is one warning which might just<00:26:41.460> go<00:26:41.640> away<00:26:41.820> once<00:26:42.480> in<00:26:42.600> the<00:26:42.720> network<00:26:42.840> is 00:26:43.850 --> 00:26:43.860 align:start position:0% just go away once in the network is 00:26:43.860 --> 00:26:46.130 align:start position:0% just go away once in the network is in<00:26:44.279> a<00:26:44.460> condition<00:26:44.640> where 00:26:46.130 --> 00:26:46.140 align:start position:0% in a condition where 00:26:46.140 --> 00:26:49.430 align:start position:0% in a condition where it<00:26:46.740> should<00:26:46.860> work<00:26:47.100> so<00:26:47.940> yeah<00:26:48.299> like<00:26:48.600> you<00:26:49.080> can<00:26:49.200> see 00:26:49.430 --> 00:26:49.440 align:start position:0% it should work so yeah like you can see 00:26:49.440 --> 00:26:54.649 align:start position:0% it should work so yeah like you can see that<00:26:50.120> I<00:26:51.120> have<00:26:51.299> connected<00:26:51.840> to<00:26:52.100> 214<00:26:53.179> other<00:26:54.179> nodes 00:26:54.649 --> 00:26:54.659 align:start position:0% that I have connected to 214 other nodes 00:26:54.659 --> 00:26:56.750 align:start position:0% that I have connected to 214 other nodes I<00:26:55.080> don't 00:26:56.750 --> 00:26:56.760 align:start position:0% I don't 00:26:56.760 --> 00:26:58.430 align:start position:0% I don't wait<00:26:57.240> yeah 00:26:58.430 --> 00:26:58.440 align:start position:0% wait yeah 00:26:58.440 --> 00:27:01.789 align:start position:0% wait yeah okay<00:26:58.799> it's<00:26:59.039> jumping<00:26:59.640> around<00:26:59.820> so<00:27:00.299> this<00:27:01.260> is<00:27:01.440> not 00:27:01.789 --> 00:27:01.799 align:start position:0% okay it's jumping around so this is not 00:27:01.799 --> 00:27:04.909 align:start position:0% okay it's jumping around so this is not what<00:27:02.760> usually<00:27:03.059> happens 00:27:04.909 --> 00:27:04.919 align:start position:0% what usually happens 00:27:04.919 --> 00:27:07.250 align:start position:0% what usually happens but<00:27:05.580> yeah<00:27:05.760> it's<00:27:06.000> like<00:27:06.179> you<00:27:06.720> connect<00:27:06.900> around 00:27:07.250 --> 00:27:07.260 align:start position:0% but yeah it's like you connect around 00:27:07.260 --> 00:27:10.370 align:start position:0% but yeah it's like you connect around 100<00:27:07.559> nodes<00:27:08.159> and<00:27:08.520> 100<00:27:08.640> Pairs<00:27:09.240> and<00:27:09.480> then<00:27:09.659> you<00:27:10.260> can 00:27:10.370 --> 00:27:10.380 align:start position:0% 100 nodes and 100 Pairs and then you can 00:27:10.380 --> 00:27:13.130 align:start position:0% 100 nodes and 100 Pairs and then you can use<00:27:10.860> that<00:27:11.159> to<00:27:11.640> uh 00:27:13.130 --> 00:27:13.140 align:start position:0% use that to uh 00:27:13.140 --> 00:27:15.649 align:start position:0% use that to uh to<00:27:13.440> to<00:27:13.559> upload<00:27:14.220> and<00:27:14.400> download<00:27:14.640> data<00:27:15.240> you<00:27:15.539> can 00:27:15.649 --> 00:27:15.659 align:start position:0% to to upload and download data you can 00:27:15.659 --> 00:27:17.990 align:start position:0% to to upload and download data you can go<00:27:15.840> here<00:27:16.080> upload<00:27:16.679> download<00:27:16.919> so<00:27:17.640> the<00:27:17.880> only 00:27:17.990 --> 00:27:18.000 align:start position:0% go here upload download so the only 00:27:18.000 --> 00:27:20.269 align:start position:0% go here upload download so the only difference<00:27:18.240> is<00:27:18.600> that<00:27:18.900> in<00:27:19.260> the<00:27:19.500> when<00:27:20.100> you 00:27:20.269 --> 00:27:20.279 align:start position:0% difference is that in the when you 00:27:20.279 --> 00:27:22.310 align:start position:0% difference is that in the when you install<00:27:20.520> it<00:27:20.820> in<00:27:21.000> the<00:27:21.179> first<00:27:21.299> time<00:27:21.539> you<00:27:22.200> don't 00:27:22.310 --> 00:27:22.320 align:start position:0% install it in the first time you don't 00:27:22.320 --> 00:27:24.289 align:start position:0% install it in the first time you don't have<00:27:22.559> the<00:27:22.799> wallet<00:27:23.159> set<00:27:23.400> up<00:27:23.580> and<00:27:23.940> you<00:27:24.120> don't 00:27:24.289 --> 00:27:24.299 align:start position:0% have the wallet set up and you don't 00:27:24.299 --> 00:27:26.750 align:start position:0% have the wallet set up and you don't have<00:27:24.659> this<00:27:24.900> checkbook<00:27:25.380> which<00:27:25.740> is<00:27:25.919> also<00:27:26.220> not 00:27:26.750 --> 00:27:26.760 align:start position:0% have this checkbook which is also not 00:27:26.760 --> 00:27:29.269 align:start position:0% have this checkbook which is also not working<00:27:27.059> at<00:27:27.299> this<00:27:27.480> moment<00:27:27.779> but<00:27:28.559> the<00:27:28.740> the<00:27:28.980> point 00:27:29.269 --> 00:27:29.279 align:start position:0% working at this moment but the the point 00:27:29.279 --> 00:27:30.649 align:start position:0% working at this moment but the the point is<00:27:29.460> that 00:27:30.649 --> 00:27:30.659 align:start position:0% is that 00:27:30.659 --> 00:27:32.930 align:start position:0% is that at<00:27:31.260> that<00:27:31.440> point<00:27:31.559> you<00:27:31.860> have<00:27:32.100> to<00:27:32.400> do<00:27:32.820> this 00:27:32.930 --> 00:27:32.940 align:start position:0% at that point you have to do this 00:27:32.940 --> 00:27:34.669 align:start position:0% at that point you have to do this Krypton<00:27:33.299> warning<00:27:33.720> and<00:27:33.900> for<00:27:34.080> that<00:27:34.200> we<00:27:34.440> actually 00:27:34.669 --> 00:27:34.679 align:start position:0% Krypton warning and for that we actually 00:27:34.679 --> 00:27:37.850 align:start position:0% Krypton warning and for that we actually have<00:27:35.159> a<00:27:35.460> way<00:27:36.000> to<00:27:36.299> like<00:27:36.840> different<00:27:37.080> ways<00:27:37.500> to<00:27:37.679> do 00:27:37.850 --> 00:27:37.860 align:start position:0% have a way to like different ways to do 00:27:37.860 --> 00:27:40.070 align:start position:0% have a way to like different ways to do like<00:27:38.340> you<00:27:38.580> can<00:27:38.700> use<00:27:38.940> either<00:27:39.299> a<00:27:39.659> gift<00:27:39.840> code 00:27:40.070 --> 00:27:40.080 align:start position:0% like you can use either a gift code 00:27:40.080 --> 00:27:42.289 align:start position:0% like you can use either a gift code which<00:27:40.500> we<00:27:40.620> have<00:27:40.799> here<00:27:41.100> so<00:27:41.580> if<00:27:41.820> you<00:27:41.880> are<00:27:42.000> curious 00:27:42.289 --> 00:27:42.299 align:start position:0% which we have here so if you are curious 00:27:42.299 --> 00:27:44.029 align:start position:0% which we have here so if you are curious and<00:27:42.480> want<00:27:42.720> to<00:27:42.840> try<00:27:43.020> out<00:27:43.200> and<00:27:43.500> you<00:27:43.679> don't<00:27:43.860> want 00:27:44.029 --> 00:27:44.039 align:start position:0% and want to try out and you don't want 00:27:44.039 --> 00:27:46.669 align:start position:0% and want to try out and you don't want to<00:27:44.159> buy<00:27:44.279> busy<00:27:44.760> easy<00:27:44.880> then<00:27:45.179> look<00:27:45.840> for<00:27:46.080> gas<00:27:46.320> pair 00:27:46.669 --> 00:27:46.679 align:start position:0% to buy busy easy then look for gas pair 00:27:46.679 --> 00:27:48.830 align:start position:0% to buy busy easy then look for gas pair here<00:27:47.159> and<00:27:47.520> then<00:27:47.640> he<00:27:47.880> has<00:27:48.059> a<00:27:48.299> bunch<00:27:48.480> of<00:27:48.600> codes 00:27:48.830 --> 00:27:48.840 align:start position:0% here and then he has a bunch of codes 00:27:48.840 --> 00:27:52.010 align:start position:0% here and then he has a bunch of codes already<00:27:49.320> printed<00:27:49.919> and<00:27:50.760> then<00:27:51.000> like<00:27:51.480> give<00:27:51.659> it<00:27:51.840> a 00:27:52.010 --> 00:27:52.020 align:start position:0% already printed and then like give it a 00:27:52.020 --> 00:27:54.769 align:start position:0% already printed and then like give it a good<00:27:52.080> internet<00:27:52.260> connection<00:27:52.740> so<00:27:53.220> that<00:27:53.520> to<00:27:54.360> to 00:27:54.769 --> 00:27:54.779 align:start position:0% good internet connection so that to to 00:27:54.779 --> 00:27:57.890 align:start position:0% good internet connection so that to to have<00:27:55.020> a<00:27:55.200> good<00:27:55.320> experience<00:27:55.799> on<00:27:56.159> that<00:27:56.779> you<00:27:57.779> can 00:27:57.890 --> 00:27:57.900 align:start position:0% have a good experience on that you can 00:27:57.900 --> 00:28:00.830 align:start position:0% have a good experience on that you can also<00:27:58.200> set<00:27:58.440> up<00:27:58.620> its<00:27:59.100> uh<00:27:59.580> with<00:27:59.940> X<00:28:00.120> die<00:28:00.360> and<00:28:00.720> we 00:28:00.830 --> 00:28:00.840 align:start position:0% also set up its uh with X die and we 00:28:00.840 --> 00:28:03.409 align:start position:0% also set up its uh with X die and we also<00:28:01.140> provided<00:28:01.559> some<00:28:01.860> guides<00:28:02.340> how<00:28:02.940> you<00:28:03.120> can<00:28:03.240> do 00:28:03.409 --> 00:28:03.419 align:start position:0% also provided some guides how you can do 00:28:03.419 --> 00:28:05.990 align:start position:0% also provided some guides how you can do it<00:28:03.600> with<00:28:03.779> with<00:28:04.140> a<00:28:04.380> bank<00:28:04.500> card<00:28:04.740> but<00:28:05.220> like<00:28:05.460> maybe 00:28:05.990 --> 00:28:06.000 align:start position:0% it with with a bank card but like maybe 00:28:06.000 --> 00:28:10.130 align:start position:0% it with with a bank card but like maybe a<00:28:06.360> crypto<00:28:06.659> so<00:28:06.960> don't<00:28:07.500> do<00:28:07.740> that<00:28:07.919> uh 00:28:10.130 --> 00:28:10.140 align:start position:0% a crypto so don't do that uh 00:28:10.140 --> 00:28:13.250 align:start position:0% a crypto so don't do that uh use<00:28:10.740> the<00:28:10.919> codes 00:28:13.250 --> 00:28:13.260 align:start position:0% 00:28:13.260 --> 00:28:17.390 align:start position:0% and<00:28:13.980> then<00:28:14.159> so<00:28:15.120> with<00:28:15.779> this<00:28:16.020> app<00:28:16.260> then<00:28:16.860> you<00:28:17.279> can 00:28:17.390 --> 00:28:17.400 align:start position:0% and then so with this app then you can 00:28:17.400 --> 00:28:19.669 align:start position:0% and then so with this app then you can hear<00:28:17.760> like<00:28:18.419> you<00:28:18.659> can<00:28:18.840> upload<00:28:19.260> and<00:28:19.440> download 00:28:19.669 --> 00:28:19.679 align:start position:0% hear like you can upload and download 00:28:19.679 --> 00:28:21.769 align:start position:0% hear like you can upload and download content<00:28:20.279> I'm<00:28:20.820> a<00:28:21.059> bit 00:28:21.769 --> 00:28:21.779 align:start position:0% content I'm a bit 00:28:21.779 --> 00:28:25.250 align:start position:0% content I'm a bit now<00:28:22.380> scared<00:28:22.919> to<00:28:23.100> try<00:28:23.400> it<00:28:23.640> because<00:28:24.419> it<00:28:25.020> might 00:28:25.250 --> 00:28:25.260 align:start position:0% now scared to try it because it might 00:28:25.260 --> 00:28:26.990 align:start position:0% now scared to try it because it might give<00:28:25.440> you<00:28:25.559> the<00:28:25.740> impression<00:28:26.279> is<00:28:26.520> not<00:28:26.760> working 00:28:26.990 --> 00:28:27.000 align:start position:0% give you the impression is not working 00:28:27.000 --> 00:28:28.310 align:start position:0% give you the impression is not working but<00:28:27.360> it<00:28:27.539> is 00:28:28.310 --> 00:28:28.320 align:start position:0% but it is 00:28:28.320 --> 00:28:31.730 align:start position:0% but it is so<00:28:28.980> like<00:28:29.520> I<00:28:29.760> will<00:28:29.880> upload<00:28:30.179> my<00:28:30.480> presentation<00:28:30.960> in 00:28:31.730 --> 00:28:31.740 align:start position:0% so like I will upload my presentation in 00:28:31.740 --> 00:28:33.409 align:start position:0% so like I will upload my presentation in this<00:28:32.159> format 00:28:33.409 --> 00:28:33.419 align:start position:0% this format 00:28:33.419 --> 00:28:35.690 align:start position:0% this format I<00:28:33.539> need<00:28:33.840> to<00:28:34.020> add<00:28:34.140> the<00:28:34.320> positive<00:28:34.620> stamp<00:28:35.100> okay<00:28:35.460> I 00:28:35.690 --> 00:28:35.700 align:start position:0% I need to add the positive stamp okay I 00:28:35.700 --> 00:28:37.789 align:start position:0% I need to add the positive stamp okay I have<00:28:35.880> one<00:28:36.179> so<00:28:36.840> there<00:28:37.020> is<00:28:37.200> this<00:28:37.320> concept<00:28:37.620> of 00:28:37.789 --> 00:28:37.799 align:start position:0% have one so there is this concept of 00:28:37.799 --> 00:28:41.870 align:start position:0% have one so there is this concept of postage<00:28:38.279> stamps<00:28:38.760> so<00:28:39.600> when<00:28:39.960> you<00:28:40.200> have<00:28:40.880> the 00:28:41.870 --> 00:28:41.880 align:start position:0% postage stamps so when you have the 00:28:41.880 --> 00:28:44.750 align:start position:0% postage stamps so when you have the money<00:28:42.059> for<00:28:42.480> for<00:28:42.900> uploading<00:28:43.679> basically<00:28:44.460> the 00:28:44.750 --> 00:28:44.760 align:start position:0% money for for uploading basically the 00:28:44.760 --> 00:28:47.149 align:start position:0% money for for uploading basically the this<00:28:44.940> postage<00:28:45.360> stamp<00:28:45.659> is<00:28:46.500> something<00:28:46.740> that<00:28:47.039> you 00:28:47.149 --> 00:28:47.159 align:start position:0% this postage stamp is something that you 00:28:47.159 --> 00:28:49.070 align:start position:0% this postage stamp is something that you need<00:28:47.279> to<00:28:47.460> attach<00:28:47.760> to<00:28:47.940> your<00:28:48.179> content<00:28:48.600> and 00:28:49.070 --> 00:28:49.080 align:start position:0% need to attach to your content and 00:28:49.080 --> 00:28:50.990 align:start position:0% need to attach to your content and basically<00:28:49.440> it's<00:28:49.620> two<00:28:49.919> things<00:28:50.159> like<00:28:50.460> you<00:28:50.640> buy<00:28:50.820> a 00:28:50.990 --> 00:28:51.000 align:start position:0% basically it's two things like you buy a 00:28:51.000 --> 00:28:52.909 align:start position:0% basically it's two things like you buy a capacit<00:28:51.480> certain<00:28:51.720> capacity<00:28:52.260> for<00:28:52.620> a<00:28:52.740> certain 00:28:52.909 --> 00:28:52.919 align:start position:0% capacit certain capacity for a certain 00:28:52.919 --> 00:28:55.850 align:start position:0% capacit certain capacity for a certain amount<00:28:53.220> of<00:28:53.460> time<00:28:53.700> so<00:28:54.480> this<00:28:54.840> is<00:28:54.900> like<00:28:55.200> the<00:28:55.679> post 00:28:55.850 --> 00:28:55.860 align:start position:0% amount of time so this is like the post 00:28:55.860 --> 00:28:57.950 align:start position:0% amount of time so this is like the post we<00:28:56.159> call<00:28:56.279> it<00:28:56.400> positive<00:28:56.820> stamp<00:28:57.179> and<00:28:57.480> then<00:28:57.659> you 00:28:57.950 --> 00:28:57.960 align:start position:0% we call it positive stamp and then you 00:28:57.960 --> 00:29:00.470 align:start position:0% we call it positive stamp and then you attach<00:28:58.380> it<00:28:58.559> I<00:28:59.039> mean<00:28:59.220> it's<00:28:59.340> formatted<00:28:59.880> easy<00:29:00.120> to 00:29:00.470 --> 00:29:00.480 align:start position:0% attach it I mean it's formatted easy to 00:29:00.480 --> 00:29:03.470 align:start position:0% attach it I mean it's formatted easy to all<00:29:00.840> your<00:29:01.279> data<00:29:02.279> that<00:29:02.460> you<00:29:02.580> uploaded<00:29:03.059> and<00:29:03.299> this 00:29:03.470 --> 00:29:03.480 align:start position:0% all your data that you uploaded and this 00:29:03.480 --> 00:29:05.750 align:start position:0% all your data that you uploaded and this is<00:29:03.600> how<00:29:03.960> the<00:29:04.140> the<00:29:04.380> node<00:29:04.620> the<00:29:04.860> store<00:29:05.039> nodes<00:29:05.460> know 00:29:05.750 --> 00:29:05.760 align:start position:0% is how the the node the store nodes know 00:29:05.760 --> 00:29:08.990 align:start position:0% is how the the node the store nodes know how<00:29:06.600> how<00:29:06.840> long<00:29:07.140> they<00:29:07.620> should<00:29:07.799> be<00:29:07.980> preserved 00:29:08.990 --> 00:29:09.000 align:start position:0% how how long they should be preserved 00:29:09.000 --> 00:29:13.070 align:start position:0% how how long they should be preserved and<00:29:09.779> then<00:29:10.020> this<00:29:10.440> is<00:29:10.559> also<00:29:10.799> used<00:29:11.039> later<00:29:11.400> for<00:29:12.179> uh 00:29:13.070 --> 00:29:13.080 align:start position:0% and then this is also used later for uh 00:29:13.080 --> 00:29:16.010 align:start position:0% and then this is also used later for uh the<00:29:13.919> redistribution<00:29:14.760> of<00:29:15.120> the<00:29:15.360> value<00:29:15.539> of<00:29:15.840> the 00:29:16.010 --> 00:29:16.020 align:start position:0% the redistribution of the value of the 00:29:16.020 --> 00:29:18.909 align:start position:0% the redistribution of the value of the posit<00:29:16.320> slam<00:29:16.740> so<00:29:16.919> the<00:29:17.100> node<00:29:17.279> operators 00:29:18.909 --> 00:29:18.919 align:start position:0% posit slam so the node operators 00:29:18.919 --> 00:29:22.730 align:start position:0% posit slam so the node operators when<00:29:19.919> they<00:29:20.159> have<00:29:20.340> the<00:29:20.760> data<00:29:21.120> stored<00:29:21.539> uh<00:29:22.380> in<00:29:22.559> the 00:29:22.730 --> 00:29:22.740 align:start position:0% when they have the data stored uh in the 00:29:22.740 --> 00:29:25.310 align:start position:0% when they have the data stored uh in the storage<00:29:22.860> incentives<00:29:23.520> game<00:29:23.820> but<00:29:24.720> I<00:29:25.020> will<00:29:25.140> talk 00:29:25.310 --> 00:29:25.320 align:start position:0% storage incentives game but I will talk 00:29:25.320 --> 00:29:28.190 align:start position:0% storage incentives game but I will talk a<00:29:25.440> bit<00:29:25.559> about<00:29:25.740> later<00:29:26.419> they<00:29:27.419> they<00:29:27.600> participate 00:29:28.190 --> 00:29:28.200 align:start position:0% a bit about later they they participate 00:29:28.200 --> 00:29:31.130 align:start position:0% a bit about later they they participate in<00:29:28.440> that<00:29:28.559> and<00:29:28.980> then<00:29:29.220> they<00:29:29.940> get<00:29:30.419> they<00:29:30.779> can<00:29:30.960> get 00:29:31.130 --> 00:29:31.140 align:start position:0% in that and then they get they can get 00:29:31.140 --> 00:29:33.710 align:start position:0% in that and then they get they can get the<00:29:31.380> value<00:29:31.559> of<00:29:31.919> these<00:29:32.159> postage<00:29:32.520> stamps<00:29:33.000> so 00:29:33.710 --> 00:29:33.720 align:start position:0% the value of these postage stamps so 00:29:33.720 --> 00:29:36.850 align:start position:0% the value of these postage stamps so here<00:29:34.020> I<00:29:34.620> chose<00:29:34.919> the<00:29:35.100> postage<00:29:35.520> slump 00:29:36.850 --> 00:29:36.860 align:start position:0% here I chose the postage slump 00:29:36.860 --> 00:29:40.130 align:start position:0% here I chose the postage slump and<00:29:37.860> then<00:29:38.100> I<00:29:38.520> will<00:29:38.640> upload<00:29:39.000> it<00:29:39.240> and<00:29:39.659> then<00:29:39.899> we 00:29:40.130 --> 00:29:40.140 align:start position:0% and then I will upload it and then we 00:29:40.140 --> 00:29:42.049 align:start position:0% and then I will upload it and then we will<00:29:40.380> see 00:29:42.049 --> 00:29:42.059 align:start position:0% will see 00:29:42.059 --> 00:29:45.710 align:start position:0% will see all<00:29:42.600> right<00:29:42.659> so<00:29:42.960> something<00:29:43.380> worked<00:29:44.159> uh 00:29:45.710 --> 00:29:45.720 align:start position:0% all right so something worked uh 00:29:45.720 --> 00:29:48.169 align:start position:0% all right so something worked uh I<00:29:46.320> mean<00:29:46.440> I<00:29:46.740> this<00:29:47.399> is<00:29:47.520> a<00:29:47.640> cheating<00:29:47.880> a<00:29:48.120> bit 00:29:48.169 --> 00:29:48.179 align:start position:0% I mean I this is a cheating a bit 00:29:48.179 --> 00:29:50.330 align:start position:0% I mean I this is a cheating a bit because<00:29:48.419> I<00:29:48.720> managed<00:29:49.080> to<00:29:49.200> upload<00:29:49.620> the<00:29:49.799> data<00:29:50.159> to 00:29:50.330 --> 00:29:50.340 align:start position:0% because I managed to upload the data to 00:29:50.340 --> 00:29:52.430 align:start position:0% because I managed to upload the data to the<00:29:50.520> my<00:29:50.820> locally<00:29:51.120> running<00:29:51.299> swarm<00:29:51.840> node<00:29:52.080> so<00:29:52.320> it 00:29:52.430 --> 00:29:52.440 align:start position:0% the my locally running swarm node so it 00:29:52.440 --> 00:29:54.409 align:start position:0% the my locally running swarm node so it doesn't<00:29:52.620> mean<00:29:52.860> necessarily<00:29:53.340> that<00:29:53.520> it<00:29:54.179> it 00:29:54.409 --> 00:29:54.419 align:start position:0% doesn't mean necessarily that it it 00:29:54.419 --> 00:29:58.310 align:start position:0% doesn't mean necessarily that it it probably<00:29:54.659> propagated<00:29:55.380> to<00:29:55.679> the<00:29:55.799> network<00:29:55.980> but 00:29:58.310 --> 00:29:58.320 align:start position:0% probably propagated to the network but 00:29:58.320 --> 00:30:00.590 align:start position:0% probably propagated to the network but um yeah<00:29:59.220> it's<00:29:59.520> like<00:29:59.760> it<00:30:00.059> would<00:30:00.179> be<00:30:00.299> good<00:30:00.419> to 00:30:00.590 --> 00:30:00.600 align:start position:0% um yeah it's like it would be good to 00:30:00.600 --> 00:30:02.810 align:start position:0% um yeah it's like it would be good to share<00:30:00.720> with<00:30:00.960> someone<00:30:01.260> and<00:30:01.919> download<00:30:02.220> that<00:30:02.580> but 00:30:02.810 --> 00:30:02.820 align:start position:0% share with someone and download that but 00:30:02.820 --> 00:30:04.250 align:start position:0% share with someone and download that but like<00:30:03.059> this<00:30:03.240> is<00:30:03.360> how<00:30:03.480> it<00:30:03.659> works<00:30:03.899> like<00:30:04.080> it 00:30:04.250 --> 00:30:04.260 align:start position:0% like this is how it works like it 00:30:04.260 --> 00:30:06.169 align:start position:0% like this is how it works like it generates<00:30:04.679> this<00:30:04.860> hash<00:30:05.100> and<00:30:05.700> you<00:30:06.000> can<00:30:06.059> just 00:30:06.169 --> 00:30:06.179 align:start position:0% generates this hash and you can just 00:30:06.179 --> 00:30:08.210 align:start position:0% generates this hash and you can just copy<00:30:06.480> this<00:30:06.659> hash<00:30:06.960> and<00:30:07.200> then<00:30:07.440> share<00:30:07.980> it<00:30:08.100> with 00:30:08.210 --> 00:30:08.220 align:start position:0% copy this hash and then share it with 00:30:08.220 --> 00:30:09.649 align:start position:0% copy this hash and then share it with someone<00:30:08.399> else<00:30:08.640> and<00:30:08.880> they<00:30:09.059> can<00:30:09.240> access<00:30:09.360> the 00:30:09.649 --> 00:30:09.659 align:start position:0% someone else and they can access the 00:30:09.659 --> 00:30:11.690 align:start position:0% someone else and they can access the data<00:30:09.960> with<00:30:10.140> this<00:30:10.320> hash<00:30:10.559> from<00:30:10.740> the<00:30:10.919> network 00:30:11.690 --> 00:30:11.700 align:start position:0% data with this hash from the network 00:30:11.700 --> 00:30:14.269 align:start position:0% data with this hash from the network and<00:30:12.539> yeah<00:30:12.840> it<00:30:13.080> has<00:30:13.200> some<00:30:13.380> functionality<00:30:13.860> where 00:30:14.269 --> 00:30:14.279 align:start position:0% and yeah it has some functionality where 00:30:14.279 --> 00:30:16.490 align:start position:0% and yeah it has some functionality where you<00:30:14.460> can<00:30:14.580> manage<00:30:15.000> your<00:30:15.240> wallet<00:30:15.659> and<00:30:16.080> then<00:30:16.320> your 00:30:16.490 --> 00:30:16.500 align:start position:0% you can manage your wallet and then your 00:30:16.500 --> 00:30:18.950 align:start position:0% you can manage your wallet and then your balance<00:30:17.039> and<00:30:17.580> your<00:30:18.179> checkbook<00:30:18.600> so<00:30:18.840> the 00:30:18.950 --> 00:30:18.960 align:start position:0% balance and your checkbook so the 00:30:18.960 --> 00:30:20.750 align:start position:0% balance and your checkbook so the checkbook<00:30:19.260> is<00:30:19.500> the<00:30:19.679> thing<00:30:19.799> that<00:30:20.100> is<00:30:20.220> used<00:30:20.460> for 00:30:20.750 --> 00:30:20.760 align:start position:0% checkbook is the thing that is used for 00:30:20.760 --> 00:30:24.889 align:start position:0% checkbook is the thing that is used for the<00:30:21.059> the<00:30:21.299> bandwidth<00:30:22.020> incentives<00:30:22.520> so<00:30:23.520> if<00:30:24.000> you 00:30:24.889 --> 00:30:24.899 align:start position:0% the the bandwidth incentives so if you 00:30:24.899 --> 00:30:26.810 align:start position:0% the the bandwidth incentives so if you if<00:30:25.260> you<00:30:25.380> are<00:30:25.500> running<00:30:25.679> a<00:30:25.919> full<00:30:26.039> node<00:30:26.399> then<00:30:26.580> this 00:30:26.810 --> 00:30:26.820 align:start position:0% if you are running a full node then this 00:30:26.820 --> 00:30:30.409 align:start position:0% if you are running a full node then this checkbook<00:30:27.440> is<00:30:28.440> uh<00:30:28.860> you<00:30:29.760> that<00:30:29.940> you<00:30:30.299> don't 00:30:30.409 --> 00:30:30.419 align:start position:0% checkbook is uh you that you don't 00:30:30.419 --> 00:30:33.110 align:start position:0% checkbook is uh you that you don't necessarily<00:30:30.779> have<00:30:31.020> to<00:30:31.380> put<00:30:32.279> money<00:30:32.520> in<00:30:32.760> it<00:30:32.880> but 00:30:33.110 --> 00:30:33.120 align:start position:0% necessarily have to put money in it but 00:30:33.120 --> 00:30:35.210 align:start position:0% necessarily have to put money in it but if<00:30:33.360> you<00:30:33.539> want<00:30:33.720> to<00:30:33.840> download<00:30:34.200> big<00:30:34.740> amount<00:30:35.039> of 00:30:35.210 --> 00:30:35.220 align:start position:0% if you want to download big amount of 00:30:35.220 --> 00:30:37.850 align:start position:0% if you want to download big amount of data<00:30:35.700> then<00:30:36.059> you<00:30:36.779> can<00:30:36.899> basically<00:30:37.380> make<00:30:37.679> it 00:30:37.850 --> 00:30:37.860 align:start position:0% data then you can basically make it 00:30:37.860 --> 00:30:40.070 align:start position:0% data then you can basically make it faster<00:30:38.100> by<00:30:38.580> by<00:30:38.760> putting<00:30:39.299> money<00:30:39.779> in<00:30:39.960> the 00:30:40.070 --> 00:30:40.080 align:start position:0% faster by by putting money in the 00:30:40.080 --> 00:30:42.169 align:start position:0% faster by by putting money in the checkbook<00:30:40.440> and<00:30:40.679> then<00:30:40.860> how<00:30:41.399> it<00:30:41.580> works<00:30:41.820> is<00:30:41.940> that 00:30:42.169 --> 00:30:42.179 align:start position:0% checkbook and then how it works is that 00:30:42.179 --> 00:30:44.210 align:start position:0% checkbook and then how it works is that when<00:30:42.360> your<00:30:42.659> node<00:30:43.020> is<00:30:43.200> requesting<00:30:43.620> data<00:30:44.039> from 00:30:44.210 --> 00:30:44.220 align:start position:0% when your node is requesting data from 00:30:44.220 --> 00:30:48.710 align:start position:0% when your node is requesting data from another<00:30:44.399> node<00:30:44.940> then<00:30:45.840> they<00:30:46.380> create<00:30:46.620> a<00:30:47.720> balance 00:30:48.710 --> 00:30:48.720 align:start position:0% another node then they create a balance 00:30:48.720 --> 00:30:51.049 align:start position:0% another node then they create a balance between<00:30:49.440> them<00:30:49.740> and<00:30:49.980> if<00:30:50.159> your<00:30:50.340> node<00:30:50.640> is<00:30:50.880> only 00:30:51.049 --> 00:30:51.059 align:start position:0% between them and if your node is only 00:30:51.059 --> 00:30:52.850 align:start position:0% between them and if your node is only downloading<00:30:51.659> then<00:30:51.899> your<00:30:52.200> balance<00:30:52.500> will<00:30:52.740> be 00:30:52.850 --> 00:30:52.860 align:start position:0% downloading then your balance will be 00:30:52.860 --> 00:30:55.070 align:start position:0% downloading then your balance will be negative<00:30:53.159> so<00:30:53.460> then<00:30:53.760> eventually<00:30:54.419> you<00:30:54.779> have<00:30:54.899> to 00:30:55.070 --> 00:30:55.080 align:start position:0% negative so then eventually you have to 00:30:55.080 --> 00:30:56.990 align:start position:0% negative so then eventually you have to have<00:30:55.380> to<00:30:55.500> settle<00:30:55.860> that<00:30:56.039> balance<00:30:56.340> and<00:30:56.580> then<00:30:56.760> you 00:30:56.990 --> 00:30:57.000 align:start position:0% have to settle that balance and then you 00:30:57.000 --> 00:30:58.970 align:start position:0% have to settle that balance and then you can<00:30:57.059> do<00:30:57.179> this<00:30:57.360> with<00:30:57.539> the<00:30:57.720> checkbook<00:30:58.080> and<00:30:58.799> if 00:30:58.970 --> 00:30:58.980 align:start position:0% can do this with the checkbook and if 00:30:58.980 --> 00:31:00.350 align:start position:0% can do this with the checkbook and if you<00:30:59.159> have<00:30:59.279> a<00:30:59.399> full<00:30:59.520> node<00:30:59.940> you<00:31:00.240> don't 00:31:00.350 --> 00:31:00.360 align:start position:0% you have a full node you don't 00:31:00.360 --> 00:31:01.850 align:start position:0% you have a full node you don't necessarily<00:31:00.779> have<00:31:00.960> to<00:31:01.080> do<00:31:01.260> this<00:31:01.380> because<00:31:01.620> the 00:31:01.850 --> 00:31:01.860 align:start position:0% necessarily have to do this because the 00:31:01.860 --> 00:31:03.889 align:start position:0% necessarily have to do this because the full<00:31:02.039> nodes<00:31:02.340> are<00:31:02.520> participating<00:31:03.000> in<00:31:03.360> in 00:31:03.889 --> 00:31:03.899 align:start position:0% full nodes are participating in in 00:31:03.899 --> 00:31:06.710 align:start position:0% full nodes are participating in in sharing<00:31:04.320> the<00:31:04.559> data<00:31:04.919> and<00:31:05.760> uh<00:31:06.120> and<00:31:06.539> then 00:31:06.710 --> 00:31:06.720 align:start position:0% sharing the data and uh and then 00:31:06.720 --> 00:31:09.049 align:start position:0% sharing the data and uh and then basically<00:31:07.140> your<00:31:07.620> overtime<00:31:08.220> your<00:31:08.640> balance 00:31:09.049 --> 00:31:09.059 align:start position:0% basically your overtime your balance 00:31:09.059 --> 00:31:11.750 align:start position:0% basically your overtime your balance will<00:31:09.240> even<00:31:09.480> out<00:31:09.840> so<00:31:10.200> you<00:31:10.860> can<00:31:10.919> also<00:31:11.159> do<00:31:11.399> that<00:31:11.580> if 00:31:11.750 --> 00:31:11.760 align:start position:0% will even out so you can also do that if 00:31:11.760 --> 00:31:13.130 align:start position:0% will even out so you can also do that if you<00:31:11.880> want<00:31:12.000> to<00:31:12.120> use<00:31:12.299> your<00:31:12.480> full<00:31:12.659> note<00:31:12.899> for 00:31:13.130 --> 00:31:13.140 align:start position:0% you want to use your full note for 00:31:13.140 --> 00:31:15.470 align:start position:0% you want to use your full note for uploading<00:31:13.620> data<00:31:13.980> as<00:31:14.159> well<00:31:14.340> but<00:31:15.000> it's<00:31:15.240> not 00:31:15.470 --> 00:31:15.480 align:start position:0% uploading data as well but it's not 00:31:15.480 --> 00:31:17.990 align:start position:0% uploading data as well but it's not necessarily<00:31:16.020> to<00:31:16.799> do<00:31:16.980> that<00:31:17.159> and<00:31:17.520> then<00:31:17.640> we<00:31:17.820> have 00:31:17.990 --> 00:31:18.000 align:start position:0% necessarily to do that and then we have 00:31:18.000 --> 00:31:20.570 align:start position:0% necessarily to do that and then we have these<00:31:18.299> postage<00:31:18.659> stamps<00:31:19.200> and<00:31:19.500> then<00:31:19.740> here<00:31:20.340> you 00:31:20.570 --> 00:31:20.580 align:start position:0% these postage stamps and then here you 00:31:20.580 --> 00:31:22.549 align:start position:0% these postage stamps and then here you can<00:31:20.700> see<00:31:20.880> the<00:31:21.120> statistics<00:31:21.539> of<00:31:21.779> foster<00:31:22.200> sample 00:31:22.549 --> 00:31:22.559 align:start position:0% can see the statistics of foster sample 00:31:22.559 --> 00:31:25.250 align:start position:0% can see the statistics of foster sample manage<00:31:22.919> for<00:31:23.580> systems<00:31:24.120> like<00:31:24.299> this<00:31:24.480> is<00:31:24.600> a 00:31:25.250 --> 00:31:25.260 align:start position:0% manage for systems like this is a 00:31:25.260 --> 00:31:28.610 align:start position:0% manage for systems like this is a the<00:31:25.919> idea<00:31:26.159> for<00:31:26.399> this<00:31:26.580> is<00:31:26.880> that<00:31:27.120> you<00:31:27.720> can<00:31:27.899> like 00:31:28.610 --> 00:31:28.620 align:start position:0% the idea for this is that you can like 00:31:28.620 --> 00:31:30.049 align:start position:0% the idea for this is that you can like basically<00:31:29.039> create<00:31:29.279> different<00:31:29.580> kind<00:31:29.940> of 00:31:30.049 --> 00:31:30.059 align:start position:0% basically create different kind of 00:31:30.059 --> 00:31:33.289 align:start position:0% basically create different kind of content<00:31:30.480> what<00:31:31.200> you<00:31:31.500> want<00:31:31.740> to<00:31:32.039> to<00:31:32.580> share<00:31:32.940> and 00:31:33.289 --> 00:31:33.299 align:start position:0% content what you want to to share and 00:31:33.299 --> 00:31:35.810 align:start position:0% content what you want to to share and for<00:31:33.480> how<00:31:33.720> long<00:31:33.899> and<00:31:34.320> then<00:31:34.440> for<00:31:34.799> those<00:31:35.039> like 00:31:35.810 --> 00:31:35.820 align:start position:0% for how long and then for those like 00:31:35.820 --> 00:31:37.250 align:start position:0% for how long and then for those like different<00:31:36.000> kind<00:31:36.360> of<00:31:36.480> categories<00:31:36.899> you<00:31:37.140> can 00:31:37.250 --> 00:31:37.260 align:start position:0% different kind of categories you can 00:31:37.260 --> 00:31:38.870 align:start position:0% different kind of categories you can create<00:31:37.380> different<00:31:37.620> kind<00:31:37.919> of<00:31:38.039> postage<00:31:38.520> stamps 00:31:38.870 --> 00:31:38.880 align:start position:0% create different kind of postage stamps 00:31:38.880 --> 00:31:42.950 align:start position:0% create different kind of postage stamps and<00:31:39.320> upload<00:31:40.320> the<00:31:40.500> data<00:31:40.980> uh<00:31:41.760> according<00:31:42.539> to<00:31:42.659> this 00:31:42.950 --> 00:31:42.960 align:start position:0% and upload the data uh according to this 00:31:42.960 --> 00:31:47.389 align:start position:0% and upload the data uh according to this category<00:31:43.820> and<00:31:44.820> uh<00:31:45.559> there<00:31:46.559> are<00:31:46.679> also<00:31:46.919> feature 00:31:47.389 --> 00:31:47.399 align:start position:0% category and uh there are also feature 00:31:47.399 --> 00:31:49.549 align:start position:0% category and uh there are also feature called<00:31:47.580> feeds<00:31:48.120> so<00:31:48.480> this<00:31:48.779> is<00:31:48.899> the<00:31:49.140> the<00:31:49.320> thing 00:31:49.549 --> 00:31:49.559 align:start position:0% called feeds so this is the the thing 00:31:49.559 --> 00:31:52.690 align:start position:0% called feeds so this is the the thing that<00:31:49.860> I<00:31:50.039> talked<00:31:50.279> about<00:31:50.399> this<00:31:50.760> mutable<00:31:51.620> chunks 00:31:52.690 --> 00:31:52.700 align:start position:0% that I talked about this mutable chunks 00:31:52.700 --> 00:31:56.510 align:start position:0% that I talked about this mutable chunks or<00:31:53.700> mutable<00:31:54.179> data<00:31:55.020> with<00:31:55.380> sign<00:31:55.620> chunks<00:31:56.220> it 00:31:56.510 --> 00:31:56.520 align:start position:0% or mutable data with sign chunks it 00:31:56.520 --> 00:32:00.529 align:start position:0% or mutable data with sign chunks it enables<00:31:57.059> you<00:31:57.240> to<00:31:57.600> to<00:31:57.960> create<00:31:58.380> like 00:32:00.529 --> 00:32:00.539 align:start position:0% enables you to to create like 00:32:00.539 --> 00:32:01.070 align:start position:0% enables you to to create like um 00:32:01.070 --> 00:32:01.080 align:start position:0% um 00:32:01.080 --> 00:32:03.950 align:start position:0% um a<00:32:01.500> version<00:32:01.860> that<00:32:02.399> can<00:32:02.580> be<00:32:02.760> updated<00:32:03.240> over<00:32:03.659> time 00:32:03.950 --> 00:32:03.960 align:start position:0% a version that can be updated over time 00:32:03.960 --> 00:32:07.610 align:start position:0% a version that can be updated over time and<00:32:04.320> then<00:32:04.559> with<00:32:05.220> that<00:32:05.460> you<00:32:06.059> can<00:32:06.240> hear<00:32:07.080> in<00:32:07.440> this 00:32:07.610 --> 00:32:07.620 align:start position:0% and then with that you can hear in this 00:32:07.620 --> 00:32:10.430 align:start position:0% and then with that you can hear in this in<00:32:07.860> this<00:32:08.100> UI<00:32:08.520> you<00:32:09.120> can<00:32:09.240> even<00:32:09.419> use<00:32:09.779> that<00:32:10.020> as<00:32:10.260> a 00:32:10.430 --> 00:32:10.440 align:start position:0% in this UI you can even use that as a 00:32:10.440 --> 00:32:12.230 align:start position:0% in this UI you can even use that as a for<00:32:10.740> example<00:32:10.919> if<00:32:11.159> you<00:32:11.279> upload<00:32:11.580> your<00:32:11.760> website 00:32:12.230 --> 00:32:12.240 align:start position:0% for example if you upload your website 00:32:12.240 --> 00:32:15.230 align:start position:0% for example if you upload your website then<00:32:12.960> the<00:32:13.260> basic<00:32:13.679> model<00:32:14.220> where<00:32:14.580> you<00:32:14.760> upload<00:32:15.000> it 00:32:15.230 --> 00:32:15.240 align:start position:0% then the basic model where you upload it 00:32:15.240 --> 00:32:16.909 align:start position:0% then the basic model where you upload it will<00:32:15.419> be<00:32:15.600> like<00:32:15.779> you<00:32:15.960> can<00:32:16.140> you<00:32:16.380> will<00:32:16.500> graduate 00:32:16.909 --> 00:32:16.919 align:start position:0% will be like you can you will graduate 00:32:16.919 --> 00:32:18.830 align:start position:0% will be like you can you will graduate the<00:32:17.100> content<00:32:17.520> hash<00:32:17.820> of<00:32:18.000> the<00:32:18.179> data<00:32:18.539> that<00:32:18.659> you 00:32:18.830 --> 00:32:18.840 align:start position:0% the content hash of the data that you 00:32:18.840 --> 00:32:21.289 align:start position:0% the content hash of the data that you uploaded<00:32:19.260> but<00:32:19.500> that<00:32:19.679> will<00:32:19.919> change<00:32:20.220> over<00:32:20.940> time 00:32:21.289 --> 00:32:21.299 align:start position:0% uploaded but that will change over time 00:32:21.299 --> 00:32:24.950 align:start position:0% uploaded but that will change over time as<00:32:21.840> you<00:32:22.020> as<00:32:22.320> you<00:32:22.559> change<00:32:22.799> your<00:32:23.100> website<00:32:23.520> so<00:32:24.419> if 00:32:24.950 --> 00:32:24.960 align:start position:0% as you as you change your website so if 00:32:24.960 --> 00:32:26.930 align:start position:0% as you as you change your website so if you<00:32:25.200> want<00:32:25.380> to<00:32:25.500> avoid<00:32:25.919> the<00:32:26.159> paying<00:32:26.580> the<00:32:26.700> cost 00:32:26.930 --> 00:32:26.940 align:start position:0% you want to avoid the paying the cost 00:32:26.940 --> 00:32:29.450 align:start position:0% you want to avoid the paying the cost for<00:32:27.360> like<00:32:27.600> updating<00:32:28.320> your<00:32:28.679> website<00:32:29.039> every 00:32:29.450 --> 00:32:29.460 align:start position:0% for like updating your website every 00:32:29.460 --> 00:32:32.990 align:start position:0% for like updating your website every time<00:32:29.760> in<00:32:30.419> in<00:32:30.600> ens<00:32:31.380> and<00:32:31.740> then<00:32:31.980> point<00:32:32.460> it<00:32:32.640> to<00:32:32.820> a 00:32:32.990 --> 00:32:33.000 align:start position:0% time in in ens and then point it to a 00:32:33.000 --> 00:32:34.610 align:start position:0% time in in ens and then point it to a different<00:32:33.120> DNS<00:32:33.600> record<00:32:33.840> and<00:32:34.260> pay<00:32:34.440> the 00:32:34.610 --> 00:32:34.620 align:start position:0% different DNS record and pay the 00:32:34.620 --> 00:32:36.590 align:start position:0% different DNS record and pay the transaction<00:32:34.980> cost<00:32:35.279> for<00:32:35.580> that<00:32:35.700> you<00:32:36.240> can<00:32:36.419> this 00:32:36.590 --> 00:32:36.600 align:start position:0% transaction cost for that you can this 00:32:36.600 --> 00:32:39.110 align:start position:0% transaction cost for that you can this you<00:32:37.020> can<00:32:37.080> use<00:32:37.260> this<00:32:37.500> feeds<00:32:37.919> functionality<00:32:38.520> and 00:32:39.110 --> 00:32:39.120 align:start position:0% you can use this feeds functionality and 00:32:39.120 --> 00:32:41.389 align:start position:0% you can use this feeds functionality and then<00:32:39.360> basically<00:32:39.720> update<00:32:40.140> you<00:32:40.740> can<00:32:40.860> you<00:32:41.220> can 00:32:41.389 --> 00:32:41.399 align:start position:0% then basically update you can you can 00:32:41.399 --> 00:32:43.850 align:start position:0% then basically update you can you can update<00:32:41.700> your<00:32:42.059> feed<00:32:42.299> and<00:32:42.960> then<00:32:43.140> your<00:32:43.380> feed<00:32:43.559> will 00:32:43.850 --> 00:32:43.860 align:start position:0% update your feed and then your feed will 00:32:43.860 --> 00:32:46.789 align:start position:0% update your feed and then your feed will also<00:32:44.279> have<00:32:44.640> uh<00:32:45.480> fixed<00:32:45.960> it's<00:32:46.320> like<00:32:46.500> not 00:32:46.789 --> 00:32:46.799 align:start position:0% also have uh fixed it's like not 00:32:46.799 --> 00:32:49.250 align:start position:0% also have uh fixed it's like not changing<00:32:47.220> hash<00:32:47.640> that<00:32:48.179> you<00:32:48.299> can<00:32:48.419> put<00:32:48.600> in<00:32:48.779> ens 00:32:49.250 --> 00:32:49.260 align:start position:0% changing hash that you can put in ens 00:32:49.260 --> 00:32:50.990 align:start position:0% changing hash that you can put in ens and<00:32:49.500> with<00:32:49.799> that<00:32:49.980> you<00:32:50.279> can<00:32:50.399> update<00:32:50.760> your 00:32:50.990 --> 00:32:51.000 align:start position:0% and with that you can update your 00:32:51.000 --> 00:32:54.289 align:start position:0% and with that you can update your website<00:32:51.480> through<00:32:52.320> the<00:32:52.620> feeds<00:32:52.980> and<00:32:53.580> that's<00:32:53.880> for 00:32:54.289 --> 00:32:54.299 align:start position:0% website through the feeds and that's for 00:32:54.299 --> 00:32:56.269 align:start position:0% website through the feeds and that's for that<00:32:54.419> you<00:32:54.720> don't<00:32:54.840> need<00:32:55.140> to<00:32:55.320> change<00:32:55.799> the<00:32:56.159> the 00:32:56.269 --> 00:32:56.279 align:start position:0% that you don't need to change the the 00:32:56.279 --> 00:32:58.010 align:start position:0% that you don't need to change the the cost<00:32:56.580> on<00:32:56.820> the<00:32:56.940> blockchain 00:32:58.010 --> 00:32:58.020 align:start position:0% cost on the blockchain 00:32:58.020 --> 00:33:00.830 align:start position:0% cost on the blockchain and<00:32:58.620> we<00:32:58.799> have<00:32:58.980> some<00:32:59.220> settings<00:32:59.460> here<00:32:59.940> so<00:33:00.600> this 00:33:00.830 --> 00:33:00.840 align:start position:0% and we have some settings here so this 00:33:00.840 --> 00:33:03.110 align:start position:0% and we have some settings here so this is<00:33:00.960> the<00:33:01.200> desktop<00:33:01.500> app<00:33:01.740> basically<00:33:02.279> just<00:33:02.580> a<00:33:02.760> UI 00:33:03.110 --> 00:33:03.120 align:start position:0% is the desktop app basically just a UI 00:33:03.120 --> 00:33:06.049 align:start position:0% is the desktop app basically just a UI and<00:33:03.720> it<00:33:03.779> looks<00:33:04.080> like<00:33:04.200> it<00:33:04.500> stabilized<00:33:05.220> a<00:33:05.340> bit<00:33:05.460> so 00:33:06.049 --> 00:33:06.059 align:start position:0% and it looks like it stabilized a bit so 00:33:06.059 --> 00:33:08.889 align:start position:0% and it looks like it stabilized a bit so now<00:33:06.779> we<00:33:07.020> have<00:33:07.260> all<00:33:07.679> everything<00:33:08.100> working 00:33:08.889 --> 00:33:08.899 align:start position:0% now we have all everything working 00:33:08.899 --> 00:33:12.110 align:start position:0% now we have all everything working seemingly<00:33:09.899> and<00:33:10.260> then<00:33:10.440> we<00:33:10.740> have<00:33:10.919> like<00:33:11.159> a<00:33:11.520> normal 00:33:12.110 --> 00:33:12.120 align:start position:0% seemingly and then we have like a normal 00:33:12.120 --> 00:33:16.730 align:start position:0% seemingly and then we have like a normal number<00:33:12.720> of<00:33:13.019> Piers<00:33:14.240> uh<00:33:15.260> and<00:33:16.260> yeah<00:33:16.500> this 00:33:16.730 --> 00:33:16.740 align:start position:0% number of Piers uh and yeah this 00:33:16.740 --> 00:33:19.310 align:start position:0% number of Piers uh and yeah this population<00:33:16.980> is<00:33:17.519> not<00:33:17.820> very<00:33:18.059> correct<00:33:18.659> so<00:33:18.840> we<00:33:19.080> we 00:33:19.310 --> 00:33:19.320 align:start position:0% population is not very correct so we we 00:33:19.320 --> 00:33:22.009 align:start position:0% population is not very correct so we we have<00:33:19.860> some<00:33:20.100> analytical<00:33:20.820> tools<00:33:21.360> and<00:33:21.539> it<00:33:21.720> shows 00:33:22.009 --> 00:33:22.019 align:start position:0% have some analytical tools and it shows 00:33:22.019 --> 00:33:24.590 align:start position:0% have some analytical tools and it shows that<00:33:22.200> there<00:33:22.380> are<00:33:22.559> about<00:33:22.880> 2000<00:33:23.880> nodes<00:33:24.179> in<00:33:24.419> the 00:33:24.590 --> 00:33:24.600 align:start position:0% that there are about 2000 nodes in the 00:33:24.600 --> 00:33:27.730 align:start position:0% that there are about 2000 nodes in the network<00:33:24.720> currently<00:33:25.380> so<00:33:26.159> it's<00:33:26.460> like<00:33:26.820> not<00:33:27.299> 80 00:33:27.730 --> 00:33:27.740 align:start position:0% network currently so it's like not 80 00:33:27.740 --> 00:33:31.149 align:start position:0% network currently so it's like not 80 not<00:33:28.740> 3<00:33:29.580> 800 00:33:31.149 --> 00:33:31.159 align:start position:0% not 3 800 00:33:31.159 --> 00:33:34.250 align:start position:0% not 3 800 and<00:33:32.159> most<00:33:32.399> of<00:33:32.580> the<00:33:32.760> nodes<00:33:33.000> are<00:33:33.299> actually<00:33:33.539> like 00:33:34.250 --> 00:33:34.260 align:start position:0% and most of the nodes are actually like 00:33:34.260 --> 00:33:37.610 align:start position:0% and most of the nodes are actually like run<00:33:34.860> by<00:33:35.519> organizations<00:33:36.240> that<00:33:36.720> support<00:33:36.960> swarm 00:33:37.610 --> 00:33:37.620 align:start position:0% run by organizations that support swarm 00:33:37.620 --> 00:33:39.950 align:start position:0% run by organizations that support swarm so<00:33:38.279> there<00:33:38.580> are<00:33:38.760> individual<00:33:39.179> nodes<00:33:39.480> as<00:33:39.779> well 00:33:39.950 --> 00:33:39.960 align:start position:0% so there are individual nodes as well 00:33:39.960 --> 00:33:42.950 align:start position:0% so there are individual nodes as well and<00:33:40.620> you<00:33:40.980> can<00:33:41.039> also<00:33:41.340> start<00:33:41.580> your<00:33:41.820> node<00:33:42.120> and<00:33:42.779> I 00:33:42.950 --> 00:33:42.960 align:start position:0% and you can also start your node and I 00:33:42.960 --> 00:33:46.070 align:start position:0% and you can also start your node and I will<00:33:43.140> talk<00:33:43.380> about<00:33:43.620> that<00:33:44.039> in<00:33:44.460> a<00:33:44.580> minute<00:33:44.760> so<00:33:45.360> I 00:33:46.070 --> 00:33:46.080 align:start position:0% will talk about that in a minute so I 00:33:46.080 --> 00:33:48.590 align:start position:0% will talk about that in a minute so I will<00:33:46.200> just<00:33:46.380> stop<00:33:46.620> this<00:33:46.919> down<00:33:47.159> because<00:33:47.640> like 00:33:48.590 --> 00:33:48.600 align:start position:0% will just stop this down because like 00:33:48.600 --> 00:33:52.730 align:start position:0% will just stop this down because like this<00:33:48.899> is<00:33:49.019> the<00:33:49.260> so<00:33:49.679> this<00:33:49.860> is<00:33:49.980> the<00:33:50.100> desktop<00:33:50.460> app 00:33:52.730 --> 00:33:52.740 align:start position:0% 00:33:52.740 --> 00:33:57.409 align:start position:0% if<00:33:53.220> you<00:33:53.340> want<00:33:53.460> to<00:33:53.640> try<00:33:53.820> out<00:33:54.059> look<00:33:55.019> for<00:33:55.200> that<00:33:55.500> guy 00:33:57.409 --> 00:33:57.419 align:start position:0% if you want to try out look for that guy 00:33:57.419 --> 00:33:58.610 align:start position:0% if you want to try out look for that guy um 00:33:58.610 --> 00:33:58.620 align:start position:0% um 00:33:58.620 --> 00:34:01.070 align:start position:0% um okay<00:33:59.100> so<00:33:59.820> then 00:34:01.070 --> 00:34:01.080 align:start position:0% okay so then 00:34:01.080 --> 00:34:04.009 align:start position:0% okay so then there<00:34:01.559> is<00:34:01.740> another<00:34:01.919> mode<00:34:02.480> which<00:34:03.480> like<00:34:03.840> the 00:34:04.009 --> 00:34:04.019 align:start position:0% there is another mode which like the 00:34:04.019 --> 00:34:05.529 align:start position:0% there is another mode which like the full<00:34:04.140> node 00:34:05.529 --> 00:34:05.539 align:start position:0% full node 00:34:05.539 --> 00:34:10.389 align:start position:0% full node so<00:34:06.539> in<00:34:06.779> order<00:34:06.899> to<00:34:07.080> do<00:34:07.320> that<00:34:07.559> uh<00:34:08.399> you<00:34:09.000> need<00:34:09.960> to 00:34:10.389 --> 00:34:10.399 align:start position:0% so in order to do that uh you need to 00:34:10.399 --> 00:34:14.089 align:start position:0% so in order to do that uh you need to read<00:34:11.399> a<00:34:11.580> bit<00:34:11.760> about<00:34:12.000> like<00:34:12.679> the<00:34:13.679> the 00:34:14.089 --> 00:34:14.099 align:start position:0% read a bit about like the the 00:34:14.099 --> 00:34:17.990 align:start position:0% read a bit about like the the documentation<00:34:14.940> and<00:34:15.780> we<00:34:16.080> just<00:34:16.260> realized<00:34:16.740> that 00:34:17.990 --> 00:34:18.000 align:start position:0% documentation and we just realized that 00:34:18.000 --> 00:34:20.750 align:start position:0% documentation and we just realized that it<00:34:18.480> seems<00:34:18.839> like<00:34:19.020> most<00:34:19.440> people<00:34:19.760> recently 00:34:20.750 --> 00:34:20.760 align:start position:0% it seems like most people recently 00:34:20.760 --> 00:34:23.510 align:start position:0% it seems like most people recently doesn't<00:34:21.419> really<00:34:21.720> like<00:34:22.080> reading<00:34:22.740> or<00:34:23.159> like 00:34:23.510 --> 00:34:23.520 align:start position:0% doesn't really like reading or like 00:34:23.520 --> 00:34:25.730 align:start position:0% doesn't really like reading or like reading<00:34:24.000> documentation<00:34:24.599> or<00:34:25.080> it<00:34:25.260> seems<00:34:25.560> like 00:34:25.730 --> 00:34:25.740 align:start position:0% reading documentation or it seems like 00:34:25.740 --> 00:34:29.089 align:start position:0% reading documentation or it seems like the<00:34:25.980> the<00:34:26.220> way<00:34:27.179> how<00:34:27.419> to<00:34:27.540> do<00:34:27.720> this<00:34:28.020> better<00:34:28.679> it 00:34:29.089 --> 00:34:29.099 align:start position:0% the the way how to do this better it 00:34:29.099 --> 00:34:32.030 align:start position:0% the the way how to do this better it would<00:34:29.280> be<00:34:29.460> video<00:34:29.760> maybe<00:34:30.200> but<00:34:31.200> so<00:34:31.500> we<00:34:31.859> have 00:34:32.030 --> 00:34:32.040 align:start position:0% would be video maybe but so we have 00:34:32.040 --> 00:34:34.129 align:start position:0% would be video maybe but so we have documentation<00:34:32.760> about<00:34:33.060> this<00:34:33.359> but<00:34:33.599> we<00:34:33.780> often 00:34:34.129 --> 00:34:34.139 align:start position:0% documentation about this but we often 00:34:34.139 --> 00:34:37.970 align:start position:0% documentation about this but we often get<00:34:34.320> questions<00:34:35.179> from<00:34:36.179> people<00:34:36.480> like<00:34:37.379> how<00:34:37.679> to<00:34:37.800> do 00:34:37.970 --> 00:34:37.980 align:start position:0% get questions from people like how to do 00:34:37.980 --> 00:34:40.849 align:start position:0% get questions from people like how to do that<00:34:38.359> but<00:34:39.359> actually<00:34:39.599> the<00:34:40.020> the<00:34:40.200> documentation 00:34:40.849 --> 00:34:40.859 align:start position:0% that but actually the the documentation 00:34:40.859 --> 00:34:42.829 align:start position:0% that but actually the the documentation has<00:34:41.399> this 00:34:42.829 --> 00:34:42.839 align:start position:0% has this 00:34:42.839 --> 00:34:43.690 align:start position:0% has this um 00:34:43.690 --> 00:34:43.700 align:start position:0% um 00:34:43.700 --> 00:34:46.730 align:start position:0% um like<00:34:44.700> it<00:34:44.940> describes<00:34:45.659> the<00:34:46.080> the<00:34:46.260> necessary 00:34:46.730 --> 00:34:46.740 align:start position:0% like it describes the the necessary 00:34:46.740 --> 00:34:49.490 align:start position:0% like it describes the the necessary steps<00:34:47.339> and<00:34:48.119> then<00:34:48.300> I'm<00:34:48.659> going<00:34:48.839> to<00:34:49.020> go<00:34:49.260> through 00:34:49.490 --> 00:34:49.500 align:start position:0% steps and then I'm going to go through 00:34:49.500 --> 00:34:52.250 align:start position:0% steps and then I'm going to go through this<00:34:49.800> and<00:34:50.040> explain<00:34:50.280> this<00:34:50.820> maybe<00:34:51.179> it's<00:34:51.599> it's 00:34:52.250 --> 00:34:52.260 align:start position:0% this and explain this maybe it's it's 00:34:52.260 --> 00:34:55.490 align:start position:0% this and explain this maybe it's it's complicated<00:34:52.980> how<00:34:53.520> it's<00:34:53.700> written<00:34:54.240> but<00:34:54.599> this<00:34:55.440> is 00:34:55.490 --> 00:34:55.500 align:start position:0% complicated how it's written but this is 00:34:55.500 --> 00:34:57.890 align:start position:0% complicated how it's written but this is what<00:34:55.740> you<00:34:55.859> need<00:34:55.980> to<00:34:56.099> do<00:34:56.339> basically<00:34:57.119> you<00:34:57.720> need 00:34:57.890 --> 00:34:57.900 align:start position:0% what you need to do basically you need 00:34:57.900 --> 00:35:01.849 align:start position:0% what you need to do basically you need to<00:34:58.200> create<00:34:58.859> a<00:34:59.099> config<00:34:59.460> file<00:34:59.900> add<00:35:00.900> six<00:35:01.500> or<00:35:01.680> seven 00:35:01.849 --> 00:35:01.859 align:start position:0% to create a config file add six or seven 00:35:01.859 --> 00:35:03.890 align:start position:0% to create a config file add six or seven things<00:35:02.099> to<00:35:02.400> it<00:35:02.520> and<00:35:02.760> then<00:35:02.940> you<00:35:03.240> are<00:35:03.359> good<00:35:03.599> to<00:35:03.720> go 00:35:03.890 --> 00:35:03.900 align:start position:0% things to it and then you are good to go 00:35:03.900 --> 00:35:05.810 align:start position:0% things to it and then you are good to go so 00:35:05.810 --> 00:35:05.820 align:start position:0% so 00:35:05.820 --> 00:35:08.030 align:start position:0% so let's<00:35:06.420> start<00:35:06.720> I<00:35:07.200> will<00:35:07.380> start<00:35:07.619> from<00:35:07.859> an 00:35:08.030 --> 00:35:08.040 align:start position:0% let's start I will start from an 00:35:08.040 --> 00:35:09.770 align:start position:0% let's start I will start from an existing<00:35:08.520> config<00:35:08.940> file<00:35:09.180> because<00:35:09.359> I<00:35:09.660> already 00:35:09.770 --> 00:35:09.780 align:start position:0% existing config file because I already 00:35:09.780 --> 00:35:12.890 align:start position:0% existing config file because I already created<00:35:10.320> this<00:35:10.740> and<00:35:11.220> I<00:35:11.460> will<00:35:11.579> go<00:35:11.880> through<00:35:12.359> that 00:35:12.890 --> 00:35:12.900 align:start position:0% created this and I will go through that 00:35:12.900 --> 00:35:16.609 align:start position:0% created this and I will go through that line<00:35:13.140> by<00:35:13.440> line<00:35:13.680> so<00:35:14.099> that<00:35:14.599> I<00:35:15.599> can<00:35:15.720> explain<00:35:15.960> like 00:35:16.609 --> 00:35:16.619 align:start position:0% line by line so that I can explain like 00:35:16.619 --> 00:35:18.050 align:start position:0% line by line so that I can explain like how<00:35:16.920> it<00:35:17.099> works 00:35:18.050 --> 00:35:18.060 align:start position:0% how it works 00:35:18.060 --> 00:35:22.490 align:start position:0% how it works so<00:35:18.960> this<00:35:19.380> is<00:35:19.500> an<00:35:19.680> existing<00:35:20.240> working<00:35:21.240> full<00:35:22.140> node 00:35:22.490 --> 00:35:22.500 align:start position:0% so this is an existing working full node 00:35:22.500 --> 00:35:25.430 align:start position:0% so this is an existing working full node setup<00:35:22.859> maybe<00:35:23.040> I<00:35:23.339> can<00:35:23.460> make<00:35:23.640> it<00:35:23.820> bigger<00:35:24.260> oops<00:35:25.260> I 00:35:25.430 --> 00:35:25.440 align:start position:0% setup maybe I can make it bigger oops I 00:35:25.440 --> 00:35:27.230 align:start position:0% setup maybe I can make it bigger oops I made<00:35:25.680> it<00:35:25.859> smaller 00:35:27.230 --> 00:35:27.240 align:start position:0% made it smaller 00:35:27.240 --> 00:35:28.730 align:start position:0% made it smaller so 00:35:28.730 --> 00:35:28.740 align:start position:0% so 00:35:28.740 --> 00:35:30.349 align:start position:0% so um 00:35:30.349 --> 00:35:30.359 align:start position:0% um 00:35:30.359 --> 00:35:32.210 align:start position:0% um so<00:35:30.780> yeah<00:35:30.900> like<00:35:31.140> first<00:35:31.380> of<00:35:31.500> all<00:35:31.619> like<00:35:31.800> you<00:35:32.099> need 00:35:32.210 --> 00:35:32.220 align:start position:0% so yeah like first of all like you need 00:35:32.220 --> 00:35:36.050 align:start position:0% so yeah like first of all like you need to<00:35:32.400> say<00:35:33.119> tell<00:35:34.079> me<00:35:34.380> that<00:35:34.800> it's<00:35:35.099> your<00:35:35.760> support 00:35:36.050 --> 00:35:36.060 align:start position:0% to say tell me that it's your support 00:35:36.060 --> 00:35:38.750 align:start position:0% to say tell me that it's your support you<00:35:36.480> want<00:35:36.660> to<00:35:36.780> run<00:35:36.960> it<00:35:37.200> in<00:35:37.440> full<00:35:37.740> node<00:35:38.040> so<00:35:38.460> you 00:35:38.750 --> 00:35:38.760 align:start position:0% you want to run it in full node so you 00:35:38.760 --> 00:35:40.849 align:start position:0% you want to run it in full node so you have<00:35:38.940> to<00:35:39.060> do<00:35:39.180> this<00:35:39.359> full<00:35:39.540> note<00:35:39.780> through<00:35:40.079> you 00:35:40.849 --> 00:35:40.859 align:start position:0% have to do this full note through you 00:35:40.859 --> 00:35:43.250 align:start position:0% have to do this full note through you have<00:35:40.920> to<00:35:41.160> specify<00:35:41.579> a<00:35:41.820> data<00:35:42.119> there<00:35:42.359> so<00:35:43.079> like 00:35:43.250 --> 00:35:43.260 align:start position:0% have to specify a data there so like 00:35:43.260 --> 00:35:45.950 align:start position:0% have to specify a data there so like this<00:35:43.500> is<00:35:43.619> where<00:35:43.800> your<00:35:44.040> files<00:35:44.579> live<00:35:44.880> and<00:35:45.780> then 00:35:45.950 --> 00:35:45.960 align:start position:0% this is where your files live and then 00:35:45.960 --> 00:35:48.290 align:start position:0% this is where your files live and then this<00:35:46.619> is<00:35:46.740> you<00:35:47.220> have<00:35:47.339> to<00:35:47.460> make<00:35:47.640> sure<00:35:47.820> that<00:35:48.060> on 00:35:48.290 --> 00:35:48.300 align:start position:0% this is you have to make sure that on 00:35:48.300 --> 00:35:50.630 align:start position:0% this is you have to make sure that on that<00:35:48.599> disk<00:35:49.020> where<00:35:49.200> it<00:35:49.320> points<00:35:49.680> to<00:35:49.859> you<00:35:50.520> have 00:35:50.630 --> 00:35:50.640 align:start position:0% that disk where it points to you have 00:35:50.640 --> 00:35:53.210 align:start position:0% that disk where it points to you have enough<00:35:50.820> space<00:35:51.240> for<00:35:51.599> that<00:35:51.780> and<00:35:52.260> it's<00:35:52.440> also<00:35:52.740> you 00:35:53.210 --> 00:35:53.220 align:start position:0% enough space for that and it's also you 00:35:53.220 --> 00:35:54.890 align:start position:0% enough space for that and it's also you have<00:35:53.339> to<00:35:53.400> make<00:35:53.520> sure<00:35:53.700> that<00:35:53.880> it's<00:35:54.060> an<00:35:54.240> SSD<00:35:54.660> so 00:35:54.890 --> 00:35:54.900 align:start position:0% have to make sure that it's an SSD so 00:35:54.900 --> 00:35:56.930 align:start position:0% have to make sure that it's an SSD so that<00:35:55.140> it's<00:35:55.380> fast<00:35:56.040> enough<00:35:56.220> there<00:35:56.640> is<00:35:56.820> a 00:35:56.930 --> 00:35:56.940 align:start position:0% that it's fast enough there is a 00:35:56.940 --> 00:35:59.930 align:start position:0% that it's fast enough there is a password<00:35:57.500> don't<00:35:58.500> use<00:35:58.800> one 00:35:59.930 --> 00:35:59.940 align:start position:0% password don't use one 00:35:59.940 --> 00:36:02.089 align:start position:0% password don't use one but<00:36:00.780> uh 00:36:02.089 --> 00:36:02.099 align:start position:0% but uh 00:36:02.099 --> 00:36:05.569 align:start position:0% but uh I<00:36:02.880> mean<00:36:03.060> that<00:36:03.839> works<00:36:04.200> for<00:36:04.320> demo<00:36:04.680> purposes 00:36:05.569 --> 00:36:05.579 align:start position:0% I mean that works for demo purposes 00:36:05.579 --> 00:36:09.050 align:start position:0% I mean that works for demo purposes and<00:36:06.480> that<00:36:06.720> protects<00:36:07.320> your<00:36:07.619> your<00:36:08.040> wallet<00:36:08.640> but 00:36:09.050 --> 00:36:09.060 align:start position:0% and that protects your your wallet but 00:36:09.060 --> 00:36:11.510 align:start position:0% and that protects your your wallet but like<00:36:09.300> what<00:36:09.720> we<00:36:09.900> do<00:36:10.140> what<00:36:10.740> and<00:36:10.920> what<00:36:11.160> we<00:36:11.280> say 00:36:11.510 --> 00:36:11.520 align:start position:0% like what we do what and what we say 00:36:11.520 --> 00:36:13.609 align:start position:0% like what we do what and what we say here<00:36:11.820> and<00:36:12.420> maybe<00:36:12.599> what's<00:36:12.960> important<00:36:13.440> to 00:36:13.609 --> 00:36:13.619 align:start position:0% here and maybe what's important to 00:36:13.619 --> 00:36:16.069 align:start position:0% here and maybe what's important to mention<00:36:13.800> is<00:36:14.760> that<00:36:15.359> um 00:36:16.069 --> 00:36:16.079 align:start position:0% mention is that um 00:36:16.079 --> 00:36:19.069 align:start position:0% mention is that um so<00:36:16.619> when<00:36:16.800> when<00:36:17.099> you<00:36:17.339> start<00:36:17.520> B<00:36:17.820> the<00:36:18.720> first<00:36:18.839> time 00:36:19.069 --> 00:36:19.079 align:start position:0% so when when you start B the first time 00:36:19.079 --> 00:36:22.250 align:start position:0% so when when you start B the first time it<00:36:19.560> creates<00:36:19.920> its<00:36:20.579> own<00:36:20.640> wallet<00:36:21.119> and<00:36:21.720> the<00:36:21.960> reason 00:36:22.250 --> 00:36:22.260 align:start position:0% it creates its own wallet and the reason 00:36:22.260 --> 00:36:24.770 align:start position:0% it creates its own wallet and the reason for<00:36:22.619> that<00:36:22.800> is<00:36:23.099> that<00:36:23.280> we<00:36:23.520> don't<00:36:23.700> want<00:36:23.940> people<00:36:24.300> to 00:36:24.770 --> 00:36:24.780 align:start position:0% for that is that we don't want people to 00:36:24.780 --> 00:36:27.530 align:start position:0% for that is that we don't want people to accidentally<00:36:25.500> you<00:36:26.339> know<00:36:26.460> import<00:36:26.820> their<00:36:27.480> their 00:36:27.530 --> 00:36:27.540 align:start position:0% accidentally you know import their their 00:36:27.540 --> 00:36:29.930 align:start position:0% accidentally you know import their their wallet<00:36:28.140> with<00:36:28.500> their<00:36:28.800> funds<00:36:29.160> in<00:36:29.339> it<00:36:29.520> and<00:36:29.760> then 00:36:29.930 --> 00:36:29.940 align:start position:0% wallet with their funds in it and then 00:36:29.940 --> 00:36:31.550 align:start position:0% wallet with their funds in it and then you<00:36:30.240> know<00:36:30.359> like 00:36:31.550 --> 00:36:31.560 align:start position:0% you know like 00:36:31.560 --> 00:36:34.910 align:start position:0% you know like you<00:36:32.220> it's<00:36:32.460> much<00:36:32.880> better<00:36:33.060> just<00:36:33.480> to<00:36:33.720> start<00:36:34.079> your 00:36:34.910 --> 00:36:34.920 align:start position:0% you it's much better just to start your 00:36:34.920 --> 00:36:37.550 align:start position:0% you it's much better just to start your your<00:36:35.220> node<00:36:35.579> without<00:36:35.880> uh<00:36:36.480> with<00:36:37.020> that<00:36:37.140> with<00:36:37.380> an 00:36:37.550 --> 00:36:37.560 align:start position:0% your node without uh with that with an 00:36:37.560 --> 00:36:40.010 align:start position:0% your node without uh with that with an empty<00:36:37.920> wallet<00:36:38.280> and<00:36:38.640> then<00:36:38.760> fund<00:36:39.180> it<00:36:39.300> and<00:36:39.780> then 00:36:40.010 --> 00:36:40.020 align:start position:0% empty wallet and then fund it and then 00:36:40.020 --> 00:36:44.390 align:start position:0% empty wallet and then fund it and then let<00:36:40.740> it<00:36:40.920> run<00:36:41.180> uh<00:36:42.180> because<00:36:42.540> uh<00:36:43.200> currently<00:36:43.920> there 00:36:44.390 --> 00:36:44.400 align:start position:0% let it run uh because uh currently there 00:36:44.400 --> 00:36:46.910 align:start position:0% let it run uh because uh currently there are<00:36:44.700> there<00:36:45.420> are<00:36:45.599> ways<00:36:45.900> to<00:36:46.020> to<00:36:46.260> secure<00:36:46.680> your 00:36:46.910 --> 00:36:46.920 align:start position:0% are there are ways to to secure your 00:36:46.920 --> 00:36:50.450 align:start position:0% are there are ways to to secure your wallet<00:36:47.339> so<00:36:47.640> swarm<00:36:48.359> also<00:36:48.720> uses<00:36:49.200> a<00:36:49.980> thing<00:36:50.160> that 00:36:50.450 --> 00:36:50.460 align:start position:0% wallet so swarm also uses a thing that 00:36:50.460 --> 00:36:52.970 align:start position:0% wallet so swarm also uses a thing that may<00:36:50.700> be<00:36:50.820> familiar<00:36:51.300> from<00:36:51.599> running<00:36:51.839> gets<00:36:52.500> this 00:36:52.970 --> 00:36:52.980 align:start position:0% may be familiar from running gets this 00:36:52.980 --> 00:36:55.430 align:start position:0% may be familiar from running gets this clef<00:36:53.400> so<00:36:54.180> there<00:36:54.359> is<00:36:54.540> there<00:36:54.780> is<00:36:54.900> a<00:36:55.020> version<00:36:55.140> of 00:36:55.430 --> 00:36:55.440 align:start position:0% clef so there is there is a version of 00:36:55.440 --> 00:36:57.349 align:start position:0% clef so there is there is a version of clef<00:36:55.859> which<00:36:56.280> works<00:36:56.579> with<00:36:56.700> swarm<00:36:57.119> which<00:36:57.300> is 00:36:57.349 --> 00:36:57.359 align:start position:0% clef which works with swarm which is 00:36:57.359 --> 00:36:59.329 align:start position:0% clef which works with swarm which is called<00:36:57.540> B<00:36:57.780> clef<00:36:58.200> but<00:36:58.560> we<00:36:58.740> found<00:36:58.980> actually 00:36:59.329 --> 00:36:59.339 align:start position:0% called B clef but we found actually 00:36:59.339 --> 00:37:01.849 align:start position:0% called B clef but we found actually that's<00:36:59.760> that<00:37:00.060> was<00:37:00.300> one<00:37:00.540> of<00:37:00.660> the<00:37:00.900> source<00:37:01.380> of<00:37:01.500> the 00:37:01.849 --> 00:37:01.859 align:start position:0% that's that was one of the source of the 00:37:01.859 --> 00:37:04.550 align:start position:0% that's that was one of the source of the problems<00:37:02.640> of<00:37:02.880> installing<00:37:03.480> your<00:37:03.839> swarm<00:37:04.320> nodes 00:37:04.550 --> 00:37:04.560 align:start position:0% problems of installing your swarm nodes 00:37:04.560 --> 00:37:07.849 align:start position:0% problems of installing your swarm nodes so<00:37:04.740> that<00:37:04.920> made<00:37:05.160> it<00:37:05.400> quite<00:37:06.180> complicated<00:37:06.859> and 00:37:07.849 --> 00:37:07.859 align:start position:0% so that made it quite complicated and 00:37:07.859 --> 00:37:10.550 align:start position:0% so that made it quite complicated and because<00:37:08.579> of<00:37:08.820> that<00:37:09.119> we<00:37:09.599> no<00:37:09.839> longer<00:37:10.079> recommend 00:37:10.550 --> 00:37:10.560 align:start position:0% because of that we no longer recommend 00:37:10.560 --> 00:37:14.089 align:start position:0% because of that we no longer recommend by<00:37:11.040> default<00:37:11.400> to<00:37:11.820> to<00:37:12.060> run<00:37:12.420> it<00:37:12.599> with<00:37:12.839> clef<00:37:13.320> also 00:37:14.089 --> 00:37:14.099 align:start position:0% by default to to run it with clef also 00:37:14.099 --> 00:37:16.910 align:start position:0% by default to to run it with clef also we<00:37:14.400> recommend<00:37:14.820> people<00:37:15.180> that<00:37:15.720> don't<00:37:16.020> put<00:37:16.440> a<00:37:16.800> lot 00:37:16.910 --> 00:37:16.920 align:start position:0% we recommend people that don't put a lot 00:37:16.920 --> 00:37:20.210 align:start position:0% we recommend people that don't put a lot of<00:37:17.040> money<00:37:17.339> in<00:37:17.880> their<00:37:18.119> full<00:37:18.359> nodes<00:37:18.720> or 00:37:20.210 --> 00:37:20.220 align:start position:0% of money in their full nodes or 00:37:20.220 --> 00:37:23.329 align:start position:0% of money in their full nodes or um<00:37:20.280> be<00:37:20.880> in<00:37:21.720> the<00:37:21.900> in<00:37:22.079> the<00:37:22.200> storage<00:37:22.320> incentives<00:37:23.040> I 00:37:23.329 --> 00:37:23.339 align:start position:0% um be in the in the storage incentives I 00:37:23.339 --> 00:37:24.770 align:start position:0% um be in the in the storage incentives I will<00:37:23.460> talk<00:37:23.640> about<00:37:23.820> like 00:37:24.770 --> 00:37:24.780 align:start position:0% will talk about like 00:37:24.780 --> 00:37:26.930 align:start position:0% will talk about like if<00:37:25.200> you<00:37:25.320> want<00:37:25.440> to<00:37:25.560> participate<00:37:26.160> in<00:37:26.460> the<00:37:26.700> in 00:37:26.930 --> 00:37:26.940 align:start position:0% if you want to participate in the in 00:37:26.940 --> 00:37:30.050 align:start position:0% if you want to participate in the in earning<00:37:27.300> BCC<00:37:27.720> you<00:37:28.680> will<00:37:29.160> have<00:37:29.339> to<00:37:29.520> stake<00:37:29.880> some 00:37:30.050 --> 00:37:30.060 align:start position:0% earning BCC you will have to stake some 00:37:30.060 --> 00:37:32.510 align:start position:0% earning BCC you will have to stake some money<00:37:30.240> in<00:37:30.480> it<00:37:30.660> but<00:37:30.900> the<00:37:31.200> the<00:37:31.380> current<00:37:31.859> stake<00:37:32.280> is 00:37:32.510 --> 00:37:32.520 align:start position:0% money in it but the the current stake is 00:37:32.520 --> 00:37:35.030 align:start position:0% money in it but the the current stake is like<00:37:32.760> 10<00:37:32.940> BCC<00:37:33.480> which<00:37:33.960> worth<00:37:34.440> like<00:37:34.740> five 00:37:35.030 --> 00:37:35.040 align:start position:0% like 10 BCC which worth like five 00:37:35.040 --> 00:37:38.569 align:start position:0% like 10 BCC which worth like five dollars<00:37:35.400> so<00:37:36.359> it's<00:37:37.200> I<00:37:37.800> think<00:37:37.920> it's<00:37:38.160> like<00:37:38.339> five 00:37:38.569 --> 00:37:38.579 align:start position:0% dollars so it's I think it's like five 00:37:38.579 --> 00:37:41.030 align:start position:0% dollars so it's I think it's like five dollars<00:37:38.940> is<00:37:39.180> not<00:37:39.359> really<00:37:39.540> worth<00:37:39.900> the<00:37:40.560> hassle 00:37:41.030 --> 00:37:41.040 align:start position:0% dollars is not really worth the hassle 00:37:41.040 --> 00:37:44.569 align:start position:0% dollars is not really worth the hassle of<00:37:41.160> setting<00:37:41.579> up<00:37:41.700> a<00:37:41.940> b<00:37:42.060> clef<00:37:42.560> and<00:37:43.560> just<00:37:44.160> you<00:37:44.400> can 00:37:44.569 --> 00:37:44.579 align:start position:0% of setting up a b clef and just you can 00:37:44.579 --> 00:37:46.730 align:start position:0% of setting up a b clef and just you can secure<00:37:45.060> your<00:37:45.359> thing<00:37:45.599> with<00:37:45.960> a<00:37:46.200> reasonable 00:37:46.730 --> 00:37:46.740 align:start position:0% secure your thing with a reasonable 00:37:46.740 --> 00:37:50.210 align:start position:0% secure your thing with a reasonable strong<00:37:47.160> password 00:37:50.210 --> 00:37:50.220 align:start position:0% 00:37:50.220 --> 00:37:51.410 align:start position:0% then 00:37:51.410 --> 00:37:51.420 align:start position:0% then 00:37:51.420 --> 00:37:54.349 align:start position:0% then there<00:37:52.079> are<00:37:52.200> two<00:37:52.320> other<00:37:52.500> config<00:37:52.980> options<00:37:53.400> that 00:37:54.349 --> 00:37:54.359 align:start position:0% there are two other config options that 00:37:54.359 --> 00:37:57.109 align:start position:0% there are two other config options that it's<00:37:54.839> also<00:37:55.079> documented<00:37:55.680> but 00:37:57.109 --> 00:37:57.119 align:start position:0% it's also documented but 00:37:57.119 --> 00:37:58.910 align:start position:0% it's also documented but um<00:37:57.180> I<00:37:57.599> will<00:37:57.839> just<00:37:58.020> style<00:37:58.200> so<00:37:58.500> the<00:37:58.619> swap 00:37:58.910 --> 00:37:58.920 align:start position:0% um I will just style so the swap 00:37:58.920 --> 00:38:01.730 align:start position:0% um I will just style so the swap endpoint<00:37:59.400> is<00:38:00.060> maybe<00:38:00.359> it's<00:38:00.960> a<00:38:01.140> it<00:38:01.440> has<00:38:01.560> this 00:38:01.730 --> 00:38:01.740 align:start position:0% endpoint is maybe it's a it has this 00:38:01.740 --> 00:38:04.190 align:start position:0% endpoint is maybe it's a it has this historical<00:38:02.160> context<00:38:02.700> so<00:38:03.000> initially<00:38:03.720> we<00:38:03.960> had 00:38:04.190 --> 00:38:04.200 align:start position:0% historical context so initially we had 00:38:04.200 --> 00:38:06.349 align:start position:0% historical context so initially we had this<00:38:04.560> the<00:38:05.040> swap<00:38:05.339> is<00:38:05.520> called<00:38:05.700> bandwidth 00:38:06.349 --> 00:38:06.359 align:start position:0% this the swap is called bandwidth 00:38:06.359 --> 00:38:10.069 align:start position:0% this the swap is called bandwidth incentives<00:38:07.040> internally<00:38:08.040> in<00:38:08.400> swarm<00:38:08.880> lingo 00:38:10.069 --> 00:38:10.079 align:start position:0% incentives internally in swarm lingo 00:38:10.079 --> 00:38:13.310 align:start position:0% incentives internally in swarm lingo and<00:38:10.859> for<00:38:11.220> that<00:38:11.460> you<00:38:12.060> need<00:38:12.240> an<00:38:12.420> RPC<00:38:12.960> endpoint 00:38:13.310 --> 00:38:13.320 align:start position:0% and for that you need an RPC endpoint 00:38:13.320 --> 00:38:16.069 align:start position:0% and for that you need an RPC endpoint and<00:38:14.280> I<00:38:14.640> just<00:38:14.880> added<00:38:15.240> one<00:38:15.480> it's<00:38:15.780> a<00:38:15.960> public 00:38:16.069 --> 00:38:16.079 align:start position:0% and I just added one it's a public 00:38:16.079 --> 00:38:19.190 align:start position:0% and I just added one it's a public endpoint<00:38:16.680> but<00:38:17.220> obviously<00:38:17.820> you<00:38:18.060> can<00:38:18.180> use<00:38:18.480> like 00:38:19.190 --> 00:38:19.200 align:start position:0% endpoint but obviously you can use like 00:38:19.200 --> 00:38:22.430 align:start position:0% endpoint but obviously you can use like on<00:38:19.500> uh<00:38:19.859> on<00:38:20.760> diagnosis<00:38:21.300> chain<00:38:21.540> it's<00:38:21.960> like<00:38:22.200> you 00:38:22.430 --> 00:38:22.440 align:start position:0% on uh on diagnosis chain it's like you 00:38:22.440 --> 00:38:24.430 align:start position:0% on uh on diagnosis chain it's like you can<00:38:22.560> use<00:38:22.740> get<00:38:22.920> block<00:38:23.220> or<00:38:23.640> or<00:38:23.880> whatever 00:38:24.430 --> 00:38:24.440 align:start position:0% can use get block or or whatever 00:38:24.440 --> 00:38:27.349 align:start position:0% can use get block or or whatever provider<00:38:25.440> you<00:38:25.740> want<00:38:25.859> to<00:38:26.040> use<00:38:26.160> or<00:38:26.579> you<00:38:26.760> run<00:38:27.000> your 00:38:27.349 --> 00:38:27.359 align:start position:0% provider you want to use or you run your 00:38:27.359 --> 00:38:29.870 align:start position:0% provider you want to use or you run your own<00:38:27.720> uh 00:38:29.870 --> 00:38:29.880 align:start position:0% own uh 00:38:29.880 --> 00:38:32.690 align:start position:0% own uh but<00:38:30.480> so<00:38:30.599> this<00:38:30.780> is<00:38:30.900> an<00:38:31.020> RPC<00:38:31.500> endpoint<00:38:31.980> to<00:38:32.460> access 00:38:32.690 --> 00:38:32.700 align:start position:0% but so this is an RPC endpoint to access 00:38:32.700 --> 00:38:34.370 align:start position:0% but so this is an RPC endpoint to access the<00:38:33.060> blockchain 00:38:34.370 --> 00:38:34.380 align:start position:0% the blockchain 00:38:34.380 --> 00:38:39.170 align:start position:0% the blockchain and<00:38:35.160> you<00:38:35.820> also<00:38:36.180> need<00:38:36.420> an<00:38:37.079> initial<00:38:37.380> deposit<00:38:38.180> uh 00:38:39.170 --> 00:38:39.180 align:start position:0% and you also need an initial deposit uh 00:38:39.180 --> 00:38:41.750 align:start position:0% and you also need an initial deposit uh config<00:38:40.020> variable<00:38:40.320> so<00:38:40.619> by<00:38:40.920> default<00:38:41.220> it's<00:38:41.520> not 00:38:41.750 --> 00:38:41.760 align:start position:0% config variable so by default it's not 00:38:41.760 --> 00:38:46.849 align:start position:0% config variable so by default it's not zero<00:38:42.180> because<00:38:43.339> as<00:38:44.339> a<00:38:44.720> historically<00:38:45.720> we<00:38:46.320> we 00:38:46.849 --> 00:38:46.859 align:start position:0% zero because as a historically we we 00:38:46.859 --> 00:38:49.910 align:start position:0% zero because as a historically we we recommended<00:38:47.700> people<00:38:47.940> to<00:38:48.300> put<00:38:48.480> some<00:38:48.720> money<00:38:48.960> in 00:38:49.910 --> 00:38:49.920 align:start position:0% recommended people to put some money in 00:38:49.920 --> 00:38:52.130 align:start position:0% recommended people to put some money in their<00:38:50.040> check<00:38:50.220> this<00:38:50.579> is<00:38:50.700> for<00:38:50.880> the<00:38:51.000> checkbook<00:38:51.420> so 00:38:52.130 --> 00:38:52.140 align:start position:0% their check this is for the checkbook so 00:38:52.140 --> 00:38:55.609 align:start position:0% their check this is for the checkbook so in<00:38:52.619> order<00:38:52.740> to<00:38:53.220> have<00:38:53.880> some<00:38:54.180> balance<00:38:54.599> but<00:38:55.079> we 00:38:55.609 --> 00:38:55.619 align:start position:0% in order to have some balance but we 00:38:55.619 --> 00:38:57.650 align:start position:0% in order to have some balance but we found<00:38:55.800> out<00:38:55.980> that<00:38:56.280> in<00:38:56.579> order<00:38:56.700> to<00:38:57.000> start<00:38:57.180> you 00:38:57.650 --> 00:38:57.660 align:start position:0% found out that in order to start you 00:38:57.660 --> 00:38:59.569 align:start position:0% found out that in order to start you don't<00:38:57.839> really<00:38:58.079> need<00:38:58.680> this<00:38:58.859> and<00:38:59.040> if<00:38:59.280> you<00:38:59.460> don't 00:38:59.569 --> 00:38:59.579 align:start position:0% don't really need this and if you don't 00:38:59.579 --> 00:39:01.730 align:start position:0% don't really need this and if you don't want<00:38:59.760> to<00:38:59.940> use<00:39:00.180> your<00:39:00.420> full<00:39:00.660> node<00:39:00.960> for<00:39:01.200> uploading 00:39:01.730 --> 00:39:01.740 align:start position:0% want to use your full node for uploading 00:39:01.740 --> 00:39:04.370 align:start position:0% want to use your full node for uploading or<00:39:01.980> downloading<00:39:02.579> data<00:39:03.060> then<00:39:03.780> you<00:39:04.079> can<00:39:04.200> leave 00:39:04.370 --> 00:39:04.380 align:start position:0% or downloading data then you can leave 00:39:04.380 --> 00:39:08.210 align:start position:0% or downloading data then you can leave it<00:39:04.619> to<00:39:05.400> the<00:39:05.760> initial<00:39:06.060> deposit<00:39:06.599> to<00:39:07.140> zero 00:39:08.210 --> 00:39:08.220 align:start position:0% it to the initial deposit to zero 00:39:08.220 --> 00:39:10.970 align:start position:0% it to the initial deposit to zero in<00:39:08.820> order<00:39:08.940> to<00:39:09.240> do<00:39:09.359> that<00:39:09.540> though<00:39:09.839> like<00:39:10.500> there<00:39:10.800> is 00:39:10.970 --> 00:39:10.980 align:start position:0% in order to do that though like there is 00:39:10.980 --> 00:39:13.490 align:start position:0% in order to do that though like there is a<00:39:11.280> an<00:39:11.700> initial<00:39:12.060> transaction<00:39:12.540> if<00:39:12.900> you<00:39:13.020> want<00:39:13.260> to 00:39:13.490 --> 00:39:13.500 align:start position:0% a an initial transaction if you want to 00:39:13.500 --> 00:39:20.150 align:start position:0% a an initial transaction if you want to run<00:39:14.180> uh<00:39:15.180> a<00:39:16.020> full<00:39:16.680> node<00:39:17.040> it<00:39:17.820> deploys<00:39:18.540> uh 00:39:20.150 --> 00:39:20.160 align:start position:0% run uh a full node it deploys uh 00:39:20.160 --> 00:39:21.410 align:start position:0% run uh a full node it deploys uh uh 00:39:21.410 --> 00:39:21.420 align:start position:0% uh 00:39:21.420 --> 00:39:24.470 align:start position:0% uh checkbook<00:39:22.140> contract<00:39:22.859> and<00:39:23.579> for<00:39:23.820> that<00:39:24.000> you<00:39:24.300> will 00:39:24.470 --> 00:39:24.480 align:start position:0% checkbook contract and for that you will 00:39:24.480 --> 00:39:29.150 align:start position:0% checkbook contract and for that you will need<00:39:24.780> some<00:39:25.619> X<00:39:25.980> die<00:39:26.780> in<00:39:27.780> order<00:39:27.900> to<00:39:28.380> make<00:39:28.920> the 00:39:29.150 --> 00:39:29.160 align:start position:0% need some X die in order to make the 00:39:29.160 --> 00:39:31.790 align:start position:0% need some X die in order to make the transaction<00:39:29.640> but<00:39:30.359> that's<00:39:30.599> the<00:39:30.900> only<00:39:31.079> initial 00:39:31.790 --> 00:39:31.800 align:start position:0% transaction but that's the only initial 00:39:31.800 --> 00:39:34.790 align:start position:0% transaction but that's the only initial cost<00:39:32.040> that<00:39:32.520> you<00:39:32.760> will<00:39:32.880> need<00:39:33.200> and<00:39:34.200> there<00:39:34.619> is 00:39:34.790 --> 00:39:34.800 align:start position:0% cost that you will need and there is 00:39:34.800 --> 00:39:38.990 align:start position:0% cost that you will need and there is this<00:39:35.040> thing<00:39:35.280> which<00:39:35.640> is<00:39:35.760> documented<00:39:36.480> also<00:39:37.020> that 00:39:38.990 --> 00:39:39.000 align:start position:0% this thing which is documented also that 00:39:39.000 --> 00:39:42.829 align:start position:0% this thing which is documented also that you<00:39:39.660> can<00:39:39.780> fine<00:39:40.079> tune<00:39:40.320> your<00:39:40.859> your<00:39:41.520> B<00:39:41.820> node<00:39:42.180> to 00:39:42.829 --> 00:39:42.839 align:start position:0% you can fine tune your your B node to 00:39:42.839 --> 00:39:45.410 align:start position:0% you can fine tune your your B node to increase<00:39:43.440> the<00:39:44.040> default<00:39:44.460> number<00:39:44.940> of<00:39:45.180> open 00:39:45.410 --> 00:39:45.420 align:start position:0% increase the default number of open 00:39:45.420 --> 00:39:47.950 align:start position:0% increase the default number of open files<00:39:46.140> which<00:39:46.380> is<00:39:46.500> something<00:39:46.800> that 00:39:47.950 --> 00:39:47.960 align:start position:0% files which is something that 00:39:47.960 --> 00:39:52.790 align:start position:0% files which is something that Unix<00:39:48.960> system<00:39:49.140> have<00:39:49.740> like<00:39:50.480> basically<00:39:51.480> the<00:39:52.260> open 00:39:52.790 --> 00:39:52.800 align:start position:0% Unix system have like basically the open 00:39:52.800 --> 00:39:56.630 align:start position:0% Unix system have like basically the open files<00:39:53.579> can<00:39:54.240> be<00:39:54.480> open<00:39:54.900> files<00:39:55.500> but<00:39:55.800> also<00:39:56.160> the<00:39:56.460> the 00:39:56.630 --> 00:39:56.640 align:start position:0% files can be open files but also the the 00:39:56.640 --> 00:39:59.150 align:start position:0% files can be open files but also the the network<00:39:57.000> connections<00:39:57.960> in<00:39:58.560> Unix<00:39:58.920> are 00:39:59.150 --> 00:39:59.160 align:start position:0% network connections in Unix are 00:39:59.160 --> 00:40:01.190 align:start position:0% network connections in Unix are represented<00:39:59.640> as<00:39:59.820> files<00:40:00.300> and<00:40:00.480> then<00:40:00.660> we<00:40:00.960> use 00:40:01.190 --> 00:40:01.200 align:start position:0% represented as files and then we use 00:40:01.200 --> 00:40:03.530 align:start position:0% represented as files and then we use quite<00:40:01.440> a<00:40:01.619> few<00:40:01.740> network<00:40:01.980> connections<00:40:02.700> so<00:40:02.940> it's 00:40:03.530 --> 00:40:03.540 align:start position:0% quite a few network connections so it's 00:40:03.540 --> 00:40:06.650 align:start position:0% quite a few network connections so it's better<00:40:03.780> to<00:40:04.079> increase<00:40:04.260> the<00:40:04.859> default<00:40:05.280> values 00:40:06.650 --> 00:40:06.660 align:start position:0% better to increase the default values 00:40:06.660 --> 00:40:09.170 align:start position:0% better to increase the default values and<00:40:07.260> then<00:40:07.440> one<00:40:08.220> more<00:40:08.400> option<00:40:08.700> is<00:40:08.940> this 00:40:09.170 --> 00:40:09.180 align:start position:0% and then one more option is this 00:40:09.180 --> 00:40:12.109 align:start position:0% and then one more option is this resolver<00:40:09.720> options<00:40:10.200> which<00:40:10.980> is<00:40:11.400> only<00:40:11.640> necessary 00:40:12.109 --> 00:40:12.119 align:start position:0% resolver options which is only necessary 00:40:12.119 --> 00:40:15.109 align:start position:0% resolver options which is only necessary if<00:40:12.540> you<00:40:12.660> want<00:40:12.839> to<00:40:13.020> use<00:40:13.260> ens<00:40:13.920> so<00:40:14.400> there<00:40:14.579> is<00:40:14.700> ens 00:40:15.109 --> 00:40:15.119 align:start position:0% if you want to use ens so there is ens 00:40:15.119 --> 00:40:18.230 align:start position:0% if you want to use ens so there is ens integration<00:40:15.599> of<00:40:15.900> swarm<00:40:16.380> that<00:40:17.280> if<00:40:17.760> you<00:40:17.880> have<00:40:18.060> an 00:40:18.230 --> 00:40:18.240 align:start position:0% integration of swarm that if you have an 00:40:18.240 --> 00:40:23.329 align:start position:0% integration of swarm that if you have an eth<00:40:19.099> domain<00:40:20.359> registered<00:40:21.359> then<00:40:22.320> basically<00:40:22.920> you 00:40:23.329 --> 00:40:23.339 align:start position:0% eth domain registered then basically you 00:40:23.339 --> 00:40:26.510 align:start position:0% eth domain registered then basically you can<00:40:23.460> you<00:40:24.000> can<00:40:24.119> set<00:40:24.359> it<00:40:24.599> in<00:40:25.440> DNS<00:40:25.859> record<00:40:26.040> you<00:40:26.400> can 00:40:26.510 --> 00:40:26.520 align:start position:0% can you can set it in DNS record you can 00:40:26.520 --> 00:40:30.550 align:start position:0% can you can set it in DNS record you can set<00:40:26.700> it<00:40:26.820> to<00:40:27.000> your<00:40:27.380> uh<00:40:28.380> to<00:40:29.040> your<00:40:29.339> swarm<00:40:30.180> address 00:40:30.550 --> 00:40:30.560 align:start position:0% set it to your uh to your swarm address 00:40:30.560 --> 00:40:34.609 align:start position:0% set it to your uh to your swarm address and<00:40:31.560> then<00:40:31.940> it<00:40:32.940> it<00:40:33.180> will<00:40:33.420> work<00:40:33.660> with<00:40:33.839> swarm<00:40:34.380> but 00:40:34.609 --> 00:40:34.619 align:start position:0% and then it it will work with swarm but 00:40:34.619 --> 00:40:37.849 align:start position:0% and then it it will work with swarm but it<00:40:34.800> only<00:40:34.980> works<00:40:35.339> with<00:40:35.520> swarm<00:40:36.000> if<00:40:36.240> you<00:40:36.480> set<00:40:37.020> up<00:40:37.260> a 00:40:37.849 --> 00:40:37.859 align:start position:0% it only works with swarm if you set up a 00:40:37.859 --> 00:40:41.329 align:start position:0% it only works with swarm if you set up a resolver<00:40:38.579> for<00:40:38.820> that<00:40:39.000> and<00:40:39.900> since<00:40:40.440> this<00:40:41.160> is 00:40:41.329 --> 00:40:41.339 align:start position:0% resolver for that and since this is 00:40:41.339 --> 00:40:43.790 align:start position:0% resolver for that and since this is happening<00:40:41.820> on<00:40:42.180> ethereum<00:40:42.720> mainnet<00:40:43.260> this 00:40:43.790 --> 00:40:43.800 align:start position:0% happening on ethereum mainnet this 00:40:43.800 --> 00:40:46.670 align:start position:0% happening on ethereum mainnet this requires<00:40:44.220> a<00:40:44.400> different<00:40:44.579> RPC<00:40:45.540> endpoint<00:40:46.020> that 00:40:46.670 --> 00:40:46.680 align:start position:0% requires a different RPC endpoint that 00:40:46.680 --> 00:40:50.450 align:start position:0% requires a different RPC endpoint that the<00:40:46.920> swap<00:40:47.160> endpoint<00:40:47.640> so<00:40:48.140> this<00:40:49.140> is<00:40:49.260> a<00:40:49.619> kind<00:40:50.220> of<00:40:50.339> a 00:40:50.450 --> 00:40:50.460 align:start position:0% the swap endpoint so this is a kind of a 00:40:50.460 --> 00:40:53.569 align:start position:0% the swap endpoint so this is a kind of a trade-off<00:40:50.820> and<00:40:51.660> this<00:40:51.839> is<00:40:52.020> also<00:40:52.320> optional<00:40:52.800> and 00:40:53.569 --> 00:40:53.579 align:start position:0% trade-off and this is also optional and 00:40:53.579 --> 00:40:56.450 align:start position:0% trade-off and this is also optional and this<00:40:53.820> this<00:40:54.060> one<00:40:54.300> this<00:40:54.540> last<00:40:54.780> option<00:40:55.280> is<00:40:56.280> only 00:40:56.450 --> 00:40:56.460 align:start position:0% this this one this last option is only 00:40:56.460 --> 00:41:00.109 align:start position:0% this this one this last option is only needed<00:40:56.940> if<00:40:57.359> you<00:40:57.720> want<00:40:58.560> to<00:40:58.859> enable<00:40:59.339> the<00:40:59.760> debug 00:41:00.109 --> 00:41:00.119 align:start position:0% needed if you want to enable the debug 00:41:00.119 --> 00:41:03.349 align:start position:0% needed if you want to enable the debug API<00:41:00.540> so<00:41:00.720> we<00:41:00.900> want<00:41:01.079> to<00:41:01.200> have<00:41:01.440> access<00:41:01.940> from<00:41:02.940> the 00:41:03.349 --> 00:41:03.359 align:start position:0% API so we want to have access from the 00:41:03.359 --> 00:41:08.329 align:start position:0% API so we want to have access from the HTTP<00:41:03.900> API<00:41:04.619> to<00:41:05.280> the<00:41:05.579> internal 00:41:08.329 --> 00:41:08.339 align:start position:0% HTTP API to the internal 00:41:08.339 --> 00:41:11.150 align:start position:0% HTTP API to the internal um administrative<00:41:09.240> functionality<00:41:10.200> of<00:41:10.980> your 00:41:11.150 --> 00:41:11.160 align:start position:0% um administrative functionality of your 00:41:11.160 --> 00:41:13.970 align:start position:0% um administrative functionality of your node<00:41:11.460> most<00:41:12.300> likely<00:41:12.540> you<00:41:12.839> want<00:41:13.079> it<00:41:13.320> so<00:41:13.560> I<00:41:13.800> have 00:41:13.970 --> 00:41:13.980 align:start position:0% node most likely you want it so I have 00:41:13.980 --> 00:41:16.010 align:start position:0% node most likely you want it so I have for<00:41:14.220> the<00:41:14.460> sake<00:41:14.640> of<00:41:14.820> completeness<00:41:15.300> I<00:41:15.540> added<00:41:15.839> it 00:41:16.010 --> 00:41:16.020 align:start position:0% for the sake of completeness I added it 00:41:16.020 --> 00:41:19.750 align:start position:0% for the sake of completeness I added it to<00:41:16.140> the<00:41:16.380> to<00:41:16.740> the<00:41:16.980> default<00:41:17.280> configuration 00:41:19.750 --> 00:41:19.760 align:start position:0% to the to the default configuration 00:41:19.760 --> 00:41:23.750 align:start position:0% to the to the default configuration and<00:41:20.760> I<00:41:21.000> will<00:41:21.180> just<00:41:21.359> try<00:41:21.540> to<00:41:21.720> run<00:41:21.900> this<00:41:22.260> so 00:41:23.750 --> 00:41:23.760 align:start position:0% and I will just try to run this so 00:41:23.760 --> 00:41:25.910 align:start position:0% and I will just try to run this so let's<00:41:24.180> see 00:41:25.910 --> 00:41:25.920 align:start position:0% let's see 00:41:25.920 --> 00:41:29.450 align:start position:0% let's see um<00:41:26.040> I<00:41:26.339> will<00:41:26.460> skip<00:41:26.760> the<00:41:27.000> step<00:41:27.240> of<00:41:27.780> like<00:41:28.460> doing 00:41:29.450 --> 00:41:29.460 align:start position:0% um I will skip the step of like doing 00:41:29.460 --> 00:41:34.790 align:start position:0% um I will skip the step of like doing the<00:41:30.200> running<00:41:31.200> it<00:41:31.560> one<00:41:31.920> by<00:41:32.160> one<00:41:32.599> like<00:41:33.599> uh<00:41:34.020> so 00:41:34.790 --> 00:41:34.800 align:start position:0% the running it one by one like uh so 00:41:34.800 --> 00:41:36.170 align:start position:0% the running it one by one like uh so starting<00:41:35.040> it<00:41:35.400> and<00:41:35.640> following<00:41:36.000> the 00:41:36.170 --> 00:41:36.180 align:start position:0% starting it and following the 00:41:36.180 --> 00:41:38.569 align:start position:0% starting it and following the documentation<00:41:36.780> step<00:41:37.260> by<00:41:37.500> step<00:41:37.740> and<00:41:38.160> then<00:41:38.280> if 00:41:38.569 --> 00:41:38.579 align:start position:0% documentation step by step and then if 00:41:38.579 --> 00:41:40.849 align:start position:0% documentation step by step and then if that<00:41:38.760> fails<00:41:39.119> then<00:41:39.240> adding<00:41:39.599> the<00:41:39.780> new<00:41:39.960> one<00:41:40.140> the 00:41:40.849 --> 00:41:40.859 align:start position:0% that fails then adding the new one the 00:41:40.859 --> 00:41:43.310 align:start position:0% that fails then adding the new one the new<00:41:41.040> config<00:41:41.339> line<00:41:41.520> I<00:41:42.000> just<00:41:42.180> just<00:41:42.480> I<00:41:42.960> will<00:41:43.079> just 00:41:43.310 --> 00:41:43.320 align:start position:0% new config line I just just I will just 00:41:43.320 --> 00:41:45.710 align:start position:0% new config line I just just I will just use<00:41:43.560> the<00:41:43.980> prepared<00:41:44.820> config<00:41:45.180> that<00:41:45.420> I<00:41:45.599> just 00:41:45.710 --> 00:41:45.720 align:start position:0% use the prepared config that I just 00:41:45.720 --> 00:41:47.390 align:start position:0% use the prepared config that I just explained 00:41:47.390 --> 00:41:47.400 align:start position:0% explained 00:41:47.400 --> 00:41:49.130 align:start position:0% explained okay 00:41:49.130 --> 00:41:49.140 align:start position:0% okay 00:41:49.140 --> 00:41:49.970 align:start position:0% okay um 00:41:49.970 --> 00:41:49.980 align:start position:0% um 00:41:49.980 --> 00:41:55.250 align:start position:0% um why<00:41:50.700> there<00:41:51.000> is<00:41:51.119> no<00:41:51.300> B<00:41:51.540> here<00:41:51.960> I<00:41:52.740> will<00:41:52.920> just<00:41:53.160> use 00:41:55.250 --> 00:41:55.260 align:start position:0% why there is no B here I will just use 00:41:55.260 --> 00:41:58.790 align:start position:0% why there is no B here I will just use I have<00:41:55.740> one<00:41:56.099> I<00:41:56.520> usually<00:41:57.180> built<00:41:57.960> from<00:41:58.200> source 00:41:58.790 --> 00:41:58.800 align:start position:0% I have one I usually built from source 00:41:58.800 --> 00:42:02.210 align:start position:0% I have one I usually built from source so 00:42:02.210 --> 00:42:02.220 align:start position:0% 00:42:02.220 --> 00:42:06.230 align:start position:0% so<00:42:02.400> okay<00:42:02.880> address<00:42:03.540> already<00:42:04.020> news<00:42:04.440> okay 00:42:06.230 --> 00:42:06.240 align:start position:0% so okay address already news okay 00:42:06.240 --> 00:42:08.270 align:start position:0% so okay address already news okay so<00:42:06.540> there<00:42:06.720> is<00:42:06.839> something<00:42:07.140> running<00:42:07.740> here 00:42:08.270 --> 00:42:08.280 align:start position:0% so there is something running here 00:42:08.280 --> 00:42:13.250 align:start position:0% so there is something running here already 00:42:13.250 --> 00:42:13.260 align:start position:0% 00:42:13.260 --> 00:42:17.030 align:start position:0% it's not<00:42:13.920> the 00:42:17.030 --> 00:42:17.040 align:start position:0% 00:42:17.040 --> 00:42:21.050 align:start position:0% ah<00:42:17.579> sorry<00:42:17.820> no<00:42:18.300> I'm<00:42:18.780> wrong<00:42:19.140> wrong<00:42:19.260> tab<00:42:19.980> it<00:42:20.820> was 00:42:21.050 --> 00:42:21.060 align:start position:0% ah sorry no I'm wrong wrong tab it was 00:42:21.060 --> 00:42:22.550 align:start position:0% ah sorry no I'm wrong wrong tab it was the 00:42:22.550 --> 00:42:22.560 align:start position:0% the 00:42:22.560 --> 00:42:27.230 align:start position:0% the the<00:42:23.099> Death<00:42:23.280> Mode 00:42:27.230 --> 00:42:27.240 align:start position:0% 00:42:27.240 --> 00:42:29.150 align:start position:0% full<00:42:27.839> node 00:42:29.150 --> 00:42:29.160 align:start position:0% full node 00:42:29.160 --> 00:42:30.950 align:start position:0% full node B 00:42:30.950 --> 00:42:30.960 align:start position:0% B 00:42:30.960 --> 00:42:33.950 align:start position:0% B so<00:42:31.560> this<00:42:31.859> is<00:42:31.920> how<00:42:32.160> you<00:42:32.339> start<00:42:32.640> it<00:42:32.880> you<00:42:33.599> specify 00:42:33.950 --> 00:42:33.960 align:start position:0% so this is how you start it you specify 00:42:33.960 --> 00:42:35.750 align:start position:0% so this is how you start it you specify the<00:42:34.260> config<00:42:34.680> file 00:42:35.750 --> 00:42:35.760 align:start position:0% the config file 00:42:35.760 --> 00:42:38.930 align:start position:0% the config file and<00:42:36.359> then<00:42:36.480> you<00:42:36.660> start<00:42:36.900> it<00:42:37.200> and<00:42:37.619> then<00:42:37.740> it<00:42:37.980> runs<00:42:38.400> I 00:42:38.930 --> 00:42:38.940 align:start position:0% and then you start it and then it runs I 00:42:38.940 --> 00:42:41.210 align:start position:0% and then you start it and then it runs I will<00:42:39.119> make<00:42:39.240> it<00:42:39.420> a<00:42:39.599> bit<00:42:39.720> smaller<00:42:40.380> so<00:42:40.740> that<00:42:40.920> maybe 00:42:41.210 --> 00:42:41.220 align:start position:0% will make it a bit smaller so that maybe 00:42:41.220 --> 00:42:51.910 align:start position:0% will make it a bit smaller so that maybe you<00:42:41.460> can<00:42:41.579> see<00:42:41.760> more<00:42:42.060> at<00:42:43.020> the<00:42:43.200> same<00:42:43.380> time 00:42:51.910 --> 00:42:51.920 align:start position:0% 00:42:51.920 --> 00:42:55.849 align:start position:0% so<00:42:52.920> what<00:42:53.160> you<00:42:53.339> can<00:42:53.400> see<00:42:53.579> here<00:42:53.820> is<00:42:54.060> that<00:42:54.300> like 00:42:55.849 --> 00:42:55.859 align:start position:0% so what you can see here is that like 00:42:55.859 --> 00:42:58.370 align:start position:0% so what you can see here is that like you<00:42:56.460> have<00:42:56.700> a<00:42:56.820> node<00:42:57.119> running<00:42:57.480> and<00:42:57.900> then<00:42:58.140> it 00:42:58.370 --> 00:42:58.380 align:start position:0% you have a node running and then it 00:42:58.380 --> 00:43:01.010 align:start position:0% you have a node running and then it connects<00:42:58.800> to<00:42:59.040> all<00:42:59.280> these<00:42:59.700> other<00:42:59.819> nodes<00:43:00.480> and 00:43:01.010 --> 00:43:01.020 align:start position:0% connects to all these other nodes and 00:43:01.020 --> 00:43:02.829 align:start position:0% connects to all these other nodes and then 00:43:02.829 --> 00:43:02.839 align:start position:0% then 00:43:02.839 --> 00:43:05.990 align:start position:0% then it<00:43:03.839> sometimes<00:43:04.260> locks<00:43:04.920> things<00:43:05.099> like<00:43:05.460> this<00:43:05.700> like 00:43:05.990 --> 00:43:06.000 align:start position:0% it sometimes locks things like this like 00:43:06.000 --> 00:43:08.630 align:start position:0% it sometimes locks things like this like you<00:43:06.900> know<00:43:06.960> you<00:43:07.500> have<00:43:07.619> to<00:43:07.740> be<00:43:07.859> familiar<00:43:08.339> with 00:43:08.630 --> 00:43:08.640 align:start position:0% you know you have to be familiar with 00:43:08.640 --> 00:43:10.309 align:start position:0% you know you have to be familiar with these<00:43:08.880> things<00:43:09.000> I<00:43:09.300> can<00:43:09.420> show<00:43:09.599> you<00:43:09.720> how<00:43:09.960> it<00:43:10.079> looks 00:43:10.309 --> 00:43:10.319 align:start position:0% these things I can show you how it looks 00:43:10.319 --> 00:43:12.589 align:start position:0% these things I can show you how it looks like<00:43:10.440> from<00:43:10.680> the<00:43:10.859> beginning<00:43:11.040> so<00:43:11.880> you<00:43:12.180> start<00:43:12.420> it 00:43:12.589 --> 00:43:12.599 align:start position:0% like from the beginning so you start it 00:43:12.599 --> 00:43:16.730 align:start position:0% like from the beginning so you start it it<00:43:12.839> prints<00:43:13.200> this<00:43:13.319> B<00:43:13.619> and<00:43:14.520> then<00:43:14.760> some<00:43:15.660> things<00:43:16.380> it 00:43:16.730 --> 00:43:16.740 align:start position:0% it prints this B and then some things it 00:43:16.740 --> 00:43:19.010 align:start position:0% it prints this B and then some things it prints<00:43:17.099> out<00:43:17.280> some<00:43:17.700> public<00:43:18.359> keys<00:43:18.900> and 00:43:19.010 --> 00:43:19.020 align:start position:0% prints out some public keys and 00:43:19.020 --> 00:43:23.349 align:start position:0% prints out some public keys and addresses<00:43:19.619> version<00:43:20.180> the<00:43:21.180> chain<00:43:21.420> backend<00:43:22.160> and 00:43:23.349 --> 00:43:23.359 align:start position:0% addresses version the chain backend and 00:43:23.359 --> 00:43:26.870 align:start position:0% addresses version the chain backend and overlay<00:43:24.359> address<00:43:24.540> so<00:43:24.839> there<00:43:25.079> is<00:43:25.200> it<00:43:25.859> uses<00:43:26.220> a<00:43:26.520> a 00:43:26.870 --> 00:43:26.880 align:start position:0% overlay address so there is it uses a a 00:43:26.880 --> 00:43:29.530 align:start position:0% overlay address so there is it uses a a different<00:43:27.660> address<00:43:28.020> than<00:43:28.440> your 00:43:29.530 --> 00:43:29.540 align:start position:0% different address than your 00:43:29.540 --> 00:43:32.870 align:start position:0% different address than your than<00:43:30.540> your<00:43:30.720> ethereum<00:43:31.140> address<00:43:31.400> that<00:43:32.400> it<00:43:32.520> uses 00:43:32.870 --> 00:43:32.880 align:start position:0% than your ethereum address that it uses 00:43:32.880 --> 00:43:35.210 align:start position:0% than your ethereum address that it uses so<00:43:33.300> that<00:43:33.540> basically 00:43:35.210 --> 00:43:35.220 align:start position:0% so that basically 00:43:35.220 --> 00:43:37.910 align:start position:0% so that basically something<00:43:35.940> that<00:43:36.300> is<00:43:36.480> it's<00:43:36.720> a<00:43:36.960> bit<00:43:37.079> harder<00:43:37.560> to 00:43:37.910 --> 00:43:37.920 align:start position:0% something that is it's a bit harder to 00:43:37.920 --> 00:43:42.230 align:start position:0% something that is it's a bit harder to just<00:43:38.640> you<00:43:38.880> know<00:43:39.000> run<00:43:39.560> a<00:43:40.560> lot<00:43:40.859> of<00:43:40.980> random<00:43:41.460> nodes 00:43:42.230 --> 00:43:42.240 align:start position:0% just you know run a lot of random nodes 00:43:42.240 --> 00:43:44.690 align:start position:0% just you know run a lot of random nodes and<00:43:42.660> then<00:43:42.839> this<00:43:43.079> overly<00:43:43.500> address<00:43:43.800> provides 00:43:44.690 --> 00:43:44.700 align:start position:0% and then this overly address provides 00:43:44.700 --> 00:43:46.730 align:start position:0% and then this overly address provides some<00:43:44.940> kind<00:43:45.060> of<00:43:45.180> protection<00:43:45.599> against<00:43:46.020> running 00:43:46.730 --> 00:43:46.740 align:start position:0% some kind of protection against running 00:43:46.740 --> 00:43:49.130 align:start position:0% some kind of protection against running a<00:43:47.040> lot<00:43:47.160> of<00:43:47.280> nodes<00:43:47.520> and<00:43:47.760> trying<00:43:48.060> to<00:43:48.420> take<00:43:48.900> over 00:43:49.130 --> 00:43:49.140 align:start position:0% a lot of nodes and trying to take over 00:43:49.140 --> 00:43:51.470 align:start position:0% a lot of nodes and trying to take over some<00:43:49.680> part<00:43:49.920> of<00:43:50.099> the<00:43:50.280> network 00:43:51.470 --> 00:43:51.480 align:start position:0% some part of the network 00:43:51.480 --> 00:43:53.690 align:start position:0% some part of the network so 00:43:53.690 --> 00:43:53.700 align:start position:0% so 00:43:53.700 --> 00:43:56.750 align:start position:0% so yeah<00:43:54.000> and<00:43:54.839> then<00:43:54.960> at<00:43:55.319> this<00:43:55.500> point<00:43:55.740> we<00:43:56.339> have<00:43:56.520> a 00:43:56.750 --> 00:43:56.760 align:start position:0% yeah and then at this point we have a 00:43:56.760 --> 00:43:59.450 align:start position:0% yeah and then at this point we have a full<00:43:56.940> node<00:43:57.300> running<00:43:57.740> and<00:43:58.740> maybe<00:43:58.980> if<00:43:59.280> the 00:43:59.450 --> 00:43:59.460 align:start position:0% full node running and maybe if the 00:43:59.460 --> 00:44:00.970 align:start position:0% full node running and maybe if the network<00:43:59.579> is<00:44:00.000> working 00:44:00.970 --> 00:44:00.980 align:start position:0% network is working 00:44:00.980 --> 00:44:03.829 align:start position:0% network is working maybe<00:44:01.980> we<00:44:02.280> can<00:44:02.460> even<00:44:02.579> try<00:44:02.880> to 00:44:03.829 --> 00:44:03.839 align:start position:0% maybe we can even try to 00:44:03.839 --> 00:44:07.250 align:start position:0% maybe we can even try to uh<00:44:04.800> okay<00:44:05.099> close<00:44:05.700> oh<00:44:06.240> no<00:44:06.420> sorry 00:44:07.250 --> 00:44:07.260 align:start position:0% uh okay close oh no sorry 00:44:07.260 --> 00:44:09.290 align:start position:0% uh okay close oh no sorry here 00:44:09.290 --> 00:44:09.300 align:start position:0% here 00:44:09.300 --> 00:44:11.809 align:start position:0% here I<00:44:09.780> closed<00:44:10.260> it<00:44:10.380> all<00:44:10.740> right<00:44:10.859> I<00:44:11.280> don't<00:44:11.400> no<00:44:11.579> longer 00:44:11.809 --> 00:44:11.819 align:start position:0% I closed it all right I don't no longer 00:44:11.819 --> 00:44:13.970 align:start position:0% I closed it all right I don't no longer have<00:44:12.060> the<00:44:12.359> the<00:44:12.480> hash<00:44:12.960> that<00:44:13.260> I<00:44:13.440> uploaded 00:44:13.970 --> 00:44:13.980 align:start position:0% have the the hash that I uploaded 00:44:13.980 --> 00:44:15.849 align:start position:0% have the the hash that I uploaded previously<00:44:14.400> I<00:44:14.700> just<00:44:14.819> wanted<00:44:15.000> to<00:44:15.300> try<00:44:15.480> maybe 00:44:15.849 --> 00:44:15.859 align:start position:0% previously I just wanted to try maybe 00:44:15.859 --> 00:44:18.589 align:start position:0% previously I just wanted to try maybe it's<00:44:16.859> downloads<00:44:17.460> so<00:44:17.700> the<00:44:17.880> the<00:44:18.000> thing<00:44:18.240> is<00:44:18.359> that 00:44:18.589 --> 00:44:18.599 align:start position:0% it's downloads so the the thing is that 00:44:18.599 --> 00:44:20.750 align:start position:0% it's downloads so the the thing is that now<00:44:18.839> it's<00:44:19.020> if<00:44:19.319> you<00:44:19.560> start<00:44:19.740> a<00:44:19.980> full<00:44:20.160> note<00:44:20.400> from 00:44:20.750 --> 00:44:20.760 align:start position:0% now it's if you start a full note from 00:44:20.760 --> 00:44:23.030 align:start position:0% now it's if you start a full note from scratch<00:44:21.060> it<00:44:21.839> at<00:44:22.079> the<00:44:22.200> beginning<00:44:22.380> it<00:44:22.859> will 00:44:23.030 --> 00:44:23.040 align:start position:0% scratch it at the beginning it will 00:44:23.040 --> 00:44:25.910 align:start position:0% scratch it at the beginning it will start<00:44:23.400> synchronizing<00:44:24.240> data<00:44:24.780> so<00:44:25.020> the<00:44:25.740> current 00:44:25.910 --> 00:44:25.920 align:start position:0% start synchronizing data so the current 00:44:25.920 --> 00:44:28.790 align:start position:0% start synchronizing data so the current full<00:44:26.579> node<00:44:26.880> capacity<00:44:27.359> is<00:44:27.540> around<00:44:27.800> 20 00:44:28.790 --> 00:44:28.800 align:start position:0% full node capacity is around 20 00:44:28.800 --> 00:44:31.670 align:start position:0% full node capacity is around 20 Gigabytes<00:44:29.579> but<00:44:30.300> it<00:44:30.480> also<00:44:30.839> has<00:44:30.960> some<00:44:31.200> caching 00:44:31.670 --> 00:44:31.680 align:start position:0% Gigabytes but it also has some caching 00:44:31.680 --> 00:44:35.329 align:start position:0% Gigabytes but it also has some caching and<00:44:32.099> some<00:44:32.400> other<00:44:32.640> overhead<00:44:33.440> so<00:44:34.440> it<00:44:34.800> uses<00:44:35.099> more 00:44:35.329 --> 00:44:35.339 align:start position:0% and some other overhead so it uses more 00:44:35.339 --> 00:44:36.770 align:start position:0% and some other overhead so it uses more data<00:44:35.760> than<00:44:35.940> that 00:44:36.770 --> 00:44:36.780 align:start position:0% data than that 00:44:36.780 --> 00:44:40.130 align:start position:0% data than that but<00:44:37.560> it<00:44:38.040> tries<00:44:38.339> to<00:44:38.700> like<00:44:39.119> synchronize<00:44:39.720> 20 00:44:40.130 --> 00:44:40.140 align:start position:0% but it tries to like synchronize 20 00:44:40.140 --> 00:44:44.030 align:start position:0% but it tries to like synchronize 20 Gigabytes<00:44:40.920> of<00:44:41.220> of<00:44:41.640> data<00:44:42.240> and<00:44:42.720> that<00:44:43.020> is<00:44:43.200> one<00:44:43.680> B 00:44:44.030 --> 00:44:44.040 align:start position:0% Gigabytes of of data and that is one B 00:44:44.040 --> 00:44:45.829 align:start position:0% Gigabytes of of data and that is one B nodes<00:44:44.400> capacity<00:44:44.880> this<00:44:45.119> is<00:44:45.240> something<00:44:45.420> that<00:44:45.720> we 00:44:45.829 --> 00:44:45.839 align:start position:0% nodes capacity this is something that we 00:44:45.839 --> 00:44:47.690 align:start position:0% nodes capacity this is something that we consider<00:44:46.200> increasing<00:44:46.800> in<00:44:46.980> the<00:44:47.099> future<00:44:47.220> but 00:44:47.690 --> 00:44:47.700 align:start position:0% consider increasing in the future but 00:44:47.700 --> 00:44:51.349 align:start position:0% consider increasing in the future but for<00:44:48.300> now<00:44:48.480> it's<00:44:48.839> like<00:44:49.140> seems<00:44:50.040> a<00:44:50.099> reasonable<00:44:50.520> uh 00:44:51.349 --> 00:44:51.359 align:start position:0% for now it's like seems a reasonable uh 00:44:51.359 --> 00:44:54.530 align:start position:0% for now it's like seems a reasonable uh default<00:44:51.800> and<00:44:52.800> then<00:44:52.980> basically<00:44:53.700> when<00:44:54.359> you 00:44:54.530 --> 00:44:54.540 align:start position:0% default and then basically when you 00:44:54.540 --> 00:44:56.630 align:start position:0% default and then basically when you start<00:44:54.720> an<00:44:54.960> empty<00:44:55.260> node<00:44:55.500> then<00:44:55.740> it<00:44:55.980> will<00:44:56.099> try<00:44:56.339> to 00:44:56.630 --> 00:44:56.640 align:start position:0% start an empty node then it will try to 00:44:56.640 --> 00:44:59.109 align:start position:0% start an empty node then it will try to fetch<00:44:57.119> as<00:44:57.540> much<00:44:57.720> as<00:44:57.960> it<00:44:58.260> fills<00:44:58.619> up<00:44:58.740> this 00:44:59.109 --> 00:44:59.119 align:start position:0% fetch as much as it fills up this 00:44:59.119 --> 00:45:03.650 align:start position:0% fetch as much as it fills up this internal<00:45:00.119> uh<00:45:00.900> storage<00:45:01.140> space<00:45:01.500> and<00:45:02.280> so<00:45:02.520> that<00:45:02.760> if 00:45:03.650 --> 00:45:03.660 align:start position:0% internal uh storage space and so that if 00:45:03.660 --> 00:45:06.530 align:start position:0% internal uh storage space and so that if serve<00:45:04.440> other<00:45:04.680> notes<00:45:05.579> from<00:45:05.760> that<00:45:05.940> so<00:45:06.240> it<00:45:06.359> may 00:45:06.530 --> 00:45:06.540 align:start position:0% serve other notes from that so it may 00:45:06.540 --> 00:45:09.349 align:start position:0% serve other notes from that so it may happen<00:45:06.720> that<00:45:07.079> if<00:45:07.380> you<00:45:07.500> run<00:45:07.740> a<00:45:08.040> full<00:45:08.160> node<00:45:08.579> then 00:45:09.349 --> 00:45:09.359 align:start position:0% happen that if you run a full node then 00:45:09.359 --> 00:45:12.230 align:start position:0% happen that if you run a full node then it<00:45:09.780> might<00:45:09.960> not<00:45:10.200> be<00:45:10.560> uh<00:45:11.280> it<00:45:11.579> might<00:45:11.700> not<00:45:11.819> be<00:45:12.000> able 00:45:12.230 --> 00:45:12.240 align:start position:0% it might not be uh it might not be able 00:45:12.240 --> 00:45:13.550 align:start position:0% it might not be uh it might not be able to 00:45:13.550 --> 00:45:13.560 align:start position:0% to 00:45:13.560 --> 00:45:16.250 align:start position:0% to um<00:45:14.040> or<00:45:14.460> it<00:45:14.700> may<00:45:14.819> slow<00:45:15.119> down<00:45:15.359> your<00:45:15.599> computer<00:45:15.839> at 00:45:16.250 --> 00:45:16.260 align:start position:0% um or it may slow down your computer at 00:45:16.260 --> 00:45:18.589 align:start position:0% um or it may slow down your computer at the<00:45:16.380> beginning<00:45:16.500> or<00:45:17.160> or<00:45:17.700> you<00:45:18.060> know<00:45:18.180> it<00:45:18.359> might 00:45:18.589 --> 00:45:18.599 align:start position:0% the beginning or or you know it might 00:45:18.599 --> 00:45:21.650 align:start position:0% the beginning or or you know it might not<00:45:18.720> be<00:45:18.900> able<00:45:19.079> to<00:45:19.200> access<00:45:19.500> all<00:45:20.400> the<00:45:20.579> data 00:45:21.650 --> 00:45:21.660 align:start position:0% not be able to access all the data 00:45:21.660 --> 00:45:25.430 align:start position:0% not be able to access all the data immediately<00:45:22.819> uh<00:45:23.819> interestingly<00:45:24.720> if<00:45:25.020> you<00:45:25.200> run 00:45:25.430 --> 00:45:25.440 align:start position:0% immediately uh interestingly if you run 00:45:25.440 --> 00:45:28.250 align:start position:0% immediately uh interestingly if you run a<00:45:25.740> light<00:45:26.099> node<00:45:26.460> that<00:45:27.180> is<00:45:27.420> not<00:45:27.599> doing<00:45:27.839> any<00:45:28.079> kind 00:45:28.250 --> 00:45:28.260 align:start position:0% a light node that is not doing any kind 00:45:28.260 --> 00:45:30.829 align:start position:0% a light node that is not doing any kind of<00:45:28.380> synchronization<00:45:28.980> it<00:45:29.460> just<00:45:29.760> asks<00:45:30.359> the<00:45:30.540> data 00:45:30.829 --> 00:45:30.839 align:start position:0% of synchronization it just asks the data 00:45:30.839 --> 00:45:34.550 align:start position:0% of synchronization it just asks the data from<00:45:31.079> other<00:45:31.260> peers<00:45:31.800> and<00:45:32.640> then<00:45:32.880> it<00:45:33.420> works<00:45:33.839> as 00:45:34.550 --> 00:45:34.560 align:start position:0% from other peers and then it works as 00:45:34.560 --> 00:45:37.370 align:start position:0% from other peers and then it works as long<00:45:34.740> as<00:45:34.920> soon<00:45:35.400> as<00:45:35.520> you<00:45:35.700> you<00:45:35.940> install<00:45:36.180> it<00:45:36.540> so<00:45:36.900> it 00:45:37.370 --> 00:45:37.380 align:start position:0% long as soon as you you install it so it 00:45:37.380 --> 00:45:38.750 align:start position:0% long as soon as you you install it so it does<00:45:37.560> not<00:45:37.680> have<00:45:37.920> this<00:45:38.160> synchronization 00:45:38.750 --> 00:45:38.760 align:start position:0% does not have this synchronization 00:45:38.760 --> 00:45:41.450 align:start position:0% does not have this synchronization period<00:45:39.300> like<00:45:39.540> if<00:45:39.780> you<00:45:39.900> use<00:45:40.020> ipfs<00:45:40.920> and<00:45:41.220> install 00:45:41.450 --> 00:45:41.460 align:start position:0% period like if you use ipfs and install 00:45:41.460 --> 00:45:43.970 align:start position:0% period like if you use ipfs and install that<00:45:41.819> you<00:45:42.359> know<00:45:42.480> that<00:45:42.720> it<00:45:42.900> also<00:45:43.200> helps<00:45:43.560> to<00:45:43.740> wait 00:45:43.970 --> 00:45:43.980 align:start position:0% that you know that it also helps to wait 00:45:43.980 --> 00:45:46.370 align:start position:0% that you know that it also helps to wait you<00:45:44.280> have<00:45:44.339> to<00:45:44.520> wait<00:45:44.640> a<00:45:44.880> few<00:45:45.060> minutes<00:45:45.300> until<00:45:46.079> it 00:45:46.370 --> 00:45:46.380 align:start position:0% you have to wait a few minutes until it 00:45:46.380 --> 00:45:49.010 align:start position:0% you have to wait a few minutes until it becomes<00:45:46.800> usable<00:45:47.160> this<00:45:47.819> is<00:45:47.940> not<00:45:48.119> the<00:45:48.359> case<00:45:48.540> with 00:45:49.010 --> 00:45:49.020 align:start position:0% becomes usable this is not the case with 00:45:49.020 --> 00:45:51.650 align:start position:0% becomes usable this is not the case with the<00:45:49.200> Swarm<00:45:49.740> light<00:45:49.980> node<00:45:50.400> but<00:45:51.060> this<00:45:51.240> is<00:45:51.359> also 00:45:51.650 --> 00:45:51.660 align:start position:0% the Swarm light node but this is also 00:45:51.660 --> 00:45:53.690 align:start position:0% the Swarm light node but this is also the<00:45:51.780> case<00:45:51.960> with<00:45:52.200> the<00:45:52.380> Swarm<00:45:52.740> phone 00:45:53.690 --> 00:45:53.700 align:start position:0% the case with the Swarm phone 00:45:53.700 --> 00:45:55.670 align:start position:0% the case with the Swarm phone and<00:45:54.480> so 00:45:55.670 --> 00:45:55.680 align:start position:0% and so 00:45:55.680 --> 00:46:00.890 align:start position:0% and so like<00:45:56.400> this<00:45:56.760> is<00:45:56.880> how<00:45:57.420> you<00:45:57.720> can<00:45:57.780> set<00:45:57.960> it<00:45:58.200> up<00:45:58.319> so 00:46:00.890 --> 00:46:00.900 align:start position:0% like this is how you can set it up so 00:46:00.900 --> 00:46:05.450 align:start position:0% like this is how you can set it up so um<00:46:00.960> maybe<00:46:02.240> yeah<00:46:03.240> we<00:46:03.420> have<00:46:03.599> like<00:46:03.960> two<00:46:04.980> um<00:46:04.980> 12 00:46:05.450 --> 00:46:05.460 align:start position:0% um maybe yeah we have like two um 12 00:46:05.460 --> 00:46:07.970 align:start position:0% um maybe yeah we have like two um 12 minutes<00:46:05.700> left<00:46:06.000> so<00:46:06.660> maybe<00:46:06.839> I<00:46:07.140> can<00:46:07.319> just<00:46:07.500> I<00:46:07.800> will 00:46:07.970 --> 00:46:07.980 align:start position:0% minutes left so maybe I can just I will 00:46:07.980 --> 00:46:10.490 align:start position:0% minutes left so maybe I can just I will just<00:46:08.160> talk<00:46:08.339> a<00:46:08.579> bit<00:46:08.760> more<00:46:09.180> about<00:46:09.480> like<00:46:09.960> the<00:46:10.319> the 00:46:10.490 --> 00:46:10.500 align:start position:0% just talk a bit more about like the the 00:46:10.500 --> 00:46:13.970 align:start position:0% just talk a bit more about like the the storage<00:46:10.740> incentives<00:46:11.460> part<00:46:12.079> uh<00:46:13.079> where<00:46:13.619> it<00:46:13.859> is 00:46:13.970 --> 00:46:13.980 align:start position:0% storage incentives part uh where it is 00:46:13.980 --> 00:46:16.010 align:start position:0% storage incentives part uh where it is currently<00:46:14.460> so 00:46:16.010 --> 00:46:16.020 align:start position:0% currently so 00:46:16.020 --> 00:46:19.730 align:start position:0% currently so yeah<00:46:16.619> the<00:46:16.920> there<00:46:17.460> is<00:46:17.720> currently<00:46:18.720> a<00:46:19.079> test<00:46:19.440> nut 00:46:19.730 --> 00:46:19.740 align:start position:0% yeah the there is currently a test nut 00:46:19.740 --> 00:46:21.770 align:start position:0% yeah the there is currently a test nut and<00:46:20.160> the<00:46:20.280> main<00:46:20.400> nut<00:46:20.700> for<00:46:21.000> the<00:46:21.180> Swarm<00:46:21.599> Network 00:46:21.770 --> 00:46:21.780 align:start position:0% and the main nut for the Swarm Network 00:46:21.780 --> 00:46:24.770 align:start position:0% and the main nut for the Swarm Network and<00:46:22.740> the<00:46:22.920> test<00:46:23.040> net<00:46:23.280> is<00:46:23.579> used<00:46:23.819> is<00:46:24.119> the<00:46:24.480> the 00:46:24.770 --> 00:46:24.780 align:start position:0% and the test net is used is the the 00:46:24.780 --> 00:46:26.930 align:start position:0% and the test net is used is the the girly<00:46:25.260> blockchain 00:46:26.930 --> 00:46:26.940 align:start position:0% girly blockchain 00:46:26.940 --> 00:46:29.510 align:start position:0% girly blockchain and<00:46:27.720> then<00:46:27.900> in<00:46:28.260> order<00:46:28.380> to<00:46:28.560> participate<00:46:29.280> in 00:46:29.510 --> 00:46:29.520 align:start position:0% and then in order to participate in 00:46:29.520 --> 00:46:31.730 align:start position:0% and then in order to participate in testing<00:46:29.940> you<00:46:30.599> will<00:46:30.780> need<00:46:31.079> some<00:46:31.380> girly 00:46:31.730 --> 00:46:31.740 align:start position:0% testing you will need some girly 00:46:31.740 --> 00:46:34.849 align:start position:0% testing you will need some girly businessy<00:46:32.400> we<00:46:33.119> can<00:46:33.359> provide<00:46:33.780> that<00:46:34.140> if<00:46:34.680> you 00:46:34.849 --> 00:46:34.859 align:start position:0% businessy we can provide that if you 00:46:34.859 --> 00:46:37.250 align:start position:0% businessy we can provide that if you need<00:46:35.040> if<00:46:35.339> you<00:46:35.460> want<00:46:35.640> to<00:46:35.760> try<00:46:36.060> out<00:46:36.300> in<00:46:37.079> the 00:46:37.250 --> 00:46:37.260 align:start position:0% need if you want to try out in the 00:46:37.260 --> 00:46:39.650 align:start position:0% need if you want to try out in the Discord<00:46:37.680> we<00:46:38.460> have<00:46:38.640> a<00:46:38.760> Discord<00:46:39.000> channel<00:46:39.240> so<00:46:39.480> if 00:46:39.650 --> 00:46:39.660 align:start position:0% Discord we have a Discord channel so if 00:46:39.660 --> 00:46:41.690 align:start position:0% Discord we have a Discord channel so if you<00:46:39.780> join<00:46:40.079> there<00:46:40.260> and<00:46:40.380> if<00:46:40.560> you<00:46:40.740> ask<00:46:40.920> my<00:46:41.160> mom<00:46:41.520> to 00:46:41.690 --> 00:46:41.700 align:start position:0% you join there and if you ask my mom to 00:46:41.700 --> 00:46:43.430 align:start position:0% you join there and if you ask my mom to participate<00:46:42.119> in<00:46:42.300> testing<00:46:42.660> then<00:46:42.900> we<00:46:43.140> can<00:46:43.260> give 00:46:43.430 --> 00:46:43.440 align:start position:0% participate in testing then we can give 00:46:43.440 --> 00:46:46.150 align:start position:0% participate in testing then we can give you<00:46:43.619> girly<00:46:44.280> BCC<00:46:44.640> for<00:46:45.000> trying<00:46:45.180> it<00:46:45.420> out 00:46:46.150 --> 00:46:46.160 align:start position:0% you girly BCC for trying it out 00:46:46.160 --> 00:46:49.069 align:start position:0% you girly BCC for trying it out these<00:46:47.160> codes<00:46:47.280> are<00:46:47.940> like<00:46:48.119> actually<00:46:48.359> like<00:46:48.780> if 00:46:49.069 --> 00:46:49.079 align:start position:0% these codes are like actually like if 00:46:49.079 --> 00:46:51.829 align:start position:0% these codes are like actually like if you<00:46:49.260> want<00:46:49.440> to<00:46:49.619> a<00:46:50.339> private<00:46:50.700> key<00:46:50.880> so<00:46:51.300> like<00:46:51.540> if<00:46:51.720> you 00:46:51.829 --> 00:46:51.839 align:start position:0% you want to a private key so like if you 00:46:51.839 --> 00:46:53.809 align:start position:0% you want to a private key so like if you want<00:46:52.020> to<00:46:52.140> try<00:46:52.319> it<00:46:52.500> on<00:46:52.619> minute<00:46:52.859> you<00:46:53.339> can<00:46:53.400> also<00:46:53.640> do 00:46:53.809 --> 00:46:53.819 align:start position:0% want to try it on minute you can also do 00:46:53.819 --> 00:46:56.630 align:start position:0% want to try it on minute you can also do and<00:46:54.060> then<00:46:54.300> you<00:46:54.540> can<00:46:54.660> use<00:46:54.839> these<00:46:55.260> codes<00:46:55.619> as<00:46:55.980> a<00:46:56.280> as 00:46:56.630 --> 00:46:56.640 align:start position:0% and then you can use these codes as a as 00:46:56.640 --> 00:46:59.510 align:start position:0% and then you can use these codes as a as a<00:46:56.880> wallet<00:46:57.260> private<00:46:58.260> key<00:46:58.440> and<00:46:58.800> then<00:46:58.980> from<00:46:59.339> that 00:46:59.510 --> 00:46:59.520 align:start position:0% a wallet private key and then from that 00:46:59.520 --> 00:47:01.490 align:start position:0% a wallet private key and then from that you<00:46:59.760> can<00:46:59.880> figure<00:47:00.119> out<00:47:00.420> the<00:47:01.020> rest<00:47:01.200> you<00:47:01.380> can 00:47:01.490 --> 00:47:01.500 align:start position:0% you can figure out the rest you can 00:47:01.500 --> 00:47:03.829 align:start position:0% you can figure out the rest you can import<00:47:01.680> it<00:47:01.920> to<00:47:02.099> metamask<00:47:02.640> and<00:47:02.940> then<00:47:03.119> transfer 00:47:03.829 --> 00:47:03.839 align:start position:0% import it to metamask and then transfer 00:47:03.839 --> 00:47:06.770 align:start position:0% import it to metamask and then transfer the<00:47:03.960> money<00:47:04.140> to<00:47:04.380> that<00:47:04.560> and<00:47:05.460> so<00:47:05.819> what's<00:47:06.480> maybe 00:47:06.770 --> 00:47:06.780 align:start position:0% the money to that and so what's maybe 00:47:06.780 --> 00:47:08.450 align:start position:0% the money to that and so what's maybe interesting<00:47:07.260> is<00:47:07.500> like<00:47:07.740> the<00:47:08.040> current<00:47:08.160> status 00:47:08.450 --> 00:47:08.460 align:start position:0% interesting is like the current status 00:47:08.460 --> 00:47:10.849 align:start position:0% interesting is like the current status of<00:47:08.819> the<00:47:09.000> project<00:47:09.180> and<00:47:09.780> where<00:47:10.200> what<00:47:10.560> are<00:47:10.740> the 00:47:10.849 --> 00:47:10.859 align:start position:0% of the project and where what are the 00:47:10.859 --> 00:47:13.790 align:start position:0% of the project and where what are the next<00:47:11.040> plans<00:47:11.400> so<00:47:11.780> uh<00:47:12.780> currently<00:47:13.260> the<00:47:13.619> the 00:47:13.790 --> 00:47:13.800 align:start position:0% next plans so uh currently the the 00:47:13.800 --> 00:47:15.650 align:start position:0% next plans so uh currently the the storage<00:47:13.980> incentives<00:47:14.700> are<00:47:14.940> on<00:47:15.060> the<00:47:15.240> test<00:47:15.420> nut 00:47:15.650 --> 00:47:15.660 align:start position:0% storage incentives are on the test nut 00:47:15.660 --> 00:47:17.930 align:start position:0% storage incentives are on the test nut so<00:47:16.319> that<00:47:16.500> means<00:47:16.800> that<00:47:16.980> we<00:47:17.160> are<00:47:17.339> testing<00:47:17.700> out 00:47:17.930 --> 00:47:17.940 align:start position:0% so that means that we are testing out 00:47:17.940 --> 00:47:19.670 align:start position:0% so that means that we are testing out this<00:47:18.480> functionality<00:47:19.260> it's<00:47:19.380> quite 00:47:19.670 --> 00:47:19.680 align:start position:0% this functionality it's quite 00:47:19.680 --> 00:47:21.650 align:start position:0% this functionality it's quite interesting<00:47:20.160> actually<00:47:20.520> and<00:47:20.880> I<00:47:21.180> suggest<00:47:21.480> you 00:47:21.650 --> 00:47:21.660 align:start position:0% interesting actually and I suggest you 00:47:21.660 --> 00:47:24.290 align:start position:0% interesting actually and I suggest you to<00:47:21.839> read<00:47:22.079> about<00:47:22.260> it<00:47:22.560> that<00:47:23.460> basically<00:47:23.819> there<00:47:24.119> is 00:47:24.290 --> 00:47:24.300 align:start position:0% to read about it that basically there is 00:47:24.300 --> 00:47:28.430 align:start position:0% to read about it that basically there is a<00:47:24.660> a<00:47:25.319> lottery<00:47:25.920> game<00:47:26.400> kind<00:47:26.880> of<00:47:27.060> thing<00:47:27.240> that 00:47:28.430 --> 00:47:28.440 align:start position:0% a a lottery game kind of thing that 00:47:28.440 --> 00:47:31.790 align:start position:0% a a lottery game kind of thing that so<00:47:28.980> the<00:47:29.220> nodes<00:47:29.460> that<00:47:30.060> have<00:47:30.720> like<00:47:31.140> the<00:47:31.560> the 00:47:31.790 --> 00:47:31.800 align:start position:0% so the nodes that have like the the 00:47:31.800 --> 00:47:33.770 align:start position:0% so the nodes that have like the the chair<00:47:32.040> the<00:47:32.460> same<00:47:32.579> partition<00:47:33.060> of<00:47:33.359> the<00:47:33.540> network 00:47:33.770 --> 00:47:33.780 align:start position:0% chair the same partition of the network 00:47:33.780 --> 00:47:37.430 align:start position:0% chair the same partition of the network they<00:47:34.680> collaborate<00:47:35.220> on<00:47:36.000> the<00:47:36.300> blockchain<00:47:36.720> in<00:47:37.319> a 00:47:37.430 --> 00:47:37.440 align:start position:0% they collaborate on the blockchain in a 00:47:37.440 --> 00:47:40.130 align:start position:0% they collaborate on the blockchain in a in<00:47:37.680> a<00:47:37.859> game<00:47:38.040> that<00:47:38.400> like<00:47:38.579> they<00:47:38.880> have<00:47:39.060> to<00:47:39.420> uh 00:47:40.130 --> 00:47:40.140 align:start position:0% in a game that like they have to uh 00:47:40.140 --> 00:47:43.849 align:start position:0% in a game that like they have to uh commit<00:47:40.579> the<00:47:41.579> approve<00:47:42.359> of<00:47:42.900> the<00:47:43.140> data<00:47:43.440> that<00:47:43.680> they 00:47:43.849 --> 00:47:43.859 align:start position:0% commit the approve of the data that they 00:47:43.859 --> 00:47:46.910 align:start position:0% commit the approve of the data that they are<00:47:44.040> storing<00:47:44.460> and<00:47:45.060> they<00:47:45.240> have<00:47:45.480> to<00:47:45.900> create<00:47:46.619> the 00:47:46.910 --> 00:47:46.920 align:start position:0% are storing and they have to create the 00:47:46.920 --> 00:47:49.190 align:start position:0% are storing and they have to create the consensus<00:47:47.460> on<00:47:47.700> that<00:47:47.880> and<00:47:48.119> then<00:47:48.359> based<00:47:48.900> on<00:47:48.960> that 00:47:49.190 --> 00:47:49.200 align:start position:0% consensus on that and then based on that 00:47:49.200 --> 00:47:53.150 align:start position:0% consensus on that and then based on that they<00:47:49.980> select<00:47:50.460> a<00:47:50.700> winner<00:47:50.940> that<00:47:51.780> takes<00:47:52.020> the<00:47:52.980> the 00:47:53.150 --> 00:47:53.160 align:start position:0% they select a winner that takes the the 00:47:53.160 --> 00:47:56.030 align:start position:0% they select a winner that takes the the Pod<00:47:53.460> but<00:47:53.720> over<00:47:54.720> time<00:47:55.020> it's<00:47:55.380> statistically 00:47:56.030 --> 00:47:56.040 align:start position:0% Pod but over time it's statistically 00:47:56.040 --> 00:47:59.089 align:start position:0% Pod but over time it's statistically everyone<00:47:56.400> can<00:47:56.880> win<00:47:57.240> and<00:47:57.540> that's<00:47:57.839> how<00:47:58.140> the<00:47:58.920> the 00:47:59.089 --> 00:47:59.099 align:start position:0% everyone can win and that's how the the 00:47:59.099 --> 00:48:01.730 align:start position:0% everyone can win and that's how the the the<00:47:59.280> the<00:47:59.460> the<00:48:00.020> distribution<00:48:01.020> the 00:48:01.730 --> 00:48:01.740 align:start position:0% the the the distribution the 00:48:01.740 --> 00:48:05.089 align:start position:0% the the the distribution the redistribution<00:48:02.339> of<00:48:02.640> the<00:48:02.880> funds<00:48:03.300> are<00:48:03.960> solved 00:48:05.089 --> 00:48:05.099 align:start position:0% redistribution of the funds are solved 00:48:05.099 --> 00:48:08.089 align:start position:0% redistribution of the funds are solved and<00:48:06.060> uh<00:48:06.540> yeah<00:48:07.020> this<00:48:07.319> happens<00:48:07.440> through<00:48:07.859> smart 00:48:08.089 --> 00:48:08.099 align:start position:0% and uh yeah this happens through smart 00:48:08.099 --> 00:48:11.329 align:start position:0% and uh yeah this happens through smart contracts<00:48:08.700> so<00:48:09.000> we<00:48:09.300> will<00:48:09.540> post 00:48:11.329 --> 00:48:11.339 align:start position:0% contracts so we will post 00:48:11.339 --> 00:48:13.490 align:start position:0% contracts so we will post um<00:48:11.400> a<00:48:11.940> lot<00:48:12.060> about<00:48:12.240> this<00:48:12.599> because<00:48:12.900> this<00:48:13.260> is<00:48:13.380> our 00:48:13.490 --> 00:48:13.500 align:start position:0% um a lot about this because this is our 00:48:13.500 --> 00:48:17.030 align:start position:0% um a lot about this because this is our current<00:48:13.800> Focus<00:48:14.640> area<00:48:14.940> that<00:48:15.839> we<00:48:15.960> want<00:48:16.140> to<00:48:16.319> get 00:48:17.030 --> 00:48:17.040 align:start position:0% current Focus area that we want to get 00:48:17.040 --> 00:48:20.030 align:start position:0% current Focus area that we want to get done<00:48:17.400> and<00:48:18.359> once<00:48:18.720> that's<00:48:18.839> working<00:48:19.140> that<00:48:19.560> we<00:48:19.800> are 00:48:20.030 --> 00:48:20.040 align:start position:0% done and once that's working that we are 00:48:20.040 --> 00:48:23.690 align:start position:0% done and once that's working that we are enable<00:48:20.579> of<00:48:21.300> like<00:48:21.960> that<00:48:22.380> will<00:48:22.619> finally<00:48:23.099> enable 00:48:23.690 --> 00:48:23.700 align:start position:0% enable of like that will finally enable 00:48:23.700 --> 00:48:27.890 align:start position:0% enable of like that will finally enable this<00:48:24.599> uh<00:48:25.380> data<00:48:25.859> economy<00:48:26.460> that<00:48:26.940> I<00:48:27.180> just<00:48:27.420> showed 00:48:27.890 --> 00:48:27.900 align:start position:0% this uh data economy that I just showed 00:48:27.900 --> 00:48:30.950 align:start position:0% this uh data economy that I just showed you<00:48:27.960> previously<00:48:28.740> where<00:48:29.640> like<00:48:30.000> people<00:48:30.599> can 00:48:30.950 --> 00:48:30.960 align:start position:0% you previously where like people can 00:48:30.960 --> 00:48:33.829 align:start position:0% you previously where like people can actually<00:48:31.140> buy<00:48:31.680> capacity<00:48:32.640> on<00:48:33.060> the<00:48:33.180> network<00:48:33.359> and 00:48:33.829 --> 00:48:33.839 align:start position:0% actually buy capacity on the network and 00:48:33.839 --> 00:48:36.829 align:start position:0% actually buy capacity on the network and the<00:48:33.960> node<00:48:34.200> operators<00:48:34.740> are<00:48:35.300> compensated<00:48:36.300> for 00:48:36.829 --> 00:48:36.839 align:start position:0% the node operators are compensated for 00:48:36.839 --> 00:48:40.130 align:start position:0% the node operators are compensated for their<00:48:37.020> efforts<00:48:37.920> and<00:48:38.760> so<00:48:39.060> that's<00:48:39.660> one<00:48:40.020> thing 00:48:40.130 --> 00:48:40.140 align:start position:0% their efforts and so that's one thing 00:48:40.140 --> 00:48:41.870 align:start position:0% their efforts and so that's one thing that<00:48:40.440> is<00:48:40.619> the<00:48:40.800> current<00:48:40.980> effort<00:48:41.400> that<00:48:41.700> we<00:48:41.760> are 00:48:41.870 --> 00:48:41.880 align:start position:0% that is the current effort that we are 00:48:41.880 --> 00:48:44.329 align:start position:0% that is the current effort that we are doing<00:48:42.000> and<00:48:42.359> after<00:48:42.540> that<00:48:42.900> we<00:48:43.319> we<00:48:43.619> will<00:48:43.800> work<00:48:44.099> on 00:48:44.329 --> 00:48:44.339 align:start position:0% doing and after that we we will work on 00:48:44.339 --> 00:48:48.589 align:start position:0% doing and after that we we will work on making<00:48:44.760> the<00:48:45.480> like<00:48:45.900> be<00:48:46.200> more<00:48:46.700> uh<00:48:47.700> stable<00:48:48.180> for 00:48:48.589 --> 00:48:48.599 align:start position:0% making the like be more uh stable for 00:48:48.599 --> 00:48:51.710 align:start position:0% making the like be more uh stable for like<00:48:48.839> handling<00:48:49.319> bigger<00:48:49.859> data<00:48:50.280> sets<00:48:50.640> and<00:48:51.720> um 00:48:51.710 --> 00:48:51.720 align:start position:0% like handling bigger data sets and um 00:48:51.720 --> 00:48:56.089 align:start position:0% like handling bigger data sets and um enabling<00:48:52.619> it<00:48:52.980> for<00:48:53.339> for<00:48:53.780> uh<00:48:54.780> use<00:48:55.200> cases<00:48:55.500> which 00:48:56.089 --> 00:48:56.099 align:start position:0% enabling it for for uh use cases which 00:48:56.099 --> 00:48:58.970 align:start position:0% enabling it for for uh use cases which uses<00:48:56.940> like<00:48:57.300> it<00:48:57.480> requires<00:48:58.079> on<00:48:58.260> bigger<00:48:58.619> data 00:48:58.970 --> 00:48:58.980 align:start position:0% uses like it requires on bigger data 00:48:58.980 --> 00:49:00.710 align:start position:0% uses like it requires on bigger data sets<00:48:59.220> like<00:48:59.339> for<00:48:59.520> example<00:48:59.760> like<00:49:00.060> video<00:49:00.300> and 00:49:00.710 --> 00:49:00.720 align:start position:0% sets like for example like video and 00:49:00.720 --> 00:49:03.950 align:start position:0% sets like for example like video and stuff<00:49:01.020> like<00:49:01.200> that<00:49:01.440> and<00:49:02.359> once<00:49:03.359> that's<00:49:03.480> in<00:49:03.720> place 00:49:03.950 --> 00:49:03.960 align:start position:0% stuff like that and once that's in place 00:49:03.960 --> 00:49:07.430 align:start position:0% stuff like that and once that's in place then<00:49:04.619> there<00:49:05.460> that<00:49:05.819> can<00:49:06.000> open<00:49:06.180> the<00:49:06.599> the 00:49:07.430 --> 00:49:07.440 align:start position:0% then there that can open the the 00:49:07.440 --> 00:49:10.609 align:start position:0% then there that can open the the uh<00:49:08.160> swarm<00:49:08.640> as<00:49:09.000> a<00:49:09.119> application<00:49:09.900> platform<00:49:10.380> for 00:49:10.609 --> 00:49:10.619 align:start position:0% uh swarm as a application platform for 00:49:10.619 --> 00:49:12.710 align:start position:0% uh swarm as a application platform for application<00:49:11.160> and<00:49:11.400> then<00:49:11.760> storing<00:49:12.180> data<00:49:12.599> on 00:49:12.710 --> 00:49:12.720 align:start position:0% application and then storing data on 00:49:12.720 --> 00:49:16.450 align:start position:0% application and then storing data on that<00:49:12.960> and<00:49:13.319> that<00:49:13.619> can<00:49:13.800> generate<00:49:14.339> like<00:49:14.760> the<00:49:15.599> the 00:49:16.450 --> 00:49:16.460 align:start position:0% that and that can generate like the the 00:49:16.460 --> 00:49:19.370 align:start position:0% that and that can generate like the the activities<00:49:17.460> on<00:49:17.819> the<00:49:18.000> network<00:49:18.180> and<00:49:18.960> we<00:49:19.200> are 00:49:19.370 --> 00:49:19.380 align:start position:0% activities on the network and we are 00:49:19.380 --> 00:49:22.550 align:start position:0% activities on the network and we are also<00:49:19.680> going<00:49:19.859> to<00:49:20.160> upload<00:49:20.700> some<00:49:21.240> initial<00:49:22.140> like 00:49:22.550 --> 00:49:22.560 align:start position:0% also going to upload some initial like 00:49:22.560 --> 00:49:24.410 align:start position:0% also going to upload some initial like public<00:49:22.800> good<00:49:23.099> data<00:49:23.579> sets<00:49:23.819> that<00:49:24.000> we<00:49:24.119> talked 00:49:24.410 --> 00:49:24.420 align:start position:0% public good data sets that we talked 00:49:24.420 --> 00:49:26.510 align:start position:0% public good data sets that we talked about<00:49:24.540> like<00:49:25.020> so<00:49:25.319> that<00:49:25.500> do<00:49:25.800> bootstrap<00:49:26.339> the 00:49:26.510 --> 00:49:26.520 align:start position:0% about like so that do bootstrap the 00:49:26.520 --> 00:49:29.030 align:start position:0% about like so that do bootstrap the network<00:49:26.700> and<00:49:27.300> make<00:49:27.599> it<00:49:27.720> useful<00:49:28.200> from<00:49:28.859> the 00:49:29.030 --> 00:49:29.040 align:start position:0% network and make it useful from the 00:49:29.040 --> 00:49:31.370 align:start position:0% network and make it useful from the get-go<00:49:29.400> but<00:49:29.880> also<00:49:30.300> to<00:49:30.480> compensate<00:49:31.079> early 00:49:31.370 --> 00:49:31.380 align:start position:0% get-go but also to compensate early 00:49:31.380 --> 00:49:34.670 align:start position:0% get-go but also to compensate early adopters<00:49:32.040> who<00:49:32.540> participate<00:49:33.540> in<00:49:33.839> the<00:49:34.140> in<00:49:34.500> the 00:49:34.670 --> 00:49:34.680 align:start position:0% adopters who participate in the in the 00:49:34.680 --> 00:49:36.950 align:start position:0% adopters who participate in the in the mainnet<00:49:35.220> and<00:49:35.579> then<00:49:35.760> eventually<00:49:36.359> we<00:49:36.780> expect 00:49:36.950 --> 00:49:36.960 align:start position:0% mainnet and then eventually we expect 00:49:36.960 --> 00:49:40.069 align:start position:0% mainnet and then eventually we expect that<00:49:37.500> like<00:49:38.160> others<00:49:38.880> will<00:49:39.060> follow<00:49:39.359> and<00:49:39.839> they're 00:49:40.069 --> 00:49:40.079 align:start position:0% that like others will follow and they're 00:49:40.079 --> 00:49:43.069 align:start position:0% that like others will follow and they're therefore<00:49:40.680> like<00:49:41.040> uh<00:49:41.880> we<00:49:42.180> can<00:49:42.359> bootstrap<00:49:42.839> this 00:49:43.069 --> 00:49:43.079 align:start position:0% therefore like uh we can bootstrap this 00:49:43.079 --> 00:49:44.930 align:start position:0% therefore like uh we can bootstrap this data<00:49:43.440> economy<00:49:43.859> and<00:49:44.099> then<00:49:44.220> this<00:49:44.460> can<00:49:44.640> be<00:49:44.760> a 00:49:44.930 --> 00:49:44.940 align:start position:0% data economy and then this can be a 00:49:44.940 --> 00:49:48.109 align:start position:0% data economy and then this can be a self-sustaining<00:49:45.720> system 00:49:48.109 --> 00:49:48.119 align:start position:0% self-sustaining system 00:49:48.119 --> 00:49:51.349 align:start position:0% self-sustaining system so<00:49:48.660> this<00:49:48.900> is<00:49:49.020> the<00:49:49.380> the<00:49:49.640> what<00:49:50.640> I<00:49:50.819> wanted<00:49:50.940> to<00:49:51.240> tell 00:49:51.349 --> 00:49:51.359 align:start position:0% so this is the the what I wanted to tell 00:49:51.359 --> 00:49:53.990 align:start position:0% so this is the the what I wanted to tell and<00:49:51.660> we<00:49:51.839> have<00:49:51.960> some<00:49:52.200> time<00:49:52.440> left<00:49:52.680> for<00:49:52.920> questions 00:49:53.990 --> 00:49:54.000 align:start position:0% and we have some time left for questions 00:49:54.000 --> 00:49:57.450 align:start position:0% and we have some time left for questions so<00:49:54.660> yeah 00:49:57.450 --> 00:49:57.460 align:start position:0% 00:49:57.460 --> 00:50:04.310 align:start position:0% [Music] 00:50:04.310 --> 00:50:04.320 align:start position:0% 00:50:04.320 --> 00:50:08.450 align:start position:0% [Music] 00:50:08.450 --> 00:50:08.460 align:start position:0% [Music] 00:50:08.460 --> 00:50:10.010 align:start position:0% [Music] so 00:50:10.010 --> 00:50:10.020 align:start position:0% so 00:50:10.020 --> 00:50:12.650 align:start position:0% so it<00:50:10.500> has<00:50:10.800> a<00:50:10.980> limited<00:50:11.400> capacity<00:50:11.940> so<00:50:12.240> it's<00:50:12.420> 20 00:50:12.650 --> 00:50:12.660 align:start position:0% it has a limited capacity so it's 20 00:50:12.660 --> 00:50:16.550 align:start position:0% it has a limited capacity so it's 20 Gigabytes<00:50:13.380> currently<00:50:14.339> what<00:50:15.119> it<00:50:15.359> uses<00:50:15.960> and 00:50:16.550 --> 00:50:16.560 align:start position:0% Gigabytes currently what it uses and 00:50:16.560 --> 00:50:19.670 align:start position:0% Gigabytes currently what it uses and like<00:50:17.339> it<00:50:18.000> uses<00:50:18.359> existing<00:50:18.900> data<00:50:19.260> in<00:50:19.380> the<00:50:19.560> sense 00:50:19.670 --> 00:50:19.680 align:start position:0% like it uses existing data in the sense 00:50:19.680 --> 00:50:22.550 align:start position:0% like it uses existing data in the sense that<00:50:19.980> like<00:50:20.220> it's<00:50:20.940> it's<00:50:21.240> it<00:50:21.839> will<00:50:21.960> populate<00:50:22.380> it 00:50:22.550 --> 00:50:22.560 align:start position:0% that like it's it's it will populate it 00:50:22.560 --> 00:50:24.829 align:start position:0% that like it's it's it will populate it with<00:50:22.800> data<00:50:23.160> that<00:50:23.400> is<00:50:23.520> already<00:50:23.700> uploaded<00:50:24.420> to 00:50:24.829 --> 00:50:24.839 align:start position:0% with data that is already uploaded to 00:50:24.839 --> 00:50:27.050 align:start position:0% with data that is already uploaded to the<00:50:25.140> peers<00:50:25.680> so<00:50:26.099> that<00:50:26.220> it<00:50:26.400> will<00:50:26.520> connect<00:50:26.760> their 00:50:27.050 --> 00:50:27.060 align:start position:0% the peers so that it will connect their 00:50:27.060 --> 00:50:28.910 align:start position:0% the peers so that it will connect their peers<00:50:27.420> which<00:50:27.720> has<00:50:27.900> similar<00:50:28.260> address<00:50:28.440> space 00:50:28.910 --> 00:50:28.920 align:start position:0% peers which has similar address space 00:50:28.920 --> 00:50:31.370 align:start position:0% peers which has similar address space and<00:50:29.280> then<00:50:29.520> fetch<00:50:30.180> the<00:50:30.300> data<00:50:30.660> from<00:50:30.839> that<00:50:31.020> so 00:50:31.370 --> 00:50:31.380 align:start position:0% and then fetch the data from that so 00:50:31.380 --> 00:50:35.329 align:start position:0% and then fetch the data from that so that<00:50:31.619> they<00:50:32.579> basically<00:50:33.119> share<00:50:33.440> the<00:50:34.440> data<00:50:34.800> in<00:50:34.920> a 00:50:35.329 --> 00:50:35.339 align:start position:0% that they basically share the data in a 00:50:35.339 --> 00:50:37.849 align:start position:0% that they basically share the data in a partition<00:50:35.640> of<00:50:35.940> the<00:50:36.119> network<00:50:36.440> and<00:50:37.440> for<00:50:37.680> that 00:50:37.849 --> 00:50:37.859 align:start position:0% partition of the network and for that 00:50:37.859 --> 00:50:39.530 align:start position:0% partition of the network and for that the<00:50:38.099> capacity<00:50:38.520> currently<00:50:38.940> is<00:50:39.060> this<00:50:39.300> 20 00:50:39.530 --> 00:50:39.540 align:start position:0% the capacity currently is this 20 00:50:39.540 --> 00:50:44.150 align:start position:0% the capacity currently is this 20 Gigabytes<00:50:40.579> you<00:50:41.579> can<00:50:41.760> also<00:50:42.200> pin<00:50:43.200> data<00:50:43.680> on<00:50:43.920> on 00:50:44.150 --> 00:50:44.160 align:start position:0% Gigabytes you can also pin data on on 00:50:44.160 --> 00:50:47.930 align:start position:0% Gigabytes you can also pin data on on your<00:50:45.060> node<00:50:45.420> and<00:50:45.960> that's<00:50:46.200> an<00:50:46.619> extra<00:50:46.800> space<00:50:47.400> that 00:50:47.930 --> 00:50:47.940 align:start position:0% your node and that's an extra space that 00:50:47.940 --> 00:50:50.210 align:start position:0% your node and that's an extra space that is<00:50:48.119> used<00:50:48.359> but<00:50:49.020> also<00:50:49.380> pinning<00:50:49.680> is<00:50:49.980> a<00:50:50.160> bit 00:50:50.210 --> 00:50:50.220 align:start position:0% is used but also pinning is a bit 00:50:50.220 --> 00:50:52.910 align:start position:0% is used but also pinning is a bit different<00:50:50.520> in<00:50:51.000> this<00:50:51.119> context<00:50:51.540> than<00:50:51.780> ipfs<00:50:52.559> so 00:50:52.910 --> 00:50:52.920 align:start position:0% different in this context than ipfs so 00:50:52.920 --> 00:50:55.970 align:start position:0% different in this context than ipfs so because<00:50:53.880> like<00:50:54.359> if<00:50:55.020> you<00:50:55.140> pin<00:50:55.380> data<00:50:55.740> on<00:50:55.800> your 00:50:55.970 --> 00:50:55.980 align:start position:0% because like if you pin data on your 00:50:55.980 --> 00:50:57.530 align:start position:0% because like if you pin data on your node<00:50:56.220> it<00:50:56.460> doesn't<00:50:56.640> necessarily<00:50:57.119> mean<00:50:57.300> that 00:50:57.530 --> 00:50:57.540 align:start position:0% node it doesn't necessarily mean that 00:50:57.540 --> 00:50:59.150 align:start position:0% node it doesn't necessarily mean that it's<00:50:57.660> available<00:50:57.900> on<00:50:58.319> the<00:50:58.440> network<00:50:58.619> because 00:50:59.150 --> 00:50:59.160 align:start position:0% it's available on the network because 00:50:59.160 --> 00:51:02.210 align:start position:0% it's available on the network because your<00:50:59.760> node<00:51:00.059> will<00:51:00.359> be<00:51:00.599> only<00:51:01.079> contacted<00:51:01.920> by 00:51:02.210 --> 00:51:02.220 align:start position:0% your node will be only contacted by 00:51:02.220 --> 00:51:05.870 align:start position:0% your node will be only contacted by other<00:51:02.460> nodes<00:51:02.819> if<00:51:03.119> you<00:51:03.300> are<00:51:03.540> if<00:51:04.500> if<00:51:05.040> the<00:51:05.460> data 00:51:05.870 --> 00:51:05.880 align:start position:0% other nodes if you are if if the data 00:51:05.880 --> 00:51:08.450 align:start position:0% other nodes if you are if if the data hash<00:51:06.720> matches<00:51:07.140> your<00:51:07.380> node<00:51:07.680> and<00:51:07.920> then<00:51:08.040> if<00:51:08.339> you 00:51:08.450 --> 00:51:08.460 align:start position:0% hash matches your node and then if you 00:51:08.460 --> 00:51:10.970 align:start position:0% hash matches your node and then if you upload<00:51:08.819> your<00:51:09.059> data<00:51:09.480> it's<00:51:09.599> not<00:51:09.780> guarant<00:51:10.260> it<00:51:10.740> so 00:51:10.970 --> 00:51:10.980 align:start position:0% upload your data it's not guarant it so 00:51:10.980 --> 00:51:13.670 align:start position:0% upload your data it's not guarant it so then<00:51:11.240> it<00:51:12.240> only<00:51:12.540> means<00:51:12.839> that<00:51:13.079> you<00:51:13.260> from<00:51:13.559> your 00:51:13.670 --> 00:51:13.680 align:start position:0% then it only means that you from your 00:51:13.680 --> 00:51:15.710 align:start position:0% then it only means that you from your node<00:51:13.980> it<00:51:14.220> will<00:51:14.339> be<00:51:14.520> available<00:51:14.700> that<00:51:15.420> can<00:51:15.540> be 00:51:15.710 --> 00:51:15.720 align:start position:0% node it will be available that can be 00:51:15.720 --> 00:51:17.750 align:start position:0% node it will be available that can be useful<00:51:16.020> for<00:51:16.319> some<00:51:16.440> use<00:51:16.619> case<00:51:16.859> if<00:51:17.099> you<00:51:17.280> want<00:51:17.460> to 00:51:17.750 --> 00:51:17.760 align:start position:0% useful for some use case if you want to 00:51:17.760 --> 00:51:20.450 align:start position:0% useful for some use case if you want to make<00:51:18.180> a<00:51:18.359> Gateway<00:51:18.720> for<00:51:19.020> a<00:51:19.200> web<00:51:19.380> to<00:51:19.740> kind<00:51:20.099> of<00:51:20.220> like 00:51:20.450 --> 00:51:20.460 align:start position:0% make a Gateway for a web to kind of like 00:51:20.460 --> 00:51:23.450 align:start position:0% make a Gateway for a web to kind of like so<00:51:20.940> as<00:51:21.300> a<00:51:21.480> Gateway<00:51:21.780> like<00:51:22.079> for<00:51:22.319> for<00:51:22.559> like 00:51:23.450 --> 00:51:23.460 align:start position:0% so as a Gateway like for for like 00:51:23.460 --> 00:51:25.730 align:start position:0% so as a Gateway like for for like compatibility<00:51:24.059> or<00:51:24.420> for<00:51:24.660> applications<00:51:25.319> or 00:51:25.730 --> 00:51:25.740 align:start position:0% compatibility or for applications or 00:51:25.740 --> 00:51:28.089 align:start position:0% compatibility or for applications or websites<00:51:26.339> that<00:51:26.640> does<00:51:26.940> not<00:51:27.119> have<00:51:27.480> like 00:51:28.089 --> 00:51:28.099 align:start position:0% websites that does not have like 00:51:28.099 --> 00:51:30.829 align:start position:0% websites that does not have like built-in<00:51:29.099> integration<00:51:29.579> with<00:51:29.940> swarm<00:51:30.359> so<00:51:30.599> like 00:51:30.829 --> 00:51:30.839 align:start position:0% built-in integration with swarm so like 00:51:30.839 --> 00:51:34.010 align:start position:0% built-in integration with swarm so like basically<00:51:31.319> providing<00:51:32.059> a<00:51:33.059> transitioning 00:51:34.010 --> 00:51:34.020 align:start position:0% basically providing a transitioning 00:51:34.020 --> 00:51:34.930 align:start position:0% basically providing a transitioning phase 00:51:34.930 --> 00:51:34.940 align:start position:0% phase 00:51:34.940 --> 00:51:37.609 align:start position:0% phase uh<00:51:35.940> but<00:51:36.480> yeah<00:51:36.660> so 00:51:37.609 --> 00:51:37.619 align:start position:0% uh but yeah so 00:51:37.619 --> 00:51:39.770 align:start position:0% uh but yeah so that's<00:51:38.280> that's<00:51:38.579> an<00:51:38.819> extra<00:51:38.940> capacity<00:51:39.599> and 00:51:39.770 --> 00:51:39.780 align:start position:0% that's that's an extra capacity and 00:51:39.780 --> 00:51:42.470 align:start position:0% that's that's an extra capacity and that's<00:51:40.020> not<00:51:40.200> counted<00:51:40.740> in<00:51:40.980> the<00:51:41.280> in<00:51:41.880> this<00:51:42.180> uh 00:51:42.470 --> 00:51:42.480 align:start position:0% that's not counted in the in this uh 00:51:42.480 --> 00:51:44.630 align:start position:0% that's not counted in the in this uh what<00:51:42.780> we<00:51:42.960> call<00:51:43.140> these<00:51:43.800> called<00:51:43.980> the<00:51:44.099> slantic 00:51:44.630 --> 00:51:44.640 align:start position:0% what we call these called the slantic 00:51:44.640 --> 00:51:46.190 align:start position:0% what we call these called the slantic earbuds<00:51:45.059> it's<00:51:45.180> called<00:51:45.300> the<00:51:45.480> reserve<00:51:46.020> space 00:51:46.190 --> 00:51:46.200 align:start position:0% earbuds it's called the reserve space 00:51:46.200 --> 00:51:48.710 align:start position:0% earbuds it's called the reserve space and<00:51:46.920> this<00:51:47.099> is<00:51:47.220> what<00:51:47.579> you<00:51:47.880> need<00:51:48.119> to<00:51:48.359> prove 00:51:48.710 --> 00:51:48.720 align:start position:0% and this is what you need to prove 00:51:48.720 --> 00:51:51.109 align:start position:0% and this is what you need to prove actually<00:51:49.079> when<00:51:49.920> you<00:51:50.099> participate<00:51:50.700> in<00:51:50.940> the 00:51:51.109 --> 00:51:51.119 align:start position:0% actually when you participate in the 00:51:51.119 --> 00:51:53.210 align:start position:0% actually when you participate in the storage<00:51:51.300> incentives<00:51:51.960> that<00:51:52.380> you<00:51:52.680> are<00:51:52.859> storing 00:51:53.210 --> 00:51:53.220 align:start position:0% storage incentives that you are storing 00:51:53.220 --> 00:51:55.490 align:start position:0% storage incentives that you are storing the<00:51:53.520> data 00:51:55.490 --> 00:51:55.500 align:start position:0% the data 00:51:55.500 --> 00:51:59.690 align:start position:0% the data yes<00:51:56.660> uh<00:51:57.660> yeah<00:51:57.960> so<00:51:58.260> there's<00:51:58.859> a<00:51:59.099> lot<00:51:59.280> of<00:51:59.460> other 00:51:59.690 --> 00:51:59.700 align:start position:0% yes uh yeah so there's a lot of other 00:51:59.700 --> 00:52:02.329 align:start position:0% yes uh yeah so there's a lot of other decentralized<00:52:00.599> storage<00:52:00.900> networks<00:52:01.380> yes 00:52:02.329 --> 00:52:02.339 align:start position:0% decentralized storage networks yes 00:52:02.339 --> 00:52:05.750 align:start position:0% decentralized storage networks yes um<00:52:02.400> I'm<00:52:02.579> trying<00:52:02.760> to<00:52:02.880> figure<00:52:03.000> out<00:52:03.180> what<00:52:03.480> uh<00:52:04.760> does 00:52:05.750 --> 00:52:05.760 align:start position:0% um I'm trying to figure out what uh does 00:52:05.760 --> 00:52:08.809 align:start position:0% um I'm trying to figure out what uh does swarm<00:52:06.300> differentiated<00:52:06.960> so<00:52:07.319> buy<00:52:08.280> its 00:52:08.809 --> 00:52:08.819 align:start position:0% swarm differentiated so buy its 00:52:08.819 --> 00:52:11.710 align:start position:0% swarm differentiated so buy its approximity<00:52:09.180> to<00:52:09.480> ethereum<00:52:09.960> if<00:52:10.920> so 00:52:11.710 --> 00:52:11.720 align:start position:0% approximity to ethereum if so 00:52:11.720 --> 00:52:14.510 align:start position:0% approximity to ethereum if so what<00:52:12.720> uh 00:52:14.510 --> 00:52:14.520 align:start position:0% what uh 00:52:14.520 --> 00:52:16.609 align:start position:0% what uh for<00:52:14.760> synergies<00:52:15.599> does<00:52:16.020> it<00:52:16.200> have<00:52:16.319> point 00:52:16.609 --> 00:52:16.619 align:start position:0% for synergies does it have point 00:52:16.619 --> 00:52:20.809 align:start position:0% for synergies does it have point ethereum<00:52:17.040> that<00:52:17.220> other 00:52:20.809 --> 00:52:20.819 align:start position:0% 00:52:20.819 --> 00:52:24.170 align:start position:0% so<00:52:21.540> yeah<00:52:22.200> I<00:52:22.380> didn't<00:52:23.040> really<00:52:23.280> want<00:52:23.579> to<00:52:23.700> go<00:52:24.000> into 00:52:24.170 --> 00:52:24.180 align:start position:0% so yeah I didn't really want to go into 00:52:24.180 --> 00:52:27.349 align:start position:0% so yeah I didn't really want to go into this<00:52:24.780> part<00:52:25.020> because<00:52:25.440> like<00:52:25.859> this<00:52:26.819> was<00:52:27.000> meant<00:52:27.240> to 00:52:27.349 --> 00:52:27.359 align:start position:0% this part because like this was meant to 00:52:27.359 --> 00:52:28.970 align:start position:0% this part because like this was meant to be<00:52:27.480> a<00:52:27.599> workshop<00:52:27.960> and<00:52:28.200> not<00:52:28.440> necessarily<00:52:28.859> a 00:52:28.970 --> 00:52:28.980 align:start position:0% be a workshop and not necessarily a 00:52:28.980 --> 00:52:31.670 align:start position:0% be a workshop and not necessarily a marketing<00:52:29.460> talk<00:52:30.180> but<00:52:30.599> yeah<00:52:30.839> so<00:52:31.140> I<00:52:31.319> this<00:52:31.619> is 00:52:31.670 --> 00:52:31.680 align:start position:0% marketing talk but yeah so I this is 00:52:31.680 --> 00:52:34.190 align:start position:0% marketing talk but yeah so I this is what<00:52:31.859> I<00:52:32.040> wanted<00:52:32.280> to<00:52:32.819> talk<00:52:33.300> a<00:52:33.480> bit<00:52:33.599> about<00:52:33.720> in<00:52:34.079> the 00:52:34.190 --> 00:52:34.200 align:start position:0% what I wanted to talk a bit about in the 00:52:34.200 --> 00:52:37.790 align:start position:0% what I wanted to talk a bit about in the beginning<00:52:34.380> so<00:52:34.980> yes<00:52:35.760> so<00:52:36.240> for<00:52:36.540> example<00:52:36.839> like<00:52:37.319> the 00:52:37.790 --> 00:52:37.800 align:start position:0% beginning so yes so for example like the 00:52:37.800 --> 00:52:39.530 align:start position:0% beginning so yes so for example like the the<00:52:37.980> thing<00:52:38.280> that 00:52:39.530 --> 00:52:39.540 align:start position:0% the thing that 00:52:39.540 --> 00:52:41.750 align:start position:0% the thing that for<00:52:40.079> example<00:52:40.380> the<00:52:40.800> the<00:52:40.980> built-in 00:52:41.750 --> 00:52:41.760 align:start position:0% for example the the built-in 00:52:41.760 --> 00:52:44.150 align:start position:0% for example the the built-in incentivization<00:52:42.660> is<00:52:43.559> something<00:52:43.800> that 00:52:44.150 --> 00:52:44.160 align:start position:0% incentivization is something that 00:52:44.160 --> 00:52:46.069 align:start position:0% incentivization is something that differentiates<00:52:44.640> from<00:52:44.880> from<00:52:45.180> others<00:52:45.599> so<00:52:45.839> like 00:52:46.069 --> 00:52:46.079 align:start position:0% differentiates from from others so like 00:52:46.079 --> 00:52:48.770 align:start position:0% differentiates from from others so like with<00:52:46.920> ipfs<00:52:47.579> there<00:52:47.760> is<00:52:47.880> no<00:52:48.000> incentivization 00:52:48.770 --> 00:52:48.780 align:start position:0% with ipfs there is no incentivization 00:52:48.780 --> 00:52:51.290 align:start position:0% with ipfs there is no incentivization you<00:52:49.500> can<00:52:49.559> have<00:52:49.800> incentivization<00:52:50.700> with<00:52:51.000> Phi 00:52:51.290 --> 00:52:51.300 align:start position:0% you can have incentivization with Phi 00:52:51.300 --> 00:52:53.329 align:start position:0% you can have incentivization with Phi coin<00:52:51.660> but<00:52:51.839> Phi<00:52:52.140> coin<00:52:52.440> is<00:52:52.619> actually<00:52:52.800> not<00:52:53.099> the 00:52:53.329 --> 00:52:53.339 align:start position:0% coin but Phi coin is actually not the 00:52:53.339 --> 00:52:56.690 align:start position:0% coin but Phi coin is actually not the same<00:52:53.460> thing<00:52:53.640> as<00:52:53.819> ipss<00:52:54.540> so<00:52:54.900> it<00:52:55.559> requires<00:52:56.280> to<00:52:56.520> run 00:52:56.690 --> 00:52:56.700 align:start position:0% same thing as ipss so it requires to run 00:52:56.700 --> 00:52:58.490 align:start position:0% same thing as ipss so it requires to run a<00:52:56.940> different<00:52:57.119> demon<00:52:57.720> and<00:52:58.079> then<00:52:58.200> it's 00:52:58.490 --> 00:52:58.500 align:start position:0% a different demon and then it's 00:52:58.500 --> 00:52:59.930 align:start position:0% a different demon and then it's different<00:52:58.740> tooling<00:52:59.339> and<00:52:59.579> the<00:52:59.760> different 00:52:59.930 --> 00:52:59.940 align:start position:0% different tooling and the different 00:52:59.940 --> 00:53:03.470 align:start position:0% different tooling and the different trade-offs<00:53:00.660> so<00:53:01.559> what<00:53:02.400> we<00:53:02.520> feel<00:53:02.700> is<00:53:02.940> that<00:53:03.180> like 00:53:03.470 --> 00:53:03.480 align:start position:0% trade-offs so what we feel is that like 00:53:03.480 --> 00:53:06.309 align:start position:0% trade-offs so what we feel is that like this<00:53:03.839> is<00:53:03.960> an<00:53:04.200> integrated<00:53:04.559> solution<00:53:05.160> that 00:53:06.309 --> 00:53:06.319 align:start position:0% this is an integrated solution that 00:53:06.319 --> 00:53:09.230 align:start position:0% this is an integrated solution that seems<00:53:07.319> to<00:53:07.380> be<00:53:07.559> easier<00:53:07.920> to<00:53:08.220> set<00:53:08.400> up<00:53:08.520> and<00:53:08.940> may 00:53:09.230 --> 00:53:09.240 align:start position:0% seems to be easier to set up and may 00:53:09.240 --> 00:53:12.589 align:start position:0% seems to be easier to set up and may serve<00:53:09.780> some<00:53:10.260> use<00:53:10.500> cases<00:53:10.800> better<00:53:11.160> and<00:53:11.819> then<00:53:12.059> we 00:53:12.589 --> 00:53:12.599 align:start position:0% serve some use cases better and then we 00:53:12.599 --> 00:53:14.270 align:start position:0% serve some use cases better and then we can<00:53:12.780> discuss<00:53:13.079> like<00:53:13.380> what<00:53:13.559> are<00:53:13.800> those<00:53:13.980> use 00:53:14.270 --> 00:53:14.280 align:start position:0% can discuss like what are those use 00:53:14.280 --> 00:53:15.530 align:start position:0% can discuss like what are those use cases 00:53:15.530 --> 00:53:15.540 align:start position:0% cases 00:53:15.540 --> 00:53:20.329 align:start position:0% cases so<00:53:16.319> I<00:53:17.220> mean<00:53:17.400> what<00:53:17.880> we<00:53:18.059> feel<00:53:18.240> is<00:53:18.540> that<00:53:18.839> with<00:53:19.619> ipfs 00:53:20.329 --> 00:53:20.339 align:start position:0% so I mean what we feel is that with ipfs 00:53:20.339 --> 00:53:22.849 align:start position:0% so I mean what we feel is that with ipfs you<00:53:20.640> store<00:53:21.059> files<00:53:21.720> and<00:53:21.839> folders<00:53:22.319> and<00:53:22.619> that's 00:53:22.849 --> 00:53:22.859 align:start position:0% you store files and folders and that's 00:53:22.859 --> 00:53:25.430 align:start position:0% you store files and folders and that's useful<00:53:23.339> for<00:53:23.940> many<00:53:24.119> things<00:53:24.420> but<00:53:24.780> we<00:53:25.079> feel<00:53:25.200> that 00:53:25.430 --> 00:53:25.440 align:start position:0% useful for many things but we feel that 00:53:25.440 --> 00:53:27.530 align:start position:0% useful for many things but we feel that for<00:53:25.619> example<00:53:25.920> swarm<00:53:26.460> you<00:53:26.760> can<00:53:26.880> store<00:53:27.240> like 00:53:27.530 --> 00:53:27.540 align:start position:0% for example swarm you can store like 00:53:27.540 --> 00:53:29.930 align:start position:0% for example swarm you can store like data<00:53:28.020> structures<00:53:28.380> that<00:53:28.859> can<00:53:29.220> point<00:53:29.460> to<00:53:29.700> to 00:53:29.930 --> 00:53:29.940 align:start position:0% data structures that can point to to 00:53:29.940 --> 00:53:31.670 align:start position:0% data structures that can point to to things<00:53:30.180> and<00:53:30.420> then<00:53:30.599> application<00:53:31.140> basically 00:53:31.670 --> 00:53:31.680 align:start position:0% things and then application basically 00:53:31.680 --> 00:53:34.069 align:start position:0% things and then application basically you<00:53:31.980> can<00:53:32.040> create<00:53:32.220> like<00:53:32.900> databases<00:53:33.900> and 00:53:34.069 --> 00:53:34.079 align:start position:0% you can create like databases and 00:53:34.079 --> 00:53:36.650 align:start position:0% you can create like databases and applications<00:53:34.619> that<00:53:35.339> store<00:53:35.760> those<00:53:36.000> form<00:53:36.359> and 00:53:36.650 --> 00:53:36.660 align:start position:0% applications that store those form and 00:53:36.660 --> 00:53:38.569 align:start position:0% applications that store those form and use<00:53:36.900> this<00:53:37.079> form<00:53:37.319> as<00:53:37.559> a<00:53:37.680> backend<00:53:37.980> so<00:53:38.220> it's<00:53:38.460> like 00:53:38.569 --> 00:53:38.579 align:start position:0% use this form as a backend so it's like 00:53:38.579 --> 00:53:41.569 align:start position:0% use this form as a backend so it's like not<00:53:38.880> only<00:53:39.079> not<00:53:40.079> only<00:53:40.200> for<00:53:40.440> storage<00:53:40.740> but<00:53:41.160> also 00:53:41.569 --> 00:53:41.579 align:start position:0% not only not only for storage but also 00:53:41.579 --> 00:53:43.970 align:start position:0% not only not only for storage but also for<00:53:41.760> like<00:53:42.000> messaging<00:53:42.660> and<00:53:43.020> and<00:53:43.559> there's<00:53:43.800> a 00:53:43.970 --> 00:53:43.980 align:start position:0% for like messaging and and there's a 00:53:43.980 --> 00:53:47.390 align:start position:0% for like messaging and and there's a decentralized<00:53:44.819> cloud<00:53:45.440> not<00:53:46.440> only<00:53:46.680> just<00:53:47.099> the 00:53:47.390 --> 00:53:47.400 align:start position:0% decentralized cloud not only just the 00:53:47.400 --> 00:53:50.450 align:start position:0% decentralized cloud not only just the storage<00:53:47.640> part 00:53:50.450 --> 00:53:50.460 align:start position:0% 00:53:50.460 --> 00:53:52.730 align:start position:0% okay<00:53:51.000> here<00:53:51.540> sorry 00:53:52.730 --> 00:53:52.740 align:start position:0% okay here sorry 00:53:52.740 --> 00:53:54.170 align:start position:0% okay here sorry um 00:53:54.170 --> 00:53:54.180 align:start position:0% um 00:53:54.180 --> 00:53:56.150 align:start position:0% um um<00:53:54.359> two<00:53:54.720> questions<00:53:54.900> quickly<00:53:55.380> uh<00:53:55.740> number<00:53:55.920> one 00:53:56.150 --> 00:53:56.160 align:start position:0% um two questions quickly uh number one 00:53:56.160 --> 00:53:58.790 align:start position:0% um two questions quickly uh number one uh<00:53:56.579> as<00:53:56.819> I<00:53:57.000> understand<00:53:57.119> uh<00:53:57.960> you<00:53:58.200> have<00:53:58.440> to<00:53:58.559> that 00:53:58.790 --> 00:53:58.800 align:start position:0% uh as I understand uh you have to that 00:53:58.800 --> 00:54:00.650 align:start position:0% uh as I understand uh you have to that you<00:53:59.220> have<00:53:59.280> to<00:53:59.400> pay<00:53:59.520> to<00:53:59.760> download<00:54:00.000> and<00:54:00.300> pay<00:54:00.480> to 00:54:00.650 --> 00:54:00.660 align:start position:0% you have to pay to download and pay to 00:54:00.660 --> 00:54:05.329 align:start position:0% you have to pay to download and pay to upload<00:54:01.020> right<00:54:01.319> yes<00:54:02.240> uh<00:54:03.240> okay<00:54:03.480> second<00:54:04.319> question 00:54:05.329 --> 00:54:05.339 align:start position:0% upload right yes uh okay second question 00:54:05.339 --> 00:54:08.089 align:start position:0% upload right yes uh okay second question um<00:54:05.460> you<00:54:06.000> said<00:54:06.180> something<00:54:06.480> about<00:54:07.020> graph<00:54:07.680> using 00:54:08.089 --> 00:54:08.099 align:start position:0% um you said something about graph using 00:54:08.099 --> 00:54:10.390 align:start position:0% um you said something about graph using clef<00:54:08.460> in<00:54:08.940> the 00:54:10.390 --> 00:54:10.400 align:start position:0% clef in the 00:54:10.400 --> 00:54:12.530 align:start position:0% clef in the installer<00:54:11.400> for<00:54:11.579> example<00:54:11.760> when<00:54:12.000> you're<00:54:12.180> using 00:54:12.530 --> 00:54:12.540 align:start position:0% installer for example when you're using 00:54:12.540 --> 00:54:14.870 align:start position:0% installer for example when you're using multiple<00:54:12.839> Hive<00:54:13.200> clients<00:54:13.619> in<00:54:13.800> this<00:54:14.220> as<00:54:14.700> a 00:54:14.870 --> 00:54:14.880 align:start position:0% multiple Hive clients in this as a 00:54:14.880 --> 00:54:17.650 align:start position:0% multiple Hive clients in this as a single<00:54:15.119> cluster<00:54:15.900> but<00:54:16.800> uh<00:54:17.220> the<00:54:17.400> the 00:54:17.650 --> 00:54:17.660 align:start position:0% single cluster but uh the the 00:54:17.660 --> 00:54:19.910 align:start position:0% single cluster but uh the the documentation<00:54:18.660> says<00:54:19.140> he<00:54:19.260> recommends<00:54:19.800> it 00:54:19.910 --> 00:54:19.920 align:start position:0% documentation says he recommends it 00:54:19.920 --> 00:54:22.609 align:start position:0% documentation says he recommends it using<00:54:20.579> clef<00:54:20.940> but<00:54:21.240> you<00:54:21.480> right<00:54:21.720> now<00:54:21.900> you<00:54:22.079> said<00:54:22.380> a 00:54:22.609 --> 00:54:22.619 align:start position:0% using clef but you right now you said a 00:54:22.619 --> 00:54:24.230 align:start position:0% using clef but you right now you said a few<00:54:22.800> minutes<00:54:22.920> ago<00:54:23.220> that<00:54:23.460> it<00:54:23.700> that<00:54:24.059> probably 00:54:24.230 --> 00:54:24.240 align:start position:0% few minutes ago that it that probably 00:54:24.240 --> 00:54:25.609 align:start position:0% few minutes ago that it that probably that<00:54:24.599> you're<00:54:24.780> having<00:54:24.960> a<00:54:25.200> little<00:54:25.319> bit<00:54:25.500> of 00:54:25.609 --> 00:54:25.619 align:start position:0% that you're having a little bit of 00:54:25.619 --> 00:54:28.790 align:start position:0% that you're having a little bit of problems<00:54:25.980> with<00:54:26.220> the<00:54:26.339> clef<00:54:26.760> swarm<00:54:27.660> so<00:54:27.900> how<00:54:28.079> does 00:54:28.790 --> 00:54:28.800 align:start position:0% problems with the clef swarm so how does 00:54:28.800 --> 00:54:31.670 align:start position:0% problems with the clef swarm so how does that<00:54:28.920> work<00:54:29.099> so<00:54:29.760> what<00:54:30.660> I<00:54:30.839> recommend<00:54:31.260> here<00:54:31.440> is 00:54:31.670 --> 00:54:31.680 align:start position:0% that work so what I recommend here is 00:54:31.680 --> 00:54:33.770 align:start position:0% that work so what I recommend here is that<00:54:31.800> if<00:54:31.980> you<00:54:32.160> want<00:54:32.280> to<00:54:32.400> try<00:54:32.760> out<00:54:33.000> running<00:54:33.420> your 00:54:33.770 --> 00:54:33.780 align:start position:0% that if you want to try out running your 00:54:33.780 --> 00:54:36.470 align:start position:0% that if you want to try out running your own<00:54:33.960> node<00:54:34.260> start<00:54:34.980> without<00:54:35.220> clef<00:54:35.880> if<00:54:36.119> you<00:54:36.300> have 00:54:36.470 --> 00:54:36.480 align:start position:0% own node start without clef if you have 00:54:36.480 --> 00:54:38.329 align:start position:0% own node start without clef if you have multiple<00:54:36.839> nodes<00:54:37.260> and<00:54:37.500> you<00:54:37.680> want<00:54:37.800> to<00:54:37.980> manage 00:54:38.329 --> 00:54:38.339 align:start position:0% multiple nodes and you want to manage 00:54:38.339 --> 00:54:40.430 align:start position:0% multiple nodes and you want to manage the<00:54:38.640> keys<00:54:38.940> for<00:54:39.300> them<00:54:39.540> and<00:54:39.900> you<00:54:40.140> want<00:54:40.319> to 00:54:40.430 --> 00:54:40.440 align:start position:0% the keys for them and you want to 00:54:40.440 --> 00:54:41.930 align:start position:0% the keys for them and you want to basically<00:54:40.740> have<00:54:40.980> an<00:54:41.160> operation<00:54:41.520> running 00:54:41.930 --> 00:54:41.940 align:start position:0% basically have an operation running 00:54:41.940 --> 00:54:44.750 align:start position:0% basically have an operation running multiple<00:54:42.839> nodes<00:54:43.200> then<00:54:43.559> consider<00:54:44.160> running<00:54:44.460> it 00:54:44.750 --> 00:54:44.760 align:start position:0% multiple nodes then consider running it 00:54:44.760 --> 00:54:47.150 align:start position:0% multiple nodes then consider running it with<00:54:44.940> clef<00:54:45.300> but<00:54:46.020> by<00:54:46.260> default<00:54:46.619> I<00:54:46.859> think<00:54:46.980> it's 00:54:47.150 --> 00:54:47.160 align:start position:0% with clef but by default I think it's 00:54:47.160 --> 00:54:49.490 align:start position:0% with clef but by default I think it's easier<00:54:47.460> to<00:54:47.760> start<00:54:47.940> without<00:54:48.180> clef<00:54:48.780> and<00:54:49.380> what 00:54:49.490 --> 00:54:49.500 align:start position:0% easier to start without clef and what 00:54:49.500 --> 00:54:52.730 align:start position:0% easier to start without clef and what was<00:54:49.740> the<00:54:49.920> first<00:54:50.099> question<00:54:50.339> sorry<00:54:50.760> uh 00:54:52.730 --> 00:54:52.740 align:start position:0% was the first question sorry uh 00:54:52.740 --> 00:54:54.290 align:start position:0% was the first question sorry uh yeah<00:54:53.220> they<00:54:53.460> upload<00:54:53.760> them<00:54:53.880> though<00:54:54.059> yeah<00:54:54.240> yeah 00:54:54.290 --> 00:54:54.300 align:start position:0% yeah they upload them though yeah yeah 00:54:54.300 --> 00:54:57.130 align:start position:0% yeah they upload them though yeah yeah pay<00:54:54.780> to<00:54:55.200> upload<00:54:55.440> pay<00:54:55.559> to<00:54:55.800> download<00:54:55.920> yes 00:54:57.130 --> 00:54:57.140 align:start position:0% pay to upload pay to download yes 00:54:57.140 --> 00:55:00.170 align:start position:0% pay to upload pay to download yes we<00:54:58.140> have<00:54:58.440> three<00:54:58.740> minutes<00:54:58.980> left<00:54:59.339> any<00:54:59.880> other 00:55:00.170 --> 00:55:00.180 align:start position:0% we have three minutes left any other 00:55:00.180 --> 00:55:06.530 align:start position:0% we have three minutes left any other questions<00:55:00.540> yeah 00:55:06.530 --> 00:55:06.540 align:start position:0% 00:55:06.540 --> 00:55:08.569 align:start position:0% so<00:55:07.079> it's<00:55:07.260> uh<00:55:07.500> regarding<00:55:07.920> the<00:55:08.099> download<00:55:08.280> and 00:55:08.569 --> 00:55:08.579 align:start position:0% so it's uh regarding the download and 00:55:08.579 --> 00:55:10.130 align:start position:0% so it's uh regarding the download and upload<00:55:08.880> payment 00:55:10.130 --> 00:55:10.140 align:start position:0% upload payment 00:55:10.140 --> 00:55:11.690 align:start position:0% upload payment so<00:55:10.619> what 00:55:11.690 --> 00:55:11.700 align:start position:0% so what 00:55:11.700 --> 00:55:13.910 align:start position:0% so what let's<00:55:12.059> say<00:55:12.420> we<00:55:12.660> have<00:55:12.780> this<00:55:12.960> app<00:55:13.140> YouTube<00:55:13.559> or 00:55:13.910 --> 00:55:13.920 align:start position:0% let's say we have this app YouTube or 00:55:13.920 --> 00:55:16.190 align:start position:0% let's say we have this app YouTube or Netflix<00:55:14.099> running<00:55:14.579> fully<00:55:14.940> on<00:55:15.119> Swarm<00:55:15.480> and 00:55:16.190 --> 00:55:16.200 align:start position:0% Netflix running fully on Swarm and 00:55:16.200 --> 00:55:17.510 align:start position:0% Netflix running fully on Swarm and there's<00:55:16.319> content<00:55:16.740> that's<00:55:16.859> very<00:55:17.040> viral<00:55:17.339> and 00:55:17.510 --> 00:55:17.520 align:start position:0% there's content that's very viral and 00:55:17.520 --> 00:55:19.190 align:start position:0% there's content that's very viral and everybody's<00:55:17.940> watching<00:55:18.300> it 00:55:19.190 --> 00:55:19.200 align:start position:0% everybody's watching it 00:55:19.200 --> 00:55:21.230 align:start position:0% everybody's watching it and<00:55:19.619> of<00:55:19.800> course<00:55:19.920> you<00:55:20.460> as<00:55:20.700> a<00:55:20.819> provider<00:55:21.180> you 00:55:21.230 --> 00:55:21.240 align:start position:0% and of course you as a provider you 00:55:21.240 --> 00:55:23.690 align:start position:0% and of course you as a provider you don't<00:55:21.359> want<00:55:21.540> to<00:55:21.599> pay<00:55:21.720> for<00:55:21.900> the<00:55:22.020> bandwidth<00:55:22.859> so 00:55:23.690 --> 00:55:23.700 align:start position:0% don't want to pay for the bandwidth so 00:55:23.700 --> 00:55:27.049 align:start position:0% don't want to pay for the bandwidth so in<00:55:24.119> terms<00:55:24.420> of<00:55:24.480> a<00:55:24.720> user<00:55:25.079> experience<00:55:25.819> that<00:55:26.819> means 00:55:27.049 --> 00:55:27.059 align:start position:0% in terms of a user experience that means 00:55:27.059 --> 00:55:28.849 align:start position:0% in terms of a user experience that means that<00:55:27.300> every<00:55:27.599> user<00:55:27.900> of<00:55:28.020> this<00:55:28.140> app<00:55:28.319> will<00:55:28.500> have<00:55:28.680> to 00:55:28.849 --> 00:55:28.859 align:start position:0% that every user of this app will have to 00:55:28.859 --> 00:55:31.790 align:start position:0% that every user of this app will have to have<00:55:29.040> a<00:55:29.400> some<00:55:30.059> sort<00:55:30.240> of<00:55:30.359> a<00:55:30.480> wallet 00:55:31.790 --> 00:55:31.800 align:start position:0% have a some sort of a wallet 00:55:31.800 --> 00:55:33.950 align:start position:0% have a some sort of a wallet that<00:55:32.280> will<00:55:32.460> have<00:55:32.640> to<00:55:32.819> pay<00:55:33.000> for<00:55:33.420> that<00:55:33.599> content 00:55:33.950 --> 00:55:33.960 align:start position:0% that will have to pay for that content 00:55:33.960 --> 00:55:36.710 align:start position:0% that will have to pay for that content to<00:55:34.859> consume<00:55:35.280> it<00:55:35.339> so<00:55:36.059> yeah<00:55:36.240> that's<00:55:36.420> a<00:55:36.599> good 00:55:36.710 --> 00:55:36.720 align:start position:0% to consume it so yeah that's a good 00:55:36.720 --> 00:55:40.089 align:start position:0% to consume it so yeah that's a good question<00:55:36.960> so<00:55:37.680> what<00:55:37.980> I<00:55:38.520> imagine<00:55:38.880> this<00:55:39.300> is<00:55:39.480> that 00:55:40.089 --> 00:55:40.099 align:start position:0% question so what I imagine this is that 00:55:40.099 --> 00:55:43.190 align:start position:0% question so what I imagine this is that basically<00:55:41.480> this<00:55:42.480> depends<00:55:42.900> on<00:55:43.020> the 00:55:43.190 --> 00:55:43.200 align:start position:0% basically this depends on the 00:55:43.200 --> 00:55:44.569 align:start position:0% basically this depends on the application<00:55:43.619> layer<00:55:44.099> and<00:55:44.160> how<00:55:44.460> the 00:55:44.569 --> 00:55:44.579 align:start position:0% application layer and how the 00:55:44.579 --> 00:55:46.609 align:start position:0% application layer and how the application<00:55:45.059> layer<00:55:45.480> manages<00:55:45.780> this<00:55:46.140> so<00:55:46.319> like 00:55:46.609 --> 00:55:46.619 align:start position:0% application layer manages this so like 00:55:46.619 --> 00:55:49.790 align:start position:0% application layer manages this so like in<00:55:47.160> this<00:55:47.220> regard<00:55:47.520> like<00:55:47.760> swarm<00:55:48.300> is<00:55:48.480> the<00:55:48.839> if<00:55:49.319> that 00:55:49.790 --> 00:55:49.800 align:start position:0% in this regard like swarm is the if that 00:55:49.800 --> 00:55:51.650 align:start position:0% in this regard like swarm is the if that we<00:55:49.980> talk<00:55:50.160> about<00:55:50.280> like<00:55:50.520> it's<00:55:50.760> a<00:55:50.940> decentralized 00:55:51.650 --> 00:55:51.660 align:start position:0% we talk about like it's a decentralized 00:55:51.660 --> 00:55:54.530 align:start position:0% we talk about like it's a decentralized cloud<00:55:51.839> then<00:55:52.619> it's<00:55:52.859> again<00:55:53.099> like<00:55:53.540> somehow 00:55:54.530 --> 00:55:54.540 align:start position:0% cloud then it's again like somehow 00:55:54.540 --> 00:55:56.690 align:start position:0% cloud then it's again like somehow applications<00:55:55.200> can<00:55:55.559> abstract<00:55:55.920> this<00:55:56.220> away<00:55:56.400> so 00:55:56.690 --> 00:55:56.700 align:start position:0% applications can abstract this away so 00:55:56.700 --> 00:55:59.569 align:start position:0% applications can abstract this away so also<00:55:57.119> on<00:55:57.359> YouTube<00:55:57.540> you<00:55:58.020> don't<00:55:58.200> pay<00:55:58.559> for<00:55:58.980> like 00:55:59.569 --> 00:55:59.579 align:start position:0% also on YouTube you don't pay for like 00:55:59.579 --> 00:56:02.270 align:start position:0% also on YouTube you don't pay for like Google<00:55:59.940> Cloud<00:56:00.480> but<00:56:01.020> like<00:56:01.319> you<00:56:01.619> pay<00:56:01.859> for<00:56:02.040> the 00:56:02.270 --> 00:56:02.280 align:start position:0% Google Cloud but like you pay for the 00:56:02.280 --> 00:56:04.490 align:start position:0% Google Cloud but like you pay for the YouTube<00:56:02.460> and<00:56:02.819> then<00:56:03.000> how<00:56:03.300> it<00:56:03.480> handles<00:56:04.020> this 00:56:04.490 --> 00:56:04.500 align:start position:0% YouTube and then how it handles this 00:56:04.500 --> 00:56:06.170 align:start position:0% YouTube and then how it handles this problem<00:56:04.920> in<00:56:05.280> the<00:56:05.400> background<00:56:05.640> it's<00:56:06.059> a 00:56:06.170 --> 00:56:06.180 align:start position:0% problem in the background it's a 00:56:06.180 --> 00:56:09.170 align:start position:0% problem in the background it's a different<00:56:06.300> story<00:56:06.720> so<00:56:07.559> we<00:56:07.800> don't<00:56:08.040> have<00:56:08.520> all<00:56:08.940> the 00:56:09.170 --> 00:56:09.180 align:start position:0% different story so we don't have all the 00:56:09.180 --> 00:56:11.750 align:start position:0% different story so we don't have all the answers<00:56:09.540> to<00:56:09.839> that<00:56:10.020> but<00:56:10.740> like<00:56:10.980> one<00:56:11.220> way<00:56:11.400> to<00:56:11.640> do 00:56:11.750 --> 00:56:11.760 align:start position:0% answers to that but like one way to do 00:56:11.760 --> 00:56:14.510 align:start position:0% answers to that but like one way to do that<00:56:12.000> is<00:56:12.359> or<00:56:12.839> one<00:56:13.140> way<00:56:13.500> how<00:56:13.920> you<00:56:14.040> imagine<00:56:14.220> this 00:56:14.510 --> 00:56:14.520 align:start position:0% that is or one way how you imagine this 00:56:14.520 --> 00:56:16.790 align:start position:0% that is or one way how you imagine this is<00:56:14.760> that<00:56:15.119> this<00:56:15.720> post<00:56:15.960> is<00:56:16.140> the<00:56:16.440> mechanism 00:56:16.790 --> 00:56:16.800 align:start position:0% is that this post is the mechanism 00:56:16.800 --> 00:56:19.069 align:start position:0% is that this post is the mechanism currently<00:56:17.460> it's<00:56:17.640> tied<00:56:18.000> to<00:56:18.300> your<00:56:18.480> node<00:56:18.780> but 00:56:19.069 --> 00:56:19.079 align:start position:0% currently it's tied to your node but 00:56:19.079 --> 00:56:20.990 align:start position:0% currently it's tied to your node but it's<00:56:19.260> it<00:56:19.500> doesn't<00:56:19.740> have<00:56:19.980> to<00:56:20.099> be<00:56:20.280> that<00:56:20.460> way<00:56:20.640> so 00:56:20.990 --> 00:56:21.000 align:start position:0% it's it doesn't have to be that way so 00:56:21.000 --> 00:56:23.329 align:start position:0% it's it doesn't have to be that way so it<00:56:21.180> can<00:56:21.300> be<00:56:21.480> actually<00:56:21.720> portable<00:56:22.319> and<00:56:23.160> then 00:56:23.329 --> 00:56:23.339 align:start position:0% it can be actually portable and then 00:56:23.339 --> 00:56:25.970 align:start position:0% it can be actually portable and then basically<00:56:23.960> you<00:56:24.960> can<00:56:25.020> you<00:56:25.319> can<00:56:25.440> you<00:56:25.680> can<00:56:25.800> make 00:56:25.970 --> 00:56:25.980 align:start position:0% basically you can you can you can make 00:56:25.980 --> 00:56:27.309 align:start position:0% basically you can you can you can make your<00:56:26.220> application 00:56:27.309 --> 00:56:27.319 align:start position:0% your application 00:56:27.319 --> 00:56:30.109 align:start position:0% your application handouts<00:56:28.319> postage<00:56:28.920> stamps<00:56:29.400> and<00:56:29.520> then<00:56:29.760> with 00:56:30.109 --> 00:56:30.119 align:start position:0% handouts postage stamps and then with 00:56:30.119 --> 00:56:32.930 align:start position:0% handouts postage stamps and then with that<00:56:30.300> it<00:56:30.599> can<00:56:30.780> enable<00:56:31.339> uploading<00:56:32.339> even<00:56:32.579> in<00:56:32.819> the 00:56:32.930 --> 00:56:32.940 align:start position:0% that it can enable uploading even in the 00:56:32.940 --> 00:56:35.569 align:start position:0% that it can enable uploading even in the browser<00:56:33.300> without<00:56:33.660> having<00:56:34.140> to<00:56:34.559> connect<00:56:35.099> to<00:56:35.400> a 00:56:35.569 --> 00:56:35.579 align:start position:0% browser without having to connect to a 00:56:35.579 --> 00:56:37.130 align:start position:0% browser without having to connect to a full<00:56:35.760> node<00:56:36.059> or<00:56:36.240> like<00:56:36.480> having<00:56:36.660> to<00:56:36.960> have 00:56:37.130 --> 00:56:37.140 align:start position:0% full node or like having to have 00:56:37.140 --> 00:56:40.910 align:start position:0% full node or like having to have capacity<00:56:37.680> for<00:56:38.040> for<00:56:38.579> things<00:56:39.059> so<00:56:39.720> that's<00:56:40.619> we 00:56:40.910 --> 00:56:40.920 align:start position:0% capacity for for things so that's we 00:56:40.920 --> 00:56:42.650 align:start position:0% capacity for for things so that's we have<00:56:41.040> ideas<00:56:41.280> about<00:56:41.640> that<00:56:41.940> but<00:56:42.240> this<00:56:42.480> is 00:56:42.650 --> 00:56:42.660 align:start position:0% have ideas about that but this is 00:56:42.660 --> 00:56:45.290 align:start position:0% have ideas about that but this is something<00:56:42.900> that<00:56:43.440> still<00:56:44.220> needs<00:56:44.520> to<00:56:44.640> come<00:56:44.880> and 00:56:45.290 --> 00:56:45.300 align:start position:0% something that still needs to come and 00:56:45.300 --> 00:56:48.950 align:start position:0% something that still needs to come and applications<00:56:45.900> are<00:56:46.800> built 00:56:48.950 --> 00:56:48.960 align:start position:0% applications are built 00:56:48.960 --> 00:56:52.309 align:start position:0% applications are built all<00:56:49.619> right<00:56:49.859> and<00:56:50.099> I<00:56:50.339> have<00:56:50.460> a<00:56:50.640> question<00:56:50.819> here<00:56:51.319> uh 00:56:52.309 --> 00:56:52.319 align:start position:0% all right and I have a question here uh 00:56:52.319 --> 00:56:56.690 align:start position:0% all right and I have a question here uh you<00:56:52.740> show<00:56:52.980> us<00:56:53.220> that<00:56:53.760> in<00:56:54.540> this<00:56:54.900> one<00:56:55.200> take<00:56:56.160> an<00:56:56.400> R 00:56:56.690 --> 00:56:56.700 align:start position:0% you show us that in this one take an R 00:56:56.700 --> 00:57:00.349 align:start position:0% you show us that in this one take an R shift<00:56:57.059> and<00:56:57.359> divide<00:56:57.780> it<00:56:58.020> in<00:56:58.260> small<00:56:58.740> blocks 00:57:00.349 --> 00:57:00.359 align:start position:0% shift and divide it in small blocks 00:57:00.359 --> 00:57:03.170 align:start position:0% shift and divide it in small blocks um<00:57:00.480> well<00:57:00.780> sharing<00:57:01.559> the<00:57:01.800> network<00:57:02.180> what 00:57:03.170 --> 00:57:03.180 align:start position:0% um well sharing the network what 00:57:03.180 --> 00:57:06.890 align:start position:0% um well sharing the network what happened<00:57:03.480> if<00:57:04.079> for<00:57:04.440> example<00:57:04.859> for<00:57:05.579> example<00:57:05.900> my 00:57:06.890 --> 00:57:06.900 align:start position:0% happened if for example for example my 00:57:06.900 --> 00:57:08.690 align:start position:0% happened if for example for example my now<00:57:07.200> is<00:57:07.619> corrupted 00:57:08.690 --> 00:57:08.700 align:start position:0% now is corrupted 00:57:08.700 --> 00:57:11.150 align:start position:0% now is corrupted and<00:57:08.940> after<00:57:09.480> this<00:57:09.720> project<00:57:10.020> and<00:57:10.740> what<00:57:10.980> happened 00:57:11.150 --> 00:57:11.160 align:start position:0% and after this project and what happened 00:57:11.160 --> 00:57:14.329 align:start position:0% and after this project and what happened if<00:57:11.520> I'm<00:57:11.819> user<00:57:12.240> want<00:57:12.540> to<00:57:12.720> make<00:57:13.559> modifications 00:57:14.329 --> 00:57:14.339 align:start position:0% if I'm user want to make modifications 00:57:14.339 --> 00:57:16.130 align:start position:0% if I'm user want to make modifications to<00:57:14.700> the<00:57:15.000> fire 00:57:16.130 --> 00:57:16.140 align:start position:0% to the fire 00:57:16.140 --> 00:57:17.770 align:start position:0% to the fire so 00:57:17.770 --> 00:57:17.780 align:start position:0% so 00:57:17.780 --> 00:57:23.030 align:start position:0% so the<00:57:19.099> so<00:57:20.099> all<00:57:20.819> the<00:57:21.059> all<00:57:21.240> the<00:57:21.420> data<00:57:21.720> on<00:57:21.900> Swarm<00:57:22.440> is 00:57:23.030 --> 00:57:23.040 align:start position:0% the so all the all the data on Swarm is 00:57:23.040 --> 00:57:26.150 align:start position:0% the so all the all the data on Swarm is is<00:57:23.339> stored<00:57:23.940> by<00:57:24.180> this<00:57:24.480> content<00:57:25.020> hash<00:57:25.500> so 00:57:26.150 --> 00:57:26.160 align:start position:0% is stored by this content hash so 00:57:26.160 --> 00:57:28.190 align:start position:0% is stored by this content hash so basically<00:57:26.640> you<00:57:27.119> can<00:57:27.240> with<00:57:27.599> that<00:57:27.839> you<00:57:28.079> can 00:57:28.190 --> 00:57:28.200 align:start position:0% basically you can with that you can 00:57:28.200 --> 00:57:30.349 align:start position:0% basically you can with that you can detect<00:57:28.619> if<00:57:28.920> the<00:57:29.099> data<00:57:29.400> has<00:57:29.640> been<00:57:29.760> tampered 00:57:30.349 --> 00:57:30.359 align:start position:0% detect if the data has been tampered 00:57:30.359 --> 00:57:33.349 align:start position:0% detect if the data has been tampered with<00:57:30.480> or<00:57:30.780> like<00:57:31.020> changed<00:57:31.500> or<00:57:31.680> corrupted<00:57:32.359> and 00:57:33.349 --> 00:57:33.359 align:start position:0% with or like changed or corrupted and 00:57:33.359 --> 00:57:34.910 align:start position:0% with or like changed or corrupted and like 00:57:34.910 --> 00:57:34.920 align:start position:0% like 00:57:34.920 --> 00:57:37.309 align:start position:0% like all<00:57:35.520> the<00:57:35.760> data<00:57:36.180> has 00:57:37.309 --> 00:57:37.319 align:start position:0% all the data has 00:57:37.319 --> 00:57:40.549 align:start position:0% all the data has is<00:57:37.800> replicated<00:57:38.700> on<00:57:39.059> the<00:57:39.180> network<00:57:39.359> so<00:57:39.900> like<00:57:40.200> if 00:57:40.549 --> 00:57:40.559 align:start position:0% is replicated on the network so like if 00:57:40.559 --> 00:57:43.690 align:start position:0% is replicated on the network so like if only<00:57:40.740> one<00:57:41.040> node<00:57:41.460> is<00:57:41.700> changing<00:57:42.480> the<00:57:42.720> data 00:57:43.690 --> 00:57:43.700 align:start position:0% only one node is changing the data 00:57:43.700 --> 00:57:46.309 align:start position:0% only one node is changing the data then<00:57:44.700> actually<00:57:45.180> it<00:57:45.540> can<00:57:45.720> be<00:57:45.839> caught<00:57:46.079> and 00:57:46.309 --> 00:57:46.319 align:start position:0% then actually it can be caught and 00:57:46.319 --> 00:57:48.470 align:start position:0% then actually it can be caught and actually<00:57:46.559> it<00:57:46.740> will<00:57:46.920> be<00:57:47.099> called<00:57:47.280> once<00:57:47.819> it's<00:57:48.000> uh 00:57:48.470 --> 00:57:48.480 align:start position:0% actually it will be called once it's uh 00:57:48.480 --> 00:57:51.049 align:start position:0% actually it will be called once it's uh participating<00:57:49.319> in<00:57:49.680> the<00:57:49.800> storage<00:57:49.980> Lottery<00:57:50.400> and 00:57:51.049 --> 00:57:51.059 align:start position:0% participating in the storage Lottery and 00:57:51.059 --> 00:57:53.809 align:start position:0% participating in the storage Lottery and make<00:57:51.300> a<00:57:51.540> claim<00:57:51.839> for<00:57:52.440> storing<00:57:52.920> data<00:57:53.339> that<00:57:53.579> they 00:57:53.809 --> 00:57:53.819 align:start position:0% make a claim for storing data that they 00:57:53.819 --> 00:57:56.809 align:start position:0% make a claim for storing data that they have<00:57:54.059> they<00:57:54.839> actually<00:57:55.020> need<00:57:55.380> to<00:57:55.680> make<00:57:56.040> a<00:57:56.280> uh 00:57:56.809 --> 00:57:56.819 align:start position:0% have they actually need to make a uh 00:57:56.819 --> 00:57:58.790 align:start position:0% have they actually need to make a uh they<00:57:57.119> they<00:57:57.300> have<00:57:57.599> to<00:57:57.720> create<00:57:57.839> a<00:57:58.140> cryptographic 00:57:58.790 --> 00:57:58.800 align:start position:0% they they have to create a cryptographic 00:57:58.800 --> 00:58:02.990 align:start position:0% they they have to create a cryptographic proof<00:57:59.280> and<00:58:00.180> when<00:58:00.720> doing<00:58:01.020> that<00:58:01.440> it<00:58:02.099> can<00:58:02.339> it<00:58:02.760> it 00:58:02.990 --> 00:58:03.000 align:start position:0% proof and when doing that it can it it 00:58:03.000 --> 00:58:05.450 align:start position:0% proof and when doing that it can it it will<00:58:03.240> reveal<00:58:03.720> that<00:58:04.020> like<00:58:04.319> if<00:58:04.740> they<00:58:04.920> tampered 00:58:05.450 --> 00:58:05.460 align:start position:0% will reveal that like if they tampered 00:58:05.460 --> 00:58:07.190 align:start position:0% will reveal that like if they tampered with<00:58:05.579> the<00:58:05.760> data<00:58:06.059> or<00:58:06.180> changed<00:58:06.540> or<00:58:06.720> corrupted 00:58:07.190 --> 00:58:07.200 align:start position:0% with the data or changed or corrupted 00:58:07.200 --> 00:58:10.910 align:start position:0% with the data or changed or corrupted then<00:58:08.160> they<00:58:08.880> cannot<00:58:09.180> really<00:58:09.420> so<00:58:10.319> at<00:58:10.559> that<00:58:10.740> point 00:58:10.910 --> 00:58:10.920 align:start position:0% then they cannot really so at that point 00:58:10.920 --> 00:58:14.290 align:start position:0% then they cannot really so at that point they<00:58:11.460> might<00:58:11.700> lose<00:58:12.000> their<00:58:12.359> stake<00:58:12.720> and<00:58:13.020> stuff<00:58:13.200> so 00:58:14.290 --> 00:58:14.300 align:start position:0% they might lose their stake and stuff so 00:58:14.300 --> 00:58:17.750 align:start position:0% they might lose their stake and stuff so in<00:58:15.300> this<00:58:15.420> regard<00:58:15.780> like<00:58:16.140> the<00:58:17.040> system<00:58:17.220> has 00:58:17.750 --> 00:58:17.760 align:start position:0% in this regard like the system has 00:58:17.760 --> 00:58:20.329 align:start position:0% in this regard like the system has Integrity<00:58:18.480> production<00:58:18.960> built<00:58:19.500> in 00:58:20.329 --> 00:58:20.339 align:start position:0% Integrity production built in 00:58:20.339 --> 00:58:22.130 align:start position:0% Integrity production built in and<00:58:21.240> uh 00:58:22.130 --> 00:58:22.140 align:start position:0% and uh 00:58:22.140 --> 00:58:25.250 align:start position:0% and uh and<00:58:22.859> yeah<00:58:23.160> so 00:58:25.250 --> 00:58:25.260 align:start position:0% and yeah so 00:58:25.260 --> 00:58:27.589 align:start position:0% and yeah so how<00:58:25.680> to<00:58:25.800> put<00:58:25.980> it<00:58:26.099> like<00:58:26.280> yeah<00:58:26.819> so<00:58:27.119> the<00:58:27.540> the 00:58:27.589 --> 00:58:27.599 align:start position:0% how to put it like yeah so the the 00:58:27.599 --> 00:58:29.690 align:start position:0% how to put it like yeah so the the content<00:58:28.140> hashing<00:58:28.619> makes<00:58:29.040> a<00:58:29.280> lot<00:58:29.400> of<00:58:29.520> things 00:58:29.690 --> 00:58:29.700 align:start position:0% content hashing makes a lot of things 00:58:29.700 --> 00:58:32.569 align:start position:0% content hashing makes a lot of things very<00:58:30.119> easy<00:58:30.780> in<00:58:31.200> this<00:58:31.319> regards 00:58:32.569 --> 00:58:32.579 align:start position:0% very easy in this regards 00:58:32.579 --> 00:58:40.010 align:start position:0% very easy in this regards like<00:58:33.000> the<00:58:33.119> content<00:58:33.420> address<00:58:33.660> hashed 00:58:40.010 --> 00:58:40.020 align:start position:0% 00:58:40.020 --> 00:58:42.410 align:start position:0% yeah<00:58:40.440> we<00:58:40.740> also<00:58:40.980> have<00:58:41.099> a<00:58:41.220> Brands<00:58:41.640> program<00:58:41.819> if 00:58:42.410 --> 00:58:42.420 align:start position:0% yeah we also have a Brands program if 00:58:42.420 --> 00:58:44.450 align:start position:0% yeah we also have a Brands program if someone<00:58:42.660> is<00:58:42.960> interested<00:58:43.440> in<00:58:43.500> in<00:58:43.920> developing 00:58:44.450 --> 00:58:44.460 align:start position:0% someone is interested in in developing 00:58:44.460 --> 00:58:46.549 align:start position:0% someone is interested in in developing apps<00:58:45.000> on<00:58:45.059> Swarm<00:58:45.540> then<00:58:45.780> we<00:58:45.960> are<00:58:46.079> looking<00:58:46.260> for 00:58:46.549 --> 00:58:46.559 align:start position:0% apps on Swarm then we are looking for 00:58:46.559 --> 00:58:48.710 align:start position:0% apps on Swarm then we are looking for ideas<00:58:46.799> also<00:58:47.460> and<00:58:47.700> we 00:58:48.710 --> 00:58:48.720 align:start position:0% ideas also and we 00:58:48.720 --> 00:58:50.569 align:start position:0% ideas also and we the<00:58:49.079> thing<00:58:49.260> is<00:58:49.440> that<00:58:49.680> we<00:58:49.859> don't<00:58:49.980> want<00:58:50.220> to<00:58:50.400> build 00:58:50.569 --> 00:58:50.579 align:start position:0% the thing is that we don't want to build 00:58:50.579 --> 00:58:52.670 align:start position:0% the thing is that we don't want to build everything<00:58:51.000> like<00:58:51.780> actually<00:58:52.020> we<00:58:52.380> want<00:58:52.559> to 00:58:52.670 --> 00:58:52.680 align:start position:0% everything like actually we want to 00:58:52.680 --> 00:58:55.270 align:start position:0% everything like actually we want to build<00:58:52.920> as<00:58:53.460> little<00:58:53.760> as<00:58:54.119> possible<00:58:54.480> and<00:58:54.960> then 00:58:55.270 --> 00:58:55.280 align:start position:0% build as little as possible and then 00:58:55.280 --> 00:58:58.089 align:start position:0% build as little as possible and then create<00:58:56.280> this<00:58:56.579> ecosystem<00:58:57.059> where<00:58:57.540> people 00:58:58.089 --> 00:58:58.099 align:start position:0% create this ecosystem where people 00:58:58.099 --> 00:59:00.410 align:start position:0% create this ecosystem where people participate<00:58:59.099> and<00:58:59.339> create<00:58:59.640> their<00:59:00.000> own<00:59:00.119> stuff 00:59:00.410 --> 00:59:00.420 align:start position:0% participate and create their own stuff 00:59:00.420 --> 00:59:03.230 align:start position:0% participate and create their own stuff and<00:59:00.660> by<00:59:00.900> that<00:59:01.200> contribute<00:59:01.859> to<00:59:02.040> the<00:59:02.400> to<00:59:03.000> the 00:59:03.230 --> 00:59:03.240 align:start position:0% and by that contribute to the to the 00:59:03.240 --> 00:59:05.030 align:start position:0% and by that contribute to the to the network<00:59:03.420> and<00:59:03.780> the<00:59:03.960> common<00:59:04.020> goods 00:59:05.030 --> 00:59:05.040 align:start position:0% network and the common goods 00:59:05.040 --> 00:59:12.289 align:start position:0% network and the common goods you<00:59:05.460> have<00:59:05.579> a<00:59:05.700> question 00:59:12.289 --> 00:59:12.299 align:start position:0% 00:59:12.299 --> 00:59:14.510 align:start position:0% yeah<00:59:12.780> yeah<00:59:12.839> yeah<00:59:12.960> so<00:59:13.440> it's<00:59:13.799> written<00:59:14.099> and<00:59:14.280> go 00:59:14.510 --> 00:59:14.520 align:start position:0% yeah yeah yeah so it's written and go 00:59:14.520 --> 00:59:16.970 align:start position:0% yeah yeah yeah so it's written and go and<00:59:14.819> go<00:59:15.059> provides<00:59:15.780> like<00:59:15.960> easy<00:59:16.200> way<00:59:16.440> to<00:59:16.619> compile 00:59:16.970 --> 00:59:16.980 align:start position:0% and go provides like easy way to compile 00:59:16.980 --> 00:59:18.950 align:start position:0% and go provides like easy way to compile it<00:59:17.220> to<00:59:17.400> any<00:59:17.700> platform 00:59:18.950 --> 00:59:18.960 align:start position:0% it to any platform 00:59:18.960 --> 00:59:22.069 align:start position:0% it to any platform Mac<00:59:19.440> Windows<00:59:19.920> Linux<00:59:20.339> you<00:59:20.700> have<00:59:21.000> Farm<00:59:21.599> version 00:59:22.069 --> 00:59:22.079 align:start position:0% Mac Windows Linux you have Farm version 00:59:22.079 --> 00:59:25.430 align:start position:0% Mac Windows Linux you have Farm version everything<00:59:22.680> so<00:59:23.339> I<00:59:24.059> I<00:59:24.299> managed<00:59:24.660> to<00:59:24.780> even<00:59:24.960> run<00:59:25.260> it 00:59:25.430 --> 00:59:25.440 align:start position:0% everything so I I managed to even run it 00:59:25.440 --> 00:59:33.589 align:start position:0% everything so I I managed to even run it on<00:59:25.680> my<00:59:25.859> phone<00:59:26.099> so<00:59:26.640> on<00:59:26.819> Android<00:59:27.200> so<00:59:28.200> yeah 00:59:33.589 --> 00:59:33.599 align:start position:0% 00:59:33.599 --> 00:59:35.990 align:start position:0% all<00:59:34.020> right<00:59:34.160> if<00:59:35.160> there<00:59:35.339> are<00:59:35.460> no<00:59:35.579> more<00:59:35.760> questions 00:59:35.990 --> 00:59:36.000 align:start position:0% all right if there are no more questions 00:59:36.000 --> 00:59:37.870 align:start position:0% all right if there are no more questions then<00:59:36.599> thank<00:59:36.960> you 00:59:37.870 --> 00:59:37.880 align:start position:0% then thank you 00:59:37.880 --> 00:59:44.570 align:start position:0% then thank you [Applause]