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:13.990 align:start position:0% [Music] 00:00:13.990 --> 00:00:14.000 align:start position:0% 00:00:14.000 --> 00:00:15.910 align:start position:0% hello 00:00:15.910 --> 00:00:15.920 align:start position:0% hello 00:00:15.920 --> 00:00:17.630 align:start position:0% hello [Music] 00:00:17.630 --> 00:00:17.640 align:start position:0% [Music] 00:00:17.640 --> 00:00:20.109 align:start position:0% [Music] Defcon<00:00:18.640> so<00:00:18.960> Remco<00:00:19.520> from<00:00:19.680> the<00:00:19.800> world 00:00:20.109 --> 00:00:20.119 align:start position:0% Defcon so Remco from the world 00:00:20.119 --> 00:00:22.029 align:start position:0% Defcon so Remco from the world foundation<00:00:21.119> and<00:00:21.240> I'm<00:00:21.359> going<00:00:21.439> to<00:00:21.560> be<00:00:21.720> talking 00:00:22.029 --> 00:00:22.039 align:start position:0% foundation and I'm going to be talking 00:00:22.039 --> 00:00:24.269 align:start position:0% foundation and I'm going to be talking about<00:00:22.560> a<00:00:22.760> thing<00:00:22.920> we're<00:00:23.080> doing<00:00:23.359> which<00:00:23.519> is<00:00:24.000> proof 00:00:24.269 --> 00:00:24.279 align:start position:0% about a thing we're doing which is proof 00:00:24.279 --> 00:00:26.950 align:start position:0% about a thing we're doing which is proof of<00:00:24.720> human<00:00:25.720> otherwise<00:00:26.119> known<00:00:26.320> as<00:00:26.480> proof<00:00:26.760> of 00:00:26.950 --> 00:00:26.960 align:start position:0% of human otherwise known as proof of 00:00:26.960 --> 00:00:28.070 align:start position:0% of human otherwise known as proof of personhood<00:00:27.480> but<00:00:27.599> that's<00:00:27.720> a<00:00:27.800> bit<00:00:27.920> of<00:00:28.000> a 00:00:28.070 --> 00:00:28.080 align:start position:0% personhood but that's a bit of a 00:00:28.080 --> 00:00:30.310 align:start position:0% personhood but that's a bit of a misnomer<00:00:28.560> we'll<00:00:28.720> get<00:00:28.920> into<00:00:29.199> that<00:00:29.759> and<00:00:30.039> how<00:00:30.199> we 00:00:30.310 --> 00:00:30.320 align:start position:0% misnomer we'll get into that and how we 00:00:30.320 --> 00:00:32.549 align:start position:0% misnomer we'll get into that and how we do<00:00:30.519> this<00:00:30.679> in<00:00:30.800> a<00:00:31.080> private<00:00:31.560> way<00:00:32.160> using 00:00:32.549 --> 00:00:32.559 align:start position:0% do this in a private way using 00:00:32.559 --> 00:00:34.750 align:start position:0% do this in a private way using Biometrics<00:00:33.559> and<00:00:33.719> why<00:00:33.920> we<00:00:34.040> need<00:00:34.200> ethereum<00:00:34.640> to 00:00:34.750 --> 00:00:34.760 align:start position:0% Biometrics and why we need ethereum to 00:00:34.760 --> 00:00:37.709 align:start position:0% Biometrics and why we need ethereum to make<00:00:34.920> that<00:00:35.320> happen<00:00:36.320> so<00:00:36.559> quickly<00:00:37.239> what<00:00:37.440> is 00:00:37.709 --> 00:00:37.719 align:start position:0% make that happen so quickly what is 00:00:37.719 --> 00:00:39.150 align:start position:0% make that happen so quickly what is proof<00:00:38.160> of 00:00:39.150 --> 00:00:39.160 align:start position:0% proof of 00:00:39.160 --> 00:00:41.950 align:start position:0% proof of personhood<00:00:40.160> the<00:00:40.480> short<00:00:40.840> version<00:00:41.239> is<00:00:41.559> it<00:00:41.680> is<00:00:41.800> a 00:00:41.950 --> 00:00:41.960 align:start position:0% personhood the short version is it is a 00:00:41.960 --> 00:00:44.869 align:start position:0% personhood the short version is it is a way<00:00:42.200> to<00:00:42.399> limit<00:00:42.800> account<00:00:43.440> registration<00:00:44.440> to<00:00:44.680> a 00:00:44.869 --> 00:00:44.879 align:start position:0% way to limit account registration to a 00:00:44.879 --> 00:00:49.990 align:start position:0% way to limit account registration to a few<00:00:45.480> ideally<00:00:46.079> one<00:00:46.760> per<00:00:47.039> human 00:00:49.990 --> 00:00:50.000 align:start position:0% 00:00:50.000 --> 00:00:54.470 align:start position:0% being<00:00:51.000> um<00:00:51.879> that<00:00:52.120> in<00:00:52.440> itself<00:00:53.440> uh<00:00:53.800> doesn't<00:00:54.280> give 00:00:54.470 --> 00:00:54.480 align:start position:0% being um that in itself uh doesn't give 00:00:54.480 --> 00:00:57.590 align:start position:0% being um that in itself uh doesn't give you<00:00:54.879> any<00:00:55.120> kind<00:00:55.239> of<00:00:55.480> privacy<00:00:56.359> in<00:00:56.559> fact<00:00:57.440> it 00:00:57.590 --> 00:00:57.600 align:start position:0% you any kind of privacy in fact it 00:00:57.600 --> 00:00:59.310 align:start position:0% you any kind of privacy in fact it usually<00:00:57.920> gives<00:00:58.079> you<00:00:58.239> the<00:00:58.399> opposite<00:00:59.120> but<00:00:59.239> you 00:00:59.310 --> 00:00:59.320 align:start position:0% usually gives you the opposite but you 00:00:59.320 --> 00:01:01.509 align:start position:0% usually gives you the opposite but you can<00:00:59.519> add<00:00:59.680> a<00:01:00.000> layer<00:01:00.239> of<00:01:00.399> zero<00:01:00.719> knowledge<00:01:01.079> proofs 00:01:01.509 --> 00:01:01.519 align:start position:0% can add a layer of zero knowledge proofs 00:01:01.519 --> 00:01:04.990 align:start position:0% can add a layer of zero knowledge proofs on<00:01:01.760> top<00:01:01.920> of<00:01:02.199> that<00:01:03.160> to<00:01:03.920> get<00:01:04.119> a<00:01:04.280> slightly<00:01:04.600> richer 00:01:04.990 --> 00:01:05.000 align:start position:0% on top of that to get a slightly richer 00:01:05.000 --> 00:01:07.950 align:start position:0% on top of that to get a slightly richer primitive<00:01:05.600> which<00:01:05.760> is<00:01:06.680> being<00:01:06.960> able<00:01:07.159> to<00:01:07.400> sign 00:01:07.950 --> 00:01:07.960 align:start position:0% primitive which is being able to sign 00:01:07.960 --> 00:01:12.149 align:start position:0% primitive which is being able to sign messages<00:01:08.560> as<00:01:08.680> a<00:01:08.920> unique<00:01:09.439> Anonymous<00:01:10.560> human<00:01:11.560> for 00:01:12.149 --> 00:01:12.159 align:start position:0% messages as a unique Anonymous human for 00:01:12.159 --> 00:01:14.950 align:start position:0% messages as a unique Anonymous human for example<00:01:13.159> within<00:01:13.479> some<00:01:13.759> context<00:01:14.439> you<00:01:14.560> can<00:01:14.720> sign 00:01:14.950 --> 00:01:14.960 align:start position:0% example within some context you can sign 00:01:14.960 --> 00:01:15.950 align:start position:0% example within some context you can sign a 00:01:15.950 --> 00:01:15.960 align:start position:0% a 00:01:15.960 --> 00:01:18.550 align:start position:0% a message<00:01:16.960> proving<00:01:17.560> that<00:01:17.720> you<00:01:17.880> are<00:01:18.119> a<00:01:18.280> human 00:01:18.550 --> 00:01:18.560 align:start position:0% message proving that you are a human 00:01:18.560 --> 00:01:20.749 align:start position:0% message proving that you are a human being<00:01:19.200> that<00:01:19.400> has<00:01:19.560> not<00:01:19.799> signed<00:01:20.159> a<00:01:20.320> message<00:01:20.600> in 00:01:20.749 --> 00:01:20.759 align:start position:0% being that has not signed a message in 00:01:20.759 --> 00:01:22.910 align:start position:0% being that has not signed a message in this<00:01:20.960> context<00:01:21.439> before<00:01:22.040> you<00:01:22.200> could<00:01:22.360> do<00:01:22.720> let's 00:01:22.910 --> 00:01:22.920 align:start position:0% this context before you could do let's 00:01:22.920 --> 00:01:25.350 align:start position:0% this context before you could do let's say<00:01:23.159> hey<00:01:23.320> dear<00:01:23.640> project<00:01:24.159> please<00:01:24.880> claim<00:01:25.200> my 00:01:25.350 --> 00:01:25.360 align:start position:0% say hey dear project please claim my 00:01:25.360 --> 00:01:28.149 align:start position:0% say hey dear project please claim my airdrop<00:01:25.799> to<00:01:25.920> this<00:01:26.119> addos<00:01:26.880> signed<00:01:27.439> Anonymous 00:01:28.149 --> 00:01:28.159 align:start position:0% airdrop to this addos signed Anonymous 00:01:28.159 --> 00:01:31.230 align:start position:0% airdrop to this addos signed Anonymous human<00:01:28.799> or<00:01:29.079> dear<00:01:29.400> da<00:01:30.159> please<00:01:30.520> allocate<00:01:31.079> my 00:01:31.230 --> 00:01:31.240 align:start position:0% human or dear da please allocate my 00:01:31.240 --> 00:01:34.550 align:start position:0% human or dear da please allocate my voting<00:01:31.600> shares<00:01:32.159> to<00:01:32.920> this<00:01:33.159> particular<00:01:33.600> vote 00:01:34.550 --> 00:01:34.560 align:start position:0% voting shares to this particular vote 00:01:34.560 --> 00:01:38.109 align:start position:0% voting shares to this particular vote signed<00:01:35.040> an<00:01:35.240> anonymous<00:01:35.720> human<00:01:36.680> or<00:01:37.079> dear<00:01:37.320> faras 00:01:38.109 --> 00:01:38.119 align:start position:0% signed an anonymous human or dear faras 00:01:38.119 --> 00:01:41.749 align:start position:0% signed an anonymous human or dear faras please<00:01:38.399> register<00:01:39.000> my<00:01:39.880> handle<00:01:40.799> as<00:01:41.040> belonging 00:01:41.749 --> 00:01:41.759 align:start position:0% please register my handle as belonging 00:01:41.759 --> 00:01:46.030 align:start position:0% please register my handle as belonging to<00:01:42.159> a<00:01:42.560> unique<00:01:43.000> human<00:01:43.280> being<00:01:43.759> and<00:01:43.880> not<00:01:44.040> a<00:01:44.600> bot<00:01:45.600> or 00:01:46.030 --> 00:01:46.040 align:start position:0% to a unique human being and not a bot or 00:01:46.040 --> 00:01:48.310 align:start position:0% to a unique human being and not a bot or dear<00:01:46.560> foraster<00:01:47.560> and<00:01:47.680> this<00:01:47.759> is<00:01:47.880> where<00:01:48.000> it<00:01:48.079> gets 00:01:48.310 --> 00:01:48.320 align:start position:0% dear foraster and this is where it gets 00:01:48.320 --> 00:01:50.830 align:start position:0% dear foraster and this is where it gets interesting<00:01:49.119> please<00:01:49.479> register<00:01:50.119> this<00:01:50.320> other 00:01:50.830 --> 00:01:50.840 align:start position:0% interesting please register this other 00:01:50.840 --> 00:01:54.389 align:start position:0% interesting please register this other handle<00:01:51.719> as<00:01:51.880> my<00:01:52.360> ALT<00:01:53.360> because<00:01:53.600> it<00:01:53.759> doesn't 00:01:54.389 --> 00:01:54.399 align:start position:0% handle as my ALT because it doesn't 00:01:54.399 --> 00:01:57.029 align:start position:0% handle as my ALT because it doesn't necessarily<00:01:55.200> mean<00:01:55.960> that<00:01:56.079> you're<00:01:56.360> restricted 00:01:57.029 --> 00:01:57.039 align:start position:0% necessarily mean that you're restricted 00:01:57.039 --> 00:01:59.990 align:start position:0% necessarily mean that you're restricted to<00:01:57.320> One<00:01:57.719> account<00:01:58.039> per<00:01:58.240> human<00:01:58.479> being 00:01:59.990 --> 00:02:00.000 align:start position:0% to One account per human being 00:02:00.000 --> 00:02:01.830 align:start position:0% to One account per human being you<00:02:00.200> can<00:02:00.520> have<00:02:00.680> multiple<00:02:01.159> accounts<00:02:01.560> it's<00:02:01.719> kind 00:02:01.830 --> 00:02:01.840 align:start position:0% you can have multiple accounts it's kind 00:02:01.840 --> 00:02:04.830 align:start position:0% you can have multiple accounts it's kind of<00:02:02.000> up<00:02:02.200> to<00:02:02.479> the<00:02:03.039> application<00:02:03.680> developer<00:02:04.600> to 00:02:04.830 --> 00:02:04.840 align:start position:0% of up to the application developer to 00:02:04.840 --> 00:02:07.270 align:start position:0% of up to the application developer to specify<00:02:05.439> what<00:02:05.640> the<00:02:05.799> desired<00:02:06.240> behavior<00:02:06.759> is<00:02:07.159> it 00:02:07.270 --> 00:02:07.280 align:start position:0% specify what the desired behavior is it 00:02:07.280 --> 00:02:09.029 align:start position:0% specify what the desired behavior is it is<00:02:07.399> a<00:02:07.600> programmable<00:02:08.239> primitive<00:02:08.759> that<00:02:08.879> we're 00:02:09.029 --> 00:02:09.039 align:start position:0% is a programmable primitive that we're 00:02:09.039 --> 00:02:10.869 align:start position:0% is a programmable primitive that we're adding<00:02:09.319> to<00:02:09.440> the 00:02:10.869 --> 00:02:10.879 align:start position:0% adding to the 00:02:10.879 --> 00:02:14.750 align:start position:0% adding to the blockchain<00:02:11.879> what<00:02:12.040> is<00:02:12.160> it<00:02:12.520> not<00:02:13.520> it<00:02:13.640> is<00:02:13.920> not<00:02:14.519> very 00:02:14.750 --> 00:02:14.760 align:start position:0% blockchain what is it not it is not very 00:02:14.760 --> 00:02:16.309 align:start position:0% blockchain what is it not it is not very importantly<00:02:15.319> a 00:02:16.309 --> 00:02:16.319 align:start position:0% importantly a 00:02:16.319 --> 00:02:19.910 align:start position:0% importantly a capture<00:02:17.319> a<00:02:17.519> proof<00:02:17.760> of<00:02:18.239> personhood<00:02:19.239> does<00:02:19.519> not 00:02:19.910 --> 00:02:19.920 align:start position:0% capture a proof of personhood does not 00:02:19.920 --> 00:02:23.509 align:start position:0% capture a proof of personhood does not prevent<00:02:20.599> a<00:02:20.959> bot<00:02:21.760> from<00:02:21.959> doing<00:02:22.400> something<00:02:23.360> it 00:02:23.509 --> 00:02:23.519 align:start position:0% prevent a bot from doing something it 00:02:23.519 --> 00:02:25.869 align:start position:0% prevent a bot from doing something it just<00:02:23.720> means<00:02:24.319> that<00:02:25.000> this 00:02:25.869 --> 00:02:25.879 align:start position:0% just means that this 00:02:25.879 --> 00:02:28.030 align:start position:0% just means that this action<00:02:26.879> was 00:02:28.030 --> 00:02:28.040 align:start position:0% action was 00:02:28.040 --> 00:02:30.990 align:start position:0% action was initiated<00:02:29.040> and<00:02:29.239> kind<00:02:29.360> of<00:02:29.440> signed<00:02:29.720> up<00:02:30.000> of<00:02:30.560> by<00:02:30.720> a 00:02:30.990 --> 00:02:31.000 align:start position:0% initiated and kind of signed up of by a 00:02:31.000 --> 00:02:33.630 align:start position:0% initiated and kind of signed up of by a specific<00:02:31.599> human<00:02:32.040> being<00:02:32.840> so<00:02:33.000> you<00:02:33.120> can<00:02:33.319> still 00:02:33.630 --> 00:02:33.640 align:start position:0% specific human being so you can still 00:02:33.640 --> 00:02:37.509 align:start position:0% specific human being so you can still automate<00:02:34.200> your 00:02:37.509 --> 00:02:37.519 align:start position:0% 00:02:37.519 --> 00:02:40.550 align:start position:0% accounts<00:02:38.519> now<00:02:38.760> why<00:02:38.879> do<00:02:39.080> we<00:02:39.239> want<00:02:39.720> proof<00:02:40.040> of 00:02:40.550 --> 00:02:40.560 align:start position:0% accounts now why do we want proof of 00:02:40.560 --> 00:02:44.390 align:start position:0% accounts now why do we want proof of personhood<00:02:41.560> at<00:02:41.680> a<00:02:41.920> high<00:02:42.319> level<00:02:43.319> AI<00:02:44.000> will<00:02:44.239> make 00:02:44.390 --> 00:02:44.400 align:start position:0% personhood at a high level AI will make 00:02:44.400 --> 00:02:47.110 align:start position:0% personhood at a high level AI will make it<00:02:44.680> impossible<00:02:45.400> to<00:02:45.720> distinguish<00:02:46.720> on 00:02:47.110 --> 00:02:47.120 align:start position:0% it impossible to distinguish on 00:02:47.120 --> 00:02:48.869 align:start position:0% it impossible to distinguish on behavioral<00:02:47.760> features 00:02:48.869 --> 00:02:48.879 align:start position:0% behavioral features 00:02:48.879 --> 00:02:51.550 align:start position:0% behavioral features alone<00:02:49.879> at<00:02:50.000> least<00:02:50.200> in<00:02:50.319> the<00:02:50.480> digital 00:02:51.550 --> 00:02:51.560 align:start position:0% alone at least in the digital 00:02:51.560 --> 00:02:54.630 align:start position:0% alone at least in the digital domain<00:02:52.560> and<00:02:53.040> AI<00:02:53.440> fueled<00:02:53.879> economic 00:02:54.630 --> 00:02:54.640 align:start position:0% domain and AI fueled economic 00:02:54.640 --> 00:02:57.670 align:start position:0% domain and AI fueled economic disruptions<00:02:55.640> require<00:02:56.159> us<00:02:56.800> to<00:02:57.040> get<00:02:57.360> much 00:02:57.670 --> 00:02:57.680 align:start position:0% disruptions require us to get much 00:02:57.680 --> 00:03:01.149 align:start position:0% disruptions require us to get much better<00:02:58.200> at<00:02:59.080> creating<00:03:00.159> human<00:03:00.519> oriented 00:03:01.149 --> 00:03:01.159 align:start position:0% better at creating human oriented 00:03:01.159 --> 00:03:04.070 align:start position:0% better at creating human oriented Financial<00:03:02.000> Solutions<00:03:03.000> to<00:03:03.280> solve<00:03:03.760> any 00:03:04.070 --> 00:03:04.080 align:start position:0% Financial Solutions to solve any 00:03:04.080 --> 00:03:06.430 align:start position:0% Financial Solutions to solve any economic<00:03:04.640> hardship<00:03:05.640> that<00:03:05.799> might<00:03:06.040> happen<00:03:06.319> in 00:03:06.430 --> 00:03:06.440 align:start position:0% economic hardship that might happen in 00:03:06.440 --> 00:03:07.750 align:start position:0% economic hardship that might happen in the 00:03:07.750 --> 00:03:07.760 align:start position:0% the 00:03:07.760 --> 00:03:10.509 align:start position:0% the world<00:03:08.799> therefore<00:03:09.799> we<00:03:09.920> need<00:03:10.080> to<00:03:10.239> add 00:03:10.509 --> 00:03:10.519 align:start position:0% world therefore we need to add 00:03:10.519 --> 00:03:13.190 align:start position:0% world therefore we need to add individuals<00:03:11.120> as<00:03:11.239> a<00:03:11.440> programmable<00:03:12.319> primitive 00:03:13.190 --> 00:03:13.200 align:start position:0% individuals as a programmable primitive 00:03:13.200 --> 00:03:15.670 align:start position:0% individuals as a programmable primitive it<00:03:13.280> is<00:03:13.440> also<00:03:13.720> critical<00:03:14.159> to<00:03:14.319> get<00:03:14.680> strong 00:03:15.670 --> 00:03:15.680 align:start position:0% it is also critical to get strong 00:03:15.680 --> 00:03:17.470 align:start position:0% it is also critical to get strong decentralization 00:03:17.470 --> 00:03:17.480 align:start position:0% decentralization 00:03:17.480 --> 00:03:20.350 align:start position:0% decentralization because<00:03:18.480> the<00:03:18.680> only<00:03:19.040> way<00:03:19.200> to<00:03:19.440> make<00:03:19.640> sure<00:03:20.120> that 00:03:20.350 --> 00:03:20.360 align:start position:0% because the only way to make sure that 00:03:20.360 --> 00:03:22.910 align:start position:0% because the only way to make sure that many<00:03:20.720> many<00:03:21.120> people<00:03:21.680> are<00:03:21.920> involved<00:03:22.640> in 00:03:22.910 --> 00:03:22.920 align:start position:0% many many people are involved in 00:03:22.920 --> 00:03:25.509 align:start position:0% many many people are involved in consensus<00:03:23.440> making<00:03:24.440> is<00:03:24.680> through<00:03:25.080> a<00:03:25.200> form<00:03:25.400> of 00:03:25.509 --> 00:03:25.519 align:start position:0% consensus making is through a form of 00:03:25.519 --> 00:03:28.710 align:start position:0% consensus making is through a form of proof<00:03:25.760> of<00:03:25.920> person<00:03:26.560> Hub<00:03:27.560> this<00:03:27.720> in<00:03:27.920> turn<00:03:28.239> unlocks 00:03:28.710 --> 00:03:28.720 align:start position:0% proof of person Hub this in turn unlocks 00:03:28.720 --> 00:03:31.350 align:start position:0% proof of person Hub this in turn unlocks Financial<00:03:29.120> Primitives<00:03:30.239> with<00:03:30.519> a<00:03:30.760> concept<00:03:31.159> of 00:03:31.350 --> 00:03:31.360 align:start position:0% Financial Primitives with a concept of 00:03:31.360 --> 00:03:33.030 align:start position:0% Financial Primitives with a concept of individuals<00:03:31.879> and<00:03:32.000> a<00:03:32.080> lot<00:03:32.239> of<00:03:32.360> them<00:03:32.560> have<00:03:32.760> that 00:03:33.030 --> 00:03:33.040 align:start position:0% individuals and a lot of them have that 00:03:33.040 --> 00:03:35.229 align:start position:0% individuals and a lot of them have that insurance<00:03:33.560> loans<00:03:34.000> pensions<00:03:34.480> Universal<00:03:34.959> basic 00:03:35.229 --> 00:03:35.239 align:start position:0% insurance loans pensions Universal basic 00:03:35.239 --> 00:03:38.270 align:start position:0% insurance loans pensions Universal basic income<00:03:36.040> none<00:03:36.280> of<00:03:36.560> these<00:03:37.280> we<00:03:37.439> can<00:03:37.680> currently<00:03:38.040> do 00:03:38.270 --> 00:03:38.280 align:start position:0% income none of these we can currently do 00:03:38.280 --> 00:03:40.270 align:start position:0% income none of these we can currently do with<00:03:38.480> programmable<00:03:39.080> money<00:03:39.760> because<00:03:40.000> we<00:03:40.120> do 00:03:40.270 --> 00:03:40.280 align:start position:0% with programmable money because we do 00:03:40.280 --> 00:03:42.550 align:start position:0% with programmable money because we do not<00:03:40.519> yet<00:03:40.760> have<00:03:41.040> programmable<00:03:41.720> individuals 00:03:42.550 --> 00:03:42.560 align:start position:0% not yet have programmable individuals 00:03:42.560 --> 00:03:43.910 align:start position:0% not yet have programmable individuals we're<00:03:42.720> changing 00:03:43.910 --> 00:03:43.920 align:start position:0% we're changing 00:03:43.920 --> 00:03:46.149 align:start position:0% we're changing that<00:03:44.920> and<00:03:45.040> that<00:03:45.200> allows<00:03:45.439> you<00:03:45.560> to<00:03:45.760> do<00:03:45.879> cool 00:03:46.149 --> 00:03:46.159 align:start position:0% that and that allows you to do cool 00:03:46.159 --> 00:03:48.750 align:start position:0% that and that allows you to do cool things<00:03:46.560> that<00:03:47.360> kind<00:03:47.519> of<00:03:47.720> I<00:03:47.840> didn't<00:03:48.159> even<00:03:48.439> expect 00:03:48.750 --> 00:03:48.760 align:start position:0% things that kind of I didn't even expect 00:03:48.760 --> 00:03:50.589 align:start position:0% things that kind of I didn't even expect when<00:03:48.879> we<00:03:49.000> started<00:03:49.360> this<00:03:49.640> like<00:03:50.000> um<00:03:50.159> the<00:03:50.280> world 00:03:50.589 --> 00:03:50.599 align:start position:0% when we started this like um the world 00:03:50.599 --> 00:03:53.470 align:start position:0% when we started this like um the world chain<00:03:50.879> L2<00:03:51.360> that<00:03:51.480> we<00:03:51.640> just<00:03:52.040> launched<00:03:53.040> has 00:03:53.470 --> 00:03:53.480 align:start position:0% chain L2 that we just launched has 00:03:53.480 --> 00:03:56.110 align:start position:0% chain L2 that we just launched has prioritized<00:03:54.200> block<00:03:54.480> space<00:03:54.720> for<00:03:54.959> humans<00:03:55.799> so<00:03:56.000> if 00:03:56.110 --> 00:03:56.120 align:start position:0% prioritized block space for humans so if 00:03:56.120 --> 00:04:00.149 align:start position:0% prioritized block space for humans so if you're<00:03:56.319> a<00:03:56.439> human<00:03:56.920> being<00:03:57.920> you<00:03:58.720> get<00:03:59.079> priority 00:04:00.149 --> 00:04:00.159 align:start position:0% you're a human being you get priority 00:04:00.159 --> 00:04:02.789 align:start position:0% you're a human being you get priority over<00:04:00.400> the<00:04:00.599> trading<00:04:01.040> bots<00:04:01.879> in<00:04:02.040> the 00:04:02.789 --> 00:04:02.799 align:start position:0% over the trading bots in the 00:04:02.799 --> 00:04:04.710 align:start position:0% over the trading bots in the sequencer<00:04:03.799> and<00:04:03.920> then<00:04:04.079> of<00:04:04.200> course<00:04:04.360> there's<00:04:04.560> the 00:04:04.710 --> 00:04:04.720 align:start position:0% sequencer and then of course there's the 00:04:04.720 --> 00:04:07.149 align:start position:0% sequencer and then of course there's the basics<00:04:05.120> like<00:04:05.239> Cil<00:04:05.799> resistance<00:04:06.360> and 00:04:07.149 --> 00:04:07.159 align:start position:0% basics like Cil resistance and 00:04:07.159 --> 00:04:08.550 align:start position:0% basics like Cil resistance and preventing<00:04:07.760> spam 00:04:08.550 --> 00:04:08.560 align:start position:0% preventing spam 00:04:08.560 --> 00:04:12.190 align:start position:0% preventing spam BBL<00:04:09.560> now<00:04:09.799> why<00:04:09.920> would<00:04:10.079> you<00:04:10.319> not<00:04:10.640> want<00:04:10.959> proof<00:04:11.200> of 00:04:12.190 --> 00:04:12.200 align:start position:0% BBL now why would you not want proof of 00:04:12.200 --> 00:04:15.190 align:start position:0% BBL now why would you not want proof of personhood<00:04:13.200> unique<00:04:13.640> human<00:04:14.439> can<00:04:14.680> often<00:04:15.000> just 00:04:15.190 --> 00:04:15.200 align:start position:0% personhood unique human can often just 00:04:15.200 --> 00:04:17.830 align:start position:0% personhood unique human can often just be<00:04:15.560> a<00:04:15.840> proxy<00:04:16.280> for<00:04:16.600> something<00:04:17.000> more<00:04:17.320> precise 00:04:17.830 --> 00:04:17.840 align:start position:0% be a proxy for something more precise 00:04:17.840 --> 00:04:20.629 align:start position:0% be a proxy for something more precise that<00:04:18.000> is<00:04:18.560> what<00:04:18.720> you<00:04:18.919> really<00:04:19.280> want<00:04:20.079> like<00:04:20.479> when 00:04:20.629 --> 00:04:20.639 align:start position:0% that is what you really want like when 00:04:20.639 --> 00:04:23.670 align:start position:0% that is what you really want like when it<00:04:20.799> comes<00:04:21.040> to<00:04:22.000> let's<00:04:22.320> say<00:04:23.320> under 00:04:23.670 --> 00:04:23.680 align:start position:0% it comes to let's say under 00:04:23.680 --> 00:04:24.870 align:start position:0% it comes to let's say under collateralized 00:04:24.870 --> 00:04:24.880 align:start position:0% collateralized 00:04:24.880 --> 00:04:27.790 align:start position:0% collateralized loans<00:04:25.880> you're<00:04:26.080> not<00:04:26.320> necessarily<00:04:27.080> interested 00:04:27.790 --> 00:04:27.800 align:start position:0% loans you're not necessarily interested 00:04:27.800 --> 00:04:29.749 align:start position:0% loans you're not necessarily interested in<00:04:28.120> a<00:04:28.360> unique<00:04:28.759> human<00:04:29.039> being<00:04:29.360> you're 00:04:29.749 --> 00:04:29.759 align:start position:0% in a unique human being you're 00:04:29.759 --> 00:04:31.070 align:start position:0% in a unique human being you're interested<00:04:30.199> in<00:04:30.360> someone's<00:04:30.759> credit 00:04:31.070 --> 00:04:31.080 align:start position:0% interested in someone's credit 00:04:31.080 --> 00:04:32.670 align:start position:0% interested in someone's credit worthiness<00:04:31.720> and<00:04:31.800> there<00:04:31.960> might<00:04:32.160> be<00:04:32.360> better 00:04:32.670 --> 00:04:32.680 align:start position:0% worthiness and there might be better 00:04:32.680 --> 00:04:34.590 align:start position:0% worthiness and there might be better tests<00:04:33.120> for<00:04:33.360> that<00:04:33.800> that<00:04:33.919> you<00:04:34.039> could<00:04:34.199> use 00:04:34.590 --> 00:04:34.600 align:start position:0% tests for that that you could use 00:04:34.600 --> 00:04:37.029 align:start position:0% tests for that that you could use directly<00:04:35.600> that<00:04:35.759> would<00:04:36.039> in<00:04:36.160> the<00:04:36.280> end<00:04:36.560> create<00:04:36.840> a 00:04:37.029 --> 00:04:37.039 align:start position:0% directly that would in the end create a 00:04:37.039 --> 00:04:38.950 align:start position:0% directly that would in the end create a system<00:04:37.360> that<00:04:37.600> abstracts<00:04:38.199> better<00:04:38.520> what<00:04:38.639> it<00:04:38.759> is 00:04:38.950 --> 00:04:38.960 align:start position:0% system that abstracts better what it is 00:04:38.960 --> 00:04:43.550 align:start position:0% system that abstracts better what it is aiming<00:04:39.280> to<00:04:39.800> do<00:04:40.800> um<00:04:41.240> you<00:04:41.360> could<00:04:41.919> also<00:04:42.919> have<00:04:43.160> a 00:04:43.550 --> 00:04:43.560 align:start position:0% aiming to do um you could also have a 00:04:43.560 --> 00:04:45.790 align:start position:0% aiming to do um you could also have a like<00:04:43.720> you<00:04:43.800> could<00:04:44.000> also<00:04:44.280> Imagine<00:04:45.199> a<00:04:45.400> social 00:04:45.790 --> 00:04:45.800 align:start position:0% like you could also Imagine a social 00:04:45.800 --> 00:04:48.670 align:start position:0% like you could also Imagine a social media<00:04:46.600> platform<00:04:47.600> where<00:04:47.960> you<00:04:48.080> don't<00:04:48.360> really 00:04:48.670 --> 00:04:48.680 align:start position:0% media platform where you don't really 00:04:48.680 --> 00:04:51.469 align:start position:0% media platform where you don't really care<00:04:49.000> whether<00:04:49.240> someone<00:04:49.520> is<00:04:49.680> a<00:04:49.840> human<00:04:50.240> or<00:04:50.400> a<00:04:50.600> bot 00:04:51.469 --> 00:04:51.479 align:start position:0% care whether someone is a human or a bot 00:04:51.479 --> 00:04:53.710 align:start position:0% care whether someone is a human or a bot as<00:04:51.639> long<00:04:51.880> as<00:04:52.080> they<00:04:52.240> make<00:04:52.600> valid<00:04:53.080> meaningful 00:04:53.710 --> 00:04:53.720 align:start position:0% as long as they make valid meaningful 00:04:53.720 --> 00:04:55.629 align:start position:0% as long as they make valid meaningful contributions<00:04:54.479> to<00:04:54.639> the 00:04:55.629 --> 00:04:55.639 align:start position:0% contributions to the 00:04:55.639 --> 00:04:57.790 align:start position:0% contributions to the discussion<00:04:56.639> so<00:04:57.000> here<00:04:57.240> again<00:04:57.440> there<00:04:57.560> is<00:04:57.639> a 00:04:57.790 --> 00:04:57.800 align:start position:0% discussion so here again there is a 00:04:57.800 --> 00:04:59.749 align:start position:0% discussion so here again there is a trade-off<00:04:58.240> for<00:04:58.360> the<00:04:58.479> app<00:04:58.720> developers<00:04:59.199> to<00:04:59.360> make 00:04:59.749 --> 00:04:59.759 align:start position:0% trade-off for the app developers to make 00:04:59.759 --> 00:05:01.830 align:start position:0% trade-off for the app developers to make like<00:05:00.000> is<00:05:00.440> is<00:05:00.600> proof<00:05:00.840> of<00:05:01.000> person<00:05:01.320> not<00:05:01.560> actually 00:05:01.830 --> 00:05:01.840 align:start position:0% like is is proof of person not actually 00:05:01.840 --> 00:05:04.310 align:start position:0% like is is proof of person not actually what<00:05:01.960> I<00:05:02.080> need 00:05:04.310 --> 00:05:04.320 align:start position:0% what I need 00:05:04.320 --> 00:05:06.670 align:start position:0% what I need here<00:05:05.320> and<00:05:05.600> there's<00:05:05.840> kind<00:05:05.960> of<00:05:06.120> like<00:05:06.240> a<00:05:06.520> an 00:05:06.670 --> 00:05:06.680 align:start position:0% here and there's kind of like a an 00:05:06.680 --> 00:05:09.189 align:start position:0% here and there's kind of like a an argument<00:05:07.120> that<00:05:07.199> you<00:05:07.280> can<00:05:07.440> make<00:05:07.840> that<00:05:08.479> um<00:05:09.039> if 00:05:09.189 --> 00:05:09.199 align:start position:0% argument that you can make that um if 00:05:09.199 --> 00:05:11.469 align:start position:0% argument that you can make that um if you<00:05:09.520> really<00:05:09.919> aim<00:05:10.160> for<00:05:10.440> maximal 00:05:11.469 --> 00:05:11.479 align:start position:0% you really aim for maximal 00:05:11.479 --> 00:05:14.350 align:start position:0% you really aim for maximal anonymity<00:05:12.479> not<00:05:12.720> even<00:05:13.039> the<00:05:13.280> number<00:05:13.680> of<00:05:13.919> humans 00:05:14.350 --> 00:05:14.360 align:start position:0% anonymity not even the number of humans 00:05:14.360 --> 00:05:16.430 align:start position:0% anonymity not even the number of humans that<00:05:14.479> are<00:05:14.600> currently<00:05:15.000> in<00:05:15.120> your<00:05:15.320> system<00:05:16.160> should 00:05:16.430 --> 00:05:16.440 align:start position:0% that are currently in your system should 00:05:16.440 --> 00:05:18.550 align:start position:0% that are currently in your system should be<00:05:16.720> transparent<00:05:17.720> which<00:05:17.880> is<00:05:18.039> something<00:05:18.400> that 00:05:18.550 --> 00:05:18.560 align:start position:0% be transparent which is something that 00:05:18.560 --> 00:05:21.189 align:start position:0% be transparent which is something that of<00:05:18.680> course<00:05:18.840> proof<00:05:19.080> of<00:05:19.240> person 00:05:21.189 --> 00:05:21.199 align:start position:0% of course proof of person 00:05:21.199 --> 00:05:23.950 align:start position:0% of course proof of person achieves<00:05:22.199> okay<00:05:23.039> now<00:05:23.240> that<00:05:23.360> we've<00:05:23.560> covered 00:05:23.950 --> 00:05:23.960 align:start position:0% achieves okay now that we've covered 00:05:23.960 --> 00:05:27.029 align:start position:0% achieves okay now that we've covered what<00:05:24.080> it<00:05:24.319> is<00:05:24.800> how<00:05:24.880> do<00:05:25.039> we<00:05:25.199> build<00:05:25.479> it<00:05:25.919> how<00:05:26.080> is<00:05:26.199> it 00:05:27.029 --> 00:05:27.039 align:start position:0% what it is how do we build it how is it 00:05:27.039 --> 00:05:29.749 align:start position:0% what it is how do we build it how is it constructed<00:05:28.039> um<00:05:28.759> the<00:05:28.919> main<00:05:29.199> problem<00:05:29.440> you 00:05:29.749 --> 00:05:29.759 align:start position:0% constructed um the main problem you 00:05:29.759 --> 00:05:31.550 align:start position:0% constructed um the main problem you solving<00:05:30.120> here<00:05:30.240> is<00:05:30.360> the<00:05:30.479> Oracle<00:05:31.000> problem 00:05:31.550 --> 00:05:31.560 align:start position:0% solving here is the Oracle problem 00:05:31.560 --> 00:05:34.430 align:start position:0% solving here is the Oracle problem you're<00:05:31.800> trying<00:05:32.120> to<00:05:32.400> build<00:05:32.800> some<00:05:33.440> information 00:05:34.430 --> 00:05:34.440 align:start position:0% you're trying to build some information 00:05:34.440 --> 00:05:37.710 align:start position:0% you're trying to build some information in<00:05:34.720> the<00:05:35.520> platonic<00:05:36.240> ideal<00:05:36.759> cryptographic 00:05:37.710 --> 00:05:37.720 align:start position:0% in the platonic ideal cryptographic 00:05:37.720 --> 00:05:40.550 align:start position:0% in the platonic ideal cryptographic trusted<00:05:38.319> domain<00:05:39.319> that<00:05:39.520> comes<00:05:39.759> from<00:05:39.960> the 00:05:40.550 --> 00:05:40.560 align:start position:0% trusted domain that comes from the 00:05:40.560 --> 00:05:42.909 align:start position:0% trusted domain that comes from the outside<00:05:41.560> that<00:05:41.720> comes<00:05:42.039> in<00:05:42.240> in<00:05:42.400> this<00:05:42.560> case<00:05:42.759> from 00:05:42.909 --> 00:05:42.919 align:start position:0% outside that comes in in this case from 00:05:42.919 --> 00:05:45.390 align:start position:0% outside that comes in in this case from the<00:05:43.120> physical<00:05:43.919> real<00:05:44.280> world<00:05:44.639> of 00:05:45.390 --> 00:05:45.400 align:start position:0% the physical real world of 00:05:45.400 --> 00:05:48.790 align:start position:0% the physical real world of humans<00:05:46.400> and<00:05:47.400> solving<00:05:47.800> Oracle<00:05:48.280> problems 00:05:48.790 --> 00:05:48.800 align:start position:0% humans and solving Oracle problems 00:05:48.800 --> 00:05:51.430 align:start position:0% humans and solving Oracle problems always<00:05:49.199> means<00:05:49.840> some<00:05:50.240> form<00:05:50.520> of<00:05:50.720> compromise<00:05:51.319> and 00:05:51.430 --> 00:05:51.440 align:start position:0% always means some form of compromise and 00:05:51.440 --> 00:05:53.670 align:start position:0% always means some form of compromise and the<00:05:51.639> question<00:05:52.000> is<00:05:52.639> what<00:05:52.759> is<00:05:52.919> the<00:05:53.120> best<00:05:53.280> trade 00:05:53.670 --> 00:05:53.680 align:start position:0% the question is what is the best trade 00:05:53.680 --> 00:05:55.150 align:start position:0% the question is what is the best trade of<00:05:53.919> for<00:05:54.120> the<00:05:54.319> specific<00:05:54.759> problem<00:05:55.000> you're 00:05:55.150 --> 00:05:55.160 align:start position:0% of for the specific problem you're 00:05:55.160 --> 00:05:57.749 align:start position:0% of for the specific problem you're trying<00:05:55.440> to<00:05:55.600> solve<00:05:56.600> the<00:05:56.759> three<00:05:57.080> main 00:05:57.749 --> 00:05:57.759 align:start position:0% trying to solve the three main 00:05:57.759 --> 00:06:00.590 align:start position:0% trying to solve the three main approaches<00:05:58.759> for<00:05:59.240> proof<00:05:59.479> of<00:05:59.720> personhood<00:06:00.280> are 00:06:00.590 --> 00:06:00.600 align:start position:0% approaches for proof of personhood are 00:06:00.600 --> 00:06:03.590 align:start position:0% approaches for proof of personhood are Authority<00:06:01.440> based<00:06:02.440> where<00:06:02.800> you<00:06:03.080> use<00:06:03.360> some 00:06:03.590 --> 00:06:03.600 align:start position:0% Authority based where you use some 00:06:03.600 --> 00:06:06.670 align:start position:0% Authority based where you use some existing<00:06:04.039> Authority<00:06:04.520> like<00:06:04.639> a<00:06:05.039> government<00:06:06.039> or 00:06:06.670 --> 00:06:06.680 align:start position:0% existing Authority like a government or 00:06:06.680 --> 00:06:11.749 align:start position:0% existing Authority like a government or a<00:06:07.440> email<00:06:07.880> provider<00:06:08.560> or<00:06:08.880> a<00:06:09.160> bank<00:06:10.120> as<00:06:10.599> a<00:06:11.240> trusted 00:06:11.749 --> 00:06:11.759 align:start position:0% a email provider or a bank as a trusted 00:06:11.759 --> 00:06:15.790 align:start position:0% a email provider or a bank as a trusted entity<00:06:12.479> to<00:06:13.479> have<00:06:13.680> a<00:06:13.840> list<00:06:14.080> of<00:06:14.240> all<00:06:14.400> the<00:06:14.800> humans 00:06:15.790 --> 00:06:15.800 align:start position:0% entity to have a list of all the humans 00:06:15.800 --> 00:06:20.350 align:start position:0% entity to have a list of all the humans others<00:06:16.080> are<00:06:16.319> graph-based<00:06:17.240> um<00:06:18.240> these<00:06:18.440> are 00:06:20.350 --> 00:06:20.360 align:start position:0% others are graph-based um these are 00:06:20.360 --> 00:06:22.749 align:start position:0% others are graph-based um these are decentralized<00:06:21.360> and<00:06:21.560> here<00:06:21.720> you<00:06:21.919> have<00:06:22.199> humans 00:06:22.749 --> 00:06:22.759 align:start position:0% decentralized and here you have humans 00:06:22.759 --> 00:06:24.670 align:start position:0% decentralized and here you have humans essentially<00:06:23.160> verifying<00:06:23.759> other<00:06:24.000> humans<00:06:24.520> or 00:06:24.670 --> 00:06:24.680 align:start position:0% essentially verifying other humans or 00:06:24.680 --> 00:06:27.589 align:start position:0% essentially verifying other humans or you<00:06:24.840> take<00:06:25.039> some<00:06:25.360> approach<00:06:25.759> to<00:06:26.720> pair<00:06:27.160> wise 00:06:27.589 --> 00:06:27.599 align:start position:0% you take some approach to pair wise 00:06:27.599 --> 00:06:30.189 align:start position:0% you take some approach to pair wise distinguish<00:06:28.199> humans<00:06:28.560> from<00:06:28.800> each<00:06:28.960> other 00:06:30.189 --> 00:06:30.199 align:start position:0% distinguish humans from each other 00:06:30.199 --> 00:06:32.469 align:start position:0% distinguish humans from each other and<00:06:30.440> then<00:06:30.919> turn<00:06:31.240> that<00:06:31.400> into<00:06:31.560> a<00:06:31.680> larger<00:06:32.039> grab 00:06:32.469 --> 00:06:32.479 align:start position:0% and then turn that into a larger grab 00:06:32.479 --> 00:06:34.029 align:start position:0% and then turn that into a larger grab I'll<00:06:32.639> get<00:06:32.759> into<00:06:32.960> more<00:06:33.160> details<00:06:33.479> on<00:06:33.639> each<00:06:33.840> of 00:06:34.029 --> 00:06:34.039 align:start position:0% I'll get into more details on each of 00:06:34.039 --> 00:06:39.390 align:start position:0% I'll get into more details on each of these<00:06:34.479> um<00:06:35.039> in<00:06:35.120> a<00:06:35.280> moment<00:06:36.240> biometric<00:06:37.160> based<00:06:38.400> is 00:06:39.390 --> 00:06:39.400 align:start position:0% these um in a moment biometric based is 00:06:39.400 --> 00:06:41.390 align:start position:0% these um in a moment biometric based is recognizing<00:06:40.039> that<00:06:40.160> humans<00:06:40.560> have<00:06:40.720> a<00:06:40.960> physical 00:06:41.390 --> 00:06:41.400 align:start position:0% recognizing that humans have a physical 00:06:41.400 --> 00:06:44.110 align:start position:0% recognizing that humans have a physical body<00:06:42.319> and<00:06:42.440> doing<00:06:42.840> measurements<00:06:43.400> on<00:06:43.639> that<00:06:43.840> body 00:06:44.110 --> 00:06:44.120 align:start position:0% body and doing measurements on that body 00:06:44.120 --> 00:06:46.469 align:start position:0% body and doing measurements on that body to<00:06:44.319> distinguish<00:06:44.800> it<00:06:44.919> from<00:06:45.120> other 00:06:46.469 --> 00:06:46.479 align:start position:0% to distinguish it from other 00:06:46.479 --> 00:06:49.670 align:start position:0% to distinguish it from other bodies<00:06:47.479> now<00:06:47.680> the<00:06:47.840> authority<00:06:48.440> based<00:06:49.440> this<00:06:49.560> is 00:06:49.670 --> 00:06:49.680 align:start position:0% bodies now the authority based this is 00:06:49.680 --> 00:06:51.749 align:start position:0% bodies now the authority based this is the<00:06:49.880> conventional<00:06:50.400> solution<00:06:50.919> this<00:06:51.039> is<00:06:51.280> what 00:06:51.749 --> 00:06:51.759 align:start position:0% the conventional solution this is what 00:06:51.759 --> 00:06:53.950 align:start position:0% the conventional solution this is what the<00:06:51.880> whole<00:06:52.080> Web<00:06:52.319> Two<00:06:52.599> World<00:06:52.919> the<00:06:53.080> non<00:06:53.560> crypto 00:06:53.950 --> 00:06:53.960 align:start position:0% the whole Web Two World the non crypto 00:06:53.960 --> 00:06:56.309 align:start position:0% the whole Web Two World the non crypto World<00:06:54.280> uses<00:06:55.160> when<00:06:55.319> they<00:06:55.440> need<00:06:55.800> anything 00:06:56.309 --> 00:06:56.319 align:start position:0% World uses when they need anything 00:06:56.319 --> 00:06:58.469 align:start position:0% World uses when they need anything remotely<00:06:56.720> resembling<00:06:57.240> proof<00:06:57.479> of<00:06:57.680> personhood 00:06:58.469 --> 00:06:58.479 align:start position:0% remotely resembling proof of personhood 00:06:58.479 --> 00:07:00.469 align:start position:0% remotely resembling proof of personhood for<00:06:58.680> example<00:06:59.000> when<00:06:59.120> the<00:06:59.240> issue<00:06:59.680> you<00:06:59.800> alone 00:07:00.469 --> 00:07:00.479 align:start position:0% for example when the issue you alone 00:07:00.479 --> 00:07:02.589 align:start position:0% for example when the issue you alone they<00:07:00.599> will<00:07:00.840> ask<00:07:01.080> you<00:07:01.199> to<00:07:01.400> KRC<00:07:01.960> yourself<00:07:02.360> using 00:07:02.589 --> 00:07:02.599 align:start position:0% they will ask you to KRC yourself using 00:07:02.599 --> 00:07:05.950 align:start position:0% they will ask you to KRC yourself using your<00:07:02.759> government<00:07:03.160> issued<00:07:03.560> ID<00:07:03.960> and<00:07:04.160> so<00:07:04.360> on<00:07:05.360> um 00:07:05.950 --> 00:07:05.960 align:start position:0% your government issued ID and so on um 00:07:05.960 --> 00:07:07.749 align:start position:0% your government issued ID and so on um this<00:07:06.080> is<00:07:06.199> an<00:07:06.479> advantage<00:07:07.080> because<00:07:07.280> this<00:07:07.440> means 00:07:07.749 --> 00:07:07.759 align:start position:0% this is an advantage because this means 00:07:07.759 --> 00:07:09.390 align:start position:0% this is an advantage because this means that<00:07:07.879> the<00:07:08.000> average<00:07:08.400> person<00:07:08.639> is<00:07:08.800> familiar<00:07:09.240> with 00:07:09.390 --> 00:07:09.400 align:start position:0% that the average person is familiar with 00:07:09.400 --> 00:07:11.309 align:start position:0% that the average person is familiar with them<00:07:09.840> that<00:07:10.000> a<00:07:10.080> lot<00:07:10.199> of<00:07:10.319> people<00:07:10.560> have<00:07:10.800> access<00:07:11.080> to 00:07:11.309 --> 00:07:11.319 align:start position:0% them that a lot of people have access to 00:07:11.319 --> 00:07:14.350 align:start position:0% them that a lot of people have access to these<00:07:11.520> means<00:07:12.080> of<00:07:12.960> uh<00:07:13.199> these<00:07:13.400> modalities 00:07:14.350 --> 00:07:14.360 align:start position:0% these means of uh these modalities 00:07:14.360 --> 00:07:16.510 align:start position:0% these means of uh these modalities they're<00:07:14.599> easily<00:07:15.039> scalable<00:07:15.720> and<00:07:15.840> easy<00:07:16.080> to 00:07:16.510 --> 00:07:16.520 align:start position:0% they're easily scalable and easy to 00:07:16.520 --> 00:07:20.309 align:start position:0% they're easily scalable and easy to implement<00:07:17.520> the<00:07:17.759> downside<00:07:18.440> is<00:07:18.759> that<00:07:19.240> um<00:07:20.199> they 00:07:20.309 --> 00:07:20.319 align:start position:0% implement the downside is that um they 00:07:20.319 --> 00:07:21.670 align:start position:0% implement the downside is that um they are<00:07:20.520> imperfect<00:07:21.080> when<00:07:21.199> it<00:07:21.360> comes<00:07:21.520> to 00:07:21.670 --> 00:07:21.680 align:start position:0% are imperfect when it comes to 00:07:21.680 --> 00:07:24.230 align:start position:0% are imperfect when it comes to uniqueness<00:07:22.680> passports<00:07:23.120> are<00:07:23.319> relatively<00:07:23.919> good 00:07:24.230 --> 00:07:24.240 align:start position:0% uniqueness passports are relatively good 00:07:24.240 --> 00:07:26.350 align:start position:0% uniqueness passports are relatively good but<00:07:24.400> still<00:07:24.680> people<00:07:24.919> have<00:07:25.080> multiple<00:07:25.560> passports 00:07:26.350 --> 00:07:26.360 align:start position:0% but still people have multiple passports 00:07:26.360 --> 00:07:29.629 align:start position:0% but still people have multiple passports and<00:07:26.560> definitely<00:07:27.000> over<00:07:27.560> lifetime<00:07:28.319> people 00:07:29.629 --> 00:07:29.639 align:start position:0% and definitely over lifetime people 00:07:29.639 --> 00:07:30.950 align:start position:0% and definitely over lifetime people renew<00:07:30.120> their 00:07:30.950 --> 00:07:30.960 align:start position:0% renew their 00:07:30.960 --> 00:07:32.869 align:start position:0% renew their passports<00:07:31.960> they<00:07:32.160> also<00:07:32.440> have<00:07:32.639> weak 00:07:32.869 --> 00:07:32.879 align:start position:0% passports they also have weak 00:07:32.879 --> 00:07:34.790 align:start position:0% passports they also have weak inclusivity<00:07:33.599> a<00:07:33.680> lot<00:07:33.800> of<00:07:33.919> people<00:07:34.240> don't<00:07:34.560> have 00:07:34.790 --> 00:07:34.800 align:start position:0% inclusivity a lot of people don't have 00:07:34.800 --> 00:07:37.309 align:start position:0% inclusivity a lot of people don't have access<00:07:35.039> to<00:07:35.240> these<00:07:35.759> means<00:07:36.759> and<00:07:36.960> of<00:07:37.120> course 00:07:37.309 --> 00:07:37.319 align:start position:0% access to these means and of course 00:07:37.319 --> 00:07:39.629 align:start position:0% access to these means and of course there<00:07:37.479> is<00:07:37.599> the<00:07:37.759> central<00:07:38.120> Authority<00:07:38.759> problem 00:07:39.629 --> 00:07:39.639 align:start position:0% there is the central Authority problem 00:07:39.639 --> 00:07:41.270 align:start position:0% there is the central Authority problem we've<00:07:39.840> all<00:07:39.960> heard<00:07:40.120> of<00:07:40.240> sim<00:07:40.479> swapping<00:07:41.080> phone 00:07:41.270 --> 00:07:41.280 align:start position:0% we've all heard of sim swapping phone 00:07:41.280 --> 00:07:43.510 align:start position:0% we've all heard of sim swapping phone numbers<00:07:41.639> kind<00:07:41.759> of<00:07:41.879> suck<00:07:42.240> in<00:07:42.400> general<00:07:42.840> for<00:07:43.240> any 00:07:43.510 --> 00:07:43.520 align:start position:0% numbers kind of suck in general for any 00:07:43.520 --> 00:07:47.309 align:start position:0% numbers kind of suck in general for any kind<00:07:43.720> of<00:07:45.000> authentication<00:07:46.000> it's<00:07:46.159> also<00:07:46.520> active 00:07:47.309 --> 00:07:47.319 align:start position:0% kind of authentication it's also active 00:07:47.319 --> 00:07:49.909 align:start position:0% kind of authentication it's also active um<00:07:47.479> you<00:07:47.639> need<00:07:47.840> to<00:07:48.800> go<00:07:49.039> through<00:07:49.319> this<00:07:49.560> process 00:07:49.909 --> 00:07:49.919 align:start position:0% um you need to go through this process 00:07:49.919 --> 00:07:52.029 align:start position:0% um you need to go through this process you<00:07:50.039> need<00:07:50.199> to<00:07:50.440> actually<00:07:51.199> make<00:07:51.400> sure<00:07:51.680> that<00:07:51.840> the 00:07:52.029 --> 00:07:52.039 align:start position:0% you need to actually make sure that the 00:07:52.039 --> 00:07:55.149 align:start position:0% you need to actually make sure that the person<00:07:52.360> presenting<00:07:53.280> you<00:07:53.599> the<00:07:54.159> passport 00:07:55.149 --> 00:07:55.159 align:start position:0% person presenting you the passport 00:07:55.159 --> 00:07:56.710 align:start position:0% person presenting you the passport matches<00:07:55.960> the 00:07:56.710 --> 00:07:56.720 align:start position:0% matches the 00:07:56.720 --> 00:07:59.230 align:start position:0% matches the document<00:07:57.720> um<00:07:58.280> you<00:07:58.440> also<00:07:58.639> need<00:07:58.759> to<00:07:58.919> make<00:07:59.039> sure 00:07:59.230 --> 00:07:59.240 align:start position:0% document um you also need to make sure 00:07:59.240 --> 00:08:02.110 align:start position:0% document um you also need to make sure that<00:07:59.599> document<00:08:00.000> itself<00:08:00.520> is<00:08:00.680> a<00:08:00.960> valid<00:08:01.400> passport 00:08:02.110 --> 00:08:02.120 align:start position:0% that document itself is a valid passport 00:08:02.120 --> 00:08:04.390 align:start position:0% that document itself is a valid passport and<00:08:02.280> not<00:08:02.520> some<00:08:02.840> copy<00:08:03.680> and<00:08:03.840> this<00:08:04.039> becomes 00:08:04.390 --> 00:08:04.400 align:start position:0% and not some copy and this becomes 00:08:04.400 --> 00:08:05.790 align:start position:0% and not some copy and this becomes substantially<00:08:04.919> harder<00:08:05.199> in<00:08:05.319> the<00:08:05.440> digital 00:08:05.790 --> 00:08:05.800 align:start position:0% substantially harder in the digital 00:08:05.800 --> 00:08:07.710 align:start position:0% substantially harder in the digital domain<00:08:06.120> and<00:08:06.240> a<00:08:06.319> lot<00:08:06.440> of<00:08:06.520> the<00:08:06.639> current 00:08:07.710 --> 00:08:07.720 align:start position:0% domain and a lot of the current 00:08:07.720 --> 00:08:10.270 align:start position:0% domain and a lot of the current solutions<00:08:08.720> could<00:08:08.879> do<00:08:09.039> a<00:08:09.120> better<00:08:09.440> job<00:08:09.720> on<00:08:09.960> on<00:08:10.120> on 00:08:10.270 --> 00:08:10.280 align:start position:0% solutions could do a better job on on on 00:08:10.280 --> 00:08:13.309 align:start position:0% solutions could do a better job on on on these<00:08:10.560> steps<00:08:11.560> and<00:08:12.240> if<00:08:12.360> we<00:08:12.479> don't<00:08:12.720> deploy<00:08:13.120> any 00:08:13.309 --> 00:08:13.319 align:start position:0% these steps and if we don't deploy any 00:08:13.319 --> 00:08:14.950 align:start position:0% these steps and if we don't deploy any kind<00:08:13.440> of<00:08:13.560> zero<00:08:13.879> knowledge<00:08:14.159> proof<00:08:14.479> methods<00:08:14.800> in 00:08:14.950 --> 00:08:14.960 align:start position:0% kind of zero knowledge proof methods in 00:08:14.960 --> 00:08:17.950 align:start position:0% kind of zero knowledge proof methods in here<00:08:15.159> of<00:08:15.280> course<00:08:15.520> it's<00:08:16.240> enormously<00:08:17.240> revealing 00:08:17.950 --> 00:08:17.960 align:start position:0% here of course it's enormously revealing 00:08:17.960 --> 00:08:20.909 align:start position:0% here of course it's enormously revealing in<00:08:18.120> terms<00:08:18.400> of<00:08:18.639> privacy<00:08:19.720> fortunately<00:08:20.720> there 00:08:20.909 --> 00:08:20.919 align:start position:0% in terms of privacy fortunately there 00:08:20.919 --> 00:08:23.510 align:start position:0% in terms of privacy fortunately there are<00:08:21.159> ZK<00:08:21.639> solutions<00:08:22.080> for<00:08:22.280> all<00:08:22.400> of<00:08:22.639> these<00:08:23.319> and 00:08:23.510 --> 00:08:23.520 align:start position:0% are ZK solutions for all of these and 00:08:23.520 --> 00:08:26.710 align:start position:0% are ZK solutions for all of these and you<00:08:23.759> can<00:08:24.159> get<00:08:24.400> them<00:08:24.639> to<00:08:24.840> a<00:08:25.280> very<00:08:25.520> high<00:08:25.840> standard 00:08:26.710 --> 00:08:26.720 align:start position:0% you can get them to a very high standard 00:08:26.720 --> 00:08:29.790 align:start position:0% you can get them to a very high standard which<00:08:26.879> is<00:08:27.199> great 00:08:29.790 --> 00:08:29.800 align:start position:0% which is great 00:08:29.800 --> 00:08:31.550 align:start position:0% which is great now<00:08:29.960> the<00:08:30.080> graph<00:08:30.400> Bas<00:08:30.720> ones<00:08:31.199> their<00:08:31.360> main 00:08:31.550 --> 00:08:31.560 align:start position:0% now the graph Bas ones their main 00:08:31.560 --> 00:08:34.870 align:start position:0% now the graph Bas ones their main strength<00:08:31.879> is<00:08:32.000> it's<00:08:32.479> decentralized<00:08:33.479> that<00:08:33.880> is 00:08:34.870 --> 00:08:34.880 align:start position:0% strength is it's decentralized that is 00:08:34.880 --> 00:08:36.870 align:start position:0% strength is it's decentralized that is the<00:08:35.120> the<00:08:35.360> superpower<00:08:36.039> of<00:08:36.200> this<00:08:36.399> particular 00:08:36.870 --> 00:08:36.880 align:start position:0% the the superpower of this particular 00:08:36.880 --> 00:08:40.630 align:start position:0% the the superpower of this particular class<00:08:37.159> of<00:08:37.680> solutions<00:08:38.680> the<00:08:38.959> downside<00:08:39.719> is<00:08:40.120> that 00:08:40.630 --> 00:08:40.640 align:start position:0% class of solutions the downside is that 00:08:40.640 --> 00:08:42.709 align:start position:0% class of solutions the downside is that uh<00:08:40.880> the<00:08:40.959> main<00:08:41.200> downside<00:08:41.760> is<00:08:42.200> a<00:08:42.320> so-called 00:08:42.709 --> 00:08:42.719 align:start position:0% uh the main downside is a so-called 00:08:42.719 --> 00:08:44.550 align:start position:0% uh the main downside is a so-called click<00:08:43.000> attack<00:08:43.640> where<00:08:43.760> you<00:08:43.919> have<00:08:44.039> a<00:08:44.200> group<00:08:44.399> of 00:08:44.550 --> 00:08:44.560 align:start position:0% click attack where you have a group of 00:08:44.560 --> 00:08:47.190 align:start position:0% click attack where you have a group of bots<00:08:45.360> that<00:08:45.600> keep<00:08:45.839> verifying<00:08:46.519> each<00:08:46.680> other<00:08:47.000> as 00:08:47.190 --> 00:08:47.200 align:start position:0% bots that keep verifying each other as 00:08:47.200 --> 00:08:50.150 align:start position:0% bots that keep verifying each other as real<00:08:47.480> humans<00:08:48.240> so<00:08:48.399> you<00:08:48.560> get<00:08:48.680> a<00:08:48.839> lot<00:08:48.959> of<00:08:49.160> signals 00:08:50.150 --> 00:08:50.160 align:start position:0% real humans so you get a lot of signals 00:08:50.160 --> 00:08:53.269 align:start position:0% real humans so you get a lot of signals on<00:08:50.519> these<00:08:51.320> Bots<00:08:52.320> that<00:08:52.480> they're<00:08:52.680> real<00:08:52.920> humans 00:08:53.269 --> 00:08:53.279 align:start position:0% on these Bots that they're real humans 00:08:53.279 --> 00:08:54.750 align:start position:0% on these Bots that they're real humans and<00:08:53.399> once<00:08:53.600> you<00:08:53.720> have<00:08:53.839> a<00:08:54.000> network<00:08:54.399> like<00:08:54.560> that 00:08:54.750 --> 00:08:54.760 align:start position:0% and once you have a network like that 00:08:54.760 --> 00:08:57.470 align:start position:0% and once you have a network like that it's<00:08:54.959> very<00:08:55.160> hard<00:08:55.360> to<00:08:55.560> get<00:08:55.760> this<00:08:56.480> out<00:08:56.880> of<00:08:57.160> your 00:08:57.470 --> 00:08:57.480 align:start position:0% it's very hard to get this out of your 00:08:57.480 --> 00:09:00.790 align:start position:0% it's very hard to get this out of your graph<00:08:57.800> based<00:08:58.160> system<00:08:59.640> um<00:09:00.240> there's<00:09:00.399> a<00:09:00.560> couple 00:09:00.790 --> 00:09:00.800 align:start position:0% graph based system um there's a couple 00:09:00.800 --> 00:09:02.990 align:start position:0% graph based system um there's a couple of<00:09:00.959> different<00:09:01.360> approaches<00:09:01.920> here<00:09:02.440> social 00:09:02.990 --> 00:09:03.000 align:start position:0% of different approaches here social 00:09:03.000 --> 00:09:04.710 align:start position:0% of different approaches here social graphs<00:09:03.320> is<00:09:03.399> an<00:09:03.560> easy<00:09:03.839> one<00:09:04.040> where<00:09:04.200> you<00:09:04.360> just<00:09:04.560> go 00:09:04.710 --> 00:09:04.720 align:start position:0% graphs is an easy one where you just go 00:09:04.720 --> 00:09:06.790 align:start position:0% graphs is an easy one where you just go to<00:09:04.839> your<00:09:05.000> friends<00:09:05.360> and<00:09:05.959> provide<00:09:06.320> proof<00:09:06.640> to 00:09:06.790 --> 00:09:06.800 align:start position:0% to your friends and provide proof to 00:09:06.800 --> 00:09:08.190 align:start position:0% to your friends and provide proof to each<00:09:07.000> of<00:09:07.200> your<00:09:07.399> friends<00:09:07.720> that<00:09:07.839> they're<00:09:08.040> all 00:09:08.190 --> 00:09:08.200 align:start position:0% each of your friends that they're all 00:09:08.200 --> 00:09:11.910 align:start position:0% each of your friends that they're all real<00:09:08.480> humans<00:09:09.399> and<00:09:10.399> you<00:09:10.640> collect<00:09:11.279> it<00:09:11.480> from<00:09:11.680> your 00:09:11.910 --> 00:09:11.920 align:start position:0% real humans and you collect it from your 00:09:11.920 --> 00:09:13.790 align:start position:0% real humans and you collect it from your friends<00:09:12.320> and<00:09:12.519> this<00:09:12.680> body<00:09:12.959> of<00:09:13.120> evidence<00:09:13.480> builds 00:09:13.790 --> 00:09:13.800 align:start position:0% friends and this body of evidence builds 00:09:13.800 --> 00:09:17.310 align:start position:0% friends and this body of evidence builds up<00:09:14.040> over<00:09:14.279> time<00:09:15.160> other<00:09:15.880> solutions<00:09:16.880> that<00:09:17.000> don't 00:09:17.310 --> 00:09:17.320 align:start position:0% up over time other solutions that don't 00:09:17.320 --> 00:09:19.430 align:start position:0% up over time other solutions that don't require<00:09:17.800> you<00:09:17.920> to<00:09:18.120> reveal<00:09:18.480> your<00:09:18.959> circle<00:09:19.279> of 00:09:19.430 --> 00:09:19.440 align:start position:0% require you to reveal your circle of 00:09:19.440 --> 00:09:22.310 align:start position:0% require you to reveal your circle of friends<00:09:20.440> um<00:09:20.560> are<00:09:20.720> based<00:09:21.000> on<00:09:21.200> video<00:09:21.560> calls 00:09:22.310 --> 00:09:22.320 align:start position:0% friends um are based on video calls 00:09:22.320 --> 00:09:24.670 align:start position:0% friends um are based on video calls where<00:09:22.480> you<00:09:23.160> either<00:09:23.560> post<00:09:23.920> a<00:09:24.120> video<00:09:24.519> of 00:09:24.670 --> 00:09:24.680 align:start position:0% where you either post a video of 00:09:24.680 --> 00:09:26.949 align:start position:0% where you either post a video of yourself<00:09:25.160> online<00:09:26.120> showing<00:09:26.600> that<00:09:26.720> you're<00:09:26.839> a 00:09:26.949 --> 00:09:26.959 align:start position:0% yourself online showing that you're a 00:09:26.959 --> 00:09:29.990 align:start position:0% yourself online showing that you're a real<00:09:27.240> human<00:09:27.600> and<00:09:27.720> then<00:09:27.880> have<00:09:28.079> other<00:09:28.320> people 00:09:29.990 --> 00:09:30.000 align:start position:0% real human and then have other people 00:09:30.000 --> 00:09:32.670 align:start position:0% real human and then have other people uh<00:09:30.200> accept<00:09:30.480> or<00:09:30.640> reject<00:09:31.040> that<00:09:31.720> or<00:09:32.040> you<00:09:32.279> go<00:09:32.440> into 00:09:32.670 --> 00:09:32.680 align:start position:0% uh accept or reject that or you go into 00:09:32.680 --> 00:09:35.430 align:start position:0% uh accept or reject that or you go into Zoom<00:09:33.000> calls<00:09:33.320> with<00:09:33.519> people<00:09:34.519> cross<00:09:34.880> verifying 00:09:35.430 --> 00:09:35.440 align:start position:0% Zoom calls with people cross verifying 00:09:35.440 --> 00:09:37.110 align:start position:0% Zoom calls with people cross verifying each<00:09:35.560> other<00:09:36.079> that<00:09:36.279> they<00:09:36.399> are<00:09:36.560> indeed<00:09:36.839> in<00:09:37.000> this 00:09:37.110 --> 00:09:37.120 align:start position:0% each other that they are indeed in this 00:09:37.120 --> 00:09:40.190 align:start position:0% each other that they are indeed in this Zoom<00:09:37.399> call<00:09:37.600> and<00:09:37.760> indeed<00:09:38.079> are<00:09:38.440> are<00:09:38.640> real<00:09:39.200> humans 00:09:40.190 --> 00:09:40.200 align:start position:0% Zoom call and indeed are are real humans 00:09:40.200 --> 00:09:42.670 align:start position:0% Zoom call and indeed are are real humans and<00:09:40.839> building<00:09:41.200> the<00:09:41.320> graph<00:09:41.640> that<00:09:41.800> way<00:09:42.360> um<00:09:42.600> I 00:09:42.670 --> 00:09:42.680 align:start position:0% and building the graph that way um I 00:09:42.680 --> 00:09:44.630 align:start position:0% and building the graph that way um I think<00:09:42.920> both<00:09:43.120> of<00:09:43.320> these<00:09:43.560> are<00:09:43.760> are<00:09:43.920> very<00:09:44.120> flawed 00:09:44.630 --> 00:09:44.640 align:start position:0% think both of these are are very flawed 00:09:44.640 --> 00:09:47.710 align:start position:0% think both of these are are very flawed ultimately<00:09:45.440> because<00:09:46.440> we<00:09:46.680> have<00:09:46.920> deep<00:09:47.240> fakes 00:09:47.710 --> 00:09:47.720 align:start position:0% ultimately because we have deep fakes 00:09:47.720 --> 00:09:50.550 align:start position:0% ultimately because we have deep fakes it's<00:09:47.959> very<00:09:48.240> easy<00:09:48.640> to<00:09:49.120> nowadays<00:09:49.720> create 00:09:50.550 --> 00:09:50.560 align:start position:0% it's very easy to nowadays create 00:09:50.560 --> 00:09:52.550 align:start position:0% it's very easy to nowadays create realistic<00:09:51.240> video 00:09:52.550 --> 00:09:52.560 align:start position:0% realistic video 00:09:52.560 --> 00:09:55.829 align:start position:0% realistic video calls<00:09:53.560> um<00:09:53.760> it's<00:09:54.000> also<00:09:54.640> just<00:09:54.800> an<00:09:55.040> awkward 00:09:55.829 --> 00:09:55.839 align:start position:0% calls um it's also just an awkward 00:09:55.839 --> 00:09:58.750 align:start position:0% calls um it's also just an awkward non-scalable<00:09:56.959> process<00:09:57.959> um<00:09:58.200> one<00:09:58.399> that<00:09:58.519> I<00:09:58.640> do 00:09:58.750 --> 00:09:58.760 align:start position:0% non-scalable process um one that I do 00:09:58.760 --> 00:10:00.310 align:start position:0% non-scalable process um one that I do want<00:09:58.839> to<00:09:58.959> highlight<00:09:59.560> because<00:09:59.800> I<00:09:59.920> just<00:10:00.079> think 00:10:00.310 --> 00:10:00.320 align:start position:0% want to highlight because I just think 00:10:00.320 --> 00:10:02.509 align:start position:0% want to highlight because I just think this<00:10:00.440> is<00:10:00.600> such<00:10:00.720> a<00:10:00.880> clever<00:10:01.240> solution<00:10:01.959> is<00:10:02.360> um 00:10:02.509 --> 00:10:02.519 align:start position:0% this is such a clever solution is um 00:10:02.519 --> 00:10:05.230 align:start position:0% this is such a clever solution is um simultaneous<00:10:03.240> capture<00:10:03.839> solving<00:10:04.839> so<00:10:05.079> the 00:10:05.230 --> 00:10:05.240 align:start position:0% simultaneous capture solving so the 00:10:05.240 --> 00:10:07.389 align:start position:0% simultaneous capture solving so the captas<00:10:05.680> I<00:10:05.800> mentioned<00:10:06.240> before<00:10:06.720> are<00:10:06.920> designed 00:10:07.389 --> 00:10:07.399 align:start position:0% captas I mentioned before are designed 00:10:07.399 --> 00:10:09.790 align:start position:0% captas I mentioned before are designed such<00:10:07.600> that<00:10:07.720> only<00:10:07.920> humans<00:10:08.240> can<00:10:08.399> solve<00:10:08.720> them<00:10:09.560> now 00:10:09.790 --> 00:10:09.800 align:start position:0% such that only humans can solve them now 00:10:09.800 --> 00:10:12.389 align:start position:0% such that only humans can solve them now if<00:10:10.000> you<00:10:11.000> through<00:10:11.480> a<00:10:11.640> blockchain<00:10:12.000> or<00:10:12.160> some 00:10:12.389 --> 00:10:12.399 align:start position:0% if you through a blockchain or some 00:10:12.399 --> 00:10:14.910 align:start position:0% if you through a blockchain or some other<00:10:12.640> means<00:10:12.959> trigger<00:10:13.680> um<00:10:13.839> let's<00:10:14.040> say<00:10:14.640> five 00:10:14.910 --> 00:10:14.920 align:start position:0% other means trigger um let's say five 00:10:14.920 --> 00:10:17.509 align:start position:0% other means trigger um let's say five people<00:10:15.200> to<00:10:15.399> solve<00:10:15.839> a<00:10:16.000> capture<00:10:16.519> simultaneously 00:10:17.509 --> 00:10:17.519 align:start position:0% people to solve a capture simultaneously 00:10:17.519 --> 00:10:19.509 align:start position:0% people to solve a capture simultaneously now<00:10:17.720> you<00:10:17.920> know<00:10:18.480> that<00:10:18.600> there's<00:10:18.880> at<00:10:19.000> least<00:10:19.279> five 00:10:19.509 --> 00:10:19.519 align:start position:0% now you know that there's at least five 00:10:19.519 --> 00:10:21.430 align:start position:0% now you know that there's at least five different<00:10:19.800> people 00:10:21.430 --> 00:10:21.440 align:start position:0% different people 00:10:21.440 --> 00:10:24.870 align:start position:0% different people there<00:10:22.440> biometric<00:10:23.000> base<00:10:23.360> this<00:10:23.519> is<00:10:23.920> the<00:10:24.480> um<00:10:24.640> the 00:10:24.870 --> 00:10:24.880 align:start position:0% there biometric base this is the um the 00:10:24.880 --> 00:10:26.870 align:start position:0% there biometric base this is the um the strongest<00:10:25.240> approach<00:10:25.920> it<00:10:26.079> gives<00:10:26.240> you<00:10:26.480> near 00:10:26.870 --> 00:10:26.880 align:start position:0% strongest approach it gives you near 00:10:26.880 --> 00:10:28.310 align:start position:0% strongest approach it gives you near perfect<00:10:27.279> uniqueness<00:10:28.079> it<00:10:28.160> is 00:10:28.310 --> 00:10:28.320 align:start position:0% perfect uniqueness it is 00:10:28.320 --> 00:10:29.829 align:start position:0% perfect uniqueness it is non-transferable 00:10:29.829 --> 00:10:29.839 align:start position:0% non-transferable 00:10:29.839 --> 00:10:32.630 align:start position:0% non-transferable you<00:10:30.120> know<00:10:30.519> that<00:10:30.680> it<00:10:30.800> is<00:10:31.200> um<00:10:31.360> this<00:10:31.600> human<00:10:32.399> and 00:10:32.630 --> 00:10:32.640 align:start position:0% you know that it is um this human and 00:10:32.640 --> 00:10:33.870 align:start position:0% you know that it is um this human and this<00:10:32.880> human 00:10:33.870 --> 00:10:33.880 align:start position:0% this human 00:10:33.880 --> 00:10:36.710 align:start position:0% this human cannot<00:10:34.880> give<00:10:35.240> this<00:10:35.519> modality<00:10:36.120> away<00:10:36.399> to<00:10:36.560> some 00:10:36.710 --> 00:10:36.720 align:start position:0% cannot give this modality away to some 00:10:36.720 --> 00:10:39.389 align:start position:0% cannot give this modality away to some other<00:10:37.040> you<00:10:37.320> human<00:10:37.560> or<00:10:37.680> cellid<00:10:38.079> or<00:10:38.200> so<00:10:38.320> on<00:10:39.279> the 00:10:39.389 --> 00:10:39.399 align:start position:0% other you human or cellid or so on the 00:10:39.399 --> 00:10:41.870 align:start position:0% other you human or cellid or so on the weakness<00:10:39.760> is<00:10:39.959> it's<00:10:40.120> immutable<00:10:41.040> it<00:10:41.279> sort<00:10:41.480> of 00:10:41.870 --> 00:10:41.880 align:start position:0% weakness is it's immutable it sort of 00:10:41.880 --> 00:10:44.110 align:start position:0% weakness is it's immutable it sort of sticks<00:10:42.279> to<00:10:42.480> you<00:10:42.680> for<00:10:42.880> your<00:10:43.120> entire<00:10:43.600> life<00:10:43.959> which 00:10:44.110 --> 00:10:44.120 align:start position:0% sticks to you for your entire life which 00:10:44.120 --> 00:10:46.069 align:start position:0% sticks to you for your entire life which might<00:10:44.320> not<00:10:44.680> necessarily<00:10:45.320> be<00:10:45.480> desirable<00:10:46.000> you 00:10:46.069 --> 00:10:46.079 align:start position:0% might not necessarily be desirable you 00:10:46.079 --> 00:10:47.829 align:start position:0% might not necessarily be desirable you might<00:10:46.279> want<00:10:46.399> to<00:10:46.600> have<00:10:46.760> like<00:10:46.880> some<00:10:47.120> ability<00:10:47.519> to 00:10:47.829 --> 00:10:47.839 align:start position:0% might want to have like some ability to 00:10:47.839 --> 00:10:51.030 align:start position:0% might want to have like some ability to reset<00:10:48.839> it<00:10:49.000> also<00:10:49.279> relies<00:10:49.720> on<00:10:50.000> trusted<00:10:50.519> sensor 00:10:51.030 --> 00:10:51.040 align:start position:0% reset it also relies on trusted sensor 00:10:51.040 --> 00:10:53.430 align:start position:0% reset it also relies on trusted sensor if<00:10:51.160> you<00:10:51.279> need<00:10:52.079> a<00:10:52.360> way<00:10:52.600> to<00:10:52.839> capture<00:10:53.200> this 00:10:53.430 --> 00:10:53.440 align:start position:0% if you need a way to capture this 00:10:53.440 --> 00:10:55.430 align:start position:0% if you need a way to capture this biometric<00:10:54.040> information<00:10:54.880> and<00:10:55.160> and<00:10:55.279> it 00:10:55.430 --> 00:10:55.440 align:start position:0% biometric information and and it 00:10:55.440 --> 00:10:57.550 align:start position:0% biometric information and and it requires<00:10:55.920> physical<00:10:56.240> interaction<00:10:57.200> the<00:10:57.320> other 00:10:57.550 --> 00:10:57.560 align:start position:0% requires physical interaction the other 00:10:57.560 --> 00:11:00.389 align:start position:0% requires physical interaction the other thing<00:10:57.760> is<00:10:58.000> the<00:10:58.519> um<00:10:58.880> so<00:10:59.440> false<00:10:59.680> match<00:10:59.959> nonmatch 00:11:00.389 --> 00:11:00.399 align:start position:0% thing is the um so false match nonmatch 00:11:00.399 --> 00:11:03.670 align:start position:0% thing is the um so false match nonmatch rates<00:11:01.240> where<00:11:02.000> faces<00:11:03.000> with<00:11:03.200> the<00:11:03.320> current 00:11:03.670 --> 00:11:03.680 align:start position:0% rates where faces with the current 00:11:03.680 --> 00:11:07.110 align:start position:0% rates where faces with the current algorithms<00:11:04.399> are<00:11:04.639> only<00:11:05.079> unique<00:11:05.680> up<00:11:05.839> to<00:11:06.760> maybe<00:11:07.000> a 00:11:07.110 --> 00:11:07.120 align:start position:0% algorithms are only unique up to maybe a 00:11:07.120 --> 00:11:09.870 align:start position:0% algorithms are only unique up to maybe a million<00:11:07.959> individuals<00:11:08.959> and<00:11:09.200> after<00:11:09.480> that<00:11:09.720> the 00:11:09.870 --> 00:11:09.880 align:start position:0% million individuals and after that the 00:11:09.880 --> 00:11:11.150 align:start position:0% million individuals and after that the algorithms<00:11:10.440> will<00:11:10.560> not<00:11:10.720> be<00:11:10.800> able<00:11:11.000> to 00:11:11.150 --> 00:11:11.160 align:start position:0% algorithms will not be able to 00:11:11.160 --> 00:11:13.069 align:start position:0% algorithms will not be able to distinguish<00:11:11.639> them 00:11:13.069 --> 00:11:13.079 align:start position:0% distinguish them 00:11:13.079 --> 00:11:15.870 align:start position:0% distinguish them anymore<00:11:14.079> um<00:11:14.360> same<00:11:14.600> thing<00:11:14.760> with<00:11:14.959> fingerprints 00:11:15.870 --> 00:11:15.880 align:start position:0% anymore um same thing with fingerprints 00:11:15.880 --> 00:11:17.430 align:start position:0% anymore um same thing with fingerprints they're<00:11:16.120> not<00:11:16.360> as<00:11:16.519> unique<00:11:16.880> as<00:11:16.959> you<00:11:17.079> would<00:11:17.240> want 00:11:17.430 --> 00:11:17.440 align:start position:0% they're not as unique as you would want 00:11:17.440 --> 00:11:20.310 align:start position:0% they're not as unique as you would want them<00:11:17.560> to<00:11:17.720> be<00:11:18.360> irises<00:11:19.120> however<00:11:19.920> have<00:11:20.120> an 00:11:20.310 --> 00:11:20.320 align:start position:0% them to be irises however have an 00:11:20.320 --> 00:11:22.629 align:start position:0% them to be irises however have an enormous<00:11:20.839> amount<00:11:21.079> of<00:11:21.200> entropy<00:11:21.680> in<00:11:21.839> them<00:11:22.360> so 00:11:22.629 --> 00:11:22.639 align:start position:0% enormous amount of entropy in them so 00:11:22.639 --> 00:11:26.069 align:start position:0% enormous amount of entropy in them so they<00:11:22.839> work<00:11:23.519> at<00:11:23.800> a<00:11:24.320> world<00:11:24.800> population<00:11:25.360> scale 00:11:26.069 --> 00:11:26.079 align:start position:0% they work at a world population scale 00:11:26.079 --> 00:11:27.829 align:start position:0% they work at a world population scale and<00:11:26.279> that<00:11:26.360> is<00:11:26.519> the<00:11:26.639> main<00:11:26.880> reason<00:11:27.440> uh<00:11:27.560> World 00:11:27.829 --> 00:11:27.839 align:start position:0% and that is the main reason uh World 00:11:27.839 --> 00:11:29.910 align:start position:0% and that is the main reason uh World went<00:11:28.079> in<00:11:28.200> this<00:11:28.399> direction 00:11:29.910 --> 00:11:29.920 align:start position:0% went in this direction 00:11:29.920 --> 00:11:32.389 align:start position:0% went in this direction now<00:11:30.519> two<00:11:30.839> common<00:11:31.200> Mis<00:11:31.399> misconceptions<00:11:32.160> about 00:11:32.389 --> 00:11:32.399 align:start position:0% now two common Mis misconceptions about 00:11:32.399 --> 00:11:34.590 align:start position:0% now two common Mis misconceptions about Biometrics<00:11:33.040> I<00:11:33.160> do<00:11:33.279> want<00:11:33.440> to<00:11:33.600> address<00:11:34.360> a 00:11:34.590 --> 00:11:34.600 align:start position:0% Biometrics I do want to address a 00:11:34.600 --> 00:11:37.430 align:start position:0% Biometrics I do want to address a biometric<00:11:35.200> is<00:11:35.399> not<00:11:35.600> a<00:11:35.839> private<00:11:36.240> key<00:11:37.079> your 00:11:37.430 --> 00:11:37.440 align:start position:0% biometric is not a private key your 00:11:37.440 --> 00:11:39.829 align:start position:0% biometric is not a private key your fingerprint<00:11:38.279> is<00:11:38.680> in<00:11:38.839> in<00:11:38.959> a<00:11:39.160> sense<00:11:39.440> not<00:11:39.600> a 00:11:39.829 --> 00:11:39.839 align:start position:0% fingerprint is in in a sense not a 00:11:39.839 --> 00:11:42.030 align:start position:0% fingerprint is in in a sense not a secret<00:11:40.440> like<00:11:40.720> you<00:11:40.839> you<00:11:41.000> leave<00:11:41.279> it<00:11:41.480> on<00:11:41.720> every 00:11:42.030 --> 00:11:42.040 align:start position:0% secret like you you leave it on every 00:11:42.040 --> 00:11:43.670 align:start position:0% secret like you you leave it on every glass<00:11:42.480> of<00:11:42.680> every<00:11:42.880> restaurant<00:11:43.320> you've<00:11:43.480> ever 00:11:43.670 --> 00:11:43.680 align:start position:0% glass of every restaurant you've ever 00:11:43.680 --> 00:11:47.110 align:start position:0% glass of every restaurant you've ever been<00:11:43.880> to<00:11:44.680> and<00:11:44.839> this<00:11:44.959> fingerprint<00:11:45.639> is<00:11:45.800> not<00:11:46.160> what 00:11:47.110 --> 00:11:47.120 align:start position:0% been to and this fingerprint is not what 00:11:47.120 --> 00:11:50.790 align:start position:0% been to and this fingerprint is not what is<00:11:47.480> you<00:11:48.399> the<00:11:48.560> thing<00:11:48.880> that<00:11:49.120> authenticates<00:11:50.000> you 00:11:50.790 --> 00:11:50.800 align:start position:0% is you the thing that authenticates you 00:11:50.800 --> 00:11:52.230 align:start position:0% is you the thing that authenticates you is<00:11:50.959> the<00:11:51.160> fact<00:11:51.399> that<00:11:51.600> you<00:11:51.839> have<00:11:52.079> this 00:11:52.230 --> 00:11:52.240 align:start position:0% is the fact that you have this 00:11:52.240 --> 00:11:54.629 align:start position:0% is the fact that you have this fingerprint<00:11:52.839> on<00:11:52.959> a<00:11:53.079> real<00:11:53.480> life<00:11:53.720> finger 00:11:54.629 --> 00:11:54.639 align:start position:0% fingerprint on a real life finger 00:11:54.639 --> 00:11:57.670 align:start position:0% fingerprint on a real life finger attached<00:11:55.040> to<00:11:55.160> a<00:11:55.279> living<00:11:55.560> breathing<00:11:56.519> body<00:11:57.519> the 00:11:57.670 --> 00:11:57.680 align:start position:0% attached to a living breathing body the 00:11:57.680 --> 00:12:00.110 align:start position:0% attached to a living breathing body the second<00:11:57.959> thing<00:11:58.240> is<00:11:58.639> um<00:11:58.839> I<00:11:59.000> res<00:11:59.399> and<00:11:59.519> retinas<00:11:59.959> are 00:12:00.110 --> 00:12:00.120 align:start position:0% second thing is um I res and retinas are 00:12:00.120 --> 00:12:02.310 align:start position:0% second thing is um I res and retinas are not<00:12:00.279> the<00:12:00.399> same<00:12:00.680> thing<00:12:01.440> so<00:12:01.680> please<00:12:01.959> get<00:12:02.120> that 00:12:02.310 --> 00:12:02.320 align:start position:0% not the same thing so please get that 00:12:02.320 --> 00:12:05.030 align:start position:0% not the same thing so please get that right<00:12:02.519> if<00:12:02.600> you<00:12:02.760> criticize 00:12:05.030 --> 00:12:05.040 align:start position:0% right if you criticize 00:12:05.040 --> 00:12:08.750 align:start position:0% right if you criticize World<00:12:06.040> um<00:12:06.600> world's<00:12:07.079> Approach<00:12:07.920> at<00:12:08.040> a<00:12:08.240> high 00:12:08.750 --> 00:12:08.760 align:start position:0% World um world's Approach at a high 00:12:08.760 --> 00:12:11.750 align:start position:0% World um world's Approach at a high level<00:12:09.760> uh<00:12:09.880> we<00:12:10.040> have<00:12:10.160> a<00:12:10.279> tiered<00:12:10.720> system<00:12:11.519> we 00:12:11.750 --> 00:12:11.760 align:start position:0% level uh we have a tiered system we 00:12:11.760 --> 00:12:12.949 align:start position:0% level uh we have a tiered system we recognize<00:12:12.360> that<00:12:12.480> there's<00:12:12.720> different 00:12:12.949 --> 00:12:12.959 align:start position:0% recognize that there's different 00:12:12.959 --> 00:12:14.750 align:start position:0% recognize that there's different trade-offs<00:12:13.519> to<00:12:13.720> these<00:12:14.240> um<00:12:14.399> different 00:12:14.750 --> 00:12:14.760 align:start position:0% trade-offs to these um different 00:12:14.760 --> 00:12:17.670 align:start position:0% trade-offs to these um different modalities<00:12:15.760> and<00:12:15.920> we<00:12:16.120> offer<00:12:16.639> a<00:12:16.880> tier<00:12:17.240> list<00:12:17.519> of 00:12:17.670 --> 00:12:17.680 align:start position:0% modalities and we offer a tier list of 00:12:17.680 --> 00:12:19.670 align:start position:0% modalities and we offer a tier list of what<00:12:17.839> we<00:12:18.000> think<00:12:18.600> covers<00:12:18.959> the<00:12:19.079> whole<00:12:19.279> spectrum 00:12:19.670 --> 00:12:19.680 align:start position:0% what we think covers the whole spectrum 00:12:19.680 --> 00:12:21.750 align:start position:0% what we think covers the whole spectrum of<00:12:19.839> what<00:12:19.959> you<00:12:20.079> might<00:12:20.320> want<00:12:20.880> we<00:12:21.000> have<00:12:21.240> the<00:12:21.560> the 00:12:21.750 --> 00:12:21.760 align:start position:0% of what you might want we have the the 00:12:21.760 --> 00:12:24.910 align:start position:0% of what you might want we have the the orb<00:12:22.440> you<00:12:22.560> see<00:12:22.760> one<00:12:22.959> right<00:12:23.120> there<00:12:23.839> which<00:12:24.040> is<00:12:24.360> a 00:12:24.910 --> 00:12:24.920 align:start position:0% orb you see one right there which is a 00:12:24.920 --> 00:12:27.470 align:start position:0% orb you see one right there which is a um<00:12:25.120> Hardware<00:12:25.519> based<00:12:25.920> biometric<00:12:26.680> Iris<00:12:27.120> based 00:12:27.470 --> 00:12:27.480 align:start position:0% um Hardware based biometric Iris based 00:12:27.480 --> 00:12:29.470 align:start position:0% um Hardware based biometric Iris based system<00:12:28.320> that<00:12:28.480> gives<00:12:28.639> you<00:12:28.800> super<00:12:29.199> High 00:12:29.470 --> 00:12:29.480 align:start position:0% system that gives you super High 00:12:29.480 --> 00:12:33.550 align:start position:0% system that gives you super High guarantees<00:12:30.480> but<00:12:31.320> um<00:12:32.320> you<00:12:32.440> need<00:12:32.639> to<00:12:32.839> go<00:12:33.240> uh<00:12:33.360> find 00:12:33.550 --> 00:12:33.560 align:start position:0% guarantees but um you need to go uh find 00:12:33.560 --> 00:12:35.750 align:start position:0% guarantees but um you need to go uh find an<00:12:33.720> orb<00:12:34.079> in<00:12:34.199> order<00:12:34.399> to<00:12:34.560> sign<00:12:34.800> up<00:12:35.279> we're<00:12:35.560> now 00:12:35.750 --> 00:12:35.760 align:start position:0% an orb in order to sign up we're now 00:12:35.760 --> 00:12:38.949 align:start position:0% an orb in order to sign up we're now rolling<00:12:36.160> out<00:12:36.639> um<00:12:36.839> a<00:12:37.160> ZK<00:12:37.560> NFC<00:12:38.160> passport<00:12:38.600> based 00:12:38.949 --> 00:12:38.959 align:start position:0% rolling out um a ZK NFC passport based 00:12:38.959 --> 00:12:41.230 align:start position:0% rolling out um a ZK NFC passport based system<00:12:39.320> that<00:12:39.480> gives<00:12:39.639> you<00:12:39.839> high<00:12:40.120> privacy<00:12:40.760> and 00:12:41.230 --> 00:12:41.240 align:start position:0% system that gives you high privacy and 00:12:41.240 --> 00:12:44.069 align:start position:0% system that gives you high privacy and can<00:12:41.440> leverage<00:12:42.000> existing<00:12:42.399> national<00:12:42.760> ID<00:12:43.120> system 00:12:44.069 --> 00:12:44.079 align:start position:0% can leverage existing national ID system 00:12:44.079 --> 00:12:47.189 align:start position:0% can leverage existing national ID system and<00:12:44.199> then<00:12:44.399> we<00:12:44.600> have<00:12:45.000> a<00:12:45.440> very<00:12:45.680> low<00:12:46.000> tier<00:12:46.360> system 00:12:47.189 --> 00:12:47.199 align:start position:0% and then we have a very low tier system 00:12:47.199 --> 00:12:49.910 align:start position:0% and then we have a very low tier system that<00:12:47.360> uses<00:12:47.760> the<00:12:47.920> tees<00:12:48.720> in<00:12:48.839> your<00:12:49.040> mobile<00:12:49.399> phones 00:12:49.910 --> 00:12:49.920 align:start position:0% that uses the tees in your mobile phones 00:12:49.920 --> 00:12:51.590 align:start position:0% that uses the tees in your mobile phones to<00:12:50.079> prove<00:12:50.399> that<00:12:50.519> you<00:12:50.639> have<00:12:50.760> a<00:12:50.920> unique<00:12:51.240> mobile 00:12:51.590 --> 00:12:51.600 align:start position:0% to prove that you have a unique mobile 00:12:51.600 --> 00:12:53.910 align:start position:0% to prove that you have a unique mobile device<00:12:52.440> now<00:12:52.880> with<00:12:53.040> that<00:12:53.240> last<00:12:53.519> year<00:12:53.720> you<00:12:53.800> can 00:12:53.910 --> 00:12:53.920 align:start position:0% device now with that last year you can 00:12:53.920 --> 00:12:55.629 align:start position:0% device now with that last year you can nobly<00:12:54.240> see<00:12:54.440> the<00:12:54.600> issue<00:12:54.959> there<00:12:55.279> uh<00:12:55.399> you<00:12:55.480> can 00:12:55.629 --> 00:12:55.639 align:start position:0% nobly see the issue there uh you can 00:12:55.639 --> 00:12:57.949 align:start position:0% nobly see the issue there uh you can just<00:12:55.800> buy<00:12:55.959> more<00:12:56.199> phones<00:12:57.199> um<00:12:57.399> and<00:12:57.560> that<00:12:57.680> is<00:12:57.839> kind 00:12:57.949 --> 00:12:57.959 align:start position:0% just buy more phones um and that is kind 00:12:57.959 --> 00:13:00.110 align:start position:0% just buy more phones um and that is kind of<00:12:58.120> the<00:12:58.279> thing<00:12:58.480> with<00:12:58.639> a<00:12:58.760> tier 00:13:00.110 --> 00:13:00.120 align:start position:0% of the thing with a tier 00:13:00.120 --> 00:13:02.590 align:start position:0% of the thing with a tier system<00:13:01.120> you<00:13:01.279> want<00:13:01.440> to<00:13:01.600> make<00:13:01.800> your<00:13:02.000> tradeoffs 00:13:02.590 --> 00:13:02.600 align:start position:0% system you want to make your tradeoffs 00:13:02.600 --> 00:13:04.269 align:start position:0% system you want to make your tradeoffs as<00:13:02.720> an<00:13:02.880> application<00:13:03.399> developer<00:13:03.880> based<00:13:04.120> on 00:13:04.269 --> 00:13:04.279 align:start position:0% as an application developer based on 00:13:04.279 --> 00:13:06.590 align:start position:0% as an application developer based on what<00:13:04.399> your<00:13:04.519> needs<00:13:04.800> are<00:13:05.160> and<00:13:05.839> how<00:13:06.160> you<00:13:06.279> want<00:13:06.480> the 00:13:06.590 --> 00:13:06.600 align:start position:0% what your needs are and how you want the 00:13:06.600 --> 00:13:09.430 align:start position:0% what your needs are and how you want the onboarding<00:13:07.160> experience<00:13:07.560> to<00:13:07.959> be<00:13:08.959> how<00:13:09.079> did<00:13:09.279> we 00:13:09.430 --> 00:13:09.440 align:start position:0% onboarding experience to be how did we 00:13:09.440 --> 00:13:12.350 align:start position:0% onboarding experience to be how did we implement<00:13:09.959> this<00:13:10.800> so<00:13:11.000> we<00:13:11.160> make<00:13:11.399> use<00:13:11.760> of<00:13:12.240> um 00:13:12.350 --> 00:13:12.360 align:start position:0% implement this so we make use of um 00:13:12.360 --> 00:13:13.269 align:start position:0% implement this so we make use of um modern 00:13:13.269 --> 00:13:13.279 align:start position:0% modern 00:13:13.279 --> 00:13:16.670 align:start position:0% modern cryptography<00:13:14.279> um<00:13:14.800> generally<00:13:15.760> when<00:13:16.040> state<00:13:16.360> is 00:13:16.670 --> 00:13:16.680 align:start position:0% cryptography um generally when state is 00:13:16.680 --> 00:13:20.509 align:start position:0% cryptography um generally when state is local<00:13:17.680> or<00:13:17.920> Global<00:13:18.440> or<00:13:18.760> public<00:13:19.120> or<00:13:19.360> private<00:13:20.360> um 00:13:20.509 --> 00:13:20.519 align:start position:0% local or Global or public or private um 00:13:20.519 --> 00:13:22.870 align:start position:0% local or Global or public or private um there's<00:13:20.839> different<00:13:21.360> things<00:13:21.600> we<00:13:21.720> can<00:13:21.920> do<00:13:22.720> but 00:13:22.870 --> 00:13:22.880 align:start position:0% there's different things we can do but 00:13:22.880 --> 00:13:26.150 align:start position:0% there's different things we can do but we<00:13:23.160> now<00:13:23.399> have<00:13:23.519> a<00:13:23.720> full<00:13:24.120> set<00:13:24.399> of<00:13:24.560> solutions<00:13:25.160> here 00:13:26.150 --> 00:13:26.160 align:start position:0% we now have a full set of solutions here 00:13:26.160 --> 00:13:27.990 align:start position:0% we now have a full set of solutions here we<00:13:26.279> can<00:13:26.600> kind<00:13:26.720> of<00:13:26.880> take<00:13:27.120> any<00:13:27.320> kind<00:13:27.480> of<00:13:27.680> problem 00:13:27.990 --> 00:13:28.000 align:start position:0% we can kind of take any kind of problem 00:13:28.000 --> 00:13:29.670 align:start position:0% we can kind of take any kind of problem and<00:13:28.160> come<00:13:28.320> up<00:13:28.440> with<00:13:28.560> a<00:13:28.639> very<00:13:28.839> Ade 00:13:29.670 --> 00:13:29.680 align:start position:0% and come up with a very Ade 00:13:29.680 --> 00:13:33.030 align:start position:0% and come up with a very Ade solution<00:13:30.680> the<00:13:30.839> high<00:13:31.000> level<00:13:31.320> strategy<00:13:32.079> is<00:13:32.839> we 00:13:33.030 --> 00:13:33.040 align:start position:0% solution the high level strategy is we 00:13:33.040 --> 00:13:35.550 align:start position:0% solution the high level strategy is we take<00:13:33.199> our<00:13:33.600> modality<00:13:34.600> uh<00:13:34.760> this<00:13:34.920> always<00:13:35.199> starts 00:13:35.550 --> 00:13:35.560 align:start position:0% take our modality uh this always starts 00:13:35.560 --> 00:13:38.509 align:start position:0% take our modality uh this always starts with<00:13:35.760> some<00:13:36.000> form<00:13:36.360> of<00:13:36.839> um<00:13:37.079> trusted<00:13:37.560> sensors 00:13:38.509 --> 00:13:38.519 align:start position:0% with some form of um trusted sensors 00:13:38.519 --> 00:13:40.269 align:start position:0% with some form of um trusted sensors either<00:13:38.800> The<00:13:39.040> Trusted<00:13:39.440> sensors<00:13:39.800> are<00:13:39.959> other 00:13:40.269 --> 00:13:40.279 align:start position:0% either The Trusted sensors are other 00:13:40.279 --> 00:13:42.629 align:start position:0% either The Trusted sensors are other humans<00:13:40.560> in<00:13:40.639> the<00:13:40.800> network<00:13:41.800> or<00:13:42.079> The<00:13:42.240> Trusted 00:13:42.629 --> 00:13:42.639 align:start position:0% humans in the network or The Trusted 00:13:42.639 --> 00:13:45.870 align:start position:0% humans in the network or The Trusted sensor<00:13:43.279> is<00:13:43.519> an<00:13:44.079> U<00:13:44.360> um<00:13:44.680> sorry<00:13:44.959> the<00:13:45.360> The<00:13:45.519> Trusted 00:13:45.870 --> 00:13:45.880 align:start position:0% sensor is an U um sorry the The Trusted 00:13:45.880 --> 00:13:48.829 align:start position:0% sensor is an U um sorry the The Trusted sensor<00:13:46.160> is<00:13:46.240> an<00:13:46.360> NFC<00:13:46.920> chip<00:13:47.240> in<00:13:47.399> your<00:13:47.720> passport 00:13:48.829 --> 00:13:48.839 align:start position:0% sensor is an NFC chip in your passport 00:13:48.839 --> 00:13:51.629 align:start position:0% sensor is an NFC chip in your passport or<00:13:49.839> it<00:13:49.959> is<00:13:50.120> the 00:13:51.629 --> 00:13:51.639 align:start position:0% or it is the 00:13:51.639 --> 00:13:55.069 align:start position:0% or it is the orb<00:13:52.639> the<00:13:52.920> or<00:13:53.880> uh<00:13:54.040> orbs<00:13:54.360> are<00:13:54.480> manufactured 00:13:55.069 --> 00:13:55.079 align:start position:0% orb the or uh orbs are manufactured 00:13:55.079 --> 00:13:56.990 align:start position:0% orb the or uh orbs are manufactured they're<00:13:55.320> registered<00:13:55.839> on<00:13:56.120> chain<00:13:56.600> which<00:13:56.720> is<00:13:56.880> how 00:13:56.990 --> 00:13:57.000 align:start position:0% they're registered on chain which is how 00:13:57.000 --> 00:13:58.670 align:start position:0% they're registered on chain which is how you<00:13:57.160> can<00:13:57.399> verify<00:13:57.920> that<00:13:58.040> they<00:13:58.160> are<00:13:58.320> authentic 00:13:58.670 --> 00:13:58.680 align:start position:0% you can verify that they are authentic 00:13:58.680 --> 00:14:01.230 align:start position:0% you can verify that they are authentic through<00:13:58.880> their<00:13:59.160> public<00:13:59.399> key<00:14:00.399> these<00:14:00.759> then 00:14:01.230 --> 00:14:01.240 align:start position:0% through their public key these then 00:14:01.240 --> 00:14:03.350 align:start position:0% through their public key these then produ<00:14:02.160> these<00:14:02.399> then<00:14:02.680> interact<00:14:03.120> with<00:14:03.240> the 00:14:03.350 --> 00:14:03.360 align:start position:0% produ these then interact with the 00:14:03.360 --> 00:14:06.389 align:start position:0% produ these then interact with the user's<00:14:03.759> wallet<00:14:04.560> to<00:14:04.880> produce<00:14:05.680> uh<00:14:05.800> secret 00:14:06.389 --> 00:14:06.399 align:start position:0% user's wallet to produce uh secret 00:14:06.399 --> 00:14:10.629 align:start position:0% user's wallet to produce uh secret shares<00:14:07.399> in<00:14:07.639> zero<00:14:07.959> knowledge<00:14:08.959> so<00:14:09.720> we 00:14:10.629 --> 00:14:10.639 align:start position:0% shares in zero knowledge so we 00:14:10.639 --> 00:14:13.749 align:start position:0% shares in zero knowledge so we know<00:14:11.639> that<00:14:12.079> all<00:14:12.199> of<00:14:12.399> this<00:14:12.560> is<00:14:12.720> done<00:14:13.040> correctly 00:14:13.749 --> 00:14:13.759 align:start position:0% know that all of this is done correctly 00:14:13.759 --> 00:14:16.030 align:start position:0% know that all of this is done correctly and<00:14:13.880> we<00:14:14.000> now<00:14:14.199> have<00:14:14.360> secret<00:14:14.720> shares<00:14:15.279> of<00:14:15.440> the 00:14:16.030 --> 00:14:16.040 align:start position:0% and we now have secret shares of the 00:14:16.040 --> 00:14:18.829 align:start position:0% and we now have secret shares of the modality<00:14:17.040> that<00:14:17.199> we<00:14:17.279> can<00:14:17.480> then<00:14:17.639> send<00:14:18.040> to<00:14:18.560> a 00:14:18.829 --> 00:14:18.839 align:start position:0% modality that we can then send to a 00:14:18.839 --> 00:14:20.550 align:start position:0% modality that we can then send to a private<00:14:19.160> uniqueness<00:14:19.680> solution<00:14:20.240> this<00:14:20.360> is 00:14:20.550 --> 00:14:20.560 align:start position:0% private uniqueness solution this is 00:14:20.560 --> 00:14:22.990 align:start position:0% private uniqueness solution this is implemented<00:14:21.079> using<00:14:21.320> multi-party 00:14:22.990 --> 00:14:23.000 align:start position:0% implemented using multi-party 00:14:23.000 --> 00:14:25.670 align:start position:0% implemented using multi-party computation<00:14:24.000> uh<00:14:24.120> which<00:14:24.279> also<00:14:24.480> runs<00:14:24.759> in<00:14:25.000> tees 00:14:25.670 --> 00:14:25.680 align:start position:0% computation uh which also runs in tees 00:14:25.680 --> 00:14:26.949 align:start position:0% computation uh which also runs in tees which<00:14:25.839> also<00:14:26.040> goes<00:14:26.240> through<00:14:26.399> onchain 00:14:26.949 --> 00:14:26.959 align:start position:0% which also goes through onchain 00:14:26.959 --> 00:14:29.110 align:start position:0% which also goes through onchain governance<00:14:27.959> and<00:14:28.160> that<00:14:28.320> verifies<00:14:28.800> the 00:14:29.110 --> 00:14:29.120 align:start position:0% governance and that verifies the 00:14:29.120 --> 00:14:31.110 align:start position:0% governance and that verifies the uniqueness<00:14:29.839> critically<00:14:30.320> it<00:14:30.519> does<00:14:30.839> this 00:14:31.110 --> 00:14:31.120 align:start position:0% uniqueness critically it does this 00:14:31.120 --> 00:14:33.430 align:start position:0% uniqueness critically it does this without<00:14:31.480> ever<00:14:31.759> seeing<00:14:32.240> the<00:14:32.399> raw<00:14:32.720> modality<00:14:33.320> it 00:14:33.430 --> 00:14:33.440 align:start position:0% without ever seeing the raw modality it 00:14:33.440 --> 00:14:35.150 align:start position:0% without ever seeing the raw modality it only<00:14:33.639> sees<00:14:34.040> encrypted<00:14:34.519> and<00:14:34.720> processes 00:14:35.150 --> 00:14:35.160 align:start position:0% only sees encrypted and processes 00:14:35.160 --> 00:14:37.550 align:start position:0% only sees encrypted and processes encrypted<00:14:35.720> data<00:14:36.120> in<00:14:36.240> the<00:14:36.399> encrypted<00:14:36.839> domain 00:14:37.550 --> 00:14:37.560 align:start position:0% encrypted data in the encrypted domain 00:14:37.560 --> 00:14:38.910 align:start position:0% encrypted data in the encrypted domain which<00:14:37.759> gives<00:14:37.959> you<00:14:38.040> a<00:14:38.160> tremendous<00:14:38.560> amount<00:14:38.800> of 00:14:38.910 --> 00:14:38.920 align:start position:0% which gives you a tremendous amount of 00:14:38.920 --> 00:14:41.629 align:start position:0% which gives you a tremendous amount of privacy<00:14:39.399> here<00:14:40.360> um<00:14:40.519> it<00:14:40.680> really<00:14:40.839> sets<00:14:41.079> a<00:14:41.240> new 00:14:41.629 --> 00:14:41.639 align:start position:0% privacy here um it really sets a new 00:14:41.639 --> 00:14:45.269 align:start position:0% privacy here um it really sets a new standard<00:14:42.639> then<00:14:42.839> we<00:14:43.079> have<00:14:43.800> um<00:14:44.480> as<00:14:44.639> a<00:14:44.880> second 00:14:45.269 --> 00:14:45.279 align:start position:0% standard then we have um as a second 00:14:45.279 --> 00:14:47.870 align:start position:0% standard then we have um as a second layer<00:14:45.600> of<00:14:45.759> defense<00:14:46.160> for<00:14:46.320> your<00:14:46.519> privacy<00:14:47.519> we 00:14:47.870 --> 00:14:47.880 align:start position:0% layer of defense for your privacy we 00:14:47.880 --> 00:14:50.430 align:start position:0% layer of defense for your privacy we don't<00:14:48.320> issue<00:14:48.720> you<00:14:49.120> some<00:14:49.360> sort<00:14:49.560> of<00:14:49.880> ethereum 00:14:50.430 --> 00:14:50.440 align:start position:0% don't issue you some sort of ethereum 00:14:50.440 --> 00:14:52.949 align:start position:0% don't issue you some sort of ethereum address<00:14:50.759> that<00:14:50.880> is<00:14:50.959> now<00:14:51.120> blessed<00:14:51.959> we<00:14:52.480> issue<00:14:52.800> you 00:14:52.949 --> 00:14:52.959 align:start position:0% address that is now blessed we issue you 00:14:52.959 --> 00:14:54.870 align:start position:0% address that is now blessed we issue you an<00:14:53.199> anonymous<00:14:53.759> credential<00:14:54.399> you<00:14:54.519> become<00:14:54.759> a 00:14:54.870 --> 00:14:54.880 align:start position:0% an anonymous credential you become a 00:14:54.880 --> 00:14:57.430 align:start position:0% an anonymous credential you become a member<00:14:55.160> of<00:14:55.279> an<00:14:55.399> onchain<00:14:56.000> set<00:14:56.800> that<00:14:56.959> you<00:14:57.079> can 00:14:57.430 --> 00:14:57.440 align:start position:0% member of an onchain set that you can 00:14:57.440 --> 00:15:01.030 align:start position:0% member of an onchain set that you can zero<00:14:57.800> knowledge<00:14:58.079> proof<00:14:58.440> membership<00:14:59.519> off<00:15:00.519> and 00:15:01.030 --> 00:15:01.040 align:start position:0% zero knowledge proof membership off and 00:15:01.040 --> 00:15:03.829 align:start position:0% zero knowledge proof membership off and this<00:15:02.040> makes<00:15:02.320> it<00:15:02.519> such<00:15:02.920> you<00:15:03.079> cannot<00:15:03.360> track<00:15:03.639> the 00:15:03.829 --> 00:15:03.839 align:start position:0% this makes it such you cannot track the 00:15:03.839 --> 00:15:06.430 align:start position:0% this makes it such you cannot track the behavior<00:15:04.440> of<00:15:04.680> any<00:15:05.399> human<00:15:05.759> that<00:15:05.920> signed<00:15:06.240> up 00:15:06.430 --> 00:15:06.440 align:start position:0% behavior of any human that signed up 00:15:06.440 --> 00:15:10.310 align:start position:0% behavior of any human that signed up through<00:15:06.720> the<00:15:06.880> system<00:15:07.720> you<00:15:08.040> cannot<00:15:09.320> um 00:15:10.310 --> 00:15:10.320 align:start position:0% through the system you cannot um 00:15:10.320 --> 00:15:12.350 align:start position:0% through the system you cannot um associate<00:15:10.920> them<00:15:11.040> to<00:15:11.240> the<00:15:11.600> modality<00:15:12.120> that<00:15:12.240> they 00:15:12.350 --> 00:15:12.360 align:start position:0% associate them to the modality that they 00:15:12.360 --> 00:15:13.829 align:start position:0% associate them to the modality that they signed<00:15:12.639> up<00:15:12.800> with<00:15:12.959> and<00:15:13.079> so 00:15:13.829 --> 00:15:13.839 align:start position:0% signed up with and so 00:15:13.839 --> 00:15:16.790 align:start position:0% signed up with and so on<00:15:14.839> now<00:15:15.360> already<00:15:15.680> covered<00:15:16.000> the<00:15:16.120> orb<00:15:16.519> this<00:15:16.639> is 00:15:16.790 --> 00:15:16.800 align:start position:0% on now already covered the orb this is 00:15:16.800 --> 00:15:18.910 align:start position:0% on now already covered the orb this is our<00:15:17.279> um<00:15:17.440> very<00:15:17.720> sophisticated<00:15:18.399> device<00:15:18.720> there's 00:15:18.910 --> 00:15:18.920 align:start position:0% our um very sophisticated device there's 00:15:18.920 --> 00:15:20.550 align:start position:0% our um very sophisticated device there's other<00:15:19.160> talks<00:15:19.440> about<00:15:19.680> this<00:15:19.839> that<00:15:19.959> I<00:15:20.079> recommend 00:15:20.550 --> 00:15:20.560 align:start position:0% other talks about this that I recommend 00:15:20.560 --> 00:15:22.389 align:start position:0% other talks about this that I recommend go<00:15:20.680> in<00:15:20.800> depth<00:15:20.959> to<00:15:21.079> how<00:15:21.199> it<00:15:21.320> works<00:15:21.959> I<00:15:22.040> do<00:15:22.160> want<00:15:22.279> to 00:15:22.389 --> 00:15:22.399 align:start position:0% go in depth to how it works I do want to 00:15:22.399 --> 00:15:23.590 align:start position:0% go in depth to how it works I do want to highlight<00:15:22.720> a<00:15:22.880> little<00:15:23.120> bit<00:15:23.279> about<00:15:23.440> the 00:15:23.590 --> 00:15:23.600 align:start position:0% highlight a little bit about the 00:15:23.600 --> 00:15:25.710 align:start position:0% highlight a little bit about the challenges<00:15:24.199> of<00:15:24.399> doing<00:15:24.759> this<00:15:25.160> biometric 00:15:25.710 --> 00:15:25.720 align:start position:0% challenges of doing this biometric 00:15:25.720 --> 00:15:27.990 align:start position:0% challenges of doing this biometric uniqueness<00:15:26.320> check<00:15:26.839> in<00:15:27.160> in<00:15:27.320> multiparty 00:15:27.990 --> 00:15:28.000 align:start position:0% uniqueness check in in multiparty 00:15:28.000 --> 00:15:30.069 align:start position:0% uniqueness check in in multiparty compute<00:15:28.319> the<00:15:28.440> scale<00:15:28.720> is<00:15:29.000> enormous<00:15:29.880> we're 00:15:30.069 --> 00:15:30.079 align:start position:0% compute the scale is enormous we're 00:15:30.079 --> 00:15:34.189 align:start position:0% compute the scale is enormous we're talking<00:15:30.360> about<00:15:30.600> a<00:15:30.880> 24<00:15:31.880> Nvidia<00:15:32.399> h100<00:15:33.199> GPU 00:15:34.189 --> 00:15:34.199 align:start position:0% talking about a 24 Nvidia h100 GPU 00:15:34.199 --> 00:15:36.710 align:start position:0% talking about a 24 Nvidia h100 GPU cluster<00:15:35.199> that<00:15:35.680> uh<00:15:35.839> requires<00:15:36.319> almost<00:15:36.519> a 00:15:36.710 --> 00:15:36.720 align:start position:0% cluster that uh requires almost a 00:15:36.720 --> 00:15:39.269 align:start position:0% cluster that uh requires almost a terabyte<00:15:37.319> of<00:15:37.440> GPU<00:15:37.880> memory<00:15:38.319> and<00:15:38.480> terabits<00:15:39.120> of 00:15:39.269 --> 00:15:39.279 align:start position:0% terabyte of GPU memory and terabits of 00:15:39.279 --> 00:15:41.990 align:start position:0% terabyte of GPU memory and terabits of communication<00:15:40.120> bandwidth<00:15:41.120> just<00:15:41.519> s<00:15:41.800> to 00:15:41.990 --> 00:15:42.000 align:start position:0% communication bandwidth just s to 00:15:42.000 --> 00:15:44.350 align:start position:0% communication bandwidth just s to sustain<00:15:42.440> the<00:15:42.560> 8<00:15:42.839> million<00:15:43.240> users<00:15:44.079> that<00:15:44.199> have 00:15:44.350 --> 00:15:44.360 align:start position:0% sustain the 8 million users that have 00:15:44.360 --> 00:15:48.030 align:start position:0% sustain the 8 million users that have signed<00:15:44.680> up<00:15:45.319> at<00:15:45.440> a<00:15:45.600> rate<00:15:45.800> of<00:15:45.959> 10<00:15:46.160> new<00:15:46.399> users<00:15:46.800> per 00:15:48.030 --> 00:15:48.040 align:start position:0% signed up at a rate of 10 new users per 00:15:48.040 --> 00:15:51.910 align:start position:0% signed up at a rate of 10 new users per second<00:15:49.440> multiparty<00:15:50.440> as<00:15:50.560> you<00:15:50.680> may<00:15:50.920> know<00:15:51.720> has 00:15:51.910 --> 00:15:51.920 align:start position:0% second multiparty as you may know has 00:15:51.920 --> 00:15:54.509 align:start position:0% second multiparty as you may know has trust<00:15:52.319> assumptions<00:15:53.279> it<00:15:53.399> is<00:15:53.720> important<00:15:54.279> that 00:15:54.509 --> 00:15:54.519 align:start position:0% trust assumptions it is important that 00:15:54.519 --> 00:15:57.389 align:start position:0% trust assumptions it is important that the<00:15:55.040> nodes<00:15:55.440> are<00:15:55.720> operated<00:15:56.399> by<00:15:56.600> non-colluding 00:15:57.389 --> 00:15:57.399 align:start position:0% the nodes are operated by non-colluding 00:15:57.399 --> 00:15:59.430 align:start position:0% the nodes are operated by non-colluding um<00:15:58.399> entities 00:15:59.430 --> 00:15:59.440 align:start position:0% um entities 00:15:59.440 --> 00:16:02.030 align:start position:0% um entities for<00:15:59.720> that<00:15:59.920> we<00:16:00.040> are<00:16:00.199> working<00:16:00.800> with<00:16:01.240> reliable 00:16:02.030 --> 00:16:02.040 align:start position:0% for that we are working with reliable 00:16:02.040 --> 00:16:04.309 align:start position:0% for that we are working with reliable third<00:16:02.399> parties<00:16:02.880> we<00:16:03.079> found<00:16:03.560> they<00:16:03.759> operate<00:16:04.160> the 00:16:04.309 --> 00:16:04.319 align:start position:0% third parties we found they operate the 00:16:04.319 --> 00:16:07.389 align:start position:0% third parties we found they operate the notes<00:16:04.600> for<00:16:04.800> us<00:16:05.600> the<00:16:06.079> world<00:16:06.480> organizations<00:16:07.240> do 00:16:07.389 --> 00:16:07.399 align:start position:0% notes for us the world organizations do 00:16:07.399 --> 00:16:09.069 align:start position:0% notes for us the world organizations do not<00:16:07.600> have<00:16:07.800> access<00:16:08.040> to<00:16:08.240> these 00:16:09.069 --> 00:16:09.079 align:start position:0% not have access to these 00:16:09.079 --> 00:16:12.350 align:start position:0% not have access to these systems<00:16:10.079> and<00:16:10.680> as<00:16:10.800> a<00:16:11.000> further<00:16:11.519> layer<00:16:11.839> of 00:16:12.350 --> 00:16:12.360 align:start position:0% systems and as a further layer of 00:16:12.360 --> 00:16:15.389 align:start position:0% systems and as a further layer of Defense<00:16:13.360> we<00:16:13.680> have<00:16:14.160> uh<00:16:14.639> we<00:16:14.759> have<00:16:14.959> developed 00:16:15.389 --> 00:16:15.399 align:start position:0% Defense we have uh we have developed 00:16:15.399 --> 00:16:17.269 align:start position:0% Defense we have uh we have developed technology<00:16:15.959> that<00:16:16.120> allows<00:16:16.440> us<00:16:16.560> to<00:16:16.720> run<00:16:17.040> these 00:16:17.269 --> 00:16:17.279 align:start position:0% technology that allows us to run these 00:16:17.279 --> 00:16:23.030 align:start position:0% technology that allows us to run these Cuda<00:16:18.079> MPCs<00:16:19.079> on<00:16:19.600> gpus<00:16:20.600> in<00:16:21.279> tees<00:16:22.279> so<00:16:22.519> inside 00:16:23.030 --> 00:16:23.040 align:start position:0% Cuda MPCs on gpus in tees so inside 00:16:23.040 --> 00:16:25.870 align:start position:0% Cuda MPCs on gpus in tees so inside trusted<00:16:23.480> execution<00:16:24.480> environments<00:16:25.480> so<00:16:25.720> that 00:16:25.870 --> 00:16:25.880 align:start position:0% trusted execution environments so that 00:16:25.880 --> 00:16:27.990 align:start position:0% trusted execution environments so that they<00:16:26.040> can<00:16:26.319> prove<00:16:27.079> that<00:16:27.199> they're<00:16:27.399> all<00:16:27.639> running 00:16:27.990 --> 00:16:28.000 align:start position:0% they can prove that they're all running 00:16:28.000 --> 00:16:30.670 align:start position:0% they can prove that they're all running the<00:16:28.199> pro<00:16:28.519> protocol<00:16:29.120> honestly<00:16:30.000> and<00:16:30.160> they<00:16:30.319> cross 00:16:30.670 --> 00:16:30.680 align:start position:0% the pro protocol honestly and they cross 00:16:30.680 --> 00:16:32.470 align:start position:0% the pro protocol honestly and they cross verify<00:16:31.199> each<00:16:31.399> other<00:16:31.720> before<00:16:31.959> they<00:16:32.160> even 00:16:32.470 --> 00:16:32.480 align:start position:0% verify each other before they even 00:16:32.480 --> 00:16:35.230 align:start position:0% verify each other before they even initiate<00:16:33.000> the<00:16:33.519> protocol<00:16:34.519> then<00:16:34.680> the<00:16:34.880> question 00:16:35.230 --> 00:16:35.240 align:start position:0% initiate the protocol then the question 00:16:35.240 --> 00:16:37.350 align:start position:0% initiate the protocol then the question is<00:16:35.800> okay<00:16:36.000> what<00:16:36.279> protocols<00:16:36.720> are<00:16:36.920> they<00:16:37.079> allowed 00:16:37.350 --> 00:16:37.360 align:start position:0% is okay what protocols are they allowed 00:16:37.360 --> 00:16:39.670 align:start position:0% is okay what protocols are they allowed to<00:16:37.519> run<00:16:38.279> can<00:16:38.440> they<00:16:38.600> do<00:16:38.720> a<00:16:38.839> uniqueness<00:16:39.319> Check 00:16:39.670 --> 00:16:39.680 align:start position:0% to run can they do a uniqueness Check 00:16:39.680 --> 00:16:42.069 align:start position:0% to run can they do a uniqueness Check Yes<00:16:40.240> um<00:16:40.600> maybe<00:16:40.920> in<00:16:41.000> the<00:16:41.120> future<00:16:41.480> we<00:16:41.600> want<00:16:41.759> other 00:16:42.069 --> 00:16:42.079 align:start position:0% Yes um maybe in the future we want other 00:16:42.079 --> 00:16:44.470 align:start position:0% Yes um maybe in the future we want other functionality<00:16:42.759> we<00:16:42.839> want<00:16:43.800> have<00:16:44.040> people<00:16:44.319> the 00:16:44.470 --> 00:16:44.480 align:start position:0% functionality we want have people the 00:16:44.480 --> 00:16:46.030 align:start position:0% functionality we want have people the ability<00:16:44.920> to<00:16:45.120> recover<00:16:45.480> their<00:16:45.720> accounts 00:16:46.030 --> 00:16:46.040 align:start position:0% ability to recover their accounts 00:16:46.040 --> 00:16:48.430 align:start position:0% ability to recover their accounts through<00:16:46.240> a<00:16:46.360> biometric<00:16:46.920> for<00:16:47.279> example<00:16:48.279> that 00:16:48.430 --> 00:16:48.440 align:start position:0% through a biometric for example that 00:16:48.440 --> 00:16:50.749 align:start position:0% through a biometric for example that requires<00:16:48.839> some<00:16:49.000> form<00:16:49.160> of<00:16:49.600> governance<00:16:50.600> that 00:16:50.749 --> 00:16:50.759 align:start position:0% requires some form of governance that 00:16:50.759 --> 00:16:54.430 align:start position:0% requires some form of governance that can<00:16:51.000> then<00:16:51.240> onchain<00:16:52.240> sign<00:16:52.600> off<00:16:53.560> on<00:16:54.160> what<00:16:54.279> are 00:16:54.430 --> 00:16:54.440 align:start position:0% can then onchain sign off on what are 00:16:54.440 --> 00:16:56.790 align:start position:0% can then onchain sign off on what are the<00:16:54.639> allowed<00:16:55.199> protocols<00:16:55.680> to<00:16:55.839> run<00:16:56.240> which 00:16:56.790 --> 00:16:56.800 align:start position:0% the allowed protocols to run which 00:16:56.800 --> 00:16:59.949 align:start position:0% the allowed protocols to run which protocols<00:16:57.800> meet<00:16:58.480> the 00:16:59.949 --> 00:16:59.959 align:start position:0% protocols meet the 00:16:59.959 --> 00:17:02.590 align:start position:0% protocols meet the criteria<00:17:00.639> for<00:17:00.920> privacy<00:17:01.800> and<00:17:01.920> the<00:17:02.079> commitments 00:17:02.590 --> 00:17:02.600 align:start position:0% criteria for privacy and the commitments 00:17:02.600 --> 00:17:05.630 align:start position:0% criteria for privacy and the commitments made<00:17:02.800> to<00:17:02.959> the<00:17:03.480> users<00:17:04.480> so<00:17:04.720> this<00:17:04.880> is<00:17:05.480> where 00:17:05.630 --> 00:17:05.640 align:start position:0% made to the users so this is where 00:17:05.640 --> 00:17:08.029 align:start position:0% made to the users so this is where Modern<00:17:06.079> cryptography<00:17:07.079> and<00:17:07.319> ethereum 00:17:08.029 --> 00:17:08.039 align:start position:0% Modern cryptography and ethereum 00:17:08.039 --> 00:17:10.429 align:start position:0% Modern cryptography and ethereum specifically<00:17:08.760> programmable<00:17:09.360> consensus<00:17:10.199> are 00:17:10.429 --> 00:17:10.439 align:start position:0% specifically programmable consensus are 00:17:10.439 --> 00:17:13.150 align:start position:0% specifically programmable consensus are critical<00:17:10.839> in<00:17:11.000> making<00:17:11.240> all<00:17:11.360> of<00:17:11.520> this<00:17:12.000> work<00:17:13.000> now 00:17:13.150 --> 00:17:13.160 align:start position:0% critical in making all of this work now 00:17:13.160 --> 00:17:16.549 align:start position:0% critical in making all of this work now to<00:17:13.439> summarize<00:17:14.439> World<00:17:14.799> ID<00:17:15.280> offers<00:17:15.640> biometric 00:17:16.549 --> 00:17:16.559 align:start position:0% to summarize World ID offers biometric 00:17:16.559 --> 00:17:19.789 align:start position:0% to summarize World ID offers biometric passport<00:17:17.559> and<00:17:17.919> device<00:17:18.439> based<00:17:19.280> proof<00:17:19.559> of 00:17:19.789 --> 00:17:19.799 align:start position:0% passport and device based proof of 00:17:19.799 --> 00:17:22.470 align:start position:0% passport and device based proof of personhood<00:17:20.360> tiers<00:17:21.360> you<00:17:21.559> as<00:17:21.679> an<00:17:21.839> app<00:17:22.079> developer 00:17:22.470 --> 00:17:22.480 align:start position:0% personhood tiers you as an app developer 00:17:22.480 --> 00:17:25.069 align:start position:0% personhood tiers you as an app developer can<00:17:22.640> integrate<00:17:23.160> this<00:17:24.160> depending<00:17:24.559> on<00:17:24.679> your 00:17:25.069 --> 00:17:25.079 align:start position:0% can integrate this depending on your 00:17:25.079 --> 00:17:27.870 align:start position:0% can integrate this depending on your needs<00:17:26.079> we<00:17:26.400> implemented<00:17:26.959> all<00:17:27.120> of<00:17:27.360> these<00:17:27.600> such 00:17:27.870 --> 00:17:27.880 align:start position:0% needs we implemented all of these such 00:17:27.880 --> 00:17:30.070 align:start position:0% needs we implemented all of these such that<00:17:28.039> the<00:17:28.199> modality<00:17:29.039> actual<00:17:29.280> underlying 00:17:30.070 --> 00:17:30.080 align:start position:0% that the modality actual underlying 00:17:30.080 --> 00:17:33.510 align:start position:0% that the modality actual underlying information<00:17:31.080> never<00:17:31.440> leaves<00:17:31.880> the<00:17:32.080> user<00:17:33.039> no<00:17:33.200> one 00:17:33.510 --> 00:17:33.520 align:start position:0% information never leaves the user no one 00:17:33.520 --> 00:17:36.230 align:start position:0% information never leaves the user no one outside<00:17:33.960> of<00:17:34.120> the<00:17:34.360> user<00:17:35.360> learns<00:17:35.799> about<00:17:36.000> the 00:17:36.230 --> 00:17:36.240 align:start position:0% outside of the user learns about the 00:17:36.240 --> 00:17:38.710 align:start position:0% outside of the user learns about the passwort<00:17:37.000> learns<00:17:37.400> about<00:17:37.640> the<00:17:37.799> iris<00:17:38.480> or 00:17:38.710 --> 00:17:38.720 align:start position:0% passwort learns about the iris or 00:17:38.720 --> 00:17:41.789 align:start position:0% passwort learns about the iris or anything<00:17:39.559> else<00:17:40.559> and<00:17:40.720> then<00:17:40.880> we<00:17:41.039> have<00:17:41.240> this 00:17:41.789 --> 00:17:41.799 align:start position:0% anything else and then we have this 00:17:41.799 --> 00:17:43.950 align:start position:0% anything else and then we have this additional<00:17:42.400> layer<00:17:42.880> of<00:17:43.039> zero<00:17:43.360> knowledge<00:17:43.640> based 00:17:43.950 --> 00:17:43.960 align:start position:0% additional layer of zero knowledge based 00:17:43.960 --> 00:17:46.750 align:start position:0% additional layer of zero knowledge based anonymization<00:17:44.880> on<00:17:45.039> each<00:17:45.320> use<00:17:46.039> so<00:17:46.240> even<00:17:46.480> if<00:17:46.600> you 00:17:46.750 --> 00:17:46.760 align:start position:0% anonymization on each use so even if you 00:17:46.760 --> 00:17:49.110 align:start position:0% anonymization on each use so even if you have<00:17:46.880> a<00:17:47.080> dowo<00:17:47.919> where<00:17:48.039> you<00:17:48.280> have<00:17:48.480> a<00:17:48.640> one<00:17:48.840> person 00:17:49.110 --> 00:17:49.120 align:start position:0% have a dowo where you have a one person 00:17:49.120 --> 00:17:51.710 align:start position:0% have a dowo where you have a one person one<00:17:49.400> phot<00:17:50.400> you<00:17:50.520> will<00:17:50.760> not<00:17:50.919> be<00:17:51.080> able<00:17:51.280> to<00:17:51.440> track 00:17:51.710 --> 00:17:51.720 align:start position:0% one phot you will not be able to track 00:17:51.720 --> 00:17:53.909 align:start position:0% one phot you will not be able to track voting<00:17:52.160> patterns<00:17:52.480> of<00:17:52.640> users<00:17:53.160> each<00:17:53.360> vote<00:17:53.679> is 00:17:53.909 --> 00:17:53.919 align:start position:0% voting patterns of users each vote is 00:17:53.919 --> 00:17:56.310 align:start position:0% voting patterns of users each vote is individually<00:17:54.679> unique<00:17:55.480> by 00:17:56.310 --> 00:17:56.320 align:start position:0% individually unique by 00:17:56.320 --> 00:17:58.549 align:start position:0% individually unique by default<00:17:57.320> but<00:17:57.520> of<00:17:57.640> course<00:17:57.880> as<00:17:58.000> an<00:17:58.159> application 00:17:58.549 --> 00:17:58.559 align:start position:0% default but of course as an application 00:17:58.559 --> 00:18:01.669 align:start position:0% default but of course as an application Dev<00:17:58.840> developer<00:17:59.200> you<00:17:59.360> can<00:18:00.000> ask<00:18:00.240> the<00:18:00.559> user<00:18:01.559> if 00:18:01.669 --> 00:18:01.679 align:start position:0% Dev developer you can ask the user if 00:18:01.679 --> 00:18:03.669 align:start position:0% Dev developer you can ask the user if you<00:18:01.799> want<00:18:02.039> different<00:18:02.360> Behavior 00:18:03.669 --> 00:18:03.679 align:start position:0% you want different Behavior 00:18:03.679 --> 00:18:08.590 align:start position:0% you want different Behavior here<00:18:04.679> now<00:18:05.280> covering<00:18:05.640> some<00:18:05.919> next<00:18:06.720> steps<00:18:07.720> um 00:18:08.590 --> 00:18:08.600 align:start position:0% here now covering some next steps um 00:18:08.600 --> 00:18:10.590 align:start position:0% here now covering some next steps um we've<00:18:08.880> recently<00:18:09.280> rolled<00:18:09.640> out<00:18:09.799> mini<00:18:10.200> apps 00:18:10.590 --> 00:18:10.600 align:start position:0% we've recently rolled out mini apps 00:18:10.600 --> 00:18:13.870 align:start position:0% we've recently rolled out mini apps which<00:18:10.799> is<00:18:11.799> a<00:18:12.039> good<00:18:12.360> way<00:18:12.720> for<00:18:13.120> people<00:18:13.400> that<00:18:13.640> have 00:18:13.870 --> 00:18:13.880 align:start position:0% which is a good way for people that have 00:18:13.880 --> 00:18:16.390 align:start position:0% which is a good way for people that have a<00:18:14.159> a<00:18:14.360> a<00:18:14.640> a<00:18:14.880> use<00:18:15.280> case<00:18:15.480> that<00:18:15.640> requires<00:18:16.000> proof<00:18:16.240> of 00:18:16.390 --> 00:18:16.400 align:start position:0% a a a a use case that requires proof of 00:18:16.400 --> 00:18:18.390 align:start position:0% a a a a use case that requires proof of personhood<00:18:17.080> to<00:18:17.320> immediately<00:18:17.840> reach<00:18:18.200> an 00:18:18.390 --> 00:18:18.400 align:start position:0% personhood to immediately reach an 00:18:18.400 --> 00:18:21.270 align:start position:0% personhood to immediately reach an audience<00:18:18.799> of<00:18:19.480> millions<00:18:20.480> um<00:18:20.720> as<00:18:20.799> I<00:18:20.919> mentioned 00:18:21.270 --> 00:18:21.280 align:start position:0% audience of millions um as I mentioned 00:18:21.280 --> 00:18:23.789 align:start position:0% audience of millions um as I mentioned we<00:18:21.440> have<00:18:21.600> World<00:18:21.919> chain<00:18:22.280> which<00:18:22.400> is<00:18:22.480> our<00:18:22.640> L2<00:18:23.320> that 00:18:23.789 --> 00:18:23.799 align:start position:0% we have World chain which is our L2 that 00:18:23.799 --> 00:18:26.870 align:start position:0% we have World chain which is our L2 that users<00:18:24.280> by<00:18:24.480> default<00:18:24.799> get<00:18:24.960> an<00:18:25.200> account<00:18:25.480> on<00:18:26.440> and 00:18:26.870 --> 00:18:26.880 align:start position:0% users by default get an account on and 00:18:26.880 --> 00:18:30.510 align:start position:0% users by default get an account on and it<00:18:27.280> it<00:18:27.440> is<00:18:27.919> um<00:18:28.200> experimen<00:18:29.200> with<00:18:29.760> ways<00:18:30.080> that<00:18:30.240> we 00:18:30.510 --> 00:18:30.520 align:start position:0% it it is um experimen with ways that we 00:18:30.520 --> 00:18:33.830 align:start position:0% it it is um experimen with ways that we can<00:18:30.840> integrate<00:18:31.840> individuals<00:18:32.480> and<00:18:32.840> humanness 00:18:33.830 --> 00:18:33.840 align:start position:0% can integrate individuals and humanness 00:18:33.840 --> 00:18:37.390 align:start position:0% can integrate individuals and humanness in<00:18:34.120> how<00:18:34.799> sequencers<00:18:36.120> prioritize<00:18:37.120> uh<00:18:37.240> the 00:18:37.390 --> 00:18:37.400 align:start position:0% in how sequencers prioritize uh the 00:18:37.400 --> 00:18:40.149 align:start position:0% in how sequencers prioritize uh the transactions<00:18:37.960> and<00:18:38.159> how<00:18:38.280> fees<00:18:38.600> are<00:18:39.159> allocated 00:18:40.149 --> 00:18:40.159 align:start position:0% transactions and how fees are allocated 00:18:40.159 --> 00:18:42.190 align:start position:0% transactions and how fees are allocated we're<00:18:40.360> currently<00:18:40.720> working<00:18:41.080> hard<00:18:41.360> on<00:18:41.679> in 00:18:42.190 --> 00:18:42.200 align:start position:0% we're currently working hard on in 00:18:42.200 --> 00:18:43.789 align:start position:0% we're currently working hard on in improving<00:18:42.600> the<00:18:42.760> technology<00:18:43.120> of<00:18:43.240> client<00:18:43.640> side 00:18:43.789 --> 00:18:43.799 align:start position:0% improving the technology of client side 00:18:43.799 --> 00:18:46.390 align:start position:0% improving the technology of client side proving<00:18:44.760> to<00:18:44.919> get<00:18:45.200> really<00:18:45.480> fast<00:18:45.799> client<00:18:46.240> side 00:18:46.390 --> 00:18:46.400 align:start position:0% proving to get really fast client side 00:18:46.400 --> 00:18:48.470 align:start position:0% proving to get really fast client side proving<00:18:46.880> so<00:18:47.080> on<00:18:47.360> device<00:18:47.720> on<00:18:47.880> on<00:18:48.000> your<00:18:48.159> mobile 00:18:48.470 --> 00:18:48.480 align:start position:0% proving so on device on on your mobile 00:18:48.480 --> 00:18:50.789 align:start position:0% proving so on device on on your mobile device<00:18:48.960> producing<00:18:49.320> zero<00:18:49.559> knowledge<00:18:49.840> proofs 00:18:50.789 --> 00:18:50.799 align:start position:0% device producing zero knowledge proofs 00:18:50.799 --> 00:18:52.470 align:start position:0% device producing zero knowledge proofs and<00:18:50.919> we<00:18:51.039> want<00:18:51.320> this<00:18:51.600> because<00:18:51.880> there<00:18:52.000> is<00:18:52.120> a<00:18:52.280> big 00:18:52.470 --> 00:18:52.480 align:start position:0% and we want this because there is a big 00:18:52.480 --> 00:18:54.950 align:start position:0% and we want this because there is a big future<00:18:53.039> in<00:18:53.200> doing<00:18:53.600> programmable<00:18:54.559> zero 00:18:54.950 --> 00:18:54.960 align:start position:0% future in doing programmable zero 00:18:54.960 --> 00:18:58.149 align:start position:0% future in doing programmable zero knowledge<00:18:55.600> identity<00:18:56.600> meaning<00:18:57.080> that<00:18:57.320> not<00:18:57.480> only 00:18:58.149 --> 00:18:58.159 align:start position:0% knowledge identity meaning that not only 00:18:58.159 --> 00:19:00.029 align:start position:0% knowledge identity meaning that not only can<00:18:58.280> you<00:18:58.440> prove<00:18:58.799> Pro<00:18:58.960> that<00:18:59.039> you're<00:18:59.159> a<00:18:59.320> unique 00:19:00.029 --> 00:19:00.039 align:start position:0% can you prove Pro that you're a unique 00:19:00.039 --> 00:19:02.149 align:start position:0% can you prove Pro that you're a unique person<00:19:00.720> but<00:19:00.840> you<00:19:00.960> can<00:19:01.120> prove<00:19:01.400> things<00:19:01.799> about 00:19:02.149 --> 00:19:02.159 align:start position:0% person but you can prove things about 00:19:02.159 --> 00:19:04.669 align:start position:0% person but you can prove things about yourself<00:19:02.640> you<00:19:02.760> can<00:19:03.000> prove<00:19:03.440> that<00:19:03.559> you're<00:19:04.400> of<00:19:04.520> a 00:19:04.669 --> 00:19:04.679 align:start position:0% yourself you can prove that you're of a 00:19:04.679 --> 00:19:06.909 align:start position:0% yourself you can prove that you're of a certain<00:19:05.000> nationality<00:19:05.679> you<00:19:05.960> are<00:19:06.360> not<00:19:06.559> of<00:19:06.760> a 00:19:06.909 --> 00:19:06.919 align:start position:0% certain nationality you are not of a 00:19:06.919 --> 00:19:09.990 align:start position:0% certain nationality you are not of a certain<00:19:07.240> nationality<00:19:07.960> or<00:19:08.880> um<00:19:09.200> of<00:19:09.440> a<00:19:09.640> certain 00:19:09.990 --> 00:19:10.000 align:start position:0% certain nationality or um of a certain 00:19:10.000 --> 00:19:12.590 align:start position:0% certain nationality or um of a certain age<00:19:10.360> and<00:19:10.520> so<00:19:10.679> on<00:19:11.400> without<00:19:11.799> revealing<00:19:12.320> anything 00:19:12.590 --> 00:19:12.600 align:start position:0% age and so on without revealing anything 00:19:12.600 --> 00:19:14.990 align:start position:0% age and so on without revealing anything else<00:19:12.919> about 00:19:14.990 --> 00:19:15.000 align:start position:0% else about 00:19:15.000 --> 00:19:18.430 align:start position:0% else about yourself<00:19:16.000> um<00:19:16.280> and<00:19:16.440> with<00:19:16.640> that<00:19:16.880> I<00:19:16.960> want<00:19:17.200> to<00:19:18.200> open 00:19:18.430 --> 00:19:18.440 align:start position:0% yourself um and with that I want to open 00:19:18.440 --> 00:19:25.950 align:start position:0% yourself um and with that I want to open the<00:19:18.600> floor<00:19:18.880> for<00:19:19.320> any<00:19:19.559> questions<00:19:20.360> thank 00:19:25.950 --> 00:19:25.960 align:start position:0% 00:19:25.960 --> 00:19:28.710 align:start position:0% you<00:19:26.960> all<00:19:27.120> right<00:19:27.440> thank<00:19:27.640> you<00:19:28.039> gu<00:19:28.360> thank<00:19:28.520> you 00:19:28.710 --> 00:19:28.720 align:start position:0% you all right thank you gu thank you 00:19:28.720 --> 00:19:30.789 align:start position:0% you all right thank you gu thank you thank<00:19:28.840> you<00:19:29.039> so<00:19:29.240> much<00:19:29.480> for<00:19:29.799> the<00:19:30.000> amazing<00:19:30.440> talk 00:19:30.789 --> 00:19:30.799 align:start position:0% thank you so much for the amazing talk 00:19:30.799 --> 00:19:34.590 align:start position:0% thank you so much for the amazing talk we<00:19:30.919> do<00:19:31.280> have<00:19:31.840> five<00:19:32.280> minutes<00:19:33.280> to<00:19:33.799> go<00:19:34.039> over<00:19:34.400> some 00:19:34.590 --> 00:19:34.600 align:start position:0% we do have five minutes to go over some 00:19:34.600 --> 00:19:36.950 align:start position:0% we do have five minutes to go over some of<00:19:34.760> the<00:19:34.960> questions<00:19:35.520> that<00:19:35.720> people<00:19:36.000> submitted 00:19:36.950 --> 00:19:36.960 align:start position:0% of the questions that people submitted 00:19:36.960 --> 00:19:38.870 align:start position:0% of the questions that people submitted so<00:19:37.400> it<00:19:37.480> would<00:19:37.640> be<00:19:37.760> great<00:19:38.000> if<00:19:38.120> you<00:19:38.280> can<00:19:38.480> come 00:19:38.870 --> 00:19:38.880 align:start position:0% so it would be great if you can come 00:19:38.880 --> 00:19:43.549 align:start position:0% so it would be great if you can come here<00:19:39.159> in<00:19:39.280> the<00:19:39.840> center<00:19:40.840> yes<00:19:41.720> so<00:19:42.000> let's 00:19:43.549 --> 00:19:43.559 align:start position:0% here in the center yes so let's 00:19:43.559 --> 00:19:47.110 align:start position:0% here in the center yes so let's go<00:19:44.559> from<00:19:44.840> the<00:19:45.039> very<00:19:45.799> first<00:19:46.039> one<00:19:46.280> at<00:19:46.400> the<00:19:46.600> top 00:19:47.110 --> 00:19:47.120 align:start position:0% go from the very first one at the top 00:19:47.120 --> 00:19:49.830 align:start position:0% go from the very first one at the top what<00:19:47.240> if<00:19:47.440> human<00:19:47.840> creates<00:19:48.240> a<00:19:48.520> proof<00:19:49.280> and<00:19:49.440> sells 00:19:49.830 --> 00:19:49.840 align:start position:0% what if human creates a proof and sells 00:19:49.840 --> 00:19:53.789 align:start position:0% what if human creates a proof and sells it<00:19:50.000> to<00:19:50.400> AI<00:19:51.400> as<00:19:51.600> there's<00:19:51.960> no<00:19:52.280> identity<00:19:52.960> attached 00:19:53.789 --> 00:19:53.799 align:start position:0% it to AI as there's no identity attached 00:19:53.799 --> 00:19:56.270 align:start position:0% it to AI as there's no identity attached and<00:19:54.039> it's<00:19:54.240> zero<00:19:54.559> knowledge<00:19:54.960> proof<00:19:55.520> there's<00:19:55.919> no 00:19:56.270 --> 00:19:56.280 align:start position:0% and it's zero knowledge proof there's no 00:19:56.280 --> 00:19:58.990 align:start position:0% and it's zero knowledge proof there's no consequence<00:19:56.919> to<00:19:57.080> sell<00:19:57.400> the<00:19:57.559> proof<00:19:58.120> or<00:19:58.400> key<00:19:58.760> is 00:19:58.990 --> 00:19:59.000 align:start position:0% consequence to sell the proof or key is 00:19:59.000 --> 00:20:00.590 align:start position:0% consequence to sell the proof or key is associated<00:19:59.799> with 00:20:00.590 --> 00:20:00.600 align:start position:0% associated with 00:20:00.600 --> 00:20:03.350 align:start position:0% associated with it<00:20:01.600> that<00:20:01.760> is<00:20:01.960> correct<00:20:02.720> um<00:20:02.960> and<00:20:03.080> that<00:20:03.200> is 00:20:03.350 --> 00:20:03.360 align:start position:0% it that is correct um and that is 00:20:03.360 --> 00:20:05.510 align:start position:0% it that is correct um and that is intentional<00:20:04.159> like<00:20:04.360> I<00:20:04.520> said<00:20:04.840> this<00:20:04.960> is<00:20:05.120> not<00:20:05.280> a 00:20:05.510 --> 00:20:05.520 align:start position:0% intentional like I said this is not a 00:20:05.520 --> 00:20:09.110 align:start position:0% intentional like I said this is not a capture<00:20:06.520> this<00:20:07.159> is<00:20:08.159> uh<00:20:08.280> you're<00:20:08.480> still<00:20:08.760> allowed 00:20:09.110 --> 00:20:09.120 align:start position:0% capture this is uh you're still allowed 00:20:09.120 --> 00:20:12.390 align:start position:0% capture this is uh you're still allowed to<00:20:09.320> have<00:20:09.440> a<00:20:09.600> bot<00:20:09.960> operate<00:20:10.400> your<00:20:10.840> account<00:20:11.840> but 00:20:12.390 --> 00:20:12.400 align:start position:0% to have a bot operate your account but 00:20:12.400 --> 00:20:16.270 align:start position:0% to have a bot operate your account but if<00:20:12.520> you<00:20:12.640> were<00:20:12.840> to<00:20:13.000> do<00:20:13.480> this<00:20:14.720> um<00:20:15.720> you<00:20:15.919> cannot 00:20:16.270 --> 00:20:16.280 align:start position:0% if you were to do this um you cannot 00:20:16.280 --> 00:20:18.270 align:start position:0% if you were to do this um you cannot bypass<00:20:16.760> rate<00:20:17.000> limits<00:20:17.360> for<00:20:17.559> example<00:20:17.960> you<00:20:18.080> would 00:20:18.270 --> 00:20:18.280 align:start position:0% bypass rate limits for example you would 00:20:18.280 --> 00:20:20.070 align:start position:0% bypass rate limits for example you would still<00:20:18.480> be<00:20:18.679> a<00:20:18.840> single<00:20:19.240> account<00:20:19.600> on<00:20:19.799> whatever 00:20:20.070 --> 00:20:20.080 align:start position:0% still be a single account on whatever 00:20:20.080 --> 00:20:21.390 align:start position:0% still be a single account on whatever system<00:20:20.320> you're<00:20:20.480> running<00:20:20.760> it<00:20:20.880> on<00:20:21.080> so<00:20:21.240> if<00:20:21.320> you 00:20:21.390 --> 00:20:21.400 align:start position:0% system you're running it on so if you 00:20:21.400 --> 00:20:23.390 align:start position:0% system you're running it on so if you want<00:20:21.559> to<00:20:21.679> bless<00:20:22.000> your<00:20:22.480> if<00:20:22.600> you<00:20:22.720> want<00:20:22.840> to<00:20:22.960> run<00:20:23.240> a 00:20:23.390 --> 00:20:23.400 align:start position:0% want to bless your if you want to run a 00:20:23.400 --> 00:20:25.750 align:start position:0% want to bless your if you want to run a Twitter<00:20:23.720> bot<00:20:24.000> as<00:20:24.080> a<00:20:24.200> unique<00:20:24.520> human<00:20:24.960> you<00:20:25.120> can 00:20:25.750 --> 00:20:25.760 align:start position:0% Twitter bot as a unique human you can 00:20:25.760 --> 00:20:27.789 align:start position:0% Twitter bot as a unique human you can but<00:20:25.880> if<00:20:26.000> it<00:20:26.120> starts<00:20:26.440> spamming<00:20:26.840> the<00:20:27.000> system<00:20:27.679> it 00:20:27.789 --> 00:20:27.799 align:start position:0% but if it starts spamming the system it 00:20:27.799 --> 00:20:30.070 align:start position:0% but if it starts spamming the system it is<00:20:28.000> obvious<00:20:28.320> that<00:20:28.480> it<00:20:28.760> is<00:20:28.880> one 00:20:30.070 --> 00:20:30.080 align:start position:0% is obvious that it is one 00:20:30.080 --> 00:20:33.669 align:start position:0% is obvious that it is one account<00:20:31.080> cool<00:20:31.880> and<00:20:32.240> what<00:20:32.360> if<00:20:32.600> World<00:20:32.919> ID<00:20:33.280> system 00:20:33.669 --> 00:20:33.679 align:start position:0% account cool and what if World ID system 00:20:33.679 --> 00:20:36.149 align:start position:0% account cool and what if World ID system gets<00:20:33.960> hacked<00:20:34.360> or<00:20:34.640> becomes<00:20:35.280> hostile<00:20:35.799> on<00:20:36.000> its 00:20:36.149 --> 00:20:36.159 align:start position:0% gets hacked or becomes hostile on its 00:20:36.159 --> 00:20:40.430 align:start position:0% gets hacked or becomes hostile on its own<00:20:36.640> AKA<00:20:37.240> evb<00:20:38.240> so<00:20:38.520> World<00:20:38.840> ID<00:20:39.360> as<00:20:39.480> a<00:20:39.679> system<00:20:40.159> is<00:20:40.280> a 00:20:40.430 --> 00:20:40.440 align:start position:0% own AKA evb so World ID as a system is a 00:20:40.440 --> 00:20:42.110 align:start position:0% own AKA evb so World ID as a system is a set<00:20:40.600> of<00:20:40.760> smart<00:20:41.080> contracts<00:20:41.559> and<00:20:41.679> a<00:20:41.760> self 00:20:42.110 --> 00:20:42.120 align:start position:0% set of smart contracts and a self 00:20:42.120 --> 00:20:44.870 align:start position:0% set of smart contracts and a self custodial<00:20:42.679> wallet<00:20:43.400> um<00:20:44.200> that<00:20:44.320> doesn't<00:20:44.640> mean 00:20:44.870 --> 00:20:44.880 align:start position:0% custodial wallet um that doesn't mean 00:20:44.880 --> 00:20:47.350 align:start position:0% custodial wallet um that doesn't mean it's<00:20:45.039> unhackable<00:20:45.880> but<00:20:46.000> it<00:20:46.120> means<00:20:46.480> it's 00:20:47.350 --> 00:20:47.360 align:start position:0% it's unhackable but it means it's 00:20:47.360 --> 00:20:49.110 align:start position:0% it's unhackable but it means it's subject<00:20:47.720> to<00:20:47.919> the<00:20:48.039> same<00:20:48.320> assumptions<00:20:48.880> as 00:20:49.110 --> 00:20:49.120 align:start position:0% subject to the same assumptions as 00:20:49.120 --> 00:20:51.270 align:start position:0% subject to the same assumptions as hacking<00:20:49.480> and<00:20:49.880> ethereum<00:20:50.880> hacking<00:20:51.159> the 00:20:51.270 --> 00:20:51.280 align:start position:0% hacking and ethereum hacking the 00:20:51.280 --> 00:20:53.830 align:start position:0% hacking and ethereum hacking the ethereum<00:20:51.760> network<00:20:52.320> and<00:20:52.919> hacking<00:20:53.320> a<00:20:53.520> self- 00:20:53.830 --> 00:20:53.840 align:start position:0% ethereum network and hacking a self- 00:20:53.840 --> 00:20:56.710 align:start position:0% ethereum network and hacking a self- custodial<00:20:54.640> wallet<00:20:55.640> um<00:20:55.880> but<00:20:56.320> the<00:20:56.440> other 00:20:56.710 --> 00:20:56.720 align:start position:0% custodial wallet um but the other 00:20:56.720 --> 00:20:58.390 align:start position:0% custodial wallet um but the other question<00:20:57.039> about<00:20:57.240> the<00:20:57.360> orb<00:20:57.720> itself<00:20:58.039> is<00:20:58.159> a<00:20:58.280> good 00:20:58.390 --> 00:20:58.400 align:start position:0% question about the orb itself is a good 00:20:58.400 --> 00:20:59.390 align:start position:0% question about the orb itself is a good one 00:20:59.390 --> 00:20:59.400 align:start position:0% one 00:20:59.400 --> 00:21:01.590 align:start position:0% one um<00:20:59.600> and<00:20:59.760> the<00:20:59.880> way<00:21:00.000> we<00:21:00.159> tackle<00:21:00.559> that<00:21:00.799> is<00:21:01.400> like<00:21:01.520> I 00:21:01.590 --> 00:21:01.600 align:start position:0% um and the way we tackle that is like I 00:21:01.600 --> 00:21:04.350 align:start position:0% um and the way we tackle that is like I said<00:21:01.760> through<00:21:02.080> transparency<00:21:02.960> in<00:21:03.159> how<00:21:03.360> the<00:21:03.480> orb 00:21:04.350 --> 00:21:04.360 align:start position:0% said through transparency in how the orb 00:21:04.360 --> 00:21:07.070 align:start position:0% said through transparency in how the orb itself<00:21:05.000> operates<00:21:05.880> on<00:21:06.120> chain<00:21:06.400> so<00:21:06.640> first<00:21:06.840> of<00:21:06.960> all 00:21:07.070 --> 00:21:07.080 align:start position:0% itself operates on chain so first of all 00:21:07.080 --> 00:21:09.310 align:start position:0% itself operates on chain so first of all the<00:21:07.200> orb<00:21:07.559> is<00:21:07.760> fully<00:21:08.080> open<00:21:08.360> source<00:21:08.960> uh<00:21:09.080> open 00:21:09.310 --> 00:21:09.320 align:start position:0% the orb is fully open source uh open 00:21:09.320 --> 00:21:11.789 align:start position:0% the orb is fully open source uh open Hardware<00:21:09.720> open<00:21:10.159> firmware<00:21:11.159> um<00:21:11.400> it<00:21:11.520> has<00:21:11.640> a 00:21:11.789 --> 00:21:11.799 align:start position:0% Hardware open firmware um it has a 00:21:11.799 --> 00:21:13.870 align:start position:0% Hardware open firmware um it has a removal<00:21:12.240> SD<00:21:12.640> card<00:21:12.919> so<00:21:13.080> you<00:21:13.159> can<00:21:13.320> verify<00:21:13.760> the 00:21:13.870 --> 00:21:13.880 align:start position:0% removal SD card so you can verify the 00:21:13.880 --> 00:21:15.950 align:start position:0% removal SD card so you can verify the build<00:21:14.159> and<00:21:14.279> so<00:21:14.440> on<00:21:14.880> they're<00:21:15.120> all<00:21:15.679> um 00:21:15.950 --> 00:21:15.960 align:start position:0% build and so on they're all um 00:21:15.960 --> 00:21:18.950 align:start position:0% build and so on they're all um registered<00:21:16.480> on<00:21:17.039> chain 00:21:18.950 --> 00:21:18.960 align:start position:0% registered on chain 00:21:18.960 --> 00:21:21.830 align:start position:0% registered on chain and<00:21:19.960> while<00:21:20.240> the<00:21:20.480> process<00:21:20.840> of<00:21:21.159> users<00:21:21.600> and<00:21:21.760> the 00:21:21.830 --> 00:21:21.840 align:start position:0% and while the process of users and the 00:21:21.840 --> 00:21:23.990 align:start position:0% and while the process of users and the user<00:21:22.120> signing<00:21:22.400> up<00:21:22.679> is<00:21:22.840> entirely<00:21:23.279> Anonymous 00:21:23.990 --> 00:21:24.000 align:start position:0% user signing up is entirely Anonymous 00:21:24.000 --> 00:21:26.269 align:start position:0% user signing up is entirely Anonymous the<00:21:24.159> behavior<00:21:24.520> of<00:21:24.640> the<00:21:24.720> orb<00:21:25.039> is<00:21:25.200> not<00:21:25.760> so<00:21:25.960> it<00:21:26.080> is 00:21:26.269 --> 00:21:26.279 align:start position:0% the behavior of the orb is not so it is 00:21:26.279 --> 00:21:28.870 align:start position:0% the behavior of the orb is not so it is public<00:21:26.760> how<00:21:26.919> many<00:21:27.520> um<00:21:27.880> um<00:21:28.039> signups<00:21:28.679> certain 00:21:28.870 --> 00:21:28.880 align:start position:0% public how many um um signups certain 00:21:28.880 --> 00:21:30.909 align:start position:0% public how many um um signups certain orb<00:21:29.200> does<00:21:29.520> and<00:21:29.640> if<00:21:29.799> there<00:21:29.919> is<00:21:30.080> any<00:21:30.320> suspicious 00:21:30.909 --> 00:21:30.919 align:start position:0% orb does and if there is any suspicious 00:21:30.919 --> 00:21:33.630 align:start position:0% orb does and if there is any suspicious behavior<00:21:31.919> that<00:21:32.080> can<00:21:32.200> be<00:21:32.360> flagged<00:21:33.360> and<00:21:33.520> the 00:21:33.630 --> 00:21:33.640 align:start position:0% behavior that can be flagged and the 00:21:33.640 --> 00:21:35.470 align:start position:0% behavior that can be flagged and the multiparty<00:21:34.279> compute<00:21:34.640> setup<00:21:35.000> can<00:21:35.159> actually 00:21:35.470 --> 00:21:35.480 align:start position:0% multiparty compute setup can actually 00:21:35.480 --> 00:21:38.190 align:start position:0% multiparty compute setup can actually revert<00:21:36.120> these<00:21:36.559> fraudulent 00:21:38.190 --> 00:21:38.200 align:start position:0% revert these fraudulent 00:21:38.200 --> 00:21:41.710 align:start position:0% revert these fraudulent signups<00:21:39.200> uh<00:21:39.400> another<00:21:39.799> question<00:21:40.559> is<00:21:41.279> Iris 00:21:41.710 --> 00:21:41.720 align:start position:0% signups uh another question is Iris 00:21:41.720 --> 00:21:44.350 align:start position:0% signups uh another question is Iris froto<00:21:42.200> hard<00:21:42.440> to<00:21:42.760> capture<00:21:43.360> can<00:21:43.480> it<00:21:43.640> be<00:21:43.840> scanned 00:21:44.350 --> 00:21:44.360 align:start position:0% froto hard to capture can it be scanned 00:21:44.360 --> 00:21:46.950 align:start position:0% froto hard to capture can it be scanned when<00:21:44.600> I'm<00:21:45.120> sleeping<00:21:46.120> no<00:21:46.279> it<00:21:46.440> cannot<00:21:46.760> it's 00:21:46.950 --> 00:21:46.960 align:start position:0% when I'm sleeping no it cannot it's 00:21:46.960 --> 00:21:50.310 align:start position:0% when I'm sleeping no it cannot it's actually<00:21:47.559> um<00:21:47.679> surprisingly<00:21:48.360> hard<00:21:48.960> uh<00:21:49.080> the<00:21:49.320> orb 00:21:50.310 --> 00:21:50.320 align:start position:0% actually um surprisingly hard uh the orb 00:21:50.320 --> 00:21:51.870 align:start position:0% actually um surprisingly hard uh the orb um<00:21:50.520> despite<00:21:50.840> being<00:21:51.039> open<00:21:51.320> Hardware 00:21:51.870 --> 00:21:51.880 align:start position:0% um despite being open Hardware 00:21:51.880 --> 00:21:55.029 align:start position:0% um despite being open Hardware unfortunately<00:21:52.679> contains<00:21:53.440> um<00:21:53.679> custom<00:21:54.159> Optics 00:21:55.029 --> 00:21:55.039 align:start position:0% unfortunately contains um custom Optics 00:21:55.039 --> 00:21:57.070 align:start position:0% unfortunately contains um custom Optics uh<00:21:55.279> that<00:21:55.960> you<00:21:56.200> can't<00:21:56.400> really<00:21:56.600> get<00:21:56.760> off<00:21:56.960> the 00:21:57.070 --> 00:21:57.080 align:start position:0% uh that you can't really get off the 00:21:57.080 --> 00:21:59.149 align:start position:0% uh that you can't really get off the shelf<00:21:57.919> you<00:21:58.039> need<00:21:58.200> to<00:21:58.279> find<00:21:58.720> someone 00:21:59.149 --> 00:21:59.159 align:start position:0% shelf you need to find someone 00:21:59.159 --> 00:22:00.990 align:start position:0% shelf you need to find someone specialized<00:21:59.679> in<00:21:59.799> making<00:22:00.080> lenses<00:22:00.480> to<00:22:00.679> get<00:22:00.799> this 00:22:00.990 --> 00:22:01.000 align:start position:0% specialized in making lenses to get this 00:22:01.000 --> 00:22:04.190 align:start position:0% specialized in making lenses to get this done<00:22:01.760> it's<00:22:02.080> it's<00:22:02.360> it's<00:22:02.480> a<00:22:02.679> hard<00:22:03.039> problem<00:22:03.520> of 00:22:04.190 --> 00:22:04.200 align:start position:0% done it's it's it's a hard problem of 00:22:04.200 --> 00:22:06.549 align:start position:0% done it's it's it's a hard problem of getting<00:22:04.440> a<00:22:04.559> high<00:22:04.760> resolution<00:22:05.360> picture<00:22:06.039> of<00:22:06.279> of 00:22:06.549 --> 00:22:06.559 align:start position:0% getting a high resolution picture of of 00:22:06.559 --> 00:22:08.269 align:start position:0% getting a high resolution picture of of something<00:22:06.880> the<00:22:07.039> size<00:22:07.240> of<00:22:07.360> a<00:22:07.480> sugar<00:22:07.840> cube<00:22:08.200> that 00:22:08.269 --> 00:22:08.279 align:start position:0% something the size of a sugar cube that 00:22:08.279 --> 00:22:10.110 align:start position:0% something the size of a sugar cube that is<00:22:08.440> bouncing<00:22:08.880> around<00:22:09.159> a<00:22:09.279> meter<00:22:09.520> and<00:22:09.640> a<00:22:09.799> half<00:22:10.000> in 00:22:10.110 --> 00:22:10.120 align:start position:0% is bouncing around a meter and a half in 00:22:10.120 --> 00:22:12.269 align:start position:0% is bouncing around a meter and a half in front<00:22:10.320> of<00:22:10.480> you<00:22:11.080> uh<00:22:11.200> and<00:22:11.279> the<00:22:11.400> ARB<00:22:11.720> does<00:22:11.880> it<00:22:12.080> it's 00:22:12.269 --> 00:22:12.279 align:start position:0% front of you uh and the ARB does it it's 00:22:12.279 --> 00:22:15.070 align:start position:0% front of you uh and the ARB does it it's quite<00:22:12.679> amazing<00:22:13.679> um<00:22:14.000> this<00:22:14.120> is<00:22:14.279> a<00:22:14.440> good<00:22:14.760> thing 00:22:15.070 --> 00:22:15.080 align:start position:0% quite amazing um this is a good thing 00:22:15.080 --> 00:22:18.029 align:start position:0% quite amazing um this is a good thing though<00:22:15.600> uh<00:22:15.760> because<00:22:16.120> this<00:22:16.279> means<00:22:16.880> that<00:22:17.880> there 00:22:18.029 --> 00:22:18.039 align:start position:0% though uh because this means that there 00:22:18.039 --> 00:22:22.110 align:start position:0% though uh because this means that there is<00:22:18.559> a<00:22:19.559> strong<00:22:19.880> form<00:22:20.440> of<00:22:20.880> uh 00:22:22.110 --> 00:22:22.120 align:start position:0% is a strong form of uh 00:22:22.120 --> 00:22:26.070 align:start position:0% is a strong form of uh consent<00:22:23.120> um<00:22:23.400> cons<00:22:24.000> yeah<00:22:24.240> kind<00:22:24.360> of<00:22:24.559> consent<00:22:25.279> in 00:22:26.070 --> 00:22:26.080 align:start position:0% consent um cons yeah kind of consent in 00:22:26.080 --> 00:22:27.789 align:start position:0% consent um cons yeah kind of consent in getting<00:22:26.360> your<00:22:26.520> iris<00:22:26.880> pictures<00:22:27.200> taken<00:22:27.600> it's 00:22:27.789 --> 00:22:27.799 align:start position:0% getting your iris pictures taken it's 00:22:27.799 --> 00:22:31.149 align:start position:0% getting your iris pictures taken it's very<00:22:28.080> hard<00:22:28.640> to<00:22:29.240> take<00:22:29.520> Iris<00:22:29.919> pictures<00:22:30.559> of 00:22:31.149 --> 00:22:31.159 align:start position:0% very hard to take Iris pictures of 00:22:31.159 --> 00:22:33.789 align:start position:0% very hard to take Iris pictures of someone<00:22:32.159> who<00:22:32.400> doesn't<00:22:32.840> actively<00:22:33.640> and 00:22:33.789 --> 00:22:33.799 align:start position:0% someone who doesn't actively and 00:22:33.799 --> 00:22:35.990 align:start position:0% someone who doesn't actively and willingly<00:22:34.320> participate<00:22:34.840> in<00:22:34.960> the 00:22:35.990 --> 00:22:36.000 align:start position:0% willingly participate in the 00:22:36.000 --> 00:22:42.830 align:start position:0% willingly participate in the process<00:22:37.000> how<00:22:37.240> does<00:22:37.520> World<00:22:37.840> earn<00:22:38.559> income<00:22:39.559> I 00:22:42.830 --> 00:22:42.840 align:start position:0% 00:22:42.840 --> 00:22:44.029 align:start position:0% [Music] 00:22:44.029 --> 00:22:44.039 align:start position:0% [Music] 00:22:44.039 --> 00:22:47.510 align:start position:0% [Music] pass<00:22:45.039> no<00:22:45.279> really<00:22:45.880> um<00:22:46.440> this<00:22:46.600> is<00:22:47.240> we<00:22:47.400> we 00:22:47.510 --> 00:22:47.520 align:start position:0% pass no really um this is we we 00:22:47.520 --> 00:22:51.750 align:start position:0% pass no really um this is we we currently<00:22:47.960> don't<00:22:48.200> have<00:22:48.440> any<00:22:49.000> uh<00:22:49.679> any<00:22:50.640> issues 00:22:51.750 --> 00:22:51.760 align:start position:0% currently don't have any uh any issues 00:22:51.760 --> 00:22:54.950 align:start position:0% currently don't have any uh any issues uh<00:22:52.760> here<00:22:53.240> um<00:22:53.600> Everything<00:22:54.039> is<00:22:54.520> Everything<00:22:54.840> is 00:22:54.950 --> 00:22:54.960 align:start position:0% uh here um Everything is Everything is 00:22:54.960 --> 00:22:57.630 align:start position:0% uh here um Everything is Everything is in<00:22:55.200> production<00:22:55.720> everything<00:22:56.000> is<00:22:56.240> running<00:22:57.240> and 00:22:57.630 --> 00:22:57.640 align:start position:0% in production everything is running and 00:22:57.640 --> 00:23:01.070 align:start position:0% in production everything is running and this<00:22:57.760> is<00:22:57.960> such<00:22:58.159> a<00:22:58.760> the<00:22:59.039> space<00:22:59.360> of<00:22:59.760> identity<00:23:00.760> is 00:23:01.070 --> 00:23:01.080 align:start position:0% this is such a the space of identity is 00:23:01.080 --> 00:23:04.669 align:start position:0% this is such a the space of identity is such<00:23:01.440> a<00:23:01.880> gigantic<00:23:03.159> opportunity<00:23:04.159> that<00:23:04.320> goes 00:23:04.669 --> 00:23:04.679 align:start position:0% such a gigantic opportunity that goes 00:23:04.679 --> 00:23:07.269 align:start position:0% such a gigantic opportunity that goes Way<00:23:04.919> Beyond<00:23:05.440> the<00:23:05.640> entire<00:23:06.080> current<00:23:06.480> crypto 00:23:07.269 --> 00:23:07.279 align:start position:0% Way Beyond the entire current crypto 00:23:07.279 --> 00:23:10.590 align:start position:0% Way Beyond the entire current crypto space<00:23:08.279> um<00:23:08.799> and<00:23:09.000> then<00:23:09.279> itself<00:23:10.039> the<00:23:10.159> world 00:23:10.590 --> 00:23:10.600 align:start position:0% space um and then itself the world 00:23:10.600 --> 00:23:13.710 align:start position:0% space um and then itself the world project<00:23:11.039> will<00:23:11.279> on<00:23:11.720> board<00:23:12.720> already<00:23:13.120> onboard<00:23:13.559> a 00:23:13.710 --> 00:23:13.720 align:start position:0% project will on board already onboard a 00:23:13.720 --> 00:23:15.590 align:start position:0% project will on board already onboard a TENS<00:23:13.960> of<00:23:14.080> millions<00:23:14.480> of<00:23:14.640> people<00:23:14.960> into<00:23:15.360> into 00:23:15.590 --> 00:23:15.600 align:start position:0% TENS of millions of people into into 00:23:15.600 --> 00:23:18.390 align:start position:0% TENS of millions of people into into blockchain<00:23:16.080> but<00:23:16.279> on<00:23:16.400> board<00:23:16.720> many<00:23:16.960> many 00:23:18.390 --> 00:23:18.400 align:start position:0% blockchain but on board many many 00:23:18.400 --> 00:23:22.310 align:start position:0% blockchain but on board many many more<00:23:19.400> um<00:23:19.760> how<00:23:19.960> about<00:23:20.480> artificial<00:23:21.080> fake<00:23:21.520> irises 00:23:22.310 --> 00:23:22.320 align:start position:0% more um how about artificial fake irises 00:23:22.320 --> 00:23:24.909 align:start position:0% more um how about artificial fake irises the<00:23:22.600> orb<00:23:23.240> could<00:23:23.600> theoretically<00:23:24.360> think<00:23:24.679> it 00:23:24.909 --> 00:23:24.919 align:start position:0% the orb could theoretically think it 00:23:24.919 --> 00:23:28.110 align:start position:0% the orb could theoretically think it registers<00:23:25.559> real<00:23:26.400> humans<00:23:27.400> yeah<00:23:27.640> I<00:23:27.720> think<00:23:27.960> I 00:23:28.110 --> 00:23:28.120 align:start position:0% registers real humans yeah I think I 00:23:28.120 --> 00:23:30.110 align:start position:0% registers real humans yeah I think I haven't<00:23:28.559> covered<00:23:28.880> enough<00:23:29.200> how<00:23:29.480> important<00:23:29.960> it 00:23:30.110 --> 00:23:30.120 align:start position:0% haven't covered enough how important it 00:23:30.120 --> 00:23:33.190 align:start position:0% haven't covered enough how important it is<00:23:30.520> for<00:23:30.760> any<00:23:31.000> kind<00:23:31.120> of<00:23:31.320> biometric<00:23:31.919> sensor<00:23:32.840> to 00:23:33.190 --> 00:23:33.200 align:start position:0% is for any kind of biometric sensor to 00:23:33.200 --> 00:23:36.310 align:start position:0% is for any kind of biometric sensor to verify<00:23:34.200> that<00:23:34.360> it<00:23:34.520> is<00:23:34.799> act<00:23:35.480> it's<00:23:35.640> not<00:23:35.880> enough<00:23:36.159> to 00:23:36.310 --> 00:23:36.320 align:start position:0% verify that it is act it's not enough to 00:23:36.320 --> 00:23:38.029 align:start position:0% verify that it is act it's not enough to just<00:23:36.559> take<00:23:36.720> a<00:23:36.880> picture<00:23:37.159> of<00:23:37.440> Iris<00:23:37.799> or<00:23:37.919> a 00:23:38.029 --> 00:23:38.039 align:start position:0% just take a picture of Iris or a 00:23:38.039 --> 00:23:40.390 align:start position:0% just take a picture of Iris or a fingerprint<00:23:38.840> you<00:23:38.960> need<00:23:39.120> to<00:23:39.320> make<00:23:39.480> sure<00:23:40.200> that 00:23:40.390 --> 00:23:40.400 align:start position:0% fingerprint you need to make sure that 00:23:40.400 --> 00:23:42.750 align:start position:0% fingerprint you need to make sure that this<00:23:40.520> is<00:23:40.720> from<00:23:40.919> a<00:23:41.120> real<00:23:41.520> life<00:23:42.320> living 00:23:42.750 --> 00:23:42.760 align:start position:0% this is from a real life living 00:23:42.760 --> 00:23:46.269 align:start position:0% this is from a real life living breathing<00:23:43.679> human<00:23:44.400> body<00:23:45.400> because<00:23:45.720> otherwise 00:23:46.269 --> 00:23:46.279 align:start position:0% breathing human body because otherwise 00:23:46.279 --> 00:23:47.909 align:start position:0% breathing human body because otherwise it<00:23:46.400> could<00:23:46.600> just<00:23:46.760> be<00:23:47.000> someone<00:23:47.320> holding<00:23:47.600> on<00:23:47.720> an 00:23:47.909 --> 00:23:47.919 align:start position:0% it could just be someone holding on an 00:23:47.919 --> 00:23:50.510 align:start position:0% it could just be someone holding on an iPad<00:23:48.400> or<00:23:48.640> someone<00:23:49.039> trying<00:23:49.360> to<00:23:49.760> squish<00:23:50.279> a 00:23:50.510 --> 00:23:50.520 align:start position:0% iPad or someone trying to squish a 00:23:50.520 --> 00:23:53.310 align:start position:0% iPad or someone trying to squish a silicone<00:23:51.000> mold<00:23:51.400> on<00:23:51.520> a<00:23:51.640> fingerprint<00:23:52.320> scanner 00:23:53.310 --> 00:23:53.320 align:start position:0% silicone mold on a fingerprint scanner 00:23:53.320 --> 00:23:55.269 align:start position:0% silicone mold on a fingerprint scanner the<00:23:53.520> the<00:23:53.679> hard<00:23:54.000> part<00:23:54.200> in<00:23:54.400> designing<00:23:54.960> any<00:23:55.159> kind 00:23:55.269 --> 00:23:55.279 align:start position:0% the the hard part in designing any kind 00:23:55.279 --> 00:23:57.789 align:start position:0% the the hard part in designing any kind of<00:23:55.480> biometric<00:23:56.080> system<00:23:56.679> is<00:23:57.039> not<00:23:57.200> so<00:23:57.400> much<00:23:57.600> the 00:23:57.789 --> 00:23:57.799 align:start position:0% of biometric system is not so much the 00:23:57.799 --> 00:24:00.070 align:start position:0% of biometric system is not so much the capturing<00:23:58.240> of<00:23:58.520> the<00:23:58.600> raw<00:23:58.880> data<00:23:59.600> but<00:23:59.760> it<00:23:59.880> is 00:24:00.070 --> 00:24:00.080 align:start position:0% capturing of the raw data but it is 00:24:00.080 --> 00:24:01.909 align:start position:0% capturing of the raw data but it is invalidating<00:24:00.919> that<00:24:01.039> it<00:24:01.200> is<00:24:01.400> actually<00:24:01.720> came 00:24:01.909 --> 00:24:01.919 align:start position:0% invalidating that it is actually came 00:24:01.919 --> 00:24:03.230 align:start position:0% invalidating that it is actually came from<00:24:02.039> a<00:24:02.200> real<00:24:02.400> human 00:24:03.230 --> 00:24:03.240 align:start position:0% from a real human 00:24:03.240 --> 00:24:06.669 align:start position:0% from a real human being<00:24:04.240> cool<00:24:04.720> uh<00:24:04.919> we<00:24:05.200> have<00:24:05.640> 30<00:24:06.000> seconds<00:24:06.400> to<00:24:06.559> go 00:24:06.669 --> 00:24:06.679 align:start position:0% being cool uh we have 30 seconds to go 00:24:06.679 --> 00:24:09.029 align:start position:0% being cool uh we have 30 seconds to go through<00:24:06.880> one<00:24:07.039> more<00:24:07.279> question<00:24:08.240> can<00:24:08.480> someone 00:24:09.029 --> 00:24:09.039 align:start position:0% through one more question can someone 00:24:09.039 --> 00:24:12.950 align:start position:0% through one more question can someone with<00:24:09.279> an<00:24:09.559> orb<00:24:10.159> produce<00:24:10.600> IDs<00:24:11.200> for<00:24:11.720> non-existent 00:24:12.950 --> 00:24:12.960 align:start position:0% with an orb produce IDs for non-existent 00:24:12.960 --> 00:24:16.470 align:start position:0% with an orb produce IDs for non-existent irises<00:24:13.960> no<00:24:14.279> the<00:24:14.919> um<00:24:15.320> even<00:24:15.559> if<00:24:15.679> you<00:24:15.840> have<00:24:16.000> an<00:24:16.200> orb 00:24:16.470 --> 00:24:16.480 align:start position:0% irises no the um even if you have an orb 00:24:16.480 --> 00:24:19.590 align:start position:0% irises no the um even if you have an orb in<00:24:16.640> physical<00:24:17.120> possession<00:24:18.000> it<00:24:18.360> is<00:24:18.960> um<00:24:19.200> near 00:24:19.590 --> 00:24:19.600 align:start position:0% in physical possession it is um near 00:24:19.600 --> 00:24:21.669 align:start position:0% in physical possession it is um near impossible<00:24:20.200> to<00:24:20.559> to<00:24:20.720> make<00:24:20.919> it<00:24:21.039> do<00:24:21.279> those<00:24:21.480> kinds 00:24:21.669 --> 00:24:21.679 align:start position:0% impossible to to make it do those kinds 00:24:21.679 --> 00:24:24.710 align:start position:0% impossible to to make it do those kinds of<00:24:21.799> things<00:24:22.600> it<00:24:22.760> it<00:24:22.880> has<00:24:23.120> like<00:24:23.320> a<00:24:23.559> very<00:24:24.000> strong 00:24:24.710 --> 00:24:24.720 align:start position:0% of things it it has like a very strong 00:24:24.720 --> 00:24:26.590 align:start position:0% of things it it has like a very strong amount<00:24:25.039> of<00:24:25.240> physical<00:24:25.640> security<00:24:26.159> in<00:24:26.320> it<00:24:26.440> and 00:24:26.590 --> 00:24:26.600 align:start position:0% amount of physical security in it and 00:24:26.600 --> 00:24:29.190 align:start position:0% amount of physical security in it and temper<00:24:26.960> protection<00:24:27.360> and<00:24:27.480> so<00:24:27.640> on<00:24:28.840> all<00:24:28.960> right 00:24:29.190 --> 00:24:29.200 align:start position:0% temper protection and so on all right 00:24:29.200 --> 00:24:32.350 align:start position:0% temper protection and so on all right cool<00:24:29.600> so<00:24:30.080> I<00:24:30.200> think<00:24:30.559> that<00:24:31.279> concludes<00:24:31.840> our<00:24:32.120> talk 00:24:32.350 --> 00:24:32.360 align:start position:0% cool so I think that concludes our talk 00:24:32.360 --> 00:24:35.640 align:start position:0% cool so I think that concludes our talk today<00:24:32.640> from<00:24:32.840> Rimco<00:24:33.360> let's