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:15.110 align:start position:0% [Music] 00:00:15.110 --> 00:00:15.120 align:start position:0% 00:00:15.120 --> 00:00:17.570 align:start position:0% hi<00:00:15.660> my<00:00:15.960> name<00:00:16.020> is<00:00:16.139> Adrian<00:00:16.560> I'm<00:00:17.039> the<00:00:17.160> founder<00:00:17.520> of 00:00:17.570 --> 00:00:17.580 align:start position:0% hi my name is Adrian I'm the founder of 00:00:17.580 --> 00:00:20.029 align:start position:0% hi my name is Adrian I'm the founder of sismo<00:00:18.240> and<00:00:18.660> I'm<00:00:18.779> excited<00:00:19.140> to<00:00:19.320> speak<00:00:19.800> today 00:00:20.029 --> 00:00:20.039 align:start position:0% sismo and I'm excited to speak today 00:00:20.039 --> 00:00:22.250 align:start position:0% sismo and I'm excited to speak today about<00:00:20.400> GK<00:00:20.760> buddies<00:00:21.119> that<00:00:21.359> are<00:00:21.600> new<00:00:21.779> primitive 00:00:22.250 --> 00:00:22.260 align:start position:0% about GK buddies that are new primitive 00:00:22.260 --> 00:00:24.769 align:start position:0% about GK buddies that are new primitive for<00:00:22.500> you<00:00:22.619> to<00:00:22.859> leverage<00:00:23.580> fully<00:00:24.060> your<00:00:24.300> own<00:00:24.480> chain 00:00:24.769 --> 00:00:24.779 align:start position:0% for you to leverage fully your own chain 00:00:24.779 --> 00:00:27.529 align:start position:0% for you to leverage fully your own chain data<00:00:25.199> you<00:00:25.619> also<00:00:25.859> bring<00:00:26.039> data<00:00:26.460> so<00:00:27.060> this<00:00:27.300> talk 00:00:27.529 --> 00:00:27.539 align:start position:0% data you also bring data so this talk 00:00:27.539 --> 00:00:29.630 align:start position:0% data you also bring data so this talk will<00:00:27.779> cover<00:00:27.960> the<00:00:28.260> notion<00:00:28.560> of<00:00:28.800> sovereign 00:00:29.630 --> 00:00:29.640 align:start position:0% will cover the notion of sovereign 00:00:29.640 --> 00:00:32.990 align:start position:0% will cover the notion of sovereign occurrence<00:00:30.380> self-solving<00:00:31.380> identities<00:00:32.000> but 00:00:32.990 --> 00:00:33.000 align:start position:0% occurrence self-solving identities but 00:00:33.000 --> 00:00:34.790 align:start position:0% occurrence self-solving identities but but<00:00:33.300> before<00:00:33.600> getting<00:00:33.899> into<00:00:34.079> that<00:00:34.320> I'd<00:00:34.620> just 00:00:34.790 --> 00:00:34.800 align:start position:0% but before getting into that I'd just 00:00:34.800 --> 00:00:37.150 align:start position:0% but before getting into that I'd just like<00:00:34.980> to<00:00:35.160> spend<00:00:35.399> a<00:00:35.520> few<00:00:35.640> words<00:00:35.760> about<00:00:35.940> sismo 00:00:37.150 --> 00:00:37.160 align:start position:0% like to spend a few words about sismo 00:00:37.160 --> 00:00:39.709 align:start position:0% like to spend a few words about sismo we<00:00:38.160> started<00:00:38.520> this<00:00:38.940> move<00:00:39.120> because<00:00:39.300> we<00:00:39.540> are 00:00:39.709 --> 00:00:39.719 align:start position:0% we started this move because we are 00:00:39.719 --> 00:00:41.569 align:start position:0% we started this move because we are concerned<00:00:40.020> about<00:00:40.140> the<00:00:40.379> centralization<00:00:41.040> and 00:00:41.569 --> 00:00:41.579 align:start position:0% concerned about the centralization and 00:00:41.579 --> 00:00:43.850 align:start position:0% concerned about the centralization and lack<00:00:41.760> of<00:00:41.940> privacy<00:00:42.420> of<00:00:43.079> our<00:00:43.200> recurrent<00:00:43.620> social 00:00:43.850 --> 00:00:43.860 align:start position:0% lack of privacy of our recurrent social 00:00:43.860 --> 00:00:46.250 align:start position:0% lack of privacy of our recurrent social tools<00:00:44.399> and<00:00:44.820> digital<00:00:45.180> identities 00:00:46.250 --> 00:00:46.260 align:start position:0% tools and digital identities 00:00:46.260 --> 00:00:49.069 align:start position:0% tools and digital identities we<00:00:46.800> think<00:00:47.040> that<00:00:47.399> there's<00:00:47.940> too<00:00:48.300> much<00:00:48.420> power<00:00:48.660> in 00:00:49.069 --> 00:00:49.079 align:start position:0% we think that there's too much power in 00:00:49.079 --> 00:00:50.690 align:start position:0% we think that there's too much power in the<00:00:49.200> hands<00:00:49.440> of<00:00:49.559> big<00:00:49.800> companies<00:00:50.219> holding<00:00:50.579> our 00:00:50.690 --> 00:00:50.700 align:start position:0% the hands of big companies holding our 00:00:50.700 --> 00:00:52.729 align:start position:0% the hands of big companies holding our personal<00:00:50.879> data<00:00:51.420> and<00:00:51.899> in<00:00:52.079> governments<00:00:52.620> that 00:00:52.729 --> 00:00:52.739 align:start position:0% personal data and in governments that 00:00:52.739 --> 00:00:56.270 align:start position:0% personal data and in governments that can<00:00:52.980> access<00:00:53.160> it<00:00:53.520> at<00:00:53.820> will<00:00:54.480> and<00:00:55.140> so<00:00:55.440> what<00:00:56.160> we 00:00:56.270 --> 00:00:56.280 align:start position:0% can access it at will and so what we 00:00:56.280 --> 00:00:58.430 align:start position:0% can access it at will and so what we want<00:00:56.460> to<00:00:56.579> do<00:00:56.760> is<00:00:57.180> really<00:00:57.300> to<00:00:57.600> add<00:00:57.840> a<00:00:58.079> privacy 00:00:58.430 --> 00:00:58.440 align:start position:0% want to do is really to add a privacy 00:00:58.440 --> 00:01:01.310 align:start position:0% want to do is really to add a privacy and<00:00:58.860> the<00:00:59.039> centralization<00:00:59.579> layer<00:01:00.059> in<00:01:00.780> identity 00:01:01.310 --> 00:01:01.320 align:start position:0% and the centralization layer in identity 00:01:01.320 --> 00:01:04.729 align:start position:0% and the centralization layer in identity systems<00:01:02.160> so<00:01:02.760> that<00:01:02.940> will<00:01:03.180> remain<00:01:03.480> Sovereign<00:01:04.140> we 00:01:04.729 --> 00:01:04.739 align:start position:0% systems so that will remain Sovereign we 00:01:04.739 --> 00:01:06.770 align:start position:0% systems so that will remain Sovereign we want<00:01:04.799> to<00:01:04.920> protect<00:01:05.220> human<00:01:05.460> sobriety<00:01:06.000> meaning 00:01:06.770 --> 00:01:06.780 align:start position:0% want to protect human sobriety meaning 00:01:06.780 --> 00:01:09.289 align:start position:0% want to protect human sobriety meaning that<00:01:07.140> we<00:01:07.619> want<00:01:07.799> to<00:01:07.920> be<00:01:08.040> sure<00:01:08.220> that<00:01:08.520> individuals 00:01:09.289 --> 00:01:09.299 align:start position:0% that we want to be sure that individuals 00:01:09.299 --> 00:01:12.469 align:start position:0% that we want to be sure that individuals remain<00:01:10.200> in<00:01:10.380> control<00:01:10.680> of<00:01:11.220> their<00:01:11.400> societies<00:01:12.060> and 00:01:12.469 --> 00:01:12.479 align:start position:0% remain in control of their societies and 00:01:12.479 --> 00:01:13.969 align:start position:0% remain in control of their societies and that<00:01:12.600> we<00:01:12.840> keep<00:01:13.020> unchecked<00:01:13.680> the<00:01:13.799> central 00:01:13.969 --> 00:01:13.979 align:start position:0% that we keep unchecked the central 00:01:13.979 --> 00:01:16.670 align:start position:0% that we keep unchecked the central entities<00:01:14.580> that<00:01:15.000> are<00:01:15.240> public<00:01:16.140> or<00:01:16.380> private 00:01:16.670 --> 00:01:16.680 align:start position:0% entities that are public or private 00:01:16.680 --> 00:01:18.950 align:start position:0% entities that are public or private institutions<00:01:17.220> what<00:01:17.880> we<00:01:18.060> do<00:01:18.299> is<00:01:18.720> build 00:01:18.950 --> 00:01:18.960 align:start position:0% institutions what we do is build 00:01:18.960 --> 00:01:21.469 align:start position:0% institutions what we do is build Primitives<00:01:19.439> to<00:01:19.860> empower<00:01:20.280> our<00:01:20.759> self-solving 00:01:21.469 --> 00:01:21.479 align:start position:0% Primitives to empower our self-solving 00:01:21.479 --> 00:01:24.530 align:start position:0% Primitives to empower our self-solving identities<00:01:21.900> so<00:01:22.439> the<00:01:22.920> first<00:01:23.520> primitive<00:01:24.299> that 00:01:24.530 --> 00:01:24.540 align:start position:0% identities so the first primitive that 00:01:24.540 --> 00:01:27.130 align:start position:0% identities so the first primitive that we<00:01:24.720> built<00:01:25.080> are<00:01:25.560> ZK<00:01:25.979> badges 00:01:27.130 --> 00:01:27.140 align:start position:0% we built are ZK badges 00:01:27.140 --> 00:01:29.510 align:start position:0% we built are ZK badges they<00:01:28.140> allow<00:01:28.439> you<00:01:28.500> to<00:01:28.680> leverage<00:01:28.920> your<00:01:29.159> serving 00:01:29.510 --> 00:01:29.520 align:start position:0% they allow you to leverage your serving 00:01:29.520 --> 00:01:31.910 align:start position:0% they allow you to leverage your serving data<00:01:29.880> we'll<00:01:30.420> see<00:01:30.659> that<00:01:30.900> later<00:01:31.080> but<00:01:31.439> there<00:01:31.740> are 00:01:31.910 --> 00:01:31.920 align:start position:0% data we'll see that later but there are 00:01:31.920 --> 00:01:33.770 align:start position:0% data we'll see that later but there are soluble<00:01:32.280> tokens<00:01:32.759> there<00:01:33.000> are<00:01:33.119> non-trustworld 00:01:33.770 --> 00:01:33.780 align:start position:0% soluble tokens there are non-trustworld 00:01:33.780 --> 00:01:36.289 align:start position:0% soluble tokens there are non-trustworld tokens<00:01:34.140> that<00:01:34.860> are<00:01:35.100> attestation<00:01:35.700> meaning<00:01:36.060> that 00:01:36.289 --> 00:01:36.299 align:start position:0% tokens that are attestation meaning that 00:01:36.299 --> 00:01:38.330 align:start position:0% tokens that are attestation meaning that when<00:01:36.600> you<00:01:36.720> have<00:01:36.840> SDK<00:01:37.320> badge<00:01:37.680> it<00:01:38.040> means 00:01:38.330 --> 00:01:38.340 align:start position:0% when you have SDK badge it means 00:01:38.340 --> 00:01:41.090 align:start position:0% when you have SDK badge it means something<00:01:38.460> about<00:01:38.880> your<00:01:39.600> identity<00:01:40.079> your<00:01:40.740> data 00:01:41.090 --> 00:01:41.100 align:start position:0% something about your identity your data 00:01:41.100 --> 00:01:44.030 align:start position:0% something about your identity your data your<00:01:41.340> reputation<00:01:41.759> your<00:01:42.060> history<00:01:42.740> they<00:01:43.740> allow 00:01:44.030 --> 00:01:44.040 align:start position:0% your reputation your history they allow 00:01:44.040 --> 00:01:46.490 align:start position:0% your reputation your history they allow to<00:01:44.220> you<00:01:44.400> to<00:01:44.640> do<00:01:44.880> three<00:01:45.240> things<00:01:45.659> first<00:01:46.259> they 00:01:46.490 --> 00:01:46.500 align:start position:0% to you to do three things first they 00:01:46.500 --> 00:01:48.289 align:start position:0% to you to do three things first they allow<00:01:46.740> you<00:01:46.860> to<00:01:46.979> import<00:01:47.159> reputation<00:01:47.880> from<00:01:48.180> an 00:01:48.289 --> 00:01:48.299 align:start position:0% allow you to import reputation from an 00:01:48.299 --> 00:01:49.789 align:start position:0% allow you to import reputation from an account<00:01:48.540> to<00:01:48.780> another<00:01:48.900> let's<00:01:49.380> say<00:01:49.560> I<00:01:49.740> have 00:01:49.789 --> 00:01:49.799 align:start position:0% account to another let's say I have 00:01:49.799 --> 00:01:51.410 align:start position:0% account to another let's say I have let's<00:01:50.280> say<00:01:50.460> that<00:01:50.579> I<00:01:50.700> have<00:01:50.820> a<00:01:50.880> point<00:01:51.060> content 00:01:51.410 --> 00:01:51.420 align:start position:0% let's say that I have a point content 00:01:51.420 --> 00:01:54.109 align:start position:0% let's say that I have a point content address<00:01:51.659> and<00:01:52.500> I<00:01:52.680> want<00:01:52.860> to<00:01:53.460> prove<00:01:53.759> that<00:01:53.880> on 00:01:54.109 --> 00:01:54.119 align:start position:0% address and I want to prove that on 00:01:54.119 --> 00:01:56.450 align:start position:0% address and I want to prove that on another<00:01:54.240> address<00:01:54.540> have<00:01:54.899> an<00:01:55.079> attestation<00:01:55.500> I<00:01:56.280> I 00:01:56.450 --> 00:01:56.460 align:start position:0% another address have an attestation I I 00:01:56.460 --> 00:01:58.730 align:start position:0% another address have an attestation I I get<00:01:56.640> to<00:01:56.700> ZK<00:01:57.060> batch<00:01:57.420> on<00:01:57.840> the<00:01:57.960> new<00:01:58.079> address<00:01:58.320> and<00:01:58.560> I 00:01:58.730 --> 00:01:58.740 align:start position:0% get to ZK batch on the new address and I 00:01:58.740 --> 00:02:01.069 align:start position:0% get to ZK batch on the new address and I have<00:01:59.280> the<00:01:59.460> proof<00:01:59.700> that<00:01:59.820> I<00:01:59.939> have<00:02:00.000> a<00:02:00.180> book<00:02:00.360> it 00:02:01.069 --> 00:02:01.079 align:start position:0% have the proof that I have a book it 00:02:01.079 --> 00:02:04.310 align:start position:0% have the proof that I have a book it also<00:02:01.380> allows<00:02:01.860> me<00:02:02.040> to<00:02:02.939> selectively<00:02:03.840> reveal 00:02:04.310 --> 00:02:04.320 align:start position:0% also allows me to selectively reveal 00:02:04.320 --> 00:02:06.830 align:start position:0% also allows me to selectively reveal what<00:02:04.560> I<00:02:04.680> want<00:02:04.799> from<00:02:04.979> my<00:02:05.159> account<00:02:05.340> so 00:02:06.830 --> 00:02:06.840 align:start position:0% what I want from my account so 00:02:06.840 --> 00:02:08.749 align:start position:0% what I want from my account so granularly<00:02:07.740> reveals<00:02:08.160> some<00:02:08.280> personality 00:02:08.749 --> 00:02:08.759 align:start position:0% granularly reveals some personality 00:02:08.759 --> 00:02:10.609 align:start position:0% granularly reveals some personality let's<00:02:09.360> say<00:02:09.539> that<00:02:09.720> I<00:02:09.780> have<00:02:09.959> an<00:02:10.080> account<00:02:10.200> with<00:02:10.500> a 00:02:10.609 --> 00:02:10.619 align:start position:0% let's say that I have an account with a 00:02:10.619 --> 00:02:12.949 align:start position:0% let's say that I have an account with a lot<00:02:10.679> of<00:02:10.860> data<00:02:11.220> I'm<00:02:11.700> able<00:02:12.000> to<00:02:12.060> pick<00:02:12.360> one<00:02:12.720> piece 00:02:12.949 --> 00:02:12.959 align:start position:0% lot of data I'm able to pick one piece 00:02:12.959 --> 00:02:14.330 align:start position:0% lot of data I'm able to pick one piece of<00:02:13.080> data<00:02:13.440> let's<00:02:13.680> say<00:02:13.800> the<00:02:13.920> crypto<00:02:14.220> pen 00:02:14.330 --> 00:02:14.340 align:start position:0% of data let's say the crypto pen 00:02:14.340 --> 00:02:15.949 align:start position:0% of data let's say the crypto pen ownership<00:02:14.700> and<00:02:15.180> I'll<00:02:15.300> be<00:02:15.420> able<00:02:15.540> to<00:02:15.660> reveal 00:02:15.949 --> 00:02:15.959 align:start position:0% ownership and I'll be able to reveal 00:02:15.959 --> 00:02:17.809 align:start position:0% ownership and I'll be able to reveal that<00:02:16.140> to<00:02:16.260> someone<00:02:16.440> I<00:02:17.160> own<00:02:17.340> that<00:02:17.520> without 00:02:17.809 --> 00:02:17.819 align:start position:0% that to someone I own that without 00:02:17.819 --> 00:02:19.850 align:start position:0% that to someone I own that without giving<00:02:18.120> my<00:02:18.300> address<00:02:18.420> or<00:02:18.660> anything<00:02:18.780> else<00:02:19.080> the 00:02:19.850 --> 00:02:19.860 align:start position:0% giving my address or anything else the 00:02:19.860 --> 00:02:21.949 align:start position:0% giving my address or anything else the the<00:02:20.099> last<00:02:20.340> thing<00:02:20.640> is<00:02:20.940> it<00:02:21.300> allows<00:02:21.660> you<00:02:21.720> to 00:02:21.949 --> 00:02:21.959 align:start position:0% the last thing is it allows you to 00:02:21.959 --> 00:02:24.710 align:start position:0% the last thing is it allows you to aggregate<00:02:22.440> your<00:02:22.620> data<00:02:23.040> let's<00:02:23.640> say<00:02:23.879> that<00:02:24.180> you 00:02:24.710 --> 00:02:24.720 align:start position:0% aggregate your data let's say that you 00:02:24.720 --> 00:02:27.770 align:start position:0% aggregate your data let's say that you have<00:02:25.040> a<00:02:26.040> punk<00:02:26.580> on<00:02:26.700> an<00:02:26.879> address<00:02:27.000> and<00:02:27.300> a<00:02:27.480> bank<00:02:27.599> on 00:02:27.770 --> 00:02:27.780 align:start position:0% have a punk on an address and a bank on 00:02:27.780 --> 00:02:30.050 align:start position:0% have a punk on an address and a bank on another<00:02:27.959> one<00:02:28.260> and<00:02:28.620> you'd<00:02:28.920> like<00:02:29.040> to<00:02:29.340> prove<00:02:29.940> that 00:02:30.050 --> 00:02:30.060 align:start position:0% another one and you'd like to prove that 00:02:30.060 --> 00:02:32.270 align:start position:0% another one and you'd like to prove that you<00:02:30.239> have<00:02:30.360> two<00:02:30.540> punks<00:02:31.020> without<00:02:31.560> creating<00:02:32.040> a 00:02:32.270 --> 00:02:32.280 align:start position:0% you have two punks without creating a 00:02:32.280 --> 00:02:35.210 align:start position:0% you have two punks without creating a link<00:02:32.459> between<00:02:33.300> your<00:02:33.599> accounts<00:02:34.500> that's<00:02:35.040> what 00:02:35.210 --> 00:02:35.220 align:start position:0% link between your accounts that's what 00:02:35.220 --> 00:02:37.790 align:start position:0% link between your accounts that's what DK<00:02:35.580> badges<00:02:35.940> allow<00:02:36.360> you<00:02:36.480> to<00:02:36.599> do<00:02:36.780> so<00:02:37.200> it<00:02:37.500> allows 00:02:37.790 --> 00:02:37.800 align:start position:0% DK badges allow you to do so it allows 00:02:37.800 --> 00:02:41.210 align:start position:0% DK badges allow you to do so it allows you<00:02:37.860> to<00:02:38.040> do<00:02:38.280> to<00:02:38.879> control<00:02:39.120> your<00:02:39.599> identities<00:02:40.220> and 00:02:41.210 --> 00:02:41.220 align:start position:0% you to do to control your identities and 00:02:41.220 --> 00:02:43.250 align:start position:0% you to do to control your identities and without<00:02:41.519> creating<00:02:42.000> links<00:02:42.300> between<00:02:42.480> them<00:02:42.720> so 00:02:43.250 --> 00:02:43.260 align:start position:0% without creating links between them so 00:02:43.260 --> 00:02:45.410 align:start position:0% without creating links between them so now<00:02:43.620> I<00:02:43.739> think<00:02:43.920> that<00:02:44.099> before<00:02:44.340> getting<00:02:44.700> into<00:02:44.940> the 00:02:45.410 --> 00:02:45.420 align:start position:0% now I think that before getting into the 00:02:45.420 --> 00:02:47.330 align:start position:0% now I think that before getting into the the<00:02:45.780> technical<00:02:46.140> parts<00:02:46.379> of<00:02:46.560> the<00:02:46.680> SDK<00:02:46.980> badges 00:02:47.330 --> 00:02:47.340 align:start position:0% the technical parts of the SDK badges 00:02:47.340 --> 00:02:48.949 align:start position:0% the technical parts of the SDK badges I'll<00:02:47.819> I'd<00:02:48.000> like<00:02:48.180> to<00:02:48.300> spend<00:02:48.540> some<00:02:48.660> time<00:02:48.780> on 00:02:48.949 --> 00:02:48.959 align:start position:0% I'll I'd like to spend some time on 00:02:48.959 --> 00:02:51.770 align:start position:0% I'll I'd like to spend some time on self-serving<00:02:49.620> identities<00:02:50.239> and<00:02:51.239> because 00:02:51.770 --> 00:02:51.780 align:start position:0% self-serving identities and because 00:02:51.780 --> 00:02:54.350 align:start position:0% self-serving identities and because that's<00:02:52.500> what<00:02:52.739> budgets<00:02:53.400> for<00:02:53.580> we<00:02:53.940> built<00:02:54.239> that 00:02:54.350 --> 00:02:54.360 align:start position:0% that's what budgets for we built that 00:02:54.360 --> 00:02:57.290 align:start position:0% that's what budgets for we built that it's<00:02:54.840> it's<00:02:54.900> our<00:02:55.680> goal<00:02:55.980> is<00:02:56.040> really<00:02:56.220> to 00:02:57.290 --> 00:02:57.300 align:start position:0% it's it's our goal is really to 00:02:57.300 --> 00:02:59.630 align:start position:0% it's it's our goal is really to with<00:02:57.780> DK<00:02:58.140> Badges<00:02:58.500> and<00:02:58.680> generally<00:02:58.920> with<00:02:59.099> cismo 00:02:59.630 --> 00:02:59.640 align:start position:0% with DK Badges and generally with cismo 00:02:59.640 --> 00:03:01.610 align:start position:0% with DK Badges and generally with cismo is<00:02:59.879> to<00:03:00.000> make<00:03:00.120> our<00:03:00.239> Sovereign<00:03:00.599> identities<00:03:00.959> more 00:03:01.610 --> 00:03:01.620 align:start position:0% is to make our Sovereign identities more 00:03:01.620 --> 00:03:03.949 align:start position:0% is to make our Sovereign identities more powerful<00:03:01.980> better<00:03:02.459> than<00:03:02.700> web<00:03:02.940> 2<00:03:03.180> identities<00:03:03.599> so 00:03:03.949 --> 00:03:03.959 align:start position:0% powerful better than web 2 identities so 00:03:03.959 --> 00:03:06.949 align:start position:0% powerful better than web 2 identities so better<00:03:04.140> than<00:03:04.440> your<00:03:04.620> Google<00:03:04.800> account<00:03:05.040> so<00:03:06.420> a<00:03:06.840> web 00:03:06.949 --> 00:03:06.959 align:start position:0% better than your Google account so a web 00:03:06.959 --> 00:03:09.290 align:start position:0% better than your Google account so a web 2<00:03:07.140> identities<00:03:07.560> a<00:03:08.280> web<00:03:08.400> to<00:03:08.580> energy<00:03:08.760> in<00:03:09.060> the<00:03:09.180> web 00:03:09.290 --> 00:03:09.300 align:start position:0% 2 identities a web to energy in the web 00:03:09.300 --> 00:03:12.589 align:start position:0% 2 identities a web to energy in the web to<00:03:09.480> world<00:03:09.720> the<00:03:10.260> ITT<00:03:10.680> is<00:03:11.220> stored<00:03:11.580> in<00:03:11.879> an<00:03:12.360> account 00:03:12.589 --> 00:03:12.599 align:start position:0% to world the ITT is stored in an account 00:03:12.599 --> 00:03:14.570 align:start position:0% to world the ITT is stored in an account let's<00:03:13.140> say<00:03:13.319> your<00:03:13.440> Twitter<00:03:13.680> account<00:03:13.920> you 00:03:14.570 --> 00:03:14.580 align:start position:0% let's say your Twitter account you 00:03:14.580 --> 00:03:16.490 align:start position:0% let's say your Twitter account you choose<00:03:14.760> your<00:03:14.940> username<00:03:15.420> your<00:03:15.659> password<00:03:15.900> and 00:03:16.490 --> 00:03:16.500 align:start position:0% choose your username your password and 00:03:16.500 --> 00:03:18.050 align:start position:0% choose your username your password and they<00:03:16.620> give<00:03:16.800> you<00:03:16.920> an<00:03:17.040> account<00:03:17.159> actually<00:03:17.640> they 00:03:18.050 --> 00:03:18.060 align:start position:0% they give you an account actually they 00:03:18.060 --> 00:03:19.670 align:start position:0% they give you an account actually they don't<00:03:18.239> really<00:03:18.540> give<00:03:18.780> you<00:03:18.959> the<00:03:19.080> accounts<00:03:19.500> it's 00:03:19.670 --> 00:03:19.680 align:start position:0% don't really give you the accounts it's 00:03:19.680 --> 00:03:22.729 align:start position:0% don't really give you the accounts it's still<00:03:19.860> theirs<00:03:20.220> but<00:03:20.760> you<00:03:21.000> can<00:03:21.180> access<00:03:21.659> it<00:03:22.019> if 00:03:22.729 --> 00:03:22.739 align:start position:0% still theirs but you can access it if 00:03:22.739 --> 00:03:25.750 align:start position:0% still theirs but you can access it if they<00:03:23.099> are<00:03:23.519> willing<00:03:23.879> to<00:03:24.000> and<00:03:24.659> you<00:03:24.780> start 00:03:25.750 --> 00:03:25.760 align:start position:0% they are willing to and you start 00:03:25.760 --> 00:03:28.250 align:start position:0% they are willing to and you start doing<00:03:26.760> things<00:03:27.120> on<00:03:27.360> Twitter<00:03:27.540> you<00:03:27.900> interact 00:03:28.250 --> 00:03:28.260 align:start position:0% doing things on Twitter you interact 00:03:28.260 --> 00:03:29.570 align:start position:0% doing things on Twitter you interact with<00:03:28.319> others<00:03:28.739> and<00:03:28.920> you<00:03:29.040> are<00:03:29.159> starting<00:03:29.340> to 00:03:29.570 --> 00:03:29.580 align:start position:0% with others and you are starting to 00:03:29.580 --> 00:03:31.430 align:start position:0% with others and you are starting to build<00:03:29.700> your<00:03:29.940> identity<00:03:30.360> so<00:03:30.840> here<00:03:31.019> you<00:03:31.200> have<00:03:31.319> an 00:03:31.430 --> 00:03:31.440 align:start position:0% build your identity so here you have an 00:03:31.440 --> 00:03:33.830 align:start position:0% build your identity so here you have an identity<00:03:31.920> in<00:03:32.640> a<00:03:32.819> webto<00:03:33.120> account<00:03:33.300> that<00:03:33.599> is<00:03:33.720> not 00:03:33.830 --> 00:03:33.840 align:start position:0% identity in a webto account that is not 00:03:33.840 --> 00:03:35.990 align:start position:0% identity in a webto account that is not yours<00:03:34.200> it's<00:03:34.800> your<00:03:35.040> identity<00:03:35.459> you<00:03:35.700> have<00:03:35.879> the 00:03:35.990 --> 00:03:36.000 align:start position:0% yours it's your identity you have the 00:03:36.000 --> 00:03:37.670 align:start position:0% yours it's your identity you have the same<00:03:36.120> with<00:03:36.300> Facebook<00:03:36.480> with<00:03:36.959> with<00:03:37.319> Instagram 00:03:37.670 --> 00:03:37.680 align:start position:0% same with Facebook with with Instagram 00:03:37.680 --> 00:03:39.830 align:start position:0% same with Facebook with with Instagram with<00:03:38.159> LinkedIn<00:03:38.580> you<00:03:38.940> have<00:03:39.060> your<00:03:39.239> identities 00:03:39.830 --> 00:03:39.840 align:start position:0% with LinkedIn you have your identities 00:03:39.840 --> 00:03:42.470 align:start position:0% with LinkedIn you have your identities that<00:03:40.200> are<00:03:40.440> on<00:03:41.159> rented<00:03:41.640> accounts<00:03:42.180> an 00:03:42.470 --> 00:03:42.480 align:start position:0% that are on rented accounts an 00:03:42.480 --> 00:03:45.289 align:start position:0% that are on rented accounts an interesting<00:03:42.959> thing<00:03:43.319> about<00:03:43.860> this<00:03:44.459> identities 00:03:45.289 --> 00:03:45.299 align:start position:0% interesting thing about this identities 00:03:45.299 --> 00:03:47.630 align:start position:0% interesting thing about this identities is<00:03:45.599> that<00:03:45.780> you<00:03:46.019> still<00:03:46.200> have<00:03:46.440> some<00:03:46.860> control<00:03:47.340> over 00:03:47.630 --> 00:03:47.640 align:start position:0% is that you still have some control over 00:03:47.640 --> 00:03:49.670 align:start position:0% is that you still have some control over them<00:03:47.940> you<00:03:48.659> can<00:03:48.780> use<00:03:48.959> them<00:03:49.140> to<00:03:49.379> connect<00:03:49.440> to 00:03:49.670 --> 00:03:49.680 align:start position:0% them you can use them to connect to 00:03:49.680 --> 00:03:52.670 align:start position:0% them you can use them to connect to other<00:03:49.920> services<00:03:50.220> that's<00:03:51.180> the<00:03:51.659> singer<00:03:52.260> sign-on 00:03:52.670 --> 00:03:52.680 align:start position:0% other services that's the singer sign-on 00:03:52.680 --> 00:03:54.350 align:start position:0% other services that's the singer sign-on for<00:03:53.040> instance<00:03:53.159> I<00:03:53.459> can<00:03:53.580> connect<00:03:53.700> to<00:03:53.879> typefully 00:03:54.350 --> 00:03:54.360 align:start position:0% for instance I can connect to typefully 00:03:54.360 --> 00:03:56.990 align:start position:0% for instance I can connect to typefully with<00:03:54.540> my<00:03:54.720> Twitter<00:03:54.840> account<00:03:55.220> and<00:03:56.220> it<00:03:56.519> allows<00:03:56.879> me 00:03:56.990 --> 00:03:57.000 align:start position:0% with my Twitter account and it allows me 00:03:57.000 --> 00:03:58.190 align:start position:0% with my Twitter account and it allows me to 00:03:58.190 --> 00:03:58.200 align:start position:0% to 00:03:58.200 --> 00:04:00.830 align:start position:0% to um I<00:03:58.739> can<00:03:59.099> bring<00:03:59.340> some<00:03:59.519> part<00:03:59.760> of<00:03:59.940> my<00:04:00.239> identity 00:04:00.830 --> 00:04:00.840 align:start position:0% um I can bring some part of my identity 00:04:00.840 --> 00:04:03.229 align:start position:0% um I can bring some part of my identity that<00:04:01.200> is<00:04:01.319> on<00:04:01.560> on<00:04:01.860> Twitter<00:04:02.159> to<00:04:02.459> type<00:04:02.700> free<00:04:02.879> so 00:04:03.229 --> 00:04:03.239 align:start position:0% that is on on Twitter to type free so 00:04:03.239 --> 00:04:05.690 align:start position:0% that is on on Twitter to type free so there<00:04:03.659> is<00:04:03.840> some<00:04:04.019> sort<00:04:04.140> of<00:04:04.260> portability<00:04:04.799> but<00:04:05.519> of 00:04:05.690 --> 00:04:05.700 align:start position:0% there is some sort of portability but of 00:04:05.700 --> 00:04:08.089 align:start position:0% there is some sort of portability but of course<00:04:05.879> it's<00:04:06.000> super<00:04:06.180> easy<00:04:06.360> restricted<00:04:07.200> at<00:04:07.860> any 00:04:08.089 --> 00:04:08.099 align:start position:0% course it's super easy restricted at any 00:04:08.099 --> 00:04:09.649 align:start position:0% course it's super easy restricted at any point<00:04:08.280> if<00:04:08.459> Twitter<00:04:08.640> thinks<00:04:09.000> that<00:04:09.120> I<00:04:09.239> produce 00:04:09.649 --> 00:04:09.659 align:start position:0% point if Twitter thinks that I produce 00:04:09.659 --> 00:04:13.009 align:start position:0% point if Twitter thinks that I produce is<00:04:10.140> competing<00:04:10.739> with<00:04:11.099> Twitter<00:04:11.840> they<00:04:12.840> will 00:04:13.009 --> 00:04:13.019 align:start position:0% is competing with Twitter they will 00:04:13.019 --> 00:04:15.170 align:start position:0% is competing with Twitter they will remove<00:04:13.200> the<00:04:13.439> access<00:04:13.560> of<00:04:13.799> these<00:04:14.040> accounts<00:04:14.400> so 00:04:15.170 --> 00:04:15.180 align:start position:0% remove the access of these accounts so 00:04:15.180 --> 00:04:18.710 align:start position:0% remove the access of these accounts so we<00:04:15.840> see<00:04:16.620> that<00:04:17.639> yeah 00:04:18.710 --> 00:04:18.720 align:start position:0% we see that yeah 00:04:18.720 --> 00:04:21.289 align:start position:0% we see that yeah web<00:04:19.139> 2<00:04:19.380> identities<00:04:19.799> are<00:04:20.160> not<00:04:20.340> yours<00:04:20.699> it's 00:04:21.289 --> 00:04:21.299 align:start position:0% web 2 identities are not yours it's 00:04:21.299 --> 00:04:23.030 align:start position:0% web 2 identities are not yours it's super<00:04:21.540> restricted<00:04:22.079> what<00:04:22.320> you<00:04:22.500> can<00:04:22.560> do<00:04:22.680> as<00:04:22.860> your 00:04:23.030 --> 00:04:23.040 align:start position:0% super restricted what you can do as your 00:04:23.040 --> 00:04:25.010 align:start position:0% super restricted what you can do as your identities<00:04:23.340> of<00:04:24.180> course<00:04:24.360> there's<00:04:24.780> no 00:04:25.010 --> 00:04:25.020 align:start position:0% identities of course there's no 00:04:25.020 --> 00:04:27.350 align:start position:0% identities of course there's no possibility<00:04:25.460> to<00:04:26.460> link<00:04:26.759> your<00:04:27.000> identities 00:04:27.350 --> 00:04:27.360 align:start position:0% possibility to link your identities 00:04:27.360 --> 00:04:29.390 align:start position:0% possibility to link your identities together<00:04:27.660> meaning<00:04:28.020> that<00:04:28.320> it's<00:04:28.740> impossible<00:04:29.220> to 00:04:29.390 --> 00:04:29.400 align:start position:0% together meaning that it's impossible to 00:04:29.400 --> 00:04:31.490 align:start position:0% together meaning that it's impossible to create<00:04:29.580> an<00:04:29.759> event<00:04:29.940> where<00:04:30.180> you<00:04:30.419> in<00:04:30.600> you<00:04:31.199> invite 00:04:31.490 --> 00:04:31.500 align:start position:0% create an event where you in you invite 00:04:31.500 --> 00:04:33.170 align:start position:0% create an event where you in you invite your<00:04:32.160> Facebook<00:04:32.280> friends<00:04:32.639> your<00:04:32.940> Twitter 00:04:33.170 --> 00:04:33.180 align:start position:0% your Facebook friends your Twitter 00:04:33.180 --> 00:04:34.850 align:start position:0% your Facebook friends your Twitter friends<00:04:33.479> your<00:04:33.660> LinkedIn<00:04:34.020> friends<00:04:34.199> because 00:04:34.850 --> 00:04:34.860 align:start position:0% friends your LinkedIn friends because 00:04:34.860 --> 00:04:36.830 align:start position:0% friends your LinkedIn friends because they<00:04:35.160> are<00:04:35.340> actually<00:04:35.460> competing<00:04:36.240> on<00:04:36.720> your 00:04:36.830 --> 00:04:36.840 align:start position:0% they are actually competing on your 00:04:36.840 --> 00:04:38.570 align:start position:0% they are actually competing on your accounts<00:04:37.320> like<00:04:37.440> it's<00:04:37.740> not<00:04:37.860> your<00:04:38.040> accounts 00:04:38.570 --> 00:04:38.580 align:start position:0% accounts like it's not your accounts 00:04:38.580 --> 00:04:40.370 align:start position:0% accounts like it's not your accounts it's<00:04:38.699> theirs<00:04:39.060> it's<00:04:39.300> their<00:04:39.540> asset<00:04:39.960> that's<00:04:40.199> how 00:04:40.370 --> 00:04:40.380 align:start position:0% it's theirs it's their asset that's how 00:04:40.380 --> 00:04:42.290 align:start position:0% it's theirs it's their asset that's how they<00:04:40.560> make<00:04:40.740> money<00:04:40.979> they<00:04:41.460> want<00:04:41.639> you<00:04:41.759> to<00:04:41.940> put<00:04:42.120> as 00:04:42.290 --> 00:04:42.300 align:start position:0% they make money they want you to put as 00:04:42.300 --> 00:04:45.950 align:start position:0% they make money they want you to put as much<00:04:42.479> data<00:04:42.840> on<00:04:42.960> it<00:04:43.139> as<00:04:43.680> possible<00:04:44.040> and<00:04:45.479> so 00:04:45.950 --> 00:04:45.960 align:start position:0% much data on it as possible and so 00:04:45.960 --> 00:04:47.510 align:start position:0% much data on it as possible and so that's<00:04:46.080> not<00:04:46.259> your<00:04:46.440> Idols<00:04:46.919> you<00:04:46.979> cannot<00:04:47.280> fully 00:04:47.510 --> 00:04:47.520 align:start position:0% that's not your Idols you cannot fully 00:04:47.520 --> 00:04:49.909 align:start position:0% that's not your Idols you cannot fully leverage<00:04:47.759> it<00:04:48.000> and<00:04:48.720> on<00:04:49.320> the<00:04:49.440> other<00:04:49.500> side<00:04:49.680> we 00:04:49.909 --> 00:04:49.919 align:start position:0% leverage it and on the other side we 00:04:49.919 --> 00:04:52.129 align:start position:0% leverage it and on the other side we have<00:04:50.100> the<00:04:50.160> Self<00:04:50.340> Storage<00:04:50.580> accounts<00:04:51.180> data<00:04:51.960> for 00:04:52.129 --> 00:04:52.139 align:start position:0% have the Self Storage accounts data for 00:04:52.139 --> 00:04:55.610 align:start position:0% have the Self Storage accounts data for instance<00:04:52.380> uh<00:04:53.040> ethern<00:04:53.460> wallet<00:04:54.259> it's<00:04:55.259> owned<00:04:55.560> by 00:04:55.610 --> 00:04:55.620 align:start position:0% instance uh ethern wallet it's owned by 00:04:55.620 --> 00:04:57.170 align:start position:0% instance uh ethern wallet it's owned by a<00:04:55.740> private<00:04:55.979> key<00:04:56.160> meaning<00:04:56.460> that<00:04:56.699> the<00:04:56.820> private 00:04:57.170 --> 00:04:57.180 align:start position:0% a private key meaning that the private 00:04:57.180 --> 00:05:00.050 align:start position:0% a private key meaning that the private key<00:04:57.500> is<00:04:58.500> the<00:04:58.860> thing<00:04:58.979> that<00:04:59.220> you<00:04:59.699> must<00:04:59.759> have<00:04:59.940> the 00:05:00.050 --> 00:05:00.060 align:start position:0% key is the thing that you must have the 00:05:00.060 --> 00:05:01.550 align:start position:0% key is the thing that you must have the priority<00:05:00.360> to<00:05:00.600> do<00:05:00.780> anything<00:05:01.020> with<00:05:01.320> these 00:05:01.550 --> 00:05:01.560 align:start position:0% priority to do anything with these 00:05:01.560 --> 00:05:03.469 align:start position:0% priority to do anything with these accounts<00:05:01.979> what's<00:05:02.520> amazing<00:05:02.880> too<00:05:03.060> is<00:05:03.180> that<00:05:03.300> is 00:05:03.469 --> 00:05:03.479 align:start position:0% accounts what's amazing too is that is 00:05:03.479 --> 00:05:06.710 align:start position:0% accounts what's amazing too is that is permissionless<00:05:04.220> anyone<00:05:05.220> can<00:05:05.460> create<00:05:05.699> a<00:05:06.419> self 00:05:06.710 --> 00:05:06.720 align:start position:0% permissionless anyone can create a self 00:05:06.720 --> 00:05:08.450 align:start position:0% permissionless anyone can create a self surrender<00:05:07.080> accounts<00:05:07.560> without<00:05:07.979> asking 00:05:08.450 --> 00:05:08.460 align:start position:0% surrender accounts without asking 00:05:08.460 --> 00:05:10.730 align:start position:0% surrender accounts without asking permission<00:05:08.759> to<00:05:08.940> anyone<00:05:09.300> so<00:05:09.960> okay<00:05:10.199> that's 00:05:10.730 --> 00:05:10.740 align:start position:0% permission to anyone so okay that's 00:05:10.740 --> 00:05:13.249 align:start position:0% permission to anyone so okay that's great<00:05:10.979> what<00:05:11.460> I<00:05:11.699> can<00:05:11.820> do<00:05:11.940> with<00:05:12.060> it<00:05:12.240> of<00:05:12.479> course<00:05:12.660> I 00:05:13.249 --> 00:05:13.259 align:start position:0% great what I can do with it of course I 00:05:13.259 --> 00:05:15.170 align:start position:0% great what I can do with it of course I can<00:05:13.380> start<00:05:13.560> adding<00:05:13.919> some<00:05:14.100> ether<00:05:14.460> to<00:05:14.699> it<00:05:14.940> for 00:05:15.170 --> 00:05:15.180 align:start position:0% can start adding some ether to it for 00:05:15.180 --> 00:05:17.390 align:start position:0% can start adding some ether to it for instance<00:05:15.360> and<00:05:15.600> I<00:05:15.780> can<00:05:15.900> trade<00:05:16.139> off<00:05:16.259> uni<00:05:16.680> swap<00:05:16.919> it 00:05:17.390 --> 00:05:17.400 align:start position:0% instance and I can trade off uni swap it 00:05:17.400 --> 00:05:19.430 align:start position:0% instance and I can trade off uni swap it starts<00:05:17.759> also<00:05:17.940> to<00:05:18.120> build<00:05:18.300> my<00:05:18.479> identity<00:05:18.900> now<00:05:19.259> I 00:05:19.430 --> 00:05:19.440 align:start position:0% starts also to build my identity now I 00:05:19.440 --> 00:05:21.650 align:start position:0% starts also to build my identity now I have<00:05:19.560> some<00:05:19.740> financial<00:05:20.240> data<00:05:21.240> on<00:05:21.360> my<00:05:21.479> account 00:05:21.650 --> 00:05:21.660 align:start position:0% have some financial data on my account 00:05:21.660 --> 00:05:25.189 align:start position:0% have some financial data on my account that<00:05:22.320> is<00:05:22.440> mine<00:05:22.680> I<00:05:23.220> can<00:05:23.340> buy<00:05:23.520> ens<00:05:24.060> name<00:05:24.300> I<00:05:25.020> can 00:05:25.189 --> 00:05:25.199 align:start position:0% that is mine I can buy ens name I can 00:05:25.199 --> 00:05:28.969 align:start position:0% that is mine I can buy ens name I can buy<00:05:25.620> a<00:05:25.800> nft<00:05:26.220> and<00:05:27.060> I<00:05:27.240> interact<00:05:27.660> on<00:05:27.900> social<00:05:28.139> on 00:05:28.969 --> 00:05:28.979 align:start position:0% buy a nft and I interact on social on 00:05:28.979 --> 00:05:31.550 align:start position:0% buy a nft and I interact on social on social<00:05:29.160> medias<00:05:29.520> on<00:05:29.880> chain<00:05:30.180> so<00:05:30.900> by<00:05:31.199> doing<00:05:31.320> this 00:05:31.550 --> 00:05:31.560 align:start position:0% social medias on chain so by doing this 00:05:31.560 --> 00:05:33.950 align:start position:0% social medias on chain so by doing this a<00:05:31.740> bit<00:05:31.919> like<00:05:32.039> on<00:05:32.220> Twitter<00:05:32.400> I<00:05:33.000> built<00:05:33.419> my<00:05:33.720> end 00:05:33.950 --> 00:05:33.960 align:start position:0% a bit like on Twitter I built my end 00:05:33.960 --> 00:05:36.770 align:start position:0% a bit like on Twitter I built my end entity<00:05:34.320> but<00:05:35.039> this<00:05:35.280> time<00:05:35.460> this<00:05:35.699> identity<00:05:36.120> is 00:05:36.770 --> 00:05:36.780 align:start position:0% entity but this time this identity is 00:05:36.780 --> 00:05:39.650 align:start position:0% entity but this time this identity is mine<00:05:37.080> the<00:05:37.680> data<00:05:37.979> I<00:05:38.039> need<00:05:38.220> is<00:05:38.880> mine<00:05:39.120> and<00:05:39.539> it's 00:05:39.650 --> 00:05:39.660 align:start position:0% mine the data I need is mine and it's 00:05:39.660 --> 00:05:42.050 align:start position:0% mine the data I need is mine and it's controlled<00:05:40.020> by<00:05:40.139> my<00:05:40.380> private<00:05:40.919> Key<00:05:41.039> by<00:05:41.820> the<00:05:41.940> way 00:05:42.050 --> 00:05:42.060 align:start position:0% controlled by my private Key by the way 00:05:42.060 --> 00:05:44.930 align:start position:0% controlled by my private Key by the way by<00:05:42.419> by<00:05:42.479> using<00:05:43.440> ens<00:05:43.800> I<00:05:43.979> also<00:05:44.160> create<00:05:44.400> this<00:05:44.639> as<00:05:44.759> a 00:05:44.930 --> 00:05:44.940 align:start position:0% by by using ens I also create this as a 00:05:44.940 --> 00:05:47.390 align:start position:0% by by using ens I also create this as a public<00:05:45.060> accountant<00:05:45.419> numbers<00:05:45.840> so<00:05:46.740> very 00:05:47.390 --> 00:05:47.400 align:start position:0% public accountant numbers so very 00:05:47.400 --> 00:05:48.469 align:start position:0% public accountant numbers so very interesting 00:05:48.469 --> 00:05:48.479 align:start position:0% interesting 00:05:48.479 --> 00:05:50.810 align:start position:0% interesting so<00:05:49.020> that's<00:05:49.320> one<00:05:49.560> part<00:05:49.740> but<00:05:50.160> actually<00:05:50.340> steps 00:05:50.810 --> 00:05:50.820 align:start position:0% so that's one part but actually steps 00:05:50.820 --> 00:05:52.969 align:start position:0% so that's one part but actually steps around<00:05:51.000> accounts<00:05:51.720> are<00:05:52.139> more<00:05:52.680> interesting 00:05:52.969 --> 00:05:52.979 align:start position:0% around accounts are more interesting 00:05:52.979 --> 00:05:54.770 align:start position:0% around accounts are more interesting than<00:05:53.160> blockchain<00:05:53.580> they<00:05:53.820> are<00:05:54.060> bigger<00:05:54.600> than 00:05:54.770 --> 00:05:54.780 align:start position:0% than blockchain they are bigger than 00:05:54.780 --> 00:05:57.110 align:start position:0% than blockchain they are bigger than that<00:05:54.960> because<00:05:55.680> okay<00:05:56.460> you<00:05:56.759> can<00:05:56.880> use<00:05:56.940> the 00:05:57.110 --> 00:05:57.120 align:start position:0% that because okay you can use the 00:05:57.120 --> 00:05:58.850 align:start position:0% that because okay you can use the private<00:05:57.360> key<00:05:57.479> to<00:05:57.660> send<00:05:57.780> transaction<00:05:58.139> to<00:05:58.680> to 00:05:58.850 --> 00:05:58.860 align:start position:0% private key to send transaction to to 00:05:58.860 --> 00:06:00.650 align:start position:0% private key to send transaction to to use<00:05:58.979> different<00:05:59.220> applications<00:05:59.880> but<00:06:00.360> you<00:06:00.539> can 00:06:00.650 --> 00:06:00.660 align:start position:0% use different applications but you can 00:06:00.660 --> 00:06:02.990 align:start position:0% use different applications but you can you<00:06:00.960> also<00:06:01.259> use<00:06:01.380> them<00:06:01.620> to<00:06:01.860> log<00:06:02.100> in<00:06:02.280> on<00:06:02.460> into<00:06:02.820> your 00:06:02.990 --> 00:06:03.000 align:start position:0% you also use them to log in on into your 00:06:03.000 --> 00:06:05.390 align:start position:0% you also use them to log in on into your app<00:06:03.180> I<00:06:03.780> think<00:06:03.900> you<00:06:04.080> know<00:06:04.320> using<00:06:04.740> snapshot<00:06:05.160> or 00:06:05.390 --> 00:06:05.400 align:start position:0% app I think you know using snapshot or 00:06:05.400 --> 00:06:07.670 align:start position:0% app I think you know using snapshot or other<00:06:05.520> applications<00:06:05.940> that<00:06:06.780> now<00:06:07.080> you<00:06:07.560> have 00:06:07.670 --> 00:06:07.680 align:start position:0% other applications that now you have 00:06:07.680 --> 00:06:10.430 align:start position:0% other applications that now you have login<00:06:07.860> system<00:06:08.360> stems<00:06:09.360> based<00:06:09.900> on<00:06:10.020> wallets 00:06:10.430 --> 00:06:10.440 align:start position:0% login system stems based on wallets 00:06:10.440 --> 00:06:13.010 align:start position:0% login system stems based on wallets that's<00:06:10.800> called<00:06:10.979> sign<00:06:11.280> in<00:06:11.460> with<00:06:11.639> ethereum<00:06:12.180> and 00:06:13.010 --> 00:06:13.020 align:start position:0% that's called sign in with ethereum and 00:06:13.020 --> 00:06:14.990 align:start position:0% that's called sign in with ethereum and you<00:06:13.139> can<00:06:13.259> log<00:06:13.440> into<00:06:13.620> an<00:06:13.919> app<00:06:14.160> traditional<00:06:14.759> app 00:06:14.990 --> 00:06:15.000 align:start position:0% you can log into an app traditional app 00:06:15.000 --> 00:06:17.330 align:start position:0% you can log into an app traditional app but<00:06:15.600> instead<00:06:15.960> of<00:06:16.139> an<00:06:16.259> email<00:06:16.440> and<00:06:16.740> password<00:06:16.979> you 00:06:17.330 --> 00:06:17.340 align:start position:0% but instead of an email and password you 00:06:17.340 --> 00:06:21.050 align:start position:0% but instead of an email and password you log<00:06:17.520> in<00:06:17.699> with<00:06:17.820> your<00:06:17.940> wallet<00:06:18.240> so<00:06:18.840> they<00:06:19.320> also<00:06:20.160> uh 00:06:21.050 --> 00:06:21.060 align:start position:0% log in with your wallet so they also uh 00:06:21.060 --> 00:06:23.150 align:start position:0% log in with your wallet so they also uh awareness<00:06:21.660> also<00:06:22.080> an<00:06:22.199> identities<00:06:22.500> accounts 00:06:23.150 --> 00:06:23.160 align:start position:0% awareness also an identities accounts 00:06:23.160 --> 00:06:26.090 align:start position:0% awareness also an identities accounts are<00:06:23.400> better<00:06:24.060> than<00:06:24.780> than<00:06:25.100> traditional 00:06:26.090 --> 00:06:26.100 align:start position:0% are better than than traditional 00:06:26.100 --> 00:06:29.210 align:start position:0% are better than than traditional accounts<00:06:27.000> even<00:06:27.180> at<00:06:27.479> work<00:06:27.660> to<00:06:27.900> stuff<00:06:28.139> so<00:06:28.560> okay<00:06:28.860> I 00:06:29.210 --> 00:06:29.220 align:start position:0% accounts even at work to stuff so okay I 00:06:29.220 --> 00:06:31.969 align:start position:0% accounts even at work to stuff so okay I can<00:06:29.280> connect<00:06:29.460> to<00:06:29.699> snapshot<00:06:30.199> with<00:06:31.199> my<00:06:31.440> ethereum 00:06:31.969 --> 00:06:31.979 align:start position:0% can connect to snapshot with my ethereum 00:06:31.979 --> 00:06:33.890 align:start position:0% can connect to snapshot with my ethereum wallet<00:06:32.340> I<00:06:32.699> send<00:06:32.940> a<00:06:33.120> message<00:06:33.240> they<00:06:33.539> say<00:06:33.720> okay 00:06:33.890 --> 00:06:33.900 align:start position:0% wallet I send a message they say okay 00:06:33.900 --> 00:06:36.290 align:start position:0% wallet I send a message they say okay you're<00:06:34.380> logged<00:06:34.740> in<00:06:34.860> and<00:06:35.580> what's<00:06:35.819> great<00:06:36.120> is 00:06:36.290 --> 00:06:36.300 align:start position:0% you're logged in and what's great is 00:06:36.300 --> 00:06:38.689 align:start position:0% you're logged in and what's great is that<00:06:36.479> you<00:06:37.020> bring<00:06:37.259> your<00:06:37.560> whole<00:06:37.740> identity<00:06:38.220> to 00:06:38.689 --> 00:06:38.699 align:start position:0% that you bring your whole identity to 00:06:38.699 --> 00:06:40.969 align:start position:0% that you bring your whole identity to the<00:06:38.819> app<00:06:39.000> so<00:06:39.419> what<00:06:39.720> does<00:06:39.900> Snapshot<00:06:40.380> is<00:06:40.560> okay 00:06:40.969 --> 00:06:40.979 align:start position:0% the app so what does Snapshot is okay 00:06:40.979 --> 00:06:42.890 align:start position:0% the app so what does Snapshot is okay you're<00:06:41.160> logged<00:06:41.460> in<00:06:41.520> as<00:06:41.699> data<00:06:42.000> entities<00:06:42.360> oh<00:06:42.660> you 00:06:42.890 --> 00:06:42.900 align:start position:0% you're logged in as data entities oh you 00:06:42.900 --> 00:06:44.510 align:start position:0% you're logged in as data entities oh you have<00:06:43.020> some<00:06:43.139> other<00:06:43.380> or<00:06:43.800> you<00:06:43.979> have<00:06:44.039> some<00:06:44.220> uni 00:06:44.510 --> 00:06:44.520 align:start position:0% have some other or you have some uni 00:06:44.520 --> 00:06:46.670 align:start position:0% have some other or you have some uni swap<00:06:44.759> tokens<00:06:45.360> you<00:06:46.020> can<00:06:46.080> vote<00:06:46.259> on<00:06:46.500> my 00:06:46.670 --> 00:06:46.680 align:start position:0% swap tokens you can vote on my 00:06:46.680 --> 00:06:49.309 align:start position:0% swap tokens you can vote on my governance<00:06:47.039> with<00:06:47.220> it<00:06:47.400> so<00:06:48.180> that's<00:06:48.900> where<00:06:49.139> you 00:06:49.309 --> 00:06:49.319 align:start position:0% governance with it so that's where you 00:06:49.319 --> 00:06:51.110 align:start position:0% governance with it so that's where you cannot<00:06:49.680> you<00:06:49.979> you<00:06:50.160> start<00:06:50.460> to<00:06:50.639> see<00:06:50.759> the 00:06:51.110 --> 00:06:51.120 align:start position:0% cannot you you start to see the 00:06:51.120 --> 00:06:53.090 align:start position:0% cannot you you start to see the sovereignty<00:06:51.900> that<00:06:52.080> we<00:06:52.259> have<00:06:52.380> over<00:06:52.620> our 00:06:53.090 --> 00:06:53.100 align:start position:0% sovereignty that we have over our 00:06:53.100 --> 00:06:55.370 align:start position:0% sovereignty that we have over our identities<00:06:53.580> with<00:06:53.880> wallets<00:06:54.300> that<00:06:54.840> I<00:06:55.080> can<00:06:55.199> bring 00:06:55.370 --> 00:06:55.380 align:start position:0% identities with wallets that I can bring 00:06:55.380 --> 00:06:57.890 align:start position:0% identities with wallets that I can bring my<00:06:55.620> identity<00:06:56.039> to<00:06:56.580> the<00:06:56.759> app 00:06:57.890 --> 00:06:57.900 align:start position:0% my identity to the app 00:06:57.900 --> 00:07:00.590 align:start position:0% my identity to the app but<00:06:58.680> that's<00:06:59.100> something<00:06:59.340> that<00:06:59.699> is<00:06:59.940> less<00:07:00.300> cool 00:07:00.590 --> 00:07:00.600 align:start position:0% but that's something that is less cool 00:07:00.600 --> 00:07:02.510 align:start position:0% but that's something that is less cool because<00:07:01.020> it's<00:07:01.319> the<00:07:01.500> beginning<00:07:01.680> we<00:07:02.039> immature 00:07:02.510 --> 00:07:02.520 align:start position:0% because it's the beginning we immature 00:07:02.520 --> 00:07:04.490 align:start position:0% because it's the beginning we immature is<00:07:02.759> the<00:07:02.880> fact<00:07:03.000> that<00:07:03.180> when<00:07:03.600> I<00:07:03.780> do<00:07:03.960> this<00:07:04.139> I 00:07:04.490 --> 00:07:04.500 align:start position:0% is the fact that when I do this I 00:07:04.500 --> 00:07:06.409 align:start position:0% is the fact that when I do this I actually<00:07:04.680> share<00:07:04.979> everything<00:07:05.580> all<00:07:06.240> my 00:07:06.409 --> 00:07:06.419 align:start position:0% actually share everything all my 00:07:06.419 --> 00:07:08.210 align:start position:0% actually share everything all my identity<00:07:06.840> let's<00:07:07.560> say<00:07:07.740> that<00:07:07.860> I<00:07:07.979> have<00:07:08.100> An 00:07:08.210 --> 00:07:08.220 align:start position:0% identity let's say that I have An 00:07:08.220 --> 00:07:10.249 align:start position:0% identity let's say that I have An Occurrence<00:07:08.639> my<00:07:09.300> menu<00:07:09.539> account<00:07:09.720> that<00:07:10.080> is 00:07:10.249 --> 00:07:10.259 align:start position:0% Occurrence my menu account that is 00:07:10.259 --> 00:07:13.309 align:start position:0% Occurrence my menu account that is private<00:07:10.560> with<00:07:10.919> a<00:07:11.100> lot<00:07:11.160> of<00:07:11.340> data<00:07:11.759> my<00:07:12.120> erc20s<00:07:13.080> my 00:07:13.309 --> 00:07:13.319 align:start position:0% private with a lot of data my erc20s my 00:07:13.319 --> 00:07:16.550 align:start position:0% private with a lot of data my erc20s my assets<00:07:13.680> my<00:07:13.919> nfts<00:07:14.580> so<00:07:14.880> many<00:07:15.000> things<00:07:15.240> and<00:07:16.020> that<00:07:16.199> I 00:07:16.550 --> 00:07:16.560 align:start position:0% assets my nfts so many things and that I 00:07:16.560 --> 00:07:18.469 align:start position:0% assets my nfts so many things and that I want<00:07:16.740> to<00:07:16.860> access<00:07:17.340> an<00:07:17.759> app 00:07:18.469 --> 00:07:18.479 align:start position:0% want to access an app 00:07:18.479 --> 00:07:21.469 align:start position:0% want to access an app to<00:07:19.319> let's<00:07:19.740> say<00:07:19.919> that<00:07:20.220> are<00:07:20.400> created<00:07:20.639> by<00:07:21.120> crypto 00:07:21.469 --> 00:07:21.479 align:start position:0% to let's say that are created by crypto 00:07:21.479 --> 00:07:23.510 align:start position:0% to let's say that are created by crypto pen<00:07:21.660> Corners<00:07:22.020> because<00:07:22.199> I<00:07:22.440> just<00:07:22.620> want<00:07:22.860> to<00:07:23.039> be 00:07:23.510 --> 00:07:23.520 align:start position:0% pen Corners because I just want to be 00:07:23.520 --> 00:07:25.550 align:start position:0% pen Corners because I just want to be part<00:07:23.699> of<00:07:23.819> a<00:07:23.940> cool<00:07:24.060> community<00:07:24.360> and<00:07:24.900> access<00:07:25.259> the 00:07:25.550 --> 00:07:25.560 align:start position:0% part of a cool community and access the 00:07:25.560 --> 00:07:27.710 align:start position:0% part of a cool community and access the chat<00:07:25.740> app<00:07:25.919> using<00:07:26.400> sign<00:07:26.580> in<00:07:26.759> with<00:07:26.940> ethereum<00:07:27.360> I 00:07:27.710 --> 00:07:27.720 align:start position:0% chat app using sign in with ethereum I 00:07:27.720 --> 00:07:29.990 align:start position:0% chat app using sign in with ethereum I would<00:07:27.840> have<00:07:28.080> to<00:07:28.680> connect<00:07:29.160> with<00:07:29.699> my<00:07:29.880> main 00:07:29.990 --> 00:07:30.000 align:start position:0% would have to connect with my main 00:07:30.000 --> 00:07:31.670 align:start position:0% would have to connect with my main wallet<00:07:30.419> and<00:07:30.599> give<00:07:30.780> so<00:07:31.080> much<00:07:31.199> data<00:07:31.560> about 00:07:31.670 --> 00:07:31.680 align:start position:0% wallet and give so much data about 00:07:31.680 --> 00:07:33.950 align:start position:0% wallet and give so much data about myself<00:07:31.979> here<00:07:32.520> what<00:07:32.759> we<00:07:32.940> saw<00:07:33.120> is<00:07:33.240> that 00:07:33.950 --> 00:07:33.960 align:start position:0% myself here what we saw is that 00:07:33.960 --> 00:07:36.529 align:start position:0% myself here what we saw is that at<00:07:34.860> every<00:07:35.160> time<00:07:35.340> that<00:07:35.460> I<00:07:35.699> connect<00:07:35.819> to<00:07:36.300> an<00:07:36.419> app 00:07:36.529 --> 00:07:36.539 align:start position:0% at every time that I connect to an app 00:07:36.539 --> 00:07:37.969 align:start position:0% at every time that I connect to an app with<00:07:36.780> learning<00:07:37.080> with<00:07:37.199> them<00:07:37.380> I<00:07:37.560> bring<00:07:37.680> all<00:07:37.800> my 00:07:37.969 --> 00:07:37.979 align:start position:0% with learning with them I bring all my 00:07:37.979 --> 00:07:40.309 align:start position:0% with learning with them I bring all my data<00:07:38.759> but<00:07:39.240> again<00:07:39.419> the<00:07:39.780> sales<00:07:39.900> training 00:07:40.309 --> 00:07:40.319 align:start position:0% data but again the sales training 00:07:40.319 --> 00:07:41.749 align:start position:0% data but again the sales training accounts<00:07:40.680> are<00:07:40.800> amazing<00:07:41.160> they're<00:07:41.400> controlled 00:07:41.749 --> 00:07:41.759 align:start position:0% accounts are amazing they're controlled 00:07:41.759 --> 00:07:43.189 align:start position:0% accounts are amazing they're controlled by<00:07:41.880> a<00:07:42.000> private<00:07:42.240> key<00:07:42.419> and<00:07:42.599> you<00:07:42.720> can<00:07:42.840> do<00:07:43.020> even 00:07:43.189 --> 00:07:43.199 align:start position:0% by a private key and you can do even 00:07:43.199 --> 00:07:44.990 align:start position:0% by a private key and you can do even more<00:07:43.440> you<00:07:43.740> can<00:07:43.860> do<00:07:43.979> zero<00:07:44.460> knowledge<00:07:44.639> proofs 00:07:44.990 --> 00:07:45.000 align:start position:0% more you can do zero knowledge proofs 00:07:45.000 --> 00:07:48.050 align:start position:0% more you can do zero knowledge proofs and<00:07:45.840> with<00:07:46.440> this<00:07:46.620> account<00:07:46.860> you<00:07:47.520> can<00:07:47.639> basically 00:07:48.050 --> 00:07:48.060 align:start position:0% and with this account you can basically 00:07:48.060 --> 00:07:49.730 align:start position:0% and with this account you can basically select<00:07:48.479> a<00:07:48.599> piece<00:07:48.780> of<00:07:48.900> data<00:07:49.199> that<00:07:49.380> you<00:07:49.500> want<00:07:49.620> to 00:07:49.730 --> 00:07:49.740 align:start position:0% select a piece of data that you want to 00:07:49.740 --> 00:07:52.370 align:start position:0% select a piece of data that you want to share<00:07:49.979> and<00:07:50.940> and<00:07:51.180> that's<00:07:51.419> it<00:07:51.660> so 00:07:52.370 --> 00:07:52.380 align:start position:0% share and and that's it so 00:07:52.380 --> 00:07:54.290 align:start position:0% share and and that's it so again<00:07:52.860> it's<00:07:53.160> super<00:07:53.460> powerful<00:07:53.819> and<00:07:54.120> that's 00:07:54.290 --> 00:07:54.300 align:start position:0% again it's super powerful and that's 00:07:54.300 --> 00:07:55.450 align:start position:0% again it's super powerful and that's everything 00:07:55.450 --> 00:07:55.460 align:start position:0% everything 00:07:55.460 --> 00:07:59.029 align:start position:0% everything that's<00:07:56.460> that's<00:07:56.639> what<00:07:56.940> badges<00:07:57.419> are<00:07:57.780> about<00:07:58.199> it 00:07:59.029 --> 00:07:59.039 align:start position:0% that's that's what badges are about it 00:07:59.039 --> 00:08:01.309 align:start position:0% that's that's what badges are about it allows<00:07:59.340> you<00:07:59.460> to<00:07:59.940> selectively<00:08:00.539> reveal<00:08:01.080> some 00:08:01.309 --> 00:08:01.319 align:start position:0% allows you to selectively reveal some 00:08:01.319 --> 00:08:03.589 align:start position:0% allows you to selectively reveal some part<00:08:01.560> of<00:08:01.800> your<00:08:02.039> Sovereign<00:08:02.580> data 00:08:03.589 --> 00:08:03.599 align:start position:0% part of your Sovereign data 00:08:03.599 --> 00:08:06.350 align:start position:0% part of your Sovereign data so<00:08:04.259> again<00:08:04.979> what<00:08:05.400> they<00:08:05.580> are<00:08:05.759> they<00:08:06.240> are 00:08:06.350 --> 00:08:06.360 align:start position:0% so again what they are they are 00:08:06.360 --> 00:08:08.629 align:start position:0% so again what they are they are tokenized<00:08:06.840> at<00:08:07.020> attestation<00:08:07.560> meaning<00:08:08.280> that 00:08:08.629 --> 00:08:08.639 align:start position:0% tokenized at attestation meaning that 00:08:08.639 --> 00:08:13.129 align:start position:0% tokenized at attestation meaning that when<00:08:09.060> a<00:08:09.660> wallet<00:08:10.380> has<00:08:10.880> this<00:08:11.880> SBT<00:08:12.539> this 00:08:13.129 --> 00:08:13.139 align:start position:0% when a wallet has this SBT this 00:08:13.139 --> 00:08:15.950 align:start position:0% when a wallet has this SBT this non-trustable<00:08:13.680> token<00:08:14.160> it<00:08:14.759> means<00:08:15.120> that<00:08:15.360> it 00:08:15.950 --> 00:08:15.960 align:start position:0% non-trustable token it means that it 00:08:15.960 --> 00:08:17.629 align:start position:0% non-trustable token it means that it means<00:08:16.080> something<00:08:16.319> about<00:08:16.560> the<00:08:16.740> identity<00:08:17.160> it's 00:08:17.629 --> 00:08:17.639 align:start position:0% means something about the identity it's 00:08:17.639 --> 00:08:19.550 align:start position:0% means something about the identity it's an<00:08:18.000> attitation<00:08:18.539> like<00:08:18.780> they<00:08:19.020> have<00:08:19.199> a<00:08:19.319> crypto 00:08:19.550 --> 00:08:19.560 align:start position:0% an attitation like they have a crypto 00:08:19.560 --> 00:08:21.710 align:start position:0% an attitation like they have a crypto plane<00:08:19.800> the<00:08:20.039> Virgin<00:08:20.160> Island<00:08:20.460> governance<00:08:21.120> they 00:08:21.710 --> 00:08:21.720 align:start position:0% plane the Virgin Island governance they 00:08:21.720 --> 00:08:23.029 align:start position:0% plane the Virgin Island governance they have<00:08:21.900> a<00:08:22.080> certain<00:08:22.440> number<00:08:22.680> of<00:08:22.860> Twitter 00:08:23.029 --> 00:08:23.039 align:start position:0% have a certain number of Twitter 00:08:23.039 --> 00:08:25.129 align:start position:0% have a certain number of Twitter followers<00:08:23.460> stuff<00:08:23.759> like<00:08:23.879> that 00:08:25.129 --> 00:08:25.139 align:start position:0% followers stuff like that 00:08:25.139 --> 00:08:28.850 align:start position:0% followers stuff like that it's<00:08:25.680> DK<00:08:26.160> because<00:08:26.400> it's<00:08:26.759> it's<00:08:27.240> minted<00:08:27.960> by<00:08:28.259> a<00:08:28.440> ZK 00:08:28.850 --> 00:08:28.860 align:start position:0% it's DK because it's it's minted by a ZK 00:08:28.860 --> 00:08:32.029 align:start position:0% it's DK because it's it's minted by a ZK attester<00:08:29.280> this<00:08:30.000> is<00:08:30.180> a<00:08:30.660> smart<00:08:30.960> contract<00:08:31.319> that 00:08:32.029 --> 00:08:32.039 align:start position:0% attester this is a smart contract that 00:08:32.039 --> 00:08:34.310 align:start position:0% attester this is a smart contract that accepts<00:08:32.399> zero<00:08:32.880> knowledge<00:08:33.120> proofs<00:08:33.479> and<00:08:34.080> okay 00:08:34.310 --> 00:08:34.320 align:start position:0% accepts zero knowledge proofs and okay 00:08:34.320 --> 00:08:36.290 align:start position:0% accepts zero knowledge proofs and okay you<00:08:34.919> brought<00:08:35.159> me<00:08:35.339> the<00:08:35.520> knowledge<00:08:35.880> proof<00:08:36.180> that 00:08:36.290 --> 00:08:36.300 align:start position:0% you brought me the knowledge proof that 00:08:36.300 --> 00:08:37.850 align:start position:0% you brought me the knowledge proof that you<00:08:36.419> have<00:08:36.539> a<00:08:36.659> crypto<00:08:36.899> bank<00:08:37.080> now<00:08:37.380> I<00:08:37.500> give<00:08:37.740> you 00:08:37.850 --> 00:08:37.860 align:start position:0% you have a crypto bank now I give you 00:08:37.860 --> 00:08:39.409 align:start position:0% you have a crypto bank now I give you the<00:08:38.279> badge<00:08:38.580> that<00:08:38.640> you<00:08:38.760> have<00:08:38.880> a<00:08:38.940> crypto<00:08:39.180> pack 00:08:39.409 --> 00:08:39.419 align:start position:0% the badge that you have a crypto pack 00:08:39.419 --> 00:08:43.370 align:start position:0% the badge that you have a crypto pack and<00:08:40.200> it's<00:08:40.560> on<00:08:40.800> evm<00:08:41.399> chance<00:08:41.580> uh<00:08:42.539> it's<00:08:42.899> uh 00:08:43.370 --> 00:08:43.380 align:start position:0% and it's on evm chance uh it's uh 00:08:43.380 --> 00:08:45.769 align:start position:0% and it's on evm chance uh it's uh deployed<00:08:44.159> currently<00:08:44.820> on<00:08:44.940> polygon<00:08:45.420> but<00:08:45.600> we 00:08:45.769 --> 00:08:45.779 align:start position:0% deployed currently on polygon but we 00:08:45.779 --> 00:08:47.570 align:start position:0% deployed currently on polygon but we plan<00:08:45.959> to<00:08:46.140> go<00:08:46.320> everywhere<00:08:46.620> especially<00:08:47.220> on<00:08:47.459> on 00:08:47.570 --> 00:08:47.580 align:start position:0% plan to go everywhere especially on on 00:08:47.580 --> 00:08:50.509 align:start position:0% plan to go everywhere especially on on layer<00:08:48.000> 2<00:08:48.120> of<00:08:48.360> course<00:08:48.839> now<00:08:49.380> a<00:08:49.800> small<00:08:50.279> thing 00:08:50.509 --> 00:08:50.519 align:start position:0% layer 2 of course now a small thing 00:08:50.519 --> 00:08:52.910 align:start position:0% layer 2 of course now a small thing about<00:08:50.700> badges<00:08:51.300> that<00:08:51.540> small<00:08:52.140> Nuance<00:08:52.500> that's 00:08:52.910 --> 00:08:52.920 align:start position:0% about badges that small Nuance that's 00:08:52.920 --> 00:08:55.009 align:start position:0% about badges that small Nuance that's not<00:08:53.100> very<00:08:53.339> important<00:08:53.700> but<00:08:53.940> still<00:08:54.120> these<00:08:54.899> are 00:08:55.009 --> 00:08:55.019 align:start position:0% not very important but still these are 00:08:55.019 --> 00:08:59.150 align:start position:0% not very important but still these are ERC<00:08:55.560> 1155<00:08:56.360> each<00:08:57.360> batch<00:08:57.779> has<00:08:58.200> a<00:08:58.380> token<00:08:58.680> ID<00:08:58.800> in 00:08:59.150 --> 00:08:59.160 align:start position:0% ERC 1155 each batch has a token ID in 00:08:59.160 --> 00:09:01.130 align:start position:0% ERC 1155 each batch has a token ID in this<00:08:59.279> contract<00:08:59.640> and<00:09:00.360> that<00:09:00.480> means<00:09:00.720> that<00:09:00.839> each 00:09:01.130 --> 00:09:01.140 align:start position:0% this contract and that means that each 00:09:01.140 --> 00:09:04.490 align:start position:0% this contract and that means that each bus<00:09:01.440> each<00:09:01.980> badge<00:09:02.339> is<00:09:02.459> a<00:09:02.640> sort<00:09:02.760> of<00:09:03.140> erc20<00:09:04.140> it's 00:09:04.490 --> 00:09:04.500 align:start position:0% bus each badge is a sort of erc20 it's 00:09:04.500 --> 00:09:07.370 align:start position:0% bus each badge is a sort of erc20 it's not<00:09:04.680> really<00:09:04.860> a<00:09:05.040> NFC<00:09:05.339> so<00:09:05.580> erc20<00:09:06.120> and<00:09:06.959> for<00:09:07.200> the 00:09:07.370 --> 00:09:07.380 align:start position:0% not really a NFC so erc20 and for the 00:09:07.380 --> 00:09:09.110 align:start position:0% not really a NFC so erc20 and for the same<00:09:07.500> batch<00:09:07.740> you<00:09:08.459> can<00:09:08.580> have<00:09:08.760> different 00:09:09.110 --> 00:09:09.120 align:start position:0% same batch you can have different 00:09:09.120 --> 00:09:11.570 align:start position:0% same batch you can have different balances<00:09:09.779> so<00:09:10.500> we'll<00:09:10.620> see<00:09:10.860> that<00:09:10.980> later<00:09:11.100> why<00:09:11.459> is 00:09:11.570 --> 00:09:11.580 align:start position:0% balances so we'll see that later why is 00:09:11.580 --> 00:09:12.970 align:start position:0% balances so we'll see that later why is interesting<00:09:11.940> but 00:09:12.970 --> 00:09:12.980 align:start position:0% interesting but 00:09:12.980 --> 00:09:15.769 align:start position:0% interesting but you<00:09:13.980> have<00:09:14.160> a<00:09:14.760> value<00:09:14.940> of<00:09:15.180> the<00:09:15.300> attestation 00:09:15.769 --> 00:09:15.779 align:start position:0% you have a value of the attestation 00:09:15.779 --> 00:09:17.990 align:start position:0% you have a value of the attestation corresponding<00:09:16.740> to<00:09:16.920> the<00:09:17.220> balance<00:09:17.700> of<00:09:17.820> your 00:09:17.990 --> 00:09:18.000 align:start position:0% corresponding to the balance of your 00:09:18.000 --> 00:09:20.269 align:start position:0% corresponding to the balance of your badge<00:09:18.360> and<00:09:18.540> the<00:09:18.720> higher<00:09:19.080> balance<00:09:19.500> maybe<00:09:19.680> it 00:09:20.269 --> 00:09:20.279 align:start position:0% badge and the higher balance maybe it 00:09:20.279 --> 00:09:23.389 align:start position:0% badge and the higher balance maybe it means<00:09:20.519> that<00:09:20.640> you<00:09:21.300> have<00:09:21.899> more<00:09:22.560> followers<00:09:23.100> or 00:09:23.389 --> 00:09:23.399 align:start position:0% means that you have more followers or 00:09:23.399 --> 00:09:25.730 align:start position:0% means that you have more followers or your<00:09:23.720> batch<00:09:24.720> means<00:09:25.080> more<00:09:25.200> we'll<00:09:25.440> see<00:09:25.620> that 00:09:25.730 --> 00:09:25.740 align:start position:0% your batch means more we'll see that 00:09:25.740 --> 00:09:27.650 align:start position:0% your batch means more we'll see that later<00:09:25.920> so<00:09:26.580> the<00:09:26.880> process<00:09:27.120> of<00:09:27.300> minting<00:09:27.600> a 00:09:27.650 --> 00:09:27.660 align:start position:0% later so the process of minting a 00:09:27.660 --> 00:09:30.050 align:start position:0% later so the process of minting a gigabad<00:09:28.140> is<00:09:28.320> pretty<00:09:28.500> simple 00:09:30.050 --> 00:09:30.060 align:start position:0% gigabad is pretty simple 00:09:30.060 --> 00:09:32.269 align:start position:0% gigabad is pretty simple I<00:09:30.600> have<00:09:30.779> a<00:09:30.899> source<00:09:31.260> account<00:09:31.380> here<00:09:32.040> is<00:09:32.160> the 00:09:32.269 --> 00:09:32.279 align:start position:0% I have a source account here is the 00:09:32.279 --> 00:09:34.310 align:start position:0% I have a source account here is the internet.if<00:09:33.000> I<00:09:33.240> have<00:09:33.420> data<00:09:33.959> I<00:09:34.019> need<00:09:34.140> my 00:09:34.310 --> 00:09:34.320 align:start position:0% internet.if I have data I need my 00:09:34.320 --> 00:09:36.170 align:start position:0% internet.if I have data I need my solving<00:09:34.680> data<00:09:34.980> one<00:09:35.279> piece<00:09:35.519> of<00:09:35.640> data<00:09:35.880> is<00:09:35.940> that<00:09:36.120> I 00:09:36.170 --> 00:09:36.180 align:start position:0% solving data one piece of data is that I 00:09:36.180 --> 00:09:37.670 align:start position:0% solving data one piece of data is that I have<00:09:36.240> a<00:09:36.360> crypto<00:09:36.600> bank<00:09:36.839> I<00:09:37.080> want<00:09:37.200> to<00:09:37.320> prove<00:09:37.560> it 00:09:37.670 --> 00:09:37.680 align:start position:0% have a crypto bank I want to prove it 00:09:37.680 --> 00:09:40.430 align:start position:0% have a crypto bank I want to prove it I'll<00:09:38.399> generate<00:09:38.820> SDK<00:09:39.180> proof<00:09:39.480> and<00:09:39.600> send<00:09:39.839> this<00:09:40.019> ZK 00:09:40.430 --> 00:09:40.440 align:start position:0% I'll generate SDK proof and send this ZK 00:09:40.440 --> 00:09:42.590 align:start position:0% I'll generate SDK proof and send this ZK proof<00:09:40.680> to<00:09:40.800> the<00:09:40.920> adjuster<00:09:41.459> the<00:09:42.060> accessor 00:09:42.590 --> 00:09:42.600 align:start position:0% proof to the adjuster the accessor 00:09:42.600 --> 00:09:44.990 align:start position:0% proof to the adjuster the accessor validates<00:09:43.080> that<00:09:43.320> okay 00:09:44.990 --> 00:09:45.000 align:start position:0% validates that okay 00:09:45.000 --> 00:09:47.810 align:start position:0% validates that okay the<00:09:45.300> legend<00:09:45.420> that<00:09:45.720> it<00:09:45.959> has<00:09:46.200> a<00:09:46.380> punk<00:09:46.640> I<00:09:47.640> value 00:09:47.810 --> 00:09:47.820 align:start position:0% the legend that it has a punk I value 00:09:47.820 --> 00:09:49.970 align:start position:0% the legend that it has a punk I value that<00:09:48.060> I<00:09:48.240> mean<00:09:48.360> the<00:09:48.540> badge<00:09:48.839> but<00:09:49.080> the<00:09:49.200> SDK<00:09:49.620> tester 00:09:49.970 --> 00:09:49.980 align:start position:0% that I mean the badge but the SDK tester 00:09:49.980 --> 00:09:51.829 align:start position:0% that I mean the badge but the SDK tester at<00:09:50.220> no<00:09:50.399> point<00:09:50.640> will<00:09:50.940> know<00:09:51.180> about<00:09:51.360> my<00:09:51.660> address 00:09:51.829 --> 00:09:51.839 align:start position:0% at no point will know about my address 00:09:51.839 --> 00:09:53.750 align:start position:0% at no point will know about my address last<00:09:52.320> thing<00:09:52.500> he<00:09:52.680> does<00:09:52.860> is<00:09:53.100> that<00:09:53.279> it<00:09:53.519> stores 00:09:53.750 --> 00:09:53.760 align:start position:0% last thing he does is that it stores 00:09:53.760 --> 00:09:55.910 align:start position:0% last thing he does is that it stores only<00:09:54.000> fires<00:09:54.540> we'll<00:09:54.600> see<00:09:54.720> that<00:09:54.899> later 00:09:55.910 --> 00:09:55.920 align:start position:0% only fires we'll see that later 00:09:55.920 --> 00:09:58.490 align:start position:0% only fires we'll see that later so<00:09:56.700> to<00:09:57.000> to<00:09:57.240> really<00:09:57.480> understand<00:09:57.660> better<00:09:58.019> GK 00:09:58.490 --> 00:09:58.500 align:start position:0% so to to really understand better GK 00:09:58.500 --> 00:10:02.570 align:start position:0% so to to really understand better GK badges<00:09:58.920> I<00:09:59.820> like<00:09:59.940> to<00:10:00.120> use<00:10:00.560> two<00:10:01.580> identities 00:10:02.570 --> 00:10:02.580 align:start position:0% badges I like to use two identities 00:10:02.580 --> 00:10:04.610 align:start position:0% badges I like to use two identities let's<00:10:03.000> say<00:10:03.180> that<00:10:03.300> I<00:10:03.480> have<00:10:03.660> my<00:10:03.959> public<00:10:04.140> wallet 00:10:04.610 --> 00:10:04.620 align:start position:0% let's say that I have my public wallet 00:10:04.620 --> 00:10:06.769 align:start position:0% let's say that I have my public wallet again<00:10:05.100> they<00:10:05.399> do<00:10:05.580> not<00:10:05.700> use<00:10:05.940> I<00:10:06.240> have<00:10:06.300> my<00:10:06.420> ens 00:10:06.769 --> 00:10:06.779 align:start position:0% again they do not use I have my ens 00:10:06.779 --> 00:10:08.810 align:start position:0% again they do not use I have my ens names<00:10:06.959> I<00:10:07.200> donated<00:10:07.440> a<00:10:07.740> Bitcoin<00:10:08.100> I'm<00:10:08.339> a<00:10:08.519> verified 00:10:08.810 --> 00:10:08.820 align:start position:0% names I donated a Bitcoin I'm a verified 00:10:08.820 --> 00:10:11.389 align:start position:0% names I donated a Bitcoin I'm a verified human<00:10:09.060> meaning<00:10:09.660> that<00:10:09.959> I<00:10:10.200> docs<00:10:10.620> myself<00:10:10.740> I 00:10:11.389 --> 00:10:11.399 align:start position:0% human meaning that I docs myself I 00:10:11.399 --> 00:10:13.370 align:start position:0% human meaning that I docs myself I uploaded<00:10:11.880> the<00:10:12.000> video<00:10:12.180> with<00:10:12.540> my<00:10:12.720> name<00:10:12.899> Master 00:10:13.370 --> 00:10:13.380 align:start position:0% uploaded the video with my name Master 00:10:13.380 --> 00:10:15.829 align:start position:0% uploaded the video with my name Master name<00:10:13.740> and<00:10:14.640> it's<00:10:14.880> linked<00:10:15.180> to<00:10:15.300> my<00:10:15.420> address<00:10:15.480> so 00:10:15.829 --> 00:10:15.839 align:start position:0% name and it's linked to my address so 00:10:15.839 --> 00:10:18.050 align:start position:0% name and it's linked to my address so this<00:10:16.019> address<00:10:16.200> is<00:10:16.500> completely<00:10:17.040> docked<00:10:17.940> like 00:10:18.050 --> 00:10:18.060 align:start position:0% this address is completely docked like 00:10:18.060 --> 00:10:20.090 align:start position:0% this address is completely docked like everybody<00:10:18.420> can<00:10:18.899> know<00:10:19.019> everything<00:10:19.200> about<00:10:19.440> it<00:10:19.680> I 00:10:20.090 --> 00:10:20.100 align:start position:0% everybody can know everything about it I 00:10:20.100 --> 00:10:21.889 align:start position:0% everybody can know everything about it I have<00:10:20.220> some<00:10:20.459> nfts<00:10:21.060> I<00:10:21.300> only<00:10:21.540> need<00:10:21.720> two 00:10:21.889 --> 00:10:21.899 align:start position:0% have some nfts I only need two 00:10:21.899 --> 00:10:23.810 align:start position:0% have some nfts I only need two conferences<00:10:22.260> so<00:10:22.500> I<00:10:22.620> have<00:10:22.680> some<00:10:22.800> perhaps 00:10:23.810 --> 00:10:23.820 align:start position:0% conferences so I have some perhaps 00:10:23.820 --> 00:10:25.670 align:start position:0% conferences so I have some perhaps and<00:10:24.360> actually<00:10:24.480> I<00:10:24.779> have<00:10:24.899> another<00:10:25.019> wallet<00:10:25.440> this 00:10:25.670 --> 00:10:25.680 align:start position:0% and actually I have another wallet this 00:10:25.680 --> 00:10:27.350 align:start position:0% and actually I have another wallet this is<00:10:25.800> this<00:10:26.040> mine<00:10:26.220> is<00:10:26.339> my<00:10:26.459> private<00:10:26.700> wallet<00:10:27.120> that's 00:10:27.350 --> 00:10:27.360 align:start position:0% is this mine is my private wallet that's 00:10:27.360 --> 00:10:29.210 align:start position:0% is this mine is my private wallet that's where<00:10:27.480> I<00:10:27.660> do<00:10:27.779> my<00:10:27.899> DJ<00:10:28.260> and<00:10:28.440> stuff<00:10:28.560> I<00:10:28.920> have<00:10:28.980> a<00:10:29.100> lot 00:10:29.210 --> 00:10:29.220 align:start position:0% where I do my DJ and stuff I have a lot 00:10:29.220 --> 00:10:30.889 align:start position:0% where I do my DJ and stuff I have a lot of<00:10:29.339> transaction<00:10:29.700> I<00:10:30.180> maybe<00:10:30.360> have<00:10:30.600> a<00:10:30.720> lot<00:10:30.779> of 00:10:30.889 --> 00:10:30.899 align:start position:0% of transaction I maybe have a lot of 00:10:30.899 --> 00:10:33.410 align:start position:0% of transaction I maybe have a lot of assets<00:10:31.200> hopefully<00:10:31.680> that's<00:10:32.519> the<00:10:32.700> dream<00:10:32.880> I 00:10:33.410 --> 00:10:33.420 align:start position:0% assets hopefully that's the dream I 00:10:33.420 --> 00:10:35.090 align:start position:0% assets hopefully that's the dream I don't<00:10:33.540> have<00:10:33.660> this<00:10:33.839> but<00:10:34.080> that<00:10:34.500> will<00:10:34.620> be<00:10:34.740> cool<00:10:34.920> to 00:10:35.090 --> 00:10:35.100 align:start position:0% don't have this but that will be cool to 00:10:35.100 --> 00:10:37.310 align:start position:0% don't have this but that will be cool to be<00:10:35.220> addition<00:10:35.640> a<00:10:36.240> lot<00:10:36.300> of<00:10:36.480> assets<00:10:36.839> a<00:10:37.080> lot<00:10:37.200> of 00:10:37.310 --> 00:10:37.320 align:start position:0% be addition a lot of assets a lot of 00:10:37.320 --> 00:10:39.949 align:start position:0% be addition a lot of assets a lot of nfts<00:10:37.920> a<00:10:38.040> lot<00:10:38.100> of<00:10:38.220> things<00:10:38.339> I<00:10:38.640> don't<00:10:38.880> quite<00:10:39.779> sure 00:10:39.949 --> 00:10:39.959 align:start position:0% nfts a lot of things I don't quite sure 00:10:39.959 --> 00:10:41.690 align:start position:0% nfts a lot of things I don't quite sure that<00:10:40.320> I<00:10:40.620> never<00:10:40.800> want<00:10:41.040> to<00:10:41.220> connect<00:10:41.399> them 00:10:41.690 --> 00:10:41.700 align:start position:0% that I never want to connect them 00:10:41.700 --> 00:10:43.190 align:start position:0% that I never want to connect them together<00:10:41.880> but 00:10:43.190 --> 00:10:43.200 align:start position:0% together but 00:10:43.200 --> 00:10:45.829 align:start position:0% together but I<00:10:43.860> want<00:10:44.040> to<00:10:44.160> use<00:10:44.339> them<00:10:44.579> together<00:10:44.820> because<00:10:45.300> both 00:10:45.829 --> 00:10:45.839 align:start position:0% I want to use them together because both 00:10:45.839 --> 00:10:49.430 align:start position:0% I want to use them together because both have<00:10:46.620> valuable<00:10:47.399> data<00:10:48.240> and<00:10:48.839> I<00:10:49.079> want<00:10:49.200> to<00:10:49.260> use 00:10:49.430 --> 00:10:49.440 align:start position:0% have valuable data and I want to use 00:10:49.440 --> 00:10:51.769 align:start position:0% have valuable data and I want to use them<00:10:49.620> together<00:10:49.860> so<00:10:50.399> that's<00:10:50.640> what<00:10:50.940> rgk<00:10:51.480> badge 00:10:51.769 --> 00:10:51.779 align:start position:0% them together so that's what rgk badge 00:10:51.779 --> 00:10:53.810 align:start position:0% them together so that's what rgk badge is<00:10:51.839> about<00:10:51.959> so<00:10:52.680> the<00:10:52.860> first<00:10:52.980> thing<00:10:53.220> that<00:10:53.519> it 00:10:53.810 --> 00:10:53.820 align:start position:0% is about so the first thing that it 00:10:53.820 --> 00:10:56.389 align:start position:0% is about so the first thing that it allows<00:10:54.120> you<00:10:54.180> to<00:10:54.360> do<00:10:54.540> I'm<00:10:55.140> a<00:10:55.320> verified<00:10:55.560> human<00:10:55.860> on 00:10:56.389 --> 00:10:56.399 align:start position:0% allows you to do I'm a verified human on 00:10:56.399 --> 00:10:58.790 align:start position:0% allows you to do I'm a verified human on daytime.heath<00:10:57.300> I'm<00:10:57.420> doxed<00:10:57.899> but<00:10:58.440> now<00:10:58.560> let's 00:10:58.790 --> 00:10:58.800 align:start position:0% daytime.heath I'm doxed but now let's 00:10:58.800 --> 00:11:00.410 align:start position:0% daytime.heath I'm doxed but now let's say<00:10:58.980> that<00:10:59.100> I<00:10:59.279> want<00:10:59.339> to<00:10:59.459> access<00:10:59.579> my<00:10:59.880> private 00:11:00.410 --> 00:11:00.420 align:start position:0% say that I want to access my private 00:11:00.420 --> 00:11:02.750 align:start position:0% say that I want to access my private wallet<00:11:00.839> an<00:11:01.500> application<00:11:01.920> that<00:11:02.160> requires<00:11:02.700> you 00:11:02.750 --> 00:11:02.760 align:start position:0% wallet an application that requires you 00:11:02.760 --> 00:11:04.790 align:start position:0% wallet an application that requires you to<00:11:03.060> prove<00:11:03.420> that<00:11:03.720> you<00:11:03.839> are<00:11:03.959> human 00:11:04.790 --> 00:11:04.800 align:start position:0% to prove that you are human 00:11:04.800 --> 00:11:06.290 align:start position:0% to prove that you are human of<00:11:05.040> course<00:11:05.160> I<00:11:05.519> don't<00:11:05.640> want<00:11:05.820> to<00:11:05.880> link<00:11:06.060> them 00:11:06.290 --> 00:11:06.300 align:start position:0% of course I don't want to link them 00:11:06.300 --> 00:11:07.190 align:start position:0% of course I don't want to link them together 00:11:07.190 --> 00:11:07.200 align:start position:0% together 00:11:07.200 --> 00:11:09.050 align:start position:0% together so<00:11:07.500> what<00:11:07.620> I'll<00:11:07.800> do<00:11:07.920> is<00:11:08.040> that<00:11:08.220> I<00:11:08.519> will<00:11:08.640> have<00:11:08.820> the 00:11:09.050 --> 00:11:09.060 align:start position:0% so what I'll do is that I will have the 00:11:09.060 --> 00:11:11.150 align:start position:0% so what I'll do is that I will have the proof<00:11:09.360> of<00:11:09.480> humanity<00:11:09.899> the<00:11:10.200> key<00:11:10.320> batch<00:11:10.620> online 00:11:11.150 --> 00:11:11.160 align:start position:0% proof of humanity the key batch online 00:11:11.160 --> 00:11:13.910 align:start position:0% proof of humanity the key batch online wallet<00:11:11.940> and<00:11:12.660> it<00:11:12.779> will<00:11:12.959> just<00:11:13.140> reveal<00:11:13.560> what<00:11:13.740> I 00:11:13.910 --> 00:11:13.920 align:start position:0% wallet and it will just reveal what I 00:11:13.920 --> 00:11:16.970 align:start position:0% wallet and it will just reveal what I need<00:11:14.100> that<00:11:14.940> is<00:11:15.120> I'm<00:11:15.779> a<00:11:16.019> human<00:11:16.200> I<00:11:16.740> have 00:11:16.970 --> 00:11:16.980 align:start position:0% need that is I'm a human I have 00:11:16.980 --> 00:11:18.949 align:start position:0% need that is I'm a human I have somewhere<00:11:17.519> a<00:11:17.700> Social<00:11:17.940> account<00:11:18.120> that<00:11:18.360> is<00:11:18.480> doxed 00:11:18.949 --> 00:11:18.959 align:start position:0% somewhere a Social account that is doxed 00:11:18.959 --> 00:11:20.569 align:start position:0% somewhere a Social account that is doxed and<00:11:19.380> I<00:11:19.500> was<00:11:19.620> able<00:11:19.860> to<00:11:19.920> do<00:11:20.040> this<00:11:20.160> badge<00:11:20.399> only 00:11:20.569 --> 00:11:20.579 align:start position:0% and I was able to do this badge only 00:11:20.579 --> 00:11:22.550 align:start position:0% and I was able to do this badge only once<00:11:20.820> okay 00:11:22.550 --> 00:11:22.560 align:start position:0% once okay 00:11:22.560 --> 00:11:24.790 align:start position:0% once okay so<00:11:23.160> now<00:11:23.399> we'll<00:11:23.579> get<00:11:23.760> into<00:11:23.880> the<00:11:24.120> technicalities 00:11:24.790 --> 00:11:24.800 align:start position:0% so now we'll get into the technicalities 00:11:24.800 --> 00:11:28.370 align:start position:0% so now we'll get into the technicalities how<00:11:25.800> everything<00:11:26.100> is<00:11:26.399> done<00:11:26.579> the<00:11:27.360> zkr<00:11:27.839> tester<00:11:28.200> I 00:11:28.370 --> 00:11:28.380 align:start position:0% how everything is done the zkr tester I 00:11:28.380 --> 00:11:30.170 align:start position:0% how everything is done the zkr tester I told<00:11:28.560> you<00:11:28.680> about<00:11:28.800> the<00:11:29.399> one<00:11:29.519> we<00:11:29.700> currently<00:11:30.000> use 00:11:30.170 --> 00:11:30.180 align:start position:0% told you about the one we currently use 00:11:30.180 --> 00:11:34.850 align:start position:0% told you about the one we currently use is<00:11:30.540> the<00:11:31.140> Hydra<00:11:31.500> s1z<00:11:32.100> cat<00:11:32.399> tester<00:11:32.760> Hydra<00:11:33.540> S1<00:11:33.959> is 00:11:34.850 --> 00:11:34.860 align:start position:0% is the Hydra s1z cat tester Hydra S1 is 00:11:34.860 --> 00:11:37.490 align:start position:0% is the Hydra s1z cat tester Hydra S1 is for<00:11:35.279> the<00:11:35.399> proving<00:11:35.760> scheme<00:11:36.180> because<00:11:36.540> we<00:11:37.260> this 00:11:37.490 --> 00:11:37.500 align:start position:0% for the proving scheme because we this 00:11:37.500 --> 00:11:39.769 align:start position:0% for the proving scheme because we this statistor<00:11:38.160> accept<00:11:38.339> a<00:11:38.940> certain 00:11:39.769 --> 00:11:39.779 align:start position:0% statistor accept a certain 00:11:39.779 --> 00:11:42.410 align:start position:0% statistor accept a certain type<00:11:40.260> of<00:11:40.500> GK<00:11:40.860> proofs<00:11:41.220> and<00:11:41.459> I'll<00:11:41.579> explain<00:11:41.760> what 00:11:42.410 --> 00:11:42.420 align:start position:0% type of GK proofs and I'll explain what 00:11:42.420 --> 00:11:45.710 align:start position:0% type of GK proofs and I'll explain what those<00:11:42.540> UK<00:11:42.839> proofs<00:11:43.140> are<00:11:43.320> so<00:11:44.240> behind<00:11:45.240> the 00:11:45.710 --> 00:11:45.720 align:start position:0% those UK proofs are so behind the 00:11:45.720 --> 00:11:47.870 align:start position:0% those UK proofs are so behind the hydration<00:11:46.140> tester<00:11:46.980> there's<00:11:47.220> always<00:11:47.399> a<00:11:47.760> group 00:11:47.870 --> 00:11:47.880 align:start position:0% hydration tester there's always a group 00:11:47.880 --> 00:11:49.730 align:start position:0% hydration tester there's always a group of<00:11:48.060> eligible<00:11:48.420> accounts<00:11:48.959> that's<00:11:49.079> how<00:11:49.260> it<00:11:49.440> works 00:11:49.730 --> 00:11:49.740 align:start position:0% of eligible accounts that's how it works 00:11:49.740 --> 00:11:52.730 align:start position:0% of eligible accounts that's how it works so<00:11:50.220> for<00:11:50.399> instance<00:11:50.579> behind<00:11:51.300> the<00:11:51.480> ZK<00:11:51.959> the<00:11:52.440> proof 00:11:52.730 --> 00:11:52.740 align:start position:0% so for instance behind the ZK the proof 00:11:52.740 --> 00:11:54.710 align:start position:0% so for instance behind the ZK the proof of<00:11:52.860> humanity<00:11:53.339> is<00:11:53.459> the<00:11:53.640> cable 00:11:54.710 --> 00:11:54.720 align:start position:0% of humanity is the cable 00:11:54.720 --> 00:11:57.230 align:start position:0% of humanity is the cable there<00:11:55.380> is<00:11:55.560> the<00:11:55.740> list<00:11:55.920> of<00:11:56.160> all<00:11:56.459> the<00:11:56.640> registrants 00:11:57.230 --> 00:11:57.240 align:start position:0% there is the list of all the registrants 00:11:57.240 --> 00:12:00.350 align:start position:0% there is the list of all the registrants that<00:11:57.839> are<00:11:58.079> on<00:11:58.380> the<00:11:58.620> poh<00:11:59.220> registry<00:11:59.820> so<00:12:00.180> of 00:12:00.350 --> 00:12:00.360 align:start position:0% that are on the poh registry so of 00:12:00.360 --> 00:12:01.610 align:start position:0% that are on the poh registry so of course<00:12:00.480> there<00:12:00.660> is<00:12:00.779> my<00:12:00.959> address 00:12:01.610 --> 00:12:01.620 align:start position:0% course there is my address 00:12:01.620 --> 00:12:04.490 align:start position:0% course there is my address we<00:12:02.160> see<00:12:02.279> this<00:12:02.519> that<00:12:02.700> there<00:12:03.000> is<00:12:03.180> a<00:12:03.779> value<00:12:03.959> to 00:12:04.490 --> 00:12:04.500 align:start position:0% we see this that there is a value to 00:12:04.500 --> 00:12:06.170 align:start position:0% we see this that there is a value to each<00:12:04.680> address<00:12:04.860> to<00:12:05.160> each<00:12:05.339> account<00:12:05.519> and<00:12:06.000> this 00:12:06.170 --> 00:12:06.180 align:start position:0% each address to each account and this 00:12:06.180 --> 00:12:07.910 align:start position:0% each address to each account and this value<00:12:06.360> will<00:12:06.600> be<00:12:06.720> the<00:12:06.839> balance<00:12:07.140> of<00:12:07.320> the<00:12:07.620> batch 00:12:07.910 --> 00:12:07.920 align:start position:0% value will be the balance of the batch 00:12:07.920 --> 00:12:11.090 align:start position:0% value will be the balance of the batch and<00:12:08.820> with<00:12:09.060> this<00:12:09.240> you<00:12:09.480> can 00:12:11.090 --> 00:12:11.100 align:start position:0% and with this you can 00:12:11.100 --> 00:12:14.210 align:start position:0% and with this you can um<00:12:11.220> you<00:12:12.120> you<00:12:12.120> can<00:12:12.480> use<00:12:12.720> it<00:12:12.959> to<00:12:13.380> to<00:12:13.620> code<00:12:13.920> some 00:12:14.210 --> 00:12:14.220 align:start position:0% um you you can use it to to code some 00:12:14.220 --> 00:12:16.850 align:start position:0% um you you can use it to to code some sort<00:12:14.459> of<00:12:14.640> tiers<00:12:15.240> so<00:12:15.540> let's<00:12:15.720> say<00:12:15.959> imagine<00:12:16.320> that 00:12:16.850 --> 00:12:16.860 align:start position:0% sort of tiers so let's say imagine that 00:12:16.860 --> 00:12:19.730 align:start position:0% sort of tiers so let's say imagine that in<00:12:17.399> V2<00:12:17.760> poh<00:12:18.360> have<00:12:18.540> a<00:12:18.720> super<00:12:18.839> verified<00:12:19.260> user 00:12:19.730 --> 00:12:19.740 align:start position:0% in V2 poh have a super verified user 00:12:19.740 --> 00:12:22.069 align:start position:0% in V2 poh have a super verified user like<00:12:20.220> it's<00:12:20.459> verified<00:12:21.060> but<00:12:21.300> very<00:12:21.540> well<00:12:21.779> with 00:12:22.069 --> 00:12:22.079 align:start position:0% like it's verified but very well with 00:12:22.079 --> 00:12:24.590 align:start position:0% like it's verified but very well with kyc<00:12:22.680> or<00:12:22.800> I<00:12:23.100> don't<00:12:23.160> know<00:12:23.279> what<00:12:23.399> you<00:12:24.180> could<00:12:24.360> have 00:12:24.590 --> 00:12:24.600 align:start position:0% kyc or I don't know what you could have 00:12:24.600 --> 00:12:26.870 align:start position:0% kyc or I don't know what you could have maybe<00:12:25.140> the<00:12:25.500> element<00:12:25.620> is<00:12:25.980> with<00:12:26.279> the<00:12:26.459> value<00:12:26.579> 2 00:12:26.870 --> 00:12:26.880 align:start position:0% maybe the element is with the value 2 00:12:26.880 --> 00:12:29.389 align:start position:0% maybe the element is with the value 2 and<00:12:27.480> it<00:12:27.660> will<00:12:27.779> give<00:12:28.079> the<00:12:28.260> badge<00:12:28.860> with<00:12:29.100> the 00:12:29.389 --> 00:12:29.399 align:start position:0% and it will give the badge with the 00:12:29.399 --> 00:12:32.810 align:start position:0% and it will give the badge with the balance<00:12:30.180> too<00:12:30.480> and<00:12:31.260> everyone<00:12:31.440> that<00:12:31.800> has<00:12:32.100> two 00:12:32.810 --> 00:12:32.820 align:start position:0% balance too and everyone that has two 00:12:32.820 --> 00:12:34.490 align:start position:0% balance too and everyone that has two badges<00:12:33.300> like<00:12:33.540> that<00:12:33.720> has<00:12:33.839> balance<00:12:34.200> two<00:12:34.320> of 00:12:34.490 --> 00:12:34.500 align:start position:0% badges like that has balance two of 00:12:34.500 --> 00:12:35.389 align:start position:0% badges like that has balance two of these<00:12:34.620> batch<00:12:34.740> means<00:12:35.040> they<00:12:35.160> are<00:12:35.279> super 00:12:35.389 --> 00:12:35.399 align:start position:0% these batch means they are super 00:12:35.399 --> 00:12:37.550 align:start position:0% these batch means they are super verified<00:12:35.820> so 00:12:37.550 --> 00:12:37.560 align:start position:0% verified so 00:12:37.560 --> 00:12:40.730 align:start position:0% verified so again<00:12:38.100> yes<00:12:38.519> here<00:12:39.300> is<00:12:39.480> just<00:12:39.600> you<00:12:39.779> have<00:12:39.959> pH<00:12:40.140> UI<00:12:40.620> in 00:12:40.730 --> 00:12:40.740 align:start position:0% again yes here is just you have pH UI in 00:12:40.740 --> 00:12:42.230 align:start position:0% again yes here is just you have pH UI in the<00:12:40.860> group<00:12:40.980> with<00:12:41.279> one<00:12:41.459> you<00:12:41.760> are<00:12:41.880> not<00:12:42.000> you're 00:12:42.230 --> 00:12:42.240 align:start position:0% the group with one you are not you're 00:12:42.240 --> 00:12:43.970 align:start position:0% the group with one you are not you're not<00:12:42.360> in<00:12:42.600> the<00:12:42.720> group<00:12:42.839> so<00:12:43.380> you<00:12:43.620> have<00:12:43.680> the<00:12:43.800> group 00:12:43.970 --> 00:12:43.980 align:start position:0% not in the group so you have the group 00:12:43.980 --> 00:12:45.410 align:start position:0% not in the group so you have the group of<00:12:44.100> eligible<00:12:44.459> accounts<00:12:44.940> these<00:12:45.180> are<00:12:45.300> the 00:12:45.410 --> 00:12:45.420 align:start position:0% of eligible accounts these are the 00:12:45.420 --> 00:12:46.670 align:start position:0% of eligible accounts these are the accounts<00:12:45.779> that<00:12:45.839> will<00:12:45.959> be<00:12:46.079> able<00:12:46.200> to<00:12:46.320> meet<00:12:46.440> the 00:12:46.670 --> 00:12:46.680 align:start position:0% accounts that will be able to meet the 00:12:46.680 --> 00:12:50.449 align:start position:0% accounts that will be able to meet the badge<00:12:47.279> and<00:12:47.940> we<00:12:48.420> put<00:12:48.600> them<00:12:48.839> in<00:12:49.320> a<00:12:49.380> Merkel<00:12:49.740> tree 00:12:50.449 --> 00:12:50.459 align:start position:0% badge and we put them in a Merkel tree 00:12:50.459 --> 00:12:52.790 align:start position:0% badge and we put them in a Merkel tree it's<00:12:50.940> a<00:12:51.120> position<00:12:51.240> Local<00:12:51.779> 3<00:12:52.079> so<00:12:52.320> that<00:12:52.500> it's<00:12:52.620> not 00:12:52.790 --> 00:12:52.800 align:start position:0% it's a position Local 3 so that it's not 00:12:52.800 --> 00:12:55.009 align:start position:0% it's a position Local 3 so that it's not friendly<00:12:53.220> which<00:12:53.399> is<00:12:53.579> that<00:12:53.760> but<00:12:54.360> in<00:12:54.600> the<00:12:54.779> leaves 00:12:55.009 --> 00:12:55.019 align:start position:0% friendly which is that but in the leaves 00:12:55.019 --> 00:12:58.190 align:start position:0% friendly which is that but in the leaves you<00:12:55.620> have<00:12:55.860> all<00:12:56.339> the<00:12:56.519> eligible<00:12:56.940> accounts<00:12:57.839> we 00:12:58.190 --> 00:12:58.200 align:start position:0% you have all the eligible accounts we 00:12:58.200 --> 00:13:00.110 align:start position:0% you have all the eligible accounts we have<00:12:58.320> the<00:12:58.500> root<00:12:58.800> we<00:12:59.220> publish<00:12:59.579> the<00:12:59.760> root<00:13:00.000> and 00:13:00.110 --> 00:13:00.120 align:start position:0% have the root we publish the root and 00:13:00.120 --> 00:13:02.870 align:start position:0% have the root we publish the root and chain<00:13:00.380> and<00:13:01.380> we'll<00:13:01.740> see<00:13:01.980> what<00:13:02.339> we<00:13:02.459> do<00:13:02.639> use 00:13:02.870 --> 00:13:02.880 align:start position:0% chain and we'll see what we do use 00:13:02.880 --> 00:13:06.710 align:start position:0% chain and we'll see what we do use everything<00:13:03.139> so<00:13:04.139> the<00:13:04.560> the<00:13:04.740> the<00:13:04.860> the<00:13:05.220> way<00:13:05.880> the 00:13:06.710 --> 00:13:06.720 align:start position:0% everything so the the the the way the 00:13:06.720 --> 00:13:10.550 align:start position:0% everything so the the the the way the the<00:13:07.700> badges<00:13:08.700> minted<00:13:09.180> is<00:13:09.839> first<00:13:10.019> you<00:13:10.200> go<00:13:10.380> to 00:13:10.550 --> 00:13:10.560 align:start position:0% the badges minted is first you go to 00:13:10.560 --> 00:13:13.430 align:start position:0% the badges minted is first you go to your<00:13:11.040> front<00:13:11.220> end<00:13:11.459> so<00:13:11.760> I<00:13:11.880> wantismo<00:13:12.660> I'm 00:13:13.430 --> 00:13:13.440 align:start position:0% your front end so I wantismo I'm 00:13:13.440 --> 00:13:15.170 align:start position:0% your front end so I wantismo I'm connected<00:13:13.860> with<00:13:13.980> the<00:13:14.100> adrenal<00:13:14.519> is<00:13:14.700> the<00:13:15.060> four 00:13:15.170 --> 00:13:15.180 align:start position:0% connected with the adrenal is the four 00:13:15.180 --> 00:13:18.170 align:start position:0% connected with the adrenal is the four seconds<00:13:15.360> I<00:13:16.320> first<00:13:16.560> I<00:13:16.920> upload<00:13:17.279> the<00:13:17.519> Merkel<00:13:18.000> tree 00:13:18.170 --> 00:13:18.180 align:start position:0% seconds I first I upload the Merkel tree 00:13:18.180 --> 00:13:19.730 align:start position:0% seconds I first I upload the Merkel tree now<00:13:18.540> I<00:13:18.720> have<00:13:18.839> in<00:13:18.959> iPhone<00:13:19.139> 10<00:13:19.440> everything 00:13:19.730 --> 00:13:19.740 align:start position:0% now I have in iPhone 10 everything 00:13:19.740 --> 00:13:22.069 align:start position:0% now I have in iPhone 10 everything happens<00:13:20.279> on<00:13:20.579> the<00:13:20.700> front<00:13:20.820> end<00:13:21.060> that's<00:13:21.779> what 00:13:22.069 --> 00:13:22.079 align:start position:0% happens on the front end that's what 00:13:22.079 --> 00:13:25.009 align:start position:0% happens on the front end that's what guarantees<00:13:22.740> the<00:13:22.920> Privacy<00:13:23.220> so<00:13:23.880> on<00:13:24.240> in<00:13:24.600> my<00:13:24.779> front 00:13:25.009 --> 00:13:25.019 align:start position:0% guarantees the Privacy so on in my front 00:13:25.019 --> 00:13:27.230 align:start position:0% guarantees the Privacy so on in my front end<00:13:25.200> I<00:13:25.500> have<00:13:25.620> the<00:13:25.980> marker<00:13:26.339> 3<00:13:26.519> I<00:13:26.940> have<00:13:27.060> my 00:13:27.230 --> 00:13:27.240 align:start position:0% end I have the marker 3 I have my 00:13:27.240 --> 00:13:29.090 align:start position:0% end I have the marker 3 I have my account<00:13:27.480> and<00:13:28.200> what<00:13:28.320> I<00:13:28.440> will<00:13:28.560> do<00:13:28.680> I<00:13:28.800> will<00:13:28.980> do 00:13:29.090 --> 00:13:29.100 align:start position:0% account and what I will do I will do 00:13:29.100 --> 00:13:30.889 align:start position:0% account and what I will do I will do three<00:13:29.279> things<00:13:29.579> first<00:13:30.000> I<00:13:30.180> will<00:13:30.300> prove<00:13:30.540> that<00:13:30.660> I'm 00:13:30.889 --> 00:13:30.899 align:start position:0% three things first I will prove that I'm 00:13:30.899 --> 00:13:34.069 align:start position:0% three things first I will prove that I'm the<00:13:31.139> owner<00:13:31.380> of<00:13:31.500> daily<00:13:31.980> not<00:13:32.459> eat<00:13:33.180> and<00:13:33.839> these 00:13:34.069 --> 00:13:34.079 align:start position:0% the owner of daily not eat and these 00:13:34.079 --> 00:13:35.870 align:start position:0% the owner of daily not eat and these three<00:13:34.200> things<00:13:34.380> will<00:13:34.620> be<00:13:34.740> done<00:13:34.920> in<00:13:35.399> the<00:13:35.519> SDK 00:13:35.870 --> 00:13:35.880 align:start position:0% three things will be done in the SDK 00:13:35.880 --> 00:13:38.389 align:start position:0% three things will be done in the SDK circuit<00:13:36.300> so<00:13:37.079> first<00:13:37.440> thing<00:13:37.620> I'm<00:13:37.920> the<00:13:38.100> owner<00:13:38.279> of 00:13:38.389 --> 00:13:38.399 align:start position:0% circuit so first thing I'm the owner of 00:13:38.399 --> 00:13:41.690 align:start position:0% circuit so first thing I'm the owner of the<00:13:38.459> adrian.t<00:13:39.120> second<00:13:39.839> the<00:13:40.440> original.e<00:13:41.279> is<00:13:41.519> in 00:13:41.690 --> 00:13:41.700 align:start position:0% the adrian.t second the original.e is in 00:13:41.700 --> 00:13:43.790 align:start position:0% the adrian.t second the original.e is in the<00:13:41.760> Mercury<00:13:42.060> Beyond<00:13:42.540> local<00:13:42.660> proof<00:13:43.079> and<00:13:43.560> the 00:13:43.790 --> 00:13:43.800 align:start position:0% the Mercury Beyond local proof and the 00:13:43.800 --> 00:13:46.129 align:start position:0% the Mercury Beyond local proof and the third<00:13:43.980> thing<00:13:44.279> is<00:13:44.639> I<00:13:45.480> actually<00:13:45.660> own<00:13:45.959> the 00:13:46.129 --> 00:13:46.139 align:start position:0% third thing is I actually own the 00:13:46.139 --> 00:13:47.629 align:start position:0% third thing is I actually own the destination<00:13:46.440> account<00:13:46.740> let's<00:13:47.160> make<00:13:47.339> sure<00:13:47.519> that 00:13:47.629 --> 00:13:47.639 align:start position:0% destination account let's make sure that 00:13:47.639 --> 00:13:49.910 align:start position:0% destination account let's make sure that I<00:13:47.880> cannot<00:13:48.120> give<00:13:48.420> budgets<00:13:48.899> to<00:13:49.079> others<00:13:49.440> or<00:13:49.740> that 00:13:49.910 --> 00:13:49.920 align:start position:0% I cannot give budgets to others or that 00:13:49.920 --> 00:13:51.769 align:start position:0% I cannot give budgets to others or that I<00:13:50.040> cannot<00:13:50.279> spam<00:13:50.579> another<00:13:50.820> account 00:13:51.769 --> 00:13:51.779 align:start position:0% I cannot spam another account 00:13:51.779 --> 00:13:54.710 align:start position:0% I cannot spam another account so<00:13:52.260> these<00:13:52.620> three<00:13:52.740> things<00:13:52.980> I<00:13:53.459> I'm<00:13:53.720> daniel.is 00:13:54.710 --> 00:13:54.720 align:start position:0% so these three things I I'm daniel.is 00:13:54.720 --> 00:13:56.990 align:start position:0% so these three things I I'm daniel.is Source<00:13:55.260> account<00:13:55.380> destination<00:13:56.160> accounts<00:13:56.700> I'm 00:13:56.990 --> 00:13:57.000 align:start position:0% Source account destination accounts I'm 00:13:57.000 --> 00:13:59.090 align:start position:0% Source account destination accounts I'm part<00:13:57.180> of<00:13:57.360> the<00:13:57.420> tree<00:13:57.660> I<00:13:58.200> do<00:13:58.380> that<00:13:58.500> in<00:13:58.680> the<00:13:58.800> ZK 00:13:59.090 --> 00:13:59.100 align:start position:0% part of the tree I do that in the ZK 00:13:59.100 --> 00:14:02.150 align:start position:0% part of the tree I do that in the ZK snack<00:13:59.399> I<00:14:00.000> get<00:14:00.120> a<00:14:00.300> ZK<00:14:00.600> proof<00:14:00.899> the<00:14:01.500> ZK<00:14:01.920> proof 00:14:02.150 --> 00:14:02.160 align:start position:0% snack I get a ZK proof the ZK proof 00:14:02.160 --> 00:14:05.150 align:start position:0% snack I get a ZK proof the ZK proof reveals<00:14:02.579> nothing<00:14:02.880> but<00:14:03.680> there<00:14:04.680> is<00:14:04.860> an<00:14:04.980> address 00:14:05.150 --> 00:14:05.160 align:start position:0% reveals nothing but there is an address 00:14:05.160 --> 00:14:07.550 align:start position:0% reveals nothing but there is an address that<00:14:05.700> like<00:14:06.060> this<00:14:06.480> users<00:14:06.839> has<00:14:07.019> proved<00:14:07.320> to<00:14:07.380> have 00:14:07.550 --> 00:14:07.560 align:start position:0% that like this users has proved to have 00:14:07.560 --> 00:14:09.350 align:start position:0% that like this users has proved to have an<00:14:07.680> address<00:14:07.800> that<00:14:08.040> is<00:14:08.160> part<00:14:08.339> of<00:14:08.459> the<00:14:08.579> tree<00:14:08.760> I 00:14:09.350 --> 00:14:09.360 align:start position:0% an address that is part of the tree I 00:14:09.360 --> 00:14:11.210 align:start position:0% an address that is part of the tree I give<00:14:09.540> that<00:14:09.660> to<00:14:09.839> the<00:14:09.959> zika<00:14:10.320> tester<00:14:10.680> and<00:14:11.040> the 00:14:11.210 --> 00:14:11.220 align:start position:0% give that to the zika tester and the 00:14:11.220 --> 00:14:13.610 align:start position:0% give that to the zika tester and the decalter<00:14:11.940> does<00:14:12.300> two<00:14:12.540> things<00:14:12.779> first<00:14:13.380> it 00:14:13.610 --> 00:14:13.620 align:start position:0% decalter does two things first it 00:14:13.620 --> 00:14:15.730 align:start position:0% decalter does two things first it verifies<00:14:13.980> the<00:14:14.160> proof<00:14:14.459> okay 00:14:15.730 --> 00:14:15.740 align:start position:0% verifies the proof okay 00:14:15.740 --> 00:14:19.610 align:start position:0% verifies the proof okay it's<00:14:16.740> valid<00:14:17.100> ZK<00:14:17.880> magic<00:14:18.120> and<00:14:18.899> then<00:14:19.019> it<00:14:19.200> register 00:14:19.610 --> 00:14:19.620 align:start position:0% it's valid ZK magic and then it register 00:14:19.620 --> 00:14:21.650 align:start position:0% it's valid ZK magic and then it register a<00:14:19.920> nullifier<00:14:20.459> I<00:14:20.880> think<00:14:21.000> that<00:14:21.120> there<00:14:21.300> was<00:14:21.480> some 00:14:21.650 --> 00:14:21.660 align:start position:0% a nullifier I think that there was some 00:14:21.660 --> 00:14:24.230 align:start position:0% a nullifier I think that there was some presentation<00:14:22.100> defconable<00:14:23.100> this<00:14:23.399> but<00:14:23.579> it's<00:14:24.060> a 00:14:24.230 --> 00:14:24.240 align:start position:0% presentation defconable this but it's a 00:14:24.240 --> 00:14:26.629 align:start position:0% presentation defconable this but it's a way<00:14:24.420> to<00:14:24.779> make<00:14:25.320> sure<00:14:25.440> that<00:14:25.680> from<00:14:26.040> One<00:14:26.160> Source<00:14:26.519> I 00:14:26.629 --> 00:14:26.639 align:start position:0% way to make sure that from One Source I 00:14:26.639 --> 00:14:29.090 align:start position:0% way to make sure that from One Source I can<00:14:26.760> do<00:14:26.940> only<00:14:27.120> one<00:14:27.360> batch<00:14:28.019> and<00:14:28.560> for<00:14:28.800> this<00:14:28.920> I 00:14:29.090 --> 00:14:29.100 align:start position:0% can do only one batch and for this I 00:14:29.100 --> 00:14:31.310 align:start position:0% can do only one batch and for this I register<00:14:29.399> on<00:14:29.579> unifier<00:14:30.000> it's<00:14:30.360> the<00:14:30.600> anonymized 00:14:31.310 --> 00:14:31.320 align:start position:0% register on unifier it's the anonymized 00:14:31.320 --> 00:14:32.930 align:start position:0% register on unifier it's the anonymized version<00:14:31.500> of<00:14:31.800> my<00:14:31.980> address<00:14:32.220> basically<00:14:32.700> that's 00:14:32.930 --> 00:14:32.940 align:start position:0% version of my address basically that's 00:14:32.940 --> 00:14:35.030 align:start position:0% version of my address basically that's great<00:14:33.180> and<00:14:33.360> now<00:14:33.540> I<00:14:33.720> have<00:14:33.839> my<00:14:34.200> badge<00:14:34.680> on<00:14:34.800> my 00:14:35.030 --> 00:14:35.040 align:start position:0% great and now I have my badge on my 00:14:35.040 --> 00:14:36.710 align:start position:0% great and now I have my badge on my destination<00:14:35.279> account<00:14:35.639> and<00:14:36.120> there's<00:14:36.240> no<00:14:36.480> leak 00:14:36.710 --> 00:14:36.720 align:start position:0% destination account and there's no leak 00:14:36.720 --> 00:14:38.269 align:start position:0% destination account and there's no leak nobody<00:14:37.019> can<00:14:37.320> know<00:14:37.440> from<00:14:37.740> this<00:14:37.920> destination 00:14:38.269 --> 00:14:38.279 align:start position:0% nobody can know from this destination 00:14:38.279 --> 00:14:39.949 align:start position:0% nobody can know from this destination account<00:14:38.579> what<00:14:38.940> account<00:14:39.180> was<00:14:39.540> used<00:14:39.779> to 00:14:39.949 --> 00:14:39.959 align:start position:0% account what account was used to 00:14:39.959 --> 00:14:44.030 align:start position:0% account what account was used to generate<00:14:40.260> it<00:14:40.440> so<00:14:41.279> again<00:14:41.760> we<00:14:42.120> saw<00:14:42.300> that<00:14:42.740> this<00:14:43.740> DK 00:14:44.030 --> 00:14:44.040 align:start position:0% generate it so again we saw that this DK 00:14:44.040 --> 00:14:45.550 align:start position:0% generate it so again we saw that this DK tester 00:14:45.550 --> 00:14:45.560 align:start position:0% tester 00:14:45.560 --> 00:14:47.689 align:start position:0% tester allows<00:14:46.560> you<00:14:46.620> to 00:14:47.689 --> 00:14:47.699 align:start position:0% allows you to 00:14:47.699 --> 00:14:50.030 align:start position:0% allows you to prove<00:14:48.240> from<00:14:48.420> a<00:14:48.600> group<00:14:48.779> to<00:14:49.199> create<00:14:49.320> from<00:14:49.920> a 00:14:50.030 --> 00:14:50.040 align:start position:0% prove from a group to create from a 00:14:50.040 --> 00:14:52.009 align:start position:0% prove from a group to create from a group<00:14:50.220> SDK<00:14:50.699> badge<00:14:51.060> and<00:14:51.420> actually<00:14:51.540> this<00:14:51.839> is<00:14:51.899> a 00:14:52.009 --> 00:14:52.019 align:start position:0% group SDK badge and actually this is a 00:14:52.019 --> 00:14:55.129 align:start position:0% group SDK badge and actually this is a complete<00:14:52.440> accessor<00:14:52.860> anyone<00:14:53.699> here<00:14:54.360> in<00:14:54.540> the<00:14:54.779> in 00:14:55.129 --> 00:14:55.139 align:start position:0% complete accessor anyone here in the in 00:14:55.139 --> 00:14:57.350 align:start position:0% complete accessor anyone here in the in the<00:14:55.260> room<00:14:55.440> can<00:14:56.100> create<00:14:56.339> its<00:14:56.760> own<00:14:56.760> Decay<00:14:57.180> batch 00:14:57.350 --> 00:14:57.360 align:start position:0% the room can create its own Decay batch 00:14:57.360 --> 00:14:58.670 align:start position:0% the room can create its own Decay batch that's<00:14:57.540> what<00:14:57.660> we<00:14:57.839> build<00:14:57.959> system<00:14:58.139> we're<00:14:58.500> going 00:14:58.670 --> 00:14:58.680 align:start position:0% that's what we build system we're going 00:14:58.680 --> 00:14:59.870 align:start position:0% that's what we build system we're going to<00:14:58.800> build<00:14:59.100> this<00:14:59.279> mode<00:14:59.399> to<00:14:59.639> do<00:14:59.760> some 00:14:59.870 --> 00:14:59.880 align:start position:0% to build this mode to do some 00:14:59.880 --> 00:15:01.550 align:start position:0% to build this mode to do some Partnerships<00:15:00.300> or<00:15:00.540> stuff<00:15:00.720> like<00:15:00.839> that<00:15:01.019> it's<00:15:01.380> a 00:15:01.550 --> 00:15:01.560 align:start position:0% Partnerships or stuff like that it's a 00:15:01.560 --> 00:15:03.170 align:start position:0% Partnerships or stuff like that it's a primitive<00:15:01.980> everything<00:15:02.339> is<00:15:02.579> open<00:15:02.699> source<00:15:03.120> of 00:15:03.170 --> 00:15:03.180 align:start position:0% primitive everything is open source of 00:15:03.180 --> 00:15:06.350 align:start position:0% primitive everything is open source of course<00:15:03.420> and<00:15:04.260> very<00:15:04.980> easily<00:15:05.279> in<00:15:05.639> 15<00:15:05.760> minutes<00:15:06.000> if 00:15:06.350 --> 00:15:06.360 align:start position:0% course and very easily in 15 minutes if 00:15:06.360 --> 00:15:09.009 align:start position:0% course and very easily in 15 minutes if you<00:15:06.480> are<00:15:06.600> developers<00:15:07.220> we<00:15:08.220> have<00:15:08.339> a<00:15:08.459> tutorial 00:15:09.009 --> 00:15:09.019 align:start position:0% you are developers we have a tutorial 00:15:09.019 --> 00:15:12.410 align:start position:0% you are developers we have a tutorial that<00:15:10.019> helps<00:15:10.560> you<00:15:10.620> with<00:15:10.740> that<00:15:10.920> you<00:15:11.519> can<00:15:11.639> fetch 00:15:12.410 --> 00:15:12.420 align:start position:0% that helps you with that you can fetch 00:15:12.420 --> 00:15:14.449 align:start position:0% that helps you with that you can fetch from<00:15:12.600> your<00:15:12.720> subgraph<00:15:13.260> from<00:15:13.620> bigquery<00:15:14.100> from 00:15:14.449 --> 00:15:14.459 align:start position:0% from your subgraph from bigquery from 00:15:14.459 --> 00:15:16.790 align:start position:0% from your subgraph from bigquery from anything<00:15:14.579> you<00:15:15.180> can<00:15:15.300> fetch<00:15:15.720> your<00:15:15.839> group<00:15:16.019> choose 00:15:16.790 --> 00:15:16.800 align:start position:0% anything you can fetch your group choose 00:15:16.800 --> 00:15:18.350 align:start position:0% anything you can fetch your group choose the<00:15:16.920> metadata<00:15:17.399> for<00:15:17.519> your<00:15:17.639> badge<00:15:17.940> choose<00:15:18.240> the 00:15:18.350 --> 00:15:18.360 align:start position:0% the metadata for your badge choose the 00:15:18.360 --> 00:15:21.350 align:start position:0% the metadata for your badge choose the visual<00:15:18.660> and<00:15:18.899> that's<00:15:19.019> done<00:15:19.260> so<00:15:19.680> again<00:15:20.360> anybody 00:15:21.350 --> 00:15:21.360 align:start position:0% visual and that's done so again anybody 00:15:21.360 --> 00:15:23.569 align:start position:0% visual and that's done so again anybody can<00:15:21.600> create<00:15:21.779> this<00:15:22.019> DK<00:15:22.380> badge<00:15:22.680> can<00:15:23.160> create<00:15:23.339> the 00:15:23.569 --> 00:15:23.579 align:start position:0% can create this DK badge can create the 00:15:23.579 --> 00:15:25.790 align:start position:0% can create this DK badge can create the group<00:15:23.699> SDK<00:15:24.300> version<00:15:24.540> and<00:15:25.139> we<00:15:25.380> just<00:15:25.560> released 00:15:25.790 --> 00:15:25.800 align:start position:0% group SDK version and we just released 00:15:25.800 --> 00:15:28.069 align:start position:0% group SDK version and we just released today<00:15:26.040> the<00:15:26.399> factory<00:15:26.579> of<00:15:26.880> sismo<00:15:27.360> it<00:15:27.600> allows<00:15:27.899> for 00:15:28.069 --> 00:15:28.079 align:start position:0% today the factory of sismo it allows for 00:15:28.079 --> 00:15:30.710 align:start position:0% today the factory of sismo it allows for even<00:15:28.500> people<00:15:28.800> that<00:15:29.100> are<00:15:29.339> neither<00:15:29.699> coder<00:15:30.300> or 00:15:30.710 --> 00:15:30.720 align:start position:0% even people that are neither coder or 00:15:30.720 --> 00:15:33.530 align:start position:0% even people that are neither coder or designer<00:15:31.260> to<00:15:31.500> build<00:15:31.620> a<00:15:31.860> GK<00:15:32.220> badge<00:15:32.579> it<00:15:33.300> works 00:15:33.530 --> 00:15:33.540 align:start position:0% designer to build a GK badge it works 00:15:33.540 --> 00:15:36.170 align:start position:0% designer to build a GK badge it works that<00:15:33.660> way<00:15:33.839> you<00:15:34.440> you<00:15:34.740> add<00:15:34.980> metadata<00:15:35.639> we<00:15:35.940> have<00:15:36.060> a 00:15:36.170 --> 00:15:36.180 align:start position:0% that way you you add metadata we have a 00:15:36.180 --> 00:15:38.509 align:start position:0% that way you you add metadata we have a SVGA<00:15:36.600> Editor<00:15:37.019> to<00:15:37.139> create<00:15:37.260> your<00:15:37.440> CK<00:15:37.800> badge<00:15:38.160> and 00:15:38.509 --> 00:15:38.519 align:start position:0% SVGA Editor to create your CK badge and 00:15:38.519 --> 00:15:39.949 align:start position:0% SVGA Editor to create your CK badge and then<00:15:38.639> you<00:15:38.760> have<00:15:38.880> just<00:15:39.060> to<00:15:39.240> copy<00:15:39.540> past<00:15:39.660> the<00:15:39.839> list 00:15:39.949 --> 00:15:39.959 align:start position:0% then you have just to copy past the list 00:15:39.959 --> 00:15:42.230 align:start position:0% then you have just to copy past the list of<00:15:40.139> address<00:15:40.320> you<00:15:40.860> push<00:15:41.279> the<00:15:41.399> button<00:15:41.699> and<00:15:41.940> done 00:15:42.230 --> 00:15:42.240 align:start position:0% of address you push the button and done 00:15:42.240 --> 00:15:44.090 align:start position:0% of address you push the button and done you<00:15:42.779> have<00:15:42.839> your<00:15:43.019> ZK<00:15:43.320> badge<00:15:43.560> available<00:15:43.680> so 00:15:44.090 --> 00:15:44.100 align:start position:0% you have your ZK badge available so 00:15:44.100 --> 00:15:46.250 align:start position:0% you have your ZK badge available so that's<00:15:44.339> I<00:15:44.699> think<00:15:44.820> that's<00:15:44.940> super<00:15:45.120> great<00:15:45.360> so<00:15:46.079> I 00:15:46.250 --> 00:15:46.260 align:start position:0% that's I think that's super great so I 00:15:46.260 --> 00:15:49.009 align:start position:0% that's I think that's super great so I invite<00:15:46.680> you<00:15:46.740> to<00:15:46.920> try<00:15:47.459> that 00:15:49.009 --> 00:15:49.019 align:start position:0% invite you to try that 00:15:49.019 --> 00:15:51.829 align:start position:0% invite you to try that um and<00:15:49.800> before<00:15:50.040> that<00:15:50.339> I'd<00:15:50.880> like<00:15:51.060> to<00:15:51.240> before 00:15:51.829 --> 00:15:51.839 align:start position:0% um and before that I'd like to before 00:15:51.839 --> 00:15:52.850 align:start position:0% um and before that I'd like to before getting 00:15:52.850 --> 00:15:52.860 align:start position:0% getting 00:15:52.860 --> 00:15:54.949 align:start position:0% getting yeah<00:15:53.279> now<00:15:53.760> I<00:15:54.000> want<00:15:54.180> to<00:15:54.300> speak<00:15:54.480> about<00:15:54.660> the 00:15:54.949 --> 00:15:54.959 align:start position:0% yeah now I want to speak about the 00:15:54.959 --> 00:15:58.069 align:start position:0% yeah now I want to speak about the protocol<00:15:55.380> so<00:15:56.339> we<00:15:56.940> saw<00:15:57.120> that<00:15:57.360> this<00:15:57.540> one<00:15:57.779> is<00:15:57.959> open 00:15:58.069 --> 00:15:58.079 align:start position:0% protocol so we saw that this one is open 00:15:58.079 --> 00:16:00.290 align:start position:0% protocol so we saw that this one is open anybody<00:15:58.740> can<00:15:58.920> add<00:15:59.100> its<00:15:59.459> group<00:15:59.579> it<00:16:00.060> will<00:16:00.180> have 00:16:00.290 --> 00:16:00.300 align:start position:0% anybody can add its group it will have 00:16:00.300 --> 00:16:02.629 align:start position:0% anybody can add its group it will have your<00:16:00.600> their<00:16:01.079> own<00:16:01.260> ZK<00:16:01.680> badge<00:16:01.980> for<00:16:02.100> their<00:16:02.339> user 00:16:02.629 --> 00:16:02.639 align:start position:0% your their own ZK badge for their user 00:16:02.639 --> 00:16:05.449 align:start position:0% your their own ZK badge for their user Community<00:16:02.820> but<00:16:03.660> even<00:16:03.899> better<00:16:04.139> actually<00:16:04.560> so 00:16:05.449 --> 00:16:05.459 align:start position:0% Community but even better actually so 00:16:05.459 --> 00:16:07.189 align:start position:0% Community but even better actually so that's<00:16:05.880> what<00:16:06.060> I<00:16:06.180> told<00:16:06.360> you<00:16:06.420> about<00:16:06.540> anybody<00:16:06.959> can 00:16:07.189 --> 00:16:07.199 align:start position:0% that's what I told you about anybody can 00:16:07.199 --> 00:16:09.230 align:start position:0% that's what I told you about anybody can add<00:16:07.380> this<00:16:07.560> group<00:16:07.860> you<00:16:08.220> get<00:16:08.339> the<00:16:08.459> batch<00:16:08.760> now 00:16:09.230 --> 00:16:09.240 align:start position:0% add this group you get the batch now 00:16:09.240 --> 00:16:11.750 align:start position:0% add this group you get the batch now which<00:16:09.480> is<00:16:09.720> even<00:16:09.899> greater<00:16:10.320> for<00:16:11.040> more<00:16:11.339> advanced 00:16:11.750 --> 00:16:11.760 align:start position:0% which is even greater for more advanced 00:16:11.760 --> 00:16:14.629 align:start position:0% which is even greater for more advanced developers<00:16:12.500> is<00:16:13.500> to<00:16:13.920> create<00:16:14.160> your<00:16:14.519> own 00:16:14.629 --> 00:16:14.639 align:start position:0% developers is to create your own 00:16:14.639 --> 00:16:17.509 align:start position:0% developers is to create your own accessor<00:16:15.360> instead<00:16:16.079> of<00:16:16.199> you<00:16:16.440> using<00:16:16.980> the<00:16:17.160> rules 00:16:17.509 --> 00:16:17.519 align:start position:0% accessor instead of you using the rules 00:16:17.519 --> 00:16:20.230 align:start position:0% accessor instead of you using the rules of<00:16:17.639> Hydra<00:16:18.000> S1<00:16:18.360> I<00:16:18.540> told<00:16:18.660> you<00:16:18.779> verify<00:16:19.260> membership 00:16:20.230 --> 00:16:20.240 align:start position:0% of Hydra S1 I told you verify membership 00:16:20.240 --> 00:16:23.030 align:start position:0% of Hydra S1 I told you verify membership verify<00:16:21.240> ownership<00:16:21.540> you<00:16:22.199> can<00:16:22.260> create<00:16:22.440> your<00:16:22.740> own 00:16:23.030 --> 00:16:23.040 align:start position:0% verify ownership you can create your own 00:16:23.040 --> 00:16:27.290 align:start position:0% verify ownership you can create your own new<00:16:23.339> rules<00:16:23.639> to<00:16:24.180> verify<00:16:24.660> the<00:16:25.560> user<00:16:25.980> request<00:16:26.579> so 00:16:27.290 --> 00:16:27.300 align:start position:0% new rules to verify the user request so 00:16:27.300 --> 00:16:29.750 align:start position:0% new rules to verify the user request so for<00:16:27.540> instance<00:16:27.779> you<00:16:28.320> can<00:16:28.440> use<00:16:28.620> simr4<00:16:29.399> it's 00:16:29.750 --> 00:16:29.760 align:start position:0% for instance you can use simr4 it's 00:16:29.760 --> 00:16:31.550 align:start position:0% for instance you can use simr4 it's another<00:16:30.000> SDK<00:16:30.540> scheme<00:16:30.839> that<00:16:30.959> will<00:16:31.079> be<00:16:31.199> SDK 00:16:31.550 --> 00:16:31.560 align:start position:0% another SDK scheme that will be SDK 00:16:31.560 --> 00:16:33.530 align:start position:0% another SDK scheme that will be SDK tester<00:16:31.980> but<00:16:32.459> you<00:16:32.639> can<00:16:32.760> also<00:16:33.000> use<00:16:33.240> a<00:16:33.420> public 00:16:33.530 --> 00:16:33.540 align:start position:0% tester but you can also use a public 00:16:33.540 --> 00:16:36.110 align:start position:0% tester but you can also use a public accessor<00:16:34.260> like<00:16:34.860> the<00:16:35.399> proof<00:16:35.699> that<00:16:35.820> you<00:16:36.000> would 00:16:36.110 --> 00:16:36.120 align:start position:0% accessor like the proof that you would 00:16:36.120 --> 00:16:37.910 align:start position:0% accessor like the proof that you would require<00:16:36.360> from<00:16:36.660> user<00:16:36.959> is<00:16:37.079> not<00:16:37.199> a<00:16:37.259> ZK<00:16:37.560> proof<00:16:37.800> but 00:16:37.910 --> 00:16:37.920 align:start position:0% require from user is not a ZK proof but 00:16:37.920 --> 00:16:39.889 align:start position:0% require from user is not a ZK proof but a<00:16:38.100> worker<00:16:38.519> proof<00:16:38.759> and<00:16:39.120> the<00:16:39.240> signature<00:16:39.660> easy 00:16:39.889 --> 00:16:39.899 align:start position:0% a worker proof and the signature easy 00:16:39.899 --> 00:16:42.050 align:start position:0% a worker proof and the signature easy recover<00:16:40.380> or<00:16:40.980> you<00:16:41.100> could<00:16:41.279> even<00:16:41.459> create<00:16:41.759> a 00:16:42.050 --> 00:16:42.060 align:start position:0% recover or you could even create a 00:16:42.060 --> 00:16:44.030 align:start position:0% recover or you could even create a centralized<00:16:42.779> adjuster<00:16:43.199> meaning<00:16:43.440> that<00:16:43.740> the 00:16:44.030 --> 00:16:44.040 align:start position:0% centralized adjuster meaning that the 00:16:44.040 --> 00:16:45.350 align:start position:0% centralized adjuster meaning that the proof<00:16:44.279> that<00:16:44.339> you<00:16:44.459> have<00:16:44.639> to<00:16:44.699> send<00:16:44.880> to<00:16:45.060> get<00:16:45.180> your 00:16:45.350 --> 00:16:45.360 align:start position:0% proof that you have to send to get your 00:16:45.360 --> 00:16:47.210 align:start position:0% proof that you have to send to get your badge<00:16:45.720> is<00:16:46.019> a<00:16:46.199> signature<00:16:46.620> of<00:16:46.740> the<00:16:46.800> third<00:16:46.980> party 00:16:47.210 --> 00:16:47.220 align:start position:0% badge is a signature of the third party 00:16:47.220 --> 00:16:49.310 align:start position:0% badge is a signature of the third party so<00:16:48.000> again<00:16:48.300> that's<00:16:48.600> that's<00:16:48.779> what<00:16:49.019> we're<00:16:49.139> trying 00:16:49.310 --> 00:16:49.320 align:start position:0% so again that's that's what we're trying 00:16:49.320 --> 00:16:51.110 align:start position:0% so again that's that's what we're trying to<00:16:49.500> do<00:16:49.620> is<00:16:49.860> really<00:16:50.040> primitive<00:16:50.519> we're<00:16:50.759> not<00:16:50.940> here 00:16:51.110 --> 00:16:51.120 align:start position:0% to do is really primitive we're not here 00:16:51.120 --> 00:16:52.370 align:start position:0% to do is really primitive we're not here to 00:16:52.370 --> 00:16:52.380 align:start position:0% to 00:16:52.380 --> 00:16:55.370 align:start position:0% to yeah<00:16:52.980> we<00:16:53.279> want<00:16:53.579> you<00:16:53.880> to<00:16:54.300> have<00:16:54.720> fun<00:16:54.899> with<00:16:55.139> this 00:16:55.370 --> 00:16:55.380 align:start position:0% yeah we want you to have fun with this 00:16:55.380 --> 00:16:57.530 align:start position:0% yeah we want you to have fun with this so<00:16:55.680> that<00:16:55.800> you<00:16:56.040> can<00:16:56.220> really<00:16:56.579> control<00:16:56.880> the<00:16:57.240> data 00:16:57.530 --> 00:16:57.540 align:start position:0% so that you can really control the data 00:16:57.540 --> 00:17:00.290 align:start position:0% so that you can really control the data of<00:16:57.600> your<00:16:57.779> users<00:16:58.160> and<00:16:59.160> and<00:16:59.579> that<00:16:59.820> you<00:16:59.940> can<00:17:00.060> build 00:17:00.290 --> 00:17:00.300 align:start position:0% of your users and and that you can build 00:17:00.300 --> 00:17:03.829 align:start position:0% of your users and and that you can build weird<00:17:00.540> stuff<00:17:00.839> like<00:17:01.019> if<00:17:01.320> I<00:17:01.620> did<00:17:01.740> in<00:17:02.220> 2020<00:17:02.820> it<00:17:03.660> did 00:17:03.829 --> 00:17:03.839 align:start position:0% weird stuff like if I did in 2020 it did 00:17:03.839 --> 00:17:05.150 align:start position:0% weird stuff like if I did in 2020 it did real<00:17:04.020> stuff<00:17:04.260> with<00:17:04.439> composability<00:17:04.919> between 00:17:05.150 --> 00:17:05.160 align:start position:0% real stuff with composability between 00:17:05.160 --> 00:17:07.130 align:start position:0% real stuff with composability between all<00:17:05.520> the<00:17:05.699> financial<00:17:05.939> applications<00:17:06.540> here<00:17:06.959> what 00:17:07.130 --> 00:17:07.140 align:start position:0% all the financial applications here what 00:17:07.140 --> 00:17:08.870 align:start position:0% all the financial applications here what we<00:17:07.319> want<00:17:07.439> to<00:17:07.559> do<00:17:07.679> is<00:17:07.919> we'll<00:17:08.160> stuff<00:17:08.459> about<00:17:08.699> the 00:17:08.870 --> 00:17:08.880 align:start position:0% we want to do is we'll stuff about the 00:17:08.880 --> 00:17:11.210 align:start position:0% we want to do is we'll stuff about the social<00:17:09.059> capital<00:17:09.299> that<00:17:09.720> you<00:17:09.839> have<00:17:09.959> so 00:17:11.210 --> 00:17:11.220 align:start position:0% social capital that you have so 00:17:11.220 --> 00:17:13.010 align:start position:0% social capital that you have so that's<00:17:11.699> it<00:17:11.819> again<00:17:12.059> all<00:17:12.299> these<00:17:12.540> open<00:17:12.660> source 00:17:13.010 --> 00:17:13.020 align:start position:0% that's it again all these open source 00:17:13.020 --> 00:17:15.890 align:start position:0% that's it again all these open source invite<00:17:13.319> you<00:17:13.439> to<00:17:13.559> read<00:17:13.679> the<00:17:13.860> docs<00:17:14.160> and<00:17:14.939> I'll<00:17:15.780> get 00:17:15.890 --> 00:17:15.900 align:start position:0% invite you to read the docs and I'll get 00:17:15.900 --> 00:17:18.110 align:start position:0% invite you to read the docs and I'll get that<00:17:16.079> so<00:17:16.500> now<00:17:16.620> we<00:17:16.799> get<00:17:16.980> back<00:17:17.160> a<00:17:17.339> bit<00:17:17.520> uh<00:17:17.880> to 00:17:18.110 --> 00:17:18.120 align:start position:0% that so now we get back a bit uh to 00:17:18.120 --> 00:17:20.270 align:start position:0% that so now we get back a bit uh to recap<00:17:18.419> a<00:17:18.600> bit<00:17:18.780> so<00:17:19.199> what<00:17:19.500> it<00:17:19.679> allows<00:17:19.980> you<00:17:19.980> to<00:17:20.160> do 00:17:20.270 --> 00:17:20.280 align:start position:0% recap a bit so what it allows you to do 00:17:20.280 --> 00:17:22.250 align:start position:0% recap a bit so what it allows you to do I<00:17:20.699> told<00:17:20.819> you<00:17:20.939> that<00:17:21.120> it<00:17:21.360> allows<00:17:21.959> you<00:17:22.020> to<00:17:22.140> import 00:17:22.250 --> 00:17:22.260 align:start position:0% I told you that it allows you to import 00:17:22.260 --> 00:17:24.650 align:start position:0% I told you that it allows you to import reputation<00:17:22.740> from<00:17:23.699> the<00:17:23.819> public<00:17:24.000> to<00:17:24.240> an<00:17:24.419> unknown 00:17:24.650 --> 00:17:24.660 align:start position:0% reputation from the public to an unknown 00:17:24.660 --> 00:17:26.929 align:start position:0% reputation from the public to an unknown wallet<00:17:25.020> but<00:17:25.260> you<00:17:25.380> can<00:17:25.500> do<00:17:25.620> the<00:17:25.919> reverse<00:17:26.339> again 00:17:26.929 --> 00:17:26.939 align:start position:0% wallet but you can do the reverse again 00:17:26.939 --> 00:17:30.110 align:start position:0% wallet but you can do the reverse again if<00:17:27.299> I<00:17:27.419> was<00:17:27.540> a<00:17:27.720> degener<00:17:28.140> in<00:17:28.380> my<00:17:28.500> and<00:17:28.919> on<00:17:29.100> wallet<00:17:29.400> I 00:17:30.110 --> 00:17:30.120 align:start position:0% if I was a degener in my and on wallet I 00:17:30.120 --> 00:17:31.430 align:start position:0% if I was a degener in my and on wallet I could<00:17:30.240> import<00:17:30.419> this<00:17:30.720> reputation<00:17:31.140> to<00:17:31.320> my 00:17:31.430 --> 00:17:31.440 align:start position:0% could import this reputation to my 00:17:31.440 --> 00:17:34.930 align:start position:0% could import this reputation to my public<00:17:31.620> wallet<00:17:32.040> have<00:17:32.400> ethernet<00:17:32.940> power<00:17:33.179> users 00:17:34.930 --> 00:17:34.940 align:start position:0% public wallet have ethernet power users 00:17:34.940 --> 00:17:39.710 align:start position:0% public wallet have ethernet power users only<00:17:35.940> top<00:17:36.799> 0.1<00:17:37.799> percent<00:17:38.340> ethernet<00:17:39.299> users<00:17:39.539> can 00:17:39.710 --> 00:17:39.720 align:start position:0% only top 0.1 percent ethernet users can 00:17:39.720 --> 00:17:41.630 align:start position:0% only top 0.1 percent ethernet users can means<00:17:40.020> and<00:17:40.320> so<00:17:40.440> that<00:17:40.620> way<00:17:40.740> approved<00:17:41.220> as<00:17:41.400> they 00:17:41.630 --> 00:17:41.640 align:start position:0% means and so that way approved as they 00:17:41.640 --> 00:17:44.690 align:start position:0% means and so that way approved as they generated<00:17:42.120> that<00:17:42.900> I'm<00:17:43.080> a<00:17:43.320> Degen<00:17:43.620> but<00:17:43.860> I<00:17:44.580> never 00:17:44.690 --> 00:17:44.700 align:start position:0% generated that I'm a Degen but I never 00:17:44.700 --> 00:17:48.289 align:start position:0% generated that I'm a Degen but I never revealed<00:17:45.179> my<00:17:45.360> wallet<00:17:46.140> so<00:17:46.860> that's<00:17:47.640> yeah<00:17:48.000> when 00:17:48.289 --> 00:17:48.299 align:start position:0% revealed my wallet so that's yeah when 00:17:48.299 --> 00:17:49.909 align:start position:0% revealed my wallet so that's yeah when do<00:17:48.480> you<00:17:48.660> think<00:17:48.720> the<00:17:49.020> other<00:17:49.140> thing<00:17:49.380> if<00:17:49.799> you 00:17:49.909 --> 00:17:49.919 align:start position:0% do you think the other thing if you 00:17:49.919 --> 00:17:52.669 align:start position:0% do you think the other thing if you think<00:17:50.100> about<00:17:50.220> it<00:17:50.520> what<00:17:51.240> happens<00:17:51.480> if<00:17:52.080> I<00:17:52.440> mint 00:17:52.669 --> 00:17:52.679 align:start position:0% think about it what happens if I mint 00:17:52.679 --> 00:17:55.250 align:start position:0% think about it what happens if I mint the<00:17:52.980> badge<00:17:53.340> on<00:17:54.120> a<00:17:54.360> one-time<00:17:54.600> address<00:17:54.780> fresh 00:17:55.250 --> 00:17:55.260 align:start position:0% the badge on a one-time address fresh 00:17:55.260 --> 00:17:57.409 align:start position:0% the badge on a one-time address fresh new<00:17:55.500> address<00:17:55.679> What<00:17:56.400> I've<00:17:56.640> Done<00:17:56.820> by<00:17:56.940> doing<00:17:57.120> this 00:17:57.409 --> 00:17:57.419 align:start position:0% new address What I've Done by doing this 00:17:57.419 --> 00:17:59.990 align:start position:0% new address What I've Done by doing this is<00:17:58.020> that<00:17:58.140> I'm<00:17:58.320> able<00:17:58.620> to<00:17:58.679> reveal<00:17:59.160> just<00:17:59.580> exactly 00:17:59.990 --> 00:18:00.000 align:start position:0% is that I'm able to reveal just exactly 00:18:00.000 --> 00:18:02.090 align:start position:0% is that I'm able to reveal just exactly what<00:18:00.179> I<00:18:00.360> need<00:18:00.480> it's<00:18:01.200> not<00:18:01.380> about<00:18:01.559> building<00:18:01.860> an 00:18:02.090 --> 00:18:02.100 align:start position:0% what I need it's not about building an 00:18:02.100 --> 00:18:04.549 align:start position:0% what I need it's not about building an identity<00:18:02.520> is<00:18:02.880> to<00:18:03.179> I<00:18:03.840> need<00:18:04.140> to<00:18:04.260> prove<00:18:04.440> to 00:18:04.549 --> 00:18:04.559 align:start position:0% identity is to I need to prove to 00:18:04.559 --> 00:18:07.430 align:start position:0% identity is to I need to prove to someone<00:18:04.740> that<00:18:05.100> I<00:18:05.940> meet<00:18:06.059> some<00:18:06.240> quitter<00:18:06.600> yeah<00:18:06.900> I 00:18:07.430 --> 00:18:07.440 align:start position:0% someone that I meet some quitter yeah I 00:18:07.440 --> 00:18:08.750 align:start position:0% someone that I meet some quitter yeah I create<00:18:07.559> a<00:18:07.740> new<00:18:07.860> address<00:18:07.980> I'm<00:18:08.280> in<00:18:08.460> the<00:18:08.580> batch 00:18:08.750 --> 00:18:08.760 align:start position:0% create a new address I'm in the batch 00:18:08.760 --> 00:18:10.669 align:start position:0% create a new address I'm in the batch there<00:18:09.000> and<00:18:09.539> I<00:18:09.660> will<00:18:09.780> also<00:18:10.020> prove<00:18:10.200> exactly<00:18:10.500> what 00:18:10.669 --> 00:18:10.679 align:start position:0% there and I will also prove exactly what 00:18:10.679 --> 00:18:12.950 align:start position:0% there and I will also prove exactly what I<00:18:10.799> need<00:18:10.980> so<00:18:11.400> here<00:18:11.580> on<00:18:11.760> the<00:18:11.880> adrian.e<00:18:12.480> again<00:18:12.780> I 00:18:12.950 --> 00:18:12.960 align:start position:0% I need so here on the adrian.e again I 00:18:12.960 --> 00:18:14.990 align:start position:0% I need so here on the adrian.e again I have<00:18:13.080> a<00:18:13.140> lot<00:18:13.260> of<00:18:13.380> data<00:18:13.740> one<00:18:14.280> of<00:18:14.460> the<00:18:14.580> data<00:18:14.820> that 00:18:14.990 --> 00:18:15.000 align:start position:0% have a lot of data one of the data that 00:18:15.000 --> 00:18:17.690 align:start position:0% have a lot of data one of the data that is<00:18:15.179> mine<00:18:15.360> sorry<00:18:15.660> is<00:18:16.440> that<00:18:16.620> I<00:18:17.100> have<00:18:17.220> a<00:18:17.340> lot<00:18:17.460> I 00:18:17.690 --> 00:18:17.700 align:start position:0% is mine sorry is that I have a lot I 00:18:17.700 --> 00:18:21.049 align:start position:0% is mine sorry is that I have a lot I have<00:18:17.880> the<00:18:18.059> HTC<00:18:18.480> prep<00:18:19.200> and<00:18:19.740> thanks<00:18:19.919> to<00:18:20.160> this<00:18:20.340> I 00:18:21.049 --> 00:18:21.059 align:start position:0% have the HTC prep and thanks to this I 00:18:21.059 --> 00:18:23.390 align:start position:0% have the HTC prep and thanks to this I can<00:18:21.240> get<00:18:21.900> I'm<00:18:22.200> eligible<00:18:22.679> to<00:18:22.980> the<00:18:23.100> proof<00:18:23.340> of 00:18:23.390 --> 00:18:23.400 align:start position:0% can get I'm eligible to the proof of 00:18:23.400 --> 00:18:25.850 align:start position:0% can get I'm eligible to the proof of attendance<00:18:24.080> behind<00:18:25.080> this<00:18:25.200> Decay<00:18:25.559> batch<00:18:25.740> the 00:18:25.850 --> 00:18:25.860 align:start position:0% attendance behind this Decay batch the 00:18:25.860 --> 00:18:27.409 align:start position:0% attendance behind this Decay batch the group<00:18:25.980> of<00:18:26.100> eligible<00:18:26.400> user<00:18:26.820> is<00:18:26.940> people<00:18:27.179> that 00:18:27.409 --> 00:18:27.419 align:start position:0% group of eligible user is people that 00:18:27.419 --> 00:18:30.230 align:start position:0% group of eligible user is people that went<00:18:27.600> to<00:18:27.780> either<00:18:28.080> a<00:18:28.380> Defcon<00:18:28.799> or<00:18:29.039> HTC<00:18:29.580> or<00:18:30.000> eat 00:18:30.230 --> 00:18:30.240 align:start position:0% went to either a Defcon or HTC or eat 00:18:30.240 --> 00:18:33.110 align:start position:0% went to either a Defcon or HTC or eat Berlin<00:18:30.600> very<00:18:31.320> legit<00:18:31.740> physical<00:18:31.919> events<00:18:32.520> and<00:18:33.000> so 00:18:33.110 --> 00:18:33.120 align:start position:0% Berlin very legit physical events and so 00:18:33.120 --> 00:18:34.549 align:start position:0% Berlin very legit physical events and so I'm<00:18:33.240> able<00:18:33.480> to<00:18:33.539> mean<00:18:33.720> that<00:18:33.900> to<00:18:34.080> a<00:18:34.260> fresh<00:18:34.380> new 00:18:34.549 --> 00:18:34.559 align:start position:0% I'm able to mean that to a fresh new 00:18:34.559 --> 00:18:36.230 align:start position:0% I'm able to mean that to a fresh new address<00:18:34.799> and<00:18:35.280> then<00:18:35.400> I<00:18:35.520> can<00:18:35.640> use<00:18:35.820> this<00:18:36.059> address 00:18:36.230 --> 00:18:36.240 align:start position:0% address and then I can use this address 00:18:36.240 --> 00:18:38.029 align:start position:0% address and then I can use this address to<00:18:36.960> for<00:18:37.200> instance<00:18:37.320> get<00:18:37.620> private 00:18:38.029 --> 00:18:38.039 align:start position:0% to for instance get private 00:18:38.039 --> 00:18:40.970 align:start position:0% to for instance get private merchandising<00:18:38.940> or<00:18:39.360> access<00:18:39.900> air<00:18:40.320> jobs<00:18:40.559> to<00:18:40.860> get 00:18:40.970 --> 00:18:40.980 align:start position:0% merchandising or access air jobs to get 00:18:40.980 --> 00:18:43.490 align:start position:0% merchandising or access air jobs to get into<00:18:41.160> events<00:18:41.700> and<00:18:42.480> with<00:18:42.720> this<00:18:42.960> what<00:18:43.140> I<00:18:43.380> was 00:18:43.490 --> 00:18:43.500 align:start position:0% into events and with this what I was 00:18:43.500 --> 00:18:45.830 align:start position:0% into events and with this what I was able<00:18:43.860> to<00:18:43.919> do<00:18:44.039> is<00:18:44.160> prove<00:18:44.460> that<00:18:44.640> I<00:18:45.179> went<00:18:45.360> into<00:18:45.539> one 00:18:45.830 --> 00:18:45.840 align:start position:0% able to do is prove that I went into one 00:18:45.840 --> 00:18:48.409 align:start position:0% able to do is prove that I went into one of<00:18:46.020> the<00:18:46.140> top<00:18:46.260> conferences<00:18:46.799> that<00:18:47.340> I'm<00:18:47.520> a<00:18:47.640> human 00:18:48.409 --> 00:18:48.419 align:start position:0% of the top conferences that I'm a human 00:18:48.419 --> 00:18:50.930 align:start position:0% of the top conferences that I'm a human and<00:18:49.260> not<00:18:49.500> that<00:18:49.740> I<00:18:49.860> went<00:18:49.980> with<00:18:50.160> no<00:18:50.640> time<00:18:50.760> the 00:18:50.930 --> 00:18:50.940 align:start position:0% and not that I went with no time the 00:18:50.940 --> 00:18:53.090 align:start position:0% and not that I went with no time the Adrian<00:18:51.179> that<00:18:51.360> is<00:18:51.480> that's<00:18:51.840> that's<00:18:52.140> leveraging 00:18:53.090 --> 00:18:53.100 align:start position:0% Adrian that is that's that's leveraging 00:18:53.100 --> 00:18:54.890 align:start position:0% Adrian that is that's that's leveraging your<00:18:53.280> data<00:18:53.520> that's<00:18:53.700> what<00:18:53.820> we<00:18:53.940> call<00:18:54.120> it<00:18:54.240> so<00:18:54.720> it's 00:18:54.890 --> 00:18:54.900 align:start position:0% your data that's what we call it so it's 00:18:54.900 --> 00:18:57.169 align:start position:0% your data that's what we call it so it's super<00:18:55.020> excited<00:18:55.380> about<00:18:55.679> this<00:18:56.340> the<00:18:56.820> last<00:18:57.000> thing 00:18:57.169 --> 00:18:57.179 align:start position:0% super excited about this the last thing 00:18:57.179 --> 00:18:59.510 align:start position:0% super excited about this the last thing that<00:18:57.539> we<00:18:57.840> intend<00:18:58.140> to<00:18:58.260> do<00:18:58.380> that<00:18:58.559> is<00:18:58.679> not<00:18:58.860> life<00:18:59.100> is 00:18:59.510 --> 00:18:59.520 align:start position:0% that we intend to do that is not life is 00:18:59.520 --> 00:19:01.549 align:start position:0% that we intend to do that is not life is the<00:18:59.640> way<00:18:59.820> to<00:18:59.940> aggregate<00:19:00.480> your<00:19:00.660> reputation 00:19:01.549 --> 00:19:01.559 align:start position:0% the way to aggregate your reputation 00:19:01.559 --> 00:19:03.890 align:start position:0% the way to aggregate your reputation in<00:19:02.100> cismo<00:19:02.580> our<00:19:02.880> governance<00:19:03.240> is<00:19:03.419> not<00:19:03.600> token 00:19:03.890 --> 00:19:03.900 align:start position:0% in cismo our governance is not token 00:19:03.900 --> 00:19:05.930 align:start position:0% in cismo our governance is not token based<00:19:04.260> oh<00:19:04.380> it<00:19:04.559> is<00:19:04.679> token<00:19:05.100> basement<00:19:05.280> but<00:19:05.760> not 00:19:05.930 --> 00:19:05.940 align:start position:0% based oh it is token basement but not 00:19:05.940 --> 00:19:09.049 align:start position:0% based oh it is token basement but not Financial<00:19:06.539> token<00:19:07.140> based<00:19:07.440> it's<00:19:07.980> been<00:19:08.160> is<00:19:08.760> based 00:19:09.049 --> 00:19:09.059 align:start position:0% Financial token based it's been is based 00:19:09.059 --> 00:19:10.730 align:start position:0% Financial token based it's been is based on<00:19:09.179> contributions<00:19:09.720> meaning<00:19:10.080> that<00:19:10.380> the<00:19:10.620> more 00:19:10.730 --> 00:19:10.740 align:start position:0% on contributions meaning that the more 00:19:10.740 --> 00:19:13.190 align:start position:0% on contributions meaning that the more contributions<00:19:11.340> you<00:19:11.940> did<00:19:12.179> for<00:19:12.419> sismo<00:19:12.900> the 00:19:13.190 --> 00:19:13.200 align:start position:0% contributions you did for sismo the 00:19:13.200 --> 00:19:15.650 align:start position:0% contributions you did for sismo the higher<00:19:13.440> voting<00:19:13.799> power<00:19:13.919> you<00:19:14.100> have<00:19:14.760> again<00:19:15.419> it 00:19:15.650 --> 00:19:15.660 align:start position:0% higher voting power you have again it 00:19:15.660 --> 00:19:17.570 align:start position:0% higher voting power you have again it reuses<00:19:16.200> the<00:19:16.559> thing<00:19:16.799> that<00:19:16.980> I<00:19:17.160> told<00:19:17.340> you<00:19:17.460> about 00:19:17.570 --> 00:19:17.580 align:start position:0% reuses the thing that I told you about 00:19:17.580 --> 00:19:20.150 align:start position:0% reuses the thing that I told you about the<00:19:17.820> balance<00:19:18.120> of<00:19:18.240> the<00:19:18.360> token<00:19:18.780> basically<00:19:19.740> the 00:19:20.150 --> 00:19:20.160 align:start position:0% the balance of the token basically the 00:19:20.160 --> 00:19:22.190 align:start position:0% the balance of the token basically the more<00:19:20.340> contributions<00:19:20.820> you<00:19:21.059> did 00:19:22.190 --> 00:19:22.200 align:start position:0% more contributions you did 00:19:22.200 --> 00:19:24.470 align:start position:0% more contributions you did you<00:19:22.860> the<00:19:23.220> higher<00:19:23.520> you<00:19:23.640> will<00:19:23.760> be<00:19:23.940> in<00:19:24.059> the<00:19:24.179> tier 00:19:24.470 --> 00:19:24.480 align:start position:0% you the higher you will be in the tier 00:19:24.480 --> 00:19:26.390 align:start position:0% you the higher you will be in the tier of<00:19:24.600> contributor<00:19:25.200> and<00:19:25.440> the<00:19:25.620> higher<00:19:25.980> voting 00:19:26.390 --> 00:19:26.400 align:start position:0% of contributor and the higher voting 00:19:26.400 --> 00:19:29.930 align:start position:0% of contributor and the higher voting power<00:19:26.640> so<00:19:27.480> here<00:19:27.840> with<00:19:28.559> ZK<00:19:29.160> badges<00:19:29.520> you<00:19:29.700> will<00:19:29.820> be 00:19:29.930 --> 00:19:29.940 align:start position:0% power so here with ZK badges you will be 00:19:29.940 --> 00:19:33.289 align:start position:0% power so here with ZK badges you will be able<00:19:30.059> to<00:19:30.440> aggregate<00:19:31.440> your<00:19:32.039> reputation<00:19:32.640> from 00:19:33.289 --> 00:19:33.299 align:start position:0% able to aggregate your reputation from 00:19:33.299 --> 00:19:35.630 align:start position:0% able to aggregate your reputation from your<00:19:33.660> private<00:19:34.140> wallet<00:19:34.500> that<00:19:34.919> maybe<00:19:35.039> you<00:19:35.340> held 00:19:35.630 --> 00:19:35.640 align:start position:0% your private wallet that maybe you held 00:19:35.640 --> 00:19:38.690 align:start position:0% your private wallet that maybe you held by<00:19:35.880> using<00:19:36.539> a<00:19:36.720> lot<00:19:36.860> sismo<00:19:37.860> and<00:19:38.280> from<00:19:38.460> your 00:19:38.690 --> 00:19:38.700 align:start position:0% by using a lot sismo and from your 00:19:38.700 --> 00:19:40.909 align:start position:0% by using a lot sismo and from your public<00:19:38.820> wallet<00:19:39.299> that<00:19:39.539> maybe<00:19:39.720> you<00:19:40.320> help<00:19:40.500> by 00:19:40.909 --> 00:19:40.919 align:start position:0% public wallet that maybe you help by 00:19:40.919 --> 00:19:42.830 align:start position:0% public wallet that maybe you help by doing<00:19:41.400> some<00:19:41.700> threads<00:19:42.240> some<00:19:42.360> communication 00:19:42.830 --> 00:19:42.840 align:start position:0% doing some threads some communication 00:19:42.840 --> 00:19:46.130 align:start position:0% doing some threads some communication about<00:19:43.080> this<00:19:43.320> more<00:19:43.620> so<00:19:44.400> yeah<00:19:45.120> again<00:19:45.360> I<00:19:46.020> think 00:19:46.130 --> 00:19:46.140 align:start position:0% about this more so yeah again I think 00:19:46.140 --> 00:19:48.470 align:start position:0% about this more so yeah again I think for<00:19:46.260> governance<00:19:46.740> power<00:19:46.919> this<00:19:47.700> is<00:19:47.940> very<00:19:48.299> very 00:19:48.470 --> 00:19:48.480 align:start position:0% for governance power this is very very 00:19:48.480 --> 00:19:51.049 align:start position:0% for governance power this is very very interesting<00:19:48.960> to<00:19:49.679> have<00:19:49.860> reputation<00:19:50.520> based 00:19:51.049 --> 00:19:51.059 align:start position:0% interesting to have reputation based 00:19:51.059 --> 00:19:55.730 align:start position:0% interesting to have reputation based governance<00:19:51.679> instead<00:19:52.679> of<00:19:52.860> just<00:19:53.480> uh<00:19:54.480> like<00:19:55.380> who 00:19:55.730 --> 00:19:55.740 align:start position:0% governance instead of just uh like who 00:19:55.740 --> 00:19:58.370 align:start position:0% governance instead of just uh like who has<00:19:55.919> been<00:19:56.100> like<00:19:56.640> instead<00:19:57.539> of<00:19:57.600> erc20<00:19:58.080> is<00:19:58.260> only 00:19:58.370 --> 00:19:58.380 align:start position:0% has been like instead of erc20 is only 00:19:58.380 --> 00:20:00.350 align:start position:0% has been like instead of erc20 is only that<00:19:58.620> is<00:19:58.740> financial<00:19:58.919> capital<00:19:59.220> or<00:19:59.940> communities 00:20:00.350 --> 00:20:00.360 align:start position:0% that is financial capital or communities 00:20:00.360 --> 00:20:02.930 align:start position:0% that is financial capital or communities that<00:20:00.720> are<00:20:00.900> ruled<00:20:01.559> by<00:20:01.679> your<00:20:01.860> nft<00:20:02.220> that<00:20:02.580> you<00:20:02.700> just 00:20:02.930 --> 00:20:02.940 align:start position:0% that are ruled by your nft that you just 00:20:02.940 --> 00:20:04.669 align:start position:0% that are ruled by your nft that you just have<00:20:03.059> to<00:20:03.240> first<00:20:03.539> come<00:20:03.840> first<00:20:04.080> serve<00:20:04.380> and<00:20:04.500> it's 00:20:04.669 --> 00:20:04.679 align:start position:0% have to first come first serve and it's 00:20:04.679 --> 00:20:06.409 align:start position:0% have to first come first serve and it's like<00:20:04.860> a<00:20:05.039> airdrop<00:20:05.460> Farmers<00:20:05.820> this<00:20:06.179> kind<00:20:06.299> of 00:20:06.409 --> 00:20:06.419 align:start position:0% like a airdrop Farmers this kind of 00:20:06.419 --> 00:20:07.970 align:start position:0% like a airdrop Farmers this kind of stuff<00:20:06.600> here 00:20:07.970 --> 00:20:07.980 align:start position:0% stuff here 00:20:07.980 --> 00:20:09.830 align:start position:0% stuff here these<00:20:08.400> tokens<00:20:08.700> means<00:20:09.059> a<00:20:09.120> lot<00:20:09.299> and<00:20:09.660> it's 00:20:09.830 --> 00:20:09.840 align:start position:0% these tokens means a lot and it's 00:20:09.840 --> 00:20:12.110 align:start position:0% these tokens means a lot and it's private<00:20:10.260> so<00:20:10.679> you<00:20:10.919> can<00:20:10.980> really<00:20:11.280> speak<00:20:11.880> your 00:20:12.110 --> 00:20:12.120 align:start position:0% private so you can really speak your 00:20:12.120 --> 00:20:14.150 align:start position:0% private so you can really speak your mind<00:20:12.299> there's<00:20:12.780> no<00:20:12.960> risk<00:20:13.200> at<00:20:13.679> knowing<00:20:13.980> that 00:20:14.150 --> 00:20:14.160 align:start position:0% mind there's no risk at knowing that 00:20:14.160 --> 00:20:16.730 align:start position:0% mind there's no risk at knowing that you're<00:20:15.000> a<00:20:15.240> team<00:20:15.360> member<00:20:15.600> or<00:20:15.780> I<00:20:15.900> don't<00:20:16.020> know<00:20:16.200> so 00:20:16.730 --> 00:20:16.740 align:start position:0% you're a team member or I don't know so 00:20:16.740 --> 00:20:18.289 align:start position:0% you're a team member or I don't know so we<00:20:17.039> are<00:20:17.160> super<00:20:17.280> excited<00:20:17.640> about<00:20:17.820> this<00:20:18.179> new 00:20:18.289 --> 00:20:18.299 align:start position:0% we are super excited about this new 00:20:18.299 --> 00:20:19.970 align:start position:0% we are super excited about this new primitive 00:20:19.970 --> 00:20:19.980 align:start position:0% primitive 00:20:19.980 --> 00:20:23.570 align:start position:0% primitive so<00:20:20.460> now<00:20:20.880> uh<00:20:21.539> I<00:20:22.380> I'd<00:20:22.559> like<00:20:22.799> to<00:20:22.919> speak<00:20:23.160> about<00:20:23.340> the 00:20:23.570 --> 00:20:23.580 align:start position:0% so now uh I I'd like to speak about the 00:20:23.580 --> 00:20:26.570 align:start position:0% so now uh I I'd like to speak about the long-term<00:20:24.059> vision<00:20:24.240> of<00:20:24.419> system<00:20:24.720> again 00:20:26.570 --> 00:20:26.580 align:start position:0% long-term vision of system again 00:20:26.580 --> 00:20:27.650 align:start position:0% long-term vision of system again [Music] 00:20:27.650 --> 00:20:27.660 align:start position:0% [Music] 00:20:27.660 --> 00:20:30.230 align:start position:0% [Music] I'm<00:20:28.020> able<00:20:28.320> to<00:20:28.380> aggregate<00:20:28.799> with<00:20:28.919> you<00:20:28.980> I<00:20:29.400> am<00:20:29.760> able 00:20:30.230 --> 00:20:30.240 align:start position:0% I'm able to aggregate with you I am able 00:20:30.240 --> 00:20:32.150 align:start position:0% I'm able to aggregate with you I am able to<00:20:30.299> aggregate<00:20:30.780> data<00:20:31.080> the<00:20:31.380> way<00:20:31.500> it<00:20:31.620> works<00:20:31.919> is 00:20:32.150 --> 00:20:32.160 align:start position:0% to aggregate data the way it works is 00:20:32.160 --> 00:20:34.370 align:start position:0% to aggregate data the way it works is that<00:20:32.460> basically<00:20:33.000> anytime<00:20:33.660> I<00:20:33.840> want<00:20:33.960> to<00:20:34.080> use<00:20:34.200> an 00:20:34.370 --> 00:20:34.380 align:start position:0% that basically anytime I want to use an 00:20:34.380 --> 00:20:36.890 align:start position:0% that basically anytime I want to use an account<00:20:34.559> to<00:20:35.280> prove<00:20:35.580> something<00:20:35.700> about<00:20:36.120> it<00:20:36.419> I 00:20:36.890 --> 00:20:36.900 align:start position:0% account to prove something about it I 00:20:36.900 --> 00:20:39.529 align:start position:0% account to prove something about it I will<00:20:37.020> send<00:20:37.140> a<00:20:37.380> message<00:20:37.500> with<00:20:37.799> it<00:20:38.340> and<00:20:39.059> it<00:20:39.299> gives 00:20:39.529 --> 00:20:39.539 align:start position:0% will send a message with it and it gives 00:20:39.539 --> 00:20:41.390 align:start position:0% will send a message with it and it gives the<00:20:39.720> second<00:20:39.900> the<00:20:40.320> ability<00:20:40.500> to<00:20:40.740> be<00:20:40.860> in<00:20:40.919> the<00:20:41.039> ZK 00:20:41.390 --> 00:20:41.400 align:start position:0% the second the ability to be in the ZK 00:20:41.400 --> 00:20:43.190 align:start position:0% the second the ability to be in the ZK world<00:20:41.580> like<00:20:41.880> from<00:20:42.240> now<00:20:42.360> on<00:20:42.539> I<00:20:42.780> can<00:20:42.900> prove 00:20:43.190 --> 00:20:43.200 align:start position:0% world like from now on I can prove 00:20:43.200 --> 00:20:45.110 align:start position:0% world like from now on I can prove everything<00:20:43.440> about<00:20:43.679> my<00:20:43.980> data<00:20:44.340> so<00:20:44.700> the<00:20:44.880> way<00:20:44.940> it 00:20:45.110 --> 00:20:45.120 align:start position:0% everything about my data so the way it 00:20:45.120 --> 00:20:47.270 align:start position:0% everything about my data so the way it works<00:20:45.360> that<00:20:45.480> I<00:20:45.960> will<00:20:46.080> import<00:20:46.260> into<00:20:46.620> the<00:20:47.100> system 00:20:47.270 --> 00:20:47.280 align:start position:0% works that I will import into the system 00:20:47.280 --> 00:20:50.750 align:start position:0% works that I will import into the system volt<00:20:47.880> that<00:20:48.480> you<00:20:48.660> encrypted<00:20:49.280> data<00:20:50.280> volt<00:20:50.580> that 00:20:50.750 --> 00:20:50.760 align:start position:0% volt that you encrypted data volt that 00:20:50.760 --> 00:20:52.970 align:start position:0% volt that you encrypted data volt that is<00:20:50.880> only<00:20:51.000> accessible<00:20:51.419> to<00:20:51.660> yours<00:20:51.960> I<00:20:52.620> will<00:20:52.799> store 00:20:52.970 --> 00:20:52.980 align:start position:0% is only accessible to yours I will store 00:20:52.980 --> 00:20:55.430 align:start position:0% is only accessible to yours I will store the<00:20:53.220> signatures<00:20:54.000> that<00:20:54.120> I<00:20:54.299> told<00:20:54.419> you<00:20:54.600> about<00:20:54.720> so 00:20:55.430 --> 00:20:55.440 align:start position:0% the signatures that I told you about so 00:20:55.440 --> 00:20:58.310 align:start position:0% the signatures that I told you about so I<00:20:55.919> sign<00:20:56.160> with<00:20:56.460> daniel.tis<00:20:57.360> now<00:20:57.840> I'm<00:20:58.020> in<00:20:58.200> the 00:20:58.310 --> 00:20:58.320 align:start position:0% I sign with daniel.tis now I'm in the 00:20:58.320 --> 00:20:59.690 align:start position:0% I sign with daniel.tis now I'm in the world<00:20:58.440> with<00:20:58.799> the<00:20:58.919> unknown<00:20:59.220> I'm<00:20:59.340> in<00:20:59.520> the<00:20:59.580> world 00:20:59.690 --> 00:20:59.700 align:start position:0% world with the unknown I'm in the world 00:20:59.700 --> 00:21:00.950 align:start position:0% world with the unknown I'm in the world and<00:20:59.940> now 00:21:00.950 --> 00:21:00.960 align:start position:0% and now 00:21:00.960 --> 00:21:03.110 align:start position:0% and now as<00:21:01.440> a<00:21:01.620> user<00:21:01.919> I'm<00:21:02.280> the<00:21:02.460> only<00:21:02.580> one<00:21:02.760> that<00:21:02.940> has 00:21:03.110 --> 00:21:03.120 align:start position:0% as a user I'm the only one that has 00:21:03.120 --> 00:21:04.610 align:start position:0% as a user I'm the only one that has access<00:21:03.240> to<00:21:03.480> all<00:21:03.660> my<00:21:03.780> data<00:21:04.080> and<00:21:04.200> now<00:21:04.320> it<00:21:04.440> doesn't 00:21:04.610 --> 00:21:04.620 align:start position:0% access to all my data and now it doesn't 00:21:04.620 --> 00:21:06.650 align:start position:0% access to all my data and now it doesn't matter<00:21:04.860> whether<00:21:05.820> it<00:21:05.940> comes<00:21:06.120> from<00:21:06.240> an<00:21:06.419> address 00:21:06.650 --> 00:21:06.660 align:start position:0% matter whether it comes from an address 00:21:06.660 --> 00:21:08.750 align:start position:0% matter whether it comes from an address to<00:21:07.020> address<00:21:07.200> or<00:21:07.500> I<00:21:07.620> don't<00:21:07.799> know<00:21:07.919> what 00:21:08.750 --> 00:21:08.760 align:start position:0% to address or I don't know what 00:21:08.760 --> 00:21:10.549 align:start position:0% to address or I don't know what I'm<00:21:09.240> the<00:21:09.480> user<00:21:09.720> I<00:21:09.840> have 00:21:10.549 --> 00:21:10.559 align:start position:0% I'm the user I have 00:21:10.559 --> 00:21:12.770 align:start position:0% I'm the user I have yeah<00:21:11.039> access<00:21:11.400> to<00:21:11.700> everything<00:21:11.940> and<00:21:12.240> I<00:21:12.419> can<00:21:12.539> use 00:21:12.770 --> 00:21:12.780 align:start position:0% yeah access to everything and I can use 00:21:12.780 --> 00:21:14.810 align:start position:0% yeah access to everything and I can use it<00:21:12.960> as<00:21:13.620> I<00:21:13.799> want 00:21:14.810 --> 00:21:14.820 align:start position:0% it as I want 00:21:14.820 --> 00:21:17.510 align:start position:0% it as I want so<00:21:15.419> for<00:21:16.200> instance<00:21:16.440> let's<00:21:16.860> say<00:21:17.100> that<00:21:17.220> I<00:21:17.340> want<00:21:17.460> to 00:21:17.510 --> 00:21:17.520 align:start position:0% so for instance let's say that I want to 00:21:17.520 --> 00:21:20.510 align:start position:0% so for instance let's say that I want to access<00:21:17.700> an<00:21:18.480> airdrop<00:21:19.020> and<00:21:19.620> they<00:21:19.799> require<00:21:19.980> me<00:21:20.340> to 00:21:20.510 --> 00:21:20.520 align:start position:0% access an airdrop and they require me to 00:21:20.520 --> 00:21:23.330 align:start position:0% access an airdrop and they require me to prove<00:21:21.299> that<00:21:21.480> I'm<00:21:21.720> a<00:21:21.900> human<00:21:22.020> that<00:21:22.380> it's<00:21:22.919> a<00:21:23.039> CP 00:21:23.330 --> 00:21:23.340 align:start position:0% prove that I'm a human that it's a CP 00:21:23.340 --> 00:21:24.770 align:start position:0% prove that I'm a human that it's a CP resistant<00:21:23.760> harder<00:21:24.059> that<00:21:24.240> would<00:21:24.419> be<00:21:24.539> great<00:21:24.660> to 00:21:24.770 --> 00:21:24.780 align:start position:0% resistant harder that would be great to 00:21:24.780 --> 00:21:28.190 align:start position:0% resistant harder that would be great to have<00:21:24.960> that<00:21:25.520> so<00:21:26.520> they<00:21:26.820> require<00:21:27.000> me<00:21:27.299> to<00:21:27.419> prove 00:21:28.190 --> 00:21:28.200 align:start position:0% have that so they require me to prove 00:21:28.200 --> 00:21:30.230 align:start position:0% have that so they require me to prove and<00:21:28.620> that<00:21:28.860> I'm<00:21:29.039> a<00:21:29.220> human 00:21:30.230 --> 00:21:30.240 align:start position:0% and that I'm a human 00:21:30.240 --> 00:21:32.210 align:start position:0% and that I'm a human and<00:21:30.720> that<00:21:30.900> I<00:21:31.140> don't<00:21:31.260> know<00:21:31.380> that<00:21:31.559> I<00:21:31.740> traded<00:21:32.039> a 00:21:32.210 --> 00:21:32.220 align:start position:0% and that I don't know that I traded a 00:21:32.220 --> 00:21:34.490 align:start position:0% and that I don't know that I traded a lot on<00:21:32.520> their<00:21:32.820> platforms<00:21:33.360> or<00:21:33.600> that<00:21:34.080> I<00:21:34.260> am<00:21:34.380> a 00:21:34.490 --> 00:21:34.500 align:start position:0% lot on their platforms or that I am a 00:21:34.500 --> 00:21:37.789 align:start position:0% lot on their platforms or that I am a big<00:21:34.740> user<00:21:35.159> so<00:21:36.000> that's<00:21:36.720> what<00:21:37.020> allows<00:21:37.380> me<00:21:37.500> the 00:21:37.789 --> 00:21:37.799 align:start position:0% big user so that's what allows me the 00:21:37.799 --> 00:21:41.090 align:start position:0% big user so that's what allows me the world<00:21:37.980> to<00:21:38.280> do<00:21:38.880> I<00:21:39.600> can<00:21:39.780> generate<00:21:40.200> the<00:21:40.380> ZK<00:21:40.679> proof 00:21:41.090 --> 00:21:41.100 align:start position:0% world to do I can generate the ZK proof 00:21:41.100 --> 00:21:42.770 align:start position:0% world to do I can generate the ZK proof let's<00:21:41.460> say<00:21:41.580> on<00:21:41.760> the<00:21:41.820> one<00:21:41.940> time<00:21:42.120> address<00:21:42.360> on<00:21:42.659> the 00:21:42.770 --> 00:21:42.780 align:start position:0% let's say on the one time address on the 00:21:42.780 --> 00:21:45.770 align:start position:0% let's say on the one time address on the go<00:21:43.380> and<00:21:43.919> I<00:21:44.159> can<00:21:44.280> give<00:21:44.580> I<00:21:45.000> can<00:21:45.179> connect<00:21:45.419> with 00:21:45.770 --> 00:21:45.780 align:start position:0% go and I can give I can connect with 00:21:45.780 --> 00:21:48.649 align:start position:0% go and I can give I can connect with standing<00:21:46.140> resistance<00:21:46.559> to<00:21:46.860> this<00:21:47.299> service<00:21:48.299> and 00:21:48.649 --> 00:21:48.659 align:start position:0% standing resistance to this service and 00:21:48.659 --> 00:21:50.750 align:start position:0% standing resistance to this service and review<00:21:48.840> just<00:21:49.140> what<00:21:49.320> I<00:21:49.500> want<00:21:49.559> the<00:21:50.159> the<00:21:50.220> other 00:21:50.750 --> 00:21:50.760 align:start position:0% review just what I want the the other 00:21:50.760 --> 00:21:52.610 align:start position:0% review just what I want the the other thing<00:21:50.940> that<00:21:51.120> is<00:21:51.299> interesting<00:21:51.720> is<00:21:52.140> that<00:21:52.380> you 00:21:52.610 --> 00:21:52.620 align:start position:0% thing that is interesting is that you 00:21:52.620 --> 00:21:55.370 align:start position:0% thing that is interesting is that you can<00:21:53.220> in<00:21:53.580> the<00:21:53.760> long<00:21:53.940> run<00:21:54.120> we<00:21:54.539> are<00:21:54.659> using<00:21:54.900> Badges 00:21:55.370 --> 00:21:55.380 align:start position:0% can in the long run we are using Badges 00:21:55.380 --> 00:21:57.770 align:start position:0% can in the long run we are using Badges and<00:21:55.500> sbts<00:21:56.100> because<00:21:56.220> we<00:21:56.940> think<00:21:57.120> that<00:21:57.360> they<00:21:57.539> are 00:21:57.770 --> 00:21:57.780 align:start position:0% and sbts because we think that they are 00:21:57.780 --> 00:22:00.230 align:start position:0% and sbts because we think that they are tremendously<00:21:58.559> great<00:21:58.860> at<00:21:59.400> standardizing 00:22:00.230 --> 00:22:00.240 align:start position:0% tremendously great at standardizing 00:22:00.240 --> 00:22:02.029 align:start position:0% tremendously great at standardizing things<00:22:00.419> because<00:22:00.780> everybody<00:22:01.200> knows<00:22:01.740> how<00:22:01.980> to 00:22:02.029 --> 00:22:02.039 align:start position:0% things because everybody knows how to 00:22:02.039 --> 00:22:04.549 align:start position:0% things because everybody knows how to fetch<00:22:02.400> a<00:22:02.520> token<00:22:02.820> how<00:22:03.179> to<00:22:03.299> read<00:22:03.480> your<00:22:03.659> token<00:22:04.080> and 00:22:04.549 --> 00:22:04.559 align:start position:0% fetch a token how to read your token and 00:22:04.559 --> 00:22:05.870 align:start position:0% fetch a token how to read your token and that's<00:22:04.679> why<00:22:04.799> I<00:22:04.980> think<00:22:05.100> that 00:22:05.870 --> 00:22:05.880 align:start position:0% that's why I think that 00:22:05.880 --> 00:22:09.169 align:start position:0% that's why I think that they<00:22:06.480> have<00:22:06.600> an<00:22:06.780> advantage<00:22:07.200> over<00:22:07.820> PCS<00:22:08.820> actually 00:22:09.169 --> 00:22:09.179 align:start position:0% they have an advantage over PCS actually 00:22:09.179 --> 00:22:11.810 align:start position:0% they have an advantage over PCS actually because<00:22:09.780> the<00:22:10.080> standardization<00:22:10.559> is<00:22:10.919> is<00:22:11.100> better 00:22:11.810 --> 00:22:11.820 align:start position:0% because the standardization is is better 00:22:11.820 --> 00:22:14.149 align:start position:0% because the standardization is is better and<00:22:12.120> you<00:22:12.419> can<00:22:12.539> do<00:22:12.720> crypto<00:22:13.200> native<00:22:13.440> stuff<00:22:13.679> you 00:22:14.149 --> 00:22:14.159 align:start position:0% and you can do crypto native stuff you 00:22:14.159 --> 00:22:14.930 align:start position:0% and you can do crypto native stuff you can 00:22:14.930 --> 00:22:14.940 align:start position:0% can 00:22:14.940 --> 00:22:18.289 align:start position:0% can what<00:22:15.480> we<00:22:15.720> did<00:22:16.140> with<00:22:16.320> ZK<00:22:16.799> is<00:22:17.520> the<00:22:17.640> ability<00:22:17.940> to 00:22:18.289 --> 00:22:18.299 align:start position:0% what we did with ZK is the ability to 00:22:18.299 --> 00:22:21.110 align:start position:0% what we did with ZK is the ability to programmatically<00:22:19.260> code<00:22:19.919> repetition<00:22:20.520> in<00:22:20.940> in 00:22:21.110 --> 00:22:21.120 align:start position:0% programmatically code repetition in in 00:22:21.120 --> 00:22:23.390 align:start position:0% programmatically code repetition in in in<00:22:21.240> in<00:22:21.539> some<00:22:21.780> sort<00:22:22.020> so<00:22:22.260> we<00:22:22.740> are<00:22:22.860> very<00:22:22.980> bullish 00:22:23.390 --> 00:22:23.400 align:start position:0% in in some sort so we are very bullish 00:22:23.400 --> 00:22:26.450 align:start position:0% in in some sort so we are very bullish and<00:22:23.580> this<00:22:23.940> is<00:22:24.120> nsbcs<00:22:24.960> but<00:22:25.140> but<00:22:25.440> we<00:22:26.039> are<00:22:26.159> mainly 00:22:26.450 --> 00:22:26.460 align:start position:0% and this is nsbcs but but we are mainly 00:22:26.460 --> 00:22:28.370 align:start position:0% and this is nsbcs but but we are mainly using<00:22:26.760> tokens<00:22:27.240> it's<00:22:27.480> a<00:22:27.600> big<00:22:27.720> question<00:22:27.960> why 00:22:28.370 --> 00:22:28.380 align:start position:0% using tokens it's a big question why 00:22:28.380 --> 00:22:30.409 align:start position:0% using tokens it's a big question why we're<00:22:28.559> using<00:22:28.919> tokens<00:22:29.220> because<00:22:29.580> they<00:22:30.240> are 00:22:30.409 --> 00:22:30.419 align:start position:0% we're using tokens because they are 00:22:30.419 --> 00:22:32.210 align:start position:0% we're using tokens because they are great<00:22:30.539> at<00:22:30.720> standardizing<00:22:31.500> once<00:22:32.039> you<00:22:32.159> have 00:22:32.210 --> 00:22:32.220 align:start position:0% great at standardizing once you have 00:22:32.220 --> 00:22:34.010 align:start position:0% great at standardizing once you have reputation<00:22:32.640> as<00:22:32.880> a<00:22:33.059> token<00:22:33.360> it's<00:22:33.659> super<00:22:33.840> easy 00:22:34.010 --> 00:22:34.020 align:start position:0% reputation as a token it's super easy 00:22:34.020 --> 00:22:36.230 align:start position:0% reputation as a token it's super easy for<00:22:34.260> anyone<00:22:34.559> to<00:22:34.679> fetch<00:22:34.980> it<00:22:35.039> to<00:22:35.159> know<00:22:35.340> that<00:22:35.580> we 00:22:36.230 --> 00:22:36.240 align:start position:0% for anyone to fetch it to know that we 00:22:36.240 --> 00:22:37.610 align:start position:0% for anyone to fetch it to know that we have<00:22:36.360> the<00:22:36.419> sign<00:22:36.600> in<00:22:36.780> with<00:22:36.840> the<00:22:37.020> term<00:22:37.140> tools<00:22:37.500> and 00:22:37.610 --> 00:22:37.620 align:start position:0% have the sign in with the term tools and 00:22:37.620 --> 00:22:39.590 align:start position:0% have the sign in with the term tools and all<00:22:37.740> these<00:22:37.980> things<00:22:38.100> but<00:22:38.760> on<00:22:39.059> the<00:22:39.179> long-term 00:22:39.590 --> 00:22:39.600 align:start position:0% all these things but on the long-term 00:22:39.600 --> 00:22:40.549 align:start position:0% all these things but on the long-term vision 00:22:40.549 --> 00:22:40.559 align:start position:0% vision 00:22:40.559 --> 00:22:42.710 align:start position:0% vision do<00:22:41.159> we<00:22:41.340> really<00:22:41.460> need<00:22:41.700> to<00:22:41.820> send<00:22:42.000> those<00:22:42.120> UK<00:22:42.419> proof 00:22:42.710 --> 00:22:42.720 align:start position:0% do we really need to send those UK proof 00:22:42.720 --> 00:22:44.090 align:start position:0% do we really need to send those UK proof to<00:22:42.780> a<00:22:42.900> Smart<00:22:43.020> contract<00:22:43.320> to<00:22:43.440> me<00:22:43.620> in<00:22:43.740> the<00:22:43.799> badge 00:22:44.090 --> 00:22:44.100 align:start position:0% to a Smart contract to me in the badge 00:22:44.100 --> 00:22:45.890 align:start position:0% to a Smart contract to me in the badge if<00:22:44.280> what<00:22:44.520> we<00:22:44.700> want<00:22:44.880> to<00:22:44.940> prove<00:22:45.360> is<00:22:45.480> to<00:22:45.659> a<00:22:45.780> third 00:22:45.890 --> 00:22:45.900 align:start position:0% if what we want to prove is to a third 00:22:45.900 --> 00:22:47.390 align:start position:0% if what we want to prove is to a third party<00:22:46.140> let's<00:22:46.500> say<00:22:46.740> that<00:22:46.740> I<00:22:46.860> want<00:22:46.980> to<00:22:47.039> prove<00:22:47.280> to 00:22:47.390 --> 00:22:47.400 align:start position:0% party let's say that I want to prove to 00:22:47.400 --> 00:22:50.330 align:start position:0% party let's say that I want to prove to a<00:22:47.520> merch<00:22:47.820> store<00:22:48.000> that<00:22:48.720> I<00:22:48.900> have<00:22:48.960> crypto<00:22:49.380> Bank<00:22:49.620> do 00:22:50.330 --> 00:22:50.340 align:start position:0% a merch store that I have crypto Bank do 00:22:50.340 --> 00:22:51.890 align:start position:0% a merch store that I have crypto Bank do I<00:22:50.460> really<00:22:50.640> need<00:22:50.760> to<00:22:50.880> send<00:22:51.059> a<00:22:51.240> badge<00:22:51.600> on<00:22:51.780> an 00:22:51.890 --> 00:22:51.900 align:start position:0% I really need to send a badge on an 00:22:51.900 --> 00:22:54.049 align:start position:0% I really need to send a badge on an address<00:22:52.080> maybe<00:22:52.740> not<00:22:52.980> I<00:22:53.159> can<00:22:53.340> directly<00:22:53.700> send 00:22:54.049 --> 00:22:54.059 align:start position:0% address maybe not I can directly send 00:22:54.059 --> 00:22:56.930 align:start position:0% address maybe not I can directly send the<00:22:54.179> ZK<00:22:54.480> badge<00:22:54.840> to<00:22:55.260> this<00:22:55.559> third<00:22:55.919> party<00:22:56.159> so 00:22:56.930 --> 00:22:56.940 align:start position:0% the ZK badge to this third party so 00:22:56.940 --> 00:22:58.909 align:start position:0% the ZK badge to this third party so that's<00:22:57.419> the<00:22:57.659> the<00:22:57.900> big<00:22:58.140> big<00:22:58.320> vision<00:22:58.559> of<00:22:58.799> system 00:22:58.909 --> 00:22:58.919 align:start position:0% that's the the big big vision of system 00:22:58.919 --> 00:23:02.750 align:start position:0% that's the the big big vision of system is<00:22:59.280> ready<00:22:59.400> to<00:22:59.580> be<00:22:59.780> to<00:23:00.780> be<00:23:01.260> a<00:23:01.440> Google<00:23:01.620> connect<00:23:01.860> on 00:23:02.750 --> 00:23:02.760 align:start position:0% is ready to be to be a Google connect on 00:23:02.760 --> 00:23:04.909 align:start position:0% is ready to be to be a Google connect on top<00:23:02.880> of<00:23:03.059> your<00:23:03.179> server<00:23:03.480> and<00:23:03.600> identities<00:23:03.960> you 00:23:04.909 --> 00:23:04.919 align:start position:0% top of your server and identities you 00:23:04.919 --> 00:23:06.529 align:start position:0% top of your server and identities you add<00:23:05.159> your<00:23:05.340> all<00:23:05.580> your<00:23:05.700> accounts<00:23:06.120> your<00:23:06.419> Twitter 00:23:06.529 --> 00:23:06.539 align:start position:0% add your all your accounts your Twitter 00:23:06.539 --> 00:23:08.810 align:start position:0% add your all your accounts your Twitter account<00:23:06.960> your<00:23:07.320> GitHub<00:23:07.679> account<00:23:07.799> you<00:23:08.580> also 00:23:08.810 --> 00:23:08.820 align:start position:0% account your GitHub account you also 00:23:08.820 --> 00:23:10.130 align:start position:0% account your GitHub account you also learn<00:23:09.000> the<00:23:09.179> address<00:23:09.299> your<00:23:09.539> Bitcoin<00:23:10.020> whether 00:23:10.130 --> 00:23:10.140 align:start position:0% learn the address your Bitcoin whether 00:23:10.140 --> 00:23:11.990 align:start position:0% learn the address your Bitcoin whether it's<00:23:10.320> your<00:23:10.440> ethereum<00:23:10.860> wallet<00:23:11.220> you<00:23:11.640> upgrade 00:23:11.990 --> 00:23:12.000 align:start position:0% it's your ethereum wallet you upgrade 00:23:12.000 --> 00:23:14.210 align:start position:0% it's your ethereum wallet you upgrade all<00:23:12.240> of<00:23:12.360> that<00:23:12.539> and<00:23:13.380> then<00:23:13.559> when<00:23:13.860> you<00:23:13.980> want<00:23:14.100> to 00:23:14.210 --> 00:23:14.220 align:start position:0% all of that and then when you want to 00:23:14.220 --> 00:23:17.090 align:start position:0% all of that and then when you want to send<00:23:14.400> to<00:23:14.580> an<00:23:14.700> app<00:23:14.880> they<00:23:15.240> say<00:23:15.419> Okay<00:23:15.799> I<00:23:16.799> want<00:23:16.919> a 00:23:17.090 --> 00:23:17.100 align:start position:0% send to an app they say Okay I want a 00:23:17.100 --> 00:23:19.070 align:start position:0% send to an app they say Okay I want a bit<00:23:17.220> like<00:23:17.340> when<00:23:17.520> you<00:23:17.640> connect<00:23:17.820> to<00:23:18.120> with<00:23:18.900> Google 00:23:19.070 --> 00:23:19.080 align:start position:0% bit like when you connect to with Google 00:23:19.080 --> 00:23:20.630 align:start position:0% bit like when you connect to with Google connect<00:23:19.380> they<00:23:19.679> say<00:23:19.860> okay<00:23:20.039> they<00:23:20.340> will<00:23:20.460> access 00:23:20.630 --> 00:23:20.640 align:start position:0% connect they say okay they will access 00:23:20.640 --> 00:23:22.490 align:start position:0% connect they say okay they will access your<00:23:20.880> email<00:23:21.120> your<00:23:21.480> contacts<00:23:21.960> your<00:23:22.080> all<00:23:22.260> these 00:23:22.490 --> 00:23:22.500 align:start position:0% your email your contacts your all these 00:23:22.500 --> 00:23:24.890 align:start position:0% your email your contacts your all these things<00:23:22.679> what<00:23:23.220> we<00:23:23.340> don't<00:23:23.520> hear<00:23:23.760> is<00:23:23.940> that<00:23:24.120> okay 00:23:24.890 --> 00:23:24.900 align:start position:0% things what we don't hear is that okay 00:23:24.900 --> 00:23:27.710 align:start position:0% things what we don't hear is that okay I<00:23:25.559> I<00:23:25.799> connect<00:23:25.980> with<00:23:26.280> this<00:23:26.400> more<00:23:26.640> this<00:23:27.299> app<00:23:27.419> want 00:23:27.710 --> 00:23:27.720 align:start position:0% I I connect with this more this app want 00:23:27.720 --> 00:23:30.830 align:start position:0% I I connect with this more this app want to<00:23:27.960> see<00:23:28.380> your<00:23:28.740> amount<00:23:29.400> of<00:23:29.580> I<00:23:29.820> don't<00:23:29.940> know<00:23:30.059> nfts 00:23:30.830 --> 00:23:30.840 align:start position:0% to see your amount of I don't know nfts 00:23:30.840 --> 00:23:32.450 align:start position:0% to see your amount of I don't know nfts your<00:23:31.140> total<00:23:31.500> net<00:23:31.740> worth<00:23:31.860> all<00:23:32.100> these<00:23:32.340> things 00:23:32.450 --> 00:23:32.460 align:start position:0% your total net worth all these things 00:23:32.460 --> 00:23:33.890 align:start position:0% your total net worth all these things and<00:23:32.640> you<00:23:32.760> choose<00:23:33.059> you<00:23:33.299> choose<00:23:33.480> what<00:23:33.659> you<00:23:33.780> want 00:23:33.890 --> 00:23:33.900 align:start position:0% and you choose you choose what you want 00:23:33.900 --> 00:23:36.049 align:start position:0% and you choose you choose what you want and<00:23:34.679> if<00:23:34.919> you<00:23:35.039> choose<00:23:35.280> your<00:23:35.460> food<00:23:35.640> to<00:23:36.000> bring 00:23:36.049 --> 00:23:36.059 align:start position:0% and if you choose your food to bring 00:23:36.059 --> 00:23:38.630 align:start position:0% and if you choose your food to bring your<00:23:36.240> full<00:23:36.360> reputation<00:23:36.840> maybe<00:23:37.679> maybe<00:23:37.980> you'll 00:23:38.630 --> 00:23:38.640 align:start position:0% your full reputation maybe maybe you'll 00:23:38.640 --> 00:23:41.090 align:start position:0% your full reputation maybe maybe you'll have<00:23:38.820> access<00:23:38.940> to<00:23:39.299> the<00:23:39.720> best<00:23:39.840> services<00:23:40.080> but<00:23:40.919> you 00:23:41.090 --> 00:23:41.100 align:start position:0% have access to the best services but you 00:23:41.100 --> 00:23:42.950 align:start position:0% have access to the best services but you can<00:23:41.220> also<00:23:41.640> choose<00:23:42.000> to<00:23:42.120> just<00:23:42.299> reveal<00:23:42.659> what<00:23:42.840> you 00:23:42.950 --> 00:23:42.960 align:start position:0% can also choose to just reveal what you 00:23:42.960 --> 00:23:45.110 align:start position:0% can also choose to just reveal what you want<00:23:43.080> because<00:23:43.320> if<00:23:44.159> you<00:23:44.400> don't<00:23:44.640> want<00:23:44.820> to<00:23:45.000> give 00:23:45.110 --> 00:23:45.120 align:start position:0% want because if you don't want to give 00:23:45.120 --> 00:23:47.390 align:start position:0% want because if you don't want to give to<00:23:45.299> this<00:23:45.480> application<00:23:45.840> everything<00:23:46.200> so<00:23:46.980> yeah 00:23:47.390 --> 00:23:47.400 align:start position:0% to this application everything so yeah 00:23:47.400 --> 00:23:49.610 align:start position:0% to this application everything so yeah that's<00:23:47.580> that's<00:23:47.940> uh<00:23:48.419> really<00:23:48.780> about<00:23:48.960> system<00:23:49.200> is 00:23:49.610 --> 00:23:49.620 align:start position:0% that's that's uh really about system is 00:23:49.620 --> 00:23:51.350 align:start position:0% that's that's uh really about system is trying<00:23:49.740> to<00:23:49.980> we<00:23:50.460> have<00:23:50.640> more<00:23:50.880> and<00:23:51.000> more<00:23:51.179> engine 00:23:51.350 --> 00:23:51.360 align:start position:0% trying to we have more and more engine 00:23:51.360 --> 00:23:52.730 align:start position:0% trying to we have more and more engine data<00:23:51.780> we<00:23:51.960> have<00:23:52.080> more<00:23:52.320> and<00:23:52.380> more<00:23:52.559> great 00:23:52.730 --> 00:23:52.740 align:start position:0% data we have more and more great 00:23:52.740 --> 00:23:55.130 align:start position:0% data we have more and more great projects<00:23:53.159> that<00:23:53.280> are<00:23:53.460> bringing<00:23:53.880> of<00:23:54.539> chain<00:23:54.780> data 00:23:55.130 --> 00:23:55.140 align:start position:0% projects that are bringing of chain data 00:23:55.140 --> 00:23:58.250 align:start position:0% projects that are bringing of chain data to<00:23:55.320> Unchained<00:23:55.799> data<00:23:56.480> but<00:23:57.480> today<00:23:57.659> we<00:23:57.960> cannot 00:23:58.250 --> 00:23:58.260 align:start position:0% to Unchained data but today we cannot 00:23:58.260 --> 00:24:00.770 align:start position:0% to Unchained data but today we cannot really<00:23:58.380> leverage<00:23:58.679> it<00:23:58.980> we<00:23:59.280> the<00:24:00.000> Privacy<00:24:00.360> is<00:24:00.600> a 00:24:00.770 --> 00:24:00.780 align:start position:0% really leverage it we the Privacy is a 00:24:00.780 --> 00:24:03.049 align:start position:0% really leverage it we the Privacy is a real<00:24:00.900> issue<00:24:01.260> about<00:24:01.440> identity<00:24:02.039> because<00:24:02.700> we<00:24:02.940> are 00:24:03.049 --> 00:24:03.059 align:start position:0% real issue about identity because we are 00:24:03.059 --> 00:24:05.090 align:start position:0% real issue about identity because we are used<00:24:03.240> to<00:24:03.480> web<00:24:03.780> to<00:24:04.080> Identity 00:24:05.090 --> 00:24:05.100 align:start position:0% used to web to Identity 00:24:05.100 --> 00:24:06.890 align:start position:0% used to web to Identity that<00:24:05.580> are<00:24:05.760> private<00:24:06.120> because<00:24:06.240> they<00:24:06.480> are<00:24:06.600> closed 00:24:06.890 --> 00:24:06.900 align:start position:0% that are private because they are closed 00:24:06.900 --> 00:24:08.750 align:start position:0% that are private because they are closed it's<00:24:07.140> closed<00:24:07.620> Gates<00:24:07.860> they<00:24:08.159> don't<00:24:08.340> want<00:24:08.460> to<00:24:08.580> see 00:24:08.750 --> 00:24:08.760 align:start position:0% it's closed Gates they don't want to see 00:24:08.760 --> 00:24:10.490 align:start position:0% it's closed Gates they don't want to see anything<00:24:08.940> so<00:24:09.480> of<00:24:09.659> course<00:24:09.780> it's<00:24:10.020> private<00:24:10.320> by 00:24:10.490 --> 00:24:10.500 align:start position:0% anything so of course it's private by 00:24:10.500 --> 00:24:13.190 align:start position:0% anything so of course it's private by Design<00:24:10.679> but<00:24:11.220> on<00:24:11.400> web3<00:24:11.760> with<00:24:12.000> public<00:24:12.240> by<00:24:12.480> Design 00:24:13.190 --> 00:24:13.200 align:start position:0% Design but on web3 with public by Design 00:24:13.200 --> 00:24:16.130 align:start position:0% Design but on web3 with public by Design but<00:24:13.799> this<00:24:14.159> also<00:24:14.460> caused<00:24:14.760> some<00:24:14.880> issues<00:24:15.179> so<00:24:15.600> I 00:24:16.130 --> 00:24:16.140 align:start position:0% but this also caused some issues so I 00:24:16.140 --> 00:24:18.350 align:start position:0% but this also caused some issues so I hope<00:24:16.320> that<00:24:16.620> uh<00:24:16.860> that<00:24:17.280> I<00:24:17.400> share<00:24:17.820> my<00:24:18.000> excitement 00:24:18.350 --> 00:24:18.360 align:start position:0% hope that uh that I share my excitement 00:24:18.360 --> 00:24:20.029 align:start position:0% hope that uh that I share my excitement about<00:24:18.600> what<00:24:19.080> we<00:24:19.260> can<00:24:19.380> do<00:24:19.500> with<00:24:19.620> serving 00:24:20.029 --> 00:24:20.039 align:start position:0% about what we can do with serving 00:24:20.039 --> 00:24:23.029 align:start position:0% about what we can do with serving identities<00:24:20.539> and<00:24:21.539> we're<00:24:22.380> hiring<00:24:22.740> by<00:24:22.919> the<00:24:23.039> way 00:24:23.029 --> 00:24:23.039 align:start position:0% identities and we're hiring by the way 00:24:23.039 --> 00:24:25.490 align:start position:0% identities and we're hiring by the way so<00:24:23.280> if<00:24:23.460> the<00:24:23.640> mission<00:24:23.760> is<00:24:24.000> exciting<00:24:24.419> to<00:24:24.539> you<00:24:24.720> we 00:24:25.490 --> 00:24:25.500 align:start position:0% so if the mission is exciting to you we 00:24:25.500 --> 00:24:27.230 align:start position:0% so if the mission is exciting to you we are<00:24:25.679> very<00:24:25.860> small<00:24:26.100> team<00:24:26.340> we<00:24:26.580> are<00:24:26.760> just<00:24:27.059> seven 00:24:27.230 --> 00:24:27.240 align:start position:0% are very small team we are just seven 00:24:27.240 --> 00:24:29.210 align:start position:0% are very small team we are just seven but<00:24:27.600> we<00:24:27.840> are<00:24:27.960> very<00:24:28.140> passionate<00:24:28.500> about<00:24:28.679> what<00:24:29.039> we 00:24:29.210 --> 00:24:29.220 align:start position:0% but we are very passionate about what we 00:24:29.220 --> 00:24:32.570 align:start position:0% but we are very passionate about what we do<00:24:29.400> so<00:24:29.940> feel<00:24:30.240> free<00:24:30.480> to<00:24:31.080> reach<00:24:31.260> out<00:24:31.860> and<00:24:32.340> again 00:24:32.570 --> 00:24:32.580 align:start position:0% do so feel free to reach out and again 00:24:32.580 --> 00:24:35.330 align:start position:0% do so feel free to reach out and again everything<00:24:33.419> is<00:24:33.720> open<00:24:33.900> source<00:24:34.320> we<00:24:34.440> spent<00:24:34.860> a<00:24:35.220> lot 00:24:35.330 --> 00:24:35.340 align:start position:0% everything is open source we spent a lot 00:24:35.340 --> 00:24:38.450 align:start position:0% everything is open source we spent a lot of<00:24:35.580> of<00:24:36.000> energy<00:24:36.600> to<00:24:36.960> the<00:24:37.080> documentation<00:24:37.559> to<00:24:38.280> the 00:24:38.450 --> 00:24:38.460 align:start position:0% of of energy to the documentation to the 00:24:38.460 --> 00:24:40.070 align:start position:0% of of energy to the documentation to the quality<00:24:38.760> of<00:24:38.880> our<00:24:39.000> code<00:24:39.299> so 00:24:40.070 --> 00:24:40.080 align:start position:0% quality of our code so 00:24:40.080 --> 00:24:42.350 align:start position:0% quality of our code so yeah<00:24:40.559> we're<00:24:40.740> here<00:24:40.919> for<00:24:41.100> the<00:24:41.220> long<00:24:41.340> term<00:24:41.520> we'd 00:24:42.350 --> 00:24:42.360 align:start position:0% yeah we're here for the long term we'd 00:24:42.360 --> 00:24:44.810 align:start position:0% yeah we're here for the long term we'd like<00:24:42.480> to<00:24:42.600> have<00:24:42.780> many<00:24:43.200> contributors<00:24:43.799> and<00:24:44.039> yeah 00:24:44.810 --> 00:24:44.820 align:start position:0% like to have many contributors and yeah 00:24:44.820 --> 00:24:48.470 align:start position:0% like to have many contributors and yeah Reach<00:24:45.480> Out<00:24:46.020> thank<00:24:46.440> you<00:24:46.559> guys 00:24:48.470 --> 00:24:48.480 align:start position:0% Reach Out thank you guys 00:24:48.480 --> 00:24:50.630 align:start position:0% Reach Out thank you guys do<00:24:48.900> we<00:24:49.020> have<00:24:49.140> time<00:24:49.380> for<00:24:49.559> our<00:24:49.740> questions<00:24:49.860> or<00:24:50.280> I 00:24:50.630 --> 00:24:50.640 align:start position:0% do we have time for our questions or I 00:24:50.640 --> 00:24:52.789 align:start position:0% do we have time for our questions or I don't<00:24:50.820> okay<00:24:51.000> so<00:24:51.659> if<00:24:51.960> if<00:24:52.200> you<00:24:52.440> guys<00:24:52.559> have 00:24:52.789 --> 00:24:52.799 align:start position:0% don't okay so if if you guys have 00:24:52.799 --> 00:24:55.909 align:start position:0% don't okay so if if you guys have questions<00:24:53.220> happy<00:24:53.760> to 00:24:55.909 --> 00:24:55.919 align:start position:0% questions happy to 00:24:55.919 --> 00:24:57.890 align:start position:0% questions happy to um hi<00:24:56.580> thank<00:24:56.940> you<00:24:57.000> for<00:24:57.179> the<00:24:57.299> talk<00:24:57.419> that<00:24:57.659> was 00:24:57.890 --> 00:24:57.900 align:start position:0% um hi thank you for the talk that was 00:24:57.900 --> 00:24:59.450 align:start position:0% um hi thank you for the talk that was super<00:24:58.020> interesting<00:24:58.440> so<00:24:58.860> my<00:24:59.039> question<00:24:59.220> was 00:24:59.450 --> 00:24:59.460 align:start position:0% super interesting so my question was 00:24:59.460 --> 00:25:00.230 align:start position:0% super interesting so my question was about 00:25:00.230 --> 00:25:00.240 align:start position:0% about 00:25:00.240 --> 00:25:02.149 align:start position:0% about um<00:25:00.299> updating<00:25:00.720> of<00:25:00.960> ZK<00:25:01.200> badges<00:25:01.679> so<00:25:01.860> for<00:25:01.980> example 00:25:02.149 --> 00:25:02.159 align:start position:0% um updating of ZK badges so for example 00:25:02.159 --> 00:25:04.190 align:start position:0% um updating of ZK badges so for example in<00:25:02.340> the<00:25:02.460> example<00:25:02.700> you<00:25:02.880> gave<00:25:03.059> you<00:25:03.299> said<00:25:03.539> you<00:25:04.080> own 00:25:04.190 --> 00:25:04.200 align:start position:0% in the example you gave you said you own 00:25:04.200 --> 00:25:05.630 align:start position:0% in the example you gave you said you own the<00:25:04.380> punk<00:25:04.559> and<00:25:04.799> then<00:25:04.860> you<00:25:04.980> create<00:25:05.159> the<00:25:05.340> zika 00:25:05.630 --> 00:25:05.640 align:start position:0% the punk and then you create the zika 00:25:05.640 --> 00:25:07.430 align:start position:0% the punk and then you create the zika badge<00:25:05.940> that<00:25:06.059> you<00:25:06.179> own<00:25:06.240> the<00:25:06.360> punk<00:25:06.600> what<00:25:07.260> happens 00:25:07.430 --> 00:25:07.440 align:start position:0% badge that you own the punk what happens 00:25:07.440 --> 00:25:09.350 align:start position:0% badge that you own the punk what happens to<00:25:07.740> that<00:25:07.860> badge<00:25:08.280> when<00:25:08.460> you<00:25:08.640> transfer<00:25:09.059> the<00:25:09.179> punk 00:25:09.350 --> 00:25:09.360 align:start position:0% to that badge when you transfer the punk 00:25:09.360 --> 00:25:11.570 align:start position:0% to that badge when you transfer the punk and<00:25:09.720> don't<00:25:09.900> own<00:25:10.440> it<00:25:10.679> anymore 00:25:11.570 --> 00:25:11.580 align:start position:0% and don't own it anymore 00:25:11.580 --> 00:25:14.090 align:start position:0% and don't own it anymore yeah<00:25:12.179> so<00:25:12.780> actually<00:25:13.020> for<00:25:13.320> the<00:25:13.500> Hydra<00:25:13.799> S1 00:25:14.090 --> 00:25:14.100 align:start position:0% yeah so actually for the Hydra S1 00:25:14.100 --> 00:25:15.490 align:start position:0% yeah so actually for the Hydra S1 resistor 00:25:15.490 --> 00:25:15.500 align:start position:0% resistor 00:25:15.500 --> 00:25:18.710 align:start position:0% resistor the<00:25:16.500> badge<00:25:16.919> is<00:25:17.280> a<00:25:17.460> snapshot<00:25:17.940> meaning<00:25:18.299> that<00:25:18.539> it 00:25:18.710 --> 00:25:18.720 align:start position:0% the badge is a snapshot meaning that it 00:25:18.720 --> 00:25:20.090 align:start position:0% the badge is a snapshot meaning that it doesn't<00:25:18.840> update 00:25:20.090 --> 00:25:20.100 align:start position:0% doesn't update 00:25:20.100 --> 00:25:22.250 align:start position:0% doesn't update but<00:25:20.640> that's<00:25:20.880> where<00:25:21.120> actually<00:25:21.360> the<00:25:21.780> protocol 00:25:22.250 --> 00:25:22.260 align:start position:0% but that's where actually the protocol 00:25:22.260 --> 00:25:23.930 align:start position:0% but that's where actually the protocol is<00:25:22.500> interesting<00:25:22.860> that<00:25:23.280> you<00:25:23.520> can<00:25:23.700> create 00:25:23.930 --> 00:25:23.940 align:start position:0% is interesting that you can create 00:25:23.940 --> 00:25:26.210 align:start position:0% is interesting that you can create another<00:25:24.600> adjuster 00:25:26.210 --> 00:25:26.220 align:start position:0% another adjuster 00:25:26.220 --> 00:25:28.370 align:start position:0% another adjuster that<00:25:26.640> could<00:25:26.760> be<00:25:26.880> updatable<00:25:27.360> and<00:25:27.840> like<00:25:28.020> I<00:25:28.200> don't 00:25:28.370 --> 00:25:28.380 align:start position:0% that could be updatable and like I don't 00:25:28.380 --> 00:25:31.190 align:start position:0% that could be updatable and like I don't know<00:25:28.500> every<00:25:29.039> like<00:25:29.880> some 00:25:31.190 --> 00:25:31.200 align:start position:0% know every like some 00:25:31.200 --> 00:25:33.289 align:start position:0% know every like some you<00:25:31.559> could<00:25:31.620> code<00:25:31.799> that<00:25:32.039> like<00:25:32.220> the<00:25:32.520> way<00:25:32.700> to<00:25:32.880> for 00:25:33.289 --> 00:25:33.299 align:start position:0% you could code that like the way to for 00:25:33.299 --> 00:25:36.169 align:start position:0% you could code that like the way to for a<00:25:33.600> central<00:25:34.260> party<00:25:34.620> to<00:25:34.919> update<00:25:35.220> the<00:25:35.460> route 00:25:36.169 --> 00:25:36.179 align:start position:0% a central party to update the route 00:25:36.179 --> 00:25:38.330 align:start position:0% a central party to update the route and<00:25:36.659> make<00:25:36.900> sure<00:25:37.140> that<00:25:37.380> the<00:25:37.620> badges<00:25:37.980> that<00:25:38.159> were 00:25:38.330 --> 00:25:38.340 align:start position:0% and make sure that the badges that were 00:25:38.340 --> 00:25:41.330 align:start position:0% and make sure that the badges that were issued<00:25:38.760> are<00:25:38.880> no<00:25:39.000> longer<00:25:39.240> issued<00:25:39.600> but 00:25:41.330 --> 00:25:41.340 align:start position:0% issued are no longer issued but 00:25:41.340 --> 00:25:43.870 align:start position:0% issued are no longer issued but I<00:25:41.820> think<00:25:41.940> that<00:25:42.179> it's<00:25:42.419> still<00:25:42.720> a<00:25:43.260> bit<00:25:43.440> complex 00:25:43.870 --> 00:25:43.880 align:start position:0% I think that it's still a bit complex 00:25:43.880 --> 00:25:46.310 align:start position:0% I think that it's still a bit complex and<00:25:44.880> the<00:25:45.059> best<00:25:45.179> way<00:25:45.360> is<00:25:45.480> really<00:25:45.720> to<00:25:45.960> think 00:25:46.310 --> 00:25:46.320 align:start position:0% and the best way is really to think 00:25:46.320 --> 00:25:47.870 align:start position:0% and the best way is really to think about<00:25:46.500> DK<00:25:46.860> badges<00:25:47.220> as<00:25:47.460> a<00:25:47.580> snapshot 00:25:47.870 --> 00:25:47.880 align:start position:0% about DK badges as a snapshot 00:25:47.880 --> 00:25:49.669 align:start position:0% about DK badges as a snapshot attestation<00:25:48.360> and<00:25:49.080> it's<00:25:49.200> up<00:25:49.380> to<00:25:49.500> the 00:25:49.669 --> 00:25:49.679 align:start position:0% attestation and it's up to the 00:25:49.679 --> 00:25:53.750 align:start position:0% attestation and it's up to the application<00:25:50.100> to<00:25:50.940> ask<00:25:51.240> for<00:25:51.659> users<00:25:51.960> to<00:25:52.140> renew<00:25:52.860> so 00:25:53.750 --> 00:25:53.760 align:start position:0% application to ask for users to renew so 00:25:53.760 --> 00:25:56.090 align:start position:0% application to ask for users to renew so yeah<00:25:54.480> that's<00:25:54.779> really<00:25:55.260> the<00:25:55.500> way<00:25:55.799> we<00:25:55.980> think 00:25:56.090 --> 00:25:56.100 align:start position:0% yeah that's really the way we think 00:25:56.100 --> 00:25:58.190 align:start position:0% yeah that's really the way we think about<00:25:56.220> it<00:25:56.460> now 00:25:58.190 --> 00:25:58.200 align:start position:0% about it now 00:25:58.200 --> 00:26:00.590 align:start position:0% about it now hi<00:25:58.679> thank<00:25:58.980> you<00:25:59.100> very<00:25:59.220> much<00:25:59.400> uh<00:26:00.059> really<00:26:00.299> cool 00:26:00.590 --> 00:26:00.600 align:start position:0% hi thank you very much uh really cool 00:26:00.600 --> 00:26:02.750 align:start position:0% hi thank you very much uh really cool stuff<00:26:01.020> uh<00:26:01.620> lack<00:26:01.860> of<00:26:01.980> privacy<00:26:02.400> is<00:26:02.520> of<00:26:02.640> course 00:26:02.750 --> 00:26:02.760 align:start position:0% stuff uh lack of privacy is of course 00:26:02.760 --> 00:26:05.930 align:start position:0% stuff uh lack of privacy is of course one<00:26:03.000> of<00:26:03.179> the<00:26:03.419> barriers<00:26:04.380> uh<00:26:04.919> in<00:26:05.220> this<00:26:05.340> ecosystem 00:26:05.930 --> 00:26:05.940 align:start position:0% one of the barriers uh in this ecosystem 00:26:05.940 --> 00:26:08.330 align:start position:0% one of the barriers uh in this ecosystem so<00:26:06.299> thank<00:26:06.539> you<00:26:06.659> for<00:26:06.779> addressing<00:26:07.140> that<00:26:07.380> uh<00:26:08.159> I 00:26:08.330 --> 00:26:08.340 align:start position:0% so thank you for addressing that uh I 00:26:08.340 --> 00:26:10.190 align:start position:0% so thank you for addressing that uh I have<00:26:08.460> a<00:26:08.640> general<00:26:08.820> question<00:26:09.240> about<00:26:09.480> how<00:26:09.900> do<00:26:10.020> you 00:26:10.190 --> 00:26:10.200 align:start position:0% have a general question about how do you 00:26:10.200 --> 00:26:11.830 align:start position:0% have a general question about how do you collaborate<00:26:10.799> with 00:26:11.830 --> 00:26:11.840 align:start position:0% collaborate with 00:26:11.840 --> 00:26:14.330 align:start position:0% collaborate with individuals<00:26:12.840> and<00:26:13.140> and<00:26:13.320> projects<00:26:13.799> within<00:26:14.159> the 00:26:14.330 --> 00:26:14.340 align:start position:0% individuals and and projects within the 00:26:14.340 --> 00:26:16.549 align:start position:0% individuals and and projects within the space<00:26:14.600> because<00:26:15.600> at<00:26:15.900> the<00:26:16.020> end<00:26:16.080> of<00:26:16.200> the<00:26:16.320> day<00:26:16.440> it's 00:26:16.549 --> 00:26:16.559 align:start position:0% space because at the end of the day it's 00:26:16.559 --> 00:26:19.070 align:start position:0% space because at the end of the day it's about<00:26:16.740> going<00:26:17.159> to<00:26:17.400> Market<00:26:17.640> and<00:26:18.179> it's<00:26:18.600> it's 00:26:19.070 --> 00:26:19.080 align:start position:0% about going to Market and it's it's 00:26:19.080 --> 00:26:21.950 align:start position:0% about going to Market and it's it's promoting<00:26:19.799> your<00:26:19.980> tool<00:26:20.340> to<00:26:20.640> yeah<00:26:21.299> individuals 00:26:21.950 --> 00:26:21.960 align:start position:0% promoting your tool to yeah individuals 00:26:21.960 --> 00:26:23.630 align:start position:0% promoting your tool to yeah individuals and<00:26:22.140> teams<00:26:22.380> that<00:26:22.559> are<00:26:22.679> building<00:26:22.799> could<00:26:23.520> you 00:26:23.630 --> 00:26:23.640 align:start position:0% and teams that are building could you 00:26:23.640 --> 00:26:26.090 align:start position:0% and teams that are building could you explain<00:26:23.760> what<00:26:24.120> kind<00:26:24.299> of<00:26:24.419> projects 00:26:26.090 --> 00:26:26.100 align:start position:0% explain what kind of projects 00:26:26.100 --> 00:26:29.029 align:start position:0% explain what kind of projects um any<00:26:26.700> projects<00:26:27.240> yeah<00:26:27.840> yeah<00:26:28.080> just<00:26:28.679> more 00:26:29.029 --> 00:26:29.039 align:start position:0% um any projects yeah yeah just more 00:26:29.039 --> 00:26:30.649 align:start position:0% um any projects yeah yeah just more generally<00:26:29.340> what's<00:26:29.580> your<00:26:29.760> strategy<00:26:30.120> to<00:26:30.480> to 00:26:30.649 --> 00:26:30.659 align:start position:0% generally what's your strategy to to 00:26:30.659 --> 00:26:33.710 align:start position:0% generally what's your strategy to to proliferate<00:26:31.380> yourself<00:26:31.980> okay<00:26:32.640> so<00:26:32.880> I<00:26:33.179> think<00:26:33.360> we 00:26:33.710 --> 00:26:33.720 align:start position:0% proliferate yourself okay so I think we 00:26:33.720 --> 00:26:35.630 align:start position:0% proliferate yourself okay so I think we are<00:26:33.840> a<00:26:33.960> project<00:26:34.080> that<00:26:34.380> that<00:26:34.679> should<00:26:35.400> be<00:26:35.580> used 00:26:35.630 --> 00:26:35.640 align:start position:0% are a project that that should be used 00:26:35.640 --> 00:26:37.909 align:start position:0% are a project that that should be used by<00:26:35.880> many<00:26:36.059> applications<00:26:36.600> first<00:26:37.380> I<00:26:37.620> think<00:26:37.740> that 00:26:37.909 --> 00:26:37.919 align:start position:0% by many applications first I think that 00:26:37.919 --> 00:26:39.409 align:start position:0% by many applications first I think that we<00:26:38.100> are<00:26:38.220> one<00:26:38.400> of<00:26:38.580> the<00:26:38.640> first<00:26:38.820> teams<00:26:39.179> that<00:26:39.299> are 00:26:39.409 --> 00:26:39.419 align:start position:0% we are one of the first teams that are 00:26:39.419 --> 00:26:42.830 align:start position:0% we are one of the first teams that are using<00:26:39.659> ZK<00:26:40.080> for<00:26:40.860> a<00:26:41.100> very<00:26:41.220> concrete<00:26:41.700> case<00:26:41.940> and<00:26:42.720> as 00:26:42.830 --> 00:26:42.840 align:start position:0% using ZK for a very concrete case and as 00:26:42.840 --> 00:26:44.330 align:start position:0% using ZK for a very concrete case and as I<00:26:43.020> told<00:26:43.140> you<00:26:43.200> about<00:26:43.380> we<00:26:43.679> can<00:26:43.799> have<00:26:43.919> multiple 00:26:44.330 --> 00:26:44.340 align:start position:0% I told you about we can have multiple 00:26:44.340 --> 00:26:47.990 align:start position:0% I told you about we can have multiple zika<00:26:44.880> testers<00:26:45.659> so<00:26:46.140> if<00:26:46.500> we<00:26:46.740> have<00:26:46.980> a<00:26:47.340> ZK<00:26:47.760> team 00:26:47.990 --> 00:26:48.000 align:start position:0% zika testers so if we have a ZK team 00:26:48.000 --> 00:26:50.269 align:start position:0% zika testers so if we have a ZK team that<00:26:48.419> has<00:26:48.539> created<00:26:48.779> a<00:26:49.020> musical<00:26:49.440> scheme<00:26:49.799> we<00:26:50.159> are 00:26:50.269 --> 00:26:50.279 align:start position:0% that has created a musical scheme we are 00:26:50.279 --> 00:26:53.210 align:start position:0% that has created a musical scheme we are using<00:26:50.580> row<00:26:50.880> 16<00:26:51.120> uh<00:26:51.900> Hydra<00:26:52.559> as<00:26:52.740> well<00:26:52.919> that<00:26:53.100> is 00:26:53.210 --> 00:26:53.220 align:start position:0% using row 16 uh Hydra as well that is 00:26:53.220 --> 00:26:54.890 align:start position:0% using row 16 uh Hydra as well that is very<00:26:53.340> specific<00:26:53.640> but<00:26:53.940> if<00:26:54.240> another<00:26:54.480> team<00:26:54.720> has 00:26:54.890 --> 00:26:54.900 align:start position:0% very specific but if another team has 00:26:54.900 --> 00:26:57.590 align:start position:0% very specific but if another team has another<00:26:55.140> way<00:26:55.380> to<00:26:55.559> create<00:26:56.179> attestations<00:26:57.179> we 00:26:57.590 --> 00:26:57.600 align:start position:0% another way to create attestations we 00:26:57.600 --> 00:26:59.750 align:start position:0% another way to create attestations we can<00:26:57.720> think<00:26:57.900> about<00:26:58.080> change<00:26:58.320> links<00:26:58.860> GCO<00:26:59.580> for 00:26:59.750 --> 00:26:59.760 align:start position:0% can think about change links GCO for 00:26:59.760 --> 00:27:01.850 align:start position:0% can think about change links GCO for instance<00:27:00.000> they<00:27:00.419> are<00:27:00.600> able<00:27:00.840> to<00:27:01.020> do<00:27:01.620> the 00:27:01.850 --> 00:27:01.860 align:start position:0% instance they are able to do the 00:27:01.860 --> 00:27:04.250 align:start position:0% instance they are able to do the characterization<00:27:02.340> from<00:27:02.640> web<00:27:02.880> to<00:27:03.120> data<00:27:03.779> they 00:27:04.250 --> 00:27:04.260 align:start position:0% characterization from web to data they 00:27:04.260 --> 00:27:06.049 align:start position:0% characterization from web to data they will<00:27:04.440> come<00:27:04.620> to<00:27:04.740> visitor<00:27:05.460> here<00:27:05.640> and<00:27:05.760> that's<00:27:05.880> why 00:27:06.049 --> 00:27:06.059 align:start position:0% will come to visitor here and that's why 00:27:06.059 --> 00:27:08.570 align:start position:0% will come to visitor here and that's why we<00:27:06.179> beat<00:27:06.360> it<00:27:06.539> for<00:27:07.380> other<00:27:07.559> teams<00:27:08.039> it's<00:27:08.220> if<00:27:08.460> you 00:27:08.570 --> 00:27:08.580 align:start position:0% we beat it for other teams it's if you 00:27:08.580 --> 00:27:09.830 align:start position:0% we beat it for other teams it's if you want<00:27:08.700> to<00:27:08.820> do<00:27:08.940> repetition<00:27:09.360> within<00:27:09.720> your 00:27:09.830 --> 00:27:09.840 align:start position:0% want to do repetition within your 00:27:09.840 --> 00:27:11.690 align:start position:0% want to do repetition within your governance<00:27:10.200> you<00:27:10.559> can<00:27:10.679> create<00:27:10.799> your<00:27:10.980> ZK<00:27:11.340> badge 00:27:11.690 --> 00:27:11.700 align:start position:0% governance you can create your ZK badge 00:27:11.700 --> 00:27:13.310 align:start position:0% governance you can create your ZK badge or<00:27:12.059> even<00:27:12.179> better<00:27:12.419> you<00:27:12.720> can<00:27:12.779> create<00:27:12.960> your<00:27:13.200> own 00:27:13.310 --> 00:27:13.320 align:start position:0% or even better you can create your own 00:27:13.320 --> 00:27:16.909 align:start position:0% or even better you can create your own zika<00:27:13.740> tester<00:27:14.100> and<00:27:15.059> build<00:27:15.900> logic<00:27:16.320> in<00:27:16.380> it<00:27:16.559> and<00:27:16.679> so 00:27:16.909 --> 00:27:16.919 align:start position:0% zika tester and build logic in it and so 00:27:16.919 --> 00:27:19.610 align:start position:0% zika tester and build logic in it and so whenever<00:27:17.340> somebody<00:27:17.580> let's<00:27:18.120> say<00:27:18.320> Minto<00:27:19.320> ZK 00:27:19.610 --> 00:27:19.620 align:start position:0% whenever somebody let's say Minto ZK 00:27:19.620 --> 00:27:21.769 align:start position:0% whenever somebody let's say Minto ZK badge<00:27:19.980> that<00:27:20.100> I<00:27:20.340> played<00:27:20.640> on<00:27:20.760> on<00:27:21.059> a<00:27:21.299> certain<00:27:21.419> game 00:27:21.769 --> 00:27:21.779 align:start position:0% badge that I played on on a certain game 00:27:21.779 --> 00:27:26.029 align:start position:0% badge that I played on on a certain game it<00:27:22.679> updates<00:27:23.100> the<00:27:23.460> metadata<00:27:24.240> of<00:27:24.600> of<00:27:25.320> their<00:27:25.620> nft 00:27:26.029 --> 00:27:26.039 align:start position:0% it updates the metadata of of their nft 00:27:26.039 --> 00:27:27.710 align:start position:0% it updates the metadata of of their nft or<00:27:26.520> you<00:27:26.640> can<00:27:26.760> do<00:27:26.880> so<00:27:27.059> much<00:27:27.179> things<00:27:27.360> it's<00:27:27.539> really 00:27:27.710 --> 00:27:27.720 align:start position:0% or you can do so much things it's really 00:27:27.720 --> 00:27:29.630 align:start position:0% or you can do so much things it's really big<00:27:27.900> to<00:27:28.200> have<00:27:28.559> fun<00:27:28.679> as<00:27:28.919> developers<00:27:29.279> but<00:27:29.520> it's 00:27:29.630 --> 00:27:29.640 align:start position:0% big to have fun as developers but it's 00:27:29.640 --> 00:27:31.850 align:start position:0% big to have fun as developers but it's going<00:27:29.820> to<00:27:29.940> gain<00:27:30.179> time<00:27:30.360> for<00:27:30.600> it<00:27:31.200> to<00:27:31.500> educate 00:27:31.850 --> 00:27:31.860 align:start position:0% going to gain time for it to educate 00:27:31.860 --> 00:27:33.409 align:start position:0% going to gain time for it to educate everybody<00:27:32.159> that 00:27:33.409 --> 00:27:33.419 align:start position:0% everybody that 00:27:33.419 --> 00:27:35.870 align:start position:0% everybody that generally<00:27:34.020> happy<00:27:34.260> to<00:27:34.500> speak<00:27:34.919> with<00:27:35.100> everyone<00:27:35.220> I 00:27:35.870 --> 00:27:35.880 align:start position:0% generally happy to speak with everyone I 00:27:35.880 --> 00:27:38.149 align:start position:0% generally happy to speak with everyone I have<00:27:36.059> a<00:27:36.179> question<00:27:36.360> here<00:27:36.740> uh<00:27:37.740> really 00:27:38.149 --> 00:27:38.159 align:start position:0% have a question here uh really 00:27:38.159 --> 00:27:41.029 align:start position:0% have a question here uh really fascinating<00:27:38.640> talk<00:27:39.000> super<00:27:39.419> amazing<00:27:39.900> and<00:27:40.620> one 00:27:41.029 --> 00:27:41.039 align:start position:0% fascinating talk super amazing and one 00:27:41.039 --> 00:27:42.769 align:start position:0% fascinating talk super amazing and one of<00:27:41.159> the<00:27:41.220> things<00:27:41.400> that<00:27:41.880> popped<00:27:42.360> into<00:27:42.480> my<00:27:42.659> mind 00:27:42.769 --> 00:27:42.779 align:start position:0% of the things that popped into my mind 00:27:42.779 --> 00:27:44.810 align:start position:0% of the things that popped into my mind when<00:27:43.080> you<00:27:43.260> said<00:27:43.440> that<00:27:43.620> this<00:27:43.860> is<00:27:44.039> comparable<00:27:44.460> to 00:27:44.810 --> 00:27:44.820 align:start position:0% when you said that this is comparable to 00:27:44.820 --> 00:27:47.330 align:start position:0% when you said that this is comparable to the<00:27:44.940> D5<00:27:45.299> movement<00:27:45.720> of<00:27:45.900> the<00:27:46.020> D5<00:27:46.260> summer 00:27:47.330 --> 00:27:47.340 align:start position:0% the D5 movement of the D5 summer 00:27:47.340 --> 00:27:50.450 align:start position:0% the D5 movement of the D5 summer D5<00:27:48.000> came<00:27:48.240> with<00:27:48.360> a<00:27:48.480> lot<00:27:48.600> of<00:27:48.720> hacks<00:27:49.020> and<00:27:49.919> a<00:27:50.159> lot<00:27:50.340> of 00:27:50.450 --> 00:27:50.460 align:start position:0% D5 came with a lot of hacks and a lot of 00:27:50.460 --> 00:27:52.430 align:start position:0% D5 came with a lot of hacks and a lot of blood<00:27:50.580> by<00:27:50.820> fire<00:27:51.059> so 00:27:52.430 --> 00:27:52.440 align:start position:0% blood by fire so 00:27:52.440 --> 00:27:55.310 align:start position:0% blood by fire so how<00:27:53.159> do<00:27:53.520> you<00:27:53.700> protect<00:27:54.059> the<00:27:54.240> Privacy<00:27:54.600> say<00:27:54.960> we 00:27:55.310 --> 00:27:55.320 align:start position:0% how do you protect the Privacy say we 00:27:55.320 --> 00:27:57.649 align:start position:0% how do you protect the Privacy say we put<00:27:55.500> all<00:27:55.679> our<00:27:55.860> addresses<00:27:56.400> have<00:27:57.179> this<00:27:57.480> like 00:27:57.649 --> 00:27:57.659 align:start position:0% put all our addresses have this like 00:27:57.659 --> 00:28:00.289 align:start position:0% put all our addresses have this like great<00:27:57.900> identity<00:27:58.320> and<00:27:59.100> you<00:27:59.640> know 00:28:00.289 --> 00:28:00.299 align:start position:0% great identity and you know 00:28:00.299 --> 00:28:03.769 align:start position:0% great identity and you know how<00:28:00.779> yeah<00:28:01.260> some<00:28:01.559> of<00:28:01.740> the<00:28:01.860> risk<00:28:02.100> of<00:28:02.159> that<00:28:02.340> and 00:28:03.769 --> 00:28:03.779 align:start position:0% how yeah some of the risk of that and 00:28:03.779 --> 00:28:06.710 align:start position:0% how yeah some of the risk of that and what<00:28:04.020> do<00:28:04.320> you<00:28:04.440> see<00:28:04.559> for<00:28:04.740> that<00:28:04.919> yeah<00:28:05.580> when<00:28:06.419> I<00:28:06.600> was 00:28:06.710 --> 00:28:06.720 align:start position:0% what do you see for that yeah when I was 00:28:06.720 --> 00:28:10.250 align:start position:0% what do you see for that yeah when I was doing<00:28:06.900> that<00:28:07.080> is<00:28:07.320> that<00:28:07.620> D5<00:28:08.520> was<00:28:08.760> raw<00:28:09.299> it<00:28:09.960> was<00:28:10.080> the 00:28:10.250 --> 00:28:10.260 align:start position:0% doing that is that D5 was raw it was the 00:28:10.260 --> 00:28:11.870 align:start position:0% doing that is that D5 was raw it was the first<00:28:10.380> time<00:28:10.500> we<00:28:10.679> discovered<00:28:11.340> like<00:28:11.580> before 00:28:11.870 --> 00:28:11.880 align:start position:0% first time we discovered like before 00:28:11.880 --> 00:28:14.690 align:start position:0% first time we discovered like before Banks<00:28:12.840> and<00:28:13.140> insurance<00:28:13.380> and<00:28:13.740> all<00:28:13.919> like<00:28:14.340> all<00:28:14.580> the 00:28:14.690 --> 00:28:14.700 align:start position:0% Banks and insurance and all like all the 00:28:14.700 --> 00:28:16.430 align:start position:0% Banks and insurance and all like all the financial<00:28:14.880> services<00:28:15.299> were<00:28:15.840> provided<00:28:16.260> by 00:28:16.430 --> 00:28:16.440 align:start position:0% financial services were provided by 00:28:16.440 --> 00:28:17.810 align:start position:0% financial services were provided by webto<00:28:16.799> applications<00:28:17.220> that<00:28:17.400> didn't<00:28:17.580> talk 00:28:17.810 --> 00:28:17.820 align:start position:0% webto applications that didn't talk 00:28:17.820 --> 00:28:20.750 align:start position:0% webto applications that didn't talk together<00:28:18.020> and<00:28:19.020> we<00:28:19.140> discovered<00:28:19.500> what<00:28:20.460> I<00:28:20.640> can 00:28:20.750 --> 00:28:20.760 align:start position:0% together and we discovered what I can 00:28:20.760 --> 00:28:22.549 align:start position:0% together and we discovered what I can deposit<00:28:21.179> in<00:28:21.299> a<00:28:21.419> lending<00:28:21.779> tool<00:28:22.020> and<00:28:22.260> then<00:28:22.380> use 00:28:22.549 --> 00:28:22.559 align:start position:0% deposit in a lending tool and then use 00:28:22.559 --> 00:28:24.110 align:start position:0% deposit in a lending tool and then use that<00:28:22.740> to<00:28:22.919> bring<00:28:23.039> Nicky<00:28:23.400> duty<00:28:23.580> to<00:28:23.700> an<00:28:23.880> exchange 00:28:24.110 --> 00:28:24.120 align:start position:0% that to bring Nicky duty to an exchange 00:28:24.120 --> 00:28:25.930 align:start position:0% that to bring Nicky duty to an exchange and<00:28:24.419> then<00:28:24.480> use<00:28:24.659> that<00:28:24.840> to<00:28:25.020> take<00:28:25.260> somewhere<00:28:25.620> and 00:28:25.930 --> 00:28:25.940 align:start position:0% and then use that to take somewhere and 00:28:25.940 --> 00:28:28.310 align:start position:0% and then use that to take somewhere and it's<00:28:26.940> huge<00:28:27.240> but<00:28:27.419> we<00:28:27.659> could<00:28:27.779> do<00:28:27.900> the<00:28:28.020> same<00:28:28.140> with 00:28:28.310 --> 00:28:28.320 align:start position:0% it's huge but we could do the same with 00:28:28.320 --> 00:28:29.690 align:start position:0% it's huge but we could do the same with social 00:28:29.690 --> 00:28:29.700 align:start position:0% social 00:28:29.700 --> 00:28:32.029 align:start position:0% social Capital<00:28:30.260> like<00:28:31.260> today 00:28:32.029 --> 00:28:32.039 align:start position:0% Capital like today 00:28:32.039 --> 00:28:34.010 align:start position:0% Capital like today it's<00:28:32.580> impossible<00:28:33.000> to<00:28:33.240> use<00:28:33.360> your<00:28:33.600> let's<00:28:33.900> say 00:28:34.010 --> 00:28:34.020 align:start position:0% it's impossible to use your let's say 00:28:34.020 --> 00:28:35.769 align:start position:0% it's impossible to use your let's say you<00:28:34.200> are<00:28:34.320> Uber<00:28:34.620> driver 00:28:35.769 --> 00:28:35.779 align:start position:0% you are Uber driver 00:28:35.779 --> 00:28:39.230 align:start position:0% you are Uber driver 2000<00:28:36.779> drives<00:28:37.320> five<00:28:37.679> stars<00:28:38.159> you<00:28:38.700> cannot<00:28:38.880> use<00:28:39.059> it 00:28:39.230 --> 00:28:39.240 align:start position:0% 2000 drives five stars you cannot use it 00:28:39.240 --> 00:28:41.090 align:start position:0% 2000 drives five stars you cannot use it to<00:28:39.419> get<00:28:39.539> a<00:28:39.779> good<00:28:39.960> loan 00:28:41.090 --> 00:28:41.100 align:start position:0% to get a good loan 00:28:41.100 --> 00:28:42.710 align:start position:0% to get a good loan that's<00:28:41.520> what<00:28:41.640> we<00:28:41.760> want<00:28:41.880> to<00:28:42.000> do<00:28:42.179> like<00:28:42.360> we<00:28:42.600> want 00:28:42.710 --> 00:28:42.720 align:start position:0% that's what we want to do like we want 00:28:42.720 --> 00:28:44.750 align:start position:0% that's what we want to do like we want to<00:28:42.900> have<00:28:43.260> credit<00:28:43.679> score<00:28:43.980> based<00:28:44.340> on<00:28:44.400> reputation 00:28:44.750 --> 00:28:44.760 align:start position:0% to have credit score based on reputation 00:28:44.760 --> 00:28:46.490 align:start position:0% to have credit score based on reputation and<00:28:45.000> you<00:28:45.179> can<00:28:45.360> access<00:28:45.659> a<00:28:46.080> better<00:28:46.200> interest 00:28:46.490 --> 00:28:46.500 align:start position:0% and you can access a better interest 00:28:46.500 --> 00:28:48.590 align:start position:0% and you can access a better interest rate<00:28:46.799> so 00:28:48.590 --> 00:28:48.600 align:start position:0% rate so 00:28:48.600 --> 00:28:50.390 align:start position:0% rate so so<00:28:48.900> again<00:28:49.140> we<00:28:49.440> are<00:28:49.620> new<00:28:49.799> primitive<00:28:50.159> that 00:28:50.390 --> 00:28:50.400 align:start position:0% so again we are new primitive that 00:28:50.400 --> 00:28:52.789 align:start position:0% so again we are new primitive that should<00:28:50.520> allow<00:28:50.820> new<00:28:51.000> stuff<00:28:51.380> in<00:28:52.380> a<00:28:52.559> privacy 00:28:52.789 --> 00:28:52.799 align:start position:0% should allow new stuff in a privacy 00:28:52.799 --> 00:28:55.610 align:start position:0% should allow new stuff in a privacy preserving<00:28:53.279> way<00:28:53.400> so<00:28:53.580> yeah<00:28:53.760> let's<00:28:54.419> uh 00:28:55.610 --> 00:28:55.620 align:start position:0% preserving way so yeah let's uh 00:28:55.620 --> 00:28:58.549 align:start position:0% preserving way so yeah let's uh I<00:28:56.159> think<00:28:56.279> it<00:28:56.520> yeah<00:28:56.940> I<00:28:57.419> think<00:28:57.539> it<00:28:57.960> time's<00:28:58.320> up<00:28:58.380> for 00:28:58.549 --> 00:28:58.559 align:start position:0% I think it yeah I think it time's up for 00:28:58.559 --> 00:29:01.310 align:start position:0% I think it yeah I think it time's up for now<00:28:58.740> maybe<00:28:59.580> you're<00:29:00.120> really<00:29:00.539> happy<00:29:00.720> to<00:29:00.960> stay 00:29:01.310 --> 00:29:01.320 align:start position:0% now maybe you're really happy to stay 00:29:01.320 --> 00:29:04.070 align:start position:0% now maybe you're really happy to stay there<00:29:01.500> for<00:29:01.980> more<00:29:02.220> questions<00:29:02.520> okay 00:29:04.070 --> 00:29:04.080 align:start position:0% there for more questions okay 00:29:04.080 --> 00:29:05.830 align:start position:0% there for more questions okay thank<00:29:04.679> you 00:29:05.830 --> 00:29:05.840 align:start position:0% thank you 00:29:05.840 --> 00:29:09.320 align:start position:0% thank you thank<00:29:06.840> you<00:29:06.900> very<00:29:07.080> much