WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.310 align:start position:0% [Music] 00:00:12.310 --> 00:00:12.320 align:start position:0% 00:00:12.320 --> 00:00:15.589 align:start position:0% I'm<00:00:13.340> from<00:00:14.340> the<00:00:14.460> privacy<00:00:15.000> and<00:00:15.120> scalings 00:00:15.589 --> 00:00:15.599 align:start position:0% I'm from the privacy and scalings 00:00:15.599 --> 00:00:18.230 align:start position:0% I'm from the privacy and scalings Explorations<00:00:16.379> team<00:00:16.800> in<00:00:17.760> the<00:00:17.820> ethereum 00:00:18.230 --> 00:00:18.240 align:start position:0% Explorations team in the ethereum 00:00:18.240 --> 00:00:19.310 align:start position:0% Explorations team in the ethereum foundation 00:00:19.310 --> 00:00:19.320 align:start position:0% foundation 00:00:19.320 --> 00:00:21.890 align:start position:0% foundation and<00:00:20.060> I'm<00:00:21.060> going<00:00:21.180> to<00:00:21.240> talk<00:00:21.420> today<00:00:21.600> about 00:00:21.890 --> 00:00:21.900 align:start position:0% and I'm going to talk today about 00:00:21.900 --> 00:00:23.630 align:start position:0% and I'm going to talk today about interrep<00:00:22.619> which<00:00:22.740> is<00:00:22.859> a<00:00:22.980> project<00:00:23.100> we've<00:00:23.460> been 00:00:23.630 --> 00:00:23.640 align:start position:0% interrep which is a project we've been 00:00:23.640 --> 00:00:30.109 align:start position:0% interrep which is a project we've been working<00:00:24.180> on<00:00:24.480> it's<00:00:25.160> in<00:00:26.160> the<00:00:26.400> identity<00:00:26.820> space 00:00:30.109 --> 00:00:30.119 align:start position:0% 00:00:30.119 --> 00:00:34.549 align:start position:0% so<00:00:30.599> brief<00:00:31.019> introduction<00:00:31.439> to<00:00:31.920> what<00:00:32.040> we<00:00:32.220> do<00:00:32.399> it's 00:00:34.549 --> 00:00:34.559 align:start position:0% so brief introduction to what we do it's 00:00:34.559 --> 00:00:38.510 align:start position:0% so brief introduction to what we do it's there's<00:00:35.100> lots<00:00:35.520> of<00:00:35.579> projects<00:00:36.480> in<00:00:37.140> the<00:00:37.520> trying 00:00:38.510 --> 00:00:38.520 align:start position:0% there's lots of projects in the trying 00:00:38.520 --> 00:00:42.670 align:start position:0% there's lots of projects in the trying to<00:00:38.700> bring<00:00:39.000> identity<00:00:39.600> into<00:00:39.840> ethereum 00:00:42.670 --> 00:00:42.680 align:start position:0% 00:00:42.680 --> 00:00:48.889 align:start position:0% and<00:00:43.820> they<00:00:44.820> tend<00:00:45.059> to<00:00:45.239> be<00:00:45.980> like<00:00:47.120> uh<00:00:48.120> have<00:00:48.600> some 00:00:48.889 --> 00:00:48.899 align:start position:0% and they tend to be like uh have some 00:00:48.899 --> 00:00:50.990 align:start position:0% and they tend to be like uh have some identity<00:00:49.440> source<00:00:49.800> and<00:00:49.920> and<00:00:50.219> build<00:00:50.460> it<00:00:50.640> up<00:00:50.760> from 00:00:50.990 --> 00:00:51.000 align:start position:0% identity source and and build it up from 00:00:51.000 --> 00:00:54.170 align:start position:0% identity source and and build it up from from<00:00:51.239> the<00:00:51.539> ground<00:00:51.719> our<00:00:52.680> approach<00:00:53.160> is<00:00:54.000> a 00:00:54.170 --> 00:00:54.180 align:start position:0% from the ground our approach is a 00:00:54.180 --> 00:00:58.670 align:start position:0% from the ground our approach is a pragmatic<00:00:54.780> approach<00:00:55.460> where<00:00:56.460> we<00:00:57.180> build<00:00:58.079> on<00:00:58.320> the 00:00:58.670 --> 00:00:58.680 align:start position:0% pragmatic approach where we build on the 00:00:58.680 --> 00:01:01.189 align:start position:0% pragmatic approach where we build on the identity<00:00:59.100> that<00:00:59.460> we<00:00:59.640> already<00:00:59.820> have<00:01:00.239> in<00:01:01.020> our 00:01:01.189 --> 00:01:01.199 align:start position:0% identity that we already have in our 00:01:01.199 --> 00:01:05.810 align:start position:0% identity that we already have in our digital<00:01:01.699> uh<00:01:02.699> in<00:01:03.059> our<00:01:03.660> digital<00:01:03.960> lives 00:01:05.810 --> 00:01:05.820 align:start position:0% digital uh in our digital lives 00:01:05.820 --> 00:01:08.390 align:start position:0% digital uh in our digital lives um<00:01:06.360> and<00:01:06.960> we<00:01:07.080> bring<00:01:07.260> that<00:01:07.439> across<00:01:07.740> to<00:01:07.860> ethereum 00:01:08.390 --> 00:01:08.400 align:start position:0% um and we bring that across to ethereum 00:01:08.400 --> 00:01:12.950 align:start position:0% um and we bring that across to ethereum so<00:01:09.060> we<00:01:09.299> can<00:01:09.479> have<00:01:10.020> an<00:01:10.200> established<00:01:10.860> pool<00:01:11.580> of<00:01:12.000> uh 00:01:12.950 --> 00:01:12.960 align:start position:0% so we can have an established pool of uh 00:01:12.960 --> 00:01:15.710 align:start position:0% so we can have an established pool of uh or<00:01:13.500> established<00:01:14.100> identity 00:01:15.710 --> 00:01:15.720 align:start position:0% or established identity 00:01:15.720 --> 00:01:18.770 align:start position:0% or established identity pool<00:01:16.340> and<00:01:17.340> we<00:01:17.520> we<00:01:17.760> can<00:01:18.000> integrate<00:01:18.420> that<00:01:18.600> into 00:01:18.770 --> 00:01:18.780 align:start position:0% pool and we we can integrate that into 00:01:18.780 --> 00:01:23.390 align:start position:0% pool and we we can integrate that into our<00:01:19.140> ethereum<00:01:20.100> applications 00:01:23.390 --> 00:01:23.400 align:start position:0% 00:01:23.400 --> 00:01:25.310 align:start position:0% um<00:01:23.520> so<00:01:24.060> yeah<00:01:24.180> very<00:01:24.479> much<00:01:24.659> a<00:01:24.780> pragmatic 00:01:25.310 --> 00:01:25.320 align:start position:0% um so yeah very much a pragmatic 00:01:25.320 --> 00:01:26.870 align:start position:0% um so yeah very much a pragmatic approach<00:01:25.619> building<00:01:25.920> on 00:01:26.870 --> 00:01:26.880 align:start position:0% approach building on 00:01:26.880 --> 00:01:30.170 align:start position:0% approach building on the<00:01:27.420> identity<00:01:27.840> sources<00:01:28.740> we<00:01:28.920> already<00:01:29.100> have 00:01:30.170 --> 00:01:30.180 align:start position:0% the identity sources we already have 00:01:30.180 --> 00:01:33.649 align:start position:0% the identity sources we already have so<00:01:30.960> what<00:01:31.080> we<00:01:31.200> aim<00:01:31.439> to<00:01:31.560> do<00:01:31.680> is<00:01:32.240> build<00:01:33.240> a<00:01:33.420> bridge 00:01:33.649 --> 00:01:33.659 align:start position:0% so what we aim to do is build a bridge 00:01:33.659 --> 00:01:37.609 align:start position:0% so what we aim to do is build a bridge from<00:01:34.560> existing<00:01:35.220> digital<00:01:36.140> identity<00:01:37.140> sources 00:01:37.609 --> 00:01:37.619 align:start position:0% from existing digital identity sources 00:01:37.619 --> 00:01:39.910 align:start position:0% from existing digital identity sources to<00:01:38.520> ethereum 00:01:39.910 --> 00:01:39.920 align:start position:0% to ethereum 00:01:39.920 --> 00:01:43.249 align:start position:0% to ethereum uh<00:01:40.920> integrate<00:01:41.400> with<00:01:41.720> providers<00:01:42.720> of<00:01:43.020> those 00:01:43.249 --> 00:01:43.259 align:start position:0% uh integrate with providers of those 00:01:43.259 --> 00:01:44.890 align:start position:0% uh integrate with providers of those identity<00:01:43.740> sources 00:01:44.890 --> 00:01:44.900 align:start position:0% identity sources 00:01:44.900 --> 00:01:48.890 align:start position:0% identity sources and<00:01:45.900> then<00:01:46.280> privacy<00:01:47.280> is<00:01:47.460> very<00:01:47.700> important<00:01:48.060> to<00:01:48.240> us 00:01:48.890 --> 00:01:48.900 align:start position:0% and then privacy is very important to us 00:01:48.900 --> 00:01:50.330 align:start position:0% and then privacy is very important to us so 00:01:50.330 --> 00:01:50.340 align:start position:0% so 00:01:50.340 --> 00:01:54.710 align:start position:0% so we<00:01:51.119> build<00:01:51.299> on<00:01:51.479> the<00:01:51.659> semaphore<00:01:52.259> framework 00:01:54.710 --> 00:01:54.720 align:start position:0% we build on the semaphore framework 00:01:54.720 --> 00:01:56.710 align:start position:0% we build on the semaphore framework and 00:01:56.710 --> 00:01:56.720 align:start position:0% and 00:01:56.720 --> 00:01:59.210 align:start position:0% and integrate<00:01:57.720> with<00:01:57.899> with<00:01:58.380> that<00:01:58.680> so<00:01:58.920> those 00:01:59.210 --> 00:01:59.220 align:start position:0% integrate with with that so those 00:01:59.220 --> 00:02:01.850 align:start position:0% integrate with with that so those building<00:01:59.399> blocks<00:01:59.939> all<00:02:00.420> come<00:02:00.659> together 00:02:01.850 --> 00:02:01.860 align:start position:0% building blocks all come together 00:02:01.860 --> 00:02:05.510 align:start position:0% building blocks all come together to<00:02:02.640> form<00:02:02.939> the<00:02:03.240> basis<00:02:03.540> of<00:02:03.780> an<00:02:04.020> application<00:02:04.520> so 00:02:05.510 --> 00:02:05.520 align:start position:0% to form the basis of an application so 00:02:05.520 --> 00:02:07.370 align:start position:0% to form the basis of an application so identity 00:02:07.370 --> 00:02:07.380 align:start position:0% identity 00:02:07.380 --> 00:02:08.210 align:start position:0% identity um 00:02:08.210 --> 00:02:08.220 align:start position:0% um 00:02:08.220 --> 00:02:10.969 align:start position:0% um we<00:02:09.119> spent<00:02:09.539> a<00:02:09.720> lot<00:02:09.840> of<00:02:09.959> time<00:02:10.200> in<00:02:10.560> our<00:02:10.739> social 00:02:10.969 --> 00:02:10.979 align:start position:0% we spent a lot of time in our social 00:02:10.979 --> 00:02:14.330 align:start position:0% we spent a lot of time in our social networks<00:02:11.760> uh 00:02:14.330 --> 00:02:14.340 align:start position:0% networks uh 00:02:14.340 --> 00:02:16.369 align:start position:0% networks uh um<00:02:14.400> some<00:02:14.760> people<00:02:14.940> more<00:02:15.120> than<00:02:15.360> others<00:02:15.720> but<00:02:15.959> you 00:02:16.369 --> 00:02:16.379 align:start position:0% um some people more than others but you 00:02:16.379 --> 00:02:18.470 align:start position:0% um some people more than others but you know<00:02:16.500> people<00:02:16.739> spend<00:02:17.280> a<00:02:17.459> lot<00:02:17.580> of<00:02:17.700> time<00:02:17.879> on<00:02:18.180> their 00:02:18.470 --> 00:02:18.480 align:start position:0% know people spend a lot of time on their 00:02:18.480 --> 00:02:23.449 align:start position:0% know people spend a lot of time on their Twitter<00:02:18.900> accounts<00:02:19.560> and<00:02:20.040> building<00:02:20.640> up 00:02:23.449 --> 00:02:23.459 align:start position:0% 00:02:23.459 --> 00:02:26.089 align:start position:0% putting<00:02:24.060> out<00:02:24.180> a<00:02:24.540> bit<00:02:24.840> of<00:02:25.020> our<00:02:25.140> personality<00:02:25.739> in 00:02:26.089 --> 00:02:26.099 align:start position:0% putting out a bit of our personality in 00:02:26.099 --> 00:02:27.610 align:start position:0% putting out a bit of our personality in into<00:02:26.280> those<00:02:26.580> accounts 00:02:27.610 --> 00:02:27.620 align:start position:0% into those accounts 00:02:27.620 --> 00:02:31.729 align:start position:0% into those accounts uh<00:02:28.700> so<00:02:29.700> we<00:02:30.000> spend<00:02:30.300> you<00:02:30.840> know<00:02:30.900> every<00:02:31.080> tweet<00:02:31.560> you 00:02:31.729 --> 00:02:31.739 align:start position:0% uh so we spend you know every tweet you 00:02:31.739 --> 00:02:33.770 align:start position:0% uh so we spend you know every tweet you you<00:02:32.640> write 00:02:33.770 --> 00:02:33.780 align:start position:0% you write 00:02:33.780 --> 00:02:36.170 align:start position:0% you write is<00:02:34.379> a<00:02:34.620> bit<00:02:34.739> of<00:02:34.860> humanity<00:02:35.340> that<00:02:35.640> goes<00:02:35.879> into<00:02:35.940> that 00:02:36.170 --> 00:02:36.180 align:start position:0% is a bit of humanity that goes into that 00:02:36.180 --> 00:02:39.229 align:start position:0% is a bit of humanity that goes into that tweet<00:02:36.540> that<00:02:37.440> represents<00:02:38.340> you 00:02:39.229 --> 00:02:39.239 align:start position:0% tweet that represents you 00:02:39.239 --> 00:02:42.350 align:start position:0% tweet that represents you and<00:02:40.020> we<00:02:40.200> build<00:02:40.379> those<00:02:40.560> up<00:02:40.800> in<00:02:40.980> our<00:02:41.459> social 00:02:42.350 --> 00:02:42.360 align:start position:0% and we build those up in our social 00:02:42.360 --> 00:02:45.110 align:start position:0% and we build those up in our social uh<00:02:42.840> Social<00:02:43.019> Network<00:02:43.319> accounts 00:02:45.110 --> 00:02:45.120 align:start position:0% uh Social Network accounts 00:02:45.120 --> 00:02:47.210 align:start position:0% uh Social Network accounts um<00:02:45.239> people<00:02:46.080> some<00:02:46.440> people<00:02:46.560> spend<00:02:46.920> a<00:02:47.040> lot<00:02:47.160> of 00:02:47.210 --> 00:02:47.220 align:start position:0% um people some people spend a lot of 00:02:47.220 --> 00:02:49.309 align:start position:0% um people some people spend a lot of time<00:02:47.400> on<00:02:47.580> that<00:02:47.760> kind<00:02:47.879> of<00:02:48.060> thing<00:02:48.180> even<00:02:48.959> if 00:02:49.309 --> 00:02:49.319 align:start position:0% time on that kind of thing even if 00:02:49.319 --> 00:02:51.290 align:start position:0% time on that kind of thing even if you're<00:02:49.620> not<00:02:49.800> into<00:02:50.099> social 00:02:51.290 --> 00:02:51.300 align:start position:0% you're not into social 00:02:51.300 --> 00:02:54.650 align:start position:0% you're not into social social<00:02:52.080> networks<00:02:52.739> big<00:02:53.459> time<00:02:53.760> we<00:02:54.239> still<00:02:54.420> have 00:02:54.650 --> 00:02:54.660 align:start position:0% social networks big time we still have 00:02:54.660 --> 00:02:57.589 align:start position:0% social networks big time we still have digital<00:02:55.140> identity<00:02:56.099> in<00:02:56.760> the 00:02:57.589 --> 00:02:57.599 align:start position:0% digital identity in the 00:02:57.599 --> 00:02:59.630 align:start position:0% digital identity in the in<00:02:58.019> the<00:02:58.200> non-web<00:02:58.620> 3<00:02:58.739> world 00:02:59.630 --> 00:02:59.640 align:start position:0% in the non-web 3 world 00:02:59.640 --> 00:03:02.570 align:start position:0% in the non-web 3 world we<00:03:00.060> have<00:03:00.180> things<00:03:00.420> like<00:03:00.660> government<00:03:01.400> IDs<00:03:02.400> and 00:03:02.570 --> 00:03:02.580 align:start position:0% we have things like government IDs and 00:03:02.580 --> 00:03:04.369 align:start position:0% we have things like government IDs and driver's<00:03:02.940> licenses<00:03:03.420> and<00:03:03.599> all<00:03:03.780> that<00:03:03.959> kind<00:03:04.260> of 00:03:04.369 --> 00:03:04.379 align:start position:0% driver's licenses and all that kind of 00:03:04.379 --> 00:03:06.110 align:start position:0% driver's licenses and all that kind of stuff<00:03:04.560> so 00:03:06.110 --> 00:03:06.120 align:start position:0% stuff so 00:03:06.120 --> 00:03:06.710 align:start position:0% stuff so um 00:03:06.710 --> 00:03:06.720 align:start position:0% um 00:03:06.720 --> 00:03:09.710 align:start position:0% um yeah<00:03:07.200> it's<00:03:07.739> our<00:03:08.280> our<00:03:08.700> real<00:03:08.940> world<00:03:09.180> human 00:03:09.710 --> 00:03:09.720 align:start position:0% yeah it's our our real world human 00:03:09.720 --> 00:03:12.770 align:start position:0% yeah it's our our real world human identity<00:03:10.340> is<00:03:11.340> reflected<00:03:12.000> in<00:03:12.180> those<00:03:12.360> digital 00:03:12.770 --> 00:03:12.780 align:start position:0% identity is reflected in those digital 00:03:12.780 --> 00:03:13.970 align:start position:0% identity is reflected in those digital sources 00:03:13.970 --> 00:03:13.980 align:start position:0% sources 00:03:13.980 --> 00:03:16.009 align:start position:0% sources so 00:03:16.009 --> 00:03:16.019 align:start position:0% so 00:03:16.019 --> 00:03:18.589 align:start position:0% so that's<00:03:16.920> what<00:03:17.220> we<00:03:17.340> try<00:03:17.519> and<00:03:17.640> build<00:03:17.819> on 00:03:18.589 --> 00:03:18.599 align:start position:0% that's what we try and build on 00:03:18.599 --> 00:03:21.170 align:start position:0% that's what we try and build on but<00:03:19.319> we<00:03:19.739> need<00:03:19.980> to 00:03:21.170 --> 00:03:21.180 align:start position:0% but we need to 00:03:21.180 --> 00:03:23.990 align:start position:0% but we need to recognize<00:03:21.900> that<00:03:22.319> those<00:03:23.040> digital<00:03:23.459> sources 00:03:23.990 --> 00:03:24.000 align:start position:0% recognize that those digital sources 00:03:24.000 --> 00:03:29.570 align:start position:0% recognize that those digital sources also<00:03:25.099> are<00:03:26.099> vulnerable<00:03:26.519> to<00:03:27.000> civil<00:03:27.659> attacks<00:03:28.580> so 00:03:29.570 --> 00:03:29.580 align:start position:0% also are vulnerable to civil attacks so 00:03:29.580 --> 00:03:32.750 align:start position:0% also are vulnerable to civil attacks so we<00:03:29.819> need<00:03:30.060> to<00:03:30.480> yeah<00:03:31.379> filter<00:03:31.680> out<00:03:31.920> the<00:03:32.099> Bots<00:03:32.280> and 00:03:32.750 --> 00:03:32.760 align:start position:0% we need to yeah filter out the Bots and 00:03:32.760 --> 00:03:34.729 align:start position:0% we need to yeah filter out the Bots and kick<00:03:32.940> them<00:03:33.120> out 00:03:34.729 --> 00:03:34.739 align:start position:0% kick them out 00:03:34.739 --> 00:03:36.470 align:start position:0% kick them out um so<00:03:35.220> they're<00:03:35.640> the<00:03:35.879> kinds<00:03:36.120> of<00:03:36.120> things<00:03:36.300> we're 00:03:36.470 --> 00:03:36.480 align:start position:0% um so they're the kinds of things we're 00:03:36.480 --> 00:03:39.290 align:start position:0% um so they're the kinds of things we're trying<00:03:36.659> to<00:03:36.780> do<00:03:36.959> with<00:03:37.140> interrep 00:03:39.290 --> 00:03:39.300 align:start position:0% trying to do with interrep 00:03:39.300 --> 00:03:40.670 align:start position:0% trying to do with interrep now 00:03:40.670 --> 00:03:40.680 align:start position:0% now 00:03:40.680 --> 00:03:42.830 align:start position:0% now um<00:03:40.739> let's<00:03:41.640> take<00:03:41.879> a<00:03:42.000> look<00:03:42.120> at<00:03:42.360> what<00:03:42.659> the 00:03:42.830 --> 00:03:42.840 align:start position:0% um let's take a look at what the 00:03:42.840 --> 00:03:45.770 align:start position:0% um let's take a look at what the interrep<00:03:43.379> Lego<00:03:44.040> block<00:03:44.400> looks<00:03:45.000> like 00:03:45.770 --> 00:03:45.780 align:start position:0% interrep Lego block looks like 00:03:45.780 --> 00:03:48.289 align:start position:0% interrep Lego block looks like in<00:03:46.260> an<00:03:46.440> application 00:03:48.289 --> 00:03:48.299 align:start position:0% in an application 00:03:48.299 --> 00:03:50.809 align:start position:0% in an application we<00:03:49.260> have 00:03:50.809 --> 00:03:50.819 align:start position:0% we have 00:03:50.819 --> 00:03:54.170 align:start position:0% we have we<00:03:51.360> have<00:03:51.680> uh<00:03:52.680> everything<00:03:53.220> rooted<00:03:53.760> in<00:03:54.060> the 00:03:54.170 --> 00:03:54.180 align:start position:0% we have uh everything rooted in the 00:03:54.180 --> 00:03:55.670 align:start position:0% we have uh everything rooted in the blockchain 00:03:55.670 --> 00:03:55.680 align:start position:0% blockchain 00:03:55.680 --> 00:03:58.130 align:start position:0% blockchain interrep<00:03:56.519> is<00:03:56.760> the<00:03:57.000> Lego<00:03:57.180> block<00:03:57.480> on<00:03:57.780> top<00:03:57.900> of 00:03:58.130 --> 00:03:58.140 align:start position:0% interrep is the Lego block on top of 00:03:58.140 --> 00:04:00.710 align:start position:0% interrep is the Lego block on top of that<00:03:58.260> that<00:03:58.560> provides<00:03:59.040> the<00:03:59.280> identity 00:04:00.710 --> 00:04:00.720 align:start position:0% that that provides the identity 00:04:00.720 --> 00:04:04.490 align:start position:0% that that provides the identity the<00:04:01.620> identity<00:04:02.040> module 00:04:04.490 --> 00:04:04.500 align:start position:0% the identity module 00:04:04.500 --> 00:04:05.949 align:start position:0% the identity module um 00:04:05.949 --> 00:04:05.959 align:start position:0% um 00:04:05.959 --> 00:04:09.110 align:start position:0% um and<00:04:06.959> the<00:04:07.860> Lego<00:04:08.040> block<00:04:08.340> on<00:04:08.580> top<00:04:08.700> of<00:04:08.819> that<00:04:08.940> is 00:04:09.110 --> 00:04:09.120 align:start position:0% and the Lego block on top of that is 00:04:09.120 --> 00:04:12.710 align:start position:0% and the Lego block on top of that is semaphore<00:04:10.140> and<00:04:11.040> your<00:04:11.400> application 00:04:12.710 --> 00:04:12.720 align:start position:0% semaphore and your application 00:04:12.720 --> 00:04:16.430 align:start position:0% semaphore and your application hooks<00:04:13.260> into<00:04:13.379> semaphore<00:04:14.239> uh<00:04:15.239> and<00:04:15.780> with<00:04:16.199> all<00:04:16.320> of 00:04:16.430 --> 00:04:16.440 align:start position:0% hooks into semaphore uh and with all of 00:04:16.440 --> 00:04:18.530 align:start position:0% hooks into semaphore uh and with all of that<00:04:16.620> we<00:04:16.859> get<00:04:17.040> the 00:04:18.530 --> 00:04:18.540 align:start position:0% that we get the 00:04:18.540 --> 00:04:23.030 align:start position:0% that we get the um<00:04:18.859> the<00:04:19.859> identity<00:04:20.340> layer<00:04:21.000> in<00:04:21.660> interrep<00:04:22.500> we<00:04:22.919> get 00:04:23.030 --> 00:04:23.040 align:start position:0% um the identity layer in interrep we get 00:04:23.040 --> 00:04:26.689 align:start position:0% um the identity layer in interrep we get the<00:04:23.220> Privacy<00:04:23.639> layer<00:04:24.120> in<00:04:24.479> semaphore<00:04:25.460> and<00:04:26.460> we 00:04:26.689 --> 00:04:26.699 align:start position:0% the Privacy layer in semaphore and we 00:04:26.699 --> 00:04:30.170 align:start position:0% the Privacy layer in semaphore and we get<00:04:26.880> the<00:04:27.000> blockchain<00:04:27.440> so<00:04:28.759> providing<00:04:29.759> all<00:04:30.000> the 00:04:30.170 --> 00:04:30.180 align:start position:0% get the blockchain so providing all the 00:04:30.180 --> 00:04:33.830 align:start position:0% get the blockchain so providing all the all<00:04:30.840> the<00:04:31.139> guarantees 00:04:33.830 --> 00:04:33.840 align:start position:0% 00:04:33.840 --> 00:04:36.710 align:start position:0% um<00:04:33.960> interrep<00:04:34.800> will<00:04:35.460> integrate<00:04:36.300> with<00:04:36.479> those 00:04:36.710 --> 00:04:36.720 align:start position:0% um interrep will integrate with those 00:04:36.720 --> 00:04:39.770 align:start position:0% um interrep will integrate with those identity<00:04:37.259> sources<00:04:37.740> like<00:04:38.580> our<00:04:38.820> social<00:04:39.000> social 00:04:39.770 --> 00:04:39.780 align:start position:0% identity sources like our social social 00:04:39.780 --> 00:04:42.230 align:start position:0% identity sources like our social social media<00:04:40.320> accounts<00:04:40.740> and<00:04:40.919> those<00:04:41.160> kinds<00:04:41.460> of<00:04:41.520> things 00:04:42.230 --> 00:04:42.240 align:start position:0% media accounts and those kinds of things 00:04:42.240 --> 00:04:45.230 align:start position:0% media accounts and those kinds of things now<00:04:42.840> semaphore<00:04:43.680> relies<00:04:44.220> on<00:04:44.580> the<00:04:44.759> idea<00:04:45.000> of 00:04:45.230 --> 00:04:45.240 align:start position:0% now semaphore relies on the idea of 00:04:45.240 --> 00:04:47.270 align:start position:0% now semaphore relies on the idea of groups 00:04:47.270 --> 00:04:47.280 align:start position:0% groups 00:04:47.280 --> 00:04:48.469 align:start position:0% groups um 00:04:48.469 --> 00:04:48.479 align:start position:0% um 00:04:48.479 --> 00:04:49.790 align:start position:0% um you<00:04:48.960> form 00:04:49.790 --> 00:04:49.800 align:start position:0% you form 00:04:49.800 --> 00:04:52.150 align:start position:0% you form form<00:04:50.220> pre-existing<00:04:51.000> groups 00:04:52.150 --> 00:04:52.160 align:start position:0% form pre-existing groups 00:04:52.160 --> 00:04:56.570 align:start position:0% form pre-existing groups and<00:04:53.160> the<00:04:53.759> semaphore<00:04:54.300> application<00:04:54.860> will<00:04:55.860> use 00:04:56.570 --> 00:04:56.580 align:start position:0% and the semaphore application will use 00:04:56.580 --> 00:04:59.390 align:start position:0% and the semaphore application will use those<00:04:56.820> identities<00:04:57.360> in<00:04:57.660> those<00:04:57.780> groups<00:04:58.400> to 00:04:59.390 --> 00:04:59.400 align:start position:0% those identities in those groups to 00:04:59.400 --> 00:05:01.070 align:start position:0% those identities in those groups to verify 00:05:01.070 --> 00:05:01.080 align:start position:0% verify 00:05:01.080 --> 00:05:02.629 align:start position:0% verify the<00:05:01.620> kinds<00:05:01.979> of<00:05:02.100> things<00:05:02.220> that<00:05:02.460> your 00:05:02.629 --> 00:05:02.639 align:start position:0% the kinds of things that your 00:05:02.639 --> 00:05:06.110 align:start position:0% the kinds of things that your application<00:05:03.000> is<00:05:03.240> doing<00:05:03.479> so<00:05:04.380> semaphore<00:05:05.040> is 00:05:06.110 --> 00:05:06.120 align:start position:0% application is doing so semaphore is 00:05:06.120 --> 00:05:08.090 align:start position:0% application is doing so semaphore is is<00:05:06.479> a<00:05:06.780> privacy<00:05:07.199> layer 00:05:08.090 --> 00:05:08.100 align:start position:0% is a privacy layer 00:05:08.100 --> 00:05:13.030 align:start position:0% is a privacy layer so<00:05:08.759> those<00:05:09.060> groups<00:05:09.540> the<00:05:09.960> group<00:05:10.080> membership<00:05:10.560> is 00:05:13.030 --> 00:05:13.040 align:start position:0% so those groups the group membership is 00:05:13.040 --> 00:05:16.330 align:start position:0% so those groups the group membership is guaranteed<00:05:14.040> but<00:05:14.940> never<00:05:15.240> revealed<00:05:15.780> it's<00:05:16.020> never 00:05:16.330 --> 00:05:16.340 align:start position:0% guaranteed but never revealed it's never 00:05:16.340 --> 00:05:19.189 align:start position:0% guaranteed but never revealed it's never revealed<00:05:17.340> what<00:05:17.580> the<00:05:17.699> underlying<00:05:18.240> ethereum 00:05:19.189 --> 00:05:19.199 align:start position:0% revealed what the underlying ethereum 00:05:19.199 --> 00:05:20.930 align:start position:0% revealed what the underlying ethereum account<00:05:19.440> is 00:05:20.930 --> 00:05:20.940 align:start position:0% account is 00:05:20.940 --> 00:05:23.090 align:start position:0% account is so<00:05:21.960> um 00:05:23.090 --> 00:05:23.100 align:start position:0% so um 00:05:23.100 --> 00:05:25.129 align:start position:0% so um yeah<00:05:23.580> so<00:05:23.820> we'll<00:05:24.000> talk<00:05:24.180> a<00:05:24.300> bit<00:05:24.419> more<00:05:24.600> about<00:05:24.780> the 00:05:25.129 --> 00:05:25.139 align:start position:0% yeah so we'll talk a bit more about the 00:05:25.139 --> 00:05:27.170 align:start position:0% yeah so we'll talk a bit more about the the<00:05:25.259> details<00:05:26.039> of<00:05:26.160> that<00:05:26.280> a<00:05:26.460> bit<00:05:26.520> later<00:05:26.699> but 00:05:27.170 --> 00:05:27.180 align:start position:0% the details of that a bit later but 00:05:27.180 --> 00:05:29.390 align:start position:0% the details of that a bit later but that's<00:05:28.020> an<00:05:28.259> idea<00:05:28.560> of<00:05:28.680> what<00:05:28.860> your<00:05:28.979> application 00:05:29.390 --> 00:05:29.400 align:start position:0% that's an idea of what your application 00:05:29.400 --> 00:05:31.070 align:start position:0% that's an idea of what your application stack<00:05:29.820> is 00:05:31.070 --> 00:05:31.080 align:start position:0% stack is 00:05:31.080 --> 00:05:33.770 align:start position:0% stack is um<00:05:31.139> it's<00:05:31.620> yeah<00:05:31.979> it's<00:05:32.220> really<00:05:32.400> just<00:05:32.699> a<00:05:32.940> bunch<00:05:33.660> of 00:05:33.770 --> 00:05:33.780 align:start position:0% um it's yeah it's really just a bunch of 00:05:33.780 --> 00:05:37.189 align:start position:0% um it's yeah it's really just a bunch of Lego<00:05:33.900> bricks<00:05:34.740> all<00:05:34.979> plugged<00:05:35.340> together 00:05:37.189 --> 00:05:37.199 align:start position:0% Lego bricks all plugged together 00:05:37.199 --> 00:05:38.450 align:start position:0% Lego bricks all plugged together uh 00:05:38.450 --> 00:05:38.460 align:start position:0% uh 00:05:38.460 --> 00:05:41.150 align:start position:0% uh the<00:05:38.940> kinds<00:05:39.240> of<00:05:39.300> identity<00:05:40.080> providers<00:05:40.860> we've 00:05:41.150 --> 00:05:41.160 align:start position:0% the kinds of identity providers we've 00:05:41.160 --> 00:05:44.689 align:start position:0% the kinds of identity providers we've been<00:05:41.539> linking<00:05:42.539> with<00:05:42.660> so<00:05:42.960> far<00:05:43.199> uh 00:05:44.689 --> 00:05:44.699 align:start position:0% been linking with so far uh 00:05:44.699 --> 00:05:47.270 align:start position:0% been linking with so far uh these<00:05:45.419> examples<00:05:45.780> Twitter<00:05:46.199> and<00:05:46.740> Reddit<00:05:46.860> and 00:05:47.270 --> 00:05:47.280 align:start position:0% these examples Twitter and Reddit and 00:05:47.280 --> 00:05:51.230 align:start position:0% these examples Twitter and Reddit and GitHub 00:05:51.230 --> 00:05:51.240 align:start position:0% 00:05:51.240 --> 00:05:56.810 align:start position:0% so<00:05:52.080> what<00:05:52.620> we'll<00:05:52.800> do<00:05:53.039> is<00:05:53.340> a<00:05:53.759> an<00:05:54.419> oauth<00:05:54.960> uh 00:05:56.810 --> 00:05:56.820 align:start position:0% so what we'll do is a an oauth uh 00:05:56.820 --> 00:05:59.450 align:start position:0% so what we'll do is a an oauth uh verification<00:05:57.660> on<00:05:58.199> your<00:05:58.320> Twitter<00:05:58.500> account<00:05:58.860> for 00:05:59.450 --> 00:05:59.460 align:start position:0% verification on your Twitter account for 00:05:59.460 --> 00:06:02.930 align:start position:0% verification on your Twitter account for instance<00:06:00.199> and<00:06:01.199> using<00:06:01.680> that<00:06:01.800> we'll<00:06:02.220> link<00:06:02.699> it 00:06:02.930 --> 00:06:02.940 align:start position:0% instance and using that we'll link it 00:06:02.940 --> 00:06:05.510 align:start position:0% instance and using that we'll link it with<00:06:03.300> an<00:06:03.960> ethereum<00:06:04.380> account 00:06:05.510 --> 00:06:05.520 align:start position:0% with an ethereum account 00:06:05.520 --> 00:06:09.290 align:start position:0% with an ethereum account and<00:06:06.560> never<00:06:07.560> reveal<00:06:08.039> that<00:06:08.280> link 00:06:09.290 --> 00:06:09.300 align:start position:0% and never reveal that link 00:06:09.300 --> 00:06:13.010 align:start position:0% and never reveal that link but<00:06:09.780> we<00:06:10.139> we<00:06:10.620> maintain<00:06:11.100> that<00:06:11.400> that<00:06:12.060> link<00:06:12.479> that 00:06:13.010 --> 00:06:13.020 align:start position:0% but we we maintain that that link that 00:06:13.020 --> 00:06:16.189 align:start position:0% but we we maintain that that link that Twitter<00:06:13.580> handle<00:06:14.580> is<00:06:15.300> always<00:06:15.419> reflected<00:06:16.020> in 00:06:16.189 --> 00:06:16.199 align:start position:0% Twitter handle is always reflected in 00:06:16.199 --> 00:06:19.909 align:start position:0% Twitter handle is always reflected in that<00:06:16.440> in<00:06:17.220> that<00:06:17.400> ethereum<00:06:17.880> account 00:06:19.909 --> 00:06:19.919 align:start position:0% that in that ethereum account 00:06:19.919 --> 00:06:22.790 align:start position:0% that in that ethereum account uh<00:06:20.639> and<00:06:20.820> it's<00:06:20.940> easy<00:06:21.180> to<00:06:21.419> for<00:06:21.660> us<00:06:21.840> to<00:06:22.080> add<00:06:22.259> new 00:06:22.790 --> 00:06:22.800 align:start position:0% uh and it's easy to for us to add new 00:06:22.800 --> 00:06:26.570 align:start position:0% uh and it's easy to for us to add new new<00:06:23.460> providers<00:06:24.120> is<00:06:24.419> really<00:06:24.720> just<00:06:25.100> it's<00:06:26.100> an 00:06:26.570 --> 00:06:26.580 align:start position:0% new providers is really just it's an 00:06:26.580 --> 00:06:28.870 align:start position:0% new providers is really just it's an oauth<00:06:27.199> verification 00:06:28.870 --> 00:06:28.880 align:start position:0% oauth verification 00:06:28.880 --> 00:06:31.490 align:start position:0% oauth verification and<00:06:29.880> some<00:06:30.240> rules<00:06:30.539> about 00:06:31.490 --> 00:06:31.500 align:start position:0% and some rules about 00:06:31.500 --> 00:06:32.150 align:start position:0% and some rules about um 00:06:32.150 --> 00:06:32.160 align:start position:0% um 00:06:32.160 --> 00:06:34.430 align:start position:0% um you<00:06:32.639> know<00:06:32.699> what's<00:06:33.300> a<00:06:33.539> qualified<00:06:33.780> account<00:06:34.020> or 00:06:34.430 --> 00:06:34.440 align:start position:0% you know what's a qualified account or 00:06:34.440 --> 00:06:36.230 align:start position:0% you know what's a qualified account or what<00:06:34.620> does<00:06:34.800> it<00:06:34.919> look<00:06:35.100> like<00:06:35.220> a<00:06:35.400> bot<00:06:35.639> does<00:06:35.940> it<00:06:36.060> not 00:06:36.230 --> 00:06:36.240 align:start position:0% what does it look like a bot does it not 00:06:36.240 --> 00:06:39.830 align:start position:0% what does it look like a bot does it not does<00:06:36.960> it<00:06:37.139> look<00:06:37.259> like<00:06:37.380> a<00:06:37.560> human 00:06:39.830 --> 00:06:39.840 align:start position:0% 00:06:39.840 --> 00:06:42.529 align:start position:0% um<00:06:39.960> we<00:06:40.440> can<00:06:40.620> also<00:06:41.039> integrate<00:06:41.520> with 00:06:42.529 --> 00:06:42.539 align:start position:0% um we can also integrate with 00:06:42.539 --> 00:06:44.749 align:start position:0% um we can also integrate with other<00:06:43.020> providers 00:06:44.749 --> 00:06:44.759 align:start position:0% other providers 00:06:44.759 --> 00:06:48.050 align:start position:0% other providers we<00:06:45.479> could<00:06:45.600> use<00:06:45.840> email<00:06:46.259> as<00:06:46.740> a<00:06:46.919> as<00:06:47.220> a 00:06:48.050 --> 00:06:48.060 align:start position:0% we could use email as a as a 00:06:48.060 --> 00:06:52.309 align:start position:0% we could use email as a as a an<00:06:48.960> identity<00:06:49.440> source<00:06:49.919> and<00:06:50.639> this<00:06:50.940> is<00:06:51.479> useful<00:06:51.780> in 00:06:52.309 --> 00:06:52.319 align:start position:0% an identity source and this is useful in 00:06:52.319 --> 00:06:54.590 align:start position:0% an identity source and this is useful in some<00:06:52.620> cases<00:06:53.039> not<00:06:53.400> in<00:06:53.759> others<00:06:54.060> maybe<00:06:54.180> it's<00:06:54.360> not 00:06:54.590 --> 00:06:54.600 align:start position:0% some cases not in others maybe it's not 00:06:54.600 --> 00:06:57.529 align:start position:0% some cases not in others maybe it's not so<00:06:54.780> useful<00:06:55.080> for<00:06:55.979> Gmail<00:06:56.220> accounts<00:06:56.880> but<00:06:57.120> even 00:06:57.529 --> 00:06:57.539 align:start position:0% so useful for Gmail accounts but even 00:06:57.539 --> 00:07:00.529 align:start position:0% so useful for Gmail accounts but even Gmail<00:06:57.900> has<00:06:58.380> some<00:06:58.620> barriers<00:06:58.979> to<00:06:59.160> entry<00:06:59.580> so<00:06:59.819> but 00:07:00.529 --> 00:07:00.539 align:start position:0% Gmail has some barriers to entry so but 00:07:00.539 --> 00:07:02.710 align:start position:0% Gmail has some barriers to entry so but if<00:07:00.720> you've<00:07:00.840> got<00:07:00.960> like<00:07:01.199> a<00:07:01.440> DOT<00:07:01.740> edu<00:07:02.220> account 00:07:02.710 --> 00:07:02.720 align:start position:0% if you've got like a DOT edu account 00:07:02.720 --> 00:07:05.770 align:start position:0% if you've got like a DOT edu account email<00:07:03.720> account<00:07:04.080> then<00:07:04.740> that's<00:07:04.979> a<00:07:05.220> fairly<00:07:05.520> good 00:07:05.770 --> 00:07:05.780 align:start position:0% email account then that's a fairly good 00:07:05.780 --> 00:07:07.909 align:start position:0% email account then that's a fairly good guarantee<00:07:06.780> that<00:07:07.020> there's<00:07:07.199> a<00:07:07.380> human<00:07:07.500> behind 00:07:07.909 --> 00:07:07.919 align:start position:0% guarantee that there's a human behind 00:07:07.919 --> 00:07:11.450 align:start position:0% guarantee that there's a human behind that<00:07:08.100> account<00:07:08.280> and<00:07:09.240> and<00:07:10.139> a<00:07:10.680> reasonably<00:07:11.160> good 00:07:11.450 --> 00:07:11.460 align:start position:0% that account and and a reasonably good 00:07:11.460 --> 00:07:14.270 align:start position:0% that account and and a reasonably good guarantee<00:07:11.940> of<00:07:12.180> uniqueness<00:07:12.780> so<00:07:13.740> we<00:07:13.979> can<00:07:14.160> use 00:07:14.270 --> 00:07:14.280 align:start position:0% guarantee of uniqueness so we can use 00:07:14.280 --> 00:07:17.390 align:start position:0% guarantee of uniqueness so we can use those<00:07:14.520> kinds<00:07:14.759> of<00:07:14.880> sources<00:07:15.919> and<00:07:16.919> integrate 00:07:17.390 --> 00:07:17.400 align:start position:0% those kinds of sources and integrate 00:07:17.400 --> 00:07:20.510 align:start position:0% those kinds of sources and integrate with<00:07:17.580> those<00:07:18.080> government<00:07:19.080> authorities 00:07:20.510 --> 00:07:20.520 align:start position:0% with those government authorities 00:07:20.520 --> 00:07:23.749 align:start position:0% with those government authorities are<00:07:21.240> good<00:07:21.539> in<00:07:22.080> that 00:07:23.749 --> 00:07:23.759 align:start position:0% are good in that 00:07:23.759 --> 00:07:24.830 align:start position:0% are good in that um 00:07:24.830 --> 00:07:24.840 align:start position:0% um 00:07:24.840 --> 00:07:27.589 align:start position:0% um you<00:07:25.800> know<00:07:25.860> the<00:07:25.979> government<00:07:26.099> make<00:07:26.520> sure<00:07:26.759> you 00:07:27.589 --> 00:07:27.599 align:start position:0% you know the government make sure you 00:07:27.599 --> 00:07:29.210 align:start position:0% you know the government make sure you only<00:07:27.780> have<00:07:27.960> one<00:07:28.139> driver's<00:07:28.620> license<00:07:28.800> for 00:07:29.210 --> 00:07:29.220 align:start position:0% only have one driver's license for 00:07:29.220 --> 00:07:32.450 align:start position:0% only have one driver's license for instance<00:07:29.539> uh<00:07:30.539> and<00:07:30.900> there's<00:07:31.199> there's<00:07:31.500> a<00:07:32.340> strong 00:07:32.450 --> 00:07:32.460 align:start position:0% instance uh and there's there's a strong 00:07:32.460 --> 00:07:34.010 align:start position:0% instance uh and there's there's a strong guarantee<00:07:32.880> there's<00:07:33.120> a<00:07:33.360> human<00:07:33.479> behind<00:07:33.840> that 00:07:34.010 --> 00:07:34.020 align:start position:0% guarantee there's a human behind that 00:07:34.020 --> 00:07:36.529 align:start position:0% guarantee there's a human behind that driver's<00:07:34.440> license<00:07:34.620> so<00:07:35.400> if<00:07:35.520> we<00:07:35.759> can<00:07:35.880> we<00:07:36.360> can 00:07:36.529 --> 00:07:36.539 align:start position:0% driver's license so if we can we can 00:07:36.539 --> 00:07:38.150 align:start position:0% driver's license so if we can we can integrate<00:07:36.960> with<00:07:37.139> those<00:07:37.319> kinds<00:07:37.620> of<00:07:37.680> sources 00:07:38.150 --> 00:07:38.160 align:start position:0% integrate with those kinds of sources 00:07:38.160 --> 00:07:40.730 align:start position:0% integrate with those kinds of sources and<00:07:38.819> it<00:07:38.940> also<00:07:39.240> includes<00:07:39.900> the<00:07:40.259> people<00:07:40.380> who 00:07:40.730 --> 00:07:40.740 align:start position:0% and it also includes the people who 00:07:40.740 --> 00:07:43.450 align:start position:0% and it also includes the people who don't<00:07:40.979> use<00:07:41.400> social<00:07:42.120> media 00:07:43.450 --> 00:07:43.460 align:start position:0% don't use social media 00:07:43.460 --> 00:07:45.230 align:start position:0% don't use social media so 00:07:45.230 --> 00:07:45.240 align:start position:0% so 00:07:45.240 --> 00:07:48.710 align:start position:0% so that's<00:07:45.599> another<00:07:45.840> approach<00:07:46.380> we<00:07:46.740> have 00:07:48.710 --> 00:07:48.720 align:start position:0% that's another approach we have 00:07:48.720 --> 00:07:51.350 align:start position:0% that's another approach we have um<00:07:48.840> we<00:07:49.500> can<00:07:49.620> do<00:07:49.800> things<00:07:49.979> like<00:07:50.220> curating<00:07:50.759> groups 00:07:51.350 --> 00:07:51.360 align:start position:0% um we can do things like curating groups 00:07:51.360 --> 00:07:53.089 align:start position:0% um we can do things like curating groups of 00:07:53.089 --> 00:07:53.099 align:start position:0% of 00:07:53.099 --> 00:07:55.430 align:start position:0% of of<00:07:54.539> um 00:07:55.430 --> 00:07:55.440 align:start position:0% of um 00:07:55.440 --> 00:07:58.189 align:start position:0% of um users<00:07:56.340> so<00:07:56.819> that<00:07:57.240> might<00:07:57.479> rely<00:07:57.840> on<00:07:57.960> personal 00:07:58.189 --> 00:07:58.199 align:start position:0% users so that might rely on personal 00:07:58.199 --> 00:08:01.370 align:start position:0% users so that might rely on personal knowledge<00:07:58.680> of<00:07:59.039> of<00:07:59.819> uh<00:08:00.539> of<00:08:00.780> the<00:08:00.900> individuals 00:08:01.370 --> 00:08:01.380 align:start position:0% knowledge of of uh of the individuals 00:08:01.380 --> 00:08:04.129 align:start position:0% knowledge of of uh of the individuals involved<00:08:01.979> so<00:08:02.580> that's<00:08:03.000> that's<00:08:03.300> also<00:08:03.780> a<00:08:03.900> strong 00:08:04.129 --> 00:08:04.139 align:start position:0% involved so that's that's also a strong 00:08:04.139 --> 00:08:06.070 align:start position:0% involved so that's that's also a strong way<00:08:04.319> to<00:08:04.560> guarantee<00:08:04.860> Humanity 00:08:06.070 --> 00:08:06.080 align:start position:0% way to guarantee Humanity 00:08:06.080 --> 00:08:08.870 align:start position:0% way to guarantee Humanity other<00:08:07.080> ID<00:08:07.440> projects<00:08:07.979> we<00:08:08.160> can<00:08:08.280> integrate<00:08:08.639> with 00:08:08.870 --> 00:08:08.880 align:start position:0% other ID projects we can integrate with 00:08:08.880 --> 00:08:12.230 align:start position:0% other ID projects we can integrate with those<00:08:09.259> and<00:08:10.259> we<00:08:10.500> can<00:08:10.880> integrate<00:08:11.880> with 00:08:12.230 --> 00:08:12.240 align:start position:0% those and we can integrate with 00:08:12.240 --> 00:08:15.409 align:start position:0% those and we can integrate with Unchained<00:08:13.020> sources<00:08:13.500> like<00:08:14.400> use<00:08:15.060> things<00:08:15.240> like 00:08:15.409 --> 00:08:15.419 align:start position:0% Unchained sources like use things like 00:08:15.419 --> 00:08:19.790 align:start position:0% Unchained sources like use things like nft<00:08:15.780> ownership<00:08:16.319> that<00:08:16.680> kind<00:08:16.860> of<00:08:16.979> thing 00:08:19.790 --> 00:08:19.800 align:start position:0% 00:08:19.800 --> 00:08:23.830 align:start position:0% now<00:08:20.280> a<00:08:20.460> bit<00:08:20.580> about<00:08:20.699> semaphore<00:08:21.479> so<00:08:22.440> with<00:08:22.919> those 00:08:23.830 --> 00:08:23.840 align:start position:0% now a bit about semaphore so with those 00:08:23.840 --> 00:08:27.409 align:start position:0% now a bit about semaphore so with those identity<00:08:24.840> sources<00:08:25.379> we<00:08:25.680> create<00:08:25.860> a<00:08:26.520> group 00:08:27.409 --> 00:08:27.419 align:start position:0% identity sources we create a group 00:08:27.419 --> 00:08:31.129 align:start position:0% identity sources we create a group we<00:08:28.139> put<00:08:28.379> someone<00:08:28.560> into<00:08:28.860> a<00:08:29.099> group 00:08:31.129 --> 00:08:31.139 align:start position:0% we put someone into a group 00:08:31.139 --> 00:08:34.630 align:start position:0% we put someone into a group now<00:08:31.740> semaphore<00:08:32.219> relies<00:08:32.580> on<00:08:32.700> these<00:08:32.940> groups 00:08:34.630 --> 00:08:34.640 align:start position:0% now semaphore relies on these groups 00:08:34.640 --> 00:08:38.230 align:start position:0% now semaphore relies on these groups semaphore<00:08:35.640> groups<00:08:36.180> uh 00:08:38.230 --> 00:08:38.240 align:start position:0% semaphore groups uh 00:08:38.240 --> 00:08:41.209 align:start position:0% semaphore groups uh membership<00:08:39.240> sets<00:08:39.839> so 00:08:41.209 --> 00:08:41.219 align:start position:0% membership sets so 00:08:41.219 --> 00:08:45.070 align:start position:0% membership sets so um<00:08:41.760> there<00:08:42.300> are<00:08:42.419> guarantees<00:08:43.200> of 00:08:45.070 --> 00:08:45.080 align:start position:0% um there are guarantees of 00:08:45.080 --> 00:08:47.690 align:start position:0% um there are guarantees of once<00:08:46.080> you're<00:08:46.140> in<00:08:46.320> that<00:08:46.440> set<00:08:46.620> you're<00:08:47.220> you're 00:08:47.690 --> 00:08:47.700 align:start position:0% once you're in that set you're you're 00:08:47.700 --> 00:08:50.690 align:start position:0% once you're in that set you're you're expected<00:08:48.240> to<00:08:48.480> be<00:08:48.680> you<00:08:49.680> know<00:08:49.740> anyone<00:08:50.519> can 00:08:50.690 --> 00:08:50.700 align:start position:0% expected to be you know anyone can 00:08:50.700 --> 00:08:53.690 align:start position:0% expected to be you know anyone can expect<00:08:51.000> that<00:08:51.959> that 00:08:53.690 --> 00:08:53.700 align:start position:0% expect that that 00:08:53.700 --> 00:08:58.730 align:start position:0% expect that that identity<00:08:54.600> to<00:08:55.260> be<00:08:55.500> to<00:08:56.279> have<00:08:56.459> a<00:08:56.640> human<00:08:56.700> behind<00:08:57.180> it 00:08:58.730 --> 00:08:58.740 align:start position:0% identity to be to have a human behind it 00:08:58.740 --> 00:08:59.829 align:start position:0% identity to be to have a human behind it um 00:08:59.829 --> 00:08:59.839 align:start position:0% um 00:08:59.839 --> 00:09:03.110 align:start position:0% um so<00:09:00.839> and<00:09:01.200> with<00:09:01.380> semaphore<00:09:01.980> it's<00:09:02.459> a<00:09:02.700> generic 00:09:03.110 --> 00:09:03.120 align:start position:0% so and with semaphore it's a generic 00:09:03.120 --> 00:09:05.150 align:start position:0% so and with semaphore it's a generic framework 00:09:05.150 --> 00:09:05.160 align:start position:0% framework 00:09:05.160 --> 00:09:08.630 align:start position:0% framework um<00:09:05.760> in<00:09:06.420> which<00:09:06.800> members<00:09:07.800> in<00:09:08.160> that<00:09:08.339> membership 00:09:08.630 --> 00:09:08.640 align:start position:0% um in which members in that membership 00:09:08.640 --> 00:09:09.650 align:start position:0% um in which members in that membership set 00:09:09.650 --> 00:09:09.660 align:start position:0% set 00:09:09.660 --> 00:09:14.269 align:start position:0% set can<00:09:10.500> signal<00:09:11.339> on<00:09:12.300> a<00:09:12.420> topic<00:09:12.779> and<00:09:13.740> that<00:09:13.920> apply 00:09:14.269 --> 00:09:14.279 align:start position:0% can signal on a topic and that apply 00:09:14.279 --> 00:09:16.610 align:start position:0% can signal on a topic and that apply that<00:09:14.640> can<00:09:14.760> be<00:09:14.880> applied<00:09:15.180> in<00:09:15.420> multiple<00:09:15.959> ways<00:09:16.320> but 00:09:16.610 --> 00:09:16.620 align:start position:0% that can be applied in multiple ways but 00:09:16.620 --> 00:09:19.850 align:start position:0% that can be applied in multiple ways but an<00:09:17.160> easy<00:09:17.339> to<00:09:17.640> grasp<00:09:18.060> example<00:09:18.959> would<00:09:19.200> be<00:09:19.320> a<00:09:19.500> dow 00:09:19.850 --> 00:09:19.860 align:start position:0% an easy to grasp example would be a dow 00:09:19.860 --> 00:09:23.350 align:start position:0% an easy to grasp example would be a dow that<00:09:20.640> has<00:09:20.820> votes<00:09:21.180> on<00:09:21.300> proposals 00:09:23.350 --> 00:09:23.360 align:start position:0% that has votes on proposals 00:09:23.360 --> 00:09:28.610 align:start position:0% that has votes on proposals in<00:09:24.360> that<00:09:24.720> situation<00:09:25.519> a<00:09:26.519> signal<00:09:26.940> is<00:09:27.300> a<00:09:27.480> vote<00:09:27.720> and 00:09:28.610 --> 00:09:28.620 align:start position:0% in that situation a signal is a vote and 00:09:28.620 --> 00:09:31.550 align:start position:0% in that situation a signal is a vote and the<00:09:28.800> topic<00:09:29.100> is<00:09:29.279> a<00:09:29.459> proposal<00:09:29.940> and<00:09:30.899> semaphore 00:09:31.550 --> 00:09:31.560 align:start position:0% the topic is a proposal and semaphore 00:09:31.560 --> 00:09:33.670 align:start position:0% the topic is a proposal and semaphore will<00:09:31.800> guarantee<00:09:32.220> that 00:09:33.670 --> 00:09:33.680 align:start position:0% will guarantee that 00:09:33.680 --> 00:09:37.850 align:start position:0% will guarantee that that<00:09:34.680> anyone<00:09:35.160> who<00:09:35.339> votes<00:09:35.760> is<00:09:36.839> a<00:09:37.440> member<00:09:37.740> of 00:09:37.850 --> 00:09:37.860 align:start position:0% that anyone who votes is a member of 00:09:37.860 --> 00:09:38.930 align:start position:0% that anyone who votes is a member of that 00:09:38.930 --> 00:09:38.940 align:start position:0% that 00:09:38.940 --> 00:09:40.490 align:start position:0% that group 00:09:40.490 --> 00:09:40.500 align:start position:0% group 00:09:40.500 --> 00:09:42.949 align:start position:0% group and<00:09:40.980> they<00:09:41.100> can<00:09:41.279> only<00:09:41.399> vote<00:09:41.640> once 00:09:42.949 --> 00:09:42.959 align:start position:0% and they can only vote once 00:09:42.959 --> 00:09:45.230 align:start position:0% and they can only vote once and<00:09:43.800> all<00:09:43.920> of<00:09:44.040> that<00:09:44.220> is 00:09:45.230 --> 00:09:45.240 align:start position:0% and all of that is 00:09:45.240 --> 00:09:47.990 align:start position:0% and all of that is is 00:09:47.990 --> 00:09:48.000 align:start position:0% 00:09:48.000 --> 00:09:50.690 align:start position:0% done<00:09:48.600> with<00:09:48.779> privacy<00:09:49.260> so<00:09:49.620> you<00:09:49.860> don't<00:09:49.980> know<00:09:50.160> who 00:09:50.690 --> 00:09:50.700 align:start position:0% done with privacy so you don't know who 00:09:50.700 --> 00:09:53.290 align:start position:0% done with privacy so you don't know who is<00:09:51.480> voting<00:09:51.899> on<00:09:52.019> a<00:09:52.200> particular 00:09:53.290 --> 00:09:53.300 align:start position:0% is voting on a particular 00:09:53.300 --> 00:09:56.230 align:start position:0% is voting on a particular voting<00:09:54.300> in<00:09:54.600> a<00:09:54.959> particular<00:09:55.200> direction 00:09:56.230 --> 00:09:56.240 align:start position:0% voting in a particular direction 00:09:56.240 --> 00:09:59.889 align:start position:0% voting in a particular direction so<00:09:57.240> it<00:09:57.959> can<00:09:58.140> support<00:09:58.320> secret<00:09:58.680> votes 00:09:59.889 --> 00:09:59.899 align:start position:0% so it can support secret votes 00:09:59.899 --> 00:10:02.509 align:start position:0% so it can support secret votes but<00:10:00.899> it<00:10:01.140> still<00:10:01.320> maintains<00:10:01.800> strong<00:10:02.040> guarantees 00:10:02.509 --> 00:10:02.519 align:start position:0% but it still maintains strong guarantees 00:10:02.519 --> 00:10:04.370 align:start position:0% but it still maintains strong guarantees of 00:10:04.370 --> 00:10:04.380 align:start position:0% of 00:10:04.380 --> 00:10:08.530 align:start position:0% of um membership<00:10:04.920> in<00:10:05.160> that<00:10:05.339> set 00:10:08.530 --> 00:10:08.540 align:start position:0% 00:10:08.540 --> 00:10:12.590 align:start position:0% uh<00:10:09.540> so<00:10:09.779> this<00:10:10.620> yeah<00:10:10.980> the<00:10:11.160> semaphore<00:10:11.700> framework 00:10:12.590 --> 00:10:12.600 align:start position:0% uh so this yeah the semaphore framework 00:10:12.600 --> 00:10:16.250 align:start position:0% uh so this yeah the semaphore framework gets<00:10:12.959> used<00:10:13.019> in<00:10:13.200> lots<00:10:13.500> of<00:10:13.560> ways<00:10:13.860> but<00:10:14.820> uh 00:10:16.250 --> 00:10:16.260 align:start position:0% gets used in lots of ways but uh 00:10:16.260 --> 00:10:18.949 align:start position:0% gets used in lots of ways but uh the<00:10:16.800> group<00:10:16.980> membership 00:10:18.949 --> 00:10:18.959 align:start position:0% the group membership 00:10:18.959 --> 00:10:21.350 align:start position:0% the group membership part<00:10:19.320> of<00:10:19.440> semaphore<00:10:19.920> semaphore<00:10:20.640> playing 00:10:21.350 --> 00:10:21.360 align:start position:0% part of semaphore semaphore playing 00:10:21.360 --> 00:10:24.110 align:start position:0% part of semaphore semaphore playing vanilla<00:10:21.899> semaphore<00:10:22.380> has<00:10:22.740> its<00:10:23.160> own<00:10:23.279> group 00:10:24.110 --> 00:10:24.120 align:start position:0% vanilla semaphore has its own group 00:10:24.120 --> 00:10:26.750 align:start position:0% vanilla semaphore has its own group management<00:10:24.420> but<00:10:25.380> what<00:10:25.620> we<00:10:25.800> do<00:10:25.920> with<00:10:26.160> interrep 00:10:26.750 --> 00:10:26.760 align:start position:0% management but what we do with interrep 00:10:26.760 --> 00:10:29.810 align:start position:0% management but what we do with interrep is<00:10:27.560> semaphore<00:10:28.560> outsources<00:10:29.279> the<00:10:29.580> group 00:10:29.810 --> 00:10:29.820 align:start position:0% is semaphore outsources the group 00:10:29.820 --> 00:10:32.810 align:start position:0% is semaphore outsources the group management<00:10:30.060> to<00:10:30.959> interrupt 00:10:32.810 --> 00:10:32.820 align:start position:0% management to interrupt 00:10:32.820 --> 00:10:34.910 align:start position:0% management to interrupt and<00:10:33.420> then<00:10:33.540> that's 00:10:34.910 --> 00:10:34.920 align:start position:0% and then that's 00:10:34.920 --> 00:10:37.730 align:start position:0% and then that's that's<00:10:36.300> um 00:10:37.730 --> 00:10:37.740 align:start position:0% that's um 00:10:37.740 --> 00:10:40.910 align:start position:0% that's um interf<00:10:38.519> itself<00:10:38.880> is<00:10:39.120> is 00:10:40.910 --> 00:10:40.920 align:start position:0% interf itself is is 00:10:40.920 --> 00:10:44.569 align:start position:0% interf itself is is basing<00:10:41.640> its<00:10:42.060> identity<00:10:42.480> groups<00:10:43.200> on<00:10:44.040> for 00:10:44.569 --> 00:10:44.579 align:start position:0% basing its identity groups on for 00:10:44.579 --> 00:10:46.850 align:start position:0% basing its identity groups on for instance<00:10:44.820> on<00:10:45.420> Twitter<00:10:45.959> membership<00:10:46.560> and 00:10:46.850 --> 00:10:46.860 align:start position:0% instance on Twitter membership and 00:10:46.860 --> 00:10:49.190 align:start position:0% instance on Twitter membership and GitHub<00:10:47.399> membership<00:10:47.820> and<00:10:48.060> so<00:10:48.240> on 00:10:49.190 --> 00:10:49.200 align:start position:0% GitHub membership and so on 00:10:49.200 --> 00:10:51.050 align:start position:0% GitHub membership and so on so 00:10:51.050 --> 00:10:51.060 align:start position:0% so 00:10:51.060 --> 00:10:52.310 align:start position:0% so um 00:10:52.310 --> 00:10:52.320 align:start position:0% um 00:10:52.320 --> 00:10:57.910 align:start position:0% um the<00:10:52.680> way<00:10:52.800> that<00:10:52.980> works<00:10:53.279> is<00:10:53.459> users<00:10:54.240> will 00:10:57.910 --> 00:10:57.920 align:start position:0% 00:10:57.920 --> 00:11:00.410 align:start position:0% prove<00:10:58.920> their<00:10:59.040> membership 00:11:00.410 --> 00:11:00.420 align:start position:0% prove their membership 00:11:00.420 --> 00:11:04.449 align:start position:0% prove their membership on<00:11:01.079> that<00:11:01.260> in<00:11:01.620> that<00:11:01.800> social<00:11:01.980> network 00:11:04.449 --> 00:11:04.459 align:start position:0% 00:11:04.459 --> 00:11:07.670 align:start position:0% identity<00:11:05.459> source 00:11:07.670 --> 00:11:07.680 align:start position:0% identity source 00:11:07.680 --> 00:11:08.810 align:start position:0% identity source um 00:11:08.810 --> 00:11:08.820 align:start position:0% um 00:11:08.820 --> 00:11:10.790 align:start position:0% um h 00:11:10.790 --> 00:11:10.800 align:start position:0% h 00:11:10.800 --> 00:11:13.850 align:start position:0% h so<00:11:11.279> that<00:11:11.459> will<00:11:11.640> form<00:11:11.760> a<00:11:11.940> Twitter<00:11:12.120> group<00:11:12.480> but<00:11:13.380> we 00:11:13.850 --> 00:11:13.860 align:start position:0% so that will form a Twitter group but we 00:11:13.860 --> 00:11:16.190 align:start position:0% so that will form a Twitter group but we subdivide<00:11:14.700> that<00:11:14.880> into 00:11:16.190 --> 00:11:16.200 align:start position:0% subdivide that into 00:11:16.200 --> 00:11:17.870 align:start position:0% subdivide that into tears 00:11:17.870 --> 00:11:17.880 align:start position:0% tears 00:11:17.880 --> 00:11:21.889 align:start position:0% tears which<00:11:18.720> basically<00:11:19.140> represent<00:11:20.000> a<00:11:21.000> level<00:11:21.600> of 00:11:21.889 --> 00:11:21.899 align:start position:0% which basically represent a level of 00:11:21.899 --> 00:11:24.410 align:start position:0% which basically represent a level of confidence<00:11:22.320> that<00:11:23.279> there<00:11:23.459> is<00:11:23.579> a<00:11:23.700> human<00:11:23.880> behind 00:11:24.410 --> 00:11:24.420 align:start position:0% confidence that there is a human behind 00:11:24.420 --> 00:11:28.130 align:start position:0% confidence that there is a human behind that<00:11:25.260> behind<00:11:25.740> that<00:11:25.920> ID<00:11:26.160> and<00:11:27.000> as<00:11:27.180> we<00:11:27.360> know<00:11:27.540> uh 00:11:28.130 --> 00:11:28.140 align:start position:0% that behind that ID and as we know uh 00:11:28.140 --> 00:11:32.829 align:start position:0% that behind that ID and as we know uh Twitter<00:11:28.440> is<00:11:29.160> riddled<00:11:29.760> with<00:11:29.940> Bots 00:11:32.829 --> 00:11:32.839 align:start position:0% Twitter is riddled with Bots 00:11:32.839 --> 00:11:36.170 align:start position:0% Twitter is riddled with Bots so<00:11:33.839> we<00:11:33.959> will<00:11:34.140> just<00:11:34.260> apply<00:11:34.560> rules<00:11:34.980> to<00:11:35.880> filter 00:11:36.170 --> 00:11:36.180 align:start position:0% so we will just apply rules to filter 00:11:36.180 --> 00:11:37.610 align:start position:0% so we will just apply rules to filter out 00:11:37.610 --> 00:11:37.620 align:start position:0% out 00:11:37.620 --> 00:11:39.910 align:start position:0% out the<00:11:38.220> spots<00:11:38.640> as<00:11:38.700> best<00:11:38.880> we<00:11:39.120> can 00:11:39.910 --> 00:11:39.920 align:start position:0% the spots as best we can 00:11:39.920 --> 00:11:41.810 align:start position:0% the spots as best we can we<00:11:40.920> won't 00:11:41.810 --> 00:11:41.820 align:start position:0% we won't 00:11:41.820 --> 00:11:43.490 align:start position:0% we won't we're<00:11:42.180> not<00:11:42.300> going<00:11:42.420> to<00:11:42.480> say<00:11:42.600> it's<00:11:42.720> perfect<00:11:43.019> but 00:11:43.490 --> 00:11:43.500 align:start position:0% we're not going to say it's perfect but 00:11:43.500 --> 00:11:46.310 align:start position:0% we're not going to say it's perfect but we'll<00:11:44.040> get<00:11:44.279> pretty<00:11:44.459> close<00:11:44.899> good<00:11:45.899> enough<00:11:46.079> for 00:11:46.310 --> 00:11:46.320 align:start position:0% we'll get pretty close good enough for 00:11:46.320 --> 00:11:47.889 align:start position:0% we'll get pretty close good enough for most<00:11:46.680> applications 00:11:47.889 --> 00:11:47.899 align:start position:0% most applications 00:11:47.899 --> 00:11:50.750 align:start position:0% most applications the<00:11:48.899> way<00:11:49.019> we<00:11:49.200> do<00:11:49.440> that<00:11:49.680> for<00:11:50.279> instance<00:11:50.399> with 00:11:50.750 --> 00:11:50.760 align:start position:0% the way we do that for instance with 00:11:50.760 --> 00:11:52.190 align:start position:0% the way we do that for instance with Twitter 00:11:52.190 --> 00:11:52.200 align:start position:0% Twitter 00:11:52.200 --> 00:11:56.090 align:start position:0% Twitter is<00:11:53.420> we'll<00:11:54.420> have<00:11:54.660> a 00:11:56.090 --> 00:11:56.100 align:start position:0% is we'll have a 00:11:56.100 --> 00:11:58.730 align:start position:0% is we'll have a we<00:11:56.519> have<00:11:56.760> some<00:11:57.120> criteria<00:11:57.779> that<00:11:58.140> we<00:11:58.380> apply 00:11:58.730 --> 00:11:58.740 align:start position:0% we have some criteria that we apply 00:11:58.740 --> 00:12:00.430 align:start position:0% we have some criteria that we apply ourselves 00:12:00.430 --> 00:12:00.440 align:start position:0% ourselves 00:12:00.440 --> 00:12:02.990 align:start position:0% ourselves with<00:12:01.440> Twitter<00:12:01.620> it's<00:12:01.920> a 00:12:02.990 --> 00:12:03.000 align:start position:0% with Twitter it's a 00:12:03.000 --> 00:12:06.850 align:start position:0% with Twitter it's a a<00:12:03.420> fairly<00:12:03.899> High<00:12:04.079> bar<00:12:04.320> to<00:12:04.560> getting<00:12:04.740> gold<00:12:05.220> status 00:12:06.850 --> 00:12:06.860 align:start position:0% a fairly High bar to getting gold status 00:12:06.860 --> 00:12:10.090 align:start position:0% a fairly High bar to getting gold status you'd<00:12:07.860> need<00:12:08.040> 7<00:12:08.579> 000<00:12:08.640> followers 00:12:10.090 --> 00:12:10.100 align:start position:0% you'd need 7 000 followers 00:12:10.100 --> 00:12:12.530 align:start position:0% you'd need 7 000 followers with<00:12:11.100> 2<00:12:11.459> 000<00:12:11.519> followers<00:12:11.940> you'd<00:12:12.180> be<00:12:12.300> silver 00:12:12.530 --> 00:12:12.540 align:start position:0% with 2 000 followers you'd be silver 00:12:12.540 --> 00:12:15.470 align:start position:0% with 2 000 followers you'd be silver with<00:12:13.500> less<00:12:13.800> than<00:12:13.980> that<00:12:14.160> you'd<00:12:14.579> be 00:12:15.470 --> 00:12:15.480 align:start position:0% with less than that you'd be 00:12:15.480 --> 00:12:20.690 align:start position:0% with less than that you'd be uh<00:12:16.320> bronze<00:12:16.980> but<00:12:17.940> we<00:12:18.720> also<00:12:19.519> linked<00:12:20.519> to 00:12:20.690 --> 00:12:20.700 align:start position:0% uh bronze but we also linked to 00:12:20.700 --> 00:12:22.130 align:start position:0% uh bronze but we also linked to botometer 00:12:22.130 --> 00:12:22.140 align:start position:0% botometer 00:12:22.140 --> 00:12:23.930 align:start position:0% botometer and<00:12:22.560> that<00:12:22.740> will<00:12:22.860> do<00:12:23.100> an<00:12:23.220> assessment<00:12:23.579> of<00:12:23.760> your 00:12:23.930 --> 00:12:23.940 align:start position:0% and that will do an assessment of your 00:12:23.940 --> 00:12:26.389 align:start position:0% and that will do an assessment of your Twitter<00:12:24.120> account<00:12:24.620> and<00:12:25.620> for<00:12:25.860> most<00:12:26.040> people 00:12:26.389 --> 00:12:26.399 align:start position:0% Twitter account and for most people 00:12:26.399 --> 00:12:28.190 align:start position:0% Twitter account and for most people that's<00:12:27.300> gonna 00:12:28.190 --> 00:12:28.200 align:start position:0% that's gonna 00:12:28.200 --> 00:12:29.750 align:start position:0% that's gonna that's 00:12:29.750 --> 00:12:29.760 align:start position:0% that's 00:12:29.760 --> 00:12:31.910 align:start position:0% that's that's<00:12:30.120> going<00:12:30.420> to<00:12:30.540> give<00:12:30.660> us<00:12:30.779> a<00:12:30.959> score 00:12:31.910 --> 00:12:31.920 align:start position:0% that's going to give us a score 00:12:31.920 --> 00:12:35.750 align:start position:0% that's going to give us a score on<00:12:32.459> how<00:12:32.760> much<00:12:32.880> botometer<00:12:34.200> uh 00:12:35.750 --> 00:12:35.760 align:start position:0% on how much botometer uh 00:12:35.760 --> 00:12:38.990 align:start position:0% on how much botometer uh how<00:12:36.660> confident<00:12:37.320> they<00:12:37.680> are<00:12:37.800> that<00:12:38.100> you<00:12:38.339> are<00:12:38.579> not 00:12:38.990 --> 00:12:39.000 align:start position:0% how confident they are that you are not 00:12:39.000 --> 00:12:40.690 align:start position:0% how confident they are that you are not a<00:12:39.240> bot 00:12:40.690 --> 00:12:40.700 align:start position:0% a bot 00:12:40.700 --> 00:12:44.210 align:start position:0% a bot so<00:12:41.700> most<00:12:42.660> people<00:12:42.899> with<00:12:43.380> a<00:12:43.620> bit<00:12:43.680> of<00:12:43.800> history<00:12:43.920> in 00:12:44.210 --> 00:12:44.220 align:start position:0% so most people with a bit of history in 00:12:44.220 --> 00:12:45.590 align:start position:0% so most people with a bit of history in their<00:12:44.399> Twitter<00:12:44.579> account<00:12:44.940> and<00:12:45.300> a<00:12:45.480> few 00:12:45.590 --> 00:12:45.600 align:start position:0% their Twitter account and a few 00:12:45.600 --> 00:12:46.810 align:start position:0% their Twitter account and a few followers 00:12:46.810 --> 00:12:46.820 align:start position:0% followers 00:12:46.820 --> 00:12:50.090 align:start position:0% followers will<00:12:47.820> be<00:12:48.240> able<00:12:48.420> to<00:12:48.660> get<00:12:48.899> in<00:12:49.260> silver<00:12:49.500> or<00:12:49.860> gold 00:12:50.090 --> 00:12:50.100 align:start position:0% will be able to get in silver or gold 00:12:50.100 --> 00:12:53.110 align:start position:0% will be able to get in silver or gold just<00:12:50.880> using<00:12:51.180> that<00:12:51.360> bottoma<00:12:52.079> to<00:12:52.380> school 00:12:53.110 --> 00:12:53.120 align:start position:0% just using that bottoma to school 00:12:53.120 --> 00:12:55.310 align:start position:0% just using that bottoma to school you<00:12:54.120> can 00:12:55.310 --> 00:12:55.320 align:start position:0% you can 00:12:55.320 --> 00:12:56.870 align:start position:0% you can you<00:12:55.860> can<00:12:55.980> try 00:12:56.870 --> 00:12:56.880 align:start position:0% you can try 00:12:56.880 --> 00:12:58.670 align:start position:0% you can try um you<00:12:57.180> can<00:12:57.240> join<00:12:57.480> a<00:12:57.600> group<00:12:57.779> in 00:12:58.670 --> 00:12:58.680 align:start position:0% um you can join a group in 00:12:58.680 --> 00:13:02.389 align:start position:0% um you can join a group in and<00:12:59.160> on<00:12:59.700> our<00:12:59.880> website<00:13:00.240> and<00:13:01.079> um<00:13:01.620> assess<00:13:02.100> your 00:13:02.389 --> 00:13:02.399 align:start position:0% and on our website and um assess your 00:13:02.399 --> 00:13:04.550 align:start position:0% and on our website and um assess your own 00:13:04.550 --> 00:13:04.560 align:start position:0% own 00:13:04.560 --> 00:13:06.290 align:start position:0% own status<00:13:04.920> there<00:13:05.279> and<00:13:05.579> see<00:13:05.700> if<00:13:05.820> you<00:13:05.820> can<00:13:05.940> get<00:13:06.120> into 00:13:06.290 --> 00:13:06.300 align:start position:0% status there and see if you can get into 00:13:06.300 --> 00:13:09.110 align:start position:0% status there and see if you can get into one<00:13:06.600> of<00:13:06.720> those<00:13:06.779> groups<00:13:07.200> I'll 00:13:09.110 --> 00:13:09.120 align:start position:0% one of those groups I'll 00:13:09.120 --> 00:13:11.329 align:start position:0% one of those groups I'll the<00:13:09.420> link<00:13:09.660> will<00:13:09.899> be<00:13:10.079> in<00:13:10.320> the 00:13:11.329 --> 00:13:11.339 align:start position:0% the link will be in the 00:13:11.339 --> 00:13:14.690 align:start position:0% the link will be in the in<00:13:11.760> a<00:13:11.940> later<00:13:12.120> slide 00:13:14.690 --> 00:13:14.700 align:start position:0% 00:13:14.700 --> 00:13:15.350 align:start position:0% um 00:13:15.350 --> 00:13:15.360 align:start position:0% um 00:13:15.360 --> 00:13:19.370 align:start position:0% um but<00:13:15.959> yeah<00:13:16.139> so<00:13:16.620> uh<00:13:16.980> the<00:13:17.160> way<00:13:17.279> we<00:13:17.399> do<00:13:17.519> it<00:13:17.700> is<00:13:18.420> um<00:13:18.480> is 00:13:19.370 --> 00:13:19.380 align:start position:0% but yeah so uh the way we do it is um is 00:13:19.380 --> 00:13:22.629 align:start position:0% but yeah so uh the way we do it is um is we'll<00:13:19.620> we'll<00:13:20.040> do<00:13:20.760> that<00:13:20.940> evaluation 00:13:22.629 --> 00:13:22.639 align:start position:0% we'll we'll do that evaluation 00:13:22.639 --> 00:13:27.050 align:start position:0% we'll we'll do that evaluation uh<00:13:23.639> give<00:13:24.000> someone<00:13:24.180> a<00:13:24.480> score<00:13:24.660> and<00:13:25.440> then 00:13:27.050 --> 00:13:27.060 align:start position:0% uh give someone a score and then 00:13:27.060 --> 00:13:30.170 align:start position:0% uh give someone a score and then assign<00:13:27.899> them<00:13:28.220> to<00:13:29.220> that 00:13:30.170 --> 00:13:30.180 align:start position:0% assign them to that 00:13:30.180 --> 00:13:33.410 align:start position:0% assign them to that to<00:13:30.660> that<00:13:30.899> that<00:13:31.320> level<00:13:31.680> that<00:13:32.100> tier<00:13:32.459> bronze 00:13:33.410 --> 00:13:33.420 align:start position:0% to that that level that tier bronze 00:13:33.420 --> 00:13:35.449 align:start position:0% to that that level that tier bronze silver<00:13:33.600> or<00:13:33.899> gold 00:13:35.449 --> 00:13:35.459 align:start position:0% silver or gold 00:13:35.459 --> 00:13:37.310 align:start position:0% silver or gold um 00:13:37.310 --> 00:13:37.320 align:start position:0% um 00:13:37.320 --> 00:13:39.550 align:start position:0% um and 00:13:39.550 --> 00:13:39.560 align:start position:0% and 00:13:39.560 --> 00:13:41.150 align:start position:0% and uh 00:13:41.150 --> 00:13:41.160 align:start position:0% uh 00:13:41.160 --> 00:13:43.670 align:start position:0% uh that<00:13:41.880> yeah<00:13:42.360> so<00:13:42.720> uh 00:13:43.670 --> 00:13:43.680 align:start position:0% that yeah so uh 00:13:43.680 --> 00:13:46.370 align:start position:0% that yeah so uh applications<00:13:44.459> will<00:13:45.120> be<00:13:45.420> able<00:13:45.540> to 00:13:46.370 --> 00:13:46.380 align:start position:0% applications will be able to 00:13:46.380 --> 00:13:49.910 align:start position:0% applications will be able to choose<00:13:47.040> what<00:13:48.000> level<00:13:48.180> of<00:13:48.480> confidence 00:13:49.910 --> 00:13:49.920 align:start position:0% choose what level of confidence 00:13:49.920 --> 00:13:52.910 align:start position:0% choose what level of confidence uh<00:13:50.880> they<00:13:51.600> they<00:13:51.779> require 00:13:52.910 --> 00:13:52.920 align:start position:0% uh they they require 00:13:52.920 --> 00:13:54.910 align:start position:0% uh they they require some<00:13:53.519> applications 00:13:54.910 --> 00:13:54.920 align:start position:0% some applications 00:13:54.920 --> 00:13:58.250 align:start position:0% some applications will<00:13:55.920> insist<00:13:56.339> on<00:13:56.579> a<00:13:56.820> strong<00:13:57.360> guarantee<00:13:57.959> of 00:13:58.250 --> 00:13:58.260 align:start position:0% will insist on a strong guarantee of 00:13:58.260 --> 00:13:59.829 align:start position:0% will insist on a strong guarantee of humanity 00:13:59.829 --> 00:13:59.839 align:start position:0% humanity 00:13:59.839 --> 00:14:02.750 align:start position:0% humanity but<00:14:00.839> they're<00:14:00.959> going<00:14:01.139> to<00:14:01.260> be<00:14:01.800> working<00:14:02.279> with<00:14:02.579> a 00:14:02.750 --> 00:14:02.760 align:start position:0% but they're going to be working with a 00:14:02.760 --> 00:14:05.329 align:start position:0% but they're going to be working with a smaller<00:14:03.120> pool<00:14:03.300> of<00:14:04.260> of<00:14:04.560> people<00:14:04.920> who<00:14:05.220> can 00:14:05.329 --> 00:14:05.339 align:start position:0% smaller pool of of people who can 00:14:05.339 --> 00:14:06.829 align:start position:0% smaller pool of of people who can qualify<00:14:05.700> for<00:14:05.940> that 00:14:06.829 --> 00:14:06.839 align:start position:0% qualify for that 00:14:06.839 --> 00:14:09.710 align:start position:0% qualify for that so<00:14:07.680> some<00:14:08.100> people<00:14:08.279> some<00:14:08.820> applications<00:14:09.300> will 00:14:09.710 --> 00:14:09.720 align:start position:0% so some people some applications will 00:14:09.720 --> 00:14:12.170 align:start position:0% so some people some applications will want<00:14:10.019> a<00:14:10.800> large<00:14:10.980> group<00:14:11.160> of<00:14:11.339> people<00:14:11.579> to<00:14:11.760> draw<00:14:11.940> on 00:14:12.170 --> 00:14:12.180 align:start position:0% want a large group of people to draw on 00:14:12.180 --> 00:14:14.710 align:start position:0% want a large group of people to draw on and<00:14:12.959> they're<00:14:13.079> not<00:14:13.320> so 00:14:14.710 --> 00:14:14.720 align:start position:0% and they're not so 00:14:14.720 --> 00:14:18.829 align:start position:0% and they're not so not<00:14:15.720> so<00:14:16.019> concerned<00:14:16.620> that<00:14:17.519> we 00:14:18.829 --> 00:14:18.839 align:start position:0% not so concerned that we 00:14:18.839 --> 00:14:19.790 align:start position:0% not so concerned that we um 00:14:19.790 --> 00:14:19.800 align:start position:0% um 00:14:19.800 --> 00:14:22.370 align:start position:0% um strongly<00:14:20.519> guarantee<00:14:20.940> Humanity<00:14:21.540> as<00:14:22.019> long<00:14:22.260> as 00:14:22.370 --> 00:14:22.380 align:start position:0% strongly guarantee Humanity as long as 00:14:22.380 --> 00:14:24.650 align:start position:0% strongly guarantee Humanity as long as we<00:14:22.560> do<00:14:22.680> some<00:14:22.860> filtering<00:14:23.399> to<00:14:24.240> kick<00:14:24.360> out<00:14:24.540> the 00:14:24.650 --> 00:14:24.660 align:start position:0% we do some filtering to kick out the 00:14:24.660 --> 00:14:26.870 align:start position:0% we do some filtering to kick out the Bots 00:14:26.870 --> 00:14:26.880 align:start position:0% 00:14:26.880 --> 00:14:30.290 align:start position:0% um so<00:14:27.120> that<00:14:27.300> would<00:14:27.420> be<00:14:27.540> a<00:14:27.660> bronze<00:14:28.019> level 00:14:30.290 --> 00:14:30.300 align:start position:0% 00:14:30.300 --> 00:14:33.590 align:start position:0% um<00:14:30.560> with<00:14:31.560> interact<00:14:32.100> groups<00:14:32.519> because<00:14:32.820> interrep 00:14:33.590 --> 00:14:33.600 align:start position:0% um with interact groups because interrep 00:14:33.600 --> 00:14:36.170 align:start position:0% um with interact groups because interrep is<00:14:33.720> managing<00:14:34.320> those<00:14:34.560> groups<00:14:34.920> if<00:14:35.700> you<00:14:35.820> join<00:14:36.060> a 00:14:36.170 --> 00:14:36.180 align:start position:0% is managing those groups if you join a 00:14:36.180 --> 00:14:39.050 align:start position:0% is managing those groups if you join a group<00:14:36.560> that<00:14:37.560> group<00:14:37.800> can<00:14:38.100> be<00:14:38.279> used<00:14:38.459> across 00:14:39.050 --> 00:14:39.060 align:start position:0% group that group can be used across 00:14:39.060 --> 00:14:42.110 align:start position:0% group that group can be used across multiple<00:14:39.839> applications 00:14:42.110 --> 00:14:42.120 align:start position:0% multiple applications 00:14:42.120 --> 00:14:43.250 align:start position:0% multiple applications um 00:14:43.250 --> 00:14:43.260 align:start position:0% um 00:14:43.260 --> 00:14:45.889 align:start position:0% um so<00:14:43.680> you<00:14:43.800> can<00:14:43.920> join<00:14:44.220> once<00:14:44.579> and<00:14:45.060> use<00:14:45.240> it<00:14:45.420> in<00:14:45.779> many 00:14:45.889 --> 00:14:45.899 align:start position:0% so you can join once and use it in many 00:14:45.899 --> 00:14:48.530 align:start position:0% so you can join once and use it in many applications<00:14:46.699> and<00:14:47.699> effectively<00:14:48.180> we've<00:14:48.420> got 00:14:48.530 --> 00:14:48.540 align:start position:0% applications and effectively we've got 00:14:48.540 --> 00:14:52.730 align:start position:0% applications and effectively we've got to<00:14:48.660> sign<00:14:48.839> in<00:14:49.100> that<00:14:50.100> will<00:14:50.339> be<00:14:51.180> workable<00:14:52.139> across 00:14:52.730 --> 00:14:52.740 align:start position:0% to sign in that will be workable across 00:14:52.740 --> 00:14:55.790 align:start position:0% to sign in that will be workable across multiple<00:14:53.519> applications<00:14:54.260> and<00:14:55.260> the<00:14:55.440> advantage 00:14:55.790 --> 00:14:55.800 align:start position:0% multiple applications and the advantage 00:14:55.800 --> 00:14:59.090 align:start position:0% multiple applications and the advantage of<00:14:56.040> doing<00:14:56.220> that<00:14:56.579> in<00:14:57.480> a<00:14:57.660> privacy<00:14:57.959> setting 00:14:59.090 --> 00:14:59.100 align:start position:0% of doing that in a privacy setting 00:14:59.100 --> 00:15:07.030 align:start position:0% of doing that in a privacy setting is<00:14:59.639> that<00:14:59.820> we<00:14:59.940> have<00:15:00.180> a<00:15:00.420> large<00:15:00.660> privacy<00:15:01.380> pool 00:15:07.030 --> 00:15:07.040 align:start position:0% 00:15:07.040 --> 00:15:09.530 align:start position:0% so<00:15:08.040> the 00:15:09.530 --> 00:15:09.540 align:start position:0% so the 00:15:09.540 --> 00:15:12.470 align:start position:0% so the nitty-gritty<00:15:10.500> process<00:15:10.860> of<00:15:11.220> of<00:15:11.760> joining<00:15:12.300> a 00:15:12.470 --> 00:15:12.480 align:start position:0% nitty-gritty process of of joining a 00:15:12.480 --> 00:15:15.710 align:start position:0% nitty-gritty process of of joining a group<00:15:12.740> the<00:15:13.740> user<00:15:14.100> will<00:15:14.519> come<00:15:15.000> to<00:15:15.120> a<00:15:15.300> sign<00:15:15.420> on 00:15:15.710 --> 00:15:15.720 align:start position:0% group the user will come to a sign on 00:15:15.720 --> 00:15:19.069 align:start position:0% group the user will come to a sign on screen<00:15:16.220> sometimes<00:15:17.220> it'll<00:15:17.880> be 00:15:19.069 --> 00:15:19.079 align:start position:0% screen sometimes it'll be 00:15:19.079 --> 00:15:22.189 align:start position:0% screen sometimes it'll be a step<00:15:19.620> just<00:15:20.040> before<00:15:20.220> they<00:15:20.639> go<00:15:21.420> in<00:15:21.600> to<00:15:21.779> use<00:15:21.959> the 00:15:22.189 --> 00:15:22.199 align:start position:0% a step just before they go in to use the 00:15:22.199 --> 00:15:25.790 align:start position:0% a step just before they go in to use the application<00:15:23.000> sometimes<00:15:24.000> it<00:15:24.360> will<00:15:24.600> it<00:15:25.560> can<00:15:25.680> be 00:15:25.790 --> 00:15:25.800 align:start position:0% application sometimes it will it can be 00:15:25.800 --> 00:15:28.250 align:start position:0% application sometimes it will it can be done<00:15:25.980> well<00:15:26.220> beforehand<00:15:26.820> someone<00:15:27.540> can<00:15:27.839> join<00:15:28.139> a 00:15:28.250 --> 00:15:28.260 align:start position:0% done well beforehand someone can join a 00:15:28.260 --> 00:15:30.590 align:start position:0% done well beforehand someone can join a group<00:15:28.380> and<00:15:29.220> then<00:15:29.339> they'll<00:15:29.579> keep<00:15:29.820> their 00:15:30.590 --> 00:15:30.600 align:start position:0% group and then they'll keep their 00:15:30.600 --> 00:15:32.350 align:start position:0% group and then they'll keep their identity 00:15:32.350 --> 00:15:32.360 align:start position:0% identity 00:15:32.360 --> 00:15:35.870 align:start position:0% identity and<00:15:33.360> use<00:15:33.480> that<00:15:33.779> to<00:15:33.959> kind<00:15:34.199> of<00:15:34.320> log<00:15:34.560> in<00:15:34.740> to<00:15:35.699> work 00:15:35.870 --> 00:15:35.880 align:start position:0% and use that to kind of log in to work 00:15:35.880 --> 00:15:37.750 align:start position:0% and use that to kind of log in to work with<00:15:36.060> the<00:15:36.240> application 00:15:37.750 --> 00:15:37.760 align:start position:0% with the application 00:15:37.760 --> 00:15:40.790 align:start position:0% with the application so<00:15:38.760> whichever<00:15:39.240> way<00:15:39.420> that's<00:15:39.660> done<00:15:39.899> first<00:15:40.560> step 00:15:40.790 --> 00:15:40.800 align:start position:0% so whichever way that's done first step 00:15:40.800 --> 00:15:43.910 align:start position:0% so whichever way that's done first step is<00:15:41.160> to<00:15:41.699> prove<00:15:42.420> the<00:15:42.540> identity<00:15:42.959> with<00:15:43.500> the 00:15:43.910 --> 00:15:43.920 align:start position:0% is to prove the identity with the 00:15:43.920 --> 00:15:45.410 align:start position:0% is to prove the identity with the provider 00:15:45.410 --> 00:15:45.420 align:start position:0% provider 00:15:45.420 --> 00:15:48.170 align:start position:0% provider that<00:15:46.320> might<00:15:46.620> be<00:15:46.800> like<00:15:46.980> Twitter<00:15:47.279> oauth<00:15:48.060> or 00:15:48.170 --> 00:15:48.180 align:start position:0% that might be like Twitter oauth or 00:15:48.180 --> 00:15:50.230 align:start position:0% that might be like Twitter oauth or GitHub<00:15:48.540> oauth 00:15:50.230 --> 00:15:50.240 align:start position:0% GitHub oauth 00:15:50.240 --> 00:15:52.790 align:start position:0% GitHub oauth having<00:15:51.240> done<00:15:51.600> that 00:15:52.790 --> 00:15:52.800 align:start position:0% having done that 00:15:52.800 --> 00:15:54.710 align:start position:0% having done that the 00:15:54.710 --> 00:15:54.720 align:start position:0% the 00:15:54.720 --> 00:15:58.449 align:start position:0% the our<00:15:55.380> application<00:15:56.100> will<00:15:56.699> do<00:15:57.420> that<00:15:57.600> assessment 00:15:58.449 --> 00:15:58.459 align:start position:0% our application will do that assessment 00:15:58.459 --> 00:16:02.150 align:start position:0% our application will do that assessment assign<00:15:59.459> the<00:16:00.240> user<00:16:00.600> to<00:16:00.839> a<00:16:01.199> tier<00:16:01.500> called<00:16:01.860> Silver 00:16:02.150 --> 00:16:02.160 align:start position:0% assign the user to a tier called Silver 00:16:02.160 --> 00:16:03.470 align:start position:0% assign the user to a tier called Silver bronze 00:16:03.470 --> 00:16:03.480 align:start position:0% bronze 00:16:03.480 --> 00:16:06.650 align:start position:0% bronze and<00:16:04.260> then<00:16:04.500> invite<00:16:04.860> them<00:16:05.100> to<00:16:05.339> join<00:16:05.579> that<00:16:05.760> group 00:16:06.650 --> 00:16:06.660 align:start position:0% and then invite them to join that group 00:16:06.660 --> 00:16:10.310 align:start position:0% and then invite them to join that group so<00:16:07.440> the<00:16:07.860> user<00:16:08.160> will<00:16:08.760> uh 00:16:10.310 --> 00:16:10.320 align:start position:0% so the user will uh 00:16:10.320 --> 00:16:13.370 align:start position:0% so the user will uh do<00:16:10.800> their<00:16:10.980> Twitter<00:16:11.220> sign<00:16:11.579> on<00:16:11.880> say<00:16:12.600> okay<00:16:13.019> you're 00:16:13.370 --> 00:16:13.380 align:start position:0% do their Twitter sign on say okay you're 00:16:13.380 --> 00:16:15.230 align:start position:0% do their Twitter sign on say okay you're in<00:16:13.560> Twitter<00:16:13.680> gold<00:16:14.040> would<00:16:14.639> you<00:16:14.760> like<00:16:14.880> to<00:16:15.000> join 00:16:15.230 --> 00:16:15.240 align:start position:0% in Twitter gold would you like to join 00:16:15.240 --> 00:16:16.790 align:start position:0% in Twitter gold would you like to join this<00:16:15.360> group<00:16:15.540> they<00:16:15.779> click<00:16:16.019> click<00:16:16.320> that<00:16:16.440> button 00:16:16.790 --> 00:16:16.800 align:start position:0% this group they click click that button 00:16:16.800 --> 00:16:19.370 align:start position:0% this group they click click that button and<00:16:17.699> then<00:16:17.880> the<00:16:18.060> next<00:16:18.240> step 00:16:19.370 --> 00:16:19.380 align:start position:0% and then the next step 00:16:19.380 --> 00:16:21.710 align:start position:0% and then the next step is<00:16:19.860> they<00:16:20.040> link<00:16:20.279> that<00:16:20.519> with<00:16:21.000> an<00:16:21.240> ethereum 00:16:21.710 --> 00:16:21.720 align:start position:0% is they link that with an ethereum 00:16:21.720 --> 00:16:23.710 align:start position:0% is they link that with an ethereum account 00:16:23.710 --> 00:16:23.720 align:start position:0% account 00:16:23.720 --> 00:16:26.710 align:start position:0% account so<00:16:24.720> the<00:16:24.899> user<00:16:25.260> will<00:16:25.380> sign<00:16:25.620> a<00:16:25.860> message 00:16:26.710 --> 00:16:26.720 align:start position:0% so the user will sign a message 00:16:26.720 --> 00:16:29.090 align:start position:0% so the user will sign a message with<00:16:27.720> their<00:16:27.899> ethereum<00:16:28.320> account<00:16:28.500> which 00:16:29.090 --> 00:16:29.100 align:start position:0% with their ethereum account which 00:16:29.100 --> 00:16:30.949 align:start position:0% with their ethereum account which guarantees<00:16:29.639> that<00:16:29.940> they<00:16:30.120> own<00:16:30.300> that<00:16:30.480> ethereum 00:16:30.949 --> 00:16:30.959 align:start position:0% guarantees that they own that ethereum 00:16:30.959 --> 00:16:33.710 align:start position:0% guarantees that they own that ethereum account<00:16:31.279> it<00:16:32.279> also<00:16:32.579> prevents<00:16:33.000> that<00:16:33.300> account 00:16:33.710 --> 00:16:33.720 align:start position:0% account it also prevents that account 00:16:33.720 --> 00:16:35.509 align:start position:0% account it also prevents that account from<00:16:34.079> being<00:16:34.320> used<00:16:34.560> again 00:16:35.509 --> 00:16:35.519 align:start position:0% from being used again 00:16:35.519 --> 00:16:38.030 align:start position:0% from being used again so<00:16:35.940> they<00:16:36.180> can<00:16:36.300> only<00:16:36.420> join<00:16:36.720> once<00:16:37.079> and<00:16:37.860> the 00:16:38.030 --> 00:16:38.040 align:start position:0% so they can only join once and the 00:16:38.040 --> 00:16:39.889 align:start position:0% so they can only join once and the Twitter<00:16:38.279> account<00:16:38.579> likewise<00:16:39.120> can<00:16:39.420> only<00:16:39.600> join 00:16:39.889 --> 00:16:39.899 align:start position:0% Twitter account likewise can only join 00:16:39.899 --> 00:16:43.430 align:start position:0% Twitter account likewise can only join once<00:16:40.399> so<00:16:41.399> having<00:16:41.880> made<00:16:42.240> that<00:16:42.480> link 00:16:43.430 --> 00:16:43.440 align:start position:0% once so having made that link 00:16:43.440 --> 00:16:45.050 align:start position:0% once so having made that link we 00:16:45.050 --> 00:16:45.060 align:start position:0% we 00:16:45.060 --> 00:16:46.790 align:start position:0% we we<00:16:45.120> have 00:16:46.790 --> 00:16:46.800 align:start position:0% we have 00:16:46.800 --> 00:16:50.930 align:start position:0% we have we<00:16:47.639> return<00:16:48.420> a<00:16:48.839> semaphore<00:16:49.320> ID<00:16:49.620> the<00:16:50.459> semaphore 00:16:50.930 --> 00:16:50.940 align:start position:0% we return a semaphore ID the semaphore 00:16:50.940 --> 00:16:52.509 align:start position:0% we return a semaphore ID the semaphore ID 00:16:52.509 --> 00:16:52.519 align:start position:0% ID 00:16:52.519 --> 00:16:54.710 align:start position:0% ID provides<00:16:53.519> that<00:16:53.639> guarantee<00:16:54.120> that<00:16:54.420> that 00:16:54.710 --> 00:16:54.720 align:start position:0% provides that guarantee that that 00:16:54.720 --> 00:16:58.189 align:start position:0% provides that guarantee that that Twitter<00:16:55.019> handle<00:16:55.940> is<00:16:56.940> represented<00:16:57.899> in<00:16:58.079> that 00:16:58.189 --> 00:16:58.199 align:start position:0% Twitter handle is represented in that 00:16:58.199 --> 00:17:00.350 align:start position:0% Twitter handle is represented in that semaphore<00:16:58.680> ID<00:16:58.920> and<00:16:59.519> that<00:16:59.699> can<00:16:59.820> be<00:16:59.940> used<00:17:00.120> from 00:17:00.350 --> 00:17:00.360 align:start position:0% semaphore ID and that can be used from 00:17:00.360 --> 00:17:03.230 align:start position:0% semaphore ID and that can be used from there<00:17:00.540> on<00:17:00.779> in<00:17:01.500> the<00:17:01.680> application<00:17:02.240> without 00:17:03.230 --> 00:17:03.240 align:start position:0% there on in the application without 00:17:03.240 --> 00:17:06.010 align:start position:0% there on in the application without revealing<00:17:04.079> that<00:17:04.559> link<00:17:04.799> of<00:17:05.220> who<00:17:05.459> the<00:17:05.699> actual 00:17:06.010 --> 00:17:06.020 align:start position:0% revealing that link of who the actual 00:17:06.020 --> 00:17:10.250 align:start position:0% revealing that link of who the actual Twitter<00:17:07.020> user<00:17:07.559> is<00:17:07.740> behind<00:17:08.220> that<00:17:08.400> account 00:17:10.250 --> 00:17:10.260 align:start position:0% Twitter user is behind that account 00:17:10.260 --> 00:17:12.490 align:start position:0% Twitter user is behind that account and<00:17:10.799> neither<00:17:11.100> is<00:17:11.339> the<00:17:11.459> ethereum<00:17:11.880> account 00:17:12.490 --> 00:17:12.500 align:start position:0% and neither is the ethereum account 00:17:12.500 --> 00:17:15.049 align:start position:0% and neither is the ethereum account revealed<00:17:13.500> in<00:17:14.220> the<00:17:14.339> actual<00:17:14.579> application 00:17:15.049 --> 00:17:15.059 align:start position:0% revealed in the actual application 00:17:15.059 --> 00:17:17.870 align:start position:0% revealed in the actual application because<00:17:15.419> we're<00:17:15.660> using<00:17:16.020> semaphore<00:17:16.919> IDs<00:17:17.400> and<00:17:17.640> it 00:17:17.870 --> 00:17:17.880 align:start position:0% because we're using semaphore IDs and it 00:17:17.880 --> 00:17:21.470 align:start position:0% because we're using semaphore IDs and it conceals<00:17:18.839> that<00:17:19.160> we<00:17:20.160> can<00:17:20.339> also<00:17:20.819> work<00:17:21.179> with 00:17:21.470 --> 00:17:21.480 align:start position:0% conceals that we can also work with 00:17:21.480 --> 00:17:24.530 align:start position:0% conceals that we can also work with on-chain<00:17:22.140> sources<00:17:22.740> of 00:17:24.530 --> 00:17:24.540 align:start position:0% on-chain sources of 00:17:24.540 --> 00:17:27.829 align:start position:0% on-chain sources of uh<00:17:25.380> proof<00:17:25.740> of<00:17:25.860> humanity<00:17:26.339> if<00:17:26.640> you<00:17:26.760> like<00:17:26.880> some<00:17:27.660> of 00:17:27.829 --> 00:17:27.839 align:start position:0% uh proof of humanity if you like some of 00:17:27.839 --> 00:17:31.630 align:start position:0% uh proof of humanity if you like some of those<00:17:28.020> are<00:17:28.679> pretty<00:17:29.400> pretty<00:17:30.120> strong 00:17:31.630 --> 00:17:31.640 align:start position:0% those are pretty pretty strong 00:17:31.640 --> 00:17:35.390 align:start position:0% those are pretty pretty strong guarantees<00:17:32.640> of<00:17:32.820> humanity<00:17:33.620> and<00:17:34.620> I'm<00:17:34.919> thinking 00:17:35.390 --> 00:17:35.400 align:start position:0% guarantees of humanity and I'm thinking 00:17:35.400 --> 00:17:39.110 align:start position:0% guarantees of humanity and I'm thinking there<00:17:35.700> of<00:17:36.059> like<00:17:36.360> Sol<00:17:36.600> burn<00:17:36.900> tokens<00:17:37.500> or<00:17:38.460> poapps 00:17:39.110 --> 00:17:39.120 align:start position:0% there of like Sol burn tokens or poapps 00:17:39.120 --> 00:17:41.510 align:start position:0% there of like Sol burn tokens or poapps like<00:17:39.299> the<00:17:39.480> pop-up<00:17:39.780> you<00:17:40.020> get<00:17:40.200> from<00:17:40.740> your<00:17:40.860> Devcon 00:17:41.510 --> 00:17:41.520 align:start position:0% like the pop-up you get from your Devcon 00:17:41.520 --> 00:17:45.830 align:start position:0% like the pop-up you get from your Devcon 6<00:17:41.900> with<00:17:42.900> your<00:17:43.080> Devcon<00:17:43.980> 6<00:17:44.340> ticket 00:17:45.830 --> 00:17:45.840 align:start position:0% 6 with your Devcon 6 ticket 00:17:45.840 --> 00:17:47.990 align:start position:0% 6 with your Devcon 6 ticket that<00:17:46.440> can<00:17:46.620> only<00:17:46.740> be<00:17:46.980> owned<00:17:47.280> by<00:17:47.400> a<00:17:47.520> human<00:17:47.640> right 00:17:47.990 --> 00:17:48.000 align:start position:0% that can only be owned by a human right 00:17:48.000 --> 00:17:49.430 align:start position:0% that can only be owned by a human right because<00:17:48.179> they're<00:17:48.360> only<00:17:48.539> giving<00:17:48.780> out<00:17:49.020> tickets 00:17:49.430 --> 00:17:49.440 align:start position:0% because they're only giving out tickets 00:17:49.440 --> 00:17:52.970 align:start position:0% because they're only giving out tickets for<00:17:49.740> humans<00:17:50.460> so<00:17:51.299> that's<00:17:51.480> a<00:17:52.080> that's<00:17:52.500> a<00:17:52.799> pretty 00:17:52.970 --> 00:17:52.980 align:start position:0% for humans so that's a that's a pretty 00:17:52.980 --> 00:17:56.450 align:start position:0% for humans so that's a that's a pretty good<00:17:53.360> indication<00:17:54.360> that<00:17:54.780> that<00:17:55.140> account<00:17:55.500> has<00:17:56.280> a 00:17:56.450 --> 00:17:56.460 align:start position:0% good indication that that account has a 00:17:56.460 --> 00:17:59.150 align:start position:0% good indication that that account has a human<00:17:56.580> behind<00:17:57.059> it<00:17:57.240> uh<00:17:58.200> it's<00:17:58.440> certainly<00:17:58.860> very 00:17:59.150 --> 00:17:59.160 align:start position:0% human behind it uh it's certainly very 00:17:59.160 --> 00:18:01.310 align:start position:0% human behind it uh it's certainly very hard<00:17:59.400> to<00:18:00.179> um 00:18:01.310 --> 00:18:01.320 align:start position:0% hard to um 00:18:01.320 --> 00:18:03.950 align:start position:0% hard to um very<00:18:01.799> resistant<00:18:02.280> to<00:18:02.520> civil<00:18:02.880> attacks 00:18:03.950 --> 00:18:03.960 align:start position:0% very resistant to civil attacks 00:18:03.960 --> 00:18:07.070 align:start position:0% very resistant to civil attacks so<00:18:04.860> yeah<00:18:05.220> so<00:18:05.580> we<00:18:05.760> we<00:18:06.120> take<00:18:06.660> a<00:18:06.840> slightly 00:18:07.070 --> 00:18:07.080 align:start position:0% so yeah so we we take a slightly 00:18:07.080 --> 00:18:10.090 align:start position:0% so yeah so we we take a slightly different<00:18:07.380> approach<00:18:07.980> with<00:18:08.280> on-chain<00:18:09.000> groups 00:18:10.090 --> 00:18:10.100 align:start position:0% different approach with on-chain groups 00:18:10.100 --> 00:18:13.130 align:start position:0% different approach with on-chain groups behind<00:18:11.100> the<00:18:11.280> scenes<00:18:11.580> but 00:18:13.130 --> 00:18:13.140 align:start position:0% behind the scenes but 00:18:13.140 --> 00:18:14.270 align:start position:0% behind the scenes but um 00:18:14.270 --> 00:18:14.280 align:start position:0% um 00:18:14.280 --> 00:18:17.029 align:start position:0% um but<00:18:14.940> they<00:18:15.240> end<00:18:15.480> up<00:18:15.600> as<00:18:15.720> a<00:18:15.840> semaphore<00:18:16.320> ID<00:18:16.500> and 00:18:17.029 --> 00:18:17.039 align:start position:0% but they end up as a semaphore ID and 00:18:17.039 --> 00:18:22.370 align:start position:0% but they end up as a semaphore ID and work<00:18:17.220> the<00:18:17.460> same<00:18:17.640> way<00:18:17.820> in<00:18:18.539> your<00:18:18.660> application 00:18:22.370 --> 00:18:22.380 align:start position:0% 00:18:22.380 --> 00:18:25.930 align:start position:0% so<00:18:23.100> the<00:18:23.820> kind<00:18:24.000> of<00:18:24.120> applications<00:18:24.480> we<00:18:24.840> work<00:18:24.960> with 00:18:25.930 --> 00:18:25.940 align:start position:0% so the kind of applications we work with 00:18:25.940 --> 00:18:29.930 align:start position:0% so the kind of applications we work with that<00:18:26.940> we<00:18:27.179> have<00:18:27.299> in<00:18:27.419> mind<00:18:27.600> for<00:18:28.320> interrep<00:18:28.980> uh 00:18:29.930 --> 00:18:29.940 align:start position:0% that we have in mind for interrep uh 00:18:29.940 --> 00:18:31.810 align:start position:0% that we have in mind for interrep uh private<00:18:30.780> voting 00:18:31.810 --> 00:18:31.820 align:start position:0% private voting 00:18:31.820 --> 00:18:35.570 align:start position:0% private voting I<00:18:32.820> talked<00:18:33.000> a<00:18:33.059> bit<00:18:33.240> about<00:18:33.600> this<00:18:33.960> before 00:18:35.570 --> 00:18:35.580 align:start position:0% I talked a bit about this before 00:18:35.580 --> 00:18:38.090 align:start position:0% I talked a bit about this before um 00:18:38.090 --> 00:18:38.100 align:start position:0% 00:18:38.100 --> 00:18:41.710 align:start position:0% yeah<00:18:38.580> membership<00:18:39.000> of<00:18:39.360> uh<00:18:39.740> Dow<00:18:40.740> for<00:18:41.039> instance 00:18:41.710 --> 00:18:41.720 align:start position:0% yeah membership of uh Dow for instance 00:18:41.720 --> 00:18:45.470 align:start position:0% yeah membership of uh Dow for instance and<00:18:42.720> we<00:18:42.900> can<00:18:43.020> guarantee<00:18:43.559> membership 00:18:45.470 --> 00:18:45.480 align:start position:0% and we can guarantee membership 00:18:45.480 --> 00:18:47.510 align:start position:0% and we can guarantee membership guarantee<00:18:46.440> that<00:18:46.559> there's<00:18:46.799> a<00:18:46.919> human<00:18:47.039> behind 00:18:47.510 --> 00:18:47.520 align:start position:0% guarantee that there's a human behind 00:18:47.520 --> 00:18:48.770 align:start position:0% guarantee that there's a human behind that 00:18:48.770 --> 00:18:48.780 align:start position:0% that 00:18:48.780 --> 00:18:50.150 align:start position:0% that um 00:18:50.150 --> 00:18:50.160 align:start position:0% um 00:18:50.160 --> 00:18:52.370 align:start position:0% um uh 00:18:52.370 --> 00:18:52.380 align:start position:0% uh 00:18:52.380 --> 00:18:55.130 align:start position:0% uh a<00:18:53.100> human<00:18:53.460> in<00:18:53.940> that 00:18:55.130 --> 00:18:55.140 align:start position:0% a human in that 00:18:55.140 --> 00:18:57.529 align:start position:0% a human in that in<00:18:55.740> that<00:18:55.919> group<00:18:56.039> but<00:18:56.340> never<00:18:56.580> reveal<00:18:57.000> who<00:18:57.299> that 00:18:57.529 --> 00:18:57.539 align:start position:0% in that group but never reveal who that 00:18:57.539 --> 00:19:00.950 align:start position:0% in that group but never reveal who that human<00:18:57.720> is<00:18:58.520> social<00:18:59.520> networking<00:19:00.120> we<00:19:00.419> think<00:19:00.600> is<00:19:00.780> a 00:19:00.950 --> 00:19:00.960 align:start position:0% human is social networking we think is a 00:19:00.960 --> 00:19:02.029 align:start position:0% human is social networking we think is a promising 00:19:02.029 --> 00:19:02.039 align:start position:0% promising 00:19:02.039 --> 00:19:04.430 align:start position:0% promising way<00:19:02.640> to<00:19:02.940> apply<00:19:03.240> this 00:19:04.430 --> 00:19:04.440 align:start position:0% way to apply this 00:19:04.440 --> 00:19:07.690 align:start position:0% way to apply this and<00:19:05.340> some<00:19:05.460> of<00:19:05.640> our<00:19:05.820> sister<00:19:06.320> projects<00:19:07.320> in 00:19:07.690 --> 00:19:07.700 align:start position:0% and some of our sister projects in 00:19:07.700 --> 00:19:10.789 align:start position:0% and some of our sister projects in privacy<00:19:08.700> and<00:19:08.880> scaling<00:19:09.360> group<00:19:09.539> are<00:19:10.260> um 00:19:10.789 --> 00:19:10.799 align:start position:0% privacy and scaling group are um 00:19:10.799 --> 00:19:12.890 align:start position:0% privacy and scaling group are um we're<00:19:11.039> working<00:19:11.280> on<00:19:11.520> this<00:19:11.760> you'll<00:19:12.539> hear<00:19:12.720> some 00:19:12.890 --> 00:19:12.900 align:start position:0% we're working on this you'll hear some 00:19:12.900 --> 00:19:15.590 align:start position:0% we're working on this you'll hear some talks<00:19:13.260> in<00:19:13.500> Devcon<00:19:13.919> about<00:19:14.160> that 00:19:15.590 --> 00:19:15.600 align:start position:0% talks in Devcon about that 00:19:15.600 --> 00:19:18.230 align:start position:0% talks in Devcon about that um<00:19:15.720> but<00:19:16.140> yeah<00:19:16.380> that's<00:19:16.799> uh<00:19:17.400> another<00:19:17.940> place 00:19:18.230 --> 00:19:18.240 align:start position:0% um but yeah that's uh another place 00:19:18.240 --> 00:19:20.210 align:start position:0% um but yeah that's uh another place where<00:19:18.480> privacy<00:19:18.900> is<00:19:19.080> important<00:19:19.500> but<00:19:19.980> also 00:19:20.210 --> 00:19:20.220 align:start position:0% where privacy is important but also 00:19:20.220 --> 00:19:22.610 align:start position:0% where privacy is important but also Humanity<00:19:20.880> proof<00:19:21.600> of<00:19:21.720> humanity<00:19:22.200> is<00:19:22.440> very 00:19:22.610 --> 00:19:22.620 align:start position:0% Humanity proof of humanity is very 00:19:22.620 --> 00:19:24.230 align:start position:0% Humanity proof of humanity is very important 00:19:24.230 --> 00:19:24.240 align:start position:0% important 00:19:24.240 --> 00:19:28.010 align:start position:0% important um we<00:19:24.600> have<00:19:24.780> anti-spam<00:19:25.940> applications<00:19:27.020> like 00:19:28.010 --> 00:19:28.020 align:start position:0% um we have anti-spam applications like 00:19:28.020 --> 00:19:30.590 align:start position:0% um we have anti-spam applications like the<00:19:28.320> rate<00:19:28.440> limiting<00:19:28.980> nullifier<00:19:29.640> another<00:19:30.299> one 00:19:30.590 --> 00:19:30.600 align:start position:0% the rate limiting nullifier another one 00:19:30.600 --> 00:19:32.529 align:start position:0% the rate limiting nullifier another one of<00:19:30.720> our<00:19:30.780> sister<00:19:30.960> projects 00:19:32.529 --> 00:19:32.539 align:start position:0% of our sister projects 00:19:32.539 --> 00:19:35.390 align:start position:0% of our sister projects we<00:19:33.539> can<00:19:33.720> do<00:19:33.840> things<00:19:34.080> like 00:19:35.390 --> 00:19:35.400 align:start position:0% we can do things like 00:19:35.400 --> 00:19:38.510 align:start position:0% we can do things like Fair<00:19:36.059> air<00:19:36.419> drops<00:19:36.900> and<00:19:37.679> civil<00:19:38.100> resistant 00:19:38.510 --> 00:19:38.520 align:start position:0% Fair air drops and civil resistant 00:19:38.520 --> 00:19:41.690 align:start position:0% Fair air drops and civil resistant faucets<00:19:39.000> so<00:19:39.840> if<00:19:40.080> you<00:19:40.200> want<00:19:40.380> to 00:19:41.690 --> 00:19:41.700 align:start position:0% faucets so if you want to 00:19:41.700 --> 00:19:42.289 align:start position:0% faucets so if you want to um 00:19:42.289 --> 00:19:42.299 align:start position:0% um 00:19:42.299 --> 00:19:45.830 align:start position:0% um yeah<00:19:42.780> put<00:19:43.260> some<00:19:43.700> anti-civil<00:19:44.700> properties<00:19:45.419> into 00:19:45.830 --> 00:19:45.840 align:start position:0% yeah put some anti-civil properties into 00:19:45.840 --> 00:19:49.390 align:start position:0% yeah put some anti-civil properties into a<00:19:46.140> an<00:19:46.440> airdrop<00:19:46.860> or<00:19:47.039> a<00:19:47.160> faucet<00:19:48.080> interrupt<00:19:49.080> can 00:19:49.390 --> 00:19:49.400 align:start position:0% a an airdrop or a faucet interrupt can 00:19:49.400 --> 00:19:51.950 align:start position:0% a an airdrop or a faucet interrupt can do<00:19:50.400> that<00:19:50.580> kind<00:19:50.760> of<00:19:50.820> thing 00:19:51.950 --> 00:19:51.960 align:start position:0% do that kind of thing 00:19:51.960 --> 00:19:54.830 align:start position:0% do that kind of thing so<00:19:52.919> to<00:19:53.580> close 00:19:54.830 --> 00:19:54.840 align:start position:0% so to close 00:19:54.840 --> 00:19:57.110 align:start position:0% so to close we<00:19:55.620> think 00:19:57.110 --> 00:19:57.120 align:start position:0% we think 00:19:57.120 --> 00:19:59.590 align:start position:0% we think a<00:19:57.720> pragmatic<00:19:58.260> approach<00:19:58.620> to<00:19:59.039> Identity 00:19:59.590 --> 00:19:59.600 align:start position:0% a pragmatic approach to Identity 00:19:59.600 --> 00:20:03.590 align:start position:0% a pragmatic approach to Identity building<00:20:00.600> on<00:20:01.080> our<00:20:01.559> history<00:20:01.860> that<00:20:02.340> we<00:20:02.520> we<00:20:02.880> all 00:20:03.590 --> 00:20:03.600 align:start position:0% building on our history that we we all 00:20:03.600 --> 00:20:07.430 align:start position:0% building on our history that we we all work<00:20:04.260> on<00:20:04.500> you<00:20:04.919> know<00:20:05.100> in<00:20:05.520> our<00:20:05.760> existing<00:20:06.539> digital 00:20:07.430 --> 00:20:07.440 align:start position:0% work on you know in our existing digital 00:20:07.440 --> 00:20:08.710 align:start position:0% work on you know in our existing digital lives 00:20:08.710 --> 00:20:08.720 align:start position:0% lives 00:20:08.720 --> 00:20:12.710 align:start position:0% lives taking<00:20:09.720> a<00:20:09.960> pragmatic<00:20:10.559> approach<00:20:10.860> to<00:20:11.700> to<00:20:12.000> use 00:20:12.710 --> 00:20:12.720 align:start position:0% taking a pragmatic approach to to use 00:20:12.720 --> 00:20:16.430 align:start position:0% taking a pragmatic approach to to use that<00:20:13.020> bring<00:20:13.440> it<00:20:13.679> across<00:20:14.039> to<00:20:14.280> ethereum 00:20:16.430 --> 00:20:16.440 align:start position:0% that bring it across to ethereum 00:20:16.440 --> 00:20:17.690 align:start position:0% that bring it across to ethereum um 00:20:17.690 --> 00:20:17.700 align:start position:0% um 00:20:17.700 --> 00:20:20.510 align:start position:0% um we<00:20:18.299> can<00:20:18.419> build<00:20:18.840> up<00:20:19.020> we<00:20:19.500> have<00:20:19.679> a<00:20:19.980> existing 00:20:20.510 --> 00:20:20.520 align:start position:0% we can build up we have a existing 00:20:20.520 --> 00:20:22.850 align:start position:0% we can build up we have a existing source<00:20:20.940> of<00:20:21.059> identity<00:20:21.660> that<00:20:22.200> we<00:20:22.380> can<00:20:22.500> build<00:20:22.679> on 00:20:22.850 --> 00:20:22.860 align:start position:0% source of identity that we can build on 00:20:22.860 --> 00:20:24.409 align:start position:0% source of identity that we can build on we<00:20:23.100> don't<00:20:23.220> need<00:20:23.340> to<00:20:23.520> build<00:20:23.580> it<00:20:23.820> from<00:20:24.120> the 00:20:24.409 --> 00:20:24.419 align:start position:0% we don't need to build it from the 00:20:24.419 --> 00:20:25.970 align:start position:0% we don't need to build it from the ground<00:20:24.840> up 00:20:25.970 --> 00:20:25.980 align:start position:0% ground up 00:20:25.980 --> 00:20:28.130 align:start position:0% ground up uh<00:20:26.820> we<00:20:27.059> don't<00:20:27.179> need<00:20:27.360> to<00:20:27.539> discard<00:20:27.840> those 00:20:28.130 --> 00:20:28.140 align:start position:0% uh we don't need to discard those 00:20:28.140 --> 00:20:30.289 align:start position:0% uh we don't need to discard those relationships<00:20:28.860> we<00:20:29.100> have<00:20:29.340> in<00:20:30.000> our<00:20:30.120> social 00:20:30.289 --> 00:20:30.299 align:start position:0% relationships we have in our social 00:20:30.299 --> 00:20:32.090 align:start position:0% relationships we have in our social networks 00:20:32.090 --> 00:20:32.100 align:start position:0% networks 00:20:32.100 --> 00:20:35.630 align:start position:0% networks um<00:20:32.640> but<00:20:33.120> we<00:20:33.419> don't<00:20:33.539> want<00:20:33.660> to<00:20:33.780> bring<00:20:33.960> along<00:20:34.640> the 00:20:35.630 --> 00:20:35.640 align:start position:0% um but we don't want to bring along the 00:20:35.640 --> 00:20:37.150 align:start position:0% um but we don't want to bring along the surveillance 00:20:37.150 --> 00:20:37.160 align:start position:0% surveillance 00:20:37.160 --> 00:20:39.529 align:start position:0% surveillance opportunities<00:20:38.160> the<00:20:38.760> opportunities<00:20:39.299> for 00:20:39.529 --> 00:20:39.539 align:start position:0% opportunities the opportunities for 00:20:39.539 --> 00:20:43.190 align:start position:0% opportunities the opportunities for misuse<00:20:40.080> and<00:20:40.380> abuse<00:20:40.820> and<00:20:41.820> we<00:20:42.120> can<00:20:42.419> build 00:20:43.190 --> 00:20:43.200 align:start position:0% misuse and abuse and we can build 00:20:43.200 --> 00:20:45.890 align:start position:0% misuse and abuse and we can build applications<00:20:43.799> that<00:20:44.580> respect<00:20:45.000> personal 00:20:45.890 --> 00:20:45.900 align:start position:0% applications that respect personal 00:20:45.900 --> 00:20:47.990 align:start position:0% applications that respect personal privacy 00:20:47.990 --> 00:20:48.000 align:start position:0% privacy 00:20:48.000 --> 00:20:51.830 align:start position:0% privacy so<00:20:48.960> our<00:20:49.140> theorem<00:20:49.620> accounts<00:20:50.360> can<00:20:51.360> be<00:20:51.480> used<00:20:51.660> for 00:20:51.830 --> 00:20:51.840 align:start position:0% so our theorem accounts can be used for 00:20:51.840 --> 00:20:55.330 align:start position:0% so our theorem accounts can be used for more<00:20:52.020> than<00:20:52.260> just<00:20:52.380> Financial<00:20:53.220> transactions 00:20:55.330 --> 00:20:55.340 align:start position:0% more than just Financial transactions 00:20:55.340 --> 00:20:58.549 align:start position:0% more than just Financial transactions we<00:20:56.340> can<00:20:56.520> start<00:20:57.000> to<00:20:57.240> extend<00:20:57.660> it<00:20:57.840> into<00:20:58.200> the 00:20:58.549 --> 00:20:58.559 align:start position:0% we can start to extend it into the 00:20:58.559 --> 00:21:01.730 align:start position:0% we can start to extend it into the social<00:20:59.280> realm<00:20:59.820> bring<00:21:00.480> along<00:21:00.780> our<00:21:01.140> social 00:21:01.730 --> 00:21:01.740 align:start position:0% social realm bring along our social 00:21:01.740 --> 00:21:04.850 align:start position:0% social realm bring along our social relationships 00:21:04.850 --> 00:21:04.860 align:start position:0% 00:21:04.860 --> 00:21:08.029 align:start position:0% give<00:21:05.520> them<00:21:05.760> a<00:21:06.000> human<00:21:06.179> context<00:21:06.720> and<00:21:07.679> make<00:21:07.799> our 00:21:08.029 --> 00:21:08.039 align:start position:0% give them a human context and make our 00:21:08.039 --> 00:21:11.330 align:start position:0% give them a human context and make our accounts<00:21:08.580> more<00:21:09.360> credibly<00:21:09.840> human 00:21:11.330 --> 00:21:11.340 align:start position:0% accounts more credibly human 00:21:11.340 --> 00:21:14.390 align:start position:0% accounts more credibly human and<00:21:11.760> our<00:21:11.940> applications<00:21:12.419> in<00:21:13.020> the<00:21:13.080> web3<00:21:13.440> world 00:21:14.390 --> 00:21:14.400 align:start position:0% and our applications in the web3 world 00:21:14.400 --> 00:21:16.730 align:start position:0% and our applications in the web3 world so 00:21:16.730 --> 00:21:16.740 align:start position:0% so 00:21:16.740 --> 00:21:20.990 align:start position:0% so the<00:21:17.280> links<00:21:18.200> that<00:21:19.200> QR<00:21:19.559> code<00:21:19.799> is<00:21:20.160> to<00:21:20.400> our<00:21:20.580> Discord 00:21:20.990 --> 00:21:21.000 align:start position:0% the links that QR code is to our Discord 00:21:21.000 --> 00:21:23.510 align:start position:0% the links that QR code is to our Discord you're<00:21:21.900> welcome<00:21:22.080> to<00:21:22.380> come<00:21:22.980> there<00:21:23.160> and<00:21:23.340> ask 00:21:23.510 --> 00:21:23.520 align:start position:0% you're welcome to come there and ask 00:21:23.520 --> 00:21:26.270 align:start position:0% you're welcome to come there and ask questions<00:21:23.820> and<00:21:24.419> find<00:21:24.600> out<00:21:24.780> more<00:21:25.140> you're<00:21:25.980> also 00:21:26.270 --> 00:21:26.280 align:start position:0% questions and find out more you're also 00:21:26.280 --> 00:21:30.470 align:start position:0% questions and find out more you're also welcome<00:21:26.520> to<00:21:26.820> come<00:21:27.419> and<00:21:27.740> hit<00:21:28.740> me<00:21:28.919> up<00:21:29.159> I'll<00:21:29.760> be 00:21:30.470 --> 00:21:30.480 align:start position:0% welcome to come and hit me up I'll be 00:21:30.480 --> 00:21:33.230 align:start position:0% welcome to come and hit me up I'll be hanging<00:21:30.840> around<00:21:31.020> a<00:21:31.320> lot<00:21:31.440> at<00:21:31.919> the<00:21:32.240> temporary 00:21:33.230 --> 00:21:33.240 align:start position:0% hanging around a lot at the temporary 00:21:33.240 --> 00:21:36.409 align:start position:0% hanging around a lot at the temporary autonomous<00:21:33.840> Zone<00:21:34.200> down<00:21:34.380> on<00:21:34.559> the<00:21:34.679> ground<00:21:34.799> floor 00:21:36.409 --> 00:21:36.419 align:start position:0% autonomous Zone down on the ground floor 00:21:36.419 --> 00:21:38.570 align:start position:0% autonomous Zone down on the ground floor um which<00:21:36.720> is<00:21:36.840> the<00:21:36.960> pse's<00:21:37.919> um 00:21:38.570 --> 00:21:38.580 align:start position:0% um which is the pse's um 00:21:38.580 --> 00:21:40.549 align:start position:0% um which is the pse's um uh<00:21:39.360> little<00:21:39.600> uh 00:21:40.549 --> 00:21:40.559 align:start position:0% uh little uh 00:21:40.559 --> 00:21:42.409 align:start position:0% uh little uh hub 00:21:42.409 --> 00:21:42.419 align:start position:0% hub 00:21:42.419 --> 00:21:44.990 align:start position:0% hub um<00:21:42.539> you're<00:21:43.380> welcome<00:21:43.620> to<00:21:43.860> visit<00:21:44.340> the 00:21:44.990 --> 00:21:45.000 align:start position:0% um you're welcome to visit the 00:21:45.000 --> 00:21:48.529 align:start position:0% um you're welcome to visit the application<00:21:46.039> interrep.link<00:21:47.059> and<00:21:48.059> you<00:21:48.360> can 00:21:48.529 --> 00:21:48.539 align:start position:0% application interrep.link and you can 00:21:48.539 --> 00:21:51.610 align:start position:0% application interrep.link and you can sign<00:21:49.440> on<00:21:49.740> there<00:21:49.919> get<00:21:50.220> just<00:21:50.460> get<00:21:51.299> yourself 00:21:51.610 --> 00:21:51.620 align:start position:0% sign on there get just get yourself 00:21:51.620 --> 00:21:55.190 align:start position:0% sign on there get just get yourself signed<00:21:52.620> up<00:21:52.740> with<00:21:52.980> a<00:21:53.280> server<00:21:54.120> ID 00:21:55.190 --> 00:21:55.200 align:start position:0% signed up with a server ID 00:21:55.200 --> 00:21:58.190 align:start position:0% signed up with a server ID see<00:21:55.620> what<00:21:55.799> your<00:21:56.100> Twitter<00:21:56.340> status<00:21:57.059> is<00:21:57.419> maybe 00:21:58.190 --> 00:21:58.200 align:start position:0% see what your Twitter status is maybe 00:21:58.200 --> 00:21:59.930 align:start position:0% see what your Twitter status is maybe you<00:21:58.380> have<00:21:58.500> to<00:21:58.620> work<00:21:58.799> on<00:21:58.980> that 00:21:59.930 --> 00:21:59.940 align:start position:0% you have to work on that 00:21:59.940 --> 00:22:03.110 align:start position:0% you have to work on that we've<00:22:00.900> got<00:22:01.020> documentation<00:22:01.620> links<00:22:02.220> we've<00:22:02.940> got 00:22:03.110 --> 00:22:03.120 align:start position:0% we've got documentation links we've got 00:22:03.120 --> 00:22:06.070 align:start position:0% we've got documentation links we've got our<00:22:03.419> code<00:22:03.980> open<00:22:04.980> source 00:22:06.070 --> 00:22:06.080 align:start position:0% our code open source 00:22:06.080 --> 00:22:10.310 align:start position:0% our code open source you'll<00:22:07.080> find<00:22:07.260> all<00:22:07.559> that<00:22:07.880> on<00:22:08.880> the<00:22:09.539> um<00:22:09.600> on<00:22:10.200> those 00:22:10.310 --> 00:22:10.320 align:start position:0% you'll find all that on the um on those 00:22:10.320 --> 00:22:14.090 align:start position:0% you'll find all that on the um on those links<00:22:10.679> but<00:22:11.539> yeah<00:22:12.539> please<00:22:12.840> come<00:22:13.799> to<00:22:13.980> the 00:22:14.090 --> 00:22:14.100 align:start position:0% links but yeah please come to the 00:22:14.100 --> 00:22:18.770 align:start position:0% links but yeah please come to the Discord<00:22:14.460> and<00:22:15.120> ask<00:22:15.780> questions<00:22:16.340> if<00:22:17.340> you<00:22:17.640> or<00:22:18.539> come 00:22:18.770 --> 00:22:18.780 align:start position:0% Discord and ask questions if you or come 00:22:18.780 --> 00:22:21.049 align:start position:0% Discord and ask questions if you or come and<00:22:18.960> ask<00:22:19.080> me<00:22:19.260> in<00:22:19.500> person 00:22:21.049 --> 00:22:21.059 align:start position:0% and ask me in person 00:22:21.059 --> 00:22:23.870 align:start position:0% and ask me in person uh<00:22:21.900> so<00:22:22.140> thanks<00:22:22.500> for<00:22:22.679> all<00:22:22.799> that 00:22:23.870 --> 00:22:23.880 align:start position:0% uh so thanks for all that 00:22:23.880 --> 00:22:25.130 align:start position:0% uh so thanks for all that um 00:22:25.130 --> 00:22:25.140 align:start position:0% um 00:22:25.140 --> 00:22:29.690 align:start position:0% um the<00:22:25.919> QR<00:22:26.280> code<00:22:26.520> on<00:22:27.360> this<00:22:27.480> slide<00:22:27.780> is<00:22:28.440> the<00:22:29.340> Discord 00:22:29.690 --> 00:22:29.700 align:start position:0% the QR code on this slide is the Discord 00:22:29.700 --> 00:22:32.390 align:start position:0% the QR code on this slide is the Discord for<00:22:30.000> privacy<00:22:30.419> and<00:22:30.600> scaling<00:22:31.020> we<00:22:31.740> do<00:22:31.919> lots<00:22:32.340> of 00:22:32.390 --> 00:22:32.400 align:start position:0% for privacy and scaling we do lots of 00:22:32.400 --> 00:22:35.590 align:start position:0% for privacy and scaling we do lots of cool<00:22:32.880> applications 00:22:35.590 --> 00:22:35.600 align:start position:0% cool applications 00:22:35.600 --> 00:22:39.770 align:start position:0% cool applications in<00:22:36.600> the<00:22:36.840> xero<00:22:37.380> knowledge<00:22:37.679> space<00:22:38.179> so<00:22:39.179> uh<00:22:39.600> you 00:22:39.770 --> 00:22:39.780 align:start position:0% in the xero knowledge space so uh you 00:22:39.780 --> 00:22:42.110 align:start position:0% in the xero knowledge space so uh you can<00:22:39.960> join<00:22:40.919> that<00:22:41.039> Discord<00:22:41.400> and<00:22:41.640> ask<00:22:41.820> questions 00:22:42.110 --> 00:22:42.120 align:start position:0% can join that Discord and ask questions 00:22:42.120 --> 00:22:45.770 align:start position:0% can join that Discord and ask questions check<00:22:43.020> out<00:22:43.260> our<00:22:43.559> job<00:22:44.159> openings<00:22:45.059> if<00:22:45.419> you<00:22:45.600> like 00:22:45.770 --> 00:22:45.780 align:start position:0% check out our job openings if you like 00:22:45.780 --> 00:22:48.890 align:start position:0% check out our job openings if you like building<00:22:46.220> cool<00:22:47.220> applications 00:22:48.890 --> 00:22:48.900 align:start position:0% building cool applications 00:22:48.900 --> 00:22:51.649 align:start position:0% building cool applications for<00:22:49.380> privacy<00:22:49.799> and<00:22:49.980> scaling<00:22:50.460> and<00:22:51.240> check<00:22:51.480> that 00:22:51.649 --> 00:22:51.659 align:start position:0% for privacy and scaling and check that 00:22:51.659 --> 00:22:53.450 align:start position:0% for privacy and scaling and check that out 00:22:53.450 --> 00:22:53.460 align:start position:0% out 00:22:53.460 --> 00:22:56.870 align:start position:0% out um and<00:22:54.240> on<00:22:54.419> that<00:22:54.600> note<00:22:54.720> thank<00:22:55.500> you 00:22:56.870 --> 00:22:56.880 align:start position:0% um and on that note thank you 00:22:56.880 --> 00:23:00.909 align:start position:0% um and on that note thank you [Applause]