WEBVTT Kind: captions Language: en 00:00:04.620 --> 00:00:14.900 align:start position:0% [Music] 00:00:14.900 --> 00:00:14.910 align:start position:0% 00:00:14.910 --> 00:00:17.150 align:start position:0% [Music] 00:00:17.150 --> 00:00:17.160 align:start position:0% [Music] 00:00:17.160 --> 00:00:19.590 align:start position:0% [Music] all<00:00:17.320> right<00:00:17.600> so<00:00:18.119> um<00:00:19.119> we're<00:00:19.279> going<00:00:19.359> to<00:00:19.480> be 00:00:19.590 --> 00:00:19.600 align:start position:0% all right so um we're going to be 00:00:19.600 --> 00:00:22.470 align:start position:0% all right so um we're going to be listening<00:00:19.960> to<00:00:20.240> a<00:00:20.439> presentation<00:00:20.880> about<00:00:21.480> swarm 00:00:22.470 --> 00:00:22.480 align:start position:0% listening to a presentation about swarm 00:00:22.480 --> 00:00:26.750 align:start position:0% listening to a presentation about swarm by<00:00:23.160> Daniel<00:00:24.160> and<00:00:24.760> Victor<00:00:25.760> um<00:00:26.000> swarm<00:00:26.439> hasn't 00:00:26.750 --> 00:00:26.760 align:start position:0% by Daniel and Victor um swarm hasn't 00:00:26.760 --> 00:00:28.269 align:start position:0% by Daniel and Victor um swarm hasn't really<00:00:27.000> had<00:00:27.240> as<00:00:27.359> much<00:00:27.599> publicity<00:00:28.039> as<00:00:28.119> it 00:00:28.269 --> 00:00:28.279 align:start position:0% really had as much publicity as it 00:00:28.279 --> 00:00:30.189 align:start position:0% really had as much publicity as it probably<00:00:28.560> should<00:00:28.880> have<00:00:29.480> um<00:00:29.599> so<00:00:30.000> please 00:00:30.189 --> 00:00:30.199 align:start position:0% probably should have um so please 00:00:30.199 --> 00:00:31.990 align:start position:0% probably should have um so please welcome<00:00:30.480> these<00:00:30.640> guys<00:00:30.840> to<00:00:30.960> the<00:00:31.119> stage<00:00:31.800> they're 00:00:31.990 --> 00:00:32.000 align:start position:0% welcome these guys to the stage they're 00:00:32.000 --> 00:00:39.869 align:start position:0% welcome these guys to the stage they're doing<00:00:32.320> awesome 00:00:39.869 --> 00:00:39.879 align:start position:0% 00:00:39.879 --> 00:00:42.470 align:start position:0% work<00:00:40.879> thanks<00:00:41.200> guys<00:00:41.520> I<00:00:41.640> start<00:00:41.920> the<00:00:42.039> talk<00:00:42.360> right 00:00:42.470 --> 00:00:42.480 align:start position:0% work thanks guys I start the talk right 00:00:42.480 --> 00:00:44.950 align:start position:0% work thanks guys I start the talk right now<00:00:42.800> before<00:00:43.039> we<00:00:43.239> set<00:00:43.440> up<00:00:43.719> yeah<00:00:44.000> just<00:00:44.520> so<00:00:44.719> that<00:00:44.879> I 00:00:44.950 --> 00:00:44.960 align:start position:0% now before we set up yeah just so that I 00:00:44.960 --> 00:00:46.750 align:start position:0% now before we set up yeah just so that I don't<00:00:45.120> want<00:00:45.239> to<00:00:45.360> make<00:00:45.480> the<00:00:45.600> same 00:00:46.750 --> 00:00:46.760 align:start position:0% don't want to make the same 00:00:46.760 --> 00:00:50.389 align:start position:0% don't want to make the same mistake<00:00:47.760> okay<00:00:48.199> so<00:00:49.000> so<00:00:49.559> so<00:00:49.760> what<00:00:49.879> is<00:00:50.039> swarm 00:00:50.389 --> 00:00:50.399 align:start position:0% mistake okay so so so what is swarm 00:00:50.399 --> 00:00:55.029 align:start position:0% mistake okay so so so what is swarm after<00:00:50.640> all<00:00:50.879> so<00:00:51.239> swarm<00:00:51.680> is<00:00:52.199> supposed<00:00:52.520> to<00:00:52.760> be<00:00:54.039> the 00:00:55.029 --> 00:00:55.039 align:start position:0% after all so swarm is supposed to be the 00:00:55.039 --> 00:00:57.990 align:start position:0% after all so swarm is supposed to be the for<00:00:55.760> for<00:00:56.320> Content<00:00:56.719> distribution<00:00:57.359> and<00:00:57.559> storage 00:00:57.990 --> 00:00:58.000 align:start position:0% for for Content distribution and storage 00:00:58.000 --> 00:01:00.990 align:start position:0% for for Content distribution and storage for<00:00:58.239> for<00:00:58.480> web<00:00:58.719> 3<00:00:59.399> so<00:00:59.559> basically<00:01:00.079> it's<00:01:00.399> it's<00:01:00.640> the 00:01:00.990 --> 00:01:01.000 align:start position:0% for for web 3 so basically it's it's the 00:01:01.000 --> 00:01:04.710 align:start position:0% for for web 3 so basically it's it's the content<00:01:01.519> distribution<00:01:02.120> Network<00:01:02.800> for<00:01:03.800> uh<00:01:03.960> for 00:01:04.710 --> 00:01:04.720 align:start position:0% content distribution Network for uh for 00:01:04.720 --> 00:01:06.149 align:start position:0% content distribution Network for uh for the<00:01:04.839> ethereum 00:01:06.149 --> 00:01:06.159 align:start position:0% the ethereum 00:01:06.159 --> 00:01:09.789 align:start position:0% the ethereum ecosystem<00:01:07.159> uh<00:01:07.400> so<00:01:07.640> if<00:01:07.799> if<00:01:08.000> ethereum<00:01:08.640> VM<00:01:09.159> is<00:01:09.400> the 00:01:09.789 --> 00:01:09.799 align:start position:0% ecosystem uh so if if ethereum VM is the 00:01:09.799 --> 00:01:11.390 align:start position:0% ecosystem uh so if if ethereum VM is the is<00:01:09.920> the<00:01:10.040> word<00:01:10.320> computer<00:01:10.759> then<00:01:10.920> you<00:01:11.000> can<00:01:11.159> say 00:01:11.390 --> 00:01:11.400 align:start position:0% is the word computer then you can say 00:01:11.400 --> 00:01:14.510 align:start position:0% is the word computer then you can say that<00:01:11.520> swarm<00:01:12.159> could<00:01:12.720> be<00:01:13.720> the<00:01:13.920> the<00:01:14.040> word<00:01:14.320> hard 00:01:14.510 --> 00:01:14.520 align:start position:0% that swarm could be the the word hard 00:01:14.520 --> 00:01:16.350 align:start position:0% that swarm could be the the word hard drive<00:01:14.759> or<00:01:15.040> a<00:01:15.280> word<00:01:15.560> hard<00:01:15.720> drive<00:01:16.000> because<00:01:16.200> there 00:01:16.350 --> 00:01:16.360 align:start position:0% drive or a word hard drive because there 00:01:16.360 --> 00:01:17.990 align:start position:0% drive or a word hard drive because there might<00:01:16.520> be<00:01:16.680> alternatives<00:01:17.320> to<00:01:17.600> to<00:01:17.759> this 00:01:17.990 --> 00:01:18.000 align:start position:0% might be alternatives to to this 00:01:18.000 --> 00:01:20.789 align:start position:0% might be alternatives to to this solution<00:01:19.000> so<00:01:19.520> on<00:01:19.720> on<00:01:19.840> the<00:01:19.960> other<00:01:20.159> hand<00:01:20.439> like 00:01:20.789 --> 00:01:20.799 align:start position:0% solution so on on the other hand like 00:01:20.799 --> 00:01:23.190 align:start position:0% solution so on on the other hand like what<00:01:21.000> else<00:01:21.600> is<00:01:21.759> is<00:01:21.880> a<00:01:22.040> swarm<00:01:22.400> I<00:01:22.479> mean<00:01:22.840> you<00:01:23.000> can 00:01:23.190 --> 00:01:23.200 align:start position:0% what else is is a swarm I mean you can 00:01:23.200 --> 00:01:26.109 align:start position:0% what else is is a swarm I mean you can you<00:01:23.720> can<00:01:24.720> can<00:01:24.880> just<00:01:25.079> imagine<00:01:25.400> an<00:01:25.640> imaginary 00:01:26.109 --> 00:01:26.119 align:start position:0% you can can just imagine an imaginary 00:01:26.119 --> 00:01:27.870 align:start position:0% you can can just imagine an imaginary swarm<00:01:26.560> where<00:01:26.799> like<00:01:27.360> the<00:01:27.520> the<00:01:27.640> happy 00:01:27.870 --> 00:01:27.880 align:start position:0% swarm where like the the happy 00:01:27.880 --> 00:01:30.749 align:start position:0% swarm where like the the happy beekeepers<00:01:28.600> like<00:01:28.759> sit<00:01:29.040> behind<00:01:29.360> their<00:01:30.360> hives 00:01:30.749 --> 00:01:30.759 align:start position:0% beekeepers like sit behind their hives 00:01:30.759 --> 00:01:32.789 align:start position:0% beekeepers like sit behind their hives and<00:01:30.960> and<00:01:31.079> look<00:01:31.240> at<00:01:31.439> their 00:01:32.789 --> 00:01:32.799 align:start position:0% and and look at their 00:01:32.799 --> 00:01:35.550 align:start position:0% and and look at their fantastic<00:01:33.799> product<00:01:34.200> of<00:01:34.399> the<00:01:34.600> from<00:01:34.759> the<00:01:34.920> bees 00:01:35.550 --> 00:01:35.560 align:start position:0% fantastic product of the from the bees 00:01:35.560 --> 00:01:38.190 align:start position:0% fantastic product of the from the bees and<00:01:35.759> just<00:01:36.640> happy<00:01:36.880> happy<00:01:37.240> to<00:01:37.399> have<00:01:37.600> their<00:01:37.920> honey 00:01:38.190 --> 00:01:38.200 align:start position:0% and just happy happy to have their honey 00:01:38.200 --> 00:01:40.429 align:start position:0% and just happy happy to have their honey harvested<00:01:38.680> from<00:01:38.880> The<00:01:39.040> Beehive<00:01:39.880> you<00:01:40.000> can<00:01:40.159> also 00:01:40.429 --> 00:01:40.439 align:start position:0% harvested from The Beehive you can also 00:01:40.439 --> 00:01:42.630 align:start position:0% harvested from The Beehive you can also look<00:01:40.600> at<00:01:40.960> the<00:01:41.040> Beehive<00:01:41.439> as<00:01:41.680> this<00:01:42.040> lovely 00:01:42.630 --> 00:01:42.640 align:start position:0% look at the Beehive as this lovely 00:01:42.640 --> 00:01:46.789 align:start position:0% look at the Beehive as this lovely repository<00:01:43.280> of<00:01:44.159> uh<00:01:45.159> honey<00:01:45.520> where<00:01:45.680> all<00:01:45.920> is<00:01:46.119> like 00:01:46.789 --> 00:01:46.799 align:start position:0% repository of uh honey where all is like 00:01:46.799 --> 00:01:49.590 align:start position:0% repository of uh honey where all is like drops<00:01:47.119> of<00:01:47.240> Honey<00:01:47.520> are<00:01:47.680> stored<00:01:48.520> and<00:01:48.880> also<00:01:49.200> look 00:01:49.590 --> 00:01:49.600 align:start position:0% drops of Honey are stored and also look 00:01:49.600 --> 00:01:51.870 align:start position:0% drops of Honey are stored and also look you<00:01:49.680> can<00:01:49.840> look<00:01:50.000> at<00:01:50.240> that<00:01:50.719> um<00:01:50.960> swarm<00:01:51.520> and<00:01:51.719> and 00:01:51.870 --> 00:01:51.880 align:start position:0% you can look at that um swarm and and 00:01:51.880 --> 00:01:55.910 align:start position:0% you can look at that um swarm and and see<00:01:52.360> the<00:01:53.520> the<00:01:54.520> buzzing<00:01:54.920> swarm<00:01:55.280> of<00:01:55.439> bees<00:01:55.719> just 00:01:55.910 --> 00:01:55.920 align:start position:0% see the the buzzing swarm of bees just 00:01:55.920 --> 00:01:57.709 align:start position:0% see the the buzzing swarm of bees just communicating<00:01:56.600> with<00:01:56.799> each<00:01:56.960> other<00:01:57.479> I<00:01:57.560> don't 00:01:57.709 --> 00:01:57.719 align:start position:0% communicating with each other I don't 00:01:57.719 --> 00:01:59.310 align:start position:0% communicating with each other I don't know<00:01:57.880> how<00:01:58.039> you<00:01:58.159> are<00:01:58.399> but<00:01:58.560> like<00:01:58.680> for<00:01:58.840> me<00:01:59.159> it 00:01:59.310 --> 00:01:59.320 align:start position:0% know how you are but like for me it 00:01:59.320 --> 00:02:02.029 align:start position:0% know how you are but like for me it obviously<00:01:59.920> reminds<00:02:00.200> me<00:02:00.399> of<00:02:00.640> of<00:02:00.840> of<00:02:00.960> a<00:02:01.079> network 00:02:02.029 --> 00:02:02.039 align:start position:0% obviously reminds me of of of a network 00:02:02.039 --> 00:02:03.709 align:start position:0% obviously reminds me of of of a network protocol<00:02:02.600> and<00:02:02.799> like<00:02:03.039> all<00:02:03.240> the<00:02:03.360> network 00:02:03.709 --> 00:02:03.719 align:start position:0% protocol and like all the network 00:02:03.719 --> 00:02:06.590 align:start position:0% protocol and like all the network messages<00:02:04.119> I<00:02:04.320> sent<00:02:04.640> around<00:02:05.479> so<00:02:06.240> let's<00:02:06.439> let's 00:02:06.590 --> 00:02:06.600 align:start position:0% messages I sent around so let's let's 00:02:06.600 --> 00:02:09.830 align:start position:0% messages I sent around so let's let's concentrate<00:02:07.079> on<00:02:07.280> these<00:02:07.479> three<00:02:07.719> aspects<00:02:08.679> so<00:02:09.679> uh 00:02:09.830 --> 00:02:09.840 align:start position:0% concentrate on these three aspects so uh 00:02:09.840 --> 00:02:11.830 align:start position:0% concentrate on these three aspects so uh so<00:02:10.360> just<00:02:10.640> go<00:02:11.039> go 00:02:11.830 --> 00:02:11.840 align:start position:0% so just go go 00:02:11.840 --> 00:02:16.190 align:start position:0% so just go go back<00:02:12.840> so<00:02:13.400> uh<00:02:13.520> so<00:02:13.800> so<00:02:14.000> first<00:02:14.200> of<00:02:14.360> all<00:02:14.800> um<00:02:15.680> as<00:02:16.000> as 00:02:16.190 --> 00:02:16.200 align:start position:0% back so uh so so first of all um as as 00:02:16.200 --> 00:02:18.710 align:start position:0% back so uh so so first of all um as as as<00:02:16.319> a<00:02:16.480> service<00:02:17.400> what<00:02:17.599> what<00:02:17.720> swarm<00:02:18.120> provides<00:02:18.519> is 00:02:18.710 --> 00:02:18.720 align:start position:0% as a service what what swarm provides is 00:02:18.720 --> 00:02:22.589 align:start position:0% as a service what what swarm provides is basically<00:02:19.680> it<00:02:20.120> it<00:02:20.879> allows<00:02:21.319> to<00:02:21.640> to<00:02:21.800> store<00:02:22.239> the 00:02:22.589 --> 00:02:22.599 align:start position:0% basically it it allows to to store the 00:02:22.599 --> 00:02:24.150 align:start position:0% basically it it allows to to store the the<00:02:22.840> the<00:02:23.000> ethereum<00:02:23.480> depths<00:02:23.920> the 00:02:24.150 --> 00:02:24.160 align:start position:0% the the ethereum depths the 00:02:24.160 --> 00:02:26.550 align:start position:0% the the ethereum depths the decentralized<00:02:24.879> applications<00:02:25.879> and<00:02:26.040> also<00:02:26.400> kind 00:02:26.550 --> 00:02:26.560 align:start position:0% decentralized applications and also kind 00:02:26.560 --> 00:02:30.270 align:start position:0% decentralized applications and also kind of<00:02:26.800> offchain<00:02:28.080> uh<00:02:29.080> data<00:02:29.640> that<00:02:30.080> that's 00:02:30.270 --> 00:02:30.280 align:start position:0% of offchain uh data that that's 00:02:30.280 --> 00:02:33.229 align:start position:0% of offchain uh data that that's important<00:02:30.720> for<00:02:30.920> example<00:02:31.760> contract<00:02:32.760> um 00:02:33.229 --> 00:02:33.239 align:start position:0% important for example contract um 00:02:33.239 --> 00:02:35.430 align:start position:0% important for example contract um sources<00:02:33.680> or<00:02:33.879> like<00:02:34.080> registry<00:02:34.560> indexes<00:02:35.280> all 00:02:35.430 --> 00:02:35.440 align:start position:0% sources or like registry indexes all 00:02:35.440 --> 00:02:36.990 align:start position:0% sources or like registry indexes all kinds<00:02:35.599> of<00:02:35.760> things<00:02:36.000> which<00:02:36.319> need<00:02:36.440> to<00:02:36.760> people 00:02:36.990 --> 00:02:37.000 align:start position:0% kinds of things which need to people 00:02:37.000 --> 00:02:39.229 align:start position:0% kinds of things which need to people need<00:02:37.160> to<00:02:37.280> store<00:02:38.000> and<00:02:38.599> what<00:02:38.800> what<00:02:38.920> they<00:02:39.040> want 00:02:39.229 --> 00:02:39.239 align:start position:0% need to store and what what they want 00:02:39.239 --> 00:02:41.229 align:start position:0% need to store and what what they want for<00:02:39.480> that<00:02:39.680> like<00:02:39.840> users<00:02:40.280> want<00:02:40.680> want<00:02:40.879> to<00:02:41.000> keep 00:02:41.229 --> 00:02:41.239 align:start position:0% for that like users want want to keep 00:02:41.239 --> 00:02:44.110 align:start position:0% for that like users want want to keep this<00:02:41.720> uh<00:02:41.840> record<00:02:42.280> safe<00:02:43.080> and<00:02:43.440> in<00:02:43.599> general<00:02:43.959> you 00:02:44.110 --> 00:02:44.120 align:start position:0% this uh record safe and in general you 00:02:44.120 --> 00:02:45.670 align:start position:0% this uh record safe and in general you want<00:02:44.280> they<00:02:44.360> want<00:02:44.599> Integrity<00:02:45.159> protection 00:02:45.670 --> 00:02:45.680 align:start position:0% want they want Integrity protection 00:02:45.680 --> 00:02:48.509 align:start position:0% want they want Integrity protection always<00:02:46.239> availability<00:02:47.239> like<00:02:47.720> basically<00:02:48.159> zero 00:02:48.509 --> 00:02:48.519 align:start position:0% always availability like basically zero 00:02:48.519 --> 00:02:50.670 align:start position:0% always availability like basically zero downtime<00:02:49.080> for<00:02:49.440> tolerance<00:02:50.120> all<00:02:50.280> these<00:02:50.480> nice 00:02:50.670 --> 00:02:50.680 align:start position:0% downtime for tolerance all these nice 00:02:50.680 --> 00:02:51.630 align:start position:0% downtime for tolerance all these nice things<00:02:50.879> that<00:02:51.000> you<00:02:51.120> want<00:02:51.319> from<00:02:51.480> a 00:02:51.630 --> 00:02:51.640 align:start position:0% things that you want from a 00:02:51.640 --> 00:02:55.190 align:start position:0% things that you want from a decentralized<00:02:52.360> solution<00:02:52.879> in<00:02:53.280> general<00:02:54.280> U<00:02:54.720> and 00:02:55.190 --> 00:02:55.200 align:start position:0% decentralized solution in general U and 00:02:55.200 --> 00:02:56.670 align:start position:0% decentralized solution in general U and one<00:02:55.360> important<00:02:55.720> message<00:02:56.000> to<00:02:56.159> take<00:02:56.319> away<00:02:56.519> from 00:02:56.670 --> 00:02:56.680 align:start position:0% one important message to take away from 00:02:56.680 --> 00:02:58.589 align:start position:0% one important message to take away from this<00:02:56.920> and<00:02:57.480> they<00:02:57.560> are<00:02:57.680> willing<00:02:57.959> to<00:02:58.159> pay<00:02:58.319> for 00:02:58.589 --> 00:02:58.599 align:start position:0% this and they are willing to pay for 00:02:58.599 --> 00:03:00.990 align:start position:0% this and they are willing to pay for this<00:02:58.920> in<00:02:59.040> a<00:02:59.200> way<00:02:59.519> like<00:03:00.120> the<00:03:00.280> enence<00:03:00.680> is<00:03:00.879> there 00:03:00.990 --> 00:03:01.000 align:start position:0% this in a way like the enence is there 00:03:01.000 --> 00:03:03.110 align:start position:0% this in a way like the enence is there for<00:03:01.200> you<00:03:01.400> like<00:03:01.560> the<00:03:01.680> user<00:03:02.080> is<00:03:02.560> wants<00:03:02.840> to<00:03:03.000> have 00:03:03.110 --> 00:03:03.120 align:start position:0% for you like the user is wants to have 00:03:03.120 --> 00:03:05.589 align:start position:0% for you like the user is wants to have the<00:03:03.280> contract<00:03:03.799> ret<00:03:04.560> the<00:03:04.799> the<00:03:05.080> content 00:03:05.589 --> 00:03:05.599 align:start position:0% the contract ret the the content 00:03:05.599 --> 00:03:08.990 align:start position:0% the contract ret the the content retrieved<00:03:06.599> and<00:03:07.319> that's<00:03:07.519> that's<00:03:07.680> an<00:03:08.000> incentive 00:03:08.990 --> 00:03:09.000 align:start position:0% retrieved and that's that's an incentive 00:03:09.000 --> 00:03:11.229 align:start position:0% retrieved and that's that's an incentive so 00:03:11.229 --> 00:03:11.239 align:start position:0% so 00:03:11.239 --> 00:03:14.470 align:start position:0% so uh<00:03:12.239> what<00:03:12.519> how<00:03:12.720> we<00:03:13.000> how<00:03:13.120> we<00:03:13.319> solve<00:03:14.000> uh<00:03:14.239> this 00:03:14.470 --> 00:03:14.480 align:start position:0% uh what how we how we solve uh this 00:03:14.480 --> 00:03:16.309 align:start position:0% uh what how we how we solve uh this problem<00:03:14.840> is<00:03:15.120> is<00:03:15.239> an<00:03:15.400> interesting<00:03:16.000> you<00:03:16.120> can 00:03:16.309 --> 00:03:16.319 align:start position:0% problem is is an interesting you can 00:03:16.319 --> 00:03:19.110 align:start position:0% problem is is an interesting you can reduce<00:03:16.840> this<00:03:17.080> problem<00:03:17.319> of<00:03:17.519> file<00:03:17.959> file<00:03:18.200> storage 00:03:19.110 --> 00:03:19.120 align:start position:0% reduce this problem of file file storage 00:03:19.120 --> 00:03:23.350 align:start position:0% reduce this problem of file file storage and<00:03:19.319> basically<00:03:19.760> hosting<00:03:20.599> to<00:03:21.360> uh<00:03:22.000> to<00:03:22.319> to<00:03:22.599> to<00:03:23.200> to 00:03:23.350 --> 00:03:23.360 align:start position:0% and basically hosting to uh to to to to 00:03:23.360 --> 00:03:25.430 align:start position:0% and basically hosting to uh to to to to resolving<00:03:23.959> the<00:03:24.159> problem<00:03:24.560> of<00:03:24.840> of<00:03:24.959> storing 00:03:25.430 --> 00:03:25.440 align:start position:0% resolving the problem of of storing 00:03:25.440 --> 00:03:28.149 align:start position:0% resolving the problem of of storing fixed<00:03:26.159> size<00:03:26.440> chunks<00:03:27.000> in<00:03:27.120> a<00:03:27.280> decentralized 00:03:28.149 --> 00:03:28.159 align:start position:0% fixed size chunks in a decentralized 00:03:28.159 --> 00:03:30.429 align:start position:0% fixed size chunks in a decentralized system<00:03:28.840> how<00:03:29.040> how<00:03:29.200> is<00:03:29.319> that<00:03:29.480> working<00:03:30.080> basically 00:03:30.429 --> 00:03:30.439 align:start position:0% system how how is that working basically 00:03:30.439 --> 00:03:32.670 align:start position:0% system how how is that working basically on<00:03:30.560> the<00:03:30.680> file<00:03:30.959> level<00:03:31.159> or<00:03:31.439> document<00:03:31.879> level<00:03:32.519> you 00:03:32.670 --> 00:03:32.680 align:start position:0% on the file level or document level you 00:03:32.680 --> 00:03:34.869 align:start position:0% on the file level or document level you can<00:03:32.920> think<00:03:33.159> of<00:03:33.480> the<00:03:33.760> the<00:03:34.040> you<00:03:34.159> can<00:03:34.439> basically 00:03:34.869 --> 00:03:34.879 align:start position:0% can think of the the you can basically 00:03:34.879 --> 00:03:36.869 align:start position:0% can think of the the you can basically chop<00:03:35.200> chop<00:03:35.480> up<00:03:35.680> the<00:03:35.799> files<00:03:36.080> into<00:03:36.319> small<00:03:36.599> little 00:03:36.869 --> 00:03:36.879 align:start position:0% chop chop up the files into small little 00:03:36.879 --> 00:03:39.990 align:start position:0% chop chop up the files into small little pieces<00:03:37.439> rearrange<00:03:38.040> them<00:03:38.159> in<00:03:38.280> a<00:03:38.439> nice<00:03:38.760> Merk<00:03:39.280> try 00:03:39.990 --> 00:03:40.000 align:start position:0% pieces rearrange them in a nice Merk try 00:03:40.000 --> 00:03:42.390 align:start position:0% pieces rearrange them in a nice Merk try this<00:03:40.080> is<00:03:40.239> not<00:03:40.400> a<00:03:40.640> swear<00:03:41.000> word<00:03:41.200> in<00:03:41.400> this<00:03:42.040> company 00:03:42.390 --> 00:03:42.400 align:start position:0% this is not a swear word in this company 00:03:42.400 --> 00:03:43.830 align:start position:0% this is not a swear word in this company of<00:03:42.560> people<00:03:42.840> I<00:03:42.879> mean<00:03:43.040> you<00:03:43.159> all<00:03:43.319> know<00:03:43.560> like<00:03:43.720> the 00:03:43.830 --> 00:03:43.840 align:start position:0% of people I mean you all know like the 00:03:43.840 --> 00:03:45.750 align:start position:0% of people I mean you all know like the ethereum<00:03:44.519> works<00:03:44.720> in<00:03:44.879> the<00:03:45.000> same<00:03:45.239> way<00:03:45.599> the 00:03:45.750 --> 00:03:45.760 align:start position:0% ethereum works in the same way the 00:03:45.760 --> 00:03:48.350 align:start position:0% ethereum works in the same way the ethereum<00:03:46.239> state<00:03:46.560> for<00:03:46.720> the<00:03:46.879> Patricia<00:03:47.360> try<00:03:48.159> and 00:03:48.350 --> 00:03:48.360 align:start position:0% ethereum state for the Patricia try and 00:03:48.360 --> 00:03:51.190 align:start position:0% ethereum state for the Patricia try and what<00:03:48.480> you<00:03:48.599> end<00:03:48.799> up<00:03:48.959> with<00:03:49.159> this<00:03:49.640> uh<00:03:49.879> with<00:03:50.200> this 00:03:51.190 --> 00:03:51.200 align:start position:0% what you end up with this uh with this 00:03:51.200 --> 00:03:53.390 align:start position:0% what you end up with this uh with this merker<00:03:51.680> try<00:03:52.200> is<00:03:52.360> that<00:03:52.519> you<00:03:52.640> can<00:03:52.799> have<00:03:53.000> like<00:03:53.120> a 00:03:53.390 --> 00:03:53.400 align:start position:0% merker try is that you can have like a 00:03:53.400 --> 00:03:56.869 align:start position:0% merker try is that you can have like a random<00:03:53.879> access<00:03:54.799> partial<00:03:55.239> read<00:03:55.959> of<00:03:56.159> a<00:03:56.519> into<00:03:56.760> a 00:03:56.869 --> 00:03:56.879 align:start position:0% random access partial read of a into a 00:03:56.879 --> 00:03:58.910 align:start position:0% random access partial read of a into a file<00:03:57.319> with<00:03:57.519> still<00:03:57.799> preserving<00:03:58.360> the<00:03:58.760> the 00:03:58.910 --> 00:03:58.920 align:start position:0% file with still preserving the the 00:03:58.920 --> 00:04:00.270 align:start position:0% file with still preserving the the integrity 00:04:00.270 --> 00:04:00.280 align:start position:0% integrity 00:04:00.280 --> 00:04:02.990 align:start position:0% integrity and<00:04:01.040> you<00:04:01.159> can<00:04:01.360> you<00:04:01.480> can<00:04:01.640> do<00:04:01.799> it<00:04:02.319> you<00:04:02.480> can<00:04:02.799> do 00:04:02.990 --> 00:04:03.000 align:start position:0% and you can you can do it you can do 00:04:03.000 --> 00:04:04.830 align:start position:0% and you can you can do it you can do this<00:04:03.200> like<00:04:03.360> one<00:04:03.599> step<00:04:03.879> further<00:04:04.239> and<00:04:04.400> say<00:04:04.680> that 00:04:04.830 --> 00:04:04.840 align:start position:0% this like one step further and say that 00:04:04.840 --> 00:04:06.910 align:start position:0% this like one step further and say that you<00:04:04.959> don't<00:04:05.599> you<00:04:05.760> you<00:04:05.879> can<00:04:06.120> not<00:04:06.280> only<00:04:06.480> handle 00:04:06.910 --> 00:04:06.920 align:start position:0% you don't you you can not only handle 00:04:06.920 --> 00:04:09.429 align:start position:0% you don't you you can not only handle like<00:04:07.920> documents<00:04:08.439> but<00:04:08.680> also<00:04:09.000> document 00:04:09.429 --> 00:04:09.439 align:start position:0% like documents but also document 00:04:09.439 --> 00:04:12.350 align:start position:0% like documents but also document collections<00:04:10.079> so<00:04:10.280> another<00:04:10.599> level<00:04:10.840> of<00:04:11.360> indexing 00:04:12.350 --> 00:04:12.360 align:start position:0% collections so another level of indexing 00:04:12.360 --> 00:04:14.949 align:start position:0% collections so another level of indexing which<00:04:12.480> is<00:04:13.439> kind<00:04:13.560> of<00:04:14.000> similar<00:04:14.400> structure<00:04:14.799> you 00:04:14.949 --> 00:04:14.959 align:start position:0% which is kind of similar structure you 00:04:14.959 --> 00:04:18.069 align:start position:0% which is kind of similar structure you call<00:04:15.159> them<00:04:15.560> you<00:04:15.760> call<00:04:15.879> it<00:04:16.000> the<00:04:16.440> Manifest<00:04:17.440> and 00:04:18.069 --> 00:04:18.079 align:start position:0% call them you call it the Manifest and 00:04:18.079 --> 00:04:21.830 align:start position:0% call them you call it the Manifest and this<00:04:18.320> also<00:04:18.840> allows<00:04:19.680> to<00:04:19.919> index<00:04:20.519> but<00:04:21.400> as<00:04:21.519> opposed 00:04:21.830 --> 00:04:21.840 align:start position:0% this also allows to index but as opposed 00:04:21.840 --> 00:04:24.749 align:start position:0% this also allows to index but as opposed to<00:04:22.000> the<00:04:22.400> previous<00:04:22.720> Merk<00:04:23.160> TR<00:04:23.759> the<00:04:24.000> the<00:04:24.160> parts<00:04:24.440> of 00:04:24.749 --> 00:04:24.759 align:start position:0% to the previous Merk TR the the parts of 00:04:24.759 --> 00:04:27.550 align:start position:0% to the previous Merk TR the the parts of the<00:04:25.320> the<00:04:26.240> the<00:04:26.360> document<00:04:26.759> collection 00:04:27.550 --> 00:04:27.560 align:start position:0% the the the document collection 00:04:27.560 --> 00:04:30.629 align:start position:0% the the the document collection obviously<00:04:28.120> artific<00:04:29.000> arbitrary<00:04:29.440> Lang<00:04:29.720> length 00:04:30.629 --> 00:04:30.639 align:start position:0% obviously artific arbitrary Lang length 00:04:30.639 --> 00:04:35.110 align:start position:0% obviously artific arbitrary Lang length and<00:04:31.600> the<00:04:31.840> the<00:04:31.960> indexes<00:04:32.520> are<00:04:32.880> are<00:04:33.840> just<00:04:34.120> pass<00:04:34.840> so 00:04:35.110 --> 00:04:35.120 align:start position:0% and the the indexes are are just pass so 00:04:35.120 --> 00:04:37.150 align:start position:0% and the the indexes are are just pass so this<00:04:35.280> means<00:04:35.639> that<00:04:35.919> if<00:04:36.160> if<00:04:36.280> you<00:04:36.440> have<00:04:36.560> a<00:04:36.720> root<00:04:37.000> of 00:04:37.150 --> 00:04:37.160 align:start position:0% this means that if if you have a root of 00:04:37.160 --> 00:04:39.909 align:start position:0% this means that if if you have a root of a<00:04:37.360> of<00:04:37.440> a<00:04:37.680> manifest<00:04:38.680> like<00:04:38.960> this<00:04:39.199> this<00:04:39.360> chunk 00:04:39.909 --> 00:04:39.919 align:start position:0% a of a manifest like this this chunk 00:04:39.919 --> 00:04:41.749 align:start position:0% a of a manifest like this this chunk then<00:04:40.080> basically<00:04:40.520> they<00:04:40.639> can<00:04:40.840> represent<00:04:41.360> entry 00:04:41.749 --> 00:04:41.759 align:start position:0% then basically they can represent entry 00:04:41.759 --> 00:04:44.110 align:start position:0% then basically they can represent entry points<00:04:42.160> to<00:04:42.520> uh<00:04:42.759> to<00:04:43.000> to<00:04:43.160> the<00:04:43.280> to<00:04:43.400> the<00:04:43.520> web<00:04:43.800> so 00:04:44.110 --> 00:04:44.120 align:start position:0% points to uh to to the to the web so 00:04:44.120 --> 00:04:45.790 align:start position:0% points to uh to to the to the web so basically<00:04:44.520> they<00:04:44.639> can<00:04:44.800> be<00:04:44.960> thought<00:04:45.199> of<00:04:45.360> as 00:04:45.790 --> 00:04:45.800 align:start position:0% basically they can be thought of as 00:04:45.800 --> 00:04:48.469 align:start position:0% basically they can be thought of as hosts<00:04:46.759> because<00:04:47.120> the<00:04:47.400> because<00:04:47.600> the<00:04:47.759> Manifest 00:04:48.469 --> 00:04:48.479 align:start position:0% hosts because the because the Manifest 00:04:48.479 --> 00:04:51.310 align:start position:0% hosts because the because the Manifest is<00:04:48.960> basically<00:04:49.479> the<00:04:50.039> uh<00:04:50.759> constitutes<00:04:51.240> the 00:04:51.310 --> 00:04:51.320 align:start position:0% is basically the uh constitutes the 00:04:51.320 --> 00:04:53.550 align:start position:0% is basically the uh constitutes the rooting<00:04:51.720> table<00:04:52.080> for<00:04:52.360> that<00:04:52.560> for<00:04:52.759> that<00:04:52.919> host<00:04:53.320> so 00:04:53.550 --> 00:04:53.560 align:start position:0% rooting table for that for that host so 00:04:53.560 --> 00:04:56.990 align:start position:0% rooting table for that for that host so basically<00:04:53.960> you<00:04:54.080> can<00:04:54.199> use<00:04:54.479> these<00:04:54.639> chunks<00:04:55.560> as<00:04:56.560> as 00:04:56.990 --> 00:04:57.000 align:start position:0% basically you can use these chunks as as 00:04:57.000 --> 00:04:59.710 align:start position:0% basically you can use these chunks as as representing<00:04:57.680> or<00:04:57.840> or<00:04:58.000> mimicking<00:04:58.639> a<00:04:59.120> a<00:04:59.240> web<00:04:59.440> CER 00:04:59.710 --> 00:04:59.720 align:start position:0% representing or or mimicking a a web CER 00:04:59.720 --> 00:05:01.590 align:start position:0% representing or or mimicking a a web CER Ser<00:05:00.199> so<00:05:00.400> this<00:05:00.520> is<00:05:00.680> how<00:05:00.800> you<00:05:00.960> how<00:05:01.080> you<00:05:01.199> make<00:05:01.479> like 00:05:01.590 --> 00:05:01.600 align:start position:0% Ser so this is how you how you make like 00:05:01.600 --> 00:05:05.430 align:start position:0% Ser so this is how you how you make like a<00:05:02.560> decentralized<00:05:03.560> server<00:05:04.039> from<00:05:04.320> from<00:05:04.479> swarm 00:05:05.430 --> 00:05:05.440 align:start position:0% a decentralized server from from swarm 00:05:05.440 --> 00:05:07.310 align:start position:0% a decentralized server from from swarm now<00:05:05.600> so<00:05:06.080> basically<00:05:06.400> the<00:05:06.520> message<00:05:06.840> is<00:05:07.039> here 00:05:07.310 --> 00:05:07.320 align:start position:0% now so basically the message is here 00:05:07.320 --> 00:05:10.029 align:start position:0% now so basically the message is here that<00:05:08.120> uh<00:05:08.520> we<00:05:08.680> we<00:05:08.840> reduce<00:05:09.160> the<00:05:09.360> problem<00:05:09.600> to<00:05:09.800> a<00:05:09.919> to 00:05:10.029 --> 00:05:10.039 align:start position:0% that uh we we reduce the problem to a to 00:05:10.039 --> 00:05:13.150 align:start position:0% that uh we we reduce the problem to a to a<00:05:10.120> chunk<00:05:10.440> store<00:05:11.400> and<00:05:11.800> we<00:05:12.120> associate<00:05:12.880> each 00:05:13.150 --> 00:05:13.160 align:start position:0% a chunk store and we associate each 00:05:13.160 --> 00:05:16.029 align:start position:0% a chunk store and we associate each chunk<00:05:13.880> with<00:05:14.080> a<00:05:14.680> with<00:05:14.880> with<00:05:15.000> a<00:05:15.160> with<00:05:15.280> a<00:05:15.400> hash 00:05:16.029 --> 00:05:16.039 align:start position:0% chunk with a with with a with a hash 00:05:16.039 --> 00:05:19.710 align:start position:0% chunk with a with with a with a hash hash<00:05:16.320> of<00:05:16.600> the<00:05:17.120> like<00:05:17.560> the<00:05:17.880> hash<00:05:18.160> of<00:05:18.319> the<00:05:18.720> content 00:05:19.710 --> 00:05:19.720 align:start position:0% hash of the like the hash of the content 00:05:19.720 --> 00:05:22.309 align:start position:0% hash of the like the hash of the content which<00:05:19.880> means<00:05:20.319> that<00:05:20.960> we<00:05:21.120> we<00:05:21.240> have<00:05:21.360> to<00:05:21.520> look<00:05:21.720> up 00:05:22.309 --> 00:05:22.319 align:start position:0% which means that we we have to look up 00:05:22.319 --> 00:05:25.309 align:start position:0% which means that we we have to look up them<00:05:22.600> based<00:05:22.840> on<00:05:23.039> these<00:05:23.240> keys<00:05:24.199> so<00:05:24.960> what<00:05:25.120> what<00:05:25.240> do 00:05:25.309 --> 00:05:25.319 align:start position:0% them based on these keys so what what do 00:05:25.319 --> 00:05:26.749 align:start position:0% them based on these keys so what what do you<00:05:25.479> actually<00:05:25.680> store<00:05:26.080> let's<00:05:26.319> let's<00:05:26.440> look<00:05:26.600> at 00:05:26.749 --> 00:05:26.759 align:start position:0% you actually store let's let's look at 00:05:26.759 --> 00:05:28.510 align:start position:0% you actually store let's let's look at the<00:05:26.880> other<00:05:27.160> aspect<00:05:27.479> of<00:05:27.680> the<00:05:27.880> of<00:05:27.960> the<00:05:28.080> highligh 00:05:28.510 --> 00:05:28.520 align:start position:0% the other aspect of the of the highligh 00:05:28.520 --> 00:05:31.870 align:start position:0% the other aspect of the of the highligh the<00:05:28.639> store<00:05:29.199> so<00:05:29.680> each<00:05:29.800> note<00:05:30.120> has<00:05:30.240> a<00:05:30.560> has<00:05:30.880> a 00:05:31.870 --> 00:05:31.880 align:start position:0% the store so each note has a has a 00:05:31.880 --> 00:05:34.150 align:start position:0% the store so each note has a has a memory<00:05:32.240> store<00:05:33.000> and<00:05:33.360> and<00:05:33.479> the<00:05:33.680> and<00:05:33.759> the<00:05:33.880> dis 00:05:34.150 --> 00:05:34.160 align:start position:0% memory store and and the and the dis 00:05:34.160 --> 00:05:35.550 align:start position:0% memory store and and the and the dis storage<00:05:34.560> so<00:05:34.720> basically<00:05:35.120> these<00:05:35.240> are<00:05:35.400> the 00:05:35.550 --> 00:05:35.560 align:start position:0% storage so basically these are the 00:05:35.560 --> 00:05:39.590 align:start position:0% storage so basically these are the caching<00:05:36.199> that<00:05:37.000> the<00:05:37.120> the<00:05:37.240> note<00:05:37.520> can<00:05:37.720> look<00:05:37.919> up<00:05:38.479> uh 00:05:39.590 --> 00:05:39.600 align:start position:0% caching that the the note can look up uh 00:05:39.600 --> 00:05:42.629 align:start position:0% caching that the the note can look up uh locally<00:05:40.600> but<00:05:41.120> eventually<00:05:41.759> like<00:05:42.479> there's 00:05:42.629 --> 00:05:42.639 align:start position:0% locally but eventually like there's 00:05:42.639 --> 00:05:44.270 align:start position:0% locally but eventually like there's going<00:05:42.720> to<00:05:42.840> be<00:05:42.960> a<00:05:43.120> situation<00:05:43.680> where<00:05:43.960> you<00:05:44.160> you 00:05:44.270 --> 00:05:44.280 align:start position:0% going to be a situation where you you 00:05:44.280 --> 00:05:45.790 align:start position:0% going to be a situation where you you can't<00:05:44.479> store<00:05:44.840> everything<00:05:45.199> so<00:05:45.360> you<00:05:45.479> have<00:05:45.680> to 00:05:45.790 --> 00:05:45.800 align:start position:0% can't store everything so you have to 00:05:45.800 --> 00:05:48.309 align:start position:0% can't store everything so you have to like<00:05:45.960> look<00:05:46.160> out<00:05:47.000> to<00:05:47.199> the<00:05:47.360> network<00:05:47.880> to<00:05:48.039> find 00:05:48.309 --> 00:05:48.319 align:start position:0% like look out to the network to find 00:05:48.319 --> 00:05:50.710 align:start position:0% like look out to the network to find something<00:05:48.919> because<00:05:49.280> the<00:05:49.720> the<00:05:49.880> the<00:05:50.000> neighbors 00:05:50.710 --> 00:05:50.720 align:start position:0% something because the the the neighbors 00:05:50.720 --> 00:05:52.629 align:start position:0% something because the the the neighbors the<00:05:50.840> neighbors<00:05:51.199> honey<00:05:51.479> is<00:05:51.600> always<00:05:51.840> sweeter 00:05:52.629 --> 00:05:52.639 align:start position:0% the neighbors honey is always sweeter 00:05:52.639 --> 00:05:56.430 align:start position:0% the neighbors honey is always sweeter anyway<00:05:53.440> so<00:05:54.360> uh<00:05:55.120> now<00:05:55.400> now<00:05:55.560> you<00:05:55.720> have<00:05:56.000> to<00:05:56.280> to 00:05:56.430 --> 00:05:56.440 align:start position:0% anyway so uh now now you have to to 00:05:56.440 --> 00:05:58.870 align:start position:0% anyway so uh now now you have to to solve<00:05:56.759> this<00:05:57.000> problem<00:05:57.360> of<00:05:57.560> of<00:05:57.759> how<00:05:58.240> how<00:05:58.400> you 00:05:58.870 --> 00:05:58.880 align:start position:0% solve this problem of of how how you 00:05:58.880 --> 00:06:00.430 align:start position:0% solve this problem of of how how you communicate 00:06:00.430 --> 00:06:00.440 align:start position:0% communicate 00:06:00.440 --> 00:06:02.510 align:start position:0% communicate your<00:06:00.600> needs<00:06:01.000> how<00:06:01.160> to<00:06:01.319> find<00:06:01.720> basically<00:06:02.240> these 00:06:02.510 --> 00:06:02.520 align:start position:0% your needs how to find basically these 00:06:02.520 --> 00:06:04.670 align:start position:0% your needs how to find basically these these<00:06:02.680> chunks<00:06:03.520> so<00:06:03.759> what<00:06:03.960> what<00:06:04.080> you<00:06:04.240> basically 00:06:04.670 --> 00:06:04.680 align:start position:0% these chunks so what what you basically 00:06:04.680 --> 00:06:08.950 align:start position:0% these chunks so what what you basically do<00:06:05.039> is<00:06:05.400> um<00:06:05.880> is<00:06:06.039> use<00:06:06.280> a<00:06:06.599> use<00:06:06.759> a<00:06:06.919> network<00:06:07.960> protocol 00:06:08.950 --> 00:06:08.960 align:start position:0% do is um is use a use a network protocol 00:06:08.960 --> 00:06:11.749 align:start position:0% do is um is use a use a network protocol and<00:06:09.560> uh<00:06:09.720> swarm<00:06:10.639> relies<00:06:11.120> heavily<00:06:11.440> on<00:06:11.599> the 00:06:11.749 --> 00:06:11.759 align:start position:0% and uh swarm relies heavily on the 00:06:11.759 --> 00:06:14.710 align:start position:0% and uh swarm relies heavily on the ethereum<00:06:12.759> network<00:06:13.479> which<00:06:13.599> is<00:06:13.880> basically<00:06:14.400> Alex 00:06:14.710 --> 00:06:14.720 align:start position:0% ethereum network which is basically Alex 00:06:14.720 --> 00:06:18.430 align:start position:0% ethereum network which is basically Alex lington<00:06:15.319> and<00:06:15.599> Felix<00:06:16.120> lung's<00:06:17.319> wonderful<00:06:18.319> you 00:06:18.430 --> 00:06:18.440 align:start position:0% lington and Felix lung's wonderful you 00:06:18.440 --> 00:06:21.150 align:start position:0% lington and Felix lung's wonderful you know<00:06:18.639> genius<00:06:19.120> product<00:06:20.000> it's<00:06:20.360> a<00:06:20.880> it's 00:06:21.150 --> 00:06:21.160 align:start position:0% know genius product it's a it's 00:06:21.160 --> 00:06:23.990 align:start position:0% know genius product it's a it's basically<00:06:22.039> a<00:06:23.039> the<00:06:23.160> death<00:06:23.440> beer<00:06:23.720> to-peer 00:06:23.990 --> 00:06:24.000 align:start position:0% basically a the death beer to-peer 00:06:24.000 --> 00:06:26.309 align:start position:0% basically a the death beer to-peer multiprotocol<00:06:25.000> Suite<00:06:25.680> I<00:06:25.759> don't<00:06:25.919> want<00:06:26.039> to<00:06:26.160> go 00:06:26.309 --> 00:06:26.319 align:start position:0% multiprotocol Suite I don't want to go 00:06:26.319 --> 00:06:28.150 align:start position:0% multiprotocol Suite I don't want to go into<00:06:26.520> the<00:06:26.639> details<00:06:27.120> just<00:06:27.520> refer<00:06:27.840> you<00:06:28.000> to 00:06:28.150 --> 00:06:28.160 align:start position:0% into the details just refer you to 00:06:28.160 --> 00:06:30.469 align:start position:0% into the details just refer you to Alex's<00:06:28.680> talk<00:06:28.919> on<00:06:29.319> like<00:06:29.599> I<00:06:29.680> think<00:06:29.840> it's 00:06:30.469 --> 00:06:30.479 align:start position:0% Alex's talk on like I think it's 00:06:30.479 --> 00:06:32.629 align:start position:0% Alex's talk on like I think it's Wednesday<00:06:30.880> morning<00:06:31.880> uh<00:06:32.039> the<00:06:32.319> the<00:06:32.400> most 00:06:32.629 --> 00:06:32.639 align:start position:0% Wednesday morning uh the the most 00:06:32.639 --> 00:06:34.909 align:start position:0% Wednesday morning uh the the most important<00:06:33.199> message<00:06:33.599> here<00:06:33.759> is<00:06:33.960> that<00:06:34.479> it<00:06:34.639> comes 00:06:34.909 --> 00:06:34.919 align:start position:0% important message here is that it comes 00:06:34.919 --> 00:06:37.029 align:start position:0% important message here is that it comes with<00:06:35.120> all<00:06:35.360> the<00:06:35.960> beautiful<00:06:36.440> security<00:06:36.880> and 00:06:37.029 --> 00:06:37.039 align:start position:0% with all the beautiful security and 00:06:37.039 --> 00:06:39.870 align:start position:0% with all the beautiful security and integrity<00:06:37.560> properties<00:06:38.000> of<00:06:38.199> this<00:06:38.800> network 00:06:39.870 --> 00:06:39.880 align:start position:0% integrity properties of this network 00:06:39.880 --> 00:06:42.870 align:start position:0% integrity properties of this network implementation<00:06:40.880> and<00:06:41.039> also<00:06:41.440> it<00:06:41.639> has<00:06:42.080> it<00:06:42.680> gives 00:06:42.870 --> 00:06:42.880 align:start position:0% implementation and also it has it gives 00:06:42.880 --> 00:06:45.230 align:start position:0% implementation and also it has it gives you<00:06:43.039> a<00:06:43.440> semi-permanent<00:06:44.440> uh<00:06:44.639> peer<00:06:44.919> pool 00:06:45.230 --> 00:06:45.240 align:start position:0% you a semi-permanent uh peer pool 00:06:45.240 --> 00:06:47.670 align:start position:0% you a semi-permanent uh peer pool basically<00:06:45.919> the<00:06:46.280> the<00:06:46.639> the<00:06:46.759> peers<00:06:47.080> that<00:06:47.240> you 00:06:47.670 --> 00:06:47.680 align:start position:0% basically the the the peers that you 00:06:47.680 --> 00:06:51.230 align:start position:0% basically the the the peers that you actively<00:06:48.039> connected<00:06:48.479> to<00:06:49.479> can<00:06:49.599> be<00:06:50.240> considered 00:06:51.230 --> 00:06:51.240 align:start position:0% actively connected to can be considered 00:06:51.240 --> 00:06:54.749 align:start position:0% actively connected to can be considered relatively<00:06:52.000> stable<00:06:53.000> and<00:06:53.360> also<00:06:53.800> the<00:06:54.039> network 00:06:54.749 --> 00:06:54.759 align:start position:0% relatively stable and also the network 00:06:54.759 --> 00:06:57.869 align:start position:0% relatively stable and also the network overlay<00:06:55.360> topology<00:06:56.199> is<00:06:56.400> is<00:06:56.560> flexible<00:06:57.160> so<00:06:57.680> all 00:06:57.869 --> 00:06:57.879 align:start position:0% overlay topology is is flexible so all 00:06:57.879 --> 00:07:01.350 align:start position:0% overlay topology is is flexible so all we<00:06:58.000> needed<00:06:58.319> to<00:06:58.440> do<00:06:58.599> for<00:06:58.879> swarm<00:06:59.680> is<00:07:00.360> basically 00:07:01.350 --> 00:07:01.360 align:start position:0% we needed to do for swarm is basically 00:07:01.360 --> 00:07:02.670 align:start position:0% we needed to do for swarm is basically use<00:07:01.759> use<00:07:01.879> a 00:07:02.670 --> 00:07:02.680 align:start position:0% use use a 00:07:02.680 --> 00:07:05.350 align:start position:0% use use a cademia<00:07:03.680> routing<00:07:04.039> table<00:07:04.639> cademia<00:07:05.120> Pier 00:07:05.350 --> 00:07:05.360 align:start position:0% cademia routing table cademia Pier 00:07:05.360 --> 00:07:08.390 align:start position:0% cademia routing table cademia Pier selection<00:07:06.039> mechanism<00:07:07.039> and<00:07:07.400> we<00:07:07.759> immediately 00:07:08.390 --> 00:07:08.400 align:start position:0% selection mechanism and we immediately 00:07:08.400 --> 00:07:11.790 align:start position:0% selection mechanism and we immediately had<00:07:08.639> like<00:07:08.840> a<00:07:09.160> a<00:07:09.360> key<00:07:09.639> based<00:07:10.319> rooting<00:07:10.840> system 00:07:11.790 --> 00:07:11.800 align:start position:0% had like a a key based rooting system 00:07:11.800 --> 00:07:14.830 align:start position:0% had like a a key based rooting system available<00:07:12.800> now<00:07:13.800> how<00:07:14.039> how<00:07:14.199> you<00:07:14.319> combine<00:07:14.680> these 00:07:14.830 --> 00:07:14.840 align:start position:0% available now how how you combine these 00:07:14.840 --> 00:07:18.430 align:start position:0% available now how how you combine these two<00:07:15.039> ideas<00:07:15.479> obviously<00:07:16.080> if<00:07:16.240> you<00:07:16.840> if<00:07:16.960> you<00:07:17.599> um 00:07:18.430 --> 00:07:18.440 align:start position:0% two ideas obviously if you if you um 00:07:18.440 --> 00:07:20.629 align:start position:0% two ideas obviously if you if you um establish<00:07:19.039> that<00:07:19.400> the<00:07:19.520> way<00:07:19.720> you<00:07:19.919> find<00:07:20.479> a 00:07:20.629 --> 00:07:20.639 align:start position:0% establish that the way you find a 00:07:20.639 --> 00:07:23.110 align:start position:0% establish that the way you find a particular<00:07:21.000> chunk<00:07:21.440> is<00:07:21.639> to<00:07:22.000> go<00:07:22.240> through<00:07:22.879> like 00:07:23.110 --> 00:07:23.120 align:start position:0% particular chunk is to go through like 00:07:23.120 --> 00:07:25.990 align:start position:0% particular chunk is to go through like the<00:07:23.280> this<00:07:23.479> the<00:07:23.800> cadamia<00:07:24.479> rooting<00:07:25.479> sorry<00:07:25.840> for 00:07:25.990 --> 00:07:26.000 align:start position:0% the this the cadamia rooting sorry for 00:07:26.000 --> 00:07:27.589 align:start position:0% the this the cadamia rooting sorry for for<00:07:26.199> those<00:07:26.319> of<00:07:26.440> you<00:07:26.599> who<00:07:26.720> are<00:07:27.000> like<00:07:27.120> not<00:07:27.319> into 00:07:27.589 --> 00:07:27.599 align:start position:0% for those of you who are like not into 00:07:27.599 --> 00:07:30.029 align:start position:0% for those of you who are like not into this<00:07:27.960> Mambo<00:07:28.319> jumo<00:07:28.759> like<00:07:29.520> let<00:07:29.599> me<00:07:29.720> give<00:07:29.840> you<00:07:29.919> an 00:07:30.029 --> 00:07:30.039 align:start position:0% this Mambo jumo like let me give you an 00:07:30.039 --> 00:07:32.110 align:start position:0% this Mambo jumo like let me give you an example<00:07:30.319> so<00:07:30.599> the<00:07:30.759> C<00:07:31.160> routing<00:07:31.560> basically<00:07:31.960> would 00:07:32.110 --> 00:07:32.120 align:start position:0% example so the C routing basically would 00:07:32.120 --> 00:07:35.629 align:start position:0% example so the C routing basically would be<00:07:32.360> that<00:07:33.000> you<00:07:33.199> organize<00:07:33.680> your<00:07:33.879> hive<00:07:34.639> so<00:07:34.879> that 00:07:35.629 --> 00:07:35.639 align:start position:0% be that you organize your hive so that 00:07:35.639 --> 00:07:39.110 align:start position:0% be that you organize your hive so that for<00:07:35.960> each<00:07:36.720> chunk<00:07:37.720> uh<00:07:37.840> you<00:07:37.960> can<00:07:38.160> find<00:07:38.400> a<00:07:38.599> b<00:07:39.000> that 00:07:39.110 --> 00:07:39.120 align:start position:0% for each chunk uh you can find a b that 00:07:39.120 --> 00:07:41.110 align:start position:0% for each chunk uh you can find a b that can<00:07:39.280> take<00:07:39.479> you<00:07:39.599> to<00:07:39.720> a<00:07:39.840> hive<00:07:40.080> that's<00:07:40.319> closer<00:07:40.840> to 00:07:41.110 --> 00:07:41.120 align:start position:0% can take you to a hive that's closer to 00:07:41.120 --> 00:07:45.830 align:start position:0% can take you to a hive that's closer to the<00:07:41.440> to<00:07:41.720> that<00:07:42.360> uh<00:07:43.199> uh<00:07:43.479> Target<00:07:44.120> than<00:07:44.319> you<00:07:44.720> are<00:07:45.720> by 00:07:45.830 --> 00:07:45.840 align:start position:0% the to that uh uh Target than you are by 00:07:45.840 --> 00:07:48.350 align:start position:0% the to that uh uh Target than you are by a<00:07:46.000> factor<00:07:46.319> of<00:07:46.479> like<00:07:46.599> a<00:07:46.720> fixed<00:07:47.000> factor<00:07:47.840> in<00:07:48.199> kind 00:07:48.350 --> 00:07:48.360 align:start position:0% a factor of like a fixed factor in kind 00:07:48.360 --> 00:07:50.670 align:start position:0% a factor of like a fixed factor in kind of<00:07:48.840> and<00:07:49.039> basically<00:07:49.479> this<00:07:49.639> logarithmic 00:07:50.670 --> 00:07:50.680 align:start position:0% of and basically this logarithmic 00:07:50.680 --> 00:07:53.589 align:start position:0% of and basically this logarithmic distance<00:07:51.680> that<00:07:51.960> that<00:07:52.080> the<00:07:52.240> keys<00:07:52.840> space 00:07:53.589 --> 00:07:53.599 align:start position:0% distance that that the keys space 00:07:53.599 --> 00:07:59.550 align:start position:0% distance that that the keys space defines<00:07:55.000> uh<00:07:56.000> in<00:07:56.599> um<00:07:57.599> makes<00:07:57.960> sure<00:07:58.680> that<00:07:58.919> you<00:07:59.080> can 00:07:59.550 --> 00:07:59.560 align:start position:0% defines uh in um makes sure that you can 00:07:59.560 --> 00:08:03.430 align:start position:0% defines uh in um makes sure that you can find<00:08:00.280> a<00:08:00.520> particular<00:08:01.520> either<00:08:01.800> node<00:08:02.159> or<00:08:02.840> uh 00:08:03.430 --> 00:08:03.440 align:start position:0% find a particular either node or uh 00:08:03.440 --> 00:08:05.550 align:start position:0% find a particular either node or uh information<00:08:04.000> about<00:08:04.280> that<00:08:04.479> particular<00:08:04.879> Chunk 00:08:05.550 --> 00:08:05.560 align:start position:0% information about that particular Chunk 00:08:05.560 --> 00:08:09.550 align:start position:0% information about that particular Chunk in<00:08:06.000> a<00:08:06.680> logarithmic<00:08:07.599> time<00:08:08.599> in<00:08:08.800> in<00:08:08.919> a<00:08:09.080> in<00:08:09.159> a<00:08:09.360> in<00:08:09.440> a 00:08:09.550 --> 00:08:09.560 align:start position:0% in a logarithmic time in in a in a in a 00:08:09.560 --> 00:08:13.149 align:start position:0% in a logarithmic time in in a in a in a fixed<00:08:10.440> constant<00:08:11.440> number<00:08:11.720> of<00:08:11.919> hops<00:08:12.680> so<00:08:12.879> this<00:08:12.960> is 00:08:13.149 --> 00:08:13.159 align:start position:0% fixed constant number of hops so this is 00:08:13.159 --> 00:08:15.629 align:start position:0% fixed constant number of hops so this is basically<00:08:13.560> the<00:08:13.680> idea<00:08:13.919> of<00:08:14.080> DHT<00:08:14.840> it's<00:08:15.280> that's 00:08:15.629 --> 00:08:15.639 align:start position:0% basically the idea of DHT it's that's 00:08:15.639 --> 00:08:17.629 align:start position:0% basically the idea of DHT it's that's nothing<00:08:15.960> not<00:08:16.199> much<00:08:16.400> new<00:08:16.680> here<00:08:17.360> the<00:08:17.520> the 00:08:17.629 --> 00:08:17.639 align:start position:0% nothing not much new here the the 00:08:17.639 --> 00:08:19.710 align:start position:0% nothing not much new here the the interesting<00:08:18.120> Twist<00:08:18.440> on<00:08:18.560> the<00:08:18.720> DHD<00:08:19.319> that<00:08:19.479> we 00:08:19.710 --> 00:08:19.720 align:start position:0% interesting Twist on the DHD that we 00:08:19.720 --> 00:08:22.710 align:start position:0% interesting Twist on the DHD that we have<00:08:20.479> is<00:08:20.919> comes<00:08:21.199> from<00:08:21.479> several<00:08:21.960> properties<00:08:22.479> of 00:08:22.710 --> 00:08:22.720 align:start position:0% have is comes from several properties of 00:08:22.720 --> 00:08:27.029 align:start position:0% have is comes from several properties of this<00:08:23.080> of<00:08:23.240> this<00:08:24.080> SE<00:08:24.319> semi-stable<00:08:25.000> peer<00:08:25.639> U<00:08:26.599> uh 00:08:27.029 --> 00:08:27.039 align:start position:0% this of this SE semi-stable peer U uh 00:08:27.039 --> 00:08:29.990 align:start position:0% this of this SE semi-stable peer U uh base<00:08:28.039> and<00:08:28.319> but<00:08:28.479> more<00:08:28.720> importantly<00:08:29.560> the<00:08:29.639> other 00:08:29.990 --> 00:08:30.000 align:start position:0% base and but more importantly the other 00:08:30.000 --> 00:08:32.949 align:start position:0% base and but more importantly the other thing<00:08:30.280> is<00:08:30.680> that<00:08:31.599> we<00:08:31.879> we<00:08:32.000> don't<00:08:32.200> only<00:08:32.479> assume 00:08:32.949 --> 00:08:32.959 align:start position:0% thing is that we we don't only assume 00:08:32.959 --> 00:08:35.790 align:start position:0% thing is that we we don't only assume that<00:08:33.479> that<00:08:33.640> the<00:08:33.760> nodes<00:08:34.599> um<00:08:34.880> that<00:08:35.039> we<00:08:35.200> reach 00:08:35.790 --> 00:08:35.800 align:start position:0% that that the nodes um that we reach 00:08:35.800 --> 00:08:38.149 align:start position:0% that that the nodes um that we reach contain<00:08:36.519> like<00:08:36.880> give<00:08:37.080> you<00:08:37.240> information<00:08:37.839> about 00:08:38.149 --> 00:08:38.159 align:start position:0% contain like give you information about 00:08:38.159 --> 00:08:39.790 align:start position:0% contain like give you information about where<00:08:38.360> the<00:08:38.560> chunks<00:08:38.919> are<00:08:39.039> found<00:08:39.479> but<00:08:39.640> they 00:08:39.790 --> 00:08:39.800 align:start position:0% where the chunks are found but they 00:08:39.800 --> 00:08:41.550 align:start position:0% where the chunks are found but they actually<00:08:40.080> give<00:08:40.200> you<00:08:40.360> the<00:08:40.479> chunks<00:08:41.039> themselves 00:08:41.550 --> 00:08:41.560 align:start position:0% actually give you the chunks themselves 00:08:41.560 --> 00:08:43.870 align:start position:0% actually give you the chunks themselves so<00:08:41.719> it's<00:08:41.839> a<00:08:42.039> proper<00:08:42.599> uh<00:08:42.760> content<00:08:43.200> addressed 00:08:43.870 --> 00:08:43.880 align:start position:0% so it's a proper uh content addressed 00:08:43.880 --> 00:08:47.470 align:start position:0% so it's a proper uh content addressed storage<00:08:44.880> what's<00:08:45.160> the<00:08:45.760> uh<00:08:46.480> advantage<00:08:46.959> of<00:08:47.200> this 00:08:47.470 --> 00:08:47.480 align:start position:0% storage what's the uh advantage of this 00:08:47.480 --> 00:08:51.389 align:start position:0% storage what's the uh advantage of this this<00:08:47.640> view<00:08:48.279> um<00:08:48.720> this<00:08:49.120> gives<00:08:49.399> you<00:08:50.200> U<00:08:51.200> the 00:08:51.389 --> 00:08:51.399 align:start position:0% this view um this gives you U the 00:08:51.399 --> 00:08:54.790 align:start position:0% this view um this gives you U the possibility<00:08:51.959> to<00:08:52.200> Define<00:08:53.200> uh<00:08:53.560> a<00:08:53.760> Content<00:08:54.279> push 00:08:54.790 --> 00:08:54.800 align:start position:0% possibility to Define uh a Content push 00:08:54.800 --> 00:08:57.910 align:start position:0% possibility to Define uh a Content push mechanism<00:08:56.120> basically<00:08:57.120> basically<00:08:57.519> how<00:08:57.720> the 00:08:57.910 --> 00:08:57.920 align:start position:0% mechanism basically basically how the 00:08:57.920 --> 00:08:59.550 align:start position:0% mechanism basically basically how the distribution<00:08:58.519> of<00:08:58.720> content<00:08:59.040> works<00:08:59.279> not<00:08:59.440> not 00:08:59.550 --> 00:08:59.560 align:start position:0% distribution of content works not not 00:08:59.560 --> 00:09:02.430 align:start position:0% distribution of content works not not only<00:08:59.720> their<00:09:00.279> retrieval<00:09:01.279> uh<00:09:01.480> basically<00:09:02.160> along 00:09:02.430 --> 00:09:02.440 align:start position:0% only their retrieval uh basically along 00:09:02.440 --> 00:09:04.110 align:start position:0% only their retrieval uh basically along the<00:09:02.600> same<00:09:02.839> kind<00:09:03.000> of<00:09:03.200> lines<00:09:03.480> as<00:09:03.600> the<00:09:03.680> routing 00:09:04.110 --> 00:09:04.120 align:start position:0% the same kind of lines as the routing 00:09:04.120 --> 00:09:07.910 align:start position:0% the same kind of lines as the routing works<00:09:04.800> or<00:09:05.000> even<00:09:05.320> simultaneously<00:09:06.200> to<00:09:06.440> that<00:09:07.279> and 00:09:07.910 --> 00:09:07.920 align:start position:0% works or even simultaneously to that and 00:09:07.920 --> 00:09:12.030 align:start position:0% works or even simultaneously to that and one<00:09:08.320> consequence<00:09:09.040> of<00:09:09.320> that<00:09:09.839> is<00:09:10.200> that<00:09:10.760> is<00:09:11.279> that 00:09:12.030 --> 00:09:12.040 align:start position:0% one consequence of that is that is that 00:09:12.040 --> 00:09:17.030 align:start position:0% one consequence of that is that is that eventually<00:09:13.040> the<00:09:14.000> um<00:09:15.000> as<00:09:15.160> as<00:09:15.279> a<00:09:15.440> result<00:09:15.880> of 00:09:17.030 --> 00:09:17.040 align:start position:0% eventually the um as as a result of 00:09:17.040 --> 00:09:18.710 align:start position:0% eventually the um as as a result of continuous 00:09:18.710 --> 00:09:18.720 align:start position:0% continuous 00:09:18.720 --> 00:09:21.310 align:start position:0% continuous retrievals<00:09:19.720> and<00:09:20.200> the<00:09:20.440> the<00:09:20.640> the<00:09:20.760> scheme<00:09:21.120> that 00:09:21.310 --> 00:09:21.320 align:start position:0% retrievals and the the the scheme that 00:09:21.320 --> 00:09:23.470 align:start position:0% retrievals and the the the scheme that we<00:09:21.519> define<00:09:22.040> basically<00:09:22.519> this<00:09:23.040> through<00:09:23.279> this 00:09:23.470 --> 00:09:23.480 align:start position:0% we define basically this through this 00:09:23.480 --> 00:09:26.230 align:start position:0% we define basically this through this forwarding<00:09:24.519> uh<00:09:25.519> the<00:09:25.640> requests<00:09:26.040> and 00:09:26.230 --> 00:09:26.240 align:start position:0% forwarding uh the requests and 00:09:26.240 --> 00:09:29.509 align:start position:0% forwarding uh the requests and forwarding<00:09:27.079> um<00:09:27.760> um<00:09:28.000> deliveries 00:09:29.509 --> 00:09:29.519 align:start position:0% forwarding um um deliveries 00:09:29.519 --> 00:09:31.190 align:start position:0% forwarding um um deliveries the<00:09:29.839> the<00:09:30.040> the<00:09:30.120> end<00:09:30.360> result<00:09:30.640> of<00:09:30.800> that<00:09:30.920> is<00:09:31.079> that 00:09:31.190 --> 00:09:31.200 align:start position:0% the the the end result of that is that 00:09:31.200 --> 00:09:33.230 align:start position:0% the the the end result of that is that you<00:09:31.360> end<00:09:31.600> up<00:09:31.839> with<00:09:32.040> the<00:09:32.399> with<00:09:32.560> the<00:09:33.000> with<00:09:33.120> the 00:09:33.230 --> 00:09:33.240 align:start position:0% you end up with the with the with the 00:09:33.240 --> 00:09:35.550 align:start position:0% you end up with the with the with the Swarm<00:09:33.560> being<00:09:33.760> a<00:09:33.920> kind<00:09:34.040> of<00:09:34.200> elastic<00:09:34.720> Cloud 00:09:35.550 --> 00:09:35.560 align:start position:0% Swarm being a kind of elastic Cloud 00:09:35.560 --> 00:09:37.829 align:start position:0% Swarm being a kind of elastic Cloud which<00:09:35.720> means<00:09:36.079> that<00:09:36.360> all<00:09:36.680> the<00:09:37.120> the<00:09:37.360> content 00:09:37.829 --> 00:09:37.839 align:start position:0% which means that all the the content 00:09:37.839 --> 00:09:40.190 align:start position:0% which means that all the the content that<00:09:38.200> that<00:09:38.320> is<00:09:38.600> popular<00:09:39.160> can<00:09:39.360> end<00:09:39.600> up 00:09:40.190 --> 00:09:40.200 align:start position:0% that that is popular can end up 00:09:40.200 --> 00:09:42.350 align:start position:0% that that is popular can end up relatively<00:09:40.800> far<00:09:41.120> from<00:09:41.399> the<00:09:41.640> from<00:09:41.800> the<00:09:41.920> node 00:09:42.350 --> 00:09:42.360 align:start position:0% relatively far from the from the node 00:09:42.360 --> 00:09:44.030 align:start position:0% relatively far from the from the node that's<00:09:42.760> supposed<00:09:43.120> to<00:09:43.200> be<00:09:43.320> close<00:09:43.600> to<00:09:43.720> it 00:09:44.030 --> 00:09:44.040 align:start position:0% that's supposed to be close to it 00:09:44.040 --> 00:09:48.030 align:start position:0% that's supposed to be close to it supposed<00:09:44.320> to<00:09:44.440> store<00:09:44.800> it<00:09:45.760> but<00:09:46.600> that<00:09:46.760> means<00:09:47.640> that 00:09:48.030 --> 00:09:48.040 align:start position:0% supposed to store it but that means that 00:09:48.040 --> 00:09:50.790 align:start position:0% supposed to store it but that means that the<00:09:48.240> content<00:09:48.680> will<00:09:48.880> be<00:09:49.560> uh<00:09:49.839> more<00:09:50.240> readily 00:09:50.790 --> 00:09:50.800 align:start position:0% the content will be uh more readily 00:09:50.800 --> 00:09:52.750 align:start position:0% the content will be uh more readily available<00:09:51.240> in<00:09:51.480> less<00:09:51.880> less<00:09:52.120> hopes<00:09:52.519> because 00:09:52.750 --> 00:09:52.760 align:start position:0% available in less less hopes because 00:09:52.760 --> 00:09:55.509 align:start position:0% available in less less hopes because it's<00:09:53.040> it's<00:09:53.200> just<00:09:53.440> more<00:09:54.120> per<00:09:54.880> pervasively 00:09:55.509 --> 00:09:55.519 align:start position:0% it's it's just more per pervasively 00:09:55.519 --> 00:09:57.590 align:start position:0% it's it's just more per pervasively present<00:09:55.880> in<00:09:56.000> the<00:09:56.160> network<00:09:56.959> and<00:09:57.120> therefore<00:09:57.440> you 00:09:57.590 --> 00:09:57.600 align:start position:0% present in the network and therefore you 00:09:57.600 --> 00:10:00.630 align:start position:0% present in the network and therefore you get<00:09:58.320> an<00:09:58.480> autoscaling<00:09:59.519> that<00:09:59.760> popular<00:10:00.200> content 00:10:00.630 --> 00:10:00.640 align:start position:0% get an autoscaling that popular content 00:10:00.640 --> 00:10:02.710 align:start position:0% get an autoscaling that popular content will<00:10:01.160> uh<00:10:01.399> will<00:10:01.680> be<00:10:01.880> retrieved<00:10:02.320> with<00:10:02.480> less 00:10:02.710 --> 00:10:02.720 align:start position:0% will uh will be retrieved with less 00:10:02.720 --> 00:10:05.550 align:start position:0% will uh will be retrieved with less latency<00:10:03.440> or<00:10:03.680> that's<00:10:04.079> that's<00:10:04.240> the<00:10:04.399> idea<00:10:05.320> and 00:10:05.550 --> 00:10:05.560 align:start position:0% latency or that's that's the idea and 00:10:05.560 --> 00:10:07.670 align:start position:0% latency or that's that's the idea and also<00:10:05.959> this<00:10:06.240> this<00:10:06.640> this<00:10:06.760> means<00:10:07.000> that<00:10:07.160> SW<00:10:07.519> is 00:10:07.670 --> 00:10:07.680 align:start position:0% also this this this means that SW is 00:10:07.680 --> 00:10:09.829 align:start position:0% also this this this means that SW is basically<00:10:08.040> a<00:10:08.200> constantly<00:10:08.800> maximum 00:10:09.829 --> 00:10:09.839 align:start position:0% basically a constantly maximum 00:10:09.839 --> 00:10:12.750 align:start position:0% basically a constantly maximum utilization<00:10:10.839> system<00:10:11.279> so<00:10:11.760> so<00:10:12.279> this<00:10:12.440> for 00:10:12.750 --> 00:10:12.760 align:start position:0% utilization system so so this for 00:10:12.760 --> 00:10:15.150 align:start position:0% utilization system so so this for forwarding<00:10:13.480> and<00:10:13.760> and<00:10:14.120> the<00:10:14.480> distribution 00:10:15.150 --> 00:10:15.160 align:start position:0% forwarding and and the distribution 00:10:15.160 --> 00:10:18.069 align:start position:0% forwarding and and the distribution scheme<00:10:15.640> that<00:10:16.040> we<00:10:16.200> also<00:10:16.440> call<00:10:16.720> like<00:10:16.880> smart 00:10:18.069 --> 00:10:18.079 align:start position:0% scheme that we also call like smart 00:10:18.079 --> 00:10:20.910 align:start position:0% scheme that we also call like smart synchronization<00:10:19.079> it<00:10:19.240> also<00:10:19.480> makes<00:10:19.720> sure<00:10:20.040> that 00:10:20.910 --> 00:10:20.920 align:start position:0% synchronization it also makes sure that 00:10:20.920 --> 00:10:25.230 align:start position:0% synchronization it also makes sure that uh<00:10:21.480> the<00:10:21.839> the<00:10:22.000> network<00:10:22.519> adapts<00:10:23.200> to<00:10:24.079> like<00:10:25.079> when 00:10:25.230 --> 00:10:25.240 align:start position:0% uh the the network adapts to like when 00:10:25.240 --> 00:10:26.829 align:start position:0% uh the the network adapts to like when when<00:10:25.399> content<00:10:25.760> becomes<00:10:26.200> popular<00:10:26.640> it 00:10:26.829 --> 00:10:26.839 align:start position:0% when content becomes popular it 00:10:26.839 --> 00:10:29.150 align:start position:0% when content becomes popular it basically<00:10:27.320> replicates<00:10:28.120> and<00:10:28.560> you<00:10:28.720> think<00:10:29.040> you 00:10:29.150 --> 00:10:29.160 align:start position:0% basically replicates and you think you 00:10:29.160 --> 00:10:31.790 align:start position:0% basically replicates and you think you can<00:10:29.360> can<00:10:29.480> think<00:10:29.760> also<00:10:30.279> of<00:10:30.560> of<00:10:30.680> it<00:10:31.040> like<00:10:31.200> a<00:10:31.680> like 00:10:31.790 --> 00:10:31.800 align:start position:0% can can think also of of it like a like 00:10:31.800 --> 00:10:34.750 align:start position:0% can can think also of of it like a like a<00:10:31.959> giant<00:10:32.240> donut<00:10:32.880> that<00:10:33.120> grows<00:10:33.640> when<00:10:33.920> everybody 00:10:34.750 --> 00:10:34.760 align:start position:0% a giant donut that grows when everybody 00:10:34.760 --> 00:10:37.949 align:start position:0% a giant donut that grows when everybody everybody<00:10:35.240> bites<00:10:35.560> bites<00:10:35.880> to<00:10:36.079> it<00:10:36.959> and<00:10:37.639> and<00:10:37.839> and 00:10:37.949 --> 00:10:37.959 align:start position:0% everybody bites bites to it and and and 00:10:37.959 --> 00:10:40.350 align:start position:0% everybody bites bites to it and and and the<00:10:38.120> same<00:10:38.320> way<00:10:38.639> it<00:10:38.880> can<00:10:39.040> also<00:10:39.279> shrink<00:10:39.680> so<00:10:39.920> if<00:10:40.120> if 00:10:40.350 --> 00:10:40.360 align:start position:0% the same way it can also shrink so if if 00:10:40.360 --> 00:10:44.710 align:start position:0% the same way it can also shrink so if if if<00:10:40.519> document<00:10:41.000> popularity<00:10:41.800> is<00:10:42.839> doings<00:10:43.839> then 00:10:44.710 --> 00:10:44.720 align:start position:0% if document popularity is doings then 00:10:44.720 --> 00:10:47.949 align:start position:0% if document popularity is doings then then<00:10:44.880> it's<00:10:45.560> it's<00:10:45.800> it's<00:10:46.399> continually<00:10:47.399> deleted 00:10:47.949 --> 00:10:47.959 align:start position:0% then it's it's it's continually deleted 00:10:47.959 --> 00:10:50.550 align:start position:0% then it's it's it's continually deleted from<00:10:48.800> uh<00:10:48.920> first<00:10:49.320> first<00:10:49.800> those<00:10:49.959> nodes<00:10:50.279> that<00:10:50.399> are 00:10:50.550 --> 00:10:50.560 align:start position:0% from uh first first those nodes that are 00:10:50.560 --> 00:10:53.069 align:start position:0% from uh first first those nodes that are relatively<00:10:51.120> far<00:10:51.760> from<00:10:51.959> it<00:10:52.399> for<00:10:52.639> for<00:10:52.839> which 00:10:53.069 --> 00:10:53.079 align:start position:0% relatively far from it for for which 00:10:53.079 --> 00:10:55.550 align:start position:0% relatively far from it for for which they<00:10:53.160> are<00:10:54.000> the<00:10:54.160> popularity<00:10:54.720> doesn't<00:10:55.040> justify 00:10:55.550 --> 00:10:55.560 align:start position:0% they are the popularity doesn't justify 00:10:55.560 --> 00:10:58.670 align:start position:0% they are the popularity doesn't justify anymore<00:10:55.959> that<00:10:56.079> they<00:10:56.240> store<00:10:56.560> it<00:10:57.320> U<00:10:58.320> just 00:10:58.670 --> 00:10:58.680 align:start position:0% anymore that they store it U just 00:10:58.680 --> 00:11:01.509 align:start position:0% anymore that they store it U just because<00:10:59.000> they<00:10:59.600> they<00:10:59.839> they<00:11:00.040> they<00:11:00.160> are<00:11:00.440> too<00:11:00.680> far 00:11:01.509 --> 00:11:01.519 align:start position:0% because they they they they are too far 00:11:01.519 --> 00:11:03.310 align:start position:0% because they they they they are too far and<00:11:01.800> and<00:11:02.000> and<00:11:02.120> so<00:11:02.519> you<00:11:02.639> can<00:11:02.800> think<00:11:02.959> of<00:11:03.079> it<00:11:03.240> as 00:11:03.310 --> 00:11:03.320 align:start position:0% and and and so you can think of it as 00:11:03.320 --> 00:11:06.230 align:start position:0% and and and so you can think of it as the<00:11:03.440> donut<00:11:03.800> shrinking<00:11:04.519> and<00:11:04.680> in<00:11:04.839> the<00:11:05.120> end<00:11:06.120> it 00:11:06.230 --> 00:11:06.240 align:start position:0% the donut shrinking and in the end it 00:11:06.240 --> 00:11:08.910 align:start position:0% the donut shrinking and in the end it can<00:11:06.399> also<00:11:06.680> happen<00:11:06.959> that<00:11:07.079> certain<00:11:07.519> content<00:11:08.519> is 00:11:08.910 --> 00:11:08.920 align:start position:0% can also happen that certain content is 00:11:08.920 --> 00:11:11.150 align:start position:0% can also happen that certain content is is<00:11:09.240> deleted<00:11:10.240> now<00:11:10.440> let's<00:11:10.600> go<00:11:10.760> to<00:11:10.920> the 00:11:11.150 --> 00:11:11.160 align:start position:0% is deleted now let's go to the 00:11:11.160 --> 00:11:14.030 align:start position:0% is deleted now let's go to the incentives<00:11:11.800> that's<00:11:12.000> this<00:11:12.240> kind<00:11:12.399> of<00:11:13.040> fourth 00:11:14.030 --> 00:11:14.040 align:start position:0% incentives that's this kind of fourth 00:11:14.040 --> 00:11:18.389 align:start position:0% incentives that's this kind of fourth aspect<00:11:14.480> of<00:11:14.760> the<00:11:15.560> of<00:11:15.760> the<00:11:16.200> uh<00:11:16.399> of<00:11:16.560> Of<00:11:16.680> Swarm<00:11:17.680> so 00:11:18.389 --> 00:11:18.399 align:start position:0% aspect of the of the uh of Of Swarm so 00:11:18.399 --> 00:11:22.710 align:start position:0% aspect of the of the uh of Of Swarm so each<00:11:18.720> each<00:11:18.920> of<00:11:19.120> the<00:11:19.360> decisions<00:11:20.200> that<00:11:20.959> um<00:11:21.720> um 00:11:22.710 --> 00:11:22.720 align:start position:0% each each of the decisions that um um 00:11:22.720 --> 00:11:26.230 align:start position:0% each each of the decisions that um um the<00:11:23.320> Swarm<00:11:24.240> participant<00:11:24.839> nodes<00:11:25.519> uh<00:11:25.680> take 00:11:26.230 --> 00:11:26.240 align:start position:0% the Swarm participant nodes uh take 00:11:26.240 --> 00:11:29.550 align:start position:0% the Swarm participant nodes uh take should<00:11:26.519> be<00:11:26.680> somehow<00:11:27.600> um 00:11:29.550 --> 00:11:29.560 align:start position:0% should be somehow um 00:11:29.560 --> 00:11:32.069 align:start position:0% should be somehow um legitimated<00:11:30.399> by<00:11:30.639> by<00:11:30.760> some<00:11:30.959> sort<00:11:31.160> of<00:11:31.399> incentive 00:11:32.069 --> 00:11:32.079 align:start position:0% legitimated by by some sort of incentive 00:11:32.079 --> 00:11:33.870 align:start position:0% legitimated by by some sort of incentive because<00:11:32.519> as<00:11:32.760> as<00:11:32.880> we<00:11:33.000> all<00:11:33.160> know<00:11:33.360> they<00:11:33.480> are<00:11:33.680> like 00:11:33.870 --> 00:11:33.880 align:start position:0% because as as we all know they are like 00:11:33.880 --> 00:11:36.550 align:start position:0% because as as we all know they are like rational<00:11:34.320> actors<00:11:34.800> and<00:11:35.320> they<00:11:35.440> are<00:11:35.959> not<00:11:36.120> shying 00:11:36.550 --> 00:11:36.560 align:start position:0% rational actors and they are not shying 00:11:36.560 --> 00:11:38.910 align:start position:0% rational actors and they are not shying away<00:11:36.800> from<00:11:37.120> maximizing<00:11:37.760> their<00:11:38.000> profits<00:11:38.519> so 00:11:38.910 --> 00:11:38.920 align:start position:0% away from maximizing their profits so 00:11:38.920 --> 00:11:40.509 align:start position:0% away from maximizing their profits so they<00:11:39.040> can<00:11:39.240> abuse<00:11:39.560> the<00:11:39.760> system<00:11:40.040> if<00:11:40.160> we<00:11:40.320> don't 00:11:40.509 --> 00:11:40.519 align:start position:0% they can abuse the system if we don't 00:11:40.519 --> 00:11:43.030 align:start position:0% they can abuse the system if we don't align<00:11:40.839> the<00:11:41.000> incentives<00:11:41.600> properly<00:11:42.600> so<00:11:42.839> what 00:11:43.030 --> 00:11:43.040 align:start position:0% align the incentives properly so what 00:11:43.040 --> 00:11:44.470 align:start position:0% align the incentives properly so what what<00:11:43.160> do<00:11:43.240> you<00:11:43.399> actually<00:11:43.639> store<00:11:44.040> let's<00:11:44.240> go<00:11:44.360> back 00:11:44.470 --> 00:11:44.480 align:start position:0% what do you actually store let's go back 00:11:44.480 --> 00:11:47.190 align:start position:0% what do you actually store let's go back to<00:11:44.639> this<00:11:44.920> question<00:11:45.279> first<00:11:46.079> you<00:11:46.279> you<00:11:46.880> we<00:11:47.000> can 00:11:47.190 --> 00:11:47.200 align:start position:0% to this question first you you we can 00:11:47.200 --> 00:11:48.910 align:start position:0% to this question first you you we can answer<00:11:47.480> this<00:11:47.680> question<00:11:47.920> simply<00:11:48.320> by<00:11:48.480> like<00:11:48.760> you 00:11:48.910 --> 00:11:48.920 align:start position:0% answer this question simply by like you 00:11:48.920 --> 00:11:51.470 align:start position:0% answer this question simply by like you store<00:11:49.399> what<00:11:49.639> you 00:11:51.470 --> 00:11:51.480 align:start position:0% store what you 00:11:51.480 --> 00:11:55.150 align:start position:0% store what you actually<00:11:52.480> deem<00:11:53.000> most<00:11:53.360> profitable<00:11:53.920> to<00:11:54.160> store 00:11:55.150 --> 00:11:55.160 align:start position:0% actually deem most profitable to store 00:11:55.160 --> 00:11:58.030 align:start position:0% actually deem most profitable to store uh<00:11:55.959> it<00:11:56.040> turns<00:11:56.360> out<00:11:56.639> that<00:11:57.200> all<00:11:57.320> you<00:11:57.480> need<00:11:57.720> is<00:11:57.839> to 00:11:58.030 --> 00:11:58.040 align:start position:0% uh it turns out that all you need is to 00:11:58.040 --> 00:12:00.910 align:start position:0% uh it turns out that all you need is to consult<00:11:58.600> like<00:11:58.800> your<00:11:59.279> database<00:11:59.680> and<00:11:59.839> see<00:12:00.320> how 00:12:00.910 --> 00:12:00.920 align:start position:0% consult like your database and see how 00:12:00.920 --> 00:12:03.870 align:start position:0% consult like your database and see how much<00:12:01.920> a<00:12:02.079> particular<00:12:02.440> chunk<00:12:02.720> or<00:12:02.959> content<00:12:03.360> was 00:12:03.870 --> 00:12:03.880 align:start position:0% much a particular chunk or content was 00:12:03.880 --> 00:12:06.389 align:start position:0% much a particular chunk or content was accessed<00:12:04.880> it's<00:12:05.279> it's<00:12:05.480> because<00:12:05.800> actually<00:12:06.160> on 00:12:06.389 --> 00:12:06.399 align:start position:0% accessed it's it's because actually on 00:12:06.399 --> 00:12:08.069 align:start position:0% accessed it's it's because actually on one<00:12:06.519> on<00:12:06.720> one<00:12:06.880> hand<00:12:07.079> access<00:12:07.440> is<00:12:07.560> a<00:12:07.680> very<00:12:07.839> good 00:12:08.069 --> 00:12:08.079 align:start position:0% one on one hand access is a very good 00:12:08.079 --> 00:12:10.269 align:start position:0% one on one hand access is a very good predictor<00:12:08.519> of<00:12:08.639> future<00:12:09.040> profitability<00:12:09.800> of<00:12:09.959> a 00:12:10.269 --> 00:12:10.279 align:start position:0% predictor of future profitability of a 00:12:10.279 --> 00:12:13.110 align:start position:0% predictor of future profitability of a chunk<00:12:11.279> to<00:12:11.480> assume<00:12:11.800> some<00:12:12.000> sort<00:12:12.240> of<00:12:12.920> um 00:12:13.110 --> 00:12:13.120 align:start position:0% chunk to assume some sort of um 00:12:13.120 --> 00:12:15.790 align:start position:0% chunk to assume some sort of um constanty<00:12:13.800> of<00:12:14.320> of<00:12:14.519> of<00:12:14.680> popularity<00:12:15.279> over<00:12:15.560> time 00:12:15.790 --> 00:12:15.800 align:start position:0% constanty of of of popularity over time 00:12:15.800 --> 00:12:18.310 align:start position:0% constanty of of of popularity over time at<00:12:15.959> least<00:12:16.760> and<00:12:17.160> on<00:12:17.320> the<00:12:17.480> other<00:12:17.680> hand<00:12:17.920> it's<00:12:18.160> it 00:12:18.310 --> 00:12:18.320 align:start position:0% at least and on the other hand it's it 00:12:18.320 --> 00:12:22.590 align:start position:0% at least and on the other hand it's it makes<00:12:18.560> sure<00:12:18.880> that<00:12:19.120> the<00:12:19.480> that<00:12:19.720> the<00:12:20.240> um<00:12:21.120> content 00:12:22.590 --> 00:12:22.600 align:start position:0% makes sure that the that the um content 00:12:22.600 --> 00:12:25.470 align:start position:0% makes sure that the that the um content um<00:12:23.639> synchronization<00:12:24.639> uh<00:12:24.800> results<00:12:25.199> in<00:12:25.320> a 00:12:25.470 --> 00:12:25.480 align:start position:0% um synchronization uh results in a 00:12:25.480 --> 00:12:27.590 align:start position:0% um synchronization uh results in a network<00:12:26.000> where<00:12:26.320> where<00:12:26.800> which<00:12:27.000> which<00:12:27.160> behaves 00:12:27.590 --> 00:12:27.600 align:start position:0% network where where which which behaves 00:12:27.600 --> 00:12:30.110 align:start position:0% network where where which which behaves like<00:12:27.760> in<00:12:27.920> this<00:12:28.199> in<00:12:28.800> elastic<00:12:29.199> cloudway<00:12:29.680> so<00:12:29.920> do 00:12:30.110 --> 00:12:30.120 align:start position:0% like in this in elastic cloudway so do 00:12:30.120 --> 00:12:31.189 align:start position:0% like in this in elastic cloudway so do the<00:12:30.240> Autos 00:12:31.189 --> 00:12:31.199 align:start position:0% the Autos 00:12:31.199 --> 00:12:36.030 align:start position:0% the Autos scaling<00:12:32.199> now<00:12:32.800> uh<00:12:33.800> I<00:12:34.000> I<00:12:34.320> I<00:12:34.480> I<00:12:34.600> realized<00:12:35.160> that<00:12:35.760> uh 00:12:36.030 --> 00:12:36.040 align:start position:0% scaling now uh I I I I realized that uh 00:12:36.040 --> 00:12:39.910 align:start position:0% scaling now uh I I I I realized that uh the<00:12:36.720> incentives<00:12:37.320> for<00:12:37.639> retrieving<00:12:38.639> certain<00:12:39.519> um 00:12:39.910 --> 00:12:39.920 align:start position:0% the incentives for retrieving certain um 00:12:39.920 --> 00:12:43.269 align:start position:0% the incentives for retrieving certain um content<00:12:40.839> takes<00:12:41.199> care<00:12:41.399> of<00:12:41.600> only<00:12:42.040> those<00:12:42.720> cases 00:12:43.269 --> 00:12:43.279 align:start position:0% content takes care of only those cases 00:12:43.279 --> 00:12:45.910 align:start position:0% content takes care of only those cases where<00:12:44.199> where<00:12:44.360> we<00:12:44.480> talk<00:12:44.720> about<00:12:44.959> deps<00:12:45.360> like<00:12:45.560> this 00:12:45.910 --> 00:12:45.920 align:start position:0% where where we talk about deps like this 00:12:45.920 --> 00:12:47.949 align:start position:0% where where we talk about deps like this typically<00:12:46.399> popular<00:12:46.800> content<00:12:47.240> that<00:12:47.519> you<00:12:47.639> want 00:12:47.949 --> 00:12:47.959 align:start position:0% typically popular content that you want 00:12:47.959 --> 00:12:50.230 align:start position:0% typically popular content that you want to<00:12:48.199> distribute<00:12:48.720> and<00:12:48.839> you<00:12:48.959> want<00:12:49.199> people<00:12:49.519> to<00:12:49.959> to 00:12:50.230 --> 00:12:50.240 align:start position:0% to distribute and you want people to to 00:12:50.240 --> 00:12:52.470 align:start position:0% to distribute and you want people to to to<00:12:50.360> reach<00:12:51.199> this<00:12:51.320> is<00:12:51.440> not<00:12:51.639> all<00:12:51.839> the<00:12:52.000> cases<00:12:52.320> we 00:12:52.470 --> 00:12:52.480 align:start position:0% to reach this is not all the cases we 00:12:52.480 --> 00:12:55.949 align:start position:0% to reach this is not all the cases we also<00:12:52.800> invis<00:12:53.560> Envision<00:12:54.079> SW<00:12:54.440> to<00:12:54.600> be<00:12:54.920> used<00:12:55.639> for 00:12:55.949 --> 00:12:55.959 align:start position:0% also invis Envision SW to be used for 00:12:55.959 --> 00:12:59.310 align:start position:0% also invis Envision SW to be used for cases<00:12:56.480> where<00:12:57.320> where<00:12:57.440> you<00:12:57.600> want<00:12:57.800> to<00:12:58.320> store<00:12:58.680> and 00:12:59.310 --> 00:12:59.320 align:start position:0% cases where where you want to store and 00:12:59.320 --> 00:13:01.910 align:start position:0% cases where where you want to store and actually<00:12:59.600> make<00:12:59.800> sure<00:13:00.120> that<00:13:00.519> you<00:13:01.360> your<00:13:01.560> content 00:13:01.910 --> 00:13:01.920 align:start position:0% actually make sure that you your content 00:13:01.920 --> 00:13:04.189 align:start position:0% actually make sure that you your content is<00:13:02.079> stored<00:13:02.839> even<00:13:03.079> if<00:13:03.199> it's<00:13:03.440> very<00:13:03.600> seldomly 00:13:04.189 --> 00:13:04.199 align:start position:0% is stored even if it's very seldomly 00:13:04.199 --> 00:13:06.550 align:start position:0% is stored even if it's very seldomly accessed<00:13:04.639> for<00:13:04.800> example<00:13:05.120> a<00:13:05.199> birth<00:13:05.560> certificate 00:13:06.550 --> 00:13:06.560 align:start position:0% accessed for example a birth certificate 00:13:06.560 --> 00:13:09.230 align:start position:0% accessed for example a birth certificate and<00:13:06.680> we<00:13:06.880> realize<00:13:07.399> that<00:13:07.839> this<00:13:08.079> incentive<00:13:09.000> that 00:13:09.230 --> 00:13:09.240 align:start position:0% and we realize that this incentive that 00:13:09.240 --> 00:13:14.430 align:start position:0% and we realize that this incentive that we<00:13:09.800> we<00:13:10.079> talking<00:13:10.399> about<00:13:10.639> is<00:13:11.079> not<00:13:12.079> handling<00:13:12.440> that 00:13:14.430 --> 00:13:14.440 align:start position:0% we we talking about is not handling that 00:13:14.440 --> 00:13:17.189 align:start position:0% we we talking about is not handling that properly<00:13:15.440> among<00:13:15.839> other<00:13:16.079> things<00:13:16.480> it's<00:13:16.720> because 00:13:17.189 --> 00:13:17.199 align:start position:0% properly among other things it's because 00:13:17.199 --> 00:13:19.069 align:start position:0% properly among other things it's because it's<00:13:17.320> a<00:13:17.480> very<00:13:17.720> different<00:13:18.079> type<00:13:18.320> of<00:13:18.720> of<00:13:18.920> of 00:13:19.069 --> 00:13:19.079 align:start position:0% it's a very different type of of of 00:13:19.079 --> 00:13:20.590 align:start position:0% it's a very different type of of of reward<00:13:19.440> mechanism<00:13:19.880> because<00:13:20.079> here<00:13:20.279> here<00:13:20.440> you 00:13:20.590 --> 00:13:20.600 align:start position:0% reward mechanism because here here you 00:13:20.600 --> 00:13:23.509 align:start position:0% reward mechanism because here here you actually<00:13:20.839> want<00:13:21.040> to<00:13:22.000> make<00:13:22.199> sure<00:13:22.519> that<00:13:22.839> my<00:13:23.240> birth 00:13:23.509 --> 00:13:23.519 align:start position:0% actually want to make sure that my birth 00:13:23.519 --> 00:13:25.350 align:start position:0% actually want to make sure that my birth certificate<00:13:24.040> is<00:13:24.320> is<00:13:24.480> is<00:13:24.639> available<00:13:25.079> I<00:13:25.199> don't 00:13:25.350 --> 00:13:25.360 align:start position:0% certificate is is is available I don't 00:13:25.360 --> 00:13:26.870 align:start position:0% certificate is is is available I don't want<00:13:25.519> to<00:13:25.680> pull<00:13:25.920> it<00:13:26.160> all<00:13:26.320> the<00:13:26.480> time<00:13:26.680> because 00:13:26.870 --> 00:13:26.880 align:start position:0% want to pull it all the time because 00:13:26.880 --> 00:13:29.509 align:start position:0% want to pull it all the time because it's<00:13:27.079> anyway<00:13:27.480> insecure<00:13:27.920> and<00:13:28.320> inefficient<00:13:29.120> so 00:13:29.509 --> 00:13:29.519 align:start position:0% it's anyway insecure and inefficient so 00:13:29.519 --> 00:13:31.430 align:start position:0% it's anyway insecure and inefficient so if<00:13:29.639> I<00:13:29.800> always<00:13:30.040> receive<00:13:30.440> it<00:13:30.880> so<00:13:31.079> it's<00:13:31.240> a 00:13:31.430 --> 00:13:31.440 align:start position:0% if I always receive it so it's a 00:13:31.440 --> 00:13:33.310 align:start position:0% if I always receive it so it's a different<00:13:31.920> different<00:13:32.279> system<00:13:32.600> it<00:13:32.720> needs 00:13:33.310 --> 00:13:33.320 align:start position:0% different different system it needs 00:13:33.320 --> 00:13:34.949 align:start position:0% different different system it needs there's<00:13:33.480> a<00:13:33.600> lot<00:13:33.760> of<00:13:33.920> discussion<00:13:34.320> about<00:13:34.560> this<00:13:34.800> I 00:13:34.949 --> 00:13:34.959 align:start position:0% there's a lot of discussion about this I 00:13:34.959 --> 00:13:36.870 align:start position:0% there's a lot of discussion about this I I'm<00:13:35.079> not<00:13:35.440> not<00:13:35.600> going<00:13:35.720> to<00:13:35.920> go<00:13:36.079> into<00:13:36.360> that<00:13:36.639> I<00:13:36.760> I 00:13:36.870 --> 00:13:36.880 align:start position:0% I'm not not going to go into that I I 00:13:36.880 --> 00:13:39.389 align:start position:0% I'm not not going to go into that I I just<00:13:37.120> refer<00:13:37.480> to<00:13:37.680> the<00:13:38.000> to<00:13:38.199> the<00:13:38.639> documentation 00:13:39.389 --> 00:13:39.399 align:start position:0% just refer to the to the documentation 00:13:39.399 --> 00:13:42.030 align:start position:0% just refer to the to the documentation and<00:13:39.639> like<00:13:39.880> the<00:13:40.519> the<00:13:40.680> kind<00:13:40.839> of<00:13:41.199> orange<00:13:41.639> paper 00:13:42.030 --> 00:13:42.040 align:start position:0% and like the the kind of orange paper 00:13:42.040 --> 00:13:44.110 align:start position:0% and like the the kind of orange paper that<00:13:42.279> we<00:13:42.839> we're<00:13:43.120> in<00:13:43.240> the<00:13:43.480> in<00:13:43.560> the<00:13:43.680> middle<00:13:43.920> of 00:13:44.110 --> 00:13:44.120 align:start position:0% that we we're in the in the middle of 00:13:44.120 --> 00:13:47.470 align:start position:0% that we we're in the in the middle of writing<00:13:44.839> for<00:13:45.240> for<00:13:45.440> this<00:13:45.800> discussion<00:13:46.800> uh<00:13:47.120> the 00:13:47.470 --> 00:13:47.480 align:start position:0% writing for for this discussion uh the 00:13:47.480 --> 00:13:49.430 align:start position:0% writing for for this discussion uh the the<00:13:47.560> main<00:13:47.880> point<00:13:48.120> is<00:13:48.279> that<00:13:48.720> one<00:13:49.040> type<00:13:49.240> of 00:13:49.430 --> 00:13:49.440 align:start position:0% the main point is that one type of 00:13:49.440 --> 00:13:52.749 align:start position:0% the main point is that one type of incentive<00:13:50.079> that<00:13:50.240> we<00:13:50.360> do<00:13:50.600> talk<00:13:50.880> about<00:13:51.440> is<00:13:51.839> is 00:13:52.749 --> 00:13:52.759 align:start position:0% incentive that we do talk about is is 00:13:52.759 --> 00:13:55.389 align:start position:0% incentive that we do talk about is is can<00:13:53.440> appropriately<00:13:54.440> handle<00:13:54.959> the<00:13:55.240> the 00:13:55.389 --> 00:13:55.399 align:start position:0% can appropriately handle the the 00:13:55.399 --> 00:13:57.150 align:start position:0% can appropriately handle the the incentives<00:13:55.959> for 00:13:57.150 --> 00:13:57.160 align:start position:0% incentives for 00:13:57.160 --> 00:14:00.550 align:start position:0% incentives for for<00:13:58.160> for<00:13:58.360> retrieval<00:13:59.160> and<00:13:59.519> basically<00:14:00.360> which 00:14:00.550 --> 00:14:00.560 align:start position:0% for for retrieval and basically which 00:14:00.560 --> 00:14:03.110 align:start position:0% for for retrieval and basically which also<00:14:00.839> translates<00:14:01.399> to 00:14:03.110 --> 00:14:03.120 align:start position:0% also translates to 00:14:03.120 --> 00:14:06.069 align:start position:0% also translates to uh<00:14:04.120> the<00:14:04.279> pricing<00:14:04.600> of<00:14:04.800> bandwidth<00:14:05.560> basically 00:14:06.069 --> 00:14:06.079 align:start position:0% uh the pricing of bandwidth basically 00:14:06.079 --> 00:14:07.430 align:start position:0% uh the pricing of bandwidth basically because<00:14:06.360> that's<00:14:06.680> that's<00:14:06.920> that's<00:14:07.160> what<00:14:07.279> it 00:14:07.430 --> 00:14:07.440 align:start position:0% because that's that's that's what it 00:14:07.440 --> 00:14:10.670 align:start position:0% because that's that's that's what it does<00:14:08.000> as<00:14:08.160> opposed<00:14:08.480> to<00:14:08.680> like<00:14:08.880> dis<00:14:09.360> storage<00:14:10.360> uh 00:14:10.670 --> 00:14:10.680 align:start position:0% does as opposed to like dis storage uh 00:14:10.680 --> 00:14:13.110 align:start position:0% does as opposed to like dis storage uh now<00:14:10.920> for<00:14:11.160> this<00:14:11.480> we<00:14:11.639> we're<00:14:11.839> using<00:14:12.360> the<00:14:12.639> the<00:14:12.839> the 00:14:13.110 --> 00:14:13.120 align:start position:0% now for this we we're using the the the 00:14:13.120 --> 00:14:15.910 align:start position:0% now for this we we're using the the the the<00:14:13.240> swap<00:14:13.680> system<00:14:14.279> which<00:14:14.480> swaps<00:14:15.079> just<00:14:15.600> is<00:14:15.759> a 00:14:15.910 --> 00:14:15.920 align:start position:0% the swap system which swaps just is a 00:14:15.920 --> 00:14:18.470 align:start position:0% the swap system which swaps just is a kind<00:14:16.079> of<00:14:16.279> pun<00:14:17.040> that<00:14:17.320> that<00:14:17.600> that<00:14:17.680> you<00:14:17.839> basically 00:14:18.470 --> 00:14:18.480 align:start position:0% kind of pun that that that you basically 00:14:18.480 --> 00:14:21.430 align:start position:0% kind of pun that that that you basically swap<00:14:19.480> payments<00:14:20.040> and<00:14:20.240> and<00:14:20.399> service<00:14:21.040> but<00:14:21.240> on<00:14:21.360> the 00:14:21.430 --> 00:14:21.440 align:start position:0% swap payments and and service but on the 00:14:21.440 --> 00:14:23.590 align:start position:0% swap payments and and service but on the other<00:14:21.759> it's<00:14:21.920> also<00:14:22.519> abbreviation<00:14:23.079> of<00:14:23.199> swarm 00:14:23.590 --> 00:14:23.600 align:start position:0% other it's also abbreviation of swarm 00:14:23.600 --> 00:14:25.430 align:start position:0% other it's also abbreviation of swarm accounting<00:14:24.040> protocol<00:14:24.839> and<00:14:25.000> some<00:14:25.199> other 00:14:25.430 --> 00:14:25.440 align:start position:0% accounting protocol and some other 00:14:25.440 --> 00:14:29.350 align:start position:0% accounting protocol and some other things<00:14:26.360> and<00:14:27.160> the<00:14:27.279> way<00:14:27.480> it<00:14:27.639> works<00:14:28.079> is<00:14:28.480> um<00:14:28.839> is<00:14:29.240> is 00:14:29.350 --> 00:14:29.360 align:start position:0% things and the way it works is um is is 00:14:29.360 --> 00:14:32.870 align:start position:0% things and the way it works is um is is that<00:14:29.560> basically<00:14:30.079> it<00:14:30.360> allows<00:14:31.120> you<00:14:31.360> to<00:14:32.120> to 00:14:32.870 --> 00:14:32.880 align:start position:0% that basically it allows you to to 00:14:32.880 --> 00:14:37.470 align:start position:0% that basically it allows you to to account<00:14:33.920> for<00:14:34.920> for<00:14:35.360> in<00:14:35.560> general<00:14:36.480> uh<00:14:37.120> kind<00:14:37.240> of 00:14:37.470 --> 00:14:37.480 align:start position:0% account for for in general uh kind of 00:14:37.480 --> 00:14:40.550 align:start position:0% account for for in general uh kind of any<00:14:37.759> commodity<00:14:38.279> class<00:14:38.639> that<00:14:38.839> can<00:14:39.000> be<00:14:39.639> um<00:14:40.399> that 00:14:40.550 --> 00:14:40.560 align:start position:0% any commodity class that can be um that 00:14:40.560 --> 00:14:42.509 align:start position:0% any commodity class that can be um that can<00:14:40.680> be<00:14:40.839> Quantified<00:14:41.399> and<00:14:41.759> has<00:14:41.920> certain<00:14:42.199> other 00:14:42.509 --> 00:14:42.519 align:start position:0% can be Quantified and has certain other 00:14:42.519 --> 00:14:43.990 align:start position:0% can be Quantified and has certain other properties<00:14:43.040> that<00:14:43.240> that<00:14:43.360> you<00:14:43.480> can<00:14:43.600> use<00:14:43.839> this 00:14:43.990 --> 00:14:44.000 align:start position:0% properties that that you can use this 00:14:44.000 --> 00:14:46.389 align:start position:0% properties that that you can use this for<00:14:44.440> and<00:14:44.639> swarm<00:14:45.079> it's<00:14:45.279> it's<00:14:45.399> used<00:14:45.680> for<00:14:46.000> for<00:14:46.199> the 00:14:46.389 --> 00:14:46.399 align:start position:0% for and swarm it's it's used for for the 00:14:46.399 --> 00:14:49.910 align:start position:0% for and swarm it's it's used for for the for<00:14:46.600> the<00:14:46.759> accounting<00:14:47.160> of<00:14:47.720> bandwidth<00:14:48.720> and<00:14:49.639> uh 00:14:49.910 --> 00:14:49.920 align:start position:0% for the accounting of bandwidth and uh 00:14:49.920 --> 00:14:53.990 align:start position:0% for the accounting of bandwidth and uh in<00:14:50.160> in<00:14:50.440> in<00:14:50.560> swarm<00:14:51.040> you<00:14:51.199> use<00:14:51.519> a<00:14:52.519> a<00:14:52.839> checkbook<00:14:53.839> uh 00:14:53.990 --> 00:14:54.000 align:start position:0% in in in swarm you use a a checkbook uh 00:14:54.000 --> 00:14:59.310 align:start position:0% in in in swarm you use a a checkbook uh contract<00:14:54.560> on<00:14:54.759> the<00:14:55.600> um<00:14:56.600> um<00:14:57.839> blockchain<00:14:58.839> and 00:14:59.310 --> 00:14:59.320 align:start position:0% contract on the um um blockchain and 00:14:59.320 --> 00:15:02.550 align:start position:0% contract on the um um blockchain and that<00:15:00.040> allows<00:15:00.399> you<00:15:00.600> to<00:15:01.199> to<00:15:01.600> to<00:15:01.720> do<00:15:01.920> the<00:15:02.040> delayed 00:15:02.550 --> 00:15:02.560 align:start position:0% that allows you to to to do the delayed 00:15:02.560 --> 00:15:05.150 align:start position:0% that allows you to to to do the delayed payments<00:15:03.320> that<00:15:03.680> that<00:15:03.839> this<00:15:04.040> system<00:15:04.360> uses<00:15:05.000> so 00:15:05.150 --> 00:15:05.160 align:start position:0% payments that that this system uses so 00:15:05.160 --> 00:15:08.350 align:start position:0% payments that that this system uses so it's<00:15:05.360> basically<00:15:05.920> you<00:15:06.120> you<00:15:06.839> you<00:15:07.839> it's<00:15:08.079> it's<00:15:08.160> a 00:15:08.350 --> 00:15:08.360 align:start position:0% it's basically you you you it's it's a 00:15:08.360 --> 00:15:11.470 align:start position:0% it's basically you you you it's it's a it's<00:15:08.440> a<00:15:08.680> micro<00:15:09.079> payment<00:15:09.720> system<00:15:10.639> in<00:15:10.800> which<00:15:11.040> you 00:15:11.470 --> 00:15:11.480 align:start position:0% it's a micro payment system in which you 00:15:11.480 --> 00:15:14.670 align:start position:0% it's a micro payment system in which you you<00:15:11.759> you<00:15:11.880> use<00:15:12.120> a<00:15:13.079> pairwise<00:15:13.680> accounting<00:15:14.199> for 00:15:14.670 --> 00:15:14.680 align:start position:0% you you use a pairwise accounting for 00:15:14.680 --> 00:15:18.269 align:start position:0% you you use a pairwise accounting for for<00:15:15.040> peers<00:15:15.759> where<00:15:16.000> they<00:15:16.160> can<00:15:17.079> exchange<00:15:18.079> one 00:15:18.269 --> 00:15:18.279 align:start position:0% for peers where they can exchange one 00:15:18.279 --> 00:15:20.509 align:start position:0% for peers where they can exchange one unit<00:15:18.560> of<00:15:18.759> service<00:15:19.120> from<00:15:19.360> one<00:15:19.560> unit<00:15:19.839> of<00:15:20.000> service 00:15:20.509 --> 00:15:20.519 align:start position:0% unit of service from one unit of service 00:15:20.519 --> 00:15:23.710 align:start position:0% unit of service from one unit of service so<00:15:20.759> that's<00:15:21.480> cons<00:15:21.880> if<00:15:22.040> if<00:15:22.199> they<00:15:22.519> consume<00:15:23.440> and 00:15:23.710 --> 00:15:23.720 align:start position:0% so that's cons if if they consume and 00:15:23.720 --> 00:15:26.030 align:start position:0% so that's cons if if they consume and provide<00:15:24.360> the<00:15:24.519> same<00:15:24.800> amount<00:15:25.079> of<00:15:25.240> service<00:15:25.839> then 00:15:26.030 --> 00:15:26.040 align:start position:0% provide the same amount of service then 00:15:26.040 --> 00:15:29.870 align:start position:0% provide the same amount of service then their<00:15:26.199> balance<00:15:26.720> be<00:15:27.720> is<00:15:28.120> hovers<00:15:28.519> around<00:15:28.759> zero 00:15:29.870 --> 00:15:29.880 align:start position:0% their balance be is hovers around zero 00:15:29.880 --> 00:15:31.309 align:start position:0% their balance be is hovers around zero obviously<00:15:30.360> there's<00:15:30.680> there<00:15:30.800> can<00:15:30.959> be<00:15:31.160> like 00:15:31.309 --> 00:15:31.319 align:start position:0% obviously there's there can be like 00:15:31.319 --> 00:15:33.389 align:start position:0% obviously there's there can be like things<00:15:31.639> that<00:15:32.000> if<00:15:32.160> I<00:15:32.319> if<00:15:32.399> I<00:15:32.519> work<00:15:32.759> at<00:15:32.959> night<00:15:33.240> and 00:15:33.389 --> 00:15:33.399 align:start position:0% things that if I if I work at night and 00:15:33.399 --> 00:15:35.350 align:start position:0% things that if I if I work at night and the<00:15:33.519> other<00:15:33.759> person<00:15:34.160> like<00:15:34.560> you<00:15:34.680> know<00:15:34.959> download 00:15:35.350 --> 00:15:35.360 align:start position:0% the other person like you know download 00:15:35.360 --> 00:15:37.790 align:start position:0% the other person like you know download films<00:15:35.720> in<00:15:35.880> the<00:15:36.079> in<00:15:36.240> the<00:15:36.880> in<00:15:37.120> the<00:15:37.279> in<00:15:37.399> the<00:15:37.560> in<00:15:37.639> the 00:15:37.790 --> 00:15:37.800 align:start position:0% films in the in the in the in the in the 00:15:37.800 --> 00:15:39.870 align:start position:0% films in the in the in the in the in the day<00:15:38.000> there<00:15:38.160> can<00:15:38.279> be<00:15:38.519> like<00:15:38.880> vast<00:15:39.399> differences 00:15:39.870 --> 00:15:39.880 align:start position:0% day there can be like vast differences 00:15:39.880 --> 00:15:42.150 align:start position:0% day there can be like vast differences in<00:15:40.040> the<00:15:40.160> utilization<00:15:40.759> over<00:15:41.120> time<00:15:41.720> so<00:15:41.920> for 00:15:42.150 --> 00:15:42.160 align:start position:0% in the utilization over time so for 00:15:42.160 --> 00:15:44.550 align:start position:0% in the utilization over time so for these<00:15:42.399> cases<00:15:43.360> basically<00:15:43.920> when<00:15:44.240> when<00:15:44.399> the 00:15:44.550 --> 00:15:44.560 align:start position:0% these cases basically when when the 00:15:44.560 --> 00:15:46.670 align:start position:0% these cases basically when when the balance<00:15:45.040> tilts<00:15:45.560> towards<00:15:46.000> one<00:15:46.240> particular 00:15:46.670 --> 00:15:46.680 align:start position:0% balance tilts towards one particular 00:15:46.680 --> 00:15:50.110 align:start position:0% balance tilts towards one particular peer<00:15:47.399> then<00:15:47.839> the<00:15:48.440> uh<00:15:48.920> then<00:15:49.199> the<00:15:49.480> the<00:15:49.600> peer<00:15:49.880> is 00:15:50.110 --> 00:15:50.120 align:start position:0% peer then the uh then the the peer is 00:15:50.120 --> 00:15:52.949 align:start position:0% peer then the uh then the the peer is obligated<00:15:50.639> to<00:15:51.399> send<00:15:51.680> the<00:15:51.880> compensation<00:15:52.759> which 00:15:52.949 --> 00:15:52.959 align:start position:0% obligated to send the compensation which 00:15:52.959 --> 00:15:55.590 align:start position:0% obligated to send the compensation which is<00:15:53.160> an<00:15:53.360> offchain<00:15:54.120> delayed<00:15:54.600> payment<00:15:55.240> in<00:15:55.399> this 00:15:55.590 --> 00:15:55.600 align:start position:0% is an offchain delayed payment in this 00:15:55.600 --> 00:15:58.269 align:start position:0% is an offchain delayed payment in this case<00:15:56.160> it's<00:15:56.279> a<00:15:56.440> signed<00:15:56.839> check<00:15:57.800> the<00:15:57.920> signed 00:15:58.269 --> 00:15:58.279 align:start position:0% case it's a signed check the signed 00:15:58.279 --> 00:16:00.269 align:start position:0% case it's a signed check the signed check<00:15:58.680> in<00:15:59.120> this<00:15:59.360> this<00:15:59.519> type<00:15:59.680> of<00:15:59.839> offine 00:16:00.269 --> 00:16:00.279 align:start position:0% check in this this type of offine 00:16:00.279 --> 00:16:03.470 align:start position:0% check in this this type of offine offline<00:16:00.639> payments<00:16:01.079> can<00:16:01.279> be<00:16:01.800> verified<00:16:02.800> offline 00:16:03.470 --> 00:16:03.480 align:start position:0% offline payments can be verified offline 00:16:03.480 --> 00:16:06.189 align:start position:0% offline payments can be verified offline but<00:16:03.639> in<00:16:03.759> order<00:16:04.000> to<00:16:04.319> redeem<00:16:05.319> the<00:16:05.639> the<00:16:05.800> amount 00:16:06.189 --> 00:16:06.199 align:start position:0% but in order to redeem the the amount 00:16:06.199 --> 00:16:08.430 align:start position:0% but in order to redeem the the amount that<00:16:06.560> they<00:16:06.759> are<00:16:07.000> about<00:16:07.480> you<00:16:07.600> need<00:16:07.800> to<00:16:07.959> transact 00:16:08.430 --> 00:16:08.440 align:start position:0% that they are about you need to transact 00:16:08.440 --> 00:16:10.870 align:start position:0% that they are about you need to transact with<00:16:08.560> the<00:16:08.680> blockchain<00:16:09.680> and<00:16:09.800> the<00:16:10.000> transaction 00:16:10.870 --> 00:16:10.880 align:start position:0% with the blockchain and the transaction 00:16:10.880 --> 00:16:13.350 align:start position:0% with the blockchain and the transaction cost<00:16:11.199> is<00:16:11.519> is<00:16:11.800> is<00:16:12.160> burdened<00:16:12.639> on<00:16:12.839> the<00:16:13.040> on<00:16:13.160> the 00:16:13.350 --> 00:16:13.360 align:start position:0% cost is is is burdened on the on the 00:16:13.360 --> 00:16:14.790 align:start position:0% cost is is is burdened on the on the recipient<00:16:13.959> which<00:16:14.079> means<00:16:14.319> that<00:16:14.480> they<00:16:14.600> are 00:16:14.790 --> 00:16:14.800 align:start position:0% recipient which means that they are 00:16:14.800 --> 00:16:17.990 align:start position:0% recipient which means that they are incentivized<00:16:15.639> to<00:16:15.959> delay<00:16:16.759> caching<00:16:17.199> it<00:16:17.800> and 00:16:17.990 --> 00:16:18.000 align:start position:0% incentivized to delay caching it and 00:16:18.000 --> 00:16:21.230 align:start position:0% incentivized to delay caching it and thereby<00:16:18.440> save<00:16:19.399> uh<00:16:19.880> blockchain<00:16:20.560> time<00:16:21.040> and 00:16:21.230 --> 00:16:21.240 align:start position:0% thereby save uh blockchain time and 00:16:21.240 --> 00:16:24.949 align:start position:0% thereby save uh blockchain time and blockchain<00:16:22.160> uh<00:16:22.360> cost<00:16:23.319> and<00:16:23.519> also<00:16:24.040> they<00:16:24.160> are 00:16:24.949 --> 00:16:24.959 align:start position:0% blockchain uh cost and also they are 00:16:24.959 --> 00:16:27.949 align:start position:0% blockchain uh cost and also they are indirectly<00:16:25.560> incentivized<00:16:26.199> to<00:16:26.360> watch<00:16:27.319> all<00:16:27.600> the 00:16:27.949 --> 00:16:27.959 align:start position:0% indirectly incentivized to watch all the 00:16:27.959 --> 00:16:31.269 align:start position:0% indirectly incentivized to watch all the the<00:16:28.120> kind<00:16:28.240> of<00:16:28.600> um<00:16:29.399> aspects<00:16:29.880> of<00:16:30.079> their<00:16:30.319> peer 00:16:31.269 --> 00:16:31.279 align:start position:0% the kind of um aspects of their peer 00:16:31.279 --> 00:16:32.910 align:start position:0% the kind of um aspects of their peer which<00:16:31.720> make 00:16:32.910 --> 00:16:32.920 align:start position:0% which make 00:16:32.920 --> 00:16:35.189 align:start position:0% which make them<00:16:33.920> trust<00:16:34.240> them<00:16:34.399> more<00:16:34.600> so<00:16:34.800> that<00:16:34.959> they<00:16:35.079> can 00:16:35.189 --> 00:16:35.199 align:start position:0% them trust them more so that they can 00:16:35.199 --> 00:16:37.150 align:start position:0% them trust them more so that they can delay<00:16:35.560> the<00:16:35.680> payment<00:16:36.079> even<00:16:36.319> longer<00:16:36.959> so 00:16:37.150 --> 00:16:37.160 align:start position:0% delay the payment even longer so 00:16:37.160 --> 00:16:39.150 align:start position:0% delay the payment even longer so basically<00:16:37.560> it<00:16:37.720> incentivizes<00:16:38.519> the<00:16:38.680> emergence 00:16:39.150 --> 00:16:39.160 align:start position:0% basically it incentivizes the emergence 00:16:39.160 --> 00:16:42.470 align:start position:0% basically it incentivizes the emergence of<00:16:39.360> of<00:16:39.480> a<00:16:39.639> reputation<00:16:40.279> system<00:16:40.600> in<00:16:40.720> a<00:16:40.880> way<00:16:41.680> and 00:16:42.470 --> 00:16:42.480 align:start position:0% of of a reputation system in a way and 00:16:42.480 --> 00:16:43.790 align:start position:0% of of a reputation system in a way and that's<00:16:42.720> also<00:16:43.079> possible<00:16:43.480> because<00:16:43.680> the 00:16:43.790 --> 00:16:43.800 align:start position:0% that's also possible because the 00:16:43.800 --> 00:16:45.590 align:start position:0% that's also possible because the checkbook<00:16:44.240> contract<00:16:44.639> is<00:16:44.880> basically 00:16:45.590 --> 00:16:45.600 align:start position:0% checkbook contract is basically 00:16:45.600 --> 00:16:48.309 align:start position:0% checkbook contract is basically historical<00:16:46.600> it's<00:16:46.759> a<00:16:46.920> credit<00:16:47.319> record<00:16:47.959> that<00:16:48.120> you 00:16:48.309 --> 00:16:48.319 align:start position:0% historical it's a credit record that you 00:16:48.319 --> 00:16:51.949 align:start position:0% historical it's a credit record that you have<00:16:48.920> so<00:16:49.920> basically<00:16:50.759> at<00:16:50.880> the<00:16:50.959> end<00:16:51.160> of<00:16:51.279> the<00:16:51.440> day 00:16:51.949 --> 00:16:51.959 align:start position:0% have so basically at the end of the day 00:16:51.959 --> 00:16:55.790 align:start position:0% have so basically at the end of the day uh<00:16:52.160> this<00:16:52.399> this<00:16:52.600> system<00:16:53.120> can<00:16:54.079> uh<00:16:54.319> all<00:16:54.880> like<00:16:55.519> to 00:16:55.790 --> 00:16:55.800 align:start position:0% uh this this system can uh all like to 00:16:55.800 --> 00:16:58.350 align:start position:0% uh this this system can uh all like to to<00:16:56.079> to<00:16:56.240> trade<00:16:56.680> reputation<00:16:57.279> for<00:16:57.560> some<00:16:57.759> sort<00:16:58.000> of 00:16:58.350 --> 00:16:58.360 align:start position:0% to to trade reputation for some sort of 00:16:58.360 --> 00:17:02.509 align:start position:0% to to trade reputation for some sort of uh<00:16:58.600> up<00:16:59.199> deposit<00:17:00.160> and<00:17:01.079> uh<00:17:01.720> most<00:17:02.199> most 00:17:02.509 --> 00:17:02.519 align:start position:0% uh up deposit and uh most most 00:17:02.519 --> 00:17:06.309 align:start position:0% uh up deposit and uh most most importantly<00:17:03.880> um<00:17:04.880> uh<00:17:05.039> can<00:17:05.280> incentivize<00:17:06.079> the 00:17:06.309 --> 00:17:06.319 align:start position:0% importantly um uh can incentivize the 00:17:06.319 --> 00:17:08.630 align:start position:0% importantly um uh can incentivize the the<00:17:06.679> the<00:17:07.120> the<00:17:07.240> the<00:17:07.360> retrieval<00:17:07.839> and<00:17:08.000> correct 00:17:08.630 --> 00:17:08.640 align:start position:0% the the the the retrieval and correct 00:17:08.640 --> 00:17:11.150 align:start position:0% the the the the retrieval and correct working<00:17:09.000> of<00:17:09.160> the<00:17:09.400> network<00:17:10.400> now<00:17:10.640> just<00:17:10.880> just<00:17:11.000> a 00:17:11.150 --> 00:17:11.160 align:start position:0% working of the network now just just a 00:17:11.160 --> 00:17:13.750 align:start position:0% working of the network now just just a quick<00:17:11.360> summary<00:17:11.760> before<00:17:12.039> I<00:17:12.480> give<00:17:12.720> it<00:17:12.880> over<00:17:13.199> to 00:17:13.750 --> 00:17:13.760 align:start position:0% quick summary before I give it over to 00:17:13.760 --> 00:17:16.510 align:start position:0% quick summary before I give it over to uh<00:17:14.280> to<00:17:14.520> dania<00:17:15.280> who<00:17:15.400> will<00:17:15.600> talk<00:17:15.839> about<00:17:16.160> the<00:17:16.400> the 00:17:16.510 --> 00:17:16.520 align:start position:0% uh to dania who will talk about the the 00:17:16.520 --> 00:17:19.710 align:start position:0% uh to dania who will talk about the the upper<00:17:16.880> layers<00:17:17.400> and<00:17:17.640> and<00:17:17.839> some<00:17:18.400> um<00:17:19.400> some<00:17:19.520> of 00:17:19.710 --> 00:17:19.720 align:start position:0% upper layers and and some um some of 00:17:19.720 --> 00:17:22.309 align:start position:0% upper layers and and some um some of these<00:17:20.000> the<00:17:20.160> applications<00:17:20.839> for<00:17:21.079> for<00:17:21.280> deps<00:17:22.079> so 00:17:22.309 --> 00:17:22.319 align:start position:0% these the applications for for deps so 00:17:22.319 --> 00:17:25.230 align:start position:0% these the applications for for deps so just<00:17:22.439> to<00:17:22.600> summarize<00:17:23.360> so<00:17:23.600> basically<00:17:24.319> swarm<00:17:24.839> is 00:17:25.230 --> 00:17:25.240 align:start position:0% just to summarize so basically swarm is 00:17:25.240 --> 00:17:27.549 align:start position:0% just to summarize so basically swarm is defined<00:17:25.880> like<00:17:26.000> more<00:17:26.199> formally<00:17:26.799> as<00:17:26.919> a<00:17:27.280> as<00:17:27.360> a 00:17:27.549 --> 00:17:27.559 align:start position:0% defined like more formally as a as a 00:17:27.559 --> 00:17:31.310 align:start position:0% defined like more formally as a as a protocol<00:17:28.480> the<00:17:28.960> is<00:17:29.080> that<00:17:29.280> protocol<00:17:30.160> uh<00:17:30.799> which 00:17:31.310 --> 00:17:31.320 align:start position:0% protocol the is that protocol uh which 00:17:31.320 --> 00:17:33.190 align:start position:0% protocol the is that protocol uh which is<00:17:31.600> kind<00:17:31.760> of 00:17:33.190 --> 00:17:33.200 align:start position:0% is kind of 00:17:33.200 --> 00:17:36.110 align:start position:0% is kind of a<00:17:34.200> a<00:17:34.360> mix<00:17:34.840> of<00:17:35.080> several 00:17:36.110 --> 00:17:36.120 align:start position:0% a a mix of several 00:17:36.120 --> 00:17:38.950 align:start position:0% a a mix of several different<00:17:37.120> aspects<00:17:37.559> of<00:17:37.840> of<00:17:38.080> of<00:17:38.240> the<00:17:38.559> of<00:17:38.679> the<00:17:38.840> of 00:17:38.950 --> 00:17:38.960 align:start position:0% different aspects of of of the of the of 00:17:38.960 --> 00:17:40.870 align:start position:0% different aspects of of of the of the of the<00:17:39.120> system<00:17:39.600> so<00:17:39.799> basically<00:17:40.360> it's<00:17:40.520> also<00:17:40.720> a 00:17:40.870 --> 00:17:40.880 align:start position:0% the system so basically it's also a 00:17:40.880 --> 00:17:44.549 align:start position:0% the system so basically it's also a protocol<00:17:41.360> for<00:17:41.919> for<00:17:42.240> for<00:17:42.480> peer<00:17:43.160> um<00:17:43.919> selection 00:17:44.549 --> 00:17:44.559 align:start position:0% protocol for for for peer um selection 00:17:44.559 --> 00:17:49.029 align:start position:0% protocol for for for peer um selection and<00:17:44.880> peer<00:17:45.600> um<00:17:46.600> like<00:17:47.039> basically<00:17:48.039> bootstrapping 00:17:49.029 --> 00:17:49.039 align:start position:0% and peer um like basically bootstrapping 00:17:49.039 --> 00:17:50.950 align:start position:0% and peer um like basically bootstrapping your<00:17:49.280> your<00:17:49.640> your<00:17:49.799> node<00:17:50.039> and<00:17:50.200> connecting<00:17:50.679> with 00:17:50.950 --> 00:17:50.960 align:start position:0% your your your node and connecting with 00:17:50.960 --> 00:17:53.270 align:start position:0% your your your node and connecting with with<00:17:51.080> others<00:17:51.320> in<00:17:51.480> the<00:17:51.600> network<00:17:52.320> it's<00:17:52.520> also<00:17:53.160> a 00:17:53.270 --> 00:17:53.280 align:start position:0% with others in the network it's also a 00:17:53.280 --> 00:17:55.470 align:start position:0% with others in the network it's also a protocol<00:17:53.720> specifying<00:17:54.400> the<00:17:54.640> the<00:17:55.000> the<00:17:55.120> request 00:17:55.470 --> 00:17:55.480 align:start position:0% protocol specifying the the the request 00:17:55.480 --> 00:17:58.029 align:start position:0% protocol specifying the the the request forwarding<00:17:56.120> and<00:17:56.360> how<00:17:56.679> how<00:17:56.880> the<00:17:57.400> how<00:17:57.600> the 00:17:58.029 --> 00:17:58.039 align:start position:0% forwarding and how how the how the 00:17:58.039 --> 00:17:59.390 align:start position:0% forwarding and how how the how the retrieval<00:17:58.600> is 00:17:59.390 --> 00:17:59.400 align:start position:0% retrieval is 00:17:59.400 --> 00:18:01.310 align:start position:0% retrieval is and<00:17:59.520> then<00:17:59.640> the<00:17:59.760> routing<00:18:00.120> works<00:18:00.760> it's<00:18:00.919> a<00:18:01.120> it's<00:18:01.200> a 00:18:01.310 --> 00:18:01.320 align:start position:0% and then the routing works it's a it's a 00:18:01.320 --> 00:18:03.630 align:start position:0% and then the routing works it's a it's a synchronization<00:18:02.120> protocol<00:18:03.000> and<00:18:03.200> and<00:18:03.360> also 00:18:03.630 --> 00:18:03.640 align:start position:0% synchronization protocol and and also 00:18:03.640 --> 00:18:05.590 align:start position:0% synchronization protocol and and also it's<00:18:03.799> a<00:18:03.960> it's<00:18:04.039> a<00:18:04.159> swap<00:18:04.520> protocol<00:18:05.120> it's<00:18:05.320> like 00:18:05.590 --> 00:18:05.600 align:start position:0% it's a it's a swap protocol it's like 00:18:05.600 --> 00:18:08.390 align:start position:0% it's a it's a swap protocol it's like the<00:18:05.720> the<00:18:05.880> payment<00:18:06.880> it<00:18:07.280> has<00:18:07.640> maybe<00:18:08.039> maybe<00:18:08.240> a 00:18:08.390 --> 00:18:08.400 align:start position:0% the the payment it has maybe maybe a 00:18:08.400 --> 00:18:10.390 align:start position:0% the the payment it has maybe maybe a fifth<00:18:08.720> part<00:18:09.000> which<00:18:09.240> relates<00:18:09.600> to<00:18:09.760> the<00:18:09.919> storage 00:18:10.390 --> 00:18:10.400 align:start position:0% fifth part which relates to the storage 00:18:10.400 --> 00:18:12.430 align:start position:0% fifth part which relates to the storage incentives<00:18:11.039> that<00:18:11.200> we<00:18:11.520> don't<00:18:11.799> talk<00:18:12.039> about 00:18:12.430 --> 00:18:12.440 align:start position:0% incentives that we don't talk about 00:18:12.440 --> 00:18:14.350 align:start position:0% incentives that we don't talk about that's<00:18:12.720> that's<00:18:13.000> also<00:18:13.320> part<00:18:13.520> of<00:18:13.679> this<00:18:13.880> protocol 00:18:14.350 --> 00:18:14.360 align:start position:0% that's that's also part of this protocol 00:18:14.360 --> 00:18:16.070 align:start position:0% that's that's also part of this protocol that<00:18:14.480> the<00:18:14.600> communication<00:18:15.280> here<00:18:15.799> and<00:18:15.960> of 00:18:16.070 --> 00:18:16.080 align:start position:0% that the communication here and of 00:18:16.080 --> 00:18:17.789 align:start position:0% that the communication here and of course<00:18:16.280> it's<00:18:16.520> it's<00:18:16.720> it's<00:18:16.880> also<00:18:17.159> defined<00:18:17.559> by<00:18:17.679> a 00:18:17.789 --> 00:18:17.799 align:start position:0% course it's it's it's also defined by a 00:18:17.799 --> 00:18:22.470 align:start position:0% course it's it's it's also defined by a set<00:18:18.000> of<00:18:18.559> apis<00:18:19.559> uh<00:18:20.200> which<00:18:21.200> are<00:18:21.640> more<00:18:21.840> related<00:18:22.240> to 00:18:22.470 --> 00:18:22.480 align:start position:0% set of apis uh which are more related to 00:18:22.480 --> 00:18:26.669 align:start position:0% set of apis uh which are more related to what<00:18:23.360> um<00:18:24.360> Daniel<00:18:24.760> is<00:18:24.919> going<00:18:25.039> to<00:18:25.240> talk<00:18:25.440> about<00:18:25.960> so 00:18:26.669 --> 00:18:26.679 align:start position:0% what um Daniel is going to talk about so 00:18:26.679 --> 00:18:30.669 align:start position:0% what um Daniel is going to talk about so um<00:18:27.039> I<00:18:27.240> give<00:18:27.400> it<00:18:27.559> over<00:18:27.840> to<00:18:28.120> him 00:18:30.669 --> 00:18:30.679 align:start position:0% um I give it over to him 00:18:30.679 --> 00:18:35.930 align:start position:0% um I give it over to him thank 00:18:35.930 --> 00:18:35.940 align:start position:0% 00:18:35.940 --> 00:18:37.270 align:start position:0% [Applause] 00:18:37.270 --> 00:18:37.280 align:start position:0% [Applause] 00:18:37.280 --> 00:18:40.950 align:start position:0% [Applause] you<00:18:38.280> so<00:18:38.559> hello<00:18:39.080> uh<00:18:39.240> I'm<00:18:39.400> going<00:18:39.640> to<00:18:39.880> talk<00:18:40.240> about 00:18:40.950 --> 00:18:40.960 align:start position:0% you so hello uh I'm going to talk about 00:18:40.960 --> 00:18:42.990 align:start position:0% you so hello uh I'm going to talk about what<00:18:41.240> can<00:18:41.440> you<00:18:41.640> build<00:18:42.120> upon<00:18:42.440> this<00:18:42.640> solid 00:18:42.990 --> 00:18:43.000 align:start position:0% what can you build upon this solid 00:18:43.000 --> 00:18:46.310 align:start position:0% what can you build upon this solid foundation<00:18:43.679> of<00:18:44.120> a<00:18:44.360> incentivized<00:18:45.280> chunk<00:18:45.640> store 00:18:46.310 --> 00:18:46.320 align:start position:0% foundation of a incentivized chunk store 00:18:46.320 --> 00:18:50.470 align:start position:0% foundation of a incentivized chunk store so<00:18:46.559> once<00:18:47.120> uh<00:18:47.520> we<00:18:47.799> have<00:18:48.240> in<00:18:48.520> place<00:18:49.360> a<00:18:49.600> reliable 00:18:50.470 --> 00:18:50.480 align:start position:0% so once uh we have in place a reliable 00:18:50.480 --> 00:18:52.789 align:start position:0% so once uh we have in place a reliable retrieval<00:18:51.240> and<00:18:51.480> storage<00:18:51.960> infrastructure 00:18:52.789 --> 00:18:52.799 align:start position:0% retrieval and storage infrastructure 00:18:52.799 --> 00:18:57.470 align:start position:0% retrieval and storage infrastructure that<00:18:52.960> stores<00:18:53.840> fix<00:18:54.280> siiz<00:18:54.559> chunks<00:18:55.559> we<00:18:55.720> can<00:18:56.240> build 00:18:57.470 --> 00:18:57.480 align:start position:0% that stores fix siiz chunks we can build 00:18:57.480 --> 00:19:00.789 align:start position:0% that stores fix siiz chunks we can build uh<00:18:58.480> uh<00:18:58.840> web-based<00:18:59.559> distributed<00:19:00.240> applications 00:19:00.789 --> 00:19:00.799 align:start position:0% uh uh web-based distributed applications 00:19:00.799 --> 00:19:03.470 align:start position:0% uh uh web-based distributed applications on<00:19:01.039> top<00:19:01.200> of<00:19:01.440> those<00:19:01.960> and<00:19:02.280> I'm<00:19:02.480> going<00:19:02.720> to<00:19:03.000> talk 00:19:03.470 --> 00:19:03.480 align:start position:0% on top of those and I'm going to talk 00:19:03.480 --> 00:19:06.270 align:start position:0% on top of those and I'm going to talk about<00:19:04.400> these<00:19:04.720> possibilities<00:19:05.360> and<00:19:05.559> the<00:19:05.720> apis 00:19:06.270 --> 00:19:06.280 align:start position:0% about these possibilities and the apis 00:19:06.280 --> 00:19:08.149 align:start position:0% about these possibilities and the apis that<00:19:06.400> we<00:19:06.600> provide<00:19:07.000> for<00:19:07.240> application 00:19:08.149 --> 00:19:08.159 align:start position:0% that we provide for application 00:19:08.159 --> 00:19:11.350 align:start position:0% that we provide for application developers<00:19:09.159> so<00:19:09.600> the<00:19:09.799> most<00:19:10.120> important<00:19:10.799> I<00:19:10.919> think 00:19:11.350 --> 00:19:11.360 align:start position:0% developers so the most important I think 00:19:11.360 --> 00:19:16.029 align:start position:0% developers so the most important I think is<00:19:11.640> the<00:19:11.840> HTTP<00:19:12.600> based<00:19:13.320> API<00:19:14.320> which<00:19:14.919> uh<00:19:15.360> really 00:19:16.029 --> 00:19:16.039 align:start position:0% is the HTTP based API which uh really 00:19:16.039 --> 00:19:20.430 align:start position:0% is the HTTP based API which uh really acts<00:19:16.559> like<00:19:17.039> a<00:19:17.880> locally<00:19:18.320> running<00:19:18.760> web<00:19:19.440> server 00:19:20.430 --> 00:19:20.440 align:start position:0% acts like a locally running web server 00:19:20.440 --> 00:19:23.950 align:start position:0% acts like a locally running web server uh<00:19:20.559> with<00:19:20.720> the<00:19:20.960> guarantee<00:19:21.640> that<00:19:21.840> the<00:19:22.200> usual 00:19:23.950 --> 00:19:23.960 align:start position:0% uh with the guarantee that the usual 00:19:23.960 --> 00:19:27.510 align:start position:0% uh with the guarantee that the usual uh<00:19:24.960> methods<00:19:25.480> the<00:19:25.600> usual<00:19:25.919> HTTP<00:19:26.600> based<00:19:27.000> methods 00:19:27.510 --> 00:19:27.520 align:start position:0% uh methods the usual HTTP based methods 00:19:27.520 --> 00:19:30.430 align:start position:0% uh methods the usual HTTP based methods are<00:19:27.880> all<00:19:28.240> efficient<00:19:28.840> so<00:19:29.080> you<00:19:29.240> can<00:19:30.039> change 00:19:30.430 --> 00:19:30.440 align:start position:0% are all efficient so you can change 00:19:30.440 --> 00:19:34.029 align:start position:0% are all efficient so you can change single<00:19:30.960> files<00:19:31.400> you<00:19:31.520> can<00:19:31.799> retrieve<00:19:32.720> uh<00:19:33.679> via 00:19:34.029 --> 00:19:34.039 align:start position:0% single files you can retrieve uh via 00:19:34.039 --> 00:19:37.230 align:start position:0% single files you can retrieve uh via range<00:19:34.440> queries<00:19:35.440> uh<00:19:36.120> some<00:19:36.400> portion<00:19:36.880> of<00:19:37.039> the 00:19:37.230 --> 00:19:37.240 align:start position:0% range queries uh some portion of the 00:19:37.240 --> 00:19:40.990 align:start position:0% range queries uh some portion of the file<00:19:37.760> which<00:19:38.080> allows<00:19:38.559> for<00:19:39.240> uh<00:19:39.760> streaming<00:19:40.760> and 00:19:40.990 --> 00:19:41.000 align:start position:0% file which allows for uh streaming and 00:19:41.000 --> 00:19:44.750 align:start position:0% file which allows for uh streaming and you<00:19:41.159> can<00:19:41.480> change<00:19:42.600> uh<00:19:43.600> uh<00:19:43.760> the<00:19:43.960> content<00:19:44.400> of<00:19:44.520> your 00:19:44.750 --> 00:19:44.760 align:start position:0% you can change uh uh the content of your 00:19:44.760 --> 00:19:47.630 align:start position:0% you can change uh uh the content of your virtual<00:19:45.200> web<00:19:45.880> server<00:19:46.880> uh<00:19:47.080> which<00:19:47.240> of<00:19:47.400> course 00:19:47.630 --> 00:19:47.640 align:start position:0% virtual web server uh which of course 00:19:47.640 --> 00:19:49.230 align:start position:0% virtual web server uh which of course raises<00:19:48.039> the<00:19:48.240> question<00:19:48.600> that<00:19:48.840> this<00:19:49.000> whole 00:19:49.230 --> 00:19:49.240 align:start position:0% raises the question that this whole 00:19:49.240 --> 00:19:51.350 align:start position:0% raises the question that this whole thing<00:19:49.520> is<00:19:49.720> content<00:19:50.200> addressed<00:19:50.799> so<00:19:51.080> what 00:19:51.350 --> 00:19:51.360 align:start position:0% thing is content addressed so what 00:19:51.360 --> 00:19:52.990 align:start position:0% thing is content addressed so what actually<00:19:51.799> happens<00:19:52.200> when<00:19:52.400> you<00:19:52.679> change 00:19:52.990 --> 00:19:53.000 align:start position:0% actually happens when you change 00:19:53.000 --> 00:19:56.270 align:start position:0% actually happens when you change something<00:19:53.640> so<00:19:53.840> here<00:19:53.960> are<00:19:54.120> a<00:19:54.200> few<00:19:54.440> URL<00:19:55.280> examples 00:19:56.270 --> 00:19:56.280 align:start position:0% something so here are a few URL examples 00:19:56.280 --> 00:19:58.950 align:start position:0% something so here are a few URL examples in<00:19:56.440> the<00:19:56.640> first<00:19:57.080> case<00:19:57.720> you're<00:19:58.080> accessing<00:19:58.799> the 00:19:58.950 --> 00:19:58.960 align:start position:0% in the first case you're accessing the 00:19:58.960 --> 00:20:01.549 align:start position:0% in the first case you're accessing the raw<00:19:59.440> API<00:20:00.440> which<00:20:00.600> means<00:20:00.960> that<00:20:01.080> you're<00:20:01.320> just 00:20:01.549 --> 00:20:01.559 align:start position:0% raw API which means that you're just 00:20:01.559 --> 00:20:05.789 align:start position:0% raw API which means that you're just downloading<00:20:02.320> without<00:20:02.679> any<00:20:03.559> metadata<00:20:04.559> a<00:20:05.360> large 00:20:05.789 --> 00:20:05.799 align:start position:0% downloading without any metadata a large 00:20:05.799 --> 00:20:10.149 align:start position:0% downloading without any metadata a large set<00:20:06.080> of<00:20:06.799> bits<00:20:07.159> or<00:20:07.880> bytes<00:20:08.880> and<00:20:09.120> then<00:20:09.840> uh<00:20:09.960> the 00:20:10.149 --> 00:20:10.159 align:start position:0% set of bits or bytes and then uh the 00:20:10.159 --> 00:20:14.990 align:start position:0% set of bits or bytes and then uh the next<00:20:10.520> one<00:20:11.480> is<00:20:12.120> a<00:20:13.120> swarm<00:20:13.760> site<00:20:14.320> which<00:20:14.440> is<00:20:14.559> a<00:20:14.760> root 00:20:14.990 --> 00:20:15.000 align:start position:0% next one is a swarm site which is a root 00:20:15.000 --> 00:20:17.350 align:start position:0% next one is a swarm site which is a root page<00:20:15.200> of<00:20:15.280> a<00:20:15.440> web<00:20:15.679> server<00:20:16.080> I<00:20:16.240> actually<00:20:16.600> have<00:20:16.760> it 00:20:17.350 --> 00:20:17.360 align:start position:0% page of a web server I actually have it 00:20:17.360 --> 00:20:26.510 align:start position:0% page of a web server I actually have it here 00:20:26.510 --> 00:20:26.520 align:start position:0% 00:20:26.520 --> 00:20:29.710 align:start position:0% uh<00:20:27.520> so<00:20:28.039> it's<00:20:28.360> it's<00:20:28.720> it's<00:20:28.960> here<00:20:29.320> this<00:20:29.440> is<00:20:29.520> a 00:20:29.710 --> 00:20:29.720 align:start position:0% uh so it's it's it's here this is a 00:20:29.720 --> 00:20:31.549 align:start position:0% uh so it's it's it's here this is a photo 00:20:31.549 --> 00:20:31.559 align:start position:0% photo 00:20:31.559 --> 00:20:33.110 align:start position:0% photo album 00:20:33.110 --> 00:20:33.120 align:start position:0% album 00:20:33.120 --> 00:20:37.110 align:start position:0% album uh<00:20:34.120> so<00:20:34.440> this<00:20:34.600> is<00:20:34.840> a<00:20:35.360> photo<00:20:35.760> album<00:20:36.480> and<00:20:36.840> if<00:20:36.919> you 00:20:37.110 --> 00:20:37.120 align:start position:0% uh so this is a photo album and if you 00:20:37.120 --> 00:20:39.549 align:start position:0% uh so this is a photo album and if you click<00:20:37.440> around<00:20:38.400> then<00:20:38.600> you<00:20:38.720> can<00:20:38.960> see<00:20:39.320> that 00:20:39.549 --> 00:20:39.559 align:start position:0% click around then you can see that 00:20:39.559 --> 00:20:42.750 align:start position:0% click around then you can see that there's<00:20:39.880> a<00:20:40.360> part<00:20:40.760> of<00:20:41.000> the<00:20:41.200> URL<00:20:41.880> which<00:20:42.039> is<00:20:42.360> just 00:20:42.750 --> 00:20:42.760 align:start position:0% there's a part of the URL which is just 00:20:42.760 --> 00:20:46.950 align:start position:0% there's a part of the URL which is just the<00:20:43.360> uh<00:20:44.280> the<00:20:44.520> fragment<00:20:45.159> part<00:20:45.880> which<00:20:46.159> is<00:20:46.440> not<00:20:46.720> a 00:20:46.950 --> 00:20:46.960 align:start position:0% the uh the fragment part which is not a 00:20:46.960 --> 00:20:48.909 align:start position:0% the uh the fragment part which is not a state<00:20:47.320> that<00:20:47.480> you<00:20:47.600> want<00:20:47.799> to<00:20:47.960> share<00:20:48.360> it<00:20:48.600> just 00:20:48.909 --> 00:20:48.919 align:start position:0% state that you want to share it just 00:20:48.919 --> 00:20:50.630 align:start position:0% state that you want to share it just which<00:20:49.159> picture<00:20:49.480> are<00:20:49.640> you<00:20:49.799> looking<00:20:50.120> at<00:20:50.320> so<00:20:50.520> this 00:20:50.630 --> 00:20:50.640 align:start position:0% which picture are you looking at so this 00:20:50.640 --> 00:20:53.350 align:start position:0% which picture are you looking at so this is<00:20:50.760> a<00:20:50.919> state<00:20:51.240> that<00:20:51.400> only<00:20:51.720> exists<00:20:52.360> locally 00:20:53.350 --> 00:20:53.360 align:start position:0% is a state that only exists locally 00:20:53.360 --> 00:20:55.590 align:start position:0% is a state that only exists locally however<00:20:54.120> if<00:20:54.320> you 00:20:55.590 --> 00:20:55.600 align:start position:0% however if you 00:20:55.600 --> 00:21:00.789 align:start position:0% however if you delete<00:20:56.640> uh<00:20:57.640> a<00:20:57.840> certain<00:20:58.240> picture 00:21:00.789 --> 00:21:00.799 align:start position:0% 00:21:00.799 --> 00:21:03.149 align:start position:0% that<00:21:01.000> means<00:21:01.400> that<00:21:01.640> as<00:21:01.760> you<00:21:01.919> can<00:21:02.159> see<00:21:02.720> even<00:21:03.039> the 00:21:03.149 --> 00:21:03.159 align:start position:0% that means that as you can see even the 00:21:03.159 --> 00:21:06.110 align:start position:0% that means that as you can see even the root<00:21:03.559> has<00:21:03.799> changes<00:21:04.799> and<00:21:05.000> once<00:21:05.240> you<00:21:05.400> share<00:21:05.919> this 00:21:06.110 --> 00:21:06.120 align:start position:0% root has changes and once you share this 00:21:06.120 --> 00:21:10.830 align:start position:0% root has changes and once you share this one<00:21:07.080> then<00:21:07.799> the<00:21:08.799> uh<00:21:09.799> the<00:21:09.960> entire<00:21:10.400> content 00:21:10.830 --> 00:21:10.840 align:start position:0% one then the uh the entire content 00:21:10.840 --> 00:21:12.950 align:start position:0% one then the uh the entire content changes<00:21:11.600> and<00:21:11.840> if<00:21:11.960> you<00:21:12.159> rearrange<00:21:12.799> the 00:21:12.950 --> 00:21:12.960 align:start position:0% changes and if you rearrange the 00:21:12.960 --> 00:21:14.870 align:start position:0% changes and if you rearrange the pictures<00:21:13.360> or<00:21:13.520> you<00:21:13.679> upload<00:21:14.080> the<00:21:14.200> pictures<00:21:14.720> the 00:21:14.870 --> 00:21:14.880 align:start position:0% pictures or you upload the pictures the 00:21:14.880 --> 00:21:16.710 align:start position:0% pictures or you upload the pictures the exact<00:21:15.159> same<00:21:15.360> thing<00:21:15.559> will<00:21:15.760> happen<00:21:16.080> the<00:21:16.200> root 00:21:16.710 --> 00:21:16.720 align:start position:0% exact same thing will happen the root 00:21:16.720 --> 00:21:21.350 align:start position:0% exact same thing will happen the root the<00:21:16.840> root<00:21:17.200> has<00:21:17.600> root<00:21:18.000> hash<00:21:19.039> changes<00:21:20.039> and<00:21:20.640> uh 00:21:21.350 --> 00:21:21.360 align:start position:0% the root has root hash changes and uh 00:21:21.360 --> 00:21:23.230 align:start position:0% the root has root hash changes and uh therefore<00:21:21.760> you<00:21:21.880> can<00:21:22.039> share<00:21:22.480> that<00:21:22.720> state<00:21:23.080> with 00:21:23.230 --> 00:21:23.240 align:start position:0% therefore you can share that state with 00:21:23.240 --> 00:21:26.269 align:start position:0% therefore you can share that state with others<00:21:24.240> and<00:21:24.400> you<00:21:24.559> can<00:21:24.799> do<00:21:25.159> that<00:21:25.679> through<00:21:26.039> a 00:21:26.269 --> 00:21:26.279 align:start position:0% others and you can do that through a 00:21:26.279 --> 00:21:28.710 align:start position:0% others and you can do that through a name<00:21:26.640> registry<00:21:27.279> contract<00:21:28.080> so<00:21:28.279> for<00:21:28.600> for 00:21:28.710 --> 00:21:28.720 align:start position:0% name registry contract so for for 00:21:28.720 --> 00:21:31.590 align:start position:0% name registry contract so for for example<00:21:29.200> this<00:21:29.360> URL<00:21:30.000> here<00:21:30.279> clipped<00:21:30.720> Wings 00:21:31.590 --> 00:21:31.600 align:start position:0% example this URL here clipped Wings 00:21:31.600 --> 00:21:35.789 align:start position:0% example this URL here clipped Wings would<00:21:31.840> be<00:21:32.279> always<00:21:32.960> the<00:21:33.480> current<00:21:34.480> state<00:21:35.480> of 00:21:35.789 --> 00:21:35.799 align:start position:0% would be always the current state of 00:21:35.799 --> 00:21:39.310 align:start position:0% would be always the current state of this<00:21:36.000> photo<00:21:36.480> album<00:21:37.480> but<00:21:37.760> this<00:21:38.400> uh<00:21:38.640> so<00:21:39.120> the 00:21:39.310 --> 00:21:39.320 align:start position:0% this photo album but this uh so the 00:21:39.320 --> 00:21:42.870 align:start position:0% this photo album but this uh so the Nexus<00:21:40.000> with<00:21:40.279> ethereum<00:21:40.840> blockchain<00:21:41.679> is<00:21:42.640> first 00:21:42.870 --> 00:21:42.880 align:start position:0% Nexus with ethereum blockchain is first 00:21:42.880 --> 00:21:45.190 align:start position:0% Nexus with ethereum blockchain is first of<00:21:43.039> all<00:21:43.240> the<00:21:43.440> Swarm<00:21:43.919> naming<00:21:44.320> system<00:21:44.880> which<00:21:45.000> is 00:21:45.190 --> 00:21:45.200 align:start position:0% of all the Swarm naming system which is 00:21:45.200 --> 00:21:47.070 align:start position:0% of all the Swarm naming system which is just<00:21:45.360> a<00:21:45.520> single<00:21:45.960> contract<00:21:46.480> where<00:21:46.640> you<00:21:46.799> can 00:21:47.070 --> 00:21:47.080 align:start position:0% just a single contract where you can 00:21:47.080 --> 00:21:51.750 align:start position:0% just a single contract where you can register<00:21:47.559> root<00:21:48.159> hashes<00:21:49.159> for<00:21:50.000> uh<00:21:50.400> for<00:21:50.880> for 00:21:51.750 --> 00:21:51.760 align:start position:0% register root hashes for uh for for 00:21:51.760 --> 00:21:53.830 align:start position:0% register root hashes for uh for for names<00:21:52.760> then<00:21:52.919> there's<00:21:53.200> this<00:21:53.400> content 00:21:53.830 --> 00:21:53.840 align:start position:0% names then there's this content 00:21:53.840 --> 00:21:55.950 align:start position:0% names then there's this content availability<00:21:54.640> Insurance<00:21:55.320> where<00:21:55.480> you<00:21:55.600> can<00:21:55.799> put 00:21:55.950 --> 00:21:55.960 align:start position:0% availability Insurance where you can put 00:21:55.960 --> 00:21:59.110 align:start position:0% availability Insurance where you can put up<00:21:56.200> a<00:21:56.559> deposit<00:21:57.559> for<00:21:57.960> making<00:21:58.679> sure<00:21:58.880> that<00:21:59.000> a 00:21:59.110 --> 00:21:59.120 align:start position:0% up a deposit for making sure that a 00:21:59.120 --> 00:22:01.750 align:start position:0% up a deposit for making sure that a certain<00:21:59.480> contract<00:21:59.919> is<00:22:00.559> uh<00:22:00.960> certain<00:22:01.320> content 00:22:01.750 --> 00:22:01.760 align:start position:0% certain contract is uh certain content 00:22:01.760 --> 00:22:04.350 align:start position:0% certain contract is uh certain content is<00:22:01.960> available<00:22:02.919> and<00:22:03.120> If<00:22:03.279> somebody<00:22:03.760> challenges 00:22:04.350 --> 00:22:04.360 align:start position:0% is available and If somebody challenges 00:22:04.360 --> 00:22:06.390 align:start position:0% is available and If somebody challenges You<00:22:04.640> by<00:22:04.760> saying<00:22:05.120> that<00:22:05.360> this<00:22:05.559> particular<00:22:06.039> chunk 00:22:06.390 --> 00:22:06.400 align:start position:0% You by saying that this particular chunk 00:22:06.400 --> 00:22:08.870 align:start position:0% You by saying that this particular chunk that<00:22:06.640> you<00:22:06.840> promised<00:22:07.600> is<00:22:07.760> not<00:22:08.120> there<00:22:08.559> unless 00:22:08.870 --> 00:22:08.880 align:start position:0% that you promised is not there unless 00:22:08.880 --> 00:22:10.510 align:start position:0% that you promised is not there unless you<00:22:09.080> upload<00:22:09.520> that<00:22:09.720> you<00:22:09.799> will<00:22:10.000> lose<00:22:10.279> that 00:22:10.510 --> 00:22:10.520 align:start position:0% you upload that you will lose that 00:22:10.520 --> 00:22:13.110 align:start position:0% you upload that you will lose that deposit<00:22:11.080> and<00:22:11.360> possibly<00:22:11.880> the<00:22:12.120> person<00:22:12.799> gets 00:22:13.110 --> 00:22:13.120 align:start position:0% deposit and possibly the person gets 00:22:13.120 --> 00:22:14.310 align:start position:0% deposit and possibly the person gets rewarded 00:22:14.310 --> 00:22:14.320 align:start position:0% rewarded 00:22:14.320 --> 00:22:16.950 align:start position:0% rewarded for<00:22:15.320> uh<00:22:15.840> for<00:22:16.159> the 00:22:16.950 --> 00:22:16.960 align:start position:0% for uh for the 00:22:16.960 --> 00:22:20.549 align:start position:0% for uh for the trouble<00:22:17.960> uh<00:22:18.760> then<00:22:19.000> you<00:22:19.120> can<00:22:19.400> also<00:22:19.720> store<00:22:20.240> off 00:22:20.549 --> 00:22:20.559 align:start position:0% trouble uh then you can also store off 00:22:20.559 --> 00:22:23.269 align:start position:0% trouble uh then you can also store off blockchain<00:22:21.200> State<00:22:21.760> so<00:22:22.360> uh<00:22:22.559> this<00:22:22.720> refers<00:22:23.120> a 00:22:23.269 --> 00:22:23.279 align:start position:0% blockchain State so uh this refers a 00:22:23.279 --> 00:22:26.070 align:start position:0% blockchain State so uh this refers a little<00:22:23.520> bit<00:22:23.880> back<00:22:24.080> to<00:22:24.360> the<00:22:25.000> uh<00:22:25.200> scalability 00:22:26.070 --> 00:22:26.080 align:start position:0% little bit back to the uh scalability 00:22:26.080 --> 00:22:29.269 align:start position:0% little bit back to the uh scalability talk<00:22:26.760> so<00:22:27.080> one<00:22:27.400> way<00:22:27.760> of<00:22:28.000> thinking<00:22:28.799> about 00:22:29.269 --> 00:22:29.279 align:start position:0% talk so one way of thinking about 00:22:29.279 --> 00:22:30.990 align:start position:0% talk so one way of thinking about somewhat<00:22:29.679> scalable<00:22:30.320> distributed 00:22:30.990 --> 00:22:31.000 align:start position:0% somewhat scalable distributed 00:22:31.000 --> 00:22:34.029 align:start position:0% somewhat scalable distributed applications<00:22:32.000> given<00:22:32.640> a<00:22:33.360> traditional 00:22:34.029 --> 00:22:34.039 align:start position:0% applications given a traditional 00:22:34.039 --> 00:22:36.230 align:start position:0% applications given a traditional blockchain<00:22:34.960> is<00:22:35.159> that<00:22:35.279> you<00:22:35.480> treat<00:22:35.840> the 00:22:36.230 --> 00:22:36.240 align:start position:0% blockchain is that you treat the 00:22:36.240 --> 00:22:39.310 align:start position:0% blockchain is that you treat the blockchain<00:22:37.240> as<00:22:37.559> an<00:22:37.760> Arbiter<00:22:38.279> of<00:22:38.480> disputes<00:22:39.159> and 00:22:39.310 --> 00:22:39.320 align:start position:0% blockchain as an Arbiter of disputes and 00:22:39.320 --> 00:22:40.990 align:start position:0% blockchain as an Arbiter of disputes and as<00:22:39.480> long<00:22:39.640> as<00:22:39.799> you<00:22:39.880> don't<00:22:40.159> have<00:22:40.400> disputes<00:22:40.880> you 00:22:40.990 --> 00:22:41.000 align:start position:0% as long as you don't have disputes you 00:22:41.000 --> 00:22:44.029 align:start position:0% as long as you don't have disputes you don't<00:22:41.279> consult<00:22:42.120> the<00:22:42.600> the<00:22:42.840> the<00:22:43.000> consensus<00:22:43.720> the 00:22:44.029 --> 00:22:44.039 align:start position:0% don't consult the the the consensus the 00:22:44.039 --> 00:22:46.350 align:start position:0% don't consult the the the consensus the uh<00:22:44.159> bantine<00:22:44.760> consensus<00:22:45.240> of<00:22:45.400> the<00:22:45.559> blockchain 00:22:46.350 --> 00:22:46.360 align:start position:0% uh bantine consensus of the blockchain 00:22:46.360 --> 00:22:49.590 align:start position:0% uh bantine consensus of the blockchain but<00:22:46.520> if<00:22:46.679> there<00:22:46.840> is<00:22:47.039> a<00:22:48.039> is<00:22:48.159> a<00:22:48.480> problem<00:22:49.400> a 00:22:49.590 --> 00:22:49.600 align:start position:0% but if there is a is a problem a 00:22:49.600 --> 00:22:51.990 align:start position:0% but if there is a is a problem a disagreement<00:22:50.240> then<00:22:50.400> you<00:22:50.559> resolve<00:22:50.919> it<00:22:51.120> through 00:22:51.990 --> 00:22:52.000 align:start position:0% disagreement then you resolve it through 00:22:52.000 --> 00:22:56.190 align:start position:0% disagreement then you resolve it through the<00:22:53.000> uh<00:22:53.440> through<00:22:53.840> the<00:22:54.400> uh<00:22:55.000> blockchain<00:22:56.000> and 00:22:56.190 --> 00:22:56.200 align:start position:0% the uh through the uh blockchain and 00:22:56.200 --> 00:22:58.669 align:start position:0% the uh through the uh blockchain and there<00:22:56.320> are<00:22:56.520> all<00:22:56.760> these<00:22:57.039> other<00:22:57.520> things<00:22:58.039> which 00:22:58.669 --> 00:22:58.679 align:start position:0% there are all these other things which 00:22:58.679 --> 00:23:02.430 align:start position:0% there are all these other things which kind<00:22:58.880> of<00:22:59.120> Link<00:22:59.880> swarm<00:23:00.440> to<00:23:00.840> to 00:23:02.430 --> 00:23:02.440 align:start position:0% kind of Link swarm to to 00:23:02.440 --> 00:23:05.870 align:start position:0% kind of Link swarm to to ethereum 00:23:05.870 --> 00:23:05.880 align:start position:0% 00:23:05.880 --> 00:23:09.950 align:start position:0% uh<00:23:06.880> so<00:23:07.640> the<00:23:08.279> uh<00:23:08.440> distributed<00:23:09.080> application<00:23:09.799> the 00:23:09.950 --> 00:23:09.960 align:start position:0% uh so the uh distributed application the 00:23:09.960 --> 00:23:12.190 align:start position:0% uh so the uh distributed application the photo<00:23:10.320> album<00:23:10.679> that<00:23:10.840> I<00:23:10.960> have<00:23:11.120> shown<00:23:11.880> is 00:23:12.190 --> 00:23:12.200 align:start position:0% photo album that I have shown is 00:23:12.200 --> 00:23:14.870 align:start position:0% photo album that I have shown is basically<00:23:12.720> the<00:23:12.919> simplest<00:23:13.520> distributed<00:23:14.200> app 00:23:14.870 --> 00:23:14.880 align:start position:0% basically the simplest distributed app 00:23:14.880 --> 00:23:17.350 align:start position:0% basically the simplest distributed app because<00:23:15.159> you<00:23:15.320> have<00:23:15.520> one<00:23:15.799> producer<00:23:16.720> many 00:23:17.350 --> 00:23:17.360 align:start position:0% because you have one producer many 00:23:17.360 --> 00:23:20.549 align:start position:0% because you have one producer many consumers<00:23:18.360> so<00:23:18.799> you<00:23:19.039> kind<00:23:19.200> of<00:23:19.400> Sid<00:23:19.799> step<00:23:20.159> the 00:23:20.549 --> 00:23:20.559 align:start position:0% consumers so you kind of Sid step the 00:23:20.559 --> 00:23:22.590 align:start position:0% consumers so you kind of Sid step the difficult<00:23:20.840> problems<00:23:21.320> there's<00:23:21.520> no<00:23:21.720> concurrent 00:23:22.590 --> 00:23:22.600 align:start position:0% difficult problems there's no concurrent 00:23:22.600 --> 00:23:25.470 align:start position:0% difficult problems there's no concurrent modification<00:23:23.600> changes<00:23:24.320> don't<00:23:24.760> happen 00:23:25.470 --> 00:23:25.480 align:start position:0% modification changes don't happen 00:23:25.480 --> 00:23:29.149 align:start position:0% modification changes don't happen frequently<00:23:26.480> and<00:23:26.960> uh<00:23:27.159> latency<00:23:27.720> is<00:23:27.919> accept<00:23:28.799> is 00:23:29.149 --> 00:23:29.159 align:start position:0% frequently and uh latency is accept is 00:23:29.159 --> 00:23:31.789 align:start position:0% frequently and uh latency is accept is acceptable<00:23:29.760> like<00:23:30.000> if<00:23:30.200> others<00:23:30.559> see<00:23:31.200> your<00:23:31.480> photo 00:23:31.789 --> 00:23:31.799 align:start position:0% acceptable like if others see your photo 00:23:31.799 --> 00:23:34.310 align:start position:0% acceptable like if others see your photo albums<00:23:32.240> changes<00:23:33.080> after<00:23:33.480> a<00:23:33.600> few<00:23:33.840> minutes<00:23:34.159> or 00:23:34.310 --> 00:23:34.320 align:start position:0% albums changes after a few minutes or 00:23:34.320 --> 00:23:37.590 align:start position:0% albums changes after a few minutes or even<00:23:34.600> hours<00:23:35.360> that's<00:23:35.559> not<00:23:35.760> really<00:23:36.000> a<00:23:36.120> big<00:23:36.600> issue 00:23:37.590 --> 00:23:37.600 align:start position:0% even hours that's not really a big issue 00:23:37.600 --> 00:23:40.190 align:start position:0% even hours that's not really a big issue however<00:23:37.960> it's<00:23:38.240> interesting<00:23:38.840> to<00:23:39.080> think<00:23:39.559> about 00:23:40.190 --> 00:23:40.200 align:start position:0% however it's interesting to think about 00:23:40.200 --> 00:23:44.190 align:start position:0% however it's interesting to think about how<00:23:40.440> would<00:23:40.679> you<00:23:41.400> go<00:23:41.720> from<00:23:42.000> web<00:23:42.320> 2<00:23:43.240> to<00:23:43.559> web<00:23:43.840> 3 00:23:44.190 --> 00:23:44.200 align:start position:0% how would you go from web 2 to web 3 00:23:44.200 --> 00:23:47.789 align:start position:0% how would you go from web 2 to web 3 like<00:23:44.360> how<00:23:44.600> do<00:23:44.720> you<00:23:44.880> build<00:23:45.440> complex<00:23:46.520> concurrent 00:23:47.789 --> 00:23:47.799 align:start position:0% like how do you build complex concurrent 00:23:47.799 --> 00:23:50.870 align:start position:0% like how do you build complex concurrent uh<00:23:48.799> uh<00:23:48.960> distributed<00:23:49.640> applications<00:23:50.480> and<00:23:50.679> we 00:23:50.870 --> 00:23:50.880 align:start position:0% uh uh distributed applications and we 00:23:50.880 --> 00:23:54.110 align:start position:0% uh uh distributed applications and we think<00:23:51.440> uh<00:23:51.559> and<00:23:51.720> we<00:23:51.919> hope<00:23:52.480> that<00:23:52.799> swarm<00:23:53.360> as<00:23:53.440> an 00:23:54.110 --> 00:23:54.120 align:start position:0% think uh and we hope that swarm as an 00:23:54.120 --> 00:23:57.269 align:start position:0% think uh and we hope that swarm as an infrastructure<00:23:55.120> together<00:23:55.559> with<00:23:55.919> ethereum<00:23:56.919> is 00:23:57.269 --> 00:23:57.279 align:start position:0% infrastructure together with ethereum is 00:23:57.279 --> 00:23:59.669 align:start position:0% infrastructure together with ethereum is actually<00:23:57.880> suitable<00:23:58.520> for<00:23:58.720> this<00:23:58.919> purpose<00:23:59.320> so<00:23:59.520> in 00:23:59.669 --> 00:23:59.679 align:start position:0% actually suitable for this purpose so in 00:23:59.679 --> 00:24:01.830 align:start position:0% actually suitable for this purpose so in case<00:23:59.960> you<00:24:00.120> want<00:24:00.360> to<00:24:00.559> do<00:24:01.120> something<00:24:01.559> like 00:24:01.830 --> 00:24:01.840 align:start position:0% case you want to do something like 00:24:01.840 --> 00:24:03.269 align:start position:0% case you want to do something like Facebook<00:24:02.400> where 00:24:03.269 --> 00:24:03.279 align:start position:0% Facebook where 00:24:03.279 --> 00:24:06.029 align:start position:0% Facebook where multiple<00:24:04.279> uh<00:24:04.679> users<00:24:05.159> can<00:24:05.400> comment<00:24:05.720> on<00:24:05.919> the 00:24:06.029 --> 00:24:06.039 align:start position:0% multiple uh users can comment on the 00:24:06.039 --> 00:24:08.390 align:start position:0% multiple uh users can comment on the same<00:24:06.400> content<00:24:07.080> then<00:24:07.320> of<00:24:07.480> course<00:24:07.679> you<00:24:07.840> need<00:24:08.120> to 00:24:08.390 --> 00:24:08.400 align:start position:0% same content then of course you need to 00:24:08.400 --> 00:24:11.789 align:start position:0% same content then of course you need to con<00:24:08.760> to<00:24:09.520> to<00:24:10.279> uh<00:24:10.960> transact<00:24:11.520> with<00:24:11.679> the 00:24:11.789 --> 00:24:11.799 align:start position:0% con to to uh transact with the 00:24:11.799 --> 00:24:13.950 align:start position:0% con to to uh transact with the blockchain<00:24:12.480> more<00:24:12.720> often<00:24:13.120> and<00:24:13.279> to<00:24:13.440> query<00:24:13.840> the 00:24:13.950 --> 00:24:13.960 align:start position:0% blockchain more often and to query the 00:24:13.960 --> 00:24:16.110 align:start position:0% blockchain more often and to query the blockchain<00:24:14.480> more<00:24:14.640> often<00:24:14.960> to<00:24:15.120> see<00:24:15.760> what<00:24:15.960> the 00:24:16.110 --> 00:24:16.120 align:start position:0% blockchain more often to see what the 00:24:16.120 --> 00:24:19.510 align:start position:0% blockchain more often to see what the actual<00:24:16.600> status<00:24:17.480> of<00:24:17.640> a<00:24:17.880> particular<00:24:18.440> content<00:24:19.000> is 00:24:19.510 --> 00:24:19.520 align:start position:0% actual status of a particular content is 00:24:19.520 --> 00:24:21.789 align:start position:0% actual status of a particular content is and<00:24:19.679> you<00:24:19.840> also<00:24:20.159> need<00:24:20.480> something<00:24:20.880> like<00:24:21.080> whisper 00:24:21.789 --> 00:24:21.799 align:start position:0% and you also need something like whisper 00:24:21.799 --> 00:24:25.470 align:start position:0% and you also need something like whisper to<00:24:22.039> distribute<00:24:23.000> uh<00:24:23.320> real<00:24:23.679> time<00:24:24.120> uh<00:24:24.240> commenting 00:24:25.470 --> 00:24:25.480 align:start position:0% to distribute uh real time uh commenting 00:24:25.480 --> 00:24:28.909 align:start position:0% to distribute uh real time uh commenting information<00:24:26.480> uh<00:24:26.880> building<00:24:27.760> a 00:24:28.909 --> 00:24:28.919 align:start position:0% information uh building a 00:24:28.919 --> 00:24:33.510 align:start position:0% information uh building a index<00:24:29.919> of<00:24:30.679> uh<00:24:31.679> of<00:24:31.960> swarm<00:24:32.960> well<00:24:33.200> that's<00:24:33.360> a 00:24:33.510 --> 00:24:33.520 align:start position:0% index of uh of swarm well that's a 00:24:33.520 --> 00:24:36.990 align:start position:0% index of uh of swarm well that's a really<00:24:34.080> difficult<00:24:34.399> task<00:24:35.120> and<00:24:35.880> it's<00:24:36.640> you<00:24:36.760> know 00:24:36.990 --> 00:24:37.000 align:start position:0% really difficult task and it's you know 00:24:37.000 --> 00:24:39.630 align:start position:0% really difficult task and it's you know it's<00:24:37.240> a<00:24:38.120> topic<00:24:38.440> for<00:24:38.760> probably<00:24:39.080> a<00:24:39.240> separate 00:24:39.630 --> 00:24:39.640 align:start position:0% it's a topic for probably a separate 00:24:39.640 --> 00:24:42.549 align:start position:0% it's a topic for probably a separate talk<00:24:39.880> or<00:24:40.039> even<00:24:40.240> a<00:24:40.440> SE<00:24:40.799> separate<00:24:41.279> section<00:24:42.279> but 00:24:42.549 --> 00:24:42.559 align:start position:0% talk or even a SE separate section but 00:24:42.559 --> 00:24:47.230 align:start position:0% talk or even a SE separate section but the<00:24:42.760> basic<00:24:43.200> idea<00:24:43.760> here<00:24:44.520> is<00:24:44.919> that<00:24:45.559> you<00:24:45.840> take<00:24:46.679> the 00:24:47.230 --> 00:24:47.240 align:start position:0% the basic idea here is that you take the 00:24:47.240 --> 00:24:50.710 align:start position:0% the basic idea here is that you take the uh<00:24:47.399> map<00:24:47.720> redu<00:24:48.440> Paradigm<00:24:49.440> with<00:24:50.000> untrusted 00:24:50.710 --> 00:24:50.720 align:start position:0% uh map redu Paradigm with untrusted 00:24:50.720 --> 00:24:53.430 align:start position:0% uh map redu Paradigm with untrusted workers<00:24:51.679> and<00:24:51.799> you<00:24:52.000> specify<00:24:52.799> what<00:24:53.000> they<00:24:53.200> can 00:24:53.430 --> 00:24:53.440 align:start position:0% workers and you specify what they can 00:24:53.440 --> 00:24:56.789 align:start position:0% workers and you specify what they can and<00:24:53.720> cannot<00:24:54.159> do<00:24:54.480> in<00:24:54.679> a<00:24:55.000> contract<00:24:55.880> and<00:24:56.159> again<00:24:56.600> in 00:24:56.789 --> 00:24:56.799 align:start position:0% and cannot do in a contract and again in 00:24:56.799 --> 00:24:58.950 align:start position:0% and cannot do in a contract and again in case<00:24:57.039> of<00:24:57.240> a<00:24:57.480> conflict<00:24:57.880> when<00:24:58.039> they<00:24:58.399> violate<00:24:58.799> the 00:24:58.950 --> 00:24:58.960 align:start position:0% case of a conflict when they violate the 00:24:58.960 --> 00:25:01.310 align:start position:0% case of a conflict when they violate the contract<00:24:59.720> then<00:24:59.919> you<00:25:00.080> can<00:25:00.480> punish<00:25:00.880> them<00:25:01.080> and 00:25:01.310 --> 00:25:01.320 align:start position:0% contract then you can punish them and 00:25:01.320 --> 00:25:03.630 align:start position:0% contract then you can punish them and otherwise<00:25:01.720> you<00:25:01.840> can<00:25:02.039> reward<00:25:02.480> them<00:25:03.279> now<00:25:03.480> the 00:25:03.630 --> 00:25:03.640 align:start position:0% otherwise you can reward them now the 00:25:03.640 --> 00:25:05.750 align:start position:0% otherwise you can reward them now the other<00:25:03.960> interesting<00:25:04.600> cases<00:25:05.320> I<00:25:05.440> think 00:25:05.750 --> 00:25:05.760 align:start position:0% other interesting cases I think 00:25:05.760 --> 00:25:08.430 align:start position:0% other interesting cases I think Wikipedia<00:25:06.360> and<00:25:06.559> open<00:25:06.799> street<00:25:07.159> map<00:25:07.520> which<00:25:07.720> are 00:25:08.430 --> 00:25:08.440 align:start position:0% Wikipedia and open street map which are 00:25:08.440 --> 00:25:11.149 align:start position:0% Wikipedia and open street map which are examples<00:25:09.399> where<00:25:09.799> the<00:25:10.000> web<00:25:10.240> 2<00:25:10.480> model<00:25:10.799> doesn't 00:25:11.149 --> 00:25:11.159 align:start position:0% examples where the web 2 model doesn't 00:25:11.159 --> 00:25:13.630 align:start position:0% examples where the web 2 model doesn't really<00:25:11.640> work<00:25:11.960> very<00:25:12.200> well<00:25:12.799> and<00:25:13.000> where<00:25:13.200> we<00:25:13.320> can 00:25:13.630 --> 00:25:13.640 align:start position:0% really work very well and where we can 00:25:13.640 --> 00:25:16.510 align:start position:0% really work very well and where we can actually<00:25:14.039> substantially<00:25:15.120> improve<00:25:16.120> uh<00:25:16.200> on<00:25:16.360> the 00:25:16.510 --> 00:25:16.520 align:start position:0% actually substantially improve uh on the 00:25:16.520 --> 00:25:19.310 align:start position:0% actually substantially improve uh on the state<00:25:16.799> of<00:25:17.039> the<00:25:17.399> of<00:25:17.559> the<00:25:17.720> web<00:25:18.559> because<00:25:18.880> in<00:25:19.120> these 00:25:19.310 --> 00:25:19.320 align:start position:0% state of the of the web because in these 00:25:19.320 --> 00:25:21.590 align:start position:0% state of the of the web because in these two<00:25:19.640> cases<00:25:20.399> there's<00:25:20.679> not<00:25:20.840> a<00:25:21.000> real<00:25:21.240> world 00:25:21.590 --> 00:25:21.600 align:start position:0% two cases there's not a real world 00:25:21.600 --> 00:25:25.350 align:start position:0% two cases there's not a real world consensus<00:25:22.200> about<00:25:22.520> the<00:25:23.120> content<00:25:24.120> uh<00:25:24.559> so<00:25:25.200> in 00:25:25.350 --> 00:25:25.360 align:start position:0% consensus about the content uh so in 00:25:25.360 --> 00:25:28.029 align:start position:0% consensus about the content uh so in Wikipedia<00:25:26.240> you<00:25:26.480> have<00:25:26.880> anything<00:25:27.399> related<00:25:27.840> to 00:25:28.029 --> 00:25:28.039 align:start position:0% Wikipedia you have anything related to 00:25:28.039 --> 00:25:30.669 align:start position:0% Wikipedia you have anything related to re<00:25:28.320> recent<00:25:28.600> history<00:25:28.919> of<00:25:29.360> conflicts<00:25:30.360> where 00:25:30.669 --> 00:25:30.679 align:start position:0% re recent history of conflicts where 00:25:30.679 --> 00:25:32.950 align:start position:0% re recent history of conflicts where there<00:25:30.799> are<00:25:31.039> edit<00:25:31.399> Wars<00:25:31.960> and<00:25:32.200> there<00:25:32.320> are<00:25:32.840> you 00:25:32.950 --> 00:25:32.960 align:start position:0% there are edit Wars and there are you 00:25:32.960 --> 00:25:35.190 align:start position:0% there are edit Wars and there are you know<00:25:33.399> disagreements<00:25:34.200> about<00:25:34.520> what<00:25:34.679> should<00:25:34.919> be 00:25:35.190 --> 00:25:35.200 align:start position:0% know disagreements about what should be 00:25:35.200 --> 00:25:37.389 align:start position:0% know disagreements about what should be there<00:25:35.919> and<00:25:36.080> in<00:25:36.320> open<00:25:36.600> street<00:25:36.960> map<00:25:37.159> you<00:25:37.279> know 00:25:37.389 --> 00:25:37.399 align:start position:0% there and in open street map you know 00:25:37.399 --> 00:25:38.710 align:start position:0% there and in open street map you know it's<00:25:37.520> a<00:25:37.720> current<00:25:38.120> question<00:25:38.480> whether 00:25:38.710 --> 00:25:38.720 align:start position:0% it's a current question whether 00:25:38.720 --> 00:25:43.190 align:start position:0% it's a current question whether liberland<00:25:39.279> is<00:25:39.360> a<00:25:39.520> country<00:25:39.799> or<00:25:40.240> not<00:25:41.240> and<00:25:41.799> uh 00:25:43.190 --> 00:25:43.200 align:start position:0% liberland is a country or not and uh 00:25:43.200 --> 00:25:46.149 align:start position:0% liberland is a country or not and uh therefore<00:25:44.200> uh<00:25:44.559> like<00:25:44.679> forking<00:25:45.279> these<00:25:45.600> projects 00:25:46.149 --> 00:25:46.159 align:start position:0% therefore uh like forking these projects 00:25:46.159 --> 00:25:48.830 align:start position:0% therefore uh like forking these projects is<00:25:46.360> not<00:25:46.640> really<00:25:47.120> feasible<00:25:47.760> so<00:25:48.080> people<00:25:48.399> try<00:25:48.720> to 00:25:48.830 --> 00:25:48.840 align:start position:0% is not really feasible so people try to 00:25:48.840 --> 00:25:50.950 align:start position:0% is not really feasible so people try to do<00:25:49.120> something<00:25:49.600> like<00:25:49.840> conservapedia<00:25:50.799> where 00:25:50.950 --> 00:25:50.960 align:start position:0% do something like conservapedia where 00:25:50.960 --> 00:25:53.190 align:start position:0% do something like conservapedia where they<00:25:51.120> try<00:25:51.360> to<00:25:51.520> eliminate<00:25:52.080> the<00:25:52.760> supposed 00:25:53.190 --> 00:25:53.200 align:start position:0% they try to eliminate the supposed 00:25:53.200 --> 00:25:55.389 align:start position:0% they try to eliminate the supposed liberal<00:25:53.559> bias<00:25:53.919> from<00:25:54.120> Wikipedia<00:25:55.039> but<00:25:55.240> the 00:25:55.389 --> 00:25:55.399 align:start position:0% liberal bias from Wikipedia but the 00:25:55.399 --> 00:25:56.990 align:start position:0% liberal bias from Wikipedia but the problem<00:25:55.760> is<00:25:55.960> that<00:25:56.120> they<00:25:56.240> have<00:25:56.440> so<00:25:56.640> little 00:25:56.990 --> 00:25:57.000 align:start position:0% problem is that they have so little 00:25:57.000 --> 00:25:59.190 align:start position:0% problem is that they have so little content<00:25:57.480> and<00:25:57.640> it's<00:25:57.799> so<00:25:58.320> expensive<00:25:58.720> to<00:25:58.840> Fork 00:25:59.190 --> 00:25:59.200 align:start position:0% content and it's so expensive to Fork 00:25:59.200 --> 00:26:01.149 align:start position:0% content and it's so expensive to Fork over<00:25:59.559> content<00:26:00.000> from<00:26:00.200> the<00:26:00.399> mainstream 00:26:01.149 --> 00:26:01.159 align:start position:0% over content from the mainstream 00:26:01.159 --> 00:26:04.070 align:start position:0% over content from the mainstream Wikipedia<00:26:02.159> that<00:26:02.600> that<00:26:02.880> project<00:26:03.279> is<00:26:03.520> simply 00:26:04.070 --> 00:26:04.080 align:start position:0% Wikipedia that that project is simply 00:26:04.080 --> 00:26:07.070 align:start position:0% Wikipedia that that project is simply unlivable<00:26:05.080> but<00:26:05.360> with<00:26:05.720> with<00:26:05.919> with<00:26:06.279> swarm<00:26:06.960> what 00:26:07.070 --> 00:26:07.080 align:start position:0% unlivable but with with with swarm what 00:26:07.080 --> 00:26:11.110 align:start position:0% unlivable but with with with swarm what you<00:26:07.240> can<00:26:07.480> do<00:26:08.240> is<00:26:08.480> you<00:26:08.679> can<00:26:09.600> present<00:26:10.600> different 00:26:11.110 --> 00:26:11.120 align:start position:0% you can do is you can present different 00:26:11.120 --> 00:26:14.470 align:start position:0% you can do is you can present different views<00:26:12.000> to<00:26:12.240> the<00:26:12.440> same<00:26:12.760> large<00:26:13.080> body<00:26:13.440> of<00:26:13.640> content 00:26:14.470 --> 00:26:14.480 align:start position:0% views to the same large body of content 00:26:14.480 --> 00:26:17.389 align:start position:0% views to the same large body of content and<00:26:14.679> simply<00:26:15.080> mark<00:26:15.520> up<00:26:16.520> uh<00:26:16.679> like<00:26:16.919> which<00:26:17.159> point 00:26:17.389 --> 00:26:17.399 align:start position:0% and simply mark up uh like which point 00:26:17.399 --> 00:26:19.590 align:start position:0% and simply mark up uh like which point of<00:26:17.600> view<00:26:18.000> would<00:26:18.159> you<00:26:18.279> would<00:26:18.480> like<00:26:18.679> to<00:26:18.919> take<00:26:19.440> and 00:26:19.590 --> 00:26:19.600 align:start position:0% of view would you would like to take and 00:26:19.600 --> 00:26:21.630 align:start position:0% of view would you would like to take and it's<00:26:19.840> really<00:26:20.120> really<00:26:20.399> cheap<00:26:21.080> to<00:26:21.279> make 00:26:21.630 --> 00:26:21.640 align:start position:0% it's really really cheap to make 00:26:21.640 --> 00:26:24.230 align:start position:0% it's really really cheap to make slightly<00:26:22.120> different<00:26:22.640> versions<00:26:23.480> of<00:26:23.679> the<00:26:23.880> same 00:26:24.230 --> 00:26:24.240 align:start position:0% slightly different versions of the same 00:26:24.240 --> 00:26:26.830 align:start position:0% slightly different versions of the same huge<00:26:24.600> data<00:26:24.960> set<00:26:25.440> so<00:26:25.640> I<00:26:25.760> think<00:26:26.000> that<00:26:26.159> in<00:26:26.360> case<00:26:26.559> of 00:26:26.830 --> 00:26:26.840 align:start position:0% huge data set so I think that in case of 00:26:26.840 --> 00:26:28.789 align:start position:0% huge data set so I think that in case of maps<00:26:27.240> and<00:26:27.480> encyclopedia 00:26:28.789 --> 00:26:28.799 align:start position:0% maps and encyclopedia 00:26:28.799 --> 00:26:30.470 align:start position:0% maps and encyclopedia we're<00:26:29.080> actually<00:26:29.440> looking<00:26:29.760> forward<00:26:30.240> to 00:26:30.470 --> 00:26:30.480 align:start position:0% we're actually looking forward to 00:26:30.480 --> 00:26:33.430 align:start position:0% we're actually looking forward to something<00:26:31.000> that<00:26:31.200> is<00:26:31.919> qualitatively<00:26:32.799> superior 00:26:33.430 --> 00:26:33.440 align:start position:0% something that is qualitatively superior 00:26:33.440 --> 00:26:36.070 align:start position:0% something that is qualitatively superior to<00:26:34.000> what<00:26:34.240> currently<00:26:34.720> exists<00:26:35.039> in<00:26:35.200> web 00:26:36.070 --> 00:26:36.080 align:start position:0% to what currently exists in web 00:26:36.080 --> 00:26:40.310 align:start position:0% to what currently exists in web 2<00:26:37.080> uh<00:26:37.640> so<00:26:37.960> finally<00:26:38.399> I<00:26:38.520> would<00:26:38.720> like<00:26:39.000> to<00:26:39.480> tell<00:26:39.880> you 00:26:40.310 --> 00:26:40.320 align:start position:0% 2 uh so finally I would like to tell you 00:26:40.320 --> 00:26:42.350 align:start position:0% 2 uh so finally I would like to tell you what<00:26:40.559> of<00:26:40.880> this<00:26:41.399> exists<00:26:41.840> and<00:26:42.039> what's<00:26:42.200> the 00:26:42.350 --> 00:26:42.360 align:start position:0% what of this exists and what's the 00:26:42.360 --> 00:26:44.590 align:start position:0% what of this exists and what's the status<00:26:42.720> of<00:26:42.919> this<00:26:43.159> project<00:26:43.880> so<00:26:44.080> we<00:26:44.279> have<00:26:44.440> a 00:26:44.590 --> 00:26:44.600 align:start position:0% status of this project so we have a 00:26:44.600 --> 00:26:47.630 align:start position:0% status of this project so we have a reference<00:26:45.520> implementation<00:26:46.520> of<00:26:47.000> uh<00:26:47.320> so<00:26:47.520> this 00:26:47.630 --> 00:26:47.640 align:start position:0% reference implementation of uh so this 00:26:47.640 --> 00:26:50.909 align:start position:0% reference implementation of uh so this is<00:26:47.760> an<00:26:48.000> extension<00:26:48.480> of<00:26:48.600> the<00:26:48.799> go<00:26:49.080> client<00:26:49.720> gu<00:26:50.720> uh 00:26:50.909 --> 00:26:50.919 align:start position:0% is an extension of the go client gu uh 00:26:50.919 --> 00:26:53.110 align:start position:0% is an extension of the go client gu uh which<00:26:51.320> has<00:26:51.919> a 00:26:53.110 --> 00:26:53.120 align:start position:0% which has a 00:26:53.120 --> 00:26:58.029 align:start position:0% which has a uh<00:26:54.120> uh<00:26:54.399> HTTP<00:26:55.320> which<00:26:55.520> has<00:26:55.679> the<00:26:55.880> HTTP<00:26:56.600> API<00:26:57.360> it<00:26:57.640> has 00:26:58.029 --> 00:26:58.039 align:start position:0% uh uh HTTP which has the HTTP API it has 00:26:58.039 --> 00:27:01.310 align:start position:0% uh uh HTTP which has the HTTP API it has a<00:26:58.399> uh<00:26:58.799> the<00:26:59.799> uh<00:27:00.080> pairwise 00:27:01.310 --> 00:27:01.320 align:start position:0% a uh the uh pairwise 00:27:01.320 --> 00:27:04.870 align:start position:0% a uh the uh pairwise accounting<00:27:02.320> uh<00:27:02.480> all<00:27:02.640> of<00:27:02.840> it<00:27:03.120> works<00:27:03.880> on<00:27:04.240> small 00:27:04.870 --> 00:27:04.880 align:start position:0% accounting uh all of it works on small 00:27:04.880 --> 00:27:07.310 align:start position:0% accounting uh all of it works on small scale<00:27:05.600> uh<00:27:05.720> we<00:27:05.919> simply<00:27:06.320> haven't<00:27:06.600> been<00:27:06.799> able<00:27:07.080> to 00:27:07.310 --> 00:27:07.320 align:start position:0% scale uh we simply haven't been able to 00:27:07.320 --> 00:27:10.310 align:start position:0% scale uh we simply haven't been able to test<00:27:07.640> it<00:27:08.159> on<00:27:08.360> on<00:27:08.480> a<00:27:08.600> larger<00:27:09.039> scale<00:27:09.520> but<00:27:09.919> uh<00:27:10.120> and 00:27:10.310 --> 00:27:10.320 align:start position:0% test it on on a larger scale but uh and 00:27:10.320 --> 00:27:12.990 align:start position:0% test it on on a larger scale but uh and I'm<00:27:10.440> sure<00:27:10.840> that<00:27:11.240> it<00:27:11.399> would<00:27:11.880> have<00:27:12.200> some 00:27:12.990 --> 00:27:13.000 align:start position:0% I'm sure that it would have some 00:27:13.000 --> 00:27:16.750 align:start position:0% I'm sure that it would have some problems<00:27:13.480> that<00:27:13.640> need<00:27:13.880> to<00:27:14.039> be<00:27:14.559> uh<00:27:15.520> ironed 00:27:16.750 --> 00:27:16.760 align:start position:0% problems that need to be uh ironed 00:27:16.760 --> 00:27:21.870 align:start position:0% problems that need to be uh ironed out<00:27:18.000> uh<00:27:19.000> so<00:27:19.279> far<00:27:19.679> it<00:27:19.880> has<00:27:20.080> been<00:27:20.320> funded<00:27:21.120> uh<00:27:21.320> by 00:27:21.870 --> 00:27:21.880 align:start position:0% out uh so far it has been funded uh by 00:27:21.880 --> 00:27:24.830 align:start position:0% out uh so far it has been funded uh by uh<00:27:22.200> ethereum<00:27:22.679> foundation<00:27:23.440> so<00:27:23.720> this<00:27:23.960> has<00:27:24.200> been 00:27:24.830 --> 00:27:24.840 align:start position:0% uh ethereum foundation so this has been 00:27:24.840 --> 00:27:26.909 align:start position:0% uh ethereum foundation so this has been uh<00:27:25.039> and<00:27:25.240> we<00:27:25.399> have<00:27:25.760> had<00:27:25.960> a<00:27:26.080> lot<00:27:26.240> of<00:27:26.399> Community 00:27:26.909 --> 00:27:26.919 align:start position:0% uh and we have had a lot of Community 00:27:26.919 --> 00:27:29.549 align:start position:0% uh and we have had a lot of Community Support<00:27:27.399> as<00:27:27.559> well 00:27:29.549 --> 00:27:29.559 align:start position:0% Support as well 00:27:29.559 --> 00:27:33.190 align:start position:0% Support as well uh<00:27:30.559> and<00:27:31.000> here<00:27:31.120> are<00:27:31.399> the<00:27:31.600> things<00:27:32.000> that<00:27:32.200> we<00:27:32.360> are 00:27:33.190 --> 00:27:33.200 align:start position:0% uh and here are the things that we are 00:27:33.200 --> 00:27:35.190 align:start position:0% uh and here are the things that we are ready<00:27:33.559> to<00:27:33.799> demo<00:27:34.200> well<00:27:34.360> not<00:27:34.640> right<00:27:34.799> now<00:27:35.039> of 00:27:35.190 --> 00:27:35.200 align:start position:0% ready to demo well not right now of 00:27:35.200 --> 00:27:38.269 align:start position:0% ready to demo well not right now of course<00:27:35.679> but<00:27:36.039> uh<00:27:36.600> hopefully<00:27:37.039> during<00:27:37.399> this 00:27:38.269 --> 00:27:38.279 align:start position:0% course but uh hopefully during this 00:27:38.279 --> 00:27:41.389 align:start position:0% course but uh hopefully during this conference<00:27:39.279> and<00:27:39.760> in<00:27:40.000> GitHub<00:27:40.519> you<00:27:40.679> can<00:27:40.880> see<00:27:41.240> the 00:27:41.389 --> 00:27:41.399 align:start position:0% conference and in GitHub you can see the 00:27:41.399 --> 00:27:43.830 align:start position:0% conference and in GitHub you can see the source<00:27:41.880> repository<00:27:42.760> which<00:27:42.919> is<00:27:43.200> basically<00:27:43.679> a 00:27:43.830 --> 00:27:43.840 align:start position:0% source repository which is basically a 00:27:43.840 --> 00:27:48.230 align:start position:0% source repository which is basically a fork<00:27:44.480> of<00:27:44.799> the<00:27:45.480> uh<00:27:45.840> go<00:27:46.600> uh<00:27:46.760> ethereum<00:27:47.360> client 00:27:48.230 --> 00:27:48.240 align:start position:0% fork of the uh go uh ethereum client 00:27:48.240 --> 00:27:50.710 align:start position:0% fork of the uh go uh ethereum client with<00:27:48.399> a<00:27:48.640> separate<00:27:49.080> Branch<00:27:49.480> Bzz<00:27:50.200> where<00:27:50.360> you<00:27:50.480> can 00:27:50.710 --> 00:27:50.720 align:start position:0% with a separate Branch Bzz where you can 00:27:50.720 --> 00:27:54.870 align:start position:0% with a separate Branch Bzz where you can always<00:27:51.120> find<00:27:51.679> the<00:27:52.279> current<00:27:52.840> state<00:27:53.840> uh<00:27:54.080> of<00:27:54.440> the 00:27:54.870 --> 00:27:54.880 align:start position:0% always find the current state uh of the 00:27:54.880 --> 00:27:58.470 align:start position:0% always find the current state uh of the bz<00:27:55.519> capable<00:27:56.200> uh<00:27:56.360> G<00:27:56.640> client<00:27:57.440> and<00:27:57.640> we<00:27:57.760> are 00:27:58.470 --> 00:27:58.480 align:start position:0% bz capable uh G client and we are 00:27:58.480 --> 00:28:01.590 align:start position:0% bz capable uh G client and we are keeping<00:27:58.880> it<00:27:59.159> up<00:27:59.360> to<00:27:59.559> date<00:27:59.880> with<00:28:00.159> the<00:28:00.720> uh 00:28:01.590 --> 00:28:01.600 align:start position:0% keeping it up to date with the uh 00:28:01.600 --> 00:28:05.029 align:start position:0% keeping it up to date with the uh Upstream<00:28:02.159> version<00:28:02.559> of<00:28:02.880> go<00:28:03.120> ethereum<00:28:03.720> so<00:28:04.440> uh 00:28:05.029 --> 00:28:05.039 align:start position:0% Upstream version of go ethereum so uh 00:28:05.039 --> 00:28:08.070 align:start position:0% Upstream version of go ethereum so uh that's<00:28:05.279> where<00:28:05.440> you<00:28:05.799> find<00:28:06.799> uh<00:28:06.919> our<00:28:07.159> source<00:28:07.559> code 00:28:08.070 --> 00:28:08.080 align:start position:0% that's where you find uh our source code 00:28:08.080 --> 00:28:11.669 align:start position:0% that's where you find uh our source code and<00:28:08.559> uh<00:28:09.039> our<00:28:09.320> documentation<00:28:10.080> as<00:28:10.399> well<00:28:11.399> uh 00:28:11.669 --> 00:28:11.679 align:start position:0% and uh our documentation as well uh 00:28:11.679 --> 00:28:13.630 align:start position:0% and uh our documentation as well uh maybe<00:28:12.159> Victor<00:28:12.480> do<00:28:12.600> you<00:28:12.679> want<00:28:12.799> to<00:28:12.960> say<00:28:13.159> anything 00:28:13.630 --> 00:28:13.640 align:start position:0% maybe Victor do you want to say anything 00:28:13.640 --> 00:28:17.070 align:start position:0% maybe Victor do you want to say anything about<00:28:13.880> the<00:28:14.279> status<00:28:15.279> okay 00:28:17.070 --> 00:28:17.080 align:start position:0% about the status okay 00:28:17.080 --> 00:28:25.040 align:start position:0% about the status okay than<00:28:18.080> thank<00:28:18.279> you 00:28:25.040 --> 00:28:25.050 align:start position:0% 00:28:25.050 --> 00:28:29.380 align:start position:0% [Music]