WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:11.230 align:start position:0% [Music] 00:00:11.230 --> 00:00:11.240 align:start position:0% 00:00:11.240 --> 00:00:15.310 align:start position:0% hello<00:00:12.080> oh<00:00:12.400> it<00:00:12.679> works<00:00:13.679> um<00:00:14.440> nice<00:00:14.639> to<00:00:14.759> meet<00:00:15.000> you<00:00:15.200> my 00:00:15.310 --> 00:00:15.320 align:start position:0% hello oh it works um nice to meet you my 00:00:15.320 --> 00:00:16.310 align:start position:0% hello oh it works um nice to meet you my name<00:00:15.480> is 00:00:16.310 --> 00:00:16.320 align:start position:0% name is 00:00:16.320 --> 00:00:19.830 align:start position:0% name is Sasha<00:00:17.320> today<00:00:18.039> um<00:00:18.600> we<00:00:18.720> will<00:00:19.039> have<00:00:19.400> a<00:00:19.560> little 00:00:19.830 --> 00:00:19.840 align:start position:0% Sasha today um we will have a little 00:00:19.840 --> 00:00:22.349 align:start position:0% Sasha today um we will have a little presentation<00:00:20.400> about<00:00:20.840> waku<00:00:21.840> uh<00:00:22.000> it<00:00:22.080> will<00:00:22.240> be 00:00:22.349 --> 00:00:22.359 align:start position:0% presentation about waku uh it will be 00:00:22.359 --> 00:00:25.870 align:start position:0% presentation about waku uh it will be two<00:00:22.519> presenters<00:00:23.039> me<00:00:23.720> and<00:00:24.080> Ian<00:00:25.080> uh<00:00:25.240> we<00:00:25.359> will 00:00:25.870 --> 00:00:25.880 align:start position:0% two presenters me and Ian uh we will 00:00:25.880 --> 00:00:27.830 align:start position:0% two presenters me and Ian uh we will explain<00:00:26.279> you 00:00:27.830 --> 00:00:27.840 align:start position:0% explain you 00:00:27.840 --> 00:00:30.710 align:start position:0% explain you um<00:00:28.840> overall<00:00:29.320> problematics<00:00:29.759> of<00:00:29.960> peer-to-peer 00:00:30.710 --> 00:00:30.720 align:start position:0% um overall problematics of peer-to-peer 00:00:30.720 --> 00:00:33.510 align:start position:0% um overall problematics of peer-to-peer networks<00:00:31.720> um<00:00:32.360> we<00:00:32.480> will<00:00:32.719> go 00:00:33.510 --> 00:00:33.520 align:start position:0% networks um we will go 00:00:33.520 --> 00:00:35.110 align:start position:0% networks um we will go through 00:00:35.110 --> 00:00:35.120 align:start position:0% through 00:00:35.120 --> 00:00:37.350 align:start position:0% through um<00:00:36.120> uh<00:00:36.320> common<00:00:36.640> parts<00:00:36.840> of<00:00:37.000> peer-to-peer 00:00:37.350 --> 00:00:37.360 align:start position:0% um uh common parts of peer-to-peer 00:00:37.360 --> 00:00:39.590 align:start position:0% um uh common parts of peer-to-peer networks<00:00:38.040> challenges<00:00:38.600> that<00:00:38.760> are<00:00:38.960> faced 00:00:39.590 --> 00:00:39.600 align:start position:0% networks challenges that are faced 00:00:39.600 --> 00:00:42.750 align:start position:0% networks challenges that are faced usually<00:00:40.280> and<00:00:40.800> uh<00:00:41.520> uh<00:00:41.640> how<00:00:41.840> they<00:00:42.000> usually<00:00:42.360> are 00:00:42.750 --> 00:00:42.760 align:start position:0% usually and uh uh how they usually are 00:00:42.760 --> 00:00:45.630 align:start position:0% usually and uh uh how they usually are dealt<00:00:43.239> with<00:00:43.680> and<00:00:44.120> the<00:00:44.239> common<00:00:44.480> tradeoffs<00:00:45.480> uh 00:00:45.630 --> 00:00:45.640 align:start position:0% dealt with and the common tradeoffs uh 00:00:45.640 --> 00:00:47.510 align:start position:0% dealt with and the common tradeoffs uh then<00:00:45.800> we<00:00:45.960> will<00:00:46.160> explain<00:00:46.480> a<00:00:46.600> bit<00:00:46.800> about<00:00:47.079> waku 00:00:47.510 --> 00:00:47.520 align:start position:0% then we will explain a bit about waku 00:00:47.520 --> 00:00:49.430 align:start position:0% then we will explain a bit about waku which<00:00:47.680> is<00:00:47.920> a<00:00:48.239> functionable<00:00:48.920> peer-to-peer 00:00:49.430 --> 00:00:49.440 align:start position:0% which is a functionable peer-to-peer 00:00:49.440 --> 00:00:52.349 align:start position:0% which is a functionable peer-to-peer network<00:00:50.440> uh<00:00:50.600> that<00:00:50.879> has<00:00:51.320> uh<00:00:51.440> some<00:00:51.719> answers<00:00:52.079> to 00:00:52.349 --> 00:00:52.359 align:start position:0% network uh that has uh some answers to 00:00:52.359 --> 00:00:54.549 align:start position:0% network uh that has uh some answers to some<00:00:52.520> of<00:00:52.640> the<00:00:52.840> problems<00:00:53.640> that<00:00:53.760> will<00:00:53.960> be 00:00:54.549 --> 00:00:54.559 align:start position:0% some of the problems that will be 00:00:54.559 --> 00:00:56.470 align:start position:0% some of the problems that will be mentioned<00:00:55.559> and<00:00:55.680> we<00:00:55.800> will<00:00:55.960> show<00:00:56.120> you<00:00:56.280> some 00:00:56.470 --> 00:00:56.480 align:start position:0% mentioned and we will show you some 00:00:56.480 --> 00:00:58.990 align:start position:0% mentioned and we will show you some examples<00:00:57.239> and<00:00:57.640> uh<00:00:57.800> we'll<00:00:58.039> try<00:00:58.199> to<00:00:58.399> do<00:00:58.600> a<00:00:58.719> bit<00:00:58.840> of 00:00:58.990 --> 00:00:59.000 align:start position:0% examples and uh we'll try to do a bit of 00:00:59.000 --> 00:01:02.549 align:start position:0% examples and uh we'll try to do a bit of programming<00:00:59.480> so<00:01:00.199> uh<00:01:00.840> yeah<00:01:01.239> uh<00:01:01.519> how<00:01:02.120> are<00:01:02.320> you 00:01:02.549 --> 00:01:02.559 align:start position:0% programming so uh yeah uh how are you 00:01:02.559 --> 00:01:05.189 align:start position:0% programming so uh yeah uh how are you guys<00:01:02.760> familiar<00:01:03.760> raise<00:01:04.000> your<00:01:04.199> hand<00:01:04.479> if<00:01:04.600> you<00:01:04.720> are 00:01:05.189 --> 00:01:05.199 align:start position:0% guys familiar raise your hand if you are 00:01:05.199 --> 00:01:06.630 align:start position:0% guys familiar raise your hand if you are really<00:01:05.519> familiar<00:01:06.000> with<00:01:06.320> peer-to-peer 00:01:06.630 --> 00:01:06.640 align:start position:0% really familiar with peer-to-peer 00:01:06.640 --> 00:01:09.149 align:start position:0% really familiar with peer-to-peer networks<00:01:07.280> you<00:01:07.439> build<00:01:07.680> one<00:01:07.840> way<00:01:08.040> yourself<00:01:08.960> uh 00:01:09.149 --> 00:01:09.159 align:start position:0% networks you build one way yourself uh 00:01:09.159 --> 00:01:11.230 align:start position:0% networks you build one way yourself uh you<00:01:09.320> know<00:01:09.600> ins<00:01:09.840> and<00:01:10.000> outs<00:01:10.200> of<00:01:10.320> Le<00:01:10.560> P2P<00:01:10.920> or<00:01:11.040> Dev 00:01:11.230 --> 00:01:11.240 align:start position:0% you know ins and outs of Le P2P or Dev 00:01:11.240 --> 00:01:14.270 align:start position:0% you know ins and outs of Le P2P or Dev P2P<00:01:11.640> or<00:01:11.799> you<00:01:11.880> build<00:01:12.159> your<00:01:12.320> stack<00:01:13.200> so<00:01:13.880> maybe<00:01:14.159> you 00:01:14.270 --> 00:01:14.280 align:start position:0% P2P or you build your stack so maybe you 00:01:14.280 --> 00:01:18.190 align:start position:0% P2P or you build your stack so maybe you can<00:01:14.960> uh<00:01:15.640> uh<00:01:15.799> enjoy<00:01:16.240> this<00:01:16.400> talk<00:01:16.799> I<00:01:16.920> hope<00:01:17.400> as<00:01:17.560> well 00:01:18.190 --> 00:01:18.200 align:start position:0% can uh uh enjoy this talk I hope as well 00:01:18.200 --> 00:01:20.030 align:start position:0% can uh uh enjoy this talk I hope as well but<00:01:18.600> uh<00:01:18.960> otherwise<00:01:19.360> it's<00:01:19.479> more<00:01:19.640> of<00:01:19.759> an 00:01:20.030 --> 00:01:20.040 align:start position:0% but uh otherwise it's more of an 00:01:20.040 --> 00:01:23.630 align:start position:0% but uh otherwise it's more of an intermediate<00:01:20.680> level<00:01:21.000> so<00:01:21.640> um<00:01:22.640> yeah<00:01:23.280> uh<00:01:23.479> let's 00:01:23.630 --> 00:01:23.640 align:start position:0% intermediate level so um yeah uh let's 00:01:23.640 --> 00:01:27.190 align:start position:0% intermediate level so um yeah uh let's start<00:01:23.960> so<00:01:24.920> uh<00:01:25.240> why<00:01:25.720> do<00:01:25.920> we<00:01:26.119> even<00:01:26.360> care<00:01:26.600> about<00:01:27.040> uh 00:01:27.190 --> 00:01:27.200 align:start position:0% start so uh why do we even care about uh 00:01:27.200 --> 00:01:28.109 align:start position:0% start so uh why do we even care about uh peer-to-peer 00:01:28.109 --> 00:01:28.119 align:start position:0% peer-to-peer 00:01:28.119 --> 00:01:31.950 align:start position:0% peer-to-peer networks<00:01:29.119> so<00:01:29.360> first<00:01:29.520> of<00:01:29.640> all<00:01:30.400> is<00:01:30.880> um<00:01:31.200> that<00:01:31.759> due 00:01:31.950 --> 00:01:31.960 align:start position:0% networks so first of all is um that due 00:01:31.960 --> 00:01:34.710 align:start position:0% networks so first of all is um that due to<00:01:32.439> architectural<00:01:33.439> uh<00:01:33.600> decision<00:01:34.200> of<00:01:34.399> going 00:01:34.710 --> 00:01:34.720 align:start position:0% to architectural uh decision of going 00:01:34.720 --> 00:01:38.830 align:start position:0% to architectural uh decision of going with<00:01:35.000> peerto<00:01:35.399> peer<00:01:36.320> uh<00:01:36.520> we<00:01:36.880> guarantee<00:01:37.360> some<00:01:38.240> uh 00:01:38.830 --> 00:01:38.840 align:start position:0% with peerto peer uh we guarantee some uh 00:01:38.840 --> 00:01:40.710 align:start position:0% with peerto peer uh we guarantee some uh potential<00:01:39.399> decentralization<00:01:40.399> and 00:01:40.710 --> 00:01:40.720 align:start position:0% potential decentralization and 00:01:40.720 --> 00:01:43.350 align:start position:0% potential decentralization and sensorship<00:01:41.479> resistance<00:01:42.479> that<00:01:42.680> comes<00:01:42.960> out<00:01:43.159> of 00:01:43.350 --> 00:01:43.360 align:start position:0% sensorship resistance that comes out of 00:01:43.360 --> 00:01:46.069 align:start position:0% sensorship resistance that comes out of it<00:01:43.799> and<00:01:44.200> uh<00:01:44.439> why<00:01:44.560> do<00:01:44.719> we<00:01:45.040> even<00:01:45.280> want<00:01:45.520> it<00:01:45.680> is<00:01:45.880> that 00:01:46.069 --> 00:01:46.079 align:start position:0% it and uh why do we even want it is that 00:01:46.079 --> 00:01:48.670 align:start position:0% it and uh why do we even want it is that because<00:01:46.280> we<00:01:46.399> are<00:01:46.479> in<00:01:46.640> crypto<00:01:47.000> space<00:01:47.600> right<00:01:48.600> I 00:01:48.670 --> 00:01:48.680 align:start position:0% because we are in crypto space right I 00:01:48.680 --> 00:01:50.950 align:start position:0% because we are in crypto space right I think<00:01:49.000> this<00:01:49.159> is<00:01:49.680> like<00:01:49.880> something<00:01:50.240> that<00:01:50.799> does 00:01:50.950 --> 00:01:50.960 align:start position:0% think this is like something that does 00:01:50.960 --> 00:01:54.370 align:start position:0% think this is like something that does not<00:01:51.479> need<00:01:51.920> a<00:01:52.040> lot<00:01:52.200> of<00:01:52.320> answers<00:01:53.079> but<00:01:53.280> then 00:01:54.370 --> 00:01:54.380 align:start position:0% not need a lot of answers but then 00:01:54.380 --> 00:01:55.630 align:start position:0% not need a lot of answers but then [Music] 00:01:55.630 --> 00:01:55.640 align:start position:0% [Music] 00:01:55.640 --> 00:02:00.950 align:start position:0% [Music] um<00:01:56.640> usually<00:01:57.200> this<00:01:57.680> uh<00:01:58.240> solution<00:01:58.680> is<00:01:58.880> made<00:01:59.719> uh 00:02:00.950 --> 00:02:00.960 align:start position:0% um usually this uh solution is made uh 00:02:00.960 --> 00:02:03.109 align:start position:0% um usually this uh solution is made uh to<00:02:01.399> introduce<00:02:01.880> some<00:02:02.119> set<00:02:02.360> some<00:02:02.560> degree<00:02:02.880> of 00:02:03.109 --> 00:02:03.119 align:start position:0% to introduce some set some degree of 00:02:03.119 --> 00:02:05.870 align:start position:0% to introduce some set some degree of privacy<00:02:04.000> and<00:02:04.240> that<00:02:04.439> data<00:02:04.719> ownership<00:02:05.360> it's<00:02:05.680> to 00:02:05.870 --> 00:02:05.880 align:start position:0% privacy and that data ownership it's to 00:02:05.880 --> 00:02:08.309 align:start position:0% privacy and that data ownership it's to provide<00:02:06.280> this<00:02:06.479> service<00:02:06.840> to<00:02:07.000> the<00:02:07.159> users<00:02:07.960> of<00:02:08.080> our 00:02:08.309 --> 00:02:08.319 align:start position:0% provide this service to the users of our 00:02:08.319 --> 00:02:10.589 align:start position:0% provide this service to the users of our applications<00:02:09.039> networks 00:02:10.589 --> 00:02:10.599 align:start position:0% applications networks 00:02:10.599 --> 00:02:13.110 align:start position:0% applications networks whatever<00:02:11.599> uh<00:02:11.959> other<00:02:12.319> properties<00:02:12.760> that 00:02:13.110 --> 00:02:13.120 align:start position:0% whatever uh other properties that 00:02:13.120 --> 00:02:14.750 align:start position:0% whatever uh other properties that peer-to-peer<00:02:13.440> networks<00:02:13.959> guarantee<00:02:14.400> that 00:02:14.750 --> 00:02:14.760 align:start position:0% peer-to-peer networks guarantee that 00:02:14.760 --> 00:02:17.309 align:start position:0% peer-to-peer networks guarantee that usually<00:02:15.160> they<00:02:15.239> are<00:02:15.360> full<00:02:15.640> tolerant<00:02:16.280> or<00:02:17.000> uh 00:02:17.309 --> 00:02:17.319 align:start position:0% usually they are full tolerant or uh 00:02:17.319 --> 00:02:20.150 align:start position:0% usually they are full tolerant or uh resilient<00:02:18.319> and<00:02:18.720> this<00:02:18.879> comes<00:02:19.120> out<00:02:19.319> of<00:02:19.519> the<00:02:19.760> fact 00:02:20.150 --> 00:02:20.160 align:start position:0% resilient and this comes out of the fact 00:02:20.160 --> 00:02:22.430 align:start position:0% resilient and this comes out of the fact that<00:02:20.599> uh<00:02:20.800> we<00:02:20.920> don't<00:02:21.239> have<00:02:21.640> single<00:02:22.080> point 00:02:22.430 --> 00:02:22.440 align:start position:0% that uh we don't have single point 00:02:22.440 --> 00:02:26.390 align:start position:0% that uh we don't have single point usually<00:02:22.920> there<00:02:23.640> and<00:02:24.160> uh<00:02:24.480> we<00:02:25.160> um<00:02:26.040> uh<00:02:26.160> can 00:02:26.390 --> 00:02:26.400 align:start position:0% usually there and uh we um uh can 00:02:26.400 --> 00:02:29.550 align:start position:0% usually there and uh we um uh can survive<00:02:27.080> as<00:02:27.200> a<00:02:27.440> as<00:02:27.519> a<00:02:27.840> as<00:02:27.920> a<00:02:28.280> set<00:02:28.480> of<00:02:28.640> nodes<00:02:29.280> if 00:02:29.550 --> 00:02:29.560 align:start position:0% survive as a as a as a set of nodes if 00:02:29.560 --> 00:02:33.350 align:start position:0% survive as a as a as a set of nodes if one<00:02:30.040> two<00:02:30.319> or<00:02:30.599> even<00:02:31.480> half<00:02:31.720> of<00:02:31.959> the<00:02:32.080> nodes<00:02:32.480> are 00:02:33.350 --> 00:02:33.360 align:start position:0% one two or even half of the nodes are 00:02:33.360 --> 00:02:36.550 align:start position:0% one two or even half of the nodes are offline<00:02:34.360> or<00:02:34.640> down<00:02:35.480> uh<00:02:35.640> and<00:02:35.879> then<00:02:36.400> uh 00:02:36.550 --> 00:02:36.560 align:start position:0% offline or down uh and then uh 00:02:36.560 --> 00:02:39.430 align:start position:0% offline or down uh and then uh potentially<00:02:37.120> we<00:02:37.280> can<00:02:37.519> get<00:02:37.720> some<00:02:38.599> scalability 00:02:39.430 --> 00:02:39.440 align:start position:0% potentially we can get some scalability 00:02:39.440 --> 00:02:41.630 align:start position:0% potentially we can get some scalability out<00:02:39.599> of<00:02:39.760> this<00:02:40.120> decision<00:02:41.120> uh<00:02:41.319> this<00:02:41.440> is 00:02:41.630 --> 00:02:41.640 align:start position:0% out of this decision uh this is 00:02:41.640 --> 00:02:44.229 align:start position:0% out of this decision uh this is questionable<00:02:42.440> actually<00:02:43.440> because<00:02:43.720> p-to-p 00:02:44.229 --> 00:02:44.239 align:start position:0% questionable actually because p-to-p 00:02:44.239 --> 00:02:47.190 align:start position:0% questionable actually because p-to-p networks<00:02:44.599> are<00:02:44.720> known<00:02:44.959> to<00:02:45.080> be<00:02:45.760> uh<00:02:46.400> difficult<00:02:46.800> to 00:02:47.190 --> 00:02:47.200 align:start position:0% networks are known to be uh difficult to 00:02:47.200 --> 00:02:51.710 align:start position:0% networks are known to be uh difficult to make<00:02:47.680> right<00:02:48.680> uh<00:02:48.879> but<00:02:49.360> U<00:02:50.599> hypothetically<00:02:51.599> we 00:02:51.710 --> 00:02:51.720 align:start position:0% make right uh but U hypothetically we 00:02:51.720 --> 00:02:54.830 align:start position:0% make right uh but U hypothetically we can<00:02:51.959> reach<00:02:52.680> a<00:02:52.920> high<00:02:53.120> degree<00:02:53.360> of<00:02:53.480> scalability 00:02:54.830 --> 00:02:54.840 align:start position:0% can reach a high degree of scalability 00:02:54.840 --> 00:02:57.949 align:start position:0% can reach a high degree of scalability naturally<00:02:55.840> um<00:02:56.319> what<00:02:56.519> challenges<00:02:57.319> there<00:02:57.440> are 00:02:57.949 --> 00:02:57.959 align:start position:0% naturally um what challenges there are 00:02:57.959 --> 00:03:01.350 align:start position:0% naturally um what challenges there are so<00:02:58.879> um<00:02:59.360> first<00:02:59.599> one<00:02:59.920> is<00:03:00.000> that<00:03:00.200> we<00:03:00.319> need<00:03:00.760> to<00:03:01.000> build 00:03:01.350 --> 00:03:01.360 align:start position:0% so um first one is that we need to build 00:03:01.360 --> 00:03:04.470 align:start position:0% so um first one is that we need to build one<00:03:02.080> and<00:03:02.280> maintain<00:03:03.080> ourself<00:03:04.080> uh<00:03:04.200> this<00:03:04.319> is 00:03:04.470 --> 00:03:04.480 align:start position:0% one and maintain ourself uh this is 00:03:04.480 --> 00:03:07.110 align:start position:0% one and maintain ourself uh this is challenging<00:03:05.040> because<00:03:06.040> uh<00:03:06.400> the<00:03:06.720> peer-to-peer 00:03:07.110 --> 00:03:07.120 align:start position:0% challenging because uh the peer-to-peer 00:03:07.120 --> 00:03:09.550 align:start position:0% challenging because uh the peer-to-peer networks<00:03:07.720> has<00:03:07.959> a<00:03:08.120> lot<00:03:08.280> of<00:03:08.440> complexity<00:03:09.040> in<00:03:09.239> it 00:03:09.550 --> 00:03:09.560 align:start position:0% networks has a lot of complexity in it 00:03:09.560 --> 00:03:11.949 align:start position:0% networks has a lot of complexity in it like<00:03:10.080> some<00:03:10.720> set<00:03:10.920> of<00:03:11.159> protocols<00:03:11.680> being 00:03:11.949 --> 00:03:11.959 align:start position:0% like some set of protocols being 00:03:11.959 --> 00:03:13.910 align:start position:0% like some set of protocols being implemented<00:03:12.519> so<00:03:12.680> we<00:03:12.840> need<00:03:13.000> to<00:03:13.159> make<00:03:13.319> sure<00:03:13.599> that 00:03:13.910 --> 00:03:13.920 align:start position:0% implemented so we need to make sure that 00:03:13.920 --> 00:03:16.070 align:start position:0% implemented so we need to make sure that all<00:03:14.120> the<00:03:14.239> peers<00:03:14.879> understand<00:03:15.080> each<00:03:15.239> other<00:03:15.920> and 00:03:16.070 --> 00:03:16.080 align:start position:0% all the peers understand each other and 00:03:16.080 --> 00:03:18.309 align:start position:0% all the peers understand each other and then<00:03:16.280> if<00:03:16.440> we<00:03:16.599> let's<00:03:16.760> say<00:03:16.920> release<00:03:17.239> a<00:03:17.400> new<00:03:18.080> uh 00:03:18.309 --> 00:03:18.319 align:start position:0% then if we let's say release a new uh 00:03:18.319 --> 00:03:20.229 align:start position:0% then if we let's say release a new uh version<00:03:18.599> of<00:03:18.720> our<00:03:18.959> software<00:03:19.680> we<00:03:19.799> need<00:03:19.959> to<00:03:20.080> make 00:03:20.229 --> 00:03:20.239 align:start position:0% version of our software we need to make 00:03:20.239 --> 00:03:21.869 align:start position:0% version of our software we need to make sure<00:03:20.480> that<00:03:20.720> it<00:03:21.000> somehow<00:03:21.480> like<00:03:21.680> gets 00:03:21.869 --> 00:03:21.879 align:start position:0% sure that it somehow like gets 00:03:21.879 --> 00:03:24.390 align:start position:0% sure that it somehow like gets propagated<00:03:22.480> or<00:03:22.920> something<00:03:23.920> this<00:03:24.040> is<00:03:24.200> quite 00:03:24.390 --> 00:03:24.400 align:start position:0% propagated or something this is quite 00:03:24.400 --> 00:03:26.190 align:start position:0% propagated or something this is quite challenging<00:03:25.120> uh<00:03:25.280> as<00:03:25.400> well<00:03:25.560> as<00:03:25.680> there<00:03:25.799> is<00:03:25.920> a<00:03:26.040> lot 00:03:26.190 --> 00:03:26.200 align:start position:0% challenging uh as well as there is a lot 00:03:26.200 --> 00:03:30.110 align:start position:0% challenging uh as well as there is a lot of<00:03:26.319> devops<00:03:26.720> involved<00:03:27.239> like<00:03:27.720> whenever<00:03:28.159> we<00:03:29.080> um 00:03:30.110 --> 00:03:30.120 align:start position:0% of devops involved like whenever we um 00:03:30.120 --> 00:03:32.110 align:start position:0% of devops involved like whenever we um whenever<00:03:30.439> we<00:03:30.599> upgrade<00:03:31.040> something<00:03:31.959> uh 00:03:32.110 --> 00:03:32.120 align:start position:0% whenever we upgrade something uh 00:03:32.120 --> 00:03:34.070 align:start position:0% whenever we upgrade something uh something<00:03:32.400> might<00:03:32.599> be<00:03:32.760> down<00:03:33.159> then<00:03:33.400> it<00:03:33.720> impact 00:03:34.070 --> 00:03:34.080 align:start position:0% something might be down then it impact 00:03:34.080 --> 00:03:37.070 align:start position:0% something might be down then it impact some<00:03:34.439> some<00:03:34.720> other<00:03:35.040> people<00:03:35.879> so<00:03:36.599> uh<00:03:36.720> it's 00:03:37.070 --> 00:03:37.080 align:start position:0% some some other people so uh it's 00:03:37.080 --> 00:03:39.789 align:start position:0% some some other people so uh it's difficult<00:03:37.239> to<00:03:37.519> to<00:03:37.760> to<00:03:37.879> do<00:03:38.120> right<00:03:39.120> um 00:03:39.789 --> 00:03:39.799 align:start position:0% difficult to to to do right um 00:03:39.799 --> 00:03:42.670 align:start position:0% difficult to to to do right um reliability<00:03:40.519> is<00:03:40.720> also<00:03:41.200> a<00:03:41.439> big<00:03:41.799> challenge<00:03:42.280> in 00:03:42.670 --> 00:03:42.680 align:start position:0% reliability is also a big challenge in 00:03:42.680 --> 00:03:46.789 align:start position:0% reliability is also a big challenge in peer-to-peer<00:03:43.200> networks<00:03:44.200> um<00:03:45.080> why<00:03:45.519> uh<00:03:45.799> because 00:03:46.789 --> 00:03:46.799 align:start position:0% peer-to-peer networks um why uh because 00:03:46.799 --> 00:03:50.030 align:start position:0% peer-to-peer networks um why uh because uh<00:03:47.319> it<00:03:47.480> also<00:03:47.680> depends<00:03:47.959> on<00:03:48.120> the<00:03:48.360> degree<00:03:48.680> of<00:03:49.040> noes 00:03:50.030 --> 00:03:50.040 align:start position:0% uh it also depends on the degree of noes 00:03:50.040 --> 00:03:52.470 align:start position:0% uh it also depends on the degree of noes amount<00:03:50.280> of<00:03:50.400> notes<00:03:50.640> in<00:03:50.720> the<00:03:50.879> network<00:03:51.680> the<00:03:51.879> less 00:03:52.470 --> 00:03:52.480 align:start position:0% amount of notes in the network the less 00:03:52.480 --> 00:03:55.190 align:start position:0% amount of notes in the network the less there<00:03:52.640> are<00:03:53.120> there<00:03:53.480> more<00:03:53.760> reliabilities<00:03:54.280> so 00:03:55.190 --> 00:03:55.200 align:start position:0% there are there more reliabilities so 00:03:55.200 --> 00:03:57.910 align:start position:0% there are there more reliabilities so like<00:03:55.640> if<00:03:55.840> there<00:03:55.959> is<00:03:56.159> one<00:03:56.480> note<00:03:57.480> it's<00:03:57.680> quite 00:03:57.910 --> 00:03:57.920 align:start position:0% like if there is one note it's quite 00:03:57.920 --> 00:04:00.550 align:start position:0% like if there is one note it's quite reliable<00:03:58.720> if<00:03:58.879> there<00:03:58.959> are<00:03:59.120> more<00:03:59.840> then<00:04:00.239> um<00:04:00.400> it 00:04:00.550 --> 00:04:00.560 align:start position:0% reliable if there are more then um it 00:04:00.560 --> 00:04:03.630 align:start position:0% reliable if there are more then um it comes<00:04:01.120> challenging<00:04:02.120> um<00:04:02.400> to<00:04:02.640> make<00:04:03.120> sure<00:04:03.439> that 00:04:03.630 --> 00:04:03.640 align:start position:0% comes challenging um to make sure that 00:04:03.640 --> 00:04:06.229 align:start position:0% comes challenging um to make sure that all<00:04:03.840> the<00:04:04.120> protocols<00:04:05.120> function<00:04:05.519> correctly<00:04:06.120> and 00:04:06.229 --> 00:04:06.239 align:start position:0% all the protocols function correctly and 00:04:06.239 --> 00:04:08.429 align:start position:0% all the protocols function correctly and the<00:04:06.360> notes<00:04:06.959> propagate<00:04:07.360> the<00:04:07.480> messages<00:04:08.120> in<00:04:08.239> the 00:04:08.429 --> 00:04:08.439 align:start position:0% the notes propagate the messages in the 00:04:08.439 --> 00:04:11.470 align:start position:0% the notes propagate the messages in the right<00:04:09.040> way<00:04:10.040> then<00:04:10.319> uh<00:04:10.439> Network<00:04:11.040> discover<00:04:11.280> is<00:04:11.360> a 00:04:11.470 --> 00:04:11.480 align:start position:0% right way then uh Network discover is a 00:04:11.480 --> 00:04:14.390 align:start position:0% right way then uh Network discover is a huge<00:04:11.720> bottleneck<00:04:12.319> there<00:04:13.159> um<00:04:13.680> all<00:04:14.000> projects 00:04:14.390 --> 00:04:14.400 align:start position:0% huge bottleneck there um all projects 00:04:14.400 --> 00:04:16.430 align:start position:0% huge bottleneck there um all projects made<00:04:14.879> uh<00:04:15.040> different<00:04:15.400> decisions<00:04:16.079> there<00:04:16.280> but 00:04:16.430 --> 00:04:16.440 align:start position:0% made uh different decisions there but 00:04:16.440 --> 00:04:17.830 align:start position:0% made uh different decisions there but more<00:04:16.600> or<00:04:16.759> L<00:04:16.919> there<00:04:17.040> are<00:04:17.160> some<00:04:17.320> patterns<00:04:17.680> that 00:04:17.830 --> 00:04:17.840 align:start position:0% more or L there are some patterns that 00:04:17.840 --> 00:04:21.030 align:start position:0% more or L there are some patterns that everyone<00:04:18.400> follows<00:04:19.400> um<00:04:20.079> and<00:04:20.479> security<00:04:20.840> and 00:04:21.030 --> 00:04:21.040 align:start position:0% everyone follows um and security and 00:04:21.040 --> 00:04:23.230 align:start position:0% everyone follows um and security and traffic<00:04:21.320> management<00:04:22.120> like<00:04:22.320> depending<00:04:22.680> on<00:04:22.880> the 00:04:23.230 --> 00:04:23.240 align:start position:0% traffic management like depending on the 00:04:23.240 --> 00:04:25.430 align:start position:0% traffic management like depending on the architecture<00:04:24.240> of<00:04:24.440> the<00:04:24.639> peer-to-peer<00:04:24.960> Network 00:04:25.430 --> 00:04:25.440 align:start position:0% architecture of the peer-to-peer Network 00:04:25.440 --> 00:04:29.350 align:start position:0% architecture of the peer-to-peer Network we<00:04:25.600> go<00:04:25.800> with<00:04:26.800> uh<00:04:27.240> we<00:04:27.600> incur<00:04:28.320> different<00:04:29.160> uh 00:04:29.350 --> 00:04:29.360 align:start position:0% we go with uh we incur different uh 00:04:29.360 --> 00:04:31.510 align:start position:0% we go with uh we incur different uh pattern<00:04:29.880> of<00:04:30.080> how<00:04:30.759> uh<00:04:30.919> data<00:04:31.160> will<00:04:31.320> be 00:04:31.510 --> 00:04:31.520 align:start position:0% pattern of how uh data will be 00:04:31.520 --> 00:04:33.670 align:start position:0% pattern of how uh data will be propagated<00:04:32.360> so<00:04:32.520> let's<00:04:32.680> say<00:04:32.840> for<00:04:33.199> the<00:04:33.320> case<00:04:33.479> for 00:04:33.670 --> 00:04:33.680 align:start position:0% propagated so let's say for the case for 00:04:33.680 --> 00:04:35.990 align:start position:0% propagated so let's say for the case for vaku<00:04:34.000> that<00:04:34.320> later<00:04:34.560> will<00:04:34.680> be<00:04:34.840> explained<00:04:35.280> by<00:04:35.440> my 00:04:35.990 --> 00:04:36.000 align:start position:0% vaku that later will be explained by my 00:04:36.000 --> 00:04:39.790 align:start position:0% vaku that later will be explained by my colleague<00:04:37.000> um<00:04:37.800> wo<00:04:38.440> goes<00:04:38.759> with<00:04:39.120> gossip<00:04:39.479> sub 00:04:39.790 --> 00:04:39.800 align:start position:0% colleague um wo goes with gossip sub 00:04:39.800 --> 00:04:41.550 align:start position:0% colleague um wo goes with gossip sub architecture<00:04:40.520> and<00:04:40.639> it<00:04:40.840> in<00:04:41.039> course<00:04:41.280> some 00:04:41.550 --> 00:04:41.560 align:start position:0% architecture and it in course some 00:04:41.560 --> 00:04:43.590 align:start position:0% architecture and it in course some particular<00:04:42.400> way<00:04:42.600> of<00:04:42.800> how<00:04:42.960> message<00:04:43.280> is<00:04:43.400> going 00:04:43.590 --> 00:04:43.600 align:start position:0% particular way of how message is going 00:04:43.600 --> 00:04:45.830 align:start position:0% particular way of how message is going to<00:04:43.720> be<00:04:43.880> exchanged<00:04:44.280> in<00:04:44.400> the<00:04:44.560> network<00:04:45.400> uh<00:04:45.520> other 00:04:45.830 --> 00:04:45.840 align:start position:0% to be exchanged in the network uh other 00:04:45.840 --> 00:04:47.710 align:start position:0% to be exchanged in the network uh other people<00:04:46.160> might<00:04:46.680> go<00:04:46.880> with<00:04:47.000> a<00:04:47.120> mixet<00:04:47.560> or 00:04:47.710 --> 00:04:47.720 align:start position:0% people might go with a mixet or 00:04:47.720 --> 00:04:51.029 align:start position:0% people might go with a mixet or something<00:04:48.000> else<00:04:48.280> so<00:04:49.039> depends<00:04:49.960> and<00:04:50.400> uh<00:04:50.639> for<00:04:50.840> the 00:04:51.029 --> 00:04:51.039 align:start position:0% something else so depends and uh for the 00:04:51.039 --> 00:04:53.230 align:start position:0% something else so depends and uh for the security<00:04:51.919> uh<00:04:52.039> there<00:04:52.160> are<00:04:52.360> more<00:04:52.600> parts<00:04:52.919> than 00:04:53.230 --> 00:04:53.240 align:start position:0% security uh there are more parts than 00:04:53.240 --> 00:04:56.350 align:start position:0% security uh there are more parts than just<00:04:53.800> you<00:04:53.919> know<00:04:54.199> encryption<00:04:55.199> any<00:04:55.880> that<00:04:56.120> other 00:04:56.350 --> 00:04:56.360 align:start position:0% just you know encryption any that other 00:04:56.360 --> 00:04:58.390 align:start position:0% just you know encryption any that other people<00:04:56.600> cannot<00:04:56.880> read<00:04:57.160> your<00:04:57.400> data<00:04:58.039> there<00:04:58.160> is 00:04:58.390 --> 00:04:58.400 align:start position:0% people cannot read your data there is 00:04:58.400 --> 00:05:01.670 align:start position:0% people cannot read your data there is also<00:04:58.680> a<00:04:58.880> security<00:04:59.240> of<00:04:59.400> over<00:05:00.080> Network<00:05:01.080> how<00:05:01.479> like 00:05:01.670 --> 00:05:01.680 align:start position:0% also a security of over Network how like 00:05:01.680 --> 00:05:03.790 align:start position:0% also a security of over Network how like identity<00:05:02.120> Seft<00:05:02.560> like<00:05:02.720> let's<00:05:02.880> say<00:05:03.120> if<00:05:03.479> someone 00:05:03.790 --> 00:05:03.800 align:start position:0% identity Seft like let's say if someone 00:05:03.800 --> 00:05:05.350 align:start position:0% identity Seft like let's say if someone can<00:05:03.960> pretend<00:05:04.240> to<00:05:04.360> be<00:05:04.520> someone<00:05:04.840> else<00:05:05.120> in<00:05:05.240> the 00:05:05.350 --> 00:05:05.360 align:start position:0% can pretend to be someone else in the 00:05:05.360 --> 00:05:06.670 align:start position:0% can pretend to be someone else in the peer-to-peer<00:05:05.680> Network<00:05:06.160> it's<00:05:06.440> quite 00:05:06.670 --> 00:05:06.680 align:start position:0% peer-to-peer Network it's quite 00:05:06.680 --> 00:05:08.430 align:start position:0% peer-to-peer Network it's quite challenging<00:05:07.280> and<00:05:07.680> has<00:05:07.800> to<00:05:07.880> be<00:05:08.000> addressed<00:05:08.360> on 00:05:08.430 --> 00:05:08.440 align:start position:0% challenging and has to be addressed on 00:05:08.440 --> 00:05:10.990 align:start position:0% challenging and has to be addressed on the<00:05:08.600> software<00:05:09.000> level<00:05:09.400> somehow<00:05:10.400> uh<00:05:10.479> so<00:05:10.639> we<00:05:10.759> can 00:05:10.990 --> 00:05:11.000 align:start position:0% the software level somehow uh so we can 00:05:11.000 --> 00:05:14.909 align:start position:0% the software level somehow uh so we can use<00:05:11.440> different<00:05:12.080> uh<00:05:12.880> um<00:05:13.639> algorithms<00:05:14.240> here<00:05:14.800> uh 00:05:14.909 --> 00:05:14.919 align:start position:0% use different uh um algorithms here uh 00:05:14.919 --> 00:05:17.430 align:start position:0% use different uh um algorithms here uh the<00:05:15.039> other<00:05:15.360> problem<00:05:15.720> there<00:05:15.880> is<00:05:16.039> that<00:05:16.840> um<00:05:17.320> how 00:05:17.430 --> 00:05:17.440 align:start position:0% the other problem there is that um how 00:05:17.440 --> 00:05:19.629 align:start position:0% the other problem there is that um how to<00:05:17.600> make<00:05:17.919> the<00:05:18.240> network<00:05:18.759> not<00:05:18.919> to<00:05:19.080> go<00:05:19.280> down 00:05:19.629 --> 00:05:19.639 align:start position:0% to make the network not to go down 00:05:19.639 --> 00:05:22.309 align:start position:0% to make the network not to go down because<00:05:19.880> of<00:05:20.080> like<00:05:20.240> some<00:05:20.880> some<00:05:21.880> someone 00:05:22.309 --> 00:05:22.319 align:start position:0% because of like some some someone 00:05:22.319 --> 00:05:25.110 align:start position:0% because of like some some someone malicious<00:05:22.880> there<00:05:23.440> let's<00:05:23.720> say<00:05:24.160> if<00:05:24.560> uh<00:05:24.840> we<00:05:24.960> have 00:05:25.110 --> 00:05:25.120 align:start position:0% malicious there let's say if uh we have 00:05:25.120 --> 00:05:27.550 align:start position:0% malicious there let's say if uh we have a<00:05:25.240> peer<00:05:25.639> that<00:05:25.960> produces<00:05:26.440> 90%<00:05:27.039> of<00:05:27.160> the<00:05:27.319> traffic 00:05:27.550 --> 00:05:27.560 align:start position:0% a peer that produces 90% of the traffic 00:05:27.560 --> 00:05:30.670 align:start position:0% a peer that produces 90% of the traffic overall<00:05:28.080> right<00:05:28.720> uh<00:05:28.960> we<00:05:29.080> don't<00:05:29.280> want 00:05:30.670 --> 00:05:30.680 align:start position:0% overall right uh we don't want 00:05:30.680 --> 00:05:33.070 align:start position:0% overall right uh we don't want single<00:05:31.680> uh<00:05:31.800> node<00:05:32.199> to<00:05:32.360> consume<00:05:32.759> all<00:05:32.960> the 00:05:33.070 --> 00:05:33.080 align:start position:0% single uh node to consume all the 00:05:33.080 --> 00:05:34.830 align:start position:0% single uh node to consume all the resources<00:05:33.479> of<00:05:33.600> the<00:05:33.720> network<00:05:34.160> yeah<00:05:34.440> this<00:05:34.560> is<00:05:34.680> a 00:05:34.830 --> 00:05:34.840 align:start position:0% resources of the network yeah this is a 00:05:34.840 --> 00:05:38.990 align:start position:0% resources of the network yeah this is a security<00:05:35.319> question<00:05:35.639> as<00:05:35.919> well<00:05:36.919> um<00:05:37.560> uh<00:05:37.840> so<00:05:38.400> um 00:05:38.990 --> 00:05:39.000 align:start position:0% security question as well um uh so um 00:05:39.000 --> 00:05:40.710 align:start position:0% security question as well um uh so um how<00:05:39.120> to<00:05:39.240> build<00:05:39.520> the<00:05:39.639> peer-to-peer<00:05:40.000> Network<00:05:40.479> so 00:05:40.710 --> 00:05:40.720 align:start position:0% how to build the peer-to-peer Network so 00:05:40.720 --> 00:05:42.830 align:start position:0% how to build the peer-to-peer Network so these<00:05:40.880> days<00:05:41.240> there<00:05:41.360> are<00:05:41.680> couple<00:05:42.000> Solutions 00:05:42.830 --> 00:05:42.840 align:start position:0% these days there are couple Solutions 00:05:42.840 --> 00:05:44.909 align:start position:0% these days there are couple Solutions usually<00:05:43.199> everyone<00:05:43.520> goes<00:05:43.759> with<00:05:43.880> CT<00:05:44.600> do<00:05:44.759> it 00:05:44.909 --> 00:05:44.919 align:start position:0% usually everyone goes with CT do it 00:05:44.919 --> 00:05:49.029 align:start position:0% usually everyone goes with CT do it yourself<00:05:45.960> diyi<00:05:46.960> um<00:05:47.560> and<00:05:47.960> many<00:05:48.199> projects<00:05:48.680> just 00:05:49.029 --> 00:05:49.039 align:start position:0% yourself diyi um and many projects just 00:05:49.039 --> 00:05:51.670 align:start position:0% yourself diyi um and many projects just go<00:05:49.400> there<00:05:50.080> try<00:05:50.319> to<00:05:50.440> figure<00:05:50.720> it<00:05:50.880> out<00:05:51.520> they 00:05:51.670 --> 00:05:51.680 align:start position:0% go there try to figure it out they 00:05:51.680 --> 00:05:53.350 align:start position:0% go there try to figure it out they figure<00:05:51.960> it<00:05:52.080> out<00:05:52.280> somehow<00:05:52.680> because<00:05:52.960> all<00:05:53.120> of<00:05:53.240> us 00:05:53.350 --> 00:05:53.360 align:start position:0% figure it out somehow because all of us 00:05:53.360 --> 00:05:56.469 align:start position:0% figure it out somehow because all of us are<00:05:53.800> quite<00:05:54.039> good<00:05:54.199> Engineers<00:05:54.759> I<00:05:55.039> I<00:05:55.199> I<00:05:55.360> hope<00:05:56.080> and 00:05:56.469 --> 00:05:56.479 align:start position:0% are quite good Engineers I I I hope and 00:05:56.479 --> 00:05:59.189 align:start position:0% are quite good Engineers I I I hope and uh<00:05:57.039> uh<00:05:57.960> all<00:05:58.160> of<00:05:58.280> them<00:05:58.520> just<00:05:58.720> answered<00:05:59.039> the 00:05:59.189 --> 00:05:59.199 align:start position:0% uh uh all of them just answered the 00:05:59.199 --> 00:06:02.550 align:start position:0% uh uh all of them just answered the questions<00:06:00.000> uh<00:06:00.240> sold<00:06:00.600> it<00:06:01.319> and<00:06:01.720> uh<00:06:01.840> release<00:06:02.400> they 00:06:02.550 --> 00:06:02.560 align:start position:0% questions uh sold it and uh release they 00:06:02.560 --> 00:06:04.550 align:start position:0% questions uh sold it and uh release they use<00:06:02.840> just<00:06:03.080> not<00:06:03.479> Network<00:06:03.800> stack<00:06:04.120> whatever<00:06:04.400> is 00:06:04.550 --> 00:06:04.560 align:start position:0% use just not Network stack whatever is 00:06:04.560 --> 00:06:06.070 align:start position:0% use just not Network stack whatever is available<00:06:05.000> in<00:06:05.199> the<00:06:05.400> language<00:06:05.759> of<00:06:05.880> their 00:06:06.070 --> 00:06:06.080 align:start position:0% available in the language of their 00:06:06.080 --> 00:06:10.589 align:start position:0% available in the language of their choice<00:06:07.039> and<00:06:07.400> um<00:06:07.680> that's<00:06:07.880> it<00:06:08.880> uh<00:06:09.160> but<00:06:09.479> other 00:06:10.589 --> 00:06:10.599 align:start position:0% choice and um that's it uh but other 00:06:10.599 --> 00:06:12.950 align:start position:0% choice and um that's it uh but other projects<00:06:11.599> has<00:06:11.800> figured<00:06:12.120> out<00:06:12.319> that<00:06:12.479> it<00:06:12.639> can<00:06:12.800> be 00:06:12.950 --> 00:06:12.960 align:start position:0% projects has figured out that it can be 00:06:12.960 --> 00:06:17.430 align:start position:0% projects has figured out that it can be scaled<00:06:13.400> somehow<00:06:13.840> so<00:06:14.800> uh<00:06:15.160> Dev<00:06:15.880> uh<00:06:16.199> def<00:06:16.520> P2P<00:06:17.280> and 00:06:17.430 --> 00:06:17.440 align:start position:0% scaled somehow so uh Dev uh def P2P and 00:06:17.440 --> 00:06:21.070 align:start position:0% scaled somehow so uh Dev uh def P2P and Le<00:06:17.680> P2P<00:06:18.039> got<00:06:18.199> born<00:06:19.000> so<00:06:19.360> they<00:06:20.199> uh<00:06:20.560> they<00:06:20.680> appeared 00:06:21.070 --> 00:06:21.080 align:start position:0% Le P2P got born so they uh they appeared 00:06:21.080 --> 00:06:23.670 align:start position:0% Le P2P got born so they uh they appeared approximately<00:06:21.680> the<00:06:21.800> same<00:06:22.080> time<00:06:22.680> def<00:06:22.919> P2P<00:06:23.360> is 00:06:23.670 --> 00:06:23.680 align:start position:0% approximately the same time def P2P is 00:06:23.680 --> 00:06:25.469 align:start position:0% approximately the same time def P2P is very<00:06:23.880> dedicated<00:06:24.319> for<00:06:24.479> ethereum<00:06:24.960> stack<00:06:25.319> and 00:06:25.469 --> 00:06:25.479 align:start position:0% very dedicated for ethereum stack and 00:06:25.479 --> 00:06:27.710 align:start position:0% very dedicated for ethereum stack and it's<00:06:25.800> like<00:06:26.520> something<00:06:26.919> that<00:06:27.160> all<00:06:27.319> ethereum 00:06:27.710 --> 00:06:27.720 align:start position:0% it's like something that all ethereum 00:06:27.720 --> 00:06:30.309 align:start position:0% it's like something that all ethereum nodes<00:06:28.080> implement<00:06:29.080> but<00:06:29.199> there<00:06:29.280> is<00:06:29.599> so<00:06:29.680> l2p 00:06:30.309 --> 00:06:30.319 align:start position:0% nodes implement but there is so l2p 00:06:30.319 --> 00:06:33.830 align:start position:0% nodes implement but there is so l2p which<00:06:30.479> was<00:06:31.080> um<00:06:31.599> more<00:06:31.880> of<00:06:32.160> a<00:06:32.680> generic<00:06:33.319> stack 00:06:33.830 --> 00:06:33.840 align:start position:0% which was um more of a generic stack 00:06:33.840 --> 00:06:35.589 align:start position:0% which was um more of a generic stack like<00:06:34.120> it<00:06:34.199> can<00:06:34.360> be<00:06:34.440> used<00:06:34.680> by<00:06:34.840> any<00:06:35.080> project<00:06:35.479> it 00:06:35.589 --> 00:06:35.599 align:start position:0% like it can be used by any project it 00:06:35.599 --> 00:06:37.870 align:start position:0% like it can be used by any project it does<00:06:35.720> not<00:06:35.960> have<00:06:36.160> any<00:06:36.639> dependency<00:06:37.160> on<00:06:37.360> any 00:06:37.870 --> 00:06:37.880 align:start position:0% does not have any dependency on any 00:06:37.880 --> 00:06:39.070 align:start position:0% does not have any dependency on any blockchain 00:06:39.070 --> 00:06:39.080 align:start position:0% blockchain 00:06:39.080 --> 00:06:41.990 align:start position:0% blockchain whatsoever<00:06:40.080> and<00:06:40.199> it's<00:06:40.360> very<00:06:40.639> modular<00:06:41.639> uh<00:06:41.759> for 00:06:41.990 --> 00:06:42.000 align:start position:0% whatsoever and it's very modular uh for 00:06:42.000 --> 00:06:44.189 align:start position:0% whatsoever and it's very modular uh for waku<00:06:42.400> it<00:06:42.479> is<00:06:42.639> the<00:06:42.800> case<00:06:43.000> that<00:06:43.160> we<00:06:43.560> built<00:06:43.880> on<00:06:44.039> top 00:06:44.189 --> 00:06:44.199 align:start position:0% waku it is the case that we built on top 00:06:44.199 --> 00:06:46.790 align:start position:0% waku it is the case that we built on top of<00:06:44.319> l2p<00:06:44.960> and<00:06:45.080> we<00:06:45.199> extend<00:06:45.520> it<00:06:45.759> with<00:06:46.360> uh<00:06:46.479> our 00:06:46.790 --> 00:06:46.800 align:start position:0% of l2p and we extend it with uh our 00:06:46.800 --> 00:06:48.909 align:start position:0% of l2p and we extend it with uh our protocols<00:06:47.599> we<00:06:47.759> we<00:06:47.919> continue<00:06:48.280> building<00:06:48.639> from 00:06:48.909 --> 00:06:48.919 align:start position:0% protocols we we continue building from 00:06:48.919 --> 00:06:52.790 align:start position:0% protocols we we continue building from there<00:06:49.880> um<00:06:50.400> so<00:06:50.639> shared<00:06:51.199> Parts<00:06:52.199> uh<00:06:52.400> it<00:06:52.560> also 00:06:52.790 --> 00:06:52.800 align:start position:0% there um so shared Parts uh it also 00:06:52.800 --> 00:06:54.390 align:start position:0% there um so shared Parts uh it also somehow<00:06:53.160> related<00:06:53.520> to<00:06:53.639> the<00:06:53.720> challenges<00:06:54.160> that<00:06:54.280> I 00:06:54.390 --> 00:06:54.400 align:start position:0% somehow related to the challenges that I 00:06:54.400 --> 00:06:57.990 align:start position:0% somehow related to the challenges that I mentioned<00:06:55.240> and<00:06:55.560> uh<00:06:55.879> usually<00:06:56.520> we<00:06:56.840> care<00:06:57.160> about 00:06:57.990 --> 00:06:58.000 align:start position:0% mentioned and uh usually we care about 00:06:58.000 --> 00:06:59.909 align:start position:0% mentioned and uh usually we care about peer<00:06:58.479> Discovery<00:06:58.720> in<00:06:58.800> the<00:06:58.919> peer-to-peer<00:06:59.199> net 00:06:59.909 --> 00:06:59.919 align:start position:0% peer Discovery in the peer-to-peer net 00:06:59.919 --> 00:07:02.029 align:start position:0% peer Discovery in the peer-to-peer net right<00:07:00.039> this<00:07:00.120> is<00:07:00.280> obvious<00:07:01.280> unless<00:07:01.560> we<00:07:01.680> know<00:07:01.840> our 00:07:02.029 --> 00:07:02.039 align:start position:0% right this is obvious unless we know our 00:07:02.039 --> 00:07:04.469 align:start position:0% right this is obvious unless we know our peers<00:07:02.400> we<00:07:02.520> cannot<00:07:02.919> form<00:07:03.199> a<00:07:03.319> network<00:07:04.199> and<00:07:04.360> there 00:07:04.469 --> 00:07:04.479 align:start position:0% peers we cannot form a network and there 00:07:04.479 --> 00:07:07.029 align:start position:0% peers we cannot form a network and there are<00:07:04.680> multiple<00:07:05.120> choices<00:07:05.560> that<00:07:06.039> uh<00:07:06.319> projects<00:07:06.759> go 00:07:07.029 --> 00:07:07.039 align:start position:0% are multiple choices that uh projects go 00:07:07.039 --> 00:07:09.909 align:start position:0% are multiple choices that uh projects go with<00:07:07.639> uh<00:07:07.759> some<00:07:07.919> of<00:07:08.080> them<00:07:08.280> are<00:07:08.599> DNS<00:07:09.599> Discovery 00:07:09.909 --> 00:07:09.919 align:start position:0% with uh some of them are DNS Discovery 00:07:09.919 --> 00:07:12.029 align:start position:0% with uh some of them are DNS Discovery we<00:07:10.039> call<00:07:10.280> some<00:07:10.520> particular<00:07:11.319> we<00:07:11.479> get<00:07:11.680> retrieve 00:07:12.029 --> 00:07:12.039 align:start position:0% we call some particular we get retrieve 00:07:12.039 --> 00:07:14.790 align:start position:0% we call some particular we get retrieve some<00:07:12.319> DNS<00:07:12.759> records<00:07:13.759> from<00:07:14.039> there<00:07:14.240> we 00:07:14.790 --> 00:07:14.800 align:start position:0% some DNS records from there we 00:07:14.800 --> 00:07:16.150 align:start position:0% some DNS records from there we understand<00:07:15.039> like<00:07:15.240> this<00:07:15.360> is<00:07:15.560> a<00:07:15.680> set<00:07:15.800> of<00:07:15.879> noes 00:07:16.150 --> 00:07:16.160 align:start position:0% understand like this is a set of noes 00:07:16.160 --> 00:07:18.110 align:start position:0% understand like this is a set of noes that<00:07:16.280> we<00:07:16.400> can<00:07:16.520> use<00:07:16.720> and<00:07:16.879> we<00:07:17.039> go<00:07:17.560> go<00:07:17.720> on<00:07:17.919> with 00:07:18.110 --> 00:07:18.120 align:start position:0% that we can use and we go go on with 00:07:18.120 --> 00:07:21.430 align:start position:0% that we can use and we go go on with them<00:07:19.120> uh<00:07:19.440> some<00:07:20.280> might<00:07:20.520> some<00:07:20.680> choices<00:07:21.080> might<00:07:21.240> be 00:07:21.430 --> 00:07:21.440 align:start position:0% them uh some might some choices might be 00:07:21.440 --> 00:07:23.550 align:start position:0% them uh some might some choices might be like<00:07:21.759> an<00:07:21.960> exchange<00:07:22.440> further<00:07:22.879> exchange<00:07:23.319> like 00:07:23.550 --> 00:07:23.560 align:start position:0% like an exchange further exchange like 00:07:23.560 --> 00:07:25.350 align:start position:0% like an exchange further exchange like we<00:07:23.680> ask<00:07:23.879> the<00:07:24.000> nodes<00:07:24.520> if<00:07:24.680> they<00:07:24.840> know<00:07:25.080> other 00:07:25.350 --> 00:07:25.360 align:start position:0% we ask the nodes if they know other 00:07:25.360 --> 00:07:28.469 align:start position:0% we ask the nodes if they know other nodes<00:07:26.240> right<00:07:26.440> so<00:07:26.680> very<00:07:26.879> natural<00:07:27.400> way<00:07:27.560> of<00:07:27.879> uh<00:07:28.080> of 00:07:28.469 --> 00:07:28.479 align:start position:0% nodes right so very natural way of uh of 00:07:28.479 --> 00:07:30.469 align:start position:0% nodes right so very natural way of uh of discovering<00:07:28.879> a<00:07:29.039> network<00:07:29.680> same<00:07:29.919> as<00:07:30.080> humans 00:07:30.469 --> 00:07:30.479 align:start position:0% discovering a network same as humans 00:07:30.479 --> 00:07:32.830 align:start position:0% discovering a network same as humans Behavior<00:07:31.400> Uh<00:07:31.560> then<00:07:32.000> uh<00:07:32.240> informational 00:07:32.830 --> 00:07:32.840 align:start position:0% Behavior Uh then uh informational 00:07:32.840 --> 00:07:34.670 align:start position:0% Behavior Uh then uh informational exchange<00:07:33.479> so 00:07:34.670 --> 00:07:34.680 align:start position:0% exchange so 00:07:34.680 --> 00:07:38.790 align:start position:0% exchange so um<00:07:35.680> a<00:07:35.879> format<00:07:36.879> uh<00:07:37.000> usually<00:07:38.000> the<00:07:38.120> networks<00:07:38.560> try 00:07:38.790 --> 00:07:38.800 align:start position:0% um a format uh usually the networks try 00:07:38.800 --> 00:07:41.790 align:start position:0% um a format uh usually the networks try to<00:07:39.319> converge<00:07:39.759> into<00:07:39.960> one<00:07:40.160> format<00:07:40.599> so<00:07:41.160> hence 00:07:41.790 --> 00:07:41.800 align:start position:0% to converge into one format so hence 00:07:41.800 --> 00:07:43.710 align:start position:0% to converge into one format so hence there<00:07:41.919> is<00:07:42.039> some<00:07:42.280> specification<00:07:42.960> for<00:07:43.479> a 00:07:43.710 --> 00:07:43.720 align:start position:0% there is some specification for a 00:07:43.720 --> 00:07:45.830 align:start position:0% there is some specification for a package<00:07:44.000> of<00:07:44.240> data<00:07:44.560> that<00:07:44.759> is<00:07:44.919> going<00:07:45.120> to<00:07:45.240> be 00:07:45.830 --> 00:07:45.840 align:start position:0% package of data that is going to be 00:07:45.840 --> 00:07:48.950 align:start position:0% package of data that is going to be populated<00:07:46.440> throughout<00:07:46.800> the<00:07:47.159> network<00:07:48.159> uh<00:07:48.440> then 00:07:48.950 --> 00:07:48.960 align:start position:0% populated throughout the network uh then 00:07:48.960 --> 00:07:50.550 align:start position:0% populated throughout the network uh then uh<00:07:49.080> something<00:07:49.440> specific<00:07:49.800> to<00:07:49.919> the<00:07:50.039> networking 00:07:50.550 --> 00:07:50.560 align:start position:0% uh something specific to the networking 00:07:50.560 --> 00:07:53.029 align:start position:0% uh something specific to the networking in<00:07:50.759> the<00:07:51.440> in<00:07:51.560> the<00:07:51.720> internet<00:07:52.400> is<00:07:52.599> that<00:07:52.759> some 00:07:53.029 --> 00:07:53.039 align:start position:0% in the in the internet is that some 00:07:53.039 --> 00:07:56.230 align:start position:0% in the in the internet is that some peers<00:07:53.680> might<00:07:53.879> be<00:07:54.120> hard<00:07:54.319> to<00:07:54.560> re<00:07:54.800> reach<00:07:55.680> uh<00:07:55.840> so 00:07:56.230 --> 00:07:56.240 align:start position:0% peers might be hard to re reach uh so 00:07:56.240 --> 00:07:58.869 align:start position:0% peers might be hard to re reach uh so hence<00:07:56.520> we<00:07:56.680> need<00:07:56.840> to<00:07:57.520> uh<00:07:57.680> use<00:07:57.919> some<00:07:58.159> ho<00:07:58.479> punching 00:07:58.869 --> 00:07:58.879 align:start position:0% hence we need to uh use some ho punching 00:07:58.879 --> 00:08:00.149 align:start position:0% hence we need to uh use some ho punching techniques 00:08:00.149 --> 00:08:00.159 align:start position:0% techniques 00:08:00.159 --> 00:08:02.909 align:start position:0% techniques uh<00:08:00.639> which<00:08:00.800> means<00:08:01.159> that<00:08:01.599> if<00:08:01.759> I<00:08:01.919> cannot<00:08:02.400> dial<00:08:02.720> you 00:08:02.909 --> 00:08:02.919 align:start position:0% uh which means that if I cannot dial you 00:08:02.919 --> 00:08:06.790 align:start position:0% uh which means that if I cannot dial you directly<00:08:03.440> maybe<00:08:03.960> we<00:08:04.240> can<00:08:05.240> bypass<00:08:05.680> it<00:08:05.879> somehow 00:08:06.790 --> 00:08:06.800 align:start position:0% directly maybe we can bypass it somehow 00:08:06.800 --> 00:08:10.189 align:start position:0% directly maybe we can bypass it somehow like<00:08:07.039> you<00:08:07.280> dial<00:08:07.639> me<00:08:07.840> instead<00:08:08.759> or<00:08:09.400> uh<00:08:09.560> let's<00:08:09.800> say 00:08:10.189 --> 00:08:10.199 align:start position:0% like you dial me instead or uh let's say 00:08:10.199 --> 00:08:12.909 align:start position:0% like you dial me instead or uh let's say uh<00:08:10.360> if<00:08:10.840> uh<00:08:11.479> it<00:08:11.599> is<00:08:11.720> not<00:08:12.000> possible<00:08:12.560> it's 00:08:12.909 --> 00:08:12.919 align:start position:0% uh if uh it is not possible it's 00:08:12.919 --> 00:08:15.390 align:start position:0% uh if uh it is not possible it's approximately<00:08:13.520> I<00:08:13.599> think<00:08:13.759> 30%<00:08:14.440> of<00:08:14.639> the<00:08:15.120> of<00:08:15.240> the 00:08:15.390 --> 00:08:15.400 align:start position:0% approximately I think 30% of the of the 00:08:15.400 --> 00:08:18.110 align:start position:0% approximately I think 30% of the of the users<00:08:15.720> overall<00:08:16.360> which<00:08:16.479> is<00:08:16.639> the<00:08:16.759> case<00:08:16.960> for<00:08:17.840> uh 00:08:18.110 --> 00:08:18.120 align:start position:0% users overall which is the case for uh 00:08:18.120 --> 00:08:21.110 align:start position:0% users overall which is the case for uh some<00:08:18.400> protocols<00:08:19.400> we<00:08:19.560> may<00:08:19.800> do<00:08:20.000> relaying<00:08:20.680> we<00:08:20.800> so 00:08:21.110 --> 00:08:21.120 align:start position:0% some protocols we may do relaying we so 00:08:21.120 --> 00:08:23.110 align:start position:0% some protocols we may do relaying we so which<00:08:21.280> means<00:08:21.560> that<00:08:22.080> I<00:08:22.159> am<00:08:22.360> going<00:08:22.560> to<00:08:22.759> ask<00:08:22.960> some 00:08:23.110 --> 00:08:23.120 align:start position:0% which means that I am going to ask some 00:08:23.120 --> 00:08:25.629 align:start position:0% which means that I am going to ask some other<00:08:23.479> peer<00:08:23.720> to<00:08:23.840> relay<00:08:24.159> you<00:08:24.319> some<00:08:25.039> some<00:08:25.319> data 00:08:25.629 --> 00:08:25.639 align:start position:0% other peer to relay you some some data 00:08:25.639 --> 00:08:27.830 align:start position:0% other peer to relay you some some data that<00:08:25.960> I<00:08:26.080> want<00:08:26.280> you<00:08:26.400> to<00:08:26.560> see<00:08:27.199> and<00:08:27.360> you<00:08:27.520> do<00:08:27.720> the 00:08:27.830 --> 00:08:27.840 align:start position:0% that I want you to see and you do the 00:08:27.840 --> 00:08:30.990 align:start position:0% that I want you to see and you do the same<00:08:28.039> so<00:08:28.240> we<00:08:28.560> like<00:08:28.759> bypass<00:08:29.240> this<00:08:29.759> uh<00:08:30.159> this<00:08:30.440> this 00:08:30.990 --> 00:08:31.000 align:start position:0% same so we like bypass this uh this this 00:08:31.000 --> 00:08:34.469 align:start position:0% same so we like bypass this uh this this W<00:08:31.199> in<00:08:31.319> between<00:08:31.639> us<00:08:32.519> um<00:08:32.959> then<00:08:33.159> the<00:08:33.279> other<00:08:34.039> uh 00:08:34.469 --> 00:08:34.479 align:start position:0% W in between us um then the other uh 00:08:34.479 --> 00:08:36.709 align:start position:0% W in between us um then the other uh shared<00:08:34.959> Parts<00:08:35.240> is<00:08:35.399> that<00:08:35.800> all<00:08:36.039> the<00:08:36.159> networks 00:08:36.709 --> 00:08:36.719 align:start position:0% shared Parts is that all the networks 00:08:36.719 --> 00:08:40.350 align:start position:0% shared Parts is that all the networks try<00:08:37.000> to<00:08:37.200> somehow<00:08:37.800> secure<00:08:38.320> themsel<00:08:39.320> from<00:08:39.760> dos 00:08:40.350 --> 00:08:40.360 align:start position:0% try to somehow secure themsel from dos 00:08:40.360 --> 00:08:43.149 align:start position:0% try to somehow secure themsel from dos so<00:08:40.800> and<00:08:41.240> some<00:08:41.479> dos<00:08:41.880> protection<00:08:42.360> come<00:08:42.680> comes<00:08:42.919> in 00:08:43.149 --> 00:08:43.159 align:start position:0% so and some dos protection come comes in 00:08:43.159 --> 00:08:45.670 align:start position:0% so and some dos protection come comes in play<00:08:43.680> and<00:08:43.839> spam<00:08:44.240> protection<00:08:45.000> how<00:08:45.160> it<00:08:45.279> should 00:08:45.670 --> 00:08:45.680 align:start position:0% play and spam protection how it should 00:08:45.680 --> 00:08:47.269 align:start position:0% play and spam protection how it should how<00:08:45.839> it<00:08:45.959> can<00:08:46.120> be<00:08:46.279> addressed<00:08:46.800> by<00:08:47.000> different 00:08:47.269 --> 00:08:47.279 align:start position:0% how it can be addressed by different 00:08:47.279 --> 00:08:49.550 align:start position:0% how it can be addressed by different meanings<00:08:47.800> usually<00:08:48.160> it<00:08:48.360> might<00:08:48.600> be<00:08:49.000> like<00:08:49.279> some 00:08:49.550 --> 00:08:49.560 align:start position:0% meanings usually it might be like some 00:08:49.560 --> 00:08:51.949 align:start position:0% meanings usually it might be like some tokens<00:08:50.240> token<00:08:50.640> exchange<00:08:51.320> there<00:08:51.519> might<00:08:51.720> be 00:08:51.949 --> 00:08:51.959 align:start position:0% tokens token exchange there might be 00:08:51.959 --> 00:08:57.870 align:start position:0% tokens token exchange there might be some<00:08:52.959> uh<00:08:53.360> common<00:08:53.760> shared<00:08:54.680> uh<00:08:55.680> uh<00:08:55.839> record<00:08:56.839> of<00:08:57.480> uh 00:08:57.870 --> 00:08:57.880 align:start position:0% some uh common shared uh uh record of uh 00:08:57.880 --> 00:09:00.230 align:start position:0% some uh common shared uh uh record of uh peers<00:08:58.320> that<00:08:58.480> are<00:08:59.120> like<00:08:59.440> reliable<00:08:59.920> whatever 00:09:00.230 --> 00:09:00.240 align:start position:0% peers that are like reliable whatever 00:09:00.240 --> 00:09:02.910 align:start position:0% peers that are like reliable whatever they<00:09:00.399> can<00:09:00.519> be<00:09:00.640> used<00:09:01.160> can<00:09:01.279> be<00:09:01.399> trusted<00:09:02.240> so 00:09:02.910 --> 00:09:02.920 align:start position:0% they can be used can be trusted so 00:09:02.920 --> 00:09:05.910 align:start position:0% they can be used can be trusted so different<00:09:03.279> ways<00:09:04.120> um<00:09:04.440> but<00:09:04.959> one<00:09:05.240> of<00:09:05.399> the<00:09:05.519> most 00:09:05.910 --> 00:09:05.920 align:start position:0% different ways um but one of the most 00:09:05.920 --> 00:09:07.389 align:start position:0% different ways um but one of the most difficult<00:09:06.160> Parts<00:09:06.440> here<00:09:06.600> is<00:09:06.720> that<00:09:06.920> it's<00:09:07.120> hard 00:09:07.389 --> 00:09:07.399 align:start position:0% difficult Parts here is that it's hard 00:09:07.399 --> 00:09:10.470 align:start position:0% difficult Parts here is that it's hard to<00:09:07.519> make<00:09:07.720> it<00:09:08.640> uh<00:09:09.200> in<00:09:09.320> a<00:09:09.560> privacy<00:09:10.000> preserving 00:09:10.470 --> 00:09:10.480 align:start position:0% to make it uh in a privacy preserving 00:09:10.480 --> 00:09:13.069 align:start position:0% to make it uh in a privacy preserving way<00:09:10.680> so<00:09:10.880> that<00:09:11.120> we<00:09:11.279> don't<00:09:11.880> uh<00:09:12.040> release<00:09:12.480> some 00:09:13.069 --> 00:09:13.079 align:start position:0% way so that we don't uh release some 00:09:13.079 --> 00:09:15.630 align:start position:0% way so that we don't uh release some Identity<00:09:13.600> or<00:09:13.800> we<00:09:13.920> don't<00:09:14.200> even<00:09:14.720> know<00:09:15.079> who<00:09:15.320> is 00:09:15.630 --> 00:09:15.640 align:start position:0% Identity or we don't even know who is 00:09:15.640 --> 00:09:18.870 align:start position:0% Identity or we don't even know who is pure<00:09:16.200> actually<00:09:16.560> is<00:09:17.279> uh<00:09:17.399> and<00:09:17.600> vaku<00:09:18.000> has<00:09:18.519> found 00:09:18.870 --> 00:09:18.880 align:start position:0% pure actually is uh and vaku has found 00:09:18.880 --> 00:09:20.430 align:start position:0% pure actually is uh and vaku has found some<00:09:19.160> answer<00:09:19.480> in<00:09:19.640> partnership<00:09:20.040> with<00:09:20.200> other 00:09:20.430 --> 00:09:20.440 align:start position:0% some answer in partnership with other 00:09:20.440 --> 00:09:23.710 align:start position:0% some answer in partnership with other projects<00:09:20.760> in<00:09:20.880> the<00:09:21.079> space<00:09:22.120> um<00:09:23.120> other<00:09:23.399> shared 00:09:23.710 --> 00:09:23.720 align:start position:0% projects in the space um other shared 00:09:23.720 --> 00:09:27.630 align:start position:0% projects in the space um other shared Parts<00:09:23.920> is<00:09:24.079> at<00:09:24.320> transport<00:09:25.240> transport<00:09:26.240> so<00:09:26.880> uh 00:09:27.630 --> 00:09:27.640 align:start position:0% Parts is at transport transport so uh 00:09:27.640 --> 00:09:30.750 align:start position:0% Parts is at transport transport so uh this<00:09:27.800> one<00:09:28.360> is<00:09:28.600> very<00:09:28.760> important<00:09:29.440> because<00:09:30.440> uh<00:09:30.600> if 00:09:30.750 --> 00:09:30.760 align:start position:0% this one is very important because uh if 00:09:30.760 --> 00:09:33.949 align:start position:0% this one is very important because uh if our<00:09:31.399> nodes<00:09:31.880> in<00:09:32.000> the<00:09:32.160> network<00:09:33.079> uh<00:09:33.480> Implement 00:09:33.949 --> 00:09:33.959 align:start position:0% our nodes in the network uh Implement 00:09:33.959 --> 00:09:35.910 align:start position:0% our nodes in the network uh Implement more<00:09:34.200> transports<00:09:34.959> such<00:09:35.120> as<00:09:35.320> websockets 00:09:35.910 --> 00:09:35.920 align:start position:0% more transports such as websockets 00:09:35.920 --> 00:09:40.910 align:start position:0% more transports such as websockets websocket<00:09:36.440> secures<00:09:37.240> uh<00:09:37.600> TCP<00:09:38.519> UDP<00:09:39.519> uh<00:09:39.839> web<00:09:40.200> RTC 00:09:40.910 --> 00:09:40.920 align:start position:0% websocket secures uh TCP UDP uh web RTC 00:09:40.920 --> 00:09:43.350 align:start position:0% websocket secures uh TCP UDP uh web RTC web<00:09:41.160> transport<00:09:42.040> the<00:09:42.160> more<00:09:42.519> they<00:09:42.880> transport 00:09:43.350 --> 00:09:43.360 align:start position:0% web transport the more they transport 00:09:43.360 --> 00:09:45.110 align:start position:0% web transport the more they transport they<00:09:43.519> Implement<00:09:44.200> uh<00:09:44.360> the<00:09:44.440> more<00:09:44.640> clients<00:09:45.000> they 00:09:45.110 --> 00:09:45.120 align:start position:0% they Implement uh the more clients they 00:09:45.120 --> 00:09:48.710 align:start position:0% they Implement uh the more clients they can<00:09:45.480> reach<00:09:46.480> uh<00:09:47.000> like<00:09:47.399> let's<00:09:47.600> say<00:09:47.959> if<00:09:48.320> uh<00:09:48.560> we 00:09:48.710 --> 00:09:48.720 align:start position:0% can reach uh like let's say if uh we 00:09:48.720 --> 00:09:51.110 align:start position:0% can reach uh like let's say if uh we have<00:09:48.880> a<00:09:49.120> websocket<00:09:49.640> implemented<00:09:50.480> we<00:09:50.600> can<00:09:50.959> be 00:09:51.110 --> 00:09:51.120 align:start position:0% have a websocket implemented we can be 00:09:51.120 --> 00:09:53.590 align:start position:0% have a websocket implemented we can be sure<00:09:51.480> that<00:09:51.839> our<00:09:52.079> node<00:09:52.440> can<00:09:52.680> function<00:09:53.079> not<00:09:53.360> only 00:09:53.590 --> 00:09:53.600 align:start position:0% sure that our node can function not only 00:09:53.600 --> 00:09:57.310 align:start position:0% sure that our node can function not only between<00:09:54.079> like<00:09:54.320> some<00:09:55.240> uh<00:09:55.640> some<00:09:56.160> Ser<00:09:56.480> servers 00:09:57.310 --> 00:09:57.320 align:start position:0% between like some uh some Ser servers 00:09:57.320 --> 00:10:00.509 align:start position:0% between like some uh some Ser servers right<00:09:57.680> but<00:09:57.880> also<00:09:58.160> with<00:09:58.519> browsers<00:09:59.040> so<00:09:59.480> hence<00:09:59.760> we 00:10:00.509 --> 00:10:00.519 align:start position:0% right but also with browsers so hence we 00:10:00.519 --> 00:10:03.550 align:start position:0% right but also with browsers so hence we uh<00:10:00.800> can<00:10:00.959> serve<00:10:01.279> more<00:10:01.640> users<00:10:02.640> um<00:10:02.920> and<00:10:03.120> much<00:10:03.279> more 00:10:03.550 --> 00:10:03.560 align:start position:0% uh can serve more users um and much more 00:10:03.560 --> 00:10:05.790 align:start position:0% uh can serve more users um and much more so<00:10:03.839> there<00:10:03.959> is<00:10:04.079> a<00:10:04.200> bandwidth<00:10:04.720> management<00:10:05.360> like 00:10:05.790 --> 00:10:05.800 align:start position:0% so there is a bandwidth management like 00:10:05.800 --> 00:10:07.630 align:start position:0% so there is a bandwidth management like how<00:10:05.959> to<00:10:06.160> make<00:10:06.320> sure<00:10:06.600> that<00:10:06.760> our<00:10:06.959> nodes<00:10:07.240> are<00:10:07.440> very 00:10:07.630 --> 00:10:07.640 align:start position:0% how to make sure that our nodes are very 00:10:07.640 --> 00:10:09.630 align:start position:0% how to make sure that our nodes are very ecological<00:10:08.480> in<00:10:08.600> the<00:10:08.760> resources<00:10:09.240> that<00:10:09.399> they 00:10:09.630 --> 00:10:09.640 align:start position:0% ecological in the resources that they 00:10:09.640 --> 00:10:12.910 align:start position:0% ecological in the resources that they have<00:10:10.440> uh<00:10:10.600> the<00:10:10.800> reputation<00:10:11.560> like<00:10:11.800> we<00:10:11.920> want<00:10:12.120> to 00:10:12.910 --> 00:10:12.920 align:start position:0% have uh the reputation like we want to 00:10:12.920 --> 00:10:15.030 align:start position:0% have uh the reputation like we want to make<00:10:13.120> sure<00:10:13.480> that<00:10:13.680> the<00:10:13.839> peers<00:10:14.240> which<00:10:14.480> we<00:10:14.600> are 00:10:15.030 --> 00:10:15.040 align:start position:0% make sure that the peers which we are 00:10:15.040 --> 00:10:17.670 align:start position:0% make sure that the peers which we are talking<00:10:15.480> at<00:10:15.760> hog<00:10:16.079> right<00:10:16.279> now<00:10:17.000> uh<00:10:17.120> are<00:10:17.320> more<00:10:17.480> or 00:10:17.670 --> 00:10:17.680 align:start position:0% talking at hog right now uh are more or 00:10:17.680 --> 00:10:20.750 align:start position:0% talking at hog right now uh are more or less<00:10:18.040> fine<00:10:18.360> or<00:10:18.560> not<00:10:19.480> uh<00:10:19.640> encryption<00:10:20.360> this<00:10:20.480> is<00:10:20.600> a 00:10:20.750 --> 00:10:20.760 align:start position:0% less fine or not uh encryption this is a 00:10:20.760 --> 00:10:22.990 align:start position:0% less fine or not uh encryption this is a huge<00:10:21.200> question<00:10:21.560> as<00:10:21.720> well<00:10:21.920> like<00:10:22.120> we<00:10:22.240> don't<00:10:22.480> want 00:10:22.990 --> 00:10:23.000 align:start position:0% huge question as well like we don't want 00:10:23.000 --> 00:10:24.430 align:start position:0% huge question as well like we don't want the<00:10:23.120> whole<00:10:23.399> network<00:10:23.800> know<00:10:24.040> what<00:10:24.160> we<00:10:24.240> are 00:10:24.430 --> 00:10:24.440 align:start position:0% the whole network know what we are 00:10:24.440 --> 00:10:26.790 align:start position:0% the whole network know what we are talking<00:10:24.760> about<00:10:25.120> what<00:10:25.240> we<00:10:25.399> exchange<00:10:26.040> right<00:10:26.519> and 00:10:26.790 --> 00:10:26.800 align:start position:0% talking about what we exchange right and 00:10:26.800 --> 00:10:29.829 align:start position:0% talking about what we exchange right and and<00:10:26.959> routing<00:10:27.760> uh<00:10:27.880> more<00:10:28.040> or<00:10:28.240> less<00:10:28.760> um 00:10:29.829 --> 00:10:29.839 align:start position:0% and routing uh more or less um 00:10:29.839 --> 00:10:32.190 align:start position:0% and routing uh more or less um so<00:10:30.079> hence<00:10:30.320> there<00:10:30.399> are<00:10:30.839> some<00:10:31.040> tradeoffs<00:10:32.000> that 00:10:32.190 --> 00:10:32.200 align:start position:0% so hence there are some tradeoffs that 00:10:32.200 --> 00:10:34.990 align:start position:0% so hence there are some tradeoffs that we<00:10:32.360> make<00:10:33.200> uh<00:10:33.360> while<00:10:33.600> building<00:10:34.000> the<00:10:34.160> networks 00:10:34.990 --> 00:10:35.000 align:start position:0% we make uh while building the networks 00:10:35.000 --> 00:10:36.790 align:start position:0% we make uh while building the networks and<00:10:35.240> one<00:10:35.360> of<00:10:35.519> them<00:10:35.720> is<00:10:35.839> that<00:10:36.040> do<00:10:36.160> we<00:10:36.320> want<00:10:36.480> to 00:10:36.790 --> 00:10:36.800 align:start position:0% and one of them is that do we want to 00:10:36.800 --> 00:10:39.470 align:start position:0% and one of them is that do we want to have<00:10:37.040> a<00:10:37.320> one<00:10:37.600> huge<00:10:37.920> Network<00:10:38.680> or<00:10:38.920> we<00:10:39.040> want<00:10:39.240> to 00:10:39.470 --> 00:10:39.480 align:start position:0% have a one huge Network or we want to 00:10:39.480 --> 00:10:42.509 align:start position:0% have a one huge Network or we want to have<00:10:40.000> like<00:10:40.360> uh<00:10:40.880> some<00:10:41.200> Sub<00:10:41.519> sub<00:10:41.760> networks<00:10:42.240> that 00:10:42.509 --> 00:10:42.519 align:start position:0% have like uh some Sub sub networks that 00:10:42.519 --> 00:10:44.790 align:start position:0% have like uh some Sub sub networks that somehow<00:10:43.160> talk<00:10:43.360> to<00:10:43.519> each<00:10:43.639> other<00:10:43.959> later<00:10:44.240> on<00:10:44.720> I 00:10:44.790 --> 00:10:44.800 align:start position:0% somehow talk to each other later on I 00:10:44.800 --> 00:10:48.590 align:start position:0% somehow talk to each other later on I don't<00:10:44.959> know<00:10:45.839> um<00:10:46.639> if<00:10:46.839> we<00:10:47.000> do<00:10:47.279> some<00:10:47.480> sharding<00:10:48.440> how 00:10:48.590 --> 00:10:48.600 align:start position:0% don't know um if we do some sharding how 00:10:48.600 --> 00:10:51.110 align:start position:0% don't know um if we do some sharding how many<00:10:48.920> of<00:10:49.120> them<00:10:49.320> we<00:10:49.480> want<00:10:49.920> like<00:10:50.160> one<00:10:50.480> two<00:10:50.880> two 00:10:51.110 --> 00:10:51.120 align:start position:0% many of them we want like one two two 00:10:51.120 --> 00:10:53.389 align:start position:0% many of them we want like one two two groups<00:10:51.760> three<00:10:52.079> groups<00:10:52.680> depending<00:10:53.040> on<00:10:53.200> the 00:10:53.389 --> 00:10:53.399 align:start position:0% groups three groups depending on the 00:10:53.399 --> 00:10:56.430 align:start position:0% groups three groups depending on the content<00:10:53.959> content<00:10:54.440> exchanged<00:10:55.079> maybe<00:10:55.920> right<00:10:56.160> so 00:10:56.430 --> 00:10:56.440 align:start position:0% content content exchanged maybe right so 00:10:56.440 --> 00:10:58.509 align:start position:0% content content exchanged maybe right so this<00:10:56.560> is<00:10:56.680> a<00:10:56.800> conscious<00:10:57.160> choice<00:10:57.480> that<00:10:57.639> we<00:10:57.839> as<00:10:58.079> uh 00:10:58.509 --> 00:10:58.519 align:start position:0% this is a conscious choice that we as uh 00:10:58.519 --> 00:11:02.350 align:start position:0% this is a conscious choice that we as uh Developers<00:10:59.639> have<00:10:59.800> to<00:10:59.959> make<00:11:00.880> uh<00:11:01.120> here<00:11:01.880> then<00:11:02.240> uh 00:11:02.350 --> 00:11:02.360 align:start position:0% Developers have to make uh here then uh 00:11:02.360 --> 00:11:04.910 align:start position:0% Developers have to make uh here then uh a<00:11:02.480> message<00:11:02.839> size<00:11:03.200> right<00:11:03.320> a<00:11:03.519> data<00:11:03.880> data<00:11:04.200> packet 00:11:04.910 --> 00:11:04.920 align:start position:0% a message size right a data data packet 00:11:04.920 --> 00:11:07.389 align:start position:0% a message size right a data data packet the<00:11:05.120> bigger<00:11:05.480> it<00:11:05.639> is<00:11:05.839> the<00:11:06.000> slower<00:11:06.800> propagation 00:11:07.389 --> 00:11:07.399 align:start position:0% the bigger it is the slower propagation 00:11:07.399 --> 00:11:09.069 align:start position:0% the bigger it is the slower propagation of<00:11:07.560> it<00:11:07.720> will<00:11:07.880> be<00:11:08.079> through<00:11:08.279> the<00:11:08.399> network 00:11:09.069 --> 00:11:09.079 align:start position:0% of it will be through the network 00:11:09.079 --> 00:11:11.310 align:start position:0% of it will be through the network regardless<00:11:09.560> of<00:11:09.720> the<00:11:10.320> architectural<00:11:11.040> choice 00:11:11.310 --> 00:11:11.320 align:start position:0% regardless of the architectural choice 00:11:11.320 --> 00:11:13.910 align:start position:0% regardless of the architectural choice of<00:11:11.480> it<00:11:11.880> right<00:11:12.279> so<00:11:12.519> we<00:11:12.639> want<00:11:12.839> to<00:11:13.079> be<00:11:13.360> cautious<00:11:13.760> of 00:11:13.910 --> 00:11:13.920 align:start position:0% of it right so we want to be cautious of 00:11:13.920 --> 00:11:15.629 align:start position:0% of it right so we want to be cautious of it<00:11:14.079> and<00:11:14.240> we<00:11:14.360> want<00:11:14.519> to<00:11:14.680> make<00:11:14.880> the<00:11:15.000> best<00:11:15.279> choice 00:11:15.629 --> 00:11:15.639 align:start position:0% it and we want to make the best choice 00:11:15.639 --> 00:11:18.190 align:start position:0% it and we want to make the best choice for<00:11:15.839> our<00:11:16.120> particular<00:11:16.839> particular 00:11:18.190 --> 00:11:18.200 align:start position:0% for our particular particular 00:11:18.200 --> 00:11:21.990 align:start position:0% for our particular particular need<00:11:19.200> uh<00:11:19.360> and<00:11:19.600> then<00:11:20.600> rate<00:11:20.880> limiting<00:11:21.480> right<00:11:21.680> we 00:11:21.990 --> 00:11:22.000 align:start position:0% need uh and then rate limiting right we 00:11:22.000 --> 00:11:24.310 align:start position:0% need uh and then rate limiting right we don't<00:11:22.240> want<00:11:22.839> uh<00:11:23.279> anyone<00:11:23.560> spam<00:11:23.880> the<00:11:23.959> network 00:11:24.310 --> 00:11:24.320 align:start position:0% don't want uh anyone spam the network 00:11:24.320 --> 00:11:26.470 align:start position:0% don't want uh anyone spam the network consume<00:11:24.680> all<00:11:24.800> the<00:11:24.920> resources<00:11:25.399> so<00:11:26.240> which 00:11:26.470 --> 00:11:26.480 align:start position:0% consume all the resources so which 00:11:26.480 --> 00:11:28.470 align:start position:0% consume all the resources so which technology<00:11:26.959> we<00:11:27.120> use<00:11:27.360> are<00:11:27.519> we<00:11:27.680> fine<00:11:28.000> with 00:11:28.470 --> 00:11:28.480 align:start position:0% technology we use are we fine with 00:11:28.480 --> 00:11:31.110 align:start position:0% technology we use are we fine with having<00:11:29.320> let's<00:11:29.440> say<00:11:29.639> common<00:11:29.959> Ledger<00:11:30.959> of 00:11:31.110 --> 00:11:31.120 align:start position:0% having let's say common Ledger of 00:11:31.120 --> 00:11:33.829 align:start position:0% having let's say common Ledger of trusted<00:11:31.480> nodes<00:11:31.839> or<00:11:32.000> we<00:11:32.120> want<00:11:32.320> to<00:11:32.519> be<00:11:33.079> more<00:11:33.399> open 00:11:33.829 --> 00:11:33.839 align:start position:0% trusted nodes or we want to be more open 00:11:33.839 --> 00:11:35.590 align:start position:0% trusted nodes or we want to be more open like<00:11:34.160> publicly<00:11:34.560> available<00:11:35.000> Network<00:11:35.399> that 00:11:35.590 --> 00:11:35.600 align:start position:0% like publicly available Network that 00:11:35.600 --> 00:11:38.069 align:start position:0% like publicly available Network that anyone<00:11:35.959> can<00:11:36.120> join<00:11:37.000> uh<00:11:37.079> so<00:11:37.440> in<00:11:37.560> that<00:11:37.760> case<00:11:37.959> what 00:11:38.069 --> 00:11:38.079 align:start position:0% anyone can join uh so in that case what 00:11:38.079 --> 00:11:40.949 align:start position:0% anyone can join uh so in that case what do<00:11:38.200> we<00:11:38.360> do<00:11:39.040> uh<00:11:39.200> how<00:11:39.360> do<00:11:39.480> we<00:11:39.639> address<00:11:39.920> it<00:11:40.720> I<00:11:40.800> don't 00:11:40.949 --> 00:11:40.959 align:start position:0% do we do uh how do we address it I don't 00:11:40.959 --> 00:11:43.829 align:start position:0% do we do uh how do we address it I don't know<00:11:41.399> it<00:11:41.560> depends<00:11:42.480> uh<00:11:42.680> incentivization<00:11:43.680> right 00:11:43.829 --> 00:11:43.839 align:start position:0% know it depends uh incentivization right 00:11:43.839 --> 00:11:47.030 align:start position:0% know it depends uh incentivization right so<00:11:44.320> some<00:11:44.519> of<00:11:44.680> the<00:11:44.880> projects<00:11:45.680> public<00:11:46.040> networks 00:11:47.030 --> 00:11:47.040 align:start position:0% so some of the projects public networks 00:11:47.040 --> 00:11:48.949 align:start position:0% so some of the projects public networks have<00:11:47.200> no<00:11:47.399> incentivization<00:11:48.240> but<00:11:48.440> they<00:11:48.639> still 00:11:48.949 --> 00:11:48.959 align:start position:0% have no incentivization but they still 00:11:48.959 --> 00:11:51.269 align:start position:0% have no incentivization but they still function<00:11:49.440> well<00:11:50.279> uh<00:11:50.399> and<00:11:50.600> why<00:11:50.720> it<00:11:50.839> happens<00:11:51.120> is 00:11:51.269 --> 00:11:51.279 align:start position:0% function well uh and why it happens is 00:11:51.279 --> 00:11:53.509 align:start position:0% function well uh and why it happens is that<00:11:51.680> because<00:11:51.920> people<00:11:52.120> share<00:11:52.399> a<00:11:52.519> common<00:11:52.839> cause 00:11:53.509 --> 00:11:53.519 align:start position:0% that because people share a common cause 00:11:53.519 --> 00:11:55.550 align:start position:0% that because people share a common cause they<00:11:53.680> want<00:11:54.040> to<00:11:54.399> be<00:11:54.680> part<00:11:54.839> of<00:11:55.000> this<00:11:55.120> network 00:11:55.550 --> 00:11:55.560 align:start position:0% they want to be part of this network 00:11:55.560 --> 00:11:57.509 align:start position:0% they want to be part of this network because<00:11:55.880> it<00:11:56.120> let's<00:11:56.320> say<00:11:56.519> gives<00:11:56.720> some<00:11:56.959> privacy 00:11:57.509 --> 00:11:57.519 align:start position:0% because it let's say gives some privacy 00:11:57.519 --> 00:11:59.949 align:start position:0% because it let's say gives some privacy it<00:11:57.680> gives<00:11:58.120> uh<00:11:58.480> underprivileged<00:11:59.279> people<00:11:59.519> AR<00:11:59.760> to 00:11:59.949 --> 00:11:59.959 align:start position:0% it gives uh underprivileged people AR to 00:11:59.959 --> 00:12:03.790 align:start position:0% it gives uh underprivileged people AR to internet<00:12:00.440> without<00:12:00.720> them<00:12:01.399> uh<00:12:01.600> fearing<00:12:02.600> for<00:12:03.480> any 00:12:03.790 --> 00:12:03.800 align:start position:0% internet without them uh fearing for any 00:12:03.800 --> 00:12:05.910 align:start position:0% internet without them uh fearing for any consequences<00:12:04.480> or<00:12:04.680> something<00:12:05.120> or<00:12:05.440> just<00:12:05.600> buying 00:12:05.910 --> 00:12:05.920 align:start position:0% consequences or something or just buying 00:12:05.920 --> 00:12:09.269 align:start position:0% consequences or something or just buying drugs<00:12:06.519> whoever<00:12:07.560> whatever 00:12:09.269 --> 00:12:09.279 align:start position:0% drugs whoever whatever 00:12:09.279 --> 00:12:12.269 align:start position:0% drugs whoever whatever um<00:12:10.279> and<00:12:10.680> Discovery<00:12:11.000> protocols<00:12:11.600> like<00:12:12.040> there 00:12:12.269 --> 00:12:12.279 align:start position:0% um and Discovery protocols like there 00:12:12.279 --> 00:12:14.629 align:start position:0% um and Discovery protocols like there could<00:12:12.440> be<00:12:12.600> a<00:12:12.839> different<00:12:13.279> way<00:12:13.480> of<00:12:13.959> how<00:12:14.120> we<00:12:14.240> can 00:12:14.629 --> 00:12:14.639 align:start position:0% could be a different way of how we can 00:12:14.639 --> 00:12:16.790 align:start position:0% could be a different way of how we can discover<00:12:14.920> so<00:12:15.440> we<00:12:15.560> do<00:12:15.760> some<00:12:15.920> tradeos<00:12:16.480> here<00:12:16.680> as 00:12:16.790 --> 00:12:16.800 align:start position:0% discover so we do some tradeos here as 00:12:16.800 --> 00:12:19.590 align:start position:0% discover so we do some tradeos here as well<00:12:17.279> some<00:12:17.680> can<00:12:17.839> be<00:12:17.959> slower<00:12:18.639> some<00:12:18.880> can<00:12:19.040> be 00:12:19.590 --> 00:12:19.600 align:start position:0% well some can be slower some can be 00:12:19.600 --> 00:12:23.230 align:start position:0% well some can be slower some can be faster<00:12:20.600> uh<00:12:20.839> and<00:12:21.399> uh<00:12:21.959> what<00:12:22.160> waku<00:12:22.480> does<00:12:22.720> so<00:12:22.959> here 00:12:23.230 --> 00:12:23.240 align:start position:0% faster uh and uh what waku does so here 00:12:23.240 --> 00:12:25.310 align:start position:0% faster uh and uh what waku does so here I<00:12:23.480> going<00:12:23.600> to<00:12:23.760> pass<00:12:23.920> it<00:12:24.120> down<00:12:24.279> to 00:12:25.310 --> 00:12:25.320 align:start position:0% I going to pass it down to 00:12:25.320 --> 00:12:30.990 align:start position:0% I going to pass it down to Ian<00:12:26.320> and<00:12:26.480> he<00:12:26.639> will<00:12:26.880> tell<00:12:27.079> you 00:12:30.990 --> 00:12:31.000 align:start position:0% 00:12:31.000 --> 00:12:31.829 align:start position:0% thank 00:12:31.829 --> 00:12:31.839 align:start position:0% thank 00:12:31.839 --> 00:12:37.030 align:start position:0% thank you<00:12:32.839> thanks<00:12:33.839> hello<00:12:34.120> everyone<00:12:35.199> um<00:12:36.199> okay<00:12:36.600> and<00:12:36.880> in 00:12:37.030 --> 00:12:37.040 align:start position:0% you thanks hello everyone um okay and in 00:12:37.040 --> 00:12:39.750 align:start position:0% you thanks hello everyone um okay and in this<00:12:37.240> part<00:12:37.440> of<00:12:37.639> the<00:12:37.920> talk<00:12:38.279> we<00:12:38.399> are<00:12:38.519> going<00:12:38.720> to<00:12:39.079> to 00:12:39.750 --> 00:12:39.760 align:start position:0% this part of the talk we are going to to 00:12:39.760 --> 00:12:41.949 align:start position:0% this part of the talk we are going to to overview<00:12:40.399> the<00:12:40.800> the<00:12:40.959> actual<00:12:41.279> implementation 00:12:41.949 --> 00:12:41.959 align:start position:0% overview the the actual implementation 00:12:41.959 --> 00:12:44.870 align:start position:0% overview the the actual implementation of<00:12:42.199> the<00:12:43.040> the<00:12:43.240> waku<00:12:43.600> protocols<00:12:44.399> as<00:12:44.680> my 00:12:44.870 --> 00:12:44.880 align:start position:0% of the the waku protocols as my 00:12:44.880 --> 00:12:48.990 align:start position:0% of the the waku protocols as my colleague<00:12:45.639> mentioned<00:12:46.639> is<00:12:47.399> um<00:12:48.399> um<00:12:48.680> an 00:12:48.990 --> 00:12:49.000 align:start position:0% colleague mentioned is um um an 00:12:49.000 --> 00:12:52.870 align:start position:0% colleague mentioned is um um an opinionated<00:12:50.000> implementation<00:12:50.639> of<00:12:51.360> the<00:12:52.360> uh<00:12:52.560> of 00:12:52.870 --> 00:12:52.880 align:start position:0% opinionated implementation of the uh of 00:12:52.880 --> 00:12:57.670 align:start position:0% opinionated implementation of the uh of our<00:12:53.440> view<00:12:54.120> or<00:12:54.440> how<00:12:55.000> we<00:12:55.760> consider<00:12:56.360> is<00:12:56.959> um<00:12:57.320> good 00:12:57.670 --> 00:12:57.680 align:start position:0% our view or how we consider is um good 00:12:57.680 --> 00:13:00.350 align:start position:0% our view or how we consider is um good to<00:12:57.920> to<00:12:58.040> solve<00:12:58.519> the<00:12:58.959> the<00:12:59.240> well-known<00:12:59.680> problems 00:13:00.350 --> 00:13:00.360 align:start position:0% to to solve the the well-known problems 00:13:00.360 --> 00:13:03.430 align:start position:0% to to solve the the well-known problems uh<00:13:00.480> such<00:13:00.680> as<00:13:00.880> the<00:13:01.440> discovery<00:13:02.440> the<00:13:02.920> the<00:13:03.079> problem 00:13:03.430 --> 00:13:03.440 align:start position:0% uh such as the discovery the the problem 00:13:03.440 --> 00:13:08.710 align:start position:0% uh such as the discovery the the problem to<00:13:04.279> of<00:13:05.040> a<00:13:05.199> nut<00:13:06.000> um<00:13:06.639> or<00:13:06.839> a<00:13:07.320> firewall<00:13:08.320> the<00:13:08.480> problem 00:13:08.710 --> 00:13:08.720 align:start position:0% to of a nut um or a firewall the problem 00:13:08.720 --> 00:13:12.310 align:start position:0% to of a nut um or a firewall the problem of<00:13:08.880> routing<00:13:09.880> uh<00:13:10.040> this<00:13:10.399> is<00:13:10.720> covered<00:13:11.279> by<00:13:11.680> all<00:13:12.079> of 00:13:12.310 --> 00:13:12.320 align:start position:0% of routing uh this is covered by all of 00:13:12.320 --> 00:13:15.150 align:start position:0% of routing uh this is covered by all of the<00:13:12.600> the<00:13:12.720> protocols<00:13:13.199> that<00:13:13.399> are<00:13:13.720> shown<00:13:14.720> in<00:13:14.920> this 00:13:15.150 --> 00:13:15.160 align:start position:0% the the protocols that are shown in this 00:13:15.160 --> 00:13:18.389 align:start position:0% the the protocols that are shown in this list<00:13:15.720> and<00:13:16.519> aside<00:13:16.800> from<00:13:17.040> that<00:13:17.600> uh<00:13:17.800> we 00:13:18.389 --> 00:13:18.399 align:start position:0% list and aside from that uh we 00:13:18.399 --> 00:13:22.509 align:start position:0% list and aside from that uh we introduced<00:13:19.040> a<00:13:19.240> new<00:13:20.160> um<00:13:20.519> new<00:13:20.720> one<00:13:21.079> which<00:13:21.240> is<00:13:22.079> the 00:13:22.509 --> 00:13:22.519 align:start position:0% introduced a new um new one which is the 00:13:22.519 --> 00:13:25.910 align:start position:0% introduced a new um new one which is the aren<00:13:23.519> uh<00:13:23.639> red<00:13:23.920> limiting<00:13:24.560> one<00:13:25.480> and<00:13:25.639> we<00:13:25.720> are 00:13:25.910 --> 00:13:25.920 align:start position:0% aren uh red limiting one and we are 00:13:25.920 --> 00:13:28.750 align:start position:0% aren uh red limiting one and we are going<00:13:26.240> we<00:13:26.360> are<00:13:26.519> going<00:13:26.680> to<00:13:27.000> to<00:13:27.160> cover<00:13:28.160> in<00:13:28.320> a<00:13:28.480> few 00:13:28.750 --> 00:13:28.760 align:start position:0% going we are going to to cover in a few 00:13:28.760 --> 00:13:31.110 align:start position:0% going we are going to to cover in a few seconds 00:13:31.110 --> 00:13:31.120 align:start position:0% seconds 00:13:31.120 --> 00:13:34.230 align:start position:0% seconds okay<00:13:31.959> uh<00:13:32.120> regarding<00:13:32.959> Discovery<00:13:33.639> uh<00:13:33.760> we<00:13:33.959> have 00:13:34.230 --> 00:13:34.240 align:start position:0% okay uh regarding Discovery uh we have 00:13:34.240 --> 00:13:37.389 align:start position:0% okay uh regarding Discovery uh we have three<00:13:34.519> main<00:13:35.120> uh<00:13:35.440> Discovery<00:13:35.920> protocols<00:13:36.680> one<00:13:36.880> is 00:13:37.389 --> 00:13:37.399 align:start position:0% three main uh Discovery protocols one is 00:13:37.399 --> 00:13:40.430 align:start position:0% three main uh Discovery protocols one is uh<00:13:37.560> perer<00:13:38.079> exchange<00:13:39.079> uh<00:13:39.440> this<00:13:39.560> is<00:13:39.959> uh<00:13:40.120> pretty 00:13:40.430 --> 00:13:40.440 align:start position:0% uh perer exchange uh this is uh pretty 00:13:40.440 --> 00:13:45.110 align:start position:0% uh perer exchange uh this is uh pretty centralized<00:13:41.079> and<00:13:41.320> is<00:13:41.959> not<00:13:42.480> ideal<00:13:43.480> but<00:13:43.680> is<00:13:44.320> um 00:13:45.110 --> 00:13:45.120 align:start position:0% centralized and is not ideal but is um 00:13:45.120 --> 00:13:47.910 align:start position:0% centralized and is not ideal but is um is<00:13:45.240> useful<00:13:45.680> in<00:13:45.839> in<00:13:45.959> certain<00:13:46.920> conditions<00:13:47.680> and 00:13:47.910 --> 00:13:47.920 align:start position:0% is useful in in certain conditions and 00:13:47.920 --> 00:13:50.629 align:start position:0% is useful in in certain conditions and what<00:13:48.120> what<00:13:48.240> it<00:13:48.600> does<00:13:49.600> sorry<00:13:50.320> what<00:13:50.440> I'm 00:13:50.629 --> 00:13:50.639 align:start position:0% what what it does sorry what I'm 00:13:50.639 --> 00:13:53.310 align:start position:0% what what it does sorry what I'm explaining<00:13:51.000> is<00:13:51.120> not<00:13:51.560> shown<00:13:51.920> in<00:13:52.120> in<00:13:52.240> the<00:13:52.360> screen 00:13:53.310 --> 00:13:53.320 align:start position:0% explaining is not shown in in the screen 00:13:53.320 --> 00:13:55.710 align:start position:0% explaining is not shown in in the screen but<00:13:53.720> uh<00:13:53.880> what<00:13:54.160> peer<00:13:54.480> exchange<00:13:55.000> protocol<00:13:55.440> does 00:13:55.710 --> 00:13:55.720 align:start position:0% but uh what peer exchange protocol does 00:13:55.720 --> 00:13:59.629 align:start position:0% but uh what peer exchange protocol does is<00:13:56.240> it<00:13:56.399> asks<00:13:56.880> to<00:13:57.120> other<00:13:57.560> peer<00:13:58.360> to<00:13:58.920> uh<00:13:59.160> share<00:13:59.480> the 00:13:59.629 --> 00:13:59.639 align:start position:0% is it asks to other peer to uh share the 00:13:59.639 --> 00:14:03.350 align:start position:0% is it asks to other peer to uh share the the<00:13:59.800> peers<00:14:00.199> that<00:14:00.759> it<00:14:01.279> knows<00:14:02.279> and<00:14:02.600> it's<00:14:02.880> just<00:14:03.120> a 00:14:03.350 --> 00:14:03.360 align:start position:0% the peers that it knows and it's just a 00:14:03.360 --> 00:14:05.829 align:start position:0% the peers that it knows and it's just a request<00:14:03.720> response<00:14:04.519> uh<00:14:04.639> protocol<00:14:05.120> where<00:14:05.519> the 00:14:05.829 --> 00:14:05.839 align:start position:0% request response uh protocol where the 00:14:05.839 --> 00:14:08.749 align:start position:0% request response uh protocol where the the<00:14:05.959> other<00:14:06.240> peer<00:14:07.399> response<00:14:08.399> about<00:14:08.680> the 00:14:08.749 --> 00:14:08.759 align:start position:0% the other peer response about the 00:14:08.759 --> 00:14:12.389 align:start position:0% the other peer response about the information<00:14:09.240> of<00:14:09.519> each<00:14:10.079> peers<00:14:11.079> and<00:14:12.079> then<00:14:12.240> we 00:14:12.389 --> 00:14:12.399 align:start position:0% information of each peers and then we 00:14:12.399 --> 00:14:15.509 align:start position:0% information of each peers and then we have<00:14:12.560> the<00:14:12.720> DNS<00:14:13.440> Discovery<00:14:14.120> uh<00:14:14.279> which<00:14:14.440> is<00:14:14.959> um 00:14:15.509 --> 00:14:15.519 align:start position:0% have the DNS Discovery uh which is um 00:14:15.519 --> 00:14:18.069 align:start position:0% have the DNS Discovery uh which is um very<00:14:15.880> interesting<00:14:16.320> protocol<00:14:16.920> that<00:14:17.800> uh<00:14:17.920> is 00:14:18.069 --> 00:14:18.079 align:start position:0% very interesting protocol that uh is 00:14:18.079 --> 00:14:21.550 align:start position:0% very interesting protocol that uh is powered<00:14:18.639> by<00:14:19.360> DNS<00:14:20.360> and<00:14:20.519> then<00:14:20.839> we<00:14:21.000> have<00:14:21.240> the 00:14:21.550 --> 00:14:21.560 align:start position:0% powered by DNS and then we have the 00:14:21.560 --> 00:14:25.350 align:start position:0% powered by DNS and then we have the Discovery<00:14:21.880> V5<00:14:22.519> which<00:14:23.079> we<00:14:23.440> consider<00:14:24.440> uh<00:14:24.560> to<00:14:24.720> be 00:14:25.350 --> 00:14:25.360 align:start position:0% Discovery V5 which we consider uh to be 00:14:25.360 --> 00:14:29.670 align:start position:0% Discovery V5 which we consider uh to be more<00:14:26.240> uh<00:14:26.399> decentralized<00:14:27.240> and<00:14:27.600> more<00:14:28.600> uh<00:14:28.720> convin 00:14:29.670 --> 00:14:29.680 align:start position:0% more uh decentralized and more uh convin 00:14:29.680 --> 00:14:36.150 align:start position:0% more uh decentralized and more uh convin for<00:14:30.000> the<00:14:30.199> web<00:14:30.440> 3<00:14:31.360> um<00:14:31.959> scenario<00:14:33.079> and<00:14:34.079> it's<00:14:35.160> um 00:14:36.150 --> 00:14:36.160 align:start position:0% for the web 3 um scenario and it's um 00:14:36.160 --> 00:14:38.430 align:start position:0% for the web 3 um scenario and it's um it's<00:14:36.480> based<00:14:37.240> its<00:14:37.399> implementation<00:14:37.959> is<00:14:38.120> based 00:14:38.430 --> 00:14:38.440 align:start position:0% it's based its implementation is based 00:14:38.440 --> 00:14:42.030 align:start position:0% it's based its implementation is based on<00:14:39.120> cadmia<00:14:40.120> and<00:14:40.440> well<00:14:40.720> as<00:14:40.800> you<00:14:40.920> know<00:14:41.120> it's<00:14:41.600> uh 00:14:42.030 --> 00:14:42.040 align:start position:0% on cadmia and well as you know it's uh 00:14:42.040 --> 00:14:45.749 align:start position:0% on cadmia and well as you know it's uh DHT<00:14:42.880> and<00:14:43.839> uh<00:14:44.000> what<00:14:44.120> it<00:14:44.279> does<00:14:44.680> it<00:14:44.839> retrieves<00:14:45.519> a 00:14:45.749 --> 00:14:45.759 align:start position:0% DHT and uh what it does it retrieves a 00:14:45.759 --> 00:14:51.710 align:start position:0% DHT and uh what it does it retrieves a random<00:14:46.199> set<00:14:46.720> of<00:14:47.480> um<00:14:48.440> en<00:14:49.279> enrs<00:14:50.279> and<00:14:51.120> um<00:14:51.519> yeah 00:14:51.710 --> 00:14:51.720 align:start position:0% random set of um en enrs and um yeah 00:14:51.720 --> 00:14:55.870 align:start position:0% random set of um en enrs and um yeah this<00:14:51.880> is<00:14:52.480> um<00:14:52.720> very<00:14:53.320> intensively<00:14:53.959> used<00:14:54.399> in<00:14:54.720> in 00:14:55.870 --> 00:14:55.880 align:start position:0% this is um very intensively used in in 00:14:55.880 --> 00:15:02.269 align:start position:0% this is um very intensively used in in woku<00:14:56.880> okay<00:14:57.639> then<00:14:58.160> regarding 00:15:02.269 --> 00:15:02.279 align:start position:0% 00:15:02.279 --> 00:15:05.189 align:start position:0% um<00:15:03.279> uh<00:15:03.800> another<00:15:04.160> family<00:15:04.440> of<00:15:04.600> protocols<00:15:05.040> that 00:15:05.189 --> 00:15:05.199 align:start position:0% um uh another family of protocols that 00:15:05.199 --> 00:15:07.430 align:start position:0% um uh another family of protocols that we<00:15:05.320> have<00:15:05.480> in<00:15:05.639> waku<00:15:06.000> is<00:15:06.079> the<00:15:06.279> request<00:15:06.639> response 00:15:07.430 --> 00:15:07.440 align:start position:0% we have in waku is the request response 00:15:07.440 --> 00:15:11.430 align:start position:0% we have in waku is the request response protocols<00:15:08.440> uh<00:15:08.639> which<00:15:09.040> are<00:15:09.959> um<00:15:10.880> you<00:15:11.000> will<00:15:11.160> see 00:15:11.430 --> 00:15:11.440 align:start position:0% protocols uh which are um you will see 00:15:11.440 --> 00:15:13.829 align:start position:0% protocols uh which are um you will see in<00:15:11.720> in<00:15:11.839> this<00:15:12.040> talk<00:15:12.360> that<00:15:12.519> we<00:15:12.680> have<00:15:12.880> two<00:15:13.120> main 00:15:13.829 --> 00:15:13.839 align:start position:0% in in this talk that we have two main 00:15:13.839 --> 00:15:16.790 align:start position:0% in in this talk that we have two main families<00:15:14.320> of<00:15:14.720> of<00:15:15.000> notes<00:15:15.759> we<00:15:15.959> have<00:15:16.519> what<00:15:16.639> we 00:15:16.790 --> 00:15:16.800 align:start position:0% families of of notes we have what we 00:15:16.800 --> 00:15:19.990 align:start position:0% families of of notes we have what we call<00:15:17.240> a<00:15:17.480> full<00:15:17.839> node<00:15:18.639> um<00:15:19.160> which<00:15:19.320> is<00:15:19.519> basically<00:15:19.880> a 00:15:19.990 --> 00:15:20.000 align:start position:0% call a full node um which is basically a 00:15:20.000 --> 00:15:24.150 align:start position:0% call a full node um which is basically a note<00:15:20.360> that<00:15:21.079> um<00:15:22.079> is<00:15:22.320> part<00:15:22.600> of<00:15:22.800> the<00:15:23.759> of<00:15:23.920> the 00:15:24.150 --> 00:15:24.160 align:start position:0% note that um is part of the of the 00:15:24.160 --> 00:15:26.990 align:start position:0% note that um is part of the of the overlay<00:15:24.639> of<00:15:24.800> the<00:15:24.920> of<00:15:25.040> the<00:15:25.160> network<00:15:25.639> and<00:15:26.040> and 00:15:26.990 --> 00:15:27.000 align:start position:0% overlay of the of the network and and 00:15:27.000 --> 00:15:30.189 align:start position:0% overlay of the of the network and and produces<00:15:27.519> the<00:15:28.319> uh<00:15:28.440> routing<00:15:28.839> of<00:15:29.120> the<00:15:29.399> data<00:15:30.000> and 00:15:30.189 --> 00:15:30.199 align:start position:0% produces the uh routing of the data and 00:15:30.199 --> 00:15:33.269 align:start position:0% produces the uh routing of the data and then<00:15:30.360> we<00:15:30.519> have<00:15:30.839> the<00:15:31.079> The<00:15:31.199> Edge<00:15:31.720> nodes<00:15:32.720> and<00:15:32.959> for 00:15:33.269 --> 00:15:33.279 align:start position:0% then we have the The Edge nodes and for 00:15:33.279 --> 00:15:36.350 align:start position:0% then we have the The Edge nodes and for these<00:15:33.480> Edge<00:15:33.800> nodes<00:15:34.680> such<00:15:34.880> as<00:15:35.600> um<00:15:35.839> a<00:15:36.040> mobile 00:15:36.350 --> 00:15:36.360 align:start position:0% these Edge nodes such as um a mobile 00:15:36.360 --> 00:15:41.470 align:start position:0% these Edge nodes such as um a mobile phone<00:15:36.800> or<00:15:37.759> a<00:15:38.319> browser<00:15:39.319> is<00:15:39.959> um<00:15:40.920> it<00:15:41.079> cannot 00:15:41.470 --> 00:15:41.480 align:start position:0% phone or a browser is um it cannot 00:15:41.480 --> 00:15:43.749 align:start position:0% phone or a browser is um it cannot participate<00:15:41.959> in<00:15:42.079> the<00:15:42.240> routing<00:15:43.079> uh<00:15:43.480> um 00:15:43.749 --> 00:15:43.759 align:start position:0% participate in the routing uh um 00:15:43.759 --> 00:15:48.430 align:start position:0% participate in the routing uh um protocol<00:15:44.279> because<00:15:45.040> is<00:15:45.720> um<00:15:46.079> data<00:15:47.440> consuming 00:15:48.430 --> 00:15:48.440 align:start position:0% protocol because is um data consuming 00:15:48.440 --> 00:15:51.790 align:start position:0% protocol because is um data consuming and<00:15:48.639> for<00:15:48.839> that<00:15:49.000> reason<00:15:49.399> we<00:15:49.880> we<00:15:50.199> created<00:15:51.120> this 00:15:51.790 --> 00:15:51.800 align:start position:0% and for that reason we we created this 00:15:51.800 --> 00:15:56.069 align:start position:0% and for that reason we we created this uh<00:15:52.079> request<00:15:52.959> response<00:15:53.959> uh<00:15:54.079> protocols<00:15:54.839> for<00:15:55.839> for 00:15:56.069 --> 00:15:56.079 align:start position:0% uh request response uh protocols for for 00:15:56.079 --> 00:15:57.829 align:start position:0% uh request response uh protocols for for helping<00:15:56.519> in<00:15:56.639> order<00:15:56.880> to<00:15:57.040> help<00:15:57.279> these<00:15:57.519> Edge 00:15:57.829 --> 00:15:57.839 align:start position:0% helping in order to help these Edge 00:15:57.839 --> 00:16:02.150 align:start position:0% helping in order to help these Edge nodes<00:15:58.680> in<00:15:59.120> in<00:15:59.360> different<00:16:00.240> ways<00:16:00.839> for<00:16:01.120> example 00:16:02.150 --> 00:16:02.160 align:start position:0% nodes in in different ways for example 00:16:02.160 --> 00:16:04.470 align:start position:0% nodes in in different ways for example in<00:16:03.160> regarding<00:16:03.560> sorry<00:16:03.800> for<00:16:03.959> the<00:16:04.079> typo 00:16:04.470 --> 00:16:04.480 align:start position:0% in regarding sorry for the typo 00:16:04.480 --> 00:16:07.269 align:start position:0% in regarding sorry for the typo regarding<00:16:04.880> the<00:16:05.040> store<00:16:05.800> note<00:16:06.800> it's<00:16:07.040> main 00:16:07.269 --> 00:16:07.279 align:start position:0% regarding the store note it's main 00:16:07.279 --> 00:16:11.590 align:start position:0% regarding the store note it's main purpose<00:16:07.720> is<00:16:08.240> to<00:16:08.959> um<00:16:09.240> allow<00:16:10.000> um<00:16:10.319> nodes<00:16:11.199> uh<00:16:11.360> to 00:16:11.590 --> 00:16:11.600 align:start position:0% purpose is to um allow um nodes uh to 00:16:11.600 --> 00:16:13.829 align:start position:0% purpose is to um allow um nodes uh to come<00:16:12.000> when<00:16:12.440> a<00:16:12.600> node<00:16:12.880> come<00:16:13.079> back<00:16:13.360> to<00:16:13.680> to 00:16:13.829 --> 00:16:13.839 align:start position:0% come when a node come back to to 00:16:13.839 --> 00:16:16.550 align:start position:0% come when a node come back to to participate<00:16:14.319> in<00:16:14.440> the<00:16:14.560> network<00:16:15.399> to<00:16:15.600> get<00:16:15.839> back 00:16:16.550 --> 00:16:16.560 align:start position:0% participate in the network to get back 00:16:16.560 --> 00:16:21.110 align:start position:0% participate in the network to get back the<00:16:17.560> the<00:16:17.800> late<00:16:18.440> latest<00:16:18.839> state<00:16:19.240> of<00:16:19.600> of<00:16:19.839> the<00:16:20.279> the 00:16:21.110 --> 00:16:21.120 align:start position:0% the the late latest state of of the the 00:16:21.120 --> 00:16:24.509 align:start position:0% the the late latest state of of the the messages<00:16:22.120> then<00:16:22.279> we<00:16:22.440> have<00:16:22.639> the<00:16:23.040> sink<00:16:24.040> and<00:16:24.279> the 00:16:24.509 --> 00:16:24.519 align:start position:0% messages then we have the sink and the 00:16:24.519 --> 00:16:27.030 align:start position:0% messages then we have the sink and the main<00:16:24.759> purpose<00:16:25.040> of<00:16:25.199> this<00:16:25.399> protocol<00:16:25.839> is<00:16:26.000> to<00:16:26.800> make 00:16:27.030 --> 00:16:27.040 align:start position:0% main purpose of this protocol is to make 00:16:27.040 --> 00:16:30.350 align:start position:0% main purpose of this protocol is to make sure<00:16:27.480> that<00:16:28.040> all<00:16:28.319> the<00:16:28.920> St<00:16:29.120> nodes<00:16:29.880> have<00:16:30.199> the 00:16:30.350 --> 00:16:30.360 align:start position:0% sure that all the St nodes have the 00:16:30.360 --> 00:16:34.110 align:start position:0% sure that all the St nodes have the latest<00:16:30.959> State<00:16:31.959> and<00:16:32.120> the<00:16:32.240> same<00:16:32.560> state<00:16:33.040> of<00:16:33.399> of 00:16:34.110 --> 00:16:34.120 align:start position:0% latest State and the same state of of 00:16:34.120 --> 00:16:37.949 align:start position:0% latest State and the same state of of messages<00:16:35.120> uh<00:16:35.279> then<00:16:35.440> we<00:16:35.600> have<00:16:36.079> light<00:16:36.720> push<00:16:37.720> the 00:16:37.949 --> 00:16:37.959 align:start position:0% messages uh then we have light push the 00:16:37.959 --> 00:16:40.590 align:start position:0% messages uh then we have light push the purpose<00:16:38.279> of<00:16:38.480> this<00:16:38.680> protocol<00:16:39.120> is<00:16:39.440> for<00:16:40.000> Edge 00:16:40.590 --> 00:16:40.600 align:start position:0% purpose of this protocol is for Edge 00:16:40.600 --> 00:16:43.150 align:start position:0% purpose of this protocol is for Edge clients<00:16:41.199> to<00:16:41.800> to<00:16:41.920> be<00:16:42.079> able<00:16:42.279> to<00:16:42.399> participate<00:16:43.079> in 00:16:43.150 --> 00:16:43.160 align:start position:0% clients to to be able to participate in 00:16:43.160 --> 00:16:45.470 align:start position:0% clients to to be able to participate in the<00:16:43.319> network<00:16:44.000> to<00:16:44.199> publish<00:16:44.560> messages<00:16:45.240> and 00:16:45.470 --> 00:16:45.480 align:start position:0% the network to publish messages and 00:16:45.480 --> 00:16:48.790 align:start position:0% the network to publish messages and filter<00:16:46.399> in<00:16:46.600> the<00:16:46.759> other<00:16:47.000> way 00:16:48.790 --> 00:16:48.800 align:start position:0% filter in the other way 00:16:48.800 --> 00:16:53.030 align:start position:0% filter in the other way around<00:16:49.800> okay<00:16:50.079> if<00:16:50.240> we<00:16:50.480> go<00:16:50.959> further 00:16:53.030 --> 00:16:53.040 align:start position:0% around okay if we go further 00:16:53.040 --> 00:16:56.350 align:start position:0% around okay if we go further to<00:16:54.040> the<00:16:54.240> routing 00:16:56.350 --> 00:16:56.360 align:start position:0% to the routing 00:16:56.360 --> 00:17:02.030 align:start position:0% to the routing protocol<00:16:57.360> sorry 00:17:02.030 --> 00:17:02.040 align:start position:0% 00:17:02.040 --> 00:17:05.110 align:start position:0% anyway<00:17:03.040> okay<00:17:03.839> uh<00:17:04.160> okay<00:17:04.480> regarding<00:17:04.959> the 00:17:05.110 --> 00:17:05.120 align:start position:0% anyway okay uh okay regarding the 00:17:05.120 --> 00:17:08.590 align:start position:0% anyway okay uh okay regarding the routing<00:17:05.439> protocol<00:17:06.079> is<00:17:06.679> um<00:17:07.679> we<00:17:07.880> we<00:17:08.039> call<00:17:08.240> it 00:17:08.590 --> 00:17:08.600 align:start position:0% routing protocol is um we we call it 00:17:08.600 --> 00:17:11.990 align:start position:0% routing protocol is um we we call it relay<00:17:09.600> and<00:17:09.760> it's<00:17:10.280> a<00:17:10.559> kind<00:17:10.720> of<00:17:11.000> opinionated 00:17:11.990 --> 00:17:12.000 align:start position:0% relay and it's a kind of opinionated 00:17:12.000 --> 00:17:16.110 align:start position:0% relay and it's a kind of opinionated version<00:17:12.400> of<00:17:12.760> of<00:17:12.959> Gossip<00:17:13.439> sa<00:17:14.439> uh<00:17:14.559> which<00:17:14.679> is<00:17:15.160> uh 00:17:16.110 --> 00:17:16.120 align:start position:0% version of of Gossip sa uh which is uh 00:17:16.120 --> 00:17:18.390 align:start position:0% version of of Gossip sa uh which is uh uh<00:17:16.520> great<00:17:16.839> and<00:17:16.959> it's<00:17:17.319> very<00:17:17.720> interesting<00:17:18.240> and 00:17:18.390 --> 00:17:18.400 align:start position:0% uh great and it's very interesting and 00:17:18.400 --> 00:17:21.110 align:start position:0% uh great and it's very interesting and we're<00:17:18.600> going<00:17:18.760> to<00:17:18.959> to<00:17:19.120> cover<00:17:19.839> very<00:17:20.039> briefly<00:17:20.880> how 00:17:21.110 --> 00:17:21.120 align:start position:0% we're going to to cover very briefly how 00:17:21.120 --> 00:17:25.590 align:start position:0% we're going to to cover very briefly how gossip<00:17:22.039> Works<00:17:22.559> in<00:17:22.880> in<00:17:23.039> this<00:17:23.520> talk 00:17:25.590 --> 00:17:25.600 align:start position:0% gossip Works in in this talk 00:17:25.600 --> 00:17:31.789 align:start position:0% gossip Works in in this talk um<00:17:26.959> okay<00:17:27.959> uh<00:17:28.679> okay<00:17:28.960> okay<00:17:29.799> this<00:17:29.919> is<00:17:30.320> a<00:17:31.240> uh<00:17:31.440> very 00:17:31.789 --> 00:17:31.799 align:start position:0% um okay uh okay okay this is a uh very 00:17:31.799 --> 00:17:34.830 align:start position:0% um okay uh okay okay this is a uh very simplified<00:17:32.600> schema<00:17:33.600> of 00:17:34.830 --> 00:17:34.840 align:start position:0% simplified schema of 00:17:34.840 --> 00:17:39.310 align:start position:0% simplified schema of um<00:17:35.840> uh<00:17:36.200> prity<00:17:36.960> interconnected<00:17:38.000> Network<00:17:39.000> and 00:17:39.310 --> 00:17:39.320 align:start position:0% um uh prity interconnected Network and 00:17:39.320 --> 00:17:42.990 align:start position:0% um uh prity interconnected Network and the<00:17:39.480> dots<00:17:40.120> uh<00:17:40.280> just<00:17:40.760> represent<00:17:41.280> nodes<00:17:42.280> and<00:17:42.880> as 00:17:42.990 --> 00:17:43.000 align:start position:0% the dots uh just represent nodes and as 00:17:43.000 --> 00:17:45.830 align:start position:0% the dots uh just represent nodes and as you<00:17:43.120> can<00:17:43.280> see<00:17:44.280> all<00:17:44.440> of<00:17:44.559> the<00:17:44.679> nodes<00:17:45.280> they<00:17:45.400> are 00:17:45.830 --> 00:17:45.840 align:start position:0% you can see all of the nodes they are 00:17:45.840 --> 00:17:48.350 align:start position:0% you can see all of the nodes they are continuously<00:17:46.840> exchanging<00:17:47.760> uh<00:17:47.880> control 00:17:48.350 --> 00:17:48.360 align:start position:0% continuously exchanging uh control 00:17:48.360 --> 00:17:52.150 align:start position:0% continuously exchanging uh control messages<00:17:49.360> like<00:17:49.520> for<00:17:49.919> example<00:17:50.919> uh<00:17:51.919> the<00:17:52.080> the 00:17:52.150 --> 00:17:52.160 align:start position:0% messages like for example uh the the 00:17:52.160 --> 00:17:55.549 align:start position:0% messages like for example uh the the messages<00:17:52.600> that<00:17:53.400> I<00:17:53.600> saw<00:17:54.000> the<00:17:54.160> messages<00:17:54.799> I'm<00:17:55.159> I'm 00:17:55.549 --> 00:17:55.559 align:start position:0% messages that I saw the messages I'm I'm 00:17:55.559 --> 00:17:59.430 align:start position:0% messages that I saw the messages I'm I'm interested<00:17:56.039> in<00:17:56.919> and<00:17:57.880> I<00:17:58.360> the 00:17:59.430 --> 00:17:59.440 align:start position:0% interested in and I the 00:17:59.440 --> 00:18:02.190 align:start position:0% interested in and I the the<00:17:59.679> control<00:18:00.000> messages<00:18:00.799> um<00:18:01.159> names<00:18:01.440> are<00:18:01.880> I<00:18:02.080> I 00:18:02.190 --> 00:18:02.200 align:start position:0% the control messages um names are I I 00:18:02.200 --> 00:18:06.029 align:start position:0% the control messages um names are I I want<00:18:02.880> or<00:18:03.880> I<00:18:04.679> I<00:18:04.799> need 00:18:06.029 --> 00:18:06.039 align:start position:0% want or I I need 00:18:06.039 --> 00:18:10.430 align:start position:0% want or I I need no<00:18:07.039> and<00:18:07.240> and<00:18:07.400> then<00:18:07.880> we<00:18:08.000> have<00:18:08.280> the<00:18:09.039> the<00:18:09.200> waku 00:18:10.430 --> 00:18:10.440 align:start position:0% no and and then we have the the waku 00:18:10.440 --> 00:18:13.789 align:start position:0% no and and then we have the the waku messages<00:18:11.440> that<00:18:12.200> these<00:18:12.600> are<00:18:13.000> the<00:18:13.159> the<00:18:13.320> actual 00:18:13.789 --> 00:18:13.799 align:start position:0% messages that these are the the actual 00:18:13.799 --> 00:18:17.990 align:start position:0% messages that these are the the actual messages<00:18:14.600> that<00:18:14.960> transport<00:18:15.880> uh<00:18:16.080> data<00:18:16.799> in<00:18:17.799> in 00:18:17.990 --> 00:18:18.000 align:start position:0% messages that transport uh data in in 00:18:18.000 --> 00:18:21.789 align:start position:0% messages that transport uh data in in the<00:18:19.000> in<00:18:19.200> the<00:18:19.880> in<00:18:20.000> the<00:18:20.360> network<00:18:21.360> something 00:18:21.789 --> 00:18:21.799 align:start position:0% the in the in the network something 00:18:21.799 --> 00:18:25.110 align:start position:0% the in the in the network something important<00:18:22.159> to<00:18:22.320> to<00:18:22.440> bear<00:18:22.640> in<00:18:22.720> mind<00:18:23.039> is<00:18:23.280> that<00:18:24.280> um 00:18:25.110 --> 00:18:25.120 align:start position:0% important to to bear in mind is that um 00:18:25.120 --> 00:18:27.590 align:start position:0% important to to bear in mind is that um we<00:18:25.280> can<00:18:25.600> have<00:18:25.799> for<00:18:25.960> example<00:18:26.720> 100<00:18:27.039> connections 00:18:27.590 --> 00:18:27.600 align:start position:0% we can have for example 100 connections 00:18:27.600 --> 00:18:32.149 align:start position:0% we can have for example 100 connections to<00:18:27.880> a<00:18:28.240> uh<00:18:28.360> to<00:18:29.120> 100<00:18:29.440> notes<00:18:30.440> but<00:18:30.840> one<00:18:31.080> single<00:18:31.400> note 00:18:32.149 --> 00:18:32.159 align:start position:0% to a uh to 100 notes but one single note 00:18:32.159 --> 00:18:38.510 align:start position:0% to a uh to 100 notes but one single note will<00:18:33.000> and<00:18:33.760> spread<00:18:34.919> um<00:18:36.240> data<00:18:37.240> Wu<00:18:37.559> messages<00:18:38.080> to 00:18:38.510 --> 00:18:38.520 align:start position:0% will and spread um data Wu messages to 00:18:38.520 --> 00:18:44.070 align:start position:0% will and spread um data Wu messages to up<00:18:38.720> to<00:18:39.120> six<00:18:39.679> eight<00:18:40.640> notes<00:18:42.080> maximum<00:18:43.080> and<00:18:43.840> every 00:18:44.070 --> 00:18:44.080 align:start position:0% up to six eight notes maximum and every 00:18:44.080 --> 00:18:46.950 align:start position:0% up to six eight notes maximum and every note<00:18:44.440> will<00:18:44.760> pick<00:18:44.960> up<00:18:45.799> the<00:18:46.000> best<00:18:46.400> from<00:18:46.679> each 00:18:46.950 --> 00:18:46.960 align:start position:0% note will pick up the best from each 00:18:46.960 --> 00:18:49.870 align:start position:0% note will pick up the best from each neighbors<00:18:47.520> will<00:18:47.760> pick<00:18:47.960> up<00:18:48.440> the<00:18:48.640> best<00:18:49.200> notes 00:18:49.870 --> 00:18:49.880 align:start position:0% neighbors will pick up the best notes 00:18:49.880 --> 00:18:53.070 align:start position:0% neighbors will pick up the best notes regarding<00:18:50.320> the<00:18:51.320> according<00:18:51.640> to<00:18:51.919> to<00:18:52.440> certain 00:18:53.070 --> 00:18:53.080 align:start position:0% regarding the according to to certain 00:18:53.080 --> 00:18:56.510 align:start position:0% regarding the according to to certain parameters<00:18:54.080> such<00:18:54.280> as<00:18:54.520> latency<00:18:55.520> and<00:18:55.960> number<00:18:56.280> of 00:18:56.510 --> 00:18:56.520 align:start position:0% parameters such as latency and number of 00:18:56.520 --> 00:18:59.230 align:start position:0% parameters such as latency and number of messages<00:18:57.080> per<00:18:57.280> per<00:18:57.600> second<00:18:58.600> uh<00:18:58.960> how 00:18:59.230 --> 00:18:59.240 align:start position:0% messages per per second uh how 00:18:59.240 --> 00:19:08.830 align:start position:0% messages per per second uh how responsive<00:19:00.039> an<00:19:00.600> is<00:19:01.600> and<00:19:01.799> and<00:19:01.960> so<00:19:02.520> on 00:19:08.830 --> 00:19:08.840 align:start position:0% 00:19:08.840 --> 00:19:12.310 align:start position:0% and<00:19:09.840> okay<00:19:10.159> uh<00:19:10.280> and<00:19:10.480> how<00:19:10.640> does<00:19:10.799> it<00:19:11.000> work<00:19:11.679> um 00:19:12.310 --> 00:19:12.320 align:start position:0% and okay uh and how does it work um 00:19:12.320 --> 00:19:16.270 align:start position:0% and okay uh and how does it work um every<00:19:12.559> note<00:19:13.200> has<00:19:13.760> uh<00:19:14.039> a<00:19:14.600> um<00:19:15.000> her<00:19:15.360> bit<00:19:16.080> that 00:19:16.270 --> 00:19:16.280 align:start position:0% every note has uh a um her bit that 00:19:16.280 --> 00:19:19.190 align:start position:0% every note has uh a um her bit that happens<00:19:16.720> every<00:19:17.080> second<00:19:18.080> and<00:19:18.360> on<00:19:18.600> every<00:19:18.840> second 00:19:19.190 --> 00:19:19.200 align:start position:0% happens every second and on every second 00:19:19.200 --> 00:19:23.230 align:start position:0% happens every second and on every second every<00:19:19.440> note<00:19:20.240> measures<00:19:21.240> or 00:19:23.230 --> 00:19:23.240 align:start position:0% every note measures or 00:19:23.240 --> 00:19:27.870 align:start position:0% every note measures or um<00:19:24.240> gives<00:19:24.799> um<00:19:25.200> a<00:19:25.400> certain<00:19:26.400> score<00:19:26.880> to<00:19:27.159> to<00:19:27.360> all<00:19:27.559> of 00:19:27.870 --> 00:19:27.880 align:start position:0% um gives um a certain score to to all of 00:19:27.880 --> 00:19:32.390 align:start position:0% um gives um a certain score to to all of its<00:19:28.400> uh<00:19:28.960> nebs<00:19:29.960> and<00:19:30.200> according<00:19:30.520> to<00:19:30.760> this<00:19:31.400> score 00:19:32.390 --> 00:19:32.400 align:start position:0% its uh nebs and according to this score 00:19:32.400 --> 00:19:35.710 align:start position:0% its uh nebs and according to this score if<00:19:32.559> the<00:19:32.720> score<00:19:33.159> is<00:19:33.640> too<00:19:33.840> low<00:19:34.480> then<00:19:34.760> it<00:19:34.960> ignores 00:19:35.710 --> 00:19:35.720 align:start position:0% if the score is too low then it ignores 00:19:35.720 --> 00:19:39.990 align:start position:0% if the score is too low then it ignores the<00:19:36.240> the<00:19:36.679> the<00:19:37.080> the<00:19:37.240> note<00:19:37.840> it<00:19:37.960> doesn't<00:19:38.240> mean<00:19:39.000> it 00:19:39.990 --> 00:19:40.000 align:start position:0% the the the the note it doesn't mean it 00:19:40.000 --> 00:19:42.350 align:start position:0% the the the the note it doesn't mean it completely<00:19:40.400> disconnects<00:19:41.240> to<00:19:41.360> the<00:19:41.480> note<00:19:42.159> it 00:19:42.350 --> 00:19:42.360 align:start position:0% completely disconnects to the note it 00:19:42.360 --> 00:19:47.070 align:start position:0% completely disconnects to the note it keeps<00:19:43.120> um<00:19:44.039> uh<00:19:44.480> gossiping<00:19:45.480> say<00:19:46.120> asking<00:19:46.960> what 00:19:47.070 --> 00:19:47.080 align:start position:0% keeps um uh gossiping say asking what 00:19:47.080 --> 00:19:49.110 align:start position:0% keeps um uh gossiping say asking what messages<00:19:47.480> do<00:19:47.640> you<00:19:47.840> have<00:19:48.280> what<00:19:48.600> what<00:19:48.840> what<00:19:48.960> I 00:19:49.110 --> 00:19:49.120 align:start position:0% messages do you have what what what I 00:19:49.120 --> 00:19:52.310 align:start position:0% messages do you have what what what I have<00:19:49.640> Etc<00:19:50.640> but<00:19:51.000> it<00:19:51.120> doesn't<00:19:51.679> uh<00:19:51.840> participate 00:19:52.310 --> 00:19:52.320 align:start position:0% have Etc but it doesn't uh participate 00:19:52.320 --> 00:19:56.830 align:start position:0% have Etc but it doesn't uh participate or<00:19:52.559> interact<00:19:53.400> share<00:19:53.799> sharing<00:19:54.960> um<00:19:55.960> um 00:19:56.830 --> 00:19:56.840 align:start position:0% or interact share sharing um um 00:19:56.840 --> 00:19:59.549 align:start position:0% or interact share sharing um um important<00:19:57.320> data<00:19:57.679> no 00:19:59.549 --> 00:19:59.559 align:start position:0% important data no 00:19:59.559 --> 00:20:02.590 align:start position:0% important data no it<00:19:59.799> only<00:20:00.280> establishes<00:20:00.960> a<00:20:01.120> mesh<00:20:01.640> with<00:20:02.200> um 00:20:02.590 --> 00:20:02.600 align:start position:0% it only establishes a mesh with um 00:20:02.600 --> 00:20:07.149 align:start position:0% it only establishes a mesh with um amplification<00:20:03.400> factor<00:20:04.400> of<00:20:05.520> um<00:20:06.520> of<00:20:06.840> value 00:20:07.149 --> 00:20:07.159 align:start position:0% amplification factor of um of value 00:20:07.159 --> 00:20:10.630 align:start position:0% amplification factor of um of value between<00:20:07.799> four<00:20:08.440> or<00:20:08.840> eight<00:20:09.640> this<00:20:09.760> is<00:20:09.960> how<00:20:10.240> we<00:20:10.520> we 00:20:10.630 --> 00:20:10.640 align:start position:0% between four or eight this is how we we 00:20:10.640 --> 00:20:16.630 align:start position:0% between four or eight this is how we we are<00:20:10.840> configuring<00:20:11.520> at<00:20:11.679> at<00:20:11.799> the<00:20:12.360> moment<00:20:13.360> and<00:20:14.000> and 00:20:16.630 --> 00:20:16.640 align:start position:0% 00:20:16.640 --> 00:20:20.830 align:start position:0% yeah<00:20:17.640> and<00:20:17.880> in<00:20:18.039> this<00:20:18.280> slide<00:20:19.120> um<00:20:19.480> it's<00:20:19.840> just<00:20:20.320> um<00:20:20.679> a 00:20:20.830 --> 00:20:20.840 align:start position:0% yeah and in this slide um it's just um a 00:20:20.840 --> 00:20:24.909 align:start position:0% yeah and in this slide um it's just um a simple<00:20:21.200> example<00:20:21.799> of<00:20:22.240> how<00:20:22.480> a<00:20:22.679> single<00:20:23.360> Noe<00:20:24.360> um 00:20:24.909 --> 00:20:24.919 align:start position:0% simple example of how a single Noe um 00:20:24.919 --> 00:20:26.430 align:start position:0% simple example of how a single Noe um establishes 00:20:26.430 --> 00:20:26.440 align:start position:0% establishes 00:20:26.440 --> 00:20:30.549 align:start position:0% establishes um<00:20:27.440> at<00:20:27.720> certain<00:20:28.320> point<00:20:28.799> time<00:20:29.480> uh<00:20:29.720> what<00:20:29.960> what<00:20:30.080> is 00:20:30.549 --> 00:20:30.559 align:start position:0% um at certain point time uh what what is 00:20:30.559 --> 00:20:35.070 align:start position:0% um at certain point time uh what what is the<00:20:31.559> about<00:20:32.000> his<00:20:32.440> its<00:20:32.840> nebs<00:20:33.840> uh<00:20:34.000> what<00:20:34.120> is<00:20:34.360> the 00:20:35.070 --> 00:20:35.080 align:start position:0% the about his its nebs uh what is the 00:20:35.080 --> 00:20:39.149 align:start position:0% the about his its nebs uh what is the the<00:20:35.360> P<00:20:35.919> score<00:20:36.919> and<00:20:37.200> for<00:20:37.600> for<00:20:37.760> example<00:20:38.440> if<00:20:38.679> note 00:20:39.149 --> 00:20:39.159 align:start position:0% the P score and for for example if note 00:20:39.159 --> 00:20:40.909 align:start position:0% the P score and for for example if note a<00:20:39.760> receives<00:20:40.039> a 00:20:40.909 --> 00:20:40.919 align:start position:0% a receives a 00:20:40.919 --> 00:20:45.470 align:start position:0% a receives a message<00:20:41.919> then<00:20:42.440> uh<00:20:42.640> given<00:20:42.960> that<00:20:43.720> the<00:20:44.240> relay<00:20:45.240> the 00:20:45.470 --> 00:20:45.480 align:start position:0% message then uh given that the relay the 00:20:45.480 --> 00:20:46.390 align:start position:0% message then uh given that the relay the S<00:20:45.760> the 00:20:46.390 --> 00:20:46.400 align:start position:0% S the 00:20:46.400 --> 00:20:49.710 align:start position:0% S the overlay<00:20:47.400> uh<00:20:47.559> network<00:20:48.080> is<00:20:48.760> uh<00:20:48.960> established 00:20:49.710 --> 00:20:49.720 align:start position:0% overlay uh network is uh established 00:20:49.720 --> 00:20:53.630 align:start position:0% overlay uh network is uh established with<00:20:49.960> b<00:20:50.200> and<00:20:50.440> d<00:20:51.400> it<00:20:51.559> will<00:20:51.799> only<00:20:52.679> deploy<00:20:53.320> or 00:20:53.630 --> 00:20:53.640 align:start position:0% with b and d it will only deploy or 00:20:53.640 --> 00:20:56.990 align:start position:0% with b and d it will only deploy or sorry<00:20:54.400> uh<00:20:54.559> spread<00:20:55.360> the<00:20:55.679> the<00:20:55.799> message<00:20:56.200> to<00:20:56.640> to<00:20:56.799> b 00:20:56.990 --> 00:20:57.000 align:start position:0% sorry uh spread the the message to to b 00:20:57.000 --> 00:20:59.149 align:start position:0% sorry uh spread the the message to to b and<00:20:57.159> d<00:20:58.039> and<00:20:58.200> not<00:20:58.400> not 00:20:59.149 --> 00:20:59.159 align:start position:0% and d and not not 00:20:59.159 --> 00:21:01.390 align:start position:0% and d and not not others<00:21:00.159> and<00:21:00.360> something<00:21:00.720> important<00:21:01.039> to<00:21:01.200> bear 00:21:01.390 --> 00:21:01.400 align:start position:0% others and something important to bear 00:21:01.400 --> 00:21:03.390 align:start position:0% others and something important to bear in<00:21:01.520> mind<00:21:01.720> is<00:21:01.880> that<00:21:02.320> this<00:21:02.480> can<00:21:02.640> change<00:21:03.120> every 00:21:03.390 --> 00:21:03.400 align:start position:0% in mind is that this can change every 00:21:03.400 --> 00:21:06.190 align:start position:0% in mind is that this can change every every<00:21:03.600> second<00:21:04.039> it's<00:21:04.240> not<00:21:04.840> a<00:21:05.039> fixed<00:21:05.600> uh<00:21:05.720> overlay 00:21:06.190 --> 00:21:06.200 align:start position:0% every second it's not a fixed uh overlay 00:21:06.200 --> 00:21:11.630 align:start position:0% every second it's not a fixed uh overlay network<00:21:06.760> but<00:21:06.919> it's<00:21:07.240> something<00:21:07.600> that<00:21:07.760> is 00:21:11.630 --> 00:21:11.640 align:start position:0% 00:21:11.640 --> 00:21:17.710 align:start position:0% alive<00:21:12.640> okay 00:21:17.710 --> 00:21:17.720 align:start position:0% 00:21:17.720 --> 00:21:20.630 align:start position:0% and<00:21:18.720> uh<00:21:19.000> okay<00:21:19.480> uh<00:21:19.720> then<00:21:19.880> we<00:21:20.000> have<00:21:20.200> the<00:21:20.360> red 00:21:20.630 --> 00:21:20.640 align:start position:0% and uh okay uh then we have the red 00:21:20.640 --> 00:21:23.470 align:start position:0% and uh okay uh then we have the red limit<00:21:21.279> nullifier<00:21:22.200> uh<00:21:22.320> this<00:21:22.400> is<00:21:22.600> a<00:21:22.760> very 00:21:23.470 --> 00:21:23.480 align:start position:0% limit nullifier uh this is a very 00:21:23.480 --> 00:21:25.350 align:start position:0% limit nullifier uh this is a very interesting<00:21:24.480> uh<00:21:24.720> topic<00:21:25.000> and<00:21:25.200> very 00:21:25.350 --> 00:21:25.360 align:start position:0% interesting uh topic and very 00:21:25.360 --> 00:21:26.990 align:start position:0% interesting uh topic and very interesting<00:21:25.760> technology 00:21:26.990 --> 00:21:27.000 align:start position:0% interesting technology 00:21:27.000 --> 00:21:29.350 align:start position:0% interesting technology because<00:21:28.000> it<00:21:28.159> it<00:21:28.279> allows 00:21:29.350 --> 00:21:29.360 align:start position:0% because it it allows 00:21:29.360 --> 00:21:33.789 align:start position:0% because it it allows um<00:21:29.679> to<00:21:30.159> protect<00:21:30.559> the<00:21:30.880> network<00:21:31.880> against<00:21:32.799> spam 00:21:33.789 --> 00:21:33.799 align:start position:0% um to protect the network against spam 00:21:33.799 --> 00:21:36.789 align:start position:0% um to protect the network against spam in<00:21:33.919> a<00:21:34.240> in<00:21:34.360> a<00:21:34.520> private<00:21:34.960> way<00:21:35.360> so<00:21:35.600> that 00:21:36.789 --> 00:21:36.799 align:start position:0% in a in a private way so that 00:21:36.799 --> 00:21:39.149 align:start position:0% in a in a private way so that the<00:21:37.799> the 00:21:39.149 --> 00:21:39.159 align:start position:0% the the 00:21:39.159 --> 00:21:43.110 align:start position:0% the the uh<00:21:40.159> the<00:21:40.320> note<00:21:40.799> can<00:21:41.279> prove<00:21:41.919> that<00:21:42.159> it<00:21:42.320> belongs<00:21:42.799> to 00:21:43.110 --> 00:21:43.120 align:start position:0% uh the note can prove that it belongs to 00:21:43.120 --> 00:21:45.269 align:start position:0% uh the note can prove that it belongs to to<00:21:43.279> the<00:21:43.400> network<00:21:44.279> without<00:21:44.760> actually 00:21:45.269 --> 00:21:45.279 align:start position:0% to the network without actually 00:21:45.279 --> 00:21:50.310 align:start position:0% to the network without actually disclosing<00:21:46.279> uh<00:21:46.720> its<00:21:47.720> information<00:21:48.600> or<00:21:49.600> it's 00:21:50.310 --> 00:21:50.320 align:start position:0% disclosing uh its information or it's 00:21:50.320 --> 00:21:53.669 align:start position:0% disclosing uh its information or it's very<00:21:51.200> very<00:21:51.360> cool<00:21:51.679> how<00:21:52.080> how<00:21:52.240> it's<00:21:52.799> um 00:21:53.669 --> 00:21:53.679 align:start position:0% very very cool how how it's um 00:21:53.679 --> 00:21:57.190 align:start position:0% very very cool how how it's um implemented<00:21:54.679> and<00:21:54.960> it's<00:21:55.159> based<00:21:55.480> on<00:21:56.080> cnar 00:21:57.190 --> 00:21:57.200 align:start position:0% implemented and it's based on cnar 00:21:57.200 --> 00:22:00.110 align:start position:0% implemented and it's based on cnar technology<00:21:58.200> and<00:21:58.960> a<00:21:59.200> smart<00:21:59.520> contract 00:22:00.110 --> 00:22:00.120 align:start position:0% technology and a smart contract 00:22:00.120 --> 00:22:04.070 align:start position:0% technology and a smart contract currently<00:22:00.679> in<00:22:01.080> sepolia<00:22:02.080> where<00:22:02.880> the<00:22:03.880> the 00:22:04.070 --> 00:22:04.080 align:start position:0% currently in sepolia where the the 00:22:04.080 --> 00:22:07.750 align:start position:0% currently in sepolia where the the membership<00:22:04.600> set<00:22:04.960> is<00:22:06.080> configured<00:22:07.080> I<00:22:07.200> think<00:22:07.640> uh 00:22:07.750 --> 00:22:07.760 align:start position:0% membership set is configured I think uh 00:22:07.760 --> 00:22:10.110 align:start position:0% membership set is configured I think uh we<00:22:07.880> are<00:22:08.039> about<00:22:08.279> to<00:22:08.600> release<00:22:09.360> um<00:22:09.559> version<00:22:09.840> two 00:22:10.110 --> 00:22:10.120 align:start position:0% we are about to release um version two 00:22:10.120 --> 00:22:11.630 align:start position:0% we are about to release um version two of 00:22:11.630 --> 00:22:11.640 align:start position:0% of 00:22:11.640 --> 00:22:16.590 align:start position:0% of rln<00:22:12.640> and<00:22:13.640> uh<00:22:14.000> and<00:22:14.200> yeah<00:22:14.440> it's<00:22:15.000> um<00:22:15.520> basically<00:22:16.000> to 00:22:16.590 --> 00:22:16.600 align:start position:0% rln and uh and yeah it's um basically to 00:22:16.600 --> 00:22:20.390 align:start position:0% rln and uh and yeah it's um basically to this<00:22:16.720> is<00:22:17.080> a<00:22:17.279> quite<00:22:17.760> complex<00:22:18.799> um<00:22:19.799> topic<00:22:20.200> and 00:22:20.390 --> 00:22:20.400 align:start position:0% this is a quite complex um topic and 00:22:20.400 --> 00:22:23.190 align:start position:0% this is a quite complex um topic and it's<00:22:20.640> be<00:22:21.120> beyond<00:22:21.440> my<00:22:21.600> knowledge<00:22:22.559> but<00:22:22.840> just<00:22:22.960> to 00:22:23.190 --> 00:22:23.200 align:start position:0% it's be beyond my knowledge but just to 00:22:23.200 --> 00:22:25.950 align:start position:0% it's be beyond my knowledge but just to to<00:22:23.360> get<00:22:23.640> an<00:22:23.799> idea<00:22:24.760> the<00:22:24.880> main<00:22:25.120> purpose<00:22:25.440> of<00:22:25.600> it<00:22:25.799> is 00:22:25.950 --> 00:22:25.960 align:start position:0% to get an idea the main purpose of it is 00:22:25.960 --> 00:22:28.510 align:start position:0% to get an idea the main purpose of it is to<00:22:26.360> protect<00:22:26.679> the<00:22:26.840> network<00:22:27.360> against<00:22:27.799> spam<00:22:28.120> in<00:22:28.240> a 00:22:28.510 --> 00:22:28.520 align:start position:0% to protect the network against spam in a 00:22:28.520 --> 00:22:33.390 align:start position:0% to protect the network against spam in a private 00:22:33.390 --> 00:22:33.400 align:start position:0% 00:22:33.400 --> 00:22:35.710 align:start position:0% way<00:22:34.400> uh<00:22:34.679> okay 00:22:35.710 --> 00:22:35.720 align:start position:0% way uh okay 00:22:35.720 --> 00:22:40.110 align:start position:0% way uh okay um<00:22:36.720> regarding<00:22:37.200> the<00:22:37.360> the<00:22:37.480> waku<00:22:37.840> message<00:22:38.679> the<00:22:39.559> um 00:22:40.110 --> 00:22:40.120 align:start position:0% um regarding the the waku message the um 00:22:40.120 --> 00:22:43.190 align:start position:0% um regarding the the waku message the um as<00:22:41.120> you<00:22:41.320> remember<00:22:41.960> this<00:22:42.080> is<00:22:42.440> the<00:22:42.640> the<00:22:42.799> one<00:22:43.039> that 00:22:43.190 --> 00:22:43.200 align:start position:0% as you remember this is the the one that 00:22:43.200 --> 00:22:46.510 align:start position:0% as you remember this is the the one that is<00:22:43.360> being<00:22:44.200> uh<00:22:44.279> sent<00:22:44.760> across<00:22:45.159> the<00:22:45.440> the<00:22:45.559> overlay 00:22:46.510 --> 00:22:46.520 align:start position:0% is being uh sent across the the overlay 00:22:46.520 --> 00:22:50.310 align:start position:0% is being uh sent across the the overlay Network<00:22:47.520> um<00:22:48.520> basically<00:22:49.279> it<00:22:49.400> contains<00:22:50.159> it 00:22:50.310 --> 00:22:50.320 align:start position:0% Network um basically it contains it 00:22:50.320 --> 00:22:54.350 align:start position:0% Network um basically it contains it contains<00:22:50.799> a<00:22:50.919> bit<00:22:51.120> more<00:22:51.760> Fields<00:22:52.679> than<00:22:53.679> uh<00:22:53.840> shown 00:22:54.350 --> 00:22:54.360 align:start position:0% contains a bit more Fields than uh shown 00:22:54.360 --> 00:22:57.710 align:start position:0% contains a bit more Fields than uh shown in<00:22:54.520> in<00:22:54.640> the<00:22:54.919> left<00:22:55.919> but<00:22:56.520> basically<00:22:57.120> we<00:22:57.320> have<00:22:57.600> a 00:22:57.710 --> 00:22:57.720 align:start position:0% in in the left but basically we have a 00:22:57.720 --> 00:22:59.070 align:start position:0% in in the left but basically we have a payload 00:22:59.070 --> 00:22:59.080 align:start position:0% payload 00:22:59.080 --> 00:23:02.110 align:start position:0% payload uh<00:22:59.360> which<00:22:59.799> for<00:23:00.080> which<00:23:00.320> we<00:23:00.440> don't<00:23:00.799> impose 00:23:02.110 --> 00:23:02.120 align:start position:0% uh which for which we don't impose 00:23:02.120 --> 00:23:06.269 align:start position:0% uh which for which we don't impose any<00:23:03.120> um<00:23:03.880> additional<00:23:04.799> encryption<00:23:05.799> we<00:23:05.960> leave 00:23:06.269 --> 00:23:06.279 align:start position:0% any um additional encryption we leave 00:23:06.279 --> 00:23:11.510 align:start position:0% any um additional encryption we leave the<00:23:06.559> encryption<00:23:07.480> to<00:23:07.640> the<00:23:07.840> app<00:23:08.440> um<00:23:09.840> developers 00:23:11.510 --> 00:23:11.520 align:start position:0% the encryption to the app um developers 00:23:11.520 --> 00:23:14.630 align:start position:0% the encryption to the app um developers and<00:23:12.520> regarding<00:23:13.159> encryption<00:23:14.159> important 00:23:14.630 --> 00:23:14.640 align:start position:0% and regarding encryption important 00:23:14.640 --> 00:23:16.789 align:start position:0% and regarding encryption important something<00:23:14.960> to<00:23:15.120> to<00:23:15.240> notice<00:23:15.600> that<00:23:16.240> uh<00:23:16.360> there<00:23:16.480> is 00:23:16.789 --> 00:23:16.799 align:start position:0% something to to notice that uh there is 00:23:16.799 --> 00:23:17.870 align:start position:0% something to to notice that uh there is pointto<00:23:17.159> point 00:23:17.870 --> 00:23:17.880 align:start position:0% pointto point 00:23:17.880 --> 00:23:22.350 align:start position:0% pointto point encryption<00:23:18.880> um<00:23:19.520> inherited<00:23:20.320> by<00:23:20.600> the<00:23:20.840> lip<00:23:21.360> P2P 00:23:22.350 --> 00:23:22.360 align:start position:0% encryption um inherited by the lip P2P 00:23:22.360 --> 00:23:26.669 align:start position:0% encryption um inherited by the lip P2P um<00:23:22.919> which<00:23:23.080> is<00:23:23.520> made<00:23:24.039> um<00:23:24.880> following<00:23:25.320> the<00:23:25.520> noise 00:23:26.669 --> 00:23:26.679 align:start position:0% um which is made um following the noise 00:23:26.679 --> 00:23:29.029 align:start position:0% um which is made um following the noise protocol<00:23:27.679> and<00:23:27.919> we<00:23:28.080> have<00:23:28.279> the<00:23:28.559> the<00:23:28.640> content 00:23:29.029 --> 00:23:29.039 align:start position:0% protocol and we have the the content 00:23:29.039 --> 00:23:32.990 align:start position:0% protocol and we have the the content topic<00:23:30.039> uh<00:23:30.159> which<00:23:30.279> is<00:23:30.400> a<00:23:30.559> field<00:23:31.279> um<00:23:32.080> useful<00:23:32.640> from 00:23:32.990 --> 00:23:33.000 align:start position:0% topic uh which is a field um useful from 00:23:33.000 --> 00:23:36.230 align:start position:0% topic uh which is a field um useful from the<00:23:33.440> for<00:23:33.640> example<00:23:34.000> in<00:23:34.120> the<00:23:34.240> filter<00:23:35.240> protocol 00:23:36.230 --> 00:23:36.240 align:start position:0% the for example in the filter protocol 00:23:36.240 --> 00:23:39.789 align:start position:0% the for example in the filter protocol um<00:23:36.600> an<00:23:36.840> H<00:23:37.120> note<00:23:37.919> uh<00:23:38.279> subscribes<00:23:39.000> to<00:23:39.240> a<00:23:39.440> certain 00:23:39.789 --> 00:23:39.799 align:start position:0% um an H note uh subscribes to a certain 00:23:39.799 --> 00:23:41.909 align:start position:0% um an H note uh subscribes to a certain content<00:23:40.159> topic<00:23:40.840> and<00:23:41.039> from<00:23:41.520> all<00:23:41.799> the 00:23:41.909 --> 00:23:41.919 align:start position:0% content topic and from all the 00:23:41.919 --> 00:23:44.029 align:start position:0% content topic and from all the information<00:23:42.400> that<00:23:42.559> is<00:23:43.200> shared<00:23:43.640> across<00:23:43.919> the 00:23:44.029 --> 00:23:44.039 align:start position:0% information that is shared across the 00:23:44.039 --> 00:23:47.750 align:start position:0% information that is shared across the network<00:23:45.039> this<00:23:45.679> uh<00:23:45.799> the<00:23:45.919> messages<00:23:46.919> the<00:23:47.480> The 00:23:47.750 --> 00:23:47.760 align:start position:0% network this uh the messages the The 00:23:47.760 --> 00:23:50.390 align:start position:0% network this uh the messages the The Edge<00:23:48.039> note<00:23:48.320> is<00:23:48.480> interested<00:23:48.919> in<00:23:49.760> is<00:23:50.039> going<00:23:50.240> to 00:23:50.390 --> 00:23:50.400 align:start position:0% Edge note is interested in is going to 00:23:50.400 --> 00:23:53.149 align:start position:0% Edge note is interested in is going to be<00:23:51.000> sent<00:23:51.679> to<00:23:52.039> to 00:23:53.149 --> 00:23:53.159 align:start position:0% be sent to to 00:23:53.159 --> 00:23:55.230 align:start position:0% be sent to to them 00:23:55.230 --> 00:23:55.240 align:start position:0% them 00:23:55.240 --> 00:24:03.230 align:start position:0% them okay<00:23:56.240> and<00:23:56.640> regarding<00:23:57.000> this<00:23:57.159> point 00:24:03.230 --> 00:24:03.240 align:start position:0% 00:24:03.240 --> 00:24:06.149 align:start position:0% okay<00:24:03.400> so<00:24:03.799> um<00:24:04.240> to<00:24:04.400> build<00:24:04.640> on<00:24:04.760> top<00:24:04.960> of<00:24:05.120> waku<00:24:05.880> uh<00:24:06.039> I 00:24:06.149 --> 00:24:06.159 align:start position:0% okay so um to build on top of waku uh I 00:24:06.159 --> 00:24:07.750 align:start position:0% okay so um to build on top of waku uh I just<00:24:06.400> going<00:24:06.520> to<00:24:06.640> introduce<00:24:07.000> you<00:24:07.120> a<00:24:07.240> bit<00:24:07.520> to 00:24:07.750 --> 00:24:07.760 align:start position:0% just going to introduce you a bit to 00:24:07.760 --> 00:24:10.230 align:start position:0% just going to introduce you a bit to cdks<00:24:08.279> that<00:24:08.440> we<00:24:08.600> have<00:24:08.919> and<00:24:09.240> languages<00:24:09.760> we 00:24:10.230 --> 00:24:10.240 align:start position:0% cdks that we have and languages we 00:24:10.240 --> 00:24:13.630 align:start position:0% cdks that we have and languages we support<00:24:11.240> uh<00:24:11.559> so<00:24:12.240> this<00:24:12.640> uh<00:24:12.760> QR<00:24:13.080> code<00:24:13.240> leads<00:24:13.520> you 00:24:13.630 --> 00:24:13.640 align:start position:0% support uh so this uh QR code leads you 00:24:13.640 --> 00:24:15.510 align:start position:0% support uh so this uh QR code leads you to<00:24:13.880> documentation<00:24:14.480> website<00:24:14.919> there<00:24:15.000> is<00:24:15.200> a<00:24:15.320> lot 00:24:15.510 --> 00:24:15.520 align:start position:0% to documentation website there is a lot 00:24:15.520 --> 00:24:17.310 align:start position:0% to documentation website there is a lot of<00:24:15.720> information<00:24:16.600> uh<00:24:16.720> links<00:24:17.000> to<00:24:17.159> our 00:24:17.310 --> 00:24:17.320 align:start position:0% of information uh links to our 00:24:17.320 --> 00:24:19.230 align:start position:0% of information uh links to our communities<00:24:17.799> and<00:24:18.039> such<00:24:18.600> if<00:24:18.720> you<00:24:18.880> have<00:24:19.039> any 00:24:19.230 --> 00:24:19.240 align:start position:0% communities and such if you have any 00:24:19.240 --> 00:24:20.909 align:start position:0% communities and such if you have any questions<00:24:19.600> about<00:24:19.880> anything<00:24:20.360> like<00:24:20.559> vaku 00:24:20.909 --> 00:24:20.919 align:start position:0% questions about anything like vaku 00:24:20.919 --> 00:24:24.510 align:start position:0% questions about anything like vaku related<00:24:21.760> uh<00:24:21.880> code<00:24:22.159> is<00:24:22.880> failing<00:24:23.880> uh<00:24:24.159> behaves 00:24:24.510 --> 00:24:24.520 align:start position:0% related uh code is failing uh behaves 00:24:24.520 --> 00:24:26.669 align:start position:0% related uh code is failing uh behaves unexpectedly<00:24:25.399> reach<00:24:25.640> out<00:24:25.799> to<00:24:25.960> us<00:24:26.440> uh 00:24:26.669 --> 00:24:26.679 align:start position:0% unexpectedly reach out to us uh 00:24:26.679 --> 00:24:28.870 align:start position:0% unexpectedly reach out to us uh everything<00:24:27.000> is<00:24:27.200> there<00:24:27.760> but<00:24:28.000> we<00:24:28.120> do<00:24:28.399> support 00:24:28.870 --> 00:24:28.880 align:start position:0% everything is there but we do support 00:24:28.880 --> 00:24:31.149 align:start position:0% everything is there but we do support JavaScript<00:24:29.320> and<00:24:29.440> typescript<00:24:30.159> right<00:24:30.360> now<00:24:30.799> and 00:24:31.149 --> 00:24:31.159 align:start position:0% JavaScript and typescript right now and 00:24:31.159 --> 00:24:34.470 align:start position:0% JavaScript and typescript right now and Nim<00:24:31.880> is<00:24:32.360> uh<00:24:32.480> and<00:24:32.720> second<00:24:33.000> language<00:24:33.559> that<00:24:33.919> uh 00:24:34.470 --> 00:24:34.480 align:start position:0% Nim is uh and second language that uh 00:24:34.480 --> 00:24:36.669 align:start position:0% Nim is uh and second language that uh it's<00:24:34.640> more<00:24:34.840> of<00:24:35.200> first<00:24:35.480> language<00:24:35.840> but<00:24:35.960> still<00:24:36.520> uh 00:24:36.669 --> 00:24:36.679 align:start position:0% it's more of first language but still uh 00:24:36.679 --> 00:24:38.669 align:start position:0% it's more of first language but still uh it's<00:24:37.080> the<00:24:37.240> language<00:24:37.760> of<00:24:37.880> our<00:24:38.120> choice<00:24:38.399> and<00:24:38.559> we 00:24:38.669 --> 00:24:38.679 align:start position:0% it's the language of our choice and we 00:24:38.679 --> 00:24:40.510 align:start position:0% it's the language of our choice and we have<00:24:38.799> an<00:24:38.960> implementation<00:24:39.559> of<00:24:39.760> waku<00:24:40.120> in<00:24:40.240> Nim 00:24:40.510 --> 00:24:40.520 align:start position:0% have an implementation of waku in Nim 00:24:40.520 --> 00:24:42.830 align:start position:0% have an implementation of waku in Nim language<00:24:41.120> and<00:24:41.240> it's<00:24:41.399> compilable<00:24:41.880> to<00:24:42.080> C<00:24:42.600> and 00:24:42.830 --> 00:24:42.840 align:start position:0% language and it's compilable to C and 00:24:42.840 --> 00:24:44.870 align:start position:0% language and it's compilable to C and you<00:24:43.000> have<00:24:43.559> uh<00:24:43.760> the<00:24:43.919> C<00:24:44.080> artifact<00:24:44.520> that<00:24:44.640> you<00:24:44.720> can 00:24:44.870 --> 00:24:44.880 align:start position:0% you have uh the C artifact that you can 00:24:44.880 --> 00:24:48.070 align:start position:0% you have uh the C artifact that you can consume<00:24:45.240> later<00:24:45.480> on<00:24:46.279> we're<00:24:46.480> also<00:24:47.120> working<00:24:47.480> on 00:24:48.070 --> 00:24:48.080 align:start position:0% consume later on we're also working on 00:24:48.080 --> 00:24:50.310 align:start position:0% consume later on we're also working on uh<00:24:48.279> better<00:24:49.000> uh 00:24:50.310 --> 00:24:50.320 align:start position:0% uh better uh 00:24:50.320 --> 00:24:55.710 align:start position:0% uh better uh go<00:24:51.320> uh<00:24:51.880> bindings<00:24:52.600> and<00:24:52.760> cdk<00:24:53.399> and<00:24:53.960> uh<00:24:54.320> rust<00:24:55.000> and 00:24:55.710 --> 00:24:55.720 align:start position:0% go uh bindings and cdk and uh rust and 00:24:55.720 --> 00:24:58.389 align:start position:0% go uh bindings and cdk and uh rust and python<00:24:56.720> uh<00:24:57.000> they<00:24:57.120> are<00:24:57.279> work<00:24:57.440> in<00:24:57.640> progress<00:24:58.000> but 00:24:58.389 --> 00:24:58.399 align:start position:0% python uh they are work in progress but 00:24:58.399 --> 00:25:01.190 align:start position:0% python uh they are work in progress but can<00:24:58.480> be<00:24:58.600> used<00:24:58.799> to<00:24:58.960> some<00:24:59.200> cases<00:24:59.640> right<00:24:59.799> now<00:25:00.520> um 00:25:01.190 --> 00:25:01.200 align:start position:0% can be used to some cases right now um 00:25:01.200 --> 00:25:03.190 align:start position:0% can be used to some cases right now um so<00:25:01.399> for<00:25:01.600> GS<00:25:01.880> waku<00:25:02.240> we<00:25:02.320> have<00:25:02.520> like<00:25:02.640> a<00:25:02.760> couple<00:25:03.000> of 00:25:03.190 --> 00:25:03.200 align:start position:0% so for GS waku we have like a couple of 00:25:03.200 --> 00:25:06.590 align:start position:0% so for GS waku we have like a couple of packages<00:25:04.080> main<00:25:04.279> one<00:25:04.480> is<00:25:04.640> waku<00:25:04.960> SDK<00:25:05.919> just<00:25:06.399> uh 00:25:06.590 --> 00:25:06.600 align:start position:0% packages main one is waku SDK just uh 00:25:06.600 --> 00:25:08.710 align:start position:0% packages main one is waku SDK just uh install<00:25:07.000> it<00:25:07.200> use<00:25:07.440> it<00:25:07.760> it<00:25:07.880> going<00:25:08.000> to<00:25:08.120> work<00:25:08.600> I 00:25:08.710 --> 00:25:08.720 align:start position:0% install it use it it going to work I 00:25:08.720 --> 00:25:12.149 align:start position:0% install it use it it going to work I hope<00:25:08.960> so<00:25:09.840> then<00:25:10.320> uh<00:25:10.480> we<00:25:10.640> have<00:25:10.880> a<00:25:11.440> a<00:25:11.640> wrapping<00:25:11.960> for 00:25:12.149 --> 00:25:12.159 align:start position:0% hope so then uh we have a a wrapping for 00:25:12.159 --> 00:25:15.789 align:start position:0% hope so then uh we have a a wrapping for react<00:25:13.159> also<00:25:14.159> uh<00:25:14.520> deals<00:25:14.880> with<00:25:15.200> react<00:25:15.600> life 00:25:15.789 --> 00:25:15.799 align:start position:0% react also uh deals with react life 00:25:15.799 --> 00:25:19.350 align:start position:0% react also uh deals with react life cycle<00:25:16.080> methods<00:25:16.399> and<00:25:16.640> stuff<00:25:17.159> that<00:25:17.520> busts<00:25:17.880> a<00:25:18.360> lot 00:25:19.350 --> 00:25:19.360 align:start position:0% cycle methods and stuff that busts a lot 00:25:19.360 --> 00:25:21.510 align:start position:0% cycle methods and stuff that busts a lot of<00:25:19.760> uh<00:25:19.960> creates<00:25:20.279> a<00:25:20.360> lot<00:25:20.520> of<00:25:20.600> unexpected<00:25:21.360> uh 00:25:21.510 --> 00:25:21.520 align:start position:0% of uh creates a lot of unexpected uh 00:25:21.520 --> 00:25:23.909 align:start position:0% of uh creates a lot of unexpected uh Behavior<00:25:22.240> Uh<00:25:22.559> then<00:25:23.000> we<00:25:23.120> have<00:25:23.200> a<00:25:23.320> create<00:25:23.640> up 00:25:23.909 --> 00:25:23.919 align:start position:0% Behavior Uh then we have a create up 00:25:23.919 --> 00:25:26.070 align:start position:0% Behavior Uh then we have a create up that<00:25:24.039> can<00:25:24.200> boost<00:25:24.559> up<00:25:24.720> your<00:25:25.000> application<00:25:25.679> quite 00:25:26.070 --> 00:25:26.080 align:start position:0% that can boost up your application quite 00:25:26.080 --> 00:25:28.950 align:start position:0% that can boost up your application quite easily<00:25:27.080> might<00:25:27.240> be<00:25:27.360> useful<00:25:27.760> as<00:25:27.880> well<00:25:28.440> so<00:25:28.840> the 00:25:28.950 --> 00:25:28.960 align:start position:0% easily might be useful as well so the 00:25:28.960 --> 00:25:32.630 align:start position:0% easily might be useful as well so the main<00:25:29.200> users<00:25:29.799> right<00:25:30.000> now<00:25:30.640> are<00:25:31.279> status<00:25:32.039> status 00:25:32.630 --> 00:25:32.640 align:start position:0% main users right now are status status 00:25:32.640 --> 00:25:35.669 align:start position:0% main users right now are status status is<00:25:33.080> uh<00:25:34.000> uh<00:25:34.440> a<00:25:34.559> messaging 00:25:35.669 --> 00:25:35.679 align:start position:0% is uh uh a messaging 00:25:35.679 --> 00:25:38.029 align:start position:0% is uh uh a messaging application<00:25:36.679> which<00:25:37.080> uh<00:25:37.200> is<00:25:37.360> dedicated<00:25:37.840> for 00:25:38.029 --> 00:25:38.039 align:start position:0% application which uh is dedicated for 00:25:38.039 --> 00:25:40.669 align:start position:0% application which uh is dedicated for onet<00:25:38.240> to<00:25:38.360> one<00:25:38.520> chat<00:25:38.799> as<00:25:38.919> well<00:25:39.080> as<00:25:39.679> communities 00:25:40.669 --> 00:25:40.679 align:start position:0% onet to one chat as well as communities 00:25:40.679 --> 00:25:44.110 align:start position:0% onet to one chat as well as communities uh<00:25:41.039> and<00:25:41.799> and<00:25:42.200> uh<00:25:42.760> uh<00:25:42.840> it<00:25:42.960> uses<00:25:43.279> Vu<00:25:43.559> underneath 00:25:44.110 --> 00:25:44.120 align:start position:0% uh and and uh uh it uses Vu underneath 00:25:44.120 --> 00:25:47.269 align:start position:0% uh and and uh uh it uses Vu underneath it<00:25:44.279> has<00:25:44.440> its<00:25:44.600> own<00:25:45.200> uh<00:25:45.559> set<00:25:45.799> of<00:25:46.159> nodes<00:25:46.960> that<00:25:47.120> are 00:25:47.269 --> 00:25:47.279 align:start position:0% it has its own uh set of nodes that are 00:25:47.279 --> 00:25:49.630 align:start position:0% it has its own uh set of nodes that are operating<00:25:48.039> uh<00:25:48.159> there<00:25:48.279> are<00:25:49.000> a<00:25:49.120> bit<00:25:49.320> different 00:25:49.630 --> 00:25:49.640 align:start position:0% operating uh there are a bit different 00:25:49.640 --> 00:25:52.269 align:start position:0% operating uh there are a bit different guarantees<00:25:50.480> than<00:25:51.159> uh<00:25:51.360> defaults<00:25:51.919> that<00:25:52.080> we 00:25:52.269 --> 00:25:52.279 align:start position:0% guarantees than uh defaults that we 00:25:52.279 --> 00:25:55.190 align:start position:0% guarantees than uh defaults that we provide<00:25:52.760> propose<00:25:53.600> uh<00:25:53.760> projects<00:25:54.080> to<00:25:54.200> use<00:25:55.000> such 00:25:55.190 --> 00:25:55.200 align:start position:0% provide propose uh projects to use such 00:25:55.200 --> 00:25:58.470 align:start position:0% provide propose uh projects to use such as<00:25:55.600> uh<00:25:55.720> a<00:25:55.840> bit<00:25:56.080> extended<00:25:56.799> uh<00:25:56.960> store<00:25:57.640> retention 00:25:58.470 --> 00:25:58.480 align:start position:0% as uh a bit extended uh store retention 00:25:58.480 --> 00:26:00.310 align:start position:0% as uh a bit extended uh store retention right<00:25:58.720> because<00:25:59.279> such<00:25:59.480> applications<00:25:59.960> want<00:26:00.159> to 00:26:00.310 --> 00:26:00.320 align:start position:0% right because such applications want to 00:26:00.320 --> 00:26:03.710 align:start position:0% right because such applications want to retain<00:26:01.240> uh<00:26:01.480> data<00:26:01.880> longer<00:26:02.880> then<00:26:03.320> a<00:26:03.440> second 00:26:03.710 --> 00:26:03.720 align:start position:0% retain uh data longer then a second 00:26:03.720 --> 00:26:05.909 align:start position:0% retain uh data longer then a second project<00:26:04.000> that<00:26:04.120> uses<00:26:04.440> waku<00:26:04.760> is<00:26:04.880> run<00:26:05.640> this<00:26:05.720> is 00:26:05.909 --> 00:26:05.919 align:start position:0% project that uses waku is run this is 00:26:05.919 --> 00:26:08.389 align:start position:0% project that uses waku is run this is privacy<00:26:06.320> oriented<00:26:06.760> defi<00:26:07.159> project<00:26:07.880> and<00:26:08.240> uh 00:26:08.389 --> 00:26:08.399 align:start position:0% privacy oriented defi project and uh 00:26:08.399 --> 00:26:10.350 align:start position:0% privacy oriented defi project and uh vaku<00:26:08.760> is<00:26:08.840> used<00:26:09.080> for<00:26:09.279> broadcasting<00:26:09.840> fees<00:26:10.240> in 00:26:10.350 --> 00:26:10.360 align:start position:0% vaku is used for broadcasting fees in 00:26:10.360 --> 00:26:15.029 align:start position:0% vaku is used for broadcasting fees in the<00:26:10.520> network<00:26:11.000> so<00:26:11.240> that<00:26:11.919> it's<00:26:12.360> uh<00:26:13.279> um<00:26:14.279> not<00:26:14.440> known 00:26:15.029 --> 00:26:15.039 align:start position:0% the network so that it's uh um not known 00:26:15.039 --> 00:26:17.750 align:start position:0% the network so that it's uh um not known where<00:26:15.279> it<00:26:15.480> originates<00:26:16.080> from<00:26:17.039> uh<00:26:17.240> then<00:26:17.559> the 00:26:17.750 --> 00:26:17.760 align:start position:0% where it originates from uh then the 00:26:17.760 --> 00:26:21.230 align:start position:0% where it originates from uh then the graph<00:26:18.200> also<00:26:18.399> uses<00:26:19.000> vaku<00:26:19.919> for<00:26:20.640> uh<00:26:20.799> information 00:26:21.230 --> 00:26:21.240 align:start position:0% graph also uses vaku for uh information 00:26:21.240 --> 00:26:24.310 align:start position:0% graph also uses vaku for uh information exchange<00:26:21.640> between<00:26:21.919> some<00:26:22.039> of<00:26:22.159> their<00:26:22.679> nodes<00:26:23.679> um 00:26:24.310 --> 00:26:24.320 align:start position:0% exchange between some of their nodes um 00:26:24.320 --> 00:26:28.830 align:start position:0% exchange between some of their nodes um yeah<00:26:24.679> so<00:26:25.720> um<00:26:26.720> and<00:26:26.960> use<00:26:27.320> cases<00:26:28.080> uh 00:26:28.830 --> 00:26:28.840 align:start position:0% yeah so um and use cases uh 00:26:28.840 --> 00:26:31.909 align:start position:0% yeah so um and use cases uh there<00:26:29.000> can<00:26:29.159> be<00:26:29.399> anything<00:26:30.320> such<00:26:30.520> as<00:26:30.880> defi<00:26:31.559> as<00:26:31.679> I 00:26:31.909 --> 00:26:31.919 align:start position:0% there can be anything such as defi as I 00:26:31.919 --> 00:26:34.430 align:start position:0% there can be anything such as defi as I already<00:26:32.240> mentioned<00:26:32.960> Community<00:26:33.440> run<00:26:33.760> UPS<00:26:34.240> as 00:26:34.430 --> 00:26:34.440 align:start position:0% already mentioned Community run UPS as 00:26:34.440 --> 00:26:38.230 align:start position:0% already mentioned Community run UPS as well<00:26:35.159> uh<00:26:35.880> some<00:26:36.080> social<00:26:37.120> interactions<00:26:38.120> uh 00:26:38.230 --> 00:26:38.240 align:start position:0% well uh some social interactions uh 00:26:38.240 --> 00:26:41.110 align:start position:0% well uh some social interactions uh wallet<00:26:38.640> to<00:26:38.840> wallet<00:26:39.120> communication<00:26:40.120> gaming 00:26:41.110 --> 00:26:41.120 align:start position:0% wallet to wallet communication gaming 00:26:41.120 --> 00:26:44.909 align:start position:0% wallet to wallet communication gaming you<00:26:41.320> name<00:26:41.559> it<00:26:42.120> so<00:26:42.960> uh<00:26:43.679> we<00:26:43.840> saw<00:26:44.279> interesting 00:26:44.909 --> 00:26:44.919 align:start position:0% you name it so uh we saw interesting 00:26:44.919 --> 00:26:48.070 align:start position:0% you name it so uh we saw interesting applications<00:26:45.919> even<00:26:46.279> with<00:26:46.840> uh<00:26:47.279> ge<00:26:47.600> location 00:26:48.070 --> 00:26:48.080 align:start position:0% applications even with uh ge location 00:26:48.080 --> 00:26:51.669 align:start position:0% applications even with uh ge location position<00:26:48.640> such<00:26:48.840> as<00:26:49.440> uh<00:26:50.200> uh<00:26:50.399> users<00:26:50.919> GE<00:26:51.200> location 00:26:51.669 --> 00:26:51.679 align:start position:0% position such as uh uh users GE location 00:26:51.679 --> 00:26:55.029 align:start position:0% position such as uh uh users GE location gets<00:26:51.919> mapped<00:26:52.360> to<00:26:52.960> a<00:26:53.240> particular<00:26:53.960> Nam<00:26:54.360> space<00:26:54.799> in 00:26:55.029 --> 00:26:55.039 align:start position:0% gets mapped to a particular Nam space in 00:26:55.039 --> 00:26:57.950 align:start position:0% gets mapped to a particular Nam space in vaku<00:26:55.399> network<00:26:56.039> and<00:26:56.240> then<00:26:56.840> you<00:26:57.000> can<00:26:57.440> talk<00:26:57.679> to 00:26:57.950 --> 00:26:57.960 align:start position:0% vaku network and then you can talk to 00:26:57.960 --> 00:27:00.870 align:start position:0% vaku network and then you can talk to the<00:26:58.240> room<00:26:58.480> in<00:26:58.640> which<00:26:58.760> you<00:26:58.880> are<00:26:59.679> located<00:27:00.679> quite 00:27:00.870 --> 00:27:00.880 align:start position:0% the room in which you are located quite 00:27:00.880 --> 00:27:02.470 align:start position:0% the room in which you are located quite interesting<00:27:01.360> approach<00:27:01.679> to<00:27:01.840> create<00:27:02.080> a<00:27:02.200> layer 00:27:02.470 --> 00:27:02.480 align:start position:0% interesting approach to create a layer 00:27:02.480 --> 00:27:03.510 align:start position:0% interesting approach to create a layer on<00:27:02.679> top<00:27:02.799> of 00:27:03.510 --> 00:27:03.520 align:start position:0% on top of 00:27:03.520 --> 00:27:06.149 align:start position:0% on top of reality<00:27:04.520> um<00:27:05.080> so<00:27:05.360> today<00:27:05.600> we're<00:27:05.760> going<00:27:05.840> to<00:27:05.960> show 00:27:06.149 --> 00:27:06.159 align:start position:0% reality um so today we're going to show 00:27:06.159 --> 00:27:09.070 align:start position:0% reality um so today we're going to show you<00:27:06.640> some<00:27:06.840> of<00:27:06.960> the<00:27:07.320> examples<00:27:08.320> uh<00:27:08.520> this<00:27:08.679> link 00:27:09.070 --> 00:27:09.080 align:start position:0% you some of the examples uh this link 00:27:09.080 --> 00:27:12.389 align:start position:0% you some of the examples uh this link will<00:27:09.640> lead<00:27:10.039> you<00:27:10.240> to<00:27:10.600> a<00:27:10.799> repository<00:27:11.440> with<00:27:12.000> uh 00:27:12.389 --> 00:27:12.399 align:start position:0% will lead you to a repository with uh 00:27:12.399 --> 00:27:15.630 align:start position:0% will lead you to a repository with uh our<00:27:13.080> examples<00:27:13.960> that<00:27:14.120> where<00:27:14.399> we<00:27:14.919> experiment 00:27:15.630 --> 00:27:15.640 align:start position:0% our examples that where we experiment 00:27:15.640 --> 00:27:18.470 align:start position:0% our examples that where we experiment where<00:27:15.799> we<00:27:15.960> play<00:27:16.200> around<00:27:16.799> and<00:27:17.120> uh<00:27:17.720> as<00:27:17.880> well<00:27:18.080> as 00:27:18.470 --> 00:27:18.480 align:start position:0% where we play around and uh as well as 00:27:18.480 --> 00:27:20.990 align:start position:0% where we play around and uh as well as do<00:27:18.720> something<00:27:19.000> for<00:27:19.240> users<00:27:20.039> I<00:27:20.120> will<00:27:20.320> show<00:27:20.520> you 00:27:20.990 --> 00:27:21.000 align:start position:0% do something for users I will show you 00:27:21.000 --> 00:27:24.350 align:start position:0% do something for users I will show you um<00:27:21.559> an<00:27:21.760> application<00:27:22.240> named<00:27:22.480> body<00:27:22.799> book<00:27:23.320> uh<00:27:23.480> we 00:27:24.350 --> 00:27:24.360 align:start position:0% um an application named body book uh we 00:27:24.360 --> 00:27:26.350 align:start position:0% um an application named body book uh we created<00:27:24.760> it<00:27:24.919> for<00:27:25.159> as<00:27:25.279> a<00:27:25.440> PC<00:27:25.880> just<00:27:26.000> to<00:27:26.120> show 00:27:26.350 --> 00:27:26.360 align:start position:0% created it for as a PC just to show 00:27:26.360 --> 00:27:29.350 align:start position:0% created it for as a PC just to show people<00:27:26.640> around<00:27:27.440> here<00:27:27.640> at<00:27:27.799> Dev 00:27:29.350 --> 00:27:29.360 align:start position:0% people around here at Dev 00:27:29.360 --> 00:27:32.310 align:start position:0% people around here at Dev and<00:27:29.919> uh<00:27:30.320> uh<00:27:30.440> there<00:27:30.559> will<00:27:30.720> be<00:27:30.880> more<00:27:31.320> examples 00:27:32.310 --> 00:27:32.320 align:start position:0% and uh uh there will be more examples 00:27:32.320 --> 00:27:34.190 align:start position:0% and uh uh there will be more examples and<00:27:32.480> we<00:27:32.640> can<00:27:32.880> try<00:27:33.080> to<00:27:33.240> do<00:27:33.399> some<00:27:33.600> programming<00:27:34.120> if 00:27:34.190 --> 00:27:34.200 align:start position:0% and we can try to do some programming if 00:27:34.200 --> 00:27:36.669 align:start position:0% and we can try to do some programming if you<00:27:34.320> are<00:27:34.720> interested<00:27:35.720> otherwise<00:27:36.159> I<00:27:36.200> will<00:27:36.399> just 00:27:36.669 --> 00:27:36.679 align:start position:0% you are interested otherwise I will just 00:27:36.679 --> 00:27:38.990 align:start position:0% you are interested otherwise I will just walk<00:27:36.919> you<00:27:37.080> through<00:27:37.399> some<00:27:37.799> simple<00:27:38.120> onepage 00:27:38.990 --> 00:27:39.000 align:start position:0% walk you through some simple onepage 00:27:39.000 --> 00:27:41.710 align:start position:0% walk you through some simple onepage JavaScript<00:27:39.520> application<00:27:40.120> with<00:27:41.080> uh<00:27:41.279> request 00:27:41.710 --> 00:27:41.720 align:start position:0% JavaScript application with uh request 00:27:41.720 --> 00:27:44.710 align:start position:0% JavaScript application with uh request response<00:27:42.200> protocols<00:27:43.200> uh<00:27:43.360> that<00:27:43.480> are<00:27:43.640> used<00:27:44.640> uh 00:27:44.710 --> 00:27:44.720 align:start position:0% response protocols uh that are used uh 00:27:44.720 --> 00:27:46.310 align:start position:0% response protocols uh that are used uh do<00:27:44.840> you<00:27:44.960> have<00:27:45.120> any<00:27:45.320> questions<00:27:45.640> at<00:27:45.799> this<00:27:45.960> point 00:27:46.310 --> 00:27:46.320 align:start position:0% do you have any questions at this point 00:27:46.320 --> 00:27:49.549 align:start position:0% do you have any questions at this point maybe<00:27:46.640> we<00:27:46.760> can<00:27:47.440> do<00:27:47.640> a<00:27:47.840> quick<00:27:48.279> Q&A<00:27:49.000> before<00:27:49.240> we<00:27:49.399> go 00:27:49.549 --> 00:27:49.559 align:start position:0% maybe we can do a quick Q&A before we go 00:27:49.559 --> 00:27:54.110 align:start position:0% maybe we can do a quick Q&A before we go into<00:27:49.799> some<00:27:50.360> code 00:27:54.110 --> 00:27:54.120 align:start position:0% 00:27:54.120 --> 00:27:56.750 align:start position:0% presentation<00:27:55.120> oh<00:27:55.320> yeah<00:27:55.440> there<00:27:55.559> is<00:27:55.720> a<00:27:55.880> question 00:27:56.750 --> 00:27:56.760 align:start position:0% presentation oh yeah there is a question 00:27:56.760 --> 00:27:58.789 align:start position:0% presentation oh yeah there is a question sorry<00:27:57.760> m 00:27:58.789 --> 00:27:58.799 align:start position:0% sorry m 00:27:58.799 --> 00:28:01.470 align:start position:0% sorry m something<00:27:59.240> specific<00:27:59.640> for<00:27:59.919> Native<00:28:00.320> mobile<00:28:00.640> SDK 00:28:01.470 --> 00:28:01.480 align:start position:0% something specific for Native mobile SDK 00:28:01.480 --> 00:28:05.950 align:start position:0% something specific for Native mobile SDK so<00:28:01.760> do<00:28:01.880> we<00:28:02.000> have<00:28:02.279> a<00:28:02.880> mobile<00:28:03.880> or<00:28:04.039> C<00:28:04.559> or<00:28:04.799> or<00:28:05.000> Swift 00:28:05.950 --> 00:28:05.960 align:start position:0% so do we have a mobile or C or or Swift 00:28:05.960 --> 00:28:07.990 align:start position:0% so do we have a mobile or C or or Swift uh<00:28:06.279> new<00:28:06.440> plans<00:28:06.720> I<00:28:06.799> mean<00:28:07.120> not<00:28:07.320> now<00:28:07.600> we<00:28:07.720> have<00:28:07.840> it 00:28:07.990 --> 00:28:08.000 align:start position:0% uh new plans I mean not now we have it 00:28:08.000 --> 00:28:11.710 align:start position:0% uh new plans I mean not now we have it in<00:28:08.159> Plants<00:28:08.840> yes<00:28:09.720> uh<00:28:10.480> JavaScript<00:28:11.080> version<00:28:11.519> can 00:28:11.710 --> 00:28:11.720 align:start position:0% in Plants yes uh JavaScript version can 00:28:11.720 --> 00:28:14.070 align:start position:0% in Plants yes uh JavaScript version can be<00:28:11.880> used<00:28:12.320> in<00:28:12.519> react<00:28:12.840> native<00:28:13.519> we<00:28:13.679> did<00:28:13.840> some 00:28:14.070 --> 00:28:14.080 align:start position:0% be used in react native we did some 00:28:14.080 --> 00:28:18.029 align:start position:0% be used in react native we did some bindings<00:28:15.080> um<00:28:15.519> we<00:28:15.640> didn't<00:28:16.279> prove<00:28:16.600> it<00:28:17.039> working 00:28:18.029 --> 00:28:18.039 align:start position:0% bindings um we didn't prove it working 00:28:18.039 --> 00:28:20.590 align:start position:0% bindings um we didn't prove it working reliably<00:28:19.039> so<00:28:19.559> this<00:28:19.720> is<00:28:19.880> also<00:28:20.159> work<00:28:20.360> in 00:28:20.590 --> 00:28:20.600 align:start position:0% reliably so this is also work in 00:28:20.600 --> 00:28:24.230 align:start position:0% reliably so this is also work in progress<00:28:21.399> we<00:28:21.600> had<00:28:21.799> some<00:28:22.279> go<00:28:22.880> uh<00:28:23.559> vaku<00:28:24.000> being 00:28:24.230 --> 00:28:24.240 align:start position:0% progress we had some go uh vaku being 00:28:24.240 --> 00:28:27.029 align:start position:0% progress we had some go uh vaku being adapted<00:28:24.679> for<00:28:25.440> running<00:28:26.039> is<00:28:26.240> also<00:28:26.519> in<00:28:26.720> react 00:28:27.029 --> 00:28:27.039 align:start position:0% adapted for running is also in react 00:28:27.039 --> 00:28:30.230 align:start position:0% adapted for running is also in react native<00:28:27.519> or<00:28:28.600> uh<00:28:28.760> other<00:28:29.039> stuff<00:28:29.360> but<00:28:29.760> uh<00:28:29.960> also 00:28:30.230 --> 00:28:30.240 align:start position:0% native or uh other stuff but uh also 00:28:30.240 --> 00:28:35.230 align:start position:0% native or uh other stuff but uh also status<00:28:30.720> is<00:28:31.000> using<00:28:32.240> um<00:28:33.240> vaku<00:28:34.200> as<00:28:34.360> well<00:28:34.799> but<00:28:35.120> uh 00:28:35.230 --> 00:28:35.240 align:start position:0% status is using um vaku as well but uh 00:28:35.240 --> 00:28:36.950 align:start position:0% status is using um vaku as well but uh they<00:28:35.360> did<00:28:35.720> little<00:28:35.919> bit<00:28:36.080> more<00:28:36.279> work<00:28:36.519> than<00:28:36.760> just 00:28:36.950 --> 00:28:36.960 align:start position:0% they did little bit more work than just 00:28:36.960 --> 00:28:39.269 align:start position:0% they did little bit more work than just you<00:28:37.080> know<00:28:37.240> installing<00:28:37.720> it<00:28:38.240> so<00:28:38.559> it<00:28:38.679> is<00:28:38.880> work<00:28:39.080> in 00:28:39.269 --> 00:28:39.279 align:start position:0% you know installing it so it is work in 00:28:39.279 --> 00:28:40.549 align:start position:0% you know installing it so it is work in progress 00:28:40.549 --> 00:28:40.559 align:start position:0% progress 00:28:40.559 --> 00:28:44.310 align:start position:0% progress yes<00:28:41.559> so<00:28:41.840> please<00:28:42.600> is<00:28:42.720> there<00:28:42.840> a<00:28:43.000> public<00:28:43.320> network 00:28:44.310 --> 00:28:44.320 align:start position:0% yes so please is there a public network 00:28:44.320 --> 00:28:46.990 align:start position:0% yes so please is there a public network uh<00:28:44.840> that<00:28:45.159> the<00:28:45.440> the<00:28:45.559> waku<00:28:45.880> nodes<00:28:46.120> run<00:28:46.360> on<00:28:46.720> or<00:28:46.919> are 00:28:46.990 --> 00:28:47.000 align:start position:0% uh that the the waku nodes run on or are 00:28:47.000 --> 00:28:48.509 align:start position:0% uh that the the waku nodes run on or are you<00:28:47.159> expected<00:28:47.440> to<00:28:47.559> run<00:28:47.720> your<00:28:47.840> own<00:28:48.000> nodes<00:28:48.320> for 00:28:48.509 --> 00:28:48.519 align:start position:0% you expected to run your own nodes for 00:28:48.519 --> 00:28:50.430 align:start position:0% you expected to run your own nodes for the<00:28:48.679> applications<00:28:49.120> that<00:28:49.200> you<00:28:49.320> run<00:28:50.000> yeah<00:28:50.159> so 00:28:50.430 --> 00:28:50.440 align:start position:0% the applications that you run yeah so 00:28:50.440 --> 00:28:52.310 align:start position:0% the applications that you run yeah so the<00:28:50.559> main<00:28:50.799> difference<00:28:51.240> between<00:28:51.640> waku<00:28:52.159> and 00:28:52.310 --> 00:28:52.320 align:start position:0% the main difference between waku and 00:28:52.320 --> 00:28:54.909 align:start position:0% the main difference between waku and let's<00:28:52.480> say<00:28:52.640> lip2p<00:28:53.240> as<00:28:53.320> I<00:28:53.480> mentioned<00:28:54.159> lip2p<00:28:54.840> is 00:28:54.909 --> 00:28:54.919 align:start position:0% let's say lip2p as I mentioned lip2p is 00:28:54.919 --> 00:28:57.470 align:start position:0% let's say lip2p as I mentioned lip2p is a<00:28:55.080> stack<00:28:55.399> that<00:28:55.519> we<00:28:55.640> are<00:28:55.840> using<00:28:56.440> and<00:28:56.640> anyone<00:28:57.039> can 00:28:57.470 --> 00:28:57.480 align:start position:0% a stack that we are using and anyone can 00:28:57.480 --> 00:28:59.990 align:start position:0% a stack that we are using and anyone can let's<00:28:57.640> say<00:28:58.480> me<00:28:58.799> you<00:28:59.080> we<00:28:59.399> together<00:28:59.679> want<00:28:59.880> to 00:28:59.990 --> 00:29:00.000 align:start position:0% let's say me you we together want to 00:29:00.000 --> 00:29:01.909 align:start position:0% let's say me you we together want to build<00:29:00.240> a<00:29:00.360> network<00:29:00.880> we<00:29:01.000> create<00:29:01.320> an<00:29:01.480> application 00:29:01.909 --> 00:29:01.919 align:start position:0% build a network we create an application 00:29:01.919 --> 00:29:05.190 align:start position:0% build a network we create an application out<00:29:02.080> of<00:29:02.279> Lip<00:29:03.080> lip<00:29:03.679> right<00:29:04.279> uh<00:29:04.440> what<00:29:04.600> waku<00:29:04.960> does 00:29:05.190 --> 00:29:05.200 align:start position:0% out of Lip lip right uh what waku does 00:29:05.200 --> 00:29:07.590 align:start position:0% out of Lip lip right uh what waku does differently<00:29:05.760> is<00:29:05.880> that<00:29:06.200> it<00:29:06.399> provides<00:29:06.840> a<00:29:07.039> set<00:29:07.200> of 00:29:07.590 --> 00:29:07.600 align:start position:0% differently is that it provides a set of 00:29:07.600 --> 00:29:09.669 align:start position:0% differently is that it provides a set of protocols<00:29:08.200> like<00:29:08.480> solutions<00:29:09.120> to<00:29:09.320> some 00:29:09.669 --> 00:29:09.679 align:start position:0% protocols like solutions to some 00:29:09.679 --> 00:29:11.350 align:start position:0% protocols like solutions to some problems<00:29:10.039> that<00:29:10.200> we<00:29:10.360> observe<00:29:10.799> and<00:29:11.000> we<00:29:11.120> want 00:29:11.350 --> 00:29:11.360 align:start position:0% problems that we observe and we want 00:29:11.360 --> 00:29:14.710 align:start position:0% problems that we observe and we want users<00:29:11.840> to<00:29:12.600> uh<00:29:12.760> have<00:29:12.960> dealt<00:29:13.320> with<00:29:14.120> as<00:29:14.279> well<00:29:14.519> as 00:29:14.710 --> 00:29:14.720 align:start position:0% users to uh have dealt with as well as 00:29:14.720 --> 00:29:16.389 align:start position:0% users to uh have dealt with as well as we<00:29:14.840> have<00:29:14.960> a<00:29:15.080> running<00:29:15.440> Network<00:29:16.120> which<00:29:16.240> is 00:29:16.389 --> 00:29:16.399 align:start position:0% we have a running Network which is 00:29:16.399 --> 00:29:19.750 align:start position:0% we have a running Network which is called<00:29:16.720> the<00:29:16.960> waku<00:29:17.279> network<00:29:18.039> tww<00:29:19.039> and<00:29:19.519> uh<00:29:19.679> I 00:29:19.750 --> 00:29:19.760 align:start position:0% called the waku network tww and uh I 00:29:19.760 --> 00:29:21.430 align:start position:0% called the waku network tww and uh I will<00:29:19.919> show<00:29:20.159> you<00:29:20.360> how<00:29:20.480> to<00:29:20.679> join<00:29:20.960> it<00:29:21.159> let's<00:29:21.320> say 00:29:21.430 --> 00:29:21.440 align:start position:0% will show you how to join it let's say 00:29:21.440 --> 00:29:24.389 align:start position:0% will show you how to join it let's say from<00:29:21.640> JavaScript<00:29:22.120> cdk<00:29:22.919> in<00:29:23.320> a<00:29:23.480> couple<00:29:23.960> of<00:29:24.159> lines 00:29:24.389 --> 00:29:24.399 align:start position:0% from JavaScript cdk in a couple of lines 00:29:24.399 --> 00:29:27.269 align:start position:0% from JavaScript cdk in a couple of lines of<00:29:24.559> code<00:29:25.440> and<00:29:25.799> you<00:29:25.919> can<00:29:26.159> hook<00:29:26.399> in<00:29:26.720> your<00:29:27.000> own 00:29:27.269 --> 00:29:27.279 align:start position:0% of code and you can hook in your own 00:29:27.279 --> 00:29:28.669 align:start position:0% of code and you can hook in your own nodes<00:29:27.640> to<00:29:27.840> each 00:29:28.669 --> 00:29:28.679 align:start position:0% nodes to each 00:29:28.679 --> 00:29:30.630 align:start position:0% nodes to each or<00:29:28.919> use<00:29:29.120> it<00:29:29.279> as<00:29:29.360> a<00:29:29.519> signaling<00:29:30.000> note<00:29:30.320> let's<00:29:30.480> say 00:29:30.630 --> 00:29:30.640 align:start position:0% or use it as a signaling note let's say 00:29:30.640 --> 00:29:32.549 align:start position:0% or use it as a signaling note let's say to<00:29:31.000> create<00:29:31.320> your<00:29:31.480> own<00:29:31.679> sub<00:29:31.960> Network<00:29:32.399> or 00:29:32.549 --> 00:29:32.559 align:start position:0% to create your own sub Network or 00:29:32.559 --> 00:29:34.830 align:start position:0% to create your own sub Network or something<00:29:33.000> like<00:29:33.200> that 00:29:34.830 --> 00:29:34.840 align:start position:0% something like that 00:29:34.840 --> 00:29:37.509 align:start position:0% something like that yes<00:29:35.840> any 00:29:37.509 --> 00:29:37.519 align:start position:0% yes any 00:29:37.519 --> 00:29:40.070 align:start position:0% yes any more<00:29:38.519> okay<00:29:39.000> um<00:29:39.159> so<00:29:39.399> I<00:29:39.519> going<00:29:39.600> to<00:29:39.720> go<00:29:39.840> to<00:29:39.960> my 00:29:40.070 --> 00:29:40.080 align:start position:0% more okay um so I going to go to my 00:29:40.080 --> 00:29:42.990 align:start position:0% more okay um so I going to go to my laptop<00:29:40.559> and<00:29:40.880> uh<00:29:41.440> let's<00:29:41.640> see<00:29:41.960> what<00:29:42.120> we<00:29:42.240> can<00:29:42.640> do 00:29:42.990 --> 00:29:43.000 align:start position:0% laptop and uh let's see what we can do 00:29:43.000 --> 00:29:50.230 align:start position:0% laptop and uh let's see what we can do with<00:29:43.360> the<00:29:43.519> code 00:29:50.230 --> 00:29:50.240 align:start position:0% 00:29:50.240 --> 00:29:54.509 align:start position:0% today<00:29:51.240> so<00:29:51.600> this<00:29:51.760> one<00:29:52.200> is<00:29:52.840> uh<00:29:53.080> for<00:29:53.880> uh<00:29:54.120> example 00:29:54.509 --> 00:29:54.519 align:start position:0% today so this one is uh for uh example 00:29:54.519 --> 00:29:58.789 align:start position:0% today so this one is uh for uh example with<00:29:54.679> rust<00:29:55.480> it<00:29:55.640> uses<00:29:56.320> n<00:29:56.679> version<00:29:57.159> of<00:29:57.559> uh 00:29:58.789 --> 00:29:58.799 align:start position:0% with rust it uses n version of uh 00:29:58.799 --> 00:30:03.350 align:start position:0% with rust it uses n version of uh um<00:29:59.799> of<00:30:00.080> of<00:30:00.640> vaku<00:30:01.640> uh<00:30:01.760> some<00:30:02.000> bindings<00:30:02.799> and<00:30:03.200> uh 00:30:03.350 --> 00:30:03.360 align:start position:0% um of of vaku uh some bindings and uh 00:30:03.360 --> 00:30:05.149 align:start position:0% um of of vaku uh some bindings and uh you<00:30:03.480> can<00:30:03.640> scan<00:30:03.960> it<00:30:04.159> and<00:30:04.360> see<00:30:04.760> how<00:30:04.919> it<00:30:05.000> is 00:30:05.149 --> 00:30:05.159 align:start position:0% you can scan it and see how it is 00:30:05.159 --> 00:30:07.909 align:start position:0% you can scan it and see how it is implemented<00:30:05.640> later<00:30:05.919> on<00:30:06.240> Ian<00:30:06.600> will<00:30:06.840> go<00:30:07.240> and 00:30:07.909 --> 00:30:07.919 align:start position:0% implemented later on Ian will go and 00:30:07.919 --> 00:30:10.389 align:start position:0% implemented later on Ian will go and present<00:30:08.360> himself<00:30:09.120> the<00:30:09.279> code<00:30:09.640> and<00:30:10.039> walk<00:30:10.240> you 00:30:10.389 --> 00:30:10.399 align:start position:0% present himself the code and walk you 00:30:10.399 --> 00:30:13.070 align:start position:0% present himself the code and walk you through<00:30:10.679> it 00:30:13.070 --> 00:30:13.080 align:start position:0% through it 00:30:13.080 --> 00:30:16.710 align:start position:0% through it um<00:30:14.080> so<00:30:14.559> uh<00:30:14.679> body<00:30:15.000> book<00:30:15.399> uh<00:30:15.519> if<00:30:15.640> you<00:30:15.760> scan<00:30:16.559> uh 00:30:16.710 --> 00:30:16.720 align:start position:0% um so uh body book uh if you scan uh 00:30:16.720 --> 00:30:18.789 align:start position:0% um so uh body book uh if you scan uh this<00:30:17.120> will<00:30:17.360> lead<00:30:17.559> you<00:30:17.679> to<00:30:17.799> the<00:30:17.919> source<00:30:18.240> code<00:30:18.519> of 00:30:18.789 --> 00:30:18.799 align:start position:0% this will lead you to the source code of 00:30:18.799 --> 00:30:23.029 align:start position:0% this will lead you to the source code of the<00:30:19.640> simple<00:30:20.640> onepage<00:30:21.360> application<00:30:22.360> otherwise 00:30:23.029 --> 00:30:23.039 align:start position:0% the simple onepage application otherwise 00:30:23.039 --> 00:30:26.669 align:start position:0% the simple onepage application otherwise you<00:30:23.159> can<00:30:23.360> visit<00:30:23.679> body<00:30:24.000> book.<00:30:24.760> fun<00:30:25.760> and<00:30:26.200> uh<00:30:26.519> what 00:30:26.669 --> 00:30:26.679 align:start position:0% you can visit body book. fun and uh what 00:30:26.679 --> 00:30:28.549 align:start position:0% you can visit body book. fun and uh what it<00:30:26.960> does<00:30:27.399> is<00:30:27.600> that 00:30:28.549 --> 00:30:28.559 align:start position:0% it does is that 00:30:28.559 --> 00:30:31.269 align:start position:0% it does is that once<00:30:28.720> you<00:30:28.960> open<00:30:29.240> it<00:30:29.480> you<00:30:29.559> can<00:30:29.799> create<00:30:30.640> um<00:30:31.080> a 00:30:31.269 --> 00:30:31.279 align:start position:0% once you open it you can create um a 00:30:31.279 --> 00:30:34.070 align:start position:0% once you open it you can create um a book<00:30:32.279> and<00:30:32.399> then<00:30:32.600> later<00:30:32.880> on<00:30:33.360> at<00:30:33.480> the<00:30:33.679> conference 00:30:34.070 --> 00:30:34.080 align:start position:0% book and then later on at the conference 00:30:34.080 --> 00:30:35.789 align:start position:0% book and then later on at the conference or<00:30:34.279> somewhere<00:30:34.679> you<00:30:34.760> can<00:30:35.000> come<00:30:35.159> to<00:30:35.360> people<00:30:35.640> and 00:30:35.789 --> 00:30:35.799 align:start position:0% or somewhere you can come to people and 00:30:35.799 --> 00:30:38.230 align:start position:0% or somewhere you can come to people and ask<00:30:36.080> them<00:30:36.240> to<00:30:36.360> sign<00:30:37.200> uh<00:30:37.279> your<00:30:37.519> book<00:30:37.880> like 00:30:38.230 --> 00:30:38.240 align:start position:0% ask them to sign uh your book like 00:30:38.240 --> 00:30:40.310 align:start position:0% ask them to sign uh your book like collect<00:30:38.600> signatures<00:30:39.440> these<00:30:39.600> signatures<00:30:40.120> will 00:30:40.310 --> 00:30:40.320 align:start position:0% collect signatures these signatures will 00:30:40.320 --> 00:30:42.909 align:start position:0% collect signatures these signatures will be<00:30:40.600> created<00:30:41.039> from<00:30:41.279> a<00:30:41.440> wallet<00:30:42.320> right<00:30:42.440> so<00:30:42.760> let's 00:30:42.909 --> 00:30:42.919 align:start position:0% be created from a wallet right so let's 00:30:42.919 --> 00:30:45.230 align:start position:0% be created from a wallet right so let's say<00:30:43.080> a<00:30:43.200> metamask<00:30:43.760> wallet<00:30:44.080> or<00:30:44.279> something<00:30:45.080> and 00:30:45.230 --> 00:30:45.240 align:start position:0% say a metamask wallet or something and 00:30:45.240 --> 00:30:46.710 align:start position:0% say a metamask wallet or something and the<00:30:45.399> interesting<00:30:45.960> point<00:30:46.240> about<00:30:46.519> this 00:30:46.710 --> 00:30:46.720 align:start position:0% the interesting point about this 00:30:46.720 --> 00:30:48.509 align:start position:0% the interesting point about this application<00:30:47.360> is<00:30:47.559> that<00:30:47.720> the<00:30:47.840> signatures<00:30:48.360> will 00:30:48.509 --> 00:30:48.519 align:start position:0% application is that the signatures will 00:30:48.519 --> 00:30:50.590 align:start position:0% application is that the signatures will be<00:30:48.679> exchanged<00:30:49.120> through<00:30:49.360> waku<00:30:50.080> and<00:30:50.240> they<00:30:50.320> won't 00:30:50.590 --> 00:30:50.600 align:start position:0% be exchanged through waku and they won't 00:30:50.600 --> 00:30:52.950 align:start position:0% be exchanged through waku and they won't be<00:30:50.720> committed<00:30:51.120> to<00:30:51.320> the<00:30:51.600> to<00:30:51.720> the<00:30:51.960> blockchain 00:30:52.950 --> 00:30:52.960 align:start position:0% be committed to the to the blockchain 00:30:52.960 --> 00:30:54.590 align:start position:0% be committed to the to the blockchain hence<00:30:53.440> there<00:30:53.600> will<00:30:53.760> be<00:30:54.000> like<00:30:54.159> an<00:30:54.320> easy 00:30:54.590 --> 00:30:54.600 align:start position:0% hence there will be like an easy 00:30:54.600 --> 00:30:57.310 align:start position:0% hence there will be like an easy propagation<00:30:55.240> of<00:30:55.639> uh<00:30:55.799> this<00:30:56.120> information<00:30:57.120> and 00:30:57.310 --> 00:30:57.320 align:start position:0% propagation of uh this information and 00:30:57.320 --> 00:30:59.389 align:start position:0% propagation of uh this information and it<00:30:57.399> will<00:30:57.559> be<00:30:57.639> stored<00:30:58.120> in<00:30:58.320> the<00:30:58.799> in<00:30:58.919> the<00:30:59.039> store 00:30:59.389 --> 00:30:59.399 align:start position:0% it will be stored in the in the store 00:30:59.399 --> 00:31:02.190 align:start position:0% it will be stored in the in the store protocols<00:30:59.880> that<00:31:00.320> Ian<00:31:00.639> mentioned<00:31:01.120> about<00:31:01.880> so 00:31:02.190 --> 00:31:02.200 align:start position:0% protocols that Ian mentioned about so 00:31:02.200 --> 00:31:04.950 align:start position:0% protocols that Ian mentioned about so here<00:31:02.480> we<00:31:02.600> have<00:31:02.840> like<00:31:03.000> a<00:31:03.120> couple<00:31:03.360> of<00:31:03.919> U<00:31:04.320> you<00:31:04.480> know 00:31:04.950 --> 00:31:04.960 align:start position:0% here we have like a couple of U you know 00:31:04.960 --> 00:31:07.590 align:start position:0% here we have like a couple of U you know just<00:31:05.360> Just<00:31:06.039> Books<00:31:06.519> whatever<00:31:07.240> and<00:31:07.360> there<00:31:07.480> are 00:31:07.590 --> 00:31:07.600 align:start position:0% just Just Books whatever and there are 00:31:07.600 --> 00:31:10.590 align:start position:0% just Just Books whatever and there are some<00:31:07.760> signatures<00:31:08.559> attached<00:31:09.559> um<00:31:10.080> yeah<00:31:10.279> so<00:31:10.480> if 00:31:10.590 --> 00:31:10.600 align:start position:0% some signatures attached um yeah so if 00:31:10.600 --> 00:31:12.549 align:start position:0% some signatures attached um yeah so if you<00:31:10.720> create<00:31:11.120> it<00:31:11.360> it's<00:31:11.480> going<00:31:11.600> to<00:31:11.760> appear<00:31:12.200> here 00:31:12.549 --> 00:31:12.559 align:start position:0% you create it it's going to appear here 00:31:12.559 --> 00:31:16.350 align:start position:0% you create it it's going to appear here and<00:31:13.120> uh<00:31:14.120> yeah<00:31:14.399> so<00:31:15.279> this<00:31:15.440> is<00:31:15.600> very<00:31:15.799> simplistic 00:31:16.350 --> 00:31:16.360 align:start position:0% and uh yeah so this is very simplistic 00:31:16.360 --> 00:31:18.950 align:start position:0% and uh yeah so this is very simplistic application<00:31:17.120> but<00:31:17.320> still<00:31:17.840> uh<00:31:18.039> very<00:31:18.480> use<00:31:18.760> case 00:31:18.950 --> 00:31:18.960 align:start position:0% application but still uh very use case 00:31:18.960 --> 00:31:20.909 align:start position:0% application but still uh very use case very<00:31:19.120> interesting<00:31:19.519> use 00:31:20.909 --> 00:31:20.919 align:start position:0% very interesting use 00:31:20.919 --> 00:31:24.509 align:start position:0% very interesting use case<00:31:21.919> Okay<00:31:22.279> so<00:31:23.000> uh<00:31:23.279> then 00:31:24.509 --> 00:31:24.519 align:start position:0% case Okay so uh then 00:31:24.519 --> 00:31:27.350 align:start position:0% case Okay so uh then uh<00:31:25.519> uh<00:31:25.639> you<00:31:25.760> can<00:31:25.919> run<00:31:26.120> a<00:31:26.279> note<00:31:26.679> this<00:31:26.799> is<00:31:26.960> another 00:31:27.350 --> 00:31:27.360 align:start position:0% uh uh you can run a note this is another 00:31:27.360 --> 00:31:29.269 align:start position:0% uh uh you can run a note this is another application 00:31:29.269 --> 00:31:29.279 align:start position:0% application 00:31:29.279 --> 00:31:32.590 align:start position:0% application example<00:31:29.799> of<00:31:30.320> how<00:31:30.679> waku<00:31:31.080> can<00:31:31.200> be<00:31:31.320> used<00:31:32.240> you<00:31:32.399> can 00:31:32.590 --> 00:31:32.600 align:start position:0% example of how waku can be used you can 00:31:32.600 --> 00:31:35.549 align:start position:0% example of how waku can be used you can be<00:31:33.159> uh<00:31:33.360> just<00:31:33.840> a<00:31:33.960> node<00:31:34.240> operator<00:31:34.799> so<00:31:35.440> uh 00:31:35.549 --> 00:31:35.559 align:start position:0% be uh just a node operator so uh 00:31:35.559 --> 00:31:37.310 align:start position:0% be uh just a node operator so uh contributing<00:31:36.159> to<00:31:36.320> the<00:31:36.440> network<00:31:36.880> let's<00:31:37.039> say<00:31:37.240> if 00:31:37.310 --> 00:31:37.320 align:start position:0% contributing to the network let's say if 00:31:37.320 --> 00:31:39.549 align:start position:0% contributing to the network let's say if you<00:31:37.480> have<00:31:37.600> a<00:31:37.760> spare<00:31:38.240> Raspberry<00:31:38.760> Pi<00:31:38.960> for<00:31:39.320> gigs 00:31:39.549 --> 00:31:39.559 align:start position:0% you have a spare Raspberry Pi for gigs 00:31:39.559 --> 00:31:43.389 align:start position:0% you have a spare Raspberry Pi for gigs of<00:31:39.720> RAM<00:31:39.919> or<00:31:40.320> something<00:31:41.320> just<00:31:41.720> uh<00:31:41.880> opening<00:31:42.880> uh<00:31:43.240> a 00:31:43.389 --> 00:31:43.399 align:start position:0% of RAM or something just uh opening uh a 00:31:43.399 --> 00:31:46.549 align:start position:0% of RAM or something just uh opening uh a Docker<00:31:44.320> and<00:31:44.720> doing<00:31:45.000> one<00:31:45.320> line<00:31:46.039> can<00:31:46.200> already 00:31:46.549 --> 00:31:46.559 align:start position:0% Docker and doing one line can already 00:31:46.559 --> 00:31:49.950 align:start position:0% Docker and doing one line can already contribute<00:31:47.000> to<00:31:47.080> the<00:31:47.240> network<00:31:47.880> quite<00:31:48.080> a<00:31:48.600> bit<00:31:49.600> uh 00:31:49.950 --> 00:31:49.960 align:start position:0% contribute to the network quite a bit uh 00:31:49.960 --> 00:31:51.789 align:start position:0% contribute to the network quite a bit uh though<00:31:50.200> I'm<00:31:50.399> line<00:31:50.639> it's<00:31:50.760> not<00:31:50.960> one<00:31:51.200> line<00:31:51.440> it's 00:31:51.789 --> 00:31:51.799 align:start position:0% though I'm line it's not one line it's 00:31:51.799 --> 00:31:56.230 align:start position:0% though I'm line it's not one line it's uh<00:31:52.080> more<00:31:52.440> of<00:31:53.200> of<00:31:53.360> one<00:31:53.600> line<00:31:54.240> to<00:31:54.440> run<00:31:54.639> in<00:31:54.840> your<00:31:55.639> um 00:31:56.230 --> 00:31:56.240 align:start position:0% uh more of of one line to run in your um 00:31:56.240 --> 00:31:59.190 align:start position:0% uh more of of one line to run in your um terminal<00:31:57.240> and<00:31:57.639> uh<00:31:58.080> now<00:31:58.399> if<00:31:58.519> you<00:31:58.720> open<00:31:59.039> this 00:31:59.190 --> 00:31:59.200 align:start position:0% terminal and uh now if you open this 00:31:59.200 --> 00:32:02.149 align:start position:0% terminal and uh now if you open this link<00:31:59.559> it<00:31:59.679> will<00:32:00.000> show<00:32:00.320> you<00:32:00.679> a<00:32:01.000> basic<00:32:01.600> JavaScript 00:32:02.149 --> 00:32:02.159 align:start position:0% link it will show you a basic JavaScript 00:32:02.159 --> 00:32:04.310 align:start position:0% link it will show you a basic JavaScript application<00:32:03.000> it<00:32:03.120> will<00:32:03.240> lead<00:32:03.440> you<00:32:03.559> to<00:32:03.799> this<00:32:04.159> to 00:32:04.310 --> 00:32:04.320 align:start position:0% application it will lead you to this to 00:32:04.320 --> 00:32:08.789 align:start position:0% application it will lead you to this to the<00:32:04.480> code<00:32:05.039> which<00:32:05.200> I<00:32:05.279> will<00:32:05.880> go<00:32:06.120> show<00:32:06.760> now<00:32:07.760> um<00:32:08.600> I 00:32:08.789 --> 00:32:08.799 align:start position:0% the code which I will go show now um I 00:32:08.799 --> 00:32:10.629 align:start position:0% the code which I will go show now um I hope<00:32:09.000> you<00:32:09.159> see<00:32:09.399> it 00:32:10.629 --> 00:32:10.639 align:start position:0% hope you see it 00:32:10.639 --> 00:32:13.590 align:start position:0% hope you see it well<00:32:11.639> yeah<00:32:12.279> is<00:32:12.360> it<00:32:12.480> readable<00:32:13.320> should<00:32:13.480> I 00:32:13.590 --> 00:32:13.600 align:start position:0% well yeah is it readable should I 00:32:13.600 --> 00:32:15.350 align:start position:0% well yeah is it readable should I increase<00:32:13.919> it<00:32:14.039> a 00:32:15.350 --> 00:32:15.360 align:start position:0% increase it a 00:32:15.360 --> 00:32:17.870 align:start position:0% increase it a bit<00:32:16.360> okay<00:32:16.840> A 00:32:17.870 --> 00:32:17.880 align:start position:0% bit okay A 00:32:17.880 --> 00:32:23.950 align:start position:0% bit okay A bit<00:32:18.880> um<00:32:19.799> this<00:32:19.960> is<00:32:20.679> just<00:32:21.799> single<00:32:22.799> one<00:32:23.440> file 00:32:23.950 --> 00:32:23.960 align:start position:0% bit um this is just single one file 00:32:23.960 --> 00:32:26.269 align:start position:0% bit um this is just single one file application<00:32:24.679> which<00:32:24.880> consumes<00:32:25.519> JavaScript 00:32:26.269 --> 00:32:26.279 align:start position:0% application which consumes JavaScript 00:32:26.279 --> 00:32:28.430 align:start position:0% application which consumes JavaScript cdk<00:32:27.279> and<00:32:27.720> uh 00:32:28.430 --> 00:32:28.440 align:start position:0% cdk and uh 00:32:28.440 --> 00:32:31.149 align:start position:0% cdk and uh uh<00:32:29.480> uh 00:32:31.149 --> 00:32:31.159 align:start position:0% uh uh 00:32:31.159 --> 00:32:34.549 align:start position:0% uh uh you<00:32:32.159> have<00:32:32.320> to<00:32:32.519> create<00:32:32.840> an<00:32:33.080> instance<00:32:33.559> of<00:32:33.720> a<00:32:33.880> node 00:32:34.549 --> 00:32:34.559 align:start position:0% you have to create an instance of a node 00:32:34.559 --> 00:32:37.830 align:start position:0% you have to create an instance of a node first<00:32:35.559> right<00:32:35.960> so<00:32:36.360> hence<00:32:37.039> uh<00:32:37.200> this<00:32:37.440> create 00:32:37.830 --> 00:32:37.840 align:start position:0% first right so hence uh this create 00:32:37.840 --> 00:32:40.990 align:start position:0% first right so hence uh this create light<00:32:38.159> node<00:32:38.840> function<00:32:39.279> is<00:32:39.440> used<00:32:40.360> uh<00:32:40.519> it<00:32:40.840> it 00:32:40.990 --> 00:32:41.000 align:start position:0% light node function is used uh it it 00:32:41.000 --> 00:32:43.269 align:start position:0% light node function is used uh it it accepts<00:32:41.679> like<00:32:41.880> different<00:32:42.240> parameters<00:32:42.919> there 00:32:43.269 --> 00:32:43.279 align:start position:0% accepts like different parameters there 00:32:43.279 --> 00:32:46.029 align:start position:0% accepts like different parameters there you<00:32:43.480> can<00:32:44.080> pass<00:32:44.840> particular<00:32:45.360> coordinates<00:32:45.919> of 00:32:46.029 --> 00:32:46.039 align:start position:0% you can pass particular coordinates of 00:32:46.039 --> 00:32:49.149 align:start position:0% you can pass particular coordinates of the<00:32:46.159> network<00:32:46.600> that<00:32:46.720> you<00:32:46.840> want<00:32:47.000> to<00:32:47.159> use<00:32:47.840> if<00:32:48.320> uh 00:32:49.149 --> 00:32:49.159 align:start position:0% the network that you want to use if uh 00:32:49.159 --> 00:32:52.190 align:start position:0% the network that you want to use if uh not<00:32:49.559> default<00:32:50.039> network<00:32:50.639> is<00:32:50.840> in<00:32:51.039> use<00:32:51.880> so<00:32:52.080> by 00:32:52.190 --> 00:32:52.200 align:start position:0% not default network is in use so by 00:32:52.200 --> 00:32:54.110 align:start position:0% not default network is in use so by default<00:32:52.519> Network<00:32:52.919> I<00:32:53.000> inan<00:32:53.279> here 00:32:54.110 --> 00:32:54.120 align:start position:0% default Network I inan here 00:32:54.120 --> 00:32:56.870 align:start position:0% default Network I inan here tww<00:32:55.120> and<00:32:55.480> if<00:32:55.600> we<00:32:55.720> want<00:32:55.880> to<00:32:56.000> use<00:32:56.159> a<00:32:56.360> default<00:32:56.679> set 00:32:56.870 --> 00:32:56.880 align:start position:0% tww and if we want to use a default set 00:32:56.880 --> 00:32:59.509 align:start position:0% tww and if we want to use a default set of<00:32:57.080> configuration<00:32:57.679> which<00:32:57.880> just<00:32:58.039> pass<00:32:58.279> default 00:32:59.509 --> 00:32:59.519 align:start position:0% of configuration which just pass default 00:32:59.519 --> 00:33:03.149 align:start position:0% of configuration which just pass default bootstrap<00:33:00.519> other<00:33:00.799> thing<00:33:01.200> that<00:33:01.600> uh<00:33:01.799> vaku<00:33:02.799> has 00:33:03.149 --> 00:33:03.159 align:start position:0% bootstrap other thing that uh vaku has 00:33:03.159 --> 00:33:07.350 align:start position:0% bootstrap other thing that uh vaku has in<00:33:03.399> it<00:33:03.840> is<00:33:04.840> um<00:33:05.639> uh<00:33:05.919> the<00:33:06.039> message<00:33:06.559> the<00:33:06.880> the<00:33:07.000> data 00:33:07.350 --> 00:33:07.360 align:start position:0% in it is um uh the message the the data 00:33:07.360 --> 00:33:09.950 align:start position:0% in it is um uh the message the the data get<00:33:07.679> right<00:33:08.039> it<00:33:08.440> it<00:33:08.600> gets<00:33:08.960> propagated<00:33:09.720> through 00:33:09.950 --> 00:33:09.960 align:start position:0% get right it it gets propagated through 00:33:09.960 --> 00:33:11.629 align:start position:0% get right it it gets propagated through the<00:33:10.120> network<00:33:10.960> and<00:33:11.120> there<00:33:11.240> are<00:33:11.399> some 00:33:11.629 --> 00:33:11.639 align:start position:0% the network and there are some 00:33:11.639 --> 00:33:14.789 align:start position:0% the network and there are some properties<00:33:12.639> uh<00:33:13.000> of<00:33:13.440> this<00:33:13.840> uh<00:33:14.159> data<00:33:14.480> packet 00:33:14.789 --> 00:33:14.799 align:start position:0% properties uh of this uh data packet 00:33:14.799 --> 00:33:19.909 align:start position:0% properties uh of this uh data packet that<00:33:15.000> help<00:33:15.679> uh<00:33:15.880> to<00:33:16.639> do<00:33:17.240> routing<00:33:18.240> and<00:33:18.799> uh<00:33:19.559> one<00:33:19.720> of 00:33:19.909 --> 00:33:19.919 align:start position:0% that help uh to do routing and uh one of 00:33:19.919 --> 00:33:21.950 align:start position:0% that help uh to do routing and uh one of them<00:33:20.120> is<00:33:20.279> content<00:33:20.720> topic<00:33:21.159> and<00:33:21.440> uh<00:33:21.559> content 00:33:21.950 --> 00:33:21.960 align:start position:0% them is content topic and uh content 00:33:21.960 --> 00:33:23.789 align:start position:0% them is content topic and uh content topic<00:33:22.240> should<00:33:22.399> be<00:33:22.600> perceived<00:33:23.120> as<00:33:23.279> the<00:33:23.440> Nam 00:33:23.789 --> 00:33:23.799 align:start position:0% topic should be perceived as the Nam 00:33:23.799 --> 00:33:27.310 align:start position:0% topic should be perceived as the Nam space<00:33:24.240> under<00:33:24.639> which<00:33:25.480> uh<00:33:25.679> data<00:33:26.679> should<00:33:27.000> be 00:33:27.310 --> 00:33:27.320 align:start position:0% space under which uh data should be 00:33:27.320 --> 00:33:29.830 align:start position:0% space under which uh data should be exchanged<00:33:27.799> ched<00:33:28.519> from<00:33:28.760> the<00:33:28.960> perspective<00:33:29.559> of 00:33:29.830 --> 00:33:29.840 align:start position:0% exchanged ched from the perspective of 00:33:29.840 --> 00:33:32.470 align:start position:0% exchanged ched from the perspective of an<00:33:30.039> application<00:33:31.039> so<00:33:31.240> let's<00:33:31.440> say<00:33:31.600> if<00:33:31.760> I<00:33:31.880> mean<00:33:32.279> an 00:33:32.470 --> 00:33:32.480 align:start position:0% an application so let's say if I mean an 00:33:32.480 --> 00:33:36.430 align:start position:0% an application so let's say if I mean an application<00:33:33.360> like<00:33:34.360> tegram<00:33:35.200> right<00:33:36.200> uh<00:33:36.320> a 00:33:36.430 --> 00:33:36.440 align:start position:0% application like tegram right uh a 00:33:36.440 --> 00:33:39.149 align:start position:0% application like tegram right uh a Content<00:33:36.840> topic<00:33:37.159> can<00:33:37.320> be<00:33:37.760> uh<00:33:37.960> one<00:33:38.240> chat<00:33:38.880> one 00:33:39.149 --> 00:33:39.159 align:start position:0% Content topic can be uh one chat one 00:33:39.159 --> 00:33:41.750 align:start position:0% Content topic can be uh one chat one group<00:33:39.799> in<00:33:40.039> which<00:33:40.279> the<00:33:40.399> messages<00:33:40.960> are<00:33:41.360> getting 00:33:41.750 --> 00:33:41.760 align:start position:0% group in which the messages are getting 00:33:41.760 --> 00:33:44.909 align:start position:0% group in which the messages are getting exchanged<00:33:42.320> so<00:33:42.600> hence<00:33:43.200> uh<00:33:43.360> I<00:33:43.559> am<00:33:43.840> as<00:33:43.960> a<00:33:44.120> user 00:33:44.909 --> 00:33:44.919 align:start position:0% exchanged so hence uh I am as a user 00:33:44.919 --> 00:33:47.669 align:start position:0% exchanged so hence uh I am as a user have<00:33:45.120> a<00:33:45.279> set<00:33:45.440> of<00:33:45.600> chats<00:33:46.360> and<00:33:46.639> only<00:33:47.120> from<00:33:47.360> them<00:33:47.559> I 00:33:47.669 --> 00:33:47.679 align:start position:0% have a set of chats and only from them I 00:33:47.679 --> 00:33:49.629 align:start position:0% have a set of chats and only from them I want<00:33:47.840> to<00:33:48.000> receive<00:33:48.320> messages<00:33:49.039> if<00:33:49.320> they<00:33:49.440> are 00:33:49.629 --> 00:33:49.639 align:start position:0% want to receive messages if they are 00:33:49.639 --> 00:33:51.350 align:start position:0% want to receive messages if they are coming<00:33:49.919> from<00:33:50.159> different<00:33:50.480> chats<00:33:50.919> I<00:33:51.000> don't<00:33:51.200> want 00:33:51.350 --> 00:33:51.360 align:start position:0% coming from different chats I don't want 00:33:51.360 --> 00:33:53.669 align:start position:0% coming from different chats I don't want to<00:33:51.519> receive<00:33:51.919> them<00:33:52.559> that's<00:33:52.799> the<00:33:52.960> simple<00:33:53.320> idea 00:33:53.669 --> 00:33:53.679 align:start position:0% to receive them that's the simple idea 00:33:53.679 --> 00:33:58.950 align:start position:0% to receive them that's the simple idea here<00:33:54.240> so<00:33:54.960> uh<00:33:55.200> and<00:33:55.440> as<00:33:55.840> anything<00:33:56.760> uh<00:33:57.360> uh<00:33:57.799> in<00:33:58.000> the 00:33:58.950 --> 00:33:58.960 align:start position:0% here so uh and as anything uh uh in the 00:33:58.960 --> 00:34:00.629 align:start position:0% here so uh and as anything uh uh in the uh<00:33:59.080> computer<00:33:59.440> science<00:33:59.720> we<00:33:59.840> want<00:34:00.080> to<00:34:00.279> create<00:34:00.519> a 00:34:00.629 --> 00:34:00.639 align:start position:0% uh computer science we want to create a 00:34:00.639 --> 00:34:03.909 align:start position:0% uh computer science we want to create a reader<00:34:01.039> and<00:34:01.240> writer<00:34:01.720> we<00:34:01.880> have<00:34:02.600> uh<00:34:02.919> a<00:34:03.039> blop<00:34:03.399> of 00:34:03.909 --> 00:34:03.919 align:start position:0% reader and writer we have uh a blop of 00:34:03.919 --> 00:34:06.310 align:start position:0% reader and writer we have uh a blop of uh<00:34:04.080> bytes<00:34:04.440> being<00:34:04.720> exchanged<00:34:05.080> in<00:34:05.200> the<00:34:05.320> network 00:34:06.310 --> 00:34:06.320 align:start position:0% uh bytes being exchanged in the network 00:34:06.320 --> 00:34:08.270 align:start position:0% uh bytes being exchanged in the network and<00:34:06.519> these<00:34:06.679> two<00:34:06.960> lines<00:34:07.240> are<00:34:07.480> doing<00:34:07.840> exactly 00:34:08.270 --> 00:34:08.280 align:start position:0% and these two lines are doing exactly 00:34:08.280 --> 00:34:10.430 align:start position:0% and these two lines are doing exactly this<00:34:08.480> they<00:34:08.639> create<00:34:08.919> decoder<00:34:09.359> and<00:34:09.520> encoder<00:34:10.320> and 00:34:10.430 --> 00:34:10.440 align:start position:0% this they create decoder and encoder and 00:34:10.440 --> 00:34:14.109 align:start position:0% this they create decoder and encoder and they<00:34:10.560> are<00:34:10.720> configured<00:34:11.280> to<00:34:12.240> uh<00:34:12.399> be<00:34:13.359> uh<00:34:13.560> using 00:34:14.109 --> 00:34:14.119 align:start position:0% they are configured to uh be uh using 00:34:14.119 --> 00:34:15.589 align:start position:0% they are configured to uh be uh using one 00:34:15.589 --> 00:34:15.599 align:start position:0% one 00:34:15.599 --> 00:34:18.069 align:start position:0% one particular<00:34:16.599> uh<00:34:16.839> content 00:34:18.069 --> 00:34:18.079 align:start position:0% particular uh content 00:34:18.079 --> 00:34:20.750 align:start position:0% particular uh content topic<00:34:19.079> later<00:34:19.359> on<00:34:19.560> we<00:34:19.679> have<00:34:19.800> to<00:34:19.919> start<00:34:20.159> the<00:34:20.320> node 00:34:20.750 --> 00:34:20.760 align:start position:0% topic later on we have to start the node 00:34:20.760 --> 00:34:22.669 align:start position:0% topic later on we have to start the node like<00:34:21.079> just<00:34:21.200> to<00:34:21.359> initiate<00:34:21.800> the<00:34:21.960> processes<00:34:22.520> part 00:34:22.669 --> 00:34:22.679 align:start position:0% like just to initiate the processes part 00:34:22.679 --> 00:34:26.310 align:start position:0% like just to initiate the processes part of<00:34:23.000> API<00:34:24.000> and<00:34:24.359> uh<00:34:24.480> the<00:34:24.599> second<00:34:24.960> one<00:34:25.320> does<00:34:25.800> uh<00:34:26.159> an 00:34:26.310 --> 00:34:26.320 align:start position:0% of API and uh the second one does uh an 00:34:26.320 --> 00:34:28.069 align:start position:0% of API and uh the second one does uh an important<00:34:26.839> part<00:34:27.119> is<00:34:27.280> that<00:34:27.560> with<00:34:27.720> the<00:34:27.839> block 00:34:28.069 --> 00:34:28.079 align:start position:0% important part is that with the block 00:34:28.079 --> 00:34:29.710 align:start position:0% important part is that with the block execution<00:34:28.520> of<00:34:28.720> application<00:34:29.240> until<00:34:29.560> we 00:34:29.710 --> 00:34:29.720 align:start position:0% execution of application until we 00:34:29.720 --> 00:34:33.790 align:start position:0% execution of application until we receive<00:34:30.079> some<00:34:30.280> peers<00:34:31.280> uh<00:34:31.440> this<00:34:31.560> is<00:34:32.520> just<00:34:33.520> uh 00:34:33.790 --> 00:34:33.800 align:start position:0% receive some peers uh this is just uh 00:34:33.800 --> 00:34:36.230 align:start position:0% receive some peers uh this is just uh one<00:34:34.040> way<00:34:34.200> to<00:34:34.359> do<00:34:34.520> it<00:34:35.119> uh<00:34:35.280> another<00:34:35.599> way<00:34:35.800> might<00:34:36.000> be 00:34:36.230 --> 00:34:36.240 align:start position:0% one way to do it uh another way might be 00:34:36.240 --> 00:34:39.790 align:start position:0% one way to do it uh another way might be to<00:34:37.119> uh<00:34:37.280> not<00:34:37.520> to<00:34:37.679> do<00:34:37.839> it<00:34:38.040> and<00:34:38.399> uh<00:34:38.800> rely<00:34:39.240> on<00:34:39.639> you 00:34:39.790 --> 00:34:39.800 align:start position:0% to uh not to do it and uh rely on you 00:34:39.800 --> 00:34:42.589 align:start position:0% to uh not to do it and uh rely on you know<00:34:40.079> lazy<00:34:41.079> uh<00:34:41.200> connect<00:34:42.000> connection<00:34:42.440> that 00:34:42.589 --> 00:34:42.599 align:start position:0% know lazy uh connect connection that 00:34:42.599 --> 00:34:45.310 align:start position:0% know lazy uh connect connection that will<00:34:42.720> be<00:34:42.839> managed<00:34:43.320> by<00:34:43.599> uh<00:34:43.760> GS<00:34:44.079> waku<00:34:44.399> in<00:34:44.520> that 00:34:45.310 --> 00:34:45.320 align:start position:0% will be managed by uh GS waku in that 00:34:45.320 --> 00:34:50.030 align:start position:0% will be managed by uh GS waku in that case<00:34:46.320> um<00:34:47.280> so<00:34:48.000> uh<00:34:48.359> then<00:34:49.119> here<00:34:49.480> I<00:34:49.639> are<00:34:49.760> going<00:34:49.919> to 00:34:50.030 --> 00:34:50.040 align:start position:0% case um so uh then here I are going to 00:34:50.040 --> 00:34:53.069 align:start position:0% case um so uh then here I are going to show<00:34:50.280> two<00:34:50.480> protocols<00:34:51.399> through<00:34:52.040> uh<00:34:52.159> two<00:34:52.760> um 00:34:53.069 --> 00:34:53.079 align:start position:0% show two protocols through uh two um 00:34:53.079 --> 00:34:55.230 align:start position:0% show two protocols through uh two um lightweight<00:34:53.639> protocols<00:34:54.079> that<00:34:54.240> we<00:34:54.440> have<00:34:54.919> for 00:34:55.230 --> 00:34:55.240 align:start position:0% lightweight protocols that we have for 00:34:55.240 --> 00:34:57.349 align:start position:0% lightweight protocols that we have for Edge<00:34:55.520> nodes<00:34:55.919> as<00:34:56.040> I<00:34:56.159> one<00:34:56.359> mentioned<00:34:57.119> one<00:34:57.240> of 00:34:57.349 --> 00:34:57.359 align:start position:0% Edge nodes as I one mentioned one of 00:34:57.359 --> 00:34:59.510 align:start position:0% Edge nodes as I one mentioned one of them<00:34:57.520> is<00:34:57.760> filter<00:34:58.160> and<00:34:58.560> another<00:34:58.839> one<00:34:59.040> is<00:34:59.200> light 00:34:59.510 --> 00:34:59.520 align:start position:0% them is filter and another one is light 00:34:59.520 --> 00:35:03.030 align:start position:0% them is filter and another one is light push<00:35:00.040> they<00:35:00.200> come<00:35:01.240> complimentary<00:35:02.240> and<00:35:02.640> uh<00:35:02.800> for 00:35:03.030 --> 00:35:03.040 align:start position:0% push they come complimentary and uh for 00:35:03.040 --> 00:35:05.710 align:start position:0% push they come complimentary and uh for filter<00:35:03.839> uh<00:35:03.960> the<00:35:04.079> main<00:35:04.320> use<00:35:04.640> case<00:35:04.880> is<00:35:05.119> that<00:35:05.520> you 00:35:05.710 --> 00:35:05.720 align:start position:0% filter uh the main use case is that you 00:35:05.720 --> 00:35:07.870 align:start position:0% filter uh the main use case is that you want<00:35:05.920> to<00:35:06.119> receive<00:35:06.520> only<00:35:06.839> those<00:35:07.119> messages<00:35:07.720> that 00:35:07.870 --> 00:35:07.880 align:start position:0% want to receive only those messages that 00:35:07.880 --> 00:35:10.310 align:start position:0% want to receive only those messages that you<00:35:08.000> are<00:35:08.320> interested<00:35:08.880> in<00:35:09.560> without<00:35:10.200> uh 00:35:10.310 --> 00:35:10.320 align:start position:0% you are interested in without uh 00:35:10.320 --> 00:35:14.910 align:start position:0% you are interested in without uh consuming<00:35:10.839> a<00:35:11.000> lot<00:35:11.240> of<00:35:11.920> um<00:35:12.400> bandwidths<00:35:13.720> Etc<00:35:14.720> uh 00:35:14.910 --> 00:35:14.920 align:start position:0% consuming a lot of um bandwidths Etc uh 00:35:14.920 --> 00:35:17.190 align:start position:0% consuming a lot of um bandwidths Etc uh and<00:35:15.160> the<00:35:15.320> filter<00:35:15.720> exactly<00:35:16.040> does<00:35:16.280> the<00:35:16.400> same<00:35:16.720> we 00:35:17.190 --> 00:35:17.200 align:start position:0% and the filter exactly does the same we 00:35:17.200 --> 00:35:19.990 align:start position:0% and the filter exactly does the same we uh<00:35:17.280> send<00:35:17.520> a<00:35:17.680> request<00:35:18.040> to<00:35:18.359> a<00:35:18.800> service<00:35:19.160> node<00:35:19.839> and 00:35:19.990 --> 00:35:20.000 align:start position:0% uh send a request to a service node and 00:35:20.000 --> 00:35:23.109 align:start position:0% uh send a request to a service node and we<00:35:20.200> ask<00:35:20.520> it<00:35:20.800> to<00:35:21.240> later<00:35:21.960> return<00:35:22.200> a<00:35:22.400> messages<00:35:22.839> to 00:35:23.109 --> 00:35:23.119 align:start position:0% we ask it to later return a messages to 00:35:23.119 --> 00:35:26.990 align:start position:0% we ask it to later return a messages to us<00:35:24.119> uh<00:35:24.280> the<00:35:24.440> whole<00:35:25.280> uh<00:35:25.839> uh<00:35:26.480> interaction 00:35:26.990 --> 00:35:27.000 align:start position:0% us uh the whole uh uh interaction 00:35:27.000 --> 00:35:29.430 align:start position:0% us uh the whole uh uh interaction happens<00:35:27.320> over<00:35:27.760> web<00:35:27.960> socket<00:35:28.520> as<00:35:28.640> of<00:35:28.839> now<00:35:29.280> in 00:35:29.430 --> 00:35:29.440 align:start position:0% happens over web socket as of now in 00:35:29.440 --> 00:35:31.910 align:start position:0% happens over web socket as of now in future<00:35:29.760> we<00:35:29.880> might<00:35:30.119> go<00:35:30.320> into<00:35:31.160> uh<00:35:31.320> having<00:35:31.599> a<00:35:31.760> web 00:35:31.910 --> 00:35:31.920 align:start position:0% future we might go into uh having a web 00:35:31.920 --> 00:35:33.430 align:start position:0% future we might go into uh having a web transport<00:35:32.400> which<00:35:32.520> is<00:35:32.640> work<00:35:32.839> in<00:35:33.040> progress 00:35:33.430 --> 00:35:33.440 align:start position:0% transport which is work in progress 00:35:33.440 --> 00:35:35.710 align:start position:0% transport which is work in progress right<00:35:33.599> now<00:35:34.079> as<00:35:34.200> well<00:35:34.359> as<00:35:34.520> web<00:35:34.680> RTC<00:35:35.119> might<00:35:35.280> be<00:35:35.480> in 00:35:35.710 --> 00:35:35.720 align:start position:0% right now as well as web RTC might be in 00:35:35.720 --> 00:35:39.430 align:start position:0% right now as well as web RTC might be in use<00:35:36.359> uh<00:35:36.520> for<00:35:36.960> some<00:35:37.560> cases<00:35:38.560> but<00:35:38.760> regardless<00:35:39.240> of 00:35:39.430 --> 00:35:39.440 align:start position:0% use uh for some cases but regardless of 00:35:39.440 --> 00:35:41.550 align:start position:0% use uh for some cases but regardless of it<00:35:39.680> we<00:35:39.880> rely<00:35:40.200> on<00:35:40.320> the<00:35:40.440> service<00:35:40.800> node<00:35:41.079> to<00:35:41.359> return 00:35:41.550 --> 00:35:41.560 align:start position:0% it we rely on the service node to return 00:35:41.560 --> 00:35:45.030 align:start position:0% it we rely on the service node to return us<00:35:41.880> messages<00:35:42.760> uh<00:35:42.880> in<00:35:43.040> that<00:35:43.240> case<00:35:44.040> um<00:35:44.520> we<00:35:44.640> can<00:35:44.800> do 00:35:45.030 --> 00:35:45.040 align:start position:0% us messages uh in that case um we can do 00:35:45.040 --> 00:35:47.069 align:start position:0% us messages uh in that case um we can do a<00:35:45.160> lot<00:35:45.280> of<00:35:45.440> H<00:35:45.720> ristics<00:35:46.160> as<00:35:46.280> I<00:35:46.400> mentioned 00:35:47.069 --> 00:35:47.079 align:start position:0% a lot of H ristics as I mentioned 00:35:47.079 --> 00:35:49.349 align:start position:0% a lot of H ristics as I mentioned peer-to-peer<00:35:47.440> networks<00:35:48.000> are<00:35:48.119> not<00:35:48.359> ideal<00:35:49.240> uh 00:35:49.349 --> 00:35:49.359 align:start position:0% peer-to-peer networks are not ideal uh 00:35:49.359 --> 00:35:52.630 align:start position:0% peer-to-peer networks are not ideal uh some<00:35:49.560> of<00:35:50.359> this<00:35:50.960> problematic<00:35:51.520> parts<00:35:51.920> are<00:35:52.440> uh 00:35:52.630 --> 00:35:52.640 align:start position:0% some of this problematic parts are uh 00:35:52.640 --> 00:35:56.069 align:start position:0% some of this problematic parts are uh having<00:35:53.599> uh<00:35:53.760> unreliable<00:35:54.359> nodes<00:35:55.240> one<00:35:55.440> node<00:35:55.720> can 00:35:56.069 --> 00:35:56.079 align:start position:0% having uh unreliable nodes one node can 00:35:56.079 --> 00:35:58.589 align:start position:0% having uh unreliable nodes one node can pretend<00:35:56.599> to<00:35:56.760> be<00:35:57.079> reliable<00:35:57.760> by<00:35:57.920> advertising 00:35:58.589 --> 00:35:58.599 align:start position:0% pretend to be reliable by advertising 00:35:58.599 --> 00:36:01.270 align:start position:0% pretend to be reliable by advertising itself<00:35:59.599> uh<00:35:59.800> with<00:36:00.280> some<00:36:00.599> protocols<00:36:01.079> that<00:36:01.200> we 00:36:01.270 --> 00:36:01.280 align:start position:0% itself uh with some protocols that we 00:36:01.280 --> 00:36:03.390 align:start position:0% itself uh with some protocols that we are<00:36:01.480> interested<00:36:01.920> in<00:36:02.359> but<00:36:02.480> it<00:36:02.640> might<00:36:02.839> not<00:36:03.040> do 00:36:03.390 --> 00:36:03.400 align:start position:0% are interested in but it might not do 00:36:03.400 --> 00:36:05.589 align:start position:0% are interested in but it might not do what<00:36:03.560> we<00:36:03.680> want<00:36:04.359> what<00:36:04.520> we<00:36:04.640> do<00:36:04.839> in<00:36:05.000> that<00:36:05.160> case<00:36:05.400> we 00:36:05.589 --> 00:36:05.599 align:start position:0% what we want what we do in that case we 00:36:05.599 --> 00:36:07.829 align:start position:0% what we want what we do in that case we Implement<00:36:05.960> some<00:36:06.119> heris<00:36:06.640> insight<00:36:07.119> such<00:36:07.280> as<00:36:07.720> if 00:36:07.829 --> 00:36:07.839 align:start position:0% Implement some heris insight such as if 00:36:07.839 --> 00:36:09.589 align:start position:0% Implement some heris insight such as if I<00:36:07.960> sent<00:36:08.160> a<00:36:08.359> message<00:36:08.640> and<00:36:08.760> I<00:36:08.880> didn't<00:36:09.160> receive<00:36:09.440> it 00:36:09.589 --> 00:36:09.599 align:start position:0% I sent a message and I didn't receive it 00:36:09.599 --> 00:36:11.030 align:start position:0% I sent a message and I didn't receive it back<00:36:09.760> from<00:36:09.920> that<00:36:10.079> note<00:36:10.319> it's<00:36:10.560> probably<00:36:10.839> not 00:36:11.030 --> 00:36:11.040 align:start position:0% back from that note it's probably not 00:36:11.040 --> 00:36:13.150 align:start position:0% back from that note it's probably not reliable<00:36:11.480> I'm<00:36:11.599> going<00:36:11.760> to<00:36:11.920> drop<00:36:12.200> it<00:36:12.720> so<00:36:12.960> this<00:36:13.040> is 00:36:13.150 --> 00:36:13.160 align:start position:0% reliable I'm going to drop it so this is 00:36:13.160 --> 00:36:15.870 align:start position:0% reliable I'm going to drop it so this is a<00:36:13.319> part<00:36:13.480> of<00:36:14.119> overall<00:36:15.119> umbrella<00:36:15.560> term 00:36:15.870 --> 00:36:15.880 align:start position:0% a part of overall umbrella term 00:36:15.880 --> 00:36:18.150 align:start position:0% a part of overall umbrella term reliability<00:36:16.880> which<00:36:17.079> we<00:36:17.319> were<00:36:17.560> working<00:36:17.920> for 00:36:18.150 --> 00:36:18.160 align:start position:0% reliability which we were working for 00:36:18.160 --> 00:36:19.309 align:start position:0% reliability which we were working for the<00:36:18.280> past<00:36:18.440> six 00:36:19.309 --> 00:36:19.319 align:start position:0% the past six 00:36:19.319 --> 00:36:22.950 align:start position:0% the past six months<00:36:20.319> so<00:36:21.119> um<00:36:22.119> yeah<00:36:22.359> this<00:36:22.440> is<00:36:22.560> a<00:36:22.680> simple 00:36:22.950 --> 00:36:22.960 align:start position:0% months so um yeah this is a simple 00:36:22.960 --> 00:36:24.790 align:start position:0% months so um yeah this is a simple callback<00:36:23.359> from<00:36:23.520> JavaScript<00:36:24.040> perspective 00:36:24.790 --> 00:36:24.800 align:start position:0% callback from JavaScript perspective 00:36:24.800 --> 00:36:28.390 align:start position:0% callback from JavaScript perspective nothing<00:36:25.160> fancy<00:36:25.880> s<00:36:26.119> to<00:36:26.359> Pi<00:36:26.960> uh<00:36:27.160> data<00:36:27.400> in<00:36:27.760> side<00:36:28.160> we 00:36:28.390 --> 00:36:28.400 align:start position:0% nothing fancy s to Pi uh data in side we 00:36:28.400 --> 00:36:32.630 align:start position:0% nothing fancy s to Pi uh data in side we just<00:36:28.880> uh<00:36:29.480> oh<00:36:29.680> yeah<00:36:30.160> wait<00:36:30.400> on<00:36:31.000> white<00:36:31.319> push<00:36:32.319> so 00:36:32.630 --> 00:36:32.640 align:start position:0% just uh oh yeah wait on white push so 00:36:32.640 --> 00:36:35.750 align:start position:0% just uh oh yeah wait on white push so here<00:36:33.160> just<00:36:33.960> one<00:36:34.240> for<00:36:34.599> Loop<00:36:35.040> send<00:36:35.319> in<00:36:35.560> 10 00:36:35.750 --> 00:36:35.760 align:start position:0% here just one for Loop send in 10 00:36:35.760 --> 00:36:38.870 align:start position:0% here just one for Loop send in 10 messages<00:36:36.560> from<00:36:37.319> from<00:36:37.520> our<00:36:37.839> site<00:36:38.319> and<00:36:38.440> the<00:36:38.560> sent 00:36:38.870 --> 00:36:38.880 align:start position:0% messages from from our site and the sent 00:36:38.880 --> 00:36:41.589 align:start position:0% messages from from our site and the sent is<00:36:39.040> exactly<00:36:39.400> sent<00:36:39.760> it's<00:36:40.040> just<00:36:40.520> one<00:36:40.960> request 00:36:41.589 --> 00:36:41.599 align:start position:0% is exactly sent it's just one request 00:36:41.599 --> 00:36:45.589 align:start position:0% is exactly sent it's just one request over<00:36:42.400> existing<00:36:43.400> uh<00:36:44.119> transport<00:36:44.839> in<00:36:45.040> our<00:36:45.319> case 00:36:45.589 --> 00:36:45.599 align:start position:0% over existing uh transport in our case 00:36:45.599 --> 00:36:46.790 align:start position:0% over existing uh transport in our case again<00:36:45.839> it's 00:36:46.790 --> 00:36:46.800 align:start position:0% again it's 00:36:46.800 --> 00:36:50.150 align:start position:0% again it's websockets<00:36:47.800> it<00:36:47.960> just<00:36:48.200> creates<00:36:48.520> a<00:36:48.640> Bop<00:36:48.960> of<00:36:49.440> uh 00:36:50.150 --> 00:36:50.160 align:start position:0% websockets it just creates a Bop of uh 00:36:50.160 --> 00:36:53.109 align:start position:0% websockets it just creates a Bop of uh of<00:36:50.359> bytes<00:36:50.839> and<00:36:51.359> and<00:36:51.560> sense<00:36:51.839> it<00:36:52.440> yeah<00:36:52.640> so<00:36:52.960> let's 00:36:53.109 --> 00:36:53.119 align:start position:0% of bytes and and sense it yeah so let's 00:36:53.119 --> 00:36:54.670 align:start position:0% of bytes and and sense it yeah so let's see<00:36:53.280> inter 00:36:54.670 --> 00:36:54.680 align:start position:0% see inter 00:36:54.680 --> 00:37:02.710 align:start position:0% see inter connection<00:36:55.680> uh 00:37:02.710 --> 00:37:02.720 align:start position:0% 00:37:02.720 --> 00:37:05.309 align:start position:0% okay<00:37:03.000> so<00:37:03.400> I'm<00:37:03.560> going<00:37:03.720> to<00:37:03.880> open<00:37:04.280> Local<00:37:04.720> Host<00:37:05.200> I 00:37:05.309 --> 00:37:05.319 align:start position:0% okay so I'm going to open Local Host I 00:37:05.319 --> 00:37:10.829 align:start position:0% okay so I'm going to open Local Host I have<00:37:05.440> it<00:37:05.680> open<00:37:06.760> and<00:37:07.760> yeah<00:37:07.960> there<00:37:08.079> are<00:37:08.240> two<00:37:08.440> tabs 00:37:10.829 --> 00:37:10.839 align:start position:0% have it open and yeah there are two tabs 00:37:10.839 --> 00:37:15.430 align:start position:0% have it open and yeah there are two tabs uh<00:37:11.839> here<00:37:12.680> we<00:37:12.960> want<00:37:13.160> to 00:37:15.430 --> 00:37:15.440 align:start position:0% uh here we want to 00:37:15.440 --> 00:37:18.430 align:start position:0% uh here we want to reconnect<00:37:16.440> here<00:37:16.599> we<00:37:16.720> want<00:37:16.880> to<00:37:17.040> reconnect<00:37:17.520> as 00:37:18.430 --> 00:37:18.440 align:start position:0% reconnect here we want to reconnect as 00:37:18.440 --> 00:37:22.069 align:start position:0% reconnect here we want to reconnect as well<00:37:19.720> um<00:37:20.720> we<00:37:20.800> are<00:37:20.960> waiting<00:37:21.240> for<00:37:21.560> Pierce<00:37:21.880> no 00:37:22.069 --> 00:37:22.079 align:start position:0% well um we are waiting for Pierce no 00:37:22.079 --> 00:37:29.630 align:start position:0% well um we are waiting for Pierce no Pierce<00:37:22.880> available<00:37:23.880> something<00:37:24.359> happened 00:37:29.630 --> 00:37:29.640 align:start position:0% 00:37:29.640 --> 00:37:31.190 align:start position:0% good<00:37:30.000> here<00:37:30.160> we<00:37:30.319> subscribed<00:37:30.800> and<00:37:30.920> here<00:37:31.040> we 00:37:31.190 --> 00:37:31.200 align:start position:0% good here we subscribed and here we 00:37:31.200 --> 00:37:33.470 align:start position:0% good here we subscribed and here we subscribed<00:37:31.720> so<00:37:31.920> now<00:37:32.200> we<00:37:32.319> are<00:37:32.839> sending<00:37:33.240> some 00:37:33.470 --> 00:37:33.480 align:start position:0% subscribed so now we are sending some 00:37:33.480 --> 00:37:35.270 align:start position:0% subscribed so now we are sending some messages<00:37:33.839> in<00:37:33.960> the<00:37:34.119> loop<00:37:34.720> and<00:37:34.880> we<00:37:34.960> are 00:37:35.270 --> 00:37:35.280 align:start position:0% messages in the loop and we are 00:37:35.280 --> 00:37:37.790 align:start position:0% messages in the loop and we are receiving<00:37:35.560> some<00:37:35.760> messages<00:37:36.720> as<00:37:36.839> we<00:37:37.000> see<00:37:37.520> uh<00:37:37.640> one 00:37:37.790 --> 00:37:37.800 align:start position:0% receiving some messages as we see uh one 00:37:37.800 --> 00:37:40.390 align:start position:0% receiving some messages as we see uh one of<00:37:37.920> the<00:37:38.119> properties<00:37:39.079> of<00:37:39.160> the<00:37:39.319> network<00:37:39.760> is<00:37:39.920> that 00:37:40.390 --> 00:37:40.400 align:start position:0% of the properties of the network is that 00:37:40.400 --> 00:37:43.550 align:start position:0% of the properties of the network is that um<00:37:41.079> howu<00:37:41.599> functions<00:37:42.400> is<00:37:42.560> that<00:37:42.760> we<00:37:42.960> going<00:37:43.280> going 00:37:43.550 --> 00:37:43.560 align:start position:0% um howu functions is that we going going 00:37:43.560 --> 00:37:44.910 align:start position:0% um howu functions is that we going going receive<00:37:43.880> our<00:37:44.079> own 00:37:44.910 --> 00:37:44.920 align:start position:0% receive our own 00:37:44.920 --> 00:37:47.790 align:start position:0% receive our own messages<00:37:45.920> uh<00:37:46.520> and<00:37:47.000> uh<00:37:47.160> this<00:37:47.280> can<00:37:47.440> be<00:37:47.599> quite 00:37:47.790 --> 00:37:47.800 align:start position:0% messages uh and uh this can be quite 00:37:47.800 --> 00:37:49.510 align:start position:0% messages uh and uh this can be quite useful<00:37:48.160> for<00:37:48.280> some<00:37:48.440> of<00:37:48.599> the 00:37:49.510 --> 00:37:49.520 align:start position:0% useful for some of the 00:37:49.520 --> 00:37:52.870 align:start position:0% useful for some of the applications<00:37:50.520> um<00:37:51.200> yeah<00:37:51.319> so<00:37:52.319> this<00:37:52.480> does<00:37:52.680> it 00:37:52.870 --> 00:37:52.880 align:start position:0% applications um yeah so this does it 00:37:52.880 --> 00:37:55.390 align:start position:0% applications um yeah so this does it thing<00:37:53.200> so<00:37:53.560> it<00:37:53.880> works<00:37:54.880> uh<00:37:55.000> one<00:37:55.160> of<00:37:55.280> the 00:37:55.390 --> 00:37:55.400 align:start position:0% thing so it works uh one of the 00:37:55.400 --> 00:37:57.750 align:start position:0% thing so it works uh one of the interesting<00:37:55.839> things<00:37:56.160> is<00:37:56.319> that<00:37:57.119> um<00:37:57.520> there<00:37:57.640> are 00:37:57.750 --> 00:37:57.760 align:start position:0% interesting things is that um there are 00:37:57.760 --> 00:38:00.710 align:start position:0% interesting things is that um there are a<00:37:57.839> lot<00:37:58.040> of<00:37:58.160> logs<00:37:59.040> uh<00:37:59.200> error<00:37:59.520> logs<00:38:00.359> they 00:38:00.710 --> 00:38:00.720 align:start position:0% a lot of logs uh error logs they 00:38:00.720 --> 00:38:04.309 align:start position:0% a lot of logs uh error logs they expected<00:38:01.720> as<00:38:02.000> for<00:38:02.720> they<00:38:02.880> cannot<00:38:03.200> be<00:38:03.960> uh 00:38:04.309 --> 00:38:04.319 align:start position:0% expected as for they cannot be uh 00:38:04.319 --> 00:38:07.190 align:start position:0% expected as for they cannot be uh ignored<00:38:05.319> uh<00:38:05.480> are<00:38:05.640> there<00:38:05.800> any<00:38:06.000> questions<00:38:06.839> uh 00:38:07.190 --> 00:38:07.200 align:start position:0% ignored uh are there any questions uh 00:38:07.200 --> 00:38:09.950 align:start position:0% ignored uh are there any questions uh right<00:38:07.359> now<00:38:07.760> yeah 00:38:09.950 --> 00:38:09.960 align:start position:0% right now yeah 00:38:09.960 --> 00:38:15.670 align:start position:0% right now yeah please 00:38:15.670 --> 00:38:15.680 align:start position:0% 00:38:15.680 --> 00:38:18.589 align:start position:0% um<00:38:16.680> light<00:38:16.960> node<00:38:17.200> instance<00:38:17.520> can<00:38:17.599> you<00:38:17.720> repeat<00:38:18.000> to 00:38:18.589 --> 00:38:18.599 align:start position:0% um light node instance can you repeat to 00:38:18.599 --> 00:38:20.990 align:start position:0% um light node instance can you repeat to yes<00:38:19.079> yeah<00:38:19.240> the<00:38:19.359> light<00:38:19.640> node<00:38:20.040> instance<00:38:20.839> it's 00:38:20.990 --> 00:38:21.000 align:start position:0% yes yeah the light node instance it's 00:38:21.000 --> 00:38:24.390 align:start position:0% yes yeah the light node instance it's not<00:38:21.160> a<00:38:21.319> P2P<00:38:22.000> instant<00:38:22.640> no<00:38:22.960> actually<00:38:23.400> it<00:38:23.560> is<00:38:23.880> so 00:38:24.390 --> 00:38:24.400 align:start position:0% not a P2P instant no actually it is so 00:38:24.400 --> 00:38:26.750 align:start position:0% not a P2P instant no actually it is so uh<00:38:24.560> but<00:38:24.960> it<00:38:25.119> depends<00:38:25.839> right<00:38:26.240> uh<00:38:26.400> there's<00:38:26.599> some 00:38:26.750 --> 00:38:26.760 align:start position:0% uh but it depends right uh there's some 00:38:26.760 --> 00:38:28.030 align:start position:0% uh but it depends right uh there's some trade-offs<00:38:27.160> that<00:38:27.240> we<00:38:27.319> have<00:38:27.560> have<00:38:27.680> to<00:38:27.760> make<00:38:27.920> in 00:38:28.030 --> 00:38:28.040 align:start position:0% trade-offs that we have have to make in 00:38:28.040 --> 00:38:30.950 align:start position:0% trade-offs that we have have to make in the<00:38:28.200> browser<00:38:29.040> one<00:38:29.240> of<00:38:29.400> them<00:38:29.640> is<00:38:29.800> that<00:38:30.319> uh<00:38:30.760> set 00:38:30.950 --> 00:38:30.960 align:start position:0% the browser one of them is that uh set 00:38:30.960 --> 00:38:33.430 align:start position:0% the browser one of them is that uh set of<00:38:31.200> available<00:38:31.680> transports<00:38:32.680> uh<00:38:32.920> for<00:38:33.160> for<00:38:33.319> the 00:38:33.430 --> 00:38:33.440 align:start position:0% of available transports uh for for the 00:38:33.440 --> 00:38:35.109 align:start position:0% of available transports uh for for the browser<00:38:33.839> tab<00:38:34.160> right<00:38:34.319> browser<00:38:34.680> is<00:38:34.880> very 00:38:35.109 --> 00:38:35.119 align:start position:0% browser tab right browser is very 00:38:35.119 --> 00:38:36.670 align:start position:0% browser tab right browser is very restricted<00:38:35.720> environment<00:38:36.200> there<00:38:36.280> are<00:38:36.440> a<00:38:36.520> lot 00:38:36.670 --> 00:38:36.680 align:start position:0% restricted environment there are a lot 00:38:36.680 --> 00:38:38.910 align:start position:0% restricted environment there are a lot of<00:38:36.800> things<00:38:37.000> that<00:38:37.160> we<00:38:37.319> cannot<00:38:37.720> do<00:38:38.400> such<00:38:38.599> as<00:38:38.800> we 00:38:38.910 --> 00:38:38.920 align:start position:0% of things that we cannot do such as we 00:38:38.920 --> 00:38:42.630 align:start position:0% of things that we cannot do such as we cannot<00:38:39.760> do<00:38:40.000> a<00:38:40.160> TCP<00:38:41.119> uh<00:38:41.560> connection<00:38:42.040> directly 00:38:42.630 --> 00:38:42.640 align:start position:0% cannot do a TCP uh connection directly 00:38:42.640 --> 00:38:45.349 align:start position:0% cannot do a TCP uh connection directly or<00:38:42.839> UDP<00:38:43.280> connection<00:38:43.760> directly<00:38:44.200> we<00:38:44.359> have<00:38:44.480> to<00:38:45.040> do 00:38:45.349 --> 00:38:45.359 align:start position:0% or UDP connection directly we have to do 00:38:45.359 --> 00:38:48.430 align:start position:0% or UDP connection directly we have to do either<00:38:45.599> HTTP<00:38:46.359> or<00:38:47.240> uh<00:38:47.359> a<00:38:47.520> websocket<00:38:48.000> connection 00:38:48.430 --> 00:38:48.440 align:start position:0% either HTTP or uh a websocket connection 00:38:48.440 --> 00:38:51.069 align:start position:0% either HTTP or uh a websocket connection that's<00:38:48.640> it<00:38:49.160> web<00:38:49.359> RTC<00:38:49.800> as<00:38:49.960> well<00:38:50.160> but<00:38:50.760> there<00:38:50.920> are 00:38:51.069 --> 00:38:51.079 align:start position:0% that's it web RTC as well but there are 00:38:51.079 --> 00:38:55.510 align:start position:0% that's it web RTC as well but there are limits<00:38:51.599> right<00:38:52.160> so<00:38:53.119> um<00:38:54.119> and<00:38:54.319> also<00:38:54.640> resources<00:38:55.400> uh 00:38:55.510 --> 00:38:55.520 align:start position:0% limits right so um and also resources uh 00:38:55.520 --> 00:38:57.589 align:start position:0% limits right so um and also resources uh browser<00:38:55.960> is<00:38:56.160> very<00:38:56.359> limited<00:38:56.760> in<00:38:57.119> how<00:38:57.240> much<00:38:57.440> much 00:38:57.589 --> 00:38:57.599 align:start position:0% browser is very limited in how much much 00:38:57.599 --> 00:38:59.069 align:start position:0% browser is very limited in how much much computation<00:38:58.119> we<00:38:58.240> can<00:38:58.400> do<00:38:58.560> like<00:38:58.800> heavy 00:38:59.069 --> 00:38:59.079 align:start position:0% computation we can do like heavy 00:38:59.079 --> 00:39:01.230 align:start position:0% computation we can do like heavy computation<00:38:59.680> right<00:39:00.200> uh<00:39:00.319> the<00:39:00.440> browser<00:39:00.800> tab<00:39:01.040> can 00:39:01.230 --> 00:39:01.240 align:start position:0% computation right uh the browser tab can 00:39:01.240 --> 00:39:03.950 align:start position:0% computation right uh the browser tab can become<00:39:01.920> suspended<00:39:02.920> uh<00:39:03.200> quite<00:39:03.400> easily<00:39:03.760> by 00:39:03.950 --> 00:39:03.960 align:start position:0% become suspended uh quite easily by 00:39:03.960 --> 00:39:05.750 align:start position:0% become suspended uh quite easily by operational<00:39:04.440> system<00:39:04.800> everything<00:39:05.440> stops 00:39:05.750 --> 00:39:05.760 align:start position:0% operational system everything stops 00:39:05.760 --> 00:39:08.349 align:start position:0% operational system everything stops working<00:39:06.119> in<00:39:06.359> there<00:39:06.680> right<00:39:07.359> uh<00:39:07.560> and<00:39:08.000> uh<00:39:08.200> it 00:39:08.349 --> 00:39:08.359 align:start position:0% working in there right uh and uh it 00:39:08.359 --> 00:39:11.190 align:start position:0% working in there right uh and uh it cannot<00:39:08.800> be<00:39:09.000> a<00:39:09.240> fully<00:39:09.800> functional<00:39:10.720> uh<00:39:10.839> part<00:39:11.040> of 00:39:11.190 --> 00:39:11.200 align:start position:0% cannot be a fully functional uh part of 00:39:11.200 --> 00:39:13.470 align:start position:0% cannot be a fully functional uh part of the<00:39:11.319> network<00:39:11.920> hence<00:39:12.240> we<00:39:12.400> call<00:39:12.599> it<00:39:12.839> an<00:39:13.079> edge 00:39:13.470 --> 00:39:13.480 align:start position:0% the network hence we call it an edge 00:39:13.480 --> 00:39:15.750 align:start position:0% the network hence we call it an edge node<00:39:14.079> meaning<00:39:14.560> that<00:39:14.839> the<00:39:15.000> traffic<00:39:15.400> kind<00:39:15.560> of 00:39:15.750 --> 00:39:15.760 align:start position:0% node meaning that the traffic kind of 00:39:15.760 --> 00:39:18.030 align:start position:0% node meaning that the traffic kind of ends<00:39:16.200> there<00:39:16.560> right<00:39:16.760> it<00:39:16.880> does<00:39:17.079> not<00:39:17.520> participate 00:39:18.030 --> 00:39:18.040 align:start position:0% ends there right it does not participate 00:39:18.040 --> 00:39:20.670 align:start position:0% ends there right it does not participate as<00:39:18.160> a<00:39:18.280> full<00:39:18.560> node<00:39:18.800> it's<00:39:18.960> not<00:39:19.079> full<00:39:19.800> but<00:39:20.359> it<00:39:20.480> is 00:39:20.670 --> 00:39:20.680 align:start position:0% as a full node it's not full but it is 00:39:20.680 --> 00:39:23.230 align:start position:0% as a full node it's not full but it is peer-to-peer<00:39:21.119> in<00:39:21.520> the<00:39:21.640> meaning<00:39:22.079> that<00:39:22.839> the<00:39:23.119> the 00:39:23.230 --> 00:39:23.240 align:start position:0% peer-to-peer in the meaning that the the 00:39:23.240 --> 00:39:25.589 align:start position:0% peer-to-peer in the meaning that the the browser<00:39:23.599> tab<00:39:23.920> is<00:39:24.160> independent<00:39:24.839> in<00:39:25.079> how<00:39:25.240> it 00:39:25.589 --> 00:39:25.599 align:start position:0% browser tab is independent in how it 00:39:25.599 --> 00:39:28.030 align:start position:0% browser tab is independent in how it discovers<00:39:25.880> the<00:39:26.000> network<00:39:26.480> it<00:39:26.599> uses<00:39:27.520> uh<00:39:27.680> almost 00:39:28.030 --> 00:39:28.040 align:start position:0% discovers the network it uses uh almost 00:39:28.040 --> 00:39:30.270 align:start position:0% discovers the network it uses uh almost everything<00:39:28.560> but<00:39:29.040> uh<00:39:29.440> Discovery<00:39:29.720> defies<00:39:30.079> that 00:39:30.270 --> 00:39:30.280 align:start position:0% everything but uh Discovery defies that 00:39:30.280 --> 00:39:34.150 align:start position:0% everything but uh Discovery defies that Ian<00:39:31.000> mentioned<00:39:32.200> um<00:39:33.200> it<00:39:33.680> discovers<00:39:34.000> the 00:39:34.150 --> 00:39:34.160 align:start position:0% Ian mentioned um it discovers the 00:39:34.160 --> 00:39:37.910 align:start position:0% Ian mentioned um it discovers the network<00:39:34.640> through<00:39:35.040> DNS<00:39:35.839> and<00:39:36.280> per<00:39:36.480> exchange<00:39:37.480> and 00:39:37.910 --> 00:39:37.920 align:start position:0% network through DNS and per exchange and 00:39:37.920 --> 00:39:40.630 align:start position:0% network through DNS and per exchange and as<00:39:38.480> uh<00:39:38.599> for<00:39:38.839> our<00:39:39.160> case<00:39:39.440> right<00:39:39.599> now<00:39:39.760> we<00:39:39.920> have<00:39:40.079> 24 00:39:40.630 --> 00:39:40.640 align:start position:0% as uh for our case right now we have 24 00:39:40.640 --> 00:39:43.589 align:start position:0% as uh for our case right now we have 24 peers<00:39:41.319> so<00:39:41.560> right<00:39:41.720> now<00:39:41.839> we<00:39:41.960> have<00:39:42.160> 24<00:39:43.040> web<00:39:43.359> socket 00:39:43.589 --> 00:39:43.599 align:start position:0% peers so right now we have 24 web socket 00:39:43.599 --> 00:39:46.829 align:start position:0% peers so right now we have 24 web socket connections<00:39:44.079> to<00:39:44.359> 24<00:39:45.240> full<00:39:45.560> nodes<00:39:46.240> that<00:39:46.480> we<00:39:46.640> can 00:39:46.829 --> 00:39:46.839 align:start position:0% connections to 24 full nodes that we can 00:39:46.839 --> 00:39:50.510 align:start position:0% connections to 24 full nodes that we can use<00:39:47.520> interchangeably<00:39:48.520> or<00:39:48.720> in<00:39:48.960> rotation<00:39:49.839> or<00:39:50.400> if 00:39:50.510 --> 00:39:50.520 align:start position:0% use interchangeably or in rotation or if 00:39:50.520 --> 00:39:52.710 align:start position:0% use interchangeably or in rotation or if we<00:39:50.720> observe<00:39:51.119> that<00:39:51.280> some<00:39:51.599> does<00:39:51.880> not<00:39:52.160> work<00:39:52.640> we 00:39:52.710 --> 00:39:52.720 align:start position:0% we observe that some does not work we 00:39:52.720 --> 00:39:54.829 align:start position:0% we observe that some does not work we can<00:39:52.880> use<00:39:53.200> others<00:39:53.760> and<00:39:53.920> if<00:39:54.119> others<00:39:54.440> does<00:39:54.640> not 00:39:54.829 --> 00:39:54.839 align:start position:0% can use others and if others does not 00:39:54.839 --> 00:39:57.829 align:start position:0% can use others and if others does not work<00:39:55.119> we<00:39:55.240> can<00:39:55.720> do<00:39:55.960> something<00:39:56.319> else<00:39:56.839> and<00:39:57.440> so<00:39:57.680> the 00:39:57.829 --> 00:39:57.839 align:start position:0% work we can do something else and so the 00:39:57.839 --> 00:40:00.550 align:start position:0% work we can do something else and so the per<00:39:58.200> exchange<00:39:58.640> is<00:39:58.800> an<00:39:59.079> abent<00:39:59.520> pure<00:40:00.040> Discovery 00:40:00.550 --> 00:40:00.560 align:start position:0% per exchange is an abent pure Discovery 00:40:00.560 --> 00:40:02.670 align:start position:0% per exchange is an abent pure Discovery meaning<00:40:00.920> that<00:40:01.079> it<00:40:01.280> happens<00:40:01.720> always<00:40:02.000> in<00:40:02.160> the 00:40:02.670 --> 00:40:02.680 align:start position:0% meaning that it happens always in the 00:40:02.680 --> 00:40:06.790 align:start position:0% meaning that it happens always in the background<00:40:03.680> so<00:40:04.200> and<00:40:04.720> uh<00:40:04.920> we<00:40:05.040> can<00:40:05.200> see<00:40:05.640> that<00:40:06.599> we 00:40:06.790 --> 00:40:06.800 align:start position:0% background so and uh we can see that we 00:40:06.800 --> 00:40:09.230 align:start position:0% background so and uh we can see that we have<00:40:07.240> quite<00:40:07.480> a<00:40:07.599> few<00:40:07.839> nodes<00:40:08.640> collected<00:40:09.119> right 00:40:09.230 --> 00:40:09.240 align:start position:0% have quite a few nodes collected right 00:40:09.240 --> 00:40:11.309 align:start position:0% have quite a few nodes collected right now<00:40:09.440> right<00:40:09.520> now<00:40:09.720> 25<00:40:10.560> but<00:40:10.720> the<00:40:10.839> longer<00:40:11.200> the 00:40:11.309 --> 00:40:11.319 align:start position:0% now right now 25 but the longer the 00:40:11.319 --> 00:40:13.670 align:start position:0% now right now 25 but the longer the browser<00:40:11.680> tab<00:40:11.960> will<00:40:12.119> be<00:40:12.560> executing<00:40:13.160> will<00:40:13.400> be 00:40:13.670 --> 00:40:13.680 align:start position:0% browser tab will be executing will be 00:40:13.680 --> 00:40:16.710 align:start position:0% browser tab will be executing will be open<00:40:14.480> the<00:40:14.599> more<00:40:14.839> peers<00:40:15.160> we're<00:40:15.280> going<00:40:15.400> to<00:40:16.280> uh 00:40:16.710 --> 00:40:16.720 align:start position:0% open the more peers we're going to uh 00:40:16.720 --> 00:40:20.109 align:start position:0% open the more peers we're going to uh discover<00:40:17.000> and<00:40:17.200> use<00:40:18.200> eventually<00:40:19.200> so<00:40:19.720> from<00:40:19.920> that 00:40:20.109 --> 00:40:20.119 align:start position:0% discover and use eventually so from that 00:40:20.119 --> 00:40:21.950 align:start position:0% discover and use eventually so from that regard<00:40:20.400> it<00:40:20.520> is<00:40:20.680> peer<00:40:20.920> to-peer<00:40:21.160> and<00:40:21.520> it<00:40:21.640> owns 00:40:21.950 --> 00:40:21.960 align:start position:0% regard it is peer to-peer and it owns 00:40:21.960 --> 00:40:25.750 align:start position:0% regard it is peer to-peer and it owns its<00:40:22.079> own<00:40:22.280> stack<00:40:22.720> as<00:40:22.880> to<00:40:23.440> like<00:40:23.960> uh<00:40:24.760> encryption 00:40:25.750 --> 00:40:25.760 align:start position:0% its own stack as to like uh encryption 00:40:25.760 --> 00:40:29.230 align:start position:0% its own stack as to like uh encryption uh<00:40:26.280> yeah<00:40:26.520> so<00:40:27.040> so<00:40:27.440> this<00:40:27.960> provides<00:40:28.359> like<00:40:28.560> a 00:40:29.230 --> 00:40:29.240 align:start position:0% uh yeah so so this provides like a 00:40:29.240 --> 00:40:31.510 align:start position:0% uh yeah so so this provides like a websocket<00:40:30.000> server<00:40:30.440> so<00:40:30.640> all<00:40:30.880> these<00:40:31.079> nodes 00:40:31.510 --> 00:40:31.520 align:start position:0% websocket server so all these nodes 00:40:31.520 --> 00:40:34.750 align:start position:0% websocket server so all these nodes provide<00:40:32.079> a<00:40:32.560> separate<00:40:33.560> websocket<00:40:34.160> server<00:40:34.520> for 00:40:34.750 --> 00:40:34.760 align:start position:0% provide a separate websocket server for 00:40:34.760 --> 00:40:36.589 align:start position:0% provide a separate websocket server for these<00:40:34.960> Edge<00:40:35.280> noes<00:40:35.920> yeah<00:40:36.040> exactly<00:40:36.400> this<00:40:36.480> is 00:40:36.589 --> 00:40:36.599 align:start position:0% these Edge noes yeah exactly this is 00:40:36.599 --> 00:40:38.510 align:start position:0% these Edge noes yeah exactly this is very<00:40:36.839> interesting<00:40:37.440> because<00:40:37.720> we<00:40:37.839> can<00:40:38.400> uh 00:40:38.510 --> 00:40:38.520 align:start position:0% very interesting because we can uh 00:40:38.520 --> 00:40:42.069 align:start position:0% very interesting because we can uh reason<00:40:38.960> about<00:40:39.240> it<00:40:39.480> as<00:40:39.640> to<00:40:40.240> having<00:40:40.760> a<00:40:41.359> server<00:40:41.800> W 00:40:42.069 --> 00:40:42.079 align:start position:0% reason about it as to having a server W 00:40:42.079 --> 00:40:44.349 align:start position:0% reason about it as to having a server W application<00:40:42.560> we<00:40:42.680> don't<00:40:42.880> have<00:40:43.079> kind<00:40:43.280> a<00:40:43.480> server 00:40:44.349 --> 00:40:44.359 align:start position:0% application we don't have kind a server 00:40:44.359 --> 00:40:46.069 align:start position:0% application we don't have kind a server but<00:40:44.520> we<00:40:44.680> still<00:40:44.920> can<00:40:45.200> have<00:40:45.359> a<00:40:45.520> connection<00:40:45.920> in 00:40:46.069 --> 00:40:46.079 align:start position:0% but we still can have a connection in 00:40:46.079 --> 00:40:49.309 align:start position:0% but we still can have a connection in between<00:40:46.440> them<00:40:46.720> right<00:40:46.920> it's<00:40:47.359> back<00:40:47.760> endless<00:40:48.760> yes 00:40:49.309 --> 00:40:49.319 align:start position:0% between them right it's back endless yes 00:40:49.319 --> 00:40:52.109 align:start position:0% between them right it's back endless yes and<00:40:49.839> I<00:40:49.960> mean<00:40:50.280> one<00:40:50.560> thing<00:40:50.800> from<00:40:51.000> the<00:40:51.280> previous 00:40:52.109 --> 00:40:52.119 align:start position:0% and I mean one thing from the previous 00:40:52.119 --> 00:40:55.950 align:start position:0% and I mean one thing from the previous uh<00:40:52.800> uh<00:40:53.000> slide<00:40:53.440> I<00:40:53.599> have<00:40:53.880> was<00:40:54.240> the<00:40:55.079> the<00:40:55.240> syncing 00:40:55.950 --> 00:40:55.960 align:start position:0% uh uh slide I have was the the syncing 00:40:55.960 --> 00:40:59.150 align:start position:0% uh uh slide I have was the the syncing right<00:40:56.160> so<00:40:56.440> how<00:40:57.400> how<00:40:57.599> does<00:40:57.839> the<00:40:58.280> syncing<00:40:58.800> works 00:40:59.150 --> 00:40:59.160 align:start position:0% right so how how does the syncing works 00:40:59.160 --> 00:41:01.870 align:start position:0% right so how how does the syncing works because<00:40:59.400> you<00:40:59.520> said<00:40:59.800> you<00:41:00.000> only<00:41:00.400> send<00:41:01.400> messages 00:41:01.870 --> 00:41:01.880 align:start position:0% because you said you only send messages 00:41:01.880 --> 00:41:05.950 align:start position:0% because you said you only send messages to<00:41:02.119> like<00:41:02.359> four<00:41:02.680> or<00:41:02.960> five<00:41:03.599> uh<00:41:04.400> peers<00:41:04.920> at<00:41:05.040> a<00:41:05.200> time 00:41:05.950 --> 00:41:05.960 align:start position:0% to like four or five uh peers at a time 00:41:05.960 --> 00:41:07.750 align:start position:0% to like four or five uh peers at a time so<00:41:06.160> how<00:41:06.359> does<00:41:06.520> it<00:41:06.760> know 00:41:07.750 --> 00:41:07.760 align:start position:0% so how does it know 00:41:07.760 --> 00:41:09.910 align:start position:0% so how does it know like<00:41:08.760> the 00:41:09.910 --> 00:41:09.920 align:start position:0% like the 00:41:09.920 --> 00:41:12.950 align:start position:0% like the me<00:41:10.920> yeah<00:41:11.079> so<00:41:11.400> uh<00:41:11.520> how<00:41:11.680> does<00:41:11.839> the<00:41:12.000> node<00:41:12.480> knows 00:41:12.950 --> 00:41:12.960 align:start position:0% me yeah so uh how does the node knows 00:41:12.960 --> 00:41:15.750 align:start position:0% me yeah so uh how does the node knows where<00:41:13.160> to<00:41:13.760> send<00:41:14.040> the<00:41:14.200> messages<00:41:14.960> yes<00:41:15.160> was<00:41:15.280> it 00:41:15.750 --> 00:41:15.760 align:start position:0% where to send the messages yes was it 00:41:15.760 --> 00:41:18.950 align:start position:0% where to send the messages yes was it the<00:41:15.920> question<00:41:16.480> yes<00:41:16.720> so<00:41:17.119> um<00:41:18.040> uh<00:41:18.240> Gossip<00:41:18.599> sub<00:41:18.839> is 00:41:18.950 --> 00:41:18.960 align:start position:0% the question yes so um uh Gossip sub is 00:41:18.960 --> 00:41:21.950 align:start position:0% the question yes so um uh Gossip sub is not<00:41:19.119> a<00:41:19.319> directed<00:41:20.079> uh<00:41:20.520> uh<00:41:20.720> way<00:41:20.880> of<00:41:21.040> routing<00:41:21.760> the 00:41:21.950 --> 00:41:21.960 align:start position:0% not a directed uh uh way of routing the 00:41:21.960 --> 00:41:24.790 align:start position:0% not a directed uh uh way of routing the traffic<00:41:22.800> and<00:41:22.960> we<00:41:23.119> rely<00:41:23.480> here<00:41:23.680> on<00:41:23.960> eventual 00:41:24.790 --> 00:41:24.800 align:start position:0% traffic and we rely here on eventual 00:41:24.800 --> 00:41:27.630 align:start position:0% traffic and we rely here on eventual consistency<00:41:25.440> let's<00:41:25.640> name<00:41:25.839> it<00:41:26.040> like<00:41:26.240> that<00:41:26.800> we 00:41:27.630 --> 00:41:27.640 align:start position:0% consistency let's name it like that we 00:41:27.640 --> 00:41:30.550 align:start position:0% consistency let's name it like that we um<00:41:28.640> we<00:41:28.800> know<00:41:29.160> that<00:41:29.520> the<00:41:29.640> node<00:41:29.960> will<00:41:30.160> relay 00:41:30.550 --> 00:41:30.560 align:start position:0% um we know that the node will relay 00:41:30.560 --> 00:41:32.910 align:start position:0% um we know that the node will relay messages<00:41:30.960> to<00:41:31.119> its<00:41:31.319> peers<00:41:32.200> in<00:41:32.359> our<00:41:32.560> case<00:41:32.760> it's 00:41:32.910 --> 00:41:32.920 align:start position:0% messages to its peers in our case it's 00:41:32.920 --> 00:41:36.069 align:start position:0% messages to its peers in our case it's four<00:41:33.359> 5<00:41:33.640> 8<00:41:34.040> something<00:41:34.400> like<00:41:34.560> that<00:41:34.880> right<00:41:35.480> and 00:41:36.069 --> 00:41:36.079 align:start position:0% four 5 8 something like that right and 00:41:36.079 --> 00:41:39.630 align:start position:0% four 5 8 something like that right and we<00:41:36.280> know<00:41:36.599> that<00:41:37.560> uh<00:41:38.560> all<00:41:38.800> the<00:41:38.920> peers<00:41:39.359> kind<00:41:39.520> of 00:41:39.630 --> 00:41:39.640 align:start position:0% we know that uh all the peers kind of 00:41:39.640 --> 00:41:42.190 align:start position:0% we know that uh all the peers kind of connected<00:41:40.000> to<00:41:40.119> each<00:41:40.280> other<00:41:40.599> right<00:41:40.880> we<00:41:41.400> uh<00:41:42.040> have 00:41:42.190 --> 00:41:42.200 align:start position:0% connected to each other right we uh have 00:41:42.200 --> 00:41:45.309 align:start position:0% connected to each other right we uh have it<00:41:42.359> as<00:41:42.520> a<00:41:42.720> a<00:41:42.880> graph<00:41:43.839> um<00:41:44.240> so<00:41:44.720> if<00:41:44.920> someone 00:41:45.309 --> 00:41:45.319 align:start position:0% it as a a graph um so if someone 00:41:45.319 --> 00:41:48.150 align:start position:0% it as a a graph um so if someone originates<00:41:45.920> with<00:41:46.040> a<00:41:46.200> message<00:41:46.480> on<00:41:46.680> one<00:41:47.040> end<00:41:48.040> uh 00:41:48.150 --> 00:41:48.160 align:start position:0% originates with a message on one end uh 00:41:48.160 --> 00:41:49.990 align:start position:0% originates with a message on one end uh by<00:41:48.280> the<00:41:48.400> rules<00:41:48.680> of<00:41:48.839> Gossip<00:41:49.200> sub<00:41:49.480> it's<00:41:49.599> going<00:41:49.800> to 00:41:49.990 --> 00:41:50.000 align:start position:0% by the rules of Gossip sub it's going to 00:41:50.000 --> 00:41:52.790 align:start position:0% by the rules of Gossip sub it's going to propagate<00:41:50.520> till<00:41:50.880> the<00:41:51.000> other<00:41:51.280> end<00:41:51.760> but<00:41:51.920> it<00:41:52.520> can 00:41:52.790 --> 00:41:52.800 align:start position:0% propagate till the other end but it can 00:41:52.800 --> 00:41:54.829 align:start position:0% propagate till the other end but it can take<00:41:53.040> a<00:41:53.200> lot<00:41:53.359> of<00:41:53.560> time<00:41:53.839> as<00:41:53.960> well<00:41:54.119> as<00:41:54.319> little<00:41:54.599> to 00:41:54.829 --> 00:41:54.839 align:start position:0% take a lot of time as well as little to 00:41:54.839 --> 00:41:56.309 align:start position:0% take a lot of time as well as little to time<00:41:55.119> right<00:41:55.240> we<00:41:55.359> don't<00:41:55.520> know<00:41:55.760> where<00:41:55.920> the<00:41:56.040> note 00:41:56.309 --> 00:41:56.319 align:start position:0% time right we don't know where the note 00:41:56.319 --> 00:41:59.270 align:start position:0% time right we don't know where the note is<00:41:56.440> placed<00:41:56.720> in<00:41:56.800> the<00:41:56.920> network<00:41:57.280> work<00:41:58.280> um<00:41:59.000> and<00:41:59.160> I 00:41:59.270 --> 00:41:59.280 align:start position:0% is placed in the network work um and I 00:41:59.280 --> 00:42:01.030 align:start position:0% is placed in the network work um and I don't<00:41:59.480> mean<00:41:59.720> geographical<00:42:00.400> position<00:42:00.800> but 00:42:01.030 --> 00:42:01.040 align:start position:0% don't mean geographical position but 00:42:01.040 --> 00:42:03.150 align:start position:0% don't mean geographical position but like<00:42:01.240> logical<00:42:01.720> from<00:42:02.000> the<00:42:02.400> the<00:42:02.520> vaku 00:42:03.150 --> 00:42:03.160 align:start position:0% like logical from the the vaku 00:42:03.160 --> 00:42:06.190 align:start position:0% like logical from the the vaku standpoint<00:42:04.160> um<00:42:04.640> yeah<00:42:04.839> so<00:42:05.200> in<00:42:05.319> our<00:42:05.560> simulations 00:42:06.190 --> 00:42:06.200 align:start position:0% standpoint um yeah so in our simulations 00:42:06.200 --> 00:42:08.309 align:start position:0% standpoint um yeah so in our simulations we<00:42:06.319> had<00:42:06.480> simulations<00:42:07.040> like<00:42:07.240> up<00:42:07.400> to<00:42:07.640> 10,000 00:42:08.309 --> 00:42:08.319 align:start position:0% we had simulations like up to 10,000 00:42:08.319 --> 00:42:12.589 align:start position:0% we had simulations like up to 10,000 noes<00:42:09.319> and<00:42:09.680> we<00:42:10.040> had<00:42:10.240> the<00:42:10.400> numbers<00:42:10.839> as<00:42:11.119> to<00:42:12.000> uh<00:42:12.359> in 00:42:12.589 --> 00:42:12.599 align:start position:0% noes and we had the numbers as to uh in 00:42:12.599 --> 00:42:15.870 align:start position:0% noes and we had the numbers as to uh in average<00:42:13.440> uh<00:42:13.560> from<00:42:14.040> 200<00:42:14.359> to<00:42:14.599> 500<00:42:15.119> milliseconds 00:42:15.870 --> 00:42:15.880 align:start position:0% average uh from 200 to 500 milliseconds 00:42:15.880 --> 00:42:18.829 align:start position:0% average uh from 200 to 500 milliseconds was<00:42:16.079> the<00:42:16.520> message<00:42:16.960> propagation<00:42:17.920> in<00:42:18.119> current 00:42:18.829 --> 00:42:18.839 align:start position:0% was the message propagation in current 00:42:18.839 --> 00:42:21.670 align:start position:0% was the message propagation in current tww<00:42:19.839> uh<00:42:20.000> which<00:42:20.160> supports<00:42:20.599> rln<00:42:21.200> as<00:42:21.359> for<00:42:21.559> the 00:42:21.670 --> 00:42:21.680 align:start position:0% tww uh which supports rln as for the 00:42:21.680 --> 00:42:26.030 align:start position:0% tww uh which supports rln as for the meaning<00:42:22.079> to<00:42:22.839> uh<00:42:23.400> shield<00:42:23.760> from<00:42:24.079> the<00:42:24.319> do<00:42:25.119> we<00:42:25.480> have 00:42:26.030 --> 00:42:26.040 align:start position:0% meaning to uh shield from the do we have 00:42:26.040 --> 00:42:29.109 align:start position:0% meaning to uh shield from the do we have like<00:42:26.480> uh<00:42:26.680> 1,000<00:42:27.200> the<00:42:27.319> nodes<00:42:28.240> and<00:42:28.680> um<00:42:29.000> the 00:42:29.109 --> 00:42:29.119 align:start position:0% like uh 1,000 the nodes and um the 00:42:29.119 --> 00:42:31.829 align:start position:0% like uh 1,000 the nodes and um the message<00:42:29.480> propagates<00:42:30.000> quite<00:42:30.280> fast<00:42:31.280> yeah<00:42:31.559> and 00:42:31.829 --> 00:42:31.839 align:start position:0% message propagates quite fast yeah and 00:42:31.839 --> 00:42:34.750 align:start position:0% message propagates quite fast yeah and so<00:42:32.280> if<00:42:32.520> the<00:42:32.680> node<00:42:33.040> is<00:42:33.200> offline<00:42:33.680> and<00:42:33.920> comes<00:42:34.160> in 00:42:34.750 --> 00:42:34.760 align:start position:0% so if the node is offline and comes in 00:42:34.760 --> 00:42:37.630 align:start position:0% so if the node is offline and comes in right<00:42:35.400> does<00:42:35.599> it<00:42:35.800> get<00:42:36.079> the<00:42:36.440> older<00:42:37.040> messages 00:42:37.630 --> 00:42:37.640 align:start position:0% right does it get the older messages 00:42:37.640 --> 00:42:41.349 align:start position:0% right does it get the older messages that<00:42:37.800> were<00:42:38.640> broadcast<00:42:39.640> yeah<00:42:39.960> uh<00:42:40.119> so<00:42:40.720> um<00:42:41.240> this 00:42:41.349 --> 00:42:41.359 align:start position:0% that were broadcast yeah uh so um this 00:42:41.359 --> 00:42:43.390 align:start position:0% that were broadcast yeah uh so um this is<00:42:41.559> why<00:42:41.760> we<00:42:41.960> actually<00:42:42.280> came<00:42:42.480> up<00:42:42.720> with<00:42:42.920> store 00:42:43.390 --> 00:42:43.400 align:start position:0% is why we actually came up with store 00:42:43.400 --> 00:42:45.390 align:start position:0% is why we actually came up with store protocol<00:42:44.000> right<00:42:44.280> in<00:42:44.400> peer-to-peer<00:42:44.800> networks 00:42:45.390 --> 00:42:45.400 align:start position:0% protocol right in peer-to-peer networks 00:42:45.400 --> 00:42:47.510 align:start position:0% protocol right in peer-to-peer networks we<00:42:45.520> kind<00:42:45.680> of<00:42:45.920> think<00:42:46.240> about<00:42:46.760> the<00:42:47.000> transport 00:42:47.510 --> 00:42:47.520 align:start position:0% we kind of think about the transport 00:42:47.520 --> 00:42:49.430 align:start position:0% we kind of think about the transport right<00:42:47.720> this<00:42:47.839> is<00:42:48.200> uh<00:42:48.640> these<00:42:48.800> are<00:42:49.000> nodes<00:42:49.280> they 00:42:49.430 --> 00:42:49.440 align:start position:0% right this is uh these are nodes they 00:42:49.440 --> 00:42:51.309 align:start position:0% right this is uh these are nodes they talk<00:42:49.599> to<00:42:49.720> each<00:42:49.880> other<00:42:50.240> a<00:42:50.480> store<00:42:50.880> everything 00:42:51.309 --> 00:42:51.319 align:start position:0% talk to each other a store everything 00:42:51.319 --> 00:42:54.030 align:start position:0% talk to each other a store everything else<00:42:51.559> it's<00:42:51.760> like<00:42:52.000> application<00:42:52.599> logic<00:42:53.480> uh<00:42:53.640> we 00:42:54.030 --> 00:42:54.040 align:start position:0% else it's like application logic uh we 00:42:54.040 --> 00:42:55.870 align:start position:0% else it's like application logic uh we agree<00:42:54.359> with<00:42:54.559> that<00:42:54.880> right<00:42:55.119> at<00:42:55.359> each 00:42:55.870 --> 00:42:55.880 align:start position:0% agree with that right at each 00:42:55.880 --> 00:42:58.030 align:start position:0% agree with that right at each application<00:42:56.400> that<00:42:56.520> uses<00:42:57.240> let's<00:42:57.359> say<00:42:57.520> vaku 00:42:58.030 --> 00:42:58.040 align:start position:0% application that uses let's say vaku 00:42:58.040 --> 00:43:01.230 align:start position:0% application that uses let's say vaku stack<00:42:58.960> uh<00:42:59.079> or<00:42:59.240> the<00:42:59.440> network<00:43:00.440> uh<00:43:00.720> needs<00:43:01.040> to 00:43:01.230 --> 00:43:01.240 align:start position:0% stack uh or the network uh needs to 00:43:01.240 --> 00:43:04.870 align:start position:0% stack uh or the network uh needs to implement<00:43:01.720> its<00:43:01.880> own<00:43:02.559> like<00:43:03.079> uh<00:43:03.559> stuff<00:43:03.839> on<00:43:04.079> top<00:43:04.720> a 00:43:04.870 --> 00:43:04.880 align:start position:0% implement its own like uh stuff on top a 00:43:04.880 --> 00:43:07.309 align:start position:0% implement its own like uh stuff on top a store<00:43:05.280> including<00:43:06.280> but<00:43:06.520> we<00:43:06.640> still<00:43:07.160> understand 00:43:07.309 --> 00:43:07.319 align:start position:0% store including but we still understand 00:43:07.319 --> 00:43:10.630 align:start position:0% store including but we still understand there<00:43:07.440> is<00:43:07.559> a<00:43:07.720> need<00:43:08.119> to<00:43:08.520> have<00:43:08.680> a<00:43:08.839> short<00:43:09.240> lift<00:43:09.960> uh 00:43:10.630 --> 00:43:10.640 align:start position:0% there is a need to have a short lift uh 00:43:10.640 --> 00:43:12.230 align:start position:0% there is a need to have a short lift uh like<00:43:10.839> while<00:43:11.040> I'm<00:43:11.200> offline<00:43:11.599> let's<00:43:11.760> say<00:43:11.880> for<00:43:12.040> 1 00:43:12.230 --> 00:43:12.240 align:start position:0% like while I'm offline let's say for 1 00:43:12.240 --> 00:43:14.270 align:start position:0% like while I'm offline let's say for 1 hour<00:43:12.520> right<00:43:12.680> I<00:43:12.800> still<00:43:12.960> want<00:43:13.240> to<00:43:13.839> get<00:43:14.040> back 00:43:14.270 --> 00:43:14.280 align:start position:0% hour right I still want to get back 00:43:14.280 --> 00:43:17.710 align:start position:0% hour right I still want to get back these<00:43:14.640> messages<00:43:15.640> so<00:43:16.200> uh<00:43:16.359> store<00:43:16.839> is<00:43:17.000> for<00:43:17.200> full 00:43:17.710 --> 00:43:17.720 align:start position:0% these messages so uh store is for full 00:43:17.720 --> 00:43:21.390 align:start position:0% these messages so uh store is for full nodes<00:43:18.720> and<00:43:19.119> it's<00:43:19.480> uh<00:43:19.640> going<00:43:20.359> uh<00:43:20.520> once<00:43:21.040> let<00:43:21.240> say 00:43:21.390 --> 00:43:21.400 align:start position:0% nodes and it's uh going uh once let say 00:43:21.400 --> 00:43:24.150 align:start position:0% nodes and it's uh going uh once let say your<00:43:21.520> full<00:43:21.760> node<00:43:22.079> goes<00:43:22.520> offline<00:43:23.520> uh<00:43:23.720> and<00:43:23.880> goes 00:43:24.150 --> 00:43:24.160 align:start position:0% your full node goes offline uh and goes 00:43:24.160 --> 00:43:27.109 align:start position:0% your full node goes offline uh and goes online<00:43:24.720> back<00:43:25.359> it's<00:43:25.599> just<00:43:25.960> going<00:43:26.200> to<00:43:26.440> ask<00:43:26.839> the 00:43:27.109 --> 00:43:27.119 align:start position:0% online back it's just going to ask the 00:43:27.119 --> 00:43:28.990 align:start position:0% online back it's just going to ask the pece<00:43:27.400> around<00:43:27.760> for<00:43:28.000> the<00:43:28.200> missing<00:43:28.599> messages 00:43:28.990 --> 00:43:29.000 align:start position:0% pece around for the missing messages 00:43:29.000 --> 00:43:30.430 align:start position:0% pece around for the missing messages through<00:43:29.200> the<00:43:29.280> store<00:43:29.599> protocol<00:43:30.040> and<00:43:30.240> it's 00:43:30.430 --> 00:43:30.440 align:start position:0% through the store protocol and it's 00:43:30.440 --> 00:43:33.349 align:start position:0% through the store protocol and it's going<00:43:30.599> to<00:43:30.760> do<00:43:31.000> the 00:43:33.349 --> 00:43:33.359 align:start position:0% 00:43:33.359 --> 00:43:38.470 align:start position:0% S<00:43:34.359> thank 00:43:38.470 --> 00:43:38.480 align:start position:0% 00:43:38.480 --> 00:43:43.549 align:start position:0% you<00:43:39.480> any<00:43:39.640> more<00:43:40.119> questions<00:43:41.119> no<00:43:42.079> um<00:43:43.079> let's<00:43:43.200> see 00:43:43.549 --> 00:43:43.559 align:start position:0% you any more questions no um let's see 00:43:43.559 --> 00:43:46.710 align:start position:0% you any more questions no um let's see something<00:43:43.920> with<00:43:44.359> rust<00:43:45.040> been<00:43:45.319> done<00:43:45.800> and<00:43:46.200> uh<00:43:46.599> if 00:43:46.710 --> 00:43:46.720 align:start position:0% something with rust been done and uh if 00:43:46.720 --> 00:43:48.790 align:start position:0% something with rust been done and uh if you<00:43:46.839> want<00:43:47.040> we<00:43:47.119> can<00:43:47.280> do<00:43:47.480> some<00:43:48.040> programming<00:43:48.599> or 00:43:48.790 --> 00:43:48.800 align:start position:0% you want we can do some programming or 00:43:48.800 --> 00:44:25.270 align:start position:0% you want we can do some programming or something 00:44:25.270 --> 00:44:25.280 align:start position:0% 00:44:25.280 --> 00:44:31.430 align:start position:0% Co 00:44:31.430 --> 00:44:31.440 align:start position:0% 00:44:31.440 --> 00:44:33.790 align:start position:0% okay<00:44:31.960> thanks<00:44:32.200> Sasha 00:44:33.790 --> 00:44:33.800 align:start position:0% okay thanks Sasha 00:44:33.800 --> 00:44:36.829 align:start position:0% okay thanks Sasha um<00:44:34.800> uh<00:44:35.000> okay<00:44:35.240> in<00:44:35.440> this<00:44:35.960> uh<00:44:36.200> part<00:44:36.400> of<00:44:36.599> the 00:44:36.829 --> 00:44:36.839 align:start position:0% um uh okay in this uh part of the 00:44:36.839 --> 00:44:41.390 align:start position:0% um uh okay in this uh part of the session<00:44:37.240> we're<00:44:37.480> going<00:44:37.760> is<00:44:37.960> it 00:44:41.390 --> 00:44:41.400 align:start position:0% 00:44:41.400 --> 00:44:46.470 align:start position:0% visible<00:44:42.400> we're<00:44:42.559> going<00:44:42.760> to<00:44:43.079> to<00:44:43.520> cover<00:44:44.800> um<00:44:45.800> the<00:44:46.400> a 00:44:46.470 --> 00:44:46.480 align:start position:0% visible we're going to to cover um the a 00:44:46.480 --> 00:44:49.829 align:start position:0% visible we're going to to cover um the a few<00:44:46.720> examples<00:44:47.599> regarding<00:44:48.160> the<00:44:49.160> uh<00:44:49.319> wagas 00:44:49.829 --> 00:44:49.839 align:start position:0% few examples regarding the uh wagas 00:44:49.839 --> 00:44:52.230 align:start position:0% few examples regarding the uh wagas bindings<00:44:50.559> uh<00:44:50.680> by<00:44:50.800> the<00:44:50.920> way<00:44:51.319> credits<00:44:51.720> to<00:44:52.079> to 00:44:52.230 --> 00:44:52.240 align:start position:0% bindings uh by the way credits to to 00:44:52.240 --> 00:44:55.510 align:start position:0% bindings uh by the way credits to to Richard<00:44:52.559> for<00:44:52.720> the<00:44:52.960> great<00:44:53.440> job<00:44:53.640> in<00:44:53.839> this<00:44:54.359> repo 00:44:55.510 --> 00:44:55.520 align:start position:0% Richard for the great job in this repo 00:44:55.520 --> 00:44:59.150 align:start position:0% Richard for the great job in this repo and<00:44:56.520> uh<00:44:56.640> this<00:44:56.720> is<00:44:56.880> the<00:44:57.160> the<00:44:57.920> uh<00:44:58.440> in<00:44:58.599> in<00:44:58.800> there 00:44:59.150 --> 00:44:59.160 align:start position:0% and uh this is the the uh in in there 00:44:59.160 --> 00:45:02.589 align:start position:0% and uh this is the the uh in in there well<00:44:59.520> in<00:44:59.800> um<00:45:00.440> QR<00:45:00.839> shared<00:45:01.440> earlier<00:45:01.720> on<00:45:02.000> by<00:45:02.200> by 00:45:02.589 --> 00:45:02.599 align:start position:0% well in um QR shared earlier on by by 00:45:02.599 --> 00:45:05.510 align:start position:0% well in um QR shared earlier on by by Sasha<00:45:03.599> uh<00:45:03.760> you<00:45:03.960> you<00:45:04.079> will<00:45:04.319> get 00:45:05.510 --> 00:45:05.520 align:start position:0% Sasha uh you you will get 00:45:05.520 --> 00:45:10.069 align:start position:0% Sasha uh you you will get um<00:45:06.520> uh<00:45:07.200> a<00:45:07.359> branch<00:45:07.920> to<00:45:08.200> do<00:45:08.440> this<00:45:09.000> uh<00:45:09.160> where<00:45:09.599> this 00:45:10.069 --> 00:45:10.079 align:start position:0% um uh a branch to do this uh where this 00:45:10.079 --> 00:45:11.030 align:start position:0% um uh a branch to do this uh where this is 00:45:11.030 --> 00:45:11.040 align:start position:0% is 00:45:11.040 --> 00:45:15.030 align:start position:0% is implemented<00:45:12.240> and<00:45:13.240> let<00:45:13.440> me<00:45:13.880> let's<00:45:14.520> uh<00:45:14.680> first<00:45:14.880> of 00:45:15.030 --> 00:45:15.040 align:start position:0% implemented and let me let's uh first of 00:45:15.040 --> 00:45:18.270 align:start position:0% implemented and let me let's uh first of all<00:45:15.800> uh<00:45:16.079> overview<00:45:16.800> the<00:45:17.079> the<00:45:17.200> repo<00:45:17.640> and<00:45:17.880> what<00:45:18.079> we 00:45:18.270 --> 00:45:18.280 align:start position:0% all uh overview the the repo and what we 00:45:18.280 --> 00:45:21.030 align:start position:0% all uh overview the the repo and what we have<00:45:18.680> in 00:45:21.030 --> 00:45:21.040 align:start position:0% 00:45:21.040 --> 00:45:25.990 align:start position:0% there<00:45:22.119> basically<00:45:23.119> we<00:45:23.319> have<00:45:24.280> wuis<00:45:25.280> bindings 00:45:25.990 --> 00:45:26.000 align:start position:0% there basically we have wuis bindings 00:45:26.000 --> 00:45:27.549 align:start position:0% there basically we have wuis bindings and<00:45:26.200> the<00:45:26.359> examples 00:45:27.549 --> 00:45:27.559 align:start position:0% and the examples 00:45:27.559 --> 00:45:31.630 align:start position:0% and the examples and<00:45:27.839> in<00:45:28.160> wuis<00:45:29.160> uh<00:45:29.520> this<00:45:29.680> is<00:45:30.040> the<00:45:30.400> the<00:45:30.520> one<00:45:30.839> that 00:45:31.630 --> 00:45:31.640 align:start position:0% and in wuis uh this is the the one that 00:45:31.640 --> 00:45:35.069 align:start position:0% and in wuis uh this is the the one that um<00:45:32.000> implements<00:45:33.000> the<00:45:34.000> the 00:45:35.069 --> 00:45:35.079 align:start position:0% um implements the the 00:45:35.079 --> 00:45:37.109 align:start position:0% um implements the the nwagu 00:45:37.109 --> 00:45:37.119 align:start position:0% nwagu 00:45:37.119 --> 00:45:40.750 align:start position:0% nwagu uh<00:45:38.119> this<00:45:38.240> is<00:45:38.559> the<00:45:38.920> the<00:45:39.119> N 00:45:40.750 --> 00:45:40.760 align:start position:0% uh this is the the N 00:45:40.760 --> 00:45:44.309 align:start position:0% uh this is the the N implementation<00:45:41.760> and<00:45:42.040> from<00:45:42.480> from<00:45:42.880> here<00:45:43.599> we've 00:45:44.309 --> 00:45:44.319 align:start position:0% implementation and from from here we've 00:45:44.319 --> 00:45:46.510 align:start position:0% implementation and from from here we've created<00:45:45.040> or<00:45:45.359> we<00:45:45.520> are<00:45:45.680> working<00:45:46.079> on<00:45:46.319> the 00:45:46.510 --> 00:45:46.520 align:start position:0% created or we are working on the 00:45:46.520 --> 00:45:51.069 align:start position:0% created or we are working on the creation<00:45:46.960> of<00:45:47.599> um<00:45:47.800> C<00:45:48.480> library<00:45:49.480> that<00:45:49.880> exposes<00:45:50.880> uh 00:45:51.069 --> 00:45:51.079 align:start position:0% creation of um C library that exposes uh 00:45:51.079 --> 00:45:53.230 align:start position:0% creation of um C library that exposes uh all<00:45:51.240> the<00:45:51.400> functionality<00:45:52.119> that<00:45:52.440> that<00:45:52.599> is 00:45:53.230 --> 00:45:53.240 align:start position:0% all the functionality that that is 00:45:53.240 --> 00:45:56.510 align:start position:0% all the functionality that that is available<00:45:54.040> from<00:45:55.040> from<00:45:55.240> aaku<00:45:55.760> no<00:45:56.079> the 00:45:56.510 --> 00:45:56.520 align:start position:0% available from from aaku no the 00:45:56.520 --> 00:45:58.309 align:start position:0% available from from aaku no the discovery<00:45:57.079> the<00:45:57.240> creation<00:45:57.559> of<00:45:57.680> a<00:45:57.839> note 00:45:58.309 --> 00:45:58.319 align:start position:0% discovery the creation of a note 00:45:58.319 --> 00:46:04.030 align:start position:0% discovery the creation of a note connection<00:45:58.680> to<00:45:58.920> another<00:45:59.760> Pier<00:46:01.079> um<00:46:02.079> H<00:46:02.559> punching 00:46:04.030 --> 00:46:04.040 align:start position:0% connection to another Pier um H punching 00:46:04.040 --> 00:46:07.549 align:start position:0% connection to another Pier um H punching um<00:46:05.040> yeah<00:46:05.520> ET<00:46:06.119> all<00:46:06.240> the<00:46:06.400> all<00:46:06.599> the<00:46:06.800> lip2p 00:46:07.549 --> 00:46:07.559 align:start position:0% um yeah ET all the all the lip2p 00:46:07.559 --> 00:46:10.470 align:start position:0% um yeah ET all the all the lip2p protocols<00:46:08.040> that<00:46:08.280> we've<00:46:08.800> uh<00:46:09.359> mentioned<00:46:10.359> uh 00:46:10.470 --> 00:46:10.480 align:start position:0% protocols that we've uh mentioned uh 00:46:10.480 --> 00:46:13.270 align:start position:0% protocols that we've uh mentioned uh earlier<00:46:10.800> on<00:46:11.119> are<00:46:11.440> covered<00:46:12.000> by<00:46:12.240> the<00:46:12.440> N 00:46:13.270 --> 00:46:13.280 align:start position:0% earlier on are covered by the N 00:46:13.280 --> 00:46:16.069 align:start position:0% earlier on are covered by the N implementation<00:46:14.280> and<00:46:14.520> in<00:46:14.720> this<00:46:15.280> C<00:46:15.599> library 00:46:16.069 --> 00:46:16.079 align:start position:0% implementation and in this C library 00:46:16.079 --> 00:46:18.190 align:start position:0% implementation and in this C library what<00:46:16.240> we<00:46:16.359> are<00:46:16.559> doing<00:46:16.880> is<00:46:17.319> we<00:46:17.440> are<00:46:17.640> exposing 00:46:18.190 --> 00:46:18.200 align:start position:0% what we are doing is we are exposing 00:46:18.200 --> 00:46:22.630 align:start position:0% what we are doing is we are exposing these<00:46:18.800> uh<00:46:19.160> features<00:46:20.160> uh<00:46:20.319> through<00:46:20.800> ffi<00:46:21.800> to<00:46:22.200> any 00:46:22.630 --> 00:46:22.640 align:start position:0% these uh features uh through ffi to any 00:46:22.640 --> 00:46:25.750 align:start position:0% these uh features uh through ffi to any any<00:46:22.880> other<00:46:23.359> languages<00:46:24.319> uh<00:46:24.440> at<00:46:24.599> the<00:46:24.720> moment<00:46:25.520> as 00:46:25.750 --> 00:46:25.760 align:start position:0% any other languages uh at the moment as 00:46:25.760 --> 00:46:29.990 align:start position:0% any other languages uh at the moment as Sasha<00:46:26.119> mentioned<00:46:27.079> we<00:46:27.200> are<00:46:27.680> covering<00:46:28.640> uh<00:46:28.960> goang 00:46:29.990 --> 00:46:30.000 align:start position:0% Sasha mentioned we are covering uh goang 00:46:30.000 --> 00:46:33.430 align:start position:0% Sasha mentioned we are covering uh goang rust<00:46:31.000> uh<00:46:31.240> python<00:46:32.240> uh 00:46:33.430 --> 00:46:33.440 align:start position:0% rust uh python uh 00:46:33.440 --> 00:46:36.270 align:start position:0% rust uh python uh C++<00:46:34.440> and<00:46:35.240> no 00:46:36.270 --> 00:46:36.280 align:start position:0% C++ and no 00:46:36.280 --> 00:46:39.549 align:start position:0% C++ and no GS<00:46:37.280> and<00:46:37.839> okay<00:46:38.040> let's<00:46:38.319> go<00:46:38.640> let's<00:46:38.839> carry<00:46:39.079> on<00:46:39.400> in 00:46:39.549 --> 00:46:39.559 align:start position:0% GS and okay let's go let's carry on in 00:46:39.559 --> 00:46:43.069 align:start position:0% GS and okay let's go let's carry on in this<00:46:39.760> particular<00:46:40.359> case<00:46:41.359> um<00:46:42.319> uh<00:46:42.480> then<00:46:42.599> we<00:46:42.760> have 00:46:43.069 --> 00:46:43.079 align:start position:0% this particular case um uh then we have 00:46:43.079 --> 00:46:47.230 align:start position:0% this particular case um uh then we have the<00:46:43.440> waku<00:46:44.359> bindings<00:46:45.280> crate<00:46:46.280> and<00:46:46.520> what<00:46:46.640> it<00:46:46.800> does 00:46:47.230 --> 00:46:47.240 align:start position:0% the waku bindings crate and what it does 00:46:47.240 --> 00:46:53.109 align:start position:0% the waku bindings crate and what it does is<00:46:47.880> um<00:46:48.680> a<00:46:49.280> li<00:46:50.079> crate<00:46:51.079> uh<00:46:51.280> which<00:46:51.440> is<00:46:52.119> just<00:46:52.599> um<00:46:52.920> a 00:46:53.109 --> 00:46:53.119 align:start position:0% is um a li crate uh which is just um a 00:46:53.119 --> 00:46:58.109 align:start position:0% is um a li crate uh which is just um a wrap<00:46:54.119> a<00:46:54.240> wer<00:46:54.800> around<00:46:55.280> the<00:46:55.760> gues 00:46:58.109 --> 00:46:58.119 align:start position:0% wrap a wer around the gues 00:46:58.119 --> 00:47:00.270 align:start position:0% wrap a wer around the gues and<00:46:58.480> in<00:46:58.720> there<00:46:58.920> we<00:46:59.119> have<00:46:59.680> the<00:47:00.160> the 00:47:00.270 --> 00:47:00.280 align:start position:0% and in there we have the the 00:47:00.280 --> 00:47:04.069 align:start position:0% and in there we have the the implementation<00:47:01.280> of<00:47:01.680> the<00:47:02.680> of<00:47:02.839> the<00:47:03.119> bindings 00:47:04.069 --> 00:47:04.079 align:start position:0% implementation of the of the bindings 00:47:04.079 --> 00:47:08.430 align:start position:0% implementation of the of the bindings stuff<00:47:05.079> and<00:47:05.359> all<00:47:05.680> the<00:47:06.599> the<00:47:06.720> complexity<00:47:07.400> is<00:47:08.160> uh 00:47:08.430 --> 00:47:08.440 align:start position:0% stuff and all the the complexity is uh 00:47:08.440 --> 00:47:12.069 align:start position:0% stuff and all the the complexity is uh tackled<00:47:09.440> within<00:47:09.839> this<00:47:10.720> this 00:47:12.069 --> 00:47:12.079 align:start position:0% tackled within this this 00:47:12.079 --> 00:47:14.390 align:start position:0% tackled within this this module 00:47:14.390 --> 00:47:14.400 align:start position:0% module 00:47:14.400 --> 00:47:16.470 align:start position:0% module and<00:47:15.400> and 00:47:16.470 --> 00:47:16.480 align:start position:0% and and 00:47:16.480 --> 00:47:19.670 align:start position:0% and and yeah<00:47:17.480> you<00:47:17.559> will<00:47:17.720> see<00:47:17.920> that<00:47:18.319> uh<00:47:18.559> we<00:47:18.880> we<00:47:19.200> apply<00:47:19.520> a 00:47:19.670 --> 00:47:19.680 align:start position:0% yeah you will see that uh we we apply a 00:47:19.680 --> 00:47:21.630 align:start position:0% yeah you will see that uh we we apply a technique<00:47:20.280> called 00:47:21.630 --> 00:47:21.640 align:start position:0% technique called 00:47:21.640 --> 00:47:24.950 align:start position:0% technique called trampoline<00:47:22.640> and<00:47:23.200> that<00:47:23.400> helps<00:47:23.680> us<00:47:23.920> to<00:47:24.720> uh<00:47:24.839> to 00:47:24.950 --> 00:47:24.960 align:start position:0% trampoline and that helps us to uh to 00:47:24.960 --> 00:47:27.430 align:start position:0% trampoline and that helps us to uh to interact<00:47:25.440> with<00:47:25.680> with<00:47:25.839> rust 00:47:27.430 --> 00:47:27.440 align:start position:0% interact with with rust 00:47:27.440 --> 00:47:30.549 align:start position:0% interact with with rust sorry<00:47:27.839> with<00:47:28.119> the<00:47:28.800> lip<00:47:29.240> guacu<00:47:29.680> library<00:47:30.200> from 00:47:30.549 --> 00:47:30.559 align:start position:0% sorry with the lip guacu library from 00:47:30.559 --> 00:47:31.390 align:start position:0% sorry with the lip guacu library from from 00:47:31.390 --> 00:47:31.400 align:start position:0% from 00:47:31.400 --> 00:47:35.829 align:start position:0% from rust<00:47:32.760> and<00:47:33.760> then<00:47:33.960> we<00:47:34.119> have<00:47:34.400> the<00:47:35.119> in<00:47:35.400> in<00:47:35.559> this 00:47:35.829 --> 00:47:35.839 align:start position:0% rust and then we have the in in this 00:47:35.839 --> 00:47:38.030 align:start position:0% rust and then we have the in in this particular<00:47:36.400> case<00:47:36.599> we<00:47:36.760> have<00:47:37.079> a<00:47:37.240> few 00:47:38.030 --> 00:47:38.040 align:start position:0% particular case we have a few 00:47:38.040 --> 00:47:40.910 align:start position:0% particular case we have a few consumers<00:47:39.040> and<00:47:39.800> this<00:47:39.920> is 00:47:40.910 --> 00:47:40.920 align:start position:0% consumers and this is 00:47:40.920 --> 00:47:44.589 align:start position:0% consumers and this is the<00:47:41.920> just<00:47:42.280> a<00:47:42.480> simple 00:47:44.589 --> 00:47:44.599 align:start position:0% the just a simple 00:47:44.599 --> 00:47:48.069 align:start position:0% the just a simple application<00:47:45.599> um<00:47:46.079> well<00:47:46.599> it<00:47:46.760> it<00:47:46.880> uses<00:47:47.240> Tokyo<00:47:47.920> as 00:47:48.069 --> 00:47:48.079 align:start position:0% application um well it it uses Tokyo as 00:47:48.079 --> 00:47:52.710 align:start position:0% application um well it it uses Tokyo as a<00:47:48.559> sync<00:47:49.559> um<00:47:50.800> framework<00:47:51.800> and<00:47:52.319> what<00:47:52.480> what<00:47:52.599> it 00:47:52.710 --> 00:47:52.720 align:start position:0% a sync um framework and what what it 00:47:52.720 --> 00:47:56.030 align:start position:0% a sync um framework and what what it does<00:47:53.240> it<00:47:53.520> basically<00:47:54.400> at<00:47:54.559> first<00:47:54.880> it<00:47:55.040> creates<00:47:55.440> a 00:47:56.030 --> 00:47:56.040 align:start position:0% does it basically at first it creates a 00:47:56.040 --> 00:47:58.190 align:start position:0% does it basically at first it creates a a<00:47:56.280> waku<00:47:56.599> node 00:47:58.190 --> 00:47:58.200 align:start position:0% a waku node 00:47:58.200 --> 00:48:00.790 align:start position:0% a waku node with<00:47:58.599> uh<00:47:58.760> certain 00:48:00.790 --> 00:48:00.800 align:start position:0% with uh certain 00:48:00.800 --> 00:48:06.750 align:start position:0% with uh certain parameters<00:48:01.880> then<00:48:02.880> it<00:48:03.079> establishes<00:48:03.920> the<00:48:04.240> DNS 00:48:06.750 --> 00:48:06.760 align:start position:0% parameters then it establishes the DNS 00:48:06.760 --> 00:48:11.870 align:start position:0% parameters then it establishes the DNS Discovery<00:48:07.760> um<00:48:09.200> URL<00:48:10.200> uh<00:48:10.359> this<00:48:10.480> is<00:48:10.880> for<00:48:11.119> ring<00:48:11.680> the 00:48:11.870 --> 00:48:11.880 align:start position:0% Discovery um URL uh this is for ring the 00:48:11.880 --> 00:48:14.309 align:start position:0% Discovery um URL uh this is for ring the B<00:48:12.240> strap<00:48:12.520> notes<00:48:13.119> in<00:48:13.200> order<00:48:13.559> for<00:48:13.760> the<00:48:13.920> not<00:48:14.119> to 00:48:14.309 --> 00:48:14.319 align:start position:0% B strap notes in order for the not to 00:48:14.319 --> 00:48:17.190 align:start position:0% B strap notes in order for the not to start<00:48:14.880> participating<00:48:15.520> in<00:48:15.720> in<00:48:15.839> the<00:48:16.079> network<00:48:17.040> it 00:48:17.190 --> 00:48:17.200 align:start position:0% start participating in in the network it 00:48:17.200 --> 00:48:21.069 align:start position:0% start participating in in the network it needs<00:48:18.000> um<00:48:18.440> an<00:48:18.640> initial<00:48:19.440> help<00:48:20.440> and<00:48:20.800> for<00:48:20.920> that 00:48:21.069 --> 00:48:21.079 align:start position:0% needs um an initial help and for that 00:48:21.079 --> 00:48:24.470 align:start position:0% needs um an initial help and for that reason<00:48:21.440> we<00:48:21.640> we<00:48:21.800> have<00:48:22.040> this<00:48:22.720> um<00:48:23.160> and<00:48:23.359> from<00:48:23.680> there 00:48:24.470 --> 00:48:24.480 align:start position:0% reason we we have this um and from there 00:48:24.480 --> 00:48:27.349 align:start position:0% reason we we have this um and from there uh<00:48:24.599> many<00:48:24.880> other<00:48:25.119> notes<00:48:25.760> can<00:48:25.960> be 00:48:27.349 --> 00:48:27.359 align:start position:0% uh many other notes can be 00:48:27.359 --> 00:48:30.150 align:start position:0% uh many other notes can be infer<00:48:28.359> and<00:48:28.520> then<00:48:28.880> we<00:48:29.040> start<00:48:29.480> the<00:48:29.680> this 00:48:30.150 --> 00:48:30.160 align:start position:0% infer and then we start the this 00:48:30.160 --> 00:48:32.829 align:start position:0% infer and then we start the this Discovery<00:48:30.480> V5<00:48:31.359> uh<00:48:31.520> protocol<00:48:32.440> which<00:48:32.559> is<00:48:32.680> in 00:48:32.829 --> 00:48:32.839 align:start position:0% Discovery V5 uh protocol which is in 00:48:32.839 --> 00:48:36.710 align:start position:0% Discovery V5 uh protocol which is in charge<00:48:33.160> of<00:48:34.119> um<00:48:35.119> discovering<00:48:35.599> other<00:48:35.920> nodes<00:48:36.480> in 00:48:36.710 --> 00:48:36.720 align:start position:0% charge of um discovering other nodes in 00:48:36.720 --> 00:48:39.150 align:start position:0% charge of um discovering other nodes in um<00:48:37.200> in<00:48:37.319> a<00:48:37.480> decentralized 00:48:39.150 --> 00:48:39.160 align:start position:0% um in a decentralized 00:48:39.160 --> 00:48:43.230 align:start position:0% um in a decentralized way<00:48:40.160> okay<00:48:40.440> this<00:48:40.559> is<00:48:40.960> part<00:48:41.160> of<00:48:41.480> the<00:48:42.480> just<00:48:42.880> of<00:48:43.040> the 00:48:43.230 --> 00:48:43.240 align:start position:0% way okay this is part of the just of the 00:48:43.240 --> 00:48:45.710 align:start position:0% way okay this is part of the just of the example<00:48:44.079> of<00:48:44.280> of<00:48:44.520> this 00:48:45.710 --> 00:48:45.720 align:start position:0% example of of this 00:48:45.720 --> 00:48:47.430 align:start position:0% example of of this application 00:48:47.430 --> 00:48:47.440 align:start position:0% application 00:48:47.440 --> 00:48:50.789 align:start position:0% application um<00:48:48.440> U<00:48:48.800> maybe<00:48:49.280> the<00:48:49.520> the<00:48:49.640> example<00:48:49.960> is<00:48:50.119> not<00:48:50.400> super 00:48:50.789 --> 00:48:50.799 align:start position:0% um U maybe the the example is not super 00:48:50.799 --> 00:48:53.630 align:start position:0% um U maybe the the example is not super idiomatic<00:48:51.520> in<00:48:51.680> terms<00:48:52.000> of<00:48:52.480> rust<00:48:53.000> at<00:48:53.119> the<00:48:53.240> moment 00:48:53.630 --> 00:48:53.640 align:start position:0% idiomatic in terms of rust at the moment 00:48:53.640 --> 00:48:56.789 align:start position:0% idiomatic in terms of rust at the moment but<00:48:53.839> it's<00:48:54.119> just<00:48:55.119> uh<00:48:55.319> a<00:48:55.520> proof<00:48:55.760> of<00:48:55.960> concept<00:48:56.480> uh 00:48:56.789 --> 00:48:56.799 align:start position:0% but it's just uh a proof of concept uh 00:48:56.799 --> 00:48:59.630 align:start position:0% but it's just uh a proof of concept uh to<00:48:57.000> to<00:48:57.160> see<00:48:57.400> how<00:48:58.400> uh<00:48:58.599> waku<00:48:58.920> note<00:48:59.200> can<00:48:59.359> be 00:48:59.630 --> 00:48:59.640 align:start position:0% to to see how uh waku note can be 00:48:59.640 --> 00:49:01.309 align:start position:0% to to see how uh waku note can be integrated<00:49:00.200> in<00:49:00.400> in 00:49:01.309 --> 00:49:01.319 align:start position:0% integrated in in 00:49:01.319 --> 00:49:04.030 align:start position:0% integrated in in Rust<00:49:02.319> and<00:49:02.599> in<00:49:02.760> this<00:49:02.960> particular<00:49:03.440> case<00:49:03.880> the 00:49:04.030 --> 00:49:04.040 align:start position:0% Rust and in this particular case the 00:49:04.040 --> 00:49:06.990 align:start position:0% Rust and in this particular case the main<00:49:04.280> purpose<00:49:04.599> of<00:49:04.799> the<00:49:05.000> application<00:49:05.680> or<00:49:06.680> what 00:49:06.990 --> 00:49:07.000 align:start position:0% main purpose of the application or what 00:49:07.000 --> 00:49:09.870 align:start position:0% main purpose of the application or what the<00:49:07.440> the<00:49:07.599> Wu<00:49:07.880> note<00:49:08.119> is<00:49:08.240> used<00:49:08.559> in<00:49:08.720> this<00:49:08.880> case<00:49:09.640> is 00:49:09.870 --> 00:49:09.880 align:start position:0% the the Wu note is used in this case is 00:49:09.880 --> 00:49:14.109 align:start position:0% the the Wu note is used in this case is just<00:49:10.119> for<00:49:10.599> for<00:49:10.799> sharing<00:49:11.680> the<00:49:12.680> the<00:49:12.920> game<00:49:13.200> State 00:49:14.109 --> 00:49:14.119 align:start position:0% just for for sharing the the game State 00:49:14.119 --> 00:49:15.190 align:start position:0% just for for sharing the the game State across 00:49:15.190 --> 00:49:15.200 align:start position:0% across 00:49:15.200 --> 00:49:19.870 align:start position:0% across users<00:49:16.200> across<00:49:16.599> the<00:49:16.839> the 00:49:19.870 --> 00:49:19.880 align:start position:0% 00:49:19.880 --> 00:49:21.870 align:start position:0% players 00:49:21.870 --> 00:49:21.880 align:start position:0% players 00:49:21.880 --> 00:49:25.670 align:start position:0% players um<00:49:22.880> okay<00:49:23.160> and<00:49:23.760> given<00:49:24.040> that<00:49:24.280> we<00:49:24.520> have<00:49:25.079> uh<00:49:25.240> a<00:49:25.359> user 00:49:25.670 --> 00:49:25.680 align:start position:0% um okay and given that we have uh a user 00:49:25.680 --> 00:49:27.349 align:start position:0% um okay and given that we have uh a user interface 00:49:27.349 --> 00:49:27.359 align:start position:0% interface 00:49:27.359 --> 00:49:29.950 align:start position:0% interface and<00:49:28.359> and<00:49:28.599> something<00:49:29.040> important<00:49:29.440> to<00:49:29.640> to<00:49:29.760> bear 00:49:29.950 --> 00:49:29.960 align:start position:0% and and something important to to bear 00:49:29.960 --> 00:49:33.390 align:start position:0% and and something important to to bear in<00:49:30.119> mind<00:49:30.760> is<00:49:31.000> that<00:49:31.680> the<00:49:32.680> the<00:49:32.880> incoming 00:49:33.390 --> 00:49:33.400 align:start position:0% in mind is that the the incoming 00:49:33.400 --> 00:49:36.990 align:start position:0% in mind is that the the incoming messages<00:49:34.400> by<00:49:34.680> the<00:49:34.960> note<00:49:35.960> these<00:49:36.160> messages<00:49:36.720> are 00:49:36.990 --> 00:49:37.000 align:start position:0% messages by the note these messages are 00:49:37.000 --> 00:49:41.430 align:start position:0% messages by the note these messages are being<00:49:37.280> handled<00:49:38.559> by<00:49:39.559> by<00:49:39.799> the<00:49:40.160> LI<00:49:40.599> Li<00:49:40.880> waku<00:49:41.280> which 00:49:41.430 --> 00:49:41.440 align:start position:0% being handled by by the LI Li waku which 00:49:41.440 --> 00:49:44.030 align:start position:0% being handled by by the LI Li waku which is<00:49:41.559> implemented<00:49:42.000> in<00:49:42.119> Nim<00:49:43.079> and<00:49:43.599> something 00:49:44.030 --> 00:49:44.040 align:start position:0% is implemented in Nim and something 00:49:44.040 --> 00:49:48.510 align:start position:0% is implemented in Nim and something important<00:49:44.400> to<00:49:44.920> mention<00:49:45.319> is<00:49:45.559> that<00:49:46.559> this<00:49:47.520> um 00:49:48.510 --> 00:49:48.520 align:start position:0% important to mention is that this um 00:49:48.520 --> 00:49:52.190 align:start position:0% important to mention is that this um guacu<00:49:48.920> note<00:49:49.480> is<00:49:49.640> running<00:49:50.240> in<00:49:50.400> a<00:49:50.760> separate<00:49:51.680> uh 00:49:52.190 --> 00:49:52.200 align:start position:0% guacu note is running in a separate uh 00:49:52.200 --> 00:49:56.069 align:start position:0% guacu note is running in a separate uh thread<00:49:53.200> and<00:49:53.680> we<00:49:53.839> need<00:49:54.400> to<00:49:55.040> and<00:49:55.240> the<00:49:55.400> liwu 00:49:56.069 --> 00:49:56.079 align:start position:0% thread and we need to and the liwu 00:49:56.079 --> 00:49:57.670 align:start position:0% thread and we need to and the liwu establishes<00:49:56.520> a<00:49:56.839> a 00:49:57.670 --> 00:49:57.680 align:start position:0% establishes a a 00:49:57.680 --> 00:50:01.150 align:start position:0% establishes a a communication<00:49:58.680> U<00:49:59.119> with<00:49:59.400> this<00:49:59.880> threat<00:50:00.880> this 00:50:01.150 --> 00:50:01.160 align:start position:0% communication U with this threat this 00:50:01.160 --> 00:50:05.109 align:start position:0% communication U with this threat this this<00:50:01.280> is<00:50:01.440> needed<00:50:02.200> because<00:50:02.680> the<00:50:03.480> name<00:50:04.079> run<00:50:04.440> time 00:50:05.109 --> 00:50:05.119 align:start position:0% this is needed because the name run time 00:50:05.119 --> 00:50:07.910 align:start position:0% this is needed because the name run time uh<00:50:05.319> should<00:50:05.720> run<00:50:06.520> separately<00:50:07.200> from<00:50:07.480> any<00:50:07.680> other 00:50:07.910 --> 00:50:07.920 align:start position:0% uh should run separately from any other 00:50:07.920 --> 00:50:11.870 align:start position:0% uh should run separately from any other run<00:50:08.240> time<00:50:08.960> such<00:50:09.119> as<00:50:09.400> the<00:50:09.559> the<00:50:09.760> rust<00:50:10.760> golang<00:50:11.760> uh 00:50:11.870 --> 00:50:11.880 align:start position:0% run time such as the the rust golang uh 00:50:11.880 --> 00:50:16.670 align:start position:0% run time such as the the rust golang uh noes<00:50:12.839> Etc<00:50:13.839> uh<00:50:13.960> in<00:50:14.079> order<00:50:14.880> to<00:50:15.880> uh<00:50:16.000> to<00:50:16.240> to<00:50:16.359> make<00:50:16.480> it 00:50:16.670 --> 00:50:16.680 align:start position:0% noes Etc uh in order to uh to to make it 00:50:16.680 --> 00:50:21.670 align:start position:0% noes Etc uh in order to uh to to make it work<00:50:17.880> properly<00:50:18.880> uh<00:50:19.079> because<00:50:20.200> um<00:50:21.200> as<00:50:21.359> we<00:50:21.520> are 00:50:21.670 --> 00:50:21.680 align:start position:0% work properly uh because um as we are 00:50:21.680 --> 00:50:24.510 align:start position:0% work properly uh because um as we are using<00:50:22.240> nowadays<00:50:22.760> Nim<00:50:23.440> we<00:50:23.520> are<00:50:23.640> using<00:50:23.920> it<00:50:24.400> with 00:50:24.510 --> 00:50:24.520 align:start position:0% using nowadays Nim we are using it with 00:50:24.520 --> 00:50:27.670 align:start position:0% using nowadays Nim we are using it with a<00:50:24.720> garbage<00:50:25.319> collector<00:50:26.319> and<00:50:26.799> it's<00:50:27.079> need<00:50:27.520> it 00:50:27.670 --> 00:50:27.680 align:start position:0% a garbage collector and it's need it 00:50:27.680 --> 00:50:30.390 align:start position:0% a garbage collector and it's need it needs<00:50:27.960> to<00:50:28.240> to<00:50:28.400> run<00:50:28.960> on<00:50:29.240> its<00:50:29.480> own 00:50:30.390 --> 00:50:30.400 align:start position:0% needs to to run on its own 00:50:30.400 --> 00:50:33.309 align:start position:0% needs to to run on its own thread<00:50:31.400> and<00:50:31.640> something<00:50:31.920> I<00:50:32.040> wanted<00:50:32.280> to 00:50:33.309 --> 00:50:33.319 align:start position:0% thread and something I wanted to 00:50:33.319 --> 00:50:37.030 align:start position:0% thread and something I wanted to mention<00:50:34.319> is<00:50:34.520> that<00:50:35.319> um<00:50:36.119> all<00:50:36.359> the<00:50:36.559> incoming 00:50:37.030 --> 00:50:37.040 align:start position:0% mention is that um all the incoming 00:50:37.040 --> 00:50:41.470 align:start position:0% mention is that um all the incoming messages<00:50:37.839> sorry 00:50:41.470 --> 00:50:41.480 align:start position:0% 00:50:41.480 --> 00:50:45.990 align:start position:0% for<00:50:42.480> they<00:50:42.680> come<00:50:43.200> in<00:50:43.960> in<00:50:44.160> this 00:50:45.990 --> 00:50:46.000 align:start position:0% for they come in in this 00:50:46.000 --> 00:50:50.270 align:start position:0% for they come in in this closure<00:50:47.000> in<00:50:47.280> here<00:50:48.160> um<00:50:48.640> as<00:50:49.040> we<00:50:49.319> as<00:50:49.760> the<00:50:49.960> example 00:50:50.270 --> 00:50:50.280 align:start position:0% closure in here um as we as the example 00:50:50.280 --> 00:50:52.750 align:start position:0% closure in here um as we as the example is<00:50:50.400> implemented<00:50:51.000> now<00:50:51.280> it<00:50:51.559> starts<00:50:52.000> the<00:50:52.240> waku 00:50:52.750 --> 00:50:52.760 align:start position:0% is implemented now it starts the waku 00:50:52.760 --> 00:50:55.430 align:start position:0% is implemented now it starts the waku node<00:50:53.760> and<00:50:53.960> then<00:50:54.440> we 00:50:55.430 --> 00:50:55.440 align:start position:0% node and then we 00:50:55.440 --> 00:50:58.750 align:start position:0% node and then we pass<00:50:56.440> a<00:50:56.760> uh<00:50:57.160> we<00:50:57.359> subscribe<00:50:57.960> the<00:50:58.119> node<00:50:58.400> to<00:50:58.599> a 00:50:58.750 --> 00:50:58.760 align:start position:0% pass a uh we subscribe the node to a 00:50:58.760 --> 00:51:03.069 align:start position:0% pass a uh we subscribe the node to a certain<00:50:59.359> topic<00:51:00.079> just<00:51:00.520> the<00:51:00.799> game<00:51:01.319> topic<00:51:02.319> and<00:51:02.760> it 00:51:03.069 --> 00:51:03.079 align:start position:0% certain topic just the game topic and it 00:51:03.079 --> 00:51:06.750 align:start position:0% certain topic just the game topic and it we<00:51:03.319> pass<00:51:03.960> a<00:51:04.119> closure<00:51:05.000> which<00:51:05.160> is<00:51:05.319> in<00:51:05.520> charge<00:51:05.960> of 00:51:06.750 --> 00:51:06.760 align:start position:0% we pass a closure which is in charge of 00:51:06.760 --> 00:51:09.190 align:start position:0% we pass a closure which is in charge of um<00:51:07.440> getting<00:51:07.839> the<00:51:08.040> incoming 00:51:09.190 --> 00:51:09.200 align:start position:0% um getting the incoming 00:51:09.200 --> 00:51:12.910 align:start position:0% um getting the incoming messages<00:51:10.200> and<00:51:10.760> with<00:51:11.359> this<00:51:12.280> uh<00:51:12.520> what<00:51:12.720> we<00:51:12.799> are 00:51:12.910 --> 00:51:12.920 align:start position:0% messages and with this uh what we are 00:51:12.920 --> 00:51:16.750 align:start position:0% messages and with this uh what we are doing<00:51:13.200> is<00:51:13.559> we<00:51:13.680> are<00:51:14.680> um<00:51:15.000> notifying<00:51:15.760> the<00:51:16.599> the 00:51:16.750 --> 00:51:16.760 align:start position:0% doing is we are um notifying the the 00:51:16.760 --> 00:51:19.230 align:start position:0% doing is we are um notifying the the main<00:51:17.000> threat<00:51:17.839> about<00:51:18.160> the<00:51:18.359> incoming<00:51:18.799> message 00:51:19.230 --> 00:51:19.240 align:start position:0% main threat about the incoming message 00:51:19.240 --> 00:51:22.910 align:start position:0% main threat about the incoming message so<00:51:19.400> that<00:51:19.559> the<00:51:19.760> game<00:51:20.040> State<00:51:20.400> can<00:51:20.920> be 00:51:22.910 --> 00:51:22.920 align:start position:0% so that the game State can be 00:51:22.920 --> 00:51:27.270 align:start position:0% so that the game State can be um<00:51:23.920> updated<00:51:24.799> when<00:51:25.359> when<00:51:25.680> you<00:51:26.680> and<00:51:26.839> now<00:51:27.119> let 00:51:27.270 --> 00:51:27.280 align:start position:0% um updated when when you and now let 00:51:27.280 --> 00:51:31.069 align:start position:0% um updated when when you and now let let's<00:51:27.520> do<00:51:27.760> a<00:51:28.079> a<00:51:28.359> quick<00:51:29.359> a<00:51:29.520> small 00:51:31.069 --> 00:51:31.079 align:start position:0% let's do a a quick a small 00:51:31.079 --> 00:51:35.230 align:start position:0% let's do a a quick a small demo<00:51:32.079> uh<00:51:32.240> in<00:51:32.440> this<00:51:33.119> uh<00:51:33.240> in<00:51:33.359> this<00:51:33.599> case<00:51:34.160> uh<00:51:34.359> just 00:51:35.230 --> 00:51:35.240 align:start position:0% demo uh in this uh in this case uh just 00:51:35.240 --> 00:51:38.109 align:start position:0% demo uh in this uh in this case uh just we<00:51:35.440> have<00:51:35.640> two<00:51:35.920> inst<00:51:36.520> instances<00:51:37.520> of<00:51:37.720> the<00:51:37.880> TIC 00:51:38.109 --> 00:51:38.119 align:start position:0% we have two inst instances of the TIC 00:51:38.119 --> 00:51:39.670 align:start position:0% we have two inst instances of the TIC Taco 00:51:39.670 --> 00:51:39.680 align:start position:0% Taco 00:51:39.680 --> 00:51:42.990 align:start position:0% Taco application<00:51:40.680> uh<00:51:41.000> on<00:51:41.119> the<00:51:41.319> left<00:51:41.960> um<00:51:42.599> each<00:51:42.760> of 00:51:42.990 --> 00:51:43.000 align:start position:0% application uh on the left um each of 00:51:43.000 --> 00:51:46.990 align:start position:0% application uh on the left um each of them<00:51:43.920> is<00:51:44.319> running<00:51:45.119> a<00:51:45.680> a<00:51:45.960> waku 00:51:46.990 --> 00:51:47.000 align:start position:0% them is running a a waku 00:51:47.000 --> 00:51:49.870 align:start position:0% them is running a a waku node<00:51:48.000> then<00:51:48.160> we<00:51:48.319> say<00:51:48.720> this<00:51:49.040> is<00:51:49.200> going<00:51:49.400> to<00:51:49.640> play 00:51:49.870 --> 00:51:49.880 align:start position:0% node then we say this is going to play 00:51:49.880 --> 00:51:54.190 align:start position:0% node then we say this is going to play as<00:51:50.240> X<00:51:50.799> and<00:51:51.000> this<00:51:51.119> is<00:51:51.280> going<00:51:51.440> to<00:51:51.599> play<00:51:51.760> as 00:51:54.190 --> 00:51:54.200 align:start position:0% 00:51:54.200 --> 00:51:59.030 align:start position:0% O<00:51:55.200> then 00:51:59.030 --> 00:51:59.040 align:start position:0% 00:51:59.040 --> 00:52:05.349 align:start position:0% they 00:52:05.349 --> 00:52:05.359 align:start position:0% 00:52:05.359 --> 00:52:08.549 align:start position:0% can<00:52:06.359> they<00:52:06.440> can<00:52:06.640> play<00:52:06.920> and<00:52:07.520> well<00:52:07.799> it's<00:52:08.160> a<00:52:08.359> very 00:52:08.549 --> 00:52:08.559 align:start position:0% can they can play and well it's a very 00:52:08.559 --> 00:52:14.549 align:start position:0% can they can play and well it's a very simple<00:52:09.559> example<00:52:10.119> in<00:52:10.280> this<00:52:10.480> case<00:52:11.400> player<00:52:12.400> x 00:52:14.549 --> 00:52:14.559 align:start position:0% simple example in this case player x 00:52:14.559 --> 00:52:18.190 align:start position:0% simple example in this case player x one<00:52:15.559> and<00:52:16.240> okay<00:52:16.799> uh<00:52:17.000> something<00:52:17.319> else<00:52:17.720> I<00:52:17.839> wanted 00:52:18.190 --> 00:52:18.200 align:start position:0% one and okay uh something else I wanted 00:52:18.200 --> 00:52:21.030 align:start position:0% one and okay uh something else I wanted to<00:52:19.040> to<00:52:19.200> share<00:52:19.599> is<00:52:20.040> in 00:52:21.030 --> 00:52:21.040 align:start position:0% to to share is in 00:52:21.040 --> 00:52:28.309 align:start position:0% to to share is in this<00:52:22.040> in<00:52:22.200> this<00:52:22.599> presentation<00:52:23.359> sorry 00:52:28.309 --> 00:52:28.319 align:start position:0% 00:52:28.319 --> 00:52:30.890 align:start position:0% feel<00:52:28.559> free<00:52:28.799> to<00:52:29.000> to<00:52:29.160> clone<00:52:29.559> this 00:52:30.890 --> 00:52:30.900 align:start position:0% feel free to to clone this 00:52:30.900 --> 00:52:31.990 align:start position:0% feel free to to clone this [Music] 00:52:31.990 --> 00:52:32.000 align:start position:0% [Music] 00:52:32.000 --> 00:52:34.190 align:start position:0% [Music] example<00:52:33.000> uh<00:52:33.119> because<00:52:33.359> we<00:52:33.440> are<00:52:33.599> going<00:52:33.760> to<00:52:34.040> to 00:52:34.190 --> 00:52:34.200 align:start position:0% example uh because we are going to to 00:52:34.200 --> 00:52:40.150 align:start position:0% example uh because we are going to to play<00:52:34.480> a<00:52:34.559> little<00:52:34.760> bit<00:52:35.040> with 00:52:40.150 --> 00:52:40.160 align:start position:0% 00:52:40.160 --> 00:52:44.349 align:start position:0% it<00:52:41.160> it's<00:52:41.520> just<00:52:42.160> um<00:52:43.160> you<00:52:43.240> will<00:52:43.440> find<00:52:43.680> it<00:52:43.960> in<00:52:44.160> the 00:52:44.349 --> 00:52:44.359 align:start position:0% it it's just um you will find it in the 00:52:44.359 --> 00:52:49.910 align:start position:0% it it's just um you will find it in the in<00:52:44.480> the<00:52:44.599> same<00:52:45.359> wakas<00:52:45.920> bindings<00:52:47.280> ripo<00:52:48.400> and<00:52:49.400> it's 00:52:49.910 --> 00:52:49.920 align:start position:0% in the same wakas bindings ripo and it's 00:52:49.920 --> 00:52:53.150 align:start position:0% in the same wakas bindings ripo and it's it's<00:52:50.040> a<00:52:50.240> bit<00:52:50.799> uh<00:52:50.960> more<00:52:51.640> simpler<00:52:52.319> and<00:52:52.839> what<00:52:53.000> it 00:52:53.150 --> 00:52:53.160 align:start position:0% it's a bit uh more simpler and what it 00:52:53.160 --> 00:52:56.829 align:start position:0% it's a bit uh more simpler and what it does 00:52:56.829 --> 00:52:56.839 align:start position:0% 00:52:56.839 --> 00:52:59.230 align:start position:0% it<00:52:57.280> uh<00:52:57.400> creates<00:52:57.960> um<00:52:58.480> it's<00:52:58.680> more<00:52:58.799> or<00:52:58.960> less<00:52:59.119> the 00:52:59.230 --> 00:52:59.240 align:start position:0% it uh creates um it's more or less the 00:52:59.240 --> 00:53:03.190 align:start position:0% it uh creates um it's more or less the same<00:53:00.160> but<00:53:00.760> um<00:53:01.000> more 00:53:03.190 --> 00:53:03.200 align:start position:0% same but um more 00:53:03.200 --> 00:53:08.470 align:start position:0% same but um more simplified<00:53:04.200> it<00:53:04.520> creates<00:53:05.160> a<00:53:05.520> w<00:53:06.240> um<00:53:06.640> waku 00:53:08.470 --> 00:53:08.480 align:start position:0% simplified it creates a w um waku 00:53:08.480 --> 00:53:12.069 align:start position:0% simplified it creates a w um waku note<00:53:09.480> we<00:53:09.599> are<00:53:09.839> passing<00:53:10.640> uh 00:53:12.069 --> 00:53:12.079 align:start position:0% note we are passing uh 00:53:12.079 --> 00:53:14.910 align:start position:0% note we are passing uh sharts<00:53:13.079> uh<00:53:13.280> this<00:53:13.480> this<00:53:13.599> is<00:53:14.000> uh<00:53:14.359> the<00:53:14.480> the<00:53:14.599> chart 00:53:14.910 --> 00:53:14.920 align:start position:0% sharts uh this this is uh the the chart 00:53:14.920 --> 00:53:17.829 align:start position:0% sharts uh this this is uh the the chart thing<00:53:15.119> is<00:53:15.720> uh<00:53:15.880> something<00:53:16.400> that<00:53:16.839> is<00:53:17.359> uh<00:53:17.480> needed 00:53:17.829 --> 00:53:17.839 align:start position:0% thing is uh something that is uh needed 00:53:17.839 --> 00:53:22.230 align:start position:0% thing is uh something that is uh needed to<00:53:18.599> split<00:53:19.000> traffic<00:53:19.720> in<00:53:19.920> in<00:53:20.040> a<00:53:20.119> certain<00:53:20.480> way 00:53:22.230 --> 00:53:22.240 align:start position:0% to split traffic in in a certain way 00:53:22.240 --> 00:53:24.950 align:start position:0% to split traffic in in a certain way um<00:53:23.240> it's<00:53:23.880> um<00:53:24.079> it<00:53:24.200> can 00:53:24.950 --> 00:53:24.960 align:start position:0% um it's um it can 00:53:24.960 --> 00:53:30.270 align:start position:0% um it's um it can be<00:53:25.960> understood<00:53:26.559> as<00:53:26.680> a<00:53:27.079> way<00:53:27.280> of<00:53:27.880> um<00:53:28.839> channels<00:53:29.520> or 00:53:30.270 --> 00:53:30.280 align:start position:0% be understood as a way of um channels or 00:53:30.280 --> 00:53:33.670 align:start position:0% be understood as a way of um channels or communication<00:53:30.839> channels<00:53:31.400> in<00:53:31.640> in<00:53:31.799> Gossip<00:53:32.680> sa 00:53:33.670 --> 00:53:33.680 align:start position:0% communication channels in in Gossip sa 00:53:33.680 --> 00:53:36.870 align:start position:0% communication channels in in Gossip sa uh<00:53:34.000> then<00:53:34.160> we<00:53:34.280> are<00:53:34.920> establishing<00:53:35.920> um<00:53:36.400> maximum 00:53:36.870 --> 00:53:36.880 align:start position:0% uh then we are establishing um maximum 00:53:36.880 --> 00:53:38.870 align:start position:0% uh then we are establishing um maximum of<00:53:37.119> 1 00:53:38.870 --> 00:53:38.880 align:start position:0% of 1 00:53:38.880 --> 00:53:43.270 align:start position:0% of 1 Megabyte<00:53:39.880> uh<00:53:40.040> L<00:53:40.680> level 00:53:43.270 --> 00:53:43.280 align:start position:0% Megabyte uh L level 00:53:43.280 --> 00:53:49.589 align:start position:0% Megabyte uh L level uh<00:53:44.280> content<00:53:44.799> topics<00:53:45.480> uh<00:53:45.640> sorry<00:53:46.040> no<00:53:46.440> uh<00:53:46.640> this<00:53:46.799> is 00:53:49.589 --> 00:53:49.599 align:start position:0% 00:53:49.599 --> 00:53:53.990 align:start position:0% the<00:53:50.599> P<00:53:50.960> subtopic<00:53:51.960> we<00:53:52.400> set<00:53:52.799> the<00:53:53.040> keep<00:53:53.240> alive<00:53:53.599> to 00:53:53.990 --> 00:53:54.000 align:start position:0% the P subtopic we set the keep alive to 00:53:54.000 --> 00:53:58.670 align:start position:0% the P subtopic we set the keep alive to true<00:53:55.000> and<00:53:55.520> as<00:53:55.720> we<00:53:55.960> show<00:53:56.680> uh<00:53:56.920> saw<00:53:57.359> earlier<00:53:57.720> on<00:53:58.559> uh 00:53:58.670 --> 00:53:58.680 align:start position:0% true and as we show uh saw earlier on uh 00:53:58.680 --> 00:54:03.510 align:start position:0% true and as we show uh saw earlier on uh we<00:53:58.799> enabled<00:53:59.319> the<00:53:59.760> DNS<00:54:00.400> Discovery<00:54:01.000> and<00:54:02.000> dis 00:54:03.510 --> 00:54:03.520 align:start position:0% we enabled the DNS Discovery and dis 00:54:03.520 --> 00:54:07.470 align:start position:0% we enabled the DNS Discovery and dis B5<00:54:04.520> okay<00:54:04.880> and<00:54:05.079> in<00:54:05.240> this<00:54:05.599> case<00:54:06.599> uh<00:54:06.839> after<00:54:07.200> that 00:54:07.470 --> 00:54:07.480 align:start position:0% B5 okay and in this case uh after that 00:54:07.480 --> 00:54:12.470 align:start position:0% B5 okay and in this case uh after that after<00:54:07.720> creating<00:54:08.119> the<00:54:08.440> note<00:54:09.440> uh<00:54:09.559> we<00:54:09.760> just 00:54:12.470 --> 00:54:12.480 align:start position:0% 00:54:12.480 --> 00:54:15.829 align:start position:0% started<00:54:13.480> and<00:54:13.720> then<00:54:13.960> we<00:54:14.160> establish<00:54:15.079> uh<00:54:15.640> we 00:54:15.829 --> 00:54:15.839 align:start position:0% started and then we establish uh we 00:54:15.839 --> 00:54:21.270 align:start position:0% started and then we establish uh we subscribe<00:54:16.640> to<00:54:17.079> to<00:54:17.200> the<00:54:17.720> waku<00:54:18.720> to<00:54:18.880> the<00:54:19.200> to<00:54:19.359> the 00:54:21.270 --> 00:54:21.280 align:start position:0% subscribe to to the waku to the to the 00:54:21.280 --> 00:54:25.230 align:start position:0% subscribe to to the waku to the to the topic<00:54:22.280> and<00:54:22.520> that's<00:54:22.760> it<00:54:23.359> and<00:54:24.359> in<00:54:24.520> this<00:54:24.720> example 00:54:25.230 --> 00:54:25.240 align:start position:0% topic and that's it and in this example 00:54:25.240 --> 00:54:27.750 align:start position:0% topic and that's it and in this example it<00:54:25.480> just<00:54:25.880> uh<00:54:26.000> creates<00:54:26.400> a<00:54:26.559> note<00:54:27.000> start<00:54:27.400> it 00:54:27.750 --> 00:54:27.760 align:start position:0% it just uh creates a note start it 00:54:27.760 --> 00:54:30.390 align:start position:0% it just uh creates a note start it subscribe<00:54:28.240> to<00:54:28.359> the<00:54:28.480> topic<00:54:28.760> and<00:54:28.920> just<00:54:29.200> wait<00:54:29.920> um 00:54:30.390 --> 00:54:30.400 align:start position:0% subscribe to the topic and just wait um 00:54:30.400 --> 00:54:34.549 align:start position:0% subscribe to the topic and just wait um until<00:54:30.680> a<00:54:31.200> contrl<00:54:31.640> c<00:54:32.000> is<00:54:32.359> pressed<00:54:33.359> and<00:54:33.559> if<00:54:33.839> we<00:54:34.400> if 00:54:34.549 --> 00:54:34.559 align:start position:0% until a contrl c is pressed and if we if 00:54:34.559 --> 00:54:45.230 align:start position:0% until a contrl c is pressed and if we if we<00:54:34.720> run<00:54:34.960> it<00:54:35.559> we<00:54:35.640> will<00:54:35.839> see 00:54:45.230 --> 00:54:45.240 align:start position:0% 00:54:45.240 --> 00:54:48.630 align:start position:0% that<00:54:46.240> uh<00:54:46.440> yeah<00:54:46.599> these<00:54:46.799> logs<00:54:47.200> are<00:54:47.520> coming<00:54:47.920> from 00:54:48.630 --> 00:54:48.640 align:start position:0% that uh yeah these logs are coming from 00:54:48.640 --> 00:54:52.510 align:start position:0% that uh yeah these logs are coming from the<00:54:49.200> implementation<00:54:50.200> of<00:54:50.920> name 00:54:52.510 --> 00:54:52.520 align:start position:0% the implementation of name 00:54:52.520 --> 00:54:54.230 align:start position:0% the implementation of name guo 00:54:54.230 --> 00:54:54.240 align:start position:0% guo 00:54:54.240 --> 00:55:02.470 align:start position:0% guo and<00:54:55.240> yeah 00:55:02.470 --> 00:55:02.480 align:start position:0% 00:55:02.480 --> 00:55:04.069 align:start position:0% okay<00:55:02.640> and<00:55:02.880> as<00:55:03.000> you<00:55:03.119> can<00:55:03.240> see<00:55:03.520> the<00:55:03.640> note<00:55:03.920> is 00:55:04.069 --> 00:55:04.079 align:start position:0% okay and as you can see the note is 00:55:04.079 --> 00:55:06.910 align:start position:0% okay and as you can see the note is starting<00:55:04.440> to<00:55:04.680> receive<00:55:05.599> um<00:55:05.839> Ray<00:55:06.359> messages 00:55:06.910 --> 00:55:06.920 align:start position:0% starting to receive um Ray messages 00:55:06.920 --> 00:55:11.549 align:start position:0% starting to receive um Ray messages because<00:55:07.319> it's<00:55:07.559> subscribed 00:55:11.549 --> 00:55:11.559 align:start position:0% 00:55:11.559 --> 00:55:15.549 align:start position:0% to<00:55:12.559> and<00:55:13.119> yeah<00:55:13.240> and<00:55:13.599> that's<00:55:13.799> it<00:55:14.119> and<00:55:14.799> we<00:55:14.960> are 00:55:15.549 --> 00:55:15.559 align:start position:0% to and yeah and that's it and we are 00:55:15.559 --> 00:55:17.789 align:start position:0% to and yeah and that's it and we are receiving<00:55:15.960> messages<00:55:16.480> from<00:55:16.920> from<00:55:17.079> the 00:55:17.789 --> 00:55:17.799 align:start position:0% receiving messages from from the 00:55:17.799 --> 00:55:18.790 align:start position:0% receiving messages from from the network 00:55:18.790 --> 00:55:18.800 align:start position:0% network 00:55:18.800 --> 00:55:20.829 align:start position:0% network [Music] 00:55:20.829 --> 00:55:20.839 align:start position:0% [Music] 00:55:20.839 --> 00:55:24.950 align:start position:0% [Music] um<00:55:21.839> they<00:55:22.400> I<00:55:22.480> believe<00:55:22.880> they<00:55:23.039> come<00:55:23.359> from<00:55:24.280> estos 00:55:24.950 --> 00:55:24.960 align:start position:0% um they I believe they come from estos 00:55:24.960 --> 00:55:29.150 align:start position:0% um they I believe they come from estos because<00:55:25.359> I<00:55:25.559> I<00:55:25.680> connected<00:55:26.039> to<00:55:26.440> to<00:55:26.640> the<00:55:26.960> estos<00:55:27.960> um 00:55:29.150 --> 00:55:29.160 align:start position:0% because I I connected to to the estos um 00:55:29.160 --> 00:55:32.349 align:start position:0% because I I connected to to the estos um Network<00:55:30.160> and<00:55:30.520> well<00:55:31.000> um 00:55:32.349 --> 00:55:32.359 align:start position:0% Network and well um 00:55:32.359 --> 00:55:35.390 align:start position:0% Network and well um just<00:55:33.359> uh<00:55:33.760> that's<00:55:34.319> that's<00:55:34.480> it<00:55:34.839> I<00:55:34.920> don't<00:55:35.039> know<00:55:35.160> if 00:55:35.390 --> 00:55:35.400 align:start position:0% just uh that's that's it I don't know if 00:55:35.400 --> 00:55:38.150 align:start position:0% just uh that's that's it I don't know if there<00:55:35.720> there<00:55:36.119> there<00:55:36.240> are<00:55:36.440> questions<00:55:37.319> or 00:55:38.150 --> 00:55:38.160 align:start position:0% there there there are questions or 00:55:38.160 --> 00:55:41.589 align:start position:0% there there there are questions or comments<00:55:38.599> or<00:55:39.480> would<00:55:39.640> you<00:55:39.760> like<00:55:40.160> to<00:55:41.160> to<00:55:41.319> see 00:55:41.589 --> 00:55:41.599 align:start position:0% comments or would you like to to see 00:55:41.599 --> 00:55:52.349 align:start position:0% comments or would you like to to see something<00:55:42.440> else 00:55:52.349 --> 00:55:52.359 align:start position:0% 00:55:52.359 --> 00:55:57.549 align:start position:0% or<00:55:53.359> how<00:55:53.680> how<00:55:53.799> is<00:55:53.960> the<00:55:54.200> DHD<00:55:55.200> look<00:55:55.559> for<00:55:55.920> the 00:55:57.549 --> 00:55:57.559 align:start position:0% or how how is the DHD look for the 00:55:57.559 --> 00:56:02.309 align:start position:0% or how how is the DHD look for the Network<00:55:58.680> like<00:55:59.680> what<00:55:59.880> flavor<00:56:00.559> of<00:56:00.960> DHD<00:56:01.960> how<00:56:02.079> is 00:56:02.309 --> 00:56:02.319 align:start position:0% Network like what flavor of DHD how is 00:56:02.319 --> 00:56:05.630 align:start position:0% Network like what flavor of DHD how is the<00:56:02.520> the<00:56:02.640> DHD<00:56:03.160> look<00:56:03.400> up<00:56:03.920> um<00:56:04.640> being<00:56:04.880> done<00:56:05.280> or<00:56:05.480> you 00:56:05.630 --> 00:56:05.640 align:start position:0% the the DHD look up um being done or you 00:56:05.640 --> 00:56:06.950 align:start position:0% the the DHD look up um being done or you mean 00:56:06.950 --> 00:56:06.960 align:start position:0% mean 00:56:06.960 --> 00:56:10.069 align:start position:0% mean um<00:56:07.960> yeah<00:56:08.280> we<00:56:08.400> have<00:56:08.599> a<00:56:09.319> discovery<00:56:09.599> with<00:56:09.760> five 00:56:10.069 --> 00:56:10.079 align:start position:0% um yeah we have a discovery with five 00:56:10.079 --> 00:56:14.829 align:start position:0% um yeah we have a discovery with five client<00:56:10.839> and<00:56:11.680> it<00:56:12.000> it<00:56:12.280> performs<00:56:13.119> um<00:56:13.680> a<00:56:13.880> a<00:56:14.039> request 00:56:14.829 --> 00:56:14.839 align:start position:0% client and it it performs um a a request 00:56:14.839 --> 00:56:19.670 align:start position:0% client and it it performs um a a request to<00:56:15.839> to<00:56:16.200> the<00:56:17.200> to<00:56:17.680> to<00:56:17.839> to<00:56:17.960> the<00:56:18.039> network<00:56:18.480> and<00:56:18.640> it's 00:56:19.670 --> 00:56:19.680 align:start position:0% to to the to to to the network and it's 00:56:19.680 --> 00:56:22.150 align:start position:0% to to the to to to the network and it's uh<00:56:20.680> but<00:56:20.880> so 00:56:22.150 --> 00:56:22.160 align:start position:0% uh but so 00:56:22.160 --> 00:56:24.829 align:start position:0% uh but so what<00:56:23.160> like<00:56:23.359> how<00:56:23.520> does<00:56:23.680> it<00:56:23.960> decide<00:56:24.440> where<00:56:24.640> to 00:56:24.829 --> 00:56:24.839 align:start position:0% what like how does it decide where to 00:56:24.839 --> 00:56:27.549 align:start position:0% what like how does it decide where to Route<00:56:25.400> the<00:56:25.640> message<00:56:26.079> just<00:56:26.319> just<00:56:26.520> on<00:56:26.839> the<00:56:27.160> peer 00:56:27.549 --> 00:56:27.559 align:start position:0% Route the message just just on the peer 00:56:27.559 --> 00:56:29.150 align:start position:0% Route the message just just on the peer scoring 00:56:29.150 --> 00:56:29.160 align:start position:0% scoring 00:56:29.160 --> 00:56:32.510 align:start position:0% scoring or<00:56:30.160> um<00:56:31.079> you<00:56:31.200> mean 00:56:32.510 --> 00:56:32.520 align:start position:0% or um you mean 00:56:32.520 --> 00:56:35.670 align:start position:0% or um you mean the<00:56:33.520> yeah<00:56:34.039> exactly 00:56:35.670 --> 00:56:35.680 align:start position:0% the yeah exactly 00:56:35.680 --> 00:56:39.430 align:start position:0% the yeah exactly the<00:56:36.680> the<00:56:36.920> the<00:56:37.079> messages<00:56:37.559> are<00:56:37.799> being<00:56:38.079> routed<00:56:38.839> by 00:56:39.430 --> 00:56:39.440 align:start position:0% the the the messages are being routed by 00:56:39.440 --> 00:56:41.309 align:start position:0% the the the messages are being routed by a<00:56:39.640> healthy 00:56:41.309 --> 00:56:41.319 align:start position:0% a healthy 00:56:41.319 --> 00:56:43.670 align:start position:0% a healthy mesh<00:56:42.319> if 00:56:43.670 --> 00:56:43.680 align:start position:0% mesh if 00:56:43.680 --> 00:56:47.390 align:start position:0% mesh if the<00:56:44.680> um<00:56:44.960> if<00:56:45.359> there<00:56:45.480> are<00:56:46.119> uh<00:56:46.480> peers<00:56:46.880> that<00:56:47.039> are 00:56:47.390 --> 00:56:47.400 align:start position:0% the um if there are uh peers that are 00:56:47.400 --> 00:56:51.270 align:start position:0% the um if there are uh peers that are misbehaving<00:56:48.520> or<00:56:49.520> are<00:56:49.960> are<00:56:50.520> spamming<00:56:51.000> the<00:56:51.160> the 00:56:51.270 --> 00:56:51.280 align:start position:0% misbehaving or are are spamming the the 00:56:51.280 --> 00:56:54.390 align:start position:0% misbehaving or are are spamming the the network<00:56:51.960> then<00:56:52.799> they<00:56:53.000> they<00:56:53.119> are<00:56:53.400> blocked<00:56:53.880> and 00:56:54.390 --> 00:56:54.400 align:start position:0% network then they they are blocked and 00:56:54.400 --> 00:57:06.150 align:start position:0% network then they they are blocked and they<00:56:54.559> don't<00:56:54.760> participate<00:56:55.280> in<00:56:55.480> the 00:57:06.150 --> 00:57:06.160 align:start position:0% 00:57:06.160 --> 00:57:10.950 align:start position:0% okay<00:57:06.920> um<00:57:07.880> in<00:57:08.079> that<00:57:08.319> case<00:57:09.400> uh<00:57:10.400> if<00:57:10.599> no<00:57:10.760> more 00:57:10.950 --> 00:57:10.960 align:start position:0% okay um in that case uh if no more 00:57:10.960 --> 00:57:43.670 align:start position:0% okay um in that case uh if no more question<00:57:11.480> think<00:57:12.039> ah<00:57:12.440> yes 00:57:43.670 --> 00:57:43.680 align:start position:0% 00:57:43.680 --> 00:57:46.309 align:start position:0% uh<00:57:44.680> yeah<00:57:44.839> thank<00:57:45.079> thank<00:57:45.200> you<00:57:45.319> for<00:57:45.440> the<00:57:45.599> question 00:57:46.309 --> 00:57:46.319 align:start position:0% uh yeah thank thank you for the question 00:57:46.319 --> 00:57:50.309 align:start position:0% uh yeah thank thank you for the question uh<00:57:46.760> good<00:57:47.039> question<00:57:47.280> indeed<00:57:48.039> um<00:57:49.039> the<00:57:49.359> as<00:57:49.920> s 00:57:50.309 --> 00:57:50.319 align:start position:0% uh good question indeed um the as s 00:57:50.319 --> 00:57:54.150 align:start position:0% uh good question indeed um the as s mentioned<00:57:51.160> um<00:57:52.160> the<00:57:52.680> gossip<00:57:53.039> sa<00:57:53.480> itself<00:57:54.039> it 00:57:54.150 --> 00:57:54.160 align:start position:0% mentioned um the gossip sa itself it 00:57:54.160 --> 00:57:56.630 align:start position:0% mentioned um the gossip sa itself it doesn't<00:57:54.520> guarantee<00:57:55.520> the<00:57:55.760> um 00:57:56.630 --> 00:57:56.640 align:start position:0% doesn't guarantee the um 00:57:56.640 --> 00:57:59.309 align:start position:0% doesn't guarantee the um um<00:57:56.839> a<00:57:56.960> certain<00:57:57.280> message<00:57:57.640> to<00:57:57.960> to<00:57:58.160> reach<00:57:58.799> uh<00:57:59.200> a 00:57:59.309 --> 00:57:59.319 align:start position:0% um a certain message to to reach uh a 00:57:59.319 --> 00:58:01.710 align:start position:0% um a certain message to to reach uh a certain<00:57:59.640> point<00:58:00.520> and<00:58:00.680> for<00:58:00.839> that<00:58:01.039> reason<00:58:01.359> we<00:58:01.480> are 00:58:01.710 --> 00:58:01.720 align:start position:0% certain point and for that reason we are 00:58:01.720 --> 00:58:05.270 align:start position:0% certain point and for that reason we are working<00:58:02.079> on<00:58:02.920> uh<00:58:03.160> on<00:58:03.559> implementing<00:58:04.559> uh<00:58:04.839> what<00:58:05.000> we 00:58:05.270 --> 00:58:05.280 align:start position:0% working on uh on implementing uh what we 00:58:05.280 --> 00:58:08.910 align:start position:0% working on uh on implementing uh what we call<00:58:05.760> reliability<00:58:07.000> protocols<00:58:08.000> and<00:58:08.839> uh 00:58:08.910 --> 00:58:08.920 align:start position:0% call reliability protocols and uh 00:58:08.920 --> 00:58:13.270 align:start position:0% call reliability protocols and uh somehow<00:58:09.400> we<00:58:09.599> had<00:58:10.599> um<00:58:11.079> an<00:58:11.280> additional<00:58:11.640> layer<00:58:11.960> of 00:58:13.270 --> 00:58:13.280 align:start position:0% somehow we had um an additional layer of 00:58:13.280 --> 00:58:18.250 align:start position:0% somehow we had um an additional layer of redundancy<00:58:14.280> um<00:58:14.559> and<00:58:15.240> one<00:58:16.160> there<00:58:16.280> is<00:58:17.240> um 00:58:18.250 --> 00:58:18.260 align:start position:0% redundancy um and one there is um 00:58:18.260 --> 00:58:19.750 align:start position:0% redundancy um and one there is um [Music] 00:58:19.750 --> 00:58:19.760 align:start position:0% [Music] 00:58:19.760 --> 00:58:22.990 align:start position:0% [Music] um<00:58:20.760> uh<00:58:21.400> sorry<00:58:21.680> I<00:58:21.799> forgot<00:58:22.119> the<00:58:22.359> precise<00:58:22.720> name 00:58:22.990 --> 00:58:23.000 align:start position:0% um uh sorry I forgot the precise name 00:58:23.000 --> 00:58:27.270 align:start position:0% um uh sorry I forgot the precise name but<00:58:23.920> one<00:58:24.480> uh<00:58:24.680> previous<00:58:25.680> um<00:58:26.480> uh<00:58:26.640> implementation 00:58:27.270 --> 00:58:27.280 align:start position:0% but one uh previous um uh implementation 00:58:27.280 --> 00:58:32.670 align:start position:0% but one uh previous um uh implementation of<00:58:27.559> or<00:58:27.799> one<00:58:28.000> enhancement<00:58:28.680> is<00:58:29.119> to<00:58:30.440> um<00:58:31.480> um 00:58:32.670 --> 00:58:32.680 align:start position:0% of or one enhancement is to um um 00:58:32.680 --> 00:58:36.309 align:start position:0% of or one enhancement is to um um consider<00:58:33.680> that<00:58:34.119> one<00:58:34.319> message<00:58:34.680> is<00:58:35.680> has<00:58:35.839> been 00:58:36.309 --> 00:58:36.319 align:start position:0% consider that one message is has been 00:58:36.319 --> 00:58:39.510 align:start position:0% consider that one message is has been received<00:58:37.039> properly<00:58:38.039> if<00:58:38.680> it<00:58:38.920> has<00:58:39.079> been 00:58:39.510 --> 00:58:39.520 align:start position:0% received properly if it has been 00:58:39.520 --> 00:58:44.270 align:start position:0% received properly if it has been received<00:58:40.400> U<00:58:40.720> by<00:58:40.920> a<00:58:41.079> store<00:58:41.880> note<00:58:42.880> so<00:58:43.599> we<00:58:44.200> uh 00:58:44.270 --> 00:58:44.280 align:start position:0% received U by a store note so we uh 00:58:44.280 --> 00:58:46.990 align:start position:0% received U by a store note so we uh somehow<00:58:44.760> we<00:58:44.920> use<00:58:45.280> the<00:58:45.480> the<00:58:45.640> store<00:58:45.920> node<00:58:46.440> as<00:58:46.599> a 00:58:46.990 --> 00:58:47.000 align:start position:0% somehow we use the the store node as a 00:58:47.000 --> 00:58:50.470 align:start position:0% somehow we use the the store node as a leverage<00:58:47.720> to<00:58:48.359> to<00:58:48.559> reinforce<00:58:49.359> the<00:58:50.200> the 00:58:50.470 --> 00:58:50.480 align:start position:0% leverage to to reinforce the the 00:58:50.480 --> 00:58:53.029 align:start position:0% leverage to to reinforce the the transmission<00:58:51.039> of<00:58:51.359> of<00:58:51.480> a<00:58:51.680> of<00:58:51.760> a<00:58:51.920> message<00:58:52.880> but 00:58:53.029 --> 00:58:53.039 align:start position:0% transmission of of a of a message but 00:58:53.039 --> 00:58:56.910 align:start position:0% transmission of of a of a message but but<00:58:53.200> yeah<00:58:53.319> inde<00:58:53.920> this<00:58:54.200> this<00:58:54.319> is<00:58:54.760> a<00:58:55.760> um 00:58:56.910 --> 00:58:56.920 align:start position:0% but yeah inde this this is a um 00:58:56.920 --> 00:58:59.549 align:start position:0% but yeah inde this this is a um a<00:58:57.079> very<00:58:57.280> big<00:58:57.520> problem<00:58:57.839> that<00:58:58.000> that<00:58:58.119> we<00:58:58.240> need<00:58:58.559> to 00:58:59.549 --> 00:58:59.559 align:start position:0% a very big problem that that we need to 00:58:59.559 --> 00:59:00.630 align:start position:0% a very big problem that that we need to um 00:59:00.630 --> 00:59:00.640 align:start position:0% um 00:59:00.640 --> 00:59:01.720 align:start position:0% um overcome 00:59:01.720 --> 00:59:01.730 align:start position:0% overcome 00:59:01.730 --> 00:59:03.549 align:start position:0% overcome [Music] 00:59:03.549 --> 00:59:03.559 align:start position:0% [Music] 00:59:03.559 --> 00:59:08.270 align:start position:0% [Music] and<00:59:04.559> uh<00:59:04.680> and<00:59:04.880> yeah<00:59:05.200> we<00:59:05.280> are<00:59:05.480> working<00:59:05.799> on<00:59:06.119> on<00:59:06.280> it 00:59:08.270 --> 00:59:08.280 align:start position:0% and uh and yeah we are working on on it 00:59:08.280 --> 00:59:11.069 align:start position:0% and uh and yeah we are working on on it and<00:59:09.280> thank<00:59:09.480> you<00:59:09.760> thank 00:59:11.069 --> 00:59:11.079 align:start position:0% and thank you thank 00:59:11.079 --> 00:59:15.549 align:start position:0% and thank you thank you<00:59:12.079> um<00:59:12.880> any<00:59:13.079> other 00:59:15.549 --> 00:59:15.559 align:start position:0% 00:59:15.559 --> 00:59:18.670 align:start position:0% question<00:59:16.640> um<00:59:17.640> okay<00:59:17.839> in<00:59:17.960> that<00:59:18.160> case<00:59:18.440> thank<00:59:18.599> you 00:59:18.670 --> 00:59:18.680 align:start position:0% question um okay in that case thank you 00:59:18.680 --> 00:59:21.470 align:start position:0% question um okay in that case thank you so<00:59:18.880> much<00:59:19.160> for<00:59:19.640> the<00:59:19.839> time 00:59:21.470 --> 00:59:21.480 align:start position:0% so much for the time 00:59:21.480 --> 00:59:26.240 align:start position:0% so much for the time and<00:59:22.480> and<00:59:22.640> see<00:59:22.799> you<00:59:22.960> see<00:59:23.119> you<00:59:23.240> around