WEBVTT Kind: captions Language: en 00:00:00.370 --> 00:00:14.430 align:start position:0% [Music] 00:00:14.430 --> 00:00:14.440 align:start position:0% [Music] 00:00:14.440 --> 00:00:16.910 align:start position:0% [Music] see<00:00:14.599> so<00:00:14.719> we're<00:00:14.960> interested<00:00:15.360> in<00:00:15.519> low 00:00:16.910 --> 00:00:16.920 align:start position:0% see so we're interested in low 00:00:16.920 --> 00:00:20.029 align:start position:0% see so we're interested in low latency<00:00:17.920> ver<00:00:18.199> instead<00:00:18.560> of<00:00:18.720> high<00:00:19.039> throughput 00:00:20.029 --> 00:00:20.039 align:start position:0% latency ver instead of high throughput 00:00:20.039 --> 00:00:22.349 align:start position:0% latency ver instead of high throughput and<00:00:20.279> we're 00:00:22.349 --> 00:00:22.359 align:start position:0% and we're 00:00:22.359 --> 00:00:24.550 align:start position:0% and we're interested<00:00:23.359> about<00:00:23.680> small<00:00:24.039> pieces<00:00:24.359> of 00:00:24.550 --> 00:00:24.560 align:start position:0% interested about small pieces of 00:00:24.560 --> 00:00:27.269 align:start position:0% interested about small pieces of information<00:00:25.279> not<00:00:25.960> like 00:00:27.269 --> 00:00:27.279 align:start position:0% information not like 00:00:27.279 --> 00:00:30.910 align:start position:0% information not like films<00:00:28.320> uh<00:00:29.320> so 00:00:30.910 --> 00:00:30.920 align:start position:0% films uh so 00:00:30.920 --> 00:00:34.270 align:start position:0% films uh so uh<00:00:31.920> so<00:00:32.320> from<00:00:32.640> a<00:00:33.040> application<00:00:33.640> programmer's 00:00:34.270 --> 00:00:34.280 align:start position:0% uh so from a application programmer's 00:00:34.280 --> 00:00:38.190 align:start position:0% uh so from a application programmer's point<00:00:34.559> of<00:00:35.040> view<00:00:36.079> uh<00:00:37.079> what<00:00:37.360> what<00:00:37.520> it<00:00:37.680> does<00:00:37.960> for 00:00:38.190 --> 00:00:38.200 align:start position:0% point of view uh what what it does for 00:00:38.200 --> 00:00:40.950 align:start position:0% point of view uh what what it does for you<00:00:38.480> is<00:00:38.719> you<00:00:39.040> ask<00:00:39.879> you<00:00:40.000> know<00:00:40.200> the<00:00:40.399> hash<00:00:40.640> of<00:00:40.760> some 00:00:40.950 --> 00:00:40.960 align:start position:0% you is you ask you know the hash of some 00:00:40.960 --> 00:00:43.830 align:start position:0% you is you ask you know the hash of some piece<00:00:41.160> of<00:00:41.440> information<00:00:42.440> you<00:00:42.680> ask<00:00:43.000> for<00:00:43.239> it<00:00:43.680> and 00:00:43.830 --> 00:00:43.840 align:start position:0% piece of information you ask for it and 00:00:43.840 --> 00:00:47.110 align:start position:0% piece of information you ask for it and you<00:00:44.000> get<00:00:44.160> it<00:00:44.360> as<00:00:44.600> fast<00:00:44.879> as<00:00:45.440> possible<00:00:46.440> uh<00:00:46.879> like 00:00:47.110 --> 00:00:47.120 align:start position:0% you get it as fast as possible uh like 00:00:47.120 --> 00:00:49.830 align:start position:0% you get it as fast as possible uh like preferably<00:00:47.760> from<00:00:48.000> the<00:00:48.160> ram<00:00:48.399> of<00:00:48.559> your<00:00:48.719> own 00:00:49.830 --> 00:00:49.840 align:start position:0% preferably from the ram of your own 00:00:49.840 --> 00:00:53.869 align:start position:0% preferably from the ram of your own computer<00:00:50.840> slightly<00:00:51.399> worse<00:00:52.079> from<00:00:52.600> the<00:00:53.600> hard 00:00:53.869 --> 00:00:53.879 align:start position:0% computer slightly worse from the hard 00:00:53.879 --> 00:00:56.549 align:start position:0% computer slightly worse from the hard drive<00:00:54.160> or<00:00:54.320> the<00:00:54.440> SSD<00:00:54.879> of<00:00:55.039> your<00:00:55.280> computer<00:00:56.239> and<00:00:56.399> in 00:00:56.549 --> 00:00:56.559 align:start position:0% drive or the SSD of your computer and in 00:00:56.559 --> 00:00:58.470 align:start position:0% drive or the SSD of your computer and in the<00:00:56.719> absolute<00:00:57.160> worst<00:00:57.480> case<00:00:57.719> from<00:00:57.879> the<00:00:58.039> network 00:00:58.470 --> 00:00:58.480 align:start position:0% the absolute worst case from the network 00:00:58.480 --> 00:01:01.229 align:start position:0% the absolute worst case from the network but<00:00:58.640> quickly 00:01:01.229 --> 00:01:01.239 align:start position:0% but quickly 00:01:01.239 --> 00:01:04.550 align:start position:0% but quickly so<00:01:01.879> the<00:01:02.079> design<00:01:02.879> goals 00:01:04.550 --> 00:01:04.560 align:start position:0% so the design goals 00:01:04.560 --> 00:01:08.149 align:start position:0% so the design goals Integrity<00:01:05.560> so<00:01:06.159> you<00:01:06.400> don't 00:01:08.149 --> 00:01:08.159 align:start position:0% Integrity so you don't 00:01:08.159 --> 00:01:12.109 align:start position:0% Integrity so you don't so<00:01:09.159> the<00:01:09.360> information<00:01:10.080> stays<00:01:10.479> immutable<00:01:11.360> and 00:01:12.109 --> 00:01:12.119 align:start position:0% so the information stays immutable and 00:01:12.119 --> 00:01:16.070 align:start position:0% so the information stays immutable and uh<00:01:13.119> and<00:01:13.280> you<00:01:13.400> can<00:01:13.600> be<00:01:13.759> sure<00:01:14.280> that<00:01:15.280> that's<00:01:15.640> what 00:01:16.070 --> 00:01:16.080 align:start position:0% uh and you can be sure that that's what 00:01:16.080 --> 00:01:19.590 align:start position:0% uh and you can be sure that that's what what<00:01:16.200> you<00:01:16.600> you<00:01:16.759> get<00:01:17.000> what<00:01:17.280> you<00:01:17.439> asked<00:01:18.080> for<00:01:19.080> uh<00:01:19.400> a 00:01:19.590 --> 00:01:19.600 align:start position:0% what you you get what you asked for uh a 00:01:19.600 --> 00:01:22.550 align:start position:0% what you you get what you asked for uh a measure<00:01:19.920> of<00:01:20.159> permanence<00:01:20.920> so<00:01:21.840> once<00:01:22.159> something 00:01:22.550 --> 00:01:22.560 align:start position:0% measure of permanence so once something 00:01:22.560 --> 00:01:27.030 align:start position:0% measure of permanence so once something gets<00:01:22.920> there<00:01:23.560> it's<00:01:24.560> it's<00:01:24.799> impossible<00:01:25.280> to 00:01:27.030 --> 00:01:27.040 align:start position:0% gets there it's it's impossible to 00:01:27.040 --> 00:01:30.270 align:start position:0% gets there it's it's impossible to delete<00:01:28.040> it's<00:01:28.360> resilient<00:01:29.119> against<00:01:29.640> both<00:01:29.960> both 00:01:30.270 --> 00:01:30.280 align:start position:0% delete it's resilient against both both 00:01:30.280 --> 00:01:33.030 align:start position:0% delete it's resilient against both both random<00:01:30.680> failures<00:01:31.479> and<00:01:31.960> malicious 00:01:33.030 --> 00:01:33.040 align:start position:0% random failures and malicious 00:01:33.040 --> 00:01:36.590 align:start position:0% random failures and malicious adversaries<00:01:34.040> where<00:01:34.880> of<00:01:35.079> course<00:01:35.759> if<00:01:35.920> it's 00:01:36.590 --> 00:01:36.600 align:start position:0% adversaries where of course if it's 00:01:36.600 --> 00:01:38.670 align:start position:0% adversaries where of course if it's resilient<00:01:37.240> against<00:01:37.520> malicious<00:01:38.079> adversaries 00:01:38.670 --> 00:01:38.680 align:start position:0% resilient against malicious adversaries 00:01:38.680 --> 00:01:40.389 align:start position:0% resilient against malicious adversaries it's<00:01:38.880> automatically<00:01:39.600> resilient<00:01:40.119> against 00:01:40.389 --> 00:01:40.399 align:start position:0% it's automatically resilient against 00:01:40.399 --> 00:01:42.789 align:start position:0% it's automatically resilient against random<00:01:40.759> failures<00:01:41.360> but<00:01:41.560> we<00:01:41.759> sort<00:01:42.000> of<00:01:42.200> keep<00:01:42.520> both 00:01:42.789 --> 00:01:42.799 align:start position:0% random failures but we sort of keep both 00:01:42.799 --> 00:01:43.670 align:start position:0% random failures but we sort of keep both in 00:01:43.670 --> 00:01:43.680 align:start position:0% in 00:01:43.680 --> 00:01:47.590 align:start position:0% in mind<00:01:44.680> uh<00:01:45.560> speed<00:01:46.119> is<00:01:46.320> very<00:01:46.520> important<00:01:47.200> and<00:01:47.399> by 00:01:47.590 --> 00:01:47.600 align:start position:0% mind uh speed is very important and by 00:01:47.600 --> 00:01:50.510 align:start position:0% mind uh speed is very important and by speed<00:01:48.119> I<00:01:48.399> I<00:01:48.520> mean<00:01:49.399> low 00:01:50.510 --> 00:01:50.520 align:start position:0% speed I I mean low 00:01:50.520 --> 00:01:54.630 align:start position:0% speed I I mean low latency<00:01:51.520> and<00:01:52.320> a<00:01:53.000> utilization<00:01:54.000> a<00:01:54.200> optimal 00:01:54.630 --> 00:01:54.640 align:start position:0% latency and a utilization a optimal 00:01:54.640 --> 00:01:57.469 align:start position:0% latency and a utilization a optimal utilization<00:01:55.320> of<00:01:55.840> available<00:01:56.399> resources<00:01:57.159> so 00:01:57.469 --> 00:01:57.479 align:start position:0% utilization of available resources so 00:01:57.479 --> 00:02:00.270 align:start position:0% utilization of available resources so network<00:01:58.079> storage<00:01:58.880> and<00:01:59.079> to<00:01:59.240> some<00:01:59.399> lesser 00:02:00.270 --> 00:02:00.280 align:start position:0% network storage and to some lesser 00:02:00.280 --> 00:02:02.270 align:start position:0% network storage and to some lesser processing<00:02:01.000> power<00:02:01.520> but<00:02:01.719> mostly<00:02:02.039> we're 00:02:02.270 --> 00:02:02.280 align:start position:0% processing power but mostly we're 00:02:02.280 --> 00:02:04.469 align:start position:0% processing power but mostly we're interested<00:02:02.799> in<00:02:03.240> network<00:02:03.759> resources<00:02:04.320> and 00:02:04.469 --> 00:02:04.479 align:start position:0% interested in network resources and 00:02:04.479 --> 00:02:05.789 align:start position:0% interested in network resources and storage 00:02:05.789 --> 00:02:05.799 align:start position:0% storage 00:02:05.799 --> 00:02:09.949 align:start position:0% storage resources 00:02:09.949 --> 00:02:09.959 align:start position:0% 00:02:09.959 --> 00:02:13.070 align:start position:0% uh<00:02:10.959> how<00:02:11.160> do<00:02:11.319> we<00:02:11.480> ensure 00:02:13.070 --> 00:02:13.080 align:start position:0% uh how do we ensure 00:02:13.080 --> 00:02:15.790 align:start position:0% uh how do we ensure Integrity<00:02:14.080> each<00:02:14.440> time<00:02:14.720> you<00:02:14.959> receive<00:02:15.400> a<00:02:15.560> piece 00:02:15.790 --> 00:02:15.800 align:start position:0% Integrity each time you receive a piece 00:02:15.800 --> 00:02:18.470 align:start position:0% Integrity each time you receive a piece of<00:02:16.080> data<00:02:16.640> if<00:02:16.800> it<00:02:17.160> comes<00:02:17.599> from<00:02:17.959> any<00:02:18.200> other 00:02:18.470 --> 00:02:18.480 align:start position:0% of data if it comes from any other 00:02:18.480 --> 00:02:21.070 align:start position:0% of data if it comes from any other source<00:02:19.000> but<00:02:19.200> your<00:02:19.519> RAM<00:02:20.040> you<00:02:20.239> check<00:02:20.680> you<00:02:20.840> check 00:02:21.070 --> 00:02:21.080 align:start position:0% source but your RAM you check you check 00:02:21.080 --> 00:02:23.750 align:start position:0% source but your RAM you check you check the<00:02:21.239> hash<00:02:22.160> that's<00:02:22.360> just<00:02:22.519> the<00:02:22.680> rule<00:02:23.560> and 00:02:23.750 --> 00:02:23.760 align:start position:0% the hash that's just the rule and 00:02:23.760 --> 00:02:26.309 align:start position:0% the hash that's just the rule and because<00:02:24.120> of<00:02:24.360> that<00:02:24.599> in<00:02:24.720> order<00:02:25.200> for<00:02:25.480> that<00:02:25.640> to<00:02:25.800> be 00:02:26.309 --> 00:02:26.319 align:start position:0% because of that in order for that to be 00:02:26.319 --> 00:02:29.350 align:start position:0% because of that in order for that to be feasible<00:02:27.319> there<00:02:28.200> we<00:02:28.319> need<00:02:28.519> to<00:02:28.720> make<00:02:28.879> sure<00:02:29.200> that 00:02:29.350 --> 00:02:29.360 align:start position:0% feasible there we need to make sure that 00:02:29.360 --> 00:02:32.949 align:start position:0% feasible there we need to make sure that there<00:02:29.440> are<00:02:29.560> no<00:02:30.000> long<00:02:30.519> unchecked<00:02:31.519> uh<00:02:32.040> downloads 00:02:32.949 --> 00:02:32.959 align:start position:0% there are no long unchecked uh downloads 00:02:32.959 --> 00:02:36.390 align:start position:0% there are no long unchecked uh downloads so<00:02:33.280> if<00:02:33.560> something<00:02:34.200> H<00:02:34.560> something<00:02:34.920> is<00:02:35.200> long<00:02:36.200> then 00:02:36.390 --> 00:02:36.400 align:start position:0% so if something H something is long then 00:02:36.400 --> 00:02:39.190 align:start position:0% so if something H something is long then it<00:02:36.519> needs<00:02:36.760> to<00:02:36.920> be<00:02:37.120> chunked<00:02:38.080> and<00:02:38.280> the<00:02:38.480> max<00:02:39.000> we<00:02:39.120> we 00:02:39.190 --> 00:02:39.200 align:start position:0% it needs to be chunked and the max we we 00:02:39.200 --> 00:02:41.430 align:start position:0% it needs to be chunked and the max we we should<00:02:39.480> maximize<00:02:40.000> the<00:02:40.120> chunk<00:02:40.519> size<00:02:41.200> in 00:02:41.430 --> 00:02:41.440 align:start position:0% should maximize the chunk size in 00:02:41.440 --> 00:02:44.509 align:start position:0% should maximize the chunk size in something<00:02:41.840> like<00:02:42.000> 4<00:02:42.280> kiloby<00:02:42.959> not<00:02:43.319> more<00:02:44.319> and 00:02:44.509 --> 00:02:44.519 align:start position:0% something like 4 kiloby not more and 00:02:44.519 --> 00:02:46.830 align:start position:0% something like 4 kiloby not more and there<00:02:44.599> are<00:02:44.840> two<00:02:45.080> kinds<00:02:45.319> of<00:02:45.480> chunks<00:02:46.400> there's<00:02:46.680> a 00:02:46.830 --> 00:02:46.840 align:start position:0% there are two kinds of chunks there's a 00:02:46.840 --> 00:02:48.470 align:start position:0% there are two kinds of chunks there's a leaf<00:02:47.239> data 00:02:48.470 --> 00:02:48.480 align:start position:0% leaf data 00:02:48.480 --> 00:02:51.390 align:start position:0% leaf data fragment<00:02:49.480> and<00:02:49.720> there's<00:02:50.040> a<00:02:50.200> Merkel<00:02:50.680> tree<00:02:50.959> node 00:02:51.390 --> 00:02:51.400 align:start position:0% fragment and there's a Merkel tree node 00:02:51.400 --> 00:02:54.790 align:start position:0% fragment and there's a Merkel tree node which<00:02:51.640> has<00:02:51.920> hashes<00:02:52.560> of<00:02:52.840> other 00:02:54.790 --> 00:02:54.800 align:start position:0% which has hashes of other 00:02:54.800 --> 00:02:59.509 align:start position:0% which has hashes of other chunks<00:02:55.800> and<00:02:56.400> this<00:02:56.599> of<00:02:56.840> course<00:02:57.440> means<00:02:58.239> that<00:02:58.800> we 00:02:59.509 --> 00:02:59.519 align:start position:0% chunks and this of course means that we 00:02:59.519 --> 00:03:03.390 align:start position:0% chunks and this of course means that we the<00:03:00.200> the<00:03:00.440> the<00:03:00.640> hash<00:03:01.200> is<00:03:01.480> really<00:03:01.720> a<00:03:01.879> merco<00:03:02.400> hash 00:03:03.390 --> 00:03:03.400 align:start position:0% the the the hash is really a merco hash 00:03:03.400 --> 00:03:06.910 align:start position:0% the the the hash is really a merco hash and<00:03:03.760> I<00:03:03.920> really<00:03:04.319> recommend<00:03:05.480> that<00:03:06.480> and<00:03:06.840> we 00:03:06.910 --> 00:03:06.920 align:start position:0% and I really recommend that and we 00:03:06.920 --> 00:03:09.869 align:start position:0% and I really recommend that and we should<00:03:07.120> probably<00:03:07.480> discuss<00:03:07.920> it<00:03:08.879> that 00:03:09.869 --> 00:03:09.879 align:start position:0% should probably discuss it that 00:03:09.879 --> 00:03:13.309 align:start position:0% should probably discuss it that everything<00:03:10.760> in<00:03:11.159> in<00:03:11.680> when<00:03:11.840> we<00:03:12.000> say<00:03:12.319> hash<00:03:12.840> inside 00:03:13.309 --> 00:03:13.319 align:start position:0% everything in in when we say hash inside 00:03:13.319 --> 00:03:15.470 align:start position:0% everything in in when we say hash inside ether<00:03:14.040> of<00:03:14.200> of<00:03:14.400> stuff<00:03:14.680> that<00:03:14.840> needs<00:03:15.080> to<00:03:15.239> be 00:03:15.470 --> 00:03:15.480 align:start position:0% ether of of stuff that needs to be 00:03:15.480 --> 00:03:18.350 align:start position:0% ether of of stuff that needs to be stored<00:03:16.480> then<00:03:16.799> we<00:03:17.000> always<00:03:17.480> have<00:03:17.840> we<00:03:18.000> always 00:03:18.350 --> 00:03:18.360 align:start position:0% stored then we always have we always 00:03:18.360 --> 00:03:21.070 align:start position:0% stored then we always have we always calculate<00:03:18.920> this<00:03:19.080> Merkel<00:03:19.560> hash<00:03:20.360> because<00:03:20.799> even 00:03:21.070 --> 00:03:21.080 align:start position:0% calculate this Merkel hash because even 00:03:21.080 --> 00:03:23.789 align:start position:0% calculate this Merkel hash because even if<00:03:21.319> you<00:03:21.680> if<00:03:21.920> even<00:03:22.159> if<00:03:22.280> you're<00:03:22.519> not<00:03:22.799> sto<00:03:23.400> if<00:03:23.560> even 00:03:23.789 --> 00:03:23.799 align:start position:0% if you if even if you're not sto if even 00:03:23.799 --> 00:03:26.030 align:start position:0% if you if even if you're not sto if even if<00:03:24.000> the<00:03:24.159> purpose<00:03:24.560> is<00:03:24.720> not<00:03:25.000> immediate<00:03:25.519> storage 00:03:26.030 --> 00:03:26.040 align:start position:0% if the purpose is not immediate storage 00:03:26.040 --> 00:03:30.190 align:start position:0% if the purpose is not immediate storage in<00:03:26.239> this<00:03:27.040> archive<00:03:28.040> uh<00:03:28.400> still<00:03:29.400> calc<00:03:29.879> ating<00:03:30.080> a 00:03:30.190 --> 00:03:30.200 align:start position:0% in this archive uh still calc ating a 00:03:30.200 --> 00:03:33.190 align:start position:0% in this archive uh still calc ating a miracle<00:03:30.640> hash<00:03:31.040> in<00:03:31.280> a<00:03:31.920> uh<00:03:32.200> multicore<00:03:32.840> machine 00:03:33.190 --> 00:03:33.200 align:start position:0% miracle hash in a uh multicore machine 00:03:33.200 --> 00:03:36.470 align:start position:0% miracle hash in a uh multicore machine is<00:03:33.400> actually<00:03:33.799> faster<00:03:34.640> and<00:03:34.799> it's<00:03:35.080> nice<00:03:35.519> if<00:03:35.799> the 00:03:36.470 --> 00:03:36.480 align:start position:0% is actually faster and it's nice if the 00:03:36.480 --> 00:03:39.869 align:start position:0% is actually faster and it's nice if the if<00:03:36.640> the<00:03:36.840> hash<00:03:37.319> is<00:03:37.879> always<00:03:38.200> refers<00:03:38.599> to<00:03:38.760> the<00:03:38.920> same 00:03:39.869 --> 00:03:39.879 align:start position:0% if the hash is always refers to the same 00:03:39.879 --> 00:03:42.710 align:start position:0% if the hash is always refers to the same thing<00:03:40.879> and<00:03:41.400> uh<00:03:41.680> but<00:03:41.879> the<00:03:42.040> underlying 00:03:42.710 --> 00:03:42.720 align:start position:0% thing and uh but the underlying 00:03:42.720 --> 00:03:44.830 align:start position:0% thing and uh but the underlying assumption<00:03:43.360> is<00:03:43.519> that<00:03:43.720> the<00:03:43.879> vast<00:03:44.239> majority<00:03:44.640> of 00:03:44.830 --> 00:03:44.840 align:start position:0% assumption is that the vast majority of 00:03:44.840 --> 00:03:47.589 align:start position:0% assumption is that the vast majority of data<00:03:45.239> that<00:03:45.480> are<00:03:45.920> is<00:03:46.080> going<00:03:46.280> to<00:03:46.400> be<00:03:46.560> stored<00:03:47.040> here 00:03:47.589 --> 00:03:47.599 align:start position:0% data that are is going to be stored here 00:03:47.599 --> 00:03:49.990 align:start position:0% data that are is going to be stored here it<00:03:47.760> fits<00:03:48.080> into<00:03:48.360> a<00:03:48.480> single<00:03:48.840> chunk<00:03:49.519> so<00:03:49.720> we're 00:03:49.990 --> 00:03:50.000 align:start position:0% it fits into a single chunk so we're 00:03:50.000 --> 00:03:53.830 align:start position:0% it fits into a single chunk so we're thinking<00:03:50.480> about<00:03:51.159> things<00:03:51.680> like<00:03:52.280> uh<00:03:53.280> uh<00:03:53.480> parts 00:03:53.830 --> 00:03:53.840 align:start position:0% thinking about things like uh uh parts 00:03:53.840 --> 00:03:58.869 align:start position:0% thinking about things like uh uh parts of<00:03:54.000> the<00:03:54.680> State<00:03:55.720> uh<00:03:57.000> transactions<00:03:58.000> contracts 00:03:58.869 --> 00:03:58.879 align:start position:0% of the State uh transactions contracts 00:03:58.879 --> 00:04:00.710 align:start position:0% of the State uh transactions contracts things<00:03:59.159> like<00:03:59.360> that<00:03:59.560> which<00:03:59.799> are<00:04:00.079> typically<00:04:00.480> not 00:04:00.710 --> 00:04:00.720 align:start position:0% things like that which are typically not 00:04:00.720 --> 00:04:02.589 align:start position:0% things like that which are typically not very 00:04:02.589 --> 00:04:02.599 align:start position:0% very 00:04:02.599 --> 00:04:05.589 align:start position:0% very long<00:04:03.599> uh<00:04:04.000> so<00:04:04.280> how<00:04:04.400> do<00:04:04.519> we<00:04:04.680> go<00:04:04.879> about<00:04:05.239> being 00:04:05.589 --> 00:04:05.599 align:start position:0% long uh so how do we go about being 00:04:05.599 --> 00:04:07.110 align:start position:0% long uh so how do we go about being resilient<00:04:06.159> and 00:04:07.110 --> 00:04:07.120 align:start position:0% resilient and 00:04:07.120 --> 00:04:11.030 align:start position:0% resilient and redundant<00:04:08.120> so<00:04:08.519> this<00:04:08.640> is<00:04:08.879> where<00:04:09.360> DHD<00:04:10.360> uh<00:04:10.560> comes 00:04:11.030 --> 00:04:11.040 align:start position:0% redundant so this is where DHD uh comes 00:04:11.040 --> 00:04:15.190 align:start position:0% redundant so this is where DHD uh comes into<00:04:12.040> into<00:04:12.560> play<00:04:13.560> so<00:04:14.239> so<00:04:14.519> this<00:04:14.640> is<00:04:14.760> going<00:04:14.959> to<00:04:15.079> be 00:04:15.190 --> 00:04:15.200 align:start position:0% into into play so so this is going to be 00:04:15.200 --> 00:04:17.069 align:start position:0% into into play so so this is going to be a<00:04:15.319> little<00:04:15.480> bit<00:04:15.599> of<00:04:15.760> an<00:04:15.920> introduction<00:04:16.560> to<00:04:16.919> what 00:04:17.069 --> 00:04:17.079 align:start position:0% a little bit of an introduction to what 00:04:17.079 --> 00:04:20.469 align:start position:0% a little bit of an introduction to what ADHD<00:04:17.799> is<00:04:17.959> and<00:04:18.160> how<00:04:18.359> they<00:04:18.519> work<00:04:19.479> pro<00:04:19.959> maybe<00:04:20.239> for 00:04:20.469 --> 00:04:20.479 align:start position:0% ADHD is and how they work pro maybe for 00:04:20.479 --> 00:04:23.749 align:start position:0% ADHD is and how they work pro maybe for some<00:04:20.639> of<00:04:20.799> you<00:04:20.959> it<00:04:21.079> will<00:04:21.280> be<00:04:21.519> a<00:04:21.639> little<00:04:22.320> boring 00:04:23.749 --> 00:04:23.759 align:start position:0% some of you it will be a little boring 00:04:23.759 --> 00:04:25.909 align:start position:0% some of you it will be a little boring so<00:04:24.759> node 00:04:25.909 --> 00:04:25.919 align:start position:0% so node 00:04:25.919 --> 00:04:28.070 align:start position:0% so node addresses<00:04:26.919> so<00:04:27.160> the<00:04:27.320> addresses<00:04:27.759> of<00:04:27.919> the 00:04:28.070 --> 00:04:28.080 align:start position:0% addresses so the addresses of the 00:04:28.080 --> 00:04:30.550 align:start position:0% addresses so the addresses of the machines<00:04:28.600> that<00:04:28.759> form<00:04:29.080> the<00:04:29.240> network 00:04:30.550 --> 00:04:30.560 align:start position:0% machines that form the network 00:04:30.560 --> 00:04:34.350 align:start position:0% machines that form the network and<00:04:31.080> the<00:04:32.000> keys<00:04:32.479> of<00:04:32.680> the<00:04:32.880> pieces<00:04:33.199> of<00:04:33.440> data<00:04:33.800> the 00:04:34.350 --> 00:04:34.360 align:start position:0% and the keys of the pieces of data the 00:04:34.360 --> 00:04:37.310 align:start position:0% and the keys of the pieces of data the hashes<00:04:35.360> they<00:04:35.639> come<00:04:36.039> from<00:04:36.360> the<00:04:36.560> same<00:04:37.039> they<00:04:37.160> are 00:04:37.310 --> 00:04:37.320 align:start position:0% hashes they come from the same they are 00:04:37.320 --> 00:04:39.629 align:start position:0% hashes they come from the same they are the<00:04:37.440> same<00:04:37.759> type<00:04:37.960> of<00:04:38.199> object<00:04:39.000> so<00:04:39.199> in<00:04:39.400> this 00:04:39.629 --> 00:04:39.639 align:start position:0% the same type of object so in this 00:04:39.639 --> 00:04:41.590 align:start position:0% the same type of object so in this particular<00:04:40.240> case<00:04:40.520> it's<00:04:40.800> probably<00:04:41.199> going<00:04:41.440> to 00:04:41.590 --> 00:04:41.600 align:start position:0% particular case it's probably going to 00:04:41.600 --> 00:04:43.749 align:start position:0% particular case it's probably going to be<00:04:42.240> 256bit 00:04:43.749 --> 00:04:43.759 align:start position:0% be 256bit 00:04:43.759 --> 00:04:46.230 align:start position:0% be 256bit hashes<00:04:44.759> uh<00:04:44.919> because<00:04:45.240> the<00:04:45.400> addresses<00:04:45.960> of<00:04:46.120> the 00:04:46.230 --> 00:04:46.240 align:start position:0% hashes uh because the addresses of the 00:04:46.240 --> 00:04:49.110 align:start position:0% hashes uh because the addresses of the nodes<00:04:46.680> are<00:04:46.919> just<00:04:47.120> the<00:04:47.320> hashes<00:04:48.039> of<00:04:48.320> their<00:04:48.919> uh 00:04:49.110 --> 00:04:49.120 align:start position:0% nodes are just the hashes of their uh 00:04:49.120 --> 00:04:50.629 align:start position:0% nodes are just the hashes of their uh public 00:04:50.629 --> 00:04:50.639 align:start position:0% public 00:04:50.639 --> 00:04:53.550 align:start position:0% public keys<00:04:51.639> and<00:04:51.840> there's<00:04:52.120> a<00:04:52.479> particular<00:04:53.080> distance 00:04:53.550 --> 00:04:53.560 align:start position:0% keys and there's a particular distance 00:04:53.560 --> 00:04:56.990 align:start position:0% keys and there's a particular distance measure<00:04:54.080> defined<00:04:54.880> on<00:04:55.160> this<00:04:55.560> space<00:04:56.560> and<00:04:56.759> by 00:04:56.990 --> 00:04:57.000 align:start position:0% measure defined on this space and by 00:04:57.000 --> 00:04:58.990 align:start position:0% measure defined on this space and by distance<00:04:57.440> measure<00:04:57.880> I<00:04:57.960> mean<00:04:58.199> the<00:04:58.400> mathematical 00:04:58.990 --> 00:04:59.000 align:start position:0% distance measure I mean the mathematical 00:04:59.000 --> 00:05:01.590 align:start position:0% distance measure I mean the mathematical definition<00:04:59.400> of<00:04:59.759> distance<00:05:00.120> measure<00:05:00.919> so<00:05:01.320> it's 00:05:01.590 --> 00:05:01.600 align:start position:0% definition of distance measure so it's 00:05:01.600 --> 00:05:03.990 align:start position:0% definition of distance measure so it's symmetric<00:05:02.600> the<00:05:02.759> distance<00:05:03.120> from<00:05:03.320> A<00:05:03.479> to<00:05:03.639> B<00:05:03.840> is 00:05:03.990 --> 00:05:04.000 align:start position:0% symmetric the distance from A to B is 00:05:04.000 --> 00:05:07.029 align:start position:0% symmetric the distance from A to B is the<00:05:04.120> same<00:05:04.360> as<00:05:04.520> the<00:05:04.639> distance<00:05:05.000> from<00:05:05.160> B<00:05:05.360> to<00:05:05.560> a<00:05:06.479> it 00:05:07.029 --> 00:05:07.039 align:start position:0% the same as the distance from B to a it 00:05:07.039 --> 00:05:09.790 align:start position:0% the same as the distance from B to a it uh<00:05:07.680> satisfies<00:05:08.280> the<00:05:08.440> triangle 00:05:09.790 --> 00:05:09.800 align:start position:0% uh satisfies the triangle 00:05:09.800 --> 00:05:13.590 align:start position:0% uh satisfies the triangle inequality<00:05:10.800> and<00:05:11.600> uh<00:05:12.600> the<00:05:12.880> distance<00:05:13.360> from 00:05:13.590 --> 00:05:13.600 align:start position:0% inequality and uh the distance from 00:05:13.600 --> 00:05:17.550 align:start position:0% inequality and uh the distance from something<00:05:14.039> from<00:05:14.320> itself<00:05:15.120> is 00:05:17.550 --> 00:05:17.560 align:start position:0% something from itself is 00:05:17.560 --> 00:05:21.230 align:start position:0% something from itself is zero<00:05:18.560> uh<00:05:18.680> so<00:05:19.000> what<00:05:19.120> you<00:05:19.400> get<00:05:19.919> is<00:05:20.319> that<00:05:20.759> suppose 00:05:21.230 --> 00:05:21.240 align:start position:0% zero uh so what you get is that suppose 00:05:21.240 --> 00:05:22.870 align:start position:0% zero uh so what you get is that suppose so<00:05:21.520> this<00:05:21.680> is<00:05:21.880> this<00:05:21.960> is<00:05:22.080> an 00:05:22.870 --> 00:05:22.880 align:start position:0% so this is this is an 00:05:22.880 --> 00:05:25.230 align:start position:0% so this is this is an illustration<00:05:23.880> where<00:05:24.160> the<00:05:24.440> distance<00:05:24.880> is<00:05:25.080> like 00:05:25.230 --> 00:05:25.240 align:start position:0% illustration where the distance is like 00:05:25.240 --> 00:05:27.950 align:start position:0% illustration where the distance is like the<00:05:25.400> alian<00:05:26.039> distance<00:05:26.400> on<00:05:26.560> the<00:05:26.759> plane<00:05:27.639> the 00:05:27.950 --> 00:05:27.960 align:start position:0% the alian distance on the plane the 00:05:27.960 --> 00:05:30.469 align:start position:0% the alian distance on the plane the black<00:05:28.360> dots<00:05:28.880> are<00:05:29.280> the 00:05:30.469 --> 00:05:30.479 align:start position:0% black dots are the 00:05:30.479 --> 00:05:33.029 align:start position:0% black dots are the machines<00:05:31.479> uh<00:05:31.680> they<00:05:31.840> are<00:05:32.319> randomly<00:05:32.840> and 00:05:33.029 --> 00:05:33.039 align:start position:0% machines uh they are randomly and 00:05:33.039 --> 00:05:35.350 align:start position:0% machines uh they are randomly and uniformly<00:05:33.759> distributed<00:05:34.479> because<00:05:34.880> the<00:05:35.160> the 00:05:35.350 --> 00:05:35.360 align:start position:0% uniformly distributed because the the 00:05:35.360 --> 00:05:38.270 align:start position:0% uniformly distributed because the the the<00:05:35.520> is<00:05:35.919> the<00:05:36.160> the<00:05:36.800> address<00:05:37.319> is<00:05:37.440> a<00:05:37.680> result<00:05:38.000> of<00:05:38.120> a 00:05:38.270 --> 00:05:38.280 align:start position:0% the is the the address is a result of a 00:05:38.280 --> 00:05:42.670 align:start position:0% the is the the address is a result of a hashing<00:05:39.280> and<00:05:39.440> the<00:05:39.639> big<00:05:40.080> black<00:05:40.600> circle<00:05:41.600> is<00:05:42.000> the 00:05:42.670 --> 00:05:42.680 align:start position:0% hashing and the big black circle is the 00:05:42.680 --> 00:05:44.550 align:start position:0% hashing and the big black circle is the uh<00:05:43.039> is<00:05:43.199> the<00:05:43.400> entire 00:05:44.550 --> 00:05:44.560 align:start position:0% uh is the entire 00:05:44.560 --> 00:05:47.070 align:start position:0% uh is the entire space<00:05:45.560> uh<00:05:45.759> so<00:05:46.039> that's<00:05:46.240> where<00:05:46.440> the<00:05:46.639> data<00:05:46.880> can 00:05:47.070 --> 00:05:47.080 align:start position:0% space uh so that's where the data can 00:05:47.080 --> 00:05:50.150 align:start position:0% space uh so that's where the data can live<00:05:47.319> so<00:05:47.440> a<00:05:47.600> piece<00:05:47.759> of<00:05:48.000> data<00:05:48.280> can<00:05:48.479> be<00:05:49.120> anywhere 00:05:50.150 --> 00:05:50.160 align:start position:0% live so a piece of data can be anywhere 00:05:50.160 --> 00:05:54.749 align:start position:0% live so a piece of data can be anywhere and<00:05:51.160> you<00:05:51.280> know<00:05:51.520> nodes<00:05:52.039> are<00:05:52.520> keeping<00:05:53.520> the<00:05:54.479> each 00:05:54.749 --> 00:05:54.759 align:start position:0% and you know nodes are keeping the each 00:05:54.759 --> 00:05:56.749 align:start position:0% and you know nodes are keeping the each node<00:05:55.280> is<00:05:55.520> keeping<00:05:56.000> the 00:05:56.749 --> 00:05:56.759 align:start position:0% node is keeping the 00:05:56.759 --> 00:06:00.150 align:start position:0% node is keeping the information<00:05:57.759> that<00:05:58.039> is<00:05:58.319> closest<00:05:58.840> to<00:05:59.120> them 00:06:00.150 --> 00:06:00.160 align:start position:0% information that is closest to them 00:06:00.160 --> 00:06:02.670 align:start position:0% information that is closest to them now<00:06:00.400> of<00:06:00.520> course<00:06:00.800> as<00:06:00.919> long<00:06:01.120> as<00:06:01.319> they<00:06:01.479> can<00:06:01.759> afford 00:06:02.670 --> 00:06:02.680 align:start position:0% now of course as long as they can afford 00:06:02.680 --> 00:06:06.110 align:start position:0% now of course as long as they can afford to<00:06:03.360> store<00:06:04.360> something<00:06:04.880> they<00:06:05.039> just<00:06:05.240> store<00:06:05.560> it 00:06:06.110 --> 00:06:06.120 align:start position:0% to store something they just store it 00:06:06.120 --> 00:06:08.189 align:start position:0% to store something they just store it but<00:06:06.319> when<00:06:06.560> their<00:06:06.800> storage<00:06:07.240> resources<00:06:07.960> get 00:06:08.189 --> 00:06:08.199 align:start position:0% but when their storage resources get 00:06:08.199 --> 00:06:11.510 align:start position:0% but when their storage resources get full<00:06:09.039> first<00:06:09.400> their<00:06:09.639> RAM<00:06:10.000> and<00:06:10.199> then<00:06:10.440> their<00:06:11.360> uh 00:06:11.510 --> 00:06:11.520 align:start position:0% full first their RAM and then their uh 00:06:11.520 --> 00:06:15.189 align:start position:0% full first their RAM and then their uh background<00:06:12.080> storage<00:06:13.080> then<00:06:13.840> they<00:06:14.160> sort<00:06:14.440> of 00:06:15.189 --> 00:06:15.199 align:start position:0% background storage then they sort of 00:06:15.199 --> 00:06:18.749 align:start position:0% background storage then they sort of delete<00:06:16.160> what<00:06:16.319> is<00:06:16.520> furthest<00:06:17.120> away<00:06:17.440> from<00:06:17.759> them 00:06:18.749 --> 00:06:18.759 align:start position:0% delete what is furthest away from them 00:06:18.759 --> 00:06:21.710 align:start position:0% delete what is furthest away from them so<00:06:19.080> basically<00:06:19.919> there's<00:06:20.160> a<00:06:20.440> radius<00:06:21.160> in<00:06:21.400> which 00:06:21.710 --> 00:06:21.720 align:start position:0% so basically there's a radius in which 00:06:21.720 --> 00:06:25.189 align:start position:0% so basically there's a radius in which they<00:06:22.319> are<00:06:22.800> responsible<00:06:23.520> for<00:06:23.759> the<00:06:23.960> data<00:06:24.759> and<00:06:25.039> as 00:06:25.189 --> 00:06:25.199 align:start position:0% they are responsible for the data and as 00:06:25.199 --> 00:06:28.950 align:start position:0% they are responsible for the data and as the<00:06:25.440> volume<00:06:26.039> of<00:06:26.199> the<00:06:26.440> data<00:06:26.960> inside<00:06:27.680> the<00:06:27.960> DHT 00:06:28.950 --> 00:06:28.960 align:start position:0% the volume of the data inside the DHT 00:06:28.960 --> 00:06:31.909 align:start position:0% the volume of the data inside the DHT increases<00:06:30.039> then<00:06:30.280> these<00:06:30.520> radi<00:06:31.280> they<00:06:31.560> they<00:06:31.680> get 00:06:31.909 --> 00:06:31.919 align:start position:0% increases then these radi they they get 00:06:31.919 --> 00:06:34.070 align:start position:0% increases then these radi they they get smaller<00:06:32.280> and<00:06:32.479> smaller<00:06:33.479> and<00:06:33.599> there<00:06:33.720> are<00:06:33.919> like 00:06:34.070 --> 00:06:34.080 align:start position:0% smaller and smaller and there are like 00:06:34.080 --> 00:06:37.029 align:start position:0% smaller and smaller and there are like two<00:06:34.360> situations<00:06:35.039> depicted<00:06:35.639> here<00:06:36.360> the<00:06:36.560> green 00:06:37.029 --> 00:06:37.039 align:start position:0% two situations depicted here the green 00:06:37.039 --> 00:06:40.110 align:start position:0% two situations depicted here the green situation<00:06:37.840> when<00:06:38.120> the<00:06:39.039> when<00:06:39.240> these<00:06:39.440> radi<00:06:39.919> are 00:06:40.110 --> 00:06:40.120 align:start position:0% situation when the when these radi are 00:06:40.120 --> 00:06:43.070 align:start position:0% situation when the when these radi are fairly<00:06:40.639> big<00:06:41.319> they<00:06:41.599> completely<00:06:42.280> overlap<00:06:42.919> the 00:06:43.070 --> 00:06:43.080 align:start position:0% fairly big they completely overlap the 00:06:43.080 --> 00:06:46.629 align:start position:0% fairly big they completely overlap the entire<00:06:43.960> space<00:06:44.960> and<00:06:45.280> of<00:06:45.440> course<00:06:45.880> if<00:06:46.080> the<00:06:46.240> system 00:06:46.629 --> 00:06:46.639 align:start position:0% entire space and of course if the system 00:06:46.639 --> 00:06:49.909 align:start position:0% entire space and of course if the system gets<00:06:46.960> overwhelmed<00:06:47.919> meaning<00:06:48.400> that<00:06:48.680> the<00:06:49.039> total 00:06:49.909 --> 00:06:49.919 align:start position:0% gets overwhelmed meaning that the total 00:06:49.919 --> 00:06:52.830 align:start position:0% gets overwhelmed meaning that the total the<00:06:50.080> total<00:06:50.400> storage<00:06:51.240> resource<00:06:52.240> inside<00:06:52.680> the 00:06:52.830 --> 00:06:52.840 align:start position:0% the total storage resource inside the 00:06:52.840 --> 00:06:55.350 align:start position:0% the total storage resource inside the system<00:06:53.160> is<00:06:53.639> insufficient<00:06:54.639> then<00:06:54.840> we<00:06:55.000> get<00:06:55.199> to 00:06:55.350 --> 00:06:55.360 align:start position:0% system is insufficient then we get to 00:06:55.360 --> 00:06:57.710 align:start position:0% system is insufficient then we get to this<00:06:55.599> rep<00:06:56.000> situation<00:06:56.960> when<00:06:57.160> they<00:06:57.280> are 00:06:57.710 --> 00:06:57.720 align:start position:0% this rep situation when they are 00:06:57.720 --> 00:07:02.350 align:start position:0% this rep situation when they are uncovered<00:06:58.720> places<00:06:59.840> so<00:07:00.199> this<00:07:00.400> is<00:07:00.800> when<00:07:01.800> so<00:07:02.080> this 00:07:02.350 --> 00:07:02.360 align:start position:0% uncovered places so this is when so this 00:07:02.360 --> 00:07:04.029 align:start position:0% uncovered places so this is when so this this<00:07:02.440> is<00:07:02.560> a<00:07:02.680> failure<00:07:03.039> mod<00:07:03.319> it's<00:07:03.440> a<00:07:03.560> graceful 00:07:04.029 --> 00:07:04.039 align:start position:0% this is a failure mod it's a graceful 00:07:04.039 --> 00:07:07.150 align:start position:0% this is a failure mod it's a graceful failure<00:07:04.560> but<00:07:04.680> it's<00:07:04.879> still<00:07:05.199> it's<00:07:05.360> it's<00:07:05.479> a 00:07:07.150 --> 00:07:07.160 align:start position:0% failure but it's still it's it's a 00:07:07.160 --> 00:07:10.629 align:start position:0% failure but it's still it's it's a failure<00:07:08.160> uh<00:07:08.840> and<00:07:09.280> this<00:07:09.520> system<00:07:10.039> provides<00:07:10.479> a 00:07:10.629 --> 00:07:10.639 align:start position:0% failure uh and this system provides a 00:07:10.639 --> 00:07:14.270 align:start position:0% failure uh and this system provides a natural<00:07:11.080> load<00:07:11.759> balancing<00:07:12.759> because<00:07:13.599> uh<00:07:13.879> since 00:07:14.270 --> 00:07:14.280 align:start position:0% natural load balancing because uh since 00:07:14.280 --> 00:07:19.029 align:start position:0% natural load balancing because uh since pieces<00:07:14.680> of<00:07:15.000> since<00:07:15.280> both<00:07:16.039> addresses<00:07:17.039> and<00:07:18.039> uh 00:07:19.029 --> 00:07:19.039 align:start position:0% pieces of since both addresses and uh 00:07:19.039 --> 00:07:22.550 align:start position:0% pieces of since both addresses and uh addresses<00:07:19.800> and<00:07:20.080> keys<00:07:20.879> are<00:07:21.240> result<00:07:22.240> from 00:07:22.550 --> 00:07:22.560 align:start position:0% addresses and keys are result from 00:07:22.560 --> 00:07:24.990 align:start position:0% addresses and keys are result from hashes<00:07:23.319> they<00:07:23.560> they're<00:07:23.720> uniformly 00:07:24.990 --> 00:07:25.000 align:start position:0% hashes they they're uniformly 00:07:25.000 --> 00:07:27.469 align:start position:0% hashes they they're uniformly distributed<00:07:26.000> that<00:07:26.240> it<00:07:26.400> means<00:07:26.840> that<00:07:27.120> all<00:07:27.319> the 00:07:27.469 --> 00:07:27.479 align:start position:0% distributed that it means that all the 00:07:27.479 --> 00:07:30.430 align:start position:0% distributed that it means that all the nodes<00:07:28.160> are 00:07:30.430 --> 00:07:30.440 align:start position:0% nodes are 00:07:30.440 --> 00:07:33.309 align:start position:0% nodes are exposed<00:07:30.960> to<00:07:31.240> roughly<00:07:31.639> the<00:07:31.800> same<00:07:32.039> load<00:07:32.800> so<00:07:33.160> this 00:07:33.309 --> 00:07:33.319 align:start position:0% exposed to roughly the same load so this 00:07:33.319 --> 00:07:38.430 align:start position:0% exposed to roughly the same load so this is<00:07:33.680> how<00:07:33.960> we<00:07:34.400> address<00:07:35.479> uh<00:07:36.479> address<00:07:37.440> uh 00:07:38.430 --> 00:07:38.440 align:start position:0% is how we address uh address uh 00:07:38.440 --> 00:07:41.270 align:start position:0% is how we address uh address uh redundancy<00:07:39.440> so<00:07:39.680> in<00:07:39.840> the<00:07:40.039> normal<00:07:40.639> situation 00:07:41.270 --> 00:07:41.280 align:start position:0% redundancy so in the normal situation 00:07:41.280 --> 00:07:43.909 align:start position:0% redundancy so in the normal situation which<00:07:41.400> is<00:07:41.680> depicted<00:07:42.199> with<00:07:42.360> green<00:07:42.800> here<00:07:43.360> if<00:07:43.560> one 00:07:43.909 --> 00:07:43.919 align:start position:0% which is depicted with green here if one 00:07:43.919 --> 00:07:47.830 align:start position:0% which is depicted with green here if one node<00:07:44.919> goes<00:07:45.319> offline<00:07:46.319> then<00:07:46.560> its<00:07:46.759> circle<00:07:47.639> is 00:07:47.830 --> 00:07:47.840 align:start position:0% node goes offline then its circle is 00:07:47.840 --> 00:07:50.070 align:start position:0% node goes offline then its circle is removed<00:07:48.319> of<00:07:48.479> course<00:07:49.000> but<00:07:49.240> still<00:07:49.720> all<00:07:49.919> the 00:07:50.070 --> 00:07:50.080 align:start position:0% removed of course but still all the 00:07:50.080 --> 00:07:52.550 align:start position:0% removed of course but still all the other<00:07:50.360> circles<00:07:51.120> still<00:07:51.479> cover<00:07:51.879> the<00:07:52.039> entire<00:07:52.440> all 00:07:52.550 --> 00:07:52.560 align:start position:0% other circles still cover the entire all 00:07:52.560 --> 00:07:55.149 align:start position:0% other circles still cover the entire all the<00:07:52.680> green<00:07:52.960> circles<00:07:53.840> still<00:07:54.199> cover<00:07:54.639> the<00:07:54.759> entire 00:07:55.149 --> 00:07:55.159 align:start position:0% the green circles still cover the entire 00:07:55.159 --> 00:07:59.950 align:start position:0% the green circles still cover the entire black<00:07:55.400> circle<00:07:56.319> so<00:07:56.639> that's<00:07:57.599> that's<00:07:57.960> how<00:07:58.840> ADH 00:07:59.950 --> 00:07:59.960 align:start position:0% black circle so that's that's how ADH 00:07:59.960 --> 00:08:02.790 align:start position:0% black circle so that's that's how ADH every<00:08:00.199> DHT<00:08:00.720> works<00:08:01.039> like<00:08:01.280> that<00:08:01.919> and<00:08:02.159> basically 00:08:02.790 --> 00:08:02.800 align:start position:0% every DHT works like that and basically 00:08:02.800 --> 00:08:04.990 align:start position:0% every DHT works like that and basically the<00:08:03.080> the<00:08:03.280> difference<00:08:03.720> between<00:08:04.039> the<00:08:04.240> different 00:08:04.990 --> 00:08:05.000 align:start position:0% the the difference between the different 00:08:05.000 --> 00:08:08.189 align:start position:0% the the difference between the different uh<00:08:05.319> dhts<00:08:06.319> largely<00:08:06.800> boiled<00:08:07.240> down<00:08:07.560> to<00:08:07.800> how<00:08:08.000> these 00:08:08.189 --> 00:08:08.199 align:start position:0% uh dhts largely boiled down to how these 00:08:08.199 --> 00:08:10.189 align:start position:0% uh dhts largely boiled down to how these nodes<00:08:08.479> are<00:08:08.720> connected<00:08:09.639> and<00:08:09.840> what<00:08:10.000> the 00:08:10.189 --> 00:08:10.199 align:start position:0% nodes are connected and what the 00:08:10.199 --> 00:08:13.029 align:start position:0% nodes are connected and what the distance<00:08:10.560> measure 00:08:13.029 --> 00:08:13.039 align:start position:0% distance measure 00:08:13.039 --> 00:08:16.230 align:start position:0% distance measure is<00:08:14.039> uh<00:08:14.199> so<00:08:14.400> let's<00:08:14.680> first<00:08:14.960> talk<00:08:15.319> about<00:08:16.000> the 00:08:16.230 --> 00:08:16.240 align:start position:0% is uh so let's first talk about the 00:08:16.240 --> 00:08:18.790 align:start position:0% is uh so let's first talk about the desirable<00:08:16.759> Network<00:08:17.240> topology<00:08:18.159> how<00:08:18.440> how<00:08:18.680> how 00:08:18.790 --> 00:08:18.800 align:start position:0% desirable Network topology how how how 00:08:18.800 --> 00:08:20.350 align:start position:0% desirable Network topology how how how to<00:08:18.960> connect<00:08:19.400> these 00:08:20.350 --> 00:08:20.360 align:start position:0% to connect these 00:08:20.360 --> 00:08:22.270 align:start position:0% to connect these nodes 00:08:22.270 --> 00:08:22.280 align:start position:0% nodes 00:08:22.280 --> 00:08:25.830 align:start position:0% nodes uh<00:08:23.280> oh<00:08:23.599> before<00:08:24.319> before<00:08:24.599> we<00:08:24.759> go<00:08:25.000> there<00:08:25.440> so 00:08:25.830 --> 00:08:25.840 align:start position:0% uh oh before before we go there so 00:08:25.840 --> 00:08:28.629 align:start position:0% uh oh before before we go there so suppose<00:08:26.520> this<00:08:26.720> node<00:08:27.159> is<00:08:27.400> interested<00:08:28.159> in<00:08:28.400> this 00:08:28.629 --> 00:08:28.639 align:start position:0% suppose this node is interested in this 00:08:28.639 --> 00:08:30.390 align:start position:0% suppose this node is interested in this piece<00:08:28.800> of<00:08:29.000> information 00:08:30.390 --> 00:08:30.400 align:start position:0% piece of information 00:08:30.400 --> 00:08:34.029 align:start position:0% piece of information then<00:08:30.680> they<00:08:30.960> need<00:08:31.320> to<00:08:32.320> need<00:08:32.519> to<00:08:32.839> follow<00:08:33.440> the<00:08:33.800> the 00:08:34.029 --> 00:08:34.039 align:start position:0% then they need to need to follow the the 00:08:34.039 --> 00:08:36.949 align:start position:0% then they need to need to follow the the path<00:08:34.440> through<00:08:34.680> the<00:08:34.839> ne<00:08:35.320> topology<00:08:36.320> so<00:08:36.599> that's 00:08:36.949 --> 00:08:36.959 align:start position:0% path through the ne topology so that's 00:08:36.959 --> 00:08:39.829 align:start position:0% path through the ne topology so that's that's<00:08:37.120> why<00:08:37.320> natur<00:08:37.719> topology<00:08:38.200> is<00:08:38.839> important 00:08:39.829 --> 00:08:39.839 align:start position:0% that's why natur topology is important 00:08:39.839 --> 00:08:42.750 align:start position:0% that's why natur topology is important so<00:08:40.440> we<00:08:40.880> we<00:08:41.000> we<00:08:41.120> are<00:08:41.440> building<00:08:41.919> a<00:08:42.120> scalable 00:08:42.750 --> 00:08:42.760 align:start position:0% so we we we are building a scalable 00:08:42.760 --> 00:08:46.190 align:start position:0% so we we we are building a scalable network<00:08:43.240> of<00:08:43.399> n<00:08:43.680> nodes<00:08:44.080> where<00:08:44.279> n<00:08:44.560> can<00:08:44.800> grow 00:08:46.190 --> 00:08:46.200 align:start position:0% network of n nodes where n can grow 00:08:46.200 --> 00:08:48.430 align:start position:0% network of n nodes where n can grow indefinitely<00:08:47.200> uh<00:08:47.320> the<00:08:47.519> first<00:08:47.800> thing<00:08:48.080> that<00:08:48.240> we 00:08:48.430 --> 00:08:48.440 align:start position:0% indefinitely uh the first thing that we 00:08:48.440 --> 00:08:50.949 align:start position:0% indefinitely uh the first thing that we want<00:08:48.839> is<00:08:49.000> a<00:08:49.160> low<00:08:49.560> diameter<00:08:50.399> that<00:08:50.600> comes 00:08:50.949 --> 00:08:50.959 align:start position:0% want is a low diameter that comes 00:08:50.959 --> 00:08:55.150 align:start position:0% want is a low diameter that comes directly<00:08:51.560> from<00:08:51.920> our<00:08:52.920> requirement<00:08:53.920> of<00:08:54.120> low 00:08:55.150 --> 00:08:55.160 align:start position:0% directly from our requirement of low 00:08:55.160 --> 00:08:59.710 align:start position:0% directly from our requirement of low latency<00:08:56.160> so<00:08:56.440> the<00:08:56.640> theoretical<00:08:57.360> minimum<00:08:58.079> is<00:08:58.800> uh 00:08:59.710 --> 00:08:59.720 align:start position:0% latency so the theoretical minimum is uh 00:08:59.720 --> 00:09:02.110 align:start position:0% latency so the theoretical minimum is uh order<00:09:00.200> one<00:09:00.800> so<00:09:01.040> for<00:09:01.240> example<00:09:01.640> if<00:09:01.720> you<00:09:01.880> think 00:09:02.110 --> 00:09:02.120 align:start position:0% order one so for example if you think 00:09:02.120 --> 00:09:04.470 align:start position:0% order one so for example if you think about<00:09:02.399> a<00:09:02.600> complete<00:09:03.079> graph<00:09:03.680> when<00:09:03.920> every<00:09:04.160> node 00:09:04.470 --> 00:09:04.480 align:start position:0% about a complete graph when every node 00:09:04.480 --> 00:09:06.910 align:start position:0% about a complete graph when every node nodes<00:09:04.959> every<00:09:05.200> other<00:09:05.440> node<00:09:06.320> there<00:09:06.680> the 00:09:06.910 --> 00:09:06.920 align:start position:0% nodes every other node there the 00:09:06.920 --> 00:09:10.310 align:start position:0% nodes every other node there the diameter<00:09:07.480> is<00:09:07.720> exactly<00:09:08.240> one<00:09:09.240> uh<00:09:09.480> for<00:09:09.760> those<00:09:10.040> of 00:09:10.310 --> 00:09:10.320 align:start position:0% diameter is exactly one uh for those of 00:09:10.320 --> 00:09:14.350 align:start position:0% diameter is exactly one uh for those of so<00:09:10.760> the<00:09:11.760> the<00:09:12.320> uh<00:09:12.480> definition<00:09:12.959> of<00:09:13.120> the<00:09:13.360> diameter 00:09:14.350 --> 00:09:14.360 align:start position:0% so the the uh definition of the diameter 00:09:14.360 --> 00:09:17.550 align:start position:0% so the the uh definition of the diameter is<00:09:14.680> the<00:09:14.920> longest<00:09:15.600> shortest<00:09:16.200> path<00:09:16.800> so<00:09:16.959> you<00:09:17.160> take 00:09:17.550 --> 00:09:17.560 align:start position:0% is the longest shortest path so you take 00:09:17.560 --> 00:09:19.710 align:start position:0% is the longest shortest path so you take every<00:09:17.839> pair<00:09:18.079> of<00:09:18.240> nodes<00:09:19.120> you<00:09:19.279> find<00:09:19.600> the 00:09:19.710 --> 00:09:19.720 align:start position:0% every pair of nodes you find the 00:09:19.720 --> 00:09:21.710 align:start position:0% every pair of nodes you find the shortest<00:09:20.279> path<00:09:20.560> between<00:09:20.959> them<00:09:21.399> and<00:09:21.600> the 00:09:21.710 --> 00:09:21.720 align:start position:0% shortest path between them and the 00:09:21.720 --> 00:09:23.949 align:start position:0% shortest path between them and the longest<00:09:22.200> of<00:09:22.440> these<00:09:22.880> across<00:09:23.200> all<00:09:23.440> the<00:09:23.560> pairs<00:09:23.800> of 00:09:23.949 --> 00:09:23.959 align:start position:0% longest of these across all the pairs of 00:09:23.959 --> 00:09:26.630 align:start position:0% longest of these across all the pairs of nodes<00:09:24.399> is<00:09:24.519> the<00:09:24.720> diameter<00:09:25.160> of<00:09:25.320> the<00:09:25.519> graph<00:09:26.360> so 00:09:26.630 --> 00:09:26.640 align:start position:0% nodes is the diameter of the graph so 00:09:26.640 --> 00:09:29.630 align:start position:0% nodes is the diameter of the graph so theoretically<00:09:27.480> it<00:09:27.600> can<00:09:27.800> be<00:09:28.000> as<00:09:28.160> low<00:09:28.440> as<00:09:28.640> one<00:09:29.079> or 00:09:29.630 --> 00:09:29.640 align:start position:0% theoretically it can be as low as one or 00:09:29.640 --> 00:09:32.030 align:start position:0% theoretically it can be as low as one or order<00:09:30.000> of<00:09:30.160> one<00:09:30.440> so<00:09:30.800> it<00:09:30.920> can<00:09:31.079> be<00:09:31.320> proportional 00:09:32.030 --> 00:09:32.040 align:start position:0% order of one so it can be proportional 00:09:32.040 --> 00:09:35.190 align:start position:0% order of one so it can be proportional to<00:09:32.480> to<00:09:33.200> it<00:09:33.320> can<00:09:33.519> be<00:09:33.720> a<00:09:34.120> fixed 00:09:35.190 --> 00:09:35.200 align:start position:0% to to it can be a fixed 00:09:35.200 --> 00:09:38.110 align:start position:0% to to it can be a fixed number<00:09:36.200> uh<00:09:36.360> and<00:09:36.519> the<00:09:36.720> acceptable<00:09:37.399> maximum<00:09:38.040> I 00:09:38.110 --> 00:09:38.120 align:start position:0% number uh and the acceptable maximum I 00:09:38.120 --> 00:09:40.910 align:start position:0% number uh and the acceptable maximum I would<00:09:38.360> say<00:09:38.680> that<00:09:38.839> it's<00:09:39.120> probably<00:09:39.560> log<00:09:39.839> n<00:09:40.720> so 00:09:40.910 --> 00:09:40.920 align:start position:0% would say that it's probably log n so 00:09:40.920 --> 00:09:44.230 align:start position:0% would say that it's probably log n so you<00:09:41.079> don't<00:09:41.440> want<00:09:42.079> the<00:09:43.079> you<00:09:43.240> don't<00:09:43.600> want<00:09:44.000> the 00:09:44.230 --> 00:09:44.240 align:start position:0% you don't want the you don't want the 00:09:44.240 --> 00:09:46.949 align:start position:0% you don't want the you don't want the diameter<00:09:44.920> to<00:09:45.079> be<00:09:45.519> longer<00:09:45.959> than<00:09:46.160> log<00:09:46.399> n<00:09:46.680> as<00:09:46.800> the 00:09:46.949 --> 00:09:46.959 align:start position:0% diameter to be longer than log n as the 00:09:46.959 --> 00:09:48.150 align:start position:0% diameter to be longer than log n as the network 00:09:48.150 --> 00:09:48.160 align:start position:0% network 00:09:48.160 --> 00:09:50.710 align:start position:0% network grows<00:09:49.160> the<00:09:49.320> other<00:09:49.560> thing<00:09:49.800> that<00:09:49.959> you<00:09:50.200> want<00:09:50.399> to 00:09:50.710 --> 00:09:50.720 align:start position:0% grows the other thing that you want to 00:09:50.720 --> 00:09:53.990 align:start position:0% grows the other thing that you want to limit<00:09:51.720> is<00:09:52.000> the<00:09:52.320> degree<00:09:52.720> of<00:09:52.880> the<00:09:53.040> nodes<00:09:53.519> so<00:09:53.839> how 00:09:53.990 --> 00:09:54.000 align:start position:0% limit is the degree of the nodes so how 00:09:54.000 --> 00:09:57.430 align:start position:0% limit is the degree of the nodes so how many<00:09:54.360> other<00:09:55.160> nodes<00:09:56.160> a<00:09:56.399> particular<00:09:56.920> node<00:09:57.240> is 00:09:57.430 --> 00:09:57.440 align:start position:0% many other nodes a particular node is 00:09:57.440 --> 00:10:00.310 align:start position:0% many other nodes a particular node is connected<00:09:58.040> to<00:09:59.040> again<00:09:59.480> the<00:09:59.640> theoretical 00:10:00.310 --> 00:10:00.320 align:start position:0% connected to again the theoretical 00:10:00.320 --> 00:10:02.670 align:start position:0% connected to again the theoretical minimum<00:10:00.880> is<00:10:01.040> order<00:10:01.440> one<00:10:01.800> so<00:10:02.079> it<00:10:02.240> it<00:10:02.360> is 00:10:02.670 --> 00:10:02.680 align:start position:0% minimum is order one so it it is 00:10:02.680 --> 00:10:06.430 align:start position:0% minimum is order one so it it is possible<00:10:03.120> to<00:10:03.440> achieve<00:10:03.920> even<00:10:04.480> Logan<00:10:05.480> diameter 00:10:06.430 --> 00:10:06.440 align:start position:0% possible to achieve even Logan diameter 00:10:06.440 --> 00:10:08.670 align:start position:0% possible to achieve even Logan diameter with<00:10:06.640> a<00:10:06.839> fixed<00:10:07.240> number<00:10:07.880> of 00:10:08.670 --> 00:10:08.680 align:start position:0% with a fixed number of 00:10:08.680 --> 00:10:11.230 align:start position:0% with a fixed number of nodes<00:10:09.680> I<00:10:09.760> will<00:10:10.000> show<00:10:10.200> you<00:10:10.360> an 00:10:11.230 --> 00:10:11.240 align:start position:0% nodes I will show you an 00:10:11.240 --> 00:10:14.509 align:start position:0% nodes I will show you an example<00:10:12.240> uh<00:10:12.560> so<00:10:12.800> that's<00:10:13.000> the<00:10:13.160> theoretical 00:10:14.509 --> 00:10:14.519 align:start position:0% example uh so that's the theoretical 00:10:14.519 --> 00:10:17.910 align:start position:0% example uh so that's the theoretical minimum<00:10:15.519> and<00:10:15.720> the<00:10:15.959> acceptable<00:10:16.720> maximum<00:10:17.600> is 00:10:17.910 --> 00:10:17.920 align:start position:0% minimum and the acceptable maximum is 00:10:17.920 --> 00:10:19.910 align:start position:0% minimum and the acceptable maximum is basically<00:10:18.480> something<00:10:18.959> proportional<00:10:19.560> to<00:10:19.720> the 00:10:19.910 --> 00:10:19.920 align:start position:0% basically something proportional to the 00:10:19.920 --> 00:10:23.790 align:start position:0% basically something proportional to the size<00:10:20.160> of<00:10:20.320> the<00:10:20.519> network<00:10:21.200> for<00:10:21.440> a<00:10:21.680> while<00:10:22.800> probably 00:10:23.790 --> 00:10:23.800 align:start position:0% size of the network for a while probably 00:10:23.800 --> 00:10:25.790 align:start position:0% size of the network for a while probably you<00:10:23.959> know<00:10:24.160> over<00:10:24.399> a<00:10:24.600> long<00:10:24.959> time<00:10:25.240> that<00:10:25.399> would<00:10:25.600> be 00:10:25.790 --> 00:10:25.800 align:start position:0% you know over a long time that would be 00:10:25.800 --> 00:10:27.389 align:start position:0% you know over a long time that would be less<00:10:26.000> and<00:10:26.240> less 00:10:27.389 --> 00:10:27.399 align:start position:0% less and less 00:10:27.399 --> 00:10:29.710 align:start position:0% less and less acceptable<00:10:28.399> and<00:10:28.600> the<00:10:28.800> problem<00:10:29.120> of<00:10:29.320> of<00:10:29.480> course 00:10:29.710 --> 00:10:29.720 align:start position:0% acceptable and the problem of of course 00:10:29.720 --> 00:10:33.269 align:start position:0% acceptable and the problem of of course with<00:10:29.880> a<00:10:30.079> large<00:10:30.440> number<00:10:31.000> of<00:10:31.480> uh<00:10:31.839> neighbors<00:10:32.839> is 00:10:33.269 --> 00:10:33.279 align:start position:0% with a large number of uh neighbors is 00:10:33.279 --> 00:10:35.870 align:start position:0% with a large number of uh neighbors is that<00:10:33.760> the<00:10:33.959> housekeeping<00:10:34.880> overhead 00:10:35.870 --> 00:10:35.880 align:start position:0% that the housekeeping overhead 00:10:35.880 --> 00:10:39.030 align:start position:0% that the housekeeping overhead maintaining<00:10:36.600> that<00:10:36.839> network<00:10:37.440> will<00:10:37.680> become<00:10:38.480> uh 00:10:39.030 --> 00:10:39.040 align:start position:0% maintaining that network will become uh 00:10:39.040 --> 00:10:41.190 align:start position:0% maintaining that network will become uh it<00:10:39.120> will<00:10:39.320> grow<00:10:39.639> and<00:10:39.800> it<00:10:39.959> will<00:10:40.240> become<00:10:41.000> a 00:10:41.190 --> 00:10:41.200 align:start position:0% it will grow and it will become a 00:10:41.200 --> 00:10:43.350 align:start position:0% it will grow and it will become a sizable<00:10:41.760> part<00:10:42.000> of<00:10:42.200> what<00:10:42.320> the<00:10:42.440> nodes<00:10:42.800> do 00:10:43.350 --> 00:10:43.360 align:start position:0% sizable part of what the nodes do 00:10:43.360 --> 00:10:46.949 align:start position:0% sizable part of what the nodes do instead<00:10:43.760> of<00:10:44.040> performing<00:10:44.639> their<00:10:44.959> direct 00:10:46.949 --> 00:10:46.959 align:start position:0% instead of performing their direct 00:10:46.959 --> 00:10:50.629 align:start position:0% instead of performing their direct duties<00:10:47.959> then<00:10:48.480> another<00:10:48.920> thing<00:10:49.200> that<00:10:49.399> you<00:10:49.639> want 00:10:50.629 --> 00:10:50.639 align:start position:0% duties then another thing that you want 00:10:50.639 --> 00:10:54.269 align:start position:0% duties then another thing that you want is<00:10:51.120> uniform<00:10:51.839> centrality<00:10:52.839> across<00:10:53.279> all<00:10:53.519> nodes 00:10:54.269 --> 00:10:54.279 align:start position:0% is uniform centrality across all nodes 00:10:54.279 --> 00:10:57.069 align:start position:0% is uniform centrality across all nodes so<00:10:54.480> what<00:10:54.680> centrality<00:10:55.399> is<00:10:56.000> centrality<00:10:56.680> in<00:10:56.800> a 00:10:57.069 --> 00:10:57.079 align:start position:0% so what centrality is centrality in a 00:10:57.079 --> 00:11:01.150 align:start position:0% so what centrality is centrality in a graph<00:10:57.839> is<00:10:58.160> defined<00:10:59.560> as<00:11:00.240> the<00:11:00.519> number<00:11:00.959> of 00:11:01.150 --> 00:11:01.160 align:start position:0% graph is defined as the number of 00:11:01.160 --> 00:11:04.190 align:start position:0% graph is defined as the number of shortest<00:11:01.959> paths<00:11:02.680> that<00:11:02.880> go<00:11:03.200> through<00:11:03.880> one 00:11:04.190 --> 00:11:04.200 align:start position:0% shortest paths that go through one 00:11:04.200 --> 00:11:06.350 align:start position:0% shortest paths that go through one particular<00:11:04.720> node<00:11:05.160> or<00:11:05.360> one<00:11:05.600> particular<00:11:06.079> Edge 00:11:06.350 --> 00:11:06.360 align:start position:0% particular node or one particular Edge 00:11:06.360 --> 00:11:08.190 align:start position:0% particular node or one particular Edge you<00:11:06.480> can<00:11:06.680> Define<00:11:06.959> Edge<00:11:07.279> centrality<00:11:07.760> and<00:11:07.920> note 00:11:08.190 --> 00:11:08.200 align:start position:0% you can Define Edge centrality and note 00:11:08.200 --> 00:11:10.790 align:start position:0% you can Define Edge centrality and note centrality<00:11:08.800> as<00:11:08.959> well<00:11:09.959> actually<00:11:10.519> this 00:11:10.790 --> 00:11:10.800 align:start position:0% centrality as well actually this 00:11:10.800 --> 00:11:11.870 align:start position:0% centrality as well actually this property 00:11:11.870 --> 00:11:11.880 align:start position:0% property 00:11:11.880 --> 00:11:15.350 align:start position:0% property centrality<00:11:12.880> was<00:11:13.639> uh<00:11:13.959> introduced<00:11:14.639> in<00:11:14.839> applied 00:11:15.350 --> 00:11:15.360 align:start position:0% centrality was uh introduced in applied 00:11:15.360 --> 00:11:17.949 align:start position:0% centrality was uh introduced in applied research<00:11:16.279> which<00:11:16.480> was<00:11:16.800> interested<00:11:17.560> in 00:11:17.949 --> 00:11:17.959 align:start position:0% research which was interested in 00:11:17.959 --> 00:11:20.590 align:start position:0% research which was interested in preventing<00:11:18.839> uh<00:11:19.000> sexually<00:11:19.880> communicable 00:11:20.590 --> 00:11:20.600 align:start position:0% preventing uh sexually communicable 00:11:20.600 --> 00:11:23.910 align:start position:0% preventing uh sexually communicable diseases<00:11:21.600> and<00:11:21.760> the<00:11:21.959> question<00:11:22.480> was<00:11:23.480> if<00:11:23.639> we<00:11:23.800> have 00:11:23.910 --> 00:11:23.920 align:start position:0% diseases and the question was if we have 00:11:23.920 --> 00:11:26.230 align:start position:0% diseases and the question was if we have a<00:11:24.120> limited<00:11:24.519> number<00:11:24.800> of<00:11:25.040> condoms<00:11:25.760> whom<00:11:25.959> are<00:11:26.079> we 00:11:26.230 --> 00:11:26.240 align:start position:0% a limited number of condoms whom are we 00:11:26.240 --> 00:11:27.790 align:start position:0% a limited number of condoms whom are we going<00:11:26.440> to<00:11:26.639> give 00:11:27.790 --> 00:11:27.800 align:start position:0% going to give 00:11:27.800 --> 00:11:31.509 align:start position:0% going to give them<00:11:28.800> uh<00:11:29.320> so<00:11:29.519> this<00:11:29.720> sort<00:11:30.000> of<00:11:30.639> uh<00:11:30.839> shows<00:11:31.240> you 00:11:31.509 --> 00:11:31.519 align:start position:0% them uh so this sort of uh shows you 00:11:31.519 --> 00:11:33.550 align:start position:0% them uh so this sort of uh shows you what<00:11:31.760> this<00:11:32.040> centrality<00:11:32.800> really 00:11:33.550 --> 00:11:33.560 align:start position:0% what this centrality really 00:11:33.560 --> 00:11:36.710 align:start position:0% what this centrality really means<00:11:34.560> uh<00:11:34.760> so<00:11:35.040> if<00:11:35.200> you<00:11:35.480> take<00:11:35.800> out<00:11:36.240> the<00:11:36.399> most 00:11:36.710 --> 00:11:36.720 align:start position:0% means uh so if you take out the most 00:11:36.720 --> 00:11:39.870 align:start position:0% means uh so if you take out the most Central<00:11:37.279> nodes<00:11:38.079> from<00:11:38.320> a<00:11:38.639> graph<00:11:39.399> the<00:11:39.600> graph 00:11:39.870 --> 00:11:39.880 align:start position:0% Central nodes from a graph the graph 00:11:39.880 --> 00:11:41.949 align:start position:0% Central nodes from a graph the graph will<00:11:40.079> fall<00:11:40.399> apart<00:11:40.880> the<00:11:41.000> connectivity<00:11:41.639> of<00:11:41.800> the 00:11:41.949 --> 00:11:41.959 align:start position:0% will fall apart the connectivity of the 00:11:41.959 --> 00:11:43.790 align:start position:0% will fall apart the connectivity of the graph<00:11:42.399> will 00:11:43.790 --> 00:11:43.800 align:start position:0% graph will 00:11:43.800 --> 00:11:48.910 align:start position:0% graph will uh<00:11:44.800> will<00:11:45.000> be<00:11:45.519> broken<00:11:46.519> so<00:11:47.240> the<00:11:47.920> centrality 00:11:48.910 --> 00:11:48.920 align:start position:0% uh will be broken so the centrality 00:11:48.920 --> 00:11:52.030 align:start position:0% uh will be broken so the centrality needs<00:11:49.240> to<00:11:49.440> be<00:11:49.920> uniform<00:11:50.920> in<00:11:51.079> order<00:11:51.440> for<00:11:51.800> there 00:11:52.030 --> 00:11:52.040 align:start position:0% needs to be uniform in order for there 00:11:52.040 --> 00:11:55.069 align:start position:0% needs to be uniform in order for there not<00:11:52.240> to<00:11:52.399> be<00:11:52.600> some<00:11:52.880> vulnerable<00:11:53.480> nodes<00:11:54.440> so<00:11:54.800> for 00:11:55.069 --> 00:11:55.079 align:start position:0% not to be some vulnerable nodes so for 00:11:55.079 --> 00:11:58.590 align:start position:0% not to be some vulnerable nodes so for the<00:11:55.480> cost<00:11:56.079> of<00:11:56.440> Bringing<00:11:56.959> Down<00:11:57.279> the<00:11:57.600> network 00:11:58.590 --> 00:11:58.600 align:start position:0% the cost of Bringing Down the network 00:11:58.600 --> 00:12:00.550 align:start position:0% the cost of Bringing Down the network would<00:11:58.760> should<00:11:58.959> be<00:11:59.399> High<00:12:00.040> because<00:12:00.279> if<00:12:00.399> the 00:12:00.550 --> 00:12:00.560 align:start position:0% would should be High because if the 00:12:00.560 --> 00:12:03.190 align:start position:0% would should be High because if the centrality<00:12:01.160> is<00:12:01.320> not<00:12:01.560> uniform<00:12:02.519> then<00:12:02.720> there's<00:12:03.000> a 00:12:03.190 --> 00:12:03.200 align:start position:0% centrality is not uniform then there's a 00:12:03.200 --> 00:12:05.350 align:start position:0% centrality is not uniform then there's a small<00:12:03.560> subset<00:12:04.040> of<00:12:04.200> nodes<00:12:04.720> that<00:12:04.880> if<00:12:04.959> you<00:12:05.160> take 00:12:05.350 --> 00:12:05.360 align:start position:0% small subset of nodes that if you take 00:12:05.360 --> 00:12:08.310 align:start position:0% small subset of nodes that if you take out<00:12:05.880> that<00:12:06.079> subset<00:12:06.519> of<00:12:06.680> nodes<00:12:07.399> then<00:12:07.600> your<00:12:07.839> graph 00:12:08.310 --> 00:12:08.320 align:start position:0% out that subset of nodes then your graph 00:12:08.320 --> 00:12:12.550 align:start position:0% out that subset of nodes then your graph is<00:12:09.320> falls<00:12:09.720> apart<00:12:10.560> which<00:12:10.720> is<00:12:11.040> bad<00:12:11.519> both<00:12:12.079> against 00:12:12.550 --> 00:12:12.560 align:start position:0% is falls apart which is bad both against 00:12:12.560 --> 00:12:16.069 align:start position:0% is falls apart which is bad both against random<00:12:13.000> failures<00:12:13.880> and<00:12:14.120> even<00:12:14.399> worse<00:12:14.880> against<00:12:15.360> a 00:12:16.069 --> 00:12:16.079 align:start position:0% random failures and even worse against a 00:12:16.079 --> 00:12:19.670 align:start position:0% random failures and even worse against a dedicated<00:12:17.079> uh<00:12:17.920> adversary<00:12:18.920> uh<00:12:19.160> because<00:12:19.480> all 00:12:19.670 --> 00:12:19.680 align:start position:0% dedicated uh adversary uh because all 00:12:19.680 --> 00:12:22.470 align:start position:0% dedicated uh adversary uh because all all<00:12:19.839> the<00:12:20.000> adversary<00:12:20.519> needs<00:12:20.800> to<00:12:21.000> do<00:12:21.600> is<00:12:21.760> to<00:12:22.000> map 00:12:22.470 --> 00:12:22.480 align:start position:0% all the adversary needs to do is to map 00:12:22.480 --> 00:12:25.110 align:start position:0% all the adversary needs to do is to map map<00:12:22.760> out<00:12:23.040> the<00:12:23.360> the<00:12:23.480> network<00:12:24.399> calculate<00:12:24.959> the 00:12:25.110 --> 00:12:25.120 align:start position:0% map out the the network calculate the 00:12:25.120 --> 00:12:28.269 align:start position:0% map out the the network calculate the centrality<00:12:25.839> and<00:12:26.079> then<00:12:26.920> Doos<00:12:27.920> the<00:12:28.040> most 00:12:28.269 --> 00:12:28.279 align:start position:0% centrality and then Doos the most 00:12:28.279 --> 00:12:31.030 align:start position:0% centrality and then Doos the most Central<00:12:28.680> nodes 00:12:31.030 --> 00:12:31.040 align:start position:0% Central nodes 00:12:31.040 --> 00:12:33.430 align:start position:0% Central nodes and<00:12:31.240> of<00:12:31.440> course<00:12:31.720> you<00:12:31.920> also<00:12:32.240> want<00:12:32.480> to<00:12:32.720> keep<00:12:33.079> the 00:12:33.430 --> 00:12:33.440 align:start position:0% and of course you also want to keep the 00:12:33.440 --> 00:12:36.509 align:start position:0% and of course you also want to keep the the<00:12:33.680> housekeeping<00:12:34.399> overhead<00:12:35.079> low<00:12:36.040> so<00:12:36.320> you 00:12:36.509 --> 00:12:36.519 align:start position:0% the housekeeping overhead low so you 00:12:36.519 --> 00:12:38.550 align:start position:0% the housekeeping overhead low so you want<00:12:36.800> some<00:12:37.160> Network<00:12:37.560> topology<00:12:38.160> which<00:12:38.279> is 00:12:38.550 --> 00:12:38.560 align:start position:0% want some Network topology which is 00:12:38.560 --> 00:12:39.509 align:start position:0% want some Network topology which is easily 00:12:39.509 --> 00:12:39.519 align:start position:0% easily 00:12:39.519 --> 00:12:41.990 align:start position:0% easily maintained<00:12:40.519> so<00:12:40.800> I<00:12:40.880> will<00:12:41.079> show<00:12:41.320> you<00:12:41.519> a<00:12:41.639> few 00:12:41.990 --> 00:12:42.000 align:start position:0% maintained so I will show you a few 00:12:42.000 --> 00:12:45.990 align:start position:0% maintained so I will show you a few examples<00:12:42.880> of<00:12:43.760> of<00:12:44.160> how<00:12:44.440> these<00:12:44.680> tradeoffs<00:12:45.680> can 00:12:45.990 --> 00:12:46.000 align:start position:0% examples of of how these tradeoffs can 00:12:46.000 --> 00:12:46.990 align:start position:0% examples of of how these tradeoffs can play 00:12:46.990 --> 00:12:47.000 align:start position:0% play 00:12:47.000 --> 00:12:50.949 align:start position:0% play out<00:12:48.000> uh<00:12:48.600> so<00:12:48.800> for<00:12:49.040> example<00:12:49.560> we<00:12:49.760> currently<00:12:50.399> have 00:12:50.949 --> 00:12:50.959 align:start position:0% out uh so for example we currently have 00:12:50.959 --> 00:12:54.670 align:start position:0% out uh so for example we currently have a<00:12:51.600> uh<00:12:52.600> a<00:12:52.880> pier<00:12:53.240> selection<00:12:53.720> algorithm<00:12:54.279> which<00:12:54.399> is 00:12:54.670 --> 00:12:54.680 align:start position:0% a uh a pier selection algorithm which is 00:12:54.680 --> 00:12:57.230 align:start position:0% a uh a pier selection algorithm which is that<00:12:54.920> simple<00:12:55.639> you<00:12:55.880> connect<00:12:56.440> to<00:12:56.680> the<00:12:56.839> nodes 00:12:57.230 --> 00:12:57.240 align:start position:0% that simple you connect to the nodes 00:12:57.240 --> 00:12:59.350 align:start position:0% that simple you connect to the nodes that<00:12:57.399> you<00:12:57.560> know<00:12:58.120> you<00:12:58.279> ask<00:12:58.560> them<00:12:58.720> about<00:12:59.199> other 00:12:59.350 --> 00:12:59.360 align:start position:0% that you know you ask them about other 00:12:59.360 --> 00:13:01.710 align:start position:0% that you know you ask them about other nodes<00:12:59.639> and<00:12:59.800> you<00:12:59.959> connect<00:13:00.279> to<00:13:00.480> those<00:13:01.199> without 00:13:01.710 --> 00:13:01.720 align:start position:0% nodes and you connect to those without 00:13:01.720 --> 00:13:03.829 align:start position:0% nodes and you connect to those without giving<00:13:02.000> it<00:13:02.160> too<00:13:02.360> much<00:13:02.600> consideration<00:13:03.360> perhaps 00:13:03.829 --> 00:13:03.839 align:start position:0% giving it too much consideration perhaps 00:13:03.839 --> 00:13:06.189 align:start position:0% giving it too much consideration perhaps you<00:13:04.360> you<00:13:04.519> stop<00:13:04.920> after<00:13:05.199> you<00:13:05.480> reach<00:13:05.760> a<00:13:05.920> certain 00:13:06.189 --> 00:13:06.199 align:start position:0% you you stop after you reach a certain 00:13:06.199 --> 00:13:10.110 align:start position:0% you you stop after you reach a certain node<00:13:06.839> limit<00:13:07.839> so<00:13:08.360> these<00:13:08.680> completely<00:13:09.160> at<00:13:09.399> hoc 00:13:10.110 --> 00:13:10.120 align:start position:0% node limit so these completely at hoc 00:13:10.120 --> 00:13:14.230 align:start position:0% node limit so these completely at hoc networks<00:13:11.600> they<00:13:12.600> they<00:13:12.839> go<00:13:13.120> through<00:13:13.440> a<00:13:13.839> phase 00:13:14.230 --> 00:13:14.240 align:start position:0% networks they they go through a phase 00:13:14.240 --> 00:13:18.430 align:start position:0% networks they they go through a phase transition<00:13:15.240> in<00:13:15.360> the<00:13:15.560> beginning<00:13:16.399> they're<00:13:17.440> they 00:13:18.430 --> 00:13:18.440 align:start position:0% transition in the beginning they're they 00:13:18.440 --> 00:13:20.829 align:start position:0% transition in the beginning they're they in<00:13:18.600> the<00:13:18.800> beginning<00:13:19.360> they<00:13:19.560> form<00:13:20.079> a<00:13:20.399> almost 00:13:20.829 --> 00:13:20.839 align:start position:0% in the beginning they form a almost 00:13:20.839 --> 00:13:24.710 align:start position:0% in the beginning they form a almost complete<00:13:21.320> graph<00:13:22.279> every<00:13:22.600> node<00:13:23.160> knows<00:13:24.000> a 00:13:24.710 --> 00:13:24.720 align:start position:0% complete graph every node knows a 00:13:24.720 --> 00:13:26.750 align:start position:0% complete graph every node knows a sizable<00:13:25.399> subset<00:13:25.920> of<00:13:26.079> the 00:13:26.750 --> 00:13:26.760 align:start position:0% sizable subset of the 00:13:26.760 --> 00:13:29.870 align:start position:0% sizable subset of the network<00:13:27.760> maybe<00:13:28.040> even<00:13:28.279> the<00:13:28.440> majority<00:13:28.839> of 00:13:29.870 --> 00:13:29.880 align:start position:0% network maybe even the majority of 00:13:29.880 --> 00:13:33.269 align:start position:0% network maybe even the majority of notes<00:13:30.880> so<00:13:31.079> it's<00:13:31.279> almost<00:13:31.880> complete<00:13:32.880> so<00:13:33.120> the 00:13:33.269 --> 00:13:33.279 align:start position:0% notes so it's almost complete so the 00:13:33.279 --> 00:13:36.269 align:start position:0% notes so it's almost complete so the number<00:13:33.600> of<00:13:33.800> neighbors<00:13:34.639> is<00:13:34.880> in<00:13:35.040> the<00:13:35.240> order<00:13:35.880> of 00:13:36.269 --> 00:13:36.279 align:start position:0% number of neighbors is in the order of 00:13:36.279 --> 00:13:39.590 align:start position:0% number of neighbors is in the order of the<00:13:36.480> size<00:13:36.720> of<00:13:36.839> the<00:13:37.399> network<00:13:38.399> the<00:13:38.639> diameter<00:13:39.399> is 00:13:39.590 --> 00:13:39.600 align:start position:0% the size of the network the diameter is 00:13:39.600 --> 00:13:41.350 align:start position:0% the size of the network the diameter is more<00:13:39.800> or<00:13:40.000> less<00:13:40.240> fixed<00:13:40.680> you<00:13:40.800> can<00:13:41.000> reach 00:13:41.350 --> 00:13:41.360 align:start position:0% more or less fixed you can reach 00:13:41.360 --> 00:13:43.629 align:start position:0% more or less fixed you can reach everybody<00:13:42.000> in<00:13:42.199> one<00:13:42.399> or<00:13:42.560> two 00:13:43.629 --> 00:13:43.639 align:start position:0% everybody in one or two 00:13:43.639 --> 00:13:47.030 align:start position:0% everybody in one or two hops<00:13:44.639> the<00:13:44.839> problem<00:13:45.279> is<00:13:45.480> that<00:13:45.639> in<00:13:45.880> this<00:13:46.120> face 00:13:47.030 --> 00:13:47.040 align:start position:0% hops the problem is that in this face 00:13:47.040 --> 00:13:50.230 align:start position:0% hops the problem is that in this face the<00:13:47.399> housekeeping<00:13:48.199> overhead<00:13:48.920> is<00:13:49.240> ballooning 00:13:50.230 --> 00:13:50.240 align:start position:0% the housekeeping overhead is ballooning 00:13:50.240 --> 00:13:53.870 align:start position:0% the housekeeping overhead is ballooning because<00:13:50.759> when<00:13:51.000> you<00:13:51.279> are<00:13:52.279> so<00:13:52.519> for<00:13:53.360> think<00:13:53.560> about 00:13:53.870 --> 00:13:53.880 align:start position:0% because when you are so for think about 00:13:53.880 --> 00:13:55.749 align:start position:0% because when you are so for think about just<00:13:54.079> pinging<00:13:54.519> all<00:13:54.720> the<00:13:54.839> other<00:13:55.040> nodes<00:13:55.639> you 00:13:55.749 --> 00:13:55.759 align:start position:0% just pinging all the other nodes you 00:13:55.759 --> 00:13:57.949 align:start position:0% just pinging all the other nodes you need<00:13:55.959> to<00:13:56.199> keep<00:13:56.480> track<00:13:56.800> of<00:13:57.000> their<00:13:57.279> addresses 00:13:57.949 --> 00:13:57.959 align:start position:0% need to keep track of their addresses 00:13:57.959 --> 00:13:59.990 align:start position:0% need to keep track of their addresses you<00:13:58.079> need<00:13:58.279> to<00:13:58.440> see<00:13:58.680> which<00:13:58.839> one<00:13:59.240> is<00:13:59.360> alive<00:13:59.720> so<00:13:59.880> a 00:13:59.990 --> 00:14:00.000 align:start position:0% you need to see which one is alive so a 00:14:00.000 --> 00:14:01.949 align:start position:0% you need to see which one is alive so a lot<00:14:00.160> of<00:14:00.360> traffic<00:14:00.680> on<00:14:00.839> the<00:14:01.000> wires<00:14:01.360> is<00:14:01.600> just 00:14:01.949 --> 00:14:01.959 align:start position:0% lot of traffic on the wires is just 00:14:01.959 --> 00:14:06.550 align:start position:0% lot of traffic on the wires is just pings<00:14:02.959> so<00:14:03.839> the<00:14:04.079> the<00:14:04.720> the<00:14:05.720> the<00:14:05.880> housekeeping 00:14:06.550 --> 00:14:06.560 align:start position:0% pings so the the the the housekeeping 00:14:06.560 --> 00:14:09.030 align:start position:0% pings so the the the the housekeeping overhead<00:14:07.279> is<00:14:07.480> actually<00:14:08.199> the<00:14:08.399> the<00:14:08.600> traffic 00:14:09.030 --> 00:14:09.040 align:start position:0% overhead is actually the the traffic 00:14:09.040 --> 00:14:11.670 align:start position:0% overhead is actually the the traffic generated<00:14:09.680> by<00:14:10.000> housekeeping<00:14:11.000> is<00:14:11.199> growing 00:14:11.670 --> 00:14:11.680 align:start position:0% generated by housekeeping is growing 00:14:11.680 --> 00:14:15.150 align:start position:0% generated by housekeeping is growing with<00:14:11.839> the<00:14:12.040> square<00:14:12.480> of<00:14:12.680> n<00:14:13.639> until<00:14:14.240> you<00:14:14.600> trans 00:14:15.150 --> 00:14:15.160 align:start position:0% with the square of n until you trans 00:14:15.160 --> 00:14:19.910 align:start position:0% with the square of n until you trans transition<00:14:15.720> to<00:14:15.920> this<00:14:16.120> other<00:14:16.720> phase<00:14:17.720> when<00:14:18.920> the 00:14:19.910 --> 00:14:19.920 align:start position:0% transition to this other phase when the 00:14:19.920 --> 00:14:22.310 align:start position:0% transition to this other phase when the the<00:14:20.160> number<00:14:20.440> of<00:14:20.639> nodes<00:14:21.120> that<00:14:21.360> one<00:14:21.639> particular 00:14:22.310 --> 00:14:22.320 align:start position:0% the number of nodes that one particular 00:14:22.320 --> 00:14:24.790 align:start position:0% the number of nodes that one particular node<00:14:22.680> knows<00:14:23.320> the<00:14:23.440> neighboring<00:14:23.959> nodes<00:14:24.600> is 00:14:24.790 --> 00:14:24.800 align:start position:0% node knows the neighboring nodes is 00:14:24.800 --> 00:14:26.870 align:start position:0% node knows the neighboring nodes is relatively<00:14:25.399> small<00:14:25.839> compared<00:14:26.199> to<00:14:26.320> the<00:14:26.519> size<00:14:26.720> of 00:14:26.870 --> 00:14:26.880 align:start position:0% relatively small compared to the size of 00:14:26.880 --> 00:14:29.670 align:start position:0% relatively small compared to the size of the<00:14:27.040> network<00:14:28.040> then<00:14:28.320> what<00:14:28.480> you<00:14:28.680> get<00:14:29.240> is<00:14:29.480> what 00:14:29.670 --> 00:14:29.680 align:start position:0% the network then what you get is what 00:14:29.680 --> 00:14:31.949 align:start position:0% the network then what you get is what mathematicians<00:14:30.440> call<00:14:30.639> a<00:14:30.800> scale<00:14:31.120> free 00:14:31.949 --> 00:14:31.959 align:start position:0% mathematicians call a scale free 00:14:31.959 --> 00:14:35.110 align:start position:0% mathematicians call a scale free graph<00:14:32.959> uh<00:14:33.120> where<00:14:33.360> you<00:14:33.680> have<00:14:34.120> a<00:14:34.519> wildly 00:14:35.110 --> 00:14:35.120 align:start position:0% graph uh where you have a wildly 00:14:35.120 --> 00:14:39.710 align:start position:0% graph uh where you have a wildly different<00:14:35.800> distribution<00:14:36.759> of<00:14:37.639> uh<00:14:38.639> of<00:14:38.839> degrees 00:14:39.710 --> 00:14:39.720 align:start position:0% different distribution of uh of degrees 00:14:39.720 --> 00:14:42.189 align:start position:0% different distribution of uh of degrees actually<00:14:40.120> they<00:14:40.279> follow<00:14:40.759> a<00:14:41.160> power<00:14:41.480> law<00:14:41.839> so<00:14:42.040> it's 00:14:42.189 --> 00:14:42.199 align:start position:0% actually they follow a power law so it's 00:14:42.199 --> 00:14:44.910 align:start position:0% actually they follow a power law so it's a<00:14:42.360> longtail<00:14:43.160> distribution<00:14:44.160> that's<00:14:44.440> usually 00:14:44.910 --> 00:14:44.920 align:start position:0% a longtail distribution that's usually 00:14:44.920 --> 00:14:47.189 align:start position:0% a longtail distribution that's usually how<00:14:45.199> natural<00:14:45.759> social<00:14:46.120> networks<00:14:46.639> work<00:14:46.920> so<00:14:47.079> if 00:14:47.189 --> 00:14:47.199 align:start position:0% how natural social networks work so if 00:14:47.199 --> 00:14:49.509 align:start position:0% how natural social networks work so if you<00:14:47.360> look<00:14:47.560> at<00:14:48.079> for<00:14:48.320> example<00:14:48.959> whom<00:14:49.240> people 00:14:49.509 --> 00:14:49.519 align:start position:0% you look at for example whom people 00:14:49.519 --> 00:14:52.350 align:start position:0% you look at for example whom people friend<00:14:49.920> on<00:14:50.240> Facebook<00:14:51.240> so<00:14:51.440> you<00:14:51.560> look<00:14:51.720> at<00:14:51.959> so 00:14:52.350 --> 00:14:52.360 align:start position:0% friend on Facebook so you look at so 00:14:52.360 --> 00:14:54.110 align:start position:0% friend on Facebook so you look at so social<00:14:52.680> networks<00:14:53.240> like<00:14:53.399> this<00:14:53.519> or<00:14:53.680> you<00:14:53.839> look<00:14:53.959> at 00:14:54.110 --> 00:14:54.120 align:start position:0% social networks like this or you look at 00:14:54.120 --> 00:14:56.749 align:start position:0% social networks like this or you look at front<00:14:54.440> to<00:14:54.600> front<00:14:54.880> computer<00:14:55.320> networks<00:14:56.320> or<00:14:56.519> you 00:14:56.749 --> 00:14:56.759 align:start position:0% front to front computer networks or you 00:14:56.759 --> 00:14:59.350 align:start position:0% front to front computer networks or you look<00:14:57.000> at<00:14:57.560> uh 00:14:59.350 --> 00:14:59.360 align:start position:0% look at uh 00:14:59.360 --> 00:15:01.910 align:start position:0% look at uh for<00:14:59.600> example<00:14:59.959> the<00:15:00.120> social<00:15:00.600> graph<00:15:00.839> of<00:15:00.959> sexual 00:15:01.910 --> 00:15:01.920 align:start position:0% for example the social graph of sexual 00:15:01.920 --> 00:15:05.150 align:start position:0% for example the social graph of sexual relationships<00:15:02.920> then<00:15:03.560> they<00:15:04.240> typically<00:15:05.040> they 00:15:05.150 --> 00:15:05.160 align:start position:0% relationships then they typically they 00:15:05.160 --> 00:15:07.030 align:start position:0% relationships then they typically they are<00:15:05.360> typically<00:15:05.759> these<00:15:06.000> scale<00:15:06.320> free<00:15:06.560> graphs<00:15:06.880> so 00:15:07.030 --> 00:15:07.040 align:start position:0% are typically these scale free graphs so 00:15:07.040 --> 00:15:08.710 align:start position:0% are typically these scale free graphs so in<00:15:07.199> nature<00:15:07.560> these<00:15:07.759> scale<00:15:08.040> threee<00:15:08.360> graphs 00:15:08.710 --> 00:15:08.720 align:start position:0% in nature these scale threee graphs 00:15:08.720 --> 00:15:11.749 align:start position:0% in nature these scale threee graphs they're<00:15:09.000> very<00:15:09.639> common<00:15:10.639> their<00:15:11.000> diameter 00:15:11.749 --> 00:15:11.759 align:start position:0% they're very common their diameter 00:15:11.759 --> 00:15:14.550 align:start position:0% they're very common their diameter statistically<00:15:12.680> is<00:15:13.120> is<00:15:13.440> pretty<00:15:13.720> low<00:15:14.199> so<00:15:14.399> these 00:15:14.550 --> 00:15:14.560 align:start position:0% statistically is is pretty low so these 00:15:14.560 --> 00:15:16.990 align:start position:0% statistically is is pretty low so these are<00:15:14.800> these<00:15:15.240> you<00:15:15.360> know<00:15:15.680> this<00:15:16.000> famous<00:15:16.360> 6<00:15:16.639> degrees 00:15:16.990 --> 00:15:17.000 align:start position:0% are these you know this famous 6 degrees 00:15:17.000 --> 00:15:19.509 align:start position:0% are these you know this famous 6 degrees of<00:15:17.240> separation<00:15:18.240> so<00:15:18.399> it's<00:15:18.639> actually<00:15:19.040> smaller 00:15:19.509 --> 00:15:19.519 align:start position:0% of separation so it's actually smaller 00:15:19.519 --> 00:15:23.430 align:start position:0% of separation so it's actually smaller than<00:15:19.759> log<00:15:20.000> n<00:15:20.600> it's<00:15:20.839> log<00:15:21.040> n<00:15:21.399> over<00:15:21.680> log<00:15:21.920> log<00:15:22.240> n<00:15:23.240> but 00:15:23.430 --> 00:15:23.440 align:start position:0% than log n it's log n over log log n but 00:15:23.440 --> 00:15:26.829 align:start position:0% than log n it's log n over log log n but that<00:15:23.639> just<00:15:24.120> statistically<00:15:25.120> it<00:15:25.959> so<00:15:26.199> and<00:15:26.440> the 00:15:26.829 --> 00:15:26.839 align:start position:0% that just statistically it so and the 00:15:26.839 --> 00:15:29.269 align:start position:0% that just statistically it so and the the<00:15:26.959> other<00:15:27.240> undesirable<00:15:28.160> property<00:15:28.720> of<00:15:29.000> scale 00:15:29.269 --> 00:15:29.279 align:start position:0% the other undesirable property of scale 00:15:29.279 --> 00:15:32.189 align:start position:0% the other undesirable property of scale free<00:15:29.519> graphs<00:15:30.360> is<00:15:30.600> that<00:15:30.839> their<00:15:31.120> centrality<00:15:32.040> is 00:15:32.189 --> 00:15:32.199 align:start position:0% free graphs is that their centrality is 00:15:32.199 --> 00:15:35.949 align:start position:0% free graphs is that their centrality is not<00:15:32.480> uniform<00:15:33.199> at<00:15:33.519> all<00:15:34.519> like<00:15:34.720> some<00:15:35.399> typically 00:15:35.949 --> 00:15:35.959 align:start position:0% not uniform at all like some typically 00:15:35.959 --> 00:15:38.910 align:start position:0% not uniform at all like some typically scale<00:15:36.319> free<00:15:36.639> graphs<00:15:37.639> have<00:15:38.040> a<00:15:38.279> very<00:15:38.560> small 00:15:38.910 --> 00:15:38.920 align:start position:0% scale free graphs have a very small 00:15:38.920 --> 00:15:41.069 align:start position:0% scale free graphs have a very small number<00:15:39.360> of<00:15:39.680> very<00:15:39.920> Central 00:15:41.069 --> 00:15:41.079 align:start position:0% number of very Central 00:15:41.079 --> 00:15:46.269 align:start position:0% number of very Central nodes<00:15:42.399> uh<00:15:43.399> which<00:15:43.600> is<00:15:44.000> interesting<00:15:45.000> uh<00:15:45.839> this 00:15:46.269 --> 00:15:46.279 align:start position:0% nodes uh which is interesting uh this 00:15:46.279 --> 00:15:49.949 align:start position:0% nodes uh which is interesting uh this fact<00:15:46.839> is<00:15:47.440> uh<00:15:48.319> widely<00:15:48.759> used<00:15:49.120> in<00:15:49.319> all<00:15:49.519> sorts<00:15:49.800> of 00:15:49.949 --> 00:15:49.959 align:start position:0% fact is uh widely used in all sorts of 00:15:49.959 --> 00:15:52.269 align:start position:0% fact is uh widely used in all sorts of social<00:15:50.319> engineering<00:15:51.160> from<00:15:51.560> marketing<00:15:52.040> to 00:15:52.269 --> 00:15:52.279 align:start position:0% social engineering from marketing to 00:15:52.279 --> 00:15:54.670 align:start position:0% social engineering from marketing to politics<00:15:53.199> that<00:15:53.360> there<00:15:53.440> are<00:15:53.680> these<00:15:53.959> influencer 00:15:54.670 --> 00:15:54.680 align:start position:0% politics that there are these influencer 00:15:54.680 --> 00:15:56.790 align:start position:0% politics that there are these influencer people<00:15:55.399> that<00:15:55.600> if<00:15:55.680> you<00:15:55.839> find<00:15:56.160> the<00:15:56.360> right<00:15:56.560> people 00:15:56.790 --> 00:15:56.800 align:start position:0% people that if you find the right people 00:15:56.800 --> 00:16:00.350 align:start position:0% people that if you find the right people to<00:15:57.000> influence<00:15:57.600> you<00:15:57.920> can<00:15:59.000> you<00:15:59.160> can<00:15:59.680> spread 00:16:00.350 --> 00:16:00.360 align:start position:0% to influence you can you can spread 00:16:00.360 --> 00:16:03.509 align:start position:0% to influence you can you can spread information<00:16:01.000> or<00:16:01.240> disease<00:16:01.600> or<00:16:02.319> whatever<00:16:03.319> uh 00:16:03.509 --> 00:16:03.519 align:start position:0% information or disease or whatever uh 00:16:03.519 --> 00:16:04.350 align:start position:0% information or disease or whatever uh very 00:16:04.350 --> 00:16:04.360 align:start position:0% very 00:16:04.360 --> 00:16:07.829 align:start position:0% very fast<00:16:05.360> or<00:16:05.639> when<00:16:05.839> you<00:16:05.959> want<00:16:06.199> to<00:16:06.440> bomb<00:16:06.959> a<00:16:07.319> railway 00:16:07.829 --> 00:16:07.839 align:start position:0% fast or when you want to bomb a railway 00:16:07.839 --> 00:16:11.550 align:start position:0% fast or when you want to bomb a railway Network<00:16:08.440> then<00:16:09.440> a<00:16:09.600> few<00:16:09.959> well-placed<00:16:10.600> bombs<00:16:11.000> can 00:16:11.550 --> 00:16:11.560 align:start position:0% Network then a few well-placed bombs can 00:16:11.560 --> 00:16:14.069 align:start position:0% Network then a few well-placed bombs can bring<00:16:11.959> a<00:16:12.120> an<00:16:12.319> economy<00:16:12.680> to<00:16:12.959> health<00:16:13.519> so<00:16:13.720> it's 00:16:14.069 --> 00:16:14.079 align:start position:0% bring a an economy to health so it's 00:16:14.079 --> 00:16:16.590 align:start position:0% bring a an economy to health so it's well<00:16:14.600> studied<00:16:15.600> uh<00:16:15.800> propert<00:16:16.240> and<00:16:16.360> it's<00:16:16.480> a 00:16:16.590 --> 00:16:16.600 align:start position:0% well studied uh propert and it's a 00:16:16.600 --> 00:16:19.030 align:start position:0% well studied uh propert and it's a well-known<00:16:17.120> property<00:16:17.440> of<00:16:17.560> scale<00:16:17.839> free<00:16:18.079> graphs 00:16:19.030 --> 00:16:19.040 align:start position:0% well-known property of scale free graphs 00:16:19.040 --> 00:16:21.749 align:start position:0% well-known property of scale free graphs so<00:16:19.319> basically<00:16:20.040> this<00:16:20.160> is<00:16:20.360> another<00:16:20.920> argument 00:16:21.749 --> 00:16:21.759 align:start position:0% so basically this is another argument 00:16:21.759 --> 00:16:24.069 align:start position:0% so basically this is another argument against<00:16:22.440> this<00:16:22.680> kind<00:16:22.839> of<00:16:23.079> at<00:16:23.279> hoc 00:16:24.069 --> 00:16:24.079 align:start position:0% against this kind of at hoc 00:16:24.079 --> 00:16:27.150 align:start position:0% against this kind of at hoc infrastructure<00:16:25.079> that<00:16:25.680> uh<00:16:26.360> in<00:16:26.560> addition<00:16:26.959> to 00:16:27.150 --> 00:16:27.160 align:start position:0% infrastructure that uh in addition to 00:16:27.160 --> 00:16:31.269 align:start position:0% infrastructure that uh in addition to the<00:16:27.360> large<00:16:28.000> housekeeping<00:16:28.639> cost<00:16:29.160> costs<00:16:30.160> uh<00:16:31.079> it 00:16:31.269 --> 00:16:31.279 align:start position:0% the large housekeeping cost costs uh it 00:16:31.279 --> 00:16:33.269 align:start position:0% the large housekeeping cost costs uh it we<00:16:31.399> will<00:16:31.600> have<00:16:31.759> centrality<00:16:32.560> problems<00:16:33.120> the 00:16:33.269 --> 00:16:33.279 align:start position:0% we will have centrality problems the 00:16:33.279 --> 00:16:35.350 align:start position:0% we will have centrality problems the network<00:16:33.759> will<00:16:33.920> not<00:16:34.120> be<00:16:34.360> resilient<00:16:35.040> there<00:16:35.160> will 00:16:35.350 --> 00:16:35.360 align:start position:0% network will not be resilient there will 00:16:35.360 --> 00:16:37.949 align:start position:0% network will not be resilient there will be<00:16:35.639> some<00:16:36.160> some<00:16:36.399> nodes<00:16:36.880> which<00:16:37.040> will<00:16:37.240> have<00:16:37.440> high 00:16:37.949 --> 00:16:37.959 align:start position:0% be some some nodes which will have high 00:16:37.959 --> 00:16:39.829 align:start position:0% be some some nodes which will have high centrality<00:16:38.959> because<00:16:39.240> of<00:16:39.399> their<00:16:39.639> high 00:16:39.829 --> 00:16:39.839 align:start position:0% centrality because of their high 00:16:39.839 --> 00:16:42.430 align:start position:0% centrality because of their high centrality<00:16:40.680> they<00:16:40.800> will<00:16:41.079> have<00:16:41.279> a<00:16:41.519> high<00:16:41.759> load<00:16:42.240> a 00:16:42.430 --> 00:16:42.440 align:start position:0% centrality they will have a high load a 00:16:42.440 --> 00:16:47.470 align:start position:0% centrality they will have a high load a disproportionally<00:16:43.399> high<00:16:44.000> load<00:16:45.000> and<00:16:45.519> uh 00:16:47.470 --> 00:16:47.480 align:start position:0% disproportionally high load and uh 00:16:47.480 --> 00:16:49.629 align:start position:0% disproportionally high load and uh okay<00:16:48.480> yep<00:16:48.800> here<00:16:48.959> we 00:16:49.629 --> 00:16:49.639 align:start position:0% okay yep here we 00:16:49.639 --> 00:16:51.629 align:start position:0% okay yep here we are<00:16:50.639> uh<00:16:50.959> they<00:16:51.079> will<00:16:51.279> have<00:16:51.399> a 00:16:51.629 --> 00:16:51.639 align:start position:0% are uh they will have a 00:16:51.639 --> 00:16:55.230 align:start position:0% are uh they will have a disproportionally<00:16:52.600> high<00:16:53.040> load<00:16:54.040> and 00:16:55.230 --> 00:16:55.240 align:start position:0% disproportionally high load and 00:16:55.240 --> 00:16:58.389 align:start position:0% disproportionally high load and uh<00:16:56.240> and<00:16:56.440> they<00:16:56.600> will<00:16:56.839> be<00:16:57.600> the<00:16:57.720> network<00:16:58.120> will<00:16:58.240> be 00:16:58.389 --> 00:16:58.399 align:start position:0% uh and they will be the network will be 00:16:58.399 --> 00:16:59.749 align:start position:0% uh and they will be the network will be vulnerable 00:16:59.749 --> 00:16:59.759 align:start position:0% vulnerable 00:16:59.759 --> 00:17:01.470 align:start position:0% vulnerable and<00:16:59.880> there's<00:17:00.160> another<00:17:00.639> problem<00:17:01.000> which<00:17:01.120> is<00:17:01.279> not 00:17:01.470 --> 00:17:01.480 align:start position:0% and there's another problem which is not 00:17:01.480 --> 00:17:04.829 align:start position:0% and there's another problem which is not mentioned<00:17:02.040> here<00:17:03.000> that<00:17:03.560> okay<00:17:04.000> we<00:17:04.240> have<00:17:04.559> a 00:17:04.829 --> 00:17:04.839 align:start position:0% mentioned here that okay we have a 00:17:04.839 --> 00:17:06.630 align:start position:0% mentioned here that okay we have a distance<00:17:05.319> measure<00:17:05.880> which<00:17:06.039> follows<00:17:06.480> the 00:17:06.630 --> 00:17:06.640 align:start position:0% distance measure which follows the 00:17:06.640 --> 00:17:10.510 align:start position:0% distance measure which follows the triangle<00:17:07.480> inequality<00:17:08.480> but<00:17:08.799> in<00:17:09.000> a<00:17:09.600> athoc<00:17:10.160> graph 00:17:10.510 --> 00:17:10.520 align:start position:0% triangle inequality but in a athoc graph 00:17:10.520 --> 00:17:13.549 align:start position:0% triangle inequality but in a athoc graph like<00:17:10.880> this<00:17:11.480> there's<00:17:11.959> no<00:17:12.959> there's<00:17:13.280> no 00:17:13.549 --> 00:17:13.559 align:start position:0% like this there's no there's no 00:17:13.559 --> 00:17:17.150 align:start position:0% like this there's no there's no guarantee<00:17:14.559> whatsoever<00:17:15.559> that<00:17:15.919> if<00:17:16.079> you<00:17:16.319> go<00:17:17.000> you 00:17:17.150 --> 00:17:17.160 align:start position:0% guarantee whatsoever that if you go you 00:17:17.160 --> 00:17:19.669 align:start position:0% guarantee whatsoever that if you go you know<00:17:17.360> along<00:17:17.679> the<00:17:17.880> gradient<00:17:18.439> like<00:17:18.600> you<00:17:18.799> always 00:17:19.669 --> 00:17:19.679 align:start position:0% know along the gradient like you always 00:17:19.679 --> 00:17:22.710 align:start position:0% know along the gradient like you always take<00:17:20.000> the<00:17:20.199> Hop<00:17:20.959> that<00:17:21.199> BR<00:17:21.600> that<00:17:22.160> brings<00:17:22.480> you 00:17:22.710 --> 00:17:22.720 align:start position:0% take the Hop that BR that brings you 00:17:22.720 --> 00:17:26.069 align:start position:0% take the Hop that BR that brings you closest<00:17:23.280> in<00:17:23.480> one<00:17:23.839> hop<00:17:24.839> to<00:17:25.079> the<00:17:25.439> to<00:17:25.600> your 00:17:26.069 --> 00:17:26.079 align:start position:0% closest in one hop to the to your 00:17:26.079 --> 00:17:28.350 align:start position:0% closest in one hop to the to your destination<00:17:27.079> then<00:17:27.280> you<00:17:27.400> will<00:17:27.760> actually 00:17:28.350 --> 00:17:28.360 align:start position:0% destination then you will actually 00:17:28.360 --> 00:17:30.590 align:start position:0% destination then you will actually follow<00:17:28.720> it<00:17:29.000> shortest<00:17:29.559> path<00:17:30.120> there's<00:17:30.400> there's 00:17:30.590 --> 00:17:30.600 align:start position:0% follow it shortest path there's there's 00:17:30.600 --> 00:17:33.470 align:start position:0% follow it shortest path there's there's no<00:17:30.799> guarantee<00:17:31.200> for<00:17:31.480> that<00:17:32.080> at 00:17:33.470 --> 00:17:33.480 align:start position:0% no guarantee for that at 00:17:33.480 --> 00:17:36.310 align:start position:0% no guarantee for that at all<00:17:34.480> actually<00:17:34.840> in<00:17:35.080> practice<00:17:35.480> it's<00:17:35.679> not<00:17:36.039> that 00:17:36.310 --> 00:17:36.320 align:start position:0% all actually in practice it's not that 00:17:36.320 --> 00:17:39.669 align:start position:0% all actually in practice it's not that bad<00:17:36.559> so<00:17:36.880> there<00:17:37.039> is<00:17:37.240> a<00:17:37.720> upper<00:17:38.640> upper 00:17:39.669 --> 00:17:39.679 align:start position:0% bad so there is a upper upper 00:17:39.679 --> 00:17:43.110 align:start position:0% bad so there is a upper upper bound<00:17:40.679> that<00:17:40.880> in<00:17:41.000> the<00:17:41.160> majority<00:17:41.600> of<00:17:41.960> cases<00:17:42.960> the 00:17:43.110 --> 00:17:43.120 align:start position:0% bound that in the majority of cases the 00:17:43.120 --> 00:17:46.750 align:start position:0% bound that in the majority of cases the number<00:17:43.360> of<00:17:43.559> hops<00:17:43.880> will<00:17:44.080> still<00:17:44.360> be<00:17:44.919> fairly<00:17:45.760> low 00:17:46.750 --> 00:17:46.760 align:start position:0% number of hops will still be fairly low 00:17:46.760 --> 00:17:52.190 align:start position:0% number of hops will still be fairly low so<00:17:46.960> it's<00:17:47.120> not<00:17:47.880> catastrophic<00:17:48.880> but<00:17:49.480> uh<00:17:50.480> but<00:17:51.200> it's 00:17:52.190 --> 00:17:52.200 align:start position:0% so it's not catastrophic but uh but it's 00:17:52.200 --> 00:17:55.750 align:start position:0% so it's not catastrophic but uh but it's it's<00:17:52.400> not<00:17:52.760> it's<00:17:53.000> definitely<00:17:53.440> not 00:17:55.750 --> 00:17:55.760 align:start position:0% 00:17:55.760 --> 00:17:58.549 align:start position:0% optimal<00:17:56.760> and<00:17:57.080> you<00:17:57.320> you<00:17:57.480> you<00:17:57.640> can<00:17:57.919> have<00:17:58.120> rare 00:17:58.549 --> 00:17:58.559 align:start position:0% optimal and you you you can have rare 00:17:58.559 --> 00:18:00.590 align:start position:0% optimal and you you you can have rare but<00:17:58.919> very<00:17:59.120> painful 00:18:00.590 --> 00:18:00.600 align:start position:0% but very painful 00:18:00.600 --> 00:18:06.070 align:start position:0% but very painful searches<00:18:01.600> so<00:18:02.679> okay<00:18:03.679> uh<00:18:04.240> but<00:18:04.919> the 00:18:06.070 --> 00:18:06.080 align:start position:0% searches so okay uh but the 00:18:06.080 --> 00:18:09.029 align:start position:0% searches so okay uh but the basic<00:18:07.080> the<00:18:07.320> basic<00:18:08.080> uh<00:18:08.159> so<00:18:08.360> I<00:18:08.440> would<00:18:08.640> not<00:18:08.840> like 00:18:09.029 --> 00:18:09.039 align:start position:0% basic the basic uh so I would not like 00:18:09.039 --> 00:18:14.270 align:start position:0% basic the basic uh so I would not like to<00:18:09.840> uh<00:18:10.000> change<00:18:10.640> the<00:18:10.960> basic<00:18:11.919> strategy<00:18:12.720> of<00:18:13.159> uh<00:18:14.000> of 00:18:14.270 --> 00:18:14.280 align:start position:0% to uh change the basic strategy of uh of 00:18:14.280 --> 00:18:18.510 align:start position:0% to uh change the basic strategy of uh of connecting<00:18:15.280> to<00:18:15.480> a<00:18:15.640> network<00:18:16.159> so<00:18:16.760> we<00:18:16.919> can<00:18:17.520> keep 00:18:18.510 --> 00:18:18.520 align:start position:0% connecting to a network so we can keep 00:18:18.520 --> 00:18:21.029 align:start position:0% connecting to a network so we can keep the<00:18:19.200> the<00:18:19.440> pattern<00:18:19.919> that<00:18:20.080> you<00:18:20.240> connect<00:18:20.600> to<00:18:20.799> one 00:18:21.029 --> 00:18:21.039 align:start position:0% the the pattern that you connect to one 00:18:21.039 --> 00:18:24.950 align:start position:0% the the pattern that you connect to one node<00:18:21.880> you<00:18:22.200> ask<00:18:23.159> about<00:18:23.520> its<00:18:23.799> neighbors<00:18:24.760> and 00:18:24.950 --> 00:18:24.960 align:start position:0% node you ask about its neighbors and 00:18:24.960 --> 00:18:28.870 align:start position:0% node you ask about its neighbors and then<00:18:25.200> by<00:18:25.400> some<00:18:25.640> clever<00:18:26.200> algorithm<00:18:27.200> you<00:18:27.559> select 00:18:28.870 --> 00:18:28.880 align:start position:0% then by some clever algorithm you select 00:18:28.880 --> 00:18:31.870 align:start position:0% then by some clever algorithm you select to<00:18:29.120> which<00:18:29.280> ones<00:18:29.600> to<00:18:29.799> connect<00:18:30.600> further<00:18:31.600> and 00:18:31.870 --> 00:18:31.880 align:start position:0% to which ones to connect further and 00:18:31.880 --> 00:18:33.950 align:start position:0% to which ones to connect further and actually<00:18:32.280> when<00:18:32.520> somebody<00:18:33.000> asks<00:18:33.400> you<00:18:33.679> about 00:18:33.950 --> 00:18:33.960 align:start position:0% actually when somebody asks you about 00:18:33.960 --> 00:18:35.789 align:start position:0% actually when somebody asks you about your<00:18:34.159> neighbors<00:18:34.679> you<00:18:34.799> can<00:18:35.000> also<00:18:35.280> be<00:18:35.480> clever 00:18:35.789 --> 00:18:35.799 align:start position:0% your neighbors you can also be clever 00:18:35.799 --> 00:18:38.710 align:start position:0% your neighbors you can also be clever and<00:18:35.960> not<00:18:36.120> tell<00:18:36.320> them<00:18:36.960> everything<00:18:37.960> so<00:18:38.320> by<00:18:38.559> by 00:18:38.710 --> 00:18:38.720 align:start position:0% and not tell them everything so by by 00:18:38.720 --> 00:18:41.110 align:start position:0% and not tell them everything so by by tweaking<00:18:39.360> these<00:18:39.559> two<00:18:39.880> things<00:18:40.520> you<00:18:40.679> can<00:18:40.880> even 00:18:41.110 --> 00:18:41.120 align:start position:0% tweaking these two things you can even 00:18:41.120 --> 00:18:43.230 align:start position:0% tweaking these two things you can even stay<00:18:41.480> compatible<00:18:42.120> with<00:18:42.280> the<00:18:42.400> original<00:18:42.919> peer 00:18:43.230 --> 00:18:43.240 align:start position:0% stay compatible with the original peer 00:18:43.240 --> 00:18:45.669 align:start position:0% stay compatible with the original peer peer<00:18:43.559> finding<00:18:43.960> algorithm<00:18:44.880> but<00:18:45.039> be<00:18:45.280> somewhat 00:18:45.669 --> 00:18:45.679 align:start position:0% peer finding algorithm but be somewhat 00:18:45.679 --> 00:18:50.669 align:start position:0% peer finding algorithm but be somewhat more<00:18:46.400> clever<00:18:47.400> and 00:18:50.669 --> 00:18:50.679 align:start position:0% 00:18:50.679 --> 00:18:53.230 align:start position:0% uh<00:18:51.679> and<00:18:52.000> and<00:18:52.240> and<00:18:52.400> and<00:18:52.520> achieve<00:18:52.919> some 00:18:53.230 --> 00:18:53.240 align:start position:0% uh and and and and achieve some 00:18:53.240 --> 00:18:56.669 align:start position:0% uh and and and and achieve some completely<00:18:53.720> different<00:18:54.640> topology<00:18:55.640> so<00:18:56.000> here's 00:18:56.669 --> 00:18:56.679 align:start position:0% completely different topology so here's 00:18:56.679 --> 00:18:58.789 align:start position:0% completely different topology so here's here's<00:18:56.960> another<00:18:57.400> example<00:18:57.919> these<00:18:58.039> are<00:18:58.280> the 00:18:58.789 --> 00:18:58.799 align:start position:0% here's another example these are the 00:18:58.799 --> 00:19:02.390 align:start position:0% here's another example these are the quazi<00:18:59.600> hierarchies<00:19:00.600> so<00:19:00.919> they<00:19:01.120> are<00:19:01.760> similar<00:19:02.200> to 00:19:02.390 --> 00:19:02.400 align:start position:0% quazi hierarchies so they are similar to 00:19:02.400 --> 00:19:04.669 align:start position:0% quazi hierarchies so they are similar to hierarchies<00:19:03.039> but<00:19:03.200> not<00:19:03.400> completely<00:19:04.000> so<00:19:04.280> just 00:19:04.669 --> 00:19:04.679 align:start position:0% hierarchies but not completely so just 00:19:04.679 --> 00:19:06.470 align:start position:0% hierarchies but not completely so just so<00:19:04.919> this<00:19:05.000> is<00:19:05.120> an<00:19:05.320> illustration<00:19:06.000> of<00:19:06.159> course<00:19:06.360> if 00:19:06.470 --> 00:19:06.480 align:start position:0% so this is an illustration of course if 00:19:06.480 --> 00:19:08.669 align:start position:0% so this is an illustration of course if you<00:19:06.600> are<00:19:06.840> doing<00:19:07.159> it<00:19:07.559> in<00:19:07.679> a<00:19:07.880> real<00:19:08.159> world 00:19:08.669 --> 00:19:08.679 align:start position:0% you are doing it in a real world 00:19:08.679 --> 00:19:11.590 align:start position:0% you are doing it in a real world scenario<00:19:09.480> it<00:19:09.600> will<00:19:09.799> never<00:19:10.120> be<00:19:10.400> this<00:19:10.640> nice<00:19:10.880> and 00:19:11.590 --> 00:19:11.600 align:start position:0% scenario it will never be this nice and 00:19:11.600 --> 00:19:15.390 align:start position:0% scenario it will never be this nice and regular<00:19:12.600> but<00:19:13.440> this<00:19:14.120> this<00:19:14.280> is<00:19:14.440> a<00:19:14.640> good<00:19:14.960> example 00:19:15.390 --> 00:19:15.400 align:start position:0% regular but this this is a good example 00:19:15.400 --> 00:19:17.870 align:start position:0% regular but this this is a good example of<00:19:15.640> the<00:19:15.840> kind<00:19:16.039> of<00:19:16.280> graph<00:19:16.679> that<00:19:16.880> you<00:19:17.520> you<00:19:17.600> will 00:19:17.870 --> 00:19:17.880 align:start position:0% of the kind of graph that you you will 00:19:17.880 --> 00:19:20.390 align:start position:0% of the kind of graph that you you will achieve<00:19:18.640> if<00:19:18.799> you<00:19:19.039> have<00:19:19.440> a 00:19:20.390 --> 00:19:20.400 align:start position:0% achieve if you have a 00:19:20.400 --> 00:19:23.070 align:start position:0% achieve if you have a limited<00:19:21.400> small<00:19:21.840> number<00:19:22.120> of<00:19:22.280> neighbors<00:19:22.840> so 00:19:23.070 --> 00:19:23.080 align:start position:0% limited small number of neighbors so 00:19:23.080 --> 00:19:25.590 align:start position:0% limited small number of neighbors so this<00:19:23.320> graph<00:19:23.600> is<00:19:23.760> for<00:19:23.960> example<00:19:24.320> three<00:19:24.760> regular 00:19:25.590 --> 00:19:25.600 align:start position:0% this graph is for example three regular 00:19:25.600 --> 00:19:28.789 align:start position:0% this graph is for example three regular it<00:19:25.799> can<00:19:26.039> grow<00:19:27.000> indefinitely<00:19:28.000> and<00:19:28.200> it's<00:19:28.400> still 00:19:28.789 --> 00:19:28.799 align:start position:0% it can grow indefinitely and it's still 00:19:28.799 --> 00:19:31.750 align:start position:0% it can grow indefinitely and it's still will<00:19:29.080> have<00:19:29.400> a<00:19:29.679> logarithmic 00:19:31.750 --> 00:19:31.760 align:start position:0% will have a logarithmic 00:19:31.760 --> 00:19:34.990 align:start position:0% will have a logarithmic diameter<00:19:32.760> uh<00:19:32.919> so<00:19:33.240> what<00:19:33.360> it<00:19:33.600> is<00:19:34.159> is<00:19:34.440> that<00:19:34.799> there 00:19:34.990 --> 00:19:35.000 align:start position:0% diameter uh so what it is is that there 00:19:35.000 --> 00:19:37.430 align:start position:0% diameter uh so what it is is that there there's<00:19:35.240> this<00:19:35.440> Central<00:19:35.840> node<00:19:36.679> it<00:19:36.880> has<00:19:37.039> three 00:19:37.430 --> 00:19:37.440 align:start position:0% there's this Central node it has three 00:19:37.440 --> 00:19:39.990 align:start position:0% there's this Central node it has three neighbors<00:19:38.440> these<00:19:38.640> neighbors<00:19:39.120> grow<00:19:39.520> binary 00:19:39.990 --> 00:19:40.000 align:start position:0% neighbors these neighbors grow binary 00:19:40.000 --> 00:19:42.310 align:start position:0% neighbors these neighbors grow binary trees<00:19:40.840> and<00:19:41.000> the<00:19:41.120> leaves<00:19:41.480> of<00:19:41.679> those<00:19:41.919> binary 00:19:42.310 --> 00:19:42.320 align:start position:0% trees and the leaves of those binary 00:19:42.320 --> 00:19:44.230 align:start position:0% trees and the leaves of those binary trees<00:19:42.600> are<00:19:42.799> connected<00:19:43.320> so<00:19:43.520> this<00:19:43.600> is<00:19:43.760> a<00:19:43.919> three 00:19:44.230 --> 00:19:44.240 align:start position:0% trees are connected so this is a three 00:19:44.240 --> 00:19:45.230 align:start position:0% trees are connected so this is a three regular 00:19:45.230 --> 00:19:45.240 align:start position:0% regular 00:19:45.240 --> 00:19:48.230 align:start position:0% regular graph<00:19:46.240> uh<00:19:46.640> logarithmic 00:19:48.230 --> 00:19:48.240 align:start position:0% graph uh logarithmic 00:19:48.240 --> 00:19:49.750 align:start position:0% graph uh logarithmic diameter 00:19:49.750 --> 00:19:49.760 align:start position:0% diameter 00:19:49.760 --> 00:19:52.230 align:start position:0% diameter constant<00:19:50.760> uh<00:19:51.039> neighbor<00:19:51.520> number<00:19:51.960> you<00:19:52.080> can 00:19:52.230 --> 00:19:52.240 align:start position:0% constant uh neighbor number you can 00:19:52.240 --> 00:19:55.029 align:start position:0% constant uh neighbor number you can achieve<00:19:52.720> this<00:19:53.400> the<00:19:53.640> problem<00:19:54.000> is<00:19:54.360> this<00:19:54.799> with 00:19:55.029 --> 00:19:55.039 align:start position:0% achieve this the problem is this with 00:19:55.039 --> 00:19:56.950 align:start position:0% achieve this the problem is this with this<00:19:55.240> is<00:19:55.440> also<00:19:55.799> that<00:19:55.960> the<00:19:56.120> centrality<00:19:56.720> of<00:19:56.880> the 00:19:56.950 --> 00:19:56.960 align:start position:0% this is also that the centrality of the 00:19:56.960 --> 00:19:59.510 align:start position:0% this is also that the centrality of the nodes<00:19:57.320> is<00:19:57.520> highly<00:19:57.880> variable<00:19:59.080> but<00:19:59.360> the 00:19:59.510 --> 00:19:59.520 align:start position:0% nodes is highly variable but the 00:19:59.520 --> 00:20:01.390 align:start position:0% nodes is highly variable but the housekeeping<00:20:00.159> overhead<00:20:00.679> on<00:20:00.799> the<00:20:00.960> other<00:20:01.159> hand 00:20:01.390 --> 00:20:01.400 align:start position:0% housekeeping overhead on the other hand 00:20:01.400 --> 00:20:05.230 align:start position:0% housekeeping overhead on the other hand is<00:20:01.640> really<00:20:01.960> really<00:20:02.240> really<00:20:02.640> short<00:20:03.480> so<00:20:03.760> if<00:20:04.240> you 00:20:05.230 --> 00:20:05.240 align:start position:0% is really really really short so if you 00:20:05.240 --> 00:20:07.950 align:start position:0% is really really really short so if you just<00:20:05.679> to<00:20:06.320> to<00:20:06.440> tell<00:20:06.760> you<00:20:06.960> how<00:20:07.280> these<00:20:07.520> kinds<00:20:07.760> of 00:20:07.950 --> 00:20:07.960 align:start position:0% just to to tell you how these kinds of 00:20:07.960 --> 00:20:11.149 align:start position:0% just to to tell you how these kinds of graphs<00:20:08.360> are<00:20:08.559> maintained<00:20:09.480> it's<00:20:09.760> very<00:20:10.159> similar 00:20:11.149 --> 00:20:11.159 align:start position:0% graphs are maintained it's very similar 00:20:11.159 --> 00:20:13.310 align:start position:0% graphs are maintained it's very similar how<00:20:11.440> real<00:20:11.760> armies<00:20:12.240> maintain<00:20:12.720> their<00:20:12.880> chain<00:20:13.159> of 00:20:13.310 --> 00:20:13.320 align:start position:0% how real armies maintain their chain of 00:20:13.320 --> 00:20:15.870 align:start position:0% how real armies maintain their chain of commands<00:20:14.080> so<00:20:14.240> if<00:20:14.320> a<00:20:14.520> generally<00:20:15.120> skilled<00:20:15.720> the 00:20:15.870 --> 00:20:15.880 align:start position:0% commands so if a generally skilled the 00:20:15.880 --> 00:20:18.390 align:start position:0% commands so if a generally skilled the Army<00:20:16.440> does<00:20:16.679> not<00:20:17.480> does<00:20:17.640> not<00:20:17.880> collapse 00:20:18.390 --> 00:20:18.400 align:start position:0% Army does not does not collapse 00:20:18.400 --> 00:20:21.070 align:start position:0% Army does not does not collapse immediately<00:20:19.400> so<00:20:19.640> there's<00:20:19.960> always<00:20:20.720> you<00:20:20.840> know 00:20:21.070 --> 00:20:21.080 align:start position:0% immediately so there's always you know 00:20:21.080 --> 00:20:23.990 align:start position:0% immediately so there's always you know all<00:20:21.720> all<00:20:21.840> the<00:20:21.960> soldiers<00:20:22.440> have<00:20:22.640> a<00:20:22.799> rank<00:20:23.559> they 00:20:23.990 --> 00:20:24.000 align:start position:0% all all the soldiers have a rank they 00:20:24.000 --> 00:20:25.470 align:start position:0% all all the soldiers have a rank they always<00:20:24.280> know<00:20:24.600> that<00:20:24.760> you<00:20:24.840> know<00:20:25.039> if<00:20:25.240> two 00:20:25.470 --> 00:20:25.480 align:start position:0% always know that you know if two 00:20:25.480 --> 00:20:27.510 align:start position:0% always know that you know if two soldiers<00:20:26.039> who<00:20:26.200> have<00:20:26.360> not<00:20:26.600> previously<00:20:27.080> met 00:20:27.510 --> 00:20:27.520 align:start position:0% soldiers who have not previously met 00:20:27.520 --> 00:20:30.270 align:start position:0% soldiers who have not previously met this<00:20:27.760> subordination<00:20:28.679> is<00:20:28.960> immediately 00:20:30.270 --> 00:20:30.280 align:start position:0% this subordination is immediately 00:20:30.280 --> 00:20:32.350 align:start position:0% this subordination is immediately established<00:20:31.280> and<00:20:31.440> you<00:20:31.600> know<00:20:31.799> they<00:20:31.960> have<00:20:32.120> some 00:20:32.350 --> 00:20:32.360 align:start position:0% established and you know they have some 00:20:32.360 --> 00:20:34.710 align:start position:0% established and you know they have some site<00:20:32.640> connections<00:20:33.400> about<00:20:34.039> like<00:20:34.360> where<00:20:34.559> where 00:20:34.710 --> 00:20:34.720 align:start position:0% site connections about like where where 00:20:34.720 --> 00:20:37.630 align:start position:0% site connections about like where where to<00:20:34.919> connect<00:20:35.280> in<00:20:35.480> case<00:20:36.240> some<00:20:36.919> some<00:20:37.080> nodes<00:20:37.360> fall 00:20:37.630 --> 00:20:37.640 align:start position:0% to connect in case some some nodes fall 00:20:37.640 --> 00:20:39.190 align:start position:0% to connect in case some some nodes fall out<00:20:37.840> so<00:20:38.039> it's<00:20:38.400> it's 00:20:39.190 --> 00:20:39.200 align:start position:0% out so it's it's 00:20:39.200 --> 00:20:42.390 align:start position:0% out so it's it's doable<00:20:40.200> so<00:20:40.440> you<00:20:40.600> you<00:20:40.720> can<00:20:41.000> build<00:20:42.000> in<00:20:42.159> a 00:20:42.390 --> 00:20:42.400 align:start position:0% doable so you you can build in a 00:20:42.400 --> 00:20:44.789 align:start position:0% doable so you you can build in a decentralized<00:20:43.360> fashion<00:20:43.840> by<00:20:44.039> each<00:20:44.240> node<00:20:44.520> only 00:20:44.789 --> 00:20:44.799 align:start position:0% decentralized fashion by each node only 00:20:44.799 --> 00:20:46.750 align:start position:0% decentralized fashion by each node only caring<00:20:45.200> about<00:20:45.480> its<00:20:45.640> own<00:20:45.880> surrounding<00:20:46.440> you<00:20:46.559> can 00:20:46.750 --> 00:20:46.760 align:start position:0% caring about its own surrounding you can 00:20:46.760 --> 00:20:49.669 align:start position:0% caring about its own surrounding you can build<00:20:47.080> grabs<00:20:47.520> like<00:20:47.799> this<00:20:48.799> but<00:20:49.120> I<00:20:49.240> think<00:20:49.520> that 00:20:49.669 --> 00:20:49.679 align:start position:0% build grabs like this but I think that 00:20:49.679 --> 00:20:52.070 align:start position:0% build grabs like this but I think that they're<00:20:49.960> still<00:20:50.640> too<00:20:50.919> vulnerable<00:20:51.600> and<00:20:51.840> they 00:20:52.070 --> 00:20:52.080 align:start position:0% they're still too vulnerable and they 00:20:52.080 --> 00:20:56.270 align:start position:0% they're still too vulnerable and they place<00:20:53.120> a<00:20:54.120> they<00:20:54.360> place<00:20:54.760> too<00:20:55.080> high<00:20:55.320> a<00:20:55.520> load<00:20:56.000> on 00:20:56.270 --> 00:20:56.280 align:start position:0% place a they place too high a load on 00:20:56.280 --> 00:20:59.830 align:start position:0% place a they place too high a load on some<00:20:56.600> Central<00:20:57.360> nodes<00:20:58.360> I'm<00:20:58.679> unfortunately<00:20:59.679> if 00:20:59.830 --> 00:20:59.840 align:start position:0% some Central nodes I'm unfortunately if 00:20:59.840 --> 00:21:03.430 align:start position:0% some Central nodes I'm unfortunately if you<00:21:00.080> keep<00:21:00.440> the<00:21:01.120> uh<00:21:01.400> degree<00:21:01.760> of<00:21:02.000> the<00:21:02.720> uh<00:21:02.840> nodes 00:21:03.430 --> 00:21:03.440 align:start position:0% you keep the uh degree of the uh nodes 00:21:03.440 --> 00:21:06.350 align:start position:0% you keep the uh degree of the uh nodes low<00:21:04.440> then<00:21:05.000> and<00:21:05.159> and<00:21:05.320> you<00:21:05.440> want<00:21:05.640> to<00:21:05.799> maintain<00:21:06.200> a 00:21:06.350 --> 00:21:06.360 align:start position:0% low then and and you want to maintain a 00:21:06.360 --> 00:21:08.830 align:start position:0% low then and and you want to maintain a logarithmic<00:21:07.000> diameter<00:21:07.760> you<00:21:07.919> cannot<00:21:08.360> avoid 00:21:08.830 --> 00:21:08.840 align:start position:0% logarithmic diameter you cannot avoid 00:21:08.840 --> 00:21:11.390 align:start position:0% logarithmic diameter you cannot avoid this<00:21:09.320> that's<00:21:09.840> a<00:21:10.080> mathematical 00:21:11.390 --> 00:21:11.400 align:start position:0% this that's a mathematical 00:21:11.400 --> 00:21:16.549 align:start position:0% this that's a mathematical result<00:21:12.400> so<00:21:12.840> what<00:21:13.039> I<00:21:13.279> propose<00:21:14.080> is<00:21:14.559> and<00:21:14.840> what<00:21:15.559> uh 00:21:16.549 --> 00:21:16.559 align:start position:0% result so what I propose is and what uh 00:21:16.559 --> 00:21:19.830 align:start position:0% result so what I propose is and what uh gab<00:21:16.840> also<00:21:17.200> proposes<00:21:17.919> is<00:21:18.120> taking<00:21:18.440> a<00:21:18.640> page<00:21:18.880> from 00:21:19.830 --> 00:21:19.840 align:start position:0% gab also proposes is taking a page from 00:21:19.840 --> 00:21:23.310 align:start position:0% gab also proposes is taking a page from cadamia<00:21:20.840> cadamia<00:21:21.679> is<00:21:21.880> not<00:21:22.320> optimal<00:21:23.000> in<00:21:23.159> the 00:21:23.310 --> 00:21:23.320 align:start position:0% cadamia cadamia is not optimal in the 00:21:23.320 --> 00:21:26.789 align:start position:0% cadamia cadamia is not optimal in the sense<00:21:23.640> that<00:21:23.799> it<00:21:23.960> doesn't<00:21:24.640> take<00:21:25.640> so<00:21:25.880> for<00:21:26.120> a 00:21:26.789 --> 00:21:26.799 align:start position:0% sense that it doesn't take so for a 00:21:26.799 --> 00:21:29.110 align:start position:0% sense that it doesn't take so for a logarithmic<00:21:27.480> number<00:21:27.760> of<00:21:27.960> Neighbors 00:21:29.110 --> 00:21:29.120 align:start position:0% logarithmic number of Neighbors 00:21:29.120 --> 00:21:31.549 align:start position:0% logarithmic number of Neighbors it<00:21:29.320> has<00:21:29.520> a<00:21:29.760> diameter<00:21:30.440> that<00:21:30.559> is<00:21:30.760> larger<00:21:31.240> than 00:21:31.549 --> 00:21:31.559 align:start position:0% it has a diameter that is larger than 00:21:31.559 --> 00:21:34.070 align:start position:0% it has a diameter that is larger than necessary<00:21:32.559> and<00:21:32.760> for<00:21:33.120> the<00:21:33.360> logarithmic 00:21:34.070 --> 00:21:34.080 align:start position:0% necessary and for the logarithmic 00:21:34.080 --> 00:21:36.230 align:start position:0% necessary and for the logarithmic diameter<00:21:34.760> it<00:21:34.919> has<00:21:35.039> a<00:21:35.200> number<00:21:35.480> of<00:21:35.640> neighbors 00:21:36.230 --> 00:21:36.240 align:start position:0% diameter it has a number of neighbors 00:21:36.240 --> 00:21:38.470 align:start position:0% diameter it has a number of neighbors that<00:21:36.360> is<00:21:36.760> larger<00:21:37.200> than<00:21:37.480> necessary<00:21:38.039> so<00:21:38.279> it's 00:21:38.470 --> 00:21:38.480 align:start position:0% that is larger than necessary so it's 00:21:38.480 --> 00:21:41.269 align:start position:0% that is larger than necessary so it's not<00:21:39.240> it<00:21:39.400> doesn't<00:21:39.760> take<00:21:40.000> anything<00:21:40.400> to<00:21:40.559> the 00:21:41.269 --> 00:21:41.279 align:start position:0% not it doesn't take anything to the 00:21:41.279 --> 00:21:45.230 align:start position:0% not it doesn't take anything to the extreme<00:21:42.279> but<00:21:42.919> it<00:21:43.440> like<00:21:43.720> both<00:21:44.120> both<00:21:44.480> values<00:21:45.000> are 00:21:45.230 --> 00:21:45.240 align:start position:0% extreme but it like both both values are 00:21:45.240 --> 00:21:46.789 align:start position:0% extreme but it like both both values are sort<00:21:45.520> of 00:21:46.789 --> 00:21:46.799 align:start position:0% sort of 00:21:46.799 --> 00:21:49.789 align:start position:0% sort of acceptable<00:21:47.799> and<00:21:48.200> for<00:21:48.559> this<00:21:49.000> like<00:21:49.240> this<00:21:49.400> is<00:21:49.559> an 00:21:49.789 --> 00:21:49.799 align:start position:0% acceptable and for this like this is an 00:21:49.799 --> 00:21:53.070 align:start position:0% acceptable and for this like this is an example<00:21:50.159> it's<00:21:50.279> a<00:21:50.440> hyper<00:21:51.159> Cube<00:21:52.159> uh<00:21:52.360> hyper<00:21:52.799> cubes 00:21:53.070 --> 00:21:53.080 align:start position:0% example it's a hyper Cube uh hyper cubes 00:21:53.080 --> 00:21:55.950 align:start position:0% example it's a hyper Cube uh hyper cubes are<00:21:53.520> also<00:21:53.880> like<00:21:54.159> that<00:21:54.360> so<00:21:54.640> cadam<00:21:55.279> results<00:21:55.679> in 00:21:55.950 --> 00:21:55.960 align:start position:0% are also like that so cadam results in 00:21:55.960 --> 00:21:59.950 align:start position:0% are also like that so cadam results in hyper<00:21:56.440> Cube<00:21:57.360> hyper<00:21:57.880> Cube<00:21:58.279> like 00:21:59.950 --> 00:21:59.960 align:start position:0% hyper Cube hyper Cube like 00:21:59.960 --> 00:22:03.149 align:start position:0% hyper Cube hyper Cube like topologies<00:22:00.960> so<00:22:01.279> here<00:22:01.720> every<00:22:02.120> note<00:22:02.840> so<00:22:03.080> there 00:22:03.149 --> 00:22:03.159 align:start position:0% topologies so here every note so there 00:22:03.159 --> 00:22:07.149 align:start position:0% topologies so here every note so there are<00:22:03.440> 16<00:22:03.919> notes<00:22:04.400> here<00:22:04.919> and<00:22:05.559> everyone<00:22:06.559> each<00:22:06.799> one 00:22:07.149 --> 00:22:07.159 align:start position:0% are 16 notes here and everyone each one 00:22:07.159 --> 00:22:09.710 align:start position:0% are 16 notes here and everyone each one has 00:22:09.710 --> 00:22:09.720 align:start position:0% 00:22:09.720 --> 00:22:13.870 align:start position:0% 4°<00:22:10.720> uh<00:22:11.360> cadamia<00:22:12.080> has<00:22:12.240> a<00:22:12.440> low<00:22:13.120> housekeeping 00:22:13.870 --> 00:22:13.880 align:start position:0% 4° uh cadamia has a low housekeeping 00:22:13.880 --> 00:22:16.710 align:start position:0% 4° uh cadamia has a low housekeeping overhead<00:22:14.640> it<00:22:14.840> has<00:22:15.039> a<00:22:15.400> perfectly<00:22:15.840> uniform 00:22:16.710 --> 00:22:16.720 align:start position:0% overhead it has a perfectly uniform 00:22:16.720 --> 00:22:19.750 align:start position:0% overhead it has a perfectly uniform centrality<00:22:17.720> and<00:22:17.960> I<00:22:18.080> think<00:22:18.400> what's<00:22:18.760> most<00:22:19.320> uh 00:22:19.750 --> 00:22:19.760 align:start position:0% centrality and I think what's most uh 00:22:19.760 --> 00:22:22.830 align:start position:0% centrality and I think what's most uh convincing<00:22:20.760> is<00:22:21.200> that<00:22:21.640> it<00:22:21.840> already<00:22:22.279> operates 00:22:22.830 --> 00:22:22.840 align:start position:0% convincing is that it already operates 00:22:22.840 --> 00:22:24.510 align:start position:0% convincing is that it already operates in<00:22:22.960> a<00:22:23.159> highly<00:22:23.480> hostile 00:22:24.510 --> 00:22:24.520 align:start position:0% in a highly hostile 00:22:24.520 --> 00:22:27.549 align:start position:0% in a highly hostile environment<00:22:25.520> because<00:22:26.039> cadamia<00:22:26.720> is<00:22:26.919> used<00:22:27.400> as 00:22:27.549 --> 00:22:27.559 align:start position:0% environment because cadamia is used as 00:22:27.559 --> 00:22:29.390 align:start position:0% environment because cadamia is used as the<00:22:27.799> DHT 00:22:29.390 --> 00:22:29.400 align:start position:0% the DHT 00:22:29.400 --> 00:22:33.669 align:start position:0% the DHT for<00:22:29.799> big<00:22:30.080> torant<00:22:31.080> for<00:22:31.440> the<00:22:31.960> uh<00:22:32.279> tracker<00:22:32.799> lless 00:22:33.669 --> 00:22:33.679 align:start position:0% for big torant for the uh tracker lless 00:22:33.679 --> 00:22:36.070 align:start position:0% for big torant for the uh tracker lless for<00:22:33.880> the<00:22:34.080> tracker<00:22:34.480> lless<00:22:34.760> torant<00:22:35.760> and<00:22:35.919> you 00:22:36.070 --> 00:22:36.080 align:start position:0% for the tracker lless torant and you 00:22:36.080 --> 00:22:39.390 align:start position:0% for the tracker lless torant and you know<00:22:36.720> there<00:22:36.840> are<00:22:37.159> many<00:22:37.880> highly<00:22:38.840> funded 00:22:39.390 --> 00:22:39.400 align:start position:0% know there are many highly funded 00:22:39.400 --> 00:22:41.669 align:start position:0% know there are many highly funded organizations<00:22:40.400> trying<00:22:40.720> to<00:22:40.919> disrupt<00:22:41.440> that 00:22:41.669 --> 00:22:41.679 align:start position:0% organizations trying to disrupt that 00:22:41.679 --> 00:22:44.549 align:start position:0% organizations trying to disrupt that Network<00:22:42.159> and<00:22:42.480> they<00:22:42.960> don't<00:22:43.760> don't<00:22:44.000> generally 00:22:44.549 --> 00:22:44.559 align:start position:0% Network and they don't don't generally 00:22:44.559 --> 00:22:47.710 align:start position:0% Network and they don't don't generally succeed<00:22:45.480> so<00:22:45.799> it<00:22:46.039> it<00:22:46.240> it<00:22:46.400> it<00:22:46.520> looks<00:22:46.760> like<00:22:46.919> a<00:22:47.080> good 00:22:47.710 --> 00:22:47.720 align:start position:0% succeed so it it it it looks like a good 00:22:47.720 --> 00:22:52.110 align:start position:0% succeed so it it it it looks like a good idea<00:22:48.720> uh<00:22:49.000> so<00:22:49.679> we<00:22:50.120> we<00:22:50.320> would<00:22:50.640> like<00:22:50.880> to<00:22:51.200> take<00:22:51.799> uh 00:22:52.110 --> 00:22:52.120 align:start position:0% idea uh so we we would like to take uh 00:22:52.120 --> 00:22:55.149 align:start position:0% idea uh so we we would like to take uh many<00:22:52.600> ideas<00:22:53.159> and<00:22:53.400> maybe<00:22:53.960> quite<00:22:54.120> a<00:22:54.240> bit<00:22:54.400> of<00:22:54.600> code 00:22:55.149 --> 00:22:55.159 align:start position:0% many ideas and maybe quite a bit of code 00:22:55.159 --> 00:22:58.630 align:start position:0% many ideas and maybe quite a bit of code from<00:22:55.960> kademlia<00:22:56.960> it<00:22:57.159> has<00:22:57.360> the<00:22:57.559> notion<00:22:58.080> of<00:22:58.240> the 00:22:58.630 --> 00:22:58.640 align:start position:0% from kademlia it has the notion of the 00:22:58.640 --> 00:22:59.950 align:start position:0% from kademlia it has the notion of the routing 00:22:59.950 --> 00:22:59.960 align:start position:0% routing 00:22:59.960 --> 00:23:05.390 align:start position:0% routing table<00:23:00.960> the<00:23:01.120> routing<00:23:01.760> table<00:23:02.760> is<00:23:03.720> basically<00:23:04.720> how 00:23:05.390 --> 00:23:05.400 align:start position:0% table the routing table is basically how 00:23:05.400 --> 00:23:09.510 align:start position:0% table the routing table is basically how the<00:23:06.400> how<00:23:06.799> the<00:23:07.039> node<00:23:07.880> structures<00:23:08.880> its 00:23:09.510 --> 00:23:09.520 align:start position:0% the how the node structures its 00:23:09.520 --> 00:23:12.990 align:start position:0% the how the node structures its neighbors<00:23:10.520> so<00:23:10.760> it<00:23:10.960> has<00:23:11.159> short<00:23:11.679> Li<00:23:12.080> lists<00:23:12.640> of 00:23:12.990 --> 00:23:13.000 align:start position:0% neighbors so it has short Li lists of 00:23:13.000 --> 00:23:15.470 align:start position:0% neighbors so it has short Li lists of live 00:23:15.470 --> 00:23:15.480 align:start position:0% live 00:23:15.480 --> 00:23:19.070 align:start position:0% live neighbors<00:23:16.480> uh<00:23:17.159> the<00:23:17.360> length<00:23:17.799> of<00:23:18.000> each<00:23:18.320> list<00:23:18.760> is 00:23:19.070 --> 00:23:19.080 align:start position:0% neighbors uh the length of each list is 00:23:19.080 --> 00:23:21.269 align:start position:0% neighbors uh the length of each list is maximized<00:23:19.760> at<00:23:19.919> some<00:23:20.159> small<00:23:20.480> number<00:23:20.919> which<00:23:21.080> is 00:23:21.269 --> 00:23:21.279 align:start position:0% maximized at some small number which is 00:23:21.279 --> 00:23:23.830 align:start position:0% maximized at some small number which is typically<00:23:22.000> between<00:23:22.559> five<00:23:22.760> and<00:23:23.000> 20<00:23:23.360> so<00:23:23.559> it's 00:23:23.830 --> 00:23:23.840 align:start position:0% typically between five and 20 so it's 00:23:23.840 --> 00:23:26.549 align:start position:0% typically between five and 20 so it's it's<00:23:24.000> not<00:23:24.200> really<00:23:24.400> a<00:23:24.559> large<00:23:25.000> number<00:23:26.000> and<00:23:26.200> for 00:23:26.549 --> 00:23:26.559 align:start position:0% it's not really a large number and for 00:23:26.559 --> 00:23:29.110 align:start position:0% it's not really a large number and for each<00:23:26.880> bit<00:23:27.120> of<00:23:27.279> the<00:23:27.520> address<00:23:28.120> they<00:23:28.279> have<00:23:28.600> have 00:23:29.110 --> 00:23:29.120 align:start position:0% each bit of the address they have have 00:23:29.120 --> 00:23:32.789 align:start position:0% each bit of the address they have have at<00:23:29.279> most<00:23:29.600> one<00:23:30.159> list<00:23:31.159> uh 00:23:32.789 --> 00:23:32.799 align:start position:0% at most one list uh 00:23:32.799 --> 00:23:38.190 align:start position:0% at most one list uh so<00:23:33.799> the<00:23:34.039> bits<00:23:34.480> means<00:23:35.120> that<00:23:36.080> so<00:23:36.480> for<00:23:37.000> each<00:23:38.000> each 00:23:38.190 --> 00:23:38.200 align:start position:0% so the bits means that so for each each 00:23:38.200 --> 00:23:42.430 align:start position:0% so the bits means that so for each each of<00:23:38.440> these<00:23:38.720> lists<00:23:39.400> correspond<00:23:40.400> to<00:23:40.640> nodes<00:23:41.559> whose 00:23:42.430 --> 00:23:42.440 align:start position:0% of these lists correspond to nodes whose 00:23:42.440 --> 00:23:46.590 align:start position:0% of these lists correspond to nodes whose address<00:23:43.440> is<00:23:43.760> the<00:23:43.960> same<00:23:44.480> up<00:23:44.679> to<00:23:44.919> that<00:23:45.360> bit<00:23:46.360> so 00:23:46.590 --> 00:23:46.600 align:start position:0% address is the same up to that bit so 00:23:46.600 --> 00:23:49.510 align:start position:0% address is the same up to that bit so the<00:23:46.799> first<00:23:47.200> list<00:23:47.799> doesn't<00:23:48.279> require 00:23:49.510 --> 00:23:49.520 align:start position:0% the first list doesn't require 00:23:49.520 --> 00:23:53.669 align:start position:0% the first list doesn't require any<00:23:50.520> uh<00:23:50.840> it<00:23:50.960> differs<00:23:51.360> even<00:23:51.559> in<00:23:51.720> the<00:23:51.880> first 00:23:53.669 --> 00:23:53.679 align:start position:0% any uh it differs even in the first 00:23:53.679 --> 00:23:58.549 align:start position:0% any uh it differs even in the first bit<00:23:54.679> uh<00:23:55.000> and<00:23:55.360> the<00:23:56.240> the<00:23:56.480> the<00:23:56.679> last<00:23:57.159> address<00:23:57.880> is 00:23:58.549 --> 00:23:58.559 align:start position:0% bit uh and the the the last address is 00:23:58.559 --> 00:24:01.269 align:start position:0% bit uh and the the the last address is one<00:23:59.400> the<00:23:59.559> last<00:23:59.880> list<00:24:00.240> which<00:24:00.360> is<00:24:00.600> where<00:24:00.799> it<00:24:01.000> is 00:24:01.269 --> 00:24:01.279 align:start position:0% one the last list which is where it is 00:24:01.279 --> 00:24:03.630 align:start position:0% one the last list which is where it is almost<00:24:01.640> always<00:24:02.000> empty<00:24:02.360> of<00:24:02.520> course<00:24:03.240> but<00:24:03.440> the 00:24:03.630 --> 00:24:03.640 align:start position:0% almost always empty of course but the 00:24:03.640 --> 00:24:07.669 align:start position:0% almost always empty of course but the last<00:24:04.000> list<00:24:05.000> contains<00:24:05.600> nodes<00:24:06.600> which<00:24:07.200> contains 00:24:07.669 --> 00:24:07.679 align:start position:0% last list contains nodes which contains 00:24:07.679 --> 00:24:09.830 align:start position:0% last list contains nodes which contains the<00:24:07.840> node<00:24:08.240> which<00:24:08.440> differs<00:24:08.840> in<00:24:09.080> only<00:24:09.320> one<00:24:09.600> bit 00:24:09.830 --> 00:24:09.840 align:start position:0% the node which differs in only one bit 00:24:09.840 --> 00:24:11.510 align:start position:0% the node which differs in only one bit of<00:24:10.000> course<00:24:10.159> it<00:24:10.279> never<00:24:10.559> happens<00:24:10.880> in<00:24:11.080> practice 00:24:11.510 --> 00:24:11.520 align:start position:0% of course it never happens in practice 00:24:11.520 --> 00:24:14.269 align:start position:0% of course it never happens in practice that<00:24:11.799> even<00:24:12.120> that<00:24:12.320> list<00:24:12.640> is<00:24:13.520> has<00:24:13.720> something<00:24:14.080> in 00:24:14.269 --> 00:24:14.279 align:start position:0% that even that list is has something in 00:24:14.279 --> 00:24:18.830 align:start position:0% that even that list is has something in it<00:24:15.279> so<00:24:15.799> cadamia<00:24:16.640> has<00:24:16.919> a<00:24:17.320> very<00:24:17.679> peculiar<00:24:18.679> uh 00:24:18.830 --> 00:24:18.840 align:start position:0% it so cadamia has a very peculiar uh 00:24:18.840 --> 00:24:21.789 align:start position:0% it so cadamia has a very peculiar uh distance<00:24:19.279> measure<00:24:20.159> it's<00:24:20.360> the<00:24:20.520> exor<00:24:21.080> Matrix<00:24:21.559> so 00:24:21.789 --> 00:24:21.799 align:start position:0% distance measure it's the exor Matrix so 00:24:21.799 --> 00:24:24.470 align:start position:0% distance measure it's the exor Matrix so they<00:24:22.000> take<00:24:22.400> the<00:24:22.520> xort<00:24:23.080> of<00:24:23.240> the<00:24:23.360> two<00:24:23.600> addresses 00:24:24.470 --> 00:24:24.480 align:start position:0% they take the xort of the two addresses 00:24:24.480 --> 00:24:26.310 align:start position:0% they take the xort of the two addresses and<00:24:24.640> treat<00:24:24.880> it<00:24:25.039> as<00:24:25.159> a<00:24:25.279> binary 00:24:26.310 --> 00:24:26.320 align:start position:0% and treat it as a binary 00:24:26.320 --> 00:24:29.710 align:start position:0% and treat it as a binary number<00:24:27.320> uh<00:24:27.799> say<00:24:28.159> good<00:24:28.520> exercise<00:24:29.080> to<00:24:29.399> check 00:24:29.710 --> 00:24:29.720 align:start position:0% number uh say good exercise to check 00:24:29.720 --> 00:24:32.350 align:start position:0% number uh say good exercise to check that<00:24:29.919> it's<00:24:30.120> really<00:24:30.399> a<00:24:30.640> distance 00:24:32.350 --> 00:24:32.360 align:start position:0% that it's really a distance 00:24:32.360 --> 00:24:34.710 align:start position:0% that it's really a distance measure 00:24:34.710 --> 00:24:34.720 align:start position:0% measure 00:24:34.720 --> 00:24:39.389 align:start position:0% measure uh<00:24:35.720> when<00:24:36.120> a<00:24:36.480> node<00:24:37.240> asks<00:24:37.720> another 00:24:39.389 --> 00:24:39.399 align:start position:0% uh when a node asks another 00:24:39.399 --> 00:24:42.590 align:start position:0% uh when a node asks another node<00:24:40.399> about<00:24:40.840> the<00:24:41.000> neighbors<00:24:41.640> that<00:24:41.880> they<00:24:42.080> know 00:24:42.590 --> 00:24:42.600 align:start position:0% node about the neighbors that they know 00:24:42.600 --> 00:24:44.750 align:start position:0% node about the neighbors that they know you<00:24:42.760> don't<00:24:43.120> tell<00:24:43.399> them<00:24:43.640> the<00:24:43.799> entire<00:24:44.159> routing 00:24:44.750 --> 00:24:44.760 align:start position:0% you don't tell them the entire routing 00:24:44.760 --> 00:24:47.029 align:start position:0% you don't tell them the entire routing table<00:24:45.200> you<00:24:45.399> tell<00:24:45.640> them<00:24:45.880> only<00:24:46.159> one 00:24:47.029 --> 00:24:47.039 align:start position:0% table you tell them only one 00:24:47.039 --> 00:24:51.710 align:start position:0% table you tell them only one list<00:24:48.039> uh<00:24:48.600> so<00:24:48.760> for<00:24:49.000> each<00:24:49.279> lookup<00:24:50.159> you<00:24:50.399> try<00:24:50.799> to 00:24:51.710 --> 00:24:51.720 align:start position:0% list uh so for each lookup you try to 00:24:51.720 --> 00:24:54.430 align:start position:0% list uh so for each lookup you try to for<00:24:51.960> each<00:24:52.520> each<00:24:52.720> lookup<00:24:53.080> that<00:24:53.320> another<00:24:53.679> node 00:24:54.430 --> 00:24:54.440 align:start position:0% for each each lookup that another node 00:24:54.440 --> 00:24:57.269 align:start position:0% for each each lookup that another node uh<00:24:54.679> makes<00:24:55.679> lookup<00:24:56.080> request<00:24:56.480> makes<00:24:56.799> at<00:24:57.000> you 00:24:57.269 --> 00:24:57.279 align:start position:0% uh makes lookup request makes at you 00:24:57.279 --> 00:24:59.990 align:start position:0% uh makes lookup request makes at you what<00:24:57.399> you<00:24:57.559> do<00:24:58.039> you<00:24:58.440> try<00:24:58.720> to<00:24:58.919> place<00:24:59.279> that<00:24:59.480> lookup 00:24:59.990 --> 00:25:00.000 align:start position:0% what you do you try to place that lookup 00:25:00.000 --> 00:25:02.669 align:start position:0% what you do you try to place that lookup on<00:25:00.200> your<00:25:00.440> lists<00:25:01.279> so<00:25:01.600> which<00:25:01.799> list<00:25:02.120> corresponds 00:25:02.669 --> 00:25:02.679 align:start position:0% on your lists so which list corresponds 00:25:02.679 --> 00:25:04.830 align:start position:0% on your lists so which list corresponds to<00:25:02.880> that<00:25:03.039> lookup<00:25:03.600> and<00:25:03.720> you<00:25:03.880> reveal<00:25:04.279> only<00:25:04.640> that 00:25:04.830 --> 00:25:04.840 align:start position:0% to that lookup and you reveal only that 00:25:04.840 --> 00:25:07.990 align:start position:0% to that lookup and you reveal only that list<00:25:05.080> you<00:25:05.200> don't<00:25:05.559> upload<00:25:05.960> your<00:25:06.559> entire<00:25:07.559> uh 00:25:07.990 --> 00:25:08.000 align:start position:0% list you don't upload your entire uh 00:25:08.000 --> 00:25:09.510 align:start position:0% list you don't upload your entire uh routing 00:25:09.510 --> 00:25:09.520 align:start position:0% routing 00:25:09.520 --> 00:25:12.190 align:start position:0% routing table<00:25:10.520> and<00:25:10.720> when<00:25:10.880> you<00:25:11.000> are<00:25:11.240> updating<00:25:11.840> your 00:25:12.190 --> 00:25:12.200 align:start position:0% table and when you are updating your 00:25:12.200 --> 00:25:14.470 align:start position:0% table and when you are updating your routing<00:25:12.679> tables<00:25:13.320> because<00:25:13.600> some<00:25:13.799> new<00:25:13.960> nodes 00:25:14.470 --> 00:25:14.480 align:start position:0% routing tables because some new nodes 00:25:14.480 --> 00:25:16.830 align:start position:0% routing tables because some new nodes come<00:25:15.240> come<00:25:15.440> in<00:25:15.720> you<00:25:15.840> learn<00:25:16.159> about<00:25:16.440> some<00:25:16.640> new 00:25:16.830 --> 00:25:16.840 align:start position:0% come come in you learn about some new 00:25:16.840 --> 00:25:19.269 align:start position:0% come come in you learn about some new nodes<00:25:17.840> then<00:25:18.159> what<00:25:18.279> you 00:25:19.269 --> 00:25:19.279 align:start position:0% nodes then what you 00:25:19.279 --> 00:25:22.630 align:start position:0% nodes then what you do<00:25:20.279> is<00:25:20.520> when<00:25:20.720> a<00:25:20.960> list<00:25:21.360> gets 00:25:22.630 --> 00:25:22.640 align:start position:0% do is when a list gets 00:25:22.640 --> 00:25:27.310 align:start position:0% do is when a list gets full<00:25:23.640> then<00:25:24.600> if<00:25:24.919> the<00:25:25.159> list<00:25:25.840> is<00:25:26.520> for<00:25:26.840> longer 00:25:27.310 --> 00:25:27.320 align:start position:0% full then if the list is for longer 00:25:27.320 --> 00:25:29.310 align:start position:0% full then if the list is for longer matching<00:25:27.840> prefixes<00:25:28.440> is<00:25:28.600> so<00:25:28.880> there<00:25:29.080> there's 00:25:29.310 --> 00:25:29.320 align:start position:0% matching prefixes is so there there's 00:25:29.320 --> 00:25:31.990 align:start position:0% matching prefixes is so there there's some<00:25:29.640> space<00:25:30.000> in<00:25:30.159> longer<00:25:30.520> matching<00:25:31.000> prefixes 00:25:31.990 --> 00:25:32.000 align:start position:0% some space in longer matching prefixes 00:25:32.000 --> 00:25:34.630 align:start position:0% some space in longer matching prefixes so<00:25:32.320> the<00:25:32.720> the 00:25:34.630 --> 00:25:34.640 align:start position:0% so the the 00:25:34.640 --> 00:25:37.830 align:start position:0% so the the list<00:25:35.640> so<00:25:35.799> for<00:25:36.000> example<00:25:36.760> you<00:25:36.960> you<00:25:37.120> have<00:25:37.279> a<00:25:37.520> list 00:25:37.830 --> 00:25:37.840 align:start position:0% list so for example you you have a list 00:25:37.840 --> 00:25:40.430 align:start position:0% list so for example you you have a list for<00:25:38.240> three<00:25:38.559> matching<00:25:39.080> bits<00:25:39.919> but<00:25:40.039> you<00:25:40.159> don't 00:25:40.430 --> 00:25:40.440 align:start position:0% for three matching bits but you don't 00:25:40.440 --> 00:25:42.909 align:start position:0% for three matching bits but you don't have<00:25:40.559> a<00:25:40.720> list<00:25:40.960> for<00:25:41.200> four<00:25:41.480> matching<00:25:41.919> bits<00:25:42.679> then 00:25:42.909 --> 00:25:42.919 align:start position:0% have a list for four matching bits then 00:25:42.919 --> 00:25:46.070 align:start position:0% have a list for four matching bits then what<00:25:43.039> you<00:25:43.240> do<00:25:43.799> is<00:25:43.960> you<00:25:44.279> split<00:25:44.679> this<00:25:44.919> list<00:25:45.320> into 00:25:46.070 --> 00:25:46.080 align:start position:0% what you do is you split this list into 00:25:46.080 --> 00:25:50.830 align:start position:0% what you do is you split this list into two<00:25:47.159> uh<00:25:48.159> and<00:25:48.360> you<00:25:48.600> start<00:25:48.960> a<00:25:49.159> new<00:25:49.399> list 00:25:50.830 --> 00:25:50.840 align:start position:0% two uh and you start a new list 00:25:50.840 --> 00:25:55.230 align:start position:0% two uh and you start a new list for<00:25:51.840> for<00:25:52.200> the<00:25:52.360> longer<00:25:53.120> prefix<00:25:54.120> uh<00:25:54.279> otherwise 00:25:55.230 --> 00:25:55.240 align:start position:0% for for the longer prefix uh otherwise 00:25:55.240 --> 00:25:58.830 align:start position:0% for for the longer prefix uh otherwise if<00:25:55.480> the<00:25:55.720> list<00:25:56.120> is<00:25:57.039> if<00:25:57.200> the<00:25:57.360> list<00:25:57.679> is<00:25:57.840> full<00:25:58.559> and 00:25:58.830 --> 00:25:58.840 align:start position:0% if the list is if the list is full and 00:25:58.840 --> 00:26:01.029 align:start position:0% if the list is if the list is full and it's<00:25:59.200> on<00:25:59.360> the<00:25:59.720> the<00:25:59.840> new<00:26:00.039> node<00:26:00.360> is<00:26:00.480> on<00:26:00.640> the<00:26:00.760> far 00:26:01.029 --> 00:26:01.039 align:start position:0% it's on the the new node is on the far 00:26:01.039 --> 00:26:03.310 align:start position:0% it's on the the new node is on the far end<00:26:01.799> then<00:26:02.080> what<00:26:02.200> you<00:26:02.360> do<00:26:02.600> is<00:26:02.720> you<00:26:02.919> simply 00:26:03.310 --> 00:26:03.320 align:start position:0% end then what you do is you simply 00:26:03.320 --> 00:26:06.789 align:start position:0% end then what you do is you simply forget<00:26:03.960> the<00:26:04.279> node<00:26:05.279> that<00:26:05.679> you<00:26:05.840> know<00:26:06.159> that<00:26:06.520> is 00:26:06.789 --> 00:26:06.799 align:start position:0% forget the node that you know that is 00:26:06.799 --> 00:26:10.389 align:start position:0% forget the node that you know that is the<00:26:07.000> worst<00:26:07.399> by<00:26:07.559> some<00:26:08.159> criteria<00:26:09.159> what<00:26:09.720> cadamia 00:26:10.389 --> 00:26:10.399 align:start position:0% the worst by some criteria what cadamia 00:26:10.399 --> 00:26:13.830 align:start position:0% the worst by some criteria what cadamia does<00:26:11.080> is<00:26:11.640> it<00:26:11.840> regularly<00:26:12.399> pings<00:26:12.799> the<00:26:12.960> nodes<00:26:13.559> and 00:26:13.830 --> 00:26:13.840 align:start position:0% does is it regularly pings the nodes and 00:26:13.840 --> 00:26:16.430 align:start position:0% does is it regularly pings the nodes and from<00:26:14.080> whichever<00:26:14.640> it<00:26:14.840> heard<00:26:15.240> last<00:26:16.039> it<00:26:16.159> will 00:26:16.430 --> 00:26:16.440 align:start position:0% from whichever it heard last it will 00:26:16.440 --> 00:26:19.190 align:start position:0% from whichever it heard last it will delete<00:26:17.440> we<00:26:17.559> might<00:26:17.799> do<00:26:18.039> something<00:26:18.480> similar<00:26:19.000> or 00:26:19.190 --> 00:26:19.200 align:start position:0% delete we might do something similar or 00:26:19.200 --> 00:26:20.669 align:start position:0% delete we might do something similar or we<00:26:19.320> might<00:26:19.600> have<00:26:19.799> some 00:26:20.669 --> 00:26:20.679 align:start position:0% we might have some 00:26:20.679 --> 00:26:23.470 align:start position:0% we might have some other<00:26:21.679> uh<00:26:21.880> criteria<00:26:22.520> by<00:26:22.679> which<00:26:22.880> to<00:26:23.039> rank<00:26:23.360> the 00:26:23.470 --> 00:26:23.480 align:start position:0% other uh criteria by which to rank the 00:26:23.480 --> 00:26:25.750 align:start position:0% other uh criteria by which to rank the notes<00:26:23.919> it<00:26:24.080> doesn't<00:26:24.720> really<00:26:25.000> matter<00:26:25.320> all<00:26:25.520> that 00:26:25.750 --> 00:26:25.760 align:start position:0% notes it doesn't really matter all that 00:26:25.760 --> 00:26:28.269 align:start position:0% notes it doesn't really matter all that much<00:26:26.120> but<00:26:26.279> it<00:26:26.559> it<00:26:26.760> provides<00:26:27.399> some<00:26:27.679> way<00:26:27.840> to 00:26:28.269 --> 00:26:28.279 align:start position:0% much but it it provides some way to 00:26:28.279 --> 00:26:30.590 align:start position:0% much but it it provides some way to control<00:26:28.640> the<00:26:28.799> quality<00:26:29.640> and<00:26:29.799> the<00:26:29.960> resilience 00:26:30.590 --> 00:26:30.600 align:start position:0% control the quality and the resilience 00:26:30.600 --> 00:26:33.750 align:start position:0% control the quality and the resilience of<00:26:30.840> the<00:26:31.159> of<00:26:31.279> the<00:26:31.880> network<00:26:32.880> so<00:26:33.080> how<00:26:33.200> do<00:26:33.320> you<00:26:33.480> join 00:26:33.750 --> 00:26:33.760 align:start position:0% of the of the network so how do you join 00:26:33.760 --> 00:26:37.070 align:start position:0% of the of the network so how do you join a<00:26:33.919> network<00:26:34.399> like<00:26:35.000> this<00:26:36.000> you<00:26:36.320> you<00:26:36.440> learn<00:26:36.799> about 00:26:37.070 --> 00:26:37.080 align:start position:0% a network like this you you learn about 00:26:37.080 --> 00:26:40.669 align:start position:0% a network like this you you learn about one<00:26:37.320> bootstrap<00:26:37.960> node<00:26:38.480> you<00:26:38.640> connect<00:26:39.039> to<00:26:39.440> it<00:26:40.440> you 00:26:40.669 --> 00:26:40.679 align:start position:0% one bootstrap node you connect to it you 00:26:40.679 --> 00:26:42.710 align:start position:0% one bootstrap node you connect to it you register<00:26:41.320> with<00:26:41.480> the<00:26:41.600> bootstrap<00:26:42.200> node<00:26:42.520> so 00:26:42.710 --> 00:26:42.720 align:start position:0% register with the bootstrap node so 00:26:42.720 --> 00:26:45.190 align:start position:0% register with the bootstrap node so basically<00:26:43.159> the<00:26:43.279> bootstrap<00:26:43.880> node<00:26:44.399> adds<00:26:44.760> you<00:26:45.000> to 00:26:45.190 --> 00:26:45.200 align:start position:0% basically the bootstrap node adds you to 00:26:45.200 --> 00:26:47.149 align:start position:0% basically the bootstrap node adds you to the<00:26:45.399> list<00:26:45.960> where<00:26:46.120> you 00:26:47.149 --> 00:26:47.159 align:start position:0% the list where you 00:26:47.159 --> 00:26:50.350 align:start position:0% the list where you belong<00:26:48.159> then<00:26:48.640> you<00:26:48.840> do<00:26:49.159> a<00:26:49.360> self<00:26:49.799> lookup<00:26:50.240> with 00:26:50.350 --> 00:26:50.360 align:start position:0% belong then you do a self lookup with 00:26:50.360 --> 00:26:52.310 align:start position:0% belong then you do a self lookup with the<00:26:50.520> bootstrap<00:26:51.039> note<00:26:51.279> you<00:26:51.399> try<00:26:51.640> to<00:26:51.799> look<00:26:51.960> up 00:26:52.310 --> 00:26:52.320 align:start position:0% the bootstrap note you try to look up 00:26:52.320 --> 00:26:55.870 align:start position:0% the bootstrap note you try to look up yourself<00:26:53.320> so<00:26:53.520> you<00:26:53.799> download<00:26:54.799> that<00:26:55.120> particular 00:26:55.870 --> 00:26:55.880 align:start position:0% yourself so you download that particular 00:26:55.880 --> 00:27:00.190 align:start position:0% yourself so you download that particular list<00:26:56.880> in<00:26:57.200> which<00:26:57.520> you<00:26:57.880> have<00:26:58.440> been 00:27:00.190 --> 00:27:00.200 align:start position:0% list in which you have been 00:27:00.200 --> 00:27:02.830 align:start position:0% list in which you have been uh<00:27:01.200> to<00:27:01.399> which<00:27:01.559> you<00:27:01.720> have<00:27:01.880> been<00:27:02.120> placed<00:27:02.640> you 00:27:02.830 --> 00:27:02.840 align:start position:0% uh to which you have been placed you 00:27:02.840 --> 00:27:06.430 align:start position:0% uh to which you have been placed you download<00:27:03.279> the<00:27:03.440> entire<00:27:04.240> list<00:27:05.240> uh<00:27:05.799> and<00:27:06.000> then<00:27:06.240> you 00:27:06.430 --> 00:27:06.440 align:start position:0% download the entire list uh and then you 00:27:06.440 --> 00:27:10.070 align:start position:0% download the entire list uh and then you insert<00:27:07.320> those<00:27:08.320> you<00:27:08.559> insert<00:27:09.120> those<00:27:09.360> nodes<00:27:09.840> one 00:27:10.070 --> 00:27:10.080 align:start position:0% insert those you insert those nodes one 00:27:10.080 --> 00:27:13.029 align:start position:0% insert those you insert those nodes one by<00:27:10.279> one<00:27:10.640> into<00:27:10.919> your<00:27:11.200> routing<00:27:11.720> table<00:27:12.240> and<00:27:12.919> you 00:27:13.029 --> 00:27:13.039 align:start position:0% by one into your routing table and you 00:27:13.039 --> 00:27:15.110 align:start position:0% by one into your routing table and you know<00:27:13.600> handle<00:27:13.960> it<00:27:14.279> the<00:27:14.399> way<00:27:14.559> they<00:27:14.679> should<00:27:14.919> be 00:27:15.110 --> 00:27:15.120 align:start position:0% know handle it the way they should be 00:27:15.120 --> 00:27:18.510 align:start position:0% know handle it the way they should be handled<00:27:16.120> and<00:27:16.360> then<00:27:16.919> you<00:27:17.200> generate<00:27:17.799> a<00:27:18.039> random 00:27:18.510 --> 00:27:18.520 align:start position:0% handled and then you generate a random 00:27:18.520 --> 00:27:21.029 align:start position:0% handled and then you generate a random address<00:27:19.039> in<00:27:19.200> the<00:27:19.399> range<00:27:20.120> which<00:27:20.240> is<00:27:20.440> one<00:27:20.720> bit 00:27:21.029 --> 00:27:21.039 align:start position:0% address in the range which is one bit 00:27:21.039 --> 00:27:23.230 align:start position:0% address in the range which is one bit further<00:27:21.480> than<00:27:21.720> the<00:27:21.960> bootstrap 00:27:23.230 --> 00:27:23.240 align:start position:0% further than the bootstrap 00:27:23.240 --> 00:27:25.870 align:start position:0% further than the bootstrap node<00:27:24.240> and<00:27:24.480> you<00:27:24.600> make<00:27:24.799> a<00:27:24.960> lookout<00:27:25.360> for<00:27:25.640> that 00:27:25.870 --> 00:27:25.880 align:start position:0% node and you make a lookout for that 00:27:25.880 --> 00:27:27.710 align:start position:0% node and you make a lookout for that address<00:27:26.399> and<00:27:26.600> that<00:27:26.799> also<00:27:27.120> gives<00:27:27.320> you<00:27:27.520> some 00:27:27.710 --> 00:27:27.720 align:start position:0% address and that also gives you some 00:27:27.720 --> 00:27:28.830 align:start position:0% address and that also gives you some nodes 00:27:28.830 --> 00:27:28.840 align:start position:0% nodes 00:27:28.840 --> 00:27:30.909 align:start position:0% nodes and<00:27:29.120> this<00:27:29.320> way<00:27:29.720> you<00:27:29.960> you<00:27:30.159> you<00:27:30.320> you<00:27:30.440> have<00:27:30.600> joined 00:27:30.909 --> 00:27:30.919 align:start position:0% and this way you you you you have joined 00:27:30.919 --> 00:27:32.750 align:start position:0% and this way you you you you have joined the<00:27:31.080> network<00:27:31.480> and<00:27:31.640> you<00:27:31.720> have<00:27:31.960> established 00:27:32.750 --> 00:27:32.760 align:start position:0% the network and you have established 00:27:32.760 --> 00:27:36.549 align:start position:0% the network and you have established yourself<00:27:33.320> as<00:27:33.480> a<00:27:34.320> equally<00:27:34.760> Central<00:27:35.320> node<00:27:36.320> as 00:27:36.549 --> 00:27:36.559 align:start position:0% yourself as a equally Central node as 00:27:36.559 --> 00:27:39.070 align:start position:0% yourself as a equally Central node as everybody<00:27:37.039> else<00:27:37.320> so<00:27:37.520> the<00:27:37.679> point<00:27:37.960> of<00:27:38.240> this<00:27:38.760> uh 00:27:39.070 --> 00:27:39.080 align:start position:0% everybody else so the point of this uh 00:27:39.080 --> 00:27:41.470 align:start position:0% everybody else so the point of this uh exercise<00:27:40.080> is<00:27:40.279> that<00:27:40.440> when<00:27:40.640> you<00:27:40.799> join<00:27:41.240> this 00:27:41.470 --> 00:27:41.480 align:start position:0% exercise is that when you join this 00:27:41.480 --> 00:27:43.909 align:start position:0% exercise is that when you join this network<00:27:42.480> it's<00:27:42.640> not<00:27:42.919> that<00:27:43.039> you're<00:27:43.279> going<00:27:43.559> to<00:27:43.720> be 00:27:43.909 --> 00:27:43.919 align:start position:0% network it's not that you're going to be 00:27:43.919 --> 00:27:45.750 align:start position:0% network it's not that you're going to be somewhere<00:27:44.519> on<00:27:44.679> the<00:27:44.799> outskirts<00:27:45.440> of<00:27:45.600> the 00:27:45.750 --> 00:27:45.760 align:start position:0% somewhere on the outskirts of the 00:27:45.760 --> 00:27:48.549 align:start position:0% somewhere on the outskirts of the network<00:27:46.440> but<00:27:46.600> you<00:27:46.720> will<00:27:47.000> establish<00:27:47.600> yourself 00:27:48.549 --> 00:27:48.559 align:start position:0% network but you will establish yourself 00:27:48.559 --> 00:27:50.830 align:start position:0% network but you will establish yourself with<00:27:48.760> deep<00:27:49.080> enough<00:27:49.440> connections<00:27:50.440> so<00:27:50.679> that 00:27:50.830 --> 00:27:50.840 align:start position:0% with deep enough connections so that 00:27:50.840 --> 00:27:53.350 align:start position:0% with deep enough connections so that you're<00:27:51.120> just<00:27:51.360> as<00:27:51.519> Central<00:27:52.000> as<00:27:52.240> any<00:27:52.480> other<00:27:52.679> node 00:27:53.350 --> 00:27:53.360 align:start position:0% you're just as Central as any other node 00:27:53.360 --> 00:27:55.750 align:start position:0% you're just as Central as any other node so<00:27:53.600> it<00:27:53.760> it<00:27:54.039> it<00:27:54.240> provides<00:27:54.640> a 00:27:55.750 --> 00:27:55.760 align:start position:0% so it it it provides a 00:27:55.760 --> 00:27:58.830 align:start position:0% so it it it provides a uniformity<00:27:56.760> uh<00:27:57.640> and<00:27:57.799> there's<00:27:58.200> some<00:27:58.320> big<00:27:58.480> open 00:27:58.830 --> 00:27:58.840 align:start position:0% uniformity uh and there's some big open 00:27:58.840 --> 00:28:01.509 align:start position:0% uniformity uh and there's some big open questions<00:27:59.279> about<00:27:59.559> what<00:27:59.720> we<00:27:59.919> do<00:28:00.919> so<00:28:01.200> first 00:28:01.509 --> 00:28:01.519 align:start position:0% questions about what we do so first 00:28:01.519 --> 00:28:03.789 align:start position:0% questions about what we do so first there's<00:28:01.840> this<00:28:02.080> thing<00:28:02.440> that<00:28:03.000> are<00:28:03.120> we<00:28:03.320> going<00:28:03.600> to 00:28:03.789 --> 00:28:03.799 align:start position:0% there's this thing that are we going to 00:28:03.799 --> 00:28:06.950 align:start position:0% there's this thing that are we going to do<00:28:04.080> this<00:28:04.240> over<00:28:04.559> UDP<00:28:05.039> or<00:28:05.240> TCP<00:28:06.080> now<00:28:06.320> since<00:28:06.679> all 00:28:06.950 --> 00:28:06.960 align:start position:0% do this over UDP or TCP now since all 00:28:06.960 --> 00:28:09.149 align:start position:0% do this over UDP or TCP now since all the<00:28:07.200> packets<00:28:07.720> that<00:28:07.880> we<00:28:08.000> are<00:28:08.159> sending<00:28:08.720> around 00:28:09.149 --> 00:28:09.159 align:start position:0% the packets that we are sending around 00:28:09.159 --> 00:28:12.830 align:start position:0% the packets that we are sending around they're<00:28:09.559> short<00:28:10.559> and<00:28:10.840> since<00:28:11.240> UDP<00:28:12.240> is<00:28:12.519> much 00:28:12.830 --> 00:28:12.840 align:start position:0% they're short and since UDP is much 00:28:12.840 --> 00:28:17.070 align:start position:0% they're short and since UDP is much easier<00:28:13.679> to<00:28:14.679> to<00:28:15.080> sand<00:28:15.519> around<00:28:16.200> uh<00:28:16.320> sand<00:28:16.760> through 00:28:17.070 --> 00:28:17.080 align:start position:0% easier to to sand around uh sand through 00:28:17.080 --> 00:28:20.029 align:start position:0% easier to to sand around uh sand through firewalls<00:28:17.919> and<00:28:18.200> nuts<00:28:18.679> and<00:28:18.919> things<00:28:19.200> like<00:28:19.480> that 00:28:20.029 --> 00:28:20.039 align:start position:0% firewalls and nuts and things like that 00:28:20.039 --> 00:28:23.110 align:start position:0% firewalls and nuts and things like that I'm<00:28:20.320> actually<00:28:20.640> leaning<00:28:21.159> towards<00:28:21.840> UDP<00:28:22.840> and 00:28:23.110 --> 00:28:23.120 align:start position:0% I'm actually leaning towards UDP and 00:28:23.120 --> 00:28:26.070 align:start position:0% I'm actually leaning towards UDP and that<00:28:23.320> means<00:28:23.960> that<00:28:24.399> maybe<00:28:25.279> this<00:28:25.519> thing<00:28:25.799> should 00:28:26.070 --> 00:28:26.080 align:start position:0% that means that maybe this thing should 00:28:26.080 --> 00:28:28.750 align:start position:0% that means that maybe this thing should have<00:28:26.279> a<00:28:26.559> separate<00:28:27.279> uh 00:28:28.750 --> 00:28:28.760 align:start position:0% have a separate uh 00:28:28.760 --> 00:28:33.190 align:start position:0% have a separate uh separate<00:28:29.279> layer<00:28:30.240> uh<00:28:31.240> with<00:28:31.760> uh<00:28:32.679> a<00:28:32.840> separate 00:28:33.190 --> 00:28:33.200 align:start position:0% separate layer uh with uh a separate 00:28:33.200 --> 00:28:36.190 align:start position:0% separate layer uh with uh a separate Network<00:28:33.640> layer<00:28:33.960> from<00:28:34.159> the<00:28:34.320> peer-to-peer<00:28:35.200> uh 00:28:36.190 --> 00:28:36.200 align:start position:0% Network layer from the peer-to-peer uh 00:28:36.200 --> 00:28:38.590 align:start position:0% Network layer from the peer-to-peer uh protocol<00:28:36.760> that<00:28:36.960> has<00:28:37.120> been<00:28:37.720> uh<00:28:37.880> presented<00:28:38.360> two 00:28:38.590 --> 00:28:38.600 align:start position:0% protocol that has been uh presented two 00:28:38.600 --> 00:28:41.509 align:start position:0% protocol that has been uh presented two talks<00:28:39.279> ago<00:28:40.279> then<00:28:40.480> there's<00:28:40.799> this<00:28:41.039> second 00:28:41.509 --> 00:28:41.519 align:start position:0% talks ago then there's this second 00:28:41.519 --> 00:28:44.630 align:start position:0% talks ago then there's this second question<00:28:42.519> these<00:28:42.720> two<00:28:42.919> are<00:28:43.080> somewhat<00:28:43.640> related 00:28:44.630 --> 00:28:44.640 align:start position:0% question these two are somewhat related 00:28:44.640 --> 00:28:47.950 align:start position:0% question these two are somewhat related so<00:28:45.039> not<00:28:45.799> tunneling<00:28:46.799> when<00:28:47.000> you're<00:28:47.320> tunneling 00:28:47.950 --> 00:28:47.960 align:start position:0% so not tunneling when you're tunneling 00:28:47.960 --> 00:28:51.630 align:start position:0% so not tunneling when you're tunneling through<00:28:48.679> n<00:28:49.679> it<00:28:49.960> you<00:28:50.120> you<00:28:50.320> either<00:28:50.640> do<00:28:50.880> it<00:28:51.200> by 00:28:51.630 --> 00:28:51.640 align:start position:0% through n it you you either do it by 00:28:51.640 --> 00:28:53.870 align:start position:0% through n it you you either do it by routing<00:28:52.200> your<00:28:52.480> traffic<00:28:52.960> through<00:28:53.279> some<00:28:53.559> third 00:28:53.870 --> 00:28:53.880 align:start position:0% routing your traffic through some third 00:28:53.880 --> 00:28:57.630 align:start position:0% routing your traffic through some third node<00:28:54.399> which<00:28:54.559> is<00:28:54.880> really<00:28:55.159> bad<00:28:56.080> or<00:28:57.080> you<00:28:57.360> you<00:28:57.480> you 00:28:57.630 --> 00:28:57.640 align:start position:0% node which is really bad or you you you 00:28:57.640 --> 00:29:00.350 align:start position:0% node which is really bad or you you you really<00:28:58.159> try<00:28:58.440> to<00:28:58.640> burrow<00:28:59.200> a<00:28:59.399> hole<00:28:59.840> through<00:29:00.120> the 00:29:00.350 --> 00:29:00.360 align:start position:0% really try to burrow a hole through the 00:29:00.360 --> 00:29:03.870 align:start position:0% really try to burrow a hole through the nut<00:29:00.799> nut<00:29:01.200> firewall<00:29:02.000> you<00:29:02.200> do<00:29:02.519> that<00:29:02.919> by<00:29:03.159> spraying 00:29:03.870 --> 00:29:03.880 align:start position:0% nut nut firewall you do that by spraying 00:29:03.880 --> 00:29:06.990 align:start position:0% nut nut firewall you do that by spraying each<00:29:04.080> other<00:29:04.559> with<00:29:04.799> udps<00:29:05.559> with<00:29:05.880> random<00:29:06.880> uh 00:29:06.990 --> 00:29:07.000 align:start position:0% each other with udps with random uh 00:29:07.000 --> 00:29:10.310 align:start position:0% each other with udps with random uh source<00:29:07.360> and<00:29:07.640> destination<00:29:08.320> ports<00:29:09.200> and<00:29:09.480> rely<00:29:10.000> on 00:29:10.310 --> 00:29:10.320 align:start position:0% source and destination ports and rely on 00:29:10.320 --> 00:29:12.149 align:start position:0% source and destination ports and rely on the<00:29:10.880> uh<00:29:11.039> birthday 00:29:12.149 --> 00:29:12.159 align:start position:0% the uh birthday 00:29:12.159 --> 00:29:16.269 align:start position:0% the uh birthday Paradox<00:29:13.159> uh<00:29:13.320> on<00:29:14.159> one<00:29:14.360> of<00:29:14.519> the<00:29:14.799> requests<00:29:15.679> being 00:29:16.269 --> 00:29:16.279 align:start position:0% Paradox uh on one of the requests being 00:29:16.279 --> 00:29:19.029 align:start position:0% Paradox uh on one of the requests being an<00:29:16.519> answer<00:29:17.039> to<00:29:17.360> to<00:29:17.519> another<00:29:17.960> request<00:29:18.480> and<00:29:18.760> from 00:29:19.029 --> 00:29:19.039 align:start position:0% an answer to to another request and from 00:29:19.039 --> 00:29:21.669 align:start position:0% an answer to to another request and from that<00:29:19.240> point<00:29:19.519> on<00:29:19.760> the<00:29:19.919> routers<00:29:20.480> will<00:29:21.159> pass 00:29:21.669 --> 00:29:21.679 align:start position:0% that point on the routers will pass 00:29:21.679 --> 00:29:25.630 align:start position:0% that point on the routers will pass those<00:29:22.200> two<00:29:23.200> uh<00:29:23.919> that<00:29:24.279> specific<00:29:24.799> Source<00:29:25.240> port 00:29:25.630 --> 00:29:25.640 align:start position:0% those two uh that specific Source port 00:29:25.640 --> 00:29:28.149 align:start position:0% those two uh that specific Source port and<00:29:25.840> that<00:29:26.080> specific<00:29:26.799> uh<00:29:26.960> destination<00:29:27.600> port 00:29:28.149 --> 00:29:28.159 align:start position:0% and that specific uh destination port 00:29:28.159 --> 00:29:29.750 align:start position:0% and that specific uh destination port right<00:29:28.360> through<00:29:28.559> the<00:29:28.720> N 00:29:29.750 --> 00:29:29.760 align:start position:0% right through the N 00:29:29.760 --> 00:29:33.710 align:start position:0% right through the N firewall<00:29:30.760> but<00:29:31.200> the<00:29:31.440> problem<00:29:31.880> is<00:29:32.279> that<00:29:32.480> in<00:29:32.760> this 00:29:33.710 --> 00:29:33.720 align:start position:0% firewall but the problem is that in this 00:29:33.720 --> 00:29:36.509 align:start position:0% firewall but the problem is that in this case<00:29:34.720> uh<00:29:35.159> the<00:29:35.399> establishment<00:29:36.200> of<00:29:36.320> a 00:29:36.509 --> 00:29:36.519 align:start position:0% case uh the establishment of a 00:29:36.519 --> 00:29:39.350 align:start position:0% case uh the establishment of a connection<00:29:37.000> is<00:29:37.159> slow<00:29:38.039> so<00:29:38.279> it's<00:29:38.519> really<00:29:39.080> not 00:29:39.350 --> 00:29:39.360 align:start position:0% connection is slow so it's really not 00:29:39.360 --> 00:29:41.870 align:start position:0% connection is slow so it's really not something<00:29:39.799> that<00:29:39.919> you<00:29:40.039> want<00:29:40.240> to<00:29:40.480> change<00:29:41.360> so<00:29:41.640> in 00:29:41.870 --> 00:29:41.880 align:start position:0% something that you want to change so in 00:29:41.880 --> 00:29:45.110 align:start position:0% something that you want to change so in this<00:29:42.159> case<00:29:42.720> instead<00:29:43.519> so<00:29:43.840> the<00:29:44.320> what<00:29:44.519> cademia 00:29:45.110 --> 00:29:45.120 align:start position:0% this case instead so the what cademia 00:29:45.120 --> 00:29:48.149 align:start position:0% this case instead so the what cademia does<00:29:45.960> and<00:29:46.200> what<00:29:46.360> the<00:29:46.559> Boran<00:29:47.399> implementation 00:29:48.149 --> 00:29:48.159 align:start position:0% does and what the Boran implementation 00:29:48.159 --> 00:29:51.470 align:start position:0% does and what the Boran implementation of<00:29:48.320> it<00:29:48.559> does<00:29:49.320> is<00:29:49.559> that<00:29:49.799> it<00:29:49.960> never<00:29:50.399> routes<00:29:51.080> data 00:29:51.470 --> 00:29:51.480 align:start position:0% of it does is that it never routes data 00:29:51.480 --> 00:29:53.950 align:start position:0% of it does is that it never routes data through<00:29:51.880> nodes<00:29:52.880> it<00:29:53.080> always<00:29:53.440> gives<00:29:53.640> you<00:29:53.799> an 00:29:53.950 --> 00:29:53.960 align:start position:0% through nodes it always gives you an 00:29:53.960 --> 00:29:55.830 align:start position:0% through nodes it always gives you an address<00:29:54.320> but<00:29:54.559> if<00:29:54.640> you're<00:29:54.919> interested<00:29:55.399> in<00:29:55.600> this 00:29:55.830 --> 00:29:55.840 align:start position:0% address but if you're interested in this 00:29:55.840 --> 00:29:58.549 align:start position:0% address but if you're interested in this particular<00:29:56.679> piece<00:29:57.240> here's<00:29:57.480> an<00:29:57.640> address<00:29:58.200> go<00:29:58.360> go 00:29:58.549 --> 00:29:58.559 align:start position:0% particular piece here's an address go go 00:29:58.559 --> 00:30:01.750 align:start position:0% particular piece here's an address go go ask<00:29:58.840> that<00:29:59.240> guide<00:30:00.240> but<00:30:00.559> if<00:30:00.919> if<00:30:01.120> if<00:30:01.240> we're<00:30:01.480> doing 00:30:01.750 --> 00:30:01.760 align:start position:0% ask that guide but if if if we're doing 00:30:01.760 --> 00:30:04.669 align:start position:0% ask that guide but if if if we're doing net<00:30:02.360> tunneling<00:30:03.360> then<00:30:03.640> this<00:30:03.799> is<00:30:03.919> an<00:30:04.159> expensive 00:30:04.669 --> 00:30:04.679 align:start position:0% net tunneling then this is an expensive 00:30:04.679 --> 00:30:07.549 align:start position:0% net tunneling then this is an expensive and<00:30:04.880> slow<00:30:05.279> step<00:30:06.039> so<00:30:06.200> we<00:30:06.320> might<00:30:06.559> not<00:30:06.720> want<00:30:06.919> to<00:30:07.120> do 00:30:07.549 --> 00:30:07.559 align:start position:0% and slow step so we might not want to do 00:30:07.559 --> 00:30:10.230 align:start position:0% and slow step so we might not want to do that<00:30:08.559> maybe<00:30:08.919> we<00:30:09.080> want<00:30:09.279> to<00:30:09.480> pass<00:30:09.760> around 00:30:10.230 --> 00:30:10.240 align:start position:0% that maybe we want to pass around 00:30:10.240 --> 00:30:12.710 align:start position:0% that maybe we want to pass around information<00:30:10.880> and<00:30:11.120> maybe<00:30:11.480> we<00:30:11.640> even<00:30:12.120> need<00:30:12.360> to<00:30:12.519> be 00:30:12.710 --> 00:30:12.720 align:start position:0% information and maybe we even need to be 00:30:12.720 --> 00:30:14.669 align:start position:0% information and maybe we even need to be somewhat<00:30:13.159> adaptable<00:30:13.760> like<00:30:14.000> distinguish 00:30:14.669 --> 00:30:14.679 align:start position:0% somewhat adaptable like distinguish 00:30:14.679 --> 00:30:16.950 align:start position:0% somewhat adaptable like distinguish between<00:30:15.080> nodes<00:30:15.480> behind<00:30:15.840> not<00:30:16.159> firewalls<00:30:16.760> and 00:30:16.950 --> 00:30:16.960 align:start position:0% between nodes behind not firewalls and 00:30:16.960 --> 00:30:20.509 align:start position:0% between nodes behind not firewalls and other<00:30:17.200> nodes<00:30:17.640> which<00:30:17.880> have<00:30:18.320> a<00:30:18.960> public<00:30:19.360> IP 00:30:20.509 --> 00:30:20.519 align:start position:0% other nodes which have a public IP 00:30:20.519 --> 00:30:22.870 align:start position:0% other nodes which have a public IP address<00:30:21.519> another<00:30:22.000> good<00:30:22.240> question<00:30:22.559> is<00:30:22.760> what 00:30:22.870 --> 00:30:22.880 align:start position:0% address another good question is what 00:30:22.880 --> 00:30:25.389 align:start position:0% address another good question is what are<00:30:23.000> we<00:30:23.159> going<00:30:23.279> to<00:30:23.440> do<00:30:23.600> with<00:30:24.000> Spam<00:30:25.000> because<00:30:25.279> if 00:30:25.389 --> 00:30:25.399 align:start position:0% are we going to do with Spam because if 00:30:25.399 --> 00:30:27.669 align:start position:0% are we going to do with Spam because if we<00:30:25.600> implement<00:30:26.120> this<00:30:26.320> directly<00:30:26.960> then<00:30:27.200> anybody 00:30:27.669 --> 00:30:27.679 align:start position:0% we implement this directly then anybody 00:30:27.679 --> 00:30:29.070 align:start position:0% we implement this directly then anybody can 00:30:29.070 --> 00:30:29.080 align:start position:0% can 00:30:29.080 --> 00:30:30.269 align:start position:0% can uh<00:30:29.399> you 00:30:30.269 --> 00:30:30.279 align:start position:0% uh you 00:30:30.279 --> 00:30:33.389 align:start position:0% uh you know<00:30:31.279> force<00:30:31.760> it<00:30:31.960> to<00:30:32.159> store 00:30:33.389 --> 00:30:33.399 align:start position:0% know force it to store 00:30:33.399 --> 00:30:38.630 align:start position:0% know force it to store forever<00:30:34.760> uh<00:30:35.760> information<00:30:36.760> to<00:30:37.039> which<00:30:37.399> there's 00:30:38.630 --> 00:30:38.640 align:start position:0% forever uh information to which there's 00:30:38.640 --> 00:30:41.710 align:start position:0% forever uh information to which there's uh<00:30:39.640> to<00:30:39.840> which<00:30:40.000> it<00:30:40.159> knows<00:30:40.480> the<00:30:40.679> hash<00:30:41.519> but 00:30:41.710 --> 00:30:41.720 align:start position:0% uh to which it knows the hash but 00:30:41.720 --> 00:30:43.630 align:start position:0% uh to which it knows the hash but whether<00:30:42.039> this<00:30:42.279> information<00:30:42.840> is<00:30:43.000> useful<00:30:43.480> or 00:30:43.630 --> 00:30:43.640 align:start position:0% whether this information is useful or 00:30:43.640 --> 00:30:47.110 align:start position:0% whether this information is useful or not<00:30:43.960> is<00:30:44.159> anybody's<00:30:45.039> guess<00:30:46.039> and<00:30:46.399> this<00:30:46.640> also 00:30:47.110 --> 00:30:47.120 align:start position:0% not is anybody's guess and this also 00:30:47.120 --> 00:30:50.029 align:start position:0% not is anybody's guess and this also gives<00:30:47.440> us<00:30:48.159> uh<00:30:48.600> this<00:30:48.799> also<00:30:49.080> leads<00:30:49.440> us<00:30:49.640> to<00:30:49.840> the 00:30:50.029 --> 00:30:50.039 align:start position:0% gives us uh this also leads us to the 00:30:50.039 --> 00:30:53.549 align:start position:0% gives us uh this also leads us to the question<00:30:50.399> of<00:30:50.640> incentives<00:30:51.600> which<00:30:52.360> uh<00:30:53.360> which 00:30:53.549 --> 00:30:53.559 align:start position:0% question of incentives which uh which 00:30:53.559 --> 00:30:55.149 align:start position:0% question of incentives which uh which really<00:30:53.840> depends<00:30:54.200> on<00:30:54.399> what<00:30:54.600> this<00:30:54.760> thing<00:30:55.000> is 00:30:55.149 --> 00:30:55.159 align:start position:0% really depends on what this thing is 00:30:55.159 --> 00:30:56.470 align:start position:0% really depends on what this thing is going<00:30:55.320> to<00:30:55.480> be<00:30:55.600> used 00:30:56.470 --> 00:30:56.480 align:start position:0% going to be used 00:30:56.480 --> 00:30:59.269 align:start position:0% going to be used for<00:30:57.480> uh<00:30:57.720> and<00:30:58.159> you<00:30:58.279> know<00:30:58.480> there<00:30:58.559> are<00:30:58.760> many<00:30:59.039> other 00:30:59.269 --> 00:30:59.279 align:start position:0% for uh and you know there are many other 00:30:59.279 --> 00:31:01.070 align:start position:0% for uh and you know there are many other open<00:30:59.600> questions<00:30:59.960> so<00:31:00.120> I<00:31:00.240> think<00:31:00.480> that<00:31:00.679> at<00:31:00.880> this 00:31:01.070 --> 00:31:01.080 align:start position:0% open questions so I think that at this 00:31:01.080 --> 00:31:05.149 align:start position:0% open questions so I think that at this point<00:31:01.399> we<00:31:01.600> start<00:31:01.919> the<00:31:02.080> Q&A<00:31:02.600> session<00:31:03.360> and<00:31:04.159> uh 00:31:05.149 --> 00:31:05.159 align:start position:0% point we start the Q&A session and uh 00:31:05.159 --> 00:31:09.909 align:start position:0% point we start the Q&A session and uh and<00:31:05.480> maybe<00:31:06.360> uh<00:31:06.919> on<00:31:07.200> Friday<00:31:07.840> we<00:31:08.000> should<00:31:08.639> have<00:31:08.919> a 00:31:09.909 --> 00:31:09.919 align:start position:0% and maybe uh on Friday we should have a 00:31:09.919 --> 00:31:13.269 align:start position:0% and maybe uh on Friday we should have a a<00:31:10.159> discussion<00:31:10.720> about<00:31:11.120> what<00:31:11.279> to<00:31:11.399> do<00:31:11.760> okay<00:31:12.679> yeah 00:31:13.269 --> 00:31:13.279 align:start position:0% a discussion about what to do okay yeah 00:31:13.279 --> 00:31:17.750 align:start position:0% a discussion about what to do okay yeah so<00:31:14.279> a<00:31:14.440> little<00:31:14.760> bit<00:31:15.159> to<00:31:15.760> to<00:31:16.080> elaborate<00:31:16.799> about 00:31:17.750 --> 00:31:17.760 align:start position:0% so a little bit to to elaborate about 00:31:17.760 --> 00:31:20.070 align:start position:0% so a little bit to to elaborate about how<00:31:17.960> I<00:31:18.120> join<00:31:18.440> to<00:31:18.639> network<00:31:19.000> and<00:31:19.279> what<00:31:19.840> what 00:31:20.070 --> 00:31:20.080 align:start position:0% how I join to network and what what 00:31:20.080 --> 00:31:22.750 align:start position:0% how I join to network and what what information<00:31:20.720> they<00:31:20.919> feel<00:31:21.279> that<00:31:21.399> I<00:31:21.600> join<00:31:22.120> to 00:31:22.750 --> 00:31:22.760 align:start position:0% information they feel that I join to 00:31:22.760 --> 00:31:25.549 align:start position:0% information they feel that I join to should<00:31:23.159> provide<00:31:23.600> me<00:31:24.279> like<00:31:24.679> maybe<00:31:24.960> the<00:31:25.159> level 00:31:25.549 --> 00:31:25.559 align:start position:0% should provide me like maybe the level 00:31:25.559 --> 00:31:29.629 align:start position:0% should provide me like maybe the level of<00:31:26.360> the<00:31:27.360> of<00:31:27.440> the<00:31:28.159> it<00:31:28.440> it<00:31:28.720> has<00:31:29.080> like<00:31:29.200> is<00:31:29.320> it<00:31:29.440> the 00:31:29.629 --> 00:31:29.639 align:start position:0% of the of the it it has like is it the 00:31:29.639 --> 00:31:34.029 align:start position:0% of the of the it it has like is it the general<00:31:30.080> or<00:31:30.960> so<00:31:31.960> no<00:31:32.120> no<00:31:32.279> no<00:31:32.960> in<00:31:33.159> this<00:31:33.440> case<00:31:33.880> when 00:31:34.029 --> 00:31:34.039 align:start position:0% general or so no no no in this case when 00:31:34.039 --> 00:31:36.950 align:start position:0% general or so no no no in this case when you're<00:31:34.360> in<00:31:34.639> cadamia<00:31:35.320> there<00:31:35.519> there's<00:31:35.720> no<00:31:36.039> rank 00:31:36.950 --> 00:31:36.960 align:start position:0% you're in cadamia there there's no rank 00:31:36.960 --> 00:31:40.389 align:start position:0% you're in cadamia there there's no rank everybody's<00:31:37.960> equal<00:31:38.720> so<00:31:38.960> what<00:31:39.120> you<00:31:39.279> do<00:31:39.679> is<00:31:39.960> you 00:31:40.389 --> 00:31:40.399 align:start position:0% everybody's equal so what you do is you 00:31:40.399 --> 00:31:42.310 align:start position:0% everybody's equal so what you do is you you<00:31:40.600> connect<00:31:40.960> to<00:31:41.120> one<00:31:41.320> node<00:31:41.720> that<00:31:41.880> is<00:31:42.159> is 00:31:42.310 --> 00:31:42.320 align:start position:0% you connect to one node that is is 00:31:42.320 --> 00:31:44.190 align:start position:0% you connect to one node that is is already<00:31:42.600> a<00:31:42.760> member<00:31:43.200> that's<00:31:43.679> that's<00:31:43.880> how<00:31:44.080> you 00:31:44.190 --> 00:31:44.200 align:start position:0% already a member that's that's how you 00:31:44.200 --> 00:31:44.870 align:start position:0% already a member that's that's how you you 00:31:44.870 --> 00:31:44.880 align:start position:0% you 00:31:44.880 --> 00:31:47.590 align:start position:0% you bootstrap<00:31:45.880> then<00:31:46.200> you<00:31:46.480> register<00:31:47.120> with<00:31:47.399> that 00:31:47.590 --> 00:31:47.600 align:start position:0% bootstrap then you register with that 00:31:47.600 --> 00:31:49.950 align:start position:0% bootstrap then you register with that node<00:31:48.039> so<00:31:48.200> you<00:31:48.399> give<00:31:48.639> your<00:31:48.960> address<00:31:49.480> to<00:31:49.760> that 00:31:49.950 --> 00:31:49.960 align:start position:0% node so you give your address to that 00:31:49.960 --> 00:31:52.629 align:start position:0% node so you give your address to that node<00:31:50.600> and<00:31:50.840> that<00:31:51.039> node<00:31:51.440> puts<00:31:51.720> it<00:31:52.039> into<00:31:52.399> the 00:31:52.629 --> 00:31:52.639 align:start position:0% node and that node puts it into the 00:31:52.639 --> 00:31:55.110 align:start position:0% node and that node puts it into the appropriate<00:31:53.240> list<00:31:53.720> where<00:31:53.919> where<00:31:54.039> it 00:31:55.110 --> 00:31:55.120 align:start position:0% appropriate list where where it 00:31:55.120 --> 00:31:58.190 align:start position:0% appropriate list where where it belongs<00:31:56.120> then<00:31:56.679> it<00:31:56.919> gives<00:31:57.200> you<00:31:57.519> back<00:31:58.080> the 00:31:58.190 --> 00:31:58.200 align:start position:0% belongs then it gives you back the 00:31:58.200 --> 00:32:01.350 align:start position:0% belongs then it gives you back the entire<00:31:58.639> list<00:31:59.519> so<00:31:59.720> it<00:31:59.880> will<00:32:00.360> you<00:32:00.480> will<00:32:00.799> have<00:32:01.159> a 00:32:01.350 --> 00:32:01.360 align:start position:0% entire list so it will you will have a 00:32:01.360 --> 00:32:04.350 align:start position:0% entire list so it will you will have a list<00:32:01.720> of<00:32:02.000> addresses<00:32:02.799> of<00:32:03.080> valid<00:32:03.399> nodes<00:32:04.159> from 00:32:04.350 --> 00:32:04.360 align:start position:0% list of addresses of valid nodes from 00:32:04.360 --> 00:32:07.990 align:start position:0% list of addresses of valid nodes from the<00:32:04.480> boot<00:32:05.360> from<00:32:05.559> the<00:32:05.720> bootstrap<00:32:06.399> node<00:32:07.399> you 00:32:07.990 --> 00:32:08.000 align:start position:0% the boot from the bootstrap node you 00:32:08.000 --> 00:32:10.629 align:start position:0% the boot from the bootstrap node you insert<00:32:08.600> all<00:32:08.880> those<00:32:09.360> addresses<00:32:10.000> into<00:32:10.240> your<00:32:10.399> own 00:32:10.629 --> 00:32:10.639 align:start position:0% insert all those addresses into your own 00:32:10.639 --> 00:32:11.590 align:start position:0% insert all those addresses into your own routing 00:32:11.590 --> 00:32:11.600 align:start position:0% routing 00:32:11.600 --> 00:32:15.149 align:start position:0% routing table<00:32:12.600> and<00:32:12.840> then<00:32:13.279> with<00:32:13.480> this<00:32:13.679> routing<00:32:14.240> table 00:32:15.149 --> 00:32:15.159 align:start position:0% table and then with this routing table 00:32:15.159 --> 00:32:20.870 align:start position:0% table and then with this routing table you<00:32:15.360> do<00:32:15.679> a<00:32:16.200> lookup<00:32:17.200> of<00:32:17.679> a<00:32:18.880> random<00:32:19.880> address 00:32:20.870 --> 00:32:20.880 align:start position:0% you do a lookup of a random address 00:32:20.880 --> 00:32:22.509 align:start position:0% you do a lookup of a random address which 00:32:22.509 --> 00:32:22.519 align:start position:0% which 00:32:22.519 --> 00:32:25.430 align:start position:0% which differs<00:32:23.519> from<00:32:24.039> the<00:32:24.399> so 00:32:25.430 --> 00:32:25.440 align:start position:0% differs from the so 00:32:25.440 --> 00:32:28.830 align:start position:0% differs from the so it<00:32:26.440> you<00:32:26.639> look<00:32:26.840> at<00:32:27.080> the<00:32:27.320> prefix<00:32:28.200> which<00:32:28.440> you 00:32:28.830 --> 00:32:28.840 align:start position:0% it you look at the prefix which you 00:32:28.840 --> 00:32:33.509 align:start position:0% it you look at the prefix which you share<00:32:29.840> with<00:32:30.080> the<00:32:30.320> bootstrap<00:32:31.399> node<00:32:32.399> and<00:32:33.240> you 00:32:33.509 --> 00:32:33.519 align:start position:0% share with the bootstrap node and you 00:32:33.519 --> 00:32:36.470 align:start position:0% share with the bootstrap node and you take<00:32:33.919> the<00:32:34.240> bit<00:32:34.760> you<00:32:35.200> flip<00:32:35.639> the 00:32:36.470 --> 00:32:36.480 align:start position:0% take the bit you flip the 00:32:36.480 --> 00:32:39.110 align:start position:0% take the bit you flip the bit<00:32:37.480> uh<00:32:37.760> that<00:32:38.039> comes 00:32:39.110 --> 00:32:39.120 align:start position:0% bit uh that comes 00:32:39.120 --> 00:32:41.629 align:start position:0% bit uh that comes afterwards<00:32:40.120> to<00:32:40.360> the<00:32:40.519> one<00:32:40.799> that<00:32:41.000> you<00:32:41.240> have<00:32:41.480> but 00:32:41.629 --> 00:32:41.639 align:start position:0% afterwards to the one that you have but 00:32:41.639 --> 00:32:43.470 align:start position:0% afterwards to the one that you have but not<00:32:41.840> the<00:32:41.960> bootstrap<00:32:42.519> node<00:32:42.799> and<00:32:42.919> you<00:32:43.039> fill<00:32:43.320> up 00:32:43.470 --> 00:32:43.480 align:start position:0% not the bootstrap node and you fill up 00:32:43.480 --> 00:32:45.110 align:start position:0% not the bootstrap node and you fill up the<00:32:43.639> rest<00:32:43.840> of<00:32:44.000> the<00:32:44.159> bits<00:32:44.519> with<00:32:44.760> with<00:32:44.880> some 00:32:45.110 --> 00:32:45.120 align:start position:0% the rest of the bits with with some 00:32:45.120 --> 00:32:48.149 align:start position:0% the rest of the bits with with some random<00:32:46.039> binary<00:32:46.559> values<00:32:47.480> and<00:32:47.639> you<00:32:47.799> make<00:32:48.000> a 00:32:48.149 --> 00:32:48.159 align:start position:0% random binary values and you make a 00:32:48.159 --> 00:32:51.470 align:start position:0% random binary values and you make a lookup<00:32:48.880> now<00:32:49.080> how<00:32:49.200> a<00:32:49.360> lookup<00:32:49.799> looks<00:32:50.360> like<00:32:51.360> with 00:32:51.470 --> 00:32:51.480 align:start position:0% lookup now how a lookup looks like with 00:32:51.480 --> 00:32:55.350 align:start position:0% lookup now how a lookup looks like with a<00:32:51.639> lookup<00:32:52.399> you<00:32:52.600> go<00:32:52.799> to<00:32:53.000> a<00:32:53.519> node<00:32:54.519> to<00:32:54.720> the<00:32:54.919> nearest 00:32:55.350 --> 00:32:55.360 align:start position:0% a lookup you go to a node to the nearest 00:32:55.360 --> 00:32:57.389 align:start position:0% a lookup you go to a node to the nearest node<00:32:55.679> that<00:32:55.799> you<00:32:55.919> can<00:32:56.120> find<00:32:56.399> in<00:32:56.519> your<00:32:56.960> routing 00:32:57.389 --> 00:32:57.399 align:start position:0% node that you can find in your routing 00:32:57.399 --> 00:32:59.750 align:start position:0% node that you can find in your routing table 00:32:59.750 --> 00:32:59.760 align:start position:0% table 00:32:59.760 --> 00:33:04.590 align:start position:0% table and<00:33:00.039> then<00:33:00.840> you<00:33:01.320> you<00:33:01.600> ask<00:33:02.080> that<00:33:02.360> next<00:33:02.760> node<00:33:03.639> to 00:33:04.590 --> 00:33:04.600 align:start position:0% and then you you ask that next node to 00:33:04.600 --> 00:33:08.230 align:start position:0% and then you you ask that next node to uh<00:33:05.360> to<00:33:05.600> give<00:33:05.880> you<00:33:06.159> the<00:33:06.399> corresponding<00:33:07.240> list 00:33:08.230 --> 00:33:08.240 align:start position:0% uh to give you the corresponding list 00:33:08.240 --> 00:33:09.990 align:start position:0% uh to give you the corresponding list you<00:33:08.440> insert<00:33:08.880> all<00:33:09.080> those<00:33:09.279> nodes<00:33:09.600> into<00:33:09.840> your 00:33:09.990 --> 00:33:10.000 align:start position:0% you insert all those nodes into your 00:33:10.000 --> 00:33:13.310 align:start position:0% you insert all those nodes into your routing<00:33:10.960> table<00:33:11.960> and<00:33:12.200> then<00:33:12.639> uh<00:33:12.880> and<00:33:13.039> then<00:33:13.159> you 00:33:13.310 --> 00:33:13.320 align:start position:0% routing table and then uh and then you 00:33:13.320 --> 00:33:15.230 align:start position:0% routing table and then uh and then you keep<00:33:13.639> continuing<00:33:14.360> until<00:33:14.679> you<00:33:14.840> find<00:33:15.080> the 00:33:15.230 --> 00:33:15.240 align:start position:0% keep continuing until you find the 00:33:15.240 --> 00:33:16.470 align:start position:0% keep continuing until you find the nearest 00:33:16.470 --> 00:33:16.480 align:start position:0% nearest 00:33:16.480 --> 00:33:20.549 align:start position:0% nearest node<00:33:17.480> uh<00:33:18.480> and<00:33:18.720> of<00:33:18.919> course<00:33:19.279> if<00:33:19.519> along<00:33:19.880> the<00:33:20.080> way 00:33:20.549 --> 00:33:20.559 align:start position:0% node uh and of course if along the way 00:33:20.559 --> 00:33:22.669 align:start position:0% node uh and of course if along the way you<00:33:20.720> find<00:33:21.120> the<00:33:21.320> actual<00:33:21.799> content<00:33:22.360> then<00:33:22.519> you 00:33:22.669 --> 00:33:22.679 align:start position:0% you find the actual content then you 00:33:22.679 --> 00:33:24.750 align:start position:0% you find the actual content then you download<00:33:23.200> that<00:33:23.440> content<00:33:24.000> you<00:33:24.120> don't<00:33:24.639> you 00:33:24.750 --> 00:33:24.760 align:start position:0% download that content you don't you 00:33:24.760 --> 00:33:27.310 align:start position:0% download that content you don't you don't<00:33:25.080> continue<00:33:25.880> but<00:33:26.039> with<00:33:26.200> a<00:33:26.360> random<00:33:26.760> lookup 00:33:27.310 --> 00:33:27.320 align:start position:0% don't continue but with a random lookup 00:33:27.320 --> 00:33:29.870 align:start position:0% don't continue but with a random lookup the<00:33:27.440> chance<00:33:27.960> of<00:33:28.120> that<00:33:28.360> happening<00:33:28.880> are 00:33:29.870 --> 00:33:29.880 align:start position:0% the chance of that happening are 00:33:29.880 --> 00:33:32.990 align:start position:0% the chance of that happening are negligible<00:33:30.720> so<00:33:30.960> that<00:33:31.080> is<00:33:31.320> nice<00:33:31.840> visualization 00:33:32.990 --> 00:33:33.000 align:start position:0% negligible so that is nice visualization 00:33:33.000 --> 00:33:37.110 align:start position:0% negligible so that is nice visualization of<00:33:34.000> look<00:33:34.760> it's<00:33:35.120> like<00:33:35.559> Circle<00:33:36.120> everybody 00:33:37.110 --> 00:33:37.120 align:start position:0% of look it's like Circle everybody 00:33:37.120 --> 00:33:39.950 align:start position:0% of look it's like Circle everybody standing<00:33:37.519> in<00:33:37.720> circle<00:33:38.240> right<00:33:38.880> so<00:33:39.200> x<00:33:39.720> no<00:33:39.840> it's 00:33:39.950 --> 00:33:39.960 align:start position:0% standing in circle right so x no it's 00:33:39.960 --> 00:33:42.549 align:start position:0% standing in circle right so x no it's not<00:33:40.080> a<00:33:40.279> circle<00:33:40.880> it's<00:33:41.120> it's<00:33:41.240> a<00:33:41.440> hyper<00:33:41.840> Cube<00:33:42.360> so 00:33:42.549 --> 00:33:42.559 align:start position:0% not a circle it's it's a hyper Cube so 00:33:42.559 --> 00:33:44.389 align:start position:0% not a circle it's it's a hyper Cube so what<00:33:42.679> you<00:33:42.840> do<00:33:43.120> when<00:33:43.279> you're<00:33:43.480> looking<00:33:43.919> up<00:33:44.159> a 00:33:44.389 --> 00:33:44.399 align:start position:0% what you do when you're looking up a 00:33:44.399 --> 00:33:47.269 align:start position:0% what you do when you're looking up a node<00:33:45.159> is<00:33:45.399> that<00:33:45.639> you're<00:33:46.200> a<00:33:46.399> lookup<00:33:46.840> is 00:33:47.269 --> 00:33:47.279 align:start position:0% node is that you're a lookup is 00:33:47.279 --> 00:33:49.870 align:start position:0% node is that you're a lookup is basically<00:33:48.279> you<00:33:48.480> you<00:33:48.639> always<00:33:49.000> go<00:33:49.279> one<00:33:49.519> bit 00:33:49.870 --> 00:33:49.880 align:start position:0% basically you you always go one bit 00:33:49.880 --> 00:33:52.789 align:start position:0% basically you you always go one bit closer<00:33:50.880> right<00:33:51.240> and<00:33:51.399> you<00:33:51.519> always<00:33:52.000> go<00:33:52.240> along<00:33:52.600> the 00:33:52.789 --> 00:33:52.799 align:start position:0% closer right and you always go along the 00:33:52.799 --> 00:33:57.029 align:start position:0% closer right and you always go along the bit<00:33:53.720> Which<00:33:54.000> is<00:33:54.760> higher<00:33:55.440> like<00:33:55.960> has<00:33:56.080> a<00:33:56.320> highest 00:33:57.029 --> 00:33:57.039 align:start position:0% bit Which is higher like has a highest 00:33:57.039 --> 00:33:59.350 align:start position:0% bit Which is higher like has a highest uh 00:33:59.350 --> 00:33:59.360 align:start position:0% uh 00:33:59.360 --> 00:34:02.590 align:start position:0% uh so<00:33:59.760> higher<00:34:00.000> order<00:34:00.440> bit<00:34:01.440> so<00:34:01.639> it's<00:34:01.880> always<00:34:02.279> like 00:34:02.590 --> 00:34:02.600 align:start position:0% so higher order bit so it's always like 00:34:02.600 --> 00:34:03.990 align:start position:0% so higher order bit so it's always like let's<00:34:02.799> suppose<00:34:03.240> this<00:34:03.440> direction<00:34:03.840> the 00:34:03.990 --> 00:34:04.000 align:start position:0% let's suppose this direction the 00:34:04.000 --> 00:34:06.029 align:start position:0% let's suppose this direction the vertical<00:34:04.559> direction<00:34:05.039> is<00:34:05.200> the<00:34:05.360> high<00:34:05.559> order 00:34:06.029 --> 00:34:06.039 align:start position:0% vertical direction is the high order 00:34:06.039 --> 00:34:08.430 align:start position:0% vertical direction is the high order Direction<00:34:06.960> so<00:34:07.200> whenever<00:34:07.600> you<00:34:07.799> go<00:34:08.040> from<00:34:08.280> this 00:34:08.430 --> 00:34:08.440 align:start position:0% Direction so whenever you go from this 00:34:08.440 --> 00:34:11.349 align:start position:0% Direction so whenever you go from this node<00:34:08.720> to<00:34:08.960> this<00:34:09.119> node<00:34:09.679> you<00:34:09.919> always<00:34:10.399> go<00:34:11.000> along 00:34:11.349 --> 00:34:11.359 align:start position:0% node to this node you always go along 00:34:11.359 --> 00:34:13.790 align:start position:0% node to this node you always go along one<00:34:11.599> dimension<00:34:12.200> closer<00:34:13.040> but<00:34:13.159> you<00:34:13.359> always 00:34:13.790 --> 00:34:13.800 align:start position:0% one dimension closer but you always 00:34:13.800 --> 00:34:16.750 align:start position:0% one dimension closer but you always follow<00:34:14.240> the<00:34:14.399> same<00:34:14.800> order<00:34:15.240> of<00:34:15.520> bits<00:34:16.440> that's<00:34:16.639> how 00:34:16.750 --> 00:34:16.760 align:start position:0% follow the same order of bits that's how 00:34:16.760 --> 00:34:19.069 align:start position:0% follow the same order of bits that's how you<00:34:16.879> do<00:34:17.040> the<00:34:17.200> lookup<00:34:17.919> and<00:34:18.040> you're<00:34:18.320> guaranteed 00:34:19.069 --> 00:34:19.079 align:start position:0% you do the lookup and you're guaranteed 00:34:19.079 --> 00:34:21.550 align:start position:0% you do the lookup and you're guaranteed to<00:34:19.399> have<00:34:20.000> a<00:34:20.200> logarithmic<00:34:20.839> number<00:34:21.280> because 00:34:21.550 --> 00:34:21.560 align:start position:0% to have a logarithmic number because 00:34:21.560 --> 00:34:25.470 align:start position:0% to have a logarithmic number because with<00:34:21.879> each<00:34:22.480> with<00:34:22.679> each<00:34:23.079> hop<00:34:24.079> the<00:34:24.760> uh<00:34:24.919> number<00:34:25.240> of 00:34:25.470 --> 00:34:25.480 align:start position:0% with each with each hop the uh number of 00:34:25.480 --> 00:34:29.750 align:start position:0% with each with each hop the uh number of common<00:34:25.919> bits<00:34:26.679> increases<00:34:27.320> at<00:34:27.480> least<00:34:27.919> by<00:34:28.560> one<00:34:29.560> so 00:34:29.750 --> 00:34:29.760 align:start position:0% common bits increases at least by one so 00:34:29.760 --> 00:34:33.389 align:start position:0% common bits increases at least by one so it<00:34:29.960> it<00:34:30.079> gives<00:34:30.280> you<00:34:30.399> a<00:34:30.560> guarantee<00:34:31.040> on<00:34:31.200> the 00:34:33.389 --> 00:34:33.399 align:start position:0% 00:34:33.399 --> 00:34:38.030 align:start position:0% diameter<00:34:34.399> okay<00:34:34.800> next 00:34:38.030 --> 00:34:38.040 align:start position:0% 00:34:38.040 --> 00:34:43.669 align:start position:0% question<00:34:39.040> what<00:34:39.200> is<00:34:39.560> the<00:34:40.560> strategy<00:34:41.119> against 00:34:43.669 --> 00:34:43.679 align:start position:0% 00:34:43.679 --> 00:34:47.909 align:start position:0% SP<00:34:44.679> well<00:34:44.960> in<00:34:45.159> case<00:34:45.359> of<00:34:45.599> bit<00:34:46.159> torant<00:34:47.159> since<00:34:47.599> they 00:34:47.909 --> 00:34:47.919 align:start position:0% SP well in case of bit torant since they 00:34:47.919 --> 00:34:51.190 align:start position:0% SP well in case of bit torant since they have<00:34:48.480> uh<00:34:49.440> since<00:34:49.839> they<00:34:50.119> it's<00:34:50.320> mutable<00:34:50.879> so<00:34:51.040> it's 00:34:51.190 --> 00:34:51.200 align:start position:0% have uh since they it's mutable so it's 00:34:51.200 --> 00:34:54.389 align:start position:0% have uh since they it's mutable so it's not<00:34:51.359> the<00:34:51.480> same<00:34:51.800> as<00:34:52.119> here<00:34:53.119> it<00:34:53.359> just<00:34:53.639> overwrites 00:34:54.389 --> 00:34:54.399 align:start position:0% not the same as here it just overwrites 00:34:54.399 --> 00:34:57.349 align:start position:0% not the same as here it just overwrites the<00:34:54.639> key<00:34:55.159> and<00:34:55.480> it<00:34:55.679> forgets<00:34:56.320> gracefully<00:34:57.040> old 00:34:57.349 --> 00:34:57.359 align:start position:0% the key and it forgets gracefully old 00:34:57.359 --> 00:35:01.390 align:start position:0% the key and it forgets gracefully old keys<00:34:57.720> so<00:34:57.920> when<00:34:58.839> so<00:34:59.200> in<00:34:59.480> in<00:34:59.800> in<00:35:00.000> case<00:35:00.240> of<00:35:01.040> in<00:35:01.240> case 00:35:01.390 --> 00:35:01.400 align:start position:0% keys so when so in in in case of in case 00:35:01.400 --> 00:35:04.230 align:start position:0% keys so when so in in in case of in case of<00:35:01.560> the<00:35:01.720> bitor<00:35:02.200> rent<00:35:02.960> the<00:35:03.160> information<00:35:03.839> is<00:35:04.000> not 00:35:04.230 --> 00:35:04.240 align:start position:0% of the bitor rent the information is not 00:35:04.240 --> 00:35:07.589 align:start position:0% of the bitor rent the information is not really<00:35:04.560> valuable<00:35:05.520> so<00:35:06.079> it<00:35:06.800> they<00:35:07.000> just<00:35:07.280> throw 00:35:07.589 --> 00:35:07.599 align:start position:0% really valuable so it they just throw 00:35:07.599 --> 00:35:09.150 align:start position:0% really valuable so it they just throw away<00:35:07.920> information<00:35:08.520> that<00:35:08.680> hasn't<00:35:08.920> been 00:35:09.150 --> 00:35:09.160 align:start position:0% away information that hasn't been 00:35:09.160 --> 00:35:11.510 align:start position:0% away information that hasn't been queried<00:35:09.560> for<00:35:09.680> a<00:35:09.839> long<00:35:10.119> time<00:35:10.960> that's<00:35:11.119> all<00:35:11.359> they 00:35:11.510 --> 00:35:11.520 align:start position:0% queried for a long time that's all they 00:35:11.520 --> 00:35:13.510 align:start position:0% queried for a long time that's all they do<00:35:11.880> and<00:35:12.079> it's<00:35:12.359> it's<00:35:12.560> sufficient<00:35:12.960> for<00:35:13.200> their 00:35:13.510 --> 00:35:13.520 align:start position:0% do and it's it's sufficient for their 00:35:13.520 --> 00:35:15.349 align:start position:0% do and it's it's sufficient for their purpose<00:35:14.200> and<00:35:14.359> it<00:35:14.480> might<00:35:14.680> be<00:35:14.839> sufficient<00:35:15.200> for 00:35:15.349 --> 00:35:15.359 align:start position:0% purpose and it might be sufficient for 00:35:15.359 --> 00:35:18.109 align:start position:0% purpose and it might be sufficient for our<00:35:15.599> purpose<00:35:15.960> as<00:35:16.320> well<00:35:17.320> I<00:35:17.400> don't<00:35:17.599> know<00:35:17.960> it 00:35:18.109 --> 00:35:18.119 align:start position:0% our purpose as well I don't know it 00:35:18.119 --> 00:35:19.670 align:start position:0% our purpose as well I don't know it depends<00:35:18.480> on<00:35:18.760> really<00:35:19.000> what<00:35:19.119> we're<00:35:19.320> going<00:35:19.520> to 00:35:19.670 --> 00:35:19.680 align:start position:0% depends on really what we're going to 00:35:19.680 --> 00:35:22.630 align:start position:0% depends on really what we're going to use<00:35:19.839> it 00:35:22.630 --> 00:35:22.640 align:start position:0% 00:35:22.640 --> 00:35:25.349 align:start position:0% for<00:35:23.640> so<00:35:23.880> what<00:35:24.000> are<00:35:24.079> we<00:35:24.200> going<00:35:24.280> to<00:35:24.400> use<00:35:24.520> it 00:35:25.349 --> 00:35:25.359 align:start position:0% for so what are we going to use it 00:35:25.359 --> 00:35:28.710 align:start position:0% for so what are we going to use it for<00:35:26.359> yeah<00:35:26.560> most<00:35:26.760> of<00:35:26.960> the<00:35:27.320> um<00:35:27.720> the<00:35:27.880> life<00:35:28.400> use<00:35:28.560> it 00:35:28.710 --> 00:35:28.720 align:start position:0% for yeah most of the um the life use it 00:35:28.720 --> 00:35:30.310 align:start position:0% for yeah most of the um the life use it you<00:35:28.839> order<00:35:29.040> to<00:35:29.560> query<00:35:29.920> things<00:35:30.160> like 00:35:30.310 --> 00:35:30.320 align:start position:0% you order to query things like 00:35:30.320 --> 00:35:31.910 align:start position:0% you order to query things like transaction 00:35:31.910 --> 00:35:31.920 align:start position:0% transaction 00:35:31.920 --> 00:35:36.670 align:start position:0% transaction receipts<00:35:33.240> for<00:35:34.240> the<00:35:34.359> only<00:35:34.599> one<00:35:35.240> no<00:35:36.240> but<00:35:36.359> you<00:35:36.440> can 00:35:36.670 --> 00:35:36.680 align:start position:0% receipts for the only one no but you can 00:35:36.680 --> 00:35:41.390 align:start position:0% receipts for the only one no but you can even<00:35:37.280> even<00:35:37.440> store<00:35:37.839> the<00:35:38.000> state<00:35:38.320> in<00:35:38.480> it<00:35:39.119> so<00:35:40.119> if<00:35:40.480> if 00:35:41.390 --> 00:35:41.400 align:start position:0% even even store the state in it so if if 00:35:41.400 --> 00:35:45.230 align:start position:0% even even store the state in it so if if the<00:35:42.400> like<00:35:42.560> if<00:35:42.680> you<00:35:42.839> have<00:35:43.040> a<00:35:43.240> full<00:35:43.960> node<00:35:44.960> but<00:35:45.119> you 00:35:45.230 --> 00:35:45.240 align:start position:0% the like if you have a full node but you 00:35:45.240 --> 00:35:47.910 align:start position:0% the like if you have a full node but you don't<00:35:45.560> have<00:35:45.720> the<00:35:45.880> storage<00:35:46.359> space<00:35:46.800> for<00:35:47.400> storing 00:35:47.910 --> 00:35:47.920 align:start position:0% don't have the storage space for storing 00:35:47.920 --> 00:35:49.470 align:start position:0% don't have the storage space for storing everything<00:35:48.320> that<00:35:48.440> a<00:35:48.560> full<00:35:48.800> node<00:35:49.040> needs<00:35:49.280> to 00:35:49.470 --> 00:35:49.480 align:start position:0% everything that a full node needs to 00:35:49.480 --> 00:35:52.589 align:start position:0% everything that a full node needs to store<00:35:50.240> it<00:35:50.440> might<00:35:50.720> dump<00:35:51.400> you<00:35:51.560> know<00:35:51.880> things<00:35:52.200> that 00:35:52.589 --> 00:35:52.599 align:start position:0% store it might dump you know things that 00:35:52.599 --> 00:35:55.390 align:start position:0% store it might dump you know things that it<00:35:53.160> that<00:35:53.319> don't<00:35:53.640> fit<00:35:54.000> into<00:35:54.280> its<00:35:54.480> storage<00:35:55.040> into 00:35:55.390 --> 00:35:55.400 align:start position:0% it that don't fit into its storage into 00:35:55.400 --> 00:36:00.190 align:start position:0% it that don't fit into its storage into this<00:35:56.040> DHD<00:35:56.839> so<00:35:56.960> it's<00:35:57.119> kind<00:35:57.200> of<00:35:57.680> public<00:35:58.400> utility 00:36:00.190 --> 00:36:00.200 align:start position:0% this DHD so it's kind of public utility 00:36:00.200 --> 00:36:01.710 align:start position:0% this DHD so it's kind of public utility forish 00:36:01.710 --> 00:36:01.720 align:start position:0% forish 00:36:01.720 --> 00:36:06.390 align:start position:0% forish yeah<00:36:02.720> if<00:36:02.920> the 00:36:06.390 --> 00:36:06.400 align:start position:0% 00:36:06.400 --> 00:36:10.030 align:start position:0% bo<00:36:07.400> well<00:36:07.560> you<00:36:07.680> need<00:36:07.880> to<00:36:08.079> find<00:36:08.440> one<00:36:08.920> so<00:36:09.760> for 00:36:10.030 --> 00:36:10.040 align:start position:0% bo well you need to find one so for 00:36:10.040 --> 00:36:12.150 align:start position:0% bo well you need to find one so for example<00:36:10.640> there<00:36:10.760> are<00:36:11.000> some<00:36:11.319> bot<00:36:11.640> nuts<00:36:12.000> that 00:36:12.150 --> 00:36:12.160 align:start position:0% example there are some bot nuts that 00:36:12.160 --> 00:36:14.589 align:start position:0% example there are some bot nuts that also<00:36:12.440> organize<00:36:13.079> themselves<00:36:13.359> into<00:36:13.680> caman<00:36:14.400> like 00:36:14.589 --> 00:36:14.599 align:start position:0% also organize themselves into caman like 00:36:14.599 --> 00:36:16.750 align:start position:0% also organize themselves into caman like networks<00:36:15.440> and<00:36:15.640> what<00:36:15.839> they<00:36:16.000> do<00:36:16.200> is<00:36:16.400> they<00:36:16.560> just 00:36:16.750 --> 00:36:16.760 align:start position:0% networks and what they do is they just 00:36:16.760 --> 00:36:19.030 align:start position:0% networks and what they do is they just probe<00:36:17.200> random<00:36:17.720> IP<00:36:18.040> addresses<00:36:18.560> until<00:36:18.880> they 00:36:19.030 --> 00:36:19.040 align:start position:0% probe random IP addresses until they 00:36:19.040 --> 00:36:21.990 align:start position:0% probe random IP addresses until they find<00:36:19.480> so<00:36:19.640> you<00:36:19.800> need<00:36:20.000> some<00:36:20.280> type<00:36:20.480> of 00:36:21.990 --> 00:36:22.000 align:start position:0% find so you need some type of 00:36:22.000 --> 00:36:25.750 align:start position:0% find so you need some type of watch<00:36:23.000> well<00:36:23.319> or<00:36:23.560> you<00:36:23.839> download<00:36:24.520> a<00:36:24.839> recent<00:36:25.319> list 00:36:25.750 --> 00:36:25.760 align:start position:0% watch well or you download a recent list 00:36:25.760 --> 00:36:28.230 align:start position:0% watch well or you download a recent list from<00:36:26.040> a<00:36:26.319> website<00:36:27.040> it's 00:36:28.230 --> 00:36:28.240 align:start position:0% from a website it's 00:36:28.240 --> 00:36:29.829 align:start position:0% from a website it's and<00:36:28.359> you<00:36:28.480> know<00:36:28.839> you<00:36:28.960> go<00:36:29.200> through<00:36:29.359> it<00:36:29.560> and<00:36:29.680> the 00:36:29.829 --> 00:36:29.839 align:start position:0% and you know you go through it and the 00:36:29.839 --> 00:36:32.270 align:start position:0% and you know you go through it and the first<00:36:30.119> Noe<00:36:30.440> that<00:36:30.560> you<00:36:30.720> find<00:36:31.000> is<00:36:31.319> okay<00:36:31.880> so<00:36:32.040> it's 00:36:32.270 --> 00:36:32.280 align:start position:0% first Noe that you find is okay so it's 00:36:32.280 --> 00:36:34.550 align:start position:0% first Noe that you find is okay so it's really<00:36:32.839> you<00:36:32.960> need<00:36:33.160> to<00:36:33.359> find<00:36:33.680> one<00:36:33.920> Noe<00:36:34.240> that<00:36:34.400> is 00:36:34.550 --> 00:36:34.560 align:start position:0% really you need to find one Noe that is 00:36:34.560 --> 00:36:35.990 align:start position:0% really you need to find one Noe that is member<00:36:34.839> of<00:36:34.960> the<00:36:35.079> network<00:36:35.480> and<00:36:35.680> then<00:36:35.800> you're 00:36:35.990 --> 00:36:36.000 align:start position:0% member of the network and then you're 00:36:36.000 --> 00:36:37.710 align:start position:0% member of the network and then you're done<00:36:36.520> and<00:36:36.680> don't<00:36:36.839> forget<00:36:37.119> it's<00:36:37.240> on<00:36:37.359> the<00:36:37.480> same 00:36:37.710 --> 00:36:37.720 align:start position:0% done and don't forget it's on the same 00:36:37.720 --> 00:36:41.349 align:start position:0% done and don't forget it's on the same network<00:36:38.000> as<00:36:38.640> ethereum<00:36:39.640> whisper<00:36:40.079> so<00:36:40.880> yeah<00:36:41.200> the 00:36:41.349 --> 00:36:41.359 align:start position:0% network as ethereum whisper so yeah the 00:36:41.359 --> 00:36:43.069 align:start position:0% network as ethereum whisper so yeah the CH<00:36:41.599> if<00:36:41.680> you<00:36:41.760> know<00:36:41.920> an<00:36:42.040> ethereum<00:36:42.520> node<00:36:42.880> you'll 00:36:43.069 --> 00:36:43.079 align:start position:0% CH if you know an ethereum node you'll 00:36:43.079 --> 00:36:46.270 align:start position:0% CH if you know an ethereum node you'll eventually<00:36:43.480> find 00:36:46.270 --> 00:36:46.280 align:start position:0% 00:36:46.280 --> 00:36:50.470 align:start position:0% a<00:36:47.280> you<00:36:47.520> remember<00:36:47.960> from 00:36:50.470 --> 00:36:50.480 align:start position:0% a you remember from 00:36:50.480 --> 00:36:52.750 align:start position:0% a you remember from connections<00:36:51.480> yeah<00:36:51.680> of<00:36:51.800> course<00:36:52.000> you<00:36:52.119> save<00:36:52.640> you 00:36:52.750 --> 00:36:52.760 align:start position:0% connections yeah of course you save you 00:36:52.760 --> 00:36:55.390 align:start position:0% connections yeah of course you save you don't<00:36:52.960> forget<00:36:53.319> your<00:36:53.480> routing<00:36:53.920> table<00:36:54.920> so<00:36:55.200> when 00:36:55.390 --> 00:36:55.400 align:start position:0% don't forget your routing table so when 00:36:55.400 --> 00:36:57.670 align:start position:0% don't forget your routing table so when when<00:36:55.520> you're<00:36:55.720> switched<00:36:56.160> on<00:36:56.760> then<00:36:56.960> you<00:36:57.160> renew 00:36:57.670 --> 00:36:57.680 align:start position:0% when you're switched on then you renew 00:36:57.680 --> 00:37:00.069 align:start position:0% when you're switched on then you renew your<00:36:57.839> routing<00:36:58.319> table<00:36:58.800> but<00:36:59.079> you<00:36:59.400> you<00:36:59.560> use<00:36:59.960> the 00:37:00.069 --> 00:37:00.079 align:start position:0% your routing table but you you use the 00:37:00.079 --> 00:37:01.510 align:start position:0% your routing table but you you use the one<00:37:00.319> that<00:37:00.440> you 00:37:01.510 --> 00:37:01.520 align:start position:0% one that you 00:37:01.520 --> 00:37:05.190 align:start position:0% one that you had<00:37:02.800> okay<00:37:03.800> the<00:37:03.960> second<00:37:04.280> SL<00:37:04.560> you<00:37:04.680> already<00:37:05.040> have 00:37:05.190 --> 00:37:05.200 align:start position:0% had okay the second SL you already have 00:37:05.200 --> 00:37:08.990 align:start position:0% had okay the second SL you already have a<00:37:05.319> bunch 00:37:08.990 --> 00:37:09.000 align:start position:0% 00:37:09.000 --> 00:37:13.069 align:start position:0% of<00:37:10.000> yes<00:37:11.000> how 00:37:13.069 --> 00:37:13.079 align:start position:0% of yes how 00:37:13.079 --> 00:37:19.069 align:start position:0% of yes how muchy<00:37:14.079> proportionally 00:37:19.069 --> 00:37:19.079 align:start position:0% 00:37:19.079 --> 00:37:22.750 align:start position:0% is<00:37:20.079> Network<00:37:20.480> to<00:37:20.680> a<00:37:20.800> scale<00:37:21.119> free<00:37:21.599> network<00:37:22.599> it 00:37:22.750 --> 00:37:22.760 align:start position:0% is Network to a scale free network it 00:37:22.760 --> 00:37:25.550 align:start position:0% is Network to a scale free network it really<00:37:23.160> depends<00:37:23.920> on<00:37:24.400> how<00:37:24.640> much<00:37:24.960> information 00:37:25.550 --> 00:37:25.560 align:start position:0% really depends on how much information 00:37:25.560 --> 00:37:29.710 align:start position:0% really depends on how much information you<00:37:26.119> store<00:37:27.119> so<00:37:27.400> this<00:37:27.680> the<00:37:27.800> latency<00:37:28.720> in<00:37:29.000> this<00:37:29.520> uh 00:37:29.710 --> 00:37:29.720 align:start position:0% you store so this the latency in this uh 00:37:29.720 --> 00:37:31.870 align:start position:0% you store so this the latency in this uh setup<00:37:30.240> really<00:37:30.560> depends<00:37:30.920> on<00:37:31.160> how<00:37:31.319> large<00:37:31.599> your 00:37:31.870 --> 00:37:31.880 align:start position:0% setup really depends on how large your 00:37:31.880 --> 00:37:34.670 align:start position:0% setup really depends on how large your diameter<00:37:32.880> is 00:37:34.670 --> 00:37:34.680 align:start position:0% diameter is 00:37:34.680 --> 00:37:38.910 align:start position:0% diameter is uh<00:37:35.680> but<00:37:36.319> uh<00:37:36.760> and<00:37:37.280> after<00:37:38.280> how<00:37:38.440> large<00:37:38.680> your 00:37:38.910 --> 00:37:38.920 align:start position:0% uh but uh and after how large your 00:37:38.920 --> 00:37:41.750 align:start position:0% uh but uh and after how large your radius<00:37:39.440> is<00:37:40.079> but<00:37:40.280> once<00:37:40.520> your<00:37:40.800> radius<00:37:41.319> has<00:37:41.480> been 00:37:41.750 --> 00:37:41.760 align:start position:0% radius is but once your radius has been 00:37:41.760 --> 00:37:43.870 align:start position:0% radius is but once your radius has been exhausted<00:37:42.760> then<00:37:42.960> it<00:37:43.119> depends<00:37:43.480> on<00:37:43.680> the 00:37:43.870 --> 00:37:43.880 align:start position:0% exhausted then it depends on the 00:37:43.880 --> 00:37:47.190 align:start position:0% exhausted then it depends on the diameter<00:37:44.560> and<00:37:44.800> actually<00:37:45.160> cam<00:37:45.640> is<00:37:45.960> slower<00:37:46.960> like 00:37:47.190 --> 00:37:47.200 align:start position:0% diameter and actually cam is slower like 00:37:47.200 --> 00:37:49.550 align:start position:0% diameter and actually cam is slower like on<00:37:47.319> a<00:37:47.560> general<00:37:47.920> scale<00:37:48.560> free<00:37:48.800> network<00:37:49.359> the 00:37:49.550 --> 00:37:49.560 align:start position:0% on a general scale free network the 00:37:49.560 --> 00:37:52.990 align:start position:0% on a general scale free network the diameter<00:37:50.240> is<00:37:50.440> Logan<00:37:51.040> over<00:37:51.480> log<00:37:51.640> Logan<00:37:52.599> whereas 00:37:52.990 --> 00:37:53.000 align:start position:0% diameter is Logan over log Logan whereas 00:37:53.000 --> 00:37:55.430 align:start position:0% diameter is Logan over log Logan whereas here<00:37:53.160> it's<00:37:53.359> log<00:37:53.599> n<00:37:53.960> so<00:37:54.200> it's<00:37:54.400> slightly<00:37:54.839> slower 00:37:55.430 --> 00:37:55.440 align:start position:0% here it's log n so it's slightly slower 00:37:55.440 --> 00:37:57.670 align:start position:0% here it's log n so it's slightly slower but<00:37:55.680> you<00:37:55.839> know<00:37:56.079> the<00:37:56.160> log<00:37:56.440> log<00:37:56.680> is<00:37:56.839> not<00:37:57.200> that<00:37:57.520> big 00:37:57.670 --> 00:37:57.680 align:start position:0% but you know the log log is not that big 00:37:57.680 --> 00:38:01.349 align:start position:0% but you know the log log is not that big a 00:38:01.349 --> 00:38:01.359 align:start position:0% 00:38:01.359 --> 00:38:03.829 align:start position:0% deal<00:38:02.359> are<00:38:02.440> you<00:38:02.560> going<00:38:02.640> to<00:38:02.839> talk 00:38:03.829 --> 00:38:03.839 align:start position:0% deal are you going to talk 00:38:03.839 --> 00:38:08.109 align:start position:0% deal are you going to talk tomorrow<00:38:04.839> uh<00:38:05.240> no<00:38:05.720> because<00:38:06.319> I<00:38:07.319> it's<00:38:07.839> it's<00:38:08.000> it's 00:38:08.109 --> 00:38:08.119 align:start position:0% tomorrow uh no because I it's it's it's 00:38:08.119 --> 00:38:09.750 align:start position:0% tomorrow uh no because I it's it's it's the<00:38:08.280> same<00:38:08.480> talk<00:38:08.720> I<00:38:08.800> didn't<00:38:09.040> realize<00:38:09.440> that<00:38:09.599> this 00:38:09.750 --> 00:38:09.760 align:start position:0% the same talk I didn't realize that this 00:38:09.760 --> 00:38:11.470 align:start position:0% the same talk I didn't realize that this talk<00:38:09.960> was<00:38:10.119> also<00:38:10.480> me<00:38:10.680> can<00:38:10.760> you 00:38:11.470 --> 00:38:11.480 align:start position:0% talk was also me can you 00:38:11.480 --> 00:38:13.550 align:start position:0% talk was also me can you elaborate<00:38:12.480> because<00:38:12.640> you<00:38:12.760> mentioned<00:38:13.079> a<00:38:13.200> lot<00:38:13.319> of 00:38:13.550 --> 00:38:13.560 align:start position:0% elaborate because you mentioned a lot of 00:38:13.560 --> 00:38:17.270 align:start position:0% elaborate because you mentioned a lot of times<00:38:13.920> before<00:38:14.319> that<00:38:14.960> mutable<00:38:15.480> and<00:38:15.880> non 00:38:17.270 --> 00:38:17.280 align:start position:0% times before that mutable and non 00:38:17.280 --> 00:38:19.069 align:start position:0% times before that mutable and non mutable 00:38:19.069 --> 00:38:19.079 align:start position:0% mutable 00:38:19.079 --> 00:38:23.829 align:start position:0% mutable dhds<00:38:20.079> kind<00:38:20.599> very<00:38:20.839> different<00:38:21.480> yes<00:38:22.200> the<00:38:22.839> there's 00:38:23.829 --> 00:38:23.839 align:start position:0% dhds kind very different yes the there's 00:38:23.839 --> 00:38:26.790 align:start position:0% dhds kind very different yes the there's interesting<00:38:24.440> about<00:38:25.240> so<00:38:25.560> about<00:38:26.000> this<00:38:26.440> the 00:38:26.790 --> 00:38:26.800 align:start position:0% interesting about so about this the 00:38:26.800 --> 00:38:29.150 align:start position:0% interesting about so about this the interesting<00:38:27.599> thing<00:38:28.000> is<00:38:28.319> that<00:38:28.520> you<00:38:28.680> never<00:38:28.960> need 00:38:29.150 --> 00:38:29.160 align:start position:0% interesting thing is that you never need 00:38:29.160 --> 00:38:31.670 align:start position:0% interesting thing is that you never need to<00:38:29.359> revisit<00:38:30.200> you<00:38:30.359> don't<00:38:30.640> need<00:38:30.920> to<00:38:31.200> keep 00:38:31.670 --> 00:38:31.680 align:start position:0% to revisit you don't need to keep 00:38:31.680 --> 00:38:33.950 align:start position:0% to revisit you don't need to keep querying<00:38:32.680> like<00:38:32.800> you<00:38:32.920> don't<00:38:33.160> need<00:38:33.839> like 00:38:33.950 --> 00:38:33.960 align:start position:0% querying like you don't need like 00:38:33.960 --> 00:38:36.750 align:start position:0% querying like you don't need like flooding<00:38:34.599> the<00:38:34.760> network<00:38:35.480> with<00:38:36.280> with<00:38:36.440> new 00:38:36.750 --> 00:38:36.760 align:start position:0% flooding the network with with new 00:38:36.760 --> 00:38:39.430 align:start position:0% flooding the network with with new information<00:38:37.319> is<00:38:37.480> not<00:38:37.680> an<00:38:37.839> issue<00:38:38.800> so<00:38:39.079> here<00:38:39.280> you 00:38:39.430 --> 00:38:39.440 align:start position:0% information is not an issue so here you 00:38:39.440 --> 00:38:41.990 align:start position:0% information is not an issue so here you can<00:38:39.680> get<00:38:39.880> away<00:38:40.359> with<00:38:40.839> if<00:38:41.040> something<00:38:41.440> is<00:38:41.640> asked 00:38:41.990 --> 00:38:42.000 align:start position:0% can get away with if something is asked 00:38:42.000 --> 00:38:44.630 align:start position:0% can get away with if something is asked of<00:38:42.200> you<00:38:42.400> that<00:38:42.560> you<00:38:42.680> don't<00:38:43.040> know<00:38:43.839> then<00:38:44.000> you<00:38:44.240> find 00:38:44.630 --> 00:38:44.640 align:start position:0% of you that you don't know then you find 00:38:44.640 --> 00:38:47.829 align:start position:0% of you that you don't know then you find it<00:38:45.640> and<00:38:45.839> you<00:38:46.000> store<00:38:46.359> it<00:38:46.480> for<00:38:46.720> later 00:38:47.829 --> 00:38:47.839 align:start position:0% it and you store it for later 00:38:47.839 --> 00:38:50.390 align:start position:0% it and you store it for later reference<00:38:48.839> and<00:38:49.119> you<00:38:49.280> know<00:38:49.480> how<00:38:49.640> to<00:38:49.800> flood<00:38:50.240> the 00:38:50.390 --> 00:38:50.400 align:start position:0% reference and you know how to flood the 00:38:50.400 --> 00:38:53.510 align:start position:0% reference and you know how to flood the network<00:38:51.119> with<00:38:51.880> uh<00:38:52.880> with<00:38:53.079> with<00:38:53.240> new 00:38:53.510 --> 00:38:53.520 align:start position:0% network with uh with with new 00:38:53.520 --> 00:38:55.750 align:start position:0% network with uh with with new information<00:38:54.240> is<00:38:54.359> not<00:38:54.560> an<00:38:54.720> issue<00:38:55.119> here<00:38:55.520> because 00:38:55.750 --> 00:38:55.760 align:start position:0% information is not an issue here because 00:38:55.760 --> 00:38:57.589 align:start position:0% information is not an issue here because it<00:38:55.880> never<00:38:56.119> gets<00:38:56.359> overwritten<00:38:57.160> you<00:38:57.319> know<00:38:57.480> know 00:38:57.589 --> 00:38:57.599 align:start position:0% it never gets overwritten you know know 00:38:57.599 --> 00:39:00.589 align:start position:0% it never gets overwritten you know know it<00:38:57.720> propagates<00:38:58.280> slowly<00:38:58.839> and<00:38:59.079> and<00:38:59.240> it's<00:38:59.599> okay 00:39:00.589 --> 00:39:00.599 align:start position:0% it propagates slowly and and it's okay 00:39:00.599 --> 00:39:04.069 align:start position:0% it propagates slowly and and it's okay basically<00:39:01.079> any<00:39:01.400> any<00:39:01.720> any<00:39:02.480> any<00:39:03.000> stupid<00:39:03.480> tactic 00:39:04.069 --> 00:39:04.079 align:start position:0% basically any any any any stupid tactic 00:39:04.079 --> 00:39:06.630 align:start position:0% basically any any any any stupid tactic for<00:39:04.280> example<00:39:04.760> if<00:39:04.920> you<00:39:05.640> if<00:39:05.800> you<00:39:06.000> get<00:39:06.200> some<00:39:06.440> piece 00:39:06.630 --> 00:39:06.640 align:start position:0% for example if you if you get some piece 00:39:06.640 --> 00:39:09.589 align:start position:0% for example if you if you get some piece of<00:39:06.880> information<00:39:07.640> you<00:39:07.960> you<00:39:08.079> send<00:39:08.440> it<00:39:09.160> to<00:39:09.400> the 00:39:09.589 --> 00:39:09.599 align:start position:0% of information you you send it to the 00:39:09.599 --> 00:39:12.589 align:start position:0% of information you you send it to the nearest<00:39:10.200> two<00:39:10.520> nodes<00:39:11.040> that<00:39:11.160> you<00:39:11.319> can<00:39:11.640> find 00:39:12.589 --> 00:39:12.599 align:start position:0% nearest two nodes that you can find 00:39:12.599 --> 00:39:15.230 align:start position:0% nearest two nodes that you can find that's<00:39:13.000> good<00:39:13.440> enough<00:39:14.440> because<00:39:14.800> that<00:39:14.960> will 00:39:15.230 --> 00:39:15.240 align:start position:0% that's good enough because that will 00:39:15.240 --> 00:39:18.309 align:start position:0% that's good enough because that will flood<00:39:16.240> like<00:39:17.119> it<00:39:17.200> will<00:39:17.440> go<00:39:17.640> in<00:39:17.760> the<00:39:17.920> general 00:39:18.309 --> 00:39:18.319 align:start position:0% flood like it will go in the general 00:39:18.319 --> 00:39:20.470 align:start position:0% flood like it will go in the general direction<00:39:18.760> where<00:39:18.880> it<00:39:19.040> needs<00:39:19.280> to<00:39:19.480> be<00:39:20.040> and<00:39:20.200> it's 00:39:20.470 --> 00:39:20.480 align:start position:0% direction where it needs to be and it's 00:39:20.480 --> 00:39:22.109 align:start position:0% direction where it needs to be and it's okay<00:39:20.680> for<00:39:20.880> you<00:39:21.079> so<00:39:21.240> you<00:39:21.400> don't<00:39:21.640> have<00:39:21.760> to<00:39:21.920> be 00:39:22.109 --> 00:39:22.119 align:start position:0% okay for you so you don't have to be 00:39:22.119 --> 00:39:24.630 align:start position:0% okay for you so you don't have to be very<00:39:22.359> clever<00:39:22.880> about<00:39:23.280> how<00:39:23.440> to<00:39:23.640> make<00:39:23.839> sure<00:39:24.280> that 00:39:24.630 --> 00:39:24.640 align:start position:0% very clever about how to make sure that 00:39:24.640 --> 00:39:26.910 align:start position:0% very clever about how to make sure that new<00:39:24.920> information<00:39:25.560> propagates<00:39:26.560> through<00:39:26.760> the 00:39:26.910 --> 00:39:26.920 align:start position:0% new information propagates through the 00:39:26.920 --> 00:39:27.990 align:start position:0% new information propagates through the network 00:39:27.990 --> 00:39:28.000 align:start position:0% network 00:39:28.000 --> 00:39:30.710 align:start position:0% network it<00:39:28.480> it<00:39:28.680> it<00:39:28.920> it<00:39:29.160> like<00:39:29.640> it's<00:39:29.960> half<00:39:30.160> of<00:39:30.319> the<00:39:30.440> code 00:39:30.710 --> 00:39:30.720 align:start position:0% it it it it like it's half of the code 00:39:30.720 --> 00:39:34.950 align:start position:0% it it it it like it's half of the code of<00:39:30.960> the<00:39:31.560> of<00:39:31.839> cadamia<00:39:32.839> you<00:39:33.280> can<00:39:34.280> safely<00:39:34.680> leave 00:39:34.950 --> 00:39:34.960 align:start position:0% of the of cadamia you can safely leave 00:39:34.960 --> 00:39:39.390 align:start position:0% of the of cadamia you can safely leave that<00:39:35.520> out 00:39:39.390 --> 00:39:39.400 align:start position:0% 00:39:39.400 --> 00:39:42.790 align:start position:0% yes 00:39:42.790 --> 00:39:42.800 align:start position:0% 00:39:42.800 --> 00:39:45.470 align:start position:0% thise<00:39:43.800> ENT 00:39:45.470 --> 00:39:45.480 align:start position:0% thise ENT 00:39:45.480 --> 00:39:50.670 align:start position:0% thise ENT exp<00:39:46.480> and<00:39:46.800> removed 00:39:50.670 --> 00:39:50.680 align:start position:0% 00:39:50.680 --> 00:39:54.910 align:start position:0% when<00:39:51.680> uh<00:39:52.240> for<00:39:52.520> with 00:39:54.910 --> 00:39:54.920 align:start position:0% when uh for with 00:39:54.920 --> 00:39:59.069 align:start position:0% when uh for with to<00:39:55.920> uh<00:39:56.319> good<00:39:56.599> question<00:39:57.040> because 00:39:59.069 --> 00:39:59.079 align:start position:0% to uh good question because 00:39:59.079 --> 00:40:05.430 align:start position:0% to uh good question because keep<00:39:59.200> it<00:39:59.520> there<00:39:59.720> you<00:39:59.920> have<00:40:00.240> refresh<00:40:01.119> or 00:40:05.430 --> 00:40:05.440 align:start position:0% 00:40:05.440 --> 00:40:08.510 align:start position:0% refesh<00:40:06.440> well<00:40:06.680> refreshing<00:40:07.240> the<00:40:07.440> spam<00:40:07.960> costs 00:40:08.510 --> 00:40:08.520 align:start position:0% refesh well refreshing the spam costs 00:40:08.520 --> 00:40:11.309 align:start position:0% refesh well refreshing the spam costs right<00:40:08.680> you<00:40:08.800> need<00:40:08.960> to<00:40:09.119> query<00:40:09.640> it<00:40:10.640> continually 00:40:11.309 --> 00:40:11.319 align:start position:0% right you need to query it continually 00:40:11.319 --> 00:40:13.349 align:start position:0% right you need to query it continually so<00:40:11.520> do<00:40:11.680> do<00:40:11.839> look<00:40:12.040> up<00:40:12.280> so<00:40:12.480> if<00:40:12.680> if<00:40:12.800> you<00:40:12.880> want<00:40:13.079> to 00:40:13.349 --> 00:40:13.359 align:start position:0% so do do look up so if if you want to 00:40:13.359 --> 00:40:16.069 align:start position:0% so do do look up so if if you want to spam<00:40:13.960> that<00:40:14.200> way<00:40:14.640> it's<00:40:14.920> probably 00:40:16.069 --> 00:40:16.079 align:start position:0% spam that way it's probably 00:40:16.079 --> 00:40:17.950 align:start position:0% spam that way it's probably doable 00:40:17.950 --> 00:40:17.960 align:start position:0% doable 00:40:17.960 --> 00:40:20.430 align:start position:0% doable uh<00:40:18.960> like<00:40:19.160> I<00:40:19.240> don't<00:40:19.400> know<00:40:19.920> it<00:40:20.040> it<00:40:20.160> really 00:40:20.430 --> 00:40:20.440 align:start position:0% uh like I don't know it it really 00:40:20.440 --> 00:40:21.950 align:start position:0% uh like I don't know it it really depends<00:40:20.760> on<00:40:20.920> what<00:40:21.040> we're<00:40:21.200> going<00:40:21.480> to<00:40:21.599> use<00:40:21.800> it 00:40:21.950 --> 00:40:21.960 align:start position:0% depends on what we're going to use it 00:40:21.960 --> 00:40:25.109 align:start position:0% depends on what we're going to use it for<00:40:22.319> how<00:40:22.640> how<00:40:22.760> do<00:40:22.880> you<00:40:23.079> incentivize<00:40:24.079> uh<00:40:25.000> like 00:40:25.109 --> 00:40:25.119 align:start position:0% for how how do you incentivize uh like 00:40:25.119 --> 00:40:26.910 align:start position:0% for how how do you incentivize uh like this<00:40:25.240> is<00:40:25.480> like<00:40:25.720> this<00:40:25.800> is<00:40:25.920> an<00:40:26.160> open<00:40:26.440> network 00:40:26.910 --> 00:40:26.920 align:start position:0% this is like this is an open network 00:40:26.920 --> 00:40:28.750 align:start position:0% this is like this is an open network basically<00:40:27.359> it<00:40:27.480> stores<00:40:27.920> anything<00:40:28.200> you<00:40:28.400> give<00:40:28.560> to 00:40:28.750 --> 00:40:28.760 align:start position:0% basically it stores anything you give to 00:40:28.760 --> 00:40:30.910 align:start position:0% basically it stores anything you give to it<00:40:29.200> it<00:40:29.359> doesn't<00:40:29.640> even<00:40:29.920> have<00:40:30.040> to<00:40:30.200> fit<00:40:30.440> into<00:40:30.680> 4 00:40:30.910 --> 00:40:30.920 align:start position:0% it it doesn't even have to fit into 4 00:40:30.920 --> 00:40:33.349 align:start position:0% it it doesn't even have to fit into 4 kiloby<00:40:31.440> you<00:40:31.560> can<00:40:31.720> split<00:40:32.000> it<00:40:32.160> up<00:40:32.760> you<00:40:32.920> can<00:40:33.280> you 00:40:33.349 --> 00:40:33.359 align:start position:0% kiloby you can split it up you can you 00:40:33.359 --> 00:40:36.150 align:start position:0% kiloby you can split it up you can you can<00:40:33.520> store<00:40:33.839> anything<00:40:34.200> in<00:40:34.319> it<00:40:35.280> there's 00:40:36.150 --> 00:40:36.160 align:start position:0% can store anything in it there's 00:40:36.160 --> 00:40:39.670 align:start position:0% can store anything in it there's no<00:40:37.160> yes<00:40:37.359> but<00:40:37.480> the<00:40:37.800> question<00:40:38.800> to<00:40:39.040> put<00:40:39.280> something 00:40:39.670 --> 00:40:39.680 align:start position:0% no yes but the question to put something 00:40:39.680 --> 00:40:41.309 align:start position:0% no yes but the question to put something in<00:40:39.839> this<00:40:40.000> network<00:40:40.480> then<00:40:40.640> you<00:40:40.760> can<00:40:40.960> keep<00:40:41.119> it 00:40:41.309 --> 00:40:41.319 align:start position:0% in this network then you can keep it 00:40:41.319 --> 00:40:42.910 align:start position:0% in this network then you can keep it alive<00:40:41.640> and<00:40:41.760> I<00:40:41.880> don't<00:40:42.119> think<00:40:42.240> it<00:40:42.400> costs<00:40:42.760> too 00:40:42.910 --> 00:40:42.920 align:start position:0% alive and I don't think it costs too 00:40:42.920 --> 00:40:46.190 align:start position:0% alive and I don't think it costs too much<00:40:43.079> you<00:40:43.319> keep<00:40:43.480> it<00:40:44.280> no<00:40:44.480> it 00:40:46.190 --> 00:40:46.200 align:start position:0% much you keep it no it 00:40:46.200 --> 00:40:49.270 align:start position:0% much you keep it no it doesn't<00:40:47.200> so<00:40:47.520> basically<00:40:48.280> what<00:40:48.560> what<00:40:48.760> happens 00:40:49.270 --> 00:40:49.280 align:start position:0% doesn't so basically what what happens 00:40:49.280 --> 00:40:53.349 align:start position:0% doesn't so basically what what happens is<00:40:49.520> is<00:40:49.640> shown<00:40:50.280> here<00:40:51.280> so<00:40:51.560> this<00:40:51.680> is<00:40:51.920> the<00:40:52.359> relevant 00:40:53.349 --> 00:40:53.359 align:start position:0% is is shown here so this is the relevant 00:40:53.359 --> 00:40:55.670 align:start position:0% is is shown here so this is the relevant uh<00:40:53.560> figure<00:40:54.560> that<00:40:54.760> you<00:40:54.839> know<00:40:55.000> if<00:40:55.160> there's<00:40:55.440> too 00:40:55.670 --> 00:40:55.680 align:start position:0% uh figure that you know if there's too 00:40:55.680 --> 00:40:58.470 align:start position:0% uh figure that you know if there's too much<00:40:56.040> stuff<00:40:56.359> and<00:40:56.480> the<00:40:56.640> notes<00:40:56.960> can<00:40:57.440> keep<00:40:57.720> up 00:40:58.470 --> 00:40:58.480 align:start position:0% much stuff and the notes can keep up 00:40:58.480 --> 00:41:00.750 align:start position:0% much stuff and the notes can keep up then<00:40:58.680> there<00:40:58.880> will<00:40:59.119> be<00:40:59.319> some<00:40:59.560> blanks<00:41:00.119> here<00:41:00.599> and 00:41:00.750 --> 00:41:00.760 align:start position:0% then there will be some blanks here and 00:41:00.760 --> 00:41:02.550 align:start position:0% then there will be some blanks here and then<00:41:00.880> you<00:41:01.040> need<00:41:01.200> to<00:41:01.480> decide<00:41:01.960> what<00:41:02.079> to<00:41:02.280> throw 00:41:02.550 --> 00:41:02.560 align:start position:0% then you need to decide what to throw 00:41:02.560 --> 00:41:05.150 align:start position:0% then you need to decide what to throw out<00:41:02.839> because<00:41:03.079> if<00:41:03.200> you<00:41:03.319> throw<00:41:03.640> out<00:41:04.160> information 00:41:05.150 --> 00:41:05.160 align:start position:0% out because if you throw out information 00:41:05.160 --> 00:41:08.190 align:start position:0% out because if you throw out information then<00:41:05.440> these<00:41:05.640> circles<00:41:06.119> will<00:41:06.359> grow<00:41:06.920> again<00:41:07.920> so 00:41:08.190 --> 00:41:08.200 align:start position:0% then these circles will grow again so 00:41:08.200 --> 00:41:09.870 align:start position:0% then these circles will grow again so basically<00:41:08.599> you<00:41:08.720> need<00:41:08.880> to<00:41:09.119> decide<00:41:09.560> what<00:41:09.680> to 00:41:09.870 --> 00:41:09.880 align:start position:0% basically you need to decide what to 00:41:09.880 --> 00:41:11.910 align:start position:0% basically you need to decide what to throw<00:41:10.200> out<00:41:10.599> when<00:41:10.920> when<00:41:11.079> you're 00:41:11.910 --> 00:41:11.920 align:start position:0% throw out when when you're 00:41:11.920 --> 00:41:14.550 align:start position:0% throw out when when you're full<00:41:12.920> uh<00:41:13.280> I<00:41:13.359> mean<00:41:13.520> when<00:41:13.640> you're<00:41:13.839> really<00:41:14.040> full 00:41:14.550 --> 00:41:14.560 align:start position:0% full uh I mean when you're really full 00:41:14.560 --> 00:41:17.430 align:start position:0% full uh I mean when you're really full when<00:41:14.839> when<00:41:15.240> when<00:41:15.440> things<00:41:15.680> get<00:41:15.920> really<00:41:16.200> bad<00:41:17.160> so 00:41:17.430 --> 00:41:17.440 align:start position:0% when when when things get really bad so 00:41:17.440 --> 00:41:19.190 align:start position:0% when when when things get really bad so when<00:41:17.680> when<00:41:17.839> not<00:41:18.000> only<00:41:18.240> are<00:41:18.400> you<00:41:18.520> full<00:41:18.880> but<00:41:19.000> your 00:41:19.190 --> 00:41:19.200 align:start position:0% when when not only are you full but your 00:41:19.200 --> 00:41:22.750 align:start position:0% when when not only are you full but your radius<00:41:19.839> is<00:41:20.319> is<00:41:20.599> is<00:41:20.800> is<00:41:20.920> too 00:41:22.750 --> 00:41:22.760 align:start position:0% radius is is is is too 00:41:22.760 --> 00:41:25.270 align:start position:0% radius is is is is too small<00:41:23.760> can<00:41:23.880> you<00:41:24.119> can<00:41:24.200> you<00:41:24.400> detect<00:41:24.960> that<00:41:25.160> this 00:41:25.270 --> 00:41:25.280 align:start position:0% small can you can you detect that this 00:41:25.280 --> 00:41:28.309 align:start position:0% small can you can you detect that this is<00:41:25.480> happening<00:41:26.240> yeah<00:41:26.400> you<00:41:26.520> can<00:41:26.760> detect<00:41:27.440> because 00:41:28.309 --> 00:41:28.319 align:start position:0% is happening yeah you can detect because 00:41:28.319 --> 00:41:31.990 align:start position:0% is happening yeah you can detect because the<00:41:28.960> again<00:41:29.400> because<00:41:29.960> the<00:41:30.599> uh<00:41:30.839> cont<00:41:31.400> the<00:41:31.599> key 00:41:31.990 --> 00:41:32.000 align:start position:0% the again because the uh cont the key 00:41:32.000 --> 00:41:34.270 align:start position:0% the again because the uh cont the key value<00:41:32.520> pair<00:41:33.040> is<00:41:33.280> not 00:41:34.270 --> 00:41:34.280 align:start position:0% value pair is not 00:41:34.280 --> 00:41:37.550 align:start position:0% value pair is not arbitrary<00:41:35.280> so<00:41:35.599> it's<00:41:35.880> a<00:41:36.359> it's<00:41:36.480> a<00:41:36.720> hash<00:41:37.079> so<00:41:37.319> it's 00:41:37.550 --> 00:41:37.560 align:start position:0% arbitrary so it's a it's a hash so it's 00:41:37.560 --> 00:41:39.309 align:start position:0% arbitrary so it's a it's a hash so it's a<00:41:38.079> uniform 00:41:39.309 --> 00:41:39.319 align:start position:0% a uniform 00:41:39.319 --> 00:41:42.430 align:start position:0% a uniform Randomness<00:41:40.319> it's<00:41:40.520> uniformly<00:41:41.160> randomly 00:41:42.430 --> 00:41:42.440 align:start position:0% Randomness it's uniformly randomly 00:41:42.440 --> 00:41:45.109 align:start position:0% Randomness it's uniformly randomly distributed<00:41:43.440> so<00:41:43.720> from<00:41:44.000> that<00:41:44.240> you<00:41:44.359> can<00:41:44.560> be<00:41:44.760> sure 00:41:45.109 --> 00:41:45.119 align:start position:0% distributed so from that you can be sure 00:41:45.119 --> 00:41:47.150 align:start position:0% distributed so from that you can be sure that<00:41:45.319> the<00:41:45.520> density<00:41:45.960> of<00:41:46.200> information<00:41:46.760> in<00:41:46.920> your 00:41:47.150 --> 00:41:47.160 align:start position:0% that the density of information in your 00:41:47.160 --> 00:41:49.030 align:start position:0% that the density of information in your neighborhood<00:41:47.720> is<00:41:47.880> the<00:41:48.040> same<00:41:48.280> as<00:41:48.400> the<00:41:48.560> density 00:41:49.030 --> 00:41:49.040 align:start position:0% neighborhood is the same as the density 00:41:49.040 --> 00:41:51.390 align:start position:0% neighborhood is the same as the density everywhere<00:41:49.480> else<00:41:50.319> and<00:41:50.520> from<00:41:50.800> that<00:41:50.960> you<00:41:51.079> can 00:41:51.390 --> 00:41:51.400 align:start position:0% everywhere else and from that you can 00:41:51.400 --> 00:41:53.470 align:start position:0% everywhere else and from that you can make<00:41:51.760> very<00:41:52.240> accurate<00:41:52.640> assumptions<00:41:53.119> of<00:41:53.319> how 00:41:53.470 --> 00:41:53.480 align:start position:0% make very accurate assumptions of how 00:41:53.480 --> 00:41:55.430 align:start position:0% make very accurate assumptions of how much<00:41:53.680> information<00:41:54.160> is<00:41:54.280> stored<00:41:54.599> in<00:41:54.720> the<00:41:54.839> whole 00:41:55.430 --> 00:41:55.440 align:start position:0% much information is stored in the whole 00:41:55.440 --> 00:41:57.790 align:start position:0% much information is stored in the whole network<00:41:56.440> but<00:41:56.599> it<00:41:56.760> still<00:41:56.960> doesn't<00:41:57.359> tell<00:41:57.560> you 00:41:57.790 --> 00:41:57.800 align:start position:0% network but it still doesn't tell you 00:41:57.800 --> 00:42:03.829 align:start position:0% network but it still doesn't tell you whether 00:42:03.829 --> 00:42:03.839 align:start position:0% 00:42:03.839 --> 00:42:06.510 align:start position:0% there's<00:42:04.839> no<00:42:05.040> you<00:42:05.240> can<00:42:05.440> you<00:42:05.560> can<00:42:05.720> make<00:42:05.960> educated 00:42:06.510 --> 00:42:06.520 align:start position:0% there's no you can you can make educated 00:42:06.520 --> 00:42:08.589 align:start position:0% there's no you can you can make educated guesses<00:42:06.920> about<00:42:07.200> how<00:42:07.400> bad<00:42:07.599> the<00:42:07.760> situation<00:42:08.240> is 00:42:08.589 --> 00:42:08.599 align:start position:0% guesses about how bad the situation is 00:42:08.599 --> 00:42:10.790 align:start position:0% guesses about how bad the situation is so<00:42:09.599> that<00:42:09.760> that's<00:42:09.960> another<00:42:10.359> thing<00:42:10.599> just 00:42:10.790 --> 00:42:10.800 align:start position:0% so that that's another thing just 00:42:10.800 --> 00:42:12.470 align:start position:0% so that that's another thing just referring<00:42:11.240> back<00:42:11.359> to<00:42:11.520> your<00:42:11.800> question<00:42:12.200> that 00:42:12.470 --> 00:42:12.480 align:start position:0% referring back to your question that 00:42:12.480 --> 00:42:14.390 align:start position:0% referring back to your question that because<00:42:12.720> of<00:42:13.000> that<00:42:13.280> because<00:42:13.520> you<00:42:13.640> can<00:42:13.800> be<00:42:14.000> sure 00:42:14.390 --> 00:42:14.400 align:start position:0% because of that because you can be sure 00:42:14.400 --> 00:42:17.230 align:start position:0% because of that because you can be sure that<00:42:14.680> the<00:42:15.359> the<00:42:15.560> keys<00:42:15.839> are<00:42:16.119> distributed 00:42:17.230 --> 00:42:17.240 align:start position:0% that the the keys are distributed 00:42:17.240 --> 00:42:20.990 align:start position:0% that the the keys are distributed uniformly<00:42:18.240> and<00:42:18.599> it's<00:42:19.240> immutable<00:42:20.240> you<00:42:20.440> can 00:42:20.990 --> 00:42:21.000 align:start position:0% uniformly and it's immutable you can 00:42:21.000 --> 00:42:23.030 align:start position:0% uniformly and it's immutable you can actually<00:42:21.480> from<00:42:21.640> a<00:42:21.800> local<00:42:22.200> point<00:42:22.400> of<00:42:22.559> view<00:42:22.760> of<00:42:22.880> a 00:42:23.030 --> 00:42:23.040 align:start position:0% actually from a local point of view of a 00:42:23.040 --> 00:42:27.829 align:start position:0% actually from a local point of view of a node<00:42:23.800> has<00:42:24.000> a<00:42:24.280> fairly<00:42:24.839> good<00:42:25.520> uh<00:42:26.520> uh<00:42:26.680> good<00:42:27.520> of<00:42:27.680> how 00:42:27.829 --> 00:42:27.839 align:start position:0% node has a fairly good uh uh good of how 00:42:27.839 --> 00:42:31.670 align:start position:0% node has a fairly good uh uh good of how full<00:42:28.160> the<00:42:28.280> whole<00:42:28.520> network 00:42:31.670 --> 00:42:31.680 align:start position:0% 00:42:31.680 --> 00:42:36.589 align:start position:0% is<00:42:32.680> yes<00:42:33.000> how<00:42:33.160> does<00:42:33.880> with<00:42:34.200> e<00:42:34.720> Road<00:42:35.640> SW<00:42:36.040> so<00:42:36.359> it 00:42:36.589 --> 00:42:36.599 align:start position:0% is yes how does with e Road SW so it 00:42:36.599 --> 00:42:38.069 align:start position:0% is yes how does with e Road SW so it first 00:42:38.069 --> 00:42:38.079 align:start position:0% first 00:42:38.079 --> 00:42:42.589 align:start position:0% first be<00:42:39.079> switch<00:42:39.400> over<00:42:39.599> to<00:42:39.880> this<00:42:40.640> or<00:42:41.640> I<00:42:41.800> think<00:42:41.960> so<00:42:42.240> so 00:42:42.589 --> 00:42:42.599 align:start position:0% be switch over to this or I think so so 00:42:42.599 --> 00:42:46.309 align:start position:0% be switch over to this or I think so so I<00:42:42.720> think<00:42:42.960> that<00:42:43.200> it<00:42:43.359> will<00:42:43.559> not<00:42:43.839> be<00:42:44.280> in<00:42:44.760> uh<00:42:45.760> in<00:42:46.160> in 00:42:46.309 --> 00:42:46.319 align:start position:0% I think that it will not be in uh in in 00:42:46.319 --> 00:42:48.470 align:start position:0% I think that it will not be in uh in in the<00:42:46.599> next<00:42:46.960> proof<00:42:47.160> of<00:42:47.400> concept<00:42:47.760> it<00:42:47.920> will<00:42:48.079> not<00:42:48.280> be 00:42:48.470 --> 00:42:48.480 align:start position:0% the next proof of concept it will not be 00:42:48.480 --> 00:42:50.190 align:start position:0% the next proof of concept it will not be there<00:42:48.839> but<00:42:49.000> in<00:42:49.160> proof<00:42:49.400> of<00:42:49.559> concept<00:42:49.960> number 00:42:50.190 --> 00:42:50.200 align:start position:0% there but in proof of concept number 00:42:50.200 --> 00:42:53.109 align:start position:0% there but in proof of concept number eight<00:42:50.520> it<00:42:50.920> might<00:42:51.920> right<00:42:52.200> that's<00:42:52.680> that's 00:42:53.109 --> 00:42:53.119 align:start position:0% eight it might right that's that's 00:42:53.119 --> 00:42:56.190 align:start position:0% eight it might right that's that's that's<00:42:53.280> where<00:42:53.400> it<00:42:53.520> belongs<00:42:54.000> that's<00:42:55.200> that's 00:42:56.190 --> 00:42:56.200 align:start position:0% that's where it belongs that's that's 00:42:56.200 --> 00:42:57.790 align:start position:0% that's where it belongs that's that's that's<00:42:56.400> entirely<00:42:56.800> feasible<00:42:57.280> so<00:42:57.400> I<00:42:57.480> think<00:42:57.640> the 00:42:57.790 --> 00:42:57.800 align:start position:0% that's entirely feasible so I think the 00:42:57.800 --> 00:43:01.750 align:start position:0% that's entirely feasible so I think the target<00:42:58.119> for<00:42:58.359> this<00:42:58.559> is<00:42:59.079> mons<00:42:59.359> of 00:43:01.750 --> 00:43:01.760 align:start position:0% 00:43:01.760 --> 00:43:04.549 align:start position:0% eight<00:43:02.760> yes<00:43:03.319> just<00:43:03.559> use<00:43:03.800> case<00:43:04.040> if<00:43:04.119> you<00:43:04.319> want<00:43:04.440> to 00:43:04.549 --> 00:43:04.559 align:start position:0% eight yes just use case if you want to 00:43:04.559 --> 00:43:06.790 align:start position:0% eight yes just use case if you want to have<00:43:04.680> a<00:43:04.839> stud<00:43:05.280> website<00:43:05.720> with<00:43:05.839> a<00:43:06.079> big<00:43:06.319> movie<00:43:06.640> on 00:43:06.790 --> 00:43:06.800 align:start position:0% have a stud website with a big movie on 00:43:06.800 --> 00:43:10.190 align:start position:0% have a stud website with a big movie on it<00:43:07.520> couple<00:43:08.040> gabes<00:43:09.000> but<00:43:09.119> if<00:43:09.359> I<00:43:09.559> always<00:43:09.839> store 00:43:10.190 --> 00:43:10.200 align:start position:0% it couple gabes but if I always store 00:43:10.200 --> 00:43:11.870 align:start position:0% it couple gabes but if I always store them<00:43:10.400> they<00:43:10.480> would<00:43:10.680> always<00:43:11.000> be<00:43:11.520> there<00:43:11.680> for 00:43:11.870 --> 00:43:11.880 align:start position:0% them they would always be there for 00:43:11.880 --> 00:43:13.990 align:start position:0% them they would always be there for other<00:43:12.040> one<00:43:12.200> to<00:43:12.400> download<00:43:12.920> right<00:43:13.599> that's<00:43:13.760> how<00:43:13.920> I 00:43:13.990 --> 00:43:14.000 align:start position:0% other one to download right that's how I 00:43:14.000 --> 00:43:16.069 align:start position:0% other one to download right that's how I would<00:43:14.160> do<00:43:14.319> this<00:43:14.559> like<00:43:14.720> I<00:43:14.960> the<00:43:15.280> server<00:43:15.680> of<00:43:15.839> my 00:43:16.069 --> 00:43:16.079 align:start position:0% would do this like I the server of my 00:43:16.079 --> 00:43:18.150 align:start position:0% would do this like I the server of my website<00:43:16.559> store<00:43:16.920> the<00:43:17.119> stuff<00:43:17.480> and<00:43:17.680> even<00:43:17.880> if<00:43:18.040> no 00:43:18.150 --> 00:43:18.160 align:start position:0% website store the stuff and even if no 00:43:18.160 --> 00:43:20.150 align:start position:0% website store the stuff and even if no one's<00:43:18.400> using<00:43:18.680> it<00:43:18.800> it's<00:43:19.040> always<00:43:19.440> there<00:43:19.960> it's 00:43:20.150 --> 00:43:20.160 align:start position:0% one's using it it's always there it's 00:43:20.160 --> 00:43:22.309 align:start position:0% one's using it it's always there it's kind<00:43:20.280> of<00:43:20.400> a<00:43:20.559> use<00:43:20.880> case<00:43:21.480> for 00:43:22.309 --> 00:43:22.319 align:start position:0% kind of a use case for 00:43:22.319 --> 00:43:24.990 align:start position:0% kind of a use case for this<00:43:23.319> yeah<00:43:23.440> you<00:43:23.559> can<00:43:23.760> use<00:43:24.000> static<00:43:24.400> content 00:43:24.990 --> 00:43:25.000 align:start position:0% this yeah you can use static content 00:43:25.000 --> 00:43:27.990 align:start position:0% this yeah you can use static content there<00:43:26.000> actually<00:43:26.319> it<00:43:26.440> would<00:43:26.599> be<00:43:27.280> like<00:43:27.480> cou 00:43:27.990 --> 00:43:28.000 align:start position:0% there actually it would be like cou 00:43:28.000 --> 00:43:30.109 align:start position:0% there actually it would be like cou gabes<00:43:28.640> yeah<00:43:29.040> yeah<00:43:29.160> sure<00:43:29.559> but<00:43:29.720> that's<00:43:29.880> also 00:43:30.109 --> 00:43:30.119 align:start position:0% gabes yeah yeah sure but that's also 00:43:30.119 --> 00:43:32.670 align:start position:0% gabes yeah yeah sure but that's also kind<00:43:30.240> of<00:43:30.480> spam<00:43:31.480> kind<00:43:31.640> of<00:43:31.880> but<00:43:32.040> I<00:43:32.200> thought<00:43:32.520> for 00:43:32.670 --> 00:43:32.680 align:start position:0% kind of spam kind of but I thought for 00:43:32.680 --> 00:43:34.270 align:start position:0% kind of spam kind of but I thought for me<00:43:32.839> at<00:43:32.960> least<00:43:33.160> so<00:43:33.359> they<00:43:33.480> can<00:43:33.599> drop<00:43:33.800> it<00:43:33.920> out<00:43:34.119> from 00:43:34.270 --> 00:43:34.280 align:start position:0% me at least so they can drop it out from 00:43:34.280 --> 00:43:35.210 align:start position:0% me at least so they can drop it out from time<00:43:34.440> to<00:43:34.640> time<00:43:34.880> but 00:43:35.210 --> 00:43:35.220 align:start position:0% time to time but 00:43:35.220 --> 00:43:39.910 align:start position:0% time to time but [Music] 00:43:39.910 --> 00:43:39.920 align:start position:0% 00:43:39.920 --> 00:43:42.990 align:start position:0% it's<00:43:40.920> yeah<00:43:41.079> it's<00:43:41.319> it's<00:43:41.599> it's<00:43:41.839> it's<00:43:42.040> possible 00:43:42.990 --> 00:43:43.000 align:start position:0% it's yeah it's it's it's it's possible 00:43:43.000 --> 00:43:46.670 align:start position:0% it's yeah it's it's it's it's possible it<00:43:43.559> is<00:43:44.559> actually<00:43:44.960> I'm<00:43:45.160> thinking<00:43:45.680> about<00:43:46.200> adding 00:43:46.670 --> 00:43:46.680 align:start position:0% it is actually I'm thinking about adding 00:43:46.680 --> 00:43:49.910 align:start position:0% it is actually I'm thinking about adding a<00:43:47.000> HTTP<00:43:47.760> interface<00:43:48.400> just<00:43:48.559> for<00:43:48.760> fun<00:43:49.119> that<00:43:49.680> when 00:43:49.910 --> 00:43:49.920 align:start position:0% a HTTP interface just for fun that when 00:43:49.920 --> 00:43:53.990 align:start position:0% a HTTP interface just for fun that when when<00:43:50.040> you<00:43:50.200> enter<00:43:50.839> a<00:43:51.440> hash<00:43:51.920> in<00:43:52.119> the<00:43:52.760> in<00:43:52.920> the<00:43:53.079> URL 00:43:53.990 --> 00:43:54.000 align:start position:0% when you enter a hash in the in the URL 00:43:54.000 --> 00:43:56.150 align:start position:0% when you enter a hash in the in the URL then<00:43:54.160> it<00:43:54.280> will<00:43:54.520> collect<00:43:55.079> the<00:43:55.400> corresponding 00:43:56.150 --> 00:43:56.160 align:start position:0% then it will collect the corresponding 00:43:56.160 --> 00:43:59.589 align:start position:0% then it will collect the corresponding PES<00:43:56.599> and<00:43:57.280> you<00:43:57.720> know 00:43:59.589 --> 00:43:59.599 align:start position:0% PES and you know 00:43:59.599 --> 00:44:03.430 align:start position:0% PES and you know uh<00:44:00.599> push<00:44:00.880> out<00:44:01.280> the<00:44:01.520> the<00:44:01.680> entire 00:44:03.430 --> 00:44:03.440 align:start position:0% uh push out the the entire 00:44:03.440 --> 00:44:05.870 align:start position:0% uh push out the the entire content<00:44:04.440> one<00:44:04.640> idea<00:44:04.880> for<00:44:05.280> but<00:44:05.400> only<00:44:05.559> for<00:44:05.720> the 00:44:05.870 --> 00:44:05.880 align:start position:0% content one idea for but only for the 00:44:05.880 --> 00:44:07.750 align:start position:0% content one idea for but only for the local<00:44:06.160> node<00:44:06.480> so<00:44:06.640> it's<00:44:06.800> only<00:44:07.160> no<00:44:07.319> no<00:44:07.440> no<00:44:07.599> it's 00:44:07.750 --> 00:44:07.760 align:start position:0% local node so it's only no no no it's 00:44:07.760 --> 00:44:10.829 align:start position:0% local node so it's only no no no it's only<00:44:08.400> accessible<00:44:09.400> from 00:44:10.829 --> 00:44:10.839 align:start position:0% only accessible from 00:44:10.839 --> 00:44:13.990 align:start position:0% only accessible from 12701<00:44:11.839> it's<00:44:12.000> not<00:44:12.280> accessible<00:44:12.680> from<00:44:12.839> the<00:44:12.960> other 00:44:13.990 --> 00:44:14.000 align:start position:0% 12701 it's not accessible from the other 00:44:14.000 --> 00:44:16.430 align:start position:0% 12701 it's not accessible from the other side<00:44:15.000> so<00:44:15.240> one<00:44:15.359> idea<00:44:15.599> for<00:44:15.720> span<00:44:16.000> prevention<00:44:16.319> is 00:44:16.430 --> 00:44:16.440 align:start position:0% side so one idea for span prevention is 00:44:16.440 --> 00:44:18.309 align:start position:0% side so one idea for span prevention is we<00:44:16.599> just<00:44:16.680> use<00:44:16.880> Pro<00:44:17.200> work<00:44:17.720> and<00:44:17.920> keep<00:44:18.119> the 00:44:18.309 --> 00:44:18.319 align:start position:0% we just use Pro work and keep the 00:44:18.319 --> 00:44:19.990 align:start position:0% we just use Pro work and keep the highest<00:44:18.880> work<00:44:19.079> stuff<00:44:19.240> in<00:44:19.359> the<00:44:19.480> table<00:44:19.760> and 00:44:19.990 --> 00:44:20.000 align:start position:0% highest work stuff in the table and 00:44:20.000 --> 00:44:22.990 align:start position:0% highest work stuff in the table and Target<00:44:20.440> kind<00:44:20.559> of<00:44:20.880> like<00:44:21.240> not<00:44:21.880> overflowing<00:44:22.880> and 00:44:22.990 --> 00:44:23.000 align:start position:0% Target kind of like not overflowing and 00:44:23.000 --> 00:44:24.430 align:start position:0% Target kind of like not overflowing and that<00:44:23.160> way<00:44:23.319> blocks<00:44:23.599> will<00:44:23.839> always<00:44:24.040> stay<00:44:24.240> in 00:44:24.430 --> 00:44:24.440 align:start position:0% that way blocks will always stay in 00:44:24.440 --> 00:44:25.990 align:start position:0% that way blocks will always stay in there<00:44:25.040> because<00:44:25.200> they<00:44:25.359> always<00:44:25.559> have<00:44:25.640> a<00:44:25.760> good 00:44:25.990 --> 00:44:26.000 align:start position:0% there because they always have a good 00:44:26.000 --> 00:44:28.549 align:start position:0% there because they always have a good work<00:44:26.559> of<00:44:26.680> course<00:44:27.480> and<00:44:27.720> transaction<00:44:28.200> receipts 00:44:28.549 --> 00:44:28.559 align:start position:0% work of course and transaction receipts 00:44:28.559 --> 00:44:31.549 align:start position:0% work of course and transaction receipts and<00:44:28.640> so<00:44:28.760> on<00:44:28.920> will<00:44:29.119> always<00:44:29.319> be<00:44:29.520> hosted<00:44:29.960> by<00:44:30.559> AR 00:44:31.549 --> 00:44:31.559 align:start position:0% and so on will always be hosted by AR 00:44:31.559 --> 00:44:32.630 align:start position:0% and so on will always be hosted by AR because<00:44:31.760> they<00:44:31.880> will<00:44:32.079> they<00:44:32.160> will<00:44:32.240> store<00:44:32.520> the 00:44:32.630 --> 00:44:32.640 align:start position:0% because they will they will store the 00:44:32.640 --> 00:44:34.390 align:start position:0% because they will they will store the data<00:44:32.960> anyway<00:44:33.359> because<00:44:33.559> they<00:44:33.720> use 00:44:34.390 --> 00:44:34.400 align:start position:0% data anyway because they use 00:44:34.400 --> 00:44:37.870 align:start position:0% data anyway because they use it<00:44:35.400> that's<00:44:35.559> kind<00:44:35.640> of<00:44:35.760> the<00:44:36.079> definition 00:44:37.870 --> 00:44:37.880 align:start position:0% it that's kind of the definition 00:44:37.880 --> 00:44:40.030 align:start position:0% it that's kind of the definition yeah 00:44:40.030 --> 00:44:40.040 align:start position:0% yeah 00:44:40.040 --> 00:44:42.630 align:start position:0% yeah they<00:44:41.040> well<00:44:41.240> if<00:44:41.400> the<00:44:41.520> proof<00:44:41.760> of<00:44:41.960> work<00:44:42.200> is<00:44:42.359> such 00:44:42.630 --> 00:44:42.640 align:start position:0% they well if the proof of work is such 00:44:42.640 --> 00:44:45.030 align:start position:0% they well if the proof of work is such that<00:44:42.760> they<00:44:42.880> need<00:44:43.079> to<00:44:43.240> look<00:44:43.440> it<00:44:43.599> up<00:44:44.400> so<00:44:44.760> if<00:44:44.880> a 00:44:45.030 --> 00:44:45.040 align:start position:0% that they need to look it up so if a 00:44:45.040 --> 00:44:48.190 align:start position:0% that they need to look it up so if a Hashimoto<00:44:45.760> style<00:44:46.520> in<00:44:46.720> Hashimoto<00:44:47.480> style<00:44:47.960> proof 00:44:48.190 --> 00:44:48.200 align:start position:0% Hashimoto style in Hashimoto style proof 00:44:48.200 --> 00:44:50.990 align:start position:0% Hashimoto style in Hashimoto style proof of<00:44:48.400> work<00:44:48.800> you<00:44:49.280> you<00:44:49.400> need 00:44:50.990 --> 00:44:51.000 align:start position:0% of work you you need 00:44:51.000 --> 00:44:54.030 align:start position:0% of work you you need to<00:44:52.000> so<00:44:52.319> full<00:44:52.680> yeah<00:44:53.000> there's<00:44:53.160> a<00:44:53.319> bit<00:44:53.440> of<00:44:53.599> weird 00:44:54.030 --> 00:44:54.040 align:start position:0% to so full yeah there's a bit of weird 00:44:54.040 --> 00:44:57.069 align:start position:0% to so full yeah there's a bit of weird so<00:44:54.240> there's<00:44:55.000> full<00:44:55.319> nodes<00:44:55.880> which<00:44:56.480> you<00:44:56.599> know 00:44:57.069 --> 00:44:57.079 align:start position:0% so there's full nodes which you know 00:44:57.079 --> 00:44:59.349 align:start position:0% so there's full nodes which you know which<00:44:57.280> keep<00:44:57.640> this<00:44:57.880> stuff<00:44:58.119> for<00:44:58.280> the<00:44:58.440> last<00:44:58.880> end 00:44:59.349 --> 00:44:59.359 align:start position:0% which keep this stuff for the last end 00:44:59.359 --> 00:45:01.670 align:start position:0% which keep this stuff for the last end blocks<00:45:00.359> there's<00:45:00.640> super<00:45:01.000> light<00:45:01.200> nodes<00:45:01.559> that 00:45:01.670 --> 00:45:01.680 align:start position:0% blocks there's super light nodes that 00:45:01.680 --> 00:45:03.069 align:start position:0% blocks there's super light nodes that don't<00:45:01.880> keep<00:45:02.160> anything<00:45:02.599> really<00:45:02.880> and<00:45:02.960> then 00:45:03.069 --> 00:45:03.079 align:start position:0% don't keep anything really and then 00:45:03.079 --> 00:45:04.470 align:start position:0% don't keep anything really and then there's<00:45:03.280> archive<00:45:03.680> nodes<00:45:04.000> that<00:45:04.160> keep 00:45:04.470 --> 00:45:04.480 align:start position:0% there's archive nodes that keep 00:45:04.480 --> 00:45:05.990 align:start position:0% there's archive nodes that keep everything<00:45:05.200> and<00:45:05.319> the<00:45:05.440> idea<00:45:05.680> is<00:45:05.760> that<00:45:05.880> the 00:45:05.990 --> 00:45:06.000 align:start position:0% everything and the idea is that the 00:45:06.000 --> 00:45:07.710 align:start position:0% everything and the idea is that the foundation<00:45:06.440> runs<00:45:06.680> a<00:45:06.800> few<00:45:06.960> archive<00:45:07.319> nodes<00:45:07.559> and 00:45:07.710 --> 00:45:07.720 align:start position:0% foundation runs a few archive nodes and 00:45:07.720 --> 00:45:09.750 align:start position:0% foundation runs a few archive nodes and maybe<00:45:07.920> some<00:45:08.720> but<00:45:08.839> actually<00:45:09.240> with<00:45:09.480> this<00:45:09.640> you 00:45:09.750 --> 00:45:09.760 align:start position:0% maybe some but actually with this you 00:45:09.760 --> 00:45:12.309 align:start position:0% maybe some but actually with this you don't<00:45:10.040> even<00:45:10.240> need<00:45:10.520> archive<00:45:11.000> nodes<00:45:12.000> because 00:45:12.309 --> 00:45:12.319 align:start position:0% don't even need archive nodes because 00:45:12.319 --> 00:45:13.510 align:start position:0% don't even need archive nodes because with<00:45:12.520> this<00:45:12.680> in 00:45:13.510 --> 00:45:13.520 align:start position:0% with this in 00:45:13.520 --> 00:45:17.190 align:start position:0% with this in place<00:45:14.520> uh<00:45:15.400> you<00:45:15.599> you<00:45:15.720> have<00:45:15.880> a<00:45:16.079> common 00:45:17.190 --> 00:45:17.200 align:start position:0% place uh you you have a common 00:45:17.200 --> 00:45:20.549 align:start position:0% place uh you you have a common archive<00:45:18.200> and<00:45:18.480> as<00:45:18.640> long<00:45:18.880> as<00:45:19.040> you<00:45:19.280> keep<00:45:20.200> keep 00:45:20.549 --> 00:45:20.559 align:start position:0% archive and as long as you keep keep 00:45:20.559 --> 00:45:23.790 align:start position:0% archive and as long as you keep keep randomly<00:45:21.319> checking<00:45:21.720> the<00:45:21.960> past<00:45:22.880> it<00:45:23.000> will<00:45:23.280> stay 00:45:23.790 --> 00:45:23.800 align:start position:0% randomly checking the past it will stay 00:45:23.800 --> 00:45:25.630 align:start position:0% randomly checking the past it will stay up<00:45:24.000> to<00:45:24.200> dat<00:45:24.559> and<00:45:24.760> it<00:45:24.880> will<00:45:25.040> be<00:45:25.240> fairly 00:45:25.630 --> 00:45:25.640 align:start position:0% up to dat and it will be fairly 00:45:25.640 --> 00:45:29.670 align:start position:0% up to dat and it will be fairly distributed 00:45:29.670 --> 00:45:29.680 align:start position:0% 00:45:29.680 --> 00:45:31.990 align:start position:0% and<00:45:29.839> you<00:45:29.960> know<00:45:30.559> this<00:45:30.960> this<00:45:31.160> kind<00:45:31.319> of<00:45:31.520> proof<00:45:31.800> of 00:45:31.990 --> 00:45:32.000 align:start position:0% and you know this this kind of proof of 00:45:32.000 --> 00:45:33.990 align:start position:0% and you know this this kind of proof of work<00:45:32.319> can<00:45:32.520> be<00:45:32.800> actually<00:45:33.119> a<00:45:33.280> contract<00:45:33.760> so<00:45:33.880> you 00:45:33.990 --> 00:45:34.000 align:start position:0% work can be actually a contract so you 00:45:34.000 --> 00:45:37.910 align:start position:0% work can be actually a contract so you can<00:45:34.240> actually<00:45:34.559> offer<00:45:35.000> ether<00:45:35.760> in<00:45:36.040> exchange<00:45:36.920> for 00:45:37.910 --> 00:45:37.920 align:start position:0% can actually offer ether in exchange for 00:45:37.920 --> 00:45:40.230 align:start position:0% can actually offer ether in exchange for for<00:45:38.359> for<00:45:38.559> checking<00:45:39.000> the<00:45:39.160> thing 00:45:40.230 --> 00:45:40.240 align:start position:0% for for checking the thing 00:45:40.240 --> 00:45:43.630 align:start position:0% for for checking the thing for<00:45:41.240> for<00:45:41.480> for<00:45:41.720> provid<00:45:42.240> for<00:45:42.960> making<00:45:43.280> spot 00:45:43.630 --> 00:45:43.640 align:start position:0% for for for provid for making spot 00:45:43.640 --> 00:45:46.230 align:start position:0% for for for provid for making spot checks<00:45:44.640> so<00:45:45.000> it<00:45:45.160> can<00:45:45.319> be<00:45:45.480> done<00:45:45.720> on<00:45:45.920> top<00:45:46.079> of 00:45:46.230 --> 00:45:46.240 align:start position:0% checks so it can be done on top of 00:45:46.240 --> 00:45:49.230 align:start position:0% checks so it can be done on top of ethereum<00:45:46.839> that<00:45:47.040> you<00:45:47.520> here's<00:45:47.720> a<00:45:47.960> contract<00:45:48.960> that 00:45:49.230 --> 00:45:49.240 align:start position:0% ethereum that you here's a contract that 00:45:49.240 --> 00:45:51.589 align:start position:0% ethereum that you here's a contract that if<00:45:49.440> you<00:45:49.920> if<00:45:50.040> you<00:45:50.200> maintain<00:45:50.680> if<00:45:50.800> you<00:45:51.000> know<00:45:51.200> you 00:45:51.589 --> 00:45:51.599 align:start position:0% if you if you maintain if you know you 00:45:51.599 --> 00:45:53.109 align:start position:0% if you if you maintain if you know you you<00:45:51.720> sweep<00:45:52.079> around<00:45:52.319> the<00:45:52.480> archives<00:45:52.960> then 00:45:53.109 --> 00:45:53.119 align:start position:0% you sweep around the archives then 00:45:53.119 --> 00:45:54.790 align:start position:0% you sweep around the archives then you're<00:45:53.280> going<00:45:53.359> to<00:45:53.520> get<00:45:53.720> paid<00:45:54.280> and<00:45:54.480> that's<00:45:54.640> it 00:45:54.790 --> 00:45:54.800 align:start position:0% you're going to get paid and that's it 00:45:54.800 --> 00:46:00.870 align:start position:0% you're going to get paid and that's it you<00:45:54.880> don't<00:45:55.119> even<00:45:55.319> need<00:45:55.520> full<00:45:55.760> archive<00:45:56.160> nodes 00:46:00.870 --> 00:46:00.880 align:start position:0% 00:46:00.880 --> 00:46:03.069 align:start position:0% what's<00:46:01.079> the<00:46:01.240> behavior<00:46:01.839> if<00:46:02.040> you<00:46:02.520> if<00:46:02.640> you<00:46:02.800> have 00:46:03.069 --> 00:46:03.079 align:start position:0% what's the behavior if you if you have 00:46:03.079 --> 00:46:05.190 align:start position:0% what's the behavior if you if you have like<00:46:03.280> two 00:46:05.190 --> 00:46:05.200 align:start position:0% like two 00:46:05.200 --> 00:46:07.990 align:start position:0% like two concurrent<00:46:06.200> uh<00:46:06.440> request<00:46:07.000> for<00:46:07.319> for<00:46:07.559> writing 00:46:07.990 --> 00:46:08.000 align:start position:0% concurrent uh request for for writing 00:46:08.000 --> 00:46:10.390 align:start position:0% concurrent uh request for for writing the<00:46:08.160> same<00:46:08.520> Ash<00:46:09.319> but<00:46:09.440> you<00:46:09.559> will<00:46:09.760> write<00:46:10.000> the<00:46:10.160> same 00:46:10.390 --> 00:46:10.400 align:start position:0% the same Ash but you will write the same 00:46:10.400 --> 00:46:13.150 align:start position:0% the same Ash but you will write the same thing<00:46:10.680> there<00:46:10.960> that's<00:46:11.160> the<00:46:11.640> point<00:46:12.640> that<00:46:12.880> the 00:46:13.150 --> 00:46:13.160 align:start position:0% thing there that's the point that the 00:46:13.160 --> 00:46:16.109 align:start position:0% thing there that's the point that the here<00:46:13.520> the<00:46:13.800> the<00:46:14.079> the<00:46:14.280> value<00:46:14.960> sorry<00:46:15.359> okay<00:46:15.920> but 00:46:16.109 --> 00:46:16.119 align:start position:0% here the the the value sorry okay but 00:46:16.119 --> 00:46:18.670 align:start position:0% here the the the value sorry okay but what<00:46:16.280> if<00:46:16.559> what<00:46:16.720> if<00:46:16.920> it's<00:46:17.119> a<00:46:17.319> mutable<00:46:17.960> time<00:46:18.559> if 00:46:18.670 --> 00:46:18.680 align:start position:0% what if what if it's a mutable time if 00:46:18.680 --> 00:46:21.549 align:start position:0% what if what if it's a mutable time if it's<00:46:18.880> mutable<00:46:19.400> it's<00:46:19.520> a<00:46:19.680> lot<00:46:19.880> harder<00:46:20.839> okay<00:46:21.359> it's 00:46:21.549 --> 00:46:21.559 align:start position:0% it's mutable it's a lot harder okay it's 00:46:21.559 --> 00:46:23.549 align:start position:0% it's mutable it's a lot harder okay it's not<00:46:22.119> it's<00:46:22.319> it's<00:46:22.520> it's<00:46:22.880> it's<00:46:23.000> not<00:46:23.160> designed<00:46:23.480> to 00:46:23.549 --> 00:46:23.559 align:start position:0% not it's it's it's it's not designed to 00:46:23.559 --> 00:46:28.470 align:start position:0% not it's it's it's it's not designed to be<00:46:23.720> mutable 00:46:28.470 --> 00:46:28.480 align:start position:0% 00:46:28.480 --> 00:46:30.430 align:start position:0% so<00:46:28.960> we<00:46:29.359> going<00:46:29.440> to 00:46:30.430 --> 00:46:30.440 align:start position:0% so we going to 00:46:30.440 --> 00:46:33.349 align:start position:0% so we going to use<00:46:31.440> we<00:46:31.599> might<00:46:31.960> but<00:46:32.160> it<00:46:32.280> will<00:46:32.520> be<00:46:32.800> a<00:46:33.119> thick 00:46:33.349 --> 00:46:33.359 align:start position:0% use we might but it will be a thick 00:46:33.359 --> 00:46:34.990 align:start position:0% use we might but it will be a thick layer<00:46:33.720> on<00:46:33.920> top 00:46:34.990 --> 00:46:35.000 align:start position:0% layer on top 00:46:35.000 --> 00:46:37.390 align:start position:0% layer on top like<00:46:36.000> that's<00:46:36.160> a<00:46:36.280> lot<00:46:36.440> more<00:46:36.640> work<00:46:36.920> than<00:46:37.040> an 00:46:37.390 --> 00:46:37.400 align:start position:0% like that's a lot more work than an 00:46:37.400 --> 00:46:40.430 align:start position:0% like that's a lot more work than an immutable 00:46:40.430 --> 00:46:40.440 align:start position:0% 00:46:40.440 --> 00:46:43.270 align:start position:0% one<00:46:41.440> and<00:46:41.680> actually<00:46:41.960> for<00:46:42.119> a<00:46:42.319> mutable<00:46:42.720> one<00:46:43.200> I 00:46:43.270 --> 00:46:43.280 align:start position:0% one and actually for a mutable one I 00:46:43.280 --> 00:46:46.309 align:start position:0% one and actually for a mutable one I would<00:46:43.640> probably<00:46:44.160> just<00:46:44.400> use<00:46:45.079> uh<00:46:45.680> bitor<00:46:46.079> and 00:46:46.309 --> 00:46:46.319 align:start position:0% would probably just use uh bitor and 00:46:46.319 --> 00:46:49.030 align:start position:0% would probably just use uh bitor and cadamia<00:46:47.160> because<00:46:48.160> you<00:46:48.280> know<00:46:48.440> it's<00:46:48.640> already 00:46:49.030 --> 00:46:49.040 align:start position:0% cadamia because you know it's already 00:46:49.040 --> 00:46:50.390 align:start position:0% cadamia because you know it's already there<00:46:49.240> and<00:46:49.400> it's<00:46:49.559> mutable<00:46:50.000> and<00:46:50.160> they<00:46:50.280> have 00:46:50.390 --> 00:46:50.400 align:start position:0% there and it's mutable and they have 00:46:50.400 --> 00:46:55.829 align:start position:0% there and it's mutable and they have solved<00:46:50.720> all<00:46:50.880> the 00:46:55.829 --> 00:46:55.839 align:start position:0% 00:46:55.839 --> 00:46:59.880 align:start position:0% problems<00:46:56.880> e