WEBVTT Kind: captions Language: en 00:00:05.070 --> 00:00:18.470 align:start position:0% [Music] 00:00:18.470 --> 00:00:18.480 align:start position:0% 00:00:18.480 --> 00:00:23.710 align:start position:0% okay<00:00:19.680> um<00:00:20.680> so<00:00:20.840> this<00:00:20.960> is<00:00:21.039> a<00:00:21.240> quick<00:00:21.920> um<00:00:22.400> talk<00:00:23.240> and 00:00:23.710 --> 00:00:23.720 align:start position:0% okay um so this is a quick um talk and 00:00:23.720 --> 00:00:27.910 align:start position:0% okay um so this is a quick um talk and hopefully<00:00:24.400> a<00:00:24.680> demo<00:00:25.000> at<00:00:25.080> the<00:00:25.240> end<00:00:26.240> um<00:00:26.400> on 00:00:27.910 --> 00:00:27.920 align:start position:0% hopefully a demo at the end um on 00:00:27.920 --> 00:00:31.749 align:start position:0% hopefully a demo at the end um on whisper<00:00:28.920> hands<00:00:29.119> up<00:00:29.279> if<00:00:29.400> you've<00:00:29.560> heard<00:00:29.679> of<00:00:29.759> whis 00:00:31.749 --> 00:00:31.759 align:start position:0% whisper hands up if you've heard of whis 00:00:31.759 --> 00:00:34.110 align:start position:0% whisper hands up if you've heard of whis hey<00:00:32.239> almost 00:00:34.110 --> 00:00:34.120 align:start position:0% hey almost 00:00:34.120 --> 00:00:35.910 align:start position:0% hey almost everybody 00:00:35.910 --> 00:00:35.920 align:start position:0% everybody 00:00:35.920 --> 00:00:38.590 align:start position:0% everybody um<00:00:36.920> so<00:00:37.160> the<00:00:37.280> first<00:00:37.520> question<00:00:37.760> to<00:00:38.000> answer<00:00:38.320> is 00:00:38.590 --> 00:00:38.600 align:start position:0% um so the first question to answer is 00:00:38.600 --> 00:00:41.029 align:start position:0% um so the first question to answer is why<00:00:39.000> why<00:00:39.320> have<00:00:39.719> whisper<00:00:40.200> at<00:00:40.360> all<00:00:40.719> when<00:00:40.840> we've 00:00:41.029 --> 00:00:41.039 align:start position:0% why why have whisper at all when we've 00:00:41.039 --> 00:00:43.069 align:start position:0% why why have whisper at all when we've got<00:00:41.239> the<00:00:41.360> blockchain<00:00:42.320> um<00:00:42.480> the<00:00:42.600> blockchain 00:00:43.069 --> 00:00:43.079 align:start position:0% got the blockchain um the blockchain 00:00:43.079 --> 00:00:45.229 align:start position:0% got the blockchain um the blockchain allows<00:00:43.600> people<00:00:43.800> to<00:00:44.000> communicate<00:00:44.680> we<00:00:44.800> can<00:00:45.039> just 00:00:45.229 --> 00:00:45.239 align:start position:0% allows people to communicate we can just 00:00:45.239 --> 00:00:46.910 align:start position:0% allows people to communicate we can just make<00:00:45.520> contracts<00:00:46.320> um<00:00:46.440> we<00:00:46.559> can<00:00:46.680> send 00:00:46.910 --> 00:00:46.920 align:start position:0% make contracts um we can send 00:00:46.920 --> 00:00:48.990 align:start position:0% make contracts um we can send transactions<00:00:47.440> to<00:00:47.680> contract<00:00:48.600> they<00:00:48.719> can<00:00:48.840> be 00:00:48.990 --> 00:00:49.000 align:start position:0% transactions to contract they can be 00:00:49.000 --> 00:00:50.470 align:start position:0% transactions to contract they can be like 00:00:50.470 --> 00:00:50.480 align:start position:0% like 00:00:50.480 --> 00:00:55.270 align:start position:0% like messages<00:00:51.960> um<00:00:52.960> the<00:00:53.160> main<00:00:54.160> obvious<00:00:54.600> answer<00:00:55.039> is 00:00:55.270 --> 00:00:55.280 align:start position:0% messages um the main obvious answer is 00:00:55.280 --> 00:00:57.590 align:start position:0% messages um the main obvious answer is that<00:00:55.680> it's<00:00:55.879> really<00:00:56.199> expensive<00:00:57.079> if<00:00:57.199> you<00:00:57.359> use 00:00:57.590 --> 00:00:57.600 align:start position:0% that it's really expensive if you use 00:00:57.600 --> 00:00:59.670 align:start position:0% that it's really expensive if you use the<00:00:57.760> blockchain<00:00:58.320> to<00:00:58.879> communicate<00:00:59.399> with<00:00:59.559> each 00:00:59.670 --> 00:00:59.680 align:start position:0% the blockchain to communicate with each 00:00:59.680 --> 00:01:01.990 align:start position:0% the blockchain to communicate with each other<00:01:00.120> then<00:01:00.320> you're<00:01:00.559> paying<00:01:01.480> essentially<00:01:01.879> to 00:01:01.990 --> 00:01:02.000 align:start position:0% other then you're paying essentially to 00:01:02.000 --> 00:01:04.149 align:start position:0% other then you're paying essentially to have<00:01:02.199> everybody<00:01:02.600> else<00:01:03.199> know<00:01:03.519> about<00:01:03.879> and 00:01:04.149 --> 00:01:04.159 align:start position:0% have everybody else know about and 00:01:04.159 --> 00:01:06.630 align:start position:0% have everybody else know about and archive<00:01:05.040> all<00:01:05.199> of<00:01:05.400> those 00:01:06.630 --> 00:01:06.640 align:start position:0% archive all of those 00:01:06.640 --> 00:01:09.870 align:start position:0% archive all of those Communications<00:01:07.640> Min<00:01:08.159> answers<00:01:08.520> also<00:01:08.880> include 00:01:09.870 --> 00:01:09.880 align:start position:0% Communications Min answers also include 00:01:09.880 --> 00:01:11.630 align:start position:0% Communications Min answers also include hey<00:01:10.080> it's<00:01:10.280> open<00:01:10.680> and<00:01:10.840> maybe<00:01:11.119> we<00:01:11.240> don't<00:01:11.400> want 00:01:11.630 --> 00:01:11.640 align:start position:0% hey it's open and maybe we don't want 00:01:11.640 --> 00:01:12.990 align:start position:0% hey it's open and maybe we don't want everybody<00:01:12.000> else<00:01:12.200> to<00:01:12.320> know<00:01:12.520> about<00:01:12.720> what<00:01:12.840> we're 00:01:12.990 --> 00:01:13.000 align:start position:0% everybody else to know about what we're 00:01:13.000 --> 00:01:15.149 align:start position:0% everybody else to know about what we're saying<00:01:13.560> but<00:01:13.720> of<00:01:13.840> course<00:01:14.040> that<00:01:14.159> can<00:01:14.320> be<00:01:15.000> um 00:01:15.149 --> 00:01:15.159 align:start position:0% saying but of course that can be um 00:01:15.159 --> 00:01:17.270 align:start position:0% saying but of course that can be um achieved<00:01:15.520> with 00:01:17.270 --> 00:01:17.280 align:start position:0% achieved with 00:01:17.280 --> 00:01:19.390 align:start position:0% achieved with encryption 00:01:19.390 --> 00:01:19.400 align:start position:0% encryption 00:01:19.400 --> 00:01:21.350 align:start position:0% encryption so<00:01:20.400> in 00:01:21.350 --> 00:01:21.360 align:start position:0% so in 00:01:21.360 --> 00:01:24.550 align:start position:0% so in essence<00:01:22.360> there<00:01:22.520> are<00:01:22.880> there<00:01:23.079> are<00:01:23.520> aspects<00:01:24.159> of 00:01:24.550 --> 00:01:24.560 align:start position:0% essence there are there are aspects of 00:01:24.560 --> 00:01:26.550 align:start position:0% essence there are there are aspects of decentralized<00:01:25.240> application<00:01:25.640> building<00:01:26.280> where 00:01:26.550 --> 00:01:26.560 align:start position:0% decentralized application building where 00:01:26.560 --> 00:01:28.310 align:start position:0% decentralized application building where we<00:01:26.720> don't<00:01:26.920> need<00:01:27.200> consensus<00:01:27.799> we<00:01:27.880> don't<00:01:28.079> want 00:01:28.310 --> 00:01:28.320 align:start position:0% we don't need consensus we don't want 00:01:28.320 --> 00:01:30.109 align:start position:0% we don't need consensus we don't want consensus<00:01:29.079> and<00:01:29.200> what<00:01:29.320> we<00:01:29.479> actually<00:01:29.680> want<00:01:30.000> to 00:01:30.109 --> 00:01:30.119 align:start position:0% consensus and what we actually want to 00:01:30.119 --> 00:01:36.590 align:start position:0% consensus and what we actually want to do<00:01:30.360> is<00:01:30.840> is<00:01:31.000> simply<00:01:31.360> do<00:01:32.119> peer-to-peer<00:01:32.560> um 00:01:36.590 --> 00:01:36.600 align:start position:0% 00:01:36.600 --> 00:01:38.830 align:start position:0% communication 00:01:38.830 --> 00:01:38.840 align:start position:0% communication 00:01:38.840 --> 00:01:41.590 align:start position:0% communication so<00:01:39.840> within 00:01:41.590 --> 00:01:41.600 align:start position:0% so within 00:01:41.600 --> 00:01:44.030 align:start position:0% so within the<00:01:42.600> the<00:01:42.759> framework<00:01:43.280> of<00:01:43.399> doing<00:01:43.680> massively 00:01:44.030 --> 00:01:44.040 align:start position:0% the the framework of doing massively 00:01:44.040 --> 00:01:46.749 align:start position:0% the the framework of doing massively multi-user<00:01:45.079> applications<00:01:46.079> which<00:01:46.360> when<00:01:46.479> I<00:01:46.560> say 00:01:46.749 --> 00:01:46.759 align:start position:0% multi-user applications which when I say 00:01:46.759 --> 00:01:48.310 align:start position:0% multi-user applications which when I say massively<00:01:47.119> multi-user<00:01:47.719> applications 00:01:48.310 --> 00:01:48.320 align:start position:0% massively multi-user applications 00:01:48.320 --> 00:01:49.670 align:start position:0% massively multi-user applications basically<00:01:48.719> what<00:01:48.840> I'm<00:01:48.960> talking<00:01:49.159> about<00:01:49.320> are<00:01:49.479> web 00:01:49.670 --> 00:01:49.680 align:start position:0% basically what I'm talking about are web 00:01:49.680 --> 00:01:52.230 align:start position:0% basically what I'm talking about are web apps<00:01:50.560> um<00:01:50.719> but<00:01:50.920> also<00:01:51.520> these<00:01:51.759> days 00:01:52.230 --> 00:01:52.240 align:start position:0% apps um but also these days 00:01:52.240 --> 00:01:54.149 align:start position:0% apps um but also these days decentralized<00:01:53.000> applications 00:01:54.149 --> 00:01:54.159 align:start position:0% decentralized applications 00:01:54.159 --> 00:01:58.429 align:start position:0% decentralized applications too<00:01:55.159> we<00:01:55.280> see<00:01:55.560> three<00:01:55.920> main<00:01:56.920> um<00:01:57.320> paradigms<00:01:58.000> for 00:01:58.429 --> 00:01:58.439 align:start position:0% too we see three main um paradigms for 00:01:58.439 --> 00:02:01.389 align:start position:0% too we see three main um paradigms for communication<00:01:59.439> the<00:01:59.560> first<00:01:59.960> this<00:02:00.159> static<00:02:01.000> um 00:02:01.389 --> 00:02:01.399 align:start position:0% communication the first this static um 00:02:01.399 --> 00:02:03.190 align:start position:0% communication the first this static um static<00:02:01.759> publication<00:02:02.399> so<00:02:02.680> where<00:02:02.840> we<00:02:03.079> we 00:02:03.190 --> 00:02:03.200 align:start position:0% static publication so where we we 00:02:03.200 --> 00:02:05.670 align:start position:0% static publication so where we we publish<00:02:03.600> generally<00:02:04.039> quite<00:02:04.200> a<00:02:04.320> lot<00:02:04.479> of<00:02:04.680> data 00:02:05.670 --> 00:02:05.680 align:start position:0% publish generally quite a lot of data 00:02:05.680 --> 00:02:08.669 align:start position:0% publish generally quite a lot of data and<00:02:05.960> it<00:02:06.079> doesn't<00:02:06.399> change<00:02:07.360> it's<00:02:07.920> the<00:02:08.119> assets<00:02:08.479> of 00:02:08.669 --> 00:02:08.679 align:start position:0% and it doesn't change it's the assets of 00:02:08.679 --> 00:02:12.910 align:start position:0% and it doesn't change it's the assets of a<00:02:09.119> of<00:02:09.200> a<00:02:09.399> web<00:02:09.679> page<00:02:10.599> um<00:02:10.840> it's<00:02:11.599> um<00:02:11.959> the<00:02:12.120> text<00:02:12.400> of<00:02:12.520> a 00:02:12.910 --> 00:02:12.920 align:start position:0% a of a web page um it's um the text of a 00:02:12.920 --> 00:02:15.309 align:start position:0% a of a web page um it's um the text of a story<00:02:13.920> um<00:02:14.239> it<00:02:14.360> it<00:02:14.480> sort<00:02:14.680> of<00:02:14.760> goes<00:02:14.959> up<00:02:15.080> there<00:02:15.200> it 00:02:15.309 --> 00:02:15.319 align:start position:0% story um it it sort of goes up there it 00:02:15.319 --> 00:02:17.630 align:start position:0% story um it it sort of goes up there it maybe<00:02:15.560> a<00:02:15.640> movie<00:02:16.160> it<00:02:16.280> goes<00:02:16.440> up<00:02:16.599> there<00:02:17.239> it<00:02:17.319> stays 00:02:17.630 --> 00:02:17.640 align:start position:0% maybe a movie it goes up there it stays 00:02:17.640 --> 00:02:19.630 align:start position:0% maybe a movie it goes up there it stays the<00:02:17.760> same<00:02:18.360> this<00:02:18.480> is<00:02:18.680> stuff<00:02:18.959> that<00:02:19.080> we<00:02:19.319> already 00:02:19.630 --> 00:02:19.640 align:start position:0% the same this is stuff that we already 00:02:19.640 --> 00:02:22.350 align:start position:0% the same this is stuff that we already have<00:02:20.120> pretty<00:02:20.360> decent<00:02:20.720> P2P<00:02:21.200> tools<00:02:21.480> for<00:02:22.080> bit 00:02:22.350 --> 00:02:22.360 align:start position:0% have pretty decent P2P tools for bit 00:02:22.360 --> 00:02:23.509 align:start position:0% have pretty decent P2P tools for bit torrent 00:02:23.509 --> 00:02:23.519 align:start position:0% torrent 00:02:23.519 --> 00:02:28.270 align:start position:0% torrent ipfs<00:02:24.519> um<00:02:25.200> and<00:02:25.480> potentially<00:02:26.480> even<00:02:26.760> like 00:02:28.270 --> 00:02:28.280 align:start position:0% ipfs um and potentially even like 00:02:28.280 --> 00:02:32.670 align:start position:0% ipfs um and potentially even like FTP<00:02:29.280> um<00:02:29.920> we<00:02:30.040> also<00:02:30.760> see<00:02:31.760> obvious<00:02:32.239> sort<00:02:32.440> of 00:02:32.670 --> 00:02:32.680 align:start position:0% FTP um we also see obvious sort of 00:02:32.680 --> 00:02:34.830 align:start position:0% FTP um we also see obvious sort of peer-to-peer<00:02:33.160> um<00:02:33.879> communication<00:02:34.360> strategies 00:02:34.830 --> 00:02:34.840 align:start position:0% peer-to-peer um communication strategies 00:02:34.840 --> 00:02:36.630 align:start position:0% peer-to-peer um communication strategies where<00:02:34.959> it's<00:02:35.160> it's<00:02:35.360> point<00:02:35.560> to<00:02:35.760> point<00:02:36.080> right<00:02:36.440> so 00:02:36.630 --> 00:02:36.640 align:start position:0% where it's it's point to point right so 00:02:36.640 --> 00:02:38.670 align:start position:0% where it's it's point to point right so it's<00:02:36.920> where<00:02:37.319> I<00:02:37.480> want<00:02:37.640> to<00:02:37.879> connect<00:02:38.200> to<00:02:38.440> one 00:02:38.670 --> 00:02:38.680 align:start position:0% it's where I want to connect to one 00:02:38.680 --> 00:02:40.670 align:start position:0% it's where I want to connect to one particular<00:02:39.159> other<00:02:39.480> identity<00:02:39.920> and<00:02:40.040> I<00:02:40.159> want<00:02:40.280> to 00:02:40.670 --> 00:02:40.680 align:start position:0% particular other identity and I want to 00:02:40.680 --> 00:02:42.750 align:start position:0% particular other identity and I want to feed<00:02:41.120> them<00:02:41.360> information<00:02:42.200> so<00:02:42.360> when<00:02:42.480> we<00:02:42.640> think 00:02:42.750 --> 00:02:42.760 align:start position:0% feed them information so when we think 00:02:42.760 --> 00:02:46.070 align:start position:0% feed them information so when we think of<00:02:42.920> this<00:02:43.040> we<00:02:43.200> think<00:02:43.319> of<00:02:43.480> things<00:02:43.760> like<00:02:44.640> Skype<00:02:45.640> um 00:02:46.070 --> 00:02:46.080 align:start position:0% of this we think of things like Skype um 00:02:46.080 --> 00:02:49.509 align:start position:0% of this we think of things like Skype um voice<00:02:46.319> over<00:02:46.599> IP<00:02:47.120> you<00:02:47.239> know<00:02:47.360> real-time 00:02:49.509 --> 00:02:49.519 align:start position:0% voice over IP you know real-time 00:02:49.519 --> 00:02:51.630 align:start position:0% voice over IP you know real-time Communications<00:02:50.519> that's<00:02:50.879> that's<00:02:51.159> generally 00:02:51.630 --> 00:02:51.640 align:start position:0% Communications that's that's generally 00:02:51.640 --> 00:02:53.030 align:start position:0% Communications that's that's generally where<00:02:51.760> we're<00:02:51.959> headed<00:02:52.319> in<00:02:52.480> that<00:02:52.680> direction 00:02:53.030 --> 00:02:53.040 align:start position:0% where we're headed in that direction 00:02:53.040 --> 00:02:55.509 align:start position:0% where we're headed in that direction when<00:02:53.159> it's<00:02:53.519> point<00:02:53.800> to<00:02:54.000> point<00:02:54.879> the<00:02:55.040> final<00:02:55.319> one 00:02:55.509 --> 00:02:55.519 align:start position:0% when it's point to point the final one 00:02:55.519 --> 00:02:57.030 align:start position:0% when it's point to point the final one is<00:02:55.760> is<00:02:55.879> much<00:02:56.040> more<00:02:56.239> interesting<00:02:56.680> than<00:02:56.879> these 00:02:57.030 --> 00:02:57.040 align:start position:0% is is much more interesting than these 00:02:57.040 --> 00:02:59.830 align:start position:0% is is much more interesting than these two<00:02:57.440> the<00:02:57.599> final<00:02:57.879> one<00:02:58.080> is<00:02:58.720> um<00:02:59.239> transient<00:02:59.640> dat 00:02:59.830 --> 00:02:59.840 align:start position:0% two the final one is um transient dat 00:02:59.840 --> 00:03:01.390 align:start position:0% two the final one is um transient dat datagrams<00:03:00.239> is<00:03:00.360> what<00:03:00.440> I've<00:03:00.560> called<00:03:00.840> them<00:03:01.239> but 00:03:01.390 --> 00:03:01.400 align:start position:0% datagrams is what I've called them but 00:03:01.400 --> 00:03:02.910 align:start position:0% datagrams is what I've called them but this<00:03:01.480> is<00:03:01.640> the<00:03:01.800> kind<00:03:01.920> of<00:03:02.080> communication<00:03:02.760> where 00:03:02.910 --> 00:03:02.920 align:start position:0% this is the kind of communication where 00:03:02.920 --> 00:03:04.789 align:start position:0% this is the kind of communication where we<00:03:03.040> want<00:03:03.200> to<00:03:03.560> generally<00:03:04.000> tell<00:03:04.200> a<00:03:04.360> group<00:03:04.640> of 00:03:04.789 --> 00:03:04.799 align:start position:0% we want to generally tell a group of 00:03:04.799 --> 00:03:06.910 align:start position:0% we want to generally tell a group of people<00:03:05.159> something<00:03:05.599> for<00:03:05.879> some<00:03:06.159> limited<00:03:06.640> period 00:03:06.910 --> 00:03:06.920 align:start position:0% people something for some limited period 00:03:06.920 --> 00:03:09.509 align:start position:0% people something for some limited period of<00:03:07.120> time<00:03:08.040> so<00:03:08.640> this<00:03:08.760> is<00:03:08.959> something<00:03:09.239> that<00:03:09.400> we 00:03:09.509 --> 00:03:09.519 align:start position:0% of time so this is something that we 00:03:09.519 --> 00:03:12.350 align:start position:0% of time so this is something that we don't<00:03:09.879> really<00:03:10.319> have<00:03:10.799> a<00:03:11.480> um<00:03:11.680> a<00:03:11.959> proper 00:03:12.350 --> 00:03:12.360 align:start position:0% don't really have a um a proper 00:03:12.360 --> 00:03:14.990 align:start position:0% don't really have a um a proper abstraction<00:03:12.920> for<00:03:13.360> yet<00:03:14.040> uh<00:03:14.200> but<00:03:14.360> you<00:03:14.480> see<00:03:14.720> it 00:03:14.990 --> 00:03:15.000 align:start position:0% abstraction for yet uh but you see it 00:03:15.000 --> 00:03:16.710 align:start position:0% abstraction for yet uh but you see it every<00:03:15.280> day<00:03:15.440> you<00:03:15.560> see<00:03:15.799> it<00:03:16.080> when<00:03:16.200> you<00:03:16.319> use<00:03:16.480> an 00:03:16.710 --> 00:03:16.720 align:start position:0% every day you see it when you use an 00:03:16.720 --> 00:03:18.390 align:start position:0% every day you see it when you use an exchange<00:03:17.400> when<00:03:17.519> you<00:03:17.599> use<00:03:17.760> an<00:03:17.920> exchange<00:03:18.280> you 00:03:18.390 --> 00:03:18.400 align:start position:0% exchange when you use an exchange you 00:03:18.400 --> 00:03:20.550 align:start position:0% exchange when you use an exchange you want<00:03:18.560> to<00:03:18.760> communicate<00:03:19.560> to<00:03:19.760> a<00:03:19.879> bunch<00:03:20.080> of<00:03:20.239> people 00:03:20.550 --> 00:03:20.560 align:start position:0% want to communicate to a bunch of people 00:03:20.560 --> 00:03:22.229 align:start position:0% want to communicate to a bunch of people generally<00:03:20.920> the<00:03:21.080> people<00:03:21.599> the<00:03:21.720> other<00:03:21.920> people<00:03:22.080> on 00:03:22.229 --> 00:03:22.239 align:start position:0% generally the people the other people on 00:03:22.239 --> 00:03:24.110 align:start position:0% generally the people the other people on the<00:03:22.360> exchange<00:03:23.159> or<00:03:23.360> the<00:03:23.440> people<00:03:23.720> at<00:03:23.879> least<00:03:24.040> on 00:03:24.110 --> 00:03:24.120 align:start position:0% the exchange or the people at least on 00:03:24.120 --> 00:03:25.350 align:start position:0% the exchange or the people at least on the<00:03:24.239> exchange<00:03:24.599> that<00:03:24.720> want<00:03:24.879> to<00:03:24.959> change<00:03:25.200> a 00:03:25.350 --> 00:03:25.360 align:start position:0% the exchange that want to change a 00:03:25.360 --> 00:03:28.589 align:start position:0% the exchange that want to change a particular<00:03:25.760> Proto<00:03:26.200> uh<00:03:26.519> particular<00:03:27.519> um 00:03:28.589 --> 00:03:28.599 align:start position:0% particular Proto uh particular um 00:03:28.599 --> 00:03:30.630 align:start position:0% particular Proto uh particular um currency<00:03:29.599> um<00:03:29.879> you<00:03:30.000> want<00:03:30.120> to<00:03:30.200> tell<00:03:30.360> them<00:03:30.480> a 00:03:30.630 --> 00:03:30.640 align:start position:0% currency um you want to tell them a 00:03:30.640 --> 00:03:31.990 align:start position:0% currency um you want to tell them a particular<00:03:31.040> message<00:03:31.519> and<00:03:31.599> you<00:03:31.720> want<00:03:31.840> that 00:03:31.990 --> 00:03:32.000 align:start position:0% particular message and you want that 00:03:32.000 --> 00:03:33.429 align:start position:0% particular message and you want that message<00:03:32.239> to<00:03:32.360> run<00:03:32.599> out<00:03:32.840> after<00:03:33.000> a<00:03:33.120> particular 00:03:33.429 --> 00:03:33.439 align:start position:0% message to run out after a particular 00:03:33.439 --> 00:03:35.670 align:start position:0% message to run out after a particular period<00:03:33.680> of<00:03:33.840> time<00:03:34.120> so<00:03:34.319> transient<00:03:34.799> messages 00:03:35.670 --> 00:03:35.680 align:start position:0% period of time so transient messages 00:03:35.680 --> 00:03:37.350 align:start position:0% period of time so transient messages between<00:03:36.000> groups<00:03:36.280> of<00:03:36.480> people<00:03:36.879> we<00:03:37.000> also<00:03:37.159> see 00:03:37.350 --> 00:03:37.360 align:start position:0% between groups of people we also see 00:03:37.360 --> 00:03:40.509 align:start position:0% between groups of people we also see them<00:03:37.480> in<00:03:37.640> things<00:03:37.879> like<00:03:38.040> Twitter<00:03:38.599> right<00:03:39.599> um<00:03:40.239> I 00:03:40.509 --> 00:03:40.519 align:start position:0% them in things like Twitter right um I 00:03:40.519 --> 00:03:42.229 align:start position:0% them in things like Twitter right um I when<00:03:40.640> I<00:03:40.840> use<00:03:41.000> a<00:03:41.159> hashtag<00:03:41.680> I'm<00:03:41.799> actually<00:03:42.040> trying 00:03:42.229 --> 00:03:42.239 align:start position:0% when I use a hashtag I'm actually trying 00:03:42.239 --> 00:03:43.990 align:start position:0% when I use a hashtag I'm actually trying to<00:03:42.439> reference<00:03:42.840> a<00:03:43.000> group<00:03:43.239> of<00:03:43.400> people<00:03:43.680> who<00:03:43.879> might 00:03:43.990 --> 00:03:44.000 align:start position:0% to reference a group of people who might 00:03:44.000 --> 00:03:45.229 align:start position:0% to reference a group of people who might be<00:03:44.200> interested<00:03:44.560> in<00:03:44.720> something<00:03:45.000> that<00:03:45.120> I'm 00:03:45.229 --> 00:03:45.239 align:start position:0% be interested in something that I'm 00:03:45.239 --> 00:03:46.350 align:start position:0% be interested in something that I'm saying<00:03:45.560> I<00:03:45.640> don't<00:03:45.760> want<00:03:45.840> to<00:03:45.920> reference 00:03:46.350 --> 00:03:46.360 align:start position:0% saying I don't want to reference 00:03:46.360 --> 00:03:48.789 align:start position:0% saying I don't want to reference everybody<00:03:47.120> so<00:03:47.280> it's<00:03:47.439> not<00:03:47.720> like<00:03:48.080> publication 00:03:48.789 --> 00:03:48.799 align:start position:0% everybody so it's not like publication 00:03:48.799 --> 00:03:52.589 align:start position:0% everybody so it's not like publication exactly<00:03:49.720> U<00:03:49.920> but<00:03:50.239> a<00:03:50.400> group<00:03:50.640> of<00:03:50.840> people<00:03:51.840> um<00:03:52.400> and 00:03:52.589 --> 00:03:52.599 align:start position:0% exactly U but a group of people um and 00:03:52.599 --> 00:03:56.550 align:start position:0% exactly U but a group of people um and for<00:03:52.879> a<00:03:53.040> particular 00:03:56.550 --> 00:03:56.560 align:start position:0% 00:03:56.560 --> 00:03:59.789 align:start position:0% period<00:03:57.560> we<00:03:57.680> can<00:03:57.799> see<00:03:58.040> some<00:03:58.159> of<00:03:58.360> the<00:03:58.879> um 00:03:59.789 --> 00:03:59.799 align:start position:0% period we can see some of the um 00:03:59.799 --> 00:04:02.309 align:start position:0% period we can see some of the um patterns<00:04:00.239> within<00:04:01.000> um<00:04:01.519> um<00:04:01.720> these<00:04:01.920> massively 00:04:02.309 --> 00:04:02.319 align:start position:0% patterns within um um these massively 00:04:02.319 --> 00:04:06.270 align:start position:0% patterns within um um these massively multi-user<00:04:03.319> um<00:04:03.920> applications<00:04:04.920> um<00:04:05.920> in<00:04:06.040> terms 00:04:06.270 --> 00:04:06.280 align:start position:0% multi-user um applications um in terms 00:04:06.280 --> 00:04:10.069 align:start position:0% multi-user um applications um in terms of<00:04:06.519> Direction<00:04:07.480> so<00:04:08.480> um<00:04:09.280> when<00:04:09.439> we<00:04:09.599> when<00:04:09.680> we<00:04:09.760> send 00:04:10.069 --> 00:04:10.079 align:start position:0% of Direction so um when we when we send 00:04:10.079 --> 00:04:12.069 align:start position:0% of Direction so um when we when we send email<00:04:10.519> it<00:04:10.640> tends<00:04:10.879> to<00:04:11.040> come<00:04:11.319> from<00:04:11.560> a<00:04:11.720> particular 00:04:12.069 --> 00:04:12.079 align:start position:0% email it tends to come from a particular 00:04:12.079 --> 00:04:13.789 align:start position:0% email it tends to come from a particular identity<00:04:12.480> it<00:04:12.560> tends<00:04:12.760> to<00:04:12.840> go<00:04:13.000> to<00:04:13.239> a<00:04:13.400> particular 00:04:13.789 --> 00:04:13.799 align:start position:0% identity it tends to go to a particular 00:04:13.799 --> 00:04:15.589 align:start position:0% identity it tends to go to a particular identity<00:04:14.480> when<00:04:14.560> we<00:04:14.680> use<00:04:14.879> things<00:04:15.079> like<00:04:15.239> mailing 00:04:15.589 --> 00:04:15.599 align:start position:0% identity when we use things like mailing 00:04:15.599 --> 00:04:17.870 align:start position:0% identity when we use things like mailing lists<00:04:15.959> or<00:04:16.120> uset<00:04:16.759> we're<00:04:16.919> going<00:04:17.120> to<00:04:17.320> a<00:04:17.440> multitude 00:04:17.870 --> 00:04:17.880 align:start position:0% lists or uset we're going to a multitude 00:04:17.880 --> 00:04:19.349 align:start position:0% lists or uset we're going to a multitude of<00:04:18.040> identities<00:04:18.479> but<00:04:18.600> it's<00:04:18.720> still<00:04:18.880> coming<00:04:19.160> from 00:04:19.349 --> 00:04:19.359 align:start position:0% of identities but it's still coming from 00:04:19.359 --> 00:04:22.990 align:start position:0% of identities but it's still coming from one<00:04:20.320> and<00:04:20.600> when<00:04:20.759> we<00:04:20.919> use<00:04:21.720> kind<00:04:21.880> of<00:04:22.440> um<00:04:22.720> there<00:04:22.840> is 00:04:22.990 --> 00:04:23.000 align:start position:0% one and when we use kind of um there is 00:04:23.000 --> 00:04:24.430 align:start position:0% one and when we use kind of um there is also<00:04:23.199> a<00:04:23.320> kind<00:04:23.440> of<00:04:23.520> notion<00:04:23.800> of<00:04:23.919> global<00:04:24.240> stuff 00:04:24.430 --> 00:04:24.440 align:start position:0% also a kind of notion of global stuff 00:04:24.440 --> 00:04:25.550 align:start position:0% also a kind of notion of global stuff where<00:04:24.560> it's<00:04:24.680> not<00:04:24.880> really<00:04:25.080> coming<00:04:25.320> from 00:04:25.550 --> 00:04:25.560 align:start position:0% where it's not really coming from 00:04:25.560 --> 00:04:26.870 align:start position:0% where it's not really coming from anybody<00:04:26.000> maybe<00:04:26.199> it's<00:04:26.280> an<00:04:26.440> anonymous 00:04:26.870 --> 00:04:26.880 align:start position:0% anybody maybe it's an anonymous 00:04:26.880 --> 00:04:28.790 align:start position:0% anybody maybe it's an anonymous publication<00:04:27.880> uh<00:04:28.000> but<00:04:28.080> it's<00:04:28.199> going<00:04:28.400> to<00:04:28.560> a<00:04:28.639> whole 00:04:28.790 --> 00:04:28.800 align:start position:0% publication uh but it's going to a whole 00:04:28.800 --> 00:04:31.590 align:start position:0% publication uh but it's going to a whole bunch<00:04:29.039> of<00:04:29.199> people 00:04:31.590 --> 00:04:31.600 align:start position:0% bunch of people 00:04:31.600 --> 00:04:35.110 align:start position:0% bunch of people um<00:04:32.520> static<00:04:32.960> content<00:04:33.960> yeah<00:04:34.240> we<00:04:34.400> already<00:04:34.720> have 00:04:35.110 --> 00:04:35.120 align:start position:0% um static content yeah we already have 00:04:35.120 --> 00:04:37.110 align:start position:0% um static content yeah we already have uh<00:04:35.240> answers<00:04:35.520> for<00:04:35.759> that<00:04:36.280> realtime 00:04:37.110 --> 00:04:37.120 align:start position:0% uh answers for that realtime 00:04:37.120 --> 00:04:38.950 align:start position:0% uh answers for that realtime Communication<00:04:38.120> in<00:04:38.240> some<00:04:38.440> sense<00:04:38.639> we<00:04:38.759> have<00:04:38.840> an 00:04:38.950 --> 00:04:38.960 align:start position:0% Communication in some sense we have an 00:04:38.960 --> 00:04:40.230 align:start position:0% Communication in some sense we have an answer<00:04:39.160> for<00:04:39.320> that<00:04:39.440> within<00:04:39.639> the<00:04:39.720> ethereum 00:04:40.230 --> 00:04:40.240 align:start position:0% answer for that within the ethereum 00:04:40.240 --> 00:04:43.350 align:start position:0% answer for that within the ethereum framework<00:04:41.240> U<00:04:41.360> using<00:04:41.960> uh<00:04:42.199> the<00:04:42.440> dev<00:04:42.680> P2P<00:04:43.160> stuff 00:04:43.350 --> 00:04:43.360 align:start position:0% framework U using uh the dev P2P stuff 00:04:43.360 --> 00:04:46.870 align:start position:0% framework U using uh the dev P2P stuff maybe<00:04:43.600> a<00:04:43.680> raw<00:04:43.880> connection<00:04:44.240> over<00:04:44.520> that<00:04:45.520> um<00:04:46.320> but 00:04:46.870 --> 00:04:46.880 align:start position:0% maybe a raw connection over that um but 00:04:46.880 --> 00:04:48.830 align:start position:0% maybe a raw connection over that um but uh<00:04:47.000> for<00:04:47.199> the<00:04:47.400> for<00:04:47.560> the<00:04:47.680> final<00:04:48.000> Paradigm<00:04:48.560> that's 00:04:48.830 --> 00:04:48.840 align:start position:0% uh for the for the final Paradigm that's 00:04:48.840 --> 00:04:51.310 align:start position:0% uh for the for the final Paradigm that's basically<00:04:49.160> what<00:04:49.320> whisper<00:04:49.639> is<00:04:49.759> designed<00:04:50.120> to 00:04:51.310 --> 00:04:51.320 align:start position:0% basically what whisper is designed to 00:04:51.320 --> 00:04:53.590 align:start position:0% basically what whisper is designed to um<00:04:52.320> uh<00:04:52.400> to<00:04:52.600> address 00:04:53.590 --> 00:04:53.600 align:start position:0% um uh to address 00:04:53.600 --> 00:04:57.430 align:start position:0% um uh to address so<00:04:54.600> in<00:04:54.800> terms<00:04:55.360> of<00:04:55.960> privacy<00:04:56.800> I<00:04:56.880> think<00:04:57.000> it's<00:04:57.199> also 00:04:57.430 --> 00:04:57.440 align:start position:0% so in terms of privacy I think it's also 00:04:57.440 --> 00:04:59.870 align:start position:0% so in terms of privacy I think it's also important<00:04:57.800> to<00:04:57.960> remember<00:04:58.400> that<00:04:59.039> um<00:04:59.240> and<00:04:59.360> we 00:04:59.870 --> 00:04:59.880 align:start position:0% important to remember that um and we 00:04:59.880 --> 00:05:01.310 align:start position:0% important to remember that um and we know<00:05:00.039> this<00:05:00.160> much<00:05:00.320> more<00:05:00.520> than<00:05:00.639> when<00:05:00.759> I<00:05:00.919> first 00:05:01.310 --> 00:05:01.320 align:start position:0% know this much more than when I first 00:05:01.320 --> 00:05:03.990 align:start position:0% know this much more than when I first authored<00:05:01.680> this<00:05:01.840> talk<00:05:02.120> but<00:05:02.880> um<00:05:03.600> it's<00:05:03.800> very 00:05:03.990 --> 00:05:04.000 align:start position:0% authored this talk but um it's very 00:05:04.000 --> 00:05:05.870 align:start position:0% authored this talk but um it's very important<00:05:04.280> to<00:05:04.440> remember<00:05:04.759> that<00:05:05.000> the<00:05:05.120> metadata 00:05:05.870 --> 00:05:05.880 align:start position:0% important to remember that the metadata 00:05:05.880 --> 00:05:08.270 align:start position:0% important to remember that the metadata of<00:05:06.080> the<00:05:06.320> communications<00:05:07.039> can<00:05:07.199> also<00:05:07.680> can<00:05:07.919> often 00:05:08.270 --> 00:05:08.280 align:start position:0% of the communications can also can often 00:05:08.280 --> 00:05:11.390 align:start position:0% of the communications can also can often be<00:05:09.039> almost<00:05:09.440> as<00:05:09.600> important<00:05:10.400> to<00:05:10.560> keep<00:05:10.800> secret<00:05:11.240> as 00:05:11.390 --> 00:05:11.400 align:start position:0% be almost as important to keep secret as 00:05:11.400 --> 00:05:12.830 align:start position:0% be almost as important to keep secret as the<00:05:11.600> content<00:05:11.880> of<00:05:12.000> the<00:05:12.120> communications 00:05:12.830 --> 00:05:12.840 align:start position:0% the content of the communications 00:05:12.840 --> 00:05:14.670 align:start position:0% the content of the communications themselves<00:05:13.280> right<00:05:13.520> so<00:05:13.919> we<00:05:14.039> have<00:05:14.160> a<00:05:14.320> notion 00:05:14.670 --> 00:05:14.680 align:start position:0% themselves right so we have a notion 00:05:14.680 --> 00:05:16.670 align:start position:0% themselves right so we have a notion that<00:05:14.840> you<00:05:14.960> know<00:05:15.520> uh<00:05:15.680> metadata<00:05:16.199> collection 00:05:16.670 --> 00:05:16.680 align:start position:0% that you know uh metadata collection 00:05:16.680 --> 00:05:18.469 align:start position:0% that you know uh metadata collection actually<00:05:16.919> gives<00:05:17.199> very<00:05:17.400> useful<00:05:17.919> information 00:05:18.469 --> 00:05:18.479 align:start position:0% actually gives very useful information 00:05:18.479 --> 00:05:21.790 align:start position:0% actually gives very useful information on<00:05:19.440> um<00:05:20.400> on<00:05:20.639> what's<00:05:20.840> going<00:05:21.039> on<00:05:21.199> so<00:05:21.360> if<00:05:21.440> we<00:05:21.560> want 00:05:21.790 --> 00:05:21.800 align:start position:0% on um on what's going on so if we want 00:05:21.800 --> 00:05:24.590 align:start position:0% on um on what's going on so if we want privacy<00:05:22.240> it's<00:05:22.400> important<00:05:22.800> to<00:05:23.319> make<00:05:23.520> sure<00:05:23.960> that 00:05:24.590 --> 00:05:24.600 align:start position:0% privacy it's important to make sure that 00:05:24.600 --> 00:05:26.430 align:start position:0% privacy it's important to make sure that the<00:05:24.680> routing<00:05:25.160> itself<00:05:25.520> is<00:05:25.680> kept<00:05:25.919> private<00:05:26.319> as 00:05:26.430 --> 00:05:26.440 align:start position:0% the routing itself is kept private as 00:05:26.440 --> 00:05:28.150 align:start position:0% the routing itself is kept private as well<00:05:26.560> as<00:05:26.720> the 00:05:28.150 --> 00:05:28.160 align:start position:0% well as the 00:05:28.160 --> 00:05:30.749 align:start position:0% well as the content<00:05:29.160> so 00:05:30.749 --> 00:05:30.759 align:start position:0% content so 00:05:30.759 --> 00:05:32.430 align:start position:0% content so what<00:05:30.919> does<00:05:31.120> whisper<00:05:31.680> what<00:05:31.840> what<00:05:32.039> actually<00:05:32.280> is 00:05:32.430 --> 00:05:32.440 align:start position:0% what does whisper what what actually is 00:05:32.440 --> 00:05:34.070 align:start position:0% what does whisper what what actually is whisper<00:05:32.840> so<00:05:33.120> it's<00:05:33.240> a<00:05:33.360> bit<00:05:33.479> of<00:05:33.560> an<00:05:33.680> odd<00:05:33.880> thing 00:05:34.070 --> 00:05:34.080 align:start position:0% whisper so it's a bit of an odd thing 00:05:34.080 --> 00:05:35.870 align:start position:0% whisper so it's a bit of an odd thing because<00:05:34.240> it's<00:05:34.479> not<00:05:34.880> it's<00:05:35.039> not<00:05:35.199> a<00:05:35.360> messaging 00:05:35.870 --> 00:05:35.880 align:start position:0% because it's not it's not a messaging 00:05:35.880 --> 00:05:38.270 align:start position:0% because it's not it's not a messaging system<00:05:36.360> so<00:05:36.520> we<00:05:36.639> don't<00:05:36.840> deal<00:05:37.160> as<00:05:37.319> being<00:05:37.840> a<00:05:38.000> pure 00:05:38.270 --> 00:05:38.280 align:start position:0% system so we don't deal as being a pure 00:05:38.280 --> 00:05:40.390 align:start position:0% system so we don't deal as being a pure point-to-point<00:05:38.759> system<00:05:39.319> for<00:05:39.520> messaging<00:05:40.280> but 00:05:40.390 --> 00:05:40.400 align:start position:0% point-to-point system for messaging but 00:05:40.400 --> 00:05:42.629 align:start position:0% point-to-point system for messaging but it's<00:05:40.560> also<00:05:40.880> not<00:05:41.120> a<00:05:41.240> DHT<00:05:41.880> either<00:05:42.240> it's<00:05:42.440> kind<00:05:42.560> of 00:05:42.629 --> 00:05:42.639 align:start position:0% it's also not a DHT either it's kind of 00:05:42.639 --> 00:05:44.350 align:start position:0% it's also not a DHT either it's kind of a<00:05:42.800> hybrid<00:05:43.160> between<00:05:43.440> the 00:05:44.350 --> 00:05:44.360 align:start position:0% a hybrid between the 00:05:44.360 --> 00:05:46.550 align:start position:0% a hybrid between the two<00:05:45.360> um<00:05:45.520> it<00:05:45.680> has<00:05:45.800> a<00:05:45.880> couple<00:05:46.080> of<00:05:46.199> additional 00:05:46.550 --> 00:05:46.560 align:start position:0% two um it has a couple of additional 00:05:46.560 --> 00:05:48.469 align:start position:0% two um it has a couple of additional attributes<00:05:47.360> it<00:05:47.479> has<00:05:47.680> probabilistic<00:05:48.319> me 00:05:48.469 --> 00:05:48.479 align:start position:0% attributes it has probabilistic me 00:05:48.479 --> 00:05:49.950 align:start position:0% attributes it has probabilistic me method<00:05:48.800> foring<00:05:49.199> which<00:05:49.319> means<00:05:49.639> the<00:05:49.840> the 00:05:49.950 --> 00:05:49.960 align:start position:0% method foring which means the the 00:05:49.960 --> 00:05:52.469 align:start position:0% method foring which means the the routing<00:05:50.400> itself<00:05:50.759> is<00:05:50.960> kept<00:05:51.280> private<00:05:52.000> it's<00:05:52.199> kept 00:05:52.469 --> 00:05:52.479 align:start position:0% routing itself is kept private it's kept 00:05:52.479 --> 00:05:54.990 align:start position:0% routing itself is kept private it's kept private<00:05:52.919> because<00:05:53.520> actually<00:05:53.960> there's<00:05:54.199> no 00:05:54.990 --> 00:05:55.000 align:start position:0% private because actually there's no 00:05:55.000 --> 00:05:56.430 align:start position:0% private because actually there's no there's<00:05:55.160> no<00:05:55.360> easy<00:05:55.680> way<00:05:55.800> of<00:05:55.960> doing<00:05:56.199> any 00:05:56.430 --> 00:05:56.440 align:start position:0% there's no easy way of doing any 00:05:56.440 --> 00:05:58.189 align:start position:0% there's no easy way of doing any analysis<00:05:56.880> on<00:05:57.039> it<00:05:57.360> since<00:05:57.600> it's<00:05:57.960> it's 00:05:58.189 --> 00:05:58.199 align:start position:0% analysis on it since it's it's 00:05:58.199 --> 00:06:00.110 align:start position:0% analysis on it since it's it's probabilistic 00:06:00.110 --> 00:06:00.120 align:start position:0% probabilistic 00:06:00.120 --> 00:06:06.270 align:start position:0% probabilistic um<00:06:01.120> it's<00:06:01.360> also<00:06:02.280> um<00:06:02.520> oddly<00:06:03.280> oriented<00:06:03.960> around<00:06:05.280> um 00:06:06.270 --> 00:06:06.280 align:start position:0% um it's also um oddly oriented around um 00:06:06.280 --> 00:06:08.629 align:start position:0% um it's also um oddly oriented around um subject<00:06:06.800> key<00:06:07.120> so<00:06:07.319> it's<00:06:07.800> um<00:06:08.160> I'll<00:06:08.280> show<00:06:08.440> you 00:06:08.629 --> 00:06:08.639 align:start position:0% subject key so it's um I'll show you 00:06:08.639 --> 00:06:11.070 align:start position:0% subject key so it's um I'll show you later<00:06:08.880> but<00:06:09.080> basically<00:06:09.720> messages<00:06:10.720> normal 00:06:11.070 --> 00:06:11.080 align:start position:0% later but basically messages normal 00:06:11.080 --> 00:06:12.350 align:start position:0% later but basically messages normal normally<00:06:11.360> when<00:06:11.440> we<00:06:11.560> consider<00:06:11.880> messages<00:06:12.240> they 00:06:12.350 --> 00:06:12.360 align:start position:0% normally when we consider messages they 00:06:12.360 --> 00:06:14.350 align:start position:0% normally when we consider messages they have<00:06:12.440> a<00:06:12.599> very<00:06:12.800> particular<00:06:13.520> um<00:06:13.680> two<00:06:13.880> end<00:06:14.120> points 00:06:14.350 --> 00:06:14.360 align:start position:0% have a very particular um two end points 00:06:14.360 --> 00:06:15.430 align:start position:0% have a very particular um two end points they<00:06:14.440> have<00:06:14.520> the<00:06:14.599> end<00:06:14.800> point<00:06:14.919> that<00:06:15.039> they<00:06:15.120> start 00:06:15.430 --> 00:06:15.440 align:start position:0% they have the end point that they start 00:06:15.440 --> 00:06:16.830 align:start position:0% they have the end point that they start the<00:06:15.520> endp<00:06:15.720> point<00:06:15.880> that<00:06:16.080> they<00:06:16.280> they<00:06:16.440> eventually 00:06:16.830 --> 00:06:16.840 align:start position:0% the endp point that they they eventually 00:06:16.840 --> 00:06:20.870 align:start position:0% the endp point that they they eventually arrive<00:06:17.280> at<00:06:18.280> um<00:06:19.199> but<00:06:19.479> within<00:06:19.759> whisper<00:06:20.599> that's 00:06:20.870 --> 00:06:20.880 align:start position:0% arrive at um but within whisper that's 00:06:20.880 --> 00:06:22.469 align:start position:0% arrive at um but within whisper that's actually<00:06:21.199> played<00:06:21.560> down<00:06:21.800> it's<00:06:21.919> not<00:06:22.080> a<00:06:22.199> major 00:06:22.469 --> 00:06:22.479 align:start position:0% actually played down it's not a major 00:06:22.479 --> 00:06:24.510 align:start position:0% actually played down it's not a major part<00:06:22.639> of<00:06:22.800> the<00:06:22.960> system<00:06:23.360> rather<00:06:23.960> the<00:06:24.120> messages 00:06:24.510 --> 00:06:24.520 align:start position:0% part of the system rather the messages 00:06:24.520 --> 00:06:25.749 align:start position:0% part of the system rather the messages have<00:06:24.639> a<00:06:24.720> couple<00:06:24.919> of<00:06:25.039> attributes<00:06:25.479> that<00:06:25.560> are 00:06:25.749 --> 00:06:25.759 align:start position:0% have a couple of attributes that are 00:06:25.759 --> 00:06:27.629 align:start position:0% have a couple of attributes that are very<00:06:26.440> very<00:06:26.639> important<00:06:27.039> one<00:06:27.160> of<00:06:27.280> them<00:06:27.400> are 00:06:27.629 --> 00:06:27.639 align:start position:0% very very important one of them are 00:06:27.639 --> 00:06:29.629 align:start position:0% very very important one of them are topics<00:06:28.400> right<00:06:28.560> so<00:06:28.680> there's<00:06:28.800> a<00:06:28.919> notion<00:06:29.160> that 00:06:29.629 --> 00:06:29.639 align:start position:0% topics right so there's a notion that 00:06:29.639 --> 00:06:32.510 align:start position:0% topics right so there's a notion that messages<00:06:30.639> um<00:06:30.880> have<00:06:31.360> um<00:06:31.599> Associated<00:06:32.240> topics 00:06:32.510 --> 00:06:32.520 align:start position:0% messages um have um Associated topics 00:06:32.520 --> 00:06:34.070 align:start position:0% messages um have um Associated topics and<00:06:32.639> it's<00:06:32.840> these<00:06:33.120> topics<00:06:33.479> that<00:06:33.560> are<00:06:33.720> used<00:06:33.960> to 00:06:34.070 --> 00:06:34.080 align:start position:0% and it's these topics that are used to 00:06:34.080 --> 00:06:37.990 align:start position:0% and it's these topics that are used to root<00:06:34.360> the<00:06:34.479> messages<00:06:34.880> through<00:06:35.080> the<00:06:35.560> system<00:06:37.000> um 00:06:37.990 --> 00:06:38.000 align:start position:0% root the messages through the system um 00:06:38.000 --> 00:06:40.150 align:start position:0% root the messages through the system um I'll<00:06:38.199> come<00:06:38.319> on<00:06:38.440> to<00:06:38.599> that<00:06:39.120> in<00:06:39.240> a<00:06:39.479> second<00:06:39.880> so<00:06:40.080> is 00:06:40.150 --> 00:06:40.160 align:start position:0% I'll come on to that in a second so is 00:06:40.160 --> 00:06:41.110 align:start position:0% I'll come on to that in a second so is it<00:06:40.280> a 00:06:41.110 --> 00:06:41.120 align:start position:0% it a 00:06:41.120 --> 00:06:43.670 align:start position:0% it a DHT<00:06:42.120> well<00:06:42.319> if<00:06:42.400> we<00:06:42.560> think<00:06:42.680> of<00:06:42.800> it<00:06:42.919> in<00:06:43.000> terms<00:06:43.240> of<00:06:43.319> a 00:06:43.670 --> 00:06:43.680 align:start position:0% DHT well if we think of it in terms of a 00:06:43.680 --> 00:06:47.309 align:start position:0% DHT well if we think of it in terms of a DHT<00:06:44.680> then<00:06:45.000> it's<00:06:45.880> it's<00:06:46.120> multi-<00:06:46.560> key<00:06:47.080> which<00:06:47.199> is 00:06:47.309 --> 00:06:47.319 align:start position:0% DHT then it's it's multi- key which is 00:06:47.319 --> 00:06:49.469 align:start position:0% DHT then it's it's multi- key which is to<00:06:47.520> say<00:06:48.000> messages<00:06:48.400> may<00:06:48.639> have<00:06:48.960> more<00:06:49.160> than<00:06:49.280> one 00:06:49.469 --> 00:06:49.479 align:start position:0% to say messages may have more than one 00:06:49.479 --> 00:06:50.950 align:start position:0% to say messages may have more than one key<00:06:49.759> these<00:06:49.880> are<00:06:50.000> the<00:06:50.160> topics<00:06:50.479> that<00:06:50.560> I<00:06:50.639> alluded 00:06:50.950 --> 00:06:50.960 align:start position:0% key these are the topics that I alluded 00:06:50.960 --> 00:06:52.909 align:start position:0% key these are the topics that I alluded to<00:06:51.120> earlier<00:06:51.800> um<00:06:51.919> it's<00:06:52.039> multivalue<00:06:52.680> which<00:06:52.800> is 00:06:52.909 --> 00:06:52.919 align:start position:0% to earlier um it's multivalue which is 00:06:52.919 --> 00:06:55.070 align:start position:0% to earlier um it's multivalue which is to<00:06:53.039> say<00:06:53.280> topic<00:06:53.840> um<00:06:54.000> topics<00:06:54.360> or<00:06:54.520> messages<00:06:54.919> that 00:06:55.070 --> 00:06:55.080 align:start position:0% to say topic um topics or messages that 00:06:55.080 --> 00:06:57.670 align:start position:0% to say topic um topics or messages that have<00:06:55.639> um<00:06:55.840> the<00:06:56.000> same<00:06:56.360> Keys<00:06:57.120> actually<00:06:57.440> there<00:06:57.560> can 00:06:57.670 --> 00:06:57.680 align:start position:0% have um the same Keys actually there can 00:06:57.680 --> 00:07:00.309 align:start position:0% have um the same Keys actually there can be<00:06:57.840> different<00:06:58.160> values<00:06:58.520> Associated<00:06:59.039> to<00:06:59.240> them 00:07:00.309 --> 00:07:00.319 align:start position:0% be different values Associated to them 00:07:00.319 --> 00:07:01.909 align:start position:0% be different values Associated to them and<00:07:00.440> it's<00:07:00.599> transient<00:07:01.160> so<00:07:01.280> they<00:07:01.400> don't<00:07:01.639> stick 00:07:01.909 --> 00:07:01.919 align:start position:0% and it's transient so they don't stick 00:07:01.919 --> 00:07:03.589 align:start position:0% and it's transient so they don't stick around<00:07:02.160> forever<00:07:02.759> they<00:07:02.879> have<00:07:03.000> an<00:07:03.160> explicit 00:07:03.589 --> 00:07:03.599 align:start position:0% around forever they have an explicit 00:07:03.599 --> 00:07:04.629 align:start position:0% around forever they have an explicit expiry 00:07:04.629 --> 00:07:04.639 align:start position:0% expiry 00:07:04.639 --> 00:07:06.869 align:start position:0% expiry date<00:07:05.639> and<00:07:05.840> if<00:07:05.960> we<00:07:06.080> think<00:07:06.240> of<00:07:06.319> it<00:07:06.440> in<00:07:06.520> terms<00:07:06.720> of<00:07:06.800> a 00:07:06.869 --> 00:07:06.879 align:start position:0% date and if we think of it in terms of a 00:07:06.879 --> 00:07:09.790 align:start position:0% date and if we think of it in terms of a datagram<00:07:07.319> transport<00:07:07.759> layer<00:07:08.720> then<00:07:09.520> which<00:07:09.639> we 00:07:09.790 --> 00:07:09.800 align:start position:0% datagram transport layer then which we 00:07:09.800 --> 00:07:11.830 align:start position:0% datagram transport layer then which we can<00:07:09.960> do<00:07:10.759> um<00:07:11.080> then<00:07:11.199> it's<00:07:11.360> also<00:07:11.560> got<00:07:11.720> some 00:07:11.830 --> 00:07:11.840 align:start position:0% can do um then it's also got some 00:07:11.840 --> 00:07:14.629 align:start position:0% can do um then it's also got some interesting<00:07:12.240> attributes<00:07:13.240> um<00:07:14.240> it<00:07:14.400> is 00:07:14.629 --> 00:07:14.639 align:start position:0% interesting attributes um it is 00:07:14.639 --> 00:07:16.270 align:start position:0% interesting attributes um it is inherently 00:07:16.270 --> 00:07:16.280 align:start position:0% inherently 00:07:16.280 --> 00:07:18.909 align:start position:0% inherently multicast<00:07:17.280> which<00:07:17.400> is<00:07:17.800> kind<00:07:17.919> of<00:07:18.280> interesting 00:07:18.909 --> 00:07:18.919 align:start position:0% multicast which is kind of interesting 00:07:18.919 --> 00:07:21.869 align:start position:0% multicast which is kind of interesting it<00:07:19.080> allows<00:07:19.479> for<00:07:20.280> um<00:07:20.520> actually<00:07:21.240> reasonably 00:07:21.869 --> 00:07:21.879 align:start position:0% it allows for um actually reasonably 00:07:21.879 --> 00:07:25.749 align:start position:0% it allows for um actually reasonably efficient<00:07:22.319> dealing<00:07:22.840> with<00:07:23.120> things<00:07:23.560> like<00:07:24.759> um 00:07:25.749 --> 00:07:25.759 align:start position:0% efficient dealing with things like um 00:07:25.759 --> 00:07:27.670 align:start position:0% efficient dealing with things like um hashtags<00:07:26.240> on<00:07:26.440> Twitter<00:07:27.199> uh<00:07:27.319> and<00:07:27.440> it's 00:07:27.670 --> 00:07:27.680 align:start position:0% hashtags on Twitter uh and it's 00:07:27.680 --> 00:07:31.430 align:start position:0% hashtags on Twitter uh and it's asynchronous<00:07:28.680> so<00:07:29.360> um<00:07:29.800> the<00:07:30.039> messages<00:07:31.039> the<00:07:31.319> the 00:07:31.430 --> 00:07:31.440 align:start position:0% asynchronous so um the messages the the 00:07:31.440 --> 00:07:33.469 align:start position:0% asynchronous so um the messages the the two<00:07:31.680> points<00:07:32.280> from<00:07:32.479> which<00:07:32.639> the<00:07:32.759> messages<00:07:33.240> go 00:07:33.469 --> 00:07:33.479 align:start position:0% two points from which the messages go 00:07:33.479 --> 00:07:35.670 align:start position:0% two points from which the messages go between<00:07:34.120> don't<00:07:34.440> actually<00:07:34.639> have<00:07:34.759> to<00:07:34.919> be<00:07:35.199> online 00:07:35.670 --> 00:07:35.680 align:start position:0% between don't actually have to be online 00:07:35.680 --> 00:07:37.830 align:start position:0% between don't actually have to be online at<00:07:35.800> the<00:07:35.919> same 00:07:37.830 --> 00:07:37.840 align:start position:0% at the same 00:07:37.840 --> 00:07:40.990 align:start position:0% at the same time<00:07:38.840> it's<00:07:39.039> also<00:07:39.280> got<00:07:39.720> um<00:07:39.919> a<00:07:40.080> nice<00:07:40.360> little<00:07:40.800> sort 00:07:40.990 --> 00:07:41.000 align:start position:0% time it's also got um a nice little sort 00:07:41.000 --> 00:07:45.070 align:start position:0% time it's also got um a nice little sort of<00:07:41.240> inbuilt<00:07:41.840> anti-dos<00:07:42.720> system<00:07:43.039> it's<00:07:43.240> not<00:07:44.080> um 00:07:45.070 --> 00:07:45.080 align:start position:0% of inbuilt anti-dos system it's not um 00:07:45.080 --> 00:07:47.469 align:start position:0% of inbuilt anti-dos system it's not um Next<00:07:45.479> Generation<00:07:46.000> but<00:07:46.159> it<00:07:46.319> it<00:07:46.800> basically<00:07:47.240> it's 00:07:47.469 --> 00:07:47.479 align:start position:0% Next Generation but it it basically it's 00:07:47.479 --> 00:07:49.110 align:start position:0% Next Generation but it it basically it's got<00:07:47.599> we've<00:07:47.759> got<00:07:47.879> some<00:07:48.080> good<00:07:48.599> good<00:07:48.720> behavior 00:07:49.110 --> 00:07:49.120 align:start position:0% got we've got some good good behavior 00:07:49.120 --> 00:07:51.350 align:start position:0% got we've got some good good behavior incentivization<00:07:49.879> in 00:07:51.350 --> 00:07:51.360 align:start position:0% incentivization in 00:07:51.360 --> 00:07:55.749 align:start position:0% incentivization in there<00:07:52.800> um<00:07:53.800> one<00:07:53.960> of<00:07:54.199> the<00:07:54.440> important<00:07:55.360> U<00:07:55.440> sort<00:07:55.639> of 00:07:55.749 --> 00:07:55.759 align:start position:0% there um one of the important U sort of 00:07:55.759 --> 00:07:58.270 align:start position:0% there um one of the important U sort of tenants<00:07:56.599> that<00:07:56.759> Whispers<00:07:57.199> designed<00:07:57.560> around<00:07:58.000> is 00:07:58.270 --> 00:07:58.280 align:start position:0% tenants that Whispers designed around is 00:07:58.280 --> 00:08:01.430 align:start position:0% tenants that Whispers designed around is always<00:07:58.759> considering<00:07:59.840> identity<00:08:00.759> and<00:08:01.000> never 00:08:01.430 --> 00:08:01.440 align:start position:0% always considering identity and never 00:08:01.440 --> 00:08:02.710 align:start position:0% always considering identity and never considering<00:08:01.879> endpoint<00:08:02.319> we<00:08:02.400> consider 00:08:02.710 --> 00:08:02.720 align:start position:0% considering endpoint we consider 00:08:02.720 --> 00:08:04.350 align:start position:0% considering endpoint we consider endpoint<00:08:03.159> to<00:08:03.280> be<00:08:03.479> basically<00:08:04.199> an 00:08:04.350 --> 00:08:04.360 align:start position:0% endpoint to be basically an 00:08:04.360 --> 00:08:07.990 align:start position:0% endpoint to be basically an implementation<00:08:05.159> detail<00:08:06.159> um<00:08:06.680> to<00:08:06.879> do<00:08:07.159> with<00:08:07.800> um 00:08:07.990 --> 00:08:08.000 align:start position:0% implementation detail um to do with um 00:08:08.000 --> 00:08:09.830 align:start position:0% implementation detail um to do with um the<00:08:08.199> hardware<00:08:08.720> that<00:08:08.840> it's<00:08:09.039> actually<00:08:09.440> running 00:08:09.830 --> 00:08:09.840 align:start position:0% the hardware that it's actually running 00:08:09.840 --> 00:08:12.469 align:start position:0% the hardware that it's actually running on<00:08:10.360> and<00:08:10.520> it's<00:08:10.960> as<00:08:11.080> such<00:08:11.319> it<00:08:11.440> fits<00:08:11.720> a<00:08:11.879> layer 00:08:12.469 --> 00:08:12.479 align:start position:0% on and it's as such it fits a layer 00:08:12.479 --> 00:08:15.550 align:start position:0% on and it's as such it fits a layer below<00:08:13.039> this<00:08:13.240> particular<00:08:14.039> protocol<00:08:15.039> um<00:08:15.400> in 00:08:15.550 --> 00:08:15.560 align:start position:0% below this particular protocol um in 00:08:15.560 --> 00:08:17.149 align:start position:0% below this particular protocol um in terms<00:08:15.759> of<00:08:15.919> whisper<00:08:16.319> we<00:08:16.479> never<00:08:16.680> deal<00:08:16.919> with<00:08:17.039> the 00:08:17.149 --> 00:08:17.159 align:start position:0% terms of whisper we never deal with the 00:08:17.159 --> 00:08:18.189 align:start position:0% terms of whisper we never deal with the end 00:08:18.189 --> 00:08:18.199 align:start position:0% end 00:08:18.199 --> 00:08:21.990 align:start position:0% end points<00:08:19.199> um<00:08:20.199> this<00:08:20.360> is<00:08:20.680> nice<00:08:21.199> because<00:08:21.520> it<00:08:21.720> has 00:08:21.990 --> 00:08:22.000 align:start position:0% points um this is nice because it has 00:08:22.000 --> 00:08:24.790 align:start position:0% points um this is nice because it has certain<00:08:23.000> um<00:08:23.560> it<00:08:23.680> ties<00:08:23.960> into<00:08:24.240> the<00:08:24.400> Privacy 00:08:24.790 --> 00:08:24.800 align:start position:0% certain um it ties into the Privacy 00:08:24.800 --> 00:08:26.469 align:start position:0% certain um it ties into the Privacy thing<00:08:25.000> if<00:08:25.080> you<00:08:25.199> never<00:08:25.400> deal<00:08:25.639> with<00:08:25.759> end<00:08:26.080> points 00:08:26.469 --> 00:08:26.479 align:start position:0% thing if you never deal with end points 00:08:26.479 --> 00:08:28.909 align:start position:0% thing if you never deal with end points then<00:08:27.199> um<00:08:27.400> in<00:08:27.639> principle<00:08:28.159> messages<00:08:28.599> can<00:08:28.720> never 00:08:28.909 --> 00:08:28.919 align:start position:0% then um in principle messages can never 00:08:28.919 --> 00:08:30.390 align:start position:0% then um in principle messages can never be<00:08:29.039> tied<00:08:29.280> to<00:08:29.560> any<00:08:29.720> particular<00:08:30.000> physical 00:08:30.390 --> 00:08:30.400 align:start position:0% be tied to any particular physical 00:08:30.400 --> 00:08:32.029 align:start position:0% be tied to any particular physical location<00:08:30.879> rather<00:08:31.120> they're<00:08:31.319> tied<00:08:31.599> to 00:08:32.029 --> 00:08:32.039 align:start position:0% location rather they're tied to 00:08:32.039 --> 00:08:35.029 align:start position:0% location rather they're tied to cryptographic<00:08:32.680> identities<00:08:33.680> and<00:08:33.880> that<00:08:34.240> that's 00:08:35.029 --> 00:08:35.039 align:start position:0% cryptographic identities and that that's 00:08:35.039 --> 00:08:37.350 align:start position:0% cryptographic identities and that that's quite<00:08:35.240> an<00:08:35.399> interesting<00:08:35.839> attribute<00:08:36.200> to 00:08:37.350 --> 00:08:37.360 align:start position:0% quite an interesting attribute to 00:08:37.360 --> 00:08:40.029 align:start position:0% quite an interesting attribute to have<00:08:38.360> um<00:08:38.760> furthermore<00:08:39.760> uh<00:08:39.919> the 00:08:40.029 --> 00:08:40.039 align:start position:0% have um furthermore uh the 00:08:40.039 --> 00:08:41.790 align:start position:0% have um furthermore uh the implementation<00:08:40.599> is<00:08:40.800> configurable<00:08:41.360> in<00:08:41.479> terms 00:08:41.790 --> 00:08:41.800 align:start position:0% implementation is configurable in terms 00:08:41.800 --> 00:08:45.110 align:start position:0% implementation is configurable in terms of<00:08:42.120> what<00:08:42.880> uh<00:08:43.039> tradeoff<00:08:43.880> the<00:08:44.080> user<00:08:44.600> or<00:08:44.800> perhaps 00:08:45.110 --> 00:08:45.120 align:start position:0% of what uh tradeoff the user or perhaps 00:08:45.120 --> 00:08:48.509 align:start position:0% of what uh tradeoff the user or perhaps even<00:08:45.360> the<00:08:45.560> application<00:08:46.200> wants<00:08:47.200> um<00:08:47.480> from<00:08:48.360> uh 00:08:48.509 --> 00:08:48.519 align:start position:0% even the application wants um from uh 00:08:48.519 --> 00:08:50.509 align:start position:0% even the application wants um from uh efficiency<00:08:49.000> and<00:08:49.160> privacy<00:08:49.880> so<00:08:50.080> on<00:08:50.200> the<00:08:50.320> one 00:08:50.509 --> 00:08:50.519 align:start position:0% efficiency and privacy so on the one 00:08:50.519 --> 00:08:52.670 align:start position:0% efficiency and privacy so on the one hand<00:08:51.080> um<00:08:51.200> if<00:08:51.279> we<00:08:51.399> want<00:08:51.560> a<00:08:51.640> lot<00:08:51.800> of<00:08:51.959> efficiency 00:08:52.670 --> 00:08:52.680 align:start position:0% hand um if we want a lot of efficiency 00:08:52.680 --> 00:08:53.590 align:start position:0% hand um if we want a lot of efficiency we're<00:08:52.800> going<00:08:52.880> to<00:08:53.000> have<00:08:53.080> to<00:08:53.160> give<00:08:53.279> up<00:08:53.480> some 00:08:53.590 --> 00:08:53.600 align:start position:0% we're going to have to give up some 00:08:53.600 --> 00:08:55.070 align:start position:0% we're going to have to give up some privacy<00:08:54.000> because<00:08:54.160> we're<00:08:54.480> necessarily<00:08:54.959> going 00:08:55.070 --> 00:08:55.080 align:start position:0% privacy because we're necessarily going 00:08:55.080 --> 00:08:58.150 align:start position:0% privacy because we're necessarily going to<00:08:55.160> be<00:08:55.360> closer<00:08:56.160> to<00:08:56.320> the<00:08:56.480> metal<00:08:57.320> in<00:08:57.480> terms<00:08:57.839> of 00:08:58.150 --> 00:08:58.160 align:start position:0% to be closer to the metal in terms of 00:08:58.160 --> 00:09:01.069 align:start position:0% to be closer to the metal in terms of rooting<00:08:58.640> the<00:08:58.800> packets<00:08:59.839> similarly<00:09:00.399> if<00:09:00.640> we<00:09:01.000> if 00:09:01.069 --> 00:09:01.079 align:start position:0% rooting the packets similarly if we if 00:09:01.079 --> 00:09:03.350 align:start position:0% rooting the packets similarly if we if we<00:09:01.240> don't<00:09:01.480> want<00:09:02.200> um<00:09:02.600> a<00:09:02.760> vast<00:09:03.040> amount<00:09:03.240> of 00:09:03.350 --> 00:09:03.360 align:start position:0% we don't want um a vast amount of 00:09:03.360 --> 00:09:05.310 align:start position:0% we don't want um a vast amount of privacy<00:09:03.760> then<00:09:03.880> we'll<00:09:04.040> be<00:09:04.160> able<00:09:04.360> to<00:09:04.920> um<00:09:05.040> trade 00:09:05.310 --> 00:09:05.320 align:start position:0% privacy then we'll be able to um trade 00:09:05.320 --> 00:09:08.430 align:start position:0% privacy then we'll be able to um trade that<00:09:05.440> off<00:09:05.560> and<00:09:05.720> get<00:09:06.279> substantially<00:09:06.880> faster<00:09:07.720> um 00:09:08.430 --> 00:09:08.440 align:start position:0% that off and get substantially faster um 00:09:08.440 --> 00:09:12.990 align:start position:0% that off and get substantially faster um faster<00:09:09.440> transmission 00:09:12.990 --> 00:09:13.000 align:start position:0% 00:09:13.000 --> 00:09:16.110 align:start position:0% times<00:09:14.000> it's<00:09:14.320> topic<00:09:14.680> based<00:09:15.040> which<00:09:15.160> means<00:09:15.720> when 00:09:16.110 --> 00:09:16.120 align:start position:0% times it's topic based which means when 00:09:16.120 --> 00:09:19.069 align:start position:0% times it's topic based which means when we<00:09:16.560> want<00:09:16.800> to<00:09:17.120> communicate<00:09:17.800> within<00:09:18.120> whisper<00:09:18.920> we 00:09:19.069 --> 00:09:19.079 align:start position:0% we want to communicate within whisper we 00:09:19.079 --> 00:09:22.190 align:start position:0% we want to communicate within whisper we do<00:09:19.240> so<00:09:19.519> by<00:09:19.720> naming<00:09:20.480> by<00:09:20.800> associating<00:09:21.680> topics 00:09:22.190 --> 00:09:22.200 align:start position:0% do so by naming by associating topics 00:09:22.200 --> 00:09:23.630 align:start position:0% do so by naming by associating topics which<00:09:22.320> are<00:09:22.519> small<00:09:22.880> cryptographic 00:09:23.630 --> 00:09:23.640 align:start position:0% which are small cryptographic 00:09:23.640 --> 00:09:27.310 align:start position:0% which are small cryptographic identifiers<00:09:24.640> with<00:09:25.079> messages<00:09:26.079> in<00:09:26.200> order<00:09:26.480> to<00:09:27.120> um 00:09:27.310 --> 00:09:27.320 align:start position:0% identifiers with messages in order to um 00:09:27.320 --> 00:09:29.590 align:start position:0% identifiers with messages in order to um eventually<00:09:27.760> re<00:09:28.079> in<00:09:28.320> these<00:09:28.480> messages<00:09:29.040> we<00:09:29.480> which 00:09:29.590 --> 00:09:29.600 align:start position:0% eventually re in these messages we which 00:09:29.600 --> 00:09:32.190 align:start position:0% eventually re in these messages we which we<00:09:29.760> may<00:09:29.880> be<00:09:30.079> interested<00:09:30.480> in<00:09:31.240> uh<00:09:31.399> we<00:09:31.560> use<00:09:32.040> the 00:09:32.190 --> 00:09:32.200 align:start position:0% we may be interested in uh we use the 00:09:32.200 --> 00:09:34.150 align:start position:0% we may be interested in uh we use the same<00:09:32.720> uh<00:09:32.839> mechanism<00:09:33.320> we<00:09:33.440> use<00:09:33.640> these<00:09:33.839> small 00:09:34.150 --> 00:09:34.160 align:start position:0% same uh mechanism we use these small 00:09:34.160 --> 00:09:37.470 align:start position:0% same uh mechanism we use these small cryptographic 00:09:37.470 --> 00:09:37.480 align:start position:0% 00:09:37.480 --> 00:09:39.030 align:start position:0% identifiers 00:09:39.030 --> 00:09:39.040 align:start position:0% identifiers 00:09:39.040 --> 00:09:42.990 align:start position:0% identifiers um<00:09:40.040> in<00:09:40.240> terms<00:09:40.760> of<00:09:41.079> the<00:09:41.240> encryption<00:09:41.720> it<00:09:41.880> uses<00:09:42.839> uh 00:09:42.990 --> 00:09:43.000 align:start position:0% um in terms of the encryption it uses uh 00:09:43.000 --> 00:09:45.750 align:start position:0% um in terms of the encryption it uses uh the<00:09:43.160> difference<00:09:43.600> between<00:09:44.200> unicast<00:09:45.000> a<00:09:45.160> unicast 00:09:45.750 --> 00:09:45.760 align:start position:0% the difference between unicast a unicast 00:09:45.760 --> 00:09:47.750 align:start position:0% the difference between unicast a unicast message<00:09:46.040> within<00:09:46.279> whisper<00:09:46.959> and<00:09:47.079> a<00:09:47.200> broadcast 00:09:47.750 --> 00:09:47.760 align:start position:0% message within whisper and a broadcast 00:09:47.760 --> 00:09:50.030 align:start position:0% message within whisper and a broadcast message<00:09:48.079> within<00:09:48.320> whisper<00:09:49.320> is<00:09:49.560> essentially 00:09:50.030 --> 00:09:50.040 align:start position:0% message within whisper is essentially 00:09:50.040 --> 00:09:52.190 align:start position:0% message within whisper is essentially the<00:09:50.240> difference<00:09:50.760> in<00:09:51.320> which<00:09:51.640> key<00:09:51.920> it's 00:09:52.190 --> 00:09:52.200 align:start position:0% the difference in which key it's 00:09:52.200 --> 00:09:54.470 align:start position:0% the difference in which key it's encrypted<00:09:52.800> with<00:09:53.120> right<00:09:53.600> so<00:09:53.800> we're<00:09:53.959> not<00:09:54.160> doing 00:09:54.470 --> 00:09:54.480 align:start position:0% encrypted with right so we're not doing 00:09:54.480 --> 00:09:58.829 align:start position:0% encrypted with right so we're not doing anything<00:09:55.360> in<00:09:55.519> terms<00:09:55.959> of<00:09:56.360> the<00:09:57.360> um<00:09:58.240> the<00:09:58.399> sort<00:09:58.600> of 00:09:58.829 --> 00:09:58.839 align:start position:0% anything in terms of the um the sort of 00:09:58.839 --> 00:10:00.949 align:start position:0% anything in terms of the um the sort of hardware<00:09:59.480> close<00:09:59.720> to<00:09:59.880> the<00:10:00.000> metal<00:10:00.279> routing<00:10:00.800> with 00:10:00.949 --> 00:10:00.959 align:start position:0% hardware close to the metal routing with 00:10:00.959 --> 00:10:02.949 align:start position:0% hardware close to the metal routing with this<00:10:01.240> what<00:10:01.360> we're<00:10:01.519> doing<00:10:01.760> is<00:10:01.920> saying<00:10:02.320> right<00:10:02.839> if 00:10:02.949 --> 00:10:02.959 align:start position:0% this what we're doing is saying right if 00:10:02.959 --> 00:10:04.790 align:start position:0% this what we're doing is saying right if it's<00:10:03.160> unicost<00:10:03.800> I'm<00:10:03.920> going<00:10:04.079> to<00:10:04.240> encrypt<00:10:04.640> it 00:10:04.790 --> 00:10:04.800 align:start position:0% it's unicost I'm going to encrypt it 00:10:04.800 --> 00:10:06.710 align:start position:0% it's unicost I'm going to encrypt it with<00:10:04.959> your<00:10:05.240> identity<00:10:05.959> which<00:10:06.120> means<00:10:06.480> doesn't 00:10:06.710 --> 00:10:06.720 align:start position:0% with your identity which means doesn't 00:10:06.720 --> 00:10:09.230 align:start position:0% with your identity which means doesn't matter<00:10:06.959> who<00:10:07.480> receives<00:10:07.720> it<00:10:08.480> we<00:10:08.600> want<00:10:08.880> everybody 00:10:09.230 --> 00:10:09.240 align:start position:0% matter who receives it we want everybody 00:10:09.240 --> 00:10:11.069 align:start position:0% matter who receives it we want everybody to<00:10:09.399> receive<00:10:09.680> it<00:10:09.800> in<00:10:10.000> principle<00:10:10.760> the<00:10:10.839> only 00:10:11.069 --> 00:10:11.079 align:start position:0% to receive it in principle the only 00:10:11.079 --> 00:10:12.990 align:start position:0% to receive it in principle the only person<00:10:11.320> who<00:10:11.440> can<00:10:11.600> actually<00:10:11.880> decrypt<00:10:12.399> it<00:10:12.839> is 00:10:12.990 --> 00:10:13.000 align:start position:0% person who can actually decrypt it is 00:10:13.000 --> 00:10:15.269 align:start position:0% person who can actually decrypt it is the 00:10:15.269 --> 00:10:15.279 align:start position:0% 00:10:15.279 --> 00:10:17.670 align:start position:0% recipient<00:10:16.279> with<00:10:16.480> broadcast<00:10:17.279> rather<00:10:17.519> than 00:10:17.670 --> 00:10:17.680 align:start position:0% recipient with broadcast rather than 00:10:17.680 --> 00:10:19.310 align:start position:0% recipient with broadcast rather than encrypting<00:10:18.120> it<00:10:18.240> with<00:10:18.320> a<00:10:18.480> particular<00:10:18.920> identity 00:10:19.310 --> 00:10:19.320 align:start position:0% encrypting it with a particular identity 00:10:19.320 --> 00:10:20.550 align:start position:0% encrypting it with a particular identity we<00:10:19.480> encrypt<00:10:19.800> it<00:10:19.839> with<00:10:19.959> the<00:10:20.079> topics<00:10:20.440> which 00:10:20.550 --> 00:10:20.560 align:start position:0% we encrypt it with the topics which 00:10:20.560 --> 00:10:22.069 align:start position:0% we encrypt it with the topics which means<00:10:20.880> anybody<00:10:21.279> who<00:10:21.399> knows<00:10:21.680> what<00:10:21.839> those 00:10:22.069 --> 00:10:22.079 align:start position:0% means anybody who knows what those 00:10:22.079 --> 00:10:24.389 align:start position:0% means anybody who knows what those topics<00:10:22.440> are<00:10:23.360> are<00:10:23.480> able<00:10:23.760> in<00:10:23.920> principle<00:10:24.240> to 00:10:24.389 --> 00:10:24.399 align:start position:0% topics are are able in principle to 00:10:24.399 --> 00:10:25.910 align:start position:0% topics are are able in principle to decrypt<00:10:24.760> the 00:10:25.910 --> 00:10:25.920 align:start position:0% decrypt the 00:10:25.920 --> 00:10:28.430 align:start position:0% decrypt the message<00:10:26.920> however<00:10:27.440> one<00:10:27.519> of<00:10:27.640> the<00:10:27.800> nice<00:10:28.120> things 00:10:28.430 --> 00:10:28.440 align:start position:0% message however one of the nice things 00:10:28.440 --> 00:10:30.509 align:start position:0% message however one of the nice things that's<00:10:28.800> that's<00:10:29.480> tied<00:10:29.800> into<00:10:30.079> this<00:10:30.240> is<00:10:30.399> the 00:10:30.509 --> 00:10:30.519 align:start position:0% that's that's tied into this is the 00:10:30.519 --> 00:10:32.230 align:start position:0% that's that's tied into this is the notion<00:10:30.720> of<00:10:30.839> root<00:10:31.040> of<00:10:31.200> deniability<00:10:31.880> which<00:10:32.000> is 00:10:32.230 --> 00:10:32.240 align:start position:0% notion of root of deniability which is 00:10:32.240 --> 00:10:34.590 align:start position:0% notion of root of deniability which is which<00:10:32.600> if<00:10:32.839> I<00:10:32.959> am<00:10:33.279> merely<00:10:33.680> storing<00:10:34.200> a<00:10:34.320> message 00:10:34.590 --> 00:10:34.600 align:start position:0% which if I am merely storing a message 00:10:34.600 --> 00:10:36.829 align:start position:0% which if I am merely storing a message or<00:10:34.800> passing<00:10:35.120> it<00:10:35.320> on<00:10:36.160> and<00:10:36.279> I<00:10:36.399> was<00:10:36.600> never 00:10:36.829 --> 00:10:36.839 align:start position:0% or passing it on and I was never 00:10:36.839 --> 00:10:38.790 align:start position:0% or passing it on and I was never interested<00:10:37.320> in<00:10:37.480> these<00:10:37.680> topics<00:10:38.120> I<00:10:38.200> will<00:10:38.399> not<00:10:38.639> be 00:10:38.790 --> 00:10:38.800 align:start position:0% interested in these topics I will not be 00:10:38.800 --> 00:10:41.310 align:start position:0% interested in these topics I will not be able<00:10:39.040> to<00:10:39.200> decrypt<00:10:39.720> the<00:10:39.880> message<00:10:40.560> because<00:10:41.120> I'm 00:10:41.310 --> 00:10:41.320 align:start position:0% able to decrypt the message because I'm 00:10:41.320 --> 00:10:43.350 align:start position:0% able to decrypt the message because I'm only<00:10:41.560> dealing<00:10:42.000> with<00:10:42.440> what<00:10:42.600> is<00:10:42.800> essentially<00:10:43.160> a 00:10:43.350 --> 00:10:43.360 align:start position:0% only dealing with what is essentially a 00:10:43.360 --> 00:10:45.990 align:start position:0% only dealing with what is essentially a partial<00:10:43.800> topic<00:10:44.079> a<00:10:44.240> small<00:10:44.519> portion<00:10:44.800> of<00:10:45.000> this 00:10:45.990 --> 00:10:46.000 align:start position:0% partial topic a small portion of this 00:10:46.000 --> 00:10:48.949 align:start position:0% partial topic a small portion of this topic<00:10:47.000> uh<00:10:47.120> which<00:10:47.240> is<00:10:47.440> sufficient<00:10:47.839> for<00:10:48.040> rooting 00:10:48.949 --> 00:10:48.959 align:start position:0% topic uh which is sufficient for rooting 00:10:48.959 --> 00:10:50.310 align:start position:0% topic uh which is sufficient for rooting but<00:10:49.160> not<00:10:49.399> sufficient<00:10:49.800> for<00:10:50.000> actually 00:10:50.310 --> 00:10:50.320 align:start position:0% but not sufficient for actually 00:10:50.320 --> 00:10:53.509 align:start position:0% but not sufficient for actually decryption<00:10:50.760> of<00:10:50.880> the<00:10:51.000> message 00:10:53.509 --> 00:10:53.519 align:start position:0% 00:10:53.519 --> 00:10:55.870 align:start position:0% itself<00:10:54.519> messages<00:10:54.880> are<00:10:55.079> authenticated<00:10:55.720> as 00:10:55.870 --> 00:10:55.880 align:start position:0% itself messages are authenticated as 00:10:55.880 --> 00:10:57.910 align:start position:0% itself messages are authenticated as well<00:10:56.279> the<00:10:56.440> difference<00:10:56.800> between<00:10:57.480> um<00:10:57.720> there 00:10:57.910 --> 00:10:57.920 align:start position:0% well the difference between um there 00:10:57.920 --> 00:11:00.150 align:start position:0% well the difference between um there being<00:10:58.320> an<00:10:58.519> origin<00:10:59.320> so<00:10:59.440> it<00:10:59.519> coming<00:10:59.800> from<00:11:00.000> a 00:11:00.150 --> 00:11:00.160 align:start position:0% being an origin so it coming from a 00:11:00.160 --> 00:11:01.509 align:start position:0% being an origin so it coming from a particular<00:11:00.560> identity<00:11:01.079> and<00:11:01.160> it<00:11:01.279> being 00:11:01.509 --> 00:11:01.519 align:start position:0% particular identity and it being 00:11:01.519 --> 00:11:02.790 align:start position:0% particular identity and it being anonymous<00:11:01.959> is<00:11:02.120> simply<00:11:02.360> the<00:11:02.480> difference 00:11:02.790 --> 00:11:02.800 align:start position:0% anonymous is simply the difference 00:11:02.800 --> 00:11:04.550 align:start position:0% anonymous is simply the difference between<00:11:03.040> it<00:11:03.160> containing<00:11:03.560> a<00:11:03.680> signature<00:11:04.399> and 00:11:04.550 --> 00:11:04.560 align:start position:0% between it containing a signature and 00:11:04.560 --> 00:11:06.430 align:start position:0% between it containing a signature and not<00:11:04.760> containing<00:11:05.120> a<00:11:05.240> signature<00:11:05.920> and<00:11:06.040> this<00:11:06.240> kind 00:11:06.430 --> 00:11:06.440 align:start position:0% not containing a signature and this kind 00:11:06.440 --> 00:11:09.430 align:start position:0% not containing a signature and this kind of<00:11:06.600> ties<00:11:06.839> into<00:11:07.160> you<00:11:07.279> know<00:11:07.880> uh<00:11:08.040> pgp<00:11:08.720> with<00:11:08.920> email 00:11:09.430 --> 00:11:09.440 align:start position:0% of ties into you know uh pgp with email 00:11:09.440 --> 00:11:11.030 align:start position:0% of ties into you know uh pgp with email when<00:11:09.880> you<00:11:10.000> can<00:11:10.200> sign<00:11:10.440> a<00:11:10.560> message<00:11:10.800> you<00:11:10.920> can 00:11:11.030 --> 00:11:11.040 align:start position:0% when you can sign a message you can 00:11:11.040 --> 00:11:12.590 align:start position:0% when you can sign a message you can encrypt<00:11:11.360> a<00:11:11.440> message<00:11:11.720> or<00:11:11.839> you<00:11:11.920> can<00:11:12.079> encrypt<00:11:12.440> and 00:11:12.590 --> 00:11:12.600 align:start position:0% encrypt a message or you can encrypt and 00:11:12.600 --> 00:11:14.750 align:start position:0% encrypt a message or you can encrypt and sign<00:11:12.800> a<00:11:12.959> message<00:11:13.639> same<00:11:13.920> kind<00:11:14.040> of<00:11:14.240> idea<00:11:14.519> except 00:11:14.750 --> 00:11:14.760 align:start position:0% sign a message same kind of idea except 00:11:14.760 --> 00:11:17.509 align:start position:0% sign a message same kind of idea except it's<00:11:14.920> actually<00:11:15.279> built<00:11:15.480> into<00:11:15.720> the 00:11:17.509 --> 00:11:17.519 align:start position:0% it's actually built into the 00:11:17.519 --> 00:11:20.509 align:start position:0% it's actually built into the protocol<00:11:18.519> now<00:11:18.760> it's<00:11:18.959> important<00:11:19.360> to<00:11:19.920> also<00:11:20.279> get 00:11:20.509 --> 00:11:20.519 align:start position:0% protocol now it's important to also get 00:11:20.519 --> 00:11:22.350 align:start position:0% protocol now it's important to also get across<00:11:20.839> what<00:11:21.000> whisper<00:11:21.440> isn't<00:11:21.959> so<00:11:22.120> it's<00:11:22.279> going 00:11:22.350 --> 00:11:22.360 align:start position:0% across what whisper isn't so it's going 00:11:22.360 --> 00:11:24.150 align:start position:0% across what whisper isn't so it's going to<00:11:22.480> be<00:11:23.040> there's<00:11:23.279> a<00:11:23.399> bunch<00:11:23.560> of<00:11:23.720> stuff<00:11:24.040> which 00:11:24.150 --> 00:11:24.160 align:start position:0% to be there's a bunch of stuff which 00:11:24.160 --> 00:11:26.670 align:start position:0% to be there's a bunch of stuff which it's<00:11:24.440> definitely<00:11:25.040> not<00:11:25.320> suited<00:11:25.760> for<00:11:26.320> it's<00:11:26.480> not 00:11:26.670 --> 00:11:26.680 align:start position:0% it's definitely not suited for it's not 00:11:26.680 --> 00:11:28.269 align:start position:0% it's definitely not suited for it's not suited<00:11:27.000> for<00:11:27.240> high<00:11:27.399> bandwidth<00:11:27.880> point-to-point 00:11:28.269 --> 00:11:28.279 align:start position:0% suited for high bandwidth point-to-point 00:11:28.279 --> 00:11:30.389 align:start position:0% suited for high bandwidth point-to-point Transmissions<00:11:29.320> so<00:11:29.440> don't<00:11:29.959> think<00:11:30.160> that<00:11:30.279> you're 00:11:30.389 --> 00:11:30.399 align:start position:0% Transmissions so don't think that you're 00:11:30.399 --> 00:11:32.430 align:start position:0% Transmissions so don't think that you're going<00:11:30.519> to<00:11:30.639> do<00:11:31.120> you<00:11:31.240> know<00:11:31.480> Skype<00:11:31.800> over<00:11:32.079> whisper 00:11:32.430 --> 00:11:32.440 align:start position:0% going to do you know Skype over whisper 00:11:32.440 --> 00:11:35.030 align:start position:0% going to do you know Skype over whisper it's<00:11:32.560> not<00:11:32.720> going<00:11:32.800> to<00:11:32.959> happen<00:11:33.920> um<00:11:34.320> it's<00:11:34.480> not 00:11:35.030 --> 00:11:35.040 align:start position:0% it's not going to happen um it's not 00:11:35.040 --> 00:11:36.550 align:start position:0% it's not going to happen um it's not particularly<00:11:35.440> suited<00:11:35.760> to<00:11:35.839> low<00:11:36.040> latency 00:11:36.550 --> 00:11:36.560 align:start position:0% particularly suited to low latency 00:11:36.560 --> 00:11:38.389 align:start position:0% particularly suited to low latency Transmissions<00:11:37.079> although<00:11:37.399> it<00:11:37.560> can<00:11:37.760> be<00:11:37.959> traded 00:11:38.389 --> 00:11:38.399 align:start position:0% Transmissions although it can be traded 00:11:38.399 --> 00:11:39.949 align:start position:0% Transmissions although it can be traded off<00:11:38.600> to<00:11:38.760> some 00:11:39.949 --> 00:11:39.959 align:start position:0% off to some 00:11:39.959 --> 00:11:42.310 align:start position:0% off to some degree<00:11:40.959> um<00:11:41.279> this<00:11:41.399> isn't<00:11:41.639> an<00:11:41.839> application 00:11:42.310 --> 00:11:42.320 align:start position:0% degree um this isn't an application 00:11:42.320 --> 00:11:43.590 align:start position:0% degree um this isn't an application Level<00:11:42.600> protocol<00:11:43.000> so<00:11:43.120> you're<00:11:43.200> not<00:11:43.320> going<00:11:43.440> to 00:11:43.590 --> 00:11:43.600 align:start position:0% Level protocol so you're not going to 00:11:43.600 --> 00:11:48.150 align:start position:0% Level protocol so you're not going to use<00:11:43.959> whisper<00:11:44.800> directly<00:11:45.560> in<00:11:45.720> order<00:11:46.000> to<00:11:46.360> say<00:11:47.279> um 00:11:48.150 --> 00:11:48.160 align:start position:0% use whisper directly in order to say um 00:11:48.160 --> 00:11:50.030 align:start position:0% use whisper directly in order to say um take<00:11:48.399> part<00:11:48.600> in<00:11:48.720> a<00:11:48.839> chat<00:11:49.120> room<00:11:49.600> applications 00:11:50.030 --> 00:11:50.040 align:start position:0% take part in a chat room applications 00:11:50.040 --> 00:11:51.670 align:start position:0% take part in a chat room applications are<00:11:50.160> going<00:11:50.279> to<00:11:50.360> be<00:11:50.440> built<00:11:50.680> on<00:11:50.959> this<00:11:51.440> and<00:11:51.560> it's 00:11:51.670 --> 00:11:51.680 align:start position:0% are going to be built on this and it's 00:11:51.680 --> 00:11:53.790 align:start position:0% are going to be built on this and it's not<00:11:51.880> connection<00:11:52.279> oriented<00:11:52.959> this<00:11:53.079> is<00:11:53.360> entirely 00:11:53.790 --> 00:11:53.800 align:start position:0% not connection oriented this is entirely 00:11:53.800 --> 00:11:57.030 align:start position:0% not connection oriented this is entirely about<00:11:54.000> datagram 00:11:57.030 --> 00:11:57.040 align:start position:0% 00:11:57.040 --> 00:11:59.509 align:start position:0% messaging<00:11:58.040> there<00:11:58.120> are<00:11:58.320> two<00:11:58.480> routes<00:11:58.880> into<00:11:59.320> in 00:11:59.509 --> 00:11:59.519 align:start position:0% messaging there are two routes into in 00:11:59.519 --> 00:12:02.350 align:start position:0% messaging there are two routes into in whisper<00:11:59.880> to<00:12:00.040> rooting<00:12:00.560> itself<00:12:01.480> um<00:12:01.800> one<00:12:02.000> is 00:12:02.350 --> 00:12:02.360 align:start position:0% whisper to rooting itself um one is 00:12:02.360 --> 00:12:04.590 align:start position:0% whisper to rooting itself um one is passive<00:12:03.160> which<00:12:03.320> is<00:12:03.519> essentially<00:12:03.959> a<00:12:04.160> case<00:12:04.360> of 00:12:04.590 --> 00:12:04.600 align:start position:0% passive which is essentially a case of 00:12:04.600 --> 00:12:06.190 align:start position:0% passive which is essentially a case of gathering<00:12:04.959> nodes<00:12:05.360> that<00:12:05.480> tend<00:12:05.720> to<00:12:05.880> pass<00:12:06.079> you 00:12:06.190 --> 00:12:06.200 align:start position:0% gathering nodes that tend to pass you 00:12:06.200 --> 00:12:08.230 align:start position:0% gathering nodes that tend to pass you the<00:12:06.360> right<00:12:06.560> messages<00:12:07.279> you<00:12:07.399> throw<00:12:07.639> out<00:12:07.839> nodes 00:12:08.230 --> 00:12:08.240 align:start position:0% the right messages you throw out nodes 00:12:08.240 --> 00:12:10.870 align:start position:0% the right messages you throw out nodes that<00:12:08.399> don't<00:12:09.360> um<00:12:09.760> and<00:12:09.880> we<00:12:10.040> call<00:12:10.279> this<00:12:10.480> Pi 00:12:10.870 --> 00:12:10.880 align:start position:0% that don't um and we call this Pi 00:12:10.880 --> 00:12:13.230 align:start position:0% that don't um and we call this Pi steering<00:12:11.760> um<00:12:11.880> this<00:12:12.000> is<00:12:12.160> something<00:12:12.519> that's<00:12:13.000> on 00:12:13.230 --> 00:12:13.240 align:start position:0% steering um this is something that's on 00:12:13.240 --> 00:12:16.230 align:start position:0% steering um this is something that's on the<00:12:14.079> uh<00:12:14.360> road<00:12:14.680> map<00:12:15.199> to<00:12:15.360> being<00:12:15.639> implemented<00:12:16.120> in 00:12:16.230 --> 00:12:16.240 align:start position:0% the uh road map to being implemented in 00:12:16.240 --> 00:12:18.509 align:start position:0% the uh road map to being implemented in the<00:12:16.360> dev<00:12:16.600> PTP 00:12:18.509 --> 00:12:18.519 align:start position:0% the dev PTP 00:12:18.519 --> 00:12:20.990 align:start position:0% the dev PTP protocol<00:12:19.519> um<00:12:19.800> and<00:12:19.920> the<00:12:20.040> second<00:12:20.279> one<00:12:20.440> is<00:12:20.720> is 00:12:20.990 --> 00:12:21.000 align:start position:0% protocol um and the second one is is 00:12:21.000 --> 00:12:22.590 align:start position:0% protocol um and the second one is is active<00:12:21.320> routing<00:12:21.720> this<00:12:21.839> is<00:12:22.000> essentially<00:12:22.440> where 00:12:22.590 --> 00:12:22.600 align:start position:0% active routing this is essentially where 00:12:22.600 --> 00:12:24.790 align:start position:0% active routing this is essentially where we<00:12:22.720> form<00:12:23.000> what<00:12:23.120> I've<00:12:23.279> called<00:12:23.480> topic<00:12:23.800> vortices 00:12:24.790 --> 00:12:24.800 align:start position:0% we form what I've called topic vortices 00:12:24.800 --> 00:12:29.389 align:start position:0% we form what I've called topic vortices or<00:12:25.440> where<00:12:25.720> I<00:12:26.160> advertise<00:12:27.160> that<00:12:27.360> I<00:12:27.519> want<00:12:28.440> um<00:12:29.000> uh 00:12:29.389 --> 00:12:29.399 align:start position:0% or where I advertise that I want um uh 00:12:29.399 --> 00:12:30.990 align:start position:0% or where I advertise that I want um uh I'm<00:12:29.600> interested<00:12:30.120> in<00:12:30.279> these<00:12:30.519> particular 00:12:30.990 --> 00:12:31.000 align:start position:0% I'm interested in these particular 00:12:31.000 --> 00:12:33.430 align:start position:0% I'm interested in these particular topics<00:12:31.600> well<00:12:31.959> technically<00:12:32.440> partial<00:12:32.800> topics 00:12:33.430 --> 00:12:33.440 align:start position:0% topics well technically partial topics 00:12:33.440 --> 00:12:35.949 align:start position:0% topics well technically partial topics and<00:12:33.560> my<00:12:33.760> peers<00:12:34.240> pass<00:12:34.440> on<00:12:34.680> messages<00:12:35.120> to<00:12:35.320> me<00:12:35.800> and 00:12:35.949 --> 00:12:35.959 align:start position:0% and my peers pass on messages to me and 00:12:35.959 --> 00:12:37.790 align:start position:0% and my peers pass on messages to me and they<00:12:36.120> select<00:12:36.600> messages<00:12:37.000> they<00:12:37.199> also<00:12:37.480> pass<00:12:37.639> on 00:12:37.790 --> 00:12:37.800 align:start position:0% they select messages they also pass on 00:12:37.800 --> 00:12:40.110 align:start position:0% they select messages they also pass on to<00:12:38.040> their<00:12:38.240> peers<00:12:39.000> the<00:12:39.160> messages<00:12:39.639> that<00:12:39.880> I'm 00:12:40.110 --> 00:12:40.120 align:start position:0% to their peers the messages that I'm 00:12:40.120 --> 00:12:41.949 align:start position:0% to their peers the messages that I'm interested<00:12:40.560> in<00:12:40.920> although<00:12:41.320> because<00:12:41.600> obviously 00:12:41.949 --> 00:12:41.959 align:start position:0% interested in although because obviously 00:12:41.959 --> 00:12:44.030 align:start position:0% interested in although because obviously it's<00:12:42.079> an<00:12:42.240> exponential<00:12:42.760> tradeoff<00:12:43.519> it<00:12:43.680> does<00:12:43.839> so 00:12:44.030 --> 00:12:44.040 align:start position:0% it's an exponential tradeoff it does so 00:12:44.040 --> 00:12:49.870 align:start position:0% it's an exponential tradeoff it does so at<00:12:44.160> a<00:12:44.279> relatively<00:12:45.000> uh<00:12:45.199> lower<00:12:45.839> accuracy 00:12:49.870 --> 00:12:49.880 align:start position:0% 00:12:49.880 --> 00:12:55.710 align:start position:0% level<00:12:50.880> so<00:12:51.760> in<00:12:51.959> terms<00:12:52.519> of<00:12:53.399> um<00:12:53.560> forwarding 00:12:55.710 --> 00:12:55.720 align:start position:0% level so in terms of um forwarding 00:12:55.720 --> 00:13:00.150 align:start position:0% level so in terms of um forwarding messages<00:12:56.720> we<00:12:57.040> have<00:12:57.839> this<00:12:58.120> notion<00:12:58.760> of<00:12:59.360> serving 00:13:00.150 --> 00:13:00.160 align:start position:0% messages we have this notion of serving 00:13:00.160 --> 00:13:02.629 align:start position:0% messages we have this notion of serving one's<00:13:00.839> one's<00:13:01.160> friends<00:13:01.600> well<00:13:02.000> we<00:13:02.120> want<00:13:02.320> them<00:13:02.440> to 00:13:02.629 --> 00:13:02.639 align:start position:0% one's one's friends well we want them to 00:13:02.639 --> 00:13:04.590 align:start position:0% one's one's friends well we want them to stay<00:13:02.920> our<00:13:03.199> peers<00:13:03.639> in<00:13:03.800> general<00:13:04.199> we<00:13:04.279> don't<00:13:04.440> want 00:13:04.590 --> 00:13:04.600 align:start position:0% stay our peers in general we don't want 00:13:04.600 --> 00:13:08.110 align:start position:0% stay our peers in general we don't want them<00:13:04.680> to<00:13:04.839> go<00:13:05.040> away<00:13:05.760> and<00:13:05.959> so<00:13:06.760> we<00:13:07.360> uh<00:13:07.480> we<00:13:07.600> want<00:13:07.800> to 00:13:08.110 --> 00:13:08.120 align:start position:0% them to go away and so we uh we want to 00:13:08.120 --> 00:13:10.629 align:start position:0% them to go away and so we uh we want to give<00:13:08.360> them<00:13:08.800> we<00:13:08.920> want<00:13:09.120> to<00:13:09.680> behave<00:13:10.120> well<00:13:10.399> we<00:13:10.519> want 00:13:10.629 --> 00:13:10.639 align:start position:0% give them we want to behave well we want 00:13:10.639 --> 00:13:11.829 align:start position:0% give them we want to behave well we want to<00:13:10.800> actually<00:13:11.040> give<00:13:11.199> them<00:13:11.360> stuff<00:13:11.600> they're 00:13:11.829 --> 00:13:11.839 align:start position:0% to actually give them stuff they're 00:13:11.839 --> 00:13:15.350 align:start position:0% to actually give them stuff they're interested<00:13:12.639> in<00:13:13.639> uh<00:13:13.839> what<00:13:14.079> there<00:13:14.160> are<00:13:14.399> three 00:13:15.350 --> 00:13:15.360 align:start position:0% interested in uh what there are three 00:13:15.360 --> 00:13:16.870 align:start position:0% interested in uh what there are three basic<00:13:15.680> ways<00:13:15.880> of<00:13:16.000> determining<00:13:16.519> this<00:13:16.680> within 00:13:16.870 --> 00:13:16.880 align:start position:0% basic ways of determining this within 00:13:16.880 --> 00:13:18.629 align:start position:0% basic ways of determining this within the<00:13:16.959> whisper<00:13:17.279> protocol<00:13:17.839> one<00:13:18.000> is<00:13:18.160> interesting 00:13:18.629 --> 00:13:18.639 align:start position:0% the whisper protocol one is interesting 00:13:18.639 --> 00:13:19.910 align:start position:0% the whisper protocol one is interesting topics<00:13:18.920> so<00:13:19.079> the<00:13:19.199> topics<00:13:19.440> that<00:13:19.560> we've<00:13:19.720> already 00:13:19.910 --> 00:13:19.920 align:start position:0% topics so the topics that we've already 00:13:19.920 --> 00:13:21.389 align:start position:0% topics so the topics that we've already told<00:13:20.160> them<00:13:20.360> hey<00:13:20.519> we're<00:13:20.680> interested<00:13:21.040> in<00:13:21.199> this 00:13:21.389 --> 00:13:21.399 align:start position:0% told them hey we're interested in this 00:13:21.399 --> 00:13:23.069 align:start position:0% told them hey we're interested in this stuff<00:13:22.000> you<00:13:22.120> should<00:13:22.360> give<00:13:22.480> us<00:13:22.680> message<00:13:23.000> you 00:13:23.069 --> 00:13:23.079 align:start position:0% stuff you should give us message you 00:13:23.079 --> 00:13:25.590 align:start position:0% stuff you should give us message you should<00:13:23.320> pass<00:13:23.480> on<00:13:23.680> messages<00:13:24.639> um<00:13:24.959> that<00:13:25.160> that<00:13:25.279> are 00:13:25.590 --> 00:13:25.600 align:start position:0% should pass on messages um that that are 00:13:25.600 --> 00:13:28.509 align:start position:0% should pass on messages um that that are actually<00:13:26.600> uh<00:13:26.839> conform<00:13:27.240> to<00:13:27.480> this<00:13:28.120> another<00:13:28.399> is 00:13:28.509 --> 00:13:28.519 align:start position:0% actually uh conform to this another is 00:13:28.519 --> 00:13:30.269 align:start position:0% actually uh conform to this another is the<00:13:28.639> lowest<00:13:28.920> time<00:13:29.120> time<00:13:29.279> to 00:13:30.269 --> 00:13:30.279 align:start position:0% the lowest time time to 00:13:30.279 --> 00:13:33.710 align:start position:0% the lowest time time to live<00:13:31.279> so<00:13:31.440> we<00:13:31.560> want<00:13:31.720> to<00:13:32.519> um<00:13:33.040> prioritize 00:13:33.710 --> 00:13:33.720 align:start position:0% live so we want to um prioritize 00:13:33.720 --> 00:13:35.990 align:start position:0% live so we want to um prioritize messages<00:13:34.199> that<00:13:34.279> are<00:13:34.480> actually<00:13:34.839> urgent<00:13:35.839> and 00:13:35.990 --> 00:13:36.000 align:start position:0% messages that are actually urgent and 00:13:36.000 --> 00:13:37.509 align:start position:0% messages that are actually urgent and the<00:13:36.120> third<00:13:36.360> is<00:13:36.480> the<00:13:36.600> highest<00:13:36.839> proof<00:13:37.079> of<00:13:37.199> work 00:13:37.509 --> 00:13:37.519 align:start position:0% the third is the highest proof of work 00:13:37.519 --> 00:13:39.230 align:start position:0% the third is the highest proof of work so<00:13:37.760> each<00:13:37.959> message<00:13:38.279> actually<00:13:38.560> has<00:13:38.760> an<00:13:39.120> an 00:13:39.230 --> 00:13:39.240 align:start position:0% so each message actually has an an 00:13:39.240 --> 00:13:41.509 align:start position:0% so each message actually has an an Associated<00:13:39.760> proof<00:13:40.000> of<00:13:40.120> work<00:13:40.360> which<00:13:40.600> basically 00:13:41.509 --> 00:13:41.519 align:start position:0% Associated proof of work which basically 00:13:41.519 --> 00:13:43.949 align:start position:0% Associated proof of work which basically um<00:13:42.279> you<00:13:42.399> know<00:13:42.720> similar<00:13:43.040> sort<00:13:43.199> of<00:13:43.279> thing<00:13:43.399> to<00:13:43.839> to 00:13:43.949 --> 00:13:43.959 align:start position:0% um you know similar sort of thing to to 00:13:43.959 --> 00:13:46.150 align:start position:0% um you know similar sort of thing to to the<00:13:44.079> blockchain<00:13:44.600> it<00:13:44.959> um<00:13:45.399> it<00:13:45.560> Associates 00:13:46.150 --> 00:13:46.160 align:start position:0% the blockchain it um it Associates 00:13:46.160 --> 00:13:48.269 align:start position:0% the blockchain it um it Associates particular<00:13:46.440> amount<00:13:46.600> of<00:13:46.760> computation<00:13:47.760> um<00:13:48.040> to 00:13:48.269 --> 00:13:48.279 align:start position:0% particular amount of computation um to 00:13:48.279 --> 00:13:52.269 align:start position:0% particular amount of computation um to this<00:13:48.480> particular 00:13:52.269 --> 00:13:52.279 align:start position:0% 00:13:52.279 --> 00:13:53.910 align:start position:0% message 00:13:53.910 --> 00:13:53.920 align:start position:0% message 00:13:53.920 --> 00:13:58.269 align:start position:0% message the<00:13:54.920> way<00:13:55.279> that<00:13:55.560> we<00:13:55.839> tell<00:13:56.440> our<00:13:57.120> peers<00:13:57.880> about 00:13:58.269 --> 00:13:58.279 align:start position:0% the way that we tell our peers about 00:13:58.279 --> 00:14:01.470 align:start position:0% the way that we tell our peers about messages<00:13:58.839> that<00:13:59.199> we<00:13:59.399> are<00:14:00.079> um<00:14:00.800> interested<00:14:01.199> in 00:14:01.470 --> 00:14:01.480 align:start position:0% messages that we are um interested in 00:14:01.480 --> 00:14:02.990 align:start position:0% messages that we are um interested in topics<00:14:01.759> that<00:14:01.880> we're<00:14:02.040> interested<00:14:02.320> in<00:14:02.440> is<00:14:02.600> using 00:14:02.990 --> 00:14:03.000 align:start position:0% topics that we're interested in is using 00:14:03.000 --> 00:14:04.670 align:start position:0% topics that we're interested in is using this<00:14:03.240> this<00:14:03.360> sort<00:14:03.519> of<00:14:03.639> masking<00:14:04.199> filtering 00:14:04.670 --> 00:14:04.680 align:start position:0% this this sort of masking filtering 00:14:04.680 --> 00:14:06.910 align:start position:0% this this sort of masking filtering approach<00:14:05.320> you<00:14:05.519> actually<00:14:05.720> use<00:14:05.959> Bloom<00:14:06.240> filters 00:14:06.910 --> 00:14:06.920 align:start position:0% approach you actually use Bloom filters 00:14:06.920 --> 00:14:08.430 align:start position:0% approach you actually use Bloom filters and<00:14:07.079> we<00:14:07.240> pass<00:14:07.440> the<00:14:07.519> bloom<00:14:07.800> filters<00:14:08.120> to<00:14:08.279> our 00:14:08.430 --> 00:14:08.440 align:start position:0% and we pass the bloom filters to our 00:14:08.440 --> 00:14:10.509 align:start position:0% and we pass the bloom filters to our peers<00:14:09.240> and<00:14:09.360> then<00:14:09.560> they<00:14:09.680> can<00:14:09.880> actually<00:14:10.120> test<00:14:10.399> to 00:14:10.509 --> 00:14:10.519 align:start position:0% peers and then they can actually test to 00:14:10.519 --> 00:14:12.550 align:start position:0% peers and then they can actually test to see<00:14:10.720> whether<00:14:11.000> particular<00:14:11.399> messages<00:14:12.240> match 00:14:12.550 --> 00:14:12.560 align:start position:0% see whether particular messages match 00:14:12.560 --> 00:14:14.110 align:start position:0% see whether particular messages match these<00:14:12.720> Bloom<00:14:13.040> filters<00:14:13.360> and<00:14:13.519> if<00:14:13.680> they<00:14:13.800> do<00:14:14.040> they 00:14:14.110 --> 00:14:14.120 align:start position:0% these Bloom filters and if they do they 00:14:14.120 --> 00:14:16.230 align:start position:0% these Bloom filters and if they do they can<00:14:14.240> send<00:14:14.480> on<00:14:14.639> to<00:14:14.800> us<00:14:15.320> they<00:14:15.399> can<00:14:15.600> combine<00:14:15.920> Bloom 00:14:16.230 --> 00:14:16.240 align:start position:0% can send on to us they can combine Bloom 00:14:16.240 --> 00:14:17.910 align:start position:0% can send on to us they can combine Bloom filters<00:14:16.560> and<00:14:16.680> send<00:14:16.920> on<00:14:17.079> to<00:14:17.240> their<00:14:17.440> peers<00:14:17.800> so 00:14:17.910 --> 00:14:17.920 align:start position:0% filters and send on to their peers so 00:14:17.920 --> 00:14:20.509 align:start position:0% filters and send on to their peers so that<00:14:18.079> their<00:14:18.240> peers<00:14:18.959> tend<00:14:19.240> to<00:14:19.959> tend<00:14:20.160> to<00:14:20.320> give 00:14:20.509 --> 00:14:20.519 align:start position:0% that their peers tend to tend to give 00:14:20.519 --> 00:14:22.590 align:start position:0% that their peers tend to tend to give them<00:14:20.720> messages<00:14:21.160> that<00:14:21.360> we<00:14:21.560> can<00:14:21.800> then<00:14:22.160> uh<00:14:22.279> we<00:14:22.399> may 00:14:22.590 --> 00:14:22.600 align:start position:0% them messages that we can then uh we may 00:14:22.600 --> 00:14:24.030 align:start position:0% them messages that we can then uh we may then<00:14:22.759> be<00:14:22.880> interested 00:14:24.030 --> 00:14:24.040 align:start position:0% then be interested 00:14:24.040 --> 00:14:26.590 align:start position:0% then be interested in<00:14:25.040> these<00:14:25.519> uh<00:14:25.639> this<00:14:25.800> kind<00:14:25.920> of<00:14:26.040> filtering<00:14:26.480> can 00:14:26.590 --> 00:14:26.600 align:start position:0% in these uh this kind of filtering can 00:14:26.600 --> 00:14:28.829 align:start position:0% in these uh this kind of filtering can be<00:14:26.759> customized<00:14:27.560> potentially<00:14:28.040> per<00:14:28.279> Pier<00:14:28.680> or 00:14:28.829 --> 00:14:28.839 align:start position:0% be customized potentially per Pier or 00:14:28.839 --> 00:14:30.509 align:start position:0% be customized potentially per Pier or even<00:14:29.320> per<00:14:29.600> application<00:14:30.079> so<00:14:30.279> that 00:14:30.509 --> 00:14:30.519 align:start position:0% even per application so that 00:14:30.519 --> 00:14:31.790 align:start position:0% even per application so that applications<00:14:31.040> that<00:14:31.199> may<00:14:31.360> have<00:14:31.560> very 00:14:31.790 --> 00:14:31.800 align:start position:0% applications that may have very 00:14:31.800 --> 00:14:34.430 align:start position:0% applications that may have very sensitive<00:14:32.800> um<00:14:33.040> topics<00:14:33.600> we<00:14:33.759> tend<00:14:34.079> not<00:14:34.240> to 00:14:34.430 --> 00:14:34.440 align:start position:0% sensitive um topics we tend not to 00:14:34.440 --> 00:14:37.470 align:start position:0% sensitive um topics we tend not to advertise<00:14:34.880> to<00:14:35.000> our<00:14:35.160> peers<00:14:35.759> applications<00:14:36.759> that 00:14:37.470 --> 00:14:37.480 align:start position:0% advertise to our peers applications that 00:14:37.480 --> 00:14:39.470 align:start position:0% advertise to our peers applications that that<00:14:37.639> are<00:14:37.800> not<00:14:38.040> in<00:14:38.680> sorry<00:14:38.959> that<00:14:39.040> are<00:14:39.199> not 00:14:39.470 --> 00:14:39.480 align:start position:0% that are not in sorry that are not 00:14:39.480 --> 00:14:42.350 align:start position:0% that are not in sorry that are not sensitive<00:14:39.959> at<00:14:40.079> all<00:14:40.320> but<00:14:40.519> actually<00:14:40.880> do<00:14:41.160> need<00:14:42.160> um 00:14:42.350 --> 00:14:42.360 align:start position:0% sensitive at all but actually do need um 00:14:42.360 --> 00:14:44.749 align:start position:0% sensitive at all but actually do need um to<00:14:42.759> have<00:14:43.399> uh<00:14:43.680> much<00:14:43.880> more<00:14:44.079> real-time 00:14:44.749 --> 00:14:44.759 align:start position:0% to have uh much more real-time 00:14:44.759 --> 00:14:48.870 align:start position:0% to have uh much more real-time characteristics<00:14:45.759> for<00:14:45.959> example<00:14:46.480> maybe<00:14:47.480> um<00:14:48.120> a 00:14:48.870 --> 00:14:48.880 align:start position:0% characteristics for example maybe um a 00:14:48.880 --> 00:14:52.749 align:start position:0% characteristics for example maybe um a uh<00:14:49.360> an<00:14:49.560> exchange<00:14:50.519> application<00:14:51.519> um<00:14:51.920> they<00:14:52.120> would 00:14:52.749 --> 00:14:52.759 align:start position:0% uh an exchange application um they would 00:14:52.759 --> 00:14:55.110 align:start position:0% uh an exchange application um they would uh<00:14:53.560> they<00:14:53.680> would<00:14:53.880> sort<00:14:54.079> of<00:14:54.399> be<00:14:54.639> much<00:14:54.839> more 00:14:55.110 --> 00:14:55.120 align:start position:0% uh they would sort of be much more 00:14:55.120 --> 00:14:56.910 align:start position:0% uh they would sort of be much more aggressive<00:14:55.600> in<00:14:55.759> telling<00:14:56.240> their<00:14:56.560> in<00:14:56.680> telling 00:14:56.910 --> 00:14:56.920 align:start position:0% aggressive in telling their in telling 00:14:56.920 --> 00:14:58.550 align:start position:0% aggressive in telling their in telling the<00:14:57.040> peers<00:14:57.839> what<00:14:57.959> it<00:14:58.079> is<00:14:58.279> that<00:14:58.399> they're 00:14:58.550 --> 00:14:58.560 align:start position:0% the peers what it is that they're 00:14:58.560 --> 00:15:01.389 align:start position:0% the peers what it is that they're interested<00:14:58.920> in 00:15:01.389 --> 00:15:01.399 align:start position:0% 00:15:01.399 --> 00:15:04.590 align:start position:0% um<00:15:02.399> yeah<00:15:02.639> I'll<00:15:02.800> go<00:15:02.959> into<00:15:03.199> that<00:15:03.560> a<00:15:03.759> little<00:15:04.120> later 00:15:04.590 --> 00:15:04.600 align:start position:0% um yeah I'll go into that a little later 00:15:04.600 --> 00:15:08.910 align:start position:0% um yeah I'll go into that a little later so<00:15:05.120> the<00:15:05.320> API<00:15:06.240> um<00:15:06.560> has<00:15:07.120> three<00:15:08.120> um<00:15:08.680> three 00:15:08.910 --> 00:15:08.920 align:start position:0% so the API um has three um three 00:15:08.920 --> 00:15:10.710 align:start position:0% so the API um has three um three functions<00:15:09.399> is<00:15:09.600> super<00:15:09.880> simple<00:15:10.279> right<00:15:10.480> new 00:15:10.710 --> 00:15:10.720 align:start position:0% functions is super simple right new 00:15:10.720 --> 00:15:12.509 align:start position:0% functions is super simple right new identity<00:15:11.320> which<00:15:11.480> creates<00:15:11.759> a<00:15:11.880> new<00:15:12.000> whisper 00:15:12.509 --> 00:15:12.519 align:start position:0% identity which creates a new whisper 00:15:12.519 --> 00:15:15.910 align:start position:0% identity which creates a new whisper identity<00:15:13.519> um<00:15:14.320> uh<00:15:14.519> post<00:15:15.279> and<00:15:15.480> actually<00:15:15.759> that's 00:15:15.910 --> 00:15:15.920 align:start position:0% identity um uh post and actually that's 00:15:15.920 --> 00:15:18.310 align:start position:0% identity um uh post and actually that's changed<00:15:16.240> it<00:15:16.360> was<00:15:16.600> watch<00:15:16.839> it's<00:15:16.959> now<00:15:17.160> filter<00:15:18.120> um 00:15:18.310 --> 00:15:18.320 align:start position:0% changed it was watch it's now filter um 00:15:18.320 --> 00:15:20.389 align:start position:0% changed it was watch it's now filter um post<00:15:18.839> just<00:15:19.160> sets<00:15:19.440> a<00:15:19.560> message<00:15:19.800> off<00:15:19.959> onto<00:15:20.199> the 00:15:20.389 --> 00:15:20.399 align:start position:0% post just sets a message off onto the 00:15:20.399 --> 00:15:23.150 align:start position:0% post just sets a message off onto the network<00:15:21.320> and<00:15:21.759> uh<00:15:21.880> the<00:15:21.959> filter<00:15:22.360> is<00:15:22.519> able<00:15:22.720> to<00:15:23.000> set 00:15:23.150 --> 00:15:23.160 align:start position:0% network and uh the filter is able to set 00:15:23.160 --> 00:15:26.150 align:start position:0% network and uh the filter is able to set up<00:15:23.920> um<00:15:24.120> filters<00:15:24.759> and<00:15:24.920> check<00:15:25.160> to<00:15:25.360> see<00:15:25.920> which 00:15:26.150 --> 00:15:26.160 align:start position:0% up um filters and check to see which 00:15:26.160 --> 00:15:27.949 align:start position:0% up um filters and check to see which messages<00:15:26.600> have<00:15:26.759> already 00:15:27.949 --> 00:15:27.959 align:start position:0% messages have already 00:15:27.959 --> 00:15:29.870 align:start position:0% messages have already arrived<00:15:29.000> there's<00:15:29.160> an<00:15:29.279> example<00:15:29.560> of<00:15:29.680> new 00:15:29.870 --> 00:15:29.880 align:start position:0% arrived there's an example of new 00:15:29.880 --> 00:15:32.309 align:start position:0% arrived there's an example of new identity<00:15:30.440> it's<00:15:30.639> pretty<00:15:30.880> simple<00:15:31.800> um<00:15:31.920> you<00:15:32.040> get<00:15:32.160> a 00:15:32.309 --> 00:15:32.319 align:start position:0% identity it's pretty simple um you get a 00:15:32.319 --> 00:15:35.949 align:start position:0% identity it's pretty simple um you get a key<00:15:32.759> back<00:15:33.759> um<00:15:34.000> there's<00:15:34.199> an<00:15:34.360> example<00:15:34.720> of<00:15:34.959> post 00:15:35.949 --> 00:15:35.959 align:start position:0% key back um there's an example of post 00:15:35.959 --> 00:15:37.790 align:start position:0% key back um there's an example of post um<00:15:36.399> this<00:15:36.519> is<00:15:36.720> a<00:15:36.839> bit<00:15:37.000> more<00:15:37.160> interesting<00:15:37.560> we<00:15:37.639> can 00:15:37.790 --> 00:15:37.800 align:start position:0% um this is a bit more interesting we can 00:15:37.800 --> 00:15:39.870 align:start position:0% um this is a bit more interesting we can optionally<00:15:38.199> send<00:15:38.399> a<00:15:38.519> from<00:15:38.720> and<00:15:38.839> a<00:15:38.959> two<00:15:39.639> it's<00:15:39.800> a 00:15:39.870 --> 00:15:39.880 align:start position:0% optionally send a from and a two it's a 00:15:39.880 --> 00:15:41.749 align:start position:0% optionally send a from and a two it's a bit<00:15:40.040> odd<00:15:40.240> to<00:15:40.360> have<00:15:40.440> an<00:15:40.600> optional<00:15:40.959> from<00:15:41.440> right 00:15:41.749 --> 00:15:41.759 align:start position:0% bit odd to have an optional from right 00:15:41.759 --> 00:15:43.710 align:start position:0% bit odd to have an optional from right because<00:15:42.279> normally<00:15:42.680> as<00:15:42.839> part<00:15:43.000> of<00:15:43.079> an<00:15:43.199> API<00:15:43.600> we 00:15:43.710 --> 00:15:43.720 align:start position:0% because normally as part of an API we 00:15:43.720 --> 00:15:46.030 align:start position:0% because normally as part of an API we don't<00:15:43.920> get<00:15:44.079> the<00:15:44.480> automatic<00:15:45.480> the<00:15:45.560> automatic 00:15:46.030 --> 00:15:46.040 align:start position:0% don't get the automatic the automatic 00:15:46.040 --> 00:15:48.389 align:start position:0% don't get the automatic the automatic ability<00:15:46.399> to<00:15:46.600> anonymize<00:15:47.160> our<00:15:47.360> messages<00:15:48.279> this 00:15:48.389 --> 00:15:48.399 align:start position:0% ability to anonymize our messages this 00:15:48.399 --> 00:15:50.749 align:start position:0% ability to anonymize our messages this one<00:15:48.600> does<00:15:49.519> um<00:15:49.680> it's<00:15:49.880> also<00:15:50.079> got<00:15:50.199> a<00:15:50.319> two<00:15:50.639> we 00:15:50.749 --> 00:15:50.759 align:start position:0% one does um it's also got a two we 00:15:50.759 --> 00:15:54.550 align:start position:0% one does um it's also got a two we canuto<00:15:51.199> we<00:15:51.319> can<00:15:51.839> um<00:15:52.480> actually<00:15:52.759> do<00:15:53.240> a<00:15:53.560> broadcast 00:15:54.550 --> 00:15:54.560 align:start position:0% canuto we can um actually do a broadcast 00:15:54.560 --> 00:15:56.710 align:start position:0% canuto we can um actually do a broadcast um<00:15:54.839> right<00:15:55.040> from<00:15:55.240> within<00:15:55.800> uh<00:15:55.920> from<00:15:56.079> within<00:15:56.360> here 00:15:56.710 --> 00:15:56.720 align:start position:0% um right from within uh from within here 00:15:56.720 --> 00:15:58.990 align:start position:0% um right from within uh from within here that<00:15:56.959> actually<00:15:57.240> means<00:15:57.800> comparatively<00:15:58.480> little 00:15:58.990 --> 00:15:59.000 align:start position:0% that actually means comparatively little 00:15:59.000 --> 00:16:00.550 align:start position:0% that actually means comparatively little because<00:15:59.120> we<00:15:59.240> have<00:15:59.399> topics<00:15:59.680> to<00:15:59.880> identify<00:16:00.399> the 00:16:00.550 --> 00:16:00.560 align:start position:0% because we have topics to identify the 00:16:00.560 --> 00:16:01.870 align:start position:0% because we have topics to identify the sorts<00:16:00.839> of<00:16:01.040> things<00:16:01.240> that<00:16:01.399> this<00:16:01.519> message<00:16:01.759> is 00:16:01.870 --> 00:16:01.880 align:start position:0% sorts of things that this message is 00:16:01.880 --> 00:16:03.590 align:start position:0% sorts of things that this message is going<00:16:01.959> to<00:16:02.120> contain<00:16:02.839> which<00:16:03.000> then<00:16:03.120> allows<00:16:03.480> the 00:16:03.590 --> 00:16:03.600 align:start position:0% going to contain which then allows the 00:16:03.600 --> 00:16:04.910 align:start position:0% going to contain which then allows the potential<00:16:04.000> recipients<00:16:04.480> to<00:16:04.639> actually 00:16:04.910 --> 00:16:04.920 align:start position:0% potential recipients to actually 00:16:04.920 --> 00:16:06.749 align:start position:0% potential recipients to actually identify<00:16:05.519> this<00:16:05.920> from<00:16:06.120> all<00:16:06.240> of<00:16:06.360> the<00:16:06.440> various 00:16:06.749 --> 00:16:06.759 align:start position:0% identify this from all of the various 00:16:06.759 --> 00:16:08.790 align:start position:0% identify this from all of the various other<00:16:07.040> unicast<00:16:07.560> message<00:16:07.959> sorry<00:16:08.160> broadcast 00:16:08.790 --> 00:16:08.800 align:start position:0% other unicast message sorry broadcast 00:16:08.800 --> 00:16:12.430 align:start position:0% other unicast message sorry broadcast messages<00:16:09.800> um<00:16:10.079> we<00:16:10.199> have<00:16:10.319> the<00:16:10.480> payload<00:16:11.480> that's<00:16:12.079> U 00:16:12.430 --> 00:16:12.440 align:start position:0% messages um we have the payload that's U 00:16:12.440 --> 00:16:13.949 align:start position:0% messages um we have the payload that's U simply<00:16:12.759> a<00:16:12.880> bunch<00:16:13.040> of<00:16:13.199> data<00:16:13.519> that<00:16:13.680> that's<00:16:13.839> the 00:16:13.949 --> 00:16:13.959 align:start position:0% simply a bunch of data that that's the 00:16:13.959 --> 00:16:15.749 align:start position:0% simply a bunch of data that that's the actual<00:16:14.240> body<00:16:14.480> of<00:16:14.600> the<00:16:14.680> message<00:16:15.319> and<00:16:15.440> a<00:16:15.560> couple 00:16:15.749 --> 00:16:15.759 align:start position:0% actual body of the message and a couple 00:16:15.759 --> 00:16:17.470 align:start position:0% actual body of the message and a couple of<00:16:15.880> other<00:16:16.079> things<00:16:16.519> priority<00:16:17.079> which<00:16:17.199> is<00:16:17.360> the 00:16:17.470 --> 00:16:17.480 align:start position:0% of other things priority which is the 00:16:17.480 --> 00:16:19.150 align:start position:0% of other things priority which is the amount<00:16:17.680> of<00:16:17.839> work<00:16:18.040> we're<00:16:18.199> going<00:16:18.279> to<00:16:18.399> put<00:16:18.560> in<00:16:18.959> and 00:16:19.150 --> 00:16:19.160 align:start position:0% amount of work we're going to put in and 00:16:19.160 --> 00:16:21.110 align:start position:0% amount of work we're going to put in and therefore<00:16:19.440> that's<00:16:19.680> going<00:16:19.839> to<00:16:20.360> alter<00:16:20.839> How 00:16:21.110 --> 00:16:21.120 align:start position:0% therefore that's going to alter How 00:16:21.120 --> 00:16:23.710 align:start position:0% therefore that's going to alter How likely<00:16:21.440> it<00:16:21.519> is<00:16:21.800> other<00:16:22.040> nodes<00:16:22.440> to<00:16:23.120> um<00:16:23.279> to<00:16:23.560> pass 00:16:23.710 --> 00:16:23.720 align:start position:0% likely it is other nodes to um to pass 00:16:23.720 --> 00:16:25.749 align:start position:0% likely it is other nodes to um to pass on<00:16:23.959> this<00:16:24.120> message<00:16:24.440> sooner<00:16:25.120> and<00:16:25.240> a<00:16:25.399> time<00:16:25.560> to 00:16:25.749 --> 00:16:25.759 align:start position:0% on this message sooner and a time to 00:16:25.759 --> 00:16:27.509 align:start position:0% on this message sooner and a time to live<00:16:26.199> which<00:16:26.360> essentially<00:16:26.720> is<00:16:26.880> the<00:16:27.040> expiry 00:16:27.509 --> 00:16:27.519 align:start position:0% live which essentially is the expiry 00:16:27.519 --> 00:16:29.829 align:start position:0% live which essentially is the expiry date<00:16:27.680> for<00:16:27.800> the<00:16:27.920> message 00:16:29.829 --> 00:16:29.839 align:start position:0% date for the message 00:16:29.839 --> 00:16:32.030 align:start position:0% date for the message um<00:16:30.079> watch<00:16:30.399> and<00:16:30.600> again<00:16:30.880> this<00:16:31.000> is<00:16:31.199> filter<00:16:31.759> but 00:16:32.030 --> 00:16:32.040 align:start position:0% um watch and again this is filter but 00:16:32.040 --> 00:16:35.069 align:start position:0% um watch and again this is filter but I'll<00:16:32.399> you'll<00:16:32.600> see<00:16:32.800> that<00:16:33.000> later<00:16:33.880> um<00:16:34.600> optionally 00:16:35.069 --> 00:16:35.079 align:start position:0% I'll you'll see that later um optionally 00:16:35.079 --> 00:16:36.590 align:start position:0% I'll you'll see that later um optionally has<00:16:35.199> a<00:16:35.319> two<00:16:35.639> now<00:16:35.800> this<00:16:35.920> is<00:16:36.160> this<00:16:36.279> is<00:16:36.399> very 00:16:36.590 --> 00:16:36.600 align:start position:0% has a two now this is this is very 00:16:36.600 --> 00:16:38.470 align:start position:0% has a two now this is this is very interesting<00:16:37.079> we<00:16:37.199> don't<00:16:37.519> automatically<00:16:38.279> we're 00:16:38.470 --> 00:16:38.480 align:start position:0% interesting we don't automatically we're 00:16:38.480 --> 00:16:40.470 align:start position:0% interesting we don't automatically we're not<00:16:38.759> automatically<00:16:39.360> able<00:16:39.639> to<00:16:39.800> filter<00:16:40.199> on<00:16:40.319> the 00:16:40.470 --> 00:16:40.480 align:start position:0% not automatically able to filter on the 00:16:40.480 --> 00:16:42.309 align:start position:0% not automatically able to filter on the recipient<00:16:40.920> of<00:16:41.040> the<00:16:41.160> message<00:16:41.680> we<00:16:41.839> have<00:16:41.920> to<00:16:42.040> know 00:16:42.309 --> 00:16:42.319 align:start position:0% recipient of the message we have to know 00:16:42.319 --> 00:16:44.790 align:start position:0% recipient of the message we have to know in<00:16:42.560> advance<00:16:42.959> who<00:16:43.120> the<00:16:43.279> recipient<00:16:43.800> is<00:16:44.399> now<00:16:44.600> if 00:16:44.790 --> 00:16:44.800 align:start position:0% in advance who the recipient is now if 00:16:44.800 --> 00:16:47.829 align:start position:0% in advance who the recipient is now if if<00:16:45.680> if<00:16:45.839> we<00:16:46.079> already<00:16:46.519> kind<00:16:46.680> of<00:16:47.079> if<00:16:47.199> we<00:16:47.399> know<00:16:47.680> that 00:16:47.829 --> 00:16:47.839 align:start position:0% if if we already kind of if we know that 00:16:47.839 --> 00:16:49.269 align:start position:0% if if we already kind of if we know that we<00:16:48.000> actually<00:16:48.240> are<00:16:48.440> going<00:16:48.600> to<00:16:48.720> want<00:16:48.880> to<00:16:49.000> filter 00:16:49.269 --> 00:16:49.279 align:start position:0% we actually are going to want to filter 00:16:49.279 --> 00:16:51.269 align:start position:0% we actually are going to want to filter on<00:16:49.360> the<00:16:49.480> recipient<00:16:49.839> of<00:16:49.959> the<00:16:50.079> message<00:16:50.639> and<00:16:51.160> the 00:16:51.269 --> 00:16:51.279 align:start position:0% on the recipient of the message and the 00:16:51.279 --> 00:16:55.069 align:start position:0% on the recipient of the message and the original<00:16:51.800> sender<00:16:52.800> um<00:16:53.639> knows<00:16:54.079> this<00:16:54.440> they<00:16:54.560> will 00:16:55.069 --> 00:16:55.079 align:start position:0% original sender um knows this they will 00:16:55.079 --> 00:16:57.990 align:start position:0% original sender um knows this they will place<00:16:55.480> that<00:16:55.680> in<00:16:55.880> the<00:16:56.199> topics<00:16:56.759> itself<00:16:57.680> so<00:16:57.839> that 00:16:57.990 --> 00:16:58.000 align:start position:0% place that in the topics itself so that 00:16:58.000 --> 00:17:00.030 align:start position:0% place that in the topics itself so that we<00:16:58.199> can<00:16:58.440> actually<00:16:59.279> filter<00:16:59.680> for<00:16:59.880> these 00:17:00.030 --> 00:17:00.040 align:start position:0% we can actually filter for these 00:17:00.040 --> 00:17:02.030 align:start position:0% we can actually filter for these particular<00:17:00.399> kinds<00:17:00.560> of<00:17:00.680> messages<00:17:01.519> but 00:17:02.030 --> 00:17:02.040 align:start position:0% particular kinds of messages but 00:17:02.040 --> 00:17:04.029 align:start position:0% particular kinds of messages but intrinsically<00:17:02.880> the<00:17:03.040> way<00:17:03.199> that<00:17:03.360> we<00:17:03.560> receive 00:17:04.029 --> 00:17:04.039 align:start position:0% intrinsically the way that we receive 00:17:04.039 --> 00:17:06.150 align:start position:0% intrinsically the way that we receive messages<00:17:04.839> are<00:17:05.079> through<00:17:05.280> the<00:17:05.520> topics<00:17:05.919> they're 00:17:06.150 --> 00:17:06.160 align:start position:0% messages are through the topics they're 00:17:06.160 --> 00:17:07.870 align:start position:0% messages are through the topics they're not<00:17:06.480> through<00:17:07.039> the<00:17:07.160> from<00:17:07.360> and<00:17:07.480> the<00:17:07.600> two<00:17:07.799> the 00:17:07.870 --> 00:17:07.880 align:start position:0% not through the from and the two the 00:17:07.880 --> 00:17:09.309 align:start position:0% not through the from and the two the from<00:17:08.039> and<00:17:08.160> the<00:17:08.240> two<00:17:08.439> are<00:17:08.600> essentially<00:17:09.120> just 00:17:09.309 --> 00:17:09.319 align:start position:0% from and the two are essentially just 00:17:09.319 --> 00:17:11.909 align:start position:0% from and the two are essentially just the<00:17:09.520> keys<00:17:09.880> that<00:17:10.039> we<00:17:10.160> are<00:17:10.760> um<00:17:10.919> signing<00:17:11.400> with<00:17:11.720> or 00:17:11.909 --> 00:17:11.919 align:start position:0% the keys that we are um signing with or 00:17:11.919 --> 00:17:14.949 align:start position:0% the keys that we are um signing with or encrypting 00:17:14.949 --> 00:17:14.959 align:start position:0% 00:17:14.959 --> 00:17:17.909 align:start position:0% with<00:17:15.959> um<00:17:16.360> there's<00:17:16.559> a<00:17:16.760> quick 00:17:17.909 --> 00:17:17.919 align:start position:0% with um there's a quick 00:17:17.919 --> 00:17:20.270 align:start position:0% with um there's a quick example<00:17:18.919> in<00:17:19.079> this<00:17:19.280> example<00:17:19.760> we're<00:17:20.079> we're 00:17:20.270 --> 00:17:20.280 align:start position:0% example in this example we're we're 00:17:20.280 --> 00:17:22.069 align:start position:0% example in this example we're we're creating<00:17:20.600> an<00:17:20.799> identity<00:17:21.360> we're<00:17:21.559> posting<00:17:21.919> a 00:17:22.069 --> 00:17:22.079 align:start position:0% creating an identity we're posting a 00:17:22.079 --> 00:17:23.510 align:start position:0% creating an identity we're posting a message<00:17:22.480> the<00:17:22.600> message<00:17:22.919> is<00:17:23.039> going<00:17:23.120> to<00:17:23.199> be<00:17:23.319> from 00:17:23.510 --> 00:17:23.520 align:start position:0% message the message is going to be from 00:17:23.520 --> 00:17:25.069 align:start position:0% message the message is going to be from our<00:17:23.760> identity<00:17:24.160> so<00:17:24.319> we<00:17:24.400> are<00:17:24.600> actually<00:17:24.839> being 00:17:25.069 --> 00:17:25.079 align:start position:0% our identity so we are actually being 00:17:25.079 --> 00:17:27.309 align:start position:0% our identity so we are actually being honest<00:17:25.360> about<00:17:25.559> it<00:17:25.679> we're<00:17:25.799> saying<00:17:26.039> who<00:17:26.199> we<00:17:26.319> are 00:17:27.309 --> 00:17:27.319 align:start position:0% honest about it we're saying who we are 00:17:27.319 --> 00:17:29.630 align:start position:0% honest about it we're saying who we are um<00:17:27.600> and<00:17:27.880> the<00:17:28.280> uh<00:17:28.400> the<00:17:28.520> topic<00:17:28.960> in<00:17:29.080> this<00:17:29.240> case<00:17:29.440> is 00:17:29.630 --> 00:17:29.640 align:start position:0% um and the uh the topic in this case is 00:17:29.640 --> 00:17:31.950 align:start position:0% um and the uh the topic in this case is the<00:17:30.000> is<00:17:30.160> just<00:17:30.320> an<00:17:30.520> application<00:17:31.039> name<00:17:31.720> and<00:17:31.840> the 00:17:31.950 --> 00:17:31.960 align:start position:0% the is just an application name and the 00:17:31.960 --> 00:17:34.110 align:start position:0% the is just an application name and the payload<00:17:32.520> is<00:17:32.840> is<00:17:33.080> just<00:17:33.200> a<00:17:33.400> message<00:17:33.760> sort<00:17:33.960> of 00:17:34.110 --> 00:17:34.120 align:start position:0% payload is is just a message sort of 00:17:34.120 --> 00:17:37.549 align:start position:0% payload is is just a message sort of saying<00:17:35.000> um<00:17:35.120> you<00:17:35.240> know<00:17:35.440> hi<00:17:35.640> what's<00:17:35.840> your<00:17:36.360> name 00:17:37.549 --> 00:17:37.559 align:start position:0% saying um you know hi what's your name 00:17:37.559 --> 00:17:40.470 align:start position:0% saying um you know hi what's your name um<00:17:38.559> we're<00:17:38.799> also<00:17:39.080> going<00:17:39.200> to<00:17:39.840> have<00:17:40.080> this<00:17:40.320> this 00:17:40.470 --> 00:17:40.480 align:start position:0% um we're also going to have this this 00:17:40.480 --> 00:17:41.990 align:start position:0% um we're also going to have this this watch<00:17:40.760> here<00:17:40.919> which<00:17:41.039> is<00:17:41.200> watching<00:17:41.520> for<00:17:41.760> these 00:17:41.990 --> 00:17:42.000 align:start position:0% watch here which is watching for these 00:17:42.000 --> 00:17:43.390 align:start position:0% watch here which is watching for these kinds<00:17:42.200> of<00:17:42.360> messages<00:17:42.799> so<00:17:42.960> it's<00:17:43.120> actually 00:17:43.390 --> 00:17:43.400 align:start position:0% kinds of messages so it's actually 00:17:43.400 --> 00:17:45.510 align:start position:0% kinds of messages so it's actually watching<00:17:43.760> for<00:17:44.039> this<00:17:44.320> this<00:17:44.480> kind<00:17:44.600> of<00:17:44.880> broadcast 00:17:45.510 --> 00:17:45.520 align:start position:0% watching for this this kind of broadcast 00:17:45.520 --> 00:17:48.549 align:start position:0% watching for this this kind of broadcast message<00:17:46.480> um<00:17:46.880> identified<00:17:47.679> via<00:17:47.960> the<00:17:48.080> fact<00:17:48.360> it's 00:17:48.549 --> 00:17:48.559 align:start position:0% message um identified via the fact it's 00:17:48.559 --> 00:17:50.669 align:start position:0% message um identified via the fact it's actually<00:17:48.919> this<00:17:49.240> this 00:17:50.669 --> 00:17:50.679 align:start position:0% actually this this 00:17:50.679 --> 00:17:53.549 align:start position:0% actually this this application<00:17:51.679> and<00:17:52.320> um<00:17:52.480> when<00:17:52.679> we<00:17:52.919> find<00:17:53.320> this 00:17:53.549 --> 00:17:53.559 align:start position:0% application and um when we find this 00:17:53.559 --> 00:17:55.789 align:start position:0% application and um when we find this what<00:17:53.640> we're<00:17:53.799> going<00:17:53.960> to<00:17:54.120> do<00:17:54.400> is<00:17:54.679> is<00:17:55.159> just<00:17:55.320> log<00:17:55.640> to 00:17:55.789 --> 00:17:55.799 align:start position:0% what we're going to do is is just log to 00:17:55.799 --> 00:17:58.270 align:start position:0% what we're going to do is is just log to the<00:17:55.960> console<00:17:56.520> hey<00:17:56.679> we<00:17:56.840> found<00:17:57.720> someone<00:17:58.000> who's 00:17:58.270 --> 00:17:58.280 align:start position:0% the console hey we found someone who's 00:17:58.280 --> 00:18:00.830 align:start position:0% the console hey we found someone who's who's<00:17:58.480> asking<00:17:58.960> us<00:17:59.120> what<00:17:59.240> our<00:17:59.360> name 00:18:00.830 --> 00:18:00.840 align:start position:0% who's asking us what our name 00:18:00.840 --> 00:18:03.870 align:start position:0% who's asking us what our name is<00:18:01.840> the<00:18:02.320> on<00:18:02.440> the<00:18:02.559> other<00:18:02.840> side<00:18:03.120> what<00:18:03.280> we'<00:18:03.760> we 00:18:03.870 --> 00:18:03.880 align:start position:0% is the on the other side what we' we 00:18:03.880 --> 00:18:05.789 align:start position:0% is the on the other side what we' we would<00:18:04.120> actually<00:18:04.640> uh<00:18:04.799> we'd<00:18:05.039> watch<00:18:05.360> this<00:18:05.640> this 00:18:05.789 --> 00:18:05.799 align:start position:0% would actually uh we'd watch this this 00:18:05.799 --> 00:18:08.830 align:start position:0% would actually uh we'd watch this this broadcast<00:18:07.000> um<00:18:08.000> and<00:18:08.200> potentially<00:18:08.559> we<00:18:08.679> could 00:18:08.830 --> 00:18:08.840 align:start position:0% broadcast um and potentially we could 00:18:08.840 --> 00:18:10.870 align:start position:0% broadcast um and potentially we could reply<00:18:09.120> to<00:18:09.280> it<00:18:09.880> so<00:18:10.080> we<00:18:10.200> would<00:18:10.400> check<00:18:10.559> to<00:18:10.720> make 00:18:10.870 --> 00:18:10.880 align:start position:0% reply to it so we would check to make 00:18:10.880 --> 00:18:12.510 align:start position:0% reply to it so we would check to make sure<00:18:11.080> that<00:18:11.200> it's<00:18:11.360> not<00:18:11.559> us<00:18:11.840> who<00:18:12.000> is<00:18:12.240> who<00:18:12.360> is 00:18:12.510 --> 00:18:12.520 align:start position:0% sure that it's not us who is who is 00:18:12.520 --> 00:18:14.590 align:start position:0% sure that it's not us who is who is actually<00:18:12.760> asking<00:18:13.039> for<00:18:13.240> people's<00:18:13.559> names<00:18:14.440> um 00:18:14.590 --> 00:18:14.600 align:start position:0% actually asking for people's names um 00:18:14.600 --> 00:18:17.029 align:start position:0% actually asking for people's names um assuming<00:18:15.000> it's<00:18:15.200> not<00:18:15.520> then<00:18:15.679> we're<00:18:15.840> going<00:18:16.039> to<00:18:16.799> um 00:18:17.029 --> 00:18:17.039 align:start position:0% assuming it's not then we're going to um 00:18:17.039 --> 00:18:19.669 align:start position:0% assuming it's not then we're going to um simply<00:18:17.559> form<00:18:17.880> a<00:18:18.039> new<00:18:18.280> message<00:18:18.880> back<00:18:19.039> to<00:18:19.280> them 00:18:19.669 --> 00:18:19.679 align:start position:0% simply form a new message back to them 00:18:19.679 --> 00:18:21.270 align:start position:0% simply form a new message back to them we're<00:18:19.799> going<00:18:19.919> to<00:18:20.039> sign<00:18:20.280> it<00:18:20.400> from<00:18:20.600> ourselves 00:18:21.270 --> 00:18:21.280 align:start position:0% we're going to sign it from ourselves 00:18:21.280 --> 00:18:22.549 align:start position:0% we're going to sign it from ourselves we're<00:18:21.440> actually<00:18:21.640> going<00:18:21.760> to<00:18:21.840> use<00:18:22.000> a<00:18:22.159> two<00:18:22.440> in 00:18:22.549 --> 00:18:22.559 align:start position:0% we're actually going to use a two in 00:18:22.559 --> 00:18:24.270 align:start position:0% we're actually going to use a two in this<00:18:22.679> case<00:18:22.880> we're<00:18:23.120> actually<00:18:23.360> going<00:18:23.520> to<00:18:23.720> say 00:18:24.270 --> 00:18:24.280 align:start position:0% this case we're actually going to say 00:18:24.280 --> 00:18:25.909 align:start position:0% this case we're actually going to say who<00:18:24.480> we<00:18:24.600> want<00:18:24.799> the<00:18:24.919> message<00:18:25.200> to<00:18:25.400> arrive<00:18:25.760> at 00:18:25.909 --> 00:18:25.919 align:start position:0% who we want the message to arrive at 00:18:25.919 --> 00:18:27.870 align:start position:0% who we want the message to arrive at it's<00:18:26.080> not<00:18:26.200> a<00:18:26.360> broadcast<00:18:27.360> and<00:18:27.480> we're<00:18:27.640> going<00:18:27.720> to 00:18:27.870 --> 00:18:27.880 align:start position:0% it's not a broadcast and we're going to 00:18:27.880 --> 00:18:29.470 align:start position:0% it's not a broadcast and we're going to identify<00:18:28.360> it<00:18:28.440> with<00:18:28.559> our<00:18:28.880> topics<00:18:29.200> we're<00:18:29.320> also 00:18:29.470 --> 00:18:29.480 align:start position:0% identify it with our topics we're also 00:18:29.480 --> 00:18:31.669 align:start position:0% identify it with our topics we're also going<00:18:29.600> to<00:18:29.720> identify<00:18:30.200> ourselves<00:18:30.640> as<00:18:30.799> being<00:18:31.559> uh 00:18:31.669 --> 00:18:31.679 align:start position:0% going to identify ourselves as being uh 00:18:31.679 --> 00:18:33.470 align:start position:0% going to identify ourselves as being uh as<00:18:31.840> one<00:18:31.960> of<00:18:32.080> the<00:18:32.240> topics<00:18:33.039> um<00:18:33.159> we're<00:18:33.280> going<00:18:33.360> to 00:18:33.470 --> 00:18:33.480 align:start position:0% as one of the topics um we're going to 00:18:33.480 --> 00:18:35.590 align:start position:0% as one of the topics um we're going to put<00:18:33.600> our<00:18:33.799> identity<00:18:34.240> in 00:18:35.590 --> 00:18:35.600 align:start position:0% put our identity in 00:18:35.600 --> 00:18:37.830 align:start position:0% put our identity in there<00:18:36.600> um<00:18:36.760> in<00:18:36.880> terms<00:18:37.080> of<00:18:37.200> where<00:18:37.360> the<00:18:37.480> protocol 00:18:37.830 --> 00:18:37.840 align:start position:0% there um in terms of where the protocol 00:18:37.840 --> 00:18:40.590 align:start position:0% there um in terms of where the protocol is<00:18:37.960> going<00:18:38.840> um<00:18:39.520> one<00:18:39.640> of<00:18:39.799> the<00:18:40.159> couple<00:18:40.360> of<00:18:40.440> things 00:18:40.590 --> 00:18:40.600 align:start position:0% is going um one of the couple of things 00:18:40.600 --> 00:18:42.549 align:start position:0% is going um one of the couple of things that<00:18:40.679> we're<00:18:40.799> going<00:18:40.960> to<00:18:41.120> sort<00:18:41.280> of<00:18:41.559> move<00:18:42.120> uh<00:18:42.240> into 00:18:42.549 --> 00:18:42.559 align:start position:0% that we're going to sort of move uh into 00:18:42.559 --> 00:18:44.350 align:start position:0% that we're going to sort of move uh into soon<00:18:43.039> plausible<00:18:43.480> deniability<00:18:44.120> of<00:18:44.240> the 00:18:44.350 --> 00:18:44.360 align:start position:0% soon plausible deniability of the 00:18:44.360 --> 00:18:46.350 align:start position:0% soon plausible deniability of the authoring<00:18:44.840> which<00:18:44.960> is<00:18:45.080> essentially<00:18:45.480> a<00:18:45.640> case<00:18:45.840> of 00:18:46.350 --> 00:18:46.360 align:start position:0% authoring which is essentially a case of 00:18:46.360 --> 00:18:51.990 align:start position:0% authoring which is essentially a case of having<00:18:46.960> um<00:18:47.400> a<00:18:47.679> future<00:18:48.919> um<00:18:50.400> uh<00:18:51.400> the<00:18:51.520> ability<00:18:51.840> to 00:18:51.990 --> 00:18:52.000 align:start position:0% having um a future um uh the ability to 00:18:52.000 --> 00:18:53.870 align:start position:0% having um a future um uh the ability to have<00:18:52.120> future<00:18:52.480> people<00:18:52.760> looking<00:18:53.000> at<00:18:53.159> messages 00:18:53.870 --> 00:18:53.880 align:start position:0% have future people looking at messages 00:18:53.880 --> 00:18:56.190 align:start position:0% have future people looking at messages not<00:18:54.039> be<00:18:54.200> able<00:18:54.400> to<00:18:54.600> be<00:18:54.919> determine<00:18:55.799> um<00:18:55.960> that<00:18:56.080> it 00:18:56.190 --> 00:18:56.200 align:start position:0% not be able to be determine um that it 00:18:56.200 --> 00:18:58.390 align:start position:0% not be able to be determine um that it was<00:18:56.360> actually<00:18:56.679> us<00:18:56.880> who<00:18:57.039> sent<00:18:57.280> the<00:18:57.440> message<00:18:58.240> um 00:18:58.390 --> 00:18:58.400 align:start position:0% was actually us who sent the message um 00:18:58.400 --> 00:19:00.110 align:start position:0% was actually us who sent the message um but<00:18:58.520> of<00:18:58.760> of<00:18:58.880> course<00:18:59.159> at<00:18:59.320> the<00:18:59.480> time<00:18:59.880> there<00:19:00.000> will 00:19:00.110 --> 00:19:00.120 align:start position:0% but of of course at the time there will 00:19:00.120 --> 00:19:02.510 align:start position:0% but of of course at the time there will be<00:19:00.679> cryptographic<00:19:01.640> certainty<00:19:02.120> that<00:19:02.240> it<00:19:02.360> was 00:19:02.510 --> 00:19:02.520 align:start position:0% be cryptographic certainty that it was 00:19:02.520 --> 00:19:06.149 align:start position:0% be cryptographic certainty that it was us<00:19:03.400> and<00:19:04.080> um<00:19:04.799> modeling<00:19:05.240> on<00:19:05.520> precisely<00:19:06.000> how 00:19:06.149 --> 00:19:06.159 align:start position:0% us and um modeling on precisely how 00:19:06.159 --> 00:19:08.710 align:start position:0% us and um modeling on precisely how scalable<00:19:07.039> uh<00:19:07.200> this<00:19:07.360> approach<00:19:07.720> is<00:19:08.240> and<00:19:08.480> what 00:19:08.710 --> 00:19:08.720 align:start position:0% scalable uh this approach is and what 00:19:08.720 --> 00:19:10.789 align:start position:0% scalable uh this approach is and what the<00:19:09.039> tradeoff<00:19:09.600> is<00:19:09.720> going<00:19:09.799> to<00:19:09.960> be<00:19:10.280> precisely 00:19:10.789 --> 00:19:10.799 align:start position:0% the tradeoff is going to be precisely 00:19:10.799 --> 00:19:12.710 align:start position:0% the tradeoff is going to be precisely between<00:19:11.120> efficiency<00:19:11.559> and 00:19:12.710 --> 00:19:12.720 align:start position:0% between efficiency and 00:19:12.720 --> 00:19:16.630 align:start position:0% between efficiency and privacy<00:19:13.720> so<00:19:14.559> um<00:19:14.960> how<00:19:15.159> much<00:19:15.640> time<00:19:15.880> do<00:19:16.000> I<00:19:16.120> have<00:19:16.400> 10 00:19:16.630 --> 00:19:16.640 align:start position:0% privacy so um how much time do I have 10 00:19:16.640 --> 00:19:19.430 align:start position:0% privacy so um how much time do I have 10 10<00:19:16.799> more<00:19:16.960> minutes<00:19:17.400> right<00:19:17.720> yeah<00:19:18.640> okay<00:19:19.240> let's 00:19:19.430 --> 00:19:19.440 align:start position:0% 10 more minutes right yeah okay let's 00:19:19.440 --> 00:19:23.110 align:start position:0% 10 more minutes right yeah okay let's see<00:19:19.640> if<00:19:19.760> I<00:19:19.880> can<00:19:20.159> give<00:19:20.520> a<00:19:20.799> quick 00:19:23.110 --> 00:19:23.120 align:start position:0% see if I can give a quick 00:19:23.120 --> 00:19:27.830 align:start position:0% see if I can give a quick demo<00:19:24.440> uh<00:19:25.440> how<00:19:25.559> do<00:19:25.679> I<00:19:25.840> get<00:19:25.960> rid<00:19:26.080> of<00:19:26.280> that<00:19:27.000> escape 00:19:27.830 --> 00:19:27.840 align:start position:0% demo uh how do I get rid of that escape 00:19:27.840 --> 00:19:32.149 align:start position:0% demo uh how do I get rid of that escape yeah<00:19:28.480> okay 00:19:32.149 --> 00:19:32.159 align:start position:0% 00:19:32.159 --> 00:19:34.149 align:start position:0% what<00:19:32.320> happened 00:19:34.149 --> 00:19:34.159 align:start position:0% what happened 00:19:34.159 --> 00:19:37.590 align:start position:0% what happened there 00:19:37.590 --> 00:19:37.600 align:start position:0% 00:19:37.600 --> 00:19:40.190 align:start position:0% uh<00:19:38.600> is<00:19:38.720> there<00:19:38.880> some<00:19:39.120> reason<00:19:39.440> that<00:19:39.640> my<00:19:39.960> ah<00:19:40.120> there 00:19:40.190 --> 00:19:40.200 align:start position:0% uh is there some reason that my ah there 00:19:40.200 --> 00:19:42.070 align:start position:0% uh is there some reason that my ah there we<00:19:40.360> go 00:19:42.070 --> 00:19:42.080 align:start position:0% we go 00:19:42.080 --> 00:19:47.669 align:start position:0% we go okay<00:19:43.200> uh<00:19:44.200> very<00:19:45.000> good<00:19:46.000> okay<00:19:46.200> so<00:19:46.480> this<00:19:46.600> is<00:19:46.840> alzero 00:19:47.669 --> 00:19:47.679 align:start position:0% okay uh very good okay so this is alzero 00:19:47.679 --> 00:19:49.909 align:start position:0% okay uh very good okay so this is alzero it's<00:19:47.799> running<00:19:48.799> um<00:19:49.159> it's<00:19:49.320> actually<00:19:49.520> running<00:19:49.799> a 00:19:49.909 --> 00:19:49.919 align:start position:0% it's running um it's actually running a 00:19:49.919 --> 00:19:56.070 align:start position:0% it's running um it's actually running a whisper<00:19:50.280> node<00:19:50.960> here<00:19:51.159> is<00:19:51.480> a<00:19:52.240> console<00:19:53.240> um<00:19:54.480> so<00:19:55.480> I'm 00:19:56.070 --> 00:19:56.080 align:start position:0% whisper node here is a console um so I'm 00:19:56.080 --> 00:20:00.510 align:start position:0% whisper node here is a console um so I'm first<00:19:56.640> going<00:19:57.280> to<00:19:58.280> um<00:19:58.760> set<00:19:58.960> up<00:19:59.360> a 00:20:00.510 --> 00:20:00.520 align:start position:0% first going to um set up a 00:20:00.520 --> 00:20:02.430 align:start position:0% first going to um set up a filter<00:20:01.520> so<00:20:01.679> this<00:20:01.799> is<00:20:01.880> going<00:20:02.000> to<00:20:02.120> filter 00:20:02.430 --> 00:20:02.440 align:start position:0% filter so this is going to filter 00:20:02.440 --> 00:20:03.990 align:start position:0% filter so this is going to filter messages<00:20:02.840> that<00:20:02.919> are 00:20:03.990 --> 00:20:04.000 align:start position:0% messages that are 00:20:04.000 --> 00:20:06.149 align:start position:0% messages that are incoming 00:20:06.149 --> 00:20:06.159 align:start position:0% incoming 00:20:06.159 --> 00:20:09.270 align:start position:0% incoming uh<00:20:07.159> you<00:20:07.320> probably<00:20:07.600> can't<00:20:07.840> see<00:20:08.120> that<00:20:08.919> oh<00:20:09.080> maybe 00:20:09.270 --> 00:20:09.280 align:start position:0% uh you probably can't see that oh maybe 00:20:09.280 --> 00:20:12.270 align:start position:0% uh you probably can't see that oh maybe you<00:20:09.400> can<00:20:09.640> it's<00:20:09.799> pretty<00:20:10.000> sharp<00:20:10.919> um<00:20:11.760> basically 00:20:12.270 --> 00:20:12.280 align:start position:0% you can it's pretty sharp um basically 00:20:12.280 --> 00:20:15.510 align:start position:0% you can it's pretty sharp um basically I've<00:20:12.440> got<00:20:12.799> a<00:20:13.000> a<00:20:13.159> topic<00:20:13.400> set<00:20:13.640> the<00:20:13.720> topic<00:20:13.960> set<00:20:14.120> is 00:20:15.510 --> 00:20:15.520 align:start position:0% I've got a a topic set the topic set is 00:20:15.520 --> 00:20:17.669 align:start position:0% I've got a a topic set the topic set is Devcon<00:20:16.520> um<00:20:16.840> and<00:20:17.039> that's<00:20:17.200> the<00:20:17.320> only<00:20:17.520> thing 00:20:17.669 --> 00:20:17.679 align:start position:0% Devcon um and that's the only thing 00:20:17.679 --> 00:20:19.310 align:start position:0% Devcon um and that's the only thing that's<00:20:17.840> in<00:20:18.039> there<00:20:18.200> so<00:20:18.360> it's<00:20:18.480> just<00:20:18.640> filtering 00:20:19.310 --> 00:20:19.320 align:start position:0% that's in there so it's just filtering 00:20:19.320 --> 00:20:21.350 align:start position:0% that's in there so it's just filtering on<00:20:19.480> the<00:20:19.600> entire<00:20:19.960> whisper<00:20:20.360> system<00:20:20.880> for<00:20:21.120> all 00:20:21.350 --> 00:20:21.360 align:start position:0% on the entire whisper system for all 00:20:21.360 --> 00:20:24.430 align:start position:0% on the entire whisper system for all messages<00:20:21.960> that<00:20:22.080> have<00:20:22.159> a<00:20:22.320> topic<00:20:22.679> of<00:20:23.159> Devcon<00:20:24.159> um 00:20:24.430 --> 00:20:24.440 align:start position:0% messages that have a topic of Devcon um 00:20:24.440 --> 00:20:25.870 align:start position:0% messages that have a topic of Devcon um and<00:20:24.600> when<00:20:24.679> it<00:20:24.799> finds<00:20:25.120> it<00:20:25.200> it's<00:20:25.320> going<00:20:25.440> to<00:20:25.760> uh 00:20:25.870 --> 00:20:25.880 align:start position:0% and when it finds it it's going to uh 00:20:25.880 --> 00:20:27.470 align:start position:0% and when it finds it it's going to uh print<00:20:26.080> something<00:20:26.320> out<00:20:26.400> to<00:20:26.559> the<00:20:26.679> console<00:20:27.400> uh 00:20:27.470 --> 00:20:27.480 align:start position:0% print something out to the console uh 00:20:27.480 --> 00:20:28.350 align:start position:0% print something out to the console uh it's<00:20:27.600> going<00:20:27.679> to<00:20:27.760> print<00:20:27.960> out<00:20:28.039> the<00:20:28.159> found 00:20:28.350 --> 00:20:28.360 align:start position:0% it's going to print out the found 00:20:28.360 --> 00:20:30.710 align:start position:0% it's going to print out the found message<00:20:29.080> then<00:20:29.320> payload<00:20:30.120> and<00:20:30.240> then<00:20:30.400> whoever 00:20:30.710 --> 00:20:30.720 align:start position:0% message then payload and then whoever 00:20:30.720 --> 00:20:31.710 align:start position:0% message then payload and then whoever it's 00:20:31.710 --> 00:20:31.720 align:start position:0% it's 00:20:31.720 --> 00:20:35.350 align:start position:0% it's from<00:20:32.720> okay<00:20:33.200> so<00:20:33.360> that's<00:20:33.520> created<00:20:33.960> that<00:20:34.360> filter 00:20:35.350 --> 00:20:35.360 align:start position:0% from okay so that's created that filter 00:20:35.360 --> 00:20:36.909 align:start position:0% from okay so that's created that filter and<00:20:35.799> the<00:20:35.919> next<00:20:36.080> thing<00:20:36.240> I'm<00:20:36.320> going<00:20:36.400> to<00:20:36.559> do<00:20:36.799> and 00:20:36.909 --> 00:20:36.919 align:start position:0% and the next thing I'm going to do and 00:20:36.919 --> 00:20:38.750 align:start position:0% and the next thing I'm going to do and this<00:20:37.000> could<00:20:37.159> be<00:20:37.240> done<00:20:37.400> on<00:20:37.520> anyone's<00:20:37.919> computer 00:20:38.750 --> 00:20:38.760 align:start position:0% this could be done on anyone's computer 00:20:38.760 --> 00:20:40.470 align:start position:0% this could be done on anyone's computer um<00:20:39.159> but<00:20:39.440> it's<00:20:39.559> going<00:20:39.679> to<00:20:39.760> be<00:20:39.840> done<00:20:40.000> on<00:20:40.159> mine 00:20:40.470 --> 00:20:40.480 align:start position:0% um but it's going to be done on mine 00:20:40.480 --> 00:20:42.510 align:start position:0% um but it's going to be done on mine because<00:20:40.720> I've<00:20:40.880> only<00:20:41.039> got<00:20:41.200> one 00:20:42.510 --> 00:20:42.520 align:start position:0% because I've only got one 00:20:42.520 --> 00:20:46.669 align:start position:0% because I've only got one here<00:20:43.520> uh<00:20:43.679> and<00:20:43.840> this<00:20:43.919> is<00:20:44.080> going<00:20:44.159> to<00:20:44.400> post<00:20:45.679> um 00:20:46.669 --> 00:20:46.679 align:start position:0% here uh and this is going to post um 00:20:46.679 --> 00:20:48.789 align:start position:0% here uh and this is going to post um post<00:20:46.880> the<00:20:47.080> message<00:20:47.760> so<00:20:48.240> the<00:20:48.360> message<00:20:48.600> is 00:20:48.789 --> 00:20:48.799 align:start position:0% post the message so the message is 00:20:48.799 --> 00:20:50.789 align:start position:0% post the message so the message is posting<00:20:49.240> is<00:20:49.360> a<00:20:49.480> message<00:20:49.760> whose<00:20:49.960> topics<00:20:50.240> are 00:20:50.789 --> 00:20:50.799 align:start position:0% posting is a message whose topics are 00:20:50.799 --> 00:20:53.430 align:start position:0% posting is a message whose topics are Devcon<00:20:51.799> yeah<00:20:52.400> so<00:20:52.640> the<00:20:52.720> first<00:20:52.880> thing<00:20:53.039> can<00:20:53.240> find 00:20:53.430 --> 00:20:53.440 align:start position:0% Devcon yeah so the first thing can find 00:20:53.440 --> 00:20:57.430 align:start position:0% Devcon yeah so the first thing can find it<00:20:54.320> and<00:20:54.760> the<00:20:54.960> payload<00:20:55.640> is<00:20:55.840> going<00:20:55.919> to<00:20:56.080> be<00:20:56.440> World 00:20:57.430 --> 00:20:57.440 align:start position:0% it and the payload is going to be World 00:20:57.440 --> 00:20:59.149 align:start position:0% it and the payload is going to be World there<00:20:57.559> we<00:20:57.679> are<00:20:58.280> and<00:20:58.480> the<00:20:58.600> there's<00:20:58.720> a<00:20:58.840> time<00:20:58.960> to 00:20:59.149 --> 00:20:59.159 align:start position:0% there we are and the there's a time to 00:20:59.159 --> 00:21:01.190 align:start position:0% there we are and the there's a time to live<00:20:59.360> which<00:20:59.480> is<00:20:59.559> a<00:20:59.720> minute<00:21:00.159> uh<00:21:00.400> which<00:21:00.559> is<00:21:01.039> a 00:21:01.190 --> 00:21:01.200 align:start position:0% live which is a minute uh which is a 00:21:01.200 --> 00:21:03.070 align:start position:0% live which is a minute uh which is a minute 00:21:03.070 --> 00:21:03.080 align:start position:0% minute 00:21:03.080 --> 00:21:06.270 align:start position:0% minute yeah<00:21:04.080> and<00:21:04.240> what<00:21:04.360> we<00:21:04.480> see<00:21:04.960> is<00:21:05.520> uh<00:21:05.679> that<00:21:05.840> found 00:21:06.270 --> 00:21:06.280 align:start position:0% yeah and what we see is uh that found 00:21:06.280 --> 00:21:08.590 align:start position:0% yeah and what we see is uh that found message<00:21:06.840> found<00:21:07.200> message<00:21:07.600> world<00:21:08.240> and<00:21:08.360> it's 00:21:08.590 --> 00:21:08.600 align:start position:0% message found message world and it's 00:21:08.600 --> 00:21:10.110 align:start position:0% message found message world and it's from<00:21:09.000> is<00:21:09.159> actually<00:21:09.360> from<00:21:09.520> the<00:21:09.600> null<00:21:09.840> address 00:21:10.110 --> 00:21:10.120 align:start position:0% from is actually from the null address 00:21:10.120 --> 00:21:11.710 align:start position:0% from is actually from the null address the<00:21:10.200> null<00:21:10.400> address<00:21:10.720> just<00:21:10.799> means<00:21:11.080> that<00:21:11.200> it<00:21:11.320> was 00:21:11.710 --> 00:21:11.720 align:start position:0% the null address just means that it was 00:21:11.720 --> 00:21:13.230 align:start position:0% the null address just means that it was not<00:21:11.960> actually<00:21:12.200> signed<00:21:12.559> by<00:21:12.679> anybody<00:21:13.039> so<00:21:13.159> we 00:21:13.230 --> 00:21:13.240 align:start position:0% not actually signed by anybody so we 00:21:13.240 --> 00:21:16.149 align:start position:0% not actually signed by anybody so we don't<00:21:13.400> actually<00:21:13.559> know<00:21:13.720> who<00:21:13.880> it's<00:21:14.279> from<00:21:15.279> okay 00:21:16.149 --> 00:21:16.159 align:start position:0% don't actually know who it's from okay 00:21:16.159 --> 00:21:19.830 align:start position:0% don't actually know who it's from okay pretty<00:21:16.480> simple<00:21:17.400> next<00:21:17.679> thing<00:21:18.000> let's<00:21:18.880> um<00:21:19.360> create 00:21:19.830 --> 00:21:19.840 align:start position:0% pretty simple next thing let's um create 00:21:19.840 --> 00:21:22.590 align:start position:0% pretty simple next thing let's um create an 00:21:22.590 --> 00:21:22.600 align:start position:0% 00:21:22.600 --> 00:21:25.430 align:start position:0% identity<00:21:23.600> there's<00:21:24.240> an<00:21:24.440> identity<00:21:25.000> that's<00:21:25.159> our 00:21:25.430 --> 00:21:25.440 align:start position:0% identity there's an identity that's our 00:21:25.440 --> 00:21:28.710 align:start position:0% identity there's an identity that's our key<00:21:25.720> so<00:21:25.880> this<00:21:25.960> is<00:21:26.159> actually<00:21:26.480> just<00:21:26.919> an<00:21:27.279> ndsa<00:21:28.279> um 00:21:28.710 --> 00:21:28.720 align:start position:0% key so this is actually just an ndsa um 00:21:28.720 --> 00:21:30.510 align:start position:0% key so this is actually just an ndsa um public<00:21:29.000> key<00:21:29.200> that<00:21:29.279> it's<00:21:29.559> returned<00:21:30.120> the<00:21:30.240> actual 00:21:30.510 --> 00:21:30.520 align:start position:0% public key that it's returned the actual 00:21:30.520 --> 00:21:32.070 align:start position:0% public key that it's returned the actual private<00:21:30.799> key<00:21:30.960> is<00:21:31.080> managed<00:21:31.440> internally<00:21:31.840> in<00:21:31.919> the 00:21:32.070 --> 00:21:32.080 align:start position:0% private key is managed internally in the 00:21:32.080 --> 00:21:34.549 align:start position:0% private key is managed internally in the applic<00:21:32.520> in<00:21:32.720> in<00:21:32.840> alth 00:21:34.549 --> 00:21:34.559 align:start position:0% applic in in alth 00:21:34.559 --> 00:21:36.870 align:start position:0% applic in in alth zero<00:21:35.559> um<00:21:35.679> and<00:21:35.799> what<00:21:35.919> I'm<00:21:36.000> going<00:21:36.120> to<00:21:36.240> do<00:21:36.400> is<00:21:36.720> just 00:21:36.870 --> 00:21:36.880 align:start position:0% zero um and what I'm going to do is just 00:21:36.880 --> 00:21:39.029 align:start position:0% zero um and what I'm going to do is just send<00:21:37.159> that<00:21:37.600> exact<00:21:37.880> same<00:21:38.120> message<00:21:38.760> but<00:21:38.919> I'm 00:21:39.029 --> 00:21:39.039 align:start position:0% send that exact same message but I'm 00:21:39.039 --> 00:21:41.710 align:start position:0% send that exact same message but I'm sending<00:21:39.360> it<00:21:40.360> um<00:21:40.640> actually<00:21:41.279> you<00:21:41.400> know<00:21:41.520> what<00:21:41.640> I'm 00:21:41.710 --> 00:21:41.720 align:start position:0% sending it um actually you know what I'm 00:21:41.720 --> 00:21:43.070 align:start position:0% sending it um actually you know what I'm going<00:21:41.799> to<00:21:41.880> change<00:21:42.120> the<00:21:42.279> payload<00:21:42.640> so<00:21:42.799> we<00:21:42.919> can 00:21:43.070 --> 00:21:43.080 align:start position:0% going to change the payload so we can 00:21:43.080 --> 00:21:45.149 align:start position:0% going to change the payload so we can tell<00:21:43.240> the<00:21:43.360> difference<00:21:43.720> this<00:21:43.799> is<00:21:43.919> going<00:21:44.039> to<00:21:44.159> be 00:21:45.149 --> 00:21:45.159 align:start position:0% tell the difference this is going to be 00:21:45.159 --> 00:21:46.510 align:start position:0% tell the difference this is going to be uh 00:21:46.510 --> 00:21:46.520 align:start position:0% uh 00:21:46.520 --> 00:21:50.110 align:start position:0% uh hello<00:21:47.520> um<00:21:48.120> uh<00:21:48.240> the<00:21:48.400> important<00:21:48.840> thing<00:21:49.120> is<00:21:49.600> that 00:21:50.110 --> 00:21:50.120 align:start position:0% hello um uh the important thing is that 00:21:50.120 --> 00:21:52.430 align:start position:0% hello um uh the important thing is that I'm<00:21:50.760> sending<00:21:51.120> it<00:21:51.320> from<00:21:51.600> that<00:21:51.760> identity<00:21:52.320> there 00:21:52.430 --> 00:21:52.440 align:start position:0% I'm sending it from that identity there 00:21:52.440 --> 00:21:54.350 align:start position:0% I'm sending it from that identity there it<00:21:52.640> is<00:21:52.880> from 00:21:54.350 --> 00:21:54.360 align:start position:0% it is from 00:21:54.360 --> 00:21:57.149 align:start position:0% it is from ID<00:21:55.360> found<00:21:55.720> message<00:21:56.080> there's<00:21:56.240> our<00:21:56.400> new<00:21:56.600> payload 00:21:57.149 --> 00:21:57.159 align:start position:0% ID found message there's our new payload 00:21:57.159 --> 00:21:59.350 align:start position:0% ID found message there's our new payload and<00:21:57.600> yes<00:21:58.000> we<00:21:58.159> know<00:21:58.320> now<00:21:58.760> that<00:21:58.880> it's<00:21:59.039> coming 00:21:59.350 --> 00:21:59.360 align:start position:0% and yes we know now that it's coming 00:21:59.360 --> 00:22:03.230 align:start position:0% and yes we know now that it's coming from<00:21:59.679> that<00:21:59.840> particular<00:22:00.240> identity<00:22:01.200> right<00:22:02.200> okay 00:22:03.230 --> 00:22:03.240 align:start position:0% from that particular identity right okay 00:22:03.240 --> 00:22:05.430 align:start position:0% from that particular identity right okay um<00:22:04.240> we<00:22:04.400> know<00:22:04.640> that<00:22:04.799> because<00:22:05.000> it's<00:22:05.200> actually 00:22:05.430 --> 00:22:05.440 align:start position:0% um we know that because it's actually 00:22:05.440 --> 00:22:06.950 align:start position:0% um we know that because it's actually been<00:22:05.600> signed<00:22:06.120> so<00:22:06.240> it's<00:22:06.400> not<00:22:06.640> just<00:22:06.760> some 00:22:06.950 --> 00:22:06.960 align:start position:0% been signed so it's not just some 00:22:06.960 --> 00:22:09.149 align:start position:0% been signed so it's not just some insecure<00:22:07.559> sort<00:22:07.720> of<00:22:08.320> thing<00:22:08.559> attached<00:22:08.880> to<00:22:09.000> it 00:22:09.149 --> 00:22:09.159 align:start position:0% insecure sort of thing attached to it 00:22:09.159 --> 00:22:11.830 align:start position:0% insecure sort of thing attached to it it's<00:22:09.279> a<00:22:09.520> proper<00:22:10.320> um<00:22:10.799> uh 00:22:11.830 --> 00:22:11.840 align:start position:0% it's a proper um uh 00:22:11.840 --> 00:22:13.870 align:start position:0% it's a proper um uh signature<00:22:12.840> now<00:22:13.120> then<00:22:13.360> we're<00:22:13.520> going<00:22:13.600> to<00:22:13.720> have 00:22:13.870 --> 00:22:13.880 align:start position:0% signature now then we're going to have 00:22:13.880 --> 00:22:15.830 align:start position:0% signature now then we're going to have another<00:22:14.159> identity<00:22:14.679> this<00:22:14.799> is<00:22:15.279> this<00:22:15.400> is<00:22:15.640> my 00:22:15.830 --> 00:22:15.840 align:start position:0% another identity this is this is my 00:22:15.840 --> 00:22:18.029 align:start position:0% another identity this is this is my identity<00:22:16.279> so<00:22:16.440> it's<00:22:16.640> gav<00:22:17.080> gav<00:22:17.320> is<00:22:17.440> equaling<00:22:17.840> a 00:22:18.029 --> 00:22:18.039 align:start position:0% identity so it's gav gav is equaling a 00:22:18.039 --> 00:22:20.149 align:start position:0% identity so it's gav gav is equaling a new<00:22:18.279> identity<00:22:18.840> there's<00:22:19.039> my<00:22:19.159> identity<00:22:19.559> ox1 00:22:20.149 --> 00:22:20.159 align:start position:0% new identity there's my identity ox1 00:22:20.159 --> 00:22:24.110 align:start position:0% new identity there's my identity ox1 1282<00:22:21.360> FF<00:22:22.360> um<00:22:23.000> and<00:22:23.360> I'm<00:22:23.440> going<00:22:23.559> to<00:22:23.640> set<00:22:23.760> up<00:22:23.880> a<00:22:24.000> new 00:22:24.110 --> 00:22:24.120 align:start position:0% 1282 FF um and I'm going to set up a new 00:22:24.120 --> 00:22:26.909 align:start position:0% 1282 FF um and I'm going to set up a new filter<00:22:24.600> this<00:22:24.720> one's<00:22:25.440> just<00:22:25.640> going<00:22:25.720> to<00:22:25.919> filter 00:22:26.909 --> 00:22:26.919 align:start position:0% filter this one's just going to filter 00:22:26.919 --> 00:22:31.269 align:start position:0% filter this one's just going to filter um<00:22:27.320> for<00:22:27.640> messages<00:22:28.679> from<00:22:29.600> um<00:22:30.279> uh<00:22:30.559> to<00:22:31.000> uh<00:22:31.159> with 00:22:31.269 --> 00:22:31.279 align:start position:0% um for messages from um uh to uh with 00:22:31.279 --> 00:22:35.350 align:start position:0% um for messages from um uh to uh with the<00:22:31.400> topic<00:22:31.679> Devcon<00:22:32.279> gav<00:22:33.440> right<00:22:34.440> um<00:22:34.960> now<00:22:35.200> we 00:22:35.350 --> 00:22:35.360 align:start position:0% the topic Devcon gav right um now we 00:22:35.360 --> 00:22:38.549 align:start position:0% the topic Devcon gav right um now we have<00:22:35.520> to<00:22:35.679> tell<00:22:36.200> it<00:22:37.200> actually<00:22:37.559> up<00:22:37.840> front<00:22:38.440> that 00:22:38.549 --> 00:22:38.559 align:start position:0% have to tell it actually up front that 00:22:38.559 --> 00:22:40.590 align:start position:0% have to tell it actually up front that it<00:22:38.679> needs<00:22:38.840> to<00:22:39.039> decrypt<00:22:39.600> with<00:22:39.799> my<00:22:40.159> key<00:22:40.400> this<00:22:40.480> is 00:22:40.590 --> 00:22:40.600 align:start position:0% it needs to decrypt with my key this is 00:22:40.600 --> 00:22:42.590 align:start position:0% it needs to decrypt with my key this is to<00:22:40.799> avoid<00:22:41.120> having<00:22:41.360> any<00:22:41.600> additional<00:22:42.000> metadata 00:22:42.590 --> 00:22:42.600 align:start position:0% to avoid having any additional metadata 00:22:42.600 --> 00:22:45.269 align:start position:0% to avoid having any additional metadata in<00:22:42.720> the<00:22:42.880> message<00:22:43.159> body<00:22:43.760> itself<00:22:44.760> um<00:22:44.960> so<00:22:45.120> we're 00:22:45.269 --> 00:22:45.279 align:start position:0% in the message body itself um so we're 00:22:45.279 --> 00:22:47.549 align:start position:0% in the message body itself um so we're saying<00:22:45.919> all<00:22:46.200> messages<00:22:46.559> of<00:22:46.720> topic<00:22:47.039> Dev<00:22:47.320> Kong 00:22:47.549 --> 00:22:47.559 align:start position:0% saying all messages of topic Dev Kong 00:22:47.559 --> 00:22:50.909 align:start position:0% saying all messages of topic Dev Kong gav<00:22:48.000> are<00:22:48.200> actually<00:22:48.480> going<00:22:48.640> to<00:22:48.799> be<00:22:48.960> sent<00:22:49.440> to 00:22:50.909 --> 00:22:50.919 align:start position:0% gav are actually going to be sent to 00:22:50.919 --> 00:22:53.750 align:start position:0% gav are actually going to be sent to me<00:22:51.919> um<00:22:52.720> now<00:22:52.840> we're<00:22:52.960> going<00:22:53.080> to<00:22:53.159> set<00:22:53.279> up<00:22:53.400> a<00:22:53.559> watch 00:22:53.750 --> 00:22:53.760 align:start position:0% me um now we're going to set up a watch 00:22:53.760 --> 00:22:55.870 align:start position:0% me um now we're going to set up a watch for<00:22:54.000> that<00:22:54.520> and<00:22:54.720> say<00:22:54.919> that<00:22:55.080> it's<00:22:55.200> going<00:22:55.320> to<00:22:55.520> say 00:22:55.870 --> 00:22:55.880 align:start position:0% for that and say that it's going to say 00:22:55.880 --> 00:22:57.590 align:start position:0% for that and say that it's going to say it's<00:22:56.159> actually<00:22:56.799> going<00:22:56.880> to<00:22:57.000> print<00:22:57.200> a<00:22:57.279> message 00:22:57.590 --> 00:22:57.600 align:start position:0% it's actually going to print a message 00:22:57.600 --> 00:23:00.630 align:start position:0% it's actually going to print a message found<00:22:57.919> message<00:22:58.200> to<00:22:58.600> gav<00:22:59.440> um<00:22:59.559> with<00:22:59.679> a<00:22:59.840> payload 00:23:00.630 --> 00:23:00.640 align:start position:0% found message to gav um with a payload 00:23:00.640 --> 00:23:01.789 align:start position:0% found message to gav um with a payload and<00:23:00.720> then<00:23:00.840> it's<00:23:01.000> also<00:23:01.159> going<00:23:01.279> to<00:23:01.360> tell<00:23:01.520> us<00:23:01.640> who 00:23:01.789 --> 00:23:01.799 align:start position:0% and then it's also going to tell us who 00:23:01.799 --> 00:23:03.549 align:start position:0% and then it's also going to tell us who it's<00:23:01.960> from<00:23:02.480> so<00:23:02.640> I<00:23:02.760> do<00:23:02.960> that<00:23:03.120> and<00:23:03.240> of<00:23:03.360> course 00:23:03.549 --> 00:23:03.559 align:start position:0% it's from so I do that and of course 00:23:03.559 --> 00:23:04.950 align:start position:0% it's from so I do that and of course nothing<00:23:03.760> comes<00:23:04.039> back<00:23:04.240> because<00:23:04.480> no<00:23:04.640> messages 00:23:04.950 --> 00:23:04.960 align:start position:0% nothing comes back because no messages 00:23:04.960 --> 00:23:09.430 align:start position:0% nothing comes back because no messages have<00:23:05.120> been<00:23:05.279> sent<00:23:05.600> yet<00:23:06.279> but<00:23:07.279> there<00:23:07.400> you<00:23:07.799> go 00:23:09.430 --> 00:23:09.440 align:start position:0% have been sent yet but there you go 00:23:09.440 --> 00:23:12.789 align:start position:0% have been sent yet but there you go um<00:23:10.440> here<00:23:10.640> is<00:23:11.039> a<00:23:11.559> uh<00:23:11.720> a<00:23:11.919> post<00:23:12.240> so<00:23:12.360> we're<00:23:12.480> going<00:23:12.600> to 00:23:12.789 --> 00:23:12.799 align:start position:0% um here is a uh a post so we're going to 00:23:12.799 --> 00:23:17.830 align:start position:0% um here is a uh a post so we're going to post<00:23:13.840> um<00:23:14.840> using<00:23:15.240> the<00:23:15.600> Devcon<00:23:16.080> gav<00:23:16.400> topic<00:23:17.400> um 00:23:17.830 --> 00:23:17.840 align:start position:0% post um using the Devcon gav topic um 00:23:17.840 --> 00:23:20.070 align:start position:0% post um using the Devcon gav topic um and<00:23:17.960> the<00:23:18.120> payload<00:23:18.679> there<00:23:18.960> is<00:23:19.360> is<00:23:19.720> well<00:23:19.919> let's 00:23:20.070 --> 00:23:20.080 align:start position:0% and the payload there is is well let's 00:23:20.080 --> 00:23:21.430 align:start position:0% and the payload there is is well let's change<00:23:20.320> the<00:23:20.440> payload<00:23:20.840> make<00:23:20.960> it<00:23:21.039> something 00:23:21.430 --> 00:23:21.440 align:start position:0% change the payload make it something 00:23:21.440 --> 00:23:22.990 align:start position:0% change the payload make it something interesting 00:23:22.990 --> 00:23:23.000 align:start position:0% interesting 00:23:23.000 --> 00:23:24.950 align:start position:0% interesting um<00:23:24.000> uh 00:23:24.950 --> 00:23:24.960 align:start position:0% um uh 00:23:24.960 --> 00:23:31.710 align:start position:0% um uh hello<00:23:26.360> uh<00:23:27.360> gav<00:23:28.240> where 00:23:31.710 --> 00:23:31.720 align:start position:0% 00:23:31.720 --> 00:23:36.470 align:start position:0% um<00:23:32.720> from<00:23:33.559> our<00:23:33.799> original<00:23:34.240> identity<00:23:34.679> Ox<00:23:35.080> CB<00:23:35.799> 4D 00:23:36.470 --> 00:23:36.480 align:start position:0% um from our original identity Ox CB 4D 00:23:36.480 --> 00:23:38.430 align:start position:0% um from our original identity Ox CB 4D blah<00:23:36.640> blah<00:23:36.840> blah<00:23:37.360> uh<00:23:37.520> but<00:23:37.679> this<00:23:37.760> one<00:23:37.919> it's<00:23:38.120> two 00:23:38.430 --> 00:23:38.440 align:start position:0% blah blah blah uh but this one it's two 00:23:38.440 --> 00:23:39.710 align:start position:0% blah blah blah uh but this one it's two gav 00:23:39.710 --> 00:23:39.720 align:start position:0% gav 00:23:39.720 --> 00:23:41.470 align:start position:0% gav right 00:23:41.470 --> 00:23:41.480 align:start position:0% right 00:23:41.480 --> 00:23:43.269 align:start position:0% right and 00:23:43.269 --> 00:23:43.279 align:start position:0% and 00:23:43.279 --> 00:23:48.029 align:start position:0% and okay<00:23:44.279> did<00:23:44.559> I<00:23:45.279> ah<00:23:45.480> yeah<00:23:45.679> there<00:23:45.760> we 00:23:48.029 --> 00:23:48.039 align:start position:0% 00:23:48.039 --> 00:23:50.909 align:start position:0% are<00:23:49.039> let's<00:23:49.240> use<00:23:49.440> double<00:23:49.760> quotes 00:23:50.909 --> 00:23:50.919 align:start position:0% are let's use double quotes 00:23:50.919 --> 00:23:53.789 align:start position:0% are let's use double quotes instead<00:23:51.919> and<00:23:52.080> there<00:23:52.159> we<00:23:52.279> go<00:23:53.039> um<00:23:53.200> found<00:23:53.520> message 00:23:53.789 --> 00:23:53.799 align:start position:0% instead and there we go um found message 00:23:53.799 --> 00:23:56.269 align:start position:0% instead and there we go um found message to<00:23:54.080> gav<00:23:55.080> hello<00:23:55.360> gav<00:23:55.600> where's<00:23:55.760> the<00:23:55.919> beer<00:23:56.200> and 00:23:56.269 --> 00:23:56.279 align:start position:0% to gav hello gav where's the beer and 00:23:56.279 --> 00:23:57.990 align:start position:0% to gav hello gav where's the beer and it's<00:23:56.440> sent<00:23:56.679> from<00:23:56.880> that<00:23:57.039> particular<00:23:57.360> identity 00:23:57.990 --> 00:23:58.000 align:start position:0% it's sent from that particular identity 00:23:58.000 --> 00:23:59.310 align:start position:0% it's sent from that particular identity cool 00:23:59.310 --> 00:23:59.320 align:start position:0% cool 00:23:59.320 --> 00:24:02.590 align:start position:0% cool um<00:23:59.919> yeah<00:24:00.159> so<00:24:00.400> that's<00:24:00.799> a<00:24:01.480> uh<00:24:01.679> it's<00:24:01.880> super<00:24:02.159> simple 00:24:02.590 --> 00:24:02.600 align:start position:0% um yeah so that's a uh it's super simple 00:24:02.600 --> 00:24:04.350 align:start position:0% um yeah so that's a uh it's super simple as<00:24:02.720> you<00:24:02.799> can<00:24:02.960> see<00:24:03.360> payload<00:24:03.799> can<00:24:03.919> be<00:24:04.080> whatever 00:24:04.350 --> 00:24:04.360 align:start position:0% as you can see payload can be whatever 00:24:04.360 --> 00:24:05.750 align:start position:0% as you can see payload can be whatever you<00:24:04.440> want<00:24:04.600> it<00:24:04.720> to<00:24:04.840> be<00:24:05.039> so<00:24:05.400> you<00:24:05.480> know<00:24:05.640> in 00:24:05.750 --> 00:24:05.760 align:start position:0% you want it to be so you know in 00:24:05.760 --> 00:24:09.190 align:start position:0% you want it to be so you know in principle<00:24:06.679> um<00:24:07.039> bite<00:24:07.400> data<00:24:08.360> um<00:24:08.520> send<00:24:08.799> images 00:24:09.190 --> 00:24:09.200 align:start position:0% principle um bite data um send images 00:24:09.200 --> 00:24:12.510 align:start position:0% principle um bite data um send images around<00:24:09.760> whatever<00:24:10.039> it<00:24:10.120> will<00:24:10.279> be<00:24:11.039> um<00:24:12.000> probably 00:24:12.510 --> 00:24:12.520 align:start position:0% around whatever it will be um probably 00:24:12.520 --> 00:24:15.230 align:start position:0% around whatever it will be um probably it's<00:24:12.880> going<00:24:13.000> to<00:24:13.159> be<00:24:13.320> mostly<00:24:13.799> asky<00:24:14.159> with<00:24:14.240> a<00:24:14.400> few 00:24:15.230 --> 00:24:15.240 align:start position:0% it's going to be mostly asky with a few 00:24:15.240 --> 00:24:17.549 align:start position:0% it's going to be mostly asky with a few hashes<00:24:16.240> uh<00:24:16.440> and<00:24:16.559> the<00:24:16.679> hashes<00:24:17.000> would<00:24:17.200> then<00:24:17.320> lead 00:24:17.549 --> 00:24:17.559 align:start position:0% hashes uh and the hashes would then lead 00:24:17.559 --> 00:24:19.390 align:start position:0% hashes uh and the hashes would then lead on<00:24:17.720> to<00:24:18.039> some<00:24:18.240> other<00:24:18.440> systems<00:24:18.840> publication 00:24:19.390 --> 00:24:19.400 align:start position:0% on to some other systems publication 00:24:19.400 --> 00:24:21.870 align:start position:0% on to some other systems publication ipfs<00:24:20.320> whatever 00:24:21.870 --> 00:24:21.880 align:start position:0% ipfs whatever 00:24:21.880 --> 00:24:24.630 align:start position:0% ipfs whatever um<00:24:22.880> the<00:24:23.520> uh<00:24:23.679> topics<00:24:24.159> there<00:24:24.279> can<00:24:24.400> be<00:24:24.520> an 00:24:24.630 --> 00:24:24.640 align:start position:0% um the uh topics there can be an 00:24:24.640 --> 00:24:26.669 align:start position:0% um the uh topics there can be an arbitrary<00:24:25.039> number<00:24:25.240> of<00:24:25.399> topics<00:24:25.760> the<00:24:25.919> topics<00:24:26.480> uh 00:24:26.669 --> 00:24:26.679 align:start position:0% arbitrary number of topics the topics uh 00:24:26.679 --> 00:24:28.669 align:start position:0% arbitrary number of topics the topics uh can<00:24:26.840> be<00:24:27.120> anded<00:24:27.480> or<00:24:27.600> Ed<00:24:28.039> together<00:24:28.399> so<00:24:28.520> that<00:24:28.600> we 00:24:28.669 --> 00:24:28.679 align:start position:0% can be anded or Ed together so that we 00:24:28.679 --> 00:24:30.750 align:start position:0% can be anded or Ed together so that we can<00:24:28.799> say<00:24:29.080> right<00:24:29.240> it's<00:24:29.399> got<00:24:29.480> to<00:24:29.640> contain<00:24:30.440> um<00:24:30.600> one 00:24:30.750 --> 00:24:30.760 align:start position:0% can say right it's got to contain um one 00:24:30.760 --> 00:24:32.750 align:start position:0% can say right it's got to contain um one of<00:24:30.880> these<00:24:31.039> two<00:24:31.240> topics<00:24:31.520> in<00:24:31.640> the<00:24:31.799> first<00:24:32.120> place 00:24:32.750 --> 00:24:32.760 align:start position:0% of these two topics in the first place 00:24:32.760 --> 00:24:34.070 align:start position:0% of these two topics in the first place uh<00:24:32.880> one<00:24:33.000> of<00:24:33.159> these<00:24:33.360> five<00:24:33.600> topics<00:24:33.880> in<00:24:33.960> the 00:24:34.070 --> 00:24:34.080 align:start position:0% uh one of these five topics in the 00:24:34.080 --> 00:24:35.389 align:start position:0% uh one of these five topics in the second<00:24:34.320> place<00:24:34.480> and<00:24:34.559> the<00:24:34.679> third<00:24:34.880> place<00:24:35.080> must<00:24:35.200> be 00:24:35.389 --> 00:24:35.399 align:start position:0% second place and the third place must be 00:24:35.399 --> 00:24:39.630 align:start position:0% second place and the third place must be this<00:24:35.600> topic<00:24:36.360> that<00:24:36.480> all<00:24:36.640> works<00:24:37.279> fine<00:24:38.279> um<00:24:39.159> and 00:24:39.630 --> 00:24:39.640 align:start position:0% this topic that all works fine um and 00:24:39.640 --> 00:24:40.870 align:start position:0% this topic that all works fine um and yeah<00:24:39.799> obviously<00:24:40.120> the<00:24:40.279> time<00:24:40.399> to<00:24:40.559> live<00:24:40.799> I 00:24:40.870 --> 00:24:40.880 align:start position:0% yeah obviously the time to live I 00:24:40.880 --> 00:24:42.190 align:start position:0% yeah obviously the time to live I haven't<00:24:41.120> bothered<00:24:41.480> doing<00:24:41.720> anything<00:24:41.960> with<00:24:42.080> the 00:24:42.190 --> 00:24:42.200 align:start position:0% haven't bothered doing anything with the 00:24:42.200 --> 00:24:44.990 align:start position:0% haven't bothered doing anything with the proof<00:24:42.399> of<00:24:42.559> work<00:24:42.799> priority<00:24:43.240> stuff<00:24:43.600> but<00:24:44.200> um<00:24:44.799> the 00:24:44.990 --> 00:24:45.000 align:start position:0% proof of work priority stuff but um the 00:24:45.000 --> 00:24:47.110 align:start position:0% proof of work priority stuff but um the principle<00:24:45.480> is<00:24:45.720> is<00:24:45.919> there<00:24:46.080> and<00:24:46.320> the<00:24:46.640> uh<00:24:46.880> and<00:24:47.000> it 00:24:47.110 --> 00:24:47.120 align:start position:0% principle is is there and the uh and it 00:24:47.120 --> 00:24:50.350 align:start position:0% principle is is there and the uh and it works<00:24:47.559> in<00:24:47.840> practice<00:24:48.840> um<00:24:49.080> this<00:24:49.159> is<00:24:49.360> proof 00:24:50.350 --> 00:24:50.360 align:start position:0% works in practice um this is proof 00:24:50.360 --> 00:24:54.870 align:start position:0% works in practice um this is proof PC3<00:24:51.360> um<00:24:51.760> this<00:24:51.840> is<00:24:51.960> in<00:24:52.080> the<00:24:52.320> CPP<00:24:53.320> um<00:24:53.520> code<00:24:53.880> base 00:24:54.870 --> 00:24:54.880 align:start position:0% PC3 um this is in the CPP um code base 00:24:54.880 --> 00:24:57.149 align:start position:0% PC3 um this is in the CPP um code base um<00:24:55.440> that<00:24:55.760> I<00:24:56.200> understand<00:24:56.360> it<00:24:56.520> is<00:24:56.720> being 00:24:57.149 --> 00:24:57.159 align:start position:0% um that I understand it is being 00:24:57.159 --> 00:24:58.950 align:start position:0% um that I understand it is being currently<00:24:57.600> implemented<00:24:58.120> in<00:24:58.440> the<00:24:58.559> go<00:24:58.760> code 00:24:58.950 --> 00:24:58.960 align:start position:0% currently implemented in the go code 00:24:58.960 --> 00:25:00.789 align:start position:0% currently implemented in the go code base<00:24:59.159> I<00:24:59.200> think<00:24:59.360> goes<00:24:59.480> up<00:24:59.600> to<00:24:59.760> PC2<00:25:00.440> at<00:25:00.520> the 00:25:00.789 --> 00:25:00.799 align:start position:0% base I think goes up to PC2 at the 00:25:00.799 --> 00:25:04.029 align:start position:0% base I think goes up to PC2 at the moment<00:25:01.799> um<00:25:02.440> and<00:25:02.799> there's<00:25:03.360> uh<00:25:03.520> substantial 00:25:04.029 --> 00:25:04.039 align:start position:0% moment um and there's uh substantial 00:25:04.039 --> 00:25:05.870 align:start position:0% moment um and there's uh substantial interest<00:25:04.480> in<00:25:04.679> the<00:25:04.960> other<00:25:05.200> code<00:25:05.399> bases<00:25:05.720> for 00:25:05.870 --> 00:25:05.880 align:start position:0% interest in the other code bases for 00:25:05.880 --> 00:25:09.669 align:start position:0% interest in the other code bases for putting<00:25:06.080> all<00:25:06.240> this<00:25:06.440> stuff<00:25:06.919> in<00:25:07.919> um<00:25:08.799> yeah<00:25:09.440> uh<00:25:09.559> if 00:25:09.669 --> 00:25:09.679 align:start position:0% putting all this stuff in um yeah uh if 00:25:09.679 --> 00:25:12.870 align:start position:0% putting all this stuff in um yeah uh if you<00:25:09.919> want<00:25:10.159> to<00:25:10.960> uh<00:25:11.159> contribute<00:25:11.640> and<00:25:11.799> help<00:25:12.559> uh 00:25:12.870 --> 00:25:12.880 align:start position:0% you want to uh contribute and help uh 00:25:12.880 --> 00:25:15.830 align:start position:0% you want to uh contribute and help uh help<00:25:13.440> uh<00:25:13.640> develop<00:25:14.039> this<00:25:14.240> then<00:25:14.520> get<00:25:14.640> in<00:25:14.840> touch 00:25:15.830 --> 00:25:15.840 align:start position:0% help uh develop this then get in touch 00:25:15.840 --> 00:25:26.269 align:start position:0% help uh develop this then get in touch uh<00:25:15.960> and<00:25:16.120> otherwise<00:25:16.840> uh<00:25:17.000> thank<00:25:17.159> you<00:25:17.320> any 00:25:26.269 --> 00:25:26.279 align:start position:0% 00:25:26.279 --> 00:25:29.149 align:start position:0% questions<00:25:27.279> two<00:25:27.559> question 00:25:29.149 --> 00:25:29.159 align:start position:0% questions two question 00:25:29.159 --> 00:25:32.830 align:start position:0% questions two question one 00:25:32.830 --> 00:25:32.840 align:start position:0% 00:25:32.840 --> 00:25:36.430 align:start position:0% question<00:25:33.840> so<00:25:34.600> uh<00:25:34.960> two<00:25:35.240> days<00:25:35.440> ago<00:25:35.679> we<00:25:35.840> discussed 00:25:36.430 --> 00:25:36.440 align:start position:0% question so uh two days ago we discussed 00:25:36.440 --> 00:25:39.310 align:start position:0% question so uh two days ago we discussed that<00:25:36.799> one<00:25:37.640> Paradigm<00:25:38.159> of<00:25:38.320> building<00:25:38.720> scalable 00:25:39.310 --> 00:25:39.320 align:start position:0% that one Paradigm of building scalable 00:25:39.320 --> 00:25:42.590 align:start position:0% that one Paradigm of building scalable daps<00:25:40.159> is<00:25:40.760> creating 00:25:42.590 --> 00:25:42.600 align:start position:0% daps is creating 00:25:42.600 --> 00:25:46.110 align:start position:0% daps is creating uh<00:25:43.600> sophisticated<00:25:44.480> State<00:25:44.799> channels<00:25:45.559> and<00:25:45.960> I'm 00:25:46.110 --> 00:25:46.120 align:start position:0% uh sophisticated State channels and I'm 00:25:46.120 --> 00:25:49.269 align:start position:0% uh sophisticated State channels and I'm wondering<00:25:46.880> whether<00:25:47.880> a<00:25:48.080> whisper<00:25:48.600> is<00:25:48.760> the<00:25:49.000> right 00:25:49.269 --> 00:25:49.279 align:start position:0% wondering whether a whisper is the right 00:25:49.279 --> 00:25:52.510 align:start position:0% wondering whether a whisper is the right protocol<00:25:49.799> to<00:25:50.039> distribute<00:25:51.000> uh<00:25:51.640> transactions 00:25:52.510 --> 00:25:52.520 align:start position:0% protocol to distribute uh transactions 00:25:52.520 --> 00:25:56.430 align:start position:0% protocol to distribute uh transactions that<00:25:52.760> happen<00:25:53.120> on<00:25:53.360> those<00:25:53.919> uh<00:25:55.039> uh<00:25:56.039> on<00:25:56.240> those 00:25:56.430 --> 00:25:56.440 align:start position:0% that happen on those uh uh on those 00:25:56.440 --> 00:25:59.230 align:start position:0% that happen on those uh uh on those State<00:25:56.720> channels<00:25:57.360> is<00:25:57.559> Whisperers<00:25:58.480> for<00:25:58.720> that 00:25:59.230 --> 00:25:59.240 align:start position:0% State channels is Whisperers for that 00:25:59.240 --> 00:26:02.669 align:start position:0% State channels is Whisperers for that yeah<00:25:59.440> so<00:25:59.679> this<00:25:59.799> is<00:26:00.360> oh<00:26:00.559> cool<00:26:01.000> this<00:26:01.120> is<00:26:01.440> a<00:26:02.159> um 00:26:02.669 --> 00:26:02.679 align:start position:0% yeah so this is oh cool this is a um 00:26:02.679 --> 00:26:04.149 align:start position:0% yeah so this is oh cool this is a um actually<00:26:02.960> something<00:26:03.240> that<00:26:03.399> I<00:26:03.480> would<00:26:03.679> like<00:26:03.840> to 00:26:04.149 --> 00:26:04.159 align:start position:0% actually something that I would like to 00:26:04.159 --> 00:26:07.430 align:start position:0% actually something that I would like to take<00:26:04.360> forward<00:26:05.159> uh<00:26:05.360> I<00:26:05.520> think<00:26:06.159> um<00:26:06.880> with<00:26:07.320> uh 00:26:07.430 --> 00:26:07.440 align:start position:0% take forward uh I think um with uh 00:26:07.440 --> 00:26:09.710 align:start position:0% take forward uh I think um with uh blocks<00:26:07.919> and<00:26:08.080> obviously<00:26:08.399> the<00:26:08.559> stuff<00:26:08.840> that<00:26:09.279> uh<00:26:09.399> Z 00:26:09.710 --> 00:26:09.720 align:start position:0% blocks and obviously the stuff that uh Z 00:26:09.720 --> 00:26:12.149 align:start position:0% blocks and obviously the stuff that uh Z was<00:26:09.840> talking<00:26:10.039> about<00:26:10.320> before<00:26:11.159> um<00:26:11.760> the<00:26:11.880> various 00:26:12.149 --> 00:26:12.159 align:start position:0% was talking about before um the various 00:26:12.159 --> 00:26:13.909 align:start position:0% was talking about before um the various bits<00:26:12.360> of<00:26:12.480> data<00:26:12.760> regarding<00:26:13.080> the<00:26:13.200> blockchain 00:26:13.909 --> 00:26:13.919 align:start position:0% bits of data regarding the blockchain 00:26:13.919 --> 00:26:16.950 align:start position:0% bits of data regarding the blockchain this<00:26:14.039> is<00:26:14.159> all<00:26:14.880> um<00:26:15.279> static<00:26:15.640> data<00:26:16.159> and<00:26:16.480> fits<00:26:16.799> well 00:26:16.950 --> 00:26:16.960 align:start position:0% this is all um static data and fits well 00:26:16.960 --> 00:26:19.870 align:start position:0% this is all um static data and fits well into<00:26:17.159> the<00:26:17.279> ipfs<00:26:17.720> Swarm<00:26:18.080> sort<00:26:18.279> of<00:26:18.720> Paradigm<00:26:19.600> uh 00:26:19.870 --> 00:26:19.880 align:start position:0% into the ipfs Swarm sort of Paradigm uh 00:26:19.880 --> 00:26:23.230 align:start position:0% into the ipfs Swarm sort of Paradigm uh transactions<00:26:20.880> uh<00:26:21.039> definitely<00:26:21.799> are<00:26:22.279> much<00:26:22.559> more 00:26:23.230 --> 00:26:23.240 align:start position:0% transactions uh definitely are much more 00:26:23.240 --> 00:26:26.149 align:start position:0% transactions uh definitely are much more um<00:26:24.240> uh<00:26:24.480> ephemeral<00:26:25.080> data<00:26:25.399> that<00:26:25.520> float<00:26:25.840> around 00:26:26.149 --> 00:26:26.159 align:start position:0% um uh ephemeral data that float around 00:26:26.159 --> 00:26:27.590 align:start position:0% um uh ephemeral data that float around generally<00:26:26.520> have<00:26:26.640> broadcast<00:26:27.039> semantics 00:26:27.590 --> 00:26:27.600 align:start position:0% generally have broadcast semantics 00:26:27.600 --> 00:26:29.230 align:start position:0% generally have broadcast semantics potentially<00:26:27.960> exist<00:26:28.720> within<00:26:29.000> different 00:26:29.230 --> 00:26:29.240 align:start position:0% potentially exist within different 00:26:29.240 --> 00:26:31.549 align:start position:0% potentially exist within different networks<00:26:29.720> for<00:26:29.960> maybe<00:26:30.240> private<00:26:30.480> sub<00:26:30.720> networks 00:26:31.549 --> 00:26:31.559 align:start position:0% networks for maybe private sub networks 00:26:31.559 --> 00:26:33.750 align:start position:0% networks for maybe private sub networks so<00:26:31.840> yeah<00:26:32.399> whisper<00:26:32.799> would<00:26:32.960> work<00:26:33.240> particularly 00:26:33.750 --> 00:26:33.760 align:start position:0% so yeah whisper would work particularly 00:26:33.760 --> 00:26:35.190 align:start position:0% so yeah whisper would work particularly well<00:26:34.000> and<00:26:34.080> it<00:26:34.200> would<00:26:34.320> be<00:26:34.520> really<00:26:34.760> cool<00:26:35.000> if<00:26:35.080> we 00:26:35.190 --> 00:26:35.200 align:start position:0% well and it would be really cool if we 00:26:35.200 --> 00:26:37.310 align:start position:0% well and it would be really cool if we can<00:26:35.360> make<00:26:35.480> the<00:26:35.640> transaction<00:26:36.559> uh<00:26:36.720> publication 00:26:37.310 --> 00:26:37.320 align:start position:0% can make the transaction uh publication 00:26:37.320 --> 00:26:39.630 align:start position:0% can make the transaction uh publication stuff<00:26:37.919> actually<00:26:38.240> be<00:26:38.799> uh<00:26:38.919> just<00:26:39.080> an<00:26:39.200> application 00:26:39.630 --> 00:26:39.640 align:start position:0% stuff actually be uh just an application 00:26:39.640 --> 00:26:41.510 align:start position:0% stuff actually be uh just an application that<00:26:39.760> sits<00:26:39.960> on<00:26:40.120> top<00:26:40.279> of<00:26:40.399> whisper<00:26:41.000> yeah 00:26:41.510 --> 00:26:41.520 align:start position:0% that sits on top of whisper yeah 00:26:41.520 --> 00:26:51.180 align:start position:0% that sits on top of whisper yeah definitely<00:26:42.520> cool<00:26:43.080> um<00:26:43.279> thanks<00:26:43.600> guys<00:26:44.000> fantastic 00:26:51.180 --> 00:26:51.190 align:start position:0% 00:26:51.190 --> 00:26:55.309 align:start position:0% [Music]