WEBVTT Kind: captions Language: en 00:00:04.670 --> 00:00:09.390 align:start position:0% wonderful<00:00:05.630> to<00:00:06.530> be<00:00:06.710> here<00:00:07.010> with<00:00:07.070> all<00:00:07.490> of<00:00:07.520> you<00:00:07.670> at 00:00:09.390 --> 00:00:09.400 align:start position:0% wonderful to be here with all of you at 00:00:09.400 --> 00:00:14.369 align:start position:0% wonderful to be here with all of you at another<00:00:10.400> Def<00:00:11.210> Con<00:00:11.600> again<00:00:12.440> and<00:00:12.709> this<00:00:13.459> time<00:00:13.520> I'm 00:00:14.369 --> 00:00:14.379 align:start position:0% another Def Con again and this time I'm 00:00:14.379 --> 00:00:18.670 align:start position:0% another Def Con again and this time I'm delighted<00:00:15.379> to<00:00:15.590> be<00:00:15.860> able<00:00:16.010> to<00:00:16.390> speak<00:00:17.440> and<00:00:18.440> I 00:00:18.670 --> 00:00:18.680 align:start position:0% delighted to be able to speak and I 00:00:18.680 --> 00:00:25.780 align:start position:0% delighted to be able to speak and I thought<00:00:18.950> I<00:00:18.980> would<00:00:22.450> take<00:00:23.450> you<00:00:23.720> back<00:00:24.020> to 00:00:25.780 --> 00:00:25.790 align:start position:0% thought I would take you back to 00:00:25.790 --> 00:00:27.030 align:start position:0% thought I would take you back to [Music] 00:00:27.030 --> 00:00:27.040 align:start position:0% [Music] 00:00:27.040 --> 00:00:31.720 align:start position:0% [Music] Berkeley<00:00:28.630> 1982<00:00:29.800> when<00:00:30.800> I<00:00:30.830> was<00:00:31.460> a<00:00:31.490> graduate 00:00:31.720 --> 00:00:31.730 align:start position:0% Berkeley 1982 when I was a graduate 00:00:31.730 --> 00:00:34.360 align:start position:0% Berkeley 1982 when I was a graduate student<00:00:32.029> they<00:00:32.540> are<00:00:32.950> reading<00:00:33.950> science 00:00:34.360 --> 00:00:34.370 align:start position:0% student they are reading science 00:00:34.370 --> 00:00:38.950 align:start position:0% student they are reading science magazine<00:00:35.000> and<00:00:35.500> it<00:00:36.500> said<00:00:36.800> that<00:00:37.280> the<00:00:37.960> director 00:00:38.950 --> 00:00:38.960 align:start position:0% magazine and it said that the director 00:00:38.960 --> 00:00:42.250 align:start position:0% magazine and it said that the director of<00:00:39.230> the<00:00:39.800> United<00:00:40.130> States<00:00:40.570> National<00:00:41.570> Security 00:00:42.250 --> 00:00:42.260 align:start position:0% of the United States National Security 00:00:42.260 --> 00:00:45.850 align:start position:0% of the United States National Security Agency<00:00:43.010> had<00:00:43.850> it<00:00:44.390> was<00:00:44.630> revealed<00:00:44.989> written 00:00:45.850 --> 00:00:45.860 align:start position:0% Agency had it was revealed written 00:00:45.860 --> 00:00:48.790 align:start position:0% Agency had it was revealed written letters<00:00:46.340> to<00:00:47.000> the<00:00:47.120> heads<00:00:47.360> of<00:00:47.540> I<00:00:47.750> Triple<00:00:48.260> E<00:00:48.350> and 00:00:48.790 --> 00:00:48.800 align:start position:0% letters to the heads of I Triple E and 00:00:48.800 --> 00:00:52.229 align:start position:0% letters to the heads of I Triple E and ACM<00:00:49.370> and<00:00:49.790> so<00:00:50.000> on<00:00:50.440> threatening<00:00:51.440> them<00:00:51.680> with 00:00:52.229 --> 00:00:52.239 align:start position:0% ACM and so on threatening them with 00:00:52.239 --> 00:00:55.240 align:start position:0% ACM and so on threatening them with draconian<00:00:53.239> the<00:00:53.600> full<00:00:53.890> force<00:00:54.890> of<00:00:55.040> the<00:00:55.100> federal 00:00:55.240 --> 00:00:55.250 align:start position:0% draconian the full force of the federal 00:00:55.250 --> 00:00:57.549 align:start position:0% draconian the full force of the federal government<00:00:55.880> if<00:00:55.970> they<00:00:56.180> were<00:00:56.239> to<00:00:56.630> even<00:00:57.350> have<00:00:57.530> a 00:00:57.549 --> 00:00:57.559 align:start position:0% government if they were to even have a 00:00:57.559 --> 00:01:00.639 align:start position:0% government if they were to even have a session<00:00:58.040> on<00:00:58.370> cryptography<00:00:59.350> let<00:01:00.350> alone<00:01:00.590> a 00:01:00.639 --> 00:01:00.649 align:start position:0% session on cryptography let alone a 00:01:00.649 --> 00:01:04.119 align:start position:0% session on cryptography let alone a whole<00:01:00.950> conference<00:01:01.489> on<00:01:01.820> it<00:01:02.350> so<00:01:03.350> what<00:01:03.950> do<00:01:04.040> you 00:01:04.119 --> 00:01:04.129 align:start position:0% whole conference on it so what do you 00:01:04.129 --> 00:01:09.070 align:start position:0% whole conference on it so what do you think<00:01:04.280> I<00:01:04.430> did<00:01:07.060> yeah<00:01:08.090> organize<00:01:08.509> the<00:01:08.540> conference 00:01:09.070 --> 00:01:09.080 align:start position:0% think I did yeah organize the conference 00:01:09.080 --> 00:01:13.000 align:start position:0% think I did yeah organize the conference on<00:01:09.170> cryptography<00:01:09.500> and<00:01:09.950> I<00:01:10.900> invited<00:01:11.900> everyone<00:01:12.890> I 00:01:13.000 --> 00:01:13.010 align:start position:0% on cryptography and I invited everyone I 00:01:13.010 --> 00:01:16.960 align:start position:0% on cryptography and I invited everyone I did<00:01:13.250> it<00:01:13.340> sort<00:01:13.490> of<00:01:13.549> covertly<00:01:14.030> and<00:01:15.700> then<00:01:16.700> I<00:01:16.729> was 00:01:16.960 --> 00:01:16.970 align:start position:0% did it sort of covertly and then I was 00:01:16.970 --> 00:01:18.880 align:start position:0% did it sort of covertly and then I was like<00:01:17.120> on<00:01:17.360> stage<00:01:17.720> announced<00:01:18.620> you<00:01:18.770> know 00:01:18.880 --> 00:01:18.890 align:start position:0% like on stage announced you know 00:01:18.890 --> 00:01:20.380 align:start position:0% like on stage announced you know welcoming<00:01:19.430> everyone<00:01:19.670> as<00:01:19.880> the<00:01:20.000> general 00:01:20.380 --> 00:01:20.390 align:start position:0% welcoming everyone as the general 00:01:20.390 --> 00:01:25.510 align:start position:0% welcoming everyone as the general chairman<00:01:20.930> of<00:01:21.760> the<00:01:23.049> event<00:01:24.049> and<00:01:24.409> and<00:01:24.619> the<00:01:25.100> front 00:01:25.510 --> 00:01:25.520 align:start position:0% chairman of the event and and the front 00:01:25.520 --> 00:01:31.060 align:start position:0% chairman of the event and and the front row<00:01:26.080> was<00:01:27.080> occupied<00:01:27.590> by<00:01:27.830> people<00:01:28.390> who<00:01:30.070> refused 00:01:31.060 --> 00:01:31.070 align:start position:0% row was occupied by people who refused 00:01:31.070 --> 00:01:33.660 align:start position:0% row was occupied by people who refused to<00:01:31.190> give<00:01:31.430> their<00:01:31.960> organizational<00:01:32.960> affiliation 00:01:33.660 --> 00:01:33.670 align:start position:0% to give their organizational affiliation 00:01:33.670 --> 00:01:37.469 align:start position:0% to give their organizational affiliation but<00:01:34.670> all<00:01:35.290> mysteriously<00:01:36.290> happened<00:01:37.040> to<00:01:37.220> live<00:01:37.430> in 00:01:37.469 --> 00:01:37.479 align:start position:0% but all mysteriously happened to live in 00:01:37.479 --> 00:01:44.469 align:start position:0% but all mysteriously happened to live in Laurel<00:01:38.479> Maryland<00:01:40.119> and<00:01:41.530> so<00:01:42.530> when<00:01:43.490> I<00:01:43.520> announced 00:01:44.469 --> 00:01:44.479 align:start position:0% Laurel Maryland and so when I announced 00:01:44.479 --> 00:01:47.499 align:start position:0% Laurel Maryland and so when I announced that<00:01:44.630> as<00:01:45.040> an<00:01:46.040> extra<00:01:46.340> benefit<00:01:46.880> of<00:01:47.030> having<00:01:47.330> paid 00:01:47.499 --> 00:01:47.509 align:start position:0% that as an extra benefit of having paid 00:01:47.509 --> 00:01:49.390 align:start position:0% that as an extra benefit of having paid their<00:01:47.780> hundred<00:01:48.080> dollars<00:01:48.470> to<00:01:48.680> attend 00:01:49.390 --> 00:01:49.400 align:start position:0% their hundred dollars to attend 00:01:49.400 --> 00:01:53.160 align:start position:0% their hundred dollars to attend they<00:01:50.270> were<00:01:50.330> now<00:01:50.689> members<00:01:51.290> of<00:01:51.590> a<00:01:51.710> new<00:01:51.920> thing<00:01:52.310> the 00:01:53.160 --> 00:01:53.170 align:start position:0% they were now members of a new thing the 00:01:53.170 --> 00:01:55.649 align:start position:0% they were now members of a new thing the International<00:01:54.170> Association<00:01:54.920> for 00:01:55.649 --> 00:01:55.659 align:start position:0% International Association for 00:01:55.659 --> 00:02:00.670 align:start position:0% International Association for Cryptologic<00:01:56.659> research<00:01:57.140> and<00:01:59.229> it<00:02:00.229> was<00:02:00.290> a<00:02:00.439> great 00:02:00.670 --> 00:02:00.680 align:start position:0% Cryptologic research and it was a great 00:02:00.680 --> 00:02:03.749 align:start position:0% Cryptologic research and it was a great pleasure<00:02:00.890> to<00:02:01.070> see<00:02:01.369> them<00:02:01.520> all<00:02:01.670> turn<00:02:01.850> green 00:02:03.749 --> 00:02:03.759 align:start position:0% pleasure to see them all turn green 00:02:03.759 --> 00:02:06.310 align:start position:0% pleasure to see them all turn green because<00:02:04.759> everyone<00:02:05.329> knew<00:02:05.509> that<00:02:05.750> it<00:02:05.840> was<00:02:05.960> over 00:02:06.310 --> 00:02:06.320 align:start position:0% because everyone knew that it was over 00:02:06.320 --> 00:02:08.649 align:start position:0% because everyone knew that it was over there<00:02:06.590> was<00:02:06.710> the<00:02:06.950> the<00:02:07.670> UN<00:02:08.000> protects 00:02:08.649 --> 00:02:08.659 align:start position:0% there was the the UN protects 00:02:08.659 --> 00:02:10.869 align:start position:0% there was the the UN protects international<00:02:09.500> scientific<00:02:09.890> associations 00:02:10.869 --> 00:02:10.879 align:start position:0% international scientific associations 00:02:10.879 --> 00:02:15.130 align:start position:0% international scientific associations and<00:02:11.180> so<00:02:12.049> I<00:02:12.650> ACR<00:02:12.890> has<00:02:13.610> had<00:02:13.940> about<00:02:14.840> several 00:02:15.130 --> 00:02:15.140 align:start position:0% and so I ACR has had about several 00:02:15.140 --> 00:02:16.839 align:start position:0% and so I ACR has had about several conferences<00:02:15.680> every<00:02:15.860> year<00:02:16.010> now<00:02:16.280> it<00:02:16.400> says<00:02:16.550> three 00:02:16.839 --> 00:02:16.849 align:start position:0% conferences every year now it says three 00:02:16.849 --> 00:02:18.220 align:start position:0% conferences every year now it says three per<00:02:17.090> year 00:02:18.220 --> 00:02:18.230 align:start position:0% per year 00:02:18.230 --> 00:02:20.559 align:start position:0% per year a<00:02:18.260> bunch<00:02:18.590> of<00:02:18.709> workshops<00:02:19.250> and<00:02:19.670> publishes<00:02:20.510> a 00:02:20.559 --> 00:02:20.569 align:start position:0% a bunch of workshops and publishes a 00:02:20.569 --> 00:02:23.050 align:start position:0% a bunch of workshops and publishes a journal<00:02:20.870> with<00:02:20.959> springer-verlag<00:02:21.379> so<00:02:22.190> it<00:02:22.819> was 00:02:23.050 --> 00:02:23.060 align:start position:0% journal with springer-verlag so it was 00:02:23.060 --> 00:02:28.440 align:start position:0% journal with springer-verlag so it was over<00:02:25.120> cryptography<00:02:26.120> was<00:02:26.330> set<00:02:26.569> free<00:02:26.930> however 00:02:28.440 --> 00:02:28.450 align:start position:0% over cryptography was set free however 00:02:28.450 --> 00:02:36.070 align:start position:0% over cryptography was set free however we<00:02:29.450> are<00:02:29.750> now<00:02:31.299> at<00:02:32.319> a<00:02:33.319> very<00:02:34.360> different<00:02:35.360> and<00:02:35.510> more 00:02:36.070 --> 00:02:36.080 align:start position:0% we are now at a very different and more 00:02:36.080 --> 00:02:39.420 align:start position:0% we are now at a very different and more fundamental<00:02:36.890> critical<00:02:37.549> juncture<00:02:38.209> it's<00:02:38.780> less 00:02:39.420 --> 00:02:39.430 align:start position:0% fundamental critical juncture it's less 00:02:39.430 --> 00:02:43.600 align:start position:0% fundamental critical juncture it's less reversible<00:02:40.430> and<00:02:40.819> much<00:02:41.599> more<00:02:42.459> important<00:02:43.459> and 00:02:43.600 --> 00:02:43.610 align:start position:0% reversible and much more important and 00:02:43.610 --> 00:02:46.990 align:start position:0% reversible and much more important and that<00:02:44.000> is<00:02:44.980> evidenced<00:02:45.980> by<00:02:46.099> the<00:02:46.250> fact<00:02:46.400> that<00:02:46.700> most 00:02:46.990 --> 00:02:47.000 align:start position:0% that is evidenced by the fact that most 00:02:47.000 --> 00:02:49.059 align:start position:0% that is evidenced by the fact that most of<00:02:47.480> the<00:02:47.690> public<00:02:47.900> is<00:02:48.290> starting<00:02:48.799> to<00:02:48.890> become 00:02:49.059 --> 00:02:49.069 align:start position:0% of the public is starting to become 00:02:49.069 --> 00:02:52.990 align:start position:0% of the public is starting to become aware<00:02:49.790> of<00:02:50.500> metadata<00:02:51.500> and<00:02:51.920> the<00:02:52.310> dangers<00:02:52.790> of 00:02:52.990 --> 00:02:53.000 align:start position:0% aware of metadata and the dangers of 00:02:53.000 --> 00:02:56.289 align:start position:0% aware of metadata and the dangers of metadata<00:02:53.450> and<00:02:53.870> how<00:02:54.530> it's<00:02:54.980> being<00:02:55.400> used<00:02:55.819> to 00:02:56.289 --> 00:02:56.299 align:start position:0% metadata and how it's being used to 00:02:56.299 --> 00:03:01.330 align:start position:0% metadata and how it's being used to steal<00:02:57.019> our<00:02:57.609> meta<00:02:58.609> Liberty<00:02:59.150> from<00:02:59.510> us<00:03:00.340> which 00:03:01.330 --> 00:03:01.340 align:start position:0% steal our meta Liberty from us which 00:03:01.340 --> 00:03:03.220 align:start position:0% steal our meta Liberty from us which includes<00:03:02.120> then<00:03:02.329> all<00:03:02.480> the<00:03:02.629> subsidiary 00:03:03.220 --> 00:03:03.230 align:start position:0% includes then all the subsidiary 00:03:03.230 --> 00:03:06.309 align:start position:0% includes then all the subsidiary liberties<00:03:03.799> right<00:03:04.129> it's<00:03:04.849> the<00:03:05.090> big<00:03:05.269> one<00:03:05.319> lose 00:03:06.309 --> 00:03:06.319 align:start position:0% liberties right it's the big one lose 00:03:06.319 --> 00:03:13.449 align:start position:0% liberties right it's the big one lose that<00:03:06.620> and<00:03:06.920> it's<00:03:07.730> game<00:03:07.970> over<00:03:09.160> so<00:03:11.920> turns<00:03:12.920> out<00:03:13.160> in 00:03:13.449 --> 00:03:13.459 align:start position:0% that and it's game over so turns out in 00:03:13.459 --> 00:03:18.210 align:start position:0% that and it's game over so turns out in Berkeley<00:03:13.910> in<00:03:13.940> 82<00:03:14.540> I<00:03:15.579> was<00:03:16.579> actually<00:03:16.790> working<00:03:17.269> on 00:03:18.210 --> 00:03:18.220 align:start position:0% Berkeley in 82 I was actually working on 00:03:18.220 --> 00:03:21.270 align:start position:0% Berkeley in 82 I was actually working on cryptography<00:03:19.220> for<00:03:19.879> the<00:03:20.239> purpose<00:03:20.660> of<00:03:20.840> finding 00:03:21.270 --> 00:03:21.280 align:start position:0% cryptography for the purpose of finding 00:03:21.280 --> 00:03:27.099 align:start position:0% cryptography for the purpose of finding metadata<00:03:22.280> shredding<00:03:23.060> techniques<00:03:24.190> so<00:03:26.109> the 00:03:27.099 --> 00:03:27.109 align:start position:0% metadata shredding techniques so the 00:03:27.109 --> 00:03:28.509 align:start position:0% metadata shredding techniques so the first<00:03:27.380> thing<00:03:27.620> I<00:03:27.709> did<00:03:27.889> was<00:03:27.950> create<00:03:28.340> a<00:03:28.370> like<00:03:28.489> a 00:03:28.509 --> 00:03:28.519 align:start position:0% first thing I did was create a like a 00:03:28.519 --> 00:03:30.670 align:start position:0% first thing I did was create a like a toy<00:03:28.790> example<00:03:29.480> where<00:03:29.630> some<00:03:29.840> privacy<00:03:30.290> would<00:03:30.560> be 00:03:30.670 --> 00:03:30.680 align:start position:0% toy example where some privacy would be 00:03:30.680 --> 00:03:32.860 align:start position:0% toy example where some privacy would be needed<00:03:30.950> so<00:03:31.130> I<00:03:31.160> used<00:03:31.400> voting<00:03:31.880> let<00:03:32.510> me<00:03:32.599> just<00:03:32.780> try 00:03:32.860 --> 00:03:32.870 align:start position:0% needed so I used voting let me just try 00:03:32.870 --> 00:03:35.470 align:start position:0% needed so I used voting let me just try to<00:03:32.989> explain<00:03:33.349> roughly<00:03:33.980> how<00:03:34.220> this<00:03:34.459> works<00:03:35.180> just 00:03:35.470 --> 00:03:35.480 align:start position:0% to explain roughly how this works just 00:03:35.480 --> 00:03:37.809 align:start position:0% to explain roughly how this works just to<00:03:35.599> give<00:03:35.750> you<00:03:35.840> a<00:03:35.870> sense<00:03:36.230> that<00:03:36.669> let's<00:03:37.669> say 00:03:37.809 --> 00:03:37.819 align:start position:0% to give you a sense that let's say 00:03:37.819 --> 00:03:40.599 align:start position:0% to give you a sense that let's say there's<00:03:38.209> a<00:03:38.299> hundred<00:03:38.510> voters<00:03:38.930> each<00:03:39.440> would<00:03:39.889> take 00:03:40.599 --> 00:03:40.609 align:start position:0% there's a hundred voters each would take 00:03:40.609 --> 00:03:43.539 align:start position:0% there's a hundred voters each would take their<00:03:40.880> ballot<00:03:41.419> and<00:03:41.829> multiple<00:03:42.829> 'i<00:03:42.889> encrypt<00:03:43.310> it 00:03:43.539 --> 00:03:43.549 align:start position:0% their ballot and multiple 'i encrypt it 00:03:43.549 --> 00:03:47.110 align:start position:0% their ballot and multiple 'i encrypt it and<00:03:43.849> publish<00:03:44.720> it<00:03:45.130> let's<00:03:46.130> say<00:03:46.250> associated<00:03:47.000> with 00:03:47.110 --> 00:03:47.120 align:start position:0% and publish it let's say associated with 00:03:47.120 --> 00:03:51.159 align:start position:0% and publish it let's say associated with their<00:03:47.329> IP<00:03:47.510> address<00:03:48.549> okay<00:03:49.579> and<00:03:49.819> then<00:03:50.450> they 00:03:51.159 --> 00:03:51.169 align:start position:0% their IP address okay and then they 00:03:51.169 --> 00:03:53.440 align:start position:0% their IP address okay and then they would<00:03:51.349> those<00:03:52.280> who<00:03:52.430> all<00:03:52.669> those<00:03:52.910> encrypted 00:03:53.440 --> 00:03:53.450 align:start position:0% would those who all those encrypted 00:03:53.450 --> 00:03:55.199 align:start position:0% would those who all those encrypted ballots<00:03:53.810> would<00:03:53.930> be<00:03:54.079> sent<00:03:54.319> to<00:03:54.440> the<00:03:54.530> first<00:03:54.799> node 00:03:55.199 --> 00:03:55.209 align:start position:0% ballots would be sent to the first node 00:03:55.209 --> 00:03:57.250 align:start position:0% ballots would be sent to the first node which<00:03:56.209> would<00:03:56.450> have<00:03:56.630> the<00:03:56.660> unique<00:03:57.079> ability 00:03:57.250 --> 00:03:57.260 align:start position:0% which would have the unique ability 00:03:57.260 --> 00:03:59.710 align:start position:0% which would have the unique ability through<00:03:57.799> its<00:03:57.950> private<00:03:58.370> key<00:03:58.549> to<00:03:58.790> decrypt<00:03:59.299> the 00:03:59.710 --> 00:03:59.720 align:start position:0% through its private key to decrypt the 00:03:59.720 --> 00:04:01.839 align:start position:0% through its private key to decrypt the outer<00:03:59.930> layer<00:04:00.349> on<00:04:00.650> all<00:04:00.680> those<00:04:01.040> ballots<00:04:01.579> and 00:04:01.839 --> 00:04:01.849 align:start position:0% outer layer on all those ballots and 00:04:01.849 --> 00:04:04.420 align:start position:0% outer layer on all those ballots and then<00:04:02.510> it<00:04:02.629> would<00:04:02.780> shuffle<00:04:03.379> them<00:04:03.739> secretly<00:04:04.160> in<00:04:04.370> a 00:04:04.420 --> 00:04:04.430 align:start position:0% then it would shuffle them secretly in a 00:04:04.430 --> 00:04:07.150 align:start position:0% then it would shuffle them secretly in a random<00:04:04.849> order<00:04:05.000> that<00:04:05.720> only<00:04:05.989> it<00:04:06.109> knew<00:04:06.319> and<00:04:06.590> send 00:04:07.150 --> 00:04:07.160 align:start position:0% random order that only it knew and send 00:04:07.160 --> 00:04:09.430 align:start position:0% random order that only it knew and send them<00:04:07.280> on<00:04:07.370> to<00:04:07.430> the<00:04:07.609> next<00:04:07.639> node<00:04:08.030> and<00:04:08.299> that<00:04:09.230> node 00:04:09.430 --> 00:04:09.440 align:start position:0% them on to the next node and that node 00:04:09.440 --> 00:04:11.289 align:start position:0% them on to the next node and that node would<00:04:09.950> do<00:04:10.069> the<00:04:10.190> same<00:04:10.370> thing<00:04:10.430> decrypt<00:04:11.150> the 00:04:11.289 --> 00:04:11.299 align:start position:0% would do the same thing decrypt the 00:04:11.299 --> 00:04:12.750 align:start position:0% would do the same thing decrypt the layer<00:04:11.480> that<00:04:11.720> only<00:04:11.870> it<00:04:12.079> could<00:04:12.260> decrypt 00:04:12.750 --> 00:04:12.760 align:start position:0% layer that only it could decrypt 00:04:12.760 --> 00:04:15.369 align:start position:0% layer that only it could decrypt randomly<00:04:13.760> permute<00:04:14.120> and<00:04:14.359> send<00:04:14.690> on<00:04:14.870> and<00:04:15.109> so<00:04:15.199> the 00:04:15.369 --> 00:04:15.379 align:start position:0% randomly permute and send on and so the 00:04:15.379 --> 00:04:17.170 align:start position:0% randomly permute and send on and so the final<00:04:15.859> batch<00:04:16.039> that<00:04:16.400> comes<00:04:16.639> out<00:04:16.880> and<00:04:17.120> is 00:04:17.170 --> 00:04:17.180 align:start position:0% final batch that comes out and is 00:04:17.180 --> 00:04:19.900 align:start position:0% final batch that comes out and is published<00:04:18.099> includes<00:04:19.099> all<00:04:19.340> the<00:04:19.459> clear<00:04:19.669> text 00:04:19.900 --> 00:04:19.910 align:start position:0% published includes all the clear text 00:04:19.910 --> 00:04:25.500 align:start position:0% published includes all the clear text ballots<00:04:21.160> but<00:04:22.160> I<00:04:22.580> say<00:04:23.360> that<00:04:23.570> we<00:04:23.990> have<00:04:24.229> vertical 00:04:25.500 --> 00:04:25.510 align:start position:0% ballots but I say that we have vertical 00:04:25.510 --> 00:04:28.600 align:start position:0% ballots but I say that we have vertical metadata<00:04:26.510> protection<00:04:27.169> because<00:04:27.590> no<00:04:28.219> one<00:04:28.400> knows 00:04:28.600 --> 00:04:28.610 align:start position:0% metadata protection because no one knows 00:04:28.610 --> 00:04:31.330 align:start position:0% metadata protection because no one knows which<00:04:29.120> IP<00:04:29.390> address<00:04:29.960> is<00:04:30.229> associated<00:04:30.919> with 00:04:31.330 --> 00:04:31.340 align:start position:0% which IP address is associated with 00:04:31.340 --> 00:04:31.780 align:start position:0% which IP address is associated with which 00:04:31.780 --> 00:04:31.790 align:start position:0% which 00:04:31.790 --> 00:04:34.570 align:start position:0% which ballot<00:04:32.210> unless<00:04:32.360> they<00:04:33.170> can<00:04:33.230> compromise<00:04:33.770> all<00:04:34.340> of 00:04:34.570 --> 00:04:34.580 align:start position:0% ballot unless they can compromise all of 00:04:34.580 --> 00:04:37.300 align:start position:0% ballot unless they can compromise all of the<00:04:34.700> nodes<00:04:35.320> because<00:04:36.320> each<00:04:36.560> node<00:04:36.830> uses<00:04:37.280> a 00:04:37.300 --> 00:04:37.310 align:start position:0% the nodes because each node uses a 00:04:37.310 --> 00:04:40.360 align:start position:0% the nodes because each node uses a totally<00:04:37.730> independent<00:04:38.800> uniform<00:04:39.800> randomly 00:04:40.360 --> 00:04:40.370 align:start position:0% totally independent uniform randomly 00:04:40.370 --> 00:04:45.370 align:start position:0% totally independent uniform randomly chosen<00:04:40.790> permutation<00:04:41.480> so<00:04:43.690> this<00:04:44.690> became<00:04:45.140> known 00:04:45.370 --> 00:04:45.380 align:start position:0% chosen permutation so this became known 00:04:45.380 --> 00:04:47.830 align:start position:0% chosen permutation so this became known as<00:04:45.560> mixing<00:04:46.130> and<00:04:46.520> there's<00:04:47.360> thousands<00:04:47.750> of 00:04:47.830 --> 00:04:47.840 align:start position:0% as mixing and there's thousands of 00:04:47.840 --> 00:04:49.180 align:start position:0% as mixing and there's thousands of papers<00:04:47.990> about<00:04:48.500> it<00:04:48.710> and<00:04:48.830> it's<00:04:48.920> generally 00:04:49.180 --> 00:04:49.190 align:start position:0% papers about it and it's generally 00:04:49.190 --> 00:04:50.470 align:start position:0% papers about it and it's generally thought<00:04:49.490> of<00:04:49.550> as<00:04:49.700> being<00:04:49.940> used<00:04:50.090> to<00:04:50.210> send 00:04:50.470 --> 00:04:50.480 align:start position:0% thought of as being used to send 00:04:50.480 --> 00:04:56.290 align:start position:0% thought of as being used to send messages<00:04:53.050> it<00:04:54.220> destroys<00:04:55.220> the<00:04:55.640> social<00:04:56.120> graph 00:04:56.290 --> 00:04:56.300 align:start position:0% messages it destroys the social graph 00:04:56.300 --> 00:04:58.750 align:start position:0% messages it destroys the social graph the<00:04:56.600> who<00:04:56.750> talks<00:04:57.080> to<00:04:57.290> who<00:04:57.440> and<00:04:57.710> when<00:04:57.950> that's 00:04:58.750 --> 00:04:58.760 align:start position:0% the who talks to who and when that's 00:04:58.760 --> 00:05:00.970 align:start position:0% the who talks to who and when that's what<00:04:59.000> we<00:04:59.090> used<00:04:59.270> to<00:04:59.390> call<00:04:59.630> traffic<00:05:00.380> analysis 00:05:00.970 --> 00:05:00.980 align:start position:0% what we used to call traffic analysis 00:05:00.980 --> 00:05:07.620 align:start position:0% what we used to call traffic analysis now<00:05:01.160> it's<00:05:01.340> been<00:05:01.520> rebranded<00:05:01.820> as<00:05:02.300> metadata<00:05:04.210> so 00:05:07.620 --> 00:05:07.630 align:start position:0% 00:05:07.630 --> 00:05:10.210 align:start position:0% then<00:05:08.630> I<00:05:08.660> thought<00:05:09.080> well<00:05:09.230> we<00:05:09.470> need<00:05:09.500> some<00:05:09.860> kind<00:05:10.130> of 00:05:10.210 --> 00:05:10.220 align:start position:0% then I thought well we need some kind of 00:05:10.220 --> 00:05:13.900 align:start position:0% then I thought well we need some kind of way<00:05:10.400> to<00:05:10.430> pay<00:05:10.850> and<00:05:11.180> stuff<00:05:11.420> like<00:05:11.660> that<00:05:12.020> and<00:05:12.670> if<00:05:13.670> I 00:05:13.900 --> 00:05:13.910 align:start position:0% way to pay and stuff like that and if I 00:05:13.910 --> 00:05:16.020 align:start position:0% way to pay and stuff like that and if I look<00:05:14.210> at<00:05:14.390> regular<00:05:14.810> like<00:05:15.200> the<00:05:15.350> kind<00:05:15.560> of<00:05:15.620> say 00:05:16.020 --> 00:05:16.030 align:start position:0% look at regular like the kind of say 00:05:16.030 --> 00:05:18.310 align:start position:0% look at regular like the kind of say account<00:05:17.030> based<00:05:17.270> payments<00:05:17.720> we<00:05:17.810> have<00:05:17.960> like<00:05:18.170> I'm 00:05:18.310 --> 00:05:18.320 align:start position:0% account based payments we have like I'm 00:05:18.320 --> 00:05:20.410 align:start position:0% account based payments we have like I'm blockchain<00:05:18.650> today<00:05:18.920> from<00:05:19.790> Walt<00:05:20.000> I<00:05:20.120> need<00:05:20.330> a 00:05:20.410 --> 00:05:20.420 align:start position:0% blockchain today from Walt I need a 00:05:20.420 --> 00:05:22.510 align:start position:0% blockchain today from Walt I need a wallet<00:05:20.630> ID<00:05:20.840> a<00:05:20.930> wallet<00:05:21.260> ID<00:05:21.380> what<00:05:21.890> that<00:05:22.070> does<00:05:22.280> is 00:05:22.510 --> 00:05:22.520 align:start position:0% wallet ID a wallet ID what that does is 00:05:22.520 --> 00:05:24.490 align:start position:0% wallet ID a wallet ID what that does is it<00:05:22.700> publishes<00:05:23.360> improves<00:05:23.900> the<00:05:24.050> whole<00:05:24.200> method 00:05:24.490 --> 00:05:24.500 align:start position:0% it publishes improves the whole method 00:05:24.500 --> 00:05:27.880 align:start position:0% it publishes improves the whole method the<00:05:24.920> whole<00:05:25.100> the<00:05:25.580> whole<00:05:25.730> graph<00:05:25.970> right<00:05:26.840> it's<00:05:27.470> all 00:05:27.880 --> 00:05:27.890 align:start position:0% the whole the whole graph right it's all 00:05:27.890 --> 00:05:31.030 align:start position:0% the whole the whole graph right it's all it<00:05:28.550> reveals<00:05:28.880> improves<00:05:29.630> all<00:05:29.810> the<00:05:29.930> metadata<00:05:30.260> so 00:05:31.030 --> 00:05:31.040 align:start position:0% it reveals improves all the metadata so 00:05:31.040 --> 00:05:34.990 align:start position:0% it reveals improves all the metadata so that's<00:05:31.460> not<00:05:31.820> a<00:05:31.880> suitable<00:05:32.420> type<00:05:33.260> of<00:05:33.650> of<00:05:34.010> payment 00:05:34.990 --> 00:05:35.000 align:start position:0% that's not a suitable type of of payment 00:05:35.000 --> 00:05:37.660 align:start position:0% that's not a suitable type of of payment technology<00:05:35.690> so<00:05:36.290> it<00:05:36.350> turns<00:05:36.650> out<00:05:36.950> that<00:05:37.460> what<00:05:37.640> I 00:05:37.660 --> 00:05:37.670 align:start position:0% technology so it turns out that what I 00:05:37.670 --> 00:05:40.960 align:start position:0% technology so it turns out that what I proposed<00:05:38.270> is<00:05:38.720> is<00:05:39.320> actually<00:05:39.950> good<00:05:40.490> enough<00:05:40.760> not 00:05:40.960 --> 00:05:40.970 align:start position:0% proposed is is actually good enough not 00:05:40.970 --> 00:05:44.490 align:start position:0% proposed is is actually good enough not perfect<00:05:41.540> but<00:05:41.900> it<00:05:42.050> can<00:05:42.470> be<00:05:42.650> perfected<00:05:43.520> so 00:05:44.490 --> 00:05:44.500 align:start position:0% perfect but it can be perfected so 00:05:44.500 --> 00:05:47.590 align:start position:0% perfect but it can be perfected so essentially<00:05:45.500> it's<00:05:45.710> a<00:05:45.860> simple<00:05:46.280> notion<00:05:47.090> that 00:05:47.590 --> 00:05:47.600 align:start position:0% essentially it's a simple notion that 00:05:47.600 --> 00:05:51.130 align:start position:0% essentially it's a simple notion that instead<00:05:47.990> of<00:05:48.050> accounts<00:05:48.710> use<00:05:49.510> digital<00:05:50.510> bearer 00:05:51.130 --> 00:05:51.140 align:start position:0% instead of accounts use digital bearer 00:05:51.140 --> 00:05:53.410 align:start position:0% instead of accounts use digital bearer instruments<00:05:51.920> that<00:05:52.070> are<00:05:52.190> let's<00:05:52.700> say<00:05:52.820> binary 00:05:53.410 --> 00:05:53.420 align:start position:0% instruments that are let's say binary 00:05:53.420 --> 00:05:56.020 align:start position:0% instruments that are let's say binary denominated<00:05:54.230> so<00:05:54.440> one<00:05:54.710> sent<00:05:55.070> to<00:05:55.340> send<00:05:55.700> four 00:05:56.020 --> 00:05:56.030 align:start position:0% denominated so one sent to send four 00:05:56.030 --> 00:05:59.520 align:start position:0% denominated so one sent to send four sent<00:05:56.390> eight<00:05:56.870> sent<00:05:57.350> 16<00:05:58.190> and<00:05:58.430> so<00:05:58.640> on<00:05:58.670> so<00:05:59.060> each 00:05:59.520 --> 00:05:59.530 align:start position:0% sent eight sent 16 and so on so each 00:05:59.530 --> 00:06:01.960 align:start position:0% sent eight sent 16 and so on so each denomination<00:06:00.530> has<00:06:00.740> its<00:06:01.100> own<00:06:01.220> corresponding 00:06:01.960 --> 00:06:01.970 align:start position:0% denomination has its own corresponding 00:06:01.970 --> 00:06:06.640 align:start position:0% denomination has its own corresponding signature<00:06:02.480> that<00:06:02.960> validates<00:06:03.560> it<00:06:03.830> and<00:06:05.350> that<00:06:06.350> way 00:06:06.640 --> 00:06:06.650 align:start position:0% signature that validates it and that way 00:06:06.650 --> 00:06:12.250 align:start position:0% signature that validates it and that way as<00:06:07.040> the<00:06:08.140> the<00:06:09.140> these<00:06:09.620> digital<00:06:10.240> tokens<00:06:11.260> migrate 00:06:12.250 --> 00:06:12.260 align:start position:0% as the the these digital tokens migrate 00:06:12.260 --> 00:06:13.930 align:start position:0% as the the these digital tokens migrate through<00:06:12.560> different<00:06:13.070> transactions<00:06:13.760> they're 00:06:13.930 --> 00:06:13.940 align:start position:0% through different transactions they're 00:06:13.940 --> 00:06:16.600 align:start position:0% through different transactions they're regrouped<00:06:14.450> and<00:06:14.720> the<00:06:14.870> metadata<00:06:15.410> kind<00:06:15.770> of<00:06:15.920> fades 00:06:16.600 --> 00:06:16.610 align:start position:0% regrouped and the metadata kind of fades 00:06:16.610 --> 00:06:20.040 align:start position:0% regrouped and the metadata kind of fades away<00:06:16.880> now<00:06:17.840> we<00:06:17.900> can<00:06:18.230> perfect<00:06:18.740> this<00:06:18.980> by<00:06:19.340> actually 00:06:20.040 --> 00:06:20.050 align:start position:0% away now we can perfect this by actually 00:06:20.050 --> 00:06:22.060 align:start position:0% away now we can perfect this by actually washing<00:06:21.050> a<00:06:21.140> whole<00:06:21.320> bus<00:06:21.470> like<00:06:21.590> all<00:06:21.800> the<00:06:21.920> one 00:06:22.060 --> 00:06:22.070 align:start position:0% washing a whole bus like all the one 00:06:22.070 --> 00:06:25.180 align:start position:0% washing a whole bus like all the one cent<00:06:22.370> coins<00:06:22.670> through<00:06:23.390> a<00:06:23.420> special<00:06:24.050> mix<00:06:24.380> that 00:06:25.180 --> 00:06:25.190 align:start position:0% cent coins through a special mix that 00:06:25.190 --> 00:06:29.860 align:start position:0% cent coins through a special mix that then<00:06:25.820> makes<00:06:26.600> every<00:06:27.050> one<00:06:27.800> cent<00:06:28.100> coin<00:06:28.870> unlink 00:06:29.860 --> 00:06:29.870 align:start position:0% then makes every one cent coin unlink 00:06:29.870 --> 00:06:31.990 align:start position:0% then makes every one cent coin unlink able<00:06:30.110> to<00:06:30.380> the<00:06:30.680> ones<00:06:31.190> that<00:06:31.400> existed<00:06:31.790> previously 00:06:31.990 --> 00:06:32.000 align:start position:0% able to the ones that existed previously 00:06:32.000 --> 00:06:33.610 align:start position:0% able to the ones that existed previously so<00:06:32.660> we<00:06:32.720> can<00:06:32.840> do<00:06:32.900> that<00:06:33.020> overnight<00:06:33.230> for<00:06:33.530> all 00:06:33.610 --> 00:06:33.620 align:start position:0% so we can do that overnight for all 00:06:33.620 --> 00:06:36.160 align:start position:0% so we can do that overnight for all coins<00:06:33.860> and<00:06:34.190> then<00:06:34.360> perfect<00:06:35.360> privacy<00:06:35.840> because 00:06:36.160 --> 00:06:36.170 align:start position:0% coins and then perfect privacy because 00:06:36.170 --> 00:06:39.880 align:start position:0% coins and then perfect privacy because we<00:06:36.320> have<00:06:36.470> the<00:06:36.620> vertical<00:06:37.660> unlinking<00:06:38.890> but 00:06:39.880 --> 00:06:39.890 align:start position:0% we have the vertical unlinking but 00:06:39.890 --> 00:06:42.850 align:start position:0% we have the vertical unlinking but through<00:06:40.340> the<00:06:40.430> mixing<00:06:40.910> of<00:06:41.150> the<00:06:41.420> CIP<00:06:42.020> mac<00:06:42.530> or 00:06:42.850 --> 00:06:42.860 align:start position:0% through the mixing of the CIP mac or 00:06:42.860 --> 00:06:44.670 align:start position:0% through the mixing of the CIP mac or your<00:06:42.950> location<00:06:43.400> or<00:06:43.490> whatever<00:06:43.790> to 00:06:44.670 --> 00:06:44.680 align:start position:0% your location or whatever to 00:06:44.680 --> 00:06:46.740 align:start position:0% your location or whatever to the<00:06:45.040> transactions<00:06:45.880> or<00:06:46.030> the<00:06:46.120> messages<00:06:46.630> to 00:06:46.740 --> 00:06:46.750 align:start position:0% the transactions or the messages to 00:06:46.750 --> 00:06:48.810 align:start position:0% the transactions or the messages to being<00:06:46.990> delivered<00:06:47.259> and<00:06:47.680> then<00:06:48.400> we<00:06:48.520> have<00:06:48.669> the 00:06:48.810 --> 00:06:48.820 align:start position:0% being delivered and then we have the 00:06:48.820 --> 00:06:50.700 align:start position:0% being delivered and then we have the horizontal<00:06:49.060> and<00:06:49.690> link<00:06:49.900> ability<00:06:50.320> or<00:06:50.410> metadata 00:06:50.700 --> 00:06:50.710 align:start position:0% horizontal and link ability or metadata 00:06:50.710 --> 00:06:52.469 align:start position:0% horizontal and link ability or metadata shredding<00:06:51.250> between<00:06:52.000> the<00:06:52.180> say<00:06:52.330> the 00:06:52.469 --> 00:06:52.479 align:start position:0% shredding between the say the 00:06:52.479 --> 00:07:04.980 align:start position:0% shredding between the say the transactions<00:06:53.320> themselves<00:06:56.190> so<00:07:03.330> the<00:07:04.330> the 00:07:04.980 --> 00:07:04.990 align:start position:0% transactions themselves so the the 00:07:04.990 --> 00:07:07.439 align:start position:0% transactions themselves so the the payment<00:07:05.380> system<00:07:05.710> actually<00:07:05.919> was<00:07:06.340> a<00:07:06.699> built<00:07:07.180> in 00:07:07.439 --> 00:07:07.449 align:start position:0% payment system actually was a built in 00:07:07.449 --> 00:07:08.400 align:start position:0% payment system actually was a built in that<00:07:07.570> you've<00:07:07.690> probably<00:07:07.960> heard<00:07:08.169> of<00:07:08.289> it 00:07:08.400 --> 00:07:08.410 align:start position:0% that you've probably heard of it 00:07:08.410 --> 00:07:10.950 align:start position:0% that you've probably heard of it famously<00:07:08.770> in<00:07:08.949> the<00:07:09.009> mid-90s<00:07:09.669> and<00:07:10.060> I 00:07:10.950 --> 00:07:10.960 align:start position:0% famously in the mid-90s and I 00:07:10.960 --> 00:07:15.689 align:start position:0% famously in the mid-90s and I air-dropped<00:07:11.680> to<00:07:12.550> anyone<00:07:13.030> who<00:07:13.210> wanted<00:07:13.750> a<00:07:14.699> who 00:07:15.689 --> 00:07:15.699 align:start position:0% air-dropped to anyone who wanted a who 00:07:15.699 --> 00:07:17.969 align:start position:0% air-dropped to anyone who wanted a who would<00:07:15.820> open<00:07:15.940> up<00:07:16.180> a<00:07:16.509> digital<00:07:16.990> shop<00:07:17.410> on<00:07:17.710> the<00:07:17.830> web 00:07:17.969 --> 00:07:17.979 align:start position:0% would open up a digital shop on the web 00:07:17.979 --> 00:07:21.750 align:start position:0% would open up a digital shop on the web and<00:07:18.639> receive<00:07:18.940> payments<00:07:19.510> a<00:07:19.889> 100<00:07:20.889> cyber<00:07:21.100> box<00:07:21.400> and 00:07:21.750 --> 00:07:21.760 align:start position:0% and receive payments a 100 cyber box and 00:07:21.760 --> 00:07:24.240 align:start position:0% and receive payments a 100 cyber box and you<00:07:22.570> can<00:07:22.750> see<00:07:22.900> the<00:07:23.020> whole<00:07:23.139> dish<00:07:23.350> the<00:07:23.560> Museum<00:07:24.039> of 00:07:24.240 --> 00:07:24.250 align:start position:0% you can see the whole dish the Museum of 00:07:24.250 --> 00:07:27.900 align:start position:0% you can see the whole dish the Museum of this<00:07:24.400> up<00:07:24.669> on<00:07:24.820> my<00:07:24.940> website<00:07:25.150> charm<00:07:26.110> comm<00:07:26.910> bunch 00:07:27.900 --> 00:07:27.910 align:start position:0% this up on my website charm comm bunch 00:07:27.910 --> 00:07:30.719 align:start position:0% this up on my website charm comm bunch of<00:07:28.090> the<00:07:28.180> shops<00:07:28.479> and<00:07:28.990> and<00:07:29.860> so<00:07:30.130> forth<00:07:30.460> and<00:07:30.610> then 00:07:30.719 --> 00:07:30.729 align:start position:0% of the shops and and so forth and then 00:07:30.729 --> 00:07:33.480 align:start position:0% of the shops and and so forth and then later<00:07:30.970> some<00:07:31.840> banks<00:07:32.260> wanted<00:07:32.620> to<00:07:32.740> issue<00:07:32.889> a<00:07:33.100> cash 00:07:33.480 --> 00:07:33.490 align:start position:0% later some banks wanted to issue a cash 00:07:33.490 --> 00:07:36.390 align:start position:0% later some banks wanted to issue a cash so<00:07:33.940> we<00:07:34.210> let<00:07:34.720> Deutsche<00:07:35.229> Bank<00:07:35.440> do<00:07:35.710> it<00:07:35.889> and<00:07:36.250> some 00:07:36.390 --> 00:07:36.400 align:start position:0% so we let Deutsche Bank do it and some 00:07:36.400 --> 00:07:37.860 align:start position:0% so we let Deutsche Bank do it and some other<00:07:36.550> banks<00:07:36.760> in<00:07:36.970> other<00:07:37.060> countries<00:07:37.479> so<00:07:37.599> we<00:07:37.720> had 00:07:37.860 --> 00:07:37.870 align:start position:0% other banks in other countries so we had 00:07:37.870 --> 00:07:40.320 align:start position:0% other banks in other countries so we had the<00:07:38.560> Deutsche<00:07:39.010> marks<00:07:39.520> and<00:07:39.760> Australian 00:07:40.320 --> 00:07:40.330 align:start position:0% the Deutsche marks and Australian 00:07:40.330 --> 00:07:42.360 align:start position:0% the Deutsche marks and Australian dollars<00:07:40.630> u.s.<00:07:40.930> dollars<00:07:41.320> as<00:07:41.440> one<00:07:41.590> and<00:07:41.800> here<00:07:42.250> in 00:07:42.360 --> 00:07:42.370 align:start position:0% dollars u.s. dollars as one and here in 00:07:42.370 --> 00:07:45.480 align:start position:0% dollars u.s. dollars as one and here in Japan<00:07:42.840> Nomura<00:07:43.840> research<00:07:44.349> recently<00:07:45.280> was 00:07:45.480 --> 00:07:45.490 align:start position:0% Japan Nomura research recently was 00:07:45.490 --> 00:07:49.350 align:start position:0% Japan Nomura research recently was revealed<00:07:46.650> secretly<00:07:47.650> they<00:07:48.250> licensee<00:07:49.120> cash 00:07:49.350 --> 00:07:49.360 align:start position:0% revealed secretly they licensee cash 00:07:49.360 --> 00:07:51.300 align:start position:0% revealed secretly they licensee cash from<00:07:49.599> us<00:07:49.810> but<00:07:50.500> they<00:07:50.680> wouldn't<00:07:50.889> tell<00:07:51.070> us<00:07:51.099> what 00:07:51.300 --> 00:07:51.310 align:start position:0% from us but they wouldn't tell us what 00:07:51.310 --> 00:07:52.890 align:start position:0% from us but they wouldn't tell us what they<00:07:51.460> were<00:07:51.520> doing<00:07:51.880> with<00:07:52.000> it<00:07:52.150> all<00:07:52.330> their 00:07:52.890 --> 00:07:52.900 align:start position:0% they were doing with it all their 00:07:52.900 --> 00:07:54.719 align:start position:0% they were doing with it all their employees<00:07:53.470> were<00:07:53.650> allowed<00:07:53.770> to<00:07:53.979> use<00:07:54.370> it<00:07:54.580> and 00:07:54.719 --> 00:07:54.729 align:start position:0% employees were allowed to use it and 00:07:54.729 --> 00:07:57.510 align:start position:0% employees were allowed to use it and access<00:07:55.030> their<00:07:55.180> bank<00:07:55.510> accounts<00:07:56.050> and<00:07:56.139> buy<00:07:56.650> like 00:07:57.510 --> 00:07:57.520 align:start position:0% access their bank accounts and buy like 00:07:57.520 --> 00:07:59.430 align:start position:0% access their bank accounts and buy like numerous<00:07:57.849> swag<00:07:58.300> and<00:07:58.660> get<00:07:58.840> reimbursed<00:07:59.289> for 00:07:59.430 --> 00:07:59.440 align:start position:0% numerous swag and get reimbursed for 00:07:59.440 --> 00:08:02.040 align:start position:0% numerous swag and get reimbursed for travel<00:07:59.590> and<00:08:00.310> all<00:08:00.400> this<00:08:00.550> stuff<00:08:00.729> so<00:08:01.120> it<00:08:01.960> was 00:08:02.040 --> 00:08:02.050 align:start position:0% travel and all this stuff so it was 00:08:02.050 --> 00:08:03.899 align:start position:0% travel and all this stuff so it was actually<00:08:02.500> actually<00:08:02.590> used<00:08:03.039> here<00:08:03.250> in<00:08:03.340> Japan<00:08:03.699> but 00:08:03.899 --> 00:08:03.909 align:start position:0% actually actually used here in Japan but 00:08:03.909 --> 00:08:12.050 align:start position:0% actually actually used here in Japan but secretly<00:08:04.780> and<00:08:07.409> so<00:08:08.409> that<00:08:08.590> was<00:08:09.720> pretty<00:08:10.720> neat<00:08:10.960> but 00:08:12.050 --> 00:08:12.060 align:start position:0% secretly and so that was pretty neat but 00:08:12.060 --> 00:08:18.240 align:start position:0% secretly and so that was pretty neat but now<00:08:13.919> we<00:08:14.919> are<00:08:15.280> in<00:08:16.270> a<00:08:17.080> world<00:08:17.320> where<00:08:17.740> everyone<00:08:18.099> has 00:08:18.240 --> 00:08:18.250 align:start position:0% now we are in a world where everyone has 00:08:18.250 --> 00:08:26.159 align:start position:0% now we are in a world where everyone has smartphones<00:08:19.000> and<00:08:22.590> the<00:08:23.590> killer<00:08:23.889> app<00:08:24.990> it's<00:08:25.990> kind 00:08:26.159 --> 00:08:26.169 align:start position:0% smartphones and the killer app it's kind 00:08:26.169 --> 00:08:28.469 align:start position:0% smartphones and the killer app it's kind of<00:08:26.260> a<00:08:26.349> sick<00:08:26.949> joke<00:08:26.979> but<00:08:27.460> it's<00:08:27.550> like<00:08:27.820> is<00:08:28.090> is 00:08:28.469 --> 00:08:28.479 align:start position:0% of a sick joke but it's like is is 00:08:28.479 --> 00:08:33.120 align:start position:0% of a sick joke but it's like is is WeChat<00:08:29.159> right<00:08:30.159> so<00:08:31.110> they<00:08:32.110> don't<00:08:32.229> see<00:08:32.349> the<00:08:32.500> humor 00:08:33.120 --> 00:08:33.130 align:start position:0% WeChat right so they don't see the humor 00:08:33.130 --> 00:08:35.610 align:start position:0% WeChat right so they don't see the humor in<00:08:33.190> that<00:08:33.279> no<00:08:33.669> okay<00:08:34.570> some<00:08:35.110> people<00:08:35.140> get<00:08:35.500> it 00:08:35.610 --> 00:08:35.620 align:start position:0% in that no okay some people get it 00:08:35.620 --> 00:08:38.310 align:start position:0% in that no okay some people get it anyways<00:08:36.539> have<00:08:37.539> to<00:08:37.690> live<00:08:37.839> there<00:08:38.020> to<00:08:38.050> really 00:08:38.310 --> 00:08:38.320 align:start position:0% anyways have to live there to really 00:08:38.320 --> 00:08:42.870 align:start position:0% anyways have to live there to really appreciate<00:08:38.830> it<00:08:38.950> so<00:08:41.430> this<00:08:42.430> is<00:08:42.610> sort<00:08:42.789> of 00:08:42.870 --> 00:08:42.880 align:start position:0% appreciate it so this is sort of 00:08:42.880 --> 00:08:44.880 align:start position:0% appreciate it so this is sort of indisputable<00:08:43.450> because<00:08:43.990> all<00:08:44.169> the<00:08:44.440> major 00:08:44.880 --> 00:08:44.890 align:start position:0% indisputable because all the major 00:08:44.890 --> 00:08:47.699 align:start position:0% indisputable because all the major social<00:08:45.420> media<00:08:46.420> messaging<00:08:47.140> systems<00:08:47.589> are 00:08:47.699 --> 00:08:47.709 align:start position:0% social media messaging systems are 00:08:47.709 --> 00:08:50.550 align:start position:0% social media messaging systems are moving<00:08:48.160> towards<00:08:48.720> payments<00:08:49.720> integrated<00:08:50.440> with 00:08:50.550 --> 00:08:50.560 align:start position:0% moving towards payments integrated with 00:08:50.560 --> 00:08:53.550 align:start position:0% moving towards payments integrated with messaging<00:08:51.570> because<00:08:52.570> that's<00:08:52.839> what<00:08:53.050> consumers 00:08:53.550 --> 00:08:53.560 align:start position:0% messaging because that's what consumers 00:08:53.560 --> 00:08:55.170 align:start position:0% messaging because that's what consumers want<00:08:53.650> they<00:08:54.010> want<00:08:54.160> those<00:08:54.430> two<00:08:54.670> in<00:08:54.880> the<00:08:54.970> same 00:08:55.170 --> 00:08:55.180 align:start position:0% want they want those two in the same 00:08:55.180 --> 00:08:57.510 align:start position:0% want they want those two in the same namespace<00:08:55.510> and<00:08:56.320> then<00:08:56.770> they<00:08:56.890> want<00:08:57.130> some<00:08:57.370> mini 00:08:57.510 --> 00:08:57.520 align:start position:0% namespace and then they want some mini 00:08:57.520 --> 00:08:58.290 align:start position:0% namespace and then they want some mini apps 00:08:58.290 --> 00:08:58.300 align:start position:0% apps 00:08:58.300 --> 00:09:00.900 align:start position:0% apps or<00:08:58.660> DAPs<00:08:58.930> in<00:08:59.710> that<00:09:00.010> same<00:09:00.250> namespace<00:09:00.730> the 00:09:00.900 --> 00:09:00.910 align:start position:0% or DAPs in that same namespace the 00:09:00.910 --> 00:09:03.720 align:start position:0% or DAPs in that same namespace the popular<00:09:01.360> ones<00:09:01.540> this<00:09:02.230> is<00:09:02.440> this<00:09:02.740> has<00:09:02.950> proven<00:09:03.610> to 00:09:03.720 --> 00:09:03.730 align:start position:0% popular ones this is this has proven to 00:09:03.730 --> 00:09:05.490 align:start position:0% popular ones this is this has proven to be<00:09:03.760> what<00:09:04.060> like<00:09:04.450> billions<00:09:04.780> of<00:09:04.930> people<00:09:05.230> actually 00:09:05.490 --> 00:09:05.500 align:start position:0% be what like billions of people actually 00:09:05.500 --> 00:09:10.170 align:start position:0% be what like billions of people actually want<00:09:06.040> so<00:09:06.760> what<00:09:07.030> we<00:09:07.240> need<00:09:07.480> to<00:09:07.510> do<00:09:08.020> here<00:09:08.680> is<00:09:09.180> to 00:09:10.170 --> 00:09:10.180 align:start position:0% want so what we need to do here is to 00:09:10.180 --> 00:09:13.950 align:start position:0% want so what we need to do here is to get<00:09:10.360> rid<00:09:10.570> of<00:09:10.600> this<00:09:10.870> giant<00:09:11.910> you<00:09:12.910> know<00:09:13.030> metadata 00:09:13.950 --> 00:09:13.960 align:start position:0% get rid of this giant you know metadata 00:09:13.960 --> 00:09:17.670 align:start position:0% get rid of this giant you know metadata capture<00:09:14.590> engine<00:09:15.100> is<00:09:15.370> create<00:09:16.270> a<00:09:16.680> replacement 00:09:17.670 --> 00:09:17.680 align:start position:0% capture engine is create a replacement 00:09:17.680 --> 00:09:20.670 align:start position:0% capture engine is create a replacement product<00:09:18.550> something<00:09:18.970> that<00:09:19.240> people<00:09:19.600> can<00:09:20.050> the 00:09:20.670 --> 00:09:20.680 align:start position:0% product something that people can the 00:09:20.680 --> 00:09:27.080 align:start position:0% product something that people can the ordinary<00:09:21.420> users<00:09:22.420> can<00:09:23.050> easily<00:09:23.430> just<00:09:24.540> switch<00:09:25.540> to 00:09:27.080 --> 00:09:27.090 align:start position:0% ordinary users can easily just switch to 00:09:27.090 --> 00:09:29.790 align:start position:0% ordinary users can easily just switch to that<00:09:28.090> does<00:09:28.360> the<00:09:28.510> same<00:09:28.540> stuff<00:09:29.140> for<00:09:29.350> them<00:09:29.500> on 00:09:29.790 --> 00:09:29.800 align:start position:0% that does the same stuff for them on 00:09:29.800 --> 00:09:33.060 align:start position:0% that does the same stuff for them on their<00:09:30.100> phone<00:09:30.340> as<00:09:30.670> say<00:09:31.210> a<00:09:31.240> WeChat<00:09:31.810> or<00:09:32.070> another 00:09:33.060 --> 00:09:33.070 align:start position:0% their phone as say a WeChat or another 00:09:33.070 --> 00:09:34.350 align:start position:0% their phone as say a WeChat or another messaging<00:09:33.550> platform<00:09:33.910> with<00:09:34.000> payments 00:09:34.350 --> 00:09:34.360 align:start position:0% messaging platform with payments 00:09:34.360 --> 00:09:38.160 align:start position:0% messaging platform with payments integrated<00:09:34.870> apps<00:09:35.620> and<00:09:36.340> but<00:09:37.150> that<00:09:37.180> is<00:09:37.450> based<00:09:37.780> on 00:09:38.160 --> 00:09:38.170 align:start position:0% integrated apps and but that is based on 00:09:38.170 --> 00:09:42.510 align:start position:0% integrated apps and but that is based on the<00:09:38.290> metadata<00:09:38.650> shredding<00:09:39.250> technology<00:09:41.520> so 00:09:42.510 --> 00:09:42.520 align:start position:0% the metadata shredding technology so 00:09:42.520 --> 00:09:45.150 align:start position:0% the metadata shredding technology so it'll<00:09:42.820> be<00:09:42.940> just<00:09:43.120> as<00:09:43.330> easy<00:09:43.510> to<00:09:43.780> use<00:09:44.020> and<00:09:44.500> work<00:09:44.950> in 00:09:45.150 --> 00:09:45.160 align:start position:0% it'll be just as easy to use and work in 00:09:45.160 --> 00:09:48.030 align:start position:0% it'll be just as easy to use and work in a<00:09:45.250> similar<00:09:45.640> way<00:09:45.670> but<00:09:46.180> the<00:09:46.930> metadata<00:09:47.410> will 00:09:48.030 --> 00:09:48.040 align:start position:0% a similar way but the metadata will 00:09:48.040 --> 00:09:50.190 align:start position:0% a similar way but the metadata will never<00:09:48.250> even<00:09:48.520> be<00:09:48.720> constituted<00:09:49.720> it<00:09:49.900> will<00:09:50.080> be 00:09:50.190 --> 00:09:50.200 align:start position:0% never even be constituted it will be 00:09:50.200 --> 00:09:53.730 align:start position:0% never even be constituted it will be shredded<00:09:50.890> in<00:09:51.130> real<00:09:51.790> time<00:09:52.150> in<00:09:52.540> its<00:09:52.990> distributed 00:09:53.730 --> 00:09:53.740 align:start position:0% shredded in real time in its distributed 00:09:53.740 --> 00:09:57.240 align:start position:0% shredded in real time in its distributed form<00:09:54.040> before<00:09:54.490> it's<00:09:54.810> actually<00:09:55.810> able<00:09:56.320> to<00:09:56.500> be 00:09:57.240 --> 00:09:57.250 align:start position:0% form before it's actually able to be 00:09:57.250 --> 00:10:02.870 align:start position:0% form before it's actually able to be abuse<00:09:57.700> in<00:09:57.910> any<00:09:58.060> way<00:10:00.990> however<00:10:01.990> the<00:10:02.650> the 00:10:02.870 --> 00:10:02.880 align:start position:0% abuse in any way however the the 00:10:02.880 --> 00:10:04.650 align:start position:0% abuse in any way however the the technologies<00:10:03.880> that<00:10:03.910> I<00:10:04.090> showed<00:10:04.360> you<00:10:04.450> that<00:10:04.510> I 00:10:04.650 --> 00:10:04.660 align:start position:0% technologies that I showed you that I 00:10:04.660 --> 00:10:06.840 align:start position:0% technologies that I showed you that I developed<00:10:05.080> the<00:10:05.170> ATS<00:10:05.620> and<00:10:05.890> we<00:10:06.010> implemented<00:10:06.790> in 00:10:06.840 --> 00:10:06.850 align:start position:0% developed the ATS and we implemented in 00:10:06.850 --> 00:10:10.410 align:start position:0% developed the ATS and we implemented in the<00:10:06.940> 90s<00:10:07.920> aren't<00:10:08.920> really<00:10:09.250> suitable<00:10:09.730> for<00:10:09.940> like 00:10:10.410 --> 00:10:10.420 align:start position:0% the 90s aren't really suitable for like 00:10:10.420 --> 00:10:12.540 align:start position:0% the 90s aren't really suitable for like smartphone<00:10:11.020> to<00:10:11.230> smartphone<00:10:11.680> transactions 00:10:12.540 --> 00:10:12.550 align:start position:0% smartphone to smartphone transactions 00:10:12.550 --> 00:10:14.820 align:start position:0% smartphone to smartphone transactions there's<00:10:12.820> their<00:10:13.660> performance<00:10:14.470> and<00:10:14.740> other 00:10:14.820 --> 00:10:14.830 align:start position:0% there's their performance and other 00:10:14.830 --> 00:10:18.180 align:start position:0% there's their performance and other issues<00:10:15.130> and<00:10:16.170> especially<00:10:17.170> when<00:10:17.530> it's<00:10:17.680> used<00:10:18.040> in 00:10:18.180 --> 00:10:18.190 align:start position:0% issues and especially when it's used in 00:10:18.190 --> 00:10:20.460 align:start position:0% issues and especially when it's used in a<00:10:18.250> mass<00:10:18.460> scale<00:10:18.820> and<00:10:19.090> because<00:10:19.360> of<00:10:19.390> the<00:10:19.660> kind<00:10:20.350> of 00:10:20.460 --> 00:10:20.470 align:start position:0% a mass scale and because of the kind of 00:10:20.470 --> 00:10:23.430 align:start position:0% a mass scale and because of the kind of speed<00:10:20.860> of<00:10:21.420> transaction<00:10:22.420> Layton<00:10:23.020> sees<00:10:23.230> that 00:10:23.430 --> 00:10:23.440 align:start position:0% speed of transaction Layton sees that 00:10:23.440 --> 00:10:24.960 align:start position:0% speed of transaction Layton sees that consumers<00:10:24.040> are<00:10:24.190> familiar<00:10:24.670> with<00:10:24.820> the 00:10:24.960 --> 00:10:24.970 align:start position:0% consumers are familiar with the 00:10:24.970 --> 00:10:27.870 align:start position:0% consumers are familiar with the messaging<00:10:25.570> today<00:10:26.350> something<00:10:27.160> some<00:10:27.700> real 00:10:27.870 --> 00:10:27.880 align:start position:0% messaging today something some real 00:10:27.880 --> 00:10:31.170 align:start position:0% messaging today something some real breakthroughs<00:10:28.420> are<00:10:28.570> needed<00:10:28.990> and<00:10:29.740> so<00:10:30.640> I<00:10:30.670> was 00:10:31.170 --> 00:10:31.180 align:start position:0% breakthroughs are needed and so I was 00:10:31.180 --> 00:10:35.070 align:start position:0% breakthroughs are needed and so I was not<00:10:32.850> really<00:10:33.850> working<00:10:34.000> on<00:10:34.270> this<00:10:34.450> stuff<00:10:34.750> when 00:10:35.070 --> 00:10:35.080 align:start position:0% not really working on this stuff when 00:10:35.080 --> 00:10:38.280 align:start position:0% not really working on this stuff when the<00:10:35.290> Snowden<00:10:35.740> revelations<00:10:35.770> came<00:10:36.700> out<00:10:36.940> and<00:10:37.600> and 00:10:38.280 --> 00:10:38.290 align:start position:0% the Snowden revelations came out and and 00:10:38.290 --> 00:10:43.350 align:start position:0% the Snowden revelations came out and and then<00:10:38.920> I<00:10:38.950> was<00:10:40.020> so<00:10:41.020> shocked<00:10:41.470> and<00:10:42.280> I<00:10:42.910> went<00:10:43.090> back<00:10:43.330> to 00:10:43.350 --> 00:10:43.360 align:start position:0% then I was so shocked and I went back to 00:10:43.360 --> 00:10:46.350 align:start position:0% then I was so shocked and I went back to the<00:10:43.840> you<00:10:44.200> know<00:10:44.320> those<00:10:45.040> crypto<00:10:45.790> conferences 00:10:46.350 --> 00:10:46.360 align:start position:0% the you know those crypto conferences 00:10:46.360 --> 00:10:48.900 align:start position:0% the you know those crypto conferences that<00:10:46.540> I<00:10:46.570> founded<00:10:47.320> and<00:10:47.680> talked<00:10:48.520> to<00:10:48.640> a<00:10:48.700> lot<00:10:48.850> of 00:10:48.900 --> 00:10:48.910 align:start position:0% that I founded and talked to a lot of 00:10:48.910 --> 00:10:51.990 align:start position:0% that I founded and talked to a lot of people<00:10:49.330> there<00:10:49.510> and<00:10:49.540> I<00:10:49.960> was<00:10:50.140> really<00:10:51.000> quite 00:10:51.990 --> 00:10:52.000 align:start position:0% people there and I was really quite 00:10:52.000 --> 00:10:55.790 align:start position:0% people there and I was really quite became<00:10:52.570> quite<00:10:53.050> concerned<00:10:53.680> because<00:10:54.190> it<00:10:54.400> was 00:10:55.790 --> 00:10:55.800 align:start position:0% became quite concerned because it was 00:10:55.800 --> 00:10:57.720 align:start position:0% became quite concerned because it was surprising<00:10:56.800> that<00:10:56.830> they<00:10:57.130> were<00:10:57.190> much<00:10:57.490> more 00:10:57.720 --> 00:10:57.730 align:start position:0% surprising that they were much more 00:10:57.730 --> 00:10:59.820 align:start position:0% surprising that they were much more interested<00:10:57.790> in<00:10:58.450> their<00:10:58.630> jobs<00:10:59.140> and<00:10:59.710> in 00:10:59.820 --> 00:10:59.830 align:start position:0% interested in their jobs and in 00:10:59.830 --> 00:11:02.700 align:start position:0% interested in their jobs and in publications<00:11:00.550> and<00:11:01.450> all<00:11:02.050> this<00:11:02.260> and<00:11:02.590> even 00:11:02.700 --> 00:11:02.710 align:start position:0% publications and all this and even 00:11:02.710 --> 00:11:04.170 align:start position:0% publications and all this and even though<00:11:02.920> they<00:11:03.100> said<00:11:03.460> they<00:11:03.700> were<00:11:03.820> there<00:11:03.970> to 00:11:04.170 --> 00:11:04.180 align:start position:0% though they said they were there to 00:11:04.180 --> 00:11:06.540 align:start position:0% though they said they were there to protect<00:11:04.360> you<00:11:05.140> know<00:11:05.260> people<00:11:05.800> from<00:11:05.980> whatever 00:11:06.540 --> 00:11:06.550 align:start position:0% protect you know people from whatever 00:11:06.550 --> 00:11:09.750 align:start position:0% protect you know people from whatever abuse<00:11:07.090> of<00:11:07.240> cryptography<00:11:08.050> they<00:11:08.770> if<00:11:09.070> no<00:11:09.490> one<00:11:09.640> was 00:11:09.750 --> 00:11:09.760 align:start position:0% abuse of cryptography they if no one was 00:11:09.760 --> 00:11:11.790 align:start position:0% abuse of cryptography they if no one was really<00:11:10.470> that 00:11:11.790 --> 00:11:11.800 align:start position:0% really that 00:11:11.800 --> 00:11:14.460 align:start position:0% really that influenced<00:11:12.279> by<00:11:12.370> the<00:11:12.640> stone<00:11:13.290> revelations<00:11:14.290> and 00:11:14.460 --> 00:11:14.470 align:start position:0% influenced by the stone revelations and 00:11:14.470 --> 00:11:18.030 align:start position:0% influenced by the stone revelations and up<00:11:14.589> but<00:11:14.800> I<00:11:14.830> was<00:11:15.160> and<00:11:15.850> so<00:11:16.720> I<00:11:16.750> took<00:11:17.649> it<00:11:17.769> upon 00:11:18.030 --> 00:11:18.040 align:start position:0% up but I was and so I took it upon 00:11:18.040 --> 00:11:20.699 align:start position:0% up but I was and so I took it upon myself<00:11:18.070> to<00:11:18.550> speed<00:11:19.000> up<00:11:19.180> the<00:11:19.360> mixing<00:11:19.839> because 00:11:20.699 --> 00:11:20.709 align:start position:0% myself to speed up the mixing because 00:11:20.709 --> 00:11:23.130 align:start position:0% myself to speed up the mixing because it's<00:11:20.980> pretty<00:11:21.370> cumbersome<00:11:22.000> and<00:11:22.149> slow<00:11:22.480> and<00:11:22.779> I 00:11:23.130 --> 00:11:23.140 align:start position:0% it's pretty cumbersome and slow and I 00:11:23.140 --> 00:11:26.370 align:start position:0% it's pretty cumbersome and slow and I found<00:11:23.440> a<00:11:23.620> way<00:11:23.769> to<00:11:24.330> speed<00:11:25.330> it<00:11:25.480> up<00:11:25.600> by<00:11:25.779> over<00:11:26.050> by<00:11:26.350> a 00:11:26.370 --> 00:11:26.380 align:start position:0% found a way to speed it up by over by a 00:11:26.380 --> 00:11:27.990 align:start position:0% found a way to speed it up by over by a factor<00:11:26.890> of<00:11:26.920> a<00:11:27.100> thousand 00:11:27.990 --> 00:11:28.000 align:start position:0% factor of a thousand 00:11:28.000 --> 00:11:31.800 align:start position:0% factor of a thousand I<00:11:28.029> took<00:11:28.720> some<00:11:29.050> real<00:11:29.260> work<00:11:29.529> and<00:11:30.060> no<00:11:31.060> one<00:11:31.269> since<00:11:31.630> I 00:11:31.800 --> 00:11:31.810 align:start position:0% I took some real work and no one since I 00:11:31.810 --> 00:11:34.829 align:start position:0% I took some real work and no one since I published<00:11:32.290> it<00:11:32.500> in<00:11:32.880> 79<00:11:33.880> is<00:11:34.089> a<00:11:34.120> type<00:11:34.360> of<00:11:34.390> reported 00:11:34.829 --> 00:11:34.839 align:start position:0% published it in 79 is a type of reported 00:11:34.839 --> 00:11:38.340 align:start position:0% published it in 79 is a type of reported with<00:11:34.930> CAC<00:11:35.230> m82<00:11:35.950> no<00:11:36.940> one<00:11:37.149> actually<00:11:37.390> ever<00:11:37.810> found 00:11:38.340 --> 00:11:38.350 align:start position:0% with CAC m82 no one actually ever found 00:11:38.350 --> 00:11:39.900 align:start position:0% with CAC m82 no one actually ever found a<00:11:38.470> way<00:11:38.589> to<00:11:38.620> speed<00:11:38.980> it<00:11:39.100> up<00:11:39.250> even<00:11:39.430> though<00:11:39.700> there's 00:11:39.900 --> 00:11:39.910 align:start position:0% a way to speed it up even though there's 00:11:39.910 --> 00:11:42.030 align:start position:0% a way to speed it up even though there's thousands<00:11:40.390> of<00:11:40.480> references<00:11:40.720> and<00:11:41.260> bunches<00:11:41.620> as<00:11:41.920> a 00:11:42.030 --> 00:11:42.040 align:start position:0% thousands of references and bunches as a 00:11:42.040 --> 00:11:43.800 align:start position:0% thousands of references and bunches as a conference<00:11:42.490> every<00:11:42.640> year<00:11:42.790> that's<00:11:43.060> mainly<00:11:43.360> used 00:11:43.800 --> 00:11:43.810 align:start position:0% conference every year that's mainly used 00:11:43.810 --> 00:11:47.280 align:start position:0% conference every year that's mainly used to<00:11:43.930> be<00:11:44.019> mainly<00:11:44.230> about<00:11:44.620> it<00:11:44.860> and<00:11:45.750> so<00:11:46.750> the<00:11:47.140> only 00:11:47.280 --> 00:11:47.290 align:start position:0% to be mainly about it and so the only 00:11:47.290 --> 00:11:49.319 align:start position:0% to be mainly about it and so the only speed-up<00:11:47.829> that<00:11:47.860> occurred<00:11:48.310> was<00:11:48.490> when<00:11:48.850> someone 00:11:49.319 --> 00:11:49.329 align:start position:0% speed-up that occurred was when someone 00:11:49.329 --> 00:11:51.600 align:start position:0% speed-up that occurred was when someone substitute<00:11:49.839> el-gamal<00:11:50.170> for<00:11:50.680> which<00:11:51.220> came<00:11:51.490> out 00:11:51.600 --> 00:11:51.610 align:start position:0% substitute el-gamal for which came out 00:11:51.610 --> 00:11:54.230 align:start position:0% substitute el-gamal for which came out four<00:11:51.850> years<00:11:52.029> after<00:11:52.209> I<00:11:52.420> published<00:11:52.690> it<00:11:53.019> for<00:11:53.980> the 00:11:54.230 --> 00:11:54.240 align:start position:0% four years after I published it for the 00:11:54.240 --> 00:11:57.660 align:start position:0% four years after I published it for the RSA<00:11:55.240> kind<00:11:55.510> of<00:11:55.600> crypto<00:11:56.050> but<00:11:56.200> I<00:11:56.230> had<00:11:56.410> defined<00:11:57.279> it 00:11:57.660 --> 00:11:57.670 align:start position:0% RSA kind of crypto but I had defined it 00:11:57.670 --> 00:11:59.670 align:start position:0% RSA kind of crypto but I had defined it in<00:11:57.850> a<00:11:57.910> way<00:11:58.060> that<00:11:58.089> the<00:11:58.630> RSA<00:11:59.200> was<00:11:59.350> just<00:11:59.529> an 00:11:59.670 --> 00:11:59.680 align:start position:0% in a way that the RSA was just an 00:11:59.680 --> 00:12:04.470 align:start position:0% in a way that the RSA was just an example<00:12:00.040> so<00:12:01.890> anyway<00:12:02.890> so<00:12:02.950> let<00:12:03.610> me<00:12:03.730> show<00:12:04.450> you 00:12:04.470 --> 00:12:04.480 align:start position:0% example so anyway so let me show you 00:12:04.480 --> 00:12:06.620 align:start position:0% example so anyway so let me show you some<00:12:04.779> of<00:12:04.870> these<00:12:04.930> breakthroughs<00:12:05.290> now<00:12:05.800> that<00:12:06.070> are 00:12:06.620 --> 00:12:06.630 align:start position:0% some of these breakthroughs now that are 00:12:06.630 --> 00:12:11.100 align:start position:0% some of these breakthroughs now that are enabling<00:12:07.630> us<00:12:08.070> to<00:12:09.070> do<00:12:10.029> exactly<00:12:10.300> what<00:12:10.810> I'm 00:12:11.100 --> 00:12:11.110 align:start position:0% enabling us to do exactly what I'm 00:12:11.110 --> 00:12:12.990 align:start position:0% enabling us to do exactly what I'm saying<00:12:11.470> if<00:12:11.829> we<00:12:12.250> pull<00:12:12.490> together<00:12:12.640> as<00:12:12.970> a 00:12:12.990 --> 00:12:13.000 align:start position:0% saying if we pull together as a 00:12:13.000 --> 00:12:16.340 align:start position:0% saying if we pull together as a community<00:12:13.269> we<00:12:13.750> can<00:12:14.589> create<00:12:15.190> a<00:12:15.640> replacement 00:12:16.340 --> 00:12:16.350 align:start position:0% community we can create a replacement 00:12:16.350 --> 00:12:19.590 align:start position:0% community we can create a replacement product<00:12:17.350> for<00:12:17.920> all<00:12:18.220> of<00:12:18.370> these<00:12:18.490> messaging<00:12:19.420> and 00:12:19.590 --> 00:12:19.600 align:start position:0% product for all of these messaging and 00:12:19.600 --> 00:12:23.430 align:start position:0% product for all of these messaging and and<00:12:20.230> combined<00:12:20.920> with<00:12:20.950> payment<00:12:21.430> systems<00:12:21.820> so<00:12:22.440> we 00:12:23.430 --> 00:12:23.440 align:start position:0% and combined with payment systems so we 00:12:23.440 --> 00:12:26.579 align:start position:0% and combined with payment systems so we actually<00:12:23.860> I<00:12:24.399> have<00:12:24.610> to<00:12:24.760> say<00:12:25.200> some<00:12:26.200> of<00:12:26.230> you<00:12:26.440> may 00:12:26.579 --> 00:12:26.589 align:start position:0% actually I have to say some of you may 00:12:26.589 --> 00:12:30.680 align:start position:0% actually I have to say some of you may have<00:12:26.740> heard<00:12:27.430> of<00:12:27.579> a<00:12:27.670> lick<00:12:27.850> sir<00:12:28.120> that's<00:12:28.779> the<00:12:29.770> are 00:12:30.680 --> 00:12:30.690 align:start position:0% have heard of a lick sir that's the are 00:12:30.690 --> 00:12:33.780 align:start position:0% have heard of a lick sir that's the are the<00:12:31.690> high<00:12:31.810> speed<00:12:32.050> mixing<00:12:32.470> technology<00:12:33.459> which 00:12:33.780 --> 00:12:33.790 align:start position:0% the high speed mixing technology which 00:12:33.790 --> 00:12:36.449 align:start position:0% the high speed mixing technology which is<00:12:33.970> is<00:12:34.209> actually<00:12:35.140> running<00:12:35.380> in<00:12:35.620> an<00:12:35.860> open<00:12:36.160> alpha 00:12:36.449 --> 00:12:36.459 align:start position:0% is is actually running in an open alpha 00:12:36.459 --> 00:12:37.710 align:start position:0% is is actually running in an open alpha and<00:12:36.579> we'll<00:12:36.760> see<00:12:37.089> that<00:12:37.209> something<00:12:37.480> about<00:12:37.540> that 00:12:37.710 --> 00:12:37.720 align:start position:0% and we'll see that something about that 00:12:37.720 --> 00:12:41.370 align:start position:0% and we'll see that something about that shortly<00:12:38.529> and<00:12:38.890> then<00:12:39.579> we<00:12:40.120> have<00:12:40.300> praxis<00:12:40.899> which<00:12:41.230> is 00:12:41.370 --> 00:12:41.380 align:start position:0% shortly and then we have praxis which is 00:12:41.380 --> 00:12:45.110 align:start position:0% shortly and then we have praxis which is our<00:12:41.560> new<00:12:41.760> very<00:12:42.760> different<00:12:43.420> quantum<00:12:44.410> resistant 00:12:45.110 --> 00:12:45.120 align:start position:0% our new very different quantum resistant 00:12:45.120 --> 00:12:47.699 align:start position:0% our new very different quantum resistant consensus<00:12:46.120> and<00:12:46.270> payments<00:12:46.810> technology<00:12:47.440> and 00:12:47.699 --> 00:12:47.709 align:start position:0% consensus and payments technology and 00:12:47.709 --> 00:12:50.040 align:start position:0% consensus and payments technology and these<00:12:48.190> are<00:12:48.370> sister<00:12:48.730> companies<00:12:49.300> and<00:12:49.570> when<00:12:49.959> you 00:12:50.040 --> 00:12:50.050 align:start position:0% these are sister companies and when you 00:12:50.050 --> 00:12:51.990 align:start position:0% these are sister companies and when you combine<00:12:50.470> them<00:12:50.709> you<00:12:50.770> get<00:12:51.070> this<00:12:51.490> kind<00:12:51.790> of<00:12:51.850> app 00:12:51.990 --> 00:12:52.000 align:start position:0% combine them you get this kind of app 00:12:52.000 --> 00:12:55.439 align:start position:0% combine them you get this kind of app that<00:12:52.209> I'm<00:12:52.329> talking<00:12:52.750> about<00:12:53.020> so<00:12:54.010> let<00:12:54.790> me<00:12:54.820> just 00:12:55.439 --> 00:12:55.449 align:start position:0% that I'm talking about so let me just 00:12:55.449 --> 00:12:57.660 align:start position:0% that I'm talking about so let me just now<00:12:55.690> show<00:12:56.020> you<00:12:56.079> a<00:12:56.260> little<00:12:56.440> bit<00:12:56.529> about<00:12:56.800> the<00:12:57.010> the 00:12:57.660 --> 00:12:57.670 align:start position:0% now show you a little bit about the the 00:12:57.670 --> 00:13:01.889 align:start position:0% now show you a little bit about the the new<00:12:57.880> approach<00:12:58.810> in<00:12:59.050> a<00:12:59.140> in<00:12:59.709> a<00:13:00.130> simplified<00:13:00.899> kind 00:13:01.889 --> 00:13:01.899 align:start position:0% new approach in a in a simplified kind 00:13:01.899 --> 00:13:08.519 align:start position:0% new approach in a in a simplified kind of<00:13:02.020> amusing<00:13:02.529> manner<00:13:06.630> suppose<00:13:07.630> Alice<00:13:08.110> wants<00:13:08.500> to 00:13:08.519 --> 00:13:08.529 align:start position:0% of amusing manner suppose Alice wants to 00:13:08.529 --> 00:13:11.069 align:start position:0% of amusing manner suppose Alice wants to send<00:13:08.709> a<00:13:08.800> message<00:13:09.100> to<00:13:09.130> Bob<00:13:09.279> but<00:13:10.149> she<00:13:10.690> doesn't 00:13:11.069 --> 00:13:11.079 align:start position:0% send a message to Bob but she doesn't 00:13:11.079 --> 00:13:13.079 align:start position:0% send a message to Bob but she doesn't want<00:13:11.230> anyone<00:13:11.589> to<00:13:11.740> know<00:13:12.070> that<00:13:12.370> the<00:13:12.640> two<00:13:12.790> of<00:13:12.820> them 00:13:13.079 --> 00:13:13.089 align:start position:0% want anyone to know that the two of them 00:13:13.089 --> 00:13:16.079 align:start position:0% want anyone to know that the two of them are<00:13:13.329> communicating<00:13:14.320> message<00:13:14.920> content<00:13:15.730> can 00:13:16.079 --> 00:13:16.089 align:start position:0% are communicating message content can 00:13:16.089 --> 00:13:18.030 align:start position:0% are communicating message content can easily<00:13:16.750> be<00:13:16.870> protected<00:13:17.440> by<00:13:17.560> so-called 00:13:18.030 --> 00:13:18.040 align:start position:0% easily be protected by so-called 00:13:18.040 --> 00:13:20.280 align:start position:0% easily be protected by so-called end-to-end<00:13:18.519> encryption<00:13:19.029> but<00:13:19.449> this<00:13:19.690> does<00:13:20.020> not 00:13:20.280 --> 00:13:20.290 align:start position:0% end-to-end encryption but this does not 00:13:20.290 --> 00:13:21.180 align:start position:0% end-to-end encryption but this does not protect 00:13:21.180 --> 00:13:21.190 align:start position:0% protect 00:13:21.190 --> 00:13:23.190 align:start position:0% protect information<00:13:21.700> about<00:13:21.820> who's<00:13:22.300> talking<00:13:22.870> to<00:13:22.960> whom 00:13:23.190 --> 00:13:23.200 align:start position:0% information about who's talking to whom 00:13:23.200 --> 00:13:25.260 align:start position:0% information about who's talking to whom and<00:13:23.530> when<00:13:23.770> the<00:13:24.190> metadata<00:13:24.700> which<00:13:25.120> is 00:13:25.260 --> 00:13:25.270 align:start position:0% and when the metadata which is 00:13:25.270 --> 00:13:27.450 align:start position:0% and when the metadata which is increasingly<00:13:25.840> recognized<00:13:26.500> as<00:13:26.860> far<00:13:27.310> more 00:13:27.450 --> 00:13:27.460 align:start position:0% increasingly recognized as far more 00:13:27.460 --> 00:13:29.760 align:start position:0% increasingly recognized as far more revealing<00:13:27.850> and<00:13:28.270> more<00:13:28.960> challenging<00:13:29.620> to 00:13:29.760 --> 00:13:29.770 align:start position:0% revealing and more challenging to 00:13:29.770 --> 00:13:32.310 align:start position:0% revealing and more challenging to protect<00:13:30.190> each<00:13:30.610> member<00:13:31.270> of<00:13:31.300> a<00:13:31.660> team<00:13:31.900> of<00:13:32.080> nodes 00:13:32.310 --> 00:13:32.320 align:start position:0% protect each member of a team of nodes 00:13:32.320 --> 00:13:34.790 align:start position:0% protect each member of a team of nodes in<00:13:32.770> order<00:13:33.250> to<00:13:33.400> protect<00:13:33.640> the<00:13:34.270> metadata 00:13:34.790 --> 00:13:34.800 align:start position:0% in order to protect the metadata 00:13:34.800 --> 00:13:37.170 align:start position:0% in order to protect the metadata successively<00:13:35.800> shuffles<00:13:36.460> the<00:13:36.640> batch<00:13:36.850> of 00:13:37.170 --> 00:13:37.180 align:start position:0% successively shuffles the batch of 00:13:37.180 --> 00:13:39.420 align:start position:0% successively shuffles the batch of encrypted<00:13:37.660> messages<00:13:38.200> using<00:13:38.650> its<00:13:38.950> container 00:13:39.420 --> 00:13:39.430 align:start position:0% encrypted messages using its container 00:13:39.430 --> 00:13:41.910 align:start position:0% encrypted messages using its container of<00:13:39.670> secretly<00:13:40.030> arranged<00:13:40.570> tubes<00:13:40.870> and<00:13:41.260> sending 00:13:41.910 --> 00:13:41.920 align:start position:0% of secretly arranged tubes and sending 00:13:41.920 --> 00:13:44.010 align:start position:0% of secretly arranged tubes and sending the<00:13:42.010> messages<00:13:42.490> without<00:13:42.760> delay<00:13:43.180> through<00:13:43.720> to 00:13:44.010 --> 00:13:44.020 align:start position:0% the messages without delay through to 00:13:44.020 --> 00:13:46.230 align:start position:0% the messages without delay through to the<00:13:44.140> next<00:13:44.380> team<00:13:44.620> member<00:13:45.010> even<00:13:45.550> just<00:13:45.820> a<00:13:46.000> single 00:13:46.230 --> 00:13:46.240 align:start position:0% the next team member even just a single 00:13:46.240 --> 00:13:48.720 align:start position:0% the next team member even just a single node<00:13:46.570> can<00:13:47.020> keep<00:13:47.230> senders<00:13:47.770> from<00:13:48.100> being<00:13:48.310> linked 00:13:48.720 --> 00:13:48.730 align:start position:0% node can keep senders from being linked 00:13:48.730 --> 00:13:54.210 align:start position:0% node can keep senders from being linked to<00:13:48.910> recipients<00:13:52.140> Alice<00:13:53.140> also<00:13:53.440> gets<00:13:53.680> a<00:13:53.770> receipt 00:13:54.210 --> 00:13:54.220 align:start position:0% to recipients Alice also gets a receipt 00:13:54.220 --> 00:13:56.460 align:start position:0% to recipients Alice also gets a receipt informing<00:13:55.030> her<00:13:55.120> confidentially<00:13:55.960> that<00:13:56.140> her 00:13:56.460 --> 00:13:56.470 align:start position:0% informing her confidentially that her 00:13:56.470 --> 00:13:58.830 align:start position:0% informing her confidentially that her message<00:13:56.680> was<00:13:56.890> provided<00:13:57.610> to<00:13:57.730> bomb<00:13:57.910> team 00:13:58.830 --> 00:13:58.840 align:start position:0% message was provided to bomb team 00:13:58.840 --> 00:14:00.690 align:start position:0% message was provided to bomb team members<00:13:59.200> that<00:13:59.380> destroy<00:13:59.950> their<00:14:00.310> secret 00:14:00.690 --> 00:14:00.700 align:start position:0% members that destroy their secret 00:14:00.700 --> 00:14:02.610 align:start position:0% members that destroy their secret pattern<00:14:01.060> of<00:14:01.210> tubes<00:14:01.480> making<00:14:02.050> way<00:14:02.320> for<00:14:02.350> a<00:14:02.590> new 00:14:02.610 --> 00:14:02.620 align:start position:0% pattern of tubes making way for a new 00:14:02.620 --> 00:14:05.820 align:start position:0% pattern of tubes making way for a new team<00:14:03.070> ready<00:14:03.550> for<00:14:03.760> a<00:14:03.790> new<00:14:04.000> batch<00:14:04.380> earlier<00:14:05.380> each 00:14:05.820 --> 00:14:05.830 align:start position:0% team ready for a new batch earlier each 00:14:05.830 --> 00:14:08.340 align:start position:0% team ready for a new batch earlier each node<00:14:06.280> is<00:14:06.550> chosen<00:14:06.970> independently<00:14:07.240> as<00:14:07.930> a<00:14:07.990> kind 00:14:08.340 --> 00:14:08.350 align:start position:0% node is chosen independently as a kind 00:14:08.350 --> 00:14:10.890 align:start position:0% node is chosen independently as a kind of<00:14:08.440> random<00:14:08.710> secret<00:14:09.310> gene<00:14:09.580> which<00:14:10.120> input<00:14:10.690> tube 00:14:10.890 --> 00:14:10.900 align:start position:0% of random secret gene which input tube 00:14:10.900 --> 00:14:13.680 align:start position:0% of random secret gene which input tube to<00:14:11.200> connect<00:14:11.530> to<00:14:11.710> which<00:14:11.890> output<00:14:12.490> tube<00:14:12.730> elixirs 00:14:13.680 --> 00:14:13.690 align:start position:0% to connect to which output tube elixirs 00:14:13.690 --> 00:14:15.900 align:start position:0% to connect to which output tube elixirs break<00:14:14.080> through<00:14:14.470> over<00:14:15.010> the<00:14:15.100> type<00:14:15.310> of<00:14:15.340> messaging 00:14:15.900 --> 00:14:15.910 align:start position:0% break through over the type of messaging 00:14:15.910 --> 00:14:17.850 align:start position:0% break through over the type of messaging and<00:14:16.000> I<00:14:16.060> open<00:14:16.330> sourced<00:14:16.630> in<00:14:16.750> the<00:14:16.840> ATS<00:14:17.260> is<00:14:17.470> a<00:14:17.560> way 00:14:17.850 --> 00:14:17.860 align:start position:0% and I open sourced in the ATS is a way 00:14:17.860 --> 00:14:20.100 align:start position:0% and I open sourced in the ATS is a way that<00:14:18.070> enables<00:14:18.160> almost<00:14:18.700> all<00:14:18.970> the<00:14:19.330> work<00:14:19.540> to<00:14:19.960> be 00:14:20.100 --> 00:14:20.110 align:start position:0% that enables almost all the work to be 00:14:20.110 --> 00:14:23.310 align:start position:0% that enables almost all the work to be done<00:14:20.320> well<00:14:20.950> in<00:14:21.220> advance<00:14:21.730> yielding<00:14:22.630> the<00:14:22.750> only 00:14:23.310 --> 00:14:23.320 align:start position:0% done well in advance yielding the only 00:14:23.320 --> 00:14:26.280 align:start position:0% done well in advance yielding the only known<00:14:23.620> way<00:14:23.890> to<00:14:24.250> provide<00:14:24.580> real-time<00:14:25.290> metadata 00:14:26.280 --> 00:14:26.290 align:start position:0% known way to provide real-time metadata 00:14:26.290 --> 00:14:29.580 align:start position:0% known way to provide real-time metadata protection<00:14:26.980> smartphone<00:14:27.820> to<00:14:28.270> smartphone<00:14:28.840> lead 00:14:29.580 --> 00:14:29.590 align:start position:0% protection smartphone to smartphone lead 00:14:29.590 --> 00:14:32.220 align:start position:0% protection smartphone to smartphone lead can<00:14:29.830> also<00:14:29.980> pay<00:14:30.550> you<00:14:31.030> me<00:14:31.240> by<00:14:31.600> sending<00:14:31.840> what 00:14:32.220 --> 00:14:32.230 align:start position:0% can also pay you me by sending what 00:14:32.230 --> 00:14:34.020 align:start position:0% can also pay you me by sending what appears<00:14:32.560> to<00:14:32.680> be<00:14:32.770> an<00:14:32.860> ordinary<00:14:32.980> message<00:14:33.640> but 00:14:34.020 --> 00:14:34.030 align:start position:0% appears to be an ordinary message but 00:14:34.030 --> 00:14:35.940 align:start position:0% appears to be an ordinary message but that<00:14:34.150> actually<00:14:34.510> contains<00:14:34.930> numbers<00:14:35.320> that 00:14:35.940 --> 00:14:35.950 align:start position:0% that actually contains numbers that 00:14:35.950 --> 00:14:38.040 align:start position:0% that actually contains numbers that serve<00:14:36.280> like<00:14:36.640> dental<00:14:36.940> coins<00:14:37.210> and<00:14:37.450> paper<00:14:37.570> money 00:14:38.040 --> 00:14:38.050 align:start position:0% serve like dental coins and paper money 00:14:38.050 --> 00:14:40.590 align:start position:0% serve like dental coins and paper money I've<00:14:38.320> called<00:14:38.620> such<00:14:38.950> denominated<00:14:39.910> unforgeable 00:14:40.590 --> 00:14:40.600 align:start position:0% I've called such denominated unforgeable 00:14:40.600 --> 00:14:43.890 align:start position:0% I've called such denominated unforgeable numbers<00:14:41.440> digital<00:14:42.340> cash<00:14:42.700> first<00:14:43.330> issued<00:14:43.780> by 00:14:43.890 --> 00:14:43.900 align:start position:0% numbers digital cash first issued by 00:14:43.900 --> 00:14:46.080 align:start position:0% numbers digital cash first issued by digit<00:14:44.260> cash<00:14:44.440> in<00:14:44.680> 90s<00:14:45.190> illiteracy<00:14:45.820> rate 00:14:46.080 --> 00:14:46.090 align:start position:0% digit cash in 90s illiteracy rate 00:14:46.090 --> 00:14:47.460 align:start position:0% digit cash in 90s illiteracy rate through<00:14:46.330> improvement<00:14:46.930> on<00:14:47.080> the<00:14:47.380> original 00:14:47.460 --> 00:14:47.470 align:start position:0% through improvement on the original 00:14:47.470 --> 00:14:50.100 align:start position:0% through improvement on the original digital<00:14:48.280> cash<00:14:48.550> now<00:14:49.180> makes<00:14:49.570> it<00:14:49.750> fully 00:14:50.100 --> 00:14:50.110 align:start position:0% digital cash now makes it fully 00:14:50.110 --> 00:14:53.130 align:start position:0% digital cash now makes it fully distributed<00:14:50.740> and<00:14:50.950> quantum<00:14:51.850> resistant<00:14:52.390> elixir 00:14:53.130 --> 00:14:53.140 align:start position:0% distributed and quantum resistant elixir 00:14:53.140 --> 00:14:56.000 align:start position:0% distributed and quantum resistant elixir thus<00:14:53.410> is<00:14:53.830> able<00:14:54.220> to<00:14:54.400> uniquely<00:14:54.910> provide<00:14:55.330> a<00:14:55.690> new 00:14:56.000 --> 00:14:56.010 align:start position:0% thus is able to uniquely provide a new 00:14:56.010 --> 00:14:58.980 align:start position:0% thus is able to uniquely provide a new ultimate<00:14:57.010> metadata<00:14:57.820> level<00:14:58.240> protection<00:14:58.510> of 00:14:58.980 --> 00:14:58.990 align:start position:0% ultimate metadata level protection of 00:14:58.990 --> 00:15:01.220 align:start position:0% ultimate metadata level protection of confidentiality<00:14:59.470> in<00:15:00.220> all<00:15:00.670> your<00:15:01.030> online 00:15:01.220 --> 00:15:01.230 align:start position:0% confidentiality in all your online 00:15:01.230 --> 00:15:03.870 align:start position:0% confidentiality in all your online communications<00:15:02.230> and<00:15:02.560> payments<00:15:03.400> for<00:15:03.790> the 00:15:03.870 --> 00:15:03.880 align:start position:0% communications and payments for the 00:15:03.880 --> 00:15:06.660 align:start position:0% communications and payments for the first<00:15:04.120> time<00:15:04.480> giving<00:15:05.170> you<00:15:05.380> a<00:15:05.410> protected<00:15:06.250> sphere 00:15:06.660 --> 00:15:06.670 align:start position:0% first time giving you a protected sphere 00:15:06.670 --> 00:15:09.420 align:start position:0% first time giving you a protected sphere protecting<00:15:07.600> your<00:15:07.810> digital<00:15:08.290> world<00:15:08.530> today<00:15:09.100> and 00:15:09.420 --> 00:15:09.430 align:start position:0% protecting your digital world today and 00:15:09.430 --> 00:15:20.850 align:start position:0% protecting your digital world today and your<00:15:10.240> digital<00:15:10.480> future 00:15:20.850 --> 00:15:20.860 align:start position:0% 00:15:20.860 --> 00:15:27.250 align:start position:0% ya<00:15:21.860> think<00:15:22.190> so<00:15:23.260> let<00:15:24.260> me<00:15:25.149> just<00:15:26.149> give<00:15:26.959> you<00:15:26.990> an 00:15:27.250 --> 00:15:27.260 align:start position:0% ya think so let me just give you an 00:15:27.260 --> 00:15:31.420 align:start position:0% ya think so let me just give you an update<00:15:27.940> we<00:15:28.940> we<00:15:29.300> announced<00:15:29.750> our<00:15:29.870> little<00:15:30.430> effort 00:15:31.420 --> 00:15:31.430 align:start position:0% update we we announced our little effort 00:15:31.430 --> 00:15:35.710 align:start position:0% update we we announced our little effort like<00:15:31.970> a<00:15:32.029> year<00:15:32.330> ago<00:15:32.360> in<00:15:32.810> Singapore<00:15:33.410> and<00:15:34.720> it's 00:15:35.710 --> 00:15:35.720 align:start position:0% like a year ago in Singapore and it's 00:15:35.720 --> 00:15:38.490 align:start position:0% like a year ago in Singapore and it's been<00:15:35.930> kind<00:15:36.200> of<00:15:36.320> a<00:15:36.440> wild<00:15:36.620> ride<00:15:37.010> since<00:15:37.430> then<00:15:37.760> been 00:15:38.490 --> 00:15:38.500 align:start position:0% been kind of a wild ride since then been 00:15:38.500 --> 00:15:41.980 align:start position:0% been kind of a wild ride since then been traveling<00:15:39.500> all<00:15:39.620> over<00:15:39.730> and<00:15:40.870> you<00:15:41.870> know 00:15:41.980 --> 00:15:41.990 align:start position:0% traveling all over and you know 00:15:41.990 --> 00:15:45.040 align:start position:0% traveling all over and you know connecting<00:15:42.740> with<00:15:42.860> the<00:15:42.980> community<00:15:44.050> learning 00:15:45.040 --> 00:15:45.050 align:start position:0% connecting with the community learning 00:15:45.050 --> 00:15:46.350 align:start position:0% connecting with the community learning what<00:15:45.290> people<00:15:45.589> want<00:15:45.860> learning<00:15:46.250> how<00:15:46.310> to 00:15:46.350 --> 00:15:46.360 align:start position:0% what people want learning how to 00:15:46.360 --> 00:15:50.500 align:start position:0% what people want learning how to understand<00:15:48.459> all<00:15:49.459> the<00:15:49.700> issues<00:15:49.970> and<00:15:50.120> how<00:15:50.209> people 00:15:50.500 --> 00:15:50.510 align:start position:0% understand all the issues and how people 00:15:50.510 --> 00:15:52.980 align:start position:0% understand all the issues and how people think<00:15:50.660> about<00:15:50.810> them<00:15:51.290> and<00:15:51.589> we've<00:15:52.100> built<00:15:52.640> up 00:15:52.980 --> 00:15:52.990 align:start position:0% think about them and we've built up 00:15:52.990 --> 00:15:56.320 align:start position:0% think about them and we've built up actually<00:15:53.990> several<00:15:54.890> really<00:15:55.339> great<00:15:55.640> teams<00:15:56.000> and 00:15:56.320 --> 00:15:56.330 align:start position:0% actually several really great teams and 00:15:56.330 --> 00:15:58.050 align:start position:0% actually several really great teams and that's<00:15:56.450> why<00:15:56.630> they're<00:15:56.839> two<00:15:57.080> different 00:15:58.050 --> 00:15:58.060 align:start position:0% that's why they're two different 00:15:58.060 --> 00:16:02.829 align:start position:0% that's why they're two different entities<00:15:59.060> we<00:15:59.450> have<00:15:59.480> a<00:16:00.760> R&D<00:16:01.760> lab<00:16:02.060> in<00:16:02.390> the<00:16:02.480> in<00:16:02.750> the 00:16:02.829 --> 00:16:02.839 align:start position:0% entities we have a R&D lab in the in the 00:16:02.839 --> 00:16:05.320 align:start position:0% entities we have a R&D lab in the in the Cayman<00:16:03.260> Islands<00:16:03.770> and<00:16:04.160> no<00:16:04.730> one<00:16:04.850> else<00:16:05.000> seems<00:16:05.240> to 00:16:05.320 --> 00:16:05.330 align:start position:0% Cayman Islands and no one else seems to 00:16:05.330 --> 00:16:06.850 align:start position:0% Cayman Islands and no one else seems to have<00:16:05.570> that<00:16:05.810> but<00:16:05.959> we<00:16:06.050> can<00:16:06.200> bring<00:16:06.410> people<00:16:06.470> from 00:16:06.850 --> 00:16:06.860 align:start position:0% have that but we can bring people from 00:16:06.860 --> 00:16:08.740 align:start position:0% have that but we can bring people from anywhere<00:16:07.100> in<00:16:07.310> the<00:16:07.339> world<00:16:07.430> there<00:16:08.270> as<00:16:08.450> long<00:16:08.660> as 00:16:08.740 --> 00:16:08.750 align:start position:0% anywhere in the world there as long as 00:16:08.750 --> 00:16:10.060 align:start position:0% anywhere in the world there as long as they're<00:16:08.870> not<00:16:08.899> like<00:16:09.470> they<00:16:09.649> don't<00:16:09.709> have<00:16:09.800> lung 00:16:10.060 --> 00:16:10.070 align:start position:0% they're not like they don't have lung 00:16:10.070 --> 00:16:14.170 align:start position:0% they're not like they don't have lung disease<00:16:10.399> or<00:16:10.430> something<00:16:10.850> and<00:16:12.610> so<00:16:13.610> we<00:16:13.880> were 00:16:14.170 --> 00:16:14.180 align:start position:0% disease or something and so we were 00:16:14.180 --> 00:16:15.910 align:start position:0% disease or something and so we were building<00:16:14.540> up<00:16:14.660> the<00:16:14.870> consensus<00:16:15.529> and<00:16:15.770> the 00:16:15.910 --> 00:16:15.920 align:start position:0% building up the consensus and the 00:16:15.920 --> 00:16:18.940 align:start position:0% building up the consensus and the payment<00:16:16.880> work<00:16:17.390> there<00:16:17.660> with<00:16:17.930> our<00:16:18.140> plan<00:16:18.680> to 00:16:18.940 --> 00:16:18.950 align:start position:0% payment work there with our plan to 00:16:18.950 --> 00:16:22.000 align:start position:0% payment work there with our plan to release<00:16:19.220> the<00:16:19.430> white<00:16:19.580> paper<00:16:19.850> this<00:16:20.570> year<00:16:20.930> and<00:16:21.260> I 00:16:22.000 --> 00:16:22.010 align:start position:0% release the white paper this year and I 00:16:22.010 --> 00:16:24.340 align:start position:0% release the white paper this year and I assure<00:16:22.940> you<00:16:23.149> that<00:16:23.329> when<00:16:23.510> you<00:16:23.630> see<00:16:23.870> it<00:16:24.079> it<00:16:24.290> will 00:16:24.340 --> 00:16:24.350 align:start position:0% assure you that when you see it it will 00:16:24.350 --> 00:16:28.000 align:start position:0% assure you that when you see it it will be<00:16:26.020> unlike<00:16:27.020> anything<00:16:27.350> you've<00:16:27.680> seen<00:16:27.709> before 00:16:28.000 --> 00:16:28.010 align:start position:0% be unlike anything you've seen before 00:16:28.010 --> 00:16:30.310 align:start position:0% be unlike anything you've seen before and<00:16:28.700> I<00:16:28.760> hope<00:16:28.910> you'll<00:16:29.120> be<00:16:29.270> as<00:16:29.420> enthusiastic 00:16:30.310 --> 00:16:30.320 align:start position:0% and I hope you'll be as enthusiastic 00:16:30.320 --> 00:16:34.960 align:start position:0% and I hope you'll be as enthusiastic about<00:16:30.440> it<00:16:30.829> as<00:16:31.670> we<00:16:32.029> are<00:16:33.070> we<00:16:34.070> have<00:16:34.310> received<00:16:34.850> a 00:16:34.960 --> 00:16:34.970 align:start position:0% about it as we are we have received a 00:16:34.970 --> 00:16:37.480 align:start position:0% about it as we are we have received a ton<00:16:35.360> of<00:16:35.740> support<00:16:36.740> from<00:16:37.070> the<00:16:37.220> broader 00:16:37.480 --> 00:16:37.490 align:start position:0% ton of support from the broader 00:16:37.490 --> 00:16:41.790 align:start position:0% ton of support from the broader community<00:16:38.110> we've<00:16:39.110> got<00:16:39.350> over<00:16:39.700> like<00:16:40.700> 680<00:16:41.329> node 00:16:41.790 --> 00:16:41.800 align:start position:0% community we've got over like 680 node 00:16:41.800 --> 00:16:44.949 align:start position:0% community we've got over like 680 node operators<00:16:42.800> that<00:16:43.040> have<00:16:43.100> participated<00:16:44.000> in<00:16:44.450> our 00:16:44.949 --> 00:16:44.959 align:start position:0% operators that have participated in our 00:16:44.959 --> 00:16:47.170 align:start position:0% operators that have participated in our open<00:16:45.500> selection<00:16:46.070> process<00:16:46.640> now<00:16:46.850> what<00:16:47.029> do<00:16:47.120> I 00:16:47.170 --> 00:16:47.180 align:start position:0% open selection process now what do I 00:16:47.180 --> 00:16:50.440 align:start position:0% open selection process now what do I mean<00:16:47.450> by<00:16:47.510> that<00:16:47.690> we<00:16:48.529> had<00:16:48.770> a<00:16:48.800> survey<00:16:49.490> first<00:16:49.820> to 00:16:50.440 --> 00:16:50.450 align:start position:0% mean by that we had a survey first to 00:16:50.450 --> 00:16:53.440 align:start position:0% mean by that we had a survey first to find<00:16:50.720> out<00:16:50.930> what<00:16:51.260> people<00:16:51.890> wanted<00:16:52.550> from<00:16:53.149> the 00:16:53.440 --> 00:16:53.450 align:start position:0% find out what people wanted from the 00:16:53.450 --> 00:16:56.139 align:start position:0% find out what people wanted from the process<00:16:54.140> then<00:16:54.829> we<00:16:55.040> built<00:16:55.339> the<00:16:55.550> process 00:16:56.139 --> 00:16:56.149 align:start position:0% process then we built the process 00:16:56.149 --> 00:16:58.240 align:start position:0% process then we built the process according<00:16:56.630> to<00:16:56.660> what<00:16:56.870> the<00:16:57.020> community<00:16:57.230> wanted 00:16:58.240 --> 00:16:58.250 align:start position:0% according to what the community wanted 00:16:58.250 --> 00:17:00.819 align:start position:0% according to what the community wanted we<00:16:58.760> ran<00:16:59.120> the<00:16:59.390> process<00:16:59.990> then<00:17:00.170> we<00:17:00.260> had<00:17:00.380> a<00:17:00.410> spute 00:17:00.819 --> 00:17:00.829 align:start position:0% we ran the process then we had a spute 00:17:00.829 --> 00:17:02.620 align:start position:0% we ran the process then we had a spute resolution<00:17:01.490> procedure<00:17:01.820> and<00:17:02.029> everything<00:17:02.149> in 00:17:02.620 --> 00:17:02.630 align:start position:0% resolution procedure and everything in 00:17:02.630 --> 00:17:05.500 align:start position:0% resolution procedure and everything in it<00:17:03.170> and<00:17:03.649> at<00:17:03.709> the<00:17:03.800> end<00:17:04.069> we<00:17:04.370> got<00:17:04.490> 680<00:17:05.209> notes 00:17:05.500 --> 00:17:05.510 align:start position:0% it and at the end we got 680 notes 00:17:05.510 --> 00:17:07.329 align:start position:0% it and at the end we got 680 notes people<00:17:06.079> that<00:17:06.380> want<00:17:06.589> to<00:17:06.679> support<00:17:07.100> us<00:17:07.189> by 00:17:07.329 --> 00:17:07.339 align:start position:0% people that want to support us by 00:17:07.339 --> 00:17:09.429 align:start position:0% people that want to support us by running<00:17:07.610> notes<00:17:07.939> for<00:17:08.209> free<00:17:08.510> in<00:17:08.809> our<00:17:09.230> beta 00:17:09.429 --> 00:17:09.439 align:start position:0% running notes for free in our beta 00:17:09.439 --> 00:17:12.790 align:start position:0% running notes for free in our beta system<00:17:09.800> and<00:17:10.600> we<00:17:11.600> have<00:17:12.079> divided<00:17:12.530> them<00:17:12.620> into 00:17:12.790 --> 00:17:12.800 align:start position:0% system and we have divided them into 00:17:12.800 --> 00:17:15.640 align:start position:0% system and we have divided them into three<00:17:12.890> teams<00:17:13.400> so<00:17:13.610> we<00:17:13.760> can<00:17:14.030> face<00:17:14.510> them<00:17:14.809> in<00:17:15.020> so 00:17:15.640 --> 00:17:15.650 align:start position:0% three teams so we can face them in so 00:17:15.650 --> 00:17:17.829 align:start position:0% three teams so we can face them in so that's<00:17:15.949> really<00:17:16.850> great<00:17:17.059> and<00:17:17.120> they're<00:17:17.630> well 00:17:17.829 --> 00:17:17.839 align:start position:0% that's really great and they're well 00:17:17.839 --> 00:17:19.419 align:start position:0% that's really great and they're well distributed<00:17:18.410> around<00:17:18.679> the<00:17:18.800> planet<00:17:19.189> everything 00:17:19.419 --> 00:17:19.429 align:start position:0% distributed around the planet everything 00:17:19.429 --> 00:17:22.210 align:start position:0% distributed around the planet everything that<00:17:19.579> was<00:17:19.670> one<00:17:19.819> of<00:17:19.850> the<00:17:19.970> criteria<00:17:20.829> we<00:17:21.829> have 00:17:22.210 --> 00:17:22.220 align:start position:0% that was one of the criteria we have 00:17:22.220 --> 00:17:25.360 align:start position:0% that was one of the criteria we have also<00:17:22.750> been<00:17:23.750> building<00:17:24.199> out<00:17:24.319> our<00:17:24.350> community<00:17:25.010> so 00:17:25.360 --> 00:17:25.370 align:start position:0% also been building out our community so 00:17:25.370 --> 00:17:26.890 align:start position:0% also been building out our community so we've<00:17:25.520> got<00:17:25.730> several<00:17:26.030> thousand<00:17:26.630> I<00:17:26.689> don't<00:17:26.839> know 00:17:26.890 --> 00:17:26.900 align:start position:0% we've got several thousand I don't know 00:17:26.900 --> 00:17:29.860 align:start position:0% we've got several thousand I don't know what<00:17:27.020> the<00:17:27.110> number<00:17:27.350> is<00:17:27.459> exactly<00:17:28.459> now<00:17:28.870> people 00:17:29.860 --> 00:17:29.870 align:start position:0% what the number is exactly now people 00:17:29.870 --> 00:17:31.200 align:start position:0% what the number is exactly now people who<00:17:29.990> have<00:17:30.110> signed<00:17:30.350> up 00:17:31.200 --> 00:17:31.210 align:start position:0% who have signed up 00:17:31.210 --> 00:17:33.300 align:start position:0% who have signed up I've<00:17:31.510> received<00:17:31.960> our<00:17:32.320> app<00:17:32.560> downloaded<00:17:33.160> our<00:17:33.280> app 00:17:33.300 --> 00:17:33.310 align:start position:0% I've received our app downloaded our app 00:17:33.310 --> 00:17:35.550 align:start position:0% I've received our app downloaded our app on<00:17:33.550> Android<00:17:33.880> and<00:17:34.030> iOS<00:17:34.120> which<00:17:35.080> is<00:17:35.200> kind<00:17:35.380> of<00:17:35.410> like 00:17:35.550 --> 00:17:35.560 align:start position:0% on Android and iOS which is kind of like 00:17:35.560 --> 00:17:38.130 align:start position:0% on Android and iOS which is kind of like a<00:17:35.590> waiting<00:17:36.070> list<00:17:36.220> to<00:17:36.580> be<00:17:37.060> the<00:17:37.390> first<00:17:37.600> users<00:17:38.020> of 00:17:38.130 --> 00:17:38.140 align:start position:0% a waiting list to be the first users of 00:17:38.140 --> 00:17:40.710 align:start position:0% a waiting list to be the first users of the<00:17:38.200> messaging<00:17:38.770> system<00:17:38.800> and<00:17:39.580> to<00:17:40.330> be<00:17:40.450> able<00:17:40.540> to 00:17:40.710 --> 00:17:40.720 align:start position:0% the messaging system and to be able to 00:17:40.720 --> 00:17:43.110 align:start position:0% the messaging system and to be able to participate<00:17:41.140> in<00:17:41.470> other<00:17:41.800> ways<00:17:42.070> so<00:17:42.850> I<00:17:42.880> would 00:17:43.110 --> 00:17:43.120 align:start position:0% participate in other ways so I would 00:17:43.120 --> 00:17:45.390 align:start position:0% participate in other ways so I would urge<00:17:43.240> you<00:17:43.480> to<00:17:43.510> get<00:17:43.780> it<00:17:43.990> as<00:17:44.110> soon<00:17:44.260> as<00:17:44.410> you<00:17:44.920> can<00:17:45.160> if 00:17:45.390 --> 00:17:45.400 align:start position:0% urge you to get it as soon as you can if 00:17:45.400 --> 00:17:47.040 align:start position:0% urge you to get it as soon as you can if you<00:17:45.490> have<00:17:45.670> the<00:17:45.790> opportunity<00:17:46.450> to<00:17:46.720> do<00:17:46.870> that 00:17:47.040 --> 00:17:47.050 align:start position:0% you have the opportunity to do that 00:17:47.050 --> 00:17:50.460 align:start position:0% you have the opportunity to do that which<00:17:47.260> I<00:17:47.410> will<00:17:47.470> give<00:17:47.770> you<00:17:48.040> and<00:17:49.020> we<00:17:50.020> are<00:17:50.260> also 00:17:50.460 --> 00:17:50.470 align:start position:0% which I will give you and we are also 00:17:50.470 --> 00:17:53.880 align:start position:0% which I will give you and we are also live<00:17:51.310> in<00:17:51.790> the<00:17:52.090> public<00:17:52.450> alpha<00:17:52.960> as<00:17:53.020> I<00:17:53.260> mentioned 00:17:53.880 --> 00:17:53.890 align:start position:0% live in the public alpha as I mentioned 00:17:53.890 --> 00:17:56.550 align:start position:0% live in the public alpha as I mentioned and<00:17:54.160> when<00:17:55.090> you<00:17:55.210> download<00:17:55.660> the<00:17:55.810> app<00:17:55.840> you<00:17:56.350> can 00:17:56.550 --> 00:17:56.560 align:start position:0% and when you download the app you can 00:17:56.560 --> 00:17:59.190 align:start position:0% and when you download the app you can see<00:17:56.950> the<00:17:57.130> dashboard<00:17:57.310> of<00:17:57.970> the<00:17:58.120> Alpha<00:17:58.840> Network 00:17:59.190 --> 00:17:59.200 align:start position:0% see the dashboard of the Alpha Network 00:17:59.200 --> 00:18:01.290 align:start position:0% see the dashboard of the Alpha Network and<00:17:59.530> watch<00:17:59.650> it<00:17:59.860> all<00:18:00.190> the<00:18:00.490> performance<00:18:01.120> and 00:18:01.290 --> 00:18:01.300 align:start position:0% and watch it all the performance and 00:18:01.300 --> 00:18:03.270 align:start position:0% and watch it all the performance and stuff<00:18:01.450> so<00:18:01.690> the<00:18:01.780> main<00:18:02.350> purpose<00:18:02.620> of<00:18:02.890> the<00:18:02.980> Alpha 00:18:03.270 --> 00:18:03.280 align:start position:0% stuff so the main purpose of the Alpha 00:18:03.280 --> 00:18:06.000 align:start position:0% stuff so the main purpose of the Alpha is<00:18:03.340> really<00:18:03.670> to<00:18:04.050> perfect<00:18:05.050> the<00:18:05.260> the<00:18:05.290> performance 00:18:06.000 --> 00:18:06.010 align:start position:0% is really to perfect the the performance 00:18:06.010 --> 00:18:09.000 align:start position:0% is really to perfect the the performance but<00:18:06.880> we've<00:18:07.090> exposed<00:18:07.570> the<00:18:07.810> api's<00:18:08.440> and<00:18:08.920> the 00:18:09.000 --> 00:18:09.010 align:start position:0% but we've exposed the api's and the 00:18:09.010 --> 00:18:13.170 align:start position:0% but we've exposed the api's and the libraries<00:18:09.730> to<00:18:10.360> our<00:18:10.540> RF<00:18:11.200> SDK<00:18:11.650> partners<00:18:12.220> because 00:18:13.170 --> 00:18:13.180 align:start position:0% libraries to our RF SDK partners because 00:18:13.180 --> 00:18:14.310 align:start position:0% libraries to our RF SDK partners because we're<00:18:13.360> not<00:18:13.420> in<00:18:13.510> the<00:18:13.540> band<00:18:13.750> with<00:18:13.900> the<00:18:13.930> support 00:18:14.310 --> 00:18:14.320 align:start position:0% we're not in the band with the support 00:18:14.320 --> 00:18:15.920 align:start position:0% we're not in the band with the support the<00:18:14.410> whole<00:18:14.560> community<00:18:15.010> yet<00:18:15.130> so<00:18:15.340> we're<00:18:15.490> kind<00:18:15.760> of 00:18:15.920 --> 00:18:15.930 align:start position:0% the whole community yet so we're kind of 00:18:15.930 --> 00:18:18.120 align:start position:0% the whole community yet so we're kind of rolling<00:18:16.930> that<00:18:16.960> out<00:18:17.140> and<00:18:17.680> trying<00:18:17.890> to<00:18:18.010> get 00:18:18.120 --> 00:18:18.130 align:start position:0% rolling that out and trying to get 00:18:18.130 --> 00:18:21.260 align:start position:0% rolling that out and trying to get everything<00:18:18.370> really<00:18:19.180> nice<00:18:19.450> to<00:18:19.690> need<00:18:19.870> before<00:18:20.110> we 00:18:21.260 --> 00:18:21.270 align:start position:0% everything really nice to need before we 00:18:21.270 --> 00:18:24.240 align:start position:0% everything really nice to need before we enlarge<00:18:22.270> the<00:18:22.600> the<00:18:22.900> sphere<00:18:23.200> of<00:18:23.470> people<00:18:24.130> have 00:18:24.240 --> 00:18:24.250 align:start position:0% enlarge the the sphere of people have 00:18:24.250 --> 00:18:26.670 align:start position:0% enlarge the the sphere of people have access<00:18:24.730> to<00:18:25.060> it<00:18:25.270> so<00:18:25.540> I've<00:18:26.080> been<00:18:26.200> traveling 00:18:26.670 --> 00:18:26.680 align:start position:0% access to it so I've been traveling 00:18:26.680 --> 00:18:29.460 align:start position:0% access to it so I've been traveling around<00:18:26.740> Asia<00:18:27.100> on<00:18:27.700> this<00:18:28.030> last<00:18:29.020> few<00:18:29.260> weeks 00:18:29.460 --> 00:18:29.470 align:start position:0% around Asia on this last few weeks 00:18:29.470 --> 00:18:33.170 align:start position:0% around Asia on this last few weeks announcing<00:18:30.840> mostly<00:18:31.840> it<00:18:31.960> meetups<00:18:32.470> and<00:18:32.620> at 00:18:33.170 --> 00:18:33.180 align:start position:0% announcing mostly it meetups and at 00:18:33.180 --> 00:18:35.640 align:start position:0% announcing mostly it meetups and at conferences<00:18:34.180> not<00:18:34.330> no<00:18:34.750> conference<00:18:35.140> as<00:18:35.290> big<00:18:35.500> as 00:18:35.640 --> 00:18:35.650 align:start position:0% conferences not no conference as big as 00:18:35.650 --> 00:18:41.490 align:start position:0% conferences not no conference as big as this<00:18:35.860> one<00:18:37.620> that<00:18:38.620> our<00:18:38.890> our<00:18:39.480> Cayman<00:18:40.480> lab<00:18:41.140> has 00:18:41.490 --> 00:18:41.500 align:start position:0% this one that our our Cayman lab has 00:18:41.500 --> 00:18:43.410 align:start position:0% this one that our our Cayman lab has come<00:18:41.890> has<00:18:42.100> come<00:18:42.340> out<00:18:42.490> of<00:18:42.640> stealth<00:18:42.940> and<00:18:43.240> that<00:18:43.330> we 00:18:43.410 --> 00:18:43.420 align:start position:0% come has come out of stealth and that we 00:18:43.420 --> 00:18:46.680 align:start position:0% come has come out of stealth and that we will<00:18:43.600> have<00:18:43.780> the<00:18:43.900> white<00:18:44.080> paper<00:18:44.410> and<00:18:45.240> that<00:18:46.240> the 00:18:46.680 --> 00:18:46.690 align:start position:0% will have the white paper and that the 00:18:46.690 --> 00:18:48.870 align:start position:0% will have the white paper and that the payment<00:18:47.560> system<00:18:47.950> it<00:18:48.100> has<00:18:48.250> is<00:18:48.490> quantum 00:18:48.870 --> 00:18:48.880 align:start position:0% payment system it has is quantum 00:18:48.880 --> 00:18:51.600 align:start position:0% payment system it has is quantum resistant<00:18:49.480> and<00:18:49.720> it<00:18:50.290> will<00:18:50.470> be<00:18:50.650> able<00:18:50.830> to<00:18:51.160> do<00:18:51.340> the 00:18:51.600 --> 00:18:51.610 align:start position:0% resistant and it will be able to do the 00:18:51.610 --> 00:18:54.540 align:start position:0% resistant and it will be able to do the kind<00:18:52.540> of<00:18:52.720> when<00:18:53.530> you<00:18:53.620> mix<00:18:54.040> that<00:18:54.310> when<00:18:54.460> you 00:18:54.540 --> 00:18:54.550 align:start position:0% kind of when you mix that when you 00:18:54.550 --> 00:18:57.570 align:start position:0% kind of when you mix that when you combine<00:18:54.910> that<00:18:54.940> with<00:18:55.180> the<00:18:55.600> elixir<00:18:56.590> you'll<00:18:57.310> have 00:18:57.570 --> 00:18:57.580 align:start position:0% combine that with the elixir you'll have 00:18:57.580 --> 00:19:02.180 align:start position:0% combine that with the elixir you'll have a<00:18:59.460> tap<00:19:00.460> say<00:19:00.670> it<00:19:00.790> but<00:19:00.970> the<00:19:01.300> world's<00:19:01.600> best<00:19:01.810> money 00:19:02.180 --> 00:19:02.190 align:start position:0% a tap say it but the world's best money 00:19:02.190 --> 00:19:09.930 align:start position:0% a tap say it but the world's best money no<00:19:03.190> question<00:19:03.670> hands<00:19:03.880> down<00:19:04.150> so<00:19:05.850> that's<00:19:08.880> kind<00:19:09.880> of 00:19:09.930 --> 00:19:09.940 align:start position:0% no question hands down so that's kind of 00:19:09.940 --> 00:19:11.790 align:start position:0% no question hands down so that's kind of what<00:19:10.060> we've<00:19:10.360> been<00:19:10.480> up<00:19:10.540> to<00:19:10.660> over<00:19:10.990> the<00:19:11.140> last<00:19:11.260> year 00:19:11.790 --> 00:19:11.800 align:start position:0% what we've been up to over the last year 00:19:11.800 --> 00:19:16.580 align:start position:0% what we've been up to over the last year and<00:19:12.750> here's<00:19:13.750> a<00:19:13.810> sort<00:19:14.080> of<00:19:14.200> preview<00:19:14.740> of<00:19:14.950> the<00:19:15.190> app 00:19:16.580 --> 00:19:16.590 align:start position:0% and here's a sort of preview of the app 00:19:16.590 --> 00:19:18.870 align:start position:0% and here's a sort of preview of the app there's<00:19:17.590> a<00:19:17.680> lot<00:19:17.830> of<00:19:17.980> things<00:19:18.160> in<00:19:18.370> it<00:19:18.520> and<00:19:18.700> if<00:19:18.760> you 00:19:18.870 --> 00:19:18.880 align:start position:0% there's a lot of things in it and if you 00:19:18.880 --> 00:19:20.930 align:start position:0% there's a lot of things in it and if you look<00:19:19.300> at<00:19:19.390> those<00:19:19.540> those<00:19:19.930> scroll<00:19:20.410> the<00:19:20.500> menu<00:19:20.740> bar 00:19:20.930 --> 00:19:20.940 align:start position:0% look at those those scroll the menu bar 00:19:20.940 --> 00:19:23.640 align:start position:0% look at those those scroll the menu bar horizontally<00:19:21.940> you'll<00:19:22.090> see<00:19:22.300> I<00:19:22.570> can<00:19:23.320> keep<00:19:23.500> track 00:19:23.640 --> 00:19:23.650 align:start position:0% horizontally you'll see I can keep track 00:19:23.650 --> 00:19:25.790 align:start position:0% horizontally you'll see I can keep track of<00:19:23.950> all<00:19:24.220> the<00:19:24.340> things<00:19:24.550> we're<00:19:24.730> doing<00:19:24.760> and 00:19:25.790 --> 00:19:25.800 align:start position:0% of all the things we're doing and 00:19:25.800 --> 00:19:28.110 align:start position:0% of all the things we're doing and there's<00:19:26.800> gonna<00:19:26.980> be<00:19:27.190> a<00:19:27.220> lot<00:19:27.430> more<00:19:27.640> interesting 00:19:28.110 --> 00:19:28.120 align:start position:0% there's gonna be a lot more interesting 00:19:28.120 --> 00:19:34.760 align:start position:0% there's gonna be a lot more interesting stuff<00:19:28.420> there<00:19:28.720> so<00:19:29.140> I<00:19:32.640> let<00:19:33.640> me<00:19:33.730> put<00:19:33.940> up<00:19:34.060> this 00:19:34.760 --> 00:19:34.770 align:start position:0% stuff there so I let me put up this 00:19:34.770 --> 00:19:40.080 align:start position:0% stuff there so I let me put up this barcode<00:19:35.770> or<00:19:36.700> QR<00:19:37.690> code<00:19:38.080> if<00:19:38.350> will<00:19:38.590> and<00:19:38.940> urge<00:19:39.940> you 00:19:40.080 --> 00:19:40.090 align:start position:0% barcode or QR code if will and urge you 00:19:40.090 --> 00:19:43.380 align:start position:0% barcode or QR code if will and urge you to<00:19:40.180> all<00:19:41.250> test<00:19:42.250> do<00:19:42.400> you<00:19:42.460> think<00:19:42.640> that<00:19:42.760> what<00:19:42.910> QR 00:19:43.380 --> 00:19:43.390 align:start position:0% to all test do you think that what QR 00:19:43.390 --> 00:19:45.049 align:start position:0% to all test do you think that what QR code<00:19:43.600> will<00:19:43.780> work 00:19:45.049 --> 00:19:45.059 align:start position:0% code will work 00:19:45.059 --> 00:19:48.180 align:start position:0% code will work why<00:19:46.059> don't<00:19:46.240> you<00:19:46.299> see<00:19:46.990> if<00:19:47.110> your<00:19:47.289> QR<00:19:47.679> code<00:19:47.919> reader 00:19:48.180 --> 00:19:48.190 align:start position:0% why don't you see if your QR code reader 00:19:48.190 --> 00:19:51.240 align:start position:0% why don't you see if your QR code reader is<00:19:48.340> capable<00:19:49.299> of<00:19:49.480> reading<00:19:50.409> that<00:19:50.559> code<00:19:50.860> and<00:19:51.130> then 00:19:51.240 --> 00:19:51.250 align:start position:0% is capable of reading that code and then 00:19:51.250 --> 00:19:53.970 align:start position:0% is capable of reading that code and then decide<00:19:51.760> if<00:19:51.909> you<00:19:52.000> want<00:19:52.210> to<00:19:52.270> download<00:19:52.590> the<00:19:53.590> the 00:19:53.970 --> 00:19:53.980 align:start position:0% decide if you want to download the the 00:19:53.980 --> 00:19:55.440 align:start position:0% decide if you want to download the the app<00:19:54.100> of<00:19:54.340> your<00:19:54.370> choice<00:19:54.730> and<00:19:55.059> then<00:19:55.150> you'll<00:19:55.299> have 00:19:55.440 --> 00:19:55.450 align:start position:0% app of your choice and then you'll have 00:19:55.450 --> 00:19:57.510 align:start position:0% app of your choice and then you'll have a<00:19:55.510> position<00:19:56.020> in<00:19:56.169> line<00:19:56.409> and<00:19:56.799> be<00:19:57.220> able<00:19:57.279> to<00:19:57.370> see 00:19:57.510 --> 00:19:57.520 align:start position:0% a position in line and be able to see 00:19:57.520 --> 00:19:59.310 align:start position:0% a position in line and be able to see what<00:19:57.669> we're<00:19:57.820> doing<00:19:57.940> and<00:19:58.330> watch<00:19:58.539> the<00:19:58.779> dashboard 00:19:59.310 --> 00:19:59.320 align:start position:0% what we're doing and watch the dashboard 00:19:59.320 --> 00:20:03.000 align:start position:0% what we're doing and watch the dashboard and<00:19:59.679> join<00:20:00.640> our<00:20:00.820> community<00:20:01.029> so<00:20:01.830> thank<00:20:02.830> you<00:20:02.980> very 00:20:03.000 --> 00:20:03.010 align:start position:0% and join our community so thank you very 00:20:03.010 --> 00:20:05.130 align:start position:0% and join our community so thank you very very<00:20:03.340> much<00:20:03.520> for<00:20:03.700> your<00:20:04.480> attention<00:20:04.809> as<00:20:05.110> a 00:20:05.130 --> 00:20:05.140 align:start position:0% very much for your attention as a 00:20:05.140 --> 00:20:07.799 align:start position:0% very much for your attention as a pleasure<00:20:05.470> and<00:20:05.799> I'll<00:20:06.250> be<00:20:06.400> around<00:20:06.700> so<00:20:07.330> look 00:20:07.799 --> 00:20:07.809 align:start position:0% pleasure and I'll be around so look 00:20:07.809 --> 00:20:10.350 align:start position:0% pleasure and I'll be around so look forward<00:20:08.020> to<00:20:08.110> having<00:20:08.590> a<00:20:08.679> chance<00:20:08.890> to<00:20:09.330> chat<00:20:10.330> with 00:20:10.350 --> 00:20:10.360 align:start position:0% forward to having a chance to chat with 00:20:10.360 --> 00:20:12.120 align:start position:0% forward to having a chance to chat with you<00:20:10.659> and<00:20:10.929> thanks<00:20:11.799> again 00:20:12.120 --> 00:20:12.130 align:start position:0% you and thanks again 00:20:12.130 --> 00:20:22.970 align:start position:0% you and thanks again [Applause] 00:20:22.970 --> 00:20:22.980 align:start position:0% 00:20:22.980 --> 00:20:25.040 align:start position:0% you