WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.030 align:start position:0% [Music] 00:00:09.030 --> 00:00:09.040 align:start position:0% [Music] 00:00:09.040 --> 00:00:10.230 align:start position:0% [Music] all<00:00:09.160> right<00:00:09.280> there<00:00:09.360> we<00:00:09.519> go<00:00:09.639> now<00:00:09.760> it's<00:00:10.080> uh 00:00:10.230 --> 00:00:10.240 align:start position:0% all right there we go now it's uh 00:00:10.240 --> 00:00:12.230 align:start position:0% all right there we go now it's uh another<00:00:10.480> Globe<00:00:10.759> spinning<00:00:11.320> very<00:00:11.519> cool<00:00:12.000> took<00:00:12.120> me 00:00:12.230 --> 00:00:12.240 align:start position:0% another Globe spinning very cool took me 00:00:12.240 --> 00:00:13.509 align:start position:0% another Globe spinning very cool took me hours<00:00:12.480> to<00:00:12.599> make<00:00:12.799> that<00:00:12.960> so<00:00:13.080> I<00:00:13.160> wanted<00:00:13.320> to<00:00:13.400> make 00:00:13.509 --> 00:00:13.519 align:start position:0% hours to make that so I wanted to make 00:00:13.519 --> 00:00:15.549 align:start position:0% hours to make that so I wanted to make sure<00:00:13.679> you<00:00:13.799> guys<00:00:13.920> saw<00:00:14.160> it<00:00:14.960> um<00:00:15.200> yeah<00:00:15.400> hey 00:00:15.549 --> 00:00:15.559 align:start position:0% sure you guys saw it um yeah hey 00:00:15.559 --> 00:00:16.830 align:start position:0% sure you guys saw it um yeah hey everyone<00:00:16.000> really<00:00:16.160> great<00:00:16.320> to<00:00:16.440> be<00:00:16.560> here<00:00:16.720> I'm 00:00:16.830 --> 00:00:16.840 align:start position:0% everyone really great to be here I'm 00:00:16.840 --> 00:00:18.349 align:start position:0% everyone really great to be here I'm excited<00:00:17.160> to<00:00:17.320> talk<00:00:17.480> about<00:00:17.840> what<00:00:17.920> it<00:00:18.039> is<00:00:18.199> we're 00:00:18.349 --> 00:00:18.359 align:start position:0% excited to talk about what it is we're 00:00:18.359 --> 00:00:21.429 align:start position:0% excited to talk about what it is we're building<00:00:19.080> I'm<00:00:19.279> Michael<00:00:19.520> Elliot<00:00:20.359> from<00:00:20.840> yeah 00:00:21.429 --> 00:00:21.439 align:start position:0% building I'm Michael Elliot from yeah 00:00:21.439 --> 00:00:23.269 align:start position:0% building I'm Michael Elliot from yeah and<00:00:21.560> I'm<00:00:21.760> d<00:00:22.199> as<00:00:22.400> introduced<00:00:22.880> from<00:00:23.000> FR 00:00:23.269 --> 00:00:23.279 align:start position:0% and I'm d as introduced from FR 00:00:23.279 --> 00:00:24.710 align:start position:0% and I'm d as introduced from FR obviously<00:00:23.519> we<00:00:23.640> just<00:00:23.720> got<00:00:23.880> introduce<00:00:24.279> so<00:00:24.560> need 00:00:24.710 --> 00:00:24.720 align:start position:0% obviously we just got introduce so need 00:00:24.720 --> 00:00:26.669 align:start position:0% obviously we just got introduce so need for<00:00:24.840> that<00:00:25.039> again<00:00:25.720> um<00:00:25.920> yeah<00:00:26.080> we're<00:00:26.480> looking 00:00:26.669 --> 00:00:26.679 align:start position:0% for that again um yeah we're looking 00:00:26.679 --> 00:00:28.669 align:start position:0% for that again um yeah we're looking forward<00:00:26.920> to<00:00:27.119> to<00:00:27.279> going<00:00:27.560> through<00:00:28.320> uh<00:00:28.480> what<00:00:28.599> it 00:00:28.669 --> 00:00:28.679 align:start position:0% forward to to going through uh what it 00:00:28.679 --> 00:00:30.710 align:start position:0% forward to to going through uh what it is<00:00:28.800> we're<00:00:28.960> building<00:00:29.480> and<00:00:29.800> uh<00:00:30.359> the<00:00:30.480> tech 00:00:30.710 --> 00:00:30.720 align:start position:0% is we're building and uh the tech 00:00:30.720 --> 00:00:33.030 align:start position:0% is we're building and uh the tech involved<00:00:31.359> and<00:00:32.000> explaining<00:00:32.399> you<00:00:32.559> how<00:00:32.680> we<00:00:32.800> built 00:00:33.030 --> 00:00:33.040 align:start position:0% involved and explaining you how we built 00:00:33.040 --> 00:00:36.510 align:start position:0% involved and explaining you how we built it<00:00:33.280> and<00:00:33.480> also<00:00:34.120> uh<00:00:34.440> why<00:00:34.559> we<00:00:34.719> built 00:00:36.510 --> 00:00:36.520 align:start position:0% it and also uh why we built 00:00:36.520 --> 00:00:38.030 align:start position:0% it and also uh why we built it 00:00:38.030 --> 00:00:38.040 align:start position:0% it 00:00:38.040 --> 00:00:40.069 align:start position:0% it so<00:00:39.040> I'm<00:00:39.160> pretty<00:00:39.320> sure<00:00:39.480> everyone<00:00:39.680> in<00:00:39.800> this<00:00:39.920> room 00:00:40.069 --> 00:00:40.079 align:start position:0% so I'm pretty sure everyone in this room 00:00:40.079 --> 00:00:42.869 align:start position:0% so I'm pretty sure everyone in this room is<00:00:40.239> quite<00:00:40.440> familiar<00:00:41.280> uh<00:00:41.719> with<00:00:41.879> the<00:00:42.039> fact<00:00:42.280> that 00:00:42.869 --> 00:00:42.879 align:start position:0% is quite familiar uh with the fact that 00:00:42.879 --> 00:00:44.430 align:start position:0% is quite familiar uh with the fact that online<00:00:43.360> identity 00:00:44.430 --> 00:00:44.440 align:start position:0% online identity 00:00:44.440 --> 00:00:47.590 align:start position:0% online identity verification<00:00:45.920> sucks<00:00:46.920> I<00:00:47.000> think<00:00:47.160> everyone<00:00:47.440> here 00:00:47.590 --> 00:00:47.600 align:start position:0% verification sucks I think everyone here 00:00:47.600 --> 00:00:50.830 align:start position:0% verification sucks I think everyone here has<00:00:47.760> had<00:00:47.920> the<00:00:48.079> experience<00:00:48.920> of<00:00:49.520> um<00:00:50.520> taking<00:00:50.760> a 00:00:50.830 --> 00:00:50.840 align:start position:0% has had the experience of um taking a 00:00:50.840 --> 00:00:52.910 align:start position:0% has had the experience of um taking a photograph<00:00:51.320> of<00:00:51.440> your<00:00:51.640> passport<00:00:52.480> and<00:00:52.640> setting 00:00:52.910 --> 00:00:52.920 align:start position:0% photograph of your passport and setting 00:00:52.920 --> 00:00:56.510 align:start position:0% photograph of your passport and setting it<00:00:53.039> off<00:00:53.160> to<00:00:53.280> some<00:00:53.520> service<00:00:54.480> for<00:00:54.879> for<00:00:55.160> kyc 00:00:56.510 --> 00:00:56.520 align:start position:0% it off to some service for for kyc 00:00:56.520 --> 00:00:58.549 align:start position:0% it off to some service for for kyc verification<00:00:57.520> um<00:00:57.680> you<00:00:57.800> know<00:00:58.039> you<00:00:58.199> got<00:00:58.280> to 00:00:58.549 --> 00:00:58.559 align:start position:0% verification um you know you got to 00:00:58.559 --> 00:01:00.349 align:start position:0% verification um you know you got to basically<00:00:58.879> trust<00:00:59.239> them<00:00:59.399> to<00:00:59.559> keep<00:00:59.760> that<00:01:00.039> data 00:01:00.349 --> 00:01:00.359 align:start position:0% basically trust them to keep that data 00:01:00.359 --> 00:01:04.710 align:start position:0% basically trust them to keep that data safe<00:01:01.359> uh<00:01:01.600> hint<00:01:02.519> they<00:01:02.879> won't<00:01:03.879> there's<00:01:04.119> been<00:01:04.600> you 00:01:04.710 --> 00:01:04.720 align:start position:0% safe uh hint they won't there's been you 00:01:04.720 --> 00:01:07.510 align:start position:0% safe uh hint they won't there's been you know<00:01:05.000> many<00:01:05.280> many<00:01:05.760> um<00:01:06.040> hacks<00:01:06.280> and<00:01:06.439> data<00:01:06.640> leaks 00:01:07.510 --> 00:01:07.520 align:start position:0% know many many um hacks and data leaks 00:01:07.520 --> 00:01:10.190 align:start position:0% know many many um hacks and data leaks uh<00:01:07.640> throughout<00:01:08.560> recent<00:01:08.960> years<00:01:09.960> that<00:01:10.080> just 00:01:10.190 --> 00:01:10.200 align:start position:0% uh throughout recent years that just 00:01:10.200 --> 00:01:11.990 align:start position:0% uh throughout recent years that just demonstrates<00:01:10.799> that<00:01:10.960> it's<00:01:11.200> you<00:01:11.320> know<00:01:11.560> very 00:01:11.990 --> 00:01:12.000 align:start position:0% demonstrates that it's you know very 00:01:12.000 --> 00:01:13.310 align:start position:0% demonstrates that it's you know very difficult<00:01:12.360> for<00:01:12.560> companies<00:01:12.920> to<00:01:13.040> keep<00:01:13.200> that 00:01:13.310 --> 00:01:13.320 align:start position:0% difficult for companies to keep that 00:01:13.320 --> 00:01:15.350 align:start position:0% difficult for companies to keep that kind<00:01:13.439> of<00:01:13.560> data<00:01:14.240> um 00:01:15.350 --> 00:01:15.360 align:start position:0% kind of data um 00:01:15.360 --> 00:01:18.870 align:start position:0% kind of data um secure<00:01:16.360> and<00:01:16.880> this<00:01:17.080> inevitably<00:01:17.600> leads<00:01:18.000> to<00:01:18.600> yeah 00:01:18.870 --> 00:01:18.880 align:start position:0% secure and this inevitably leads to yeah 00:01:18.880 --> 00:01:23.350 align:start position:0% secure and this inevitably leads to yeah theft<00:01:19.360> and<00:01:19.799> uh<00:01:20.479> uh<00:01:20.680> identity<00:01:21.159> theft<00:01:21.799> and<00:01:22.360> fraud 00:01:23.350 --> 00:01:23.360 align:start position:0% theft and uh uh identity theft and fraud 00:01:23.360 --> 00:01:25.830 align:start position:0% theft and uh uh identity theft and fraud and<00:01:23.600> another<00:01:23.960> downside<00:01:24.520> of<00:01:24.720> this<00:01:25.360> is<00:01:25.600> that<00:01:25.720> you 00:01:25.830 --> 00:01:25.840 align:start position:0% and another downside of this is that you 00:01:25.840 --> 00:01:27.789 align:start position:0% and another downside of this is that you can't<00:01:26.040> bring<00:01:26.200> it<00:01:26.360> on 00:01:27.789 --> 00:01:27.799 align:start position:0% can't bring it on 00:01:27.799 --> 00:01:32.789 align:start position:0% can't bring it on chain<00:01:28.799> so<00:01:30.280> another<00:01:30.560> more<00:01:30.799> recent<00:01:31.360> kind<00:01:31.479> of<00:01:31.799> um 00:01:32.789 --> 00:01:32.799 align:start position:0% chain so another more recent kind of um 00:01:32.799 --> 00:01:34.910 align:start position:0% chain so another more recent kind of um threat<00:01:33.079> to<00:01:33.280> this<00:01:33.560> par<00:01:33.880> this<00:01:34.040> model<00:01:34.439> is 00:01:34.910 --> 00:01:34.920 align:start position:0% threat to this par this model is 00:01:34.920 --> 00:01:37.429 align:start position:0% threat to this par this model is generative<00:01:35.840> AI<00:01:36.840> um<00:01:36.960> this<00:01:37.040> is<00:01:37.159> becoming 00:01:37.429 --> 00:01:37.439 align:start position:0% generative AI um this is becoming 00:01:37.439 --> 00:01:40.550 align:start position:0% generative AI um this is becoming increasingly<00:01:38.439> Advanced<00:01:39.040> and<00:01:39.880> uh<00:01:40.040> easy<00:01:40.320> to 00:01:40.550 --> 00:01:40.560 align:start position:0% increasingly Advanced and uh easy to 00:01:40.560 --> 00:01:43.069 align:start position:0% increasingly Advanced and uh easy to access<00:01:41.320> so<00:01:41.520> this<00:01:41.640> is<00:01:41.759> an<00:01:41.960> example<00:01:42.320> of<00:01:42.560> a<00:01:42.759> a<00:01:42.880> fake 00:01:43.069 --> 00:01:43.079 align:start position:0% access so this is an example of a a fake 00:01:43.079 --> 00:01:45.230 align:start position:0% access so this is an example of a a fake ID<00:01:43.399> generated<00:01:44.200> by<00:01:44.320> a<00:01:44.439> service<00:01:44.759> called<00:01:45.000> only 00:01:45.230 --> 00:01:45.240 align:start position:0% ID generated by a service called only 00:01:45.240 --> 00:01:47.389 align:start position:0% ID generated by a service called only fakes<00:01:46.079> so<00:01:46.240> it's<00:01:46.360> it's<00:01:46.479> currently<00:01:46.880> possible<00:01:47.240> to 00:01:47.389 --> 00:01:47.399 align:start position:0% fakes so it's it's currently possible to 00:01:47.399 --> 00:01:50.990 align:start position:0% fakes so it's it's currently possible to pay<00:01:47.680> like<00:01:48.479> $15<00:01:49.479> and<00:01:49.560> you<00:01:49.680> can<00:01:49.840> have<00:01:50.119> a<00:01:50.600> a<00:01:50.759> really 00:01:50.990 --> 00:01:51.000 align:start position:0% pay like $15 and you can have a a really 00:01:51.000 --> 00:01:52.950 align:start position:0% pay like $15 and you can have a a really genuine<00:01:51.399> authentic<00:01:51.840> looking<00:01:52.600> government 00:01:52.950 --> 00:01:52.960 align:start position:0% genuine authentic looking government 00:01:52.960 --> 00:01:55.030 align:start position:0% genuine authentic looking government issue<00:01:53.280> document<00:01:53.640> created<00:01:54.640> so<00:01:54.799> what<00:01:54.920> you<00:01:54.960> know 00:01:55.030 --> 00:01:55.040 align:start position:0% issue document created so what you know 00:01:55.040 --> 00:01:56.670 align:start position:0% issue document created so what you know a<00:01:55.159> high<00:01:55.280> school<00:01:55.920> high<00:01:56.079> school<00:01:56.240> kid<00:01:56.399> could<00:01:56.520> do 00:01:56.670 --> 00:01:56.680 align:start position:0% a high school high school kid could do 00:01:56.680 --> 00:01:59.149 align:start position:0% a high school high school kid could do this<00:01:56.880> find<00:01:57.240> a<00:01:57.439> profile<00:01:57.719> photo<00:01:58.000> of<00:01:58.119> someone<00:01:58.960> on 00:01:59.149 --> 00:01:59.159 align:start position:0% this find a profile photo of someone on 00:01:59.159 --> 00:02:01.230 align:start position:0% this find a profile photo of someone on like<00:01:59.320> Twitter<00:02:00.000> and<00:02:00.159> then<00:02:00.520> easily<00:02:00.880> generate 00:02:01.230 --> 00:02:01.240 align:start position:0% like Twitter and then easily generate 00:02:01.240 --> 00:02:03.590 align:start position:0% like Twitter and then easily generate something<00:02:01.479> that<00:02:01.600> would<00:02:01.719> fool<00:02:02.240> the<00:02:02.399> KY<00:02:02.920> of<00:02:03.320> of 00:02:03.590 --> 00:02:03.600 align:start position:0% something that would fool the KY of of 00:02:03.600 --> 00:02:06.310 align:start position:0% something that would fool the KY of of some<00:02:03.840> services<00:02:04.680> in<00:02:04.840> fact<00:02:05.039> the<00:02:05.159> article<00:02:05.880> that 00:02:06.310 --> 00:02:06.320 align:start position:0% some services in fact the article that 00:02:06.320 --> 00:02:08.910 align:start position:0% some services in fact the article that um<00:02:06.560> this<00:02:06.680> is<00:02:06.840> from<00:02:07.239> originally<00:02:08.239> um<00:02:08.520> they<00:02:08.640> tried 00:02:08.910 --> 00:02:08.920 align:start position:0% um this is from originally um they tried 00:02:08.920 --> 00:02:10.910 align:start position:0% um this is from originally um they tried it<00:02:09.080> out<00:02:09.360> and<00:02:09.479> they<00:02:09.599> actually<00:02:09.879> managed<00:02:10.160> a<00:02:10.280> kyc 00:02:10.910 --> 00:02:10.920 align:start position:0% it out and they actually managed a kyc 00:02:10.920 --> 00:02:12.030 align:start position:0% it out and they actually managed a kyc on<00:02:11.039> a<00:02:11.160> crypto 00:02:12.030 --> 00:02:12.040 align:start position:0% on a crypto 00:02:12.040 --> 00:02:13.710 align:start position:0% on a crypto exchange<00:02:13.040> and<00:02:13.120> I<00:02:13.200> think<00:02:13.319> it's<00:02:13.440> just<00:02:13.520> going<00:02:13.640> to 00:02:13.710 --> 00:02:13.720 align:start position:0% exchange and I think it's just going to 00:02:13.720 --> 00:02:15.070 align:start position:0% exchange and I think it's just going to get<00:02:13.800> easier<00:02:14.080> and<00:02:14.200> easier<00:02:14.519> for<00:02:14.680> this<00:02:14.760> to<00:02:14.879> be<00:02:15.000> the 00:02:15.070 --> 00:02:15.080 align:start position:0% get easier and easier for this to be the 00:02:15.080 --> 00:02:16.949 align:start position:0% get easier and easier for this to be the case<00:02:15.239> so<00:02:15.360> this<00:02:15.480> completely<00:02:15.879> breaks<00:02:16.160> the<00:02:16.280> model 00:02:16.949 --> 00:02:16.959 align:start position:0% case so this completely breaks the model 00:02:16.959 --> 00:02:18.229 align:start position:0% case so this completely breaks the model of<00:02:17.200> um<00:02:17.319> taking<00:02:17.519> a<00:02:17.599> photograph<00:02:18.040> of<00:02:18.120> your 00:02:18.229 --> 00:02:18.239 align:start position:0% of um taking a photograph of your 00:02:18.239 --> 00:02:20.750 align:start position:0% of um taking a photograph of your documents<00:02:18.560> and<00:02:18.640> sending<00:02:18.920> it 00:02:20.750 --> 00:02:20.760 align:start position:0% documents and sending it 00:02:20.760 --> 00:02:24.550 align:start position:0% documents and sending it in<00:02:21.760> so<00:02:22.720> what<00:02:22.879> if<00:02:23.120> instead<00:02:23.519> of<00:02:23.720> this<00:02:24.239> what<00:02:24.360> if 00:02:24.550 --> 00:02:24.560 align:start position:0% in so what if instead of this what if 00:02:24.560 --> 00:02:27.670 align:start position:0% in so what if instead of this what if instead<00:02:25.480> um<00:02:25.959> you<00:02:26.120> could<00:02:26.599> reveal<00:02:27.160> only<00:02:27.519> what 00:02:27.670 --> 00:02:27.680 align:start position:0% instead um you could reveal only what 00:02:27.680 --> 00:02:30.190 align:start position:0% instead um you could reveal only what you<00:02:28.200> absolutely<00:02:28.640> needed<00:02:28.920> to<00:02:29.120> reveal<00:02:29.920> for<00:02:30.080> a 00:02:30.190 --> 00:02:30.200 align:start position:0% you absolutely needed to reveal for a 00:02:30.200 --> 00:02:32.710 align:start position:0% you absolutely needed to reveal for a particular<00:02:30.599> service<00:02:31.599> so<00:02:31.920> for<00:02:32.080> example<00:02:32.480> if<00:02:32.560> you 00:02:32.710 --> 00:02:32.720 align:start position:0% particular service so for example if you 00:02:32.720 --> 00:02:35.190 align:start position:0% particular service so for example if you just<00:02:32.840> needed<00:02:33.120> to<00:02:33.280> reveal<00:02:34.040> uh<00:02:34.480> your<00:02:34.680> country 00:02:35.190 --> 00:02:35.200 align:start position:0% just needed to reveal uh your country 00:02:35.200 --> 00:02:36.750 align:start position:0% just needed to reveal uh your country and<00:02:35.360> nothing<00:02:35.599> more<00:02:36.120> then<00:02:36.280> that's<00:02:36.400> all<00:02:36.560> that 00:02:36.750 --> 00:02:36.760 align:start position:0% and nothing more then that's all that 00:02:36.760 --> 00:02:38.350 align:start position:0% and nothing more then that's all that you<00:02:37.000> you<00:02:37.200> you<00:02:37.360> need<00:02:37.519> to 00:02:38.350 --> 00:02:38.360 align:start position:0% you you you need to 00:02:38.360 --> 00:02:41.910 align:start position:0% you you you need to diss<00:02:39.360> um<00:02:39.840> and<00:02:40.000> what<00:02:40.120> if<00:02:40.239> you<00:02:40.400> could<00:02:40.959> generate 00:02:41.910 --> 00:02:41.920 align:start position:0% diss um and what if you could generate 00:02:41.920 --> 00:02:46.070 align:start position:0% diss um and what if you could generate uh<00:02:42.480> unforgeable<00:02:43.480> onetime<00:02:44.159> proofs<00:02:45.159> so<00:02:45.400> onetime 00:02:46.070 --> 00:02:46.080 align:start position:0% uh unforgeable onetime proofs so onetime 00:02:46.080 --> 00:02:48.190 align:start position:0% uh unforgeable onetime proofs so onetime in<00:02:46.200> the<00:02:46.360> sense<00:02:46.680> that<00:02:46.879> you<00:02:47.000> can't<00:02:47.239> replay<00:02:47.680> these 00:02:48.190 --> 00:02:48.200 align:start position:0% in the sense that you can't replay these 00:02:48.200 --> 00:02:49.509 align:start position:0% in the sense that you can't replay these so<00:02:48.360> once<00:02:48.519> they<00:02:48.640> us<00:02:48.840> are<00:02:48.959> consumed<00:02:49.319> by<00:02:49.400> the 00:02:49.509 --> 00:02:49.519 align:start position:0% so once they us are consumed by the 00:02:49.519 --> 00:02:52.190 align:start position:0% so once they us are consumed by the service<00:02:50.400> um<00:02:50.519> they<00:02:50.640> can't<00:02:50.800> use<00:02:50.959> it<00:02:51.159> again<00:02:51.920> so 00:02:52.190 --> 00:02:52.200 align:start position:0% service um they can't use it again so 00:02:52.200 --> 00:02:53.509 align:start position:0% service um they can't use it again so unlike<00:02:52.519> a<00:02:52.680> photograph<00:02:53.239> which<00:02:53.319> could 00:02:53.509 --> 00:02:53.519 align:start position:0% unlike a photograph which could 00:02:53.519 --> 00:02:55.030 align:start position:0% unlike a photograph which could obviously<00:02:53.879> be<00:02:54.120> you<00:02:54.239> know<00:02:54.440> if<00:02:54.519> it's<00:02:54.640> stolen<00:02:55.000> it 00:02:55.030 --> 00:02:55.040 align:start position:0% obviously be you know if it's stolen it 00:02:55.040 --> 00:02:55.869 align:start position:0% obviously be you know if it's stolen it could<00:02:55.159> be 00:02:55.869 --> 00:02:55.879 align:start position:0% could be 00:02:55.879 --> 00:02:57.630 align:start position:0% could be reused 00:02:57.630 --> 00:02:57.640 align:start position:0% reused 00:02:57.640 --> 00:02:59.630 align:start position:0% reused um<00:02:58.640> what<00:02:58.720> if<00:02:58.840> you<00:02:58.959> could<00:02:59.120> prove<00:02:59.360> that<00:02:59.440> you're<00:02:59.560> a 00:02:59.630 --> 00:02:59.640 align:start position:0% um what if you could prove that you're a 00:02:59.640 --> 00:03:02.830 align:start position:0% um what if you could prove that you're a person<00:02:59.879> person<00:03:00.480> and<00:03:00.680> and<00:03:00.800> not<00:03:00.920> an<00:03:01.080> AI<00:03:01.720> or<00:03:01.879> a<00:03:02.080> bot 00:03:02.830 --> 00:03:02.840 align:start position:0% person person and and not an AI or a bot 00:03:02.840 --> 00:03:04.869 align:start position:0% person person and and not an AI or a bot who<00:03:03.000> holds<00:03:03.200> a<00:03:03.319> valid<00:03:03.599> passport<00:03:04.319> and<00:03:04.480> reveal 00:03:04.869 --> 00:03:04.879 align:start position:0% who holds a valid passport and reveal 00:03:04.879 --> 00:03:07.030 align:start position:0% who holds a valid passport and reveal nothing<00:03:05.120> else<00:03:05.319> about 00:03:07.030 --> 00:03:07.040 align:start position:0% nothing else about 00:03:07.040 --> 00:03:08.910 align:start position:0% nothing else about yourself<00:03:08.040> um<00:03:08.200> and<00:03:08.319> what<00:03:08.440> if<00:03:08.519> you<00:03:08.599> could<00:03:08.720> use 00:03:08.910 --> 00:03:08.920 align:start position:0% yourself um and what if you could use 00:03:08.920 --> 00:03:10.430 align:start position:0% yourself um and what if you could use this<00:03:09.080> on 00:03:10.430 --> 00:03:10.440 align:start position:0% this on 00:03:10.440 --> 00:03:12.430 align:start position:0% this on Shane<00:03:11.440> I<00:03:11.519> think<00:03:11.640> we'd<00:03:11.799> all<00:03:11.920> agree<00:03:12.200> in<00:03:12.319> this 00:03:12.430 --> 00:03:12.440 align:start position:0% Shane I think we'd all agree in this 00:03:12.440 --> 00:03:14.949 align:start position:0% Shane I think we'd all agree in this room<00:03:12.799> that<00:03:13.400> that<00:03:13.560> would<00:03:13.680> be<00:03:13.920> pretty<00:03:14.159> damn 00:03:14.949 --> 00:03:14.959 align:start position:0% room that that would be pretty damn 00:03:14.959 --> 00:03:17.789 align:start position:0% room that that would be pretty damn cool<00:03:15.959> and<00:03:16.120> so<00:03:16.599> uh<00:03:17.040> okay<00:03:17.200> Mike<00:03:17.440> that's<00:03:17.640> great 00:03:17.789 --> 00:03:17.799 align:start position:0% cool and so uh okay Mike that's great 00:03:17.799 --> 00:03:19.190 align:start position:0% cool and so uh okay Mike that's great that<00:03:17.920> sounds<00:03:18.159> wonderful<00:03:18.560> but<00:03:18.680> like<00:03:18.840> how<00:03:18.920> do<00:03:19.040> we 00:03:19.190 --> 00:03:19.200 align:start position:0% that sounds wonderful but like how do we 00:03:19.200 --> 00:03:20.589 align:start position:0% that sounds wonderful but like how do we actually<00:03:19.440> get 00:03:20.589 --> 00:03:20.599 align:start position:0% actually get 00:03:20.599 --> 00:03:23.149 align:start position:0% actually get there<00:03:21.599> great<00:03:21.840> question<00:03:22.159> Mike<00:03:22.640> well<00:03:22.799> let<00:03:22.920> me 00:03:23.149 --> 00:03:23.159 align:start position:0% there great question Mike well let me 00:03:23.159 --> 00:03:26.869 align:start position:0% there great question Mike well let me let<00:03:23.239> me<00:03:23.799> explain<00:03:24.920> so<00:03:25.920> most<00:03:26.159> people<00:03:26.599> might<00:03:26.720> not 00:03:26.869 --> 00:03:26.879 align:start position:0% let me explain so most people might not 00:03:26.879 --> 00:03:28.429 align:start position:0% let me explain so most people might not be<00:03:27.000> aware<00:03:27.239> of<00:03:27.400> this<00:03:27.599> although<00:03:27.879> maybe<00:03:28.080> you<00:03:28.200> are 00:03:28.429 --> 00:03:28.439 align:start position:0% be aware of this although maybe you are 00:03:28.439 --> 00:03:31.030 align:start position:0% be aware of this although maybe you are now<00:03:28.959> um<00:03:29.799> given<00:03:30.280> the<00:03:30.360> booth<00:03:30.599> and<00:03:30.799> there's<00:03:30.959> you 00:03:31.030 --> 00:03:31.040 align:start position:0% now um given the booth and there's you 00:03:31.040 --> 00:03:32.869 align:start position:0% now um given the booth and there's you know<00:03:31.159> kind<00:03:31.280> of<00:03:31.400> more<00:03:31.599> more<00:03:31.760> awareness<00:03:32.159> of<00:03:32.360> this 00:03:32.869 --> 00:03:32.879 align:start position:0% know kind of more more awareness of this 00:03:32.879 --> 00:03:35.949 align:start position:0% know kind of more more awareness of this but<00:03:33.120> everybody<00:03:33.640> in<00:03:33.799> this<00:03:34.040> room<00:03:34.879> um<00:03:35.239> on<00:03:35.480> your 00:03:35.949 --> 00:03:35.959 align:start position:0% but everybody in this room um on your 00:03:35.959 --> 00:03:38.110 align:start position:0% but everybody in this room um on your your<00:03:36.159> passports<00:03:37.159> your<00:03:37.319> e<00:03:37.599> passports<00:03:38.000> that 00:03:38.110 --> 00:03:38.120 align:start position:0% your passports your e passports that 00:03:38.120 --> 00:03:40.070 align:start position:0% your passports your e passports that were<00:03:38.200> issued<00:03:38.480> by<00:03:38.560> your<00:03:38.840> government<00:03:39.840> on<00:03:39.959> the 00:03:40.070 --> 00:03:40.080 align:start position:0% were issued by your government on the 00:03:40.080 --> 00:03:41.949 align:start position:0% were issued by your government on the NFC<00:03:40.519> chip<00:03:40.920> there's<00:03:41.120> your<00:03:41.319> personal 00:03:41.949 --> 00:03:41.959 align:start position:0% NFC chip there's your personal 00:03:41.959 --> 00:03:44.670 align:start position:0% NFC chip there's your personal information<00:03:42.959> and<00:03:43.640> your<00:03:43.920> issuing<00:03:44.319> government 00:03:44.670 --> 00:03:44.680 align:start position:0% information and your issuing government 00:03:44.680 --> 00:03:46.309 align:start position:0% information and your issuing government has<00:03:44.840> digitally<00:03:45.239> signed<00:03:45.519> over<00:03:45.760> this 00:03:46.309 --> 00:03:46.319 align:start position:0% has digitally signed over this 00:03:46.319 --> 00:03:48.550 align:start position:0% has digitally signed over this information<00:03:47.319> essentially<00:03:47.720> attesting<00:03:48.120> to<00:03:48.319> its 00:03:48.550 --> 00:03:48.560 align:start position:0% information essentially attesting to its 00:03:48.560 --> 00:03:50.190 align:start position:0% information essentially attesting to its authenticity<00:03:49.280> and<00:03:49.400> creating<00:03:49.680> like<00:03:49.760> a<00:03:49.879> tamper 00:03:50.190 --> 00:03:50.200 align:start position:0% authenticity and creating like a tamper 00:03:50.200 --> 00:03:51.309 align:start position:0% authenticity and creating like a tamper proof 00:03:51.309 --> 00:03:51.319 align:start position:0% proof 00:03:51.319 --> 00:03:54.069 align:start position:0% proof seal<00:03:52.319> so<00:03:52.920> we're<00:03:53.159> able 00:03:54.069 --> 00:03:54.079 align:start position:0% seal so we're able 00:03:54.079 --> 00:03:56.390 align:start position:0% seal so we're able to<00:03:55.079> verify<00:03:55.560> the 00:03:56.390 --> 00:03:56.400 align:start position:0% to verify the 00:03:56.400 --> 00:03:59.390 align:start position:0% to verify the signatures<00:03:57.480> um<00:03:58.480> we<00:03:58.640> leverage<00:03:59.000> this<00:03:59.159> existing 00:03:59.390 --> 00:03:59.400 align:start position:0% signatures um we leverage this existing 00:03:59.400 --> 00:04:01.990 align:start position:0% signatures um we leverage this existing INF<00:03:59.799> structure<00:04:00.720> um<00:04:01.079> of<00:04:01.319> essentially<00:04:01.720> like<00:04:01.840> a 00:04:01.990 --> 00:04:02.000 align:start position:0% INF structure um of essentially like a 00:04:02.000 --> 00:04:04.710 align:start position:0% INF structure um of essentially like a government<00:04:02.879> signatures<00:04:03.439> and<00:04:03.879> root 00:04:04.710 --> 00:04:04.720 align:start position:0% government signatures and root 00:04:04.720 --> 00:04:06.630 align:start position:0% government signatures and root certificates<00:04:05.720> um<00:04:06.040> that<00:04:06.120> are<00:04:06.239> used<00:04:06.519> by 00:04:06.630 --> 00:04:06.640 align:start position:0% certificates um that are used by 00:04:06.640 --> 00:04:08.910 align:start position:0% certificates um that are used by airports<00:04:07.079> around<00:04:07.319> the<00:04:07.400> world<00:04:07.760> every<00:04:08.000> day<00:04:08.599> for 00:04:08.910 --> 00:04:08.920 align:start position:0% airports around the world every day for 00:04:08.920 --> 00:04:10.350 align:start position:0% airports around the world every day for by<00:04:09.079> by<00:04:09.200> governments<00:04:09.599> to<00:04:09.760> protect<00:04:10.239> their 00:04:10.350 --> 00:04:10.360 align:start position:0% by by governments to protect their 00:04:10.360 --> 00:04:12.069 align:start position:0% by by governments to protect their borders<00:04:11.200> that's<00:04:11.319> a<00:04:11.439> kind<00:04:11.560> of<00:04:11.640> level<00:04:11.840> of 00:04:12.069 --> 00:04:12.079 align:start position:0% borders that's a kind of level of 00:04:12.079 --> 00:04:14.229 align:start position:0% borders that's a kind of level of security<00:04:13.079> we<00:04:13.280> we<00:04:13.400> take<00:04:13.599> these<00:04:13.760> signatures<00:04:14.120> and 00:04:14.229 --> 00:04:14.239 align:start position:0% security we we take these signatures and 00:04:14.239 --> 00:04:17.509 align:start position:0% security we we take these signatures and we<00:04:14.319> can<00:04:14.480> verify<00:04:15.040> them<00:04:16.040> um<00:04:16.479> in<00:04:16.680> zero 00:04:17.509 --> 00:04:17.519 align:start position:0% we can verify them um in zero 00:04:17.519 --> 00:04:19.430 align:start position:0% we can verify them um in zero knowledge<00:04:18.519> and<00:04:18.680> then<00:04:18.880> and<00:04:18.959> then<00:04:19.079> eventually 00:04:19.430 --> 00:04:19.440 align:start position:0% knowledge and then and then eventually 00:04:19.440 --> 00:04:21.629 align:start position:0% knowledge and then and then eventually we<00:04:19.560> can<00:04:19.959> M<00:04:20.320> another<00:04:20.519> circuit<00:04:20.840> we<00:04:20.919> can<00:04:21.079> disclose 00:04:21.629 --> 00:04:21.639 align:start position:0% we can M another circuit we can disclose 00:04:21.639 --> 00:04:23.510 align:start position:0% we can M another circuit we can disclose that<00:04:22.079> um 00:04:23.510 --> 00:04:23.520 align:start position:0% that um 00:04:23.520 --> 00:04:25.749 align:start position:0% that um selectively<00:04:24.520> and<00:04:24.759> this<00:04:24.919> allows<00:04:25.320> the<00:04:25.440> creation 00:04:25.749 --> 00:04:25.759 align:start position:0% selectively and this allows the creation 00:04:25.759 --> 00:04:28.270 align:start position:0% selectively and this allows the creation of<00:04:25.960> these<00:04:26.199> private<00:04:26.680> and<00:04:27.080> unforgeable<00:04:27.759> proofs 00:04:28.270 --> 00:04:28.280 align:start position:0% of these private and unforgeable proofs 00:04:28.280 --> 00:04:31.629 align:start position:0% of these private and unforgeable proofs of<00:04:28.560> identity 00:04:31.629 --> 00:04:31.639 align:start position:0% 00:04:31.639 --> 00:04:34.550 align:start position:0% and<00:04:31.880> so<00:04:32.560> you<00:04:32.680> can<00:04:32.919> actually<00:04:33.160> leverage<00:04:33.759> this<00:04:34.320> so 00:04:34.550 --> 00:04:34.560 align:start position:0% and so you can actually leverage this so 00:04:34.560 --> 00:04:36.189 align:start position:0% and so you can actually leverage this so we're<00:04:34.759> going<00:04:34.880> to<00:04:35.000> show<00:04:35.160> you<00:04:35.400> the<00:04:35.520> app<00:04:35.759> later 00:04:36.189 --> 00:04:36.199 align:start position:0% we're going to show you the app later 00:04:36.199 --> 00:04:39.070 align:start position:0% we're going to show you the app later but<00:04:36.639> as<00:04:36.759> a<00:04:36.919> developer<00:04:37.919> you<00:04:38.039> can<00:04:38.320> easily 00:04:39.070 --> 00:04:39.080 align:start position:0% but as a developer you can easily 00:04:39.080 --> 00:04:41.650 align:start position:0% but as a developer you can easily integrate<00:04:39.680> this<00:04:40.280> can<00:04:40.360> you<00:04:40.479> just<00:04:40.960> oh<00:04:41.080> yeah 00:04:41.650 --> 00:04:41.660 align:start position:0% integrate this can you just oh yeah 00:04:41.660 --> 00:04:43.390 align:start position:0% integrate this can you just oh yeah [Music] 00:04:43.390 --> 00:04:43.400 align:start position:0% [Music] 00:04:43.400 --> 00:04:46.510 align:start position:0% [Music] sorry<00:04:44.400> so<00:04:44.639> we<00:04:44.800> have<00:04:45.000> built<00:04:45.360> like<00:04:45.479> a<00:04:45.720> SDK<00:04:46.400> which 00:04:46.510 --> 00:04:46.520 align:start position:0% sorry so we have built like a SDK which 00:04:46.520 --> 00:04:48.749 align:start position:0% sorry so we have built like a SDK which is<00:04:46.639> going<00:04:46.759> to<00:04:46.919> be<00:04:47.160> usable<00:04:47.720> easily<00:04:48.080> to<00:04:48.320> easy<00:04:48.560> to 00:04:48.749 --> 00:04:48.759 align:start position:0% is going to be usable easily to easy to 00:04:48.759 --> 00:04:50.909 align:start position:0% is going to be usable easily to easy to plug<00:04:49.120> for<00:04:49.360> any<00:04:49.720> JavaScript<00:04:50.320> or<00:04:50.639> web 00:04:50.909 --> 00:04:50.919 align:start position:0% plug for any JavaScript or web 00:04:50.919 --> 00:04:52.790 align:start position:0% plug for any JavaScript or web developers<00:04:51.919> whether<00:04:52.160> it's<00:04:52.280> in<00:04:52.360> the<00:04:52.479> context 00:04:52.790 --> 00:04:52.800 align:start position:0% developers whether it's in the context 00:04:52.800 --> 00:04:54.909 align:start position:0% developers whether it's in the context of<00:04:52.919> web<00:04:53.080> two<00:04:53.280> or<00:04:53.400> web<00:04:53.720> web<00:04:53.919> 3<00:04:54.280> whatever<00:04:54.639> kind<00:04:54.759> of 00:04:54.909 --> 00:04:54.919 align:start position:0% of web two or web web 3 whatever kind of 00:04:54.919 --> 00:04:57.950 align:start position:0% of web two or web web 3 whatever kind of web<00:04:55.320> app<00:04:56.320> so<00:04:56.520> it's<00:04:56.720> really<00:04:57.039> friendly<00:04:57.600> strongly 00:04:57.950 --> 00:04:57.960 align:start position:0% web app so it's really friendly strongly 00:04:57.960 --> 00:05:01.670 align:start position:0% web app so it's really friendly strongly type<00:04:58.280> typescript<00:04:58.759> SDK<00:04:59.240> so<00:04:59.680> itive<00:05:00.039> to<00:05:00.240> use<00:05:00.880> to 00:05:01.670 --> 00:05:01.680 align:start position:0% type typescript SDK so itive to use to 00:05:01.680 --> 00:05:03.670 align:start position:0% type typescript SDK so itive to use to choose<00:05:02.039> which<00:05:02.199> kind<00:05:02.320> of<00:05:02.479> field<00:05:02.800> you<00:05:02.960> need<00:05:03.479> from 00:05:03.670 --> 00:05:03.680 align:start position:0% choose which kind of field you need from 00:05:03.680 --> 00:05:05.230 align:start position:0% choose which kind of field you need from the<00:05:03.840> passport<00:05:04.360> what<00:05:04.440> kind<00:05:04.560> of<00:05:04.720> information 00:05:05.230 --> 00:05:05.240 align:start position:0% the passport what kind of information 00:05:05.240 --> 00:05:06.870 align:start position:0% the passport what kind of information you 00:05:06.870 --> 00:05:06.880 align:start position:0% you 00:05:06.880 --> 00:05:09.990 align:start position:0% you want<00:05:07.880> it's<00:05:08.039> going<00:05:08.160> to<00:05:08.639> really<00:05:08.880> unlock<00:05:09.479> like<00:05:09.880> a 00:05:09.990 --> 00:05:10.000 align:start position:0% want it's going to really unlock like a 00:05:10.000 --> 00:05:11.469 align:start position:0% want it's going to really unlock like a lot<00:05:10.120> of<00:05:10.240> interesting<00:05:10.600> use<00:05:10.919> case<00:05:11.120> we<00:05:11.240> thought 00:05:11.469 --> 00:05:11.479 align:start position:0% lot of interesting use case we thought 00:05:11.479 --> 00:05:13.629 align:start position:0% lot of interesting use case we thought about<00:05:11.759> some<00:05:12.560> uh<00:05:12.720> but<00:05:12.880> we<00:05:13.039> really<00:05:13.240> curious<00:05:13.520> to 00:05:13.629 --> 00:05:13.639 align:start position:0% about some uh but we really curious to 00:05:13.639 --> 00:05:14.990 align:start position:0% about some uh but we really curious to see<00:05:13.800> what<00:05:13.960> people<00:05:14.160> can<00:05:14.320> build<00:05:14.560> with<00:05:14.680> it<00:05:14.840> maybe 00:05:14.990 --> 00:05:15.000 align:start position:0% see what people can build with it maybe 00:05:15.000 --> 00:05:16.150 align:start position:0% see what people can build with it maybe they're<00:05:15.160> going<00:05:15.240> to<00:05:15.360> come<00:05:15.479> up<00:05:15.680> with<00:05:15.800> something 00:05:16.150 --> 00:05:16.160 align:start position:0% they're going to come up with something 00:05:16.160 --> 00:05:17.430 align:start position:0% they're going to come up with something we<00:05:16.320> didn't<00:05:16.600> think<00:05:16.880> about<00:05:17.120> so<00:05:17.320> that's 00:05:17.430 --> 00:05:17.440 align:start position:0% we didn't think about so that's 00:05:17.440 --> 00:05:19.110 align:start position:0% we didn't think about so that's something<00:05:17.800> very<00:05:18.000> curious 00:05:19.110 --> 00:05:19.120 align:start position:0% something very curious 00:05:19.120 --> 00:05:22.390 align:start position:0% something very curious about<00:05:20.120> and<00:05:20.400> this<00:05:20.479> is<00:05:20.680> fully<00:05:21.240> nonprofit<00:05:22.039> public 00:05:22.390 --> 00:05:22.400 align:start position:0% about and this is fully nonprofit public 00:05:22.400 --> 00:05:24.309 align:start position:0% about and this is fully nonprofit public goods<00:05:22.720> so<00:05:22.960> it's<00:05:23.120> like<00:05:23.319> free<00:05:23.680> to<00:05:23.840> use<00:05:24.160> there's 00:05:24.309 --> 00:05:24.319 align:start position:0% goods so it's like free to use there's 00:05:24.319 --> 00:05:26.309 align:start position:0% goods so it's like free to use there's no<00:05:24.520> restriction<00:05:25.080> there's<00:05:25.280> no<00:05:25.639> payment 00:05:26.309 --> 00:05:26.319 align:start position:0% no restriction there's no payment 00:05:26.319 --> 00:05:28.029 align:start position:0% no restriction there's no payment nothing<00:05:26.759> you<00:05:26.919> just<00:05:27.160> plug<00:05:27.400> it<00:05:27.520> in<00:05:27.759> and<00:05:27.880> you're 00:05:28.029 --> 00:05:28.039 align:start position:0% nothing you just plug it in and you're 00:05:28.039 --> 00:05:31.150 align:start position:0% nothing you just plug it in and you're free<00:05:28.240> to<00:05:28.400> go<00:05:28.639> no<00:05:28.800> API<00:05:29.199> key<00:05:29.360> whats 00:05:31.150 --> 00:05:31.160 align:start position:0% free to go no API key whats 00:05:31.160 --> 00:05:34.029 align:start position:0% free to go no API key whats ever<00:05:32.160> so<00:05:32.400> here's<00:05:32.639> an<00:05:32.840> example<00:05:33.280> of<00:05:33.520> how<00:05:33.919> it 00:05:34.029 --> 00:05:34.039 align:start position:0% ever so here's an example of how it 00:05:34.039 --> 00:05:35.950 align:start position:0% ever so here's an example of how it would<00:05:34.240> look<00:05:34.520> so<00:05:34.840> as<00:05:35.000> a<00:05:35.120> first<00:05:35.360> version<00:05:35.639> of<00:05:35.759> our 00:05:35.950 --> 00:05:35.960 align:start position:0% would look so as a first version of our 00:05:35.960 --> 00:05:38.270 align:start position:0% would look so as a first version of our SDK<00:05:36.639> typescript<00:05:37.160> so<00:05:37.360> you<00:05:37.720> specify<00:05:38.160> your 00:05:38.270 --> 00:05:38.280 align:start position:0% SDK typescript so you specify your 00:05:38.280 --> 00:05:40.550 align:start position:0% SDK typescript so you specify your domain<00:05:38.600> name<00:05:39.160> the<00:05:39.319> name<00:05:39.720> the<00:05:39.919> purpose<00:05:40.240> of<00:05:40.440> what 00:05:40.550 --> 00:05:40.560 align:start position:0% domain name the name the purpose of what 00:05:40.560 --> 00:05:43.189 align:start position:0% domain name the name the purpose of what you're<00:05:40.680> trying<00:05:40.960> to<00:05:41.160> do<00:05:41.479> with<00:05:42.280> what<00:05:42.520> the<00:05:42.680> PE<00:05:42.960> the 00:05:43.189 --> 00:05:43.199 align:start position:0% you're trying to do with what the PE the 00:05:43.199 --> 00:05:45.270 align:start position:0% you're trying to do with what the PE the visitors<00:05:43.600> or<00:05:43.880> users<00:05:44.280> of<00:05:44.440> your 00:05:45.270 --> 00:05:45.280 align:start position:0% visitors or users of your 00:05:45.280 --> 00:05:48.510 align:start position:0% visitors or users of your website<00:05:46.280> and<00:05:46.680> you<00:05:46.800> will<00:05:47.080> get<00:05:47.520> the<00:05:47.639> URL<00:05:48.360> which 00:05:48.510 --> 00:05:48.520 align:start position:0% website and you will get the URL which 00:05:48.520 --> 00:05:50.550 align:start position:0% website and you will get the URL which encodes<00:05:49.000> all<00:05:49.199> the<00:05:49.360> parameters<00:05:49.919> you<00:05:50.120> requested 00:05:50.550 --> 00:05:50.560 align:start position:0% encodes all the parameters you requested 00:05:50.560 --> 00:05:52.510 align:start position:0% encodes all the parameters you requested all<00:05:50.800> the<00:05:50.880> fields<00:05:51.160> you<00:05:51.280> paramed<00:05:52.240> and<00:05:52.319> then<00:05:52.440> you 00:05:52.510 --> 00:05:52.520 align:start position:0% all the fields you paramed and then you 00:05:52.520 --> 00:05:55.150 align:start position:0% all the fields you paramed and then you can<00:05:52.680> encode<00:05:53.039> that<00:05:53.160> into<00:05:53.880> QR<00:05:54.240> code<00:05:54.880> and<00:05:55.000> that 00:05:55.150 --> 00:05:55.160 align:start position:0% can encode that into QR code and that 00:05:55.160 --> 00:05:57.070 align:start position:0% can encode that into QR code and that the<00:05:55.240> user<00:05:55.520> scan<00:05:55.800> it<00:05:56.160> from<00:05:56.400> the 00:05:57.070 --> 00:05:57.080 align:start position:0% the user scan it from the 00:05:57.080 --> 00:05:58.909 align:start position:0% the user scan it from the app<00:05:58.080> and<00:05:58.199> then<00:05:58.319> you<00:05:58.440> will<00:05:58.639> get<00:05:58.800> the 00:05:58.909 --> 00:05:58.919 align:start position:0% app and then you will get the 00:05:58.919 --> 00:06:01.550 align:start position:0% app and then you will get the information<00:05:59.479> with<00:05:59.639> with<00:05:59.960> the<00:06:00.280> proof<00:06:01.120> in<00:06:01.400> some 00:06:01.550 --> 00:06:01.560 align:start position:0% information with with the proof in some 00:06:01.560 --> 00:06:04.150 align:start position:0% information with with the proof in some of<00:06:01.680> the<00:06:01.800> Callback<00:06:02.240> like<00:06:02.400> on<00:06:02.600> prooof<00:06:03.160> generated 00:06:04.150 --> 00:06:04.160 align:start position:0% of the Callback like on prooof generated 00:06:04.160 --> 00:06:05.110 align:start position:0% of the Callback like on prooof generated that<00:06:04.319> you 00:06:05.110 --> 00:06:05.120 align:start position:0% that you 00:06:05.120 --> 00:06:07.790 align:start position:0% that you requested<00:06:06.120> uh<00:06:06.240> the<00:06:06.400> next<00:06:06.639> step<00:06:07.240> is<00:06:07.400> that<00:06:07.680> we're 00:06:07.790 --> 00:06:07.800 align:start position:0% requested uh the next step is that we're 00:06:07.800 --> 00:06:10.110 align:start position:0% requested uh the next step is that we're going<00:06:07.880> to<00:06:08.039> build<00:06:08.319> like<00:06:08.440> a<00:06:08.560> react<00:06:08.960> SDK<00:06:09.720> so<00:06:09.880> it's 00:06:10.110 --> 00:06:10.120 align:start position:0% going to build like a react SDK so it's 00:06:10.120 --> 00:06:11.670 align:start position:0% going to build like a react SDK so it's even<00:06:10.360> easier<00:06:10.680> to<00:06:10.840> use<00:06:11.160> we're<00:06:11.280> going<00:06:11.400> to<00:06:11.520> take 00:06:11.670 --> 00:06:11.680 align:start position:0% even easier to use we're going to take 00:06:11.680 --> 00:06:13.790 align:start position:0% even easier to use we're going to take care<00:06:11.800> of<00:06:11.960> all<00:06:12.080> the<00:06:12.240> UI<00:06:12.520> in<00:06:12.639> ux<00:06:13.000> flow<00:06:13.560> so<00:06:13.680> you 00:06:13.790 --> 00:06:13.800 align:start position:0% care of all the UI in ux flow so you 00:06:13.800 --> 00:06:15.629 align:start position:0% care of all the UI in ux flow so you don't<00:06:13.919> have<00:06:14.039> to<00:06:14.199> take<00:06:14.360> care<00:06:14.520> of<00:06:14.759> that<00:06:15.280> so<00:06:15.440> it's 00:06:15.629 --> 00:06:15.639 align:start position:0% don't have to take care of that so it's 00:06:15.639 --> 00:06:22.070 align:start position:0% don't have to take care of that so it's really<00:06:16.120> one<00:06:16.400> button<00:06:16.960> and<00:06:17.199> everything<00:06:17.479> will<00:06:17.639> be 00:06:22.070 --> 00:06:22.080 align:start position:0% 00:06:22.080 --> 00:06:25.469 align:start position:0% handled<00:06:23.080> cool<00:06:23.400> and<00:06:23.800> um<00:06:24.000> yeah<00:06:24.160> so<00:06:24.360> this<00:06:24.520> section 00:06:25.469 --> 00:06:25.479 align:start position:0% handled cool and um yeah so this section 00:06:25.479 --> 00:06:28.110 align:start position:0% handled cool and um yeah so this section we're<00:06:25.599> going<00:06:25.680> to<00:06:25.840> go<00:06:26.120> go<00:06:26.720> over<00:06:27.720> uh<00:06:27.840> kind<00:06:27.960> of<00:06:28.039> the 00:06:28.110 --> 00:06:28.120 align:start position:0% we're going to go go over uh kind of the 00:06:28.120 --> 00:06:30.629 align:start position:0% we're going to go go over uh kind of the differences<00:06:28.520> between<00:06:28.919> custodial<00:06:29.800> versus 00:06:30.629 --> 00:06:30.639 align:start position:0% differences between custodial versus 00:06:30.639 --> 00:06:32.909 align:start position:0% differences between custodial versus self<00:06:31.080> custodial<00:06:32.080> and<00:06:32.199> if<00:06:32.280> it<00:06:32.400> wasn't<00:06:32.639> already 00:06:32.909 --> 00:06:32.919 align:start position:0% self custodial and if it wasn't already 00:06:32.919 --> 00:06:35.670 align:start position:0% self custodial and if it wasn't already obvious<00:06:33.199> by<00:06:33.360> the<00:06:33.440> colors<00:06:33.759> that<00:06:33.880> I<00:06:34.160> chose<00:06:35.160> um 00:06:35.670 --> 00:06:35.680 align:start position:0% obvious by the colors that I chose um 00:06:35.680 --> 00:06:38.270 align:start position:0% obvious by the colors that I chose um one<00:06:35.919> is<00:06:36.479> good<00:06:36.680> and<00:06:36.840> one<00:06:37.000> is<00:06:37.199> bad<00:06:37.880> and<00:06:38.000> just<00:06:38.120> to 00:06:38.270 --> 00:06:38.280 align:start position:0% one is good and one is bad and just to 00:06:38.280 --> 00:06:41.710 align:start position:0% one is good and one is bad and just to kind<00:06:38.360> of<00:06:38.479> maybe<00:06:38.720> like<00:06:38.840> reinforce<00:06:39.520> that<00:06:40.720> uh 00:06:41.710 --> 00:06:41.720 align:start position:0% kind of maybe like reinforce that uh 00:06:41.720 --> 00:06:45.270 align:start position:0% kind of maybe like reinforce that uh yeah<00:06:42.000> this<00:06:42.120> is<00:06:42.240> the<00:06:42.440> bad<00:06:42.680> one<00:06:43.880> and<00:06:44.880> this<00:06:45.039> is<00:06:45.160> the 00:06:45.270 --> 00:06:45.280 align:start position:0% yeah this is the bad one and this is the 00:06:45.280 --> 00:06:46.029 align:start position:0% yeah this is the bad one and this is the good 00:06:46.029 --> 00:06:46.039 align:start position:0% good 00:06:46.039 --> 00:06:50.309 align:start position:0% good one<00:06:47.039> okay<00:06:47.720> so<00:06:48.160> uh<00:06:48.800> so<00:06:48.960> for<00:06:49.160> custodial<00:06:49.919> identity 00:06:50.309 --> 00:06:50.319 align:start position:0% one okay so uh so for custodial identity 00:06:50.319 --> 00:06:52.150 align:start position:0% one okay so uh so for custodial identity verification<00:06:50.960> as<00:06:51.160> kind<00:06:51.280> of<00:06:51.440> like<00:06:51.759> uh 00:06:52.150 --> 00:06:52.160 align:start position:0% verification as kind of like uh 00:06:52.160 --> 00:06:54.110 align:start position:0% verification as kind of like uh conceptually<00:06:53.160> this<00:06:53.280> is<00:06:53.440> how<00:06:53.599> it<00:06:53.720> currently 00:06:54.110 --> 00:06:54.120 align:start position:0% conceptually this is how it currently 00:06:54.120 --> 00:06:57.670 align:start position:0% conceptually this is how it currently works<00:06:55.120> so<00:06:55.240> you're<00:06:55.400> issuing<00:06:56.120> government<00:06:57.120> uh<00:06:57.560> of 00:06:57.670 --> 00:06:57.680 align:start position:0% works so you're issuing government uh of 00:06:57.680 --> 00:06:59.189 align:start position:0% works so you're issuing government uh of your<00:06:57.840> passport<00:06:58.199> or<00:06:58.400> other<00:06:58.879> government 00:06:59.189 --> 00:06:59.199 align:start position:0% your passport or other government 00:06:59.199 --> 00:07:00.869 align:start position:0% your passport or other government documents<00:06:59.840> they'll<00:07:00.000> they'll<00:07:00.240> provide<00:07:00.479> it<00:07:00.639> to 00:07:00.869 --> 00:07:00.879 align:start position:0% documents they'll they'll provide it to 00:07:00.879 --> 00:07:04.790 align:start position:0% documents they'll they'll provide it to you<00:07:01.879> and<00:07:02.240> then<00:07:03.240> you'll<00:07:03.479> be<00:07:03.960> so<00:07:04.400> also<00:07:04.680> like 00:07:04.790 --> 00:07:04.800 align:start position:0% you and then you'll be so also like 00:07:04.800 --> 00:07:06.550 align:start position:0% you and then you'll be so also like digitally<00:07:05.120> signing<00:07:05.440> over<00:07:05.599> it<00:07:05.960> in<00:07:06.199> example<00:07:06.479> of 00:07:06.550 --> 00:07:06.560 align:start position:0% digitally signing over it in example of 00:07:06.560 --> 00:07:09.070 align:start position:0% digitally signing over it in example of a<00:07:06.720> passport<00:07:07.240> or<00:07:07.360> a<00:07:07.479> national<00:07:07.759> ID<00:07:08.039> card<00:07:08.800> you'll 00:07:09.070 --> 00:07:09.080 align:start position:0% a passport or a national ID card you'll 00:07:09.080 --> 00:07:12.510 align:start position:0% a passport or a national ID card you'll then<00:07:09.840> uh<00:07:10.000> take<00:07:10.199> a<00:07:10.280> photograph<00:07:10.840> of<00:07:10.960> it<00:07:11.680> and<00:07:11.879> then 00:07:12.510 --> 00:07:12.520 align:start position:0% then uh take a photograph of it and then 00:07:12.520 --> 00:07:14.670 align:start position:0% then uh take a photograph of it and then you'll<00:07:12.800> provide<00:07:13.039> that<00:07:13.160> to<00:07:13.280> a<00:07:13.400> kyc<00:07:13.919> provider 00:07:14.670 --> 00:07:14.680 align:start position:0% you'll provide that to a kyc provider 00:07:14.680 --> 00:07:16.350 align:start position:0% you'll provide that to a kyc provider who<00:07:14.840> will<00:07:15.039> then<00:07:15.680> maybe<00:07:15.840> do<00:07:16.080> a<00:07:16.160> bunch<00:07:16.280> of 00:07:16.350 --> 00:07:16.360 align:start position:0% who will then maybe do a bunch of 00:07:16.360 --> 00:07:18.990 align:start position:0% who will then maybe do a bunch of lookups<00:07:16.720> in<00:07:16.759> a<00:07:16.879> private<00:07:17.199> database<00:07:18.199> and<00:07:18.360> then 00:07:18.990 --> 00:07:19.000 align:start position:0% lookups in a private database and then 00:07:19.000 --> 00:07:20.150 align:start position:0% lookups in a private database and then eventually<00:07:19.319> they'll<00:07:19.560> just<00:07:19.720> kind<00:07:19.800> of<00:07:19.919> let<00:07:20.039> the 00:07:20.150 --> 00:07:20.160 align:start position:0% eventually they'll just kind of let the 00:07:20.160 --> 00:07:22.309 align:start position:0% eventually they'll just kind of let the service<00:07:20.520> know<00:07:21.199> um<00:07:21.520> you<00:07:21.599> know<00:07:21.840> Yep<00:07:22.080> this<00:07:22.160> is 00:07:22.309 --> 00:07:22.319 align:start position:0% service know um you know Yep this is 00:07:22.319 --> 00:07:26.350 align:start position:0% service know um you know Yep this is Michael<00:07:22.960> no<00:07:23.280> this<00:07:23.400> is<00:07:23.599> not<00:07:24.520> um<00:07:25.280> and<00:07:26.000> the<00:07:26.120> issue 00:07:26.350 --> 00:07:26.360 align:start position:0% Michael no this is not um and the issue 00:07:26.360 --> 00:07:29.230 align:start position:0% Michael no this is not um and the issue with<00:07:26.520> this<00:07:26.680> model<00:07:27.080> here<00:07:27.759> is<00:07:27.960> you<00:07:28.160> have<00:07:28.319> a<00:07:28.840> like 00:07:29.230 --> 00:07:29.240 align:start position:0% with this model here is you have a like 00:07:29.240 --> 00:07:31.029 align:start position:0% with this model here is you have a like it's<00:07:29.360> not<00:07:29.560> not<00:07:29.639> really<00:07:29.759> end<00:07:29.919> to<00:07:30.000> end<00:07:30.599> and<00:07:30.879> so 00:07:31.029 --> 00:07:31.039 align:start position:0% it's not not really end to end and so 00:07:31.039 --> 00:07:32.790 align:start position:0% it's not not really end to end and so you<00:07:31.160> lose<00:07:31.400> the<00:07:31.560> trust 00:07:32.790 --> 00:07:32.800 align:start position:0% you lose the trust 00:07:32.800 --> 00:07:34.670 align:start position:0% you lose the trust Providence<00:07:33.800> uh<00:07:33.960> along<00:07:34.160> the<00:07:34.319> route<00:07:34.520> through 00:07:34.670 --> 00:07:34.680 align:start position:0% Providence uh along the route through 00:07:34.680 --> 00:07:36.869 align:start position:0% Providence uh along the route through this<00:07:35.240> counterparty<00:07:36.240> so<00:07:36.400> it's<00:07:36.520> kind<00:07:36.639> of<00:07:36.759> like 00:07:36.869 --> 00:07:36.879 align:start position:0% this counterparty so it's kind of like 00:07:36.879 --> 00:07:38.029 align:start position:0% this counterparty so it's kind of like it's<00:07:37.039> wasted<00:07:37.400> because<00:07:37.599> the<00:07:37.680> government's 00:07:38.029 --> 00:07:38.039 align:start position:0% it's wasted because the government's 00:07:38.039 --> 00:07:40.909 align:start position:0% it's wasted because the government's attesting<00:07:38.440> to<00:07:38.560> it<00:07:38.800> originally<00:07:39.759> and<00:07:39.919> then<00:07:40.800> that 00:07:40.909 --> 00:07:40.919 align:start position:0% attesting to it originally and then that 00:07:40.919 --> 00:07:42.469 align:start position:0% attesting to it originally and then that gets<00:07:41.120> broken<00:07:41.520> when<00:07:41.759> you<00:07:41.919> have<00:07:42.080> this<00:07:42.240> third 00:07:42.469 --> 00:07:42.479 align:start position:0% gets broken when you have this third 00:07:42.479 --> 00:07:44.749 align:start position:0% gets broken when you have this third party<00:07:42.759> that<00:07:42.879> has<00:07:43.000> to<00:07:43.120> re<00:07:43.280> attest<00:07:43.560> to<00:07:43.720> it<00:07:44.639> uh 00:07:44.749 --> 00:07:44.759 align:start position:0% party that has to re attest to it uh 00:07:44.759 --> 00:07:46.230 align:start position:0% party that has to re attest to it uh there's<00:07:44.879> a<00:07:45.000> Reliance<00:07:45.319> on<00:07:45.479> this<00:07:45.680> this<00:07:45.840> third 00:07:46.230 --> 00:07:46.240 align:start position:0% there's a Reliance on this this third 00:07:46.240 --> 00:07:48.869 align:start position:0% there's a Reliance on this this third party<00:07:47.240> another<00:07:47.520> downside<00:07:47.960> is<00:07:48.280> is<00:07:48.400> it's<00:07:48.520> all<00:07:48.680> or 00:07:48.869 --> 00:07:48.879 align:start position:0% party another downside is is it's all or 00:07:48.879 --> 00:07:49.950 align:start position:0% party another downside is is it's all or nothing<00:07:49.159> so<00:07:49.280> you're<00:07:49.400> taking<00:07:49.720> you<00:07:49.800> know<00:07:49.919> a 00:07:49.950 --> 00:07:49.960 align:start position:0% nothing so you're taking you know a 00:07:49.960 --> 00:07:52.070 align:start position:0% nothing so you're taking you know a whole<00:07:50.120> photograph<00:07:50.639> of<00:07:50.759> the 00:07:52.070 --> 00:07:52.080 align:start position:0% whole photograph of the 00:07:52.080 --> 00:07:55.149 align:start position:0% whole photograph of the passport<00:07:53.080> um<00:07:53.479> fraud<00:07:53.759> is<00:07:53.919> much<00:07:54.080> easier<00:07:55.000> with 00:07:55.149 --> 00:07:55.159 align:start position:0% passport um fraud is much easier with 00:07:55.159 --> 00:07:56.710 align:start position:0% passport um fraud is much easier with this<00:07:55.360> approach<00:07:55.919> because<00:07:56.240> like<00:07:56.319> I<00:07:56.400> mentioned 00:07:56.710 --> 00:07:56.720 align:start position:0% this approach because like I mentioned 00:07:56.720 --> 00:07:58.149 align:start position:0% this approach because like I mentioned before<00:07:57.000> generative<00:07:57.440> AI<00:07:57.759> you<00:07:57.879> know<00:07:58.000> that's 00:07:58.149 --> 00:07:58.159 align:start position:0% before generative AI you know that's 00:07:58.159 --> 00:08:00.629 align:start position:0% before generative AI you know that's coming<00:07:58.639> it's<00:07:58.759> going<00:07:58.879> to<00:07:58.960> get<00:07:59.120> better 00:08:00.629 --> 00:08:00.639 align:start position:0% coming it's going to get better 00:08:00.639 --> 00:08:02.589 align:start position:0% coming it's going to get better uh<00:08:00.960> it's<00:08:01.120> also<00:08:01.400> quite<00:08:01.599> expensive<00:08:02.280> so 00:08:02.589 --> 00:08:02.599 align:start position:0% uh it's also quite expensive so 00:08:02.599 --> 00:08:03.670 align:start position:0% uh it's also quite expensive so sometimes<00:08:02.800> they<00:08:02.879> need<00:08:03.000> to<00:08:03.120> fall<00:08:03.360> back<00:08:03.479> to 00:08:03.670 --> 00:08:03.680 align:start position:0% sometimes they need to fall back to 00:08:03.680 --> 00:08:05.550 align:start position:0% sometimes they need to fall back to manual<00:08:04.120> verification<00:08:04.919> which<00:08:05.080> can<00:08:05.280> can<00:08:05.400> be 00:08:05.550 --> 00:08:05.560 align:start position:0% manual verification which can can be 00:08:05.560 --> 00:08:06.990 align:start position:0% manual verification which can can be costly<00:08:05.840> for<00:08:05.960> businesses<00:08:06.680> which<00:08:06.800> doesn't 00:08:06.990 --> 00:08:07.000 align:start position:0% costly for businesses which doesn't 00:08:07.000 --> 00:08:08.230 align:start position:0% costly for businesses which doesn't scale<00:08:07.319> very 00:08:08.230 --> 00:08:08.240 align:start position:0% scale very 00:08:08.240 --> 00:08:10.950 align:start position:0% scale very well<00:08:09.240> and<00:08:10.080> I<00:08:10.159> guess<00:08:10.319> this<00:08:10.440> is<00:08:10.520> kind<00:08:10.639> of<00:08:10.759> like 00:08:10.950 --> 00:08:10.960 align:start position:0% well and I guess this is kind of like 00:08:10.960 --> 00:08:12.390 align:start position:0% well and I guess this is kind of like the<00:08:11.080> you<00:08:11.159> know<00:08:11.440> the<00:08:11.560> big<00:08:11.759> issue<00:08:12.000> with<00:08:12.120> it 00:08:12.390 --> 00:08:12.400 align:start position:0% the you know the big issue with it 00:08:12.400 --> 00:08:14.230 align:start position:0% the you know the big issue with it really<00:08:12.919> one<00:08:13.039> of<00:08:13.120> the<00:08:13.240> ma<00:08:13.400> major<00:08:13.680> issues<00:08:13.960> is 00:08:14.230 --> 00:08:14.240 align:start position:0% really one of the ma major issues is 00:08:14.240 --> 00:08:15.990 align:start position:0% really one of the ma major issues is you've<00:08:14.400> got<00:08:14.479> to<00:08:14.639> rely<00:08:14.879> on<00:08:15.080> them<00:08:15.479> to<00:08:15.639> keep<00:08:15.800> your 00:08:15.990 --> 00:08:16.000 align:start position:0% you've got to rely on them to keep your 00:08:16.000 --> 00:08:18.270 align:start position:0% you've got to rely on them to keep your data<00:08:16.280> safe<00:08:17.039> and<00:08:17.159> they<00:08:17.319> often<00:08:17.560> don't<00:08:18.120> which 00:08:18.270 --> 00:08:18.280 align:start position:0% data safe and they often don't which 00:08:18.280 --> 00:08:19.070 align:start position:0% data safe and they often don't which really 00:08:19.070 --> 00:08:19.080 align:start position:0% really 00:08:19.080 --> 00:08:23.149 align:start position:0% really sucks<00:08:20.080> and<00:08:20.319> so<00:08:21.479> contrasting<00:08:22.479> to<00:08:22.759> that<00:08:22.919> you've 00:08:23.149 --> 00:08:23.159 align:start position:0% sucks and so contrasting to that you've 00:08:23.159 --> 00:08:25.189 align:start position:0% sucks and so contrasting to that you've got<00:08:23.479> self-<00:08:23.800> custodial<00:08:24.720> identity 00:08:25.189 --> 00:08:25.199 align:start position:0% got self- custodial identity 00:08:25.199 --> 00:08:28.350 align:start position:0% got self- custodial identity verification<00:08:26.199> which<00:08:26.319> is<00:08:26.520> truly<00:08:27.120> end<00:08:27.360> to<00:08:27.479> end 00:08:28.350 --> 00:08:28.360 align:start position:0% verification which is truly end to end 00:08:28.360 --> 00:08:30.909 align:start position:0% verification which is truly end to end and<00:08:28.440> so<00:08:28.599> in<00:08:28.759> this<00:08:28.919> model<00:08:29.520> the<00:08:29.919> government's 00:08:30.909 --> 00:08:30.919 align:start position:0% and so in this model the government's 00:08:30.919 --> 00:08:32.110 align:start position:0% and so in this model the government's you<00:08:31.039> know<00:08:31.159> digitally<00:08:31.479> signing<00:08:31.759> over<00:08:31.960> your 00:08:32.110 --> 00:08:32.120 align:start position:0% you know digitally signing over your 00:08:32.120 --> 00:08:34.430 align:start position:0% you know digitally signing over your documents<00:08:32.479> or<00:08:33.159> attesting<00:08:33.560> to<00:08:33.800> these<00:08:34.120> facts 00:08:34.430 --> 00:08:34.440 align:start position:0% documents or attesting to these facts 00:08:34.440 --> 00:08:37.670 align:start position:0% documents or attesting to these facts about<00:08:34.959> you<00:08:35.959> and<00:08:36.360> providing<00:08:36.680> it<00:08:36.800> to<00:08:37.000> you<00:08:37.599> and 00:08:37.670 --> 00:08:37.680 align:start position:0% about you and providing it to you and 00:08:37.680 --> 00:08:41.149 align:start position:0% about you and providing it to you and then<00:08:37.800> you<00:08:37.919> can<00:08:38.200> use<00:08:39.200> uh<00:08:40.159> you<00:08:40.279> can<00:08:40.440> use<00:08:40.839> Z 00:08:41.149 --> 00:08:41.159 align:start position:0% then you can use uh you can use Z 00:08:41.159 --> 00:08:44.829 align:start position:0% then you can use uh you can use Z knowledge<00:08:41.440> proofs<00:08:41.919> here<00:08:42.959> to<00:08:43.959> uh<00:08:44.399> verify<00:08:44.720> the 00:08:44.829 --> 00:08:44.839 align:start position:0% knowledge proofs here to uh verify the 00:08:44.839 --> 00:08:46.710 align:start position:0% knowledge proofs here to uh verify the signatures<00:08:45.360> in<00:08:45.480> zero<00:08:45.720> knowledge<00:08:46.480> and<00:08:46.600> then 00:08:46.710 --> 00:08:46.720 align:start position:0% signatures in zero knowledge and then 00:08:46.720 --> 00:08:48.030 align:start position:0% signatures in zero knowledge and then selectively<00:08:47.160> reveal<00:08:47.440> what<00:08:47.560> it<00:08:47.640> is<00:08:47.760> you<00:08:47.880> want 00:08:48.030 --> 00:08:48.040 align:start position:0% selectively reveal what it is you want 00:08:48.040 --> 00:08:50.630 align:start position:0% selectively reveal what it is you want to<00:08:48.680> and<00:08:48.880> provide<00:08:49.200> that<00:08:49.360> proof<00:08:49.839> directly<00:08:50.279> to 00:08:50.630 --> 00:08:50.640 align:start position:0% to and provide that proof directly to 00:08:50.640 --> 00:08:53.030 align:start position:0% to and provide that proof directly to the<00:08:50.800> actual<00:08:51.080> service<00:08:51.600> end<00:08:51.839> to<00:08:52.000> end<00:08:52.680> there's<00:08:52.880> no 00:08:53.030 --> 00:08:53.040 align:start position:0% the actual service end to end there's no 00:08:53.040 --> 00:08:54.430 align:start position:0% the actual service end to end there's no other<00:08:53.399> uh<00:08:53.519> you<00:08:53.600> know<00:08:53.720> middleman<00:08:54.120> that<00:08:54.200> need<00:08:54.320> to 00:08:54.430 --> 00:08:54.440 align:start position:0% other uh you know middleman that need to 00:08:54.440 --> 00:08:56.190 align:start position:0% other uh you know middleman that need to be<00:08:54.519> involved<00:08:54.839> in<00:08:54.959> this<00:08:55.600> even<00:08:55.800> ask<00:08:56.000> we<00:08:56.120> just 00:08:56.190 --> 00:08:56.200 align:start position:0% be involved in this even ask we just 00:08:56.200 --> 00:08:58.230 align:start position:0% be involved in this even ask we just create<00:08:56.440> the<00:08:56.600> circuits<00:08:57.600> um<00:08:57.839> that<00:08:58.040> to 00:08:58.230 --> 00:08:58.240 align:start position:0% create the circuits um that to 00:08:58.240 --> 00:08:59.910 align:start position:0% create the circuits um that to facilitate<00:08:58.680> this<00:08:58.839> but<00:08:58.920> we<00:08:59.000> aren't<00:08:59.160> really<00:08:59.279> the 00:08:59.910 --> 00:08:59.920 align:start position:0% facilitate this but we aren't really the 00:08:59.920 --> 00:09:02.630 align:start position:0% facilitate this but we aren't really the middleman<00:09:00.920> and<00:09:01.279> another<00:09:02.040> great<00:09:02.279> way<00:09:02.399> to<00:09:02.560> kind 00:09:02.630 --> 00:09:02.640 align:start position:0% middleman and another great way to kind 00:09:02.640 --> 00:09:05.910 align:start position:0% middleman and another great way to kind of<00:09:02.800> think<00:09:03.000> about<00:09:03.480> this<00:09:04.480> is<00:09:05.160> who<00:09:05.360> better<00:09:05.600> to 00:09:05.910 --> 00:09:05.920 align:start position:0% of think about this is who better to 00:09:05.920 --> 00:09:08.470 align:start position:0% of think about this is who better to attest<00:09:06.240> to<00:09:06.480> the<00:09:06.959> attest<00:09:07.240> to<00:09:07.360> your<00:09:07.519> identity 00:09:08.470 --> 00:09:08.480 align:start position:0% attest to the attest to your identity 00:09:08.480 --> 00:09:10.750 align:start position:0% attest to the attest to your identity and<00:09:08.720> your<00:09:08.880> your<00:09:09.000> personal<00:09:09.399> information<00:09:10.399> than 00:09:10.750 --> 00:09:10.760 align:start position:0% and your your personal information than 00:09:10.760 --> 00:09:12.110 align:start position:0% and your your personal information than the<00:09:10.880> same<00:09:11.120> entity<00:09:11.480> that<00:09:11.600> issued<00:09:11.920> you<00:09:12.000> your 00:09:12.110 --> 00:09:12.120 align:start position:0% the same entity that issued you your 00:09:12.120 --> 00:09:13.750 align:start position:0% the same entity that issued you your birth<00:09:12.360> certificate<00:09:13.120> so<00:09:13.279> you<00:09:13.360> know<00:09:13.440> you<00:09:13.560> change 00:09:13.750 --> 00:09:13.760 align:start position:0% birth certificate so you know you change 00:09:13.760 --> 00:09:15.670 align:start position:0% birth certificate so you know you change your<00:09:13.920> name<00:09:14.480> or<00:09:14.560> you<00:09:14.680> get<00:09:14.800> married<00:09:15.399> who<00:09:15.480> do<00:09:15.560> you 00:09:15.670 --> 00:09:15.680 align:start position:0% your name or you get married who do you 00:09:15.680 --> 00:09:17.670 align:start position:0% your name or you get married who do you go<00:09:15.760> to<00:09:16.040> right<00:09:16.240> you<00:09:16.360> go<00:09:16.480> to<00:09:16.600> your<00:09:16.720> government 00:09:17.670 --> 00:09:17.680 align:start position:0% go to right you go to your government 00:09:17.680 --> 00:09:19.350 align:start position:0% go to right you go to your government and<00:09:17.760> it's<00:09:18.000> also<00:09:18.480> another<00:09:18.720> way<00:09:18.920> to<00:09:19.040> think<00:09:19.200> about 00:09:19.350 --> 00:09:19.360 align:start position:0% and it's also another way to think about 00:09:19.360 --> 00:09:21.430 align:start position:0% and it's also another way to think about it<00:09:19.800> it's<00:09:19.920> kind<00:09:20.040> of<00:09:20.160> decentralized<00:09:21.079> across<00:09:21.360> the 00:09:21.430 --> 00:09:21.440 align:start position:0% it it's kind of decentralized across the 00:09:21.440 --> 00:09:23.389 align:start position:0% it it's kind of decentralized across the whole<00:09:21.640> world<00:09:22.360> in<00:09:22.480> the<00:09:22.600> sense<00:09:22.880> that<00:09:23.079> each 00:09:23.389 --> 00:09:23.399 align:start position:0% whole world in the sense that each 00:09:23.399 --> 00:09:24.630 align:start position:0% whole world in the sense that each government<00:09:23.839> around<00:09:24.040> the<00:09:24.160> world<00:09:24.440> they're 00:09:24.630 --> 00:09:24.640 align:start position:0% government around the world they're 00:09:24.640 --> 00:09:26.269 align:start position:0% government around the world they're attesting<00:09:25.040> to<00:09:25.240> these<00:09:25.440> facts<00:09:25.720> about<00:09:25.920> their<00:09:26.079> own 00:09:26.269 --> 00:09:26.279 align:start position:0% attesting to these facts about their own 00:09:26.279 --> 00:09:32.190 align:start position:0% attesting to these facts about their own citizens<00:09:26.640> of<00:09:26.800> their<00:09:26.959> country 00:09:32.190 --> 00:09:32.200 align:start position:0% 00:09:32.200 --> 00:09:33.870 align:start position:0% and<00:09:32.360> so<00:09:32.560> onto<00:09:32.839> some<00:09:33.200> some<00:09:33.360> interesting<00:09:33.640> use 00:09:33.870 --> 00:09:33.880 align:start position:0% and so onto some some interesting use 00:09:33.880 --> 00:09:35.910 align:start position:0% and so onto some some interesting use cases<00:09:34.160> here<00:09:34.240> for<00:09:34.399> Z<00:09:34.800> passport<00:09:35.560> there's<00:09:35.760> really 00:09:35.910 --> 00:09:35.920 align:start position:0% cases here for Z passport there's really 00:09:35.920 --> 00:09:38.310 align:start position:0% cases here for Z passport there's really a<00:09:36.040> myriad<00:09:36.399> of<00:09:36.600> different<00:09:37.200> possibilities<00:09:38.200> um 00:09:38.310 --> 00:09:38.320 align:start position:0% a myriad of different possibilities um 00:09:38.320 --> 00:09:40.110 align:start position:0% a myriad of different possibilities um but<00:09:38.399> we'll<00:09:38.519> just<00:09:38.640> go<00:09:38.760> over<00:09:39.040> a<00:09:39.160> few<00:09:39.839> that<00:09:40.000> kind 00:09:40.110 --> 00:09:40.120 align:start position:0% but we'll just go over a few that kind 00:09:40.120 --> 00:09:41.870 align:start position:0% but we'll just go over a few that kind of<00:09:40.440> popped<00:09:40.680> out<00:09:40.800> to<00:09:40.920> us<00:09:41.079> is<00:09:41.279> quite<00:09:41.440> interesting 00:09:41.870 --> 00:09:41.880 align:start position:0% of popped out to us is quite interesting 00:09:41.880 --> 00:09:42.590 align:start position:0% of popped out to us is quite interesting and 00:09:42.590 --> 00:09:42.600 align:start position:0% and 00:09:42.600 --> 00:09:45.590 align:start position:0% and compelling<00:09:43.600> uh<00:09:43.800> private<00:09:44.320> and<00:09:44.680> compliant 00:09:45.590 --> 00:09:45.600 align:start position:0% compelling uh private and compliant 00:09:45.600 --> 00:09:47.470 align:start position:0% compelling uh private and compliant private<00:09:45.920> tokens<00:09:46.920> so<00:09:47.040> we're<00:09:47.160> currently 00:09:47.470 --> 00:09:47.480 align:start position:0% private tokens so we're currently 00:09:47.480 --> 00:09:49.470 align:start position:0% private tokens so we're currently building<00:09:47.800> out<00:09:48.480> uh<00:09:48.560> a<00:09:48.680> wallet<00:09:48.920> called<00:09:49.079> obsidian 00:09:49.470 --> 00:09:49.480 align:start position:0% building out uh a wallet called obsidian 00:09:49.480 --> 00:09:52.350 align:start position:0% building out uh a wallet called obsidian wallet<00:09:49.920> on<00:09:50.160> Aztec<00:09:50.600> Network<00:09:51.600> and<00:09:51.959> we<00:09:52.079> want<00:09:52.200> to 00:09:52.350 --> 00:09:52.360 align:start position:0% wallet on Aztec Network and we want to 00:09:52.360 --> 00:09:53.990 align:start position:0% wallet on Aztec Network and we want to have<00:09:52.560> privacy<00:09:52.880> as<00:09:52.959> the<00:09:53.120> default<00:09:53.640> and<00:09:53.720> be<00:09:53.839> able 00:09:53.990 --> 00:09:54.000 align:start position:0% have privacy as the default and be able 00:09:54.000 --> 00:09:56.190 align:start position:0% have privacy as the default and be able to<00:09:54.079> have<00:09:54.200> these<00:09:54.360> stable<00:09:54.680> coins<00:09:54.880> like<00:09:55.040> usdc<00:09:56.000> on 00:09:56.190 --> 00:09:56.200 align:start position:0% to have these stable coins like usdc on 00:09:56.200 --> 00:09:57.710 align:start position:0% to have these stable coins like usdc on ramp<00:09:56.600> and<00:09:56.720> then<00:09:56.839> be<00:09:56.959> used<00:09:57.320> completely 00:09:57.710 --> 00:09:57.720 align:start position:0% ramp and then be used completely 00:09:57.720 --> 00:09:59.910 align:start position:0% ramp and then be used completely privately<00:09:58.399> so<00:09:58.519> you<00:09:58.640> can<00:09:58.800> actually<00:09:59.079> have 00:09:59.910 --> 00:09:59.920 align:start position:0% privately so you can actually have 00:09:59.920 --> 00:10:01.790 align:start position:0% privately so you can actually have um<00:10:00.079> this<00:10:00.240> peer<00:10:00.440> to-peer<00:10:00.640> you<00:10:01.079> know<00:10:01.360> private 00:10:01.790 --> 00:10:01.800 align:start position:0% um this peer to-peer you know private 00:10:01.800 --> 00:10:04.470 align:start position:0% um this peer to-peer you know private cash<00:10:02.279> for<00:10:02.640> for<00:10:02.800> using<00:10:03.079> it<00:10:03.720> for<00:10:04.000> just<00:10:04.160> normal 00:10:04.470 --> 00:10:04.480 align:start position:0% cash for for using it for just normal 00:10:04.480 --> 00:10:05.870 align:start position:0% cash for for using it for just normal everyday<00:10:04.800> transactions<00:10:05.320> without<00:10:05.519> worrying 00:10:05.870 --> 00:10:05.880 align:start position:0% everyday transactions without worrying 00:10:05.880 --> 00:10:07.630 align:start position:0% everyday transactions without worrying about<00:10:06.519> privacy<00:10:06.920> concerns<00:10:07.200> and<00:10:07.399> everyone 00:10:07.630 --> 00:10:07.640 align:start position:0% about privacy concerns and everyone 00:10:07.640 --> 00:10:10.829 align:start position:0% about privacy concerns and everyone seeing<00:10:07.880> your<00:10:08.040> full<00:10:08.640> transaction<00:10:09.360> history<00:10:10.360> and 00:10:10.829 --> 00:10:10.839 align:start position:0% seeing your full transaction history and 00:10:10.839 --> 00:10:13.590 align:start position:0% seeing your full transaction history and so<00:10:11.839> uh<00:10:12.160> yeah<00:10:12.480> in<00:10:12.560> the<00:10:12.680> future<00:10:12.920> we<00:10:13.040> hope<00:10:13.200> to<00:10:13.360> have 00:10:13.590 --> 00:10:13.600 align:start position:0% so uh yeah in the future we hope to have 00:10:13.600 --> 00:10:16.430 align:start position:0% so uh yeah in the future we hope to have this<00:10:14.240> um<00:10:14.839> integrated<00:10:15.360> into<00:10:15.640> obsidian<00:10:16.000> wallet 00:10:16.430 --> 00:10:16.440 align:start position:0% this um integrated into obsidian wallet 00:10:16.440 --> 00:10:17.710 align:start position:0% this um integrated into obsidian wallet so<00:10:16.560> we're<00:10:16.680> going<00:10:16.760> to<00:10:16.839> have<00:10:17.000> basically<00:10:17.279> Zig 00:10:17.710 --> 00:10:17.720 align:start position:0% so we're going to have basically Zig 00:10:17.720 --> 00:10:19.590 align:start position:0% so we're going to have basically Zig passport<00:10:18.360> as<00:10:18.600> this<00:10:18.760> kind<00:10:18.880> of<00:10:19.040> first<00:10:19.320> class 00:10:19.590 --> 00:10:19.600 align:start position:0% passport as this kind of first class 00:10:19.600 --> 00:10:22.910 align:start position:0% passport as this kind of first class citizen<00:10:20.600> F<00:10:20.839> first<00:10:21.160> class<00:10:21.959> uh<00:10:22.160> citizen<00:10:22.480> for 00:10:22.910 --> 00:10:22.920 align:start position:0% citizen F first class uh citizen for 00:10:22.920 --> 00:10:25.630 align:start position:0% citizen F first class uh citizen for identity<00:10:23.920> um<00:10:24.079> as<00:10:24.240> identity<00:10:24.640> provider<00:10:25.560> that 00:10:25.630 --> 00:10:25.640 align:start position:0% identity um as identity provider that 00:10:25.640 --> 00:10:27.310 align:start position:0% identity um as identity provider that will<00:10:25.800> be<00:10:25.880> able<00:10:26.040> to<00:10:26.160> automatically<00:10:26.720> generate 00:10:27.310 --> 00:10:27.320 align:start position:0% will be able to automatically generate 00:10:27.320 --> 00:10:29.910 align:start position:0% will be able to automatically generate proofs<00:10:28.320> uh<00:10:28.519> whenever<00:10:29.040> you<00:10:29.120> know<00:10:29.720> you're 00:10:29.910 --> 00:10:29.920 align:start position:0% proofs uh whenever you know you're 00:10:29.920 --> 00:10:32.030 align:start position:0% proofs uh whenever you know you're transferring<00:10:30.720> us<00:10:31.040> usdc 00:10:32.030 --> 00:10:32.040 align:start position:0% transferring us usdc 00:10:32.040 --> 00:10:34.389 align:start position:0% transferring us usdc around<00:10:33.040> and<00:10:33.120> so<00:10:33.560> some<00:10:33.720> maybe<00:10:33.920> some<00:10:34.040> examples 00:10:34.389 --> 00:10:34.399 align:start position:0% around and so some maybe some examples 00:10:34.399 --> 00:10:36.590 align:start position:0% around and so some maybe some examples here<00:10:34.519> of<00:10:34.640> the<00:10:34.760> proofs<00:10:35.320> would<00:10:35.440> be<00:10:35.560> generated<00:10:36.440> so 00:10:36.590 --> 00:10:36.600 align:start position:0% here of the proofs would be generated so 00:10:36.600 --> 00:10:38.710 align:start position:0% here of the proofs would be generated so you'd<00:10:36.800> have<00:10:36.959> like<00:10:37.200> uh<00:10:37.440> compliance<00:10:37.920> proofs 00:10:38.710 --> 00:10:38.720 align:start position:0% you'd have like uh compliance proofs 00:10:38.720 --> 00:10:39.829 align:start position:0% you'd have like uh compliance proofs which<00:10:38.839> would<00:10:39.000> prove<00:10:39.279> maybe<00:10:39.480> that<00:10:39.560> you're<00:10:39.680> not 00:10:39.829 --> 00:10:39.839 align:start position:0% which would prove maybe that you're not 00:10:39.839 --> 00:10:42.150 align:start position:0% which would prove maybe that you're not an<00:10:40.040> ofac<00:10:40.440> scn<00:10:40.880> list<00:10:41.440> you're<00:10:41.600> not<00:10:41.760> from<00:10:42.079> a 00:10:42.150 --> 00:10:42.160 align:start position:0% an ofac scn list you're not from a 00:10:42.160 --> 00:10:44.710 align:start position:0% an ofac scn list you're not from a sanction<00:10:42.720> country<00:10:43.720> and<00:10:43.839> then<00:10:44.120> another<00:10:44.440> option 00:10:44.710 --> 00:10:44.720 align:start position:0% sanction country and then another option 00:10:44.720 --> 00:10:47.030 align:start position:0% sanction country and then another option here<00:10:44.880> could<00:10:45.040> be<00:10:45.920> maybe<00:10:46.200> using<00:10:46.560> this<00:10:46.720> unique 00:10:47.030 --> 00:10:47.040 align:start position:0% here could be maybe using this unique 00:10:47.040 --> 00:10:48.790 align:start position:0% here could be maybe using this unique identifier<00:10:47.839> that<00:10:47.920> is<00:10:48.079> the<00:10:48.160> same<00:10:48.360> for<00:10:48.519> every 00:10:48.790 --> 00:10:48.800 align:start position:0% identifier that is the same for every 00:10:48.800 --> 00:10:50.949 align:start position:0% identifier that is the same for every passport<00:10:49.720> um<00:10:49.839> but<00:10:50.000> also<00:10:50.399> completely 00:10:50.949 --> 00:10:50.959 align:start position:0% passport um but also completely 00:10:50.959 --> 00:10:53.389 align:start position:0% passport um but also completely Anonymous<00:10:51.959> you<00:10:52.120> could<00:10:52.279> track<00:10:52.680> like<00:10:52.800> transfers 00:10:53.389 --> 00:10:53.399 align:start position:0% Anonymous you could track like transfers 00:10:53.399 --> 00:10:54.949 align:start position:0% Anonymous you could track like transfers over<00:10:53.600> time<00:10:53.959> so<00:10:54.120> you<00:10:54.240> might<00:10:54.399> impose<00:10:54.760> like<00:10:54.880> a 00:10:54.949 --> 00:10:54.959 align:start position:0% over time so you might impose like a 00:10:54.959 --> 00:10:57.310 align:start position:0% over time so you might impose like a super<00:10:55.240> generous<00:10:55.680> limit<00:10:56.279> of<00:10:56.440> maybe<00:10:56.880> 100,000 00:10:57.310 --> 00:10:57.320 align:start position:0% super generous limit of maybe 100,000 00:10:57.320 --> 00:11:00.629 align:start position:0% super generous limit of maybe 100,000 usdc<00:10:58.000> per<00:10:58.160> month<00:10:58.680> that's<00:10:58.880> enough<00:10:59.040> for<00:10:59.639> 99.999% 00:11:00.629 --> 00:11:00.639 align:start position:0% usdc per month that's enough for 99.999% 00:11:00.639 --> 00:11:02.269 align:start position:0% usdc per month that's enough for 99.999% of<00:11:00.800> people<00:11:01.480> but<00:11:01.600> that's<00:11:01.720> going<00:11:01.839> to<00:11:01.920> severely 00:11:02.269 --> 00:11:02.279 align:start position:0% of people but that's going to severely 00:11:02.279 --> 00:11:04.670 align:start position:0% of people but that's going to severely limit<00:11:02.880> uh<00:11:03.040> like<00:11:03.560> you<00:11:03.639> know<00:11:03.800> Bad<00:11:03.959> actors<00:11:04.360> from 00:11:04.670 --> 00:11:04.680 align:start position:0% limit uh like you know Bad actors from 00:11:04.680 --> 00:11:06.230 align:start position:0% limit uh like you know Bad actors from from<00:11:04.959> laundering<00:11:05.360> lots<00:11:05.560> of<00:11:05.680> of<00:11:05.800> money<00:11:06.000> through 00:11:06.230 --> 00:11:06.240 align:start position:0% from laundering lots of of money through 00:11:06.240 --> 00:11:08.949 align:start position:0% from laundering lots of of money through this<00:11:07.040> and<00:11:07.480> ultimately<00:11:08.040> it's<00:11:08.240> going<00:11:08.440> to<00:11:08.680> mean 00:11:08.949 --> 00:11:08.959 align:start position:0% this and ultimately it's going to mean 00:11:08.959 --> 00:11:11.870 align:start position:0% this and ultimately it's going to mean that<00:11:09.079> you<00:11:09.200> can<00:11:09.720> off-ramp<00:11:10.240> onto<00:11:10.480> an<00:11:10.880> exchange 00:11:11.870 --> 00:11:11.880 align:start position:0% that you can off-ramp onto an exchange 00:11:11.880 --> 00:11:13.230 align:start position:0% that you can off-ramp onto an exchange and<00:11:12.120> not<00:11:12.279> have<00:11:12.399> to<00:11:12.480> be<00:11:12.600> worried<00:11:12.880> about<00:11:13.079> the 00:11:13.230 --> 00:11:13.240 align:start position:0% and not have to be worried about the 00:11:13.240 --> 00:11:15.910 align:start position:0% and not have to be worried about the exchange<00:11:14.000> you<00:11:14.120> know<00:11:14.279> Banning<00:11:14.600> your<00:11:14.920> account 00:11:15.910 --> 00:11:15.920 align:start position:0% exchange you know Banning your account 00:11:15.920 --> 00:11:17.790 align:start position:0% exchange you know Banning your account um<00:11:16.360> because<00:11:16.560> you've<00:11:16.680> used<00:11:16.959> this<00:11:17.200> this<00:11:17.320> sort<00:11:17.480> of 00:11:17.790 --> 00:11:17.800 align:start position:0% um because you've used this this sort of 00:11:17.800 --> 00:11:21.430 align:start position:0% um because you've used this this sort of this<00:11:17.959> private<00:11:18.279> and<00:11:18.519> compliant 00:11:21.430 --> 00:11:21.440 align:start position:0% 00:11:21.440 --> 00:11:24.069 align:start position:0% token<00:11:22.440> another<00:11:22.800> use<00:11:23.120> case<00:11:23.360> could<00:11:23.519> be<00:11:23.680> proof<00:11:23.920> of 00:11:24.069 --> 00:11:24.079 align:start position:0% token another use case could be proof of 00:11:24.079 --> 00:11:26.069 align:start position:0% token another use case could be proof of personhood<00:11:24.560> so<00:11:24.680> you<00:11:24.760> can<00:11:24.880> have<00:11:25.279> increased<00:11:25.680> Cil 00:11:26.069 --> 00:11:26.079 align:start position:0% personhood so you can have increased Cil 00:11:26.079 --> 00:11:28.030 align:start position:0% personhood so you can have increased Cil resistance<00:11:26.839> so<00:11:27.000> both<00:11:27.160> in<00:11:27.279> the<00:11:27.440> context<00:11:27.720> of<00:11:27.880> web 00:11:28.030 --> 00:11:28.040 align:start position:0% resistance so both in the context of web 00:11:28.040 --> 00:11:29.870 align:start position:0% resistance so both in the context of web 2<00:11:28.200> and<00:11:28.320> three<00:11:28.519> is<00:11:28.680> quite<00:11:28.880> important<00:11:29.680> you<00:11:29.800> want 00:11:29.870 --> 00:11:29.880 align:start position:0% 2 and three is quite important you want 00:11:29.880 --> 00:11:31.910 align:start position:0% 2 and three is quite important you want to<00:11:30.040> prevent<00:11:30.360> spam<00:11:30.600> and<00:11:30.800> Bots<00:11:31.440> for<00:11:31.560> example<00:11:31.839> you 00:11:31.910 --> 00:11:31.920 align:start position:0% to prevent spam and Bots for example you 00:11:31.920 --> 00:11:33.870 align:start position:0% to prevent spam and Bots for example you can<00:11:32.040> have<00:11:32.120> a<00:11:32.240> social<00:11:32.480> media<00:11:32.839> platform<00:11:33.720> that 00:11:33.870 --> 00:11:33.880 align:start position:0% can have a social media platform that 00:11:33.880 --> 00:11:36.269 align:start position:0% can have a social media platform that wants<00:11:34.079> to<00:11:34.279> really<00:11:34.519> have<00:11:34.760> one<00:11:35.040> person<00:11:35.680> and<00:11:35.920> one 00:11:36.269 --> 00:11:36.279 align:start position:0% wants to really have one person and one 00:11:36.279 --> 00:11:38.310 align:start position:0% wants to really have one person and one account<00:11:36.720> so<00:11:36.959> you<00:11:37.079> can<00:11:37.480> do<00:11:37.760> that<00:11:38.000> much<00:11:38.160> more 00:11:38.310 --> 00:11:38.320 align:start position:0% account so you can do that much more 00:11:38.320 --> 00:11:40.629 align:start position:0% account so you can do that much more easily<00:11:38.680> with<00:11:38.800> this<00:11:38.959> solution<00:11:39.839> or<00:11:40.000> like<00:11:40.200> simply 00:11:40.629 --> 00:11:40.639 align:start position:0% easily with this solution or like simply 00:11:40.639 --> 00:11:42.870 align:start position:0% easily with this solution or like simply the<00:11:40.760> use<00:11:41.040> case<00:11:41.160> we<00:11:41.320> use<00:11:41.560> now<00:11:41.839> day<00:11:41.959> a<00:11:42.120> capture 00:11:42.870 --> 00:11:42.880 align:start position:0% the use case we use now day a capture 00:11:42.880 --> 00:11:45.269 align:start position:0% the use case we use now day a capture you<00:11:42.959> could<00:11:43.160> replace<00:11:43.560> that<00:11:43.760> with<00:11:43.880> a<00:11:44.160> proof<00:11:44.440> of<00:11:44.720> P 00:11:45.269 --> 00:11:45.279 align:start position:0% you could replace that with a proof of P 00:11:45.279 --> 00:11:48.190 align:start position:0% you could replace that with a proof of P passport<00:11:46.279> that<00:11:46.399> would<00:11:46.560> be<00:11:46.800> much 00:11:48.190 --> 00:11:48.200 align:start position:0% passport that would be much 00:11:48.200 --> 00:11:51.350 align:start position:0% passport that would be much stronger<00:11:49.200> another<00:11:49.480> one<00:11:49.760> is<00:11:50.399> uh<00:11:50.760> being<00:11:50.959> able<00:11:51.120> to 00:11:51.350 --> 00:11:51.360 align:start position:0% stronger another one is uh being able to 00:11:51.360 --> 00:11:53.389 align:start position:0% stronger another one is uh being able to prove<00:11:52.200> you<00:11:52.320> know<00:11:52.519> your<00:11:52.680> name<00:11:52.880> is<00:11:53.000> really<00:11:53.320> what 00:11:53.389 --> 00:11:53.399 align:start position:0% prove you know your name is really what 00:11:53.399 --> 00:11:55.590 align:start position:0% prove you know your name is really what you<00:11:53.480> say<00:11:53.720> it<00:11:53.800> is<00:11:53.959> on<00:11:54.120> social<00:11:54.399> media<00:11:55.240> so<00:11:55.360> you<00:11:55.440> can 00:11:55.590 --> 00:11:55.600 align:start position:0% you say it is on social media so you can 00:11:55.600 --> 00:11:56.829 align:start position:0% you say it is on social media so you can imagine<00:11:55.959> like<00:11:56.200> a<00:11:56.399> very<00:11:56.600> you<00:11:56.680> know 00:11:56.829 --> 00:11:56.839 align:start position:0% imagine like a very you know 00:11:56.839 --> 00:11:59.069 align:start position:0% imagine like a very you know decentralized<00:11:57.480> kind<00:11:57.600> of<00:11:57.839> way<00:11:57.959> to<00:11:58.120> do<00:11:58.360> this 00:11:59.069 --> 00:11:59.079 align:start position:0% decentralized kind of way to do this 00:11:59.079 --> 00:12:00.629 align:start position:0% decentralized kind of way to do this with<00:11:59.240> with<00:11:59.279> a<00:11:59.360> verified<00:11:59.760> name<00:11:59.959> badge<00:12:00.279> You<00:12:00.440> just 00:12:00.629 --> 00:12:00.639 align:start position:0% with with a verified name badge You just 00:12:00.639 --> 00:12:02.629 align:start position:0% with with a verified name badge You just prove<00:12:00.920> your<00:12:01.079> first<00:12:01.279> and<00:12:01.480> last<00:12:01.720> name<00:12:02.360> that<00:12:02.480> was 00:12:02.629 --> 00:12:02.639 align:start position:0% prove your first and last name that was 00:12:02.639 --> 00:12:04.670 align:start position:0% prove your first and last name that was attested<00:12:03.079> by<00:12:03.240> some<00:12:03.440> recognized<00:12:03.920> government 00:12:04.670 --> 00:12:04.680 align:start position:0% attested by some recognized government 00:12:04.680 --> 00:12:05.550 align:start position:0% attested by some recognized government and<00:12:04.760> then<00:12:04.880> you<00:12:05.000> could<00:12:05.160> you<00:12:05.240> could<00:12:05.360> have<00:12:05.480> that 00:12:05.550 --> 00:12:05.560 align:start position:0% and then you could you could have that 00:12:05.560 --> 00:12:08.110 align:start position:0% and then you could you could have that on<00:12:05.680> social<00:12:05.920> media<00:12:06.639> as<00:12:06.720> a<00:12:06.920> a<00:12:07.000> proof<00:12:07.240> of 00:12:08.110 --> 00:12:08.120 align:start position:0% on social media as a a proof of 00:12:08.120 --> 00:12:10.750 align:start position:0% on social media as a a proof of name<00:12:09.120> and<00:12:09.320> another<00:12:09.920> strong<00:12:10.079> use<00:12:10.440> case<00:12:10.600> is 00:12:10.750 --> 00:12:10.760 align:start position:0% name and another strong use case is 00:12:10.760 --> 00:12:12.550 align:start position:0% name and another strong use case is proof<00:12:11.000> of<00:12:11.200> age<00:12:11.720> there's<00:12:11.880> some<00:12:12.079> country<00:12:12.399> that's 00:12:12.550 --> 00:12:12.560 align:start position:0% proof of age there's some country that's 00:12:12.560 --> 00:12:14.790 align:start position:0% proof of age there's some country that's start<00:12:12.800> to<00:12:12.959> impose<00:12:13.560> age<00:12:13.880> gating<00:12:14.279> on<00:12:14.440> some 00:12:14.790 --> 00:12:14.800 align:start position:0% start to impose age gating on some 00:12:14.800 --> 00:12:17.550 align:start position:0% start to impose age gating on some website<00:12:15.240> such<00:12:15.440> as<00:12:15.639> adult<00:12:15.959> content<00:12:16.959> I<00:12:17.079> know 00:12:17.550 --> 00:12:17.560 align:start position:0% website such as adult content I know 00:12:17.560 --> 00:12:19.269 align:start position:0% website such as adult content I know that<00:12:17.959> because<00:12:18.320> France<00:12:18.680> is<00:12:18.839> actually<00:12:19.160> the 00:12:19.269 --> 00:12:19.279 align:start position:0% that because France is actually the 00:12:19.279 --> 00:12:21.710 align:start position:0% that because France is actually the country<00:12:19.560> where<00:12:19.680> I'm<00:12:19.920> from<00:12:20.639> is<00:12:20.800> doing<00:12:21.160> that 00:12:21.710 --> 00:12:21.720 align:start position:0% country where I'm from is doing that 00:12:21.720 --> 00:12:23.829 align:start position:0% country where I'm from is doing that they<00:12:21.959> impose<00:12:22.399> this<00:12:22.560> legally<00:12:22.920> speaking<00:12:23.440> so<00:12:23.720> but 00:12:23.829 --> 00:12:23.839 align:start position:0% they impose this legally speaking so but 00:12:23.839 --> 00:12:25.350 align:start position:0% they impose this legally speaking so but they<00:12:23.920> want<00:12:24.040> to<00:12:24.160> do<00:12:24.279> it<00:12:24.480> privacy<00:12:24.880> preserving 00:12:25.350 --> 00:12:25.360 align:start position:0% they want to do it privacy preserving 00:12:25.360 --> 00:12:27.430 align:start position:0% they want to do it privacy preserving way<00:12:26.079> they<00:12:26.240> still<00:12:26.480> care<00:12:26.680> about<00:12:26.920> privacy<00:12:27.360> which 00:12:27.430 --> 00:12:27.440 align:start position:0% way they still care about privacy which 00:12:27.440 --> 00:12:29.590 align:start position:0% way they still care about privacy which is<00:12:27.639> nice<00:12:27.920> to<00:12:28.120> hear<00:12:28.279> from<00:12:28.440> the<00:12:28.600> government<00:12:29.320> so 00:12:29.590 --> 00:12:29.600 align:start position:0% is nice to hear from the government so 00:12:29.600 --> 00:12:33.910 align:start position:0% is nice to hear from the government so that's<00:12:29.800> one<00:12:30.120> use<00:12:30.480> case<00:12:30.680> as 00:12:33.910 --> 00:12:33.920 align:start position:0% 00:12:33.920 --> 00:12:37.030 align:start position:0% well<00:12:34.920> um<00:12:35.120> so<00:12:35.519> here<00:12:36.079> if<00:12:36.199> you<00:12:36.320> wanted<00:12:36.639> to<00:12:36.800> know 00:12:37.030 --> 00:12:37.040 align:start position:0% well um so here if you wanted to know 00:12:37.040 --> 00:12:38.389 align:start position:0% well um so here if you wanted to know which<00:12:37.279> country<00:12:37.560> actually 00:12:38.389 --> 00:12:38.399 align:start position:0% which country actually 00:12:38.399 --> 00:12:41.110 align:start position:0% which country actually support<00:12:39.399> e<00:12:39.720> passport<00:12:40.160> electronic<00:12:40.639> passport 00:12:41.110 --> 00:12:41.120 align:start position:0% support e passport electronic passport 00:12:41.120 --> 00:12:43.189 align:start position:0% support e passport electronic passport this<00:12:41.240> is<00:12:41.399> all<00:12:41.680> the<00:12:41.800> country<00:12:42.120> in<00:12:42.279> blue<00:12:42.839> so<00:12:43.040> that 00:12:43.189 --> 00:12:43.199 align:start position:0% this is all the country in blue so that 00:12:43.199 --> 00:12:45.150 align:start position:0% this is all the country in blue so that covers<00:12:43.560> a<00:12:43.760> PR<00:12:43.959> big<00:12:44.079> chunk<00:12:44.320> of<00:12:44.399> the<00:12:44.480> world<00:12:44.760> over 00:12:45.150 --> 00:12:45.160 align:start position:0% covers a PR big chunk of the world over 00:12:45.160 --> 00:12:48.350 align:start position:0% covers a PR big chunk of the world over 150<00:12:46.120> countries<00:12:47.120> so<00:12:47.600> this<00:12:47.720> is<00:12:47.839> an<00:12:48.040> Open 00:12:48.350 --> 00:12:48.360 align:start position:0% 150 countries so this is an Open 00:12:48.360 --> 00:12:51.750 align:start position:0% 150 countries so this is an Open Standards<00:12:49.120> set<00:12:49.320> out<00:12:49.560> by<00:12:49.720> the<00:12:49.920> IAL<00:12:50.680> is<00:12:50.839> an<00:12:51.560> um 00:12:51.750 --> 00:12:51.760 align:start position:0% Standards set out by the IAL is an um 00:12:51.760 --> 00:12:54.790 align:start position:0% Standards set out by the IAL is an um institution<00:12:52.240> of<00:12:52.360> the<00:12:52.519> United<00:12:52.880> Nation<00:12:53.800> so<00:12:54.480> it's 00:12:54.790 --> 00:12:54.800 align:start position:0% institution of the United Nation so it's 00:12:54.800 --> 00:12:57.430 align:start position:0% institution of the United Nation so it's actually<00:12:55.399> quite<00:12:56.040> widely<00:12:56.440> supported<00:12:57.120> you<00:12:57.240> will 00:12:57.430 --> 00:12:57.440 align:start position:0% actually quite widely supported you will 00:12:57.440 --> 00:12:59.470 align:start position:0% actually quite widely supported you will notice<00:12:57.839> that<00:12:58.000> India<00:12:58.320> is<00:12:58.480> not<00:12:58.720> part<00:12:58.880> of<00:12:59.000> it<00:12:59.320> it's 00:12:59.470 --> 00:12:59.480 align:start position:0% notice that India is not part of it it's 00:12:59.480 --> 00:13:01.030 align:start position:0% notice that India is not part of it it's like<00:12:59.600> a<00:12:59.760> big<00:13:00.000> country<00:13:00.360> that's<00:13:00.560> not<00:13:00.800> actually 00:13:01.030 --> 00:13:01.040 align:start position:0% like a big country that's not actually 00:13:01.040 --> 00:13:03.230 align:start position:0% like a big country that's not actually part<00:13:01.199> of<00:13:01.320> it<00:13:01.800> for<00:13:02.000> that<00:13:02.199> country<00:13:02.959> you<00:13:03.079> would 00:13:03.230 --> 00:13:03.240 align:start position:0% part of it for that country you would 00:13:03.240 --> 00:13:05.389 align:start position:0% part of it for that country you would have<00:13:03.399> solution<00:13:03.760> like<00:13:03.959> anadar<00:13:04.959> which<00:13:05.160> actually 00:13:05.389 --> 00:13:05.399 align:start position:0% have solution like anadar which actually 00:13:05.399 --> 00:13:07.350 align:start position:0% have solution like anadar which actually supports<00:13:05.880> that<00:13:06.079> kind<00:13:06.199> of<00:13:06.440> like<00:13:06.560> alternative 00:13:07.350 --> 00:13:07.360 align:start position:0% supports that kind of like alternative 00:13:07.360 --> 00:13:10.189 align:start position:0% supports that kind of like alternative system<00:13:08.360> uh<00:13:08.519> but<00:13:08.760> others<00:13:09.240> like<00:13:09.600> passport<00:13:10.000> is 00:13:10.189 --> 00:13:10.199 align:start position:0% system uh but others like passport is 00:13:10.199 --> 00:13:12.470 align:start position:0% system uh but others like passport is pretty<00:13:10.480> good<00:13:11.199> there's<00:13:11.399> some<00:13:11.680> disparities<00:13:12.360> in 00:13:12.470 --> 00:13:12.480 align:start position:0% pretty good there's some disparities in 00:13:12.480 --> 00:13:14.069 align:start position:0% pretty good there's some disparities in the<00:13:12.600> signature<00:13:13.000> algorithm<00:13:13.639> though<00:13:13.760> so<00:13:13.959> they 00:13:14.069 --> 00:13:14.079 align:start position:0% the signature algorithm though so they 00:13:14.079 --> 00:13:15.590 align:start position:0% the signature algorithm though so they don't<00:13:14.360> always<00:13:14.600> use<00:13:14.839> the<00:13:14.959> same<00:13:15.320> kind<00:13:15.440> of 00:13:15.590 --> 00:13:15.600 align:start position:0% don't always use the same kind of 00:13:15.600 --> 00:13:17.350 align:start position:0% don't always use the same kind of signatures<00:13:16.079> so<00:13:16.199> we<00:13:16.320> have<00:13:16.440> to<00:13:16.600> adapt<00:13:16.880> to<00:13:17.079> that 00:13:17.350 --> 00:13:17.360 align:start position:0% signatures so we have to adapt to that 00:13:17.360 --> 00:13:19.710 align:start position:0% signatures so we have to adapt to that it's<00:13:17.519> not<00:13:18.079> fully<00:13:18.880> standardized<00:13:19.480> but<00:13:19.600> there's 00:13:19.710 --> 00:13:19.720 align:start position:0% it's not fully standardized but there's 00:13:19.720 --> 00:13:21.110 align:start position:0% it's not fully standardized but there's some<00:13:19.880> flexibility<00:13:20.320> to<00:13:20.399> those<00:13:20.560> standards<00:13:21.040> but 00:13:21.110 --> 00:13:21.120 align:start position:0% some flexibility to those standards but 00:13:21.120 --> 00:13:23.310 align:start position:0% some flexibility to those standards but it's<00:13:21.279> already<00:13:21.720> quite<00:13:22.040> good<00:13:22.920> and<00:13:23.079> another 00:13:23.310 --> 00:13:23.320 align:start position:0% it's already quite good and another 00:13:23.320 --> 00:13:24.829 align:start position:0% it's already quite good and another thing<00:13:23.440> I<00:13:23.560> want<00:13:23.680> to<00:13:23.839> point<00:13:24.040> out<00:13:24.240> is<00:13:24.440> that 00:13:24.829 --> 00:13:24.839 align:start position:0% thing I want to point out is that 00:13:24.839 --> 00:13:26.910 align:start position:0% thing I want to point out is that National<00:13:25.199> IDs<00:13:25.639> especially<00:13:26.000> in<00:13:26.120> the<00:13:26.240> EU<00:13:26.680> also 00:13:26.910 --> 00:13:26.920 align:start position:0% National IDs especially in the EU also 00:13:26.920 --> 00:13:28.710 align:start position:0% National IDs especially in the EU also support<00:13:27.279> that<00:13:27.440> standards<00:13:28.120> sometimes<00:13:28.440> even 00:13:28.710 --> 00:13:28.720 align:start position:0% support that standards sometimes even 00:13:28.720 --> 00:13:31.550 align:start position:0% support that standards sometimes even resident<00:13:29.320> permit<00:13:30.199> so<00:13:30.440> we<00:13:30.519> can<00:13:30.720> extend<00:13:31.120> to<00:13:31.320> that 00:13:31.550 --> 00:13:31.560 align:start position:0% resident permit so we can extend to that 00:13:31.560 --> 00:13:33.750 align:start position:0% resident permit so we can extend to that and<00:13:31.720> the<00:13:31.839> EU<00:13:32.040> is<00:13:32.160> also<00:13:32.360> pushing<00:13:32.800> generally<00:13:33.240> for 00:13:33.750 --> 00:13:33.760 align:start position:0% and the EU is also pushing generally for 00:13:33.760 --> 00:13:36.990 align:start position:0% and the EU is also pushing generally for digital<00:13:34.560> identity<00:13:35.560> uh<00:13:35.720> with<00:13:35.880> the<00:13:36.160> EU<00:13:36.639> digital 00:13:36.990 --> 00:13:37.000 align:start position:0% digital identity uh with the EU digital 00:13:37.000 --> 00:13:39.110 align:start position:0% digital identity uh with the EU digital identity<00:13:37.480> wallet<00:13:37.959> and<00:13:38.120> the<00:13:38.240> general<00:13:38.680> identity 00:13:39.110 --> 00:13:39.120 align:start position:0% identity wallet and the general identity 00:13:39.120 --> 00:13:41.790 align:start position:0% identity wallet and the general identity framework<00:13:39.639> they're<00:13:39.839> pushing<00:13:40.360> with 00:13:41.790 --> 00:13:41.800 align:start position:0% framework they're pushing with 00:13:41.800 --> 00:13:44.030 align:start position:0% framework they're pushing with Eis<00:13:42.800> and<00:13:42.959> to<00:13:43.079> give<00:13:43.199> a<00:13:43.279> bit<00:13:43.399> of<00:13:43.480> an<00:13:43.600> overview 00:13:44.030 --> 00:13:44.040 align:start position:0% Eis and to give a bit of an overview 00:13:44.040 --> 00:13:46.389 align:start position:0% Eis and to give a bit of an overview here<00:13:44.199> of<00:13:44.440> the<00:13:44.800> um<00:13:45.199> the<00:13:45.320> hierarchy<00:13:45.760> of<00:13:45.880> how<00:13:46.040> this 00:13:46.389 --> 00:13:46.399 align:start position:0% here of the um the hierarchy of how this 00:13:46.399 --> 00:13:48.949 align:start position:0% here of the um the hierarchy of how this works<00:13:47.399> it's<00:13:47.560> very<00:13:47.680> similar<00:13:48.000> to<00:13:48.160> pki<00:13:48.680> with<00:13:48.880> like 00:13:48.949 --> 00:13:48.959 align:start position:0% works it's very similar to pki with like 00:13:48.959 --> 00:13:50.910 align:start position:0% works it's very similar to pki with like the<00:13:49.079> current<00:13:49.920> the<00:13:50.040> current<00:13:50.279> web<00:13:50.440> and<00:13:50.560> SSL 00:13:50.910 --> 00:13:50.920 align:start position:0% the current the current web and SSL 00:13:50.920 --> 00:13:53.069 align:start position:0% the current the current web and SSL certificates<00:13:51.920> you<00:13:52.079> have<00:13:52.240> this<00:13:52.440> organization 00:13:53.069 --> 00:13:53.079 align:start position:0% certificates you have this organization 00:13:53.079 --> 00:13:56.870 align:start position:0% certificates you have this organization called<00:13:53.800> iow<00:13:54.800> and<00:13:55.160> uh<00:13:55.279> and<00:13:55.440> iow<00:13:56.079> they<00:13:56.480> they<00:13:56.720> are 00:13:56.870 --> 00:13:56.880 align:start position:0% called iow and uh and iow they they are 00:13:56.880 --> 00:13:59.670 align:start position:0% called iow and uh and iow they they are under<00:13:57.120> the<00:13:57.240> UN<00:13:58.160> and<00:13:58.680> uh 00:13:59.670 --> 00:13:59.680 align:start position:0% under the UN and uh 00:13:59.680 --> 00:14:01.629 align:start position:0% under the UN and uh they<00:13:59.839> collect<00:14:00.279> through<00:14:00.519> diplomatic<00:14:00.920> channels 00:14:01.629 --> 00:14:01.639 align:start position:0% they collect through diplomatic channels 00:14:01.639 --> 00:14:03.990 align:start position:0% they collect through diplomatic channels these<00:14:01.800> root<00:14:02.040> certificates<00:14:02.600> from<00:14:02.880> different 00:14:03.990 --> 00:14:04.000 align:start position:0% these root certificates from different 00:14:04.000 --> 00:14:06.030 align:start position:0% these root certificates from different countries<00:14:05.000> and<00:14:05.160> then<00:14:05.639> these<00:14:05.800> root 00:14:06.030 --> 00:14:06.040 align:start position:0% countries and then these root 00:14:06.040 --> 00:14:07.710 align:start position:0% countries and then these root certificates<00:14:06.959> they<00:14:07.160> then<00:14:07.279> sign<00:14:07.560> these 00:14:07.710 --> 00:14:07.720 align:start position:0% certificates they then sign these 00:14:07.720 --> 00:14:09.350 align:start position:0% certificates they then sign these intermediate<00:14:08.199> certificates<00:14:08.639> called<00:14:08.800> DS<00:14:09.240> or 00:14:09.350 --> 00:14:09.360 align:start position:0% intermediate certificates called DS or 00:14:09.360 --> 00:14:11.110 align:start position:0% intermediate certificates called DS or document<00:14:09.639> signing<00:14:09.920> certificates<00:14:10.720> and<00:14:10.959> those 00:14:11.110 --> 00:14:11.120 align:start position:0% document signing certificates and those 00:14:11.120 --> 00:14:13.069 align:start position:0% document signing certificates and those certificates<00:14:12.079> they<00:14:12.240> sign<00:14:12.480> the<00:14:12.600> actual<00:14:12.800> e 00:14:13.069 --> 00:14:13.079 align:start position:0% certificates they sign the actual e 00:14:13.079 --> 00:14:16.550 align:start position:0% certificates they sign the actual e passport<00:14:13.600> data 00:14:16.550 --> 00:14:16.560 align:start position:0% 00:14:16.560 --> 00:14:19.509 align:start position:0% itself<00:14:17.560> so<00:14:17.800> I'm<00:14:17.920> going<00:14:18.040> to<00:14:18.240> go<00:14:18.839> do<00:14:19.000> a<00:14:19.320> quick 00:14:19.509 --> 00:14:19.519 align:start position:0% itself so I'm going to go do a quick 00:14:19.519 --> 00:14:21.629 align:start position:0% itself so I'm going to go do a quick overview<00:14:20.040> this<00:14:20.160> is<00:14:20.320> this<00:14:20.480> our<00:14:20.639> SEC<00:14:21.160> work<00:14:21.440> so 00:14:21.629 --> 00:14:21.639 align:start position:0% overview this is this our SEC work so 00:14:21.639 --> 00:14:24.110 align:start position:0% overview this is this our SEC work so essentially<00:14:22.639> we<00:14:22.759> get<00:14:23.079> most<00:14:23.240> of<00:14:23.360> our<00:14:23.560> data<00:14:23.920> from 00:14:24.110 --> 00:14:24.120 align:start position:0% essentially we get most of our data from 00:14:24.120 --> 00:14:25.870 align:start position:0% essentially we get most of our data from what<00:14:24.240> we<00:14:24.399> call<00:14:24.600> the<00:14:24.800> data<00:14:25.040> group<00:14:25.320> one<00:14:25.600> so<00:14:25.720> it's 00:14:25.870 --> 00:14:25.880 align:start position:0% what we call the data group one so it's 00:14:25.880 --> 00:14:27.509 align:start position:0% what we call the data group one so it's like<00:14:26.079> visible<00:14:26.399> on<00:14:26.519> the<00:14:26.639> passport<00:14:27.040> so<00:14:27.199> the<00:14:27.320> two 00:14:27.509 --> 00:14:27.519 align:start position:0% like visible on the passport so the two 00:14:27.519 --> 00:14:29.509 align:start position:0% like visible on the passport so the two bottom<00:14:27.880> lines<00:14:28.519> so<00:14:28.680> it's<00:14:28.839> like<00:14:29.120> contain<00:14:29.360> the 00:14:29.509 --> 00:14:29.519 align:start position:0% bottom lines so it's like contain the 00:14:29.519 --> 00:14:31.389 align:start position:0% bottom lines so it's like contain the name<00:14:30.120> the<00:14:30.399> date<00:14:30.600> of<00:14:30.759> birth<00:14:31.000> and<00:14:31.160> other 00:14:31.389 --> 00:14:31.399 align:start position:0% name the date of birth and other 00:14:31.399 --> 00:14:33.110 align:start position:0% name the date of birth and other information<00:14:31.959> where<00:14:32.120> you<00:14:32.199> can<00:14:32.360> derive<00:14:32.839> a<00:14:32.959> lot 00:14:33.110 --> 00:14:33.120 align:start position:0% information where you can derive a lot 00:14:33.120 --> 00:14:35.590 align:start position:0% information where you can derive a lot of<00:14:33.880> information<00:14:34.880> that<00:14:35.040> generally<00:14:35.360> people 00:14:35.590 --> 00:14:35.600 align:start position:0% of information that generally people 00:14:35.600 --> 00:14:39.230 align:start position:0% of information that generally people want<00:14:36.399> and<00:14:36.600> this<00:14:36.839> is<00:14:37.839> hashed<00:14:38.199> into<00:14:38.639> content 00:14:39.230 --> 00:14:39.240 align:start position:0% want and this is hashed into content 00:14:39.240 --> 00:14:41.550 align:start position:0% want and this is hashed into content with<00:14:39.399> the<00:14:39.560> rest<00:14:39.759> of<00:14:39.920> the<00:14:40.120> data<00:14:40.920> which<00:14:41.240> itself 00:14:41.550 --> 00:14:41.560 align:start position:0% with the rest of the data which itself 00:14:41.560 --> 00:14:45.150 align:start position:0% with the rest of the data which itself is<00:14:41.800> signed<00:14:42.600> so<00:14:43.519> this<00:14:43.720> is<00:14:43.959> what<00:14:44.120> is<00:14:44.320> interesting 00:14:45.150 --> 00:14:45.160 align:start position:0% is signed so this is what is interesting 00:14:45.160 --> 00:14:47.550 align:start position:0% is signed so this is what is interesting because<00:14:45.320> that<00:14:45.480> signed<00:14:45.880> data<00:14:46.759> is<00:14:47.000> then<00:14:47.240> we<00:14:47.360> can 00:14:47.550 --> 00:14:47.560 align:start position:0% because that signed data is then we can 00:14:47.560 --> 00:14:49.629 align:start position:0% because that signed data is then we can verify<00:14:48.000> it<00:14:48.199> with<00:14:48.399> the<00:14:48.680> certificate<00:14:49.240> mentioned 00:14:49.629 --> 00:14:49.639 align:start position:0% verify it with the certificate mentioned 00:14:49.639 --> 00:14:52.629 align:start position:0% verify it with the certificate mentioned by<00:14:49.839> Michael<00:14:50.639> the<00:14:50.800> root<00:14:51.160> trust<00:14:51.680> chain<00:14:52.240> go<00:14:52.480> all 00:14:52.629 --> 00:14:52.639 align:start position:0% by Michael the root trust chain go all 00:14:52.639 --> 00:14:54.430 align:start position:0% by Michael the root trust chain go all the<00:14:52.759> way<00:14:52.920> up<00:14:53.160> to<00:14:53.279> the<00:14:53.639> certificate<00:14:54.160> that<00:14:54.279> way 00:14:54.430 --> 00:14:54.440 align:start position:0% the way up to the certificate that way 00:14:54.440 --> 00:14:56.230 align:start position:0% the way up to the certificate that way we<00:14:54.560> sure<00:14:54.839> that<00:14:55.000> that<00:14:55.240> data<00:14:55.639> has<00:14:55.759> been<00:14:55.920> issued 00:14:56.230 --> 00:14:56.240 align:start position:0% we sure that that data has been issued 00:14:56.240 --> 00:14:58.069 align:start position:0% we sure that that data has been issued in<00:14:56.440> time<00:14:56.639> by<00:14:56.759> the<00:14:56.920> state<00:14:57.519> and<00:14:57.639> from<00:14:57.839> that<00:14:57.959> we 00:14:58.069 --> 00:14:58.079 align:start position:0% in time by the state and from that we 00:14:58.079 --> 00:15:01.790 align:start position:0% in time by the state and from that we can<00:14:58.240> derive<00:14:59.279> proof<00:14:59.920> of<00:15:00.199> country<00:15:00.639> proof<00:15:00.880> of<00:15:01.079> age 00:15:01.790 --> 00:15:01.800 align:start position:0% can derive proof of country proof of age 00:15:01.800 --> 00:15:03.509 align:start position:0% can derive proof of country proof of age while<00:15:02.000> being<00:15:02.199> sure<00:15:02.560> that's<00:15:02.800> coming<00:15:03.040> from<00:15:03.199> a 00:15:03.509 --> 00:15:03.519 align:start position:0% while being sure that's coming from a 00:15:03.519 --> 00:15:06.230 align:start position:0% while being sure that's coming from a verifiable<00:15:04.519> source<00:15:05.360> without<00:15:05.639> riveting 00:15:06.230 --> 00:15:06.240 align:start position:0% verifiable source without riveting 00:15:06.240 --> 00:15:08.189 align:start position:0% verifiable source without riveting anything<00:15:06.560> else<00:15:06.920> about<00:15:07.279> the<00:15:07.440> information<00:15:08.040> of 00:15:08.189 --> 00:15:08.199 align:start position:0% anything else about the information of 00:15:08.199 --> 00:15:08.870 align:start position:0% anything else about the information of the 00:15:08.870 --> 00:15:08.880 align:start position:0% the 00:15:08.880 --> 00:15:13.629 align:start position:0% the document<00:15:10.000> um<00:15:11.000> so<00:15:12.000> cool<00:15:12.279> great<00:15:12.920> and<00:15:13.320> uh<00:15:13.480> so 00:15:13.629 --> 00:15:13.639 align:start position:0% document um so cool great and uh so 00:15:13.639 --> 00:15:14.870 align:start position:0% document um so cool great and uh so rather<00:15:13.800> than<00:15:13.920> just<00:15:14.040> talk<00:15:14.240> about<00:15:14.440> it<00:15:14.680> let's 00:15:14.870 --> 00:15:14.880 align:start position:0% rather than just talk about it let's 00:15:14.880 --> 00:15:16.509 align:start position:0% rather than just talk about it let's actually<00:15:15.160> dive<00:15:15.360> in<00:15:15.600> and<00:15:15.720> take<00:15:15.839> a<00:15:16.000> look<00:15:16.160> at<00:15:16.360> what 00:15:16.509 --> 00:15:16.519 align:start position:0% actually dive in and take a look at what 00:15:16.519 --> 00:15:18.790 align:start position:0% actually dive in and take a look at what ZK<00:15:16.920> passport<00:15:17.560> um<00:15:17.880> looks<00:15:18.120> like<00:15:18.240> and<00:15:18.360> how<00:15:18.480> it 00:15:18.790 --> 00:15:18.800 align:start position:0% ZK passport um looks like and how it 00:15:18.800 --> 00:15:21.749 align:start position:0% ZK passport um looks like and how it works<00:15:19.800> so<00:15:20.120> this<00:15:20.199> is<00:15:20.360> ZK<00:15:20.680> passport<00:15:21.519> and<00:15:21.639> the 00:15:21.749 --> 00:15:21.759 align:start position:0% works so this is ZK passport and the 00:15:21.759 --> 00:15:23.870 align:start position:0% works so this is ZK passport and the first<00:15:22.000> step<00:15:22.320> here<00:15:22.519> is<00:15:22.639> I'm<00:15:22.759> going<00:15:22.839> to<00:15:23.240> tap<00:15:23.480> my 00:15:23.870 --> 00:15:23.880 align:start position:0% first step here is I'm going to tap my 00:15:23.880 --> 00:15:26.269 align:start position:0% first step here is I'm going to tap my um<00:15:24.199> government<00:15:24.519> issue<00:15:24.959> passport<00:15:25.959> against<00:15:26.199> the 00:15:26.269 --> 00:15:26.279 align:start position:0% um government issue passport against the 00:15:26.279 --> 00:15:27.910 align:start position:0% um government issue passport against the phone<00:15:26.519> and<00:15:26.639> it'll<00:15:26.800> read<00:15:27.079> the<00:15:27.360> passport<00:15:27.680> data 00:15:27.910 --> 00:15:27.920 align:start position:0% phone and it'll read the passport data 00:15:27.920 --> 00:15:29.990 align:start position:0% phone and it'll read the passport data in<00:15:28.079> by<00:15:28.199> NFC 00:15:29.990 --> 00:15:30.000 align:start position:0% in by NFC 00:15:30.000 --> 00:15:31.350 align:start position:0% in by NFC and<00:15:30.120> then<00:15:30.279> once<00:15:30.440> that's<00:15:30.600> done<00:15:30.800> you'll<00:15:30.959> see<00:15:31.120> it 00:15:31.350 --> 00:15:31.360 align:start position:0% and then once that's done you'll see it 00:15:31.360 --> 00:15:32.670 align:start position:0% and then once that's done you'll see it come<00:15:31.519> up<00:15:31.680> here<00:15:31.839> so<00:15:31.959> that's<00:15:32.079> me<00:15:32.240> loaded<00:15:32.480> into 00:15:32.670 --> 00:15:32.680 align:start position:0% come up here so that's me loaded into 00:15:32.680 --> 00:15:35.430 align:start position:0% come up here so that's me loaded into zikar<00:15:33.360> passport<00:15:34.360> and<00:15:34.519> then<00:15:34.839> the<00:15:34.920> next<00:15:35.120> step<00:15:35.279> is 00:15:35.430 --> 00:15:35.440 align:start position:0% zikar passport and then the next step is 00:15:35.440 --> 00:15:37.110 align:start position:0% zikar passport and then the next step is just<00:15:35.759> to<00:15:36.040> connect<00:15:36.279> it<00:15:36.399> with<00:15:36.519> the<00:15:36.639> DAP<00:15:36.880> so<00:15:37.000> we 00:15:37.110 --> 00:15:37.120 align:start position:0% just to connect it with the DAP so we 00:15:37.120 --> 00:15:38.509 align:start position:0% just to connect it with the DAP so we can<00:15:37.240> actually<00:15:37.600> generate<00:15:37.920> some<00:15:38.079> identity 00:15:38.509 --> 00:15:38.519 align:start position:0% can actually generate some identity 00:15:38.519 --> 00:15:40.590 align:start position:0% can actually generate some identity proofs<00:15:39.519> this<00:15:39.600> is<00:15:39.920> an<00:15:40.000> integration<00:15:40.399> that<00:15:40.480> we 00:15:40.590 --> 00:15:40.600 align:start position:0% proofs this is an integration that we 00:15:40.600 --> 00:15:42.430 align:start position:0% proofs this is an integration that we did<00:15:40.720> with<00:15:40.880> Devcon<00:15:41.440> and<00:15:41.519> this<00:15:41.639> allowed<00:15:42.040> people 00:15:42.430 --> 00:15:42.440 align:start position:0% did with Devcon and this allowed people 00:15:42.440 --> 00:15:44.269 align:start position:0% did with Devcon and this allowed people who<00:15:42.600> are<00:15:42.759> from<00:15:42.920> Southeast<00:15:43.360> Asia<00:15:43.880> to<00:15:44.040> prove 00:15:44.269 --> 00:15:44.279 align:start position:0% who are from Southeast Asia to prove 00:15:44.279 --> 00:15:45.269 align:start position:0% who are from Southeast Asia to prove they<00:15:44.399> from<00:15:44.560> one<00:15:44.680> of<00:15:44.759> the<00:15:44.839> countries<00:15:45.120> from 00:15:45.269 --> 00:15:45.279 align:start position:0% they from one of the countries from 00:15:45.279 --> 00:15:47.629 align:start position:0% they from one of the countries from Southeast<00:15:45.680> Asia<00:15:46.600> um<00:15:46.720> but<00:15:46.880> nothing<00:15:47.079> else<00:15:47.279> about 00:15:47.629 --> 00:15:47.639 align:start position:0% Southeast Asia um but nothing else about 00:15:47.639 --> 00:15:49.230 align:start position:0% Southeast Asia um but nothing else about themselves<00:15:48.199> and<00:15:48.319> then<00:15:48.639> they're<00:15:48.839> able<00:15:49.000> to<00:15:49.160> get 00:15:49.230 --> 00:15:49.240 align:start position:0% themselves and then they're able to get 00:15:49.240 --> 00:15:50.949 align:start position:0% themselves and then they're able to get a<00:15:49.399> discount<00:15:49.800> voucher<00:15:50.199> applied<00:15:50.560> to<00:15:50.759> their 00:15:50.949 --> 00:15:50.959 align:start position:0% a discount voucher applied to their 00:15:50.959 --> 00:15:53.470 align:start position:0% a discount voucher applied to their purchase<00:15:51.319> of<00:15:51.440> their<00:15:51.560> Defcon<00:15:51.959> ticket<00:15:52.839> so<00:15:53.079> to<00:15:53.240> do 00:15:53.470 --> 00:15:53.480 align:start position:0% purchase of their Defcon ticket so to do 00:15:53.480 --> 00:15:56.309 align:start position:0% purchase of their Defcon ticket so to do that<00:15:54.480> simply<00:15:54.839> click<00:15:55.440> on<00:15:55.560> the<00:15:55.680> continue<00:15:56.040> button 00:15:56.309 --> 00:15:56.319 align:start position:0% that simply click on the continue button 00:15:56.319 --> 00:15:58.509 align:start position:0% that simply click on the continue button here<00:15:56.600> this<00:15:56.720> will<00:15:56.920> generate<00:15:57.240> a<00:15:57.360> QR<00:15:57.639> code<00:15:58.319> which 00:15:58.509 --> 00:15:58.519 align:start position:0% here this will generate a QR code which 00:15:58.519 --> 00:16:00.870 align:start position:0% here this will generate a QR code which I'll<00:15:58.720> then<00:15:59.160> scan<00:15:59.639> with<00:15:59.880> my 00:16:00.870 --> 00:16:00.880 align:start position:0% I'll then scan with my 00:16:00.880 --> 00:16:03.150 align:start position:0% I'll then scan with my phone<00:16:01.880> and<00:16:02.040> then<00:16:02.279> that<00:16:02.360> will<00:16:02.560> prompt<00:16:03.079> that 00:16:03.150 --> 00:16:03.160 align:start position:0% phone and then that will prompt that 00:16:03.160 --> 00:16:06.949 align:start position:0% phone and then that will prompt that will<00:16:03.319> prompt<00:16:03.600> me<00:16:04.079> to<00:16:05.079> um<00:16:06.000> which<00:16:06.480> it'll<00:16:06.720> prompt 00:16:06.949 --> 00:16:06.959 align:start position:0% will prompt me to um which it'll prompt 00:16:06.959 --> 00:16:08.829 align:start position:0% will prompt me to um which it'll prompt me<00:16:07.040> to<00:16:07.240> prove<00:16:07.600> particular<00:16:07.920> credentials<00:16:08.720> that 00:16:08.829 --> 00:16:08.839 align:start position:0% me to prove particular credentials that 00:16:08.839 --> 00:16:11.189 align:start position:0% me to prove particular credentials that are<00:16:09.560> being<00:16:09.680> asked<00:16:09.880> of<00:16:09.959> me<00:16:10.079> from<00:16:10.240> this<00:16:10.399> service 00:16:11.189 --> 00:16:11.199 align:start position:0% are being asked of me from this service 00:16:11.199 --> 00:16:13.389 align:start position:0% are being asked of me from this service in<00:16:11.360> this<00:16:11.519> case<00:16:11.839> it's<00:16:12.079> just<00:16:12.240> my<00:16:12.399> country<00:16:13.199> um<00:16:13.279> and 00:16:13.389 --> 00:16:13.399 align:start position:0% in this case it's just my country um and 00:16:13.399 --> 00:16:14.829 align:start position:0% in this case it's just my country um and that's<00:16:13.560> completely<00:16:14.120> up<00:16:14.240> to<00:16:14.360> the<00:16:14.440> developer 00:16:14.829 --> 00:16:14.839 align:start position:0% that's completely up to the developer 00:16:14.839 --> 00:16:17.670 align:start position:0% that's completely up to the developer that's<00:16:15.040> integrating<00:16:15.560> this<00:16:16.199> so<00:16:16.399> I<00:16:16.480> will<00:16:16.759> hit<00:16:17.399> uh 00:16:17.670 --> 00:16:17.680 align:start position:0% that's integrating this so I will hit uh 00:16:17.680 --> 00:16:19.389 align:start position:0% that's integrating this so I will hit uh accept<00:16:18.519> this<00:16:18.600> will<00:16:18.759> generate<00:16:19.040> the<00:16:19.160> zero 00:16:19.389 --> 00:16:19.399 align:start position:0% accept this will generate the zero 00:16:19.399 --> 00:16:21.990 align:start position:0% accept this will generate the zero knowledge<00:16:19.720> proof<00:16:20.079> on<00:16:20.279> my<00:16:20.600> phone<00:16:21.600> it'll<00:16:21.880> then 00:16:21.990 --> 00:16:22.000 align:start position:0% knowledge proof on my phone it'll then 00:16:22.000 --> 00:16:23.949 align:start position:0% knowledge proof on my phone it'll then be<00:16:22.160> sent<00:16:22.759> via<00:16:23.040> the<00:16:23.240> secure<00:16:23.560> end<00:16:23.720> to<00:16:23.800> end 00:16:23.949 --> 00:16:23.959 align:start position:0% be sent via the secure end to end 00:16:23.959 --> 00:16:25.990 align:start position:0% be sent via the secure end to end encrypted<00:16:24.360> websocket<00:16:25.319> where<00:16:25.480> it's<00:16:25.680> then 00:16:25.990 --> 00:16:26.000 align:start position:0% encrypted websocket where it's then 00:16:26.000 --> 00:16:28.590 align:start position:0% encrypted websocket where it's then verified<00:16:27.000> um<00:16:27.240> either<00:16:27.440> on<00:16:27.560> the<00:16:27.680> back<00:16:27.800> end<00:16:28.399> or 00:16:28.590 --> 00:16:28.600 align:start position:0% verified um either on the back end or 00:16:28.600 --> 00:16:31.590 align:start position:0% verified um either on the back end or even<00:16:29.160> um<00:16:29.279> on<00:16:29.360> a<00:16:29.480> smart 00:16:31.590 --> 00:16:31.600 align:start position:0% even um on a smart 00:16:31.600 --> 00:16:36.230 align:start position:0% even um on a smart contract<00:16:32.639> uh<00:16:33.639> we<00:16:34.160> uh<00:16:34.759> we<00:16:35.040> recently<00:16:35.399> blessed<00:16:35.800> by 00:16:36.230 --> 00:16:36.240 align:start position:0% contract uh we uh we recently blessed by 00:16:36.240 --> 00:16:38.030 align:start position:0% contract uh we uh we recently blessed by uh<00:16:36.360> from<00:16:36.639> with<00:16:36.759> a<00:16:36.920> visit<00:16:37.279> from<00:16:37.560> uh<00:16:37.720> father 00:16:38.030 --> 00:16:38.040 align:start position:0% uh from with a visit from uh father 00:16:38.040 --> 00:16:40.389 align:start position:0% uh from with a visit from uh father vitalic<00:16:38.639> at<00:16:38.759> our<00:16:38.959> booth<00:16:39.600> just<00:16:39.839> around<00:16:40.279> the 00:16:40.389 --> 00:16:40.399 align:start position:0% vitalic at our booth just around the 00:16:40.399 --> 00:16:42.389 align:start position:0% vitalic at our booth just around the corner<00:16:40.720> outside<00:16:41.519> so<00:16:41.720> please<00:16:41.920> feel<00:16:42.079> free<00:16:42.279> to 00:16:42.389 --> 00:16:42.399 align:start position:0% corner outside so please feel free to 00:16:42.399 --> 00:16:44.069 align:start position:0% corner outside so please feel free to come<00:16:42.600> by<00:16:42.880> um<00:16:42.959> we've<00:16:43.160> got<00:16:43.240> it<00:16:43.399> for<00:16:43.600> the<00:16:43.759> rest<00:16:43.880> of 00:16:44.069 --> 00:16:44.079 align:start position:0% come by um we've got it for the rest of 00:16:44.079 --> 00:16:47.389 align:start position:0% come by um we've got it for the rest of the<00:16:44.600> day<00:16:45.600> and<00:16:46.000> um<00:16:46.120> we<00:16:46.279> have<00:16:46.360> a<00:16:46.519> workshop<00:16:47.000> on 00:16:47.389 --> 00:16:47.399 align:start position:0% the day and um we have a workshop on 00:16:47.399 --> 00:16:50.269 align:start position:0% the day and um we have a workshop on tomorrow<00:16:48.000> in<00:16:48.160> classroom<00:16:48.680> B<00:16:49.360> at<00:16:49.519> 12:00<00:16:49.839> p.m.<00:16:50.120> so 00:16:50.269 --> 00:16:50.279 align:start position:0% tomorrow in classroom B at 12:00 p.m. so 00:16:50.279 --> 00:16:51.309 align:start position:0% tomorrow in classroom B at 12:00 p.m. so if<00:16:50.319> you'd<00:16:50.480> like<00:16:50.600> to<00:16:50.680> learn<00:16:50.880> more<00:16:51.000> about<00:16:51.160> our 00:16:51.309 --> 00:16:51.319 align:start position:0% if you'd like to learn more about our 00:16:51.319 --> 00:16:54.509 align:start position:0% if you'd like to learn more about our SDK<00:16:52.319> and<00:16:52.800> uh<00:16:53.079> and<00:16:53.240> and<00:16:53.399> how<00:16:53.519> it<00:16:53.639> works<00:16:54.279> please 00:16:54.509 --> 00:16:54.519 align:start position:0% SDK and uh and and how it works please 00:16:54.519 --> 00:16:57.430 align:start position:0% SDK and uh and and how it works please come<00:16:54.759> by<00:16:55.079> and<00:16:55.639> yeah<00:16:55.839> you<00:16:55.959> can<00:16:56.079> chat<00:16:56.279> with<00:16:56.440> us 00:16:57.430 --> 00:16:57.440 align:start position:0% come by and yeah you can chat with us 00:16:57.440 --> 00:16:58.949 align:start position:0% come by and yeah you can chat with us sick 00:16:58.949 --> 00:16:58.959 align:start position:0% sick 00:16:58.959 --> 00:17:01.470 align:start position:0% sick and<00:16:59.079> I<00:16:59.160> guess<00:16:59.319> lastly<00:16:59.800> one<00:17:00.040> one<00:17:00.199> last<00:17:00.360> QR<00:17:00.680> code 00:17:01.470 --> 00:17:01.480 align:start position:0% and I guess lastly one one last QR code 00:17:01.480 --> 00:17:03.189 align:start position:0% and I guess lastly one one last QR code uh<00:17:01.600> we<00:17:01.720> have<00:17:01.800> a<00:17:01.959> demo<00:17:02.279> available<00:17:02.839> it<00:17:02.959> works 00:17:03.189 --> 00:17:03.199 align:start position:0% uh we have a demo available it works 00:17:03.199 --> 00:17:04.549 align:start position:0% uh we have a demo available it works best<00:17:03.360> on<00:17:03.560> desktop<00:17:03.920> it's<00:17:04.000> the<00:17:04.079> one<00:17:04.240> we're<00:17:04.360> using 00:17:04.549 --> 00:17:04.559 align:start position:0% best on desktop it's the one we're using 00:17:04.559 --> 00:17:06.669 align:start position:0% best on desktop it's the one we're using at<00:17:04.679> the<00:17:04.760> booth<00:17:05.679> um<00:17:05.919> so<00:17:06.160> yeah<00:17:06.280> there's<00:17:06.400> a<00:17:06.480> QR 00:17:06.669 --> 00:17:06.679 align:start position:0% at the booth um so yeah there's a QR 00:17:06.679 --> 00:17:08.429 align:start position:0% at the booth um so yeah there's a QR code<00:17:06.880> if<00:17:06.919> you<00:17:07.000> want<00:17:07.079> to<00:17:07.160> try<00:17:07.319> it<00:17:07.439> out<00:17:08.280> and 00:17:08.429 --> 00:17:08.439 align:start position:0% code if you want to try it out and 00:17:08.439 --> 00:17:09.630 align:start position:0% code if you want to try it out and you'll<00:17:08.600> be<00:17:08.679> able<00:17:08.799> to<00:17:08.919> load<00:17:09.079> your<00:17:09.199> passport<00:17:09.520> in 00:17:09.630 --> 00:17:09.640 align:start position:0% you'll be able to load your passport in 00:17:09.640 --> 00:17:12.590 align:start position:0% you'll be able to load your passport in it<00:17:09.760> supports<00:17:10.160> both<00:17:10.480> Android<00:17:11.000> and<00:17:11.240> iOS<00:17:12.240> um<00:17:12.480> yeah 00:17:12.590 --> 00:17:12.600 align:start position:0% it supports both Android and iOS um yeah 00:17:12.600 --> 00:17:13.590 align:start position:0% it supports both Android and iOS um yeah but<00:17:12.679> if<00:17:12.760> you<00:17:12.839> have<00:17:12.959> any<00:17:13.039> issues<00:17:13.280> with<00:17:13.400> that 00:17:13.590 --> 00:17:13.600 align:start position:0% but if you have any issues with that 00:17:13.600 --> 00:17:15.350 align:start position:0% but if you have any issues with that please<00:17:13.880> reach<00:17:14.079> out<00:17:14.240> to<00:17:14.439> us<00:17:14.799> and<00:17:15.000> we<00:17:15.120> can<00:17:15.199> help 00:17:15.350 --> 00:17:15.360 align:start position:0% please reach out to us and we can help 00:17:15.360 --> 00:17:15.990 align:start position:0% please reach out to us and we can help you 00:17:15.990 --> 00:17:16.000 align:start position:0% you 00:17:16.000 --> 00:17:20.069 align:start position:0% you out<00:17:17.000> all<00:17:17.240> right<00:17:18.079> round<00:17:18.400> of 00:17:20.069 --> 00:17:20.079 align:start position:0% out all right round of 00:17:20.079 --> 00:17:22.750 align:start position:0% out all right round of applause<00:17:21.079> give<00:17:21.199> it<00:17:21.319> up<00:17:21.559> give<00:17:21.679> it<00:17:21.799> up<00:17:22.199> okay<00:17:22.400> cool 00:17:22.750 --> 00:17:22.760 align:start position:0% applause give it up give it up okay cool 00:17:22.760 --> 00:17:24.309 align:start position:0% applause give it up give it up okay cool so<00:17:23.160> we 00:17:24.309 --> 00:17:24.319 align:start position:0% so we 00:17:24.319 --> 00:17:27.270 align:start position:0% so we have<00:17:25.319> a<00:17:25.480> couple<00:17:25.919> of<00:17:26.120> minutes<00:17:26.520> left<00:17:26.799> maybe<00:17:27.120> time 00:17:27.270 --> 00:17:27.280 align:start position:0% have a couple of minutes left maybe time 00:17:27.280 --> 00:17:29.310 align:start position:0% have a couple of minutes left maybe time for<00:17:27.520> two<00:17:27.839> questions<00:17:28.439> and<00:17:28.679> uh<00:17:28.919> let's<00:17:29.039> just<00:17:29.160> go 00:17:29.310 --> 00:17:29.320 align:start position:0% for two questions and uh let's just go 00:17:29.320 --> 00:17:32.110 align:start position:0% for two questions and uh let's just go with<00:17:29.480> the<00:17:29.600> top<00:17:29.799> two<00:17:30.280> so<00:17:31.280> um<00:17:31.640> I<00:17:31.720> think<00:17:31.840> you<00:17:31.960> guys 00:17:32.110 --> 00:17:32.120 align:start position:0% with the top two so um I think you guys 00:17:32.120 --> 00:17:34.150 align:start position:0% with the top two so um I think you guys could<00:17:32.280> just<00:17:32.400> read<00:17:32.600> that<00:17:32.720> and<00:17:32.880> answer<00:17:33.080> it<00:17:33.320> yeah 00:17:34.150 --> 00:17:34.160 align:start position:0% could just read that and answer it yeah 00:17:34.160 --> 00:17:35.390 align:start position:0% could just read that and answer it yeah yeah<00:17:34.320> that's<00:17:34.640> go<00:17:34.720> for 00:17:35.390 --> 00:17:35.400 align:start position:0% yeah that's go for 00:17:35.400 --> 00:17:39.549 align:start position:0% yeah that's go for it<00:17:36.400> um<00:17:36.720> so<00:17:37.120> regarding<00:17:37.559> Noir<00:17:38.080> as<00:17:38.200> a 00:17:39.549 --> 00:17:39.559 align:start position:0% it um so regarding Noir as a 00:17:39.559 --> 00:17:42.430 align:start position:0% it um so regarding Noir as a DSL<00:17:40.559> as<00:17:40.760> a<00:17:41.000> system<00:17:41.400> so<00:17:41.679> how<00:17:41.840> did<00:17:41.960> you<00:17:42.080> land<00:17:42.320> on 00:17:42.430 --> 00:17:42.440 align:start position:0% DSL as a system so how did you land on 00:17:42.440 --> 00:17:44.590 align:start position:0% DSL as a system so how did you land on Noir<00:17:42.720> as<00:17:42.880> the<00:17:42.960> DSL<00:17:43.320> for<00:17:43.559> circuit<00:17:43.919> does<00:17:44.200> your 00:17:44.590 --> 00:17:44.600 align:start position:0% Noir as the DSL for circuit does your 00:17:44.600 --> 00:17:47.110 align:start position:0% Noir as the DSL for circuit does your system<00:17:44.960> interact<00:17:45.280> with<00:17:45.400> a<00:17:45.760> itself<00:17:46.160> so<00:17:46.720> first 00:17:47.110 --> 00:17:47.120 align:start position:0% system interact with a itself so first 00:17:47.120 --> 00:17:50.270 align:start position:0% system interact with a itself so first question<00:17:48.120> um<00:17:48.400> Noir<00:17:49.320> so<00:17:49.520> why<00:17:49.640> did<00:17:49.799> we<00:17:49.919> choose 00:17:50.270 --> 00:17:50.280 align:start position:0% question um Noir so why did we choose 00:17:50.280 --> 00:17:52.230 align:start position:0% question um Noir so why did we choose that<00:17:50.720> um<00:17:50.880> we<00:17:51.000> did<00:17:51.160> choose<00:17:51.400> it<00:17:51.600> pretty<00:17:51.799> early<00:17:52.039> on 00:17:52.230 --> 00:17:52.240 align:start position:0% that um we did choose it pretty early on 00:17:52.240 --> 00:17:54.029 align:start position:0% that um we did choose it pretty early on when<00:17:52.360> it<00:17:52.480> was<00:17:52.640> still<00:17:53.120> quite<00:17:53.320> unstable<00:17:53.760> but<00:17:53.880> now 00:17:54.029 --> 00:17:54.039 align:start position:0% when it was still quite unstable but now 00:17:54.039 --> 00:17:56.470 align:start position:0% when it was still quite unstable but now it's<00:17:54.200> pretty<00:17:54.480> stable<00:17:55.159> so<00:17:55.400> Noir<00:17:55.720> I<00:17:55.840> see<00:17:56.039> it<00:17:56.159> as<00:17:56.280> a 00:17:56.470 --> 00:17:56.480 align:start position:0% it's pretty stable so Noir I see it as a 00:17:56.480 --> 00:17:58.669 align:start position:0% it's pretty stable so Noir I see it as a very<00:17:57.159> um<00:17:57.520> good<00:17:57.760> language<00:17:58.159> if<00:17:58.240> you<00:17:58.320> want<00:17:58.440> to<00:17:58.520> do 00:17:58.669 --> 00:17:58.679 align:start position:0% very um good language if you want to do 00:17:58.679 --> 00:17:59.390 align:start position:0% very um good language if you want to do Z 00:17:59.390 --> 00:17:59.400 align:start position:0% Z 00:17:59.400 --> 00:18:02.350 align:start position:0% Z cdsl<00:18:00.400> cdsl<00:18:01.039> that's<00:18:01.240> mainten<00:18:01.760> toward<00:18:02.039> the 00:18:02.350 --> 00:18:02.360 align:start position:0% cdsl cdsl that's mainten toward the 00:18:02.360 --> 00:18:04.950 align:start position:0% cdsl cdsl that's mainten toward the future<00:18:03.360> the<00:18:03.520> Aztec<00:18:03.840> team<00:18:04.039> is<00:18:04.159> pretty<00:18:04.440> reliable 00:18:04.950 --> 00:18:04.960 align:start position:0% future the Aztec team is pretty reliable 00:18:04.960 --> 00:18:06.669 align:start position:0% future the Aztec team is pretty reliable they're<00:18:05.080> a<00:18:05.200> good<00:18:05.360> team<00:18:05.880> so<00:18:06.039> you<00:18:06.120> can<00:18:06.280> rely<00:18:06.559> on 00:18:06.669 --> 00:18:06.679 align:start position:0% they're a good team so you can rely on 00:18:06.679 --> 00:18:08.950 align:start position:0% they're a good team so you can rely on them<00:18:07.320> and<00:18:07.600> it's<00:18:07.720> a<00:18:07.880> universal<00:18:08.400> language<00:18:08.840> which 00:18:08.950 --> 00:18:08.960 align:start position:0% them and it's a universal language which 00:18:08.960 --> 00:18:10.750 align:start position:0% them and it's a universal language which means<00:18:09.240> you<00:18:09.360> can<00:18:09.720> have<00:18:09.880> like<00:18:10.000> a<00:18:10.120> single<00:18:10.480> code 00:18:10.750 --> 00:18:10.760 align:start position:0% means you can have like a single code 00:18:10.760 --> 00:18:12.750 align:start position:0% means you can have like a single code base<00:18:11.400> and<00:18:11.520> switch<00:18:11.840> your<00:18:12.039> back<00:18:12.200> end<00:18:12.440> for<00:18:12.640> a 00:18:12.750 --> 00:18:12.760 align:start position:0% base and switch your back end for a 00:18:12.760 --> 00:18:13.990 align:start position:0% base and switch your back end for a different<00:18:13.000> one<00:18:13.200> if<00:18:13.280> you<00:18:13.400> want<00:18:13.600> a<00:18:13.720> different 00:18:13.990 --> 00:18:14.000 align:start position:0% different one if you want a different 00:18:14.000 --> 00:18:17.710 align:start position:0% different one if you want a different proving<00:18:14.360> scheme<00:18:15.080> so<00:18:15.280> you<00:18:15.400> can<00:18:16.120> still<00:18:17.120> just 00:18:17.710 --> 00:18:17.720 align:start position:0% proving scheme so you can still just 00:18:17.720 --> 00:18:20.549 align:start position:0% proving scheme so you can still just improve<00:18:18.720> uh<00:18:18.880> with<00:18:19.120> the<00:18:19.720> whatever<00:18:20.240> latest 00:18:20.549 --> 00:18:20.559 align:start position:0% improve uh with the whatever latest 00:18:20.559 --> 00:18:22.270 align:start position:0% improve uh with the whatever latest Improvement<00:18:20.919> has<00:18:21.080> been<00:18:21.200> done<00:18:21.400> in<00:18:21.559> ZK<00:18:22.080> while 00:18:22.270 --> 00:18:22.280 align:start position:0% Improvement has been done in ZK while 00:18:22.280 --> 00:18:23.950 align:start position:0% Improvement has been done in ZK while still<00:18:22.440> maintaining<00:18:23.000> the<00:18:23.080> same<00:18:23.320> Cod<00:18:23.600> base<00:18:23.799> so 00:18:23.950 --> 00:18:23.960 align:start position:0% still maintaining the same Cod base so 00:18:23.960 --> 00:18:26.350 align:start position:0% still maintaining the same Cod base so that<00:18:24.120> I<00:18:24.240> found<00:18:24.679> this<00:18:24.919> pretty<00:18:25.200> powerful<00:18:25.960> as<00:18:26.120> for 00:18:26.350 --> 00:18:26.360 align:start position:0% that I found this pretty powerful as for 00:18:26.360 --> 00:18:28.230 align:start position:0% that I found this pretty powerful as for whether<00:18:26.600> we<00:18:26.720> interact<00:18:27.039> with<00:18:27.159> that<00:18:27.400> St<00:18:27.640> itself 00:18:28.230 --> 00:18:28.240 align:start position:0% whether we interact with that St itself 00:18:28.240 --> 00:18:30.590 align:start position:0% whether we interact with that St itself so<00:18:28.440> zik<00:18:28.880> passport<00:18:29.280> is<00:18:29.559> blockchain<00:18:30.039> agnostic 00:18:30.590 --> 00:18:30.600 align:start position:0% so zik passport is blockchain agnostic 00:18:30.600 --> 00:18:32.029 align:start position:0% so zik passport is blockchain agnostic like<00:18:30.760> the<00:18:30.840> protocol<00:18:31.240> itself<00:18:31.480> is<00:18:31.640> blockchain 00:18:32.029 --> 00:18:32.039 align:start position:0% like the protocol itself is blockchain 00:18:32.039 --> 00:18:33.950 align:start position:0% like the protocol itself is blockchain agnostic<00:18:32.640> but<00:18:32.919> as<00:18:33.080> mentioned<00:18:33.440> by<00:18:33.600> Michael 00:18:33.950 --> 00:18:33.960 align:start position:0% agnostic but as mentioned by Michael 00:18:33.960 --> 00:18:35.070 align:start position:0% agnostic but as mentioned by Michael we're<00:18:34.080> building<00:18:34.400> this<00:18:34.559> wallet<00:18:34.840> called 00:18:35.070 --> 00:18:35.080 align:start position:0% we're building this wallet called 00:18:35.080 --> 00:18:37.470 align:start position:0% we're building this wallet called obsidian<00:18:35.840> which<00:18:36.480> yes<00:18:36.919> that<00:18:37.080> one's<00:18:37.280> going<00:18:37.400> to 00:18:37.470 --> 00:18:37.480 align:start position:0% obsidian which yes that one's going to 00:18:37.480 --> 00:18:39.270 align:start position:0% obsidian which yes that one's going to be<00:18:37.679> interacted<00:18:38.159> with<00:18:38.320> Aztec<00:18:38.760> specifically 00:18:39.270 --> 00:18:39.280 align:start position:0% be interacted with Aztec specifically 00:18:39.280 --> 00:18:41.270 align:start position:0% be interacted with Aztec specifically and<00:18:39.440> going<00:18:39.520> to<00:18:39.640> integrate<00:18:40.039> ZK<00:18:40.400> passport<00:18:41.000> for 00:18:41.270 --> 00:18:41.280 align:start position:0% and going to integrate ZK passport for 00:18:41.280 --> 00:18:43.870 align:start position:0% and going to integrate ZK passport for compliance<00:18:41.760> and<00:18:42.280> privacy<00:18:43.280> mixed<00:18:43.640> with 00:18:43.870 --> 00:18:43.880 align:start position:0% compliance and privacy mixed with 00:18:43.880 --> 00:18:46.870 align:start position:0% compliance and privacy mixed with identity<00:18:44.559> at<00:18:44.840> the<00:18:45.039> wallet<00:18:45.320> level<00:18:45.600> on<00:18:45.880> atic 00:18:46.870 --> 00:18:46.880 align:start position:0% identity at the wallet level on atic 00:18:46.880 --> 00:18:47.750 align:start position:0% identity at the wallet level on atic yeah<00:18:47.000> there's<00:18:47.120> no<00:18:47.240> reason<00:18:47.440> this<00:18:47.559> can't<00:18:47.679> be 00:18:47.750 --> 00:18:47.760 align:start position:0% yeah there's no reason this can't be 00:18:47.760 --> 00:18:49.669 align:start position:0% yeah there's no reason this can't be used<00:18:47.960> on<00:18:48.080> other<00:18:48.200> chains<00:18:48.520> like<00:18:48.679> Alo<00:18:49.320> or<00:18:49.480> even 00:18:49.669 --> 00:18:49.679 align:start position:0% used on other chains like Alo or even 00:18:49.679 --> 00:18:52.270 align:start position:0% used on other chains like Alo or even like<00:18:49.880> ethereum<00:18:50.640> lay<00:18:50.880> one<00:18:51.600> um<00:18:51.880> but<00:18:52.000> it's<00:18:52.080> more 00:18:52.270 --> 00:18:52.280 align:start position:0% like ethereum lay one um but it's more 00:18:52.280 --> 00:18:54.149 align:start position:0% like ethereum lay one um but it's more suitable<00:18:52.640> as<00:18:52.760> suppose<00:18:53.000> on<00:18:53.159> privacy<00:18:53.480> chains 00:18:54.149 --> 00:18:54.159 align:start position:0% suitable as suppose on privacy chains 00:18:54.159 --> 00:18:56.549 align:start position:0% suitable as suppose on privacy chains where<00:18:54.280> you<00:18:54.360> can<00:18:54.480> have<00:18:54.679> these<00:18:55.000> uh<00:18:55.200> approv<00:18:55.559> data 00:18:56.549 --> 00:18:56.559 align:start position:0% where you can have these uh approv data 00:18:56.559 --> 00:18:59.310 align:start position:0% where you can have these uh approv data um<00:18:57.159> more<00:18:57.440> private<00:18:57.880> you<00:18:58.080> more<00:18:58.200> privately 00:18:59.310 --> 00:18:59.320 align:start position:0% um more private you more privately 00:18:59.320 --> 00:19:01.149 align:start position:0% um more private you more privately um<00:18:59.480> how<00:18:59.559> do<00:18:59.640> you<00:18:59.720> handle<00:18:59.960> the<00:19:00.039> ux<00:19:00.440> problem<00:19:01.000> of 00:19:01.149 --> 00:19:01.159 align:start position:0% um how do you handle the ux problem of 00:19:01.159 --> 00:19:02.909 align:start position:0% um how do you handle the ux problem of convincing<00:19:01.720> users<00:19:02.159> that<00:19:02.360> their<00:19:02.600> passport 00:19:02.909 --> 00:19:02.919 align:start position:0% convincing users that their passport 00:19:02.919 --> 00:19:04.830 align:start position:0% convincing users that their passport forther<00:19:03.360> remains<00:19:03.640> client<00:19:04.080> side<00:19:04.559> that's<00:19:04.679> a 00:19:04.830 --> 00:19:04.840 align:start position:0% forther remains client side that's a 00:19:04.840 --> 00:19:05.950 align:start position:0% forther remains client side that's a great<00:19:05.039> question<00:19:05.360> I<00:19:05.440> think<00:19:05.559> this<00:19:05.679> is<00:19:05.760> going<00:19:05.840> to 00:19:05.950 --> 00:19:05.960 align:start position:0% great question I think this is going to 00:19:05.960 --> 00:19:07.710 align:start position:0% great question I think this is going to be<00:19:06.039> a<00:19:06.159> challenge<00:19:06.600> and<00:19:07.200> it's<00:19:07.320> going<00:19:07.440> to<00:19:07.520> come 00:19:07.710 --> 00:19:07.720 align:start position:0% be a challenge and it's going to come 00:19:07.720 --> 00:19:10.390 align:start position:0% be a challenge and it's going to come down<00:19:07.880> to<00:19:08.360> to<00:19:08.919> Brand<00:19:09.240> trust<00:19:09.960> and<00:19:10.159> basically 00:19:10.390 --> 00:19:10.400 align:start position:0% down to to Brand trust and basically 00:19:10.400 --> 00:19:12.549 align:start position:0% down to to Brand trust and basically building<00:19:10.720> that<00:19:11.000> up<00:19:11.200> over<00:19:11.440> time<00:19:11.960> so<00:19:12.120> we've<00:19:12.280> got 00:19:12.549 --> 00:19:12.559 align:start position:0% building that up over time so we've got 00:19:12.559 --> 00:19:14.430 align:start position:0% building that up over time so we've got open<00:19:12.840> source<00:19:13.120> circuits<00:19:13.640> and<00:19:13.880> and<00:19:14.039> open<00:19:14.240> source 00:19:14.430 --> 00:19:14.440 align:start position:0% open source circuits and and open source 00:19:14.440 --> 00:19:15.990 align:start position:0% open source circuits and and open source codebase<00:19:15.080> I<00:19:15.159> think<00:19:15.320> that's<00:19:15.480> going<00:19:15.559> to<00:19:15.679> be 00:19:15.990 --> 00:19:16.000 align:start position:0% codebase I think that's going to be 00:19:16.000 --> 00:19:17.669 align:start position:0% codebase I think that's going to be that's<00:19:16.120> going<00:19:16.200> to<00:19:16.320> help<00:19:16.520> for<00:19:16.679> sure<00:19:17.480> uh<00:19:17.559> and 00:19:17.669 --> 00:19:17.679 align:start position:0% that's going to help for sure uh and 00:19:17.679 --> 00:19:19.549 align:start position:0% that's going to help for sure uh and just<00:19:17.840> being<00:19:18.039> like<00:19:18.200> critically<00:19:18.559> neutral<00:19:19.280> um 00:19:19.549 --> 00:19:19.559 align:start position:0% just being like critically neutral um 00:19:19.559 --> 00:19:20.950 align:start position:0% just being like critically neutral um you<00:19:19.640> know<00:19:19.799> people<00:19:19.960> can<00:19:20.039> trust<00:19:20.320> this<00:19:20.480> as<00:19:20.559> a<00:19:20.760> as 00:19:20.950 --> 00:19:20.960 align:start position:0% you know people can trust this as a as 00:19:20.960 --> 00:19:21.990 align:start position:0% you know people can trust this as a as as<00:19:21.039> a<00:19:21.159> brand<00:19:21.360> that's<00:19:21.480> going<00:19:21.600> to<00:19:21.720> respect 00:19:21.990 --> 00:19:22.000 align:start position:0% as a brand that's going to respect 00:19:22.000 --> 00:19:24.070 align:start position:0% as a brand that's going to respect privacy<00:19:22.360> it's<00:19:22.520> one<00:19:22.640> of<00:19:22.679> about<00:19:23.000> core<00:19:23.200> values<00:19:23.919> so 00:19:24.070 --> 00:19:24.080 align:start position:0% privacy it's one of about core values so 00:19:24.080 --> 00:19:25.350 align:start position:0% privacy it's one of about core values so that's<00:19:24.200> just<00:19:24.280> going<00:19:24.400> to<00:19:24.480> take<00:19:24.679> time<00:19:24.919> I<00:19:25.039> think 00:19:25.350 --> 00:19:25.360 align:start position:0% that's just going to take time I think 00:19:25.360 --> 00:19:27.310 align:start position:0% that's just going to take time I think and<00:19:25.640> and<00:19:25.880> you<00:19:26.000> know<00:19:26.760> demonstrating<00:19:27.240> it 00:19:27.310 --> 00:19:27.320 align:start position:0% and and you know demonstrating it 00:19:27.320 --> 00:19:30.270 align:start position:0% and and you know demonstrating it through<00:19:27.480> our<00:19:27.640> actions 00:19:30.270 --> 00:19:30.280 align:start position:0% through our actions 00:19:30.280 --> 00:19:32.720 align:start position:0% through our actions okay<00:19:30.480> make