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.830 align:start position:0% [Music] 00:00:09.830 --> 00:00:09.840 align:start position:0% [Music] 00:00:09.840 --> 00:00:12.990 align:start position:0% [Music] so<00:00:10.840> I<00:00:10.920> know<00:00:11.200> many<00:00:11.519> people<00:00:11.880> here<00:00:12.440> uh<00:00:12.559> work 00:00:12.990 --> 00:00:13.000 align:start position:0% so I know many people here uh work 00:00:13.000 --> 00:00:15.350 align:start position:0% so I know many people here uh work multiplying<00:00:13.920> matrices<00:00:14.639> and<00:00:14.839> like<00:00:15.000> doing<00:00:15.240> a 00:00:15.350 --> 00:00:15.360 align:start position:0% multiplying matrices and like doing a 00:00:15.360 --> 00:00:17.790 align:start position:0% multiplying matrices and like doing a lot<00:00:15.440> of<00:00:15.599> polinomial<00:00:16.320> day<00:00:16.440> in<00:00:16.720> day<00:00:16.880> out<00:00:17.520> uh<00:00:17.680> but 00:00:17.790 --> 00:00:17.800 align:start position:0% lot of polinomial day in day out uh but 00:00:17.800 --> 00:00:19.189 align:start position:0% lot of polinomial day in day out uh but I<00:00:17.880> think<00:00:18.000> my<00:00:18.160> talk<00:00:18.359> is<00:00:18.439> going<00:00:18.560> to<00:00:18.640> be<00:00:18.720> a<00:00:18.840> little 00:00:19.189 --> 00:00:19.199 align:start position:0% I think my talk is going to be a little 00:00:19.199 --> 00:00:21.349 align:start position:0% I think my talk is going to be a little higher<00:00:19.439> level<00:00:19.680> on<00:00:19.840> like<00:00:20.160> how<00:00:20.800> programmable 00:00:21.349 --> 00:00:21.359 align:start position:0% higher level on like how programmable 00:00:21.359 --> 00:00:23.109 align:start position:0% higher level on like how programmable cryptography<00:00:21.960> can<00:00:22.080> solve<00:00:22.439> one<00:00:22.560> of<00:00:22.720> the<00:00:23.080> I 00:00:23.109 --> 00:00:23.119 align:start position:0% cryptography can solve one of the I 00:00:23.119 --> 00:00:25.189 align:start position:0% cryptography can solve one of the I would<00:00:23.279> say<00:00:23.519> most<00:00:23.720> important<00:00:24.199> use<00:00:24.519> cases<00:00:24.920> for 00:00:25.189 --> 00:00:25.199 align:start position:0% would say most important use cases for 00:00:25.199 --> 00:00:28.109 align:start position:0% would say most important use cases for our<00:00:25.439> space<00:00:25.800> and<00:00:26.160> and<00:00:26.279> in<00:00:26.400> general<00:00:26.880> like<00:00:27.359> uh 00:00:28.109 --> 00:00:28.119 align:start position:0% our space and and in general like uh 00:00:28.119 --> 00:00:30.669 align:start position:0% our space and and in general like uh society<00:00:28.960> which<00:00:29.080> is<00:00:29.279> like<00:00:29.480> private<00:00:30.000> identities 00:00:30.669 --> 00:00:30.679 align:start position:0% society which is like private identities 00:00:30.679 --> 00:00:32.229 align:start position:0% society which is like private identities and<00:00:30.880> this<00:00:31.039> product<00:00:31.400> Vision<00:00:31.679> it<00:00:31.759> will<00:00:31.880> be<00:00:32.000> more 00:00:32.229 --> 00:00:32.239 align:start position:0% and this product Vision it will be more 00:00:32.239 --> 00:00:34.069 align:start position:0% and this product Vision it will be more like<00:00:32.360> a<00:00:32.599> high<00:00:32.800> level<00:00:33.040> overview<00:00:33.520> about<00:00:33.879> what 00:00:34.069 --> 00:00:34.079 align:start position:0% like a high level overview about what 00:00:34.079 --> 00:00:36.150 align:start position:0% like a high level overview about what characteristics<00:00:34.719> do<00:00:34.840> we<00:00:35.000> want<00:00:35.600> and<00:00:35.760> some<00:00:35.960> sort 00:00:36.150 --> 00:00:36.160 align:start position:0% characteristics do we want and some sort 00:00:36.160 --> 00:00:37.950 align:start position:0% characteristics do we want and some sort of<00:00:36.360> approaches<00:00:36.800> that<00:00:36.960> we<00:00:37.079> have<00:00:37.200> been<00:00:37.399> seeing 00:00:37.950 --> 00:00:37.960 align:start position:0% of approaches that we have been seeing 00:00:37.960 --> 00:00:40.670 align:start position:0% of approaches that we have been seeing in<00:00:38.120> the<00:00:38.280> space<00:00:39.200> um<00:00:39.920> yeah<00:00:40.079> trying<00:00:40.280> to<00:00:40.399> solve 00:00:40.670 --> 00:00:40.680 align:start position:0% in the space um yeah trying to solve 00:00:40.680 --> 00:00:43.709 align:start position:0% in the space um yeah trying to solve these<00:00:40.920> these<00:00:41.280> issues<00:00:42.280> so<00:00:42.920> as<00:00:43.079> we<00:00:43.239> are<00:00:43.520> in 00:00:43.709 --> 00:00:43.719 align:start position:0% these these issues so as we are in 00:00:43.719 --> 00:00:45.549 align:start position:0% these these issues so as we are in Thailand<00:00:44.280> I<00:00:44.399> thought<00:00:44.520> it<00:00:44.640> was<00:00:44.840> great<00:00:45.039> to<00:00:45.200> start 00:00:45.549 --> 00:00:45.559 align:start position:0% Thailand I thought it was great to start 00:00:45.559 --> 00:00:48.389 align:start position:0% Thailand I thought it was great to start with<00:00:45.879> uh<00:00:46.039> an<00:00:46.199> analogy<00:00:46.800> of<00:00:46.960> this<00:00:47.160> blind<00:00:47.520> man<00:00:48.280> uh 00:00:48.389 --> 00:00:48.399 align:start position:0% with uh an analogy of this blind man uh 00:00:48.399 --> 00:00:50.150 align:start position:0% with uh an analogy of this blind man uh elephant<00:00:48.960> illustration<00:00:49.600> because<00:00:49.920> this<00:00:50.000> is 00:00:50.150 --> 00:00:50.160 align:start position:0% elephant illustration because this is 00:00:50.160 --> 00:00:53.950 align:start position:0% elephant illustration because this is the<00:00:50.280> land<00:00:50.480> of<00:00:50.640> the<00:00:50.800> white<00:00:51.399> elephants<00:00:52.760> um<00:00:53.760> I 00:00:53.950 --> 00:00:53.960 align:start position:0% the land of the white elephants um I 00:00:53.960 --> 00:00:55.549 align:start position:0% the land of the white elephants um I think<00:00:54.520> where<00:00:54.680> people<00:00:54.879> who<00:00:55.000> are<00:00:55.160> inside<00:00:55.440> the 00:00:55.549 --> 00:00:55.559 align:start position:0% think where people who are inside the 00:00:55.559 --> 00:00:57.270 align:start position:0% think where people who are inside the identity<00:00:55.960> space<00:00:56.320> we<00:00:56.440> kind<00:00:56.559> of<00:00:56.680> like<00:00:56.800> see<00:00:57.039> a<00:00:57.160> lot 00:00:57.270 --> 00:00:57.280 align:start position:0% identity space we kind of like see a lot 00:00:57.280 --> 00:01:00.869 align:start position:0% identity space we kind of like see a lot of<00:00:57.520> acronyms<00:00:58.039> thr<00:00:58.640> everywhere<00:00:59.239> like<00:00:59.440> Dad<00:01:00.160> pod 00:01:00.869 --> 00:01:00.879 align:start position:0% of acronyms thr everywhere like Dad pod 00:01:00.879 --> 00:01:04.229 align:start position:0% of acronyms thr everywhere like Dad pod SSI<00:01:01.879> um<00:01:02.199> and<00:01:02.480> those<00:01:02.640> are<00:01:03.120> these<00:01:03.359> idea<00:01:03.800> like 00:01:04.229 --> 00:01:04.239 align:start position:0% SSI um and those are these idea like 00:01:04.239 --> 00:01:06.190 align:start position:0% SSI um and those are these idea like self-sovereign<00:01:05.000> identities<00:01:05.680> verifiable 00:01:06.190 --> 00:01:06.200 align:start position:0% self-sovereign identities verifiable 00:01:06.200 --> 00:01:07.670 align:start position:0% self-sovereign identities verifiable credential<00:01:06.760> decentralized<00:01:07.280> identities 00:01:07.670 --> 00:01:07.680 align:start position:0% credential decentralized identities 00:01:07.680 --> 00:01:11.109 align:start position:0% credential decentralized identities those<00:01:07.840> are<00:01:08.400> useful<00:01:09.360> and<00:01:09.680> have<00:01:10.119> nuances<00:01:10.840> but<00:01:11.000> at 00:01:11.109 --> 00:01:11.119 align:start position:0% those are useful and have nuances but at 00:01:11.119 --> 00:01:13.070 align:start position:0% those are useful and have nuances but at the<00:01:11.200> end<00:01:11.400> it<00:01:11.600> has<00:01:12.000> some<00:01:12.240> core<00:01:12.600> properties 00:01:13.070 --> 00:01:13.080 align:start position:0% the end it has some core properties 00:01:13.080 --> 00:01:15.510 align:start position:0% the end it has some core properties which<00:01:13.360> I<00:01:13.439> want<00:01:13.560> to<00:01:13.840> like<00:01:14.040> explore<00:01:14.400> in<00:01:14.600> this 00:01:15.510 --> 00:01:15.520 align:start position:0% which I want to like explore in this 00:01:15.520 --> 00:01:18.429 align:start position:0% which I want to like explore in this talk<00:01:16.520> I'll<00:01:16.759> say<00:01:17.360> these<00:01:17.560> are<00:01:17.799> the<00:01:18.000> properties 00:01:18.429 --> 00:01:18.439 align:start position:0% talk I'll say these are the properties 00:01:18.439 --> 00:01:20.749 align:start position:0% talk I'll say these are the properties that<00:01:18.600> we<00:01:18.759> care<00:01:19.600> um<00:01:19.799> and<00:01:19.960> probably<00:01:20.240> we<00:01:20.320> can<00:01:20.479> grow 00:01:20.749 --> 00:01:20.759 align:start position:0% that we care um and probably we can grow 00:01:20.759 --> 00:01:22.590 align:start position:0% that we care um and probably we can grow the<00:01:20.840> list<00:01:21.079> even<00:01:21.280> more<00:01:21.479> and<00:01:21.600> we<00:01:21.680> can<00:01:21.840> even<00:01:22.040> make 00:01:22.590 --> 00:01:22.600 align:start position:0% the list even more and we can even make 00:01:22.600 --> 00:01:25.030 align:start position:0% the list even more and we can even make um<00:01:22.880> security<00:01:23.640> assumptions<00:01:24.240> models<00:01:24.640> to 00:01:25.030 --> 00:01:25.040 align:start position:0% um security assumptions models to 00:01:25.040 --> 00:01:27.030 align:start position:0% um security assumptions models to understand<00:01:25.360> how<00:01:25.720> like<00:01:25.880> in<00:01:26.159> which<00:01:26.439> sense<00:01:26.799> these 00:01:27.030 --> 00:01:27.040 align:start position:0% understand how like in which sense these 00:01:27.040 --> 00:01:28.830 align:start position:0% understand how like in which sense these properties<00:01:27.439> we<00:01:27.560> want<00:01:27.680> to<00:01:27.880> achieve<00:01:28.520> want<00:01:28.680> of 00:01:28.830 --> 00:01:28.840 align:start position:0% properties we want to achieve want of 00:01:28.840 --> 00:01:30.870 align:start position:0% properties we want to achieve want of flexibility<00:01:29.400> we<00:01:29.520> want<00:01:29.640> to<00:01:29.960> verifiability<00:01:30.799> we 00:01:30.870 --> 00:01:30.880 align:start position:0% flexibility we want to verifiability we 00:01:30.880 --> 00:01:33.109 align:start position:0% flexibility we want to verifiability we want<00:01:31.200> privacy<00:01:31.680> we<00:01:31.759> want<00:01:32.119> decentralization 00:01:33.109 --> 00:01:33.119 align:start position:0% want privacy we want decentralization 00:01:33.119 --> 00:01:36.749 align:start position:0% want privacy we want decentralization self<00:01:33.439> ownership<00:01:34.439> transfers<00:01:34.960> ship<00:01:35.520> etc<00:01:36.040> etc 00:01:36.749 --> 00:01:36.759 align:start position:0% self ownership transfers ship etc etc 00:01:36.759 --> 00:01:39.109 align:start position:0% self ownership transfers ship etc etc etc<00:01:37.759> but<00:01:37.920> I<00:01:37.960> would<00:01:38.079> say<00:01:38.240> if<00:01:38.320> I<00:01:38.399> were<00:01:38.560> to<00:01:38.720> sum<00:01:38.960> it 00:01:39.109 --> 00:01:39.119 align:start position:0% etc but I would say if I were to sum it 00:01:39.119 --> 00:01:41.710 align:start position:0% etc but I would say if I were to sum it up<00:01:39.360> to<00:01:39.600> like<00:01:39.799> the<00:01:40.040> core<00:01:40.560> core<00:01:41.040> properties<00:01:41.560> that 00:01:41.710 --> 00:01:41.720 align:start position:0% up to like the core core properties that 00:01:41.720 --> 00:01:44.069 align:start position:0% up to like the core core properties that we<00:01:41.880> really<00:01:42.079> want<00:01:42.240> to<00:01:42.560> key<00:01:43.119> achieve<00:01:43.520> with<00:01:43.720> this 00:01:44.069 --> 00:01:44.079 align:start position:0% we really want to key achieve with this 00:01:44.079 --> 00:01:47.709 align:start position:0% we really want to key achieve with this are<00:01:45.000> um<00:01:45.920> basically<00:01:46.399> three<00:01:46.799> actions<00:01:47.399> that<00:01:47.600> I 00:01:47.709 --> 00:01:47.719 align:start position:0% are um basically three actions that I 00:01:47.719 --> 00:01:49.749 align:start position:0% are um basically three actions that I think<00:01:47.960> we<00:01:48.079> should<00:01:48.759> uh<00:01:48.920> pursue<00:01:49.280> and<00:01:49.439> target 00:01:49.749 --> 00:01:49.759 align:start position:0% think we should uh pursue and target 00:01:49.759 --> 00:01:51.310 align:start position:0% think we should uh pursue and target with<00:01:49.920> programmable<00:01:50.360> cryptography<00:01:50.960> in<00:01:51.119> this 00:01:51.310 --> 00:01:51.320 align:start position:0% with programmable cryptography in this 00:01:51.320 --> 00:01:52.389 align:start position:0% with programmable cryptography in this identity 00:01:52.389 --> 00:01:52.399 align:start position:0% identity 00:01:52.399 --> 00:01:55.310 align:start position:0% identity space<00:01:53.399> first<00:01:54.040> uh<00:01:54.240> and<00:01:54.439> and<00:01:54.560> the<00:01:54.680> ones<00:01:54.880> bolded 00:01:55.310 --> 00:01:55.320 align:start position:0% space first uh and and the ones bolded 00:01:55.320 --> 00:01:57.590 align:start position:0% space first uh and and the ones bolded are<00:01:55.600> things<00:01:55.880> that<00:01:56.119> a<00:01:56.240> user<00:01:56.560> will<00:01:56.799> typically<00:01:57.200> do 00:01:57.590 --> 00:01:57.600 align:start position:0% are things that a user will typically do 00:01:57.600 --> 00:01:59.630 align:start position:0% are things that a user will typically do in<00:01:57.719> order<00:01:58.000> to<00:01:58.439> leverage<00:01:58.960> private<00:01:59.240> identities 00:01:59.630 --> 00:01:59.640 align:start position:0% in order to leverage private identities 00:01:59.640 --> 00:02:00.469 align:start position:0% in order to leverage private identities one<00:01:59.759> is 00:02:00.469 --> 00:02:00.479 align:start position:0% one is 00:02:00.479 --> 00:02:02.670 align:start position:0% one is the<00:02:00.680> capacity<00:02:01.079> to<00:02:01.320> import<00:02:01.680> all<00:02:01.840> my<00:02:02.079> identities 00:02:02.670 --> 00:02:02.680 align:start position:0% the capacity to import all my identities 00:02:02.680 --> 00:02:05.749 align:start position:0% the capacity to import all my identities and<00:02:02.880> data<00:02:03.280> into<00:02:03.640> something<00:02:04.200> a<00:02:04.560> container<00:02:05.560> um 00:02:05.749 --> 00:02:05.759 align:start position:0% and data into something a container um 00:02:05.759 --> 00:02:07.789 align:start position:0% and data into something a container um let's<00:02:05.960> call<00:02:06.079> it<00:02:06.200> a<00:02:06.320> wallet<00:02:06.600> for<00:02:06.799> now<00:02:07.560> the<00:02:07.640> other 00:02:07.789 --> 00:02:07.799 align:start position:0% let's call it a wallet for now the other 00:02:07.799 --> 00:02:09.869 align:start position:0% let's call it a wallet for now the other one<00:02:07.960> is<00:02:08.080> to<00:02:08.200> generate<00:02:08.640> proofs<00:02:09.080> or<00:02:09.280> generate<00:02:09.679> an 00:02:09.869 --> 00:02:09.879 align:start position:0% one is to generate proofs or generate an 00:02:09.879 --> 00:02:13.589 align:start position:0% one is to generate proofs or generate an artifact<00:02:10.840> that<00:02:11.080> then<00:02:11.200> I<00:02:11.319> can<00:02:11.640> take<00:02:12.239> and<00:02:12.599> then 00:02:13.589 --> 00:02:13.599 align:start position:0% artifact that then I can take and then 00:02:13.599 --> 00:02:15.670 align:start position:0% artifact that then I can take and then uh<00:02:13.760> proof<00:02:14.400> an<00:02:14.640> identity<00:02:15.080> an<00:02:15.239> attribute 00:02:15.670 --> 00:02:15.680 align:start position:0% uh proof an identity an attribute 00:02:15.680 --> 00:02:18.229 align:start position:0% uh proof an identity an attribute something<00:02:16.040> about<00:02:16.319> myself<00:02:16.959> so<00:02:17.200> that<00:02:17.519> I<00:02:17.640> can 00:02:18.229 --> 00:02:18.239 align:start position:0% something about myself so that I can 00:02:18.239 --> 00:02:19.949 align:start position:0% something about myself so that I can execute<00:02:18.599> an<00:02:18.800> action<00:02:19.080> so<00:02:19.280> my<00:02:19.440> proofs<00:02:19.760> being 00:02:19.949 --> 00:02:19.959 align:start position:0% execute an action so my proofs being 00:02:19.959 --> 00:02:20.949 align:start position:0% execute an action so my proofs being useful 00:02:20.949 --> 00:02:20.959 align:start position:0% useful 00:02:20.959 --> 00:02:23.430 align:start position:0% useful elsewhere<00:02:21.959> so<00:02:22.160> if<00:02:22.400> we<00:02:22.519> were<00:02:22.720> to<00:02:22.879> summarize 00:02:23.430 --> 00:02:23.440 align:start position:0% elsewhere so if we were to summarize 00:02:23.440 --> 00:02:24.990 align:start position:0% elsewhere so if we were to summarize like<00:02:23.560> all<00:02:23.760> the<00:02:24.000> complexity<00:02:24.480> that<00:02:24.599> we<00:02:24.720> have<00:02:24.840> in 00:02:24.990 --> 00:02:25.000 align:start position:0% like all the complexity that we have in 00:02:25.000 --> 00:02:26.509 align:start position:0% like all the complexity that we have in these<00:02:25.319> three<00:02:25.680> kind<00:02:25.800> of<00:02:25.879> like<00:02:26.040> steps<00:02:26.319> and 00:02:26.509 --> 00:02:26.519 align:start position:0% these three kind of like steps and 00:02:26.519 --> 00:02:28.949 align:start position:0% these three kind of like steps and actions<00:02:27.040> it<00:02:27.160> turns<00:02:27.480> out<00:02:27.800> that<00:02:28.080> it's<00:02:28.519> uh<00:02:28.680> a<00:02:28.800> bit 00:02:28.949 --> 00:02:28.959 align:start position:0% actions it turns out that it's uh a bit 00:02:28.959 --> 00:02:31.470 align:start position:0% actions it turns out that it's uh a bit easier<00:02:29.280> to<00:02:30.239> about<00:02:30.519> like<00:02:30.800> what<00:02:30.959> type<00:02:31.160> of<00:02:31.360> like 00:02:31.470 --> 00:02:31.480 align:start position:0% easier to about like what type of like 00:02:31.480 --> 00:02:33.030 align:start position:0% easier to about like what type of like cryptography<00:02:32.000> systems<00:02:32.319> and<00:02:32.480> targets<00:02:32.800> do<00:02:32.920> we 00:02:33.030 --> 00:02:33.040 align:start position:0% cryptography systems and targets do we 00:02:33.040 --> 00:02:34.509 align:start position:0% cryptography systems and targets do we want<00:02:33.120> to<00:02:33.400> achieve<00:02:33.840> with<00:02:34.000> programmable 00:02:34.509 --> 00:02:34.519 align:start position:0% want to achieve with programmable 00:02:34.519 --> 00:02:36.750 align:start position:0% want to achieve with programmable cryptography<00:02:35.360> in<00:02:35.800> uh 00:02:36.750 --> 00:02:36.760 align:start position:0% cryptography in uh 00:02:36.760 --> 00:02:39.030 align:start position:0% cryptography in uh identity<00:02:37.760> so<00:02:37.959> the<00:02:38.080> first<00:02:38.239> section<00:02:38.560> is<00:02:38.879> let's 00:02:39.030 --> 00:02:39.040 align:start position:0% identity so the first section is let's 00:02:39.040 --> 00:02:40.750 align:start position:0% identity so the first section is let's import<00:02:39.360> all<00:02:39.879> let's<00:02:40.080> import<00:02:40.400> all<00:02:40.599> my 00:02:40.750 --> 00:02:40.760 align:start position:0% import all let's import all my 00:02:40.760 --> 00:02:43.190 align:start position:0% import all let's import all my identities<00:02:41.360> my<00:02:41.560> data<00:02:42.440> uh<00:02:42.599> and<00:02:42.760> what<00:02:42.840> does<00:02:43.040> that 00:02:43.190 --> 00:02:43.200 align:start position:0% identities my data uh and what does that 00:02:43.200 --> 00:02:47.149 align:start position:0% identities my data uh and what does that mean<00:02:44.200> it<00:02:44.360> means<00:02:44.720> that<00:02:45.239> for<00:02:45.519> all<00:02:45.879> the<00:02:46.280> documents 00:02:47.149 --> 00:02:47.159 align:start position:0% mean it means that for all the documents 00:02:47.159 --> 00:02:49.509 align:start position:0% mean it means that for all the documents and<00:02:47.760> data<00:02:48.280> that<00:02:48.480> exists<00:02:48.800> in<00:02:48.920> the<00:02:49.000> world<00:02:49.200> in<00:02:49.319> the 00:02:49.509 --> 00:02:49.519 align:start position:0% and data that exists in the world in the 00:02:49.519 --> 00:02:52.630 align:start position:0% and data that exists in the world in the digital<00:02:49.920> space<00:02:50.680> anything<00:02:51.080> that<00:02:51.200> is<00:02:51.440> signed<00:02:52.440> we 00:02:52.630 --> 00:02:52.640 align:start position:0% digital space anything that is signed we 00:02:52.640 --> 00:02:55.229 align:start position:0% digital space anything that is signed we should<00:02:53.040> and<00:02:53.239> want<00:02:53.440> to<00:02:53.640> Target<00:02:54.080> it<00:02:54.280> to<00:02:54.480> bring<00:02:54.720> it 00:02:55.229 --> 00:02:55.239 align:start position:0% should and want to Target it to bring it 00:02:55.239 --> 00:02:58.350 align:start position:0% should and want to Target it to bring it to<00:02:55.800> private<00:02:56.400> identities<00:02:57.400> um<00:02:57.640> cryptography 00:02:58.350 --> 00:02:58.360 align:start position:0% to private identities um cryptography 00:02:58.360 --> 00:03:00.750 align:start position:0% to private identities um cryptography use<00:02:58.640> cases<00:02:59.400> and<00:02:59.519> that<00:02:59.640> means<00:02:59.840> means<00:03:00.360> obvious 00:03:00.750 --> 00:03:00.760 align:start position:0% use cases and that means means obvious 00:03:00.760 --> 00:03:02.589 align:start position:0% use cases and that means means obvious things<00:03:01.040> like<00:03:01.159> your<00:03:01.360> national<00:03:01.720> ID<00:03:02.040> card<00:03:02.319> your 00:03:02.589 --> 00:03:02.599 align:start position:0% things like your national ID card your 00:03:02.599 --> 00:03:05.390 align:start position:0% things like your national ID card your passport<00:03:03.080> there<00:03:03.159> are<00:03:03.480> great<00:03:03.720> teams<00:03:04.599> um<00:03:05.200> in 00:03:05.390 --> 00:03:05.400 align:start position:0% passport there are great teams um in 00:03:05.400 --> 00:03:07.309 align:start position:0% passport there are great teams um in here<00:03:05.959> targeting<00:03:06.360> that<00:03:06.640> but<00:03:06.799> also<00:03:06.959> driver 00:03:07.309 --> 00:03:07.319 align:start position:0% here targeting that but also driver 00:03:07.319 --> 00:03:10.869 align:start position:0% here targeting that but also driver licenses<00:03:07.879> sign<00:03:08.200> documents<00:03:09.080> PDFs<00:03:10.080> credit<00:03:10.440> card 00:03:10.869 --> 00:03:10.879 align:start position:0% licenses sign documents PDFs credit card 00:03:10.879 --> 00:03:13.190 align:start position:0% licenses sign documents PDFs credit card transactions<00:03:11.840> maybe<00:03:12.080> we<00:03:12.200> can<00:03:12.400> like<00:03:12.680> Leverage 00:03:13.190 --> 00:03:13.200 align:start position:0% transactions maybe we can like Leverage 00:03:13.200 --> 00:03:15.789 align:start position:0% transactions maybe we can like Leverage from<00:03:13.799> WhatsApp<00:03:14.239> telegram<00:03:14.799> over<00:03:15.159> reputation 00:03:15.789 --> 00:03:15.799 align:start position:0% from WhatsApp telegram over reputation 00:03:15.799 --> 00:03:18.509 align:start position:0% from WhatsApp telegram over reputation social<00:03:16.200> graphs<00:03:16.879> Spotify<00:03:17.560> history<00:03:18.239> there's 00:03:18.509 --> 00:03:18.519 align:start position:0% social graphs Spotify history there's 00:03:18.519 --> 00:03:20.350 align:start position:0% social graphs Spotify history there's all<00:03:18.799> this<00:03:19.000> signed<00:03:19.360> data<00:03:19.840> that<00:03:20.000> I<00:03:20.080> think<00:03:20.239> we 00:03:20.350 --> 00:03:20.360 align:start position:0% all this signed data that I think we 00:03:20.360 --> 00:03:23.030 align:start position:0% all this signed data that I think we need<00:03:20.480> to<00:03:20.879> hijack<00:03:21.799> and<00:03:22.040> literally<00:03:22.680> start 00:03:23.030 --> 00:03:23.040 align:start position:0% need to hijack and literally start 00:03:23.040 --> 00:03:25.789 align:start position:0% need to hijack and literally start adding<00:03:23.360> into<00:03:23.879> all<00:03:24.000> of<00:03:24.200> these<00:03:24.519> containers<00:03:25.319> that 00:03:25.789 --> 00:03:25.799 align:start position:0% adding into all of these containers that 00:03:25.799 --> 00:03:27.070 align:start position:0% adding into all of these containers that it<00:03:25.920> can<00:03:26.040> be<00:03:26.200> called<00:03:26.519> it<00:03:26.599> can<00:03:26.760> have<00:03:26.920> very 00:03:27.070 --> 00:03:27.080 align:start position:0% it can be called it can have very 00:03:27.080 --> 00:03:28.630 align:start position:0% it can be called it can have very different<00:03:27.319> names<00:03:27.879> and<00:03:27.959> we<00:03:28.080> need<00:03:28.200> to<00:03:28.319> do<00:03:28.480> that 00:03:28.630 --> 00:03:28.640 align:start position:0% different names and we need to do that 00:03:28.640 --> 00:03:31.030 align:start position:0% different names and we need to do that permissionless<00:03:29.599> that<00:03:29.840> means<00:03:30.120> without<00:03:30.480> asking 00:03:31.030 --> 00:03:31.040 align:start position:0% permissionless that means without asking 00:03:31.040 --> 00:03:32.630 align:start position:0% permissionless that means without asking the<00:03:31.200> national<00:03:31.599> government<00:03:31.959> to<00:03:32.120> allow<00:03:32.360> us<00:03:32.480> to 00:03:32.630 --> 00:03:32.640 align:start position:0% the national government to allow us to 00:03:32.640 --> 00:03:35.110 align:start position:0% the national government to allow us to do<00:03:32.879> that<00:03:33.480> we<00:03:33.599> need<00:03:33.760> to<00:03:34.000> do<00:03:34.200> that<00:03:34.480> privately 00:03:35.110 --> 00:03:35.120 align:start position:0% do that we need to do that privately 00:03:35.120 --> 00:03:36.910 align:start position:0% do that we need to do that privately without<00:03:35.519> them<00:03:35.879> realizing<00:03:36.480> that<00:03:36.720> because 00:03:36.910 --> 00:03:36.920 align:start position:0% without them realizing that because 00:03:36.920 --> 00:03:38.589 align:start position:0% without them realizing that because maybe<00:03:37.159> you<00:03:37.280> want<00:03:37.439> to<00:03:37.560> use<00:03:37.799> it<00:03:37.920> for<00:03:38.239> things<00:03:38.439> that 00:03:38.589 --> 00:03:38.599 align:start position:0% maybe you want to use it for things that 00:03:38.599 --> 00:03:40.190 align:start position:0% maybe you want to use it for things that the<00:03:38.720> government<00:03:39.040> doesn't<00:03:39.319> approve<00:03:39.640> or<00:03:39.840> the 00:03:40.190 --> 00:03:40.200 align:start position:0% the government doesn't approve or the 00:03:40.200 --> 00:03:42.470 align:start position:0% the government doesn't approve or the Spotify<00:03:40.720> or<00:03:40.840> whoever<00:03:41.680> and<00:03:41.799> we<00:03:41.920> want<00:03:42.000> to<00:03:42.239> make 00:03:42.470 --> 00:03:42.480 align:start position:0% Spotify or whoever and we want to make 00:03:42.480 --> 00:03:43.789 align:start position:0% Spotify or whoever and we want to make that<00:03:42.640> data 00:03:43.789 --> 00:03:43.799 align:start position:0% that data 00:03:43.799 --> 00:03:47.270 align:start position:0% that data verifiable<00:03:44.799> that's<00:03:45.080> why<00:03:45.760> CK<00:03:46.120> npcf<00:03:46.920> and<00:03:47.040> other 00:03:47.270 --> 00:03:47.280 align:start position:0% verifiable that's why CK npcf and other 00:03:47.280 --> 00:03:48.750 align:start position:0% verifiable that's why CK npcf and other programmable<00:03:47.760> cryptography<00:03:48.319> Technologies 00:03:48.750 --> 00:03:48.760 align:start position:0% programmable cryptography Technologies 00:03:48.760 --> 00:03:50.750 align:start position:0% programmable cryptography Technologies are<00:03:48.920> so<00:03:49.200> good<00:03:49.720> and<00:03:49.840> we<00:03:49.959> need<00:03:50.080> to<00:03:50.200> achieve<00:03:50.599> like 00:03:50.750 --> 00:03:50.760 align:start position:0% are so good and we need to achieve like 00:03:50.760 --> 00:03:53.030 align:start position:0% are so good and we need to achieve like a<00:03:50.920> web<00:03:51.200> two<00:03:51.720> user<00:03:52.159> experience<00:03:52.560> in<00:03:52.680> order<00:03:52.879> for 00:03:53.030 --> 00:03:53.040 align:start position:0% a web two user experience in order for 00:03:53.040 --> 00:03:55.550 align:start position:0% a web two user experience in order for this<00:03:53.200> to<00:03:53.319> be<00:03:53.480> useful<00:03:54.159> and<00:03:54.439> get 00:03:55.550 --> 00:03:55.560 align:start position:0% this to be useful and get 00:03:55.560 --> 00:03:57.710 align:start position:0% this to be useful and get adoption<00:03:56.560> and<00:03:56.720> that<00:03:56.840> means<00:03:57.200> technically<00:03:57.599> that 00:03:57.710 --> 00:03:57.720 align:start position:0% adoption and that means technically that 00:03:57.720 --> 00:03:59.110 align:start position:0% adoption and that means technically that we<00:03:57.799> have<00:03:57.920> a<00:03:58.000> lot<00:03:58.120> of<00:03:58.239> challenges<00:03:58.760> that<00:03:58.879> we<00:03:59.000> need 00:03:59.110 --> 00:03:59.120 align:start position:0% we have a lot of challenges that we need 00:03:59.120 --> 00:04:01.470 align:start position:0% we have a lot of challenges that we need to<00:03:59.360> support<00:03:59.920> a<00:04:00.000> lot<00:04:00.079> of<00:04:00.200> hashing<00:04:00.599> mechanisms<00:04:01.360> a 00:04:01.470 --> 00:04:01.480 align:start position:0% to support a lot of hashing mechanisms a 00:04:01.480 --> 00:04:03.069 align:start position:0% to support a lot of hashing mechanisms a lot<00:04:01.599> of<00:04:01.720> signature<00:04:02.159> schemes<00:04:02.519> a<00:04:02.599> lot<00:04:02.720> of<00:04:02.799> dat 00:04:03.069 --> 00:04:03.079 align:start position:0% lot of signature schemes a lot of dat 00:04:03.079 --> 00:04:05.429 align:start position:0% lot of signature schemes a lot of dat structures<00:04:03.840> uh<00:04:04.040> standards<00:04:05.000> uh<00:04:05.120> that<00:04:05.239> means 00:04:05.429 --> 00:04:05.439 align:start position:0% structures uh standards uh that means 00:04:05.439 --> 00:04:07.030 align:start position:0% structures uh standards uh that means that<00:04:05.560> we<00:04:05.640> need<00:04:05.760> to<00:04:05.879> invent<00:04:06.280> new<00:04:06.519> things<00:04:06.879> like 00:04:07.030 --> 00:04:07.040 align:start position:0% that we need to invent new things like 00:04:07.040 --> 00:04:09.270 align:start position:0% that we need to invent new things like not<00:04:07.159> only<00:04:07.799> wrap<00:04:08.079> things<00:04:08.280> into<00:04:08.519> CK<00:04:08.920> but<00:04:09.040> also 00:04:09.270 --> 00:04:09.280 align:start position:0% not only wrap things into CK but also 00:04:09.280 --> 00:04:12.470 align:start position:0% not only wrap things into CK but also like<00:04:09.560> 2pc<00:04:10.120> and<00:04:10.239> NPC<00:04:10.720> a<00:04:10.920> proxies<00:04:11.439> and<00:04:12.079> have<00:04:12.280> like 00:04:12.470 --> 00:04:12.480 align:start position:0% like 2pc and NPC a proxies and have like 00:04:12.480 --> 00:04:14.470 align:start position:0% like 2pc and NPC a proxies and have like wallet<00:04:12.879> like<00:04:13.200> experiences<00:04:14.079> if<00:04:14.200> we<00:04:14.360> really 00:04:14.470 --> 00:04:14.480 align:start position:0% wallet like experiences if we really 00:04:14.480 --> 00:04:17.030 align:start position:0% wallet like experiences if we really want<00:04:14.599> to<00:04:14.840> achieve<00:04:15.200> this<00:04:15.799> property<00:04:16.639> the<00:04:16.759> other 00:04:17.030 --> 00:04:17.040 align:start position:0% want to achieve this property the other 00:04:17.040 --> 00:04:19.509 align:start position:0% want to achieve this property the other one<00:04:17.199> is<00:04:17.560> proof<00:04:17.919> facts<00:04:18.199> about<00:04:18.560> them<00:04:19.160> and<00:04:19.280> if<00:04:19.400> we 00:04:19.509 --> 00:04:19.519 align:start position:0% one is proof facts about them and if we 00:04:19.519 --> 00:04:21.469 align:start position:0% one is proof facts about them and if we want<00:04:19.639> to<00:04:19.959> have<00:04:20.079> a<00:04:20.280> great<00:04:20.479> user<00:04:20.840> experience 00:04:21.469 --> 00:04:21.479 align:start position:0% want to have a great user experience 00:04:21.479 --> 00:04:24.430 align:start position:0% want to have a great user experience then<00:04:22.120> we<00:04:22.240> need<00:04:22.400> to<00:04:22.639> generate<00:04:23.240> proofs<00:04:24.240> in 00:04:24.430 --> 00:04:24.440 align:start position:0% then we need to generate proofs in 00:04:24.440 --> 00:04:26.510 align:start position:0% then we need to generate proofs in useful<00:04:24.880> ways<00:04:25.240> doing<00:04:25.520> selective<00:04:25.919> disclosure 00:04:26.510 --> 00:04:26.520 align:start position:0% useful ways doing selective disclosure 00:04:26.520 --> 00:04:28.670 align:start position:0% useful ways doing selective disclosure in<00:04:26.919> things<00:04:27.199> like<00:04:27.440> less<00:04:27.600> than<00:04:27.759> one<00:04:27.960> second<00:04:28.520> in 00:04:28.670 --> 00:04:28.680 align:start position:0% in things like less than one second in 00:04:28.680 --> 00:04:30.710 align:start position:0% in things like less than one second in targets<00:04:29.080> where<00:04:29.240> our<00:04:29.400> user<00:04:29.919> are<00:04:30.000> going<00:04:30.120> to<00:04:30.280> be 00:04:30.710 --> 00:04:30.720 align:start position:0% targets where our user are going to be 00:04:30.720 --> 00:04:33.390 align:start position:0% targets where our user are going to be and<00:04:30.880> that<00:04:31.000> means<00:04:31.400> browser<00:04:32.039> in<00:04:32.240> your<00:04:32.800> laptop 00:04:33.390 --> 00:04:33.400 align:start position:0% and that means browser in your laptop 00:04:33.400 --> 00:04:35.110 align:start position:0% and that means browser in your laptop but<00:04:33.560> also<00:04:33.759> browser<00:04:34.120> in<00:04:34.199> your<00:04:34.400> phone<00:04:34.759> and<00:04:34.919> also 00:04:35.110 --> 00:04:35.120 align:start position:0% but also browser in your phone and also 00:04:35.120 --> 00:04:38.110 align:start position:0% but also browser in your phone and also means<00:04:35.520> native<00:04:35.880> phone<00:04:36.280> like<00:04:36.520> apps<00:04:37.479> um<00:04:37.880> and<00:04:38.000> that 00:04:38.110 --> 00:04:38.120 align:start position:0% means native phone like apps um and that 00:04:38.120 --> 00:04:40.749 align:start position:0% means native phone like apps um and that means<00:04:38.440> mobile<00:04:39.440> mo<00:04:39.680> mobile<00:04:40.120> side<00:04:40.320> proving<00:04:40.639> or 00:04:40.749 --> 00:04:40.759 align:start position:0% means mobile mo mobile side proving or 00:04:40.759 --> 00:04:42.029 align:start position:0% means mobile mo mobile side proving or client<00:04:41.080> side<00:04:41.199> proving<00:04:41.440> is<00:04:41.639> extremely 00:04:42.029 --> 00:04:42.039 align:start position:0% client side proving is extremely 00:04:42.039 --> 00:04:44.390 align:start position:0% client side proving is extremely important<00:04:42.600> which<00:04:42.960> not<00:04:43.240> every<00:04:43.880> programmable 00:04:44.390 --> 00:04:44.400 align:start position:0% important which not every programmable 00:04:44.400 --> 00:04:46.510 align:start position:0% important which not every programmable cryptography<00:04:45.039> project<00:04:45.360> is<00:04:45.639> is<00:04:45.840> is<00:04:45.960> targeting 00:04:46.510 --> 00:04:46.520 align:start position:0% cryptography project is is is targeting 00:04:46.520 --> 00:04:48.430 align:start position:0% cryptography project is is is targeting and<00:04:46.600> it<00:04:46.759> needs<00:04:46.960> to<00:04:47.039> be<00:04:47.199> very<00:04:47.400> cheap<00:04:47.840> or<00:04:48.199> even 00:04:48.430 --> 00:04:48.440 align:start position:0% and it needs to be very cheap or even 00:04:48.440 --> 00:04:50.350 align:start position:0% and it needs to be very cheap or even free<00:04:49.000> it<00:04:49.120> needs<00:04:49.280> to<00:04:49.360> be<00:04:49.520> very<00:04:49.720> easy<00:04:49.960> for<00:04:50.120> me<00:04:50.280> as 00:04:50.350 --> 00:04:50.360 align:start position:0% free it needs to be very easy for me as 00:04:50.360 --> 00:04:52.990 align:start position:0% free it needs to be very easy for me as a<00:04:50.479> non-technical<00:04:51.039> user<00:04:51.360> to<00:04:51.960> leverage<00:04:52.440> my<00:04:52.639> data 00:04:52.990 --> 00:04:53.000 align:start position:0% a non-technical user to leverage my data 00:04:53.000 --> 00:04:55.029 align:start position:0% a non-technical user to leverage my data and<00:04:53.199> import<00:04:53.520> it<00:04:53.960> and<00:04:54.120> generate<00:04:54.520> facts<00:04:54.840> about 00:04:55.029 --> 00:04:55.039 align:start position:0% and import it and generate facts about 00:04:55.039 --> 00:04:57.790 align:start position:0% and import it and generate facts about it<00:04:55.400> whenever<00:04:56.240> a<00:04:56.600> website<00:04:56.960> or<00:04:57.120> a<00:04:57.280> platform 00:04:57.790 --> 00:04:57.800 align:start position:0% it whenever a website or a platform 00:04:57.800 --> 00:05:00.990 align:start position:0% it whenever a website or a platform queries<00:04:58.560> and<00:04:58.680> I<00:04:58.880> respond<00:04:59.240> to<00:04:59.400> that 00:05:00.990 --> 00:05:01.000 align:start position:0% queries and I respond to that 00:05:01.000 --> 00:05:02.710 align:start position:0% queries and I respond to that the<00:05:01.120> other<00:05:01.280> one<00:05:01.600> yeah<00:05:01.840> technically<00:05:02.240> this<00:05:02.400> mean 00:05:02.710 --> 00:05:02.720 align:start position:0% the other one yeah technically this mean 00:05:02.720 --> 00:05:06.070 align:start position:0% the other one yeah technically this mean Wason<00:05:03.160> mobile<00:05:03.520> proving<00:05:04.240> small<00:05:04.639> Ram<00:05:05.160> uh<00:05:05.320> memory 00:05:06.070 --> 00:05:06.080 align:start position:0% Wason mobile proving small Ram uh memory 00:05:06.080 --> 00:05:07.990 align:start position:0% Wason mobile proving small Ram uh memory uh<00:05:06.320> Resort<00:05:06.759> like<00:05:06.919> low<00:05:07.120> bandwidth 00:05:07.990 --> 00:05:08.000 align:start position:0% uh Resort like low bandwidth 00:05:08.000 --> 00:05:10.270 align:start position:0% uh Resort like low bandwidth environments<00:05:09.000> uh<00:05:09.120> that<00:05:09.240> means<00:05:09.639> leveraging 00:05:10.270 --> 00:05:10.280 align:start position:0% environments uh that means leveraging 00:05:10.280 --> 00:05:11.749 align:start position:0% environments uh that means leveraging techniques<00:05:10.759> like<00:05:10.960> proof<00:05:11.240> aggregation 00:05:11.749 --> 00:05:11.759 align:start position:0% techniques like proof aggregation 00:05:11.759 --> 00:05:13.909 align:start position:0% techniques like proof aggregation recursion<00:05:12.280> folding<00:05:13.000> different<00:05:13.240> verification 00:05:13.909 --> 00:05:13.919 align:start position:0% recursion folding different verification 00:05:13.919 --> 00:05:16.390 align:start position:0% recursion folding different verification layers<00:05:14.919> things<00:05:15.280> exploring<00:05:15.720> things<00:05:15.919> like<00:05:16.080> Co 00:05:16.390 --> 00:05:16.400 align:start position:0% layers things exploring things like Co 00:05:16.400 --> 00:05:18.230 align:start position:0% layers things exploring things like Co Nars<00:05:16.759> in<00:05:16.840> order<00:05:17.039> to<00:05:17.160> do<00:05:17.360> delegate<00:05:17.800> proving 00:05:18.230 --> 00:05:18.240 align:start position:0% Nars in order to do delegate proving 00:05:18.240 --> 00:05:20.390 align:start position:0% Nars in order to do delegate proving exploring<00:05:18.720> things<00:05:18.960> like<00:05:19.280> proof<00:05:19.639> composition 00:05:20.390 --> 00:05:20.400 align:start position:0% exploring things like proof composition 00:05:20.400 --> 00:05:22.550 align:start position:0% exploring things like proof composition like<00:05:21.319> I<00:05:21.400> don't<00:05:21.520> know<00:05:21.680> client<00:05:22.039> side<00:05:22.199> proving 00:05:22.550 --> 00:05:22.560 align:start position:0% like I don't know client side proving 00:05:22.560 --> 00:05:23.870 align:start position:0% like I don't know client side proving with<00:05:22.759> with<00:05:22.919> one<00:05:23.160> proving<00:05:23.440> system<00:05:23.759> like 00:05:23.870 --> 00:05:23.880 align:start position:0% with with one proving system like 00:05:23.880 --> 00:05:27.350 align:start position:0% with with one proving system like sparton<00:05:24.520> then<00:05:24.720> aggregating<00:05:25.240> on<00:05:25.400> a<00:05:26.199> ckvm<00:05:27.199> and 00:05:27.350 --> 00:05:27.360 align:start position:0% sparton then aggregating on a ckvm and 00:05:27.360 --> 00:05:29.070 align:start position:0% sparton then aggregating on a ckvm and then<00:05:27.520> like<00:05:27.639> proving<00:05:27.960> unchain<00:05:28.360> with<00:05:28.479> gr<00:05:28.720> 16 00:05:29.070 --> 00:05:29.080 align:start position:0% then like proving unchain with gr 16 00:05:29.080 --> 00:05:30.309 align:start position:0% then like proving unchain with gr 16 those<00:05:29.199> are<00:05:29.319> kind<00:05:29.400> of<00:05:29.520> like<00:05:29.759> the<00:05:29.919> solutions 00:05:30.309 --> 00:05:30.319 align:start position:0% those are kind of like the solutions 00:05:30.319 --> 00:05:31.430 align:start position:0% those are kind of like the solutions that<00:05:30.400> we're<00:05:30.560> seeing<00:05:30.880> because<00:05:31.039> we<00:05:31.160> want<00:05:31.240> to 00:05:31.430 --> 00:05:31.440 align:start position:0% that we're seeing because we want to 00:05:31.440 --> 00:05:35.469 align:start position:0% that we're seeing because we want to have<00:05:32.000> cheap<00:05:32.600> fast<00:05:33.080> composable<00:05:33.720> proofs<00:05:34.440> of<00:05:34.680> our 00:05:35.469 --> 00:05:35.479 align:start position:0% have cheap fast composable proofs of our 00:05:35.479 --> 00:05:38.790 align:start position:0% have cheap fast composable proofs of our data<00:05:36.479> and<00:05:36.680> lastly<00:05:37.080> we<00:05:37.160> want<00:05:37.280> to<00:05:38.199> basically<00:05:38.520> do 00:05:38.790 --> 00:05:38.800 align:start position:0% data and lastly we want to basically do 00:05:38.800 --> 00:05:40.790 align:start position:0% data and lastly we want to basically do very<00:05:39.000> useful<00:05:39.440> actions<00:05:39.720> with<00:05:39.919> that<00:05:40.440> and<00:05:40.680> the 00:05:40.790 --> 00:05:40.800 align:start position:0% very useful actions with that and the 00:05:40.800 --> 00:05:42.950 align:start position:0% very useful actions with that and the most<00:05:41.000> obvious<00:05:41.360> candidates<00:05:41.759> are<00:05:42.080> voting 00:05:42.950 --> 00:05:42.960 align:start position:0% most obvious candidates are voting 00:05:42.960 --> 00:05:46.430 align:start position:0% most obvious candidates are voting forums<00:05:43.880> chats<00:05:44.880> um<00:05:45.160> Etc<00:05:45.880> but<00:05:46.000> there<00:05:46.080> are<00:05:46.240> things 00:05:46.430 --> 00:05:46.440 align:start position:0% forums chats um Etc but there are things 00:05:46.440 --> 00:05:47.870 align:start position:0% forums chats um Etc but there are things that<00:05:46.560> are<00:05:46.720> popping<00:05:47.000> up<00:05:47.199> like<00:05:47.440> yeah<00:05:47.600> data 00:05:47.870 --> 00:05:47.880 align:start position:0% that are popping up like yeah data 00:05:47.880 --> 00:05:50.150 align:start position:0% that are popping up like yeah data syndicates<00:05:48.360> or<00:05:48.600> data<00:05:48.800> marketplaces<00:05:49.600> where<00:05:50.080> a 00:05:50.150 --> 00:05:50.160 align:start position:0% syndicates or data marketplaces where a 00:05:50.160 --> 00:05:52.710 align:start position:0% syndicates or data marketplaces where a lot<00:05:50.319> of<00:05:50.440> people<00:05:50.720> can<00:05:50.919> just<00:05:51.520> add<00:05:51.720> up<00:05:51.960> their<00:05:52.199> data 00:05:52.710 --> 00:05:52.720 align:start position:0% lot of people can just add up their data 00:05:52.720 --> 00:05:55.909 align:start position:0% lot of people can just add up their data and<00:05:52.880> then<00:05:53.280> make<00:05:54.000> um<00:05:54.720> charge<00:05:55.199> basically<00:05:55.560> to<00:05:55.680> do 00:05:55.909 --> 00:05:55.919 align:start position:0% and then make um charge basically to do 00:05:55.919 --> 00:05:57.510 align:start position:0% and then make um charge basically to do statistic<00:05:56.400> analysis<00:05:56.800> on<00:05:57.000> that<00:05:57.199> private 00:05:57.510 --> 00:05:57.520 align:start position:0% statistic analysis on that private 00:05:57.520 --> 00:06:00.189 align:start position:0% statistic analysis on that private anonymized<00:05:58.120> data<00:05:58.880> we<00:05:59.000> can<00:05:59.160> do<00:05:59.639> reimbursements 00:06:00.189 --> 00:06:00.199 align:start position:0% anonymized data we can do reimbursements 00:06:00.199 --> 00:06:04.270 align:start position:0% anonymized data we can do reimbursements compliance<00:06:00.720> stuff<00:06:01.280> uh<00:06:01.400> a<00:06:01.520> lot<00:06:01.639> of<00:06:02.039> ux<00:06:02.919> on<00:06:03.199> web<00:06:03.600> 3 00:06:04.270 --> 00:06:04.280 align:start position:0% compliance stuff uh a lot of ux on web 3 00:06:04.280 --> 00:06:06.070 align:start position:0% compliance stuff uh a lot of ux on web 3 like<00:06:04.479> multi6<00:06:05.080> account<00:06:05.400> recovery<00:06:05.759> social 00:06:06.070 --> 00:06:06.080 align:start position:0% like multi6 account recovery social 00:06:06.080 --> 00:06:08.909 align:start position:0% like multi6 account recovery social recovery<00:06:06.680> are<00:06:07.080> needed<00:06:07.720> like<00:06:07.880> need<00:06:08.440> identity 00:06:08.909 --> 00:06:08.919 align:start position:0% recovery are needed like need identity 00:06:08.919 --> 00:06:11.029 align:start position:0% recovery are needed like need identity so<00:06:09.080> I<00:06:09.160> think<00:06:09.360> that's<00:06:09.560> where<00:06:10.240> our<00:06:10.520> Solutions<00:06:10.919> in 00:06:11.029 --> 00:06:11.039 align:start position:0% so I think that's where our Solutions in 00:06:11.039 --> 00:06:12.390 align:start position:0% so I think that's where our Solutions in this<00:06:11.199> space<00:06:11.440> are<00:06:11.520> going<00:06:11.639> to<00:06:11.759> be<00:06:11.960> extremely 00:06:12.390 --> 00:06:12.400 align:start position:0% this space are going to be extremely 00:06:12.400 --> 00:06:15.990 align:start position:0% this space are going to be extremely important<00:06:12.800> humanitarian<00:06:13.639> cases<00:06:14.360> anti-il 00:06:15.990 --> 00:06:16.000 align:start position:0% important humanitarian cases anti-il 00:06:16.000 --> 00:06:18.790 align:start position:0% important humanitarian cases anti-il Etc<00:06:17.000> so<00:06:17.599> yeah<00:06:17.880> basically<00:06:18.240> we<00:06:18.319> need<00:06:18.440> to<00:06:18.560> be<00:06:18.639> able 00:06:18.790 --> 00:06:18.800 align:start position:0% Etc so yeah basically we need to be able 00:06:18.800 --> 00:06:20.670 align:start position:0% Etc so yeah basically we need to be able to<00:06:18.919> do<00:06:19.120> useful<00:06:19.560> actions<00:06:19.960> and<00:06:20.080> one<00:06:20.199> of<00:06:20.360> the 00:06:20.670 --> 00:06:20.680 align:start position:0% to do useful actions and one of the 00:06:20.680 --> 00:06:22.950 align:start position:0% to do useful actions and one of the biggest<00:06:21.560> I'll<00:06:21.800> say<00:06:22.240> challenges<00:06:22.680> is<00:06:22.800> like 00:06:22.950 --> 00:06:22.960 align:start position:0% biggest I'll say challenges is like 00:06:22.960 --> 00:06:25.230 align:start position:0% biggest I'll say challenges is like nullifiers<00:06:23.880> and<00:06:24.000> the<00:06:24.120> Nar<00:06:24.639> is<00:06:24.720> like<00:06:24.800> a<00:06:25.000> strong 00:06:25.230 --> 00:06:25.240 align:start position:0% nullifiers and the Nar is like a strong 00:06:25.240 --> 00:06:28.510 align:start position:0% nullifiers and the Nar is like a strong problem<00:06:25.960> I<00:06:26.080> just<00:06:26.280> listed<00:06:27.160> um<00:06:28.160> different 00:06:28.510 --> 00:06:28.520 align:start position:0% problem I just listed um different 00:06:28.520 --> 00:06:29.950 align:start position:0% problem I just listed um different approaches<00:06:28.919> and<00:06:29.080> levels<00:06:29.360> of<00:06:29.560> like<00:06:29.680> nullif 00:06:29.950 --> 00:06:29.960 align:start position:0% approaches and levels of like nullif 00:06:29.960 --> 00:06:31.110 align:start position:0% approaches and levels of like nullif fire<00:06:30.120> is<00:06:30.199> where<00:06:30.360> the<00:06:30.479> government<00:06:30.840> basically 00:06:31.110 --> 00:06:31.120 align:start position:0% fire is where the government basically 00:06:31.120 --> 00:06:33.150 align:start position:0% fire is where the government basically no<00:06:31.280> nullifier<00:06:31.960> that's<00:06:32.120> the<00:06:32.240> worst<00:06:32.479> case<00:06:32.720> and 00:06:33.150 --> 00:06:33.160 align:start position:0% no nullifier that's the worst case and 00:06:33.160 --> 00:06:34.950 align:start position:0% no nullifier that's the worst case and best<00:06:33.440> case<00:06:33.599> is<00:06:33.800> like<00:06:34.199> yeah<00:06:34.360> not<00:06:34.560> even<00:06:34.800> the 00:06:34.950 --> 00:06:34.960 align:start position:0% best case is like yeah not even the 00:06:34.960 --> 00:06:36.430 align:start position:0% best case is like yeah not even the government<00:06:35.360> trying<00:06:35.599> to<00:06:35.800> collude<00:06:36.160> will<00:06:36.319> be 00:06:36.430 --> 00:06:36.440 align:start position:0% government trying to collude will be 00:06:36.440 --> 00:06:38.430 align:start position:0% government trying to collude will be able<00:06:36.599> to<00:06:36.919> you<00:06:37.000> know<00:06:37.560> see<00:06:37.800> that<00:06:37.919> you<00:06:38.039> sign<00:06:38.280> up 00:06:38.430 --> 00:06:38.440 align:start position:0% able to you know see that you sign up 00:06:38.440 --> 00:06:41.790 align:start position:0% able to you know see that you sign up for<00:06:38.639> a<00:06:39.039> really<00:06:39.960> controversial<00:06:40.840> uh 00:06:41.790 --> 00:06:41.800 align:start position:0% for a really controversial uh 00:06:41.800 --> 00:06:45.230 align:start position:0% for a really controversial uh service<00:06:42.800> so<00:06:43.000> yeah<00:06:43.360> for<00:06:44.000> last<00:06:44.240> things<00:06:44.680> uh<00:06:45.120> this 00:06:45.230 --> 00:06:45.240 align:start position:0% service so yeah for last things uh this 00:06:45.240 --> 00:06:46.909 align:start position:0% service so yeah for last things uh this needs<00:06:45.440> to<00:06:45.560> be<00:06:45.720> secure<00:06:46.039> post<00:06:46.280> Quantum<00:06:46.639> is<00:06:46.759> like 00:06:46.909 --> 00:06:46.919 align:start position:0% needs to be secure post Quantum is like 00:06:46.919 --> 00:06:48.790 align:start position:0% needs to be secure post Quantum is like a<00:06:47.039> must<00:06:47.400> have<00:06:47.599> now<00:06:48.000> because<00:06:48.240> like<00:06:48.360> in<00:06:48.560> five 00:06:48.790 --> 00:06:48.800 align:start position:0% a must have now because like in five 00:06:48.800 --> 00:06:50.990 align:start position:0% a must have now because like in five years<00:06:49.080> you're<00:06:49.319> doing<00:06:49.599> voting<00:06:50.000> and<00:06:50.520> it<00:06:50.680> gets 00:06:50.990 --> 00:06:51.000 align:start position:0% years you're doing voting and it gets 00:06:51.000 --> 00:06:53.710 align:start position:0% years you're doing voting and it gets like<00:06:51.680> uh<00:06:51.880> captured<00:06:52.280> the<00:06:52.440> data<00:06:52.680> and<00:06:52.840> then<00:06:53.319> uh 00:06:53.710 --> 00:06:53.720 align:start position:0% like uh captured the data and then uh 00:06:53.720 --> 00:06:55.670 align:start position:0% like uh captured the data and then uh decrypted<00:06:54.479> later<00:06:55.000> it<00:06:55.080> could<00:06:55.240> be<00:06:55.319> a<00:06:55.479> problem 00:06:55.670 --> 00:06:55.680 align:start position:0% decrypted later it could be a problem 00:06:55.680 --> 00:06:57.430 align:start position:0% decrypted later it could be a problem for<00:06:55.800> you<00:06:55.960> it<00:06:56.039> needs<00:06:56.199> to<00:06:56.319> be<00:06:56.440> interoperable<00:06:57.240> no 00:06:57.430 --> 00:06:57.440 align:start position:0% for you it needs to be interoperable no 00:06:57.440 --> 00:06:59.270 align:start position:0% for you it needs to be interoperable no Bender<00:06:57.800> lock<00:06:58.039> in<00:06:58.440> it<00:06:58.560> needs<00:06:58.720> to<00:06:58.800> be<00:06:58.919> movable 00:06:59.270 --> 00:06:59.280 align:start position:0% Bender lock in it needs to be movable 00:06:59.280 --> 00:07:00.869 align:start position:0% Bender lock in it needs to be movable from<00:06:59.560> wallet<00:06:59.759> to<00:06:59.919> wallet<00:07:00.400> it<00:07:00.520> needs<00:07:00.720> to 00:07:00.869 --> 00:07:00.879 align:start position:0% from wallet to wallet it needs to 00:07:00.879 --> 00:07:03.189 align:start position:0% from wallet to wallet it needs to support<00:07:01.280> key<00:07:01.520> rotations<00:07:02.039> live<00:07:02.400> checks<00:07:02.840> etc 00:07:03.189 --> 00:07:03.199 align:start position:0% support key rotations live checks etc 00:07:03.199 --> 00:07:04.990 align:start position:0% support key rotations live checks etc etc<00:07:03.680> so<00:07:03.840> these<00:07:03.960> are<00:07:04.120> some<00:07:04.400> properties<00:07:04.800> that<00:07:04.879> we 00:07:04.990 --> 00:07:05.000 align:start position:0% etc so these are some properties that we 00:07:05.000 --> 00:07:06.950 align:start position:0% etc so these are some properties that we want<00:07:05.120> to<00:07:05.319> achieve<00:07:05.879> and<00:07:06.120> I<00:07:06.199> think<00:07:06.400> we<00:07:06.599> all<00:07:06.800> in 00:07:06.950 --> 00:07:06.960 align:start position:0% want to achieve and I think we all in 00:07:06.960 --> 00:07:08.550 align:start position:0% want to achieve and I think we all in this<00:07:07.080> space<00:07:07.319> are<00:07:07.400> trying<00:07:07.680> to<00:07:07.960> actively<00:07:08.319> work 00:07:08.550 --> 00:07:08.560 align:start position:0% this space are trying to actively work 00:07:08.560 --> 00:07:11.270 align:start position:0% this space are trying to actively work on<00:07:09.280> so<00:07:09.479> to<00:07:09.680> finalize<00:07:10.280> I<00:07:10.360> think<00:07:10.680> the<00:07:10.840> three<00:07:11.080> key 00:07:11.270 --> 00:07:11.280 align:start position:0% on so to finalize I think the three key 00:07:11.280 --> 00:07:13.309 align:start position:0% on so to finalize I think the three key messages<00:07:11.720> that<00:07:11.840> I<00:07:11.960> want<00:07:12.120> you<00:07:12.199> to<00:07:12.360> take<00:07:12.639> is<00:07:12.879> like 00:07:13.309 --> 00:07:13.319 align:start position:0% messages that I want you to take is like 00:07:13.319 --> 00:07:15.589 align:start position:0% messages that I want you to take is like first<00:07:13.680> let's<00:07:13.919> hijack<00:07:14.440> everything<00:07:15.039> let's<00:07:15.240> take 00:07:15.589 --> 00:07:15.599 align:start position:0% first let's hijack everything let's take 00:07:15.599 --> 00:07:17.909 align:start position:0% first let's hijack everything let's take all<00:07:15.800> the<00:07:16.000> data<00:07:16.360> of<00:07:16.639> identity<00:07:17.080> sources<00:07:17.400> and<00:07:17.560> da 00:07:17.909 --> 00:07:17.919 align:start position:0% all the data of identity sources and da 00:07:17.919 --> 00:07:20.629 align:start position:0% all the data of identity sources and da sources<00:07:18.240> and<00:07:18.400> try<00:07:18.520> to<00:07:18.680> Bing<00:07:19.639> um<00:07:19.800> to<00:07:19.960> our<00:07:20.280> use 00:07:20.629 --> 00:07:20.639 align:start position:0% sources and try to Bing um to our use 00:07:20.639 --> 00:07:22.990 align:start position:0% sources and try to Bing um to our use case<00:07:20.800> onchain<00:07:21.319> or<00:07:21.560> offchain<00:07:22.360> let's<00:07:22.560> try<00:07:22.720> to 00:07:22.990 --> 00:07:23.000 align:start position:0% case onchain or offchain let's try to 00:07:23.000 --> 00:07:24.790 align:start position:0% case onchain or offchain let's try to discover<00:07:23.199> novel<00:07:23.599> use<00:07:23.919> cases<00:07:24.280> like<00:07:24.440> different 00:07:24.790 --> 00:07:24.800 align:start position:0% discover novel use cases like different 00:07:24.800 --> 00:07:26.469 align:start position:0% discover novel use cases like different interactions<00:07:25.360> that<00:07:25.479> we<00:07:25.560> can<00:07:25.720> unlock<00:07:26.319> with 00:07:26.469 --> 00:07:26.479 align:start position:0% interactions that we can unlock with 00:07:26.479 --> 00:07:29.749 align:start position:0% interactions that we can unlock with this<00:07:26.840> new<00:07:27.120> data<00:07:27.639> Providence<00:07:28.639> um<00:07:28.919> things<00:07:29.560> and 00:07:29.749 --> 00:07:29.759 align:start position:0% this new data Providence um things and 00:07:29.759 --> 00:07:32.589 align:start position:0% this new data Providence um things and now<00:07:29.960> let's<00:07:30.199> build<00:07:30.639> uh<00:07:31.000> new<00:07:31.240> Lego<00:07:31.599> blocks<00:07:32.280> to 00:07:32.589 --> 00:07:32.599 align:start position:0% now let's build uh new Lego blocks to 00:07:32.599 --> 00:07:35.430 align:start position:0% now let's build uh new Lego blocks to build<00:07:32.840> a<00:07:32.960> better<00:07:33.199> future 00:07:35.430 --> 00:07:35.440 align:start position:0% build a better future 00:07:35.440 --> 00:07:37.150 align:start position:0% build a better future thanks<00:07:36.440> thank<00:07:36.639> you 00:07:37.150 --> 00:07:37.160 align:start position:0% thanks thank you 00:07:37.160 --> 00:07:38.550 align:start position:0% thanks thank you [Music] 00:07:38.550 --> 00:07:38.560 align:start position:0% [Music] 00:07:38.560 --> 00:07:42.629 align:start position:0% [Music] Andy<00:07:39.560> there's<00:07:39.759> a<00:07:40.000> question 00:07:42.629 --> 00:07:42.639 align:start position:0% Andy there's a question 00:07:42.639 --> 00:07:45.749 align:start position:0% Andy there's a question there<00:07:43.639> oh<00:07:43.840> I<00:07:43.960> did<00:07:44.199> pretty<00:07:44.400> well<00:07:44.639> thank<00:07:44.840> you 00:07:45.749 --> 00:07:45.759 align:start position:0% there oh I did pretty well thank you 00:07:45.759 --> 00:07:47.510 align:start position:0% there oh I did pretty well thank you good<00:07:45.960> throw 00:07:47.510 --> 00:07:47.520 align:start position:0% good throw 00:07:47.520 --> 00:07:51.309 align:start position:0% good throw yeah<00:07:48.520> um<00:07:49.039> so<00:07:49.360> question<00:07:50.080> um<00:07:50.639> great<00:07:51.039> great<00:07:51.199> to 00:07:51.309 --> 00:07:51.319 align:start position:0% yeah um so question um great great to 00:07:51.319 --> 00:07:53.309 align:start position:0% yeah um so question um great great to see<00:07:51.479> the<00:07:51.639> product<00:07:52.000> perspective<00:07:52.440> for<00:07:52.680> once<00:07:53.159> and 00:07:53.309 --> 00:07:53.319 align:start position:0% see the product perspective for once and 00:07:53.319 --> 00:07:56.070 align:start position:0% see the product perspective for once and I<00:07:53.560> really<00:07:53.759> like<00:07:54.039> the<00:07:54.479> three<00:07:55.319> three<00:07:55.680> stage 00:07:56.070 --> 00:07:56.080 align:start position:0% I really like the three three stage 00:07:56.080 --> 00:07:58.990 align:start position:0% I really like the three three stage components<00:07:57.000> and<00:07:58.000> um<00:07:58.280> product<00:07:58.599> deals<00:07:58.840> with 00:07:58.990 --> 00:07:59.000 align:start position:0% components and um product deals with 00:07:59.000 --> 00:08:01.990 align:start position:0% components and um product deals with human<00:07:59.240> nature<00:07:59.840> right<00:08:00.360> so<00:08:01.360> human<00:08:01.639> nature 00:08:01.990 --> 00:08:02.000 align:start position:0% human nature right so human nature 00:08:02.000 --> 00:08:04.550 align:start position:0% human nature right so human nature usually<00:08:02.280> runs<00:08:02.520> on<00:08:02.720> incentives<00:08:03.720> so<00:08:04.159> if<00:08:04.240> I<00:08:04.440> give 00:08:04.550 --> 00:08:04.560 align:start position:0% usually runs on incentives so if I give 00:08:04.560 --> 00:08:05.710 align:start position:0% usually runs on incentives so if I give an<00:08:04.720> example<00:08:05.000> for<00:08:05.159> the<00:08:05.280> government<00:08:05.639> the 00:08:05.710 --> 00:08:05.720 align:start position:0% an example for the government the 00:08:05.720 --> 00:08:08.149 align:start position:0% an example for the government the government<00:08:06.080> gives<00:08:06.479> you<00:08:07.479> the<00:08:07.599> right<00:08:07.759> to<00:08:07.879> drive 00:08:08.149 --> 00:08:08.159 align:start position:0% government gives you the right to drive 00:08:08.159 --> 00:08:10.629 align:start position:0% government gives you the right to drive a<00:08:08.319> car<00:08:09.199> so<00:08:09.360> you<00:08:09.479> have<00:08:09.639> to<00:08:09.800> get<00:08:10.039> a<00:08:10.199> driver 00:08:10.629 --> 00:08:10.639 align:start position:0% a car so you have to get a driver 00:08:10.639 --> 00:08:12.309 align:start position:0% a car so you have to get a driver license<00:08:11.240> therefore<00:08:11.560> you<00:08:11.680> have<00:08:11.800> to<00:08:11.960> get<00:08:12.120> an 00:08:12.309 --> 00:08:12.319 align:start position:0% license therefore you have to get an 00:08:12.319 --> 00:08:14.589 align:start position:0% license therefore you have to get an identity<00:08:13.240> yes<00:08:13.599> so<00:08:13.759> it<00:08:13.879> usually<00:08:14.240> goes 00:08:14.589 --> 00:08:14.599 align:start position:0% identity yes so it usually goes 00:08:14.599 --> 00:08:17.309 align:start position:0% identity yes so it usually goes backwards<00:08:15.080> right<00:08:15.240> from<00:08:15.479> 3<00:08:15.639> to<00:08:15.879> one<00:08:16.879> so<00:08:17.080> I<00:08:17.159> was 00:08:17.309 --> 00:08:17.319 align:start position:0% backwards right from 3 to one so I was 00:08:17.319 --> 00:08:19.029 align:start position:0% backwards right from 3 to one so I was wondering<00:08:17.720> what<00:08:17.840> are<00:08:18.039> the<00:08:18.319> cases<00:08:18.680> that<00:08:18.840> you've 00:08:19.029 --> 00:08:19.039 align:start position:0% wondering what are the cases that you've 00:08:19.039 --> 00:08:22.390 align:start position:0% wondering what are the cases that you've seen<00:08:19.319> that<00:08:19.520> the<00:08:19.759> incentive<00:08:20.759> is<00:08:20.919> so<00:08:21.240> big<00:08:22.240> that 00:08:22.390 --> 00:08:22.400 align:start position:0% seen that the incentive is so big that 00:08:22.400 --> 00:08:25.909 align:start position:0% seen that the incentive is so big that you<00:08:22.520> would<00:08:22.759> then<00:08:23.080> go<00:08:23.639> and<00:08:23.840> find<00:08:24.199> an<00:08:24.400> identity 00:08:25.909 --> 00:08:25.919 align:start position:0% you would then go and find an identity 00:08:25.919 --> 00:08:28.990 align:start position:0% you would then go and find an identity Source<00:08:26.919> um<00:08:27.479> because<00:08:27.720> if<00:08:27.840> you<00:08:27.960> want<00:08:28.159> to<00:08:28.680> use 00:08:28.990 --> 00:08:29.000 align:start position:0% Source um because if you want to use 00:08:29.000 --> 00:08:31.830 align:start position:0% Source um because if you want to use this<00:08:29.159> as<00:08:29.280> a<00:08:29.680> uh<00:08:30.280> as<00:08:30.440> an<00:08:30.599> actual<00:08:30.960> identity<00:08:31.680> that 00:08:31.830 --> 00:08:31.840 align:start position:0% this as a uh as an actual identity that 00:08:31.840 --> 00:08:34.550 align:start position:0% this as a uh as an actual identity that people<00:08:32.120> use<00:08:32.919> they<00:08:33.120> usually<00:08:33.440> don't<00:08:33.719> start<00:08:34.120> with 00:08:34.550 --> 00:08:34.560 align:start position:0% people use they usually don't start with 00:08:34.560 --> 00:08:36.909 align:start position:0% people use they usually don't start with wow<00:08:34.800> this<00:08:34.919> is<00:08:35.039> so<00:08:35.399> private<00:08:35.839> and<00:08:36.159> has<00:08:36.440> like 00:08:36.909 --> 00:08:36.919 align:start position:0% wow this is so private and has like 00:08:36.919 --> 00:08:38.550 align:start position:0% wow this is so private and has like encrypted<00:08:37.479> proof<00:08:37.800> and<00:08:38.000> hashes<00:08:38.360> and 00:08:38.550 --> 00:08:38.560 align:start position:0% encrypted proof and hashes and 00:08:38.560 --> 00:08:41.029 align:start position:0% encrypted proof and hashes and everything<00:08:39.200> yeah<00:08:40.039> so<00:08:40.240> I<00:08:40.279> was<00:08:40.440> wondering<00:08:40.839> what 00:08:41.029 --> 00:08:41.039 align:start position:0% everything yeah so I was wondering what 00:08:41.039 --> 00:08:44.949 align:start position:0% everything yeah so I was wondering what what<00:08:41.159> do<00:08:41.240> you<00:08:41.360> see<00:08:41.760> that<00:08:42.760> uh<00:08:43.760> that<00:08:44.320> has<00:08:44.600> kind<00:08:44.720> of 00:08:44.949 --> 00:08:44.959 align:start position:0% what do you see that uh that has kind of 00:08:44.959 --> 00:08:48.030 align:start position:0% what do you see that uh that has kind of grass<00:08:45.240> roots<00:08:45.640> in<00:08:45.880> in<00:08:46.080> in<00:08:46.279> reality<00:08:46.880> when<00:08:47.640> can<00:08:47.839> it 00:08:48.030 --> 00:08:48.040 align:start position:0% grass roots in in in reality when can it 00:08:48.040 --> 00:08:50.350 align:start position:0% grass roots in in in reality when can it can<00:08:48.160> really<00:08:48.399> brings<00:08:48.839> the<00:08:49.000> masses<00:08:49.560> back<00:08:49.880> to<00:08:50.120> the 00:08:50.350 --> 00:08:50.360 align:start position:0% can really brings the masses back to the 00:08:50.360 --> 00:08:52.310 align:start position:0% can really brings the masses back to the to<00:08:50.480> the<00:08:50.640> platform<00:08:51.200> to<00:08:51.399> platforms<00:08:51.800> like<00:08:52.000> this 00:08:52.310 --> 00:08:52.320 align:start position:0% to the platform to platforms like this 00:08:52.320 --> 00:08:53.389 align:start position:0% to the platform to platforms like this okay<00:08:52.480> I<00:08:52.560> think<00:08:52.680> that's<00:08:52.800> a<00:08:52.920> great<00:08:53.160> question 00:08:53.389 --> 00:08:53.399 align:start position:0% okay I think that's a great question 00:08:53.399 --> 00:08:54.990 align:start position:0% okay I think that's a great question what<00:08:53.519> I<00:08:53.640> understood<00:08:54.000> is<00:08:54.160> like<00:08:54.320> what<00:08:54.399> are 00:08:54.990 --> 00:08:55.000 align:start position:0% what I understood is like what are 00:08:55.000 --> 00:08:56.430 align:start position:0% what I understood is like what are places<00:08:55.320> where<00:08:55.440> we<00:08:55.560> will<00:08:55.720> search<00:08:56.000> for 00:08:56.430 --> 00:08:56.440 align:start position:0% places where we will search for 00:08:56.440 --> 00:08:57.990 align:start position:0% places where we will search for identities<00:08:56.920> or<00:08:57.160> data<00:08:57.480> where<00:08:57.640> people<00:08:57.839> are 00:08:57.990 --> 00:08:58.000 align:start position:0% identities or data where people are 00:08:58.000 --> 00:09:00.310 align:start position:0% identities or data where people are already<00:08:58.399> there<00:08:58.640> I<00:08:58.720> would<00:08:58.839> say<00:08:59.040> like<00:08:59.240> yeah 00:09:00.310 --> 00:09:00.320 align:start position:0% already there I would say like yeah 00:09:00.320 --> 00:09:02.350 align:start position:0% already there I would say like yeah I<00:09:00.399> will<00:09:00.600> start<00:09:00.880> with<00:09:01.240> where<00:09:01.440> are<00:09:01.680> people<00:09:02.040> there 00:09:02.350 --> 00:09:02.360 align:start position:0% I will start with where are people there 00:09:02.360 --> 00:09:04.509 align:start position:0% I will start with where are people there like<00:09:02.519> it's<00:09:02.720> very<00:09:02.959> hard<00:09:03.160> for<00:09:03.480> us<00:09:03.760> to<00:09:04.000> request<00:09:04.360> to 00:09:04.509 --> 00:09:04.519 align:start position:0% like it's very hard for us to request to 00:09:04.519 --> 00:09:06.310 align:start position:0% like it's very hard for us to request to everyone<00:09:04.800> to<00:09:04.959> sign<00:09:05.200> up<00:09:05.320> to<00:09:05.480> a<00:09:05.640> system<00:09:06.120> but<00:09:06.240> it 00:09:06.310 --> 00:09:06.320 align:start position:0% everyone to sign up to a system but it 00:09:06.320 --> 00:09:08.030 align:start position:0% everyone to sign up to a system but it will<00:09:06.480> be<00:09:06.720> way<00:09:06.920> better<00:09:07.160> if<00:09:07.320> we<00:09:07.480> just<00:09:07.600> say<00:09:07.839> like 00:09:08.030 --> 00:09:08.040 align:start position:0% will be way better if we just say like 00:09:08.040 --> 00:09:09.509 align:start position:0% will be way better if we just say like yeah<00:09:08.240> all<00:09:08.560> people<00:09:08.760> are<00:09:09.000> interested<00:09:09.360> in 00:09:09.509 --> 00:09:09.519 align:start position:0% yeah all people are interested in 00:09:09.519 --> 00:09:11.710 align:start position:0% yeah all people are interested in driving<00:09:09.800> a<00:09:09.959> car<00:09:10.399> in<00:09:10.600> these<00:09:10.920> locations<00:09:11.519> let's 00:09:11.710 --> 00:09:11.720 align:start position:0% driving a car in these locations let's 00:09:11.720 --> 00:09:13.630 align:start position:0% driving a car in these locations let's just<00:09:11.920> use<00:09:12.120> that<00:09:12.279> as<00:09:12.399> a<00:09:12.560> like<00:09:12.760> source<00:09:13.040> of 00:09:13.630 --> 00:09:13.640 align:start position:0% just use that as a like source of 00:09:13.640 --> 00:09:15.389 align:start position:0% just use that as a like source of starting<00:09:14.079> point<00:09:14.320> to<00:09:14.480> bring<00:09:14.680> their<00:09:14.839> identity 00:09:15.389 --> 00:09:15.399 align:start position:0% starting point to bring their identity 00:09:15.399 --> 00:09:17.110 align:start position:0% starting point to bring their identity on<00:09:15.519> chain<00:09:15.720> and<00:09:15.839> to<00:09:15.959> do<00:09:16.079> actions<00:09:16.560> on<00:09:16.760> chain<00:09:17.000> and 00:09:17.110 --> 00:09:17.120 align:start position:0% on chain and to do actions on chain and 00:09:17.120 --> 00:09:21.910 align:start position:0% on chain and to do actions on chain and to<00:09:17.240> do<00:09:17.480> like<00:09:17.839> voting<00:09:18.360> and<00:09:18.560> etc<00:09:19.000> etc<00:09:20.480> um<00:09:21.480> so<00:09:21.720> yeah 00:09:21.910 --> 00:09:21.920 align:start position:0% to do like voting and etc etc um so yeah 00:09:21.920 --> 00:09:24.430 align:start position:0% to do like voting and etc etc um so yeah like<00:09:22.760> I<00:09:22.839> don't<00:09:22.959> know<00:09:23.240> like<00:09:23.560> anything<00:09:24.160> that 00:09:24.430 --> 00:09:24.440 align:start position:0% like I don't know like anything that 00:09:24.440 --> 00:09:25.790 align:start position:0% like I don't know like anything that that<00:09:24.519> you<00:09:24.640> sign<00:09:24.880> up<00:09:25.079> that<00:09:25.240> has<00:09:25.360> a<00:09:25.480> digital 00:09:25.790 --> 00:09:25.800 align:start position:0% that you sign up that has a digital 00:09:25.800 --> 00:09:27.230 align:start position:0% that you sign up that has a digital signature<00:09:26.240> I<00:09:26.320> think<00:09:26.440> it<00:09:26.519> would<00:09:26.640> be<00:09:26.839> great<00:09:27.040> to 00:09:27.230 --> 00:09:27.240 align:start position:0% signature I think it would be great to 00:09:27.240 --> 00:09:29.550 align:start position:0% signature I think it would be great to just<00:09:27.640> hijack<00:09:28.040> it<00:09:28.279> and<00:09:28.480> the<00:09:28.600> more<00:09:28.920> people<00:09:29.440> use 00:09:29.550 --> 00:09:29.560 align:start position:0% just hijack it and the more people use 00:09:29.560 --> 00:09:31.509 align:start position:0% just hijack it and the more people use it<00:09:29.680> the<00:09:29.800> more<00:09:30.040> common<00:09:30.360> they<00:09:30.480> are<00:09:31.200> the<00:09:31.320> more 00:09:31.509 --> 00:09:31.519 align:start position:0% it the more common they are the more 00:09:31.519 --> 00:09:33.910 align:start position:0% it the more common they are the more used<00:09:31.800> to<00:09:32.040> they<00:09:32.160> are<00:09:32.440> like<00:09:32.760> face<00:09:33.000> ID<00:09:33.360> Touch<00:09:33.600> ID 00:09:33.910 --> 00:09:33.920 align:start position:0% used to they are like face ID Touch ID 00:09:33.920 --> 00:09:35.350 align:start position:0% used to they are like face ID Touch ID all<00:09:34.320> these<00:09:34.480> secure<00:09:34.760> enclaves<00:09:35.200> I<00:09:35.279> think 00:09:35.350 --> 00:09:35.360 align:start position:0% all these secure enclaves I think 00:09:35.360 --> 00:09:39.509 align:start position:0% all these secure enclaves I think they're<00:09:35.640> great<00:09:36.000> to<00:09:36.320> to<00:09:36.600> to<00:09:36.760> start<00:09:36.959> to<00:09:37.120> do 00:09:39.509 --> 00:09:39.519 align:start position:0% 00:09:39.519 --> 00:09:43.310 align:start position:0% that<00:09:40.519> just<00:09:40.720> just<00:09:40.839> to<00:09:40.959> follow<00:09:41.240> on<00:09:41.560> that 00:09:43.310 --> 00:09:43.320 align:start position:0% that just just to follow on that 00:09:43.320 --> 00:09:46.509 align:start position:0% that just just to follow on that um<00:09:44.320> like<00:09:44.600> the<00:09:44.720> way<00:09:44.880> I<00:09:45.040> approach<00:09:45.440> it<00:09:45.760> just<00:09:46.320> uh 00:09:46.509 --> 00:09:46.519 align:start position:0% um like the way I approach it just uh 00:09:46.519 --> 00:09:48.230 align:start position:0% um like the way I approach it just uh just<00:09:46.640> to<00:09:46.800> say<00:09:46.959> it<00:09:47.040> in<00:09:47.160> a<00:09:47.279> couple<00:09:47.600> words<00:09:47.959> we<00:09:48.120> we 00:09:48.230 --> 00:09:48.240 align:start position:0% just to say it in a couple words we we 00:09:48.240 --> 00:09:51.389 align:start position:0% just to say it in a couple words we we have<00:09:48.320> a<00:09:48.440> company<00:09:48.760> called<00:09:49.000> Grappa<00:09:50.000> and<00:09:51.000> um<00:09:51.279> we 00:09:51.389 --> 00:09:51.399 align:start position:0% have a company called Grappa and um we 00:09:51.399 --> 00:09:53.550 align:start position:0% have a company called Grappa and um we use<00:09:51.680> reputation<00:09:52.320> basically<00:09:52.760> so<00:09:52.920> we're<00:09:53.079> saying 00:09:53.550 --> 00:09:53.560 align:start position:0% use reputation basically so we're saying 00:09:53.560 --> 00:09:55.790 align:start position:0% use reputation basically so we're saying you<00:09:53.680> want<00:09:53.839> to<00:09:54.040> prove<00:09:54.279> your<00:09:54.640> reputation<00:09:55.640> going 00:09:55.790 --> 00:09:55.800 align:start position:0% you want to prove your reputation going 00:09:55.800 --> 00:09:57.630 align:start position:0% you want to prove your reputation going to<00:09:55.959> say<00:09:56.160> that<00:09:56.279> you<00:09:56.480> did<00:09:56.720> something<00:09:57.040> in<00:09:57.279> life 00:09:57.630 --> 00:09:57.640 align:start position:0% to say that you did something in life 00:09:57.640 --> 00:10:00.870 align:start position:0% to say that you did something in life you<00:09:57.760> want<00:09:57.959> to<00:09:58.200> have<00:09:58.600> some<00:09:58.839> kind<00:09:59.000> of 00:10:00.870 --> 00:10:00.880 align:start position:0% you want to have some kind of 00:10:00.880 --> 00:10:03.389 align:start position:0% you want to have some kind of um<00:10:01.519> attestation<00:10:02.120> from<00:10:02.360> somebody<00:10:02.800> else<00:10:03.240> that 00:10:03.389 --> 00:10:03.399 align:start position:0% um attestation from somebody else that 00:10:03.399 --> 00:10:05.829 align:start position:0% um attestation from somebody else that you<00:10:03.560> are<00:10:04.240> nor<00:10:04.680> worthy<00:10:05.000> in<00:10:05.200> something<00:10:05.680> that's 00:10:05.829 --> 00:10:05.839 align:start position:0% you are nor worthy in something that's 00:10:05.839 --> 00:10:07.750 align:start position:0% you are nor worthy in something that's usually<00:10:06.160> a<00:10:06.399> start<00:10:06.720> for<00:10:06.880> an<00:10:07.040> identity<00:10:07.560> that 00:10:07.750 --> 00:10:07.760 align:start position:0% usually a start for an identity that 00:10:07.760 --> 00:10:09.269 align:start position:0% usually a start for an identity that usually<00:10:08.160> I<00:10:08.279> want<00:10:08.399> to<00:10:08.560> prove<00:10:08.839> this<00:10:08.959> to<00:10:09.120> the 00:10:09.269 --> 00:10:09.279 align:start position:0% usually I want to prove this to the 00:10:09.279 --> 00:10:12.230 align:start position:0% usually I want to prove this to the world<00:10:10.200> I<00:10:10.360> start<00:10:10.680> with<00:10:10.920> that<00:10:11.600> that<00:10:11.760> starts<00:10:12.120> to 00:10:12.230 --> 00:10:12.240 align:start position:0% world I start with that that starts to 00:10:12.240 --> 00:10:14.350 align:start position:0% world I start with that that starts to be<00:10:12.480> kind<00:10:12.600> of<00:10:12.720> the<00:10:12.839> seed<00:10:13.200> of<00:10:13.320> my<00:10:13.519> identity<00:10:14.200> and 00:10:14.350 --> 00:10:14.360 align:start position:0% be kind of the seed of my identity and 00:10:14.360 --> 00:10:18.350 align:start position:0% be kind of the seed of my identity and then<00:10:14.519> I<00:10:14.640> cannot<00:10:15.000> forgo<00:10:15.560> that<00:10:16.600> yeah<00:10:17.600> right<00:10:18.120> yeah 00:10:18.350 --> 00:10:18.360 align:start position:0% then I cannot forgo that yeah right yeah 00:10:18.360 --> 00:10:21.790 align:start position:0% then I cannot forgo that yeah right yeah no<00:10:18.600> great<00:10:18.839> use<00:10:19.120> case<00:10:19.680> all 00:10:21.790 --> 00:10:21.800 align:start position:0% no great use case all 00:10:21.800 --> 00:10:25.829 align:start position:0% no great use case all right<00:10:22.800> so<00:10:23.079> one<00:10:23.360> question<00:10:23.720> there<00:10:24.360> okay<00:10:25.360> I<00:10:25.560> saw 00:10:25.829 --> 00:10:25.839 align:start position:0% right so one question there okay I saw 00:10:25.839 --> 00:10:28.670 align:start position:0% right so one question there okay I saw on<00:10:26.040> your<00:10:26.279> slide<00:10:26.920> uh<00:10:27.320> verifiable<00:10:28.160> oblivia 00:10:28.670 --> 00:10:28.680 align:start position:0% on your slide uh verifiable oblivia 00:10:28.680 --> 00:10:31.110 align:start position:0% on your slide uh verifiable oblivia pseudo<00:10:29.000> Ren<00:10:29.360> functions<00:10:29.959> yes<00:10:30.279> uh<00:10:30.480> what's<00:10:30.800> the 00:10:31.110 --> 00:10:31.120 align:start position:0% pseudo Ren functions yes uh what's the 00:10:31.120 --> 00:10:33.430 align:start position:0% pseudo Ren functions yes uh what's the uh<00:10:31.560> what<00:10:31.760> where<00:10:31.880> do<00:10:32.000> you<00:10:32.120> see<00:10:32.320> it<00:10:32.480> fitting<00:10:32.800> in 00:10:33.430 --> 00:10:33.440 align:start position:0% uh what where do you see it fitting in 00:10:33.440 --> 00:10:35.269 align:start position:0% uh what where do you see it fitting in yes<00:10:33.720> that's<00:10:33.959> a<00:10:34.200> technique<00:10:34.600> that<00:10:34.800> a<00:10:34.920> couple<00:10:35.160> of 00:10:35.269 --> 00:10:35.279 align:start position:0% yes that's a technique that a couple of 00:10:35.279 --> 00:10:36.590 align:start position:0% yes that's a technique that a couple of teams<00:10:35.600> in<00:10:35.720> the<00:10:35.839> identity<00:10:36.160> space<00:10:36.440> are 00:10:36.590 --> 00:10:36.600 align:start position:0% teams in the identity space are 00:10:36.600 --> 00:10:38.030 align:start position:0% teams in the identity space are exploring<00:10:37.040> I<00:10:37.160> think<00:10:37.320> is<00:10:37.440> great<00:10:37.680> they<00:10:37.800> didn't 00:10:38.030 --> 00:10:38.040 align:start position:0% exploring I think is great they didn't 00:10:38.040 --> 00:10:39.590 align:start position:0% exploring I think is great they didn't get<00:10:38.160> to<00:10:38.320> all<00:10:38.440> the<00:10:38.600> technical<00:10:38.920> details<00:10:39.279> but 00:10:39.590 --> 00:10:39.600 align:start position:0% get to all the technical details but 00:10:39.600 --> 00:10:41.990 align:start position:0% get to all the technical details but basically<00:10:39.920> a<00:10:40.040> network<00:10:40.440> like<00:10:40.560> MPC<00:10:41.079> of<00:10:41.240> nodes 00:10:41.990 --> 00:10:42.000 align:start position:0% basically a network like MPC of nodes 00:10:42.000 --> 00:10:43.509 align:start position:0% basically a network like MPC of nodes and<00:10:42.160> basically<00:10:42.560> how<00:10:42.680> it<00:10:42.839> does<00:10:43.040> is<00:10:43.240> like<00:10:43.360> it 00:10:43.509 --> 00:10:43.519 align:start position:0% and basically how it does is like it 00:10:43.519 --> 00:10:45.750 align:start position:0% and basically how it does is like it calculates<00:10:44.000> the<00:10:44.160> salt<00:10:44.639> with<00:10:44.839> this<00:10:45.120> like<00:10:45.480> in<00:10:45.560> an 00:10:45.750 --> 00:10:45.760 align:start position:0% calculates the salt with this like in an 00:10:45.760 --> 00:10:48.790 align:start position:0% calculates the salt with this like in an MPC<00:10:46.279> fashion<00:10:46.920> that<00:10:47.040> is<00:10:47.160> deterministic<00:10:48.040> but<00:10:48.240> no 00:10:48.790 --> 00:10:48.800 align:start position:0% MPC fashion that is deterministic but no 00:10:48.800 --> 00:10:52.150 align:start position:0% MPC fashion that is deterministic but no any<00:10:49.720> no<00:10:50.120> node<00:10:50.600> by<00:10:50.959> themselves<00:10:51.399> can<00:10:51.760> calculate 00:10:52.150 --> 00:10:52.160 align:start position:0% any no node by themselves can calculate 00:10:52.160 --> 00:10:54.069 align:start position:0% any no node by themselves can calculate that<00:10:52.320> salt<00:10:52.680> for<00:10:52.839> you<00:10:53.279> so<00:10:53.399> I<00:10:53.480> think<00:10:53.639> this<00:10:53.760> solves 00:10:54.069 --> 00:10:54.079 align:start position:0% that salt for you so I think this solves 00:10:54.079 --> 00:10:55.949 align:start position:0% that salt for you so I think this solves two<00:10:54.320> really<00:10:54.519> important<00:10:54.920> problems<00:10:55.399> one<00:10:55.760> is 00:10:55.949 --> 00:10:55.959 align:start position:0% two really important problems one is 00:10:55.959 --> 00:10:57.990 align:start position:0% two really important problems one is like<00:10:56.519> using<00:10:56.839> your<00:10:57.079> private<00:10:57.440> data<00:10:57.720> and<00:10:57.880> this 00:10:57.990 --> 00:10:58.000 align:start position:0% like using your private data and this 00:10:58.000 --> 00:10:59.470 align:start position:0% like using your private data and this Soul<00:10:58.320> generation<00:10:58.839> process<00:10:59.279> which<00:10:59.360> is 00:10:59.470 --> 00:10:59.480 align:start position:0% Soul generation process which is 00:10:59.480 --> 00:11:01.110 align:start position:0% Soul generation process which is deterministic<00:11:00.120> you<00:11:00.200> can<00:11:00.360> recover<00:11:00.800> your 00:11:01.110 --> 00:11:01.120 align:start position:0% deterministic you can recover your 00:11:01.120 --> 00:11:02.790 align:start position:0% deterministic you can recover your account<00:11:01.480> or<00:11:01.600> you<00:11:01.720> can<00:11:01.839> recover<00:11:02.160> your<00:11:02.320> identity 00:11:02.790 --> 00:11:02.800 align:start position:0% account or you can recover your identity 00:11:02.800 --> 00:11:05.150 align:start position:0% account or you can recover your identity even<00:11:02.959> if<00:11:03.079> you<00:11:03.240> lose<00:11:03.480> your<00:11:03.639> phone<00:11:03.920> or<00:11:04.240> like<00:11:04.560> your 00:11:05.150 --> 00:11:05.160 align:start position:0% even if you lose your phone or like your 00:11:05.160 --> 00:11:08.990 align:start position:0% even if you lose your phone or like your cash<00:11:05.480> data<00:11:06.279> the<00:11:06.440> other<00:11:06.600> one<00:11:06.880> is<00:11:07.320> that 00:11:08.990 --> 00:11:09.000 align:start position:0% cash data the other one is that 00:11:09.000 --> 00:11:11.710 align:start position:0% cash data the other one is that um<00:11:10.000> yeah<00:11:10.200> just<00:11:10.519> like<00:11:10.760> way<00:11:11.000> way<00:11:11.120> better<00:11:11.360> user 00:11:11.710 --> 00:11:11.720 align:start position:0% um yeah just like way way better user 00:11:11.720 --> 00:11:13.509 align:start position:0% um yeah just like way way better user experience<00:11:12.200> and<00:11:12.440> oh<00:11:12.639> the<00:11:12.760> other<00:11:12.920> one<00:11:13.120> was<00:11:13.320> that 00:11:13.509 --> 00:11:13.519 align:start position:0% experience and oh the other one was that 00:11:13.519 --> 00:11:15.590 align:start position:0% experience and oh the other one was that no<00:11:13.760> government<00:11:14.160> can<00:11:14.399> calculate<00:11:14.880> that<00:11:15.000> unless 00:11:15.590 --> 00:11:15.600 align:start position:0% no government can calculate that unless 00:11:15.600 --> 00:11:17.870 align:start position:0% no government can calculate that unless yeah<00:11:16.399> they<00:11:16.600> tap<00:11:16.880> into<00:11:17.160> that<00:11:17.440> these<00:11:17.680> these 00:11:17.870 --> 00:11:17.880 align:start position:0% yeah they tap into that these these 00:11:17.880 --> 00:11:20.069 align:start position:0% yeah they tap into that these these process<00:11:18.279> type<00:11:18.600> uh<00:11:18.760> like<00:11:19.120> private<00:11:19.440> data<00:11:19.720> so<00:11:19.959> and 00:11:20.069 --> 00:11:20.079 align:start position:0% process type uh like private data so and 00:11:20.079 --> 00:11:22.110 align:start position:0% process type uh like private data so and and<00:11:20.200> we<00:11:20.279> can<00:11:20.399> make<00:11:20.600> these<00:11:20.839> like<00:11:21.040> very<00:11:21.959> Uh 00:11:22.110 --> 00:11:22.120 align:start position:0% and we can make these like very Uh 00:11:22.120 --> 00:11:24.310 align:start position:0% and we can make these like very Uh custom<00:11:22.600> so<00:11:22.800> like<00:11:23.040> yeah<00:11:23.279> you<00:11:23.360> can<00:11:23.560> choose<00:11:24.000> like 00:11:24.310 --> 00:11:24.320 align:start position:0% custom so like yeah you can choose like 00:11:24.320 --> 00:11:26.030 align:start position:0% custom so like yeah you can choose like private<00:11:24.639> data<00:11:24.839> that<00:11:24.959> only<00:11:25.240> you<00:11:25.399> know<00:11:25.680> in<00:11:25.800> your 00:11:26.030 --> 00:11:26.040 align:start position:0% private data that only you know in your 00:11:26.040 --> 00:11:27.949 align:start position:0% private data that only you know in your head<00:11:26.519> plus<00:11:26.800> like<00:11:27.000> private<00:11:27.320> data<00:11:27.600> that<00:11:27.800> I<00:11:27.839> don't 00:11:27.949 --> 00:11:27.959 align:start position:0% head plus like private data that I don't 00:11:27.959 --> 00:11:29.750 align:start position:0% head plus like private data that I don't know<00:11:28.120> it's<00:11:28.279> very<00:11:28.560> filed<00:11:28.800> in<00:11:28.880> a<00:11:29.000> credential<00:11:29.440> so 00:11:29.750 --> 00:11:29.760 align:start position:0% know it's very filed in a credential so 00:11:29.760 --> 00:11:32.829 align:start position:0% know it's very filed in a credential so yeah<00:11:29.920> in<00:11:30.120> short<00:11:30.800> very<00:11:31.079> strong<00:11:31.240> por<00:11:31.839> periers 00:11:32.829 --> 00:11:32.839 align:start position:0% yeah in short very strong por periers 00:11:32.839 --> 00:11:37.269 align:start position:0% yeah in short very strong por periers and<00:11:33.279> uh<00:11:33.560> yeah<00:11:33.760> anti-is<00:11:34.240> Discovery 00:11:37.269 --> 00:11:37.279 align:start position:0% 00:11:37.279 --> 00:11:41.949 align:start position:0% mechanisms<00:11:38.279> any<00:11:38.480> more<00:11:38.839> questions<00:11:39.399> for 00:11:41.949 --> 00:11:41.959 align:start position:0% 00:11:41.959 --> 00:11:46.260 align:start position:0% Andy<00:11:42.959> okay<00:11:43.200> thank<00:11:43.399> you<00:11:43.560> so<00:11:43.839> much<00:11:44.639> thank<00:11:44.800> you 00:11:46.260 --> 00:11:46.270 align:start position:0% Andy okay thank you so much thank you 00:11:46.270 --> 00:11:48.460 align:start position:0% Andy okay thank you so much thank you [Applause]