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:13.930 align:start position:0% [Music] 00:00:13.930 --> 00:00:13.940 align:start position:0% 00:00:13.940 --> 00:00:16.970 align:start position:0% and<00:00:14.940> I<00:00:15.120> work<00:00:15.299> as<00:00:15.480> a<00:00:15.599> software<00:00:15.900> engineer<00:00:16.260> with<00:00:16.859> a 00:00:16.970 --> 00:00:16.980 align:start position:0% and I work as a software engineer with a 00:00:16.980 --> 00:00:21.050 align:start position:0% and I work as a software engineer with a privacy<00:00:17.340> and<00:00:17.520> scanning<00:00:17.880> Explorations<00:00:18.359> team 00:00:21.050 --> 00:00:21.060 align:start position:0% 00:00:21.060 --> 00:00:23.929 align:start position:0% so<00:00:21.600> I'm<00:00:22.560> going<00:00:22.800> to<00:00:22.980> talk<00:00:23.160> about<00:00:23.340> Anonymous 00:00:23.929 --> 00:00:23.939 align:start position:0% so I'm going to talk about Anonymous 00:00:23.939 --> 00:00:25.730 align:start position:0% so I'm going to talk about Anonymous signaling<00:00:24.480> on<00:00:24.600> ethereum 00:00:25.730 --> 00:00:25.740 align:start position:0% signaling on ethereum 00:00:25.740 --> 00:00:27.349 align:start position:0% signaling on ethereum and<00:00:26.220> I<00:00:26.340> would<00:00:26.519> like<00:00:26.699> to<00:00:26.820> start<00:00:27.000> with<00:00:27.240> an 00:00:27.349 --> 00:00:27.359 align:start position:0% and I would like to start with an 00:00:27.359 --> 00:00:29.150 align:start position:0% and I would like to start with an important<00:00:27.720> question 00:00:29.150 --> 00:00:29.160 align:start position:0% important question 00:00:29.160 --> 00:00:31.669 align:start position:0% important question why<00:00:29.699> anonymity<00:00:30.240> is<00:00:30.480> important 00:00:31.669 --> 00:00:31.679 align:start position:0% why anonymity is important 00:00:31.679 --> 00:00:34.069 align:start position:0% why anonymity is important I<00:00:32.279> don't<00:00:32.399> know<00:00:32.579> why<00:00:32.880> people<00:00:33.120> are<00:00:33.360> so<00:00:33.600> Keen<00:00:33.899> to 00:00:34.069 --> 00:00:34.079 align:start position:0% I don't know why people are so Keen to 00:00:34.079 --> 00:00:35.870 align:start position:0% I don't know why people are so Keen to put<00:00:34.200> the<00:00:34.380> details<00:00:34.800> of<00:00:34.980> different<00:00:35.160> life<00:00:35.640> in 00:00:35.870 --> 00:00:35.880 align:start position:0% put the details of different life in 00:00:35.880 --> 00:00:39.350 align:start position:0% put the details of different life in public<00:00:36.140> they<00:00:37.140> forget<00:00:37.380> that<00:00:38.100> invisibility<00:00:38.700> is 00:00:39.350 --> 00:00:39.360 align:start position:0% public they forget that invisibility is 00:00:39.360 --> 00:00:41.270 align:start position:0% public they forget that invisibility is a<00:00:39.540> superpower 00:00:41.270 --> 00:00:41.280 align:start position:0% a superpower 00:00:41.280 --> 00:00:43.250 align:start position:0% a superpower we<00:00:41.700> cannot<00:00:41.940> be<00:00:42.059> sure<00:00:42.300> if<00:00:42.480> this<00:00:42.660> quote<00:00:42.899> is<00:00:43.079> from 00:00:43.250 --> 00:00:43.260 align:start position:0% we cannot be sure if this quote is from 00:00:43.260 --> 00:00:46.250 align:start position:0% we cannot be sure if this quote is from Banksy<00:00:43.860> but<00:00:44.399> even<00:00:44.579> if<00:00:44.820> it<00:00:44.940> was<00:00:45.059> Anonymous<00:00:45.540> the 00:00:46.250 --> 00:00:46.260 align:start position:0% Banksy but even if it was Anonymous the 00:00:46.260 --> 00:00:48.410 align:start position:0% Banksy but even if it was Anonymous the message<00:00:46.440> is<00:00:46.739> still<00:00:46.920> very<00:00:47.100> important 00:00:48.410 --> 00:00:48.420 align:start position:0% message is still very important 00:00:48.420 --> 00:00:51.170 align:start position:0% message is still very important invisibility<00:00:49.260> or<00:00:49.739> anonymity<00:00:50.280> is<00:00:51.000> a 00:00:51.170 --> 00:00:51.180 align:start position:0% invisibility or anonymity is a 00:00:51.180 --> 00:00:54.470 align:start position:0% invisibility or anonymity is a superpower<00:00:51.660> because<00:00:52.260> intercouples<00:00:53.160> an<00:00:53.399> idea 00:00:54.470 --> 00:00:54.480 align:start position:0% superpower because intercouples an idea 00:00:54.480 --> 00:00:57.229 align:start position:0% superpower because intercouples an idea from<00:00:54.780> the<00:00:55.020> density<00:00:55.320> of<00:00:55.500> its<00:00:55.680> owner<00:00:56.460> because<00:00:56.940> it 00:00:57.229 --> 00:00:57.239 align:start position:0% from the density of its owner because it 00:00:57.239 --> 00:00:59.810 align:start position:0% from the density of its owner because it allows<00:00:57.539> flowers<00:00:57.840> to<00:00:58.620> be<00:00:58.739> thrown<00:00:59.039> without<00:00:59.579> the 00:00:59.810 --> 00:00:59.820 align:start position:0% allows flowers to be thrown without the 00:00:59.820 --> 00:01:02.389 align:start position:0% allows flowers to be thrown without the identity<00:01:00.059> of<00:01:00.300> the<00:01:00.360> thrower<00:01:00.840> being<00:01:01.320> known<00:01:01.559> so 00:01:02.389 --> 00:01:02.399 align:start position:0% identity of the thrower being known so 00:01:02.399 --> 00:01:04.310 align:start position:0% identity of the thrower being known so all<00:01:03.000> talk<00:01:03.239> ideas<00:01:03.480> are<00:01:03.780> intrinsically 00:01:04.310 --> 00:01:04.320 align:start position:0% all talk ideas are intrinsically 00:01:04.320 --> 00:01:06.950 align:start position:0% all talk ideas are intrinsically connected<00:01:04.860> to<00:01:05.280> the<00:01:05.460> hotel<00:01:05.760> sometimes<00:01:06.720> the 00:01:06.950 --> 00:01:06.960 align:start position:0% connected to the hotel sometimes the 00:01:06.960 --> 00:01:08.810 align:start position:0% connected to the hotel sometimes the message<00:01:07.140> is<00:01:07.860> more<00:01:08.040> important<00:01:08.400> than<00:01:08.640> the 00:01:08.810 --> 00:01:08.820 align:start position:0% message is more important than the 00:01:08.820 --> 00:01:11.390 align:start position:0% message is more important than the messenger<00:01:09.600> and<00:01:10.260> sometimes<00:01:10.680> preserving<00:01:11.280> the 00:01:11.390 --> 00:01:11.400 align:start position:0% messenger and sometimes preserving the 00:01:11.400 --> 00:01:13.730 align:start position:0% messenger and sometimes preserving the identity<00:01:11.700> of<00:01:11.939> the<00:01:12.060> messenger<00:01:12.540> is<00:01:13.260> even<00:01:13.500> more 00:01:13.730 --> 00:01:13.740 align:start position:0% identity of the messenger is even more 00:01:13.740 --> 00:01:14.690 align:start position:0% identity of the messenger is even more important 00:01:14.690 --> 00:01:14.700 align:start position:0% important 00:01:14.700 --> 00:01:16.789 align:start position:0% important so<00:01:15.180> anonymity<00:01:15.780> can<00:01:16.020> therefore<00:01:16.260> become<00:01:16.619> an 00:01:16.789 --> 00:01:16.799 align:start position:0% so anonymity can therefore become an 00:01:16.799 --> 00:01:19.749 align:start position:0% so anonymity can therefore become an important<00:01:17.159> tool<00:01:17.520> because<00:01:18.180> it<00:01:19.140> limits<00:01:19.560> power 00:01:19.749 --> 00:01:19.759 align:start position:0% important tool because it limits power 00:01:19.759 --> 00:01:23.270 align:start position:0% important tool because it limits power those<00:01:20.759> with<00:01:21.420> a<00:01:21.600> lot<00:01:21.720> of<00:01:21.840> power<00:01:22.140> derive<00:01:22.740> much<00:01:22.979> of 00:01:23.270 --> 00:01:23.280 align:start position:0% those with a lot of power derive much of 00:01:23.280 --> 00:01:25.130 align:start position:0% those with a lot of power derive much of that<00:01:23.520> power<00:01:23.759> from<00:01:24.060> Knowledge<00:01:24.479> from 00:01:25.130 --> 00:01:25.140 align:start position:0% that power from Knowledge from 00:01:25.140 --> 00:01:26.330 align:start position:0% that power from Knowledge from information 00:01:26.330 --> 00:01:26.340 align:start position:0% information 00:01:26.340 --> 00:01:29.030 align:start position:0% information the<00:01:26.820> more<00:01:27.000> someone<00:01:27.240> knows<00:01:27.720> about<00:01:27.900> us 00:01:29.030 --> 00:01:29.040 align:start position:0% the more someone knows about us 00:01:29.040 --> 00:01:32.030 align:start position:0% the more someone knows about us the<00:01:29.460> more<00:01:29.580> power<00:01:29.820> they<00:01:30.119> can<00:01:30.299> have<00:01:30.420> over<00:01:30.720> us 00:01:32.030 --> 00:01:32.040 align:start position:0% the more power they can have over us 00:01:32.040 --> 00:01:34.870 align:start position:0% the more power they can have over us keeping<00:01:32.640> our<00:01:32.759> data<00:01:33.360> or<00:01:33.720> our<00:01:33.960> identity<00:01:34.380> private 00:01:34.870 --> 00:01:34.880 align:start position:0% keeping our data or our identity private 00:01:34.880 --> 00:01:36.830 align:start position:0% keeping our data or our identity private decentralized<00:01:35.880> that<00:01:36.060> power 00:01:36.830 --> 00:01:36.840 align:start position:0% decentralized that power 00:01:36.840 --> 00:01:39.649 align:start position:0% decentralized that power anonymity<00:01:37.560> promotes<00:01:38.220> freedom<00:01:38.579> of<00:01:38.640> speech 00:01:39.649 --> 00:01:39.659 align:start position:0% anonymity promotes freedom of speech 00:01:39.659 --> 00:01:42.050 align:start position:0% anonymity promotes freedom of speech the<00:01:40.200> first<00:01:40.380> step<00:01:40.560> in<00:01:40.799> censoring<00:01:41.280> an<00:01:41.400> idea<00:01:41.700> is 00:01:42.050 --> 00:01:42.060 align:start position:0% the first step in censoring an idea is 00:01:42.060 --> 00:01:44.929 align:start position:0% the first step in censoring an idea is to<00:01:42.180> attack<00:01:42.360> its<00:01:43.140> author<00:01:43.920> and<00:01:44.400> the<00:01:44.579> fear<00:01:44.820> of 00:01:44.929 --> 00:01:44.939 align:start position:0% to attack its author and the fear of 00:01:44.939 --> 00:01:47.030 align:start position:0% to attack its author and the fear of suffering<00:01:45.299> repercussions<00:01:45.960> for<00:01:46.320> what<00:01:46.560> we<00:01:46.799> say 00:01:47.030 --> 00:01:47.040 align:start position:0% suffering repercussions for what we say 00:01:47.040 --> 00:01:51.530 align:start position:0% suffering repercussions for what we say or<00:01:47.640> write<00:01:48.299> also<00:01:49.140> limits<00:01:49.619> our<00:01:49.860> thinking 00:01:51.530 --> 00:01:51.540 align:start position:0% or write also limits our thinking 00:01:51.540 --> 00:01:54.170 align:start position:0% or write also limits our thinking so<00:01:52.140> knowing<00:01:52.560> that<00:01:52.799> our<00:01:53.040> data<00:01:53.520> and<00:01:53.640> identity 00:01:54.170 --> 00:01:54.180 align:start position:0% so knowing that our data and identity 00:01:54.180 --> 00:01:57.830 align:start position:0% so knowing that our data and identity are<00:01:54.420> safe<00:01:54.619> encourages<00:01:55.619> us<00:01:55.979> to<00:01:56.700> think<00:01:56.880> freely 00:01:57.830 --> 00:01:57.840 align:start position:0% are safe encourages us to think freely 00:01:57.840 --> 00:02:00.530 align:start position:0% are safe encourages us to think freely anonymity<00:01:58.439> safeguards<00:01:59.100> reputation<00:01:59.579> it<00:02:00.420> is 00:02:00.530 --> 00:02:00.540 align:start position:0% anonymity safeguards reputation it is 00:02:00.540 --> 00:02:02.149 align:start position:0% anonymity safeguards reputation it is important<00:02:00.899> that<00:02:01.259> people<00:02:01.439> are<00:02:01.740> held 00:02:02.149 --> 00:02:02.159 align:start position:0% important that people are held 00:02:02.159 --> 00:02:04.130 align:start position:0% important that people are held accountable<00:02:02.579> for<00:02:03.240> their<00:02:03.420> actions<00:02:03.899> and 00:02:04.130 --> 00:02:04.140 align:start position:0% accountable for their actions and 00:02:04.140 --> 00:02:05.469 align:start position:0% accountable for their actions and especially<00:02:04.439> for<00:02:04.680> their<00:02:04.860> mistakes 00:02:05.469 --> 00:02:05.479 align:start position:0% especially for their mistakes 00:02:05.479 --> 00:02:08.330 align:start position:0% especially for their mistakes particularly<00:02:06.479> when<00:02:07.079> these<00:02:07.560> people<00:02:07.680> have<00:02:08.099> a 00:02:08.330 --> 00:02:08.340 align:start position:0% particularly when these people have a 00:02:08.340 --> 00:02:10.910 align:start position:0% particularly when these people have a lot<00:02:08.399> of<00:02:08.580> responsibility<00:02:09.360> when<00:02:10.200> they<00:02:10.440> have<00:02:10.679> an 00:02:10.910 --> 00:02:10.920 align:start position:0% lot of responsibility when they have an 00:02:10.920 --> 00:02:13.550 align:start position:0% lot of responsibility when they have an important<00:02:11.280> role<00:02:11.700> but<00:02:12.480> it<00:02:12.780> is<00:02:12.900> also<00:02:13.200> important 00:02:13.550 --> 00:02:13.560 align:start position:0% important role but it is also important 00:02:13.560 --> 00:02:15.650 align:start position:0% important role but it is also important that<00:02:13.860> our<00:02:13.980> ideas<00:02:14.220> are<00:02:14.640> not<00:02:14.819> judged<00:02:15.180> based<00:02:15.540> on 00:02:15.650 --> 00:02:15.660 align:start position:0% that our ideas are not judged based on 00:02:15.660 --> 00:02:18.949 align:start position:0% that our ideas are not judged based on who<00:02:16.020> we<00:02:16.200> are<00:02:16.379> but<00:02:17.040> either<00:02:17.400> on<00:02:18.120> what<00:02:18.420> we<00:02:18.540> have<00:02:18.720> to 00:02:18.949 --> 00:02:18.959 align:start position:0% who we are but either on what we have to 00:02:18.959 --> 00:02:21.350 align:start position:0% who we are but either on what we have to say<00:02:19.140> anonymity<00:02:20.040> allows<00:02:20.640> an<00:02:20.760> idea<00:02:21.060> to<00:02:21.239> be 00:02:21.350 --> 00:02:21.360 align:start position:0% say anonymity allows an idea to be 00:02:21.360 --> 00:02:23.449 align:start position:0% say anonymity allows an idea to be shared<00:02:21.660> regardless<00:02:22.260> of<00:02:22.680> its<00:02:22.980> author's 00:02:23.449 --> 00:02:23.459 align:start position:0% shared regardless of its author's 00:02:23.459 --> 00:02:25.729 align:start position:0% shared regardless of its author's reputation<00:02:23.940> which<00:02:24.780> allows<00:02:25.200> people<00:02:25.379> to 00:02:25.729 --> 00:02:25.739 align:start position:0% reputation which allows people to 00:02:25.739 --> 00:02:27.949 align:start position:0% reputation which allows people to consider<00:02:26.160> and<00:02:26.340> evaluate<00:02:26.940> ideas<00:02:27.180> for<00:02:27.599> a<00:02:27.780> more 00:02:27.949 --> 00:02:27.959 align:start position:0% consider and evaluate ideas for a more 00:02:27.959 --> 00:02:31.070 align:start position:0% consider and evaluate ideas for a more objective<00:02:28.800> perspective<00:02:29.879> most<00:02:30.480> of<00:02:30.660> us<00:02:30.780> are 00:02:31.070 --> 00:02:31.080 align:start position:0% objective perspective most of us are 00:02:31.080 --> 00:02:33.350 align:start position:0% objective perspective most of us are aware<00:02:31.379> of<00:02:31.560> the<00:02:31.800> importance<00:02:32.099> of<00:02:32.280> anonymity<00:02:32.819> and 00:02:33.350 --> 00:02:33.360 align:start position:0% aware of the importance of anonymity and 00:02:33.360 --> 00:02:36.650 align:start position:0% aware of the importance of anonymity and privacy<00:02:33.840> but<00:02:34.620> what<00:02:34.920> about<00:02:35.099> our<00:02:35.400> challenges 00:02:36.650 --> 00:02:36.660 align:start position:0% privacy but what about our challenges 00:02:36.660 --> 00:02:38.809 align:start position:0% privacy but what about our challenges what<00:02:37.260> are<00:02:37.379> the<00:02:37.500> main<00:02:37.680> drawbacks<00:02:38.280> right<00:02:38.640> now 00:02:38.809 --> 00:02:38.819 align:start position:0% what are the main drawbacks right now 00:02:38.819 --> 00:02:40.790 align:start position:0% what are the main drawbacks right now and<00:02:39.180> how<00:02:39.420> can<00:02:39.540> we<00:02:39.660> solve<00:02:39.959> them 00:02:40.790 --> 00:02:40.800 align:start position:0% and how can we solve them 00:02:40.800 --> 00:02:43.009 align:start position:0% and how can we solve them there<00:02:41.340> are<00:02:41.459> probably<00:02:41.640> many<00:02:41.879> reasons<00:02:42.360> but<00:02:42.780> two 00:02:43.009 --> 00:02:43.019 align:start position:0% there are probably many reasons but two 00:02:43.019 --> 00:02:45.410 align:start position:0% there are probably many reasons but two of<00:02:43.200> them<00:02:43.319> deserve<00:02:43.860> particular<00:02:44.220> attention<00:02:44.580> the 00:02:45.410 --> 00:02:45.420 align:start position:0% of them deserve particular attention the 00:02:45.420 --> 00:02:48.350 align:start position:0% of them deserve particular attention the first<00:02:45.540> one<00:02:45.780> is<00:02:46.019> complexity<00:02:46.680> of<00:02:46.920> Technology 00:02:48.350 --> 00:02:48.360 align:start position:0% first one is complexity of Technology 00:02:48.360 --> 00:02:50.330 align:start position:0% first one is complexity of Technology in<00:02:48.840> recent<00:02:49.140> years 00:02:50.330 --> 00:02:50.340 align:start position:0% in recent years 00:02:50.340 --> 00:02:52.309 align:start position:0% in recent years we<00:02:50.760> have<00:02:50.879> seen<00:02:51.060> a<00:02:51.300> constant<00:02:51.599> growth<00:02:51.959> in<00:02:52.140> the 00:02:52.309 --> 00:02:52.319 align:start position:0% we have seen a constant growth in the 00:02:52.319 --> 00:02:54.050 align:start position:0% we have seen a constant growth in the development<00:02:52.680> and<00:02:52.920> use<00:02:53.099> of<00:02:53.340> cryptographic 00:02:54.050 --> 00:02:54.060 align:start position:0% development and use of cryptographic 00:02:54.060 --> 00:02:55.190 align:start position:0% development and use of cryptographic Technologies 00:02:55.190 --> 00:02:55.200 align:start position:0% Technologies 00:02:55.200 --> 00:02:57.350 align:start position:0% Technologies data<00:02:55.680> knowledge<00:02:55.920> proofs<00:02:56.340> for<00:02:56.760> example<00:02:57.060> are 00:02:57.350 --> 00:02:57.360 align:start position:0% data knowledge proofs for example are 00:02:57.360 --> 00:02:59.630 align:start position:0% data knowledge proofs for example are now<00:02:57.540> being<00:02:57.720> used<00:02:57.900> in<00:02:58.080> many<00:02:58.260> applications 00:02:59.630 --> 00:02:59.640 align:start position:0% now being used in many applications 00:02:59.640 --> 00:03:01.190 align:start position:0% now being used in many applications proving<00:03:00.239> you<00:03:00.420> have<00:03:00.540> a<00:03:00.720> certain<00:03:00.840> information 00:03:01.190 --> 00:03:01.200 align:start position:0% proving you have a certain information 00:03:01.200 --> 00:03:03.290 align:start position:0% proving you have a certain information without<00:03:01.800> revealing<00:03:02.459> the<00:03:02.519> information<00:03:02.700> itself 00:03:03.290 --> 00:03:03.300 align:start position:0% without revealing the information itself 00:03:03.300 --> 00:03:06.949 align:start position:0% without revealing the information itself is<00:03:03.900> a<00:03:04.140> really<00:03:04.319> powerful<00:03:04.920> concept<00:03:05.640> by<00:03:06.540> the<00:03:06.780> way 00:03:06.949 --> 00:03:06.959 align:start position:0% is a really powerful concept by the way 00:03:06.959 --> 00:03:09.710 align:start position:0% is a really powerful concept by the way these<00:03:07.680> Technologies<00:03:08.160> work<00:03:08.459> is<00:03:09.060> not<00:03:09.300> trivial 00:03:09.710 --> 00:03:09.720 align:start position:0% these Technologies work is not trivial 00:03:09.720 --> 00:03:11.690 align:start position:0% these Technologies work is not trivial for<00:03:10.379> people<00:03:10.620> without<00:03:10.860> a<00:03:11.159> background<00:03:11.459> in 00:03:11.690 --> 00:03:11.700 align:start position:0% for people without a background in 00:03:11.700 --> 00:03:13.910 align:start position:0% for people without a background in mathematics<00:03:12.239> or<00:03:12.420> cryptography 00:03:13.910 --> 00:03:13.920 align:start position:0% mathematics or cryptography 00:03:13.920 --> 00:03:16.190 align:start position:0% mathematics or cryptography in<00:03:14.519> addition<00:03:14.819> the<00:03:15.300> availability<00:03:15.659> of<00:03:15.959> simple 00:03:16.190 --> 00:03:16.200 align:start position:0% in addition the availability of simple 00:03:16.200 --> 00:03:18.350 align:start position:0% in addition the availability of simple and<00:03:16.440> practical<00:03:16.800> development<00:03:17.280> tools<00:03:17.700> is<00:03:18.120> still 00:03:18.350 --> 00:03:18.360 align:start position:0% and practical development tools is still 00:03:18.360 --> 00:03:19.430 align:start position:0% and practical development tools is still Limited 00:03:19.430 --> 00:03:19.440 align:start position:0% Limited 00:03:19.440 --> 00:03:21.470 align:start position:0% Limited well<00:03:20.099> a<00:03:20.400> lot<00:03:20.519> of<00:03:20.580> progress<00:03:20.940> has<00:03:21.180> been<00:03:21.360> made 00:03:21.470 --> 00:03:21.480 align:start position:0% well a lot of progress has been made 00:03:21.480 --> 00:03:23.930 align:start position:0% well a lot of progress has been made actually<00:03:21.720> but<00:03:22.560> I<00:03:22.980> believe 00:03:23.930 --> 00:03:23.940 align:start position:0% actually but I believe 00:03:23.940 --> 00:03:26.030 align:start position:0% actually but I believe one<00:03:24.480> more<00:03:24.599> step<00:03:24.840> is<00:03:25.140> needed<00:03:25.500> in<00:03:25.680> order<00:03:25.800> to 00:03:26.030 --> 00:03:26.040 align:start position:0% one more step is needed in order to 00:03:26.040 --> 00:03:28.309 align:start position:0% one more step is needed in order to further<00:03:26.400> abstract<00:03:26.760> some<00:03:27.060> technical<00:03:27.360> Concepts 00:03:28.309 --> 00:03:28.319 align:start position:0% further abstract some technical Concepts 00:03:28.319 --> 00:03:30.710 align:start position:0% further abstract some technical Concepts so<00:03:28.920> the<00:03:29.760> second<00:03:29.879> drawback<00:03:30.360> is<00:03:30.599> the 00:03:30.710 --> 00:03:30.720 align:start position:0% so the second drawback is the 00:03:30.720 --> 00:03:32.390 align:start position:0% so the second drawback is the indifference<00:03:31.140> of<00:03:31.319> people 00:03:32.390 --> 00:03:32.400 align:start position:0% indifference of people 00:03:32.400 --> 00:03:34.970 align:start position:0% indifference of people one<00:03:32.879> of<00:03:33.000> the<00:03:33.180> reasons<00:03:33.720> why<00:03:34.260> some<00:03:34.560> people<00:03:34.739> don't 00:03:34.970 --> 00:03:34.980 align:start position:0% one of the reasons why some people don't 00:03:34.980 --> 00:03:37.070 align:start position:0% one of the reasons why some people don't care<00:03:35.159> enough<00:03:35.400> about<00:03:35.760> privacy 00:03:37.070 --> 00:03:37.080 align:start position:0% care enough about privacy 00:03:37.080 --> 00:03:39.830 align:start position:0% care enough about privacy and<00:03:37.440> anonymity<00:03:37.980> might<00:03:38.580> be<00:03:38.760> that<00:03:39.120> there<00:03:39.540> is<00:03:39.659> not 00:03:39.830 --> 00:03:39.840 align:start position:0% and anonymity might be that there is not 00:03:39.840 --> 00:03:42.770 align:start position:0% and anonymity might be that there is not enough<00:03:40.019> awareness<00:03:40.680> and<00:03:41.280> education<00:03:41.819> about<00:03:42.299> how 00:03:42.770 --> 00:03:42.780 align:start position:0% enough awareness and education about how 00:03:42.780 --> 00:03:45.470 align:start position:0% enough awareness and education about how our<00:03:43.200> data<00:03:43.680> is<00:03:43.739> used<00:03:43.920> and<00:03:44.640> why<00:03:44.819> anonymity<00:03:45.299> is 00:03:45.470 --> 00:03:45.480 align:start position:0% our data is used and why anonymity is 00:03:45.480 --> 00:03:47.449 align:start position:0% our data is used and why anonymity is important<00:03:45.840> in<00:03:46.019> ielt<00:03:46.440> society 00:03:47.449 --> 00:03:47.459 align:start position:0% important in ielt society 00:03:47.459 --> 00:03:49.789 align:start position:0% important in ielt society so<00:03:48.180> what<00:03:48.420> can<00:03:48.599> we<00:03:48.720> do<00:03:48.840> then 00:03:49.789 --> 00:03:49.799 align:start position:0% so what can we do then 00:03:49.799 --> 00:03:51.890 align:start position:0% so what can we do then there<00:03:50.340> are<00:03:50.459> many<00:03:50.580> solutions<00:03:51.060> but<00:03:51.420> I<00:03:51.780> would 00:03:51.890 --> 00:03:51.900 align:start position:0% there are many solutions but I would 00:03:51.900 --> 00:03:54.110 align:start position:0% there are many solutions but I would like<00:03:52.080> to<00:03:52.260> focus<00:03:52.440> on<00:03:52.560> free<00:03:52.739> Solutions<00:03:53.159> the 00:03:54.110 --> 00:03:54.120 align:start position:0% like to focus on free Solutions the 00:03:54.120 --> 00:03:56.390 align:start position:0% like to focus on free Solutions the first<00:03:54.239> one<00:03:54.420> is<00:03:54.599> privacy<00:03:55.080> by<00:03:55.319> default<00:03:55.680> the 00:03:56.390 --> 00:03:56.400 align:start position:0% first one is privacy by default the 00:03:56.400 --> 00:03:58.309 align:start position:0% first one is privacy by default the right<00:03:56.640> to<00:03:56.819> privacy<00:03:57.239> is<00:03:57.659> mentioned<00:03:58.019> in<00:03:58.140> most 00:03:58.309 --> 00:03:58.319 align:start position:0% right to privacy is mentioned in most 00:03:58.319 --> 00:04:00.710 align:start position:0% right to privacy is mentioned in most natural<00:03:58.560> constitutions<00:03:59.400> but<00:04:00.120> it<00:04:00.299> has<00:04:00.480> often 00:04:00.710 --> 00:04:00.720 align:start position:0% natural constitutions but it has often 00:04:00.720 --> 00:04:02.270 align:start position:0% natural constitutions but it has often been<00:04:00.900> neglected<00:04:01.379> in<00:04:01.680> the<00:04:01.799> name<00:04:01.920> of<00:04:02.099> National 00:04:02.270 --> 00:04:02.280 align:start position:0% been neglected in the name of National 00:04:02.280 --> 00:04:04.789 align:start position:0% been neglected in the name of National Security<00:04:02.760> issues<00:04:03.420> or<00:04:04.260> to<00:04:04.500> make<00:04:04.620> the 00:04:04.789 --> 00:04:04.799 align:start position:0% Security issues or to make the 00:04:04.799 --> 00:04:07.670 align:start position:0% Security issues or to make the applications<00:04:05.220> we<00:04:05.519> use<00:04:05.700> every<00:04:06.120> day<00:04:06.680> smarter 00:04:07.670 --> 00:04:07.680 align:start position:0% applications we use every day smarter 00:04:07.680 --> 00:04:09.050 align:start position:0% applications we use every day smarter and<00:04:07.860> more<00:04:08.099> efficient 00:04:09.050 --> 00:04:09.060 align:start position:0% and more efficient 00:04:09.060 --> 00:04:11.210 align:start position:0% and more efficient privacy<00:04:09.720> and<00:04:10.019> cryptography<00:04:10.680> should<00:04:10.860> be<00:04:11.040> the 00:04:11.210 --> 00:04:11.220 align:start position:0% privacy and cryptography should be the 00:04:11.220 --> 00:04:13.630 align:start position:0% privacy and cryptography should be the backbone<00:04:11.700> of<00:04:12.239> the<00:04:12.420> internet<00:04:12.480> infrastructure 00:04:13.630 --> 00:04:13.640 align:start position:0% backbone of the internet infrastructure 00:04:13.640 --> 00:04:16.430 align:start position:0% backbone of the internet infrastructure protocols<00:04:14.640> and<00:04:14.819> applications<00:04:15.420> should<00:04:16.260> be 00:04:16.430 --> 00:04:16.440 align:start position:0% protocols and applications should be 00:04:16.440 --> 00:04:19.490 align:start position:0% protocols and applications should be supported<00:04:17.040> all<00:04:17.340> user<00:04:17.699> data<00:04:18.000> by<00:04:18.120> default<00:04:19.019> and 00:04:19.490 --> 00:04:19.500 align:start position:0% supported all user data by default and 00:04:19.500 --> 00:04:21.949 align:start position:0% supported all user data by default and in<00:04:19.739> addition<00:04:20.180> users<00:04:21.180> should<00:04:21.479> be<00:04:21.600> free<00:04:21.780> to 00:04:21.949 --> 00:04:21.959 align:start position:0% in addition users should be free to 00:04:21.959 --> 00:04:23.749 align:start position:0% in addition users should be free to change<00:04:22.139> the<00:04:22.320> settings<00:04:22.560> not<00:04:22.979> the<00:04:23.160> opposite 00:04:23.749 --> 00:04:23.759 align:start position:0% change the settings not the opposite 00:04:23.759 --> 00:04:26.330 align:start position:0% change the settings not the opposite another<00:04:24.300> point<00:04:24.600> is<00:04:24.840> education<00:04:25.320> explaining<00:04:26.160> to 00:04:26.330 --> 00:04:26.340 align:start position:0% another point is education explaining to 00:04:26.340 --> 00:04:29.090 align:start position:0% another point is education explaining to people<00:04:26.520> why<00:04:26.940> privacy<00:04:27.419> is<00:04:27.479> important<00:04:28.020> and<00:04:28.919> how 00:04:29.090 --> 00:04:29.100 align:start position:0% people why privacy is important and how 00:04:29.100 --> 00:04:30.350 align:start position:0% people why privacy is important and how we<00:04:29.280> can<00:04:29.400> build<00:04:29.520> privacy<00:04:29.940> focused 00:04:30.350 --> 00:04:30.360 align:start position:0% we can build privacy focused 00:04:30.360 --> 00:04:32.030 align:start position:0% we can build privacy focused applications<00:04:30.780> are<00:04:31.320> very<00:04:31.560> valuable 00:04:32.030 --> 00:04:32.040 align:start position:0% applications are very valuable 00:04:32.040 --> 00:04:33.170 align:start position:0% applications are very valuable challenges 00:04:33.170 --> 00:04:33.180 align:start position:0% challenges 00:04:33.180 --> 00:04:34.610 align:start position:0% challenges it<00:04:33.540> is<00:04:33.660> important<00:04:33.960> to<00:04:34.139> choose<00:04:34.320> the<00:04:34.500> right 00:04:34.610 --> 00:04:34.620 align:start position:0% it is important to choose the right 00:04:34.620 --> 00:04:37.969 align:start position:0% it is important to choose the right words<00:04:34.919> build<00:04:35.820> effective<00:04:36.419> designs<00:04:36.960> and<00:04:37.620> convey 00:04:37.969 --> 00:04:37.979 align:start position:0% words build effective designs and convey 00:04:37.979 --> 00:04:40.490 align:start position:0% words build effective designs and convey information<00:04:38.220> as<00:04:38.820> simply<00:04:39.180> as<00:04:39.540> possible 00:04:40.490 --> 00:04:40.500 align:start position:0% information as simply as possible 00:04:40.500 --> 00:04:43.790 align:start position:0% information as simply as possible however<00:04:41.220> simplify<00:04:41.880> things<00:04:42.060> is<00:04:42.360> not<00:04:42.540> enough 00:04:43.790 --> 00:04:43.800 align:start position:0% however simplify things is not enough 00:04:43.800 --> 00:04:46.550 align:start position:0% however simplify things is not enough making<00:04:44.280> people<00:04:44.580> aware<00:04:45.060> of<00:04:45.300> the<00:04:46.020> technological 00:04:46.550 --> 00:04:46.560 align:start position:0% making people aware of the technological 00:04:46.560 --> 00:04:48.830 align:start position:0% making people aware of the technological and<00:04:46.979> social<00:04:47.160> complexity<00:04:47.880> of<00:04:48.300> the<00:04:48.540> work<00:04:48.660> we 00:04:48.830 --> 00:04:48.840 align:start position:0% and social complexity of the work we 00:04:48.840 --> 00:04:51.950 align:start position:0% and social complexity of the work we live<00:04:49.020> in<00:04:49.259> is<00:04:49.800> equally<00:04:50.160> important<00:04:50.580> because<00:04:51.479> we 00:04:51.950 --> 00:04:51.960 align:start position:0% live in is equally important because we 00:04:51.960 --> 00:04:53.450 align:start position:0% live in is equally important because we don't<00:04:52.080> just<00:04:52.320> want<00:04:52.500> users<00:04:52.919> to<00:04:53.040> enjoy<00:04:53.220> an 00:04:53.450 --> 00:04:53.460 align:start position:0% don't just want users to enjoy an 00:04:53.460 --> 00:04:55.430 align:start position:0% don't just want users to enjoy an experience<00:04:53.820> we<00:04:54.240> want<00:04:54.419> new<00:04:54.720> friends<00:04:54.900> helping 00:04:55.430 --> 00:04:55.440 align:start position:0% experience we want new friends helping 00:04:55.440 --> 00:04:58.430 align:start position:0% experience we want new friends helping us<00:04:55.620> build<00:04:55.979> a<00:04:56.400> new<00:04:56.520> web<00:04:56.759> free<00:04:57.479> so<00:04:57.960> the<00:04:58.139> fear 00:04:58.430 --> 00:04:58.440 align:start position:0% us build a new web free so the fear 00:04:58.440 --> 00:05:00.890 align:start position:0% us build a new web free so the fear point<00:04:58.620> is<00:04:59.220> the<00:04:59.400> developer<00:04:59.820> experience 00:05:00.890 --> 00:05:00.900 align:start position:0% point is the developer experience 00:05:00.900 --> 00:05:02.689 align:start position:0% point is the developer experience the<00:05:01.440> growth<00:05:01.680> of<00:05:01.800> our<00:05:01.979> community<00:05:02.160> and<00:05:02.580> the 00:05:02.689 --> 00:05:02.699 align:start position:0% the growth of our community and the 00:05:02.699 --> 00:05:04.129 align:start position:0% the growth of our community and the adoption<00:05:03.060> of<00:05:03.240> our<00:05:03.360> technology<00:05:03.660> depend 00:05:04.129 --> 00:05:04.139 align:start position:0% adoption of our technology depend 00:05:04.139 --> 00:05:06.650 align:start position:0% adoption of our technology depend heavily<00:05:04.500> on<00:05:04.740> how<00:05:05.100> clear<00:05:05.220> the<00:05:05.520> goals<00:05:05.880> are<00:05:06.060> and 00:05:06.650 --> 00:05:06.660 align:start position:0% heavily on how clear the goals are and 00:05:06.660 --> 00:05:08.930 align:start position:0% heavily on how clear the goals are and how<00:05:06.960> easily<00:05:07.440> the<00:05:07.740> main<00:05:07.979> values<00:05:08.340> and<00:05:08.520> Concepts 00:05:08.930 --> 00:05:08.940 align:start position:0% how easily the main values and Concepts 00:05:08.940 --> 00:05:11.570 align:start position:0% how easily the main values and Concepts can<00:05:09.120> be<00:05:09.240> conveyed<00:05:10.080> however<00:05:10.740> another 00:05:11.570 --> 00:05:11.580 align:start position:0% can be conveyed however another 00:05:11.580 --> 00:05:13.370 align:start position:0% can be conveyed however another extremely<00:05:12.180> important<00:05:12.540> aspect<00:05:12.900> is<00:05:13.139> the 00:05:13.370 --> 00:05:13.380 align:start position:0% extremely important aspect is the 00:05:13.380 --> 00:05:15.230 align:start position:0% extremely important aspect is the quality<00:05:13.740> of<00:05:13.919> the<00:05:14.100> code 00:05:15.230 --> 00:05:15.240 align:start position:0% quality of the code 00:05:15.240 --> 00:05:18.010 align:start position:0% quality of the code the<00:05:15.660> call<00:05:15.840> should<00:05:16.080> be<00:05:16.259> tested<00:05:16.940> documented 00:05:18.010 --> 00:05:18.020 align:start position:0% the call should be tested documented 00:05:18.020 --> 00:05:21.590 align:start position:0% the call should be tested documented formatted<00:05:19.020> with<00:05:19.860> Atmos<00:05:20.400> care<00:05:20.639> it<00:05:21.479> is 00:05:21.590 --> 00:05:21.600 align:start position:0% formatted with Atmos care it is 00:05:21.600 --> 00:05:23.450 align:start position:0% formatted with Atmos care it is extremely<00:05:22.020> important<00:05:22.500> to<00:05:22.919> use<00:05:23.039> the<00:05:23.340> right 00:05:23.450 --> 00:05:23.460 align:start position:0% extremely important to use the right 00:05:23.460 --> 00:05:25.670 align:start position:0% extremely important to use the right partners<00:05:24.060> and<00:05:24.900> to<00:05:25.080> follow<00:05:25.259> the<00:05:25.500> best 00:05:25.670 --> 00:05:25.680 align:start position:0% partners and to follow the best 00:05:25.680 --> 00:05:28.850 align:start position:0% partners and to follow the best practices<00:05:26.039> like<00:05:26.580> dry<00:05:26.940> and<00:05:27.720> kiss<00:05:27.960> so 00:05:28.850 --> 00:05:28.860 align:start position:0% practices like dry and kiss so 00:05:28.860 --> 00:05:30.830 align:start position:0% practices like dry and kiss so developers<00:05:29.699> need<00:05:29.880> to<00:05:30.000> be<00:05:30.120> able<00:05:30.300> to<00:05:30.419> rely<00:05:30.720> on 00:05:30.830 --> 00:05:30.840 align:start position:0% developers need to be able to rely on 00:05:30.840 --> 00:05:33.110 align:start position:0% developers need to be able to rely on robust<00:05:31.320> easy<00:05:31.860> to<00:05:32.100> use<00:05:32.220> tools<00:05:32.639> that<00:05:32.820> allow 00:05:33.110 --> 00:05:33.120 align:start position:0% robust easy to use tools that allow 00:05:33.120 --> 00:05:34.850 align:start position:0% robust easy to use tools that allow applications<00:05:33.479> to<00:05:33.780> be<00:05:33.900> built<00:05:34.259> in<00:05:34.320> a<00:05:34.500> short<00:05:34.620> time 00:05:34.850 --> 00:05:34.860 align:start position:0% applications to be built in a short time 00:05:34.860 --> 00:05:37.810 align:start position:0% applications to be built in a short time while<00:05:35.639> also<00:05:36.120> allowing<00:05:36.419> them<00:05:36.660> to<00:05:36.900> be<00:05:37.199> extended 00:05:37.810 --> 00:05:37.820 align:start position:0% while also allowing them to be extended 00:05:37.820 --> 00:05:41.150 align:start position:0% while also allowing them to be extended customized<00:05:38.820> and<00:05:39.240> adapted<00:05:39.720> for<00:05:40.080> the<00:05:40.740> specific 00:05:41.150 --> 00:05:41.160 align:start position:0% customized and adapted for the specific 00:05:41.160 --> 00:05:44.450 align:start position:0% customized and adapted for the specific uses<00:05:42.000> so<00:05:42.860> developer<00:05:43.860> experience<00:05:44.280> and 00:05:44.450 --> 00:05:44.460 align:start position:0% uses so developer experience and 00:05:44.460 --> 00:05:47.210 align:start position:0% uses so developer experience and education<00:05:44.940> is<00:05:45.660> what<00:05:45.960> we<00:05:46.139> have<00:05:46.320> focused<00:05:46.740> on<00:05:46.860> in 00:05:47.210 --> 00:05:47.220 align:start position:0% education is what we have focused on in 00:05:47.220 --> 00:05:49.550 align:start position:0% education is what we have focused on in the<00:05:47.340> last<00:05:47.520> few<00:05:48.000> months<00:05:48.300> of<00:05:48.539> work<00:05:48.720> is<00:05:49.080> some<00:05:49.320> of 00:05:49.550 --> 00:05:49.560 align:start position:0% the last few months of work is some of 00:05:49.560 --> 00:05:51.590 align:start position:0% the last few months of work is some of her<00:05:50.039> but<00:05:50.520> many<00:05:50.699> of<00:05:50.880> you<00:05:50.940> may<00:05:51.120> be<00:05:51.240> wondering 00:05:51.590 --> 00:05:51.600 align:start position:0% her but many of you may be wondering 00:05:51.600 --> 00:05:54.050 align:start position:0% her but many of you may be wondering summer<00:05:52.080> for<00:05:52.380> his<00:05:52.580> semaphore<00:05:53.580> is<00:05:53.699> a<00:05:53.820> zero 00:05:54.050 --> 00:05:54.060 align:start position:0% summer for his semaphore is a zero 00:05:54.060 --> 00:05:55.850 align:start position:0% summer for his semaphore is a zero knowledge<00:05:54.240> protocol<00:05:54.660> that<00:05:54.960> allow<00:05:55.259> people<00:05:55.440> to 00:05:55.850 --> 00:05:55.860 align:start position:0% knowledge protocol that allow people to 00:05:55.860 --> 00:05:59.629 align:start position:0% knowledge protocol that allow people to join<00:05:56.699> a<00:05:56.820> group<00:05:57.000> and<00:05:57.900> then<00:05:58.139> to<00:05:58.560> send<00:05:59.100> signals 00:05:59.629 --> 00:05:59.639 align:start position:0% join a group and then to send signals 00:05:59.639 --> 00:06:02.029 align:start position:0% join a group and then to send signals such<00:05:59.759> as<00:05:59.940> messages<00:06:00.259> endorsements<00:06:01.259> or<00:06:01.500> votes 00:06:02.029 --> 00:06:02.039 align:start position:0% such as messages endorsements or votes 00:06:02.039 --> 00:06:04.969 align:start position:0% such as messages endorsements or votes without<00:06:02.580> revealing<00:06:03.180> the<00:06:03.300> original<00:06:03.479> identity 00:06:04.969 --> 00:06:04.979 align:start position:0% without revealing the original identity 00:06:04.979 --> 00:06:07.070 align:start position:0% without revealing the original identity in<00:06:05.340> addition<00:06:05.580> it<00:06:06.000> also<00:06:06.240> provides<00:06:06.539> a<00:06:06.720> mechanism 00:06:07.070 --> 00:06:07.080 align:start position:0% in addition it also provides a mechanism 00:06:07.080 --> 00:06:09.230 align:start position:0% in addition it also provides a mechanism to<00:06:07.259> prevent<00:06:07.560> double<00:06:07.800> signaling<00:06:08.460> which 00:06:09.230 --> 00:06:09.240 align:start position:0% to prevent double signaling which 00:06:09.240 --> 00:06:10.670 align:start position:0% to prevent double signaling which basically<00:06:09.539> means<00:06:09.840> you<00:06:09.960> cannot<00:06:10.259> create<00:06:10.440> the 00:06:10.670 --> 00:06:10.680 align:start position:0% basically means you cannot create the 00:06:10.680 --> 00:06:13.730 align:start position:0% basically means you cannot create the same<00:06:10.800> proof<00:06:11.100> twice<00:06:11.460> or<00:06:12.300> the<00:06:12.660> proof<00:06:13.020> cannot<00:06:13.620> be 00:06:13.730 --> 00:06:13.740 align:start position:0% same proof twice or the proof cannot be 00:06:13.740 --> 00:06:17.029 align:start position:0% same proof twice or the proof cannot be verified<00:06:14.100> so<00:06:15.000> what<00:06:15.539> makes<00:06:15.720> them<00:06:15.900> a<00:06:16.139> powerful 00:06:17.029 --> 00:06:17.039 align:start position:0% verified so what makes them a powerful 00:06:17.039 --> 00:06:18.950 align:start position:0% verified so what makes them a powerful tool<00:06:17.340> is<00:06:17.520> the<00:06:17.639> Simplicity<00:06:18.180> of<00:06:18.419> the<00:06:18.600> protocol 00:06:18.950 --> 00:06:18.960 align:start position:0% tool is the Simplicity of the protocol 00:06:18.960 --> 00:06:21.050 align:start position:0% tool is the Simplicity of the protocol and<00:06:19.800> the<00:06:19.979> flexibility 00:06:21.050 --> 00:06:21.060 align:start position:0% and the flexibility 00:06:21.060 --> 00:06:22.610 align:start position:0% and the flexibility it<00:06:21.539> can<00:06:21.720> be<00:06:21.840> used<00:06:22.020> to<00:06:22.259> build<00:06:22.380> many 00:06:22.610 --> 00:06:22.620 align:start position:0% it can be used to build many 00:06:22.620 --> 00:06:24.770 align:start position:0% it can be used to build many applications<00:06:23.100> like<00:06:23.880> private<00:06:24.360> voting 00:06:24.770 --> 00:06:24.780 align:start position:0% applications like private voting 00:06:24.780 --> 00:06:26.629 align:start position:0% applications like private voting applications<00:06:25.280> whistle<00:06:26.280> borrower 00:06:26.629 --> 00:06:26.639 align:start position:0% applications whistle borrower 00:06:26.639 --> 00:06:29.090 align:start position:0% applications whistle borrower applications<00:06:27.180> or<00:06:27.720> the<00:06:27.960> knowledge<00:06:28.319> dials 00:06:29.090 --> 00:06:29.100 align:start position:0% applications or the knowledge dials 00:06:29.100 --> 00:06:31.610 align:start position:0% applications or the knowledge dials semaphore<00:06:29.759> is<00:06:29.940> made<00:06:30.120> of<00:06:30.360> three<00:06:30.960> different 00:06:31.610 --> 00:06:31.620 align:start position:0% semaphore is made of three different 00:06:31.620 --> 00:06:34.129 align:start position:0% semaphore is made of three different parts<00:06:31.979> vehicle<00:06:32.940> circuits<00:06:33.539> solidity 00:06:34.129 --> 00:06:34.139 align:start position:0% parts vehicle circuits solidity 00:06:34.139 --> 00:06:36.590 align:start position:0% parts vehicle circuits solidity contracts<00:06:34.620> and<00:06:34.800> JavaScript<00:06:35.220> libraries<00:06:35.759> my 00:06:36.590 --> 00:06:36.600 align:start position:0% contracts and JavaScript libraries my 00:06:36.600 --> 00:06:39.110 align:start position:0% contracts and JavaScript libraries my work<00:06:36.840> has<00:06:37.380> focused<00:06:37.919> more 00:06:39.110 --> 00:06:39.120 align:start position:0% work has focused more 00:06:39.120 --> 00:06:41.270 align:start position:0% work has focused more JavaScript<00:06:39.720> JavaScript<00:06:40.380> libraries<00:06:40.979> and 00:06:41.270 --> 00:06:41.280 align:start position:0% JavaScript JavaScript libraries and 00:06:41.280 --> 00:06:43.249 align:start position:0% JavaScript JavaScript libraries and solidity<00:06:41.699> contracts<00:06:42.300> so<00:06:42.600> I<00:06:42.840> would<00:06:42.960> like<00:06:43.139> to 00:06:43.249 --> 00:06:43.259 align:start position:0% solidity contracts so I would like to 00:06:43.259 --> 00:06:45.110 align:start position:0% solidity contracts so I would like to show<00:06:43.500> you<00:06:43.680> the<00:06:43.979> main<00:06:44.100> sum<00:06:44.400> of<00:06:44.520> our<00:06:44.699> Concepts 00:06:45.110 --> 00:06:45.120 align:start position:0% show you the main sum of our Concepts 00:06:45.120 --> 00:06:47.150 align:start position:0% show you the main sum of our Concepts and<00:06:45.419> how<00:06:45.660> our<00:06:45.900> libraries<00:06:46.380> and<00:06:46.620> contracts 00:06:47.150 --> 00:06:47.160 align:start position:0% and how our libraries and contracts 00:06:47.160 --> 00:06:48.950 align:start position:0% and how our libraries and contracts works<00:06:47.699> and<00:06:47.819> how<00:06:48.060> they<00:06:48.300> can<00:06:48.419> be<00:06:48.539> used<00:06:48.660> to<00:06:48.840> build 00:06:48.950 --> 00:06:48.960 align:start position:0% works and how they can be used to build 00:06:48.960 --> 00:06:50.330 align:start position:0% works and how they can be used to build private<00:06:49.319> applications 00:06:50.330 --> 00:06:50.340 align:start position:0% private applications 00:06:50.340 --> 00:06:52.850 align:start position:0% private applications so<00:06:51.060> creating<00:06:51.479> a<00:06:51.600> consumer<00:06:52.020> for<00:06:52.139> identity<00:06:52.620> is 00:06:52.850 --> 00:06:52.860 align:start position:0% so creating a consumer for identity is 00:06:52.860 --> 00:06:54.529 align:start position:0% so creating a consumer for identity is the<00:06:53.100> first<00:06:53.280> step<00:06:53.520> to<00:06:53.819> interact<00:06:54.120> with<00:06:54.419> the 00:06:54.529 --> 00:06:54.539 align:start position:0% the first step to interact with the 00:06:54.539 --> 00:06:57.290 align:start position:0% the first step to interact with the protocol<00:06:55.319> each<00:06:55.919> identity<00:06:56.400> is<00:06:56.580> made<00:06:56.759> up<00:06:56.880> of<00:06:57.060> two 00:06:57.290 --> 00:06:57.300 align:start position:0% protocol each identity is made up of two 00:06:57.300 --> 00:06:58.629 align:start position:0% protocol each identity is made up of two secret<00:06:57.479> values 00:06:58.629 --> 00:06:58.639 align:start position:0% secret values 00:06:58.639 --> 00:07:01.430 align:start position:0% secret values trapdoor<00:06:59.639> and<00:06:59.819> nullifier<00:07:00.419> and<00:07:00.900> one<00:07:01.139> public 00:07:01.430 --> 00:07:01.440 align:start position:0% trapdoor and nullifier and one public 00:07:01.440 --> 00:07:04.370 align:start position:0% trapdoor and nullifier and one public value<00:07:01.800> commitment<00:07:02.639> so<00:07:03.300> the<00:07:03.600> positive<00:07:03.900> hash<00:07:04.199> of 00:07:04.370 --> 00:07:04.380 align:start position:0% value commitment so the positive hash of 00:07:04.380 --> 00:07:06.469 align:start position:0% value commitment so the positive hash of the<00:07:04.500> identity<00:07:04.740> nullifier<00:07:05.340> and<00:07:05.580> tractor<00:07:06.060> is 00:07:06.469 --> 00:07:06.479 align:start position:0% the identity nullifier and tractor is 00:07:06.479 --> 00:07:08.870 align:start position:0% the identity nullifier and tractor is called<00:07:06.660> the<00:07:06.840> identity<00:07:07.199> secret<00:07:07.500> and<00:07:08.460> the<00:07:08.699> ash 00:07:08.870 --> 00:07:08.880 align:start position:0% called the identity secret and the ash 00:07:08.880 --> 00:07:11.330 align:start position:0% called the identity secret and the ash of<00:07:09.660> the<00:07:09.900> identity<00:07:10.199> secret<00:07:10.500> is<00:07:10.800> the<00:07:10.979> identity 00:07:11.330 --> 00:07:11.340 align:start position:0% of the identity secret is the identity 00:07:11.340 --> 00:07:14.330 align:start position:0% of the identity secret is the identity commitment<00:07:11.819> so<00:07:12.600> although<00:07:13.500> in<00:07:13.860> this<00:07:13.919> case<00:07:14.100> we 00:07:14.330 --> 00:07:14.340 align:start position:0% commitment so although in this case we 00:07:14.340 --> 00:07:17.570 align:start position:0% commitment so although in this case we are<00:07:14.520> not<00:07:14.759> using<00:07:15.240> asymmetric<00:07:15.900> encryption<00:07:16.580> an 00:07:17.570 --> 00:07:17.580 align:start position:0% are not using asymmetric encryption an 00:07:17.580 --> 00:07:19.969 align:start position:0% are not using asymmetric encryption an identity<00:07:17.940> commitment<00:07:18.539> can<00:07:19.380> be<00:07:19.560> considered 00:07:19.969 --> 00:07:19.979 align:start position:0% identity commitment can be considered 00:07:19.979 --> 00:07:21.950 align:start position:0% identity commitment can be considered something<00:07:20.340> like<00:07:20.580> an<00:07:20.759> ethereum<00:07:21.180> address 00:07:21.950 --> 00:07:21.960 align:start position:0% something like an ethereum address 00:07:21.960 --> 00:07:24.350 align:start position:0% something like an ethereum address it<00:07:22.380> is<00:07:22.500> a<00:07:22.680> public<00:07:22.860> value<00:07:23.160> used<00:07:23.639> to<00:07:24.000> represent 00:07:24.350 --> 00:07:24.360 align:start position:0% it is a public value used to represent 00:07:24.360 --> 00:07:26.930 align:start position:0% it is a public value used to represent people<00:07:24.660> in<00:07:24.960> the<00:07:25.080> protocol<00:07:25.400> and<00:07:26.400> in<00:07:26.639> particular 00:07:26.930 --> 00:07:26.940 align:start position:0% people in the protocol and in particular 00:07:26.940 --> 00:07:28.909 align:start position:0% people in the protocol and in particular commitments<00:07:27.780> are<00:07:28.080> used<00:07:28.259> in<00:07:28.440> some<00:07:28.560> of<00:07:28.740> our 00:07:28.909 --> 00:07:28.919 align:start position:0% commitments are used in some of our 00:07:28.919 --> 00:07:31.189 align:start position:0% commitments are used in some of our groups<00:07:29.220> to<00:07:29.699> represent<00:07:30.060> the<00:07:30.360> identity<00:07:30.599> of<00:07:31.020> a 00:07:31.189 --> 00:07:31.199 align:start position:0% groups to represent the identity of a 00:07:31.199 --> 00:07:33.350 align:start position:0% groups to represent the identity of a group<00:07:31.380> member<00:07:31.800> the<00:07:32.400> secret<00:07:32.580> values<00:07:33.060> are<00:07:33.240> like 00:07:33.350 --> 00:07:33.360 align:start position:0% group member the secret values are like 00:07:33.360 --> 00:07:35.570 align:start position:0% group member the secret values are like ethereum<00:07:33.840> private<00:07:34.139> keys<00:07:34.440> and<00:07:35.099> they<00:07:35.280> are<00:07:35.460> used 00:07:35.570 --> 00:07:35.580 align:start position:0% ethereum private keys and they are used 00:07:35.580 --> 00:07:37.730 align:start position:0% ethereum private keys and they are used to<00:07:35.819> generate<00:07:36.120> semaphore<00:07:36.720> zero<00:07:37.080> logic<00:07:37.380> proofs 00:07:37.730 --> 00:07:37.740 align:start position:0% to generate semaphore zero logic proofs 00:07:37.740 --> 00:07:39.830 align:start position:0% to generate semaphore zero logic proofs and<00:07:37.919> authenticate<00:07:38.639> signals 00:07:39.830 --> 00:07:39.840 align:start position:0% and authenticate signals 00:07:39.840 --> 00:07:41.870 align:start position:0% and authenticate signals some<00:07:40.319> of<00:07:40.500> our<00:07:40.620> identities<00:07:41.039> can<00:07:41.340> be<00:07:41.520> generated 00:07:41.870 --> 00:07:41.880 align:start position:0% some of our identities can be generated 00:07:41.880 --> 00:07:43.909 align:start position:0% some of our identities can be generated off<00:07:42.180> chain<00:07:42.419> with<00:07:42.840> our<00:07:43.020> JavaScript<00:07:43.560> library 00:07:43.909 --> 00:07:43.919 align:start position:0% off chain with our JavaScript library 00:07:43.919 --> 00:07:45.710 align:start position:0% off chain with our JavaScript library and 00:07:45.710 --> 00:07:45.720 align:start position:0% and 00:07:45.720 --> 00:07:48.050 align:start position:0% and quite<00:07:46.319> simple<00:07:46.500> and<00:07:46.919> you<00:07:47.099> can<00:07:47.220> generate<00:07:47.699> it<00:07:47.880> in 00:07:48.050 --> 00:07:48.060 align:start position:0% quite simple and you can generate it in 00:07:48.060 --> 00:07:51.050 align:start position:0% quite simple and you can generate it in two<00:07:48.240> ways<00:07:48.599> randomly<00:07:49.440> or<00:07:49.620> deterministically 00:07:51.050 --> 00:07:51.060 align:start position:0% two ways randomly or deterministically 00:07:51.060 --> 00:07:52.850 align:start position:0% two ways randomly or deterministically you<00:07:51.479> can<00:07:51.599> generate<00:07:51.960> a<00:07:52.080> random<00:07:52.380> identity 00:07:52.850 --> 00:07:52.860 align:start position:0% you can generate a random identity 00:07:52.860 --> 00:07:55.490 align:start position:0% you can generate a random identity without<00:07:53.400> passing<00:07:53.880> any<00:07:54.060> parameters<00:07:54.599> and<00:07:55.199> a 00:07:55.490 --> 00:07:55.500 align:start position:0% without passing any parameters and a 00:07:55.500 --> 00:07:57.469 align:start position:0% without passing any parameters and a deterministic<00:07:56.160> identity<00:07:56.639> passing<00:07:57.240> a<00:07:57.360> secret 00:07:57.469 --> 00:07:57.479 align:start position:0% deterministic identity passing a secret 00:07:57.479 --> 00:07:58.430 align:start position:0% deterministic identity passing a secret message 00:07:58.430 --> 00:07:58.440 align:start position:0% message 00:07:58.440 --> 00:08:00.490 align:start position:0% message like<00:07:58.919> a<00:07:59.099> password<00:07:59.220> or<00:07:59.580> a<00:07:59.759> silent<00:08:00.120> message 00:08:00.490 --> 00:08:00.500 align:start position:0% like a password or a silent message 00:08:00.500 --> 00:08:03.409 align:start position:0% like a password or a silent message groups<00:08:01.500> are<00:08:01.979> an<00:08:02.160> important<00:08:02.520> concept<00:08:02.940> when<00:08:03.240> we 00:08:03.409 --> 00:08:03.419 align:start position:0% groups are an important concept when we 00:08:03.419 --> 00:08:05.330 align:start position:0% groups are an important concept when we speak<00:08:03.720> about<00:08:04.080> privacy<00:08:04.680> and<00:08:04.860> zero<00:08:05.160> knowledge 00:08:05.330 --> 00:08:05.340 align:start position:0% speak about privacy and zero knowledge 00:08:05.340 --> 00:08:06.469 align:start position:0% speak about privacy and zero knowledge Technologies 00:08:06.469 --> 00:08:06.479 align:start position:0% Technologies 00:08:06.479 --> 00:08:10.249 align:start position:0% Technologies they<00:08:07.020> can<00:08:07.199> be<00:08:07.380> fought<00:08:07.680> as<00:08:08.180> anonymity<00:08:09.180> sets<00:08:09.720> and 00:08:10.249 --> 00:08:10.259 align:start position:0% they can be fought as anonymity sets and 00:08:10.259 --> 00:08:12.170 align:start position:0% they can be fought as anonymity sets and they<00:08:10.440> are<00:08:10.560> a<00:08:10.740> way<00:08:10.860> to<00:08:10.979> establish<00:08:11.340> necessary 00:08:12.170 --> 00:08:12.180 align:start position:0% they are a way to establish necessary 00:08:12.180 --> 00:08:14.210 align:start position:0% they are a way to establish necessary trust<00:08:12.660> among<00:08:13.020> participants 00:08:14.210 --> 00:08:14.220 align:start position:0% trust among participants 00:08:14.220 --> 00:08:17.150 align:start position:0% trust among participants in<00:08:14.699> semaphora<00:08:15.300> group<00:08:15.479> can<00:08:15.780> be<00:08:16.020> people<00:08:16.860> who 00:08:17.150 --> 00:08:17.160 align:start position:0% in semaphora group can be people who 00:08:17.160 --> 00:08:18.950 align:start position:0% in semaphora group can be people who have<00:08:17.340> an<00:08:17.580> account<00:08:17.759> on<00:08:18.180> some<00:08:18.360> web<00:08:18.599> tube 00:08:18.950 --> 00:08:18.960 align:start position:0% have an account on some web tube 00:08:18.960 --> 00:08:21.890 align:start position:0% have an account on some web tube platforms<00:08:19.500> with<00:08:20.039> high<00:08:20.220> reputation<00:08:20.900> employees 00:08:21.890 --> 00:08:21.900 align:start position:0% platforms with high reputation employees 00:08:21.900 --> 00:08:24.650 align:start position:0% platforms with high reputation employees of<00:08:22.139> a<00:08:22.259> specific<00:08:22.560> company<00:08:23.300> voters<00:08:24.300> in<00:08:24.479> an 00:08:24.650 --> 00:08:24.660 align:start position:0% of a specific company voters in an 00:08:24.660 --> 00:08:26.990 align:start position:0% of a specific company voters in an election<00:08:24.840> or<00:08:25.319> people<00:08:25.560> with<00:08:25.860> specific<00:08:26.220> sbts<00:08:26.879> or 00:08:26.990 --> 00:08:27.000 align:start position:0% election or people with specific sbts or 00:08:27.000 --> 00:08:30.290 align:start position:0% election or people with specific sbts or nfts<00:08:27.960> essentially<00:08:28.500> any<00:08:28.860> set<00:08:29.099> of<00:08:29.300> individuals 00:08:30.290 --> 00:08:30.300 align:start position:0% nfts essentially any set of individuals 00:08:30.300 --> 00:08:32.149 align:start position:0% nfts essentially any set of individuals who<00:08:30.720> are<00:08:30.900> eligible<00:08:31.379> to<00:08:31.620> participate 00:08:32.149 --> 00:08:32.159 align:start position:0% who are eligible to participate 00:08:32.159 --> 00:08:33.829 align:start position:0% who are eligible to participate participate<00:08:32.940> in<00:08:33.060> something 00:08:33.829 --> 00:08:33.839 align:start position:0% participate in something 00:08:33.839 --> 00:08:37.130 align:start position:0% participate in something so<00:08:34.520> groups<00:08:35.520> can<00:08:35.700> can<00:08:36.120> use<00:08:36.360> several<00:08:36.779> types<00:08:37.080> of 00:08:37.130 --> 00:08:37.140 align:start position:0% so groups can can use several types of 00:08:37.140 --> 00:08:39.829 align:start position:0% so groups can can use several types of data<00:08:37.560> structures<00:08:37.919> but<00:08:38.820> Miracle<00:08:39.300> trees<00:08:39.599> are 00:08:39.829 --> 00:08:39.839 align:start position:0% data structures but Miracle trees are 00:08:39.839 --> 00:08:42.230 align:start position:0% data structures but Miracle trees are particularly<00:08:40.380> efficient<00:08:40.919> since<00:08:41.700> since<00:08:41.940> they 00:08:42.230 --> 00:08:42.240 align:start position:0% particularly efficient since since they 00:08:42.240 --> 00:08:43.969 align:start position:0% particularly efficient since since they can<00:08:42.419> prove<00:08:42.659> that<00:08:42.839> a<00:08:42.959> leaf<00:08:43.200> belongs<00:08:43.560> to<00:08:43.620> a<00:08:43.800> tree 00:08:43.969 --> 00:08:43.979 align:start position:0% can prove that a leaf belongs to a tree 00:08:43.979 --> 00:08:47.329 align:start position:0% can prove that a leaf belongs to a tree by<00:08:44.459> using<00:08:44.880> just<00:08:45.600> one<00:08:45.839> portion<00:08:46.260> of<00:08:46.440> that<00:08:46.560> tree 00:08:47.329 --> 00:08:47.339 align:start position:0% by using just one portion of that tree 00:08:47.339 --> 00:08:49.550 align:start position:0% by using just one portion of that tree so<00:08:47.760> some<00:08:48.000> of<00:08:48.120> our<00:08:48.240> uses<00:08:48.540> binary<00:08:48.839> medical<00:08:49.019> trees 00:08:49.550 --> 00:08:49.560 align:start position:0% so some of our uses binary medical trees 00:08:49.560 --> 00:08:51.050 align:start position:0% so some of our uses binary medical trees in<00:08:49.920> which<00:08:50.040> the<00:08:50.220> leaves<00:08:50.459> are<00:08:50.580> the<00:08:50.760> identity 00:08:51.050 --> 00:08:51.060 align:start position:0% in which the leaves are the identity 00:08:51.060 --> 00:08:53.449 align:start position:0% in which the leaves are the identity commitments<00:08:51.779> and<00:08:52.380> all<00:08:52.560> the<00:08:52.680> other<00:08:52.800> nodes<00:08:53.160> in 00:08:53.449 --> 00:08:53.459 align:start position:0% commitments and all the other nodes in 00:08:53.459 --> 00:08:56.210 align:start position:0% commitments and all the other nodes in the<00:08:53.580> three<00:08:53.700> hard<00:08:54.060> dashes<00:08:54.660> of<00:08:55.200> their<00:08:55.980> child 00:08:56.210 --> 00:08:56.220 align:start position:0% the three hard dashes of their child 00:08:56.220 --> 00:08:59.030 align:start position:0% the three hard dashes of their child nodes<00:08:56.580> when<00:08:57.300> a<00:08:57.480> user<00:08:57.720> join<00:08:57.959> a<00:08:58.140> group<00:08:58.260> their 00:08:59.030 --> 00:08:59.040 align:start position:0% nodes when a user join a group their 00:08:59.040 --> 00:09:01.610 align:start position:0% nodes when a user join a group their public<00:08:59.279> identity<00:08:59.820> is<00:09:00.420> added<00:09:00.779> to<00:09:00.899> that<00:09:01.140> group's 00:09:01.610 --> 00:09:01.620 align:start position:0% public identity is added to that group's 00:09:01.620 --> 00:09:03.829 align:start position:0% public identity is added to that group's Miracle<00:09:01.980> 3<00:09:02.160> which<00:09:02.820> is<00:09:03.000> therefore<00:09:03.360> used<00:09:03.600> to 00:09:03.829 --> 00:09:03.839 align:start position:0% Miracle 3 which is therefore used to 00:09:03.839 --> 00:09:05.449 align:start position:0% Miracle 3 which is therefore used to allow<00:09:04.140> users<00:09:04.440> to<00:09:04.680> generate<00:09:05.040> proof<00:09:05.399> of 00:09:05.449 --> 00:09:05.459 align:start position:0% allow users to generate proof of 00:09:05.459 --> 00:09:08.150 align:start position:0% allow users to generate proof of membership<00:09:06.360> and<00:09:06.779> then<00:09:06.959> send<00:09:07.560> anonymous 00:09:08.150 --> 00:09:08.160 align:start position:0% membership and then send anonymous 00:09:08.160 --> 00:09:11.750 align:start position:0% membership and then send anonymous signals<00:09:09.000> so<00:09:10.019> groups<00:09:10.800> can<00:09:10.980> be<00:09:11.160> created<00:09:11.459> off 00:09:11.750 --> 00:09:11.760 align:start position:0% signals so groups can be created off 00:09:11.760 --> 00:09:13.790 align:start position:0% signals so groups can be created off chain<00:09:12.060> with<00:09:12.300> our<00:09:12.420> JavaScript<00:09:12.899> library 00:09:13.790 --> 00:09:13.800 align:start position:0% chain with our JavaScript library 00:09:13.800 --> 00:09:16.310 align:start position:0% chain with our JavaScript library or<00:09:14.580> Unchained<00:09:15.180> without<00:09:15.240> with<00:09:15.660> our<00:09:15.779> semaphore 00:09:16.310 --> 00:09:16.320 align:start position:0% or Unchained without with our semaphore 00:09:16.320 --> 00:09:18.889 align:start position:0% or Unchained without with our semaphore Contours<00:09:16.860> when<00:09:17.220> a<00:09:17.399> group<00:09:17.580> is<00:09:17.820> very<00:09:18.060> large<00:09:18.300> and 00:09:18.889 --> 00:09:18.899 align:start position:0% Contours when a group is very large and 00:09:18.899 --> 00:09:20.990 align:start position:0% Contours when a group is very large and is<00:09:19.140> updated<00:09:19.500> very<00:09:19.800> frequently<00:09:20.279> and<00:09:20.580> of<00:09:20.820> chain 00:09:20.990 --> 00:09:21.000 align:start position:0% is updated very frequently and of chain 00:09:21.000 --> 00:09:23.329 align:start position:0% is updated very frequently and of chain group<00:09:21.240> might<00:09:21.720> be<00:09:21.959> a<00:09:22.019> valuable<00:09:22.440> alternative<00:09:23.040> or 00:09:23.329 --> 00:09:23.339 align:start position:0% group might be a valuable alternative or 00:09:23.339 --> 00:09:25.970 align:start position:0% group might be a valuable alternative or solution<00:09:23.760> this<00:09:24.360> solution<00:09:24.720> is<00:09:24.899> cheaper<00:09:25.380> faster 00:09:25.970 --> 00:09:25.980 align:start position:0% solution this solution is cheaper faster 00:09:25.980 --> 00:09:28.490 align:start position:0% solution this solution is cheaper faster but<00:09:26.339> tended<00:09:26.700> to<00:09:26.880> be<00:09:27.000> more<00:09:27.240> centralized<00:09:27.779> on<00:09:28.380> the 00:09:28.490 --> 00:09:28.500 align:start position:0% but tended to be more centralized on the 00:09:28.500 --> 00:09:30.889 align:start position:0% but tended to be more centralized on the other<00:09:28.560> hand<00:09:28.800> if<00:09:29.700> you<00:09:29.820> need<00:09:29.940> correct<00:09:30.360> execution 00:09:30.889 --> 00:09:30.899 align:start position:0% other hand if you need correct execution 00:09:30.899 --> 00:09:32.990 align:start position:0% other hand if you need correct execution or<00:09:31.140> sensitive<00:09:31.680> resistance<00:09:32.220> groups<00:09:32.640> can<00:09:32.820> also 00:09:32.990 --> 00:09:33.000 align:start position:0% or sensitive resistance groups can also 00:09:33.000 --> 00:09:34.610 align:start position:0% or sensitive resistance groups can also be<00:09:33.060> created<00:09:33.360> on<00:09:33.600> chain 00:09:34.610 --> 00:09:34.620 align:start position:0% be created on chain 00:09:34.620 --> 00:09:36.590 align:start position:0% be created on chain for<00:09:35.279> each<00:09:35.459> unchain<00:09:35.880> groups<00:09:36.180> there<00:09:36.360> is<00:09:36.480> an 00:09:36.590 --> 00:09:36.600 align:start position:0% for each unchain groups there is an 00:09:36.600 --> 00:09:40.009 align:start position:0% for each unchain groups there is an admin<00:09:36.959> which<00:09:37.920> can<00:09:38.100> be<00:09:38.220> an<00:09:38.279> ethereum<00:09:38.700> address<00:09:39.019> a 00:09:40.009 --> 00:09:40.019 align:start position:0% admin which can be an ethereum address a 00:09:40.019 --> 00:09:42.230 align:start position:0% admin which can be an ethereum address a smart<00:09:40.200> contract<00:09:40.680> or<00:09:40.920> a<00:09:41.040> modific<00:09:41.339> world<00:09:41.640> for 00:09:42.230 --> 00:09:42.240 align:start position:0% smart contract or a modific world for 00:09:42.240 --> 00:09:44.389 align:start position:0% smart contract or a modific world for example<00:09:42.540> if<00:09:43.260> you<00:09:43.380> want<00:09:43.560> to<00:09:43.680> create<00:09:43.920> a<00:09:44.160> fully 00:09:44.389 --> 00:09:44.399 align:start position:0% example if you want to create a fully 00:09:44.399 --> 00:09:46.130 align:start position:0% example if you want to create a fully decentralized<00:09:44.880> on<00:09:45.120> chain<00:09:45.360> group<00:09:45.600> you<00:09:45.959> could 00:09:46.130 --> 00:09:46.140 align:start position:0% decentralized on chain group you could 00:09:46.140 --> 00:09:47.509 align:start position:0% decentralized on chain group you could create<00:09:46.380> a<00:09:46.620> group 00:09:47.509 --> 00:09:47.519 align:start position:0% create a group 00:09:47.519 --> 00:09:49.910 align:start position:0% create a group um<00:09:47.940> a<00:09:48.300> group<00:09:48.540> and<00:09:48.779> send<00:09:49.019> your<00:09:49.260> contract<00:09:49.680> as 00:09:49.910 --> 00:09:49.920 align:start position:0% um a group and send your contract as 00:09:49.920 --> 00:09:54.110 align:start position:0% um a group and send your contract as admin<00:09:50.519> or<00:09:51.360> your<00:09:51.540> E3<00:09:51.899> models<00:09:52.440> which<00:09:53.040> can<00:09:53.279> which 00:09:54.110 --> 00:09:54.120 align:start position:0% admin or your E3 models which can which 00:09:54.120 --> 00:09:56.570 align:start position:0% admin or your E3 models which can which called<00:09:54.300> used<00:09:54.660> to<00:09:55.320> allow<00:09:55.620> people<00:09:55.860> to<00:09:56.100> join<00:09:56.399> that 00:09:56.570 --> 00:09:56.580 align:start position:0% called used to allow people to join that 00:09:56.580 --> 00:09:59.690 align:start position:0% called used to allow people to join that group<00:09:56.880> only<00:09:57.240> if<00:09:57.540> they<00:09:57.720> own<00:09:58.019> specific<00:09:58.580> nfts<00:09:59.580> or 00:09:59.690 --> 00:09:59.700 align:start position:0% group only if they own specific nfts or 00:09:59.700 --> 00:10:03.050 align:start position:0% group only if they own specific nfts or sbts<00:10:00.420> so<00:10:01.140> after<00:10:01.620> creating<00:10:02.100> the<00:10:02.339> identity<00:10:02.760> and 00:10:03.050 --> 00:10:03.060 align:start position:0% sbts so after creating the identity and 00:10:03.060 --> 00:10:05.030 align:start position:0% sbts so after creating the identity and joining<00:10:03.420> a<00:10:03.540> group<00:10:03.720> users<00:10:04.320> can<00:10:04.500> anonymously 00:10:05.030 --> 00:10:05.040 align:start position:0% joining a group users can anonymously 00:10:05.040 --> 00:10:06.590 align:start position:0% joining a group users can anonymously prove<00:10:05.399> that<00:10:05.519> they<00:10:05.700> are<00:10:05.880> members<00:10:06.240> of<00:10:06.360> that 00:10:06.590 --> 00:10:06.600 align:start position:0% prove that they are members of that 00:10:06.600 --> 00:10:07.670 align:start position:0% prove that they are members of that group 00:10:07.670 --> 00:10:07.680 align:start position:0% group 00:10:07.680 --> 00:10:09.590 align:start position:0% group and<00:10:08.220> send<00:10:08.399> signals 00:10:09.590 --> 00:10:09.600 align:start position:0% and send signals 00:10:09.600 --> 00:10:11.509 align:start position:0% and send signals such<00:10:10.019> as<00:10:10.140> voice<00:10:10.380> endorsements<00:10:11.100> or<00:10:11.279> any 00:10:11.509 --> 00:10:11.519 align:start position:0% such as voice endorsements or any 00:10:11.519 --> 00:10:12.889 align:start position:0% such as voice endorsements or any message 00:10:12.889 --> 00:10:12.899 align:start position:0% message 00:10:12.899 --> 00:10:14.690 align:start position:0% message signals<00:10:13.620> are<00:10:13.740> part<00:10:13.920> of<00:10:14.040> a<00:10:14.160> zero<00:10:14.459> knowledge 00:10:14.690 --> 00:10:14.700 align:start position:0% signals are part of a zero knowledge 00:10:14.700 --> 00:10:18.769 align:start position:0% signals are part of a zero knowledge proof<00:10:15.060> which<00:10:15.740> must<00:10:16.740> be<00:10:16.920> generated<00:10:17.279> by<00:10:17.580> users 00:10:18.769 --> 00:10:18.779 align:start position:0% proof which must be generated by users 00:10:18.779 --> 00:10:21.110 align:start position:0% proof which must be generated by users preferably<00:10:19.440> in<00:10:19.800> their<00:10:19.920> home<00:10:20.160> device<00:10:20.399> as<00:10:20.940> they 00:10:21.110 --> 00:10:21.120 align:start position:0% preferably in their home device as they 00:10:21.120 --> 00:10:23.030 align:start position:0% preferably in their home device as they need<00:10:21.300> to<00:10:21.420> use<00:10:21.540> their<00:10:21.839> private<00:10:22.200> identity<00:10:22.620> so 00:10:23.030 --> 00:10:23.040 align:start position:0% need to use their private identity so 00:10:23.040 --> 00:10:24.590 align:start position:0% need to use their private identity so secret<00:10:23.279> values 00:10:24.590 --> 00:10:24.600 align:start position:0% secret values 00:10:24.600 --> 00:10:27.530 align:start position:0% secret values and<00:10:25.580> it's<00:10:26.580> something<00:10:26.760> like<00:10:27.000> client-side 00:10:27.530 --> 00:10:27.540 align:start position:0% and it's something like client-side 00:10:27.540 --> 00:10:30.170 align:start position:0% and it's something like client-side encryption<00:10:28.080> in<00:10:28.860> this<00:10:28.980> case<00:10:29.100> and<00:10:29.640> it<00:10:29.820> allows 00:10:30.170 --> 00:10:30.180 align:start position:0% encryption in this case and it allows 00:10:30.180 --> 00:10:31.970 align:start position:0% encryption in this case and it allows proofs<00:10:30.660> to<00:10:30.720> be<00:10:30.839> generated<00:10:31.140> in<00:10:31.380> a<00:10:31.560> protected 00:10:31.970 --> 00:10:31.980 align:start position:0% proofs to be generated in a protected 00:10:31.980 --> 00:10:36.110 align:start position:0% proofs to be generated in a protected environment<00:10:32.480> locally<00:10:33.480> so<00:10:34.440> that<00:10:34.800> proof<00:10:35.220> can 00:10:36.110 --> 00:10:36.120 align:start position:0% environment locally so that proof can 00:10:36.120 --> 00:10:38.690 align:start position:0% environment locally so that proof can then<00:10:36.360> be<00:10:36.660> made<00:10:37.260> public<00:10:37.560> and<00:10:37.980> verified<00:10:38.339> by 00:10:38.690 --> 00:10:38.700 align:start position:0% then be made public and verified by 00:10:38.700 --> 00:10:41.210 align:start position:0% then be made public and verified by everyone<00:10:39.000> on<00:10:39.660> chain<00:10:39.959> or<00:10:40.200> off<00:10:40.320> chain<00:10:40.560> to 00:10:41.210 --> 00:10:41.220 align:start position:0% everyone on chain or off chain to 00:10:41.220 --> 00:10:43.430 align:start position:0% everyone on chain or off chain to generate<00:10:41.580> a<00:10:41.700> valid<00:10:42.060> proof<00:10:42.300> we<00:10:42.660> also<00:10:42.899> need<00:10:43.080> an 00:10:43.430 --> 00:10:43.440 align:start position:0% generate a valid proof we also need an 00:10:43.440 --> 00:10:46.190 align:start position:0% generate a valid proof we also need an external<00:10:43.860> amplifier<00:10:44.399> and<00:10:45.360> the<00:10:45.600> ash<00:10:45.779> of<00:10:46.079> this 00:10:46.190 --> 00:10:46.200 align:start position:0% external amplifier and the ash of this 00:10:46.200 --> 00:10:48.769 align:start position:0% external amplifier and the ash of this value<00:10:46.440> and<00:10:46.800> the<00:10:47.220> identity<00:10:47.880> nullifier<00:10:48.360> is<00:10:48.600> the 00:10:48.769 --> 00:10:48.779 align:start position:0% value and the identity nullifier is the 00:10:48.779 --> 00:10:51.410 align:start position:0% value and the identity nullifier is the nullifier<00:10:49.260> ash<00:10:50.040> which<00:10:50.519> can<00:10:50.700> be<00:10:50.820> used<00:10:50.940> to<00:10:51.120> avoid 00:10:51.410 --> 00:10:51.420 align:start position:0% nullifier ash which can be used to avoid 00:10:51.420 --> 00:10:53.810 align:start position:0% nullifier ash which can be used to avoid double<00:10:51.660> signaling<00:10:52.320> so<00:10:53.100> imagine<00:10:53.220> you<00:10:53.519> have<00:10:53.700> a 00:10:53.810 --> 00:10:53.820 align:start position:0% double signaling so imagine you have a 00:10:53.820 --> 00:10:55.069 align:start position:0% double signaling so imagine you have a group<00:10:53.940> you<00:10:54.120> are<00:10:54.240> using<00:10:54.480> to<00:10:54.600> vote<00:10:54.720> on<00:10:54.899> some 00:10:55.069 --> 00:10:55.079 align:start position:0% group you are using to vote on some 00:10:55.079 --> 00:10:56.210 align:start position:0% group you are using to vote on some proposals 00:10:56.210 --> 00:10:56.220 align:start position:0% proposals 00:10:56.220 --> 00:10:58.250 align:start position:0% proposals and<00:10:56.760> you<00:10:56.880> want<00:10:57.060> all<00:10:57.300> members<00:10:57.660> of<00:10:57.839> that<00:10:58.019> group 00:10:58.250 --> 00:10:58.260 align:start position:0% and you want all members of that group 00:10:58.260 --> 00:11:01.310 align:start position:0% and you want all members of that group to<00:10:58.500> vote<00:10:58.620> only<00:10:58.860> once<00:10:59.279> you<00:11:00.120> can<00:11:00.240> use<00:11:00.540> the<00:11:00.899> ID<00:11:01.079> of 00:11:01.310 --> 00:11:01.320 align:start position:0% to vote only once you can use the ID of 00:11:01.320 --> 00:11:03.949 align:start position:0% to vote only once you can use the ID of the<00:11:01.440> group<00:11:01.620> as<00:11:02.399> an<00:11:02.579> externalifier 00:11:03.949 --> 00:11:03.959 align:start position:0% the group as an externalifier 00:11:03.959 --> 00:11:06.470 align:start position:0% the group as an externalifier and<00:11:04.380> when<00:11:04.560> a<00:11:04.740> user<00:11:04.980> was<00:11:05.160> the<00:11:05.459> first<00:11:05.579> time 00:11:06.470 --> 00:11:06.480 align:start position:0% and when a user was the first time 00:11:06.480 --> 00:11:08.389 align:start position:0% and when a user was the first time you<00:11:06.959> can<00:11:07.079> save<00:11:07.200> the<00:11:07.500> ash<00:11:07.680> of<00:11:07.920> their<00:11:08.040> identity 00:11:08.389 --> 00:11:08.399 align:start position:0% you can save the ash of their identity 00:11:08.399 --> 00:11:11.389 align:start position:0% you can save the ash of their identity nullifier<00:11:08.940> and<00:11:09.120> your<00:11:09.240> PD<00:11:10.140> and<00:11:10.740> afterwards 00:11:11.389 --> 00:11:11.399 align:start position:0% nullifier and your PD and afterwards 00:11:11.399 --> 00:11:13.490 align:start position:0% nullifier and your PD and afterwards block<00:11:11.880> any<00:11:12.120> double<00:11:12.360> votes<00:11:12.779> by<00:11:13.079> checking<00:11:13.380> if 00:11:13.490 --> 00:11:13.500 align:start position:0% block any double votes by checking if 00:11:13.500 --> 00:11:15.710 align:start position:0% block any double votes by checking if that<00:11:13.740> Ash<00:11:13.920> already<00:11:14.220> exists<00:11:14.760> also<00:11:15.420> in<00:11:15.540> this 00:11:15.710 --> 00:11:15.720 align:start position:0% that Ash already exists also in this 00:11:15.720 --> 00:11:18.290 align:start position:0% that Ash already exists also in this case<00:11:15.839> we<00:11:16.079> have<00:11:16.200> a<00:11:16.440> JavaScript<00:11:16.800> library 00:11:18.290 --> 00:11:18.300 align:start position:0% case we have a JavaScript library 00:11:18.300 --> 00:11:20.810 align:start position:0% case we have a JavaScript library which<00:11:18.839> can<00:11:19.079> be<00:11:19.200> used<00:11:19.500> to<00:11:19.980> generate<00:11:20.399> proofs 00:11:20.810 --> 00:11:20.820 align:start position:0% which can be used to generate proofs 00:11:20.820 --> 00:11:23.050 align:start position:0% which can be used to generate proofs proofs<00:11:21.360> must<00:11:21.540> be<00:11:21.660> generated<00:11:22.019> of<00:11:22.260> chain 00:11:23.050 --> 00:11:23.060 align:start position:0% proofs must be generated of chain 00:11:23.060 --> 00:11:26.449 align:start position:0% proofs must be generated of chain and<00:11:24.060> those<00:11:25.019> proofs<00:11:25.440> can<00:11:25.560> be<00:11:25.680> verified<00:11:25.980> on 00:11:26.449 --> 00:11:26.459 align:start position:0% and those proofs can be verified on 00:11:26.459 --> 00:11:28.550 align:start position:0% and those proofs can be verified on chain<00:11:26.640> or<00:11:26.940> off<00:11:27.060> chain<00:11:27.300> off<00:11:28.019> chain<00:11:28.260> with<00:11:28.440> our 00:11:28.550 --> 00:11:28.560 align:start position:0% chain or off chain off chain with our 00:11:28.560 --> 00:11:30.470 align:start position:0% chain or off chain off chain with our JavaScript<00:11:28.980> library<00:11:29.339> the<00:11:29.700> same<00:11:29.880> library<00:11:30.120> and 00:11:30.470 --> 00:11:30.480 align:start position:0% JavaScript library the same library and 00:11:30.480 --> 00:11:32.990 align:start position:0% JavaScript library the same library and on<00:11:30.660> chain<00:11:30.899> with<00:11:31.140> our<00:11:31.320> smart<00:11:31.800> contract<00:11:32.279> also<00:11:32.940> in 00:11:32.990 --> 00:11:33.000 align:start position:0% on chain with our smart contract also in 00:11:33.000 --> 00:11:34.970 align:start position:0% on chain with our smart contract also in this<00:11:33.180> case<00:11:33.300> the<00:11:33.600> way<00:11:33.720> you<00:11:33.899> use<00:11:34.079> them<00:11:34.320> depends 00:11:34.970 --> 00:11:34.980 align:start position:0% this case the way you use them depends 00:11:34.980 --> 00:11:37.670 align:start position:0% this case the way you use them depends on<00:11:35.100> your<00:11:35.279> application<00:11:35.700> on<00:11:36.360> your<00:11:36.600> use<00:11:36.839> case 00:11:37.670 --> 00:11:37.680 align:start position:0% on your application on your use case 00:11:37.680 --> 00:11:40.310 align:start position:0% on your application on your use case so<00:11:38.040> verifying<00:11:38.640> kind<00:11:38.820> of<00:11:38.940> chain<00:11:39.120> proofs<00:11:39.720> allows 00:11:40.310 --> 00:11:40.320 align:start position:0% so verifying kind of chain proofs allows 00:11:40.320 --> 00:11:43.250 align:start position:0% so verifying kind of chain proofs allows the<00:11:40.440> verifier<00:11:40.980> your<00:11:41.640> server<00:11:42.000> or<00:11:42.240> you<00:11:42.480> to<00:11:43.140> be 00:11:43.250 --> 00:11:43.260 align:start position:0% the verifier your server or you to be 00:11:43.260 --> 00:11:45.590 align:start position:0% the verifier your server or you to be certain<00:11:43.440> of<00:11:43.740> the<00:11:43.860> validity<00:11:44.279> of<00:11:44.399> the<00:11:44.519> proof 00:11:45.590 --> 00:11:45.600 align:start position:0% certain of the validity of the proof 00:11:45.600 --> 00:11:48.290 align:start position:0% certain of the validity of the proof so<00:11:46.019> it's<00:11:46.140> more<00:11:46.380> centralized<00:11:46.920> and<00:11:47.640> verifying 00:11:48.290 --> 00:11:48.300 align:start position:0% so it's more centralized and verifying 00:11:48.300 --> 00:11:50.930 align:start position:0% so it's more centralized and verifying it<00:11:48.540> on<00:11:48.779> chain<00:11:49.500> on<00:11:49.980> the<00:11:50.160> other<00:11:50.279> end<00:11:50.399> allows 00:11:50.930 --> 00:11:50.940 align:start position:0% it on chain on the other end allows 00:11:50.940 --> 00:11:52.790 align:start position:0% it on chain on the other end allows everyone<00:11:51.120> to<00:11:51.720> consider<00:11:52.079> that<00:11:52.320> proof<00:11:52.680> value 00:11:52.790 --> 00:11:52.800 align:start position:0% everyone to consider that proof value 00:11:52.800 --> 00:11:55.910 align:start position:0% everyone to consider that proof value because<00:11:53.399> the<00:11:53.700> smart<00:11:54.060> contract<00:11:54.480> is<00:11:54.660> public<00:11:55.260> so 00:11:55.910 --> 00:11:55.920 align:start position:0% because the smart contract is public so 00:11:55.920 --> 00:11:58.550 align:start position:0% because the smart contract is public so semaphore<00:11:56.519> is<00:11:56.700> already<00:11:56.820> being<00:11:57.120> used<00:11:57.360> by<00:11:58.320> some 00:11:58.550 --> 00:11:58.560 align:start position:0% semaphore is already being used by some 00:11:58.560 --> 00:11:59.690 align:start position:0% semaphore is already being used by some projects 00:11:59.690 --> 00:11:59.700 align:start position:0% projects 00:11:59.700 --> 00:12:01.550 align:start position:0% projects like<00:12:00.120> unirap 00:12:01.550 --> 00:12:01.560 align:start position:0% like unirap 00:12:01.560 --> 00:12:03.829 align:start position:0% like unirap unirap<00:12:02.399> is<00:12:02.579> a<00:12:02.760> protocol<00:12:03.060> or<00:12:03.300> a<00:12:03.480> reputation 00:12:03.829 --> 00:12:03.839 align:start position:0% unirap is a protocol or a reputation 00:12:03.839 --> 00:12:06.170 align:start position:0% unirap is a protocol or a reputation system<00:12:04.140> built<00:12:04.680> on<00:12:04.740> top<00:12:04.920> of<00:12:05.040> semaphore<00:12:05.640> where 00:12:06.170 --> 00:12:06.180 align:start position:0% system built on top of semaphore where 00:12:06.180 --> 00:12:08.990 align:start position:0% system built on top of semaphore where users<00:12:06.660> can<00:12:06.839> anonymously<00:12:07.440> give<00:12:07.740> receive<00:12:08.399> and 00:12:08.990 --> 00:12:09.000 align:start position:0% users can anonymously give receive and 00:12:09.000 --> 00:12:10.730 align:start position:0% users can anonymously give receive and prove<00:12:09.360> reputation 00:12:10.730 --> 00:12:10.740 align:start position:0% prove reputation 00:12:10.740 --> 00:12:12.590 align:start position:0% prove reputation it<00:12:11.100> is<00:12:11.160> a<00:12:11.339> great<00:12:11.459> way<00:12:11.700> to<00:12:11.880> allow<00:12:12.120> people<00:12:12.360> to 00:12:12.590 --> 00:12:12.600 align:start position:0% it is a great way to allow people to 00:12:12.600 --> 00:12:14.990 align:start position:0% it is a great way to allow people to build<00:12:12.779> reputation<00:12:13.380> over<00:12:13.680> time 00:12:14.990 --> 00:12:15.000 align:start position:0% build reputation over time 00:12:15.000 --> 00:12:17.750 align:start position:0% build reputation over time while<00:12:15.480> giving<00:12:15.779> them<00:12:16.019> total<00:12:16.560> control<00:12:16.740> over<00:12:17.339> how 00:12:17.750 --> 00:12:17.760 align:start position:0% while giving them total control over how 00:12:17.760 --> 00:12:19.970 align:start position:0% while giving them total control over how much<00:12:17.880> they<00:12:18.060> reveal<00:12:18.420> about<00:12:18.540> themselves<00:12:19.079> in<00:12:19.860> a 00:12:19.970 --> 00:12:19.980 align:start position:0% much they reveal about themselves in a 00:12:19.980 --> 00:12:22.670 align:start position:0% much they reveal about themselves in a given<00:12:20.279> interaction<00:12:20.660> so<00:12:21.660> another<00:12:22.079> interesting 00:12:22.670 --> 00:12:22.680 align:start position:0% given interaction so another interesting 00:12:22.680 --> 00:12:24.710 align:start position:0% given interaction so another interesting project<00:12:22.980> is<00:12:23.459> the<00:12:23.700> guitar<00:12:23.940> which<00:12:24.480> is<00:12:24.660> an 00:12:24.710 --> 00:12:24.720 align:start position:0% project is the guitar which is an 00:12:24.720 --> 00:12:26.449 align:start position:0% project is the guitar which is an anonymous<00:12:25.019> social<00:12:25.440> network<00:12:25.740> where<00:12:26.100> people 00:12:26.449 --> 00:12:26.459 align:start position:0% anonymous social network where people 00:12:26.459 --> 00:12:29.930 align:start position:0% anonymous social network where people can<00:12:27.060> post<00:12:27.300> and<00:12:28.200> chat<00:12:28.620> without<00:12:29.279> using<00:12:29.820> their 00:12:29.930 --> 00:12:29.940 align:start position:0% can post and chat without using their 00:12:29.940 --> 00:12:32.569 align:start position:0% can post and chat without using their real<00:12:30.120> life<00:12:30.360> reputation<00:12:30.899> and 00:12:32.569 --> 00:12:32.579 align:start position:0% real life reputation and 00:12:32.579 --> 00:12:33.170 align:start position:0% real life reputation and um 00:12:33.170 --> 00:12:33.180 align:start position:0% um 00:12:33.180 --> 00:12:36.230 align:start position:0% um temporary<00:12:33.899> Anonymous<00:12:34.320> zone<00:12:34.740> is<00:12:35.459> like<00:12:35.880> an 00:12:36.230 --> 00:12:36.240 align:start position:0% temporary Anonymous zone is like an 00:12:36.240 --> 00:12:38.030 align:start position:0% temporary Anonymous zone is like an experiment 00:12:38.030 --> 00:12:38.040 align:start position:0% experiment 00:12:38.040 --> 00:12:40.970 align:start position:0% experiment we<00:12:38.519> have<00:12:38.640> a<00:12:38.760> booth<00:12:39.120> on<00:12:39.779> the<00:12:39.959> first<00:12:40.140> floor<00:12:40.440> you 00:12:40.970 --> 00:12:40.980 align:start position:0% we have a booth on the first floor you 00:12:40.980 --> 00:12:42.769 align:start position:0% we have a booth on the first floor you can<00:12:41.100> try<00:12:41.279> our<00:12:41.459> applications<00:12:41.940> and<00:12:42.360> there<00:12:42.540> is 00:12:42.769 --> 00:12:42.779 align:start position:0% can try our applications and there is 00:12:42.779 --> 00:12:45.170 align:start position:0% can try our applications and there is like<00:12:42.959> there<00:12:43.680> are<00:12:43.920> like<00:12:44.040> two<00:12:44.399> applications<00:12:44.820> you 00:12:45.170 --> 00:12:45.180 align:start position:0% like there are like two applications you 00:12:45.180 --> 00:12:46.870 align:start position:0% like there are like two applications you can<00:12:45.300> use<00:12:45.420> where<00:12:45.839> you<00:12:46.200> can 00:12:46.870 --> 00:12:46.880 align:start position:0% can use where you can 00:12:46.880 --> 00:12:49.310 align:start position:0% can use where you can answer<00:12:47.880> questions<00:12:48.420> and<00:12:48.839> ask<00:12:49.019> questions 00:12:49.310 --> 00:12:49.320 align:start position:0% answer questions and ask questions 00:12:49.320 --> 00:12:52.310 align:start position:0% answer questions and ask questions anonymously<00:12:50.160> with<00:12:51.060> one<00:12:51.240> application<00:12:51.720> and 00:12:52.310 --> 00:12:52.320 align:start position:0% anonymously with one application and 00:12:52.320 --> 00:12:54.650 align:start position:0% anonymously with one application and make<00:12:52.680> art<00:12:53.180> anonymously<00:12:54.180> with<00:12:54.420> the<00:12:54.540> other 00:12:54.650 --> 00:12:54.660 align:start position:0% make art anonymously with the other 00:12:54.660 --> 00:12:57.350 align:start position:0% make art anonymously with the other application<00:12:55.139> Collective<00:12:56.040> art<00:12:56.220> it's<00:12:56.940> like<00:12:57.120> an 00:12:57.350 --> 00:12:57.360 align:start position:0% application Collective art it's like an 00:12:57.360 --> 00:12:58.970 align:start position:0% application Collective art it's like an experiment<00:12:57.660> to<00:12:57.899> allow<00:12:58.139> people<00:12:58.320> to<00:12:58.560> learn<00:12:58.740> more 00:12:58.970 --> 00:12:58.980 align:start position:0% experiment to allow people to learn more 00:12:58.980 --> 00:13:00.889 align:start position:0% experiment to allow people to learn more about<00:12:59.160> our<00:12:59.399> Technologies<00:13:00.060> and<00:13:00.720> about 00:13:00.889 --> 00:13:00.899 align:start position:0% about our Technologies and about 00:13:00.899 --> 00:13:04.610 align:start position:0% about our Technologies and about semaphore<00:13:02.040> so<00:13:02.579> stem<00:13:02.940> of<00:13:03.180> 4<00:13:03.360> is<00:13:03.899> still<00:13:04.200> in<00:13:04.440> its 00:13:04.610 --> 00:13:04.620 align:start position:0% semaphore so stem of 4 is still in its 00:13:04.620 --> 00:13:07.550 align:start position:0% semaphore so stem of 4 is still in its early<00:13:04.740> stage<00:13:05.480> and<00:13:06.480> some<00:13:06.720> of<00:13:06.839> the<00:13:07.019> ideas<00:13:07.200> for 00:13:07.550 --> 00:13:07.560 align:start position:0% early stage and some of the ideas for 00:13:07.560 --> 00:13:09.530 align:start position:0% early stage and some of the ideas for improving<00:13:07.980> it<00:13:08.160> are<00:13:08.399> the<00:13:08.579> following 00:13:09.530 --> 00:13:09.540 align:start position:0% improving it are the following 00:13:09.540 --> 00:13:11.269 align:start position:0% improving it are the following create<00:13:10.019> an<00:13:10.260> infrastructure<00:13:10.860> to<00:13:10.980> manage 00:13:11.269 --> 00:13:11.279 align:start position:0% create an infrastructure to manage 00:13:11.279 --> 00:13:14.210 align:start position:0% create an infrastructure to manage groups<00:13:11.700> the<00:13:12.000> idea<00:13:12.180> is<00:13:12.480> to<00:13:12.839> have 00:13:14.210 --> 00:13:14.220 align:start position:0% groups the idea is to have 00:13:14.220 --> 00:13:16.850 align:start position:0% groups the idea is to have a<00:13:14.579> cloud<00:13:14.940> or<00:13:15.300> self-hosted<00:13:16.079> dashboard<00:13:16.500> where 00:13:16.850 --> 00:13:16.860 align:start position:0% a cloud or self-hosted dashboard where 00:13:16.860 --> 00:13:19.069 align:start position:0% a cloud or self-hosted dashboard where people<00:13:17.100> can<00:13:17.339> create<00:13:17.579> groups<00:13:18.180> add<00:13:18.660> members 00:13:19.069 --> 00:13:19.079 align:start position:0% people can create groups add members 00:13:19.079 --> 00:13:22.250 align:start position:0% people can create groups add members remove<00:13:19.320> members<00:13:19.860> or<00:13:20.100> update<00:13:20.639> members<00:13:21.260> and 00:13:22.250 --> 00:13:22.260 align:start position:0% remove members or update members and 00:13:22.260 --> 00:13:24.530 align:start position:0% remove members or update members and they<00:13:22.920> they<00:13:23.220> can<00:13:23.399> create<00:13:23.579> many<00:13:23.880> kind<00:13:24.120> of<00:13:24.240> groups 00:13:24.530 --> 00:13:24.540 align:start position:0% they they can create many kind of groups 00:13:24.540 --> 00:13:26.509 align:start position:0% they they can create many kind of groups like<00:13:24.779> permission<00:13:25.260> at<00:13:25.560> groups<00:13:25.980> or 00:13:26.509 --> 00:13:26.519 align:start position:0% like permission at groups or 00:13:26.519 --> 00:13:29.329 align:start position:0% like permission at groups or permissionless<00:13:27.200> decentralized<00:13:28.200> groups<00:13:28.680> and 00:13:29.329 --> 00:13:29.339 align:start position:0% permissionless decentralized groups and 00:13:29.339 --> 00:13:32.629 align:start position:0% permissionless decentralized groups and also<00:13:29.579> reputational<00:13:30.060> groups<00:13:30.540> similar<00:13:30.959> to<00:13:31.079> prep 00:13:32.629 --> 00:13:32.639 align:start position:0% also reputational groups similar to prep 00:13:32.639 --> 00:13:36.110 align:start position:0% also reputational groups similar to prep so<00:13:33.060> another<00:13:33.300> point<00:13:33.660> is<00:13:34.040> create<00:13:35.120> attestations 00:13:36.110 --> 00:13:36.120 align:start position:0% so another point is create attestations 00:13:36.120 --> 00:13:38.569 align:start position:0% so another point is create attestations contracts<00:13:36.720> for<00:13:36.839> decentralized<00:13:37.500> groups 00:13:38.569 --> 00:13:38.579 align:start position:0% contracts for decentralized groups 00:13:38.579 --> 00:13:41.990 align:start position:0% contracts for decentralized groups Lydia<00:13:39.300> here<00:13:39.540> is<00:13:39.839> quite<00:13:40.139> simple<00:13:40.320> uh<00:13:41.160> it<00:13:41.639> is<00:13:41.760> to 00:13:41.990 --> 00:13:42.000 align:start position:0% Lydia here is quite simple uh it is to 00:13:42.000 --> 00:13:44.269 align:start position:0% Lydia here is quite simple uh it is to create<00:13:42.380> on-chain<00:13:43.380> contracts<00:13:43.860> smart 00:13:44.269 --> 00:13:44.279 align:start position:0% create on-chain contracts smart 00:13:44.279 --> 00:13:46.850 align:start position:0% create on-chain contracts smart contracts<00:13:44.760> where<00:13:44.940> people<00:13:45.180> can<00:13:45.540> join<00:13:46.139> groups 00:13:46.850 --> 00:13:46.860 align:start position:0% contracts where people can join groups 00:13:46.860 --> 00:13:49.790 align:start position:0% contracts where people can join groups directly<00:13:47.339> without<00:13:48.000> any<00:13:48.360> external<00:13:48.839> approval 00:13:49.790 --> 00:13:49.800 align:start position:0% directly without any external approval 00:13:49.800 --> 00:13:52.190 align:start position:0% directly without any external approval based<00:13:50.519> on<00:13:50.579> Unchained<00:13:51.000> attributes<00:13:51.360> like<00:13:51.540> sbts 00:13:52.190 --> 00:13:52.200 align:start position:0% based on Unchained attributes like sbts 00:13:52.200 --> 00:13:55.430 align:start position:0% based on Unchained attributes like sbts or<00:13:52.320> nfts<00:13:52.920> or<00:13:53.459> just<00:13:53.760> the<00:13:54.000> amount<00:13:54.300> of<00:13:54.480> money<00:13:55.079> you 00:13:55.430 --> 00:13:55.440 align:start position:0% or nfts or just the amount of money you 00:13:55.440 --> 00:13:57.949 align:start position:0% or nfts or just the amount of money you have<00:13:55.980> we<00:13:56.519> will<00:13:56.700> investigate<00:13:57.300> our<00:13:57.540> zero 00:13:57.949 --> 00:13:57.959 align:start position:0% have we will investigate our zero 00:13:57.959 --> 00:13:58.910 align:start position:0% have we will investigate our zero knowledge<00:13:58.139> Technologies<00:13:58.560> and<00:13:58.740> public 00:13:58.910 --> 00:13:58.920 align:start position:0% knowledge Technologies and public 00:13:58.920 --> 00:14:01.550 align:start position:0% knowledge Technologies and public systems<00:13:59.579> of<00:13:59.820> course<00:14:00.000> and<00:14:00.959> we<00:14:01.200> will<00:14:01.380> continue 00:14:01.550 --> 00:14:01.560 align:start position:0% systems of course and we will continue 00:14:01.560 --> 00:14:03.590 align:start position:0% systems of course and we will continue improving<00:14:02.100> the<00:14:02.220> developer<00:14:02.700> experience<00:14:03.060> and 00:14:03.590 --> 00:14:03.600 align:start position:0% improving the developer experience and 00:14:03.600 --> 00:14:06.050 align:start position:0% improving the developer experience and our<00:14:03.779> documentation<00:14:04.440> website<00:14:05.040> the<00:14:05.459> idea<00:14:05.700> is<00:14:05.880> to 00:14:06.050 --> 00:14:06.060 align:start position:0% our documentation website the idea is to 00:14:06.060 --> 00:14:08.930 align:start position:0% our documentation website the idea is to create<00:14:06.240> like<00:14:06.660> an<00:14:07.079> educational<00:14:07.500> website 00:14:08.930 --> 00:14:08.940 align:start position:0% create like an educational website 00:14:08.940 --> 00:14:11.810 align:start position:0% create like an educational website and<00:14:09.540> last<00:14:09.779> but<00:14:09.959> not<00:14:10.139> least<00:14:10.380> we<00:14:11.100> want<00:14:11.459> to<00:14:11.639> create 00:14:11.810 --> 00:14:11.820 align:start position:0% and last but not least we want to create 00:14:11.820 --> 00:14:13.490 align:start position:0% and last but not least we want to create a<00:14:12.120> strong<00:14:12.300> community 00:14:13.490 --> 00:14:13.500 align:start position:0% a strong community 00:14:13.500 --> 00:14:15.889 align:start position:0% a strong community we<00:14:13.860> have<00:14:13.980> many<00:14:14.160> ideas<00:14:14.399> here 00:14:15.889 --> 00:14:15.899 align:start position:0% we have many ideas here 00:14:15.899 --> 00:14:18.590 align:start position:0% we have many ideas here one<00:14:16.500> of<00:14:16.680> them<00:14:16.800> is<00:14:17.040> our<00:14:17.339> guns<00:14:17.760> round<00:14:17.880> so<00:14:18.300> we<00:14:18.480> are 00:14:18.590 --> 00:14:18.600 align:start position:0% one of them is our guns round so we are 00:14:18.600 --> 00:14:20.690 align:start position:0% one of them is our guns round so we are launching<00:14:18.899> a<00:14:19.019> summer<00:14:19.200> foreground<00:14:19.680> round 00:14:20.690 --> 00:14:20.700 align:start position:0% launching a summer foreground round 00:14:20.700 --> 00:14:21.410 align:start position:0% launching a summer foreground round um 00:14:21.410 --> 00:14:21.420 align:start position:0% um 00:14:21.420 --> 00:14:23.629 align:start position:0% um you<00:14:21.899> can<00:14:22.019> scan<00:14:22.200> the<00:14:22.380> core<00:14:22.560> code<00:14:22.800> on<00:14:22.980> the<00:14:23.100> left 00:14:23.629 --> 00:14:23.639 align:start position:0% you can scan the core code on the left 00:14:23.639 --> 00:14:26.269 align:start position:0% you can scan the core code on the left and<00:14:24.540> uh<00:14:24.899> yeah<00:14:25.139> if<00:14:25.320> you<00:14:25.440> are<00:14:25.860> interested<00:14:26.160> in 00:14:26.269 --> 00:14:26.279 align:start position:0% and uh yeah if you are interested in 00:14:26.279 --> 00:14:28.009 align:start position:0% and uh yeah if you are interested in building<00:14:26.639> privacy<00:14:27.120> preserving<00:14:27.660> applications 00:14:28.009 --> 00:14:28.019 align:start position:0% building privacy preserving applications 00:14:28.019 --> 00:14:29.870 align:start position:0% building privacy preserving applications with<00:14:28.260> semaphore 00:14:29.870 --> 00:14:29.880 align:start position:0% with semaphore 00:14:29.880 --> 00:14:30.769 align:start position:0% with semaphore um 00:14:30.769 --> 00:14:30.779 align:start position:0% um 00:14:30.779 --> 00:14:33.650 align:start position:0% um you<00:14:31.260> can<00:14:31.320> scan<00:14:31.500> that<00:14:31.740> QR<00:14:32.100> code<00:14:32.220> we<00:14:33.000> will<00:14:33.180> we 00:14:33.650 --> 00:14:33.660 align:start position:0% you can scan that QR code we will we 00:14:33.660 --> 00:14:35.090 align:start position:0% you can scan that QR code we will we will<00:14:33.899> be<00:14:34.019> really<00:14:34.200> excited<00:14:34.680> to<00:14:34.800> know<00:14:34.920> more 00:14:35.090 --> 00:14:35.100 align:start position:0% will be really excited to know more 00:14:35.100 --> 00:14:37.550 align:start position:0% will be really excited to know more about<00:14:35.279> your<00:14:35.579> ideas<00:14:35.760> and<00:14:36.120> projects 00:14:37.550 --> 00:14:37.560 align:start position:0% about your ideas and projects 00:14:37.560 --> 00:14:38.990 align:start position:0% about your ideas and projects whereas<00:14:38.040> if<00:14:38.220> you<00:14:38.399> want<00:14:38.579> more<00:14:38.820> information 00:14:38.990 --> 00:14:39.000 align:start position:0% whereas if you want more information 00:14:39.000 --> 00:14:41.569 align:start position:0% whereas if you want more information about<00:14:39.360> semaphore<00:14:40.079> or<00:14:40.380> if<00:14:40.680> you<00:14:40.860> have<00:14:41.100> any 00:14:41.569 --> 00:14:41.579 align:start position:0% about semaphore or if you have any 00:14:41.579 --> 00:14:43.850 align:start position:0% about semaphore or if you have any questions<00:14:41.820> please<00:14:42.300> visit<00:14:42.600> our<00:14:42.959> website<00:14:43.440> where 00:14:43.850 --> 00:14:43.860 align:start position:0% questions please visit our website where 00:14:43.860 --> 00:14:46.189 align:start position:0% questions please visit our website where you<00:14:44.040> can<00:14:44.160> also<00:14:44.459> find<00:14:44.699> our<00:14:45.240> disc<00:14:45.540> the<00:14:45.839> link<00:14:45.959> of 00:14:46.189 --> 00:14:46.199 align:start position:0% you can also find our disc the link of 00:14:46.199 --> 00:14:49.490 align:start position:0% you can also find our disc the link of our<00:14:46.320> Discord<00:14:46.800> server<00:14:47.240> or<00:14:48.240> come<00:14:48.600> come<00:14:48.959> to<00:14:49.260> our 00:14:49.490 --> 00:14:49.500 align:start position:0% our Discord server or come come to our 00:14:49.500 --> 00:14:52.490 align:start position:0% our Discord server or come come to our touch<00:14:49.800> boot<00:14:50.279> on<00:14:50.519> the<00:14:50.639> first<00:14:50.760> floor 00:14:52.490 --> 00:14:52.500 align:start position:0% touch boot on the first floor 00:14:52.500 --> 00:14:55.910 align:start position:0% touch boot on the first floor so<00:14:53.459> I<00:14:53.880> of<00:14:54.120> my<00:14:54.240> talk<00:14:54.420> has<00:14:54.660> been<00:14:54.779> helpful<00:14:55.139> and<00:14:55.560> I 00:14:55.910 --> 00:14:55.920 align:start position:0% so I of my talk has been helpful and I 00:14:55.920 --> 00:14:56.990 align:start position:0% so I of my talk has been helpful and I really<00:14:56.040> want<00:14:56.279> to<00:14:56.399> thank<00:14:56.519> you<00:14:56.699> all<00:14:56.820> for 00:14:56.990 --> 00:14:57.000 align:start position:0% really want to thank you all for 00:14:57.000 --> 00:15:01.430 align:start position:0% really want to thank you all for listening 00:15:01.430 --> 00:15:01.440 align:start position:0% 00:15:01.440 --> 00:15:03.230 align:start position:0% thank<00:15:02.100> you 00:15:03.230 --> 00:15:03.240 align:start position:0% thank you 00:15:03.240 --> 00:15:05.750 align:start position:0% thank you we<00:15:03.899> have<00:15:04.079> eight<00:15:04.560> minutes<00:15:04.800> for<00:15:05.220> any<00:15:05.519> question 00:15:05.750 --> 00:15:05.760 align:start position:0% we have eight minutes for any question 00:15:05.760 --> 00:15:08.629 align:start position:0% we have eight minutes for any question that<00:15:06.060> you<00:15:06.180> have<00:15:06.300> for<00:15:06.660> cedor 00:15:08.629 --> 00:15:08.639 align:start position:0% that you have for cedor 00:15:08.639 --> 00:15:12.410 align:start position:0% that you have for cedor no<00:15:09.420> no<00:15:09.839> questions<00:15:10.079> okay 00:15:12.410 --> 00:15:12.420 align:start position:0% no no questions okay 00:15:12.420 --> 00:15:14.689 align:start position:0% no no questions okay so<00:15:12.779> you<00:15:12.899> can<00:15:13.019> go<00:15:13.139> to<00:15:13.320> those<00:15:13.500> QR<00:15:14.040> and<00:15:14.459> continue 00:15:14.689 --> 00:15:14.699 align:start position:0% so you can go to those QR and continue 00:15:14.699 --> 00:15:16.550 align:start position:0% so you can go to those QR and continue the<00:15:15.000> conversation<00:15:15.360> on<00:15:15.600> the<00:15:15.720> website<00:15:16.019> and<00:15:16.320> the 00:15:16.550 --> 00:15:16.560 align:start position:0% the conversation on the website and the 00:15:16.560 --> 00:15:19.040 align:start position:0% the conversation on the website and the grants