WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:09.970 align:start position:0% [Applause] 00:00:09.970 --> 00:00:09.980 align:start position:0% 00:00:09.980 --> 00:00:15.730 align:start position:0% I<00:00:12.669> work<00:00:13.669> for<00:00:13.879> a<00:00:13.910> project<00:00:14.389> called<00:00:14.660> NIMH<00:00:15.230> and 00:00:15.730 --> 00:00:15.740 align:start position:0% I work for a project called NIMH and 00:00:15.740 --> 00:00:18.220 align:start position:0% I work for a project called NIMH and we're<00:00:16.430> talking<00:00:16.789> about<00:00:17.060> privacy<00:00:17.480> and<00:00:17.900> block 00:00:18.220 --> 00:00:18.230 align:start position:0% we're talking about privacy and block 00:00:18.230 --> 00:00:19.960 align:start position:0% we're talking about privacy and block panes<00:00:18.500> and<00:00:18.829> decentralized<00:00:19.430> systems<00:00:19.789> and 00:00:19.960 --> 00:00:19.970 align:start position:0% panes and decentralized systems and 00:00:19.970 --> 00:00:21.400 align:start position:0% panes and decentralized systems and distributed<00:00:20.060> systems<00:00:20.689> today<00:00:20.840> a<00:00:20.960> little<00:00:21.259> bit 00:00:21.400 --> 00:00:21.410 align:start position:0% distributed systems today a little bit 00:00:21.410 --> 00:00:24.640 align:start position:0% distributed systems today a little bit about<00:00:21.619> the<00:00:22.160> internet<00:00:22.550> and<00:00:22.930> sort<00:00:23.930> of<00:00:24.020> more 00:00:24.640 --> 00:00:24.650 align:start position:0% about the internet and sort of more 00:00:24.650 --> 00:00:26.380 align:start position:0% about the internet and sort of more general<00:00:25.070> systems<00:00:25.460> outside<00:00:25.640> the<00:00:25.939> block<00:00:26.119> chains 00:00:26.380 --> 00:00:26.390 align:start position:0% general systems outside the block chains 00:00:26.390 --> 00:00:29.769 align:start position:0% general systems outside the block chains and<00:00:26.810> where<00:00:27.050> a<00:00:27.619> project<00:00:27.920> is<00:00:28.339> basically<00:00:28.779> about 00:00:29.769 --> 00:00:29.779 align:start position:0% and where a project is basically about 00:00:29.779 --> 00:00:31.269 align:start position:0% and where a project is basically about privacy<00:00:30.140> the<00:00:30.500> kinds<00:00:30.800> of<00:00:30.859> things<00:00:31.039> we're<00:00:31.160> going 00:00:31.269 --> 00:00:31.279 align:start position:0% privacy the kinds of things we're going 00:00:31.279 --> 00:00:33.939 align:start position:0% privacy the kinds of things we're going to<00:00:31.310> talk<00:00:31.460> about<00:00:31.490> today<00:00:32.440> why<00:00:33.440> are<00:00:33.589> we<00:00:33.800> doing 00:00:33.939 --> 00:00:33.949 align:start position:0% to talk about today why are we doing 00:00:33.949 --> 00:00:35.770 align:start position:0% to talk about today why are we doing this<00:00:34.190> like<00:00:34.670> what<00:00:34.910> what<00:00:35.120> are<00:00:35.150> one<00:00:35.629> of<00:00:35.720> the 00:00:35.770 --> 00:00:35.780 align:start position:0% this like what what are one of the 00:00:35.780 --> 00:00:37.000 align:start position:0% this like what what are one of the things<00:00:35.989> that<00:00:36.110> were<00:00:36.170> interested<00:00:36.530> in<00:00:36.620> what<00:00:36.829> kind 00:00:37.000 --> 00:00:37.010 align:start position:0% things that were interested in what kind 00:00:37.010 --> 00:00:38.819 align:start position:0% things that were interested in what kind of<00:00:37.040> problems<00:00:37.339> were<00:00:37.400> interested<00:00:37.760> in<00:00:37.850> solving 00:00:38.819 --> 00:00:38.829 align:start position:0% of problems were interested in solving 00:00:38.829 --> 00:00:41.110 align:start position:0% of problems were interested in solving getting<00:00:39.829> the<00:00:39.949> quick<00:00:40.159> definition<00:00:40.699> of<00:00:40.820> privacy 00:00:41.110 --> 00:00:41.120 align:start position:0% getting the quick definition of privacy 00:00:41.120 --> 00:00:43.299 align:start position:0% getting the quick definition of privacy and<00:00:41.809> we're<00:00:41.900> going<00:00:42.050> to<00:00:42.079> talk<00:00:42.230> about<00:00:42.260> two<00:00:42.860> core 00:00:43.299 --> 00:00:43.309 align:start position:0% and we're going to talk about two core 00:00:43.309 --> 00:00:45.970 align:start position:0% and we're going to talk about two core technologies<00:00:43.940> so<00:00:44.120> that<00:00:44.149> we<00:00:44.390> are<00:00:44.680> working<00:00:45.680> on 00:00:45.970 --> 00:00:45.980 align:start position:0% technologies so that we are working on 00:00:45.980 --> 00:00:48.369 align:start position:0% technologies so that we are working on one<00:00:46.940> of<00:00:46.969> them<00:00:47.120> is<00:00:47.210> called<00:00:47.360> a<00:00:47.539> mixed<00:00:47.840> net<00:00:47.989> which 00:00:48.369 --> 00:00:48.379 align:start position:0% one of them is called a mixed net which 00:00:48.379 --> 00:00:52.889 align:start position:0% one of them is called a mixed net which is<00:00:48.410> a<00:00:48.559> kind<00:00:49.250> of<00:00:49.370> better<00:00:50.239> than<00:00:50.359> tor<00:00:50.840> way<00:00:51.559> of 00:00:52.889 --> 00:00:52.899 align:start position:0% is a kind of better than tor way of 00:00:52.899 --> 00:00:55.240 align:start position:0% is a kind of better than tor way of anonymizing<00:00:53.899> your<00:00:54.079> internet<00:00:54.379> traffic<00:00:54.559> and 00:00:55.240 --> 00:00:55.250 align:start position:0% anonymizing your internet traffic and 00:00:55.250 --> 00:00:57.069 align:start position:0% anonymizing your internet traffic and the<00:00:55.670> second<00:00:56.000> one<00:00:56.120> is<00:00:56.359> decentralized 00:00:57.069 --> 00:00:57.079 align:start position:0% the second one is decentralized 00:00:57.079 --> 00:01:01.389 align:start position:0% the second one is decentralized credentials<00:00:57.890> so<00:00:58.160> that's<00:00:58.340> kind<00:00:58.699> of<00:00:58.879> like<00:01:00.399> the 00:01:01.389 --> 00:01:01.399 align:start position:0% credentials so that's kind of like the 00:01:01.399 --> 00:01:02.650 align:start position:0% credentials so that's kind of like the quickest<00:01:01.760> way<00:01:01.910> I've<00:01:02.030> ever<00:01:02.059> tried<00:01:02.420> to<00:01:02.510> figure 00:01:02.650 --> 00:01:02.660 align:start position:0% quickest way I've ever tried to figure 00:01:02.660 --> 00:01:04.119 align:start position:0% quickest way I've ever tried to figure out<00:01:02.870> to<00:01:03.019> explain<00:01:03.590> it<00:01:03.710> to<00:01:03.769> people<00:01:03.800> with 00:01:04.119 --> 00:01:04.129 align:start position:0% out to explain it to people with 00:01:04.129 --> 00:01:07.510 align:start position:0% out to explain it to people with something<00:01:04.339> like<00:01:04.640> a<00:01:04.670> decentralized<00:01:05.479> a<00:01:05.780> lot<00:01:06.520> but 00:01:07.510 --> 00:01:07.520 align:start position:0% something like a decentralized a lot but 00:01:07.520 --> 00:01:08.889 align:start position:0% something like a decentralized a lot but it's<00:01:07.729> actually<00:01:07.850> much<00:01:08.149> more<00:01:08.270> powerful<00:01:08.780> than 00:01:08.889 --> 00:01:08.899 align:start position:0% it's actually much more powerful than 00:01:08.899 --> 00:01:10.919 align:start position:0% it's actually much more powerful than that<00:01:09.050> so<00:01:09.259> you<00:01:09.289> can<00:01:09.500> actually<00:01:09.530> use<00:01:09.800> it<00:01:10.070> to 00:01:10.919 --> 00:01:10.929 align:start position:0% that so you can actually use it to 00:01:10.929 --> 00:01:14.949 align:start position:0% that so you can actually use it to anonymize<00:01:12.280> pretty<00:01:13.280> much<00:01:13.429> any<00:01:13.959> crypto 00:01:14.949 --> 00:01:14.959 align:start position:0% anonymize pretty much any crypto 00:01:14.959 --> 00:01:16.180 align:start position:0% anonymize pretty much any crypto currency<00:01:15.289> transaction<00:01:15.860> or<00:01:15.950> block<00:01:16.160> a 00:01:16.180 --> 00:01:16.190 align:start position:0% currency transaction or block a 00:01:16.190 --> 00:01:18.430 align:start position:0% currency transaction or block a transaction<00:01:17.200> using 00:01:18.430 --> 00:01:18.440 align:start position:0% transaction using 00:01:18.440 --> 00:01:20.469 align:start position:0% transaction using anonymizing<00:01:19.160> claims<00:01:19.490> which<00:01:19.759> I'll<00:01:19.940> explain<00:01:20.179> in 00:01:20.469 --> 00:01:20.479 align:start position:0% anonymizing claims which I'll explain in 00:01:20.479 --> 00:01:22.779 align:start position:0% anonymizing claims which I'll explain in great<00:01:21.020> detail<00:01:21.380> in<00:01:21.530> just<00:01:21.560> a<00:01:21.709> moment<00:01:21.979> then<00:01:22.640> we'll 00:01:22.779 --> 00:01:22.789 align:start position:0% great detail in just a moment then we'll 00:01:22.789 --> 00:01:24.370 align:start position:0% great detail in just a moment then we'll do<00:01:22.880> a<00:01:22.910> quick<00:01:23.090> demo<00:01:23.810> and<00:01:24.080> then<00:01:24.170> we<00:01:24.229> have<00:01:24.349> a 00:01:24.370 --> 00:01:24.380 align:start position:0% do a quick demo and then we have a 00:01:24.380 --> 00:01:26.290 align:start position:0% do a quick demo and then we have a discussion<00:01:24.709> how<00:01:25.340> many<00:01:25.489> of<00:01:25.580> you<00:01:25.880> here<00:01:26.239> are 00:01:26.290 --> 00:01:26.300 align:start position:0% discussion how many of you here are 00:01:26.300 --> 00:01:28.809 align:start position:0% discussion how many of you here are developers<00:01:27.140> who<00:01:27.200> have<00:01:27.349> projects<00:01:27.830> that<00:01:28.069> maybe 00:01:28.809 --> 00:01:28.819 align:start position:0% developers who have projects that maybe 00:01:28.819 --> 00:01:31.240 align:start position:0% developers who have projects that maybe have<00:01:29.060> interests<00:01:29.420> in<00:01:29.509> privacy<00:01:29.920> you<00:01:30.920> can<00:01:31.069> be 00:01:31.240 --> 00:01:31.250 align:start position:0% have interests in privacy you can be 00:01:31.250 --> 00:01:32.919 align:start position:0% have interests in privacy you can be useful<00:01:31.399> to<00:01:31.819> have<00:01:31.940> different<00:01:32.630> privacy 00:01:32.919 --> 00:01:32.929 align:start position:0% useful to have different privacy 00:01:32.929 --> 00:01:36.580 align:start position:0% useful to have different privacy preserving<00:01:33.229> things<00:01:33.709> that's<00:01:34.780> great<00:01:35.780> I'm<00:01:36.259> super 00:01:36.580 --> 00:01:36.590 align:start position:0% preserving things that's great I'm super 00:01:36.590 --> 00:01:38.620 align:start position:0% preserving things that's great I'm super happy<00:01:36.679> ok<00:01:37.099> good<00:01:37.310> so<00:01:37.550> hopefully<00:01:38.300> we<00:01:38.390> can<00:01:38.479> have<00:01:38.569> a 00:01:38.620 --> 00:01:38.630 align:start position:0% happy ok good so hopefully we can have a 00:01:38.630 --> 00:01:40.749 align:start position:0% happy ok good so hopefully we can have a really<00:01:38.840> good<00:01:38.959> discussion<00:01:39.229> as<00:01:39.470> well<00:01:39.590> I<00:01:40.369> think 00:01:40.749 --> 00:01:40.759 align:start position:0% really good discussion as well I think 00:01:40.759 --> 00:01:42.309 align:start position:0% really good discussion as well I think we<00:01:40.880> should<00:01:40.910> introduce<00:01:41.179> ourselves<00:01:41.450> first<00:01:41.810> just 00:01:42.309 --> 00:01:42.319 align:start position:0% we should introduce ourselves first just 00:01:42.319 --> 00:01:48.760 align:start position:0% we should introduce ourselves first just as<00:01:42.979> people<00:01:43.190> so<00:01:46.479> my<00:01:47.479> name<00:01:47.660> is<00:01:47.780> andrew<00:01:48.319> scott<00:01:48.380> and 00:01:48.760 --> 00:01:48.770 align:start position:0% as people so my name is andrew scott and 00:01:48.770 --> 00:01:52.990 align:start position:0% as people so my name is andrew scott and their<00:01:49.009> head<00:01:49.220> of 00:01:52.990 --> 00:01:53.000 align:start position:0% 00:01:53.000 --> 00:01:56.600 align:start position:0% my<00:01:54.000> research<00:01:54.780> -<00:01:55.200> investing<00:01:55.740> technologies<00:01:56.369> and 00:01:56.600 --> 00:01:56.610 align:start position:0% my research - investing technologies and 00:01:56.610 --> 00:02:00.100 align:start position:0% my research - investing technologies and in<00:01:56.729> particular<00:01:57.090> and<00:01:57.479> identification<00:01:57.930> metals 00:02:00.100 --> 00:02:00.110 align:start position:0% in particular and identification metals 00:02:00.110 --> 00:02:03.350 align:start position:0% in particular and identification metals cool<00:02:01.110> and<00:02:01.409> my<00:02:01.710> name<00:02:01.860> is<00:02:01.950> Dave<00:02:02.100> Harrison<00:02:02.549> as<00:02:03.149> you 00:02:03.350 --> 00:02:03.360 align:start position:0% cool and my name is Dave Harrison as you 00:02:03.360 --> 00:02:05.270 align:start position:0% cool and my name is Dave Harrison as you can<00:02:03.479> see<00:02:03.630> from<00:02:03.780> my<00:02:03.869> last<00:02:04.170> name<00:02:04.380> I<00:02:04.680> got<00:02:04.950> quite<00:02:05.130> an 00:02:05.270 --> 00:02:05.280 align:start position:0% can see from my last name I got quite an 00:02:05.280 --> 00:02:08.870 align:start position:0% can see from my last name I got quite an early<00:02:05.340> start<00:02:05.729> with<00:02:05.880> encryption<00:02:07.789> I'm<00:02:08.789> a 00:02:08.870 --> 00:02:08.880 align:start position:0% early start with encryption I'm a 00:02:08.880 --> 00:02:11.150 align:start position:0% early start with encryption I'm a founding<00:02:09.660> member<00:02:09.720> of<00:02:10.170> decentralized 00:02:11.150 --> 00:02:11.160 align:start position:0% founding member of decentralized 00:02:11.160 --> 00:02:12.680 align:start position:0% founding member of decentralized derivatives<00:02:11.760> platform<00:02:12.180> called<00:02:12.390> the<00:02:12.510> Vega 00:02:12.680 --> 00:02:12.690 align:start position:0% derivatives platform called the Vega 00:02:12.690 --> 00:02:15.860 align:start position:0% derivatives platform called the Vega protocol<00:02:13.200> I<00:02:13.700> previously<00:02:14.700> built<00:02:15.090> a<00:02:15.330> started 00:02:15.860 --> 00:02:15.870 align:start position:0% protocol I previously built a started 00:02:15.870 --> 00:02:18.259 align:start position:0% protocol I previously built a started scalable<00:02:16.769> blockchain<00:02:17.550> and<00:02:17.730> consensus<00:02:18.150> system 00:02:18.259 --> 00:02:18.269 align:start position:0% scalable blockchain and consensus system 00:02:18.269 --> 00:02:20.449 align:start position:0% scalable blockchain and consensus system called<00:02:18.690> chain<00:02:18.900> space<00:02:19.170> moved<00:02:19.860> to<00:02:19.980> Libre<00:02:20.280> very 00:02:20.449 --> 00:02:20.459 align:start position:0% called chain space moved to Libre very 00:02:20.459 --> 00:02:23.210 align:start position:0% called chain space moved to Libre very briefly<00:02:20.849> and<00:02:21.209> I<00:02:21.720> thought<00:02:22.650> that<00:02:22.890> it<00:02:23.069> was 00:02:23.210 --> 00:02:23.220 align:start position:0% briefly and I thought that it was 00:02:23.220 --> 00:02:24.740 align:start position:0% briefly and I thought that it was actually<00:02:23.370> more<00:02:23.640> interested<00:02:24.030> in<00:02:24.090> working<00:02:24.239> on 00:02:24.740 --> 00:02:24.750 align:start position:0% actually more interested in working on 00:02:24.750 --> 00:02:26.930 align:start position:0% actually more interested in working on Internet<00:02:25.560> privacy<00:02:25.709> issues<00:02:26.310> since<00:02:26.550> that's<00:02:26.790> why 00:02:26.930 --> 00:02:26.940 align:start position:0% Internet privacy issues since that's why 00:02:26.940 --> 00:02:30.259 align:start position:0% Internet privacy issues since that's why I'm<00:02:27.060> working<00:02:27.330> here<00:02:27.450> at<00:02:27.920> the<00:02:28.920> wider<00:02:29.130> team<00:02:29.430> this 00:02:30.259 --> 00:02:30.269 align:start position:0% I'm working here at the wider team this 00:02:30.269 --> 00:02:33.080 align:start position:0% I'm working here at the wider team this is<00:02:30.480> the<00:02:30.780> kind<00:02:31.319> of<00:02:31.350> production<00:02:32.100> team<00:02:32.580> including 00:02:33.080 --> 00:02:33.090 align:start position:0% is the kind of production team including 00:02:33.090 --> 00:02:35.780 align:start position:0% is the kind of production team including some<00:02:33.269> of<00:02:33.299> our<00:02:33.450> coders<00:02:33.690> and<00:02:34.430> other<00:02:35.430> surrounding 00:02:35.780 --> 00:02:35.790 align:start position:0% some of our coders and other surrounding 00:02:35.790 --> 00:02:37.820 align:start position:0% some of our coders and other surrounding people<00:02:36.360> and<00:02:36.630> we<00:02:36.750> actually<00:02:37.019> have<00:02:37.170> quite<00:02:37.739> a 00:02:37.820 --> 00:02:37.830 align:start position:0% people and we actually have quite a 00:02:37.830 --> 00:02:40.370 align:start position:0% people and we actually have quite a large<00:02:38.069> team<00:02:38.430> of<00:02:38.780> advisers<00:02:39.780> from<00:02:40.049> across 00:02:40.370 --> 00:02:40.380 align:start position:0% large team of advisers from across 00:02:40.380 --> 00:02:42.440 align:start position:0% large team of advisers from across Europe<00:02:40.739> from<00:02:41.150> four<00:02:42.150> or<00:02:42.209> five<00:02:42.330> different 00:02:42.440 --> 00:02:42.450 align:start position:0% Europe from four or five different 00:02:42.450 --> 00:02:44.479 align:start position:0% Europe from four or five different universities<00:02:43.049> across<00:02:43.260> Europe<00:02:43.590> basically<00:02:43.769> so 00:02:44.479 --> 00:02:44.489 align:start position:0% universities across Europe basically so 00:02:44.489 --> 00:02:49.520 align:start position:0% universities across Europe basically so our<00:02:44.970> goals<00:02:45.980> we<00:02:46.980> have<00:02:47.069> one<00:02:47.280> goal<00:02:48.230> it's<00:02:49.230> pending 00:02:49.520 --> 00:02:49.530 align:start position:0% our goals we have one goal it's pending 00:02:49.530 --> 00:02:50.890 align:start position:0% our goals we have one goal it's pending mass<00:02:49.830> surveillance 00:02:50.890 --> 00:02:50.900 align:start position:0% mass surveillance 00:02:50.900 --> 00:02:55.870 align:start position:0% mass surveillance why<00:02:51.900> would<00:02:52.200> we<00:02:52.380> want<00:02:52.560> to<00:02:52.650> do<00:02:52.860> this<00:02:54.380> quick<00:02:55.380> quick 00:02:55.870 --> 00:02:55.880 align:start position:0% why would we want to do this quick quick 00:02:55.880 --> 00:02:58.940 align:start position:0% why would we want to do this quick quick kind<00:02:56.880> of<00:02:56.970> overview<00:02:57.390> I<00:02:57.870> kind<00:02:58.470> of<00:02:58.560> think<00:02:58.829> that 00:02:58.940 --> 00:02:58.950 align:start position:0% kind of overview I kind of think that 00:02:58.950 --> 00:03:00.620 align:start position:0% kind of overview I kind of think that the<00:02:59.130> present<00:02:59.489> situation<00:02:59.640> on<00:03:00.090> the<00:03:00.209> Internet<00:03:00.540> is 00:03:00.620 --> 00:03:00.630 align:start position:0% the present situation on the Internet is 00:03:00.630 --> 00:03:03.319 align:start position:0% the present situation on the Internet is something<00:03:00.840> like<00:03:01.140> crypto<00:03:02.130> Wars<00:03:02.340> -<00:03:02.820> so<00:03:03.239> it's 00:03:03.319 --> 00:03:03.329 align:start position:0% something like crypto Wars - so it's 00:03:03.329 --> 00:03:05.810 align:start position:0% something like crypto Wars - so it's like<00:03:03.390> the<00:03:03.600> sequel<00:03:03.989> to<00:03:04.170> the<00:03:04.260> crypto<00:03:04.560> Wars<00:03:04.820> for 00:03:05.810 --> 00:03:05.820 align:start position:0% like the sequel to the crypto Wars for 00:03:05.820 --> 00:03:07.340 align:start position:0% like the sequel to the crypto Wars for those<00:03:05.940> of<00:03:06.090> you<00:03:06.180> who<00:03:06.299> miss<00:03:06.450> crypto<00:03:06.810> Wars<00:03:06.989> one 00:03:07.340 --> 00:03:07.350 align:start position:0% those of you who miss crypto Wars one 00:03:07.350 --> 00:03:09.680 align:start position:0% those of you who miss crypto Wars one the<00:03:07.530> original<00:03:07.859> episode<00:03:08.220> the<00:03:08.609> 1990s<00:03:09.480> were 00:03:09.680 --> 00:03:09.690 align:start position:0% the original episode the 1990s were 00:03:09.690 --> 00:03:11.860 align:start position:0% the original episode the 1990s were quite<00:03:09.989> there<00:03:10.500> were<00:03:10.620> quite<00:03:10.829> bold<00:03:11.100> attempts<00:03:11.609> by 00:03:11.860 --> 00:03:11.870 align:start position:0% quite there were quite bold attempts by 00:03:11.870 --> 00:03:14.960 align:start position:0% quite there were quite bold attempts by Lina's<00:03:12.870> government<00:03:13.260> to<00:03:13.320> legislate<00:03:13.970> things 00:03:14.960 --> 00:03:14.970 align:start position:0% Lina's government to legislate things 00:03:14.970 --> 00:03:16.819 align:start position:0% Lina's government to legislate things like<00:03:15.150> hardware<00:03:15.480> backdoors<00:03:16.140> into<00:03:16.440> computers 00:03:16.819 --> 00:03:16.829 align:start position:0% like hardware backdoors into computers 00:03:16.829 --> 00:03:18.979 align:start position:0% like hardware backdoors into computers and<00:03:16.890> network<00:03:17.190> systems<00:03:17.670> and<00:03:18.600> they<00:03:18.780> basically 00:03:18.979 --> 00:03:18.989 align:start position:0% and network systems and they basically 00:03:18.989 --> 00:03:21.229 align:start position:0% and network systems and they basically want<00:03:19.380> to<00:03:19.440> work<00:03:19.650> reroute<00:03:20.070> all<00:03:20.310> cryptography<00:03:21.120> at 00:03:21.229 --> 00:03:21.239 align:start position:0% want to work reroute all cryptography at 00:03:21.239 --> 00:03:23.330 align:start position:0% want to work reroute all cryptography at the<00:03:21.359> time<00:03:21.540> that<00:03:21.750> was<00:03:21.959> so<00:03:22.739> they're<00:03:22.920> kind<00:03:23.130> of<00:03:23.160> big 00:03:23.330 --> 00:03:23.340 align:start position:0% the time that was so they're kind of big 00:03:23.340 --> 00:03:25.819 align:start position:0% the time that was so they're kind of big aim<00:03:23.579> strong<00:03:24.359> cryptography<00:03:24.720> in<00:03:25.200> the<00:03:25.290> 90s<00:03:25.650> was 00:03:25.819 --> 00:03:25.829 align:start position:0% aim strong cryptography in the 90s was 00:03:25.829 --> 00:03:28.310 align:start position:0% aim strong cryptography in the 90s was classed<00:03:26.070> as<00:03:26.280> ammunition<00:03:26.790> and<00:03:27.030> it<00:03:27.840> was<00:03:27.959> subject 00:03:28.310 --> 00:03:28.320 align:start position:0% classed as ammunition and it was subject 00:03:28.320 --> 00:03:29.960 align:start position:0% classed as ammunition and it was subject to<00:03:28.350> export<00:03:28.769> bans<00:03:28.980> so<00:03:29.549> that<00:03:29.700> you<00:03:29.760> couldn't 00:03:29.960 --> 00:03:29.970 align:start position:0% to export bans so that you couldn't 00:03:29.970 --> 00:03:33.140 align:start position:0% to export bans so that you couldn't share<00:03:30.209> it<00:03:30.329> outside<00:03:30.600> the<00:03:30.690> United<00:03:30.959> States<00:03:32.150> many 00:03:33.140 --> 00:03:33.150 align:start position:0% share it outside the United States many 00:03:33.150 --> 00:03:35.180 align:start position:0% share it outside the United States many arguments<00:03:33.780> against<00:03:34.049> privacy<00:03:34.590> were<00:03:34.769> advanced 00:03:35.180 --> 00:03:35.190 align:start position:0% arguments against privacy were advanced 00:03:35.190 --> 00:03:37.280 align:start position:0% arguments against privacy were advanced at<00:03:35.310> that<00:03:35.459> time<00:03:35.760> and<00:03:36.180> if<00:03:36.600> the<00:03:36.720> anti<00:03:36.900> privacy 00:03:37.280 --> 00:03:37.290 align:start position:0% at that time and if the anti privacy 00:03:37.290 --> 00:03:39.650 align:start position:0% at that time and if the anti privacy advocates<00:03:37.709> had<00:03:37.950> won<00:03:38.160> in<00:03:38.310> the<00:03:38.400> 90s<00:03:38.790> most<00:03:39.450> of 00:03:39.650 --> 00:03:39.660 align:start position:0% advocates had won in the 90s most of 00:03:39.660 --> 00:03:41.870 align:start position:0% advocates had won in the 90s most of internet<00:03:40.019> systems<00:03:40.410> that<00:03:40.650> we<00:03:41.220> use<00:03:41.250> today<00:03:41.489> would 00:03:41.870 --> 00:03:41.880 align:start position:0% internet systems that we use today would 00:03:41.880 --> 00:03:44.120 align:start position:0% internet systems that we use today would probably<00:03:41.910> never<00:03:42.569> have<00:03:42.720> happened<00:03:43.019> but<00:03:43.799> as<00:03:43.980> it 00:03:44.120 --> 00:03:44.130 align:start position:0% probably never have happened but as it 00:03:44.130 --> 00:03:45.770 align:start position:0% probably never have happened but as it turns<00:03:44.310> out<00:03:44.459> the<00:03:44.700> original<00:03:44.880> crypto<00:03:45.299> Wars<00:03:45.450> were 00:03:45.770 --> 00:03:45.780 align:start position:0% turns out the original crypto Wars were 00:03:45.780 --> 00:03:49.809 align:start position:0% turns out the original crypto Wars were one<00:03:46.019> during<00:03:46.799> the<00:03:46.889> course<00:03:47.130> of<00:03:47.340> the<00:03:47.549> nineties<00:03:48.260> I 00:03:49.809 --> 00:03:49.819 align:start position:0% one during the course of the nineties I 00:03:49.819 --> 00:03:51.949 align:start position:0% one during the course of the nineties I think<00:03:50.819> that<00:03:50.970> the<00:03:51.090> available<00:03:51.480> the 00:03:51.949 --> 00:03:51.959 align:start position:0% think that the available the 00:03:51.959 --> 00:03:55.729 align:start position:0% think that the available the availability<00:03:52.380> of<00:03:52.829> SSL<00:03:53.819> probably<00:03:54.450> did<00:03:54.630> more<00:03:54.900> to 00:03:55.729 --> 00:03:55.739 align:start position:0% availability of SSL probably did more to 00:03:55.739 --> 00:03:56.690 align:start position:0% availability of SSL probably did more to advance<00:03:55.859> here 00:03:56.690 --> 00:03:56.700 align:start position:0% advance here 00:03:56.700 --> 00:03:59.990 align:start position:0% advance here security<00:03:57.510> and<00:03:58.170> privacy<00:03:58.440> of<00:03:58.680> Internet<00:03:59.160> in<00:03:59.819> the 00:03:59.990 --> 00:04:00.000 align:start position:0% security and privacy of Internet in the 00:04:00.000 --> 00:04:01.610 align:start position:0% security and privacy of Internet in the nominees<00:04:00.300> than<00:04:00.450> anything<00:04:00.599> else<00:04:00.840> is<00:04:01.290> rarely 00:04:01.610 --> 00:04:01.620 align:start position:0% nominees than anything else is rarely 00:04:01.620 --> 00:04:04.490 align:start position:0% nominees than anything else is rarely viewed<00:04:02.010> this<00:04:02.190> way<00:04:02.250> but<00:04:03.239> SSL<00:04:03.690> and<00:04:04.020> success 00:04:04.490 --> 00:04:04.500 align:start position:0% viewed this way but SSL and success 00:04:04.500 --> 00:04:07.190 align:start position:0% viewed this way but SSL and success protocols<00:04:04.980> like<00:04:05.099> TLS<00:04:05.459> are<00:04:06.150> a<00:04:06.209> practical<00:04:06.870> and 00:04:07.190 --> 00:04:07.200 align:start position:0% protocols like TLS are a practical and 00:04:07.200 --> 00:04:09.530 align:start position:0% protocols like TLS are a practical and very<00:04:07.470> important<00:04:07.980> contribution<00:04:08.610> to<00:04:09.300> help 00:04:09.530 --> 00:04:09.540 align:start position:0% very important contribution to help 00:04:09.540 --> 00:04:11.080 align:start position:0% very important contribution to help ensure<00:04:09.840> a<00:04:09.870> civil<00:04:10.230> rights<00:04:10.410> worldwide 00:04:11.080 --> 00:04:11.090 align:start position:0% ensure a civil rights worldwide 00:04:11.090 --> 00:04:13.130 align:start position:0% ensure a civil rights worldwide Transport<00:04:12.090> Security<00:04:12.239> is<00:04:12.780> the<00:04:12.900> core 00:04:13.130 --> 00:04:13.140 align:start position:0% Transport Security is the core 00:04:13.140 --> 00:04:15.290 align:start position:0% Transport Security is the core infrastructure<00:04:13.770> of<00:04:14.130> global<00:04:14.580> civil<00:04:14.880> society 00:04:15.290 --> 00:04:15.300 align:start position:0% infrastructure of global civil society 00:04:15.300 --> 00:04:19.580 align:start position:0% infrastructure of global civil society in<00:04:15.660> my<00:04:16.049> view<00:04:16.430> it<00:04:17.430> also<00:04:17.760> ensured<00:04:18.419> that<00:04:19.290> a<00:04:19.350> lot<00:04:19.560> of 00:04:19.580 --> 00:04:19.590 align:start position:0% in my view it also ensured that a lot of 00:04:19.590 --> 00:04:22.300 align:start position:0% in my view it also ensured that a lot of new<00:04:19.799> industries<00:04:20.250> categories<00:04:20.820> so<00:04:21.359> things<00:04:21.570> like 00:04:22.300 --> 00:04:22.310 align:start position:0% new industries categories so things like 00:04:22.310 --> 00:04:25.460 align:start position:0% new industries categories so things like e-commerce<00:04:23.630> internet<00:04:24.630> banking<00:04:25.050> private 00:04:25.460 --> 00:04:25.470 align:start position:0% e-commerce internet banking private 00:04:25.470 --> 00:04:27.620 align:start position:0% e-commerce internet banking private messaging<00:04:25.889> photo<00:04:26.220> sharing<00:04:26.490> many<00:04:27.419> of<00:04:27.540> the 00:04:27.620 --> 00:04:27.630 align:start position:0% messaging photo sharing many of the 00:04:27.630 --> 00:04:29.090 align:start position:0% messaging photo sharing many of the convenience<00:04:28.169> of<00:04:28.260> the<00:04:28.350> modern<00:04:28.650> life<00:04:28.800> that<00:04:28.830> we 00:04:29.090 --> 00:04:29.100 align:start position:0% convenience of the modern life that we 00:04:29.100 --> 00:04:31.100 align:start position:0% convenience of the modern life that we take<00:04:29.340> for<00:04:29.520> granted<00:04:29.900> everything<00:04:30.900> would<00:04:31.020> be 00:04:31.100 --> 00:04:31.110 align:start position:0% take for granted everything would be 00:04:31.110 --> 00:04:33.200 align:start position:0% take for granted everything would be very<00:04:31.320> different<00:04:31.590> today<00:04:31.889> if<00:04:32.280> the<00:04:32.400> coders<00:04:32.760> of 00:04:33.200 --> 00:04:33.210 align:start position:0% very different today if the coders of 00:04:33.210 --> 00:04:35.930 align:start position:0% very different today if the coders of starting<00:04:33.750> in<00:04:33.840> the<00:04:33.900> 90s<00:04:34.290> have<00:04:34.800> been<00:04:34.979> prevented 00:04:35.930 --> 00:04:35.940 align:start position:0% starting in the 90s have been prevented 00:04:35.940 --> 00:04:40.219 align:start position:0% starting in the 90s have been prevented from<00:04:36.060> protecting<00:04:36.570> user<00:04:36.780> data<00:04:37.050> now<00:04:37.850> today<00:04:39.229> just 00:04:40.219 --> 00:04:40.229 align:start position:0% from protecting user data now today just 00:04:40.229 --> 00:04:42.290 align:start position:0% from protecting user data now today just like<00:04:40.410> in<00:04:40.620> the<00:04:40.710> 90s<00:04:41.040> we<00:04:41.190> have<00:04:41.340> a<00:04:41.370> kind<00:04:42.090> of<00:04:42.150> new 00:04:42.290 --> 00:04:42.300 align:start position:0% like in the 90s we have a kind of new 00:04:42.300 --> 00:04:44.810 align:start position:0% like in the 90s we have a kind of new technical<00:04:43.010> set<00:04:44.010> of<00:04:44.100> possibilities<00:04:44.460> in<00:04:44.790> front 00:04:44.810 --> 00:04:44.820 align:start position:0% technical set of possibilities in front 00:04:44.820 --> 00:04:47.900 align:start position:0% technical set of possibilities in front of<00:04:45.030> us<00:04:45.120> and<00:04:45.300> the<00:04:45.720> same<00:04:45.930> arguments<00:04:46.910> about 00:04:47.900 --> 00:04:47.910 align:start position:0% of us and the same arguments about 00:04:47.910 --> 00:04:52.030 align:start position:0% of us and the same arguments about privacy<00:04:48.450> are<00:04:48.630> being<00:04:49.220> advanced<00:04:50.220> I<00:04:50.400> think<00:04:51.090> that 00:04:52.030 --> 00:04:52.040 align:start position:0% privacy are being advanced I think that 00:04:52.040 --> 00:04:54.800 align:start position:0% privacy are being advanced I think that we<00:04:53.040> have<00:04:53.250> to<00:04:53.430> we<00:04:53.760> have<00:04:53.790> to<00:04:53.940> win<00:04:54.210> the<00:04:54.600> kind<00:04:54.780> of 00:04:54.800 --> 00:04:54.810 align:start position:0% we have to we have to win the kind of 00:04:54.810 --> 00:04:57.469 align:start position:0% we have to we have to win the kind of crypto<00:04:55.139> Wars<00:04:55.290> to<00:04:55.590> in<00:04:56.160> order<00:04:56.340> to<00:04:56.490> make<00:04:56.610> both 00:04:57.469 --> 00:04:57.479 align:start position:0% crypto Wars to in order to make both 00:04:57.479 --> 00:05:00.500 align:start position:0% crypto Wars to in order to make both global<00:04:58.260> civil<00:04:58.500> society<00:04:58.919> secure<00:04:59.460> and<00:04:59.910> also 00:05:00.500 --> 00:05:00.510 align:start position:0% global civil society secure and also 00:05:00.510 --> 00:05:02.719 align:start position:0% global civil society secure and also take<00:05:01.410> advantage<00:05:01.440> of<00:05:01.979> the<00:05:02.039> new<00:05:02.250> economic 00:05:02.719 --> 00:05:02.729 align:start position:0% take advantage of the new economic 00:05:02.729 --> 00:05:03.770 align:start position:0% take advantage of the new economic opportunities<00:05:02.820> that<00:05:03.300> we<00:05:03.419> have<00:05:03.539> in<00:05:03.600> front<00:05:03.660> of 00:05:03.770 --> 00:05:03.780 align:start position:0% opportunities that we have in front of 00:05:03.780 --> 00:05:05.529 align:start position:0% opportunities that we have in front of us 00:05:05.529 --> 00:05:05.539 align:start position:0% us 00:05:05.539 --> 00:05:08.540 align:start position:0% us yeah<00:05:06.539> so<00:05:06.810> that's<00:05:06.930> in<00:05:07.800> a<00:05:08.039> nutshell<00:05:08.070> the<00:05:08.520> reason 00:05:08.540 --> 00:05:08.550 align:start position:0% yeah so that's in a nutshell the reason 00:05:08.550 --> 00:05:11.650 align:start position:0% yeah so that's in a nutshell the reason why<00:05:08.970> we're<00:05:09.240> doing<00:05:09.390> this 00:05:11.650 --> 00:05:11.660 align:start position:0% 00:05:11.660 --> 00:05:17.480 align:start position:0% how<00:05:13.430> ok<00:05:14.750> so<00:05:15.750> you<00:05:16.260> might<00:05:16.440> rightly<00:05:17.039> ask<00:05:17.160> how 00:05:17.480 --> 00:05:17.490 align:start position:0% how ok so you might rightly ask how 00:05:17.490 --> 00:05:19.580 align:start position:0% how ok so you might rightly ask how we're<00:05:17.729> planning<00:05:18.060> to<00:05:18.090> do<00:05:18.330> this<00:05:18.500> we<00:05:19.500> have 00:05:19.580 --> 00:05:19.590 align:start position:0% we're planning to do this we have 00:05:19.590 --> 00:05:21.650 align:start position:0% we're planning to do this we have basically<00:05:20.039> two<00:05:20.160> core<00:05:20.729> technologies<00:05:21.390> in<00:05:21.570> our 00:05:21.650 --> 00:05:21.660 align:start position:0% basically two core technologies in our 00:05:21.660 --> 00:05:24.170 align:start position:0% basically two core technologies in our system<00:05:22.050> the<00:05:22.650> first<00:05:22.830> one<00:05:23.130> as<00:05:23.400> I<00:05:23.550> said<00:05:23.760> as<00:05:23.880> a<00:05:23.910> mix 00:05:24.170 --> 00:05:24.180 align:start position:0% system the first one as I said as a mix 00:05:24.180 --> 00:05:26.270 align:start position:0% system the first one as I said as a mix then<00:05:24.390> which<00:05:25.050> is<00:05:25.169> a<00:05:25.200> better<00:05:25.410> than<00:05:25.530> tor<00:05:25.919> network 00:05:26.270 --> 00:05:26.280 align:start position:0% then which is a better than tor network 00:05:26.280 --> 00:05:30.409 align:start position:0% then which is a better than tor network security<00:05:26.850> layer<00:05:27.120> and<00:05:28.160> Anya's<00:05:29.190> Mixon<00:05:30.000> expert 00:05:30.409 --> 00:05:30.419 align:start position:0% security layer and Anya's Mixon expert 00:05:30.419 --> 00:05:32.240 align:start position:0% security layer and Anya's Mixon expert she's<00:05:30.570> going<00:05:30.750> to<00:05:30.810> talk<00:05:30.960> about<00:05:31.229> what<00:05:32.039> better 00:05:32.240 --> 00:05:32.250 align:start position:0% she's going to talk about what better 00:05:32.250 --> 00:05:34.580 align:start position:0% she's going to talk about what better than<00:05:32.490> tor<00:05:32.760> means<00:05:33.000> not<00:05:33.990> to<00:05:34.110> rag<00:05:34.260> on<00:05:34.410> tour 00:05:34.580 --> 00:05:34.590 align:start position:0% than tor means not to rag on tour 00:05:34.590 --> 00:05:35.510 align:start position:0% than tor means not to rag on tour because<00:05:34.680> it<00:05:34.860> actually<00:05:35.100> does<00:05:35.220> a<00:05:35.280> really<00:05:35.310> good 00:05:35.510 --> 00:05:35.520 align:start position:0% because it actually does a really good 00:05:35.520 --> 00:05:37.909 align:start position:0% because it actually does a really good job<00:05:35.580> but<00:05:36.300> there<00:05:36.720> are<00:05:36.960> certain<00:05:37.650> attacks 00:05:37.909 --> 00:05:37.919 align:start position:0% job but there are certain attacks 00:05:37.919 --> 00:05:40.480 align:start position:0% job but there are certain attacks against<00:05:38.310> tour<00:05:38.520> and<00:05:38.880> we<00:05:39.690> think<00:05:39.900> we<00:05:39.960> can<00:05:40.110> just 00:05:40.480 --> 00:05:40.490 align:start position:0% against tour and we think we can just 00:05:40.490 --> 00:05:42.860 align:start position:0% against tour and we think we can just generally<00:05:41.490> do<00:05:41.580> a<00:05:41.640> better<00:05:41.789> job<00:05:41.850> the<00:05:42.510> second 00:05:42.860 --> 00:05:42.870 align:start position:0% generally do a better job the second 00:05:42.870 --> 00:05:44.630 align:start position:0% generally do a better job the second thing<00:05:43.050> which<00:05:43.350> I'll<00:05:43.530> talk<00:05:43.710> about<00:05:43.770> is<00:05:44.550> a 00:05:44.630 --> 00:05:44.640 align:start position:0% thing which I'll talk about is a 00:05:44.640 --> 00:05:47.990 align:start position:0% thing which I'll talk about is a signature<00:05:45.060> scheme<00:05:45.390> that<00:05:45.570> provides<00:05:47.000> these 00:05:47.990 --> 00:05:48.000 align:start position:0% signature scheme that provides these 00:05:48.000 --> 00:05:50.719 align:start position:0% signature scheme that provides these properties<00:05:49.100> and<00:05:50.100> I'll<00:05:50.250> go<00:05:50.340> into<00:05:50.550> those<00:05:50.669> in 00:05:50.719 --> 00:05:50.729 align:start position:0% properties and I'll go into those in 00:05:50.729 --> 00:05:52.760 align:start position:0% properties and I'll go into those in detail<00:05:50.970> in<00:05:51.450> a<00:05:51.539> little<00:05:51.720> bit<00:05:51.840> but<00:05:52.320> first<00:05:52.530> I'll 00:05:52.760 --> 00:05:52.770 align:start position:0% detail in a little bit but first I'll 00:05:52.770 --> 00:05:58.520 align:start position:0% detail in a little bit but first I'll hand<00:05:53.010> off<00:05:53.160> to<00:05:53.220> money 00:05:58.520 --> 00:05:58.530 align:start position:0% 00:05:58.530 --> 00:06:01.020 align:start position:0% it's<00:05:59.530> the<00:05:59.680> first<00:05:59.889> time<00:06:00.040> using<00:06:00.370> the<00:06:00.639> clickers 00:06:01.020 --> 00:06:01.030 align:start position:0% it's the first time using the clickers 00:06:01.030 --> 00:06:03.330 align:start position:0% it's the first time using the clickers Obama's<00:06:01.540> accident<00:06:02.020> like<00:06:02.230> explode<00:06:02.800> the<00:06:02.980> screen 00:06:03.330 --> 00:06:03.340 align:start position:0% Obama's accident like explode the screen 00:06:03.340 --> 00:06:06.300 align:start position:0% Obama's accident like explode the screen or<00:06:03.580> try<00:06:03.820> not<00:06:04.030> to<00:06:04.290> so<00:06:05.290> before<00:06:05.590> we're<00:06:05.740> gonna<00:06:05.889> jump 00:06:06.300 --> 00:06:06.310 align:start position:0% or try not to so before we're gonna jump 00:06:06.310 --> 00:06:08.700 align:start position:0% or try not to so before we're gonna jump to<00:06:06.580> like<00:06:06.820> discussing<00:06:07.600> what<00:06:07.810> big<00:06:07.990> networks<00:06:08.440> are 00:06:08.700 --> 00:06:08.710 align:start position:0% to like discussing what big networks are 00:06:08.710 --> 00:06:11.100 align:start position:0% to like discussing what big networks are alleges<00:06:09.250> discuss<00:06:09.700> what<00:06:09.910> privacy<00:06:10.419> actually 00:06:11.100 --> 00:06:11.110 align:start position:0% alleges discuss what privacy actually 00:06:11.110 --> 00:06:13.590 align:start position:0% alleges discuss what privacy actually means<00:06:11.350> to<00:06:11.710> privacy<00:06:12.070> the<00:06:12.480> fundamental<00:06:13.480> human 00:06:13.590 --> 00:06:13.600 align:start position:0% means to privacy the fundamental human 00:06:13.600 --> 00:06:16.470 align:start position:0% means to privacy the fundamental human right<00:06:13.990> and<00:06:14.590> we<00:06:14.980> can<00:06:15.130> think<00:06:15.310> about<00:06:15.639> privacy<00:06:15.940> in 00:06:16.470 --> 00:06:16.480 align:start position:0% right and we can think about privacy in 00:06:16.480 --> 00:06:19.770 align:start position:0% right and we can think about privacy in the<00:06:16.660> context<00:06:17.200> of<00:06:17.880> legal<00:06:18.880> basis<00:06:19.389> in<00:06:19.660> the 00:06:19.770 --> 00:06:19.780 align:start position:0% the context of legal basis in the 00:06:19.780 --> 00:06:22.080 align:start position:0% the context of legal basis in the content<00:06:20.440> in<00:06:20.710> the<00:06:20.889> context<00:06:21.250> of<00:06:21.400> human<00:06:21.639> need<00:06:22.060> and 00:06:22.080 --> 00:06:22.090 align:start position:0% content in the context of human need and 00:06:22.090 --> 00:06:24.030 align:start position:0% content in the context of human need and we<00:06:22.450> can<00:06:22.480> also<00:06:22.750> think<00:06:23.020> about<00:06:23.139> privacy<00:06:23.740> in<00:06:23.919> the 00:06:24.030 --> 00:06:24.040 align:start position:0% we can also think about privacy in the 00:06:24.040 --> 00:06:26.700 align:start position:0% we can also think about privacy in the context<00:06:24.400> of<00:06:24.520> computer<00:06:24.940> security<00:06:25.560> so<00:06:26.560> in 00:06:26.700 --> 00:06:26.710 align:start position:0% context of computer security so in 00:06:26.710 --> 00:06:29.129 align:start position:0% context of computer security so in context<00:06:27.130> of<00:06:27.250> computer<00:06:27.669> security<00:06:28.300> and<00:06:28.780> in<00:06:28.900> any 00:06:29.129 --> 00:06:29.139 align:start position:0% context of computer security and in any 00:06:29.139 --> 00:06:31.620 align:start position:0% context of computer security and in any other<00:06:29.290> the<00:06:29.830> most<00:06:30.040> general<00:06:30.729> way<00:06:31.060> to<00:06:31.090> define 00:06:31.620 --> 00:06:31.630 align:start position:0% other the most general way to define 00:06:31.630 --> 00:06:34.469 align:start position:0% other the most general way to define privacy<00:06:32.320> is<00:06:32.530> that<00:06:32.710> privacy<00:06:33.610> is<00:06:34.000> the<00:06:34.270> ability 00:06:34.469 --> 00:06:34.479 align:start position:0% privacy is that privacy is the ability 00:06:34.479 --> 00:06:36.900 align:start position:0% privacy is that privacy is the ability for<00:06:34.720> us<00:06:35.050> to<00:06:35.080> decide<00:06:35.770> what<00:06:36.669> type<00:06:36.850> of 00:06:36.900 --> 00:06:36.910 align:start position:0% for us to decide what type of 00:06:36.910 --> 00:06:38.850 align:start position:0% for us to decide what type of information<00:06:37.389> we<00:06:37.900> would<00:06:38.050> like<00:06:38.260> to<00:06:38.500> share<00:06:38.680> with 00:06:38.850 --> 00:06:38.860 align:start position:0% information we would like to share with 00:06:38.860 --> 00:06:40.740 align:start position:0% information we would like to share with other<00:06:39.070> people<00:06:39.160> or<00:06:40.000> disclosed<00:06:40.540> about 00:06:40.740 --> 00:06:40.750 align:start position:0% other people or disclosed about 00:06:40.750 --> 00:06:44.730 align:start position:0% other people or disclosed about ourselves<00:06:41.200> and<00:06:42.210> privacy<00:06:43.210> is<00:06:43.389> a<00:06:43.419> is<00:06:44.320> a<00:06:44.380> very 00:06:44.730 --> 00:06:44.740 align:start position:0% ourselves and privacy is a is a very 00:06:44.740 --> 00:06:46.469 align:start position:0% ourselves and privacy is a is a very complex<00:06:45.220> topic<00:06:45.490> because<00:06:46.030> when<00:06:46.300> we<00:06:46.419> are 00:06:46.469 --> 00:06:46.479 align:start position:0% complex topic because when we are 00:06:46.479 --> 00:06:49.620 align:start position:0% complex topic because when we are building<00:06:47.430> privacy<00:06:48.430> enhancing<00:06:48.550> systems<00:06:49.330> we 00:06:49.620 --> 00:06:49.630 align:start position:0% building privacy enhancing systems we 00:06:49.630 --> 00:06:51.420 align:start position:0% building privacy enhancing systems we have<00:06:49.810> to<00:06:49.960> make<00:06:50.169> sure<00:06:50.440> that<00:06:50.770> we're<00:06:51.310> gonna 00:06:51.420 --> 00:06:51.430 align:start position:0% have to make sure that we're gonna 00:06:51.430 --> 00:06:53.430 align:start position:0% have to make sure that we're gonna consider<00:06:51.820> each<00:06:52.240> of<00:06:52.419> the<00:06:52.570> components<00:06:53.169> of<00:06:53.290> the 00:06:53.430 --> 00:06:53.440 align:start position:0% consider each of the components of the 00:06:53.440 --> 00:06:55.230 align:start position:0% consider each of the components of the system<00:06:53.889> in<00:06:54.070> terms<00:06:54.100> of<00:06:54.400> privacy<00:06:54.940> so<00:06:54.970> it's<00:06:55.210> a 00:06:55.230 --> 00:06:55.240 align:start position:0% system in terms of privacy so it's a 00:06:55.240 --> 00:06:57.390 align:start position:0% system in terms of privacy so it's a very<00:06:55.419> holistic<00:06:55.720> property<00:06:56.440> which<00:06:56.979> means<00:06:57.220> that 00:06:57.390 --> 00:06:57.400 align:start position:0% very holistic property which means that 00:06:57.400 --> 00:06:59.430 align:start position:0% very holistic property which means that the<00:06:57.520> information<00:06:57.669> leakage<00:06:58.540> in<00:06:58.870> one<00:06:59.169> of<00:06:59.320> the 00:06:59.430 --> 00:06:59.440 align:start position:0% the information leakage in one of the 00:06:59.440 --> 00:07:01.770 align:start position:0% the information leakage in one of the components<00:06:59.979> of<00:07:00.070> the<00:07:00.190> system<00:07:00.400> may<00:07:01.270> vary 00:07:01.770 --> 00:07:01.780 align:start position:0% components of the system may vary 00:07:01.780 --> 00:07:03.150 align:start position:0% components of the system may vary significantly 00:07:03.150 --> 00:07:03.160 align:start position:0% significantly 00:07:03.160 --> 00:07:06.870 align:start position:0% significantly decorate<00:07:04.000> the<00:07:04.240> privacy<00:07:04.690> properties<00:07:05.880> provided 00:07:06.870 --> 00:07:06.880 align:start position:0% decorate the privacy properties provided 00:07:06.880 --> 00:07:08.400 align:start position:0% decorate the privacy properties provided by<00:07:07.030> given<00:07:07.300> the<00:07:07.450> most<00:07:07.630> and<00:07:08.050> hence 00:07:08.400 --> 00:07:08.410 align:start position:0% by given the most and hence 00:07:08.410 --> 00:07:10.230 align:start position:0% by given the most and hence cryptographic<00:07:09.010> techniques<00:07:09.729> in<00:07:10.000> the<00:07:10.120> other 00:07:10.230 --> 00:07:10.240 align:start position:0% cryptographic techniques in the other 00:07:10.240 --> 00:07:13.409 align:start position:0% cryptographic techniques in the other component<00:07:10.840> of<00:07:10.960> the<00:07:11.020> system<00:07:11.640> so<00:07:12.640> with<00:07:12.850> because 00:07:13.409 --> 00:07:13.419 align:start position:0% component of the system so with because 00:07:13.419 --> 00:07:15.120 align:start position:0% component of the system so with because today<00:07:13.750> we<00:07:13.900> are<00:07:13.960> talking<00:07:14.080> about<00:07:14.289> them<00:07:14.740> and<00:07:14.919> them 00:07:15.120 --> 00:07:15.130 align:start position:0% today we are talking about them and them 00:07:15.130 --> 00:07:17.909 align:start position:0% today we are talking about them and them is<00:07:15.310> a<00:07:15.789> system<00:07:16.270> for<00:07:16.300> enhancing<00:07:17.110> the<00:07:17.320> privacy 00:07:17.909 --> 00:07:17.919 align:start position:0% is a system for enhancing the privacy 00:07:17.919 --> 00:07:20.550 align:start position:0% is a system for enhancing the privacy properties<00:07:18.460> of<00:07:18.729> the<00:07:19.120> online<00:07:19.510> users<00:07:19.870> the<00:07:20.530> most 00:07:20.550 --> 00:07:20.560 align:start position:0% properties of the online users the most 00:07:20.560 --> 00:07:25.050 align:start position:0% properties of the online users the most basic<00:07:22.530> component<00:07:23.530> of<00:07:23.650> the<00:07:23.890> system<00:07:24.490> which<00:07:24.850> we 00:07:25.050 --> 00:07:25.060 align:start position:0% basic component of the system which we 00:07:25.060 --> 00:07:27.150 align:start position:0% basic component of the system which we want<00:07:25.240> to<00:07:25.360> run<00:07:25.720> online<00:07:25.960> is<00:07:26.380> the<00:07:26.530> network<00:07:26.979> layer 00:07:27.150 --> 00:07:27.160 align:start position:0% want to run online is the network layer 00:07:27.160 --> 00:07:29.219 align:start position:0% want to run online is the network layer security<00:07:27.880> and<00:07:28.389> when<00:07:28.570> we're<00:07:28.750> thinking<00:07:28.960> about 00:07:29.219 --> 00:07:29.229 align:start position:0% security and when we're thinking about 00:07:29.229 --> 00:07:32.219 align:start position:0% security and when we're thinking about the<00:07:29.440> network<00:07:29.830> layer<00:07:30.010> security<00:07:30.479> one<00:07:31.479> basic 00:07:32.219 --> 00:07:32.229 align:start position:0% the network layer security one basic 00:07:32.229 --> 00:07:33.779 align:start position:0% the network layer security one basic thing<00:07:32.260> which<00:07:32.620> were<00:07:32.800> thinking<00:07:33.160> about<00:07:33.400> is<00:07:33.669> the 00:07:33.779 --> 00:07:33.789 align:start position:0% thing which were thinking about is the 00:07:33.789 --> 00:07:36.810 align:start position:0% thing which were thinking about is the anonymity<00:07:34.360> so<00:07:34.750> what<00:07:34.960> is<00:07:35.139> anonymity<00:07:35.860> anonymity 00:07:36.810 --> 00:07:36.820 align:start position:0% anonymity so what is anonymity anonymity 00:07:36.820 --> 00:07:38.969 align:start position:0% anonymity so what is anonymity anonymity in<00:07:37.240> general<00:07:37.570> is<00:07:37.720> the<00:07:37.840> property<00:07:38.500> which<00:07:38.710> allows 00:07:38.969 --> 00:07:38.979 align:start position:0% in general is the property which allows 00:07:38.979 --> 00:07:41.700 align:start position:0% in general is the property which allows us<00:07:39.310> to<00:07:39.520> remain<00:07:39.789> indistinguishable<00:07:40.710> among 00:07:41.700 --> 00:07:41.710 align:start position:0% us to remain indistinguishable among 00:07:41.710 --> 00:07:44.279 align:start position:0% us to remain indistinguishable among other<00:07:42.070> people<00:07:42.639> performing<00:07:43.120> smart<00:07:43.510> actions<00:07:44.110> or 00:07:44.279 --> 00:07:44.289 align:start position:0% other people performing smart actions or 00:07:44.289 --> 00:07:44.600 align:start position:0% other people performing smart actions or of 00:07:44.600 --> 00:07:44.610 align:start position:0% of 00:07:44.610 --> 00:07:46.790 align:start position:0% of patience<00:07:44.969> and<00:07:45.120> in<00:07:45.659> the<00:07:45.750> online<00:07:45.960> world<00:07:46.169> we 00:07:46.790 --> 00:07:46.800 align:start position:0% patience and in the online world we 00:07:46.800 --> 00:07:48.350 align:start position:0% patience and in the online world we gonna<00:07:47.099> talk<00:07:47.280> about<00:07:47.340> anonymous<00:07:48.120> communication 00:07:48.350 --> 00:07:48.360 align:start position:0% gonna talk about anonymous communication 00:07:48.360 --> 00:07:51.709 align:start position:0% gonna talk about anonymous communication at<00:07:49.229> the<00:07:49.409> network<00:07:49.800> layer<00:07:50.210> so<00:07:51.210> we<00:07:51.330> would<00:07:51.509> like<00:07:51.689> to 00:07:51.709 --> 00:07:51.719 align:start position:0% at the network layer so we would like to 00:07:51.719 --> 00:07:53.809 align:start position:0% at the network layer so we would like to hide<00:07:52.199> the<00:07:52.379> fact<00:07:52.620> who<00:07:53.039> is<00:07:53.159> communicating 00:07:53.809 --> 00:07:53.819 align:start position:0% hide the fact who is communicating 00:07:53.819 --> 00:07:55.610 align:start position:0% hide the fact who is communicating before<00:07:54.240> or<00:07:54.419> who<00:07:54.629> is<00:07:54.689> exchanging<00:07:55.319> information 00:07:55.610 --> 00:07:55.620 align:start position:0% before or who is exchanging information 00:07:55.620 --> 00:08:00.290 align:start position:0% before or who is exchanging information with<00:07:56.129> home<00:07:56.750> and<00:07:58.009> the<00:07:59.009> witness<00:07:59.550> anonymity<00:08:00.030> is 00:08:00.290 --> 00:08:00.300 align:start position:0% with home and the witness anonymity is 00:08:00.300 --> 00:08:02.510 align:start position:0% with home and the witness anonymity is important<00:08:00.870> so<00:08:01.139> if<00:08:01.530> you're<00:08:01.740> gonna<00:08:01.919> think<00:08:02.250> about 00:08:02.510 --> 00:08:02.520 align:start position:0% important so if you're gonna think about 00:08:02.520 --> 00:08:05.959 align:start position:0% important so if you're gonna think about network<00:08:03.240> layer<00:08:03.449> security<00:08:04.460> you<00:08:05.460> have<00:08:05.610> to<00:08:05.759> think 00:08:05.959 --> 00:08:05.969 align:start position:0% network layer security you have to think 00:08:05.969 --> 00:08:07.939 align:start position:0% network layer security you have to think about<00:08:06.090> the<00:08:06.330> metadata<00:08:06.870> so<00:08:07.349> when<00:08:07.500> the<00:08:07.590> internet 00:08:07.939 --> 00:08:07.949 align:start position:0% about the metadata so when the internet 00:08:07.949 --> 00:08:10.309 align:start position:0% about the metadata so when the internet was<00:08:08.099> first<00:08:08.400> introduced<00:08:08.969> in<00:08:09.300> DARPA<00:08:09.840> it<00:08:10.080> was 00:08:10.309 --> 00:08:10.319 align:start position:0% was first introduced in DARPA it was 00:08:10.319 --> 00:08:13.040 align:start position:0% was first introduced in DARPA it was developed<00:08:10.979> as<00:08:11.159> a<00:08:11.189> small<00:08:12.030> side<00:08:12.360> project 00:08:13.040 --> 00:08:13.050 align:start position:0% developed as a small side project 00:08:13.050 --> 00:08:16.040 align:start position:0% developed as a small side project focused<00:08:13.560> on<00:08:13.650> fast<00:08:14.280> packet<00:08:14.759> switching<00:08:15.270> and<00:08:15.509> it 00:08:16.040 --> 00:08:16.050 align:start position:0% focused on fast packet switching and it 00:08:16.050 --> 00:08:18.080 align:start position:0% focused on fast packet switching and it was<00:08:16.199> intended<00:08:16.590> to<00:08:16.830> be<00:08:16.979> used<00:08:17.279> for<00:08:17.430> casual 00:08:18.080 --> 00:08:18.090 align:start position:0% was intended to be used for casual 00:08:18.090 --> 00:08:21.559 align:start position:0% was intended to be used for casual communication<00:08:18.870> not<00:08:19.650> for<00:08:20.009> an<00:08:20.340> exchange<00:08:21.300> of 00:08:21.559 --> 00:08:21.569 align:start position:0% communication not for an exchange of 00:08:21.569 --> 00:08:23.749 align:start position:0% communication not for an exchange of confidential<00:08:22.199> information<00:08:22.370> there<00:08:23.370> further 00:08:23.749 --> 00:08:23.759 align:start position:0% confidential information there further 00:08:23.759 --> 00:08:25.790 align:start position:0% confidential information there further was<00:08:23.879> a<00:08:23.909> very<00:08:24.270> small<00:08:24.599> amount<00:08:24.900> of<00:08:25.169> thought<00:08:25.500> put 00:08:25.790 --> 00:08:25.800 align:start position:0% was a very small amount of thought put 00:08:25.800 --> 00:08:27.529 align:start position:0% was a very small amount of thought put into<00:08:25.860> securing<00:08:26.699> actually<00:08:27.270> this 00:08:27.529 --> 00:08:27.539 align:start position:0% into securing actually this 00:08:27.539 --> 00:08:30.019 align:start position:0% into securing actually this communication<00:08:28.139> and<00:08:28.650> how<00:08:29.250> it<00:08:29.430> turned<00:08:29.699> out<00:08:29.789> this 00:08:30.019 --> 00:08:30.029 align:start position:0% communication and how it turned out this 00:08:30.029 --> 00:08:32.120 align:start position:0% communication and how it turned out this little<00:08:30.419> project<00:08:30.779> ended<00:08:31.529> up<00:08:31.680> being<00:08:31.919> a 00:08:32.120 --> 00:08:32.130 align:start position:0% little project ended up being a 00:08:32.130 --> 00:08:34.159 align:start position:0% little project ended up being a worldwide<00:08:32.550> project<00:08:33.269> and<00:08:33.510> we<00:08:33.630> all<00:08:33.899> use 00:08:34.159 --> 00:08:34.169 align:start position:0% worldwide project and we all use 00:08:34.169 --> 00:08:36.380 align:start position:0% worldwide project and we all use internet<00:08:34.800> nowadays<00:08:35.039> for<00:08:35.519> everything<00:08:36.149> and 00:08:36.380 --> 00:08:36.390 align:start position:0% internet nowadays for everything and 00:08:36.390 --> 00:08:38.719 align:start position:0% internet nowadays for everything and every<00:08:37.349> online<00:08:37.560> activity<00:08:38.219> which<00:08:38.339> we<00:08:38.490> perform 00:08:38.719 --> 00:08:38.729 align:start position:0% every online activity which we perform 00:08:38.729 --> 00:08:42.050 align:start position:0% every online activity which we perform lives<00:08:39.390> a<00:08:39.630> digital<00:08:40.169> fingerprint<00:08:41.159> what<00:08:41.909> it 00:08:42.050 --> 00:08:42.060 align:start position:0% lives a digital fingerprint what it 00:08:42.060 --> 00:08:43.819 align:start position:0% lives a digital fingerprint what it means<00:08:42.269> that<00:08:42.630> every<00:08:43.050> operation<00:08:43.529> would<00:08:43.709> you 00:08:43.819 --> 00:08:43.829 align:start position:0% means that every operation would you 00:08:43.829 --> 00:08:47.120 align:start position:0% means that every operation would you perform<00:08:45.230> with<00:08:46.230> every<00:08:46.470> operation<00:08:46.890> which<00:08:47.040> you 00:08:47.120 --> 00:08:47.130 align:start position:0% perform with every operation which you 00:08:47.130 --> 00:08:48.920 align:start position:0% perform with every operation which you perform<00:08:47.519> online<00:08:47.910> is<00:08:48.120> associated<00:08:48.630> the 00:08:48.920 --> 00:08:48.930 align:start position:0% perform online is associated the 00:08:48.930 --> 00:08:49.610 align:start position:0% perform online is associated the metadata 00:08:49.610 --> 00:08:49.620 align:start position:0% metadata 00:08:49.620 --> 00:08:51.639 align:start position:0% metadata what<00:08:49.829> is<00:08:50.040> this<00:08:50.190> metadata<00:08:50.760> the<00:08:51.120> best<00:08:51.329> way<00:08:51.600> to 00:08:51.639 --> 00:08:51.649 align:start position:0% what is this metadata the best way to 00:08:51.649 --> 00:08:55.610 align:start position:0% what is this metadata the best way to define<00:08:52.649> metadata<00:08:53.250> is<00:08:53.670> to<00:08:54.269> say<00:08:54.540> that<00:08:55.260> it<00:08:55.470> is 00:08:55.610 --> 00:08:55.620 align:start position:0% define metadata is to say that it is 00:08:55.620 --> 00:08:57.139 align:start position:0% define metadata is to say that it is everything<00:08:56.339> about<00:08:56.490> your<00:08:56.790> communication 00:08:57.139 --> 00:08:57.149 align:start position:0% everything about your communication 00:08:57.149 --> 00:08:59.780 align:start position:0% everything about your communication except<00:08:58.050> the<00:08:58.170> content<00:08:58.620> so<00:08:59.430> this<00:08:59.730> is 00:08:59.780 --> 00:08:59.790 align:start position:0% except the content so this is 00:08:59.790 --> 00:09:02.540 align:start position:0% except the content so this is information<00:09:00.600> for<00:09:00.839> example<00:09:00.930> about<00:09:01.500> who<00:09:02.459> is 00:09:02.540 --> 00:09:02.550 align:start position:0% information for example about who is 00:09:02.550 --> 00:09:05.300 align:start position:0% information for example about who is communicating<00:09:03.209> with<00:09:03.240> whom<00:09:03.630> how<00:09:04.170> often<00:09:04.680> both 00:09:05.300 --> 00:09:05.310 align:start position:0% communicating with whom how often both 00:09:05.310 --> 00:09:08.150 align:start position:0% communicating with whom how often both times<00:09:05.610> of<00:09:05.850> the<00:09:06.000> day<00:09:06.199> what<00:09:07.199> is<00:09:07.230> the<00:09:07.380> dynamic<00:09:07.680> of 00:09:08.150 --> 00:09:08.160 align:start position:0% times of the day what is the dynamic of 00:09:08.160 --> 00:09:09.710 align:start position:0% times of the day what is the dynamic of the<00:09:08.370> group<00:09:08.519> what<00:09:08.850> is<00:09:08.940> the<00:09:09.089> sequence<00:09:09.630> of 00:09:09.710 --> 00:09:09.720 align:start position:0% the group what is the sequence of 00:09:09.720 --> 00:09:12.650 align:start position:0% the group what is the sequence of communication<00:09:10.680> from<00:09:11.339> which<00:09:11.579> location<00:09:12.360> you're 00:09:12.650 --> 00:09:12.660 align:start position:0% communication from which location you're 00:09:12.660 --> 00:09:15.050 align:start position:0% communication from which location you're communicating<00:09:13.019> with<00:09:13.500> people<00:09:13.860> and<00:09:14.250> so<00:09:14.760> on<00:09:14.790> and 00:09:15.050 --> 00:09:15.060 align:start position:0% communicating with people and so on and 00:09:15.060 --> 00:09:17.090 align:start position:0% communicating with people and so on and so<00:09:15.240> on<00:09:15.269> and<00:09:15.870> when<00:09:16.079> the<00:09:16.199> priests<00:09:16.470> program<00:09:16.920> was 00:09:17.090 --> 00:09:17.100 align:start position:0% so on and when the priests program was 00:09:17.100 --> 00:09:20.660 align:start position:0% so on and when the priests program was revealed<00:09:17.519> the<00:09:18.329> NSA<00:09:18.750> was<00:09:18.959> saying<00:09:19.380> that<00:09:19.680> no<00:09:20.339> big 00:09:20.660 --> 00:09:20.670 align:start position:0% revealed the NSA was saying that no big 00:09:20.670 --> 00:09:24.019 align:start position:0% revealed the NSA was saying that no big deal<00:09:20.970> that<00:09:21.000> here<00:09:22.130> were<00:09:23.130> trying<00:09:23.550> to<00:09:23.699> record 00:09:24.019 --> 00:09:24.029 align:start position:0% deal that here were trying to record 00:09:24.029 --> 00:09:25.430 align:start position:0% deal that here were trying to record your<00:09:24.149> communication<00:09:24.720> because<00:09:24.990> we<00:09:25.110> are<00:09:25.199> not 00:09:25.430 --> 00:09:25.440 align:start position:0% your communication because we are not 00:09:25.440 --> 00:09:26.800 align:start position:0% your communication because we are not reading<00:09:25.800> your<00:09:25.949> content<00:09:26.250> we're 00:09:26.800 --> 00:09:26.810 align:start position:0% reading your content we're 00:09:26.810 --> 00:09:29.769 align:start position:0% reading your content we're the<00:09:27.410> metadata<00:09:27.890> but<00:09:28.670> it<00:09:28.820> turns<00:09:29.060> out<00:09:29.300> that<00:09:29.540> this 00:09:29.769 --> 00:09:29.779 align:start position:0% the metadata but it turns out that this 00:09:29.779 --> 00:09:32.560 align:start position:0% the metadata but it turns out that this metadata<00:09:30.350> carries<00:09:31.010> a<00:09:31.220> lot<00:09:31.850> of<00:09:32.029> sensitive 00:09:32.560 --> 00:09:32.570 align:start position:0% metadata carries a lot of sensitive 00:09:32.570 --> 00:09:35.440 align:start position:0% metadata carries a lot of sensitive information<00:09:32.930> about<00:09:33.740> the<00:09:33.950> users<00:09:34.400> which<00:09:35.000> very 00:09:35.440 --> 00:09:35.450 align:start position:0% information about the users which very 00:09:35.450 --> 00:09:37.840 align:start position:0% information about the users which very often<00:09:35.840> is<00:09:36.140> as<00:09:36.470> revealing<00:09:36.950> as<00:09:37.100> the<00:09:37.430> content 00:09:37.840 --> 00:09:37.850 align:start position:0% often is as revealing as the content 00:09:37.850 --> 00:09:40.660 align:start position:0% often is as revealing as the content itself<00:09:38.240> you<00:09:38.570> don't<00:09:38.810> actually<00:09:39.320> try<00:09:40.160> to<00:09:40.220> prove 00:09:40.660 --> 00:09:40.670 align:start position:0% itself you don't actually try to prove 00:09:40.670 --> 00:09:42.670 align:start position:0% itself you don't actually try to prove the<00:09:40.940> messages<00:09:41.480> and<00:09:41.750> look<00:09:41.900> if<00:09:42.020> it<00:09:42.170> wanted<00:09:42.620> to 00:09:42.670 --> 00:09:42.680 align:start position:0% the messages and look if it wanted to 00:09:42.680 --> 00:09:45.040 align:start position:0% the messages and look if it wanted to infer<00:09:43.279> a<00:09:43.430> lot<00:09:43.670> of<00:09:43.820> information<00:09:44.480> about<00:09:44.779> the 00:09:45.040 --> 00:09:45.050 align:start position:0% infer a lot of information about the 00:09:45.050 --> 00:09:47.950 align:start position:0% infer a lot of information about the users<00:09:45.470> which<00:09:46.040> in<00:09:46.250> result<00:09:46.670> allows<00:09:47.480> you<00:09:47.720> to 00:09:47.950 --> 00:09:47.960 align:start position:0% users which in result allows you to 00:09:47.960 --> 00:09:50.710 align:start position:0% users which in result allows you to infer<00:09:48.800> what<00:09:49.130> are<00:09:49.430> the<00:09:49.580> relationship<00:09:50.390> whether 00:09:50.710 --> 00:09:50.720 align:start position:0% infer what are the relationship whether 00:09:50.720 --> 00:09:53.170 align:start position:0% infer what are the relationship whether they're<00:09:50.990> political<00:09:51.710> or<00:09:51.920> sexual<00:09:52.400> preferences 00:09:53.170 --> 00:09:53.180 align:start position:0% they're political or sexual preferences 00:09:53.180 --> 00:09:57.160 align:start position:0% they're political or sexual preferences religions<00:09:53.779> and<00:09:54.020> so<00:09:54.260> on<00:09:54.380> and<00:09:54.620> so<00:09:54.770> on<00:09:54.800> so<00:09:56.170> let's 00:09:57.160 --> 00:09:57.170 align:start position:0% religions and so on and so on so let's 00:09:57.170 --> 00:09:59.470 align:start position:0% religions and so on and so on so let's look<00:09:57.320> at<00:09:57.500> a<00:09:57.529> couple<00:09:57.740> of<00:09:57.950> examples<00:09:58.130> of<00:09:58.760> privacy 00:09:59.470 --> 00:09:59.480 align:start position:0% look at a couple of examples of privacy 00:09:59.480 --> 00:10:01.180 align:start position:0% look at a couple of examples of privacy enhancing<00:09:59.570> technologies<00:09:59.960> which<00:10:00.770> are<00:10:00.920> very 00:10:01.180 --> 00:10:01.190 align:start position:0% enhancing technologies which are very 00:10:01.190 --> 00:10:03.670 align:start position:0% enhancing technologies which are very popular<00:10:01.610> nowadays<00:10:01.820> I'm<00:10:02.300> pretty<00:10:02.570> sure<00:10:02.720> you<00:10:02.930> saw 00:10:03.670 --> 00:10:03.680 align:start position:0% popular nowadays I'm pretty sure you saw 00:10:03.680 --> 00:10:06.550 align:start position:0% popular nowadays I'm pretty sure you saw or<00:10:03.950> heard<00:10:03.980> at<00:10:04.400> least<00:10:04.610> about<00:10:04.940> one<00:10:05.210> of<00:10:05.390> them<00:10:05.570> and 00:10:06.550 --> 00:10:06.560 align:start position:0% or heard at least about one of them and 00:10:06.560 --> 00:10:08.680 align:start position:0% or heard at least about one of them and let's<00:10:06.800> think<00:10:07.040> whether<00:10:07.550> they<00:10:07.940> offer<00:10:08.360> us 00:10:08.680 --> 00:10:08.690 align:start position:0% let's think whether they offer us 00:10:08.690 --> 00:10:11.079 align:start position:0% let's think whether they offer us anonymity<00:10:09.200> at<00:10:09.410> the<00:10:09.529> network<00:10:09.920> level<00:10:10.160> or<00:10:10.760> not 00:10:11.079 --> 00:10:11.089 align:start position:0% anonymity at the network level or not 00:10:11.089 --> 00:10:13.150 align:start position:0% anonymity at the network level or not and<00:10:11.480> how<00:10:11.779> good<00:10:11.960> is<00:10:12.110> this<00:10:12.260> anonymity<00:10:12.860> so<00:10:13.010> the 00:10:13.150 --> 00:10:13.160 align:start position:0% and how good is this anonymity so the 00:10:13.160 --> 00:10:15.880 align:start position:0% and how good is this anonymity so the first<00:10:13.400> example<00:10:13.580> is<00:10:14.210> as<00:10:14.510> to<00:10:14.750> an<00:10:14.810> encryption<00:10:15.200> I'm 00:10:15.880 --> 00:10:15.890 align:start position:0% first example is as to an encryption I'm 00:10:15.890 --> 00:10:17.890 align:start position:0% first example is as to an encryption I'm quite<00:10:16.220> sure<00:10:16.460> that<00:10:16.670> to<00:10:16.850> you<00:10:16.970> either<00:10:17.210> use<00:10:17.600> I've 00:10:17.890 --> 00:10:17.900 align:start position:0% quite sure that to you either use I've 00:10:17.900 --> 00:10:21.010 align:start position:0% quite sure that to you either use I've heard<00:10:18.170> about<00:10:18.500> PGP<00:10:19.130> for<00:10:19.339> emails<00:10:19.670> or<00:10:20.029> add<00:10:20.540> to<00:10:20.930> an 00:10:21.010 --> 00:10:21.020 align:start position:0% heard about PGP for emails or add to an 00:10:21.020 --> 00:10:23.230 align:start position:0% heard about PGP for emails or add to an encrypted<00:10:21.440> instant<00:10:21.860> messaging<00:10:22.610> applications 00:10:23.230 --> 00:10:23.240 align:start position:0% encrypted instant messaging applications 00:10:23.240 --> 00:10:26.500 align:start position:0% encrypted instant messaging applications by<00:10:23.480> whatsapp<00:10:24.140> signal<00:10:24.710> telegram<00:10:25.310> and<00:10:25.520> so<00:10:25.760> on<00:10:25.910> so 00:10:26.500 --> 00:10:26.510 align:start position:0% by whatsapp signal telegram and so on so 00:10:26.510 --> 00:10:28.390 align:start position:0% by whatsapp signal telegram and so on so this<00:10:26.690> is<00:10:26.900> a<00:10:26.930> very<00:10:27.290> good<00:10:27.380> example<00:10:28.010> of<00:10:28.190> a 00:10:28.390 --> 00:10:28.400 align:start position:0% this is a very good example of a 00:10:28.400 --> 00:10:30.490 align:start position:0% this is a very good example of a progressing<00:10:28.910> and<00:10:29.000> hansung<00:10:29.360> technology<00:10:30.020> which 00:10:30.490 --> 00:10:30.500 align:start position:0% progressing and hansung technology which 00:10:30.500 --> 00:10:33.130 align:start position:0% progressing and hansung technology which allows<00:10:30.710> you<00:10:31.130> to<00:10:31.190> have<00:10:31.790> confidentiality<00:10:32.510> so 00:10:33.130 --> 00:10:33.140 align:start position:0% allows you to have confidentiality so 00:10:33.140 --> 00:10:35.020 align:start position:0% allows you to have confidentiality so which<00:10:33.380> allows<00:10:33.770> you<00:10:33.920> to<00:10:33.950> hide<00:10:34.250> the<00:10:34.370> content<00:10:34.910> of 00:10:35.020 --> 00:10:35.030 align:start position:0% which allows you to hide the content of 00:10:35.030 --> 00:10:37.270 align:start position:0% which allows you to hide the content of your<00:10:35.060> communication<00:10:35.960> but<00:10:36.650> it<00:10:36.830> doesn't 00:10:37.270 --> 00:10:37.280 align:start position:0% your communication but it doesn't 00:10:37.280 --> 00:10:39.550 align:start position:0% your communication but it doesn't protect<00:10:37.640> the<00:10:37.940> network<00:10:38.420> player<00:10:38.690> metadata 00:10:39.550 --> 00:10:39.560 align:start position:0% protect the network player metadata 00:10:39.560 --> 00:10:41.320 align:start position:0% protect the network player metadata associated<00:10:39.920> with<00:10:40.310> your<00:10:40.580> communication<00:10:40.940> so 00:10:41.320 --> 00:10:41.330 align:start position:0% associated with your communication so 00:10:41.330 --> 00:10:43.150 align:start position:0% associated with your communication so even<00:10:41.570> though<00:10:41.720> you're<00:10:41.870> hiding<00:10:42.350> your<00:10:42.740> actual 00:10:43.150 --> 00:10:43.160 align:start position:0% even though you're hiding your actual 00:10:43.160 --> 00:10:45.790 align:start position:0% even though you're hiding your actual messages<00:10:43.760> you're<00:10:44.210> not<00:10:44.480> hiding<00:10:44.750> the<00:10:44.990> fact<00:10:45.320> with 00:10:45.790 --> 00:10:45.800 align:start position:0% messages you're not hiding the fact with 00:10:45.800 --> 00:10:47.610 align:start position:0% messages you're not hiding the fact with whom<00:10:46.070> and<00:10:46.250> however<00:10:46.460> you're<00:10:46.940> communicating 00:10:47.610 --> 00:10:47.620 align:start position:0% whom and however you're communicating 00:10:47.620 --> 00:10:50.500 align:start position:0% whom and however you're communicating another<00:10:48.620> example<00:10:49.280> are<00:10:49.580> the<00:10:49.820> privacy 00:10:50.500 --> 00:10:50.510 align:start position:0% another example are the privacy 00:10:50.510 --> 00:10:53.050 align:start position:0% another example are the privacy enhancing<00:10:50.950> crypto<00:10:51.950> pies<00:10:52.160> so<00:10:52.700> I<00:10:52.730> think<00:10:52.790> I<00:10:53.000> don't 00:10:53.050 --> 00:10:53.060 align:start position:0% enhancing crypto pies so I think I don't 00:10:53.060 --> 00:10:55.600 align:start position:0% enhancing crypto pies so I think I don't have<00:10:53.450> to<00:10:53.720> convince<00:10:54.050> anyone<00:10:54.589> that<00:10:54.710> bitcoin<00:10:55.430> is 00:10:55.600 --> 00:10:55.610 align:start position:0% have to convince anyone that bitcoin is 00:10:55.610 --> 00:10:57.880 align:start position:0% have to convince anyone that bitcoin is not<00:10:55.640> anonymous<00:10:56.210> but<00:10:56.780> let's<00:10:57.050> look<00:10:57.320> at<00:10:57.530> for 00:10:57.880 --> 00:10:57.890 align:start position:0% not anonymous but let's look at for 00:10:57.890 --> 00:10:59.950 align:start position:0% not anonymous but let's look at for privacy<00:10:58.700> friendly<00:10:59.150> coins<00:10:59.390> like<00:10:59.660> for<00:10:59.870> example 00:10:59.950 --> 00:10:59.960 align:start position:0% privacy friendly coins like for example 00:10:59.960 --> 00:11:03.520 align:start position:0% privacy friendly coins like for example zip<00:11:00.560> hash<00:11:00.770> so<00:11:01.460> seepage<00:11:01.880> is<00:11:02.150> a<00:11:02.350> very<00:11:03.350> nice 00:11:03.520 --> 00:11:03.530 align:start position:0% zip hash so seepage is a very nice 00:11:03.530 --> 00:11:05.560 align:start position:0% zip hash so seepage is a very nice promise<00:11:03.980> privacy<00:11:04.520> supporting<00:11:05.000> point<00:11:05.240> because 00:11:05.560 --> 00:11:05.570 align:start position:0% promise privacy supporting point because 00:11:05.570 --> 00:11:08.020 align:start position:0% promise privacy supporting point because it<00:11:05.750> offers<00:11:06.140> a<00:11:06.380> good<00:11:06.650> privacy<00:11:07.130> properties<00:11:07.790> on 00:11:08.020 --> 00:11:08.030 align:start position:0% it offers a good privacy properties on 00:11:08.030 --> 00:11:11.310 align:start position:0% it offers a good privacy properties on chain<00:11:08.420> thanks<00:11:08.780> choosing<00:11:09.170> the<00:11:09.380> zero<00:11:10.190> knowledge 00:11:11.310 --> 00:11:11.320 align:start position:0% chain thanks choosing the zero knowledge 00:11:11.320 --> 00:11:14.410 align:start position:0% chain thanks choosing the zero knowledge technology<00:11:12.320> but<00:11:12.890> it<00:11:13.130> does<00:11:13.339> not<00:11:13.520> protect<00:11:13.850> the 00:11:14.410 --> 00:11:14.420 align:start position:0% technology but it does not protect the 00:11:14.420 --> 00:11:17.740 align:start position:0% technology but it does not protect the network<00:11:14.839> layer<00:11:15.320> so<00:11:16.040> in<00:11:16.220> result<00:11:16.670> the<00:11:17.150> adversary 00:11:17.740 --> 00:11:17.750 align:start position:0% network layer so in result the adversary 00:11:17.750 --> 00:11:20.380 align:start position:0% network layer so in result the adversary who<00:11:17.900> has<00:11:18.080> access<00:11:18.650> to<00:11:18.680> the<00:11:19.160> network<00:11:19.550> layer<00:11:19.730> is 00:11:20.380 --> 00:11:20.390 align:start position:0% who has access to the network layer is 00:11:20.390 --> 00:11:23.710 align:start position:0% who has access to the network layer is able<00:11:20.990> to<00:11:21.140> correlate<00:11:21.560> users<00:11:22.160> transacting<00:11:22.940> just 00:11:23.710 --> 00:11:23.720 align:start position:0% able to correlate users transacting just 00:11:23.720 --> 00:11:24.800 align:start position:0% able to correlate users transacting just looking<00:11:24.050> at<00:11:24.140> their<00:11:24.320> net 00:11:24.800 --> 00:11:24.810 align:start position:0% looking at their net 00:11:24.810 --> 00:11:28.850 align:start position:0% looking at their net addresses<00:11:25.320> and<00:11:26.310> the<00:11:26.490> example<00:11:27.360> is<00:11:27.480> VPN<00:11:27.990> also 00:11:28.850 --> 00:11:28.860 align:start position:0% addresses and the example is VPN also 00:11:28.860 --> 00:11:30.530 align:start position:0% addresses and the example is VPN also the<00:11:29.010> threshold<00:11:29.430> fighters<00:11:29.790> network<00:11:30.150> so<00:11:30.330> here 00:11:30.530 --> 00:11:30.540 align:start position:0% the threshold fighters network so here 00:11:30.540 --> 00:11:31.820 align:start position:0% the threshold fighters network so here we<00:11:30.660> are<00:11:30.690> getting<00:11:30.870> a<00:11:31.080> little<00:11:31.200> bit<00:11:31.380> closer 00:11:31.820 --> 00:11:31.830 align:start position:0% we are getting a little bit closer 00:11:31.830 --> 00:11:33.920 align:start position:0% we are getting a little bit closer towards<00:11:32.310> securing<00:11:32.790> the<00:11:32.910> network<00:11:33.330> layer<00:11:33.570> of 00:11:33.920 --> 00:11:33.930 align:start position:0% towards securing the network layer of 00:11:33.930 --> 00:11:36.650 align:start position:0% towards securing the network layer of communication<00:11:34.560> because<00:11:34.860> actually<00:11:35.520> VPNs 00:11:36.650 --> 00:11:36.660 align:start position:0% communication because actually VPNs 00:11:36.660 --> 00:11:39.380 align:start position:0% communication because actually VPNs of<00:11:36.780> a<00:11:37.460> some<00:11:38.460> type<00:11:38.640> of<00:11:38.790> network<00:11:39.210> level 00:11:39.380 --> 00:11:39.390 align:start position:0% of a some type of network level 00:11:39.390 --> 00:11:41.660 align:start position:0% of a some type of network level protection<00:11:39.720> by<00:11:40.410> a<00:11:40.440> frank<00:11:40.950> and<00:11:41.190> encrypted 00:11:41.660 --> 00:11:41.670 align:start position:0% protection by a frank and encrypted 00:11:41.670 --> 00:11:43.790 align:start position:0% protection by a frank and encrypted channel<00:11:42.120> between<00:11:42.300> the<00:11:42.510> user<00:11:42.840> and<00:11:43.020> the<00:11:43.290> VPN 00:11:43.790 --> 00:11:43.800 align:start position:0% channel between the user and the VPN 00:11:43.800 --> 00:11:46.790 align:start position:0% channel between the user and the VPN provider<00:11:44.250> which<00:11:44.580> acts<00:11:44.940> as<00:11:45.270> a<00:11:45.300> proxy<00:11:45.600> but<00:11:46.590> what 00:11:46.790 --> 00:11:46.800 align:start position:0% provider which acts as a proxy but what 00:11:46.800 --> 00:11:49.280 align:start position:0% provider which acts as a proxy but what is<00:11:46.920> the<00:11:47.160> limitation<00:11:47.880> of<00:11:48.000> the<00:11:48.150> VPN<00:11:48.480> or<00:11:48.750> VPNs<00:11:49.170> are 00:11:49.280 --> 00:11:49.290 align:start position:0% is the limitation of the VPN or VPNs are 00:11:49.290 --> 00:11:53.060 align:start position:0% is the limitation of the VPN or VPNs are centralized<00:11:49.950> which<00:11:50.280> means<00:11:50.520> that<00:11:51.740> simply<00:11:52.740> you 00:11:53.060 --> 00:11:53.070 align:start position:0% centralized which means that simply you 00:11:53.070 --> 00:11:57.470 align:start position:0% centralized which means that simply you have<00:11:54.000> to<00:11:54.150> trust<00:11:54.420> the<00:11:54.630> PPM<00:11:55.050> provider<00:11:55.560> that<00:11:56.520> he 00:11:57.470 --> 00:11:57.480 align:start position:0% have to trust the PPM provider that he 00:11:57.480 --> 00:11:59.420 align:start position:0% have to trust the PPM provider that he will<00:11:57.600> be<00:11:57.750> behaving<00:11:58.080> honestly<00:11:58.800> because<00:11:59.100> he<00:11:59.370> is 00:11:59.420 --> 00:11:59.430 align:start position:0% will be behaving honestly because he is 00:11:59.430 --> 00:12:01.670 align:start position:0% will be behaving honestly because he is the<00:11:59.640> one<00:11:59.760> who<00:12:00.090> sees<00:12:00.300> your<00:12:00.840> traffic<00:12:01.290> between 00:12:01.670 --> 00:12:01.680 align:start position:0% the one who sees your traffic between 00:12:01.680 --> 00:12:04.610 align:start position:0% the one who sees your traffic between the<00:12:01.860> user<00:12:02.160> and<00:12:02.370> the<00:12:02.580> public<00:12:03.390> Internet<00:12:03.960> so<00:12:04.470> in 00:12:04.610 --> 00:12:04.620 align:start position:0% the user and the public Internet so in 00:12:04.620 --> 00:12:07.010 align:start position:0% the user and the public Internet so in results<00:12:05.190> you<00:12:05.670> have<00:12:05.850> to<00:12:05.880> trust<00:12:06.270> that<00:12:06.420> the<00:12:06.570> VPN 00:12:07.010 --> 00:12:07.020 align:start position:0% results you have to trust that the VPN 00:12:07.020 --> 00:12:09.500 align:start position:0% results you have to trust that the VPN is<00:12:07.260> not<00:12:07.470> malicious<00:12:08.040> or<00:12:08.280> it<00:12:08.730> does<00:12:08.880> not<00:12:09.090> keep<00:12:09.300> any 00:12:09.500 --> 00:12:09.510 align:start position:0% is not malicious or it does not keep any 00:12:09.510 --> 00:12:11.840 align:start position:0% is not malicious or it does not keep any logs<00:12:09.810> about<00:12:09.990> your<00:12:10.530> online<00:12:10.860> activities<00:12:11.640> and 00:12:11.840 --> 00:12:11.850 align:start position:0% logs about your online activities and 00:12:11.850 --> 00:12:14.170 align:start position:0% logs about your online activities and does<00:12:12.000> not<00:12:12.180> share<00:12:12.450> with<00:12:12.660> anyone 00:12:14.170 --> 00:12:14.180 align:start position:0% does not share with anyone 00:12:14.180 --> 00:12:17.150 align:start position:0% does not share with anyone so<00:12:15.180> the<00:12:15.660> research<00:12:15.990> in<00:12:16.230> anonymous 00:12:17.150 --> 00:12:17.160 align:start position:0% so the research in anonymous 00:12:17.160 --> 00:12:19.310 align:start position:0% so the research in anonymous communication<00:12:17.820> networks<00:12:18.210> is<00:12:18.420> definitely<00:12:19.140> not 00:12:19.310 --> 00:12:19.320 align:start position:0% communication networks is definitely not 00:12:19.320 --> 00:12:21.410 align:start position:0% communication networks is definitely not known<00:12:19.620> already<00:12:20.220> in<00:12:20.460> the<00:12:20.550> early<00:12:20.820> 80s 00:12:21.410 --> 00:12:21.420 align:start position:0% known already in the early 80s 00:12:21.420 --> 00:12:23.360 align:start position:0% known already in the early 80s David<00:12:21.870> champion<00:12:22.380> ear<00:12:22.590> the<00:12:22.770> idea<00:12:23.040> of<00:12:23.220> the 00:12:23.360 --> 00:12:23.370 align:start position:0% David champion ear the idea of the 00:12:23.370 --> 00:12:26.270 align:start position:0% David champion ear the idea of the first-ever<00:12:24.150> anonymous<00:12:24.840> Network<00:12:25.470> called<00:12:26.130> the 00:12:26.270 --> 00:12:26.280 align:start position:0% first-ever anonymous Network called the 00:12:26.280 --> 00:12:28.610 align:start position:0% first-ever anonymous Network called the mixed<00:12:26.520> Network<00:12:27.060> so<00:12:27.810> I<00:12:27.870> will<00:12:27.990> try<00:12:28.200> to<00:12:28.230> give<00:12:28.590> like 00:12:28.610 --> 00:12:28.620 align:start position:0% mixed Network so I will try to give like 00:12:28.620 --> 00:12:31.430 align:start position:0% mixed Network so I will try to give like a<00:12:28.800> very<00:12:29.130> brief<00:12:29.730> crash<00:12:30.210> course<00:12:30.540> on<00:12:30.840> what<00:12:31.080> mixed 00:12:31.430 --> 00:12:31.440 align:start position:0% a very brief crash course on what mixed 00:12:31.440 --> 00:12:34.670 align:start position:0% a very brief crash course on what mixed networks<00:12:31.800> are<00:12:32.070> so<00:12:32.850> let's<00:12:33.030> start<00:12:33.300> first<00:12:34.170> what 00:12:34.670 --> 00:12:34.680 align:start position:0% networks are so let's start first what 00:12:34.680 --> 00:12:37.820 align:start position:0% networks are so let's start first what is<00:12:34.800> a<00:12:34.830> mix<00:12:35.220> mix<00:12:35.760> is<00:12:36.030> simply<00:12:36.450> a<00:12:36.780> router<00:12:37.320> and<00:12:37.710> that 00:12:37.820 --> 00:12:37.830 align:start position:0% is a mix mix is simply a router and that 00:12:37.830 --> 00:12:40.460 align:start position:0% is a mix mix is simply a router and that will<00:12:38.010> project<00:12:38.550> for<00:12:39.150> any<00:12:39.450> type<00:12:39.780> of<00:12:39.810> Internet 00:12:40.460 --> 00:12:40.470 align:start position:0% will project for any type of Internet 00:12:40.470 --> 00:12:42.380 align:start position:0% will project for any type of Internet traffic<00:12:40.590> which<00:12:41.010> would<00:12:41.430> like<00:12:41.610> to<00:12:41.790> use<00:12:41.940> and<00:12:42.210> it 00:12:42.380 --> 00:12:42.390 align:start position:0% traffic which would like to use and it 00:12:42.390 --> 00:12:45.020 align:start position:0% traffic which would like to use and it makes<00:12:42.600> network<00:12:43.020> is<00:12:43.200> just<00:12:43.470> a<00:12:43.650> set<00:12:43.920> of<00:12:44.220> such<00:12:44.550> mix 00:12:45.020 --> 00:12:45.030 align:start position:0% makes network is just a set of such mix 00:12:45.030 --> 00:12:47.210 align:start position:0% makes network is just a set of such mix now<00:12:45.240> and<00:12:45.720> don't<00:12:45.930> be<00:12:46.080> particularly<00:12:46.470> face<00:12:46.950> that 00:12:47.210 --> 00:12:47.220 align:start position:0% now and don't be particularly face that 00:12:47.220 --> 00:12:49.520 align:start position:0% now and don't be particularly face that I'm<00:12:47.340> showing<00:12:47.580> the<00:12:47.850> mix<00:12:48.210> ontology<00:12:48.570> just<00:12:49.380> a 00:12:49.520 --> 00:12:49.530 align:start position:0% I'm showing the mix ontology just a 00:12:49.530 --> 00:12:52.850 align:start position:0% I'm showing the mix ontology just a single<00:12:49.950> sequence<00:12:50.960> in<00:12:51.960> general<00:12:52.380> you<00:12:52.470> can<00:12:52.590> have 00:12:52.850 --> 00:12:52.860 align:start position:0% single sequence in general you can have 00:12:52.860 --> 00:12:55.790 align:start position:0% single sequence in general you can have many<00:12:53.280> topologies<00:12:53.940> of<00:12:54.090> this<00:12:54.270> network<00:12:54.750> but<00:12:55.530> just 00:12:55.790 --> 00:12:55.800 align:start position:0% many topologies of this network but just 00:12:55.800 --> 00:12:57.920 align:start position:0% many topologies of this network but just for<00:12:55.980> cyclic<00:12:56.330> simplification<00:12:57.330> I<00:12:57.420> have<00:12:57.630> just<00:12:57.840> a 00:12:57.920 --> 00:12:57.930 align:start position:0% for cyclic simplification I have just a 00:12:57.930 --> 00:13:02.180 align:start position:0% for cyclic simplification I have just a single<00:12:58.230> path<00:12:59.030> but<00:13:00.030> on<00:13:00.360> top<00:13:00.780> of<00:13:00.930> being<00:13:01.230> just<00:13:01.980> a 00:13:02.180 --> 00:13:02.190 align:start position:0% single path but on top of being just a 00:13:02.190 --> 00:13:05.540 align:start position:0% single path but on top of being just a network<00:13:02.490> router<00:13:03.000> the<00:13:03.840> mixes<00:13:04.470> have<00:13:05.250> some 00:13:05.540 --> 00:13:05.550 align:start position:0% network router the mixes have some 00:13:05.550 --> 00:13:08.330 align:start position:0% network router the mixes have some security<00:13:06.330> properties<00:13:06.900> which<00:13:07.170> allow<00:13:07.590> you<00:13:07.650> to 00:13:08.330 --> 00:13:08.340 align:start position:0% security properties which allow you to 00:13:08.340 --> 00:13:09.790 align:start position:0% security properties which allow you to remain<00:13:08.610> anonymous 00:13:09.790 --> 00:13:09.800 align:start position:0% remain anonymous 00:13:09.800 --> 00:13:12.490 align:start position:0% remain anonymous a<00:13:09.830> player<00:13:10.630> so<00:13:11.630> what<00:13:11.779> are<00:13:11.930> those<00:13:12.050> properties 00:13:12.490 --> 00:13:12.500 align:start position:0% a player so what are those properties 00:13:12.500 --> 00:13:15.480 align:start position:0% a player so what are those properties the<00:13:13.070> first<00:13:13.279> property<00:13:13.910> is<00:13:14.060> that<00:13:14.269> it<00:13:14.690> makes 00:13:15.480 --> 00:13:15.490 align:start position:0% the first property is that it makes 00:13:15.490 --> 00:13:17.500 align:start position:0% the first property is that it makes transforms<00:13:16.490> the<00:13:16.640> received<00:13:17.029> packets 00:13:17.500 --> 00:13:17.510 align:start position:0% transforms the received packets 00:13:17.510 --> 00:13:20.530 align:start position:0% transforms the received packets cryptographically<00:13:18.910> what<00:13:19.910> does<00:13:20.060> it<00:13:20.209> mean<00:13:20.360> that 00:13:20.530 --> 00:13:20.540 align:start position:0% cryptographically what does it mean that 00:13:20.540 --> 00:13:22.680 align:start position:0% cryptographically what does it mean that if<00:13:20.690> Alice<00:13:21.050> wants<00:13:21.320> to<00:13:21.350> send<00:13:21.500> a<00:13:21.769> message<00:13:22.130> to<00:13:22.160> Bob 00:13:22.680 --> 00:13:22.690 align:start position:0% if Alice wants to send a message to Bob 00:13:22.690 --> 00:13:25.930 align:start position:0% if Alice wants to send a message to Bob she<00:13:23.690> gonna<00:13:23.899> and<00:13:24.290> coat<00:13:24.709> her<00:13:25.160> message<00:13:25.670> into<00:13:25.910> a 00:13:25.930 --> 00:13:25.940 align:start position:0% she gonna and coat her message into a 00:13:25.940 --> 00:13:28.810 align:start position:0% she gonna and coat her message into a special<00:13:26.420> cryptographic<00:13:26.750> packet<00:13:27.410> format<00:13:27.920> in 00:13:28.810 --> 00:13:28.820 align:start position:0% special cryptographic packet format in 00:13:28.820 --> 00:13:31.810 align:start position:0% special cryptographic packet format in such<00:13:29.180> a<00:13:29.209> way<00:13:29.510> that<00:13:29.779> each<00:13:30.380> mix<00:13:30.860> on<00:13:31.130> the<00:13:31.310> package 00:13:31.810 --> 00:13:31.820 align:start position:0% such a way that each mix on the package 00:13:31.820 --> 00:13:35.560 align:start position:0% such a way that each mix on the package with<00:13:32.029> Alex<00:13:32.540> Alice<00:13:33.079> and<00:13:33.350> Bob<00:13:33.820> will<00:13:34.820> remove<00:13:35.240> one 00:13:35.560 --> 00:13:35.570 align:start position:0% with Alex Alice and Bob will remove one 00:13:35.570 --> 00:13:37.600 align:start position:0% with Alex Alice and Bob will remove one layer<00:13:35.839> of<00:13:36.500> this<00:13:36.620> cryptographic<00:13:37.130> protection 00:13:37.600 --> 00:13:37.610 align:start position:0% layer of this cryptographic protection 00:13:37.610 --> 00:13:39.759 align:start position:0% layer of this cryptographic protection so<00:13:38.089> if<00:13:38.180> some<00:13:38.450> of<00:13:38.660> you<00:13:38.839> know<00:13:38.870> Onion<00:13:39.529> Routing 00:13:39.759 --> 00:13:39.769 align:start position:0% so if some of you know Onion Routing 00:13:39.769 --> 00:13:41.530 align:start position:0% so if some of you know Onion Routing it's<00:13:40.160> a<00:13:40.250> very<00:13:40.519> similar<00:13:40.790> idea 00:13:41.530 --> 00:13:41.540 align:start position:0% it's a very similar idea 00:13:41.540 --> 00:13:43.600 align:start position:0% it's a very similar idea so<00:13:41.899> we<00:13:42.050> layer<00:13:42.260> and<00:13:42.589> crimp<00:13:42.860> the<00:13:43.010> packets<00:13:43.459> and 00:13:43.600 --> 00:13:43.610 align:start position:0% so we layer and crimp the packets and 00:13:43.610 --> 00:13:45.940 align:start position:0% so we layer and crimp the packets and what<00:13:44.300> this<00:13:44.480> gives<00:13:44.690> us<00:13:44.930> is<00:13:45.140> the<00:13:45.230> property 00:13:45.940 --> 00:13:45.950 align:start position:0% what this gives us is the property 00:13:45.950 --> 00:13:48.490 align:start position:0% what this gives us is the property called<00:13:46.220> bitwise<00:13:46.670> unlink<00:13:47.149> ability<00:13:47.660> this<00:13:48.230> means 00:13:48.490 --> 00:13:48.500 align:start position:0% called bitwise unlink ability this means 00:13:48.500 --> 00:13:50.319 align:start position:0% called bitwise unlink ability this means that<00:13:48.709> if<00:13:48.920> the<00:13:49.040> adversary<00:13:49.310> observes<00:13:50.029> any 00:13:50.319 --> 00:13:50.329 align:start position:0% that if the adversary observes any 00:13:50.329 --> 00:13:53.620 align:start position:0% that if the adversary observes any single<00:13:51.079> mix<00:13:51.560> and<00:13:51.920> he<00:13:52.370> sees<00:13:52.610> packets<00:13:53.000> coming<00:13:53.300> in 00:13:53.620 --> 00:13:53.630 align:start position:0% single mix and he sees packets coming in 00:13:53.630 --> 00:13:56.019 align:start position:0% single mix and he sees packets coming in and<00:13:53.930> packets<00:13:54.500> coming<00:13:54.709> out<00:13:55.070> he<00:13:55.459> won't<00:13:55.700> be<00:13:55.820> able 00:13:56.019 --> 00:13:56.029 align:start position:0% and packets coming out he won't be able 00:13:56.029 --> 00:13:57.880 align:start position:0% and packets coming out he won't be able to<00:13:56.360> correlate<00:13:56.810> them<00:13:57.050> looking<00:13:57.410> at<00:13:57.470> the<00:13:57.620> binary 00:13:57.880 --> 00:13:57.890 align:start position:0% to correlate them looking at the binary 00:13:57.890 --> 00:14:00.460 align:start position:0% to correlate them looking at the binary representation<00:13:58.490> so<00:13:59.209> the<00:13:59.329> bit<00:13:59.570> pattern<00:14:00.079> of<00:14:00.260> the 00:14:00.460 --> 00:14:00.470 align:start position:0% representation so the bit pattern of the 00:14:00.470 --> 00:14:03.009 align:start position:0% representation so the bit pattern of the packets<00:14:00.890> in<00:14:01.100> and<00:14:01.339> out<00:14:01.519> does<00:14:02.209> not<00:14:02.240> correspond 00:14:03.009 --> 00:14:03.019 align:start position:0% packets in and out does not correspond 00:14:03.019 --> 00:14:06.610 align:start position:0% packets in and out does not correspond to<00:14:03.140> each<00:14:03.290> other<00:14:04.300> another<00:14:05.300> property<00:14:05.870> of<00:14:06.230> the 00:14:06.610 --> 00:14:06.620 align:start position:0% to each other another property of the 00:14:06.620 --> 00:14:09.370 align:start position:0% to each other another property of the mixed<00:14:07.279> networks<00:14:07.700> and<00:14:08.060> the<00:14:08.180> mixes<00:14:08.600> is<00:14:09.079> not 00:14:09.370 --> 00:14:09.380 align:start position:0% mixed networks and the mixes is not 00:14:09.380 --> 00:14:11.590 align:start position:0% mixed networks and the mixes is not related<00:14:09.890> anymore<00:14:10.190> to<00:14:10.670> the<00:14:10.760> bitstream<00:14:11.149> but 00:14:11.590 --> 00:14:11.600 align:start position:0% related anymore to the bitstream but 00:14:11.600 --> 00:14:14.949 align:start position:0% related anymore to the bitstream but rather<00:14:11.810> to<00:14:12.050> the<00:14:12.170> timing<00:14:12.500> of<00:14:12.890> the<00:14:12.980> packets<00:14:13.959> so 00:14:14.949 --> 00:14:14.959 align:start position:0% rather to the timing of the packets so 00:14:14.959 --> 00:14:17.290 align:start position:0% rather to the timing of the packets so most<00:14:15.410> of<00:14:15.560> the<00:14:15.709> routers<00:14:15.920> of<00:14:16.310> the<00:14:16.430> network<00:14:16.880> work 00:14:17.290 --> 00:14:17.300 align:start position:0% most of the routers of the network work 00:14:17.300 --> 00:14:19.810 align:start position:0% most of the routers of the network work at<00:14:17.540> the<00:14:17.750> first<00:14:18.170> in<00:14:18.380> first<00:14:18.740> out<00:14:18.920> basis<00:14:19.579> which 00:14:19.810 --> 00:14:19.820 align:start position:0% at the first in first out basis which 00:14:19.820 --> 00:14:21.760 align:start position:0% at the first in first out basis which means<00:14:20.060> the<00:14:20.240> first<00:14:20.450> packet<00:14:20.899> coming<00:14:21.170> in<00:14:21.470> will<00:14:21.649> be 00:14:21.760 --> 00:14:21.770 align:start position:0% means the first packet coming in will be 00:14:21.770 --> 00:14:24.850 align:start position:0% means the first packet coming in will be probably<00:14:22.130> the<00:14:22.339> first<00:14:22.579> coming<00:14:23.390> out<00:14:23.570> so<00:14:24.380> imagine 00:14:24.850 --> 00:14:24.860 align:start position:0% probably the first coming out so imagine 00:14:24.860 --> 00:14:26.800 align:start position:0% probably the first coming out so imagine your<00:14:25.430> mix<00:14:25.730> works<00:14:26.089> like<00:14:26.300> that<00:14:26.329> and<00:14:26.720> the 00:14:26.800 --> 00:14:26.810 align:start position:0% your mix works like that and the 00:14:26.810 --> 00:14:28.930 align:start position:0% your mix works like that and the adversary<00:14:27.350> observes<00:14:27.860> the<00:14:28.100> mix<00:14:28.310> and<00:14:28.550> he<00:14:28.760> says 00:14:28.930 --> 00:14:28.940 align:start position:0% adversary observes the mix and he says 00:14:28.940 --> 00:14:31.210 align:start position:0% adversary observes the mix and he says packets<00:14:29.360> coming<00:14:29.720> in<00:14:29.959> and<00:14:30.230> out<00:14:30.320> and<00:14:30.709> even 00:14:31.210 --> 00:14:31.220 align:start position:0% packets coming in and out and even 00:14:31.220 --> 00:14:33.460 align:start position:0% packets coming in and out and even though<00:14:31.339> we<00:14:31.459> cannot<00:14:31.760> correlate<00:14:32.329> them<00:14:32.600> based<00:14:33.350> on 00:14:33.460 --> 00:14:33.470 align:start position:0% though we cannot correlate them based on 00:14:33.470 --> 00:14:35.319 align:start position:0% though we cannot correlate them based on their<00:14:33.589> binary<00:14:33.920> representation<00:14:34.790> you<00:14:35.089> will<00:14:35.209> be 00:14:35.319 --> 00:14:35.329 align:start position:0% their binary representation you will be 00:14:35.329 --> 00:14:37.389 align:start position:0% their binary representation you will be able<00:14:35.510> to<00:14:35.779> correlate<00:14:36.200> them<00:14:36.440> looking<00:14:37.130> at<00:14:37.220> the 00:14:37.389 --> 00:14:37.399 align:start position:0% able to correlate them looking at the 00:14:37.399 --> 00:14:39.130 align:start position:0% able to correlate them looking at the time<00:14:37.640> of<00:14:37.790> their<00:14:37.910> arrivals<00:14:38.480> and<00:14:38.600> departures 00:14:39.130 --> 00:14:39.140 align:start position:0% time of their arrivals and departures 00:14:39.140 --> 00:14:41.740 align:start position:0% time of their arrivals and departures that's<00:14:39.860> why<00:14:40.070> the<00:14:40.430> mixes<00:14:40.940> do<00:14:41.180> not<00:14:41.390> forward 00:14:41.740 --> 00:14:41.750 align:start position:0% that's why the mixes do not forward 00:14:41.750 --> 00:14:44.250 align:start position:0% that's why the mixes do not forward packets<00:14:42.170> at<00:14:42.560> the<00:14:42.709> first-in<00:14:43.250> first-out 00:14:44.250 --> 00:14:44.260 align:start position:0% packets at the first-in first-out 00:14:44.260 --> 00:14:48.010 align:start position:0% packets at the first-in first-out role<00:14:45.260> instead<00:14:46.100> of<00:14:46.250> that<00:14:46.490> they<00:14:47.089> reorder<00:14:47.810> the 00:14:48.010 --> 00:14:48.020 align:start position:0% role instead of that they reorder the 00:14:48.020 --> 00:14:49.810 align:start position:0% role instead of that they reorder the packets<00:14:48.589> following<00:14:49.190> some<00:14:49.370> secret 00:14:49.810 --> 00:14:49.820 align:start position:0% packets following some secret 00:14:49.820 --> 00:14:52.960 align:start position:0% packets following some secret permutation<00:14:50.709> what<00:14:51.709> this<00:14:51.890> does<00:14:52.160> is<00:14:52.459> that<00:14:52.760> the 00:14:52.960 --> 00:14:52.970 align:start position:0% permutation what this does is that the 00:14:52.970 --> 00:14:55.240 align:start position:0% permutation what this does is that the timing<00:14:53.740> correspondence<00:14:54.740> between<00:14:54.860> the 00:14:55.240 --> 00:14:55.250 align:start position:0% timing correspondence between the 00:14:55.250 --> 00:14:57.550 align:start position:0% timing correspondence between the incoming<00:14:55.790> and<00:14:55.910> outgoing<00:14:56.060> packets<00:14:56.899> is<00:14:57.079> broken 00:14:57.550 --> 00:14:57.560 align:start position:0% incoming and outgoing packets is broken 00:14:57.560 --> 00:15:00.220 align:start position:0% incoming and outgoing packets is broken up<00:14:57.890> and<00:14:58.100> there<00:14:58.699> are<00:14:58.730> many<00:14:59.060> different<00:14:59.300> ways<00:15:00.079> to 00:15:00.220 --> 00:15:00.230 align:start position:0% up and there are many different ways to 00:15:00.230 --> 00:15:02.970 align:start position:0% up and there are many different ways to perform<00:15:00.529> this<00:15:01.270> reordering<00:15:02.270> following 00:15:02.970 --> 00:15:02.980 align:start position:0% perform this reordering following 00:15:02.980 --> 00:15:07.139 align:start position:0% perform this reordering following presentation<00:15:03.850> the<00:15:04.149> original<00:15:04.899> chance<00:15:05.910> mix<00:15:06.910> net 00:15:07.139 --> 00:15:07.149 align:start position:0% presentation the original chance mix net 00:15:07.149 --> 00:15:10.290 align:start position:0% presentation the original chance mix net words<00:15:07.389> operated<00:15:08.170> in<00:15:08.760> synchronised<00:15:09.760> batches 00:15:10.290 --> 00:15:10.300 align:start position:0% words operated in synchronised batches 00:15:10.300 --> 00:15:13.500 align:start position:0% words operated in synchronised batches which<00:15:10.779> meant<00:15:11.139> that<00:15:11.260> the<00:15:12.220> mix<00:15:12.519> is<00:15:12.730> waiting<00:15:13.360> the 00:15:13.500 --> 00:15:13.510 align:start position:0% which meant that the mix is waiting the 00:15:13.510 --> 00:15:15.180 align:start position:0% which meant that the mix is waiting the whole<00:15:13.750> round<00:15:14.050> with<00:15:14.380> which<00:15:14.709> can<00:15:14.920> be<00:15:15.040> for 00:15:15.180 --> 00:15:15.190 align:start position:0% whole round with which can be for 00:15:15.190 --> 00:15:17.660 align:start position:0% whole round with which can be for example<00:15:15.220> an<00:15:15.850> hour<00:15:16.149> or<00:15:16.570> something<00:15:16.779> like<00:15:16.959> that 00:15:17.660 --> 00:15:17.670 align:start position:0% example an hour or something like that 00:15:17.670 --> 00:15:20.970 align:start position:0% example an hour or something like that and<00:15:18.670> gathered<00:15:19.540> some<00:15:19.570> packets<00:15:20.230> processes<00:15:20.829> them 00:15:20.970 --> 00:15:20.980 align:start position:0% and gathered some packets processes them 00:15:20.980 --> 00:15:22.769 align:start position:0% and gathered some packets processes them and<00:15:21.160> at<00:15:21.339> the<00:15:21.370> end<00:15:21.639> of<00:15:21.760> the<00:15:21.940> round<00:15:22.089> shuffles 00:15:22.769 --> 00:15:22.779 align:start position:0% and at the end of the round shuffles 00:15:22.779 --> 00:15:25.230 align:start position:0% and at the end of the round shuffles flowing<00:15:23.079> a<00:15:23.170> secret<00:15:23.500> permutation<00:15:24.220> and<00:15:24.399> flashes 00:15:25.230 --> 00:15:25.240 align:start position:0% flowing a secret permutation and flashes 00:15:25.240 --> 00:15:27.990 align:start position:0% flowing a secret permutation and flashes to<00:15:25.360> the<00:15:25.389> next<00:15:25.750> hole<00:15:25.899> so<00:15:26.589> those<00:15:26.889> two<00:15:27.220> properties 00:15:27.990 --> 00:15:28.000 align:start position:0% to the next hole so those two properties 00:15:28.000 --> 00:15:30.420 align:start position:0% to the next hole so those two properties the<00:15:28.420> bitwise<00:15:28.630> and<00:15:28.990> unlink<00:15:29.589> ability<00:15:30.130> and<00:15:30.339> the 00:15:30.420 --> 00:15:30.430 align:start position:0% the bitwise and unlink ability and the 00:15:30.430 --> 00:15:33.060 align:start position:0% the bitwise and unlink ability and the timing<00:15:30.820> and<00:15:30.970> likability<00:15:31.649> allow<00:15:32.649> you<00:15:32.709> to 00:15:33.060 --> 00:15:33.070 align:start position:0% timing and likability allow you to 00:15:33.070 --> 00:15:35.430 align:start position:0% timing and likability allow you to achieve<00:15:33.209> anonymity<00:15:34.209> of<00:15:34.510> your<00:15:34.660> communication 00:15:35.430 --> 00:15:35.440 align:start position:0% achieve anonymity of your communication 00:15:35.440 --> 00:15:38.790 align:start position:0% achieve anonymity of your communication because<00:15:35.920> the<00:15:36.279> mixes<00:15:36.850> are<00:15:37.839> combined<00:15:38.320> in<00:15:38.560> long 00:15:38.790 --> 00:15:38.800 align:start position:0% because the mixes are combined in long 00:15:38.800 --> 00:15:42.180 align:start position:0% because the mixes are combined in long chains<00:15:38.829> and<00:15:39.610> thanks<00:15:40.600> to<00:15:40.720> that<00:15:40.899> none<00:15:41.889> of<00:15:41.920> the 00:15:42.180 --> 00:15:42.190 align:start position:0% chains and thanks to that none of the 00:15:42.190 --> 00:15:44.850 align:start position:0% chains and thanks to that none of the mixes<00:15:42.670> knows<00:15:43.269> who<00:15:43.959> is<00:15:44.019> the<00:15:44.260> sender<00:15:44.529> and 00:15:44.850 --> 00:15:44.860 align:start position:0% mixes knows who is the sender and 00:15:44.860 --> 00:15:46.710 align:start position:0% mixes knows who is the sender and recipient<00:15:45.279> because<00:15:45.970> they<00:15:46.120> only<00:15:46.329> know<00:15:46.449> that 00:15:46.710 --> 00:15:46.720 align:start position:0% recipient because they only know that 00:15:46.720 --> 00:15:48.930 align:start position:0% recipient because they only know that previous<00:15:47.230> and<00:15:47.500> the<00:15:47.740> last<00:15:47.949> and<00:15:48.160> then<00:15:48.550> at<00:15:48.820> the 00:15:48.930 --> 00:15:48.940 align:start position:0% previous and the last and then at the 00:15:48.940 --> 00:15:51.389 align:start position:0% previous and the last and then at the next<00:15:49.060> hold<00:15:49.480> so<00:15:50.110> they<00:15:50.290> don't<00:15:50.589> know<00:15:50.829> what<00:15:51.100> is<00:15:51.250> the 00:15:51.389 --> 00:15:51.399 align:start position:0% next hold so they don't know what is the 00:15:51.399 --> 00:15:53.280 align:start position:0% next hold so they don't know what is the whole<00:15:51.639> path<00:15:52.000> and<00:15:52.300> who<00:15:52.449> is<00:15:52.540> sending<00:15:52.839> messages 00:15:53.280 --> 00:15:53.290 align:start position:0% whole path and who is sending messages 00:15:53.290 --> 00:15:56.340 align:start position:0% whole path and who is sending messages to<00:15:53.500> home<00:15:53.740> and<00:15:54.190> at<00:15:54.760> the<00:15:54.790> other<00:15:55.000> and<00:15:55.690> at<00:15:55.839> the<00:15:55.959> same 00:15:56.340 --> 00:15:56.350 align:start position:0% to home and at the other and at the same 00:15:56.350 --> 00:15:59.040 align:start position:0% to home and at the other and at the same time<00:15:56.680> the<00:15:57.160> adversary<00:15:57.399> who's<00:15:58.149> observing<00:15:58.329> even 00:15:59.040 --> 00:15:59.050 align:start position:0% time the adversary who's observing even 00:15:59.050 --> 00:16:01.350 align:start position:0% time the adversary who's observing even the<00:15:59.170> entire<00:15:59.589> network<00:15:59.920> can<00:16:00.550> sniff<00:16:00.880> all<00:16:01.180> the 00:16:01.350 --> 00:16:01.360 align:start position:0% the entire network can sniff all the 00:16:01.360 --> 00:16:03.689 align:start position:0% the entire network can sniff all the packets<00:16:01.779> at<00:16:01.990> all<00:16:02.320> the<00:16:02.470> links<00:16:02.769> won't<00:16:03.279> be<00:16:03.459> able 00:16:03.689 --> 00:16:03.699 align:start position:0% packets at all the links won't be able 00:16:03.699 --> 00:16:06.480 align:start position:0% packets at all the links won't be able to<00:16:03.880> correlate<00:16:04.449> your<00:16:04.529> communication<00:16:05.529> so<00:16:06.130> as 00:16:06.480 --> 00:16:06.490 align:start position:0% to correlate your communication so as 00:16:06.490 --> 00:16:09.030 align:start position:0% to correlate your communication so as long<00:16:06.760> as<00:16:06.820> at<00:16:07.149> least<00:16:07.329> one<00:16:07.510> mix<00:16:08.110> in<00:16:08.380> the<00:16:08.620> path<00:16:08.829> is 00:16:09.030 --> 00:16:09.040 align:start position:0% long as at least one mix in the path is 00:16:09.040 --> 00:16:13.860 align:start position:0% long as at least one mix in the path is honest<00:16:09.430> your<00:16:09.910> strong<00:16:10.269> anonymity<00:16:10.839> remains<00:16:12.870> so 00:16:13.860 --> 00:16:13.870 align:start position:0% honest your strong anonymity remains so 00:16:13.870 --> 00:16:15.809 align:start position:0% honest your strong anonymity remains so any<00:16:14.139> mixed<00:16:14.500> network<00:16:14.800> designs<00:16:15.190> had<00:16:15.459> a<00:16:15.490> couple 00:16:15.809 --> 00:16:15.819 align:start position:0% any mixed network designs had a couple 00:16:15.819 --> 00:16:18.180 align:start position:0% any mixed network designs had a couple of<00:16:16.089> limitations<00:16:16.560> in<00:16:17.560> terms<00:16:17.620> of<00:16:17.949> performance 00:16:18.180 --> 00:16:18.190 align:start position:0% of limitations in terms of performance 00:16:18.190 --> 00:16:21.180 align:start position:0% of limitations in terms of performance mostly<00:16:19.029> scalability<00:16:19.690> and<00:16:20.170> very<00:16:20.470> high<00:16:20.709> latency 00:16:21.180 --> 00:16:21.190 align:start position:0% mostly scalability and very high latency 00:16:21.190 --> 00:16:23.759 align:start position:0% mostly scalability and very high latency overhead<00:16:21.720> because<00:16:22.720> those<00:16:22.930> batching<00:16:23.440> plants 00:16:23.759 --> 00:16:23.769 align:start position:0% overhead because those batching plants 00:16:23.769 --> 00:16:25.949 align:start position:0% overhead because those batching plants required<00:16:24.130> a<00:16:24.339> lot<00:16:24.670> of<00:16:24.699> time<00:16:24.880> to<00:16:25.360> wait<00:16:25.480> for<00:16:25.510> many 00:16:25.949 --> 00:16:25.959 align:start position:0% required a lot of time to wait for many 00:16:25.959 --> 00:16:28.650 align:start position:0% required a lot of time to wait for many packets<00:16:26.410> to<00:16:26.589> arrive<00:16:26.620> that's<00:16:27.579> why<00:16:27.760> the<00:16:28.180> nimac 00:16:28.650 --> 00:16:28.660 align:start position:0% packets to arrive that's why the nimac 00:16:28.660 --> 00:16:30.689 align:start position:0% packets to arrive that's why the nimac network<00:16:29.139> is<00:16:29.380> based<00:16:29.680> on<00:16:29.949> the<00:16:30.130> modern<00:16:30.339> mix 00:16:30.689 --> 00:16:30.699 align:start position:0% network is based on the modern mix 00:16:30.699 --> 00:16:32.850 align:start position:0% network is based on the modern mix network<00:16:31.089> design<00:16:31.449> called<00:16:31.779> topics<00:16:32.260> which 00:16:32.850 --> 00:16:32.860 align:start position:0% network design called topics which 00:16:32.860 --> 00:16:34.920 align:start position:0% network design called topics which solves<00:16:33.370> the<00:16:33.459> problems<00:16:33.970> of<00:16:34.120> traditional<00:16:34.690> mix 00:16:34.920 --> 00:16:34.930 align:start position:0% solves the problems of traditional mix 00:16:34.930 --> 00:16:40.379 align:start position:0% solves the problems of traditional mix networks<00:16:36.779> so<00:16:37.779> a<00:16:37.810> little<00:16:38.260> bit<00:16:38.440> about<00:16:39.310> how<00:16:39.730> name 00:16:40.379 --> 00:16:40.389 align:start position:0% networks so a little bit about how name 00:16:40.389 --> 00:16:42.420 align:start position:0% networks so a little bit about how name mix<00:16:40.630> at<00:16:40.810> work<00:16:40.959> works<00:16:41.230> and<00:16:41.529> how<00:16:41.709> we<00:16:41.769> solve<00:16:42.190> those 00:16:42.420 --> 00:16:42.430 align:start position:0% mix at work works and how we solve those 00:16:42.430 --> 00:16:45.420 align:start position:0% mix at work works and how we solve those issue<00:16:43.079> of<00:16:44.079> limited<00:16:44.649> performance<00:16:44.949> in 00:16:45.420 --> 00:16:45.430 align:start position:0% issue of limited performance in 00:16:45.430 --> 00:16:48.900 align:start position:0% issue of limited performance in traditional<00:16:45.880> mix<00:16:46.089> networks<00:16:46.510> so<00:16:47.199> the<00:16:47.319> first 00:16:48.900 --> 00:16:48.910 align:start position:0% traditional mix networks so the first 00:16:48.910 --> 00:16:52.380 align:start position:0% traditional mix networks so the first is<00:16:49.510> the<00:16:49.660> network<00:16:49.870> topology<00:16:50.370> so<00:16:51.370> apology<00:16:52.090> means 00:16:52.380 --> 00:16:52.390 align:start position:0% is the network topology so apology means 00:16:52.390 --> 00:16:55.470 align:start position:0% is the network topology so apology means that<00:16:52.830> mixed<00:16:53.830> notes<00:16:54.010> are<00:16:54.310> roped<00:16:54.730> into<00:16:54.970> layers 00:16:55.470 --> 00:16:55.480 align:start position:0% that mixed notes are roped into layers 00:16:55.480 --> 00:16:58.080 align:start position:0% that mixed notes are roped into layers and<00:16:55.810> the<00:16:56.440> traffic<00:16:56.890> is<00:16:57.070> flowing<00:16:57.280> from<00:16:57.760> first 00:16:58.080 --> 00:16:58.090 align:start position:0% and the traffic is flowing from first 00:16:58.090 --> 00:17:00.470 align:start position:0% and the traffic is flowing from first layer<00:16:58.330> to<00:16:58.660> the<00:16:58.810> last<00:16:59.050> layer<00:16:59.320> in<00:16:59.620> one<00:16:59.860> direction 00:17:00.470 --> 00:17:00.480 align:start position:0% layer to the last layer in one direction 00:17:00.480 --> 00:17:02.940 align:start position:0% layer to the last layer in one direction and<00:17:01.480> why<00:17:01.660> did<00:17:01.900> we<00:17:02.020> pick<00:17:02.230> the<00:17:02.440> stratified 00:17:02.940 --> 00:17:02.950 align:start position:0% and why did we pick the stratified 00:17:02.950 --> 00:17:05.280 align:start position:0% and why did we pick the stratified topology<00:17:03.550> it's<00:17:03.730> because<00:17:04.089> as<00:17:04.300> research<00:17:05.050> has 00:17:05.280 --> 00:17:05.290 align:start position:0% topology it's because as research has 00:17:05.290 --> 00:17:06.990 align:start position:0% topology it's because as research has shown<00:17:05.589> the<00:17:05.800> stratified<00:17:06.370> topology<00:17:06.970> has 00:17:06.990 --> 00:17:07.000 align:start position:0% shown the stratified topology has 00:17:07.000 --> 00:17:09.689 align:start position:0% shown the stratified topology has debates<00:17:07.630> the<00:17:08.079> best<00:17:08.290> trade<00:17:08.620> off<00:17:08.860> between<00:17:09.100> the 00:17:09.689 --> 00:17:09.699 align:start position:0% debates the best trade off between the 00:17:09.699 --> 00:17:12.270 align:start position:0% debates the best trade off between the anonymity<00:17:10.120> and<00:17:10.600> performance<00:17:11.170> and<00:17:11.440> it's<00:17:12.190> a 00:17:12.270 --> 00:17:12.280 align:start position:0% anonymity and performance and it's a 00:17:12.280 --> 00:17:14.550 align:start position:0% anonymity and performance and it's a topology<00:17:12.579> which<00:17:12.940> scales<00:17:13.270> horizontally<00:17:14.079> which 00:17:14.550 --> 00:17:14.560 align:start position:0% topology which scales horizontally which 00:17:14.560 --> 00:17:16.680 align:start position:0% topology which scales horizontally which means<00:17:14.829> that<00:17:15.100> you<00:17:15.190> can<00:17:15.339> very<00:17:15.699> easily<00:17:15.790> scale 00:17:16.680 --> 00:17:16.690 align:start position:0% means that you can very easily scale 00:17:16.690 --> 00:17:19.770 align:start position:0% means that you can very easily scale your<00:17:17.020> network<00:17:17.560> if<00:17:18.520> the<00:17:18.670> number<00:17:19.270> of<00:17:19.300> users 00:17:19.770 --> 00:17:19.780 align:start position:0% your network if the number of users 00:17:19.780 --> 00:17:21.630 align:start position:0% your network if the number of users using<00:17:20.050> it<00:17:20.290> increases<00:17:20.920> or<00:17:21.100> the<00:17:21.220> volume<00:17:21.520> of 00:17:21.630 --> 00:17:21.640 align:start position:0% using it increases or the volume of 00:17:21.640 --> 00:17:24.000 align:start position:0% using it increases or the volume of traffic<00:17:21.880> increases<00:17:22.689> because<00:17:23.230> you<00:17:23.439> simply 00:17:24.000 --> 00:17:24.010 align:start position:0% traffic increases because you simply 00:17:24.010 --> 00:17:26.610 align:start position:0% traffic increases because you simply have<00:17:24.339> to<00:17:24.370> incrementally<00:17:24.880> add<00:17:25.480> more<00:17:25.810> nodes<00:17:26.020> so 00:17:26.610 --> 00:17:26.620 align:start position:0% have to incrementally add more nodes so 00:17:26.620 --> 00:17:28.530 align:start position:0% have to incrementally add more nodes so for<00:17:26.800> example<00:17:27.189> tourists<00:17:27.610> an<00:17:27.699> example<00:17:28.209> of<00:17:28.390> a 00:17:28.530 --> 00:17:28.540 align:start position:0% for example tourists an example of a 00:17:28.540 --> 00:17:30.480 align:start position:0% for example tourists an example of a network<00:17:28.990> of<00:17:29.290> an<00:17:29.470> anonymous<00:17:29.770> network<00:17:30.340> which 00:17:30.480 --> 00:17:30.490 align:start position:0% network of an anonymous network which 00:17:30.490 --> 00:17:35.100 align:start position:0% network of an anonymous network which also<00:17:30.760> scans<00:17:31.210> horizontally<00:17:33.450> in<00:17:34.450> terms<00:17:34.780> of<00:17:35.020> the 00:17:35.100 --> 00:17:35.110 align:start position:0% also scans horizontally in terms of the 00:17:35.110 --> 00:17:37.160 align:start position:0% also scans horizontally in terms of the bitwise<00:17:35.470> amicability<00:17:36.130> and<00:17:36.670> the 00:17:37.160 --> 00:17:37.170 align:start position:0% bitwise amicability and the 00:17:37.170 --> 00:17:39.630 align:start position:0% bitwise amicability and the cryptographic<00:17:38.170> packet<00:17:38.860> format<00:17:39.220> which<00:17:39.460> were 00:17:39.630 --> 00:17:39.640 align:start position:0% cryptographic packet format which were 00:17:39.640 --> 00:17:41.550 align:start position:0% cryptographic packet format which were using<00:17:39.940> we're<00:17:40.360> using<00:17:40.570> the<00:17:40.840> Sphynx<00:17:41.230> packet 00:17:41.550 --> 00:17:41.560 align:start position:0% using we're using the Sphynx packet 00:17:41.560 --> 00:17:44.430 align:start position:0% using we're using the Sphynx packet format<00:17:41.950> if<00:17:42.640> some<00:17:43.300> of<00:17:43.480> you<00:17:43.600> know<00:17:43.660> lightning 00:17:44.430 --> 00:17:44.440 align:start position:0% format if some of you know lightning 00:17:44.440 --> 00:17:46.140 align:start position:0% format if some of you know lightning networks<00:17:44.920> you<00:17:45.070> will<00:17:45.190> know<00:17:45.310> that<00:17:45.340> exactly<00:17:45.820> the 00:17:46.140 --> 00:17:46.150 align:start position:0% networks you will know that exactly the 00:17:46.150 --> 00:17:48.090 align:start position:0% networks you will know that exactly the same<00:17:46.330> cryptographic<00:17:46.720> packet<00:17:47.290> format<00:17:47.650> is<00:17:47.860> used 00:17:48.090 --> 00:17:48.100 align:start position:0% same cryptographic packet format is used 00:17:48.100 --> 00:17:50.700 align:start position:0% same cryptographic packet format is used in<00:17:48.310> the<00:17:48.490> Lightning<00:17:48.850> networks<00:17:49.270> and<00:17:49.570> the<00:17:50.410> Sphinx 00:17:50.700 --> 00:17:50.710 align:start position:0% in the Lightning networks and the Sphinx 00:17:50.710 --> 00:17:54.000 align:start position:0% in the Lightning networks and the Sphinx packet<00:17:51.040> format<00:17:51.630> offers<00:17:52.630> the<00:17:53.260> unlink<00:17:53.590> ability 00:17:54.000 --> 00:17:54.010 align:start position:0% packet format offers the unlink ability 00:17:54.010 --> 00:17:55.710 align:start position:0% packet format offers the unlink ability of<00:17:54.130> the<00:17:54.220> binary<00:17:54.550> pattern<00:17:54.850> and<00:17:55.270> make<00:17:55.420> sure<00:17:55.570> that 00:17:55.710 --> 00:17:55.720 align:start position:0% of the binary pattern and make sure that 00:17:55.720 --> 00:17:57.480 align:start position:0% of the binary pattern and make sure that all<00:17:55.960> the<00:17:56.080> messages<00:17:56.470> are<00:17:56.710> padded<00:17:57.040> to<00:17:57.160> the<00:17:57.250> same 00:17:57.480 --> 00:17:57.490 align:start position:0% all the messages are padded to the same 00:17:57.490 --> 00:18:01.350 align:start position:0% all the messages are padded to the same length<00:17:57.730> but<00:17:58.690> it<00:17:59.170> also<00:17:59.590> ensures<00:18:00.150> resistance<00:18:01.150> to 00:18:01.350 --> 00:18:01.360 align:start position:0% length but it also ensures resistance to 00:18:01.360 --> 00:18:04.200 align:start position:0% length but it also ensures resistance to packing<00:18:01.780> and<00:18:01.930> replay<00:18:02.290> attacks<00:18:02.710> and<00:18:03.310> it<00:18:03.880> allows 00:18:04.200 --> 00:18:04.210 align:start position:0% packing and replay attacks and it allows 00:18:04.210 --> 00:18:06.000 align:start position:0% packing and replay attacks and it allows to<00:18:04.420> encode<00:18:04.870> all<00:18:05.260> the<00:18:05.530> relevant<00:18:05.800> information 00:18:06.000 --> 00:18:06.010 align:start position:0% to encode all the relevant information 00:18:06.010 --> 00:18:09.570 align:start position:0% to encode all the relevant information will<00:18:06.640> fit<00:18:06.850> the<00:18:07.030> packet<00:18:07.540> with<00:18:08.290> what<00:18:08.950> means<00:18:09.250> that 00:18:09.570 --> 00:18:09.580 align:start position:0% will fit the packet with what means that 00:18:09.580 --> 00:18:12.030 align:start position:0% will fit the packet with what means that the<00:18:10.180> sender<00:18:10.690> as<00:18:10.900> soon<00:18:11.080> as<00:18:11.260> he<00:18:11.500> sends<00:18:11.920> the 00:18:12.030 --> 00:18:12.040 align:start position:0% the sender as soon as he sends the 00:18:12.040 --> 00:18:13.800 align:start position:0% the sender as soon as he sends the message<00:18:12.400> into<00:18:12.820> the<00:18:12.940> network<00:18:13.300> we<00:18:13.480> can<00:18:13.510> go 00:18:13.800 --> 00:18:13.810 align:start position:0% message into the network we can go 00:18:13.810 --> 00:18:15.840 align:start position:0% message into the network we can go offline<00:18:14.230> which<00:18:14.890> for<00:18:15.130> example<00:18:15.160> does<00:18:15.670> not 00:18:15.840 --> 00:18:15.850 align:start position:0% offline which for example does not 00:18:15.850 --> 00:18:17.970 align:start position:0% offline which for example does not happen<00:18:16.180> in<00:18:16.270> tour<00:18:16.480> because<00:18:16.690> it<00:18:16.840> or<00:18:17.230> you<00:18:17.620> have<00:18:17.830> to 00:18:17.970 --> 00:18:17.980 align:start position:0% happen in tour because it or you have to 00:18:17.980 --> 00:18:19.650 align:start position:0% happen in tour because it or you have to be<00:18:18.100> online<00:18:18.280> all<00:18:18.670> the<00:18:18.700> time<00:18:19.060> to<00:18:19.270> be<00:18:19.390> able<00:18:19.510> to 00:18:19.650 --> 00:18:19.660 align:start position:0% be online all the time to be able to 00:18:19.660 --> 00:18:21.420 align:start position:0% be online all the time to be able to communicate<00:18:20.320> when<00:18:20.500> you're<00:18:20.620> sending<00:18:20.920> packets 00:18:21.420 --> 00:18:21.430 align:start position:0% communicate when you're sending packets 00:18:21.430 --> 00:18:25.010 align:start position:0% communicate when you're sending packets because<00:18:21.760> you<00:18:21.880> have<00:18:22.000> an<00:18:22.120> open<00:18:22.420> circuit<00:18:22.810> in<00:18:23.440> the 00:18:25.010 --> 00:18:25.020 align:start position:0% because you have an open circuit in the 00:18:25.020 --> 00:18:27.080 align:start position:0% because you have an open circuit in the because<00:18:25.710> we're<00:18:25.890> using<00:18:26.040> Sphinx<00:18:26.610> we<00:18:26.730> can<00:18:26.880> just 00:18:27.080 --> 00:18:27.090 align:start position:0% because we're using Sphinx we can just 00:18:27.090 --> 00:18:32.120 align:start position:0% because we're using Sphinx we can just set<00:18:27.480> the<00:18:27.630> message<00:18:28.020> and<00:18:28.410> go<00:18:28.680> online<00:18:29.870> and<00:18:31.130> in 00:18:32.120 --> 00:18:32.130 align:start position:0% set the message and go online and in 00:18:32.130 --> 00:18:34.160 align:start position:0% set the message and go online and in terms<00:18:32.340> of<00:18:32.520> this<00:18:32.730> mixing<00:18:33.330> operation<00:18:33.630> this 00:18:34.160 --> 00:18:34.170 align:start position:0% terms of this mixing operation this 00:18:34.170 --> 00:18:36.320 align:start position:0% terms of this mixing operation this reordering<00:18:34.740> we<00:18:35.250> use<00:18:35.430> the<00:18:35.820> so<00:18:36.060> called 00:18:36.320 --> 00:18:36.330 align:start position:0% reordering we use the so called 00:18:36.330 --> 00:18:38.740 align:start position:0% reordering we use the so called continuous<00:18:36.990> time<00:18:37.230> axis<00:18:37.650> and<00:18:37.680> this<00:18:37.980> is<00:18:38.040> a<00:18:38.220> very 00:18:38.740 --> 00:18:38.750 align:start position:0% continuous time axis and this is a very 00:18:38.750 --> 00:18:43.210 align:start position:0% continuous time axis and this is a very nice<00:18:39.750> technique<00:18:40.440> for<00:18:40.770> mixing<00:18:41.250> at<00:18:41.700> the<00:18:42.000> packets 00:18:43.210 --> 00:18:43.220 align:start position:0% nice technique for mixing at the packets 00:18:43.220 --> 00:18:45.650 align:start position:0% nice technique for mixing at the packets how<00:18:44.220> it<00:18:44.370> works<00:18:44.700> we<00:18:44.850> don't<00:18:45.000> have<00:18:45.210> synchronized 00:18:45.650 --> 00:18:45.660 align:start position:0% how it works we don't have synchronized 00:18:45.660 --> 00:18:48.410 align:start position:0% how it works we don't have synchronized friends<00:18:46.170> we<00:18:46.890> do<00:18:47.010> not<00:18:47.100> batch<00:18:47.430> messages<00:18:48.030> instead 00:18:48.410 --> 00:18:48.420 align:start position:0% friends we do not batch messages instead 00:18:48.420 --> 00:18:52.640 align:start position:0% friends we do not batch messages instead of<00:18:48.660> that<00:18:48.900> each<00:18:49.620> packet<00:18:50.310> is<00:18:50.460> delayed<00:18:51.410> with<00:18:52.410> some 00:18:52.640 --> 00:18:52.650 align:start position:0% of that each packet is delayed with some 00:18:52.650 --> 00:18:55.280 align:start position:0% of that each packet is delayed with some random<00:18:53.070> amount<00:18:53.430> of<00:18:53.520> time<00:18:53.580> and<00:18:54.300> the<00:18:54.810> sender 00:18:55.280 --> 00:18:55.290 align:start position:0% random amount of time and the sender 00:18:55.290 --> 00:18:58.010 align:start position:0% random amount of time and the sender when<00:18:55.700> he's<00:18:56.700> preparing<00:18:57.210> the<00:18:57.390> packet<00:18:57.750> to<00:18:57.780> be 00:18:58.010 --> 00:18:58.020 align:start position:0% when he's preparing the packet to be 00:18:58.020 --> 00:19:00.320 align:start position:0% when he's preparing the packet to be sent<00:18:58.320> into<00:18:58.590> the<00:18:58.800> mix<00:18:59.010> Network<00:18:59.460> encapsulate 00:19:00.320 --> 00:19:00.330 align:start position:0% sent into the mix Network encapsulate 00:19:00.330 --> 00:19:03.380 align:start position:0% sent into the mix Network encapsulate those<00:19:00.960> random<00:19:01.320> delays<00:19:01.860> from<00:19:02.310> each<00:19:02.670> mix<00:19:03.000> on<00:19:03.270> the 00:19:03.380 --> 00:19:03.390 align:start position:0% those random delays from each mix on the 00:19:03.390 --> 00:19:06.860 align:start position:0% those random delays from each mix on the path<00:19:04.040> this<00:19:05.040> delay<00:19:05.310> is<00:19:05.490> randomized<00:19:06.180> and<00:19:06.450> that 00:19:06.860 --> 00:19:06.870 align:start position:0% path this delay is randomized and that 00:19:06.870 --> 00:19:09.110 align:start position:0% path this delay is randomized and that makes<00:19:07.140> when<00:19:07.560> he<00:19:07.800> strips<00:19:08.430> the<00:19:08.700> level<00:19:09.000> of 00:19:09.110 --> 00:19:09.120 align:start position:0% makes when he strips the level of 00:19:09.120 --> 00:19:10.940 align:start position:0% makes when he strips the level of cryptographic<00:19:09.510> protection<00:19:09.960> because<00:19:10.680> I<00:19:10.710> see 00:19:10.940 --> 00:19:10.950 align:start position:0% cryptographic protection because I see 00:19:10.950 --> 00:19:12.530 align:start position:0% cryptographic protection because I see this<00:19:11.130> delay<00:19:11.400> and<00:19:11.640> she<00:19:11.790> knows<00:19:12.000> for<00:19:12.300> how<00:19:12.360> long 00:19:12.530 --> 00:19:12.540 align:start position:0% this delay and she knows for how long 00:19:12.540 --> 00:19:14.180 align:start position:0% this delay and she knows for how long you<00:19:12.870> should<00:19:12.930> keep<00:19:13.110> the<00:19:13.440> packet<00:19:13.800> before 00:19:14.180 --> 00:19:14.190 align:start position:0% you should keep the packet before 00:19:14.190 --> 00:19:16.700 align:start position:0% you should keep the packet before flashing<00:19:14.850> it<00:19:15.000> and<00:19:15.390> why<00:19:15.750> actually<00:19:16.050> this<00:19:16.500> is<00:19:16.680> a 00:19:16.700 --> 00:19:16.710 align:start position:0% flashing it and why actually this is a 00:19:16.710 --> 00:19:19.340 align:start position:0% flashing it and why actually this is a good<00:19:17.100> technique<00:19:17.280> for<00:19:17.490> mixing<00:19:18.060> well<00:19:18.810> we<00:19:19.230> are 00:19:19.340 --> 00:19:19.350 align:start position:0% good technique for mixing well we are 00:19:19.350 --> 00:19:22.490 align:start position:0% good technique for mixing well we are picking<00:19:19.830> the<00:19:20.390> delays<00:19:21.390> from<00:19:21.600> the<00:19:21.750> exponential 00:19:22.490 --> 00:19:22.500 align:start position:0% picking the delays from the exponential 00:19:22.500 --> 00:19:24.050 align:start position:0% picking the delays from the exponential distribution<00:19:22.650> and<00:19:23.430> the<00:19:23.580> exponential 00:19:24.050 --> 00:19:24.060 align:start position:0% distribution and the exponential 00:19:24.060 --> 00:19:25.880 align:start position:0% distribution and the exponential distribution<00:19:24.300> has<00:19:25.050> a<00:19:25.080> very<00:19:25.410> nice<00:19:25.560> property 00:19:25.880 --> 00:19:25.890 align:start position:0% distribution has a very nice property 00:19:25.890 --> 00:19:29.620 align:start position:0% distribution has a very nice property called<00:19:26.550> memoryless<00:19:27.300> property<00:19:27.890> what<00:19:28.890> it<00:19:29.040> means 00:19:29.620 --> 00:19:29.630 align:start position:0% called memoryless property what it means 00:19:29.630 --> 00:19:32.570 align:start position:0% called memoryless property what it means imagine<00:19:30.630> you<00:19:30.990> are<00:19:31.500> the<00:19:31.560> adversary<00:19:32.250> and<00:19:32.460> you're 00:19:32.570 --> 00:19:32.580 align:start position:0% imagine you are the adversary and you're 00:19:32.580 --> 00:19:35.300 align:start position:0% imagine you are the adversary and you're observing<00:19:33.150> and<00:19:33.390> mixed<00:19:33.690> knot<00:19:33.870> and<00:19:34.140> you<00:19:34.260> see<00:19:34.500> one 00:19:35.300 --> 00:19:35.310 align:start position:0% observing and mixed knot and you see one 00:19:35.310 --> 00:19:37.490 align:start position:0% observing and mixed knot and you see one packet<00:19:35.730> arriving<00:19:36.090> at<00:19:36.240> some<00:19:36.420> pot<00:19:36.720> at<00:19:37.080> some<00:19:37.290> time 00:19:37.490 --> 00:19:37.500 align:start position:0% packet arriving at some pot at some time 00:19:37.500 --> 00:19:39.350 align:start position:0% packet arriving at some pot at some time and<00:19:37.770> then<00:19:37.920> another<00:19:38.100> packet<00:19:38.670> arriving<00:19:39.090> to<00:19:39.270> the 00:19:39.350 --> 00:19:39.360 align:start position:0% and then another packet arriving to the 00:19:39.360 --> 00:19:41.630 align:start position:0% and then another packet arriving to the mix<00:19:39.570> at<00:19:39.780> another<00:19:40.290> time<00:19:40.590> and<00:19:40.800> then<00:19:41.310> you<00:19:41.430> see<00:19:41.610> a 00:19:41.630 --> 00:19:41.640 align:start position:0% mix at another time and then you see a 00:19:41.640 --> 00:19:44.180 align:start position:0% mix at another time and then you see a packet<00:19:42.000> leaving<00:19:42.420> the<00:19:42.630> mix<00:19:42.810> this<00:19:43.500> memory<00:19:43.860> and 00:19:44.180 --> 00:19:44.190 align:start position:0% packet leaving the mix this memory and 00:19:44.190 --> 00:19:46.460 align:start position:0% packet leaving the mix this memory and memory<00:19:44.430> less<00:19:44.730> property<00:19:44.760> tells<00:19:45.570> you<00:19:45.810> that<00:19:46.080> you 00:19:46.460 --> 00:19:46.470 align:start position:0% memory less property tells you that you 00:19:46.470 --> 00:19:50.360 align:start position:0% memory less property tells you that you cannot<00:19:47.630> guess<00:19:48.630> which<00:19:49.170> of<00:19:49.500> the<00:19:49.920> incoming 00:19:50.360 --> 00:19:50.370 align:start position:0% cannot guess which of the incoming 00:19:50.370 --> 00:19:52.520 align:start position:0% cannot guess which of the incoming packets<00:19:51.060> is<00:19:51.270> that<00:19:51.630> one<00:19:51.930> would<00:19:52.110> you<00:19:52.230> observe 00:19:52.520 --> 00:19:52.530 align:start position:0% packets is that one would you observe 00:19:52.530 --> 00:19:56.000 align:start position:0% packets is that one would you observe going<00:19:53.010> out<00:19:53.280> because<00:19:54.170> the<00:19:55.170> timing<00:19:55.650> at<00:19:55.800> which 00:19:56.000 --> 00:19:56.010 align:start position:0% going out because the timing at which 00:19:56.010 --> 00:19:58.220 align:start position:0% going out because the timing at which the<00:19:56.220> packets<00:19:56.610> departure<00:19:57.390> from<00:19:57.600> the<00:19:57.750> mix<00:19:57.960> is 00:19:58.220 --> 00:19:58.230 align:start position:0% the packets departure from the mix is 00:19:58.230 --> 00:20:01.040 align:start position:0% the packets departure from the mix is not<00:19:58.620> related<00:19:59.370> to<00:19:59.610> their<00:19:59.880> arrival<00:20:00.150> times<00:20:00.690> and 00:20:01.040 --> 00:20:01.050 align:start position:0% not related to their arrival times and 00:20:01.050 --> 00:20:04.850 align:start position:0% not related to their arrival times and what<00:20:01.770> it<00:20:01.950> gives<00:20:02.580> like<00:20:03.270> in<00:20:03.630> the<00:20:03.870> big<00:20:04.050> picture<00:20:04.350> it 00:20:04.850 --> 00:20:04.860 align:start position:0% what it gives like in the big picture it 00:20:04.860 --> 00:20:07.670 align:start position:0% what it gives like in the big picture it increases<00:20:05.580> the<00:20:05.700> anonymity<00:20:06.300> set<00:20:06.690> because<00:20:07.470> in 00:20:07.670 --> 00:20:07.680 align:start position:0% increases the anonymity set because in 00:20:07.680 --> 00:20:09.710 align:start position:0% increases the anonymity set because in the<00:20:07.830> synchronized<00:20:08.430> mix<00:20:08.700> networks<00:20:09.210> you<00:20:09.540> have 00:20:09.710 --> 00:20:09.720 align:start position:0% the synchronized mix networks you have 00:20:09.720 --> 00:20:12.320 align:start position:0% the synchronized mix networks you have the<00:20:09.900> unlimited<00:20:10.290> set<00:20:10.890> of<00:20:11.190> the<00:20:11.640> size<00:20:11.910> of<00:20:12.180> how 00:20:12.320 --> 00:20:12.330 align:start position:0% the unlimited set of the size of how 00:20:12.330 --> 00:20:14.270 align:start position:0% the unlimited set of the size of how many<00:20:12.540> messages<00:20:12.750> you've<00:20:13.200> managed<00:20:13.560> to<00:20:13.830> gather 00:20:14.270 --> 00:20:14.280 align:start position:0% many messages you've managed to gather 00:20:14.280 --> 00:20:17.330 align:start position:0% many messages you've managed to gather during<00:20:14.730> the<00:20:14.880> run<00:20:15.030> here<00:20:15.930> because<00:20:16.620> everything 00:20:17.330 --> 00:20:17.340 align:start position:0% during the run here because everything 00:20:17.340 --> 00:20:19.850 align:start position:0% during the run here because everything works<00:20:17.490> in<00:20:17.760> a<00:20:17.790> continuous<00:20:18.330> manner<00:20:18.540> and<00:20:19.230> the 00:20:19.850 --> 00:20:19.860 align:start position:0% works in a continuous manner and the 00:20:19.860 --> 00:20:21.530 align:start position:0% works in a continuous manner and the exponential<00:20:20.340> distribution<00:20:20.760> is<00:20:21.150> known<00:20:21.360> to 00:20:21.530 --> 00:20:21.540 align:start position:0% exponential distribution is known to 00:20:21.540 --> 00:20:23.700 align:start position:0% exponential distribution is known to hell<00:20:21.840> you're<00:20:22.530> you're<00:20:23.070> under<00:20:23.370> limit 00:20:23.700 --> 00:20:23.710 align:start position:0% hell you're you're under limit 00:20:23.710 --> 00:20:26.100 align:start position:0% hell you're you're under limit it's<00:20:24.159> much<00:20:24.429> larger<00:20:24.760> because<00:20:25.210> you<00:20:25.750> actually 00:20:26.100 --> 00:20:26.110 align:start position:0% it's much larger because you actually 00:20:26.110 --> 00:20:28.350 align:start position:0% it's much larger because you actually have<00:20:26.440> to<00:20:26.770> consider<00:20:27.130> all<00:20:27.490> the<00:20:27.730> messages<00:20:28.179> which 00:20:28.350 --> 00:20:28.360 align:start position:0% have to consider all the messages which 00:20:28.360 --> 00:20:30.419 align:start position:0% have to consider all the messages which you<00:20:28.480> have<00:20:28.690> ever<00:20:29.080> seen<00:20:29.470> arriving<00:20:29.980> to<00:20:30.130> the<00:20:30.250> mix 00:20:30.419 --> 00:20:30.429 align:start position:0% you have ever seen arriving to the mix 00:20:30.429 --> 00:20:32.100 align:start position:0% you have ever seen arriving to the mix not<00:20:30.610> as<00:20:30.789> being<00:20:31.059> potentially<00:20:31.809> the<00:20:31.960> one 00:20:32.100 --> 00:20:32.110 align:start position:0% not as being potentially the one 00:20:32.110 --> 00:20:37.350 align:start position:0% not as being potentially the one departure<00:20:33.990> and<00:20:34.990> the<00:20:35.799> last<00:20:36.159> thing<00:20:36.490> about<00:20:37.029> the 00:20:37.350 --> 00:20:37.360 align:start position:0% departure and the last thing about the 00:20:37.360 --> 00:20:40.860 align:start position:0% departure and the last thing about the new<00:20:37.779> swing<00:20:38.110> set<00:20:38.140> is<00:20:38.590> that<00:20:39.510> you<00:20:40.510> know<00:20:40.600> it's<00:20:40.779> very 00:20:40.860 --> 00:20:40.870 align:start position:0% new swing set is that you know it's very 00:20:40.870 --> 00:20:42.360 align:start position:0% new swing set is that you know it's very intuitive<00:20:41.289> that<00:20:41.649> when<00:20:41.860> we<00:20:41.950> are<00:20:42.070> talking<00:20:42.340> about 00:20:42.360 --> 00:20:42.370 align:start position:0% intuitive that when we are talking about 00:20:42.370 --> 00:20:44.789 align:start position:0% intuitive that when we are talking about anonymity<00:20:43.059> the<00:20:43.360> larger<00:20:43.809> the<00:20:44.020> group<00:20:44.049> of<00:20:44.440> people 00:20:44.789 --> 00:20:44.799 align:start position:0% anonymity the larger the group of people 00:20:44.799 --> 00:20:47.310 align:start position:0% anonymity the larger the group of people among<00:20:45.130> which<00:20:45.429> you're<00:20:45.730> anonymous<00:20:46.210> the<00:20:47.049> better 00:20:47.310 --> 00:20:47.320 align:start position:0% among which you're anonymous the better 00:20:47.320 --> 00:20:49.710 align:start position:0% among which you're anonymous the better is<00:20:47.529> your<00:20:47.649> anonymity<00:20:48.220> so<00:20:49.000> mix<00:20:49.299> that<00:20:49.419> works 00:20:49.710 --> 00:20:49.720 align:start position:0% is your anonymity so mix that works 00:20:49.720 --> 00:20:52.980 align:start position:0% is your anonymity so mix that works better<00:20:49.960> often<00:20:50.200> use<00:20:50.590> covering<00:20:51.279> traffic<00:20:51.990> but 00:20:52.980 --> 00:20:52.990 align:start position:0% better often use covering traffic but 00:20:52.990 --> 00:20:54.330 align:start position:0% better often use covering traffic but the<00:20:53.080> problem<00:20:53.409> with<00:20:53.529> the<00:20:53.620> traditional<00:20:54.190> mix 00:20:54.330 --> 00:20:54.340 align:start position:0% the problem with the traditional mix 00:20:54.340 --> 00:20:56.399 align:start position:0% the problem with the traditional mix network<00:20:54.700> design<00:20:55.059> was<00:20:55.330> that<00:20:55.570> this<00:20:56.020> covered 00:20:56.399 --> 00:20:56.409 align:start position:0% network design was that this covered 00:20:56.409 --> 00:20:58.320 align:start position:0% network design was that this covered traffic<00:20:56.799> usually<00:20:57.309> required<00:20:57.760> a<00:20:57.940> lot<00:20:58.149> of 00:20:58.320 --> 00:20:58.330 align:start position:0% traffic usually required a lot of 00:20:58.330 --> 00:21:01.620 align:start position:0% traffic usually required a lot of bandwidth<00:20:58.840> and<00:20:59.110> that's<00:21:00.039> why<00:21:00.220> in<00:21:00.580> them<00:21:01.059> and<00:21:01.419> in 00:21:01.620 --> 00:21:01.630 align:start position:0% bandwidth and that's why in them and in 00:21:01.630 --> 00:21:03.510 align:start position:0% bandwidth and that's why in them and in the<00:21:01.750> dim<00:21:01.899> sum<00:21:02.020> example<00:21:02.620> we're<00:21:02.919> using<00:21:02.950> a 00:21:03.510 --> 00:21:03.520 align:start position:0% the dim sum example we're using a 00:21:03.520 --> 00:21:05.970 align:start position:0% the dim sum example we're using a tunable<00:21:03.940> covered<00:21:04.750> traffic<00:21:05.200> and<00:21:05.409> Chernobyl 00:21:05.970 --> 00:21:05.980 align:start position:0% tunable covered traffic and Chernobyl 00:21:05.980 --> 00:21:07.950 align:start position:0% tunable covered traffic and Chernobyl means<00:21:06.190> that<00:21:06.460> when<00:21:07.059> the<00:21:07.179> volume<00:21:07.450> of<00:21:07.720> real 00:21:07.950 --> 00:21:07.960 align:start position:0% means that when the volume of real 00:21:07.960 --> 00:21:10.049 align:start position:0% means that when the volume of real traffic<00:21:08.380> increases<00:21:08.919> in<00:21:09.070> the<00:21:09.159> mix<00:21:09.340> network<00:21:09.760> you 00:21:10.049 --> 00:21:10.059 align:start position:0% traffic increases in the mix network you 00:21:10.059 --> 00:21:11.880 align:start position:0% traffic increases in the mix network you can<00:21:10.240> tune<00:21:10.570> down<00:21:10.840> the<00:21:11.140> amount<00:21:11.440> of<00:21:11.529> common 00:21:11.880 --> 00:21:11.890 align:start position:0% can tune down the amount of common 00:21:11.890 --> 00:21:13.769 align:start position:0% can tune down the amount of common traffic<00:21:12.100> which<00:21:12.370> you're<00:21:12.580> using<00:21:12.610> and<00:21:13.510> vice 00:21:13.769 --> 00:21:13.779 align:start position:0% traffic which you're using and vice 00:21:13.779 --> 00:21:16.230 align:start position:0% traffic which you're using and vice versa<00:21:14.289> if<00:21:14.529> the<00:21:14.559> amount<00:21:15.309> of<00:21:15.399> real<00:21:15.669> traffic<00:21:15.940> is 00:21:16.230 --> 00:21:16.240 align:start position:0% versa if the amount of real traffic is 00:21:16.240 --> 00:21:18.210 align:start position:0% versa if the amount of real traffic is dropping<00:21:16.630> and<00:21:16.840> the<00:21:17.649> type<00:21:17.830> of<00:21:17.860> covert 00:21:18.210 --> 00:21:18.220 align:start position:0% dropping and the type of covert 00:21:18.220 --> 00:21:20.370 align:start position:0% dropping and the type of covert particles<00:21:18.820> were<00:21:19.000> using<00:21:19.360> is<00:21:19.539> called<00:21:19.870> a<00:21:20.080> loop 00:21:20.370 --> 00:21:20.380 align:start position:0% particles were using is called a loop 00:21:20.380 --> 00:21:22.620 align:start position:0% particles were using is called a loop covered<00:21:20.770> traffic<00:21:21.220> alone<00:21:21.610> means<00:21:22.029> that<00:21:22.299> the 00:21:22.620 --> 00:21:22.630 align:start position:0% covered traffic alone means that the 00:21:22.630 --> 00:21:24.600 align:start position:0% covered traffic alone means that the sender<00:21:23.110> and<00:21:23.350> the<00:21:23.409> recipient<00:21:23.770> of<00:21:24.100> this<00:21:24.220> packet 00:21:24.600 --> 00:21:24.610 align:start position:0% sender and the recipient of this packet 00:21:24.610 --> 00:21:27.539 align:start position:0% sender and the recipient of this packet is<00:21:24.760> the<00:21:24.970> same<00:21:25.179> person<00:21:25.690> and<00:21:26.020> both<00:21:26.830> the<00:21:27.070> clients 00:21:27.539 --> 00:21:27.549 align:start position:0% is the same person and both the clients 00:21:27.549 --> 00:21:28.860 align:start position:0% is the same person and both the clients and<00:21:27.669> the<00:21:27.820> mix<00:21:28.059> notes<00:21:28.330> are<00:21:28.570> sending 00:21:28.860 --> 00:21:28.870 align:start position:0% and the mix notes are sending 00:21:28.870 --> 00:21:30.960 align:start position:0% and the mix notes are sending blood-covered<00:21:29.380> traffic<00:21:30.010> following<00:21:30.850> the 00:21:30.960 --> 00:21:30.970 align:start position:0% blood-covered traffic following the 00:21:30.970 --> 00:21:33.870 align:start position:0% blood-covered traffic following the Poisson<00:21:31.419> distribution<00:21:31.830> this<00:21:32.850> ensures<00:21:33.850> that 00:21:33.870 --> 00:21:33.880 align:start position:0% Poisson distribution this ensures that 00:21:33.880 --> 00:21:36.690 align:start position:0% Poisson distribution this ensures that the<00:21:34.330> potheads<00:21:34.960> the<00:21:35.169> real<00:21:35.380> ones<00:21:35.679> and<00:21:35.919> the<00:21:36.520> loop 00:21:36.690 --> 00:21:36.700 align:start position:0% the potheads the real ones and the loop 00:21:36.700 --> 00:21:38.730 align:start position:0% the potheads the real ones and the loop packets<00:21:37.270> are<00:21:37.450> very<00:21:37.809> nicely<00:21:38.020> mixed<00:21:38.590> together 00:21:38.730 --> 00:21:38.740 align:start position:0% packets are very nicely mixed together 00:21:38.740 --> 00:21:41.130 align:start position:0% packets are very nicely mixed together so<00:21:39.279> the<00:21:39.429> adversary<00:21:39.970> can<00:21:40.179> not<00:21:40.419> distinguish 00:21:41.130 --> 00:21:41.140 align:start position:0% so the adversary can not distinguish 00:21:41.140 --> 00:21:43.260 align:start position:0% so the adversary can not distinguish looking<00:21:41.890> at<00:21:42.010> some<00:21:42.220> sample<00:21:42.610> of<00:21:42.700> traffic 00:21:43.260 --> 00:21:43.270 align:start position:0% looking at some sample of traffic 00:21:43.270 --> 00:21:45.870 align:start position:0% looking at some sample of traffic whether<00:21:43.750> he<00:21:44.380> sees<00:21:44.590> real<00:21:44.830> messages<00:21:45.370> or<00:21:45.700> loop 00:21:45.870 --> 00:21:45.880 align:start position:0% whether he sees real messages or loop 00:21:45.880 --> 00:21:49.110 align:start position:0% whether he sees real messages or loop messages<00:21:46.450> and<00:21:47.440> so<00:21:47.590> on<00:21:47.740> but<00:21:48.700> the<00:21:48.850> local 00:21:49.110 --> 00:21:49.120 align:start position:0% messages and so on but the local 00:21:49.120 --> 00:21:50.940 align:start position:0% messages and so on but the local messages<00:21:49.240> they<00:21:49.630> also<00:21:49.779> have<00:21:50.140> another<00:21:50.470> burgnik 00:21:50.940 --> 00:21:50.950 align:start position:0% messages they also have another burgnik 00:21:50.950 --> 00:21:53.490 align:start position:0% messages they also have another burgnik advantage<00:21:51.580> they<00:21:51.909> allow<00:21:52.270> to<00:21:52.570> detect<00:21:53.289> and 00:21:53.490 --> 00:21:53.500 align:start position:0% advantage they allow to detect and 00:21:53.500 --> 00:21:56.549 align:start position:0% advantage they allow to detect and prevent<00:21:53.529> active<00:21:54.399> attacks<00:21:54.840> in<00:21:55.840> which<00:21:56.140> either 00:21:56.549 --> 00:21:56.559 align:start position:0% prevent active attacks in which either 00:21:56.559 --> 00:21:58.919 align:start position:0% prevent active attacks in which either malicious<00:21:57.190> mixes<00:21:57.669> or<00:21:58.029> malicious<00:21:58.750> adversary 00:21:58.919 --> 00:21:58.929 align:start position:0% malicious mixes or malicious adversary 00:21:58.929 --> 00:22:01.799 align:start position:0% malicious mixes or malicious adversary can<00:21:59.799> block<00:22:00.130> or<00:22:00.399> drop<00:22:00.669> some<00:22:01.000> of<00:22:01.120> the<00:22:01.240> packets<00:22:01.659> in 00:22:01.799 --> 00:22:01.809 align:start position:0% can block or drop some of the packets in 00:22:01.809 --> 00:22:04.350 align:start position:0% can block or drop some of the packets in the<00:22:01.870> network<00:22:02.049> this<00:22:02.980> are<00:22:03.370> properties<00:22:03.820> which 00:22:04.350 --> 00:22:04.360 align:start position:0% the network this are properties which 00:22:04.360 --> 00:22:06.720 align:start position:0% the network this are properties which were<00:22:04.510> not<00:22:04.779> in<00:22:05.140> the<00:22:05.590> traditional<00:22:05.799> mix<00:22:06.340> at<00:22:06.520> work 00:22:06.720 --> 00:22:06.730 align:start position:0% were not in the traditional mix at work 00:22:06.730 --> 00:22:10.460 align:start position:0% were not in the traditional mix at work designs<00:22:07.090> so<00:22:08.049> it's<00:22:08.200> a<00:22:08.320> very<00:22:08.620> big<00:22:08.830> advantage 00:22:10.460 --> 00:22:10.470 align:start position:0% designs so it's a very big advantage 00:22:10.470 --> 00:22:14.100 align:start position:0% designs so it's a very big advantage okay<00:22:11.470> just<00:22:12.460> to<00:22:12.610> wrap<00:22:12.789> up<00:22:12.940> about<00:22:13.299> the<00:22:13.480> names<00:22:13.720> mix 00:22:14.100 --> 00:22:14.110 align:start position:0% okay just to wrap up about the names mix 00:22:14.110 --> 00:22:16.860 align:start position:0% okay just to wrap up about the names mix that<00:22:14.350> what<00:22:14.649> is<00:22:14.890> like<00:22:15.130> the<00:22:15.340> key<00:22:16.149> takeaways<00:22:16.720> you 00:22:16.860 --> 00:22:16.870 align:start position:0% that what is like the key takeaways you 00:22:16.870 --> 00:22:19.320 align:start position:0% that what is like the key takeaways you should<00:22:17.020> remember<00:22:17.320> is<00:22:17.710> that<00:22:18.070> we<00:22:18.640> have<00:22:18.880> a<00:22:18.909> mixed 00:22:19.320 --> 00:22:19.330 align:start position:0% should remember is that we have a mixed 00:22:19.330 --> 00:22:21.360 align:start position:0% should remember is that we have a mixed network<00:22:19.750> which<00:22:20.169> has<00:22:20.200> a 00:22:21.360 --> 00:22:21.370 align:start position:0% network which has a 00:22:21.370 --> 00:22:23.639 align:start position:0% network which has a anonymity<00:22:22.090> versus<00:22:22.600> performance<00:22:22.809> trade-off 00:22:23.639 --> 00:22:23.649 align:start position:0% anonymity versus performance trade-off 00:22:23.649 --> 00:22:26.070 align:start position:0% anonymity versus performance trade-off the<00:22:23.890> network<00:22:24.250> scales<00:22:24.669> very<00:22:24.789> well<00:22:25.090> we<00:22:25.899> can 00:22:26.070 --> 00:22:26.080 align:start position:0% the network scales very well we can 00:22:26.080 --> 00:22:29.130 align:start position:0% the network scales very well we can adjust<00:22:26.520> the<00:22:27.520> latency<00:22:28.179> which<00:22:28.480> we<00:22:28.720> need<00:22:28.870> in<00:22:29.020> our 00:22:29.130 --> 00:22:29.140 align:start position:0% adjust the latency which we need in our 00:22:29.140 --> 00:22:31.320 align:start position:0% adjust the latency which we need in our system<00:22:29.799> depending<00:22:30.520> on<00:22:30.640> the<00:22:30.760> amount<00:22:30.970> and 00:22:31.320 --> 00:22:31.330 align:start position:0% system depending on the amount and 00:22:31.330 --> 00:22:35.340 align:start position:0% system depending on the amount and volume<00:22:31.720> of<00:22:31.870> traffic<00:22:32.110> which<00:22:32.470> we<00:22:32.649> have<00:22:33.149> we<00:22:34.350> can 00:22:35.340 --> 00:22:35.350 align:start position:0% volume of traffic which we have we can 00:22:35.350 --> 00:22:39.990 align:start position:0% volume of traffic which we have we can detect<00:22:36.220> and<00:22:36.580> resist<00:22:36.909> active<00:22:37.480> attacks<00:22:37.840> and<00:22:39.000> so 00:22:39.990 --> 00:22:40.000 align:start position:0% detect and resist active attacks and so 00:22:40.000 --> 00:22:44.669 align:start position:0% detect and resist active attacks and so that's<00:22:40.179> about<00:22:40.299> mixels<00:22:43.350> thanks<00:22:44.350> Anya<00:22:44.500> so 00:22:44.669 --> 00:22:44.679 align:start position:0% that's about mixels thanks Anya so 00:22:44.679 --> 00:22:47.310 align:start position:0% that's about mixels thanks Anya so that's<00:22:44.860> half<00:22:45.159> of<00:22:45.250> our<00:22:45.429> system<00:22:45.909> and<00:22:46.299> by<00:22:47.110> the<00:22:47.169> way 00:22:47.310 --> 00:22:47.320 align:start position:0% that's half of our system and by the way 00:22:47.320 --> 00:22:49.799 align:start position:0% that's half of our system and by the way we're<00:22:47.500> going<00:22:47.590> to<00:22:47.649> try<00:22:47.980> to<00:22:48.039> do<00:22:48.309> well<00:22:49.179> we're 00:22:49.799 --> 00:22:49.809 align:start position:0% we're going to try to do well we're 00:22:49.809 --> 00:22:51.330 align:start position:0% we're going to try to do well we're gonna<00:22:49.899> succeed<00:22:50.140> in<00:22:50.440> doing<00:22:50.559> a<00:22:50.710> demo<00:22:51.010> because<00:22:51.250> we 00:22:51.330 --> 00:22:51.340 align:start position:0% gonna succeed in doing a demo because we 00:22:51.340 --> 00:22:52.830 align:start position:0% gonna succeed in doing a demo because we don't<00:22:51.490> have<00:22:51.640> any<00:22:51.789> dependencies<00:22:52.299> on<00:22:52.450> internet 00:22:52.830 --> 00:22:52.840 align:start position:0% don't have any dependencies on internet 00:22:52.840 --> 00:22:54.840 align:start position:0% don't have any dependencies on internet a<00:22:53.020> shuttle<00:22:53.350> movie<00:22:53.649> last<00:22:54.250> night<00:22:54.429> in<00:22:54.640> my<00:22:54.730> hotel 00:22:54.840 --> 00:22:54.850 align:start position:0% a shuttle movie last night in my hotel 00:22:54.850 --> 00:22:55.230 align:start position:0% a shuttle movie last night in my hotel room 00:22:55.230 --> 00:22:55.240 align:start position:0% room 00:22:55.240 --> 00:22:57.269 align:start position:0% room so<00:22:55.659> we'll<00:22:56.260> actually<00:22:56.409> be<00:22:56.559> able<00:22:56.620> to<00:22:56.770> see<00:22:56.950> some<00:22:57.190> of 00:22:57.269 --> 00:22:57.279 align:start position:0% so we'll actually be able to see some of 00:22:57.279 --> 00:22:59.460 align:start position:0% so we'll actually be able to see some of the<00:22:57.340> stuff<00:22:57.520> happening<00:22:57.909> so<00:22:58.140> we've<00:22:59.140> built<00:22:59.320> a 00:22:59.460 --> 00:22:59.470 align:start position:0% the stuff happening so we've built a 00:22:59.470 --> 00:23:01.320 align:start position:0% the stuff happening so we've built a small<00:22:59.590> chat<00:23:00.010> application<00:23:00.640> just<00:23:00.880> as<00:23:01.000> a<00:23:01.029> kind<00:23:01.210> of 00:23:01.320 --> 00:23:01.330 align:start position:0% small chat application just as a kind of 00:23:01.330 --> 00:23:04.019 align:start position:0% small chat application just as a kind of tester<00:23:01.890> and<00:23:02.890> we<00:23:03.159> you'll<00:23:03.549> be<00:23:03.669> able<00:23:03.730> to<00:23:03.880> see 00:23:04.019 --> 00:23:04.029 align:start position:0% tester and we you'll be able to see 00:23:04.029 --> 00:23:06.539 align:start position:0% tester and we you'll be able to see messages<00:23:04.899> going<00:23:05.350> into<00:23:05.649> the<00:23:05.710> mix<00:23:05.890> net<00:23:06.100> going 00:23:06.539 --> 00:23:06.549 align:start position:0% messages going into the mix net going 00:23:06.549 --> 00:23:07.919 align:start position:0% messages going into the mix net going between<00:23:06.700> two<00:23:07.029> terminals<00:23:07.450> as<00:23:07.600> a<00:23:07.630> kind<00:23:07.870> of 00:23:07.919 --> 00:23:07.929 align:start position:0% between two terminals as a kind of 00:23:07.929 --> 00:23:11.190 align:start position:0% between two terminals as a kind of simple<00:23:08.710> example<00:23:09.450> but<00:23:10.450> you<00:23:10.600> could<00:23:10.750> use<00:23:10.929> mix 00:23:11.190 --> 00:23:11.200 align:start position:0% simple example but you could use mix 00:23:11.200 --> 00:23:13.049 align:start position:0% simple example but you could use mix Network<00:23:11.679> many<00:23:11.919> more<00:23:12.130> things<00:23:12.370> than<00:23:12.490> chat<00:23:12.850> we 00:23:13.049 --> 00:23:13.059 align:start position:0% Network many more things than chat we 00:23:13.059 --> 00:23:15.630 align:start position:0% Network many more things than chat we can<00:23:13.179> use<00:23:13.360> it<00:23:13.510> to<00:23:13.539> pretty<00:23:14.500> much<00:23:14.620> anonymize<00:23:15.190> any 00:23:15.630 --> 00:23:15.640 align:start position:0% can use it to pretty much anonymize any 00:23:15.640 --> 00:23:17.760 align:start position:0% can use it to pretty much anonymize any of<00:23:16.210> your<00:23:16.360> blockchain<00:23:16.809> transactions<00:23:17.440> any<00:23:17.710> of 00:23:17.760 --> 00:23:17.770 align:start position:0% of your blockchain transactions any of 00:23:17.770 --> 00:23:20.010 align:start position:0% of your blockchain transactions any of your<00:23:17.890> crypto<00:23:18.130> currency<00:23:18.460> transactions<00:23:19.059> or 00:23:20.010 --> 00:23:20.020 align:start position:0% your crypto currency transactions or 00:23:20.020 --> 00:23:23.220 align:start position:0% your crypto currency transactions or anything<00:23:20.409> else<00:23:20.649> for<00:23:20.860> that<00:23:20.890> matter<00:23:22.049> yeah<00:23:23.049> the 00:23:23.220 --> 00:23:23.230 align:start position:0% anything else for that matter yeah the 00:23:23.230 --> 00:23:25.769 align:start position:0% anything else for that matter yeah the second<00:23:23.590> part<00:23:23.890> of<00:23:23.980> our<00:23:24.100> system<00:23:24.340> is<00:23:24.700> a<00:23:25.120> system<00:23:25.659> of 00:23:25.769 --> 00:23:25.779 align:start position:0% second part of our system is a system of 00:23:25.779 --> 00:23:28.440 align:start position:0% second part of our system is a system of privacy<00:23:26.289> preserving<00:23:26.559> credentials<00:23:27.549> so<00:23:28.029> these 00:23:28.440 --> 00:23:28.450 align:start position:0% privacy preserving credentials so these 00:23:28.450 --> 00:23:31.080 align:start position:0% privacy preserving credentials so these are<00:23:28.630> working<00:23:29.529> at<00:23:29.649> different<00:23:29.860> layers<00:23:30.399> here<00:23:30.610> a 00:23:31.080 --> 00:23:31.090 align:start position:0% are working at different layers here a 00:23:31.090 --> 00:23:33.720 align:start position:0% are working at different layers here a mixed<00:23:31.539> net<00:23:31.690> defends<00:23:32.289> you<00:23:32.440> at<00:23:33.159> the<00:23:33.399> network 00:23:33.720 --> 00:23:33.730 align:start position:0% mixed net defends you at the network 00:23:33.730 --> 00:23:37.169 align:start position:0% mixed net defends you at the network layer<00:23:34.620> whereas<00:23:35.620> the<00:23:35.919> credentials<00:23:36.880> that<00:23:36.970> we 00:23:37.169 --> 00:23:37.179 align:start position:0% layer whereas the credentials that we 00:23:37.179 --> 00:23:39.000 align:start position:0% layer whereas the credentials that we have<00:23:37.390> can<00:23:37.659> defend<00:23:37.960> you<00:23:38.110> at<00:23:38.350> the<00:23:38.500> layer<00:23:38.679> of<00:23:38.860> your 00:23:39.000 --> 00:23:39.010 align:start position:0% have can defend you at the layer of your 00:23:39.010 --> 00:23:43.350 align:start position:0% have can defend you at the layer of your transactions<00:23:39.640> or<00:23:39.820> your<00:23:40.059> block<00:23:40.240> chain<00:23:41.039> so<00:23:42.360> the 00:23:43.350 --> 00:23:43.360 align:start position:0% transactions or your block chain so the 00:23:43.360 --> 00:23:45.570 align:start position:0% transactions or your block chain so the mix<00:23:43.539> that<00:23:43.690> protects<00:23:44.200> your<00:23:44.529> IP<00:23:44.860> traffic<00:23:45.250> as 00:23:45.570 --> 00:23:45.580 align:start position:0% mix that protects your IP traffic as 00:23:45.580 --> 00:23:46.680 align:start position:0% mix that protects your IP traffic as it's<00:23:45.730> traveling<00:23:46.090> across<00:23:46.299> the<00:23:46.419> element 00:23:46.680 --> 00:23:46.690 align:start position:0% it's traveling across the element 00:23:46.690 --> 00:23:48.690 align:start position:0% it's traveling across the element unprotected<00:23:47.559> wilds<00:23:47.919> of<00:23:48.010> the<00:23:48.070> internet<00:23:48.490> and 00:23:48.690 --> 00:23:48.700 align:start position:0% unprotected wilds of the internet and 00:23:48.700 --> 00:23:50.880 align:start position:0% unprotected wilds of the internet and the<00:23:49.270> privacy<00:23:49.720> preserving<00:23:49.960> credentials<00:23:50.679> allow 00:23:50.880 --> 00:23:50.890 align:start position:0% the privacy preserving credentials allow 00:23:50.890 --> 00:23:53.789 align:start position:0% the privacy preserving credentials allow you<00:23:50.950> to<00:23:51.279> code<00:23:51.730> cryptographic<00:23:52.179> claims<00:23:52.750> and<00:23:53.620> use 00:23:53.789 --> 00:23:53.799 align:start position:0% you to code cryptographic claims and use 00:23:53.799 --> 00:23:57.450 align:start position:0% you to code cryptographic claims and use them<00:23:54.010> so<00:23:54.190> we're<00:23:54.730> using<00:23:54.970> a<00:23:56.100> signature<00:23:57.100> scheme 00:23:57.450 --> 00:23:57.460 align:start position:0% them so we're using a signature scheme 00:23:57.460 --> 00:24:00.120 align:start position:0% them so we're using a signature scheme called<00:23:57.700> coconut<00:23:58.240> so<00:23:58.630> what<00:23:58.809> is<00:23:58.929> coconut<00:23:59.380> well 00:24:00.120 --> 00:24:00.130 align:start position:0% called coconut so what is coconut well 00:24:00.130 --> 00:24:03.690 align:start position:0% called coconut so what is coconut well coconut<00:24:01.029> is<00:24:01.240> a<00:24:01.539> signature<00:24:01.929> scheme<00:24:02.289> and<00:24:02.590> as<00:24:03.370> you 00:24:03.690 --> 00:24:03.700 align:start position:0% coconut is a signature scheme and as you 00:24:03.700 --> 00:24:06.389 align:start position:0% coconut is a signature scheme and as you may<00:24:03.820> know<00:24:04.000> all<00:24:04.270> signature<00:24:04.750> schemes<00:24:05.020> have<00:24:05.399> at 00:24:06.389 --> 00:24:06.399 align:start position:0% may know all signature schemes have at 00:24:06.399 --> 00:24:07.860 align:start position:0% may know all signature schemes have at least<00:24:06.640> these<00:24:06.820> three<00:24:07.090> algorithms<00:24:07.330> that<00:24:07.779> you 00:24:07.860 --> 00:24:07.870 align:start position:0% least these three algorithms that you 00:24:07.870 --> 00:24:09.779 align:start position:0% least these three algorithms that you need<00:24:08.110> to<00:24:08.200> be<00:24:08.260> able<00:24:08.320> to<00:24:08.440> generate<00:24:08.710> your<00:24:08.919> keys<00:24:09.130> be 00:24:09.779 --> 00:24:09.789 align:start position:0% need to be able to generate your keys be 00:24:09.789 --> 00:24:12.630 align:start position:0% need to be able to generate your keys be able<00:24:10.029> to<00:24:10.179> verify<00:24:10.649> a<00:24:11.649> signature<00:24:12.250> that<00:24:12.520> you 00:24:12.630 --> 00:24:12.640 align:start position:0% able to verify a signature that you 00:24:12.640 --> 00:24:14.460 align:start position:0% able to verify a signature that you received<00:24:13.000> and<00:24:13.179> you<00:24:13.600> somebody<00:24:14.110> has<00:24:14.260> to<00:24:14.350> be<00:24:14.409> able 00:24:14.460 --> 00:24:14.470 align:start position:0% received and you somebody has to be able 00:24:14.470 --> 00:24:17.039 align:start position:0% received and you somebody has to be able to<00:24:14.590> sign<00:24:14.830> okay<00:24:15.490> so<00:24:15.640> given<00:24:15.850> given<00:24:16.570> the<00:24:16.690> public 00:24:17.039 --> 00:24:17.049 align:start position:0% to sign okay so given given the public 00:24:17.049 --> 00:24:18.810 align:start position:0% to sign okay so given given the public key<00:24:17.260> of<00:24:17.289> the<00:24:17.730> first 00:24:18.810 --> 00:24:18.820 align:start position:0% key of the first 00:24:18.820 --> 00:24:20.039 align:start position:0% key of the first that<00:24:18.940> you<00:24:19.029> want<00:24:19.240> to<00:24:19.330> assign<00:24:19.480> a<00:24:19.539> message<00:24:19.840> for 00:24:20.039 --> 00:24:20.049 align:start position:0% that you want to assign a message for 00:24:20.049 --> 00:24:21.810 align:start position:0% that you want to assign a message for you<00:24:20.529> should<00:24:20.679> be<00:24:20.799> able<00:24:20.860> to<00:24:21.009> assign<00:24:21.429> that<00:24:21.610> thing 00:24:21.810 --> 00:24:21.820 align:start position:0% you should be able to assign that thing 00:24:21.820 --> 00:24:24.120 align:start position:0% you should be able to assign that thing and<00:24:22.029> it's<00:24:22.389> anybody<00:24:22.809> who<00:24:22.929> has<00:24:23.080> the<00:24:23.230> public<00:24:23.799> key 00:24:24.120 --> 00:24:24.130 align:start position:0% and it's anybody who has the public key 00:24:24.130 --> 00:24:25.590 align:start position:0% and it's anybody who has the public key that<00:24:24.159> was<00:24:24.820> signed<00:24:25.059> which<00:24:25.210> they<00:24:25.330> should<00:24:25.509> be 00:24:25.590 --> 00:24:25.600 align:start position:0% that was signed which they should be 00:24:25.600 --> 00:24:27.419 align:start position:0% that was signed which they should be able<00:24:25.659> to<00:24:25.779> verify<00:24:25.990> right<00:24:26.590> so<00:24:27.100> everybody's 00:24:27.419 --> 00:24:27.429 align:start position:0% able to verify right so everybody's 00:24:27.429 --> 00:24:29.039 align:start position:0% able to verify right so everybody's pretty<00:24:27.700> much<00:24:27.909> familiar<00:24:28.059> with<00:24:28.389> these<00:24:28.509> things 00:24:29.039 --> 00:24:29.049 align:start position:0% pretty much familiar with these things 00:24:29.049 --> 00:24:30.600 align:start position:0% pretty much familiar with these things who<00:24:29.679> a<00:24:29.710> lot<00:24:30.009> of<00:24:30.130> know<00:24:30.220> that<00:24:30.340> you<00:24:30.429> know<00:24:30.490> it's 00:24:30.600 --> 00:24:30.610 align:start position:0% who a lot of know that you know it's 00:24:30.610 --> 00:24:31.110 align:start position:0% who a lot of know that you know it's very<00:24:30.759> good 00:24:31.110 --> 00:24:31.120 align:start position:0% very good 00:24:31.120 --> 00:24:34.529 align:start position:0% very good cool<00:24:31.509> so<00:24:32.259> name<00:24:32.500> signatures<00:24:33.009> are<00:24:33.389> it<00:24:34.389> is<00:24:34.509> a 00:24:34.529 --> 00:24:34.539 align:start position:0% cool so name signatures are it is a 00:24:34.539 --> 00:24:36.360 align:start position:0% cool so name signatures are it is a signature<00:24:34.870> scheme<00:24:35.200> but<00:24:35.740> we<00:24:35.889> have<00:24:36.039> several 00:24:36.360 --> 00:24:36.370 align:start position:0% signature scheme but we have several 00:24:36.370 --> 00:24:38.430 align:start position:0% signature scheme but we have several additional<00:24:37.120> properties<00:24:37.750> so<00:24:38.110> the<00:24:38.200> first 00:24:38.430 --> 00:24:38.440 align:start position:0% additional properties so the first 00:24:38.440 --> 00:24:40.680 align:start position:0% additional properties so the first property<00:24:38.860> that<00:24:38.950> we've<00:24:39.220> had<00:24:39.429> to<00:24:40.000> the<00:24:40.419> server 00:24:40.680 --> 00:24:40.690 align:start position:0% property that we've had to the server 00:24:40.690 --> 00:24:43.620 align:start position:0% property that we've had to the server normal<00:24:41.080> 3<00:24:41.370> we<00:24:42.370> have<00:24:42.490> blind<00:24:42.789> signatures<00:24:43.419> or 00:24:43.620 --> 00:24:43.630 align:start position:0% normal 3 we have blind signatures or 00:24:43.630 --> 00:24:45.930 align:start position:0% normal 3 we have blind signatures or blind<00:24:43.990> issuance<00:24:44.799> this<00:24:45.250> do<00:24:45.429> people<00:24:45.700> know<00:24:45.820> what 00:24:45.930 --> 00:24:45.940 align:start position:0% blind issuance this do people know what 00:24:45.940 --> 00:24:48.960 align:start position:0% blind issuance this do people know what that<00:24:45.970> means<00:24:47.009> some<00:24:48.009> people<00:24:48.190> not<00:24:48.730> everybody 00:24:48.960 --> 00:24:48.970 align:start position:0% that means some people not everybody 00:24:48.970 --> 00:24:49.860 align:start position:0% that means some people not everybody okay<00:24:49.450> cool 00:24:49.860 --> 00:24:49.870 align:start position:0% okay cool 00:24:49.870 --> 00:24:52.409 align:start position:0% okay cool so<00:24:50.139> again<00:24:50.980> david<00:24:51.399> chung<00:24:51.580> cryptographic 00:24:52.409 --> 00:24:52.419 align:start position:0% so again david chung cryptographic 00:24:52.419 --> 00:24:55.289 align:start position:0% so again david chung cryptographic genius<00:24:52.929> invented<00:24:53.529> blind<00:24:53.740> signatures<00:24:54.299> which 00:24:55.289 --> 00:24:55.299 align:start position:0% genius invented blind signatures which 00:24:55.299 --> 00:24:56.789 align:start position:0% genius invented blind signatures which have<00:24:55.509> some<00:24:55.750> additional<00:24:55.960> properties<00:24:56.649> and 00:24:56.789 --> 00:24:56.799 align:start position:0% have some additional properties and 00:24:56.799 --> 00:24:59.730 align:start position:0% have some additional properties and functions<00:24:57.269> let's<00:24:58.269> take<00:24:58.570> a<00:24:58.600> fictional<00:24:59.230> ecash 00:24:59.730 --> 00:24:59.740 align:start position:0% functions let's take a fictional ecash 00:24:59.740 --> 00:25:02.340 align:start position:0% functions let's take a fictional ecash scheme<00:25:00.129> just<00:25:00.429> to<00:25:00.519> kind<00:25:00.879> of<00:25:00.909> use<00:25:01.690> an<00:25:01.809> example<00:25:02.259> to 00:25:02.340 --> 00:25:02.350 align:start position:0% scheme just to kind of use an example to 00:25:02.350 --> 00:25:03.539 align:start position:0% scheme just to kind of use an example to try<00:25:02.409> to<00:25:02.559> walk<00:25:02.830> through<00:25:03.100> what<00:25:03.309> a<00:25:03.340> blind 00:25:03.539 --> 00:25:03.549 align:start position:0% try to walk through what a blind 00:25:03.549 --> 00:25:05.669 align:start position:0% try to walk through what a blind signature<00:25:04.000> is<00:25:04.149> so<00:25:04.570> i'm<00:25:05.169> going<00:25:05.259> to<00:25:05.320> create<00:25:05.620> a 00:25:05.669 --> 00:25:05.679 align:start position:0% signature is so i'm going to create a 00:25:05.679 --> 00:25:08.009 align:start position:0% signature is so i'm going to create a cryptographic<00:25:06.070> claim<00:25:06.610> so<00:25:07.600> a<00:25:07.629> piece<00:25:07.870> of 00:25:08.009 --> 00:25:08.019 align:start position:0% cryptographic claim so a piece of 00:25:08.019 --> 00:25:10.200 align:start position:0% cryptographic claim so a piece of cryptographic<00:25:08.320> material<00:25:09.070> that<00:25:09.639> basically 00:25:10.200 --> 00:25:10.210 align:start position:0% cryptographic material that basically 00:25:10.210 --> 00:25:12.539 align:start position:0% cryptographic material that basically says<00:25:10.649> what<00:25:11.649> I<00:25:11.710> want<00:25:11.919> to<00:25:11.980> end<00:25:12.100> up<00:25:12.220> with<00:25:12.340> is<00:25:12.490> a 00:25:12.539 --> 00:25:12.549 align:start position:0% says what I want to end up with is a 00:25:12.549 --> 00:25:15.269 align:start position:0% says what I want to end up with is a bear<00:25:12.759> a<00:25:12.970> bear<00:25:13.149> or<00:25:13.299> token<00:25:13.690> saying<00:25:13.929> I<00:25:14.049> have<00:25:14.230> $1<00:25:14.649> ok 00:25:15.269 --> 00:25:15.279 align:start position:0% bear a bear or token saying I have $1 ok 00:25:15.279 --> 00:25:16.860 align:start position:0% bear a bear or token saying I have $1 ok that's<00:25:15.549> that's<00:25:15.730> already<00:25:16.000> don't<00:25:16.450> take<00:25:16.720> it<00:25:16.809> out 00:25:16.860 --> 00:25:16.870 align:start position:0% that's that's already don't take it out 00:25:16.870 --> 00:25:18.029 align:start position:0% that's that's already don't take it out of<00:25:16.990> the<00:25:17.049> blockchain<00:25:17.230> world<00:25:17.649> for<00:25:17.830> just<00:25:17.950> a 00:25:18.029 --> 00:25:18.039 align:start position:0% of the blockchain world for just a 00:25:18.039 --> 00:25:19.769 align:start position:0% of the blockchain world for just a second<00:25:18.370> so<00:25:18.519> I'm<00:25:18.879> gonna<00:25:19.000> create<00:25:19.269> this<00:25:19.450> claim 00:25:19.769 --> 00:25:19.779 align:start position:0% second so I'm gonna create this claim 00:25:19.779 --> 00:25:22.259 align:start position:0% second so I'm gonna create this claim saying<00:25:20.110> Dave<00:25:20.799> has<00:25:21.009> $1<00:25:21.460> and<00:25:21.820> it'll<00:25:22.090> be<00:25:22.179> in 00:25:22.259 --> 00:25:22.269 align:start position:0% saying Dave has $1 and it'll be in 00:25:22.269 --> 00:25:26.310 align:start position:0% saying Dave has $1 and it'll be in clear-text<00:25:22.620> cool<00:25:23.620> so<00:25:24.220> I've<00:25:24.309> lined<00:25:24.610> it<00:25:25.320> locally 00:25:26.310 --> 00:25:26.320 align:start position:0% clear-text cool so I've lined it locally 00:25:26.320 --> 00:25:27.869 align:start position:0% clear-text cool so I've lined it locally on<00:25:26.470> my<00:25:26.500> client<00:25:27.129> and<00:25:27.279> that<00:25:27.370> turns<00:25:27.610> it<00:25:27.759> into 00:25:27.869 --> 00:25:27.879 align:start position:0% on my client and that turns it into 00:25:27.879 --> 00:25:30.450 align:start position:0% on my client and that turns it into gobbledygook<00:25:28.480> so<00:25:28.899> it<00:25:29.080> just<00:25:29.259> it's<00:25:29.559> just<00:25:29.649> a<00:25:29.950> you 00:25:30.450 --> 00:25:30.460 align:start position:0% gobbledygook so it just it's just a you 00:25:30.460 --> 00:25:33.509 align:start position:0% gobbledygook so it just it's just a you know<00:25:30.490> a<00:25:30.820> piece<00:25:31.299> of<00:25:31.450> string<00:25:32.080> E<00:25:32.139> string<00:25:32.500> eNOS<00:25:32.740> and 00:25:33.509 --> 00:25:33.519 align:start position:0% know a piece of string E string eNOS and 00:25:33.519 --> 00:25:35.430 align:start position:0% know a piece of string E string eNOS and I'm<00:25:33.669> gonna<00:25:33.789> send<00:25:34.090> it<00:25:34.269> to<00:25:34.450> the<00:25:34.570> bank<00:25:34.779> over<00:25:35.230> the 00:25:35.430 --> 00:25:35.440 align:start position:0% I'm gonna send it to the bank over the 00:25:35.440 --> 00:25:37.649 align:start position:0% I'm gonna send it to the bank over the network<00:25:35.610> along<00:25:36.610> with<00:25:36.759> a<00:25:36.789> dollar<00:25:37.059> if<00:25:37.389> I<00:25:37.509> could 00:25:37.649 --> 00:25:37.659 align:start position:0% network along with a dollar if I could 00:25:37.659 --> 00:25:39.210 align:start position:0% network along with a dollar if I could transmit<00:25:37.960> a<00:25:38.080> dollar<00:25:38.320> through<00:25:38.649> the<00:25:38.769> through 00:25:39.210 --> 00:25:39.220 align:start position:0% transmit a dollar through the through 00:25:39.220 --> 00:25:42.119 align:start position:0% transmit a dollar through the through the<00:25:39.279> pipes<00:25:39.659> the<00:25:40.659> bank<00:25:40.870> is<00:25:41.139> gonna<00:25:41.350> then<00:25:41.559> sign<00:25:41.919> it 00:25:42.119 --> 00:25:42.129 align:start position:0% the pipes the bank is gonna then sign it 00:25:42.129 --> 00:25:43.680 align:start position:0% the pipes the bank is gonna then sign it and<00:25:42.309> saying<00:25:42.580> they<00:25:42.789> attest<00:25:43.120> yet<00:25:43.389> Dave 00:25:43.680 --> 00:25:43.690 align:start position:0% and saying they attest yet Dave 00:25:43.690 --> 00:25:45.210 align:start position:0% and saying they attest yet Dave definitely<00:25:44.110> has<00:25:44.230> a<00:25:44.259> dollar<00:25:44.529> we're<00:25:44.799> rolling<00:25:45.100> it 00:25:45.210 --> 00:25:45.220 align:start position:0% definitely has a dollar we're rolling it 00:25:45.220 --> 00:25:47.310 align:start position:0% definitely has a dollar we're rolling it cool<00:25:45.460> now<00:25:45.490> he's<00:25:45.820> got<00:25:46.000> this<00:25:46.120> claim<00:25:46.779> that<00:25:47.049> he<00:25:47.169> can 00:25:47.310 --> 00:25:47.320 align:start position:0% cool now he's got this claim that he can 00:25:47.320 --> 00:25:48.749 align:start position:0% cool now he's got this claim that he can run<00:25:47.440> around<00:25:47.590> with<00:25:47.799> and<00:25:48.159> they<00:25:48.460> give<00:25:48.610> me<00:25:48.639> a 00:25:48.749 --> 00:25:48.759 align:start position:0% run around with and they give me a 00:25:48.759 --> 00:25:50.690 align:start position:0% run around with and they give me a signature<00:25:49.149> back<00:25:49.450> so<00:25:49.960> they've<00:25:50.080> signed 00:25:50.690 --> 00:25:50.700 align:start position:0% signature back so they've signed 00:25:50.700 --> 00:25:53.430 align:start position:0% signature back so they've signed basically<00:25:51.700> a<00:25:51.909> piece<00:25:52.210> of<00:25:52.450> blind<00:25:52.809> cryptographic 00:25:53.430 --> 00:25:53.440 align:start position:0% basically a piece of blind cryptographic 00:25:53.440 --> 00:25:56.669 align:start position:0% basically a piece of blind cryptographic material<00:25:54.279> they<00:25:55.179> give<00:25:55.330> it<00:25:55.419> back<00:25:55.450> to<00:25:55.779> me<00:25:55.929> and<00:25:56.259> now 00:25:56.669 --> 00:25:56.679 align:start position:0% material they give it back to me and now 00:25:56.679 --> 00:25:59.990 align:start position:0% material they give it back to me and now I<00:25:56.710> now<00:25:57.370> I<00:25:57.399> unwind<00:25:58.090> the<00:25:58.360> credential<00:25:58.870> and<00:25:59.139> I<00:25:59.289> can 00:25:59.990 --> 00:26:00.000 align:start position:0% I now I unwind the credential and I can 00:26:00.000 --> 00:26:02.310 align:start position:0% I now I unwind the credential and I can basically<00:26:01.000> D<00:26:01.179> Link<00:26:01.419> it<00:26:01.570> back<00:26:01.720> from<00:26:01.990> what<00:26:02.139> I<00:26:02.169> got 00:26:02.310 --> 00:26:02.320 align:start position:0% basically D Link it back from what I got 00:26:02.320 --> 00:26:03.930 align:start position:0% basically D Link it back from what I got back<00:26:02.529> from<00:26:02.679> the<00:26:02.830> bank<00:26:03.129> so<00:26:03.460> I<00:26:03.490> now<00:26:03.700> have<00:26:03.730> a 00:26:03.930 --> 00:26:03.940 align:start position:0% back from the bank so I now have a 00:26:03.940 --> 00:26:06.389 align:start position:0% back from the bank so I now have a bearer<00:26:04.269> token<00:26:04.809> which<00:26:05.350> attests<00:26:05.679> that<00:26:05.980> I<00:26:06.129> on<00:26:06.309> a 00:26:06.389 --> 00:26:06.399 align:start position:0% bearer token which attests that I on a 00:26:06.399 --> 00:26:07.580 align:start position:0% bearer token which attests that I on a dollar<00:26:06.610> and<00:26:06.970> yet 00:26:07.580 --> 00:26:07.590 align:start position:0% dollar and yet 00:26:07.590 --> 00:26:12.620 align:start position:0% dollar and yet the<00:26:07.800> bank<00:26:08.040> never<00:26:08.540> actually<00:26:11.390> they<00:26:12.390> can't 00:26:12.620 --> 00:26:12.630 align:start position:0% the bank never actually they can't 00:26:12.630 --> 00:26:14.330 align:start position:0% the bank never actually they can't really<00:26:12.780> identify<00:26:13.020> because<00:26:13.530> that<00:26:14.010> you<00:26:14.220> know 00:26:14.330 --> 00:26:14.340 align:start position:0% really identify because that you know 00:26:14.340 --> 00:26:16.130 align:start position:0% really identify because that you know that<00:26:14.550> all<00:26:14.820> the<00:26:14.970> other<00:26:15.000> materially<00:26:15.750> in<00:26:15.900> that 00:26:16.130 --> 00:26:16.140 align:start position:0% that all the other materially in that 00:26:16.140 --> 00:26:19.010 align:start position:0% that all the other materially in that blinded<00:26:16.770> credential<00:26:17.280> they<00:26:17.550> never<00:26:18.450> saw<00:26:18.720> they 00:26:19.010 --> 00:26:19.020 align:start position:0% blinded credential they never saw they 00:26:19.020 --> 00:26:21.020 align:start position:0% blinded credential they never saw they just<00:26:19.200> saw<00:26:19.320> some<00:26:19.530> gobbledygook<00:26:20.010> so<00:26:20.580> this 00:26:21.020 --> 00:26:21.030 align:start position:0% just saw some gobbledygook so this 00:26:21.030 --> 00:26:23.000 align:start position:0% just saw some gobbledygook so this process<00:26:21.330> of<00:26:21.780> that<00:26:21.900> to<00:26:22.200> create<00:26:22.470> the<00:26:22.590> clear<00:26:22.800> text 00:26:23.000 --> 00:26:23.010 align:start position:0% process of that to create the clear text 00:26:23.010 --> 00:26:25.190 align:start position:0% process of that to create the clear text blinded<00:26:23.940> clear<00:26:24.120> text<00:26:24.360> locally<00:26:24.750> send<00:26:25.020> it<00:26:25.110> to 00:26:25.190 --> 00:26:25.200 align:start position:0% blinded clear text locally send it to 00:26:25.200 --> 00:26:28.280 align:start position:0% blinded clear text locally send it to the<00:26:25.290> signer<00:26:25.530> the<00:26:26.070> signer<00:26:26.310> signs<00:26:26.640> it<00:26:27.170> return<00:26:28.170> it 00:26:28.280 --> 00:26:28.290 align:start position:0% the signer the signer signs it return it 00:26:28.290 --> 00:26:29.720 align:start position:0% the signer the signer signs it return it to<00:26:28.350> the<00:26:28.440> creator<00:26:28.740> and<00:26:29.010> the<00:26:29.130> creator<00:26:29.430> on<00:26:29.490> the 00:26:29.720 --> 00:26:29.730 align:start position:0% to the creator and the creator on the 00:26:29.730 --> 00:26:31.760 align:start position:0% to the creator and the creator on the blinds<00:26:29.970> it<00:26:30.180> to<00:26:30.330> use<00:26:30.450> it<00:26:30.600> as<00:26:30.690> bearer<00:26:30.960> token<00:26:31.350> this 00:26:31.760 --> 00:26:31.770 align:start position:0% blinds it to use it as bearer token this 00:26:31.770 --> 00:26:34.550 align:start position:0% blinds it to use it as bearer token this is<00:26:31.980> the<00:26:32.190> kind<00:26:32.640> of<00:26:32.700> general<00:26:33.540> process<00:26:34.170> of<00:26:34.290> wine 00:26:34.550 --> 00:26:34.560 align:start position:0% is the kind of general process of wine 00:26:34.560 --> 00:26:36.920 align:start position:0% is the kind of general process of wine signatures<00:26:35.130> now<00:26:35.550> some<00:26:36.360> of<00:26:36.390> you<00:26:36.630> may<00:26:36.900> have 00:26:36.920 --> 00:26:36.930 align:start position:0% signatures now some of you may have 00:26:36.930 --> 00:26:39.290 align:start position:0% signatures now some of you may have noted<00:26:37.470> that<00:26:37.500> there's<00:26:37.860> a<00:26:37.920> problem<00:26:38.190> with<00:26:39.060> the 00:26:39.290 --> 00:26:39.300 align:start position:0% noted that there's a problem with the 00:26:39.300 --> 00:26:41.870 align:start position:0% noted that there's a problem with the mind<00:26:39.540> issuance<00:26:39.980> you<00:26:40.980> may<00:26:41.100> but<00:26:41.250> I<00:26:41.280> detect<00:26:41.520> what 00:26:41.870 --> 00:26:41.880 align:start position:0% mind issuance you may but I detect what 00:26:41.880 --> 00:26:48.110 align:start position:0% mind issuance you may but I detect what it<00:26:41.970> might<00:26:42.150> be<00:26:45.830> exactly<00:26:46.860> so<00:26:47.160> the<00:26:47.280> cider<00:26:47.520> has 00:26:48.110 --> 00:26:48.120 align:start position:0% it might be exactly so the cider has 00:26:48.120 --> 00:26:49.550 align:start position:0% it might be exactly so the cider has just<00:26:48.480> been<00:26:48.600> presented<00:26:48.870> with<00:26:49.350> this 00:26:49.550 --> 00:26:49.560 align:start position:0% just been presented with this 00:26:49.560 --> 00:26:51.290 align:start position:0% just been presented with this gobbledygook<00:26:50.280> and<00:26:50.520> they<00:26:50.580> signed<00:26:50.850> it<00:26:51.030> and<00:26:51.180> then 00:26:51.290 --> 00:26:51.300 align:start position:0% gobbledygook and they signed it and then 00:26:51.300 --> 00:26:52.640 align:start position:0% gobbledygook and they signed it and then given<00:26:51.510> it<00:26:51.600> back<00:26:51.720> to<00:26:51.780> me<00:26:51.990> so<00:26:52.170> it<00:26:52.380> could<00:26:52.560> have 00:26:52.640 --> 00:26:52.650 align:start position:0% given it back to me so it could have 00:26:52.650 --> 00:26:54.590 align:start position:0% given it back to me so it could have said<00:26:52.830> dave<00:26:53.010> has<00:26:53.190> $1,000,000<00:26:54.030> in<00:26:54.060> it<00:26:54.300> and<00:26:54.510> they 00:26:54.590 --> 00:26:54.600 align:start position:0% said dave has $1,000,000 in it and they 00:26:54.600 --> 00:26:56.120 align:start position:0% said dave has $1,000,000 in it and they would<00:26:54.780> be<00:26:54.900> unable<00:26:55.110> to<00:26:55.170> tell<00:26:55.590> without<00:26:55.920> some 00:26:56.120 --> 00:26:56.130 align:start position:0% would be unable to tell without some 00:26:56.130 --> 00:26:58.730 align:start position:0% would be unable to tell without some further<00:26:56.340> active<00:26:57.300> verification<00:26:57.990> so<00:26:58.470> if<00:26:58.620> you're 00:26:58.730 --> 00:26:58.740 align:start position:0% further active verification so if you're 00:26:58.740 --> 00:27:00.350 align:start position:0% further active verification so if you're the<00:26:58.860> you're<00:26:59.400> the<00:26:59.490> bank<00:26:59.670> you<00:26:59.820> get<00:26:59.940> some<00:27:00.090> gully 00:27:00.350 --> 00:27:00.360 align:start position:0% the you're the bank you get some gully 00:27:00.360 --> 00:27:03.050 align:start position:0% the you're the bank you get some gully the<00:27:01.710> youthful<00:27:02.130> solution<00:27:02.550> to<00:27:02.640> this<00:27:02.760> is<00:27:03.000> to 00:27:03.050 --> 00:27:03.060 align:start position:0% the youthful solution to this is to 00:27:03.060 --> 00:27:05.150 align:start position:0% the youthful solution to this is to use<00:27:03.390> as<00:27:03.540> your<00:27:03.660> knowledge<00:27:03.990> proof<00:27:04.200> attesting 00:27:05.150 --> 00:27:05.160 align:start position:0% use as your knowledge proof attesting 00:27:05.160 --> 00:27:07.400 align:start position:0% use as your knowledge proof attesting that<00:27:05.220> the<00:27:05.550> message<00:27:05.880> contains<00:27:06.270> one<00:27:06.480> dollar<00:27:06.750> but 00:27:07.400 --> 00:27:07.410 align:start position:0% that the message contains one dollar but 00:27:07.410 --> 00:27:08.510 align:start position:0% that the message contains one dollar but reveals<00:27:07.830> nothing<00:27:08.220> else 00:27:08.510 --> 00:27:08.520 align:start position:0% reveals nothing else 00:27:08.520 --> 00:27:10.550 align:start position:0% reveals nothing else so<00:27:08.760> the<00:27:08.880> serial<00:27:09.270> number<00:27:09.540> of<00:27:09.570> the<00:27:09.900> credential 00:27:10.550 --> 00:27:10.560 align:start position:0% so the serial number of the credential 00:27:10.560 --> 00:27:12.980 align:start position:0% so the serial number of the credential my<00:27:10.980> identity<00:27:11.610> anything<00:27:12.210> like<00:27:12.360> that<00:27:12.390> so 00:27:12.980 --> 00:27:12.990 align:start position:0% my identity anything like that so 00:27:12.990 --> 00:27:14.060 align:start position:0% my identity anything like that so there's<00:27:13.170> a<00:27:13.230> bit<00:27:13.380> of<00:27:13.410> zero<00:27:13.650> knowledge<00:27:13.830> of 00:27:14.060 --> 00:27:14.070 align:start position:0% there's a bit of zero knowledge of 00:27:14.070 --> 00:27:16.490 align:start position:0% there's a bit of zero knowledge of action<00:27:14.460> inside<00:27:14.880> this<00:27:15.090> so<00:27:15.600> coconut<00:27:16.050> our 00:27:16.490 --> 00:27:16.500 align:start position:0% action inside this so coconut our 00:27:16.500 --> 00:27:18.710 align:start position:0% action inside this so coconut our signature<00:27:16.980> scheme<00:27:17.220> has<00:27:17.670> this<00:27:18.000> hero<00:27:18.390> knowledge 00:27:18.710 --> 00:27:18.720 align:start position:0% signature scheme has this hero knowledge 00:27:18.720 --> 00:27:20.330 align:start position:0% signature scheme has this hero knowledge proof<00:27:18.930> abilities<00:27:19.440> that's<00:27:19.710> one<00:27:19.890> of<00:27:20.010> the<00:27:20.100> things 00:27:20.330 --> 00:27:20.340 align:start position:0% proof abilities that's one of the things 00:27:20.340 --> 00:27:23.840 align:start position:0% proof abilities that's one of the things that<00:27:20.460> it<00:27:20.550> does<00:27:20.580> so<00:27:20.880> we<00:27:20.970> can<00:27:21.120> do<00:27:21.270> my<00:27:21.540> dishes<00:27:22.850> cool 00:27:23.840 --> 00:27:23.850 align:start position:0% that it does so we can do my dishes cool 00:27:23.850 --> 00:27:29.060 align:start position:0% that it does so we can do my dishes cool a<00:27:24.980> second<00:27:25.980> thing<00:27:26.250> that<00:27:26.490> we<00:27:26.760> have<00:27:26.940> is<00:27:28.070> the 00:27:29.060 --> 00:27:29.070 align:start position:0% a second thing that we have is the 00:27:29.070 --> 00:27:30.740 align:start position:0% a second thing that we have is the concept<00:27:29.520> of<00:27:29.610> reran<00:27:30.060> demise<00:27:30.390> of<00:27:30.570> bold 00:27:30.740 --> 00:27:30.750 align:start position:0% concept of reran demise of bold 00:27:30.750 --> 00:27:32.330 align:start position:0% concept of reran demise of bold signatures<00:27:31.290> does<00:27:31.470> anybody<00:27:31.680> ever<00:27:31.920> run<00:27:32.100> across 00:27:32.330 --> 00:27:32.340 align:start position:0% signatures does anybody ever run across 00:27:32.340 --> 00:27:34.730 align:start position:0% signatures does anybody ever run across this<00:27:32.520> before<00:27:32.990> now<00:27:33.990> it's<00:27:34.140> a<00:27:34.200> pretty<00:27:34.380> weird<00:27:34.530> one 00:27:34.730 --> 00:27:34.740 align:start position:0% this before now it's a pretty weird one 00:27:34.740 --> 00:27:36.620 align:start position:0% this before now it's a pretty weird one I'm<00:27:35.430> gonna<00:27:35.580> demonstrate<00:27:35.730> it<00:27:36.120> in<00:27:36.210> a<00:27:36.270> little<00:27:36.480> bit 00:27:36.620 --> 00:27:36.630 align:start position:0% I'm gonna demonstrate it in a little bit 00:27:36.630 --> 00:27:40.460 align:start position:0% I'm gonna demonstrate it in a little bit but<00:27:38.330> this<00:27:39.330> type<00:27:39.540> of<00:27:39.570> signature<00:27:40.080> has<00:27:40.290> an 00:27:40.460 --> 00:27:40.470 align:start position:0% but this type of signature has an 00:27:40.470 --> 00:27:42.170 align:start position:0% but this type of signature has an additional<00:27:40.980> algorithm<00:27:41.610> to<00:27:41.760> these<00:27:41.880> three 00:27:42.170 --> 00:27:42.180 align:start position:0% additional algorithm to these three 00:27:42.180 --> 00:27:45.500 align:start position:0% additional algorithm to these three which<00:27:42.750> is<00:27:42.930> basically<00:27:43.310> randomized<00:27:44.310> so<00:27:45.000> you 00:27:45.500 --> 00:27:45.510 align:start position:0% which is basically randomized so you 00:27:45.510 --> 00:27:48.440 align:start position:0% which is basically randomized so you basically<00:27:45.750> can<00:27:46.080> take<00:27:46.290> a<00:27:46.440> signature<00:27:47.180> and<00:27:48.180> then 00:27:48.440 --> 00:27:48.450 align:start position:0% basically can take a signature and then 00:27:48.450 --> 00:27:50.270 align:start position:0% basically can take a signature and then from<00:27:48.780> that<00:27:48.960> signature<00:27:49.320> you<00:27:49.620> can<00:27:49.770> call<00:27:49.950> a<00:27:49.980> call 00:27:50.270 --> 00:27:50.280 align:start position:0% from that signature you can call a call 00:27:50.280 --> 00:27:52.490 align:start position:0% from that signature you can call a call to<00:27:50.400> randomized<00:27:50.790> method<00:27:51.180> on<00:27:51.270> it<00:27:51.300> and<00:27:51.570> you<00:27:52.350> can 00:27:52.490 --> 00:27:52.500 align:start position:0% to randomized method on it and you can 00:27:52.500 --> 00:27:55.010 align:start position:0% to randomized method on it and you can basically<00:27:53.540> generate<00:27:54.540> a<00:27:54.570> brand<00:27:54.870> new 00:27:55.010 --> 00:27:55.020 align:start position:0% basically generate a brand new 00:27:55.020 --> 00:27:57.320 align:start position:0% basically generate a brand new credential<00:27:55.640> which<00:27:56.640> is<00:27:56.820> cryptographically 00:27:57.320 --> 00:27:57.330 align:start position:0% credential which is cryptographically 00:27:57.330 --> 00:27:59.780 align:start position:0% credential which is cryptographically equivalent<00:27:58.140> to<00:27:58.740> the<00:27:58.830> original<00:27:58.950> credential 00:27:59.780 --> 00:27:59.790 align:start position:0% equivalent to the original credential 00:27:59.790 --> 00:28:02.060 align:start position:0% equivalent to the original credential that<00:27:59.940> you<00:28:00.060> originally<00:28:00.210> had<00:28:00.630> in<00:28:00.780> your<00:28:00.870> hand<00:28:01.140> is 00:28:02.060 --> 00:28:02.070 align:start position:0% that you originally had in your hand is 00:28:02.070 --> 00:28:04.340 align:start position:0% that you originally had in your hand is completely<00:28:02.430> delinked<00:28:03.240> become<00:28:03.660> completely 00:28:04.340 --> 00:28:04.350 align:start position:0% completely delinked become completely 00:28:04.350 --> 00:28:06.350 align:start position:0% completely delinked become completely anonymizes<00:28:05.160> the<00:28:05.640> cryptographic<00:28:05.910> that 00:28:06.350 --> 00:28:06.360 align:start position:0% anonymizes the cryptographic that 00:28:06.360 --> 00:28:08.750 align:start position:0% anonymizes the cryptographic that here<00:28:06.480> they<00:28:06.690> have<00:28:06.960> in<00:28:07.110> the<00:28:07.200> bearer<00:28:07.410> token<00:28:07.860> so<00:28:08.640> it 00:28:08.750 --> 00:28:08.760 align:start position:0% here they have in the bearer token so it 00:28:08.760 --> 00:28:10.460 align:start position:0% here they have in the bearer token so it looks<00:28:09.000> like<00:28:09.240> a<00:28:09.270> brand<00:28:09.570> new<00:28:09.720> credentialism<00:28:10.230> s 00:28:10.460 --> 00:28:10.470 align:start position:0% looks like a brand new credentialism s 00:28:10.470 --> 00:28:12.950 align:start position:0% looks like a brand new credentialism s are<00:28:10.590> unthinkable<00:28:10.830> between<00:28:11.490> the<00:28:11.610> two<00:28:11.760> but<00:28:12.330> it 00:28:12.950 --> 00:28:12.960 align:start position:0% are unthinkable between the two but it 00:28:12.960 --> 00:28:14.360 align:start position:0% are unthinkable between the two but it can<00:28:13.110> still<00:28:13.350> be<00:28:13.410> verified<00:28:14.040> through 00:28:14.360 --> 00:28:14.370 align:start position:0% can still be verified through 00:28:14.370 --> 00:28:16.550 align:start position:0% can still be verified through cryptography<00:28:15.180> and<00:28:15.330> this<00:28:15.540> as<00:28:15.930> if<00:28:16.110> it<00:28:16.260> was<00:28:16.410> the 00:28:16.550 --> 00:28:16.560 align:start position:0% cryptography and this as if it was the 00:28:16.560 --> 00:28:18.350 align:start position:0% cryptography and this as if it was the original<00:28:16.650> one<00:28:17.070> so<00:28:17.490> I'll<00:28:17.580> demonstrate<00:28:17.820> that<00:28:18.150> in 00:28:18.350 --> 00:28:18.360 align:start position:0% original one so I'll demonstrate that in 00:28:18.360 --> 00:28:21.320 align:start position:0% original one so I'll demonstrate that in a<00:28:18.540> bit<00:28:18.920> but<00:28:19.920> that<00:28:20.130> basically<00:28:20.730> can<00:28:21.000> make<00:28:21.180> your 00:28:21.320 --> 00:28:21.330 align:start position:0% a bit but that basically can make your 00:28:21.330 --> 00:28:24.920 align:start position:0% a bit but that basically can make your bearer<00:28:21.570> tokens<00:28:22.310> untraceable<00:28:23.310> so<00:28:23.880> you<00:28:24.750> get<00:28:24.900> a 00:28:24.920 --> 00:28:24.930 align:start position:0% bearer tokens untraceable so you get a 00:28:24.930 --> 00:28:26.420 align:start position:0% bearer tokens untraceable so you get a very<00:28:25.200> very<00:28:25.290> backward<00:28:25.950> and<00:28:26.070> some<00:28:26.220> kind<00:28:26.400> of 00:28:26.420 --> 00:28:26.430 align:start position:0% very very backward and some kind of 00:28:26.430 --> 00:28:28.160 align:start position:0% very very backward and some kind of authority<00:28:26.880> you<00:28:27.060> call<00:28:27.510> the<00:28:27.600> random<00:28:27.870> re 00:28:28.160 --> 00:28:28.170 align:start position:0% authority you call the random re 00:28:28.170 --> 00:28:30.170 align:start position:0% authority you call the random re randomize<00:28:28.590> method<00:28:28.980> on<00:28:29.070> it<00:28:29.100> you<00:28:29.640> get<00:28:29.790> a<00:28:29.820> new 00:28:30.170 --> 00:28:30.180 align:start position:0% randomize method on it you get a new 00:28:30.180 --> 00:28:31.490 align:start position:0% randomize method on it you get a new bearer<00:28:30.450> token<00:28:30.750> as<00:28:30.930> the<00:28:31.020> same<00:28:31.200> cryptographic 00:28:31.490 --> 00:28:31.500 align:start position:0% bearer token as the same cryptographic 00:28:31.500 --> 00:28:33.530 align:start position:0% bearer token as the same cryptographic material<00:28:32.160> but<00:28:32.340> the<00:28:32.670> authority<00:28:33.120> can't<00:28:33.360> say 00:28:33.530 --> 00:28:33.540 align:start position:0% material but the authority can't say 00:28:33.540 --> 00:28:35.090 align:start position:0% material but the authority can't say guess<00:28:33.810> was<00:28:34.110> they<00:28:34.260> have<00:28:34.380> that<00:28:34.500> generated<00:28:34.950> this 00:28:35.090 --> 00:28:35.100 align:start position:0% guess was they have that generated this 00:28:35.100 --> 00:28:36.410 align:start position:0% guess was they have that generated this because<00:28:35.250> I<00:28:35.370> saw<00:28:35.550> that<00:28:35.700> one<00:28:35.880> and<00:28:36.060> I<00:28:36.120> gave<00:28:36.270> it<00:28:36.390> to 00:28:36.410 --> 00:28:36.420 align:start position:0% because I saw that one and I gave it to 00:28:36.420 --> 00:28:39.470 align:start position:0% because I saw that one and I gave it to it's<00:28:37.140> that<00:28:37.290> kind<00:28:37.680> of<00:28:37.710> makes<00:28:37.920> sense<00:28:38.480> getting 00:28:39.470 --> 00:28:39.480 align:start position:0% it's that kind of makes sense getting 00:28:39.480 --> 00:28:43.610 align:start position:0% it's that kind of makes sense getting cool<00:28:41.090> okay<00:28:42.090> so<00:28:42.150> what<00:28:42.390> is<00:28:42.480> this<00:28:42.570> used<00:28:42.780> for<00:28:42.900> so 00:28:43.610 --> 00:28:43.620 align:start position:0% cool okay so what is this used for so 00:28:43.620 --> 00:28:45.470 align:start position:0% cool okay so what is this used for so you<00:28:43.680> could<00:28:43.950> create<00:28:44.160> multiple<00:28:44.550> signatures<00:28:45.060> and 00:28:45.470 --> 00:28:45.480 align:start position:0% you could create multiple signatures and 00:28:45.480 --> 00:28:47.210 align:start position:0% you could create multiple signatures and show<00:28:45.780> them<00:28:45.900> to<00:28:45.960> different<00:28:46.260> people<00:28:46.620> but<00:28:47.100> the 00:28:47.210 --> 00:28:47.220 align:start position:0% show them to different people but the 00:28:47.220 --> 00:28:49.130 align:start position:0% show them to different people but the people<00:28:47.370> that<00:28:47.580> you<00:28:47.970> show<00:28:48.150> it<00:28:48.270> to<00:28:48.420> cannot<00:28:48.810> link 00:28:49.130 --> 00:28:49.140 align:start position:0% people that you show it to cannot link 00:28:49.140 --> 00:28:50.690 align:start position:0% people that you show it to cannot link you<00:28:49.320> back<00:28:49.530> to<00:28:49.770> the<00:28:49.860> original<00:28:49.950> original 00:28:50.690 --> 00:28:50.700 align:start position:0% you back to the original original 00:28:50.700 --> 00:28:53.720 align:start position:0% you back to the original original signature<00:28:51.150> or<00:28:51.390> any<00:28:51.870> of<00:28:52.230> the<00:28:52.410> other<00:28:52.680> rear<00:28:53.580> end 00:28:53.720 --> 00:28:53.730 align:start position:0% signature or any of the other rear end 00:28:53.730 --> 00:28:55.370 align:start position:0% signature or any of the other rear end of<00:28:53.820> my<00:28:53.910> signatures<00:28:54.420> but<00:28:54.900> the<00:28:55.050> underlying 00:28:55.370 --> 00:28:55.380 align:start position:0% of my signatures but the underlying 00:28:55.380 --> 00:28:59.150 align:start position:0% of my signatures but the underlying messages<00:28:55.980> in<00:28:56.750> in<00:28:57.750> this<00:28:57.870> case<00:28:58.050> is<00:28:58.500> all<00:28:58.830> the<00:28:58.980> same 00:28:59.150 --> 00:28:59.160 align:start position:0% messages in in this case is all the same 00:28:59.160 --> 00:29:00.560 align:start position:0% messages in in this case is all the same so<00:28:59.520> that<00:28:59.760> caught<00:28:59.940> the<00:29:00.090> crypto<00:29:00.330> got<00:29:00.480> the 00:29:00.560 --> 00:29:00.570 align:start position:0% so that caught the crypto got the 00:29:00.570 --> 00:29:02.060 align:start position:0% so that caught the crypto got the content<00:29:00.900> is<00:29:01.050> all<00:29:01.170> the<00:29:01.260> same<00:29:01.410> across<00:29:01.770> all<00:29:01.950> these 00:29:02.060 --> 00:29:02.070 align:start position:0% content is all the same across all these 00:29:02.070 --> 00:29:03.800 align:start position:0% content is all the same across all these credentials<00:29:02.820> so<00:29:03.210> we<00:29:03.300> basically<00:29:03.510> have 00:29:03.800 --> 00:29:03.810 align:start position:0% credentials so we basically have 00:29:03.810 --> 00:29:05.660 align:start position:0% credentials so we basically have multiple<00:29:04.200> anonymized<00:29:04.680> bearer<00:29:04.950> tokens<00:29:05.400> that 00:29:05.660 --> 00:29:05.670 align:start position:0% multiple anonymized bearer tokens that 00:29:05.670 --> 00:29:07.550 align:start position:0% multiple anonymized bearer tokens that can<00:29:06.120> each<00:29:06.330> be<00:29:06.510> validated<00:29:07.080> as<00:29:07.170> if<00:29:07.320> they<00:29:07.470> were 00:29:07.550 --> 00:29:07.560 align:start position:0% can each be validated as if they were 00:29:07.560 --> 00:29:09.050 align:start position:0% can each be validated as if they were the<00:29:07.740> originals<00:29:08.130> so<00:29:08.220> we<00:29:08.430> have<00:29:08.550> the<00:29:08.640> property<00:29:09.030> of 00:29:09.050 --> 00:29:09.060 align:start position:0% the originals so we have the property of 00:29:09.060 --> 00:29:15.500 align:start position:0% the originals so we have the property of unlink<00:29:09.540> ability<00:29:11.870> cool<00:29:13.700> we<00:29:14.700> also<00:29:14.880> have<00:29:15.240> a 00:29:15.500 --> 00:29:15.510 align:start position:0% unlink ability cool we also have a 00:29:15.510 --> 00:29:18.260 align:start position:0% unlink ability cool we also have a concept<00:29:15.960> of<00:29:16.170> selective<00:29:16.770> disclosure<00:29:16.980> so<00:29:17.850> in<00:29:18.180> a 00:29:18.260 --> 00:29:18.270 align:start position:0% concept of selective disclosure so in a 00:29:18.270 --> 00:29:20.570 align:start position:0% concept of selective disclosure so in a traditional<00:29:18.450> scheme<00:29:19.110> when<00:29:20.070> you<00:29:20.160> sign<00:29:20.430> the 00:29:20.570 --> 00:29:20.580 align:start position:0% traditional scheme when you sign the 00:29:20.580 --> 00:29:21.980 align:start position:0% traditional scheme when you sign the message<00:29:20.910> and<00:29:21.180> somebody<00:29:21.600> wants<00:29:21.810> to<00:29:21.840> be 00:29:21.980 --> 00:29:21.990 align:start position:0% message and somebody wants to be 00:29:21.990 --> 00:29:23.360 align:start position:0% message and somebody wants to be verifies<00:29:22.440> the<00:29:22.590> message<00:29:22.860> they<00:29:22.980> have<00:29:23.070> to<00:29:23.190> verify 00:29:23.360 --> 00:29:23.370 align:start position:0% verifies the message they have to verify 00:29:23.370 --> 00:29:25.040 align:start position:0% verifies the message they have to verify the<00:29:23.640> whole<00:29:23.910> thing<00:29:24.180> okay 00:29:25.040 --> 00:29:25.050 align:start position:0% the whole thing okay 00:29:25.050 --> 00:29:27.350 align:start position:0% the whole thing okay so<00:29:25.500> selective<00:29:25.950> disclosure<00:29:26.160> means<00:29:27.120> that 00:29:27.350 --> 00:29:27.360 align:start position:0% so selective disclosure means that 00:29:27.360 --> 00:29:29.090 align:start position:0% so selective disclosure means that instead<00:29:27.690> of<00:29:27.840> needing<00:29:28.170> to<00:29:28.200> verify<00:29:28.710> the<00:29:28.770> whole 00:29:29.090 --> 00:29:29.100 align:start position:0% instead of needing to verify the whole 00:29:29.100 --> 00:29:32.000 align:start position:0% instead of needing to verify the whole message<00:29:29.370> you<00:29:30.180> can<00:29:30.360> have<00:29:30.810> people<00:29:31.050> verify<00:29:31.590> only 00:29:32.000 --> 00:29:32.010 align:start position:0% message you can have people verify only 00:29:32.010 --> 00:29:34.310 align:start position:0% message you can have people verify only certain<00:29:32.460> attributes<00:29:33.090> in<00:29:33.810> the<00:29:34.020> message 00:29:34.310 --> 00:29:34.320 align:start position:0% certain attributes in the message 00:29:34.320 --> 00:29:36.320 align:start position:0% certain attributes in the message keeping<00:29:35.070> other<00:29:35.250> parts<00:29:35.580> of<00:29:35.670> it<00:29:35.820> private<00:29:36.240> so 00:29:36.320 --> 00:29:36.330 align:start position:0% keeping other parts of it private so 00:29:36.330 --> 00:29:38.870 align:start position:0% keeping other parts of it private so let's<00:29:36.660> consider<00:29:37.020> an<00:29:38.010> example<00:29:38.100> again<00:29:38.640> to<00:29:38.760> make 00:29:38.870 --> 00:29:38.880 align:start position:0% let's consider an example again to make 00:29:38.880 --> 00:29:40.880 align:start position:0% let's consider an example again to make things<00:29:39.090> easier<00:29:39.390> let's<00:29:40.260> assume<00:29:40.500> that<00:29:40.560> we<00:29:40.860> have 00:29:40.880 --> 00:29:40.890 align:start position:0% things easier let's assume that we have 00:29:40.890 --> 00:29:44.300 align:start position:0% things easier let's assume that we have a<00:29:41.460> passport<00:29:42.090> so<00:29:42.840> my<00:29:43.230> passport<00:29:43.650> has<00:29:43.770> my<00:29:43.920> name<00:29:43.980> my 00:29:44.300 --> 00:29:44.310 align:start position:0% a passport so my passport has my name my 00:29:44.310 --> 00:29:46.760 align:start position:0% a passport so my passport has my name my nationality<00:29:44.820> age<00:29:45.000> photo<00:29:45.780> and<00:29:46.200> place<00:29:46.500> of<00:29:46.650> issue 00:29:46.760 --> 00:29:46.770 align:start position:0% nationality age photo and place of issue 00:29:46.770 --> 00:29:48.430 align:start position:0% nationality age photo and place of issue in<00:29:47.190> it<00:29:47.370> right<00:29:47.610> so<00:29:47.880> these<00:29:47.970> are<00:29:48.060> the<00:29:48.180> attributes 00:29:48.430 --> 00:29:48.440 align:start position:0% in it right so these are the attributes 00:29:48.440 --> 00:29:51.350 align:start position:0% in it right so these are the attributes in<00:29:49.440> the<00:29:49.590> passport<00:29:49.910> let's<00:29:50.910> say<00:29:51.000> I<00:29:51.060> want<00:29:51.240> to<00:29:51.270> go 00:29:51.350 --> 00:29:51.360 align:start position:0% in the passport let's say I want to go 00:29:51.360 --> 00:29:53.390 align:start position:0% in the passport let's say I want to go to<00:29:51.420> the<00:29:51.540> pub<00:29:51.720> and<00:29:51.870> have<00:29:51.990> a<00:29:52.020> drink<00:29:52.230> and<00:29:52.500> they 00:29:53.390 --> 00:29:53.400 align:start position:0% to the pub and have a drink and they 00:29:53.400 --> 00:29:55.640 align:start position:0% to the pub and have a drink and they like<00:29:53.640> I<00:29:54.060> mean<00:29:54.300> I'm<00:29:54.720> so<00:29:55.050> old<00:29:55.230> that<00:29:55.290> I<00:29:55.440> would 00:29:55.640 --> 00:29:55.650 align:start position:0% like I mean I'm so old that I would 00:29:55.650 --> 00:29:57.440 align:start position:0% like I mean I'm so old that I would never<00:29:55.770> need<00:29:56.010> to<00:29:56.160> prove<00:29:56.370> that<00:29:56.400> I'm<00:29:56.700> old<00:29:57.300> enough 00:29:57.440 --> 00:29:57.450 align:start position:0% never need to prove that I'm old enough 00:29:57.450 --> 00:29:59.060 align:start position:0% never need to prove that I'm old enough to<00:29:57.540> get<00:29:57.720> it<00:29:57.840> but<00:29:57.990> other<00:29:58.110> people<00:29:58.200> might<00:29:58.680> need<00:29:58.920> to 00:29:59.060 --> 00:29:59.070 align:start position:0% to get it but other people might need to 00:29:59.070 --> 00:30:00.530 align:start position:0% to get it but other people might need to actually<00:29:59.190> like<00:29:59.610> produce<00:29:59.880> some<00:30:00.090> kind<00:30:00.330> of<00:30:00.360> ID 00:30:00.530 --> 00:30:00.540 align:start position:0% actually like produce some kind of ID 00:30:00.540 --> 00:30:05.090 align:start position:0% actually like produce some kind of ID and<00:30:00.980> you<00:30:01.980> know<00:30:02.990> you<00:30:03.990> could<00:30:04.260> in<00:30:04.500> an<00:30:04.560> electronic 00:30:05.090 --> 00:30:05.100 align:start position:0% and you know you could in an electronic 00:30:05.100 --> 00:30:07.400 align:start position:0% and you know you could in an electronic kind<00:30:05.370> of<00:30:05.520> way<00:30:06.210> you<00:30:06.660> might<00:30:06.930> send<00:30:07.170> your<00:30:07.290> whole 00:30:07.400 --> 00:30:07.410 align:start position:0% kind of way you might send your whole 00:30:07.410 --> 00:30:08.930 align:start position:0% kind of way you might send your whole passport<00:30:07.890> over<00:30:08.070> right<00:30:08.250> and<00:30:08.460> identify 00:30:08.930 --> 00:30:08.940 align:start position:0% passport over right and identify 00:30:08.940 --> 00:30:11.270 align:start position:0% passport over right and identify yourself<00:30:09.420> completely<00:30:09.650> but<00:30:10.650> actually<00:30:11.040> can 00:30:11.270 --> 00:30:11.280 align:start position:0% yourself completely but actually can 00:30:11.280 --> 00:30:12.640 align:start position:0% yourself completely but actually can anybody<00:30:11.550> see<00:30:11.820> what<00:30:12.000> we 00:30:12.640 --> 00:30:12.650 align:start position:0% anybody see what we 00:30:12.650 --> 00:30:15.790 align:start position:0% anybody see what we to<00:30:12.980> get<00:30:13.130> into<00:30:13.250> the<00:30:13.370> Pelletier<00:30:13.820> age<00:30:14.360> page<00:30:15.170> and 00:30:15.790 --> 00:30:15.800 align:start position:0% to get into the Pelletier age page and 00:30:15.800 --> 00:30:18.760 align:start position:0% to get into the Pelletier age page and photo<00:30:16.150> right<00:30:17.150> and<00:30:17.390> actually<00:30:18.050> we're<00:30:18.560> doing<00:30:18.590> you 00:30:18.760 --> 00:30:18.770 align:start position:0% photo right and actually we're doing you 00:30:18.770 --> 00:30:21.220 align:start position:0% photo right and actually we're doing you really<00:30:18.980> want<00:30:19.310> to<00:30:19.400> say<00:30:19.550> you<00:30:19.880> know<00:30:20.000> how<00:30:20.870> old<00:30:21.080> is 00:30:21.220 --> 00:30:21.230 align:start position:0% really want to say you know how old is 00:30:21.230 --> 00:30:23.230 align:start position:0% really want to say you know how old is Davis<00:30:21.650> is<00:30:21.770> really<00:30:21.980> super<00:30:22.250> ancient<00:30:22.610> what<00:30:23.120> we 00:30:23.230 --> 00:30:23.240 align:start position:0% Davis is really super ancient what we 00:30:23.240 --> 00:30:24.730 align:start position:0% Davis is really super ancient what we really<00:30:23.480> just<00:30:23.660> want<00:30:23.840> to<00:30:23.900> say<00:30:23.990> is<00:30:24.050> he's<00:30:24.200> over<00:30:24.440> 18 00:30:24.730 --> 00:30:24.740 align:start position:0% really just want to say is he's over 18 00:30:24.740 --> 00:30:27.430 align:start position:0% really just want to say is he's over 18 right<00:30:25.280> so<00:30:25.520> that's<00:30:25.670> that's<00:30:26.150> that's<00:30:26.750> basically 00:30:27.430 --> 00:30:27.440 align:start position:0% right so that's that's that's basically 00:30:27.440 --> 00:30:29.830 align:start position:0% right so that's that's that's basically what<00:30:27.830> we<00:30:27.980> want<00:30:28.160> to<00:30:28.280> selectively<00:30:28.790> disclose<00:30:29.330> so 00:30:29.830 --> 00:30:29.840 align:start position:0% what we want to selectively disclose so 00:30:29.840 --> 00:30:32.380 align:start position:0% what we want to selectively disclose so coconut<00:30:30.170> allows<00:30:30.620> us<00:30:30.860> to<00:30:31.010> do<00:30:31.160> this 00:30:32.380 --> 00:30:32.390 align:start position:0% coconut allows us to do this 00:30:32.390 --> 00:30:34.600 align:start position:0% coconut allows us to do this so<00:30:33.110> you're<00:30:33.470> basically<00:30:33.560> signed<00:30:34.160> a<00:30:34.250> tuple<00:30:34.520> of 00:30:34.600 --> 00:30:34.610 align:start position:0% so you're basically signed a tuple of 00:30:34.610 --> 00:30:36.610 align:start position:0% so you're basically signed a tuple of all<00:30:34.760> fields<00:30:35.150> in<00:30:35.210> the<00:30:35.330> passport<00:30:35.510> and<00:30:36.080> when<00:30:36.530> it 00:30:36.610 --> 00:30:36.620 align:start position:0% all fields in the passport and when it 00:30:36.620 --> 00:30:38.530 align:start position:0% all fields in the passport and when it comes<00:30:36.710> to<00:30:36.890> verify<00:30:37.310> the<00:30:37.370> verifier<00:30:37.970> can<00:30:38.270> verify 00:30:38.530 --> 00:30:38.540 align:start position:0% comes to verify the verifier can verify 00:30:38.540 --> 00:30:41.380 align:start position:0% comes to verify the verifier can verify only<00:30:39.230> some<00:30:39.470> of<00:30:39.500> the<00:30:39.710> attributes<00:30:40.270> despite<00:30:41.270> the 00:30:41.380 --> 00:30:41.390 align:start position:0% only some of the attributes despite the 00:30:41.390 --> 00:30:42.400 align:start position:0% only some of the attributes despite the fact<00:30:41.540> that<00:30:41.600> the<00:30:41.750> rest<00:30:41.930> of<00:30:42.020> them<00:30:42.140> are<00:30:42.230> still 00:30:42.400 --> 00:30:42.410 align:start position:0% fact that the rest of them are still 00:30:42.410 --> 00:30:43.300 align:start position:0% fact that the rest of them are still there 00:30:43.300 --> 00:30:43.310 align:start position:0% there 00:30:43.310 --> 00:30:45.370 align:start position:0% there you<00:30:43.610> can<00:30:43.790> selectively<00:30:44.390> choose<00:30:44.810> to<00:30:45.080> quote 00:30:45.370 --> 00:30:45.380 align:start position:0% you can selectively choose to quote 00:30:45.380 --> 00:30:47.110 align:start position:0% you can selectively choose to quote disclose<00:30:45.860> these<00:30:46.100> things<00:30:46.340> and<00:30:46.670> you<00:30:46.970> can 00:30:47.110 --> 00:30:47.120 align:start position:0% disclose these things and you can 00:30:47.120 --> 00:30:48.760 align:start position:0% disclose these things and you can selectively<00:30:47.540> choose<00:30:47.840> to<00:30:47.990> declare<00:30:48.290> disclose 00:30:48.760 --> 00:30:48.770 align:start position:0% selectively choose to declare disclose 00:30:48.770 --> 00:30:50.590 align:start position:0% selectively choose to declare disclose from<00:30:49.160> different<00:30:49.550> ones<00:30:49.730> to<00:30:49.940> different<00:30:50.240> people 00:30:50.590 --> 00:30:50.600 align:start position:0% from different ones to different people 00:30:50.600 --> 00:30:54.280 align:start position:0% from different ones to different people basically<00:30:51.760> so<00:30:52.760> yeah<00:30:53.150> so<00:30:53.660> basically<00:30:53.810> we<00:30:54.140> have 00:30:54.280 --> 00:30:54.290 align:start position:0% basically so yeah so basically we have 00:30:54.290 --> 00:30:56.440 align:start position:0% basically so yeah so basically we have three<00:30:54.320> parties<00:30:54.800> we<00:30:55.640> have<00:30:55.760> the<00:30:55.910> passport 00:30:56.440 --> 00:30:56.450 align:start position:0% three parties we have the passport 00:30:56.450 --> 00:30:58.780 align:start position:0% three parties we have the passport authority<00:30:56.870> the<00:30:57.530> subject<00:30:57.950> that's<00:30:58.340> whoever 00:30:58.780 --> 00:30:58.790 align:start position:0% authority the subject that's whoever 00:30:58.790 --> 00:31:00.760 align:start position:0% authority the subject that's whoever wants<00:30:59.060> to<00:30:59.090> go<00:30:59.180> in<00:30:59.300> the<00:30:59.360> pub<00:30:59.540> and<00:30:59.870> then<00:31:00.530> we<00:31:00.620> have 00:31:00.760 --> 00:31:00.770 align:start position:0% wants to go in the pub and then we have 00:31:00.770 --> 00:31:02.800 align:start position:0% wants to go in the pub and then we have the<00:31:00.950> the<00:31:01.160> relying<00:31:01.490> party<00:31:01.610> we<00:31:02.090> call<00:31:02.270> it<00:31:02.420> which 00:31:02.800 --> 00:31:02.810 align:start position:0% the the relying party we call it which 00:31:02.810 --> 00:31:04.930 align:start position:0% the the relying party we call it which is<00:31:03.110> the<00:31:03.260> bouncer<00:31:03.620> at<00:31:03.800> the<00:31:03.920> pub<00:31:04.100> door<00:31:04.280> right<00:31:04.700> and 00:31:04.930 --> 00:31:04.940 align:start position:0% is the bouncer at the pub door right and 00:31:04.940 --> 00:31:07.120 align:start position:0% is the bouncer at the pub door right and you<00:31:05.750> can<00:31:05.900> basically<00:31:06.080> choose<00:31:06.320> to<00:31:06.680> selectively 00:31:07.120 --> 00:31:07.130 align:start position:0% you can basically choose to selectively 00:31:07.130 --> 00:31:09.910 align:start position:0% you can basically choose to selectively disclose<00:31:07.820> some<00:31:08.630> or<00:31:08.870> all<00:31:09.080> of<00:31:09.110> the<00:31:09.500> attributes 00:31:09.910 --> 00:31:09.920 align:start position:0% disclose some or all of the attributes 00:31:09.920 --> 00:31:14.560 align:start position:0% disclose some or all of the attributes of<00:31:10.010> the<00:31:10.100> message<00:31:11.170> so<00:31:13.120> when<00:31:14.120> you<00:31:14.210> put<00:31:14.390> it<00:31:14.480> all 00:31:14.560 --> 00:31:14.570 align:start position:0% of the message so when you put it all 00:31:14.570 --> 00:31:16.900 align:start position:0% of the message so when you put it all together<00:31:14.830> selective<00:31:15.830> disclosure<00:31:16.010> can<00:31:16.730> be 00:31:16.900 --> 00:31:16.910 align:start position:0% together selective disclosure can be 00:31:16.910 --> 00:31:19.480 align:start position:0% together selective disclosure can be applied<00:31:17.240> to<00:31:17.620> normal<00:31:18.620> signature<00:31:19.190> schemes 00:31:19.480 --> 00:31:19.490 align:start position:0% applied to normal signature schemes 00:31:19.490 --> 00:31:21.550 align:start position:0% applied to normal signature schemes without<00:31:19.850> winding<00:31:20.150> without<00:31:20.990> reran<00:31:21.320> demise 00:31:21.550 --> 00:31:21.560 align:start position:0% without winding without reran demise 00:31:21.560 --> 00:31:23.950 align:start position:0% without winding without reran demise ation<00:31:21.860> so<00:31:22.400> you<00:31:23.150> can<00:31:23.240> get<00:31:23.360> a<00:31:23.390> signed<00:31:23.630> message 00:31:23.950 --> 00:31:23.960 align:start position:0% ation so you can get a signed message 00:31:23.960 --> 00:31:25.870 align:start position:0% ation so you can get a signed message from<00:31:24.200> an<00:31:24.320> authority<00:31:24.740> and<00:31:24.980> disclose<00:31:25.670> them 00:31:25.870 --> 00:31:25.880 align:start position:0% from an authority and disclose them 00:31:25.880 --> 00:31:29.020 align:start position:0% from an authority and disclose them selectively<00:31:26.440> and<00:31:27.440> this<00:31:27.950> provides<00:31:28.340> privacy 00:31:29.020 --> 00:31:29.030 align:start position:0% selectively and this provides privacy 00:31:29.030 --> 00:31:31.210 align:start position:0% selectively and this provides privacy against<00:31:29.330> the<00:31:29.780> relying<00:31:30.350> party<00:31:30.410> the<00:31:30.890> bouncer 00:31:31.210 --> 00:31:31.220 align:start position:0% against the relying party the bouncer 00:31:31.220 --> 00:31:33.370 align:start position:0% against the relying party the bouncer and<00:31:31.400> also<00:31:32.300> against<00:31:32.600> the<00:31:32.690> passport<00:31:33.110> of<00:31:33.200> 30 00:31:33.370 --> 00:31:33.380 align:start position:0% and also against the passport of 30 00:31:33.380 --> 00:31:34.810 align:start position:0% and also against the passport of 30 right 00:31:34.810 --> 00:31:34.820 align:start position:0% right 00:31:34.820 --> 00:31:38.770 align:start position:0% right oh<00:31:36.160> sorry<00:31:37.160> if<00:31:37.790> you<00:31:38.000> go<00:31:38.150> to<00:31:38.210> this<00:31:38.330> if<00:31:38.540> you<00:31:38.630> go<00:31:38.720> to 00:31:38.770 --> 00:31:38.780 align:start position:0% oh sorry if you go to this if you go to 00:31:38.780 --> 00:31:42.220 align:start position:0% oh sorry if you go to this if you go to the<00:31:38.900> pub<00:31:39.050> again<00:31:39.200> or<00:31:40.160> if<00:31:40.970> the<00:31:41.300> if<00:31:41.660> the<00:31:41.780> passport 00:31:42.220 --> 00:31:42.230 align:start position:0% the pub again or if the if the passport 00:31:42.230 --> 00:31:44.050 align:start position:0% the pub again or if the if the passport authority<00:31:42.560> wants<00:31:42.680> to<00:31:42.980> without<00:31:43.580> the<00:31:43.700> other 00:31:44.050 --> 00:31:44.060 align:start position:0% authority wants to without the other 00:31:44.060 --> 00:31:47.470 align:start position:0% authority wants to without the other properties<00:31:44.860> that<00:31:45.860> is<00:31:46.040> blind<00:31:46.970> issuance<00:31:47.330> and 00:31:47.470 --> 00:31:47.480 align:start position:0% properties that is blind issuance and 00:31:47.480 --> 00:31:49.690 align:start position:0% properties that is blind issuance and rear<00:31:47.600> analyzable<00:31:48.050> signatures<00:31:48.560> they<00:31:49.520> can 00:31:49.690 --> 00:31:49.700 align:start position:0% rear analyzable signatures they can 00:31:49.700 --> 00:31:51.250 align:start position:0% rear analyzable signatures they can identify<00:31:49.910> you<00:31:50.300> the<00:31:50.510> second<00:31:50.840> time<00:31:50.960> you<00:31:51.050> go<00:31:51.170> to 00:31:51.250 --> 00:31:51.260 align:start position:0% identify you the second time you go to 00:31:51.260 --> 00:31:53.110 align:start position:0% identify you the second time you go to the<00:31:51.350> pub<00:31:51.500> as<00:31:51.680> being<00:31:51.860> the<00:31:51.920> same<00:31:52.100> person<00:31:52.130> right 00:31:53.110 --> 00:31:53.120 align:start position:0% the pub as being the same person right 00:31:53.120 --> 00:31:55.150 align:start position:0% the pub as being the same person right or<00:31:53.540> the<00:31:53.900> passport<00:31:54.320> authority<00:31:54.680> to<00:31:54.800> break<00:31:55.010> your 00:31:55.150 --> 00:31:55.160 align:start position:0% or the passport authority to break your 00:31:55.160 --> 00:31:56.830 align:start position:0% or the passport authority to break your anonymity<00:31:55.430> if<00:31:55.730> they<00:31:55.850> wanted<00:31:56.090> to<00:31:56.240> if<00:31:56.570> we 00:31:56.830 --> 00:31:56.840 align:start position:0% anonymity if they wanted to if we 00:31:56.840 --> 00:31:59.830 align:start position:0% anonymity if they wanted to if we combine<00:31:57.320> all<00:31:57.710> of<00:31:58.310> these<00:31:58.670> things<00:31:58.840> blinded 00:31:59.830 --> 00:31:59.840 align:start position:0% combine all of these things blinded 00:31:59.840 --> 00:32:02.050 align:start position:0% combine all of these things blinded credentials<00:32:00.350> re<00:32:01.010> randomize<00:32:01.400> Mel<00:32:01.610> signatures 00:32:02.050 --> 00:32:02.060 align:start position:0% credentials re randomize Mel signatures 00:32:02.060 --> 00:32:04.660 align:start position:0% credentials re randomize Mel signatures and<00:32:02.360> selective<00:32:03.200> disclosure<00:32:03.350> we<00:32:04.190> can<00:32:04.400> protect 00:32:04.660 --> 00:32:04.670 align:start position:0% and selective disclosure we can protect 00:32:04.670 --> 00:32:06.850 align:start position:0% and selective disclosure we can protect the<00:32:04.790> users<00:32:05.030> provide<00:32:05.410> privacy<00:32:06.410> against 00:32:06.850 --> 00:32:06.860 align:start position:0% the users provide privacy against 00:32:06.860 --> 00:32:09.220 align:start position:0% the users provide privacy against multiple<00:32:07.700> shows<00:32:08.000> that<00:32:08.450> is<00:32:08.600> uses<00:32:08.990> of<00:32:09.140> the 00:32:09.220 --> 00:32:09.230 align:start position:0% multiple shows that is uses of the 00:32:09.230 --> 00:32:11.410 align:start position:0% multiple shows that is uses of the credential<00:32:09.680> at<00:32:10.310> the<00:32:10.490> pub<00:32:10.670> so<00:32:11.000> the<00:32:11.090> bouncer 00:32:11.410 --> 00:32:11.420 align:start position:0% credential at the pub so the bouncer 00:32:11.420 --> 00:32:12.490 align:start position:0% credential at the pub so the bouncer will<00:32:11.600> always<00:32:11.840> think<00:32:11.990> it's<00:32:12.080> the<00:32:12.110> first<00:32:12.350> time 00:32:12.490 --> 00:32:12.500 align:start position:0% will always think it's the first time 00:32:12.500 --> 00:32:13.130 align:start position:0% will always think it's the first time you've<00:32:12.680> been<00:32:12.710> there 00:32:13.130 --> 00:32:13.140 align:start position:0% you've been there 00:32:13.140 --> 00:32:14.419 align:start position:0% you've been there which<00:32:13.320> might<00:32:13.500> be<00:32:13.650> important<00:32:14.070> in<00:32:14.160> certain 00:32:14.419 --> 00:32:14.429 align:start position:0% which might be important in certain 00:32:14.429 --> 00:32:16.910 align:start position:0% which might be important in certain applications<00:32:14.960> and<00:32:15.960> we<00:32:16.170> can<00:32:16.320> also<00:32:16.410> protect<00:32:16.770> you 00:32:16.910 --> 00:32:16.920 align:start position:0% applications and we can also protect you 00:32:16.920 --> 00:32:18.710 align:start position:0% applications and we can also protect you against<00:32:17.220> the<00:32:17.309> passport<00:32:17.730> Authority<00:32:18.120> who<00:32:18.600> has 00:32:18.710 --> 00:32:18.720 align:start position:0% against the passport Authority who has 00:32:18.720 --> 00:32:21.020 align:start position:0% against the passport Authority who has no<00:32:18.900> way<00:32:19.080> of<00:32:19.110> linking<00:32:19.470> the<00:32:20.370> credentials<00:32:20.910> you're 00:32:21.020 --> 00:32:21.030 align:start position:0% no way of linking the credentials you're 00:32:21.030 --> 00:32:24.230 align:start position:0% no way of linking the credentials you're using<00:32:21.210> to<00:32:21.480> what<00:32:21.660> they've<00:32:21.870> issued<00:32:22.080> now<00:32:23.150> keep<00:32:24.150> in 00:32:24.230 --> 00:32:24.240 align:start position:0% using to what they've issued now keep in 00:32:24.240 --> 00:32:25.490 align:start position:0% using to what they've issued now keep in mind<00:32:24.450> we're<00:32:24.780> not<00:32:24.809> really<00:32:25.140> talking<00:32:25.380> about 00:32:25.490 --> 00:32:25.500 align:start position:0% mind we're not really talking about 00:32:25.500 --> 00:32:27.500 align:start position:0% mind we're not really talking about making<00:32:25.770> a<00:32:25.980> passport<00:32:26.160> Authority<00:32:26.760> any<00:32:27.090> kind<00:32:27.420> of 00:32:27.500 --> 00:32:27.510 align:start position:0% making a passport Authority any kind of 00:32:27.510 --> 00:32:28.880 align:start position:0% making a passport Authority any kind of authority<00:32:27.630> that<00:32:28.140> you<00:32:28.230> want<00:32:28.410> to<00:32:28.500> have<00:32:28.590> it<00:32:28.740> can 00:32:28.880 --> 00:32:28.890 align:start position:0% authority that you want to have it can 00:32:28.890 --> 00:32:30.650 align:start position:0% authority that you want to have it can assert<00:32:29.160> any<00:32:29.400> useful<00:32:30.030> information<00:32:30.150> about 00:32:30.650 --> 00:32:30.660 align:start position:0% assert any useful information about 00:32:30.660 --> 00:32:32.930 align:start position:0% assert any useful information about anything<00:32:31.590> in<00:32:31.890> your<00:32:32.010> applications<00:32:32.580> can<00:32:32.700> be 00:32:32.930 --> 00:32:32.940 align:start position:0% anything in your applications can be 00:32:32.940 --> 00:32:38.180 align:start position:0% anything in your applications can be contained<00:32:33.299> inside<00:32:34.280> an<00:32:35.280> in<00:32:35.460> credentials 00:32:38.180 --> 00:32:38.190 align:start position:0% 00:32:38.190 --> 00:32:40.419 align:start position:0% so<00:32:38.580> all<00:32:38.880> the<00:32:39.030> elements<00:32:39.390> thus<00:32:39.600> far 00:32:40.419 --> 00:32:40.429 align:start position:0% so all the elements thus far 00:32:40.429 --> 00:32:44.330 align:start position:0% so all the elements thus far basically<00:32:42.590> existed<00:32:43.590> in<00:32:43.679> the<00:32:43.770> cryptography 00:32:44.330 --> 00:32:44.340 align:start position:0% basically existed in the cryptography 00:32:44.340 --> 00:32:46.100 align:start position:0% basically existed in the cryptography literature<00:32:44.730> and<00:32:45.000> we<00:32:45.419> were<00:32:45.600> we're<00:32:45.960> just 00:32:46.100 --> 00:32:46.110 align:start position:0% literature and we were we're just 00:32:46.110 --> 00:32:47.510 align:start position:0% literature and we were we're just stringing<00:32:46.350> them<00:32:46.559> together<00:32:46.740> so<00:32:47.220> like<00:32:47.340> this 00:32:47.510 --> 00:32:47.520 align:start position:0% stringing them together so like this 00:32:47.520 --> 00:32:50.240 align:start position:0% stringing them together so like this isn't<00:32:47.820> some<00:32:48.030> you<00:32:48.960> know<00:32:49.080> mind<00:32:49.559> blowing<00:32:49.919> the<00:32:50.070> new 00:32:50.240 --> 00:32:50.250 align:start position:0% isn't some you know mind blowing the new 00:32:50.250 --> 00:32:52.460 align:start position:0% isn't some you know mind blowing the new set<00:32:50.640> of<00:32:50.669> things<00:32:51.360> maybe<00:32:51.840> you<00:32:51.929> haven't<00:32:52.140> heard<00:32:52.350> of 00:32:52.460 --> 00:32:52.470 align:start position:0% set of things maybe you haven't heard of 00:32:52.470 --> 00:32:53.930 align:start position:0% set of things maybe you haven't heard of it<00:32:52.559> before<00:32:52.679> but<00:32:52.919> all<00:32:53.400> of<00:32:53.669> this<00:32:53.730> stuff 00:32:53.930 --> 00:32:53.940 align:start position:0% it before but all of this stuff 00:32:53.940 --> 00:32:56.750 align:start position:0% it before but all of this stuff basically<00:32:54.360> exists<00:32:54.950> but<00:32:55.950> they<00:32:56.070> only<00:32:56.220> existed 00:32:56.750 --> 00:32:56.760 align:start position:0% basically exists but they only existed 00:32:56.760 --> 00:32:59.299 align:start position:0% basically exists but they only existed in<00:32:56.850> centralized<00:32:57.390> systems<00:32:57.780> so<00:32:58.350> up<00:32:58.890> until<00:32:59.100> now 00:32:59.299 --> 00:32:59.309 align:start position:0% in centralized systems so up until now 00:32:59.309 --> 00:33:01.190 align:start position:0% in centralized systems so up until now it's<00:32:59.730> been<00:32:59.790> impossible<00:33:00.240> to<00:33:00.570> string<00:33:01.049> these 00:33:01.190 --> 00:33:01.200 align:start position:0% it's been impossible to string these 00:33:01.200 --> 00:33:03.169 align:start position:0% it's been impossible to string these things<00:33:01.470> together<00:33:01.620> in<00:33:01.860> decentralized<00:33:02.850> systems 00:33:03.169 --> 00:33:03.179 align:start position:0% things together in decentralized systems 00:33:03.179 --> 00:33:04.460 align:start position:0% things together in decentralized systems and<00:33:03.419> that's<00:33:03.809> what 00:33:04.460 --> 00:33:04.470 align:start position:0% and that's what 00:33:04.470 --> 00:33:06.409 align:start position:0% and that's what kokin<00:33:04.919> Eyes<00:33:05.040> coconut<00:33:05.669> basically<00:33:06.059> gives<00:33:06.240> you 00:33:06.409 --> 00:33:06.419 align:start position:0% kokin Eyes coconut basically gives you 00:33:06.419 --> 00:33:10.460 align:start position:0% kokin Eyes coconut basically gives you is<00:33:06.870> this<00:33:07.049> one<00:33:07.380> more<00:33:07.590> thing<00:33:09.440> which<00:33:10.440> is 00:33:10.460 --> 00:33:10.470 align:start position:0% is this one more thing which is 00:33:10.470 --> 00:33:12.560 align:start position:0% is this one more thing which is threshold<00:33:11.220> issuance<00:33:11.640> so<00:33:12.030> you<00:33:12.090> can<00:33:12.419> actually 00:33:12.560 --> 00:33:12.570 align:start position:0% threshold issuance so you can actually 00:33:12.570 --> 00:33:15.799 align:start position:0% threshold issuance so you can actually have<00:33:13.320> a<00:33:13.890> decentralized<00:33:14.429> set<00:33:15.090> of<00:33:15.270> authorities 00:33:15.799 --> 00:33:15.809 align:start position:0% have a decentralized set of authorities 00:33:15.809 --> 00:33:19.060 align:start position:0% have a decentralized set of authorities all<00:33:16.309> generating<00:33:17.309> the<00:33:17.370> part<00:33:17.610> of<00:33:17.790> a<00:33:17.880> credential 00:33:19.060 --> 00:33:19.070 align:start position:0% all generating the part of a credential 00:33:19.070 --> 00:33:26.419 align:start position:0% all generating the part of a credential so<00:33:21.799> that<00:33:22.799> allows<00:33:23.040> the<00:33:23.429> the<00:33:23.900> kind<00:33:24.900> of<00:33:25.429> the 00:33:26.419 --> 00:33:26.429 align:start position:0% so that allows the the kind of the 00:33:26.429 --> 00:33:28.010 align:start position:0% so that allows the the kind of the decentralization<00:33:27.240> of<00:33:27.630> the<00:33:27.750> kind<00:33:27.960> of 00:33:28.010 --> 00:33:28.020 align:start position:0% decentralization of the kind of 00:33:28.020 --> 00:33:30.200 align:start position:0% decentralization of the kind of blockchain<00:33:28.440> ization<00:33:28.799> of<00:33:29.090> abusing<00:33:30.090> these 00:33:30.200 --> 00:33:30.210 align:start position:0% blockchain ization of abusing these 00:33:30.210 --> 00:33:31.669 align:start position:0% blockchain ization of abusing these kinds<00:33:30.570> of<00:33:30.660> attributes<00:33:30.780> for<00:33:31.200> the<00:33:31.290> first<00:33:31.470> time 00:33:31.669 --> 00:33:31.679 align:start position:0% kinds of attributes for the first time 00:33:31.679 --> 00:33:32.990 align:start position:0% kinds of attributes for the first time so<00:33:31.799> we're<00:33:31.919> not<00:33:32.010> aware<00:33:32.130> of<00:33:32.309> anybody<00:33:32.490> else<00:33:32.820> who's 00:33:32.990 --> 00:33:33.000 align:start position:0% so we're not aware of anybody else who's 00:33:33.000 --> 00:33:36.500 align:start position:0% so we're not aware of anybody else who's done<00:33:33.210> this<00:33:33.830> so<00:33:34.830> it<00:33:34.919> makes<00:33:35.130> all<00:33:35.910> of<00:33:35.970> these<00:33:36.270> other 00:33:36.500 --> 00:33:36.510 align:start position:0% done this so it makes all of these other 00:33:36.510 --> 00:33:39.080 align:start position:0% done this so it makes all of these other things<00:33:37.080> like<00:33:37.440> blind<00:33:37.710> issuance<00:33:38.130> rear<00:33:38.880> end<00:33:39.000> of 00:33:39.080 --> 00:33:39.090 align:start position:0% things like blind issuance rear end of 00:33:39.090 --> 00:33:41.150 align:start position:0% things like blind issuance rear end of my<00:33:39.150> signature<00:33:39.510> selective<00:33:40.110> disclosure<00:33:40.230> use<00:33:41.130> a 00:33:41.150 --> 00:33:41.160 align:start position:0% my signature selective disclosure use a 00:33:41.160 --> 00:33:43.700 align:start position:0% my signature selective disclosure use a bowl<00:33:41.429> in<00:33:41.669> a<00:33:41.760> blockchain<00:33:41.970> context<00:33:42.600> so<00:33:43.440> this<00:33:43.559> is 00:33:43.700 --> 00:33:43.710 align:start position:0% bowl in a blockchain context so this is 00:33:43.710 --> 00:33:46.850 align:start position:0% bowl in a blockchain context so this is known<00:33:44.040> as<00:33:44.340> a<00:33:44.370> threshold<00:33:45.090> signature<00:33:45.840> scheme<00:33:46.080> so 00:33:46.850 --> 00:33:46.860 align:start position:0% known as a threshold signature scheme so 00:33:46.860 --> 00:33:49.730 align:start position:0% known as a threshold signature scheme so that's<00:33:47.700> basically<00:33:48.540> what<00:33:48.840> coconut<00:33:49.350> does<00:33:49.559> and 00:33:49.730 --> 00:33:49.740 align:start position:0% that's basically what coconut does and 00:33:49.740 --> 00:33:51.710 align:start position:0% that's basically what coconut does and what<00:33:49.860> the<00:33:49.950> mix<00:33:50.100> that<00:33:50.280> does<00:33:50.460> well<00:33:50.910> they'll 00:33:51.710 --> 00:33:51.720 align:start position:0% what the mix that does well they'll 00:33:51.720 --> 00:33:53.270 align:start position:0% what the mix that does well they'll break<00:33:51.900> for<00:33:52.169> some<00:33:52.320> questions<00:33:52.740> here<00:33:52.980> just<00:33:53.160> to 00:33:53.270 --> 00:33:53.280 align:start position:0% break for some questions here just to 00:33:53.280 --> 00:33:56.299 align:start position:0% break for some questions here just to keep<00:33:53.400> things<00:33:53.640> going<00:33:54.440> back<00:33:55.440> and<00:33:55.590> forth<00:33:55.860> and 00:33:56.299 --> 00:33:56.309 align:start position:0% keep things going back and forth and 00:33:56.309 --> 00:33:58.640 align:start position:0% keep things going back and forth and then<00:33:56.490> I'll<00:33:56.580> do<00:33:56.760> a<00:33:57.450> quick<00:33:58.020> architecture 00:33:58.640 --> 00:33:58.650 align:start position:0% then I'll do a quick architecture 00:33:58.650 --> 00:33:59.990 align:start position:0% then I'll do a quick architecture diagram<00:33:59.040> of<00:33:59.190> what<00:33:59.340> we<00:33:59.429> have<00:33:59.549> running<00:33:59.850> right 00:33:59.990 --> 00:34:00.000 align:start position:0% diagram of what we have running right 00:34:00.000 --> 00:34:01.549 align:start position:0% diagram of what we have running right now<00:34:00.150> and<00:34:00.299> then<00:34:00.390> I'll<00:34:00.480> show<00:34:00.690> thee<00:34:01.260> that<00:34:01.440> can 00:34:01.549 --> 00:34:01.559 align:start position:0% now and then I'll show thee that can 00:34:01.559 --> 00:34:03.440 align:start position:0% now and then I'll show thee that can show<00:34:01.799> some<00:34:02.520> of<00:34:02.640> this<00:34:02.730> stuff<00:34:02.940> in<00:34:03.090> action 00:34:03.440 --> 00:34:03.450 align:start position:0% show some of this stuff in action 00:34:03.450 --> 00:34:08.070 align:start position:0% show some of this stuff in action yeah<00:34:03.840> cool<00:34:04.230> so<00:34:04.470> questions<00:34:04.980> any 00:34:08.070 --> 00:34:08.080 align:start position:0% 00:34:08.080 --> 00:34:20.340 align:start position:0% yeah<00:34:18.090> okay<00:34:19.090> so<00:34:19.180> the<00:34:19.450> question<00:34:19.570> is<00:34:19.930> what<00:34:20.170> is 00:34:20.340 --> 00:34:20.350 align:start position:0% yeah okay so the question is what is 00:34:20.350 --> 00:34:22.890 align:start position:0% yeah okay so the question is what is that<00:34:20.380> timing<00:34:20.890> in<00:34:21.160> replay<00:34:21.460> attack<00:34:21.900> so 00:34:22.890 --> 00:34:22.900 align:start position:0% that timing in replay attack so 00:34:22.900 --> 00:34:26.220 align:start position:0% that timing in replay attack so attacking<00:34:23.290> attack<00:34:23.740> is<00:34:23.980> if<00:34:24.340> the<00:34:24.660> adversary<00:34:25.660> is 00:34:26.220 --> 00:34:26.230 align:start position:0% attacking attack is if the adversary is 00:34:26.230 --> 00:34:30.090 align:start position:0% attacking attack is if the adversary is able<00:34:26.830> to<00:34:27.160> slip<00:34:27.850> to<00:34:28.210> snip<00:34:28.780> a<00:34:29.020> package<00:34:29.530> going<00:34:29.800> for 00:34:30.090 --> 00:34:30.100 align:start position:0% able to slip to snip a package going for 00:34:30.100 --> 00:34:32.250 align:start position:0% able to slip to snip a package going for the<00:34:30.190> network<00:34:30.550> and<00:34:30.850> then<00:34:31.030> sleep<00:34:31.540> like<00:34:31.750> a<00:34:31.780> single 00:34:32.250 --> 00:34:32.260 align:start position:0% the network and then sleep like a single 00:34:32.260 --> 00:34:34.650 align:start position:0% the network and then sleep like a single bit<00:34:32.440> for<00:34:32.680> example<00:34:32.800> in<00:34:33.550> order<00:34:33.820> to<00:34:34.090> be<00:34:34.210> able<00:34:34.390> to 00:34:34.650 --> 00:34:34.660 align:start position:0% bit for example in order to be able to 00:34:34.660 --> 00:34:37.200 align:start position:0% bit for example in order to be able to like<00:34:34.980> trace<00:34:35.980> this<00:34:36.280> packet<00:34:36.640> per<00:34:36.850> day<00:34:37.060> in<00:34:37.180> the 00:34:37.200 --> 00:34:37.210 align:start position:0% like trace this packet per day in the 00:34:37.210 --> 00:34:38.810 align:start position:0% like trace this packet per day in the network<00:34:37.720> so<00:34:37.840> if<00:34:37.990> you<00:34:38.110> don't<00:34:38.290> have<00:34:38.470> a 00:34:38.810 --> 00:34:38.820 align:start position:0% network so if you don't have a 00:34:38.820 --> 00:34:41.550 align:start position:0% network so if you don't have a cryptographic<00:34:39.820> packet<00:34:40.390> for<00:34:40.570> my<00:34:40.720> schedule<00:34:41.080> to 00:34:41.550 --> 00:34:41.560 align:start position:0% cryptographic packet for my schedule to 00:34:41.560 --> 00:34:44.010 align:start position:0% cryptographic packet for my schedule to be<00:34:41.680> resistant<00:34:42.250> to<00:34:42.310> that<00:34:42.520> it<00:34:43.240> will<00:34:43.390> just<00:34:43.630> flip<00:34:43.990> a 00:34:44.010 --> 00:34:44.020 align:start position:0% be resistant to that it will just flip a 00:34:44.020 --> 00:34:45.630 align:start position:0% be resistant to that it will just flip a bit<00:34:44.290> and<00:34:44.530> then<00:34:44.710> you<00:34:44.770> will<00:34:44.890> be<00:34:45.010> able<00:34:45.100> to<00:34:45.400> trace 00:34:45.630 --> 00:34:45.640 align:start position:0% bit and then you will be able to trace 00:34:45.640 --> 00:34:48.000 align:start position:0% bit and then you will be able to trace the<00:34:45.820> packet<00:34:46.150> the<00:34:46.570> replay<00:34:46.900> attack<00:34:47.230> a<00:34:47.470> can<00:34:47.890> be 00:34:48.000 --> 00:34:48.010 align:start position:0% the packet the replay attack a can be 00:34:48.010 --> 00:34:49.770 align:start position:0% the packet the replay attack a can be used<00:34:48.190> also<00:34:48.340> for<00:34:48.520> tagging<00:34:49.060> it<00:34:49.270> means<00:34:49.540> that 00:34:49.770 --> 00:34:49.780 align:start position:0% used also for tagging it means that 00:34:49.780 --> 00:34:52.110 align:start position:0% used also for tagging it means that you're<00:34:50.380> repeating<00:34:50.920> the<00:34:50.950> same<00:34:51.280> packet<00:34:51.760> once 00:34:52.110 --> 00:34:52.120 align:start position:0% you're repeating the same packet once 00:34:52.120 --> 00:34:55.140 align:start position:0% you're repeating the same packet once again<00:34:52.560> just<00:34:53.560> for<00:34:53.710> example<00:34:54.160> to<00:34:54.310> see<00:34:54.520> where<00:34:55.030> it 00:34:55.140 --> 00:34:55.150 align:start position:0% again just for example to see where it 00:34:55.150 --> 00:34:57.390 align:start position:0% again just for example to see where it will<00:34:55.330> go<00:34:55.480> again<00:34:55.750> so<00:34:55.900> you're<00:34:56.080> able<00:34:56.620> to<00:34:56.950> sniff<00:34:57.250> it 00:34:57.390 --> 00:34:57.400 align:start position:0% will go again so you're able to sniff it 00:34:57.400 --> 00:35:03.000 align:start position:0% will go again so you're able to sniff it and<00:34:57.580> then<00:34:58.120> resend<00:34:58.720> it<00:34:58.810> again 00:35:03.000 --> 00:35:03.010 align:start position:0% 00:35:03.010 --> 00:35:05.580 align:start position:0% you<00:35:03.370> mentioned<00:35:03.760> that<00:35:03.820> you<00:35:04.360> like<00:35:05.080> set<00:35:05.320> out<00:35:05.410> to 00:35:05.580 --> 00:35:05.590 align:start position:0% you mentioned that you like set out to 00:35:05.590 --> 00:35:07.110 align:start position:0% you mentioned that you like set out to basically<00:35:05.740> build<00:35:06.310> something<00:35:06.820> that's<00:35:06.970> better 00:35:07.110 --> 00:35:07.120 align:start position:0% basically build something that's better 00:35:07.120 --> 00:35:08.870 align:start position:0% basically build something that's better than<00:35:07.360> tour<00:35:07.630> in<00:35:07.930> terms<00:35:08.200> of<00:35:08.350> network<00:35:08.590> security 00:35:08.870 --> 00:35:08.880 align:start position:0% than tour in terms of network security 00:35:08.880 --> 00:35:11.490 align:start position:0% than tour in terms of network security so<00:35:09.880> the<00:35:10.000> main<00:35:10.180> attack<00:35:10.450> against<00:35:10.900> tor<00:35:11.200> is 00:35:11.490 --> 00:35:11.500 align:start position:0% so the main attack against tor is 00:35:11.500 --> 00:35:13.740 align:start position:0% so the main attack against tor is essentially<00:35:12.130> a<00:35:12.160> government<00:35:12.850> agency<00:35:13.120> running 00:35:13.740 --> 00:35:13.750 align:start position:0% essentially a government agency running 00:35:13.750 --> 00:35:17.400 align:start position:0% essentially a government agency running like<00:35:14.230> over<00:35:14.650> 30%<00:35:15.460> of<00:35:15.490> all<00:35:15.760> nodes<00:35:16.150> and<00:35:16.600> by<00:35:17.110> having 00:35:17.400 --> 00:35:17.410 align:start position:0% like over 30% of all nodes and by having 00:35:17.410 --> 00:35:19.050 align:start position:0% like over 30% of all nodes and by having a<00:35:17.470> majority<00:35:17.890> of<00:35:17.920> exit<00:35:18.310> nodes<00:35:18.580> they<00:35:18.730> just<00:35:18.910> see 00:35:19.050 --> 00:35:19.060 align:start position:0% a majority of exit nodes they just see 00:35:19.060 --> 00:35:21.630 align:start position:0% a majority of exit nodes they just see where<00:35:19.210> the<00:35:19.390> all<00:35:19.600> the<00:35:19.780> packets<00:35:20.110> end<00:35:20.290> up<00:35:20.580> how<00:35:21.580> do 00:35:21.630 --> 00:35:21.640 align:start position:0% where the all the packets end up how do 00:35:21.640 --> 00:35:24.330 align:start position:0% where the all the packets end up how do you<00:35:21.970> address<00:35:22.240> that<00:35:22.360> attack<00:35:22.930> so<00:35:23.590> for<00:35:23.890> example 00:35:24.330 --> 00:35:24.340 align:start position:0% you address that attack so for example 00:35:24.340 --> 00:35:25.980 align:start position:0% you address that attack so for example the<00:35:24.640> thinking<00:35:24.970> tour<00:35:25.210> is<00:35:25.360> that<00:35:25.570> all<00:35:25.810> the 00:35:25.980 --> 00:35:25.990 align:start position:0% the thinking tour is that all the 00:35:25.990 --> 00:35:27.870 align:start position:0% the thinking tour is that all the packets<00:35:26.290> are<00:35:26.410> going<00:35:26.680> like<00:35:27.220> all<00:35:27.460> of<00:35:27.760> your 00:35:27.870 --> 00:35:27.880 align:start position:0% packets are going like all of your 00:35:27.880 --> 00:35:29.370 align:start position:0% packets are going like all of your packets<00:35:28.360> from<00:35:28.480> the<00:35:28.630> nation<00:35:28.900> packets<00:35:29.200> are 00:35:29.370 --> 00:35:29.380 align:start position:0% packets from the nation packets are 00:35:29.380 --> 00:35:32.490 align:start position:0% packets from the nation packets are going<00:35:29.590> by<00:35:29.770> the<00:35:29.830> same<00:35:30.190> circuit<00:35:31.060> and<00:35:31.600> so<00:35:32.350> with 00:35:32.490 --> 00:35:32.500 align:start position:0% going by the same circuit and so with 00:35:32.500 --> 00:35:35.070 align:start position:0% going by the same circuit and so with the<00:35:32.620> same<00:35:32.830> entry<00:35:33.310> and<00:35:33.490> exit<00:35:33.790> knob<00:35:33.970> here<00:35:34.750> in<00:35:34.990> the 00:35:35.070 --> 00:35:35.080 align:start position:0% the same entry and exit knob here in the 00:35:35.080 --> 00:35:37.290 align:start position:0% the same entry and exit knob here in the mix<00:35:35.290> Network<00:35:35.680> effort<00:35:36.220> packet<00:35:36.550> is<00:35:36.670> going<00:35:36.940> by<00:35:37.090> an 00:35:37.290 --> 00:35:37.300 align:start position:0% mix Network effort packet is going by an 00:35:37.300 --> 00:35:39.540 align:start position:0% mix Network effort packet is going by an independent<00:35:37.600> path<00:35:38.200> which<00:35:38.950> is<00:35:38.980> selected 00:35:39.540 --> 00:35:39.550 align:start position:0% independent path which is selected 00:35:39.550 --> 00:35:42.240 align:start position:0% independent path which is selected randomly<00:35:39.730> so<00:35:40.690> this<00:35:40.840> is<00:35:41.020> already<00:35:41.230> causing<00:35:42.040> a 00:35:42.240 --> 00:35:42.250 align:start position:0% randomly so this is already causing a 00:35:42.250 --> 00:35:43.800 align:start position:0% randomly so this is already causing a little<00:35:42.340> a<00:35:42.610> little<00:35:42.790> bit<00:35:42.940> of<00:35:43.150> trouble<00:35:43.540> because 00:35:43.800 --> 00:35:43.810 align:start position:0% little a little bit of trouble because 00:35:43.810 --> 00:35:46.610 align:start position:0% little a little bit of trouble because then<00:35:44.110> it's<00:35:44.470> not<00:35:44.620> that<00:35:44.770> the<00:35:44.920> agent<00:35:45.340> I<00:35:45.400> just<00:35:45.820> know 00:35:46.610 --> 00:35:46.620 align:start position:0% then it's not that the agent I just know 00:35:46.620 --> 00:35:49.320 align:start position:0% then it's not that the agent I just know like<00:35:47.620> try<00:35:47.950> to<00:35:47.980> control<00:35:48.460> some<00:35:48.760> of<00:35:48.790> the<00:35:49.000> exit 00:35:49.320 --> 00:35:49.330 align:start position:0% like try to control some of the exit 00:35:49.330 --> 00:35:52.050 align:start position:0% like try to control some of the exit nodes<00:35:49.600> and<00:35:49.780> so<00:35:50.020> on<00:35:50.280> another<00:35:51.280> thing<00:35:51.640> is 00:35:52.050 --> 00:35:52.060 align:start position:0% nodes and so on another thing is 00:35:52.060 --> 00:35:54.800 align:start position:0% nodes and so on another thing is they<00:35:52.300> will<00:35:52.870> be<00:35:53.080> when<00:35:53.620> we<00:35:53.770> random<00:35:54.280> big<00:35:54.460> stones 00:35:54.800 --> 00:35:54.810 align:start position:0% they will be when we random big stones 00:35:54.810 --> 00:35:57.150 align:start position:0% they will be when we random big stones there<00:35:55.810> are<00:35:55.900> a<00:35:55.960> couple<00:35:56.140> of<00:35:56.410> techniques<00:35:56.680> which 00:35:57.150 --> 00:35:57.160 align:start position:0% there are a couple of techniques which 00:35:57.160 --> 00:36:03.060 align:start position:0% there are a couple of techniques which allow<00:35:57.610> you<00:35:57.670> to<00:35:59.610> detect<00:36:00.610> any<00:36:00.850> notes<00:36:01.920> based<00:36:02.920> on 00:36:03.060 --> 00:36:03.070 align:start position:0% allow you to detect any notes based on 00:36:03.070 --> 00:36:05.100 align:start position:0% allow you to detect any notes based on the<00:36:03.190> reputation<00:36:03.430> so<00:36:04.240> try<00:36:04.630> to<00:36:04.660> build<00:36:04.930> a 00:36:05.100 --> 00:36:05.110 align:start position:0% the reputation so try to build a 00:36:05.110 --> 00:36:07.290 align:start position:0% the reputation so try to build a reputation<00:36:05.350> which<00:36:05.890> notes<00:36:06.430> are<00:36:06.700> there<00:36:06.880> honest 00:36:07.290 --> 00:36:07.300 align:start position:0% reputation which notes are there honest 00:36:07.300 --> 00:36:16.670 align:start position:0% reputation which notes are there honest ones<00:36:07.510> and<00:36:07.780> which<00:36:07.930> might<00:36:08.140> be<00:36:08.320> malicious<00:36:08.560> ones 00:36:16.670 --> 00:36:16.680 align:start position:0% 00:36:16.680 --> 00:36:25.650 align:start position:0% so<00:36:17.680> exactly<00:36:21.630> yeah<00:36:22.660> so<00:36:23.790> we<00:36:24.790> basically<00:36:24.940> did<00:36:25.420> just 00:36:25.650 --> 00:36:25.660 align:start position:0% so exactly yeah so we basically did just 00:36:25.660 --> 00:36:27.630 align:start position:0% so exactly yeah so we basically did just a<00:36:25.750> complete<00:36:26.050> are<00:36:26.200> give<00:36:26.770> a<00:36:26.800> quick<00:36:27.010> maybe<00:36:27.250> visual 00:36:27.630 --> 00:36:27.640 align:start position:0% a complete are give a quick maybe visual 00:36:27.640 --> 00:36:28.800 align:start position:0% a complete are give a quick maybe visual over<00:36:27.880> Vienna<00:36:28.120> might<00:36:28.510> help 00:36:28.800 --> 00:36:28.810 align:start position:0% over Vienna might help 00:36:28.810 --> 00:36:30.570 align:start position:0% over Vienna might help partly<00:36:29.260> answer<00:36:29.560> some<00:36:29.710> of<00:36:29.740> the<00:36:29.890> question<00:36:30.220> we 00:36:30.570 --> 00:36:30.580 align:start position:0% partly answer some of the question we 00:36:30.580 --> 00:36:33.030 align:start position:0% partly answer some of the question we basically<00:36:30.940> have<00:36:31.150> to<00:36:31.390> two<00:36:32.290> chunks<00:36:32.560> of<00:36:32.740> our<00:36:32.860> to 00:36:33.030 --> 00:36:33.040 align:start position:0% basically have to two chunks of our to 00:36:33.040 --> 00:36:35.520 align:start position:0% basically have to two chunks of our to two<00:36:33.280> parts<00:36:33.490> of<00:36:33.670> our<00:36:33.820> system<00:36:34.050> at<00:36:35.050> the<00:36:35.140> top<00:36:35.320> here 00:36:35.520 --> 00:36:35.530 align:start position:0% two parts of our system at the top here 00:36:35.530 --> 00:36:37.520 align:start position:0% two parts of our system at the top here is<00:36:35.620> the<00:36:35.650> mix<00:36:35.920> net<00:36:36.100> and<00:36:36.550> then<00:36:36.880> we<00:36:37.000> also<00:36:37.150> have 00:36:37.520 --> 00:36:37.530 align:start position:0% is the mix net and then we also have 00:36:37.530 --> 00:36:39.630 align:start position:0% is the mix net and then we also have validator<00:36:38.530> notes<00:36:38.830> of<00:36:39.040> decentralized 00:36:39.630 --> 00:36:39.640 align:start position:0% validator notes of decentralized 00:36:39.640 --> 00:36:42.300 align:start position:0% validator notes of decentralized authorities<00:36:40.180> that<00:36:40.800> communicate<00:36:41.800> among 00:36:42.300 --> 00:36:42.310 align:start position:0% authorities that communicate among 00:36:42.310 --> 00:36:43.770 align:start position:0% authorities that communicate among themselves<00:36:42.340> and<00:36:42.910> it<00:36:43.000> kind<00:36:43.120> of<00:36:43.150> B<00:36:43.300> of<00:36:43.390> T<00:36:43.540> round 00:36:43.770 --> 00:36:43.780 align:start position:0% themselves and it kind of B of T round 00:36:43.780 --> 00:36:46.200 align:start position:0% themselves and it kind of B of T round four<00:36:44.110> they're<00:36:44.200> doing<00:36:44.380> that<00:36:44.530> and<00:36:44.830> we<00:36:45.730> have<00:36:45.910> some 00:36:46.200 --> 00:36:46.210 align:start position:0% four they're doing that and we have some 00:36:46.210 --> 00:36:48.690 align:start position:0% four they're doing that and we have some dummy<00:36:46.960> service<00:36:47.500> providers<00:36:48.010> over<00:36:48.250> here<00:36:48.460> built 00:36:48.690 --> 00:36:48.700 align:start position:0% dummy service providers over here built 00:36:48.700 --> 00:36:52.230 align:start position:0% dummy service providers over here built as<00:36:48.850> well<00:36:49.000> to<00:36:49.900> talk<00:36:50.170> about<00:36:50.850> you<00:36:51.850> know<00:36:51.940> to<00:36:52.000> answer 00:36:52.230 --> 00:36:52.240 align:start position:0% as well to talk about you know to answer 00:36:52.240 --> 00:36:54.930 align:start position:0% as well to talk about you know to answer your<00:36:52.360> question<00:36:52.750> we<00:36:53.440> have<00:36:53.620> a<00:36:53.650> system<00:36:54.220> which<00:36:54.580> we 00:36:54.930 --> 00:36:54.940 align:start position:0% your question we have a system which we 00:36:54.940 --> 00:36:56.670 align:start position:0% your question we have a system which we haven't<00:36:55.120> yet<00:36:55.420> built<00:36:55.690> so<00:36:56.050> all<00:36:56.290> of<00:36:56.380> it<00:36:56.500> all<00:36:56.650> of 00:36:56.670 --> 00:36:56.680 align:start position:0% haven't yet built so all of it all of 00:36:56.680 --> 00:36:58.050 align:start position:0% haven't yet built so all of it all of the<00:36:56.830> stuff<00:36:57.010> I've<00:36:57.160> just<00:36:57.310> drawn<00:36:57.550> here<00:36:57.790> actually 00:36:58.050 --> 00:36:58.060 align:start position:0% the stuff I've just drawn here actually 00:36:58.060 --> 00:37:00.180 align:start position:0% the stuff I've just drawn here actually is<00:36:58.390> running<00:36:58.690> right<00:36:58.840> now<00:36:58.990> and<00:36:59.230> you<00:36:59.770> people<00:37:00.070> can 00:37:00.180 --> 00:37:00.190 align:start position:0% is running right now and you people can 00:37:00.190 --> 00:37:01.590 align:start position:0% is running right now and you people can start<00:37:00.370> to<00:37:00.490> integrate<00:37:00.700> it<00:37:00.910> against<00:37:01.180> it<00:37:01.270> try<00:37:01.540> it 00:37:01.590 --> 00:37:01.600 align:start position:0% start to integrate it against it try it 00:37:01.600 --> 00:37:03.750 align:start position:0% start to integrate it against it try it out<00:37:01.750> the<00:37:02.350> this<00:37:02.650> this<00:37:03.130> new<00:37:03.310> thing<00:37:03.520> that<00:37:03.550> I'm 00:37:03.750 --> 00:37:03.760 align:start position:0% out the this this new thing that I'm 00:37:03.760 --> 00:37:06.030 align:start position:0% out the this this new thing that I'm about<00:37:03.940> to<00:37:04.060> talk<00:37:04.210> about<00:37:04.290> doesn't<00:37:05.290> yet<00:37:05.470> exist<00:37:05.650> as 00:37:06.030 --> 00:37:06.040 align:start position:0% about to talk about doesn't yet exist as 00:37:06.040 --> 00:37:07.410 align:start position:0% about to talk about doesn't yet exist as running<00:37:06.220> code<00:37:06.490> is<00:37:06.670> it's<00:37:06.820> only<00:37:06.970> a<00:37:07.060> few<00:37:07.240> weeks 00:37:07.410 --> 00:37:07.420 align:start position:0% running code is it's only a few weeks 00:37:07.420 --> 00:37:09.660 align:start position:0% running code is it's only a few weeks old<00:37:07.570> so<00:37:07.810> it's<00:37:08.410> kind<00:37:08.650> of<00:37:08.740> we<00:37:09.070> just<00:37:09.310> haven't<00:37:09.610> had 00:37:09.660 --> 00:37:09.670 align:start position:0% old so it's kind of we just haven't had 00:37:09.670 --> 00:37:11.100 align:start position:0% old so it's kind of we just haven't had a<00:37:09.730> chance<00:37:09.880> yet<00:37:10.000> to<00:37:10.150> actually<00:37:10.780> put<00:37:10.960> it<00:37:11.020> together 00:37:11.100 --> 00:37:11.110 align:start position:0% a chance yet to actually put it together 00:37:11.110 --> 00:37:14.280 align:start position:0% a chance yet to actually put it together but<00:37:11.770> it's<00:37:12.180> essentially<00:37:13.180> a<00:37:13.210> way<00:37:13.570> of<00:37:13.600> saying 00:37:14.280 --> 00:37:14.290 align:start position:0% but it's essentially a way of saying 00:37:14.290 --> 00:37:17.550 align:start position:0% but it's essentially a way of saying okay<00:37:14.680> cool<00:37:15.150> the<00:37:16.150> original<00:37:16.600> loop<00:37:16.750> mix<00:37:16.930> design<00:37:17.260> I 00:37:17.550 --> 00:37:17.560 align:start position:0% okay cool the original loop mix design I 00:37:17.560 --> 00:37:19.350 align:start position:0% okay cool the original loop mix design I need<00:37:18.250> to<00:37:18.340> take<00:37:18.490> a<00:37:18.520> bit<00:37:18.670> of<00:37:18.700> a<00:37:18.790> detour<00:37:19.030> but<00:37:19.210> I'll 00:37:19.350 --> 00:37:19.360 align:start position:0% need to take a bit of a detour but I'll 00:37:19.360 --> 00:37:22.230 align:start position:0% need to take a bit of a detour but I'll get<00:37:19.630> back<00:37:19.750> to<00:37:19.810> it<00:37:20.040> was<00:37:21.040> okay<00:37:21.490> cool<00:37:21.700> your<00:37:21.880> client 00:37:22.230 --> 00:37:22.240 align:start position:0% get back to it was okay cool your client 00:37:22.240 --> 00:37:25.280 align:start position:0% get back to it was okay cool your client starts<00:37:22.690> sending<00:37:22.870> stuff<00:37:23.560> so<00:37:23.950> we<00:37:24.100> have<00:37:24.430> a<00:37:24.460> packet 00:37:25.280 --> 00:37:25.290 align:start position:0% starts sending stuff so we have a packet 00:37:25.290 --> 00:37:28.470 align:start position:0% starts sending stuff so we have a packet which<00:37:26.290> is<00:37:26.320> like<00:37:26.710> here<00:37:27.310> think<00:37:28.060> of<00:37:28.150> it<00:37:28.240> as<00:37:28.330> I 00:37:28.470 --> 00:37:28.480 align:start position:0% which is like here think of it as I 00:37:28.480 --> 00:37:30.840 align:start position:0% which is like here think of it as I guess<00:37:28.750> on<00:37:28.960> repair<00:37:29.310> encrypted<00:37:30.310> Russian<00:37:30.640> dolls 00:37:30.840 --> 00:37:30.850 align:start position:0% guess on repair encrypted Russian dolls 00:37:30.850 --> 00:37:32.790 align:start position:0% guess on repair encrypted Russian dolls that<00:37:31.060> all<00:37:31.300> kind<00:37:31.600> of<00:37:31.660> open<00:37:32.110> operate<00:37:32.470> so<00:37:32.680> the 00:37:32.790 --> 00:37:32.800 align:start position:0% that all kind of open operate so the 00:37:32.800 --> 00:37:34.860 align:start position:0% that all kind of open operate so the center<00:37:33.100> Galba<00:37:33.490> the<00:37:33.610> littlest<00:37:34.240> one<00:37:34.360> is<00:37:34.480> though 00:37:34.860 --> 00:37:34.870 align:start position:0% center Galba the littlest one is though 00:37:34.870 --> 00:37:36.480 align:start position:0% center Galba the littlest one is though the<00:37:35.080> message<00:37:35.230> you<00:37:35.470> actually<00:37:35.680> turn<00:37:35.800> us<00:37:35.890> in<00:37:36.070> then 00:37:36.480 --> 00:37:36.490 align:start position:0% the message you actually turn us in then 00:37:36.490 --> 00:37:39.420 align:start position:0% the message you actually turn us in then there's<00:37:36.700> these<00:37:36.820> layers<00:37:37.060> of<00:37:37.270> encryption<00:37:38.430> and 00:37:39.420 --> 00:37:39.430 align:start position:0% there's these layers of encryption and 00:37:39.430 --> 00:37:41.130 align:start position:0% there's these layers of encryption and that<00:37:39.970> basically<00:37:40.300> defines<00:37:40.480> a<00:37:40.690> path<00:37:40.870> that<00:37:41.080> goes 00:37:41.130 --> 00:37:41.140 align:start position:0% that basically defines a path that goes 00:37:41.140 --> 00:37:43.560 align:start position:0% that basically defines a path that goes in<00:37:41.410> here<00:37:41.710> comes<00:37:42.400> out<00:37:42.520> here<00:37:42.760> goes<00:37:43.180> this<00:37:43.360> way 00:37:43.560 --> 00:37:43.570 align:start position:0% in here comes out here goes this way 00:37:43.570 --> 00:37:46.740 align:start position:0% in here comes out here goes this way ends<00:37:44.530> up<00:37:44.620> at<00:37:44.800> this<00:37:45.160> storage<00:37:45.940> node<00:37:46.270> over<00:37:46.540> here 00:37:46.740 --> 00:37:46.750 align:start position:0% ends up at this storage node over here 00:37:46.750 --> 00:37:48.900 align:start position:0% ends up at this storage node over here and<00:37:46.930> then<00:37:47.230> the<00:37:47.380> offline<00:37:47.770> client<00:37:48.340> maybe<00:37:48.550> that 00:37:48.900 --> 00:37:48.910 align:start position:0% and then the offline client maybe that 00:37:48.910 --> 00:37:50.490 align:start position:0% and then the offline client maybe that was<00:37:49.030> here<00:37:49.240> maybe<00:37:49.390> somebody<00:37:49.720> comes<00:37:50.140> out<00:37:50.290> of<00:37:50.410> the 00:37:50.490 --> 00:37:50.500 align:start position:0% was here maybe somebody comes out of the 00:37:50.500 --> 00:37:53.730 align:start position:0% was here maybe somebody comes out of the Metro<00:37:51.280> something<00:37:51.640> like<00:37:51.790> that<00:37:52.230> grabs<00:37:53.230> that<00:37:53.470> and 00:37:53.730 --> 00:37:53.740 align:start position:0% Metro something like that grabs that and 00:37:53.740 --> 00:37:55.950 align:start position:0% Metro something like that grabs that and actually<00:37:54.060> gets<00:37:55.060> the<00:37:55.210> content<00:37:55.600> delivered 00:37:55.950 --> 00:37:55.960 align:start position:0% actually gets the content delivered 00:37:55.960 --> 00:37:58.380 align:start position:0% actually gets the content delivered right<00:37:56.110> now<00:37:56.680> the<00:37:57.010> original<00:37:57.190> design<00:37:57.730> of<00:37:57.760> Lubich 00:37:58.380 --> 00:37:58.390 align:start position:0% right now the original design of Lubich 00:37:58.390 --> 00:38:00.720 align:start position:0% right now the original design of Lubich which<00:37:58.720> is<00:37:58.950> something<00:37:59.950> that<00:38:00.069> on<00:38:00.279> you<00:38:00.400> worked<00:38:00.579> on 00:38:00.720 --> 00:38:00.730 align:start position:0% which is something that on you worked on 00:38:00.730 --> 00:38:05.190 align:start position:0% which is something that on you worked on what's<00:38:01.539> very<00:38:01.990> individualistic<00:38:02.760> so<00:38:04.049> you<00:38:05.049> can 00:38:05.190 --> 00:38:05.200 align:start position:0% what's very individualistic so you can 00:38:05.200 --> 00:38:07.289 align:start position:0% what's very individualistic so you can do<00:38:05.319> Luke<00:38:05.529> Luke<00:38:05.980> traffic<00:38:06.460> it's<00:38:06.640> called<00:38:06.880> and<00:38:07.210> you 00:38:07.289 --> 00:38:07.299 align:start position:0% do Luke Luke traffic it's called and you 00:38:07.299 --> 00:38:09.750 align:start position:0% do Luke Luke traffic it's called and you can<00:38:07.450> be<00:38:07.650> spitting<00:38:08.650> even<00:38:09.309> if<00:38:09.400> you're<00:38:09.549> not 00:38:09.750 --> 00:38:09.760 align:start position:0% can be spitting even if you're not 00:38:09.760 --> 00:38:11.670 align:start position:0% can be spitting even if you're not sending<00:38:10.180> any<00:38:10.510> real<00:38:10.809> messages<00:38:11.319> through<00:38:11.559> the 00:38:11.670 --> 00:38:11.680 align:start position:0% sending any real messages through the 00:38:11.680 --> 00:38:14.370 align:start position:0% sending any real messages through the system<00:38:12.010> you<00:38:12.549> might<00:38:12.670> be<00:38:12.819> spitting<00:38:13.240> new<00:38:13.990> traffic 00:38:14.370 --> 00:38:14.380 align:start position:0% system you might be spitting new traffic 00:38:14.380 --> 00:38:15.630 align:start position:0% system you might be spitting new traffic through<00:38:14.529> your<00:38:14.650> cigar<00:38:14.950> your<00:38:15.160> packet<00:38:15.430> might<00:38:15.549> go 00:38:15.630 --> 00:38:15.640 align:start position:0% through your cigar your packet might go 00:38:15.640 --> 00:38:17.279 align:start position:0% through your cigar your packet might go boom<00:38:15.819> boom<00:38:15.970> boom<00:38:16.150> boom<00:38:16.269> book<00:38:16.450> and<00:38:16.720> actually 00:38:17.279 --> 00:38:17.289 align:start position:0% boom boom boom boom book and actually 00:38:17.289 --> 00:38:20.490 align:start position:0% boom boom boom boom book and actually loop<00:38:17.950> back<00:38:18.190> around<00:38:18.220> to<00:38:19.059> you<00:38:19.240> and<00:38:20.049> say<00:38:20.319> cool 00:38:20.490 --> 00:38:20.500 align:start position:0% loop back around to you and say cool 00:38:20.500 --> 00:38:21.900 align:start position:0% loop back around to you and say cool well<00:38:20.799> my<00:38:20.950> message<00:38:21.069> made<00:38:21.369> it<00:38:21.490> through<00:38:21.640> so<00:38:21.700> you 00:38:21.900 --> 00:38:21.910 align:start position:0% well my message made it through so you 00:38:21.910 --> 00:38:24.299 align:start position:0% well my message made it through so you said<00:38:22.119> maybe<00:38:22.450> one<00:38:23.260> every<00:38:23.380> ten<00:38:23.650> times<00:38:23.890> you<00:38:24.130> sent 00:38:24.299 --> 00:38:24.309 align:start position:0% said maybe one every ten times you sent 00:38:24.309 --> 00:38:26.339 align:start position:0% said maybe one every ten times you sent they'll<00:38:24.400> do<00:38:24.490> pack<00:38:24.700> it<00:38:24.849> around<00:38:25.059> and<00:38:25.329> you<00:38:26.230> can 00:38:26.339 --> 00:38:26.349 align:start position:0% they'll do pack it around and you can 00:38:26.349 --> 00:38:28.910 align:start position:0% they'll do pack it around and you can you<00:38:26.559> can<00:38:26.589> basically<00:38:26.859> see<00:38:27.250> cool<00:38:27.519> these<00:38:28.269> guys 00:38:28.910 --> 00:38:28.920 align:start position:0% you can basically see cool these guys 00:38:28.920 --> 00:38:31.650 align:start position:0% you can basically see cool these guys delivered<00:38:29.920> my<00:38:30.069> message<00:38:30.099> right<00:38:30.670> the<00:38:31.390> problem 00:38:31.650 --> 00:38:31.660 align:start position:0% delivered my message right the problem 00:38:31.660 --> 00:38:35.759 align:start position:0% delivered my message right the problem we<00:38:31.930> have<00:38:32.109> to<00:38:32.440> solve<00:38:32.710> is<00:38:33.150> okay<00:38:34.260> for<00:38:35.260> if<00:38:35.440> this<00:38:35.619> is 00:38:35.759 --> 00:38:35.769 align:start position:0% we have to solve is okay for if this is 00:38:35.769 --> 00:38:39.690 align:start position:0% we have to solve is okay for if this is me<00:38:37.019> I'm<00:38:38.019> a<00:38:38.049> good<00:38:38.260> person<00:38:38.470> I<00:38:38.829> would<00:38:39.339> never<00:38:39.430> say 00:38:39.690 --> 00:38:39.700 align:start position:0% me I'm a good person I would never say 00:38:39.700 --> 00:38:42.779 align:start position:0% me I'm a good person I would never say anything<00:38:39.730> wrong<00:38:40.059> how<00:38:40.779> can<00:38:40.839> we<00:38:41.170> if<00:38:41.769> we<00:38:42.250> just 00:38:42.779 --> 00:38:42.789 align:start position:0% anything wrong how can we if we just 00:38:42.789 --> 00:38:44.190 align:start position:0% anything wrong how can we if we just rely<00:38:43.119> on<00:38:43.180> the<00:38:43.299> user's<00:38:43.720> to<00:38:43.930> do<00:38:44.049> this 00:38:44.190 --> 00:38:44.200 align:start position:0% rely on the user's to do this 00:38:44.200 --> 00:38:46.349 align:start position:0% rely on the user's to do this measurements<00:38:44.740> that<00:38:45.400> I<00:38:45.549> could<00:38:45.849> also<00:38:45.970> be<00:38:46.269> an 00:38:46.349 --> 00:38:46.359 align:start position:0% measurements that I could also be an 00:38:46.359 --> 00:38:48.210 align:start position:0% measurements that I could also be an attacker<00:38:46.660> right<00:38:47.079> so<00:38:47.589> we<00:38:47.710> have<00:38:47.829> to<00:38:47.950> come<00:38:48.099> up 00:38:48.210 --> 00:38:48.220 align:start position:0% attacker right so we have to come up 00:38:48.220 --> 00:38:51.390 align:start position:0% attacker right so we have to come up with<00:38:48.369> a<00:38:48.400> way<00:38:48.579> of<00:38:48.819> verifying<00:38:49.650> the<00:38:50.650> the<00:38:50.950> behavior 00:38:51.390 --> 00:38:51.400 align:start position:0% with a way of verifying the the behavior 00:38:51.400 --> 00:38:53.220 align:start position:0% with a way of verifying the the behavior of<00:38:51.519> each<00:38:51.609> of<00:38:51.819> these<00:38:51.940> nodes<00:38:52.240> in<00:38:52.779> a<00:38:52.900> way<00:38:53.019> that's 00:38:53.220 --> 00:38:53.230 align:start position:0% of each of these nodes in a way that's 00:38:53.230 --> 00:38:55.650 align:start position:0% of each of these nodes in a way that's publicly<00:38:53.740> verifiable<00:38:54.180> in<00:38:55.180> a<00:38:55.240> way<00:38:55.329> that's<00:38:55.539> kind 00:38:55.650 --> 00:38:55.660 align:start position:0% publicly verifiable in a way that's kind 00:38:55.660 --> 00:38:59.250 align:start position:0% publicly verifiable in a way that's kind of<00:38:55.750> akin<00:38:56.019> to<00:38:56.170> like<00:38:57.359> BFD<00:38:58.359> consensus<00:38:58.869> system 00:38:59.250 --> 00:38:59.260 align:start position:0% of akin to like BFD consensus system 00:38:59.260 --> 00:39:05.009 align:start position:0% of akin to like BFD consensus system right<00:38:59.950> because<00:39:00.880> I<00:39:01.980> could<00:39:02.980> say<00:39:03.220> hey<00:39:03.819> my<00:39:04.480> my<00:39:04.809> back 00:39:05.009 --> 00:39:05.019 align:start position:0% right because I could say hey my my back 00:39:05.019 --> 00:39:06.630 align:start position:0% right because I could say hey my my back it<00:39:05.200> never<00:39:05.410> made<00:39:05.619> it<00:39:05.740> past<00:39:05.769> here<00:39:06.220> and<00:39:06.279> if<00:39:06.490> we 00:39:06.630 --> 00:39:06.640 align:start position:0% it never made it past here and if we 00:39:06.640 --> 00:39:08.940 align:start position:0% it never made it past here and if we rely<00:39:06.910> on<00:39:06.940> my<00:39:07.359> individual<00:39:07.900> judgment<00:39:08.319> I<00:39:08.470> could 00:39:08.940 --> 00:39:08.950 align:start position:0% rely on my individual judgment I could 00:39:08.950 --> 00:39:10.380 align:start position:0% rely on my individual judgment I could be<00:39:09.009> the<00:39:09.130> attacker<00:39:09.339> trying<00:39:09.789> to<00:39:09.880> damage<00:39:10.089> the 00:39:10.380 --> 00:39:10.390 align:start position:0% be the attacker trying to damage the 00:39:10.390 --> 00:39:12.509 align:start position:0% be the attacker trying to damage the reputation<00:39:10.599> of<00:39:11.019> this<00:39:11.200> node<00:39:11.380> right<00:39:11.529> so<00:39:12.220> we 00:39:12.509 --> 00:39:12.519 align:start position:0% reputation of this node right so we 00:39:12.519 --> 00:39:15.839 align:start position:0% reputation of this node right so we basically<00:39:12.880> come<00:39:13.150> up<00:39:13.180> with<00:39:13.420> a<00:39:13.450> way<00:39:13.660> of<00:39:14.849> using 00:39:15.839 --> 00:39:15.849 align:start position:0% basically come up with a way of using 00:39:15.849 --> 00:39:18.120 align:start position:0% basically come up with a way of using the<00:39:16.029> verifiable<00:39:16.660> randomness<00:39:17.140> function<00:39:17.529> to 00:39:18.120 --> 00:39:18.130 align:start position:0% the verifiable randomness function to 00:39:18.130 --> 00:39:19.950 align:start position:0% the verifiable randomness function to pre<00:39:18.519> generate<00:39:18.970> a<00:39:19.119> bunch<00:39:19.329> of<00:39:19.420> packets<00:39:19.839> and 00:39:19.950 --> 00:39:19.960 align:start position:0% pre generate a bunch of packets and 00:39:19.960 --> 00:39:22.440 align:start position:0% pre generate a bunch of packets and assign<00:39:20.259> them<00:39:20.440> to<00:39:20.500> clients<00:39:20.940> the<00:39:21.940> clients<00:39:22.329> will 00:39:22.440 --> 00:39:22.450 align:start position:0% assign them to clients the clients will 00:39:22.450 --> 00:39:24.569 align:start position:0% assign them to clients the clients will send<00:39:22.660> them<00:39:22.809> through<00:39:22.960> the<00:39:23.829> Viera<00:39:24.099> will<00:39:24.460> be 00:39:24.569 --> 00:39:24.579 align:start position:0% send them through the Viera will be 00:39:24.579 --> 00:39:28.039 align:start position:0% send them through the Viera will be revealed<00:39:25.359> at<00:39:25.569> the<00:39:25.660> end<00:39:25.779> of<00:39:25.900> a<00:39:25.990> timed<00:39:26.559> round<00:39:26.890> and 00:39:28.039 --> 00:39:28.049 align:start position:0% revealed at the end of a timed round and 00:39:28.049 --> 00:39:31.470 align:start position:0% revealed at the end of a timed round and we<00:39:29.049> can<00:39:29.230> then<00:39:29.380> check<00:39:29.819> does<00:39:30.819> the<00:39:30.970> Merkel<00:39:31.269> trees 00:39:31.470 --> 00:39:31.480 align:start position:0% we can then check does the Merkel trees 00:39:31.480 --> 00:39:33.480 align:start position:0% we can then check does the Merkel trees of<00:39:31.660> each<00:39:31.779> of<00:39:31.990> these<00:39:32.109> nodes<00:39:32.500> which<00:39:32.859> they've 00:39:33.480 --> 00:39:33.490 align:start position:0% of each of these nodes which they've 00:39:33.490 --> 00:39:35.940 align:start position:0% of each of these nodes which they've been<00:39:33.609> keeping<00:39:33.759> for<00:39:34.559> record-keeping<00:39:35.559> purposes 00:39:35.940 --> 00:39:35.950 align:start position:0% been keeping for record-keeping purposes 00:39:35.950 --> 00:39:37.980 align:start position:0% been keeping for record-keeping purposes basically<00:39:36.369> they<00:39:37.089> have<00:39:37.180> to<00:39:37.299> show<00:39:37.480> the<00:39:37.690> Merkel 00:39:37.980 --> 00:39:37.990 align:start position:0% basically they have to show the Merkel 00:39:37.990 --> 00:39:39.299 align:start position:0% basically they have to show the Merkel trees<00:39:38.170> and<00:39:38.380> the<00:39:38.440> commitments<00:39:38.920> inside<00:39:39.190> the 00:39:39.299 --> 00:39:39.309 align:start position:0% trees and the commitments inside the 00:39:39.309 --> 00:39:42.120 align:start position:0% trees and the commitments inside the marble<00:39:39.460> trees<00:39:39.759> that<00:39:39.940> each<00:39:40.420> node<00:39:40.720> has<00:39:41.130> they 00:39:42.120 --> 00:39:42.130 align:start position:0% marble trees that each node has they 00:39:42.130 --> 00:39:45.839 align:start position:0% marble trees that each node has they send<00:39:42.430> that<00:39:42.549> back<00:39:42.759> to<00:39:43.440> the<00:39:44.849> staking 00:39:45.839 --> 00:39:45.849 align:start position:0% send that back to the staking 00:39:45.849 --> 00:39:47.849 align:start position:0% send that back to the staking authorities<00:39:46.269> and<00:39:46.539> the<00:39:47.200> state<00:39:47.380> authorities 00:39:47.849 --> 00:39:47.859 align:start position:0% authorities and the state authorities 00:39:47.859 --> 00:39:50.370 align:start position:0% authorities and the state authorities can<00:39:48.069> then<00:39:48.250> verify<00:39:48.900> did<00:39:49.900> they<00:39:50.019> do<00:39:50.079> the<00:39:50.289> right 00:39:50.370 --> 00:39:50.380 align:start position:0% can then verify did they do the right 00:39:50.380 --> 00:39:50.880 align:start position:0% can then verify did they do the right thing 00:39:50.880 --> 00:39:50.890 align:start position:0% thing 00:39:50.890 --> 00:39:52.829 align:start position:0% thing add<00:39:51.160> a<00:39:51.220> kind<00:39:51.430> of<00:39:51.549> system<00:39:51.849> level<00:39:52.180> not<00:39:52.450> at<00:39:52.480> the 00:39:52.829 --> 00:39:52.839 align:start position:0% add a kind of system level not at the 00:39:52.839 --> 00:39:54.329 align:start position:0% add a kind of system level not at the individual<00:39:53.230> level<00:39:53.319> so<00:39:53.680> this<00:39:53.829> is<00:39:54.039> something 00:39:54.329 --> 00:39:54.339 align:start position:0% individual level so this is something 00:39:54.339 --> 00:39:57.180 align:start position:0% individual level so this is something we've<00:39:54.460> just<00:39:54.700> come<00:39:54.849> up<00:39:54.940> with<00:39:55.650> it's<00:39:56.650> probably 00:39:57.180 --> 00:39:57.190 align:start position:0% we've just come up with it's probably 00:39:57.190 --> 00:39:58.680 align:start position:0% we've just come up with it's probably the<00:39:57.309> first<00:39:57.519> time<00:39:57.819> that<00:39:58.000> anybody's<00:39:58.359> come<00:39:58.569> up 00:39:58.680 --> 00:39:58.690 align:start position:0% the first time that anybody's come up 00:39:58.690 --> 00:40:01.529 align:start position:0% the first time that anybody's come up with<00:39:59.009> kind<00:40:00.009> of<00:40:00.099> a<00:40:00.190> incentivization<00:40:01.150> system 00:40:01.529 --> 00:40:01.539 align:start position:0% with kind of a incentivization system 00:40:01.539 --> 00:40:04.880 align:start position:0% with kind of a incentivization system that<00:40:02.140> works<00:40:02.440> with<00:40:02.890> a<00:40:02.920> mixed<00:40:03.460> net<00:40:03.579> like<00:40:03.759> this<00:40:03.789> so 00:40:04.880 --> 00:40:04.890 align:start position:0% that works with a mixed net like this so 00:40:04.890 --> 00:40:12.410 align:start position:0% that works with a mixed net like this so we're<00:40:05.039> quite<00:40:05.489> proud<00:40:05.640> of<00:40:05.730> it<00:40:06.619> we<00:40:07.619> haven't<00:40:11.420> we're 00:40:12.410 --> 00:40:12.420 align:start position:0% we're quite proud of it we haven't we're 00:40:12.420 --> 00:40:14.299 align:start position:0% we're quite proud of it we haven't we're checking<00:40:12.749> the<00:40:12.960> quality<00:40:13.410> of<00:40:13.499> service<00:40:13.920> offered 00:40:14.299 --> 00:40:14.309 align:start position:0% checking the quality of service offered 00:40:14.309 --> 00:40:16.279 align:start position:0% checking the quality of service offered by<00:40:14.489> the<00:40:14.549> make<00:40:14.849> make<00:40:15.239> sense<00:40:15.539> and<00:40:15.749> if<00:40:15.900> we<00:40:16.079> see 00:40:16.279 --> 00:40:16.289 align:start position:0% by the make make sense and if we see 00:40:16.289 --> 00:40:19.220 align:start position:0% by the make make sense and if we see that<00:40:16.499> some<00:40:16.739> mixes<00:40:17.220> are<00:40:17.489> behaving<00:40:18.230> dishonest 00:40:19.220 --> 00:40:19.230 align:start position:0% that some mixes are behaving dishonest 00:40:19.230 --> 00:40:21.589 align:start position:0% that some mixes are behaving dishonest or<00:40:19.410> that<00:40:19.589> or<00:40:19.890> in<00:40:20.099> a<00:40:20.160> malicious<00:40:20.339> way<00:40:20.579> we're<00:40:21.299> just 00:40:21.589 --> 00:40:21.599 align:start position:0% or that or in a malicious way we're just 00:40:21.599 --> 00:40:35.690 align:start position:0% or that or in a malicious way we're just cutting<00:40:22.049> from<00:40:22.440> their<00:40:22.619> stakes<00:40:23.009> so<00:40:31.009> cool<00:40:34.190> as<00:40:35.190> as 00:40:35.690 --> 00:40:35.700 align:start position:0% cutting from their stakes so cool as as 00:40:35.700 --> 00:40:39.380 align:start position:0% cutting from their stakes so cool as as far<00:40:35.970> as<00:40:36.150> I'm<00:40:36.299> stunned<00:40:36.779> it<00:40:37.019> and<00:40:38.089> taller<00:40:39.089> just 00:40:39.380 --> 00:40:39.390 align:start position:0% far as I'm stunned it and taller just 00:40:39.390 --> 00:40:40.970 align:start position:0% far as I'm stunned it and taller just has<00:40:39.539> very<00:40:39.779> simple<00:40:40.349> we<00:40:40.499> just<00:40:40.710> send<00:40:40.890> the 00:40:40.970 --> 00:40:40.980 align:start position:0% has very simple we just send the 00:40:40.980 --> 00:40:43.430 align:start position:0% has very simple we just send the messages<00:40:41.460> out<00:40:41.700> directly<00:40:42.329> there's<00:40:43.079> a<00:40:43.170> mixed 00:40:43.430 --> 00:40:43.440 align:start position:0% messages out directly there's a mixed 00:40:43.440 --> 00:40:44.839 align:start position:0% messages out directly there's a mixed network<00:40:43.799> want<00:40:44.069> to<00:40:44.160> use<00:40:44.279> a<00:40:44.309> Poisson 00:40:44.839 --> 00:40:44.849 align:start position:0% network want to use a Poisson 00:40:44.849 --> 00:40:47.930 align:start position:0% network want to use a Poisson distribution<00:40:45.650> for<00:40:46.650> the<00:40:46.769> sending<00:40:47.670> out<00:40:47.789> of 00:40:47.930 --> 00:40:47.940 align:start position:0% distribution for the sending out of 00:40:47.940 --> 00:40:52.039 align:start position:0% distribution for the sending out of messages<00:40:48.470> and<00:40:49.470> also<00:40:50.430> different<00:40:51.390> classes<00:40:51.900> of 00:40:52.039 --> 00:40:52.049 align:start position:0% messages and also different classes of 00:40:52.049 --> 00:40:53.299 align:start position:0% messages and also different classes of applications<00:40:52.170> will<00:40:52.890> have<00:40:53.039> different 00:40:53.299 --> 00:40:53.309 align:start position:0% applications will have different 00:40:53.309 --> 00:40:56.509 align:start position:0% applications will have different profiles<00:40:54.119> how<00:40:54.720> do<00:40:54.779> you<00:40:54.900> want<00:40:55.079> to<00:40:55.190> create<00:40:56.190> those 00:40:56.509 --> 00:40:56.519 align:start position:0% profiles how do you want to create those 00:40:56.519 --> 00:40:58.489 align:start position:0% profiles how do you want to create those profiles<00:40:57.210> for<00:40:57.509> the<00:40:57.599> different<00:40:57.930> applications 00:40:58.489 --> 00:40:58.499 align:start position:0% profiles for the different applications 00:40:58.499 --> 00:41:01.160 align:start position:0% profiles for the different applications what<00:40:59.059> processes<00:41:00.059> and<00:41:00.210> tools<00:41:00.450> are<00:41:00.690> interested 00:41:01.160 --> 00:41:01.170 align:start position:0% what processes and tools are interested 00:41:01.170 --> 00:41:05.329 align:start position:0% what processes and tools are interested create<00:41:01.859> noise<00:41:03.589> so<00:41:04.589> just<00:41:04.619> make<00:41:05.130> sure<00:41:05.309> I 00:41:05.329 --> 00:41:05.339 align:start position:0% create noise so just make sure I 00:41:05.339 --> 00:41:06.710 align:start position:0% create noise so just make sure I understand<00:41:05.759> your<00:41:05.819> question<00:41:05.970> you're<00:41:06.299> asking 00:41:06.710 --> 00:41:06.720 align:start position:0% understand your question you're asking 00:41:06.720 --> 00:41:09.529 align:start position:0% understand your question you're asking like<00:41:06.779> if<00:41:07.049> people<00:41:07.289> we<00:41:07.970> discuss<00:41:08.970> different<00:41:08.999> use 00:41:09.529 --> 00:41:09.539 align:start position:0% like if people we discuss different use 00:41:09.539 --> 00:41:11.359 align:start position:0% like if people we discuss different use cases<00:41:09.809> where<00:41:10.109> people<00:41:10.470> send<00:41:10.799> different 00:41:11.359 --> 00:41:11.369 align:start position:0% cases where people send different 00:41:11.369 --> 00:41:13.819 align:start position:0% cases where people send different volumes<00:41:11.759> of<00:41:11.940> traffic<00:41:12.239> it's<00:41:13.019> also<00:41:13.170> like<00:41:13.440> a<00:41:13.529> chop 00:41:13.819 --> 00:41:13.829 align:start position:0% volumes of traffic it's also like a chop 00:41:13.829 --> 00:41:15.920 align:start position:0% volumes of traffic it's also like a chop okay<00:41:14.220> yeah<00:41:14.400> what<00:41:15.359> it<00:41:15.480> will<00:41:15.599> have<00:41:15.690> different 00:41:15.920 --> 00:41:15.930 align:start position:0% okay yeah what it will have different 00:41:15.930 --> 00:41:18.349 align:start position:0% okay yeah what it will have different yeah<00:41:16.410> so<00:41:17.009> just<00:41:17.369> to<00:41:17.579> give<00:41:17.730> you<00:41:17.759> a<00:41:17.849> little<00:41:18.029> bit<00:41:18.180> of 00:41:18.349 --> 00:41:18.359 align:start position:0% yeah so just to give you a little bit of 00:41:18.359 --> 00:41:22.160 align:start position:0% yeah so just to give you a little bit of the<00:41:18.539> background<00:41:19.519> in<00:41:20.519> the<00:41:20.849> looping<00:41:21.720> Society 00:41:22.160 --> 00:41:22.170 align:start position:0% the background in the looping Society 00:41:22.170 --> 00:41:25.430 align:start position:0% the background in the looping Society and<00:41:22.289> hence<00:41:22.529> in<00:41:22.710> the<00:41:22.859> Linda's<00:41:23.400> mix<00:41:23.609> net<00:41:24.200> we<00:41:25.200> and 00:41:25.430 --> 00:41:25.440 align:start position:0% and hence in the Linda's mix net we and 00:41:25.440 --> 00:41:28.160 align:start position:0% and hence in the Linda's mix net we and force<00:41:26.039> kind<00:41:26.489> of<00:41:26.730> the<00:41:27.089> clients<00:41:27.690> to<00:41:27.900> send 00:41:28.160 --> 00:41:28.170 align:start position:0% force kind of the clients to send 00:41:28.170 --> 00:41:29.809 align:start position:0% force kind of the clients to send following<00:41:28.680> a<00:41:28.890> following<00:41:29.220> a<00:41:29.339> Poisson 00:41:29.809 --> 00:41:29.819 align:start position:0% following a following a Poisson 00:41:29.819 --> 00:41:32.359 align:start position:0% following a following a Poisson distribution<00:41:30.420> what<00:41:31.200> does<00:41:31.349> it<00:41:31.529> mean<00:41:31.710> imagine 00:41:32.359 --> 00:41:32.369 align:start position:0% distribution what does it mean imagine 00:41:32.369 --> 00:41:33.829 align:start position:0% distribution what does it mean imagine you<00:41:32.579> have<00:41:32.730> a<00:41:32.759> phone<00:41:33.059> and<00:41:33.390> you<00:41:33.509> press<00:41:33.809> the 00:41:33.829 --> 00:41:33.839 align:start position:0% you have a phone and you press the 00:41:33.839 --> 00:41:35.989 align:start position:0% you have a phone and you press the button<00:41:33.989> send<00:41:34.619> your<00:41:35.279> message<00:41:35.640> is<00:41:35.819> not 00:41:35.989 --> 00:41:35.999 align:start position:0% button send your message is not 00:41:35.999 --> 00:41:37.999 align:start position:0% button send your message is not immediately<00:41:36.509> is<00:41:36.630> injected<00:41:37.380> into<00:41:37.559> the<00:41:37.710> mix 00:41:37.999 --> 00:41:38.009 align:start position:0% immediately is injected into the mix 00:41:38.009 --> 00:41:40.789 align:start position:0% immediately is injected into the mix network<00:41:38.430> instead<00:41:38.999> of<00:41:39.150> that<00:41:39.359> it's<00:41:39.900> buffered<00:41:40.559> in 00:41:40.789 --> 00:41:40.799 align:start position:0% network instead of that it's buffered in 00:41:40.799 --> 00:41:43.039 align:start position:0% network instead of that it's buffered in like<00:41:41.039> a<00:41:41.069> special<00:41:41.579> here<00:41:41.910> which<00:41:42.329> is<00:41:42.509> controlled 00:41:43.039 --> 00:41:43.049 align:start position:0% like a special here which is controlled 00:41:43.049 --> 00:41:44.930 align:start position:0% like a special here which is controlled by<00:41:43.140> the<00:41:43.259> Poisson<00:41:43.739> process<00:41:43.769> and<00:41:44.400> from<00:41:44.579> time<00:41:44.789> to 00:41:44.930 --> 00:41:44.940 align:start position:0% by the Poisson process and from time to 00:41:44.940 --> 00:41:46.880 align:start position:0% by the Poisson process and from time to time<00:41:44.970> at<00:41:45.509> random<00:41:45.869> times<00:41:46.019> disposal<00:41:46.680> process 00:41:46.880 --> 00:41:46.890 align:start position:0% time at random times disposal process 00:41:46.890 --> 00:41:49.249 align:start position:0% time at random times disposal process weights<00:41:47.249> up<00:41:47.549> and<00:41:47.759> checks<00:41:48.539> this<00:41:48.690> backward<00:41:49.109> if 00:41:49.249 --> 00:41:49.259 align:start position:0% weights up and checks this backward if 00:41:49.259 --> 00:41:51.200 align:start position:0% weights up and checks this backward if there<00:41:49.440> is<00:41:49.559> a<00:41:49.589> real<00:41:49.859> message<00:41:50.099> you<00:41:50.730> take<00:41:50.999> this 00:41:51.200 --> 00:41:51.210 align:start position:0% there is a real message you take this 00:41:51.210 --> 00:41:53.690 align:start position:0% there is a real message you take this message<00:41:51.480> and<00:41:51.839> send<00:41:52.230> it<00:41:52.410> if<00:41:52.650> there<00:41:53.249> is<00:41:53.339> no<00:41:53.519> real 00:41:53.690 --> 00:41:53.700 align:start position:0% message and send it if there is no real 00:41:53.700 --> 00:41:55.819 align:start position:0% message and send it if there is no real message<00:41:54.119> he<00:41:54.420> sends<00:41:54.749> an<00:41:54.900> undercover<00:41:55.349> message 00:41:55.819 --> 00:41:55.829 align:start position:0% message he sends an undercover message 00:41:55.829 --> 00:41:57.859 align:start position:0% message he sends an undercover message what<00:41:56.430> this<00:41:56.579> gives<00:41:56.789> you<00:41:56.999> is<00:41:57.150> that<00:41:57.359> you're 00:41:57.859 --> 00:41:57.869 align:start position:0% what this gives you is that you're 00:41:57.869 --> 00:41:59.569 align:start position:0% what this gives you is that you're sending<00:41:58.259> pattern<00:41:58.859> and 00:41:59.569 --> 00:41:59.579 align:start position:0% sending pattern and 00:41:59.579 --> 00:42:02.209 align:start position:0% sending pattern and so<00:42:00.299> from<00:42:00.450> the<00:42:00.569> perspective<00:42:00.839> of<00:42:01.380> the<00:42:01.619> adversary 00:42:02.209 --> 00:42:02.219 align:start position:0% so from the perspective of the adversary 00:42:02.219 --> 00:42:04.370 align:start position:0% so from the perspective of the adversary who's<00:42:02.430> observing<00:42:02.640> your<00:42:03.209> client<00:42:03.690> it<00:42:04.109> just 00:42:04.370 --> 00:42:04.380 align:start position:0% who's observing your client it just 00:42:04.380 --> 00:42:05.959 align:start position:0% who's observing your client it just looks<00:42:04.589> like<00:42:04.680> you're<00:42:05.249> always<00:42:05.549> sending 00:42:05.959 --> 00:42:05.969 align:start position:0% looks like you're always sending 00:42:05.969 --> 00:42:08.660 align:start position:0% looks like you're always sending something<00:42:06.660> but<00:42:07.380> whether<00:42:08.099> you're<00:42:08.249> sending 00:42:08.660 --> 00:42:08.670 align:start position:0% something but whether you're sending 00:42:08.670 --> 00:42:10.519 align:start position:0% something but whether you're sending krill<00:42:08.880> traffic<00:42:09.359> or<00:42:09.539> just<00:42:09.749> cover<00:42:09.900> traffic<00:42:10.380> we 00:42:10.519 --> 00:42:10.529 align:start position:0% krill traffic or just cover traffic we 00:42:10.529 --> 00:42:12.499 align:start position:0% krill traffic or just cover traffic we don't<00:42:10.709> know<00:42:10.829> that<00:42:10.859> so<00:42:11.789> coming<00:42:12.150> back<00:42:12.180> to<00:42:12.450> our 00:42:12.499 --> 00:42:12.509 align:start position:0% don't know that so coming back to our 00:42:12.509 --> 00:42:15.709 align:start position:0% don't know that so coming back to our beers<00:42:12.779> question<00:42:13.640> if<00:42:14.640> we<00:42:14.849> have<00:42:15.059> different<00:42:15.569> use 00:42:15.709 --> 00:42:15.719 align:start position:0% beers question if we have different use 00:42:15.719 --> 00:42:19.069 align:start position:0% beers question if we have different use cases<00:42:16.049> like<00:42:16.579> instant<00:42:17.579> messaging<00:42:18.119> or<00:42:18.599> given 00:42:19.069 --> 00:42:19.079 align:start position:0% cases like instant messaging or given 00:42:19.079 --> 00:42:21.109 align:start position:0% cases like instant messaging or given someone<00:42:19.440> is<00:42:19.650> fast<00:42:20.160> sending<00:42:20.579> the<00:42:20.700> other<00:42:20.789> is 00:42:21.109 --> 00:42:21.119 align:start position:0% someone is fast sending the other is 00:42:21.119 --> 00:42:24.079 align:start position:0% someone is fast sending the other is slow<00:42:21.420> sending<00:42:21.930> then<00:42:22.529> we<00:42:22.769> can<00:42:22.979> adjust<00:42:23.489> this 00:42:24.079 --> 00:42:24.089 align:start position:0% slow sending then we can adjust this 00:42:24.089 --> 00:42:26.449 align:start position:0% slow sending then we can adjust this Poisson<00:42:24.539> process<00:42:25.019> to<00:42:25.170> be<00:42:25.289> sending<00:42:25.650> faster<00:42:26.249> or 00:42:26.449 --> 00:42:26.459 align:start position:0% Poisson process to be sending faster or 00:42:26.459 --> 00:42:28.729 align:start position:0% Poisson process to be sending faster or slower<00:42:26.729> but<00:42:27.420> we<00:42:27.479> actually<00:42:27.839> all<00:42:28.380> the<00:42:28.529> time 00:42:28.729 --> 00:42:28.739 align:start position:0% slower but we actually all the time 00:42:28.739 --> 00:42:30.739 align:start position:0% slower but we actually all the time confiscate<00:42:29.400> is<00:42:29.579> sending<00:42:29.969> pattern<00:42:30.450> of<00:42:30.630> the 00:42:30.739 --> 00:42:30.749 align:start position:0% confiscate is sending pattern of the 00:42:30.749 --> 00:42:32.900 align:start position:0% confiscate is sending pattern of the client<00:42:31.200> so<00:42:31.380> the<00:42:31.769> other<00:42:31.890> side<00:42:32.219> cannot<00:42:32.609> tell 00:42:32.900 --> 00:42:32.910 align:start position:0% client so the other side cannot tell 00:42:32.910 --> 00:42:34.759 align:start position:0% client so the other side cannot tell whether<00:42:33.150> you're<00:42:33.599> actually<00:42:33.869> communicating 00:42:34.759 --> 00:42:34.769 align:start position:0% whether you're actually communicating 00:42:34.769 --> 00:42:36.529 align:start position:0% whether you're actually communicating with<00:42:34.950> someone<00:42:35.400> or<00:42:35.640> you're<00:42:35.999> just<00:42:36.119> being 00:42:36.529 --> 00:42:36.539 align:start position:0% with someone or you're just being 00:42:36.539 --> 00:42:45.440 align:start position:0% with someone or you're just being completely<00:42:37.140> you<00:42:37.319> know<00:42:37.469> on<00:42:37.650> hold<00:42:43.099> so<00:42:44.209> yeah<00:42:45.209> so 00:42:45.440 --> 00:42:45.450 align:start position:0% completely you know on hold so yeah so 00:42:45.450 --> 00:42:49.130 align:start position:0% completely you know on hold so yeah so we<00:42:45.479> we<00:42:45.869> have<00:42:45.989> a<00:42:46.019> very<00:42:46.319> very<00:42:47.420> preliminary<00:42:48.420> let's 00:42:49.130 --> 00:42:49.140 align:start position:0% we we have a very very preliminary let's 00:42:49.140 --> 00:42:52.459 align:start position:0% we we have a very very preliminary let's call<00:42:49.380> it<00:42:49.529> demo<00:42:50.719> nobody<00:42:51.719> trusts<00:42:51.930> the<00:42:52.019> judges<00:42:52.319> on 00:42:52.459 --> 00:42:52.469 align:start position:0% call it demo nobody trusts the judges on 00:42:52.469 --> 00:42:53.749 align:start position:0% call it demo nobody trusts the judges on our<00:42:52.589> graphic<00:42:52.950> design<00:42:53.190> or<00:42:53.219> anything<00:42:53.519> like<00:42:53.729> that 00:42:53.749 --> 00:42:53.759 align:start position:0% our graphic design or anything like that 00:42:53.759 --> 00:42:56.150 align:start position:0% our graphic design or anything like that I'm<00:42:54.390> just<00:42:54.569> gonna<00:42:54.690> show<00:42:54.900> we<00:42:55.079> just<00:42:55.289> built<00:42:55.650> built 00:42:56.150 --> 00:42:56.160 align:start position:0% I'm just gonna show we just built built 00:42:56.160 --> 00:42:58.579 align:start position:0% I'm just gonna show we just built built a<00:42:56.249> client<00:42:56.640> cool<00:42:57.089> we<00:42:57.539> have<00:42:57.660> a<00:42:57.690> really<00:42:57.989> cool<00:42:58.289> like 00:42:58.579 --> 00:42:58.589 align:start position:0% a client cool we have a really cool like 00:42:58.589 --> 00:43:00.949 align:start position:0% a client cool we have a really cool like set<00:42:59.130> of<00:42:59.219> graphical<00:42:59.729> and<00:43:00.180> introduction<00:43:00.719> to<00:43:00.869> the 00:43:00.949 --> 00:43:00.959 align:start position:0% set of graphical and introduction to the 00:43:00.959 --> 00:43:03.699 align:start position:0% set of graphical and introduction to the client<00:43:01.289> to<00:43:01.319> it<00:43:01.499> as<00:43:01.589> well<00:43:01.799> you<00:43:02.039> started 00:43:03.699 --> 00:43:03.709 align:start position:0% client to it as well you started 00:43:03.709 --> 00:43:07.279 align:start position:0% client to it as well you started basically<00:43:04.709> I'm<00:43:05.160> about<00:43:05.609> to<00:43:05.789> run<00:43:05.969> it<00:43:06.150> here<00:43:06.289> to 00:43:07.279 --> 00:43:07.289 align:start position:0% basically I'm about to run it here to 00:43:07.289 --> 00:43:08.479 align:start position:0% basically I'm about to run it here to see<00:43:07.440> just<00:43:07.680> so<00:43:07.739> you<00:43:07.829> can<00:43:07.949> see<00:43:08.099> what<00:43:08.219> it<00:43:08.309> says 00:43:08.479 --> 00:43:08.489 align:start position:0% see just so you can see what it says 00:43:08.489 --> 00:43:11.989 align:start position:0% see just so you can see what it says I've<00:43:09.329> edited<00:43:09.569> an<00:43:10.079> ALICE<00:43:10.739> user<00:43:11.219> so<00:43:11.699> it's<00:43:11.849> like 00:43:11.989 --> 00:43:11.999 align:start position:0% I've edited an ALICE user so it's like 00:43:11.999 --> 00:43:15.499 align:start position:0% I've edited an ALICE user so it's like Luke's<00:43:12.719> client<00:43:13.049> in<00:43:13.229> it<00:43:13.380> Alice<00:43:13.940> so<00:43:14.940> Alice<00:43:15.209> now 00:43:15.499 --> 00:43:15.509 align:start position:0% Luke's client in it Alice so Alice now 00:43:15.509 --> 00:43:17.209 align:start position:0% Luke's client in it Alice so Alice now get<00:43:15.749> some<00:43:15.959> private<00:43:16.289> private<00:43:16.680> and<00:43:16.769> public<00:43:16.859> keys 00:43:17.209 --> 00:43:17.219 align:start position:0% get some private private and public keys 00:43:17.219 --> 00:43:21.199 align:start position:0% get some private private and public keys generated<00:43:17.729> and<00:43:17.880> stored<00:43:17.940> on<00:43:18.209> her<00:43:18.329> system<00:43:20.209> now 00:43:21.199 --> 00:43:21.209 align:start position:0% generated and stored on her system now 00:43:21.209 --> 00:43:24.529 align:start position:0% generated and stored on her system now it<00:43:21.359> started<00:43:21.660> to<00:43:21.779> run<00:43:23.029> in<00:43:24.029> the<00:43:24.209> kind<00:43:24.449> of 00:43:24.529 --> 00:43:24.539 align:start position:0% it started to run in the kind of 00:43:24.539 --> 00:43:26.269 align:start position:0% it started to run in the kind of boo-boos<00:43:24.930> client<00:43:25.499> binary<00:43:25.769> which<00:43:26.009> you'll<00:43:26.219> be 00:43:26.269 --> 00:43:26.279 align:start position:0% boo-boos client binary which you'll be 00:43:26.279 --> 00:43:27.920 align:start position:0% boo-boos client binary which you'll be able<00:43:26.430> you<00:43:26.699> can<00:43:26.729> you<00:43:27.029> can<00:43:27.209> integrate<00:43:27.390> against 00:43:27.920 --> 00:43:27.930 align:start position:0% able you can you can integrate against 00:43:27.930 --> 00:43:29.630 align:start position:0% able you can you can integrate against if<00:43:28.049> you're<00:43:28.229> actually<00:43:28.440> interested<00:43:28.829> in<00:43:29.309> like 00:43:29.630 --> 00:43:29.640 align:start position:0% if you're actually interested in like 00:43:29.640 --> 00:43:31.249 align:start position:0% if you're actually interested in like trying<00:43:30.119> to<00:43:30.239> make<00:43:30.390> your<00:43:30.539> applications<00:43:31.079> work 00:43:31.249 --> 00:43:31.259 align:start position:0% trying to make your applications work 00:43:31.259 --> 00:43:32.689 align:start position:0% trying to make your applications work with<00:43:31.469> a<00:43:31.499> mix<00:43:31.769> then<00:43:31.920> we<00:43:32.069> have<00:43:32.309> a<00:43:32.339> bunch<00:43:32.519> of 00:43:32.689 --> 00:43:32.699 align:start position:0% with a mix then we have a bunch of 00:43:32.699 --> 00:43:34.069 align:start position:0% with a mix then we have a bunch of running<00:43:33.029> mix<00:43:33.180> net<00:43:33.390> notes<00:43:33.599> we<00:43:33.809> have<00:43:33.839> this 00:43:34.069 --> 00:43:34.079 align:start position:0% running mix net notes we have this 00:43:34.079 --> 00:43:36.949 align:start position:0% running mix net notes we have this topology<00:43:34.259> of<00:43:34.709> six<00:43:35.430> notes<00:43:35.779> running<00:43:36.779> on<00:43:36.869> the 00:43:36.949 --> 00:43:36.959 align:start position:0% topology of six notes running on the 00:43:36.959 --> 00:43:39.410 align:start position:0% topology of six notes running on the internet<00:43:37.259> right<00:43:37.410> now<00:43:37.469> with<00:43:38.309> two<00:43:38.579> storage 00:43:39.410 --> 00:43:39.420 align:start position:0% internet right now with two storage 00:43:39.420 --> 00:43:41.660 align:start position:0% internet right now with two storage nodes<00:43:39.809> at<00:43:40.170> the<00:43:40.229> end<00:43:40.440> so<00:43:40.709> even<00:43:40.829> if<00:43:41.009> you're<00:43:41.160> kind 00:43:41.660 --> 00:43:41.670 align:start position:0% nodes at the end so even if you're kind 00:43:41.670 --> 00:43:43.489 align:start position:0% nodes at the end so even if you're kind of<00:43:41.729> end<00:43:41.910> user<00:43:42.150> clients<00:43:42.630> are<00:43:42.719> offline<00:43:43.019> you<00:43:43.349> can 00:43:43.489 --> 00:43:43.499 align:start position:0% of end user clients are offline you can 00:43:43.499 --> 00:43:46.009 align:start position:0% of end user clients are offline you can do<00:43:43.559> that<00:43:43.709> as<00:43:44.430> soon<00:43:44.670> as<00:43:44.759> we<00:43:44.969> told<00:43:45.180> Alice<00:43:45.569> as<00:43:45.839> soon 00:43:46.009 --> 00:43:46.019 align:start position:0% do that as soon as we told Alice as soon 00:43:46.019 --> 00:43:48.459 align:start position:0% do that as soon as we told Alice as soon as<00:43:46.109> Alice<00:43:46.380> said<00:43:46.559> Hana<00:43:46.769> to<00:43:46.949> run<00:43:47.099> this<00:43:47.249> client 00:43:48.459 --> 00:43:48.469 align:start position:0% as Alice said Hana to run this client 00:43:48.469 --> 00:43:51.199 align:start position:0% as Alice said Hana to run this client the<00:43:49.469> client<00:43:49.949> automatically<00:43:50.609> starts<00:43:50.999> sending 00:43:51.199 --> 00:43:51.209 align:start position:0% the client automatically starts sending 00:43:51.209 --> 00:43:54.229 align:start position:0% the client automatically starts sending packets<00:43:51.809> so<00:43:52.259> it<00:43:52.380> starts<00:43:52.849> encrypting<00:43:53.849> packets 00:43:54.229 --> 00:43:54.239 align:start position:0% packets so it starts encrypting packets 00:43:54.239 --> 00:43:55.729 align:start position:0% packets so it starts encrypting packets through<00:43:54.390> the<00:43:54.539> system<00:43:54.869> and<00:43:55.019> sending<00:43:55.380> them<00:43:55.559> back 00:43:55.729 --> 00:43:55.739 align:start position:0% through the system and sending them back 00:43:55.739 --> 00:43:58.189 align:start position:0% through the system and sending them back to<00:43:55.890> herself<00:43:56.459> right<00:43:56.969> so<00:43:57.209> starts<00:43:57.930> generating 00:43:58.189 --> 00:43:58.199 align:start position:0% to herself right so starts generating 00:43:58.199 --> 00:44:00.019 align:start position:0% to herself right so starts generating covered<00:43:58.829> traffic<00:43:59.190> as<00:43:59.309> soon<00:43:59.459> as<00:43:59.579> the<00:43:59.789> client 00:44:00.019 --> 00:44:00.029 align:start position:0% covered traffic as soon as the client 00:44:00.029 --> 00:44:02.299 align:start position:0% covered traffic as soon as the client has<00:44:00.119> started<00:44:00.390> up<00:44:00.509> this<00:44:01.140> client<00:44:01.559> doesn't<00:44:02.160> do 00:44:02.299 --> 00:44:02.309 align:start position:0% has started up this client doesn't do 00:44:02.309 --> 00:44:04.189 align:start position:0% has started up this client doesn't do anything<00:44:02.579> else<00:44:02.729> than<00:44:02.910> that<00:44:02.940> so<00:44:03.329> you<00:44:03.930> might<00:44:04.079> be 00:44:04.189 --> 00:44:04.199 align:start position:0% anything else than that so you might be 00:44:04.199 --> 00:44:05.479 align:start position:0% anything else than that so you might be a<00:44:04.229> bit<00:44:04.380> disappointed<00:44:04.589> if<00:44:05.069> you<00:44:05.160> just<00:44:05.339> like 00:44:05.479 --> 00:44:05.489 align:start position:0% a bit disappointed if you just like 00:44:05.489 --> 00:44:07.049 align:start position:0% a bit disappointed if you just like fired<00:44:06.089> up<00:44:06.299> in<00:44:06.449> the<00:44:06.539> newbie 00:44:07.049 --> 00:44:07.059 align:start position:0% fired up in the newbie 00:44:07.059 --> 00:44:09.430 align:start position:0% fired up in the newbie doesn't<00:44:08.059> really<00:44:08.240> do<00:44:08.480> anything<00:44:08.690> but<00:44:08.990> it<00:44:09.319> is 00:44:09.430 --> 00:44:09.440 align:start position:0% doesn't really do anything but it is 00:44:09.440 --> 00:44:10.599 align:start position:0% doesn't really do anything but it is actually<00:44:09.650> doing<00:44:09.829> something<00:44:10.220> if<00:44:10.309> you<00:44:10.369> like<00:44:10.430> if 00:44:10.599 --> 00:44:10.609 align:start position:0% actually doing something if you like if 00:44:10.609 --> 00:44:12.309 align:start position:0% actually doing something if you like if you<00:44:10.760> wireshark<00:44:11.510> yourself<00:44:11.869> you'll<00:44:12.019> be<00:44:12.079> able<00:44:12.170> to 00:44:12.309 --> 00:44:12.319 align:start position:0% you wireshark yourself you'll be able to 00:44:12.319 --> 00:44:13.359 align:start position:0% you wireshark yourself you'll be able to see<00:44:12.410> in<00:44:12.470> a<00:44:12.529> cover<00:44:12.710> traffic<00:44:13.039> going 00:44:13.359 --> 00:44:13.369 align:start position:0% see in a cover traffic going 00:44:13.369 --> 00:44:16.480 align:start position:0% see in a cover traffic going however<00:44:14.089> yeah<00:44:14.750> we're<00:44:15.470> basically<00:44:15.680> within<00:44:16.400> the 00:44:16.480 --> 00:44:16.490 align:start position:0% however yeah we're basically within the 00:44:16.490 --> 00:44:18.400 align:start position:0% however yeah we're basically within the next<00:44:16.640> week<00:44:16.880> our<00:44:17.089> plan<00:44:17.359> is<00:44:17.539> to<00:44:17.569> build<00:44:17.839> a<00:44:18.079> set<00:44:18.260> of 00:44:18.400 --> 00:44:18.410 align:start position:0% next week our plan is to build a set of 00:44:18.410 --> 00:44:21.220 align:start position:0% next week our plan is to build a set of socket<00:44:19.250> interfaces<00:44:19.789> so<00:44:19.940> you<00:44:20.000> can<00:44:20.240> just<00:44:20.900> have 00:44:21.220 --> 00:44:21.230 align:start position:0% socket interfaces so you can just have 00:44:21.230 --> 00:44:22.539 align:start position:0% socket interfaces so you can just have this<00:44:21.380> binary<00:44:21.650> sitting<00:44:22.220> inside<00:44:22.369> your 00:44:22.539 --> 00:44:22.549 align:start position:0% this binary sitting inside your 00:44:22.549 --> 00:44:24.339 align:start position:0% this binary sitting inside your application<00:44:23.180> you<00:44:23.359> can<00:44:23.480> connect<00:44:23.720> to<00:44:23.990> it<00:44:24.019> by 00:44:24.339 --> 00:44:24.349 align:start position:0% application you can connect to it by 00:44:24.349 --> 00:44:26.500 align:start position:0% application you can connect to it by either<00:44:24.619> a<00:44:24.769> web<00:44:24.950> socket<00:44:25.309> or<00:44:25.400> a<00:44:25.430> TCP<00:44:25.819> socket<00:44:26.180> and 00:44:26.500 --> 00:44:26.510 align:start position:0% either a web socket or a TCP socket and 00:44:26.510 --> 00:44:28.539 align:start position:0% either a web socket or a TCP socket and just<00:44:26.750> push<00:44:26.960> bytes<00:44:27.230> into<00:44:27.500> it<00:44:27.710> and<00:44:27.920> those<00:44:28.309> will 00:44:28.539 --> 00:44:28.549 align:start position:0% just push bytes into it and those will 00:44:28.549 --> 00:44:30.069 align:start position:0% just push bytes into it and those will be<00:44:28.700> those<00:44:28.970> bytes<00:44:29.210> that<00:44:29.359> you<00:44:29.539> push<00:44:29.750> into<00:44:29.960> it 00:44:30.069 --> 00:44:30.079 align:start position:0% be those bytes that you push into it 00:44:30.079 --> 00:44:32.740 align:start position:0% be those bytes that you push into it will<00:44:30.710> basically<00:44:30.980> go<00:44:31.490> through<00:44:31.849> the<00:44:32.390> mix<00:44:32.569> net 00:44:32.740 --> 00:44:32.750 align:start position:0% will basically go through the mix net 00:44:32.750 --> 00:44:34.269 align:start position:0% will basically go through the mix net and<00:44:32.960> you'll<00:44:33.109> be<00:44:33.170> able<00:44:33.230> to<00:44:33.410> send<00:44:33.559> messages<00:44:33.980> so 00:44:34.269 --> 00:44:34.279 align:start position:0% and you'll be able to send messages so 00:44:34.279 --> 00:44:36.339 align:start position:0% and you'll be able to send messages so that's<00:44:34.640> a<00:44:34.730> kind<00:44:34.940> of<00:44:34.970> example<00:44:35.480> of<00:44:35.599> that<00:44:35.779> we're 00:44:36.339 --> 00:44:36.349 align:start position:0% that's a kind of example of that we're 00:44:36.349 --> 00:44:39.430 align:start position:0% that's a kind of example of that we're building<00:44:36.549> a<00:44:37.549> chat<00:44:38.240> client<00:44:38.420> and<00:44:39.109> we've<00:44:39.230> got<00:44:39.410> it 00:44:39.430 --> 00:44:39.440 align:start position:0% building a chat client and we've got it 00:44:39.440 --> 00:44:41.380 align:start position:0% building a chat client and we've got it built<00:44:39.710> up<00:44:39.920> the<00:44:40.010> show<00:44:40.190> right<00:44:40.400> here<00:44:40.579> so<00:44:41.210> I'm<00:44:41.269> just 00:44:41.380 --> 00:44:41.390 align:start position:0% built up the show right here so I'm just 00:44:41.390 --> 00:44:43.870 align:start position:0% built up the show right here so I'm just gonna<00:44:41.480> I'm<00:44:41.960> just<00:44:42.019> backing<00:44:42.319> out<00:44:42.640> I'm<00:44:43.640> saying 00:44:43.870 --> 00:44:43.880 align:start position:0% gonna I'm just backing out I'm saying 00:44:43.880 --> 00:44:46.509 align:start position:0% gonna I'm just backing out I'm saying okay<00:44:44.180> cool<00:44:44.450> we're<00:44:44.990> gonna<00:44:45.109> go<00:44:45.349> to<00:44:46.220> the<00:44:46.309> chat 00:44:46.509 --> 00:44:46.519 align:start position:0% okay cool we're gonna go to the chat 00:44:46.519 --> 00:44:50.559 align:start position:0% okay cool we're gonna go to the chat client<00:44:46.819> demo<00:44:47.980> and<00:44:48.980> I'm<00:44:49.609> gonna<00:44:49.730> spark<00:44:50.059> it<00:44:50.180> up<00:44:50.269> so 00:44:50.559 --> 00:44:50.569 align:start position:0% client demo and I'm gonna spark it up so 00:44:50.569 --> 00:44:54.039 align:start position:0% client demo and I'm gonna spark it up so we're<00:44:50.750> gonna<00:44:50.809> use<00:44:51.309> this<00:44:52.309> Alice<00:44:52.849> thing<00:44:53.390> just 00:44:54.039 --> 00:44:54.049 align:start position:0% we're gonna use this Alice thing just 00:44:54.049 --> 00:44:58.539 align:start position:0% we're gonna use this Alice thing just Alice<00:44:54.380> user<00:44:56.470> cool<00:44:57.470> so<00:44:57.769> now<00:44:57.799> I'm<00:44:58.039> going<00:44:58.220> to<00:44:58.339> test 00:44:58.539 --> 00:44:58.549 align:start position:0% Alice user cool so now I'm going to test 00:44:58.549 --> 00:45:00.549 align:start position:0% Alice user cool so now I'm going to test what<00:44:58.819> Alice's<00:44:59.210> public<00:44:59.359> key<00:44:59.569> is<00:44:59.869> and<00:45:00.380> she<00:45:00.529> has 00:45:00.549 --> 00:45:00.559 align:start position:0% what Alice's public key is and she has 00:45:00.559 --> 00:45:01.750 align:start position:0% what Alice's public key is and she has to<00:45:00.740> figure<00:45:00.890> out<00:45:01.010> who<00:45:01.250> she<00:45:01.400> wants<00:45:01.670> to 00:45:01.750 --> 00:45:01.760 align:start position:0% to figure out who she wants to 00:45:01.760 --> 00:45:03.430 align:start position:0% to figure out who she wants to communicate<00:45:01.940> with<00:45:02.390> we've<00:45:02.690> also<00:45:02.869> made<00:45:03.109> a<00:45:03.170> bog 00:45:03.430 --> 00:45:03.440 align:start position:0% communicate with we've also made a bog 00:45:03.440 --> 00:45:06.039 align:start position:0% communicate with we've also made a bog user<00:45:03.829> and<00:45:04.369> I'm<00:45:04.910> just<00:45:05.390> gonna<00:45:05.480> start<00:45:05.630> him<00:45:06.019> in 00:45:06.039 --> 00:45:06.049 align:start position:0% user and I'm just gonna start him in 00:45:06.049 --> 00:45:10.269 align:start position:0% user and I'm just gonna start him in another<00:45:07.000> terminal<00:45:08.000> there<00:45:08.240> startup<00:45:08.990> bog<00:45:09.279> good 00:45:10.269 --> 00:45:10.279 align:start position:0% another terminal there startup bog good 00:45:10.279 --> 00:45:14.079 align:start position:0% another terminal there startup bog good cool<00:45:10.760> key<00:45:11.329> select<00:45:11.660> Alice's<00:45:12.140> public<00:45:12.289> key<00:45:13.089> which 00:45:14.079 --> 00:45:14.089 align:start position:0% cool key select Alice's public key which 00:45:14.089 --> 00:45:15.609 align:start position:0% cool key select Alice's public key which has<00:45:14.240> to<00:45:14.390> be<00:45:14.480> sent<00:45:14.660> out<00:45:14.779> of<00:45:14.930> fans<00:45:15.109> he<00:45:15.380> has<00:45:15.500> to 00:45:15.609 --> 00:45:15.619 align:start position:0% has to be sent out of fans he has to 00:45:15.619 --> 00:45:18.420 align:start position:0% has to be sent out of fans he has to know<00:45:15.769> that<00:45:16.269> cool<00:45:17.269> now<00:45:17.480> we<00:45:17.539> have<00:45:17.750> this<00:45:17.869> two 00:45:18.420 --> 00:45:18.430 align:start position:0% know that cool now we have this two 00:45:18.430 --> 00:45:21.579 align:start position:0% know that cool now we have this two message<00:45:19.430> thing<00:45:19.700> now<00:45:20.059> just<00:45:20.329> as<00:45:20.869> that<00:45:21.289> kind<00:45:21.470> of 00:45:21.579 --> 00:45:21.589 align:start position:0% message thing now just as that kind of 00:45:21.589 --> 00:45:23.410 align:start position:0% message thing now just as that kind of goes<00:45:21.829> through<00:45:21.859> I'll<00:45:22.579> just<00:45:22.759> explain<00:45:23.089> what's 00:45:23.410 --> 00:45:23.420 align:start position:0% goes through I'll just explain what's 00:45:23.420 --> 00:45:26.829 align:start position:0% goes through I'll just explain what's going<00:45:23.480> on<00:45:23.720> we<00:45:23.960> have<00:45:24.049> two<00:45:24.230> clients<00:45:25.599> both<00:45:26.599> of 00:45:26.829 --> 00:45:26.839 align:start position:0% going on we have two clients both of 00:45:26.839 --> 00:45:28.900 align:start position:0% going on we have two clients both of them<00:45:27.019> start<00:45:27.319> sending<00:45:27.710> cover<00:45:27.920> traffic<00:45:28.400> and<00:45:28.759> we 00:45:28.900 --> 00:45:28.910 align:start position:0% them start sending cover traffic and we 00:45:28.910 --> 00:45:30.339 align:start position:0% them start sending cover traffic and we have<00:45:29.029> a<00:45:29.059> dashboard<00:45:29.329> that<00:45:29.690> you<00:45:29.900> can<00:45:30.019> actually 00:45:30.339 --> 00:45:30.349 align:start position:0% have a dashboard that you can actually 00:45:30.349 --> 00:45:31.990 align:start position:0% have a dashboard that you can actually see<00:45:30.619> on<00:45:30.920> the<00:45:30.950> internet<00:45:31.400> right<00:45:31.549> now<00:45:31.579> it's<00:45:31.880> at 00:45:31.990 --> 00:45:32.000 align:start position:0% see on the internet right now it's at 00:45:32.000 --> 00:45:35.019 align:start position:0% see on the internet right now it's at dashboard<00:45:32.539> Jim<00:45:32.930> tech<00:45:33.140> dotnet<00:45:33.319> and<00:45:34.220> you<00:45:34.849> can 00:45:35.019 --> 00:45:35.029 align:start position:0% dashboard Jim tech dotnet and you can 00:45:35.029 --> 00:45:36.880 align:start position:0% dashboard Jim tech dotnet and you can we're<00:45:35.509> always<00:45:35.690> sending<00:45:36.079> cover<00:45:36.470> traffic 00:45:36.880 --> 00:45:36.890 align:start position:0% we're always sending cover traffic 00:45:36.890 --> 00:45:38.650 align:start position:0% we're always sending cover traffic through<00:45:37.099> that<00:45:37.250> anyway<00:45:37.700> and<00:45:37.940> you<00:45:38.509> can 00:45:38.650 --> 00:45:38.660 align:start position:0% through that anyway and you can 00:45:38.660 --> 00:45:43.960 align:start position:0% through that anyway and you can basically<00:45:38.839> see<00:45:42.309> the<00:45:43.309> cover<00:45:43.490> traffic<00:45:43.819> going 00:45:43.960 --> 00:45:43.970 align:start position:0% basically see the cover traffic going 00:45:43.970 --> 00:45:45.549 align:start position:0% basically see the cover traffic going through<00:45:44.059> the<00:45:44.299> nodes<00:45:44.480> is<00:45:44.690> it<00:45:44.809> you<00:45:44.960> can<00:45:45.140> see<00:45:45.259> it 00:45:45.549 --> 00:45:45.559 align:start position:0% through the nodes is it you can see it 00:45:45.559 --> 00:45:48.130 align:start position:0% through the nodes is it you can see it tells<00:45:45.799> you<00:45:46.039> you<00:45:46.549> know<00:45:46.670> this<00:45:47.390> note<00:45:47.660> here<00:45:47.900> let's 00:45:48.130 --> 00:45:48.140 align:start position:0% tells you you know this note here let's 00:45:48.140 --> 00:45:51.910 align:start position:0% tells you you know this note here let's say<00:45:48.319> in<00:45:48.740> the<00:45:48.859> last<00:45:49.039> one<00:45:49.309> second<00:45:49.819> it<00:45:50.240> sent<00:45:50.920> 20 00:45:51.910 --> 00:45:51.920 align:start position:0% say in the last one second it sent 20 00:45:51.920 --> 00:45:55.029 align:start position:0% say in the last one second it sent 20 packets<00:45:52.339> and<00:45:52.549> it<00:45:52.730> received<00:45:53.200> 18<00:45:54.200> packets<00:45:54.650> or<00:45:54.799> 12 00:45:55.029 --> 00:45:55.039 align:start position:0% packets and it received 18 packets or 12 00:45:55.039 --> 00:45:56.589 align:start position:0% packets and it received 18 packets or 12 packs<00:45:55.279> or<00:45:55.490> whatever<00:45:55.730> whatever<00:45:55.910> times<00:45:56.299> to<00:45:56.480> be 00:45:56.589 --> 00:45:56.599 align:start position:0% packs or whatever whatever times to be 00:45:56.599 --> 00:45:58.569 align:start position:0% packs or whatever whatever times to be so<00:45:57.079> you<00:45:57.140> can<00:45:57.259> basically<00:45:57.410> get<00:45:57.799> a<00:45:57.859> view<00:45:58.160> overall 00:45:58.569 --> 00:45:58.579 align:start position:0% so you can basically get a view overall 00:45:58.579 --> 00:46:00.099 align:start position:0% so you can basically get a view overall of<00:45:58.910> the<00:45:58.940> whole<00:45:59.150> network<00:45:59.299> and<00:45:59.599> what 00:46:00.099 --> 00:46:00.109 align:start position:0% of the whole network and what 00:46:00.109 --> 00:46:04.719 align:start position:0% of the whole network and what within<00:46:00.440> it<00:46:02.349> yeah<00:46:03.349> so<00:46:03.799> you<00:46:04.039> can<00:46:04.160> see<00:46:04.279> the<00:46:04.400> speeds 00:46:04.719 --> 00:46:04.729 align:start position:0% within it yeah so you can see the speeds 00:46:04.729 --> 00:46:06.519 align:start position:0% within it yeah so you can see the speeds this<00:46:04.910> is<00:46:04.969> actually<00:46:05.420> going<00:46:05.779> through<00:46:05.930> from<00:46:06.410> my 00:46:06.519 --> 00:46:06.529 align:start position:0% this is actually going through from my 00:46:06.529 --> 00:46:10.880 align:start position:0% this is actually going through from my hotel<00:46:06.829> room<00:46:06.859> in<00:46:07.099> Japan<00:46:07.430> to<00:46:08.059> our<00:46:08.239> mix<00:46:08.749> net<00:46:08.959> in 00:46:10.880 --> 00:46:10.890 align:start position:0% hotel room in Japan to our mix net in 00:46:10.890 --> 00:46:12.239 align:start position:0% hotel room in Japan to our mix net in [Music] 00:46:12.239 --> 00:46:12.249 align:start position:0% [Music] 00:46:12.249 --> 00:46:15.609 align:start position:0% [Music] Europe<00:46:13.249> somewhere<00:46:14.109> through<00:46:15.109> the<00:46:15.229> six<00:46:15.410> notes 00:46:15.609 --> 00:46:15.619 align:start position:0% Europe somewhere through the six notes 00:46:15.619 --> 00:46:17.529 align:start position:0% Europe somewhere through the six notes and<00:46:15.859> then<00:46:15.950> back<00:46:16.130> up<00:46:16.339> back<00:46:16.609> to<00:46:16.789> Japan<00:46:17.150> so<00:46:17.390> it's 00:46:17.529 --> 00:46:17.539 align:start position:0% and then back up back to Japan so it's 00:46:17.539 --> 00:46:19.390 align:start position:0% and then back up back to Japan so it's you<00:46:18.140> can<00:46:18.259> see<00:46:18.289> the<00:46:18.469> speeds<00:46:18.739> actually<00:46:18.979> not<00:46:19.219> that 00:46:19.390 --> 00:46:19.400 align:start position:0% you can see the speeds actually not that 00:46:19.400 --> 00:46:22.479 align:start position:0% you can see the speeds actually not that bad<00:46:19.609> as<00:46:19.849> far<00:46:20.029> as<00:46:20.089> when<00:46:20.779> something<00:46:21.170> is<00:46:22.009> typed<00:46:22.309> in 00:46:22.479 --> 00:46:22.489 align:start position:0% bad as far as when something is typed in 00:46:22.489 --> 00:46:24.160 align:start position:0% bad as far as when something is typed in here<00:46:22.789> or<00:46:22.969> you<00:46:23.180> can<00:46:23.450> see<00:46:23.630> it<00:46:23.660> appear<00:46:24.019> on<00:46:24.079> the 00:46:24.160 --> 00:46:24.170 align:start position:0% here or you can see it appear on the 00:46:24.170 --> 00:46:26.650 align:start position:0% here or you can see it appear on the other<00:46:24.319> side<00:46:24.469> quite<00:46:24.680> rapidly<00:46:25.099> so<00:46:25.640> it's<00:46:25.789> yeah 00:46:26.650 --> 00:46:26.660 align:start position:0% other side quite rapidly so it's yeah 00:46:26.660 --> 00:46:28.930 align:start position:0% other side quite rapidly so it's yeah it's<00:46:27.140> definitely<00:46:27.619> sub-second<00:46:28.369> latency<00:46:28.759> it's 00:46:28.930 --> 00:46:28.940 align:start position:0% it's definitely sub-second latency it's 00:46:28.940 --> 00:46:31.660 align:start position:0% it's definitely sub-second latency it's like<00:46:29.119> sort<00:46:29.359> of<00:46:29.650> 300<00:46:30.650> 400<00:46:31.009> milliseconds<00:46:31.549> I'd 00:46:31.660 --> 00:46:31.670 align:start position:0% like sort of 300 400 milliseconds I'd 00:46:31.670 --> 00:46:35.079 align:start position:0% like sort of 300 400 milliseconds I'd say<00:46:31.849> of<00:46:32.809> latency<00:46:33.170> that<00:46:33.739> gets<00:46:33.920> added<00:46:34.130> at<00:46:34.910> that 00:46:35.079 --> 00:46:35.089 align:start position:0% say of latency that gets added at that 00:46:35.089 --> 00:46:37.479 align:start position:0% say of latency that gets added at that thing<00:46:35.299> so<00:46:35.660> we<00:46:35.809> can<00:46:35.839> also<00:46:36.079> see<00:46:36.410> the<00:46:37.069> mixed<00:46:37.309> notes 00:46:37.479 --> 00:46:37.489 align:start position:0% thing so we can also see the mixed notes 00:46:37.489 --> 00:46:42.279 align:start position:0% thing so we can also see the mixed notes and<00:46:38.469> the<00:46:39.469> validators<00:46:39.950> here<00:46:40.160> as<00:46:40.249> well<00:46:40.719> okay<00:46:41.719> if 00:46:42.279 --> 00:46:42.289 align:start position:0% and the validators here as well okay if 00:46:42.289 --> 00:46:43.829 align:start position:0% and the validators here as well okay if I<00:46:42.469> bet<00:46:42.680> just<00:46:42.859> back<00:46:43.009> it<00:46:43.160> up<00:46:43.249> a<00:46:43.400> little<00:46:43.579> bit 00:46:43.829 --> 00:46:43.839 align:start position:0% I bet just back it up a little bit 00:46:43.839 --> 00:46:52.720 align:start position:0% I bet just back it up a little bit you'll<00:46:44.839> be<00:46:44.989> able<00:46:45.049> to<00:46:45.259> see<00:46:48.459> right<00:46:49.459> here 00:46:52.720 --> 00:46:52.730 align:start position:0% 00:46:52.730 --> 00:46:55.960 align:start position:0% yeah<00:46:53.349> cool<00:46:54.410> over<00:46:55.280> on<00:46:55.369> the<00:46:55.490> right-hand<00:46:55.640> side 00:46:55.960 --> 00:46:55.970 align:start position:0% yeah cool over on the right-hand side 00:46:55.970 --> 00:46:57.579 align:start position:0% yeah cool over on the right-hand side there<00:46:56.180> you<00:46:56.210> can<00:46:56.420> see<00:46:56.570> it<00:46:56.690> says<00:46:56.839> received<00:46:57.290> and 00:46:57.579 --> 00:46:57.589 align:start position:0% there you can see it says received and 00:46:57.589 --> 00:46:59.890 align:start position:0% there you can see it says received and sent<00:46:57.859> in<00:46:58.460> that<00:46:58.700> one<00:46:58.910> second<00:46:59.329> period<00:46:59.570> that's 00:46:59.890 --> 00:46:59.900 align:start position:0% sent in that one second period that's 00:46:59.900 --> 00:47:01.720 align:start position:0% sent in that one second period that's what<00:47:00.200> the<00:47:00.380> mixed<00:47:00.800> nodes<00:47:01.010> actually<00:47:01.190> receiving 00:47:01.720 --> 00:47:01.730 align:start position:0% what the mixed nodes actually receiving 00:47:01.730 --> 00:47:03.790 align:start position:0% what the mixed nodes actually receiving in<00:47:02.000> and<00:47:02.240> you<00:47:02.570> can<00:47:02.720> see<00:47:02.839> you<00:47:03.140> can<00:47:03.260> kind<00:47:03.470> of<00:47:03.560> tell 00:47:03.790 --> 00:47:03.800 align:start position:0% in and you can see you can kind of tell 00:47:03.800 --> 00:47:05.829 align:start position:0% in and you can see you can kind of tell that<00:47:03.950> the<00:47:04.099> orbital<00:47:04.520> reordering<00:47:05.270> is<00:47:05.390> happening 00:47:05.829 --> 00:47:05.839 align:start position:0% that the orbital reordering is happening 00:47:05.839 --> 00:47:07.780 align:start position:0% that the orbital reordering is happening inside<00:47:06.079> the<00:47:06.260> nodes<00:47:06.470> because<00:47:07.250> otherwise<00:47:07.490> the 00:47:07.780 --> 00:47:07.790 align:start position:0% inside the nodes because otherwise the 00:47:07.790 --> 00:47:09.069 align:start position:0% inside the nodes because otherwise the numbers<00:47:08.060> would<00:47:08.210> be<00:47:08.240> exactly<00:47:08.599> the<00:47:08.839> same 00:47:09.069 --> 00:47:09.079 align:start position:0% numbers would be exactly the same 00:47:09.079 --> 00:47:11.109 align:start position:0% numbers would be exactly the same I've<00:47:09.290> sent<00:47:09.530> and<00:47:09.680> received<00:47:09.710> in<00:47:10.700> that<00:47:10.940> one 00:47:11.109 --> 00:47:11.119 align:start position:0% I've sent and received in that one 00:47:11.119 --> 00:47:13.900 align:start position:0% I've sent and received in that one second<00:47:11.420> period<00:47:11.570> uh<00:47:11.720> they're<00:47:11.869> not<00:47:11.990> across<00:47:12.910> all 00:47:13.900 --> 00:47:13.910 align:start position:0% second period uh they're not across all 00:47:13.910 --> 00:47:15.160 align:start position:0% second period uh they're not across all of<00:47:14.060> this<00:47:14.150> thing<00:47:14.359> said<00:47:14.599> so<00:47:14.839> that's<00:47:14.930> the 00:47:15.160 --> 00:47:15.170 align:start position:0% of this thing said so that's the 00:47:15.170 --> 00:47:16.800 align:start position:0% of this thing said so that's the reordering<00:47:15.619> of<00:47:15.800> the<00:47:15.890> packet<00:47:16.220> of<00:47:16.280> the<00:47:16.339> packet 00:47:16.800 --> 00:47:16.810 align:start position:0% reordering of the packet of the packet 00:47:16.810 --> 00:47:22.290 align:start position:0% reordering of the packet of the packet [Music] 00:47:22.290 --> 00:47:22.300 align:start position:0% 00:47:22.300 --> 00:47:25.630 align:start position:0% yeah<00:47:23.300> yeah<00:47:23.480> so<00:47:23.660> there's<00:47:23.839> there's<00:47:24.230> the<00:47:25.099> the 00:47:25.630 --> 00:47:25.640 align:start position:0% yeah yeah so there's there's the the 00:47:25.640 --> 00:47:27.730 align:start position:0% yeah yeah so there's there's the the rico's<00:47:25.940> that<00:47:26.089> we<00:47:26.180> have<00:47:26.329> are<00:47:26.540> completely<00:47:26.740> open 00:47:27.730 --> 00:47:27.740 align:start position:0% rico's that we have are completely open 00:47:27.740 --> 00:47:29.560 align:start position:0% rico's that we have are completely open the<00:47:28.400> chat<00:47:28.609> client<00:47:28.880> might<00:47:29.000> not<00:47:29.150> be<00:47:29.300> but<00:47:29.480> that's 00:47:29.560 --> 00:47:29.570 align:start position:0% the chat client might not be but that's 00:47:29.570 --> 00:47:32.079 align:start position:0% the chat client might not be but that's more<00:47:29.930> oversight<00:47:30.380> the<00:47:30.829> the<00:47:31.369> main<00:47:31.550> notes<00:47:31.820> that 00:47:32.079 --> 00:47:32.089 align:start position:0% more oversight the the main notes that 00:47:32.089 --> 00:47:33.790 align:start position:0% more oversight the the main notes that both<00:47:32.390> have<00:47:32.599> been<00:47:32.750> in<00:47:32.900> validator<00:47:33.380> notes<00:47:33.619> that 00:47:33.790 --> 00:47:33.800 align:start position:0% both have been in validator notes that 00:47:33.800 --> 00:47:36.160 align:start position:0% both have been in validator notes that run<00:47:33.920> the<00:47:33.980> credential<00:47:34.369> system<00:47:34.730> and<00:47:34.910> the<00:47:35.480> mixed 00:47:36.160 --> 00:47:36.170 align:start position:0% run the credential system and the mixed 00:47:36.170 --> 00:47:38.260 align:start position:0% run the credential system and the mixed notes<00:47:36.349> that<00:47:36.619> run<00:47:37.280> the<00:47:37.430> the<00:47:37.700> mixed<00:47:37.910> mixing 00:47:38.260 --> 00:47:38.270 align:start position:0% notes that run the the mixed mixing 00:47:38.270 --> 00:47:40.150 align:start position:0% notes that run the the mixed mixing system<00:47:38.450> it's<00:47:39.079> all<00:47:39.230> open<00:47:39.380> right<00:47:39.589> now<00:47:39.859> so<00:47:40.070> you 00:47:40.150 --> 00:47:40.160 align:start position:0% system it's all open right now so you 00:47:40.160 --> 00:47:42.160 align:start position:0% system it's all open right now so you can<00:47:40.190> you<00:47:40.490> can<00:47:40.640> look<00:47:40.670> at<00:47:40.940> it<00:47:41.089> have<00:47:41.720> a<00:47:41.780> look<00:47:41.930> to<00:47:42.050> it 00:47:42.160 --> 00:47:42.170 align:start position:0% can you can look at it have a look to it 00:47:42.170 --> 00:47:52.140 align:start position:0% can you can look at it have a look to it it's<00:47:42.800> not<00:47:42.920> super<00:47:43.430> beautiful<00:47:43.640> yeah<00:47:49.900> services 00:47:52.140 --> 00:47:52.150 align:start position:0% it's not super beautiful yeah services 00:47:52.150 --> 00:47:53.589 align:start position:0% it's not super beautiful yeah services no<00:47:53.150> clora 00:47:53.589 --> 00:47:53.599 align:start position:0% no clora 00:47:53.599 --> 00:47:55.060 align:start position:0% no clora so<00:47:53.839> right<00:47:53.990> now<00:47:54.170> we're<00:47:54.380> running<00:47:54.650> a<00:47:54.710> directory 00:47:55.060 --> 00:47:55.070 align:start position:0% so right now we're running a directory 00:47:55.070 --> 00:47:57.910 align:start position:0% so right now we're running a directory server<00:47:55.280> at<00:47:55.460> directory<00:47:55.970> w<00:47:56.329> tech<00:47:56.540> dotnet<00:47:56.920> bit 00:47:57.910 --> 00:47:57.920 align:start position:0% server at directory w tech dotnet bit 00:47:57.920 --> 00:47:59.920 align:start position:0% server at directory w tech dotnet bit centralized<00:47:58.460> at<00:47:58.819> the<00:47:59.030> moment<00:47:59.329> but<00:47:59.630> that's<00:47:59.810> a 00:47:59.920 --> 00:47:59.930 align:start position:0% centralized at the moment but that's a 00:47:59.930 --> 00:48:01.329 align:start position:0% centralized at the moment but that's a temporary<00:48:00.170> things<00:48:00.530> we<00:48:00.740> need<00:48:00.859> to<00:48:00.890> bootstrap 00:48:01.329 --> 00:48:01.339 align:start position:0% temporary things we need to bootstrap 00:48:01.339 --> 00:48:02.620 align:start position:0% temporary things we need to bootstrap the<00:48:01.369> network<00:48:01.760> and<00:48:02.030> then<00:48:02.180> I<00:48:02.270> need<00:48:02.420> to<00:48:02.450> figure 00:48:02.620 --> 00:48:02.630 align:start position:0% the network and then I need to figure 00:48:02.630 --> 00:48:05.470 align:start position:0% the network and then I need to figure out<00:48:03.069> is<00:48:04.069> going<00:48:04.190> to<00:48:04.250> be<00:48:04.369> as<00:48:04.490> far<00:48:04.700> as<00:48:04.730> just<00:48:04.970> you 00:48:05.470 --> 00:48:05.480 align:start position:0% out is going to be as far as just you 00:48:05.480 --> 00:48:29.470 align:start position:0% out is going to be as far as just you know<00:48:17.829> deciding<00:48:18.829> in<00:48:18.980> advance<00:48:27.700> how<00:48:28.700> to<00:48:28.970> miss<00:48:29.240> mix 00:48:29.470 --> 00:48:29.480 align:start position:0% know deciding in advance how to miss mix 00:48:29.480 --> 00:48:31.960 align:start position:0% know deciding in advance how to miss mix man<00:48:29.630> so<00:48:29.990> so<00:48:30.349> they're<00:48:30.530> a<00:48:30.859> couple<00:48:31.520> of<00:48:31.700> reasons 00:48:31.960 --> 00:48:31.970 align:start position:0% man so so they're a couple of reasons 00:48:31.970 --> 00:48:34.270 align:start position:0% man so so they're a couple of reasons why<00:48:32.480> the<00:48:33.109> first<00:48:33.380> one<00:48:33.560> is<00:48:33.770> if<00:48:33.980> you're<00:48:34.130> in<00:48:34.190> the 00:48:34.270 --> 00:48:34.280 align:start position:0% why the first one is if you're in the 00:48:34.280 --> 00:48:36.170 align:start position:0% why the first one is if you're in the center<00:48:34.640> and<00:48:34.910> your<00:48:35.390> pick 00:48:36.170 --> 00:48:36.180 align:start position:0% center and your pick 00:48:36.180 --> 00:48:39.650 align:start position:0% center and your pick delays<00:48:36.480> in<00:48:36.990> advance<00:48:37.500> for<00:48:37.950> each<00:48:38.130> halt<00:48:38.670> you<00:48:39.390> know 00:48:39.650 --> 00:48:39.660 align:start position:0% delays in advance for each halt you know 00:48:39.660 --> 00:48:42.140 align:start position:0% delays in advance for each halt you know where<00:48:40.230> your<00:48:40.470> packet<00:48:40.980> should<00:48:41.250> arrive<00:48:41.819> at<00:48:42.030> the 00:48:42.140 --> 00:48:42.150 align:start position:0% where your packet should arrive at the 00:48:42.150 --> 00:48:44.540 align:start position:0% where your packet should arrive at the other<00:48:42.270> end<00:48:42.540> this<00:48:43.380> allows<00:48:43.800> you<00:48:43.980> to<00:48:44.099> flex<00:48:44.430> our 00:48:44.540 --> 00:48:44.550 align:start position:0% other end this allows you to flex our 00:48:44.550 --> 00:48:47.150 align:start position:0% other end this allows you to flex our program<00:48:45.030> expecting<00:48:45.660> an<00:48:46.020> acknowledgment<00:48:46.980> for 00:48:47.150 --> 00:48:47.160 align:start position:0% program expecting an acknowledgment for 00:48:47.160 --> 00:48:48.890 align:start position:0% program expecting an acknowledgment for your<00:48:47.280> packet<00:48:47.670> so<00:48:48.059> you<00:48:48.119> will<00:48:48.420> know<00:48:48.599> whether 00:48:48.890 --> 00:48:48.900 align:start position:0% your packet so you will know whether 00:48:48.900 --> 00:48:51.079 align:start position:0% your packet so you will know whether your<00:48:49.230> message<00:48:49.710> go<00:48:49.920> to<00:48:49.980> the<00:48:50.190> other<00:48:50.339> end<00:48:50.430> or<00:48:50.880> not 00:48:51.079 --> 00:48:51.089 align:start position:0% your message go to the other end or not 00:48:51.089 --> 00:48:53.329 align:start position:0% your message go to the other end or not whether<00:48:51.569> one<00:48:51.869> of<00:48:51.990> the<00:48:52.140> mixes<00:48:52.530> dropped<00:48:52.890> it<00:48:53.099> or 00:48:53.329 --> 00:48:53.339 align:start position:0% whether one of the mixes dropped it or 00:48:53.339 --> 00:48:57.109 align:start position:0% whether one of the mixes dropped it or not<00:48:53.569> so<00:48:54.569> that's<00:48:54.780> one<00:48:54.930> of<00:48:54.960> the<00:48:55.170> advantages<00:48:56.119> yeah 00:48:57.109 --> 00:48:57.119 align:start position:0% not so that's one of the advantages yeah 00:48:57.119 --> 00:48:59.089 align:start position:0% not so that's one of the advantages yeah it's<00:48:57.599> the<00:48:57.720> main<00:48:57.869> one<00:48:58.050> because<00:48:58.349> also<00:48:58.710> it<00:48:58.920> will 00:48:59.089 --> 00:48:59.099 align:start position:0% it's the main one because also it will 00:48:59.099 --> 00:49:02.390 align:start position:0% it's the main one because also it will allow<00:48:59.369> you<00:48:59.430> to<00:48:59.550> detect<00:49:00.030> malicious<00:49:00.210> mix<00:49:00.660> now<00:49:01.400> if 00:49:02.390 --> 00:49:02.400 align:start position:0% allow you to detect malicious mix now if 00:49:02.400 --> 00:49:04.730 align:start position:0% allow you to detect malicious mix now if your<00:49:02.730> packet<00:49:03.180> you<00:49:03.559> didn't<00:49:04.559> get<00:49:04.650> the 00:49:04.730 --> 00:49:04.740 align:start position:0% your packet you didn't get the 00:49:04.740 --> 00:49:06.170 align:start position:0% your packet you didn't get the acknowledgement<00:49:04.859> for<00:49:05.490> your<00:49:05.579> packet 00:49:06.170 --> 00:49:06.180 align:start position:0% acknowledgement for your packet 00:49:06.180 --> 00:49:07.790 align:start position:0% acknowledgement for your packet this<00:49:06.480> means<00:49:06.720> that<00:49:06.869> maybe<00:49:07.050> your<00:49:07.319> packet<00:49:07.619> will 00:49:07.790 --> 00:49:07.800 align:start position:0% this means that maybe your packet will 00:49:07.800 --> 00:49:09.170 align:start position:0% this means that maybe your packet will throw<00:49:07.980> someone<00:49:08.250> on<00:49:08.460> the<00:49:08.579> way<00:49:08.700> and<00:49:08.940> you<00:49:08.970> should 00:49:09.170 --> 00:49:09.180 align:start position:0% throw someone on the way and you should 00:49:09.180 --> 00:49:11.540 align:start position:0% throw someone on the way and you should investigate<00:49:09.839> which<00:49:10.559> of<00:49:10.829> those<00:49:10.950> makes<00:49:11.309> notes 00:49:11.540 --> 00:49:11.550 align:start position:0% investigate which of those makes notes 00:49:11.550 --> 00:49:13.309 align:start position:0% investigate which of those makes notes potentially<00:49:12.180> dropped<00:49:12.420> your<00:49:12.569> packet<00:49:12.960> and<00:49:13.109> so 00:49:13.309 --> 00:49:13.319 align:start position:0% potentially dropped your packet and so 00:49:13.319 --> 00:49:20.720 align:start position:0% potentially dropped your packet and so on<00:49:13.440> I<00:49:18.109> just<00:49:19.109> see<00:49:19.260> that<00:49:19.410> your<00:49:19.740> received<00:49:20.460> and 00:49:20.720 --> 00:49:20.730 align:start position:0% on I just see that your received and 00:49:20.730 --> 00:49:24.410 align:start position:0% on I just see that your received and sent<00:49:21.210> I<00:49:21.869> expected<00:49:22.740> that<00:49:22.859> to<00:49:22.890> be<00:49:23.069> equal<00:49:23.730> tender 00:49:24.410 --> 00:49:24.420 align:start position:0% sent I expected that to be equal tender 00:49:24.420 --> 00:49:30.349 align:start position:0% sent I expected that to be equal tender so<00:49:24.690> you're<00:49:24.930> not<00:49:25.050> received<00:49:25.530> edges<00:49:29.359> they're 00:49:30.349 --> 00:49:30.359 align:start position:0% so you're not received edges they're 00:49:30.359 --> 00:49:32.059 align:start position:0% so you're not received edges they're supposed<00:49:30.690> to<00:49:30.750> be<00:49:30.869> different<00:49:31.050> because<00:49:31.440> the<00:49:31.680> the 00:49:32.059 --> 00:49:32.069 align:start position:0% supposed to be different because the the 00:49:32.069 --> 00:49:34.370 align:start position:0% supposed to be different because the the packet<00:49:32.940> says<00:49:33.059> they<00:49:33.270> received<00:49:33.599> our<00:49:33.869> help<00:49:34.109> for 00:49:34.370 --> 00:49:34.380 align:start position:0% packet says they received our help for 00:49:34.380 --> 00:49:36.950 align:start position:0% packet says they received our help for random<00:49:34.710> amounts<00:49:34.980> of<00:49:35.099> time<00:49:35.510> so<00:49:36.510> that's<00:49:36.690> why<00:49:36.839> we 00:49:36.950 --> 00:49:36.960 align:start position:0% random amounts of time so that's why we 00:49:36.960 --> 00:49:38.450 align:start position:0% random amounts of time so that's why we have<00:49:37.079> the<00:49:37.170> reordering<00:49:37.559> so<00:49:37.920> they<00:49:38.099> were<00:49:38.160> the 00:49:38.450 --> 00:49:38.460 align:start position:0% have the reordering so they were the 00:49:38.460 --> 00:49:41.480 align:start position:0% have the reordering so they were the same<00:49:38.670> that's<00:49:39.089> when<00:49:39.359> we<00:49:39.480> would<00:49:39.599> be<00:49:40.490> unhappy 00:49:41.480 --> 00:49:41.490 align:start position:0% same that's when we would be unhappy 00:49:41.490 --> 00:49:43.220 align:start position:0% same that's when we would be unhappy because<00:49:42.000> then<00:49:42.329> we<00:49:42.480> would<00:49:42.599> be<00:49:42.720> going<00:49:42.809> like<00:49:43.049> why 00:49:43.220 --> 00:49:43.230 align:start position:0% because then we would be going like why 00:49:43.230 --> 00:49:45.140 align:start position:0% because then we would be going like why why<00:49:43.500> it's<00:49:43.710> just<00:49:43.920> me<00:49:44.369> what<00:49:44.849> if<00:49:44.940> it's<00:49:45.059> just 00:49:45.140 --> 00:49:45.150 align:start position:0% why it's just me what if it's just 00:49:45.150 --> 00:49:46.849 align:start position:0% why it's just me what if it's just passing<00:49:45.750> the<00:49:45.869> same<00:49:46.079> things<00:49:46.319> in<00:49:46.440> and<00:49:46.619> out<00:49:46.680> in 00:49:46.849 --> 00:49:46.859 align:start position:0% passing the same things in and out in 00:49:46.859 --> 00:49:48.049 align:start position:0% passing the same things in and out in the<00:49:46.920> same<00:49:47.040> order<00:49:47.220> and<00:49:47.430> it's<00:49:47.549> not<00:49:47.670> reordering 00:49:48.049 --> 00:49:48.059 align:start position:0% the same order and it's not reordering 00:49:48.059 --> 00:49:50.809 align:start position:0% the same order and it's not reordering anything<00:49:48.450> what's<00:49:48.990> actually<00:49:49.470> doing<00:49:49.859> is<00:49:50.040> it's 00:49:50.809 --> 00:49:50.819 align:start position:0% anything what's actually doing is it's 00:49:50.819 --> 00:49:52.039 align:start position:0% anything what's actually doing is it's you<00:49:51.089> we<00:49:51.210> can<00:49:51.329> tell<00:49:51.450> it's<00:49:51.599> working<00:49:51.990> because 00:49:52.039 --> 00:49:52.049 align:start position:0% you we can tell it's working because 00:49:52.049 --> 00:49:55.250 align:start position:0% you we can tell it's working because it's<00:49:52.290> holding<00:49:52.650> the<00:49:52.710> packets<00:49:53.190> for<00:49:53.490> a<00:49:54.420> random 00:49:55.250 --> 00:49:55.260 align:start position:0% it's holding the packets for a random 00:49:55.260 --> 00:49:57.799 align:start position:0% it's holding the packets for a random interval<00:49:55.680> and<00:49:56.119> therefore<00:49:57.119> we<00:49:57.420> can<00:49:57.540> see<00:49:57.690> that 00:49:57.799 --> 00:49:57.809 align:start position:0% interval and therefore we can see that 00:49:57.809 --> 00:50:00.829 align:start position:0% interval and therefore we can see that it's<00:49:57.930> actually<00:49:58.020> mixing<00:49:58.530> but<00:49:59.270> why<00:50:00.270> didn't<00:50:00.630> some 00:50:00.829 --> 00:50:00.839 align:start position:0% it's actually mixing but why didn't some 00:50:00.839 --> 00:50:05.160 align:start position:0% it's actually mixing but why didn't some notes<00:50:01.109> have<00:50:01.890> one<00:50:02.400> messages<00:50:02.970> and 00:50:05.160 --> 00:50:05.170 align:start position:0% notes have one messages and 00:50:05.170 --> 00:50:08.590 align:start position:0% notes have one messages and yeah<00:50:06.170> so<00:50:06.470> they<00:50:06.830> also<00:50:07.040> like<00:50:07.340> imagine<00:50:08.240> like<00:50:08.390> in 00:50:08.590 --> 00:50:08.600 align:start position:0% yeah so they also like imagine like in 00:50:08.600 --> 00:50:11.230 align:start position:0% yeah so they also like imagine like in one<00:50:08.780> second<00:50:09.170> Felicity<00:50:09.590> and<00:50:09.830> packets<00:50:10.310> in<00:50:11.090> the 00:50:11.230 --> 00:50:11.240 align:start position:0% one second Felicity and packets in the 00:50:11.240 --> 00:50:13.720 align:start position:0% one second Felicity and packets in the other<00:50:11.390> second<00:50:11.870> you<00:50:11.990> Center<00:50:12.320> five<00:50:12.470> of<00:50:12.680> them<00:50:12.890> and 00:50:13.720 --> 00:50:13.730 align:start position:0% other second you Center five of them and 00:50:13.730 --> 00:50:15.250 align:start position:0% other second you Center five of them and then<00:50:13.850> you<00:50:13.970> receive<00:50:14.270> another<00:50:14.510> five<00:50:14.990> and<00:50:15.170> then 00:50:15.250 --> 00:50:15.260 align:start position:0% then you receive another five and then 00:50:15.260 --> 00:50:22.810 align:start position:0% then you receive another five and then you<00:50:15.350> said<00:50:15.500> 15<00:50:15.920> so<00:50:16.670> like<00:50:17.030> oh<00:50:21.460> cool 00:50:22.810 --> 00:50:22.820 align:start position:0% you said 15 so like oh cool 00:50:22.820 --> 00:50:26.140 align:start position:0% you said 15 so like oh cool sorry<00:50:23.630> go<00:50:23.720> ahead<00:50:23.780> the<00:50:24.530> Everson<00:50:24.950> scheme<00:50:25.520> for<00:50:25.880> in 00:50:26.140 --> 00:50:26.150 align:start position:0% sorry go ahead the Everson scheme for in 00:50:26.150 --> 00:50:35.470 align:start position:0% sorry go ahead the Everson scheme for in the<00:50:26.240> notes<00:50:27.310> my<00:50:28.310> public<00:50:28.700> key<00:50:28.880> or<00:50:29.150> and<00:50:34.390> so<00:50:35.390> the 00:50:35.470 --> 00:50:35.480 align:start position:0% the notes my public key or and so the 00:50:35.480 --> 00:50:37.150 align:start position:0% the notes my public key or and so the client<00:50:35.900> the<00:50:36.080> client<00:50:36.110> binary<00:50:36.770> is<00:50:36.860> the<00:50:36.890> thing 00:50:37.150 --> 00:50:37.160 align:start position:0% client the client binary is the thing 00:50:37.160 --> 00:50:39.370 align:start position:0% client the client binary is the thing that<00:50:37.190> you'll<00:50:37.430> want<00:50:37.910> to<00:50:37.970> use<00:50:38.030> it's<00:50:39.020> written<00:50:39.260> and 00:50:39.370 --> 00:50:39.380 align:start position:0% that you'll want to use it's written and 00:50:39.380 --> 00:50:41.800 align:start position:0% that you'll want to use it's written and go<00:50:39.560> right<00:50:39.800> now<00:50:39.950> so<00:50:40.880> if<00:50:40.970> you're<00:50:41.120> a<00:50:41.150> go<00:50:41.330> user<00:50:41.570> you 00:50:41.800 --> 00:50:41.810 align:start position:0% go right now so if you're a go user you 00:50:41.810 --> 00:50:43.150 align:start position:0% go right now so if you're a go user you can<00:50:41.930> just<00:50:42.110> compile<00:50:42.410> the<00:50:42.530> client<00:50:42.800> right<00:50:42.950> into 00:50:43.150 --> 00:50:43.160 align:start position:0% can just compile the client right into 00:50:43.160 --> 00:50:45.250 align:start position:0% can just compile the client right into your<00:50:43.280> into<00:50:44.090> your<00:50:44.120> software<00:50:44.420> if<00:50:44.900> you're<00:50:45.110> not 00:50:45.250 --> 00:50:45.260 align:start position:0% your into your software if you're not 00:50:45.260 --> 00:50:47.520 align:start position:0% your into your software if you're not going<00:50:45.500> users<00:50:45.800> where<00:50:46.190> we're<00:50:46.430> gonna<00:50:46.520> provide 00:50:47.520 --> 00:50:47.530 align:start position:0% going users where we're gonna provide 00:50:47.530 --> 00:50:49.960 align:start position:0% going users where we're gonna provide socket<00:50:48.530> connections<00:50:49.010> so<00:50:49.340> let's<00:50:49.550> say<00:50:49.670> you<00:50:49.730> were 00:50:49.960 --> 00:50:49.970 align:start position:0% socket connections so let's say you were 00:50:49.970 --> 00:50:51.940 align:start position:0% socket connections so let's say you were a<00:50:50.300> JavaScript<00:50:51.290> air<00:50:51.410> just<00:50:51.560> for<00:50:51.620> instance 00:50:51.940 --> 00:50:51.950 align:start position:0% a JavaScript air just for instance 00:50:51.950 --> 00:50:54.130 align:start position:0% a JavaScript air just for instance there'll<00:50:52.760> be<00:50:52.790> a<00:50:52.880> WebSocket<00:50:53.390> connection<00:50:53.780> you 00:50:54.130 --> 00:50:54.140 align:start position:0% there'll be a WebSocket connection you 00:50:54.140 --> 00:50:56.200 align:start position:0% there'll be a WebSocket connection you basically<00:50:54.710> you're<00:50:54.860> a<00:50:54.890> patient<00:50:55.760> us<00:50:55.940> to<00:50:56.030> fire 00:50:56.200 --> 00:50:56.210 align:start position:0% basically you're a patient us to fire 00:50:56.210 --> 00:50:57.880 align:start position:0% basically you're a patient us to fire the<00:50:56.360> binary<00:50:56.600> up<00:50:56.780> that<00:50:57.230> will<00:50:57.380> take<00:50:57.560> care<00:50:57.710> of<00:50:57.770> all 00:50:57.880 --> 00:50:57.890 align:start position:0% the binary up that will take care of all 00:50:57.890 --> 00:51:00.880 align:start position:0% the binary up that will take care of all the<00:50:58.010> key<00:50:58.160> generation<00:50:58.700> all<00:50:59.180> of<00:50:59.480> the<00:50:59.690> loop<00:51:00.650> cover 00:51:00.880 --> 00:51:00.890 align:start position:0% the key generation all of the loop cover 00:51:00.890 --> 00:51:02.230 align:start position:0% the key generation all of the loop cover traffic<00:51:01.310> all<00:51:01.490> of<00:51:01.580> the<00:51:01.670> kind<00:51:01.850> of<00:51:01.880> Mason<00:51:02.150> any 00:51:02.230 --> 00:51:02.240 align:start position:0% traffic all of the kind of Mason any 00:51:02.240 --> 00:51:04.900 align:start position:0% traffic all of the kind of Mason any stuff<00:51:02.510> for<00:51:02.750> you<00:51:02.900> and<00:51:03.170> then<00:51:03.620> you're<00:51:04.610> you 00:51:04.900 --> 00:51:04.910 align:start position:0% stuff for you and then you're you 00:51:04.910 --> 00:51:06.730 align:start position:0% stuff for you and then you're you subscribe<00:51:05.450> to<00:51:05.660> events<00:51:05.720> on<00:51:06.050> that<00:51:06.230> WebSocket 00:51:06.730 --> 00:51:06.740 align:start position:0% subscribe to events on that WebSocket 00:51:06.740 --> 00:51:09.250 align:start position:0% subscribe to events on that WebSocket and<00:51:06.980> you<00:51:07.400> can<00:51:07.670> push<00:51:07.880> events<00:51:08.480> into<00:51:08.630> the<00:51:08.810> socket 00:51:09.250 --> 00:51:09.260 align:start position:0% and you can push events into the socket 00:51:09.260 --> 00:51:10.750 align:start position:0% and you can push events into the socket so<00:51:09.620> from<00:51:09.770> your<00:51:09.860> point<00:51:10.040> of<00:51:10.130> view<00:51:10.190> you're<00:51:10.490> making 00:51:10.750 --> 00:51:10.760 align:start position:0% so from your point of view you're making 00:51:10.760 --> 00:51:12.280 align:start position:0% so from your point of view you're making a<00:51:10.820> chat<00:51:11.000> application<00:51:11.210> with<00:51:11.630> a<00:51:11.690> WebSocket<00:51:12.020> or 00:51:12.280 --> 00:51:12.290 align:start position:0% a chat application with a WebSocket or 00:51:12.290 --> 00:51:14.140 align:start position:0% a chat application with a WebSocket or you<00:51:12.410> making<00:51:12.710> some<00:51:12.890> other<00:51:13.070> application<00:51:13.730> talk 00:51:14.140 --> 00:51:14.150 align:start position:0% you making some other application talk 00:51:14.150 --> 00:51:17.200 align:start position:0% you making some other application talk it<00:51:14.330> in<00:51:14.480> JavaScript<00:51:14.750> and<00:51:15.170> it<00:51:15.440> goes<00:51:15.910> into<00:51:16.910> the 00:51:17.200 --> 00:51:17.210 align:start position:0% it in JavaScript and it goes into the 00:51:17.210 --> 00:51:19.150 align:start position:0% it in JavaScript and it goes into the the<00:51:17.240> go<00:51:17.570> binary<00:51:17.930> the<00:51:18.170> go<00:51:18.260> binary<00:51:18.560> goes<00:51:18.770> hey 00:51:19.150 --> 00:51:19.160 align:start position:0% the go binary the go binary goes hey 00:51:19.160 --> 00:51:20.590 align:start position:0% the go binary the go binary goes hey cool<00:51:19.370> does<00:51:19.550> this<00:51:19.670> guy<00:51:19.820> have<00:51:19.850> any<00:51:20.060> like<00:51:20.390> real 00:51:20.590 --> 00:51:20.600 align:start position:0% cool does this guy have any like real 00:51:20.600 --> 00:51:22.330 align:start position:0% cool does this guy have any like real stuff<00:51:20.900> to<00:51:21.080> send<00:51:21.260> no<00:51:21.560> cool<00:51:21.860> send<00:51:22.130> a<00:51:22.190> cover 00:51:22.330 --> 00:51:22.340 align:start position:0% stuff to send no cool send a cover 00:51:22.340 --> 00:51:24.040 align:start position:0% stuff to send no cool send a cover message<00:51:22.670> good<00:51:22.910> or<00:51:23.240> if<00:51:23.480> you<00:51:23.540> have<00:51:23.660> real<00:51:23.840> stuff 00:51:24.040 --> 00:51:24.050 align:start position:0% message good or if you have real stuff 00:51:24.050 --> 00:51:27.370 align:start position:0% message good or if you have real stuff to<00:51:24.170> sin<00:51:24.430> yes<00:51:25.430> and<00:51:25.760> will<00:51:26.570> send<00:51:26.750> will<00:51:27.050> send<00:51:27.260> your 00:51:27.370 --> 00:51:27.380 align:start position:0% to sin yes and will send will send your 00:51:27.380 --> 00:51:29.020 align:start position:0% to sin yes and will send will send your real<00:51:27.500> stuff<00:51:27.740> it<00:51:28.160> will<00:51:28.400> take<00:51:28.580> care<00:51:28.760> of<00:51:28.820> all<00:51:28.970> of 00:51:29.020 --> 00:51:29.030 align:start position:0% real stuff it will take care of all of 00:51:29.030 --> 00:51:31.200 align:start position:0% real stuff it will take care of all of that<00:51:29.180> stuff<00:51:29.390> for<00:51:29.720> you<00:51:29.840> and<00:51:30.380> the<00:51:30.530> the<00:51:30.950> client 00:51:31.200 --> 00:51:31.210 align:start position:0% that stuff for you and the the client 00:51:31.210 --> 00:51:33.790 align:start position:0% that stuff for you and the the client also<00:51:32.210> takes<00:51:32.540> care<00:51:32.630> of<00:51:32.810> going<00:51:33.650> to<00:51:33.710> the 00:51:33.790 --> 00:51:33.800 align:start position:0% also takes care of going to the 00:51:33.800 --> 00:51:35.470 align:start position:0% also takes care of going to the directory<00:51:34.220> server<00:51:34.460> looking<00:51:35.000> up<00:51:35.120> where<00:51:35.300> all 00:51:35.470 --> 00:51:35.480 align:start position:0% directory server looking up where all 00:51:35.480 --> 00:51:36.940 align:start position:0% directory server looking up where all the<00:51:35.570> nodes<00:51:35.720> are<00:51:35.960> downloading<00:51:36.560> like<00:51:36.710> grabbing 00:51:36.940 --> 00:51:36.950 align:start position:0% the nodes are downloading like grabbing 00:51:36.950 --> 00:51:38.290 align:start position:0% the nodes are downloading like grabbing their<00:51:37.160> public<00:51:37.490> keys<00:51:37.670> getting<00:51:38.150> the<00:51:38.210> whole 00:51:38.290 --> 00:51:38.300 align:start position:0% their public keys getting the whole 00:51:38.300 --> 00:51:39.730 align:start position:0% their public keys getting the whole network<00:51:38.840> topology<00:51:39.320> everything<00:51:39.590> like<00:51:39.710> that 00:51:39.730 --> 00:51:39.740 align:start position:0% network topology everything like that 00:51:39.740 --> 00:51:42.760 align:start position:0% network topology everything like that and<00:51:40.070> then<00:51:41.000> the<00:51:41.300> client<00:51:41.930> will<00:51:42.080> automatically 00:51:42.760 --> 00:51:42.770 align:start position:0% and then the client will automatically 00:51:42.770 --> 00:51:46.240 align:start position:0% and then the client will automatically do<00:51:43.640> your<00:51:44.110> client-side<00:51:45.110> writing<00:51:45.470> for<00:51:45.650> you<00:51:45.800> so 00:51:46.240 --> 00:51:46.250 align:start position:0% do your client-side writing for you so 00:51:46.250 --> 00:51:47.650 align:start position:0% do your client-side writing for you so you<00:51:46.310> never<00:51:46.550> as<00:51:46.940> an<00:51:47.180> application<00:51:47.540> developer 00:51:47.650 --> 00:51:47.660 align:start position:0% you never as an application developer 00:51:47.660 --> 00:51:50.470 align:start position:0% you never as an application developer need<00:51:48.140> to<00:51:48.230> think<00:51:48.410> about<00:51:48.520> you<00:51:49.520> know<00:51:49.610> what<00:51:50.240> past 00:51:50.470 --> 00:51:50.480 align:start position:0% need to think about you know what past 00:51:50.480 --> 00:51:51.610 align:start position:0% need to think about you know what past am<00:51:50.630> I<00:51:50.720> going<00:51:50.840> to<00:51:50.930> choose<00:51:51.080> or<00:51:51.350> anything<00:51:51.470> like 00:51:51.610 --> 00:51:51.620 align:start position:0% am I going to choose or anything like 00:51:51.620 --> 00:51:54.420 align:start position:0% am I going to choose or anything like that<00:51:51.680> it's<00:51:51.980> all<00:51:52.040> done<00:51:52.250> for<00:51:52.430> you<00:51:52.490> so<00:51:52.850> if<00:51:53.720> I<00:51:53.840> had 00:51:54.420 --> 00:51:54.430 align:start position:0% that it's all done for you so if I had 00:51:54.430 --> 00:51:55.620 align:start position:0% that it's all done for you so if I had inside 00:51:55.620 --> 00:51:55.630 align:start position:0% inside 00:51:55.630 --> 00:51:58.890 align:start position:0% inside but<00:51:55.869> for<00:51:56.229> example<00:51:56.680> asserted<00:51:57.579> like<00:51:57.759> a<00:51:57.900> sentient 00:51:58.890 --> 00:51:58.900 align:start position:0% but for example asserted like a sentient 00:51:58.900 --> 00:52:02.849 align:start position:0% but for example asserted like a sentient file<00:51:59.369> could<00:52:00.369> I<00:52:00.519> read<00:52:01.119> prophase<00:52:01.539> curl<00:52:01.989> to<00:52:02.589> the 00:52:02.849 --> 00:52:02.859 align:start position:0% file could I read prophase curl to the 00:52:02.859 --> 00:52:05.309 align:start position:0% file could I read prophase curl to the register<00:52:03.309> file<00:52:03.519> by<00:52:03.880> going<00:52:04.150> through<00:52:04.539> its<00:52:04.690> proxy 00:52:05.309 --> 00:52:05.319 align:start position:0% register file by going through its proxy 00:52:05.319 --> 00:52:08.460 align:start position:0% register file by going through its proxy locally<00:52:06.150> you<00:52:07.150> would<00:52:07.329> need<00:52:07.509> to<00:52:07.720> packetize<00:52:08.259> it 00:52:08.460 --> 00:52:08.470 align:start position:0% locally you would need to packetize it 00:52:08.470 --> 00:52:09.630 align:start position:0% locally you would need to packetize it that<00:52:08.680> would<00:52:08.829> be<00:52:08.950> the<00:52:09.069> one<00:52:09.190> thing<00:52:09.430> that<00:52:09.549> you 00:52:09.630 --> 00:52:09.640 align:start position:0% that would be the one thing that you 00:52:09.640 --> 00:52:11.729 align:start position:0% that would be the one thing that you need<00:52:09.819> to<00:52:09.880> do<00:52:10.059> in<00:52:10.180> that<00:52:10.509> case<00:52:10.569> of<00:52:10.960> you<00:52:11.140> you<00:52:11.589> need 00:52:11.729 --> 00:52:11.739 align:start position:0% need to do in that case of you you need 00:52:11.739 --> 00:52:14.370 align:start position:0% need to do in that case of you you need to<00:52:11.829> chop<00:52:12.039> up<00:52:12.249> that<00:52:12.279> file<00:52:12.999> into<00:52:13.720> chunks<00:52:14.200> that 00:52:14.370 --> 00:52:14.380 align:start position:0% to chop up that file into chunks that 00:52:14.380 --> 00:52:16.109 align:start position:0% to chop up that file into chunks that match<00:52:14.680> the<00:52:14.920> size<00:52:15.130> of<00:52:15.309> the<00:52:15.430> of<00:52:15.670> the<00:52:15.789> mix<00:52:15.970> net 00:52:16.109 --> 00:52:16.119 align:start position:0% match the size of the of the mix net 00:52:16.119 --> 00:52:19.410 align:start position:0% match the size of the of the mix net packets<00:52:16.769> and<00:52:17.769> at<00:52:17.979> the<00:52:18.069> other<00:52:18.190> end<00:52:18.309> of<00:52:18.670> your 00:52:19.410 --> 00:52:19.420 align:start position:0% packets and at the other end of your 00:52:19.420 --> 00:52:20.759 align:start position:0% packets and at the other end of your application<00:52:19.900> you<00:52:19.930> would<00:52:20.170> need<00:52:20.319> to<00:52:20.470> provide 00:52:20.759 --> 00:52:20.769 align:start position:0% application you would need to provide 00:52:20.769 --> 00:52:22.890 align:start position:0% application you would need to provide some<00:52:21.460> way<00:52:21.640> of<00:52:21.759> turning<00:52:21.940> those<00:52:22.210> packets<00:52:22.630> into 00:52:22.890 --> 00:52:22.900 align:start position:0% some way of turning those packets into 00:52:22.900 --> 00:52:24.420 align:start position:0% some way of turning those packets into something<00:52:23.229> that<00:52:23.349> maybe<00:52:23.529> gets<00:52:23.829> reordered<00:52:24.309> if 00:52:24.420 --> 00:52:24.430 align:start position:0% something that maybe gets reordered if 00:52:24.430 --> 00:52:26.009 align:start position:0% something that maybe gets reordered if you<00:52:24.549> need<00:52:24.700> ordering<00:52:25.089> in<00:52:25.210> your<00:52:25.329> application<00:52:25.839> so 00:52:26.009 --> 00:52:26.019 align:start position:0% you need ordering in your application so 00:52:26.019 --> 00:52:31.799 align:start position:0% you need ordering in your application so that's<00:52:26.140> the<00:52:29.369> yeah<00:52:30.369> kind<00:52:30.789> of<00:52:30.880> it's<00:52:30.999> uh<00:52:31.210> it's 00:52:31.799 --> 00:52:31.809 align:start position:0% that's the yeah kind of it's uh it's 00:52:31.809 --> 00:52:35.069 align:start position:0% that's the yeah kind of it's uh it's like<00:52:31.989> super<00:52:32.739> anonymous<00:52:33.130> UDP<00:52:33.549> I<00:52:33.579> guess<00:52:33.910> we<00:52:34.900> were 00:52:35.069 --> 00:52:35.079 align:start position:0% like super anonymous UDP I guess we were 00:52:35.079 --> 00:52:37.529 align:start position:0% like super anonymous UDP I guess we were just<00:52:35.109> reinvented<00:52:35.739> this<00:52:36.700> one<00:52:37.029> more<00:52:37.269> thing<00:52:37.299> that 00:52:37.529 --> 00:52:37.539 align:start position:0% just reinvented this one more thing that 00:52:37.539 --> 00:52:39.509 align:start position:0% just reinvented this one more thing that we've<00:52:37.809> got<00:52:38.019> here<00:52:38.229> which<00:52:38.410> is<00:52:38.529> a<00:52:38.559> quick<00:52:39.130> demo<00:52:39.400> of 00:52:39.509 --> 00:52:39.519 align:start position:0% we've got here which is a quick demo of 00:52:39.519 --> 00:52:42.210 align:start position:0% we've got here which is a quick demo of the<00:52:39.970> credentials<00:52:40.630> I'm<00:52:41.200> just<00:52:41.349> going<00:52:41.499> to<00:52:41.529> jump 00:52:42.210 --> 00:52:42.220 align:start position:0% the credentials I'm just going to jump 00:52:42.220 --> 00:52:46.140 align:start position:0% the credentials I'm just going to jump forward<00:52:42.519> a<00:52:42.819> tiny<00:52:43.089> bit<00:52:44.670> just<00:52:45.670> to<00:52:45.789> see<00:52:45.970> you<00:52:46.029> can 00:52:46.140 --> 00:52:46.150 align:start position:0% forward a tiny bit just to see you can 00:52:46.150 --> 00:52:47.700 align:start position:0% forward a tiny bit just to see you can see<00:52:46.299> it<00:52:46.390> running<00:52:46.749> code<00:52:47.019> we're<00:52:47.170> just<00:52:47.319> about<00:52:47.470> to 00:52:47.700 --> 00:52:47.710 align:start position:0% see it running code we're just about to 00:52:47.710 --> 00:52:49.349 align:start position:0% see it running code we're just about to this<00:52:47.950> was<00:52:48.069> loading<00:52:48.400> up<00:52:48.489> some<00:52:48.700> configuration 00:52:49.349 --> 00:52:49.359 align:start position:0% this was loading up some configuration 00:52:49.359 --> 00:52:51.960 align:start position:0% this was loading up some configuration files<00:52:49.599> but<00:52:50.289> basically<00:52:50.650> what<00:52:50.859> we<00:52:50.979> have<00:52:51.099> here<00:52:51.130> is 00:52:51.960 --> 00:52:51.970 align:start position:0% files but basically what we have here is 00:52:51.970 --> 00:52:55.170 align:start position:0% files but basically what we have here is a<00:52:52.410> wonderfully<00:52:53.410> designed<00:52:53.769> QT<00:52:54.400> thing<00:52:54.700> which 00:52:55.170 --> 00:52:55.180 align:start position:0% a wonderfully designed QT thing which 00:52:55.180 --> 00:52:58.739 align:start position:0% a wonderfully designed QT thing which basically<00:52:55.479> will<00:52:55.720> take<00:52:56.640> some<00:52:57.640> GRC<00:52:58.150> 20<00:52:58.479> NIM 00:52:58.739 --> 00:52:58.749 align:start position:0% basically will take some GRC 20 NIM 00:52:58.749 --> 00:53:00.660 align:start position:0% basically will take some GRC 20 NIM tokens<00:52:59.200> and<00:52:59.559> just<00:53:00.190> that's<00:53:00.339> a<00:53:00.430> kind<00:53:00.640> of 00:53:00.660 --> 00:53:00.670 align:start position:0% tokens and just that's a kind of 00:53:00.670 --> 00:53:02.459 align:start position:0% tokens and just that's a kind of demonstration<00:53:00.969> it's<00:53:01.479> not<00:53:01.599> pretty<00:53:01.809> real 00:53:02.459 --> 00:53:02.469 align:start position:0% demonstration it's not pretty real 00:53:02.469 --> 00:53:03.839 align:start position:0% demonstration it's not pretty real reason<00:53:02.739> what<00:53:03.130> I'm<00:53:03.249> trying<00:53:03.489> to<00:53:03.519> do<00:53:03.700> is 00:53:03.839 --> 00:53:03.849 align:start position:0% reason what I'm trying to do is 00:53:03.849 --> 00:53:05.880 align:start position:0% reason what I'm trying to do is demonstrate<00:53:04.119> the<00:53:04.960> kind<00:53:05.170> of<00:53:05.229> flow<00:53:05.499> so 00:53:05.880 --> 00:53:05.890 align:start position:0% demonstrate the kind of flow so 00:53:05.890 --> 00:53:07.680 align:start position:0% demonstrate the kind of flow so basically<00:53:06.249> what's<00:53:06.489> gonna<00:53:06.579> happen<00:53:06.700> is<00:53:07.119> the 00:53:07.680 --> 00:53:07.690 align:start position:0% basically what's gonna happen is the 00:53:07.690 --> 00:53:10.410 align:start position:0% basically what's gonna happen is the client<00:53:08.170> that's<00:53:09.130> this<00:53:09.369> white<00:53:09.849> thing<00:53:09.880> you<00:53:10.239> see 00:53:10.410 --> 00:53:10.420 align:start position:0% client that's this white thing you see 00:53:10.420 --> 00:53:15.329 align:start position:0% client that's this white thing you see on<00:53:10.539> the<00:53:10.630> screen<00:53:10.719> will<00:53:11.469> ask<00:53:12.160> for<00:53:13.619> hey<00:53:14.619> here's 00:53:15.329 --> 00:53:15.339 align:start position:0% on the screen will ask for hey here's 00:53:15.339 --> 00:53:17.849 align:start position:0% on the screen will ask for hey here's aetherium<00:53:15.849> we're<00:53:16.509> gonna<00:53:16.599> ask<00:53:17.259> for<00:53:17.559> aetherium 00:53:17.849 --> 00:53:17.859 align:start position:0% aetherium we're gonna ask for aetherium 00:53:17.859 --> 00:53:20.400 align:start position:0% aetherium we're gonna ask for aetherium to<00:53:18.130> basically<00:53:18.430> pump<00:53:18.789> some<00:53:19.089> aetherium<00:53:20.079> tokens 00:53:20.400 --> 00:53:20.410 align:start position:0% to basically pump some aetherium tokens 00:53:20.410 --> 00:53:23.729 align:start position:0% to basically pump some aetherium tokens into<00:53:20.650> newm<00:53:20.979> into<00:53:21.910> this<00:53:22.450> tetraman<00:53:23.440> around 00:53:23.729 --> 00:53:23.739 align:start position:0% into newm into this tetraman around 00:53:23.739 --> 00:53:25.229 align:start position:0% into newm into this tetraman around which<00:53:24.009> is<00:53:24.160> what<00:53:24.309> we're<00:53:24.430> actually<00:53:24.549> using<00:53:24.849> for 00:53:25.229 --> 00:53:25.239 align:start position:0% which is what we're actually using for 00:53:25.239 --> 00:53:28.499 align:start position:0% which is what we're actually using for that<00:53:25.680> for<00:53:26.680> the<00:53:26.739> validators<00:53:27.190> that<00:53:28.059> will<00:53:28.269> create 00:53:28.499 --> 00:53:28.509 align:start position:0% that for the validators that will create 00:53:28.509 --> 00:53:30.599 align:start position:0% that for the validators that will create some<00:53:28.809> names<00:53:29.049> on<00:53:29.380> in<00:53:29.680> the<00:53:29.859> in<00:53:30.099> the<00:53:30.190> tenorman 00:53:30.599 --> 00:53:30.609 align:start position:0% some names on in the in the tenorman 00:53:30.609 --> 00:53:33.029 align:start position:0% some names on in the in the tenorman side<00:53:30.849> of<00:53:31.029> things<00:53:31.539> you'll<00:53:32.170> then<00:53:32.440> get<00:53:32.829> back<00:53:32.979> a 00:53:33.029 --> 00:53:33.039 align:start position:0% side of things you'll then get back a 00:53:33.039 --> 00:53:36.239 align:start position:0% side of things you'll then get back a credential<00:53:33.700> from<00:53:34.599> the<00:53:34.719> validators<00:53:35.289> so<00:53:36.069> all 00:53:36.239 --> 00:53:36.249 align:start position:0% credential from the validators so all 00:53:36.249 --> 00:53:38.670 align:start position:0% credential from the validators so all these<00:53:36.430> guys<00:53:36.670> will<00:53:36.910> respond<00:53:37.299> to<00:53:37.390> you<00:53:37.569> and<00:53:38.049> say 00:53:38.670 --> 00:53:38.680 align:start position:0% these guys will respond to you and say 00:53:38.680 --> 00:53:41.880 align:start position:0% these guys will respond to you and say cool<00:53:39.670> yeah<00:53:39.940> here's<00:53:40.569> your<00:53:40.630> here's<00:53:40.869> here's<00:53:41.319> each 00:53:41.880 --> 00:53:41.890 align:start position:0% cool yeah here's your here's here's each 00:53:41.890 --> 00:53:43.650 align:start position:0% cool yeah here's your here's here's each piece<00:53:42.309> of<00:53:42.519> your<00:53:42.700> credential<00:53:43.210> because<00:53:43.420> you<00:53:43.509> get 00:53:43.650 --> 00:53:43.660 align:start position:0% piece of your credential because you get 00:53:43.660 --> 00:53:45.989 align:start position:0% piece of your credential because you get a<00:53:43.690> you<00:53:44.259> know<00:53:44.349> a<00:53:44.410> threshold<00:53:44.739> credential<00:53:45.400> we<00:53:45.849> can 00:53:45.989 --> 00:53:45.999 align:start position:0% a you know a threshold credential we can 00:53:45.999 --> 00:53:48.180 align:start position:0% a you know a threshold credential we can then<00:53:46.150> re<00:53:46.299> randomize<00:53:46.839> their<00:53:47.079> credential<00:53:47.529> and<00:53:47.829> I 00:53:48.180 --> 00:53:48.190 align:start position:0% then re randomize their credential and I 00:53:48.190 --> 00:53:50.549 align:start position:0% then re randomize their credential and I will<00:53:48.489> show<00:53:48.640> that<00:53:48.670> working<00:53:49.180> and<00:53:49.509> then<00:53:50.289> you<00:53:50.319> can 00:53:50.549 --> 00:53:50.559 align:start position:0% will show that working and then you can 00:53:50.559 --> 00:53:53.009 align:start position:0% will show that working and then you can spend<00:53:50.890> the<00:53:51.009> credential<00:53:51.630> with<00:53:52.630> a<00:53:52.660> service 00:53:53.009 --> 00:53:53.019 align:start position:0% spend the credential with a service 00:53:53.019 --> 00:53:54.690 align:start position:0% spend the credential with a service provider<00:53:53.109> and<00:53:53.799> the<00:53:53.890> service<00:53:54.190> provider<00:53:54.519> can 00:53:54.690 --> 00:53:54.700 align:start position:0% provider and the service provider can 00:53:54.700 --> 00:53:57.329 align:start position:0% provider and the service provider can then<00:53:54.880> redeem<00:53:55.150> it<00:53:55.359> over<00:53:56.289> here<00:53:56.559> and<00:53:56.829> say<00:53:57.130> cool 00:53:57.329 --> 00:53:57.339 align:start position:0% then redeem it over here and say cool 00:53:57.339 --> 00:53:59.940 align:start position:0% then redeem it over here and say cool pay<00:53:57.910> me<00:53:58.119> and<00:53:58.359> we<00:53:58.960> can<00:53:59.109> have<00:53:59.170> double<00:53:59.680> spend 00:53:59.940 --> 00:53:59.950 align:start position:0% pay me and we can have double spend 00:53:59.950 --> 00:54:02.130 align:start position:0% pay me and we can have double spend reduction<00:54:00.339> there<00:54:00.460> as<00:54:00.550> well<00:54:00.700> so<00:54:01.119> that's<00:54:01.240> that's 00:54:02.130 --> 00:54:02.140 align:start position:0% reduction there as well so that's that's 00:54:02.140 --> 00:54:03.599 align:start position:0% reduction there as well so that's that's the<00:54:02.290> basic<00:54:02.589> flow<00:54:02.829> of<00:54:03.130> the<00:54:03.250> cocoanut 00:54:03.599 --> 00:54:03.609 align:start position:0% the basic flow of the cocoanut 00:54:03.609 --> 00:54:08.220 align:start position:0% the basic flow of the cocoanut credentials<00:54:04.000> so<00:54:04.450> cool<00:54:05.260> we<00:54:05.800> just<00:54:05.980> got<00:54:06.960> ten<00:54:07.960> nibs 00:54:08.220 --> 00:54:08.230 align:start position:0% credentials so cool we just got ten nibs 00:54:08.230 --> 00:54:12.329 align:start position:0% credentials so cool we just got ten nibs in<00:54:10.320> we're<00:54:11.320> gonna<00:54:11.410> create<00:54:11.710> a<00:54:11.770> credential<00:54:12.250> that 00:54:12.329 --> 00:54:12.339 align:start position:0% in we're gonna create a credential that 00:54:12.339 --> 00:54:14.400 align:start position:0% in we're gonna create a credential that code<00:54:12.640> supplied<00:54:13.000> names<00:54:13.329> in<00:54:13.480> this<00:54:13.570> case<00:54:13.780> don't 00:54:14.400 --> 00:54:14.410 align:start position:0% code supplied names in this case don't 00:54:14.410 --> 00:54:15.990 align:start position:0% code supplied names in this case don't get<00:54:14.650> sucked<00:54:14.859> in<00:54:15.040> by<00:54:15.070> thinking<00:54:15.550> you<00:54:15.700> always 00:54:15.990 --> 00:54:16.000 align:start position:0% get sucked in by thinking you always 00:54:16.000 --> 00:54:17.520 align:start position:0% get sucked in by thinking you always have<00:54:16.180> to<00:54:16.300> quit<00:54:16.480> currency<00:54:17.050> inside<00:54:17.349> your 00:54:17.520 --> 00:54:17.530 align:start position:0% have to quit currency inside your 00:54:17.530 --> 00:54:19.890 align:start position:0% have to quit currency inside your credentials<00:54:18.010> this<00:54:18.490> is<00:54:18.670> a<00:54:18.910> very<00:54:19.570> general 00:54:19.890 --> 00:54:19.900 align:start position:0% credentials this is a very general 00:54:19.900 --> 00:54:23.730 align:start position:0% credentials this is a very general purpose<00:54:20.079> system<00:54:20.589> so<00:54:21.690> the<00:54:22.690> name<00:54:22.839> credential<00:54:23.380> is 00:54:23.730 --> 00:54:23.740 align:start position:0% purpose system so the name credential is 00:54:23.740 --> 00:54:26.250 align:start position:0% purpose system so the name credential is the<00:54:23.920> same<00:54:24.130> thing<00:54:24.400> as<00:54:24.579> like<00:54:25.020> like<00:54:26.020> this 00:54:26.250 --> 00:54:26.260 align:start position:0% the same thing as like like this 00:54:26.260 --> 00:54:29.000 align:start position:0% the same thing as like like this application<00:54:26.920> is<00:54:27.040> like<00:54:27.160> a<00:54:27.190> smart<00:54:27.460> contract<00:54:27.910> as 00:54:29.000 --> 00:54:29.010 align:start position:0% application is like a smart contract as 00:54:29.010 --> 00:54:31.530 align:start position:0% application is like a smart contract as it's<00:54:30.010> what's<00:54:30.250> a<00:54:30.400> smart<00:54:30.730> contract<00:54:31.180> is<00:54:31.329> to<00:54:31.450> the 00:54:31.530 --> 00:54:31.540 align:start position:0% it's what's a smart contract is to the 00:54:31.540 --> 00:54:34.650 align:start position:0% it's what's a smart contract is to the EVM<00:54:31.930> the<00:54:32.589> the<00:54:33.099> basic<00:54:33.970> thing<00:54:34.119> underneath<00:54:34.480> all 00:54:34.650 --> 00:54:34.660 align:start position:0% EVM the the basic thing underneath all 00:54:34.660 --> 00:54:37.140 align:start position:0% EVM the the basic thing underneath all of<00:54:34.690> this<00:54:34.839> is<00:54:35.109> very<00:54:35.440> general<00:54:36.430> purpose<00:54:36.579> cool 00:54:37.140 --> 00:54:37.150 align:start position:0% of this is very general purpose cool 00:54:37.150 --> 00:54:39.270 align:start position:0% of this is very general purpose cool we've<00:54:37.630> got<00:54:37.810> back<00:54:37.960> a<00:54:37.990> partial<00:54:38.680> credential<00:54:39.070> our 00:54:39.270 --> 00:54:39.280 align:start position:0% we've got back a partial credential our 00:54:39.280 --> 00:54:41.220 align:start position:0% we've got back a partial credential our client<00:54:39.609> has<00:54:39.730> reassembled<00:54:39.940> it<00:54:40.329> over<00:54:40.630> here<00:54:40.810> and 00:54:41.220 --> 00:54:41.230 align:start position:0% client has reassembled it over here and 00:54:41.230 --> 00:54:43.770 align:start position:0% client has reassembled it over here and I'm<00:54:41.650> pressing<00:54:41.890> the<00:54:42.070> re<00:54:42.250> randomize<00:54:42.700> button<00:54:42.780> and 00:54:43.770 --> 00:54:43.780 align:start position:0% I'm pressing the re randomize button and 00:54:43.780 --> 00:54:45.180 align:start position:0% I'm pressing the re randomize button and you<00:54:43.900> can<00:54:44.020> see<00:54:44.200> the<00:54:44.320> credential<00:54:44.740> changing 00:54:45.180 --> 00:54:45.190 align:start position:0% you can see the credential changing 00:54:45.190 --> 00:54:48.720 align:start position:0% you can see the credential changing right<00:54:45.310> there<00:54:45.660> as<00:54:46.660> I'm<00:54:47.260> pressing<00:54:47.470> it<00:54:47.770> so<00:54:48.670> I<00:54:48.700> just 00:54:48.720 --> 00:54:48.730 align:start position:0% right there as I'm pressing it so I just 00:54:48.730 --> 00:54:51.270 align:start position:0% right there as I'm pressing it so I just free<00:54:49.060> randomize<00:54:49.480> at<00:54:49.630> five<00:54:49.810> times<00:54:50.079> it<00:54:50.770> has<00:54:51.040> now 00:54:51.270 --> 00:54:51.280 align:start position:0% free randomize at five times it has now 00:54:51.280 --> 00:54:52.859 align:start position:0% free randomize at five times it has now the<00:54:51.400> same<00:54:51.700> five<00:54:52.030> names<00:54:52.300> inside<00:54:52.720> the 00:54:52.859 --> 00:54:52.869 align:start position:0% the same five names inside the 00:54:52.869 --> 00:54:55.050 align:start position:0% the same five names inside the credential<00:54:53.290> that<00:54:53.380> it<00:54:53.530> always<00:54:53.680> had<00:54:53.980> but<00:54:54.609> it<00:54:54.730> is 00:54:55.050 --> 00:54:55.060 align:start position:0% credential that it always had but it is 00:54:55.060 --> 00:54:57.030 align:start position:0% credential that it always had but it is a<00:54:55.089> totally<00:54:55.510> different<00:54:55.540> credential<00:54:56.349> than<00:54:56.800> what 00:54:57.030 --> 00:54:57.040 align:start position:0% a totally different credential than what 00:54:57.040 --> 00:54:58.380 align:start position:0% a totally different credential than what we<00:54:57.130> got<00:54:57.280> back<00:54:57.460> from<00:54:57.730> these<00:54:57.820> issuing 00:54:58.380 --> 00:54:58.390 align:start position:0% we got back from these issuing 00:54:58.390 --> 00:55:00.030 align:start position:0% we got back from these issuing authorities<00:54:58.780> so<00:54:59.200> they<00:54:59.230> can't<00:54:59.530> run<00:54:59.710> on<00:54:59.770> me 00:55:00.030 --> 00:55:00.040 align:start position:0% authorities so they can't run on me 00:55:00.040 --> 00:55:02.430 align:start position:0% authorities so they can't run on me anymore<00:55:00.520> they<00:55:01.000> can't<00:55:01.210> tell<00:55:01.450> who<00:55:01.660> who<00:55:01.990> who<00:55:02.320> they 00:55:02.430 --> 00:55:02.440 align:start position:0% anymore they can't tell who who who they 00:55:02.440 --> 00:55:05.160 align:start position:0% anymore they can't tell who who who they gave<00:55:02.619> it<00:55:02.740> to<00:55:02.770> even<00:55:03.430> if<00:55:03.520> they<00:55:03.640> colluded<00:55:04.170> unable 00:55:05.160 --> 00:55:05.170 align:start position:0% gave it to even if they colluded unable 00:55:05.170 --> 00:55:09.420 align:start position:0% gave it to even if they colluded unable to<00:55:05.290> do<00:55:05.470> that<00:55:05.619> so<00:55:07.859> we<00:55:08.859> then<00:55:09.040> send<00:55:09.310> the 00:55:09.420 --> 00:55:09.430 align:start position:0% to do that so we then send the 00:55:09.430 --> 00:55:12.120 align:start position:0% to do that so we then send the credential<00:55:10.140> former<00:55:11.140> client<00:55:11.530> to<00:55:11.680> some<00:55:11.859> kind<00:55:12.069> of 00:55:12.120 --> 00:55:12.130 align:start position:0% credential former client to some kind of 00:55:12.130 --> 00:55:13.890 align:start position:0% credential former client to some kind of service<00:55:12.339> provider<00:55:12.790> to<00:55:13.270> pay<00:55:13.450> for<00:55:13.720> something 00:55:13.890 --> 00:55:13.900 align:start position:0% service provider to pay for something 00:55:13.900 --> 00:55:18.839 align:start position:0% service provider to pay for something could<00:55:14.770> be<00:55:14.890> for<00:55:15.069> anything<00:55:15.220> um<00:55:17.640> that's<00:55:18.640> great 00:55:18.839 --> 00:55:18.849 align:start position:0% could be for anything um that's great 00:55:18.849 --> 00:55:20.190 align:start position:0% could be for anything um that's great the<00:55:19.000> service<00:55:19.150> part<00:55:19.510> of<00:55:19.599> redeemed<00:55:19.869> it<00:55:20.020> that 00:55:20.190 --> 00:55:20.200 align:start position:0% the service part of redeemed it that 00:55:20.200 --> 00:55:22.140 align:start position:0% the service part of redeemed it that means<00:55:20.349> it's<00:55:20.530> been<00:55:20.619> spent<00:55:20.950> I<00:55:21.220> then<00:55:21.880> tried<00:55:22.119> to 00:55:22.140 --> 00:55:22.150 align:start position:0% means it's been spent I then tried to 00:55:22.150 --> 00:55:25.950 align:start position:0% means it's been spent I then tried to spend<00:55:23.079> it<00:55:23.170> again<00:55:23.579> and<00:55:24.579> it<00:55:25.480> said<00:55:25.630> no<00:55:25.750> you've 00:55:25.950 --> 00:55:25.960 align:start position:0% spend it again and it said no you've 00:55:25.960 --> 00:55:27.630 align:start position:0% spend it again and it said no you've already<00:55:26.079> spent<00:55:26.380> it<00:55:26.500> the<00:55:27.280> really<00:55:27.430> interesting 00:55:27.630 --> 00:55:27.640 align:start position:0% already spent it the really interesting 00:55:27.640 --> 00:55:30.059 align:start position:0% already spent it the really interesting thing<00:55:28.089> I'm<00:55:28.930> gonna<00:55:29.140> reran<00:55:29.470> demise<00:55:29.710> it<00:55:29.890> another 00:55:30.059 --> 00:55:30.069 align:start position:0% thing I'm gonna reran demise it another 00:55:30.069 --> 00:55:32.460 align:start position:0% thing I'm gonna reran demise it another five<00:55:30.310> times<00:55:30.579> here<00:55:31.050> so<00:55:32.050> you<00:55:32.109> can<00:55:32.230> see<00:55:32.380> the 00:55:32.460 --> 00:55:32.470 align:start position:0% five times here so you can see the 00:55:32.470 --> 00:55:34.109 align:start position:0% five times here so you can see the credential<00:55:32.890> changing<00:55:33.280> again<00:55:33.490> so<00:55:33.880> sorry 00:55:34.109 --> 00:55:34.119 align:start position:0% credential changing again so sorry 00:55:34.119 --> 00:55:35.819 align:start position:0% credential changing again so sorry that's<00:55:34.300> a<00:55:34.359> bit<00:55:34.540> thank<00:55:35.500> you 00:55:35.819 --> 00:55:35.829 align:start position:0% that's a bit thank you 00:55:35.829 --> 00:55:38.640 align:start position:0% that's a bit thank you I<00:55:35.859> try<00:55:36.550> to<00:55:36.609> spend<00:55:36.880> it<00:55:37.030> now<00:55:37.210> and<00:55:37.599> despite<00:55:38.470> the 00:55:38.640 --> 00:55:38.650 align:start position:0% I try to spend it now and despite the 00:55:38.650 --> 00:55:40.579 align:start position:0% I try to spend it now and despite the fact<00:55:38.680> that<00:55:38.980> it's<00:55:39.220> a<00:55:39.310> brand<00:55:39.700> new<00:55:39.760> credential 00:55:40.579 --> 00:55:40.589 align:start position:0% fact that it's a brand new credential 00:55:40.589 --> 00:55:43.910 align:start position:0% fact that it's a brand new credential the<00:55:41.589> blockchain<00:55:42.010> has<00:55:42.369> rejected<00:55:42.730> it<00:55:43.030> as<00:55:43.210> being 00:55:43.910 --> 00:55:43.920 align:start position:0% the blockchain has rejected it as being 00:55:43.920 --> 00:55:45.809 align:start position:0% the blockchain has rejected it as being already<00:55:44.920> spent<00:55:45.250> so<00:55:45.460> the<00:55:45.550> cryptographic 00:55:45.809 --> 00:55:45.819 align:start position:0% already spent so the cryptographic 00:55:45.819 --> 00:55:49.140 align:start position:0% already spent so the cryptographic material<00:55:46.450> in<00:55:46.540> there<00:55:46.690> has<00:55:47.260> been<00:55:48.150> recognized 00:55:49.140 --> 00:55:49.150 align:start position:0% material in there has been recognized 00:55:49.150 --> 00:55:51.150 align:start position:0% material in there has been recognized even<00:55:49.599> if<00:55:49.690> it's<00:55:49.810> a<00:55:49.869> different<00:55:50.109> credential<00:55:50.770> so 00:55:51.150 --> 00:55:51.160 align:start position:0% even if it's a different credential so 00:55:51.160 --> 00:55:52.589 align:start position:0% even if it's a different credential so we<00:55:51.280> still<00:55:51.460> have<00:55:51.609> double<00:55:51.880> spending<00:55:52.119> protection 00:55:52.589 --> 00:55:52.599 align:start position:0% we still have double spending protection 00:55:52.599 --> 00:55:56.670 align:start position:0% we still have double spending protection even<00:55:53.349> with<00:55:53.500> the<00:55:53.589> randomization<00:55:55.050> cool<00:55:56.050> that's 00:55:56.670 --> 00:55:56.680 align:start position:0% even with the randomization cool that's 00:55:56.680 --> 00:56:01.090 align:start position:0% even with the randomization cool that's pretty<00:55:56.770> much<00:55:57.069> it<00:55:57.250> so<00:55:57.750> any<00:55:58.750> other<00:55:58.900> questions 00:56:01.090 --> 00:56:01.100 align:start position:0% 00:56:01.100 --> 00:56:05.050 align:start position:0% how<00:56:01.550> was<00:56:01.730> your<00:56:01.880> work<00:56:02.060> thunder<00:56:03.610> we<00:56:04.610> have<00:56:04.880> some 00:56:05.050 --> 00:56:05.060 align:start position:0% how was your work thunder we have some 00:56:05.060 --> 00:56:16.660 align:start position:0% how was your work thunder we have some investment<00:56:05.480> from<00:56:05.720> different<00:56:15.160> sure<00:56:16.160> it 00:56:16.660 --> 00:56:16.670 align:start position:0% investment from different sure it 00:56:16.670 --> 00:56:18.190 align:start position:0% investment from different sure it doesn't<00:56:17.030> right<00:56:17.180> now<00:56:17.330> but<00:56:17.600> eventually<00:56:17.960> the 00:56:18.190 --> 00:56:18.200 align:start position:0% doesn't right now but eventually the 00:56:18.200 --> 00:56:19.330 align:start position:0% doesn't right now but eventually the vision<00:56:18.410> is<00:56:18.500> that<00:56:18.620> it<00:56:18.710> will<00:56:18.830> eyes<00:56:18.980> having<00:56:19.220> that 00:56:19.330 --> 00:56:19.340 align:start position:0% vision is that it will eyes having that 00:56:19.340 --> 00:56:20.710 align:start position:0% vision is that it will eyes having that time<00:56:19.490> to<00:56:19.610> plumb<00:56:19.820> it<00:56:19.910> all<00:56:20.000> together<00:56:20.180> quite<00:56:20.570> yet 00:56:20.710 --> 00:56:20.720 align:start position:0% time to plumb it all together quite yet 00:56:20.720 --> 00:56:29.380 align:start position:0% time to plumb it all together quite yet but<00:56:20.900> yeah<00:56:24.370> I'm<00:56:25.370> not<00:56:25.820> sure<00:56:25.850> I<00:56:26.420> don't<00:56:26.780> know<00:56:28.390> which 00:56:29.380 --> 00:56:29.390 align:start position:0% but yeah I'm not sure I don't know which 00:56:29.390 --> 00:56:31.600 align:start position:0% but yeah I'm not sure I don't know which be<00:56:29.570> our<00:56:29.690> instruction<00:56:30.290> I<00:56:30.380> think<00:56:30.530> I<00:56:30.590> heard<00:56:30.740> yeah 00:56:31.600 --> 00:56:31.610 align:start position:0% be our instruction I think I heard yeah 00:56:31.610 --> 00:56:37.330 align:start position:0% be our instruction I think I heard yeah yeah<00:56:32.180> and<00:56:32.390> on<00:56:32.570> the<00:56:32.720> I<00:56:33.040> yeah<00:56:34.040> I<00:56:34.070> can<00:56:35.500> the<00:56:36.500> person 00:56:37.330 --> 00:56:37.340 align:start position:0% yeah and on the I yeah I can the person 00:56:37.340 --> 00:56:39.250 align:start position:0% yeah and on the I yeah I can the person who<00:56:37.520> invented<00:56:37.700> the<00:56:38.000> two<00:56:38.480> people<00:56:38.780> invented<00:56:39.200> the 00:56:39.250 --> 00:56:39.260 align:start position:0% who invented the two people invented the 00:56:39.260 --> 00:56:40.720 align:start position:0% who invented the two people invented the scheme<00:56:39.470> Martin<00:56:39.770> Gritty<00:56:39.920> here<00:56:39.980> NS<00:56:40.370> I'm<00:56:40.550> not 00:56:40.720 --> 00:56:40.730 align:start position:0% scheme Martin Gritty here NS I'm not 00:56:40.730 --> 00:56:41.710 align:start position:0% scheme Martin Gritty here NS I'm not sure<00:56:40.880> where<00:56:41.060> they're<00:56:41.150> planning<00:56:41.480> to<00:56:41.570> use<00:56:41.690> that 00:56:41.710 --> 00:56:41.720 align:start position:0% sure where they're planning to use that 00:56:41.720 --> 00:56:52.510 align:start position:0% sure where they're planning to use that so<00:56:42.080> I<00:56:42.380> can't<00:56:42.710> say<00:56:42.860> sorry<00:56:50.800> if<00:56:51.800> I<00:56:52.010> just<00:56:52.160> wanted<00:56:52.370> to 00:56:52.510 --> 00:56:52.520 align:start position:0% so I can't say sorry if I just wanted to 00:56:52.520 --> 00:56:53.890 align:start position:0% so I can't say sorry if I just wanted to say<00:56:52.670> that<00:56:52.820> following<00:56:53.030> your<00:56:53.300> question<00:56:53.450> we're 00:56:53.890 --> 00:56:53.900 align:start position:0% say that following your question we're 00:56:53.900 --> 00:56:55.690 align:start position:0% say that following your question we're working<00:56:54.350> on<00:56:54.410> a<00:56:54.530> research<00:56:54.650> paper<00:56:55.010> about<00:56:55.430> this 00:56:55.690 --> 00:56:55.700 align:start position:0% working on a research paper about this 00:56:55.700 --> 00:57:08.620 align:start position:0% working on a research paper about this so<00:56:56.060> in<00:56:56.360> the<00:56:56.480> research<00:57:06.730> the<00:57:07.730> public<00:57:08.240> client 00:57:08.620 --> 00:57:08.630 align:start position:0% so in the research the public client 00:57:08.630 --> 00:57:11.140 align:start position:0% so in the research the public client will<00:57:08.780> still<00:57:09.020> generate<00:57:09.170> the<00:57:09.500> path<00:57:09.680> but<00:57:10.340> the 00:57:11.140 --> 00:57:11.150 align:start position:0% will still generate the path but the 00:57:11.150 --> 00:57:12.790 align:start position:0% will still generate the path but the mixed<00:57:11.390> nerds<00:57:11.600> will<00:57:11.780> need<00:57:11.930> to<00:57:12.140> say<00:57:12.350> what<00:57:12.620> they 00:57:12.790 --> 00:57:12.800 align:start position:0% mixed nerds will need to say what they 00:57:12.800 --> 00:57:15.040 align:start position:0% mixed nerds will need to say what they saw<00:57:13.010> and<00:57:13.310> then<00:57:13.820> factor<00:57:14.090> afterwards<00:57:14.810> the 00:57:15.040 --> 00:57:15.050 align:start position:0% saw and then factor afterwards the 00:57:15.050 --> 00:57:17.470 align:start position:0% saw and then factor afterwards the vieira<00:57:15.350> comes<00:57:15.980> into<00:57:16.220> play<00:57:16.400> everybody<00:57:16.850> opens 00:57:17.470 --> 00:57:17.480 align:start position:0% vieira comes into play everybody opens 00:57:17.480 --> 00:57:20.620 align:start position:0% vieira comes into play everybody opens up<00:57:17.600> the<00:57:17.690> box<00:57:17.900> and<00:57:18.110> goes<00:57:18.260> hey<00:57:18.470> did<00:57:19.090> did<00:57:20.090> Timmy 00:57:20.620 --> 00:57:20.630 align:start position:0% up the box and goes hey did did Timmy 00:57:20.630 --> 00:57:22.690 align:start position:0% up the box and goes hey did did Timmy mix<00:57:20.930> net<00:57:21.140> no<00:57:21.350> to<00:57:21.410> like<00:57:22.010> actually<00:57:22.250> said<00:57:22.580> the 00:57:22.690 --> 00:57:22.700 align:start position:0% mix net no to like actually said the 00:57:22.700 --> 00:57:24.250 align:start position:0% mix net no to like actually said the correct<00:57:22.880> pockets<00:57:23.360> and<00:57:23.570> there's<00:57:23.900> there's 00:57:24.250 --> 00:57:24.260 align:start position:0% correct pockets and there's there's 00:57:24.260 --> 00:57:25.450 align:start position:0% correct pockets and there's there's going<00:57:24.380> to<00:57:24.440> be<00:57:24.500> a<00:57:24.560> record<00:57:24.740> of<00:57:24.920> what<00:57:25.100> he<00:57:25.280> was 00:57:25.450 --> 00:57:25.460 align:start position:0% going to be a record of what he was 00:57:25.460 --> 00:57:28.690 align:start position:0% going to be a record of what he was supposed<00:57:25.610> to<00:57:25.850> have<00:57:26.030> sent<00:57:26.240> basically<00:57:26.660> yeah<00:57:27.700> is 00:57:28.690 --> 00:57:28.700 align:start position:0% supposed to have sent basically yeah is 00:57:28.700 --> 00:57:30.190 align:start position:0% supposed to have sent basically yeah is only<00:57:29.360> produced 00:57:30.190 --> 00:57:30.200 align:start position:0% only produced 00:57:30.200 --> 00:57:32.620 align:start position:0% only produced special<00:57:30.609> measurement<00:57:31.609> messages<00:57:32.240> which<00:57:32.480> are 00:57:32.620 --> 00:57:32.630 align:start position:0% special measurement messages which are 00:57:32.630 --> 00:57:34.930 align:start position:0% special measurement messages which are checking<00:57:32.990> the<00:57:33.230> quality<00:57:33.650> of<00:57:33.740> service<00:57:34.190> the 00:57:34.930 --> 00:57:34.940 align:start position:0% checking the quality of service the 00:57:34.940 --> 00:57:37.240 align:start position:0% checking the quality of service the regular<00:57:35.359> messages<00:57:35.599> is<00:57:36.140> after<00:57:36.740> the<00:57:36.859> client 00:57:37.240 --> 00:57:37.250 align:start position:0% regular messages is after the client 00:57:37.250 --> 00:57:39.339 align:start position:0% regular messages is after the client what<00:57:37.430> he<00:57:37.609> is<00:57:37.670> using<00:57:37.910> wiping<00:57:38.660> the<00:57:38.780> power<00:57:39.050> from 00:57:39.339 --> 00:57:39.349 align:start position:0% what he is using wiping the power from 00:57:39.349 --> 00:57:42.940 align:start position:0% what he is using wiping the power from the<00:57:39.440> cloud<00:57:39.680> he<00:57:40.339> likes<00:57:40.640> and<00:57:40.880> so<00:57:41.030> on<00:57:41.920> thank<00:57:42.920> you 00:57:42.940 --> 00:57:42.950 align:start position:0% the cloud he likes and so on thank you 00:57:42.950 --> 00:57:45.940 align:start position:0% the cloud he likes and so on thank you very<00:57:43.099> much<00:57:43.280> for<00:57:43.369> at<00:57:43.520> a<00:57:43.579> time<00:57:43.790> but<00:57:44.540> if<00:57:45.200> you<00:57:45.740> want 00:57:45.940 --> 00:57:45.950 align:start position:0% very much for at a time but if you want 00:57:45.950 --> 00:57:47.109 align:start position:0% very much for at a time but if you want to<00:57:46.040> keep<00:57:46.160> on<00:57:46.310> chatting<00:57:46.550> out<00:57:46.760> in<00:57:46.849> the<00:57:46.940> hall 00:57:47.109 --> 00:57:47.119 align:start position:0% to keep on chatting out in the hall 00:57:47.119 --> 00:57:50.140 align:start position:0% to keep on chatting out in the hall please<00:57:47.930> come<00:57:48.680> say<00:57:48.829> hello<00:57:48.920> and<00:57:49.430> if<00:57:49.760> anybody's 00:57:50.140 --> 00:57:50.150 align:start position:0% please come say hello and if anybody's 00:57:50.150 --> 00:57:52.000 align:start position:0% please come say hello and if anybody's interested<00:57:50.570> in<00:57:50.720> trying<00:57:51.440> out<00:57:51.650> some<00:57:51.859> of<00:57:51.950> the 00:57:52.000 --> 00:57:52.010 align:start position:0% interested in trying out some of the 00:57:52.010 --> 00:57:53.500 align:start position:0% interested in trying out some of the code<00:57:52.190> or<00:57:52.400> trying<00:57:52.640> to<00:57:52.730> develop<00:57:52.970> against<00:57:53.329> this 00:57:53.500 --> 00:57:53.510 align:start position:0% code or trying to develop against this 00:57:53.510 --> 00:57:58.800 align:start position:0% code or trying to develop against this and 00:57:58.800 --> 00:57:58.810 align:start position:0% 00:57:58.810 --> 00:58:05.670 align:start position:0% [Applause]