WEBVTT Kind: captions Language: en 00:00:00.500 --> 00:00:04.579 align:start position:0% we<00:00:01.500> live<00:00:01.680> in<00:00:01.800> a<00:00:01.890> world<00:00:02.899> where<00:00:03.899> there<00:00:04.140> are<00:00:04.170> very 00:00:04.579 --> 00:00:04.589 align:start position:0% we live in a world where there are very 00:00:04.589 --> 00:00:09.919 align:start position:0% we live in a world where there are very few<00:00:06.529> certification<00:00:07.529> authorities<00:00:08.750> most<00:00:09.750> of 00:00:09.919 --> 00:00:09.929 align:start position:0% few certification authorities most of 00:00:09.929 --> 00:00:16.970 align:start position:0% few certification authorities most of them<00:00:10.139> are<00:00:12.710> banks<00:00:14.240> government's<00:00:15.980> big 00:00:16.970 --> 00:00:16.980 align:start position:0% them are banks government's big 00:00:16.980 --> 00:00:21.980 align:start position:0% them are banks government's big corporations<00:00:18.710> but<00:00:19.710> we<00:00:20.609> want<00:00:20.970> that<00:00:21.539> each<00:00:21.930> of 00:00:21.980 --> 00:00:21.990 align:start position:0% corporations but we want that each of 00:00:21.990 --> 00:00:25.970 align:start position:0% corporations but we want that each of you<00:00:22.470> each<00:00:22.769> of<00:00:23.010> us<00:00:23.900> can<00:00:24.900> be<00:00:24.960> a<00:00:25.320> certification 00:00:25.970 --> 00:00:25.980 align:start position:0% you each of us can be a certification 00:00:25.980 --> 00:00:29.630 align:start position:0% you each of us can be a certification Authority<00:00:26.990> that's<00:00:27.990> the<00:00:28.199> main<00:00:28.380> goal<00:00:28.410> of<00:00:28.949> the 00:00:29.630 --> 00:00:29.640 align:start position:0% Authority that's the main goal of the 00:00:29.640 --> 00:00:32.600 align:start position:0% Authority that's the main goal of the island<00:00:30.150> free<00:00:30.449> project<00:00:31.380> we<00:00:32.160> want<00:00:32.430> to 00:00:32.600 --> 00:00:32.610 align:start position:0% island free project we want to 00:00:32.610 --> 00:00:35.420 align:start position:0% island free project we want to democratize<00:00:33.210> democratize<00:00:34.430> the 00:00:35.420 --> 00:00:35.430 align:start position:0% democratize democratize the 00:00:35.430 --> 00:00:38.090 align:start position:0% democratize democratize the certification<00:00:36.270> part<00:00:36.540> the<00:00:37.320> claiming<00:00:37.829> part 00:00:38.090 --> 00:00:38.100 align:start position:0% certification part the claiming part 00:00:38.100 --> 00:00:41.889 align:start position:0% certification part the claiming part when<00:00:38.940> we<00:00:38.969> are<00:00:39.180> doing<00:00:39.480> a<00:00:39.600> claim<00:00:39.960> not<00:00:40.920> matter<00:00:41.250> if 00:00:41.889 --> 00:00:41.899 align:start position:0% when we are doing a claim not matter if 00:00:41.899 --> 00:00:45.740 align:start position:0% when we are doing a claim not matter if is<00:00:42.899> done<00:00:43.739> by<00:00:43.980> a<00:00:44.010> government<00:00:44.309> or<00:00:44.820> if<00:00:45.270> it's<00:00:45.480> done 00:00:45.740 --> 00:00:45.750 align:start position:0% is done by a government or if it's done 00:00:45.750 --> 00:00:48.860 align:start position:0% is done by a government or if it's done by<00:00:46.320> your<00:00:46.530> fake<00:00:46.890> identity<00:00:47.640> when<00:00:48.570> they<00:00:48.780> are 00:00:48.860 --> 00:00:48.870 align:start position:0% by your fake identity when they are 00:00:48.870 --> 00:00:51.740 align:start position:0% by your fake identity when they are doing<00:00:49.079> a<00:00:49.289> claim<00:00:49.850> cryptographically<00:00:50.850> this 00:00:51.740 --> 00:00:51.750 align:start position:0% doing a claim cryptographically this 00:00:51.750 --> 00:00:54.319 align:start position:0% doing a claim cryptographically this claim<00:00:52.079> is<00:00:52.289> exactly<00:00:52.800> the<00:00:52.980> same<00:00:53.190> it's<00:00:53.820> a<00:00:54.059> claim 00:00:54.319 --> 00:00:54.329 align:start position:0% claim is exactly the same it's a claim 00:00:54.329 --> 00:00:57.590 align:start position:0% claim is exactly the same it's a claim that<00:00:54.930> can<00:00:55.170> be<00:00:55.320> proved<00:00:55.620> tomorrow<00:00:56.579> or<00:00:56.969> any<00:00:57.329> day 00:00:57.590 --> 00:00:57.600 align:start position:0% that can be proved tomorrow or any day 00:00:57.600 --> 00:01:02.650 align:start position:0% that can be proved tomorrow or any day in<00:00:57.780> the<00:00:57.870> future<00:01:00.260> before<00:01:01.260> going<00:01:01.829> deep<00:01:02.039> in<00:01:02.280> what 00:01:02.650 --> 00:01:02.660 align:start position:0% in the future before going deep in what 00:01:02.660 --> 00:01:06.100 align:start position:0% in the future before going deep in what technically<00:01:03.660> we<00:01:03.780> were<00:01:03.989> doing<00:01:04.320> in<00:01:04.559> iron<00:01:05.309> 3<00:01:05.580> I 00:01:06.100 --> 00:01:06.110 align:start position:0% technically we were doing in iron 3 I 00:01:06.110 --> 00:01:08.420 align:start position:0% technically we were doing in iron 3 I would<00:01:07.110> like<00:01:07.320> first<00:01:07.590> to<00:01:07.770> introduce<00:01:08.189> three 00:01:08.420 --> 00:01:08.430 align:start position:0% would like first to introduce three 00:01:08.430 --> 00:01:10.580 align:start position:0% would like first to introduce three concepts<00:01:08.939> I<00:01:09.210> want<00:01:09.570> to<00:01:09.900> introduce<00:01:10.260> what<00:01:10.560> we 00:01:10.580 --> 00:01:10.590 align:start position:0% concepts I want to introduce what we 00:01:10.590 --> 00:01:14.000 align:start position:0% concepts I want to introduce what we understand<00:01:11.510> as<00:01:12.510> an<00:01:12.750> identity<00:01:13.170> what<00:01:13.860> we 00:01:14.000 --> 00:01:14.010 align:start position:0% understand as an identity what we 00:01:14.010 --> 00:01:17.690 align:start position:0% understand as an identity what we understand<00:01:14.640> as<00:01:15.270> a<00:01:16.200> claim<00:01:16.470> and<00:01:16.799> when<00:01:17.159> what<00:01:17.520> we 00:01:17.690 --> 00:01:17.700 align:start position:0% understand as a claim and when what we 00:01:17.700 --> 00:01:21.649 align:start position:0% understand as a claim and when what we understand<00:01:18.240> as<00:01:18.509> a<00:01:18.570> proof<00:01:19.460> identity<00:01:20.460> I<00:01:20.729> don't 00:01:21.649 --> 00:01:21.659 align:start position:0% understand as a proof identity I don't 00:01:21.659 --> 00:01:24.800 align:start position:0% understand as a proof identity I don't want<00:01:21.840> to<00:01:22.080> go<00:01:22.320> deep<00:01:22.770> I<00:01:23.220> don't<00:01:24.030> want<00:01:24.210> to<00:01:24.420> enter<00:01:24.540> in 00:01:24.800 --> 00:01:24.810 align:start position:0% want to go deep I don't want to enter in 00:01:24.810 --> 00:01:27.770 align:start position:0% want to go deep I don't want to enter in philosophical<00:01:26.030> philosophical<00:01:27.030> definitions 00:01:27.770 --> 00:01:27.780 align:start position:0% philosophical philosophical definitions 00:01:27.780 --> 00:01:29.480 align:start position:0% philosophical philosophical definitions and<00:01:27.990> all<00:01:28.110> that<00:01:28.320> I<00:01:28.619> will<00:01:29.040> put<00:01:29.189> you<00:01:29.310> some 00:01:29.480 --> 00:01:29.490 align:start position:0% and all that I will put you some 00:01:29.490 --> 00:01:31.700 align:start position:0% and all that I will put you some examples<00:01:30.000> an<00:01:30.180> identity<00:01:30.570> can<00:01:30.840> be<00:01:30.869> a<00:01:30.990> person<00:01:31.500> but 00:01:31.700 --> 00:01:31.710 align:start position:0% examples an identity can be a person but 00:01:31.710 --> 00:01:34.940 align:start position:0% examples an identity can be a person but can<00:01:32.280> be<00:01:32.430> a<00:01:32.700> company<00:01:33.420> can<00:01:33.990> be<00:01:34.110> an<00:01:34.229> organization 00:01:34.940 --> 00:01:34.950 align:start position:0% can be a company can be an organization 00:01:34.950 --> 00:01:38.420 align:start position:0% can be a company can be an organization can<00:01:35.250> be<00:01:35.400> a<00:01:35.430> dau<00:01:35.670> can<00:01:36.540> be<00:01:36.689> a<00:01:36.720> government<00:01:37.110> or<00:01:37.500> if 00:01:38.420 --> 00:01:38.430 align:start position:0% can be a dau can be a government or if 00:01:38.430 --> 00:01:40.640 align:start position:0% can be a dau can be a government or if you<00:01:38.610> want<00:01:38.850> even<00:01:39.450> can<00:01:39.689> be<00:01:39.840> a<00:01:39.869> thing<00:01:40.259> you<00:01:40.530> know 00:01:40.640 --> 00:01:40.650 align:start position:0% you want even can be a thing you know 00:01:40.650 --> 00:01:43.160 align:start position:0% you want even can be a thing you know can<00:01:40.890> be<00:01:40.920> a<00:01:41.070> microphone<00:01:41.790> or<00:01:41.850> can<00:01:42.240> be<00:01:42.390> a<00:01:42.420> chair<00:01:42.899> or 00:01:43.160 --> 00:01:43.170 align:start position:0% can be a microphone or can be a chair or 00:01:43.170 --> 00:01:45.350 align:start position:0% can be a microphone or can be a chair or can<00:01:43.560> be<00:01:43.680> this<00:01:43.829> room<00:01:44.130> half<00:01:44.640> an<00:01:44.790> identity<00:01:45.119> or<00:01:45.240> a 00:01:45.350 --> 00:01:45.360 align:start position:0% can be this room half an identity or a 00:01:45.360 --> 00:01:46.819 align:start position:0% can be this room half an identity or a bought<00:01:45.619> okay 00:01:46.819 --> 00:01:46.829 align:start position:0% bought okay 00:01:46.829 --> 00:01:49.730 align:start position:0% bought okay in<00:01:47.399> we<00:01:47.850> in<00:01:48.180> an<00:01:48.659> or<00:01:48.869> system<00:01:49.259> when<00:01:49.409> we<00:01:49.530> talk<00:01:49.710> about 00:01:49.730 --> 00:01:49.740 align:start position:0% in we in an or system when we talk about 00:01:49.740 --> 00:01:51.800 align:start position:0% in we in an or system when we talk about the<00:01:50.159> identity<00:01:50.640> mainly<00:01:51.329> we<00:01:51.450> refer<00:01:51.780> to 00:01:51.800 --> 00:01:51.810 align:start position:0% the identity mainly we refer to 00:01:51.810 --> 00:01:56.120 align:start position:0% the identity mainly we refer to identities<00:01:52.500> as<00:01:53.930> accounts<00:01:54.930> we<00:01:55.560> represent 00:01:56.120 --> 00:01:56.130 align:start position:0% identities as accounts we represent 00:01:56.130 --> 00:01:58.340 align:start position:0% identities as accounts we represent identities<00:01:56.790> by<00:01:56.969> accounts<00:01:57.509> in<00:01:57.630> general<00:01:58.140> they 00:01:58.340 --> 00:01:58.350 align:start position:0% identities by accounts in general they 00:01:58.350 --> 00:02:00.800 align:start position:0% identities by accounts in general they are<00:01:58.380> going<00:01:58.680> to<00:01:58.740> be<00:01:58.860> smart<00:01:59.130> contracts<00:01:59.729> okay<00:02:00.420> so 00:02:00.800 --> 00:02:00.810 align:start position:0% are going to be smart contracts okay so 00:02:00.810 --> 00:02:02.749 align:start position:0% are going to be smart contracts okay so the<00:02:01.229> address<00:02:01.649> of<00:02:01.770> a<00:02:01.860> smart<00:02:02.070> contract<00:02:02.460> is<00:02:02.549> going 00:02:02.749 --> 00:02:02.759 align:start position:0% the address of a smart contract is going 00:02:02.759 --> 00:02:06.740 align:start position:0% the address of a smart contract is going to<00:02:02.850> be<00:02:02.909> or<00:02:03.200> identifier<00:02:04.200> of<00:02:04.469> that<00:02:04.829> identity<00:02:05.750> the 00:02:06.740 --> 00:02:06.750 align:start position:0% to be or identifier of that identity the 00:02:06.750 --> 00:02:11.410 align:start position:0% to be or identifier of that identity the next<00:02:06.990> concept<00:02:07.439> is<00:02:08.039> about<00:02:08.280> claim<00:02:08.759> claim<00:02:09.479> is 00:02:11.410 --> 00:02:11.420 align:start position:0% next concept is about claim claim is 00:02:11.420 --> 00:02:12.790 align:start position:0% next concept is about claim claim is understand<00:02:12.420> me 00:02:12.790 --> 00:02:12.800 align:start position:0% understand me 00:02:12.800 --> 00:02:15.160 align:start position:0% understand me if<00:02:13.370> you<00:02:13.580> want<00:02:13.790> and<00:02:14.030> and<00:02:14.390> not<00:02:14.570> rightist<00:02:15.080> a 00:02:15.160 --> 00:02:15.170 align:start position:0% if you want and and not rightist a 00:02:15.170 --> 00:02:18.970 align:start position:0% if you want and and not rightist a statment<00:02:15.820> okay<00:02:16.820> so<00:02:17.390> something<00:02:17.870> that<00:02:18.140> an 00:02:18.970 --> 00:02:18.980 align:start position:0% statment okay so something that an 00:02:18.980 --> 00:02:21.940 align:start position:0% statment okay so something that an identity<00:02:19.490> is<00:02:19.760> saying<00:02:20.410> most<00:02:21.410> of<00:02:21.560> the<00:02:21.680> times 00:02:21.940 --> 00:02:21.950 align:start position:0% identity is saying most of the times 00:02:21.950 --> 00:02:24.700 align:start position:0% identity is saying most of the times these<00:02:22.520> talents<00:02:23.240> refer<00:02:23.630> to<00:02:23.870> other<00:02:24.050> identities 00:02:24.700 --> 00:02:24.710 align:start position:0% these talents refer to other identities 00:02:24.710 --> 00:02:29.890 align:start position:0% these talents refer to other identities for<00:02:25.700> example<00:02:26.350> when<00:02:27.350> a<00:02:27.640> university<00:02:28.640> is<00:02:29.390> saying 00:02:29.890 --> 00:02:29.900 align:start position:0% for example when a university is saying 00:02:29.900 --> 00:02:33.010 align:start position:0% for example when a university is saying that<00:02:30.770> this<00:02:31.460> a<00:02:31.520> student<00:02:32.030> make<00:02:32.480> it<00:02:32.660> make<00:02:32.840> the 00:02:33.010 --> 00:02:33.020 align:start position:0% that this a student make it make the 00:02:33.020 --> 00:02:35.440 align:start position:0% that this a student make it make the degree<00:02:33.320> this<00:02:34.220> is<00:02:34.400> a<00:02:34.430> stand<00:02:34.910> man<00:02:35.090> this<00:02:35.300> is<00:02:35.420> a 00:02:35.440 --> 00:02:35.450 align:start position:0% degree this is a stand man this is a 00:02:35.450 --> 00:02:38.620 align:start position:0% degree this is a stand man this is a claim<00:02:35.870> that<00:02:36.320> the<00:02:36.500> university<00:02:37.070> is<00:02:37.280> doing<00:02:37.790> over 00:02:38.620 --> 00:02:38.630 align:start position:0% claim that the university is doing over 00:02:38.630 --> 00:02:41.290 align:start position:0% claim that the university is doing over that<00:02:38.840> student<00:02:39.590> but<00:02:40.340> if<00:02:40.580> you<00:02:40.790> think<00:02:41.090> a<00:02:41.180> little 00:02:41.290 --> 00:02:41.300 align:start position:0% that student but if you think a little 00:02:41.300 --> 00:02:44.650 align:start position:0% that student but if you think a little bit<00:02:41.600> you<00:02:41.990> will<00:02:42.140> see<00:02:42.440> that<00:02:42.860> almost<00:02:43.660> anything 00:02:44.650 --> 00:02:44.660 align:start position:0% bit you will see that almost anything 00:02:44.660 --> 00:02:47.680 align:start position:0% bit you will see that almost anything that<00:02:44.990> we<00:02:45.710> are<00:02:45.830> saying<00:02:46.160> can<00:02:46.460> be<00:02:46.610> not<00:02:46.790> rights<00:02:47.060> can 00:02:47.680 --> 00:02:47.690 align:start position:0% that we are saying can be not rights can 00:02:47.690 --> 00:02:50.620 align:start position:0% that we are saying can be not rights can be<00:02:47.810> converted<00:02:48.110> as<00:02:48.410> a<00:02:48.440> claim<00:02:49.390> examples<00:02:50.390> an 00:02:50.620 --> 00:02:50.630 align:start position:0% be converted as a claim examples an 00:02:50.630 --> 00:02:56.680 align:start position:0% be converted as a claim examples an invoice<00:02:51.200> that's<00:02:51.950> making<00:02:52.370> a<00:02:52.490> company<00:02:53.090> I<00:02:55.690> like 00:02:56.680 --> 00:02:56.690 align:start position:0% invoice that's making a company I like 00:02:56.690 --> 00:03:01.450 align:start position:0% invoice that's making a company I like in<00:02:57.560> a<00:02:57.710> facebook<00:02:58.330> can<00:02:59.330> be<00:02:59.530> an<00:03:00.530> endorsement<00:03:01.070> to 00:03:01.450 --> 00:03:01.460 align:start position:0% in a facebook can be an endorsement to 00:03:01.460 --> 00:03:05.020 align:start position:0% in a facebook can be an endorsement to somebody<00:03:02.000> else<00:03:02.920> or<00:03:03.920> if<00:03:04.040> you<00:03:04.190> want<00:03:04.430> even<00:03:04.760> a 00:03:05.020 --> 00:03:05.030 align:start position:0% somebody else or if you want even a 00:03:05.030 --> 00:03:07.450 align:start position:0% somebody else or if you want even a single<00:03:05.270> message<00:03:05.780> a<00:03:06.050> single<00:03:06.470> email<00:03:06.590> at<00:03:07.190> the<00:03:07.340> end 00:03:07.450 --> 00:03:07.460 align:start position:0% single message a single email at the end 00:03:07.460 --> 00:03:10.330 align:start position:0% single message a single email at the end is<00:03:07.670> a<00:03:07.700> claim<00:03:08.090> that<00:03:08.630> I'm<00:03:08.810> doing<00:03:08.990> as<00:03:09.380> you<00:03:10.010> can<00:03:10.160> see 00:03:10.330 --> 00:03:10.340 align:start position:0% is a claim that I'm doing as you can see 00:03:10.340 --> 00:03:13.060 align:start position:0% is a claim that I'm doing as you can see there<00:03:10.580> are<00:03:10.670> claims<00:03:10.940> that<00:03:11.090> can<00:03:11.330> be<00:03:11.470> public<00:03:12.470> but 00:03:13.060 --> 00:03:13.070 align:start position:0% there are claims that can be public but 00:03:13.070 --> 00:03:14.580 align:start position:0% there are claims that can be public but there<00:03:13.220> are<00:03:13.340> so<00:03:13.490> claims<00:03:13.760> that<00:03:13.910> can<00:03:14.090> be<00:03:14.210> private 00:03:14.580 --> 00:03:14.590 align:start position:0% there are so claims that can be private 00:03:14.590 --> 00:03:16.780 align:start position:0% there are so claims that can be private claims<00:03:15.590> is<00:03:15.770> something<00:03:16.130> that<00:03:16.280> we<00:03:16.460> are<00:03:16.490> just 00:03:16.780 --> 00:03:16.790 align:start position:0% claims is something that we are just 00:03:16.790 --> 00:03:20.560 align:start position:0% claims is something that we are just saying<00:03:17.110> okay<00:03:18.110> and<00:03:18.290> the<00:03:18.830> next<00:03:19.190> and<00:03:19.430> why<00:03:20.090> we<00:03:20.330> want 00:03:20.560 --> 00:03:20.570 align:start position:0% saying okay and the next and why we want 00:03:20.570 --> 00:03:22.810 align:start position:0% saying okay and the next and why we want to<00:03:20.630> do<00:03:20.810> claims<00:03:21.110> why<00:03:21.800> we<00:03:22.010> want<00:03:22.250> to<00:03:22.430> not<00:03:22.580> write 00:03:22.810 --> 00:03:22.820 align:start position:0% to do claims why we want to not write 00:03:22.820 --> 00:03:23.380 align:start position:0% to do claims why we want to not write claims 00:03:23.380 --> 00:03:23.390 align:start position:0% claims 00:03:23.390 --> 00:03:25.870 align:start position:0% claims mainly<00:03:24.170> because<00:03:24.320> we<00:03:24.740> want<00:03:25.010> to<00:03:25.220> prove<00:03:25.520> those 00:03:25.870 --> 00:03:25.880 align:start position:0% mainly because we want to prove those 00:03:25.880 --> 00:03:29.980 align:start position:0% mainly because we want to prove those claims<00:03:27.459> sometime<00:03:28.459> in<00:03:28.670> the<00:03:28.790> future<00:03:28.940> and<00:03:29.390> here 00:03:29.980 --> 00:03:29.990 align:start position:0% claims sometime in the future and here 00:03:29.990 --> 00:03:33.730 align:start position:0% claims sometime in the future and here is<00:03:30.140> these<00:03:30.440> three<00:03:31.390> actor<00:03:32.390> parties<00:03:32.870> they<00:03:33.709> have 00:03:33.730 --> 00:03:33.740 align:start position:0% is these three actor parties they have 00:03:33.740 --> 00:03:35.949 align:start position:0% is these three actor parties they have the<00:03:34.160> claimer<00:03:34.430> this<00:03:35.360> game<00:03:35.570> could<00:03:35.780> be<00:03:35.870> the 00:03:35.949 --> 00:03:35.959 align:start position:0% the claimer this game could be the 00:03:35.959 --> 00:03:38.530 align:start position:0% the claimer this game could be the university<00:03:36.590> that's<00:03:37.280> doing<00:03:37.520> the<00:03:37.670> claim<00:03:37.910> over<00:03:38.120> a 00:03:38.530 --> 00:03:38.540 align:start position:0% university that's doing the claim over a 00:03:38.540 --> 00:03:42.910 align:start position:0% university that's doing the claim over a student<00:03:39.130> and<00:03:40.390> then<00:03:41.390> the<00:03:41.660> student<00:03:41.840> when<00:03:42.680> goes 00:03:42.910 --> 00:03:42.920 align:start position:0% student and then the student when goes 00:03:42.920 --> 00:03:47.500 align:start position:0% student and then the student when goes to<00:03:43.190> for<00:03:43.520> a<00:03:43.550> job<00:03:43.880> and<00:03:44.090> is<00:03:44.800> proving<00:03:46.390> to<00:03:47.390> the 00:03:47.500 --> 00:03:47.510 align:start position:0% to for a job and is proving to the 00:03:47.510 --> 00:03:51.190 align:start position:0% to for a job and is proving to the employee<00:03:47.959> that<00:03:48.490> he<00:03:49.490> already<00:03:49.670> had<00:03:50.420> this<00:03:50.750> degree 00:03:51.190 --> 00:03:51.200 align:start position:0% employee that he already had this degree 00:03:51.200 --> 00:03:54.720 align:start position:0% employee that he already had this degree and<00:03:51.760> because<00:03:52.760> there<00:03:53.000> is<00:03:53.060> this<00:03:53.650> relationship 00:03:54.720 --> 00:03:54.730 align:start position:0% and because there is this relationship 00:03:54.730 --> 00:03:57.850 align:start position:0% and because there is this relationship this<00:03:55.730> truce<00:03:56.060> Ness<00:03:56.270> between<00:03:56.780> the<00:03:57.200> employee<00:03:57.470> and 00:03:57.850 --> 00:03:57.860 align:start position:0% this truce Ness between the employee and 00:03:57.860 --> 00:04:01.630 align:start position:0% this truce Ness between the employee and the<00:03:57.890> university<00:03:58.850> this<00:03:59.660> proof<00:03:59.990> is<00:04:00.459> valid<00:04:01.459> for 00:04:01.630 --> 00:04:01.640 align:start position:0% the university this proof is valid for 00:04:01.640 --> 00:04:06.550 align:start position:0% the university this proof is valid for him<00:04:03.130> okay<00:04:04.160> these<00:04:04.670> proofs<00:04:04.970> can<00:04:05.930> be<00:04:06.050> many<00:04:06.230> kind 00:04:06.550 --> 00:04:06.560 align:start position:0% him okay these proofs can be many kind 00:04:06.560 --> 00:04:08.350 align:start position:0% him okay these proofs can be many kind of<00:04:06.740> proof<00:04:06.980> we<00:04:07.400> will<00:04:07.520> talk<00:04:07.700> a<00:04:07.730> little<00:04:07.880> bit<00:04:08.150> later 00:04:08.350 --> 00:04:08.360 align:start position:0% of proof we will talk a little bit later 00:04:08.360 --> 00:04:11.710 align:start position:0% of proof we will talk a little bit later but<00:04:08.989> can<00:04:09.260> be<00:04:09.410> on<00:04:09.709> chain<00:04:10.370> proof<00:04:10.670> if<00:04:10.970> you<00:04:11.420> want<00:04:11.600> to 00:04:11.710 --> 00:04:11.720 align:start position:0% but can be on chain proof if you want to 00:04:11.720 --> 00:04:14.080 align:start position:0% but can be on chain proof if you want to prove<00:04:11.930> to<00:04:12.110> a<00:04:12.140> smart<00:04:12.410> contract<00:04:12.860> of<00:04:13.040> chain<00:04:13.790> proof 00:04:14.080 --> 00:04:14.090 align:start position:0% prove to a smart contract of chain proof 00:04:14.090 --> 00:04:16.170 align:start position:0% prove to a smart contract of chain proof when<00:04:14.450> you<00:04:14.570> want<00:04:14.780> to<00:04:14.900> prove<00:04:15.350> peer-to-peer 00:04:16.170 --> 00:04:16.180 align:start position:0% when you want to prove peer-to-peer 00:04:16.180 --> 00:04:18.520 align:start position:0% when you want to prove peer-to-peer public<00:04:17.180> proof<00:04:17.450> when<00:04:17.810> you<00:04:17.900> want<00:04:18.049> to<00:04:18.169> prove<00:04:18.380> to 00:04:18.520 --> 00:04:18.530 align:start position:0% public proof when you want to prove to 00:04:18.530 --> 00:04:21.520 align:start position:0% public proof when you want to prove to everybody<00:04:19.540> there<00:04:20.540> are<00:04:20.630> many<00:04:20.870> kind<00:04:21.169> of<00:04:21.260> proof 00:04:21.520 --> 00:04:21.530 align:start position:0% everybody there are many kind of proof 00:04:21.530 --> 00:04:24.010 align:start position:0% everybody there are many kind of proof but<00:04:21.770> the<00:04:21.830> system<00:04:22.280> at<00:04:22.400> the<00:04:22.550> end<00:04:22.700> works<00:04:23.210> about<00:04:23.570> - 00:04:24.010 --> 00:04:24.020 align:start position:0% but the system at the end works about - 00:04:24.020 --> 00:04:27.230 align:start position:0% but the system at the end works about - we're<00:04:24.169> talking<00:04:24.350> about<00:04:24.620> this<00:04:25.160> kind<00:04:25.370> of 00:04:27.230 --> 00:04:27.240 align:start position:0% we're talking about this kind of 00:04:27.240 --> 00:04:34.610 align:start position:0% we're talking about this kind of in<00:04:28.240> area<00:04:28.600> 3<00:04:28.840> what<00:04:29.770> are<00:04:29.800> the<00:04:31.949> road<00:04:32.949> or<00:04:33.160> goals 00:04:34.610 --> 00:04:34.620 align:start position:0% in area 3 what are the road or goals 00:04:34.620 --> 00:04:38.610 align:start position:0% in area 3 what are the road or goals what<00:04:35.620> we<00:04:35.800> won<00:04:36.010> we<00:04:36.490> won<00:04:36.699> a<00:04:36.940> system<00:04:37.660> that<00:04:38.320> first 00:04:38.610 --> 00:04:38.620 align:start position:0% what we won we won a system that first 00:04:38.620 --> 00:04:42.270 align:start position:0% what we won we won a system that first of<00:04:38.800> all<00:04:38.949> must<00:04:39.669> be<00:04:39.850> private<00:04:40.660> by<00:04:41.110> design<00:04:41.560> and<00:04:41.830> by 00:04:42.270 --> 00:04:42.280 align:start position:0% of all must be private by design and by 00:04:42.280 --> 00:04:45.960 align:start position:0% of all must be private by design and by default<00:04:43.020> privacy<00:04:44.020> is<00:04:44.530> an<00:04:44.889> important<00:04:45.430> value<00:04:45.550> of 00:04:45.960 --> 00:04:45.970 align:start position:0% default privacy is an important value of 00:04:45.970 --> 00:04:50.640 align:start position:0% default privacy is an important value of iron<00:04:47.160> 3-1<00:04:48.190> self<00:04:48.760> sovereign<00:04:49.150> identity<00:04:49.840> we<00:04:50.350> want 00:04:50.640 --> 00:04:50.650 align:start position:0% iron 3-1 self sovereign identity we want 00:04:50.650 --> 00:04:54.629 align:start position:0% iron 3-1 self sovereign identity we want to<00:04:51.840> address<00:04:52.840> the<00:04:53.050> key<00:04:53.229> management<00:04:53.530> we<00:04:54.280> want<00:04:54.490> to 00:04:54.629 --> 00:04:54.639 align:start position:0% to address the key management we want to 00:04:54.639 --> 00:04:57.810 align:start position:0% to address the key management we want to be<00:04:54.760> accessible<00:04:55.720> usable<00:04:56.350> we<00:04:57.340> need<00:04:57.550> to<00:04:57.699> be 00:04:57.810 --> 00:04:57.820 align:start position:0% be accessible usable we need to be 00:04:57.820 --> 00:05:00.750 align:start position:0% be accessible usable we need to be scalable<00:04:58.240> and<00:04:58.720> we<00:04:59.710> also<00:04:59.860> want<00:05:00.280> to<00:05:00.490> be 00:05:00.750 --> 00:05:00.760 align:start position:0% scalable and we also want to be 00:05:00.760 --> 00:05:02.700 align:start position:0% scalable and we also want to be universal<00:05:01.540> that<00:05:01.660> is<00:05:01.780> interoperable<00:05:02.080> between 00:05:02.700 --> 00:05:02.710 align:start position:0% universal that is interoperable between 00:05:02.710 --> 00:05:06.050 align:start position:0% universal that is interoperable between the<00:05:02.800> systems<00:05:03.190> ok<00:05:04.090> let's<00:05:04.510> go<00:05:05.050> step<00:05:05.410> by<00:05:05.470> step 00:05:06.050 --> 00:05:06.060 align:start position:0% the systems ok let's go step by step 00:05:06.060 --> 00:05:09.570 align:start position:0% the systems ok let's go step by step first<00:05:07.060> cell<00:05:07.840> sovereign<00:05:08.290> identity<00:05:08.860> what<00:05:09.400> does 00:05:09.570 --> 00:05:09.580 align:start position:0% first cell sovereign identity what does 00:05:09.580 --> 00:05:12.120 align:start position:0% first cell sovereign identity what does it<00:05:09.729> mean<00:05:09.910> with<00:05:10.270> that<00:05:10.479> that<00:05:11.110> means<00:05:11.380> that<00:05:11.620> any<00:05:11.889> of 00:05:12.120 --> 00:05:12.130 align:start position:0% it mean with that that means that any of 00:05:12.130 --> 00:05:15.960 align:start position:0% it mean with that that means that any of you<00:05:12.340> can<00:05:13.180> create<00:05:13.720> as<00:05:13.990> many<00:05:14.729> identities<00:05:15.729> as 00:05:15.960 --> 00:05:15.970 align:start position:0% you can create as many identities as 00:05:15.970 --> 00:05:21.029 align:start position:0% you can create as many identities as they<00:05:16.360> won<00:05:17.160> and<00:05:18.270> this<00:05:19.270> should<00:05:19.570> be<00:05:19.600> I<00:05:20.050> would<00:05:21.010> say 00:05:21.029 --> 00:05:21.039 align:start position:0% they won and this should be I would say 00:05:21.039 --> 00:05:24.060 align:start position:0% they won and this should be I would say free<00:05:21.580> creating<00:05:22.419> an<00:05:22.539> identity<00:05:22.780> should<00:05:23.650> be<00:05:23.860> as 00:05:24.060 --> 00:05:24.070 align:start position:0% free creating an identity should be as 00:05:24.070 --> 00:05:27.689 align:start position:0% free creating an identity should be as easy<00:05:24.520> as<00:05:24.550> creating<00:05:25.210> a<00:05:25.840> normal<00:05:26.410> account<00:05:26.919> it 00:05:27.689 --> 00:05:27.699 align:start position:0% easy as creating a normal account it 00:05:27.699 --> 00:05:30.180 align:start position:0% easy as creating a normal account it does<00:05:27.940> not<00:05:28.120> need<00:05:28.360> to<00:05:28.690> have<00:05:29.080> any<00:05:29.199> gas<00:05:29.530> and<00:05:29.830> ether 00:05:30.180 --> 00:05:30.190 align:start position:0% does not need to have any gas and ether 00:05:30.190 --> 00:05:33.719 align:start position:0% does not need to have any gas and ether or<00:05:30.550> anything<00:05:30.820> like<00:05:31.210> that<00:05:31.240> and<00:05:32.280> we<00:05:33.280> say<00:05:33.490> that 00:05:33.719 --> 00:05:33.729 align:start position:0% or anything like that and we say that 00:05:33.729 --> 00:05:35.760 align:start position:0% or anything like that and we say that self-serving<00:05:34.450> because<00:05:34.870> you<00:05:35.260> full<00:05:35.530> control 00:05:35.760 --> 00:05:35.770 align:start position:0% self-serving because you full control 00:05:35.770 --> 00:05:40.050 align:start position:0% self-serving because you full control that<00:05:36.280> and<00:05:37.440> the<00:05:38.440> same<00:05:38.650> that<00:05:38.830> the<00:05:39.520> same<00:05:39.729> way<00:05:39.910> that 00:05:40.050 --> 00:05:40.060 align:start position:0% that and the same that the same way that 00:05:40.060 --> 00:05:41.670 align:start position:0% that and the same that the same way that happened<00:05:40.510> with<00:05:40.660> when<00:05:40.840> you<00:05:40.960> hold<00:05:41.200> a<00:05:41.349> normal 00:05:41.670 --> 00:05:41.680 align:start position:0% happened with when you hold a normal 00:05:41.680 --> 00:05:44.159 align:start position:0% happened with when you hold a normal account<00:05:42.010> in<00:05:42.340> Bitcoin<00:05:43.090> you<00:05:43.750> need<00:05:43.990> these 00:05:44.159 --> 00:05:44.169 align:start position:0% account in Bitcoin you need these 00:05:44.169 --> 00:05:48.300 align:start position:0% account in Bitcoin you need these responsibilities<00:05:45.130> of<00:05:45.310> keeping<00:05:45.910> the<00:05:46.030> keys<00:05:47.310> if 00:05:48.300 --> 00:05:48.310 align:start position:0% responsibilities of keeping the keys if 00:05:48.310 --> 00:05:50.370 align:start position:0% responsibilities of keeping the keys if you<00:05:48.729> lose<00:05:49.030> the<00:05:49.240> keys<00:05:49.450> in<00:05:49.690> some<00:05:49.870> way<00:05:50.020> you<00:05:50.080> can 00:05:50.370 --> 00:05:50.380 align:start position:0% you lose the keys in some way you can 00:05:50.380 --> 00:05:51.719 align:start position:0% you lose the keys in some way you can lose<00:05:50.560> the<00:05:50.710> responsibility<00:05:51.280> the<00:05:51.400> same<00:05:51.550> way 00:05:51.719 --> 00:05:51.729 align:start position:0% lose the responsibility the same way 00:05:51.729 --> 00:05:53.580 align:start position:0% lose the responsibility the same way that<00:05:51.910> in<00:05:52.060> Bitcoin<00:05:52.450> or<00:05:52.630> in<00:05:52.750> ether<00:05:52.930> you<00:05:53.080> if<00:05:53.380> you 00:05:53.580 --> 00:05:53.590 align:start position:0% that in Bitcoin or in ether you if you 00:05:53.590 --> 00:05:55.230 align:start position:0% that in Bitcoin or in ether you if you lose<00:05:53.710> the<00:05:53.860> keys<00:05:54.039> you<00:05:54.550> lose<00:05:54.729> that<00:05:54.940> you<00:05:55.210> lose 00:05:55.230 --> 00:05:55.240 align:start position:0% lose the keys you lose that you lose 00:05:55.240 --> 00:05:58.050 align:start position:0% lose the keys you lose that you lose that<00:05:55.630> so<00:05:56.080> because<00:05:56.470> this<00:05:56.680> responsibility<00:05:57.370> we 00:05:58.050 --> 00:05:58.060 align:start position:0% that so because this responsibility we 00:05:58.060 --> 00:06:00.379 align:start position:0% that so because this responsibility we need<00:05:58.240> to<00:05:58.360> work<00:05:58.570> a<00:05:58.840> lot<00:05:59.229> in<00:05:59.500> the<00:05:59.680> key<00:05:59.860> management 00:06:00.379 --> 00:06:00.389 align:start position:0% need to work a lot in the key management 00:06:00.389 --> 00:06:03.600 align:start position:0% need to work a lot in the key management ok<00:06:01.419> and<00:06:01.599> this<00:06:01.990> here<00:06:02.560> we<00:06:02.710> share<00:06:02.979> a<00:06:03.010> lot<00:06:03.370> of<00:06:03.400> the 00:06:03.600 --> 00:06:03.610 align:start position:0% ok and this here we share a lot of the 00:06:03.610 --> 00:06:08.279 align:start position:0% ok and this here we share a lot of the problems<00:06:04.060> that<00:06:04.240> any<00:06:04.419> wallet<00:06:04.930> have<00:06:06.539> here<00:06:07.539> as 00:06:08.279 --> 00:06:08.289 align:start position:0% problems that any wallet have here as 00:06:08.289 --> 00:06:10.020 align:start position:0% problems that any wallet have here as you<00:06:08.410> can<00:06:08.590> assume<00:06:08.889> as<00:06:09.039> you<00:06:09.280> can<00:06:09.430> imagine<00:06:09.669> the 00:06:10.020 --> 00:06:10.030 align:start position:0% you can assume as you can imagine the 00:06:10.030 --> 00:06:13.710 align:start position:0% you can assume as you can imagine the key<00:06:10.240> should<00:06:10.780> be<00:06:10.840> revocable<00:06:11.410> recoverable<00:06:12.720> we 00:06:13.710 --> 00:06:13.720 align:start position:0% key should be revocable recoverable we 00:06:13.720 --> 00:06:17.430 align:start position:0% key should be revocable recoverable we are<00:06:13.840> thinking<00:06:14.349> that<00:06:15.840> we<00:06:16.840> don't<00:06:16.990> want<00:06:17.169> the<00:06:17.289> keys 00:06:17.430 --> 00:06:17.440 align:start position:0% are thinking that we don't want the keys 00:06:17.440 --> 00:06:20.040 align:start position:0% are thinking that we don't want the keys to<00:06:17.500> go<00:06:17.979> around<00:06:18.370> that<00:06:18.639> belief<00:06:19.030> among<00:06:19.300> the<00:06:19.570> that 00:06:20.040 --> 00:06:20.050 align:start position:0% to go around that belief among the that 00:06:20.050 --> 00:06:22.440 align:start position:0% to go around that belief among the that leave<00:06:20.229> the<00:06:20.349> devices<00:06:20.860> we<00:06:21.340> are<00:06:21.430> sharing<00:06:21.700> a<00:06:21.970> lot 00:06:22.440 --> 00:06:22.450 align:start position:0% leave the devices we are sharing a lot 00:06:22.450 --> 00:06:24.060 align:start position:0% leave the devices we are sharing a lot of<00:06:22.630> the<00:06:22.750> concepts<00:06:23.169> and<00:06:23.410> we<00:06:23.560> are<00:06:23.710> a<00:06:23.740> fully 00:06:24.060 --> 00:06:24.070 align:start position:0% of the concepts and we are a fully 00:06:24.070 --> 00:06:26.520 align:start position:0% of the concepts and we are a fully alignment<00:06:24.580> with<00:06:25.030> I<00:06:25.450> don't<00:06:26.020> know<00:06:26.110> if<00:06:26.229> you<00:06:26.289> saw 00:06:26.520 --> 00:06:26.530 align:start position:0% alignment with I don't know if you saw 00:06:26.530 --> 00:06:28.260 align:start position:0% alignment with I don't know if you saw yesterday<00:06:26.830> the<00:06:27.130> Alexander's<00:06:27.789> are<00:06:28.030> a 00:06:28.260 --> 00:06:28.270 align:start position:0% yesterday the Alexander's are a 00:06:28.270 --> 00:06:31.770 align:start position:0% yesterday the Alexander's are a universal<00:06:29.080> login<00:06:30.300> we<00:06:31.300> work<00:06:31.450> in<00:06:31.660> that 00:06:31.770 --> 00:06:31.780 align:start position:0% universal login we work in that 00:06:31.780 --> 00:06:34.680 align:start position:0% universal login we work in that direction<00:06:31.990> one<00:06:32.830> keeper<00:06:33.310> application<00:06:34.000> so<00:06:34.510> the 00:06:34.680 --> 00:06:34.690 align:start position:0% direction one keeper application so the 00:06:34.690 --> 00:06:36.510 align:start position:0% direction one keeper application so the key<00:06:34.900> management<00:06:35.289> is<00:06:35.530> an<00:06:35.680> important<00:06:36.159> part<00:06:36.370> of 00:06:36.510 --> 00:06:36.520 align:start position:0% key management is an important part of 00:06:36.520 --> 00:06:38.779 align:start position:0% key management is an important part of these<00:06:37.000> of<00:06:37.270> this<00:06:37.510> project 00:06:38.779 --> 00:06:38.789 align:start position:0% these of this project 00:06:38.789 --> 00:06:42.439 align:start position:0% these of this project accessibility<00:06:39.749> I<00:06:39.960> think<00:06:40.830> we<00:06:41.669> want<00:06:41.849> to<00:06:41.999> create 00:06:42.439 --> 00:06:42.449 align:start position:0% accessibility I think we want to create 00:06:42.449 --> 00:06:45.409 align:start position:0% accessibility I think we want to create a<00:06:43.069> system<00:06:44.069> that's<00:06:44.460> made<00:06:44.849> that<00:06:45.210> goes 00:06:45.409 --> 00:06:45.419 align:start position:0% a system that's made that goes 00:06:45.419 --> 00:06:47.600 align:start position:0% a system that's made that goes mainstream<00:06:45.800> that<00:06:46.800> everybody<00:06:47.219> should<00:06:47.339> be<00:06:47.490> able 00:06:47.600 --> 00:06:47.610 align:start position:0% mainstream that everybody should be able 00:06:47.610 --> 00:06:51.320 align:start position:0% mainstream that everybody should be able to<00:06:47.999> use<00:06:48.150> it<00:06:48.360> so<00:06:48.870> be<00:06:49.020> easy<00:06:49.229> to<00:06:49.559> do<00:06:50.279> so<00:06:50.879> be<00:06:51.059> easy 00:06:51.320 --> 00:06:51.330 align:start position:0% to use it so be easy to do so be easy 00:06:51.330 --> 00:06:55.040 align:start position:0% to use it so be easy to do so be easy for<00:06:52.139> anybody<00:06:52.529> to<00:06:52.800> start<00:06:53.839> working<00:06:54.839> in<00:06:54.960> the 00:06:55.040 --> 00:06:55.050 align:start position:0% for anybody to start working in the 00:06:55.050 --> 00:06:58.070 align:start position:0% for anybody to start working in the system<00:06:55.400> this<00:06:56.400> is<00:06:56.550> for<00:06:56.729> example<00:06:57.180> and<00:06:57.419> I'm<00:06:57.809> going 00:06:58.070 --> 00:06:58.080 align:start position:0% system this is for example and I'm going 00:06:58.080 --> 00:06:59.839 align:start position:0% system this is for example and I'm going and<00:06:58.319> start<00:06:58.770> into<00:06:59.009> entering<00:06:59.370> a<00:06:59.430> little<00:06:59.699> bit 00:06:59.839 --> 00:06:59.849 align:start position:0% and start into entering a little bit 00:06:59.849 --> 00:07:02.119 align:start position:0% and start into entering a little bit technical<00:07:00.089> how<00:07:00.930> we<00:07:01.080> are<00:07:01.199> doing<00:07:01.319> we<00:07:01.860> are<00:07:01.919> using 00:07:02.119 --> 00:07:02.129 align:start position:0% technical how we are doing we are using 00:07:02.129 --> 00:07:03.619 align:start position:0% technical how we are doing we are using this<00:07:02.430> when<00:07:02.699> you<00:07:02.849> are<00:07:02.879> creating<00:07:03.300> an<00:07:03.389> identity 00:07:03.619 --> 00:07:03.629 align:start position:0% this when you are creating an identity 00:07:03.629 --> 00:07:05.329 align:start position:0% this when you are creating an identity mainly<00:07:04.469> what<00:07:04.620> you<00:07:04.710> are<00:07:04.800> doing<00:07:04.979> is<00:07:05.129> creating 00:07:05.329 --> 00:07:05.339 align:start position:0% mainly what you are doing is creating 00:07:05.339 --> 00:07:10.309 align:start position:0% mainly what you are doing is creating this<00:07:06.199> contractual<00:07:07.199> or<00:07:07.379> if<00:07:07.589> this<00:07:09.319> identity 00:07:10.309 --> 00:07:10.319 align:start position:0% this contractual or if this identity 00:07:10.319 --> 00:07:12.739 align:start position:0% this contractual or if this identity contract<00:07:10.800> that<00:07:11.309> you<00:07:11.520> don't<00:07:11.759> actually<00:07:12.419> deploy 00:07:12.739 --> 00:07:12.749 align:start position:0% contract that you don't actually deploy 00:07:12.749 --> 00:07:15.219 align:start position:0% contract that you don't actually deploy when<00:07:13.020> you<00:07:13.110> are<00:07:13.229> creating<00:07:13.649> that<00:07:13.800> identity<00:07:14.189> but 00:07:15.219 --> 00:07:15.229 align:start position:0% when you are creating that identity but 00:07:15.229 --> 00:07:18.350 align:start position:0% when you are creating that identity but once<00:07:16.229> you<00:07:16.379> create<00:07:16.680> this<00:07:16.889> contract<00:07:17.610> that's<00:07:18.089> not 00:07:18.350 --> 00:07:18.360 align:start position:0% once you create this contract that's not 00:07:18.360 --> 00:07:20.659 align:start position:0% once you create this contract that's not deployed<00:07:18.719> yet<00:07:19.139> they<00:07:19.919> already<00:07:20.219> have<00:07:20.520> an 00:07:20.659 --> 00:07:20.669 align:start position:0% deployed yet they already have an 00:07:20.669 --> 00:07:21.249 align:start position:0% deployed yet they already have an address 00:07:21.249 --> 00:07:21.259 align:start position:0% address 00:07:21.259 --> 00:07:24.290 align:start position:0% address so<00:07:22.259> these<00:07:22.469> already<00:07:22.860> have<00:07:23.039> an<00:07:23.189> address<00:07:23.699> so<00:07:24.059> this 00:07:24.290 --> 00:07:24.300 align:start position:0% so these already have an address so this 00:07:24.300 --> 00:07:26.899 align:start position:0% so these already have an address so this identity<00:07:24.809> is<00:07:24.960> created<00:07:25.529> already<00:07:26.009> so<00:07:26.490> you<00:07:26.550> the 00:07:26.899 --> 00:07:26.909 align:start position:0% identity is created already so you the 00:07:26.909 --> 00:07:28.549 align:start position:0% identity is created already so you the people<00:07:27.180> can<00:07:27.330> start<00:07:27.659> doing<00:07:27.779> claims<00:07:28.169> on<00:07:28.409> that 00:07:28.549 --> 00:07:28.559 align:start position:0% people can start doing claims on that 00:07:28.559 --> 00:07:31.969 align:start position:0% people can start doing claims on that and<00:07:29.370> all<00:07:29.669> that<00:07:29.879> without<00:07:30.270> the<00:07:30.419> user<00:07:30.629> having<00:07:30.979> to 00:07:31.969 --> 00:07:31.979 align:start position:0% and all that without the user having to 00:07:31.979 --> 00:07:34.219 align:start position:0% and all that without the user having to do<00:07:32.279> anything<00:07:32.580> else<00:07:32.909> that<00:07:33.479> just<00:07:33.689> running<00:07:34.110> at 00:07:34.219 --> 00:07:34.229 align:start position:0% do anything else that just running at 00:07:34.229 --> 00:07:36.709 align:start position:0% do anything else that just running at random<00:07:34.620> dies<00:07:34.800> at<00:07:35.279> some<00:07:35.759> point<00:07:35.999> and<00:07:36.210> creating 00:07:36.709 --> 00:07:36.719 align:start position:0% random dies at some point and creating 00:07:36.719 --> 00:07:41.899 align:start position:0% random dies at some point and creating that<00:07:36.809> identity<00:07:39.800> scalability<00:07:40.800> and<00:07:41.309> here<00:07:41.789> is 00:07:41.899 --> 00:07:41.909 align:start position:0% that identity scalability and here is 00:07:41.909 --> 00:07:43.820 align:start position:0% that identity scalability and here is what<00:07:42.089> we<00:07:42.240> are<00:07:42.330> going<00:07:42.479> to<00:07:42.569> go<00:07:42.779> deep<00:07:43.020> we<00:07:43.529> want<00:07:43.740> a 00:07:43.820 --> 00:07:43.830 align:start position:0% what we are going to go deep we want a 00:07:43.830 --> 00:07:45.589 align:start position:0% what we are going to go deep we want a system<00:07:44.069> where<00:07:44.459> everybody<00:07:44.729> can<00:07:45.060> create<00:07:45.449> as 00:07:45.589 --> 00:07:45.599 align:start position:0% system where everybody can create as 00:07:45.599 --> 00:07:48.050 align:start position:0% system where everybody can create as many<00:07:45.629> identities<00:07:46.229> as<00:07:46.469> they<00:07:46.620> want<00:07:46.860> but<00:07:47.069> we<00:07:47.849> want 00:07:48.050 --> 00:07:48.060 align:start position:0% many identities as they want but we want 00:07:48.060 --> 00:07:50.719 align:start position:0% many identities as they want but we want a<00:07:48.209> system<00:07:48.419> also<00:07:48.870> that<00:07:49.589> anybody<00:07:50.009> can<00:07:50.219> create<00:07:50.430> as 00:07:50.719 --> 00:07:50.729 align:start position:0% a system also that anybody can create as 00:07:50.729 --> 00:07:54.050 align:start position:0% a system also that anybody can create as many<00:07:50.759> claims<00:07:51.300> as<00:07:51.599> they<00:07:51.930> want<00:07:52.229> and<00:07:52.789> to<00:07:53.789> scale 00:07:54.050 --> 00:07:54.060 align:start position:0% many claims as they want and to scale 00:07:54.060 --> 00:07:55.939 align:start position:0% many claims as they want and to scale that<00:07:54.270> in<00:07:54.539> a<00:07:54.659> global<00:07:55.050> basis<00:07:55.379> so<00:07:55.529> that<00:07:55.680> we<00:07:55.830> are 00:07:55.939 --> 00:07:55.949 align:start position:0% that in a global basis so that we are 00:07:55.949 --> 00:07:57.949 align:start position:0% that in a global basis so that we are there<00:07:56.219> are<00:07:56.310> millions<00:07:57.149> of<00:07:57.240> claims<00:07:57.449> in<00:07:57.779> the 00:07:57.949 --> 00:07:57.959 align:start position:0% there are millions of claims in the 00:07:57.959 --> 00:08:00.559 align:start position:0% there are millions of claims in the world<00:07:58.370> we<00:07:59.370> need<00:07:59.550> to<00:07:59.669> apply<00:07:59.909> some<00:07:59.939> techniques 00:08:00.559 --> 00:08:00.569 align:start position:0% world we need to apply some techniques 00:08:00.569 --> 00:08:03.619 align:start position:0% world we need to apply some techniques that<00:08:00.959> I'm<00:08:01.080> going<00:08:01.289> to<00:08:01.379> describe<00:08:01.680> next<00:08:02.629> to 00:08:03.619 --> 00:08:03.629 align:start position:0% that I'm going to describe next to 00:08:03.629 --> 00:08:09.559 align:start position:0% that I'm going to describe next to explain<00:08:03.959> that<00:08:04.909> how<00:08:05.909> we<00:08:08.089> anchored<00:08:09.089> the<00:08:09.270> claims 00:08:09.559 --> 00:08:09.569 align:start position:0% explain that how we anchored the claims 00:08:09.569 --> 00:08:14.179 align:start position:0% explain that how we anchored the claims in<00:08:09.959> the<00:08:10.319> blockchain<00:08:12.709> what<00:08:13.709> we<00:08:13.889> are<00:08:14.009> doing 00:08:14.179 --> 00:08:14.189 align:start position:0% in the blockchain what we are doing 00:08:14.189 --> 00:08:18.439 align:start position:0% in the blockchain what we are doing mainly<00:08:14.459> is<00:08:15.709> if<00:08:16.709> I<00:08:16.949> want<00:08:17.219> to<00:08:17.339> create<00:08:17.580> many 00:08:18.439 --> 00:08:18.449 align:start position:0% mainly is if I want to create many 00:08:18.449 --> 00:08:21.139 align:start position:0% mainly is if I want to create many claims<00:08:18.809> I<00:08:19.199> put<00:08:20.129> all<00:08:20.279> those<00:08:20.490> claims<00:08:20.789> in<00:08:21.059> a 00:08:21.139 --> 00:08:21.149 align:start position:0% claims I put all those claims in a 00:08:21.149 --> 00:08:23.570 align:start position:0% claims I put all those claims in a database<00:08:21.419> I<00:08:21.839> take<00:08:22.709> this<00:08:22.830> database<00:08:23.129> I 00:08:23.570 --> 00:08:23.580 align:start position:0% database I take this database I 00:08:23.580 --> 00:08:25.579 align:start position:0% database I take this database I construct<00:08:24.209> a<00:08:24.330> miracle<00:08:24.689> tree<00:08:24.930> of<00:08:25.139> that 00:08:25.579 --> 00:08:25.589 align:start position:0% construct a miracle tree of that 00:08:25.589 --> 00:08:28.040 align:start position:0% construct a miracle tree of that database<00:08:25.889> and<00:08:26.339> I<00:08:26.879> just<00:08:27.209> publish<00:08:27.659> with<00:08:28.020> a 00:08:28.040 --> 00:08:28.050 align:start position:0% database and I just publish with a 00:08:28.050 --> 00:08:31.399 align:start position:0% database and I just publish with a transaction<00:08:28.770> the<00:08:29.459> root<00:08:29.669> of<00:08:29.939> that<00:08:30.599> of<00:08:31.169> that 00:08:31.399 --> 00:08:31.409 align:start position:0% transaction the root of that of that 00:08:31.409 --> 00:08:36.050 align:start position:0% transaction the root of that of that miracle<00:08:32.099> tree<00:08:32.459> in<00:08:32.639> the<00:08:33.469> chain<00:08:34.819> every<00:08:35.819> time 00:08:36.050 --> 00:08:36.060 align:start position:0% miracle tree in the chain every time 00:08:36.060 --> 00:08:39.469 align:start position:0% miracle tree in the chain every time that<00:08:36.510> I<00:08:36.750> have<00:08:36.839> new<00:08:37.560> claims<00:08:37.979> I<00:08:38.339> have<00:08:38.789> changes<00:08:39.300> I 00:08:39.469 --> 00:08:39.479 align:start position:0% that I have new claims I have changes I 00:08:39.479 --> 00:08:42.170 align:start position:0% that I have new claims I have changes I could<00:08:40.110> change<00:08:40.829> the<00:08:41.099> route<00:08:41.310> or<00:08:41.519> I<00:08:41.579> will<00:08:41.940> change 00:08:42.170 --> 00:08:42.180 align:start position:0% could change the route or I will change 00:08:42.180 --> 00:08:45.650 align:start position:0% could change the route or I will change the<00:08:42.389> route<00:08:42.569> of<00:08:42.719> the<00:08:43.110> database<00:08:43.500> as<00:08:44.389> one<00:08:45.389> chain 00:08:45.650 --> 00:08:45.660 align:start position:0% the route of the database as one chain 00:08:45.660 --> 00:08:48.380 align:start position:0% the route of the database as one chain as<00:08:45.839> you<00:08:46.170> can<00:08:46.319> see<00:08:46.560> this<00:08:46.980> is<00:08:47.160> scales<00:08:47.640> very<00:08:47.910> well 00:08:48.380 --> 00:08:48.390 align:start position:0% as you can see this is scales very well 00:08:48.390 --> 00:08:52.060 align:start position:0% as you can see this is scales very well for<00:08:50.269> identities<00:08:51.269> that<00:08:51.720> may 00:08:52.060 --> 00:08:52.070 align:start position:0% for identities that may 00:08:52.070 --> 00:08:56.290 align:start position:0% for identities that may a<00:08:52.100> lot<00:08:52.460> of<00:08:52.640> claims<00:08:53.410> example<00:08:54.410> a<00:08:54.620> government<00:08:55.610> in 00:08:56.290 --> 00:08:56.300 align:start position:0% a lot of claims example a government in 00:08:56.300 --> 00:08:59.770 align:start position:0% a lot of claims example a government in the<00:08:56.420> government<00:08:56.900> there<00:08:57.350> are<00:08:57.530> many<00:08:58.780> things 00:08:59.770 --> 00:08:59.780 align:start position:0% the government there are many things 00:08:59.780 --> 00:09:01.900 align:start position:0% the government there are many things that<00:09:00.080> happen<00:09:00.650> in<00:09:00.770> a<00:09:00.860> country<00:09:01.250> there<00:09:01.490> is<00:09:01.550> people 00:09:01.900 --> 00:09:01.910 align:start position:0% that happen in a country there is people 00:09:01.910 --> 00:09:04.300 align:start position:0% that happen in a country there is people does<00:09:02.060> get<00:09:02.300> born<00:09:02.600> people<00:09:03.260> that<00:09:03.380> die<00:09:03.560> people 00:09:04.300 --> 00:09:04.310 align:start position:0% does get born people that die people 00:09:04.310 --> 00:09:06.460 align:start position:0% does get born people that die people that<00:09:04.460> get<00:09:04.670> married<00:09:05.000> people<00:09:05.570> that<00:09:05.720> change 00:09:06.460 --> 00:09:06.470 align:start position:0% that get married people that change 00:09:06.470 --> 00:09:09.010 align:start position:0% that get married people that change their<00:09:06.650> addresses<00:09:07.040> so<00:09:07.790> the<00:09:07.970> government<00:09:08.420> just 00:09:09.010 --> 00:09:09.020 align:start position:0% their addresses so the government just 00:09:09.020 --> 00:09:12.460 align:start position:0% their addresses so the government just with<00:09:09.230> a<00:09:09.260> single<00:09:09.640> transaction<00:09:10.640> per<00:09:11.270> day<00:09:11.470> could 00:09:12.460 --> 00:09:12.470 align:start position:0% with a single transaction per day could 00:09:12.470 --> 00:09:17.350 align:start position:0% with a single transaction per day could abate<00:09:13.040> the<00:09:13.910> full<00:09:14.150> database<00:09:15.880> if<00:09:16.880> you<00:09:17.120> want 00:09:17.350 --> 00:09:17.360 align:start position:0% abate the full database if you want 00:09:17.360 --> 00:09:19.840 align:start position:0% abate the full database if you want instead<00:09:18.140> of<00:09:18.320> one<00:09:18.500> per<00:09:18.650> day<00:09:18.680> one<00:09:19.160> per<00:09:19.340> hour<00:09:19.490> or 00:09:19.840 --> 00:09:19.850 align:start position:0% instead of one per day one per hour or 00:09:19.850 --> 00:09:20.980 align:start position:0% instead of one per day one per hour or one<00:09:20.000> every<00:09:20.270> five<00:09:20.510> minutes 00:09:20.980 --> 00:09:20.990 align:start position:0% one every five minutes 00:09:20.990 --> 00:09:22.990 align:start position:0% one every five minutes but<00:09:21.530> this<00:09:21.770> is<00:09:21.920> quite<00:09:22.220> cheap<00:09:22.580> for<00:09:22.880> the 00:09:22.990 --> 00:09:23.000 align:start position:0% but this is quite cheap for the 00:09:23.000 --> 00:09:25.840 align:start position:0% but this is quite cheap for the government<00:09:23.450> just<00:09:23.870> to<00:09:23.990> keep<00:09:24.440> a<00:09:24.740> millions<00:09:25.580> of 00:09:25.840 --> 00:09:25.850 align:start position:0% government just to keep a millions of 00:09:25.850 --> 00:09:29.260 align:start position:0% government just to keep a millions of claims<00:09:26.210> database<00:09:27.130> okay<00:09:28.130> but<00:09:28.610> what<00:09:28.790> happens 00:09:29.260 --> 00:09:29.270 align:start position:0% claims database okay but what happens 00:09:29.270 --> 00:09:32.560 align:start position:0% claims database okay but what happens when<00:09:29.990> an<00:09:30.290> individual<00:09:31.130> user<00:09:31.370> a<00:09:31.760> normal<00:09:32.330> user 00:09:32.560 --> 00:09:32.570 align:start position:0% when an individual user a normal user 00:09:32.570 --> 00:09:35.530 align:start position:0% when an individual user a normal user just<00:09:33.230> wants<00:09:33.470> to<00:09:33.620> do<00:09:33.740> one<00:09:34.550> two<00:09:34.850> three<00:09:35.180> ten 00:09:35.530 --> 00:09:35.540 align:start position:0% just wants to do one two three ten 00:09:35.540 --> 00:09:39.390 align:start position:0% just wants to do one two three ten transactions<00:09:36.230> per<00:09:36.410> day<00:09:36.590> should<00:09:37.030> they<00:09:38.030> do<00:09:38.230> pen 00:09:39.390 --> 00:09:39.400 align:start position:0% transactions per day should they do pen 00:09:39.400 --> 00:09:41.650 align:start position:0% transactions per day should they do pen transactions<00:09:40.400> should<00:09:40.460> they<00:09:40.820> do<00:09:40.880> ten 00:09:41.650 --> 00:09:41.660 align:start position:0% transactions should they do ten 00:09:41.660 --> 00:09:43.660 align:start position:0% transactions should they do ten transactions<00:09:42.320> if<00:09:42.680> they<00:09:43.160> want<00:09:43.370> to<00:09:43.430> make<00:09:43.640> just 00:09:43.660 --> 00:09:43.670 align:start position:0% transactions if they want to make just 00:09:43.670 --> 00:09:47.260 align:start position:0% transactions if they want to make just ten<00:09:44.180> claims<00:09:44.450> and<00:09:45.380> here<00:09:45.830> is<00:09:45.950> when<00:09:46.700> we<00:09:46.730> introduce 00:09:47.260 --> 00:09:47.270 align:start position:0% ten claims and here is when we introduce 00:09:47.270 --> 00:09:48.520 align:start position:0% ten claims and here is when we introduce the<00:09:47.480> indirect<00:09:48.050> claims 00:09:48.520 --> 00:09:48.530 align:start position:0% the indirect claims 00:09:48.530 --> 00:09:51.040 align:start position:0% the indirect claims what's<00:09:49.250> the<00:09:49.430> indirect<00:09:49.790> claims<00:09:50.030> here<00:09:50.870> we 00:09:51.040 --> 00:09:51.050 align:start position:0% what's the indirect claims here we 00:09:51.050 --> 00:09:55.750 align:start position:0% what's the indirect claims here we introduce<00:09:51.170> a<00:09:51.710> relay<00:09:52.600> so<00:09:53.600> when<00:09:54.170> a<00:09:54.500> user<00:09:54.890> wants 00:09:55.750 --> 00:09:55.760 align:start position:0% introduce a relay so when a user wants 00:09:55.760 --> 00:09:58.660 align:start position:0% introduce a relay so when a user wants to<00:09:55.820> create<00:09:56.150> a<00:09:56.480> claim<00:09:56.870> let<00:09:57.770> me<00:09:57.890> for<00:09:58.220> example 00:09:58.660 --> 00:09:58.670 align:start position:0% to create a claim let me for example 00:09:58.670 --> 00:10:01.990 align:start position:0% to create a claim let me for example saying<00:09:58.910> okay<00:09:59.690> I<00:10:00.140> like<00:10:00.890> this<00:10:01.040> picture<00:10:01.310> okay 00:10:01.990 --> 00:10:02.000 align:start position:0% saying okay I like this picture okay 00:10:02.000 --> 00:10:03.760 align:start position:0% saying okay I like this picture okay this<00:10:02.210> is<00:10:02.330> a<00:10:02.360> claim<00:10:02.630> that<00:10:02.720> I<00:10:02.840> want<00:10:03.020> to<00:10:03.110> do<00:10:03.200> but 00:10:03.760 --> 00:10:03.770 align:start position:0% this is a claim that I want to do but 00:10:03.770 --> 00:10:06.190 align:start position:0% this is a claim that I want to do but instead<00:10:04.190> of<00:10:04.400> creating<00:10:04.760> a<00:10:05.200> transaction 00:10:06.190 --> 00:10:06.200 align:start position:0% instead of creating a transaction 00:10:06.200 --> 00:10:09.070 align:start position:0% instead of creating a transaction abating<00:10:06.980> my<00:10:07.130> route<00:10:07.430> of<00:10:07.640> claims<00:10:07.970> what<00:10:08.930> times 00:10:09.070 --> 00:10:09.080 align:start position:0% abating my route of claims what times 00:10:09.080 --> 00:10:11.320 align:start position:0% abating my route of claims what times what<00:10:09.590> I<00:10:09.650> do<00:10:09.770> is<00:10:10.100> I'm<00:10:10.280> telling<00:10:10.670> to<00:10:10.700> our<00:10:10.970> layer 00:10:11.320 --> 00:10:11.330 align:start position:0% what I do is I'm telling to our layer 00:10:11.330 --> 00:10:14.230 align:start position:0% what I do is I'm telling to our layer let's<00:10:12.080> think<00:10:12.350> for<00:10:12.620> a<00:10:13.520> moment<00:10:13.580> that<00:10:13.880> this<00:10:14.060> is<00:10:14.120> a 00:10:14.230 --> 00:10:14.240 align:start position:0% let's think for a moment that this is a 00:10:14.240 --> 00:10:15.280 align:start position:0% let's think for a moment that this is a trusted<00:10:14.660> relay 00:10:15.280 --> 00:10:15.290 align:start position:0% trusted relay 00:10:15.290 --> 00:10:16.720 align:start position:0% trusted relay we<00:10:15.800> will<00:10:15.890> see<00:10:16.100> that<00:10:16.250> that<00:10:16.430> that's<00:10:16.550> not 00:10:16.720 --> 00:10:16.730 align:start position:0% we will see that that that's not 00:10:16.730 --> 00:10:18.910 align:start position:0% we will see that that that's not necessary<00:10:17.360> necessarily<00:10:17.960> but<00:10:18.560> if<00:10:18.710> it's<00:10:18.860> a 00:10:18.910 --> 00:10:18.920 align:start position:0% necessary necessarily but if it's a 00:10:18.920 --> 00:10:20.470 align:start position:0% necessary necessarily but if it's a trusted<00:10:19.250> layer<00:10:19.490> and<00:10:19.760> telling<00:10:20.030> to<00:10:20.150> the<00:10:20.240> relay 00:10:20.470 --> 00:10:20.480 align:start position:0% trusted layer and telling to the relay 00:10:20.480 --> 00:10:24.340 align:start position:0% trusted layer and telling to the relay er<00:10:20.510> a<00:10:20.830> relay<00:10:21.830> er<00:10:21.860> I<00:10:22.250> want<00:10:23.210> to<00:10:23.360> say<00:10:23.570> I<00:10:23.840> want<00:10:24.170> to 00:10:24.340 --> 00:10:24.350 align:start position:0% er a relay er I want to say I want to 00:10:24.350 --> 00:10:27.640 align:start position:0% er a relay er I want to say I want to claim<00:10:24.590> that<00:10:25.490> I<00:10:25.790> like<00:10:26.270> this<00:10:26.480> picture<00:10:26.690> so<00:10:27.470> the 00:10:27.640 --> 00:10:27.650 align:start position:0% claim that I like this picture so the 00:10:27.650 --> 00:10:31.330 align:start position:0% claim that I like this picture so the relay<00:10:28.270> what<00:10:29.270> could<00:10:29.480> say<00:10:29.720> you<00:10:30.200> say<00:10:30.470> Oh<00:10:30.740> Jordi 00:10:31.330 --> 00:10:31.340 align:start position:0% relay what could say you say Oh Jordi 00:10:31.340 --> 00:10:34.560 align:start position:0% relay what could say you say Oh Jordi makes<00:10:32.240> a<00:10:32.420> claim<00:10:32.660> that<00:10:32.960> says<00:10:33.170> Jordi<00:10:33.740> is<00:10:33.770> saying 00:10:34.560 --> 00:10:34.570 align:start position:0% makes a claim that says Jordi is saying 00:10:34.570 --> 00:10:38.020 align:start position:0% makes a claim that says Jordi is saying that<00:10:35.570> he<00:10:36.170> likes<00:10:36.410> that<00:10:36.710> picture<00:10:37.190> okay<00:10:37.820> this 00:10:38.020 --> 00:10:38.030 align:start position:0% that he likes that picture okay this 00:10:38.030 --> 00:10:40.210 align:start position:0% that he likes that picture okay this would<00:10:38.180> be<00:10:38.300> an<00:10:38.420> indirect<00:10:38.780> claim<00:10:38.990> but<00:10:39.830> instead 00:10:40.210 --> 00:10:40.220 align:start position:0% would be an indirect claim but instead 00:10:40.220 --> 00:10:43.150 align:start position:0% would be an indirect claim but instead of<00:10:40.400> doing<00:10:40.670> claim<00:10:40.970> by<00:10:41.150> claim<00:10:41.770> what<00:10:42.770> I'm<00:10:42.920> really 00:10:43.150 --> 00:10:43.160 align:start position:0% of doing claim by claim what I'm really 00:10:43.160 --> 00:10:45.880 align:start position:0% of doing claim by claim what I'm really asking<00:10:43.550> to<00:10:44.030> the<00:10:44.150> relay<00:10:44.390> is<00:10:44.870> just<00:10:45.290> to<00:10:45.410> update<00:10:45.680> my 00:10:45.880 --> 00:10:45.890 align:start position:0% asking to the relay is just to update my 00:10:45.890 --> 00:10:48.190 align:start position:0% asking to the relay is just to update my wrote<00:10:46.130> my<00:10:46.310> route<00:10:46.580> of<00:10:46.820> claims<00:10:47.210> a<00:10:47.510> relay<00:10:48.170> er 00:10:48.190 --> 00:10:48.200 align:start position:0% wrote my route of claims a relay er 00:10:48.200 --> 00:10:51.310 align:start position:0% wrote my route of claims a relay er please<00:10:48.910> update<00:10:49.910> my<00:10:50.090> fruit<00:10:50.300> of<00:10:50.450> claims<00:10:50.690> so<00:10:51.200> the 00:10:51.310 --> 00:10:51.320 align:start position:0% please update my fruit of claims so the 00:10:51.320 --> 00:10:53.530 align:start position:0% please update my fruit of claims so the relay<00:10:51.560> er<00:10:51.590> just<00:10:52.280> take<00:10:52.520> that<00:10:52.730> route<00:10:53.120> of<00:10:53.270> claims 00:10:53.530 --> 00:10:53.540 align:start position:0% relay er just take that route of claims 00:10:53.540 --> 00:10:56.620 align:start position:0% relay er just take that route of claims and<00:10:53.750> publish<00:10:54.440> as<00:10:54.740> a<00:10:54.980> claim<00:10:55.370> inside<00:10:56.240> that<00:10:56.420> and 00:10:56.620 --> 00:10:56.630 align:start position:0% and publish as a claim inside that and 00:10:56.630 --> 00:10:59.680 align:start position:0% and publish as a claim inside that and you<00:10:56.690> see<00:10:56.870> this<00:10:57.310> miracle<00:10:58.310> tree<00:10:58.700> that<00:10:59.210> depends 00:10:59.680 --> 00:10:59.690 align:start position:0% you see this miracle tree that depends 00:10:59.690 --> 00:11:01.480 align:start position:0% you see this miracle tree that depends on<00:10:59.780> the<00:10:59.900> other<00:11:00.050> on<00:11:00.410> the<00:11:00.860> other<00:11:00.980> America<00:11:01.310> tree 00:11:01.480 --> 00:11:01.490 align:start position:0% on the other on the other America tree 00:11:01.490 --> 00:11:05.079 align:start position:0% on the other on the other America tree okay<00:11:02.090> but<00:11:02.510> this<00:11:02.690> system<00:11:02.870> as<00:11:03.290> you<00:11:03.620> can<00:11:03.650> imagine 00:11:05.079 --> 00:11:05.089 align:start position:0% okay but this system as you can imagine 00:11:05.089 --> 00:11:08.350 align:start position:0% okay but this system as you can imagine quite<00:11:05.269> a<00:11:05.600> truce<00:11:05.959> nests<00:11:06.170> between<00:11:06.829> the<00:11:07.399> between 00:11:08.350 --> 00:11:08.360 align:start position:0% quite a truce nests between the between 00:11:08.360 --> 00:11:12.730 align:start position:0% quite a truce nests between the between the<00:11:08.569> user<00:11:09.019> and<00:11:09.199> the<00:11:09.410> relator<00:11:10.329> so<00:11:11.350> in<00:11:12.350> order<00:11:12.559> to 00:11:12.730 --> 00:11:12.740 align:start position:0% the user and the relator so in order to 00:11:12.740 --> 00:11:15.160 align:start position:0% the user and the relator so in order to solve<00:11:13.069> to<00:11:13.459> solve<00:11:13.670> that<00:11:13.970> what<00:11:14.629> we<00:11:14.839> are<00:11:14.930> working 00:11:15.160 --> 00:11:15.170 align:start position:0% solve to solve that what we are working 00:11:15.170 --> 00:11:16.889 align:start position:0% solve to solve that what we are working is<00:11:15.499> in<00:11:15.680> the<00:11:15.769> truth<00:11:16.009> less<00:11:16.220> relayer 00:11:16.889 --> 00:11:16.899 align:start position:0% is in the truth less relayer 00:11:16.899 --> 00:11:20.079 align:start position:0% is in the truth less relayer so<00:11:17.899> what's<00:11:18.230> a<00:11:18.379> trusted<00:11:18.769> relay<00:11:19.069> a<00:11:19.430> truce<00:11:19.910> less 00:11:20.079 --> 00:11:20.089 align:start position:0% so what's a trusted relay a truce less 00:11:20.089 --> 00:11:22.299 align:start position:0% so what's a trusted relay a truce less relay<00:11:20.480> here<00:11:20.540> is<00:11:21.110> several<00:11:21.620> layer<00:11:21.740> that<00:11:22.069> can 00:11:22.299 --> 00:11:22.309 align:start position:0% relay here is several layer that can 00:11:22.309 --> 00:11:26.199 align:start position:0% relay here is several layer that can match<00:11:22.550> it<00:11:22.759> so<00:11:23.720> layer<00:11:24.050> that<00:11:24.709> I<00:11:24.889> can<00:11:25.129> tell<00:11:25.970> to<00:11:26.120> the 00:11:26.199 --> 00:11:26.209 align:start position:0% match it so layer that I can tell to the 00:11:26.209 --> 00:11:30.509 align:start position:0% match it so layer that I can tell to the river<00:11:26.360> layer<00:11:26.509> and<00:11:26.839> the<00:11:27.350> layer<00:11:28.809> cannot<00:11:29.809> publish 00:11:30.509 --> 00:11:30.519 align:start position:0% river layer and the layer cannot publish 00:11:30.519 --> 00:11:35.710 align:start position:0% river layer and the layer cannot publish anything<00:11:31.519> in<00:11:32.209> the<00:11:32.809> unchain<00:11:34.300> to<00:11:35.300> ensure<00:11:35.689> that 00:11:35.710 --> 00:11:35.720 align:start position:0% anything in the unchain to ensure that 00:11:35.720 --> 00:11:38.489 align:start position:0% anything in the unchain to ensure that the<00:11:36.379> relay<00:11:36.649> when<00:11:37.279> the<00:11:37.399> relay<00:11:37.610> is<00:11:37.639> publishing 00:11:38.489 --> 00:11:38.499 align:start position:0% the relay when the relay is publishing 00:11:38.499 --> 00:11:40.900 align:start position:0% the relay when the relay is publishing when<00:11:39.499> the<00:11:39.589> relay<00:11:39.829> is<00:11:39.860> publishing<00:11:40.370> that<00:11:40.699> on 00:11:40.900 --> 00:11:40.910 align:start position:0% when the relay is publishing that on 00:11:40.910 --> 00:11:45.400 align:start position:0% when the relay is publishing that on chain<00:11:41.379> it's<00:11:42.379> also<00:11:43.509> besides<00:11:44.509> that<00:11:44.809> besides<00:11:45.019> the 00:11:45.400 --> 00:11:45.410 align:start position:0% chain it's also besides that besides the 00:11:45.410 --> 00:11:48.449 align:start position:0% chain it's also besides that besides the route<00:11:45.589> it<00:11:45.980> also<00:11:46.309> adds<00:11:46.699> zero<00:11:47.480> knowledge<00:11:47.689> proof 00:11:48.449 --> 00:11:48.459 align:start position:0% route it also adds zero knowledge proof 00:11:48.459 --> 00:11:52.030 align:start position:0% route it also adds zero knowledge proof that<00:11:49.459> warranties<00:11:50.059> that<00:11:50.449> disclaim<00:11:51.379> or<00:11:51.620> if<00:11:51.920> you 00:11:52.030 --> 00:11:52.040 align:start position:0% that warranties that disclaim or if you 00:11:52.040 --> 00:11:53.889 align:start position:0% that warranties that disclaim or if you want<00:11:52.220> all<00:11:52.339> the<00:11:52.519> claims<00:11:52.759> that<00:11:52.939> are<00:11:53.059> updated<00:11:53.720> in 00:11:53.889 --> 00:11:53.899 align:start position:0% want all the claims that are updated in 00:11:53.899 --> 00:11:58.210 align:start position:0% want all the claims that are updated in this<00:11:54.379> change<00:11:54.879> follows<00:11:55.879> a<00:11:56.089> specific<00:11:56.300> rules<00:11:57.220> so 00:11:58.210 --> 00:11:58.220 align:start position:0% this change follows a specific rules so 00:11:58.220 --> 00:12:01.030 align:start position:0% this change follows a specific rules so in<00:11:58.370> this<00:11:58.519> way<00:11:58.759> the<00:11:59.660> user<00:11:59.870> have<00:12:00.319> the<00:12:00.529> warranty 00:12:01.030 --> 00:12:01.040 align:start position:0% in this way the user have the warranty 00:12:01.040 --> 00:12:04.420 align:start position:0% in this way the user have the warranty that<00:12:01.699> the<00:12:01.850> relay<00:12:02.120> err<00:12:02.149> will<00:12:02.930> not<00:12:03.499> what<00:12:04.279> we 00:12:04.420 --> 00:12:04.430 align:start position:0% that the relay err will not what we 00:12:04.430 --> 00:12:05.769 align:start position:0% that the relay err will not what we means<00:12:04.610> with<00:12:04.819> that<00:12:04.970> of<00:12:05.120> course<00:12:05.389> the<00:12:05.480> relator 00:12:05.769 --> 00:12:05.779 align:start position:0% means with that of course the relator 00:12:05.779 --> 00:12:09.460 align:start position:0% means with that of course the relator can<00:12:06.019> stop<00:12:06.290> working<00:12:07.120> maybe<00:12:08.120> we<00:12:08.300> have<00:12:08.569> maybe<00:12:09.170> or 00:12:09.460 --> 00:12:09.470 align:start position:0% can stop working maybe we have maybe or 00:12:09.470 --> 00:12:11.530 align:start position:0% can stop working maybe we have maybe or maybe<00:12:09.769> you<00:12:10.550> don't<00:12:10.730> get<00:12:10.819> any<00:12:11.089> proof<00:12:11.300> from<00:12:11.449> the 00:12:11.530 --> 00:12:11.540 align:start position:0% maybe you don't get any proof from the 00:12:11.540 --> 00:12:13.530 align:start position:0% maybe you don't get any proof from the earlier<00:12:11.870> of<00:12:12.170> course<00:12:12.620> the<00:12:12.709> users<00:12:13.009> also<00:12:13.220> can 00:12:13.530 --> 00:12:13.540 align:start position:0% earlier of course the users also can 00:12:13.540 --> 00:12:16.600 align:start position:0% earlier of course the users also can always<00:12:14.540> can<00:12:14.809> change<00:12:15.319> offer<00:12:16.009> a<00:12:16.189> layer<00:12:16.339> and 00:12:16.600 --> 00:12:16.610 align:start position:0% always can change offer a layer and 00:12:16.610 --> 00:12:18.730 align:start position:0% always can change offer a layer and maybe<00:12:16.759> change<00:12:17.089> another<00:12:17.360> to<00:12:17.600> server<00:12:17.870> layer<00:12:18.019> but 00:12:18.730 --> 00:12:18.740 align:start position:0% maybe change another to server layer but 00:12:18.740 --> 00:12:21.220 align:start position:0% maybe change another to server layer but if<00:12:18.889> you<00:12:19.009> get<00:12:19.249> a<00:12:19.279> proof<00:12:19.670> from<00:12:20.420> the<00:12:20.509> layer<00:12:20.870> you 00:12:21.220 --> 00:12:21.230 align:start position:0% if you get a proof from the layer you 00:12:21.230 --> 00:12:26.470 align:start position:0% if you get a proof from the layer you know<00:12:21.800> that<00:12:22.339> this<00:12:22.550> proof<00:12:22.819> is<00:12:23.089> valid<00:12:25.480> valid 00:12:26.470 --> 00:12:26.480 align:start position:0% know that this proof is valid valid 00:12:26.480 --> 00:12:28.840 align:start position:0% know that this proof is valid valid means<00:12:26.839> that<00:12:27.199> if<00:12:27.470> this<00:12:27.920> proof<00:12:28.220> says<00:12:28.490> that<00:12:28.730> you 00:12:28.840 --> 00:12:28.850 align:start position:0% means that if this proof says that you 00:12:28.850 --> 00:12:31.720 align:start position:0% means that if this proof says that you claim<00:12:29.120> it<00:12:29.269> something<00:12:30.040> you<00:12:31.040> can<00:12:31.309> be<00:12:31.429> sure<00:12:31.699> that 00:12:31.720 --> 00:12:31.730 align:start position:0% claim it something you can be sure that 00:12:31.730 --> 00:12:34.900 align:start position:0% claim it something you can be sure that this<00:12:32.209> user<00:12:32.629> claim<00:12:33.319> it<00:12:33.499> something<00:12:33.889> or<00:12:34.370> the 00:12:34.900 --> 00:12:34.910 align:start position:0% this user claim it something or the 00:12:34.910 --> 00:12:37.269 align:start position:0% this user claim it something or the other<00:12:34.939> way<00:12:35.209> around<00:12:35.360> if<00:12:35.809> the<00:12:36.199> proof<00:12:36.439> says<00:12:36.679> said 00:12:37.269 --> 00:12:37.279 align:start position:0% other way around if the proof says said 00:12:37.279 --> 00:12:40.480 align:start position:0% other way around if the proof says said that<00:12:37.490> you<00:12:37.639> didn't<00:12:37.910> claim<00:12:38.179> something<00:12:39.189> then<00:12:40.189> you 00:12:40.480 --> 00:12:40.490 align:start position:0% that you didn't claim something then you 00:12:40.490 --> 00:12:42.689 align:start position:0% that you didn't claim something then you can<00:12:40.519> be<00:12:40.850> sure<00:12:41.029> that<00:12:41.360> the<00:12:41.689> user<00:12:41.870> didn't<00:12:42.379> claim 00:12:42.689 --> 00:12:42.699 align:start position:0% can be sure that the user didn't claim 00:12:42.699 --> 00:12:46.419 align:start position:0% can be sure that the user didn't claim didn't<00:12:43.699> claim<00:12:43.879> that<00:12:44.259> okay<00:12:45.259> so<00:12:45.709> and<00:12:46.069> as<00:12:46.249> I<00:12:46.370> told 00:12:46.419 --> 00:12:46.429 align:start position:0% didn't claim that okay so and as I told 00:12:46.429 --> 00:12:48.610 align:start position:0% didn't claim that okay so and as I told you<00:12:46.699> to<00:12:46.879> use<00:12:46.999> that<00:12:47.059> to<00:12:47.569> work<00:12:47.809> with<00:12:48.050> that<00:12:48.199> we 00:12:48.610 --> 00:12:48.620 align:start position:0% you to use that to work with that we 00:12:48.620 --> 00:12:49.989 align:start position:0% you to use that to work with that we need<00:12:48.800> to<00:12:48.920> create<00:12:49.129> this<00:12:49.370> zero<00:12:49.639> knowledge<00:12:49.819> proof 00:12:49.989 --> 00:12:49.999 align:start position:0% need to create this zero knowledge proof 00:12:49.999 --> 00:12:52.090 align:start position:0% need to create this zero knowledge proof as<00:12:50.449> you<00:12:50.629> can<00:12:50.809> imagine<00:12:50.959> if<00:12:51.410> you<00:12:51.499> want<00:12:51.709> to<00:12:51.800> if<00:12:51.949> you 00:12:52.090 --> 00:12:52.100 align:start position:0% as you can imagine if you want to if you 00:12:52.100 --> 00:12:53.710 align:start position:0% as you can imagine if you want to if you want<00:12:52.249> to<00:12:52.399> scale<00:12:52.670> that<00:12:52.850> we<00:12:53.420> need<00:12:53.540> to<00:12:53.629> create 00:12:53.710 --> 00:12:53.720 align:start position:0% want to scale that we need to create 00:12:53.720 --> 00:12:57.549 align:start position:0% want to scale that we need to create this<00:12:53.929> big<00:12:54.699> constraint<00:12:55.699> circuit<00:12:56.509> to<00:12:56.689> create<00:12:57.290> as 00:12:57.549 --> 00:12:57.559 align:start position:0% this big constraint circuit to create as 00:12:57.559 --> 00:13:01.299 align:start position:0% this big constraint circuit to create as many<00:12:58.240> claims<00:12:59.240> per<00:12:59.870> transactions<00:13:00.499> and<00:13:00.709> this<00:13:01.189> is 00:13:01.299 --> 00:13:01.309 align:start position:0% many claims per transactions and this is 00:13:01.309 --> 00:13:03.009 align:start position:0% many claims per transactions and this is where<00:13:01.519> we<00:13:01.730> are<00:13:01.759> working<00:13:02.029> later<00:13:02.449> will<00:13:02.720> explain 00:13:03.009 --> 00:13:03.019 align:start position:0% where we are working later will explain 00:13:03.019 --> 00:13:05.110 align:start position:0% where we are working later will explain little<00:13:03.470> bit<00:13:03.649> the<00:13:03.920> update<00:13:04.220> on<00:13:04.399> the<00:13:04.730> zero 00:13:05.110 --> 00:13:05.120 align:start position:0% little bit the update on the zero 00:13:05.120 --> 00:13:09.850 align:start position:0% little bit the update on the zero knowledge<00:13:05.300> proof<00:13:05.449> state<00:13:08.470> let's<00:13:09.470> go<00:13:09.620> to<00:13:09.679> the 00:13:09.850 --> 00:13:09.860 align:start position:0% knowledge proof state let's go to the 00:13:09.860 --> 00:13:12.069 align:start position:0% knowledge proof state let's go to the privacy<00:13:10.399> part<00:13:10.639> because<00:13:11.240> here<00:13:11.480> we<00:13:11.809> are<00:13:11.899> also 00:13:12.069 --> 00:13:12.079 align:start position:0% privacy part because here we are also 00:13:12.079 --> 00:13:13.929 align:start position:0% privacy part because here we are also using<00:13:12.230> zero<00:13:12.649> knowledge<00:13:12.800> proof<00:13:12.920> but<00:13:13.670> this<00:13:13.819> is 00:13:13.929 --> 00:13:13.939 align:start position:0% using zero knowledge proof but this is 00:13:13.939 --> 00:13:16.150 align:start position:0% using zero knowledge proof but this is just<00:13:14.209> to<00:13:14.389> to<00:13:14.990> prove<00:13:15.230> things<00:13:15.559> without 00:13:16.150 --> 00:13:16.160 align:start position:0% just to to prove things without 00:13:16.160 --> 00:13:18.840 align:start position:0% just to to prove things without revealing<00:13:16.429> the<00:13:16.670> full<00:13:16.970> identity<00:13:17.529> in 00:13:18.840 --> 00:13:18.850 align:start position:0% revealing the full identity in 00:13:18.850 --> 00:13:21.329 align:start position:0% revealing the full identity in for<00:13:19.300> example<00:13:19.720> that<00:13:19.810> I<00:13:19.870> want<00:13:20.199> to<00:13:20.410> enter<00:13:21.160> to<00:13:21.190> a 00:13:21.329 --> 00:13:21.339 align:start position:0% for example that I want to enter to a 00:13:21.339 --> 00:13:24.600 align:start position:0% for example that I want to enter to a nightclub<00:13:21.610> I<00:13:22.180> want<00:13:23.019> to<00:13:23.230> prove<00:13:23.920> that<00:13:23.980> I'm<00:13:24.430> 18 00:13:24.600 --> 00:13:24.610 align:start position:0% nightclub I want to prove that I'm 18 00:13:24.610 --> 00:13:28.439 align:start position:0% nightclub I want to prove that I'm 18 years<00:13:24.970> old<00:13:25.269> but<00:13:26.079> I<00:13:26.139> don't<00:13:26.620> want<00:13:26.920> to<00:13:27.269> tell<00:13:28.269> to 00:13:28.439 --> 00:13:28.449 align:start position:0% years old but I don't want to tell to 00:13:28.449 --> 00:13:30.150 align:start position:0% years old but I don't want to tell to the<00:13:28.529> entry<00:13:29.529> people 00:13:30.150 --> 00:13:30.160 align:start position:0% the entry people 00:13:30.160 --> 00:13:32.639 align:start position:0% the entry people Who<00:13:30.819> am<00:13:30.850> I<00:13:31.060> where<00:13:31.540> I<00:13:31.569> live<00:13:31.839> and<00:13:32.139> all<00:13:32.500> the 00:13:32.639 --> 00:13:32.649 align:start position:0% Who am I where I live and all the 00:13:32.649 --> 00:13:35.280 align:start position:0% Who am I where I live and all the information<00:13:33.190> about<00:13:33.279> that<00:13:33.430> so<00:13:34.300> I<00:13:34.569> can<00:13:35.019> make<00:13:35.259> a 00:13:35.280 --> 00:13:35.290 align:start position:0% information about that so I can make a 00:13:35.290 --> 00:13:37.650 align:start position:0% information about that so I can make a zero<00:13:35.740> knowledge<00:13:35.949> proof<00:13:36.100> that<00:13:36.970> prove<00:13:37.329> that<00:13:37.360> I 00:13:37.650 --> 00:13:37.660 align:start position:0% zero knowledge proof that prove that I 00:13:37.660 --> 00:13:40.889 align:start position:0% zero knowledge proof that prove that I really<00:13:38.050> hold<00:13:38.319> the<00:13:38.440> key<00:13:39.240> that<00:13:40.240> according<00:13:40.870> to 00:13:40.889 --> 00:13:40.899 align:start position:0% really hold the key that according to 00:13:40.899 --> 00:13:45.809 align:start position:0% really hold the key that according to the<00:13:41.380> government<00:13:42.630> I'm<00:13:43.630> 18<00:13:44.470> a<00:13:44.680> year<00:13:44.920> years<00:13:45.190> old 00:13:45.809 --> 00:13:45.819 align:start position:0% the government I'm 18 a year years old 00:13:45.819 --> 00:13:49.740 align:start position:0% the government I'm 18 a year years old but<00:13:47.220> without<00:13:48.220> revealing<00:13:48.540> anything<00:13:49.540> else 00:13:49.740 --> 00:13:49.750 align:start position:0% but without revealing anything else 00:13:49.750 --> 00:13:52.710 align:start position:0% but without revealing anything else about<00:13:50.199> my<00:13:50.500> identity<00:13:51.360> the<00:13:52.360> same<00:13:52.540> thing 00:13:52.710 --> 00:13:52.720 align:start position:0% about my identity the same thing 00:13:52.720 --> 00:13:54.150 align:start position:0% about my identity the same thing happened<00:13:53.050> for<00:13:53.170> example<00:13:53.529> with<00:13:53.709> anonymous 00:13:54.150 --> 00:13:54.160 align:start position:0% happened for example with anonymous 00:13:54.160 --> 00:13:57.809 align:start position:0% happened for example with anonymous voting<00:13:55.470> if<00:13:56.470> I<00:13:56.649> when<00:13:56.829> I<00:13:56.860> want<00:13:57.130> to<00:13:57.279> vote<00:13:57.459> when<00:13:57.790> I 00:13:57.809 --> 00:13:57.819 align:start position:0% voting if I when I want to vote when I 00:13:57.819 --> 00:14:01.439 align:start position:0% voting if I when I want to vote when I want<00:13:58.029> to<00:13:58.149> vote<00:13:58.360> I<00:13:59.819> don't<00:14:00.819> want<00:14:01.000> to<00:14:01.089> reveal<00:14:01.269> my 00:14:01.439 --> 00:14:01.449 align:start position:0% want to vote I don't want to reveal my 00:14:01.449 --> 00:14:04.530 align:start position:0% want to vote I don't want to reveal my identity<00:14:01.660> I<00:14:02.380> want<00:14:03.339> to<00:14:03.430> vote<00:14:03.610> I<00:14:03.880> need<00:14:04.209> but<00:14:04.389> I 00:14:04.530 --> 00:14:04.540 align:start position:0% identity I want to vote I need but I 00:14:04.540 --> 00:14:07.379 align:start position:0% identity I want to vote I need but I need<00:14:04.720> to<00:14:04.839> ensure<00:14:05.319> that<00:14:05.589> I<00:14:05.800> can<00:14:06.069> vote<00:14:06.250> but<00:14:07.120> I<00:14:07.240> can 00:14:07.379 --> 00:14:07.389 align:start position:0% need to ensure that I can vote but I can 00:14:07.389 --> 00:14:10.079 align:start position:0% need to ensure that I can vote but I can vote<00:14:07.540> that<00:14:07.720> I<00:14:07.810> can<00:14:08.019> that<00:14:08.560> I<00:14:08.769> am<00:14:09.160> that<00:14:09.699> somebody 00:14:10.079 --> 00:14:10.089 align:start position:0% vote that I can that I am that somebody 00:14:10.089 --> 00:14:13.079 align:start position:0% vote that I can that I am that somebody claim<00:14:10.449> it<00:14:10.660> that<00:14:11.500> I<00:14:11.709> can<00:14:12.009> participate<00:14:12.339> in<00:14:12.819> that 00:14:13.079 --> 00:14:13.089 align:start position:0% claim it that I can participate in that 00:14:13.089 --> 00:14:16.769 align:start position:0% claim it that I can participate in that voting<00:14:13.990> okay<00:14:14.649> this<00:14:14.949> can<00:14:15.130> be<00:14:15.220> used<00:14:15.370> in<00:14:15.569> this<00:14:16.569> can 00:14:16.769 --> 00:14:16.779 align:start position:0% voting okay this can be used in this can 00:14:16.779 --> 00:14:21.120 align:start position:0% voting okay this can be used in this can be<00:14:16.899> use<00:14:17.079> in<00:14:17.110> in<00:14:17.829> in<00:14:18.720> this<00:14:19.720> can<00:14:19.930> be<00:14:20.019> used<00:14:20.170> so<00:14:20.980> this 00:14:21.120 --> 00:14:21.130 align:start position:0% be use in in in this can be used so this 00:14:21.130 --> 00:14:22.889 align:start position:0% be use in in in this can be used so this can<00:14:21.279> be<00:14:21.370> used<00:14:21.490> for<00:14:21.610> a<00:14:21.639> for<00:14:22.089> a<00:14:22.120> voting<00:14:22.509> system 00:14:22.889 --> 00:14:22.899 align:start position:0% can be used for a for a voting system 00:14:22.899 --> 00:14:25.379 align:start position:0% can be used for a for a voting system another<00:14:23.740> example<00:14:23.920> that<00:14:24.310> implies<00:14:24.790> for<00:14:24.819> example 00:14:25.379 --> 00:14:25.389 align:start position:0% another example that implies for example 00:14:25.389 --> 00:14:28.759 align:start position:0% another example that implies for example as<00:14:25.480> Marc<00:14:25.689> contract<00:14:26.050> would<00:14:26.170> be<00:14:26.319> an<00:14:26.410> IC<00:14:26.560> o---- 00:14:28.759 --> 00:14:28.769 align:start position:0% as Marc contract would be an IC o---- 00:14:28.769 --> 00:14:33.210 align:start position:0% as Marc contract would be an IC o---- may<00:14:29.769> be<00:14:29.829> an<00:14:30.189> IC<00:14:30.519> o----<00:14:31.139> requires<00:14:32.139> that<00:14:33.040> the 00:14:33.210 --> 00:14:33.220 align:start position:0% may be an IC o---- requires that the 00:14:33.220 --> 00:14:34.710 align:start position:0% may be an IC o---- requires that the people<00:14:33.490> that<00:14:33.610> participate<00:14:34.120> in<00:14:34.149> this<00:14:34.389> in<00:14:34.689> that 00:14:34.710 --> 00:14:34.720 align:start position:0% people that participate in this in that 00:14:34.720 --> 00:14:36.920 align:start position:0% people that participate in this in that IC<00:14:35.139> o----<00:14:35.170> is<00:14:35.380> authorized<00:14:35.860> by<00:14:36.130> a<00:14:36.160> third<00:14:36.430> party 00:14:36.920 --> 00:14:36.930 align:start position:0% IC o---- is authorized by a third party 00:14:36.930 --> 00:14:39.389 align:start position:0% IC o---- is authorized by a third party because<00:14:37.930> somehow<00:14:38.110> I<00:14:38.290> see<00:14:38.649> from<00:14:38.980> some<00:14:39.220> legal 00:14:39.389 --> 00:14:39.399 align:start position:0% because somehow I see from some legal 00:14:39.399 --> 00:14:44.340 align:start position:0% because somehow I see from some legal stuff<00:14:39.730> I<00:14:40.380> can't<00:14:41.380> create<00:14:41.680> an<00:14:41.920> IC<00:14:42.310> o----<00:14:42.339> a<00:14:43.350> smart 00:14:44.340 --> 00:14:44.350 align:start position:0% stuff I can't create an IC o---- a smart 00:14:44.350 --> 00:14:46.920 align:start position:0% stuff I can't create an IC o---- a smart contract<00:14:44.529> IC<00:14:44.920> o----<00:14:45.130> that<00:14:45.970> accepts<00:14:46.509> zero 00:14:46.920 --> 00:14:46.930 align:start position:0% contract IC o---- that accepts zero 00:14:46.930 --> 00:14:52.259 align:start position:0% contract IC o---- that accepts zero knowledge<00:14:47.170> proof<00:14:48.600> that<00:14:49.600> warranties<00:14:50.439> that<00:14:51.269> the 00:14:52.259 --> 00:14:52.269 align:start position:0% knowledge proof that warranties that the 00:14:52.269 --> 00:14:57.329 align:start position:0% knowledge proof that warranties that the people<00:14:52.630> that<00:14:52.779> participate<00:14:53.410> that<00:14:55.980> it's<00:14:56.980> okay 00:14:57.329 --> 00:14:57.339 align:start position:0% people that participate that it's okay 00:14:57.339 --> 00:14:59.400 align:start position:0% people that participate that it's okay it's<00:14:57.550> in<00:14:57.670> the<00:14:57.790> list<00:14:57.970> it's<00:14:58.750> now<00:14:58.930> to<00:14:58.990> write<00:14:59.259> this 00:14:59.400 --> 00:14:59.410 align:start position:0% it's in the list it's now to write this 00:14:59.410 --> 00:15:01.679 align:start position:0% it's in the list it's now to write this person<00:14:59.889> but<00:15:00.459> without<00:15:00.819> revealing<00:15:01.060> exactly 00:15:01.679 --> 00:15:01.689 align:start position:0% person but without revealing exactly 00:15:01.689 --> 00:15:04.559 align:start position:0% person but without revealing exactly what<00:15:01.870> I<00:15:01.899> Who<00:15:02.079> am<00:15:02.380> I<00:15:02.500> or<00:15:02.740> even<00:15:03.220> how<00:15:03.490> much<00:15:03.699> money<00:15:04.449> I 00:15:04.559 --> 00:15:04.569 align:start position:0% what I Who am I or even how much money I 00:15:04.569 --> 00:15:12.079 align:start position:0% what I Who am I or even how much money I spend<00:15:05.019> on<00:15:05.139> that<00:15:05.649> on<00:15:05.980> that<00:15:06.269> on<00:15:07.269> that<00:15:07.569> IC<00:15:08.079> o---- 00:15:12.079 --> 00:15:12.089 align:start position:0% 00:15:12.089 --> 00:15:14.790 align:start position:0% another<00:15:13.089> interesting<00:15:13.630> things<00:15:13.899> that<00:15:14.259> we<00:15:14.740> are 00:15:14.790 --> 00:15:14.800 align:start position:0% another interesting things that we are 00:15:14.800 --> 00:15:17.160 align:start position:0% another interesting things that we are doing<00:15:15.069> is<00:15:15.430> this<00:15:15.970> concept<00:15:16.449> of<00:15:16.600> non-reusable 00:15:17.160 --> 00:15:17.170 align:start position:0% doing is this concept of non-reusable 00:15:17.170 --> 00:15:18.030 align:start position:0% doing is this concept of non-reusable proofs 00:15:18.030 --> 00:15:18.040 align:start position:0% proofs 00:15:18.040 --> 00:15:21.329 align:start position:0% proofs what's<00:15:18.699> a<00:15:18.850> non-reusable<00:15:19.269> proof<00:15:20.130> imagine<00:15:21.130> that 00:15:21.329 --> 00:15:21.339 align:start position:0% what's a non-reusable proof imagine that 00:15:21.339 --> 00:15:24.420 align:start position:0% what's a non-reusable proof imagine that i<00:15:21.550> belongs<00:15:22.060> to<00:15:22.360> a<00:15:22.389> political<00:15:22.750> party<00:15:23.430> according 00:15:24.420 --> 00:15:24.430 align:start position:0% i belongs to a political party according 00:15:24.430 --> 00:15:26.939 align:start position:0% i belongs to a political party according to<00:15:24.790> the<00:15:24.880> political<00:15:25.300> party<00:15:25.660> so<00:15:26.620> the<00:15:26.740> political 00:15:26.939 --> 00:15:26.949 align:start position:0% to the political party so the political 00:15:26.949 --> 00:15:29.129 align:start position:0% to the political party so the political party<00:15:27.399> maybe<00:15:27.579> makes<00:15:28.000> a<00:15:28.209> private<00:15:28.569> claim<00:15:28.750> on<00:15:28.990> me 00:15:29.129 --> 00:15:29.139 align:start position:0% party maybe makes a private claim on me 00:15:29.139 --> 00:15:31.410 align:start position:0% party maybe makes a private claim on me that<00:15:29.680> I<00:15:29.800> belongs<00:15:30.100> to<00:15:30.189> a<00:15:30.279> political<00:15:30.430> party 00:15:31.410 --> 00:15:31.420 align:start position:0% that I belongs to a political party 00:15:31.420 --> 00:15:34.199 align:start position:0% that I belongs to a political party I<00:15:31.450> want<00:15:32.140> to<00:15:32.290> prove<00:15:32.470> him<00:15:32.790> that<00:15:33.790> I'm<00:15:33.970> from<00:15:34.180> that 00:15:34.199 --> 00:15:34.209 align:start position:0% I want to prove him that I'm from that 00:15:34.209 --> 00:15:37.949 align:start position:0% I want to prove him that I'm from that political<00:15:34.779> party<00:15:35.250> but<00:15:36.250> what<00:15:36.430> happened<00:15:37.000> if<00:15:37.240> he 00:15:37.949 --> 00:15:37.959 align:start position:0% political party but what happened if he 00:15:37.959 --> 00:15:41.579 align:start position:0% political party but what happened if he just<00:15:38.680> published<00:15:38.890> this<00:15:39.880> proof<00:15:40.300> to<00:15:41.019> everywhere 00:15:41.579 --> 00:15:41.589 align:start position:0% just published this proof to everywhere 00:15:41.589 --> 00:15:44.550 align:start position:0% just published this proof to everywhere in<00:15:41.649> the<00:15:41.920> world<00:15:42.209> everybody<00:15:43.209> would<00:15:43.450> know<00:15:43.480> that<00:15:43.990> I 00:15:44.550 --> 00:15:44.560 align:start position:0% in the world everybody would know that I 00:15:44.560 --> 00:15:46.550 align:start position:0% in the world everybody would know that I am<00:15:44.680> from<00:15:44.890> that<00:15:44.920> political<00:15:45.579> party<00:15:45.910> a 00:15:46.550 --> 00:15:46.560 align:start position:0% am from that political party a 00:15:46.560 --> 00:15:50.160 align:start position:0% am from that political party a non-reusable<00:15:47.560> proof<00:15:48.250> is<00:15:48.550> a<00:15:48.610> proof<00:15:49.029> that<00:15:49.870> I 00:15:50.160 --> 00:15:50.170 align:start position:0% non-reusable proof is a proof that I 00:15:50.170 --> 00:15:53.100 align:start position:0% non-reusable proof is a proof that I can't<00:15:50.800> send<00:15:51.190> it<00:15:51.339> to<00:15:51.459> him<00:15:51.700> and<00:15:51.940> I<00:15:52.690> have<00:15:52.959> the 00:15:53.100 --> 00:15:53.110 align:start position:0% can't send it to him and I have the 00:15:53.110 --> 00:15:56.220 align:start position:0% can't send it to him and I have the warranty<00:15:53.620> that<00:15:54.070> if<00:15:54.220> he<00:15:54.399> published<00:15:54.790> that<00:15:55.230> it 00:15:56.220 --> 00:15:56.230 align:start position:0% warranty that if he published that it 00:15:56.230 --> 00:15:59.040 align:start position:0% warranty that if he published that it will<00:15:56.560> not<00:15:56.800> prove<00:15:57.100> nothing<00:15:57.519> of<00:15:57.730> course<00:15:58.390> he<00:15:58.839> can 00:15:59.040 --> 00:15:59.050 align:start position:0% will not prove nothing of course he can 00:15:59.050 --> 00:16:00.810 align:start position:0% will not prove nothing of course he can always<00:15:59.560> say<00:15:59.800> that<00:15:59.829> I'm<00:16:00.130> from<00:16:00.310> that<00:16:00.430> political 00:16:00.810 --> 00:16:00.820 align:start position:0% always say that I'm from that political 00:16:00.820 --> 00:16:02.370 align:start position:0% always say that I'm from that political party<00:16:01.120> and<00:16:01.209> his<00:16:01.300> information<00:16:01.750> that<00:16:02.050> he<00:16:02.200> knows 00:16:02.370 --> 00:16:02.380 align:start position:0% party and his information that he knows 00:16:02.380 --> 00:16:05.910 align:start position:0% party and his information that he knows but<00:16:02.890> he<00:16:02.950> will<00:16:03.310> not<00:16:03.519> be<00:16:03.700> able<00:16:03.880> to<00:16:04.060> prove<00:16:04.860> how<00:16:05.860> we 00:16:05.910 --> 00:16:05.920 align:start position:0% but he will not be able to prove how we 00:16:05.920 --> 00:16:06.780 align:start position:0% but he will not be able to prove how we do<00:16:06.279> that 00:16:06.780 --> 00:16:06.790 align:start position:0% do that 00:16:06.790 --> 00:16:10.009 align:start position:0% do that mainly<00:16:07.600> is<00:16:07.779> we're<00:16:07.959> taking<00:16:08.320> the<00:16:08.589> proof<00:16:09.339> I'm 00:16:10.009 --> 00:16:10.019 align:start position:0% mainly is we're taking the proof I'm 00:16:10.019 --> 00:16:14.069 align:start position:0% mainly is we're taking the proof I'm from<00:16:11.019> that<00:16:11.050> political<00:16:11.740> party<00:16:12.450> okay<00:16:13.450> and<00:16:13.690> I'm 00:16:14.069 --> 00:16:14.079 align:start position:0% from that political party okay and I'm 00:16:14.079 --> 00:16:18.230 align:start position:0% from that political party okay and I'm creating<00:16:14.380> like<00:16:14.769> another<00:16:15.160> proof<00:16:15.550> that<00:16:16.950> says 00:16:18.230 --> 00:16:18.240 align:start position:0% creating like another proof that says 00:16:18.240 --> 00:16:22.440 align:start position:0% creating like another proof that says okay<00:16:19.240> I'm<00:16:19.510> proving<00:16:20.050> to<00:16:20.079> you<00:16:20.440> that<00:16:20.579> I<00:16:21.579> am<00:16:22.000> from 00:16:22.440 --> 00:16:22.450 align:start position:0% okay I'm proving to you that I am from 00:16:22.450 --> 00:16:26.040 align:start position:0% okay I'm proving to you that I am from that<00:16:22.630> political<00:16:23.170> party<00:16:23.620> or<00:16:24.399> I<00:16:25.089> know<00:16:25.360> your 00:16:26.040 --> 00:16:26.050 align:start position:0% that political party or I know your 00:16:26.050 --> 00:16:29.970 align:start position:0% that political party or I know your private<00:16:26.529> key<00:16:27.329> of<00:16:28.329> course<00:16:28.839> I<00:16:29.200> don't<00:16:29.620> know<00:16:29.740> his 00:16:29.970 --> 00:16:29.980 align:start position:0% private key of course I don't know his 00:16:29.980 --> 00:16:33.840 align:start position:0% private key of course I don't know his private<00:16:30.339> key<00:16:30.490> so<00:16:30.700> he<00:16:31.510> is<00:16:31.660> sure<00:16:32.279> that<00:16:33.279> I<00:16:33.459> am<00:16:33.579> from 00:16:33.840 --> 00:16:33.850 align:start position:0% private key so he is sure that I am from 00:16:33.850 --> 00:16:36.600 align:start position:0% private key so he is sure that I am from that<00:16:34.000> political<00:16:34.480> party<00:16:34.949> but<00:16:35.949> what<00:16:36.130> happened 00:16:36.600 --> 00:16:36.610 align:start position:0% that political party but what happened 00:16:36.610 --> 00:16:38.819 align:start position:0% that political party but what happened now<00:16:36.790> when<00:16:37.329> he<00:16:37.600> published<00:16:37.839> that<00:16:38.170> to<00:16:38.440> everywhere 00:16:38.819 --> 00:16:38.829 align:start position:0% now when he published that to everywhere 00:16:38.829 --> 00:16:42.240 align:start position:0% now when he published that to everywhere else<00:16:38.910> he's<00:16:39.910> saying<00:16:40.240> his<00:16:41.199> proof<00:16:41.500> is<00:16:41.920> saying 00:16:42.240 --> 00:16:42.250 align:start position:0% else he's saying his proof is saying 00:16:42.250 --> 00:16:46.769 align:start position:0% else he's saying his proof is saying Jordi<00:16:43.060> is<00:16:43.089> from<00:16:43.839> that<00:16:43.990> political<00:16:44.500> party<00:16:44.890> or<00:16:45.779> I 00:16:46.769 --> 00:16:46.779 align:start position:0% Jordi is from that political party or I 00:16:46.779 --> 00:16:51.720 align:start position:0% Jordi is from that political party or I know<00:16:47.529> my<00:16:48.459> I<00:16:49.000> know<00:16:49.180> my<00:16:49.600> private<00:16:50.019> key<00:16:50.230> so<00:16:50.730> because 00:16:51.720 --> 00:16:51.730 align:start position:0% know my I know my private key so because 00:16:51.730 --> 00:16:54.090 align:start position:0% know my I know my private key so because you<00:16:52.510> know<00:16:52.630> everybody<00:16:53.260> knows<00:16:53.440> that<00:16:53.769> he<00:16:53.949> knows 00:16:54.090 --> 00:16:54.100 align:start position:0% you know everybody knows that he knows 00:16:54.100 --> 00:16:56.490 align:start position:0% you know everybody knows that he knows that<00:16:54.370> he<00:16:54.760> knows<00:16:54.910> the<00:16:55.089> private<00:16:55.390> key<00:16:55.570> is<00:16:55.899> obvious 00:16:56.490 --> 00:16:56.500 align:start position:0% that he knows the private key is obvious 00:16:56.500 --> 00:16:58.949 align:start position:0% that he knows the private key is obvious that<00:16:56.709> he<00:16:57.339> can<00:16:57.820> generate<00:16:57.940> as<00:16:58.300> many<00:16:58.420> proof<00:16:58.810> of 00:16:58.949 --> 00:16:58.959 align:start position:0% that he can generate as many proof of 00:16:58.959 --> 00:17:03.329 align:start position:0% that he can generate as many proof of those<00:16:59.670> faking<00:17:01.079> even<00:17:02.079> if<00:17:02.199> I'm<00:17:02.470> or<00:17:02.709> I'm<00:17:02.920> not<00:17:03.130> from 00:17:03.329 --> 00:17:03.339 align:start position:0% those faking even if I'm or I'm not from 00:17:03.339 --> 00:17:04.770 align:start position:0% those faking even if I'm or I'm not from the<00:17:03.430> political<00:17:03.640> party<00:17:04.030> so<00:17:04.209> this<00:17:04.360> part<00:17:04.630> this 00:17:04.770 --> 00:17:04.780 align:start position:0% the political party so this part this 00:17:04.780 --> 00:17:12.539 align:start position:0% the political party so this part this proof<00:17:05.169> is<00:17:05.500> not<00:17:06.160> usable<00:17:06.669> anymore<00:17:11.160> so<00:17:12.160> here<00:17:12.400> is 00:17:12.539 --> 00:17:12.549 align:start position:0% proof is not usable anymore so here is 00:17:12.549 --> 00:17:14.490 align:start position:0% proof is not usable anymore so here is more<00:17:12.910> or<00:17:12.939> less<00:17:13.179> the<00:17:13.419> technical<00:17:13.929> details<00:17:14.260> of 00:17:14.490 --> 00:17:14.500 align:start position:0% more or less the technical details of 00:17:14.500 --> 00:17:16.860 align:start position:0% more or less the technical details of what<00:17:14.799> we<00:17:14.980> are<00:17:15.010> doing<00:17:15.250> of<00:17:15.579> course 00:17:16.860 --> 00:17:16.870 align:start position:0% what we are doing of course 00:17:16.870 --> 00:17:19.770 align:start position:0% what we are doing of course identity<00:17:17.470> systems<00:17:17.890> like<00:17:18.459> this<00:17:18.669> are<00:17:19.089> required 00:17:19.770 --> 00:17:19.780 align:start position:0% identity systems like this are required 00:17:19.780 --> 00:17:22.710 align:start position:0% identity systems like this are required in<00:17:20.130> if<00:17:21.130> not<00:17:21.429> all<00:17:21.610> most<00:17:21.850> of<00:17:22.089> the<00:17:22.179> applications 00:17:22.710 --> 00:17:22.720 align:start position:0% in if not all most of the applications 00:17:22.720 --> 00:17:25.500 align:start position:0% in if not all most of the applications in<00:17:23.380> the<00:17:23.470> space<00:17:23.829> there<00:17:24.429> are<00:17:24.520> many<00:17:24.760> uses<00:17:25.000> to<00:17:25.329> use 00:17:25.500 --> 00:17:25.510 align:start position:0% in the space there are many uses to use 00:17:25.510 --> 00:17:28.289 align:start position:0% in the space there are many uses to use cases<00:17:25.780> from<00:17:26.110> reputation<00:17:26.890> systems<00:17:27.339> directory 00:17:28.289 --> 00:17:28.299 align:start position:0% cases from reputation systems directory 00:17:28.299 --> 00:17:31.760 align:start position:0% cases from reputation systems directory systems<00:17:29.010> signals<00:17:30.010> saying<00:17:30.160> simple<00:17:30.610> sang<00:17:30.790> ons 00:17:31.760 --> 00:17:31.770 align:start position:0% systems signals saying simple sang ons 00:17:31.770 --> 00:17:35.909 align:start position:0% systems signals saying simple sang ons many<00:17:32.770> I<00:17:32.860> would<00:17:33.460> say<00:17:33.640> that<00:17:34.620> almost<00:17:35.620> any 00:17:35.909 --> 00:17:35.919 align:start position:0% many I would say that almost any 00:17:35.919 --> 00:17:38.100 align:start position:0% many I would say that almost any application<00:17:36.610> that<00:17:36.640> you<00:17:37.390> think<00:17:37.690> that<00:17:37.900> there<00:17:38.020> is 00:17:38.100 --> 00:17:38.110 align:start position:0% application that you think that there is 00:17:38.110 --> 00:17:40.350 align:start position:0% application that you think that there is like<00:17:38.350> a<00:17:38.380> login<00:17:38.830> password<00:17:39.250> will<00:17:39.730> require<00:17:40.120> an 00:17:40.350 --> 00:17:40.360 align:start position:0% like a login password will require an 00:17:40.360 --> 00:17:44.570 align:start position:0% like a login password will require an identity<00:17:40.900> system<00:17:41.200> like<00:17:42.130> that 00:17:44.570 --> 00:17:44.580 align:start position:0% 00:17:44.580 --> 00:17:46.920 align:start position:0% what's<00:17:45.580> the<00:17:45.670> status<00:17:45.880> of<00:17:46.180> the<00:17:46.270> project<00:17:46.450> well<00:17:46.840> we 00:17:46.920 --> 00:17:46.930 align:start position:0% what's the status of the project well we 00:17:46.930 --> 00:17:49.370 align:start position:0% what's the status of the project well we have<00:17:47.080> him<00:17:47.200> working<00:17:47.440> very<00:17:48.070> hard<00:17:48.370> for<00:17:48.700> the<00:17:49.030> last 00:17:49.370 --> 00:17:49.380 align:start position:0% have him working very hard for the last 00:17:49.380 --> 00:17:52.050 align:start position:0% have him working very hard for the last four<00:17:50.380> five<00:17:50.710> months<00:17:51.070> so<00:17:51.430> it's<00:17:51.580> a<00:17:51.670> very<00:17:51.880> young 00:17:52.050 --> 00:17:52.060 align:start position:0% four five months so it's a very young 00:17:52.060 --> 00:17:55.860 align:start position:0% four five months so it's a very young project<00:17:52.570> right<00:17:52.750> now<00:17:52.780> but<00:17:54.150> what<00:17:55.150> what<00:17:55.540> we<00:17:55.690> have 00:17:55.860 --> 00:17:55.870 align:start position:0% project right now but what what we have 00:17:55.870 --> 00:17:57.480 align:start position:0% project right now but what what we have a<00:17:55.900> chief<00:17:56.170> right<00:17:56.380> now<00:17:56.500> we<00:17:56.680> already<00:17:56.830> have<00:17:57.070> a 00:17:57.480 --> 00:17:57.490 align:start position:0% a chief right now we already have a 00:17:57.490 --> 00:18:01.980 align:start position:0% a chief right now we already have a fully<00:17:57.730> functional<00:17:58.560> wallet<00:17:59.970> wallet<00:18:00.970> four<00:18:01.390> four 00:18:01.980 --> 00:18:01.990 align:start position:0% fully functional wallet wallet four four 00:18:01.990 --> 00:18:04.410 align:start position:0% fully functional wallet wallet four four identities<00:18:02.190> where<00:18:03.190> you<00:18:03.310> can<00:18:03.520> see<00:18:03.790> where<00:18:04.300> you 00:18:04.410 --> 00:18:04.420 align:start position:0% identities where you can see where you 00:18:04.420 --> 00:18:06.960 align:start position:0% identities where you can see where you can<00:18:04.450> create<00:18:05.410> your<00:18:05.590> identities<00:18:06.160> you<00:18:06.460> can<00:18:06.700> do 00:18:06.960 --> 00:18:06.970 align:start position:0% can create your identities you can do 00:18:06.970 --> 00:18:08.640 align:start position:0% can create your identities you can do start<00:18:07.330> doing<00:18:07.540> claims<00:18:07.810> checking<00:18:08.290> the<00:18:08.410> claims 00:18:08.640 --> 00:18:08.650 align:start position:0% start doing claims checking the claims 00:18:08.650 --> 00:18:11.670 align:start position:0% start doing claims checking the claims proving<00:18:09.550> the<00:18:09.640> claims<00:18:09.880> and<00:18:10.180> so<00:18:10.300> on<00:18:10.450> we<00:18:11.440> have<00:18:11.470> a 00:18:11.670 --> 00:18:11.680 align:start position:0% proving the claims and so on we have a 00:18:11.680 --> 00:18:14.070 align:start position:0% proving the claims and so on we have a relator<00:18:12.100> right<00:18:12.700> now<00:18:12.880> is<00:18:13.090> still<00:18:13.360> a<00:18:13.390> trusted<00:18:13.900> for 00:18:14.070 --> 00:18:14.080 align:start position:0% relator right now is still a trusted for 00:18:14.080 --> 00:18:16.620 align:start position:0% relator right now is still a trusted for layer<00:18:14.200> and<00:18:14.560> we<00:18:15.340> have<00:18:15.550> been<00:18:15.730> working<00:18:15.910> also<00:18:16.480> in 00:18:16.620 --> 00:18:16.630 align:start position:0% layer and we have been working also in 00:18:16.630 --> 00:18:18.900 align:start position:0% layer and we have been working also in the<00:18:16.780> zero-knowledge<00:18:17.230> technology<00:18:18.070> for<00:18:18.790> the 00:18:18.900 --> 00:18:18.910 align:start position:0% the zero-knowledge technology for the 00:18:18.910 --> 00:18:21.150 align:start position:0% the zero-knowledge technology for the zero-knowledge<00:18:19.300> technology<00:18:20.050> we<00:18:20.470> just<00:18:20.650> live 00:18:21.150 --> 00:18:21.160 align:start position:0% zero-knowledge technology we just live 00:18:21.160 --> 00:18:22.800 align:start position:0% zero-knowledge technology we just live right<00:18:21.190> now<00:18:21.490> just<00:18:21.760> created<00:18:22.120> a<00:18:22.180> couple<00:18:22.390> of<00:18:22.570> tools 00:18:22.800 --> 00:18:22.810 align:start position:0% right now just created a couple of tools 00:18:22.810 --> 00:18:25.590 align:start position:0% right now just created a couple of tools one<00:18:23.470> is<00:18:23.650> a<00:18:24.090> circuit<00:18:25.090> compiler 00:18:25.590 --> 00:18:25.600 align:start position:0% one is a circuit compiler 00:18:25.600 --> 00:18:28.980 align:start position:0% one is a circuit compiler it's<00:18:26.200> a<00:18:26.380> compressor<00:18:27.100> well<00:18:27.820> it<00:18:27.940> just<00:18:27.970> is<00:18:28.270> a<00:18:28.300> it's 00:18:28.980 --> 00:18:28.990 align:start position:0% it's a compressor well it just is a it's 00:18:28.990 --> 00:18:31.640 align:start position:0% it's a compressor well it just is a it's a<00:18:29.170> language<00:18:29.590> where<00:18:30.070> you<00:18:30.160> can<00:18:30.400> create 00:18:31.640 --> 00:18:31.650 align:start position:0% a language where you can create 00:18:31.650 --> 00:18:35.610 align:start position:0% a language where you can create zero-knowledge<00:18:32.820> circuits<00:18:33.820> and<00:18:34.270> you<00:18:34.960> can<00:18:35.290> and 00:18:35.610 --> 00:18:35.620 align:start position:0% zero-knowledge circuits and you can and 00:18:35.620 --> 00:18:38.340 align:start position:0% zero-knowledge circuits and you can and and<00:18:36.280> then<00:18:36.940> we<00:18:37.330> have<00:18:37.480> another<00:18:37.750> tool<00:18:38.110> that's 00:18:38.340 --> 00:18:38.350 align:start position:0% and then we have another tool that's 00:18:38.350 --> 00:18:40.860 align:start position:0% and then we have another tool that's called<00:18:38.770> snarky<00:18:39.400> I<00:18:39.490> guess<00:18:39.670> it's<00:18:39.940> just<00:18:40.150> a<00:18:40.330> simple 00:18:40.860 --> 00:18:40.870 align:start position:0% called snarky I guess it's just a simple 00:18:40.870 --> 00:18:44.580 align:start position:0% called snarky I guess it's just a simple JavaScript<00:18:41.760> implementation<00:18:42.760> of<00:18:43.750> the<00:18:43.990> of<00:18:44.350> the 00:18:44.580 --> 00:18:44.590 align:start position:0% JavaScript implementation of the of the 00:18:44.590 --> 00:18:49.350 align:start position:0% JavaScript implementation of the of the Zetas<00:18:45.010> narcs<00:18:47.280> right<00:18:48.280> now<00:18:48.460> currently<00:18:49.030> we<00:18:49.090> are 00:18:49.350 --> 00:18:49.360 align:start position:0% Zetas narcs right now currently we are 00:18:49.360 --> 00:18:52.530 align:start position:0% Zetas narcs right now currently we are working<00:18:49.390> hard<00:18:49.960> in<00:18:50.290> trying<00:18:50.590> to<00:18:50.790> scale<00:18:51.790> the 00:18:52.530 --> 00:18:52.540 align:start position:0% working hard in trying to scale the 00:18:52.540 --> 00:18:55.800 align:start position:0% working hard in trying to scale the generation<00:18:53.230> of<00:18:53.380> Zika<00:18:53.740> snarks<00:18:54.190> proof<00:18:54.940> we<00:18:55.660> are 00:18:55.800 --> 00:18:55.810 align:start position:0% generation of Zika snarks proof we are 00:18:55.810 --> 00:18:57.810 align:start position:0% generation of Zika snarks proof we are working<00:18:56.050> with<00:18:56.530> different<00:18:57.160> people<00:18:57.520> in<00:18:57.730> the 00:18:57.810 --> 00:18:57.820 align:start position:0% working with different people in the 00:18:57.820 --> 00:19:01.230 align:start position:0% working with different people in the community<00:18:58.180> and<00:18:58.300> so<00:18:58.510> on<00:18:59.760> mainly<00:19:00.760> the<00:19:00.850> idea<00:19:00.880> is 00:19:01.230 --> 00:19:01.240 align:start position:0% community and so on mainly the idea is 00:19:01.240 --> 00:19:05.060 align:start position:0% community and so on mainly the idea is to<00:19:01.450> try<00:19:01.750> to<00:19:02.190> or<00:19:03.190> goal<00:19:03.490> right<00:19:03.730> now<00:19:03.760> is<00:19:03.910> to<00:19:04.120> create 00:19:05.060 --> 00:19:05.070 align:start position:0% to try to or goal right now is to create 00:19:05.070 --> 00:19:08.130 align:start position:0% to try to or goal right now is to create 1<00:19:06.070> billion<00:19:06.340> constraints<00:19:07.270> in<00:19:07.450> 10<00:19:07.720> seconds 00:19:08.130 --> 00:19:08.140 align:start position:0% 1 billion constraints in 10 seconds 00:19:08.140 --> 00:19:10.230 align:start position:0% 1 billion constraints in 10 seconds that's<00:19:08.380> our<00:19:08.530> goal<00:19:08.830> and<00:19:08.980> we<00:19:09.550> are<00:19:09.670> working<00:19:10.060> with 00:19:10.230 --> 00:19:10.240 align:start position:0% that's our goal and we are working with 00:19:10.240 --> 00:19:12.890 align:start position:0% that's our goal and we are working with different<00:19:10.540> technologies<00:19:11.380> GPU<00:19:11.920> FPGAs<00:19:12.640> and 00:19:12.890 --> 00:19:12.900 align:start position:0% different technologies GPU FPGAs and 00:19:12.900 --> 00:19:15.030 align:start position:0% different technologies GPU FPGAs and different<00:19:13.900> technologies<00:19:14.320> and<00:19:14.530> seeing<00:19:14.830> and 00:19:15.030 --> 00:19:15.040 align:start position:0% different technologies and seeing and 00:19:15.040 --> 00:19:16.470 align:start position:0% different technologies and seeing and trying<00:19:15.250> to<00:19:15.340> check<00:19:15.520> which<00:19:15.730> one<00:19:15.940> is<00:19:16.180> the<00:19:16.330> best 00:19:16.470 --> 00:19:16.480 align:start position:0% trying to check which one is the best 00:19:16.480 --> 00:19:20.610 align:start position:0% trying to check which one is the best one<00:19:16.630> for<00:19:17.050> that<00:19:17.790> and<00:19:18.790> that's<00:19:19.270> mainly<00:19:19.870> my 00:19:20.610 --> 00:19:20.620 align:start position:0% one for that and that's mainly my 00:19:20.620 --> 00:19:24.170 align:start position:0% one for that and that's mainly my presentation<00:19:21.340> here<00:19:21.730> are<00:19:21.960> some<00:19:22.960> takeaways 00:19:24.170 --> 00:19:24.180 align:start position:0% presentation here are some takeaways 00:19:24.180 --> 00:19:27.120 align:start position:0% presentation here are some takeaways self<00:19:25.180> sobering<00:19:25.510> and<00:19:25.630> identity<00:19:26.050> should<00:19:26.950> be<00:19:27.100> a 00:19:27.120 --> 00:19:27.130 align:start position:0% self sobering and identity should be a 00:19:27.130 --> 00:19:31.710 align:start position:0% self sobering and identity should be a scalable<00:19:27.670> privacy<00:19:28.660> by<00:19:28.780> design<00:19:30.150> have<00:19:31.150> we<00:19:31.510> have 00:19:31.710 --> 00:19:31.720 align:start position:0% scalable privacy by design have we have 00:19:31.720 --> 00:19:33.380 align:start position:0% scalable privacy by design have we have this<00:19:31.930> wallet<00:19:32.200> and<00:19:32.440> this<00:19:32.590> key<00:19:32.830> management 00:19:33.380 --> 00:19:33.390 align:start position:0% this wallet and this key management 00:19:33.390 --> 00:19:36.450 align:start position:0% this wallet and this key management early<00:19:34.390> version<00:19:34.810> if<00:19:35.230> any<00:19:35.560> of<00:19:35.740> you<00:19:35.920> is 00:19:36.450 --> 00:19:36.460 align:start position:0% early version if any of you is 00:19:36.460 --> 00:19:38.850 align:start position:0% early version if any of you is interested<00:19:37.000> in<00:19:37.120> checking<00:19:37.330> and<00:19:38.230> having<00:19:38.560> a<00:19:38.650> demo 00:19:38.850 --> 00:19:38.860 align:start position:0% interested in checking and having a demo 00:19:38.860 --> 00:19:40.590 align:start position:0% interested in checking and having a demo here<00:19:39.250> there<00:19:39.430> is<00:19:39.490> a<00:19:39.520> bunch<00:19:39.760> of<00:19:39.880> people<00:19:40.210> with<00:19:40.360> my 00:19:40.590 --> 00:19:40.600 align:start position:0% here there is a bunch of people with my 00:19:40.600 --> 00:19:43.590 align:start position:0% here there is a bunch of people with my shirt<00:19:40.870> there<00:19:41.380> we'll<00:19:41.530> be<00:19:41.680> glad<00:19:41.830> to<00:19:42.360> explain<00:19:43.360> it 00:19:43.590 --> 00:19:43.600 align:start position:0% shirt there we'll be glad to explain it 00:19:43.600 --> 00:19:47.520 align:start position:0% shirt there we'll be glad to explain it to<00:19:43.630> you<00:19:43.870> and<00:19:44.220> also<00:19:46.410> focusing<00:19:47.410> in 00:19:47.520 --> 00:19:47.530 align:start position:0% to you and also focusing in 00:19:47.530 --> 00:19:49.170 align:start position:0% to you and also focusing in standardization<00:19:48.160> centralization<00:19:48.970> is 00:19:49.170 --> 00:19:49.180 align:start position:0% standardization centralization is 00:19:49.180 --> 00:19:50.670 align:start position:0% standardization centralization is something<00:19:49.480> that<00:19:49.630> we<00:19:49.720> have<00:19:49.870> not<00:19:50.050> talked<00:19:50.260> very 00:19:50.670 --> 00:19:50.680 align:start position:0% something that we have not talked very 00:19:50.680 --> 00:19:55.150 align:start position:0% something that we have not talked very much<00:19:50.890> but<00:19:51.550> yeah<00:19:52.090> we<00:19:52.690> believe<00:19:53.200> that<00:19:53.910> the 00:19:55.150 --> 00:19:55.160 align:start position:0% much but yeah we believe that the 00:19:55.160 --> 00:19:57.070 align:start position:0% much but yeah we believe that the the<00:19:55.309> system<00:19:55.669> should<00:19:55.880> be<00:19:55.910> very<00:19:56.600> standardized 00:19:57.070 --> 00:19:57.080 align:start position:0% the system should be very standardized 00:19:57.080 --> 00:19:59.020 align:start position:0% the system should be very standardized that's<00:19:57.410> why<00:19:57.710> we<00:19:58.190> are<00:19:58.370> just<00:19:58.700> an<00:19:58.820> association 00:19:59.020 --> 00:19:59.030 align:start position:0% that's why we are just an association 00:19:59.030 --> 00:20:01.690 align:start position:0% that's why we are just an association it's<00:19:59.539> an<00:19:59.630> open-source<00:20:00.049> project<00:20:00.200> and<00:20:00.679> we<00:20:01.340> want 00:20:01.690 --> 00:20:01.700 align:start position:0% it's an open-source project and we want 00:20:01.700 --> 00:20:04.150 align:start position:0% it's an open-source project and we want to<00:20:01.940> work<00:20:02.450> and<00:20:02.750> contribute<00:20:03.020> as<00:20:03.380> much<00:20:03.410> as<00:20:03.799> we<00:20:03.950> can 00:20:04.150 --> 00:20:04.160 align:start position:0% to work and contribute as much as we can 00:20:04.160 --> 00:20:07.840 align:start position:0% to work and contribute as much as we can to<00:20:04.460> a<00:20:04.789> world<00:20:05.150> where<00:20:06.309> everything<00:20:07.309> is<00:20:07.490> more<00:20:07.730> or 00:20:07.840 --> 00:20:07.850 align:start position:0% to a world where everything is more or 00:20:07.850 --> 00:20:09.250 align:start position:0% to a world where everything is more or less<00:20:08.000> than<00:20:08.270> the<00:20:08.360> rights<00:20:08.510> and<00:20:08.780> the<00:20:08.900> system's 00:20:09.250 --> 00:20:09.260 align:start position:0% less than the rights and the system's 00:20:09.260 --> 00:20:10.539 align:start position:0% less than the rights and the system's connects<00:20:09.620> one<00:20:10.010> each<00:20:10.160> other 00:20:10.539 --> 00:20:10.549 align:start position:0% connects one each other 00:20:10.549 --> 00:20:20.760 align:start position:0% connects one each other and<00:20:10.640> that's<00:20:11.150> my<00:20:11.240> presentation<00:20:11.660> thank<00:20:12.500> you 00:20:20.760 --> 00:20:20.770 align:start position:0% 00:20:20.770 --> 00:20:27.820 align:start position:0% yeah<00:20:25.330> we<00:20:26.330> have<00:20:26.540> a<00:20:26.570> fair<00:20:27.200> amount<00:20:27.290> of<00:20:27.470> time<00:20:27.650> for 00:20:27.820 --> 00:20:27.830 align:start position:0% yeah we have a fair amount of time for 00:20:27.830 --> 00:20:35.080 align:start position:0% yeah we have a fair amount of time for questions<00:20:28.160> if<00:20:28.460> anyone<00:20:28.700> has<00:20:28.820> to<00:20:29.000> me<00:20:33.790> yeah<00:20:34.790> I 00:20:35.080 --> 00:20:35.090 align:start position:0% questions if anyone has to me yeah I 00:20:35.090 --> 00:20:37.030 align:start position:0% questions if anyone has to me yeah I just<00:20:35.240> came<00:20:35.540> back<00:20:36.020> from<00:20:36.260> the<00:20:36.440> internet 00:20:37.030 --> 00:20:37.040 align:start position:0% just came back from the internet 00:20:37.040 --> 00:20:39.250 align:start position:0% just came back from the internet identity<00:20:37.190> workshop<00:20:37.880> in<00:20:38.120> California<00:20:39.110> and<00:20:39.200> it 00:20:39.250 --> 00:20:39.260 align:start position:0% identity workshop in California and it 00:20:39.260 --> 00:20:40.930 align:start position:0% identity workshop in California and it was<00:20:39.380> great<00:20:39.740> it<00:20:39.920> seems<00:20:40.070> like<00:20:40.280> a<00:20:40.460> lot<00:20:40.790> of<00:20:40.880> these 00:20:40.930 --> 00:20:40.940 align:start position:0% was great it seems like a lot of these 00:20:40.940 --> 00:20:42.010 align:start position:0% was great it seems like a lot of these conversations<00:20:41.180> are<00:20:41.630> happening<00:20:41.750> around 00:20:42.010 --> 00:20:42.020 align:start position:0% conversations are happening around 00:20:42.020 --> 00:20:43.480 align:start position:0% conversations are happening around identity<00:20:42.410> in<00:20:42.620> the<00:20:42.710> internet<00:20:43.070> right<00:20:43.190> now<00:20:43.220> it's 00:20:43.480 --> 00:20:43.490 align:start position:0% identity in the internet right now it's 00:20:43.490 --> 00:20:46.440 align:start position:0% identity in the internet right now it's awesome<00:20:43.610> I<00:20:43.970> was<00:20:44.390> curious<00:20:44.630> if<00:20:44.840> I'd<00:20:45.560> entry<00:20:46.010> has 00:20:46.440 --> 00:20:46.450 align:start position:0% awesome I was curious if I'd entry has 00:20:46.450 --> 00:20:50.080 align:start position:0% awesome I was curious if I'd entry has an<00:20:47.450> D<00:20:48.140> ID<00:20:48.290> method<00:20:48.860> so<00:20:49.400> be<00:20:49.550> compatible<00:20:49.790> with<00:20:50.000> the 00:20:50.080 --> 00:20:50.090 align:start position:0% an D ID method so be compatible with the 00:20:50.090 --> 00:20:54.940 align:start position:0% an D ID method so be compatible with the ID<00:20:50.360> spec<00:20:51.370> yeah<00:20:52.370> the<00:20:52.910> ID<00:20:53.030> is<00:20:53.300> just<00:20:53.660> standard<00:20:54.620> for 00:20:54.940 --> 00:20:54.950 align:start position:0% ID spec yeah the ID is just standard for 00:20:54.950 --> 00:20:57.430 align:start position:0% ID spec yeah the ID is just standard for referring<00:20:55.430> to<00:20:55.640> the<00:20:55.820> identities<00:20:56.360> of<00:20:56.870> course 00:20:57.430 --> 00:20:57.440 align:start position:0% referring to the identities of course 00:20:57.440 --> 00:20:59.800 align:start position:0% referring to the identities of course it's<00:20:57.680> absolutely<00:20:58.190> compatible<00:20:58.520> because<00:20:59.090> even 00:20:59.800 --> 00:20:59.810 align:start position:0% it's absolutely compatible because even 00:20:59.810 --> 00:21:02.820 align:start position:0% it's absolutely compatible because even there<00:20:59.960> are<00:21:00.020> some<00:21:00.260> specific<00:21:01.010> standards<00:21:01.760> for<00:21:02.060> a 00:21:02.820 --> 00:21:02.830 align:start position:0% there are some specific standards for a 00:21:02.830 --> 00:21:07.180 align:start position:0% there are some specific standards for a theory<00:21:03.830> based<00:21:04.100> kind<00:21:04.760> identities<00:21:05.600> so<00:21:06.140> yes<00:21:06.860> it's 00:21:07.180 --> 00:21:07.190 align:start position:0% theory based kind identities so yes it's 00:21:07.190 --> 00:21:09.250 align:start position:0% theory based kind identities so yes it's I<00:21:07.580> would<00:21:07.850> say<00:21:07.970> that<00:21:08.330> the<00:21:08.450> current<00:21:08.630> standards 00:21:09.250 --> 00:21:09.260 align:start position:0% I would say that the current standards 00:21:09.260 --> 00:21:12.910 align:start position:0% I would say that the current standards are<00:21:09.940> appliable<00:21:10.940> the<00:21:11.900> main<00:21:12.110> problem<00:21:12.590> of<00:21:12.740> the 00:21:12.910 --> 00:21:12.920 align:start position:0% are appliable the main problem of the 00:21:12.920 --> 00:21:14.980 align:start position:0% are appliable the main problem of the current<00:21:13.250> standards<00:21:13.460> is<00:21:13.910> that<00:21:13.970> all<00:21:14.510> these<00:21:14.690> zero 00:21:14.980 --> 00:21:14.990 align:start position:0% current standards is that all these zero 00:21:14.990 --> 00:21:18.550 align:start position:0% current standards is that all these zero knowledge<00:21:15.200> technology<00:21:16.010> is<00:21:16.370> not<00:21:17.410> it's<00:21:18.410> not 00:21:18.550 --> 00:21:18.560 align:start position:0% knowledge technology is not it's not 00:21:18.560 --> 00:21:23.200 align:start position:0% knowledge technology is not it's not very<00:21:18.860> much<00:21:19.100> on<00:21:19.520> their<00:21:19.880> mind<00:21:20.210> and<00:21:20.590> you<00:21:21.590> know<00:21:22.210> for 00:21:23.200 --> 00:21:23.210 align:start position:0% very much on their mind and you know for 00:21:23.210 --> 00:21:24.910 align:start position:0% very much on their mind and you know for example<00:21:23.300> it<00:21:23.600> makes<00:21:23.750> no<00:21:23.960> sense<00:21:24.230> at<00:21:24.440> all<00:21:24.530> to<00:21:24.560> put 00:21:24.910 --> 00:21:24.920 align:start position:0% example it makes no sense at all to put 00:21:24.920 --> 00:21:28.270 align:start position:0% example it makes no sense at all to put a<00:21:24.980> jsonparser<00:21:25.550> inserted<00:21:26.450> inside<00:21:26.900> the<00:21:27.830> cosmic 00:21:28.270 --> 00:21:28.280 align:start position:0% a jsonparser inserted inside the cosmic 00:21:28.280 --> 00:21:31.240 align:start position:0% a jsonparser inserted inside the cosmic circuit<00:21:28.670> so<00:21:29.300> I<00:21:29.630> would<00:21:30.320> say<00:21:30.530> that<00:21:30.560> there<00:21:31.130> are 00:21:31.240 --> 00:21:31.250 align:start position:0% circuit so I would say that there are 00:21:31.250 --> 00:21:34.300 align:start position:0% circuit so I would say that there are some<00:21:31.490> modifications<00:21:31.760> and<00:21:32.600> some<00:21:33.190> adoptions<00:21:34.190> to 00:21:34.300 --> 00:21:34.310 align:start position:0% some modifications and some adoptions to 00:21:34.310 --> 00:21:36.690 align:start position:0% some modifications and some adoptions to those<00:21:34.460> standards<00:21:34.940> that<00:21:35.240> we<00:21:35.420> we<00:21:35.870> need<00:21:36.080> to<00:21:36.200> take 00:21:36.690 --> 00:21:36.700 align:start position:0% those standards that we we need to take 00:21:36.700 --> 00:21:40.090 align:start position:0% those standards that we we need to take with<00:21:37.700> we<00:21:38.270> need<00:21:38.450> to<00:21:38.570> take<00:21:38.720> B<00:21:38.930> in<00:21:39.140> account<00:21:39.620> in 00:21:40.090 --> 00:21:40.100 align:start position:0% with we need to take B in account in 00:21:40.100 --> 00:21:43.410 align:start position:0% with we need to take B in account in order<00:21:40.310> to<00:21:40.520> adapt<00:21:40.910> to<00:21:40.940> this<00:21:41.300> new<00:21:41.360> kind<00:21:41.930> of 00:21:43.410 --> 00:21:43.420 align:start position:0% order to adapt to this new kind of 00:21:43.420 --> 00:21:50.650 align:start position:0% order to adapt to this new kind of identities<00:21:47.590> so<00:21:48.590> for<00:21:49.400> application<00:21:50.180> developers 00:21:50.650 --> 00:21:50.660 align:start position:0% identities so for application developers 00:21:50.660 --> 00:21:56.170 align:start position:0% identities so for application developers what<00:21:50.900> can<00:21:51.080> we<00:21:51.200> use<00:21:54.160> yeah<00:21:55.160> we<00:21:55.400> have<00:21:55.580> a<00:21:55.610> we<00:21:56.150> are 00:21:56.170 --> 00:21:56.180 align:start position:0% what can we use yeah we have a we are 00:21:56.180 --> 00:21:59.170 align:start position:0% what can we use yeah we have a we are building<00:21:56.990> III<00:21:57.770> think<00:21:58.220> it's<00:21:58.520> quite<00:21:58.790> ready<00:21:59.090> but 00:21:59.170 --> 00:21:59.180 align:start position:0% building III think it's quite ready but 00:21:59.180 --> 00:22:02.200 align:start position:0% building III think it's quite ready but we're<00:21:59.900> building<00:22:00.140> mainly<00:22:00.620> an<00:22:00.710> SDK<00:22:01.250> where<00:22:01.940> all 00:22:02.200 --> 00:22:02.210 align:start position:0% we're building mainly an SDK where all 00:22:02.210 --> 00:22:06.280 align:start position:0% we're building mainly an SDK where all these<00:22:02.540> all<00:22:03.440> these<00:22:03.680> basic<00:22:04.490> functions<00:22:04.850> of<00:22:05.450> you 00:22:06.280 --> 00:22:06.290 align:start position:0% these all these basic functions of you 00:22:06.290 --> 00:22:08.080 align:start position:0% these all these basic functions of you know<00:22:06.380> creating<00:22:06.800> an<00:22:06.890> identity<00:22:07.250> creating<00:22:08.000> a 00:22:08.080 --> 00:22:08.090 align:start position:0% know creating an identity creating a 00:22:08.090 --> 00:22:11.950 align:start position:0% know creating an identity creating a claim<00:22:08.920> very<00:22:09.920> proving<00:22:10.580> a<00:22:10.640> claim<00:22:10.940> all<00:22:11.300> that 00:22:11.950 --> 00:22:11.960 align:start position:0% claim very proving a claim all that 00:22:11.960 --> 00:22:14.920 align:start position:0% claim very proving a claim all that should<00:22:12.230> be<00:22:12.440> embed<00:22:13.070> as<00:22:14.030> a<00:22:14.090> black<00:22:14.510> box 00:22:14.920 --> 00:22:14.930 align:start position:0% should be embed as a black box 00:22:14.930 --> 00:22:17.050 align:start position:0% should be embed as a black box so<00:22:15.350> we<00:22:15.530> are<00:22:15.650> working<00:22:15.800> in<00:22:16.160> this<00:22:16.370> library<00:22:16.700> in 00:22:17.050 --> 00:22:17.060 align:start position:0% so we are working in this library in 00:22:17.060 --> 00:22:20.170 align:start position:0% so we are working in this library in this<00:22:17.210> SDK<00:22:17.720> where<00:22:18.410> applications<00:22:19.040> will<00:22:19.760> be<00:22:19.790> able 00:22:20.170 --> 00:22:20.180 align:start position:0% this SDK where applications will be able 00:22:20.180 --> 00:22:23.740 align:start position:0% this SDK where applications will be able to<00:22:20.480> build<00:22:20.690> on<00:22:20.930> that<00:22:21.580> or<00:22:22.580> goal<00:22:22.910> for<00:22:23.240> example<00:22:23.330> or 00:22:23.740 --> 00:22:23.750 align:start position:0% to build on that or goal for example or 00:22:23.750 --> 00:22:25.690 align:start position:0% to build on that or goal for example or applicator<00:22:24.200> that<00:22:24.440> but<00:22:25.310> the<00:22:25.460> wallet 00:22:25.690 --> 00:22:25.700 align:start position:0% applicator that but the wallet 00:22:25.700 --> 00:22:26.980 align:start position:0% applicator that but the wallet application<00:22:26.300> is<00:22:26.450> just<00:22:26.720> a<00:22:26.810> reference 00:22:26.980 --> 00:22:26.990 align:start position:0% application is just a reference 00:22:26.990 --> 00:22:29.470 align:start position:0% application is just a reference application<00:22:27.440> we<00:22:28.100> are<00:22:28.130> working<00:22:28.670> very<00:22:28.880> much<00:22:29.090> in 00:22:29.470 --> 00:22:29.480 align:start position:0% application we are working very much in 00:22:29.480 --> 00:22:31.810 align:start position:0% application we are working very much in in<00:22:29.690> you<00:22:30.260> know<00:22:30.320> in<00:22:30.410> the<00:22:30.650> in<00:22:31.010> the<00:22:31.130> protocol<00:22:31.550> in 00:22:31.810 --> 00:22:31.820 align:start position:0% in you know in the in the protocol in 00:22:31.820 --> 00:22:33.540 align:start position:0% in you know in the in the protocol in the<00:22:31.940> standard<00:22:32.300> so<00:22:32.690> that 00:22:33.540 --> 00:22:33.550 align:start position:0% the standard so that 00:22:33.550 --> 00:22:35.490 align:start position:0% the standard so that you<00:22:33.640> know<00:22:33.730> even<00:22:34.150> if<00:22:34.510> anybody<00:22:34.960> wants<00:22:35.230> to<00:22:35.260> create 00:22:35.490 --> 00:22:35.500 align:start position:0% you know even if anybody wants to create 00:22:35.500 --> 00:22:37.380 align:start position:0% you know even if anybody wants to create an<00:22:35.650> application<00:22:35.800> that<00:22:36.190> horse<00:22:36.610> identity<00:22:37.180> is<00:22:37.240> in 00:22:37.380 --> 00:22:37.390 align:start position:0% an application that horse identity is in 00:22:37.390 --> 00:22:39.090 align:start position:0% an application that horse identity is in that<00:22:37.510> side<00:22:37.780> that<00:22:38.380> should<00:22:38.560> be<00:22:38.680> perfectly 00:22:39.090 --> 00:22:39.100 align:start position:0% that side that should be perfectly 00:22:39.100 --> 00:22:46.050 align:start position:0% that side that should be perfectly possible<00:22:39.310> i<00:22:42.660> cost<00:22:43.660> revere<00:22:43.960> Anahuac<00:22:45.060> imagine 00:22:46.050 --> 00:22:46.060 align:start position:0% possible i cost revere Anahuac imagine 00:22:46.060 --> 00:22:49.020 align:start position:0% possible i cost revere Anahuac imagine the<00:22:46.120> use<00:22:46.240> of<00:22:46.420> Zika<00:22:46.810> starts<00:22:47.170> to<00:22:47.940> alleviate<00:22:48.940> this 00:22:49.020 --> 00:22:49.030 align:start position:0% the use of Zika starts to alleviate this 00:22:49.030 --> 00:22:51.450 align:start position:0% the use of Zika starts to alleviate this sort<00:22:49.210> of<00:22:49.270> trusted<00:22:49.630> relayer<00:22:49.930> set<00:22:50.230> up<00:22:50.320> ZK<00:22:51.190> starks 00:22:51.450 --> 00:22:51.460 align:start position:0% sort of trusted relayer set up ZK starks 00:22:51.460 --> 00:22:53.040 align:start position:0% sort of trusted relayer set up ZK starks require<00:22:51.700> the<00:22:51.880> trusted<00:22:52.330> set<00:22:52.510> up<00:22:52.630> is<00:22:52.840> that<00:22:53.020> a 00:22:53.040 --> 00:22:53.050 align:start position:0% require the trusted set up is that a 00:22:53.050 --> 00:22:54.990 align:start position:0% require the trusted set up is that a concern<00:22:53.800> editor<00:22:54.400> is<00:22:54.460> there<00:22:54.580> anything<00:22:54.700> like 00:22:54.990 --> 00:22:55.000 align:start position:0% concern editor is there anything like 00:22:55.000 --> 00:22:56.100 align:start position:0% concern editor is there anything like malicious<00:22:55.240> you<00:22:55.420> could<00:22:55.540> do<00:22:55.630> if<00:22:55.750> there<00:22:55.900> was<00:22:55.990> an 00:22:56.100 --> 00:22:56.110 align:start position:0% malicious you could do if there was an 00:22:56.110 --> 00:22:59.000 align:start position:0% malicious you could do if there was an issue<00:22:56.260> with<00:22:56.500> the<00:22:56.620> generation<00:22:57.220> ceremony<00:22:57.580> yeah 00:22:59.000 --> 00:22:59.010 align:start position:0% issue with the generation ceremony yeah 00:22:59.010 --> 00:23:01.200 align:start position:0% issue with the generation ceremony yeah Zika<00:23:00.010> stars<00:23:00.250> we<00:23:00.460> all<00:23:00.580> of<00:23:00.670> us<00:23:00.820> this<00:23:01.060> is<00:23:01.180> a 00:23:01.200 --> 00:23:01.210 align:start position:0% Zika stars we all of us this is a 00:23:01.210 --> 00:23:04.950 align:start position:0% Zika stars we all of us this is a concern<00:23:02.550> you<00:23:03.550> know<00:23:03.730> this<00:23:03.940> is<00:23:04.030> the<00:23:04.150> big<00:23:04.330> pretty 00:23:04.950 --> 00:23:04.960 align:start position:0% concern you know this is the big pretty 00:23:04.960 --> 00:23:06.510 align:start position:0% concern you know this is the big pretty I<00:23:05.260> would<00:23:05.410> say<00:23:05.470> that<00:23:05.740> the<00:23:05.890> cars<00:23:06.280> are<00:23:06.370> quite 00:23:06.510 --> 00:23:06.520 align:start position:0% I would say that the cars are quite 00:23:06.520 --> 00:23:08.490 align:start position:0% I would say that the cars are quite perfect<00:23:07.000> except<00:23:07.330> for<00:23:07.510> that<00:23:07.630> which<00:23:07.900> is<00:23:07.930> a<00:23:08.110> huge 00:23:08.490 --> 00:23:08.500 align:start position:0% perfect except for that which is a huge 00:23:08.500 --> 00:23:09.000 align:start position:0% perfect except for that which is a huge issue 00:23:09.000 --> 00:23:09.010 align:start position:0% issue 00:23:09.010 --> 00:23:13.770 align:start position:0% issue so<00:23:10.410> yeah<00:23:11.670> just<00:23:12.670> set<00:23:12.910> up<00:23:13.000> is<00:23:13.150> a<00:23:13.240> problem<00:23:13.660> that 00:23:13.770 --> 00:23:13.780 align:start position:0% so yeah just set up is a problem that 00:23:13.780 --> 00:23:17.010 align:start position:0% so yeah just set up is a problem that you<00:23:13.900> have<00:23:14.080> once<00:23:14.380> we<00:23:14.770> are<00:23:15.100> thinking<00:23:15.640> in<00:23:16.020> of 00:23:17.010 --> 00:23:17.020 align:start position:0% you have once we are thinking in of 00:23:17.020 --> 00:23:19.310 align:start position:0% you have once we are thinking in of course<00:23:17.110> it's<00:23:18.040> something<00:23:18.160> that<00:23:18.460> we<00:23:18.550> are<00:23:18.700> start 00:23:19.310 --> 00:23:19.320 align:start position:0% course it's something that we are start 00:23:19.320 --> 00:23:21.960 align:start position:0% course it's something that we are start thinking<00:23:20.320> and<00:23:20.590> things<00:23:21.190> and<00:23:21.400> solutions<00:23:21.850> on 00:23:21.960 --> 00:23:21.970 align:start position:0% thinking and things and solutions on 00:23:21.970 --> 00:23:23.460 align:start position:0% thinking and things and solutions on that<00:23:22.120> we<00:23:22.360> have<00:23:22.510> thinking<00:23:22.780> for<00:23:22.930> example<00:23:22.990> in 00:23:23.460 --> 00:23:23.470 align:start position:0% that we have thinking for example in 00:23:23.470 --> 00:23:25.440 align:start position:0% that we have thinking for example in using<00:23:23.800> for<00:23:24.070> example<00:23:24.160> some<00:23:24.640> trusted<00:23:25.060> hardware 00:23:25.440 --> 00:23:25.450 align:start position:0% using for example some trusted hardware 00:23:25.450 --> 00:23:29.490 align:start position:0% using for example some trusted hardware to<00:23:25.930> do<00:23:26.080> these<00:23:26.910> these<00:23:27.910> ceremonies<00:23:28.780> of<00:23:29.050> course 00:23:29.490 --> 00:23:29.500 align:start position:0% to do these these ceremonies of course 00:23:29.500 --> 00:23:31.380 align:start position:0% to do these these ceremonies of course there<00:23:29.650> is<00:23:29.740> these<00:23:29.890> multi-party<00:23:30.550> computations 00:23:31.380 --> 00:23:31.390 align:start position:0% there is these multi-party computations 00:23:31.390 --> 00:23:33.840 align:start position:0% there is these multi-party computations on<00:23:31.690> that<00:23:31.870> we<00:23:32.260> need<00:23:32.410> to<00:23:32.530> automate<00:23:32.680> in<00:23:33.430> some<00:23:33.760> way 00:23:33.840 --> 00:23:33.850 align:start position:0% on that we need to automate in some way 00:23:33.850 --> 00:23:35.910 align:start position:0% on that we need to automate in some way or<00:23:33.970> the<00:23:34.000> other<00:23:34.150> but<00:23:34.870> the<00:23:34.990> nice<00:23:35.140> thing<00:23:35.170> of<00:23:35.560> the 00:23:35.910 --> 00:23:35.920 align:start position:0% or the other but the nice thing of the 00:23:35.920 --> 00:23:38.100 align:start position:0% or the other but the nice thing of the truce<00:23:36.520> is<00:23:36.610> set<00:23:36.760> up<00:23:36.880> is<00:23:37.030> that<00:23:37.060> once<00:23:37.570> you<00:23:37.900> have 00:23:38.100 --> 00:23:38.110 align:start position:0% truce is set up is that once you have 00:23:38.110 --> 00:23:39.720 align:start position:0% truce is set up is that once you have done<00:23:38.410> that<00:23:38.440> and<00:23:38.650> if<00:23:39.040> you<00:23:39.250> very<00:23:39.580> worried 00:23:39.720 --> 00:23:39.730 align:start position:0% done that and if you very worried 00:23:39.730 --> 00:23:42.120 align:start position:0% done that and if you very worried believes<00:23:40.180> in<00:23:40.480> that<00:23:40.630> ceremony<00:23:41.230> it's<00:23:41.620> valid 00:23:42.120 --> 00:23:42.130 align:start position:0% believes in that ceremony it's valid 00:23:42.130 --> 00:23:46.350 align:start position:0% believes in that ceremony it's valid then<00:23:42.850> the<00:23:43.090> system<00:23:43.510> is<00:23:43.630> good<00:23:44.560> forever<00:23:44.860> so<00:23:45.820> yeah 00:23:46.350 --> 00:23:46.360 align:start position:0% then the system is good forever so yeah 00:23:46.360 --> 00:23:48.930 align:start position:0% then the system is good forever so yeah we<00:23:46.570> are<00:23:46.600> just<00:23:47.440> analyzing<00:23:48.100> different<00:23:48.430> options 00:23:48.930 --> 00:23:48.940 align:start position:0% we are just analyzing different options 00:23:48.940 --> 00:23:51.620 align:start position:0% we are just analyzing different options of<00:23:49.060> that<00:23:49.240> and<00:23:49.510> yeah<00:23:49.930> that's<00:23:50.200> one<00:23:50.350> of<00:23:50.500> the<00:23:50.620> weak 00:23:51.620 --> 00:23:51.630 align:start position:0% of that and yeah that's one of the weak 00:23:51.630 --> 00:23:54.300 align:start position:0% of that and yeah that's one of the weak problems<00:23:52.630> there<00:23:53.200> are<00:23:53.230> there<00:23:53.680> are<00:23:53.800> also<00:23:53.980> all 00:23:54.300 --> 00:23:54.310 align:start position:0% problems there are there are also all 00:23:54.310 --> 00:23:57.120 align:start position:0% problems there are there are also all these<00:23:54.550> new<00:23:54.990> technologies<00:23:55.990> hysterics<00:23:56.950> for 00:23:57.120 --> 00:23:57.130 align:start position:0% these new technologies hysterics for 00:23:57.130 --> 00:23:58.470 align:start position:0% these new technologies hysterics for example<00:23:57.550> that<00:23:57.730> we<00:23:57.940> are<00:23:57.970> also<00:23:58.180> very<00:23:58.330> interested 00:23:58.470 --> 00:23:58.480 align:start position:0% example that we are also very interested 00:23:58.480 --> 00:24:02.210 align:start position:0% example that we are also very interested in<00:23:58.930> on<00:23:59.260> that<00:23:59.770> that<00:24:00.280> they<00:24:00.400> don't<00:24:00.520> require<00:24:00.820> these 00:24:02.210 --> 00:24:02.220 align:start position:0% in on that that they don't require these 00:24:02.220 --> 00:24:05.580 align:start position:0% in on that that they don't require these true<00:24:03.220> state<00:24:03.400> ceremonies<00:24:04.260> yeah<00:24:05.260> they<00:24:05.500> are 00:24:05.580 --> 00:24:05.590 align:start position:0% true state ceremonies yeah they are 00:24:05.590 --> 00:24:07.260 align:start position:0% true state ceremonies yeah they are quite<00:24:05.800> better<00:24:06.010> except<00:24:06.610> that<00:24:06.790> when<00:24:07.000> you<00:24:07.090> want 00:24:07.260 --> 00:24:07.270 align:start position:0% quite better except that when you want 00:24:07.270 --> 00:24:10.260 align:start position:0% quite better except that when you want to<00:24:07.330> go<00:24:07.510> on<00:24:07.930> chain<00:24:08.370> now<00:24:09.370> they<00:24:09.580> are<00:24:09.670> huge<00:24:10.090> I<00:24:10.240> think 00:24:10.260 --> 00:24:10.270 align:start position:0% to go on chain now they are huge I think 00:24:10.270 --> 00:24:14.880 align:start position:0% to go on chain now they are huge I think minimum<00:24:11.250> was<00:24:13.260> kilobytes<00:24:14.260> of<00:24:14.470> that<00:24:14.650> and 00:24:14.880 --> 00:24:14.890 align:start position:0% minimum was kilobytes of that and 00:24:14.890 --> 00:24:18.300 align:start position:0% minimum was kilobytes of that and putting<00:24:15.250> that<00:24:15.400> on<00:24:15.730> chain<00:24:16.620> at<00:24:17.620> least<00:24:17.950> right<00:24:18.130> now 00:24:18.300 --> 00:24:18.310 align:start position:0% putting that on chain at least right now 00:24:18.310 --> 00:24:20.910 align:start position:0% putting that on chain at least right now is<00:24:18.580> quite<00:24:19.510> a<00:24:19.540> problem<00:24:19.930> so<00:24:20.230> that's<00:24:20.440> why<00:24:20.620> we<00:24:20.800> are 00:24:20.910 --> 00:24:20.920 align:start position:0% is quite a problem so that's why we are 00:24:20.920 --> 00:24:23.700 align:start position:0% is quite a problem so that's why we are sticking<00:24:21.250> a<00:24:21.550> lot<00:24:21.730> in<00:24:21.940> in<00:24:22.720> the<00:24:22.960> snarks<00:24:23.500> but 00:24:23.700 --> 00:24:23.710 align:start position:0% sticking a lot in in the snarks but 00:24:23.710 --> 00:24:27.240 align:start position:0% sticking a lot in in the snarks but clearly<00:24:24.720> starks<00:24:25.720> is<00:24:25.870> technology<00:24:26.560> that<00:24:27.040> we<00:24:27.220> are 00:24:27.240 --> 00:24:27.250 align:start position:0% clearly starks is technology that we are 00:24:27.250 --> 00:24:31.350 align:start position:0% clearly starks is technology that we are start<00:24:27.940> looking<00:24:28.660> at<00:24:28.810> and<00:24:29.080> it's<00:24:29.620> a<00:24:29.860> another<00:24:30.820> zero 00:24:31.350 --> 00:24:31.360 align:start position:0% start looking at and it's a another zero 00:24:31.360 --> 00:24:33.570 align:start position:0% start looking at and it's a another zero knowledge<00:24:31.570> technologies<00:24:32.290> that<00:24:32.500> are<00:24:32.740> coming 00:24:33.570 --> 00:24:33.580 align:start position:0% knowledge technologies that are coming 00:24:33.580 --> 00:24:39.250 align:start position:0% knowledge technologies that are coming from<00:24:33.850> the<00:24:34.030> research<00:24:34.360> world 00:24:39.250 --> 00:24:39.260 align:start position:0% 00:24:39.260 --> 00:24:41.680 align:start position:0% there<00:24:40.100> was<00:24:40.250> a<00:24:40.280> someone<00:24:41.000> had<00:24:41.210> a<00:24:41.240> question<00:24:41.660> in 00:24:41.680 --> 00:24:41.690 align:start position:0% there was a someone had a question in 00:24:41.690 --> 00:24:57.010 align:start position:0% there was a someone had a question in the<00:24:41.780> back<00:24:41.809> who<00:24:42.080> has<00:24:42.200> a<00:24:42.230> mic<00:24:45.460> no<00:24:46.460> eats<00:24:46.610> kid<00:24:46.850> oh<00:24:56.020> hi 00:24:57.010 --> 00:24:57.020 align:start position:0% the back who has a mic no eats kid oh hi 00:24:57.020 --> 00:25:00.490 align:start position:0% the back who has a mic no eats kid oh hi maybe<00:24:57.740> this<00:24:57.919> is<00:24:58.040> a<00:24:58.270> longer<00:24:59.270> answer<00:24:59.540> but<00:25:00.020> I<00:25:00.200> was 00:25:00.490 --> 00:25:00.500 align:start position:0% maybe this is a longer answer but I was 00:25:00.500 --> 00:25:03.700 align:start position:0% maybe this is a longer answer but I was actually<00:25:00.710> unsure<00:25:01.640> how<00:25:01.940> when<00:25:02.870> the<00:25:03.169> receiver<00:25:03.500> of 00:25:03.700 --> 00:25:03.710 align:start position:0% actually unsure how when the receiver of 00:25:03.710 --> 00:25:06.370 align:start position:0% actually unsure how when the receiver of the<00:25:03.740> identity<00:25:04.309> he<00:25:05.240> exposes<00:25:05.570> the<00:25:05.809> information 00:25:06.370 --> 00:25:06.380 align:start position:0% the identity he exposes the information 00:25:06.380 --> 00:25:10.450 align:start position:0% the identity he exposes the information his<00:25:07.130> private<00:25:07.850> keys<00:25:08.090> you<00:25:08.570> were<00:25:08.660> saying<00:25:08.900> the<00:25:09.890> if 00:25:10.450 --> 00:25:10.460 align:start position:0% his private keys you were saying the if 00:25:10.460 --> 00:25:15.340 align:start position:0% his private keys you were saying the if he<00:25:10.640> publishes<00:25:10.940> the<00:25:11.210> identity<00:25:11.720> the<00:25:14.350> his 00:25:15.340 --> 00:25:15.350 align:start position:0% he publishes the identity the his 00:25:15.350 --> 00:25:17.289 align:start position:0% he publishes the identity the his private<00:25:15.740> keys<00:25:15.919> were<00:25:16.130> exposed<00:25:16.549> or<00:25:16.820> he<00:25:17.179> were 00:25:17.289 --> 00:25:17.299 align:start position:0% private keys were exposed or he were 00:25:17.299 --> 00:25:19.930 align:start position:0% private keys were exposed or he were saying<00:25:17.540> the<00:25:18.100> sender<00:25:19.100> of<00:25:19.190> the<00:25:19.280> identity<00:25:19.700> their 00:25:19.930 --> 00:25:19.940 align:start position:0% saying the sender of the identity their 00:25:19.940 --> 00:25:22.150 align:start position:0% saying the sender of the identity their private<00:25:20.330> keys<00:25:20.510> were<00:25:20.660> exposed<00:25:21.049> no<00:25:21.650> the<00:25:21.799> private 00:25:22.150 --> 00:25:22.160 align:start position:0% private keys were exposed no the private 00:25:22.160 --> 00:25:25.840 align:start position:0% private keys were exposed no the private keys<00:25:22.400> are<00:25:22.610> not<00:25:22.760> exposed<00:25:23.240> and<00:25:23.510> we<00:25:24.110> are<00:25:24.440> even<00:25:24.850> the 00:25:25.840 --> 00:25:25.850 align:start position:0% keys are not exposed and we are even the 00:25:25.850 --> 00:25:27.640 align:start position:0% keys are not exposed and we are even the private<00:25:26.090> keys<00:25:26.360> should<00:25:26.720> not<00:25:26.900> even<00:25:27.140> leave<00:25:27.350> the 00:25:27.640 --> 00:25:27.650 align:start position:0% private keys should not even leave the 00:25:27.650 --> 00:25:30.850 align:start position:0% private keys should not even leave the device<00:25:28.299> so<00:25:29.299> private<00:25:30.020> key<00:25:30.140> is<00:25:30.260> something<00:25:30.620> that 00:25:30.850 --> 00:25:30.860 align:start position:0% device so private key is something that 00:25:30.860 --> 00:25:33.580 align:start position:0% device so private key is something that only<00:25:31.190> you<00:25:31.549> hold<00:25:31.970> and<00:25:32.299> it's<00:25:32.600> of<00:25:32.809> I<00:25:32.990> would<00:25:33.380> say 00:25:33.580 --> 00:25:33.590 align:start position:0% only you hold and it's of I would say 00:25:33.590 --> 00:25:35.470 align:start position:0% only you hold and it's of I would say that's<00:25:33.919> it's<00:25:34.669> very<00:25:34.910> important<00:25:35.270> in<00:25:35.390> any 00:25:35.470 --> 00:25:35.480 align:start position:0% that's it's very important in any 00:25:35.480 --> 00:25:37.120 align:start position:0% that's it's very important in any cryptographic<00:25:35.840> system<00:25:36.500> that<00:25:36.679> private<00:25:36.950> key<00:25:37.100> is 00:25:37.120 --> 00:25:37.130 align:start position:0% cryptographic system that private key is 00:25:37.130 --> 00:25:39.280 align:start position:0% cryptographic system that private key is keep<00:25:37.400> keep<00:25:37.700> sacred<00:25:38.059> the<00:25:38.570> only<00:25:38.750> thing<00:25:38.960> that<00:25:39.140> we 00:25:39.280 --> 00:25:39.290 align:start position:0% keep keep sacred the only thing that we 00:25:39.290 --> 00:25:41.350 align:start position:0% keep keep sacred the only thing that we are<00:25:39.340> transferring<00:25:40.340> from<00:25:40.549> one<00:25:40.850> side<00:25:41.179> to<00:25:41.299> the 00:25:41.350 --> 00:25:41.360 align:start position:0% are transferring from one side to the 00:25:41.360 --> 00:25:43.990 align:start position:0% are transferring from one side to the other<00:25:41.530> mainly<00:25:42.530> are<00:25:42.650> proofs<00:25:43.010> of<00:25:43.309> if<00:25:43.640> you<00:25:43.760> want 00:25:43.990 --> 00:25:44.000 align:start position:0% other mainly are proofs of if you want 00:25:44.000 --> 00:25:46.299 align:start position:0% other mainly are proofs of if you want requests<00:25:44.600> for<00:25:44.780> proofs<00:25:45.080> a<00:25:45.320> please<00:25:45.890> prove<00:25:46.250> me 00:25:46.299 --> 00:25:46.309 align:start position:0% requests for proofs a please prove me 00:25:46.309 --> 00:25:49.060 align:start position:0% requests for proofs a please prove me that<00:25:46.730> you<00:25:46.910> are<00:25:47.059> 18<00:25:47.419> years<00:25:47.450> old<00:25:47.929> here<00:25:48.679> comes<00:25:48.950> the 00:25:49.060 --> 00:25:49.070 align:start position:0% that you are 18 years old here comes the 00:25:49.070 --> 00:25:52.690 align:start position:0% that you are 18 years old here comes the proof<00:25:49.570> okay<00:25:50.570> so<00:25:51.020> that's<00:25:51.260> mainly<00:25:51.500> what<00:25:52.160> what 00:25:52.690 --> 00:25:52.700 align:start position:0% proof okay so that's mainly what what 00:25:52.700 --> 00:25:55.150 align:start position:0% proof okay so that's mainly what what the<00:25:53.030> data<00:25:53.240> that's<00:25:53.540> moving<00:25:53.929> is<00:25:54.260> about<00:25:54.559> it's 00:25:55.150 --> 00:25:55.160 align:start position:0% the data that's moving is about it's 00:25:55.160 --> 00:25:58.690 align:start position:0% the data that's moving is about it's about<00:25:55.280> it's<00:25:55.790> about<00:25:55.880> proofs<00:25:56.330> I<00:25:57.610> want<00:25:58.610> to 00:25:58.690 --> 00:25:58.700 align:start position:0% about it's about proofs I want to 00:25:58.700 --> 00:26:00.760 align:start position:0% about it's about proofs I want to mention<00:25:59.090> something<00:25:59.720> that's<00:26:00.020> important<00:26:00.530> we 00:26:00.760 --> 00:26:00.770 align:start position:0% mention something that's important we 00:26:00.770 --> 00:26:03.450 align:start position:0% mention something that's important we have<00:26:00.919> not<00:26:01.100> talked<00:26:01.280> about<00:26:01.900> where<00:26:02.900> all<00:26:03.110> these 00:26:03.450 --> 00:26:03.460 align:start position:0% have not talked about where all these 00:26:03.460 --> 00:26:06.520 align:start position:0% have not talked about where all these miracle<00:26:04.460> treats<00:26:04.730> and<00:26:05.150> all<00:26:05.299> these<00:26:05.540> data<00:26:06.200> is 00:26:06.520 --> 00:26:06.530 align:start position:0% miracle treats and all these data is 00:26:06.530 --> 00:26:11.350 align:start position:0% miracle treats and all these data is stored<00:26:06.950> okay<00:26:08.830> the<00:26:09.830> data<00:26:10.010> each<00:26:10.520> user 00:26:11.350 --> 00:26:11.360 align:start position:0% stored okay the data each user 00:26:11.360 --> 00:26:13.840 align:start position:0% stored okay the data each user each<00:26:12.080> user<00:26:12.410> should<00:26:12.799> be<00:26:12.830> responsible<00:26:13.370> for 00:26:13.840 --> 00:26:13.850 align:start position:0% each user should be responsible for 00:26:13.850 --> 00:26:17.049 align:start position:0% each user should be responsible for their<00:26:14.360> data<00:26:14.600> so<00:26:15.169> if<00:26:15.890> I'm<00:26:16.070> doing<00:26:16.100> claims<00:26:16.669> all 00:26:17.049 --> 00:26:17.059 align:start position:0% their data so if I'm doing claims all 00:26:17.059 --> 00:26:19.210 align:start position:0% their data so if I'm doing claims all the<00:26:17.419> claims<00:26:17.660> that<00:26:17.809> I'm<00:26:17.929> doing<00:26:18.080> with<00:26:18.679> all<00:26:18.980> the 00:26:19.210 --> 00:26:19.220 align:start position:0% the claims that I'm doing with all the 00:26:19.220 --> 00:26:22.150 align:start position:0% the claims that I'm doing with all the miracle<00:26:19.669> the<00:26:20.299> miracle<00:26:20.330> notes<00:26:20.990> all<00:26:21.380> the<00:26:21.650> notes 00:26:22.150 --> 00:26:22.160 align:start position:0% miracle the miracle notes all the notes 00:26:22.160 --> 00:26:26.590 align:start position:0% miracle the miracle notes all the notes of<00:26:22.280> the<00:26:22.400> miracle<00:26:22.700> tree<00:26:22.970> I<00:26:23.510> should<00:26:25.270> care<00:26:26.270> about 00:26:26.590 --> 00:26:26.600 align:start position:0% of the miracle tree I should care about 00:26:26.600 --> 00:26:29.710 align:start position:0% of the miracle tree I should care about that<00:26:27.320> data<00:26:27.590> I<00:26:27.950> can<00:26:28.220> store<00:26:28.610> that<00:26:28.790> data<00:26:28.940> maybe 00:26:29.710 --> 00:26:29.720 align:start position:0% that data I can store that data maybe 00:26:29.720 --> 00:26:31.690 align:start position:0% that data I can store that data maybe there<00:26:29.870> is<00:26:29.960> some<00:26:30.710> people<00:26:31.010> that's<00:26:31.220> comfortable 00:26:31.690 --> 00:26:31.700 align:start position:0% there is some people that's comfortable 00:26:31.700 --> 00:26:35.890 align:start position:0% there is some people that's comfortable in<00:26:31.970> storing<00:26:32.600> that<00:26:32.750> in<00:26:33.020> a<00:26:33.309> Google<00:26:34.309> cloud<00:26:34.900> maybe 00:26:35.890 --> 00:26:35.900 align:start position:0% in storing that in a Google cloud maybe 00:26:35.900 --> 00:26:37.299 align:start position:0% in storing that in a Google cloud maybe there<00:26:36.200> are<00:26:36.320> some<00:26:36.559> governments<00:26:37.070> that<00:26:37.160> they 00:26:37.299 --> 00:26:37.309 align:start position:0% there are some governments that they 00:26:37.309 --> 00:26:39.490 align:start position:0% there are some governments that they have<00:26:37.549> their<00:26:37.760> own<00:26:37.790> premises<00:26:38.210> maybe<00:26:39.200> there<00:26:39.410> are 00:26:39.490 --> 00:26:39.500 align:start position:0% have their own premises maybe there are 00:26:39.500 --> 00:26:41.740 align:start position:0% have their own premises maybe there are solutions<00:26:39.830> that<00:26:40.130> people<00:26:40.700> that<00:26:41.000> want<00:26:41.240> to<00:26:41.419> store 00:26:41.740 --> 00:26:41.750 align:start position:0% solutions that people that want to store 00:26:41.750 --> 00:26:46.000 align:start position:0% solutions that people that want to store those<00:26:42.049> data<00:26:42.650> in<00:26:42.830> an<00:26:43.220> IP<00:26:43.700> FS<00:26:44.530> in<00:26:45.530> an<00:26:45.679> encrypted 00:26:46.000 --> 00:26:46.010 align:start position:0% those data in an IP FS in an encrypted 00:26:46.010 --> 00:26:48.700 align:start position:0% those data in an IP FS in an encrypted way<00:26:46.400> ipfs<00:26:47.150> and<00:26:47.419> maybe<00:26:47.600> using<00:26:47.870> no<00:26:48.290> say<00:26:48.500> no 00:26:48.700 --> 00:26:48.710 align:start position:0% way ipfs and maybe using no say no 00:26:48.710 --> 00:26:51.210 align:start position:0% way ipfs and maybe using no say no cipher<00:26:49.159> just<00:26:49.549> to<00:26:49.760> access 00:26:51.210 --> 00:26:51.220 align:start position:0% cipher just to access 00:26:51.220 --> 00:26:53.970 align:start position:0% cipher just to access so<00:26:51.490> there<00:26:51.670> are<00:26:51.730> many<00:26:51.970> options<00:26:52.240> about<00:26:53.200> where 00:26:53.970 --> 00:26:53.980 align:start position:0% so there are many options about where 00:26:53.980 --> 00:26:59.220 align:start position:0% so there are many options about where the<00:26:54.280> user<00:26:54.490> keeps<00:26:55.150> that<00:26:55.630> data<00:26:55.900> but<00:26:56.970> in<00:26:57.970> a<00:26:58.230> cell 00:26:59.220 --> 00:26:59.230 align:start position:0% the user keeps that data but in a cell 00:26:59.230 --> 00:27:02.010 align:start position:0% the user keeps that data but in a cell sovereign<00:26:59.680> system<00:27:00.160> ajusshi<00:27:00.820> user<00:27:01.480> have<00:27:01.840> to 00:27:02.010 --> 00:27:02.020 align:start position:0% sovereign system ajusshi user have to 00:27:02.020 --> 00:27:04.830 align:start position:0% sovereign system ajusshi user have to take<00:27:02.230> care<00:27:02.530> of<00:27:02.830> his<00:27:03.460> data<00:27:03.640> of<00:27:04.270> course<00:27:04.450> we<00:27:04.630> can 00:27:04.830 --> 00:27:04.840 align:start position:0% take care of his data of course we can 00:27:04.840 --> 00:27:07.890 align:start position:0% take care of his data of course we can provide<00:27:05.530> tools<00:27:05.800> for<00:27:06.150> in<00:27:07.150> order<00:27:07.300> to<00:27:07.570> have<00:27:07.750> the 00:27:07.890 --> 00:27:07.900 align:start position:0% provide tools for in order to have the 00:27:07.900 --> 00:27:10.800 align:start position:0% provide tools for in order to have the users<00:27:08.230> but<00:27:08.940> it's<00:27:09.940> important<00:27:10.540> that<00:27:10.630> we 00:27:10.800 --> 00:27:10.810 align:start position:0% users but it's important that we 00:27:10.810 --> 00:27:14.940 align:start position:0% users but it's important that we understand<00:27:11.500> that<00:27:13.170> when<00:27:14.170> they<00:27:14.320> when<00:27:14.650> you<00:27:14.770> have 00:27:14.940 --> 00:27:14.950 align:start position:0% understand that when they when you have 00:27:14.950 --> 00:27:18.330 align:start position:0% understand that when they when you have a<00:27:14.980> censoring<00:27:15.780> identity<00:27:16.780> you<00:27:17.530> own<00:27:17.830> your 00:27:18.330 --> 00:27:18.340 align:start position:0% a censoring identity you own your 00:27:18.340 --> 00:27:20.160 align:start position:0% a censoring identity you own your identity<00:27:18.850> and<00:27:19.060> that<00:27:19.090> means<00:27:19.480> you<00:27:19.690> own<00:27:19.870> your 00:27:20.160 --> 00:27:20.170 align:start position:0% identity and that means you own your 00:27:20.170 --> 00:27:26.430 align:start position:0% identity and that means you own your data<00:27:22.890> question<00:27:23.890> so<00:27:24.820> as<00:27:25.090> a<00:27:25.900> developer 00:27:26.430 --> 00:27:26.440 align:start position:0% data question so as a developer 00:27:26.440 --> 00:27:28.530 align:start position:0% data question so as a developer obviously<00:27:27.400> I'm<00:27:27.490> very<00:27:27.700> interested<00:27:28.120> in<00:27:28.360> what 00:27:28.530 --> 00:27:28.540 align:start position:0% obviously I'm very interested in what 00:27:28.540 --> 00:27:29.910 align:start position:0% obviously I'm very interested in what you're<00:27:28.690> doing<00:27:29.020> I'm<00:27:29.170> gonna<00:27:29.320> take<00:27:29.530> a<00:27:29.560> look<00:27:29.830> at 00:27:29.910 --> 00:27:29.920 align:start position:0% you're doing I'm gonna take a look at 00:27:29.920 --> 00:27:32.970 align:start position:0% you're doing I'm gonna take a look at your<00:27:30.160> library<00:27:31.030> I'm<00:27:31.720> over<00:27:31.960> here<00:27:32.080> okay<00:27:32.620> I'm 00:27:32.970 --> 00:27:32.980 align:start position:0% your library I'm over here okay I'm 00:27:32.980 --> 00:27:34.890 align:start position:0% your library I'm over here okay I'm gonna<00:27:33.130> take<00:27:33.340> a<00:27:33.400> look<00:27:33.640> at<00:27:33.760> your<00:27:34.000> github 00:27:34.890 --> 00:27:34.900 align:start position:0% gonna take a look at your github 00:27:34.900 --> 00:27:36.830 align:start position:0% gonna take a look at your github libraries<00:27:35.470> as<00:27:35.740> well<00:27:35.770> as<00:27:35.950> your<00:27:36.190> documentation 00:27:36.830 --> 00:27:36.840 align:start position:0% libraries as well as your documentation 00:27:36.840 --> 00:27:39.900 align:start position:0% libraries as well as your documentation one<00:27:37.840> thing<00:27:38.050> just<00:27:38.350> to<00:27:38.560> help<00:27:38.890> me<00:27:39.130> when<00:27:39.550> I<00:27:39.580> start 00:27:39.900 --> 00:27:39.910 align:start position:0% one thing just to help me when I start 00:27:39.910 --> 00:27:42.390 align:start position:0% one thing just to help me when I start that<00:27:40.090> journey<00:27:40.300> is<00:27:40.570> you<00:27:41.470> know<00:27:41.590> compared<00:27:42.190> to 00:27:42.390 --> 00:27:42.400 align:start position:0% that journey is you know compared to 00:27:42.400 --> 00:27:46.230 align:start position:0% that journey is you know compared to what<00:27:43.000> is<00:27:43.870> being<00:27:44.170> developed<00:27:44.410> by<00:27:44.700> you<00:27:45.700> port<00:27:45.970> in 00:27:46.230 --> 00:27:46.240 align:start position:0% what is being developed by you port in 00:27:46.240 --> 00:27:49.650 align:start position:0% what is being developed by you port in the<00:27:46.630> etherium<00:27:46.990> space<00:27:47.290> or<00:27:47.970> you<00:27:48.970> know<00:27:49.090> sovereign 00:27:49.650 --> 00:27:49.660 align:start position:0% the etherium space or you know sovereign 00:27:49.660 --> 00:27:53.430 align:start position:0% the etherium space or you know sovereign or<00:27:49.900> hyper<00:27:50.230> ledger<00:27:50.500> indie<00:27:51.600> on<00:27:52.600> their<00:27:52.960> own<00:27:53.110> chain 00:27:53.430 --> 00:27:53.440 align:start position:0% or hyper ledger indie on their own chain 00:27:53.440 --> 00:27:55.980 align:start position:0% or hyper ledger indie on their own chain how<00:27:53.770> would<00:27:54.040> I<00:27:54.070> think<00:27:54.400> about<00:27:54.670> this<00:27:55.360> effort<00:27:55.780> in 00:27:55.980 --> 00:27:55.990 align:start position:0% how would I think about this effort in 00:27:55.990 --> 00:27:58.310 align:start position:0% how would I think about this effort in this<00:27:56.170> technology<00:27:56.860> in<00:27:57.040> comparison<00:27:57.730> to<00:27:57.820> those 00:27:58.310 --> 00:27:58.320 align:start position:0% this technology in comparison to those 00:27:58.320 --> 00:28:01.110 align:start position:0% this technology in comparison to those yeah<00:27:59.320> well<00:27:59.530> we<00:27:59.710> are<00:27:59.740> different<00:28:00.640> different 00:28:01.110 --> 00:28:01.120 align:start position:0% yeah well we are different different 00:28:01.120 --> 00:28:03.270 align:start position:0% yeah well we are different different projects<00:28:01.960> that<00:28:02.170> maybe<00:28:02.380> we<00:28:02.560> have<00:28:02.800> different 00:28:03.270 --> 00:28:03.280 align:start position:0% projects that maybe we have different 00:28:03.280 --> 00:28:05.160 align:start position:0% projects that maybe we have different views<00:28:03.370> we<00:28:03.760> are<00:28:03.880> all<00:28:04.120> of<00:28:04.330> us<00:28:04.450> working<00:28:04.900> together 00:28:05.160 --> 00:28:05.170 align:start position:0% views we are all of us working together 00:28:05.170 --> 00:28:08.880 align:start position:0% views we are all of us working together we<00:28:05.740> are<00:28:06.150> connected<00:28:07.150> on<00:28:07.450> each<00:28:07.600> other<00:28:07.840> and<00:28:08.080> we 00:28:08.880 --> 00:28:08.890 align:start position:0% we are connected on each other and we 00:28:08.890 --> 00:28:11.670 align:start position:0% we are connected on each other and we are<00:28:09.340> just<00:28:09.910> working<00:28:10.270> I<00:28:10.720> would<00:28:11.170> say<00:28:11.350> more<00:28:11.560> or 00:28:11.670 --> 00:28:11.680 align:start position:0% are just working I would say more or 00:28:11.680 --> 00:28:14.070 align:start position:0% are just working I would say more or less<00:28:11.860> in<00:28:12.070> the<00:28:12.190> same<00:28:12.220> direction<00:28:12.640> but<00:28:13.480> if<00:28:13.720> even 00:28:14.070 --> 00:28:14.080 align:start position:0% less in the same direction but if even 00:28:14.080 --> 00:28:15.630 align:start position:0% less in the same direction but if even if<00:28:14.200> there<00:28:14.470> are<00:28:14.560> different<00:28:14.950> projects<00:28:15.340> that<00:28:15.430> are 00:28:15.630 --> 00:28:15.640 align:start position:0% if there are different projects that are 00:28:15.640 --> 00:28:17.730 align:start position:0% if there are different projects that are trying<00:28:15.940> to<00:28:16.180> do<00:28:16.330> a<00:28:16.360> little<00:28:16.600> bit<00:28:16.840> the<00:28:16.930> same<00:28:17.110> at 00:28:17.730 --> 00:28:17.740 align:start position:0% trying to do a little bit the same at 00:28:17.740 --> 00:28:19.800 align:start position:0% trying to do a little bit the same at the<00:28:17.980> end<00:28:18.100> end<00:28:18.310> users<00:28:18.760> the<00:28:19.030> developers<00:28:19.510> the 00:28:19.800 --> 00:28:19.810 align:start position:0% the end end users the developers the 00:28:19.810 --> 00:28:22.710 align:start position:0% the end end users the developers the people<00:28:20.110> will<00:28:20.290> just<00:28:20.700> you<00:28:21.700> know<00:28:21.730> be<00:28:22.000> the<00:28:22.180> the<00:28:22.540> are 00:28:22.710 --> 00:28:22.720 align:start position:0% people will just you know be the the are 00:28:22.720 --> 00:28:24.720 align:start position:0% people will just you know be the the are they<00:28:23.230> were<00:28:23.440> they<00:28:23.740> will<00:28:23.920> say<00:28:24.100> which<00:28:24.310> is<00:28:24.490> one<00:28:24.700> the 00:28:24.720 --> 00:28:24.730 align:start position:0% they were they will say which is one the 00:28:24.730 --> 00:28:27.810 align:start position:0% they were they will say which is one the the<00:28:25.510> one<00:28:25.690> more<00:28:25.900> the<00:28:26.800> one<00:28:26.950> was<00:28:27.130> useful<00:28:27.580> to<00:28:27.700> them 00:28:27.810 --> 00:28:27.820 align:start position:0% the one more the one was useful to them 00:28:27.820 --> 00:28:29.880 align:start position:0% the one more the one was useful to them so<00:28:28.060> it's<00:28:28.210> a<00:28:28.480> what<00:28:28.900> do<00:28:28.990> you<00:28:29.050> mean<00:28:29.230> by<00:28:29.410> connected 00:28:29.880 --> 00:28:29.890 align:start position:0% so it's a what do you mean by connected 00:28:29.890 --> 00:28:32.220 align:start position:0% so it's a what do you mean by connected though<00:28:30.040> is<00:28:30.400> there<00:28:30.640> an<00:28:30.760> interrupt<00:28:31.230> just 00:28:32.220 --> 00:28:32.230 align:start position:0% though is there an interrupt just 00:28:32.230 --> 00:28:34.740 align:start position:0% though is there an interrupt just looking<00:28:32.590> to<00:28:32.710> do<00:28:33.090> just<00:28:34.090> connected<00:28:34.510> mean<00:28:34.630> that 00:28:34.740 --> 00:28:34.750 align:start position:0% looking to do just connected mean that 00:28:34.750 --> 00:28:37.200 align:start position:0% looking to do just connected mean that I'm<00:28:34.840> connected<00:28:35.260> with<00:28:35.550> most<00:28:36.550> of<00:28:36.700> the<00:28:36.850> people 00:28:37.200 --> 00:28:37.210 align:start position:0% I'm connected with most of the people 00:28:37.210 --> 00:28:39.680 align:start position:0% I'm connected with most of the people that's<00:28:37.660> developing<00:28:38.260> and<00:28:38.470> we<00:28:38.770> are<00:28:38.890> trying<00:28:39.160> to 00:28:39.680 --> 00:28:39.690 align:start position:0% that's developing and we are trying to 00:28:39.690 --> 00:28:42.150 align:start position:0% that's developing and we are trying to you<00:28:40.690> know<00:28:40.750> for<00:28:40.990> example<00:28:41.050> the<00:28:41.380> three<00:28:41.590> magicians 00:28:42.150 --> 00:28:42.160 align:start position:0% you know for example the three magicians 00:28:42.160 --> 00:28:45.540 align:start position:0% you know for example the three magicians and<00:28:42.460> in<00:28:42.670> different<00:28:43.480> environments<00:28:44.400> there<00:28:45.400> is 00:28:45.540 --> 00:28:45.550 align:start position:0% and in different environments there is 00:28:45.550 --> 00:28:48.210 align:start position:0% and in different environments there is to<00:28:45.790> try<00:28:46.450> to<00:28:46.540> generate<00:28:47.200> those<00:28:47.470> standards<00:28:48.070> and 00:28:48.210 --> 00:28:48.220 align:start position:0% to try to generate those standards and 00:28:48.220 --> 00:28:51.300 align:start position:0% to try to generate those standards and those<00:28:48.430> standards<00:28:48.490> that<00:28:48.970> we<00:28:49.330> are<00:28:49.980> aligned<00:28:50.980> on 00:28:51.300 --> 00:28:51.310 align:start position:0% those standards that we are aligned on 00:28:51.310 --> 00:28:54.300 align:start position:0% those standards that we are aligned on that<00:28:51.640> and<00:28:51.850> trying<00:28:52.480> to<00:28:52.600> get<00:28:52.870> consensus<00:28:53.530> in<00:28:53.770> what 00:28:54.300 --> 00:28:54.310 align:start position:0% that and trying to get consensus in what 00:28:54.310 --> 00:28:57.660 align:start position:0% that and trying to get consensus in what are<00:28:54.430> those<00:28:54.610> protocols<00:28:55.680> that<00:28:56.680> appear<00:28:57.430> the<00:28:57.520> main 00:28:57.660 --> 00:28:57.670 align:start position:0% are those protocols that appear the main 00:28:57.670 --> 00:29:00.750 align:start position:0% are those protocols that appear the main problem<00:28:58.090> here<00:28:58.120> is<00:28:58.510> that<00:28:59.340> now<00:29:00.340> the<00:29:00.400> technology 00:29:00.750 --> 00:29:00.760 align:start position:0% problem here is that now the technology 00:29:00.760 --> 00:29:03.840 align:start position:0% problem here is that now the technology is<00:29:01.060> not<00:29:01.270> clear<00:29:01.570> yet<00:29:01.840> so<00:29:02.170> I<00:29:02.410> would<00:29:03.040> say<00:29:03.190> first<00:29:03.550> we 00:29:03.840 --> 00:29:03.850 align:start position:0% is not clear yet so I would say first we 00:29:03.850 --> 00:29:04.380 align:start position:0% is not clear yet so I would say first we need<00:29:04.000> to 00:29:04.380 --> 00:29:04.390 align:start position:0% need to 00:29:04.390 --> 00:29:06.539 align:start position:0% need to the<00:29:04.480> develop<00:29:05.020> the<00:29:05.170> technology<00:29:05.650> develop<00:29:06.370> some 00:29:06.539 --> 00:29:06.549 align:start position:0% the develop the technology develop some 00:29:06.549 --> 00:29:08.789 align:start position:0% the develop the technology develop some applications<00:29:07.150> see<00:29:07.570> how<00:29:07.780> the<00:29:07.840> people<00:29:08.290> how<00:29:08.440> the 00:29:08.789 --> 00:29:08.799 align:start position:0% applications see how the people how the 00:29:08.799 --> 00:29:10.680 align:start position:0% applications see how the people how the people<00:29:09.190> is<00:29:09.309> using<00:29:09.670> that<00:29:09.790> how<00:29:10.179> the<00:29:10.240> system 00:29:10.680 --> 00:29:10.690 align:start position:0% people is using that how the system 00:29:10.690 --> 00:29:14.310 align:start position:0% people is using that how the system works<00:29:10.960> and<00:29:11.460> once<00:29:12.460> the<00:29:13.330> reason<00:29:13.480> adoption<00:29:14.170> of 00:29:14.310 --> 00:29:14.320 align:start position:0% works and once the reason adoption of 00:29:14.320 --> 00:29:17.760 align:start position:0% works and once the reason adoption of those<00:29:14.799> technologies<00:29:15.400> we<00:29:15.910> can<00:29:16.559> start<00:29:17.559> thinking 00:29:17.760 --> 00:29:17.770 align:start position:0% those technologies we can start thinking 00:29:17.770 --> 00:29:21.690 align:start position:0% those technologies we can start thinking very<00:29:18.610> much<00:29:18.820> in<00:29:19.030> what<00:29:19.059> what<00:29:19.750> what<00:29:20.740> what<00:29:21.460> are<00:29:21.580> the 00:29:21.690 --> 00:29:21.700 align:start position:0% very much in what what what what are the 00:29:21.700 --> 00:29:23.730 align:start position:0% very much in what what what what are the best<00:29:21.850> standards<00:29:22.360> if<00:29:22.690> we<00:29:23.170> define<00:29:23.530> the 00:29:23.730 --> 00:29:23.740 align:start position:0% best standards if we define the 00:29:23.740 --> 00:29:25.890 align:start position:0% best standards if we define the standards<00:29:24.660> prematurely 00:29:25.890 --> 00:29:25.900 align:start position:0% standards prematurely 00:29:25.900 --> 00:29:29.340 align:start position:0% standards prematurely we<00:29:26.380> have<00:29:26.880> women<00:29:27.880> it's<00:29:28.179> possible<00:29:28.840> that<00:29:28.990> maybe 00:29:29.340 --> 00:29:29.350 align:start position:0% we have women it's possible that maybe 00:29:29.350 --> 00:29:31.890 align:start position:0% we have women it's possible that maybe the<00:29:29.559> standards<00:29:30.040> would<00:29:30.460> not<00:29:30.520> be<00:29:30.940> working<00:29:31.420> and 00:29:31.890 --> 00:29:31.900 align:start position:0% the standards would not be working and 00:29:31.900 --> 00:29:34.350 align:start position:0% the standards would not be working and maybe<00:29:32.200> we<00:29:32.350> will<00:29:32.410> have<00:29:32.559> having<00:29:33.549> another<00:29:34.059> de 00:29:34.350 --> 00:29:34.360 align:start position:0% maybe we will have having another de 00:29:34.360 --> 00:29:35.310 align:start position:0% maybe we will have having another de facto<00:29:34.720> standards 00:29:35.310 --> 00:29:35.320 align:start position:0% facto standards 00:29:35.320 --> 00:29:37.799 align:start position:0% facto standards so<00:29:35.650> here<00:29:36.070> the<00:29:36.220> tempos<00:29:36.610> are<00:29:36.790> very<00:29:37.150> important<00:29:37.630> I 00:29:37.799 --> 00:29:37.809 align:start position:0% so here the tempos are very important I 00:29:37.809 --> 00:29:39.600 align:start position:0% so here the tempos are very important I think<00:29:38.110> it's<00:29:38.410> important<00:29:38.890> that<00:29:38.919> there<00:29:39.250> are<00:29:39.340> many 00:29:39.600 --> 00:29:39.610 align:start position:0% think it's important that there are many 00:29:39.610 --> 00:29:42.270 align:start position:0% think it's important that there are many many<00:29:40.030> teams<00:29:40.330> that<00:29:40.540> are<00:29:40.660> working<00:29:40.690> in<00:29:41.200> in<00:29:41.559> in 00:29:42.270 --> 00:29:42.280 align:start position:0% many teams that are working in in in 00:29:42.280 --> 00:29:44.280 align:start position:0% many teams that are working in in in solutions<00:29:42.910> like<00:29:43.179> that<00:29:43.210> or<00:29:43.570> sort<00:29:43.750> of<00:29:43.840> solutions 00:29:44.280 --> 00:29:44.290 align:start position:0% solutions like that or sort of solutions 00:29:44.290 --> 00:29:49.610 align:start position:0% solutions like that or sort of solutions similar<00:29:44.710> to<00:29:44.950> that<00:29:45.240> and<00:29:47.669> keep<00:29:48.669> working<00:29:48.880> and 00:29:49.610 --> 00:29:49.620 align:start position:0% similar to that and keep working and 00:29:49.620 --> 00:29:52.650 align:start position:0% similar to that and keep working and being<00:29:50.620> aware<00:29:50.950> of<00:29:51.190> what<00:29:51.820> all<00:29:52.030> the<00:29:52.179> other<00:29:52.360> teams 00:29:52.650 --> 00:29:52.660 align:start position:0% being aware of what all the other teams 00:29:52.660 --> 00:29:55.919 align:start position:0% being aware of what all the other teams are<00:29:52.929> doing<00:29:53.290> just<00:29:54.100> being<00:29:54.309> transparent<00:29:54.940> and<00:29:55.390> you 00:29:55.919 --> 00:29:55.929 align:start position:0% are doing just being transparent and you 00:29:55.929 --> 00:29:57.600 align:start position:0% are doing just being transparent and you know<00:29:56.020> the<00:29:56.559> nice<00:29:56.679> thing<00:29:56.710> of<00:29:56.980> open-source<00:29:57.250> is 00:29:57.600 --> 00:29:57.610 align:start position:0% know the nice thing of open-source is 00:29:57.610 --> 00:30:00.120 align:start position:0% know the nice thing of open-source is that<00:29:57.760> we<00:29:58.299> don't<00:29:58.480> have<00:29:58.600> to<00:29:58.750> hide<00:29:58.960> anything<00:29:59.290> just 00:30:00.120 --> 00:30:00.130 align:start position:0% that we don't have to hide anything just 00:30:00.130 --> 00:30:02.130 align:start position:0% that we don't have to hide anything just just<00:30:00.700> talk<00:30:00.940> and<00:30:01.179> if<00:30:01.390> they<00:30:01.570> are<00:30:01.630> battery 00:30:02.130 --> 00:30:02.140 align:start position:0% just talk and if they are battery 00:30:02.140 --> 00:30:06.000 align:start position:0% just talk and if they are battery there's<00:30:03.240> as<00:30:04.240> an<00:30:04.390> example<00:30:04.660> alex<00:30:05.620> van<00:30:05.740> der<00:30:05.860> Sar 00:30:06.000 --> 00:30:06.010 align:start position:0% there's as an example alex van der Sar 00:30:06.010 --> 00:30:08.100 align:start position:0% there's as an example alex van der Sar is<00:30:06.190> doing<00:30:06.400> an<00:30:06.520> incredible<00:30:06.790> job<00:30:07.090> in<00:30:07.510> the<00:30:07.929> login 00:30:08.100 --> 00:30:08.110 align:start position:0% is doing an incredible job in the login 00:30:08.110 --> 00:30:11.299 align:start position:0% is doing an incredible job in the login we<00:30:08.440> are<00:30:08.500> just<00:30:09.600> going<00:30:10.600> in<00:30:10.780> that<00:30:10.900> direction 00:30:11.299 --> 00:30:11.309 align:start position:0% we are just going in that direction 00:30:11.309 --> 00:30:14.280 align:start position:0% we are just going in that direction maybe<00:30:12.309> there<00:30:12.549> is<00:30:12.640> some<00:30:13.450> security<00:30:14.020> issue<00:30:14.140> that 00:30:14.280 --> 00:30:14.290 align:start position:0% maybe there is some security issue that 00:30:14.290 --> 00:30:16.980 align:start position:0% maybe there is some security issue that we<00:30:14.650> are<00:30:14.770> not<00:30:15.240> what<00:30:16.240> we<00:30:16.390> don't<00:30:16.510> see<00:30:16.720> it<00:30:16.780> clear 00:30:16.980 --> 00:30:16.990 align:start position:0% we are not what we don't see it clear 00:30:16.990 --> 00:30:18.450 align:start position:0% we are not what we don't see it clear okay<00:30:17.320> we<00:30:17.440> will<00:30:17.559> tell<00:30:17.710> them<00:30:17.860> we're<00:30:18.040> attack<00:30:18.280> him 00:30:18.450 --> 00:30:18.460 align:start position:0% okay we will tell them we're attack him 00:30:18.460 --> 00:30:20.400 align:start position:0% okay we will tell them we're attack him hey<00:30:18.820> what<00:30:19.210> happened<00:30:19.540> with<00:30:19.660> this<00:30:19.809> and<00:30:20.049> there<00:30:20.320> is 00:30:20.400 --> 00:30:20.410 align:start position:0% hey what happened with this and there is 00:30:20.410 --> 00:30:22.560 align:start position:0% hey what happened with this and there is will<00:30:20.559> be<00:30:20.650> a<00:30:20.679> talk<00:30:20.919> and<00:30:21.160> there<00:30:21.280> is<00:30:21.370> a<00:30:21.400> feedback<00:30:22.390> I 00:30:22.560 --> 00:30:22.570 align:start position:0% will be a talk and there is a feedback I 00:30:22.570 --> 00:30:24.210 align:start position:0% will be a talk and there is a feedback I really<00:30:22.900> mean<00:30:22.990> our<00:30:23.140> limitation<00:30:23.830> between<00:30:24.130> the 00:30:24.210 --> 00:30:24.220 align:start position:0% really mean our limitation between the 00:30:24.220 --> 00:30:28.020 align:start position:0% really mean our limitation between the teams<00:30:24.429> and<00:30:24.820> if<00:30:25.090> we<00:30:25.210> work<00:30:25.390> that<00:30:25.570> way<00:30:26.100> mmm<00:30:27.100> I'm 00:30:28.020 --> 00:30:28.030 align:start position:0% teams and if we work that way mmm I'm 00:30:28.030 --> 00:30:32.520 align:start position:0% teams and if we work that way mmm I'm sure<00:30:28.390> that<00:30:29.070> we<00:30:30.070> can<00:30:30.250> get<00:30:30.429> a<00:30:30.669> good<00:30:31.200> we<00:30:32.200> can<00:30:32.350> get<00:30:32.470> a 00:30:32.520 --> 00:30:32.530 align:start position:0% sure that we can get a good we can get a 00:30:32.530 --> 00:30:34.140 align:start position:0% sure that we can get a good we can get a good<00:30:32.740> consensus<00:30:33.250> of<00:30:33.340> that<00:30:33.549> and<00:30:33.760> if<00:30:33.970> we<00:30:34.059> don't 00:30:34.140 --> 00:30:34.150 align:start position:0% good consensus of that and if we don't 00:30:34.150 --> 00:30:35.400 align:start position:0% good consensus of that and if we don't get<00:30:34.270> the<00:30:34.390> consensus<00:30:34.809> maybe<00:30:34.990> it's<00:30:35.140> because 00:30:35.400 --> 00:30:35.410 align:start position:0% get the consensus maybe it's because 00:30:35.410 --> 00:30:37.770 align:start position:0% get the consensus maybe it's because there<00:30:35.590> is<00:30:35.679> two<00:30:36.010> approaches<00:30:36.520> that<00:30:37.210> make<00:30:37.480> sense 00:30:37.770 --> 00:30:37.780 align:start position:0% there is two approaches that make sense 00:30:37.780 --> 00:30:42.600 align:start position:0% there is two approaches that make sense and<00:30:38.049> at<00:30:39.040> the<00:30:39.190> end<00:30:40.410> the<00:30:41.410> people<00:30:41.559> the<00:30:42.040> market<00:30:42.429> the 00:30:42.600 --> 00:30:42.610 align:start position:0% and at the end the people the market the 00:30:42.610 --> 00:30:46.470 align:start position:0% and at the end the people the market the community<00:30:43.290> will<00:30:44.290> decide<00:30:44.679> which<00:30:45.580> one<00:30:45.850> is<00:30:46.210> the 00:30:46.470 --> 00:30:46.480 align:start position:0% community will decide which one is the 00:30:46.480 --> 00:30:49.700 align:start position:0% community will decide which one is the best<00:30:46.630> one<00:30:47.700> last<00:30:48.700> question 00:30:49.700 --> 00:30:49.710 align:start position:0% best one last question 00:30:49.710 --> 00:30:51.930 align:start position:0% best one last question all<00:30:50.710> right<00:30:50.860> Jordi<00:30:51.250> thank<00:30:51.520> you<00:30:51.610> for<00:30:51.760> work 00:30:51.930 --> 00:30:51.940 align:start position:0% all right Jordi thank you for work 00:30:51.940 --> 00:30:53.130 align:start position:0% all right Jordi thank you for work really<00:30:52.270> appreciate<00:30:52.660> it 00:30:53.130 --> 00:30:53.140 align:start position:0% really appreciate it 00:30:53.140 --> 00:30:59.550 align:start position:0% really appreciate it right<00:30:53.710> here 00:30:59.550 --> 00:30:59.560 align:start position:0% 00:30:59.560 --> 00:31:03.450 align:start position:0% I<00:31:00.960> was<00:31:01.960> hoping<00:31:02.170> you'd<00:31:02.350> indulge<00:31:03.100> us<00:31:03.220> a<00:31:03.310> little 00:31:03.450 --> 00:31:03.460 align:start position:0% I was hoping you'd indulge us a little 00:31:03.460 --> 00:31:05.370 align:start position:0% I was hoping you'd indulge us a little more<00:31:03.640> I'm<00:31:04.210> very<00:31:04.480> curious<00:31:04.720> about<00:31:04.870> how<00:31:05.110> you<00:31:05.140> made 00:31:05.370 --> 00:31:05.380 align:start position:0% more I'm very curious about how you made 00:31:05.380 --> 00:31:07.740 align:start position:0% more I'm very curious about how you made it<00:31:05.470> a<00:31:05.560> one-time<00:31:06.280> use<00:31:06.550> proof<00:31:06.940> with<00:31:07.330> the<00:31:07.420> private 00:31:07.740 --> 00:31:07.750 align:start position:0% it a one-time use proof with the private 00:31:07.750 --> 00:31:09.810 align:start position:0% it a one-time use proof with the private key<00:31:07.780> could<00:31:08.470> you<00:31:08.560> really<00:31:08.770> reiterate<00:31:09.130> that<00:31:09.430> one 00:31:09.810 --> 00:31:09.820 align:start position:0% key could you really reiterate that one 00:31:09.820 --> 00:31:10.440 align:start position:0% key could you really reiterate that one more<00:31:10.000> time 00:31:10.440 --> 00:31:10.450 align:start position:0% more time 00:31:10.450 --> 00:31:12.660 align:start position:0% more time the<00:31:11.020> one-time<00:31:11.440> proof<00:31:11.770> the<00:31:12.190> proof<00:31:12.220> that<00:31:12.490> not 00:31:12.660 --> 00:31:12.670 align:start position:0% the one-time proof the proof that not 00:31:12.670 --> 00:31:14.940 align:start position:0% the one-time proof the proof that not reducible<00:31:13.090> proof<00:31:13.390> you<00:31:13.540> mean<00:31:13.690> yeah<00:31:14.200> okay<00:31:14.770> yeah 00:31:14.940 --> 00:31:14.950 align:start position:0% reducible proof you mean yeah okay yeah 00:31:14.950 --> 00:31:16.860 align:start position:0% reducible proof you mean yeah okay yeah okay<00:31:14.980> that<00:31:15.460> is<00:31:15.610> imagine<00:31:16.300> that<00:31:16.330> I<00:31:16.510> want<00:31:16.750> to 00:31:16.860 --> 00:31:16.870 align:start position:0% okay that is imagine that I want to 00:31:16.870 --> 00:31:18.870 align:start position:0% okay that is imagine that I want to prove<00:31:17.080> that<00:31:17.140> I<00:31:17.530> am<00:31:17.590> from<00:31:17.890> a<00:31:18.010> specific<00:31:18.400> religion 00:31:18.870 --> 00:31:18.880 align:start position:0% prove that I am from a specific religion 00:31:18.880 --> 00:31:24.120 align:start position:0% prove that I am from a specific religion okay<00:31:19.720> I<00:31:21.270> don't<00:31:22.270> want<00:31:22.480> you<00:31:22.690> just<00:31:23.130> you 00:31:24.120 --> 00:31:24.130 align:start position:0% okay I don't want you just you 00:31:24.130 --> 00:31:25.410 align:start position:0% okay I don't want you just you understand<00:31:24.580> that<00:31:24.700> you<00:31:24.820> I<00:31:24.850> don't<00:31:25.120> want<00:31:25.300> you 00:31:25.410 --> 00:31:25.420 align:start position:0% understand that you I don't want you 00:31:25.420 --> 00:31:27.720 align:start position:0% understand that you I don't want you that<00:31:25.570> you<00:31:25.810> are<00:31:25.960> able<00:31:26.170> to<00:31:26.470> prove<00:31:26.860> to<00:31:27.340> everybody 00:31:27.720 --> 00:31:27.730 align:start position:0% that you are able to prove to everybody 00:31:27.730 --> 00:31:30.240 align:start position:0% that you are able to prove to everybody else<00:31:28.120> that<00:31:29.080> I'm<00:31:29.230> from<00:31:29.440> that<00:31:29.560> pollution<00:31:29.950> but 00:31:30.240 --> 00:31:30.250 align:start position:0% else that I'm from that pollution but 00:31:30.250 --> 00:31:32.820 align:start position:0% else that I'm from that pollution but actually<00:31:30.670> I<00:31:30.730> want<00:31:30.970> to<00:31:31.030> prove<00:31:31.330> you<00:31:31.540> okay<00:31:32.140> so<00:31:32.680> the 00:31:32.820 --> 00:31:32.830 align:start position:0% actually I want to prove you okay so the 00:31:32.830 --> 00:31:35.310 align:start position:0% actually I want to prove you okay so the proof<00:31:33.070> that<00:31:33.100> I'm<00:31:33.430> sending<00:31:33.730> to<00:31:34.060> you<00:31:34.240> is<00:31:34.600> a<00:31:34.900> proof 00:31:35.310 --> 00:31:35.320 align:start position:0% proof that I'm sending to you is a proof 00:31:35.320 --> 00:31:38.430 align:start position:0% proof that I'm sending to you is a proof so<00:31:36.190> I<00:31:36.220> am<00:31:36.340> proving<00:31:36.610> to<00:31:36.880> you<00:31:37.030> that<00:31:37.060> I<00:31:37.630> either 00:31:38.430 --> 00:31:38.440 align:start position:0% so I am proving to you that I either 00:31:38.440 --> 00:31:43.190 align:start position:0% so I am proving to you that I either I'm<00:31:39.250> from<00:31:39.580> that<00:31:39.730> religion<00:31:40.270> or<00:31:40.450> either<00:31:41.790> I'm<00:31:42.790> I 00:31:43.190 --> 00:31:43.200 align:start position:0% I'm from that religion or either I'm I 00:31:43.200 --> 00:31:47.600 align:start position:0% I'm from that religion or either I'm I hope<00:31:44.200> I<00:31:44.440> have<00:31:44.860> your<00:31:45.310> private<00:31:45.790> key<00:31:45.970> which<00:31:46.930> I<00:31:47.080> run 00:31:47.600 --> 00:31:47.610 align:start position:0% hope I have your private key which I run 00:31:47.610 --> 00:31:50.580 align:start position:0% hope I have your private key which I run okay<00:31:48.610> so<00:31:48.970> I<00:31:49.000> will<00:31:49.360> be<00:31:49.510> able<00:31:49.720> to<00:31:49.840> create<00:31:50.020> a<00:31:50.110> valid 00:31:50.580 --> 00:31:50.590 align:start position:0% okay so I will be able to create a valid 00:31:50.590 --> 00:31:54.300 align:start position:0% okay so I will be able to create a valid proof<00:31:50.860> if<00:31:51.280> I<00:31:51.550> have<00:31:51.850> your<00:31:52.030> private<00:31:52.420> key<00:31:52.600> or<00:31:52.840> I<00:31:53.590> am 00:31:54.300 --> 00:31:54.310 align:start position:0% proof if I have your private key or I am 00:31:54.310 --> 00:31:57.420 align:start position:0% proof if I have your private key or I am from<00:31:54.580> that<00:31:54.610> I'm<00:31:55.170> and<00:31:56.170> I'm<00:31:56.500> from<00:31:56.830> that<00:31:56.860> religion 00:31:57.420 --> 00:31:57.430 align:start position:0% from that I'm and I'm from that religion 00:31:57.430 --> 00:31:59.760 align:start position:0% from that I'm and I'm from that religion because<00:31:58.420> I<00:31:58.600> don't<00:31:58.810> have<00:31:58.990> your<00:31:59.140> private<00:31:59.590> key 00:31:59.760 --> 00:31:59.770 align:start position:0% because I don't have your private key 00:31:59.770 --> 00:32:04.190 align:start position:0% because I don't have your private key the<00:32:00.280> only<00:32:00.310> way<00:32:00.760> to<00:32:00.820> generate<00:32:01.420> a<00:32:01.780> proof<00:32:02.560> of<00:32:02.950> that 00:32:04.190 --> 00:32:04.200 align:start position:0% the only way to generate a proof of that 00:32:04.200 --> 00:32:10.650 align:start position:0% the only way to generate a proof of that kind<00:32:05.200> is<00:32:05.520> by<00:32:07.380> really<00:32:08.380> having<00:32:09.190> the<00:32:09.400> having<00:32:10.180> so 00:32:10.650 --> 00:32:10.660 align:start position:0% kind is by really having the having so 00:32:10.660 --> 00:32:13.440 align:start position:0% kind is by really having the having so happy<00:32:10.960> having<00:32:11.440> the<00:32:11.560> claim<00:32:11.830> that<00:32:12.640> says<00:32:13.150> that 00:32:13.440 --> 00:32:13.450 align:start position:0% happy having the claim that says that 00:32:13.450 --> 00:32:15.840 align:start position:0% happy having the claim that says that I'm<00:32:13.630> from<00:32:13.870> that<00:32:14.020> religion<00:32:14.500> okay<00:32:15.280> so<00:32:15.520> when<00:32:15.820> I 00:32:15.840 --> 00:32:15.850 align:start position:0% I'm from that religion okay so when I 00:32:15.850 --> 00:32:19.080 align:start position:0% I'm from that religion okay so when I send<00:32:16.210> you<00:32:16.300> that<00:32:16.570> proof<00:32:17.070> you<00:32:18.070> have<00:32:18.760> the 00:32:19.080 --> 00:32:19.090 align:start position:0% send you that proof you have the 00:32:19.090 --> 00:32:21.570 align:start position:0% send you that proof you have the warranty<00:32:19.660> the<00:32:20.410> time<00:32:20.650> from<00:32:20.920> that<00:32:21.100> religion 00:32:21.570 --> 00:32:21.580 align:start position:0% warranty the time from that religion 00:32:21.580 --> 00:32:23.960 align:start position:0% warranty the time from that religion because<00:32:22.150> I<00:32:22.300> don't<00:32:22.570> hold<00:32:22.750> your<00:32:22.930> private<00:32:23.290> key 00:32:23.960 --> 00:32:23.970 align:start position:0% because I don't hold your private key 00:32:23.970 --> 00:32:26.400 align:start position:0% because I don't hold your private key what<00:32:24.970> happened<00:32:25.420> when<00:32:25.540> you<00:32:25.690> take<00:32:25.930> that<00:32:26.110> proof 00:32:26.400 --> 00:32:26.410 align:start position:0% what happened when you take that proof 00:32:26.410 --> 00:32:30.480 align:start position:0% what happened when you take that proof out<00:32:26.700> outside<00:32:28.590> when<00:32:29.590> you<00:32:29.710> publish<00:32:30.100> that<00:32:30.130> proof 00:32:30.480 --> 00:32:30.490 align:start position:0% out outside when you publish that proof 00:32:30.490 --> 00:32:34.490 align:start position:0% out outside when you publish that proof you<00:32:31.420> are<00:32:31.540> saying<00:32:31.810> to<00:32:32.110> the<00:32:32.200> people<00:32:33.120> world 00:32:34.490 --> 00:32:34.500 align:start position:0% you are saying to the people world 00:32:34.500 --> 00:32:38.910 align:start position:0% you are saying to the people world surely<00:32:35.500> is<00:32:35.920> either<00:32:36.220> from<00:32:37.090> that<00:32:37.240> religion<00:32:37.780> or<00:32:37.960> I 00:32:38.910 --> 00:32:38.920 align:start position:0% surely is either from that religion or I 00:32:38.920 --> 00:32:44.630 align:start position:0% surely is either from that religion or I hold<00:32:39.930> my<00:32:40.930> private<00:32:41.440> key<00:32:42.120> so<00:32:43.200> everybody<00:32:44.200> knows 00:32:44.630 --> 00:32:44.640 align:start position:0% hold my private key so everybody knows 00:32:44.640 --> 00:32:47.820 align:start position:0% hold my private key so everybody knows that<00:32:45.640> you<00:32:45.790> hold<00:32:46.060> your<00:32:46.240> private<00:32:46.600> key<00:32:46.780> so<00:32:47.590> this 00:32:47.820 --> 00:32:47.830 align:start position:0% that you hold your private key so this 00:32:47.830 --> 00:32:51.570 align:start position:0% that you hold your private key so this you<00:32:48.700> can't<00:32:49.000> generate<00:32:49.390> as<00:32:49.630> many<00:32:49.900> proofs<00:32:50.580> even 00:32:51.570 --> 00:32:51.580 align:start position:0% you can't generate as many proofs even 00:32:51.580 --> 00:32:54.390 align:start position:0% you can't generate as many proofs even as<00:32:52.030> you<00:32:52.510> want<00:32:52.750> if<00:32:53.110> I'm<00:32:53.470> from<00:32:53.770> that<00:32:53.890> religion<00:32:54.250> or 00:32:54.390 --> 00:32:54.400 align:start position:0% as you want if I'm from that religion or 00:32:54.400 --> 00:32:58.830 align:start position:0% as you want if I'm from that religion or not<00:32:54.990> so<00:32:55.990> this<00:32:56.230> proof<00:32:56.620> to<00:32:57.340> the<00:32:57.430> people<00:32:57.820> is<00:32:58.300> not 00:32:58.830 --> 00:32:58.840 align:start position:0% not so this proof to the people is not 00:32:58.840 --> 00:33:00.780 align:start position:0% not so this proof to the people is not valid<00:32:59.230> anymore<00:32:59.320> it's<00:32:59.950> not<00:33:00.100> a<00:33:00.160> valid<00:33:00.460> proof 00:33:00.780 --> 00:33:00.790 align:start position:0% valid anymore it's not a valid proof 00:33:00.790 --> 00:33:03.360 align:start position:0% valid anymore it's not a valid proof other<00:33:01.630> thing<00:33:01.990> is<00:33:02.230> that<00:33:02.260> you<00:33:02.560> can<00:33:02.800> do<00:33:02.980> a<00:33:03.010> claim 00:33:03.360 --> 00:33:03.370 align:start position:0% other thing is that you can do a claim 00:33:03.370 --> 00:33:05.520 align:start position:0% other thing is that you can do a claim saying<00:33:03.760> Jordi's<00:33:04.150> from<00:33:04.300> that<00:33:04.450> religion<00:33:04.900> but 00:33:05.520 --> 00:33:05.530 align:start position:0% saying Jordi's from that religion but 00:33:05.530 --> 00:33:07.770 align:start position:0% saying Jordi's from that religion but then<00:33:05.740> it's<00:33:06.070> according<00:33:06.610> to<00:33:06.850> you<00:33:07.030> that<00:33:07.570> I<00:33:07.690> am 00:33:07.770 --> 00:33:07.780 align:start position:0% then it's according to you that I am 00:33:07.780 --> 00:33:09.690 align:start position:0% then it's according to you that I am from<00:33:07.930> that<00:33:08.080> religion<00:33:08.470> not<00:33:08.950> according<00:33:09.490> to<00:33:09.520> the 00:33:09.690 --> 00:33:09.700 align:start position:0% from that religion not according to the 00:33:09.700 --> 00:33:10.710 align:start position:0% from that religion not according to the church 00:33:10.710 --> 00:33:10.720 align:start position:0% church 00:33:10.720 --> 00:33:13.349 align:start position:0% church the<00:33:11.080> time<00:33:11.229> from<00:33:11.409> that<00:33:11.559> religion<00:33:12.179> that's<00:33:13.179> the 00:33:13.349 --> 00:33:13.359 align:start position:0% the time from that religion that's the 00:33:13.359 --> 00:33:15.930 align:start position:0% the time from that religion that's the difference<00:33:13.749> of<00:33:13.989> course<00:33:14.529> when<00:33:15.039> I<00:33:15.070> proving 00:33:15.930 --> 00:33:15.940 align:start position:0% difference of course when I proving 00:33:15.940 --> 00:33:18.690 align:start position:0% difference of course when I proving something<00:33:16.179> to<00:33:16.359> you<00:33:16.599> I<00:33:16.749> am<00:33:16.840> giving<00:33:17.470> some<00:33:17.739> piece 00:33:18.690 --> 00:33:18.700 align:start position:0% something to you I am giving some piece 00:33:18.700 --> 00:33:22.169 align:start position:0% something to you I am giving some piece of<00:33:18.940> information<00:33:19.679> okay<00:33:20.679> but<00:33:21.369> I'm<00:33:21.609> giving<00:33:21.820> to 00:33:22.169 --> 00:33:22.179 align:start position:0% of information okay but I'm giving to 00:33:22.179 --> 00:33:22.649 align:start position:0% of information okay but I'm giving to you 00:33:22.649 --> 00:33:22.659 align:start position:0% you 00:33:22.659 --> 00:33:26.219 align:start position:0% you I'm<00:33:22.799> not<00:33:23.799> giving<00:33:24.159> a<00:33:24.279> proof<00:33:24.749> so<00:33:25.749> what<00:33:25.899> I'm<00:33:26.049> not 00:33:26.219 --> 00:33:26.229 align:start position:0% I'm not giving a proof so what I'm not 00:33:26.229 --> 00:33:28.889 align:start position:0% I'm not giving a proof so what I'm not giving<00:33:26.529> is<00:33:26.769> the<00:33:27.070> capacity<00:33:27.669> to<00:33:27.909> prove<00:33:28.450> that 00:33:28.889 --> 00:33:28.899 align:start position:0% giving is the capacity to prove that 00:33:28.899 --> 00:33:32.580 align:start position:0% giving is the capacity to prove that that<00:33:28.960> information<00:33:29.409> is<00:33:29.950> valid<00:33:31.409> okay<00:33:32.409> and 00:33:32.580 --> 00:33:32.590 align:start position:0% that information is valid okay and 00:33:32.590 --> 00:33:34.799 align:start position:0% that information is valid okay and that's<00:33:32.739> that's<00:33:33.159> very<00:33:33.340> I<00:33:33.700> think<00:33:34.029> that's<00:33:34.179> very 00:33:34.799 --> 00:33:34.809 align:start position:0% that's that's very I think that's very 00:33:34.809 --> 00:33:36.570 align:start position:0% that's that's very I think that's very tricky<00:33:35.049> here<00:33:35.499> I<00:33:35.559> have<00:33:35.830> to<00:33:35.979> thank<00:33:36.159> you<00:33:36.369> a<00:33:36.399> lot 00:33:36.570 --> 00:33:36.580 align:start position:0% tricky here I have to thank you a lot 00:33:36.580 --> 00:33:39.989 align:start position:0% tricky here I have to thank you a lot here<00:33:37.119> to<00:33:37.149> Vitalik<00:33:37.899> because<00:33:38.639> the<00:33:39.639> rare<00:33:39.820> comes 00:33:39.989 --> 00:33:39.999 align:start position:0% here to Vitalik because the rare comes 00:33:39.999 --> 00:33:42.269 align:start position:0% here to Vitalik because the rare comes from<00:33:40.179> him<00:33:40.389> in<00:33:40.869> instances<00:33:41.559> but<00:33:41.769> I<00:33:41.830> think<00:33:42.099> it's<00:33:42.220> a 00:33:42.269 --> 00:33:42.279 align:start position:0% from him in instances but I think it's a 00:33:42.279 --> 00:33:50.430 align:start position:0% from him in instances but I think it's a cool<00:33:42.460> idea 00:33:50.430 --> 00:33:50.440 align:start position:0% 00:33:50.440 --> 00:33:52.500 align:start position:0% you